Date: Mon, 22 Dec 2003 09:55:43 -0800 From: Frank McConnell <fmc@reanimators.org> To: "Oivind H. Danielsen" <oivind.danielsen@kopek.net> Cc: freebsd-stable@freebsd.org Subject: Re: WRITE command timeout Message-ID: <200312221755.hBMHthcf091011@daemonweed.reanimators.org> In-Reply-To: <NMEPLAHDNAPMGKOIJMLLIEFNCAAA.oivind.danielsen@kopek.net> (Oivind H. Danielsen's message of "Sat, 20 Dec 2003 19:07:41 %2B0100") References: <NMEPLAHDNAPMGKOIJMLLIEFNCAAA.oivind.danielsen@kopek.net>
next in thread | previous in thread | raw e-mail | index | archive | help
"Oivind H. Danielsen" <oivind.danielsen@kopek.net> wrote: > Dec 18 15:15:39 <> /kernel: ad0: WRITE command timeout tag=0 serv=0 - > resetting > Dec 19 15:03:23 <> /kernel: ad0: READ command timeout tag=0 serv=0 - > resetting I have recently (Friday, today) seen these messages with a new box running 4.8-RELEASE-p14. Replacing the hard disk and cable did not help. The key in this case appears to be the kernel configuration, which included options SMP and APIC but not HTT. GENERIC works fine, GENERIC + SMP + APIC fails, GENERIC + SMP + APIC + HTT appears to work thus far (makes it through a buildworld without provoking a timeout). 4.8-RELEASE-p14 on Intel SE7501CW2 with two 2.4GHz Xeons and 512MB RAM. No idea whether this will help you; looking at your kernel config file, I have my doubts (doesn't look like you are using SMP). Maybe it will be a clue to someone though. -Frank McConnell
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200312221755.hBMHthcf091011>