iwn panics with assertion on boot.
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.
#1 Updated by eocallaghan about 6 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)
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
* 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?*
#2 Updated by eocallaghan about 6 years ago
OK, According to swildner this happened due to my misconig where rc.conf *should
have* looked like this:
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.
#3 Updated by ahuete.devel about 6 years ago
Did you upload the core to leaf? I don't see a backtrace either.
2011/10/24 Edward O'Callaghan (via DragonFly issue tracker) <
> Edward O'Callaghan <email@example.com> added the comment:
> OK, According to swildner this happened due to my misconig where rc.conf
> have* looked like this:
> Instead of
> 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 <firstname.lastname@example.org>