> -----Original Message-----
> From: DD [mailto:bqlist (at mark) distortal.com]
> Sent: Saturday, August 22, 2009 1:16 PM
> To: coba-e (at mark) bluequartz.org
> Subject: [coba-e:15909] Fatal exception: panic in 5 seconds
>
> Hi all,
>
> Since this morning I've had a server shutting down on me repeatedly -
> there
> goes my Saturday. It responds to Ping but HTTP, FTP etc re
> unavailable and
> I have to get the on-site guys to reboot it each time.
>
> Does the following, from /var/spool/messages/ aruond the time of the
> last-but-one shutdown, give anyone any ideas?
>
> Regards,
>
>
>
> Dick
>
> -----------------------------
>
> Aug 22 17:00:08 server30338 cced(smd)[12276]: client 0:[0:12257]: SET
> succeeded
> Aug 22 17:00:08 server30338 cced(smd)[12276]: client 0:[0:12257]: SET
> 17 .
> Admserv lastChange = 1250956808 currentState = G currentMessage =
> "[[base-apache.amAdmservStatusOK]]"
> Aug 22 17:00:08 server30338 cced(smd)[12276]: client 0:[0:12257]: SET
> succeeded
> Aug 22 17:00:49 server30338 PAM_pwdb[12507]: check pass; user unknown
> Aug 22 17:01:01 server30338 loadavg: 17:01:01 up 1:01, 0 users, load
> average: 0.42, 0.36, 0.36
> Aug 22 17:01:01 server30338 memavg: total used free shared buffers
> cached
> Aug 22 17:01:01 server30338 memavg: Mem: 1511 807 703 0 72 319
> Aug 22 17:01:01 server30338 memavg: -/+ buffers/cache: 415 1095
> Aug 22 17:01:01 server30338 memavg: Swap: 1027 0 1027
> Aug 22 17:01:02 server30338 iptables: succeeded
> Aug 22 17:01:02 server30338 iptables: succeeded
> Aug 22 17:01:03 server30338 kernel: Unable to handle kernel paging
> request
> at virtual address f89d7168
> Aug 22 17:01:03 server30338 kernel: printing eip:
> Aug 22 17:01:03 server30338 kernel: c02d48af
> Aug 22 17:01:03 server30338 kernel: *pde = 01d24067
> Aug 22 17:01:03 server30338 kernel: Oops: 0000 [#1]
> Aug 22 17:01:03 server30338 kernel: Modules linked in: ip_conntrack
> autofs4
> i2c_dev i2c_core cpufreq_powersave dm_mirror dm_mod button battery ac
> uhci_hcd ehci_hcd snd_intel8x0 snd_ac97_codec snd_pcm_oss
> snd_mixer_oss
> snd_pcm snd_timer snd_page_alloc snd_mpu401_uart snd_rawmidi
> snd_seq_device
> snd soundcore 8139too mii floppy ata_piix libata scsi_mod ext3 jbd
> Aug 22 17:01:03 server30338 kernel: CPU: 0
> Aug 22 17:01:03 server30338 kernel: EIP: 0060:[<c02d48af>] Not
> tainted VLI
> Aug 22 17:01:03 server30338 kernel: EFLAGS: 00010216 (2.6.9-
> 78.0.8.EL)
> Aug 22 17:01:03 server30338 kernel: EIP is at
> nf_unregister_sockopt+0x47/0x81
> Aug 22 17:01:03 server30338 kernel: eax: 00000002 ebx: c03a2040 ecx:
> f6b7f920 edx: f89d7160
> Aug 22 17:01:03 server30338 kernel: esi: f8aae380 edi: 00000000 ebp:
> ef4ac000 esp: ef4acf5c
> Aug 22 17:01:03 server30338 kernel: ds: 007b es: 007b ss: 0068
> Aug 22 17:01:03 server30338 kernel: Process modprobe (pid: 12662,
> threadinfo=ef4ac000 task=f48721b0)
> Aug 22 17:01:03 server30338 kernel: Stack: 00000000 c037d800 f8aa5732
> f8aae880 c014031d 00000000 635f7069 746e6e6f
> Aug 22 17:01:03 server30338 kernel: 6b636172 00000000 efbd8400
> b7f29000
> b7f2a000 c01602fe efbd8400 ee4a1c48
> Aug 22 17:01:03 server30338 kernel: c01606a3 ee4a1f90 efbd8400
> efbd8430
> 00000000 ef4ac000 09030180 00000000
> Aug 22 17:01:03 server30338 kernel: Call Trace:
> Aug 22 17:01:03 server30338 kernel: [<f8aa5732>]
> init_or_cleanup+0x1e6/0x1ea
> [ip_conntrack]
> Aug 22 17:01:03 server30338 kernel: [<c014031d>]
> sys_delete_module+0x139/0x180
> Aug 22 17:01:03 server30338 kernel: [<c01602fe>]
> unmap_vma_list+0xe/0x17
> Aug 22 17:01:03 server30338 kernel: [<c01606a3>]
> do_munmap+0x1a7/0x1b1
> Aug 22 17:01:03 server30338 kernel: [<c03279ab>] syscall_call+0x7/0xb
> Aug 22 17:01:03 server30338 kernel: Code: 17 05 00 89 d9 ff 0d 40 20
> 3a c0
> 0f 88 40 0d 00 00 8b 0d 68 20 3a c0 8b 01 0f 18 00 90 81 f9 68 20 3a
> c0 74
> 2f 8b 51 08 8b 46 08 <39> 42 08 8b 11 75 1e 8b 41 04 89 42 04 89 10
> 89 c8 c7
> 01 00 01
> Aug 22 17:01:03 server30338 kernel: <0>Fatal exception: panic in 5
> seconds
> Aug 22 17:37:06 server30338 syslogd 1.4.1: restart.
>
My guess you may have a bad hard drive sector in the swap space:
Aug 22 17:01:03 server30338 kernel: Unable to handle kernel paging request
at virtual address f89d7168
Might be worth (if you have a raid 1 array) pulling one disk out, trying to
boot. If that works, great. If not, try the other drive.
Just a "gut feeling" - not sure but an idea.
Thanks,
-Stephanie