mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: <Hell.Surfers@cwctv.net>
To: kirk@braille.uwo.ca, alan@lxorguk.ukuu.org.uk,
	linux-kernel@vger.kernel.org
Subject: RE:Re: 2.5.xx kernels won't run on my Athlon boxes
Date: Fri, 6 Sep 2002 20:59:22 +0100	[thread overview]
Message-ID: <0c40b1758190692DTVMAIL7@smtp.cwctv.net> (raw)

[-- Attachment #1: Type: text/plain, Size: 234 bytes --]

If you have coding knowledge, you can cross write 2.5 with 2.4 IDE code... Lotsof people could help you, BUT i dont think it would be as easy as it sounds...



On 	06 Sep 2002 07:51:40 -0400 	Kirk Reiser <kirk@braille.uwo.ca> wrote:

[-- Attachment #2: Type: message/rfc822, Size: 2624 bytes --]

From: Kirk Reiser <kirk@braille.uwo.ca>
To: <Hell.Surfers@cwctv.net>
Cc: alan@lxorguk.ukuu.org.uk, linux-kernel@vger.kernel.org
Subject: Re: 2.5.xx kernels won't run on my Athlon boxes
Date: 06 Sep 2002 07:51:40 -0400
Message-ID: <x71y879vzn.fsf@speech.braille.uwo.ca>

<Hell.Surfers@cwctv.net> writes:

> I was going to suggest a kernel check from the begining of 2.4ac to see if the problem occurs at some point, as major features are usually stuck in from them first...

The 2.4.19 kernels seem to be fine on the box unless it's right after
I've rebooted from 2.5.33.  Then 2.4.19 seems to be flakey in various
interesting ways until I do a full shut off of the hardware and turn
it back on.  Usually when I'm seeing problems under 2.4.19 they seem
to be vm errors in processes.  It really likes to kill off my
setiathome process with a vm error.  It's very consistant.  I run a
twenty minute cron job to restart setiathome and vm kills it almost
immediately.  Of course, I shut down the box and turn it off and when
it comes back up it runs fine until I restart under 2.5 again.  Then
five minutes or so and it's dead in the water again.

  Kirk

-- 

Kirk Reiser				The Computer Braille Facility
e-mail: kirk@braille.uwo.ca		University of Western Ontario
phone: (519) 661-3061
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

             reply	other threads:[~2002-09-06 19:57 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-09-06 19:59 Hell.Surfers [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-09-06  0:55 Hell.Surfers

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=0c40b1758190692DTVMAIL7@smtp.cwctv.net \
    --to=hell.surfers@cwctv.net \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=kirk@braille.uwo.ca \
    --cc=linux-kernel@vger.kernel.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

all inboxes | Powered by JetHome®