From owner-freebsd-acpi@FreeBSD.ORG Sun Nov 4 14:55:25 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 C468B294 for ; Sun, 4 Nov 2012 14:55:25 +0000 (UTC) (envelope-from webmaster@babymama.sk) Received: from isp3.d2u.sk (isp3.d2u.sk [93.184.68.183]) by mx1.freebsd.org (Postfix) with ESMTP id 7AD4F8FC17 for ; Sun, 4 Nov 2012 14:55:25 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by isp3.d2u.sk (Postfix) with ESMTP id D096E9C379B for ; Sun, 4 Nov 2012 15:55:18 +0100 (CET) X-Virus-Scanned: Debian amavisd-new at isp3.d2u.sk X-Amavis-Alert: BAD HEADER SECTION, Improper use of control character (char 0D hex): From: Ryan James \r Received: from isp3.d2u.sk ([127.0.0.1]) by localhost (isp3.d2u.sk [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id of08x+zyTOez for ; Sun, 4 Nov 2012 15:55:18 +0100 (CET) Received: by isp3.d2u.sk (Postfix, from userid 33) id 238FD9C3160; Sun, 4 Nov 2012 15:55:05 +0100 (CET) To: freebsd-acpi@freebsd.org Subject: Contact Me Urgently From: Ryan James MIME-Version: 1.0 Content-Type: text/plain Content-Transfer-Encoding: 8bit Message-Id: <20121104145505.238FD9C3160@isp3.d2u.sk> Date: Sun, 4 Nov 2012 15:55:05 +0100 (CET) X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list Reply-To: bierberhincom@gmail.com List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 04 Nov 2012 14:55:25 -0000 I NEED YOUR ASSISTANCE FOR INVESTMENT PROJECT, It is true we did not know each Other before I contacted you but I’m convinced that you can handle this my MULTIMILLION Project as a Foreign Business Partner with me. In order to protect our interest and dignity would like you to write me through this email. Best Wishes, Personal Assistance, James David From owner-freebsd-acpi@FreeBSD.ORG Sun Nov 4 14:58:04 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 DE13333D for ; Sun, 4 Nov 2012 14:58:04 +0000 (UTC) (envelope-from webmaster@babymama.sk) Received: from isp3.d2u.sk (isp3.d2u.sk [93.184.68.183]) by mx1.freebsd.org (Postfix) with ESMTP id 979608FC12 for ; Sun, 4 Nov 2012 14:58:04 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by isp3.d2u.sk (Postfix) with ESMTP id E27B19C393B for ; Sun, 4 Nov 2012 15:58:03 +0100 (CET) X-Virus-Scanned: Debian amavisd-new at isp3.d2u.sk X-Amavis-Alert: BAD HEADER SECTION, Improper use of control character (char 0D hex): From: James David \r Received: from isp3.d2u.sk ([127.0.0.1]) by localhost (isp3.d2u.sk [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id AioCwChEt+5u for ; Sun, 4 Nov 2012 15:58:03 +0100 (CET) Received: by isp3.d2u.sk (Postfix, from userid 33) id DCD3E9C37AA; Sun, 4 Nov 2012 15:57:49 +0100 (CET) To: freebsd-acpi@freebsd.org Subject: Contact Me Urgently From: James David MIME-Version: 1.0 Content-Type: text/plain Content-Transfer-Encoding: 8bit Message-Id: <20121104145749.DCD3E9C37AA@isp3.d2u.sk> Date: Sun, 4 Nov 2012 15:57:49 +0100 (CET) X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list Reply-To: bierberhincom@gmail.com List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 04 Nov 2012 14:58:05 -0000 I NEED YOUR ASSISTANCE FOR INVESTMENT PROJECT, It is true we did not know each Other before I contacted you but I’m convinced that you can handle this my MULTIMILLION Project as a Foreign Business Partner with me. In order to protect our interest and dignity would like you to write me through this email. Best Wishes, Personal Assistance, James David From owner-freebsd-acpi@FreeBSD.ORG Mon Nov 5 08:35:04 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 D8D85B44 for ; Mon, 5 Nov 2012 08:35:04 +0000 (UTC) (envelope-from demelier.david@gmail.com) Received: from mail-pb0-f54.google.com (mail-pb0-f54.google.com [209.85.160.54]) by mx1.freebsd.org (Postfix) with ESMTP id AB9998FC0C for ; Mon, 5 Nov 2012 08:35:04 +0000 (UTC) Received: by mail-pb0-f54.google.com with SMTP id rp8so3950838pbb.13 for ; Mon, 05 Nov 2012 00:35:04 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=hIl6l9kM5g9aJGXGaMJncBApGS1h4iJaK7jLkrF46Lw=; b=TbNWSiInFHI91XXBp2x29z+fk5quasbk7zJNLb2kDLvike7Cecsx0snNn6XWutnOvo SL0HDTzqOpglPkQ2mHKeATXE/6nekOI8BD9aPIXn8Vhu9+9Gw4pDr5uV+Wd87TTD/Dm6 5EGFHkp5COBsZrolVhUFRAgxZGbe2rkGCJ296imociM3/m3+SIMODvMYTk3tAHv0Y9p2 73Ae5BBsMkSBI54W6Nro6Egdhh1Ot45HXjOWZEwi8Fkx3gOVpIohlOpuKlrLgj4pWBnk 6xph8bxrvrvv83IbnbFJ4sR5mA2xVlrrW3v2/Ef6rISrcuOB/9hGswTAVDcsHUKchdzl MAMw== MIME-Version: 1.0 Received: by 10.66.77.201 with SMTP id u9mr26683857paw.6.1352104504050; Mon, 05 Nov 2012 00:35:04 -0800 (PST) Received: by 10.66.80.36 with HTTP; Mon, 5 Nov 2012 00:35:04 -0800 (PST) Date: Mon, 5 Nov 2012 09:35:04 +0100 Message-ID: Subject: ACPI Regression, battery does not update From: David Demelier To: freebsd-acpi@freebsd.org Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 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: Mon, 05 Nov 2012 08:35:04 -0000 Hello, Since I've updated to 9.1-* (RC3 now) my battery does not update, my laptop is HP Probook 4510s, in fact if I unplug the AC adaptor, the remaining capacity of the battery will not discharge and stays as the remaining capacity from when I unplugged the adaptor. (If that could be real... :)) And sometimes the battery is updated after a while like, when the laptop battery change to 40% but then I won't see 39%, 38%, and so on.. I think I have the same problem as: http://www.freebsd.org/cgi/query-pr.cgi?pr=162859 -- Demelier David From owner-freebsd-acpi@FreeBSD.ORG Mon Nov 5 10:26:55 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 CDD8A9B9; Mon, 5 Nov 2012 10:26:55 +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 239718FC0A; Mon, 5 Nov 2012 10:26:53 +0000 (UTC) Received: from mail55-am1-R.bigfish.com (10.3.201.239) by AM1EHSOBE009.bigfish.com (10.3.204.29) with Microsoft SMTP Server id 14.1.225.23; Mon, 5 Nov 2012 10:26:47 +0000 Received: from mail55-am1 (localhost [127.0.0.1]) by mail55-am1-R.bigfish.com (Postfix) with ESMTP id 6B079440061; Mon, 5 Nov 2012 10:26:47 +0000 (UTC) X-Forefront-Antispam-Report: CIP:195.159.75.198; KIP:(null); UIP:(null); IPV:NLI; H:nomtaout01.proact.no; RD:nomtaout01.proact.no; EFVD:NLI X-SpamScore: -7 X-BigFish: VPS-7(zzbb2dI542M1432Izz1de0h1d18h1202h1d1ah1d2ahzz8275dhz2dh668h839h944hd25hf0ah1220h1288h12a5h12a9h12bdh137ah13b6h1441h1504h1537h153bh1155h) Received: from mail55-am1 (localhost.localdomain [127.0.0.1]) by mail55-am1 (MessageSwitch) id 1352111204573544_25782; Mon, 5 Nov 2012 10:26:44 +0000 (UTC) Received: from AM1EHSMHS016.bigfish.com (unknown [10.3.201.248]) by mail55-am1.bigfish.com (Postfix) with ESMTP id 8028A18007C; Mon, 5 Nov 2012 10:26:44 +0000 (UTC) Received: from nomtaout01.proact.no (195.159.75.198) by AM1EHSMHS016.bigfish.com (10.3.207.154) with Microsoft SMTP Server id 14.1.225.23; Mon, 5 Nov 2012 10:26:37 +0000 Received: from Semail04.proact.local (outside.proact.se [212.214.215.3]) by nomtaout01.proact.no (Postfix) with ESMTP id ACB195DD85; Mon, 5 Nov 2012 11:26:37 +0100 (MET) 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; Mon, 5 Nov 2012 11:26:37 +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/nHcv4QJaCSOXSiMVayQAP8Y0AACFOYqAAF8a9gAAYYgXwAAYhBQAAk9ux8A== Date: Mon, 5 Nov 2012 10:26:35 +0000 Message-ID: References: <509172F6.2040400@FreeBSD.org> <5092F209.7090803@FreeBSD.org> In-Reply-To: <5093BECC.1030709@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: Mon, 05 Nov 2012 10:26:56 -0000 > -----Original Message----- > From: Andriy Gapon [mailto:avg@FreeBSD.org] > Sent: 2. november 2012 13:39 > 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 02/11/2012 11:56 Tom Lislegaard said the following: > > The machine is usually connected to a docking station and I believe the= power is very stable. I > sometimes take it home and connect it to a different powersupply and sees= the same behavior with > panics there. Panics can occur while I'm at the machine working, or if I = leave the machine idle for > some time I find it has paniced/rebooted when I come back. > > The time of panic seems totally random and I can't correlate this to an= y particular activity like > cronjobs, etc. >=20 > I see. Could you please try setting debug.acpi.max_threads=3D1 in /boot/= loader.conf, reboot and see if > that makes any difference? >=20 > -- > Andriy Gapon It does make a difference. I've had the machine running over the week-end, = and haven't had a crash in 56 hours. After applying the setting I get some errors on reboot, no idea if they are= harmful in any way (none that I have notced): AcpiOsExecute: failed to enqueue task, consider increasing the debug.acpi.m= ax_tasks tunable ACPI Error: Method parse/execution failed [\\PNOT] (Node 0xfffffe00052e6400= ), AE_NO_MEMORY (20110527/psparse-560) ACPI Error: Method parse/execution failed [\\_SB_.AC__._PSR] (Node 0xfffffe= 00052f57c0), AE_NO_MEMORY (20110527/psparse-560) The same messages repeats 6 times -tom From owner-freebsd-acpi@FreeBSD.ORG Mon Nov 5 10:58:28 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 20F09A45; Mon, 5 Nov 2012 10:58:28 +0000 (UTC) (envelope-from avg@FreeBSD.org) Received: from citadel.icyb.net.ua (citadel.icyb.net.ua [212.40.38.140]) by mx1.freebsd.org (Postfix) with ESMTP id 34DBF8FC08; Mon, 5 Nov 2012 10:58:26 +0000 (UTC) Received: from porto.starpoint.kiev.ua (porto-e.starpoint.kiev.ua [212.40.38.100]) by citadel.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id MAA28185; Mon, 05 Nov 2012 12:58:23 +0200 (EET) (envelope-from avg@FreeBSD.org) Received: from localhost ([127.0.0.1]) by porto.starpoint.kiev.ua with esmtp (Exim 4.34 (FreeBSD)) id 1TVKNq-0004Nm-Va; Mon, 05 Nov 2012 12:58:23 +0200 Message-ID: <50979BCD.3060000@FreeBSD.org> Date: Mon, 05 Nov 2012 12:58:21 +0200 From: Andriy Gapon User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:16.0) Gecko/20121030 Thunderbird/16.0.2 MIME-Version: 1.0 To: Tom Lislegaard Subject: Re: 9-Stable panic: resource_list_unreserve: can't find resource References: <509172F6.2040400@FreeBSD.org> <5092F209.7090803@FreeBSD.org> In-Reply-To: X-Enigmail-Version: 1.4.5 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit 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: Mon, 05 Nov 2012 10:58:28 -0000 on 05/11/2012 12:26 Tom Lislegaard said the following: >> -----Original Message----- >> From: Andriy Gapon [mailto:avg@FreeBSD.org] >> I see. Could you please try setting debug.acpi.max_threads=1 in /boot/loader.conf, reboot and see if >> that makes any difference? > > It does make a difference. I've had the machine running over the week-end, and haven't had a crash in 56 hours. > > After applying the setting I get some errors on reboot, no idea if they are harmful in any way (none that I have notced): > > AcpiOsExecute: failed to enqueue task, consider increasing the debug.acpi.max_tasks tunable > ACPI Error: Method parse/execution failed [\\PNOT] (Node 0xfffffe00052e6400), AE_NO_MEMORY (20110527/psparse-560) > ACPI Error: Method parse/execution failed [\\_SB_.AC__._PSR] (Node 0xfffffe00052f57c0), AE_NO_MEMORY (20110527/psparse-560) > > The same messages repeats 6 times Thank you for the test! Try to set debug.acpi.max_tasks to 128 or even higher to get rid of the new ACPI errors. Additionally I would like to ask you to do the following test. Please stop devd and then run it (as root) from command line as such devd -D -d. Please check what event are reported by devd. In particular I am interested in ACAD events, but all high frequency events are important. Thanks! -- Andriy Gapon From owner-freebsd-acpi@FreeBSD.ORG Mon Nov 5 11:06:31 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 2CA96CDB for ; Mon, 5 Nov 2012 11:06:31 +0000 (UTC) (envelope-from owner-bugmaster@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:1900:2254:206c::16:87]) by mx1.freebsd.org (Postfix) with ESMTP id ED1268FC0C for ; Mon, 5 Nov 2012 11:06:30 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.5/8.14.5) with ESMTP id qA5B6UjC001068 for ; Mon, 5 Nov 2012 11:06:30 GMT (envelope-from owner-bugmaster@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.5/8.14.5/Submit) id qA5B6Ucc001066 for freebsd-acpi@FreeBSD.org; Mon, 5 Nov 2012 11:06:30 GMT (envelope-from owner-bugmaster@FreeBSD.org) Date: Mon, 5 Nov 2012 11:06:30 GMT Message-Id: <201211051106.qA5B6Ucc001066@freefall.freebsd.org> X-Authentication-Warning: freefall.freebsd.org: gnats set sender to owner-bugmaster@FreeBSD.org using -f From: FreeBSD bugmaster To: freebsd-acpi@FreeBSD.org Subject: Current problem reports assigned to freebsd-acpi@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: Mon, 05 Nov 2012 11:06:31 -0000 Note: to view an individual PR, use: http://www.freebsd.org/cgi/query-pr.cgi?pr=(number). The following is a listing of current problems submitted by FreeBSD users. These represent problem reports covering all versions including experimental development code and obsolete releases. S Tracker Resp. Description -------------------------------------------------------------------------------- o kern/171305 acpi [acpi] acpi_tz0: _CRT value is absurd, ignored (256.0C o kern/164329 acpi [acpi] hw.acpi.thermal.tz0.temperature shows strange v o kern/163268 acpi [acpi_hp] fix driver detach in absence of CMI o kern/162859 acpi [acpi] ACPI battery/acline monitoring partialy working o kern/161715 acpi [acpi] Dell E6520 doesn't resume after ACPI suspend o kern/161713 acpi [acpi] Suspend on Dell E6520 o kern/160838 acpi [acpi] ACPI Battery Monitor Non-Functional o kern/160419 acpi [acpi_thermal] acpi_thermal kernel thread high CPU usa o kern/158689 acpi [acpi] value of sysctl hw.acpi.thermal.polling_rate ne o kern/154955 acpi [acpi] Keyboard or ACPI doesn't work on Lenovo S10-3 o kern/152438 acpi [acpi]: patch to acpi_asus(4) to add extra sysctls for o kern/152098 acpi [acpi] Lenovo T61p does not resume o i386/146715 acpi [acpi] Suspend works, resume not on a HP Probook 4510s o kern/145306 acpi [acpi]: Can't change brightness on HP ProBook 4510s o i386/143798 acpi [acpi] shutdown problem with SiS K7S5A o kern/143420 acpi [acpi] ACPI issues with Toshiba o kern/142009 acpi [acpi] [panic] Panic in AcpiNsGetAttachedObject o kern/139088 acpi [acpi] ACPI Exception: AE_AML_INFINITE_LOOP error o amd64/138210 acpi [acpi] acer aspire 5536 ACPI problems (S3, brightness, o kern/137042 acpi [acpi] hp laptop's lcd not wakes up after suspend to r o i386/136008 acpi [acpi] Dell Vostro 1310 will not shutdown (Requires us o kern/132602 acpi [acpi] ACPI Problem with Intel SS4200: System does not p kern/128634 acpi [patch] fix acpi_asus(4) in asus a6f laptop o bin/126162 acpi [acpi] ACPI autoload failed : loading required module o kern/123039 acpi [acpi] ACPI AML_BUFFER_LIMIT errors during boot a i386/122887 acpi [panic] [atkbdc] 7.0-RELEASE on IBM HS20 panics immed s kern/112544 acpi [acpi] [patch] Add High Precision Event Timer Driver f o kern/105537 acpi [acpi] problems in acpi on HP Compaq nc6320 o kern/91594 acpi [acpi] FreeBSD > 5.4 w/ACPI fails to detect Intel Pro/ o kern/73823 acpi [request] acpi / power-on by timer support o kern/56024 acpi ACPI suspend drains battery while in S3 31 problems total. From owner-freebsd-acpi@FreeBSD.ORG Mon Nov 5 13:55:04 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 C6761C03; Mon, 5 Nov 2012 13:55:04 +0000 (UTC) (envelope-from Tom.Lislegaard@proact.no) Received: from db3outboundpool.messaging.microsoft.com (db3ehsobe004.messaging.microsoft.com [213.199.154.142]) by mx1.freebsd.org (Postfix) with ESMTP id 167758FC17; Mon, 5 Nov 2012 13:55:03 +0000 (UTC) Received: from mail2-db3-R.bigfish.com (10.3.81.232) by DB3EHSOBE005.bigfish.com (10.3.84.25) with Microsoft SMTP Server id 14.1.225.23; Mon, 5 Nov 2012 13:54:56 +0000 Received: from mail2-db3 (localhost [127.0.0.1]) by mail2-db3-R.bigfish.com (Postfix) with ESMTP id D0BD34402DE; Mon, 5 Nov 2012 13:54:56 +0000 (UTC) X-Forefront-Antispam-Report: CIP:195.159.75.198; KIP:(null); UIP:(null); IPV:NLI; H:nomtaout01.proact.no; RD:nomtaout01.proact.no; EFVD:NLI X-SpamScore: -10 X-BigFish: VPS-10(zzbb2dI103dK542M1432Izz1de0h1d18h1202h1d1ah1d2ahzz8275dhz2dh668h839h944hd25hf0ah1220h1288h12a5h12a9h12bdh137ah13b6h1441h1504h1537h153bh1155h) Received: from mail2-db3 (localhost.localdomain [127.0.0.1]) by mail2-db3 (MessageSwitch) id 1352123679394215_26717; Mon, 5 Nov 2012 13:54:39 +0000 (UTC) Received: from DB3EHSMHS007.bigfish.com (unknown [10.3.81.245]) by mail2-db3.bigfish.com (Postfix) with ESMTP id 5DCEB2C0045; Mon, 5 Nov 2012 13:54:39 +0000 (UTC) Received: from nomtaout01.proact.no (195.159.75.198) by DB3EHSMHS007.bigfish.com (10.3.87.107) with Microsoft SMTP Server id 14.1.225.23; Mon, 5 Nov 2012 13:54:38 +0000 Received: from Semail04.proact.local (outside.proact.se [212.214.215.3]) by nomtaout01.proact.no (Postfix) with ESMTP id BE0BD5DD81; Mon, 5 Nov 2012 14:54:38 +0100 (MET) 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; Mon, 5 Nov 2012 14:54:38 +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//+/I1A= Date: Mon, 5 Nov 2012 13:54:37 +0000 Message-ID: References: <509172F6.2040400@FreeBSD.org> <5092F209.7090803@FreeBSD.org> <50979BCD.3060000@FreeBSD.org> In-Reply-To: <50979BCD.3060000@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: Mon, 05 Nov 2012 13:55:04 -0000 > -----Original Message----- > From: Andriy Gapon [mailto:avg@FreeBSD.org] > Sent: 5. november 2012 11:58 > 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 12:26 Tom Lislegaard said the following: > >> -----Original Message----- > >> From: Andriy Gapon [mailto:avg@FreeBSD.org] I see. Could you please > >> try setting debug.acpi.max_threads=3D1 in /boot/loader.conf, reboot an= d > >> see if that makes any difference? > > > > It does make a difference. I've had the machine running over the week-e= nd, and haven't had a crash > in 56 hours. > > > > After applying the setting I get some errors on reboot, no idea if they= are harmful in any way (none > that I have notced): > > > > AcpiOsExecute: failed to enqueue task, consider increasing the > > debug.acpi.max_tasks tunable ACPI Error: Method parse/execution failed > > [\\PNOT] (Node 0xfffffe00052e6400), AE_NO_MEMORY > > (20110527/psparse-560) ACPI Error: Method parse/execution failed > > [\\_SB_.AC__._PSR] (Node 0xfffffe00052f57c0), AE_NO_MEMORY > > (20110527/psparse-560) > > > > The same messages repeats 6 times >=20 > Thank you for the test! > Try to set debug.acpi.max_tasks to 128 or even higher to get rid of the n= ew ACPI errors. >=20 > Additionally I would like to ask you to do the following test. > Please stop devd and then run it (as root) from command line as such devd= -D -d. > Please check what event are reported by devd. In particular I am interes= ted in ACAD events, but all > high frequency events are important. >=20 > Thanks! > -- > Andriy Gapon 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=3DCREATE cdev= =3Ddsp4.1' 1 Processing event '!system=3DDEVFS subsystem=3DCDEV type=3DCREATE cdev= =3Dpts/2' 1 Processing event '!system=3DDEVFS subsystem=3DCDEV type=3DCREATE cdev= =3Dvboxdrv0' 1 Processing event '!system=3DDEVFS subsystem=3DCDEV type=3DDESTROY cde= v=3Ddsp4.1' 1 Processing event '!system=3DDEVFS subsystem=3DCDEV type=3DDESTROY cde= v=3Dvboxdrv0' Any use in running it over a longer period of time? -tom From owner-freebsd-acpi@FreeBSD.ORG Mon Nov 5 14:20:36 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 5D0AAFFD; Mon, 5 Nov 2012 14:20:36 +0000 (UTC) (envelope-from avg@FreeBSD.org) Received: from citadel.icyb.net.ua (citadel.icyb.net.ua [212.40.38.140]) by mx1.freebsd.org (Postfix) with ESMTP id 6A6168FC08; Mon, 5 Nov 2012 14:20:35 +0000 (UTC) Received: from odyssey.starpoint.kiev.ua (alpha-e.starpoint.kiev.ua [212.40.38.101]) by citadel.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id QAA01659; Mon, 05 Nov 2012 16:20:23 +0200 (EET) (envelope-from avg@FreeBSD.org) Message-ID: <5097CB27.8040802@FreeBSD.org> Date: Mon, 05 Nov 2012 16:20:23 +0200 From: Andriy Gapon User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:16.0) Gecko/20121029 Thunderbird/16.0.2 MIME-Version: 1.0 To: Tom Lislegaard Subject: Re: 9-Stable panic: resource_list_unreserve: can't find resource References: <509172F6.2040400@FreeBSD.org> <5092F209.7090803@FreeBSD.org> <50979BCD.3060000@FreeBSD.org> In-Reply-To: X-Enigmail-Version: 1.4.5 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit 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: Mon, 05 Nov 2012 14:20:36 -0000 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? -- Andriy Gapon From owner-freebsd-acpi@FreeBSD.ORG Mon Nov 5 14:52:42 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 6CD3CE21; Mon, 5 Nov 2012 14:52:42 +0000 (UTC) (envelope-from Tom.Lislegaard@proact.no) Received: from db3outboundpool.messaging.microsoft.com (db3ehsobe004.messaging.microsoft.com [213.199.154.142]) by mx1.freebsd.org (Postfix) with ESMTP id ABC2B8FC0C; Mon, 5 Nov 2012 14:52:41 +0000 (UTC) Received: from mail39-db3-R.bigfish.com (10.3.81.244) by DB3EHSOBE002.bigfish.com (10.3.84.22) with Microsoft SMTP Server id 14.1.225.23; Mon, 5 Nov 2012 14:52:40 +0000 Received: from mail39-db3 (localhost [127.0.0.1]) by mail39-db3-R.bigfish.com (Postfix) with ESMTP id 5D7361801C2; Mon, 5 Nov 2012 14:52:40 +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 mail39-db3 (localhost.localdomain [127.0.0.1]) by mail39-db3 (MessageSwitch) id 1352127157256193_3348; Mon, 5 Nov 2012 14:52:37 +0000 (UTC) Received: from DB3EHSMHS002.bigfish.com (unknown [10.3.81.229]) by mail39-db3.bigfish.com (Postfix) with ESMTP id 32AD94E010B; Mon, 5 Nov 2012 14:52:37 +0000 (UTC) Received: from semtaout01.proact.se (212.214.215.133) by DB3EHSMHS002.bigfish.com (10.3.87.102) with Microsoft SMTP Server id 14.1.225.23; Mon, 5 Nov 2012 14:52:35 +0000 Received: from Semail04.proact.local (unknown [10.7.1.58]) by semtaout01.proact.se (Postfix) with ESMTP id 15F6D5727C; Mon, 5 Nov 2012 15:52:35 +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; Mon, 5 Nov 2012 15:52:34 +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//5ozA Date: Mon, 5 Nov 2012 14:52:33 +0000 Message-ID: References: <509172F6.2040400@FreeBSD.org> <5092F209.7090803@FreeBSD.org> <50979BCD.3060000@FreeBSD.org> <5097CB27.8040802@FreeBSD.org> In-Reply-To: <5097CB27.8040802@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: Mon, 05 Nov 2012 14:52:42 -0000 > -----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 >=20 > 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=3DCREATE = cdev=3Ddsp4.1' > > 1 Processing event '!system=3DDEVFS subsystem=3DCDEV type=3DCREATE = cdev=3Dpts/2' > > 1 Processing event '!system=3DDEVFS subsystem=3DCDEV type=3DCREATE = cdev=3Dvboxdrv0' > > 1 Processing event '!system=3DDEVFS subsystem=3DCDEV type=3DDESTROY= cdev=3Ddsp4.1' > > 1 Processing event '!system=3DDEVFS subsystem=3DCDEV type=3DDESTROY= cdev=3Dvboxdrv0' > > > > Any use in running it over a longer period of time? >=20 > Very interesting. > So the processors get _CST change notifications rather frequently, but th= ere is no obvious > source/cause for them... >=20 > Could you please send to me acpidump -dt output or upload it somewhere an= d post a link? >=20 > -- > Andriy Gapon Here you go https://dl.dropbox.com/u/13263820/acpidump.txt -tom From owner-freebsd-acpi@FreeBSD.ORG Mon Nov 5 17:07:34 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 DD0AAEE1; Mon, 5 Nov 2012 17:07:33 +0000 (UTC) (envelope-from avg@FreeBSD.org) Received: from citadel.icyb.net.ua (citadel.icyb.net.ua [212.40.38.140]) by mx1.freebsd.org (Postfix) with ESMTP id F14928FC0A; Mon, 5 Nov 2012 17:07:32 +0000 (UTC) Received: from odyssey.starpoint.kiev.ua (alpha-e.starpoint.kiev.ua [212.40.38.101]) by citadel.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id TAA07201; Mon, 05 Nov 2012 19:07:25 +0200 (EET) (envelope-from avg@FreeBSD.org) Message-ID: <5097F24D.7040206@FreeBSD.org> Date: Mon, 05 Nov 2012 19:07:25 +0200 From: Andriy Gapon User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:16.0) Gecko/20121029 Thunderbird/16.0.2 MIME-Version: 1.0 To: Tom Lislegaard Subject: Re: 9-Stable panic: resource_list_unreserve: can't find resource References: <509172F6.2040400@FreeBSD.org> <5092F209.7090803@FreeBSD.org> <50979BCD.3060000@FreeBSD.org> <5097CB27.8040802@FreeBSD.org> In-Reply-To: X-Enigmail-Version: 1.4.5 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit 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: Mon, 05 Nov 2012 17:07:34 -0000 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 From owner-freebsd-acpi@FreeBSD.ORG Tue Nov 6 07:30:56 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 8B78C88C for ; Tue, 6 Nov 2012 07:30:56 +0000 (UTC) (envelope-from demelier.david@gmail.com) Received: from mail-pb0-f54.google.com (mail-pb0-f54.google.com [209.85.160.54]) by mx1.freebsd.org (Postfix) with ESMTP id 5B90D8FC0A for ; Tue, 6 Nov 2012 07:30:56 +0000 (UTC) Received: by mail-pb0-f54.google.com with SMTP id rp8so187241pbb.13 for ; Mon, 05 Nov 2012 23:30:56 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=7kff1OI6ufIr8XS35jWmQVqdmaCYtu0XL6adSAavOgM=; b=qf3ZsGeqqJGPPtayNfS9HGK810RfXWjCM2gJp5+3C1ZO+V8KYvcFt7pdhK0jkcgwqX DNJmfxnfTlj7oEnNg5C2qehh2XP2TQJ5MVQT/hVJNzsIPF3afMlmbhDGIHi58GAiiGuN 1F5P1izFwR4o5lUE4ES4eiWnzM3IzI4wYd+mpSK5eI7alvFnC/bTrsHwxfv8w6nFQbod bbfnpMKWPlFL9rcHhO4L2GTJ/0/qVEarPxroFD7SC4h9PSYq1J8F0YVe79V/Lec9jesb x+FgvsQSsJKOODg09Hf/q2L1I5G4cJLibrZg0AUNNkPSj86hsuik3JiN7QCTr46eHJ5t ddog== MIME-Version: 1.0 Received: by 10.68.227.67 with SMTP id ry3mr435370pbc.134.1352187056133; Mon, 05 Nov 2012 23:30:56 -0800 (PST) Received: by 10.66.80.36 with HTTP; Mon, 5 Nov 2012 23:30:56 -0800 (PST) In-Reply-To: References: Date: Tue, 6 Nov 2012 08:30:56 +0100 Message-ID: Subject: Re: ACPI Regression, battery does not update From: David Demelier To: freebsd-acpi@freebsd.org Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 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 07:30:56 -0000 I've just made a PR http://www.freebsd.org/cgi/query-pr.cgi?pr=173408 2012/11/5 David Demelier > Hello, > > Since I've updated to 9.1-* (RC3 now) my battery does not update, my > laptop is HP Probook 4510s, in fact if I unplug the AC adaptor, the > remaining capacity of the battery will not discharge and stays as the > remaining capacity from when I unplugged the adaptor. > > (If that could be real... :)) > > And sometimes the battery is updated after a while like, when the laptop > battery change to 40% but then I won't see 39%, 38%, and so on.. > > I think I have the same problem as: > > http://www.freebsd.org/cgi/query-pr.cgi?pr=162859 > > -- > Demelier David > -- Demelier David 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 From owner-freebsd-acpi@FreeBSD.ORG Tue Nov 6 18:53:09 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 271EC412; Tue, 6 Nov 2012 18:53:09 +0000 (UTC) (envelope-from avg@FreeBSD.org) Received: from citadel.icyb.net.ua (citadel.icyb.net.ua [212.40.38.140]) by mx1.freebsd.org (Postfix) with ESMTP id 3B4FB8FC16; Tue, 6 Nov 2012 18:53:07 +0000 (UTC) Received: from odyssey.starpoint.kiev.ua (alpha-e.starpoint.kiev.ua [212.40.38.101]) by citadel.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id UAA24459; Tue, 06 Nov 2012 20:53:03 +0200 (EET) (envelope-from avg@FreeBSD.org) Message-ID: <50995C8F.3040309@FreeBSD.org> Date: Tue, 06 Nov 2012 20:53:03 +0200 From: Andriy Gapon User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:16.0) Gecko/20121029 Thunderbird/16.0.2 MIME-Version: 1.0 To: Tom Lislegaard Subject: Re: 9-Stable panic: resource_list_unreserve: can't find resource References: <509172F6.2040400@FreeBSD.org> <5092F209.7090803@FreeBSD.org> <50979BCD.3060000@FreeBSD.org> <5097CB27.8040802@FreeBSD.org> <5097F24D.7040206@FreeBSD.org> In-Reply-To: X-Enigmail-Version: 1.4.5 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit 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 18:53:09 -0000 on 06/11/2012 10:50 Tom Lislegaard said the following: > 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 > repeating again and again so I think this is representative > > https://dl.dropbox.com/u/13263820/debug_dmesg.txt This didn't clarify things as much as I hoped, but I am inclined to think that it is polling from userland that triggers all the processor notifications. In any case, here is a patch to try: http://people.freebsd.org/~avg/acpi_cpu-stable.diff Please disable all the tunings added to loader.conf during debugging when testing this patch. The patch is a combination of two changes: 1. Do not needlessly use ever-increasing resource IDs. Rather use the IDs that are tied to Cx level IDs. Also, release previous resources upon _CST change. 2. Bind a thread that processes a processor _CST change notification to the target processor and perform _CST processing in a critical section. These should ensure the following: - the CPU doesn't enter an idle state and doesn't try to use Cx level parameters while they are being changed - Cx level parameters are never concurrently modified when multiple notifications fire in a rapid succession and multiple ACPI task threads are configured sched_bind is a heavy-weight operation, but it is OK in this context because processor notifications should not occur too often > And, btw, thanks for your efforts. Thank you for all the excellent debugging and testing! P.S. I still believe that BIOS/ACPI on the machine behaves sub-optimally. -- Andriy Gapon From owner-freebsd-acpi@FreeBSD.ORG Thu Nov 8 09:22:02 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 4B6C4450; Thu, 8 Nov 2012 09:22:02 +0000 (UTC) (envelope-from Tom.Lislegaard@proact.no) Received: from ch1outboundpool.messaging.microsoft.com (ch1ehsobe004.messaging.microsoft.com [216.32.181.184]) by mx1.freebsd.org (Postfix) with ESMTP id D96C98FC15; Thu, 8 Nov 2012 09:22:00 +0000 (UTC) Received: from mail64-ch1-R.bigfish.com (10.43.68.241) by CH1EHSOBE005.bigfish.com (10.43.70.55) with Microsoft SMTP Server id 14.1.225.23; Thu, 8 Nov 2012 09:06:46 +0000 Received: from mail64-ch1 (localhost [127.0.0.1]) by mail64-ch1-R.bigfish.com (Postfix) with ESMTP id B40604201C9; Thu, 8 Nov 2012 09:06:46 +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: -4 X-BigFish: VPS-4(zzbb2dI542M1452I1432Izz1de0h1d18h1202h1d1ah1d2ahzz17326ah8275bh8275dhz2dh668h839h944hd25hf0ah1220h1288h12a5h12a9h12bdh137ah13b6h1441h1504h1537h153bh15d0l1155h) Received: from mail64-ch1 (localhost.localdomain [127.0.0.1]) by mail64-ch1 (MessageSwitch) id 1352365604890328_23454; Thu, 8 Nov 2012 09:06:44 +0000 (UTC) Received: from CH1EHSMHS037.bigfish.com (snatpool1.int.messaging.microsoft.com [10.43.68.252]) by mail64-ch1.bigfish.com (Postfix) with ESMTP id D6D2B2001D; Thu, 8 Nov 2012 09:06:44 +0000 (UTC) Received: from semtaout01.proact.se (212.214.215.133) by CH1EHSMHS037.bigfish.com (10.43.69.246) with Microsoft SMTP Server id 14.1.225.23; Thu, 8 Nov 2012 09:06:40 +0000 Received: from Semail04.proact.local (unknown [10.7.1.58]) by semtaout01.proact.se (Postfix) with ESMTP id 3EF105727C; Thu, 8 Nov 2012 10:06: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; Thu, 8 Nov 2012 10:06: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//unQQABYwRGA//1wI8A= Date: Thu, 8 Nov 2012 09:06:38 +0000 Message-ID: References: <509172F6.2040400@FreeBSD.org> <5092F209.7090803@FreeBSD.org> <50979BCD.3060000@FreeBSD.org> <5097CB27.8040802@FreeBSD.org> <5097F24D.7040206@FreeBSD.org> <50995C8F.3040309@FreeBSD.org> In-Reply-To: <50995C8F.3040309@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: Thu, 08 Nov 2012 09:22:02 -0000 > -----Original Message----- > From: Andriy Gapon [mailto:avg@FreeBSD.org] > Sent: 6. november 2012 19:53 > 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 06/11/2012 10:50 Tom Lislegaard said the following: > > 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 repeating again and again > > so I think this is representative > > > > https://dl.dropbox.com/u/13263820/debug_dmesg.txt >=20 > This didn't clarify things as much as I hoped, but I am inclined to think= that it is polling from > userland that triggers all the processor notifications. >=20 > In any case, here is a patch to try: > http://people.freebsd.org/~avg/acpi_cpu-stable.diff >=20 > Please disable all the tunings added to loader.conf during debugging when= testing this patch. >=20 > The patch is a combination of two changes: >=20 > 1. > Do not needlessly use ever-increasing resource IDs. > Rather use the IDs that are tied to Cx level IDs. > Also, release previous resources upon _CST change. >=20 > 2. > Bind a thread that processes a processor _CST change notification to the = target processor and perform > _CST processing in a critical section. These should ensure the following= : > - the CPU doesn't enter an idle state and doesn't try to use Cx level par= ameters > while they are being changed > - Cx level parameters are never concurrently modified when multiple notif= ications > fire in a rapid succession and multiple ACPI task threads are configure= d sched_bind is a heavy- > weight operation, but it is OK in this context because processor notifica= tions should not occur too > often >=20 Thanks. I applied the patch yesterday, but found this morning the machine h= ad crashed during the night with a page fault (kgdb) bt #0 doadump (textdump=3DVariable "textdump" is not available. ) at pcpu.h:229 #1 0xffffffff804441f4 in kern_reboot (howto=3D260) at /usr/src/sys/kern/ke= rn_shutdown.c:448 #2 0xffffffff804446dc in panic (fmt=3D0x1
) at = /usr/src/sys/kern/kern_shutdown.c:636 #3 0xffffffff806f234d in trap_fatal (frame=3D0xfffffe00089264a0, eva=3DVar= iable "eva" is not available. ) at /usr/src/sys/amd64/amd64/trap.c:878 #4 0xffffffff806f2668 in trap_pfault (frame=3D0xffffff82450401b0, usermode= =3D0) at /usr/src/sys/amd64/amd64/trap.c:794 #5 0xffffffff806f29ec in trap (frame=3D0xffffff82450401b0) at /usr/src/sys= /amd64/amd64/trap.c:463 #6 0xffffffff806dc5ff in calltrap () at /usr/src/sys/amd64/amd64/exception= .S:228 #7 0xffffffff802d1bdd in AcpiOsAcquireObject (Cache=3D0xfffffe00052bac60) = at /usr/src/sys/contrib/dev/acpica/utilities/utcache.c:316 #8 0xffffffff802d6883 in AcpiUtAllocateObjectDescDbg (ModuleName=3D0xfffff= fff8074c3f0 "dsutils", LineNumber=3D703, ComponentId=3DVariable "ComponentI= d" is not available. ) at /usr/src/sys/contrib/dev/acpica/utilities/utobject.c:437 #9 0xffffffff802d6a1d in AcpiUtCreateInternalObjectDbg (ModuleName=3D0xfff= fffff8074c3f0 "dsutils", LineNumber=3D703, ComponentId=3D64, Type=3D1) at /= usr/src/sys/contrib/dev/acpica/utilities/utobject.c:112 #10 0xffffffff802a71e8 in AcpiDsCreateOperand (WalkState=3D0xfffffe0008a3bc= 00, Arg=3D0xfffffe0005366800, ArgIndex=3D0) at /usr/src/sys/contrib/dev/acp= ica/dispatcher/dsutils.c:703 #11 0xffffffff802a7587 in AcpiDsCreateOperands (WalkState=3D0xfffffe0008a3b= c00, FirstArg=3D0xfffffe0005366800) at /usr/src/sys/contrib/dev/acpica/disp= atcher/dsutils.c:798 #12 0xffffffff802a856e in AcpiDsExecEndOp (WalkState=3D0xfffffe0008a3bc00) = at /usr/src/sys/contrib/dev/acpica/dispatcher/dswexec.c:567 #13 0xffffffff802c9441 in AcpiPsParseLoop (WalkState=3D0xfffffe0008a3bc00) = at /usr/src/sys/contrib/dev/acpica/parser/psloop.c:1249 #14 0xffffffff802ca8dd in AcpiPsParseAml (WalkState=3D0xfffffe0008a3bc00) a= t /usr/src/sys/contrib/dev/acpica/parser/psparse.c:525 #15 0xffffffff802cb981 in AcpiPsExecuteMethod (Info=3D0xfffffe01a2143100) a= t /usr/src/sys/contrib/dev/acpica/parser/psxface.c:368 #16 0xffffffff802c2287 in AcpiNsEvaluate (Info=3D0xfffffe01a2143100) at /us= r/src/sys/contrib/dev/acpica/namespace/nseval.c:193 #17 0xffffffff802d3f56 in AcpiUtEvaluateObject (PrefixNode=3D0xfffffe00052f= 6540, Path=3D0xffffffff807538f6 "_STA", ExpectedReturnBtypes=3D1, ReturnDes= c=3D0xffffff8245040660) at /usr/src/sys/contrib/dev/acpica/utilities/uteval= .c:102 #18 0xffffffff802d428f in AcpiUtExecute_STA (DeviceNode=3D0xfffffe00052f654= 0, Flags=3D0xfffffe01cc0d1e18) at /usr/src/sys/contrib/dev/acpica/utilities= /uteval.c:276 #19 0xffffffff802c7e47 in AcpiGetObjectInfo (Handle=3DVariable "Handle" is = not available. ) at /usr/src/sys/contrib/dev/acpica/namespace/nsxfname.c:423 #20 0xffffffff802e35ed in acpi_BatteryIsPresent (dev=3D0xfffffe0005378c00) = at /usr/src/sys/dev/acpica/acpi.c:2064 #21 0xffffffff802e66e1 in acpi_battery_get_battinfo (dev=3D0x0, battinfo=3D= 0xffffffff80a4ba70) at /usr/src/sys/dev/acpica/acpi_battery.c:176 #22 0xffffffff802e6a44 in acpi_battery_sysctl (oidp=3D0xfffffe0008785600, a= rg1=3DVariable "arg1" is not available. ) at /usr/src/sys/dev/acpica/acpi_battery.c:428 #23 0xffffffff8044e057 in sysctl_root (oidp=3DVariable "oidp" is not availa= ble. ) at /usr/src/sys/kern/kern_sysctl.c:1513 #24 0xffffffff8044e335 in userland_sysctl (td=3DVariable "td" is not availa= ble. ) at /usr/src/sys/kern/kern_sysctl.c:1623 #25 0xffffffff8044e84a in sys___sysctl (td=3D0xfffffe0008c6c920, uap=3D0xff= ffff8245040a70) at /usr/src/sys/kern/kern_sysctl.c:1549 #26 0xffffffff806f1c40 in amd64_syscall (td=3D0xfffffe0008c6c920, traced=3D= 0) at subr_syscall.c:135 #27 0xffffffff806dc8e7 in Xfast_syscall () at /usr/src/sys/amd64/amd64/exce= ption.S:387 #28 0x00000008026587ec in ?? () Previous frame inner to this frame (corrupt stack?) (kgdb)=20 -tom From owner-freebsd-acpi@FreeBSD.ORG Thu Nov 8 10:53:16 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 D384EFC5; Thu, 8 Nov 2012 10:53:16 +0000 (UTC) (envelope-from avg@FreeBSD.org) Received: from citadel.icyb.net.ua (citadel.icyb.net.ua [212.40.38.140]) by mx1.freebsd.org (Postfix) with ESMTP id DF9F68FC0A; Thu, 8 Nov 2012 10:53:15 +0000 (UTC) Received: from porto.starpoint.kiev.ua (porto-e.starpoint.kiev.ua [212.40.38.100]) by citadel.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id MAA14815; Thu, 08 Nov 2012 12:53:10 +0200 (EET) (envelope-from avg@FreeBSD.org) Received: from localhost ([127.0.0.1]) by porto.starpoint.kiev.ua with esmtp (Exim 4.34 (FreeBSD)) id 1TWPjS-000LXF-Eh; Thu, 08 Nov 2012 12:53:10 +0200 Message-ID: <509B8F15.4030300@FreeBSD.org> Date: Thu, 08 Nov 2012 12:53:09 +0200 From: Andriy Gapon User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:16.0) Gecko/20121030 Thunderbird/16.0.2 MIME-Version: 1.0 To: Tom Lislegaard Subject: Re: 9-Stable panic: resource_list_unreserve: can't find resource References: <509172F6.2040400@FreeBSD.org> <5092F209.7090803@FreeBSD.org> <50979BCD.3060000@FreeBSD.org> <5097CB27.8040802@FreeBSD.org> <5097F24D.7040206@FreeBSD.org> <50995C8F.3040309@FreeBSD.org> In-Reply-To: X-Enigmail-Version: 1.4.5 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit 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: Thu, 08 Nov 2012 10:53:16 -0000 on 08/11/2012 11:06 Tom Lislegaard said the following: > >> -----Original Message----- >> From: Andriy Gapon [mailto:avg@FreeBSD.org] >> Sent: 6. november 2012 19:53 >> 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 06/11/2012 10:50 Tom Lislegaard said the following: >>> 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 repeating again and again >>> so I think this is representative >>> >>> https://dl.dropbox.com/u/13263820/debug_dmesg.txt >> >> This didn't clarify things as much as I hoped, but I am inclined to think that it is polling from >> userland that triggers all the processor notifications. >> >> In any case, here is a patch to try: >> http://people.freebsd.org/~avg/acpi_cpu-stable.diff >> >> Please disable all the tunings added to loader.conf during debugging when testing this patch. >> >> The patch is a combination of two changes: >> >> 1. >> Do not needlessly use ever-increasing resource IDs. >> Rather use the IDs that are tied to Cx level IDs. >> Also, release previous resources upon _CST change. >> >> 2. >> Bind a thread that processes a processor _CST change notification to the target processor and perform >> _CST processing in a critical section. These should ensure the following: >> - the CPU doesn't enter an idle state and doesn't try to use Cx level parameters >> while they are being changed >> - Cx level parameters are never concurrently modified when multiple notifications >> fire in a rapid succession and multiple ACPI task threads are configured sched_bind is a heavy- >> weight operation, but it is OK in this context because processor notifications should not occur too >> often >> > > Thanks. I applied the patch yesterday, but found this morning the machine had crashed during the night with a page fault This looks like an unrelated / new / different problem. Could you please poke around frame 7? BTW, what version of FreeBSD do you use? What ACPICA version is there (debug.acpi.acpi_ca_version) ? It seems like somewhat similar panics were reported in the past: http://lists.freebsd.org/pipermail/freebsd-current/2012-March/032637.html http://lists.freebsd.org/pipermail/freebsd-acpi/2012-January/007406.html > (kgdb) bt > #0 doadump (textdump=Variable "textdump" is not available. > ) at pcpu.h:229 > #1 0xffffffff804441f4 in kern_reboot (howto=260) at /usr/src/sys/kern/kern_shutdown.c:448 > #2 0xffffffff804446dc in panic (fmt=0x1
) at /usr/src/sys/kern/kern_shutdown.c:636 > #3 0xffffffff806f234d in trap_fatal (frame=0xfffffe00089264a0, eva=Variable "eva" is not available. > ) at /usr/src/sys/amd64/amd64/trap.c:878 > #4 0xffffffff806f2668 in trap_pfault (frame=0xffffff82450401b0, usermode=0) at /usr/src/sys/amd64/amd64/trap.c:794 > #5 0xffffffff806f29ec in trap (frame=0xffffff82450401b0) at /usr/src/sys/amd64/amd64/trap.c:463 > #6 0xffffffff806dc5ff in calltrap () at /usr/src/sys/amd64/amd64/exception.S:228 > #7 0xffffffff802d1bdd in AcpiOsAcquireObject (Cache=0xfffffe00052bac60) at /usr/src/sys/contrib/dev/acpica/utilities/utcache.c:316 > #8 0xffffffff802d6883 in AcpiUtAllocateObjectDescDbg (ModuleName=0xffffffff8074c3f0 "dsutils", LineNumber=703, ComponentId=Variable "ComponentId" is not available. > ) at /usr/src/sys/contrib/dev/acpica/utilities/utobject.c:437 > #9 0xffffffff802d6a1d in AcpiUtCreateInternalObjectDbg (ModuleName=0xffffffff8074c3f0 "dsutils", LineNumber=703, ComponentId=64, Type=1) at /usr/src/sys/contrib/dev/acpica/utilities/utobject.c:112 > #10 0xffffffff802a71e8 in AcpiDsCreateOperand (WalkState=0xfffffe0008a3bc00, Arg=0xfffffe0005366800, ArgIndex=0) at /usr/src/sys/contrib/dev/acpica/dispatcher/dsutils.c:703 > #11 0xffffffff802a7587 in AcpiDsCreateOperands (WalkState=0xfffffe0008a3bc00, FirstArg=0xfffffe0005366800) at /usr/src/sys/contrib/dev/acpica/dispatcher/dsutils.c:798 > #12 0xffffffff802a856e in AcpiDsExecEndOp (WalkState=0xfffffe0008a3bc00) at /usr/src/sys/contrib/dev/acpica/dispatcher/dswexec.c:567 > #13 0xffffffff802c9441 in AcpiPsParseLoop (WalkState=0xfffffe0008a3bc00) at /usr/src/sys/contrib/dev/acpica/parser/psloop.c:1249 > #14 0xffffffff802ca8dd in AcpiPsParseAml (WalkState=0xfffffe0008a3bc00) at /usr/src/sys/contrib/dev/acpica/parser/psparse.c:525 > #15 0xffffffff802cb981 in AcpiPsExecuteMethod (Info=0xfffffe01a2143100) at /usr/src/sys/contrib/dev/acpica/parser/psxface.c:368 > #16 0xffffffff802c2287 in AcpiNsEvaluate (Info=0xfffffe01a2143100) at /usr/src/sys/contrib/dev/acpica/namespace/nseval.c:193 > #17 0xffffffff802d3f56 in AcpiUtEvaluateObject (PrefixNode=0xfffffe00052f6540, Path=0xffffffff807538f6 "_STA", ExpectedReturnBtypes=1, ReturnDesc=0xffffff8245040660) at /usr/src/sys/contrib/dev/acpica/utilities/uteval.c:102 > #18 0xffffffff802d428f in AcpiUtExecute_STA (DeviceNode=0xfffffe00052f6540, Flags=0xfffffe01cc0d1e18) at /usr/src/sys/contrib/dev/acpica/utilities/uteval.c:276 > #19 0xffffffff802c7e47 in AcpiGetObjectInfo (Handle=Variable "Handle" is not available. > ) at /usr/src/sys/contrib/dev/acpica/namespace/nsxfname.c:423 > #20 0xffffffff802e35ed in acpi_BatteryIsPresent (dev=0xfffffe0005378c00) at /usr/src/sys/dev/acpica/acpi.c:2064 > #21 0xffffffff802e66e1 in acpi_battery_get_battinfo (dev=0x0, battinfo=0xffffffff80a4ba70) at /usr/src/sys/dev/acpica/acpi_battery.c:176 > #22 0xffffffff802e6a44 in acpi_battery_sysctl (oidp=0xfffffe0008785600, arg1=Variable "arg1" is not available. > ) at /usr/src/sys/dev/acpica/acpi_battery.c:428 > #23 0xffffffff8044e057 in sysctl_root (oidp=Variable "oidp" is not available. > ) at /usr/src/sys/kern/kern_sysctl.c:1513 > #24 0xffffffff8044e335 in userland_sysctl (td=Variable "td" is not available. > ) at /usr/src/sys/kern/kern_sysctl.c:1623 > #25 0xffffffff8044e84a in sys___sysctl (td=0xfffffe0008c6c920, uap=0xffffff8245040a70) at /usr/src/sys/kern/kern_sysctl.c:1549 > #26 0xffffffff806f1c40 in amd64_syscall (td=0xfffffe0008c6c920, traced=0) at subr_syscall.c:135 > #27 0xffffffff806dc8e7 in Xfast_syscall () at /usr/src/sys/amd64/amd64/exception.S:387 > #28 0x00000008026587ec in ?? () > Previous frame inner to this frame (corrupt stack?) > (kgdb) > > -tom > -- Andriy Gapon From owner-freebsd-acpi@FreeBSD.ORG Thu Nov 8 16:26:42 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 D4998B52; Thu, 8 Nov 2012 16:26:42 +0000 (UTC) (envelope-from Tom.Lislegaard@proact.no) Received: from am1outboundpool.messaging.microsoft.com (am1ehsobe006.messaging.microsoft.com [213.199.154.209]) by mx1.freebsd.org (Postfix) with ESMTP id 1ECF08FC14; Thu, 8 Nov 2012 16:26:41 +0000 (UTC) Received: from mail114-am1-R.bigfish.com (10.3.201.244) by AM1EHSOBE009.bigfish.com (10.3.204.29) with Microsoft SMTP Server id 14.1.225.23; Thu, 8 Nov 2012 16:11:31 +0000 Received: from mail114-am1 (localhost [127.0.0.1]) by mail114-am1-R.bigfish.com (Postfix) with ESMTP id 06D85480298; Thu, 8 Nov 2012 16:11:31 +0000 (UTC) X-Forefront-Antispam-Report: CIP:195.159.75.198; KIP:(null); UIP:(null); IPV:NLI; H:nomtaout01.proact.no; RD:nomtaout01.proact.no; EFVD:NLI X-SpamScore: -4 X-BigFish: VPS-4(zzbb2dI542M1452I1432Izz1de0h1d18h1202h1d1ah1d2ahzz17326ah8275bh8275dhz2dh668h839h944hd25hf0ah1220h1288h12a5h12a9h12bdh137ah13b6h1441h1504h1537h153bh15d0l1155h) Received: from mail114-am1 (localhost.localdomain [127.0.0.1]) by mail114-am1 (MessageSwitch) id 1352391088260958_8804; Thu, 8 Nov 2012 16:11:28 +0000 (UTC) Received: from AM1EHSMHS012.bigfish.com (unknown [10.3.201.233]) by mail114-am1.bigfish.com (Postfix) with ESMTP id 3362B44004A; Thu, 8 Nov 2012 16:11:28 +0000 (UTC) Received: from nomtaout01.proact.no (195.159.75.198) by AM1EHSMHS012.bigfish.com (10.3.207.112) with Microsoft SMTP Server id 14.1.225.23; Thu, 8 Nov 2012 16:11:26 +0000 Received: from Semail04.proact.local (outside.proact.se [212.214.215.3]) by nomtaout01.proact.no (Postfix) with ESMTP id BB57F5DD81; Thu, 8 Nov 2012 17:11:26 +0100 (MET) 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; Thu, 8 Nov 2012 17:11:26 +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//unQQABYwRGA//1wI8D/+tGOgP/1OpgA Date: Thu, 8 Nov 2012 16:11:26 +0000 Message-ID: References: <509172F6.2040400@FreeBSD.org> <5092F209.7090803@FreeBSD.org> <50979BCD.3060000@FreeBSD.org> <5097CB27.8040802@FreeBSD.org> <5097F24D.7040206@FreeBSD.org> <50995C8F.3040309@FreeBSD.org> <509B8F15.4030300@FreeBSD.org> In-Reply-To: <509B8F15.4030300@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: Thu, 08 Nov 2012 16:26:42 -0000 > -----Original Message----- > From: Andriy Gapon [mailto:avg@FreeBSD.org] > Sent: 8. november 2012 11:53 > 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 08/11/2012 11:06 Tom Lislegaard said the following: > > > >> -----Original Message----- > >> From: Andriy Gapon [mailto:avg@FreeBSD.org] > >> Sent: 6. november 2012 19:53 > >> 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 06/11/2012 10:50 Tom Lislegaard said the following: > >>> 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 repeating again and > >>> again so I think this is representative > >>> > >>> https://dl.dropbox.com/u/13263820/debug_dmesg.txt > >> > >> This didn't clarify things as much as I hoped, but I am inclined to > >> think that it is polling from userland that triggers all the processor= notifications. > >> > >> In any case, here is a patch to try: > >> http://people.freebsd.org/~avg/acpi_cpu-stable.diff > >> > >> Please disable all the tunings added to loader.conf during debugging w= hen testing this patch. > >> > >> The patch is a combination of two changes: > >> > >> 1. > >> Do not needlessly use ever-increasing resource IDs. > >> Rather use the IDs that are tied to Cx level IDs. > >> Also, release previous resources upon _CST change. > >> > >> 2. > >> Bind a thread that processes a processor _CST change notification to > >> the target processor and perform _CST processing in a critical section= . These should ensure the > following: > >> - the CPU doesn't enter an idle state and doesn't try to use Cx level = parameters > >> while they are being changed > >> - Cx level parameters are never concurrently modified when multiple no= tifications > >> fire in a rapid succession and multiple ACPI task threads are > >> configured sched_bind is a heavy- weight operation, but it is OK in > >> this context because processor notifications should not occur too > >> often > >> > > > > Thanks. I applied the patch yesterday, but found this morning the > > machine had crashed during the night with a page fault >=20 > This looks like an unrelated / new / different problem. > Could you please poke around frame 7? I've put up some more info=20 https://dl.dropbox.com/u/13263820/vmcore_7.txt > BTW, what version of FreeBSD do you use? Version is RELENG_9 checked out ~3 days ago > What ACPICA version is there (debug.acpi.acpi_ca_version) ? debug.acpi.acpi_ca_version: 20110527 -tom >=20 > It seems like somewhat similar panics were reported in the past: > http://lists.freebsd.org/pipermail/freebsd-current/2012-March/032637.html > http://lists.freebsd.org/pipermail/freebsd-acpi/2012-January/007406.html >=20 > > (kgdb) bt > > #0 doadump (textdump=3DVariable "textdump" is not available. > > ) at pcpu.h:229 > > #1 0xffffffff804441f4 in kern_reboot (howto=3D260) at > > /usr/src/sys/kern/kern_shutdown.c:448 > > #2 0xffffffff804446dc in panic (fmt=3D0x1
) > > at /usr/src/sys/kern/kern_shutdown.c:636 > > #3 0xffffffff806f234d in trap_fatal (frame=3D0xfffffe00089264a0, eva= =3DVariable "eva" is not available. > > ) at /usr/src/sys/amd64/amd64/trap.c:878 > > #4 0xffffffff806f2668 in trap_pfault (frame=3D0xffffff82450401b0, > > usermode=3D0) at /usr/src/sys/amd64/amd64/trap.c:794 > > #5 0xffffffff806f29ec in trap (frame=3D0xffffff82450401b0) at > > /usr/src/sys/amd64/amd64/trap.c:463 > > #6 0xffffffff806dc5ff in calltrap () at > > /usr/src/sys/amd64/amd64/exception.S:228 > > #7 0xffffffff802d1bdd in AcpiOsAcquireObject > > (Cache=3D0xfffffe00052bac60) at > > /usr/src/sys/contrib/dev/acpica/utilities/utcache.c:316 > > #8 0xffffffff802d6883 in AcpiUtAllocateObjectDescDbg (ModuleName=3D0xf= fffffff8074c3f0 "dsutils", > LineNumber=3D703, ComponentId=3DVariable "ComponentId" is not available. > > ) at /usr/src/sys/contrib/dev/acpica/utilities/utobject.c:437 > > #9 0xffffffff802d6a1d in AcpiUtCreateInternalObjectDbg > > (ModuleName=3D0xffffffff8074c3f0 "dsutils", LineNumber=3D703, > > ComponentId=3D64, Type=3D1) at > > /usr/src/sys/contrib/dev/acpica/utilities/utobject.c:112 > > #10 0xffffffff802a71e8 in AcpiDsCreateOperand > > (WalkState=3D0xfffffe0008a3bc00, Arg=3D0xfffffe0005366800, ArgIndex=3D0= ) at > > /usr/src/sys/contrib/dev/acpica/dispatcher/dsutils.c:703 > > #11 0xffffffff802a7587 in AcpiDsCreateOperands > > (WalkState=3D0xfffffe0008a3bc00, FirstArg=3D0xfffffe0005366800) at > > /usr/src/sys/contrib/dev/acpica/dispatcher/dsutils.c:798 > > #12 0xffffffff802a856e in AcpiDsExecEndOp > > (WalkState=3D0xfffffe0008a3bc00) at > > /usr/src/sys/contrib/dev/acpica/dispatcher/dswexec.c:567 > > #13 0xffffffff802c9441 in AcpiPsParseLoop > > (WalkState=3D0xfffffe0008a3bc00) at > > /usr/src/sys/contrib/dev/acpica/parser/psloop.c:1249 > > #14 0xffffffff802ca8dd in AcpiPsParseAml > > (WalkState=3D0xfffffe0008a3bc00) at > > /usr/src/sys/contrib/dev/acpica/parser/psparse.c:525 > > #15 0xffffffff802cb981 in AcpiPsExecuteMethod > > (Info=3D0xfffffe01a2143100) at > > /usr/src/sys/contrib/dev/acpica/parser/psxface.c:368 > > #16 0xffffffff802c2287 in AcpiNsEvaluate (Info=3D0xfffffe01a2143100) at > > /usr/src/sys/contrib/dev/acpica/namespace/nseval.c:193 > > #17 0xffffffff802d3f56 in AcpiUtEvaluateObject > > (PrefixNode=3D0xfffffe00052f6540, Path=3D0xffffffff807538f6 "_STA", > > ExpectedReturnBtypes=3D1, ReturnDesc=3D0xffffff8245040660) at > > /usr/src/sys/contrib/dev/acpica/utilities/uteval.c:102 > > #18 0xffffffff802d428f in AcpiUtExecute_STA > > (DeviceNode=3D0xfffffe00052f6540, Flags=3D0xfffffe01cc0d1e18) at > > /usr/src/sys/contrib/dev/acpica/utilities/uteval.c:276 > > #19 0xffffffff802c7e47 in AcpiGetObjectInfo (Handle=3DVariable "Handle"= is not available. > > ) at /usr/src/sys/contrib/dev/acpica/namespace/nsxfname.c:423 > > #20 0xffffffff802e35ed in acpi_BatteryIsPresent > > (dev=3D0xfffffe0005378c00) at /usr/src/sys/dev/acpica/acpi.c:2064 > > #21 0xffffffff802e66e1 in acpi_battery_get_battinfo (dev=3D0x0, > > battinfo=3D0xffffffff80a4ba70) at > > /usr/src/sys/dev/acpica/acpi_battery.c:176 > > #22 0xffffffff802e6a44 in acpi_battery_sysctl (oidp=3D0xfffffe000878560= 0, arg1=3DVariable "arg1" is not > available. > > ) at /usr/src/sys/dev/acpica/acpi_battery.c:428 > > #23 0xffffffff8044e057 in sysctl_root (oidp=3DVariable "oidp" is not av= ailable. > > ) at /usr/src/sys/kern/kern_sysctl.c:1513 > > #24 0xffffffff8044e335 in userland_sysctl (td=3DVariable "td" is not av= ailable. > > ) at /usr/src/sys/kern/kern_sysctl.c:1623 > > #25 0xffffffff8044e84a in sys___sysctl (td=3D0xfffffe0008c6c920, > > uap=3D0xffffff8245040a70) at /usr/src/sys/kern/kern_sysctl.c:1549 > > #26 0xffffffff806f1c40 in amd64_syscall (td=3D0xfffffe0008c6c920, > > traced=3D0) at subr_syscall.c:135 > > #27 0xffffffff806dc8e7 in Xfast_syscall () at > > /usr/src/sys/amd64/amd64/exception.S:387 > > #28 0x00000008026587ec in ?? () > > Previous frame inner to this frame (corrupt stack?) > > (kgdb) > > > > -tom > > >=20 >=20 > -- > Andriy Gapon From owner-freebsd-acpi@FreeBSD.ORG Thu Nov 8 16:36:30 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 5B353228 for ; Thu, 8 Nov 2012 16:36:30 +0000 (UTC) (envelope-from avg@FreeBSD.org) Received: from citadel.icyb.net.ua (citadel.icyb.net.ua [212.40.38.140]) by mx1.freebsd.org (Postfix) with ESMTP id 6DB9B8FC0A for ; Thu, 8 Nov 2012 16:36:28 +0000 (UTC) Received: from odyssey.starpoint.kiev.ua (alpha-e.starpoint.kiev.ua [212.40.38.101]) by citadel.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id SAA18883; Thu, 08 Nov 2012 18:36:23 +0200 (EET) (envelope-from avg@FreeBSD.org) Message-ID: <509BDF86.3080502@FreeBSD.org> Date: Thu, 08 Nov 2012 18:36:22 +0200 From: Andriy Gapon User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:16.0) Gecko/20121029 Thunderbird/16.0.2 MIME-Version: 1.0 To: Tom Lislegaard , freebsd-acpi@FreeBSD.org Subject: AcpiOsAcquireObject crash [Was: 9-Stable panic: resource_list_unreserve: can't find resource] References: <509172F6.2040400@FreeBSD.org> <5092F209.7090803@FreeBSD.org> <50979BCD.3060000@FreeBSD.org> <5097CB27.8040802@FreeBSD.org> <5097F24D.7040206@FreeBSD.org> <50995C8F.3040309@FreeBSD.org> <509B8F15.4030300@FreeBSD.org> In-Reply-To: X-Enigmail-Version: 1.4.5 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit 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: Thu, 08 Nov 2012 16:36:30 -0000 on 08/11/2012 18:11 Tom Lislegaard said the following: > I've put up some more info > https://dl.dropbox.com/u/13263820/vmcore_7.txt > >> BTW, what version of FreeBSD do you use? > > Version is RELENG_9 checked out ~3 days ago > >> What ACPICA version is there (debug.acpi.acpi_ca_version) ? > > debug.acpi.acpi_ca_version: 20110527 Thanks! Could you please also do: x/9a Cache->ListHead ? I suspect that this bug is of very inconvenient nature: a memory corruption, either semi-random or some sort of use after free. -- Andriy Gapon From owner-freebsd-acpi@FreeBSD.ORG Fri Nov 9 02:01:46 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 4B10A7DB for ; Fri, 9 Nov 2012 02:01:46 +0000 (UTC) (envelope-from nitroboost@gmail.com) Received: from mail-we0-f182.google.com (mail-we0-f182.google.com [74.125.82.182]) by mx1.freebsd.org (Postfix) with ESMTP id C93168FC0A for ; Fri, 9 Nov 2012 02:01:45 +0000 (UTC) Received: by mail-we0-f182.google.com with SMTP id x43so1934064wey.13 for ; Thu, 08 Nov 2012 18:01:39 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=xh/pxK2cFfTfOAXlXyLJXSFYFKLtyTOxGHoUxF6fUy8=; b=b9QUZbHC48Myh5uct31URY2fxEAOkk5cMghYD7h90FfzTcwcB+YSmFAVhb2DULInWL 59tYxyPE8kww6m5z6zuRnvWuGZjFxj7gw3aFRiT1YWYGmu2gm0s0JZhtwbvb267Xshbg ZXW5ldFeUN17oH1z10cNX7+77jHu4hSbMPDnQ9Mt4A5hDxm58GCtC04OHsB5Ol+4QpgV BcCg2gs7sCONNgmp0v4HP/gPqa/6OQnHrg69CqmrZXjDqfKrPHv9Bisgsc7EYcsuuiD1 essQS0tinNH+WTE64f/aHn0R67bIfd25odXwlkF56Sw2vRLKwNMRQ+OkW6npI+Lr9o1Z gcXA== MIME-Version: 1.0 Received: by 10.180.108.38 with SMTP id hh6mr280574wib.0.1352426499382; Thu, 08 Nov 2012 18:01:39 -0800 (PST) Received: by 10.194.15.196 with HTTP; Thu, 8 Nov 2012 18:01:39 -0800 (PST) Date: Thu, 8 Nov 2012 19:01:39 -0700 Message-ID: Subject: High ACPI CPU usage on a Supermicro X9DRT-HF+ From: Jason Wolfe To: freebsd-acpi@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 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: Fri, 09 Nov 2012 02:01:46 -0000 Hi, I'm having an issue with a large pool of Supermicro X9DRT-HF+ servers in which the ACPI processes basically burn up a whole CPU. I have ACPI debug mode compiled/enabled, but as I'm not actually having any issues per se, I'm having trouble with the next steps. This is fairly new Sandy Bridge hardware, so I figure it's possible something needs to be fleshed out in the code. Every BIOS option relating to ACPI has been flipped back and forth, and booting without ACPI support causes a panic. Here is the verbose boot log as well as the acpidump -dt output, and other interesting bits: http://nitrology.com/dmesg.acpi http://nitrology.com/jason-X9DRT-HF.asl sysctl hw.acpi: hw.acpi.supported_sleep_state: S1 S4 S5 hw.acpi.power_button_state: S5 hw.acpi.sleep_button_state: S1 hw.acpi.lid_switch_state: NONE hw.acpi.standby_state: S1 hw.acpi.suspend_state: NONE hw.acpi.sleep_delay: 1 hw.acpi.s4bios: 0 hw.acpi.verbose: 1 hw.acpi.disable_on_reboot: 0 hw.acpi.handle_reboot: 1 hw.acpi.reset_video: 0 hw.acpi.cpu.cx_lowest: C1 vmstat -i: interrupt total rate irq9: acpi0 12170706 14610 cpu0: timer 1662074 1995 cpu3: timer 1644465 1974 cpu4: timer 1644529 1974 cpu1: timer 1644423 1974 cpu5: timer 1644498 1974 cpu2: timer 1644479 1974 top -SHb: last pid: 1979; load averages: 1.39, 1.35, 0.90 up 0+00:13:54 18:46:27 160 processes: 8 running, 119 sleeping, 33 waiting Mem: 2355M Active, 11G Inact, 7431M Wired, 216K Cache, 6559M Buf, 41G Free Swap: 24G Total, 24G Free PID USERNAME PRI NICE SIZE RES STATE C TIME WCPU COMMAND 11 root 171 ki31 0K 96K RUN 4 11:52 89.70% idle{idle: cpu4} 11 root 171 ki31 0K 96K CPU5 5 11:55 86.67% idle{idle: cpu5} 11 root 171 ki31 0K 96K CPU2 2 11:14 84.08% idle{idle: cpu2} 11 root 171 ki31 0K 96K CPU3 3 9:56 76.76% idle{idle: cpu3} 11 root 171 ki31 0K 96K CPU1 1 9:09 70.90% idle{idle: cpu1} 11 root 171 ki31 0K 96K RUN 0 9:24 70.07% idle{idle: cpu0} 12 root -52 - 0K 528K WAIT 3 3:25 27.29% intr{irq9: acpi0} 0 root 8 0 0K 320K CPU4 4 3:39 25.59% kernel{acpi_task_2} 0 root 8 0 0K 320K - 2 3:40 25.39% kernel{acpi_task_0} 0 root 8 0 0K 320K - 5 3:39 25.20% kernel{acpi_task_1} 1583 squid 49 0 1378M 1299M kqread 2 1:26 10.50% squid 12 root -68 - 0K 528K WAIT 2 0:15 2.49% intr{irq258: igb0:que} 12 root -68 - 0K 528K WAIT 1 0:12 2.29% intr{irq257: igb0:que} 12 root -68 - 0K 528K WAIT 0 0:14 1.95% intr{irq256: igb0:que} 12 root -68 - 0K 528K WAIT 5 0:12 1.66% intr{irq261: igb0:que} 12 root -68 - 0K 528K WAIT 3 0:13 1.27% intr{irq259: igb0:que} 12 root -68 - 0K 528K WAIT 4 0:12 1.07% intr{irq260: igb0:que} 0 root -16 0 0K 320K sched 1 413:17 0.00% kernel{swapper} Thanks! Jason From owner-freebsd-acpi@FreeBSD.ORG Fri Nov 9 07:06:59 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 3E21A6BA for ; Fri, 9 Nov 2012 07:06:59 +0000 (UTC) (envelope-from avg@FreeBSD.org) Received: from citadel.icyb.net.ua (citadel.icyb.net.ua [212.40.38.140]) by mx1.freebsd.org (Postfix) with ESMTP id 6525C8FC0A for ; Fri, 9 Nov 2012 07:06:57 +0000 (UTC) Received: from porto.starpoint.kiev.ua (porto-e.starpoint.kiev.ua [212.40.38.100]) by citadel.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id JAA24023; Fri, 09 Nov 2012 09:06:55 +0200 (EET) (envelope-from avg@FreeBSD.org) Received: from localhost ([127.0.0.1]) by porto.starpoint.kiev.ua with esmtp (Exim 4.34 (FreeBSD)) id 1TWig3-000Pai-E4; Fri, 09 Nov 2012 09:06:55 +0200 Message-ID: <509CAB8C.1000106@FreeBSD.org> Date: Fri, 09 Nov 2012 09:06:52 +0200 From: Andriy Gapon User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:16.0) Gecko/20121030 Thunderbird/16.0.2 MIME-Version: 1.0 To: Jason Wolfe Subject: Re: High ACPI CPU usage on a Supermicro X9DRT-HF+ References: In-Reply-To: X-Enigmail-Version: 1.4.5 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-acpi@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: Fri, 09 Nov 2012 07:06:59 -0000 on 09/11/2012 04:01 Jason Wolfe said the following: > Hi, > > I'm having an issue with a large pool of Supermicro X9DRT-HF+ servers in > which the ACPI processes basically burn up a whole CPU. I have ACPI debug > mode compiled/enabled, but as I'm not actually having any issues per se, > I'm having trouble with the next steps. This is fairly new Sandy Bridge > hardware, so I figure it's possible something needs to be fleshed out in > the code. Every BIOS option relating to ACPI has been flipped back and > forth, and booting without ACPI support causes a panic. > > Here is the verbose boot log as well as the acpidump -dt output, and other > interesting bits: > > http://nitrology.com/dmesg.acpi > http://nitrology.com/jason-X9DRT-HF.asl > > sysctl hw.acpi: > hw.acpi.supported_sleep_state: S1 S4 S5 > hw.acpi.power_button_state: S5 > hw.acpi.sleep_button_state: S1 > hw.acpi.lid_switch_state: NONE > hw.acpi.standby_state: S1 > hw.acpi.suspend_state: NONE > hw.acpi.sleep_delay: 1 > hw.acpi.s4bios: 0 > hw.acpi.verbose: 1 > hw.acpi.disable_on_reboot: 0 > hw.acpi.handle_reboot: 1 > hw.acpi.reset_video: 0 > hw.acpi.cpu.cx_lowest: C1 > > vmstat -i: > interrupt total rate > irq9: acpi0 12170706 14610 > cpu0: timer 1662074 1995 > cpu3: timer 1644465 1974 > cpu4: timer 1644529 1974 > cpu1: timer 1644423 1974 > cpu5: timer 1644498 1974 > cpu2: timer 1644479 1974 > > top -SHb: > last pid: 1979; load averages: 1.39, 1.35, 0.90 up 0+00:13:54 18:46:27 > 160 processes: 8 running, 119 sleeping, 33 waiting > > Mem: 2355M Active, 11G Inact, 7431M Wired, 216K Cache, 6559M Buf, 41G Free > Swap: 24G Total, 24G Free > > PID USERNAME PRI NICE SIZE RES STATE C TIME WCPU COMMAND > 11 root 171 ki31 0K 96K RUN 4 11:52 89.70% idle{idle: cpu4} > 11 root 171 ki31 0K 96K CPU5 5 11:55 86.67% idle{idle: cpu5} > 11 root 171 ki31 0K 96K CPU2 2 11:14 84.08% idle{idle: cpu2} > 11 root 171 ki31 0K 96K CPU3 3 9:56 76.76% idle{idle: cpu3} > 11 root 171 ki31 0K 96K CPU1 1 9:09 70.90% idle{idle: cpu1} > 11 root 171 ki31 0K 96K RUN 0 9:24 70.07% idle{idle: cpu0} > 12 root -52 - 0K 528K WAIT 3 3:25 27.29% intr{irq9: acpi0} > 0 root 8 0 0K 320K CPU4 4 3:39 25.59% kernel{acpi_task_2} > 0 root 8 0 0K 320K - 2 3:40 25.39% kernel{acpi_task_0} > 0 root 8 0 0K 320K - 5 3:39 25.20% kernel{acpi_task_1} As a first step please add the following to the loader.conf and see what gets reported and at what frequency: debug.acpi.layer="ACPI_EVENTS" debug.acpi.level="ACPI_LV_INFO Also, is your system DTrace-enabled? -- Andriy Gapon From owner-freebsd-acpi@FreeBSD.ORG Fri Nov 9 13:02:57 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 0438BDFC; Fri, 9 Nov 2012 13:02:56 +0000 (UTC) (envelope-from Tom.Lislegaard@proact.no) Received: from tx2outboundpool.messaging.microsoft.com (tx2ehsobe004.messaging.microsoft.com [65.55.88.14]) by mx1.freebsd.org (Postfix) with ESMTP id 91D2C8FC12; Fri, 9 Nov 2012 13:02:55 +0000 (UTC) Received: from mail258-tx2-R.bigfish.com (10.9.14.248) by TX2EHSOBE001.bigfish.com (10.9.40.21) with Microsoft SMTP Server id 14.1.225.23; Fri, 9 Nov 2012 12:17:30 +0000 Received: from mail258-tx2 (localhost [127.0.0.1]) by mail258-tx2-R.bigfish.com (Postfix) with ESMTP id F413E16C0299; Fri, 9 Nov 2012 12:17:29 +0000 (UTC) X-Forefront-Antispam-Report: CIP:195.159.75.198; KIP:(null); UIP:(null); IPV:NLI; H:nomtaout01.proact.no; RD:nomtaout01.proact.no; EFVD:NLI X-SpamScore: -6 X-BigFish: VPS-6(zzbb2dI103dK542M1432Izz1de0h1d18h1202h1d1ah1d2ahzz8275bh8275dhz2dh668h839h944hd25hf0ah1220h1288h12a5h12a9h12bdh137ah13b6h1441h1504h1537h153bh15d0l1155h) Received: from mail258-tx2 (localhost.localdomain [127.0.0.1]) by mail258-tx2 (MessageSwitch) id 1352463447511681_27634; Fri, 9 Nov 2012 12:17:27 +0000 (UTC) Received: from TX2EHSMHS026.bigfish.com (unknown [10.9.14.239]) by mail258-tx2.bigfish.com (Postfix) with ESMTP id 66966D00049; Fri, 9 Nov 2012 12:17:27 +0000 (UTC) Received: from nomtaout01.proact.no (195.159.75.198) by TX2EHSMHS026.bigfish.com (10.9.99.126) with Microsoft SMTP Server id 14.1.225.23; Fri, 9 Nov 2012 12:17:27 +0000 Received: from Semail04.proact.local (outside.proact.se [212.214.215.3]) by nomtaout01.proact.no (Postfix) with ESMTP id 6E7CD5DD81; Fri, 9 Nov 2012 13:17:26 +0100 (MET) 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; Fri, 9 Nov 2012 13:17:25 +0100 From: Tom Lislegaard To: 'Andriy Gapon' , "freebsd-acpi@FreeBSD.org" Subject: RE: AcpiOsAcquireObject crash [Was: 9-Stable panic: resource_list_unreserve: can't find resource] Thread-Topic: AcpiOsAcquireObject crash [Was: 9-Stable panic: resource_list_unreserve: can't find resource] Thread-Index: AQHNvc81+Z+//tujgE2NCdmsWuXGgZfhbFxQ Date: Fri, 9 Nov 2012 12:17:25 +0000 Message-ID: References: <509172F6.2040400@FreeBSD.org> <5092F209.7090803@FreeBSD.org> <50979BCD.3060000@FreeBSD.org> <5097CB27.8040802@FreeBSD.org> <5097F24D.7040206@FreeBSD.org> <50995C8F.3040309@FreeBSD.org> <509B8F15.4030300@FreeBSD.org> <509BDF86.3080502@FreeBSD.org> In-Reply-To: <509BDF86.3080502@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 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: Fri, 09 Nov 2012 13:02:57 -0000 > -----Original Message----- > From: Andriy Gapon [mailto:avg@FreeBSD.org] > Sent: 8. november 2012 17:37 > To: Tom Lislegaard; freebsd-acpi@FreeBSD.org > Subject: AcpiOsAcquireObject crash [Was: 9-Stable panic: resource_list_un= reserve: can't find resource] >=20 > on 08/11/2012 18:11 Tom Lislegaard said the following: > > I've put up some more info > > https://dl.dropbox.com/u/13263820/vmcore_7.txt > > > >> BTW, what version of FreeBSD do you use? > > > > Version is RELENG_9 checked out ~3 days ago > > > >> What ACPICA version is there (debug.acpi.acpi_ca_version) ? > > > > debug.acpi.acpi_ca_version: 20110527 >=20 > Thanks! > Could you please also do: > x/9a Cache->ListHead > ? >=20 > I suspect that this bug is of very inconvenient nature: a memory corrupti= on, either semi-random or > some sort of use after free. >=20 > -- > Andriy Gapon Here you go kgdb) up 7 #7 0xffffffff802d1bdd in AcpiOsAcquireObject (Cache=3D0xfffffe00052bac60) = at /usr/src/sys/contrib/dev/acpica/utilities/utcache.c:316 316 ACPI_DEBUG_PRINT ((ACPI_DB_EXEC, (kgdb) x/9a Cache->ListHead 0xfffffffeec85c730: Cannot access memory at address 0xfffffffeec85c730 tom From owner-freebsd-acpi@FreeBSD.ORG Fri Nov 9 13:46:07 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 A6B9471D for ; Fri, 9 Nov 2012 13:46:07 +0000 (UTC) (envelope-from avg@FreeBSD.org) Received: from citadel.icyb.net.ua (citadel.icyb.net.ua [212.40.38.140]) by mx1.freebsd.org (Postfix) with ESMTP id CEE408FC12 for ; Fri, 9 Nov 2012 13:46:06 +0000 (UTC) Received: from odyssey.starpoint.kiev.ua (alpha-e.starpoint.kiev.ua [212.40.38.101]) by citadel.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id PAA26923; Fri, 09 Nov 2012 15:46:02 +0200 (EET) (envelope-from avg@FreeBSD.org) Message-ID: <509D091A.8080108@FreeBSD.org> Date: Fri, 09 Nov 2012 15:46:02 +0200 From: Andriy Gapon User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:16.0) Gecko/20121029 Thunderbird/16.0.2 MIME-Version: 1.0 To: Tom Lislegaard Subject: Re: AcpiOsAcquireObject crash [Was: 9-Stable panic: resource_list_unreserve: can't find resource] References: <509172F6.2040400@FreeBSD.org> <5092F209.7090803@FreeBSD.org> <50979BCD.3060000@FreeBSD.org> <5097CB27.8040802@FreeBSD.org> <5097F24D.7040206@FreeBSD.org> <50995C8F.3040309@FreeBSD.org> <509B8F15.4030300@FreeBSD.org> <509BDF86.3080502@FreeBSD.org> In-Reply-To: X-Enigmail-Version: 1.4.5 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: freebsd-acpi@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: Fri, 09 Nov 2012 13:46:07 -0000 on 09/11/2012 14:17 Tom Lislegaard said the following: > kgdb) up 7 > #7 0xffffffff802d1bdd in AcpiOsAcquireObject (Cache=0xfffffe00052bac60) at /usr/src/sys/contrib/dev/acpica/utilities/utcache.c:316 > 316 ACPI_DEBUG_PRINT ((ACPI_DB_EXEC, > (kgdb) x/9a Cache->ListHead > 0xfffffffeec85c730: Cannot access memory at address 0xfffffffeec85c730 [Slaps forehead] Ah, right, indeed. I guess the problem hasn't happened again since then? Does the patch appear to work OK so far (with respect to the original problem)? I have a suspicion about what causes the new problem. If it is correct then the following experimental patch may help with it: --- a/sys/contrib/dev/acpica/components/utilities/utdelete.c +++ b/sys/contrib/dev/acpica/components/utilities/utdelete.c @@ -415,6 +415,8 @@ AcpiUtUpdateRefCount ( return; } + (void) AcpiUtAcquireMutex (ACPI_MTX_REFCOUNTS); + Count = Object->Common.ReferenceCount; NewCount = Count; @@ -490,6 +492,8 @@ AcpiUtUpdateRefCount ( ACPI_WARNING ((AE_INFO, "Large Reference Count (0x%X) in object %p", Count, Object)); } + + (void) AcpiUtReleaseMutex (ACPI_MTX_REFCOUNTS); } --- a/sys/contrib/dev/acpica/include/aclocal.h +++ b/sys/contrib/dev/acpica/include/aclocal.h @@ -89,8 +89,9 @@ union acpi_parse_object; #define ACPI_MTX_MEMORY 5 /* Debug memory tracking lists */ #define ACPI_MTX_DEBUG_CMD_COMPLETE 6 /* AML debugger */ #define ACPI_MTX_DEBUG_CMD_READY 7 /* AML debugger */ +#define ACPI_MTX_REFCOUNTS 8 /* ACPI object reference counts */ -#define ACPI_MAX_MUTEX 7 +#define ACPI_MAX_MUTEX 8 #define ACPI_NUM_MUTEX ACPI_MAX_MUTEX+1 -- Andriy Gapon From owner-freebsd-acpi@FreeBSD.ORG Fri Nov 9 18:31:45 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 73B47B69; Fri, 9 Nov 2012 18:31:45 +0000 (UTC) (envelope-from nitroboost@gmail.com) Received: from mail-ea0-f182.google.com (mail-ea0-f182.google.com [209.85.215.182]) by mx1.freebsd.org (Postfix) with ESMTP id CFC4A8FC08; Fri, 9 Nov 2012 18:31:44 +0000 (UTC) Received: by mail-ea0-f182.google.com with SMTP id c10so2052699eaa.13 for ; Fri, 09 Nov 2012 10:31:43 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=R6lumVhnxpgaHyeQvuKbqMFXRcyKAexknAQRnAGnweY=; b=yRCKujjdQctmYPNhTjb0k4MhV83h3vVtE8LwlbXnLe4UCVLQ0yjUXoIlNhqLsulhL/ osSdArywLo0u/ZKRtacJbGWKjY+/aJ/+yJed4Ttmixia/LVsBM1FAqUqFAQ1LGRozxXR vVYZHHn+CaBAHE2b6DjENAvxzHjqYEbPhScey3InfQ+LXO40w50NuxKeCiI+TbIqUmUI Dah1W/o0/JzFIXKL/ccV1c3dLrklilB7f6UNqPNAxKneO37IgE+22IYkrjuwuB1+xsvX QKDFX2iV+PnuOTFF+ixkMlVgt2zQTb7dj1f9aNLbYCqaITxgz6j9DH84t2vIFD/xYH8a +mOw== MIME-Version: 1.0 Received: by 10.14.219.2 with SMTP id l2mr40395857eep.3.1352485903661; Fri, 09 Nov 2012 10:31:43 -0800 (PST) Received: by 10.14.218.133 with HTTP; Fri, 9 Nov 2012 10:31:43 -0800 (PST) In-Reply-To: <509CAB8C.1000106@FreeBSD.org> References: <509CAB8C.1000106@FreeBSD.org> Date: Fri, 9 Nov 2012 11:31:43 -0700 Message-ID: Subject: Re: High ACPI CPU usage on a Supermicro X9DRT-HF+ From: Jason Wolfe To: Andriy Gapon Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 Cc: freebsd-acpi@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: Fri, 09 Nov 2012 18:31:45 -0000 On Fri, Nov 9, 2012 at 12:06 AM, Andriy Gapon wrote: > on 09/11/2012 04:01 Jason Wolfe said the following: > > Hi, > > > > I'm having an issue with a large pool of Supermicro X9DRT-HF+ servers in > > which the ACPI processes basically burn up a whole CPU. I have ACPI > debug > > mode compiled/enabled, but as I'm not actually having any issues per se, > > I'm having trouble with the next steps. This is fairly new Sandy Bridge > > hardware, so I figure it's possible something needs to be fleshed out in > > the code. Every BIOS option relating to ACPI has been flipped back and > > forth, and booting without ACPI support causes a panic. > > > > Here is the verbose boot log as well as the acpidump -dt output, and > other > > interesting bits: > > > > http://nitrology.com/dmesg.acpi > > http://nitrology.com/jason-X9DRT-HF.asl > > > > sysctl hw.acpi: > > hw.acpi.supported_sleep_state: S1 S4 S5 > > hw.acpi.power_button_state: S5 > > hw.acpi.sleep_button_state: S1 > > hw.acpi.lid_switch_state: NONE > > hw.acpi.standby_state: S1 > > hw.acpi.suspend_state: NONE > > hw.acpi.sleep_delay: 1 > > hw.acpi.s4bios: 0 > > hw.acpi.verbose: 1 > > hw.acpi.disable_on_reboot: 0 > > hw.acpi.handle_reboot: 1 > > hw.acpi.reset_video: 0 > > hw.acpi.cpu.cx_lowest: C1 > > > > vmstat -i: > > interrupt total rate > > irq9: acpi0 12170706 14610 > > cpu0: timer 1662074 1995 > > cpu3: timer 1644465 1974 > > cpu4: timer 1644529 1974 > > cpu1: timer 1644423 1974 > > cpu5: timer 1644498 1974 > > cpu2: timer 1644479 1974 > > > > top -SHb: > > last pid: 1979; load averages: 1.39, 1.35, 0.90 up 0+00:13:54 18:46:27 > > 160 processes: 8 running, 119 sleeping, 33 waiting > > > > Mem: 2355M Active, 11G Inact, 7431M Wired, 216K Cache, 6559M Buf, 41G > Free > > Swap: 24G Total, 24G Free > > > > PID USERNAME PRI NICE SIZE RES STATE C TIME WCPU COMMAND > > 11 root 171 ki31 0K 96K RUN 4 11:52 89.70% idle{idle: cpu4} > > 11 root 171 ki31 0K 96K CPU5 5 11:55 86.67% idle{idle: cpu5} > > 11 root 171 ki31 0K 96K CPU2 2 11:14 84.08% idle{idle: cpu2} > > 11 root 171 ki31 0K 96K CPU3 3 9:56 76.76% idle{idle: cpu3} > > 11 root 171 ki31 0K 96K CPU1 1 9:09 70.90% idle{idle: cpu1} > > 11 root 171 ki31 0K 96K RUN 0 9:24 70.07% idle{idle: cpu0} > > 12 root -52 - 0K 528K WAIT 3 3:25 27.29% intr{irq9: acpi0} > > 0 root 8 0 0K 320K CPU4 4 3:39 25.59% kernel{acpi_task_2} > > 0 root 8 0 0K 320K - 2 3:40 25.39% kernel{acpi_task_0} > > 0 root 8 0 0K 320K - 5 3:39 25.20% kernel{acpi_task_1} > > As a first step please add the following to the loader.conf and see what > gets > reported and at what frequency: > debug.acpi.layer="ACPI_EVENTS" > debug.acpi.level="ACPI_LV_INFO > > Also, is your system DTrace-enabled? > > -- > Andriy Gapon > Andriy, I've enabled the info debug level, here is the mere 1600 line resulting boot log. After the system is live I see no ACPI messages being written. I have also enabled DTrace support. http://nitrology.com/acpi.verbose.info Jason From owner-freebsd-acpi@FreeBSD.ORG Fri Nov 9 18:36:14 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 8F59DC62 for ; Fri, 9 Nov 2012 18:36:14 +0000 (UTC) (envelope-from avg@FreeBSD.org) Received: from citadel.icyb.net.ua (citadel.icyb.net.ua [212.40.38.140]) by mx1.freebsd.org (Postfix) with ESMTP id B04568FC0A for ; Fri, 9 Nov 2012 18:36:13 +0000 (UTC) Received: from odyssey.starpoint.kiev.ua (alpha-e.starpoint.kiev.ua [212.40.38.101]) by citadel.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id UAA28783; Fri, 09 Nov 2012 20:36:07 +0200 (EET) (envelope-from avg@FreeBSD.org) Message-ID: <509D4D17.7060703@FreeBSD.org> Date: Fri, 09 Nov 2012 20:36:07 +0200 From: Andriy Gapon User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:16.0) Gecko/20121029 Thunderbird/16.0.2 MIME-Version: 1.0 To: Jason Wolfe Subject: Re: High ACPI CPU usage on a Supermicro X9DRT-HF+ References: <509CAB8C.1000106@FreeBSD.org> In-Reply-To: X-Enigmail-Version: 1.4.5 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: freebsd-acpi@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: Fri, 09 Nov 2012 18:36:14 -0000 on 09/11/2012 20:31 Jason Wolfe said the following: > I've enabled the info debug level, here is the mere 1600 line resulting boot log. > After the system is live I see no ACPI messages being written. I have also > enabled DTrace support. > > http://nitrology.com/acpi.verbose.info Are you sure that you have ACPI_DEBUG option enabled? -- Andriy Gapon From owner-freebsd-acpi@FreeBSD.ORG Sat Nov 10 19:50:04 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 D623A591 for ; Sat, 10 Nov 2012 19:50:04 +0000 (UTC) (envelope-from stefan.horomnea@gmail.com) Received: from mail-we0-f182.google.com (mail-we0-f182.google.com [74.125.82.182]) by mx1.freebsd.org (Postfix) with ESMTP id 690948FC12 for ; Sat, 10 Nov 2012 19:50:04 +0000 (UTC) Received: by mail-we0-f182.google.com with SMTP id x43so2821205wey.13 for ; Sat, 10 Nov 2012 11:50:03 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=PiKxTvAcIMDHm6Cho/HzKIc41XSWiH+uV56yC8MfMx0=; b=x+gpIhJSXScvGHhMd0T36sc7rqAKwux/eGOYTOigQ2sUNTwrL5u2hRCZudpOERdCue XNo21WYjT9S5Mv+Yzo3MsSqX452S9TgSQFbbrRNOyx8crakvwGKuvDOJ1zmtYp3Tc2uV ydvc7OXSXq5O1EN+FaDYy+/y3hkDHXJgCtV0wJX6EOuBw4clo4zB4Rtia8TkREwI2TT9 9nmZpRDVWjIXSAlyzQtUMfM7ir+Q/QRCmGd1DVnfW2xeal/RQhedrTslFZnV9Xpa6zpx EaxUFc5dOFMzSRoc7taCibhhmoSYcjTuE5YV5BUErOw77NrnwC1j09wQSb02sDFb+4sP SCAg== MIME-Version: 1.0 Received: by 10.180.19.197 with SMTP id h5mr8296469wie.22.1352577003207; Sat, 10 Nov 2012 11:50:03 -0800 (PST) Received: by 10.194.65.70 with HTTP; Sat, 10 Nov 2012 11:50:03 -0800 (PST) Date: Sat, 10 Nov 2012 20:50:03 +0100 Message-ID: Subject: Sleep/resume in FreeBSD 9 on a ThinkPad From: Stefan Horomnea To: freebsd-acpi@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 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: Sat, 10 Nov 2012 19:50:05 -0000 Hi, I am enthusiastic to have switched recently to FreeBSD on my laptop. I have been using Linux (Fedora, Ubuntu) in the past few years. I am using FreeBSD 9.0 on a ThinkPad L512. One of my challenges now is to make again my laptop to sleep and resume from sleep correctly. I have read and tried a few things written here: http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/acpi-debug.htmlbut with no luck. What happens is: acpiconf -s 3 seems to get the job done, the hdd and monitor stop, the power button is blinking, so it looks like in the sleep state. But after I push the power button, it reboots instead of coming out of the sleep. I also tried killing X, unloading some of the kernel modules, and then run the sleep command. But it does the same. Debug info: dmesg: http://bit.ly/TSiPCJ asl dump: http://bit.ly/RP559M The files are hosted on dropbox so they are not formatted correctly but you can download them to see them properly. Any help is much appreciated :) Thank you, Stefan