qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Michael S. Tsirkin" <mst@redhat.com>
To: Blue Swirl <blauwirbel@gmail.com>
Cc: Mark Cave-Ayland <mark.cave-ayland@ilande.co.uk>,
	Avi Kivity <avi@redhat.com>,
	Anthony Liguori <anthony@codemonkey.ws>,
	qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] pci: fix bridge IO/BASE
Date: Sun, 4 Mar 2012 15:21:17 +0200	[thread overview]
Message-ID: <20120304132116.GA12047@redhat.com> (raw)
In-Reply-To: <CAAu8pHvSbp_vGFic782dS9+U6UfLpgx0iDiXQCJns1DsZ3j1pw@mail.gmail.com>

On Sun, Mar 04, 2012 at 12:46:23PM +0000, Blue Swirl wrote:
> On Sun, Mar 4, 2012 at 12:41, Avi Kivity <avi@redhat.com> wrote:
> > On 03/04/2012 02:38 PM, Blue Swirl wrote:
> >> >>
> >> >> This unassigned memory exception is triggered because CMD646 IDE I/O
> >> >> registers are not accessible:
> >> >>
> >> >> (qemu) info pci
> >> >>   Bus  0, device   5, function 0:
> >> >>     IDE controller: PCI device 1095:0646
> >> >>       IRQ 1.
> >> >>       BAR0: I/O at 0xffffffffffffffff [0x0006].
> >> >>       BAR1: I/O at 0xffffffffffffffff [0x0002].
> >> >>       BAR2: I/O at 0xffffffffffffffff [0x0006].
> >> >>       BAR3: I/O at 0xffffffffffffffff [0x0002].
> >> >>       BAR4: I/O at 0xffffffffffffffff [0x000e].
> >> >>       id ""
> >> >
> >> > The BARs are not initialized, so they aren't accessible.
> >> >
> >> > But perhaps the dump was not taken at the point of failure, can you
> >> > provide a relevant dump if so?
> >>
> >> No, this is after failure.
> >
> > I don't see why the guest expects the BARs to work then.
> 
> OpenBIOS could initialize them before this commit, now it obviously
> can't (or initializes the bridges incorrectly).

I traced all config reads and writes to the bridge
and there's no difference I can see
between before and after this commit.

I think there's some other bug, tweaking this
specific bit just happens to trigger it.

> Maybe also the devices should be moved behind the bridges, that's
> where they really should be.
> 
> >
> > --
> > error compiling committee.c: too many arguments to function
> >

  reply	other threads:[~2012-03-04 13:21 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-04  9:46 [Qemu-devel] [PATCH] pci: fix bridge IO/BASE Michael S. Tsirkin
2012-03-04 10:27 ` Blue Swirl
2012-03-04 12:21   ` Michael S. Tsirkin
2012-03-04 12:37     ` Blue Swirl
2012-03-04 13:28       ` Michael S. Tsirkin
2012-03-04 13:38         ` Blue Swirl
2012-03-04 14:23           ` Michael S. Tsirkin
2012-03-04 14:35             ` Blue Swirl
2012-03-04 15:22               ` Michael S. Tsirkin
2012-03-04 17:07                 ` Blue Swirl
2012-03-04 17:35                   ` Michael S. Tsirkin
2012-03-04 19:51                     ` Blue Swirl
2012-03-04 20:02                       ` Michael S. Tsirkin
2012-03-04 20:32                         ` Blue Swirl
2012-03-04 21:28                           ` Michael S. Tsirkin
2012-03-04 21:54                             ` Blue Swirl
2012-03-04 22:29                               ` Michael S. Tsirkin
2012-03-05 18:34                                 ` Blue Swirl
2012-03-06 13:42                                   ` Michael S. Tsirkin
2012-03-04 21:56                       ` Mark Cave-Ayland
2012-03-04 15:41               ` Michael S. Tsirkin
2012-03-04 13:38       ` Michael S. Tsirkin
2012-03-04 12:28   ` Avi Kivity
2012-03-04 12:38     ` Blue Swirl
2012-03-04 12:41       ` Avi Kivity
2012-03-04 12:46         ` Blue Swirl
2012-03-04 13:21           ` Michael S. Tsirkin [this message]
2012-03-04 13:22         ` Michael S. Tsirkin
2012-03-04 13:33           ` Blue Swirl
2012-03-04 14:08             ` Michael S. Tsirkin
2012-03-04 14:26               ` Blue Swirl
2012-03-04 16:42                 ` Michael S. Tsirkin
2012-03-04 17:49                   ` Blue Swirl
2012-03-04 18:11                     ` Mark Cave-Ayland
2012-03-04 19:27                       ` Michael S. Tsirkin
2012-03-04 19:43                       ` Michael S. Tsirkin
2012-03-04 19:27                     ` Michael S. Tsirkin
2012-03-04 12:33   ` Michael S. Tsirkin
2012-03-04 12:35     ` Avi Kivity
2012-03-04 12:35     ` Michael S. Tsirkin
2012-03-04 12:42     ` Blue Swirl

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=20120304132116.GA12047@redhat.com \
    --to=mst@redhat.com \
    --cc=anthony@codemonkey.ws \
    --cc=avi@redhat.com \
    --cc=blauwirbel@gmail.com \
    --cc=mark.cave-ayland@ilande.co.uk \
    --cc=qemu-devel@nongnu.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).