From owner-freebsd-current@FreeBSD.ORG Mon Aug 16 06:10:06 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 49DB216A4CE for ; Mon, 16 Aug 2004 06:10:06 +0000 (GMT) Received: from ctb-mesg6.saix.net (ctb-mesg6.saix.net [196.25.240.78]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8C10D43D45 for ; Mon, 16 Aug 2004 06:10:05 +0000 (GMT) (envelope-from marc@bowtie.nl) Received: from [192.168.0.104] (tbnb-101-245.telkomadsl.co.za [165.165.101.245]) by ctb-mesg6.saix.net (Postfix) with ESMTP id 7DE36160AB3; Mon, 16 Aug 2004 08:10:02 +0200 (SAST) From: Marc van Kempen To: freebsd-current@freebsd.org Date: Mon, 16 Aug 2004 08:10:00 +0200 User-Agent: KMail/1.6.2 MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Message-Id: <200408160810.00366.marc@bowtie.nl> Subject: 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 06:10:06 -0000 Hi, Since two weeks I get this warning after resuming my laptop (IBM Thinkpad R40), this is with acpi enabled on a -current of yesterday (15 Aug), some relevant settings: hw.acpi.sleep_button_state=S3 hw.acpi.lid_switch_state=S3 hw.syscons.sc_no_suspend_vtswitch=1 hw.acpi.reset_video=0 In a time frame of about two or three weeks this setup worked wonderfully, everything worked when suspending/resuming. I could even enable glx again. After I resume I get these warnings: ATA write-dma interrupt was seen but timeout fired LBA=53346288 ATA write-dma interrupt was seen but timeout fired LBA=53346288 ATA write-dma interrupt was seen but taskqueue stalled LBA=53346288 This basically results in the harddisk being unaccessible and the systems hangs eventually. Rebooting does not work because the harddisk can't be synced, etc. Does anyone know what is going on? Regards, Marc.