From: Sergei Shtylyov <sshtylyov@ru.mvista.com>
To: Bob Ham <rah@bash.sh>
Cc: Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>,
linux-ide@vger.kernel.org, Alan Cox <alan@lxorguk.ukuu.org.uk>
Subject: Re: hpt374 sata (Highpoint Rocket 1540)
Date: Thu, 02 Aug 2007 01:08:28 +0400 [thread overview]
Message-ID: <46B0F64C.7050706@ru.mvista.com> (raw)
In-Reply-To: <1186002225.16340.11.camel@orchid.arb.net>
Bob Ham wrote:
>>>hpt37x: DPLL did not stabilize.
>>>pata_hpt37x: BIOS has not set timing clocks.
>>>hpt37x: DPLL did not stabilize.
>> Yes, this ia a known issue, and the fix for it is in the -mm tree:
> I applied just that pata_hpt37x.c patch, not the whole -mm tree. It
> locks the machine hard again. Here is the transcribed output:
> hpt37x: Bus clock 66 MHz, using DPLL.
Oh?! hpt366.c detected 33 MHz... :-O
> ACPI: PCI Interrupt 0000:00:0d.0[A] -> GSI 16 (level, low) -> IRQ 17
> scsi2: pata_hpt37x
> scsi3: pata_hpt37x
> ata3: PATA max UDMA/100 cmd 0x0001efa0 ctl 0x0001ef9e bmdma 0x0001ec00 irq 17
> ata4: PATA max UDMA/100 cmd 0x0001ef90 ctl 0x0001ef9a bmdma 0x0001ec00 irq 17
MBR, Sergei
next prev parent reply other threads:[~2007-08-01 21:06 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-31 11:08 hpt374 sata (Highpoint Rocket 1540) Bob Ham
2007-07-31 12:23 ` Alan Cox
2007-07-31 20:12 ` Bob Ham
2007-07-31 13:29 ` Sergei Shtylyov
2007-07-31 15:35 ` Brad Campbell
2007-07-31 17:52 ` Sergei Shtylyov
2007-07-31 21:22 ` Bob Ham
2007-07-31 21:32 ` Bartlomiej Zolnierkiewicz
2007-07-31 22:06 ` Bob Ham
2007-08-01 13:40 ` Sergei Shtylyov
2007-08-01 15:52 ` Bob Ham
2007-08-01 15:58 ` Sergei Shtylyov
2007-08-01 17:15 ` Bob Ham
2007-08-01 18:19 ` Sergei Shtylyov
2007-08-01 22:43 ` Alan Cox
2007-08-02 12:41 ` Sergei Shtylyov
2007-08-02 13:12 ` Alan Cox
2007-08-01 21:03 ` Bob Ham
2007-08-01 21:08 ` Sergei Shtylyov [this message]
2007-08-01 22:42 ` Alan Cox
2007-08-05 18:10 ` Sergei Shtylyov
2007-08-01 21:07 ` Bartlomiej Zolnierkiewicz
2007-08-01 21:16 ` Sergei Shtylyov
2007-08-01 21:29 ` Bartlomiej Zolnierkiewicz
2007-08-01 16:14 ` Alan Cox
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=46B0F64C.7050706@ru.mvista.com \
--to=sshtylyov@ru.mvista.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=bzolnier@gmail.com \
--cc=linux-ide@vger.kernel.org \
--cc=rah@bash.sh \
/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).