Date: Sat, 28 Apr 2001 11:50:42 -0700 From: Cy Schubert - ITSD Open Systems Group <Cy.Schubert@uumail.gov.bc.ca> To: cjm88@home.com Cc: UEDA Hiroyuki <ueda@netforest.co.jp>, freebsd-stable@FreeBSD.ORG Subject: Re: 4.3-RELEASE kernel freeze(message dumped by ahc driver?) Message-ID: <200104281851.f3SIpG103311@cwsys.cwsent.com> In-Reply-To: Your message of "Sat, 28 Apr 2001 14:15:25 EDT." <3AEB08BD.BD686DBE@home.com>
next in thread | previous in thread | raw e-mail | index | archive | help
In message <3AEB08BD.BD686DBE@home.com>, cjm88@home.com writes: > I have seen similar messages on adaptec hardware. It was quite mystifying > because at first I thought there might [edited] I'm not sure whether this is relevant or not. My problem when I had it appeared to be different. You may want to take a look at the following, http://www.scsifaq.org/dev_probs.html When I purchased my PIII/933 on an ASUS CUSL2-C motherboard about 2-3 weeks ago, replacing an aging P120, my system would on occasion hang. There were no messages to syslog. I was able to reproduce it almost at will with a lot of I/O to my Zip 100 drive, though any amount of I/O to any drive on the SCSI bus would randomly produce the hang. Then I discovered the URL above. Not wanting to spend $$$ on a new PCI SCSI adapter, fiddled around with the BIOS settings, finally disabling the PCI 2.1 in the BIOS, which I assume limits the MB to the PCI 2.0 protocol. Since disabling the PCI 2.1 setting in the BIOS I've experienced no hangs. The system's been extremely stable. Regards, Phone: (250)387-8437 Cy Schubert Fax: (250)387-5766 Team Leader, Sun/Alpha Team Internet: Cy.Schubert@osg.gov.bc.ca Open Systems Group, ITSD, ISTA Province of BC > be some hardware issues on the system I was trying to resurect and the time > required to reproduce the error seemed > to be inversely proportional to the amount of disk IO taking place. I ran > hardware diagnostics yet they came up > clean. I ran seagate's scsi diagnostics (seatools) which you can download fo > r > free and they also came > up clean. Eventually I was able to track down the documentation for the host > adapter and discovered that the scsi > bus was not properly terminated on the motherboard. Specifically the wide > terminaters should have been removed. > I did this, reinstalled the OS and the system ran clean. Note that I had to > perform a reinstall... it appeared > that some data corruption had crept in. Note also that while I was chasing > this issue down I permutated > through about 4 or 5 different versions of FreeBSD (4.2 and 4.3) and it seeme > d > some where more sensitive to the > issue than others. > > Hope this helps. > > C > > UEDA Hiroyuki wrote: > > > Thanks for your reply. > > > > On Sat, 28 Apr 2001 18:46:47 +0200 > > Thomas Seck <tmseck@web.de> wrote: > > ; > > > > I used FreeBSD 4.3-RC(1), and cvsuped with RELENG_4_3_0_RELEASE on > > > > 27th Apr, did make world, make kernel, and then reboot on 28th. I > > > > thought there was no problem, but 1 day later, kernel logged following > > ; > > > I have a PR open (kern/26880, unexpected busfree errors), cocerning > > > similar problems with an Adaptec 19160 and Quantum Atlas V discs. > > > Let's see what Justin T. Gibbs says about it. > > > > I have checked your PR. Yes, my SCSI card is Adaptec AHA-2940U, but > > the HDD is made by IBM... Have you never seen such messages after > > updating HDD firmware ? If so, I will try to update HDD firmware(but I > > think it's dangerous for me...). > > > > ------------- > > UEDA Hiroyuki <ueda@netforest.co.jp> > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-stable" in the body of the message > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200104281851.f3SIpG103311>