Re: SATA drive lock-up
It seems Derek Ragona wrote: 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 Ok, I'll try to get something semialr setup here and try to reproduce. 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. Hmm debugging this kind of problems most often requires hands on access to the HW, in some cases the ability to hook up measuring/test equipment greatly enhances the problem hunting (or is the only way to catch it). -Søren ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: SATA drive lock-up
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 Best regards, Putinas - Original Message - From: Soren Schmidt [EMAIL PROTECTED] To: Derek Ragona [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Sent: Saturday, September 20, 2003 10:07 Subject: Re: SATA drive lock-up It seems Derek Ragona wrote: I have a single SATA drive on an Adaptec 1210SA card. The drive will give a write error warning a few times, then will repeatedly give: ad4: timeout sending command=ca The only recovery is the reset switch, reboot single-user fsck, and then come back up in multiuser. These errors occur with disk access, but not with a predictable nature (not on large files, or small files, etc.) And you are on an uptodate -current ? If so I'd suspect HW ... -Søren ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: SATA drive lock-up
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 ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: SATA drive lock-up
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 ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: SATA drive lock-up
I couldn't make a kernel with 9/19 cvsuped. I downloaded and installed the 9/20 snapshot. That also wouldn't complete a buildworld without breaking with the hard drive error. I booted windows and stress tested the drive with all kinds of I/O. Not a hiccup. It isn't the hardware, it has to be the driver code under 5.1-current. -Derek At 02:53 PM 9/20/2003 -0500, Derek Ragona wrote: The 9/19 snapshot has the same issues. I will try to cvsup it and build a new kernel, if I can. -Derek At 05:36 AM 9/20/2003 -0500, Derek Ragona wrote: This was using the 9/18 snapshot, I tried to cvsup it to the most current, but the drive errors prevent the update. I just reloaded with the 9/19 snapshot, and will report if the error still exists. As for the hardware, it is all brand new hardware, and the system dual boots, the other OS has no issues. -Derek At 10:07 AM 9/20/2003 +0200, Soren Schmidt wrote: It seems Derek Ragona wrote: I have a single SATA drive on an Adaptec 1210SA card. The drive will give a write error warning a few times, then will repeatedly give: ad4: timeout sending command=ca The only recovery is the reset switch, reboot single-user fsck, and then come back up in multiuser. These errors occur with disk access, but not with a predictable nature (not on large files, or small files, etc.) And you are on an uptodate -current ? If so I'd suspect HW ... -Søren ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: SATA drive lock-up
On Mon, 2003-09-22 at 06:54, Derek Ragona wrote: I couldn't make a kernel with 9/19 cvsuped. I downloaded and installed the 9/20 snapshot. That also wouldn't complete a buildworld without breaking with the hard drive error. I booted windows and stress tested the drive with all kinds of I/O. Not a hiccup. It isn't the hardware, it has to be the driver code under 5.1-current. -Derek Okay, this is off the subject here on this. But I wanted to comment, Just because something 'works' in another OS doesn't mean it's working right. Just because my VIA KT133A chipset doesn't hiccup in Windows, doesn't mean it's not broken. Just because I get Data corruption in FreeBSD due to my KT133A chipset, doesn't mean it's FreeBSD's fault. Infact, you'll find FreeBSD and other accompany'ing OS's that are GNU/GPL/BSD licenesed to have a more strict driver set. They can show you things you wouldn't normally see in other OS's so to speak. As i said this is off topic, but saying But it works in Windows, is like saying But i'm a complete idiot who doesn't have a friggen clue how to help. Don't take this at all personally, it's just that i've hung out in the usenet groups, and irc channels long enuf to see the same thing over and over again. So I wanted to stop this trend before it started. From my personal experience, if you want something fixed with any Free OS you need to give the person who's fixing the problem as much information as possible. In otherwords, turning on all the debugging features, including DDB and trying to help them delve into it and find out what the exact problem really is. It maybe a problem with the controller, maybe the drive, maybe your system. At any rate, you're other OS *cough* does work properly. That doesn't mean that the driver in that other OS isn't correcting a hardware issue on the controller that was seen after manufactering. Infact it's quite common to see Defects after manufactering that the driver does correct. So please bear in mind a few things, One, everyone here does this for the Love of FreeBSD, Two, it's free. So in essence you get what you pay for, We do what we can to bring you the best damned Free OS possible. But we don't always have the resources to get all the information possible to create the drivers. Some Hardware Manufacter'ers are more then willing to give us specs and hardware to test their hardware and help us write drivers. Others are flat out do it yourself. Then you have even to the more extreme where they don't want us to write drivers. So, if you could please get as much information possible as to why? It may mean your system working properly and not. Sincerely, Scott M. Likens ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: SATA drive lock-up
I don't want to get into some flame war here. I am trying to provide what information I can. If Soren, or anyone else wants more debugging information I will be happy to do what I can to provide that information. I simply need them to tell me what and how to capture the information. As the system locks up, there is little ability at present to get any information beyond what is on the console. I offered some additional information as Soren had suggested I was having a hardware problem, which I am not. Again this is all new hardware, all shows no issues with diagnostic tests. As the Adaptec board I am using is based on Sil3112A controller, and I have heard from another user experiencing the same issue, I am simply trying to keep the information on this issue up to date. A couple weeks ago the OS wouldn't even load, a week later it does load. So while not all fixes are well publicized, I know there are ongoing code changes that do effect the disk subsystems. Yes FreeBSD is free. I'm not whining that it doesn't work on this drive and controller. Rather I am trying to report an issue, and follow-up on that issue, as this is new hardware. I have been using FreeBSD since 2.X. In my experience over the years and releases, problems do not get fixed if no one knows they exist. With 4.9 and 5.2 on the horizon, and more SATA drives and cards getting used it is reasonable to expect more users having problems with a Sil3112A based controller. -Derek At 07:35 AM 9/22/2003 -0700, Scott Likens wrote: On Mon, 2003-09-22 at 06:54, Derek Ragona wrote: I couldn't make a kernel with 9/19 cvsuped. I downloaded and installed the 9/20 snapshot. That also wouldn't complete a buildworld without breaking with the hard drive error. I booted windows and stress tested the drive with all kinds of I/O. Not a hiccup. It isn't the hardware, it has to be the driver code under 5.1-current. -Derek Okay, this is off the subject here on this. But I wanted to comment, Just because something 'works' in another OS doesn't mean it's working right. Just because my VIA KT133A chipset doesn't hiccup in Windows, doesn't mean it's not broken. Just because I get Data corruption in FreeBSD due to my KT133A chipset, doesn't mean it's FreeBSD's fault. Infact, you'll find FreeBSD and other accompany'ing OS's that are GNU/GPL/BSD licenesed to have a more strict driver set. They can show you things you wouldn't normally see in other OS's so to speak. As i said this is off topic, but saying But it works in Windows, is like saying But i'm a complete idiot who doesn't have a friggen clue how to help. Don't take this at all personally, it's just that i've hung out in the usenet groups, and irc channels long enuf to see the same thing over and over again. So I wanted to stop this trend before it started. From my personal experience, if you want something fixed with any Free OS you need to give the person who's fixing the problem as much information as possible. In otherwords, turning on all the debugging features, including DDB and trying to help them delve into it and find out what the exact problem really is. It maybe a problem with the controller, maybe the drive, maybe your system. At any rate, you're other OS *cough* does work properly. That doesn't mean that the driver in that other OS isn't correcting a hardware issue on the controller that was seen after manufactering. Infact it's quite common to see Defects after manufactering that the driver does correct. So please bear in mind a few things, One, everyone here does this for the Love of FreeBSD, Two, it's free. So in essence you get what you pay for, We do what we can to bring you the best damned Free OS possible. But we don't always have the resources to get all the information possible to create the drivers. Some Hardware Manufacter'ers are more then willing to give us specs and hardware to test their hardware and help us write drivers. Others are flat out do it yourself. Then you have even to the more extreme where they don't want us to write drivers. So, if you could please get as much information possible as to why? It may mean your system working properly and not. Sincerely, Scott M. Likens ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: SATA drive lock-up
It seems Derek Ragona wrote: I have a single SATA drive on an Adaptec 1210SA card. The drive will give a write error warning a few times, then will repeatedly give: ad4: timeout sending command=ca The only recovery is the reset switch, reboot single-user fsck, and then come back up in multiuser. These errors occur with disk access, but not with a predictable nature (not on large files, or small files, etc.) And you are on an uptodate -current ? If so I'd suspect HW ... -Søren ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: SATA drive lock-up
Since Adapted 1210SA is based on Sil3112A controller I still also have same problem what I reported few weeks before with my onboard sil3112a controller. tested tonight with fresh kernel - Original Message - From: Soren Schmidt [EMAIL PROTECTED] To: Derek Ragona [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Sent: Saturday, September 20, 2003 10:07 AM Subject: Re: SATA drive lock-up It seems Derek Ragona wrote: I have a single SATA drive on an Adaptec 1210SA card. The drive will give a write error warning a few times, then will repeatedly give: ad4: timeout sending command=ca The only recovery is the reset switch, reboot single-user fsck, and then come back up in multiuser. These errors occur with disk access, but not with a predictable nature (not on large files, or small files, etc.) And you are on an uptodate -current ? If so I'd suspect HW ... -Søren ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: SATA drive lock-up
This was using the 9/18 snapshot, I tried to cvsup it to the most current, but the drive errors prevent the update. I just reloaded with the 9/19 snapshot, and will report if the error still exists. As for the hardware, it is all brand new hardware, and the system dual boots, the other OS has no issues. -Derek At 10:07 AM 9/20/2003 +0200, Soren Schmidt wrote: It seems Derek Ragona wrote: I have a single SATA drive on an Adaptec 1210SA card. The drive will give a write error warning a few times, then will repeatedly give: ad4: timeout sending command=ca The only recovery is the reset switch, reboot single-user fsck, and then come back up in multiuser. These errors occur with disk access, but not with a predictable nature (not on large files, or small files, etc.) And you are on an uptodate -current ? If so I'd suspect HW ... -Søren ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: SATA drive lock-up
The 9/19 snapshot has the same issues. I will try to cvsup it and build a new kernel, if I can. -Derek At 05:36 AM 9/20/2003 -0500, Derek Ragona wrote: This was using the 9/18 snapshot, I tried to cvsup it to the most current, but the drive errors prevent the update. I just reloaded with the 9/19 snapshot, and will report if the error still exists. As for the hardware, it is all brand new hardware, and the system dual boots, the other OS has no issues. -Derek At 10:07 AM 9/20/2003 +0200, Soren Schmidt wrote: It seems Derek Ragona wrote: I have a single SATA drive on an Adaptec 1210SA card. The drive will give a write error warning a few times, then will repeatedly give: ad4: timeout sending command=ca The only recovery is the reset switch, reboot single-user fsck, and then come back up in multiuser. These errors occur with disk access, but not with a predictable nature (not on large files, or small files, etc.) And you are on an uptodate -current ? If so I'd suspect HW ... -Søren ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: SATA drive lock-up
The system died in buildworld, this time it fell into the debugger. spec_getpages(ad4s1d) I/O read failure (error=5) -Derek At 02:53 PM 9/20/2003 -0500, Derek Ragona wrote: The 9/19 snapshot has the same issues. I will try to cvsup it and build a new kernel, if I can. -Derek At 05:36 AM 9/20/2003 -0500, Derek Ragona wrote: This was using the 9/18 snapshot, I tried to cvsup it to the most current, but the drive errors prevent the update. I just reloaded with the 9/19 snapshot, and will report if the error still exists. As for the hardware, it is all brand new hardware, and the system dual boots, the other OS has no issues. -Derek At 10:07 AM 9/20/2003 +0200, Soren Schmidt wrote: It seems Derek Ragona wrote: I have a single SATA drive on an Adaptec 1210SA card. The drive will give a write error warning a few times, then will repeatedly give: ad4: timeout sending command=ca The only recovery is the reset switch, reboot single-user fsck, and then come back up in multiuser. These errors occur with disk access, but not with a predictable nature (not on large files, or small files, etc.) And you are on an uptodate -current ? If so I'd suspect HW ... -Søren ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
