linux-kernel - Re: Misidentification and failing revalidations of ide dvd-roms with libata

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, 30 Jul 2008 21:39:40 +0100
From:	Alistair John Strachan <alistair@...zero.co.uk>
To:	Simen Timian Thoresen <simentt@...phinics.no>
Cc:	Alan Cox <alan@...rguk.ukuu.org.uk>, linux-kernel@...r.kernel.org
Subject: Re: Misidentification and failing revalidations of ide dvd-roms with libata

On Wednesday 30 July 2008 18:31:15 Simen Timian Thoresen wrote:
> Alistair John Strachan wrote:
> > I used Alan's nForce4 pata driver for a year or so and didn't have any
> > problems. OTOH maybe at this stage it's worth checking whether amd74xx
> > (old IDE) breaks in similar ways?
>
> from dmesg, I have this;
>
> [   17.647757] pata_amd 0000:00:06.0: version 0.3.10
> [   17.650097] scsi0 : pata_amd
> [   17.650229] scsi1 : pata_amd
> (that's the one, right?)
>
> ...so the driver exists in the running kernel. Would I have to build my
> own kernel, or is there some way to have this driver take hold instead
> of libata? ...or can I do something in modprobe.conf to use the other
> driver?

I have no clue what your distributor has enabled or disabled. The easiest way 
would be to ignore your distribution kernel and just build your own one.

You'll probably need to disable pata_amd (from "Serial ATA (prod) and Parallel 
ATA (experimental) drivers") and enable amd74xx (from "ATA/ATAPI/MFM/RLL 
support -> Enhanced IDE/MFM/RLL disk/cdrom/tape/floppy support -> AMD and 
nVidia IDE support (NEW)"). Note that you'll also need ide-cd for this 
subsystem.

As for DMA, I know there were issues with ATAPI on nForce 4 chipsets, but I 
don't really know the specifics. Could you try sata_nv.adma=0 on the kernel 
cmdline? This is probably a red herring though, as I'm not sure what relation 
the sata_nv driver has to pata_amd.

-- 
Cheers,
Alistair.
--
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/