Bug 64488

Summary: 3.10.0-rc1: WARNING: at drivers/gpu/drm/drm_crtc.c:84 drm_fb_helper_restore_fbdev_mode+0x10/0x40()
Product: xorg Reporter: Ronald <ronald645>
Component: Driver/nouveauAssignee: Nouveau Project <nouveau>
Status: RESOLVED FIXED QA Contact: Xorg Project Team <xorg-team>
Severity: normal    
Priority: medium    
Version: git   
Hardware: x86 (IA32)   
OS: Linux (All)   
Whiteboard:
i915 platform: i915 features:
Attachments:
Description Flags
Last DRM warning (typed over from a photo). Note the tainted flags(!) none

Description Ronald 2013-05-12 10:15:30 UTC 
Created attachment 79192 [details]
Last DRM warning (typed over from a photo). Note the tainted flags(!)

Since a few cycles, it seems that nouveau is preventing the kernel from correctly displaying OOPS, BUGS and Warnings etc etc.

This is because the DRM system seems to provide warnings each time the kernel kills X and moves to console to display these messages.

Today, I enabled some debug options and captured the last WARNING by this system. NOTE: The oops is typed over from a camera photo, so it might not be entirely accurate.

This is an 32bit UP system with the notorious(?) Geforce FX5200 (NV34). I attached the Warning as an attachment.

I modified rsyslog to log directly to disk, hoping to capture more information. When that happens, I will post more.

I think this is also a regression, usually I got errors about page faults and stuff.
Comment 1 Emil Velikov 2013-05-12 10:40:57 UTC 
Hi Ronald

Similar/same case was reported on dri-devel, and the patch [1] has not hit upstream. Can you give it a try


[1] http://lists.freedesktop.org/archives/dri-devel/2013-May/038164.html
Comment 2 Ronald 2013-05-12 10:48:52 UTC 
Thanks! I'll test. Next crash should not be far away on this box...
Comment 3 Ronald 2013-05-13 06:08:42 UTC 
Yes, I can see the OOPS now. Thanks.
Comment 4 Emil Velikov 2013-05-13 10:37:07 UTC 
Glad it helps

The patch has been queued for 3.10 and the stable branches

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.