From owner-freebsd-current@FreeBSD.ORG Mon Aug 16 08:09:52 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 E261816A4CE for ; Mon, 16 Aug 2004 08:09:52 +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 425BB43D39 for ; Mon, 16 Aug 2004 08:09:52 +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 i7G89TeL029160; Mon, 16 Aug 2004 10:09:34 +0200 (CEST) (envelope-from sos@DeepCore.dk) Message-ID: <41206BA6.80908@DeepCore.dk> Date: Mon, 16 Aug 2004 10:09:10 +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 van Kempen References: <200408160810.00366.marc@bowtie.nl> In-Reply-To: <200408160810.00366.marc@bowtie.nl> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: quoted-printable X-mail-scanned: by DeepCore Virus & Spam killer v1.4 cc: freebsd-current@freebsd.org 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: Mon, 16 Aug 2004 08:09:53 -0000 Marc van Kempen wrote: > Hi, >=20 > Since two weeks I get this warning after resuming my laptop (IBM Thinkp= ad=20 > R40), this is with acpi enabled on a -current of yesterday (15 Aug), so= me=20 > relevant settings: >=20 > hw.acpi.sleep_button_state=3DS3 > hw.acpi.lid_switch_state=3DS3 > hw.syscons.sc_no_suspend_vtswitch=3D1 > hw.acpi.reset_video=3D0 >=20 > In a time frame of about two or three weeks this setup worked wonderful= ly,=20 > everything worked when suspending/resuming. I could even enable glx aga= in. >=20 > After I resume I get these warnings: >=20 > ATA write-dma interrupt was seen but timeout fired LBA=3D53346288 > ATA write-dma interrupt was seen but timeout fired LBA=3D53346288 > ATA write-dma interrupt was seen but taskqueue stalled LBA=3D53346288 >=20 > This basically results in the harddisk being unaccessible and the syste= ms=20 > hangs eventually. Rebooting does not work because the harddisk can't be= =20 > synced, etc. >=20 > Does anyone know what is going on? Something is holding on to one of the taskqueues blocking the request=20 processesing. I'm not sure what caused it but backstepping ATA doesn't=20 make things work at least, suggesting to look somewhere else... For me at least network seems to be troublesome, if I exclude as much=20 network related code as possible in the config, I can resume just fine. YMMV as usual... -S=F8ren