i810 Xv crashes after suspend -> infinite resprawn
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
X.Org X server |
Won't Fix
|
High
|
|||
xserver-xorg-video-i810 (Ubuntu) |
Fix Released
|
High
|
Unassigned |
Bug Description
X using the i810 driver on a i915MG chipset will cause a crash. The crash seems
most related use of the Xv video extension, for instance, starting up Totem
which uses it for visulisation display.
The X server then goes into an infinite loop of:
Respawn
Watch pointer
Arrow pointer
Respawn
With the background remaining black. It is not possible to get to a console and
the only way out is sysrq-s sysrq-u sysrq. On reboot, /var/log/Xorg.0.old contains:
Error in I830WaitLpRing(), now is -1274101884, start is -1274103885
pgetbl_ctl: 0x1ffc0001 pgetbl_err: 0x0
ipeir: 0 iphdr: 1810000
LP ring tail: c8 head: 0 len: 1f801 start 0
eir: 0 esr: 0 emr: ffff
instdone: ffc0 instpm: 0
memmode: 108 instps: f0000
hwstam: fffe ier: 2 imr: 8 iir: 220
space: 130864 wanted 131064
(II) I810(0): [drm] removed 1 reserved context for kernel
(II) I810(0): [drm] unmapping 8192 bytes of SAREA 0xe04c3000 at 0xb7940000
Fatal server error:
lockup
Error in I830WaitLpRing(), now is -1274099866, start is -1274101867
pgetbl_ctl: 0x1ffc0001 pgetbl_err: 0x0
ipeir: 0 iphdr: 1810000
LP ring tail: d0 head: 0 len: 1f801 start 0
eir: 0 esr: 0 emr: ffff
instdone: ffc0 instpm: 0
memmode: 108 instps: f0000
hwstam: ffff ier: 0 imr: ffff iir: 220
space: 130856 wanted 131064
FatalError re-entered, aborting
lockup
A suspend-to-RAM cycle had happened at some point a couple of hours before.
Angelo Lisco (angystardust-gmail) wrote : | #1 |
Angelo Lisco (angystardust-gmail) wrote : | #2 |
Paul, i'm now trying the experimental driver provided by Alan Hourihane (http://
Maybe it's too soon to say that but i think the bug is gone away: i cannot reproduce the crash anymore!
However look at this: https:/
Changed in xserver-xorg-driver-i810: | |
status: | Unconfirmed → Confirmed |
DanH (holmsand-gmail) wrote : | #3 |
This is maybe the same bug as #22741, that's still haunting me.
I've tried a number of the experimental drivers of Alan Hourihane's with breezy, and they have mostly been working really well (no xv-related crashes in a really long while).
Changed in xserver-xorg-driver-i810: | |
assignee: | daniels → nobody |
Changed in xserver-xorg-driver-i810: | |
assignee: | nobody → ubuntu-x-swat |
DanH (holmsand-gmail) wrote : | #4 |
In case it's gone unnoticed: I've attached a patch to bug #22741 that fixes this bug for me.
Baishampayan Ghose (b.ghose) wrote : | #5 |
I can confirm this bug. It hit me after I did a suspend to RAM on my Toshiba Satellite Laptop. I think somebody should apply the backported patch which can be found in bug #22741
Baishampayan Ghose (b.ghose) wrote : Crash log | #6 |
Florian Boucault (fboucault) wrote : Re: crashes after long-use -> infinite resprawn (Xv trigger?) | #7 |
I used to have the same here (T43 1871-W34, i915GM using i810 driver).
Jim Gettys (jg-laptop) wrote : | #8 |
I don't crash after long use.
I did crash after resume with totem, until installing Alan Horihane's driver, which has been working fine for me.
Paul Sladen (sladen) wrote : | #9 |
This happened to me again yesterday - I suppose I should fix it and backport the necessary...
Dave Love (fx-gnu) wrote : | #10 |
There seems to be a suggestion that this is related to
suspending, but it happens to me directly after
rebooting (on a Thinkpad X30 with current Dapper
packages).
Florian Boucault (fboucault) wrote : | #11 |
There are two links on the xorg bugzilla, one closed (https:/
Concerning the closed one, the solution might be in the comment #11 (https:/
I am still reading the full log of the opened one...
Zack Cerza (zcerza-deactivatedaccount) wrote : | #12 |
Marking critical because of the possibility (heh, more like probability) of data loss...
As I understand it, there are fixes for this that people have tested. I haven't yet, but I'm about to. Any chance of getting this fixed before dapper releases? The i810 chips are extremely common in laptops...
Zack Cerza (zcerza-deactivatedaccount) wrote : | #13 |
Someone even submitted a patch[0] to the duplicate bug #22741, but never got a response. :(
DanH (holmsand-gmail) wrote : | #14 |
> Someone even submitted a patch[0] to the
> duplicate bug #22741, but never got a
> response.
Yeah, I did. I'm still using my patched i810 driver, and still haven't had any crashes with it.
Unfortunately, I don't know what else to do. Whining about crashing drivers here seems entirely pointless.
And who the hell is "X SWAT" anyway?
Zack Cerza (zcerza-deactivatedaccount) wrote : | #15 |
You'd think clicking "Ubuntu X SWAT" would take you there, but it doesn't so here's their info page: https:/
By the way, I'm using your patch and haven't seen crashes with it yet.
Changed in xserver-xorg-driver-i810: | |
assignee: | ubuntu-x-swat → nobody |
DanH (holmsand-gmail) wrote : | #16 |
So now the "SWAT team" has given up as well, and the maintainer (Daniel Stone) is nowhere to be seen.
This rather confirms my feeling that it's completely, utterly pointless to file bugs and patches in launchpad.
Paul Sladen (sladen) wrote : | #17 |
I've been meaning to pull this out of CVS since January, thanks to Dan grabbing the base of the patch and to Zack for testing and confirming that it worked.
I've tested the patch and after some fairly harsh treatment still made the xserver freeze (but not resprawn...) but that may have been unrelated. Lets see how it goes:
xserver-
* Remove duplicate dpatch entries in '00list'.
Changes from Dan Holmsand <email address hidden>:
* Backport of some changes from freedesktop.org CVS to fix the
I830WaitLpR
Attempt to close [Malone: #28326] and all its duplicates...
-- Paul Sladen <email address hidden> Sun, 30 Apr 2006 02:51:28 +0200
(Daniels now works for a large Finnish Mobile Phone manufacturer rather than fulltime on Ubuntu).
Changed in xserver-xorg-driver-i810: | |
assignee: | nobody → sladen |
status: | Confirmed → Fix Released |
Angelo Lisco (angystardust-gmail) wrote : | #18 |
ok guys...i upgraded to the last driver but unfortunately bug is still there (even if now i have a different beviour): no more X crash&respawn after suspend or hibernate when i watch a video but totem (xine backend) and mplayer crash as I try to open a large video (1024x768 avi file)...
Angelo Lisco (angystardust-gmail) wrote : mplayer log | #19 |
- mplayer log Edit (2.1 KiB, text/plain)
This is mplayer log...
I think that the most relevant line is:
X11 error: BadAlloc (insufficient resources for operation)
Angelo Lisco (angystardust-gmail) wrote : totem crash | #20 |
- totem crash Edit (614 bytes, text/plain)
and that's totem log...
Same error message as the one found in mplayer log:
The error was 'BadAlloc (insufficient resources for operation)'
Tero Karvinen (karvinen+launchpad) wrote : Still no picture after suspend-to-ram | #21 |
- Xorg log after 2006-04-30 update Edit (72.9 KiB, text/plain)
Still no picture after waking up from suspend-to-ram (s3, sleep). Can connect to computer using ssh. Screen blinks when attempting to change virtual terminals, but not even text mode works. Currently using 915resolution. Using Dapper 6.06 beta 2, just updated. Computer is Travelmate 3004WTMi.
Tero Karvinen (karvinen+launchpad) wrote : | #22 |
Just tested without 915resolution and screen stays blank after sleep (s3) just like above.
Nafallo Bjälevik (nafallo) wrote : | #23 |
That was the wrong button :-/.
Changed in malone: | |
status: | Unconfirmed → Rejected |
Angelo Lisco (angystardust-gmail) wrote : | #24 |
The fix doesn't work...reopening it
Changed in xserver-xorg-driver-i810: | |
status: | Fix Released → Confirmed |
Paul Sladen (sladen) wrote : | #25 |
Tero: you can a different issue, please can you file a bug against 'acpi-support' with the details of your laptop and 'dmidecode' output, along with an lspci -n and details of which video driver it is.
Angelo: The BadAlloc issue I think is a different one (there's another bug somewhere) and is to do with with the media player requesting a Xv drawable larger than the memory allocated to the video card (eg. it happens with the start-up image displayed on loading Xine).
Getting back to the core bug, Dan: can you confirm that the drivers at alanh's page do fix the bug; I'll try and diff out what he has in those although I'm slightly cautious because of the mention of a newer version of libshadow.
DanH (holmsand-gmail) wrote : | #26 |
Paul: I haven't tried alanh's drivers in quite a while. They used to work fine (and fixed this particular bug in september last year), except for DRI and a stupendous amount of logging.
But testing them turned out to be a bit pointless, since the source isn't available.
Why do you ask?
Zack Cerza (zcerza-deactivatedaccount) wrote : | #27 |
I've seen it crash at least once since using the new package. It doesn't respawn, but it does lock up hard. Pressing the power button to do a semi-graceful shutdown no longer works; I have to hold the button down until the power supply cuts off. So, it's still not totally fixed.
Jean-Christophe Baptiste (jc-baptiste) wrote : | #28 |
I am experiencing it again too (Bug #34232).
Paul Sladen (sladen) wrote : | #29 |
My results have been one hard-lock-up and two X-restarting to GDM login. But no infinity respawns.
...I'm not sure which is better.
Florian Boucault (fboucault) wrote : | #30 |
I have had no crashes nor restart since a long time but it seems that the DRI is deactivated. I'll try from a live CD given that I have been playing with my installation a way too much.
Angelo Lisco (angystardust-gmail) wrote : | #31 |
Bug #24371 as been marked as a duplicate of this bug.
Paul Sladen (sladen) wrote : | #32 |
Since applying the separate fix for bug #29880 (Intel bridge fixups), I've not had this crash show up since; I think it is the combination of the two may have nailed it...
Please reopen this if you have the very latest Dapper and still have it.
Changed in xserver-xorg-driver-i810: | |
status: | Confirmed → Fix Released |
Valentijn Sessink (valentijn) wrote : | #33 |
linux-image-386 version 2.6.15-23 still seems to have this bug, but linux-image-686 hasn't.
Paul Sladen (sladen) wrote : | #34 |
Valentijn: I've now fixed this to the point that I can't reproduce it on my laptop. Can you provide the exact set of steps that you are using the reproduce this now (and eg, the kernel version (as above), whether you're using 'totem-xine' or 'totem-gstreamer'.
Valentijn Sessink (valentijn) wrote : Re: [Bug 28326] Re: i810 Xv crashes after suspend -> infinite resprawn | #35 |
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi Paul,
(Hoping a reply by E-mail works)
At Wed, May 24, 2006 at 02:41:58PM -0000, Paul Sladen wrote:
> Valentijn: I've now fixed this to the point that I can't reproduce it
> on my laptop. Can you provide the exact set of steps that you are using
IBM R50e laptop
Ubuntu Dapper install, made up-to-date yesterday, kernel linux-image-386,
trying to suspend-to-disk. We couldn't get either one of them working, but
in the end I think the setup was as follows:
- - "nosplash" grub option
- - "ACPI_HIBERNATE" and "ACPI_SLEEP" both true
- - an extra ec_intr=0 (IIRC) option for the kernel (seen somewhere on the
Thinkwiki)
We did not need to start any programs, just a Fn-F12 (hibernate) or a Fn-F4
(sleep), then a start (either turning laptop on or waking it up) would start
the problem.
I'm sorry to tell you that the laptop itself was shipped to a customer
today, but we have another one waiting for installation and I'll try it out
next week.
In the mean time, you might just want to check a plain simple setup with a
386 kernel and see if it crashes for you. For my X40 laptop, the problem
doesn't occur anymore - even with -386 kernel.
I'll let you know if it pops up.
Kind regards,
Valentijn
- --
http://
Valentijn Sessink <email address hidden> +31(0)20-4214059
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.5 (GNU/Linux)
iD8DBQFEdJpLTRf
Ifxjssb8n8R5ycG
=47vv
-----END PGP SIGNATURE-----
neurol23 (neurol23) wrote : | #36 |
what helped me, was adding the boot parameter "acpi_sleep=
Paul Sladen (sladen) wrote : | #37 |
This isn't fixed, sadly. I had it once a week ago; and bug #40621 is seeing it aswell.
Changed in xserver-xorg-driver-i810: | |
status: | Fix Released → Confirmed |
Morlan Liu (morlanliu) wrote : | #38 |
Could this be related to the problem I'm having.
I just installed Dapper LTS and video playing is not very good. On Breezy it was working perfectly fine, I used Totem-xine to watch everything and Mplayer plugin for Firefox streaming.
Now Totem-xine won't open unless I right-click a file and open it with Movie Player. Also, Mplayer sometimes will display an error saying it can't open the -vo device or something.
If this is related, I hope there's a fix soon. It's driving me crazy!
Valentijn Sessink (valentijn) wrote : | #39 |
Paul, sorry for the fuzz. I can't reproduce the issue now (while we were having a really, really bad day due to the respawn and other stupid issues with a IBM R50 laptop only 2 weeks ago). It must have been a combination of older kernels (might even have been a non upgraded kernel from an older Dapper beta). There are other sleep/resume issues, but none has to do with the infinite respawn in this bug. Sorry, again, for the confusion; as far as I'm concerned, it's fixed.
Jean-Christophe Baptiste (jc-baptiste) wrote : | #40 |
It still remains for me. It is just in a different and at least less serious form.
Totem or any player freeze after few seconds and takes 100% of ressources.
Now, it doesn't freeze anymore the whole X server.
I can kill the application and work normally, BUT I can't read any movie, it freezes again in the same way.
And, more curiously, I get no sound anymore. For example, reading a mp3 file doesn't give anything, the player can't start reading a file and stay stack at the begining.
Mattias Bengtsson (moonlite) wrote : | #41 |
I've been experiencing this a lot lately.
Basically, if i suspend and resume and then use XV the desktop will either crash or the infinite GDM respawn will happen.
This won't happen if i didn't suspend during the session.
I use ubuntu 6.06.
Aigars Mahinovs (aigarius) wrote : | #42 |
Xv crash with infinite GDM respan is still happening to me on nx6110, but it is not deterministic - the crash happens sometimes, but not always. However, when the crash happens it always happlens on start of new video playback and after the laptop has been suspended.
Paul Sladen (sladen) wrote : | #43 |
Aigarius: the sequence, if it does happen will probably be:
1. use an Xvideo-using application (eg. Totem/mplayer)
2. suspend (or hibernate)
3. use an Xvideo-using application (eg. Totem/mplayer)
Mathias De Belder (mathias-de-belder) wrote : | #44 |
I've just ran hard into this bug. The machine exhibiting the problem is a Dell Latitude D505 with an 855GM chip. It may be of interest to note that I've only encountered this once, and that was _after_ installing 2.6.15-26-686 and the corresponding modules, so I hadn't seen it on the 386 flavored kernel. The kernel is not tainted BTW.
More importantly, I *hadn't* put the system into sleep when this happened. It was triggered through MPlayer, trying to get a movie with the XV backend go into fullscreen. The result was a constantly respawning gdm. I did manage to reboot the system gracefully through an SSH login.
Still, I plan on using 6.06 for a long time (I used Warty satisfactorily on this same machine until it was EOL'ed and Breezy came out!), and it would be quite bad if the X system would go down randomly when something uses XV, rendering the for me fantastic 3 year desktop support useless :(.
Anyway, here's the relevant part of the X.org.log file. It's not the original log of the server when it crashed, as it was scribbled over a few times by a continuously respawning GDM.
Error in I830WaitLpRing(), now is -1067443022, start is -1067445023
pgetbl_ctl: 0x3ffe0001 pgetbl_err: 0x0
ipeir: 0 iphdr: 1810000
LP ring tail: 38 head: 0 len: 1f001 start 0
eir: 0 esr: 0 emr: ffff
instdone: ffc0 instpm: 0
memmode: 108 instps: 0
hwstam: ffff ier: 82 imr: 9 iir: 220
space: 131008 wanted 131064
(II) I810(0): [drm] removed 1 reserved context for kernel
(II) I810(0): [drm] unmapping 8192 bytes of SAREA 0xf8d06000 at 0xb78ba000
Fatal server error:
lockup
Error in I830WaitLpRing(), now is -1067440824, start is -1067442825
pgetbl_ctl: 0x3ffe0001 pgetbl_err: 0x0
ipeir: 0 iphdr: 1810000
LP ring tail: 40 head: 0 len: 1f001 start 0
eir: 0 esr: 0 emr: ffff
instdone: ffc0 instpm: 0
memmode: 108 instps: 0
hwstam: ffff ier: 0 imr: ffff iir: 0
space: 131000 wanted 131064
FatalError re-entered, aborting
lockup
joehill (joseph-hill) wrote : | #45 |
For several months, I had the problem of the infinite respawn when I used Totem after a hibernate, but then it went away.
I reinstalled Dapper about a month ago, and I've had the problem for the last week or so of the infinite respawn happening immediately when I turn my computer back on after a hibernate. That is, I can't log in at all and just see the watch pointer reappearing and disappearing on a black screen, and the login dialog doesn't appear.
I'm using the i810 driver on an 855GM chipset.
Niran Babalola (niran) wrote : | #46 |
I'm pretty sure this bug involves swapping somehow. Back when I actually had the bug, I noticed that if I suspended before I'd swapped anything to disk, playing video after I came back would still work. If it had swapped, the unfortunate crashing loop would occur. Since then, I swapped out one of my 256 MB sticks of RAM for a 1 GB one, and I haven't had the bug since.
Allison Karlitskaya (desrt) wrote : | #47 |
I just hit this bug on my 945GM-equipped macbook. On return from sleep I instantly get the evil behaviour described in the initial report. Similar Xorg log:
Could not init font path element /usr/share/
Could not init font path element /usr/share/
Could not init font path element /usr/share/
...go to sleep here...
Error in I830WaitLpRing(), now is -2076544419, start is -2076546420
pgetbl_ctl: 0x3ffc0001 pgetbl_err: 0x0
ipeir: 0 iphdr: 0
LP ring tail: f8 head: 0 len: 1f001 start 0
eir: 0 esr: 1 emr: ffff
instdone: ffc1 instpm: 0
memmode: 306 instps: 2014c0
hwstam: fffe ier: 82 imr: 0 iir: 20
space: 130816 wanted 131064
(II) I810(0): [drm] removed 1 reserved context for kernel
(II) I810(0): [drm] unmapping 8192 bytes of SAREA 0xf8a50000 at 0xb7b5c000
Fatal server error:
lockup
Error in I830WaitLpRing(), now is -2076542416, start is -2076544417
pgetbl_ctl: 0x3ffc0001 pgetbl_err: 0x0
ipeir: 0 iphdr: 0
LP ring tail: 100 head: 0 len: 1f001 start 0
eir: 0 esr: 1 emr: ffff
instdone: ffc1 instpm: 0
memmode: 306 instps: 2014c0
hwstam: ffff ier: 0 imr: ffff iir: 0
space: 130808 wanted 131064
FatalError re-entered, aborting
lockup
Allison Karlitskaya (desrt) wrote : | #48 |
I disagree with the comment about swapping causing the problem. I just tried disabling swap and got no love.
Paul Sladen (sladen) wrote : | #49 |
Hello Ryan, are you running 'edgy' or 6.06 LTS?
Santiago Canez (canez) wrote : | #50 |
I get this bug using Edgy on my Latitude D610 with 915GM video. I won't post the contents of /var/log/Xorg.0.log since it is the same error as listed above in Ryan's post. It seems to happen randomly, meaning I can't reproduce it on queue. Sometimes resuming from suspend works perfectly fine, other times not.
Santiago Canez (canez) wrote : | #51 |
Perhaps I should also mention that under Dapper I only got the problem when using viewing videos with Totem (again randomly) as the original poster did. But now under Edgy it happens right away (randomly) on resume.
Stefanr (stefan-stefanlinux) wrote : | #52 |
Maybe a workaround for some people:
I had a similar problem here, using the Dapper i810 driver with a 82845G/GL integrated graphics. X started up fine, but entering into terminal mode with Ctrl+Alt+F1 and back again caused infinite respawn.
From my Xorg.log:
Error in I830WaitLpRing(), now is -1569538191, start is -1569540192
pgetbl_ctl: 0x1ffe0001 pgetbl_err: 0x49
ipeir: 0 iphdr: 810000
LP ring tail: d0 head: 90 len: 1f001 start 0
eir: 0 esr: 10 emr: ff7b
instdone: ffc1 instpm: 0
memmode: 0 instps: 2c
hwstam: fffe ier: 82 imr: 53c iir: 1
space: 131000 wanted 131064
(II) I810(0): [drm] removed 1 reserved context for kernel
(II) I810(0): [drm] unmapping 8192 bytes of SAREA 0xe0c5f000 at 0xb7885000
Fatal server error:
lockup
Changing the "Internal Graphics Mode Select" bios setting from 1MB to 8MB solved the problem for me.
David Carr (dc) wrote : | #53 |
My Dell D620 is also exhibiting this or a closely related issue. Coming back from suspend I occasionally enter the gdm restart loop which terminates (with failure) after a couple of iterations.
An interesting thing is that this problem occurs more frequently after the machine has been suspended for a longer period of time. If I suspend the machine and immediately wake it back up, I almost never see this bug. However I see it about 20% of the time after the machine has been suspended for a few hours.
I'm going to try enabling SAVE_VIDEO_
Here are the relevant details:
lspci:
00:02.0 VGA compatible controller: Intel Corporation Mobile 945GM/GMS/940GML Express Integrated Graphics Controller (rev 03)
Xorg:
Error in I830WaitLpRing(), now is -354572395, start is -354574396
pgetbl_ctl: 0x3ffc0001 pgetbl_err: 0x0
ipeir: 0 iphdr: 0
LP ring tail: f8 head: 0 len: 1f001 start 0
eir: 0 esr: 1 emr: ffff
instdone: ffc1 instpm: 0
memmode: 10f instps: 2014c0
hwstam: fffe ier: 2 imr: 0 iir: 20
space: 130816 wanted 131064
(II) I810(0): [drm] removed 1 reserved context for kernel
(II) I810(0): [drm] unmapping 8192 bytes of SAREA 0xf8b8d000 at 0xb7a87000
Fatal server error:
lockup
<...snip...>
FatalError re-entered, aborting
lockup
-David Carr
Martin Bergner (martin-bergner) wrote : | #54 |
I have this problem sometimes on edgy, on dapper it just locks up dead. It normally occurs after suspend, but it has happened with just switching back and foward to the console with ctrl-alt-f1.
Alexander Berger (alex-berger) wrote : | #55 |
I experience the same problem with my DELL XPS M1210. The Xserver crashes every now and then with the same "I830WaitLpRing()" error message. I already increased the video memory in the xorg.conf (VideoRam) but this did not help at all. The problem occurs without any obvious reason. I do not use suspend, hibernate or CTRL-ALT-N. The XServer just crashes out of the blue.
Alexander Berger (alex-berger) wrote : | #56 |
Searching on the net has lead me to the following bugs which might be rleated to this one.
https:/
https:/
https:/
And also this one at www.x.org
Andrew Bennetts (spiv) wrote : | #57 |
Looks like bug #63727 is a duplicate?
Also, does title of this bug needs updating? From the comments, it appears this bug is about X failing with I830WaitLpRing errors after suspend/resume in general, not just involving Xv.
David Carr (dc) wrote : | #58 |
The freedesktop.org bug #5774 suggests trying the 1.7.0 Intel driver available from http://
There are some reports that this fixes the x video crashes.
I haven't experienced the xv crashes but this driver does NOT fix the suspend/resume issues on my 945GM.
-David Carr
michelem (michele-marcucci) wrote : | #59 |
- Gdm crash syslog Edit (3.9 KiB, text/plain)
Could someone tell me please if this my log is related to this bug?
I often find my Dell D610 with the gdm restarted with the login screen, may be it happens when screensaver (but I try with blank screen too) starts.
However the "crash" is very very random, one night I left it turned on with lid closed it crashed the morning after but often it crashs in few minutes of "inactivity".
Thank you
Timothy Smith (tas50) wrote : | #60 |
Perhaps I'm totally off here, but it sounds like the 810 driver 1.7 has problems with resume. Just gets a black screen according to:
https:/
They commited a fix for that issue in 1.7.1. Perhaps someone can try that to see if resume is working all the way here.
Timothy Smith (tas50) wrote : | #61 |
Just to clarify my last comment. The issue exists for drivers from 1.6.1 to 1.7 according to the bug post at freedesktop.org and has been fixed in 1.7.1.
Khalid Baheyeldin (kbahey) wrote : Same problem on Toshiba Satellite with suspend or hibernate | #62 |
I am facing this exact same issue with Ubuntu 6.10 (Edgy).
This is a laptop, Toshiba Satellite A100-TA6, which has an Intel 945.
lspci says:
00:02.0 VGA compatible controller: Intel Corporation Mobile 945GM/GMS/940GML Express Integrated Graphics Controller (rev 03)
When I hibernate or suspend the computer, it comes back fine, except for the display and keyboard. By fine, I mean I can ssh to the laptop, and do command line things.
The screen goes from clock pointer to mouse pointer to nothing and keeps cycling into that loop. The keyboard does nothing, so I can't even go to a VT and do stuff.
I tried Alan Hourihane's driver (dated Nov 24, 2006), but it did not solve the problem.
One person above mentioned Toshiba as well.
Can anyone confirm whether they still have the issue with Edgy or was the problem solved?
Khalid Baheyeldin (kbahey) wrote : | #63 |
Here is a workaround that may work for some.
Since the problem is in the i810 driver, replacing that by another driver would avoid the problem. Some high end features of the hardware may not be available, but for general use, this works for me.
What you need to do is replace the i810 entry in the X.org configuration file with the vesa driver.
So, edit /etc/X11/xorg.conf and find the word i810. Replace that with vesa.
Before:
Driver "i810"
After:
Driver "vesa"
Reboot, and then you would be able to suspend/hibernate the computer.
James Stansell (jamesstansell) wrote : Re: [Bug 28326] Re: i810 Xv crashes after suspend -> infinite resprawn | #64 |
The work-around I've been using (unwittingly at first) is to allocate only 8
MB to the video card. That isn't enough to enable 3D operations, which
prevents this bug for me.
Mathias De Belder (mathias-de-belder) wrote : Re: [Bug 28326] Same problem on Toshiba Satellite with suspend or hibernate | #65 |
On 02/12/06, Khalid Baheyeldin wrote:
> I am facing this exact same issue with Ubuntu 6.10 (Edgy).
>
> This is a laptop, Toshiba Satellite A100-TA6, which has an Intel 945.
>
> lspci says:
>
> 00:02.0 VGA compatible controller: Intel Corporation Mobile
> 945GM/GMS/940GML Express Integrated Graphics Controller (rev 03)
>
> When I hibernate or suspend the computer, it comes back fine, except for
> the display and keyboard. By fine, I mean I can ssh to the laptop, and
> do command line things.
>
> The screen goes from clock pointer to mouse pointer to nothing and keeps
> cycling into that loop. The keyboard does nothing, so I can't even go to
> a VT and do stuff.
>
> I tried Alan Hourihane's driver (dated Nov 24, 2006), but it did not
> solve the problem.
>
> One person above mentioned Toshiba as well.
>
> Can anyone confirm whether they still have the issue with Edgy or was
> the problem solved?
The same problem manifests itself with Edgy too. I'm hoping that Xorg
7.2.1, to be shipped with Feisty, contains a fix.
Also, please note that your work-around of using the vesa instead of
the i810 driver might work with suspend, but will *drastically* reduce
performance. The vesa standard is implemented through the video card's
bios and offers no acceleration whatsoever (OpenGL, 2D, xvideo). I'd
rather have no suspend than 1995-era video card performance.
So, at the moment, it's a matter of waiting for new Xorg releases, or
trying different git branches posted on
http://
Khalid Baheyeldin (kbahey) wrote : | #66 |
It depends on what you do with the video.
For someone who uses the machine for development, browsing, email, IM, ...etc, this is acceptable.
Of course, if you want multimedia intensive applications, then you are stuck.
The latest driver from A Hourihane did not work for me. It is dated Nov 24, so that path is also a dead end.
Jeroen Vijfhuizen (jeroenvijfhuizen) wrote : | #67 |
I did not have this issue on resume, but I did have it on starting totem on a .ogg file. All kinds of weird colored lines on the screen but you can still see x trying to restart.
The driver on http://
Dell Inspiron 510m
Intel 855GME Integrated chip set
Running Ubuntu Edgy.
lcampagn (luke-campagnola) wrote : | #68 |
Confirming this bug on a thinkpad x60 tablet/intel 945 chipset, I get infinite respawn after resuming from suspend and the same error in my Xorg.0.log.old. Kubuntu edgy, kernel 2.6.17-11.
Florian Boucault (fboucault) wrote : | #69 |
A new release of the driver has been uploaded recently. It might fix it :)
Khalid Baheyeldin (kbahey) wrote : | #70 |
If you are referring to the i810_drv.so that is available on Alan Hourihan's site (link above), then this is still the old one, dated 2006-11-24 07:06.
I tested this one, and it did not solve the problem. Moreover, the bugzilla report above is now closed with Alan asking people to open a new report.
Or are you referring to some other place for upload? If so, then where?
Florian Boucault (fboucault) wrote : | #71 |
I am referring to this:
https:/
Changelog:
https:/
lcampagn (luke-campagnola) wrote : Re: [Bug 28326] Re: i810 Xv crashes after suspend -> infinite resprawn | #72 |
I just tried this driver, it did not help :(
On 3/4/07, Kaleo <email address hidden> wrote:
>
> I am referring to this:
>
> https:/
>
> Changelog:
>
> https:/
> video-i810/
>
> --
> i810 Xv crashes after suspend -> infinite resprawn
> https:/
>
Timo Aaltonen (tjaalton) wrote : | #73 |
Please try with Feisty Herd5, this _should_ be fixed in 1.7.4.
Changed in xserver-xorg-video-i810: | |
status: | Confirmed → Needs Info |
Khalid Baheyeldin (kbahey) wrote : | #74 |
The comment from Kaleo above says that he tested 1.7.4 and it is not yet fixed.
The upstream package did not fix this problem. See Alan Hourihane's comment here https:/
Timo Aaltonen (tjaalton) wrote : | #75 |
Still, try Feisty.. your problem is not necessarily in the driver, but maybe in mesa or in the kernel.
Khalid Baheyeldin (kbahey) wrote : | #76 |
Timo
Thanks for the info.
I assume that the Herd5 of Kubuntu would also have that, since I am not using Ubuntu.
I don't know if hibernate would from the live CD or does it need to be installed on the hard disk. Will check.
Khalid Baheyeldin (kbahey) wrote : | #77 |
I downloaded Kubuntu Feisty Herd5, and tested using the Live CD.
I can say it is promising.
Issuing the following commands on my Toshiba laptop:
# sudo bash
# /etc/acpi/sleep.sh
Causes the blue power LED to become flashing amber (meaning it did go to suspend). Pressing it makes it go back normally to a functioning desktop. No more hourglass/respawn problem.
On a whim, I tried with the Kubuntu Edgy CD as a live CD. Doing the same steps above causes the screen to blank, but the LED stays blue (i.e. power on), and nothing happens.
This means I cannot reproduce the problem with Edgy as a live CD, but there sure is hope with Feisty.
I will wait till Feisty is officially released before I plunge into an upgrade.
lcampagn (luke-campagnola) wrote : | #78 |
I have feisty installed on my X60 tablet, and the i810 crash appears to be
fixed after the latest update!
On 3/10/07, Khalid Baheyeldin wrote:
>
> I downloaded Kubuntu Feisty Herd5, and tested using the Live CD.
>
> I can say it is promising.
>
> Issuing the following commands on my Toshiba laptop:
>
> # sudo bash
> # /etc/acpi/sleep.sh
>
> Causes the blue power LED to become flashing amber (meaning it did go to
> suspend). Pressing it makes it go back normally to a functioning
> desktop. No more hourglass/respawn problem.
>
> On a whim, I tried with the Kubuntu Edgy CD as a live CD. Doing the same
> steps above causes the screen to blank, but the LED stays blue (i.e.
> power on), and nothing happens.
>
> This means I cannot reproduce the problem with Edgy as a live CD, but
> there sure is hope with Feisty.
>
> I will wait till Feisty is officially released before I plunge into an
> upgrade.
>
> --
> i810 Xv crashes after suspend -> infinite resprawn
> https:/
>
lcampagn (luke-campagnola) wrote : | #79 |
I take it back. After a few days of blissful suspend-resuming, the problem
has returned after the last upgrade. I don't actually know whether this is
related to the upgrade or to some other configuration change I made.. still
looking.
Luke
On 3/11/07, Luke Campagnola <email address hidden> wrote:
>
> I have feisty installed on my X60 tablet, and the i810 crash appears to be
> fixed after the latest update!
Id2ndR (id2ndr) wrote : | #80 |
I've got the trouble too. I thank before that it was linked to usplash (see bug https:/
The bug occurs when GDM normaly appears. The cursor "rounds" and then stops and after the sceens goes to standy mode 1 time. It goes up after a return to standy mode just after.
The bug doesn't occur each boot, and I've done a diff log that may help (when gdm went up and when it didn't).
ant2ne (tony-78280z) wrote : | #81 |
I've got a similar bug. I can go into suspend mode just fine. But if I try to restart or shut down in anyway other than "powerdown now" It hangs up with a dark screen. And doesn't shut down or restart.
Dell Inspiron E1505 running Kubuntu and Beryl
Paul Sladen (sladen) wrote : | #83 |
Believed to be fixed with Feisty.
Changed in xserver-xorg-video-i810: | |
status: | Needs Info → Fix Released |
Paul Sladen (sladen) wrote : | #84 |
ant2ne: Hi, your issue sounds like a new one; please could you open a new bug report specifically for your laptop (please put "Dell Inspiron E1505" somewhere in the subject).
Martin Rehn (minpost) wrote : still present in eisty | #85 |
This bug is still present in Feisty as per today (xserver-
I can go through several suspend/resume cycles with no problem sometimes, but then as soon as an application tries to paint video to the screen there is a crash. The crash does not occur until the video is actually painted to the screen; the video window can be sitting behind other windows on the desktop without causing a crash.
Description of a crash with feisty: when I bring the video window forward it is all blue rather than containing any video. Then the screen goes blank and starts to display a moving band of video artifacts towards the bottom of the screen. I can still move the cursor mouse, but the machine does not respond to e.g. ctrl-alt-f1, ctrl-alt-backspace, ctrl-alt-delete. There is disk activity. The machine does shut itself down gracefully when I press the power button.
I get the following in syslog, the last two messages repeating, indicating, I presume, that kdm repeatedly tries to restart the X server without success:
Apr 1 09:04:21 machine kdm[5191]: X server for display :0 terminated unexpectedly
Apr 1 09:04:22 machine gconfd (user-6570): Exiting
Apr 1 09:04:31 machine kdm_greet[27446]: Can't open default user face
Apr 1 09:04:37 machine kdm_greet[27446]: Internal error: memory corruption detected
Martin Rehn (minpost) wrote : Re: Still present in Feisty | #86 |
- syslog (see below for Xorg.0.log.old!) Edit (279 bytes, text/plain)
I attach what I believe is the relevant part of Xorg.0.log.old relating to my comment above.
By the way: What fix is referred to in the status of this bug: "Fix released"?
Martin Rehn (minpost) wrote : | #87 |
- Xorg.0.log.old Edit (873 bytes, text/plain)
Wrong file! Here is the real Xorg.0.log.old for this crash.
Krzysztof Lichota (krzysiek-launchpad-ubuntu-com) wrote : | #88 |
I think this bug might be caused by bug in Intel hardware. I have seen problems with hibernate (blue screens after resume and using some 3D app) on recent Dell laptop with Intel graphics running Windows with latest drivers (WHQL certified).
Martin Rehn (minpost) wrote : | #89 |
Not fixed in Feisty, unfortunately.
Changed in xserver-xorg-video-i810: | |
status: | Fix Released → Confirmed |
Id2ndR (id2ndr) wrote : | #90 |
- cat /var/log/gdm/\:0.log Edit (1.9 KiB, text/plain)
I can see lockup error on gdm log, not Xorg ones.
tomaszr (tomasz-rosinski) wrote : | #91 |
:( in IBM Thinkpad R50e too. It's a big problem. New Feisty Fawn afresh installed and everything it's good, but last night after reasume from suspend GDM crashes ... and blinking avery time. reboot not solved this problem and any others solutions.
i810 is very troublesome for me... please help me and help other people.
Id2ndR (id2ndr) wrote : | #92 |
I've no longer got this problem since I reinstall Ubuntu from Feisty liveCd release.
In freedesktop.org Bugzilla #10798, lcampagn (luke-campagnola) wrote : | #93 |
I am using the i810 driver on a Lenovo X60 tablet running kubuntu/feisty. lspci calls my video device an "Intel Corporation Mobile 945GM/PM/GMS/940GML and 945GT Express Memory Controller Hub (rev 03)". When I resume from suspend on my machine, about half of the time the X server will start, freeze, and restart in an infinite loop. The X log from this crash contains the following:
Error in I830WaitLpRing(), now is 353619, start is 351618
pgetbl_ctl: 0x3ffc0001 pgetbl_err: 0x0
ipeir: 0 iphdr: c000720
LP ring tail: 8 head: 18 len: 1f001 start 0
eir: 0 esr: 0 emr: ffff
instdone: ffc1 instpm: 0
memmode: 306 instps: f84cc
hwstam: ffff ier: a2 imr: ffff iir: 0
space: 8 wanted 80
DRIUnlock called when not locked
(II) I810(0): [drm] removed 1 reserved context for kernel
(II) I810(0): [drm] unmapping 8192 bytes of SAREA 0xf8fdf000 at 0xb7c25000
Fatal server error:
lockup
This bug appears to be related to several others: 5774 (which has been closed), 10258, 10472.. There are also a number of people reporting this bug on launchpad (https:/
Yannick (splitsch) wrote : | #94 |
Hi!
I'm using a thinkpad r50e with an uptodate Feisty.
On herd 4, suspend worked, but now, it doesn't naymore: Iwhen resuming, the screen goes block except text-box, and under firefox, the scrolling is broken.
Anyone has a workaroung ? (I've set vberestore : true in xorg.conf but it didn't work...)
Thanks
Khalid Baheyeldin (kbahey) wrote : | #95 |
As I mentioned previously, my laptop is a Toshiba Satellite A100-TA6, using the Intel 945GM chip.
Following my test using Kubuntu Feisty Herd5 (see <a href="https:/
However, after the upgrade, whenever I changed the xorg.conf file to use "i810" or "intel" (instead of "vesa"), the screen is messed up. The best way to explain the problem is to say that the font is way too big. Here is a <a href="http://
I also noted that the source tar.gz for the xserver-
"Common issues not caused by the driver
- Font sizes (DPI) are wrong. Some displays incorrectly report their
physical size, which is harmless on most OSes that always assume 96dpi
displays. This can be fixed through quirks for specific monitors in the X
Server, and the output of xrandr --prop along with a physical measurement of
the screen size in a bug report against the server can help get that fixed."
I tried setting DisplaySize 338 212 in xorg.conf Monitor section to fix the DPI, but that did not work either.
I noticed that Feisty has a new package name <a href="https:/
So, what I did was
a) Install xserver-
b) Uninstall 915resolution
c) Then in /etc/default/
POST_VIDEO=false
d) In /etc/X11/xorg.conf, I now have:
Section "Device"
Identifier "Intel i945"
Driver "i810"
Option "VBERestore" "True"
Option "Dri" "True"
BusID "PCI:0:2:0"
EndSection
The good news is after I did this, I am able to:
a) Cycle through the resolutions using Ctrl-Alt-+/-
b) Send the output to the external VGA port by the Fn key combo.
c) Resuming from hibernate works well too.
The only drawback is that I am not sure if this is a sustainable solution though, since the -i810 package is replaced by the -intel package which does not work, and will be the only package in Gutsy.
Jonathan Amir (jonathan-amir) wrote : | #96 |
I am using Kubuntu 7.04 as well, on a lenovo R60e. Last week I changed the console resolution, by adding vga=791 to the boot configuration in grub. Since then I have experienced the same behavior reported here - an infinite loop of Respawn, Watch pointer, Arrow pointer, Respawn. Removing the offending line from grub completely solved the problem for me.
Kernel: 2.6.20-15.27
pc: lenovo R60e
This is from lspci:
00:02.0 VGA compatible controller: Intel Corporation Mobile 945GM/GMS/940GML Express Integrated Graphics Controller (rev 03)
00:02.1 Display controller: Intel Corporation Mobile 945GM/GMS/940GML Express Integrated Graphics Controller (rev 03)
Driver: i810, dri enabled
Felipe Navarro V. (fnavarrov) wrote : | #97 |
I agree with <a href="https:/
Kernel: 2.6.20-15-generic
pc: Sony Vaio VGN-N21S/W
driver: intel, Legacy3D true
915resolution: uninstalled
This is from lspci:
00:02.0 VGA compatible controller: Intel Corporation Mobile 945GM/GMS/940GML Express Integrated Graphics Controller (rev 03)
00:02.1 Display controller: Intel Corporation Mobile 945GM/GMS/940GML Express Integrated Graphics Controller (rev 03)
Changed in xorg-server: | |
status: | Unknown → Confirmed |
Martin Rehn (minpost) wrote : | #98 |
The "vga=791" thing has no bearing on my case. I never had that option set up and this bug happens to me regularly. Dell D610 laptop here.
Dave Gilbert (ubuntu-treblig) wrote : | #99 |
Hi,
I've just had something that may be similar on Gutsy (Toshiba A100-306 Equium)
00:02.0 VGA compatible controller: Intel Corporation Mobile 945GM/GMS, 943/940GML Express Integrated Graphics Controller (rev 03)
00:02.1 Display controller: Intel Corporation Mobile 945GM/GMS/GME, 943/940GML Express Integrated Graphics Controller (rev 03)
I tried to watch the penguins at:
http://
using the totem plugin in mozilla and got a black box rather than the video, I hit the 'open in Movie Player' on the menu and X hung and eventually restarted X in a not too happy state (gnome settings daemon didn't start?); I had compiz on and the machine had previously done a hibernate (not a suspend to RAM); here is the bottom of the xorg.0.log I'm assuming all these errors came at the point it crashed?
Error in I830WaitLpRing(), timeout for 2 seconds
pgetbl_ctl: 0x3ffc0001 pgetbl_err: 0x0
ipeir: 0 iphdr: 1810000
LP ring tail: 16550 head: 16544 len: 1f801 start 0
eir: 0 esr: 0 emr: ffff
instdone: ffc0 instpm: 0
memmode: 306 instps: f0000
hwstam: fffe ier: a2 imr: 0 iir: 200
Ring at virtual 0xe5b0c000 head 0x16544 tail 0x16550 count 3
000164c4: 00000000
000164c8: 02000011
000164cc: 00000000
000164d0: 02000011
000164d4: 00000000
000164d8: 02000011
000164dc: 00000000
000164e0: 02000011
000164e4: 00000000
000164e8: 02000011
000164ec: 00000000
000164f0: 02000011
000164f4: 00000000
000164f8: 02000011
000164fc: 00000000
00016500: 02000011
00016504: 00000000
00016508: 02000011
0001650c: 00000000
00016510: 02000011
00016514: 00000000
00016518: 02000011
0001651c: 00000000
00016520: 02000011
00016524: 00000000
00016528: 02000011
0001652c: 00000000
00016530: 02000011
00016534: 00000000
00016538: 02000011
0001653c: 00000000
00016540: 01810000
00016544: 00000000
Ring end
space: 131052 wanted 131064
(II) intel(0): [drm] removed 1 reserved context for kernel
(II) intel(0): [drm] unmapping 8192 bytes of SAREA 0x2efff000 at 0x2ba9e5461000
Fatal server error:
lockup
(II) AIGLX: Suspending AIGLX clients for VT switch
Error in I830WaitLpRing(), timeout for 2 seconds
pgetbl_ctl: 0x3ffc0001 pgetbl_err: 0x0
ipeir: 0 iphdr: 1810000
LP ring tail: 16578 head: 16544 len: 1f801 start 0
eir: 0 esr: 0 emr: ffff
instdone: ffc0 instpm: 0
memmode: 306 instps: f0000
hwstam: fffe ier: a2 imr: 0 iir: 200
Ring at virtual 0xe5b0c000 head 0x16544 tail 0x16578 count 13
000164c4: 00000000
000164c8: 02000011
000164cc: 00000000
000164d0: 02000011
000164d4: 00000000
000164d8: 02000011
000164dc: 00000000
000164e0: 02000011
000164e4: 00000000
000164e8: 02000011
000164ec: 00000000
000164f0: 02000011
000164f4: 00000000
000164f8: 02000011
000164fc: 00000000
00016500: 02000011
00016504: 00000000
00016508: 02000011
0001650c: 00000000
In freedesktop.org Bugzilla #10798, Smajchl (smajchl) wrote : | #100 |
I have the same problem on HP nx6110 with the same graphics card. Debian testting.
I spent lot of time to get it worgking and now I am using old version 2:1.7.2-4 with vbetool, without 3d rendering. With 3d rendering it makes this problem and with newer version, it doesn't do anything, only black screen, even if 3d rendering is off :-(
Jesus (casiciaco) wrote : | #101 |
Hello,
I am having the same problem on my MacBook C2D 2Ghz. I am running ubuntu Gutsy ( 7.10 )
with the last kernel: 2.6.22-14-generic
When I resume from suspend, the screen gets black and the mouse freezes.
Then the screen turns off and on, the mouse responds for a few seconds and freezes again,
and so on.
The Xorg.0.log file:
-------
....
Synaptics Touchpad auto-dev sets device to /dev/input/event2
(**) Option "Device" "/dev/input/event2
(--) Synaptics Touchpad touchpad found
(II) Configured Mouse: ps2EnableDataRe
Error in I830WaitLpRing(), now is -950203834, start is -950205835
pgetbl_ctl: 0x7ffc0001 pgetbl_err: 0x0
ipeir: 0 iphdr: a303030
LP ring tail: e8 head: 0 len: 1f001 start 0
eir: 0 esr: 0 emr: ffff
instdone: ffc1 instpm: 0
memmode: 306 instps: 2014ca
hwstam: fffe ier: a2 imr: 0 iir: 10
space: 130832 wanted 131064
(II) I810(0): [drm] removed 1 reserved context for kernel
(II) I810(0): [drm] unmapping 8192 bytes of SAREA 0xf8ac1000 at 0xb79c9000
Fatal server error:
lockup
(II) AIGLX: Suspending AIGLX clients for VT switch
Error in I830WaitLpRing(), now is -950201826, start is -950203827
pgetbl_ctl: 0x7ffc0001 pgetbl_err: 0x0
ipeir: 0 iphdr: a303030
LP ring tail: f0 head: 0 len: 1f001 start 0
eir: 0 esr: 0 emr: ffff
instdone: ffc1 instpm: 0
memmode: 306 instps: 2014ca
hwstam: fffe ier: a2 imr: 0 iir: 10
space: 130824 wanted 131064
FatalError re-entered, aborting
lockup
-------
Any suggestion?
unggnu (unggnu) wrote : | #102 |
Could you please recheck it with Gutsy Final Live CD? In Gutsy i810 driver is deprecated and intel driver is used instead.
Changed in xserver-xorg-video-i810: | |
status: | Confirmed → Incomplete |
Khalid Baheyeldin (kbahey) wrote : | #103 |
I reported this above in comment 62 last year on a Toshiba A100-TA6.
I tried the Gutsy live CD. It allows suspend, but not hibernate.
When I tried suspend, the video was fine after and the desktop appeared again unharmed.
So, I can say that Gutsy fixed it with suspend. Unsure about hibernate, but it probably is the same.
I am tempted to upgrade to Gutsy and see what happens.
Khalid Baheyeldin (kbahey) wrote : | #104 |
The first sentence I posted above may be confusing.
I had the problem initially on Edgy. When I upgraded to Feisty, I installed an alternative driver, and it works fine. See comment 94.
Now with Gutsy, there seems to be solution, based on the live CD test in my comment above this one. I will confirm it when I upgrade to Gutsy soon.
unggnu (unggnu) wrote : | #105 |
I am closing this bug because it seems to be fixed. Feel free to open it again if the issue still happens with Gutsy Gibbon and the new Intel driver.
@Khalid Baheyeldin
Hibernate couldn't work with Live CD since everything is stored only in Memory.
Changed in xserver-xorg-video-i810: | |
status: | Incomplete → Fix Released |
Jesus (casiciaco) wrote : Re: [Bug 28326] Re: i810 Xv crashes after suspend -> infinite resprawn | #106 |
The intel driver also crashes. It seems to be a problem related to the last
kernel update.
Actually, in the following link it is recommended to downgrade to kernel
2.6.22-12-generic:
https:/
Now, suspend works properly.
In freedesktop.org Bugzilla #10798, Freedesktop-tmp (freedesktop-tmp) wrote : | #107 |
Created an attachment (id=12642)
Xorg-log after crash
Same problem here, tested with
- Intel Corporation Mobile 915GM/GMS/910GML Express Graphics Controller
- Gentoo system
- xorg-server-1.4-r2
- xf86-video-i810 2.1.0, 2.1.1, 2.1.99 and current git version
- kernel 2.6.22 and 2.6.23
- with framebuffer (vesa, uvesa) and without
Steps to reproduce:
1. Boot system (drm and i915 unloaded)
2. Start X (everything's ok)
3. Use xterm or switch back to VT
4. s2ram
5. Resume
X will crash as soon it is activated.
It does not matter if you exit X and unload drm and i915 before suspending! X will crash when you try to restart it after resume.
Other way to reproduce:
1. Start system (without X)
2. s2ram
3. resume
4. Start X -> everything is OK
5. Quit X
6. s2ram
7. resume
8. Start X -> Crash
So I don't think this might be a kernel problem.
Interesting line from the logfile:
> space: 130800 wanted 131064
This value varies from time to time, so it seems to be a memory allocation problem?
In freedesktop.org Bugzilla #10798, Freedesktop-tmp (freedesktop-tmp) wrote : | #108 |
Created an attachment (id=12643)
my current xorg.conf
In freedesktop.org Bugzilla #10798, Freedesktop-tmp (freedesktop-tmp) wrote : | #109 |
Created an attachment (id=12644)
current kernel config
In freedesktop.org Bugzilla #10798, Freedesktop-tmp (freedesktop-tmp) wrote : | #110 |
X doesn't crash when setting option "NoAccel" to true. But... no dri, no compiz and very slow window redraw (e.g. when moving windows). Just a temporary solution for me.
This bug might be related to bug #11720.
In freedesktop.org Bugzilla #10798, Jesse Barnes (jbarnes-virtuousgeek) wrote : | #111 |
Sounds like an intel driver bug.
In freedesktop.org Bugzilla #10798, Jesse Barnes (jbarnes-virtuousgeek) wrote : | #112 |
Upping severity as this causes a crash/hang.
In freedesktop.org Bugzilla #10798, Jesse Barnes (jbarnes-virtuousgeek) wrote : | #113 |
Have you tested with the latest git driver? We fixed several suspend/resume bugs (really Enter/LeaveVT bugs) for that release, hopefully yours was fixed as well.
Could also be related to 11432 or 13196.
It would be helpful if you could build the intel_reg_dumper tool and capture some register state from after the resume before the X crash along with a dump from before starting a working X session.
In freedesktop.org Bugzilla #10798, Jesse Barnes (jbarnes-virtuousgeek) wrote : | #114 |
*** Bug 11720 has been marked as a duplicate of this bug. ***
In freedesktop.org Bugzilla #10798, Freedesktop-tmp (freedesktop-tmp) wrote : | #115 |
Created an attachment (id=13040)
Log the crashed server with current git tree
I've just compiled and tested the current git version. The server still crashes (same procedure as described earlier or in bug #11720), but now it looks somewhat different. I'll doing additional tests tomorrow.
In freedesktop.org Bugzilla #10798, Freedesktop-tmp (freedesktop-tmp) wrote : | #116 |
Created an attachment (id=13068)
Backtrace when X crashed after resume and vt-switch
New backtrace with current git version of xf86-video-intel
1. Start system w/o X
2. Start X with gdb (ssh)
3. Switch to vt1 and suspend
4. Resume and switch back to vt7 -> crash
In freedesktop.org Bugzilla #10798, Freedesktop-tmp (freedesktop-tmp) wrote : | #117 |
Created an attachment (id=13069)
intel_reg_dump after startup but before X
In freedesktop.org Bugzilla #10798, Freedesktop-tmp (freedesktop-tmp) wrote : | #118 |
Created an attachment (id=13070)
intel_reg_dump after startup while X is running
In freedesktop.org Bugzilla #10798, Freedesktop-tmp (freedesktop-tmp) wrote : | #119 |
Created an attachment (id=13071)
intel_reg_dump after resume but before switching to vt7
In freedesktop.org Bugzilla #10798, Freedesktop-tmp (freedesktop-tmp) wrote : | #120 |
Created an attachment (id=13072)
intel_reg_dump after resume and switch to vt7 (this means, after crash)
In freedesktop.org Bugzilla #10798, Freedesktop-tmp (freedesktop-tmp) wrote : | #121 |
If you require additional info, let me suggest to give you temporary root-access to my system so you can trace this bug by yourself. Please contact me by mail.
Changed in xorg-server: | |
status: | Confirmed → Incomplete |
In freedesktop.org Bugzilla #10798, Freedesktop-tmp (freedesktop-tmp) wrote : | #122 |
Created an attachment (id=13115)
Xorg.log when crashing after resuming from disk (tuxonice)
I just did some tests with tuxonice instead of default suspend. When resuming from disk, the server keeps crashing when entering vt7. But it seems to be slightly different because I was not able to backtrace this crash with gdb. The screen shows garbage but the server still runs and receives SIGUSR1-events (however it does not handle them).
Maybe an interesting detail: When suspending to mem via sysfs (using hibernate-tools) after killing a running X-session, the screen is blank after resuming. If I'm not totally wrong even the backlight keeps disabled. But when starting X (using an ssh-connection) the backlight is enabled again and the server crashes the same way it did when suspending to disk.
None of this problems occurs when option NoAccel is true in xorg.conf.
Is someone working on this? I will help as best as I can, but this bug is really annoying.
In freedesktop.org Bugzilla #10798, Jesse Barnes (jbarnes-virtuousgeek) wrote : | #123 |
I wonder if this might be related to 13196... my latest theory there is that we're not letting the PLLs settle for a long enough period before writing the pipe registers... There's a patch there to test that theory, can you give it a try?
In freedesktop.org Bugzilla #10798, Freedesktop-tmp (freedesktop-tmp) wrote : | #124 |
Thanks to Jesse, I was able to find out more information about the problem. To make it short, resuming works fine with classic vesafb, although I'm not sure wether it had worked all the time. Actually, it seems that I experienced different problems, all related to the kernel:
The first one (which encouraged me to start experimenting with various versions and kernel settings), resuming from disk with vesafb-tng (kernel 2.6.22), was apparently fixed some times ago and works at least with current git drivers.
The second one, resuming from ram with vesafb-tng, still exists but is a kernel problem (the screen stays black and the system completely hangs on resume, independently of starting an X-session).
The third and current one (used for the backtraces) occurs with the new uvesafb and kernel 2.6.23, but I think it may be an uvesafb-bug so I'll report it there, too.
I stupidly never tested with classic vesafb or without fb-support because I thought the driver is disabled when omitting the video=-line from kernel options, but obviously I was wrong.
@Jesse: Thank you for your patience, and sorry for the missleading and imperfect description of the bug. At least I learned how to use git and how to get backtraces with gdb ;-). Please change status if you think that this bug doesn't belong to xorg any longer.
In freedesktop.org Bugzilla #10798, Freedesktop-tmp (freedesktop-tmp) wrote : | #125 |
Added the bug to gentoo database:
http://
In freedesktop.org Bugzilla #10798, Michael Fu (michael-fu-intel) wrote : | #126 |
(In reply to comment #19)
>
> @Jesse: Thank you for your patience, and sorry for the missleading and
> imperfect description of the bug. At least I learned how to use git and how to
> get backtraces with gdb ;-). Please change status if you think that this bug
> doesn't belong to xorg any longer.
>
Roland, did you have a chance to try the patch in bug# 13196 that Jesse mentioned?
In freedesktop.org Bugzilla #10798, Freedesktop-tmp (freedesktop-tmp) wrote : | #127 |
I tried already, it had no effect. At the moment I'm pretty sure that this is an uvesafb-issue because my system resumes perfectly since I'm using classic vesafb. Futhermore there is another user with the same problem at gentoo's bugzilla.
In freedesktop.org Bugzilla #10798, Benjamin-close (benjamin-close) wrote : | #128 |
Bugzilla Upgrade Mass Bug Change
NEEDSINFO state was removed in Bugzilla 3.x, reopening any bugs previously listed as NEEDSINFO.
- benjsc
fd.o Wrangler
Changed in xorg-server: | |
status: | Incomplete → Confirmed |
In freedesktop.org Bugzilla #10798, Michael Fu (michael-fu-intel) wrote : | #129 |
(In reply to comment #19)
>
> I stupidly never tested with classic vesafb or without fb-support because I
> thought the driver is disabled when omitting the video=-line from kernel
> options, but obviously I was wrong.
>
Roland, it sounds to me if you remove vesafb kernel driver, just using drm driver, the suspend/resume works fine then?
In freedesktop.org Bugzilla #10798, Priit Laes (plaes) wrote : | #130 |
(In reply to comment #24)
> (In reply to comment #19)
> >
> > I stupidly never tested with classic vesafb or without fb-support because I
> > thought the driver is disabled when omitting the video=-line from kernel
> > options, but obviously I was wrong.
> >
>
> Roland, it sounds to me if you remove vesafb kernel driver, just using drm
> driver, the suspend/resume works fine then?
>
Withouth uvesafb compiled in kernel, suspend-resume works fine for me.
In freedesktop.org Bugzilla #10798, Michael Fu (michael-fu-intel) wrote : | #131 |
(In reply to comment #25)
> (In reply to comment #24)
> > (In reply to comment #19)
> > >
> > > I stupidly never tested with classic vesafb or without fb-support because I
> > > thought the driver is disabled when omitting the video=-line from kernel
> > > options, but obviously I was wrong.
> > >
> >
> > Roland, it sounds to me if you remove vesafb kernel driver, just using drm
> > driver, the suspend/resume works fine then?
> >
>
> Withouth uvesafb compiled in kernel, suspend-resume works fine for me.
>
great. I'm closing this bug then..
Changed in xorg-server: | |
status: | Confirmed → Invalid |
Julien Olivier (julo) wrote : | #132 |
This bug is back in Lucid.
Changed in xserver-xorg-video-i810 (Ubuntu): | |
status: | Fix Released → Confirmed |
affects: | malone → null |
Changed in xorg-server: | |
importance: | Unknown → High |
status: | Invalid → Won't Fix |
Changed in xorg-server: | |
importance: | High → Unknown |
Changed in xorg-server: | |
importance: | Unknown → High |
Timo Aaltonen (tjaalton) wrote : | #133 |
don't reopen ancient bugs, file new ones instead.
Changed in xserver-xorg-video-i810 (Ubuntu): | |
assignee: | Paul Sladen (sladen) → nobody |
status: | Confirmed → Fix Released |
no longer affects: | null |
You're not alone...Same behaviour here!
OS: Linux (k)ubuntu Dapper
kernel: 2.6.15
pc: IBM Thinkpad X40
svga: Intel Corporation 82852/855GM Integrated Graphics Device
driver: i810
options: xv and dri enabled
I opened a bug at freedesktop bugzilla. /bugs.freedeskt op.org/ show_bug. cgi?id= 5774
https:/