From: Jens Axboe <axboe@suse.de>
To: Matthias Andree <matthias.andree@gmx.de>
Cc: Thomas Maguin <T.Maguin@web.de>, linux-scsi@vger.kernel.org
Subject: Re: cdrecord: Cannot allocate memory. Cannot get SCSI I/O buffer.
Date: Fri, 13 Jan 2006 10:52:23 +0100 [thread overview]
Message-ID: <20060113095221.GT3945@suse.de> (raw)
In-Reply-To: <m34q48qxd2.fsf@merlin.emma.line.org>
On Fri, Jan 13 2006, Matthias Andree wrote:
> Jens Axboe <axboe@suse.de> writes:
>
> > On Fri, Jan 13 2006, Thomas Maguin wrote:
> >> This patch is working with alpha04 on my mashine:
> >> http://de.geocities.com/linux_piewie/download/alpha04.txt
> >
> > So any particular reason you think this is a kernel bug??
>
> Perhaps because <http://de.geocities.com/linux_piewie/download/Readme.txt>
>
> contains this text:
>
> "3. solution for the root problem, not existent for kernel >= 2.6.14-rc2"
Dunno if that is what you meant, but it states that >= 2.6.14-rc2 fixes
the root problem - your line states that a solution for kernel >=
2.6.14-rc2 is non-existant.
> OTOH, if 2.6.14 and 2.6.15 are fixed, why would a kernel developer take
> interest? 2.6.X isn't "stable" after all... as fiercely discussed on
Well there's nothing to fix if it works in newer kernels, is there? I
can't travel back in time and make sure that eg 2.6.10 works.
--
Jens Axboe
next prev parent reply other threads:[~2006-01-13 9:50 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-12 12:21 cdrecord: Cannot allocate memory. Cannot get SCSI I/O buffer Thomas Maguin
2006-01-12 12:30 ` Matthias Andree
2006-01-12 12:32 ` Matthias Andree
2006-01-12 12:52 ` Thomas Maguin
2006-01-12 15:30 ` Matthias Andree
2006-01-13 8:23 ` Thomas Maguin
2006-01-13 9:02 ` Jens Axboe
2006-01-13 9:40 ` Matthias Andree
2006-01-13 9:52 ` Jens Axboe [this message]
2006-01-13 10:08 ` Matthias Andree
2006-01-13 10:14 ` Jens Axboe
2006-01-13 10:08 ` Thomas Maguin
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=20060113095221.GT3945@suse.de \
--to=axboe@suse.de \
--cc=T.Maguin@web.de \
--cc=linux-scsi@vger.kernel.org \
--cc=matthias.andree@gmx.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.