DaemonForums  

Go Back   DaemonForums > OpenBSD > OpenBSD General

OpenBSD General Other questions regarding OpenBSD which do not fit in any of the categories below.

Reply
 
Thread Tools Display Modes
  #1   (View Single Post)  
Old 17th December 2017
mefisto mefisto is offline
Port Guard
 
Join Date: Sep 2017
Posts: 24
Default Strange dmessage upon upgrade to 6.2

Greetings all,

after upgrading from 6.1 to 6.2 a message "vblank wait timed out on crtc 1", repeated five times appears during startup.

My search does not seem to result in any relevant topic or solution; consequently, any help would be appreciated.

Kindest regards,

M
Reply With Quote
  #2   (View Single Post)  
Old 17th December 2017
johnR johnR is offline
Port Guard
 
Join Date: Nov 2017
Posts: 14
Default

That's something to do with your graphics hardware. Were there any changes that could affect your particular hardware (you didn't mention what you're using) between 6.1 and 6.2?
Reply With Quote
  #3   (View Single Post)  
Old 17th December 2017
LeFrettchen's Avatar
LeFrettchen LeFrettchen is offline
Marveled user
 
Join Date: Aug 2012
Location: Bronvaux, France
Posts: 272
Default

You can try to change the acceleration method of your graphic driver.

Depending on your graphic card, you've got several options for AccelMethod.

In xorg.conf :
Code:
Section "your_device"
  Identifier "your_dev_name"
  Driver "your_driver_name"
  AccelMethod "off" // or "SNA" or "UXA" or ...
EndSection
I.e. with a intel HD graphics, you can find options here : OpenBSD man's page - intel(4)
__________________
The secret of wisdom is not wisdom itself, it's the road that leads us there.
Reply With Quote
  #4   (View Single Post)  
Old 17th December 2017
jggimi's Avatar
jggimi jggimi is offline
More noise than signal
 
Join Date: May 2008
Location: USA
Posts: 6,044
Default

The message is produced by sys/dev/pci/drm/drm_irq.c, which provides IRQ and vblank support for DRM in the kernel. It was added as part of revision 1.68, one of the two revisions to this module between OpenBSD-release 6.1 and 6.2.
Code:
----------------------------
revision 1.68
date: 2017/07/01 16:14:10;  author: kettenis;  state: Exp;  lines: +1076 -478;  commitid: KnwRPOZok9A30HI4;
Update inteldrm(4) to code based on Linux 4.4.70.  This brings us support for
Skylake and Cherryview and better support for Broadwell and Valleyview.  Also
adds MST support.  Some tweaks to the TTM code and radeondrm(4) to keep it
working with the updated generic DRM code needed for inteldrm(4).

Tested by many.
----------------------------
Reply With Quote
  #5   (View Single Post)  
Old 17th December 2017
mefisto mefisto is offline
Port Guard
 
Join Date: Sep 2017
Posts: 24
Default

Hi johnR,

thank you for your answer. It is the same hardware, just re-installation 6.2 instead of 6.1.

Hi LeFrettchen,

thank you for your suggestion. I will try that, but please also see my reply to jggimi.

Hi jggimi,

thank you for your answer. Since you noticed the source emitting the message, I wonder if there is not any relation with another message just received on a console: "error: [drmid81937:intel_pipe_update_start] *ERROR* Potential atomic update update failure on pipe A".

How to approach debugging?

Kindest regards,

M
Reply With Quote
  #6   (View Single Post)  
Old 17th December 2017
jggimi's Avatar
jggimi jggimi is offline
More noise than signal
 
Join Date: May 2008
Location: USA
Posts: 6,044
Default

Quote:
Originally Posted by mefisto View Post
...I wonder if there is not any relation with another message just received on a console..
Yes. This is produced by src/sys/dev/pci/drm/i915/intel_sprite.c, which also had the same change log entry (revision 1.8) on July 1, and this message was also included as part of the code in this revision.
Quote:
How to approach debugging?
It is not clear to me that there is a bug. These messages are produced when hardware is not behaving as expected.
  • To understand the root cause of these messages, on your own, you will need to read the source code to determine why these warnings are produced.
  • If you want assistance from the OpenBSD Project to understand why these messages are produced, and whether you should be concerned about them, you can submit an informal query to the Project's misc@ mailing list. At minimum, you must include your dmesg(8) so that your hardware environment and your specific kernel that is reporting the messages are made clear.
  • Formal problem reports are sent to the bugs@ mailing list, most often through the use of the sendbug(1) tool.
You can do the same sort of research I did. It isn't debugging, and all it takes is a cvs(1) working directory of the kernel source. Example:

$ find /usr/src/sys -type f -exec grep "Potential atomic update failure" {} +

$ cd /usr/src/sys/dev/pci/drm/i915
$ cvs log intel_sprite.c | less
$ cvs blame intel_sprite.c | less

Last edited by jggimi; 17th December 2017 at 05:29 PM. Reason: typos
Reply With Quote
  #7   (View Single Post)  
Old 17th December 2017
mefisto mefisto is offline
Port Guard
 
Join Date: Sep 2017
Posts: 24
Default

Hi jggimi,

thank you for the pointers.

Kindest regards,

M
Reply With Quote
  #8   (View Single Post)  
Old 18th December 2017
ibara's Avatar
ibara ibara is offline
WR Slowest SNOBOL4 laptop
 
Join Date: Jan 2014
Posts: 531
Default

Additionally, if one does not want to or cannot check out the cvs tree, the site http://bxr.su can help with your search.
For example:
http://bxr.su/search?q=%22Potential+...roject=OpenBSD
You can get to the CVSweb from any source file, which does what log and blame do, effectively.
Reply With Quote
  #9   (View Single Post)  
Old 18th December 2017
jggimi's Avatar
jggimi jggimi is offline
More noise than signal
 
Join Date: May 2008
Location: USA
Posts: 6,044
Default

Good suggestion!

It may help to know that cvs blame is a synonym for cvs annotate.
Reply With Quote
Reply

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump

Similar Threads
Thread Thread Starter Forum Replies Last Post
strange behavior of PF majkelos OpenBSD Security 2 23rd October 2011 06:23 PM
Strange issues with 7.2 DNAeon FreeBSD General 5 26th September 2009 11:19 AM
Strange lib problem mururoa FreeBSD General 3 1st August 2009 07:34 AM
PF: strange port 21 iwi OpenBSD Security 3 25th November 2008 02:21 PM
strange with dvd+rw-format cyberboy FreeBSD General 0 26th May 2008 05:43 PM


All times are GMT. The time now is 12:12 PM.


Powered by vBulletin® Version 3.8.4
Copyright ©2000 - 2018, Jelsoft Enterprises Ltd.
Content copyright © 2007-2010, the authors
Daemon image copyright ©1988, Marshall Kirk McKusick