Date: Mon, 05 Nov 2012 19:07:25 +0200 From: Andriy Gapon <avg@FreeBSD.org> To: Tom Lislegaard <Tom.Lislegaard@proact.no> Cc: freebsd-acpi@FreeBSD.org, freebsd-stable@FreeBSD.org Subject: Re: 9-Stable panic: resource_list_unreserve: can't find resource Message-ID: <5097F24D.7040206@FreeBSD.org> In-Reply-To: <E8A24BEFDC390C4491718DEE8A9C4F20921C6A@Semail03.proact.local> 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>
next in thread | previous in thread | raw e-mail | index | archive | help
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=ACPI subsystem=PROCESSOR type=\\_PR_.CPU0 notify=0x81' >>> 590 Processing event '!system=ACPI subsystem=PROCESSOR type=\\_PR_.CPU1 notify=0x81' >>> 590 Processing event '!system=ACPI subsystem=PROCESSOR type=\\_PR_.CPU2 notify=0x81' >>> 590 Processing event '!system=ACPI subsystem=PROCESSOR type=\\_PR_.CPU3 notify=0x81' >>> 590 Processing event '!system=ACPI subsystem=PROCESSOR type=\\_PR_.CPU4 notify=0x81' >>> 590 Processing event '!system=ACPI subsystem=PROCESSOR type=\\_PR_.CPU5 notify=0x81' >>> 590 Processing event '!system=ACPI subsystem=PROCESSOR type=\\_PR_.CPU6 notify=0x81' >>> 590 Processing event '!system=ACPI subsystem=PROCESSOR type=\\_PR_.CPU7 notify=0x81' >>> 1 Processing event '!system=DEVFS subsystem=CDEV type=CREATE cdev=dsp4.1' >>> 1 Processing event '!system=DEVFS subsystem=CDEV type=CREATE cdev=pts/2' >>> 1 Processing event '!system=DEVFS subsystem=CDEV type=CREATE cdev=vboxdrv0' >>> 1 Processing event '!system=DEVFS subsystem=CDEV type=DESTROY cdev=dsp4.1' >>> 1 Processing event '!system=DEVFS subsystem=CDEV type=DESTROY cdev=vboxdrv0' >>> >>> 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 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 status queries from userland (some battery / line monitoring program/applet) or internal ACPI notifications. Are you willing to go as far as recompiling your kernel with 'options ACPI_DEBUG' to get to the bottom of this issue? If yes, then please do that and also add the following lines to loader.conf: debug.acpi.layer="ACPI_EVENTS ACPI_AC_ADAPTER" debug.acpi.level="ACPI_LV_INFO" I would be interested in all periodically occurring ACPI debug messages (after boot is finished). 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? In any case, I am starting to work on a patch that should fix this problem 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?5097F24D.7040206>