https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=260393
Andrey V. Elsukov changed:
What|Removed |Added
See Also||https://bugs.freebsd.org/bu
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=260393
--- Comment #92 from Dobri Dobrev ---
(In reply to Michael Tuexen from comment #91)
I hadn't had a chance to update to the latest stable/13.
Just got a crash after 112 days uptime on stable/13-n248590-b7da472979a
Here's what kgdb shows:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=260393
--- Comment #91 from Michael Tuexen ---
(In reply to Dobri Dobrev from comment #89)
OK, I MFCed all relevant changes I wanted to MFC. It would be great if you
could update a machine to stable/13, test it, and report the outcome of the
test.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=260393
--- Comment #90 from Michael Tuexen ---
(In reply to Dobri Dobrev from comment #89)
I would suggest the following:
1. During this week I will MFC all TCP related changes to stable/13, which I
think should go into 13.1. I'll ping you when
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=260393
--- Comment #89 from Dobri Dobrev ---
(In reply to Michael Tuexen from comment #88)
I don't suppose there's anything new regarding this issue?
I could do a separate 13-stable install, place some traffic and see if it'd
crash again, howeve
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=260393
--- Comment #88 from Michael Tuexen ---
(In reply to Dobri Dobrev from comment #87)
I tried to trigger a panic on a local system using packetdrill scripts, but
were not able to to this. So without being able to reproduce this in a system I
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=260393
--- Comment #87 from Dobri Dobrev ---
(In reply to Gleb Smirnoff from comment #86)
The problem is ... I switched to -release. On -stable it crashed very
frequently resulting in disruptions of customer traffic, which is something I'd
like t
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=260393
--- Comment #86 from Gleb Smirnoff ---
Yes, full dump would be exactly size of your physical RAM. There are two ways
two check: search the dump file for a sample of the data you are concerned to
leak, or open the dump in kgdb, find the proc
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=260393
--- Comment #85 from Dobri Dobrev ---
(In reply to Gleb Smirnoff from comment #83)
Also, how can I check to confirm no actual binaries don't exist in the dump?
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=260393
--- Comment #84 from Dobri Dobrev ---
(In reply to Gleb Smirnoff from comment #83)
>From what I remember the crash dump files were ~3.5-3.6 GB. Does that
correspond to a minidump crash size?
--
You are receiving this mail because:
You ar
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=260393
Gleb Smirnoff changed:
What|Removed |Added
CC||gleb...@freebsd.org
--- Comment #8
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=260393
--- Comment #82 from Dobri Dobrev ---
(In reply to Hans Petter Selasky from comment #81)
Here are the modules loaded on both Stable and Release:
13-Stable:
Id Refs AddressSize Name
1 36 0x8020 1f2a788 kerne
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=260393
--- Comment #81 from Hans Petter Selasky ---
Are you loading any modules from /boot/modules, typically installed from ports,
which access the network? Just curious.
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=260393
--- Comment #80 from Dobri Dobrev ---
(In reply to Michael Tuexen from comment #79)
Btw, I moved over to -release, no issues there.
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=260393
--- Comment #79 from Michael Tuexen ---
(In reply to Dobri Dobrev from comment #78)
Not yet. I'll bring it up at the transport telco on next Thursday.
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=260393
--- Comment #78 from Dobri Dobrev ---
(In reply to Michael Tuexen from comment #77)
Any news?
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=260393
--- Comment #77 from Michael Tuexen ---
(In reply to Dobri Dobrev from comment #76)
Not right now from my side. Will setup a local test system an explore a couple
of packetflows...
--
You are receiving this mail because:
You are the assig
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=260393
--- Comment #76 from Dobri Dobrev ---
Anything more from the dump, or, potential fix to test on the server?
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=260393
--- Comment #75 from Dobri Dobrev ---
(In reply to Hans Petter Selasky from comment #74)
>From frame 14:
(kgdb) print /x *(int *)0xfe017fd6282c
$8 = 0x264
(kgdb)
--
You are receiving this mail because:
You are the assignee for the b
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=260393
--- Comment #74 from Hans Petter Selasky ---
And this one:
print /x *(int *)0xfe017fd6282c
--HPS
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=260393
--- Comment #73 from Dobri Dobrev ---
(In reply to Hans Petter Selasky from comment #72)
(kgdb) frame 14
#14 0x80e0607a in tcp_do_segment (m=,
th=0xf80bc659e87a, so=, tp=0xfe0252e24000,
drop_hdrlen=40, tlen=, iptos=0 '\000'
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=260393
--- Comment #72 from Hans Petter Selasky ---
And also:
frame 14
print /x *(tp->t_inpcb->inp_socket->so_snd.sb_mb)
This dumps the faulty mbuf. I see that so_snd reports bytes available, let's
see if that matches the mbuf:
sb_acc = 0x7cf,
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=260393
--- Comment #71 from Dobri Dobrev ---
(In reply to Hans Petter Selasky from comment #70)
(kgdb) frame 14
#14 0x80e0607a in tcp_do_segment (m=,
th=0xf80bc659e87a, so=, tp=0xfe0252e24000,
drop_hdrlen=40, tlen=, iptos=0 '\000'
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=260393
--- Comment #70 from Hans Petter Selasky ---
Could you also get:
frame 14
print /x *(tp->t_inpcb)
print /x *(tp->t_inpcb->inp_socket)
--HPS
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=260393
--- Comment #69 from Dobri Dobrev ---
(In reply to Michael Tuexen from comment #68)
Same. Let's continue tomorrow.
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=260393
--- Comment #68 from Michael Tuexen ---
Thanks. Need to think when I'm more awake than now...
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=260393
--- Comment #67 from Dobri Dobrev ---
(In reply to Michael Tuexen from comment #66)
(kgdb) frame 12
#12 0x80e11a3b in tcp_m_copym (m=0x0, m@entry=0xf80bc680b500,
off0=1388, plen=, plen@entry=0xfe017fd6282c, seglimit=1,
segl
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=260393
--- Comment #66 from Michael Tuexen ---
That was fast...
Let's start with:
frame 12
print *(struct mbuf *)0xf80bc680b500
print *(int32_t *)0xfe017fd6282c
frame 14
print *th
print *tp
--
You are receiving this mail because:
You a
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=260393
--- Comment #65 from Dobri Dobrev ---
(In reply to Hans Petter Selasky from comment #63)
So, here it is - I believe this is what we're looking for: "panic: tcp_m_copym,
length > size of mbuf chain"
Unread portion of the kernel message buf
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=260393
--- Comment #64 from Dobri Dobrev ---
(In reply to Hans Petter Selasky from comment #63)
I already installed the new kernel and cleaned all the old dumps (there wasn't
much space left in /).
I'll extract everything again after the next cr
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=260393
--- Comment #63 from Hans Petter Selasky ---
It could also be interesting to see the socket state, especially so_snd:
Can you try this:
frame 10
print /x *(tp->t_inpcb->inp_socket)
--HPS
--
You are receiving this mail because:
You are
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=260393
--- Comment #62 from Dobri Dobrev ---
(In reply to Michael Tuexen from comment #61)
Running stable/13-n248688-ecb7f44be90, waiting for a crash.
So far the invariants don't cause issues.
--
You are receiving this mail because:
You are the
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=260393
--- Comment #61 from Michael Tuexen ---
(In reply to Dobri Dobrev from comment #60)
Thats OK. Lets see what happens.
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=260393
--- Comment #60 from Dobri Dobrev ---
(In reply to Hans Petter Selasky from comment #59)
SACK is enabled.
I'm rebuilding the latest available stable/13 kernel with invariants.
When it crashes - I'll start providing data.
Hopefully the sl
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=260393
--- Comment #59 from Hans Petter Selasky ---
Hi Dobri,
Can you confirm that SACK is enabled?
sysctl net.inet.tcp.sack.enable
--HPS
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=260393
--- Comment #58 from Michael Tuexen ---
(In reply to Dobri Dobrev from comment #57)
1. During runtime it is slower, since it does additional checking.
2. Downtime is the same.
--
You are receiving this mail because:
You are the assignee f
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=260393
--- Comment #57 from Dobri Dobrev ---
(In reply to Michael Tuexen from comment #56)
I can build the kernel with invariants, however...
1. During runtime - is there a noticeable slowdown or anything that would
otherwise interfere with prod
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=260393
--- Comment #56 from Michael Tuexen ---
Let us try to use a kernel build with INVARIANTS, let it crash and look at the
core. Don't update the system while we are doing this. And let us focus on one
system and one crash at a time.
--
You a
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=260393
--- Comment #55 from Dobri Dobrev ---
(In reply to Hans Petter Selasky from comment #54)
So, Do I hold off installing the kernel/world that I've build today, or install
it, wait for a crash and extract new data?
--
You are receiving this
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=260393
--- Comment #54 from Hans Petter Selasky ---
Let's use the updated machine for now and follow Michael's thread.
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=260393
--- Comment #53 from Dobri Dobrev ---
(In reply to Hans Petter Selasky from comment #52)
Hello,
The sbdrop() only appeared once on 1 of the servers, I've since then updated
the kernel there, and have not extracted core dumps / etc from th
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=260393
--- Comment #52 from Hans Petter Selasky ---
Hi,
There appears to be multiple dumps with different issues!
Decoding the thread name from the last printout you provided:
td_name = {0x69, 0x66, 0x5f, 0x69, 0x6f, 0x5f, 0x74, 0x71, 0x67, 0x5
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=260393
--- Comment #51 from Dobri Dobrev ---
(In reply to Hans Petter Selasky from comment #50)
(kgdb) frame 10
#10 0x80dcd382 in tcp_do_segment (m=, th=, so=, tp=0xfe0251638870, drop_hdrlen=40,
tlen=, iptos=0 '\000') at /usr/src/sys/
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=260393
--- Comment #50 from Hans Petter Selasky ---
Then see if you can get this working:
frame 10
print /x *(struct thread *)(tp->t_inpcb->inp_lock.rw_lock)
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=260393
--- Comment #49 from Hans Petter Selasky ---
Then see if you can get this working:
frame 10
print /x *(struct thread *)tp->t_inpcb.inp_lock.rw_lock
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=260393
--- Comment #48 from Dobri Dobrev ---
(In reply to Hans Petter Selasky from comment #47)
Here is from frame 10:
(kgdb) frame 10
#10 0x80dcd382 in tcp_do_segment (m=, th=, so=, tp=0xfe0251638870, drop_hdrlen=40,
tlen=, iptos=0
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=260393
--- Comment #47 from Hans Petter Selasky ---
Try instead:
frame 10
print /x *tp->t_inpcb
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=260393
--- Comment #46 from Dobri Dobrev ---
(In reply to Hans Petter Selasky from comment #44)
Here is from frame 9:
(kgdb) frame 9
#9 0x80dd5fa9 in tcp_output (tp=) at
/usr/src/sys/netinet/tcp_output.c:1081
warning: Source file is more
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=260393
--- Comment #45 from Dobri Dobrev ---
(In reply to Hans Petter Selasky from comment #44)
(kgdb) where
#0 __curthread () at /usr/src/sys/amd64/include/pcpu_aux.h:55
#1 doadump (textdump=) at /usr/src/sys/kern/kern_shutdown.c:399
#2 0xfff
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=260393
--- Comment #44 from Hans Petter Selasky ---
(kgdb) frame 8
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=260393
--- Comment #43 from Dobri Dobrev ---
(In reply to Hans Petter Selasky from comment #42)
>From which frame ?
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=260393
--- Comment #42 from Hans Petter Selasky ---
Could you dump the INPCB aswell:
print /x *tp->t_inpcb
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=260393
--- Comment #41 from Hans Petter Selasky ---
I note that in order to reach the sbdrop() where we panic happens we need to
pass:
if (tp->t_state == TCPS_ESTABLISHED)
But:
tp->t_state = 8 (TCPS_LAST_ACK)
So that means there is a race some
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=260393
--- Comment #40 from Hans Petter Selasky ---
Might be you need to:
make toolchain
first.
--HPS
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=260393
--- Comment #39 from Dobri Dobrev ---
(In reply to Michael Tuexen from comment #34)
for some reason I'm unable to build world/kernel on older revisions due to "ld:
error: /usr/obj/usr/src/amd64.amd64/tmp/lib/libc.so.7: undefined reference t
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=260393
--- Comment #38 from Dobri Dobrev ---
(In reply to Hans Petter Selasky from comment #37)
The thing is... when did something in regards to this got changed?
Had to have happened between 12.2 and 13 at some point.. if we can find the
actual
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=260393
Hans Petter Selasky changed:
What|Removed |Added
CC||hsela...@freebsd.org
--- Com
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=260393
--- Comment #36 from Hans Petter Selasky ---
Hi,
I wonder if we need to subtract 1 from tp->snd_max, when TF_SENTFIN is set?
t_state = 8
#define TCPS_LAST_ACK 8 /* had fin and close; await FIN ACK */
t_flags = 554697333
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=260393
--- Comment #35 from Dobri Dobrev ---
(In reply to Michael Tuexen from comment #34)
I'll rebuild the kernel with these when I find which commit actually causes the
problem (I suspect these options will slow down the system somewhat)
--
Y
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=260393
--- Comment #34 from Michael Tuexen ---
Add to the kernel config file GENERIC
options BUF_TRACKING# Track buffer history
options DDB # Support DDB.
options FULL_BUF_TRACKING # T
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=260393
--- Comment #33 from Dobri Dobrev ---
(In reply to Michael Tuexen from comment #32)
Let me know what "INVARIANTS" are and how to build the kernel with it.
I'm building the "GENERIC" config.
--
You are receiving this mail because:
You ar
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=260393
--- Comment #32 from Michael Tuexen ---
(In reply to Dobri Dobrev from comment #31)
Are you using a kernel build with INVARIANTS? If not, you might want to do that
first. Maybe that gives a hint, because it might panic sooner...
--
You ar
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=260393
--- Comment #31 from Dobri Dobrev ---
(In reply to Michael Tuexen from comment #29)
I'm building d04c12765cfa2bf0f33f7489d48843648073ce06, will test it for few
days.
--
You are receiving this mail because:
You are the assignee for the bu
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=260393
--- Comment #30 from Dobri Dobrev ---
(In reply to Michael Tuexen from comment #29)
Few days.
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=260393
--- Comment #29 from Michael Tuexen ---
Great, thanks. How long does it take for a machine to panic?
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=260393
--- Comment #28 from Dobri Dobrev ---
(In reply to Michael Tuexen from comment #27)
I'll try to do that sometime tomorrow, and let you know.
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=260393
--- Comment #27 from Michael Tuexen ---
(In reply to Dobri Dobrev from comment #26)
I actually don't know which version you should try. But you might pick some
older version, give it a try and to some binary search. It would help to know
wh
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=260393
--- Comment #26 from Dobri Dobrev ---
(In reply to Michael Tuexen from comment #25)
If you wish, I can test an earlier revision of 13/stable, before changes to
these files (noticed you did some commits changing several of the files listed
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=260393
--- Comment #25 from Michael Tuexen ---
(In reply to Dobri Dobrev from comment #24)
The point I had in mind was to exclude pf from the system to be sure it is a
TCP problem. But that does not seem to be possible. Thanks for the feedback.
Wi
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=260393
--- Comment #24 from Dobri Dobrev ---
(In reply to Michael Tuexen from comment #23)
Unfortunately PF is essential, I cannot disable it.
To answer a question you might be having - yes, I tested without the PF patch
before I made the bug su
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=260393
--- Comment #23 from Michael Tuexen ---
(In reply to Dobri Dobrev from comment #22)
I'm not interested in testing 13-release. But I would be interested if the
problem also shows up if you don't use pf. Is that possible?
--
You are receivi
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=260393
--- Comment #22 from Dobri Dobrev ---
I'm only having 1 patch to pf_table.c (3-4 lines in total, nothing major) that
also works w/o any issues on 12.2, and from what I can see in the dump - pf is
not related to the crash.
I'll be willing t
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=260393
--- Comment #21 from Dobri Dobrev ---
(In reply to Michael Tuexen from comment #20)
I'm using the exact same settings on 12.2 w/o problems.
Most of the loader/sysctl are calomel defaults with maybe 2-3 settings changed
in total.
Traffic
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=260393
--- Comment #20 from Michael Tuexen ---
(In reply to Dobri Dobrev from comment #19)
Thanks. Right now I'm trying to figure out what could be going on.
Are you using anything non-default? Alternate CC module? Alternate stack? Are
you using
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=260393
--- Comment #19 from Dobri Dobrev ---
(In reply to Michael Tuexen from comment #17)
If something more is needed - I'll provide as quickly as possible.
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=260393
--- Comment #18 from Dobri Dobrev ---
(In reply to Michael Tuexen from comment #17)
(kgdb) frame 8
#8 m_copydata (m=0x0, m@entry=0xf8010ee80d00, off=0, len=1, cp=) at /usr/src/sys/kern/uipc_mbuf.c:657
657 count = m
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=260393
--- Comment #17 from Michael Tuexen ---
frame 8
print count
print m
print off
print len
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=260393
--- Comment #16 from Michael Tuexen ---
frame 8
print count
print m
print off
print len
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=260393
--- Comment #15 from Dobri Dobrev ---
(In reply to Michael Tuexen from comment #14)
(kgdb) frame 9
#9 0x80dd5fa9 in tcp_output (tp=) at
/usr/src/sys/netinet/tcp_output.c:1081
1081m_copydata(mb, moff, le
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=260393
--- Comment #14 from Michael Tuexen ---
frame 9
print mb
print *mb
print moff
print len
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=260393
--- Comment #13 from Dobri Dobrev ---
(In reply to Michael Tuexen from comment #12)
(kgdb) frame 12
#12 0x80dca9eb in tcp_input (mp=0xf8010ee80d00, offp=0x0, proto=1)
at /usr/src/sys/netinet/tcp_input.c:1496
1496ret
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=260393
--- Comment #12 from Michael Tuexen ---
(In reply to Michael Tuexen from comment #11)
Sorry, I meant:
frame 12
print *mp
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=260393
--- Comment #11 from Michael Tuexen ---
frame 12
print **mp
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=260393
--- Comment #10 from Dobri Dobrev ---
(In reply to Michael Tuexen from comment #9)
(kgdb) frame 8
#8 m_copydata (m=0x0, m@entry=0xf8010ee80d00, off=0, len=1, cp=) at /usr/src/sys/kern/uipc_mbuf.c:657
657 count = mi
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=260393
--- Comment #9 from Michael Tuexen ---
Please run
frame 8
list
print *(struct mbuf *)0xf8010ee80d00
frame 10
print *tp
frame 12
print **mp
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=260393
--- Comment #8 from Dobri Dobrev ---
(In reply to Michael Tuexen from comment #7)
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from /boot/kernel/kernel...
Reading symbols from /usr/
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=260393
--- Comment #7 from Michael Tuexen ---
(In reply to Dobri Dobrev from comment #6)
When you are at the debugger, you can type `dump` and `reboot` and the kernel
dump should be written to disk. After reboot, you can then use `sudo kgdb -c
/va
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=260393
--- Comment #6 from Dobri Dobrev ---
(In reply to Michael Tuexen from comment #5)
I updated to stable/13-n248590-b7da472979a, waiting to crash and will check the
dump.
--
You are receiving this mail because:
You are the assignee for the
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=260393
--- Comment #5 from Michael Tuexen ---
(In reply to Dobri Dobrev from comment #4)
The kernel dump most likely contains stuff you don't want to share... So could
you start kgdb with one of the cores and provide the output of `where`. If you
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=260393
--- Comment #4 from Dobri Dobrev ---
(In reply to Michael Tuexen from comment #3)
Depends.
How do you want to access it? Can I access it for you and provide the necessary
output? There is proprietary company software running on these serv
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=260393
Michael Tuexen changed:
What|Removed |Added
CC||tue...@freebsd.org
--- Comment #3
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=260393
--- Comment #2 from Dobri Dobrev ---
If any additional information is needed - let me know and I'll provide it.
The problem keeps happening once every 2-3 days, constantly, on both servers.
--
You are receiving this mail because:
You are
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=260393
Mark Linimon changed:
What|Removed |Added
Assignee|b...@freebsd.org|n...@freebsd.org
--
You are receiv
93 matches
Mail list logo
