Date: Fri, 23 Aug 2002 17:44:41 +0200 From: "Patrick O'Reilly" <bsd@perimeter.co.za> To: "Daniel O'Connor" <doconnor@gsoft.com.au> Cc: freebsd-hackers@freebsd.org Subject: Re: Kernel Panic = System crash 8 times in 4 days Message-ID: <06d301c24abc$0088fd40$b50d030a@PATRICK> References: <028401c24a95$dbacc270$b50d030a@PATRICK><3D6619B0.3080708@agava.com> <036401c24a99$db5c5bb0$b50d030a@PATRICK><3D66258F.7080506@agava.com> <044301c24a9f$6627e020$b50d030a@PATRICK> <1030116703.410.4.camel@chowder.dons.net.au>
next in thread | previous in thread | raw e-mail | index | archive | help
From: "Daniel O'Connor" <doconnor@gsoft.com.au>
> > 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,
thanks for this.
See this:
---
# atacontrol list
ATA channel 0:
Master: ad0 <Maxtor 2B020H1/WAK21R90> ATA/ATAPI rev 7
Slave: ad1 <Maxtor 4D040H2/DAH017K0> ATA/ATAPI rev 6
ATA channel 1:
Master: ad2 <Maxtor 4D040H2/DAH017K0> ATA/ATAPI rev 6
Slave: no device present
# atacontrol mode 0
Master = UDMA100
Slave = UDMA100
# atacontrol mode 1
Master = PIO4
Slave = ???
---
This correctly reflects my current setup. Now, the disk on ata1-Master
is identical to that on ata0-Slave (as you can see), but the cable on
ata1 is an old cable. I have picked up a new cable, but have not been
able to get to the site to install it yet.
Do you think that it will make the box more stable if I explicitly
issue:
# atacontrol mode 0 udma33 xxx
or should it perhaps be
# atacontrol mode 0 xxx udma33
Patrick.
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?06d301c24abc$0088fd40$b50d030a>