I have similar symptoms with my Kubuntu 7.04. Didn't have these problems
at all with Edgy. Today I've already had two crashes. I haven't found a
way to reproduce it, but I do have firefox open and last time it crashed
when I was just typing some text in firefox. Before the last time it has
crashed few times when I've switched between virtual desktops.

What always happens is that CPU level goes to 100% before the crash
(I've gkrellm running) and then I end up with a black screen with a
blinking cursor. Last time I was able to login with ssh from another
machine and start KDM remotely, but I've had crashes that kills sshd
too. My daemon.log said last time:

----8<----
Jun 12 16:33:57 localhost kdm[5204]: X server for display :0 terminated 
unexpectedly
Jun 12 16:34:00 localhost kdm[5204]: Unknown session exit code 0 (sig 11) from 
manager process
Jun 12 16:34:04 localhost udevd-event[12190]: wait_for_sysfs: waiting for 
'/sys/class/vc/vcs7/·' failed
Jun 12 16:34:04 localhost udevd-event[12191]: wait_for_sysfs: waiting for 
'/sys/class/vc/vcsa7/·' failed
Jun 12 16:36:00 localhost udevd-event[12307]: wait_for_sysfs: waiting for 
'/sys/class/vc/vcs7/·' failed
Jun 12 16:36:00 localhost udevd-event[12308]: wait_for_sysfs: waiting for 
'/sys/class/vc/vcsa7/·' failed
----8<----

I've also had the same NetworkManager messages there, but I removed it
earlier when I thought it was the reason for my crashes. Here's some
logs from an earlier crash:

----8<----
Jun  7 18:42:33 localhost hcid[5377]: Got disconnected from the system message 
bus
Jun  7 18:42:33 localhost NetworkManager: <WARNING>^I nm_hal_deinit (): libhal 
shutdown failed - Connection is closed
Jun  7 18:42:33 localhost avahi-daemon[5031]: Disconnnected from D-Bus, exiting.
Jun  7 18:42:33 localhost avahi-daemon[5031]: Got SIGQUIT, quitting.
Jun  7 18:42:33 localhost NetworkManager: <WARNING>^I nm_dbus_init (): 
nm_dbus_init() could not get the system bus.  Make sure the message bus daemon 
is running!
Jun  7 18:42:33 localhost avahi-daemon[5031]: Leaving mDNS multicast group on 
interface eth0.IPv4 with address 192.168.1.2.
Jun  7 18:42:33 localhost NetworkManager: <WARNING>^I nm_dbus_init (): 
nm_dbus_init() could not get the system bus.  Make sure the message bus daemon 
is running!
Jun  7 18:42:36 localhost NetworkManager: <WARNING>^I nm_dbus_init (): 
nm_dbus_init() could not get the system bus.  Make sure the message bus daemon 
is running!
Jun  7 18:42:37 localhost kdm[5334]: X server for display :0 terminated 
unexpectedly
Jun  7 18:42:39 localhost NetworkManager: <WARNING>^I nm_dbus_init (): 
nm_dbus_init() could not get the system bus.  Make sure the message bus daemon 
is running!
Jun  7 18:42:42 localhost NetworkManager: <WARNING>^I nm_dbus_init (): 
nm_dbus_init() could not get the system bus.  Make sure the message bus daemon 
is running!
Jun  7 18:42:44 localhost kdm[5334]: Unknown session exit code 0 (sig 11) from 
manager process
Jun  7 18:42:45 localhost NetworkManager: <WARNING>^I nm_dbus_init (): 
nm_dbus_init() could not get the system bus.  Make sure the message bus daemon 
is running!
Jun  7 18:43:15 localhost last message repeated 10 times
Jun  7 18:44:15 localhost last message repeated 20 times
Jun  7 18:45:15 localhost last message repeated 20 times
Jun  7 18:46:15 localhost last message repeated 20 times
Jun  7 18:47:15 localhost last message repeated 20 times
Jun  7 18:48:15 localhost last message repeated 20 times
Jun  7 18:49:15 localhost last message repeated 20 times
Jun  7 18:50:15 localhost last message repeated 20 times
Jun  7 18:51:15 localhost last message repeated 20 times
Jun  7 18:52:16 localhost last message repeated 20 times
Jun  7 18:53:16 localhost last message repeated 20 times
Jun  7 18:54:16 localhost last message repeated 20 times
Jun  7 18:55:16 localhost last message repeated 20 times
Jun  7 18:56:16 localhost last message repeated 20 times
Jun  7 18:56:46 localhost last message repeated 10 times
Jun  7 18:56:46 localhost init: tty4 main process (4406) killed by TERM signal
Jun  7 18:56:46 localhost init: tty5 main process (4407) killed by TERM signal
Jun  7 18:56:46 localhost init: tty2 main process (4411) killed by TERM signal
Jun  7 18:56:47 localhost init: tty3 main process (4412) killed by TERM signal
Jun  7 18:56:47 localhost init: tty1 main process (4413) killed by TERM signal
Jun  7 18:56:47 localhost init: tty6 main process (4414) killed by TERM signal
Jun  7 18:56:49 localhost NetworkManager: <WARNING>^I nm_dbus_init (): 
nm_dbus_init() could not get the system bus.  Make sure the message bus daemon 
is running!
----8<----

(I removed the bluetooth stuff after that too, but it wasn't the reason
for my crashes either.)

I use also KArm, which is using 100% CPU time for many seconds when
changing tasks now in Feisty, but I guess that hasn't anything to do
with this issue. One other thing that uses all CPU resources is the
logout fade, but these are probably just KDE issues.

These crashes are bad, and since this bug was the closest I could find
there must be some configuration or driver issue. My X configuration
differs from many others since I have two monitors using xinerama, which
might have something to do here. (No 3D accelaration of any kind because
of that...) My graphics card is:

----8<----
01:00.0 VGA compatible controller: ATI Technologies Inc Radeon RV200 QW [Radeon 
7500] (prog-if 00 [VGA])
        Subsystem: C.P. Technology Co. Ltd RV200 QW [Radeon 7500 Evil Master 
Multi Display Edition]
        Flags: bus master, stepping, 66MHz, medium devsel, latency 32, IRQ 16
        Memory at d0000000 (32-bit, prefetchable) [size=128M]
        I/O ports at c800 [size=256]
        Memory at dfef0000 (32-bit, non-prefetchable) [size=64K]
        Expansion ROM at dfec0000 [disabled] [size=128K]
        Capabilities: [58] AGP version 2.0
        Capabilities: [50] Power Management version 2
----8<----

I of course have all the latest updates. Kernel "2.6.20-16-386 #2 Thu
Jun 7 20:16:13 UTC 2007 i686 GNU/Linux", KDM - 3.5.6-0ubuntu20.1,
xserver-xorg - 7.2-0ubuntu11, xserver-xorg-core - 1.2.0-3ubuntu8 and so
on.

Does anyone how ideas how to find out what's causing these crashes and
how to fix it?

-- 
XServer crash while using firefox (Ubuntu 7.04)
https://bugs.launchpad.net/bugs/108829
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to