From: Dragan Stancevic <visitor@xalien.org>
To: Markus Walser <walsi@freesurf.ch>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Terrible Memory leak on 2.6
Date: Tue, 17 Aug 2004 22:01:32 -0700 [thread overview]
Message-ID: <200408172201.32461.visitor@xalien.org> (raw)
In-Reply-To: <200408172349.11738.walsi@freesurf.ch>
On Tuesday 17 August 2004 14:49, Markus Walser wrote:
> yes, same problem here. And on the SuSE mailing list many other reported
> the same when burning audio CDRs. I could reproduce it with
> vanilla-2.6.8-rc3/ 2.6.8-rc4 too. Up to now I was just reading about
> problems with IDE drives.
Thanks Markus for your mail. My CD is an ide drive too. And this only
happens when burning or ripping CDs. Mount and copy work fine for me.
Is that the case for you too?
PS: I dare not try and burn a DVD.
--
Peace can only come as a natural consequence
of universal enlightenment. -Dr. Nikola Tesla
prev parent reply other threads:[~2004-08-18 5:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-15 7:51 Terrible Memory leak on 2.6 Dragan Stancevic
2004-08-17 21:49 ` Markus Walser
2004-08-18 5:01 ` Dragan Stancevic [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=200408172201.32461.visitor@xalien.org \
--to=visitor@xalien.org \
--cc=linux-kernel@vger.kernel.org \
--cc=walsi@freesurf.ch \
/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