public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@suse.de>
To: Robert Crawford <flacycads@access4less.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6.8-rc3-mm1 & mm2 break k3b
Date: Tue, 10 Aug 2004 10:14:54 +0200	[thread overview]
Message-ID: <20040810081453.GJ10381@suse.de> (raw)
In-Reply-To: <200408100011.30730.flacycads@access4less.net>

On Tue, Aug 10 2004, Robert Crawford wrote:
> I posted this on the Con Kolivas kernel list, and he suggested I post
> here, regarding 2.6.8-rc3-mm kernels. I'm no expert by any means, but
> have been testing kernels since 2.5.67, and have posted about kernels
> on the Gentoo & PCLOS forums, among others.
> 
> "Just tested the latest staircase7.I with 2.6.8-rc3 vanilla, and
> 2.6.8-rc3-mm2, and both work fine- no problems I can see so far on my
> test box. However,  2.6.8-rc3-mm1 and mm2 both still break my k3b cd
> burning software, with these errors (using cdrecord 2.1a33, on Gentoo)
> :
> 
> Unable to determine the last tracks data mode. using default cdrecord
> returned an unknown error (code 12) Cannot allocate memory
> 
> Sometimes it says to lower the burn speed, even when it's set to 4x
> (on a 48x burner), but that doesn't solve the problem. I get the same
> errors.
> 
> This doesn't occur with all previous mm kernels (up to 2.6.8-rc2-mm2),
> or any other kernel I've tried, and not with any ck patches, so I'm
> convinced it's the rc3-mm patches causing this, and not anything ck."
> If I boot with other kernels, same hardware, same config file, k3b
> works perfectly.

Try 2.6.8-rc4, please.

-- 
Jens Axboe


  parent reply	other threads:[~2004-08-10  8:15 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 ` [cdrecord ('Cannot allocate memory') breakage] " bert hubert
2004-08-10  8:14 ` Jens Axboe [this message]
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=20040810081453.GJ10381@suse.de \
    --to=axboe@suse.de \
    --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