[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <19f34abd0807271240x71fb85e3qae5d7beaad6eaba3@mail.gmail.com>
Date: Sun, 27 Jul 2008 21:40:46 +0200
From: "Vegard Nossum" <vegard.nossum@...il.com>
To: "Thomas Gleixner" <tglx@...utronix.de>
Cc: "Dmitry Adamushko" <dmitry.adamushko@...il.com>,
lkml <linux-kernel@...r.kernel.org>,
"Thomas Meyer" <thomas@...3r.de>,
"the arch/x86 maintainers" <x86@...nel.org>
Subject: Re: -git: BUG: unable to handle kernel paging request at c0100248 [CPU hotplug]
On Sun, Jul 27, 2008 at 9:35 PM, Vegard Nossum <vegard.nossum@...il.com> wrote:
> On Sun, Jul 27, 2008 at 9:23 PM, Thomas Gleixner <tglx@...utronix.de> wrote:
>> On Sun, 27 Jul 2008, Vegard Nossum wrote:
>>> Booting processor 1/1 ip 6000
>>> Initializing CPU#1
>>> [...]
>>> Write protecting the kernel text: 5648k
>>>
>>> So it succeeds because the protection happens much later :-)
>>
>> Patch below fixes the issue. I get it to Linus ASAP.
>
> Nice :)
>
> [...]
>
>> +.section .cpuinit.data,"wa"
>> +.align 4
>> +ENTRY(initial_code)
>> + .long i386_start_kernel
>> +
>> .section .text
>> /*
>> * Real beginning of normal "text" segment
>>
>
> Hm, isn't there some kind of "section stack" that can be used to
> restore the previous section? .pushsection/.popsection directives?
Oh, never mind :-)
(Sorry for the noise.)
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
--
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