System needs to be hard reset few times to boot

GlitchyDot

GlitchyDot

Having some issues booting FreeBSD 14.1-STABLE.
Sometimes it boots ok sometimes i have to do hard reset sometimes i have to do few times ( just now had to do 2 times )
When it fails to boot its always stuck on same process
Code: 
---<<BOOT>>---
Copyright (c) 1992-2023 The FreeBSD Project.
Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
        The Regents of the University of California. All rights reserved.
FreeBSD is a registered trademark of The FreeBSD Foundation.
FreeBSD 14.1-STABLE stable/14-n268744-79c34d704f31 GENERIC amd64
FreeBSD clang version 18.1.6 (https://github.com/llvm/llvm-project.git llvmorg-18.1.6-0-g1118c2e05e67)
VT(efifb): resolution 800x600
CPU: Intel(R) Xeon(R) CPU E5-2690 v4 @ 2.60GHz (2594.42-MHz K8-class CPU)
  Origin="GenuineIntel"  Id=0x406f1  Family=0x6  Model=0x4f  Stepping=1
  Features=0xbfebfbff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE>
  Features2=0x7ffefbff<SSE3,PCLMULQDQ,DTES64,MON,DS_CPL,VMX,SMX,EST,TM2,SSSE3,SDBG,FMA,CX16,xTPR,PDCM,PCID,DCA,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,TSCDLT,AESNI,XSAVE,OSXSAVE,AVX,F16C,RDRAND>
  AMD Features=0x2c100800<SYSCALL,NX,Page1GB,RDTSCP,LM>
  AMD Features2=0x121<LAHF,ABM,Prefetch>
  Structured Extended Features=0x21cbfbb<FSGSBASE,TSCADJ,BMI1,HLE,AVX2,SMEP,BMI2,ERMS,INVPCID,RTM,PQM,NFPUSG,PQE,RDSEED,ADX,SMAP,PROCTRACE>
  Structured Extended Features3=0x9c000400<MD_CLEAR,IBPB,STIBP,L1DFL,SSBD>
  XSAVE Features=0x1<XSAVEOPT>
  VT-x: PAT,HLT,MTF,PAUSE,EPT,UG,VPID,VID,PostIntr
  TSC: P-state invariant, performance statistics
real memory  = 34359738368 (32768 MB)
avail memory = 33202286592 (31664 MB)
Event timer "LAPIC" quality 600
ACPI APIC Table: <ALASKA A M I >
FreeBSD/SMP: Multiprocessor System Detected: 56 CPUs
FreeBSD/SMP: 2 package(s) x 14 core(s) x 2 hardware threads
random: registering fast source Intel Secure Key RNG
random: fast provider: "Intel Secure Key RNG"
random: unblocking device.
ioapic0 <Version 2.0> irqs 0-23
ioapic1 <Version 2.0> irqs 24-47
ioapic2 <Version 2.0> irqs 48-71
Launching APs: 1 28 2 54 26 12 39 6 9 8 51 50 25 19 49 43 13 7 30 27 18 20 23 4 46 3 32 41 53 52 29 14 15 22 17 48 36 42 34 40 24 11 44 16 45 55 38 31 10 21 35 47 37 5 33
random: entropy device external interface
kbd1 at kbdmux0
efirtc0: <EFI Realtime Clock>
efirtc0: registered as a time-of-day clock, resolution 1.000000s
smbios0: <System Management BIOS> at iomem 0x7db76918-0x7db76936
smbios0: Version: 2.8, BCD Revision: 2.8
aesni0: <AES-CBC,AES-CCM,AES-GCM,AES-ICM,AES-XTS>
acpi0: <ALASKA A M I >
acpi0: Power Button (fixed)

Attached full dmesg.
 

Attachments

Have been running stable/14 since it was branched off, never had this issue. Neither with any of the previous stable branches.

Updated yesterday:
Code: 
dice@hosaka:~ % uname -a
FreeBSD hosaka.dicelan.home 14.1-STABLE FreeBSD 14.1-STABLE stable/14-n268895-a651978fc40c HOSAKA amd64
dice@hosaka:~ % uptime
 4:45PM  up 7 hrs, 1 user, load averages: 0.43, 0.42, 0.41
Some time ago:
Code: 
dice@molly:~ % uname -a
FreeBSD molly.dicelan.home 14.1-STABLE FreeBSD 14.1-STABLE stable/14-n268714-953142d6baf3 MOLLY amd64
dice@molly:~ % uptime
 4:46PM  up 18 days, 23:12, 2 users, load averages: 0.20, 0.16, 0.15

All running (and booting) just fine.
 
After installkernel, installworld, do you also run etcupdate(8)? And I always run make -DBATCH_DELETE_OLD_FILES delete-old and make -DBATCH_DELETE_OLD_FILES delete-old-libs too.
 
SirDice said:
After installkernel, installworld, do you also run etcupdate(8)? And I always run make -DBATCH_DELETE_OLD_FILES delete-old and make -DBATCH_DELETE_OLD_FILES delete-old-libs too.
Click to expand...
delete-old-libs should be something to do after installing kernel, wold, 'and' new packages when it is relevant. Running it before may leave things broken until they are appropriately reinstalled.
 
GlitchyDot said:
Ive never updated STABLE . This is going to be my first time. Reading handbook now. :)
Click to expand...
'before' upgrading your source tree, go through the etcupdate bootstrapping step to minimize work; not doing so is not the end of the world but its documentation doesn't make such a situration's next steps clear to the user. /usr/src/UPDATING also has good information to check & refer to.
 
