linux-kernel - Re: 2.6.21-rc6-mm1 ATA HPT37x regression

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: <4624D4C3.9010109@ru.mvista.com>
Date:	Tue, 17 Apr 2007 18:08:03 +0400
From:	Sergei Shtylyov <sshtylyov@...mvista.com>
To:	John Stoffel <john@...ffel.org>
CC:	linux-kernel@...r.kernel.org, linux-ide@...r.kernel.org
Subject: Re: 2.6.21-rc6-mm1 ATA HPT37x regression

Hello.

John Stoffel wrote:

> I was just testing out 2.6.21-rc6-mm1 to test some Cyclades patches
> and I noticed that my HPT302 (rev1) controller with a pair of 120gb WD
> disks are not longer detected and I get the following in the dmesg
> logs:

>     [  148.121490] hpt37x: DPLL did not stabilize.

> Where before, under 2.6.21-rc6 I got the following:

   For the moment I thought you're reporting another hpt366.c driver breakage but then noticed the next line:

>     [  173.749349] pata_hpt37x: BIOS has not set timing clocks.
>     [  173.752949] hpt37x: HPT302: Bus clock 33MHz.

   Obviously this was bacause of switching from PCI to DPLL clock. The old and new drivers are different in how they handle DPLL calibration though.  Could you try hpt366.c (there's been report about its failure too recently -- not enought details yet)?

>     [  173.754409] ACPI: PCI Interrupt 0000:03:06.0[A] -> GSI 18 (level,
>     low) -> IRQ
>      18
>     [  173.758403] ata5: PATA max UDMA/133 cmd 0x0001ecf8 ctl 0x0001ecf2
>     bmdma 0x000
>     1e800 irq 18
>     [  173.761396] ata6: PATA max UDMA/133 cmd 0x0001ece0 ctl 0x0001ecda
>     bmdma 0x000
>     1e808 irq 18
>     [  173.764319] scsi6 : pata_hpt37x
>     [  173.928997] ATA: abnormal status 0x78 on port 0x0001ecff
>     [  173.930511] scsi7 : pata_hpt37x
>     [  174.094906] ATA: abnormal status 0x8 on port 0x0001ece7
 
> Here's my lspci infomation on the board, it's an addon.  My apologies
> for the crappy word wrapping, xterms inside screen, etc. 

>   03:06.0 RAID bus controller: Triones Technologies, Inc. HPT302/302N
>   (rev 01)
> 	  Subsystem: Triones Technologies, Inc. Unknown device 0001
> 	  Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop-
>   ParErr- Step
>   ping- SERR+ FastB2B-
> 	  Status: Cap+ 66MHz+ UDF- FastB2B- ParErr- DEVSEL=medium
>   >TAbort- <TAbort
>   - <MAbort- >SERR- <PERR-
> 	  Latency: 120 (2000ns min, 2000ns max)
> 	  Interrupt: pin A routed to IRQ 11
> 	  Region 0: I/O ports at ecf8 [size=8]
> 	  Region 1: I/O ports at ecf0 [size=4]
> 	  Region 2: I/O ports at ece0 [size=8]
> 	  Region 3: I/O ports at ecd8 [size=4]
> 	  Region 4: I/O ports at e800 [size=256]
> 	  Expansion ROM at f9000000 [disabled] [size=128K]
> 	  Capabilities: [60] Power Management version 2
> 		  Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA
>   PME(D0-,D1-,D2-,D3hot
>   -,D3cold-)
> 		  Status: D0 PME-Enable- DSel=0 DScale=0 PME-

   Yeah, that's a "plain" HPT302 chip with the default 66 MHz DPLL clock.

MBR, Sergei
-
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/