From owner-freebsd-current@FreeBSD.ORG Tue Mar 23 00:53:38 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3E96C16A4CE for ; Tue, 23 Mar 2004 00:53:38 -0800 (PST) Received: from spider.deepcore.dk (cpe.atm2-0-53484.0x50a6c9a6.abnxx9.customer.tele.dk [80.166.201.166]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1995B43D45 for ; Tue, 23 Mar 2004 00:53:37 -0800 (PST) (envelope-from sos@DeepCore.dk) Received: from DeepCore.dk (sos.deepcore.dk [194.192.25.130]) by spider.deepcore.dk (8.12.11/8.12.10) with ESMTP id i2N8rON0093430; Tue, 23 Mar 2004 09:53:29 +0100 (CET) (envelope-from sos@DeepCore.dk) Message-ID: <405FFB04.1090005@DeepCore.dk> Date: Tue, 23 Mar 2004 09:53:24 +0100 From: =?ISO-8859-1?Q?S=F8ren_Schmidt?= User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.6b) Gecko/20040126 Thunderbird/0.4 X-Accept-Language: en-us, en MIME-Version: 1.0 To: "Ketrien I. Saihr-Kesenchedra" 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> In-Reply-To: <6.0.3.0.2.20040323033603.0383c040@error404.nls.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit X-mail-scanned: by DeepCore Virus & Spam killer v1.4 cc: current@freebsd.org Subject: Re: ata - interrupt seen but task queue stalled X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 23 Mar 2004 08:53:38 -0000 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