From: Alex Williamson <alex.williamson@redhat.com>
To: David Ahern <dsahern@gmail.com>
Cc: Avi Kivity <avi@redhat.com>, KVM <kvm@vger.kernel.org>
Subject: Re: hang on reboot with 3.6-rc1
Date: Thu, 09 Aug 2012 13:03:55 -0600 [thread overview]
Message-ID: <1344539035.3441.220.camel@ul30vt.home> (raw)
In-Reply-To: <5023FE9D.40803@gmail.com>
On Thu, 2012-08-09 at 12:17 -0600, David Ahern wrote:
> On 8/9/12 11:26 AM, Alex Williamson wrote:
> > On Thu, 2012-08-09 at 11:10 -0600, David Ahern wrote:
> >> On 8/9/12 3:42 AM, Avi Kivity wrote:
> >>> On 08/08/2012 07:27 PM, David Ahern wrote:
> >>>> Not sure if KVM is the culprit, but it is the last line shown on the
> >>>> console. I have to power cycle the server to reboot.
> >>>
> >>> Have you tried rmmoding the kvm modules before reboot?
> >>>
> >>> Were any guests running during this?
> >>
> >> hmm.... seems to be a side effect of https://lkml.org/lkml/2012/8/3/370.
> >
> > Is it fixed with the patches for that? We're operating on a NULL
> > pointer with that bug on your system, so you probably don't want to be
> > assuming the system is entirely healthy after you hit it. Thanks,
>
>
> Agreed and yes.
>
> Latest Linus tree has the iommu patch. Still need to get the other one
> in (https://lkml.org/lkml/2012/8/4/141) or whatever alternative is
> deemed better.
I think you should be ok with just what is in Linus' tree now. The
change in pci_acs_path_enabled is the same kind of bug, but I don't
think you'll hit it with the fixed iommu code. Please let me know if
that's not the case. Thanks,
Alex
next prev parent reply other threads:[~2012-08-09 19:03 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-08 16:27 hang on reboot with 3.6-rc1 David Ahern
2012-08-09 9:42 ` Avi Kivity
2012-08-09 17:10 ` David Ahern
2012-08-09 17:26 ` Alex Williamson
2012-08-09 18:17 ` David Ahern
2012-08-09 19:03 ` Alex Williamson [this message]
2012-08-09 19:35 ` David Ahern
2012-08-09 19:52 ` Alex Williamson
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=1344539035.3441.220.camel@ul30vt.home \
--to=alex.williamson@redhat.com \
--cc=avi@redhat.com \
--cc=dsahern@gmail.com \
--cc=kvm@vger.kernel.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).