Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1621917 > unrolled thread
| Started by | Dave Young <dyoung@redhat.com> |
|---|---|
| First post | 2017-04-12 10:30 +0200 |
| Last post | 2017-04-12 15:00 +0200 |
| Articles | 4 — 2 participants |
Back to article view | Back to linux.kernel
This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by
below is the oldest one visible, not the original post.
Re: KASLR causes intermittent boot failures on some systems Dave Young <dyoung@redhat.com> - 2017-04-12 10:30 +0200
Re: KASLR causes intermittent boot failures on some systems Dave Young <dyoung@redhat.com> - 2017-04-12 10:30 +0200
Re: KASLR causes intermittent boot failures on some systems Dave Young <dyoung@redhat.com> - 2017-04-12 10:50 +0200
Re: KASLR causes intermittent boot failures on some systems Jeff Moyer <jmoyer@redhat.com> - 2017-04-12 15:00 +0200
| From | Dave Young <dyoung@redhat.com> |
|---|---|
| Date | 2017-04-12 10:30 +0200 |
| Subject | Re: KASLR causes intermittent boot failures on some systems |
| Message-ID | <tvlP3-2b9-3@gated-at.bofh.it> |
On 04/07/17 at 10:41am, Jeff Moyer wrote:
> Hi,
>
> commit 021182e52fe01 ("x86/mm: Enable KASLR for physical mapping memory
> regions") causes some of my systems with persistent memory (whether real
> or emulated) to fail to boot with a couple of different crash
> signatures. The first signature is a NMI watchdog lockup of all but 1
> cpu, which causes much difficulty in extracting useful information from
> the console. The second variant is an invalid paging request, listed
> below.
>
> On some systems, I haven't hit this problem at all. Other systems
> experience a failed boot maybe 20-30% of the time. To reproduce it,
> configure some emulated pmem on your system. You can find directions
> for that here: https://nvdimm.wiki.kernel.org/
>
> Install ndctl (https://github.com/pmem/ndctl).
> Configure the namespace:
> # ndctl create-namespace -f -e namespace0.0 -m memory
>
> Then just reboot several times (5 should be enough), and hopefully
> you'll hit the issue.
>
> I've attached both my .config and the dmesg output from a successful
> boot at the end of this mail.
>
[snip]
I did some tests about emulated pmem via memmap=, kdump kernel hangs or
just reboots early during compressing kernel, no clue how to handle it.
Since for kdump kernel kaslr is pointless a workaround is use "nokaslr"
In Fedora or RHEL, just add "nokaslr" in KDUMP_COMMANDLINE_APPEND
in /etc/sysconfig/kdump
Can you try if this works?
Thanks
Dave
[toc] | [next] | [standalone]
| From | Dave Young <dyoung@redhat.com> |
|---|---|
| Date | 2017-04-12 10:30 +0200 |
| Message-ID | <tvlP4-2b9-15@gated-at.bofh.it> |
| In reply to | #1621917 |
On 04/12/17 at 04:24pm, Dave Young wrote:
> On 04/07/17 at 10:41am, Jeff Moyer wrote:
> > Hi,
> >
> > commit 021182e52fe01 ("x86/mm: Enable KASLR for physical mapping memory
> > regions") causes some of my systems with persistent memory (whether real
> > or emulated) to fail to boot with a couple of different crash
> > signatures. The first signature is a NMI watchdog lockup of all but 1
> > cpu, which causes much difficulty in extracting useful information from
> > the console. The second variant is an invalid paging request, listed
> > below.
> >
> > On some systems, I haven't hit this problem at all. Other systems
> > experience a failed boot maybe 20-30% of the time. To reproduce it,
> > configure some emulated pmem on your system. You can find directions
> > for that here: https://nvdimm.wiki.kernel.org/
> >
> > Install ndctl (https://github.com/pmem/ndctl).
> > Configure the namespace:
> > # ndctl create-namespace -f -e namespace0.0 -m memory
> >
> > Then just reboot several times (5 should be enough), and hopefully
> > you'll hit the issue.
> >
> > I've attached both my .config and the dmesg output from a successful
> > boot at the end of this mail.
> >
> [snip]
>
> I did some tests about emulated pmem via memmap=, kdump kernel hangs or
> just reboots early during compressing kernel, no clue how to handle it.
s/compressing/uncompressing
> Since for kdump kernel kaslr is pointless a workaround is use "nokaslr"
>
> In Fedora or RHEL, just add "nokaslr" in KDUMP_COMMANDLINE_APPEND
> in /etc/sysconfig/kdump
>
> Can you try if this works?
>
> Thanks
> Dave
[toc] | [prev] | [next] | [standalone]
| From | Dave Young <dyoung@redhat.com> |
|---|---|
| Date | 2017-04-12 10:50 +0200 |
| Message-ID | <tvm8p-2hK-3@gated-at.bofh.it> |
| In reply to | #1621917 |
On 04/12/17 at 04:24pm, Dave Young wrote:
> On 04/07/17 at 10:41am, Jeff Moyer wrote:
> > Hi,
> >
> > commit 021182e52fe01 ("x86/mm: Enable KASLR for physical mapping memory
> > regions") causes some of my systems with persistent memory (whether real
> > or emulated) to fail to boot with a couple of different crash
> > signatures. The first signature is a NMI watchdog lockup of all but 1
> > cpu, which causes much difficulty in extracting useful information from
> > the console. The second variant is an invalid paging request, listed
> > below.
> >
> > On some systems, I haven't hit this problem at all. Other systems
> > experience a failed boot maybe 20-30% of the time. To reproduce it,
> > configure some emulated pmem on your system. You can find directions
> > for that here: https://nvdimm.wiki.kernel.org/
> >
> > Install ndctl (https://github.com/pmem/ndctl).
> > Configure the namespace:
> > # ndctl create-namespace -f -e namespace0.0 -m memory
> >
> > Then just reboot several times (5 should be enough), and hopefully
> > you'll hit the issue.
> >
> > I've attached both my .config and the dmesg output from a successful
> > boot at the end of this mail.
> >
> [snip]
>
> I did some tests about emulated pmem via memmap=, kdump kernel hangs or
> just reboots early during compressing kernel, no clue how to handle it.
> Since for kdump kernel kaslr is pointless a workaround is use "nokaslr"
>
> In Fedora or RHEL, just add "nokaslr" in KDUMP_COMMANDLINE_APPEND
> in /etc/sysconfig/kdump
>
> Can you try if this works?
Oops, your problem is normal boot instead of kdump so this is two
different problems. Seems we have not met your bug yet..
Thanks
Dave
[toc] | [prev] | [next] | [standalone]
| From | Jeff Moyer <jmoyer@redhat.com> |
|---|---|
| Date | 2017-04-12 15:00 +0200 |
| Message-ID | <tvq2l-4yp-7@gated-at.bofh.it> |
| In reply to | #1621928 |
Dave Young <dyoung@redhat.com> writes: > On 04/12/17 at 04:24pm, Dave Young wrote: >> I did some tests about emulated pmem via memmap=, kdump kernel hangs or >> just reboots early during compressing kernel, no clue how to handle it. >> Since for kdump kernel kaslr is pointless a workaround is use "nokaslr" >> >> In Fedora or RHEL, just add "nokaslr" in KDUMP_COMMANDLINE_APPEND >> in /etc/sysconfig/kdump >> >> Can you try if this works? > > Oops, your problem is normal boot instead of kdump so this is two > different problems. Seems we have not met your bug yet.. Correct. -Jeff
[toc] | [prev] | [standalone]
Back to top | Article view | linux.kernel
csiph-web