public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ed Sweetman <safemode@comcast.net>
To: Con Kolivas <kernel@kolivas.org>
Cc: Justin Piszcz <jpiszcz@lucidpixels.com>,
	apiszcz@lucidpixels.com, linux-kernel@vger.kernel.org
Subject: Re: Burning audio CD's is totally broken under 2.6.8.1.
Date: Sat, 28 Aug 2004 20:02:40 -0400	[thread overview]
Message-ID: <41311D20.7050600@comcast.net> (raw)
In-Reply-To: <41306C8F.8040307@kolivas.org>

I went to linux-2.6.8-rc1-ck6 when i found this problem to exist in 
2.6.7 and patches to the kernel and the problem went away.  But I was 
told it had nothing t odo with the ck6 patchset as it didn't touch the 
area that was effected (as i was told anyway).  

I've just upgraded to 2.6.9-rc1-mm1 (with nick's patch and mm's patches 
backed out as he suggested to do).  Now the kernel does not leak memory, 
which it did with vanilla 2.6.9-rc1. 

Audio writing however doesn't seem to be using dma. I get heavy io 
related cpu usage when burning the cd that brings write speed and system 
responsiveness down significantly. This should not be  obviously and i 
was wondering if that had something to do with why the mem leak no 
longer exists or if it's something else entirely separate.  Note, in ck6 
audio writing was fine and did not exibit this non-dma-like behavior and 
no configuration changes were made between versions. DMA is detected and 
enabled for the drive in data mode. 





Con Kolivas wrote:

> Justin Piszcz wrote:
>
>> Out of Memory: Killed process 737 (xchats).
>
>
> Known issue:
> http://marc.theaimsgroup.com/?l=linux-kernel&m=109309119620622&w=2
>
> Cheers,
> Con



      parent reply	other threads:[~2004-08-29  0:02 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-28 11:15 Burning audio CD's is totally broken under 2.6.8.1 Justin Piszcz
2004-08-28 11:29 ` Con Kolivas
2004-08-28 11:30   ` Justin Piszcz
2004-08-29  0:02   ` Ed Sweetman [this message]

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=41311D20.7050600@comcast.net \
    --to=safemode@comcast.net \
    --cc=apiszcz@lucidpixels.com \
    --cc=jpiszcz@lucidpixels.com \
    --cc=kernel@kolivas.org \
    --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