X-MimeOLE: Produced By Microsoft Exchange V6.5
Received: by onstor-exch02.onstor.net 
	id <01C76CB5.D2C17065@onstor-exch02.onstor.net>; Thu, 22 Mar 2007 12:10:58 -0700
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Content-class: urn:content-classes:message
Subject: RE: what is PCI error 0x200000?
Date: Thu, 22 Mar 2007 12:10:57 -0700
Message-ID: <BB375AF679D4A34E9CA8DFA650E2B04E02F12A2E@onstor-exch02.onstor.net>
In-Reply-To: <20070321185116.7b53b5f8@ripper.onstor.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: what is PCI error 0x200000?
Thread-Index: AcdsJJR0GK31J5U6SJW6AT7rCCW+rwAjy0aA
References: <20070321185116.7b53b5f8@ripper.onstor.net>
From: "Brian Stark" <brian.stark@onstor.com>
To: "Andy Sharp" <andy.sharp@onstor.com>

Andy,

Where is the PCI error being read from?  If this is a register in the
Marvell or the Intel bridge for PCI status, it may have something to do
with the National Semi base addresses being off.  It could be a master
abort, signaling that nothing is responding to accesses to 0x19020000 or
0x19021000.  I confirmed at the PROM prompt that accesses to these bases
returns 0xffffffff, which is commonly seen when master aborts occur.

If it's from the National, I'll have to look at the datasheet.  As you
said, it could have something to do with Marvell memory if the
descriptor ring hasn't been located there.

The reads from the Marvell registers for the PCI1 mapping look good.  It
also looks like the vendor id and device id is being read properly from
the Nat Semi MACs.

I'd say let's get the base addresses for the National MAC fixed up and
see if the PCI error goes away.


Brian



