From: Matthew Denner <matt@denner.demon.co.uk>
To: linux-kernel@vger.kernel.org
Subject: Re: 45 minute boot time with 2.6.4/2.6.6-mm5 kernel on 1.7GHz laptop
Date: Tue, 15 Jun 2004 19:45:55 +0100 [thread overview]
Message-ID: <40CF43E3.3080504@denner.demon.co.uk> (raw)
In-Reply-To: <16590.65369.579162.568380@alkaid.it.uu.se>
Mikael Pettersson wrote:
> Matthew Denner writes:
> > On Saturday I installed SuSE 9.1 Personal on my laptop and I'm beginning
> > to wonder whether this was a bad idea. It takes my laptop (a Pentium-M
> > Centrino 1.7Ghz with 1GB DDR RAM and 40GB HDD) 45 minutes to boot (from
> > selecting "linux" in GRUB to having the KDE interface up and running).
> > It spends about 20-25 minutes in the boot procedure before it even gets
> > to starting X. Yesterday I managed to tidy my front room, put some
>
> Sounds a lot like a BIOS MTRR problem we've seen before, where
> the BIOS fails to make the top-most part of physical RAM cacheable.
>
> Send the contents of /proc/mtrr and the head of dmesg (the part
> that shows the physical memory map) to LKML.
I would have done this ealier, had I not broken everything with my last
kernel rebuild and had to re-install! Kernel is back to 2.6.4.
The output of /proc/mtrr is:
reg00: base=0x00000000 ( 0MB), size= 512MB: write-back, count=1
reg01: base=0x20000000 ( 512MB), size= 256MB: write-back, count=1
reg02: base=0x30000000 ( 768MB), size= 128MB: write-back, count=1
reg03: base=0x38000000 ( 896MB), size= 64MB: write-back, count=1
reg04: base=0x3c000000 ( 960MB), size= 32MB: write-back, count=1
reg05: base=0x3e000000 ( 992MB), size= 16MB: write-back, count=1
reg06: base=0xf0000000 (3840MB), size= 4MB: write-combining, count=1
And the physical RAM map bit is:
BIOS-provided physical RAM map:
BIOS-e820: 0000000000000000 - 000000000009fc00 (usable)
BIOS-e820: 000000000009fc00 - 00000000000a0000 (reserved)
BIOS-e820: 00000000000e0000 - 0000000000100000 (reserved)
BIOS-e820: 0000000000100000 - 000000003f7d0000 (usable)
BIOS-e820: 000000003f7d0000 - 000000003f7df000 (ACPI data)
BIOS-e820: 000000003f7df000 - 000000003f800000 (ACPI NVS)
BIOS-e820: 00000000fff80000 - 0000000100000000 (reserved)
128MB vmalloc/ioremap area available.
119MB HIGHMEM available.
896MB LOWMEM available.
On node 0 totalpages: 260048
DMA zone: 4096 pages, LIFO batch:1
Normal zone: 225280 pages, LIFO batch:16
HighMem zone: 30672 pages, LIFO batch:7
If you need any more info please let me know.
Matt
next prev parent reply other threads:[~2004-06-15 18:46 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-15 13:41 45 minute boot time with 2.6.4/2.6.6-mm5 kernel on 1.7GHz laptop Matthew Denner
2004-06-15 13:53 ` Mikael Pettersson
2004-06-15 18:45 ` Matthew Denner [this message]
2004-06-15 22:06 ` Mikael Pettersson
2004-06-16 9:06 ` Matthew Denner
2004-06-15 14:29 ` Marco Roeland
-- strict thread matches above, loose matches on Subject: below --
2004-06-15 15:09 Michael W. Salo
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=40CF43E3.3080504@denner.demon.co.uk \
--to=matt@denner.demon.co.uk \
--cc=linux-kernel@vger.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