karmic 2.6.31-2 gnome-session: Fatal IO error 11

Bug #396843 reported by jerrylamos
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Ubuntu
Fix Released
Undecided
Unassigned

Bug Description

i845 KMS with:
Linux version 2.6.31-2-generic (buildd@palmer) (gcc version 4.4.0 (Ubuntu 4.4.0-8ubuntu2) ) #16-Ubuntu SMP Mon Jul 6 20:38:51 UTC 2009
Firefox up, entering text, screen goes black. Can't even get a command line prompt from Ctrl-Alt-F1 or F2 or F3 or ...

Nothing visible in /var/crash. There are errors in .xsession-errors and Xorg.0.log, also a little in Syslog:

Jul 7 13:45:55 linux console-kit-daemon[2169]: WARNING: Unable to activate console: No such device or address
Jul 7 13:45:58 linux pulseaudio[3696]: bluetooth-util.c: Error from ListAdapters reply: org.freedesktop.DBus.Error.ServiceUnknown

Was not able to log in via ssh: connection refused.

Do not seem to have this problem with 2.6.31-1.

Anything I can try or any other logs that might be useful?

Jerry

Tags: karmic
Revision history for this message
jerrylamos (jerrylamos) wrote :
Revision history for this message
jerrylamos (jerrylamos) wrote :

Xorg showing a number of complaints

Revision history for this message
jerrylamos (jerrylamos) wrote :

lspci from i845 video graphics pc

Revision history for this message
jerrylamos (jerrylamos) wrote :

lspci from i845 video graphics pc

Revision history for this message
jerrylamos (jerrylamos) wrote :

Karmic died black screen three times this morning in the last hour, one each with 2.6.31-2 update as of 9 am EST 20090708, 2.6.31-1, 2.6.30-10. That's all from the same boot and all from the latest gnome gdm. Same pc as in original bug description. Common factor is the latest karmic gnome gdm.

Note I followed the update recommendations from "Next karmic gdm upgrade WILL BREAK your system". It does run for a while....then bang.

This entry is from intrepid, same pc, different boot. Attached are xsession-errors, Xorg.0.log, last part of syslog.

Jerry

Revision history for this message
jerrylamos (jerrylamos) wrote :

End of the syslog at last black screen crash

Jerry

Revision history for this message
jerrylamos (jerrylamos) wrote :

Note at the black screen, the pc is dead altogether.

Cannot get command line from Ctrl-Alt-F1 or 2 or ....

Cannot ssh in over the network "connection refused".

Attached is the Xorg.0.log.

Does Gnome keep any kind of an error log?

Jerry

Revision history for this message
jerrylamos (jerrylamos) wrote :

Been running all day without a black screen.

Removed:

splash

from /etc/default/grub then did sudo update-grub.

In this pc the "random black screen" must be very related to the "random logout" in other processors, see bug #396226 as written about in "Workaround for random crash bug on gdm 2.26" http://ubuntuforums.org/showthread.php?t=1206717

therefore this bug 396843 looks like a duplicate of 396226,

Jerry

Revision history for this message
Philip Muškovac (yofel) wrote :

 Thank you for taking the time to report this bug and helping to make Ubuntu better. You reported this bug a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue for you. Can you try with the final Ubuntu release? Thanks in advance.

Changed in ubuntu:
status: New → Incomplete
Revision history for this message
Philip Muškovac (yofel) wrote :

We'd like to figure out what's causing this bug for you, but we haven't heard back from you in a while. Could you please provide the requested information? Thanks!

tags: added: karmic
Revision history for this message
jerrylamos (jerrylamos) wrote :

Have not had this problem with Lucid Beta 2.6.32-17.

Thanks, Jerry

Revision history for this message
Philip Muškovac (yofel) wrote :

This has been fixed then, thanks for the feedback. Please report any other bugs you may find.

Changed in ubuntu:
status: Incomplete → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.