From: "Michael S. Tsirkin" <mst@redhat.com>
To: Ivan <ivan@prestigetransportation.com>
Cc: "David S. Miller" <davem@davemloft.net>,
virtualization@lists.linux-foundation.org,
Willem de Bruijn <willemb@google.com>
Subject: Re: PROBLEM: virtio_net LRO kernel panics
Date: Fri, 23 Jul 2021 03:59:47 -0400 [thread overview]
Message-ID: <20210723035713-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <CACFia2eH3eCZxtt70LB5zoPbhLXRv=crPh5oOhR=6mY3auDdQA@mail.gmail.com>
On Thu, Jul 22, 2021 at 11:50:11PM -0500, Ivan wrote:
> On Thu, Jul 22, 2021 at 11:25 PM Jason Wang <jasowang@redhat.com> wrote:
> > 在 2021/7/23 上午10:54, Ivan 写道:
> > > On Thu, Jul 22, 2021 at 9:37 PM Jason Wang <jasowang@redhat.com> wrote:
> > >> Does it work if you turn off lro before enabling the forwarding?
> > > 0 root@NuRaid:~# ethtool -K eth0 lro off
> > > Actual changes:
> > > rx-lro: on [requested off]
> > > Could not change any device features
> >
> > Ok, it looks like the device misses the VIRTIO_NET_F_CTRL_GUEST_OFFLOADS
> > which makes it impossible to change the LRO setting.
> >
> > Did you use qemu? If yes, what's the qemu version you've used?
>
> These are VirtualBox machines, which I've been using for years with
> longterm kernels 4.19, and I never had such a problem. But now that I
> tried upgrading to kernels 5.10 or 5.13 -- the panics started. These
> are just generic kernel builds, and a minimalistic userspace.
I would be useful to see the features your virtualbox instance provides
cat /sys/class/net/eth0/device/features
replacing eth0 with device name as appropriate
--
MST
_______________________________________________
Virtualization mailing list
Virtualization@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/virtualization
next prev parent reply other threads:[~2021-07-23 8:00 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CACFia2dwacaVVYD+1uG=CDGaJqdCOSBvZ5FcXp04caecaWAY3w@mail.gmail.com>
2021-07-23 1:28 ` PROBLEM: virtio_net LRO kernel panics Tonghao Zhang
[not found] ` <CACFia2fDZHUZB5wJ7LK8M2sv_+W58rHw0NzzrwPPoX9=s7yPdQ@mail.gmail.com>
2021-07-23 2:37 ` Jason Wang
[not found] ` <CACFia2eLCJuy=w1r20691s_cSYkBkPaY-Dbd-9CkrcpSAe7z6g@mail.gmail.com>
2021-07-23 4:25 ` Jason Wang
[not found] ` <CACFia2eH3eCZxtt70LB5zoPbhLXRv=crPh5oOhR=6mY3auDdQA@mail.gmail.com>
2021-07-23 7:59 ` Michael S. Tsirkin [this message]
[not found] ` <CACFia2fWhWKMGF3g8SfU++2-jQ1rCKtCJo3h08KmhGfMTuZaQQ@mail.gmail.com>
2021-07-23 8:13 ` Michael S. Tsirkin
2021-07-23 12:10 ` Michael S. Tsirkin
[not found] ` <CACFia2en0JJDFyz3Umk-JTnMT=kjvRogt4PudED4kiLeMjcHFg@mail.gmail.com>
[not found] ` <CACFia2fx7Lt-4o_uqDznvk-VgdsMtD64qv6RYkrCjKLu2yt8bg@mail.gmail.com>
[not found] ` <CACFia2eUi4KNRC7MYktzUS9Nq2WcBiesX04Tbn2pTuvuGkY4qA@mail.gmail.com>
[not found] ` <CACFia2dns1rTe5OQj4H-kpurVm2CTtGfAXz0aOUS0_cs0QUrsA@mail.gmail.com>
2021-07-27 9:11 ` Michael S. Tsirkin
[not found] ` <CACFia2dLp19pzJsScSvVYREpQm0n6XCWLieWXzA94=OVYVHTbw@mail.gmail.com>
2021-08-02 19:51 ` Michael S. Tsirkin
[not found] ` <CACFia2f8xmOwB69Cj+OUNobNSurVnrLrJFdrxnmurww9aSzJMw@mail.gmail.com>
2021-08-10 15:31 ` Michael S. Tsirkin
2021-08-11 3:38 ` Jason Wang
2021-08-11 7:39 ` Michael S. Tsirkin
2021-08-11 7:45 ` Jason Wang
2021-08-11 8:01 ` Michael S. Tsirkin
2021-08-11 8:17 ` Jason Wang
[not found] ` <CACFia2fYQG4Y3_ffym06C1HGrOiOS38YWxuoUu4HYorwS9qOjA@mail.gmail.com>
2021-07-23 8:59 ` Michael S. Tsirkin
2021-07-30 11:42 ` Michael S. Tsirkin
2021-07-30 11:42 ` Michael S. Tsirkin
2021-07-30 17:04 ` Ivan
2021-07-31 20:53 ` Michael S. Tsirkin
2021-07-31 20:53 ` Michael S. Tsirkin
2021-07-31 23:52 ` Ivan
2021-08-02 4:35 ` Jason Wang
2021-08-02 4:35 ` Jason Wang
2021-08-02 18:16 ` Ivan
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=20210723035713-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=davem@davemloft.net \
--cc=ivan@prestigetransportation.com \
--cc=virtualization@lists.linux-foundation.org \
--cc=willemb@google.com \
/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.