mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Vegard Nossum" <vegard.nossum@gmail.com>
To: "Ingo Molnar" <mingo@elte.hu>
Cc: "Pekka Enberg" <penberg@cs.helsinki.fi>, linux-kernel@vger.kernel.org
Subject: Re: kmemcheck: Caught 32-bit read from uninitialized memory (f6038ec0)
Date: Sun, 5 Oct 2008 14:42:35 +0200	[thread overview]
Message-ID: <19f34abd0810050542k607221acs526b38aaba36b501@mail.gmail.com> (raw)
In-Reply-To: <20080929131411.GA26442@elte.hu>

On Mon, Sep 29, 2008 at 3:14 PM, Ingo Molnar <mingo@elte.hu> wrote:
>
> another crash is below - config attached.
>
>        Ingo
>
> ----------------->
> initcall 0xc08eabf0 returned 0 after 7 msecs
> calling  0xc08eae70 @ 1
> PnPBIOS: Scanning system for PnP BIOS support...
> PnPBIOS: Found PnP BIOS installation structure at 0xc00fc550
> PnPBIOS: PnP BIOS version 1.0, entry 0xf0000:0xc580, dseg 0xf0000
> BUG: unable to handle kernel paging request at 0000c6ef

Thanks, I can reproduce it. And that's very interesting. Look at the
faulting address and the line just above:

    PnP BIOS version 1.0, entry 0xf0000:0xc580

When I run it, I get something similar:

    PnPBIOS: PnP BIOS version 1.0, entry 0xf0000:0x67ba, dseg 0xf0000
    BUG: unable to handle kernel paging request at 000068ac

Enabling debug information also gives me the location of the crash. It
happens in kmemcheck's opcode decoder, when we dereference regs->eip.
Is it possible that PnPBIOS is executing some code which is located at
these weird addresses (like 16-bit code) and requires a different
segment register?

Maybe we should just check regs->flags to make sure that we are not in
VM86 mode or similar. Will experiment a bit with it. Thanks.


Vegard

-- 
"The animistic metaphor of the bug that maliciously sneaked in while
the programmer was not looking is intellectually dishonest as it
disguises that the error is the programmer's own creation."
	-- E. W. Dijkstra, EWD1036

      reply	other threads:[~2008-10-05 12:42 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-28 18:06 [GIT PULL] kmemcheck fixlets (for -tip) Vegard Nossum
2008-09-29  7:54 ` Ingo Molnar
2008-09-29  7:59   ` Ingo Molnar
2008-09-29  8:55 ` Ingo Molnar
2008-09-29  9:13   ` Vegard Nossum
2008-09-29  9:25     ` Ingo Molnar
2008-09-29  9:43       ` Ingo Molnar
2008-09-29 11:13         ` Ingo Molnar
2008-09-29 11:57           ` kmemcheck: Caught 32-bit read from uninitialized memory (f6038ec0) Ingo Molnar
2008-09-29 13:14             ` Ingo Molnar
2008-10-05 12:42               ` Vegard Nossum [this message]

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=19f34abd0810050542k607221acs526b38aaba36b501@mail.gmail.com \
    --to=vegard.nossum@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=penberg@cs.helsinki.fi \
    /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®