On 2026/07/08 09:42, MrArchive wrote: > Panic Attack upon fresh install boot > > sendbug — Coming straight to your house
there's nothing from "sendbug" output in here... > On my ASUSTeK COMPUTOR INC. E402MA with 4GB Memory and a Intel Celeron(R) CPU > N2940 @ 1.83GHz x > 4, I found that after a clean install of openBSD, it was having issues where > it fails to boot. > See the attached images bellow for the exact error message on display. the top lines visible on screen read ize 0x0 panic: extent_do_alloc_region: bad size (followed by a backtrace showing that this was called from sdhc_acpi_attach) it would probably be useful to know what the line that was cut off before "ize 0x0" says (you might catch it with a slow-motion video; !do not attach the video to the list! just re-type the text of that line instead). > I found the solution to be turning on fastboot in system bios. > > I don’t know why this works, but it did... > > This is after several attempts to ‘fix’ the usb bootable device and > reinstalling openbsd to > confirm it wasn’t a corruption with the installer and a sneaky Ubuntu install > to confirm the > hardware wasn’t fucked. you may be able to boot OpenBSD if you disable the sdhc driver: "boot -c" at the "boot>" prompt, "disable sdhc", "quit". it would probably be useful to have copies of the acpi tables and other information with "fastboot" both disabled and enabled. so if you are able to boot OpenBSD with the above, you can save this information to a file by running "sendbug -P > somefile" as root (i.e. save to one file with fastboot disabled, one with fastboot enabled, and attach them both to an email reply to [email protected]). if unable to do this on OpenBSD, you might be able to do it on another OS if you install "acpica-tools" and use "acpidump -b", this writes a bunch of files to the current directory so you'll need to create separate directories for fastboot and not-fastboot.
