We are closing this bug report because it lacks the information we need
to investigate the problem, as described in the previous comments.
Please reopen it if you can give us the missing information, and don't
hesitate to submit bug reports in the future. To reopen the bug report
you can click on
The 18 month support period for Gutsy Gibbon 7.10 has reached its end of life -
http://www.ubuntu.com/news/ubuntu-7.10-eol . As a result, we are closing the
linux-restricted-modules-2.6.22 task. It would be helpful if you could test the
new Jaunty Jackalope 9.04 release and confirm if this issue
Thank you for taking the time to report this bug and helping to make
Ubuntu better. You reported this bug a while ago and there hasn't been
any activity in it recently. We were wondering if this is still an issue
for you. Can you try with the latest Ubuntu release? Thanks in advance.
** Changed
** Description changed:
Binary package hint: linux-source-2.6.22
While using GUTSY daily build 05-JUN-2007, with powertop 1.5 installed,
I noticed that my computer was in the C2 power-saving state for an
average of 95%+ of the time, and was not able to reach the battery-
friendly C3
Here is my powertop output on a macbook 3rd generation with madwifi-ng
trunk. madwifi is still generating a decent number of wakeups but not as
bad as before.
CnAvg residency P-states (frequencies)
C0 (cpu running)( 4.5%) 2.17 Ghz 0.9%
C1
I am also running the latest snapshot of madwifi-ng, and indeed I get ~10-20
wps.
BUT... while wireless in on, my CPU still spends ~70-80% in C2 while completely
idle.
As soon as I turn wireless off (in Network Manager), the CPU goes back to ~99%
in C3/C4.
Could it be a hardware characteristic
No deal: I just compiled 2.6.23-rc8 from source with the cpuidle patch. Nothing
changed.
As soon as I enable wireless (even at the console in single mode), CPU usage
jumps from ~99% C3/C4 to ~70-80% C2.
Latest madwifi used, version r2708, recompiled for the new kernel.
--
Unable to reach C3/C4
I've just compiled the latest snapshot of madwifi-ng and with this
driver revision the problem completely vanished for me. With the
original gutsy driver i got 90-100 wakeups per second (wps). With the
new driver i get about 10 wps.
--
Unable to reach C3/C4 states while wireless is up.
I looked at the Madwifi report, and it seems like this issue has been
largely resolved upstrem with the latest madwifi trunk. However, the
trunk snapshot used in Gutsy still produces 200 wakeups per second.
Could the updates be applied to the Gutsy kernel? This has been
somewhat of a
** Changed in: madwifi
Status: Unknown = New
--
Unable to reach C3/C4 states while wireless is up.
https://bugs.launchpad.net/bugs/118808
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
It's not purely a madwifi issue - tickless kernels without cpuidle
support make it possible for DMA devices to block entry to C3 even when
it's not entirely necessary.
--
Unable to reach C3/C4 states while wireless is up.
https://bugs.launchpad.net/bugs/118808
You received this bug notification
** Bug watch added: Madwifi Trac #1363
http://madwifi.org/ticket/1363
** Also affects: madwifi (upstream) via
http://madwifi.org/ticket/1363
Importance: Unknown
Status: Unknown
--
Unable to reach C3/C4 states while wireless is up.
https://bugs.launchpad.net/bugs/118808
You
This would definitely be a bug in the atheros (madwifi) driver then.
Please see about posting a bug on their site as well and adding a
reference to it from here.
Thanks
** Changed in: linux-restricted-modules-2.6.22 (Ubuntu)
Sourcepackagename: linux-source-2.6.22 =
Thank you Ben.
The bug has been opened in the madwifi trac also.
For reference:
http://madwifi.org/ticket/1363
--
Unable to reach C3/C4 states while wireless is up.
https://bugs.launchpad.net/bugs/118808
You received this bug notification because you are a member of Ubuntu
Bugs, which is the
14 matches
Mail list logo
