Date: Tue, 6 Nov 2012 08:50:39 +0000 From: Tom Lislegaard <Tom.Lislegaard@proact.no> To: 'Andriy Gapon' <avg@FreeBSD.org> Cc: "freebsd-acpi@FreeBSD.org" <freebsd-acpi@FreeBSD.org>, "freebsd-stable@FreeBSD.org" <freebsd-stable@FreeBSD.org> Subject: RE: 9-Stable panic: resource_list_unreserve: can't find resource Message-ID: <E8A24BEFDC390C4491718DEE8A9C4F209220E2@Semail03.proact.local> In-Reply-To: <5097F24D.7040206@FreeBSD.org> References: <E8A24BEFDC390C4491718DEE8A9C4F2091F824@Semail03.proact.local> <509172F6.2040400@FreeBSD.org> <E8A24BEFDC390C4491718DEE8A9C4F2091FC33@Semail03.proact.local> <5092F209.7090803@FreeBSD.org> <E8A24BEFDC390C4491718DEE8A9C4F20920DD1@Semail03.proact <5093BECC.1030709@FreeBSD.org> <E8A24BEFDC390C4491718DEE8A9C4F20921BAC@Semail03.proact.local> <50979BCD.3060000@FreeBSD.org> <E8A24BEFDC390C4491718DEE8A9C4F20921C47@Semail03.proact.local> <5097CB27.8040802@FreeBSD.org> <E8A24BEFDC390C4491718DEE8A9C4F20921C6A@Semail03.proact.local> <5097F24D.7040206@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
> -----Original Message----- > From: Andriy Gapon [mailto:avg@FreeBSD.org] > Sent: 5. november 2012 18:08 > To: Tom Lislegaard > Cc: freebsd-stable@FreeBSD.org; freebsd-acpi@FreeBSD.org > Subject: Re: 9-Stable panic: resource_list_unreserve: can't find resource >=20 > on 05/11/2012 16:52 Tom Lislegaard said the following: > > > > > >> -----Original Message----- > >> From: Andriy Gapon [mailto:avg@FreeBSD.org] > >> Sent: 5. november 2012 15:21 > >> To: Tom Lislegaard > >> Cc: freebsd-stable@FreeBSD.org; freebsd-acpi@FreeBSD.org > >> Subject: Re: 9-Stable panic: resource_list_unreserve: can't find > >> resource > >> > >> on 05/11/2012 15:54 Tom Lislegaard said the following: > >>> Here's the distribution from running devd over 40 minutes > >>> > >>> 589 Processing event '!system=3DACPI subsystem=3DPROCESSOR type=3D\= \_PR_.CPU0 notify=3D0x81' > >>> 590 Processing event '!system=3DACPI subsystem=3DPROCESSOR type=3D\= \_PR_.CPU1 notify=3D0x81' > >>> 590 Processing event '!system=3DACPI subsystem=3DPROCESSOR type=3D\= \_PR_.CPU2 notify=3D0x81' > >>> 590 Processing event '!system=3DACPI subsystem=3DPROCESSOR type=3D\= \_PR_.CPU3 notify=3D0x81' > >>> 590 Processing event '!system=3DACPI subsystem=3DPROCESSOR type=3D\= \_PR_.CPU4 notify=3D0x81' > >>> 590 Processing event '!system=3DACPI subsystem=3DPROCESSOR type=3D\= \_PR_.CPU5 notify=3D0x81' > >>> 590 Processing event '!system=3DACPI subsystem=3DPROCESSOR type=3D\= \_PR_.CPU6 notify=3D0x81' > >>> 590 Processing event '!system=3DACPI subsystem=3DPROCESSOR type=3D\= \_PR_.CPU7 notify=3D0x81' > >>> 1 Processing event '!system=3DDEVFS subsystem=3DCDEV type=3DCREAT= E cdev=3Ddsp4.1' > >>> 1 Processing event '!system=3DDEVFS subsystem=3DCDEV type=3DCREAT= E cdev=3Dpts/2' > >>> 1 Processing event '!system=3DDEVFS subsystem=3DCDEV type=3DCREAT= E cdev=3Dvboxdrv0' > >>> 1 Processing event '!system=3DDEVFS subsystem=3DCDEV type=3DDESTR= OY cdev=3Ddsp4.1' > >>> 1 Processing event '!system=3DDEVFS subsystem=3DCDEV type=3DDESTR= OY cdev=3Dvboxdrv0' > >>> > >>> Any use in running it over a longer period of time? > >> > >> Very interesting. > >> So the processors get _CST change notifications rather frequently, > >> but there is no obvious source/cause for them... > >> > >> Could you please send to me acpidump -dt output or upload it somewhere= and post a link? > > > > Here you go > > > > https://dl.dropbox.com/u/13263820/acpidump.txt >=20 > So, ACPI platform on your machine sends 0x81 notification for processors = objects each time "_PSR" > method of AC Adapter / Power Source device is queried. > There could be a number of reason to invoke the method - either AC line s= tatus queries from userland > (some battery / line monitoring program/applet) or internal ACPI notifica= tions. >=20 > Are you willing to go as far as recompiling your kernel with 'options AC= PI_DEBUG' > to get to the bottom of this issue? > If yes, then please do that and also add the following lines to loader.co= nf: > debug.acpi.layer=3D"ACPI_EVENTS ACPI_AC_ADAPTER" > debug.acpi.level=3D"ACPI_LV_INFO" > I would be interested in all periodically occurring ACPI debug messages (= after boot is finished). >=20 No problem, I'm happy to assist in debugging this. Enabling the acpi debugging quickly fills the kernel message buffer, but it= seems to be the same set of messages=20 repeating again and again so I think this is representative https://dl.dropbox.com/u/13263820/debug_dmesg.txt And, btw, thanks for your efforts. -tom > I suspect that the ACPI platform and/or embedded controller send too many= notifications when they are > not strictly necessary. > Maybe there is a BIOS update for your machine? >=20 > In any case, I am starting to work on a patch that should fix this proble= m without resorting to any > special configuration. > -- > Andriy Gapon
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?E8A24BEFDC390C4491718DEE8A9C4F209220E2>