Project

General

Profile

Actions

Bug #2158

open

iwn panics with assertion on boot.

Added by eocallaghan over 12 years ago. Updated over 12 years ago.

Status:
New
Priority:
Normal
Assignee:
-
Category:
-
Target version:
Start date:
Due date:
% Done:

0%

Estimated time:

Description

iwn panics on boot with an assertion on "IS_SERIALIZED"..

add iwn to loader.conf
and ifconfig_iwn0="DHCP" to rc.conf

happens in current.


Files

unnamed (1.48 KB) unnamed ahuete.devel, 10/24/2011 04:13 PM
Actions #1

Updated by eocallaghan over 12 years ago

OK, I think I have figured out what is wrong, please correct me if I am wrong
however I think something like this happens on init:

static void iwn_init(void arg)
...
wlan_serialize_enter();
iwn_init_locked(sc); -----> static void iwn_init_locked(struct iwn_softc *sc)
...
/
Read firmware images from the filesystem. /
error = iwn_read_firmware(sc); -----> static int iwn_read_firmware(struct
iwn_softc *sc)
...
/
* Read firmware image from filesystem. The firmware can block * in a taskq and deadlock against our serializer so unlock * while we do tihs.
/
wlan_assert_serialized(); <------- *KABOOM?

wlan_serialize_exit();

Actions #2

Updated by eocallaghan over 12 years ago

OK, According to swildner this happened due to my misconig where rc.conf should
have
looked like this:

---------
wlans_iwn0="wlan0"
ifconfig_wlan0="DHCP"

Instead of
------------
ifconfig_iwn0="DHCP"

However such misconfigurations should not panic the kernel.
Also according to swildner this happens to ndis(4) so this is likely a issue in
the actual wifi stack.

Actions #3

Updated by ahuete.devel over 12 years ago

Edward,

Did you upload the core to leaf? I don't see a backtrace either.

Cheers,
Antonio Huete

2011/10/24 Edward O'Callaghan (via DragonFly issue tracker) <
>

Edward O'Callaghan <> added the comment:

OK, According to swildner this happened due to my misconig where rc.conf
should
have
looked like this:

---------
wlans_iwn0="wlan0"
ifconfig_wlan0="DHCP"

Instead of
------------
ifconfig_iwn0="DHCP"

However such misconfigurations should not panic the kernel.
Also according to swildner this happens to ndis(4) so this is likely a
issue in
the actual wifi stack.

_____________________________________________
DragonFly issue tracker <>
<http://bugs.dragonflybsd.org/issue2158>
_____________________________________________

Actions

Also available in: Atom PDF