Skip site navigation (1)Skip section navigation (2)
Date:      24 Aug 2002 01:01:42 +0930
From:      "Daniel O'Connor" <doconnor@gsoft.com.au>
To:        "Patrick O'Reilly" <bsd@perimeter.co.za>
Cc:        ivan_alb@agava.com, freebsd-hackers@FreeBSD.ORG
Subject:   Re: Kernel Panic = System crash 8 times in 4 days
Message-ID:  <1030116703.410.4.camel@chowder.dons.net.au>
In-Reply-To: <044301c24a9f$6627e020$b50d030a@PATRICK>
References:  <028401c24a95$dbacc270$b50d030a@PATRICK> <3D6619B0.3080708@agava.com> <036401c24a99$db5c5bb0$b50d030a@PATRICK> <3D66258F.7080506@agava.com>  <044301c24a9f$6627e020$b50d030a@PATRICK>

next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, 2002-08-23 at 21:49, Patrick O'Reilly wrote:
> > What about this message:
> > ad2: UDMA ICRC error reading fsbn 0 (ad2 bn 0; cn 0 tn 0 sn 0)
> retrying
> > ad2: UDMA ICRC error reading fsbn 0 (ad2 bn 0; cn 0 tn 0 sn 0)
> retrying
> > ad2: UDMA ICRC error reading fsbn 0 (ad2 bn 0; cn 0 tn 0 sn 0)
> retrying
> > ad2: UDMA ICRC error reading fsbn 0 (ad2 bn 0; cn 0 tn 0 sn 0) falling
> > back to PIO mode

> I know my hardware is not the best.  I will be installing the correct
> IDE cable in the second controller as soon as I can get to the site.

I had this problem..
I think it is because the ATA code doesn't detect your cable type
properly (or the controller?)

I worked around it by doing 'atacontrol mode 0 udma33 xxx'

--
Daniel O'Connor software and network engineer
for Genesis Software - http://www.gsoft.com.au
"The nice thing about standards is that there
are so many of them to choose from."
  -- Andrew Tanenbaum
GPG Fingerprint - 9A8C 569F 685A D928 5140  AE4B 319B 41F4 5D17 FDD5


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1030116703.410.4.camel>