From: Andrew Morton <akpm@osdl.org>
To: Uwe Bugla <uwe.bugla@gmx.de>
Cc: linux-ide@vger.kernel.org, linux-kernel-announce@vger.kernel.org,
Jens Axboe <axboe@kernel.dk>, Adrian Bunk <bunk@stusta.de>,
Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>
Subject: Re: 2.6.20-rc6: known unfixed regressions (v2) (part 2)
Date: Sun, 28 Jan 2007 15:21:31 -0800 [thread overview]
Message-ID: <20070128152131.a4354c91.akpm@osdl.org> (raw)
In-Reply-To: <20070128133344.214070@gmx.net>
On Sun, 28 Jan 2007 14:33:44 +0100
"Uwe Bugla" <uwe.bugla@gmx.de> wrote:
> > Subject : problems with CD burning
> > References : http://www.spinics.net/lists/linux-ide/msg06545.html
> > Submitter : Uwe Bugla <uwe.bugla@gmx.de>
> > Status : unknown
> >
> >
>
> ...
>
> Hi everybody,
> the problem I already reported for earlier release candidates of kernel 2.6.20
> (rc1 – 5) unfortunately stills persists.
>
> The regression has become more extreme: While in earlier release candidates nerolinux recognized my burning devices at least after the first start and then never again after all following starts the situation in rc6 is different from that:
>
> The CD and DVD burning devices aren´t recognized even once and the drive seek errors I already reported are still there.
>
> nerolinux runs excellently with kernel 2.6.19.2, but only shows an “image recorder” (i. e. no burning device at all) in kernel 2.6.20-rc6.
>
> Still hope that this terrible bug will not be part of the final version of 2.6.20!
>
Not sure what to do about this. It looks like a failure in the IDE driver.
Perhaps you could start by telling us about the IDE hardware, which driver
is in use, etc.
Is the floppy-disk bug still there?
next prev parent reply other threads:[~2007-01-28 23:24 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.4.64.0701241847360.25027@woody.linux-foundation.org>
2007-01-26 18:11 ` 2.6.20-rc6: known unfixed regressions (part 2) Adrian Bunk
2007-01-26 19:04 ` Michal Piotrowski
2007-01-27 17:42 ` 2.6.20-rc6: known unfixed regressions (v2) " Adrian Bunk
2007-01-28 13:33 ` Uwe Bugla
2007-01-28 23:21 ` Andrew Morton [this message]
2007-02-02 12:58 ` Uwe Bugla
2007-01-29 6:26 ` Mike Galbraith
2007-01-29 6:48 ` Andrew Morton
2007-01-29 7:08 ` Mike Galbraith
2007-01-29 7:13 ` Linus Torvalds
2007-01-29 7:04 ` Linus Torvalds
2007-01-29 7:19 ` Mike Galbraith
2007-01-29 10:01 ` Mike Galbraith
2007-01-29 18:16 ` Mike Galbraith
2007-01-29 18:43 ` Linus Torvalds
2007-01-30 4:14 ` Mike Galbraith
2007-01-29 17:16 ` Mike Christie
2007-01-29 20:37 ` Mike Christie
2007-01-29 20:58 ` Linus Torvalds
2007-01-29 22:16 ` Linus Torvalds
2007-01-29 23:01 ` Linus Torvalds
2007-01-29 23:32 ` Linus Torvalds
2007-01-29 23:42 ` Mike Christie
2007-01-30 0:23 ` Linus Torvalds
2007-01-30 0:55 ` Mike Christie
2007-01-30 1:04 ` Mike Christie
2007-01-30 1:45 ` Linus Torvalds
2007-01-30 2:50 ` Mike Christie
2007-01-30 3:02 ` Mike Christie
2007-01-30 3:08 ` Andrew Morton
2007-01-30 2:18 ` Mike Christie
2007-01-30 3:33 ` Andrew Morton
2007-01-30 4:44 ` Linus Torvalds
2007-01-30 4:00 ` Mike Galbraith
2007-01-30 3:25 ` Mike Galbraith
2007-01-30 4:14 ` Jeff Garzik
2007-02-02 13:07 ` Uwe Bugla
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=20070128152131.a4354c91.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=axboe@kernel.dk \
--cc=bunk@stusta.de \
--cc=bzolnier@gmail.com \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel-announce@vger.kernel.org \
--cc=uwe.bugla@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).