How to debug crash; where to file bug?

Asked by Rusty Burchfield

I can somewhat consistently (4/5) cause a crash on a fresh hardy 64-bit install with fglrx, compiz normal and dual screens (via Option "DesktopSetup" "horizontal") with an x1950 Pro.

To reproduce:
1. Start a fresh graphical session with the above
2. Open firefox
3. Open a YouTube video
4. While that video is playing open a new tab
5. Start a second YouTube video in the new tab
6. Open a new firefox window
7. Move the new firefox window onto the second display
8. Open a YouTube video in the new window on the second screen
9. With all three videos playing, close the one on the primary display (it has two tabs)
10. When prompted select close tabs to confirm
11. Xorg crashes either completely (thus restarting gdm) or it takes the displays down (leaving the contents of the session running) and spins, usually unable to be killed even with "sudo pkill -9 Xorg"

What is the best way to get a stack trace or other debug output to indicate what is crashing so I can report a proper bug?

I have the following from my Xorg.0.log, but it is probably just a symptom.
Backtrace:
0: /usr/bin/X(xf86SigHandler+0x6a) [0x48402a]
1: /lib/libc.so.6 [0x7f1c2e95d100]
2: /usr/lib/xorg/modules//libxaa.so [0x7f1c2beccc9c]
3: /usr/lib/xorg/modules//libxaa.so [0x7f1c2becce96]
4: /usr/bin/X [0x527ea2]
5: /usr/bin/X [0x515c3f]
6: /usr/bin/X(Dispatch+0x2ef) [0x44eaaf]
7: /usr/bin/X(main+0x47d) [0x436b9d]
8: /lib/libc.so.6(__libc_start_main+0xf4) [0x7f1c2e9491c4]
9: /usr/bin/X(FontFileCompleteXLFD+0x279) [0x435ed9]

I also have the following from /var/log/syslog, but it still doesn't seem very useful.
Sep 6 12:38:42 gicodex2 kernel: [ 4494.637234] BUG: soft lockup - CPU#0 stuck for 11s! [Xorg:7018]
Sep 6 12:38:42 gicodex2 kernel: [ 4494.637240] CPU 0:
Sep 6 12:38:42 gicodex2 kernel: [ 4494.637242] Modules linked in: af_packet rfcomm l2cap bluetooth ppdev ipv6 powernow_k8 cpufreq_stats cpufreq_conservative cpufreq_powersave cpufreq_userspace cpufreq_ondemand freq_table video output sbs sbshc dock container battery iptable_filter ip_tables x_tables ac lp loop fglrx(P) snd_intel8x0 snd_ac97_codec ac97_bus snd_pcm_oss snd_mixer_oss snd_pcm snd_seq_dummy snd_seq_oss snd_seq_midi snd_rawmidi snd_seq_midi_event serio_raw snd_seq psmouse snd_timer snd_seq_device i2c_nforce2 button i2c_core shpchp pci_hotplug parport_pc parport snd k8temp soundcore snd_page_alloc evdev pcspkr ext3 jbd mbcache usbhid hid sg sr_mod cdrom sd_mod sata_nv ata_generic floppy pata_acpi pata_amd forcedeth libata scsi_mod ehci_hcd ohci_hcd usbcore dm_mirror dm_snapshot dm_mod thermal processor fan fbcon tileblit font bitblit softcursor fuse
Sep 6 12:38:42 gicodex2 kernel: [ 4494.637289] Pid: 7018, comm: Xorg Tainted: P 2.6.24-19-generic #1
Sep 6 12:38:42 gicodex2 kernel: [ 4494.637291] RIP: 0010:[dm_mod:_spin_lock+0x7/0x10] [dm_mod:_spin_lock+0x7/0x10] _spin_lock+0x7/0x10
Sep 6 12:38:42 gicodex2 kernel: [ 4494.637299] RSP: 0018:ffff810139851dd0 EFLAGS: 00000286
Sep 6 12:38:42 gicodex2 kernel: [ 4494.637300] RAX: 0000000000000000 RBX: ffff810139651e40 RCX: 0000000000000000
Sep 6 12:38:42 gicodex2 kernel: [ 4494.637302] RDX: 0000000000000400 RSI: 0000000000000000 RDI: ffffffff8846f064
Sep 6 12:38:42 gicodex2 kernel: [ 4494.637304] RBP: ffff810139651e40 R08: 0000000000000000 R09: ffff810139b15a80
Sep 6 12:38:42 gicodex2 kernel: [ 4494.637306] R10: 0000000000000000 R11: ffffffff80316a10 R12: 0000000000000007
Sep 6 12:38:42 gicodex2 kernel: [ 4494.637308] R13: 0000000000008002 R14: 0000000000000282 R15: ffff81013aacb000
Sep 6 12:38:42 gicodex2 kernel: [ 4494.637310] FS: 00007ff3b7c5e6e0(0000) GS:ffffffff805b9000(0000) knlGS:00000000f2b49b90
Sep 6 12:38:42 gicodex2 kernel: [ 4494.637312] CS: 0010 DS: 0000 ES: 0000 CR0: 000000008005003b
Sep 6 12:38:42 gicodex2 kernel: [ 4494.637313] CR2: 00007ff3b4946080 CR3: 00000001222ab000 CR4: 00000000000006e0
Sep 6 12:38:42 gicodex2 kernel: [ 4494.637315] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
Sep 6 12:38:42 gicodex2 kernel: [ 4494.637317] DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
Sep 6 12:38:42 gicodex2 kernel: [ 4494.637318]
Sep 6 12:38:42 gicodex2 kernel: [ 4494.637319] Call Trace:
Sep 6 12:38:42 gicodex2 kernel: [ 4494.637422] [fglrx:firegl_open+0x7b/0x1440] :fglrx:firegl_open+0x7b/0x1e0
Sep 6 12:38:42 gicodex2 kernel: [ 4494.637478] [fglrx:firegl_stub_open+0xcf/0x1e0] :fglrx:firegl_stub_open+0xcf/0x140
Sep 6 12:38:42 gicodex2 kernel: [ 4494.637486] [chrdev_open+0xc1/0x1d0] chrdev_open+0xc1/0x1d0
Sep 6 12:38:42 gicodex2 kernel: [ 4494.637493] [__dentry_open+0xdb/0x200] __dentry_open+0xdb/0x200
Sep 6 12:38:42 gicodex2 kernel: [ 4494.637500] [do_filp_open+0x3a/0x50] do_filp_open+0x3a/0x50
Sep 6 12:38:42 gicodex2 kernel: [ 4494.637505] [sys_chown+0x67/0xa0] sys_chown+0x67/0xa0
Sep 6 12:38:42 gicodex2 kernel: [ 4494.637512] [get_unused_fd_flags+0x77/0x120] get_unused_fd_flags+0x77/0x120
Sep 6 12:38:42 gicodex2 kernel: [ 4494.637519] [do_sys_open+0x5a/0xf0] do_sys_open+0x5a/0xf0
Sep 6 12:38:42 gicodex2 kernel: [ 4494.637525] [system_call+0x7e/0x83] system_call+0x7e/0x83

