Date: Tue, 23 Mar 2004 03:38:46 -0500 From: "Ketrien I. Saihr-Kesenchedra" <ketrien@error404.nls.net> To: =?iso-8859-1?Q?S=F8ren?= Schmidt <sos@DeepCore.dk> Cc: current@freebsd.org Subject: Re: ata - interrupt seen but task queue stalled Message-ID: <6.0.3.0.2.20040323033603.0383c040@error404.nls.net> In-Reply-To: <405FEC11.7050001@DeepCore.dk> References: <6.0.3.0.2.20040323011610.03842e70@mail.nls.net> <20040323062914.GL4875@camelot.theinternet.com.au> <6.0.3.0.2.20040323023317.03842be0@error404.nls.net> <405FEC11.7050001@DeepCore.dk>
next in thread | previous in thread | raw e-mail | index | archive | help
At 02:49 AM 3/23/2004, S=F8ren Schmidt wrote: >Didn't you say it was on a ROSB4 chipset ? The ROSB4 doesn't really=20 >support DMA on ATAPI devices, and has severe HW bugs that can cause=20 >problems with UDMA on disks as well.. Yes, but this and sysctl's are a non-issue. The controller is set to PIO4=20 and actually locked there. The drive itself doesn't do anything but PIO4,=20 being a slim CD-ROM. The OS resides on an ips. ie; This is a genuinely new= =20 issue, and I can say with a fair degree of certainty that it's something=20 that's been changed. I can't break to debug either, but the kernel=20 configuration didn't change between working and non-working. -Ketrien I. Saihr-Kesenchedra <ketrien AT error404 DOT nls DOT net> # Maybe this world is another planet's hell. --Aldous Huxley Feanor smiles, "We, of course, are enlightened and s/Maybe t/T"=20
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?6.0.3.0.2.20040323033603.0383c040>