From owner-freebsd-current@FreeBSD.ORG Tue Aug 17 07:29:32 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 1D9C516A4CE; Tue, 17 Aug 2004 07:29:32 +0000 (GMT) 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 70FAA43D67; Tue, 17 Aug 2004 07:29:31 +0000 (GMT) (envelope-from sos@DeepCore.dk) Received: from [194.192.25.143] (laptop.deepcore.dk [194.192.25.143]) by spider.deepcore.dk (8.12.11/8.12.10) with ESMTP id i7H7TFLb042203; Tue, 17 Aug 2004 09:29:16 +0200 (CEST) (envelope-from sos@DeepCore.dk) Message-ID: <4121B3B8.9030204@DeepCore.dk> Date: Tue, 17 Aug 2004 09:28:56 +0200 From: =?ISO-8859-1?Q?S=F8ren_Schmidt?= User-Agent: Mozilla Thunderbird 0.7.2 (X11/20040802) X-Accept-Language: en-us, en MIME-Version: 1.0 To: marc@bowtie.nl References: <200408160810.00366.marc@bowtie.nl> <200408162319.i7GNJB0J027625@Espresso.NEEBU.Net> <20040816235200.GB2335@host10.meck.bowtie.nl> In-Reply-To: <20040816235200.GB2335@host10.meck.bowtie.nl> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: quoted-printable cc: freebsd-current@freebsd.org cc: rwatson@freebsd.org cc: Jake Khuon Subject: Re: ATA write-dma interrupt was seen but timeout fired LBA=53346288 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, 17 Aug 2004 07:29:32 -0000 Marc van Kempen wrote: >>It was very frustrating to not have reliable suspend. However, I think= I >>might have solved it. Do you have a CDROM (or similar) device attached= ? >> >>I added "atacontrol detach 1" to /etc/rc.suspend to detach the CDROM dr= ive >>before suspending. Likewise, I added a complementary "atacontrol attac= h 1" >>in /etc/rc.resume. Since doing that, I have not seen the interrupt >>problems. I do notice now that shortly before the re-attachment kicks = in >>after coming back from suspend, I will see: >> >>Aug 16 15:45:02 Mocha kernel: stray irq15 >> > I see exactly the same thing (from some quick testing), manually attach= ing > detaching the cdrom drive (actually dvd/cdrom-writer) makes suspend/res= ume > work reliably! That does not fix it here at least :( I cannot tell if I get any stray irq's since the laptop locks before it=20 gets so far as to switch on the display... >>I'm not sure if this is normal or is an indication of some weird IRQ st= orm.=20 >>At anyrate, detaching and reattaching during the suspend/resume cycle s= eems >>to damp it and stablised the whole ATA subsystem. An interrupt storm would be bad and make the system seem to lockup in=20 various places, maybe we are seeing that but on different irq's due to=20 how the HW is setup etc.. -S=F8ren