linux-kernel - Re: SATA Burner Pioneer DVR-216-DBK won't burn

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Wed, 15 Oct 2008 16:47:01 +0200
From:	Peter Alfredsen <loki_val@...too.org>
To:	Tejun Heo <tj@...nel.org>
Cc:	linux-kernel@...r.kernel.org, linux-ide@...r.kernel.org
Subject: Re: SATA Burner Pioneer DVR-216-DBK won't burn

I've tried to burn other things in the meantime. Some things, I'm
actually able to burn. But when I can't burn something, I have so far
been able to reproduce the failure. Very strange.

On Tuesday 14 October 2008, Tejun Heo <tj@...nel.org> wrote:
> Hello,
>
> Peter Alfredsen wrote:
> > [please CC me on replies]
> > Linux loki 2.6.27-rc8 #5 SMP PREEMPT Sun Oct 5 17:56:00 CEST 2008
> > x86_64 Intel(R) Core(TM)2 Quad CPU Q9550 @ 2.83GHz GenuineIntel
> > GNU/Linux
> >
> > I recently acquired a DVR-216-DBK Pioneer SATA burner. With my old
> > burner, a DVR-110D,  I am able to burn a DVD. With the DVR-216DBK,
> > I'm not, it stops always at 98%, no matter which speed I burn at.
>
> Can you please attach kernel boot log?  And does the kernel whine
> about anything after the failure?

No, but when my harddrives have a lot of IO, sometimes the DVD drive
will reset itself. It's hard to duplicate and happens only when the
moon is right, but has never happened while the drive was actually in use:
Oct  5 23:45:50 loki kernel: [18287.041021] ata5.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
Oct  5 23:45:50 loki kernel: [18287.041029] ata5.00: cmd a0/00:00:00:00:00/00:00:00:00:00/a0 tag 0
Oct  5 23:45:50 loki kernel: [18287.041030]          cdb 35 02 00 00 00 00 00 00  00 00 00 00 00 00 00 00
Oct  5 23:45:50 loki kernel: [18287.041031]          res 40/00:03:00:00:00/00:00:00:00:00/a0 Emask 0x4 (timeout)
Oct  5 23:45:50 loki kernel: [18287.041034] ata5.00: status: { DRDY }
Oct  5 23:45:50 loki kernel: [18287.041039] ata5: hard resetting link
Oct  5 23:45:50 loki kernel: [18287.499015] ata5: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
Oct  5 23:45:50 loki kernel: [18287.503347] ata5.00: configured for UDMA/66
Oct  5 23:45:50 loki kernel: [18287.503357] ata5: EH complete

> > My motherboard is a ASUS P5Q-EM, I have 8GB of ram and am running
> > Gentoo Linux. I've tried both cdrkit and cdrtools.
> > DVR-216-DBK Fails, connected to ICH10R AHCI SATA controller
> > DVR-110D Succeeds, connected to Marvell 6101 PATA_MARVELL
> > controller
>
> What if you swap the two?  Or is one SATA and the other PATA?

Yes.

> In 
> that case, can you get a chip sil3152 controller (probably ~10USD)
> and see whether it works any better?

Sorry.

> > This seems to me to point to a problem with the AHCI driver's
> > interaction with the drive.
> >
> > Attached is lspci -k and debug output from K3B:
> >
> > 00:1f.2 SATA controller: Intel Corporation 82801JI (ICH10 Family)
> > SATA AHCI Controller
> >         Kernel driver in use: ahci
>
> I suppose the drive is hanging off this one, right?

Yes.

> >  3942252544/4008087552 (98.4%) @16.8x, remaining 0:03 RBU 100.0%
> > UBU 100.0%
> >
> > :-[ WRITE@...=1ddcd0h failed with SK=5h/ASC=A8h/ACQ=04h]:
> > : Input/output
> >
> > error
> >
> > :-( write failed: Input/output error
> >
> > /dev/sr0: flushing cache
>
> k3b doesn't really show which command failed.  I suppose it's
> WRITE(10).  The failure code is ILLEGAL REQUEST and the ASC/ASCQ are
> vendor specific and don't really tell us much detail about the
> failure.  :-(
>
> Can you please try wodim with "-pad -v -V" options?  It will generate
> a lot of output.  You'll probably want to redirect the output to a
> file and watch it using tail or less.

When I get around to finding something to burn that fails again, I will
take a look at this and see if I can get more detailed logs.

-- 
/PA

View attachment "dmesg" of type "text/plain" (70161 bytes)

Download attachment "signature.asc " of type "application/pgp-signature" (198 bytes)