Bug 36392
| Summary: | 2.6.39, 3.0-rc2 Intel DRI Regression: Black Screen after trying to play video | ||
|---|---|---|---|
| Product: | Drivers | Reporter: | Dennis Jansen (dennis.jansen) |
| Component: | Video(DRI - Intel) | Assignee: | drivers_video-dri-intel (drivers_video-dri-intel) |
| Status: | CLOSED UNREPRODUCIBLE | ||
| Severity: | high | CC: | akpm, bugzilla-kernel, chris, florian, maciej.rutecki, rjw |
| Priority: | P1 | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Kernel Version: | 2.6.39,3.0-rc3 | Subsystem: | |
| Regression: | Yes | Bisected commit-id: | |
| Bug Depends on: | |||
| Bug Blocks: | 32012 | ||
| Attachments: |
xorg log
/var/log/messages excerpt error_state second recorded crash second crash xorg.log 3: error_state 4: error_state in 3.0-rc2 4: xorg.log in 3.0-rc2 4: dmesg in 3.0-rc2 5: var/log/messages in 3.0-rc3 |
||
|
Description
Dennis Jansen
2011-06-01 04:41:57 UTC
Created attachment 60332 [details]
xorg log
Created attachment 60342 [details]
/var/log/messages excerpt
The "dmesg" is quite long. A lot is happening at the end.
I assume that 2.6.38 was OK, and that this is a 2.6.38->2.6.39 regression? Yes, this is a .38->.39 regression. There was a different bug in .38, though, more rare, but also related to a black screen (https://bugzilla.kernel.org/show_bug.cgi?id=27312#c8). Created attachment 61372 [details]
error_state second recorded crash
I've logged the error state from debug/dri this time.
Created attachment 61382 [details]
second crash xorg.log
btw. This time the backlight didn't turn off, no idea why. And I see lots of iwlagn problems in demsg. let me know if you want the full and I'll extract it from /var/log
Still there in 3.0-rc2 Created attachment 61542 [details]
3: error_state
Created attachment 61552 [details]
4: error_state in 3.0-rc2
Created attachment 61562 [details]
4: xorg.log in 3.0-rc2
Created attachment 61572 [details]
4: dmesg in 3.0-rc2
By the way: The backlight doesn't turn off (anymore?). (Maybe I confused that with the other bug?)
And it always happened with mplayer, never with flash video.
Ok, it's actually much worse now, it crashes really hard on VT switch between X and console sometimes now. I can't say any more than that because it's a bit harder to reproduce and its a very hard freeze: no reisub, no response in any way. wifi still blinking but otherwise unresponsive. And as a make was going on, I had to replace the entire source tree because several files were cut off somewhere or filled with junk data. this might be related to "[drm:drm_mode_getfb] *ERROR* invalid framebuffer id" which shows up each time I switch out of X and back in. On Monday, June 13, 2011, Dennis Jansen wrote:
> On Sun, Jun 12, 2011 at 11:12 PM, Rafael J. Wysocki <rjw@sisk.pl> wrote:
> > This message has been generated automatically as a part of a report
> > of regressions introduced between 2.6.38 and 2.6.39.
> >
> > The following bug entry is on the current list of known regressions
> > introduced between 2.6.38 and 2.6.39. Please verify if it still should
> > be listed and let the tracking team know (either way).
>
> Yes it should. And there's nobody actively working on it yet it seems.
> >
> >
> > Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=36392
> > Subject : 2.6.39, 3.0-rc2 Intel DRI Regression: Black Screen after
> trying to play video
> > Submitter : Dennis Jansen <dennis.jansen@web.de>
> > Date : 2011-06-01 04:41 (12 days old)
On Wed, Jun 15, 2011 at 8:52 PM, Jesse Barnes <jbarnes@virtuousgeek.org> wrote: > On Sun, 12 Jun 2011 23:12:11 +0200 (CEST) > "Rafael J. Wysocki" <rjw@sisk.pl> wrote: > >> This message has been generated automatically as a part of a report >> of regressions introduced between 2.6.38 and 2.6.39. >> >> The following bug entry is on the current list of known regressions >> introduced between 2.6.38 and 2.6.39. 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=36392 >> Subject : 2.6.39, 3.0-rc2 Intel DRI Regression: Black Screen >> after trying to play video >> Submitter : Dennis Jansen <dennis.jansen@web.de> >> Date : 2011-06-01 04:41 (12 days old) > > Did you ever bisect this issue? > > -- > Jesse Barnes, Intel Open Source Technology Center > No. Do you mean the black screen or the framebuffer id error? Because the black screen problem is not really bisectable. I don't know how exactly to provoke it. It doesn't happen immediately after boot, but after at least a day or so and one or more suspends I think. And not knowing what exactly is need to provoke it, it would take *quite a while* to get there. I'm currently trying -rc3 to see if things have improved. The GPU hang is due to the broken xf86-video-intel DDX. The blank screen is due to failed reset on the chip. The "invalid framebuffer id" error is relatively harmless and due to a silly Ubuntu patch. I think this is fixed in 3.0-rc3. No, it wasn't. It took longer this time than before. But that could just be random of course. Created attachment 62752 [details]
5: var/log/messages in 3.0-rc3
attachded messages from 3.0-rc3.
First you see resume from standby, then the crash, then a new clean boot.
As always, it happened when trying to playback a video.
So Chris, are you saying that the crash is due to the driver being "too old"? If so, is this a Won't fix? Do I have to upgrade my distribution or at least X driver to use and keep testing new releases? I haven't noticed this anymore after the last -rc upgrade. Hoping it's not just accident or less frequent, I'm closing the bug. Thanks for following up on this. If the fix is not known, we better close it as unreproducible. Regards, Flo |