Date: Sun, 30 Nov 2003 12:55:44 -0500 From: Joe Marcus Clarke <marcus@marcuscom.com> To: Soren Schmidt <sos@spider.deepcore.dk> Cc: Will Andrews <will@csociety.org> Subject: Re: Western Digital WD360GD SATA disk on -CURRENT Message-ID: <1070214944.98573.4.camel@shumai.marcuscom.com> In-Reply-To: <200311300852.hAU8qwej014854@spider.deepcore.dk> References: <200311300852.hAU8qwej014854@spider.deepcore.dk>
next in thread | previous in thread | raw e-mail | index | archive | help
--=-QQCOj8LytdcQqK6o7gI0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable On Sun, 2003-11-30 at 03:52, Soren Schmidt wrote: > It seems Joe Marcus Clarke wrote: > > I agree. I really needed to be up and running ASAP, so I opted for the > > new controller. S=F8ren, if you're listening, and need an SiI controll= er > > for testing, you're free to have mine. Else, I can keep it and test it > > as needed (I can put a test drive on it). >=20 > I have both the old one with the errata and the new one without so > thanks for the offer but it might be betterused somewhere else. As soon as my RMA drive arrives, I can do more testing. What would be beneficial? Backing down the drivers as I had planned, or is there something better I can do to help? >=20 > > I have a basic time line. Everything worked fine until I upgraded on > > November 18 at 02:23 UTC. I had a 160 GB Seagate SATA drive running on > > the same chipset for about a month before that. As soon as I rebooted > > on the new kernel, everything went south. Until S=F8ren told me about = the > > buggy chipset, I was going to back my ATA drivers back to November 11, > > 2003 00:00 UTC, and see if that helped. That was right before a big > > change went into the driver. >=20 > I dont recall doing any major changes in that timeline, what exact > large changes are you talking about ?? By "large change," I mean a change that affected a few files, that happened before things went south. According to the CVS log: "Centralise mode setting. Instead of doing it in all subdrivers, do it in ata-all.c where it belongs." If this still failed, I was going to keep working back until I found exactly where things started to fail. Joe >=20 > -S=F8ren --=20 PGP Key : http://www.marcuscom.com/pgp.asc --=-QQCOj8LytdcQqK6o7gI0 Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.3 (FreeBSD) iD8DBQA/yi8gb2iPiv4Uz4cRAo2mAJ4qXo14jaspj3mwT/0xFT2RC0Ui9QCfYNKk Znmy76kTucTdIlpoQiOAF0c= =oVPv -----END PGP SIGNATURE----- --=-QQCOj8LytdcQqK6o7gI0--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1070214944.98573.4.camel>