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 | Fri, 3 Jul 2009 14:30:00 +0200 |
| |
On Friday 03 July 2009 14:03:01 Jarek Poplawski wrote: > On Fri, Jul 03, 2009 at 01:26:21PM +0200, Andres Freund wrote: > > On Friday 03 July 2009 08:12:13 Jarek Poplawski wrote: > > > On Fri, Jul 03, 2009 at 03:31:31AM +0200, Andres Freund wrote: > > > ... > > > > > > > Ok. I finally see the light. I bisected the issue down to > > > > eea08f32adb3f97553d49a4f79a119833036000a : timers: Logic to move non > > > > pinned timers > > > > > > > > Disabling timer migration like provided in the earlier commit stops > > > > the issue from occuring. > > > > > > > > That it is related to timers is sensible in the light of my findings, > > > > that I could trigger the issue only when using delay in netem - that > > > > is the codepath using qdisc_watchdog... > > > Andres, thanks for your work and time. It saved me a lot of searching, > > > because I wasn't able to trigger this on my old box. > > Thanks. It allowed me to go through some of my remaining paperwork ;-) > > Does anybody of you have an idea where the problem actually resides? > Do you mean possibly broken timers are not enough? I have no ideas how/if the timers are actually broken or if the problem does reside somewhere else and is just made visible by the timer changes.
I would have expected more problem with completely borked timers ;-)
> > Aside from that - is the whole PSCHED_TICKS2NS/PSCHED_NS2TICKS conversion > > business purely backward compatibility? > The whole PSCHED_ conversion was to get finer resolution without > breaking backward compatibility, I hope.;-) I haven't seen any problems - just curious ;-)
Andres
| |