NetBSD Problem Report #30343
From tron@colwyn.zhadum.de Thu May 26 18:33:15 2005
Return-Path: <tron@colwyn.zhadum.de>
Received: from colwyn.zhadum.de (colwyn.zhadum.de [81.187.181.114])
by narn.netbsd.org (Postfix) with ESMTP id 0908163B104
for <gnats-bugs@gnats.NetBSD.org>; Thu, 26 May 2005 18:33:15 +0000 (UTC)
Message-Id: <200505261824.j4QIOWHr005915@sheridan.zhadum.de>
Date: Thu, 26 May 2005 19:24:32 +0100 (BST)
From: Matthias Scheler <tron@zhadum.de>
Reply-To: tron@zhadum.de
To: gnats-bugs@netbsd.org
Subject: NetBSD-sparc64 seems to have trouble initializing PCI interrupts
X-Send-Pr-Version: 3.95
>Number: 30343
>Category: port-sparc64
>Synopsis: NetBSD-sparc64 seems to have trouble initializing PCI interrupts
>Confidential: no
>Severity: serious
>Priority: medium
>Responsible: martin
>State: closed
>Class: sw-bug
>Submitter-Id: net
>Arrival-Date: Thu May 26 18:34:00 +0000 2005
>Closed-Date: Sat Feb 02 13:20:25 +0000 2008
>Last-Modified: Sat Feb 02 13:42:08 +0000 2008
>Originator: tron@zhadum.de
>Release: NetBSD 3.99.5
>Organization:
Matthias Scheler http://scheler.de/~matthias/
>Environment:
System: NetBSD sheridan.zhadum.de 3.99.5 NetBSD 3.99.5 (SHERIDAN) #0: Thu May 26 15:38:37 BST 2005 tron@colwyn.zhadum.de:/src/sys/compile/SHERIDAN sparc64
Architecture: sparc64
Machine: sparc64
>Description:
A few month ago I tried to use a 3Com 3C996B-T in my ULTRA60 which failed
because the interrupt doesn't get initialized properly:
bge0 at pci1 dev 1 function 0: PCI configuration registers:
bge0: interrupting at ivec 0 <---
bge0: firmware handshake timed out, val = 4b657654
bge0: ASIC BCM5701 B5 (0x0105), Ethernet address 00:0a:5e:1e:97:d5
brgphy0 at bge0 phy 1: BCM5701 1000BASE-T media interface, rev. 0
I initially blamed the bge(4) driver. Today I've put a Intel PRO/1000T
in my ULTRA60 and it fails with exactly the same problem:
wm0 at pci1 dev 1 function 0: Intel i82543GC 1000BASE-T Ethernet, rev. 2
wm0: interrupting at ivec 0 <---
wm0: 64-bit 66MHz PCI bus
wm0: 64 word (6 address bits) MicroWire EEPROM
wm0: Ethernet address 00:03:47:b0:e8:6e
It appears that NetBSD-sparc64 has problems initializing PCI interrupts.
Solaris 10 has no problems using the 3Com 3C996B-T in that ULTRA60
and the card also works fine with NetBSD-i386.
>How-To-Repeat:
Put a a 3Com 3C996B-T or Intel PRO/1000T (82543GC) in an ULTRA60.
>Fix:
None provided.
>Release-Note:
>Audit-Trail:
From: Martin Husemann <martin@duskware.de>
To: gnats-bugs@netbsd.org
Cc:
Subject: Re: port-sparc64/30343: NetBSD-sparc64 seems to have trouble initializing PCI interrupts
Date: Thu, 26 May 2005 22:45:44 +0200
Could you add all OF .properties on the path from / to the device node
to the PR?
Martin
From: Andrey Petrov <petrov@netbsd.org>
To: gnats-bugs@netbsd.org
Cc: port-sparc64-maintainer@netbsd.org, gnats-admin@netbsd.org,
netbsd-bugs@netbsd.org
Subject: Re: port-sparc64/30343: NetBSD-sparc64 seems to have trouble initializing PCI interrupts
Date: Thu, 26 May 2005 15:15:40 -0700
Fairly recent kernel runs all right on V100, i'll try ultra30.
It'd be interesting to have your ofw configuration ('prtconf -pv' or 'ofdump')
attached to the ticket and also if you can try older kernels.
--Andrei
State-Changed-From-To: open->feedback
State-Changed-By: tron@netbsd.org
State-Changed-When: Tue, 14 Jun 2005 20:48:15 +0000
State-Changed-Why:
PRs *must* be put into state feedback if you have questions for the
submitter.
From: Matthias Scheler <tron@zhadum.de>
To: port-sparc64-maintainer@netbsd.org, netbsd-bugs@netbsd.org,
NetBSD GNATS <gnats-bugs@netbsd.org>
Cc:
Subject: Re: port-sparc64/30343
Date: Tue, 14 Jun 2005 22:09:20 +0100
On Tue, Jun 14, 2005 at 08:48:16PM +0000, tron@netbsd.org wrote:
> Synopsis: NetBSD-sparc64 seems to have trouble initializing PCI interrupts
>
> State-Changed-From-To: open->feedback
> State-Changed-By: tron@netbsd.org
> State-Changed-When: Tue, 14 Jun 2005 20:48:15 +0000
> State-Changed-Why:
> PRs *must* be put into state feedback if you have questions for the
> submitter.
Here is the OFW output for the 3Com card:
{0} ok show-devs
[...]
/pci@1f,2000/ethernet@1
[...]
{0} ok dev /pci@1f,2000/ethernet@1
{0} ok .properties
available 82800000 00000000 00120000 00000000
7fee0000 81800000 00000000 00001000
00000000 0000f000 00006176 61696c61
bus-range 00000080
00000080
scsi-initiator-id 00000007
clock-frequency 03ef1480
version# 00 00 00 04
implementation# 00 00 00 00
address fffc6000
fffc4000
fffb6000
interrupt-map 00800800 00000000 00000000 00000001 f005fd74 00000000
00800800 00000000 00000000 00000002 f005fd74 00000001
00800800 00000000 00000000 00000003 f005fd74 00000002
00800800 00000000 00000000 00000004 f005fd74 00000003
interrupt-map-mask 00fff800 00000000 00000000 00000007
#interrupt-cells 00000001
slot-names 00 00 00 02 50 43 49 36 36 20 31 00
no-probe-list 0
upa-portid 0000001f
66mhz-capable
interrupts 000007f0
000007ee
000007ef
000007e5
000007e8
000007f2
ranges 00800000 00000000 00000000 000001fe 01000000 00000000 00800000
01000000 00000000 00000000 000001fe 02000000 00000000 00010000
02000000 00000000 00000000 000001ff 00000000 00000000 80000000
03000000 00000000 00000000 000001ff 00000000 00000000 80000000
reg 000001fe 00002000 00000000 00002000
000001fe 01800000 00000000 00000100
000001fe 00000000 00000000 0000d000
bus-parity-generated
#size-cells 00000002
#address-cells 00000003
device_type pci
name pci
model SUNW,psycho
compatible 70 63 69 31 30 38 65 2c 38 30 30 30 00 70 63 69
thermal-interrupt
{0} ok dev /pci@1f,2000/ethernet@1
{0} ok .properties
assigned-addresses 83800810 00000000 00100000 00000000 00010000
82800830 00000000 00110000 00000000 00010000
power-consumption 00000000 007270e0
reg 00800800 00000000 00000000 00000000 00000000
03800810 00000000 00000000 00000000 00010000
02800830 00000000 00000000 00000000 00010000
compatible 70 63 69 31 34 65 34 2c 31 36 34 35 2e 31 30 62
name ethernet
66mhz-capable
fast-back-to-back
devsel-speed 00000001
class-code 00020000
interrupts 00000001
max-latency 00000000
min-grant 00000040
subsystem-vendor-id 000010b7
subsystem-id 00001006
revision-id 00000015
device-id 00001645
vendor-id 000014e4
And here is output from "ofdump":
[Caching 41 nodes and 376 properties]
f0029970: /SUNW,Ultra-60
f002cbb4: /packages
f0033d38: /terminal-emulator
f0036a74: /deblocker
f0037150: /obp-tftp
f0041f10: /disk-label
f005b764: /SUNW,builtin-drivers
f006923c: /sun-keyboard
f002cc24: /chosen
f002cc90: /openprom
f002cd20: /client-services
f002cdc8: /options
f002ce38: /aliases
f004ca84: /memory@0,80000000
f004d064: /virtual-memory
f005fd74: /pci@1f,4000
f00614f4: /ebus@1
f0061a30: /auxio@14,726000
f0061af0: /power@14,724000
f0061b80: /SUNW,pll@14,504000
f0061c14: /sc@14,500000
f0061cc8: /se@14,400000
f00635f8: /su@14,3083f8
f0064e58: /su@14,3062f8
f0064f74: /ecpp@14,3043bc
f0065074: /fdthree@14,3023f0
f0066b58: /eeprom@14,0
f0066c40: /flashprom@10,0
f006dea8: /SUNW,CS4231@14,200000
f00778d8: /network@1,1
f007f0a0: /scsi@3
f0082e84: /disk
f0083a48: /tape
f0084774: /scsi@3,1
f0088558: /disk
f008911c: /tape
f00605f0: /pci@1f,2000
f0089fbc: /ethernet@1
f00611fc: /counter-timer@1f,1c00
f006d538: /SUNW,UltraSPARC-II@1c,0
f006d8a4: /SUNW,UltraSPARC-II@1c,0
f006e4b8: /SUNW,afb@1f,0
Kind regards
--
Matthias Scheler http://scheler.de/~matthias/
State-Changed-From-To: feedback->open
State-Changed-By: tron@netbsd.org
State-Changed-When: Tue, 14 Jun 2005 21:10:46 +0000
State-Changed-Why:
The requested information was provided.
Responsible-Changed-From-To: port-sparc64-maintainer->martin
Responsible-Changed-By: martin@netbsd.org
Responsible-Changed-When: Wed, 15 Jun 2005 07:23:23 +0000
Responsible-Changed-Why:
I'll handle this.
State-Changed-From-To: open->feedback
State-Changed-By: martin@netbsd.org
State-Changed-When: Wed, 15 Jun 2005 07:23:23 +0000
State-Changed-Why:
We need the properties of dev /pci@1f,2000 and / too.
State-Changed-From-To: feedback->open
State-Changed-By: tron@netbsd.org
State-Changed-When: Wed, 15 Jun 2005 14:21:56 +0000
State-Changed-Why:
The requested information was provided.
From: Matthias Scheler <tron@zhadum.de>
To: Martin Husemann <martin@netbsd.org>
Cc: NetBSD GNATS <gnats-bugs@netbsd.org>, netbsd-bugs@netbsd.org
Subject: Re: port-sparc64/30343
Date: Wed, 15 Jun 2005 15:21:27 +0100
On Wed, Jun 15, 2005 at 07:23:24AM +0000, martin@netbsd.org wrote:
> Synopsis: NetBSD-sparc64 seems to have trouble initializing PCI interrupts
>
> Responsible-Changed-From-To: port-sparc64-maintainer->martin
> Responsible-Changed-By: martin@netbsd.org
> Responsible-Changed-When: Wed, 15 Jun 2005 07:23:23 +0000
> Responsible-Changed-Why:
> I'll handle this.
>
>
> State-Changed-From-To: open->feedback
> State-Changed-By: martin@netbsd.org
> State-Changed-When: Wed, 15 Jun 2005 07:23:23 +0000
> State-Changed-Why:
> We need the properties of dev /pci@1f,2000 and / too.
{0} ok dev /
{0} ok .properties
energystar-v2
idprom 01 80 08 00 20 a9 29 ed 00 00 00 00 a9 29 ed a9
reset-reason B-POR
interrupt-map 0000003c 00000000 00000000 f005fd74 80000033
0000003a 00000000 00000000 f005fd74 80000034
interrupt-map-mask 0000003e 00000000 00000000
#interrupt-cells 00000001
#address-cells 00000002
breakpoint-trap 0000007f
#size-cells 00000002
model SUNW,501-4450
name SUNW,Ultra-60
clock-frequency 06b4b2c6
banner-name Sun Ultra 60 UPA/PCI (2 X UltraSPARC-II 450MHz)
device_type upa
{0} ok dev /pci@1f,2000
{0} ok .properties
available 82800000 00000000 00120000 00000000
7fee0000 81800000 00000000 00001000
00000000 0000f000 00006176 61696c61
bus-range 00000080
00000080
scsi-initiator-id 00000007
clock-frequency 03ef1480
version# 00 00 00 04
implementation# 00 00 00 00
address fffc6000
fffc4000
fffb6000
interrupt-map 00800800 00000000 00000000 00000001 f005fd74 00000000
00800800 00000000 00000000 00000002 f005fd74 00000001
00800800 00000000 00000000 00000003 f005fd74 00000002
00800800 00000000 00000000 00000004 f005fd74 00000003
interrupt-map-mask 00fff800 00000000 00000000 00000007
#interrupt-cells 00000001
slot-names 00 00 00 02 50 43 49 36 36 20 31 00
no-probe-list 0
upa-portid 0000001f
66mhz-capable
interrupts 000007f0
000007ee
000007ef
000007e5
000007e8
000007f2
ranges 00800000 00000000 00000000 000001fe 01000000 00000000 00800000
01000000 00000000 00000000 000001fe 02000000 00000000 00010000
02000000 00000000 00000000 000001ff 00000000 00000000 80000000
03000000 00000000 00000000 000001ff 00000000 00000000 80000000
reg 000001fe 00002000 00000000 00002000
000001fe 01800000 00000000 00000100
000001fe 00000000 00000000 0000d000
bus-parity-generated
#size-cells 00000002
#address-cells 00000003
device_type pci
name pci
model SUNW,psycho
compatible 70 63 69 31 30 38 65 2c 38 30 30 30 00 70 63 69
thermal-interrupt
Kind regards
--
Matthias Scheler http://scheler.de/~matthias/
From: Matthias Scheler <tron@zhadum.de>
To: Martin Husemann <martin@NetBSD.org>
Cc: netbsd-bugs@NetBSD.org, NetBSD GNATS <gnats-bugs@netbsd.org>
Subject: Re: port-sparc64/30343
Date: Wed, 15 Jun 2005 16:02:59 +0100
On Wed, Jun 15, 2005 at 02:21:56PM +0000, tron@netbsd.org wrote:
> Synopsis: NetBSD-sparc64 seems to have trouble initializing PCI interrupts
>
> State-Changed-From-To: feedback->open
> State-Changed-By: tron@netbsd.org
> State-Changed-When: Wed, 15 Jun 2005 14:21:56 +0000
> State-Changed-Why:
> The requested information was provided.
I've also tried a 3.99.6 kernel built from today's (2005-06-15) sources
and the problem is still there:
bge0 at pci1 dev 1 function 0: Broadcom BCM5701 Gigabit Ethernet
--> bge0: interrupting at ivec 0
--> bge0: firmware handshake timed out, val = 4b657654
bge0: ASIC BCM5701 B5 (0x0105), Ethernet address 00:0a:5e:1e:97:d5
brgphy0 at bge0 phy 1: BCM5701 1000BASE-T media interface, rev. 0
I've not tried an older kernel as Andrey suggested. But because I've got
this problem since about a year (when I installed NetBSD on that ULTRA60)
I don't see the point in trying that.
Kind regards
--
Matthias Scheler http://scheler.de/~matthias/
From: Matthias Scheler <tron@zhadum.de>
To: NetBSD GNATS <gnats-bugs@netbsd.org>
Cc:
Subject: Re: port-sparc64/30343
Date: Tue, 6 Dec 2005 22:48:37 +0000
On Wed, Jun 15, 2005 at 02:21:56PM +0000, tron@netbsd.org wrote:
> Synopsis: NetBSD-sparc64 seems to have trouble initializing PCI interrupts
>
> State-Changed-From-To: feedback->open
> State-Changed-By: tron@netbsd.org
> State-Changed-When: Wed, 15 Jun 2005 14:21:56 +0000
> State-Changed-Why:
> The requested information was provided.
Here is another attempt to provide the correct OFW output which
Martin Husemann request:
{0} ok dev /pci@1f,2000/ethernet@1
{0} ok .properties
assigned-addresses 83800810 00000000 00100000 00000000 00010000
power-consumption 00000000 007270e0
reg 00800800 00000000 00000000 00000000 00000000
03800810 00000000 00000000 00000000 00010000
compatible 70 63 69 31 34 65 34 2c 31 36 34 35 2e 31 30 62
name ethernet
66mhz-capable
fast-back-to-back
devsel-speed 00000001
class-code 00020000
interrupts 00000001
max-latency 00000000
min-grant 00000040
subsystem-vendor-id 000010b7
subsystem-id 00001006
revision-id 00000015
device-id 00001645
vendor-id 000014e4
{0} ok dev ..
{0} ok .properties
available 82800000 00000000 00110000 00000000
7fef0000 81800000 00000000 00001000
00000000 0000f000 00006176 61696c61
bus-range 00000080
00000080
scsi-initiator-id 00000007
clock-frequency 03ef1480
version# 00 00 00 04
implementation# 00 00 00 00
address fffc6000
fffc4000
fffb6000
interrupt-map 00800800 00000000 00000000 00000001 f005fd74 00000000
00800800 00000000 00000000 00000002 f005fd74 00000001
00800800 00000000 00000000 00000003 f005fd74 00000002
00800800 00000000 00000000 00000004 f005fd74 00000003
interrupt-map-mask 00fff800 00000000 00000000 00000007
#interrupt-cells 00000001
slot-names 00 00 00 02 50 43 49 36 36 20 31 00
no-probe-list 0
upa-portid 0000001f
66mhz-capable
interrupts 000007f0
000007ee
000007ef
000007e5
000007e8
000007f2
ranges 00800000 00000000 00000000 000001fe 01000000 00000000 00800000
01000000 00000000 00000000 000001fe 02000000 00000000 00010000
02000000 00000000 00000000 000001ff 00000000 00000000 80000000
03000000 00000000 00000000 000001ff 00000000 00000000 80000000
reg 000001fe 00002000 00000000 00002000
000001fe 01800000 00000000 00000100
000001fe 00000000 00000000 0000d000
bus-parity-generated
#size-cells 00000002
#address-cells 00000003
device_type pci
name pci
model SUNW,psycho
compatible 70 63 69 31 30 38 65 2c 38 30 30 30 00 70 63 69
thermal-interrupt
{0} ok dev ..
{0} ok .properties
energystar-v2
idprom 01 80 08 00 20 a9 29 ed 00 00 00 00 a9 29 ed a9
reset-reason S-POR
interrupt-map 0000003c 00000000 00000000 f005fd74 80000033
0000003a 00000000 00000000 f005fd74 80000034
interrupt-map-mask 0000003e 00000000 00000000
#interrupt-cells 00000001
#address-cells 00000002
breakpoint-trap 0000007f
#size-cells 00000002
model SUNW,501-4450
name SUNW,Ultra-60
clock-frequency 06b4b157
banner-name Sun Ultra 60 UPA/PCI (2 X UltraSPARC-II 450MHz)
device_type upa
I hope it's fine this time.
Kind regards
--
Matthias Scheler http://scheler.de/~matthias/
From: Matthias Scheler <tron@zhadum.de>
To: NetBSD GNATS <gnats-bugs@netbsd.org>
Cc:
Subject: Re: port-sparc64/30343
Date: Wed, 7 Dec 2005 21:49:46 +0000
On Tue, Dec 06, 2005 at 10:48:36PM +0000, Matthias Scheler wrote:
> Here is another attempt to provide the correct OFW output which
> Martin Husemann request:
Here is more debugging information which Martin asked for:
{0} ok dev /pci@1f,4000
{0} ok .properties
available 82000000 00000000 0010f000 00000000
7fef1000 81000000 00000000 00001500
00000000 0000eb00 00006176 61696c61
bus-range 00000000
00000000
scsi-initiator-id 00000007
version# 00 00 00 04
implementation# 00 00 00 00
address fffb4000
fffb2000
fffa4000
interrupt-map 00000800 00000000 00000000 00000001 f005fd74 00000021
00001000 00000000 00000000 00000001 f005fd74 00000010
00001000 00000000 00000000 00000002 f005fd74 00000011
00001000 00000000 00000000 00000003 f005fd74 00000012
00001000 00000000 00000000 00000004 f005fd74 00000013
00001800 00000000 00000000 00000001 f005fd74 00000020
00001800 00000000 00000000 00000002 f005fd74 00000026
00002000 00000000 00000000 00000001 f005fd74 00000018
00002000 00000000 00000000 00000002 f005fd74 00000019
00002000 00000000 00000000 00000003 f005fd74 0000001a
00002000 00000000 00000000 00000004 f005fd74 0000001b
00002800 00000000 00000000 00000001 f005fd74 0000001c
00002800 00000000 00000000 00000002 f005fd74 0000001d
00002800 00000000 00000000 00000003 f005fd74 0000001e
00002800 00000000 00000000 00000004 f005fd74 0000001f
interrupt-map-mask 00fff800 00000000 00000000 00000007
#interrupt-cells 00000001
slot-names 00 00 00 34 50 43 49 20 32 00 50 43 49 20 33 00
no-probe-list 0
clock-frequency 01f78a40
upa-portid 0000001f
interrupts 000007f1
000007ee
000007ef
000007e5
000007e8
000007f2
ranges 00000000 00000000 00000000 000001fe 01000000 00000000 00800000
01000000 00000000 00000000 000001fe 02010000 00000000 00010000
02000000 00000000 00000000 000001ff 80000000 00000000 80000000
03000000 00000000 00000000 000001ff 80000000 00000000 80000000
reg 000001fe 00004000 00000000 00002000
000001fe 01000000 00000000 00000100
000001fe 00000000 00000000 0000d000
bus-parity-generated
#size-cells 00000002
#address-cells 00000003
device_type pci
name pci
model SUNW,psycho
compatible 70 63 69 31 30 38 65 2c 38 30 30 30 00 70 63 69
thermal-interrupt
Kind regards
--
Matthias Scheler http://scheler.de/~matthias/
From: Matthias Scheler <tron@zhadum.de>
To: NetBSD GNATS <gnats-bugs@netbsd.org>
Cc:
Subject: Re: port-sparc64/30343
Date: Wed, 12 Apr 2006 21:57:28 +0100
Hello,
I just put an Intel PRO/1000 MT into a Tadpole Voyager running a
NetBSD-sparc64 3.0_STABLE kernel and the card works fine:
wm0 at pci1 dev 2 function 0: Intel i82540EM 1000BASE-T Ethernet, rev. 2
wm0: interrupting at ivec 1c
wm0: 32-bit 33MHz PCI bus
wm0: 64 word (6 address bits) MicroWire EEPROM
wm0: Ethernet address 00:07:e9:0e:bb:33
makphy0 at wm0 phy 1: Marvell 88E1011 Gigabit PHY, rev. 3
ttcp-t: buflen=32768, nbuf=8192, align=16384/0, port=5001, sockbufsize=131072 tcp -> 10.0.0.2
ttcp-t: socket
ttcp-t: sndbuf
ttcp-t: connect
ttcp-t: 268435456 bytes in 18.41 real seconds = 14239.97 KB/sec +++
ttcp-t: 8192 I/O calls, msec/call = 2.30, calls/sec = 445.00
ttcp-t: 0.0user 1.7sys 0:18real 9% 0i+0d 0maxrss 0+32793pf 6+14csw
So it is really an interrupt routing problem and not a problem with either
the bge(4) or the wm(4) driver.
Kind regards
--
Matthias Scheler http://scheler.de/~matthias/
From: Tobias Nygren <tnn@NetBSD.org>
To: gnats-bugs@NetBSD.org
Cc:
Subject: Re: port-sparc64/30343 (NetBSD-sparc64 seems to have trouble initializing
PCI interrupts)
Date: Tue, 24 Apr 2007 14:31:45 +0200
This is a multi-part message in MIME format.
--------------070409080506030201060508
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Looks like the Ultra60 has a pci-pci bridge.
This problem might have been fixed in sparc64/dev/pci_machdep.c r1.54.
If it still doesn't work maybe the attached diff will.
--------------070409080506030201060508
Content-Type: text/plain;
name="test.diff"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline;
filename="test.diff"
Index: pci_machdep.c
===================================================================
RCS file: /cvsroot/src/sys/arch/sparc64/dev/pci_machdep.c,v
retrieving revision 1.54
diff -u -r1.54 pci_machdep.c
--- pci_machdep.c 4 Apr 2007 11:04:33 -0000 1.54
+++ pci_machdep.c 24 Apr 2007 12:30:27 -0000
@@ -499,6 +499,9 @@
printf("OF_mapintr failed\n");
pci_find_ino(pa, &interrupts);
}
+ /* experimental */
+ if (interrupts == 0)
+ pci_find_ino(pa, &interrupts);
/* Try to find an IPL for this type of device. */
prom_getpropstringA(node, "device_type", devtype, sizeof(devtype));
--------------070409080506030201060508--
From: Matthias Scheler <tron@zhadum.de>
To: gnats-bugs@NetBSD.org
Cc: Tobias Nygren <tnn@NetBSD.org>
Subject: Re: port-sparc64/30343 (NetBSD-sparc64 seems to have trouble initializing PCI interrupts)
Date: Tue, 24 Apr 2007 20:18:19 +0100
On Tue, Apr 24, 2007 at 12:35:05PM +0000, Tobias Nygren wrote:
> This problem might have been fixed in sparc64/dev/pci_machdep.c r1.54.
It still doesn't work with a kernel using that revision of "pci_machdep.c".
> If it still doesn't work maybe the attached diff will.
This patch gets me from this ...
bge0 at pci1 dev 1 function 0: Broadcom BCM5701 Gigabit Ethernet
bge0: interrupting at ivec 0
bge0: firmware handshake timed out, val = 4b657654
bge0: ASIC BCM5701 B5 (0x0105), Ethernet address 00:0a:5e:1e:97:d5
... to this:
bge0 at pci1 dev 1 function 0: Broadcom BCM5701 Gigabit Ethernet
bge0: interrupting at ivec 7c0
bge0: firmware handshake timed out, val = 4b657654
bge0: ASIC BCM5701 B5 (0x0105), Ethernet address 00:0a:5e:1e:97:d5
The card does however still not work. If I enable the interface I get
more error messages:
bge0: firmware handshake timed out, val = 4b657654
bge0: firmware handshake timed out, val = 4b657654
The interface can afterwards transmit packets but not receive them.
Kind regards
--
Matthias Scheler http://zhadum.org.uk/
From: Matthias Scheler <tron@zhadum.de>
To: NetBSD GNATS <gnats-bugs@NetBSD.org>
Cc: Julian Coleman <jdc@coris.org.uk>
Subject: Re: port-sparc64/30343 (NetBSD-sparc64 seems to have trouble initializing PCI interrupts)
Date: Sat, 2 Feb 2008 12:21:56 +0000
Hello,
Julian Coleman asked me to try out whether this change ...
http://mail-index.NetBSD.org/source-changes/2007/12/03/0010.html
... fixes my problem. And it seems to help. I still get error message
when brining up the interfaces ...
bge0: firmware handshake timed out, val = 4b657654
bge0: firmware handshake timed out, val = 4b657654
... but it is now usable:
PING 192.168.25.111 (192.168.25.111): 56 data bytes
64 bytes from 192.168.25.111: icmp_seq=1 ttl=255 time=0.560 ms
64 bytes from 192.168.25.111: icmp_seq=2 ttl=255 time=0.445 ms
64 bytes from 192.168.25.111: icmp_seq=0 ttl=255 time=3014.252 ms <---
64 bytes from 192.168.25.111: icmp_seq=5 ttl=255 time=0.485 ms
64 bytes from 192.168.25.111: icmp_seq=4 ttl=255 time=2001.821 ms <---
64 bytes from 192.168.25.111: icmp_seq=7 ttl=255 time=0.483 ms
The occasional high RTTs (both machines are connected to the same
Gigabit switch) are however worrying.
Kind regards
--
Matthias Scheler http://zhadum.org.uk/
State-Changed-From-To: open->closed
State-Changed-By: tron@narn.netbsd.org
State-Changed-When: Sat, 02 Feb 2008 13:20:25 +0000
State-Changed-Why:
I've replaced the 3Com card with an Intel PRO1000/MT network card:
wm0 at pci1 dev 1 function 0: Intel i82540EM 1000BASE-T Ethernet, rev. 2
wm0: interrupting at ivec 0
wm0: 32-bit 66MHz PCI bus
wm0: 64 word (6 address bits) MicroWire EEPROM
wm0: Ethernet address 00:07:e9:XX:XX:XX
makphy0 at wm0 phy 1: Marvell 88E1011 Gigabit PHY, rev. 3
makphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 1000baseT-FDX, auto
There are no problems with this card:
PING 192.168.25.222 (192.168.25.222): 56 data bytes
64 bytes from 192.168.25.222: icmp_seq=0 ttl=255 time=0.646 ms
64 bytes from 192.168.25.222: icmp_seq=1 ttl=255 time=0.831 ms
64 bytes from 192.168.25.222: icmp_seq=2 ttl=255 time=0.840 ms
64 bytes from 192.168.25.222: icmp_seq=3 ttl=255 time=1.054 ms
64 bytes from 192.168.25.222: icmp_seq=4 ttl=255 time=0.826 ms
64 bytes from 192.168.25.222: icmp_seq=5 ttl=255 time=1.032 ms
64 bytes from 192.168.25.222: icmp_seq=6 ttl=255 time=0.808 ms
64 bytes from 192.168.25.222: icmp_seq=7 ttl=255 time=1.018 ms
64 bytes from 192.168.25.222: icmp_seq=8 ttl=255 time=0.768 ms
64 bytes from 192.168.25.222: icmp_seq=9 ttl=255 time=1.000 ms
64 bytes from 192.168.25.222: icmp_seq=10 ttl=255 time=0.843 ms
64 bytes from 192.168.25.222: icmp_seq=11 ttl=255 time=1.107 ms
^C
----192.168.25.222 PING Statistics----
12 packets transmitted, 12 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 0.646/0.898/1.107/0.140 ms
The interrupt handling issue is definitely fixed.
>Unformatted:
(Contact us)
$NetBSD: query-full-pr,v 1.51 2026/08/10 02:28:17 riastradh Exp $
$NetBSD: gnats_config.sh,v 1.10 2026/05/13 22:00:09 riastradh Exp $
Copyright © 1994-2026
The NetBSD Foundation, Inc. ALL RIGHTS RESERVED.