public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Tupshin Harper <tupshin@tupshin.com>
To: linux-kernel <linux-kernel@vger.kernel.org>
Subject: 2.6.0-test6 happiness
Date: Sun, 05 Oct 2003 12:50:57 -0700	[thread overview]
Message-ID: <3F807621.9070702@tupshin.com> (raw)

I just wanted to give a *very* positive report about stock test6. In so 
many ways, it's a giant step forward for me.

1) 7 days of uptime (and counting) on a moderately loaded server running 
lvm2,xfs,nfs, and a whole bunch of services. Previous 2.5/2.6 record (up 
through test5)  was 2 1/2 days before any one of a variety of exceptions 
would occur. (Athlon XP system)

2) Dramatically improved desktop interactivity, with no audio glitching. 
(Different Athlon XP system)

3) Fully functional Dell Inspiron laptop (P3). This is the first time I 
have ever been able to boot this machine without disabling ACPI in the 
kernel(2.4.x included). I've also had many problems with 802.11b 
wireless pcmcia on this laptop, but it too works fine with this kernel. 
(These improvements might be a couple of versions old...didn't try test4 
or test5 on this machine).

Kudos, commendations, and thanks.

-Tupshin


                 reply	other threads:[~2003-10-05 19:51 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=3F807621.9070702@tupshin.com \
    --to=tupshin@tupshin.com \
    --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