https://bugs.dragonflybsd.org/https://bugs.dragonflybsd.org/favicon.ico?16293952082011-10-24T10:10:58ZDragonFlyBSD bugtrackerDragonFlyBSD - Bug #2158: iwn panics with assertion on boot.https://bugs.dragonflybsd.org/issues/2158?journal_id=102242011-10-24T10:10:58Zeocallaghan
<ul></ul><p>OK, I think I have figured out what is wrong, please correct me if I am wrong<br />however I think something like this happens on init:</p>
<p>static void iwn_init(void <strong>arg)<br />...<br /> wlan_serialize_enter();<br /> iwn_init_locked(sc); -----> static void iwn_init_locked(struct iwn_softc *sc)<br /> ...<br /> /</strong> Read firmware images from the filesystem. <strong>/<br /> error = iwn_read_firmware(sc); -----> static int iwn_read_firmware(struct<br />iwn_softc *sc)<br /> ...<br /> /</strong>
* Read firmware image from filesystem. The firmware can block
* in a taskq and deadlock against our serializer so unlock
* while we do tihs.<br /> <strong>/<br /> wlan_assert_serialized(); <------- *KABOOM?</strong><br /> wlan_serialize_exit();</p> DragonFlyBSD - Bug #2158: iwn panics with assertion on boot.https://bugs.dragonflybsd.org/issues/2158?journal_id=102252011-10-24T10:30:23Zeocallaghan
<ul></ul><p>OK, According to swildner this happened due to my misconig where rc.conf <strong>should<br />have</strong> looked like this:</p>
<p>---------<br />wlans_iwn0="wlan0" <br />ifconfig_wlan0="DHCP"</p>
<p>Instead of<br />------------<br />ifconfig_iwn0="DHCP"</p>
<p>However such misconfigurations should not panic the kernel.<br />Also according to swildner this happens to ndis(4) so this is likely a issue in<br />the actual wifi stack.</p> DragonFlyBSD - Bug #2158: iwn panics with assertion on boot.https://bugs.dragonflybsd.org/issues/2158?journal_id=102262011-10-24T23:13:00Zahuete.devel
<ul></ul><p>Edward,</p>
<p>Did you upload the core to leaf? I don't see a backtrace either.</p>
<p>Cheers,<br />Antonio Huete</p>
<p>2011/10/24 Edward O'Callaghan (via DragonFly issue tracker) <<br /><a class="email" href="mailto:sinknull@leaf.dragonflybsd.org">sinknull@leaf.dragonflybsd.org</a>></p>
<blockquote>
<p>Edward O'Callaghan <<a class="email" href="mailto:eocallaghan@auroraux.org">eocallaghan@auroraux.org</a>> added the comment:</p>
<p>OK, According to swildner this happened due to my misconig where rc.conf<br /><strong>should<br />have</strong> looked like this:</p>
<p>---------<br />wlans_iwn0="wlan0" <br />ifconfig_wlan0="DHCP"</p>
<p>Instead of<br />------------<br />ifconfig_iwn0="DHCP"</p>
<p>However such misconfigurations should not panic the kernel.<br />Also according to swildner this happens to ndis(4) so this is likely a<br />issue in<br />the actual wifi stack.</p>
<p>_<em><i></em></i>__<em>_</em>_________________________________________<br />DragonFly issue tracker <<a class="email" href="mailto:bugs@lists.dragonflybsd.org">bugs@lists.dragonflybsd.org</a>><br /><<a class="external" href="http://bugs.dragonflybsd.org/issue2158">http://bugs.dragonflybsd.org/issue2158</a>><br />_<em><i></em></i>__<em>_</em>_________________________________________</p>
</blockquote>