Carl Billington
asked on
Linux crash analysing message log
I am running 2.6.18-1.2798.fc6
How do I find out what has caused the crash? I have copied the message log below:
Jul 28 00:23:15 FILESERVER smbd[7229]: call_nt_transact_ioctl(0x9 009c): Currently not implemented.
Jul 28 00:57:42 FILESERVER kernel: BUG: unable to handle kernel NULL pointer dereference at virtual address 00000008
Jul 28 00:57:42 FILESERVER kernel: printing eip:
Jul 28 00:57:42 FILESERVER kernel: c04e24cc
Jul 28 00:57:42 FILESERVER kernel: *pde = 593c1067
Jul 28 00:57:42 FILESERVER kernel: Oops: 0000 [#1]
Jul 28 00:57:42 FILESERVER kernel: SMP
Jul 28 00:57:42 FILESERVER kernel: last sysfs file: /devices/pci0000:00/0000:0 0:12.0/000 0:02:0c.0/ fw-host0/0 0148556001 e098e/0014 8556001e09 8e-0/versi on
Jul 28 00:57:42 FILESERVER kernel: Modules linked in: iptable_nat ip_nat ip_conntrack nfnetlink iptable_mangle iptable_filter ip_tables x_tables autofs4 hidp rfcomm l2cap bluetooth sunrpc freq_table dm_multipath video sbs i2c_ec button battery ac radeon drm ipv6 parport_pc lp parport snd_intel8x0 snd_ac97_codec snd_ac97_bus snd_seq_dummy snd_seq_oss snd_seq_midi_event snd_seq snd_seq_device snd_pcm_oss snd_mixer_oss snd_pcm snd_timer ohci1394 snd soundcore ieee1394 e1000 snd_page_alloc ide_cd cdrom i2c_nforce2 serio_raw floppy i2c_core pcspkr dm_snapshot dm_zero dm_mirror dm_mod sata_nv libata sd_mod scsi_mod ext3 jbd ehci_hcd ohci_hcd uhci_hcd
Jul 28 00:57:42 FILESERVER kernel: CPU: 0
Jul 28 00:57:42 FILESERVER kernel: EIP: 0060:[<c04e24cc>] Not tainted VLI
Jul 28 00:57:42 FILESERVER kernel: EFLAGS: 00210286 (2.6.18-1.2798.fc6 #1)
Jul 28 00:57:42 FILESERVER kernel: EIP is at __rb_rotate_left+0xc/0x50
Jul 28 00:57:42 FILESERVER kernel: eax: f6b60ec8 ebx: f6b60ec8 ecx: f5279a48 edx: 00000000
Jul 28 00:57:43 FILESERVER kernel: esi: f6b60748 edi: c07ff8c0 ebp: 00000000 esp: e1703ed0
Jul 28 00:57:43 FILESERVER kernel: ds: 007b es: 007b ss: 0068
Jul 28 00:57:43 FILESERVER kernel: Process smbd (pid: 7229, ti=e1703000 task=f7f192c0 task.ti=e1703000)
Jul 28 00:57:43 FILESERVER kernel: Stack: f5279a48 f6b60ec8 f52797c8 c04e25ec c07ff8c0 f5279a4c 00000000 f5279820
Jul 28 00:57:43 FILESERVER kernel: f3a388c0 c04b7140 00003a98 c067ed20 00000000 f52797c0 f52797c0 0000001f
Jul 28 00:57:43 FILESERVER kernel: 00003a98 f6b5f7c0 e1703f50 c07ee590 c04b7eb2 ffffffff f7f192c0 1f3f0000
Jul 28 00:57:43 FILESERVER kernel: Call Trace:
Jul 28 00:57:43 FILESERVER kernel: [<c04e25ec>] rb_insert_color+0x8c/0xad
Jul 28 00:57:43 FILESERVER kernel: [<c04b7140>] key_alloc+0x25c/0x325
Jul 28 00:57:43 FILESERVER kernel: [<c04b7eb2>] keyring_alloc+0x30/0x6a
Jul 28 00:57:43 FILESERVER kernel: [<c04b9550>] alloc_uid_keyring+0x4c/0xb 2
Jul 28 00:57:43 FILESERVER kernel: [<c042a82d>] alloc_uid+0x95/0x13c
Jul 28 00:57:43 FILESERVER kernel: [<c042d68f>] set_user+0xb/0x8e
Jul 28 00:57:43 FILESERVER kernel: [<c042ef4c>] sys_setresuid+0x111/0x1dd
Jul 28 00:57:43 FILESERVER kernel: [<c0404027>] syscall_call+0x7/0xb
Jul 28 00:57:43 FILESERVER kernel: DWARF2 unwinder stuck at syscall_call+0x7/0xb
Jul 28 00:57:43 FILESERVER kernel: Leftover inexact backtrace:
Jul 28 00:57:43 FILESERVER kernel: =======================
Jul 28 00:57:43 FILESERVER kernel: Code: 00 00 00 8b 45 04 83 c1 14 d3 e2 85 d0 75 05 09 d0 89 45 04 5a 89 f0 59 5b 5e 5f 5d c3 90 90 57 89 d7 56 53 8b 50 04 89 c3 8b 30 <8b> 4a 08 83 e6 fc 85 c9 89 48 04 74 09 8b 01 83 e0 03 09 d8 89
Jul 28 00:57:43 FILESERVER kernel: EIP: [<c04e24cc>] __rb_rotate_left+0xc/0x50 SS:ESP 0068:e1703ed0
Jul 28 00:57:52 FILESERVER kernel: <3>BUG: soft lockup detected on CPU#0!
Jul 28 00:57:52 FILESERVER kernel: [<c0405876>] dump_trace+0x69/0x1af
Jul 28 00:57:52 FILESERVER kernel: [<c04059d4>] show_trace_log_lvl+0x18/0x 2c
Jul 28 00:57:52 FILESERVER kernel: [<c0405f83>] show_trace+0xf/0x11
Jul 28 00:57:52 FILESERVER kernel: [<c0406080>] dump_stack+0x15/0x17
Jul 28 00:57:52 FILESERVER kernel: [<c04497ed>] softlockup_tick+0xad/0xc4
Jul 28 00:57:52 FILESERVER kernel: [<c042a3b5>] update_process_times+0x39/ 0x5c
Jul 28 00:57:52 FILESERVER kernel: [<c04148c5>] smp_apic_timer_interrupt+0 x5b/0x62
Jul 28 00:57:52 FILESERVER kernel: [<c040512f>] apic_timer_interrupt+0x1f/ 0x30
Jul 28 00:57:52 FILESERVER kernel: DWARF2 unwinder stuck at apic_timer_interrupt+0x1f/ 0x30
Jul 28 00:57:52 FILESERVER kernel: Leftover inexact backtrace:
Jul 28 00:57:52 FILESERVER kernel: [<c052007b>] acpi_processor_write_limit +0x62/0xc3
Jul 28 00:57:52 FILESERVER kernel: [<c04e5377>] _raw_spin_lock+0x6f/0xdc
Jul 28 00:57:52 FILESERVER kernel: [<c04b70b1>] key_alloc+0x1cd/0x325
Jul 28 00:57:52 FILESERVER kernel: [<c04b7eb2>] keyring_alloc+0x30/0x6a
Jul 28 00:57:52 FILESERVER kernel: [<c04b9550>] alloc_uid_keyring+0x4c/0xb 2
Jul 28 00:57:52 FILESERVER kernel: [<c042a82d>] alloc_uid+0x95/0x13c
Jul 28 00:57:52 FILESERVER kernel: [<c042d68f>] set_user+0xb/0x8e
Jul 28 00:57:52 FILESERVER kernel: [<c042ef4c>] sys_setresuid+0x111/0x1dd
Jul 28 00:57:52 FILESERVER kernel: [<c0404027>] syscall_call+0x7/0xb
Jul 28 00:57:52 FILESERVER kernel: =======================
Jul 28 00:59:07 FILESERVER kernel: BUG: spinlock lockup on CPU#0, smbd/7290, c067ec20 (Not tainted)
Jul 28 00:59:07 FILESERVER kernel: [<c0405876>] dump_trace+0x69/0x1af
Jul 28 00:59:07 FILESERVER kernel: [<c04059d4>] show_trace_log_lvl+0x18/0x 2c
Jul 28 00:59:07 FILESERVER kernel: [<c0405f83>] show_trace+0xf/0x11
Jul 28 00:59:07 FILESERVER kernel: [<c0406080>] dump_stack+0x15/0x17
Jul 28 00:59:07 FILESERVER kernel: [<c04e53c7>] _raw_spin_lock+0xbf/0xdc
Jul 28 00:59:07 FILESERVER kernel: [<c04b70b1>] key_alloc+0x1cd/0x325
Jul 28 00:59:07 FILESERVER kernel: [<c04b7eb2>] keyring_alloc+0x30/0x6a
Jul 28 00:59:07 FILESERVER kernel: [<c04b9550>] alloc_uid_keyring+0x4c/0xb 2
Jul 28 00:59:07 FILESERVER kernel: [<c042a82d>] alloc_uid+0x95/0x13c
Jul 28 00:59:07 FILESERVER kernel: [<c042d68f>] set_user+0xb/0x8e
Jul 28 00:59:07 FILESERVER kernel: [<c042ef4c>] sys_setresuid+0x111/0x1dd
Jul 28 00:59:07 FILESERVER kernel: [<c0404027>] syscall_call+0x7/0xb
Jul 28 00:59:07 FILESERVER kernel: DWARF2 unwinder stuck at syscall_call+0x7/0xb
Jul 28 00:59:07 FILESERVER kernel: Leftover inexact backtrace:
Jul 28 00:59:07 FILESERVER kernel: =======================
Regards
How do I find out what has caused the crash? I have copied the message log below:
Jul 28 00:23:15 FILESERVER smbd[7229]: call_nt_transact_ioctl(0x9
Jul 28 00:57:42 FILESERVER kernel: BUG: unable to handle kernel NULL pointer dereference at virtual address 00000008
Jul 28 00:57:42 FILESERVER kernel: printing eip:
Jul 28 00:57:42 FILESERVER kernel: c04e24cc
Jul 28 00:57:42 FILESERVER kernel: *pde = 593c1067
Jul 28 00:57:42 FILESERVER kernel: Oops: 0000 [#1]
Jul 28 00:57:42 FILESERVER kernel: SMP
Jul 28 00:57:42 FILESERVER kernel: last sysfs file: /devices/pci0000:00/0000:0
Jul 28 00:57:42 FILESERVER kernel: Modules linked in: iptable_nat ip_nat ip_conntrack nfnetlink iptable_mangle iptable_filter ip_tables x_tables autofs4 hidp rfcomm l2cap bluetooth sunrpc freq_table dm_multipath video sbs i2c_ec button battery ac radeon drm ipv6 parport_pc lp parport snd_intel8x0 snd_ac97_codec snd_ac97_bus snd_seq_dummy snd_seq_oss snd_seq_midi_event snd_seq snd_seq_device snd_pcm_oss snd_mixer_oss snd_pcm snd_timer ohci1394 snd soundcore ieee1394 e1000 snd_page_alloc ide_cd cdrom i2c_nforce2 serio_raw floppy i2c_core pcspkr dm_snapshot dm_zero dm_mirror dm_mod sata_nv libata sd_mod scsi_mod ext3 jbd ehci_hcd ohci_hcd uhci_hcd
Jul 28 00:57:42 FILESERVER kernel: CPU: 0
Jul 28 00:57:42 FILESERVER kernel: EIP: 0060:[<c04e24cc>] Not tainted VLI
Jul 28 00:57:42 FILESERVER kernel: EFLAGS: 00210286 (2.6.18-1.2798.fc6 #1)
Jul 28 00:57:42 FILESERVER kernel: EIP is at __rb_rotate_left+0xc/0x50
Jul 28 00:57:42 FILESERVER kernel: eax: f6b60ec8 ebx: f6b60ec8 ecx: f5279a48 edx: 00000000
Jul 28 00:57:43 FILESERVER kernel: esi: f6b60748 edi: c07ff8c0 ebp: 00000000 esp: e1703ed0
Jul 28 00:57:43 FILESERVER kernel: ds: 007b es: 007b ss: 0068
Jul 28 00:57:43 FILESERVER kernel: Process smbd (pid: 7229, ti=e1703000 task=f7f192c0 task.ti=e1703000)
Jul 28 00:57:43 FILESERVER kernel: Stack: f5279a48 f6b60ec8 f52797c8 c04e25ec c07ff8c0 f5279a4c 00000000 f5279820
Jul 28 00:57:43 FILESERVER kernel: f3a388c0 c04b7140 00003a98 c067ed20 00000000 f52797c0 f52797c0 0000001f
Jul 28 00:57:43 FILESERVER kernel: 00003a98 f6b5f7c0 e1703f50 c07ee590 c04b7eb2 ffffffff f7f192c0 1f3f0000
Jul 28 00:57:43 FILESERVER kernel: Call Trace:
Jul 28 00:57:43 FILESERVER kernel: [<c04e25ec>] rb_insert_color+0x8c/0xad
Jul 28 00:57:43 FILESERVER kernel: [<c04b7140>] key_alloc+0x25c/0x325
Jul 28 00:57:43 FILESERVER kernel: [<c04b7eb2>] keyring_alloc+0x30/0x6a
Jul 28 00:57:43 FILESERVER kernel: [<c04b9550>] alloc_uid_keyring+0x4c/0xb
Jul 28 00:57:43 FILESERVER kernel: [<c042a82d>] alloc_uid+0x95/0x13c
Jul 28 00:57:43 FILESERVER kernel: [<c042d68f>] set_user+0xb/0x8e
Jul 28 00:57:43 FILESERVER kernel: [<c042ef4c>] sys_setresuid+0x111/0x1dd
Jul 28 00:57:43 FILESERVER kernel: [<c0404027>] syscall_call+0x7/0xb
Jul 28 00:57:43 FILESERVER kernel: DWARF2 unwinder stuck at syscall_call+0x7/0xb
Jul 28 00:57:43 FILESERVER kernel: Leftover inexact backtrace:
Jul 28 00:57:43 FILESERVER kernel: =======================
Jul 28 00:57:43 FILESERVER kernel: Code: 00 00 00 8b 45 04 83 c1 14 d3 e2 85 d0 75 05 09 d0 89 45 04 5a 89 f0 59 5b 5e 5f 5d c3 90 90 57 89 d7 56 53 8b 50 04 89 c3 8b 30 <8b> 4a 08 83 e6 fc 85 c9 89 48 04 74 09 8b 01 83 e0 03 09 d8 89
Jul 28 00:57:43 FILESERVER kernel: EIP: [<c04e24cc>] __rb_rotate_left+0xc/0x50 SS:ESP 0068:e1703ed0
Jul 28 00:57:52 FILESERVER kernel: <3>BUG: soft lockup detected on CPU#0!
Jul 28 00:57:52 FILESERVER kernel: [<c0405876>] dump_trace+0x69/0x1af
Jul 28 00:57:52 FILESERVER kernel: [<c04059d4>] show_trace_log_lvl+0x18/0x
Jul 28 00:57:52 FILESERVER kernel: [<c0405f83>] show_trace+0xf/0x11
Jul 28 00:57:52 FILESERVER kernel: [<c0406080>] dump_stack+0x15/0x17
Jul 28 00:57:52 FILESERVER kernel: [<c04497ed>] softlockup_tick+0xad/0xc4
Jul 28 00:57:52 FILESERVER kernel: [<c042a3b5>] update_process_times+0x39/
Jul 28 00:57:52 FILESERVER kernel: [<c04148c5>] smp_apic_timer_interrupt+0
Jul 28 00:57:52 FILESERVER kernel: [<c040512f>] apic_timer_interrupt+0x1f/
Jul 28 00:57:52 FILESERVER kernel: DWARF2 unwinder stuck at apic_timer_interrupt+0x1f/
Jul 28 00:57:52 FILESERVER kernel: Leftover inexact backtrace:
Jul 28 00:57:52 FILESERVER kernel: [<c052007b>] acpi_processor_write_limit
Jul 28 00:57:52 FILESERVER kernel: [<c04e5377>] _raw_spin_lock+0x6f/0xdc
Jul 28 00:57:52 FILESERVER kernel: [<c04b70b1>] key_alloc+0x1cd/0x325
Jul 28 00:57:52 FILESERVER kernel: [<c04b7eb2>] keyring_alloc+0x30/0x6a
Jul 28 00:57:52 FILESERVER kernel: [<c04b9550>] alloc_uid_keyring+0x4c/0xb
Jul 28 00:57:52 FILESERVER kernel: [<c042a82d>] alloc_uid+0x95/0x13c
Jul 28 00:57:52 FILESERVER kernel: [<c042d68f>] set_user+0xb/0x8e
Jul 28 00:57:52 FILESERVER kernel: [<c042ef4c>] sys_setresuid+0x111/0x1dd
Jul 28 00:57:52 FILESERVER kernel: [<c0404027>] syscall_call+0x7/0xb
Jul 28 00:57:52 FILESERVER kernel: =======================
Jul 28 00:59:07 FILESERVER kernel: BUG: spinlock lockup on CPU#0, smbd/7290, c067ec20 (Not tainted)
Jul 28 00:59:07 FILESERVER kernel: [<c0405876>] dump_trace+0x69/0x1af
Jul 28 00:59:07 FILESERVER kernel: [<c04059d4>] show_trace_log_lvl+0x18/0x
Jul 28 00:59:07 FILESERVER kernel: [<c0405f83>] show_trace+0xf/0x11
Jul 28 00:59:07 FILESERVER kernel: [<c0406080>] dump_stack+0x15/0x17
Jul 28 00:59:07 FILESERVER kernel: [<c04e53c7>] _raw_spin_lock+0xbf/0xdc
Jul 28 00:59:07 FILESERVER kernel: [<c04b70b1>] key_alloc+0x1cd/0x325
Jul 28 00:59:07 FILESERVER kernel: [<c04b7eb2>] keyring_alloc+0x30/0x6a
Jul 28 00:59:07 FILESERVER kernel: [<c04b9550>] alloc_uid_keyring+0x4c/0xb
Jul 28 00:59:07 FILESERVER kernel: [<c042a82d>] alloc_uid+0x95/0x13c
Jul 28 00:59:07 FILESERVER kernel: [<c042d68f>] set_user+0xb/0x8e
Jul 28 00:59:07 FILESERVER kernel: [<c042ef4c>] sys_setresuid+0x111/0x1dd
Jul 28 00:59:07 FILESERVER kernel: [<c0404027>] syscall_call+0x7/0xb
Jul 28 00:59:07 FILESERVER kernel: DWARF2 unwinder stuck at syscall_call+0x7/0xb
Jul 28 00:59:07 FILESERVER kernel: Leftover inexact backtrace:
Jul 28 00:59:07 FILESERVER kernel: =======================
Regards
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Tell us if it was broken memory or something else?
The best bet would be to actually submit this to the kernel.org mailing list.