[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: ext3 involved in kernel panic in 2.6.13?

 > Dual Opteron system running ext3 atop drbd (network RAID) devices,
 which, in turn, are atop LVM logical volumes. The underlying device
 is hardware SCSI RAID via a LSILogic HBA. The kernel is vanilla
 2.6.13 on a Gentoo-based system.

 A panic occurred, which contains references to ext3 code.

 I'm not sure how others manage to get these typed out, but I'm
 manually typing it from what's on the monitor:

  There should be more in the logs (just before the Call Trace:). Didn't
you capture also that information? Without it it is rather hard to find
out what was happening.

Unfortunately, crash information never appears in regular system log, at least using the metalog logging program. I think I would have to configure the netconsole to do that.

 > Call Trace: <IRQ> <ffffffff802820df>{i8042_interrupt+111}
 <ffffffff8010ee63>{call_softirq+31} <ffffffff80110a55>{do_softirq+53}
 <ffffffff8010e5c8>{apic_timer_interrupt+132} <EOI>
 <ffffffff801fb88e>{do_get_write_access+94} <ffffffff80185d1f>{__getblk+47}
 <ffffffff8019bd2b>{update_atime+123} <ffffffff80195016>{vfs_readdir+166}
 <ffffffff801952e2>{syst_getdents+130} <ffffffff8019465e>{sys_fcntl+830}

 Code: 8b 40 18 48 c1 e0 07 48 8b 98 08 58 5b 80 4c 01 e3 48 89 df
 RIP <ffffffff8012f369>{try_to_wake_up+57} RSP <ffff810004827e88>
 <0>Kernel panic - not syncing: Aiee, killing interrupt handler!

Jan Kara <jack suse cz>
SuSE CR Labs


Maurice Volaski, mvolaski aecom yu edu
Computing Support, Rose F. Kennedy Center
Albert Einstein College of Medicine of Yeshiva University

[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]