Current problem reports assigned to freebsd-acpi@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/187152 acpi [i386] [acpi] resume from ACPI suspend (s3) sometimes o kern/181665 acpi [acpi] System will not go into S3 state. o kern/180897 acpi [acpi] ACPI error with MB p8h67 v.1405 o kern/174766 acpi [acpi] Random acpi panic o kern/174504 acpi [ACPI] Suspend/resume broken on Lenovo x220 o kern/173408 acpi [acpi] [regression] ACPI Regression: battery does not o kern/171305 acpi [acpi] acpi_tz0: _CRT value is absurd, ignored (256.0C o kern/165381 acpi [cpufreq] powerd(8) eats CPUs for breakfast o kern/164329 acpi [acpi] hw.acpi.thermal.tz0.temperature shows strange v o kern/162859 acpi [acpi] ACPI battery/acline monitoring partialy working o kern/161715 acpi [acpi] Dell E6520 doesn't resume after ACPI suspend o kern/161713 acpi [acpi] Suspend on Dell E6520 o kern/160838 acpi [acpi] ACPI Battery Monitor Non-Functional o kern/160419 acpi [acpi_thermal] acpi_thermal kernel thread high CPU usa o kern/158689 acpi [acpi] value of sysctl hw.acpi.thermal.polling_rate ne o kern/154955 acpi [acpi] Keyboard or ACPI doesn't work on Lenovo S10-3 o kern/152098 acpi [acpi] Lenovo T61p does not resume o i386/146715 acpi [acpi] Suspend works, resume not on a HP Probook 4510s o kern/145306 acpi [acpi]: Can't change brightness on HP ProBook 4510s o i386/143798 acpi [acpi] shutdown problem with SiS K7S5A o kern/143420 acpi [acpi] ACPI issues with Toshiba o kern/142009 acpi [acpi] [panic] Panic in AcpiNsGetAttachedObject o kern/139088 acpi [acpi] ACPI Exception: AE_AML_INFINITE_LOOP error o amd64/138210 acpi [acpi] acer aspire 5536 ACPI problems (S3, brightness, o i386/136008 acpi [acpi] Dell Vostro 1310 will not shutdown (Requires us o kern/132602 acpi [acpi] ACPI Problem with Intel SS4200: System does not a i386/122887 acpi [panic] [atkbdc] 7.0-RELEASE on IBM HS20 panics immed s kern/112544 acpi [acpi] [patch] Add High Precision Event Timer Driver f o kern/73823 acpi [request] acpi / power-on by timer support 29 problems total. ___ freebsd-acpi@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-acpi To unsubscribe, send any mail to freebsd-acpi-unsubscr...@freebsd.org
Re: ACPI issues with PC engines APU beta board
On 3/3/2014 10:48 AM, Larry Baird wrote: This beta board runs coreboot, which is GPL'ed software. This means that it is possible to submit a contribution that lets you boot FreeBSD 9.2 and 10. Working with PC Engines to come up with a solution is the right way. FWIW, I can boot FreeBSD 9.2 just fine on amd64 hardware (ASUS F2A85-M) that also starts with coreboot. FreeBSD has working on the issue from two directions. 1) John Baldwin j...@freebsd.org has made software changes to FreeBSD head that work around the issue (http://svnweb.freebsd.org/base?view=revisionsortby=daterevision=261243). This issue was to be MFCed a few weeks back. I am sure that John will MFC it at some point. 2) I worked with Jung-uk Kim j...@freebsd.org to develop BIOS patches to give to PC Engines to provide back to SAGE. I received an updated BIOS with this change the end of last week. Hi, I just got one of these boards to evaluate. I was trying to load the watchdog, but no luck. There seem to be a few other errors too amdsbwd0: ResetStatus0 = 0xf9 amdsbwd0: ResetStatus1 = 0x0b amdsbwd0: memory base address = 0xfec000f0 amdsbwd0: AMD SB8xx Watchdog Timer at iomem 0xfec000f0-0xfec000f3,0xfec000f4-0xfec000f7 on isa0 amdsbwd0: bus_alloc_resource for ctrl failed device_attach: amdsbwd0 attach returned 6 USB seems to have some issues as well device_attach: pcib4 attach returned 6 ohci0: AMD SB7x0/SB8x0/SB9x0 USB controller at device 20.5 on pci0 ohci0: 0x1000 bytes of rid 0x10 res 3 failed (0, 0x). ohci0: Could not map memory device_attach: ohci0 attach returned 6 pcib4: ACPI PCI-PCI bridge at device 21.0 on pci0 pci4: ACPI PCI bus on pcib4 ohci0: AMD SB7x0/SB8x0/SB9x0 USB controller at device 22.0 on pci0 ohci0: 0x1000 bytes of rid 0x10 res 3 failed (0, 0x). ohci0: Could not map memory device_attach: ohci0 attach returned 6 ehci0: AMD SB7x0/SB8x0/SB9x0 USB 2.0 controller at device 22.2 on pci0 ehci0: 0x100 bytes of rid 0x10 res 3 failed (0, 0x). ehci0: Could not map memory device_attach: ehci0 attach returned 6 acpi_button0: Power Button on acpi0 pmtimer0 on isa0 not sure of the NIC errors are issues too ? re2: RealTek 8168/8111 B/C/CP/D/DP/E/F/G PCIe Gigabit Ethernet port 0x3000-0x30ff at device 0.0 on pci3 re2: 0x1000 bytes of rid 0x18 res 3 failed (0, 0x). re2: 0x4000 bytes of rid 0x20 res 3 failed (0, 0x). re2: could not allocate MSI-X PBA resource re2: Using 1 MSI message re2: ASPM disabled re2: Chip rev. 0x2c00 re2: MAC rev. 0x0020 miibus2: MII bus on re2 rgephy2: RTL8169S/8110S/8211 1000BASE-T media interface PHY 1 on miibus2 rgephy2: none, 10baseT, 10baseT-FDX, 10baseT-FDX-flow, 100baseTX, 100baseTX-FDX, 100baseTX-FDX-flow, 1000baseT, 1000baseT-master, 1000baseT-FDX, 1000baseT-FDX-master, 1000baseT-FDX-flow, 1000baseT-FDX-flow-master, auto, auto-flow re2: Ethernet address: 00:0d:b9:33:11:c6 Start bios (version ?-20131224_111227-ubuntubuilderx64) CPU Mhz=1000 10.0-STABLE FreeBSD 10.0-STABLE #2 r262153 i386 ---Mike -- --- Mike Tancsa, tel +1 519 651 3400 Sentex Communications, m...@sentex.net Providing Internet services since 1994 www.sentex.net Cambridge, Ontario Canada http://www.tancsa.com/ ___ freebsd-acpi@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-acpi To unsubscribe, send any mail to freebsd-acpi-unsubscr...@freebsd.org
Re: ACPI issues with PC engines APU beta board
On Mon, Mar 10, 2014 at 03:49:22PM -0400, Mike Tancsa wrote: On 3/3/2014 10:48 AM, Larry Baird wrote: This beta board runs coreboot, which is GPL'ed software. This means that it is possible to submit a contribution that lets you boot FreeBSD 9.2 and 10. Working with PC Engines to come up with a solution is the right way. FWIW, I can boot FreeBSD 9.2 just fine on amd64 hardware (ASUS F2A85-M) that also starts with coreboot. FreeBSD has working on the issue from two directions. 1) John Baldwin j...@freebsd.org has made software changes to FreeBSD head that work around the issue (http://svnweb.freebsd.org/base?view=revisionsortby=daterevision=261243). This issue was to be MFCed a few weeks back. I am sure that John will MFC it at some point. 2) I worked with Jung-uk Kim j...@freebsd.org to develop BIOS patches to give to PC Engines to provide back to SAGE. I received an updated BIOS with this change the end of last week. Hi, I just got one of these boards to evaluate. I was trying to load the watchdog, but no luck. There seem to be a few other errors too amdsbwd0: ResetStatus0 = 0xf9 amdsbwd0: ResetStatus1 = 0x0b amdsbwd0: memory base address = 0xfec000f0 amdsbwd0: AMD SB8xx Watchdog Timer at iomem 0xfec000f0-0xfec000f3,0xfec000f4-0xfec000f7 on isa0 amdsbwd0: bus_alloc_resource for ctrl failed device_attach: amdsbwd0 attach returned 6 USB seems to have some issues as well device_attach: pcib4 attach returned 6 ohci0: AMD SB7x0/SB8x0/SB9x0 USB controller at device 20.5 on pci0 ohci0: 0x1000 bytes of rid 0x10 res 3 failed (0, 0x). ohci0: Could not map memory device_attach: ohci0 attach returned 6 pcib4: ACPI PCI-PCI bridge at device 21.0 on pci0 pci4: ACPI PCI bus on pcib4 ohci0: AMD SB7x0/SB8x0/SB9x0 USB controller at device 22.0 on pci0 ohci0: 0x1000 bytes of rid 0x10 res 3 failed (0, 0x). ohci0: Could not map memory device_attach: ohci0 attach returned 6 ehci0: AMD SB7x0/SB8x0/SB9x0 USB 2.0 controller at device 22.2 on pci0 ehci0: 0x100 bytes of rid 0x10 res 3 failed (0, 0x). ehci0: Could not map memory device_attach: ehci0 attach returned 6 acpi_button0: Power Button on acpi0 pmtimer0 on isa0 not sure of the NIC errors are issues too ? re2: RealTek 8168/8111 B/C/CP/D/DP/E/F/G PCIe Gigabit Ethernet port 0x3000-0x30ff at device 0.0 on pci3 re2: 0x1000 bytes of rid 0x18 res 3 failed (0, 0x). re2: 0x4000 bytes of rid 0x20 res 3 failed (0, 0x). re2: could not allocate MSI-X PBA resource re2: Using 1 MSI message re2: ASPM disabled re2: Chip rev. 0x2c00 re2: MAC rev. 0x0020 miibus2: MII bus on re2 rgephy2: RTL8169S/8110S/8211 1000BASE-T media interface PHY 1 on miibus2 rgephy2: none, 10baseT, 10baseT-FDX, 10baseT-FDX-flow, 100baseTX, 100baseTX-FDX, 100baseTX-FDX-flow, 1000baseT, 1000baseT-master, 1000baseT-FDX, 1000baseT-FDX-master, 1000baseT-FDX-flow, 1000baseT-FDX-flow-master, auto, auto-flow re2: Ethernet address: 00:0d:b9:33:11:c6 Start bios (version ?-20131224_111227-ubuntubuilderx64) CPU Mhz=1000 10.0-STABLE FreeBSD 10.0-STABLE #2 r262153 i386 You will need to either update the BIOS or patch FreeBSD 10. The patch associated with: http://svnweb.freebsd.org/base?view=revisionsortby=daterevision=261243 applies cleanly to FreeBSD 10. The latest BIOS from PC engines for the APU board is very noisy when it boots. Hopefully the code change will get MFCed now that the APU board is generally available: http://www.pcengines.ch/apu.htm Larry -- Larry Baird Global Technology Associates, Inc. 1992-2012| http://www.gta.com Celebrating Twenty Years of Software Innovation | Orlando, FL Email: l...@gta.com | TEL 407-380-0220 ___ freebsd-acpi@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-acpi To unsubscribe, send any mail to freebsd-acpi-unsubscr...@freebsd.org
Re: ACPI issues with PC engines APU beta board
On 3/10/2014 4:03 PM, Larry Baird wrote: On Mon, Mar 10, 2014 at 03:49:22PM -0400, Mike Tancsa wrote: On 3/3/2014 10:48 AM, Larry Baird wrote: This beta board runs coreboot, which is GPL'ed software. This means that it is possible to submit a contribution that lets you boot FreeBSD 9.2 and 10. Working with PC Engines to come up with a solution is the right way. FWIW, I can boot FreeBSD 9.2 just fine on amd64 hardware (ASUS F2A85-M) that also starts with coreboot. FreeBSD has working on the issue from two directions. 1) John Baldwin j...@freebsd.org has made software changes to FreeBSD head that work around the issue (http://svnweb.freebsd.org/base?view=revisionsortby=daterevision=261243). This issue was to be MFCed a few weeks back. I am sure that John will MFC it at some point. 2) I worked with Jung-uk Kim j...@freebsd.org to develop BIOS patches to give to PC Engines to provide back to SAGE. I received an updated BIOS with this change the end of last week. Hi, I just got one of these boards to evaluate. I was trying to load the watchdog, but no luck. There seem to be a few other errors too amdsbwd0: ResetStatus0 = 0xf9 amdsbwd0: ResetStatus1 = 0x0b amdsbwd0: memory base address = 0xfec000f0 amdsbwd0: AMD SB8xx Watchdog Timer at iomem 0xfec000f0-0xfec000f3,0xfec000f4-0xfec000f7 on isa0 amdsbwd0: bus_alloc_resource for ctrl failed device_attach: amdsbwd0 attach returned 6 USB seems to have some issues as well device_attach: pcib4 attach returned 6 ohci0: AMD SB7x0/SB8x0/SB9x0 USB controller at device 20.5 on pci0 ohci0: 0x1000 bytes of rid 0x10 res 3 failed (0, 0x). ohci0: Could not map memory device_attach: ohci0 attach returned 6 pcib4: ACPI PCI-PCI bridge at device 21.0 on pci0 pci4: ACPI PCI bus on pcib4 ohci0: AMD SB7x0/SB8x0/SB9x0 USB controller at device 22.0 on pci0 ohci0: 0x1000 bytes of rid 0x10 res 3 failed (0, 0x). ohci0: Could not map memory device_attach: ohci0 attach returned 6 ehci0: AMD SB7x0/SB8x0/SB9x0 USB 2.0 controller at device 22.2 on pci0 ehci0: 0x100 bytes of rid 0x10 res 3 failed (0, 0x). ehci0: Could not map memory device_attach: ehci0 attach returned 6 acpi_button0: Power Button on acpi0 pmtimer0 on isa0 not sure of the NIC errors are issues too ? re2: RealTek 8168/8111 B/C/CP/D/DP/E/F/G PCIe Gigabit Ethernet port 0x3000-0x30ff at device 0.0 on pci3 re2: 0x1000 bytes of rid 0x18 res 3 failed (0, 0x). re2: 0x4000 bytes of rid 0x20 res 3 failed (0, 0x). re2: could not allocate MSI-X PBA resource re2: Using 1 MSI message re2: ASPM disabled re2: Chip rev. 0x2c00 re2: MAC rev. 0x0020 miibus2: MII bus on re2 rgephy2: RTL8169S/8110S/8211 1000BASE-T media interface PHY 1 on miibus2 rgephy2: none, 10baseT, 10baseT-FDX, 10baseT-FDX-flow, 100baseTX, 100baseTX-FDX, 100baseTX-FDX-flow, 1000baseT, 1000baseT-master, 1000baseT-FDX, 1000baseT-FDX-master, 1000baseT-FDX-flow, 1000baseT-FDX-flow-master, auto, auto-flow re2: Ethernet address: 00:0d:b9:33:11:c6 Start bios (version ?-20131224_111227-ubuntubuilderx64) CPU Mhz=1000 10.0-STABLE FreeBSD 10.0-STABLE #2 r262153 i386 You will need to either update the BIOS or patch FreeBSD 10. The patch associated with: http://svnweb.freebsd.org/base?view=revisionsortby=daterevision=261243 applies cleanly to FreeBSD 10. The latest BIOS from PC engines for the APU board is very noisy when it boots. Hopefully the code change will get MFCed now that the APU board is generally available: http://www.pcengines.ch/apu.htm Where can I find the latest BIOS ? Its not on the website Any reason why this has not been MFC'd ? Is there a downside to having it applied / running with it ? ---Mike Larry -- --- Mike Tancsa, tel +1 519 651 3400 Sentex Communications, m...@sentex.net Providing Internet services since 1994 www.sentex.net Cambridge, Ontario Canada http://www.tancsa.com/ ___ freebsd-acpi@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-acpi To unsubscribe, send any mail to freebsd-acpi-unsubscr...@freebsd.org
