From: "Thomas D." <whissi@whissi.de>
To: Mike Snitzer <snitzer@redhat.com>, Hannes Reinecke <hare@suse.de>
Cc: "Michael S. Tsirkin" <mst@redhat.com>,
Jens Axboe <axboe@kernel.dk>, Christoph Hellwig <hch@lst.de>,
"virtualization@lists.linux-foundation.org"
<virtualization@lists.linux-foundation.org>,
"linux-scsi@vger.kernel.org" <Linux-scsi@vger.kernel.org>
Subject: Re: req->nr_phys_segments > queue_max_segments (was Re: kernel BUG at drivers/block/virtio_blk.c:172!)
Date: Thu, 1 Oct 2015 17:35:58 +0200 [thread overview]
Message-ID: <560D52DE.3020303@whissi.de> (raw)
In-Reply-To: <560D36DC.5050205@whissi.de>
Hi,
seems like we have two problems:
The first (origin) problem seems to be already fixed by Mike's patch.
I applied the patch against linux-4.1.8, rebooted several times without
a problem. But I'll keep testing for sure.
The second problem is a new bug within linux-4.1.9: I experience the
> NMI watchdog: BUG: soft lockup - CPU#3 stuck for 23s!
freeze now on all my systems (virtual machines *and* physical systems;
Gentoo boxes, Debian boxes, with and without dm (LUKS), with XFS or ext4
-- looks like a general problem). I will post it to LKML itself (I don't
have a trace about what's hanging).
Thanks for all your time and help!
-Thomas
next prev parent reply other threads:[~2015-10-01 15:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <560C87F6.4080708@whissi.de>
[not found] ` <20151001114817-mutt-send-email-mst@redhat.com>
2015-10-01 9:20 ` req->nr_phys_segments > queue_max_segments (was Re: kernel BUG at drivers/block/virtio_blk.c:172!) Hannes Reinecke
2015-10-01 13:09 ` Mike Snitzer
2015-10-01 13:36 ` Thomas D.
2015-10-01 15:35 ` Thomas D. [this message]
2015-10-01 16:06 ` Thomas D.
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=560D52DE.3020303@whissi.de \
--to=whissi@whissi.de \
--cc=Linux-scsi@vger.kernel.org \
--cc=axboe@kernel.dk \
--cc=hare@suse.de \
--cc=hch@lst.de \
--cc=mst@redhat.com \
--cc=snitzer@redhat.com \
--cc=virtualization@lists.linux-foundation.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox