From: Martin Costabel <costabel@wanadoo.fr>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Dev-Linux <linuxppc-dev@lists.linuxppc.org>
Subject: Re: Kernel debugging??
Date: Tue, 16 Nov 1999 23:44:11 +0100 [thread overview]
Message-ID: <3831DE3B.5F2C790@wanadoo.fr> (raw)
In-Reply-To: Pine.LNX.4.05.9911161844270.25661-100000@callisto.of.borg
Geert Uytterhoeven wrote:
> > And I could boot a stock 2.3.26 with changes in asm-ppc/fcntl.h
> > (O_LARGEFILE ....)
>
> That's very interesting to know! It means we just have to analyse the 2.3.27
> and 2.3.28 patches to find out what went wrong.
Just for information: Paul M's 2.3.27 rsync kernel compiles and runs
just fine on this Pmac 6400. The machine swaps like crazy and is
therefore rather slow, but I am not sure if this is the kernel's fault.
--
Martin
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~1999-11-16 22:44 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-11-16 12:25 Kernel debugging?? Andreas Tobler
1999-11-16 15:52 ` Ani Joshi
1999-11-16 16:03 ` Andreas Tobler
1999-11-16 17:45 ` Geert Uytterhoeven
1999-11-16 22:44 ` Martin Costabel [this message]
1999-11-17 21:08 ` Geert Uytterhoeven
1999-11-17 23:48 ` Martin Costabel
1999-11-18 9:13 ` Martin Costabel
1999-11-18 0:35 ` Extreme swapping / new location of Paul's kernels [was Re: Kernel debugging??] phandel
1999-11-18 10:04 ` Benjamin Herrenschmidt
1999-11-18 10:22 ` phandel
1999-11-18 10:40 ` Benjamin Herrenschmidt
1999-11-19 0:51 ` Martin Costabel
1999-11-19 10:25 ` Benjamin Herrenschmidt
1999-11-18 2:37 ` Kernel debugging?? Paul Mackerras
1999-11-18 17:32 ` Michael Fenske
1999-11-18 18:30 ` Benjamin Herrenschmidt
1999-11-19 9:10 ` Michael Fenske
1999-11-20 19:36 ` Joel Klecker
1999-11-18 18:34 ` Kevin Hendricks
1999-11-18 23:29 ` Paul Mackerras
1999-11-18 10:02 ` Benjamin Herrenschmidt
1999-11-22 20:00 ` Geert Uytterhoeven
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=3831DE3B.5F2C790@wanadoo.fr \
--to=costabel@wanadoo.fr \
--cc=geert@linux-m68k.org \
--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.