> -----Original Message-----
> From: Andy Sharp=20
> Sent: Wednesday, March 21, 2007 6:51 PM
> To: Brian Stark
> Subject: what is PCI error 0x200000?
>=20
> Inquiring minds want to know. Might have something to do with=20
> not using the Marvell memory, but hey.
>=20
> The latest trace output is at the end, and was produced with=20
> a kernel with no header fixups, all scanning etc.  It seems=20
> to have the best results so far, the the numbers that come=20
> out from the natsemi driver seem a little odd, but what do I=20
> know?  They don't correspond to the memory map but whatever.
>=20
> It's giving 0x19020000 as the start address for the first=20
> DP83816 and 0x19021000 as the start address for the second. =20
> But it's not complaining about the device not coming out of=20
> reset or any of the rest of that stuff.
>=20
> The messages above that for the mem0_base and mem0_base can=20
> be interpreted as follows: ignore bobcat_pci0_init, as they=20
> are for the init of the first PCI bus.  The lines
>=20
> bobcat_pci1_init: io_base =3D 0x18000000, io_size =3D 0x800000
> bobcat_pci1_init: mem0_base =3D 0x1a000000, mem0_size =3D 0x2000000
> bobcat_pci1_init: mem2_base =3D 0x18800000, mem2_size =3D 0x800000
> bobcat_pci1_init: mem1_base =3D 0x19000000, mem1_size =3D 0x1000000
>=20
> indicate all detected values.  I queried for all three memory=20
> windows, not in order, because I decided to use the mem1=20
> values to register the
> PCI-1 bus controller with the kernel.  You only get to=20
> specify one memory resource and one IO resource.
>=20
> What do you think?
>=20
> Cheers,
>=20
> a
>=20
>=20
>=20
>=20
>=20
>=20
>=20
>=20
>=20
>=20
> Booting Linux kernel...
> Linux version 2.6.20-bc9k-gf5483b8e-dirty (andys@ripper) (gcc=20
> version 4.1.2 20061115 (prerelease) (Debian 4.1.1-21)) #242=20
> Wed Mar 21 18:12:54 PDT 2007 CPU revision is: 00003440 FPU=20
> revision is: 00003420 OnStor Bobcat: Board Assembly Rev. A3=20
> Booting from recovery prom Bus clock speed: 133MHz Determined=20
> physical RAM map:
>  memory: 0d000000 @ 03000000 (usable)
> Built 1 zonelists.  Total pages: 32512
> Kernel command line: console=3DttyS0,57600n8 console=3DttyMM0=20
> root=3D/dev/nfs nfsroot=3D10.0.0.42:/var/nfsroot/bobcat,v3=20
> ip=3D10.2.9.7:10.0.0.42:10.2.0.1:255.255.255.0:b00bcat
> Primary instruction cache 16kB, physically tagged, 4-way,=20
> 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=20
> 399.994 MHz high precision timer.
> Dentry cache hash table entries: 16384 (order: 4, 65536=20
> bytes) Inode-cache hash table entries: 8192 (order: 3, 32768 bytes)
> Memory: 78208k/81920k available (1838k kernel code, 3620k=20
> reserved, 426k data, 124k init, 0k highmem)
> 796.67 BogoMIPS (lpj=3D398336)
> Mount-cache hash table entries: 512
> NET: Registered protocol family 16
> pci enable word =3D 0xffffc5f3
> bobcat_pci0_init: io_base =3D 0x0, io_size =3D 0x10000
> bobcat_pci0_init: mem0_base =3D 0x1d000000, mem0_size =3D 0x1000000
> bobcat_pci0_init: mv_io_base =3D 0x0, mv_io_size =3D 0x10000
> bobcat_pci1_init: io_base =3D 0x18000000, io_size =3D 0x800000
> bobcat_pci1_init: mem0_base =3D 0x1a000000, mem0_size =3D 0x2000000
> bobcat_pci1_init: mem2_base =3D 0x18800000, mem2_size =3D 0x800000
> bobcat_pci1_init: mem1_base =3D 0x19000000, mem1_size =3D 0x1000000
> bobcat_pci1_init: mem0_base =3D 0x19000000, mem0_size =3D 0x1000000
> bobcat_pci1_init: mv_io_base =3D 0x0, mv_io_size =3D 0x10000
> bobcat_pci1_init: mv_io_base =3D 0x18000000, mv_io_size =3D=20
> 0x800000 pci io_v_base =3D 0xb8000000
> PCI: Failed to allocate mem resource #0:20000000@20000000 for=20
> 0000:00:01.0
> PCI: Failed to allocate mem resource #2:20000000@20000000 for=20
> 0000:00:01.0
> PCI: Failed to allocate mem resource #4:2000000@1e000000 for=20
> 0000:00:01.3
> NET: Registered protocol family 2
> IP route cache hash table entries: 1024 (order: 0, 4096=20
> bytes) TCP established hash table entries: 4096 (order: 2,=20
> 16384 bytes) TCP bind hash table entries: 2048 (order: 1, 8192 bytes)
> TCP: Hash tables configured (established 4096 bind 2048) TCP=20
> reno registered io scheduler noop registered io scheduler=20
> 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 =3D 52) is a MPSC natsemi=20
> 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=3D0x100b, pdev->device=3D0x20
> PCI: Enabling device 0000:01:00.0 (0006 -> 0007)
> natsemi_probe1: iostart/sz for port 0 =3D 0x19020000/0x1000=20
> natsemi_probe1:ioaddr =3D b9020000 natsemi eth0: NatSemi=20
> DP8381[56] at 0x19020000 (0000:01:00.0), 00:07:34:02:9d:00,=20
> IRQ 8, port TP.
> natsemi_probe1: pdev->vendor=3D0x100b, pdev->device=3D0x20
> PCI: Enabling device 0000:01:01.0 (0006 -> 0007)
> natsemi_probe1: iostart/sz for port 1 =3D 0x19021000/0x1000=20
> natsemi_probe1:ioaddr =3D b9021000 natsemi eth1: NatSemi=20
> DP8381[56] at 0x19021000 (0000:01:01.0), 00:07:34:02:9d:01,=20
> IRQ 9, port TP.
> Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
> ide: Assuming 33MHz system bus speed for PIO modes; override=20
> with idebus=3Dxx 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
>=20
