Re: Constant watchdog timeouts on em0 with today's -CURRENT

From: Scott Long <scottl_at_samsco.org>
Date: Thu, 23 Nov 2006 01:18:54 -0700
Joe Marcus Clarke wrote:
> On Thu, 2006-11-23 at 00:35 -0700, Scott Long wrote:
>> Joe Marcus Clarke wrote:
>>> I just synced with today's -CURRENT, and rendered by port build machine
>>> useless.  With minimal network traffic (just logging in via SSH with a
>>> TCP NFS-mounted home) I get an immediate watchdog timeout on em0, and
>>> they just keep coming as I type in the session.  The machine is
>>> otherwise idle while this is occurring.
>>>
>>> I am currently running:
>>>
>>> FreeBSD fugu.marcuscom.com 7.0-CURRENT FreeBSD 7.0-CURRENT #83: Thu Nov
>>> 23 01:51:05 EST 2006
>>> root_at_fugu.marcuscom.com:/space2/obj/usr/src/sys/FUGU  i386
>>>
>>> I was running:
>>>
>>> FreeBSD 7.0-CURRENT #80: Fri Nov 10 15:53:48 EST 2006
>>>     marcus_at_fugu.marcuscom.com:/space2/obj/usr/src/sys/FUGU
>>>
>>> Which provided stable networking.  Here are my verbose dmesg and kernel
>>> config.  Note: this machine has both am if_em and an mpt card.  Could
>>> the recent MSI changes have exacerbated the em watchdog problem?  What
>>> can I do (besides downgrade) to resolve this?  Thanks.
>>>
>>> http://www.marcuscom.com/downloads/fugu_dmesg.txt
>>> http://www.marcuscom.com/downloads/fugu_kernel.txt
>>>
>>> Joe
>> Have you followed the instructions in src/UPDATING on how to turn MSI
>> off?
> 
> Man, do I feel stupid.  I completely overlooked UPDATING.  Indeed,
> disabling MSI restores network stability.  Thanks, Scott.
> 
> Joe
> 

Btw, could you submit a PR with your system information and assign it to
John?  I know that he intends to do some form of blacklist or whitelist
for MSI support, and data like yours is needed for that.

Scott
Received on Thu Nov 23 2006 - 07:19:04 UTC

This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:39:03 UTC