Date: Thu, 19 Aug 2004 14:21:14 -0400 From: Anish Mistry <mistry.7@osu.edu> To: freebsd-current@freebsd.org Cc: nate@root.org Subject: Re: Panic on resume ACPI / ATA / UMA Message-ID: <200408191421.21519.mistry.7@osu.edu> In-Reply-To: <200408191344.31672.mistry.7@osu.edu> References: <200408190130.27386.mistry.7@osu.edu> <200408190917.39482.sam@errno.com> <200408191344.31672.mistry.7@osu.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
=2D----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Thursday 19 August 2004 01:44 pm, Anish Mistry wrote: > On Thursday 19 August 2004 12:17 pm, Sam Leffler wrote: > > On Wednesday 18 August 2004 10:30 pm, Anish Mistry wrote: > > > -----BEGIN PGP SIGNED MESSAGE----- > > > Hash: SHA1 > > > > > > With CURRENT as of a few hours ago (12:00 AM EST) I'm getting the > > > following panic below which then results in a reboot without creating= a > > > core dump. How to repeat on my laptop: > > > 1) suspend (close lid) > > > 2) resume (open lid) > > > - - At this point the lid switch stops working so to suspend again... > > > 3) suspend (acpiconf -s 3) > > > 4) resume (press power button) > > > > > > ASL: > > > http://am-productions.biz/docs/littleguy.asl.gz > > > DMESG: > > > http://am-productions.biz/docs/dmesg.txt.gz > > > > > > After a few seconds the following appears: > > > > > > ad0: WARNING - WRITE_DMA interrupt was seen but timeout fired > > > LBA=3D12086925 ad0: WARNING - READ_DMA interrupt was seen but timeout > > > fired LBA=3D13004061 ad0: WARNING - READ_DMA interrupt was seen but > > > timeout fired LBA=3D13004061 acpi_cmbat1: battery initialization fail= ed, > > > giving up ad0: WARNING - READ_DMA interrupt was seen but taskqueue > > > stalled LBA=3D13004061 Slab at 0xc15e4f70, freei 7 =3D 0. > > > panic: Duplicate free of item 0xc15e439c from zone 0xc0c44c60(g_bio) > > > > I hit identical behaviour w/o suspend-resume on upgrading an ibm t41p (= it > > panics on boot). The upgrade was, I believe, from an 8/10 kernel to an > > 8/18 kernel so some commit to the ata code in that timeframe is likely > > the cause. Looking through the logs this appears most likely: > > > > cvs commit: src/sys/dev/ata ata-all.c ata-lowlevel.c ata-queue.c > > > > From: SXren Schmidt <sos@FreeBSD.org> > > To: src-committers@FreeBSD.org, cvs-src@FreeBSD.org, cvs-all@FreeBSD.org > > Date: Monday 02:32:35 am > > > > sos 2004-08-16 09:32:35 UTC > > > > FreeBSD src repository > > > > Modified files: > > sys/dev/ata ata-all.c ata-lowlevel.c ata-queue.c > > Log: > > Improve (hopefully) on the workaround code for devices that doesn't > > interrupt when command is done, ie some ATAPI CD drives with no > > media loaded. > > > > Don't know if backing out this change requires undoing other stuff. > > > > Sam > > Backing out that commit fixes the ATA panic on resume for me, but the lid > switch still isn't working after resume which is an ACPI issue so I'll po= st > that separately. > S=F8ren, is there any other info that I need to provide than the dmesg ab= ove? Well, guess I was just lucky, since it just happened again even with that=20 commit backed out :(. =2D --=20 Anish Mistry =2D----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (FreeBSD) iD8DBQFBJO+gxqA5ziudZT0RAvVfAJwOiUJTgpntDGPRLm+PMPVF89kg/ACfRkaq 4MyYKXdo2MiotpSGqcbbONI=3D =3DYypG =2D----END PGP SIGNATURE-----
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200408191421.21519.mistry.7>