Date: Tue, 23 Sep 2003 19:06:20 -0500 From: Derek Ragona <derek@computinginnovations.com> To: Soren Schmidt <sos@spider.deepcore.dk>, Putinas <pilkis@gmx.net> Cc: freebsd-current@freebsd.org Subject: Re: SATA drive lock-up Message-ID: <5.2.1.1.2.20030923185208.012f2240@www.computinginnovations.com> In-Reply-To: <200309231551.h8NFpXcj021932@spider.deepcore.dk> References: <004c01c381dc$f27aace0$1e64a8c0@spotripoli.local>
next in thread | previous in thread | raw e-mail | index | archive | help
Søren,
My setup is as follows:
Maxtor 6Y120MO 120GB SATA drive
Adaptec Serial ATA RAID 1210SA
Intel® Desktop Board D845GEBV2
1GB RAM
1.7 GHz Celeron CPU
The motherboard has the latest P17 BIOS.
The system has a teac 52x CD-ROM as the Master ATA device on the
motherboards primary IDE controller. The secondary IDE controller is
disabled (I disabled this to reduce conflicts.)
The Maxtor drive is on the only drive connected to the adaptec SATA card.
There is a standard floppy disk installed as well.
I loaded the 9/22 snapshot, and after a couple drives was able to cvsup and
rebuild to current. I am running the GENERIC kernel.
If there is some way to get more debugging information, please let me
know. If you want the ATA subsystem rebuilt differently for more
debugging, I'm happy to do that as well. If you want access to the box, I
will give you that too.
-Derek
At 05:51 PM 9/23/2003 +0200, Soren Schmidt wrote:
>It seems Putinas wrote:
> > Hi all,
> > Inspired with all the FreeBSD is free software , windows and buggy hardware
> > and blabla I realize what maybe I could do more to help solve this problem.
> > I made small research on my computer and I find out what till the cvsup
> date
> > 2003.08.24.00.00.00 till ATAng commitment to the source my SATA Sil3112A
> > working fine.
> > After this date I always get WRITE_DMA recovered from missing interrupt
> > error
> > after more or less intensive input output with harddisk subsystem , and
> > after I/O error and so on ...
> > My bet is what in this case buggy is not hardware .. at least this bug
> > didn't
> > show up until 25 August
>
>Well, it works here with pure SATA drives at least, do you use real
>SATA disks on PATA ones with SATA dongles ?
>
>So long that I cant reproduce the problem its hard to fix...
>
>-Søren
>_______________________________________________
>freebsd-current@freebsd.org mailing list
>http://lists.freebsd.org/mailman/listinfo/freebsd-current
>To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?5.2.1.1.2.20030923185208.012f2240>
