From: "Matthew Gregan" <mgregan@jade.co.nz>
To: <linux-kernel@vger.kernel.org>
Subject: Alpha XLT 366 fails to boot kernel >= 2.4.14
Date: Sun, 18 Nov 2001 00:51:31 +1300 [thread overview]
Message-ID: <00e801c16f5e$3319eab0$9681608f@cnw.co.nz> (raw)
My Alpha XLT 366 fails to boot kernels 2.4.14 and higher - the problem
appears to be related to the cpu_hz struct added in (I think)
2.4.14-pre8 or detection of the CPU (EV5, EV56, etc.)
Linux 2.4.12 boots fine - one thing I have noticed is that the bogomips
have doubled since 2.2.19, not that it should matter...
Booting 2.4.15-pre5 (generic, I have some other problems with an alcor
specific kernel) the machine freezes during bogomips calculation -
before that is an error about HWRPB being bogus and failing to guess a
usable value.
The 2.2.19 (alcor) kernel detects the machine as:
Booting on Alcor using machine vector Alcor from MILO
cat /proc/cpuinfo under 2.2.19 gives:
cpu : Alpha
cpu model : EV5
cpu variation : 0
cpu revision : 0
cpu serial number : Linux_is_Great!
system type : Alcor
system variation : 0
system revision : 0
system serial number : MILO-0000
cycle frequency [Hz] : 0
timer frequency [Hz] : 1024.00
page size [bytes] : 8192
phys. address bits : 40
max. addr. space # : 127
BogoMIPS : 362.80
kernel unaligned acc : 0 (pc=0,va=0)
user unaligned acc : 0 (pc=0,va=0)
platform string : N/A
cpus detected : 0
The cpu_hz struct in arch/alpha/kernel/time.c lists the EV5 as being
between 266 and 333 MHz. The CPU in this box is 366 MHz.
So... either this machine is being misdetected as an EV5 when it's an
EV56, or there really _are_ 366MHz EV5s, and cpu_hz needs fixing.
I have attached a patch to fix cpu_hz, which gets the machine booting
with 2.4.15-pre5.
I also have some other problems with an alcor specific kernel, in the
form of lots of machine checks on boot, but I have not investigated that
yet.
diff -ru linux-2.4.15-pre5.orig/arch/alpha/kernel/time.c
linux-2.4.15-pre5/arch/alpha/kernel/time.c
--- linux-2.4.15-pre5.orig/arch/alpha/kernel/time.c Sun Nov 18
00:17:55 2001
+++ linux-2.4.15-pre5/arch/alpha/kernel/time.c Sun Nov 18 00:16:32 2001
@@ -186,7 +186,7 @@
[EV4_CPU] = { 150000000, 300000000 },
[LCA4_CPU] = { 150000000, 300000000 }, /* guess
*/
[EV45_CPU] = { 200000000, 300000000 },
- [EV5_CPU] = { 266000000, 333333333 },
+ [EV5_CPU] = { 266000000, 366000000 },
[EV56_CPU] = { 366000000, 667000000 },
[PCA56_CPU] = { 400000000, 600000000 }, /* guess
*/
[PCA57_CPU] = { 500000000, 600000000 }, /* guess
*/
--
Matthew Gregan Operations Consultant
JADE Direct Central Systems NZ: 0 800 65 2266
Aoraki Corporation Limited AU: 1 800 12 0181
PO Box 20-152, Christchurch 8005 Cell: +64 2977 8839
New Zealand Fax: +64 3358 7156
next reply other threads:[~2001-11-17 11:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-17 11:51 Matthew Gregan [this message]
2001-11-17 19:38 Matthew Gregan
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='00e801c16f5e$3319eab0$9681608f@cnw.co.nz' \
--to=mgregan@jade.co.nz \
--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
all inboxes | Powered by JetHome®