DragonFlyBSD

Some lines from dmesg:

re0: <RealTek 8111/8168 PCIe Gigabit Ethernet> port 0xee00-0xeeff mem 0xfdff8000-0xfdffbfff,0xfdfff000-0xfdffffff irq 18 at device 0.0 on pci3
re0: Hardware rev. 0x28000000; MAC ver. 0x2a; PCI-E 125MHz
miibus0: <MII bus> on re0

On Mon, Mar 25, 2013 at 3:34 AM, Tim Darby via Redmine
<bugtracker-admin@leaf.dragonflybsd.org> wrote:

Issue #2533 has been updated by t_dfbsd.

Some lines from dmesg:

re0: <RealTek 8111/8168 PCIe Gigabit Ethernet> port 0xee00-0xeeff mem 0xfdff8000-0xfdffbfff,0xfdfff000-0xfdffffff irq 18 at device 0.0 on pci3
re0: Hardware rev. 0x28000000; MAC ver. 0x2a; PCI-E 125MHz
miibus0: <MII bus> on re0
----------------------------------------
Bug #2533: re0: watchdog timeouts, network loss
http://bugs.dragonflybsd.org/issues/2533

Author: t_dfbsd
Status: New
Priority: High
Assignee:
Category:
Target version:

I've seen these lately:

kernel: re0: watchdog timeout

Set hw.re.msi.enable to 0 in /boot/loader.conf, and see whether it helps or not.

Best Regards,
sephe

Thanks, I added that setting. Is there way to verify that it's in effect?

On Tue, Mar 26, 2013 at 12:32 AM, Tim Darby via Redmine
<bugtracker-admin@leaf.dragonflybsd.org> wrote:

Issue #2533 has been updated by t_dfbsd.

Thanks, I added that setting. Is there way to verify that it's in effect?

pciconf -lvc

Look for the re0 related lines, e.g. for my emx1 w/ MSI enabled

emx1@pci0:3:0:0: class=0x020000 card=0x83691043 chip=0x10d38086
rev=0x00 hdr=0x00
vendor = 'Intel Corporation'
device = '82574L Gigabit Network Connection'
class = network
subclass = ethernet
cap 01[c8] = powerspec 2 supports D0 D3 current D0
cap 05[d0] = MSI supports 1 message, 64 bit enabled with 1 message
cap 10[e0] = PCI-Express 1 endpoint
cap 11[a0] = MSI-X supports 5 messages in map 0x1c

Note the "cap 05" line.

After you disable the MSI on re(4), the MSI will not reported as being
enabled in 'pciconf -lvc'

Best Regards,
sephe

----------------------------------------
Bug #2533: re0: watchdog timeouts, network loss
http://bugs.dragonflybsd.org/issues/2533

Author: t_dfbsd
Status: New
Priority: High
Assignee:
Category:
Target version:

I've seen these lately:

kernel: re0: watchdog timeout

and the box loses network connectivity. I started getting them after updating to DragonFly v3.3.0.1365.g972077-DEVELOPMENT

--
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

Thanks, and so far so good. I'll give it a few more days, but it looks like this stopped the watchdog errors.

It looks like this setting did the trick, thanks! Should I keep it in place and close this ticket?

On Thu, Mar 28, 2013 at 11:04 PM, Tim Darby via Redmine
<bugtracker-admin@leaf.dragonflybsd.org> wrote:

Issue #2533 has been updated by t_dfbsd.

It looks like this setting did the trick, thanks! Should I keep it in place and close this ticket?

Well, I do want to enable MSI by default on re(4). I will give you a
patch to try later today.

Best Regards,
sephe

----------------------------------------
Bug #2533: re0: watchdog timeouts, network loss
http://bugs.dragonflybsd.org/issues/2533

Author: t_dfbsd
Status: New
Priority: High
Assignee:
Category:
Target version:

I've seen these lately:

kernel: re0: watchdog timeout

and the box loses network connectivity. I started getting them after updating to DragonFly v3.3.0.1365.g972077-DEVELOPMENT

--
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

On Thu, Mar 28, 2013 at 11:04 PM, Tim Darby via Redmine
<bugtracker-admin@leaf.dragonflybsd.org> wrote:

Issue #2533 has been updated by t_dfbsd.

It looks like this setting did the trick, thanks! Should I keep it in place and close this ticket?

Please test following patch:
http://leaf.dragonflybsd.org/~sephe/re_msi.diff

Using following command to patch:
cd /usr/src
fetch http://leaf.dragonflybsd.org/~sephe/re_msi.diff
patch -p 1 -i ./re_msi.diff

It is against the latest master:
c079e3c45b058bda25081e3357e6a764f8bf018e

And remove the hw.re.msi.enable="0" line from /boot/loader.conf

----------------------------------------
Bug #2533: re0: watchdog timeouts, network loss
http://bugs.dragonflybsd.org/issues/2533

Author: t_dfbsd
Status: New
Priority: High
Assignee:
Category:
Target version:

I've seen these lately:

kernel: re0: watchdog timeout

and the box loses network connectivity. I started getting them after updating to DragonFly v3.3.0.1365.g972077-DEVELOPMENT

--
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

Thanks, the patch is installed and I'll let you know.

I just saw a watchdog timeout with the patch in place. This is with master d88b9605be186eb2c93c4f2683c997a128758b5a

On Tue, Apr 2, 2013 at 5:46 AM, Tim Darby via Redmine
<bugtracker-admin@leaf.dragonflybsd.org> wrote:

Issue #2533 has been updated by t_dfbsd.

I just saw a watchdog timeout with the patch in place. This is with master d88b9605be186eb2c93c4f2683c997a128758b5a

Well, I will disable MSI by default even for PCI-e chips. Thank you
for testing.

Best Regards,
sephe

----------------------------------------
Bug #2533: re0: watchdog timeouts, network loss
http://bugs.dragonflybsd.org/issues/2533

Author: t_dfbsd
Status: New
Priority: High
Assignee:
Category:
Target version:

I've seen these lately:

kernel: re0: watchdog timeout

and the box loses network connectivity. I started getting them after updating to DragonFly v3.3.0.1365.g972077-DEVELOPMENT

--
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

No problem. I'd be happy to test another patch if you decide to revisit this at some point.

I reverted the patch 3 days ago, updated to 19fe0477806ae874bdfcbed56e0e7437cb609aa0, and haven't seen any watchdog timeouts since