Any suggestions on how to debug this issue further?

Thank you,
Rusty Burchfield

Question information

Language:
English Edit question
Status:
Solved
For:
Ubuntu compiz Edit question
Assignee:
No assignee Edit question
Solved by:
Rusty Burchfield
Solved:
Last query:
Last reply:
Revision history for this message
Shane Fagan (shanepatrickfagan) said :
#1

The best way to upload a crash is to send a crash report made by the OS itself. This only happens when ubuntu detects the crash and stores the info in a .crash file. These are stored in /var/crash. If you are using 8.04 or 8.10 you are using the pre-release version of Xorg so this bug like many others dont genrally last long.

Hope that helps
Shane Fagan

Revision history for this message
Rusty Burchfield (gicodewarrior) said :
#2

Thanks for the information. Yes I am using 8.04 (Hardy) 64-bit. Given that I am using fglrx + compiz + dual-screens this bug may not be showing up for a lot of other people.

I took a look in /var/crash, but alas it is empty. :-/
$ ls -la /var/crash/
total 8
drwxr-xr-x 2 root root 4096 2008-04-04 14:34 .
drwxr-xr-x 15 root root 4096 2008-09-04 02:02 ..

This is a fresh install from a 8.04.1 iso so I bet that this is already turned on, but just in case, is there anything I should turn on to generate a crash report?

Any other thoughts on how I can file a proper bug for this issue?

Thank you,
Rusty Burchfield

Revision history for this message
Shane Fagan (shanepatrickfagan) said :
#3

I dont know the format that a crash report should be in. There is no way to generate a crash report with out the system making it.

Revision history for this message
Rusty Burchfield (gicodewarrior) said :
#4

I am not suggesting that it is possible to generate a crash report by hand.

Perhaps some advice on where to file the bug so that it can be triaged?

~Rusty

Revision history for this message
Shane Fagan (shanepatrickfagan) said :
#5

The best place to file a bug is in launchpad.

Revision history for this message
Rusty Burchfield (gicodewarrior) said :
#6

Ok, yea... I will just file it under a pile somewhere.

Revision history for this message
Rusty Burchfield (gicodewarrior) said :
#7

A link to https://wiki.ubuntu.com/DebuggingCompiz might have been useful...