NetBSD Problem Report #32186
From www@netbsd.org Mon Nov 28 19:27:13 2005
Return-Path: <www@netbsd.org>
Received: by narn.netbsd.org (Postfix, from userid 31301)
id C584D63B884; Mon, 28 Nov 2005 19:27:13 +0000 (UTC)
Message-Id: <20051128192713.C584D63B884@narn.netbsd.org>
Date: Mon, 28 Nov 2005 19:27:13 +0000 (UTC)
From: matthias.christian@tiscali.de
Reply-To: matthias.christian@tiscali.de
To: gnats-bugs@netbsd.org
Subject: rtw rx/tx overflow
X-Send-Pr-Version: www-1.0
>Number: 32186
>Category: kern
>Synopsis: rtw rx/tx overflow
>Confidential: no
>Severity: serious
>Priority: high
>Responsible: kern-bug-people
>State: open
>Class: sw-bug
>Submitter-Id: net
>Arrival-Date: Mon Nov 28 19:28:00 +0000 2005
>Last-Modified: Fri May 11 19:25:00 +0000 2007
>Originator: Matthias-Christian Ott
>Release: netbsd-4
>Organization:
>Environment:
NetBSD antineutrino 3.99.12 NetBSD 3.99.12 (GENERIC) #0: Mon Nov 28 17:20:47 CET 2005 ott@antineutrino:/home/ott/netbsd-4/src/sys/arch/i386/compile/obj/GENERIC i386
>Description:
After some minutes I get a rx/tx overflow when using the rtw driver [0].
[0] http://metawire.org/~matthias-christian-ott/pub/netbsd/netbsd-4/rtw-rx-tx-overflow
>How-To-Repeat:
>Fix:
>Audit-Trail:
From: Rui Paulo <rpaulo@fnop.net>
To: gnats-bugs@NetBSD.org
Cc:
Subject: Re: kern/32186
Date: Thu, 02 Mar 2006 15:40:20 +0000
cbb0: power on failed?
rtw0: link state changed to UP
rtw0: tx fifo underflow
rtw_rxring_fixup: rx-ring expected next 24, read 266678655
rtw_txring_fixup: tx-ring 0 expected next 0, read 133339519
rtw_txring_fixup: tx-ring 1 expected next 39, read 133339455
rtw_txring_fixup: tx-ring 2 expected next 0, read 133339391
rtw_txring_fixup: tx-ring 3 expected next 1, read 133339295
rtw0: tx fifo underflow
rtw_rxring_fixup: rx-ring expected next 63, read 266678655
rtw_txring_fixup: tx-ring 0 expected next 63, read 133339519
rtw_txring_fixup: tx-ring 1 expected next 63, read 133339455
rtw_txring_fixup: tx-ring 2 expected next 63, read 133339391
rtw_txring_fixup: tx-ring 3 expected next 0, read 133339295
rtw0: tx fifo underflow
rtw_rxring_fixup: rx-ring expected next 63, read 266678655
rtw_txring_fixup: tx-ring 0 expected next 63, read 133339519
rtw_txring_fixup: tx-ring 1 expected next 63, read 133339455
rtw_txring_fixup: tx-ring 2 expected next 63, read 133339391
rtw_txring_fixup: tx-ring 3 expected next 0, read 133339295
rtw0: tx fifo underflow
rtw_rxring_fixup: rx-ring expected next 63, read 266678655
rtw_txring_fixup: tx-ring 0 expected next 63, read 133339519
rtw_txring_fixup: tx-ring 1 expected next 63, read 133339455
rtw_txring_fixup: tx-ring 2 expected next 63, read 133339391
rtw_txring_fixup: tx-ring 3 expected next 0, read 133339295
rtw0: tx fifo underflow
rtw_rxring_fixup: rx-ring expected next 63, read 266678655
rtw_txring_fixup: tx-ring 0 expected next 63, read 133339519
rtw_txring_fixup: tx-ring 1 expected next 63, read 133339455
rtw_txring_fixup: tx-ring 2 expected next 63, read 133339391
rtw_txring_fixup: tx-ring 3 expected next 0, read 133339295
rtw0: tx fifo underflow
rtw_rxring_fixup: rx-ring expected next 63, read 266678655
rtw_txring_fixup: tx-ring 0 expected next 63, read 133339519
rtw_txring_fixup: tx-ring 1 expected next 63, read 133339455
rtw_txring_fixup: tx-ring 2 expected next 63, read 133339391
rtw_txring_fixup: tx-ring 3 expected next 0, read 133339295
rtw0: tx fifo underflow
rtw_rxring_fixup: rx-ring expected next 63, read 266678655
rtw_txring_fixup: tx-ring 0 expected next 63, read 133339519
rtw_txring_fixup: tx-ring 1 expected next 63, read 133339455
rtw_txring_fixup: tx-ring 2 expected next 63, read 133339391
rtw_txring_fixup: tx-ring 3 expected next 0, read 133339295
rtw0: tx fifo underflow
rtw_rxring_fixup: rx-ring expected next 63, read 266678655
rtw_txring_fixup: tx-ring 0 expected next 63, read 133339519
rtw_txring_fixup: tx-ring 1 expected next 63, read 133339455
rtw_txring_fixup: tx-ring 2 expected next 63, read 133339391
rtw_txring_fixup: tx-ring 3 expected next 0, read 133339295
rtw0: tx fifo underflow
rtw_rxring_fixup: rx-ring expected next 63, read 266678655
rtw_txring_fixup: tx-ring 0 expected next 63, read 133339519
rtw_txring_fixup: tx-ring 1 expected next 63, read 133339455
rtw_txring_fixup: tx-ring 2 expected next 63, read 133339391
rtw_txring_fixup: tx-ring 3 expected next 0, read 133339295
rtw0: tx fifo underflow
rtw_rxring_fixup: rx-ring expected next 63, read 266678655
rtw_txring_fixup: tx-ring 0 expected next 63, read 133339519
rtw_txring_fixup: tx-ring 1 expected next 63, read 133339455
rtw_txring_fixup: tx-ring 2 expected next 63, read 133339391
rtw_txring_fixup: tx-ring 3 expected next 0, read 133339295
rtw0: tx fifo underflow
rtw_rxring_fixup: rx-ring expected next 57, read 0
rtw0: tx fifo underflow
rtw_rxring_fixup: rx-ring expected next 22, read 0
rtw0: tx fifo underflow
rtw_rxring_fixup: rx-ring expected next 49, read 0
rtw0: tx fifo underflow
rtw_rxring_fixup: rx-ring expected next 21, read 0
rtw0: tx fifo underflow
rtw_rxring_fixup: rx-ring expected next 1, read 0
rtw0: tx fifo underflow
rtw_rxring_fixup: rx-ring expected next 21, read 0
rtw0: tx fifo underflow
rtw_rxring_fixup: rx-ring expected next 4, read 0
rtw0: tx fifo underflow
rtw_rxring_fixup: rx-ring expected next 55, read 0
rtw0: tx fifo underflow
rtw_rxring_fixup: rx-ring expected next 38, read 0
rtw0: tx fifo underflow
rtw_rxring_fixup: rx-ring expected next 19, read 0
rtw0: tx fifo underflow
rtw_rxring_fixup: rx-ring expected next 45, read 0
rtw0: tx fifo underflow
rtw_rxring_fixup: rx-ring expected next 63, read 0
rtw0: tx fifo underflow
rtw_rxring_fixup: rx-ring expected next 28, read 0
rtw0: tx fifo underflow
rtw_rxring_fixup: rx-ring expected next 33, read 0
rtw0: tx fifo underflow
rtw_rxring_fixup: rx-ring expected next 19, read 0
rtw0: tx fifo underflow
rtw_rxring_fixup: rx-ring expected next 16, read 0
rtw0: tx fifo underflow
rtw_rxring_fixup: rx-ring expected next 26, read 0
rtw0: tx fifo underflow
rtw_rxring_fixup: rx-ring expected next 59, read 0
rtw0: tx fifo underflow
rtw_rxring_fixup: rx-ring expected next 31, read 0
rtw0: tx fifo underflow
rtw_rxring_fixup: rx-ring expected next 6, read 0
rtw0: tx fifo underflow
rtw_rxring_fixup: rx-ring expected next 27, read 0
rtw0: tx fifo underflow
rtw_rxring_fixup: rx-ring expected next 52, read 0
rtw0: tx fifo underflow
rtw_rxring_fixup: rx-ring expected next 52, read 0
rtw0: tx fifo underflow
rtw_rxring_fixup: rx-ring expected next 19, read 0
rtw0: tx fifo underflow
rtw_rxring_fixup: rx-ring expected next 53, read 0
rtw0: tx fifo underflow
rtw_rxring_fixup: rx-ring expected next 12, read 0
rtw0: tx fifo underflow
rtw_rxring_fixup: rx-ring expected next 36, read 0
rtw0: tx fifo underflow
rtw_rxring_fixup: rx-ring expected next 41, read 0
rtw0: tx fifo underflow
rtw_rxring_fixup: rx-ring expected next 22, read 0
rtw0: tx fifo underflow
rtw_rxring_fixup: rx-ring expected next 33, read 0
rtw0: tx fifo underflow
rtw_rxring_fixup: rx-ring expected next 16, read 0
rtw0: tx fifo underflow
rtw_rxring_fixup: rx-ring expected next 18, read 0
rtw0: tx fifo underflow
rtw_rxring_fixup: rx-ring expected next 50, read 0
rtw0: tx fifo underflow
rtw_rxring_fixup: rx-ring expected next 15, read 0
rtw0: tx fifo underflow
rtw_rxring_fixup: rx-ring expected next 8, read 0
rtw0: tx fifo underflow
rtw_rxring_fixup: rx-ring expected next 28, read 0
rtw_seg_too_short: segment too short
rtw0: tx fifo underflow
rtw_rxring_fixup: rx-ring expected next 49, read 0
rtw0: tx fifo underflow
rtw_rxring_fixup: rx-ring expected next 39, read 0
rtw0: tx fifo underflow
rtw_rxring_fixup: rx-ring expected next 15, read 0
rtw0: tx fifo underflow
rtw_rxring_fixup: rx-ring expected next 27, read 0
rtw0: tx fifo underflow
rtw_rxring_fixup: rx-ring expected next 9, read 0
rtw0: tx fifo underflow
rtw_rxring_fixup: rx-ring expected next 56, read 0
rtw0: tx fifo underflow
rtw_rxring_fixup: rx-ring expected next 46, read 0
rtw_rxring_fixup: rx-ring expected next 21, read 0
rtw0: tx fifo underflow
rtw_rxring_fixup: rx-ring expected next 50, read 0
rtw0: tx fifo underflow
rtw_rxring_fixup: rx-ring expected next 7, read 0
rtw0: tx fifo underflow
rtw_rxring_fixup: rx-ring expected next 3, read 0
rtw0: tx fifo underflow
rtw_rxring_fixup: rx-ring expected next 42, read 0
rtw0: tx fifo underflow
rtw_rxring_fixup: rx-ring expected next 28, read 0
rtw0: tx fifo underflow
rtw_rxring_fixup: rx-ring expected next 34, read 0
--
Rui Paulo <rpaulo@{NetBSD{,-PT}.org,fnop.net}>
From: Rudi Ludwig <rudihl@gmx.de>
To: gnats-bugs@NetBSD.org, kern-bug-people@netbsd.org
Cc:
Subject: Re: kern/32186
Date: Fri, 11 May 2007 11:32:17 +0200
Hello,
I am running NetBSD 4.0 Beta 2 on an otherwise Netbsd-3
system -just installed the kernel to test it.
Though this may not be the most correct setup, it should not effect the
interior of the kernel, IMHO.
I can still repeat the rtw0 messages described in the PR.
On a separate 4.99.19 installation (different partition) I only
got one "tx fifo underflow" while running cvs update of
sys and common over that link, i.e. causing some traffic.
So, is there a fix that was not pulled back to 4.0?
Or is this just the sideeffect of something different?
Regards,
Rudi
Details:
========
4.0 Beta 2
NetBSD 4.0_BETA2 (GENERIC_LAPTOP) #0: Thu May 3 01:25:31 UTC 2007
builds@b1.netbsd.org:/home/builds/ab/netbsd-4/i386/200705020000Z-obj/hom
e/builds/ab/netbsd-4/src/sys/arch/i386/compile/GENERIC_LAPTOP
May 10 00:46:00 ratte savecore: /netbsd: _time not in namelist
May 10 00:46:02 ratte /netbsd: rtw_seg_too_short: segment too short
May 10 00:46:40 ratte last message repeated 2 times
May 10 00:46:45 ratte /netbsd: rtw_seg_too_short: segment too short
May 10 00:50:06 ratte /netbsd: rtw0: tx fifo underflow
May 10 00:50:06 ratte /netbsd: rtw_rxring_fixup: rx-ring expected next
42, read
0
May 10 00:50:09 ratte /netbsd: rtw_seg_too_short: segment too short
May 10 00:50:20 ratte last message repeated 10 times
May 10 00:52:41 ratte last message repeated 7 times
May 10 00:55:56 ratte last message repeated 8 times
May 10 00:55:56 ratte /netbsd: rtw0: tx fifo underflow
May 10 00:55:56 ratte /netbsd: rtw_rxring_fixup: rx-ring expected next
63, read
0
May 10 00:55:58 ratte /netbsd: rtw0: tx fifo underflow
May 10 00:55:58 ratte /netbsd: rtw_rxring_fixup: rx-ring expected next
58, read
0
May 10 00:57:13 ratte /netbsd: rtw_seg_too_short: segment too short
May 10 00:57:19 ratte last message repeated 7 times
May 10 00:57:20 ratte /netbsd: rtw0: tx fifo underflow
4.99.19: (taken from /var/log/messages)
May 11 09:57:09 ratte /netbsd: NetBSD 4.99.19 (GENERIC_LAPTOP) #0: Fri
May 4 00
:05:00 PDT 2007
May 11 09:57:09 ratte /netbsd:
builds@wb44:/home/builds/ab/HEAD/i386/20070503000
2Z-obj/home/builds/ab/HEAD/src/sys/arch/i386/compile/GENERIC_LAPTOP
May 11 10:04:04 ratte /netbsd: rtw0: tx fifo underflow
From: David Young <dyoung@pobox.com>
To: Rudi Ludwig <rudihl@gmx.de>
Cc: gnats-bugs@NetBSD.org, kern-bug-people@NetBSD.org
Subject: Re: kern/32186
Date: Fri, 11 May 2007 14:20:29 -0500
On Fri, May 11, 2007 at 11:32:17AM +0200, Rudi Ludwig wrote:
>
> Hello,
>
> I am running NetBSD 4.0 Beta 2 on an otherwise Netbsd-3
> system -just installed the kernel to test it.
> Though this may not be the most correct setup, it should not effect the
> interior of the kernel, IMHO.
>
> I can still repeat the rtw0 messages described in the PR.
>
> On a separate 4.99.19 installation (different partition) I only
> got one "tx fifo underflow" while running cvs update of
> sys and common over that link, i.e. causing some traffic.
>
> So, is there a fix that was not pulled back to 4.0?
> Or is this just the sideeffect of something different?
Rudi,
AFAICT, rtw at the netbsd-4 branch point and at HEAD are virtually
identically. I guess that it is the side effect of something different.
Dave
--
David Young OJC Technologies
dyoung@ojctech.com Urbana, IL * (217) 278-3933
(Contact us)
$NetBSD: query-full-pr,v 1.39 2013/11/01 18:47:49 spz Exp $
$NetBSD: gnats_config.sh,v 1.8 2006/05/07 09:23:38 tsutsui Exp $
Copyright © 1994-2007
The NetBSD Foundation, Inc. ALL RIGHTS RESERVED.
Home