From owner-freebsd-acpi@FreeBSD.ORG Tue Nov 6 08:50:50 2012 Return-Path: Delivered-To: freebsd-acpi@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 79809AEF; Tue, 6 Nov 2012 08:50:50 +0000 (UTC) (envelope-from Tom.Lislegaard@proact.no) Received: from am1outboundpool.messaging.microsoft.com (am1ehsobe005.messaging.microsoft.com [213.199.154.208]) by mx1.freebsd.org (Postfix) with ESMTP id BB85A8FC08; Tue, 6 Nov 2012 08:50:48 +0000 (UTC) Received: from mail118-am1-R.bigfish.com (10.3.201.250) by AM1EHSOBE009.bigfish.com (10.3.204.29) with Microsoft SMTP Server id 14.1.225.23; Tue, 6 Nov 2012 08:50:47 +0000 Received: from mail118-am1 (localhost [127.0.0.1]) by mail118-am1-R.bigfish.com (Postfix) with ESMTP id 89D6F460257; Tue, 6 Nov 2012 08:50:47 +0000 (UTC) X-Forefront-Antispam-Report: CIP:212.214.215.133; KIP:(null); UIP:(null); IPV:NLI; H:semtaout01.proact.se; RD:semtaout01.proact.se; EFVD:NLI X-SpamScore: -7 X-BigFish: VPS-7(zzbb2dI542M1432Izz1de0h1d18h1202h1d1ah1d2ahzz8275bh8275dhz2dh668h839h944hd25hf0ah1220h1288h12a5h12a9h12bdh137ah13b6h1441h1504h1537h153bh1155h) Received: from mail118-am1 (localhost.localdomain [127.0.0.1]) by mail118-am1 (MessageSwitch) id 1352191844493342_22348; Tue, 6 Nov 2012 08:50:44 +0000 (UTC) Received: from AM1EHSMHS010.bigfish.com (unknown [10.3.201.246]) by mail118-am1.bigfish.com (Postfix) with ESMTP id 5793D4A005F; Tue, 6 Nov 2012 08:50:44 +0000 (UTC) Received: from semtaout01.proact.se (212.214.215.133) by AM1EHSMHS010.bigfish.com (10.3.207.110) with Microsoft SMTP Server id 14.1.225.23; Tue, 6 Nov 2012 08:50:40 +0000 Received: from Semail04.proact.local (unknown [10.7.1.58]) by semtaout01.proact.se (Postfix) with ESMTP id 4E87A5727C; Tue, 6 Nov 2012 09:50:40 +0100 (CET) Received: from SEMAIL03.proact.local ([fe80::a52b:385d:b44f:ecb9]) by Semail04.proact.local ([fe80::885:6e64:c1e6:dcf1%20]) with mapi id 14.02.0318.001; Tue, 6 Nov 2012 09:50:39 +0100 From: Tom Lislegaard To: 'Andriy Gapon' Subject: RE: 9-Stable panic: resource_list_unreserve: can't find resource Thread-Topic: 9-Stable panic: resource_list_unreserve: can't find resource Thread-Index: Ac23UHFrRe/nHcv4QJaCSOXSiMVayQAP8Y0AACFOYqAAF8a9gAAYYgXwAAYhBQAAk9ux8P///B6A//+/I1CAAHlQgP//5ozAgABIH4D//unQQA== Date: Tue, 6 Nov 2012 08:50:39 +0000 Message-ID: References: <509172F6.2040400@FreeBSD.org> <5092F209.7090803@FreeBSD.org> <50979BCD.3060000@FreeBSD.org> <5097CB27.8040802@FreeBSD.org> <5097F24D.7040206@FreeBSD.org> In-Reply-To: <5097F24D.7040206@FreeBSD.org> Accept-Language: en-US, sv-SE Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.7.1.59] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-OriginatorOrg: proact.no Cc: "freebsd-acpi@FreeBSD.org" , "freebsd-stable@FreeBSD.org" X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 06 Nov 2012 08:50:50 -0000 > -----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