From owner-freebsd-acpi@FreeBSD.ORG Sun Sep 19 16:37:14 2004 Return-Path: Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 93AB816A4CE for ; Sun, 19 Sep 2004 16:37:14 +0000 (GMT) Received: from sianna.shopkeeper.de (sianna.shopkeeper.de [217.17.196.5]) by mx1.FreeBSD.org (Postfix) with ESMTP id 58B7143D2F for ; Sun, 19 Sep 2004 16:37:13 +0000 (GMT) (envelope-from sklauder@trimind.de) Received: from avalon.dobu.local (p5090B381.dip.t-dialin.net [80.144.179.129]) (authenticated bits=0) by sianna.shopkeeper.de (8.13.1/8.13.1) with ESMTP id i8JGbG5X069110; Sun, 19 Sep 2004 18:37:17 +0200 (CEST) (envelope-from sklauder@trimind.de) Received: from avalon.dobu.local (localhost.dobu.local [127.0.0.1]) by avalon.dobu.local (8.13.1/8.12.11) with ESMTP id i8JGb7CI001913; Sun, 19 Sep 2004 18:37:07 +0200 (CEST) (envelope-from sklauder@avalon.dobu.local) Received: (from sklauder@localhost) by avalon.dobu.local (8.13.1/8.13.1/Submit) id i8JGb65W001912; Sun, 19 Sep 2004 18:37:06 +0200 (CEST) (envelope-from sklauder) Date: Sun, 19 Sep 2004 18:37:06 +0200 From: Sascha Klauder To: Nate Lawson Message-ID: <20040919163706.GA904@trimind.de> References: <37F890616C995246BE76B3E6B2DBE05502071306@orsmsx403.amr.corp.intel.com> <414CA156.7040606@root.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <414CA156.7040606@root.org> User-Agent: Mutt/1.4.2.1i X-Virus-Scanned: by amavisd-new cc: freebsd-acpi@freebsd.org cc: "Moore, Robert" Subject: Re: trouble overriding DSDT X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 19 Sep 2004 16:37:14 -0000 On Sat, Sep 18, 2004 at 01:57:58PM -0700, Nate Lawson wrote: > To do this on freebsd, build the module with options ACPI_DEBUG and then > set the loader variables of debug.acpi.layer and debug.acpi.level > according to the man page. I suggest to start with: > > debug.acpi.layer="ACPI_ALL_COMPONENTS" > debug.acpi.level="ACPI_LV_ALL_EXCEPTIONS" Ok, just tried that. Unfortunately, I was unable to get the serial console working (it was just outputting garbage, while the same setup (cabling, software) works just fine as soon as the kernel has finished booting), so I had to transcribe the parts looking most re- levant to me: [...information about RDSP locating and RSDT, XSDT, FACP, BOOT, SSDT and FACS table loading...] tbinstall-0176 [07] TbMatchSignature : Table [DSDT] is an ACPI table consumed by the core subsystem ACPI: DSDT was overridden. tbget-0497 [08] TbGetThisTable : Found table [DSDT] at 200000c07b4a54, mapped/copied to 0xc1989028 tbget-0374: *** Info: Table [DSDT] replaced by host OS tbinstall-0233 [06] TbInstallTable : DSDT located at 0xc1989028 tbxface-0195 [03] AcpiLoadTables : ACPI Tables successfully aquired nsload-0264 [05] NsLoadTableByType : Loading DSDT nsload-0171 [06] NsLoadTable : AML block at 0xc198904c nsload-0190 [06] NsLoadTable : *** Loading table into namespace *** nsload-0213 [06] NsLoadTable : *** Begin Table Method Parsing and Object Initialization *** Parsing all Control Methods:................................................. .............................[...]... Table [DSDT](id f005) - 756 Objects with 52 Devices 254 Methods 17 Regions nsload-0289 [06] NsLoadTable : *** Completed Table Method Parsing and Object Initialization *** nsload-0289 [05] NsLoadTableByType : Loading 1 SSDTs nsload-0171 [06] NsLoadTable : AML block at 0xd421eeeb nsload-0190 [06] NsLoadTable : *** Loading table into namespace *** dswload-0380: *** Error: Looking up [_PCT] in namespace, AE_ALREADY_EXISTS psparse-0710 [10] PsParseLoop : During name lookup/catalog, AE_ALREADY_EXISTS psparse-1303: *** Error: [NULL NAME], AE_ALREADY_EXISTS Fatal trap 12: page fault while in kernel mode [...] Cheers, -sascha From owner-freebsd-acpi@FreeBSD.ORG Sun Sep 19 21:08:00 2004 Return-Path: Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A42AF16A4DF for ; Sun, 19 Sep 2004 21:08:00 +0000 (GMT) Received: from ylpvm01.prodigy.net (ylpvm01-ext.prodigy.net [207.115.57.32]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4A19343D2F for ; Sun, 19 Sep 2004 21:08:00 +0000 (GMT) (envelope-from nate@root.org) Received: from [10.0.5.52] (adsl-64-171-186-250.dsl.snfc21.pacbell.net [64.171.186.250])i8JL7swn014599; Sun, 19 Sep 2004 17:07:55 -0400 Message-ID: <414DF52E.1030109@root.org> Date: Sun, 19 Sep 2004 14:07:58 -0700 From: Nate Lawson User-Agent: Mozilla Thunderbird 0.7.3 (X11/20040901) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Sascha Klauder References: <37F890616C995246BE76B3E6B2DBE05502071306@orsmsx403.amr.corp.intel.com> <414CA156.7040606@root.org> <20040919163706.GA904@trimind.de> In-Reply-To: <20040919163706.GA904@trimind.de> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit cc: freebsd-acpi@freebsd.org cc: "Moore, Robert" Subject: Re: trouble overriding DSDT X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 19 Sep 2004 21:08:00 -0000 Sascha Klauder wrote: > On Sat, Sep 18, 2004 at 01:57:58PM -0700, Nate Lawson wrote: > >>To do this on freebsd, build the module with options ACPI_DEBUG and then >>set the loader variables of debug.acpi.layer and debug.acpi.level >>according to the man page. I suggest to start with: >> >>debug.acpi.layer="ACPI_ALL_COMPONENTS" >>debug.acpi.level="ACPI_LV_ALL_EXCEPTIONS" > > Ok, just tried that. Unfortunately, I was unable to get the serial > console working (it was just outputting garbage, while the same > setup (cabling, software) works just fine as soon as the kernel has > finished booting), so I had to transcribe the parts looking most re- > levant to me: > > tbget-0497 [08] TbGetThisTable : Found table [DSDT] at 200000c07b4a54, mapped/copied to 0xc1989028 > tbget-0374: *** Info: Table [DSDT] replaced by host OS > tbinstall-0233 [06] TbInstallTable : DSDT located at 0xc1989028 > tbxface-0195 [03] AcpiLoadTables : ACPI Tables successfully aquired > nsload-0264 [05] NsLoadTableByType : Loading DSDT > nsload-0171 [06] NsLoadTable : AML block at 0xc198904c > nsload-0190 [06] NsLoadTable : *** Loading table into namespace *** > nsload-0289 [06] NsLoadTable : *** Completed Table Method Parsing and Object Initialization *** > nsload-0289 [05] NsLoadTableByType : Loading 1 SSDTs ^^^^^^^^^^^^^^^^ There's your problem. > nsload-0171 [06] NsLoadTable : AML block at 0xd421eeeb > nsload-0190 [06] NsLoadTable : *** Loading table into namespace *** > dswload-0380: *** Error: Looking up [_PCT] in namespace, AE_ALREADY_EXISTS > psparse-0710 [10] PsParseLoop : During name lookup/catalog, AE_ALREADY_EXISTS > psparse-1303: *** Error: [NULL NAME], AE_ALREADY_EXISTS > > Fatal trap 12: page fault while in kernel mode > [...] When we disassemble the DSDT in acpidump(8), we also disassemble any SSDTs as well. When you override the DSDT, you are loading a combined DSDT+SSDT table but the original SSDT is still in memory. Thus you get the duplicated namespace values. An easy way to test this is to comment out everything in your ASL from the Scope(...CPU0) to the end, recompile, load it, then if it boots ok, do another acpidump and diff the two. If I'm right, you'll find commenting out some part gets you the same ASL after booting with the custom one. The right fix I think is to disable SSDT loading if we've overridden the DSDT. Bob, what do you think? Marcel, we should fix this for 5.3R because it will prevent people from using custom ASL easily. Another quick fix would be to put a comment block around the disassembled SSDT so it is there for inspection but doesn't affect recompilation. -Nate From owner-freebsd-acpi@FreeBSD.ORG Sun Sep 19 21:55:51 2004 Return-Path: Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5FD2016A4CE for ; Sun, 19 Sep 2004 21:55:51 +0000 (GMT) Received: from ns1.xcllnt.net (209-128-86-226.bayarea.net [209.128.86.226]) by mx1.FreeBSD.org (Postfix) with ESMTP id EC1F843D31 for ; Sun, 19 Sep 2004 21:55:50 +0000 (GMT) (envelope-from marcel@xcllnt.net) Received: from dhcp44.pn.xcllnt.net (dhcp44.pn.xcllnt.net [192.168.4.244]) by ns1.xcllnt.net (8.13.1/8.13.1) with ESMTP id i8JLtoRD032153; Sun, 19 Sep 2004 14:55:50 -0700 (PDT) (envelope-from marcel@piii.pn.xcllnt.net) Received: from dhcp44.pn.xcllnt.net (localhost [127.0.0.1]) by dhcp44.pn.xcllnt.net (8.13.1/8.13.1) with ESMTP id i8JLtoQd040492; Sun, 19 Sep 2004 14:55:50 -0700 (PDT) (envelope-from marcel@dhcp44.pn.xcllnt.net) Received: (from marcel@localhost) by dhcp44.pn.xcllnt.net (8.13.1/8.13.1/Submit) id i8JLtnkH040490; Sun, 19 Sep 2004 14:55:49 -0700 (PDT) (envelope-from marcel) Date: Sun, 19 Sep 2004 14:55:49 -0700 From: Marcel Moolenaar To: Nate Lawson Message-ID: <20040919215548.GA37391@dhcp44.pn.xcllnt.net> References: <37F890616C995246BE76B3E6B2DBE05502071306@orsmsx403.amr.corp.intel.com> <414CA156.7040606@root.org> <20040919163706.GA904@trimind.de> <414DF52E.1030109@root.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <414DF52E.1030109@root.org> User-Agent: Mutt/1.4.2.1i cc: Sascha Klauder cc: "Moore, Robert" cc: freebsd-acpi@freebsd.org Subject: Re: trouble overriding DSDT X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 19 Sep 2004 21:55:51 -0000 On Sun, Sep 19, 2004 at 02:07:58PM -0700, Nate Lawson wrote: > > The right fix I think is to disable SSDT loading if we've overridden the > DSDT. Bob, what do you think? Marcel, we should fix this for 5.3R > because it will prevent people from using custom ASL easily. Another > quick fix would be to put a comment block around the disassembled SSDT > so it is there for inspection but doesn't affect recompilation. Tricky. The advantage of SSDTs is that it allows you to modularize, which means that one may want to be able to override a single SSDT. In that case, overriding the DSDT does not automaticly imply that none of the SSDTs should be loaded. If by default we do load SSDTs when overriding the DSDT (like we happen to do now by coincidence), we should not dump any SSDTs by default in acpidump(8) and vice versa. This also means that we should be able to just dump some SSDT and override just some SSDT. If overriding is acceptable to be an all or nothing approach, then acpidump(8) behaves correctly and we just need to stop loading SSDTs when the DSDT is overridden. I prefer the flexibility and given that we currently do load SSDTs, it makes sense to at least enhance acpidump(8) to make dumping the SSDTs optional when dumping the DSDT. Irrespective of what we'll do in the future. This would be a good compromise to put in 5.3R... -- Marcel Moolenaar USPA: A-39004 marcel@xcllnt.net From owner-freebsd-acpi@FreeBSD.ORG Sun Sep 19 22:20:05 2004 Return-Path: Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2194916A4CE for ; Sun, 19 Sep 2004 22:20:05 +0000 (GMT) Received: from sianna.shopkeeper.de (sianna.shopkeeper.de [217.17.196.5]) by mx1.FreeBSD.org (Postfix) with ESMTP id 243B543D1F for ; Sun, 19 Sep 2004 22:20:04 +0000 (GMT) (envelope-from sklauder@trimind.de) Received: from avalon.dobu.local (p5090B381.dip.t-dialin.net [80.144.179.129]) (authenticated bits=0) by sianna.shopkeeper.de (8.13.1/8.13.1) with ESMTP id i8JMK8d6080884; Mon, 20 Sep 2004 00:20:09 +0200 (CEST) (envelope-from sklauder@trimind.de) Received: from avalon.dobu.local (localhost.dobu.local [127.0.0.1]) by avalon.dobu.local (8.13.1/8.12.11) with ESMTP id i8JMJxmr018165; Mon, 20 Sep 2004 00:19:59 +0200 (CEST) (envelope-from sklauder@avalon.dobu.local) Received: (from sklauder@localhost) by avalon.dobu.local (8.13.1/8.13.1/Submit) id i8JMJwK4018164; Mon, 20 Sep 2004 00:19:58 +0200 (CEST) (envelope-from sklauder) Date: Mon, 20 Sep 2004 00:19:58 +0200 From: Sascha Klauder To: Nate Lawson Message-ID: <20040919221958.GA17850@trimind.de> References: <37F890616C995246BE76B3E6B2DBE05502071306@orsmsx403.amr.corp.intel.com> <414CA156.7040606@root.org> <20040919163706.GA904@trimind.de> <414DF52E.1030109@root.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <414DF52E.1030109@root.org> User-Agent: Mutt/1.4.2.1i X-Virus-Scanned: by amavisd-new cc: freebsd-acpi@freebsd.org cc: "Moore, Robert" Subject: Re: trouble overriding DSDT X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: sklauder@trimind.de List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 19 Sep 2004 22:20:05 -0000 On Sun, Sep 19, 2004 at 02:07:58PM -0700, Nate Lawson wrote: > SSDTs as well. When you override the DSDT, you are loading a combined > DSDT+SSDT table but the original SSDT is still in memory. Thus you get > the duplicated namespace values. An easy way to test this is to comment > out everything in your ASL from the Scope(...CPU0) to the end, Yes, that did the trick! > recompile, load it, then if it boots ok, do another acpidump and diff > the two. If I'm right, you'll find commenting out some part gets you > the same ASL after booting with the custom one. Right, the ASLs are effectively the same, with the exception that the very changes I did in the first place now seem to be "backed out". Is this the supposed behaviour when the DSDT is overridden (i.e. acpidump(8) always dumps the DSDT pro- vided by the BIOS (or something to that effect))? Cheers, -sascha From owner-freebsd-acpi@FreeBSD.ORG Mon Sep 20 05:30:29 2004 Return-Path: Delivered-To: freebsd-acpi@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id BC1B516A4CE for ; Mon, 20 Sep 2004 05:30:29 +0000 (GMT) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id A994443D4C for ; Mon, 20 Sep 2004 05:30:29 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.12.11/8.12.11) with ESMTP id i8K5UTeV043568 for ; Mon, 20 Sep 2004 05:30:29 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.12.11/8.12.11/Submit) id i8K5UTmK043561; Mon, 20 Sep 2004 05:30:29 GMT (envelope-from gnats) Date: Mon, 20 Sep 2004 05:30:29 GMT Message-Id: <200409200530.i8K5UTmK043561@freefall.freebsd.org> To: freebsd-acpi@FreeBSD.org From: supraexpress@globaleyes.net Subject: Re: i386/60817: FBSD-5.1/5.2-RC1 "fdc0: cmd 3 failed at out byte 1 of 3" X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: supraexpress@globaleyes.net List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 20 Sep 2004 05:30:29 -0000 The following reply was made to PR i386/60817; it has been noted by GNATS. From: supraexpress@globaleyes.net To: freebsd-gnats-submit@FreeBSD.org Cc: Subject: Re: i386/60817: FBSD-5.1/5.2-RC1 "fdc0: cmd 3 failed at out byte 1 of 3" Date: Mon, 20 Sep 2004 00:28:21 -0500 (CDT) FBSD-5.3-Beta5 has FIXED the problem with my floppy drive. I have tested it and it appears to work just fine under ACPI. THANK YOU! You may close out PR#60817. On 5 Sep, To: freebsd-gnats-submit@FreeBSD.org wrote: > MSI MS-6758 875P Neo + ACPI with FBSD-5.3-Beta3 SESNAP 09/04/2004 and > FBSD-6.0-CURRENT SESNAP 09/04/2004 is still unable to use FDC0 with ACPI > enabled: > > fdc0: port 0x3f7, 0x3f4-0x3f5, 0x3fs-0x3f3 irq > 6 drq 2 on acpi0 > [FBSD-6.0] fdc0: does not respond > [FBSD-5.3] fdc0: cmd 3 failed at out byte 1 of 3 > device_attach: fdc0 attach returned 6 > > Disabling ACPI allows the floppy controller to be "properly" determined > and set up. > Running without ACPI is not a problem for me since I don't have a laptop > and have no > need for "power controls". No modifications to DSDT were made. > From owner-freebsd-acpi@FreeBSD.ORG Mon Sep 20 05:35:40 2004 Return-Path: Delivered-To: freebsd-acpi@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D66FE16A4CF; Mon, 20 Sep 2004 05:35:40 +0000 (GMT) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id AEA7D43D54; Mon, 20 Sep 2004 05:35:40 +0000 (GMT) (envelope-from imp@FreeBSD.org) Received: from freefall.freebsd.org (imp@localhost [127.0.0.1]) i8K5Ze6b043814; Mon, 20 Sep 2004 05:35:40 GMT (envelope-from imp@freefall.freebsd.org) Received: (from imp@localhost) by freefall.freebsd.org (8.12.11/8.12.11/Submit) id i8K5ZeYx043810; Sun, 19 Sep 2004 23:35:40 -0600 (MDT) (envelope-from imp) Date: Sun, 19 Sep 2004 23:35:40 -0600 (MDT) From: Warner Losh Message-Id: <200409200535.i8K5ZeYx043810@freefall.freebsd.org> To: supraexpress@globaleyes.net, imp@FreeBSD.org, freebsd-acpi@FreeBSD.org Subject: Re: i386/60817: FBSD-5.1/5.2-RC1 "fdc0: cmd 3 failed at out byte 1 of 3" X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 20 Sep 2004 05:35:41 -0000 Synopsis: FBSD-5.1/5.2-RC1 "fdc0: cmd 3 failed at out byte 1 of 3" State-Changed-From-To: feedback->closed State-Changed-By: imp State-Changed-When: Sun Sep 19 23:35:20 MDT 2004 State-Changed-Why: Closed! Fixed in head and releng_5, nothing else matters. http://www.freebsd.org/cgi/query-pr.cgi?pr=60817 From owner-freebsd-acpi@FreeBSD.ORG Mon Sep 20 06:19:56 2004 Return-Path: Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8390016A4CE for ; Mon, 20 Sep 2004 06:19:56 +0000 (GMT) Received: from ylpvm01.prodigy.net (ylpvm01-ext.prodigy.net [207.115.57.32]) by mx1.FreeBSD.org (Postfix) with ESMTP id 28D5743D41 for ; Mon, 20 Sep 2004 06:19:56 +0000 (GMT) (envelope-from nate@root.org) Received: from [10.0.5.52] (adsl-64-171-186-250.dsl.snfc21.pacbell.net [64.171.186.250])i8K6Jown027868; Mon, 20 Sep 2004 02:19:51 -0400 Message-ID: <414E7689.80703@root.org> Date: Sun, 19 Sep 2004 23:19:53 -0700 From: Nate Lawson User-Agent: Mozilla Thunderbird 0.7.3 (X11/20040901) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Marcel Moolenaar References: <37F890616C995246BE76B3E6B2DBE05502071306@orsmsx403.amr.corp.intel.com> <414CA156.7040606@root.org> <20040919163706.GA904@trimind.de> <414DF52E.1030109@root.org> <20040919215548.GA37391@dhcp44.pn.xcllnt.net> In-Reply-To: <20040919215548.GA37391@dhcp44.pn.xcllnt.net> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit cc: Sascha Klauder cc: "Moore, Robert" cc: freebsd-acpi@freebsd.org Subject: Re: trouble overriding DSDT X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 20 Sep 2004 06:19:56 -0000 Marcel Moolenaar wrote: > On Sun, Sep 19, 2004 at 02:07:58PM -0700, Nate Lawson wrote: > >>The right fix I think is to disable SSDT loading if we've overridden the >>DSDT. Bob, what do you think? Marcel, we should fix this for 5.3R >>because it will prevent people from using custom ASL easily. Another >>quick fix would be to put a comment block around the disassembled SSDT >>so it is there for inspection but doesn't affect recompilation. > > > Tricky. The advantage of SSDTs is that it allows you to modularize, > which means that one may want to be able to override a single SSDT. > In that case, overriding the DSDT does not automaticly imply that > none of the SSDTs should be loaded. > > If by default we do load SSDTs when overriding the DSDT (like we happen > to do now by coincidence), we should not dump any SSDTs by default in > acpidump(8) and vice versa. This also means that we should be able to > just dump some SSDT and override just some SSDT. > > If overriding is acceptable to be an all or nothing approach, then > acpidump(8) behaves correctly and we just need to stop loading SSDTs > when the DSDT is overridden. Overriding is only for debugging or for known-bad machines. So I think it's acceptable for the user to pass a combined/hacked DSDT+SSDT and have it override all DSDT/SSDT tables. This is the way I'd like to handle this. For now, I think it makes sense to put the SSDT in a comment block in acpidump(8) so that recompiling and overriding works properly and the SSDT is still available for examining. We can do the first fix in -current but we need something for 5.3. Objections? > I prefer the flexibility and given that we currently do load SSDTs, it > makes sense to at least enhance acpidump(8) to make dumping the SSDTs > optional when dumping the DSDT. Irrespective of what we'll do in the > future. This would be a good compromise to put in 5.3R... I'd like to still dump it but comment it out. This gives the info in the SSDT but points out that it's read-only. -Nate From owner-freebsd-acpi@FreeBSD.ORG Mon Sep 20 06:20:39 2004 Return-Path: Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B69E116A4CE for ; Mon, 20 Sep 2004 06:20:39 +0000 (GMT) Received: from ylpvm01.prodigy.net (ylpvm01-ext.prodigy.net [207.115.57.32]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7151543D2F for ; Mon, 20 Sep 2004 06:20:39 +0000 (GMT) (envelope-from nate@root.org) Received: from [10.0.5.52] (adsl-64-171-186-250.dsl.snfc21.pacbell.net [64.171.186.250])i8K6KYwn028426; Mon, 20 Sep 2004 02:20:35 -0400 Message-ID: <414E76B6.1010107@root.org> Date: Sun, 19 Sep 2004 23:20:38 -0700 From: Nate Lawson User-Agent: Mozilla Thunderbird 0.7.3 (X11/20040901) X-Accept-Language: en-us, en MIME-Version: 1.0 To: sklauder@trimind.de References: <37F890616C995246BE76B3E6B2DBE05502071306@orsmsx403.amr.corp.intel.com> <414CA156.7040606@root.org> <20040919163706.GA904@trimind.de> <414DF52E.1030109@root.org> <20040919221958.GA17850@trimind.de> In-Reply-To: <20040919221958.GA17850@trimind.de> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit cc: freebsd-acpi@freebsd.org cc: "Moore, Robert" Subject: Re: trouble overriding DSDT X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 20 Sep 2004 06:20:39 -0000 Sascha Klauder wrote: > On Sun, Sep 19, 2004 at 02:07:58PM -0700, Nate Lawson wrote: > >>SSDTs as well. When you override the DSDT, you are loading a combined >>DSDT+SSDT table but the original SSDT is still in memory. Thus you get >>the duplicated namespace values. An easy way to test this is to comment >>out everything in your ASL from the Scope(...CPU0) to the end, > > > Yes, that did the trick! > > >>recompile, load it, then if it boots ok, do another acpidump and diff >>the two. If I'm right, you'll find commenting out some part gets you >>the same ASL after booting with the custom one. > > > Right, the ASLs are effectively the same, with the exception > that the very changes I did in the first place now seem to be > "backed out". Is this the supposed behaviour when the DSDT > is overridden (i.e. acpidump(8) always dumps the DSDT pro- > vided by the BIOS (or something to that effect))? Oh, sorry. Yes, acpidump(8) will always pull the underlying "real" table from memory. -Nate From owner-freebsd-acpi@FreeBSD.ORG Mon Sep 20 11:02:07 2004 Return-Path: Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1038B16A4CF for ; Mon, 20 Sep 2004 11:02:07 +0000 (GMT) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0347F43D49 for ; Mon, 20 Sep 2004 11:02:07 +0000 (GMT) (envelope-from owner-bugmaster@freebsd.org) Received: from freefall.freebsd.org (peter@localhost [127.0.0.1]) by freefall.freebsd.org (8.12.11/8.12.11) with ESMTP id i8KB26ui001347 for ; Mon, 20 Sep 2004 11:02:06 GMT (envelope-from owner-bugmaster@freebsd.org) Received: (from peter@localhost) by freefall.freebsd.org (8.12.11/8.12.11/Submit) id i8KB25mP001341 for freebsd-acpi@freebsd.org; Mon, 20 Sep 2004 11:02:05 GMT (envelope-from owner-bugmaster@freebsd.org) Date: Mon, 20 Sep 2004 11:02:05 GMT Message-Id: <200409201102.i8KB25mP001341@freefall.freebsd.org> X-Authentication-Warning: freefall.freebsd.org: peter set sender to owner-bugmaster@freebsd.org using -f From: FreeBSD bugmaster To: freebsd-acpi@FreeBSD.org Subject: Current problem reports assigned to you X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 20 Sep 2004 11:02:07 -0000 Current FreeBSD problem reports Critical problems Serious problems S Submitted Tracker Resp. Description ------------------------------------------------------------------------------- o [2003/06/07] kern/53008 acpi [PATCH] genwakecode generates errornously o [2003/07/22] i386/54756 acpi ACPI suspend/resume problem on CF-W2 lapt o [2003/08/20] kern/55822 acpi No ACPI power off with SMP kernel f [2003/09/10] kern/56659 acpi ACPI trouble on IBM ThinkPad X31 f [2003/12/17] i386/60317 acpi FreeBSD 5.2rc1 doesn't boot with ACPI ena o [2004/03/09] i386/64002 acpi acpi problem o [2004/05/27] i386/67273 acpi [hang] system hangs with acpi and Xfree 7 problems total. Non-critical problems S Submitted Tracker Resp. Description ------------------------------------------------------------------------------- f [2004/01/22] i386/61703 acpi ACPI + Sound + Boot = Reboot o [2004/03/17] kern/64365 acpi ACPI problems f [2004/05/25] i386/67189 acpi ACPI S3 reboot computer on Dell Latitude o [2004/05/28] kern/67309 acpi zzz reboot computer (ACPI S3) f [2004/06/23] i386/68219 acpi ACPI + snd_maestro3 problem o [2004/07/29] i386/69750 acpi Boot without ACPI failed on ASUS L5 6 problems total. From owner-freebsd-acpi@FreeBSD.ORG Mon Sep 20 15:59:54 2004 Return-Path: Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 84E4416A4CE for ; Mon, 20 Sep 2004 15:59:54 +0000 (GMT) Received: from mail2.speakeasy.net (mail2.speakeasy.net [216.254.0.202]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5921843D5C for ; Mon, 20 Sep 2004 15:59:54 +0000 (GMT) (envelope-from jhb@FreeBSD.org) Received: (qmail 1257 invoked from network); 20 Sep 2004 15:59:53 -0000 Received: from dsl027-160-063.atl1.dsl.speakeasy.net (HELO server.baldwin.cx) ([216.27.160.63]) (envelope-sender ) encrypted SMTP for ; 20 Sep 2004 15:59:53 -0000 Received: from [10.50.40.210] (gw1.twc.weather.com [216.133.140.1]) (authenticated bits=0) by server.baldwin.cx (8.12.11/8.12.11) with ESMTP id i8KFxiu9023593; Mon, 20 Sep 2004 11:59:44 -0400 (EDT) (envelope-from jhb@FreeBSD.org) From: John Baldwin To: freebsd-acpi@FreeBSD.org Date: Mon, 20 Sep 2004 11:59:33 -0400 User-Agent: KMail/1.6.2 References: <37F890616C995246BE76B3E6B2DBE05502071306@orsmsx403.amr.corp.intel.com> <20040919215548.GA37391@dhcp44.pn.xcllnt.net> <414E7689.80703@root.org> In-Reply-To: <414E7689.80703@root.org> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200409201159.33995.jhb@FreeBSD.org> X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on server.baldwin.cx cc: Sascha Klauder cc: "Moore, Robert" Subject: Re: trouble overriding DSDT X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 20 Sep 2004 15:59:54 -0000 On Monday 20 September 2004 02:19 am, Nate Lawson wrote: > Marcel Moolenaar wrote: > > On Sun, Sep 19, 2004 at 02:07:58PM -0700, Nate Lawson wrote: > >>The right fix I think is to disable SSDT loading if we've overridden the > >>DSDT. Bob, what do you think? Marcel, we should fix this for 5.3R > >>because it will prevent people from using custom ASL easily. Another > >>quick fix would be to put a comment block around the disassembled SSDT > >>so it is there for inspection but doesn't affect recompilation. > > > > Tricky. The advantage of SSDTs is that it allows you to modularize, > > which means that one may want to be able to override a single SSDT. > > In that case, overriding the DSDT does not automaticly imply that > > none of the SSDTs should be loaded. > > > > If by default we do load SSDTs when overriding the DSDT (like we happen > > to do now by coincidence), we should not dump any SSDTs by default in > > acpidump(8) and vice versa. This also means that we should be able to > > just dump some SSDT and override just some SSDT. > > > > If overriding is acceptable to be an all or nothing approach, then > > acpidump(8) behaves correctly and we just need to stop loading SSDTs > > when the DSDT is overridden. > > Overriding is only for debugging or for known-bad machines. So I think > it's acceptable for the user to pass a combined/hacked DSDT+SSDT and > have it override all DSDT/SSDT tables. This is the way I'd like to > handle this. > > For now, I think it makes sense to put the SSDT in a comment block in > acpidump(8) so that recompiling and overriding works properly and the > SSDT is still available for examining. We can do the first fix in > -current but we need something for 5.3. > > Objections? I think it's a good idea to override all the DSDT+SSDT's when you load a new dsdt. Otherwise it just makes things much more complicated for the user to have to know what lives in different SSDT's, etc. If acpidump continues to dump a full table that can then be compiled into a single foo.dsdt that makes the user interface a lot simpler and easier to manage. -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve" = http://www.FreeBSD.org From owner-freebsd-acpi@FreeBSD.ORG Mon Sep 20 18:59:44 2004 Return-Path: Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id AF75716A4D2; Mon, 20 Sep 2004 18:59:44 +0000 (GMT) Received: from crumpet.united-ware.com (ddsl-66-42-172-210.fuse.net [66.42.172.210]) by mx1.FreeBSD.org (Postfix) with ESMTP id C824F43D69; Mon, 20 Sep 2004 18:59:43 +0000 (GMT) (envelope-from mistry.7@osu.edu) Received: from [192.168.0.6] (adsl-68-250-185-35.dsl.wotnoh.ameritech.net [68.250.185.35]) (authenticated bits=0)i8KIj5HR023489 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NO); Mon, 20 Sep 2004 14:45:06 -0400 (EDT) (envelope-from mistry.7@osu.edu) From: Anish Mistry To: freebsd-current@freebsd.org, freebsd-acpi@freebsd.org Date: Mon, 20 Sep 2004 15:01:30 -0400 User-Agent: KMail/1.7 MIME-Version: 1.0 Content-Type: Multipart/Mixed; boundary="Boundary-00=_ckyTBOvqhu/kXeL" Message-Id: <200409201501.48755.mistry.7@osu.edu> X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.64 X-Spam-Checker-Version: SpamAssassin 2.64 (2004-01-11) on crumpet.united-ware.com X-Content-Filtered-By: Mailman/MimeDel 2.1.1 Subject: RELENG_5 panic: mtx_lock() with ACPI X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 20 Sep 2004 18:59:44 -0000 --Boundary-00=_ckyTBOvqhu/kXeL Content-Type: multipart/signed; boundary="nextPart3714879.qVzd4VjKlY"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit --nextPart3714879.qVzd4VjKlY Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline I'm getting the following panic on boot only with ACPI enabled. On a verbose boot right after: start_init: trying /sbin/init panic: mtx_lock() of spin mutex(null) @ /usr/src/sys/tty/tty.c:2809 Can't seem to get a dump even if dumpdev is set at the loader prompt. Verbose boot without ACPI enabled and ASL attached. =2D-=20 Anish Mistry --nextPart3714879.qVzd4VjKlY Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (FreeBSD) iD8DBQBBTykcxqA5ziudZT0RAofBAKCoR2zeqpdhcvCMqdeuTg7qzlAFFACff/iL 9JIyMNy2D5qdyXS1imFUu2A= =2J0s -----END PGP SIGNATURE----- --nextPart3714879.qVzd4VjKlY-- --Boundary-00=_ckyTBOvqhu/kXeL-- From owner-freebsd-acpi@FreeBSD.ORG Mon Sep 20 19:08:57 2004 Return-Path: Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9390016A4CF for ; Mon, 20 Sep 2004 19:08:57 +0000 (GMT) Received: from crumpet.united-ware.com (ddsl-66-42-172-210.fuse.net [66.42.172.210]) by mx1.FreeBSD.org (Postfix) with ESMTP id 35EDE43D48 for ; Mon, 20 Sep 2004 19:08:57 +0000 (GMT) (envelope-from mistry.7@osu.edu) Received: from [192.168.0.6] (adsl-68-250-185-35.dsl.wotnoh.ameritech.net [68.250.185.35]) (authenticated bits=0)i8KIsIHR023517 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NO) for ; Mon, 20 Sep 2004 14:54:19 -0400 (EDT) (envelope-from mistry.7@osu.edu) From: Anish Mistry To: freebsd-acpi@freebsd.org Date: Mon, 20 Sep 2004 15:11:02 -0400 User-Agent: KMail/1.7 References: <200409201501.48755.mistry.7@osu.edu> In-Reply-To: <200409201501.48755.mistry.7@osu.edu> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart3523794.ZFyZtnDpBr"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200409201511.02523.mistry.7@osu.edu> X-Spam-Status: No, hits=0.8 required=5.0 tests=BIZ_TLD autolearn=no version=2.64 X-Spam-Checker-Version: SpamAssassin 2.64 (2004-01-11) on crumpet.united-ware.com Subject: Re: RELENG_5 panic: mtx_lock() with ACPI X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 20 Sep 2004 19:08:57 -0000 --nextPart3523794.ZFyZtnDpBr Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Monday 20 September 2004 03:01 pm, Anish Mistry wrote: > I'm getting the following panic on boot only with ACPI enabled. > On a verbose boot right after: start_init: trying /sbin/init > panic: mtx_lock() of spin mutex(null) @ /usr/src/sys/tty/tty.c:2809 > Can't seem to get a dump even if dumpdev is set at the loader prompt. > > Verbose boot without ACPI enabled and ASL attached. Attachments got stripped. http://am-productions.biz/debug/BIGGUY-dmesg.txt.gz http://am-productions.biz/debug/bigguy.asl.gz =2D-=20 Anish Mistry --nextPart3523794.ZFyZtnDpBr Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (FreeBSD) iD8DBQBBTytGxqA5ziudZT0RAg1VAJ0dHh3KGWHMwKIdfxALcgngPWAvlQCfTXZ3 h4S1CHzmZduL3ZXJVH8YqWo= =R5j4 -----END PGP SIGNATURE----- --nextPart3523794.ZFyZtnDpBr-- From owner-freebsd-acpi@FreeBSD.ORG Mon Sep 20 19:35:28 2004 Return-Path: Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id EF4D016A57A for ; Mon, 20 Sep 2004 19:35:28 +0000 (GMT) Received: from www.cryptography.com (li-22.members.linode.com [64.5.53.22]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9D40F43D46 for ; Mon, 20 Sep 2004 19:35:21 +0000 (GMT) (envelope-from nate@root.org) Received: from [10.0.0.34] (adsl-67-127-84-57.dsl.snfc21.pacbell.net [67.127.84.57]) by www.cryptography.com (8.12.8/8.12.8) with ESMTP id i8KJZJDl009138; Mon, 20 Sep 2004 12:35:19 -0700 Message-ID: <414F30E9.4060300@root.org> Date: Mon, 20 Sep 2004 12:35:05 -0700 From: Nate Lawson User-Agent: Mozilla Thunderbird 0.7.3 (Windows/20040803) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Anish Mistry References: <200409201501.48755.mistry.7@osu.edu> <200409201511.02523.mistry.7@osu.edu> In-Reply-To: <200409201511.02523.mistry.7@osu.edu> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit cc: freebsd-acpi@freebsd.org Subject: Re: RELENG_5 panic: mtx_lock() with ACPI X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 20 Sep 2004 19:35:29 -0000 Anish Mistry wrote: > On Monday 20 September 2004 03:01 pm, Anish Mistry wrote: > >>I'm getting the following panic on boot only with ACPI enabled. >>On a verbose boot right after: start_init: trying /sbin/init >>panic: mtx_lock() of spin mutex(null) @ /usr/src/sys/tty/tty.c:2809 >>Can't seem to get a dump even if dumpdev is set at the loader prompt. >> >>Verbose boot without ACPI enabled and ASL attached. > > Attachments got stripped. > http://am-productions.biz/debug/BIGGUY-dmesg.txt.gz > http://am-productions.biz/debug/bigguy.asl.gz Can you send a backtrace ("tr" from ddb)? -- Nate From owner-freebsd-acpi@FreeBSD.ORG Mon Sep 20 19:54:33 2004 Return-Path: Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id EF10D16A4CE for ; Mon, 20 Sep 2004 19:54:33 +0000 (GMT) Received: from crumpet.united-ware.com (ddsl-66-42-172-210.fuse.net [66.42.172.210]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8BCAC43D4C for ; Mon, 20 Sep 2004 19:54:33 +0000 (GMT) (envelope-from mistry.7@osu.edu) Received: from [192.168.0.6] (adsl-68-250-185-35.dsl.wotnoh.ameritech.net [68.250.185.35]) (authenticated bits=0)i8KJdsHR023578 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NO); Mon, 20 Sep 2004 15:39:56 -0400 (EDT) (envelope-from mistry.7@osu.edu) From: Anish Mistry To: Nate Lawson Date: Mon, 20 Sep 2004 15:56:39 -0400 User-Agent: KMail/1.7 References: <200409201501.48755.mistry.7@osu.edu> <200409201511.02523.mistry.7@osu.edu> <414F30E9.4060300@root.org> In-Reply-To: <414F30E9.4060300@root.org> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart1453344.yMVVdSI0Y0"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200409201556.39518.mistry.7@osu.edu> X-Spam-Status: No, hits=0.8 required=5.0 tests=BIZ_TLD autolearn=no version=2.64 X-Spam-Checker-Version: SpamAssassin 2.64 (2004-01-11) on crumpet.united-ware.com cc: freebsd-acpi@freebsd.org Subject: Re: RELENG_5 panic: mtx_lock() with ACPI X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 20 Sep 2004 19:54:34 -0000 --nextPart1453344.yMVVdSI0Y0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Monday 20 September 2004 03:35 pm, you wrote: > Anish Mistry wrote: > > On Monday 20 September 2004 03:01 pm, Anish Mistry wrote: > >>I'm getting the following panic on boot only with ACPI enabled. > >>On a verbose boot right after: start_init: trying /sbin/init > >>panic: mtx_lock() of spin mutex(null) @ /usr/src/sys/tty/tty.c:2809 > >>Can't seem to get a dump even if dumpdev is set at the loader prompt. > >> > >>Verbose boot without ACPI enabled and ASL attached. > > > > Attachments got stripped. > > http://am-productions.biz/debug/BIGGUY-dmesg.txt.gz > > http://am-productions.biz/debug/bigguy.asl.gz > > Can you send a backtrace ("tr" from ddb)? It doesn't break to the ddb prompt. =2D-=20 Anish Mistry --nextPart1453344.yMVVdSI0Y0 Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (FreeBSD) iD8DBQBBTzX3xqA5ziudZT0RAoP0AKCkjzoNnQlw3QFbdjYbRLxu0OBJbACfWn7t az7+jSqNW1UBveXPXBYN8eU= =JH9u -----END PGP SIGNATURE----- --nextPart1453344.yMVVdSI0Y0-- From owner-freebsd-acpi@FreeBSD.ORG Mon Sep 20 20:00:49 2004 Return-Path: Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3CC8116A4CE for ; Mon, 20 Sep 2004 20:00:49 +0000 (GMT) Received: from www.cryptography.com (li-22.members.linode.com [64.5.53.22]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0272B43D1D for ; Mon, 20 Sep 2004 20:00:49 +0000 (GMT) (envelope-from nate@root.org) Received: from [10.0.0.34] (adsl-67-127-84-57.dsl.snfc21.pacbell.net [67.127.84.57]) by www.cryptography.com (8.12.8/8.12.8) with ESMTP id i8KK0mDl009543; Mon, 20 Sep 2004 13:00:48 -0700 Message-ID: <414F36E2.6050100@root.org> Date: Mon, 20 Sep 2004 13:00:34 -0700 From: Nate Lawson User-Agent: Mozilla Thunderbird 0.7.3 (Windows/20040803) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Anish Mistry References: <200409201501.48755.mistry.7@osu.edu> <200409201511.02523.mistry.7@osu.edu> <414F30E9.4060300@root.org> <200409201556.39518.mistry.7@osu.edu> In-Reply-To: <200409201556.39518.mistry.7@osu.edu> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit cc: freebsd-acpi@freebsd.org Subject: Re: RELENG_5 panic: mtx_lock() with ACPI X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 20 Sep 2004 20:00:49 -0000 Anish Mistry wrote: > On Monday 20 September 2004 03:35 pm, you wrote: > >>Anish Mistry wrote: >> >>>On Monday 20 September 2004 03:01 pm, Anish Mistry wrote: >>> >>>>I'm getting the following panic on boot only with ACPI enabled. >>>>On a verbose boot right after: start_init: trying /sbin/init >>>>panic: mtx_lock() of spin mutex(null) @ /usr/src/sys/tty/tty.c:2809 >>>>Can't seem to get a dump even if dumpdev is set at the loader prompt. >>>> >>>>Verbose boot without ACPI enabled and ASL attached. >>> >>>Attachments got stripped. >>>http://am-productions.biz/debug/BIGGUY-dmesg.txt.gz >>>http://am-productions.biz/debug/bigguy.asl.gz >> >>Can you send a backtrace ("tr" from ddb)? > > It doesn't break to the ddb prompt. Can you enable options DDB? If ddb is enabled, all panics should break to the debugger. -- Nate From owner-freebsd-acpi@FreeBSD.ORG Mon Sep 20 23:04:05 2004 Return-Path: Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A134016A4CE for ; Mon, 20 Sep 2004 23:04:05 +0000 (GMT) Received: from caduceus.jf.intel.com (fmr06.intel.com [134.134.136.7]) by mx1.FreeBSD.org (Postfix) with ESMTP id 637EA43D45 for ; Mon, 20 Sep 2004 23:04:05 +0000 (GMT) (envelope-from robert.moore@intel.com) Received: from petasus.jf.intel.com (petasus.jf.intel.com [10.7.209.6]) major-outer.mc,v 1.15 2004/01/30 18:16:28 root Exp $) with ESMTP id i8KN3prr011816; Mon, 20 Sep 2004 23:03:51 GMT Received: from orsmsxvs041.jf.intel.com (orsmsxvs041.jf.intel.com [192.168.65.54]) major-inner.mc,v 1.11 2004/07/29 22:51:53 root Exp $) with SMTP id i8KN6hUs024419; Mon, 20 Sep 2004 23:06:54 GMT Received: from orsmsx331.amr.corp.intel.com ([192.168.65.56]) M2004092016033922791 ; Mon, 20 Sep 2004 16:03:39 -0700 Received: from orsmsx403.amr.corp.intel.com ([192.168.65.209]) by orsmsx331.amr.corp.intel.com with Microsoft SMTPSVC(6.0.3790.0); Mon, 20 Sep 2004 16:03:39 -0700 X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Date: Mon, 20 Sep 2004 16:03:37 -0700 Message-ID: <37F890616C995246BE76B3E6B2DBE055020AD7F8@orsmsx403.amr.corp.intel.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: trouble overriding DSDT thread-index: AcSe2fRvX8WM8h9hQvyth5/+87+MjwAi/+oQ From: "Moore, Robert" To: "Nate Lawson" , X-OriginalArrivalTime: 20 Sep 2004 23:03:39.0137 (UTC) FILETIME=[10D93F10:01C49F66] X-Scanned-By: MIMEDefang 2.31 (www . roaringpenguin . com / mimedefang) cc: freebsd-acpi@freebsd.org Subject: RE: trouble overriding DSDT X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 20 Sep 2004 23:04:05 -0000 > Oh, sorry. Yes, acpidump(8) will always pull the underlying "real" > table from memory. If acpidump is dumping the "real" tables, why does the DSDT get combined with the SSDT? > -----Original Message----- > From: Nate Lawson [mailto:nate@root.org] > Sent: Sunday, September 19, 2004 11:21 PM > To: sklauder@trimind.de > Cc: Moore, Robert; freebsd-acpi@freebsd.org; Marcel Moolenaar > Subject: Re: trouble overriding DSDT >=20 > Sascha Klauder wrote: > > On Sun, Sep 19, 2004 at 02:07:58PM -0700, Nate Lawson wrote: > > > >>SSDTs as well. When you override the DSDT, you are loading a combined > >>DSDT+SSDT table but the original SSDT is still in memory. Thus you get > >>the duplicated namespace values. An easy way to test this is to comment > >>out everything in your ASL from the Scope(...CPU0) to the end, > > > > > > Yes, that did the trick! > > > > > >>recompile, load it, then if it boots ok, do another acpidump and diff > >>the two. If I'm right, you'll find commenting out some part gets you > >>the same ASL after booting with the custom one. > > > > > > Right, the ASLs are effectively the same, with the exception > > that the very changes I did in the first place now seem to be > > "backed out". Is this the supposed behaviour when the DSDT > > is overridden (i.e. acpidump(8) always dumps the DSDT pro- > > vided by the BIOS (or something to that effect))? >=20 > Oh, sorry. Yes, acpidump(8) will always pull the underlying "real" > table from memory. >=20 > -Nate From owner-freebsd-acpi@FreeBSD.ORG Tue Sep 21 01:21:18 2004 Return-Path: Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7A8BE16A4CE for ; Tue, 21 Sep 2004 01:21:18 +0000 (GMT) Received: from www.cryptography.com (li-22.members.linode.com [64.5.53.22]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2664743D2D for ; Tue, 21 Sep 2004 01:21:18 +0000 (GMT) (envelope-from nate@root.org) Received: from [10.0.0.34] (adsl-67-127-84-57.dsl.snfc21.pacbell.net [67.127.84.57]) by www.cryptography.com (8.12.8/8.12.8) with ESMTP id i8L1LDDl016310; Mon, 20 Sep 2004 18:21:14 -0700 Message-ID: <414F81FB.2080309@root.org> Date: Mon, 20 Sep 2004 18:20:59 -0700 From: Nate Lawson User-Agent: Mozilla Thunderbird 0.7.3 (Windows/20040803) X-Accept-Language: en-us, en MIME-Version: 1.0 To: "Moore, Robert" References: <37F890616C995246BE76B3E6B2DBE055020AD7F8@orsmsx403.amr.corp.intel.com> In-Reply-To: <37F890616C995246BE76B3E6B2DBE055020AD7F8@orsmsx403.amr.corp.intel.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit cc: sklauder@trimind.de cc: freebsd-acpi@freebsd.org Subject: Re: trouble overriding DSDT X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 21 Sep 2004 01:21:18 -0000 Moore, Robert wrote: >>Oh, sorry. Yes, acpidump(8) will always pull the underlying "real" >>table from memory. > > > If acpidump is dumping the "real" tables, why does the DSDT get combined > with the SSDT? Our acpidump dumps all tables that contain AML (DSDT, SSDT) at once. The user load of "which table do I dump?" would otherwise be too great when trying to get debugging info from them. It's hard enough as it is to get both -t and -d output (fixed tables + AML). I'm thinking about making -t automatic when -d is specified. -- Nate From owner-freebsd-acpi@FreeBSD.ORG Tue Sep 21 11:11:21 2004 Return-Path: Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 76AC916A4CE for ; Tue, 21 Sep 2004 11:11:21 +0000 (GMT) Received: from nulis.lt (adsl-213-190-44-175.takas.lt [213.190.44.175]) by mx1.FreeBSD.org (Postfix) with ESMTP id CD2B343D54 for ; Tue, 21 Sep 2004 11:11:20 +0000 (GMT) (envelope-from bob@nulis.lt) Received: from highland.tamsa ([10.0.1.1]) by nulis.lt with esmtp (Exim 4.34) id 1C9iX8-0004un-Gi for freebsd-acpi@freebsd.org; Tue, 21 Sep 2004 14:10:06 +0300 Message-ID: <41500C59.3080407@nulis.lt> Date: Tue, 21 Sep 2004 14:11:21 +0300 From: Saulius Menkevicius User-Agent: Mozilla Thunderbird 0.7.3 (X11/20040907) X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-acpi@freebsd.org Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Subject: cpu fan spped does not drop down to normal when cpu temperature goes back to normal X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 21 Sep 2004 11:11:21 -0000 Hello, Is there a way to find why the ACPI code does not lower CPU fan speed when temperature drops back to low (as set in BIOS)? It does turn the speed to 100% when temperature gets high. Can it be a buggy BIOS ACPI. And it works fine in Windows though. The motherboard is Abit IS7, desktop with a P4 2.4C. Running 5.3-BETA5. Don't know where to look at myself. I can post the output of acpidump -d if needed, it's a fairly large dump. Thanks, -- Saulius Menkevicius From owner-freebsd-acpi@FreeBSD.ORG Tue Sep 21 19:03:22 2004 Return-Path: Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CEC3E16A4CE for ; Tue, 21 Sep 2004 19:03:22 +0000 (GMT) Received: from crumpet.united-ware.com (ddsl-66-42-172-210.fuse.net [66.42.172.210]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0CD8D43D2F for ; Tue, 21 Sep 2004 19:03:22 +0000 (GMT) (envelope-from mistry.7@osu.edu) Received: from [192.168.0.6] (adsl-68-250-185-35.dsl.wotnoh.ameritech.net [68.250.185.35]) (authenticated bits=0)i8LImbHR055985 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NO); Tue, 21 Sep 2004 14:48:39 -0400 (EDT) (envelope-from mistry.7@osu.edu) From: Anish Mistry To: Nate Lawson Date: Tue, 21 Sep 2004 15:05:18 -0400 User-Agent: KMail/1.7 References: <200409201501.48755.mistry.7@osu.edu> <200409201556.39518.mistry.7@osu.edu> <414F36E2.6050100@root.org> In-Reply-To: <414F36E2.6050100@root.org> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart1233284.Vg69CPLG8b"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200409211505.27479.mistry.7@osu.edu> X-Spam-Status: No, hits=0.8 required=5.0 tests=BIZ_TLD autolearn=no version=2.64 X-Spam-Checker-Version: SpamAssassin 2.64 (2004-01-11) on crumpet.united-ware.com cc: freebsd-acpi@freebsd.org Subject: Re: RELENG_5 panic: mtx_lock() with ACPI X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 21 Sep 2004 19:03:23 -0000 --nextPart1233284.Vg69CPLG8b Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Monday 20 September 2004 04:00 pm, you wrote: > Anish Mistry wrote: > > On Monday 20 September 2004 03:35 pm, you wrote: > >>Anish Mistry wrote: > >>>On Monday 20 September 2004 03:01 pm, Anish Mistry wrote: > >>>>I'm getting the following panic on boot only with ACPI enabled. > >>>>On a verbose boot right after: start_init: trying /sbin/init > >>>>panic: mtx_lock() of spin mutex(null) @ /usr/src/sys/tty/tty.c:2809 > >>>>Can't seem to get a dump even if dumpdev is set at the loader prompt. > >>>> > >>>>Verbose boot without ACPI enabled and ASL attached. > >>> > >>>Attachments got stripped. > >>>http://am-productions.biz/debug/BIGGUY-dmesg.txt.gz > >>>http://am-productions.biz/debug/bigguy.asl.gz > >> > >>Can you send a backtrace ("tr" from ddb)? > > > > It doesn't break to the ddb prompt. > > Can you enable options DDB? If ddb is enabled, all panics should break > to the debugger. Ok, I removed WITNESS and INVARIANTS from my kernel config, and now it's=20 dropping to a db> prompt. Hand transcribed: kernel trap 12 with interrupts disableed =46atal trap 12: page fault while in kernel mode fault virtual address =3D 0x6c fault code =3D supervisor read, page not present=20 instruction pointer =3D 0x8 : 0xc04dfb85 stack pointer =3D 0x10 : 0xd0c3bad4 frame pointer =3D 0x10 : 0xd0c3bad8 code segment =3D base 0x0, limit 0xfffff, type 0x1b =3D DPL 0, pres 1, def32 1,gran 1 processor eflags =3D resume, IOPL =3D 0 current process =3D 63 (sysctl) [thread 100063] Stopped at turnstile_setowner+0x9: movl0x6c(%edx),%eax turnstile_setowner(d0c3bb6c,d0c3bb18,c069a700,c069b460,c13e58c0 at=20 turnstile_setowner+0x9 turnstile_wait(0,c069b460,0) at turnstile_wait+0x47a _mtx_lock_sleep(c069b460, c13f04b0,0,0,0) at _mtx_lock_sleep+0x7f sysctl_kern_ttys(c0674660,0,0,d0c3bc14,c0674660) at sysctl_kern_ttys+0x253 sysctl_root(2,d0c3bc14,c13f04b0,0) at sysctl_root+0x80 userland_sysctl(c13f04b0,d0c3bc80,2,0,bfbfe4ac,0,0,0,d0c3bc7c) at=20 userland_sysctl __sysctl(c13f0410) at __sysctl+0x77 syscall(2f,2f,2f,2,bfbfe4ac) at syscall+0x1c7 Xint0x80_syscall() at Xint0x80_syscall+0x1f =2D- syscall (202, FreeBSD ELF32, __sysctl), eip=3D0x280cb7c3, esp=3D0xbfbf= e41c,=20 ebp+0xbfbfe458 BTW, is there a way to set the dump device at the loader that works. =2D-=20 Anish Mistry --nextPart1233284.Vg69CPLG8b Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (FreeBSD) iD8DBQBBUHt3xqA5ziudZT0RAhggAKCJZQhDQb2p3W1+3teeX2PYeWpAJACfXwGQ DY01Q1qdMDrr71caG60G56o= =XsFa -----END PGP SIGNATURE----- --nextPart1233284.Vg69CPLG8b-- From owner-freebsd-acpi@FreeBSD.ORG Tue Sep 21 19:43:56 2004 Return-Path: Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7E27316A4CE for ; Tue, 21 Sep 2004 19:43:56 +0000 (GMT) Received: from ack.Berkeley.EDU (ack.berkeley.edu [128.32.206.66]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4CF8743D39 for ; Tue, 21 Sep 2004 19:43:56 +0000 (GMT) (envelope-from mhunter@ack.Berkeley.EDU) Received: (from mhunter@localhost) by ack.Berkeley.EDU (8.11.3/8.11.3) id i8LJhtC17784 for freebsd-acpi@freebsd.org; Tue, 21 Sep 2004 12:43:55 -0700 (PDT) Date: Tue, 21 Sep 2004 12:43:55 -0700 From: Mike Hunter To: freebsd-acpi@freebsd.org Message-ID: <20040921194355.GA17564@ack.Berkeley.EDU> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.6i Subject: 5.3-BETA5 "ACPI autoload failed - no such file or directory" X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 21 Sep 2004 19:43:56 -0000 Hi, Upon upgrading to 5.3-BETA5 I got the message: ACPI autoload failed - no such file or directory I did some google searching and came up with this: http://lists.freebsd.org/pipermail/freebsd-current/2004-August/033757.html Which told me to change /boot/defaults/loader.conf to change module_path="/boot/modules" to module_path="/boot/kernel;/boot/modules" Which solved the problem. I'm just wondering what I missed in upgrading that made this a problem in the first place...? Also, my dmesg now has this: ACPI link \\_SB_.PCI0.LNKB has invalid initial irq 11, ignoring Is that just a quirk of my custom DSDT? Last but not least (here's a silly question)...what's the proper mailing list to send general 5.3-BETA questions to? current is at 6, and stable is at 4.10...:| Thanks, Mike From owner-freebsd-acpi@FreeBSD.ORG Tue Sep 21 20:29:21 2004 Return-Path: Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9D90516A4CE for ; Tue, 21 Sep 2004 20:29:21 +0000 (GMT) Received: from www.cryptography.com (li-22.members.linode.com [64.5.53.22]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5CC0743D31 for ; Tue, 21 Sep 2004 20:29:21 +0000 (GMT) (envelope-from nate@root.org) Received: from [10.0.0.34] (adsl-67-127-84-57.dsl.snfc21.pacbell.net [67.127.84.57]) by www.cryptography.com (8.12.8/8.12.8) with ESMTP id i8LKTGDl008302; Tue, 21 Sep 2004 13:29:16 -0700 Message-ID: <41508F04.5040504@root.org> Date: Tue, 21 Sep 2004 13:28:52 -0700 From: Nate Lawson User-Agent: Mozilla Thunderbird 0.7.3 (Windows/20040803) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Mike Hunter References: <20040921194355.GA17564@ack.Berkeley.EDU> In-Reply-To: <20040921194355.GA17564@ack.Berkeley.EDU> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit cc: freebsd-acpi@freebsd.org Subject: Re: 5.3-BETA5 "ACPI autoload failed - no such file or directory" X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 21 Sep 2004 20:29:21 -0000 Mike Hunter wrote: > Hi, > > Upon upgrading to 5.3-BETA5 I got the message: > ACPI autoload failed - no such file or directory > > I did some google searching and came up with this: > > http://lists.freebsd.org/pipermail/freebsd-current/2004-August/033757.html > > Which told me to change /boot/defaults/loader.conf to change > > module_path="/boot/modules" > > to > > module_path="/boot/kernel;/boot/modules" > > Which solved the problem. I'm just wondering what I missed in upgrading > that made this a problem in the first place...? Read /usr/src/UPDATING. You need to update loader.rc > Also, my dmesg now has this: > > ACPI link \\_SB_.PCI0.LNKB has invalid initial irq 11, ignoring > > Is that just a quirk of my custom DSDT? It's probably a quirk in an original part of your DSDT. _PRS doesn't contain 11 but the device had that value initially. It should get a new irq routed. Report the full dmesg if the devices that use LNKB have timeouts or other problems. > Last but not least (here's a silly question)...what's the proper mailing > list to send general 5.3-BETA questions to? current is at 6, and stable > is at 4.10...:| -current -- Nate From owner-freebsd-acpi@FreeBSD.ORG Tue Sep 21 20:34:05 2004 Return-Path: Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 41E6116A4CE for ; Tue, 21 Sep 2004 20:34:05 +0000 (GMT) Received: from mail4.speakeasy.net (mail4.speakeasy.net [216.254.0.204]) by mx1.FreeBSD.org (Postfix) with ESMTP id 12EFA43D39 for ; Tue, 21 Sep 2004 20:34:05 +0000 (GMT) (envelope-from jhb@FreeBSD.org) Received: (qmail 19276 invoked from network); 21 Sep 2004 20:25:39 -0000 Received: from dsl027-160-063.atl1.dsl.speakeasy.net (HELO server.baldwin.cx) ([216.27.160.63]) (envelope-sender ) encrypted SMTP for ; 21 Sep 2004 20:25:38 -0000 Received: from [10.50.40.210] (gw1.twc.weather.com [216.133.140.1]) (authenticated bits=0) by server.baldwin.cx (8.12.11/8.12.11) with ESMTP id i8LKPWap034041; Tue, 21 Sep 2004 16:25:35 -0400 (EDT) (envelope-from jhb@FreeBSD.org) From: John Baldwin To: freebsd-acpi@FreeBSD.org Date: Tue, 21 Sep 2004 15:26:47 -0400 User-Agent: KMail/1.6.2 References: <200409201501.48755.mistry.7@osu.edu> <414F36E2.6050100@root.org> <200409211505.27479.mistry.7@osu.edu> In-Reply-To: <200409211505.27479.mistry.7@osu.edu> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200409211526.47015.jhb@FreeBSD.org> X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on server.baldwin.cx Subject: Re: RELENG_5 panic: mtx_lock() with ACPI X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 21 Sep 2004 20:34:05 -0000 On Tuesday 21 September 2004 03:05 pm, Anish Mistry wrote: > On Monday 20 September 2004 04:00 pm, you wrote: > > Anish Mistry wrote: > > > On Monday 20 September 2004 03:35 pm, you wrote: > > >>Anish Mistry wrote: > > >>>On Monday 20 September 2004 03:01 pm, Anish Mistry wrote: > > >>>>I'm getting the following panic on boot only with ACPI enabled. > > >>>>On a verbose boot right after: start_init: trying /sbin/init > > >>>>panic: mtx_lock() of spin mutex(null) @ /usr/src/sys/tty/tty.c:2809 > > >>>>Can't seem to get a dump even if dumpdev is set at the loader prompt. > > >>>> > > >>>>Verbose boot without ACPI enabled and ASL attached. > > >>> > > >>>Attachments got stripped. > > >>>http://am-productions.biz/debug/BIGGUY-dmesg.txt.gz > > >>>http://am-productions.biz/debug/bigguy.asl.gz > > >> > > >>Can you send a backtrace ("tr" from ddb)? > > > > > > It doesn't break to the ddb prompt. > > > > Can you enable options DDB? If ddb is enabled, all panics should break > > to the debugger. > > Ok, I removed WITNESS and INVARIANTS from my kernel config, and now it's > dropping to a db> prompt. You want to keep INVARIANTS as it find problems sooner and in easier to debug locations. Can you turn INVARIANTS back on at least and then get a trace? > BTW, is there a way to set the dump device at the loader that works. Not that I'm aware of. -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve" = http://www.FreeBSD.org From owner-freebsd-acpi@FreeBSD.ORG Tue Sep 21 22:12:48 2004 Return-Path: Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 374E216A55D; Tue, 21 Sep 2004 22:12:48 +0000 (GMT) Received: from crumpet.united-ware.com (ddsl-66-42-172-210.fuse.net [66.42.172.210]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0E58343D45; Tue, 21 Sep 2004 22:12:47 +0000 (GMT) (envelope-from mistry.7@osu.edu) Received: from [192.168.0.6] (adsl-68-250-185-35.dsl.wotnoh.ameritech.net [68.250.185.35]) (authenticated bits=0)i8LLw2HR056241 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NO); Tue, 21 Sep 2004 17:58:03 -0400 (EDT) (envelope-from mistry.7@osu.edu) From: Anish Mistry To: John Baldwin Date: Tue, 21 Sep 2004 18:14:45 -0400 User-Agent: KMail/1.7 References: <200409201501.48755.mistry.7@osu.edu> <200409211505.27479.mistry.7@osu.edu> <200409211526.47015.jhb@FreeBSD.org> In-Reply-To: <200409211526.47015.jhb@FreeBSD.org> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart1791194.HIF3ikVMvN"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200409211814.52805.mistry.7@osu.edu> X-Spam-Status: No, hits=0.8 required=5.0 tests=BIZ_TLD autolearn=no version=2.64 X-Spam-Checker-Version: SpamAssassin 2.64 (2004-01-11) on crumpet.united-ware.com cc: freebsd-acpi@freebsd.org Subject: Re: RELENG_5 panic: mtx_lock() with ACPI X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 21 Sep 2004 22:12:49 -0000 --nextPart1791194.HIF3ikVMvN Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Tuesday 21 September 2004 03:26 pm, you wrote: > On Tuesday 21 September 2004 03:05 pm, Anish Mistry wrote: > > On Monday 20 September 2004 04:00 pm, you wrote: > > > Anish Mistry wrote: > > > > On Monday 20 September 2004 03:35 pm, you wrote: > > > >>Anish Mistry wrote: > > > >>>On Monday 20 September 2004 03:01 pm, Anish Mistry wrote: > > > >>>>I'm getting the following panic on boot only with ACPI enabled. > > > >>>>On a verbose boot right after: start_init: trying /sbin/init > > > >>>>panic: mtx_lock() of spin mutex(null) @ /usr/src/sys/tty/tty.c:28= 09 > > > >>>>Can't seem to get a dump even if dumpdev is set at the loader > > > >>>> prompt. > > > >>>> > > > >>>>Verbose boot without ACPI enabled and ASL attached. > > > >>> > > > >>>Attachments got stripped. > > > >>>http://am-productions.biz/debug/BIGGUY-dmesg.txt.gz > > > >>>http://am-productions.biz/debug/bigguy.asl.gz > > > >> > > > >>Can you send a backtrace ("tr" from ddb)? > > > > > > > > It doesn't break to the ddb prompt. > > > > > > Can you enable options DDB? If ddb is enabled, all panics should bre= ak > > > to the debugger. > > > > Ok, I removed WITNESS and INVARIANTS from my kernel config, and now it's > > dropping to a db> prompt. > > You want to keep INVARIANTS as it find problems sooner and in easier to > debug locations. Can you turn INVARIANTS back on at least and then get a > trace? > > > BTW, is there a way to set the dump device at the loader that works. > > Not that I'm aware of. With INVARIANTS enabled: panic: mtx_lock() of spin mutex(null) @ /usr/src/sys/tty/tty.c:2809 KDB: enter: panic [thread 100063] Stopped at kdb_enter+0x2c: leave kdb_enter(c06288da,100,af9,c062c3f3,0) at kdb_enter+0x2c _mtx_lock_flags(c0680f80,0,c062c3f4,af9,d0c3bb60) at _mtx_lock_flags+0x82 sysctl_kern_ttys(c065a160,0,0,d0c3bc04,c065a160) at sysctl_kern_ttys+0x22 sysctl_root(2,d0c3bc04,c13f04b0,1,0) at sysctl_root+0x83 userland_sysctl(c13f04b0,d0c3bc80,2,0,bfbfe4ac,0,0,0,d0c3bc7c,c067bdc0,0,c0= 62929c,4e7)=20 at userland_sysctl+0xd8 __sysctl(c13f04b0,d0c3db14,6,0,292) at __sysctl+0x78 syscall(2f,2f,2f,2,bfbfe4ac) at syscall+0x127 Xint0x80_syscall() at Xint0x80_syscall+0x1f =2D- syscall (202, FreeBSD ELF32, __sysctl), eip=3D0x280cb7c3, esp=3D0xbfbf= e41c,=20 ebp+0xbfbfe458 =2D-=20 Anish Mistry --nextPart1791194.HIF3ikVMvN Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (FreeBSD) iD8DBQBBUKfcxqA5ziudZT0RAiffAKCmZTNKk/t6uDe9z3x6kFJvAb+ioACg0f6P zMw+ti2m2o7J/l/0ZmwCWhk= =5IgA -----END PGP SIGNATURE----- --nextPart1791194.HIF3ikVMvN-- From owner-freebsd-acpi@FreeBSD.ORG Wed Sep 22 16:52:07 2004 Return-Path: Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4648C16A4CE for ; Wed, 22 Sep 2004 16:52:07 +0000 (GMT) Received: from citadel.icyb.net.ua (citadel.icyb.net.ua [212.40.38.140]) by mx1.FreeBSD.org (Postfix) with ESMTP id D976343D1F for ; Wed, 22 Sep 2004 16:52:05 +0000 (GMT) (envelope-from avg@icyb.net.ua) Received: from [212.40.38.87] (oddity.topspin.kiev.ua [212.40.38.87]) by citadel.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id TAA01711; Wed, 22 Sep 2004 19:51:30 +0300 (EEST) (envelope-from avg@icyb.net.ua) Message-ID: <4151AD92.8050905@icyb.net.ua> Date: Wed, 22 Sep 2004 19:51:30 +0300 From: Andriy Gapon User-Agent: Mozilla Thunderbird 0.7.3 (X11/20040831) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Saulius Menkevicius References: <1095693793.00135239.1095680401@10.7.7.3> In-Reply-To: <1095693793.00135239.1095680401@10.7.7.3> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit cc: freebsd-acpi@freebsd.org Subject: Re: acpi fan does not lower speed when CPU temp is back to low X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 22 Sep 2004 16:52:07 -0000 on 20.09.2004 14:38 Saulius Menkevicius said the following: > Is there a way to find why the ACPI code does not lower > CPU fan speed when temperature drops back to low (as set in BIOS)? > It does turn the speed to 100% when temperature gets high. > > Can it be a buggy BIOS ACPI? Though it's working fine in Windows. > > The motherboard is Abit IS7, desktop with a P4 2.4C. > Running 5.3-BETA4. turning fans on/off is done by OS (kernel), but it is done through calling ACPI methods, so the problem can be in either place. Try to take dump of your ACPI DSDT (using acpidump) and look for FAN device section in there. You can post it to the list or send to me in private. If you are ineterested, you can also google for ACPI specs and download them, they are not very hard to comperehend (but bulky). -- Andriy Gapon From owner-freebsd-acpi@FreeBSD.ORG Wed Sep 22 19:17:29 2004 Return-Path: Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 863AE16A4E9 for ; Wed, 22 Sep 2004 19:17:29 +0000 (GMT) Received: from mail3.speakeasy.net (mail3.speakeasy.net [216.254.0.203]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4E96943D45 for ; Wed, 22 Sep 2004 19:17:29 +0000 (GMT) (envelope-from jhb@FreeBSD.org) Received: (qmail 6393 invoked from network); 22 Sep 2004 19:17:29 -0000 Received: from dsl027-160-063.atl1.dsl.speakeasy.net (HELO server.baldwin.cx) ([216.27.160.63]) (envelope-sender ) encrypted SMTP for ; 22 Sep 2004 19:17:28 -0000 Received: from [10.50.40.210] (gw1.twc.weather.com [216.133.140.1]) (authenticated bits=0) by server.baldwin.cx (8.12.11/8.12.11) with ESMTP id i8MJHHiv002614; Wed, 22 Sep 2004 15:17:25 -0400 (EDT) (envelope-from jhb@FreeBSD.org) From: John Baldwin To: Anish Mistry Date: Wed, 22 Sep 2004 15:18:00 -0400 User-Agent: KMail/1.6.2 References: <200409201501.48755.mistry.7@osu.edu> <200409211526.47015.jhb@FreeBSD.org> <200409211814.52805.mistry.7@osu.edu> In-Reply-To: <200409211814.52805.mistry.7@osu.edu> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200409221518.00328.jhb@FreeBSD.org> X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on server.baldwin.cx cc: freebsd-acpi@FreeBSD.org cc: Poul-Henning Kamp Subject: Re: RELENG_5 panic: mtx_lock() with ACPI X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 22 Sep 2004 19:17:29 -0000 On Tuesday 21 September 2004 06:14 pm, Anish Mistry wrote: > On Tuesday 21 September 2004 03:26 pm, you wrote: > > On Tuesday 21 September 2004 03:05 pm, Anish Mistry wrote: > > > On Monday 20 September 2004 04:00 pm, you wrote: > > > > Anish Mistry wrote: > > > > > On Monday 20 September 2004 03:35 pm, you wrote: > > > > >>Anish Mistry wrote: > > > > >>>On Monday 20 September 2004 03:01 pm, Anish Mistry wrote: > > > > >>>>I'm getting the following panic on boot only with ACPI enabled. > > > > >>>>On a verbose boot right after: start_init: trying /sbin/init > > > > >>>>panic: mtx_lock() of spin mutex(null) @ > > > > >>>> /usr/src/sys/tty/tty.c:2809 Can't seem to get a dump even if > > > > >>>> dumpdev is set at the loader prompt. > > > > >>>> > > > > >>>>Verbose boot without ACPI enabled and ASL attached. > > > > >>> > > > > >>>Attachments got stripped. > > > > >>>http://am-productions.biz/debug/BIGGUY-dmesg.txt.gz > > > > >>>http://am-productions.biz/debug/bigguy.asl.gz > > > > >> > > > > >>Can you send a backtrace ("tr" from ddb)? > > > > > > > > > > It doesn't break to the ddb prompt. > > > > > > > > Can you enable options DDB? If ddb is enabled, all panics should > > > > break to the debugger. > > > > > > Ok, I removed WITNESS and INVARIANTS from my kernel config, and now > > > it's dropping to a db> prompt. > > > > You want to keep INVARIANTS as it find problems sooner and in easier to > > debug locations. Can you turn INVARIANTS back on at least and then get a > > trace? > > > > > BTW, is there a way to set the dump device at the loader that works. > > > > Not that I'm aware of. > > With INVARIANTS enabled: > panic: mtx_lock() of spin mutex(null) @ /usr/src/sys/tty/tty.c:2809 > KDB: enter: panic > [thread 100063] > Stopped at kdb_enter+0x2c: leave > kdb_enter(c06288da,100,af9,c062c3f3,0) at kdb_enter+0x2c > _mtx_lock_flags(c0680f80,0,c062c3f4,af9,d0c3bb60) at _mtx_lock_flags+0x82 > sysctl_kern_ttys(c065a160,0,0,d0c3bc04,c065a160) at sysctl_kern_ttys+0x22 > sysctl_root(2,d0c3bc04,c13f04b0,1,0) at sysctl_root+0x83 > userland_sysctl(c13f04b0,d0c3bc80,2,0,bfbfe4ac,0,0,0,d0c3bc7c,c067bdc0,0,c0 >62929c,4e7) at userland_sysctl+0xd8 > __sysctl(c13f04b0,d0c3db14,6,0,292) at __sysctl+0x78 > syscall(2f,2f,2f,2,bfbfe4ac) at syscall+0x127 > Xint0x80_syscall() at Xint0x80_syscall+0x1f > -- syscall (202, FreeBSD ELF32, __sysctl), eip=0x280cb7c3, esp=0xbfbfe41c, > ebp+0xbfbfe458 Looks like the ttys_list_mutex is busted. Hmm: struct tty * ttymalloc(struct tty *tp) { static int once; if (!once) { mtx_init(&tty_list_mutex, "ttylist", NULL, MTX_DEF); once++; } This code is not MP safe as multiple processors could attempt to call mtx_init() twice. The mutex should probably be initialized via MTX_SYSINIT instead. An alternative fix might be to change the code to work like this: if (once != 2) { if (atomic_cmpset_int(&once, 0, 1)) { mtx_init(...); atomic_store_rel_int(&once, 2); } else while (once != 2) cpu_spinwait(); } To ensure that 1) only one CPU can do the mtx_init() at a time and 2) that if any other CPU enters the function while another CPU is doing the mtx_init() it will wait until the mutex is initialized before proceeding. -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve" = http://www.FreeBSD.org From owner-freebsd-acpi@FreeBSD.ORG Fri Sep 24 01:34:58 2004 Return-Path: Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2E38B16A4CE; Fri, 24 Sep 2004 01:34:58 +0000 (GMT) Received: from crumpet.united-ware.com (ddsl-66-42-172-210.fuse.net [66.42.172.210]) by mx1.FreeBSD.org (Postfix) with ESMTP id 357CF43D48; Fri, 24 Sep 2004 01:34:57 +0000 (GMT) (envelope-from mistry.7@osu.edu) Received: from [192.168.0.6] (adsl-68-250-185-35.dsl.wotnoh.ameritech.net [68.250.185.35]) (authenticated bits=0)i8O1K1HR010505 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NO); Thu, 23 Sep 2004 21:20:03 -0400 (EDT) (envelope-from mistry.7@osu.edu) From: Anish Mistry To: John Baldwin Date: Thu, 23 Sep 2004 21:36:46 -0400 User-Agent: KMail/1.7 References: <200409201501.48755.mistry.7@osu.edu> <200409211814.52805.mistry.7@osu.edu> <200409221518.00328.jhb@FreeBSD.org> In-Reply-To: <200409221518.00328.jhb@FreeBSD.org> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart1156537.TaMmmeu2YT"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200409232136.54285.mistry.7@osu.edu> X-Spam-Status: No, hits=0.8 required=5.0 tests=BIZ_TLD autolearn=no version=2.64 X-Spam-Checker-Version: SpamAssassin 2.64 (2004-01-11) on crumpet.united-ware.com cc: freebsd-acpi@freebsd.org cc: Poul-Henning Kamp Subject: Re: RELENG_5 panic: mtx_lock() with ACPI X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 24 Sep 2004 01:34:58 -0000 --nextPart1156537.TaMmmeu2YT Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Wednesday 22 September 2004 03:18 pm, John Baldwin wrote: > On Tuesday 21 September 2004 06:14 pm, Anish Mistry wrote: > > On Tuesday 21 September 2004 03:26 pm, you wrote: > > > On Tuesday 21 September 2004 03:05 pm, Anish Mistry wrote: > > > > On Monday 20 September 2004 04:00 pm, you wrote: > > > > > Anish Mistry wrote: > > > > > > On Monday 20 September 2004 03:35 pm, you wrote: > > > > > >>Anish Mistry wrote: > > > > > >>>On Monday 20 September 2004 03:01 pm, Anish Mistry wrote: > > > > > >>>>I'm getting the following panic on boot only with ACPI enable= d. > > > > > >>>>On a verbose boot right after: start_init: trying /sbin/init > > > > > >>>>panic: mtx_lock() of spin mutex(null) @ > > > > > >>>> /usr/src/sys/tty/tty.c:2809 Can't seem to get a dump even if > > > > > >>>> dumpdev is set at the loader prompt. > > > > > >>>> > > > > > >>>>Verbose boot without ACPI enabled and ASL attached. > > > > > >>> > > > > > >>>Attachments got stripped. > > > > > >>>http://am-productions.biz/debug/BIGGUY-dmesg.txt.gz > > > > > >>>http://am-productions.biz/debug/bigguy.asl.gz > > > > > >> > > > > > >>Can you send a backtrace ("tr" from ddb)? > > > > > > > > > > > > It doesn't break to the ddb prompt. > > > > > > > > > > Can you enable options DDB? If ddb is enabled, all panics should > > > > > break to the debugger. > > > > > > > > Ok, I removed WITNESS and INVARIANTS from my kernel config, and now > > > > it's dropping to a db> prompt. > > > > > > You want to keep INVARIANTS as it find problems sooner and in easier = to > > > debug locations. Can you turn INVARIANTS back on at least and then g= et > > > a trace? > > > > > > > BTW, is there a way to set the dump device at the loader that works. > > > > > > Not that I'm aware of. > > > > With INVARIANTS enabled: > > panic: mtx_lock() of spin mutex(null) @ /usr/src/sys/tty/tty.c:2809 > > KDB: enter: panic > > [thread 100063] > > Stopped at kdb_enter+0x2c: leave > > kdb_enter(c06288da,100,af9,c062c3f3,0) at kdb_enter+0x2c > > _mtx_lock_flags(c0680f80,0,c062c3f4,af9,d0c3bb60) at _mtx_lock_flags+0x= 82 > > sysctl_kern_ttys(c065a160,0,0,d0c3bc04,c065a160) at sysctl_kern_ttys+0x= 22 > > sysctl_root(2,d0c3bc04,c13f04b0,1,0) at sysctl_root+0x83 > > userland_sysctl(c13f04b0,d0c3bc80,2,0,bfbfe4ac,0,0,0,d0c3bc7c,c067bdc0,= 0, > >c0 62929c,4e7) at userland_sysctl+0xd8 > > __sysctl(c13f04b0,d0c3db14,6,0,292) at __sysctl+0x78 > > syscall(2f,2f,2f,2,bfbfe4ac) at syscall+0x127 > > Xint0x80_syscall() at Xint0x80_syscall+0x1f > > -- syscall (202, FreeBSD ELF32, __sysctl), eip=3D0x280cb7c3, > > esp=3D0xbfbfe41c, ebp+0xbfbfe458 > > Looks like the ttys_list_mutex is busted. Hmm: > > struct tty * > ttymalloc(struct tty *tp) > { > static int once; > > if (!once) { > mtx_init(&tty_list_mutex, "ttylist", NULL, MTX_DEF); > once++; > } > > This code is not MP safe as multiple processors could attempt to call > mtx_init() twice. The mutex should probably be initialized via MTX_SYSIN= IT > instead. An alternative fix might be to change the code to work like thi= s: > > if (once !=3D 2) { > if (atomic_cmpset_int(&once, 0, 1)) { > mtx_init(...); > atomic_store_rel_int(&once, 2); > } else while (once !=3D 2) > cpu_spinwait(); > } > > To ensure that 1) only one CPU can do the mtx_init() at a time and 2) that > if any other CPU enters the function while another CPU is doing the > mtx_init() it will wait until the mutex is initialized before proceeding. Any futher progress on this that I could test out? =2D-=20 Anish Mistry --nextPart1156537.TaMmmeu2YT Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (FreeBSD) iD8DBQBBU3o2xqA5ziudZT0RAtxHAJ42+nH7o6zSTj1L9ceYUEWkD8uFqACfXy3E NKbVwCHA2KlE5VxOLCAINYw= =O/r0 -----END PGP SIGNATURE----- --nextPart1156537.TaMmmeu2YT-- From owner-freebsd-acpi@FreeBSD.ORG Fri Sep 24 16:04:25 2004 Return-Path: Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2025516A558 for ; Fri, 24 Sep 2004 16:04:25 +0000 (GMT) Received: from postal2.es.net (postal2.es.net [198.128.3.206]) by mx1.FreeBSD.org (Postfix) with ESMTP id D0B0E43D39 for ; Fri, 24 Sep 2004 16:04:24 +0000 (GMT) (envelope-from oberman@es.net) Received: from ptavv.es.net ([198.128.4.29]) by postal2.es.net (Postal Node 2) with ESMTP (SSL) id IBA74465 for ; Fri, 24 Sep 2004 09:04:23 -0700 Received: from ptavv (localhost [127.0.0.1]) by ptavv.es.net (Tachyon Server) with ESMTP id 9777D5D04 for ; Fri, 24 Sep 2004 09:04:23 -0700 (PDT) To: acpi@freebsd.org Date: Fri, 24 Sep 2004 09:04:23 -0700 From: "Kevin Oberman" Message-Id: <20040924160423.9777D5D04@ptavv.es.net> Subject: ASUS P5A broken by ACPI black-list X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 24 Sep 2004 16:04:27 -0000 A couple of weeks ago I tried to upgrade a system to RELENG_5 from CURRENT of June 13. The unit failed in 2 areas: No network and continual DMA timeouts from one disk. After building some old kernels, it became apparent that the network broke long before the disk problem showed up and was the result of the ACPI black-list implemented back on June 30. Unfortunately, this board seems to require ACPI to run. Without it I get continuous xl0: watchdog timeout messages from the system. I have now re-enabled ACPI in the hints file and the network is fine. (I'm still looking for the source of the disk problem.) Why it fails without ACPI is another issue. This is a rather old board and has run just fine for years on V3 and V4 kernels. If I understand the acpidump, this BIOS should not be matching the quirk. But it's quite possible that I am not correctly interpreting what the 'oem_rev' is. Is this BIOS REALLY black-listed? If so, why? It seems that it should not be. The quirk entry is: # ASUS P5A 03/12/99 name: ASUS_P5A oem: FADT "ASUS " "P5A " oem_rev: FADT <= 0x58582e31 quirks: ACPI_Q_BROKEN My FADT is: FADT: FACS=0x5fff000, DSDT=0x5ffc100 INT_MODEL=PIC Preferred_PM_Profile=Unspecified (0) SCI_INT=9 SMI_CMD=0xb1, ACPI_ENABLE=0xa1, ACPI_DISABLE=0xa0, S4BIOS_REQ=0x0 PSTATE_CNT=0x0 PM1a_EVT_BLK=0xec00-0xec03 PM1a_CNT_BLK=0xec04-0xec05 PM2_CNT_BLK=0xec30-0xec30 PM_TMR_BLK=0xec08-0xec0b GPE0_BLK=0xec18-0xec1b GPE1_BLK=0xec1c-0xec1f, GPE1_BASE=16 P_LVL2_LAT=90 us, P_LVL3_LAT=900 us FLUSH_SIZE=0, FLUSH_STRIDE=0 DUTY_OFFSET=1, DUTY_WIDTH=0 DAY_ALRM=13, MON_ALRM=0, CENTURY=0 IAPC_BOOT_ARCH= Flags={WBINVD,PROC_C1,SLP_BUTTON,RTC_S4} -- R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: oberman@es.net Phone: +1 510 486-8634 From owner-freebsd-acpi@FreeBSD.ORG Sat Sep 25 04:44:18 2004 Return-Path: Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D3BDF16A4CE for ; Sat, 25 Sep 2004 04:44:18 +0000 (GMT) Received: from samuelstringham.com (cs666986-52.satx.rr.com [66.69.86.52]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5C48043D3F for ; Sat, 25 Sep 2004 04:44:18 +0000 (GMT) (envelope-from samuel@mail.samuelstringham.com) Received: from laptop.samuelstringham.com (laptop [127.0.0.1]) by samuelstringham.com (8.13.1/8.13.1) with ESMTP id i8P3atoh003309 for ; Fri, 24 Sep 2004 22:36:56 -0500 (CDT) (envelope-from samuel@laptop.samuelstringham.com) Received: (from samuel@localhost) by laptop.samuelstringham.com (8.13.1/8.13.1/Submit) id i8P3at9M003308 for freebsd-acpi@freebsd.org; Fri, 24 Sep 2004 22:36:55 -0500 (CDT) (envelope-from samuel) Date: Fri, 24 Sep 2004 22:36:55 -0500 From: Samuel Stringham To: freebsd-acpi@freebsd.org Message-ID: <20040925033655.GB2967@laptop.samuelstringham.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="AqsLC8rIMeq19msA" Content-Disposition: inline X-Operating-System: "FreeBSD 5.3-BETA4" X-PGP-Key: http://samuelstringham.com/samuel.asc User-Agent: Mutt/1.5.6i Subject: Dell Inspiron 4000 woes X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Samuel Stringham List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 25 Sep 2004 04:44:18 -0000 --AqsLC8rIMeq19msA Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hello, I have a Dell Inspiron 4000, which is running 5.3-BETA5. I am unable to get the ACPI to function correctly on this machine. I have dug around google for hours, looked=20 through the source (though I am not quite familiar enough to make changes), but could not find any great howtos on getting the suspend/resume working how I would like. Here is the state now: S1: will detach wireless card, leave hard drive spun, not sure about CPU stepping. When suspending from X, it first switches to console, then 'freezes' without turning off the LCD. S2: not tested/supported S3: will detach pcmcia wireless card, spin down hard drive, not sure about CPU stepping. When suspending from X, it first switches to console, then turns off for a second,=20 then turns back on completely _white_. S4: I don't have a partition to handle this correctly. S5: shutdown, as expected. So, I have come to realize that S3 will probably be my best bet. However, I can't get the monitor to turn off. I was wondering if anyone else had any good hints on getting this working correctly. My configuration output is located here: http://samuelstringham.com/devinfo.txt http://samuelstringham.com/dmesg.txt http://samuelstringham.com/kldstat.txt http://samuelstringham.com/pciconf.txt http://samuelstringham.com/sysctl.txt http://samuelstringham.com/dell_insp_4000_samuelstringham.dsl And the only thing I have done to my rc.resume/suspend=20 scripts is the addition of: sysctl hw.acpi.video.lcd0.active=3D1 to rc.resume, so that my monitor comes back up correctly. If I leave this out, sometimes my X will look like the=20 timings are off or something (like a shadow image across the right hand side of the screen). Please help, and much karma will be in store for you. Best regards, Samuel Stringham --AqsLC8rIMeq19msA Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (FreeBSD) iD8DBQFBVOfXBz+QjiNF1oARAlRLAKCh8G6HGqyhaxbnN6fIpY/iGGu9DgCfYOjr as0DODQfLkCOeZhuWM2HimI= =faJB -----END PGP SIGNATURE----- --AqsLC8rIMeq19msA-- From owner-freebsd-acpi@FreeBSD.ORG Sat Sep 25 17:55:19 2004 Return-Path: Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C67C916A4CE for ; Sat, 25 Sep 2004 17:55:19 +0000 (GMT) Received: from www.cryptography.com (li-22.members.linode.com [64.5.53.22]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8FC2443D2D for ; Sat, 25 Sep 2004 17:55:17 +0000 (GMT) (envelope-from nate@root.org) Received: from [10.0.5.50] (adsl-64-171-186-250.dsl.snfc21.pacbell.net [64.171.186.250]) by www.cryptography.com (8.12.8/8.12.8) with ESMTP id i8PHtCDl032189 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Sat, 25 Sep 2004 10:55:14 -0700 Message-ID: <4155B100.3030601@root.org> Date: Sat, 25 Sep 2004 10:55:12 -0700 From: Nate Lawson User-Agent: Mozilla Thunderbird 0.7.3 (Windows/20040803) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Andriy Gapon References: <1095693793.00135239.1095680401@10.7.7.3> <4151AD92.8050905@icyb.net.ua> In-Reply-To: <4151AD92.8050905@icyb.net.ua> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit cc: freebsd-acpi@freebsd.org Subject: Re: acpi fan does not lower speed when CPU temp is back to low X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 25 Sep 2004 17:55:19 -0000 Andriy Gapon wrote: > on 20.09.2004 14:38 Saulius Menkevicius said the following: > >>Is there a way to find why the ACPI code does not lower >>CPU fan speed when temperature drops back to low (as set in BIOS)? >>It does turn the speed to 100% when temperature gets high. >> >>Can it be a buggy BIOS ACPI? Though it's working fine in Windows. >> >>The motherboard is Abit IS7, desktop with a P4 2.4C. >>Running 5.3-BETA4. > > > turning fans on/off is done by OS (kernel), but it is done > through calling ACPI methods, so the problem can be in either place. > Try to take dump of your ACPI DSDT (using acpidump) and look for FAN > device section in there. You can post it to the list or send to me in > private. > If you are ineterested, you can also google for ACPI specs and download > them, they are not very hard to comperehend (but bulky). Build your acpi module with options ACPI_DEBUG. Then put this in loader.conf: hw.acpi.verbose="1" debug.acpi.layer="ACPI_THERMAL" debug.acpi.level="ACPI_LV_ALL_EXCEPTIONS" Send the dmesg output including any fan events. BTW, a lot of this info is in the acpi(4) man page and the ACPI debugging section of the handbook. -- Nate From owner-freebsd-acpi@FreeBSD.ORG Sat Sep 25 19:24:52 2004 Return-Path: Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id AFD3A16A4CE for ; Sat, 25 Sep 2004 19:24:52 +0000 (GMT) Received: from www.cryptography.com (li-22.members.linode.com [64.5.53.22]) by mx1.FreeBSD.org (Postfix) with ESMTP id 78EB643D39 for ; Sat, 25 Sep 2004 19:24:52 +0000 (GMT) (envelope-from nate@root.org) Received: from [10.0.5.50] (adsl-64-171-186-250.dsl.snfc21.pacbell.net [64.171.186.250]) by www.cryptography.com (8.12.8/8.12.8) with ESMTP id i8PJOoDl001217 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Sat, 25 Sep 2004 12:24:51 -0700 Message-ID: <4155C602.4050709@root.org> Date: Sat, 25 Sep 2004 12:24:50 -0700 From: Nate Lawson User-Agent: Mozilla Thunderbird 0.7.3 (Windows/20040803) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Samuel Stringham References: <20040925033655.GB2967@laptop.samuelstringham.com> In-Reply-To: <20040925033655.GB2967@laptop.samuelstringham.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit cc: freebsd-acpi@freebsd.org Subject: Re: Dell Inspiron 4000 woes X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 25 Sep 2004 19:24:52 -0000 Samuel Stringham wrote: > I have a Dell Inspiron 4000, which is running 5.3-BETA5. > I am unable to get the ACPI to function correctly on this > machine. I have dug around google for hours, looked > through the source (though I am not quite familiar enough > to make changes), but could not find any great howtos on > getting the suspend/resume working how I would like. If suspend/resume is vital, try apm. There are still some problems with suspend/resume, many of them in the display system (handled by X.) > S3: will detach pcmcia wireless card, spin down hard drive, > not sure about CPU stepping. When suspending from X, it > first switches to console, then turns off for a second, > then turns back on completely _white_. There's an option, like SYSCONS_NO_VTY_SWITCH (or similar), that disables that switch. See if it helps. > So, I have come to realize that S3 will probably be my best > bet. However, I can't get the monitor to turn off. I was > wondering if anyone else had any good hints on getting this > working correctly. Turning off the monitor requires DPMS support and a proper PCI/AGP video driver. -- Nate From owner-freebsd-acpi@FreeBSD.ORG Sat Sep 25 19:54:40 2004 Return-Path: Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 818B316A4CE for ; Sat, 25 Sep 2004 19:54:40 +0000 (GMT) Received: from samuelstringham.com (nat-vlan200.sat.rackspace.com [64.39.1.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id F192A43D2D for ; Sat, 25 Sep 2004 19:54:39 +0000 (GMT) (envelope-from samuel@mail.samuelstringham.com) Received: from laptop.samuelstringham.com (laptop [127.0.0.1]) by samuelstringham.com (8.13.1/8.13.1) with ESMTP id i8PJkm8X031202; Sat, 25 Sep 2004 14:46:49 -0500 (CDT) (envelope-from samuel@laptop.samuelstringham.com) Received: (from samuel@localhost)i8PJkmEL031201; Sat, 25 Sep 2004 14:46:48 -0500 (CDT) (envelope-from samuel) Date: Sat, 25 Sep 2004 14:46:48 -0500 From: Samuel Stringham To: Nate Lawson Message-ID: <20040925194648.GB5159@laptop.samuelstringham.com> References: <20040925033655.GB2967@laptop.samuelstringham.com> <4155C602.4050709@root.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="NDin8bjvE/0mNLFQ" Content-Disposition: inline In-Reply-To: <4155C602.4050709@root.org> X-Operating-System: "FreeBSD 5.3-BETA4" X-PGP-Key: http://samuelstringham.com/samuel.asc User-Agent: Mutt/1.5.6i cc: freebsd-acpi@freebsd.org Subject: Re: Dell Inspiron 4000 woes X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Samuel Stringham List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 25 Sep 2004 19:54:40 -0000 --NDin8bjvE/0mNLFQ Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sat, Sep 25, 2004 at 12:24:50PM -0700, Nate Lawson wrote: > Samuel Stringham wrote: > >I have a Dell Inspiron 4000, which is running 5.3-BETA5. > >I am unable to get the ACPI to function correctly on this > >machine. I have dug around google for hours, looked=20 > >through the source (though I am not quite familiar enough > >to make changes), but could not find any great howtos on > >getting the suspend/resume working how I would like. >=20 > If suspend/resume is vital, try apm. There are still some problems with= =20 > suspend/resume, many of them in the display system (handled by X.) It isn't that vital ;-) I am more interested in solving the=20 problem, than in the solution state. >=20 > >S3: will detach pcmcia wireless card, spin down hard drive, > >not sure about CPU stepping. When suspending from X, it > >first switches to console, then turns off for a second,=20 > >then turns back on completely _white_. >=20 > There's an option, like SYSCONS_NO_VTY_SWITCH (or similar), that=20 > disables that switch. See if it helps. If I turn this on (SC_NO_VTY_SWITCH), then sometimes my laptop will start an interrrupt storm on resume, and have no video. I can type blind for a couple seconds, but then upon the=20 attempt to re-initialize the display, it slows very quickly to nothingness. >=20 > >So, I have come to realize that S3 will probably be my best > >bet. However, I can't get the monitor to turn off. I was > >wondering if anyone else had any good hints on getting this > >working correctly. >=20 > Turning off the monitor requires DPMS support and a proper PCI/AGP video= =20 > driver. DPMS support is enabled, and working. =20 'xset -display :0 dpms force off' works as expected. Also, the fact that it turns white instead=20 of off leads me to believe it may be a mis-guessed register=20 location on the radeon 128. I downloaded a C program called radeontool to try and find the right registers to use to turn this off, but cannot find the associated function in the acpi video handling code. I am assuming someone else will have way more intimate knowledge with the kernel codebase than me. Thank you kindly for your insight, and I will continue to look for a graceful solution. >=20 > --=20 > Nate Best, Samuel Stringham --NDin8bjvE/0mNLFQ Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (FreeBSD) iD8DBQFBVcsoBz+QjiNF1oARAkZCAJ4848e6LT/ETGXng5d19aY8adNcOQCdHawz Mx6Pp/8adsSUisGnzVe7c6M= =Lb7e -----END PGP SIGNATURE----- --NDin8bjvE/0mNLFQ--