[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] Re: [Xen-devel] Re: [Xen-bugs] Re: [Xen-users] Network problem after updates
El mar, 22-06-2010 a las 10:41 -0400, Konrad Rzeszutek Wilk escribió: On Tue, Jun 22, 2010 at 04:23:13PM +0200, Francisco Barrera wrote: > Hello Konrad, > > I follow your suggestion and I downgrade the Xen dom0 and hipervisor to > the 3.1.2 vesion and 2.6.18-194.3.1.el5xen kernel (versions by default > in RHEL 3.5). > > At this moment all works fine, but this message in /var/log/mesages > worry me a lot: > > pciback 0000:09:00.0: Driver tried to write to a read-only configuration > space field at offset 0x4c, size 2. This may be harmless, but if you > have problems with your device: > 1) see permissive attribute in sysfs > 2) report problems to the xen-devel mailing list along with details of > your device obtained from lspci. Well, do the second. Get the 'lspci -vvv' output of the device and lets take a look at what offset 0x4c is? If might be complelty benign at which point your problem is with something else. This is the output of 'lspci -vvv' of the device: 09:00.0 Ethernet controller: Broadcom Corporation NetXtreme II BCM5708 Gigabit Ethernet (rev 12) Subsystem: Broadcom Corporation NetXtreme II BCM5708 Gigabit Ethernet Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- Latency: 64 (16000ns min), Cache Line Size: 64 bytes Interrupt: pin A routed to IRQ 19 Region 0: Memory at d2000000 (64-bit, non-prefetchable) [size=32M] Capabilities: [40] PCI-X non-bridge device Command: DPERE- ERO- RBC=512 OST=8 Status: Dev=09:00.0 64bit+ 133MHz+ SCD- USC- DC=simple DMMRBC=512 DMOST=8 DMCRS=32 RSCEM- 266MHz- 533MHz- Capabilities: [48] Power Management version 2 Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot+,D3cold+) Status: D0 PME-Enable- DSel=0 DScale=1 PME- Capabilities: [50] Vital Product Data Capabilities: [58] Message Signalled Interrupts: 64bit+ Queue=0/0 Enable- Address: ffedf9efbfff9fec Data: de3f Anything appears in reference of 0x4c, or I don't understand you. > > This is the same message that appears in the previous update to xen > 3.4.1 that I did make, and at the moment to make it, all works fine > also. > Then, after a lot of network traffic, the system began to freeze, as I > describe in my first message. Just to make sure I comprehend this properly. 1). You are running the same software setup you did months ago after a brief update. 2). Your machine freezes. But it did not freeze months ago when you ran the same software setup? No, I don't explain correctly, I'm sorry for my English. 1). The software version running actually is the above I write, 3.1.2 in xen hypervisor and 2.6.18-194.3.1.el5xen in kernel, that are the versions by default in CentOS 3.5. The software version running before the update to xen 3.4.1 was CentOS-5.2 with Xen 3.0.3 and 2.6.18.128.el5xen kernel. I've installed CentOS 3.5 because I assumed this versions are stables. 2). Now my machine don't freezes, but I suspect that will freezes when network traffic overloads some buffer > > The question is if I add the address in the message in the > xend-pci-permissive file can solve this, or if I need to downgrade to > lower version to avoid it. I am definitly missing something here. You did have a stable version at some point that did not exhibit any problems, correct? Is that the version you are running now? Ok, I've a stable version running now (that cames in CentOS 3.5), and at the moment I don't have any problem, only the message that I comment above.
_______________________________________________ Xen-devel mailing list Xen-devel@xxxxxxxxxxxxxxxxxxx http://lists.xensource.com/xen-devel
|
Lists.xenproject.org is hosted with RackSpace, monitoring our |