NetBSD Problem Report #35711
From www@NetBSD.org Mon Feb 19 15:47:52 2007
Return-Path: <www@NetBSD.org>
Received: by narn.NetBSD.org (Postfix, from userid 31301)
id A393B63BA6C; Mon, 19 Feb 2007 15:47:52 +0000 (UTC)
Message-Id: <20070219154752.A393B63BA6C@narn.NetBSD.org>
Date: Mon, 19 Feb 2007 15:47:52 +0000 (UTC)
From: tru@pasteur.fr
Reply-To: tru@pasteur.fr
To: gnats-bugs@NetBSD.org
Subject: NetBSD-current msk/amd64 random failures
X-Send-Pr-Version: www-1.0
>Number: 35711
>Category: kern
>Synopsis: NetBSD-current msk/amd64 random failures
>Confidential: no
>Severity: serious
>Priority: medium
>Responsible: jdolecek
>State: closed
>Class: sw-bug
>Submitter-Id: net
>Arrival-Date: Mon Feb 19 15:50:01 +0000 2007
>Closed-Date: Wed Jun 20 19:56:56 +0000 2018
>Last-Modified: Wed Jun 20 19:56:56 +0000 2018
>Originator: tru
>Release: 4.99.11 Mon Feb 19 00:45:31 CET 2007
>Organization:
>Environment:
GENERIC+SMP+ACPI+WPI enabled
arch: amd64
hardware: Sony laptop SZ3XP (core duo2)
>Description:
msk0 initialisation failure?
dmesg:
mskc0 at pci3 dev 0 function 0mskc0: interrupt moderation is 0 us
, Yukon-2 FE rev. A1 (0x1): ioapic0 pin 18 (irq 10)
msk0 at mskc0 port A: Ethernet address 00:13:a9:8c:78:69
mvphy0 at msk0 phy 0: Marvell 88E6060 10/100 5-port PHY switch, rev. 3
mvphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
ukphy0 at msk0 phy 3: Generic IEEE 802.3u media interface
ukphy0: OUI 0x000800, model 0x0004, rev. 0
ukphy0: no media present
ukphy1 at msk0 phy 6: Generic IEEE 802.3u media interface
ukphy1: OUI 0x002200, model 0x0011, rev. 0
ukphy1: no media present
ifconfig -m msk0:
msk0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
address: 00:13:a9:8c:78:69
media: Ethernet autoselect (none)
status: no carrier
supported Ethernet media:
media none
media 10baseT
media 10baseT mediaopt full-duplex
media 100baseTX
media 100baseTX mediaopt full-duplex
media autoselect
inet 0.0.0.0 netmask 0xff000000 broadcast 255.255.255.255
inet6 fe80::213:a9ff:fe8c:7869%msk0 prefixlen 64 scopeid 0x2
>How-To-Repeat:
compile current
plug the network cable
ifconfig -a
depending on the switch on the other side, the link is either up on down
(no electrical connection -> "status: no carrier)".
The cable is fine, as any of the device on the other end.
The NIC is properly initiated under linux Fedora Core 6 x86_64.
Any thing I can add to help debug the problem?
>Fix:
>Release-Note:
>Audit-Trail:
From: Manuel Bouyer <bouyer@antioche.eu.org>
To: gnats-bugs@NetBSD.org
Cc: kern-bug-people@NetBSD.org, gnats-admin@NetBSD.org,
netbsd-bugs@NetBSD.org
Subject: Re: kern/35711: NetBSD-current msk/amd64 random failures
Date: Mon, 19 Feb 2007 22:34:57 +0100
On Mon, Feb 19, 2007 at 03:50:01PM +0000, tru@pasteur.fr wrote:
> >Number: 35711
> >Category: kern
> >Synopsis: NetBSD-current msk/amd64 random failures
> >Confidential: no
> >Severity: serious
> >Priority: medium
> >Responsible: kern-bug-people
> >State: open
> >Class: sw-bug
> >Submitter-Id: net
> >Arrival-Date: Mon Feb 19 15:50:01 +0000 2007
> >Originator: tru
> >Release: 4.99.11 Mon Feb 19 00:45:31 CET 2007
> >Organization:
> >Environment:
> GENERIC+SMP+ACPI+WPI enabled
>
> arch: amd64
>
> hardware: Sony laptop SZ3XP (core duo2)
>
>
> >Description:
> msk0 initialisation failure?
>
> dmesg:
> mskc0 at pci3 dev 0 function 0mskc0: interrupt moderation is 0 us
> , Yukon-2 FE rev. A1 (0x1): ioapic0 pin 18 (irq 10)
> msk0 at mskc0 port A: Ethernet address 00:13:a9:8c:78:69
> mvphy0 at msk0 phy 0: Marvell 88E6060 10/100 5-port PHY switch, rev. 3
> mvphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
> ukphy0 at msk0 phy 3: Generic IEEE 802.3u media interface
> ukphy0: OUI 0x000800, model 0x0004, rev. 0
> ukphy0: no media present
> ukphy1 at msk0 phy 6: Generic IEEE 802.3u media interface
> ukphy1: OUI 0x002200, model 0x0011, rev. 0
> ukphy1: no media present
>
> ifconfig -m msk0:
> msk0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
> address: 00:13:a9:8c:78:69
> media: Ethernet autoselect (none)
> status: no carrier
> supported Ethernet media:
> media none
> media 10baseT
> media 10baseT mediaopt full-duplex
> media 100baseTX
> media 100baseTX mediaopt full-duplex
> media autoselect
> inet 0.0.0.0 netmask 0xff000000 broadcast 255.255.255.255
> inet6 fe80::213:a9ff:fe8c:7869%msk0 prefixlen 64 scopeid 0x2
Strange, it's seeing 3 PHYs while only one seems to be really present.
The 2 others PHYs seems to return nonsence.
What happens if you tell explicitely to use phy 0:
ifconfig msk0 media autoselect instance 0
--
Manuel Bouyer <bouyer@antioche.eu.org>
NetBSD: 26 ans d'experience feront toujours la difference
--
From: Tru Huynh <tru@pasteur.fr>
To: gnats-bugs@NetBSD.org
Cc: kern-bug-people@netbsd.org, gnats-admin@netbsd.org,
netbsd-bugs@netbsd.org
Subject: Re: kern/35711: NetBSD-current msk/amd64 random failures
Date: Tue, 20 Feb 2007 12:06:25 +0100
On Mon, Feb 19, 2007 at 09:40:04PM +0000, Manuel Bouyer wrote:
...
>
> Strange, it's seeing 3 PHYs while only one seems to be really present.
> The 2 others PHYs seems to return nonsence.
> What happens if you tell explicitely to use phy 0:
> ifconfig msk0 media autoselect instance 0
>
here is the results from a working switch with today's kernel:
tru@woodstock [~]> uname -a
NetBSD woodstock.bis.pasteur.fr 4.99.12 NetBSD 4.99.12 (WOODSTOCK_ACPI) #4: Tue Feb 20 12:30:25 CET 2007 tru@woodstock.bis.pasteur.fr:/home/tru/NetBSD/build/amd64/home/tru/NetBSD/source/usr/src/sys/arch/amd64/compile/WOODSTOCK_ACPI amd64
tru@woodstock [usr/src]> grep -v '^#' conf-amd64/WOODSTOCK*
conf-amd64/WOODSTOCK:include "arch/amd64/conf/GENERIC"
conf-amd64/WOODSTOCK:options MULTIPROCESSOR
conf-amd64/WOODSTOCK:options DIAGNOSTIC # expensive kernel consistency checks
conf-amd64/WOODSTOCK:options LOCKDEBUG
conf-amd64/WOODSTOCK:makeoptions COPTS="-O2 -fno-omit-frame-pointer"
conf-amd64/WOODSTOCK:options DDB # in-kernel debugger
conf-amd64/WOODSTOCK:options DDB_TEE_MSGBUF=1
conf-amd64/WOODSTOCK:makeoptions DEBUG="-g" # compile full symbol table
conf-amd64/WOODSTOCK:wpi* at pci? dev ? function ? # Intel PRO/Wireless 3945ABG
conf-amd64/WOODSTOCK:agp* at pchb?
conf-amd64/WOODSTOCK:cbb* at pci? dev ? function ?
conf-amd64/WOODSTOCK:cardslot* at cbb?
conf-amd64/WOODSTOCK:cardbus* at cardslot?
conf-amd64/WOODSTOCK:pcmcia* at cardslot?
conf-amd64/WOODSTOCK:mvphy* at mii? phy ?
conf-amd64/WOODSTOCK_ACPI:include "arch/amd64/conf/WOODSTOCK"
conf-amd64/WOODSTOCK_ACPI:acpi0 at mainbus0
conf-amd64/WOODSTOCK_ACPI:no options MPBIOS_SCANPCI
conf-amd64/WOODSTOCK_ACPI:acpiacad* at acpi? # ACPI AC Adapter
conf-amd64/WOODSTOCK_ACPI:acpibat* at acpi? # ACPI Battery
conf-amd64/WOODSTOCK_ACPI:acpibut* at acpi? # ACPI Button
conf-amd64/WOODSTOCK_ACPI:acpiec* at acpi? # ACPI Embedded Controller
conf-amd64/WOODSTOCK_ACPI:acpilid* at acpi? # ACPI Lid Switch
conf-amd64/WOODSTOCK_ACPI:acpitz* at acpi? # ACPI Thermal Zone
conf-amd64/WOODSTOCK_ACPI:com* at acpi? # Serial communications interface
conf-amd64/WOODSTOCK_ACPI:fdc* at acpi? # Floppy disk controller
conf-amd64/WOODSTOCK_ACPI:joy* at acpi? # Joystick/Game port
conf-amd64/WOODSTOCK_ACPI:lpt* at acpi? # Parallel port
conf-amd64/WOODSTOCK_ACPI:mpu* at acpi? # Roland MPU-401 MIDI UART
conf-amd64/WOODSTOCK_ACPI:pckbc* at acpi? # PC keyboard controller
conf-amd64/WOODSTOCK_ACPI:attimer* at acpi? # AT Timer
conf-amd64/WOODSTOCK_ACPI:pcppi* at acpi? # AT-style speaker sound
conf-amd64/WOODSTOCK_ACPI:wss* at acpi? # NeoMagic 256AV in wss mode
conf-amd64/WOODSTOCK_ACPI:no attimer0 at isa?
conf-amd64/WOODSTOCK_ACPI:no com0 at isa?
conf-amd64/WOODSTOCK_ACPI:no com1 at isa?
conf-amd64/WOODSTOCK_ACPI:no fdc0 at isa?
conf-amd64/WOODSTOCK_ACPI:no lpt0 at isa?
conf-amd64/WOODSTOCK_ACPI:no lpt1 at isa?
conf-amd64/WOODSTOCK_ACPI:no pckbc0 at isa?
conf-amd64/WOODSTOCK_ACPI:no pcppi0 at is
dmesg:
...
mskc0 at pci3 dev 0 function 0mskc0: interrupt moderation is 0 us
, Yukon-2 FE rev. A1 (0x1): ioapic0 pin 18 (irq 10)
msk0 at mskc0 port A: Ethernet address 00:13:a9:8c:78:69
mvphy0 at msk0 phy 0: Marvell 88E6060 10/100 5-port PHY switch, rev. 3
mvphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
ukphy0 at msk0 phy 3: Generic IEEE 802.3u media interface
ukphy0: OUI 0x000800, model 0x0004, rev. 0
ukphy0: no media present
ukphy1 at msk0 phy 6: Generic IEEE 802.3u media interface
ukphy1: OUI 0x002200, model 0x0011, rev. 0
ukphy1: no media present
...
mskc0: interrupt moderation is 1000 us
tru@woodstock [usr/src]> ifconfig msk0
msk0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
address: 00:13:a9:8c:78:69
media: Ethernet autoselect (100baseTX full-duplex)
status: active
inet 157.99.90.151 netmask 0xffffff00 broadcast 157.99.90.255
inet6 fe80::213:a9ff:fe8c:7869%msk0 prefixlen 64 scopeid 0x2
tru@woodstock [usr/src]> ifconfig -m msk0
msk0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
address: 00:13:a9:8c:78:69
media: Ethernet autoselect (100baseTX full-duplex)
status: active
supported Ethernet media:
media none
media 10baseT
media 10baseT mediaopt full-duplex
media 100baseTX
media 100baseTX mediaopt full-duplex
media autoselect
inet 157.99.90.151 netmask 0xffffff00 broadcast 157.99.90.255
inet6 fe80::213:a9ff:fe8c:7869%msk0 prefixlen 64 scopeid 0x2
tru@woodstock [usr/src]> sudo ifconfig msk0 media autoselect instance 0
tru@woodstock [usr/src]> ifconfig -m msk0
msk0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
address: 00:13:a9:8c:78:69
media: Ethernet autoselect (100baseTX full-duplex)
status: active
supported Ethernet media:
media none
media 10baseT
media 10baseT mediaopt full-duplex
media 100baseTX
media 100baseTX mediaopt full-duplex
media autoselect
inet 157.99.90.151 netmask 0xffffff00 broadcast 157.99.90.255
inet6 fe80::213:a9ff:fe8c:7869%msk0 prefixlen 64 scopeid 0x2
tru@woodstock [usr/src]> ifconfig msk0
msk0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
address: 00:13:a9:8c:78:69
media: Ethernet autoselect (100baseTX full-duplex)
status: active
inet 157.99.90.151 netmask 0xffffff00 broadcast 157.99.90.255
inet6 fe80::213:a9ff:fe8c:7869%msk0 prefixlen 64 scopeid 0x2
I will report after changing building on a "non-working" switch.
Thanks,
Tru
--
Dr Tru Huynh | http://www.pasteur.fr/recherche/unites/Binfs/
mailto:tru@pasteur.fr | tel/fax +33 1 45 68 87 37/19
Institut Pasteur, 25-28 rue du Docteur Roux, 75724 Paris CEDEX 15 France
Responsible-Changed-From-To: kern-bug-people->jdolecek
Responsible-Changed-By: jdolecek@NetBSD.org
Responsible-Changed-When: Mon, 11 Jun 2018 19:18:50 +0000
Responsible-Changed-Why:
I've committed possible fix.
State-Changed-From-To: open->feedback
State-Changed-By: jdolecek@NetBSD.org
State-Changed-When: Mon, 11 Jun 2018 19:18:50 +0000
State-Changed-Why:
Can you confirm if the change done for PR kern/36454 fixes this problem too
by chance?
From: =?UTF-8?B?SmFyb23DrXIgRG9sZcSNZWs=?= <jaromir.dolecek@gmail.com>
To: "gnats-bugs@NetBSD.org" <gnats-bugs@netbsd.org>
Cc: tru@pasteur.fr
Subject: Re: kern/35711 (NetBSD-current msk/amd64 random failures)
Date: Sat, 16 Jun 2018 12:46:46 +0200
Specifically, rev. 1.63 of dev/pci/if_msk.c made the code probe only
PHY instance 0, so exactly your problem.
Jaromir
From: Tru Huynh <tru@pasteur.fr>
To: gnats-bugs@gnats.netbsd.org
Cc:
Subject: Re: kern/35711
Date: Wed, 20 Jun 2018 07:23:01 +0200
Hi,
I no longer have the hardware available to test, sorry.
Thanks
Tru
--
Dr Tru Huynh | mailto:tru@pasteur.fr | tel/fax +33 1 45 68 87 37/19
https://research.pasteur.fr/en/team/structural-bioinformatics/
Institut Pasteur, 25-28 rue du Docteur Roux, 75724 Paris CEDEX 15 France
State-Changed-From-To: feedback->closed
State-Changed-By: jdolecek@NetBSD.org
State-Changed-When: Wed, 20 Jun 2018 19:56:56 +0000
State-Changed-Why:
Submitted no longer has hardware, but the bug should be fixed - there was
specific change to only probe MII index 0, which should avoid the ghosts.
Thanks for report, and feedback reply.
>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.
Home