public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@suse.de>
To: DervishD <raul@pleyades.net>
Cc: Linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: 3-order allocation failed with cdda2wav
Date: Tue, 16 Mar 2004 19:56:09 +0100	[thread overview]
Message-ID: <20040316185609.GV2977@suse.de> (raw)
In-Reply-To: <20040316184640.GA14088@DervishD>

On Tue, Mar 16 2004, DervishD wrote:
>     Hi all :)
> 
>     I've recently started to use cdda2wav (I've been using cdparanoia
> for years and wanted to take a look at cdda2wav), and I have a
> problem: each time I use cdda2wav the kernel spills '__alloc_pages:
> 3-order allocation failed (gpf=0x20/0)' six times.
> 
>     I'm using cdrtools 2.0.3, with kernel 2.4.25 and ide-scsi. I have
> a Plextor CD-writer that I use to do CDDA ripping, but the problem
> appears with other drives too (I've tested with a Liteon DVD, too).
> 
>     Maybe a cdda2wav problem? Kernel problem?

You can ignore the messages, but yeah I know they are annoying...

>     In addition to this problem, I have another one, this time
> related with interfaces: if I use the SCSI generic interface with
> cdda2wav, it runs without problems (well, except that noted above)
> but uses a lot of CPU (up to 60%), so I tested with cooked_ioctl
> interface, and then the CPU use drops to 4% but I got two error
> messages about CDIOCSETCDDA not available, but the allocation problem
> DOES NOT HAPPEN :?
> 
>     Any help? Thanks in advance :)

Upgrade to 2.6.5-rc1, it'll solve all your problems in this area :-)

-- 
Jens Axboe


  reply	other threads:[~2004-03-16 18:56 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-16 18:46 3-order allocation failed with cdda2wav DervishD
2004-03-16 18:56 ` Jens Axboe [this message]
2004-03-16 19:00   ` DervishD

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=20040316185609.GV2977@suse.de \
    --to=axboe@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=raul@pleyades.net \
    /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