Probably should have cc'd virtualization@xxxxxxxxxxxxxxxxxxxxxxxxxx too. On Fri, May 26, 2017 at 11:08:39AM -0400, bfields@xxxxxxxxxxxx wrote: > On Tue, May 23, 2017 at 08:23:34AM -0400, bfields@xxxxxxxxxxxx wrote: > > Unfortunately I can't get anything through testing. It's not your > > patches, it's something in -rc1. My server VM stops responding to > > any network traffic randomly in the middle of a run. If I log in from a > > serial console, I see the interface is up and everything looks OK. I > > haven't had the chance to do much more, and I'm not sure where to > > start.... I started a git-bisect attempt, but there are several > > unrelated problems, and I'm not sure this one is 100% reproduceable. > > It looks like it may be due to something pulled in with virtio updates. > I've reproduced the problem on c8b0d7290657 "s390/virtio: change > maintainership" but not on v4.11. Are there any known issues with those > commits? > > I've just been doing this long-running bisect while working on other > stuff. My reproducer (basically just running a bunch of NFS > connectathon tests over a variety of protocol versions and security > flavors) doesn't hit the bug reliably, and I've had to restart a couple > times probably due to false negatives. But this looks pretty promising, > and there's only 17 commits in that range, so I'll keep bisecting. > > --b. -- To unsubscribe from this list: send the line "unsubscribe linux-nfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
