From: "Luiz Fernando N. Capitulino" <lcapitulino@mandriva.com.br>
To: linux-kernel@vger.kernel.org
Cc: mathieu.desnoyers@polymtl.ca, mingo@elte.hu
Subject: 2.6.{26.2,27-rc} oops on virtualbox
Date: Wed, 20 Aug 2008 16:29:25 -0300 [thread overview]
Message-ID: <20080820162925.75a5e064@doriath.conectiva> (raw)
Hi there,
Users of different Linux distros (includes Ubuntu, Mandriva, ArchLinux and
possibly Fedora) are reporting that kernel 2.6.26.2 is OOPSing in the
Virtual Box emulator[1].
It is not clear if this is a kernel or Virtual Box bug, but as the kernel
is also OOPsing in QEMU (although with different behaivor) I have decided
to post my debug results here in case someone is interested in debugging
the kernel part further.
I have done a bisection by hand among kernel versions and found that
the commit which triggers the oops in _Virtual Box_ was introduced in
2.6.26-rc1 and the problem also happens with latest Linus tree.
By using git bisect I found that the commit is this:
"""
commit e587cadd8f47e202a30712e2906a65a0606d5865
Author: Mathieu Desnoyers <mathieu.desnoyers@polymtl.ca>
Date: Thu Mar 6 08:48:49 2008 -0500
x86: enhance DEBUG_RODATA support - alternatives
[...]
"""
By reverting this commit I don't get the OOPS anymore. I have
tested with 2.6.26-rc1 and latest Linus tree (2.6.27-rc3).
What puzzles me though is that a similar problem happens with
QEMU, but it also OOPSes with kernels before 2.6.26-rc1,
reverting the patch above makes no difference and it works with
current Linus tree.
Does this look like a kernel bug?
All my tests have been done with vanilla kernels, but I have
built .iso installation images with them and I'm not sure of
what the build script does.
[1] http://en.wikipedia.org/wiki/Virtual_box
Thanks for reading this.
--
Luiz Fernando N. Capitulino
next reply other threads:[~2008-08-20 19:31 UTC|newest]
Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-20 19:29 Luiz Fernando N. Capitulino [this message]
2008-08-21 21:34 ` H. Peter Anvin
2008-08-22 6:42 ` H. Peter Anvin
2008-08-22 6:50 ` Ingo Molnar
2008-08-22 14:39 ` Luiz Fernando N. Capitulino
2008-08-22 15:34 ` Mathieu Desnoyers
2008-08-22 16:29 ` Luiz Fernando N. Capitulino
2008-08-22 16:35 ` Mathieu Desnoyers
2008-08-22 17:20 ` Luiz Fernando N. Capitulino
2008-08-22 18:11 ` H. Peter Anvin
2008-08-22 19:40 ` Luiz Fernando N. Capitulino
2008-08-22 20:31 ` H. Peter Anvin
2008-08-22 20:55 ` Luiz Fernando N. Capitulino
2008-08-22 20:57 ` Luiz Fernando N. Capitulino
2008-08-22 21:08 ` H. Peter Anvin
2008-08-26 14:18 ` Gerhard Brauer
2008-08-26 14:53 ` Mathieu Desnoyers
2008-08-26 16:09 ` Luiz Fernando N. Capitulino
2008-08-26 16:13 ` Luiz Fernando N. Capitulino
2008-08-26 17:18 ` Mathieu Desnoyers
2008-08-26 17:32 ` H. Peter Anvin
2008-08-26 18:02 ` Luiz Fernando N. Capitulino
2008-08-26 18:15 ` Mathieu Desnoyers
2008-08-26 19:52 ` H. Peter Anvin
2008-08-26 20:34 ` Gerhard Brauer
2008-08-26 20:48 ` Mathieu Desnoyers
2008-08-26 21:25 ` Gerhard Brauer
2008-08-26 21:35 ` Mathieu Desnoyers
2008-08-26 21:51 ` H. Peter Anvin
2008-08-27 0:13 ` Gerhard Brauer
2008-08-27 19:13 ` Luiz Fernando N. Capitulino
2008-08-27 23:33 ` Mathieu Desnoyers
2008-08-28 13:30 ` Luiz Fernando N. Capitulino
2008-08-31 9:29 ` Gerhard Brauer
2008-08-31 13:28 ` Stefan Lippers-Hollmann
2008-08-31 14:03 ` Gerhard Brauer
2008-08-31 14:09 ` Luiz Fernando N. Capitulino
2008-09-21 13:41 ` Gerhard Brauer
2008-09-22 9:51 ` Ingo Molnar
2008-09-24 13:24 ` Luiz Fernando N. Capitulino
2008-08-28 13:50 ` Gerhard Brauer
2008-08-26 19:27 ` Gerhard Brauer
2008-08-26 16:02 ` Luiz Fernando N. Capitulino
2008-08-26 16:40 ` Gerhard Brauer
2008-08-22 17:16 ` H. Peter Anvin
2008-08-22 17:45 ` Mathieu Desnoyers
2008-08-22 17:57 ` H. Peter Anvin
2008-08-22 19:10 ` Luiz Fernando N. Capitulino
2008-08-22 19:14 ` H. Peter Anvin
2008-08-22 19:18 ` H. Peter Anvin
2008-08-22 19:42 ` Luiz Fernando N. Capitulino
2008-08-22 14:28 ` Luiz Fernando N. Capitulino
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=20080820162925.75a5e064@doriath.conectiva \
--to=lcapitulino@mandriva.com.br \
--cc=linux-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@polymtl.ca \
--cc=mingo@elte.hu \
/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
all inboxes | Powered by JetHome®