linux-kernel - Re: pata_cs5536 hangs on boot with hdd attached

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]

Message-ID: <yq163x47wsy.fsf@sermon.lab.mkp.net>
Date:	Tue, 05 Feb 2008 01:16:13 -0500
From:	"Martin K. Petersen" <martin.petersen@...cle.com>
To:	Gregor Radtke <mail@...adtke.name>
Cc:	linux-kernel@...r.kernel.org, Tim Kunschke <beatmeistah@....de>
Subject: Re: pata_cs5536 hangs on boot with hdd attached

>>>>> "Gregor" == Gregor Radtke <mail@...adtke.name> writes:

Gregor,

Gregor> I tested with various kernel releases before 2.6.24 (and
Gregor> -rcX), up to 2.6.23.12. Both libata and the old ATA subsystem
Gregor> do work, libata with cs5535.

pata_cs5535 won't drive a 5536 -- they're completely different beasts.
So you haven't been testing what you think you're testing...

Try booting your pata_cs5536 kernel with libata.dma=0

I also suggest you try a kernel with pata_amd compiled in instead of
pata_cs5536.  Slight timings aside there shouldn't be any functional
difference between the way the two drivers configure things.  But let
us know how that goes.  And include the diff of the relevant portion
of the boot logs.

Finally - which drive is it?

-- 
Martin K. Petersen	Oracle Linux Engineering
--
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/