From: "B.G. Bruce" <bgb@nt-nv.com>
To: xen-devel <xen-devel@lists.sourceforge.net>
Subject: Re: Driver domain: e1000 pci error
Date: Tue, 01 Feb 2005 09:22:31 -0400 [thread overview]
Message-ID: <1107264150.4411.25.camel@master.vms.security> (raw)
In-Reply-To: <1107199668.4566.248.camel@master.vms.security>
Sorry this issue has already been addressed under "Multiple network
interfaces setup".
B.
On Mon, 2005-01-31 at 15:27, B.G. Bruce wrote:
> I'm trying to build a driver dom for an Intel E1000, but I keep getting:
>
> Intel(R) PRO/1000 Network Driver - version 5.5.4-k2
> Copyright (c) 1999-2004 Intel Corporation.
> PCI: Obtained IRQ 18 for device 0000:01:01.0
> PCI: Setting latency timer of device 0000:01:01.0 to 64
> e1000: probe of 0000:01:01.0 failed with error -5
>
> Has anyone else run into this before? or have nay ideas on how to
> correct this?
>
> (Yes, the pci device is excluded from DOM0, and the correct pci=
> statement is in my config).
>
> B.
>
>
> -------------------------------------------------------
> This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
> Tool for open source databases. Create drag-&-drop reports. Save time
> by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
> Download a FREE copy at http://www.intelliview.com/go/osdn_nl
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/xen-devel
>
-------------------------------------------------------
This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
Tool for open source databases. Create drag-&-drop reports. Save time
by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
Download a FREE copy at http://www.intelliview.com/go/osdn_nl
prev parent reply other threads:[~2005-02-01 13:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-31 19:27 Driver domain: e1000 pci error B.G. Bruce
2005-02-01 13:22 ` B.G. Bruce [this message]
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=1107264150.4411.25.camel@master.vms.security \
--to=bgb@nt-nv.com \
--cc=xen-devel@lists.sourceforge.net \
/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.