[ILUG] [Ubuntu Hoary] box getting kernel OOPS
Paul Jakma
paul at clubi.ie
Thu Sep 1 13:29:22 IST 2005
On Thu, 1 Sep 2005, Niall O Broin wrote:
> Your wish is my command - and sadly, this comes from the box currently
> running knoppix, so it's not just an Ubuntu issue.
What are the kernels involved? The below is 2.4 isn't it?
(page_remove_rmap). The hoary kernel is 2.6 though, right?
> ------------[ cut here ]------------
> kernel BUG at mm/rmap.c:482!
> invalid operand: 0000 [#1]
> PREEMPT SMP
> Modules linked in: jfs efs autofs4 af_packet ntfs cmpci opl3 mpu401 sound
> soundcore gameport 3c59x mii via_agp agpgart via_ircc irda
> crc_ccitt parport_pc parport 8250 serial_core usbhid pcmcia yenta_socket
> rsrc_nonstatic pcmcia_core video thermal processor fan con
> tainer button battery ac genrtc unionfs cloop sbp2 ohci1394 ieee1394
> usb_storage ub ohci_hcd uhci_hcd ehci_hcd usbcore
> CPU: 0
> EIP: 0060:[<c014a501>] Not tainted VLI
> EFLAGS: 00010286 (2.6.11)
> EIP is at page_remove_rmap+0x29/0x40
> eax: ffffffff ebx: 00003000 ecx: c100e6a0 edx: c100e6a0
> esi: ce933284 edi: c100e6a0 ebp: 00008000 esp: ddc3de58
> ds: 007b es: 007b ss: 0068
> Process convert (pid: 4109, threadinfo=ddc3c000 task=debba550)
> Stack: c0144534 c100e6a0 00735067 b0c9e000 debf4b08 b08a6000 00000000
> c01446e1
> c1405400 debf4b08 b089e000 00008000 00000000 b089e000 debf4b08
> b08a6000
> 00000000 c0144725 c1405400 debf4b08 b089e000 00008000 00000000
> b08a6000
> Call Trace:
> [<c0144534>] zap_pte_range+0x13c/0x2ac
> [<c01446e1>] zap_pmd_range+0x3d/0x5c
> [<c0144725>] zap_pud_range+0x25/0x44
> [<c014479e>] unmap_page_range+0x5a/0x78
> [<c01448c7>] unmap_vmas+0x10b/0x28c
> [<c0148426>] unmap_region+0x7a/0xf0
> [<c01486c6>] do_munmap+0xde/0x118
> [<c0148726>] sys_munmap+0x26/0x38
> [<c010342b>] syscall_call+0x7/0xb
> Code: eb c2 8b 54 24 04 8b 02 f6 c4 08 75 28 f0 83 42 08 ff 0f 98 c0 84 c0 74
> 11 8b 42 08 40 78 0c 6a ff 6a 10 e8 36 22 ff ff 59 58
> c3 <0f> 0b e2 01 b8 46 2e c0 eb ea 0f 0b df 01 b8 46 2e c0 eb ce 8d
> <6>note: convert[4109] exited with preempt_count 1
> scheduling while atomic: convert/0x00000001/4109
> [<c02cc5bc>] schedule+0x608/0x610
> [<c011b1ad>] call_console_drivers+0x5d/0x104
> [<c02cd0fd>] __down_read+0x65/0x8c
> [<c011ca16>] exit_mm+0x26/0xec
> [<c011d31b>] do_exit+0x9b/0x338
> [<c010456a>] die+0x16a/0x16c
everything above is i think related to logging the panic
> [<c01047dc>] do_invalid_op+0x0/0x88
> [<c0104856>] do_invalid_op+0x7a/0x88
> [<c014a501>] page_remove_rmap+0x29/0x40
> [<c0123315>] update_wall_time+0xd/0x38
> [<c01236a2>] do_timer+0xce/0xd4
> [<c010786d>] timer_interrupt+0x35/0x124
> [<c0107901>] timer_interrupt+0xc9/0x124
> [<c0136f6b>] handle_IRQ_event+0x23/0x58
> [<c01370bc>] __do_IRQ+0x11c/0x124
> [<c01370a5>] __do_IRQ+0x105/0x124
hmm, irq came in. Presumably because of error_code? Some funky x86
fault handling?
> [<c0103ecf>] error_code+0x2b/0x30
> [<c014a501>] page_remove_rmap+0x29/0x40
> [<c0144534>] zap_pte_range+0x13c/0x2ac
> [<c01446e1>] zap_pmd_range+0x3d/0x5c
> [<c0144725>] zap_pud_range+0x25/0x44
> [<c014479e>] unmap_page_range+0x5a/0x78
> [<c01448c7>] unmap_vmas+0x10b/0x28c
> [<c0148426>] unmap_region+0x7a/0xf0
> [<c01486c6>] do_munmap+0xde/0x118
> [<c0148726>] sys_munmap+0x26/0x38
> [<c010342b>] syscall_call+0x7/0xb
this is exact same as the trace after the interrupt, i'm guessing to
do with interrupt having come in. But something called munmap(), as
it was doing that, interrupt came in and things went pear-shaped.
Alternatively, page_remove_rmap() triggered a fault. I can't find the
"error_code" function, and its a word used a lot for other things. :(
Likely some x86 fault voodoo.
> See above :-) Whenever it has oopsed there has been FS related
> activity happening, on JFS filesystems.
The above isn't your 'do_lookup' problem though, which you had
reliably. The above is the VM blowing up. Tried running memtest86? :)
Also, was the above the /first/ oops?
regards,
--
Paul Jakma paul at clubi.ie paul at jakma.org Key ID: 64A2FF6A
Fortune:
The proof of the pudding is in the eating.
-- Miguel de Cervantes
More information about the ILUG
mailing list