linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <bh40@calva.net>
To: Tony Mantler <nicoya@apia.dhs.org>, <linuxppc-dev@lists.linuxppc.org>
Subject: Re: 2.4 madness!
Date: Thu, 5 Oct 2000 11:47:01 +0200	[thread overview]
Message-ID: <19340830031845.6771@192.168.1.2> (raw)
In-Reply-To: <v04003a04b60151e18975@[24.70.162.14]>


>over and over and over and over and over.
>
>Should I be expecting 2.4 to work, or is it still not quite there yet?

It should work (except for some known 2.4 VM bugs that are not PPC specific).

Can you check if it also crash without the Promise card ?


** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

      parent reply	other threads:[~2000-10-05  9:47 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-10-04 21:53 2.4 madness! Tony Mantler
2000-10-05  5:57 ` Michel Lanners
2000-10-05 20:06   ` Eric Lowe
2000-10-06 23:30   ` Tony Mantler
2000-10-05  9:47 ` Benjamin Herrenschmidt [this message]

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=19340830031845.6771@192.168.1.2 \
    --to=bh40@calva.net \
    --cc=linuxppc-dev@lists.linuxppc.org \
    --cc=nicoya@apia.dhs.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).