All of lore.kernel.org
 help / color / mirror / Atom feed
From: David F Barrera <dfbp@us.ibm.com>
To: Ian Pratt <m+Ian.Pratt@cl.cam.ac.uk>
Cc: xen-devel@lists.xensource.com
Subject: Re: help with bugs
Date: Thu, 04 Aug 2005 16:29:14 -0500	[thread overview]
Message-ID: <42F288AA.3040804@us.ibm.com> (raw)
In-Reply-To: <A95E2296287EAD4EB592B5DEEFCE0E9D282970@liverpoolst.ad.cl.cam.ac.uk>



Ian Pratt wrote:

>>>I'd like to appeal for some help tracking down a couple of bugs that 
>>>we're struggling to reproduce:
>>>
>>>BUG62  eth0 -> veth0 in network script can loose network
>>> 
>>>
>>>      
>>>
>>I've been able to reproduce this problem frequently on SLES 9 
>>SP2 based platforms, x86 and x86_64. It seems that when I 
>>first reported the problem it happened very infrequently, and 
>>I could not reliably reproduce it. Now, I seems to be 
>>happening all the time on my SLES 9 boxes; curiously, it does 
>>not seem to happen on my FC/RH boxes.
>>    
>>
>
>Is there anything unusal about the SLES9 setup, e.g. multiple phsical
>interfaces, alias addresses on interfaces etc?
>  
>
No, nothing unusual. In fact, in one case, I have a machine that has 
both SLES 9 and FC3. When I build Xen on SLES 9 and boot Dom0, I can 
recreate the problem. On the same machine, when I build Xen on FC3 and 
boot Dom0, the problem does not occur. I built Xen the same way in both 
instances; the setups are the same with regards to Xen, the only 
variable (and a big one) is the distro.

>Have you tried my suggestion of adding 'promisc' to the ifconfig up
>lines in the script?
>  
>
Yes, and the problem still occurred.

>Thanks,
>Ian
>
>  
>

  reply	other threads:[~2005-08-04 21:29 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-04 21:02 help with bugs Ian Pratt
2005-08-04 21:29 ` David F Barrera [this message]
2005-08-04 21:55   ` Paul Larson
2005-08-05  3:10     ` David F Barrera
  -- strict thread matches above, loose matches on Subject: below --
2005-08-10 18:39 Ian Pratt
2005-08-10 19:00 ` Nivedita Singhvi
2005-08-05 14:22 Ian Pratt
2005-08-05  9:12 Ian Pratt
2005-08-05 13:20 ` Gerd Knorr
2005-08-10 18:38   ` Nivedita Singhvi
2005-08-04 21:48 Ian Pratt
2005-08-04 22:21 ` Sean Dague
2005-08-04 15:04 Ian Pratt
2005-08-04 19:53 ` Anthony Liguori
2005-08-04 20:18 ` Sean Dague
2005-08-04 20:49 ` David F Barrera
2005-08-05  8:29 ` Gerd Knorr

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=42F288AA.3040804@us.ibm.com \
    --to=dfbp@us.ibm.com \
    --cc=m+Ian.Pratt@cl.cam.ac.uk \
    --cc=xen-devel@lists.xensource.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.