WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-bugs

Re: [Xen-devel] Re: [Xen-bugs] Re: [Xen-users] Network problem after upd

Konrad,
the version that I refer in all my comments is 5.5, not 3.5.
I' sorry.


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 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?

> 
> 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?

--------------------------------------------
empelt
Francisco Barrera

Móvil - +34 659253221
francisco.barrera@xxxxxxxxx
http://www.empelt.es







Antes de imprimir este e-mail piense en su responsabilidad compromiso con el medio ambiente

AVISO LEGAL
Este mensaje y los documentos anexos que pudiera incluir se dirige exclusivamente a su/s destinatario/s y puede contener información privilegiada o confidencial. Si no es ud. el destinatario del mensaje, le rogamos que lo comunique inmediatamente al remitente y proceda a su destrucción. La utilización, grabación, divulgación, copia o cualquier otro uso de la información sin el consentimiento de EMPELT está prohibida en virtud de la legislación vigente.

EMPELT cumple la Ley Orgánica 15/99 de 14 de Diciembre de Protección de Datos de Carácter Personal. Su e-mail y datos personales pueden estar incluidos en un fichero para su tratamiento. En cualquier momento puede ejercer sus derechos de acceso, rectificación, cancelación y oposición, mediante el envío de un e-mail o comunicación por escrito.





Before printing think about your responsability and commitment with the environment

DISCLAIMER
This message and all its attached documents is intended exclusively for its addressee(s) and may contain information that is confidential and protected by a professional privilege or whose disclosure is prohibited by law. If this message has been received by mistake, please we require to notify the sender immediately via e-mail and delete it. Any dissemination, copy, disclosure or, in any other way, using any of the information without the EMPELT consent is strictly prohibited by law.

EMPELT meets the Organica Law 15/99 of December 14 for the Protection of Personal Data. Your e-mail and personal information can be included in a file for treatment. In any moment you can exercise their rigths of access, rectification, cancellation and oposition by sending and e-mail or written communication.
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel