linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Downing, Thomas" <Thomas.Downing@ipc.com>
To: "'Andrew Morton'" <akpm@osdl.org>,
	linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: RE: 2.6.0-test1-mm1
Date: Thu, 17 Jul 2003 07:57:38 -0400	[thread overview]
Message-ID: <170EBA504C3AD511A3FE00508BB89A920234CD4A@exnanycmbx4.ipc.com> (raw)

> -----Original Message-----
> From: Andrew Morton [mailto:akpm@osdl.org]
> 
> ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/
> 2.6.0-test1/2.6.0-test1-mm1/
> 
> . Lots of bugfixes.
> 
> . A big one-liner from Mark Haverkamp fixes some hanges which 
> were being
>   seen with the aacraid driver and may fix the problem which 
> people have seen
>   on other SCSI drivers: everything getting stuck in 
> io_schedule() under load.
> 
> . Another interactivity patch from Con.  Feedback is needed on this
>   please - we cannot make much progress on this fairly subjective work
>   without lots of people telling us how it is working for them.

I have been testing 2.5.75-mm1.  I was able to cause video skip in xine,
but not audio.  I will repeat the tests using test1-mm1.  Anyone else
seen the video-only type skip?  It appears to be caused by other GUI
operations, not so much by CPU load.  Just dragging windows is not enough,
it needs to be more intensive than that.

More results later with test1-mm1

Thanks for all the great stuff!!

td

             reply	other threads:[~2003-07-17 11:43 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-17 11:57 Downing, Thomas [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-07-20 18:50 2.6.0-test1-mm1 Downing, Thomas
2003-07-16  5:56 2.6.0-test1-mm1 Andrew Morton
2003-07-16  6:16 ` 2.6.0-test1-mm1 Joshua Kwan
2003-07-16  6:22   ` 2.6.0-test1-mm1 Andrew Morton
2003-07-16  8:07 ` 2.6.0-test1-mm1 Sean Neakums
2003-07-16  8:55   ` 2.6.0-test1-mm1 Ingo Molnar
2003-07-16 10:19     ` 2.6.0-test1-mm1 Antonio Vargas
2003-07-16 13:37       ` 2.6.0-test1-mm1 Helge Hafting
2003-07-16 14:24         ` 2.6.0-test1-mm1 Antonio Vargas
2003-07-16  9:15   ` 2.6.0-test1-mm1 Con Kolivas
2003-07-16 10:44 ` 2.6.0-test1-mm1 Barry K. Nathan
2003-07-16 10:58   ` 2.6.0-test1-mm1 Andrew Morton
2003-07-16 12:24     ` 2.6.0-test1-mm1 William Lee Irwin III
2003-07-16 14:32       ` 2.6.0-test1-mm1 Barry K. Nathan
2003-07-16 14:41         ` 2.6.0-test1-mm1 William Lee Irwin III
2003-07-16 15:02           ` 2.6.0-test1-mm1 Barry K. Nathan
2003-07-16 15:09             ` 2.6.0-test1-mm1 William Lee Irwin III
2003-07-16 16:38               ` 2.6.0-test1-mm1 Andrew Morton
2003-07-16 14:03     ` 2.6.0-test1-mm1 Barry K. Nathan
2003-07-16 12:53 ` 2.6.0-test1-mm1 Philippe Gramoullé
2003-07-16 17:21 ` 2.6.0-test1-mm1 Ramón Rey Vicente󮠒
2003-07-16 19:01   ` 2.6.0-test1-mm1 Zwane Mwaikambo
2003-07-16 23:25     ` 2.6.0-test1-mm1 Ramón Rey Vicente󮠒
2003-07-16 23:56       ` 2.6.0-test1-mm1 Zwane Mwaikambo
2003-07-16 22:02 ` 2.6.0-test1-mm1 Mike Fedyk
2003-07-16 22:08   ` 2.6.0-test1-mm1 William Lee Irwin III
2003-07-16 22:17     ` 2.6.0-test1-mm1 Mike Fedyk
2003-07-16 22:36   ` 2.6.0-test1-mm1 William Lee Irwin III
2003-07-16 22:56     ` 2.6.0-test1-mm1 Mike Fedyk

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=170EBA504C3AD511A3FE00508BB89A920234CD4A@exnanycmbx4.ipc.com \
    --to=thomas.downing@ipc.com \
    --cc=akpm@osdl.org \
    --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;
as well as URLs for NNTP newsgroup(s).