From: Andres Freund <andres@anarazel.de>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: Xuan Zhuo <xuanzhuo@linux.alibaba.com>,
Linus Torvalds <torvalds@linux-foundation.org>,
kvm@vger.kernel.org, virtualization@lists.linux-foundation.org,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
alvaro.karsz@solid-run.com, colin.i.king@gmail.com,
colin.king@intel.com, dan.carpenter@oracle.com, david@redhat.com,
elic@nvidia.com, eperezma@redhat.com, gautam.dawar@xilinx.com,
gshan@redhat.com, hdegoede@redhat.com, hulkci@huawei.com,
jasowang@redhat.com, jiaming@nfschina.com,
kangjie.xu@linux.alibaba.com, lingshan.zhu@intel.com,
liubo03@inspur.com, michael.christie@oracle.com,
pankaj.gupta@amd.com, peng.fan@nxp.com, quic_mingxue@quicinc.com,
robin.murphy@arm.com, sgarzare@redhat.com,
suwan.kim027@gmail.com, syoshida@redhat.com,
xieyongji@bytedance.com, xuqiang36@huawei.com
Subject: Re: [GIT PULL] virtio: fatures, fixes
Date: Sun, 14 Aug 2022 12:40:31 -0700 [thread overview]
Message-ID: <20220814194031.ciql3slc5c34ayjw@awork3.anarazel.de> (raw)
In-Reply-To: <20220814045853-mutt-send-email-mst@kernel.org>
Hi,
On 2022-08-14 04:59:48 -0400, Michael S. Tsirkin wrote:
> On Sat, Aug 13, 2022 at 09:39:06PM -0700, Andres Freund wrote:
> > Hi,
> >
> > On 2022-08-13 20:52:39 -0700, Andres Freund wrote:
> > > Is there specific information you'd like from the VM? I just recreated the
> > > problem and can extract.
> >
> > Actually, after reproducing I seem to now hit a likely different issue. I
> > guess I should have checked exactly the revision I had a problem with earlier,
> > rather than doing a git pull (up to aea23e7c464b)
>
> Looks like there's a generic memory corruption so it crashes
> in random places.
Either a generic memory corruption, or something wrong with IO.
> Would bisect be possible for you?
I'll give it a go.
Greetings,
Andres Freund
WARNING: multiple messages have this Message-ID (diff)
From: Andres Freund <andres@anarazel.de>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: peng.fan@nxp.com, kvm@vger.kernel.org,
alvaro.karsz@solid-run.com,
virtualization@lists.linux-foundation.org,
quic_mingxue@quicinc.com, syoshida@redhat.com, elic@nvidia.com,
eperezma@redhat.com, jiaming@nfschina.com, hulkci@huawei.com,
liubo03@inspur.com, dan.carpenter@oracle.com,
kangjie.xu@linux.alibaba.com, robin.murphy@arm.com,
hdegoede@redhat.com, pankaj.gupta@amd.com,
gautam.dawar@xilinx.com, suwan.kim027@gmail.com,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
xuqiang36@huawei.com, xieyongji@bytedance.com,
colin.i.king@gmail.com, lingshan.zhu@intel.com,
colin.king@intel.com,
Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: [GIT PULL] virtio: fatures, fixes
Date: Sun, 14 Aug 2022 12:40:31 -0700 [thread overview]
Message-ID: <20220814194031.ciql3slc5c34ayjw@awork3.anarazel.de> (raw)
In-Reply-To: <20220814045853-mutt-send-email-mst@kernel.org>
Hi,
On 2022-08-14 04:59:48 -0400, Michael S. Tsirkin wrote:
> On Sat, Aug 13, 2022 at 09:39:06PM -0700, Andres Freund wrote:
> > Hi,
> >
> > On 2022-08-13 20:52:39 -0700, Andres Freund wrote:
> > > Is there specific information you'd like from the VM? I just recreated the
> > > problem and can extract.
> >
> > Actually, after reproducing I seem to now hit a likely different issue. I
> > guess I should have checked exactly the revision I had a problem with earlier,
> > rather than doing a git pull (up to aea23e7c464b)
>
> Looks like there's a generic memory corruption so it crashes
> in random places.
Either a generic memory corruption, or something wrong with IO.
> Would bisect be possible for you?
I'll give it a go.
Greetings,
Andres Freund
_______________________________________________
Virtualization mailing list
Virtualization@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/virtualization
next prev parent reply other threads:[~2022-08-14 19:40 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-12 15:42 [GIT PULL] virtio: fatures, fixes Michael S. Tsirkin
2022-08-12 15:42 ` Michael S. Tsirkin
2022-08-12 16:59 ` pr-tracker-bot
2022-08-12 16:59 ` pr-tracker-bot
2022-08-14 0:45 ` Andres Freund
2022-08-14 0:45 ` Andres Freund
2022-08-14 1:50 ` Xuan Zhuo
2022-08-14 1:50 ` Xuan Zhuo
2022-08-14 3:52 ` Andres Freund
2022-08-14 3:52 ` Andres Freund
2022-08-14 4:39 ` Andres Freund
2022-08-14 4:39 ` Andres Freund
2022-08-14 8:59 ` Michael S. Tsirkin
2022-08-14 8:59 ` Michael S. Tsirkin
2022-08-14 19:40 ` Andres Freund [this message]
2022-08-14 19:40 ` Andres Freund
2022-08-15 7:02 ` Andres Freund
2022-08-15 7:02 ` Andres Freund
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=20220814194031.ciql3slc5c34ayjw@awork3.anarazel.de \
--to=andres@anarazel.de \
--cc=alvaro.karsz@solid-run.com \
--cc=colin.i.king@gmail.com \
--cc=colin.king@intel.com \
--cc=dan.carpenter@oracle.com \
--cc=david@redhat.com \
--cc=elic@nvidia.com \
--cc=eperezma@redhat.com \
--cc=gautam.dawar@xilinx.com \
--cc=gshan@redhat.com \
--cc=hdegoede@redhat.com \
--cc=hulkci@huawei.com \
--cc=jasowang@redhat.com \
--cc=jiaming@nfschina.com \
--cc=kangjie.xu@linux.alibaba.com \
--cc=kvm@vger.kernel.org \
--cc=lingshan.zhu@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=liubo03@inspur.com \
--cc=michael.christie@oracle.com \
--cc=mst@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=pankaj.gupta@amd.com \
--cc=peng.fan@nxp.com \
--cc=quic_mingxue@quicinc.com \
--cc=robin.murphy@arm.com \
--cc=sgarzare@redhat.com \
--cc=suwan.kim027@gmail.com \
--cc=syoshida@redhat.com \
--cc=torvalds@linux-foundation.org \
--cc=virtualization@lists.linux-foundation.org \
--cc=xieyongji@bytedance.com \
--cc=xuanzhuo@linux.alibaba.com \
--cc=xuqiang36@huawei.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.