Bug 449173 - burning slow
Summary: burning slow
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 9
Hardware: i386
OS: Linux
low
low
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2008-05-30 21:31 UTC by Philipp N.
Modified: 2009-11-16 17:00 UTC (History)
1 user (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2009-11-16 17:00:41 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Philipp N. 2008-05-30 21:31:27 UTC
Description of problem:
the burning is agonizingly slow
the mouse does not move fluently (and if music plays, this is no longer fluently
either)
then burning is about 1x even if 4x or more is possible


Version-Release number of selected component (if applicable):
fedora 7-9

How reproducible:
start k3b or any other burning program and burn a disk

Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:

hdparm -i /dev/cdrom

/dev/cdrom:

Model=HL-DT-ST DVD-RW GWA-4082N , FwRev=CW02 , SerialNo=9688CA465AE5
Config={ Fixed Removeable DTR<=5Mbs DTR>10Mbs nonMagnetic }
RawCHS=0/0/0, TrkSize=0, SectSize=0, ECCbytes=0
BuffType=unknown, BuffSize=0kB, MaxMultSect=0
(maybe): CurCHS=0/0/0, CurSects=0, LBA=yes, LBAsects=0
IORDY=on/off, tPIO={min:120,w/IORDY:120}, tDMA={min:120,rec:120}
PIO modes: pio0 pio1 pio2 pio3 pio4
DMA modes: mdma0 mdma1 mdma2
UDMA modes: udma0 udma1 *udma2
AdvancedPM=no
Drive conforms to: ATA/ATAPI-5 T13 1321D revision 3: ATA/ATAPI-2,3,4,5

* signifies the current active mode 

(It is not the dma mode... well at least Ubuntu works fast with this (udma2-) mode)

Comment 1 Harry Bock 2008-06-03 18:59:32 UTC
I can confirm this problem; seems like the same drive, different revision
(laptop). Working while burning is impossible; it brings the load average up to
at least 1.8 on my machine. Also, many times the burn fails, with
gnome-cd-burner reporting that the "system is too slow to burn at this speed".
Didn't have this problem with older versions of Fedora, and current Ubuntu 8.04
is fine as well.


[hbock@fuyutsuki ~]$ /sbin/hdparm -i /dev/sr0

/dev/sr0:

 Model=HL-DT-ST DVD-RW GWA-4082N               , FwRev=CB03    ,
SerialNo=478CB1981E34        
 Config={ Fixed Removeable DTR<=5Mbs DTR>10Mbs nonMagnetic }
 RawCHS=0/0/0, TrkSize=0, SectSize=0, ECCbytes=0
 BuffType=unknown, BuffSize=0kB, MaxMultSect=0
 (maybe): CurCHS=0/0/0, CurSects=0, LBA=yes, LBAsects=0
 IORDY=on/off, tPIO={min:120,w/IORDY:120}, tDMA={min:120,rec:120}
 PIO modes:  pio0 pio1 pio2 pio3 pio4 
 DMA modes:  mdma0 mdma1 mdma2 
 UDMA modes: udma0 udma1 *udma2 
 AdvancedPM=no
 Drive conforms to: ATA/ATAPI-5 T13 1321D revision 3:  ATA/ATAPI-2,3,4,5

 * signifies the current active mode


Comment 2 Philipp N. 2008-06-06 21:11:10 UTC
Yes it is exactly that bug! Fedora 6 I remember as working very well. About 7 I
am not sure, but I am about 8 and I can confirm it for 9. There was wodim in k3b
and then the bug appeared...
... even more strange is, that every other distro support our drive.

Bye

Comment 3 John Poelstra 2008-06-27 23:56:03 UTC
changing to ASSIGNED.  We do not use the VERIFIED state and it appears this bug
is still present.

Comment 4 Roman Rakus 2008-07-01 13:35:13 UTC
I can't reproduce it. With my HL-DT-ST DVDRAM GSA-E40L everything works well.
And I think this is related to the kernel improvments -> reassigning to kernel.
If this is not related to kernel, feel free to reassign back to cdrkit.

Comment 5 Philipp N. 2008-07-05 13:16:57 UTC
We have the 4082N drive, not yours so that does not say anything about the
reproducibility.
Of course it can be a kernel bug, too. My reason to assign it to cdrkit was
wodim, which appeared in k3b, but that can be chance, too. The kernel makes more
sense of course, because I don't think there are many (or even any) changes
between Ubuntu's (or Mandriva's) cdrkit and Fedora's. But the kernels definitely
have differences!

Comment 6 Bug Zapper 2009-06-10 01:18:04 UTC
This message is a reminder that Fedora 9 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 9.  It is Fedora's policy to close all
bug reports from releases that are no longer maintained.  At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '9'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 9's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 9 is end of life.  If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 7 Bug Zapper 2009-07-14 18:04:56 UTC
Fedora 9 changed to end-of-life (EOL) status on 2009-07-10. Fedora 9 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.

Comment 8 Philipp N. 2009-09-12 00:04:41 UTC
the reason is the change from "hda" and "sda" to "sda" only

not sure what the new tool for handling ide devices is, but that is the reason

Comment 9 John Poelstra 2009-11-16 17:00:41 UTC
Fedora 9 is no longer maintained.  If this bug exists in a currently maintained version please reopen against that version.

Thank you


Note You need to log in before you can comment on or make changes to this bug.