From: Christian Kujau <evil@g-house.de>
To: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: 2.5.71 compile error on alpha
Date: Wed, 18 Jun 2003 00:27:52 +0200 [thread overview]
Message-ID: <3EEF95E8.5040109@g-house.de> (raw)
In-Reply-To: <yw1xptlcs8ng.fsf@zaphod.guide>
Måns Rullgård schrieb:
>>lila:~# cat /proc/cpuinfo
[...]
>>kernel unaligned acc : 32 (pc=fffffc0000478394,va=fffffc0002dbf176)
>
> That's not good. Do you know what is causing it.
i did not even know that this one is bad. the only weird thing which
comes into my mind when thinking about this alpha is: it is filled up
whith fine 128 MB RAM -- but it is only seeing 64 MB. when we inserted
64 MB RAM, only 32 MB are recognized. with 32 MB working with it was no
fun, working with 64 MB is quite good. must be the type of RAM but i
don't really know much about the different RAM types.
> Good, what's it like performance-wise? 2.5.68 had trouble with my IDE
> disks, and I wonder if it's been fixed since.
can't tell about IDE, since it has only scsi in it. i used to run
benchmarks (tiobench) on the alpha, with different loop-mounted
filesystems, but the alpha has been frozen very often during these
benchmarks...will redo with 2.5.72 later.
Thanks,
Christian.
next prev parent reply other threads:[~2003-06-17 22:15 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-16 22:52 2.5.71 compile error on alpha Christian Kujau
2003-06-16 23:00 ` Måns Rullgård
2003-06-17 12:16 ` Ivan Kokshaysky
2003-06-17 18:33 ` Christian Kujau
[not found] ` <wrpr85te3fa.fsf@hina.wild-wind.fr.eu.org>
2003-06-17 18:05 ` Christian Kujau
2003-06-17 18:26 ` Måns Rullgård
2003-06-17 20:22 ` Jan-Benedict Glaw
2003-06-17 20:33 ` Christian Kujau
2003-06-17 21:20 ` Måns Rullgård
2003-06-17 22:27 ` Christian Kujau [this message]
2003-06-18 19:36 ` Geert Uytterhoeven
2003-06-17 21:00 ` Christian Kujau
2003-06-17 21:00 ` Christian Kujau
2003-06-17 21:23 ` Måns Rullgård
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=3EEF95E8.5040109@g-house.de \
--to=evil@g-house.de \
--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