From: "G.R." <firemeteor@users.sourceforge.net>
To: "Roger Pau Monné" <roger.pau@citrix.com>
Cc: xen-devel <xen-devel@lists.xen.org>
Subject: Re: Possible bug? DOM-U network stopped working after fatal error reported in DOM0
Date: Thu, 23 Dec 2021 23:49:08 +0800 [thread overview]
Message-ID: <CAKhsbWZMRMfrsWDcZLSS7q4ciR0UbyGE2sO-tN1dr+9juuEfsQ@mail.gmail.com> (raw)
In-Reply-To: <YcInKtCNgA9v0k+c@Air-de-Roger>
On Wed, Dec 22, 2021 at 3:13 AM Roger Pau Monné <roger.pau@citrix.com> wrote:
> Could you build a debug kernel with the following patch applied and
> give me the trace when it explodes?
Please find the trace and the kernel CL below.
Note, the domU get stuck into a bootloop with this assertion as the
situation will come back after domU restart and only dom0 reboot can
get the situation back to normal.
The trace I captured below is within the boot loop. I suspect the
initial trigger may look different. Will give it another try soon.
FreeBSD 12.2-RELEASE-p11 #0 c8625d629c3(truenas/12.0-stable)-dirty:
Wed Dec 22 20:26:46 UTC 2021
The repo is here: https://github.com/freenas/os.git
db:0:kdb.enter.default> bt
Tracing pid 0 tid 101637 td 0xfffff80069cc4000
kdb_enter() at kdb_enter+0x37/frame 0xfffffe009f121460
vpanic() at vpanic+0x197/frame 0xfffffe009f1214b0
panic() at panic+0x43/frame 0xfffffe009f121510
xn_txq_mq_start_locked() at xn_txq_mq_start_locked+0x4c6/frame
0xfffffe009f121580
xn_txq_mq_start() at xn_txq_mq_start+0x84/frame 0xfffffe009f1215b0
ether_output_frame() at ether_output_frame+0xb4/frame 0xfffffe009f1215e0
ether_output() at ether_output+0x6a5/frame 0xfffffe009f121680
ip_output() at ip_output+0x1319/frame 0xfffffe009f1217e0
tcp_output() at tcp_output+0x1dbf/frame 0xfffffe009f121980
tcp_usr_send() at tcp_usr_send+0x3c9/frame 0xfffffe009f121a40
sosend_generic() at sosend_generic+0x440/frame 0xfffffe009f121af0
sosend() at sosend+0x66/frame 0xfffffe009f121b20
icl_send_thread() at icl_send_thread+0x44e/frame 0xfffffe009f121bb0
fork_exit() at fork_exit+0x80/frame 0xfffffe009f121bf0
fork_trampoline() at fork_trampoline+0xe/frame 0xfffffe009f121bf0
next prev parent reply other threads:[~2021-12-23 15:49 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-18 18:35 Possible bug? DOM-U network stopped working after fatal error reported in DOM0 G.R.
2021-12-19 6:10 ` Juergen Gross
2021-12-19 17:31 ` G.R.
2021-12-20 17:13 ` G.R.
2021-12-21 13:50 ` Roger Pau Monné
2021-12-21 18:19 ` G.R.
2021-12-21 19:12 ` Roger Pau Monné
2021-12-23 15:49 ` G.R. [this message]
2021-12-24 11:24 ` Roger Pau Monné
2021-12-25 16:39 ` G.R.
2021-12-25 18:06 ` G.R.
2021-12-27 19:04 ` Roger Pau Monné
[not found] ` <CAKhsbWY5=vENgwgq3NV44KSZQgpOPY=33CMSZo=jweAcRDjBwg@mail.gmail.com>
2021-12-29 8:32 ` Roger Pau Monné
2021-12-29 9:13 ` G.R.
2021-12-29 10:27 ` Roger Pau Monné
2021-12-29 19:07 ` Roger Pau Monné
2021-12-30 15:12 ` G.R.
2021-12-30 18:51 ` Roger Pau Monné
2021-12-31 14:47 ` G.R.
2022-01-04 10:25 ` Roger Pau Monné
2022-01-04 16:05 ` G.R.
2022-01-05 14:33 ` Roger Pau Monné
2022-01-07 17:14 ` G.R.
2022-01-10 14:53 ` Roger Pau Monné
2022-01-11 14:24 ` G.R.
2022-10-30 16:36 ` G.R.
2022-11-03 6:58 ` Paul Leiber
2022-11-03 12:22 ` Roger Pau Monné
2022-12-14 6:16 ` G.R.
2024-01-09 11:13 ` Niklas Hallqvist
2024-01-09 13:53 ` Roger Pau Monné
2024-01-19 15:51 ` G.R.
2021-12-20 13:51 ` Roger Pau Monné
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAKhsbWZMRMfrsWDcZLSS7q4ciR0UbyGE2sO-tN1dr+9juuEfsQ@mail.gmail.com \
--to=firemeteor@users.sourceforge.net \
--cc=roger.pau@citrix.com \
--cc=xen-devel@lists.xen.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.