Skip to contentSkip to conversation

gen6 (SNB) GPU still stalling besides latest patches

DISCUSSION Nicolas Kalkhof 3 participants 4 messages Jun 21, 2011

lore
Share & tools
lore
#0 lore raw

Thanks for bringing that up. Is there a bug report for this issue? I was just about to file a report myself but I don't want to create any duplicates.

@Chris: What do you mean with giving X a kick? Neither mouse nor keyboard are responding anymore. Killing X from a remote ssh is the only option. :(

Btw. This only happens with SNA enabled. When using the classic (UXA?), dropping back to framebuffer console works fine. I too have a laptop (T420). Is this issues restricted to mobile systems only?

Thanks and regards,
nic

-----Ursprüngliche Nachricht-----
Von: "Andrew Lutomirski" <[email protected]>
Gesendet: Jun 21, 2011 8:24:21 PM
An: "Chris Wilson" <[email protected]>
Betreff: Re: [Intel-gfx] gen6 (SNB) GPU still stalling besides latest patches

Quoted 8 lines · Chris Wilson
Quoted 6 lines · Nicolas Kalkhof
Quoted 1 line

However now it seems I'm unable to get my framebuffer console back after I bailed out of X. The screen stays black but my system is still responsive via ssh. This happens without your patch. I'll do some more investigation to make sure I didnt introduce this issue.

No, that's another bug with /dev/dri/card0 not honouring O_NONBLOCK. Give X a swift kick and it'll wake up again.
-Chris

Quoted 8 lines

Any plans on fixing this (and related bugs)? The SNA driver makes X freeze sometimes for me, and it's hard to recover on a laptop when ctrl-alt-backspace and even alt-sysrq-v don't seem to give me control of my system back.

ssh-ing in and killall -9 Xorg works, but it's not so easy on a laptop.

--Andy

___________________________________________________________
Schon gehört? WEB.DE hat einen genialen Phishing-Filter in die Toolbar eingebaut! http://produkte.web.de/go/toolbar
_______________________________________________
Intel-gfx mailing list [email protected]
http://lists.freedesktop.org/mailman/listinfo/intel-gfx

#1 lore raw
Quoted 3 lines · Nicolas Kalkhof

Thanks for bringing that up. Is there a bug report for this issue? I was just about to file a report myself but I don't want to create any duplicates.

@Chris: What do you mean with giving X a kick? Neither mouse nor keyboard are responding anymore. Killing X from a remote ssh is the only option. :(

ssh from-other-machine killall -INT X; is the only way to do it because X is blocked waiting for an event /dev/dri/card0.

Quoted 1 line

Btw. This only happens with SNA enabled. When using the classic (UXA?), dropping back to framebuffer console works fine.

It's a consequence of handling zaphod and trying to drain all in-fligh DRI2 events to paper-over a crash should one arrive after the Xserver has freed all Resources without calling the destroy handlers...

Quoted 1 line

I too have a laptop (T420). Is this issues restricted to mobile systems only?

Any non-blocking read on /dev/dri/card0 will block without patches... -Chris

Signature · 1 line
Chris Wilson, Intel Open Source Technology Centre
#2 lore raw
Quoted 5 lines · Chris Wilson
Quoted 3 lines · Nicolas Kalkhof

Thanks for bringing that up. Is there a bug report for this issue? I was just about to file a report myself but I don't want to create any duplicates.

@Chris: What do you mean with giving X a kick? Neither mouse nor keyboard are responding anymore. Killing X from a remote ssh is the only option. :(

Quoted 7 lines

ssh from-other-machine killall -INT X; is the only way to do it because X is blocked waiting for an event /dev/dri/card0.

Quoted 1 line

Btw. This only happens with SNA enabled. When using the classic (UXA?), dropping back to framebuffer console works fine.

It's a consequence of handling zaphod and trying to drain all in-fligh DRI2 events to paper-over a crash should one arrive after the Xserver has freed all Resources without calling the destroy handlers...

Shouldn't sysrq-v switch even if X isn't cooperating, though?

--Andy

#3 lore raw
Quoted 1 line · Andrew Lutomirski

Shouldn't sysrq-v switch even if X isn't cooperating, though?

That's what the theory says. In practice I find I ssh hostname echo > /proc/sysrq-trigger... ;-)

If the GPU hung and took the machine with it, only the power switch will reset it.
-Chris

Signature · 1 line
Chris Wilson, Intel Open Source Technology Centre