Thomas D.
2015-Oct-01 13:36 UTC
req->nr_phys_segments > queue_max_segments (was Re: kernel BUG at drivers/block/virtio_blk.c:172!)
Hi, Mike Snitzer wrote:> This particular dm-crypt on virtio-blk issue is fixed with this commit: > http://git.kernel.org/linus/586b286b110e94eb31840ac5afc0c24e0881fe34 > > Linus pulled this into v4.3-rc3.I have this patch applied to linux-4.1.9. This could be the reason why I don't see the issue on boot with linux-4.1.9. So is the freeze I am experiencing with linux-4.1.9 another issue introduced with linux-4.1.9 or another symptom/regression? Any idea? -Thomas
Thomas D.
2015-Oct-01 15:35 UTC
req->nr_phys_segments > queue_max_segments (was Re: kernel BUG at drivers/block/virtio_blk.c:172!)
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
Thomas D.
2015-Oct-01 16:06 UTC
req->nr_phys_segments > queue_max_segments (was Re: kernel BUG at drivers/block/virtio_blk.c:172!)
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.I already experienced one freeze with linux-4.1.8 and Mike's patch (same like in 4.1.9). Doesn't mean that this is related to Mike's patch (I see the same freezes with vanilla 4.1.9 not containing the patch with a higher frequency). -Thomas
Seemingly Similar Threads
- req->nr_phys_segments > queue_max_segments (was Re: kernel BUG at drivers/block/virtio_blk.c:172!)
- req->nr_phys_segments > queue_max_segments (was Re: kernel BUG at drivers/block/virtio_blk.c:172!)
- req->nr_phys_segments > queue_max_segments (was Re: kernel BUG at drivers/block/virtio_blk.c:172!)
- req->nr_phys_segments > queue_max_segments (was Re: kernel BUG at drivers/block/virtio_blk.c:172!)
- req->nr_phys_segments > queue_max_segments (was Re: kernel BUG at drivers/block/virtio_blk.c:172!)