On Monday 28 May 2007, Thomas Gleixner wrote:
quoted text
> On Mon, 2007-05-28 at 19:44 +0200, Maximilian Engelhardt wrote:
> > > Can you please keep CONFIG_HIGH_RES_TIMERS and CONFIG_NOHZ and try the
> > > following combinations on the kernel command line:
> > >
> > > 1) highres=3Doff nohz=3Doff (should be the same as your working confi=
g)
quoted text
> > > 2) highres=3Doff
> > > 3) nohz=3Doff
> >
> > I tested this with my 2.6.22-rc3 kernel, here are the results:
> >
> > without any special boot parameters: problem does appear
> > highres=3Doff nohz=3Doff: problem does not appear
> > highres=3Doff: problem does not appear
> > nohz=3Doff: problem does appear
>
> Is there any other strange behavior of the high res enabled kernel than
> the b44 problem ?

I didn't notice anything in the past (as I wrote). But today I did some tes=
ts=20
for an updated version of the p54 mac80211 wlan driver and I noticed exactl=
y=20
the same problem:

when booting with highres=3Doff everything is fine.
But when I boot an highres enabled kernel and I do the iperf-test with the =
p54=20
driver, my systems becomes unresponsive during the test. It seems to be=20
exactly the same problem I have with the b44 driver.
So this might not be a bug in the b44 code but a bug somewhere in the linux=
=20
networking code.

I did the test with an 2.6.22-rc3-git4 kernel and the p54 driver built=20
external as module.=20

Maxi