https://bugs.dragonflybsd.org/https://bugs.dragonflybsd.org/favicon.ico?16293952082017-10-17T13:23:14ZDragonFlyBSD bugtrackerDragonFlyBSD - Bug #3082: network hangshttps://bugs.dragonflybsd.org/issues/3082?journal_id=132722017-10-17T13:23:14Zsepherosa
<ul></ul><p>My two realtek NICs work fine. I'd suggest to run memtest first.<br />Could you get a core dump?</p>
<p>On Tue, Oct 17, 2017 at 1:18 AM,<br /><<a class="email" href="mailto:bugtracker-admin@leaf.dragonflybsd.org">bugtracker-admin@leaf.dragonflybsd.org</a>> wrote:</p>
<blockquote>
<p>Issue <a class="issue tracker-1 status-5 priority-4 priority-default closed" title="Bug: network hangs (Closed)" href="https://bugs.dragonflybsd.org/issues/3082">#3082</a> has been reported by daftaupe.</p>
<p>----------------------------------------<br />Bug <a class="issue tracker-1 status-5 priority-4 priority-default closed" title="Bug: network hangs (Closed)" href="https://bugs.dragonflybsd.org/issues/3082">#3082</a>: network hangs<br /><a class="external" href="http://bugs.dragonflybsd.org/issues/3082">http://bugs.dragonflybsd.org/issues/3082</a></p>
<ul>
<li>Author: daftaupe</li>
<li>Status: New</li>
<li>Priority: Normal</li>
<li>Assignee:</li>
<li>Category: Driver</li>
<li>Target version: Latest stable<br />----------------------------------------<br />Hello,</li>
</ul>
<p>I have installed Dragonfly 5.0 on a little computer having this network device :<br />re0@pci0:4:0:0: class=0x020000 card=0x816810ec chip=0x816810ec rev=0x02 hdr=0x00<br />vendor = 'Realtek Semiconductor Co., Ltd.'<br />device = 'RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller'<br />class = network<br />subclass = ethernet</p>
<p>I've setup my network in the installer following what's prompted with a static IP address. I ended up with a re0 interface setup as such :</p>
<blockquote>
<p>ifconfig</p>
</blockquote>
<p>re0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500<br />options=1b<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING><br />inet 192.168.0.100 netmask 0xffffff00 broadcast 192.168.0.255<br />inet6 fe80::2e0:4cff:fe68:4e8%re0 prefixlen 64 scopeid 0x1<br />ether 00:e0:4c:68:04:e8<br />media: Ethernet autoselect (1000baseT <full-duplex>)<br />status: active</p>
<p>I can access my computer remotely and the computer can access remote computers without any issue. The network works fine in that meaning.</p>
<p>The problem begins to appear when there's more activity on the device than just a ssh connection (for example retrieving an iso with curl is enough).<br />After that the network hangs, sometimes I can get it back, sometimes I get a kernel panic.<br />I can reproduce it everytime.</p>
<p>Anyway something seems wrong and makes the network unusable (I can't make src-create-shallow :/)</p>
<p>Tell me if you need files. I'm joining a screenshot from last kernel issue following a iso download (5.0rc2).</p>
<p>Regards,</p>
<p>---Files--------------------------------<br />IMG_20171015_204008.jpg (1.37 MB)</p>
<p>--<br />You have received this notification because you have either subscribed to it, or are involved in it.<br />To change your notification preferences, please click here: <a class="external" href="http://bugs.dragonflybsd.org/my/account">http://bugs.dragonflybsd.org/my/account</a></p>
</blockquote>
<p>-- <br />Tomorrow Will Never Die</p> DragonFlyBSD - Bug #3082: network hangshttps://bugs.dragonflybsd.org/issues/3082?journal_id=132732017-10-17T15:21:11Zdaftaupepierre-alain@toret.fr
<ul></ul><p>sepherosa wrote:</p>
<blockquote>
<p>My two realtek NICs work fine. I'd suggest to run memtest first.<br />Could you get a core dump?</p>
<p>On Tue, Oct 17, 2017 at 1:18 AM,<br /><<a class="email" href="mailto:bugtracker-admin@leaf.dragonflybsd.org">bugtracker-admin@leaf.dragonflybsd.org</a>> wrote:</p>
<blockquote>
<p>Issue <a class="issue tracker-1 status-5 priority-4 priority-default closed" title="Bug: network hangs (Closed)" href="https://bugs.dragonflybsd.org/issues/3082">#3082</a> has been reported by daftaupe.</p>
</blockquote>
<p>-- <br />Tomorrow Will Never Die</p>
</blockquote>
<p>Hello,</p>
<p>actually this nic was working perfectly under Fedora until I decided to install DragonflyBSD, so I will run a memtest, but I would be surprised to get bad news from it.<br />Concerning the core dump I guess I can't upload it here, so how would you like to do ?</p>
<p>Regards,</p> DragonFlyBSD - Bug #3082: network hangshttps://bugs.dragonflybsd.org/issues/3082?journal_id=134692018-09-17T17:48:38Zdaftaupepierre-alain@toret.fr
<ul><li><strong>Status</strong> changed from <i>New</i> to <i>Closed</i></li></ul><p>It seems to be fixed on 5.2.2 so I'm closing the bug. Can't explain why though.</p>