From: bugzilla-daemon@bugzilla.kernel.org
To: kvm@vger.kernel.org
Subject: [Bug 27052] Module KVM : unable to handle kernel NULL pointer dereference at
Date: Thu, 21 Apr 2011 12:13:35 GMT [thread overview]
Message-ID: <201104211213.p3LCDZeC016231@demeter2.kernel.org> (raw)
In-Reply-To: <bug-27052-28872@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=27052
--- Comment #40 from Avi Kivity <avi@redhat.com> 2011-04-21 12:13:33 ---
(In reply to comment #39)
> Is this issue resolved?
> I'm seeing almost the same issue with 2.6.38 + qemu-kvm-0.14.0 (on NEC
> Express5800/110Ge server), except that my backtrace is calling
> paging64_sync_page instead of paging32_sync_page.
Do you also have netfilter enabled on the host?
What happens if you enable debug options as per comment #29?
--
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.
next prev parent reply other threads:[~2011-04-21 12:13 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-19 10:04 [Bug 27052] New: Module KVM : unable to handle kernel NULL pointer dereference at bugzilla-daemon
2011-01-19 11:06 ` [Bug 27052] " bugzilla-daemon
2011-01-19 11:26 ` bugzilla-daemon
2011-01-19 11:34 ` bugzilla-daemon
2011-01-20 17:29 ` bugzilla-daemon
2011-01-20 17:30 ` bugzilla-daemon
2011-01-20 19:45 ` bugzilla-daemon
2011-01-21 3:27 ` bugzilla-daemon
2011-01-21 3:29 ` bugzilla-daemon
2011-01-25 8:49 ` bugzilla-daemon
2011-01-25 13:09 ` bugzilla-daemon
2011-01-25 13:35 ` bugzilla-daemon
2011-01-25 13:55 ` bugzilla-daemon
2011-01-25 17:08 ` bugzilla-daemon
2011-01-25 17:08 ` bugzilla-daemon
2011-01-25 17:29 ` bugzilla-daemon
2011-01-28 6:58 ` bugzilla-daemon
2011-02-04 21:11 ` bugzilla-daemon
2011-02-04 21:13 ` bugzilla-daemon
2011-02-08 9:46 ` bugzilla-daemon
2011-02-08 10:50 ` bugzilla-daemon
2011-02-10 8:25 ` bugzilla-daemon
2011-02-10 13:36 ` bugzilla-daemon
2011-02-10 13:50 ` bugzilla-daemon
2011-02-10 14:14 ` bugzilla-daemon
2011-02-10 14:16 ` bugzilla-daemon
2011-02-10 16:57 ` bugzilla-daemon
2011-02-10 16:58 ` bugzilla-daemon
2011-02-11 15:43 ` bugzilla-daemon
2011-02-11 21:33 ` bugzilla-daemon
2011-02-12 17:06 ` bugzilla-daemon
2011-02-13 16:11 ` bugzilla-daemon
2011-02-13 16:38 ` bugzilla-daemon
2011-02-13 19:39 ` bugzilla-daemon
2011-02-13 20:13 ` bugzilla-daemon
2011-02-14 14:52 ` bugzilla-daemon
2011-02-14 15:50 ` bugzilla-daemon
2011-02-14 15:51 ` bugzilla-daemon
2011-02-14 16:02 ` bugzilla-daemon
2011-04-21 11:45 ` bugzilla-daemon
2011-04-21 12:13 ` bugzilla-daemon [this message]
2011-04-21 12:39 ` 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=201104211213.p3LCDZeC016231@demeter2.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).