All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugme-daemon@bugzilla.kernel.org
To: linux-ide@vger.kernel.org
Subject: [Bug 11742] Device buffer on a DVD multi standard writer runs out burning a CD
Date: Thu, 16 Oct 2008 09:33:49 -0700 (PDT)	[thread overview]
Message-ID: <20081016163349.9AC88108040@picon.linux-foundation.org> (raw)
In-Reply-To: <bug-11742-11633@http.bugzilla.kernel.org/>

http://bugzilla.kernel.org/show_bug.cgi?id=11742





------- Comment #21 from valerio.p@libero.it  2008-10-16 09:33 -------
Thank Boris and Stan for you replies.

Stan said:
>If ata_piix works for you, just use that. Please attach the boot time errors
>you mentioned in Comment #14 so that they can be fixed in libata/ata_piix.

Don't worry, it was "my" mistake. In the procedure I've found to blacklist piix
it was not mentioned to "depmod -ae" before creating an initrd image. Anyhow,
now that I have fixed it, there is no more any warning at boot time :).
It's time to be happy, relax and take a coffee ;)


>You could bisect search for the commit which is causing that regression -
>this'll be of great help. Here's a good tutorial on that:
Ok, it seems not easy, but sadly now I've a lot of free time and I think that
spending it on helping in fixing this bug is not that bad... at least until you
have both frameworks in the kernel. I don't want to mess in the discussion, I'm
not a developer, just an user. But I have a practical approach to almost
everything and IMO until we have both, we should have them working and avoid
problems to other users. I consider this as a service to the community. That's
all


-- 
Configure bugmail: http://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

  parent reply	other threads:[~2008-10-16 16:33 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-11 22:54 [Bug 11742] New: Device buffer on a DVD multi standard writer runs out burning a CD bugme-daemon
2008-10-11 23:31 ` [Bug 11742] " bugme-daemon
2008-10-13  6:44 ` bugme-daemon
2008-10-13  8:25 ` bugme-daemon
2008-10-14  5:55 ` bugme-daemon
2008-10-14  8:23 ` bugme-daemon
2008-10-14  8:37 ` bugme-daemon
2008-10-14  8:38 ` bugme-daemon
2008-10-14  8:40 ` bugme-daemon
2008-10-15  1:51 ` bugme-daemon
2008-10-15  5:08 ` bugme-daemon
2008-10-15 11:11 ` bugme-daemon
2008-10-15 11:13 ` bugme-daemon
2008-10-15 11:22 ` bugme-daemon
2008-10-16  0:18 ` bugme-daemon
2008-10-16  8:54 ` bugme-daemon
2008-10-16 10:00 ` bugme-daemon
2008-10-16 12:36 ` bugme-daemon
2008-10-16 12:56 ` bugme-daemon
2008-10-16 14:49 ` bugme-daemon
2008-10-16 14:51 ` bugme-daemon
2008-10-16 14:56 ` bugme-daemon
2008-10-16 16:33 ` bugme-daemon [this message]
2008-10-16 16:42 ` bugme-daemon
2008-10-16 17:16 ` bugme-daemon

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=20081016163349.9AC88108040@picon.linux-foundation.org \
    --to=bugme-daemon@bugzilla.kernel.org \
    --cc=linux-ide@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 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.