Bug 33272 - drm related hard-hang
Summary: drm related hard-hang
Status: CLOSED UNREPRODUCIBLE
Alias: None
Product: Drivers
Classification: Unclassified
Component: Video(DRI - Intel) (show other bugs)
Hardware: All Linux
: P1 blocking
Assignee: drivers_video-dri-intel@kernel-bugs.osdl.org
URL:
Keywords:
Depends on:
Blocks: 32012
  Show dependency tree
 
Reported: 2011-04-14 01:29 UTC by Peter Teoh
Modified: 2011-06-12 20:46 UTC (History)
6 users (show)

See Also:
Kernel Version: 2.6.39-rc3
Subsystem:
Regression: Yes
Bisected commit-id:


Attachments
dmesg output immediately after a hard-hang (and then reboot) (118.86 KB, application/octet-stream)
2011-04-14 15:01 UTC, Peter Teoh
Details

Description Peter Teoh 2011-04-14 01:29:10 UTC
The system - while in use - can suddenly hanged itself - display no change, mouse/keyboard not responsive, and even going into the system via ssh is impossible.   The "A" yellow alert signal light on my Lenovo R400 laptop will then start to blink.

Upon reboot the trace is this:

Apr 14 09:02:26 tteikhua-laptop kernel: [ 2132.938702] [drm] capturing error event; look for more information in /debug/dri/0/i915_error_state
Apr 14 09:08:18 tteikhua-laptop syslogd 1.5.0#5ubuntu3: restart.
Apr 14 09:08:18 tteikhua-laptop kernel: Inspecting /boot/System.map-2.6.39-rc3+
Apr 14 09:08:18 tteikhua-laptop kernel: Cannot find map file.
Apr 14 09:08:18 tteikhua-laptop kernel: Loaded 69004 symbols from 47 modules.

And the funny thing is if I mount debugfs the /debug directory, I can see there is no error in the i915_error_state output, but when it hanged, being non-responsive to any form of input, there is no way to query the error state - even via ssh.

The previous version of 2.6.38-rc2+ has been wonderful for me, perfectly running system - except for some problem with NFS shutting down, but the present version - linus git-tree updated as of yesterday is not working.

Thanks.
Comment 1 Peter Teoh 2011-04-14 15:01:36 UTC
Created attachment 54362 [details]
dmesg output immediately after a hard-hang (and then reboot)
Comment 2 Rafael J. Wysocki 2011-04-17 18:21:25 UTC
On Sunday, April 17, 2011, Peter Teoh wrote:
> oh yes, as shown in the bug report, the version at linus-git tree is not
> working as of 14 Apr 2011,
> 
> On Sun, Apr 17, 2011 at 8:57 PM, Rafael J. Wysocki <rjw@sisk.pl> wrote:
> 
> > This message has been generated automatically as a part of a summary report
> > of recent regressions.
> >
> > The following bug entry is on the current list of known regressions
> > from 2.6.38.  Please verify if it still should be listed and let the
> > tracking team
> > know (either way).
> >
> >
> > Bug-Entry       : http://bugzilla.kernel.org/show_bug.cgi?id=33272
> > Subject         : drm related hard-hang
> > Submitter       : Peter Teoh <htmldeveloper@gmail.com>
> > Date            : 2011-04-14 01:29 (4 days old)
Comment 3 Peter Teoh 2011-04-20 01:52:11 UTC
Last night (19 Apr 2011) I sync-ed with linus git tree, and the system still hanged - perhaps after about one hour of usage, and this hangup repeats several times after reboot.
Comment 4 Keith Packard 2011-05-14 22:38:51 UTC
It'd be great if you could bisect between -rc2 and -rc3+ to find the problem commit. Otherwise, there's too little information here to be of much use.
Comment 5 Rafael J. Wysocki 2011-05-15 09:20:41 UTC
On Sunday, May 15, 2011, Peter Teoh wrote:
> I am on 2.6.39-rc6+ now and the issue has been resolved.   Thanks.
> 
> On Sun, May 15, 2011 at 6:30 AM, Rafael J. Wysocki <rjw@sisk.pl> wrote:
> 
> > This message has been generated automatically as a part of a summary report
> > of recent regressions.
> >
> > The following bug entry is on the current list of known regressions
> > from 2.6.38.  Please verify if it still should be listed and let the
> > tracking team
> > know (either way).
> >
> >
> > Bug-Entry       : http://bugzilla.kernel.org/show_bug.cgi?id=33272
> > Subject         : drm related hard-hang
> > Submitter       : Peter Teoh <htmldeveloper@gmail.com>
> > Date            : 2011-04-14 01:29 (31 days old)

Note You need to log in before you can comment on or make changes to this bug.