linux-kernel - Re: memory beyond4GB invisible to the system even though CONFIG

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <baeb34bc0901151235v3c19306enaa2b6b11a18e1275@mail.gmail.com>
Date:	Thu, 15 Jan 2009 15:35:02 -0500
From:	"James Kirin" <james.kirin40@...il.com>
To:	"Yinghai Lu" <yinghai@...nel.org>
Cc:	"Roland Dreier" <rdreier@...co.com>, linux-kernel@...r.kernel.org
Subject: Re: memory beyond4GB invisible to the system even though CONFIG_HIGHMEM64G=y

I tried disabing CONFIG_MTRR_SANITIZER and CONFIG_X86_PAT in the
kernel, and now a different kernel panic occurs:

[... ] Write protecting the kernel text: 3040k
[...] Write protecting the kernel read-only data: 1352k
[... ] khelper used greatest stack depth: 6724 bytes left
[ ...] Kernel panic - not syncing: No init found. Try passing init=
option to kernel.

Is an "init=" option necessary when using disable_mtrr_trim?

Thanks in advance,

James

On Thu, Jan 15, 2009 at 2:50 PM, James Kirin <james.kirin40@...il.com> wrote:
> Hi Yinghai,
>
>> please do
>> 1. boot linux with "disable_mtrr_trim" in grub.conf etc
>> 2. after booting input:
>> echo "base=0x100000000 size=0x20000000 type=write-back" >/proc/mtrr
>
> Thank you for your suggestion.
>
> Unfortunately, booting with disable_mtrr_trim leads to a kernel panic:
>
> [<c0103abb>] kernel_thread_helper+0x7/0x1c
> ===========
> Code: 0c 31 d2 89 e8 e8 c2 f4 ff ff 89 c3 eb 8e 8b 85 cc 00 00 00 89 44 24 10 83
> bd ec 00 01 00 04 0f 84 cf 00 00 00 8b 9d f0 00 01 00 <8b> 43 10 3b 43 0c 0f 84
> d5 00 00 00 8b 53 10 8b 85 ec 00 01 00
> EIP: [<c026bc2f] hid_parser_main+0xcf/0x290 SS:ESP 0068:f7c2bd7c
> ---[ end trace 34615b445589fbb6 ]---
> Kernel panic - not syncing: Attempted to kill init!
>
> I am attaching the kernel config file. The system boots fine if I
> remove "disable_mtrr_trim" from lilo.conf (and rerun lilo).
>
> Thank you for any help,
>
> James
>
--
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/