oops?

[Thomas Cameron]

----- Original Message ----- 
From: "Rob" <wasguru at gmail.com>
To: "For users of Fedora Core releases" <fedora-list at redhat.com>
Sent: Monday, January 03, 2005 4:08 PM
Subject: Re: oops?


> Jan  3 04:06:42 everest kernel: Unable to handle kernel paging request
> at 00001118003e0000 RIP:
> Jan  3 04:06:42 everest kernel: <ffffffff801246a0>{do_page_fault+1341}
> Jan  3 04:06:42 everest kernel: PML4 0
> Jan  3 04:06:42 everest kernel: Oops: 0000 [1]
> Jan  3 04:06:42 everest kernel: CPU 0
> Jan  3 04:06:42 everest kernel: Modules linked in: vfat fat md5 ipv6
> parport_pc lp parport autofs4 i2c_dev i2c_core smbfs sunrpc ds
> yenta_socket pcmcia_core
> joydev button battery ac usb_storage ohci1394 ieee1394 uhci_hcd
> ehci_hcd snd_via82xx snd_ac97_codec snd_pcm_oss snd_mixer_oss snd_pcm
> snd_timer snd_page_allo
> c gameport snd_mpu401_uart snd_rawmidi snd_seq_device snd soundcore
> sk98lin floppy dm_snapshot dm_zero dm_mirror ext3 jbd raid0 dm_mod
> sata_sil sata_via liba
> ta sd_mod scsi_mod
> Jan  3 04:06:42 everest kernel: Pid: 5482, comm: updatedb Not tainted
> 2.6.9-1.681_FC3
> Jan  3 04:06:42 everest kernel: RIP: 0010:[<ffffffff801246a0>]
> <ffffffff801246a0>{do_page_fault+1341}
> Jan  3 04:06:42 everest kernel: RSP: 0018:00000100164aba98  EFLAGS: 
> 00010246
> Jan  3 04:06:42 everest kernel: RAX: 00001018003e0000 RBX:
> 0000000000000001 RCX: 000ffffffffff000
> Jan  3 04:06:42 everest kernel: RDX: 00001018003e0000 RSI:
> 0000010000000000 RDI: 00000100164abb58
> Jan  3 04:06:42 everest kernel: RBP: 000001a400000103 R08:
> 000001002d0d87a0 R09: 0000010034760000
> Jan  3 04:06:42 everest kernel: R10: ffffffff804d5d60 R11:
> 00000100164abd18 R12: 000001001e6f85b0
> Jan  3 04:06:42 everest kernel: R13: 00000100164abb58 R14:
> 0000000000000000 R15: 000001003d858280
> Jan  3 04:06:42 everest kernel: FS:  0000002a9589eb00(0000)
> GS:ffffffff80511980(0000) knlGS:00000000f760e6c0
> Jan  3 04:06:42 everest kernel: CS:  0010 DS: 0000 ES: 0000 CR0:
> 000000008005003b
> Jan  3 04:06:42 everest kernel: CR2: 00001118003e0000 CR3:
> 0000000000101000 CR4: 00000000000006e0
> Jan  3 04:06:42 everest kernel: Process updatedb (pid: 5482,
> threadinfo 00000100164aa000, task 000001001e6f85b0)
> Jan  3 04:06:42 everest kernel: Stack: 0000000000000000
> 0000010000030001 ffffffff80432d03 ffffffffffffff00
> Jan  3 04:06:42 everest kernel:        00000000000000d0
> ffffffff8043d800 00000100164abd00 ffffffff80162f40
> Jan  3 04:06:42 everest kernel:        0000000000000007 0000000000000000
> Jan  3 04:06:42 everest kernel: Call
> Trace:<ffffffff80162f40>{find_get_page+156}
> <ffffffff8018ca93>{__find_get_block_slow+505}
> Jan  3 04:06:42 everest kernel:
> <ffffffff80111099>{error_exit+0} <ffffffff801ec4d8>{uni2char+36}
> Jan  3 04:06:42 everest kernel:
> <ffffffffa0300dc5>{:fat:uni16_to_x8+61}
> <ffffffffa0302491>{:fat:fat_readdirx+3429}
> Jan  3 04:06:42 everest kernel:        <ffffffff801aee30>{iunique+282}
> <ffffffff801f7ad5>{avc_has_perm+69}
> Jan  3 04:06:42 everest kernel:        <ffffffff801a289a>{filldir64+0}
> <ffffffff801fb299>{selinux_inode_getattr+80}
> Jan  3 04:06:42 everest kernel:
> <ffffffff801f8cfe>{inode_has_perm+89} <ffffffff801a7e03>{dput+55}
> Jan  3 04:06:42 everest kernel:
> <ffffffff801fb8a3>{selinux_file_permission+298}
> <ffffffff801a289a>{filldir64+0}
> Jan  3 04:06:42 everest kernel:
> <ffffffff801a25da>{vfs_readdir+154}
> <ffffffff801a29ca>{sys_getdents64+118}
> Jan  3 04:06:42 everest kernel:        <ffffffff801107a2>{system_call+126}
> Jan  3 04:06:42 everest kernel:
> Jan  3 04:06:42 everest kernel: Code: 48 8b 14 30 f6 c2 01 0f 84 89 fc
> ff ff 48 89 e8 48 21 ca 48
> Jan  3 04:06:42 everest kernel: RIP
> <ffffffff801246a0>{do_page_fault+1341} RSP <00000100164aba98>
> Jan  3 04:06:42 everest kernel: CR2: 00001118003e0000
> Jan  3 04:06:43 everest crond(pam_unix)[4999]: session closed for user 
> root

Hrm - "Unable to handle kernel paging request" sounds ominous.  It looks 
like whenever your system runs /etc/cron.daily/slocate your system is 
running out of memory and trying to page to disk.  The kernel is unable to 
do so and throws an "oops."

I'd open a ticket with Bugzilla.  Also have a look at some of these: 
http://www.google.com/search?hl=en&lr=&q=updatedb++kernel+oops&btnG=Search

Thomas