Created attachment 16897 [details] my kernel configuration (2.6.25-tuxonice-r3) Hallo! I have a HP NC4200 Laptop with an "Intel 915 GM" GFX-Card. When i use the xf86-video-vesa driver s2ram works great, but when i use "xf86-video-i810" driver, version 2.1.1 X crashes. I can reboot the system by pressing the power button, or access the machine via ssh, but i have no chance to get X working again.
Created attachment 16898 [details] lspci -v
Created attachment 16899 [details] xorf.conf
Created attachment 16900 [details] tail -f /var/log/Xorg.0.log during resume
Please try a newer driver, i.e. 2.3.1 release or git master branch, which includes some suspend/resume fixes. Please attach the _full_ Xorg.0.log.
Hi! Now i upgraded the folling Packages in the attachment. But now i get a black screen, i can access the box via ssh, but i can not access X or console. A full Xorg.0.log is also attached and a xorg.conf. regards Thorsten
Created attachment 16912 [details] installed packages
Created attachment 16913 [details] full Xorg.0.log
Created attachment 16914 [details] xorg.conf
Better comment below lines in xorg.conf, as EXA is the default setting: Option "AccelMethod" "XAA" # XAA & EXA are valid values Option "PageFlip" "true" Option "TripleBuffer" "true" Option "XaaNoSolidFillRect" "false" I don't have other idea. Let Jesse to comment. Maybe we need rename the title now.
(In reply to comment #9) > Better comment below lines in xorg.conf, as EXA is the default setting: > Option "AccelMethod" "XAA" # XAA & EXA are valid values > Option "PageFlip" "true" > Option "TripleBuffer" "true" > Option "XaaNoSolidFillRect" "false" > > I don't have other idea. Let Jesse to comment. Maybe we need rename the title > now. > I commented the lines attached in the following xorg.conf, but this does not solve the error. regards Thorsten
Created attachment 16924 [details] xorg.conf
Created attachment 16925 [details] Xorg.0.log
(In reply to comment #0) > Created an attachment (id=16897) [details] > my kernel configuration (2.6.25-tuxonice-r3) > > Hallo! > I have a HP NC4200 Laptop with an "Intel 915 GM" GFX-Card. When i use the > xf86-video-vesa driver s2ram works great, but when i use "xf86-video-i810" > driver, version 2.1.1 X crashes. I can reboot the system by pressing the power > button, or access the machine via ssh, but i have no chance to get X working > again. > Thorsten, when you say "X crashes" , do you mean it happen when you resume back from s2ram? Normal boot-up will give you a working X, right? Your kernel config shows that you've enabled uvesa. could you please remove any vesa fb kernel module and re-test? thanks.
(In reply to comment #13) > (In reply to comment #0) [...] > > Thorsten, when you say "X crashes" , do you mean it happen when you resume back > from s2ram? Normal boot-up will give you a working X, right? When i start my notebook, X works normal. Suspending to ram works too, but when the machine resumes from suspend to ram, X crashes. I tested the xf86-video-vesa driver and suspend to ram und resume from suspend to ram worked like a charm. > Your kernel config shows that you've enabled uvesa. could you please remove any > vesa fb kernel module and re-test? > > thanks. > Ok, i will compile an other kernel without uvesa and test it, but i think that uvesa is not the problem. regards Thorsten
(In reply to comment #14) > (In reply to comment #13) > > (In reply to comment #0) > [...] > > Your kernel config shows that you've enabled uvesa. could you please remove any > > vesa fb kernel module and re-test? > > > > thanks. > > > > Ok, i will compile an other kernel without uvesa and test it, but i think that > uvesa is not the problem. > > regards Thorsten > Ok, i compiled a kernel without "Support for frame buffer devices". But there is no change, i get a black screen. It must be a Bug in the intel driver. Attached you can find the Xorg.0.log and the kernel config files. regards Thorsten
Created attachment 16933 [details] kernel config
Created attachment 16934 [details] Xorg.0.log
Hi! I changed the name of the report, because of "Existing errors found in hardware state." in the Xorg.0.log file. A Friend of mine has the same Laptop with Debian unstable, but resume works on his Laptop without any errors. Does Debian patch the driver? So i cannot understand what this bug causes. regards Thorsten
> --- Comment #18 from Thorsten Lusser <tlusser@gmail.com> 2008-06-06 06:42:35 PST --- > Does Debian patch the driver? no, we don't.
Hi Thorsten, a couple of things to try/verify: - make sure you're not running vbetool in your suspend/resume path at all it can conflict with the kernel driver suspend/resume code - try suspend/resume from the console only with the i915 DRM driver loaded this *should* work (also try it w/o using s2ram scripts, e.g. echo mem > /sys/power/state) Normally, suspend to ram does a VT switch away from X, suspends, then on resume it'll VT switch back to X. So you could also try switching to a text console by hand before suspending to see if that works. If you're able to resume to a text console but the manual VT switch back to X fails, that will give us a clue. In that case, you could capture register dumps (using the intel_reg_dumper tool in src/reg_dumper) from before suspend and after resume and we can look for problems.
(In reply to comment #20) > Hi Thorsten, a couple of things to try/verify: Hi! > - make sure you're not running vbetool in your suspend/resume path at all > it can conflict with the kernel driver suspend/resume code I deinstalled vbetool. > - try suspend/resume from the console only with the i915 DRM driver loaded > this *should* work (also try it w/o using s2ram scripts, e.g. > echo mem > /sys/power/state) > > Normally, suspend to ram does a VT switch away from X, suspends, then on resume > it'll VT switch back to X. So you could also try switching to a text console > by hand before suspending to see if that works. > If you're able to resume to a > text console but the manual VT switch back to X fails, that will give us a > clue. In that case, you could capture register dumps (using the > intel_reg_dumper tool in src/reg_dumper) from before suspend and after resume > and we can look for problems. > When i suspend X switches to console and then the laptop goes into sleep mode. There is no change, if I go to console manualy. The Laptop suspends normally and wakes up in the console, but if i want to switch to X the same error appears and i can not switch back to console, i can only access the machine via ssh or switch it of by pressing the power button.> regards thorsten
Created attachment 17008 [details] intel_reg_dump before suspend
Created attachment 17009 [details] intel_reg_dump after resume
Hallo! I compiled "intel_reg_dumper" and saved the data before and after suspend(in the console with "echo mem > /sys/power/state") to files which were attached to the bug report. I hope this information can help you. regards Thorsten
Hallo! I found the problem! Gentoo does not provide the "x11-libs/libpciaccess" in the portage. I had to install this package for building the "intel_reg_dumper" by useing a portage overlay. Now resuming works like a charm!(in the console and also under X). So this error only occurs if the libpciaccess package is not installed! Thank you for your help and i hope that this dependency goes into gentoo ebuilds. I have also read that this driver needs x11-libs/libpciaccess in version 0.10 or higher. Regards Thorsten
Ah, so there must have been a library version problem. Thanks for the update.
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.