Created attachment 147876 [details] picture of the panic The system is a HP Probook 430 G1 with Intel Core i5-4200U CPU and with integrated GPU. The kernel paniced with 10.1-BETA3 and current 11-SNAPSHOT too. See the attached picture.
Created attachment 147878 [details] linux's dmesg
Created attachment 147879 [details] linux's lspci
addr2line "RIP": sys/vm/vm_map.c:502 map->system_map does not exists void _vm_map_lock_read(vm_map_t map, const char *file, int line) { if (map->system_map) mtx_lock_flags_(&map->system_mtx, 0, file, line); else sx_slock_(&map->lock, file, line); }
After BIOS update to latest BIOS, the problem _not_ changed.
This is with UEFI Hybrid mode (with CSM).
Created attachment 147887 [details] load prompt in UEFI native mode (without CSM)
Would you kindly addr2line the previous few addresses in the backtrace?
Created attachment 147888 [details] load prompt in UEFI native mode (without CSM) I got this screen, when booting with UEFI native mode (without CSM). Possibly this is an kernel panic.
This looks like it might just be incorrect framebuffer information. You may be able to try blindly logging in, or blindly rebooting if you're in ddb.
Seems like the system is in ddb or something similar, because when I pressed the power button, the system immediately go to S5 (shuting down).
Does the screen change after kernel starts, or does it show the same static corruption the whole time? (I.e., it's useful to know if it's booting up and then panics, or happens very early on.) You can confirm it's in ddb by blindly typing 'reset' and hitting enter -- if it does reboot, then it was in ddb.
To this point the screen changed. The blindly writing trick don't working, because to early to initialize the keyboard. If I try boot -v in hybrid mode, I got a different trap: Privileged instructionn fault in cam_compat.c +60 line of 10.1-BETA3. But at this point it's again to early to get a working keyboard. After that I tried to boot w/ and w/o EFI signing keys to boot, but none of them worked. Is there any EFI facility to create EFI logs, which I can read via EFI BIOS menu?
Created attachment 147929 [details] hbsd-11 native mode w/o csm
Created attachment 147930 [details] hbsd-11 hybrid mode w/ csm
Created attachment 147931 [details] hbsd-11 hybrid mode w/ csm
Created attachment 147932 [details] hbsd-11 hybrid mode w/ csm
http://www.crysys.hu/~op/freebsd/memstick-debug.img Builded a new memstick installer, and enabled VERBOSE_SYSINIT and DEBUG options in kernel config, but these options don't have any effect. With CURRENT, I got a running DDB. In native mode w/o CSM the kernel hanged up after printed out terminal settings. In native mode defaulted to 1366x768 resolution. In hybrid mode, the system goes towards, but paniced due NULL pointer deref. The stack traces are in newly uploaded images. The R12 registers value is 0, and the system derefed this. In hybrid mode, the system defaulted to 1024x768 resolution.
Created attachment 147933 [details] hbsd-11 hybrid mode w/ csm
Created attachment 148041 [details] fbsd10rc1 uefi hybrid mode with csm
Created attachment 148042 [details] fbsd10rc1 uefi native mode without csm
I can boot my 430, if I copied the 9.3 /boot/loader to installer (as troyax mentioned in #187488) but only if I hit ESC and after it ENTER in first stage loader. Probably there are differences between gcc and clang generated /boot/loader. I'm now investigating in this way.
Created attachment 148207 [details] mostly working loader from FreeBSD 9.3-RELEASE added mostly working loader in legacy mode from FreeBSD 9.3-RELEASE
Created attachment 148208 [details] broken loader from 11-CURRENT broken loader in legacy mode from 11-CURRENT
The UEFI mode remained broken, but in legacy mode I can install FreeBSD with the described hack. In overall, in legacy mode the system will boot if copied the loader binary (compiled with gcc) from FreeBSD 9.3 release to memstick usb installer, and named loader.gcc, and manually change to load them at boot time. After this, the installation completed as expected and the system able to boot up with the original 11-CURRENT's loader (which compiled with clang).
I'm having the exact same problem with my HP ProBook 6475b (CPU: A6-4400M) with BIOS F.47 and the latest F.50 Rev.A. So it might be not a problem that is limited to the ProBook G430 G1 but a problem with the UEFI used by HP.
I had the same problem on my Pavilion x2. The solution for me was to use "mode 3" before boot. This works on 10.1, however it is not working on 11-CURRENT.
Try this installer: http://www.crysys.hu/~op/freebsd/memstick-debug.img
(In reply to Oliver Pinter from comment #27) > Try this installer: http://www.crysys.hu/~op/freebsd/memstick-debug.img Default boot gives me EFI framebuffer information, like the original 11-current. With "mode 3", kernel starts to boot, and then screen goes blank and pc freezes. The last thing I think can see (It's hard to tell because it goes blank fast) is something like cpu start and virtual memory.
please ping me, and I will create a new set with the workaround, or just try this another installers: http://jenkins.hardenedbsd.org/builds/HardenedBSD_Master/latest-amd64/
Updated 10.1-BETA and 10.1-RC versioned bugs to 10.1-STABLE.
See http://lists.freebsd.org/pipermail/freebsd-stable/2015-March/081972.html for details about similar problems with HP EliteBook 850 G1.
If possible can you please test with the patch in PR 191564
This is believed to be fixed for everybody in FreeBSD -current as of today (revision 286667). Please test at your earliest convenience.
Confirmed. The mentioned patch fixed the panic issue with UEFI + CSM mode, but I still have problems with pure UEFI mode.