Hi!
I just had the same panic, with a 10.99.14 GENERIC from 20250505,
during a bulk build.
Before that I was running 10.99.12 that was stable.
On Mon, Apr 21, 2025 at 03:50:08PM +0100, Patrick Welche wrote:
> On Mon, Apr 21, 2025 at 07:52:07AM +1000, matthew green wrote:
> > > (gdb) print panics
On Mon, Apr 21, 2025 at 07:51:45PM +0100, Patrick Welche wrote:
> Just got another one - opening a PR...
kern/59339
Just got another one - opening a PR...
cpu0: found cpu1 heart stopped beating after 16 seconds
panic: cpu1[27 softclk/1]: heart stopped beating
cpu1: Begin traceback...
vpanic() at netbsd:vpanic+0x161
panic() at netbsd:panic+0x3c
defibrillator() at netbsd:defibrillator+0x6b
ipi_msg_cpu_handler() a
On Mon, Apr 21, 2025 at 07:52:07AM +1000, matthew green wrote:
> > (gdb) print panicstr
> > $2 = 0x80f06020 "cpu0: softints stuck for 16 seconds"
>
> you'll need to find cpu0's back trace. try feeding the core
> into crash(8) instead of GDB, it should be easier to find.
crash> bt
end()
On Mon, 21 Apr 2025, matthew green wrote:
(gdb) print panicstr
$2 = 0x80f06020 "cpu0: softints stuck for 16 seconds"
you'll need to find cpu0's back trace. try feeding the core
into crash(8) instead of GDB, it should be easier to find.
FWIW, i upgraded my main desktop to sources fro
> (gdb) print panicstr
> $2 = 0x80f06020 "cpu0: softints stuck for 16 seconds"
you'll need to find cpu0's back trace. try feeding the core
into crash(8) instead of GDB, it should be easier to find.
FWIW, i upgraded my main desktop to sources from about 70
hours ago, shortly after 70 hou
On Sun, Apr 20, 2025 at 06:36:46PM +0100, Patrick Welche wrote:
> I have been running 10.99.14 since Thursday, and just now, while
> untarring 600MB of gcc 16, I got
Of course, after the reboot, it untarred just fine, so not exactly
reproducible...
P
On Thu, Apr 17, 2025 at 09:46:02AM +0200, Thomas Klausner wrote:
> I just tried updating from 10.99.12 from March 24 to 10.99.14 from
> today. After a reboot with the new kernel, while installing the
> userland (basically, two pax(1) and then postinstall fix) I did some
> emacs editing, when the ma
Not while upgrading, that went fine but, I got a complete freeze today on a 4
day old 10.99.14
Had to do a force shutdown and on a new boot I got a file system corruption.
So, no details here either :(
