From: Mikael Pettersson <mikpe@it.uu.se>
To: "Carlos R. Mafra" <crmafra2@gmail.com>
Cc: Mikael Pettersson <mikpe@it.uu.se>,
linux-kernel@vger.kernel.org,
James.Bottomley@HansenPartnership.com, htejun@gmail.com,
jens.axboe@oracle.com
Subject: Re: [BUG] 2.6.25-rc2-git3 broke cdrecord
Date: Mon, 3 Mar 2008 01:34:01 +0100 [thread overview]
Message-ID: <18379.18297.838050.536473@harpo.it.uu.se> (raw)
In-Reply-To: <20080302233415.GA6258@Pilar>
Carlos R. Mafra writes:
>
> On Sun 2.Mar'08 at 21:53:25 +0100, Mikael Pettersson wrote:
> > On my main workstation (Intel P965 chipset, ICH8 SATA driven by ahci,
> > Samsung/Toshiba SH-203P SATA DVD writer, FC5 user-space), cdrecord
> > stopped working on the 2.6.25-rc3 kernel, with the complaint:
> >
> > Warning: controller returns zero sized CD capabilities page.
> > Warning: controller returns wrong page 0 for CD capabilities page (2A).
> >
> > There's nothing in dmesg to suggest that the kernel has experienced
> > some problem.
> >
> > 2.6.25-rc2-git2 was the last working kernel, 2.6.25-rc2-git3 up to
> > today's 2.6.25-rc3-git3 are all non-working.
> >
> > I've narrowed the cause down to these two commits in 2.6.25-rc2-git3:
> >
> > 40b01b9bbdf51ae543a04744283bf2d56c4a6afa
> > block: update bio according to DMA alignment padding
> >
> > 6b00769fe1502b4ad97bb327ef7ac971b208bfb5
> > block: add request->raw_data_len
> >
> > Four or so subsequent commits depend on the second of these, so it's
> > easier to test them by applying them to -git2 than to revert them.
> >
> > Also, these two need to be treated as a unit. With only the first
> > applied, I get a massive delay as init tries to start udev, and then
> > if I try cdrecord it hangs in an unkillable state.
> >
> > I've put some information in
> > <http://user.it.uu.se/~mikpe/linux/bug-2.6.25-rc3-cdrecord/>:
> > - the kernel's .config
> > - cdrecord -VV dev=/dev/scd0 blank=fast output for 2.6.25-rc2-git2 and -git3
> > - strace -v logs for the above cdrecord runs
>
> I will try to help by pointing you to the patch here:
> http://lkml.org/lkml/2008/2/28/76
>
> It seems your problem is similar to the one Mike Galbraith reported.
That patch does seem to fix the problem. Thanks.
next prev parent reply other threads:[~2008-03-03 0:34 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-02 20:53 Mikael Pettersson
2008-03-02 23:34 ` Carlos R. Mafra
2008-03-03 0:34 ` Mikael Pettersson [this message]
2008-03-03 1:48 ` Stefan Richter
2008-03-03 8:26 ` FUJITA Tomonori
2008-03-03 9:08 ` Stefan Richter
2008-03-03 9:45 ` Mikael Pettersson
2008-03-03 10:20 ` Mikael Pettersson
2008-03-03 10:29 ` Tejun Heo
2008-03-03 14:51 ` James Bottomley
2008-03-03 17:39 ` Stefan Richter
2008-03-03 18:00 ` Boris Petkov
2008-03-03 21:41 ` Stefan Richter
2008-03-03 0:04 ` James Bottomley
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=18379.18297.838050.536473@harpo.it.uu.se \
--to=mikpe@it.uu.se \
--cc=James.Bottomley@HansenPartnership.com \
--cc=crmafra2@gmail.com \
--cc=htejun@gmail.com \
--cc=jens.axboe@oracle.com \
--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
all inboxes | Powered by JetHome®