linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Thomas Molina <tmolina@cox.net>
To: Andrew Morton <akpm@digeo.com>
Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: 2.5.64-mm6
Date: Thu, 13 Mar 2003 14:35:18 -0600 (CST)	[thread overview]
Message-ID: <Pine.LNX.4.44.0303131419570.4241-100000@localhost.localdomain> (raw)
In-Reply-To: <20030313032615.7ca491d6.akpm@digeo.com>

On Thu, 13 Mar 2003, Andrew Morton wrote:

> 
> ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.5/2.5.64/2.5.64-mm6/
> 
> . Added all of Russell King's PCMCIA changes.  If anyone tests this on
>   cardbus/PCMCIA machines please let us know.

I decided to try it because of this.  My test machine was a Compaq 
Presario 12XL325, PIII-650, RedHat 8.0 with updates.  The cardbus bridge 
is listed as a TI PCI1410 controller.  I've been doing daily bk pulls and 
compiles on this machine for some time with no problems noted on the 
resulting kernel.  On the cardbus interface I have an SMC wireless NIC as 
modules.  

I downloaded the mm-6 patch and a pristine 2.5.64 tarball.  After applying 
the patch I compiled with the standard configuration I've been using all 
along.  No problems were noted during the compile cycle.  During bootup 
the system locked up at the point where it did a modprobe uhci-hcd for the 
USB controller.  Nothing of interest was noted in the log.  I rebooted 
with nousb in the command line and got a good boot.  After working with 
this kernel for awhile I don't see anything out of the ordainary except 
that on a 2.5.64-bk kernel I get 330 Kbytes per second download speed 
whereas with mm6 I get 280 Kbytes per second.  Several runs show this is 
fairly consistent, with results within one or two percent.

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"aart@kvack.org">aart@kvack.org</a>

  parent reply	other threads:[~2003-03-13 20:35 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-13 11:26 2.5.64-mm6 Andrew Morton
2003-03-13 16:23 ` 2.5.64-mm6 Jeremy Fitzhardinge
2003-03-13 19:34   ` 2.5.64-mm6 Andrew Morton
2003-03-13 20:07     ` 2.5.64-mm6 Roger Larsson
2003-03-14  3:04     ` 2.5.64-mm6 Steven Cole
2003-03-14  3:28       ` 2.5.64-mm6 Andrew Morton
2003-03-14  3:46         ` 2.5.64-mm6 Shawn
2003-03-14  3:51           ` 2.5.64-mm6 Andrew Morton
2003-03-14  3:56           ` 2.5.64-mm6 Robert Love
2003-03-13 20:35 ` Thomas Molina [this message]
2003-03-14  9:29 ` 2.5.64-mm6 Alexander Hoogerhuis
2003-03-14 11:55   ` 2.5.64-mm6 Andrew Morton
2003-03-15  8:38     ` 2.5.64-mm6 Alexander Hoogerhuis
2003-03-14 12:01 ` 2.5.64-mm6 Helge Hafting
2003-03-14 12:14   ` 2.5.64-mm6 Andrew Morton
2003-03-14 20:38 ` 2.5.64-mm6 Eli Carter
2003-03-14 20:53   ` 2.5.64-mm6 Andrew Morton
2003-03-14 22:01     ` 2.5.64-mm6 Eli Carter
2003-03-14 22:21       ` 2.5.64-mm6 Andrew Morton
2003-03-13 13:42 2.5.64-mm6 Felipe Alfaro Solana
2003-03-13 21:49 2.5.64-mm6 Felipe Alfaro Solana
2003-03-14  0:23 ` 2.5.64-mm6 Thomas Molina

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=Pine.LNX.4.44.0303131419570.4241-100000@localhost.localdomain \
    --to=tmolina@cox.net \
    --cc=akpm@digeo.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.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