Bug #168
openLivelocked limit engaged while trying to setup IPW wireless
Description
Dear all,
A few days ago I wanted to try Sephe's 80211 patch to get wpa
working under DF. However, I can't load the firmware (neither with
nor without the patch). After ipwcontrol and ifconfig I get the
following error messages:
intr 5 at 50001 > 50000 hz, livelocked limit engaged!
ipw0: timeout waiting for firmware initialization to complete
ipw0: could not load firmware
intr 5 at 7399 < 20000 hz, livelock removed
ACPI turned on or off doesn't seem to make a difference.
I attached a verbose dmesg and vmstat -i before and after
ipwcontrol ipw0 -f....
and after
ifconfig ipw0 inet ... netmask ...
Best regards,
Mathias
PS: wep worked under FBSD60 and under WinXP
Files
Updated by johnvonelite almost 19 years ago
I've observed similar messages in the 1.4.4REL and these directly from 1.2REL on
a Dell laptop.
dmesg clip:
xl0: watchdog timeout
intr 3 at 2083 hz, removing livelock limit
intr 3 at 82596 hz, livelocked! limiting at 20000 hz
xl0: watchdog timeout
intr 3 at 2866 hz, removing livelock limit
intr 3 at 82579 hz, livelocked! limiting at 20000 hz
xl0: watchdog timeout
intr 3 at 1322 hz, removing livelock limit
intr 3 at 82436 hz, livelocked! limiting at 20000 hz
Updated by corecode almost 19 years ago
Creator doen't run DragonFly on this box anymore, closing this issue for now.
Updated by johnvonelite almost 19 years ago
Just tried the latest (i think) daily devel snapshot ISO. The watchdog timeout
issue persists when I run a 'dhclient xl0'. I've included a dmesg from the
serial port on the laptop in dmesg.latitude.txt
Updated by dillon almost 19 years ago
:John Leimon <jleimon@sbcglobal.net> added the comment:
:
:Just tried the latest (i think) daily devel snapshot ISO. The watchdog time=
:out=20
:issue persists when I run a 'dhclient xl0'. I've included a dmesg from the=20
:serial port on the laptop in dmesg.latitude.txt
It thinks it is on IRQ11 but clearly it is on IRQ3.
It should be possible to make it work by turning on polling
for that interface.
sysctl kern.polling.enable=1
ifconfig xl0 polling
...
Not the best solution, but until we get around to bringing
in all the FreeBSD PCI interrupt routing infrastructure we
are going to be stuck with the problem on certain machines.
-Matt
Updated by johnvonelite almost 19 years ago
:sysctl kern.polling.enable=1
:ifconfig xl0 polling
Just tested this workaround on 1.8.0-REL and it was unsuccessful.
Updated by sepherosa almost 19 years ago
Please try following patch:
http://leaf.dragonflybsd.org/~sephe/cbb_020407.diff
Apply under src/sys
patch -p0 -i cbb_020407.diff
Best Regards,
sephe
Updated by sepherosa almost 19 years ago
Don't know. It looks much like interrupt routing problem. Grab anyway.
Updated by tuxillo almost 19 years ago
- Description updated (diff)
- Category set to Driver
- Status changed from New to In Progress
- Assignee set to sepherosa
- Target version set to 4.2
Hi sephe,
Do you think this is still relevant?
Cheers,
Antonio Huete