X-MimeOLE: Produced By Microsoft Exchange V6.5
Received: by onstor-exch02.onstor.net 
	id <01C80124.FEBF0342@onstor-exch02.onstor.net>; Thu, 27 Sep 2007 08:39:38 -0800
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Content-class: urn:content-classes:message
Subject: RE: system freezes/hangs when scanning PCI bus
Date: Thu, 27 Sep 2007 08:39:39 -0800
Message-ID: <BB375AF679D4A34E9CA8DFA650E2B04E05C028D2@onstor-exch02.onstor.net>
In-Reply-To: <20070926215733.3fc928ba@ripper.onstor.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: system freezes/hangs when scanning PCI bus
Thread-Index: AcgAwuw/fsfVWaIdSN+5AgecnF8L4AAYbYEg
References: <20070926215733.3fc928ba@ripper.onstor.net>
From: "Brian Stark" <brian.stark@onstor.com>
To: "Andy Sharp" <andy.sharp@onstor.com>

Andy,

First, let me make sure I'm following you here.  Are you trying to read
device 0, 16, 24, 32, 40, and 48?  If so, I'm not sure the 1125 supports
a read from device 48.  What's probably going on is that the 1125
continues to retry the transaction and nothing is ever responding. =20

Can you just limit the devices to 5, 6, 7, and 8?


Brian



> -----Original Message-----
> From: Andy Sharp=20
> Sent: Wednesday, September 26, 2007 9:58 PM
> To: Brian Stark
> Subject: system freezes/hangs when scanning PCI bus
>=20
> Here's the relevant kernel debug output that might even speak for
> itself:
>=20
>=20
> PCI: Scanning bus 0000:00
> scanning device bus:  ; devfn: 0
> preparing to read PCI_VENDOR_ID config keyword for devfn 0
> pci_scan_device: vendor id =3D 0x1166d
> PCI: Found 0000:00:00.0 [166d/0001] 000600 00
> PCI: Calling quirk ffffffff832bb468 for 0000:00:00.0 scanning=20
> device bus: 0 ; devfn: 8 preparing to read PCI_VENDOR_ID=20
> config keyword for devfn 8
> pci_scan_device: vendor id =3D 0xffffffff
> scanning device bus: 0 ; devfn: 16
> preparing to read PCI_VENDOR_ID config keyword for devfn 16
> pci_scan_device: vendor id =3D 0xffffffff
> scanning device bus: 0 ; devfn: 24
> preparing to read PCI_VENDOR_ID config keyword for devfn 24
> pci_scan_device: vendor id =3D 0xffffffff
> scanning device bus: 0 ; devfn: 32
> preparing to read PCI_VENDOR_ID config keyword for devfn 32
> pci_scan_device: vendor id =3D 0xffffffff
> scanning device bus: 0 ; devfn: 40
> preparing to read PCI_VENDOR_ID config keyword for devfn 40
> pci_scan_device: vendor id =3D 0xffffffff
> scanning device bus: 0 ; devfn: 48
> preparing to read PCI_VENDOR_ID config keyword for devfn 48
>=20
> And here it hangs until the watchdog kicks.
>=20
> This is the first line of code after the last print:
>=20
> pci_bus_read_config_dword(bus, devfn, PCI_VENDOR_ID, &l);
>=20
> devfn being 48, PCI_VENDOR_ID being 0, bus being the bus, and=20
> l being where to put the result of the read.
>=20
> it never returns.
>=20
> Any ideas?
>=20
> Thanks,
>=20
> a
>=20
>=20
