Date: Tue, 2 Dec 2003 17:34:08 -0500 (EST) From: "Aaron Myles Landwehr" <aaron@snaphat.com> To: "J S Goldberg" <jsg@san.rr.com> Cc: questions@freebsd.org Subject: Re: 4.9 ATA hangs with 2 ata drives Message-ID: <33552.68.33.78.247.1070404448.squirrel@mail.snaphat.com> In-Reply-To: <p0521060fbbf19833ee43@[192.168.27.23]> References: <p0521060bbbf11ed81a27@[192.168.27.23]><33052.68.33.78.247.1070332853.squirrel@mail.snaphat.com> <p0521060fbbf19833ee43@[192.168.27.23]>
next in thread | previous in thread | raw e-mail | index | archive | help
try turning off dma on the affected drive...see if it boots correctly > At 21:40 -0500 12/01/2003, Aaron Myles Landwehr wrote: >>I have the same problem with my asus p4s8x mobo on freebsd 4.9 and >>prior....If i disable dma the cd will boot.; >>5.1 works correctly(with dma enabled). >>from the cases i've seen...they all include an ASUS motherboard... >>-aaron<aaron@snaphat.com> > > I didn't have any trouble with the cd booting. I've got it > set up as my secondary ata master. It sees my ad0 fine, and > then hangs before showing the drive type for ad1. > > This post had ad0 hang using a GA - 8SG800 motherboard. > Maybe also an nforce2 chipset? > http://www.freebsd.org/cgi/getmsg.cgi?fetch=2472274+2474865+/usr/local/www/db/text/2003/freebsd-questions/20031109.freebsd-questions > > I could swear there were others, but the only ones that I could > find quickly were about cdrom problems, not hard drives. > >>... 4.9 hangs on boot with: ... >> > ad1: READ command timeout tag=0 serv=0 - resetting >>> ata0: resetting devices >>> >>> I've seen what looks like similar problems in the archives (e.g., >>> http://docs.freebsd.org/cgi/mid.cgi?188200406.20031109073901). >>> It seems to happen on various motherboards and disk configurations. >> > I wanted to provide another datapoint for configurations. >>> > > tks > j >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?33552.68.33.78.247.1070404448.squirrel>