Xorg crashes unexpectedly (amd64, gutsy, compiz)
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux (Ubuntu) |
Fix Released
|
Medium
|
Unassigned | ||
linux-source-2.6.22 (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
Using the Ubuntu Gutsy amd64 version (on a single core Athlon64 3000+), an ati radeon 9200 (128MB) (using the opensource driver) and an Asus k8v-x motherboard during last days I've experienced more than one crash: the Xserver freezes and in seconds restarts, bringing me back to GDM screen.
Syslog reports this issue:
[ 1323.558390] Unable to handle kernel paging request at ffffffffffffffff RIP:
[ 1323.558397] [<fffffffffffff
[ 1323.558404] PGD 203067 PUD 100c067 PMD 0
[ 1323.558408] Oops: 0010 [1] SMP
[ 1323.558411] CPU 0
[ 1323.558413] Modules linked in: snd_rtctimer tun binfmt_misc radeon drm rfcomm l2cap bluetooth af_packet xt_tcpudp xt_length ipt_ttl xt_tcpmss xt_TCPMSS iptable_mangle iptable_filter xt_multiport xt_limit ipt_tos ipt_REJECT ip_tables x_tables vboxdrv ppdev powernow_k8 cpufreq_stats cpufreq_powersave cpufreq_ondemand freq_table cpufreq_userspace cpufreq_
[ 1323.558453] Pid: 5293, comm: Xorg Not tainted 2.6.22-14-generic #1
[ 1323.558456] RIP: 0010:[<
[ 1323.558460] RSP: 0018:ffff810044
[ 1323.558464] RAX: ffffffff88581da0 RBX: ffff810045ff2d00 RCX: ffffffffffffffff
[ 1323.558468] RDX: 00007fff7794c200 RSI: 00000000c0406429 RDI: ffff810045ff2d00
[ 1323.558471] RBP: 00007fff7794c200 R08: 0000000003b15e20 R09: 00000000ec2aa000
[ 1323.558475] R10: ffece8e4ffeeeae7 R11: 0000000000003246 R12: 00007fff7794c200
[ 1323.558478] R13: 00000000c0406429 R14: 00000000c0406429 R15: 0000000001174f10
[ 1323.558482] FS: 00002b0234877e2
[ 1323.558484] CS: 0010 DS: 0000 ES: 0000 CR0: 000000008005003b
[ 1323.558488] CR2: ffffffffffffffff CR3: 0000000044458000 CR4: 00000000000006e0
[ 1323.558491] Process Xorg (pid: 5293, threadinfo ffff810044516000, task ffff8100444ef4a0)
[ 1323.558493] Stack: ffffffff802a6e05 000000000413c984 ffff810045ff2d00 00007fff7794c200
[ 1323.558499] 0000000000000008 0000000000000008 ffffffff802a6f24 0000000000a72730
[ 1323.558504] ffff8100010141e8 0000000000000000 ffff810045ff2d00 00007fff7794c200
[ 1323.558507] Call Trace:
[ 1323.558513] [<ffffffff802a6
[ 1323.558520] [<ffffffff802a6
[ 1323.558528] [<ffffffff802a7
[ 1323.558536] [<ffffffff80209
[ 1323.558547]
[ 1323.558548]
[ 1323.558549] Code: Bad RIP value.
[ 1323.558552] RIP [<fffffffffffff
[ 1323.558555] RSP <ffff810044517ed0>
[ 1323.558558] CR2: ffffffffffffffff
[ 1325.690437] agpgart: Found an AGP 3.5 compliant device at 0000:00:00.0.
[ 1325.690518] agpgart: Putting AGP V3 device at 0000:00:00.0 into 8x mode
[ 1325.690616] agpgart: Putting AGP V3 device at 0000:01:00.0 into 8x mode
[ 1325.883588] [drm] Setting GART location based on new memory map
[ 1325.883595] [drm] Loading R200 Microcode
[ 1325.883630] [drm] writeback test succeeded in 1 usecs
Thank you for taking the time to report this bug and helping to make Ubuntu better. This bug did not have a package associated with it, which is important for ensuring that it gets looked at by the proper developers. You can learn more about finding the right package at https:/ /wiki.ubuntu. com/Bugs/ FindRightPackag e . I have classified this bug as a bug in linux-source- 2.6.22.