Messages in this thread | | | From | Andres Freund <> | Subject | Re: Soft-Lockup/Race in networking in 2.6.31-rc1+195 ( possibly?caused by netem) | Date | Thu, 9 Jul 2009 17:28:22 +0200 |
| |
Hi,
On Thursday 09 July 2009 16:28:05 Thomas Gleixner wrote: > On Thu, 9 Jul 2009, Jarek Poplawski wrote: > > On Thu, Jul 09, 2009 at 04:15:28PM +0200, Thomas Gleixner wrote: > > > On Thu, 9 Jul 2009, Jarek Poplawski wrote: > > > > On Thu, Jul 09, 2009 at 02:03:50PM +0200, Thomas Gleixner wrote: > > > > > On Thu, 9 Jul 2009, Jarek Poplawski wrote: > > > > > > > I have the feeling that the code relies on some implicit cpu > > > > > > > boundness, which is not longer guaranteed with the timer > > > > > > > migration changes, but that's a question for the network > > > > > > > experts. > > > > > > > > > > > > As a matter of fact, I've just looked at this __netif_schedule(), > > > > > > which really is cpu bound, so you might be 100% right. > > > > > > > > > > So the watchdog is the one which causes the trouble. The patch > > > > > below should fix this. > > > > > > > > I hope so. On the other hand it seems it should work with this > > > > migration yet, so it probably needs additional debugging. > > > > > > Right. I just provided the patch to narrow down the problem, but > > > please test the fix of the hrtimer migration code which I sent out a > > > bit earlier: http://lkml.org/lkml/2009/7/9/150 > > > > > > It fixes a possible endless loop in the timer code which is related to > > > the migration changes. Looking at the backtraces of the spinlock > > > lockup I think that is what you hit. > > > > Actually, Andres and Joao hit this, and I hope they'll try these two > > patches. > > Please test them separate from each other. The one I sent in this > thread was just for narrowing down the issue, but I'm now quite sure > that they really hit the issue which is addressed by the hrtimer > patch. No crash yet. 15min running (seconds to a minute before).
Will let it run for some hours to be sure.
Nice!
Andres
| |