Fanying Jen wrote:
Hello, I have an IBM xSeries x335 Dual Xeon processors and 4GB memory which have a system crash. The system locked up hard and only a hard reboot would recover the system. I could only get the kernel panic dump. There was no core dump.
Dec 21 09:48:13 columbia kernel: Dec 21 09:48:13 columbia kernel: wait_on_irq, CPU 3: Dec 21 09:48:13 columbia kernel: irq: 0 [ 0 0 0 0 ] Dec 21 09:48:13 columbia kernel: bh: 1 [ 2 4 0 0 ] Dec 21 09:48:13 columbia kernel: Stack dumps: Dec 21 09:48:13 columbia kernel: CPU 0: <unknown> Dec 21 09:48:13 columbia kernel: CPU 1:6b6b6b6b 6b6b6b6b 6b6b6b6b 6b6b6b6b 6b6b6b6b 6b6b6b6b 6b6b6b6b 6b6b6b6b Dec 21 09:48:13 columbia kernel: 6b6b6b6b 6b6b6b6b 6b6b6b6b 6b6b6b6b 6b6b6b6b 6b6b6b6b 6b6b6b6b 6b6b6b6b Dec 21 09:48:13 columbia kernel: 6b6b6b6b 6b6b6b6b 6b6b6b6b 6b6b6b6b 6b6b6b6b 6b6b6b6b 6b6b6b6b 6b6b6b6b Dec 21 09:48:13 columbia kernel: Call Trace: Dec 21 09:48:13 columbia kernel: Dec 21 09:48:13 columbia kernel: CPU 2:c037eb88 00000000 00000000 00000000 00000000 00000000 6d6d6873 5a007861 Dec 21 09:48:13 columbia kernel: 5a5a5a5a 5a5a5a5a 5a5a5a5a 5a5a5a5a 5a5a5a5a 5a5a5a5a 5a5a5a5a 5a5a5a5a Dec 21 09:48:13 columbia kernel: 5a5a5a5a 5a5a5a5a a55a5a5a 170fc2a5 170fc2a5 00061041 c405e7b0 000181a4 Dec 21 09:48:13 columbia kernel: Call Trace: Dec 21 09:48:13 columbia kernel: Dec 21 09:48:13 columbia kernel: CPU 3:f7f99f2c 00000003 00000003 ffffffff 00000003 c010c7c8 c02a8aca 00000003 Dec 21 09:48:13 columbia kernel: d93ab000 c010b962 00000003 c03864c4 c01b64a1 c037f66c c037f668 f7f98000 Dec 21 09:48:13 columbia kernel: 0000013d d93ab368 c03864c4 f7f99f8c f7f9836e 00000000 c012c05a d93ab000 Dec 21 09:48:13 columbia kernel: Call Trace: [<c010c7c8>] wait_on_irq [kernel] 0xf8 (0xf7f99f40) Dec 21 09:48:13 columbia kernel: [<c010b962>] __global_cli [kernel] 0x62 (0xf7f99f50) Dec 21 09:48:13 columbia kernel: [<c01b64a1>] flush_to_ldisc [kernel] 0xb1 (0xf7f99f5c) Dec 21 09:48:13 columbia kernel: [<c012c05a>] __run_task_queue [kernel] 0x6a (0xf7f99f84) Dec 21 09:48:13 columbia kernel: [<c01375d9>] context_thread [kernel] 0x149 (0xf7f99f9c) Dec 21 09:48:14 columbia kernel: [<c0137490>] context_thread [kernel] 0x0 (0xf7f99fc4) Dec 21 09:48:14 columbia kernel: [<c0137490>] context_thread [kernel] 0x0 (0xf7f99fe0) Dec 21 09:48:14 columbia kernel: [<c010758d>] kernel_thread_helper [kernel] 0x5 (0xf7f99ff0) Dec 21 09:48:14 columbia kernel: Dec 21 09:04:24 columbia kernel: klogd 1.4.1, log source = /proc/kmsg started. Dec 21 09:04:24 columbia kernel: Linux version 2.4.22-1.2105.nptlsmp (bhcompile@xxxxxxxxxxxxxxxxxxxxxx) (gcc version 3.2.3 20030422 (Red Hat Linux 3.2.3-6)) #1 SMP Tue Oct 21 21:56:41 EDT 2003 Dec 21 09:04:24 columbia kernel: BIOS-provided physical RAM map:
This system is identical to two other system in every way including kernel and hardware but those systems never crashed. This particular system is running LDAP, NFS, Samba, CUPS, and DNS. The other systems are LTSP servers which running far more applications and services than this system and the question is why did this system crashed so hard with absolutely no warning? I don't believe it is hardware or the kernel since other systems would exhibit this problem as well.
------------------------------------------------------------------ Fanying Jen Email: fanying@xxxxxxxxx
Pgp Key: http://fanying.fynet.com:11371/pks/lookup?op=get&search=0x6B92EAC5
The Fanying Jen Network http://www.fy-net.com/ http://www.fynet.com/ ------------------------------------------------------------------ - : send the line "unsubscribe linux-admin" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
- : send the line "unsubscribe linux-admin" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
