|
|
|
|
|
|
|
|
|
|
xen-users
Re: [Xen-users] pcifront pci-0: pciback not responding (tg3)
I just duplicated your pci not responding error. I seem to hit it only
if I have my domU configured to use 4 processors. If I use less than
that my nic is up and working just fine. I'll file a bug against
SLES10. Does yours work if you use 1 proc?
Thanks,
Glen
>>> <buw20031220@xxxxxxxxxxxxxx> 06/01/06 5:30 pm >>>
> It is working for me on SLES10 RC2 x86_64, using the config in my
> previous post, I know this was busted in some earlier betas though.
>
good to hear this.
I just downloaded SLES10 xen build 9697 and the problem has slightly,
changed.
If a Network is specified in domU /etc/sysconfig/network/ifcfg- eth-
id- 00\:...
domU hangs in the boot.
domU dmesg:
pcifront pci- 0: pciback not responding!!!
tg3.c:v3.49 (Feb 2, 2006)
pcifront pci- 0: pciback not responding!!!
pcifront pci- 0: pciback not responding!!!
PCI: Enabling device 0000:00:00.1 (0000 - > 0002)
pcifront pci- 0: pciback not responding!!!
pcifront pci- 0: pciback not responding!!!
pcifront pci- 0: pciback not responding!!!
pcifront pci- 0: pciback not responding!!!
PCI: Setting latency timer of device 0000:00:00.1 to 64
pcifront pci- 0: pciback not responding!!!
pcifront pci- 0: pciback not responding!!!
tg3: Cannot find PowerManagement capability, aborting.
pcifront pci- 0: pciback not responding!!!
tg3: probe of 0000:00:00.1 failed with error - 5
Uniform Multi- Platform E- IDE driver Revision: 7.00alpha2
ide: Assuming 33MHz system bus speed for PIO modes; override with
idebus=xx
SCSI subsystem initialized
Driver 'sd' needs updating - please use bus_type methods
st: Version 20050830, fixed bufsize 32768, s/g segs 256
tg3.c:v3.49 (Feb 2, 2006)
eth0: Tigon3 [partno(349321- 001) rev 2100 PHY(5704)] (PCIX:100MHz:64-
bit)
10/100/1000BaseT Ethernet 00:17:08:4c:fe:f5
eth0: RXcsums[1] LinkChgREG[0] MIirq[0] ASF[0] Split[0] WireSpeed[1]
TSOcap[1]
eth0: dma_rwctrl[769f4000] dma_mask[64- bit]
pcifront pci- 0: pciback not responding!!!
pcifront pci- 0: pciback not responding!!!
dom0 boot parameter "pci=noacpi" won't help here, in this case the
system won't
boot at all.
So is it a problem specific to the Networking card ? Using bnx2 instead
does not
work at all.
_______________________________________________
Xen- users mailing list
Xen- users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen- users
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
|
|
|
|
|