NetBSD Problem Report #38075

From martin@duskware.de  Thu Feb 21 10:38:33 2008
Return-Path: <martin@duskware.de>
Received: from mail.netbsd.org (mail.netbsd.org [204.152.190.11])
	by narn.NetBSD.org (Postfix) with ESMTP id C066263BA8C
	for <gnats-bugs@gnats.netbsd.org>; Thu, 21 Feb 2008 10:38:33 +0000 (UTC)
Message-Id: <20080221005433.C8C1563BA8C@narn.NetBSD.org>
Date: Thu, 21 Feb 2008 00:54:33 +0000 (UTC)
From: mrkj.yy@gmail.com
Reply-To: mrkj.yy@gmail.com
To: netbsd-bugs-owner@NetBSD.org
Subject: wm(4) can not receive arp request
X-Send-Pr-Version: www-1.0

>Number:         38075
>Category:       kern
>Synopsis:       wm(4) can not receive arp request
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    msaitoh
>State:          closed
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Thu Feb 21 10:40:00 +0000 2008
>Closed-Date:    Sun Sep 01 23:45:16 +0000 2019
>Last-Modified:  Sun Sep 01 23:45:16 +0000 2019
>Originator:     Koji Mori
>Release:        NetBSD 4.0
>Organization:
>Environment:
NetBSD myhost 4.0 NetBSD 4.0 (GENERIC) #0: Sun Dec 16 00:20:10 PST 2007  builds@wb34:/home/builds/ab/netbsd-4-0-RELEASE/i386/200712160005Z-obj/home/builds/ab/netbsd-4-0-RELEASE/src/sys/arch/i386/compile/GENERIC i386

>Description:
Fujitsu PRIMERGY RX200 has two LAN interfaces detected as wm0 and wm1.
wm0 can not receieve arp request from other hosts, but wm1 can receive.

The interfaces is detected as follows:

wm0 at pci2 dev 2 function 0: Intel i82546EB 1000BASE-T Ethernet, rev.1
wm0: interrupting at ioapic2 pin 0 (irq 10)
wm0: 64-bit 100MHz PCIX bus
wm0: 256 word (8 address bits) MicroWire EEPROM
wm0: Ethernet address 00:14:85:07:04:80
makphy0 at wm0 phy 1: Marvell 88E1011 Gigabit PHY, rev. 3
makphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 1000baseT-FDX, auto
wm1 at pci2 dev 2 function 1: Intel i82546EB 1000BASE-T Ethernet, rev. 1
wm1: interrupting at ioapic2 pin 1 (irq 10)
wm1: 64-bit 100MHz PCIX bus
wm1: 256 word (8 address bits) MicroWire EEPROM
wm1: Ethernet address 00:14:85:07:04:81
makphy1 at wm1 phy 1: Marvell 88E1011 Gigabit PHY, rev. 3
makphy1: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 1000baseT-FDX, auto

This behavior is shown on NetBSD 3.0, too.
But this machine is no problem with other OS (ex. FreeBSD, Linux).

>How-To-Repeat:

>Fix:

>Release-Note:

>Audit-Trail:
From: Martin Husemann <martin@duskware.de>
To: gnats-bugs@NetBSD.org
Cc: 
Subject: Re: kern/38075: wm(4) can not receive arp request
Date: Thu, 21 Feb 2008 11:42:29 +0100

 Have you tried connecting it to a non-gigE switch?
 (c.f. PR 36430)

 Martin

From: Koji Mori <mrkj.yy@gmail.com>
To: gnats-bugs@NetBSD.org
Cc: 
Subject: Re: kern/38075: wm(4) can not receive arp request
Date: Mon, 25 Feb 2008 10:35:45 +0900

 I tried to 100baseTX switch and 10baseT repeater HUB.
 This problem appeared in both cases.

 I tried arping in pkgsrc/net/arping and monitored by tcpdump(8).
 Then, wm0 cannot received arp who-has packet from other host,
 but can send arp who-has to other host and can received arp reply
 from other host.
 And wm1 can send/receive all arp packet.

 This problem is only on wm0 and arp.
 If a host already appeared in the arp table,
 comminucation to it is no problem.

 -- 
 Koji

Responsible-Changed-From-To: kern-bug-people->msaitoh
Responsible-Changed-By: msaitoh@NetBSD.org
Responsible-Changed-When: Fri, 05 Feb 2010 07:09:35 +0000
Responsible-Changed-Why:
mine.


State-Changed-From-To: open->feedback
State-Changed-By: msaitoh@NetBSD.org
State-Changed-When: Fri, 09 Nov 2018 04:42:53 +0000
State-Changed-Why:
The code to disable/enable hardware ARP function was added in March 2010.
I suspect that change fixed this problem. Could you verify it or just
close this PR because it's very old?


State-Changed-From-To: feedback->closed
State-Changed-By: maya@NetBSD.org
State-Changed-When: Sun, 01 Sep 2019 23:45:16 +0000
State-Changed-Why:
feedback timeout, assuming fixed (based on msaitoh's last message, suggesting it probably is fixed)


>Unformatted:

Home	PR Database Search