Date: Sun, 20 Sep 1998 00:16:27 -0700 From: Manfred Antar <mantar@netcom.com> To: KATO Takenori <kato@ganko.eps.nagoya-u.ac.jp>, gibbs@narnia.plutotech.com Cc: current@FreeBSD.ORG Subject: Re: [CAM] Broken tagged queuing drive? Message-ID: <199809200716.AAA00304@pozo.pozo.com> In-Reply-To: <19980920154842T.kato@gneiss.eps.nagoya-u.ac.jp> References: <Your message of "Sat, 19 Sep 1998 22:42:38 -0600 (MDT)"<199809200442.WAA06694@narnia.plutotech.com> <199809200442.WAA06694@narnia.plutotech.com>
next in thread | previous in thread | raw e-mail | index | archive | help
At 03:48 PM 9/20/98 +0900, KATO Takenori wrote: >"Justin T. Gibbs" <gibbs@narnia.plutotech.com> wrote: > >> I believe I've found the cause of this panic. I would appreciate it if >> you could test to see if the next revision of aic7xxx.c survives the >> timeout. > >The panic went away. > > >> My guess is that the SAMSUNG blows away other pending transactions when >> it sends a queue full message. You may want to try setting maxtags >> to a value that will avoid the queue full response (perhaps 32 or 31). > >The value 32 works without problem. > >Thanks! > I just built a kernel with this new code. The machine just goes into a panic on boot right after ffs_mountfs: superblock updated The machine is a Intel PR440FX SMP-pentiumpro 200mhz DPT controller -->da0 softupdates on all partitions and built in adaptec 7880 connected to a CDROM I can't get to the debugger as it just keeps scrolling. something about boot called on cpu0 and lock something. I can't read it as it is scrolling too fast. This is with current sources A kernel built just before the aic7xxx.c commit worked fine. Manfred ============================== || mantar@netcom.com || || pozo@infinex.com || || Ph. (415) 681-6235 || ============================== To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199809200716.AAA00304>