From jkim at FreeBSD.org Thu Oct 1 21:02:22 2009 From: jkim at FreeBSD.org (Jung-uk Kim) Date: Thu Oct 1 21:02:29 2009 Subject: ACPI_DEBUG: undefined symbol in acpi.ko In-Reply-To: <4AC347EE.20308@icyb.net.ua> References: <4AC347EE.20308@icyb.net.ua> Message-ID: <200910011702.12127.jkim@FreeBSD.org> On Wednesday 30 September 2009 07:58 am, Andriy Gapon wrote: > With the latest head sources: > $ make buildkernel KERNCONF=GENERICacpidbg __MAKE_CONF=/dev/null > TARGET=i386 ... > $ nm > /usr/obj/i386/usr/src/sys/GENERICacpidbg/modules/usr/src/sys/module >s/acpi/acpi/acpi.ko > > | fgrep AcpiDmDumpMethodInfo > > U AcpiDmDumpMethodInfo > > $ cat sys/i386/conf/GENERICacpidbg > ident GENERICapcidbg > include GENERIC > options ACPI_DEBUG > > Looks like a build problem. > > Apparently the same happens with 7.2 without cross-build. This has been a long standing problem for ACPI kernel module. Please try r197688. It should fix the problem. Jung-uk Kim From kama at pvp.se Fri Oct 2 11:24:10 2009 From: kama at pvp.se (kama) Date: Fri Oct 2 11:24:16 2009 Subject: FreeBSD 7.2-STABLE boot freeze In-Reply-To: <4AC35CC6.1020103@freebsd.org> References: <20090921140345.H37424@ns1.as.pvp.se> <20090922103150.V37424@ns1.as.pvp.se> <4AB8A95E.3060307@icyb.net.ua> <20090922142526.P37424@ns1.as.pvp.se> <4AB8E082.8050100@icyb.net.ua> <20090922215700.V37424@ns1.as.pvp.se> <4ABA1D1F.3080704@icyb.net.ua> <20090923171004.Q37424@ns1.as.pvp.se> <4ABA457E.3060800@freebsd.org> <20090924141927.Y37424@ns1.as.pvp.se> <20090925110209.E37424@ns1.as.pvp.se> <4ABC894E.7040204@freebsd.org> <20090928092026.B37424@ns1.as.pvp.se> <4AC06ED6.7030402@freebsd.org> <20090928235136.F37424@ns1.as.pvp.se> <20090929085000.B37424@ns1.as.pvp.se> <4AC211AC.1070404@freebsd.org> <20090929204651.G37424@ns1.as.pvp.se> <4AC34952.9010508@freebsd.org> <20090930151542.G37424@ns1.as.pvp.se> <4AC35CC6.1020103@freebsd.org> Message-ID: <20091002132218.P37424@ns1.as.pvp.se> On Wed, 30 Sep 2009, Andriy Gapon wrote: > on 30/09/2009 16:21 kama said the following: > > > > It boot occationally. It does not seem to matter if I include the acpi > > device into the kernel or not. > > > > I get this message in an verbose boot: > > KLD file acpi.ko - could not finalize loading > > Do you get this message in all cases? That is, every time you tried? > Or only with ACPI_DEBUG defined? I cant recall. I have tried so many things lately. But I believe I get it on a verbose boot without ACPI_DEBUG. Im currently rebuilding the system to 8.0. /Bjorn From kama at pvp.se Fri Oct 2 21:28:38 2009 From: kama at pvp.se (kama) Date: Fri Oct 2 21:28:43 2009 Subject: FreeBSD 7.2-STABLE boot freeze In-Reply-To: <20091002132218.P37424@ns1.as.pvp.se> References: <20090921140345.H37424@ns1.as.pvp.se> <20090922103150.V37424@ns1.as.pvp.se> <4AB8A95E.3060307@icyb.net.ua> <20090922142526.P37424@ns1.as.pvp.se> <4AB8E082.8050100@icyb.net.ua> <20090922215700.V37424@ns1.as.pvp.se> <4ABA1D1F.3080704@icyb.net.ua> <20090923171004.Q37424@ns1.as.pvp.se> <4ABA457E.3060800@freebsd.org> <20090924141927.Y37424@ns1.as.pvp.se> <20090925110209.E37424@ns1.as.pvp.se> <4ABC894E.7040204@freebsd.org> <20090928092026.B37424@ns1.as.pvp.se> <4AC06ED6.7030402@freebsd.org> <20090928235136.F37424@ns1.as.pvp.se> <20090929085000.B37424@ns1.as.pvp.se> <4AC211AC.1070404@freebsd.org> <20090929204651.G37424@ns1.as.pvp.se> <4AC34952.9010508@freebsd.org> <20090930151542.G37424@ns1.as.pvp.se> <4AC35CC6.1020103@freebsd.org> <20091002132218.P37424@ns1.as.pvp.se> Message-ID: <20091002212626.O37424@ns1.as.pvp.se> On Fri, 2 Oct 2009, kama wrote: > > > On Wed, 30 Sep 2009, Andriy Gapon wrote: > > > on 30/09/2009 16:21 kama said the following: > > > > > > It boot occationally. It does not seem to matter if I include the acpi > > > device into the kernel or not. > > > > > > I get this message in an verbose boot: > > > KLD file acpi.ko - could not finalize loading > > > > Do you get this message in all cases? That is, every time you tried? > > Or only with ACPI_DEBUG defined? > > I cant recall. I have tried so many things lately. But I believe I get it > on a verbose boot without ACPI_DEBUG. > > Im currently rebuilding the system to 8.0. Just upgrading to 8.0 did not help regarding the freezes. I ran into the bge freeze bug too when disabling acpi. I then read the acpi-manpage abit more carefully. With ACPI_DEBUG and debug.acpi.disabled="timer" in loader.conf and verbose boot seems to help against the freeze and freezes again if I dont run it in verbose mode. But thats just after 5 starts. Anyhow its better. loader.conf: debug.acpi.disabled="timer" debug.acpi.layer="ACPI_ALL_COMPONENTS" debug.acpi.level="ACPI_LV_VERBOSE,ACPI_LV_VERBOSITY3,ACPI_LV_VERBOSITY1,ACPI_LV_ALL_EXCEPTIONS" I dont know if the output below gives anything. /Bjorn # dmesg | grep -i acpi ACPI set debug layer 'ACPI_ALL_COMPONENTS' level 'ACPI_LV_VERBOSE,ACPI_LV_VERBOSITY3,ACPI_LV_VERBOSITY1,ACPI_LV_ALL_EXCEPTIONS' MADT: Found CPU APIC ID 0 ACPI ID 0: enabled MADT: Found CPU APIC ID 2 ACPI ID 2: enabled MADT: Found CPU APIC ID 4 ACPI ID 4: disabled MADT: Found CPU APIC ID 6 ACPI ID 6: disabled MADT: Found CPU APIC ID 1 ACPI ID 1: enabled MADT: Found CPU APIC ID 3 ACPI ID 3: enabled MADT: Found CPU APIC ID 5 ACPI ID 5: disabled MADT: Found CPU APIC ID 7 ACPI ID 7: disabled ACPI APIC Table: APIC: CPU 0 has ACPI ID 0 APIC: CPU 1 has ACPI ID 1 APIC: CPU 2 has ACPI ID 2 APIC: CPU 3 has ACPI ID 3 ACPI: RSDP 0xf4f20 00024 (v2 HP ) ACPI: XSDT 0xbfff83e0 00044 (v1 HP A05 00000002 \M-R\^D 0000162E) ACPI: FACP 0xbfff8460 000F4 (v3 HP A05 00000002 \M-R\^D 0000162E) ACPI Warning: Invalid length for Pm1aControlBlock: 32, using default 16 20090521 tbfadt-707 ACPI Warning: Invalid length for Pm1bControlBlock: 32, using default 16 20090521 tbfadt-707 ACPI: DSDT 0xbfff8560 0422D (v1 HP DSDT 00000001 MSFT 02000001) ACPI: FACS 0xbfff80c0 00040 ACPI: APIC 0xbfff8100 000B8 (v1 HP 00000083 00000002 00000000) ACPI: SPCR 0xbfff81e0 00050 (v1 HP SPCRRBSU 00000001 \M-R\^D 0000162E) ACPI: SRAT 0xbfff8260 00150 (v1 HP A05 00000001 00000000) acpi0: on motherboard acpi0: [MPSAFE] acpi0: [ITHREAD] ACPI: SSDT 0xbfffd000 0059D (v1 HP SSDT0 00000001 MSFT 02000001) ACPI: SSDT 0xbfffd700 0059D (v1 HP SSDT1 00000001 MSFT 02000001) ACPI: SSDT 0xbfffde00 0059D (v1 HP SSDT2 00000001 MSFT 02000001) ACPI: SSDT 0xbfffe500 0059D (v1 HP SSDT3 00000001 MSFT 02000001) acpi0: Power Button (fixed) acpi0: wakeup code va 0xc62cd000 pa 0x1000 AcpiOsDerivePciId: \\_SB_.CFG0.NDE0.NDE0 -> bus 0 dev 24 func 0 AcpiOsDerivePciId: \\_SB_.CFG0.MEMC.MEMC -> bus 0 dev 24 func 1 AcpiOsDerivePciId: \\_SB_.CFG0.PCI0.PCI0 -> bus 0 dev 3 func 0 AcpiOsDerivePciId: \\_SB_.CFG0.IBRG.IBRG -> bus 0 dev 4 func 0 AcpiOsDerivePciId: \\_SB_.CFG0.PCI1.PCI1 -> bus 0 dev 7 func 0 AcpiOsDerivePciId: \\_SB_.CFG0.PCI2.PCI2 -> bus 0 dev 8 func 0 AcpiOsDerivePciId: \\_SB_.CFG1.PCI3.PCI3 -> bus 4 dev 9 func 0 AcpiOsDerivePciId: \\_SB_.CFG1.PCI4.PCI4 -> bus 4 dev 10 func 0 AcpiOsDerivePciId: \\_SB_.CFG0.TSMM.TSMM -> bus 0 dev 4 func 3 pcib0: on acpi0 pci0: on pcib0 pcib1: at device 3.0 on pci0 pci1: on pcib1 pcib2: at device 7.0 on pci0 pci2: on pcib2 pcib3: at device 8.0 on pci0 pci3: on pcib3 pcib4: on acpi0 pci4: on pcib4 pcib5: at device 9.0 on pci4 pci5: on pcib5 pcib6: at device 10.0 on pci4 pci6: on pcib6 atkbdc0: port 0x60,0x64 irq 1 on acpi0 psmcpnp0: irq 12 on acpi0 uart0: <16550 or compatible> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0 fdc0: port 0x3f2-0x3f5 irq 6 drq 2 on acpi0 cpu0: on acpi0 cpu1: on acpi0 cpu2: on acpi0 cpu3: on acpi0 From bugmaster at FreeBSD.org Mon Oct 5 11:06:46 2009 From: bugmaster at FreeBSD.org (FreeBSD bugmaster) Date: Mon Oct 5 11:06:59 2009 Subject: Current problem reports assigned to freebsd-acpi@FreeBSD.org Message-ID: <200910051106.n95B6j6H088571@freefall.freebsd.org> Note: to view an individual PR, use: http://www.freebsd.org/cgi/query-pr.cgi?pr=(number). The following is a listing of current problems submitted by FreeBSD users. These represent problem reports covering all versions including experimental development code and obsolete releases. S Tracker Resp. Description -------------------------------------------------------------------------------- o kern/139088 acpi [acpi] ACPI Exception: AE_AML_INFINITE_LOOP error o amd64/138210 acpi [acpi] acer aspire 5536 ACPI problems (S3, brightness, o bin/137053 acpi [hang] FreeBSD 8.0 BETA2Compaq Mini 700 locks on boot o kern/137042 acpi [acpi] hp laptop's lcd not wakes up after suspend to r o kern/136808 acpi [acpi] panic when switching to s3 o i386/136008 acpi [acpi] Dell Vostro 1310 will not shutdown (Requires us o bin/135349 acpi [patch] teach acpidump(8) to disassemble arbitrary mem o kern/135070 acpi [acpi] [patch] BIOS resource allocation and FreeBSD AC o kern/132602 acpi [acpi] ACPI Problem with Intel SS4200: System does not o kern/130683 acpi [ACPI] shutdown hangs after syncing disks - ACPI race? o i386/129953 acpi [acpi] ACPI timeout (CDROM) with Shuttle X27D o kern/129618 acpi [acpi] Problem with ACPI on HP Pavilion DV2899 laptop o kern/129563 acpi [acpi] sleep broken on IBM/Lenovo T61 in amd64 mode f kern/128639 acpi [patch] [acpi_asus] acpi for ASUS A6F,A3E,A3F,A3N not f kern/128634 acpi [patch] fix acpi_asus(4) in asus a6f laptop o kern/127581 acpi [patch] [acpi_sony] Add support for more Sony features o kern/124744 acpi [acpi] [patch] incorrect _BST result validation for To o kern/124412 acpi [acpi] power off error on Toshiba M40 laptop o kern/123039 acpi [acpi] ACPI AML_BUFFER_LIMIT errors during boot o kern/121504 acpi [patch] Correctly set hw.acpi.osname on certain machin f kern/121454 acpi [pst] Promise SuperTrak SX6000 does not load during bo o amd64/121439 acpi [boot] Installation of FreeBSD 7.0 fails: ACPI problem o kern/121102 acpi [acpi_fujitsu] [patch] update acpi_fujitsu for the P80 o kern/120515 acpi [acpi] [patch] acpi_alloc_wakeup_handler: can't alloc o kern/119356 acpi [acpi]: i386 ACPI wakeup not work due resource exhaust o kern/119200 acpi [acpi] Lid close switch suspends CPU for 1 second on H o kern/118973 acpi [acpi]: Kernel panic with acpi boot o kern/117605 acpi [acpi] [request] add debug.cpufreq.highest o kern/116939 acpi [acpi] PCI-to-PCI misconfigured for bus three and can o i386/114562 acpi [acpi] cardbus is dead after s3 on Thinkpad T43 with a o kern/114165 acpi [acpi] Dell C810 - ACPI problem s kern/112544 acpi [acpi] [patch] Add High Precision Event Timer Driver f o kern/108954 acpi [acpi] 'sleep(1)' sleeps >1 seconds when speedstep (Cx o kern/108695 acpi [acpi]: Fatal trap 9: general protection fault when in o kern/108488 acpi [acpi] ACPI-1304: *** Error: Method execution failed o kern/108017 acpi [acpi]: Acer Aspire 5600 o kern/106924 acpi [acpi] ACPI resume returns g_vfs_done() errors and ker o kern/105537 acpi [acpi] problems in acpi on HP Compaq nc6320 o kern/104625 acpi ACPI on ASUS A8N-32 SLI/ASUS P4P800 does not show ther o kern/102252 acpi acpi thermal does not work on Abit AW8D (intel 975) o kern/97383 acpi Volume buttons on IBM Thinkpad crash system with ACPI s i386/91748 acpi acpi problem on Acer TravelMare 4652LMi (nvidia panic, s kern/91038 acpi [panic] [ata] [acpi] 6.0-RELEASE on Fujitsu Siemens Am s kern/90243 acpi Laptop fan doesn't turn off (ACPI enabled) (Packard Be o i386/83018 acpi [install] Installer will not boot on Asus P4S8X BIOS 1 f kern/81000 acpi [apic] Via 8235 sound card worked great with FreeBSD 5 o i386/79081 acpi ACPI suspend/resume not working on HP nx6110 o kern/76950 acpi ACPI wrongly blacklisted on Micron ClientPro 766Xi sys s kern/73823 acpi [request] acpi / power-on by timer support o i386/72566 acpi ACPI, FreeBSD disables fan on Compaq Armada 1750 o i386/69750 acpi Boot without ACPI failed on ASUS L5 o kern/56024 acpi ACPI suspend drains battery while in S3 o i386/55661 acpi ACPI suspend/resume problem on ARMADA M700 o i386/54756 acpi ACPI suspend/resume problem on CF-W2 laptop 54 problems total. From patrick at code-monkey.nl Sat Oct 10 17:55:02 2009 From: patrick at code-monkey.nl (patrick) Date: Sat Oct 10 17:55:09 2009 Subject: ICH7 watchdog Message-ID: <20091010173557.ee589825@f89199.upc-f.chello.nl> Does anyone have an example in C to reset the hardware watchdog? I tried the man 4 watchdog example, but it doesn't reset the timer though. I have a supermicro mainboard with the Intel ICH7 on it. Thanks Patrick From mike at sentex.net Sat Oct 10 23:31:25 2009 From: mike at sentex.net (Mike Tancsa) Date: Sat Oct 10 23:31:36 2009 Subject: ICH7 watchdog In-Reply-To: <20091010173557.ee589825@f89199.upc-f.chello.nl> References: <20091010173557.ee589825@f89199.upc-f.chello.nl> Message-ID: <200910102253.n9AMrF0H067046@lava.sentex.ca> At 01:35 PM 10/10/2009, patrick wrote: >Does anyone have an example in C to reset the hardware watchdog? >I tried the man 4 watchdog example, but it doesn't reset the timer though. >I have a supermicro mainboard with the Intel ICH7 on it. Hi, Take a look at the source code in /usr/src/sys/dev/ichwd and /usr/src/usr.sbin/watchdogd ---Mike >Thanks >Patrick >_______________________________________________ >freebsd-acpi@freebsd.org mailing list >http://lists.freebsd.org/mailman/listinfo/freebsd-acpi >To unsubscribe, send any mail to "freebsd-acpi-unsubscribe@freebsd.org" -------------------------------------------------------------------- Mike Tancsa, tel +1 519 651 3400 Sentex Communications, mike@sentex.net Providing Internet since 1994 www.sentex.net Cambridge, Ontario Canada www.sentex.net/mike From uqs at spoerlein.net Sun Oct 11 14:23:00 2009 From: uqs at spoerlein.net (Ulrich =?utf-8?B?U3DDtnJsZWlu?=) Date: Sun Oct 11 14:23:12 2009 Subject: ACPI Warning: Converted Buffer to expected String Message-ID: <20091011142256.GA3770@roadrunner.spoerlein.net> Just FYI, Dell Inspiron 8600c laptop, semi-recent CURRENT, latest BIOS (A14), machine is 5 years old and producing these warnings when inserting a battery (or booting with one inserted) ACPI Warning for \\_SB_.BAT0._BIF: Converted Buffer to expected String at index 9 (20090903/nsrepair-215) ACPI Warning for \\_SB_.BAT0._BIF: Converted Buffer to expected String at index 10 (20090903/nsrepair-215) ACPI Warning for \\_SB_.BAT0._BIF: Converted Buffer to expected String at index 11 (20090903/nsrepair-215) ACPI Warning for \\_SB_.BAT0._BIF: Converted Buffer to expected String at index 12 (20090903/nsrepair-215) Everything works just before the ACPI import, there's also another bunch of (harmless) errors during boot. acpi0: on motherboard acpi0: [ITHREAD] acpi0: reservation of 0, 9fc00 (3) failed acpi0: reservation of 100000, 3fef0000 (3) failed This is just for reference, perhaps someone wants to know. Cheers, Uli From bugmaster at FreeBSD.org Mon Oct 12 11:06:46 2009 From: bugmaster at FreeBSD.org (FreeBSD bugmaster) Date: Mon Oct 12 11:07:09 2009 Subject: Current problem reports assigned to freebsd-acpi@FreeBSD.org Message-ID: <200910121106.n9CB6jBp036273@freefall.freebsd.org> Note: to view an individual PR, use: http://www.freebsd.org/cgi/query-pr.cgi?pr=(number). The following is a listing of current problems submitted by FreeBSD users. These represent problem reports covering all versions including experimental development code and obsolete releases. S Tracker Resp. Description -------------------------------------------------------------------------------- o kern/139088 acpi [acpi] ACPI Exception: AE_AML_INFINITE_LOOP error o amd64/138210 acpi [acpi] acer aspire 5536 ACPI problems (S3, brightness, o bin/137053 acpi [hang] FreeBSD 8.0 BETA2Compaq Mini 700 locks on boot o kern/137042 acpi [acpi] hp laptop's lcd not wakes up after suspend to r o kern/136808 acpi [acpi] panic when switching to s3 o i386/136008 acpi [acpi] Dell Vostro 1310 will not shutdown (Requires us o bin/135349 acpi [patch] teach acpidump(8) to disassemble arbitrary mem o kern/135070 acpi [acpi] [patch] BIOS resource allocation and FreeBSD AC o kern/132602 acpi [acpi] ACPI Problem with Intel SS4200: System does not o kern/130683 acpi [ACPI] shutdown hangs after syncing disks - ACPI race? o i386/129953 acpi [acpi] ACPI timeout (CDROM) with Shuttle X27D o kern/129618 acpi [acpi] Problem with ACPI on HP Pavilion DV2899 laptop o kern/129563 acpi [acpi] sleep broken on IBM/Lenovo T61 in amd64 mode f kern/128639 acpi [patch] [acpi_asus] acpi for ASUS A6F,A3E,A3F,A3N not f kern/128634 acpi [patch] fix acpi_asus(4) in asus a6f laptop o kern/127581 acpi [patch] [acpi_sony] Add support for more Sony features o kern/124744 acpi [acpi] [patch] incorrect _BST result validation for To o kern/124412 acpi [acpi] power off error on Toshiba M40 laptop o kern/123039 acpi [acpi] ACPI AML_BUFFER_LIMIT errors during boot o kern/121504 acpi [patch] Correctly set hw.acpi.osname on certain machin f kern/121454 acpi [pst] Promise SuperTrak SX6000 does not load during bo o amd64/121439 acpi [boot] Installation of FreeBSD 7.0 fails: ACPI problem o kern/121102 acpi [acpi_fujitsu] [patch] update acpi_fujitsu for the P80 o kern/120515 acpi [acpi] [patch] acpi_alloc_wakeup_handler: can't alloc o kern/119356 acpi [acpi]: i386 ACPI wakeup not work due resource exhaust o kern/119200 acpi [acpi] Lid close switch suspends CPU for 1 second on H o kern/118973 acpi [acpi]: Kernel panic with acpi boot o kern/117605 acpi [acpi] [request] add debug.cpufreq.highest o kern/116939 acpi [acpi] PCI-to-PCI misconfigured for bus three and can o i386/114562 acpi [acpi] cardbus is dead after s3 on Thinkpad T43 with a o kern/114165 acpi [acpi] Dell C810 - ACPI problem s kern/112544 acpi [acpi] [patch] Add High Precision Event Timer Driver f o kern/108954 acpi [acpi] 'sleep(1)' sleeps >1 seconds when speedstep (Cx o kern/108695 acpi [acpi]: Fatal trap 9: general protection fault when in o kern/108488 acpi [acpi] ACPI-1304: *** Error: Method execution failed o kern/108017 acpi [acpi]: Acer Aspire 5600 o kern/106924 acpi [acpi] ACPI resume returns g_vfs_done() errors and ker o kern/105537 acpi [acpi] problems in acpi on HP Compaq nc6320 o kern/104625 acpi ACPI on ASUS A8N-32 SLI/ASUS P4P800 does not show ther o kern/102252 acpi acpi thermal does not work on Abit AW8D (intel 975) o kern/97383 acpi Volume buttons on IBM Thinkpad crash system with ACPI s i386/91748 acpi acpi problem on Acer TravelMare 4652LMi (nvidia panic, s kern/91038 acpi [panic] [ata] [acpi] 6.0-RELEASE on Fujitsu Siemens Am s kern/90243 acpi Laptop fan doesn't turn off (ACPI enabled) (Packard Be o i386/83018 acpi [install] Installer will not boot on Asus P4S8X BIOS 1 f kern/81000 acpi [apic] Via 8235 sound card worked great with FreeBSD 5 o i386/79081 acpi ACPI suspend/resume not working on HP nx6110 o kern/76950 acpi ACPI wrongly blacklisted on Micron ClientPro 766Xi sys s kern/73823 acpi [request] acpi / power-on by timer support o i386/72566 acpi ACPI, FreeBSD disables fan on Compaq Armada 1750 o i386/69750 acpi Boot without ACPI failed on ASUS L5 o kern/56024 acpi ACPI suspend drains battery while in S3 o i386/55661 acpi ACPI suspend/resume problem on ARMADA M700 o i386/54756 acpi ACPI suspend/resume problem on CF-W2 laptop 54 problems total. From jkim at FreeBSD.org Tue Oct 13 15:33:33 2009 From: jkim at FreeBSD.org (Jung-uk Kim) Date: Tue Oct 13 15:33:45 2009 Subject: ACPI Warning: Converted Buffer to expected String In-Reply-To: <20091011142256.GA3770@roadrunner.spoerlein.net> References: <20091011142256.GA3770@roadrunner.spoerlein.net> Message-ID: <200910131133.16487.jkim@FreeBSD.org> On Sunday 11 October 2009 10:22 am, Ulrich Sp?rlein wrote: > Just FYI, > > Dell Inspiron 8600c laptop, semi-recent CURRENT, latest BIOS (A14), > machine is 5 years old and producing these warnings when inserting > a battery (or booting with one inserted) > > ACPI Warning for \\_SB_.BAT0._BIF: Converted Buffer to expected > String at index 9 (20090903/nsrepair-215) ACPI Warning for > \\_SB_.BAT0._BIF: Converted Buffer to expected String at index 10 > (20090903/nsrepair-215) ACPI Warning for \\_SB_.BAT0._BIF: > Converted Buffer to expected String at index 11 > (20090903/nsrepair-215) ACPI Warning for \\_SB_.BAT0._BIF: > Converted Buffer to expected String at index 12 > (20090903/nsrepair-215) These are just informational. FYI, new ACPICA checks predefined method/object types per spec. and tries to correct common DSDT errors. Previously these "quirks" were handled by OS layer case by case. The warning message is telling you that _BIF method (get battery information) returned Buffer object instead of String object and ACPICA corrected the errors. In fact, this is a very common mistake by laptop BIOS writers. Thus, it is automatically corrected by new ACPICA. However, if you see "ACPI Error", that's something to worry about, e.g., cannot convert predefined types. > Everything works just before the ACPI import, there's also another > bunch of (harmless) errors during boot. > > acpi0: on motherboard > acpi0: [ITHREAD] > acpi0: reservation of 0, 9fc00 (3) failed > acpi0: reservation of 100000, 3fef0000 (3) failed > > This is just for reference, perhaps someone wants to know. It is harmless. Jung-uk Kim From robert.moore at intel.com Tue Oct 13 20:48:31 2009 From: robert.moore at intel.com (Moore, Robert) Date: Tue Oct 13 20:49:13 2009 Subject: ACPICA version 20091013 released Message-ID: <4911F71203A09E4D9981D27F9D8308583B31AFCB@orsmsx503.amr.corp.intel.com> 13 October 2009. Summary of changes for version 20091013: This release is available at www.acpica.org/downloads 1) ACPI CA Core Subsystem: Fixed a problem where an Operation Region _REG method could be executed more than once. If a custom address space handler is installed by the host before the "initialize operation regions" phase of the ACPICA initialization, any _REG methods for that address space could be executed twice. This change fixes the problem. ACPICA BZ 427. Lin Ming. Fixed a possible memory leak for the Scope() ASL operator. When the exact invocation of "Scope(\)" is executed (change scope to root), one internal operand object was leaked. Lin Ming. Implemented a run-time repair for the _MAT predefined method. If the _MAT return value is defined as a Field object in the AML, and the field size is less than or equal to the default width of an integer (32 or 64),_MAT can incorrectly return an Integer instead of a Buffer. ACPICA now automatically repairs this problem. ACPICA BZ 810. Implemented a run-time repair for the _BIF and _BIX predefined methods. The "OEM Information" field is often incorrectly returned as an Integer with value zero if the field is not supported by the platform. This is due to an ambiguity in the ACPI specification. The field should always be a string. ACPICA now automatically repairs this problem by returning a NULL string within the returned Package. ACPICA BZ 807. Example Code and Data Size: These are the sizes for the OS-independent acpica.lib produced by the Microsoft Visual C++ 6.0 32-bit compiler. The debug version of the code includes the debug output trace mechanism and has a much larger code and data size. Previous Release: Non-Debug Version: 85.6K Code, 18.0K Data, 103.6K Total Debug Version: 161.7K Code, 50.9K Data, 212.6K Total Current Release: Non-Debug Version: 85.8K Code, 18.0K Data, 103.8K Total Debug Version: 161.8K Code, 50.6K Data, 212.4K Total 2) iASL Compiler/Disassembler and Tools: Disassembler: Fixed a problem where references to external symbols that contained one or more parent-prefixes (carats) were not handled correctly, possibly causing a fault. ACPICA BZ 806. Lin Ming. Disassembler: Restructured the code so that all functions that handle external symbols are in a single module. One new file is added, common/dmextern.c. AML Debugger: Added a max count argument for the Batch command (which executes multiple predefined methods within the namespace.) iASL: Updated the compiler documentation (User Reference.) Available at http://www.acpica.org/documentation/. ACPICA BZ 750. AcpiXtract: Updated for Lint and other formatting changes. Close all open files. From lstewart at freebsd.org Tue Oct 13 22:08:13 2009 From: lstewart at freebsd.org (Lawrence Stewart) Date: Tue Oct 13 22:08:19 2009 Subject: ACPI Warning: Converted Buffer to expected String In-Reply-To: <200910131133.16487.jkim@FreeBSD.org> References: <20091011142256.GA3770@roadrunner.spoerlein.net> <200910131133.16487.jkim@FreeBSD.org> Message-ID: <4AD4F611.6080504@freebsd.org> Jung-uk Kim wrote: [snip] > by new ACPICA. However, if you see "ACPI Error", that's something to > worry about, e.g., cannot convert predefined types. > So I should be worried about this line from my Toshiba R600 laptop's dmesg? ACPI Error: Package List length (0xC) larger than NumElements count (0x4), truncated Cheers, Lawrence From jkim at FreeBSD.org Tue Oct 13 22:16:13 2009 From: jkim at FreeBSD.org (Jung-uk Kim) Date: Tue Oct 13 22:16:25 2009 Subject: ACPI Warning: Converted Buffer to expected String In-Reply-To: <4AD4F611.6080504@freebsd.org> References: <20091011142256.GA3770@roadrunner.spoerlein.net> <200910131133.16487.jkim@FreeBSD.org> <4AD4F611.6080504@freebsd.org> Message-ID: <200910131815.53053.jkim@FreeBSD.org> On Tuesday 13 October 2009 05:50 pm, Lawrence Stewart wrote: > Jung-uk Kim wrote: > > [snip] > > > by new ACPICA. However, if you see "ACPI Error", that's > > something to worry about, e.g., cannot convert predefined types. > > So I should be worried about this line from my Toshiba R600 > laptop's dmesg? > > ACPI Error: Package List length (0xC) larger than NumElements count > (0x4), truncated Strictly speaking, it is an error because ACPI specification says so (hence the error message). However, no exception is returned because of Windows compatibility according to the comments in the source. If everything is working fine, just ignore it. :-) Jung-uk Kim From robert.moore at intel.com Tue Oct 13 22:21:37 2009 From: robert.moore at intel.com (Moore, Robert) Date: Tue Oct 13 22:21:43 2009 Subject: ACPI Warning: Converted Buffer to expected String In-Reply-To: <200910131815.53053.jkim@FreeBSD.org> References: <20091011142256.GA3770@roadrunner.spoerlein.net> <200910131133.16487.jkim@FreeBSD.org> <4AD4F611.6080504@freebsd.org> <200910131815.53053.jkim@FreeBSD.org> Message-ID: <4911F71203A09E4D9981D27F9D8308583B31B180@orsmsx503.amr.corp.intel.com> Probably should be dropped down to a warning. This is usually caused by the BIOS modifying the package length on the fly. No ASL compiler would do this. >-----Original Message----- >From: owner-freebsd-acpi@freebsd.org [mailto:owner-freebsd- >acpi@freebsd.org] On Behalf Of Jung-uk Kim >Sent: Tuesday, October 13, 2009 3:16 PM >To: freebsd-current@FreeBSD.org >Cc: Lawrence Stewart; freebsd-acpi@freebsd.org >Subject: Re: ACPI Warning: Converted Buffer to expected String > >On Tuesday 13 October 2009 05:50 pm, Lawrence Stewart wrote: >> Jung-uk Kim wrote: >> >> [snip] >> >> > by new ACPICA. However, if you see "ACPI Error", that's >> > something to worry about, e.g., cannot convert predefined types. >> >> So I should be worried about this line from my Toshiba R600 >> laptop's dmesg? >> >> ACPI Error: Package List length (0xC) larger than NumElements count >> (0x4), truncated > >Strictly speaking, it is an error because ACPI specification says so >(hence the error message). However, no exception is returned because >of Windows compatibility according to the comments in the source. > >If everything is working fine, just ignore it. :-) > >Jung-uk Kim >_______________________________________________ >freebsd-acpi@freebsd.org mailing list >http://lists.freebsd.org/mailman/listinfo/freebsd-acpi >To unsubscribe, send any mail to "freebsd-acpi-unsubscribe@freebsd.org" From lstewart at freebsd.org Tue Oct 13 23:43:05 2009 From: lstewart at freebsd.org (Lawrence Stewart) Date: Tue Oct 13 23:43:17 2009 Subject: ACPI Warning: Converted Buffer to expected String In-Reply-To: <200910131815.53053.jkim@FreeBSD.org> References: <20091011142256.GA3770@roadrunner.spoerlein.net> <200910131133.16487.jkim@FreeBSD.org> <4AD4F611.6080504@freebsd.org> <200910131815.53053.jkim@FreeBSD.org> Message-ID: <4AD51077.1030603@freebsd.org> Jung-uk Kim wrote: > On Tuesday 13 October 2009 05:50 pm, Lawrence Stewart wrote: >> Jung-uk Kim wrote: >> >> [snip] >> >>> by new ACPICA. However, if you see "ACPI Error", that's >>> something to worry about, e.g., cannot convert predefined types. >> So I should be worried about this line from my Toshiba R600 >> laptop's dmesg? >> >> ACPI Error: Package List length (0xC) larger than NumElements count >> (0x4), truncated > > Strictly speaking, it is an error because ACPI specification says so > (hence the error message). However, no exception is returned because > of Windows compatibility according to the comments in the source. > Ok thanks for explaining. > If everything is working fine, just ignore it. :-) When I boot this particular laptop into windows and then back into FreeBSD (even after a power down in between), I get a reproducible panic while the kernel is booting and probing devices which can only be fixed by going into the BIOS config screen and restoring to defaults. I suspect the Windows drivers are leaving the hardware in some fancy state the FreeBSD kernel doesn't like. I have a hunch it is ACPI related. Is there some way I can tell? The panic/backtrace is always the same as follows: Slab at 0xffffff00025d5b18, freei 3 = 0. panic: Duplicate free of item 0xffffff00025f8c00 from zone 0xffffff00b697d400(1024) Backtrace at the ddb prompt looks like this: db> bt kdb_enter()+0x3d panic()+0x17b uma_dbg_free()+0x171 uma_zfree_arg()+0x68 free()+0xbd device_set_driver()+0x8e device_attach()+0x19b bus_generic_attach()+0x1a acpi_pci_attach()+0x147 device_attach()+0x69 bus_generic_attach()+0x1a acpi_pcib_attach()+0x1a7 acpi_pcib_acpi_attach()+0x1a5 device_attach()+0x69 bus_generic_attach()+0x1a acpi_attach()+0x9e4 device_attach()+0x69 bus_generic_attach()+0x1a device_attach()+0x69 root_bus_configure()+0x28 configure()+0xa mi_startup()+0x59 btext()+0x2c Cheers, Lawrence From avg at icyb.net.ua Wed Oct 14 17:12:33 2009 From: avg at icyb.net.ua (Andriy Gapon) Date: Wed Oct 14 17:12:48 2009 Subject: heci: a new driver for review and testing Message-ID: <4AD6067E.2010503@icyb.net.ua> Some time ago I posted some ideas about HECI/MEI driver for FreeBSD: http://docs.freebsd.org/cgi/mid.cgi?4968E9A1.3080006 I actually got around to implementing it (in initial/basic form): http://people.freebsd.org/~avg/heci.tgz Other drivers are: [Linux] http://www.openamt.org/ [OpenSolaris] http://src.opensolaris.org/source/xref/onnv/onnv-gate/usr/src/uts/intel/io/heci/ An example of what functionality this driver could provide: http://article.gmane.org/gmane.linux.drivers.sensors/20398 This actually was my primary motivation for looking into this driver. Your hardware may be supported by this driver if pciconf -lv has something like the following: none0@pci0:0:3:0: class=0x078000 card=0x50448086 chip=0x29c48086 rev=0x02 hdr=0x00 vendor = 'Intel Corporation' device = '(Bearlake) HECI Controller' class = simple comms Here's how successful attachment of this driver looks on my system: heci0: mem 0xe0426100-0xe042610f irq 16 at device 3.0 on pci0 heci0: using MSI heci0: [ITHREAD] heci0: found ME client at address 0x03: heci0: status = 0x00 heci0: protocol_name(guid) = A12FF5CA-FACB-4CB4-A958-19A23B2E6881 heci0: found ME client at address 0x07: heci0: status = 0x00 heci0: protocol_name(guid) = 55213584-9A29-4916-BADF-0FB7ED682AEB heci0: found ME client at address 0x20: heci0: status = 0x00 heci0: protocol_name(guid) = 309DCDE8-CCB1-4062-8F78-600115A34327 heci0: found ME client at address 0x21: heci0: status = 0x00 heci0: protocol_name(guid) = 6B5205B9-8185-4519-B889-D98724B58607 The driver has many functional and programming shortcomings, but I still would like to ask for its review and testing. Please read the following warnings and notices: 1. right now the driver is provided only as a module. 2. the driver recognizes only PCI ID of 0x29c48086, which is what I tested it with; please see hecireg.h for a list of potentially supported IDs and add your ID to heci_probe(). 3. heciio.h does not get installed into /usr/include, so for time being you need to take an extra step to make it available to code that wishes to communicate to heci. 4. this driver has far less capabilities than Linux and OpenSolaris drivers, so don't expect every OpenAMT program to work with it (but it does reliably work for me for the QST thing). Now more details about the code: 1. the code contains some style violations like overly long lines, probably others; but I still would like to hear your comments on its style. 2. there are some bad design decisions like using the same mutex+condvar pair for signaling different events (reception of data from ME, emptying of user buffer); but I still would like to hear your comments about improving the design. 3. only a single connection is allowed for a host client 4. only a single connection is allowed to a ME client (if the client can support more). 5. quite an arbitrary timeout is used in all places where we wait for simething to happen. 6. no power management supported. 7. only messages of size less than 512 bytes are supported. 8. only complete messages are supported, multi-part messages are not. 9. userland is expected to read or write the whole message in one go. 10. poll/select functionality is not tested. 11. non-blocking reads/writes are not supported. 12. some (probably important) properties and statuses of ME clients are not interpreted. 13. no specific support for watchdog and PTHI, only simple HECI/MEI communications. 14. probably many more... I think that ultimately, if complete feature support is needed, it would be easier to port the driver from either OpenSolaris or Linux than to add all the features to the presented driver. This is because documentation/description for many features is severely lacking in public access. I guess that Intel developers that worked on the OpenAMT driver had much more detailed specifications to work with. But reverse-engineering some parts of OpenAMT code is very hard. You can see for yourself, if not for the hacker who decompiled a Windows DLL, there would be no way of obtaining even GUID of QST client from public sources. Thank you very much in advance for any feedback, comments, ideas! P.S. BTW, can/may I drop "alternatively GPL" wording from License block of the files I borrowed from Intel? I.e. can a dual BSD+GPL licensed file be turned into BSD-only? Some additional info. The files contain only some data structure/constants definitions. I guess those are not copyrightable at all? I added a bunch of comments to those file describing the constants and structs. -- Andriy Gapon From rnoland at FreeBSD.org Wed Oct 14 21:25:41 2009 From: rnoland at FreeBSD.org (Robert Noland) Date: Wed Oct 14 21:25:49 2009 Subject: heci: a new driver for review and testing In-Reply-To: <4AD6067E.2010503@icyb.net.ua> References: <4AD6067E.2010503@icyb.net.ua> Message-ID: <1255555532.95374.147.camel@balrog.2hip.net> On Wed, 2009-10-14 at 20:12 +0300, Andriy Gapon wrote: > Some time ago I posted some ideas about HECI/MEI driver for FreeBSD: > http://docs.freebsd.org/cgi/mid.cgi?4968E9A1.3080006 > > I actually got around to implementing it (in initial/basic form): > http://people.freebsd.org/~avg/heci.tgz Your getting a WITNESS warning from malloc() while holding a lock at like 941 of heci.c mec = (struct me_client *)malloc(sizeof(*mec), M_HECI, M_NOWAIT | M_ZERO); fixes it. It also locked up the machine when I tried to kldunload, but haven't identified a root cause of that. robert. > Other drivers are: > [Linux] http://www.openamt.org/ > [OpenSolaris] > http://src.opensolaris.org/source/xref/onnv/onnv-gate/usr/src/uts/intel/io/heci/ > > An example of what functionality this driver could provide: > http://article.gmane.org/gmane.linux.drivers.sensors/20398 > This actually was my primary motivation for looking into this driver. > > Your hardware may be supported by this driver if pciconf -lv has something like > the following: > none0@pci0:0:3:0: class=0x078000 card=0x50448086 chip=0x29c48086 rev=0x02 > hdr=0x00 > vendor = 'Intel Corporation' > device = '(Bearlake) HECI Controller' > class = simple comms > > Here's how successful attachment of this driver looks on my system: > heci0: mem > 0xe0426100-0xe042610f irq 16 at device 3.0 on pci0 > heci0: using MSI > heci0: [ITHREAD] > heci0: found ME client at address 0x03: > heci0: status = 0x00 > heci0: protocol_name(guid) = A12FF5CA-FACB-4CB4-A958-19A23B2E6881 > heci0: found ME client at address 0x07: > heci0: status = 0x00 > heci0: protocol_name(guid) = 55213584-9A29-4916-BADF-0FB7ED682AEB > heci0: found ME client at address 0x20: > heci0: status = 0x00 > heci0: protocol_name(guid) = 309DCDE8-CCB1-4062-8F78-600115A34327 > heci0: found ME client at address 0x21: > heci0: status = 0x00 > heci0: protocol_name(guid) = 6B5205B9-8185-4519-B889-D98724B58607 > > The driver has many functional and programming shortcomings, but I still would > like to ask for its review and testing. > Please read the following warnings and notices: > 1. right now the driver is provided only as a module. > 2. the driver recognizes only PCI ID of 0x29c48086, which is what I tested it > with; please see hecireg.h for a list of potentially supported IDs and add your ID > to heci_probe(). > 3. heciio.h does not get installed into /usr/include, so for time being you need > to take an extra step to make it available to code that wishes to communicate to heci. > 4. this driver has far less capabilities than Linux and OpenSolaris drivers, so > don't expect every OpenAMT program to work with it (but it does reliably work for > me for the QST thing). > > Now more details about the code: > 1. the code contains some style violations like overly long lines, probably > others; but I still would like to hear your comments on its style. > 2. there are some bad design decisions like using the same mutex+condvar pair for > signaling different events (reception of data from ME, emptying of user buffer); > but I still would like to hear your comments about improving the design. > 3. only a single connection is allowed for a host client > 4. only a single connection is allowed to a ME client (if the client can support > more). > 5. quite an arbitrary timeout is used in all places where we wait for simething to > happen. > 6. no power management supported. > 7. only messages of size less than 512 bytes are supported. > 8. only complete messages are supported, multi-part messages are not. > 9. userland is expected to read or write the whole message in one go. > 10. poll/select functionality is not tested. > 11. non-blocking reads/writes are not supported. > 12. some (probably important) properties and statuses of ME clients are not > interpreted. > 13. no specific support for watchdog and PTHI, only simple HECI/MEI communications. > 14. probably many more... > > I think that ultimately, if complete feature support is needed, it would be easier > to port the driver from either OpenSolaris or Linux than to add all the features > to the presented driver. This is because documentation/description for many > features is severely lacking in public access. I guess that Intel developers that > worked on the OpenAMT driver had much more detailed specifications to work with. > But reverse-engineering some parts of OpenAMT code is very hard. > You can see for yourself, if not for the hacker who decompiled a Windows DLL, > there would be no way of obtaining even GUID of QST client from public sources. > > Thank you very much in advance for any feedback, comments, ideas! > > P.S. > BTW, can/may I drop "alternatively GPL" wording from License block of the files I > borrowed from Intel? I.e. can a dual BSD+GPL licensed file be turned into BSD-only? > Some additional info. The files contain only some data structure/constants > definitions. I guess those are not copyrightable at all? I added a bunch of > comments to those file describing the constants and structs. > -- Robert Noland FreeBSD From unixmania at gmail.com Wed Oct 14 23:14:42 2009 From: unixmania at gmail.com (Carlos A. M. dos Santos) Date: Wed Oct 14 23:15:06 2009 Subject: heci: a new driver for review and testing In-Reply-To: <4AD6067E.2010503@icyb.net.ua> References: <4AD6067E.2010503@icyb.net.ua> Message-ID: On Wed, Oct 14, 2009 at 2:12 PM, Andriy Gapon wrote: > BTW, can/may I drop "alternatively GPL" wording from License block of the files I > borrowed from Intel? I.e. can a dual BSD+GPL licensed file be turned into BSD-only? If Intel is the copyright owner then you can not change the license without their permission. -- My preferred quotation of Robert Louis Stevenson is "You cannot make an omelette without breaking eggs". Not because I like the omelettes, but because I like the sound of eggs being broken. From rnoland at FreeBSD.org Wed Oct 14 23:36:09 2009 From: rnoland at FreeBSD.org (Robert Noland) Date: Wed Oct 14 23:36:22 2009 Subject: heci: a new driver for review and testing In-Reply-To: <4AD6067E.2010503@icyb.net.ua> References: <4AD6067E.2010503@icyb.net.ua> Message-ID: <1255556129.95374.160.camel@balrog.2hip.net> On Wed, 2009-10-14 at 20:12 +0300, Andriy Gapon wrote: > Some time ago I posted some ideas about HECI/MEI driver for FreeBSD: > http://docs.freebsd.org/cgi/mid.cgi?4968E9A1.3080006 > > I actually got around to implementing it (in initial/basic form): > http://people.freebsd.org/~avg/heci.tgz > > Other drivers are: > [Linux] http://www.openamt.org/ > [OpenSolaris] > http://src.opensolaris.org/source/xref/onnv/onnv-gate/usr/src/uts/intel/io/heci/ > > An example of what functionality this driver could provide: > http://article.gmane.org/gmane.linux.drivers.sensors/20398 > This actually was my primary motivation for looking into this driver. Could you also post the client code in some form more readily accessible than trying to cut/paste from the web page? robert. > Your hardware may be supported by this driver if pciconf -lv has something like > the following: > none0@pci0:0:3:0: class=0x078000 card=0x50448086 chip=0x29c48086 rev=0x02 > hdr=0x00 > vendor = 'Intel Corporation' > device = '(Bearlake) HECI Controller' > class = simple comms > > Here's how successful attachment of this driver looks on my system: > heci0: mem > 0xe0426100-0xe042610f irq 16 at device 3.0 on pci0 > heci0: using MSI > heci0: [ITHREAD] > heci0: found ME client at address 0x03: > heci0: status = 0x00 > heci0: protocol_name(guid) = A12FF5CA-FACB-4CB4-A958-19A23B2E6881 > heci0: found ME client at address 0x07: > heci0: status = 0x00 > heci0: protocol_name(guid) = 55213584-9A29-4916-BADF-0FB7ED682AEB > heci0: found ME client at address 0x20: > heci0: status = 0x00 > heci0: protocol_name(guid) = 309DCDE8-CCB1-4062-8F78-600115A34327 > heci0: found ME client at address 0x21: > heci0: status = 0x00 > heci0: protocol_name(guid) = 6B5205B9-8185-4519-B889-D98724B58607 > > The driver has many functional and programming shortcomings, but I still would > like to ask for its review and testing. > Please read the following warnings and notices: > 1. right now the driver is provided only as a module. > 2. the driver recognizes only PCI ID of 0x29c48086, which is what I tested it > with; please see hecireg.h for a list of potentially supported IDs and add your ID > to heci_probe(). > 3. heciio.h does not get installed into /usr/include, so for time being you need > to take an extra step to make it available to code that wishes to communicate to heci. > 4. this driver has far less capabilities than Linux and OpenSolaris drivers, so > don't expect every OpenAMT program to work with it (but it does reliably work for > me for the QST thing). > > Now more details about the code: > 1. the code contains some style violations like overly long lines, probably > others; but I still would like to hear your comments on its style. > 2. there are some bad design decisions like using the same mutex+condvar pair for > signaling different events (reception of data from ME, emptying of user buffer); > but I still would like to hear your comments about improving the design. > 3. only a single connection is allowed for a host client > 4. only a single connection is allowed to a ME client (if the client can support > more). > 5. quite an arbitrary timeout is used in all places where we wait for simething to > happen. > 6. no power management supported. > 7. only messages of size less than 512 bytes are supported. > 8. only complete messages are supported, multi-part messages are not. > 9. userland is expected to read or write the whole message in one go. > 10. poll/select functionality is not tested. > 11. non-blocking reads/writes are not supported. > 12. some (probably important) properties and statuses of ME clients are not > interpreted. > 13. no specific support for watchdog and PTHI, only simple HECI/MEI communications. > 14. probably many more... > > I think that ultimately, if complete feature support is needed, it would be easier > to port the driver from either OpenSolaris or Linux than to add all the features > to the presented driver. This is because documentation/description for many > features is severely lacking in public access. I guess that Intel developers that > worked on the OpenAMT driver had much more detailed specifications to work with. > But reverse-engineering some parts of OpenAMT code is very hard. > You can see for yourself, if not for the hacker who decompiled a Windows DLL, > there would be no way of obtaining even GUID of QST client from public sources. > > Thank you very much in advance for any feedback, comments, ideas! > > P.S. > BTW, can/may I drop "alternatively GPL" wording from License block of the files I > borrowed from Intel? I.e. can a dual BSD+GPL licensed file be turned into BSD-only? > Some additional info. The files contain only some data structure/constants > definitions. I guess those are not copyrightable at all? I added a bunch of > comments to those file describing the constants and structs. > -- Robert Noland FreeBSD From avg at icyb.net.ua Thu Oct 15 05:23:54 2009 From: avg at icyb.net.ua (Andriy Gapon) Date: Thu Oct 15 05:24:01 2009 Subject: heci: a new driver for review and testing In-Reply-To: <1255555532.95374.147.camel@balrog.2hip.net> References: <4AD6067E.2010503@icyb.net.ua> <1255555532.95374.147.camel@balrog.2hip.net> Message-ID: <4AD6B1D5.3010003@icyb.net.ua> on 15/10/2009 00:25 Robert Noland said the following: > On Wed, 2009-10-14 at 20:12 +0300, Andriy Gapon wrote: >> Some time ago I posted some ideas about HECI/MEI driver for FreeBSD: >> http://docs.freebsd.org/cgi/mid.cgi?4968E9A1.3080006 >> >> I actually got around to implementing it (in initial/basic form): >> http://people.freebsd.org/~avg/heci.tgz > > Your getting a WITNESS warning from malloc() while holding a lock at > like 941 of heci.c > > mec = (struct me_client *)malloc(sizeof(*mec), M_HECI, > M_NOWAIT | M_ZERO); > > fixes it. Shame on me! I have to admit that tested/used this module only on stable/7 (amd64) and without WITNESS/INVARIANTS. Thank you for catching this. I guess I should also add a check for malloc returning NULL. > It also locked up the machine when I tried to kldunload, but > haven't identified a root cause of that. Haven't seen it here. I will try to investigate. -- Andriy Gapon From avg at icyb.net.ua Thu Oct 15 05:26:31 2009 From: avg at icyb.net.ua (Andriy Gapon) Date: Thu Oct 15 05:27:30 2009 Subject: heci: a new driver for review and testing In-Reply-To: <1255556129.95374.160.camel@balrog.2hip.net> References: <4AD6067E.2010503@icyb.net.ua> <1255556129.95374.160.camel@balrog.2hip.net> Message-ID: <4AD6B274.5050906@icyb.net.ua> on 15/10/2009 00:35 Robert Noland said the following: > On Wed, 2009-10-14 at 20:12 +0300, Andriy Gapon wrote: >> Some time ago I posted some ideas about HECI/MEI driver for FreeBSD: >> http://docs.freebsd.org/cgi/mid.cgi?4968E9A1.3080006 >> >> I actually got around to implementing it (in initial/basic form): >> http://people.freebsd.org/~avg/heci.tgz >> >> Other drivers are: >> [Linux] http://www.openamt.org/ >> [OpenSolaris] >> http://src.opensolaris.org/source/xref/onnv/onnv-gate/usr/src/uts/intel/io/heci/ >> >> An example of what functionality this driver could provide: >> http://article.gmane.org/gmane.linux.drivers.sensors/20398 >> This actually was my primary motivation for looking into this driver. > > Could you also post the client code in some form more readily accessible > than trying to cut/paste from the web page? > > robert. Sure: http://people.freebsd.org/~avg/heci-qst.c Sorry for not doing this from the very start. -- Andriy Gapon From des at des.no Thu Oct 15 10:41:07 2009 From: des at des.no (=?utf-8?Q?Dag-Erling_Sm=C3=B8rgrav?=) Date: Thu Oct 15 10:41:14 2009 Subject: heci: a new driver for review and testing In-Reply-To: <4AD6067E.2010503@icyb.net.ua> (Andriy Gapon's message of "Wed, 14 Oct 2009 20:12:30 +0300") References: <4AD6067E.2010503@icyb.net.ua> Message-ID: <86iqehx8bf.fsf@ds4.des.no> Andriy Gapon writes: > BTW, can / may I drop "alternatively GPL" wording from License block > of the files I borrowed from Intel? I.e. can a dual BSD+GPL licensed > file be turned into BSD-only? No. Why would you want to? > Some additional info. The files contain only some data structure / > constants definitions. I guess those are not copyrightable at all? That's debatable. It is probably safe to assume that they aren't *if* they only describe the interface to another piece of software or to the hardware, but if they represent internal data structures used by the Linux driver, they are definitely copyrightable. DES -- Dag-Erling Sm?rgrav - des@des.no From rnoland at FreeBSD.org Thu Oct 15 14:17:04 2009 From: rnoland at FreeBSD.org (Robert Noland) Date: Thu Oct 15 14:17:15 2009 Subject: heci: a new driver for review and testing In-Reply-To: <4AD6B1D5.3010003@icyb.net.ua> References: <4AD6067E.2010503@icyb.net.ua> <1255555532.95374.147.camel@balrog.2hip.net> <4AD6B1D5.3010003@icyb.net.ua> Message-ID: <1255616214.2356.872.camel@balrog.2hip.net> On Thu, 2009-10-15 at 08:23 +0300, Andriy Gapon wrote: > on 15/10/2009 00:25 Robert Noland said the following: > > On Wed, 2009-10-14 at 20:12 +0300, Andriy Gapon wrote: > >> Some time ago I posted some ideas about HECI/MEI driver for FreeBSD: > >> http://docs.freebsd.org/cgi/mid.cgi?4968E9A1.3080006 > >> > >> I actually got around to implementing it (in initial/basic form): > >> http://people.freebsd.org/~avg/heci.tgz > > > > Your getting a WITNESS warning from malloc() while holding a lock at > > like 941 of heci.c > > > > mec = (struct me_client *)malloc(sizeof(*mec), M_HECI, > > M_NOWAIT | M_ZERO); > > > > fixes it. > > Shame on me! > I have to admit that tested/used this module only on stable/7 (amd64) and > without WITNESS/INVARIANTS. > Thank you for catching this. > I guess I should also add a check for malloc returning NULL. Yes, with M_NOWAIT you should. Here is the dmesg output. heci0: mem 0xd0526100-0xd052610f irq 16 at device 3.0 on pci0 heci0: using MSI heci0: [ITHREAD] heci0: found ME client at address 0x02: heci0: status = 0x00 heci0: protocol_name(guid) = BB875E12-CB58-4D14-AE93-8566183C66C7 heci0: found ME client at address 0x03: heci0: status = 0x00 heci0: protocol_name(guid) = A12FF5CA-FACB-4CB4-A958-19A23B2E6881 heci0: found ME client at address 0x06: heci0: status = 0x00 heci0: protocol_name(guid) = 9B27FD6D-EF72-4967-BCC2-471A32679620 heci0: found ME client at address 0x07: heci0: status = 0x00 heci0: protocol_name(guid) = 55213584-9A29-4916-BADF-0FB7ED682AEB heci0: found ME client at address 0x20: heci0: status = 0x00 heci0: protocol_name(guid) = 23F27E9B-9D26-4FCE-9227-DE06446E5B06 heci0: found ME client at address 0x21: heci0: status = 0x00 heci0: protocol_name(guid) = 309DCDE8-CCB1-4062-8F78-600115A34327 heci0: found ME client at address 0x22: heci0: status = 0x00 heci0: protocol_name(guid) = 6B5205B9-8185-4519-B889-D98724B58607 heci0: found ME client at address 0x23: heci0: status = 0x00 heci0: protocol_name(guid) = 9D9105BD-C8C6-41CA-AC28-84738E2CE9FD heci0: found ME client at address 0x24: heci0: status = 0x00 heci0: protocol_name(guid) = DC506909-7ADB-4A0D-B109-4E25E38C382C heci0: found ME client at address 0x25: heci0: status = 0x00 heci0: protocol_name(guid) = 6733A4DB-0476-4E7B-B3AF-BCFC29BEE7A7 heci0: found ME client at address 0x26: heci0: status = 0x00 heci0: protocol_name(guid) = 12F80028-B4B7-4B2D-ACA8-46E0FF65814C heci0: found ME client at address 0x27: heci0: status = 0x00 heci0: protocol_name(guid) = 05B79A6F-4628-4D7F-899D-A91514CB32AB robert. > > It also locked up the machine when I tried to kldunload, but > > haven't identified a root cause of that. > > Haven't seen it here. > I will try to investigate. > -- Robert Noland FreeBSD From unixmania at gmail.com Thu Oct 15 15:01:51 2009 From: unixmania at gmail.com (Carlos A. M. dos Santos) Date: Thu Oct 15 15:02:03 2009 Subject: heci: a new driver for review and testing In-Reply-To: <20091014203428.7d84bf96@bhuda.mired.org> References: <4AD6067E.2010503@icyb.net.ua> <20091014203428.7d84bf96@bhuda.mired.org> Message-ID: On Wed, Oct 14, 2009 at 9:34 PM, Mike Meyer wrote: > On Wed, 14 Oct 2009 19:46:20 -0300 > "Carlos A. M. dos Santos" wrote: > >> On Wed, Oct 14, 2009 at 2:12 PM, Andriy Gapon wrote: >> >> > BTW, can/may I drop "alternatively GPL" wording from License block of the files I >> > borrowed from Intel? I.e. can a dual BSD+GPL licensed file be turned into BSD-only? >> >> If Intel is the copyright owner then you can not change the license >> without their permission. > > True. But he *has* their permission. They list the requirements for > use and redistribution in the license block in question: > > ?* Redistribution and use in source and binary forms, with or without > ?* modification, are permitted provided that the following conditions > ?* are met: > ?* 1. Redistributions of source code must retain the above copyright > ?* ? ?notice, this list of conditions, and the following disclaimer, > ?* ? ?without modification. > ?* 2. Redistributions in binary form must reproduce at minimum a disclaimer > ?* ? ?substantially similar to the "NO WARRANTY" disclaimer below > ?* ? ?("Disclaimer") and any redistribution must be conditioned upon > ?* ? ?including a substantially similar Disclaimer requirement for further > ?* ? ?binary redistribution. > ?* 3. Neither the names of the above-listed copyright holders nor the names > ?* ? ?of any contributors may be used to endorse or promote products derived > ?* ? ?from this software without specific prior written permission. > > I don't see anything there about retaining the ability to choose an > alternative license. The paragraph in question says that people can > *choose* to distribute it under the GPLv2, not that it *is* being > distributed under the GPLv2. Conversely, I don't see anything there explicitly *allowing* somebody to remove that paragraph so I'd keep it unless I had express clearance from Intel. Making assumptions can be dangerous, especially when dealing with large corporations. That's the main lesson I've learned after several years dealing with such matters. I don't want to make this discussion longer than necessary, so I stop here. -- My preferred quotation of Robert Louis Stevenson is "You cannot make an omelette without breaking eggs". Not because I like the omelettes, but because I like the sound of eggs being broken. From avg at icyb.net.ua Sun Oct 18 20:11:11 2009 From: avg at icyb.net.ua (Andriy Gapon) Date: Sun Oct 18 20:12:04 2009 Subject: SB7xx watchdog: new driver for review and testing Message-ID: <4ADB764C.2010900@icyb.net.ua> Please review and/or test a new driver for watchdog driver included into AMD SB7xx: http://people.freebsd.org/~avg/amdsbwd.tgz I have tested this driver only with SB700 on Gigabyte GA-MA780G-UD3H motherboard. ichwd driver was used as a starting point for this driver. This can be seen from some function names, general code organization and some small code snippets. Many thanks to ichwd authors and maintainers! Right now I have infrastructure only for building this driver as a module. Things for which that I need the most feedback/ideas: 1. If the driver actually works on your hardware and the hardware description. The driver can be tested by loading the driver and doing 'watchdog -t '. Having debug.bootverbose=1 may provide additional useful info. And better to test this from single-user mode with filesystems mounted r/o. 2. Better name for the driver. amdsbwd stands for "AMD S(outh)B(ridge) WatchDog", but this abbreviation could be cryptic to decipher. 3. Proper location for this driver. At least on my system this driver needs resources (I/O ports and MEM range) that are claimed by ACPI, thus I've made it a child of acpi bus. But this driver doesn't have anything else ACPI-ish in it, so I decided that it doesn't belong under acpica/ or acpi_support/. Am I correct about this? Anything else you would like to report or comment or advise to me. Thank you very much for your help. -- Andriy Gapon From avg at freebsd.org Sun Oct 18 20:15:10 2009 From: avg at freebsd.org (Andriy Gapon) Date: Sun Oct 18 20:15:16 2009 Subject: SB7xx watchdog: new driver for review and testing In-Reply-To: <4ADB764C.2010900@icyb.net.ua> References: <4ADB764C.2010900@icyb.net.ua> Message-ID: <4ADB773C.8090600@freebsd.org> on 18/10/2009 23:10 Andriy Gapon said the following: > Please review and/or test a new driver for watchdog driver included into AMD ^^^^^^^^^-hardware Oh, and please note things marked with XXX and TODO in the code. -- Andriy Gapon From bugmaster at FreeBSD.org Mon Oct 19 11:06:47 2009 From: bugmaster at FreeBSD.org (FreeBSD bugmaster) Date: Mon Oct 19 11:07:16 2009 Subject: Current problem reports assigned to freebsd-acpi@FreeBSD.org Message-ID: <200910191106.n9JB6kJ2063345@freefall.freebsd.org> Note: to view an individual PR, use: http://www.freebsd.org/cgi/query-pr.cgi?pr=(number). The following is a listing of current problems submitted by FreeBSD users. These represent problem reports covering all versions including experimental development code and obsolete releases. S Tracker Resp. Description -------------------------------------------------------------------------------- o kern/139088 acpi [acpi] ACPI Exception: AE_AML_INFINITE_LOOP error o amd64/138210 acpi [acpi] acer aspire 5536 ACPI problems (S3, brightness, o bin/137053 acpi [hang] FreeBSD 8.0 BETA2Compaq Mini 700 locks on boot o kern/137042 acpi [acpi] hp laptop's lcd not wakes up after suspend to r o kern/136808 acpi [acpi] panic when switching to s3 o i386/136008 acpi [acpi] Dell Vostro 1310 will not shutdown (Requires us o bin/135349 acpi [patch] teach acpidump(8) to disassemble arbitrary mem o kern/135070 acpi [acpi] [patch] BIOS resource allocation and FreeBSD AC o kern/132602 acpi [acpi] ACPI Problem with Intel SS4200: System does not o kern/130683 acpi [ACPI] shutdown hangs after syncing disks - ACPI race? o i386/129953 acpi [acpi] ACPI timeout (CDROM) with Shuttle X27D o kern/129618 acpi [acpi] Problem with ACPI on HP Pavilion DV2899 laptop o kern/129563 acpi [acpi] sleep broken on IBM/Lenovo T61 in amd64 mode f kern/128639 acpi [patch] [acpi_asus] acpi for ASUS A6F,A3E,A3F,A3N not f kern/128634 acpi [patch] fix acpi_asus(4) in asus a6f laptop o kern/127581 acpi [patch] [acpi_sony] Add support for more Sony features o kern/124744 acpi [acpi] [patch] incorrect _BST result validation for To o kern/124412 acpi [acpi] power off error on Toshiba M40 laptop o kern/123039 acpi [acpi] ACPI AML_BUFFER_LIMIT errors during boot o kern/121504 acpi [patch] Correctly set hw.acpi.osname on certain machin f kern/121454 acpi [pst] Promise SuperTrak SX6000 does not load during bo o amd64/121439 acpi [boot] Installation of FreeBSD 7.0 fails: ACPI problem o kern/121102 acpi [acpi_fujitsu] [patch] update acpi_fujitsu for the P80 o kern/120515 acpi [acpi] [patch] acpi_alloc_wakeup_handler: can't alloc o kern/119356 acpi [acpi]: i386 ACPI wakeup not work due resource exhaust o kern/119200 acpi [acpi] Lid close switch suspends CPU for 1 second on H o kern/118973 acpi [acpi]: Kernel panic with acpi boot o kern/117605 acpi [acpi] [request] add debug.cpufreq.highest o kern/116939 acpi [acpi] PCI-to-PCI misconfigured for bus three and can o i386/114562 acpi [acpi] cardbus is dead after s3 on Thinkpad T43 with a o kern/114165 acpi [acpi] Dell C810 - ACPI problem s kern/112544 acpi [acpi] [patch] Add High Precision Event Timer Driver f o kern/108954 acpi [acpi] 'sleep(1)' sleeps >1 seconds when speedstep (Cx o kern/108695 acpi [acpi]: Fatal trap 9: general protection fault when in o kern/108488 acpi [acpi] ACPI-1304: *** Error: Method execution failed o kern/108017 acpi [acpi]: Acer Aspire 5600 o kern/106924 acpi [acpi] ACPI resume returns g_vfs_done() errors and ker o kern/105537 acpi [acpi] problems in acpi on HP Compaq nc6320 o kern/104625 acpi ACPI on ASUS A8N-32 SLI/ASUS P4P800 does not show ther o kern/102252 acpi acpi thermal does not work on Abit AW8D (intel 975) o kern/97383 acpi Volume buttons on IBM Thinkpad crash system with ACPI s i386/91748 acpi acpi problem on Acer TravelMare 4652LMi (nvidia panic, s kern/91038 acpi [panic] [ata] [acpi] 6.0-RELEASE on Fujitsu Siemens Am s kern/90243 acpi Laptop fan doesn't turn off (ACPI enabled) (Packard Be o i386/83018 acpi [install] Installer will not boot on Asus P4S8X BIOS 1 f kern/81000 acpi [apic] Via 8235 sound card worked great with FreeBSD 5 o i386/79081 acpi ACPI suspend/resume not working on HP nx6110 o kern/76950 acpi ACPI wrongly blacklisted on Micron ClientPro 766Xi sys s kern/73823 acpi [request] acpi / power-on by timer support o i386/72566 acpi ACPI, FreeBSD disables fan on Compaq Armada 1750 o i386/69750 acpi Boot without ACPI failed on ASUS L5 o kern/56024 acpi ACPI suspend drains battery while in S3 o i386/55661 acpi ACPI suspend/resume problem on ARMADA M700 o i386/54756 acpi ACPI suspend/resume problem on CF-W2 laptop 54 problems total. From rpaulo at freebsd.org Mon Oct 19 11:17:27 2009 From: rpaulo at freebsd.org (Rui Paulo) Date: Mon Oct 19 11:17:34 2009 Subject: SB7xx watchdog: new driver for review and testing In-Reply-To: <4ADB764C.2010900@icyb.net.ua> References: <4ADB764C.2010900@icyb.net.ua> Message-ID: <5E0DD277-CAA3-4F01-8561-35CF6C511718@freebsd.org> On 18 Oct 2009, at 21:10, Andriy Gapon wrote: > Please review and/or test a new driver for watchdog driver included > into AMD SB7xx: > http://people.freebsd.org/~avg/amdsbwd.tgz > I have tested this driver only with SB700 on Gigabyte GA-MA780G-UD3H > motherboard. > > ichwd driver was used as a starting point for this driver. This can > be seen from > some function names, general code organization and some small code > snippets. > Many thanks to ichwd authors and maintainers! > > Right now I have infrastructure only for building this driver as a > module. > > Things for which that I need the most feedback/ideas: > 1. If the driver actually works on your hardware and the hardware > description. > The driver can be tested by loading the driver and doing 'watchdog - > t number>'. Having debug.bootverbose=1 may provide additional useful > info. > And better to test this from single-user mode with filesystems > mounted r/o. > > 2. Better name for the driver. amdsbwd stands for "AMD S(outh)B(ridge) > WatchDog", but this abbreviation could be cryptic to decipher. > > 3. Proper location for this driver. > At least on my system this driver needs resources (I/O ports and MEM > range) that > are claimed by ACPI, thus I've made it a child of acpi bus. But this > driver > doesn't have anything else ACPI-ish in it, so I decided that it > doesn't belong > under acpica/ or acpi_support/. Am I correct about this? > > Anything else you would like to report or comment or advise to me. > Thank you very much for your help. The driver looks good in general. A few questions: - Can you make the magic numbers a define ? Where did they come from ? - Are you missing a device_set_desc() call ? - If this is what you want to commit, C++ comments are not allowed per- style Regards, -- Rui Paulo From avg at icyb.net.ua Mon Oct 19 11:23:43 2009 From: avg at icyb.net.ua (Andriy Gapon) Date: Mon Oct 19 11:23:50 2009 Subject: SB7xx watchdog: new driver for review and testing In-Reply-To: <5E0DD277-CAA3-4F01-8561-35CF6C511718@freebsd.org> References: <4ADB764C.2010900@icyb.net.ua> <5E0DD277-CAA3-4F01-8561-35CF6C511718@freebsd.org> Message-ID: <4ADC4C3C.3000007@icyb.net.ua> on 19/10/2009 14:17 Rui Paulo said the following: > On 18 Oct 2009, at 21:10, Andriy Gapon wrote: > >> Please review and/or test a new driver for watchdog driver included >> into AMD SB7xx: >> http://people.freebsd.org/~avg/amdsbwd.tgz >> I have tested this driver only with SB700 on Gigabyte GA-MA780G-UD3H >> motherboard. >> >> ichwd driver was used as a starting point for this driver. This can be >> seen from >> some function names, general code organization and some small code >> snippets. >> Many thanks to ichwd authors and maintainers! >> >> Right now I have infrastructure only for building this driver as a >> module. >> >> Things for which that I need the most feedback/ideas: >> 1. If the driver actually works on your hardware and the hardware >> description. >> The driver can be tested by loading the driver and doing 'watchdog -t >> > number>'. Having debug.bootverbose=1 may provide additional useful info. >> And better to test this from single-user mode with filesystems mounted >> r/o. >> >> 2. Better name for the driver. amdsbwd stands for "AMD S(outh)B(ridge) >> WatchDog", but this abbreviation could be cryptic to decipher. >> >> 3. Proper location for this driver. >> At least on my system this driver needs resources (I/O ports and MEM >> range) that >> are claimed by ACPI, thus I've made it a child of acpi bus. But this >> driver >> doesn't have anything else ACPI-ish in it, so I decided that it >> doesn't belong >> under acpica/ or acpi_support/. Am I correct about this? >> >> Anything else you would like to report or comment or advise to me. >> Thank you very much for your help. > > The driver looks good in general. A few questions: > - Can you make the magic numbers a define ? Where did they come from ? Yes, will do this. The numbers are from register definitions in AMD SB700/710/750 Register Reference Guide: http://developer.amd.com/assets/43009_sb7xx_rrg_pub_1.00.pdf I will add a link to the document too. > - Are you missing a device_set_desc() call ? Yes, I missed this. Thanks! > - If this is what you want to commit, C++ comments are not allowed > per-style Those lines were a result of quick hacking. I will remove them altogether, -- Andriy Gapon From kama at pvp.se Mon Oct 19 11:24:08 2009 From: kama at pvp.se (kama) Date: Mon Oct 19 11:24:14 2009 Subject: FreeBSD 7.2-STABLE boot freeze In-Reply-To: <20091002212626.O37424@ns1.as.pvp.se> References: <20090921140345.H37424@ns1.as.pvp.se> <20090922103150.V37424@ns1.as.pvp.se> <4AB8A95E.3060307@icyb.net.ua> <20090922142526.P37424@ns1.as.pvp.se> <4AB8E082.8050100@icyb.net.ua> <20090922215700.V37424@ns1.as.pvp.se> <4ABA1D1F.3080704@icyb.net.ua> <20090923171004.Q37424@ns1.as.pvp.se> <4ABA457E.3060800@freebsd.org> <20090924141927.Y37424@ns1.as.pvp.se> <20090925110209.E37424@ns1.as.pvp.se> <4ABC894E.7040204@freebsd.org> <20090928092026.B37424@ns1.as.pvp.se> <4AC06ED6.7030402@freebsd.org> <20090928235136.F37424@ns1.as.pvp.se> <20090929085000.B37424@ns1.as.pvp.se> <4AC211AC.1070404@freebsd.org> <20090929204651.G37424@ns1.as.pvp.se> <4AC34952.9010508@freebsd.org> <20090930151542.G37424@ns1.as.pvp.se> <4AC35CC6.1020103@freebsd.org> <20091002132218.P37424@ns1.as.pvp.se> <20091002212626.O37424@ns1.as.pvp.se> Message-ID: <20091019131327.U33520@ns1.as.pvp.se> On Fri, 2 Oct 2009, kama wrote: > > > Do you get this message in all cases? That is, every time you tried? > > > Or only with ACPI_DEBUG defined? > > > > I cant recall. I have tried so many things lately. But I believe I get it > > on a verbose boot without ACPI_DEBUG. > > > > Im currently rebuilding the system to 8.0. > > Just upgrading to 8.0 did not help regarding the freezes. > > I ran into the bge freeze bug too when disabling acpi. > > I then read the acpi-manpage abit more carefully. > > With ACPI_DEBUG and debug.acpi.disabled="timer" in loader.conf and verbose > boot seems to help against the freeze and freezes again if I dont run it > in verbose mode. But thats just after 5 starts. Anyhow its better. > > loader.conf: > debug.acpi.disabled="timer" > debug.acpi.layer="ACPI_ALL_COMPONENTS" > debug.acpi.level="ACPI_LV_VERBOSE,ACPI_LV_VERBOSITY3,ACPI_LV_VERBOSITY1,ACPI_LV_ALL_EXCEPTIONS" > I just wanted to bump this. After the checkout yesterday and installation today I still get these freezes. # cat /boot/loader.conf hw.bge.allow_asf="0" hw.acpi.verbose="1" debug.acpi.max_threads="1" debug.acpi.disabled="timer" debug.acpi.layer="ACPI_ALL_COMPONENTS" debug.acpi.level="ACPI_LV_VERBOSE,ACPI_LV_VERBOSITY3,ACPI_LV_VERBOSITY1,ACPI_LV_ALL_EXCEPTIONS" # With this setup and with an GENERIC kernel I am able to boot if I choose a verbose boot. I dont know why it should work with these. If I only use debug.acpi.disabled="timer" it will freeze. Is there anyway for me to get more info when it exactly freezes. Like having it print out to the screen when it enters and leaves functions or something. Im not to familiar with where to put these and its "quite" a large project for me to start to understand where everything goes. If someone wants to give me patches or specify which files to alter and how I print to the screen during boot I might be able to pinpoint where it freezes and mail in the results. /Bjorn From avg at icyb.net.ua Mon Oct 19 15:41:50 2009 From: avg at icyb.net.ua (Andriy Gapon) Date: Mon Oct 19 15:41:56 2009 Subject: SB7xx watchdog: new driver for review and testing In-Reply-To: <5E0DD277-CAA3-4F01-8561-35CF6C511718@freebsd.org> References: <4ADB764C.2010900@icyb.net.ua> <5E0DD277-CAA3-4F01-8561-35CF6C511718@freebsd.org> Message-ID: <4ADC88BA.10507@icyb.net.ua> I have put updated version of the driver (C file only) here: http://people.freebsd.org/~avg/amdsbwd.c Please let me know how it looks now. Thank you! -- Andriy Gapon From rpaulo at freebsd.org Mon Oct 19 15:47:38 2009 From: rpaulo at freebsd.org (Rui Paulo) Date: Mon Oct 19 15:48:11 2009 Subject: SB7xx watchdog: new driver for review and testing In-Reply-To: <4ADC88BA.10507@icyb.net.ua> References: <4ADB764C.2010900@icyb.net.ua> <5E0DD277-CAA3-4F01-8561-35CF6C511718@freebsd.org> <4ADC88BA.10507@icyb.net.ua> Message-ID: On 19 Oct 2009, at 16:41, Andriy Gapon wrote: > > I have put updated version of the driver (C file only) here: > http://people.freebsd.org/~avg/amdsbwd.c Looks good to me. -- Rui Paulo From avg at icyb.net.ua Mon Oct 19 19:43:57 2009 From: avg at icyb.net.ua (Andriy Gapon) Date: Mon Oct 19 19:44:04 2009 Subject: SB7xx watchdog: new driver for review and testing In-Reply-To: References: <4ADB764C.2010900@icyb.net.ua> <5E0DD277-CAA3-4F01-8561-35CF6C511718@freebsd.org> <4ADC88BA.10507@icyb.net.ua> Message-ID: <4ADCC16A.1080203@icyb.net.ua> on 19/10/2009 18:47 Rui Paulo said the following: > On 19 Oct 2009, at 16:41, Andriy Gapon wrote: > >> >> I have put updated version of the driver (C file only) here: >> http://people.freebsd.org/~avg/amdsbwd.c > > Looks good to me. Thank you for the review and the help! I have now produced a diff against the main tree for full integration of this driver: http://people.freebsd.org/~avg/amdsbwd.diff -- Andriy Gapon From c.r.n.a at wanadoo.fr Sat Oct 24 11:18:57 2009 From: c.r.n.a at wanadoo.fr (Nicolas) Date: Sat Oct 24 11:19:03 2009 Subject: acpi_hp Message-ID: <4AE2D7DC.1080800@wanadoo.fr> Hi, I'm trying to use the acpi_hp but no luck: acpi_wmi0: on acpi0 acpi_hp0: on acpi0 acpi_hp0: WMI device does not provide the HP BIOS GUID device_attach: acpi_hp0 attach returned 22 What's the problem with my computer ? I need this driver to switch on my wireless card. Thanks in advance, Nicolas. From rpaulo at freebsd.org Sat Oct 24 11:28:34 2009 From: rpaulo at freebsd.org (Rui Paulo) Date: Sat Oct 24 11:28:41 2009 Subject: acpi_hp In-Reply-To: <4AE2D7DC.1080800@wanadoo.fr> References: <4AE2D7DC.1080800@wanadoo.fr> Message-ID: On 24 Oct 2009, at 11:33, Nicolas wrote: > Hi, > > I'm trying to use the acpi_hp but no luck: > > acpi_wmi0: on acpi0 > acpi_hp0: on acpi0 > acpi_hp0: WMI device does not provide the HP BIOS GUID > device_attach: acpi_hp0 attach returned 22 > > What's the problem with my computer ? > I need this driver to switch on my wireless card. Try asking Michael (CC'ed). Regards, -- Rui Paulo From bugmaster at FreeBSD.org Mon Oct 26 11:06:53 2009 From: bugmaster at FreeBSD.org (FreeBSD bugmaster) Date: Mon Oct 26 11:07:13 2009 Subject: Current problem reports assigned to freebsd-acpi@FreeBSD.org Message-ID: <200910261106.n9QB6qdq043662@freefall.freebsd.org> Note: to view an individual PR, use: http://www.freebsd.org/cgi/query-pr.cgi?pr=(number). The following is a listing of current problems submitted by FreeBSD users. These represent problem reports covering all versions including experimental development code and obsolete releases. S Tracker Resp. Description -------------------------------------------------------------------------------- o kern/139088 acpi [acpi] ACPI Exception: AE_AML_INFINITE_LOOP error o amd64/138210 acpi [acpi] acer aspire 5536 ACPI problems (S3, brightness, o bin/137053 acpi [hang] FreeBSD 8.0 BETA2Compaq Mini 700 locks on boot o kern/137042 acpi [acpi] hp laptop's lcd not wakes up after suspend to r o kern/136808 acpi [acpi] panic when switching to s3 o i386/136008 acpi [acpi] Dell Vostro 1310 will not shutdown (Requires us o bin/135349 acpi [patch] teach acpidump(8) to disassemble arbitrary mem o kern/135070 acpi [acpi] [patch] BIOS resource allocation and FreeBSD AC o kern/132602 acpi [acpi] ACPI Problem with Intel SS4200: System does not o kern/130683 acpi [ACPI] shutdown hangs after syncing disks - ACPI race? o i386/129953 acpi [acpi] ACPI timeout (CDROM) with Shuttle X27D o kern/129618 acpi [acpi] Problem with ACPI on HP Pavilion DV2899 laptop o kern/129563 acpi [acpi] sleep broken on IBM/Lenovo T61 in amd64 mode f kern/128639 acpi [patch] [acpi_asus] acpi for ASUS A6F,A3E,A3F,A3N not f kern/128634 acpi [patch] fix acpi_asus(4) in asus a6f laptop o kern/127581 acpi [patch] [acpi_sony] Add support for more Sony features o kern/124744 acpi [acpi] [patch] incorrect _BST result validation for To o kern/124412 acpi [acpi] power off error on Toshiba M40 laptop o kern/123039 acpi [acpi] ACPI AML_BUFFER_LIMIT errors during boot o kern/121504 acpi [patch] Correctly set hw.acpi.osname on certain machin f kern/121454 acpi [pst] Promise SuperTrak SX6000 does not load during bo o amd64/121439 acpi [boot] Installation of FreeBSD 7.0 fails: ACPI problem o kern/121102 acpi [acpi_fujitsu] [patch] update acpi_fujitsu for the P80 o kern/120515 acpi [acpi] [patch] acpi_alloc_wakeup_handler: can't alloc o kern/119356 acpi [acpi]: i386 ACPI wakeup not work due resource exhaust o kern/119200 acpi [acpi] Lid close switch suspends CPU for 1 second on H o kern/118973 acpi [acpi]: Kernel panic with acpi boot o kern/117605 acpi [acpi] [request] add debug.cpufreq.highest o kern/116939 acpi [acpi] PCI-to-PCI misconfigured for bus three and can o i386/114562 acpi [acpi] cardbus is dead after s3 on Thinkpad T43 with a o kern/114165 acpi [acpi] Dell C810 - ACPI problem s kern/112544 acpi [acpi] [patch] Add High Precision Event Timer Driver f o kern/108954 acpi [acpi] 'sleep(1)' sleeps >1 seconds when speedstep (Cx o kern/108695 acpi [acpi]: Fatal trap 9: general protection fault when in o kern/108488 acpi [acpi] ACPI-1304: *** Error: Method execution failed o kern/108017 acpi [acpi]: Acer Aspire 5600 o kern/106924 acpi [acpi] ACPI resume returns g_vfs_done() errors and ker o kern/105537 acpi [acpi] problems in acpi on HP Compaq nc6320 o kern/104625 acpi ACPI on ASUS A8N-32 SLI/ASUS P4P800 does not show ther o kern/102252 acpi acpi thermal does not work on Abit AW8D (intel 975) o kern/97383 acpi Volume buttons on IBM Thinkpad crash system with ACPI s i386/91748 acpi acpi problem on Acer TravelMare 4652LMi (nvidia panic, s kern/91038 acpi [panic] [ata] [acpi] 6.0-RELEASE on Fujitsu Siemens Am s kern/90243 acpi Laptop fan doesn't turn off (ACPI enabled) (Packard Be o i386/83018 acpi [install] Installer will not boot on Asus P4S8X BIOS 1 f kern/81000 acpi [apic] Via 8235 sound card worked great with FreeBSD 5 o i386/79081 acpi ACPI suspend/resume not working on HP nx6110 o kern/76950 acpi ACPI wrongly blacklisted on Micron ClientPro 766Xi sys s kern/73823 acpi [request] acpi / power-on by timer support o i386/72566 acpi ACPI, FreeBSD disables fan on Compaq Armada 1750 o i386/69750 acpi Boot without ACPI failed on ASUS L5 o kern/56024 acpi ACPI suspend drains battery while in S3 o i386/55661 acpi ACPI suspend/resume problem on ARMADA M700 o i386/54756 acpi ACPI suspend/resume problem on CF-W2 laptop 54 problems total.