https://bugs.dragonflybsd.org/https://bugs.dragonflybsd.org/favicon.ico?16293952082008-08-03T08:48:00ZDragonFlyBSD bugtrackerDragonFlyBSD - Bug #1106: Network-related crash on boothttps://bugs.dragonflybsd.org/issues/1106?journal_id=51502008-08-03T08:48:00Zsepherosa
<ul></ul><p>Look like mbuf is NULL.</p>
<p>This probably is:<br />m->m_pkthdr.rcvif = ifp;<br />on line 2571</p>
<p>Please test following patch:<br /><a class="external" href="http://leaf.dragonflybsd.org/~sephe/if_dc.c.diff">http://leaf.dragonflybsd.org/~sephe/if_dc.c.diff</a></p>
<p>Best Regards,<br />sephe</p> DragonFlyBSD - Bug #1106: Network-related crash on boothttps://bugs.dragonflybsd.org/issues/1106?journal_id=51642008-08-03T12:18:01Zt-df
<ul></ul><p>Thanks for the quick reply. This didn't help, but I have more info after <br />playing with it a bit. It turns out that the crash specifically occurs <br />when both interfaces are ifconfig'ed in rc.conf AND dc0 is set to use <br />dhcp. It seems that any other combination is safe.</p>
<p>Tim</p> DragonFlyBSD - Bug #1106: Network-related crash on boothttps://bugs.dragonflybsd.org/issues/1106?journal_id=51652008-08-03T13:20:00Zsepherosa
<ul></ul><p>Same backtrace or something new? If possible give me a coredump.</p>
<p>Best Regards,<br />sephe</p> DragonFlyBSD - Bug #1106: Network-related crash on boothttps://bugs.dragonflybsd.org/issues/1106?journal_id=51692008-08-04T00:16:00Zt-df
<ul></ul><p>It produced the same backtrace, except that frame pointer = 0x10 :0xca615cdc</p>
<p>How do I get the system to generate a coredump? After it drops me into <br />the debugger, the only thing I can see to do is execute reset to reboot <br />and then I have to boot into single user mode to be able to change <br />rc.conf file, so the machine will boot normally again.</p>
<p>Tim</p> DragonFlyBSD - Bug #1106: Network-related crash on boothttps://bugs.dragonflybsd.org/issues/1106?journal_id=51702008-08-04T00:31:01Zluxh
<ul></ul><p>Try to follow this guide on the wiki:<br /><a class="external" href="http://wiki.dragonflybsd.org/index.cgi/HowToCreateACoreDump">http://wiki.dragonflybsd.org/index.cgi/HowToCreateACoreDump</a></p>
<p>Good luck.</p>
<p>Max</p> DragonFlyBSD - Bug #1106: Network-related crash on boothttps://bugs.dragonflybsd.org/issues/1106?journal_id=51712008-08-04T02:36:01Zt-df
<ul></ul><p>Thanks for the pointer. I somehow failed to find that in the wiki. I <br />think I succeeded, although I had to execute the panic command twice in <br />the debugger before it actually dumped the kernel. The files are <br />available at <a class="external" href="http://host.timdarby.net/debug/">http://host.timdarby.net/debug/</a></p>
<p>Thanks,<br />Tim</p> DragonFlyBSD - Bug #1106: Network-related crash on boothttps://bugs.dragonflybsd.org/issues/1106?journal_id=51732008-08-04T19:23:02Zsepherosa
<ul></ul><p>Please test following patch:<br /><a class="external" href="http://leaf.dragonflybsd.org/~sephe/if_dc.c.diff2">http://leaf.dragonflybsd.org/~sephe/if_dc.c.diff2</a></p>
<p>Best Regards,<br />sephe</p> DragonFlyBSD - Bug #1106: Network-related crash on boothttps://bugs.dragonflybsd.org/issues/1106?journal_id=51742008-08-04T20:45:01Zt-df
<ul></ul><p>I tried this patch and got the panic message "dc0 is not running yet". <br />xl0 appears to have come up ok. I have to run off to work now, but I can <br />get you more details later, if needed.</p>
<p>Thanks,<br />Tim</p> DragonFlyBSD - Bug #1106: Network-related crash on boothttps://bugs.dragonflybsd.org/issues/1106?journal_id=51792008-08-05T08:49:02Zsepherosa
<ul></ul><p>Please test the attached patch.</p>
<p>Best Regards,<br />sephe</p> DragonFlyBSD - Bug #1106: Network-related crash on boothttps://bugs.dragonflybsd.org/issues/1106?journal_id=51802008-08-05T11:00:02Zt-df
<ul></ul><p>It works! So, out of curiosity, what does this patch do?</p>
<p>Thanks,<br />Tim</p> DragonFlyBSD - Bug #1106: Network-related crash on boothttps://bugs.dragonflybsd.org/issues/1106?journal_id=51812008-08-05T12:48:03Zsepherosa
<ul></ul><p>Thank you for testing!</p>
<p>- Driver should only check IFF_RUNNING in intr handler, not IFF_UP<br />- SIOC{ADD,DEL}MULTI will try to reprogram hardware's mcast filter,<br />but that should only be done after device is running (IFF_RUNNING)<br />- For unknown reason xircom's mcast filter programming function turns<br />on IFF_RUNNING, which is wrong. I nuked that line and added an<br />assertion in xircom's mcast programming function to make sure that NIC<br />is running, but I forgot that in dc_init() IFF_RUNNING is turned on<br />after mcast filter programming (that's the cause of the latest panic<br />:P)</p>
<p>Best Regards,<br />sephe</p> DragonFlyBSD - Bug #1106: Network-related crash on boothttps://bugs.dragonflybsd.org/issues/1106?journal_id=52972008-08-20T18:43:13Zsepherosa
<ul></ul><p>fix committed to 2.0 and HEAD</p>