Date: Mon, 16 Aug 2004 10:09:10 +0200 From: =?ISO-8859-1?Q?S=F8ren_Schmidt?= <sos@DeepCore.dk> To: Marc van Kempen <marc@bowtie.nl> Cc: freebsd-current@freebsd.org Subject: Re: ATA write-dma interrupt was seen but timeout fired LBA=53346288 Message-ID: <41206BA6.80908@DeepCore.dk> In-Reply-To: <200408160810.00366.marc@bowtie.nl> References: <200408160810.00366.marc@bowtie.nl>
next in thread | previous in thread | raw e-mail | index | archive | help
Marc van Kempen wrote: > 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? Something is holding on to one of the taskqueues blocking the request processesing. I'm not sure what caused it but backstepping ATA doesn't make things work at least, suggesting to look somewhere else... For me at least network seems to be troublesome, if I exclude as much network related code as possible in the config, I can resume just fine. YMMV as usual... -Søren
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?41206BA6.80908>