From: bert hubert <ahu@ds9a.nl>
To: Robert Crawford <flacycads@access4less.net>
Cc: linux-kernel@vger.kernel.org
Subject: [cdrecord ('Cannot allocate memory') breakage] Re: 2.6.8-rc3-mm1 & mm2 break k3b
Date: Tue, 10 Aug 2004 09:52:39 +0200 [thread overview]
Message-ID: <20040810075239.GA23087@outpost.ds9a.nl> (raw)
In-Reply-To: <200408100011.30730.flacycads@access4less.net>
On Tue, Aug 10, 2004 at 12:11:30AM +0000, Robert Crawford wrote:
> Unable to determine the last tracks data mode. using default
> cdrecord returned an unknown error (code 12)
> Cannot allocate memory
This error has also been reported by:
Alexander Gran ( 0.5K) Re: Cannot burn without strace on 2.6.8-rc3-mm1
In his case it goes away when stracing the process.
--
http://www.PowerDNS.com Open source, database driven DNS Software
http://lartc.org Linux Advanced Routing & Traffic Control HOWTO
next prev parent reply other threads:[~2004-08-10 7:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-10 0:11 2.6.8-rc3-mm1 & mm2 break k3b Robert Crawford
2004-08-10 7:52 ` bert hubert [this message]
2004-08-10 8:14 ` Jens Axboe
2004-08-10 8:20 ` Jens Axboe
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=20040810075239.GA23087@outpost.ds9a.nl \
--to=ahu@ds9a.nl \
--cc=flacycads@access4less.net \
--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