From: Sergei Shtylyov <sshtylyov@ru.mvista.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Johan Palmqvist <johan.palmqvist@inap.se>,
mlaks@verizon.net, linux-kernel@vger.kernel.org,
linux-ide@vger.kernel.org
Subject: Re: hpt366 driver oops or panic with HighPoint RocketRAID 1520 SATA (HPT372N)
Date: Fri, 05 May 2006 02:21:28 +0400 [thread overview]
Message-ID: <445A7E68.7080109@ru.mvista.com> (raw)
In-Reply-To: <1146781505.24513.3.camel@localhost.localdomain>
Hello.
Alan Cox wrote:
> On Iau, 2006-05-04 at 23:53 +0400, Sergei Shtylyov wrote:
>
>> I think I've dealt with this oops now, see my recent patches to this
>>driver, particularly the one that reads the f_CNT value saved by BIOS...
>
>
> I have them queued to review in depth, although in that specific case I
> don't know if I can help - none of my cards set the BIOS provided
> value..
Judging on a FREQ value (about 125) from the boot logs, the BIOS had set
up PLL to 50 MHz (125/192 ~ 32/50) which should have "spoilt" the value in the
f_CNT register. Hence, we may guess that the BIOS had saved the f_CNT value
beforehand. If not, there's not much we can do except to guess at the DPLL
frequence that BIOS might have set.
MBR, Sergei
prev parent reply other threads:[~2006-05-04 22:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <436FB350.6020309@inap.se>
2005-11-08 16:37 ` hpt366 driver oops or panic with HighPoint RocketRAID 1520 SATA (HPT372N) Alan Cox
2005-11-11 21:08 ` Sergei Shtylylov
2006-04-03 16:58 ` Sergei Shtylyov
2006-05-04 19:53 ` Sergei Shtylyov
2006-05-04 22:25 ` Alan Cox
2006-05-04 22:21 ` Sergei Shtylyov [this message]
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=445A7E68.7080109@ru.mvista.com \
--to=sshtylyov@ru.mvista.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=johan.palmqvist@inap.se \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mlaks@verizon.net \
/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).