Hi Andrius,thanks for your response. You are right, the issue maps not exactly to the reported problem as a different CPU is installed.
Anyway, the following actions did not succeed so far: - booting with boot -12 - booting from SATA hard drive with pre-installed NetBSD - USB options not configurable in BIOS- older Release NetBSD 6.0 did also not boot (hangs at the second spinner 123456\ but does not reboot)
- switching from AHCI to legacy/native IDE mode - Booting FreeBSD 11.2 also hangs in primary bootstrap Especially the fact that FreeBSD doesn't boot either led me to I will try to find out if I get to the point where I could debug into the kernel from my serial console...
Kind regards Matthias http://freebsd.1045724.x6.nabble.com/boot-hang-with-certain-Phenom-II-cpu-models-td6300528.html
Am 09.12.2019 um 22:08 schrieb Andrius V:
Hi, It is quite unlikely that your issue is related to the original bug report since hardware was VIA based (VIA C7-M+VN896) HP 2133 netbook. The typical actions I would try to do: 1) boot without ACPI/SMP enabled (boot -12) 2) if you're booting using USB media, you can try to change some relevant USB options (speed let's say, depends on BIOS) or try to boot from non USB media (CD, netboot or install it to HDD on the compatible machine and attach it to your system). If any of those boot, you can check dmesg output for potentially unsupported hardware. Finally you can try to boot older releases to see if it worked before. Otherwise you are probably out of luck (playing with some BIOS options like switching between AHCI/IDE modes may help but not necessarily). P.S. gnats-bugs%netbsd.org@localhost should be added as one of email addresses. On Mon, Dec 9, 2019 at 9:18 PM Matthias Petermann <mp%petermann-it.de@localhost> wrote:resent mail, removed tuotila%gmx.com@localhost from cc (address seams to be not existing anymore) --- Hi, Am 09.12.2019 um 14:38 schrieb Paul Goyette:WARNING: 1 module failed to load How do I find out which module failed to load here?Almost certainly, this is a failure to load the ffs filesystem, since the filesystem module is already built-in to the kernel. The message can safely be ignored.That's bad news ;-) So there is no known way to debug this further. I wish I had more knowledge on possible causes. The box boots without any issue into Slackware Linux. I should try a BIOS upgrade and/or try a NetBSD version older than the one where the issue was first reported. Kind regards Matthias -- Matthias Petermann <mp%petermann-it.de@localhost> | www.petermann-it.de Innovative IT-Lösungen, Systemintegration, Linux/FreeBSD/Unix-Support Wildparkring 13, 01458 Ottendorf-Okrilla | Tel.: +49 (0)35205 597 991
-- Matthias Petermann <mp%petermann-it.de@localhost> | www.petermann-it.de Innovative IT-Lösungen, Systemintegration, Linux/FreeBSD/Unix-Support Wildparkring 13, 01458 Ottendorf-Okrilla | Tel.: +49 (0)35205 597 991
Description: S/MIME Cryptographic Signature