Page 2 of 2

Re: Burning disks seems to freeze daryna

Posted: Wed Jan 02, 2008 3:50 pm
by NiksaVel
P.S. KDE Daryna kicks a$$!!! Had a bunch of friends here for new years eve party drooling all over my setup :D

Re: Burning disks seems to freeze daryna

Posted: Sat Jan 05, 2008 4:35 pm
by NiksaVel
I'm afraid that after a few days of being away from my comp I have to report that the problem still persists... every second, third or sometimes fourth DVD that I try to burn freezes my comp and I have to do a hard reset...

This problem is becoming EXTREMELY annoying and I'm close to fixing it with a hammer permenantly :evil: if anyone has any ideas please help me out...

Re: Burning disks seems to freeze daryna

Posted: Sat Jan 05, 2008 5:23 pm
by NiksaVel
here's a little clip from my /var/log/kern.log file... maybe this could give some ideas to some1..

Code: Select all

Jan  5 21:20:40 localhost kernel: [  182.554328] NET: Registered protocol family 17
Jan  5 21:38:14 localhost kernel: [ 1229.960392] hdc: DMA timeout retry
Jan  5 21:38:14 localhost kernel: [ 1229.960401] hdc: timeout waiting for DMA
Jan  5 21:38:14 localhost kernel: [ 1234.964817] hdc: status timeout: status=0xd0 { Busy }
Jan  5 21:38:14 localhost kernel: [ 1234.964821] ide: failed opcode was: unknown
Jan  5 21:38:14 localhost kernel: [ 1234.964828] hdc: drive not ready for command
Jan  5 21:38:14 localhost kernel: [ 1239.370687] Clocksource tsc unstable (delta = 9374162295 ns)
Jan  5 21:38:14 localhost kernel: [ 1239.373285] Time: acpi_pm clocksource has been installed.
Jan  5 21:39:38 localhost kernel: [ 1323.323169] cdrom: This disc doesn't have any tracks I recognize!
Jan  5 21:45:59 localhost kernel: [ 1704.005882] ppdev0: registered pardevice
Jan  5 21:46:11 localhost kernel: [ 1715.509146] ppdev0: unregistered pardevice
Jan  5 21:46:43 localhost kernel: [ 1747.226815] ppdev0: registered pardevice
Jan  5 21:46:56 localhost kernel: [ 1758.831756] ppdev0: unregistered pardevice
Jan  5 21:53:04 localhost kernel: [ 2128.863679] cdrom: This disc doesn't have any tracks I recognize!

Re: Burning disks seems to freeze daryna

Posted: Sat Jan 05, 2008 6:04 pm
by nick
Hi
""I'm having this after recording 2 DVDs on a TSSTcorpCD/DVDW TS-H552B. The first burns ok but when writing the next DVD the system slows to a crawl. I was able to pin point the issue to hald-addon-storage and also get those kernel errors, but it is hald-addon-storage that slows the system down.""


https://bugs.launchpad.net/ubuntu/+sour ... +bug/75295

""UPDATE: Fix status timeout: status=0xd0 { Busy }
I got a nice Acer laptop for not much from PC World, but it has a sucky TSSTcorpCD/DVDW TS-L632D, ATAPI""----- Fix Here
http://www.liddicott.com/~sam/?p=79

Also get those messages when drive is on way out

Nick

Re: Burning disks seems to freeze daryna

Posted: Sun Jan 06, 2008 1:01 pm
by NiksaVel
hey nick, thanks for pointing this one out... even though it doesn't solve my problem, at least I can put my finger on it and it makes me breath a heck of a lot easier knowing that there are other people out there with the same prob.. :D

After going through all those threads I can deffinitelly confirm that I have the bug reported at: https://bugs.launchpad.net/ubuntu/+sour ... +bug/75295

