All of lore.kernel.org
 help / color / mirror / Atom feed
From: linas@austin.ibm.com
To: Hollis Blanchard <hollisb@us.ibm.com>
Cc: Hawkins Jeffrey-CJH016 <Jeffrey.F.Hawkins@motorola.com>,
	linuxppc-dev@lists.linuxppc.org
Subject: Re: Kernel Panic in 2.2.x
Date: Fri, 30 May 2003 11:34:02 -0500	[thread overview]
Message-ID: <20030530113402.B29314@forte.austin.ibm.com> (raw)
In-Reply-To: <AD5AB542-92BA-11D7-A2DA-000A95A0560C@us.ibm.com>; from hollisb@us.ibm.com on Fri, May 30, 2003 at 11:20:50AM -0500


On Fri, May 30, 2003 at 11:20:50AM -0500, Hollis Blanchard wrote:
>
> On Friday, May 30, 2003, at 11:11 US/Central, Hawkins Jeffrey-CJH016
> wrote:
> >>
> >> With respect to responses, please don't say go to the 2.4.x Kernel
> >> as a solution for the Issue....:)  This is in our plans, but
> >> at this time,
> >> we are locked into the 2.2 Kernel due to Proprietary Hardware Driver
> >> Support.  For the short term, I just want to identify the true root
> >> cause (to appease the Management Gods), and to possibly implement
> >> a short term fix until we migrate to the 2.4.x or 2.6 Kernel.
>
> Hi Jeff, I know it's important to you, but I would be pretty surprised
> if you could interest anyone else with a 2.2 bug. :) You may want to

I did read in slashdot about some group that was planing on supporting
version 2.2 indefinitely.

Its not a bad idea ... I run a 2.2 kernel on a server; I haven't switched
to 2.4 because the particular tool that I need was never ported to 2.4.
I occasionally think about doing the port myself, but time constraints
& all ... I'm expecting to keep that server on 2.2 forever, or at least
till the hardware dies.

Latest & greatest is only the best if you are a developer.  For users,
old-trustworthy is usually a much better bet.

--linas

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

  reply	other threads:[~2003-05-30 16:34 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-30 16:11 Kernel Panic in 2.2.x Hawkins Jeffrey-CJH016
2003-05-30 16:20 ` Hollis Blanchard
2003-05-30 16:34   ` linas [this message]
2003-05-30 16:40     ` Hollis Blanchard
2003-05-30 21:48       ` linas
2003-05-30 22:11         ` Hollis Blanchard
2003-05-31  0:58         ` Linas Vepstas
2003-06-02 14:53           ` Hollis Blanchard
2003-06-02 16:47             ` linas
2003-06-03 22:01           ` Remote serial console through USB daRonin
  -- strict thread matches above, loose matches on Subject: below --
2003-05-30 22:47 Kernel Panic in 2.2.x Hawkins Jeffrey-CJH016
2003-05-29 19:04 Hawkins Jeffrey-CJH016

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=20030530113402.B29314@forte.austin.ibm.com \
    --to=linas@austin.ibm.com \
    --cc=Jeffrey.F.Hawkins@motorola.com \
    --cc=hollisb@us.ibm.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 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.