From: Antoine Reversat <a.reversat@gmail.com>
To: linux-mm@kvack.org
Subject: Re: [BUG] Kernel panic on >= 4.12 because of NX
Date: Tue, 6 Aug 2019 13:34:16 -0400 [thread overview]
Message-ID: <CAA=2nCZNA5iGQk3QRCzAbSMrCst0oWqi_OCLEO6A7Ux8A3+dbg@mail.gmail.com> (raw)
In-Reply-To: <CAA=2nCZbZDxF4bDQ22Lu0fbUyzmCAoWJKtU1XLrfdtmkJ84J9w@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 5934 bytes --]
As it turns out adding the efi=old_map kernel parameter (and removing
noexec=off) also fixes the issue.
Le mar. 6 août 2019 à 12:25, Antoine Reversat <a.reversat@gmail.com> a
écrit :
> Could this be caused by the fact that this machine uses a 32bit efi bios
> on a 64bit platform ?
>
> Le mar. 6 août 2019 à 12:23, Antoine Reversat <a.reversat@gmail.com> a
> écrit :
>
>> On a booted 5.2.5, at the point where I see the panic I get :
>>
>> [ 0.183953] efi: Error mapping PA 0x0 -> VA 0x0!
>> [ 0.183956] efi: Error mapping PA 0x90000 -> VA 0x90000!
>> [ 0.183959] efi: Error mapping PA 0x100000 -> VA 0x100000!
>> [ 0.183961] efi: Error mapping PA 0x2165000 -> VA 0x2165000!
>> [ 0.183963] efi: Error mapping PA 0x2200000 -> VA 0x2200000!
>> [ 0.183966] efi: Error mapping PA 0x4265000 -> VA 0x4265000!
>> [ 0.183968] efi: Error mapping PA 0x30ae7000 -> VA 0x30ae7000!
>> [ 0.183971] efi: Error mapping PA 0x3456b000 -> VA 0x3456b000!
>> [ 0.183973] efi: Error mapping PA 0x5d590000 -> VA 0x5d590000!
>> [ 0.183975] efi: Error mapping PA 0x7c84e000 -> VA 0x7c84e000!
>> [ 0.183978] efi: Error mapping PA 0x7c864000 -> VA 0x7c864000!
>> [ 0.183980] efi: Error mapping PA 0x7c86f000 -> VA 0x7c86f000!
>> [ 0.183982] efi: Error mapping PA 0x7c891000 -> VA 0x7c891000!
>> [ 0.183985] efi: Error mapping PA 0x7c8cb000 -> VA 0x7c8cb000!
>> [ 0.183987] efi: Error mapping PA 0x7c8d0000 -> VA 0x7c8d0000!
>> [ 0.183989] efi: Error mapping PA 0x7d0d6000 -> VA 0x7d0d6000!
>> [ 0.183992] efi: Error mapping PA 0x7d0d9000 -> VA 0x7d0d9000!
>> [ 0.183994] efi: Error mapping PA 0x7d0de000 -> VA 0x7d0de000!
>> [ 0.183996] efi: Error mapping PA 0x7d0df000 -> VA 0x7d0df000!
>> [ 0.183999] efi: Error mapping PA 0x7d11c000 -> VA 0x7d11c000!
>> [ 0.184001] efi: Error mapping PA 0x7d11d000 -> VA 0x7d11d000!
>> [ 0.184003] efi: Error mapping PA 0x7e776000 -> VA 0x7e776000!
>> [ 0.184006] efi: Error mapping PA 0x7e78b000 -> VA 0x7e78b000!
>> [ 0.184008] efi: Error mapping PA 0x7e7cb000 -> VA 0x7e7cb000!
>> [ 0.184010] efi: Error mapping PA 0x7e7cc000 -> VA 0x7e7cc000!
>> [ 0.184013] efi: Error mapping PA 0x7e7d6000 -> VA 0x7e7d6000!
>> [ 0.184015] efi: Error mapping PA 0x7e7d9000 -> VA 0x7e7d9000!
>> [ 0.184017] efi: Error mapping PA 0x7e7dd000 -> VA 0x7e7dd000!
>> [ 0.184020] efi: Error mapping PA 0x7e7e0000 -> VA 0x7e7e0000!
>> [ 0.184022] efi: Error mapping PA 0x7e7e2000 -> VA 0x7e7e2000!
>> [ 0.184025] efi: Error mapping PA 0x7e7e3000 -> VA 0x7e7e3000!
>> [ 0.184027] efi: Error mapping PA 0x7e7e6000 -> VA 0x7e7e6000!
>> [ 0.184029] efi: Error mapping PA 0x7e7e9000 -> VA 0x7e7e9000!
>> [ 0.184032] efi: Error mapping PA 0x7e7eb000 -> VA 0x7e7eb000!
>> [ 0.184034] efi: Error mapping PA 0x7e7ec000 -> VA 0x7e7ec000!
>> [ 0.184036] efi: Error mapping PA 0x7e801000 -> VA 0x7e801000!
>> [ 0.184039] efi: Error mapping PA 0x7e812000 -> VA 0x7e812000!
>> [ 0.184041] efi: Error mapping PA 0x7e823000 -> VA 0x7e823000!
>> [ 0.184043] efi: Error mapping PA 0x7e82b000 -> VA 0x7e82b000!
>> [ 0.184046] efi: Error mapping PA 0x7e82e000 -> VA 0x7e82e000!
>> [ 0.184048] efi: Error mapping PA 0x7e831000 -> VA 0x7e831000!
>> [ 0.184050] efi: Error mapping PA 0x7e94d000 -> VA 0x7e94d000!
>> [ 0.184053] efi: Error mapping PA 0x7e96f000 -> VA 0x7e96f000!
>> [ 0.184055] efi: Error mapping PA 0x7e997000 -> VA 0x7e997000!
>> [ 0.184057] efi: Error mapping PA 0x7e9a4000 -> VA 0x7e9a4000!
>> [ 0.184060] efi: Error mapping PA 0x7e9b2000 -> VA 0x7e9b2000!
>> [ 0.184062] efi: Error mapping PA 0x7ec26000 -> VA 0x7ec26000!
>> [ 0.184065] efi: Error mapping PA 0x7ec27000 -> VA 0x7ec27000!
>> [ 0.184067] efi: Error mapping PA 0x7f5f7000 -> VA 0x7f5f7000!
>> [ 0.184069] efi: Error mapping PA 0x7f6f7000 -> VA 0x7f6f7000!
>> [ 0.184072] efi: Error mapping PA 0x7f7e1000 -> VA 0x7f7e1000!
>> [ 0.184074] efi: Error mapping PA 0x7f7f7000 -> VA 0x7f7f7000!
>> [ 0.184076] efi: Error mapping PA 0x7f8ca000 -> VA 0x7f8ca000!
>> [ 0.184079] efi: Error mapping PA 0x7f8f7000 -> VA 0x7f8f7000!
>> [ 0.184081] efi: Error mapping PA 0x7fb7b000 -> VA 0x7fb7b000!
>> [ 0.184083] efi: Error mapping PA 0x7fb89000 -> VA 0x7fb89000!
>> [ 0.184086] efi: Error mapping PA 0x7fbbb000 -> VA 0x7fbbb000!
>> [ 0.184088] efi: Error mapping PA 0x7fbbc000 -> VA 0x7fbbc000!
>> [ 0.184091] efi: Error mapping PA 0x100000000 -> VA 0x100000000!
>> [ 0.184093] efi: Error mapping PA 0xfff90000 -> VA 0xfff90000!
>> [ 0.184097] efi: Error ident-mapping new memmap (0x17b5a4000)!
>>
>> Le mar. 6 août 2019 à 11:39, Antoine Reversat <a.reversat@gmail.com> a
>> écrit :
>>
>>> Sorry for the maybe not so helpful title.
>>>
>>> Here is the problem :
>>> I'm running Linux on a Mac pro 1,1 (the first x86 mac pro). It's a dual
>>> xeon 5150 with ECC ram. I have 2 ram kits in it : 2x512M and 2x2G (this one
>>> :
>>> http://www.ec.kingston.com/ecom/hyperx_us/partsinfo.asp?root=&ktcpartno=KTA-MP667AK2/4G
>>> )
>>>
>>> If I only have the 2x512M kit everything works fine for all kernel
>>> versions but if I have both kits or just the 2x2G kit any kernel above 4.10
>>> panics very early on (picture of said panic https://imgur.com/a/PipU5Oc).
>>> The picture was taken on 4.15 (using earlyprintk=efi,keep) on other
>>> versions even using earlyprintk I don't get any output.
>>>
>>> I have been trying several kernels and everything up to 4.11 works no
>>> problem. Then on 4.11 I got a panic which mentionned NX and pages being in
>>> W+X which prompted me to try noexec=off on newer versions and that fixes
>>> the panic. This works up to 5.2.5.
>>>
>>> /proc/cpuinfo reports that the CPU support the NX flag.
>>>
>>> I would need help in order to troubleshoot this further.
>>>
>>
[-- Attachment #2: Type: text/html, Size: 7314 bytes --]
prev parent reply other threads:[~2019-08-06 17:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-06 15:39 Antoine Reversat
2019-08-06 16:23 ` Antoine Reversat
2019-08-06 16:25 ` Antoine Reversat
2019-08-06 17:34 ` Antoine Reversat [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='CAA=2nCZNA5iGQk3QRCzAbSMrCst0oWqi_OCLEO6A7Ux8A3+dbg@mail.gmail.com' \
--to=a.reversat@gmail.com \
--cc=linux-mm@kvack.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox