https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=285867

anth...@adfw.co.uk changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |anth...@adfw.co.uk

--- Comment #8 from anth...@adfw.co.uk ---
I can report the same issue with 14.2-RELEASE, and also 14-STABLE on a T400.
I've spent weeks trying to diagnose this so I'm pleased it's not just me!


The "solution" is the same as Henrich reports. Booting with kern.smp.disabled=1
is successful and I'm able to login graphically.


If I build 14-STABLE with some debugging options enabled, it will boot with SMP
enabled maybe 2 out of 3 times, and otherwise it locks up during boot (usually
just after bringing the network interfaces up). Once it boots (with or without
SMP), everything seems stable, suspend/resume works and I can do intensive
tasks like buildkernel. But of course things are slower due to the debugging
options.

Happy to try things out, unfortunately the T400 is not getting any younger and
make buildkernel without SMP takes well over 1 hour, so things take a bit of
time to test!

Regards,
Anthony

Options set as follows:

$ diff GENERIC T400
21c21
< ident         GENERIC
---
> ident         T400
95a96,106
> options       DDB                     # Support DDB
> options       GDB                     # Support remote GDB
> options       DEADLKRES               # Enable the deadlock resolver
> options       INVARIANTS              # Enable calls of extra sanity checking
> options       INVARIANT_SUPPORT       # Extra sanity checks of internal 
> structures
> options       WITNESS                 # Enable checks to detect deadlocks and 
> cycles
> options       WITNESS_SKIPSPIN        # Don't run witness on spinlocks for 
> speed
> options       ALT_BREAK_TO_DEBUGGER   # Enter debugger on keyboard escape 
> sequence
> options       VERBOSE_SYSINIT=0       # Support debug.verbose_sysinit, off by 
> default

-- 
You are receiving this mail because:
You are the assignee for the bug.

Reply via email to