ipw2200 playing bad

[Morten Thunberg Svendsen]

On Mon, Feb 11, 2008 at 1:45 PM, Jose Carlos <josec.rodriguez at gmail.com> wrote:
> OK, I'm a little bit confused with all these dynticks, tickless
> kernel, HPET, cpuidle and friends. What is it new now that is
> causing the problem? Is there any configuration option in 2.6.24 I
> can play with to recompile it to obtain the nice behaviour I had
> with 2.6.22 regarding ipw2200? This is, not being stuck at C2 when
> the wifi radio is on?

I am joining the confused camp. With Linux 2.6.25-rc3-g18a4bf0 and the
ipw2200 I get the following when Wifi is OFF (phycical switch)

PowerTOP 1.9    (C) 2007 Intel Corporation

Collecting data for 60 seconds
Cn	          Avg residency
C0 (cpu running)        ( 0,4%)
C1		  0,0ms ( 0,0%)
C2		132,6ms (13,9%)
C3		154,8ms (85,7%)
P-states (frequencies)
  1,71 Ghz     0,1%
  1400 Mhz     0,0%
  1200 Mhz     0,0%
   600 Mhz    99,9%
Wakeups-from-idle per second :  6,6	interval: 60,0s
Power usage (ACPI estimate): 11,4W (1,7 hours)
Top causes for wakeups:
  55,9% (  6,8)       <interrupt> : acpi
   8,2% (  1,0)           apache2 : schedule_timeout (process_timeout)
   8,2% (  1,0)           fluxbox : schedule_timeout (process_timeout)


And when it is ON

PowerTOP 1.9    (C) 2007 Intel Corporation

Collecting data for 60 seconds
Cn	          Avg residency
C0 (cpu running)        ( 0,5%)
C1		  0,0ms ( 0,0%)
C2		 88,3ms (99,5%)
C3		  0,0ms ( 0,0%)
P-states (frequencies)
  1,71 Ghz     0,1%
  1400 Mhz     0,0%
  1200 Mhz     0,0%
   600 Mhz    99,9%
Wakeups-from-idle per second : 11,3	interval: 60,0s
Power usage (ACPI estimate): 14,0W (1,6 hours)
Top causes for wakeups:
  52,6% ( 11,8)       <interrupt> : acpi
  17,9% (  4,0)   <kernel module> : usb_hcd_poll_rh_status (rh_timer_func)
   5,0% (  1,1)       <interrupt> : ehci_hcd:usb1, uhci_hcd:usb3,
uhci_hcd:usb4, ipw2200
   4,6% (  1,0)           fluxbox : schedule_timeout (process_timeout)
   4,5% (  1,0)           apache2 : schedule_timeout (process_timeout)


The becaon interval is set at 1000ms so that is not the problem.

Can someone explain how to get down to C3 when using the ipw2200 driver?