Topic: [solved] Kernel panic

[Paperguides]

One of the servers I look after has crashed with the following log messages:

Mar 10 06:23:07 thurley kernel: scsi3: ERROR on channel 0, id 0, lun 0, CDB: Read (10) 00 00 7d 10 97 00 00 01 00
Mar 10 06:23:07 thurley kernel: Info fld=0x7d1097, Current sr0: sense key Medium Error
Mar 10 06:23:07 thurley kernel: Additional sense: Error too long to correct
Mar 10 06:23:07 thurley kernel: end_request: I/O error, dev sr0, sector 32784988
Mar 10 06:23:07 thurley kernel: udf: udf_read_inode(ino 8196247) failed !bh
Mar 10 06:23:07 thurley kernel: Unable to handle kernel NULL pointer dereference at virtual address 00000019
Mar 10 06:23:07 thurley kernel:  printing eip:
Mar 10 06:23:07 thurley kernel: f8c2f7c9
Mar 10 06:23:07 thurley kernel: *pde = 00000000
Mar 10 06:23:07 thurley kernel: Oops: 0000 [#1]
Mar 10 06:23:07 thurley kernel: Modules linked in: nls_utf8 cifs udf appletalk(U) e1000 ipt_ULOG ipt_REJECT ipt_MASQUERADE ipt_state ip_nat_ftp ip_conntrack_ftp iptable_mangle iptable_nat ip_conntrack iptable_filter ip_tables loop button battery ac uhci_hcd ehci_hcd i3000_edac edac_mc hw_random bonding(U) floppy sr_mod dm_snapshot dm_zero dm_mirror ext3 jbd raid1 dm_mod ata_piix ahci libata sd_mod scsi_mod
Mar 10 06:23:07 thurley kernel: CPU:    0
Mar 10 06:23:07 thurley kernel: EIP:    0060:[<f8c2f7c9>]    Not tainted VLI
Mar 10 06:23:07 thurley kernel: EFLAGS: 00010246   (2.6.9-89.31.1.EL)
Mar 10 06:23:07 thurley kernel: EIP is at udf_get_filelongad+0x38/0x4b [udf]
Mar 10 06:23:07 thurley kernel: eax: 00000000   ebx: 00000019   ecx: d6bc2d84   edx: 00000038
Mar 10 06:23:07 thurley kernel: esi: 0b7500c8   edi: d8d9c214   ebp: d6bc2d74   esp: d6bc2d04
Mar 10 06:23:07 thurley kernel: ds: 007b   es: 007b   ss: 0068
Mar 10 06:23:07 thurley kernel: Process ls (pid: 15852, threadinfo=d6bc2000 task=d70358f0)
Mar 10 06:23:07 thurley kernel: Stack: 00000019 d6bc2d80 f8c27be8 00000001 00000000 00000000 111205c5 00000000
Mar 10 06:23:07 thurley kernel:        00000000 c03757b8 00000001 d6bc2d80 d8d9c24c d6bc2d74 00000001 f8c27abb
Mar 10 06:23:07 thurley kernel:        d6bc2d7c 00000001 00000010 d8d9c24c 00000000 00000000 f8c2e996 d6bc2d7c
Mar 10 06:23:07 thurley kernel: Call Trace:
Mar 10 06:23:07 thurley kernel:  [<f8c27be8>] udf_current_aext+0x11f/0x174 [udf]
Mar 10 06:23:07 thurley kernel:  [<f8c27abb>] udf_next_aext+0x6a/0x78 [udf]
Mar 10 06:23:07 thurley kernel:  [<f8c2e996>] udf_discard_prealloc+0xa2/0x19c [udf]
Mar 10 06:23:07 thurley kernel:  [<f8c23e0b>] udf_clear_inode+0xb1/0x157 [udf]
Mar 10 06:23:07 thurley kernel:  [clear_inode+204/258] clear_inode+0xcc/0x102
Mar 10 06:23:07 thurley kernel:  [<c018d3c0>] clear_inode+0xcc/0x102
Mar 10 06:23:07 thurley kernel:  [generic_forget_inode+629/645] generic_forget_inode+0x275/0x285
Mar 10 06:23:07 thurley kernel:  [<c018f3c1>] generic_forget_inode+0x275/0x285
Mar 10 06:23:07 thurley kernel:  [iput+95/97] iput+0x5f/0x61
Mar 10 06:23:07 thurley kernel:  [<c018f440>] iput+0x5f/0x61
Mar 10 06:23:07 thurley kernel:  [<f8c2752e>] udf_iget+0xb8/0xc1 [udf]
Mar 10 06:23:07 thurley kernel:  [<f8c28b6e>] udf_lookup+0x11c/0x213 [udf]
Mar 10 06:23:07 thurley kernel:  [__cond_resched+20/59] __cond_resched+0x14/0x3b
Mar 10 06:23:07 thurley kernel:  [<c0322098>] __cond_resched+0x14/0x3b
Mar 10 06:23:07 thurley kernel:  [real_lookup+126/259] real_lookup+0x7e/0x103
Mar 10 06:23:07 thurley kernel:  [<c017e67b>] real_lookup+0x7e/0x103
Mar 10 06:23:07 thurley kernel:  [do_lookup+93/186] do_lookup+0x5d/0xba
Mar 10 06:23:07 thurley kernel:  [<c017e9cc>] do_lookup+0x5d/0xba
Mar 10 06:23:07 thurley kernel:  [__link_path_walk+2736/3710] __link_path_walk+0xab0/0xe7e
Mar 10 06:23:07 thurley kernel:  [<c017f4d9>] __link_path_walk+0xab0/0xe7e
Mar 10 06:23:07 thurley kernel:  [__d_lookup+325/495] __d_lookup+0x145/0x1ef
Mar 10 06:23:07 thurley kernel:  [<c018b051>] __d_lookup+0x145/0x1ef
Mar 10 06:23:07 thurley kernel:  [link_path_walk+52/156] link_path_walk+0x34/0x9c
Mar 10 06:23:07 thurley kernel:  [<c017f8db>] link_path_walk+0x34/0x9c
Mar 10 06:23:07 thurley kernel:  [path_lookup+260/313] path_lookup+0x104/0x139
Mar 10 06:23:07 thurley kernel:  [<c017fbc3>] path_lookup+0x104/0x139
Mar 10 06:23:07 thurley kernel:  [__user_walk+33/81] __user_walk+0x21/0x51
Mar 10 06:23:07 thurley kernel:  [<c017fd18>] __user_walk+0x21/0x51
Mar 10 06:23:07 thurley kernel:  [vfs_lstat64+17/55] vfs_lstat64+0x11/0x37
Mar 10 06:23:07 thurley kernel:  [<c0179c51>] vfs_lstat64+0x11/0x37
Mar 10 06:23:07 thurley kernel:  [dput+51/1059] dput+0x33/0x423
Mar 10 06:23:07 thurley kernel:  [<c0188c17>] dput+0x33/0x423
Mar 10 06:23:07 thurley kernel:  [__cond_resched+20/59] __cond_resched+0x14/0x3b
Mar 10 06:23:07 thurley kernel:  [<c0322098>] __cond_resched+0x14/0x3b
Mar 10 06:23:07 thurley kernel:  [dput+51/1059] dput+0x33/0x423
Mar 10 06:23:07 thurley kernel:  [<c0188c17>] dput+0x33/0x423
Mar 10 06:23:07 thurley kernel:  [path_release+10/44] path_release+0xa/0x2c
Mar 10 06:23:07 thurley kernel:  [<c017e519>] path_release+0xa/0x2c
Mar 10 06:23:07 thurley kernel:  [sys_lstat64+15/35] sys_lstat64+0xf/0x23
Mar 10 06:23:07 thurley kernel:  [<c017a27c>] sys_lstat64+0xf/0x23
Mar 10 06:23:07 thurley kernel:  [syscall_call+7/11] syscall_call+0x7/0xb
Mar 10 06:23:07 thurley kernel:  [<c03239eb>] syscall_call+0x7/0xb
Mar 10 06:23:07 thurley kernel: Code: 0f 94 c2 09 d0 a8 01 74 0f 68 3a 15 c3 f8 e8 9c 5c 4f c7 59 31 c0 eb 23 8b 01 85 c0 78 07 8d 50 10 39 f2 76 04 31 c0 eb 12 31 c0 <83> 3b 00 74 0b 83 7c 24 0c 00 74 02 89 11 89 d8 5b 5e c3 56 53
Mar 10 06:23:07 thurley kernel:  <0>Fatal exception: panic in 5 seconds

How do I pick the bones out this?  I suspect it is due the failure of yet another Iomega disk.  But why cause the system to crash?

edit by cactus: added solved keyword to subject and changed a minor typo in it.

[byte]

How do I pick the bones out this?  I suspect it is due the failure of yet another Iomega disk. 

What setup do you have? Raid 1 ?

But why cause the system to crash?

If it was due to a bad disk then you will have received warning emails telling you/admin of an impending failure or action required.

[Stefano]

I would check the ram too...

[Paperguides]

I raised a bug report on this and it looks like a kernel problem with UDF disks.

I have had no end of problems with the Iomega Rev system in this server and will never use or recommend an Iomega removable media solution ever again in the future.  I have ordered a set of steel cased USB external drives (Toshiba) to replace the system.

When I remove the drive, I will also run some memory diags just to sure.  For the record the system is a Acer Altos G330 with a h/w raid 1 of 2 500G drives and 4Gb memory.

Tony

[byte]

I raised a bug report on this and it looks like a kernel problem with UDF disks.

Could you please post the bug number for future readers and put in title [SOLVED] - Thanks.