Date: Thu, 18 Sep 2003 18:38:25 +0200 (CEST) From: Soren Schmidt <sos@spider.deepcore.dk> To: w@dream.vg Cc: freebsd-current@FreeBSD.ORG Subject: Re: ATAng still problematic Message-ID: <200309181638.h8IGcPox025307@spider.deepcore.dk> In-Reply-To: <20030918155125.GC22643@student.agh.edu.pl>
next in thread | previous in thread | raw e-mail | index | archive | help
It seems Jan Srzednicki wrote: > > > First of all, the drive still does not get detected properly. Funny > > > thing is that after some playing with atacontrol attach/detach, it > > > finally gets detected. And later on, it is normally detected, before. > > > Same scenario happened like 3 times with ATAng and newer and newer > > > kernels. I don't know whether some device hints or anything are just > > > updated; yet, I didn't have _any_ drive detection problems with ATAold. > > > > > > The problem is with the second drive. There's still some randomness in > > > it, as it gets undetected from time to time. > > > > Try the below patch and let me know if that changes anything.. > > It seems that things have changed a bit (the drive gets detected more > often), but still, it's not perfect. Perfect ? hmm - I'd settle for works :) Anyhow, what I need to be able to tell what may be going on, is that you boot verbose and get me the output from dmesg from a boot that found all device, and from a boot that missed. > Anyway, here's backtrace for atapicam panic I've mentioned. It's > triggered by: No idea, atapicam is not my area, maybe thomas@ can help... -Søren
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200309181638.h8IGcPox025307>