[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <49E4517B.4020301@goop.org>
Date: Tue, 14 Apr 2009 02:03:55 -0700
From: Jeremy Fitzhardinge <jeremy@...p.org>
To: "H. Peter Anvin" <hpa@...or.com>
CC: Ingo Molnar <mingo@...e.hu>,
"H. Peter Anvin" <hpa@...ux.intel.com>,
alan-jenkins@...fmail.co.uk, Avi Kivity <avi@...hat.com>,
Linus Torvalds <torvalds@...ux-foundation.org>,
Pavel Machek <pavel@....cz>, mingo@...hat.com,
linux-kernel@...r.kernel.org, tglx@...utronix.de, rjw@...k.pl,
linux-tip-commits@...r.kernel.org
Subject: Re: [tip:x86/setup] x86, setup: "glove box" BIOS calls -- infrastructure
H. Peter Anvin wrote:
> Ingo Molnar wrote:
>
>> ... looks like an x86 descriptor table. Does the pattern below make
>> any sense to anyone? I've attached the relevant bits of one of the
>> reports below.
>>
>>
>
> It's weird... it's clearly not random, but the pattern is shifting all
> over the place. Almost makes me want to guess some kind of bitmask (the
> 0xaaaaaa00 bit and the stretches of 00 and ff kind of hint that way) but
> even then it doesn't really seem to make a whole lot of sense. Perhaps
> it's a data segment of some code which is barfing on memory.
>
> 960 bytes at 0xc000 (48K)... almost makes one wonder if someone confused
> address 0xc000 with segment 0xc000 (the VGA BIOS)...
>
(I wonder if its a bunch of super-secret HDMI crypto keys ;)
J
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists