From: Christian Kujau <evil@g-house.de>
To: linuxppc-dev@lists.linuxppc.org
Subject: Re: ppc32 lockups with 2.6
Date: Tue, 18 Nov 2003 15:14:49 +0100 [thread overview]
Message-ID: <3FBA2959.80609@g-house.de> (raw)
In-Reply-To: <3FBA11AC.8090408@g-house.de>
Christian Kujau wrote:
> i will go on with 2.6.0-tes5 now....
no strange error messages anymore with -test5, but still no routing.
i someone wants to have a look:
http://nerdbynature.de/bits/
(i've re-orderd the links, sorry. the "my PReP machine (ppc32) doesn't
like the new kernel" are the right ones.)
Thanks,
Christian.
--
BOFH excuse #179:
multicasts on broken packets
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2003-11-18 14:14 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-02 20:31 ppc32 lockups with 2.6 Christian Kujau
2003-11-06 21:34 ` Christian
2003-11-10 18:50 ` linas
2003-11-10 20:32 ` Tom Rini
2003-11-10 22:39 ` Christian
2003-11-10 23:57 ` linas
2003-11-11 0:25 ` Christian
2003-11-11 15:36 ` Tom Rini
2003-11-13 0:59 ` Christian Kujau
2003-11-13 17:47 ` Tom Rini
2003-11-13 23:56 ` Christian Kujau
2003-11-14 15:57 ` Tom Rini
2003-11-18 12:33 ` Christian Kujau
2003-11-18 14:14 ` Christian Kujau [this message]
2003-11-21 15:25 ` Christian Kujau
2003-11-21 17:54 ` Tom Rini
-- strict thread matches above, loose matches on Subject: below --
2003-11-01 4:30 Christian
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=3FBA2959.80609@g-house.de \
--to=evil@g-house.de \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.