I'll post back here as the situation develops... unfortunately from what I see this is a bug that's been around since edgy... :(


btw... this is the error that keeps looping in dmesg or /var/log/kern.log:

Code: Select all

[58779.299206] hdc: DMA timeout retry
[58779.299216] hdc: timeout waiting for DMA
[58784.299239] hdc: status timeout: status=0xd0 { Busy }
[58784.299244] ide: failed opcode was: unknown
[58784.299251] hdc: drive not ready for command
[58789.299290] hdc: status timeout: status=0xd0 { Busy }
[58789.299293] ide: failed opcode was: unknown
[58789.299298] hdc: drive not ready for command
[58794.327354] hdc: status timeout: status=0xd0 { Busy }
[58794.327362] ide: failed opcode was: unknown
[58794.327368] hdc: drive not ready for command
[58799.327379] hdc: status timeout: status=0xd0 { Busy }
[58799.327386] ide: failed opcode was: unknown
[58799.327391] hdc: drive not ready for command
[58804.343418] hdc: status timeout: status=0xd0 { Busy }
[58804.343425] ide: failed opcode was: unknown
[58804.343431] hdc: drive not ready for command
[58809.343471] hdc: status timeout: status=0xd0 { Busy }
[58809.343478] ide: failed opcode was: unknown
[58809.343483] hdc: drive not ready for command
[58814.567356] hdc: status timeout: status=0xd0 { Busy }
[58814.567363] ide: failed opcode was: unknown
[58814.567372] hdc: drive not ready for command
[58819.579390] hdc: status timeout: status=0xd0 { Busy }
[58819.579397] ide: failed opcode was: unknown
[58819.579402] hdc: drive not ready for command
[58824.599427] hdc: status timeout: status=0xd0 { Busy }
[58824.599434] ide: failed opcode was: unknown
[58824.599439] hdc: drive not ready for command
[58829.631453] hdc: status timeout: status=0xd0 { Busy }
[58829.631460] ide: failed opcode was: unknown
[58829.631464] hdc: drive not ready for command
[58834.767397] hdc: status timeout: status=0xd0 { Busy }
[58834.767405] ide: failed opcode was: unknown
[58834.767410] hdc: drive not ready for command
[58839.799425] hdc: status timeout: status=0xd0 { Busy }
[58839.799432] ide: failed opcode was: unknown
[58839.799437] hdc: drive not ready for command
[58845.670790] hdc: status timeout: status=0xd0 { Busy }
[58845.670799] ide: failed opcode was: unknown
[58845.670805] hdc: drive not ready for command
[58850.710811] hdc: status timeout: status=0xd0 { Busy }
[58850.710820] ide: failed opcode was: unknown
[58850.710825] hdc: drive not ready for command
[58856.094561] hdc: status timeout: status=0xd0 { Busy }
[58856.094570] ide: failed opcode was: unknown
[58856.094575] hdc: drive not ready for command
[58861.418356] hdc: status timeout: status=0xd0 { Busy }
[58861.418365] ide: failed opcode was: unknown
[58861.418371] hdc: drive not ready for command
[58868.129058] hdc: status timeout: status=0xd0 { Busy }
[58868.129067] ide: failed opcode was: unknown
[58868.129072] hdc: drive not ready for command
[58873.237026] hdc: status timeout: status=0xd0 { Busy }
[58873.237036] ide: failed opcode was: unknown
[58873.237041] hdc: drive not ready for command
[58878.680728] hdc: status timeout: status=0xd0 { Busy }
[58878.680737] ide: failed opcode was: unknown
[58878.680743] hdc: drive not ready for command
[58883.788695] hdc: status timeout: status=0xd0 { Busy }
[58883.788704] ide: failed opcode was: unknown
[58883.788709] hdc: drive not ready for command
[58888.876677] hdc: status timeout: status=0xd0 { Busy }
[58888.876686] ide: failed opcode was: unknown
[58888.876690] hdc: drive not ready for command
[58893.968657] hdc: status timeout: status=0xd0 { Busy }
[58893.968666] ide: failed opcode was: unknown
[58893.968671] hdc: drive not ready for command
[58899.056641] hdc: status timeout: status=0xd0 { Busy }
[58899.056649] ide: failed opcode was: unknown
[58899.056654] hdc: drive not ready for command
[58904.144624] hdc: status timeout: status=0xd0 { Busy }
[58904.144632] ide: failed opcode was: unknown
[58904.144637] hdc: drive not ready for command
[58909.456429] hdc: status timeout: status=0xd0 { Busy }
[58909.456438] ide: failed opcode was: unknown
[58909.456442] hdc: drive not ready for command
[58914.692296] hdc: status timeout: status=0xd0 { Busy }
[58914.692305] ide: failed opcode was: unknown
[58914.692309] hdc: drive not ready for command
[58919.792271] hdc: status timeout: status=0xd0 { Busy }
[58919.792280] ide: failed opcode was: unknown
[58919.792285] hdc: drive not ready for command
[58924.912227] hdc: status timeout: status=0xd0 { Busy }
[58924.912236] ide: failed opcode was: unknown
[58924.912240] hdc: drive not ready for command
[58930.064161] hdc: status timeout: status=0xd0 { Busy }
[58930.064169] ide: failed opcode was: unknown
[58930.064174] hdc: drive not ready for command
[58935.136156] hdc: status timeout: status=0xd0 { Busy }
[58935.136165] ide: failed opcode was: unknown
[58935.136170] hdc: drive not ready for command
[58940.415987] hdc: status timeout: status=0xd0 { Busy }
[58940.415996] ide: failed opcode was: unknown
[58940.416002] hdc: drive not ready for command
[58945.699817] hdc: status timeout: status=0xd0 { Busy }
[58945.699825] ide: failed opcode was: unknown
[58945.699829] hdc: drive not ready for command
[58950.767814] hdc: status timeout: status=0xd0 { Busy }
[58950.767823] ide: failed opcode was: unknown
[58950.767827] hdc: drive not ready for command
[58955.999683] hdc: status timeout: status=0xd0 { Busy }
[58955.999692] ide: failed opcode was: unknown
[58955.999697] hdc: drive not ready for command
[58961.139628] hdc: status timeout: status=0xd0 { Busy }
[58961.139637] ide: failed opcode was: unknown
[58961.139642] hdc: drive not ready for command
[58966.395477] hdc: status timeout: status=0xd0 { Busy }
[58966.395486] ide: failed opcode was: unknown
[58966.395492] hdc: drive not ready for command
[58966.571367] hdc: ATAPI reset complete
you can see near the bottom the result of the

Code: Select all

sudo hdparm -w /dev/hdc
The system came back to life instantly - k3b reported a failed burn at the DVD was ruined, but at least I can get my system back now without hard reset and know what the problem is...

Re: Burning disks seems to freeze daryna

Posted: Sun Jan 06, 2008 1:07 pm
by NiksaVel
also... if some1 has more knowledge in this particular area... what seems to me here is that the driver for the IDE ports is conflicting in some freak hardware setups and I'm one of the lucky winners...

if anyone knows some other configurations I might try please do shed some light on the subject... I've noticed they've been mentioning something about the problem starting to occur with the introduction od the piix driver - but I don't think I'm using that... I guess? :mrgreen:

Re: Burning disks seems to freeze daryna

Posted: Sun Jan 06, 2008 3:29 pm
by nick
Hi

Just remembered, I had problems with my previous CD/DVD
timing out - wrong cable, I had used standard IDE cable,

When I replaced it with 80-conductor IDE cable UDMA
all problems cured, also cured my neighbours box, even
though the supplied cable was 40-conductor

Nick

Re: Burning disks seems to freeze daryna

Posted: Sun Jan 06, 2008 4:12 pm
by NiksaVel
I'll try to change the cable... that's the simplest solution :mrgreen:

Re: Burning disks seems to freeze daryna

Posted: Tue Jan 08, 2008 11:21 am
by NiksaVel
A little update on the problem... it isn't just enough to reset my /dev/hdc, I have to do it just before burning...

I have burnt a DVD yesterday, and did the reset right after the burning process finished.

Sure enough the first DVD I tried to burn today froze up the system again. reset got it back and the second attempt was successful.