Hi, [7-STABLE/i386-SMP] When I enable powerd, ndis takes all the CPU. Powerd alone and ndis alone works fine. The kernel threads "Windows DCP0" and "ndis0 taskq" run at 100%. But the machine is still running (but is very very slow), I can kldunload my ndis module and all is ok. I tried with a kernel (GENERIC) without SMP but there is the same problem. Any idea? Thanks. CPU: Intel(R) Core(TM)2 Duo CPU T7500 @ 2.20GHz (2194.52-MHz 686-class CPU) cpu0: <ACPI CPU> on acpi0 est0: <Enhanced SpeedStep Frequency Control> on cpu0 p4tcc0: <CPU Frequency Thermal Control> on cpu0 Ndis: ndis0: <Atheros AR5008 Wireless Network Adapter> mem 0x97300000-0x9730ffff irq 16 at device 0.0 on pci11 ndis0: [ITHREAD] ndis0: NDIS API version: 5.1 NDIS: open file /compat/ndis/preparse.ini failed: 2 NDIS: open file /compat/ndis/regAdd.txt failed: 2 ndis0: WARNING: using obsoleted if_watchdog interface ndis0: Ethernet address: 00:1e:52:76:65:60 NDIS: open file /compat/ndis/preparse.ini failed: 2 NDIS: open file /compat/ndis/regAdd.txt failed: 2 ndis0: setting BSSID failed: 45
Le Sun, 1 Mar 2009 13:00:18 +0100, Patrick Lamaizi?re <patfbsd@davenulle.org>:> [7-STABLE/i386-SMP] > > When I enable powerd, ndis takes all the CPU. Powerd alone and ndis > alone works fine. > > The kernel threads "Windows DCP0" and "ndis0 taskq" run at > 100%. But the machine is still running (but is very very slow), I can > kldunload my ndis module and all is ok. > > I tried with a kernel (GENERIC) without SMP but there is the same > problem. > > Any idea? Thanks.The problem was simply that the frequency was lowered too many. I have to limit the frequency with debug.cpufreq.lowest. Sorry!
On 3/3/09, Patrick Lamaiziere <patfbsd@davenulle.org> wrote:> Le Sun, 1 Mar 2009 13:00:18 +0100, > Patrick Lamaiziere <patfbsd@davenulle.org>: > >> [7-STABLE/i386-SMP] >> >> When I enable powerd, ndis takes all the CPU. Powerd alone and ndis >> alone works fine. >> >> The kernel threads "Windows DCP0" and "ndis0 taskq" run at >> 100%. But the machine is still running (but is very very slow), I can >> kldunload my ndis module and all is ok. >> >> I tried with a kernel (GENERIC) without SMP but there is the same >> problem. >> >> Any idea? Thanks. > > The problem was simply that the frequency was lowered too many. I have > to limit the frequency with debug.cpufreq.lowest.How much small it was? powerd -b min with 125 freq works fine on CURRENT with ndis for me (except that in such case watchdog errors are displayed on console if connection is heavily used) Note that ndis watchdog stuff have been rewritten on CURRENT. -- Paul