From: Matt C <wago@phlinux.com>
To: Praveen Ray <praveen.ray@crcnet1.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: timer interrupts on HP machines
Date: Thu, 30 Jan 2003 09:01:50 -0800 (PST) [thread overview]
Message-ID: <Pine.LNX.4.44.0301300859340.22492-100000@fubar.phlinux.com> (raw)
In-Reply-To: <200301300934.54201.praveen.ray@crcnet1.com>
Hi Praveen-
We have a few LT6000r servers as well, and have the same problem on all
2.4 kernels -- this happens when your MP spec is set to 1.1 in the BIOS.
Change it to 1.4 and you should be okay.
The other common problem on these guys is the CPU speed misdetect, which
causes the kernel to think your CPU is roughly 2x as fast as it really is.
The solution to that one is to unplug and replug the power cords (even a
power-off doesn't fix it, go figure).
Hope that helps.
-Matt
On Thu, 30 Jan 2003, Praveen Ray wrote:
> We have few HP (LPR NetServers and LT6000) which run 2.4.18 (from RedHat 8.0)
> . The problem is that sometimes the time interrupts stop coming - i.e. the
> (time) counts in /proc/interrupts stop getting incremented! When this
> happens, the date on the system falls behind, 'sleep' calls stop working and
> basically machine becomes unusable.Has anyone else encountered this problem?
> Is it an HP issue?
> Thanks.
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
next prev parent reply other threads:[~2003-01-30 16:52 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-30 14:34 Praveen Ray
2003-01-30 16:44 ` Alan Cox
2003-01-30 17:01 ` Matt C [this message]
[not found] <Pine.LNX.4.33.0301291003220.19934-100000@mars.cmie.ernet.in>
2003-02-03 13:22 ` Nohez
2003-02-03 15:03 ` Valdis.Kletnieks
2003-02-04 4:34 ` Nohez
2003-02-04 2:54 ` Matt C
2003-02-04 4:59 ` Nohez
2003-02-04 19:48 ` Matt C
2003-05-19 13:00 Edwin Top
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=Pine.LNX.4.44.0301300859340.22492-100000@fubar.phlinux.com \
--to=wago@phlinux.com \
--cc=linux-kernel@vger.kernel.org \
--cc=praveen.ray@crcnet1.com \
/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
all inboxes | Powered by JetHome®