Subject: Re: kern/22493 (my problem may have been a bad anoncvs snapshot)
To: None <kern-bug-people@netbsd.org, gnats-admin@netbsd.org,>
From: Arto Selonen <arto@selonen.org>
List: netbsd-bugs
Date: 02/08/2005 08:57:02
The following reply was made to PR kern/22493; it has been noted by GNATS.

From: Arto Selonen <arto@selonen.org>
To: Steve Woodford <scw@netbsd.org>
Cc: gnats-bugs@netbsd.org
Subject: Re: kern/22493 (my problem may have been a bad anoncvs snapshot)
Date: Tue, 8 Feb 2005 10:56:12 +0200 (EET)

 Hi!
 
 On Fri, 4 Feb 2005, Steve Woodford wrote:
 
 > On Friday 04 February 2005 10:09, Arto Selonen wrote:
 >
 >>  Just upgraded a -current to 2.99.15 with whatever sources anoncvs-us2
 >>  mirror gave on 20050203. Observed a panic quite like in this PR.
 >>  We have several NetBSD-current systems with wm(4) cards, and this is
 >>  the first time this PR bites us.
 >
 > Can you try the attached patch and let me know the outcome?
 
 I upgraded two other current systems yesterday. Both have wm(4) interfaces
 and act as gateways (one is 1:1 and the other is 1:N). Neither one showed
 any signs of this PR with stock -current, so no patch was requierd.
 
 I checked 'ident /netbsd' for these systems, and for some reason the
 problem system had several source files with revisions older than
 the working systems (although the sources were synced approximately at the 
 same time; though for the patched system I needed to sync later from 
 another mirror, as anoncvs.us2 was giving corrupted/partial data at the 
 time). I've now synced the problem system sources again, and upgraded 
 to stock -current without any patches. Panic on shutdown is gone, and can 
 not be re-produced.
 
 I can only assume that the problem I experienced was caused by anoncvs
 related problem(s), and only by chance looked like what is described
 in this PR. Your quick patch fixed it for me, which in turn gave me 
 confidence in upgrading the other systems, and then realizing it
 may not have been a real problem, after all.
 
 As I only experienced this on one current system, and even in there only 
 briefly, I can not say whether this is (or even has ever been) a 
 problem in -current. I don't run releases on our systems.
 
 Here are some details from the interfaces I have, and where -current
 is working properly (= this PR is not an issue):
 
 wm0 at pci2 dev 1 function 0: Intel i82547EI 1000BASE-T Ethernet, rev. 0
 wm0: interrupting at irq 5
 wm0: Communication Streaming Architecture
 wm0: using 82547 Tx FIFO stall work-around
 wm0: 65536 word (16 address bits) SPI EEPROM
 igphy0 at wm0 phy 1: Intel IGP01E1000 Gigabit PHY, rev. 0
 
 wm1 at pci3 dev 0 function 0: Intel i82545EM 1000BASE-T Ethernet, rev. 1
 wm1: interrupting at irq 11
 wm1: 32-bit 33MHz PCI bus
 wm1: 256 word (8 address bits) MicroWire EEPROM
 makphy0 at wm1 phy 1: Marvell 88E1011 Gigabit PHY, rev. 3
 
 wm0 at pci2 dev 2 function 0: Intel i82546EB 1000BASE-T Ethernet, rev. 1
 wm0: interrupting at irq 11
 wm0: 32-bit 33MHz PCI bus
 wm0: 256 word (8 address bits) MicroWire EEPROM
 makphy0 at wm0 phy 1: Marvell 88E1011 Gigabit PHY, rev. 3
 
 wm6 at pci2 dev 10 function 0: Intel i82541EI 1000BASE-T Ethernet, rev. 0
 wm6: interrupting at irq 9
 wm6: 32-bit 33MHz PCI bus
 wm6: 64 word (6 address bits) MicroWire EEPROM
 igphy0 at wm6 phy 1: Intel IGP01E1000 Gigabit PHY, rev. 0
 
 wm7 at pci2 dev 11 function 0: Intel i82541EI 1000BASE-T Ethernet, rev. 0
 wm7: interrupting at irq 5
 wm7: 32-bit 33MHz PCI bus
 wm7: 64 word (6 address bits) MicroWire EEPROM
 igphy1 at wm7 phy 1: Intel IGP01E1000 Gigabit PHY, rev. 0
 ukphy0 at wm7 phy 2: Generic IEEE 802.3u media interface
 
 wm0 at pci4 dev 5 function 0: Intel i82540EM 1000BASE-T Ethernet, rev. 2
 wm0: interrupting at irq 11
 wm0: 32-bit 33MHz PCI bus
 wm0: 64 word (6 address bits) MicroWire EEPROM
 makphy0 at wm0 phy 1: Marvell 88E1011 Gigabit PHY, rev. 3
 
 
 I'd be happy to test any wm-related patches against current, if there is
 any need, though I realize this PR seems to concern releases.
 
 
 Thanks again for looking into this,
 
 Artsi
 -- 
 #######======------  http://www.selonen.org/arto/  --------========########
 Everstinkuja 5 B 35                               Don't mind doing it.
 FIN-02600 Espoo        arto@selonen.org         Don't mind not doing it.
 Finland              tel +358 50 560 4826     Don't know anything about it.