Bug #3082
closednetwork hangs
0%
Description
Hello,
I have installed Dragonfly 5.0 on a little computer having this network device :
re0@pci0:4:0:0: class=0x020000 card=0x816810ec chip=0x816810ec rev=0x02 hdr=0x00
vendor = 'Realtek Semiconductor Co., Ltd.'
device = 'RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller'
class = network
subclass = ethernet
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 :
ifconfig
re0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
options=1b<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING>
inet 192.168.0.100 netmask 0xffffff00 broadcast 192.168.0.255
inet6 fe80::2e0:4cff:fe68:4e8%re0 prefixlen 64 scopeid 0x1
ether 00:e0:4c:68:04:e8
media: Ethernet autoselect (1000baseT <full-duplex>)
status: active
I can access my computer remotely and the computer can access remote computers without any issue. The network works fine in that meaning.
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).
After that the network hangs, sometimes I can get it back, sometimes I get a kernel panic.
I can reproduce it everytime.
Anyway something seems wrong and makes the network unusable (I can't make src-create-shallow :/)
Tell me if you need files. I'm joining a screenshot from last kernel issue following a iso download (5.0rc2).
Regards,
Files
Updated by sepherosa about 7 years ago
My two realtek NICs work fine. I'd suggest to run memtest first.
Could you get a core dump?
On Tue, Oct 17, 2017 at 1:18 AM,
<bugtracker-admin@leaf.dragonflybsd.org> wrote:
Issue #3082 has been reported by daftaupe.
----------------------------------------
Bug #3082: network hangs
http://bugs.dragonflybsd.org/issues/3082
- Author: daftaupe
- Status: New
- Priority: Normal
- Assignee:
- Category: Driver
- Target version: Latest stable
----------------------------------------
Hello,I have installed Dragonfly 5.0 on a little computer having this network device :
re0@pci0:4:0:0: class=0x020000 card=0x816810ec chip=0x816810ec rev=0x02 hdr=0x00
vendor = 'Realtek Semiconductor Co., Ltd.'
device = 'RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller'
class = network
subclass = ethernetI'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 :
ifconfig
re0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
options=1b<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING>
inet 192.168.0.100 netmask 0xffffff00 broadcast 192.168.0.255
inet6 fe80::2e0:4cff:fe68:4e8%re0 prefixlen 64 scopeid 0x1
ether 00:e0:4c:68:04:e8
media: Ethernet autoselect (1000baseT <full-duplex>)
status: activeI can access my computer remotely and the computer can access remote computers without any issue. The network works fine in that meaning.
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).
After that the network hangs, sometimes I can get it back, sometimes I get a kernel panic.
I can reproduce it everytime.Anyway something seems wrong and makes the network unusable (I can't make src-create-shallow :/)
Tell me if you need files. I'm joining a screenshot from last kernel issue following a iso download (5.0rc2).
Regards,
---Files--------------------------------
IMG_20171015_204008.jpg (1.37 MB)--
You have received this notification because you have either subscribed to it, or are involved in it.
To change your notification preferences, please click here: http://bugs.dragonflybsd.org/my/account
--
Tomorrow Will Never Die
Updated by daftaupe about 7 years ago
sepherosa wrote:
My two realtek NICs work fine. I'd suggest to run memtest first.
Could you get a core dump?On Tue, Oct 17, 2017 at 1:18 AM,
<bugtracker-admin@leaf.dragonflybsd.org> wrote:Issue #3082 has been reported by daftaupe.
--
Tomorrow Will Never Die
Hello,
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.
Concerning the core dump I guess I can't upload it here, so how would you like to do ?
Regards,
Updated by daftaupe over 6 years ago
- Status changed from New to Closed
It seems to be fixed on 5.2.2 so I'm closing the bug. Can't explain why though.