NetBSD Problem Report #45494
From www@NetBSD.org Wed Oct 19 06:58:06 2011
Return-Path: <www@NetBSD.org>
Received: from mail.netbsd.org (mail.netbsd.org [204.152.190.11])
by www.NetBSD.org (Postfix) with ESMTP id 6EBC763D5A5
for <gnats-bugs@gnats.NetBSD.org>; Wed, 19 Oct 2011 06:58:06 +0000 (UTC)
Message-Id: <20111019065805.CB8EA63B955@www.NetBSD.org>
Date: Wed, 19 Oct 2011 06:58:05 +0000 (UTC)
From: rm@gnu.org
Reply-To: rm@gnu.org
To: gnats-bugs@NetBSD.org
Subject: bge0 watchdog timeout
X-Send-Pr-Version: www-1.0
>Number: 45494
>Category: port-i386
>Synopsis: bge0 watchdog timeout
>Confidential: no
>Severity: serious
>Priority: medium
>Responsible: msaitoh
>State: closed
>Class: sw-bug
>Submitter-Id: net
>Arrival-Date: Wed Oct 19 07:00:00 +0000 2011
>Closed-Date: Thu Nov 29 18:18:56 +0000 2018
>Last-Modified: Thu Nov 29 18:18:56 +0000 2018
>Originator: Riccardo
>Release: 5.99.56
>Organization:
GNUstep
>Environment:
NetBSD grid 5.99.56 NetBSD 5.99.56 (nc6120) #2: Tue Oct 18 11:08:54 CEST 2011 root@grid:/usr/obj/sys/arch/i386/compile/nc6120 i386
>Description:
The network card will interrupt from time to time, the following message appears:
bge0: watchdog timeout -- resetting
bge0: block failed to stop: reg 0x2c00, bit 0x00000002
bge0: block failed to stop: reg 0xc00, bit 0x00000002
After a bit, connection will usually resume, enough to have dropped any exported X session, telnet session, etc.
ifconfig bge0
bge0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
capabilities=3f00<IP4CSUM_Rx,IP4CSUM_Tx,TCP4CSUM_Rx,TCP4CSUM_Tx,UDP4CSUM_Rx,UDP4CSUM_Tx>
enabled=0
address: 00:14:c2:d9:1f:f1
media: Ethernet autoselect (100baseTX full-duplex,flowcontrol,rxpause,txpause)
status: active
inet 10.10.0.113 netmask 0xffffff00 broadcast 10.10.0.255
inet6 fe80::214:c2ff:fed9:1ff1%bge0 prefixlen 64 scopeid 0x3
dmesg | grep bge0
bge0 at pci2 dev 14 function 0: Broadcom BCM5705M Gigabit Ethernet
bge0: interrupting at ioapic0 pin 16
bge0: ASIC BCM5705 A3 (0x3003), Ethernet address 00:14:c2:d9:1f:f1
bge0: setting short Tx thresholds
brgphy0 at bge0 phy 1: BCM5705 1000BASE-T media interface, rev. 2
>How-To-Repeat:
Usually under machine load or under heavier network load, like X11 exporting and un-minimizing a window.
>Fix:
>Release-Note:
>Audit-Trail:
Responsible-Changed-From-To: port-i386-maintainer->msaitoh
Responsible-Changed-By: msaitoh@NetBSD.org
Responsible-Changed-When: Fri, 01 Aug 2014 04:03:00 +0000
Responsible-Changed-Why:
mine.
State-Changed-From-To: open->feedback
State-Changed-By: bouyer@NetBSD.org
State-Changed-When: Mon, 26 Nov 2018 14:45:43 +0000
State-Changed-Why:
If you still have this hardware, could you test a recent kernel ?
From: Riccardo Mottola <riccardo.mottola@libero.it>
To: gnats-bugs@NetBSD.org, msaitoh@NetBSD.org, netbsd-bugs@netbsd.org,
gnats-admin@netbsd.org, bouyer@NetBSD.org, rm@gnu.org
Cc:
Subject: Re: port-i386/45494 (bge0 watchdog timeout)
Date: Thu, 29 Nov 2018 17:38:48 +0100
Hi!
sorry, I don't have that exact hardware anymore - motherboard failed.
I replaced it with a ThinkPad which still has bge0 and similar CPU,
however other components are different (e.g. ATI video card vs. Intel).
I do not have seen this issue, but it might not manifest itself.
I think the PR can be closed because not reproducible by me and others
did not chime in.
bouyer@NetBSD.org wrote:
> Synopsis: bge0 watchdog timeout
>
> State-Changed-From-To: open->feedback
> State-Changed-By: bouyer@NetBSD.org
> State-Changed-When: Mon, 26 Nov 2018 14:45:43 +0000
> State-Changed-Why:
> If you still have this hardware, could you test a recent kernel ?
>
>
>
State-Changed-From-To: feedback->closed
State-Changed-By: bouyer@NetBSD.org
State-Changed-When: Thu, 29 Nov 2018 18:18:56 +0000
State-Changed-Why:
User donesn't have the hardware any more, so no way to test.
Likely fixed anyway.
>Unformatted:
(Contact us)
$NetBSD: query-full-pr,v 1.43 2018/01/16 07:36:43 maya Exp $
$NetBSD: gnats_config.sh,v 1.9 2014/08/02 14:16:04 spz Exp $
Copyright © 1994-2017
The NetBSD Foundation, Inc. ALL RIGHTS RESERVED.