| View previous topic :: View next topic |
| Author |
Message |
Drasica
Tux's lil' helper
Joined: 16 Apr 2006
Posts: 137
|
 Posted: Fri Apr 13, 2012 9:30 pm Post subject: Machine has been kernel panicking during daily use |
 |
|
It happened twice within an hour today. The most recent occasion other than that is probably 1 month ago
I have: Linux version 2.6.39-gentoo-r3 (gcc version 4.4.5 (Gentoo 4.4.5 p1.2, pie-0.4.5)
Here's a snippet from /var/log/messages describing a panic. Any help in interpreting this is greatly appreciated.
| Code: |
Apr 13 15:37:13 localhost kernel: [ 120.000296] Hardware name: System Product Name
Apr 13 15:37:13 localhost kernel: [ 120.000297] Modules linked in: snd_aloop fuse fglrx(P) radeon ttm drm_kms_helper drm agpgart i2c_algo_bit cfbcopyarea cfbimgblt cfbfillrect firewire_ohci firewire_core
Apr 13 15:37:13 localhost kernel: [ 120.000306] Pid: 2919, comm: X Tainted: P 2.6.39-gentoo-r3 #2
Apr 13 15:37:13 localhost kernel: [ 120.000308] Call Trace:
Apr 13 15:37:13 localhost kernel: [ 120.000312] [<ffffffff8104403b>] ?warn_slowpath_common+0x7b/0xc0
Apr 13 15:37:13 localhost kernel: [ 120.000315] [<ffffffff81258491>] ?pci_enable_msi_block+0x2a1/0x2b0
Apr 13 15:37:13 localhost kernel: [ 120.000346] [<ffffffffa01ca9bf>] ?irqmgr_wrap_assert_interrupt+0x37f/0x8c0 [fglrx]
Apr 13 15:37:13 localhost kernel: [ 120.000366] [<ffffffffa01ca717>] ?irqmgr_wrap_assert_interrupt+0xd7/0x8c0 [fglrx]
Apr 13 15:37:13 localhost kernel: [ 120.000385] [<ffffffffa01c9b52>] ?irqmgr_wrap_initialize+0x22/0xb0 [fglrx]
Apr 13 15:37:13 localhost kernel: [ 120.000403] [<ffffffffa01c9474>] ? firegl_interrupt_control+0x174/0x1a0 [fglrx]
Apr 13 15:37:13 localhost kernel: [ 120.000406] [<ffffffff8104e159>] ?ns_capable+0x29/0x60
Apr 13 15:37:13 localhost kernel: [ 120.000424] [<ffffffffa01c9300>] ?firegl_enable_hifreq_interrupt+0x100/0x100 [fglrx]
Apr 13 15:37:13 localhost kernel: [ 120.000442] [<ffffffffa01bb218>] ?firegl_ioctl+0x1e8/0xf20 [fglrx]
Apr 13 15:37:13 localhost kernel: [ 120.000459] [<ffffffffa01b0b99>] ?ip_firegl_unlocked_ioctl+0x9/0x10 [fglrx]
Apr 13 15:37:13 localhost kernel: [ 120.000462] [<ffffffff810e2a6b>] ?do_vfs_ioctl+0x9b/0x4f0
Apr 13 15:37:13 localhost kernel: [ 120.000464] [<ffffffff810d2939>] ?vfs_write+0x129/0x170
Apr 13 15:37:13 localhost kernel: [ 120.000466] [<ffffffff810e2f09>] ?sys_ioctl+0x49/0x80
Apr 13 15:37:13 localhost kernel: [ 120.000469] [<ffffffff814e113b>] ?system_call_fastpath+0x16/0x1b
Apr 13 15:37:13 localhost kernel: [ 120.000470] ---[ end trace bcd08c1a4c2b7a4a ]---
|
|
|
| Back to top |
|
 |
Hu
Watchman
Joined: 06 Mar 2007
Posts: 7607
|
| Posted: Fri Apr 13, 2012 10:24 pm Post subject: |
|
|
| That is not a panic. A panic leaves the system unable to log anything to local storage. Can you reproduce the problem with a modern untainted kernel? |
|
| Back to top |
|
|
Aquous
l33t
Joined: 08 Jan 2011
Posts: 619
|
| Posted: Sun Apr 15, 2012 1:01 pm Post subject: |
|
|
The problem is happening inside the fglrx driver; there's nothing we can do to help 
edit: but how the hell did you manage to load both fglrx AND radeon? that's very wrong. |
|
| Back to top |
|
|
Drasica
Tux's lil' helper
Joined: 16 Apr 2006
Posts: 137
|
| Posted: Wed Apr 18, 2012 7:39 am Post subject: |
|
|
| Hu wrote: | | That is not a panic. A panic leaves the system unable to log anything to local storage. Can you reproduce the problem with a modern untainted kernel? |
Oh, I was unaware. What is this event called then?
As far as reproducing this with an untainted kernel... well, the problem is extremely intermittent right now (the last time it happened before a couple days ago was 1-2months ago), so it could take months for me to be able to tell for sure if the problem goes away.
It seems likely, as Aquous said, that its in fglrx, the proprietary video driver. I suppose I could switch to the opensource driver at some point. As to why fglrx and radeon are loading together.... I'm not sure. I can't remove either one with modprobe. |
|
| Back to top |
|
|
DaggyStyle
Advocate
Joined: 22 Mar 2006
Posts: 4735
|
| Posted: Wed Apr 18, 2012 9:40 am Post subject: |
|
|
| Quote: | | fglrx(P) radeon ttm drm_kms_helper drm |
that is a big no no.
you cannot use the closed driver and open driver in the same time, you need to decide which one you use.
_________________
Only two things are infinite, the universe and human stupidity and I'm not sure about the former - Albert Einstein
ProjectFootball |
|
| Back to top |
|
|
|
Kernel & Hardware
