All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Andrew Lyon <andrew.lyon@gmail.com>
Cc: Xen-devel <xen-devel@lists.xensource.com>
Subject: Re: Xen killing my e1000s?
Date: Sun, 13 Dec 2009 11:09:10 -0800	[thread overview]
Message-ID: <4B253BD6.8010903@goop.org> (raw)
In-Reply-To: <f4527be0912120616o57ee2b10gf6d1e61a09ef2841@mail.gmail.com>

On 12/12/09 06:16, Andrew Lyon wrote:
> Have you tried using the latest version of the e1000 driver from intel
> rather than the in-kernel one? I've had the same problem when using
> older kernels on systems with e1000 and Xen, I used the intel driver
> for a while but once I switched to using a newer dom0 kernel the
> problem went away.
>    

Which drivers are those?

I've been reproducing this fairly reliably with the stock F12 kernel, so 
I think Xen is off the hook.  Still unsure whether its a driver problem 
or something to do with the platform (hardware/BIOS/etc).  It's an Ibex 
Peak-based system, which I think it relatively new.  The BIOS is 1.0a, 
so is probably due for an update...

     J

  parent reply	other threads:[~2009-12-13 19:09 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-11 23:36 Xen killing my e1000s? Jeremy Fitzhardinge
2009-12-12  0:11 ` Nathan Stratton
2009-12-12  0:22   ` Jeremy Fitzhardinge
2009-12-12 14:16 ` Andrew Lyon
2009-12-12 15:07   ` Pygrub cannot detect kernel on ISO image at Xen 4.0-rc1-pre Dom0 Boris Derzhavets
2009-12-13 19:09   ` Jeremy Fitzhardinge [this message]
2009-12-13 19:17     ` Xen killing my e1000s? Andrew Lyon

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=4B253BD6.8010903@goop.org \
    --to=jeremy@goop.org \
    --cc=andrew.lyon@gmail.com \
    --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.