From owner-freebsd-current Thu Jun 21 14: 1:34 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 CFF1737B407 for ; Thu, 21 Jun 2001 14:01:22 -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 f5LL1FI51749; Thu, 21 Jun 2001 14:01:15 -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: <200106212012.f5LKC3d73352@white.dogwood.com> Date: Thu, 21 Jun 2001 15:56:36 -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 21-Jun-01 Dave Cornejo wrote: > John Baldwin wrote: >> Is this on -current or -stable? If it's on -current, why did you ask on >> -questions? :) It looks like an interrupt problem however. > > When I asked on questions, I was of the belief that I had a hardware > problem and that it was not necessarily a -current issue. When I > later went back and installed 4.3 and it worked I then realized that I > had justification to post it on -current. Hey, at least I didn't > cross-post to questions, stable, scsi, and current! :) Ok, sounds good, just checking. :) Can you provide the output of mptable for this box? In the SMP case, -current does interrupt routing for PCI interrupts a bit differently, which might be a possible reason. Hmm, but you are getting interrupts eventually it seems. > I guess my next step is to try and trace through what's happening - > can you suggest a good place to start (like a routine to start > tracing), or is there anything I can do that might get more info for > the people that know what is going on? 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. -- 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