From mboxrd@z Thu Jan 1 00:00:00 1970 From: Thomas Gleixner Subject: Re: b44: regression in 2.6.22 (resend) Date: Mon, 28 May 2007 17:32:51 +0200 Message-ID: <1180366371.4952.5.camel@chaos> References: <20070525172431.60affaca@freepuppy> <200705281216.51690.mb@bu3sch.de> <200705281609.49859.maxi@daemonizer.de> <200705281714.25841.mb@bu3sch.de> Mime-Version: 1.0 Content-Type: text/plain Content-Transfer-Encoding: 7bit Cc: Maximilian Engelhardt , linux-kernel , linux-wireless , Stephen Hemminger , Arnaldo Carvalho de Melo , Jeff Garzik , Gary Zambrano , netdev-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, Andrew Morton To: Michael Buesch Return-path: In-Reply-To: <200705281714.25841.mb-fseUSCV1ubazQB+pC5nmwQ@public.gmane.org> Sender: linux-wireless-owner-u79uwXL29TY76Z2rM5mHXA@public.gmane.org List-Id: netdev.vger.kernel.org On Mon, 2007-05-28 at 17:14 +0200, Michael Buesch wrote: > > The -oldconfig1 is the kernel that had no problems and the other shows the b44 > > problem. So if High Resolution Timer Support is disabled everything works > > fine and if I enable it the problems do appear again. > > > > I didn't test this on my 2.6.22-rc3 kernel yet, but I guess disabling High > > Resolution Timer Support will also solve the problem there. > > > > The older kernels I tried also work perfectly fine and they didn't have the > > High Resolution Timer Support yet. > > So, that's interesting, indeed. > Any idea what's going on, someone? Thomas? Not off the top of my head. Maximilian, does the kernel work otherwise (I mean aside of the b44 driver) ? Can you please keep CONFIG_HIGH_RES_TIMERS and CONFIG_NOHZ and try the following combinations on the kernel command line: 1) highres=off nohz=off (should be the same as your working config) 2) highres=off 3) nohz=off Michael, is anything in the b44 driver timer driven ? Thanks, tglx