AF:
NF:0
PS:10
SRH:1
SFN:
DSR:
MID:<20070321185005.3dc89032@ripper.onstor.net>
CFG:
PT:0
S:andy.sharp@onstor.com
RQ:
SSV:onstor-exch02.onstor.net
NSV:
SSH:
R:<brian.stark@onstor.com>
MAID:1
X-Sylpheed-Privacy-System:
X-Sylpheed-Sign:0
SCF:#mh/Mailbox/sent
X-Sylpheed-End-Special-Headers: 1
Date: Wed, 21 Mar 2007 18:51:16 -0700
From: Andrew Sharp <andy.sharp@onstor.com>
To: Brian Stark <brian.stark@onstor.com>
Subject: what is PCI error 0x200000?
Message-ID: <20070321185116.7b53b5f8@ripper.onstor.net>
Organization: Onstor
X-Mailer: Sylpheed-Claws 2.6.0 (GTK+ 2.8.20; x86_64-pc-linux-gnu)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit

Inquiring minds want to know. Might have something to do with not using
the Marvell memory, but hey.

The latest trace output is at the end, and was produced with a
kernel with no header fixups, all scanning etc.  It seems to have the
best results so far, the the numbers that come out from the natsemi
driver seem a little odd, but what do I know?  They don't correspond to
the memory map but whatever.

It's giving 0x19020000 as the start address for the first DP83816 and
0x19021000 as the start address for the second.  But it's not
complaining about the device not coming out of reset or any of the rest
of that stuff.

The messages above that for the mem0_base and mem0_base can be
interpreted as follows: ignore bobcat_pci0_init, as they are for the
init of the first PCI bus.  The lines

bobcat_pci1_init: io_base = 0x18000000, io_size = 0x800000
bobcat_pci1_init: mem0_base = 0x1a000000, mem0_size = 0x2000000
bobcat_pci1_init: mem2_base = 0x18800000, mem2_size = 0x800000
bobcat_pci1_init: mem1_base = 0x19000000, mem1_size = 0x1000000

indicate all detected values.  I queried for all three memory windows,
not in order, because I decided to use the mem1 values to register the
PCI-1 bus controller with the kernel.  You only get to specify one
memory resource and one IO resource.

What do you think?

Cheers,

a










Booting Linux kernel...
Linux version 2.6.20-bc9k-gf5483b8e-dirty (andys@ripper) (gcc version 4.1.2 20061115 (prerelease) (Debian 4.1.1-21)) #242 Wed Mar 21 18:12:54 PDT 2007
CPU revision is: 00003440
FPU revision is: 00003420
OnStor Bobcat: Board Assembly Rev. A3
Booting from recovery prom
Bus clock speed: 133MHz
Determined physical RAM map:
 memory: 0d000000 @ 03000000 (usable)
Built 1 zonelists.  Total pages: 32512
Kernel command line: console=ttyS0,57600n8 console=ttyMM0 root=/dev/nfs nfsroot=10.0.0.42:/var/nfsroot/bobcat,v3 ip=10.2.9.7:10.0.0.42:10.2.0.1:255.255.255.0:b00bcat
Primary instruction cache 16kB, physically tagged, 4-way, linesize 32 bytes.
Primary data cache 16kB, 4-way, linesize 32 bytes.
Synthesized TLB refill handler (27 instructions).
Synthesized TLB load handler fastpath (39 instructions).
Synthesized TLB store handler fastpath (39 instructions).
Synthesized TLB modify handler fastpath (38 instructions).
PID hash table entries: 512 (order: 9, 2048 bytes)
Using 399.994 MHz high precision timer.
Dentry cache hash table entries: 16384 (order: 4, 65536 bytes)
Inode-cache hash table entries: 8192 (order: 3, 32768 bytes)
Memory: 78208k/81920k available (1838k kernel code, 3620k reserved, 426k data, 124k init, 0k highmem)
796.67 BogoMIPS (lpj=398336)
Mount-cache hash table entries: 512
NET: Registered protocol family 16
pci enable word = 0xffffc5f3
bobcat_pci0_init: io_base = 0x0, io_size = 0x10000
bobcat_pci0_init: mem0_base = 0x1d000000, mem0_size = 0x1000000
bobcat_pci0_init: mv_io_base = 0x0, mv_io_size = 0x10000
bobcat_pci1_init: io_base = 0x18000000, io_size = 0x800000
bobcat_pci1_init: mem0_base = 0x1a000000, mem0_size = 0x2000000
bobcat_pci1_init: mem2_base = 0x18800000, mem2_size = 0x800000
bobcat_pci1_init: mem1_base = 0x19000000, mem1_size = 0x1000000
bobcat_pci1_init: mem0_base = 0x19000000, mem0_size = 0x1000000
bobcat_pci1_init: mv_io_base = 0x0, mv_io_size = 0x10000
bobcat_pci1_init: mv_io_base = 0x18000000, mv_io_size = 0x800000
pci io_v_base = 0xb8000000
PCI: Failed to allocate mem resource #0:20000000@20000000 for 0000:00:01.0
PCI: Failed to allocate mem resource #2:20000000@20000000 for 0000:00:01.0
PCI: Failed to allocate mem resource #4:2000000@1e000000 for 0000:00:01.3
NET: Registered protocol family 2
IP route cache hash table entries: 1024 (order: 0, 4096 bytes)
TCP established hash table entries: 4096 (order: 2, 16384 bytes)
TCP bind hash table entries: 2048 (order: 1, 8192 bytes)
TCP: Hash tables configured (established 4096 bind 2048)
TCP reno registered
io scheduler noop registered
io scheduler deadline registered (default)
Serial: MPSC driver $Revision: 1.00 $
mpsc_drv_probe: Adding MPSC 0
mpsc_init_hw[0]: Initializing
mpsc_hw_init[0]: Initializing hardware
ttyMM0 at MMIO 0xbc008000 (irq = 52) is a MPSC
natsemi dp8381x driver, version 2.1, Sept 11, 2006
  originally by Donald Becker <becker@scyld.com>
  http://www.scyld.com/network/natsemi.html
  2.4.x kernel port by Jeff Garzik, Tjeerd Mulder
natsemi_probe1: pdev->vendor=0x100b, pdev->device=0x20
PCI: Enabling device 0000:01:00.0 (0006 -> 0007)
natsemi_probe1: iostart/sz for port 0 = 0x19020000/0x1000
natsemi_probe1:ioaddr = b9020000
natsemi eth0: NatSemi DP8381[56] at 0x19020000 (0000:01:00.0), 00:07:34:02:9d:00, IRQ 8, port TP.
natsemi_probe1: pdev->vendor=0x100b, pdev->device=0x20
PCI: Enabling device 0000:01:01.0 (0006 -> 0007)
natsemi_probe1: iostart/sz for port 1 = 0x19021000/0x1000
natsemi_probe1:ioaddr = b9021000
natsemi eth1: NatSemi DP8381[56] at 0x19021000 (0000:01:01.0), 00:07:34:02:9d:01, IRQ 9, port TP.
Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
i2c /dev entries driver
TCP cubic registered
NET: Registered protocol family 1
NET: Registered protocol family 17
drivers/rtc/hctosys.c: unable to open rtc device (rtc0)
Time: MIPS clocksource has been installed.
eth0: DSPCFG accepted after 0 usec.
eth0: link up.
eth0: Setting full-duplex based on negotiated link capability.
eth0: PCI error 0x200000
eth1: DSPCFG accepted after 0 usec.
eth1: PCI error 0x200000
Sending DHCP requests .<5>eth0: PCI error 0x200000
.<5>eth0: PCI error 0x200000
