https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=231080
--- Comment #21 from Sean Bruno ---
(In reply to Mark Johnston from comment #19)
88 seems to be where I started and these systems were not crashing at that
point.
--
You are receiving this mail because:
You are the assignee for the bu
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=231080
--- Comment #20 from Mark Johnston ---
Created attachment 197531
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=197531&action=edit
debug patch
Please give the attached patch a try. It adds some panic()s that will
hopefully catc
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=231080
--- Comment #19 from Mark Johnston ---
Sean, do you have some idea when the panic was introduced? Seems it was first
seen at r338350; which revision were the systems running before that?
--
You are receiving this mail because:
You are th
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=231080
--- Comment #18 from Mark Johnston ---
(In reply to Mark Johnston from comment #17)
s/lle_entry/llentry/
--
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bug
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=231080
--- Comment #17 from Mark Johnston ---
(In reply to Sean Bruno from comment #16)
The new kernel dump is more useful. The callout looks like this:
$2 = {
c_links = {
le = {
le_next = 0x11777be9162acbc1,
le_prev = 0xff
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=231080
--- Comment #16 from Sean Bruno ---
INVARIANTS does not crash. I waited for several days and no fault detected.
I updated the hosts to ALPHA6 and one of the hosts crashed after a few days of
uptime.
I have dumped the crash/kernel/debug i
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=231080
--- Comment #15 from Lawrence Stewart ---
I've only seen this once on the machine I have access to, so can't be much help
with reproduction or debugging unfortunately unless there's something useful I
can poke at in the core file.
Similar
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=231080
--- Comment #14 from Mark Johnston ---
(In reply to John Baldwin from comment #13)
Sean's also trying an INVARIANTS kernel at the moment, so we'll see if that
provides any insight.
--
You are receiving this mail because:
You are the assig
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=231080
--- Comment #13 from John Baldwin ---
You could try adding KTR with KTR_CALLOUT enabled in KTR_COMPILE and KTR_MASK.
We could then see if we can find the most recent actions for the offending
callout structure and work back from there.
--
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=231080
--- Comment #12 from Sean Bruno ---
(In reply to Mark Johnston from comment #10)
I added the boot dmesg from one of the example machines earlier in this ticket.
--
You are receiving this mail because:
You are the assignee for the bug.
___
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=231080
--- Comment #11 from Sean Bruno ---
(In reply to Mark Johnston from comment #10)
I have only seen the Atom servers (service1, igw0) crash in this way.
igw0 is acting as a router/firewall/gateway
service1 is acting as a jail host with a dn
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=231080
--- Comment #10 from Mark Johnston ---
(In reply to Sean Bruno from comment #9)
All 8 machines are crashing this way? Or is it just the two so far?
Can we identify the common configurations between service1 and igw0? It looks
like the lat
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=231080
--- Comment #9 from Sean Bruno ---
So I see this happen on my freebsd.org machines testing -current about every
other day. I'm only running about 8 machines at this point in the release
process.
Since its fairly consistent, is there some
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=231080
--- Comment #8 from Lawrence Stewart ---
I believe I may have hit this too the other day on a big iron server at $work
running GENERIC-NODEBUG r338290.
% sudo kgdb /boot/kernel/kernel /var/crash/vmcore.0
GNU gdb (GDB) 8.1.1 [GDB v8.1.1 fo
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=231080
--- Comment #7 from Sean Bruno ---
I've dropped the crashdump + kernel in my homedir on
freefall:~sbruno/igw0_crash.tgz
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=231080
Mark Johnston changed:
What|Removed |Added
CC||ma...@freebsd.org
Keywor
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=231080
--- Comment #6 from Sean Bruno ---
Created attachment 196917
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=196917&action=edit
Crash summary from igw0 (another Atom server) in the freebsd cluster
--
You are receiving this mail
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=231080
--- Comment #5 from Sean Bruno ---
Created attachment 196916
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=196916&action=edit
dmesg from atom servers that seem to be more likely to fall down
--
You are receiving this mail beca
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=231080
--- Comment #4 from Sean Bruno ---
I've had this happen at least 2 more times on these lower end machine (atom
class) in the freebsd cluster. This happens at svn 338340 but does not happen
at svn 88. That's not really "helpful" here,
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=231080
Sean Bruno changed:
What|Removed |Added
Summary|Possible HPET timer panic |callout struture corruption
20 matches
Mail list logo
