From: Martin Costabel <costabel@wanadoo.fr>
To: linuxppc-dev@lists.linuxppc.org
Cc: Benjamin Herrenschmidt <benh@mipsys.com>
Subject: Re: Re; 2.4.0-test9 on B&W G3
Date: Fri, 22 Sep 2000 20:51:40 +0200 [thread overview]
Message-ID: <39CBAA3C.2CC16A34@wanadoo.fr> (raw)
In-Reply-To: 20000922164705.32547@mail.mipsys.com
Benjamin Herrenschmidt wrote:
>
> >I have also been seeing the same old 'lost interrupt' problem when trying
> >to boot a B&W G3 using the latest yaboot (0.8) on the latest pmac-devel
> >rsync kernel. I was wondering if this was a know bug with the latest 2.4
> >tree kernel's. I also booted the same kernel on a new G4/450 with no
> >problems.
>
> I have a fix for that too. I'll push it as soon as I have access to bk again.
> In the meantime, apply enclosed changeset to the current linuxppc_2_3 bk tree.
Glad to hear that the linuxppc_2_3 bk tree is not dead. I was just going
to ask about it, because since 2 weeks it has remained at -test8 which
is feared for its terrible mailbox-eating habits.
On the other hand, I am running a kernel obtained from this tree by
applying just the "official" test9-pre1 patch, and I have now an uptime
of 4 days, 22:02. This is the longest uptime I ever had with a 2.3/4
kernel. No spontaneous freezes so far <knocking on wood>.
--
Martin
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2000-09-22 18:51 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-09-22 16:47 Re; 2.4.0-test9 on B&W G3 Benjamin Herrenschmidt
2000-09-22 18:51 ` Martin Costabel [this message]
2000-09-23 5:19 ` Martin Costabel
2000-09-23 5:31 ` Tom Rini
2000-09-23 5:57 ` Martin Costabel
2000-09-23 14:08 ` MOL on 2.4/603 Samuel Rydh
2000-09-23 12:38 ` Re; 2.4.0-test9 on B&W G3 Geert Uytterhoeven
2000-09-22 20:37 ` Michel Lanners
2000-09-22 21:37 ` Benjamin Herrenschmidt
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=39CBAA3C.2CC16A34@wanadoo.fr \
--to=costabel@wanadoo.fr \
--cc=benh@mipsys.com \
--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).