Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1260914
| From | Chris Worley <chris.worley@primarydata.com> |
|---|---|
| Newsgroups | linux.kernel |
| Subject | Re: timer code oops when calling mod_delayed_work |
| Date | 2015-11-02 20:50 +0100 |
| Message-ID | <qqth7-VK-7@gated-at.bofh.it> (permalink) |
| References | (1 earlier) <qoZEt-3ix-1@gated-at.bofh.it> <qptMd-5iJ-1@gated-at.bofh.it> <qpCFP-2fo-11@gated-at.bofh.it> <qpM2u-82l-5@gated-at.bofh.it> <qpMlP-890-7@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
On Sat, Oct 31, 2015 at 11:54 AM, Jeff Layton <jlayton@poochiereds.net> wrote: > On Sat, 31 Oct 2015 17:31:07 -0400 > Tejun Heo <tj@kernel.org> wrote: ... >> >> > I have asked Chris and Michael to see if they can bisect it down, but >> > it may be a bit before they can get that done. Any insight you might >> > have in the meantime would helpful. >> >> Yeah, I'd love to find out how reproducible the issue is. If the >> problem is rarely reproducible, it might make sense to try >> instrumentation before trying bisection as it *could* be a latent bug >> which has been there all along and bisecting to the commit introducing >> the code wouldn't help us too much. >> > > It seems fairly reproducible, at least on v4.3-rc7 kernels: > > This came about when I asked them to perf test some nfsd patches that I > have queued up. I patched a Fedora 4.3-rc7 kernel and wanted to see > what the perf delta was (with NFSv3, fwiw): > > Patched kernels here: http://koji.fedoraproject.org/koji/taskinfo?taskID=11598089 > > Unpatched kernels here: http://koji.fedoraproject.org/koji/buildinfo?buildID=694377 > > Michael was using the SPEC SFS VDI workload to test, and was able to > get the same panic on both kernels. So it does seem to be reproducible. > It might even be possible to tune the VM to make the shrinker fire more > often, which may help tickle this more. > > In any case, I've asked them to try something v4.2-ish and see if it's > reproducible there, and then try v4.1 if it is. I figure anything > earlier is probably not worth testing if it still fails on v4.1. If it > turns out not to be reproducible on those earlier kernels then we can > bisect from there to track it down. The trick seems to be the NFS thread count: I initially though this was SFS/VDI specific, but when I ratcheted up the thread count to what Michael was using, 256 threads oopses on fio (throughput) benchmarks too. In bisecting kernels, it appeared between 4.2.3-200 and 4.2.5-200 (all the 4.2.4 kernels were bad). Jeff has a lead on this... Chris -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Back to linux.kernel | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
Re: timer code oops when calling mod_delayed_work Tejun Heo <tj@kernel.org> - 2015-10-31 22:40 +0100
Re: timer code oops when calling mod_delayed_work Jeff Layton <jlayton@poochiereds.net> - 2015-10-31 23:00 +0100
Re: timer code oops when calling mod_delayed_work Chris Worley <chris.worley@primarydata.com> - 2015-11-02 20:50 +0100
Re: timer code oops when calling mod_delayed_work Jeff Layton <jlayton@poochiereds.net> - 2015-11-02 21:00 +0100
Re: timer code oops when calling mod_delayed_work Jeff Layton <jlayton@poochiereds.net> - 2015-11-03 02:40 +0100
Re: timer code oops when calling mod_delayed_work Jeff Layton <jlayton@poochiereds.net> - 2015-11-03 19:00 +0100
Re: timer code oops when calling mod_delayed_work Tejun Heo <tj@kernel.org> - 2015-11-04 00:00 +0100
Re: timer code oops when calling mod_delayed_work Tejun Heo <tj@kernel.org> - 2015-11-04 01:10 +0100
Re: timer code oops when calling mod_delayed_work Jeff Layton <jlayton@poochiereds.net> - 2015-11-04 12:50 +0100
[PATCH] timer: add_timer_on() should perform proper migration Tejun Heo <tj@kernel.org> - 2015-11-04 18:20 +0100
[tip:timers/urgent] timers: Use proper base migration in add_timer_on() tip-bot for Tejun Heo <tipbot@zytor.com> - 2015-11-04 20:30 +0100
Re: [PATCH] timer: add_timer_on() should perform proper migration Thomas Gleixner <tglx@linutronix.de> - 2015-11-04 20:40 +0100
Re: [PATCH] timer: add_timer_on() should perform proper migration Tejun Heo <tj@kernel.org> - 2015-11-04 20:50 +0100
csiph-web