Date: Tue, 15 Dec 1998 19:26:07 -0700 (MST) From: "Kenneth D. Merry" <ken@plutotech.com> To: swjeong@net.kitel.co.kr (swjeong) Cc: freebsd-scsi@FreeBSD.ORG Subject: Re: kernel panic with ufsspec_write Message-ID: <199812160226.TAA64896@panzer.plutotech.com> In-Reply-To: <199812152222.HAA01711@net.kitel.co.kr> from swjeong at "Dec 16, 98 07:22:35 am"
next in thread | previous in thread | raw e-mail | index | archive | help
swjeong wrote... > > I have used segate ST34572W (4G ultra wide) under heavy load on RELEASE-2.2.5 . > But in the same configuration with ST34371W on RELEASE-3.0, > there is kernel panic. > Printed message is > > 'ufsspec_write .....' > > What is the reason of the panic? It looks like a filesystem type panic. I doubt it is SCSI-related. > I turned off tagged queue by setting DQue bit in mode page 10. > But the panic still existed. Turning off tagged queueing will only help your problem if it is load-related. (i.e., if load on the filesystem causes the panic, turning off tagged queueing will have the effect of decreasing the amount of simultaneous I/O you can do to the drive, and therefore decrease the load the filesystem.) > System up time is a day or two. And it's heavily loaded system. > > And I couldn't debug on dump image. > > www# gdb -k /kernel.981215.debug vmcore.0 > GDB is free software and you are welcome to distribute copies of it > under certain conditions; type "show copying" to see the conditions. > There is absolutely no warranty for GDB; type "show warranty" for details. > GDB 4.16 (i386-unknown-freebsd), > Copyright 1996 Free Software Foundation, Inc... > > "/kernel.981215.debug": not in executable format: File format not recognized > > kgdb could not open the exec-file, please check the name you used ! > (kgdb) > > How can I debug with aout image ? I'm not sure if 3.0-RELEASE shipped with an a.out verison of gdb. If it did, you could probably do something like: gdb -aout -k /kernel.981215.debug vmcore.0 If it didn't, you can fetch an a.out verison of gdb here: ftp://ftp.lemis.com/pub/vinum/gdb-aout Hopefully that will enable you get a good stack trace from your core dump and debugging kernel. Without a stack trace, it'll be difficult to track down the problem. Ken -- Kenneth Merry ken@plutotech.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199812160226.TAA64896>