2.6.8-rc3-mm1 & mm2 break k3b

2.6.8-rc3-mm1 & mm2 break k3b

[Robert Crawford]

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.

Robert Crawford

[cdrecord ('Cannot allocate memory') breakage] Re: 2.6.8-rc3-mm1 & mm2 break k3b

[bert hubert]

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

Re: 2.6.8-rc3-mm1 & mm2 break k3b

[Jens Axboe]

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

Re: 2.6.8-rc3-mm1 & mm2 break k3b

[Jens Axboe]

On Tue, Aug 10 2004, Jens Axboe wrote:
> 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.

Or 2.6.8-rc4-mm1, I see that is out as well.

-- 
Jens Axboe