All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jochen Hein <jochen@jochen.org>
To: linux-kernel <linux-kernel@vger.kernel.org>
Cc: ianh@iahastie.clara.net
Subject: Re: [2.6] Missing L2-cache after warm boot
Date: Tue, 02 Dec 2003 14:26:20 +0100	[thread overview]
Message-ID: <878ylvjqpv.fsf@echidna.jochen.org> (raw)
In-Reply-To: <200312020300.13067.ianh@iahastie.local.net> (Ian Hastie's message of "Tue, 2 Dec 2003 03:00:11 +0000")

Ian Hastie <ianh@iahastie.clara.net> writes:

> On Monday 01 Dec 2003 14:04, Jochen Hein wrote:
>> I'm running 2.6.0-test11 on an older Thinkpad 390E,
>> When booting into 2.6.0-test11 after running Windows2000 I get:
>
> Do any of the previous test releases show this problem?  

-test11 is the first release running on that machine.  My older TP600
destroyed its WIndows 95 so I got a replacement.  Compiling a kernel
takes an hour or two, so it is not much fun trying different kernels.

> How are you booting  
> Linux?  Full warm boot via the BIOS or some loadlin kind of boot?  

via BIOS, lilo in MBR

> If it's 
> via the BIOS then does that show the L2 cache as being present?

The BIOS doesn't tell anything, the setup doesn't have a "cache
enable" or "turbo" entry.

>> When booting cold the boot messages are:
>
> Presumably from switch on.

Yes.

>> /proc/cpuinfo contains (after warm boot):
>> processor       : 0
>> vendor_id       : GenuineIntel
>> cpu family      : 6
>> model           : 6
>> model name      : Mobile Pentium II
>> stepping        : 10
>> cpu MHz         : 298.598
>> cache size      : 256 KB
>
> And shows as 0 after warm boot?

Hm, can't say for sure, because it didn't happen again.

> My immediate thought was a BIOS problem.  IBM's web site doesn't say any BIOS 
> updates fix L2 cache related problems, but then it doesn't seem to use 
> technical descriptions like that.  It says the latest BIOS is 1.55 - R01_C9.
>
> http://www-1.ibm.com/support/docview.wss?rs=0&uid=psg1MIGR-4F3VKB&loc=en_US

I'll see what BIOS I have - it is the latest.  Thanks for the hint anyway.

> Or maybe it's possible that something in MS Windows 2000 is turning off the L2 
> cache and it isn't getting reactivated by the warm boot?  

Is there any way to see what Windows does here?  I only found a manual
enable of the L2cache when using older processors.

> What happens when 
> you do a cold boot to Linux then reboot from there?

That is fine.

For now the system seems to be fine, even when starting from Win2k via
BIOS reboot.  Hmpf.

Jochen

-- 
#include <~/.signature>: permission denied

  reply	other threads:[~2003-12-02 13:46 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-01 14:04 [2.6] Missing L2-cache after warm boot Jochen Hein
2003-12-01 19:33 ` Randy.Dunlap
2003-12-02 13:16   ` Jochen Hein
2003-12-02 18:14     ` Mike Fedyk
2003-12-02 19:15       ` Jochen Hein
2003-12-02  3:00 ` Ian Hastie
2003-12-02 13:26   ` Jochen Hein [this message]
2003-12-03 17:10     ` Ian Hastie
2003-12-03 17:37       ` Jochen Hein

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=878ylvjqpv.fsf@echidna.jochen.org \
    --to=jochen@jochen.org \
    --cc=ianh@iahastie.clara.net \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.