Date: Tue, 23 Mar 2004 09:53:24 +0100 From: =?ISO-8859-1?Q?S=F8ren_Schmidt?= <sos@DeepCore.dk> To: "Ketrien I. Saihr-Kesenchedra" <ketrien@error404.nls.net> Cc: current@freebsd.org Subject: Re: ata - interrupt seen but task queue stalled Message-ID: <405FFB04.1090005@DeepCore.dk> In-Reply-To: <6.0.3.0.2.20040323033603.0383c040@error404.nls.net> 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> <6.0.3.0.2.20040323033603.0383c040@error404.nls.net>
next in thread | previous in thread | raw e-mail | index | archive | help
Ketrien I. Saihr-Kesenchedra wrote: > At 02:49 AM 3/23/2004, Søren Schmidt wrote: > >> Didn't you say it was on a ROSB4 chipset ? The ROSB4 doesn't really >> support DMA on ATAPI devices, and has severe HW bugs that can cause >> problems with UDMA on disks as well.. > > > Yes, but this and sysctl's are a non-issue. The controller is set to > PIO4 and actually locked there. The drive itself doesn't do anything but > PIO4, being a slim CD-ROM. The OS resides on an ips. ie; This is a > genuinely new issue, and I can say with a fair degree of certainty that > it's something that's been changed. I can't break to debug either, but > the kernel configuration didn't change between working and non-working. Hmm, if you could provide us with a bit more information as to which date it worked at and which date it broke, and the output of dmesg, then we could do some qualified support, but without that, ENOCLUE... -- -Søren
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?405FFB04.1090005>