From: Michael Lundkvist <ml@epact.se>
To: linuxppc-dev@lists.linuxppc.org
Subject: Re: Going from 2.2.12 to 2.2.17pre10
Date: 07 Jul 2000 00:23:07 +0200 [thread overview]
Message-ID: <qpvgyihp9w.fsf@erbium.epact.se> (raw)
In-Reply-To: Gabriel Paubert's message of "Thu, 6 Jul 2000 19:55:44 +0200 (METDST)"
Gabriel Paubert <paubert@iram.es> writes:
> Ok, never had any problems with SCSI since DMA always gets the byte order
> right ;-)
>
It wasn't my decision to go with IDE...
>
> Where is and what is Bugboot ?
>
It's a bootloader for flashed kernels. Written by Matt Porter from Motorola.
http://members.home.net/mmporter/linux/
Could I do the same thing with your bootloader?
I would like to have a bootloader that can read from disk so that it
is easy to replace the kernel.
>
> Quite a lot. A complete bootloader, drivers for VME and many small patches
> in the arch/ppc/kernel subtree. A diffstat of both patches gives:
>
> 73 files changed, 19880 insertions, 478 deletions
>
OK. Then I'd like to try it. My initial tests with 2.2.17pre10 didn't
turn out well.
>
> I had to shut down an MVME2600 after 6 months of uptime with this kernel
> for hardware upgrade. It is used as a server for all the nfsroot machines
> and to compile all the software for these (and sometimes heavily swapping:
> 3 compiles in parallel in 32 Mb or RAM are noticeable). The MVME2400 have
> never been under serious load, so I don't know if they have specific
> problems but the kernel is essentially the same (less drivers and
> filesystems).
>
I ran the Debian 2.2.12 (with Motorola SROM bug patch) on a 2300 with
a fair bit of compiling and it was stable. The same kernel on an 2400
was unstable during compiles.
> I have not heavily stress-tested 2.4.0-test2 (well recompiling kernels and
> performing bitkeeper patch imports is kind of stress testing I/O,
> especially with 16Mb), I had some filesystem problems in 2.3.50 but they
> have vanished it seems.
>
> Gabriel.
I'll give your 2.4 a try. I need to get atleast one more PMC disk so I
can have one stable and one unstable evironment.
On an unrelated subject. I would like to have a Linux-board as SYSCON
on the VME bus that is able to generate a reset on the bus but doesn't
listen to it. Have you got any idea if it would be possible to modify
a MVME-card that way? To me it looks like it would be possible to
disconnect the signal from the Universe-bridge.
/Micke
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2000-07-06 22:23 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-07-06 13:27 Going from 2.2.12 to 2.2.17pre10 Michael Lundkvist
2000-07-06 13:54 ` Hollis Blanchard
2000-07-06 17:17 ` Gabriel Paubert
2000-07-06 17:32 ` Michael Lundkvist
2000-07-06 17:55 ` Gabriel Paubert
2000-07-06 22:23 ` Michael Lundkvist [this message]
2000-07-07 8:22 ` Gabriel Paubert
2000-07-07 8:55 ` Michael Lundkvist
2000-07-07 9:21 ` Gabriel Paubert
2000-07-07 9:47 ` Michael Lundkvist
2000-07-07 10:19 ` Gabriel Paubert
2000-07-08 0:08 ` Problem with de4x5 on an MVME-2400 Michael Lundkvist
2000-07-10 11:58 ` Gabriel Paubert
2000-07-12 13:01 ` Michael Lundkvist
2000-07-08 23:29 ` Going from 2.2.12 to 2.2.17pre10 Matt Porter
2000-07-09 6:12 ` Michael Lundkvist
2000-07-10 5:29 ` Matt Porter
2000-07-10 12:25 ` Gabriel Paubert
2000-07-11 5:57 ` Matt Porter
2000-07-11 9:37 ` Adrian Cox
2000-07-11 10:17 ` Benjamin Herrenschmidt
2000-07-11 12:57 ` Adrian Cox
2000-07-11 14:10 ` Claus
2000-07-11 19:15 ` Geert Uytterhoeven
2000-07-12 13:31 ` Benjamin Herrenschmidt
2000-07-13 11:17 ` Geert Uytterhoeven
2000-07-12 9:11 ` Timothy A. Seufert
2000-07-12 14:16 ` Matt Porter
2000-07-13 11:43 ` Gabriel Paubert
2000-07-13 14:12 ` Matt Porter
2000-07-12 12:52 ` Michael Lundkvist
2000-07-12 14:17 ` Matt Porter
2000-07-10 12:12 ` Gabriel Paubert
2000-07-11 6:12 ` Matt Porter
2000-07-11 10:48 ` Gabriel Paubert
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=qpvgyihp9w.fsf@erbium.epact.se \
--to=ml@epact.se \
--cc=linuxppc-dev@lists.linuxppc.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;
as well as URLs for NNTP newsgroup(s).