linux-kernel - Re: non functional pata dvd drive under 2.6.25.6

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:	Fri, 18 Jul 2008 14:00:42 +0900
From:	Tejun Heo <tj@...nel.org>
To:	Jeroen Beerstra <jb@...rpion77.cjb.net>
CC:	linux-kernel@...r.kernel.org,
	IDE/ATA development list <linux-ide@...r.kernel.org>
Subject: Re: non functional pata dvd drive under 2.6.25.6

Hello, Jeroen.

[cc'ing linux-ide]

Jeroen Beerstra wrote:
> hi there,
> 
> I've filed this as a bug with redhat bugzilla (12-6), https://
> bugzilla.redhat.com/show_bug.cgi?id=451081, but so far I've had no 
> response at all ... so here we go ;)
> 
> Basicly my ide dvd writer is non functional with Fedora 9 (kernel 
> 2.6.25.6). So far I've seen it functional only once when I booted with 
> media already inserted, but for the rest it's pretty much like this:
> 
> excerpt from dmesg
> 
> ata10.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 frozen
> ata10.00: cmd a0/00:00:00:00:00/00:00:00:00:00/a0 tag 0
>          cdb 1e 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00
>          res 40/00:02:00:08:00/00:00:00:00:00/a0 Emask 0x4 (timeout)
> ata10.00: status: { DRDY }
> ata10: soft resetting link
> ata10: nv_mode_filter: 0x1&0x1f01f->0x1, BIOS=0x1f000 (0xc5000000) 
> ACPI=0x1f01f (30:600:0x13)
> ata10.00: configured for PIO0
> ata10: EH complete
> ata10.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 frozen
> ata10.00: cmd a0/00:00:00:00:00/00:00:00:00:00/a0 tag 0
>          cdb 1e 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00
>          res 40/00:02:00:08:00/00:00:00:00:00/a0 Emask 0x4 (timeout)
> ata10.00: status: { DRDY }
> ata10: soft resetting link
> ata10: nv_mode_filter: 0x1&0x1f01f->0x1, BIOS=0x1f000 (0xc5000000) 
> ACPI=0x1f01f (30:600:0x13)
> ata10.00: configured for PIO0
> ata10: EH complete
> sr 10:0:0:0: ioctl_internal_command return code = 8000002
>    : Sense Key : Aborted Command [current] [descriptor]
>    : Add. Sense: No additional sense information
> ata10.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 frozen
> ata10.00: cmd a0/00:00:00:00:00/00:00:00:00:00/a0 tag 0
>          cdb 00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00
>          res 40/00:02:00:08:00/00:00:00:00:00/a0 Emask 0x4 (timeout)
> ata10.00: status: { DRDY }
> ata10: soft resetting link
> ata10: nv_mode_filter: 0x1&0x1f01f->0x1, BIOS=0x1f000 (0xc5000000) 
> ACPI=0x1f01f (30:600:0x13)
> ata10.00: configured for PIO0
> ata10: EH complete
> 
> cat /sys/bus/scsi/devices/10:0:0:0/model 
> PATA 20X20X12X 
> 
> The drive is completely non functional.
> 
> System is a Nforce 780i SLI MB (Asus P5N-T Deluxe) with an Q9450 INtel 
> Core2 Quad CPU and 4 GB of ram.
> 
> With Windows XP/Vista there are no problems with this drive and also I 
> had no problems installing Fedora from this drive in the first place, so 
> I doubt if it is a hardware problem. 
> 
> I can live with the fact that I only have one writer available but not 
> with the fact that everything that tries to access the drive hangs with 
> status D for a very long time, hald-addon-storage for one....

Hmmm... the problem could be caused by hald polling for media presence.
 Does "hal-disable-polling /dev/srX" make any difference?
hal-disable-polling setting is persistent so if your drive goes bonkers
quickly after boot, you can disable polling, reboot and see whether
anything is different.  Also, please post the result of "lspci -nn" and
"hdparm -I /dev/srX" && please try 2.6.26.

Thanks.

-- 
tejun
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/