NetBSD Problem Report #49519

From www@NetBSD.org  Thu Jan  1 05:54:58 2015
Return-Path: <www@NetBSD.org>
Received: from mail.netbsd.org (mail.netbsd.org [149.20.53.66])
	(using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
	(Client CN "mail.netbsd.org", Issuer "Postmaster NetBSD.org" (verified OK))
	by mollari.NetBSD.org (Postfix) with ESMTPS id DEFF5A5864
	for <gnats-bugs@gnats.NetBSD.org>; Thu,  1 Jan 2015 05:54:57 +0000 (UTC)
Message-Id: <20150101055456.9F3DFA65BB@mollari.NetBSD.org>
Date: Thu,  1 Jan 2015 05:54:56 +0000 (UTC)
From: bexley410@aim.com
Reply-To: bexley410@aim.com
To: gnats-bugs@NetBSD.org
Subject: bge{0,1} interfaces "confused"; no connectivity
X-Send-Pr-Version: www-1.0

>Number:         49519
>Category:       kern
>Synopsis:       bge{0,1} interfaces "confused"; no connectivity
>Confidential:   no
>Severity:       critical
>Priority:       high
>Responsible:    kern-bug-people
>State:          closed
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Thu Jan 01 05:55:00 +0000 2015
>Closed-Date:    Mon Nov 26 14:56:21 +0000 2018
>Last-Modified:  Mon Nov 26 14:56:21 +0000 2018
>Originator:     Don Y
>Release:        6.1.4
>Organization:
>Environment:
>Description:
bge0 and bge1 appear to interact in such a way that each interferes (disables?) the other.  As a result, neither interface works.
>How-To-Repeat:
connect network cable to "first" interface
front panel indicator illuminates
boot 6.1.4 install media
configure network (bge0 bge1 detected)
select bge0
autoselect, no DHCP, set domain and host names, IP, mask, gateway, DNS
indicator goes out - and stays out/ping fails
repeat for bge1 (same settings as bge0) -- no change
drop into shell
ifconfig shows both interfaces as UP and configured per above
bring bge0 DOWN --> front panel indicator comes back on!
ping DNS still fails
ping bge0's IP and all packets ack'd -- but no activity as seen by switch
ping from DNS machine to this machine fail
swap cable to other network connector and repeat for similar results

I.e., no way to get either interface operational.

>Fix:
Machine will probably see another OS installed, RSN.  Or, scrapped.  So, unlikely I'll spend time finding a fix.

[And your mailing lists are essentially inaccessible due to the "greylisting" -- even for incoming mail from verified subscribers!]

>Release-Note:

>Audit-Trail:
From: Martin Husemann <martin@duskware.de>
To: gnats-bugs@NetBSD.org
Cc: 
Subject: Re: kern/49519: bge{0,1} interfaces "confused"; no connectivity
Date: Thu, 1 Jan 2015 11:03:25 +0100

 It would help if you'd tell us a bit about your machine, a good start
 would be the lines from /var/run/dmesg.boot that start with bge0: or bge1:.

 A good test would also be booting a netbsd-7 beta kernel (leave your installed
 userland alone, it should just work and is a very quick thing to try).
 You can get kernels from the daily builds at

 	http://nyftp.netbsd.org/pub/NetBSD-daily/netbsd-7/

 Martin

From: David Holland <dholland-bugs@netbsd.org>
To: gnats-bugs@NetBSD.org
Cc: 
Subject: Re: kern/49519: bge{0,1} interfaces "confused"; no connectivity
Date: Thu, 1 Jan 2015 20:25:20 +0000

 On Thu, Jan 01, 2015 at 05:55:00AM +0000, bexley410@aim.com wrote:
  > connect network cable to "first" interface
  > front panel indicator illuminates
  > boot 6.1.4 install media
  > configure network (bge0 bge1 detected)
  > select bge0
  > autoselect, no DHCP, set domain and host names, IP, mask, gateway, DNS
  > indicator goes out - and stays out/ping fails
  > repeat for bge1 (same settings as bge0) -- no change
  > drop into shell
  > ifconfig shows both interfaces as UP and configured per above
  > bring bge0 DOWN --> front panel indicator comes back on!
  > ping DNS still fails
  > ping bge0's IP and all packets ack'd -- but no activity as seen by switch
  > ping from DNS machine to this machine fail
  > swap cable to other network connector and repeat for similar results
  > 
  > I.e., no way to get either interface operational.

 bge devices have so many hardware-level bugs that we need to know (as
 precisely as possible) what device you have.

  > [And your mailing lists are essentially inaccessible due to the
  > "greylisting" -- even for incoming mail from verified subscribers!]

 ?

 Only if your mailserver is broken. You aren't likely to get a response
 on a mailing list in an hour anyway; if you want instant discussion,
 try freenode.

 -- 
 David A. Holland
 dholland@netbsd.org

From: Don Y <Bexley410@aim.com>
To: gnats-bugs@NetBSD.org, kern-bug-people@netbsd.org, 
 gnats-admin@netbsd.org, netbsd-bugs@netbsd.org
Cc: 
Subject: Re: kern/49519: bge{0,1} interfaces "confused"; no connectivity
Date: Thu, 01 Jan 2015 15:50:39 -0700

 Hi Martin,

 On 1/1/2015 3:05 AM, Martin Husemann wrote:
 > The following reply was made to PR kern/49519; it has been noted by GNATS.
 >
 > From: Martin Husemann <martin@duskware.de>
 > To: gnats-bugs@NetBSD.org
 > Cc:
 > Subject: Re: kern/49519: bge{0,1} interfaces "confused"; no connectivity
 > Date: Thu, 1 Jan 2015 11:03:25 +0100
 >
 >   It would help if you'd tell us a bit about your machine, a good start
 >   would be the lines from /var/run/dmesg.boot that start with bge0: or bge1:.

 Sorry, I've already installed FreeBSD on the box -- I was in a hurry to retire
 the machine that this box replaces before year-end.  Now, in a rush to get the
 FreeBSD machine into production (I've not used FreeBSD since 2.2.1 so a fair
 bit of learning to get under my belt before Monday).

 However, FreeBSD's probe of the pertinent devices yields:

 bge0: <Broadcom NetXtreme Gigabit Ethernet Controller, ASIC rev. 0x002002> mem 
 0xfebd0000-0xfebdffff,0xfebc0000-0xfebcffff irq 21 at device 0.0 on pci2
 bge0: CHIP ID 0x00002002; ASIC REV 0x02; CHIP REV 0x20; PCI-X 133 MHz
 miibus0: <MII bus> on bge0
 brgphy0: <BCM5704 1000BASE-T media interface> PHY 1 on miibus0
 brgphy0:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 
 1000baseT-master, 1000baseT-FDX, 1000baseT-FDX-master, auto, auto-flow
 bge0: Ethernet address: 00:c0:b6:xx:xx:x2
 bge1: <Broadcom NetXtreme Gigabit Ethernet Controller, ASIC rev. 0x002002> mem 
 0xfebf0000-0xfebfffff,0xfebe0000-0xfebeffff irq 22 at device 0.1 on pci2
 bge1: CHIP ID 0x00002002; ASIC REV 0x02; CHIP REV 0x20; PCI-X 133 MHz
 miibus1: <MII bus> on bge1
 brgphy1: <BCM5704 1000BASE-T media interface> PHY 1 on miibus1
 brgphy1:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 
 1000baseT-master, 1000baseT-FDX, 1000baseT-FDX-master, auto, auto-flow
 bge1: Ethernet address: 00:c0:b6:xx:xx:x3

 >   A good test would also be booting a netbsd-7 beta kernel (leave your installed
 >   userland alone, it should just work and is a very quick thing to try).
 >   You can get kernels from the daily builds at
 >
 >   	http://nyftp.netbsd.org/pub/NetBSD-daily/netbsd-7/

 The machine will be tied up for the near future so unlikely I'll get around
 to that anytime soon.  After ~20 years with NetBSD, probably time to make a
 bit of an investment in FreeBSD...

 Happy Holiday!

 (BTW, this email account will be deleted some time today so probably not
 worth replying  :< )

 --don

From: Masanobu SAITOH <msaitoh@execsw.org>
To: gnats-bugs@NetBSD.org, kern-bug-people@netbsd.org, 
 gnats-admin@netbsd.org, netbsd-bugs@netbsd.org, bexley410@aim.com
Cc: msaitoh@execsw.org
Subject: Re: kern/49519: bge{0,1} interfaces "confused"; no connectivity
Date: Mon, 05 Jan 2015 10:14:20 +0900

 On 2015/01/02 7:55, Don Y wrote:
 > The following reply was made to PR kern/49519; it has been noted by GNATS.
 > 
 > From: Don Y <Bexley410@aim.com>
 > To: gnats-bugs@NetBSD.org, kern-bug-people@netbsd.org,
 >   gnats-admin@netbsd.org, netbsd-bugs@netbsd.org
 > Cc:
 > Subject: Re: kern/49519: bge{0,1} interfaces "confused"; no connectivity
 > Date: Thu, 01 Jan 2015 15:50:39 -0700
 > 
 >   Hi Martin,
 >   
 >   On 1/1/2015 3:05 AM, Martin Husemann wrote:
 >   > The following reply was made to PR kern/49519; it has been noted by GNATS.
 >   >
 >   > From: Martin Husemann <martin@duskware.de>
 >   > To: gnats-bugs@NetBSD.org
 >   > Cc:
 >   > Subject: Re: kern/49519: bge{0,1} interfaces "confused"; no connectivity
 >   > Date: Thu, 1 Jan 2015 11:03:25 +0100
 >   >
 >   >   It would help if you'd tell us a bit about your machine, a good start
 >   >   would be the lines from /var/run/dmesg.boot that start with bge0: or bge1:.
 >   
 >   Sorry, I've already installed FreeBSD on the box -- I was in a hurry to retire
 >   the machine that this box replaces before year-end.  Now, in a rush to get the
 >   FreeBSD machine into production (I've not used FreeBSD since 2.2.1 so a fair
 >   bit of learning to get under my belt before Monday).
 >   
 >   However, FreeBSD's probe of the pertinent devices yields:
 >   
 >   bge0: <Broadcom NetXtreme Gigabit Ethernet Controller, ASIC rev. 0x002002> mem
 >   0xfebd0000-0xfebdffff,0xfebc0000-0xfebcffff irq 21 at device 0.0 on pci2
 >   bge0: CHIP ID 0x00002002; ASIC REV 0x02; CHIP REV 0x20; PCI-X 133 MHz
 >   miibus0: <MII bus> on bge0
 >   brgphy0: <BCM5704 1000BASE-T media interface> PHY 1 on miibus0
 >   brgphy0:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT,
 >   1000baseT-master, 1000baseT-FDX, 1000baseT-FDX-master, auto, auto-flow
 >   bge0: Ethernet address: 00:c0:b6:xx:xx:x2
 >   bge1: <Broadcom NetXtreme Gigabit Ethernet Controller, ASIC rev. 0x002002> mem
 >   0xfebf0000-0xfebfffff,0xfebe0000-0xfebeffff irq 22 at device 0.1 on pci2
 >   bge1: CHIP ID 0x00002002; ASIC REV 0x02; CHIP REV 0x20; PCI-X 133 MHz
 >   miibus1: <MII bus> on bge1
 >   brgphy1: <BCM5704 1000BASE-T media interface> PHY 1 on miibus1
 >   brgphy1:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT,
 >   1000baseT-master, 1000baseT-FDX, 1000baseT-FDX-master, auto, auto-flow
 >   bge1: Ethernet address: 00:c0:b6:xx:xx:x3
 >   
 >   >   A good test would also be booting a netbsd-7 beta kernel (leave your installed
 >   >   userland alone, it should just work and is a very quick thing to try).
 >   >   You can get kernels from the daily builds at
 >   >
 >   >   	http://nyftp.netbsd.org/pub/NetBSD-daily/netbsd-7/
 >   
 >   The machine will be tied up for the near future so unlikely I'll get around
 >   to that anytime soon.  After ~20 years with NetBSD, probably time to make a
 >   bit of an investment in FreeBSD...
 >   
 >   Happy Holiday!
 >   
 >   (BTW, this email account will be deleted some time today so probably not
 >   worth replying  :< )
 >   
 >   --don

  Perhaps this problem was fixed in netbsd-6 branch (which will be released in
 NetBSD 6.2), netbsd-7 and -current.

  Is it OK to close this ticket? Or should we wait until you verify it?


 -- 
 -----------------------------------------------
                 SAITOH Masanobu (msaitoh@execsw.org
                                  msaitoh@netbsd.org)

From: "Paul Goyette" <pgoyette@netbsd.org>
To: gnats-bugs@gnats.NetBSD.org
Cc: 
Subject: PR/49519 CVS commit: src/share/man/man3
Date: Wed, 1 Jun 2016 01:31:11 +0000

 Module Name:	src
 Committed By:	pgoyette
 Date:		Wed Jun  1 01:31:11 UTC 2016

 Modified Files:
 	src/share/man/man3: assert.3

 Log Message:
 Fix AT&T version reference.  From PR misc/49519


 To generate a diff of this commit:
 cvs rdiff -u -r1.13 -r1.14 src/share/man/man3/assert.3

 Please note that diffs are not public domain; they are subject to the
 copyright notices on the relevant files.

State-Changed-From-To: open->closed
State-Changed-By: bouyer@NetBSD.org
State-Changed-When: Mon, 26 Nov 2018 14:56:21 +0000
State-Changed-Why:
msaitoh@ asked a question in 2015, no reply. Looks like a
BCM5704_A2 chip. Assume fixed since then.


>Unformatted:

Home	PR Database Search