From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: akorud@polynet.lviv.ua
Cc: linux-kernel@vger.kernel.org
Subject: Re: Where are you going with 2.4.x?
Date: Sun, 11 Feb 2001 17:17:26 +0000 (GMT) [thread overview]
Message-ID: <E14S07t-0004Ty-00@the-village.bc.nu> (raw)
In-Reply-To: <1394806431.20010211181744@polynet.lviv.ua> from "Andriy Korud" at Feb 11, 2001 06:17:44 PM
> I've installed 2.4.x there. Just immedualtely I've noticed performance
> improve, responce time improve.
That is good news
> BUT: All kernels prior to 2.1.4-ac8 hangs during first few hours of
> work on heavy disk (Mylex) activity.
Ok Im glad to know we have made some progress there
> 2.1.4-ac8 was the first kernel which was able to work nore then 24
> hours. But on 26'th our of work it crashed with:
>
> Kernel panic: Aiee:, killing interrupt handler!
> In interrupt handler - not syncing
What is the oops data before the kernel panic. I need that to debug the
driver. Also did you build the DAC960 support with gcc 2.96-x x<74 ?
> Can I know your thoughts about target market of 2.4.x kernel? I assume
> that the goal is to make it feature-rich multimedia desktop system?
And a rock solid server and anything else people want it to be.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2001-02-11 17:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-11 16:17 Andriy Korud
2001-02-11 17:17 ` Alan Cox [this message]
2001-02-11 18:01 ` Re[2]: " Andriy Korud
2001-02-11 18:13 ` David Weinehall
2001-02-12 16:32 ` Christian Ehrhardt
2001-02-13 10:55 ` Serial Console and plam (was: Where are you going with 2.4.x?) ehrhardt
2001-02-11 20:23 ` Re[2]: Where are you going with 2.4.x? Alan Cox
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=E14S07t-0004Ty-00@the-village.bc.nu \
--to=alan@lxorguk.ukuu.org.uk \
--cc=akorud@polynet.lviv.ua \
--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®