From: "Roger Pau Monné" <roger.pau@citrix.com>
To: Adam Szewczyk <szewcson@gmail.com>
Cc: xen-devel@lists.xen.org
Subject: Re: [BUG] problems with NICs pass through to OpenBSD guest
Date: Fri, 16 Sep 2022 15:35:20 +0200 [thread overview]
Message-ID: <YyR7mIMh2htWkR7o@Air-de-Roger> (raw)
In-Reply-To: <YyR1eUfbq9aVSVXV@Air-de-Roger>
Again, please keep xen-devel on Cc and don't top-post.
On Fri, Sep 16, 2022 at 03:19:30PM +0200, Adam Szewczyk wrote:
> I executed it in dom0 terminal and it prints lots of stuff, but when I run
> jus xl dmesg it prints almost the same logs. So I'm not sure if I have
> right output or what I shuld search for to paste it here.
Hm, you should see something like:
(XEN) [ 8729.266567] MSI information:
[...]
(XEN) [ 8709.154958] IRQ information:
[...]
In the output of `xl dmesg`
You can paste the full output of `xl dmesg`, that should be fine.
> Regards Adam.
>
> pt., 16 wrz 2022, 15:09 użytkownik Roger Pau Monné <roger.pau@citrix.com>
> napisał:
>
> > Please keep xen-devel in Cc and avoid top-posting.
> >
> > On Fri, Sep 16, 2022 at 02:35:17PM +0200, Adam Szewczyk wrote:
> > > > 0:7:0: Intel AC 9560
> > > > 0x0000: Vendor ID: 8086, Product ID: a370
> > > > 0x0004: Command: 0006, Status: 0010
> > > > 0x0008: Class: 02 Network, Subclass: 80 Miscellaneous,
> > > > Interface: 00, Revision: 10
> > > > 0x000c: BIST: 00, Header Type: 80, Latency Timer: 00,
> > > > Cache Line Size: 00
> > > > 0x0010: BAR mem 64bit addr: 0x00000000f2014000/0x00004000
> > > > 0x0018: BAR empty (00000000)
> > > > 0x001c: BAR empty (00000000)
> > > > 0x0020: BAR empty (00000000)
> > > > 0x0024: BAR empty (00000000)
> > > > 0x0028: Cardbus CIS: 00000000
> > > > 0x002c: Subsystem Vendor ID: 8086 Product ID: 0034
> > > > 0x0030: Expansion ROM Base Address: 00000000
> > > > 0x0038: 00000000
> >
> > None of the BARs are at 0x404000 which seems to be where OpenBSD is
> > trying to load the firmware?
> >
> > I would have to look at the code to figure out exactly what it is
> > trying to do here (and why it fails).
> >
> > Can you also paste the output from `lspci -v`?
You seem to have missed this bit.
Regards, Roger.
next prev parent reply other threads:[~2022-09-16 13:35 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-16 6:22 [BUG] problems with NICs pass through to OpenBSD guest Adam Szewczyk
2022-09-16 9:37 ` Roger Pau Monné
[not found] ` <CAHsotTibs204KVYsm5E0x7ogUzpZOdmV4g_6LyD8RSkLnfJ0UA@mail.gmail.com>
2022-09-16 13:09 ` Roger Pau Monné
2022-09-16 13:35 ` Roger Pau Monné [this message]
2022-09-16 15:08 ` Adam Szewczyk
2022-09-16 19:26 ` Adam Szewczyk
2022-09-16 20:50 ` Adam Szewczyk
2022-09-19 9:21 ` Roger Pau Monné
2022-09-20 7:41 ` Adam Szewczyk
2022-09-20 8:12 ` Adam Szewczyk
2022-09-20 9:13 ` Roger Pau Monné
2022-09-21 8:59 ` Adam Szewczyk
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=YyR7mIMh2htWkR7o@Air-de-Roger \
--to=roger.pau@citrix.com \
--cc=szewcson@gmail.com \
--cc=xen-devel@lists.xen.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).