kvm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: kvm@vger.kernel.org
Subject: [Bug 60850] New: BUG: Bad page state in process libvirtd pfn:76000
Date: Wed, 04 Sep 2013 21:10:04 +0000	[thread overview]
Message-ID: <bug-60850-28872@https.bugzilla.kernel.org/> (raw)

https://bugzilla.kernel.org/show_bug.cgi?id=60850

            Bug ID: 60850
           Summary: BUG: Bad page state in process libvirtd pfn:76000
           Product: Virtualization
           Version: unspecified
    Kernel Version: 3.11
          Hardware: x86-64
                OS: Linux
              Tree: Mainline
            Status: NEW
          Severity: normal
          Priority: P1
         Component: kvm
          Assignee: virtualization_kvm@kernel-bugs.osdl.org
          Reporter: alexanderyt@gmail.com
        Regression: No

Created attachment 107419
  --> https://bugzilla.kernel.org/attachment.cgi?id=107419&action=edit
The part of dmesg  (3.11)

This bug reproduced on kernel 3.11 and earlier. 
Steps to reproduce:
1. Add intel_iommu=on in kernel boot cmdline
2. Dettach some NIC from host: for example
# virsh nodedev-dettach pci_0000_02_00_1

I attached dmesg of kernel 3.11. And more info avaible in
https://bugs.gentoo.org/show_bug.cgi?id=477258 and
https://bugs.launchpad.net/ubuntu/+source/ipxe/+bug/1181777, the post #23

-- 
You are receiving this mail because:
You are watching the assignee of the bug.

             reply	other threads:[~2013-09-04 21:10 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-04 21:10 bugzilla-daemon [this message]
2013-09-05  7:46 ` [Bug 60850] BUG: Bad page state in process libvirtd pfn:76000 bugzilla-daemon
2013-09-15 11:46 ` bugzilla-daemon
2016-03-24  1:59 ` bugzilla-daemon

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=bug-60850-28872@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@bugzilla.kernel.org \
    --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).