For the original issue, does it sometimes work on first power on or can you 'fix' a bad boot with a full power off + on? Depending on the issue, you may get different output with more verbose booting (think that may impact normal system performance though) and it may be worth trying different boot options at the boot loader. Intermittent issues are not fun to track though but if it can be found that a setting eliminates the issue then its likely we narrowed down where to troubleshoot.

For bad hardware (was reproducibly failing with any OS trying to launch all cores) I added
hint.lapic.2.disabled=1
hint.lapic.3.disabled=1 to /boot/loader.conf to work around having 1 CPU core (+ its hyperthread) that is unstable on a machine; the BIOS didn't offer the option to shut off individual cores so I lost 2 or all but 1 if using its options. I forget how but you can set an option during boot of FreeBSD to boot without multiple cores.
 
I'm still patiently waiting for pkgbase to reach the official documentation with workflow. All I have been able to find is a wiki page and posts here, mailing list (always a good place to check for update related stuff), and reddit. Handbook, manpages, and /usr/src/UPDATING entries appearing will be when I figure its more official that it is intended for use now. At least people discussing it makes it sound like a good goal people have been working on.

When I've tried to read up on it, it seems like it has had growing pains like packages getting renamed requiring the user to manually make sure the old is removed + new is installed and update config merging sounds like a manual step of 'we copied all files with conflicts to an area for you to manually review and merge to what we now installed' which seems unnecessarily tedious and scary.
 
Mirror176 said:
growing pains
Click to expand...

True, but then GhostBSD switched to pkgbase, from which I assume that it's fairly mature.

1728180178960.pngpkg was significantly enhanced last year:
  • only generate .pkgsave files when really needed
Ideally, switch to pkgbase at the earliest opportunity – before exiting the installer, before adding a user to the system. Then there should be nothing, or next to nothing, tedious or scary.

I'll ping Colin Percival to ask which of these two paths will be used for FreeBSD-base.conf in 14.2:
  • /etc/pkg
  • /usr/local/etc/pkg/repos
 
With my laptop (Dell Latitude 5591), if I have the lid shut during boot, FreeBSD was consistent at freezing at the boot loader when trying to boot the OS or somewhere early-boot. No problems with lid open. I have my laptop docked to a screen/mouse/keyboard/speakers table set-up.

I think this has something to do with the VBIOS or GPU and whatever is done by having BIOS display on an external HDMI screen instead of the laptop screen (maybe something with UEFI GOP VBIOS vs Legacy/CSM).

Edit: Saw last night that the Legacy Option ROMs option in my BIOS actively changes what VBIOS is used (GOP 1017 without Legacy, and something 1015 with Legacy; it's shown in the BIOS system information page towards the bottom).
 
Last edited:
You must log in or register to reply here.
Back
Top