Summary: | Exiting KDE causes lock, loss of video output with 2.6.28-gentoo on x86_64 system. | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Bob Raitz <pappy_mcfae> |
Component: | [OLD] Core system | Assignee: | Gentoo X packagers <x11> |
Status: | RESOLVED NEEDINFO | ||
Severity: | normal | CC: | esigra, jer |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | AMD64 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: |
2.6.28-gentoo.config
Vanilla 2.6.28 .config (for comparison) |
Description
Bob Raitz
2008-12-28 10:47:34 UTC
Created attachment 176580 [details]
2.6.28-gentoo.config
Created attachment 176582 [details]
Vanilla 2.6.28 .config (for comparison)
Thanks for the report. @kde team: I think this should be assigned to you. Please feel free to re-assign if appropriate. what kde version? tried with multiple video drivers? vga or vesa instead of intel? It would really be nice to have more info to go on. I have 2.6.28 working fine with kde4 and both radeon and nvidia-drivers (In reply to comment #4) > what kde version? tried with multiple video drivers? vga or vesa instead of > intel? It would really be nice to have more info to go on. I have 2.6.28 > working fine with kde4 and both radeon and nvidia-drivers > KDE-3.5.10, No, only the Intel. And I'm actually pretty sure it's a problem with the transition to GEM. I'll set up the (gag) vesa driver for verification, but I'm betting it's a GEM issue. Testing with the vesa driver shows that this problem is definitely related to the Intel video driver, and how it's interacting. Even when the system was made unstable with microcode enabled (bug #252798), the display didn't lock coming out of X with the vesa driver. tried rebuilding glibc with the 2.6.28 linux-headers? (In reply to comment #7) > tried rebuilding glibc with the 2.6.28 linux-headers? > How is that going to fix what is OBVIOUSLY a kernel issue? Looks like a intel driver issue to me... even you yourself said "Testing with the vesa driver shows that this problem is definitely related to the Intel video driver" (In reply to comment #9) > Looks like a intel driver issue to me... even you yourself said "Testing with > the vesa driver shows that this problem is definitely related to the Intel > video driver" > Yes, it's either the i915 module(s), or the new drm setup (for intel and GEM), or a deadly combo of both. It doesn't affect my new laptop. However, it seems that this bug pops up with my old Toshiba laptop. I'm not going to run the .28 kernels until the Madagascar Hissing Cockroaches are gone. @X11: Any thoughts about this? Which version of x11-base/xorg-server are we dealing with, here? Looks like bug #253718 may be a duplicate with some more details. @everyone: Please stop posting speculative remarks without providing information about xorg-server/kernel/KDE versions. (In reply to comment #12) > Which version of x11-base/xorg-server are we dealing with, here? Looks like bug > #253718 may be a duplicate with some more details. > > @everyone: Please stop posting speculative remarks without providing > information about xorg-server/kernel/KDE versions. > xorg-server-1.5.3 KDE-3.5.10 And, I would say it's only like the other bug if the other bug is caused by the presence of 2.6.28. Could anyone try to reproduce this bug on the latest ~amd64 gentoo-sources kernel along with xf86-video-intel 2.6.3 or, better yet, 2.7.0 ? Thanks This isn't a kde related issue so i'll remove kde from CC list Please get back to us. Thanks |