Re: APU2, legacy firmware 4.0.22, FreeBSD 12.0 hangs in boot
Hi! > Testing FreeBSD 12.0 on an apu2d4 with WLAN board, after upgrading to > > http://pcengines.ch/file/apu2_v4.0.22.rom.tar.gz > > the boot hangs after: With apu2_v4.8.0.5.rom it boots. -- p...@freebsd.org +49 171 3101372 2 years to go ! ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
APU2, legacy firmware 4.0.22, FreeBSD 12.0 hangs in boot
Hi! Testing FreeBSD 12.0 on an apu2d4 with WLAN board, after upgrading to http://pcengines.ch/file/apu2_v4.0.22.rom.tar.gz the boot hangs after: [...] Event timer "RTC" frequency 32768 Hz quality 0 attimer0: port 0x40-0x43 irq 0 on acpi0 Timecounter "i8254" frequency 1193182 Hz quality 0 Event timer "i8254" frequency 1193182 Hz quality 100 hpet0: iomem 0xfed0-0xfed003ff on acpi0 Timecounter "HPET" frequency 14318180 Hz quality 950 Timecounter "ACPI-safe" frequency 3579545 Hz quality 850 acpi_timer0: <32-bit timer at 3.579545MHz> port 0x818-0x81b on acpi0 acpi_button0: on acpi0 pcib0: port 0xcf8-0xcff on acpi0 pci0: on pcib0 It booted with the former version, but very slowly. I can provide a full boot log if required. Any ideas ? -- p...@freebsd.org +49 171 3101372 2 years to go ! ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: boot hang with certain Phenom II cpu models
On 14/12/2018 21:37, Sascha Klauder wrote: > On Fri, 2018-12-14 11:56 +0200, Andriy Gapon wrote: >> On 13/12/2018 12:56, Sascha Klauder wrote: >>> So far, I tried (unsuccessfully) to disable obvious ACPI sub- >>> systems (cpu, mwait, quirks) and debug settings (acpi.cpu_unordered, >>> acpi.max_threads). Anyone got a hint where to look or debug this >>> further? >> Are you able to identify if you have a hardware or a software hang? >> E.g., are you able to enter ddb? > > Hardware; can't enter ddb and can't toggle caps lock. I could > probably setup remote GDB (serial) but would need some pointer > how to proceed from there. The only idea I have is to boot to ddb (boot_ddb="YES" or boot -d), set a breakpoint in a function from which the last printed line comes[*], continue until the breakpoint is hit and then step from there trying to narrow down a function (or even an instruction) where the hang happens. [*] - seems to be pcie_cfgregopen() -- Andriy Gapon ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
