Imek
Guru
Joined: 20 Jan 2004
Posts: 390
Location: Newcastle, England
|
 Posted: Tue Mar 23, 2004 10:22 pm Post subject: New kernel.. Segfault while shutting down? |
 |
|
Ok, so I decided that my first try with mm-sources-2.6.5 and my PC not booting was just a one off. How wrong I was. I tried the previous version, the last 2.6.4, and everything seemed to work fine.. Until I shut down. Then I get a segfault, and it refuses to finish halting. Here's a bit from the end of dmesg:
| Code: | 0: NVRM: AGPGART: unable to retrieve symbol table
atkbd.c: Unknown key released (translated set 2, code 0x7a on isa0060/serio0).
atkbd.c: This is an XFree86 bug. It shouldn't access hardware directly.
atkbd.c: Unknown key released (translated set 2, code 0x7a on isa0060/serio0).
atkbd.c: This is an XFree86 bug. It shouldn't access hardware directly.
Debug: sleeping function called from invalid context at include/linux/rwsem.h:43
in_atomic():0, irqs_disabled():1
Call Trace:
[<c0118dae>] do_page_fault+0x0/0x53a
[<c011e7a1>] __might_sleep+0xab/0xc9
[<c0119023>] do_page_fault+0x275/0x53a
[<c014e3bd>] unmap_vma+0x40/0x7d
[<c014e416>] unmap_vma_list+0x1c/0x28
[<c014e8ff>] do_munmap+0x15e/0x1a8
[<c010ceaa>] do_gettimeofday+0x1e/0xba
[<c0124e0d>] sys_gettimeofday+0x67/0xd0
[<c0118dae>] do_page_fault+0x0/0x53a
[<c033551b>] error_code+0x2f/0x38
------------[ cut here ]------------
kernel BUG at fs/proc/generic.c:664!
invalid operand: 0000 [#1]
PREEMPT SMP
CPU: 0
EIP: 0060:[<c018db48>] Tainted: PF VLI
EFLAGS: 00010286
EIP is at remove_proc_entry+0xe4/0x124
eax: de7d5d00 ebx: de989830 ecx: 00000000 edx: ded3db80
esi: 00000005 edi: def4e100 ebp: dea72000 esp: dea73e60
ds: 007b es: 007b ss: 0068
Process rmmod (pid: 5949, threadinfo=dea72000 task=dee28c80)
Stack: def4e100 def4e148 def4e100 0000000c def4e148 e094bcf0 def4e180 de989800
e0942de1 def4e148 de989800 de9b2c00 de9b2c00 e09b7be4 e0942924 def4e180
de989800 dea72000 e0940f75 de9b2c00 00000002 c01751c8 dffe0a34 decad080
Call Trace:
[<e0942de1>] snd_info_unregister+0x54/0x85 [snd]
[<e0942924>] snd_info_card_free+0x31/0x5a [snd]
[<e0940f75>] snd_card_free+0x130/0x2da [snd]
[<c01751c8>] destroy_inode+0x4e/0x50
[<c0172c49>] dput+0x22/0x2b1
[<e09b429a>] snd_intel8x0_remove+0x20/0x2f [snd_intel8x0]
[<c0204588>] pci_device_remove+0x3b/0x3d
[<c02504fe>] device_release_driver+0x64/0x66
[<c0250520>] driver_detach+0x20/0x2e
[<c02507ba>] bus_remove_driver+0x5c/0x99
[<c0250b6f>] driver_unregister+0x1a/0x48
[<c01381f2>] try_stop_module+0x37/0x3b
[<c0204739>] pci_unregister_driver+0x16/0x26
[<e09b447f>] alsa_card_intel8x0_exit+0xf/0x2b [snd_intel8x0]
[<c01383db>] sys_delete_module+0x14a/0x197
[<c014e9a2>] sys_munmap+0x59/0x7a
[<c0334a8f>] syscall_call+0x7/0xb
Code: 01 00 00 00 89 44 24 0c 8b 47 04 89 44 24 08 8b 44 24 28 8b 40 04 c7 04 24 00 d8 34 c0 89 44 24 04 e8 8e 3e f9 ff e9 76 ff ff ff <0f> 0b 98 02 fb ad 34 c0 eb b4 8b 44 24 28 66 83 68 0a 01 eb 84
<6>drivers/usb/core/usb.c: deregistering driver snd-usb-audio
|
Is this one of those things I should report? What exactly is causing it, and is there some way around it?
Thanks,
- I
_________________
- I
(very old) "Current" desktop | Adopt an unanswered post today! |
|
Kernel & Hardware
