From: James Courtier-Dutton <James@superbug.demon.co.uk>
To: linux-kernel@vger.kernel.org
Subject: no vm86_info: BAD
Date: Tue, 29 Sep 2009 19:33:00 +0100 [thread overview]
Message-ID: <4AC252DC.9070209@superbug.demon.co.uk> (raw)
Hi,
I have a system that sees this message "no vm86_info: BAD"
This happens while doing an "aptitude update", inside a qemu virtual
machine, and causes the http module to segv. This is with kernel 2.6.30
and 2.6.31. Using an older kernel in the virtual machine, cures the problem.
When I move the virtual machine image to another machine, it runs
perfectly OK, so I think that this will be difficult to reproduce elsewhere.
I would like to track this down, can anyone who has knowledge of this
area of the kernel please provide me with some pointers.
Kind Regards
James
reply other threads:[~2009-09-29 18:53 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=4AC252DC.9070209@superbug.demon.co.uk \
--to=james@superbug.demon.co.uk \
--cc=linux-kernel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.