linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: bugme-daemon@bugzilla.kernel.org
To: linux-ide@vger.kernel.org
Subject: [Bug 11742] New: Device buffer on a DVD multi standard writer runs out burning a CD
Date: Sat, 11 Oct 2008 15:54:52 -0700 (PDT)	[thread overview]
Message-ID: <bug-11742-11633@http.bugzilla.kernel.org/> (raw)

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

           Summary: Device buffer on a DVD multi standard writer runs out
                    burning a CD
           Product: IO/Storage
           Version: 2.5
     KernelVersion: 2.6.27
          Platform: All
        OS/Version: Linux
              Tree: Mainline
            Status: NEW
          Severity: normal
          Priority: P1
         Component: IDE
        AssignedTo: io_ide@kernel-bugs.osdl.org
        ReportedBy: valerio.p@libero.it


Latest working kernel version: 2.6.26
Earliest failing kernel version:2.6.27
Distribution: Debian Unstable
Hardware Environment: Laptop Acer 5920G with a Samsung CDDVDW TS-L632H
connected through IDE 
Software Environment: KDE 3.5.9; k3b 1.0.5; Brasero
Problem Description: I have compiled the 2.6.27 kernel using make oldconf, thus
almost copying the passed 2.6.26.5 configuration. Since then, when I burn a CD
the internal buffer in my DVD burner reaches 0% obliging k3b and brasero to
slow down the writing speed. It happens even if I don't run any other
application. I have noticed that the device buffer runs out even if the
software buffer is full, like there was not a fast transfer from the software
buffer to the device buffer. In the end, k3b reports a big amount of buffer
under-runs (> 100).Everything works as expected with an older 2.6.26.5 kernel.
What I need to do to help solving this bug? See you

Valerio

Steps to reproduce: Using 2.6.27 kernel and k3b or brasero to burn a CD. It
works in simulation mode too (so you don't waste too much CD's ;))


-- 
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.

             reply	other threads:[~2008-10-11 22:54 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-11 22:54 bugme-daemon [this message]
2008-10-11 23:31 ` [Bug 11742] Device buffer on a DVD multi standard writer runs out burning a CD 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
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=bug-11742-11633@http.bugzilla.kernel.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 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).