From: Andrew Morton <akpm@linux-foundation.org>
To: "James Kirin" <james.kirin40@gmail.com>
Cc: yinghai@kernel.org, rdreier@cisco.com, linux-kernel@vger.kernel.org
Subject: Re: kernel panic when using disable_mtrr_trim [was: Re: memory beyond4GB invisible to the system even though CONFIG_HIGHMEM64G=y]
Date: Thu, 29 Jan 2009 16:09:43 -0800 [thread overview]
Message-ID: <20090129160943.1bb0d3b5.akpm@linux-foundation.org> (raw)
In-Reply-To: <baeb34bc0901201018s5c6eaedcp9ba0dc7e81642509@mail.gmail.com>
On Tue, 20 Jan 2009 13:18:15 -0500
"James Kirin" <james.kirin40@gmail.com> wrote:
> Hi Yinghai,
>
> When I boot with "disable_mtrr_trim mem=4g", the system boots fine.
> Then I changed that to
> "disable_mtrr_trim mem=6g" and a kernel panic occurs:
>
> [...] Freeing unused kernel memory: 296k freed
> [...] Write protecting the kernel text: 3040k
> [...] Write protecting the kernel read-only data: 1352k
> [...] khelper used greatest stack depth: 6724 byytes left
> [...] Kernel panic - not syncing: No init found. Try passing init=
> option to kernel.
>
> I can always reproduce this: all it takes it to boot from a rescue CD,
> switch between "mem=4g" and "mem=6g" in /etc/lilo.conf, run lilo and
> reboot. If it is 4g, it boots fine; if it is 6g, a kernel panic
> occurs. No other changes at all were made.
>
> Same thing (kernel panic) occurs if mem=5g is used.
>
> I am attaching the kernel config used when this happens.
>
> Please let me know how I can help fix this. Does it somehow depend on
> all those MTRR/etc memory-related options in the kernel configuration?
>
Did this get fixed?
Which kernel versions are affected?
Thanks.
next prev parent reply other threads:[~2009-01-30 0:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-20 18:18 kernel panic when using disable_mtrr_trim [was: Re: memory beyond4GB invisible to the system even though CONFIG_HIGHMEM64G=y] James Kirin
2009-01-30 0:09 ` Andrew Morton [this message]
2009-01-30 0:13 ` Andrew Morton
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=20090129160943.1bb0d3b5.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=james.kirin40@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rdreier@cisco.com \
--cc=yinghai@kernel.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