linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sergei Shtylyov <sshtylyov@ru.mvista.com>
To: John Stoffel <john@stoffel.org>
Cc: linux-kernel@vger.kernel.org, linux-ide@vger.kernel.org
Subject: Re: 2.6.21-rc6-mm1 ATA HPT37x regression
Date: Tue, 17 Apr 2007 21:06:16 +0400	[thread overview]
Message-ID: <4624FE88.2010908@ru.mvista.com> (raw)
In-Reply-To: <17956.63043.521397.597430@smtp.charter.net>

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:
 
> Sergei> For the moment I thought you're reporting another hpt366.c
> Sergei> driver breakage but then noticed the next line:

> I used to think that I wanted to use that driver too, but it's not
> going to work.  It's because I've got the version 1 of the chip, not
> the newer version 2 or higher version.

   So what?

> It looks like you really mean for me to use the hpt3x2.c driver
> instead, since that's the only other one which mentions the
> PCI_DEVICE_ID_TTI_HPT302 device id in it's init method.

   I actually meant drivers/ide/pci/hpt366.c. :-)
 
>>>[  173.749349] pata_hpt37x: BIOS has not set timing clocks.
>>>[  173.752949] hpt37x: HPT302: Bus clock 33MHz.
 
> Sergei>    Obviously this was bacause of switching from PCI to DPLL
> Sergei>    clock. The old and new drivers are different in how they
> Sergei>    handle DPLL calibration though.  Could you try hpt366.c
> Sergei>    (there's been report about its failure too recently -- not
> Sergei>    enought details yet)?

> I don't think it will work here, it won't even touch the card since
> the pci_device_id won't match at all.  The htp366.c only looks at
> HPT366 ids, while mine is an HPT302 id.

   The driver I've named should work (unless something is broken somewhere, that is).
Basically, it uses wider range to calibrate DPLL.

> As a quick note, 2.6.21-rc7 is working just fine here.

   Yeah, it's still using PCI clock.

> Ok, so do I need to do anything special with the next -mm release and
> the next version?

   Well, let Alan decide that (2Alan: and I said that HPT code is bogus :-).

> Thanks,
> John

MBR, Sergei

  reply	other threads:[~2007-04-17 17:06 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-17  2:36 2.6.21-rc6-mm1 ATA HPT37x regression John Stoffel
2007-04-17 14:08 ` Sergei Shtylyov
2007-04-17 16:30   ` John Stoffel
2007-04-17 17:06     ` Sergei Shtylyov [this message]
2007-04-17 17:13       ` Alan Cox
2007-04-17 19:27         ` John Stoffel
2007-04-17 19:37           ` Sergei Shtylyov
2007-04-17 20:03             ` Mark Lord
2007-04-19  1:34           ` John Stoffel
2007-04-19  1:49             ` John Stoffel

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4624FE88.2010908@ru.mvista.com \
    --to=sshtylyov@ru.mvista.com \
    --cc=john@stoffel.org \
    --cc=linux-ide@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).