On 09/01/2017 04:40 AM, Jose Abreu wrote:
I recently came upon a scenario where I would get a double fault
after a machine check error. It turns out that for Ksymbol lookup
to work with modules we need to have MMU enabled because module
address is mapped in the cached space.
This patch re-enable
Hi Jose,
On Fri, 2017-09-01 at 13:33 +0100, Jose Abreu wrote:
> Hi Alexey,
>
> On 01-09-2017 12:48, Alexey Brodkin wrote:
> >
> > Hi Jose,
> >
> > On Fri, 2017-09-01 at 12:39 +0100, Jose Abreu wrote:
> > >
> > > I recently came upon a scenario where I would get a double fault
> > > after a mac
Hi Alexey,
On 01-09-2017 12:48, Alexey Brodkin wrote:
> Hi Jose,
>
> On Fri, 2017-09-01 at 12:39 +0100, Jose Abreu wrote:
>> I recently came upon a scenario where I would get a double fault
>> after a machine check error. It turns out that for Ksymbol lookup
>> to work with modules we need to have
Hi Jose,
On Fri, 2017-09-01 at 12:39 +0100, Jose Abreu wrote:
> I recently came upon a scenario where I would get a double fault
> after a machine check error. It turns out that for Ksymbol lookup
> to work with modules we need to have MMU enabled because module
> address is mapped in the cached s
I recently came upon a scenario where I would get a double fault
after a machine check error. It turns out that for Ksymbol lookup
to work with modules we need to have MMU enabled because module
address is mapped in the cached space.
This patch re-enables the MMU before start printing the stacktra
