From owner-freebsd-current Fri Jun 22 9:38:47 2001 Delivered-To: freebsd-current@freebsd.org Received: from meow.osd.bsdi.com (meow.osd.bsdi.com [204.216.28.88]) by hub.freebsd.org (Postfix) with ESMTP id 0AA1B37B409 for ; Fri, 22 Jun 2001 09:38:44 -0700 (PDT) (envelope-from jhb@FreeBSD.org) Received: from laptop.baldwin.cx (john@jhb-laptop.osd.bsdi.com [204.216.28.241]) by meow.osd.bsdi.com (8.11.3/8.11.2) with ESMTP id f5MGcdI69665; Fri, 22 Jun 2001 09:38:39 -0700 (PDT) (envelope-from jhb@FreeBSD.org) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <200106220507.f5M57TT94014@white.dogwood.com> Date: Fri, 22 Jun 2001 09:42:22 -0700 (PDT) From: John Baldwin To: Dave Cornejo Subject: Re: SCSI hangs w/SuperMicro 6010H Cc: freebsd-current@FreeBSD.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On 22-Jun-01 Dave Cornejo wrote: > John Baldwin wrote: >> Actuually, KTR is your friend here. :) Read the ktr(4) manpage, then >> compile a >> kernel with KTR_MASK and KTR_COMPILE set to KTR_INTR|KTR_PROC. Then when it >> hangs, break into DDB and look at the longs via 'show ktr' to see if you can >> locate any interrutps coming in from ahc0 or ahc1. > > Okay - fired up the box, built a kernel off of a 6/18 source snapshot, > and it hangs in about the same place - however what I get that as soon > as I touch a key to invoke the debugger from the console, it continues > merrily booting and I can't break into DDB until way past the > problem. In my mind this kind of confirms something is busted in the > interrupts. Hrmm, perhaps you are getting an interrupt storm from ahc. Ok, try this: find the ahc driver's interrupt handler, and add a printf. Then see if the printf fires while the machine is hung. > Tried looking back through the show ktr output and I'm not 100% clear > on what it all means - I guess I'm interested in the ithread stuff and > the only thing I ever see is swi6: tty:sio+ in the trace buffer > besides what appears to be normal process rescheduling (?) which is > mostly idle task time... Unfortunately, clock interrupts can fill the trace buffer up, yes. :( If rolling back the source tree gets you a working kernel, then you might want to do a binary search using date tags to narrow down what commit actually broke things on your box. -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message