From: Sergei Shtylyov <sshtylyov@ru.mvista.com>
To: Andy Shaw <ashaw@seberg.co.uk>
Cc: linux-ide@vger.kernel.org
Subject: Re: [BUGREPORT 1/3] Kernel Oops with HPT372A IDE controller
Date: Fri, 19 May 2006 20:58:31 +0400 [thread overview]
Message-ID: <446DF937.9010607@ru.mvista.com> (raw)
In-Reply-To: <cadb0abbb3dd59f2fe9583e019508ef2@localhost>
Hello.
Andy Shaw wrote:
>>>>>>Kernel Oops with HighPoint RocketRAID ATA133 aka HPT372A/N since
>>>>>>kernel 2.6
>>>>>>Now tested with kernel 2.6.17-rc4
>>>>>>Kernel is on bootable CD-ROM
>>>>>>Modules are loaded from initrd
>>>>>>This is what I copied from screen:
>>>>>>Loading hpt366
>>>>>>[17179578.396000] HPT372A: IDE controller at PCI slot 0000:01:0a.0
>>>>>>[17179578.400000] ACPI: PCI Interrupt Link [APC1] enabled at IRQ 16
>>>>>>[17179578.404000] ACPI: PCI Interrupt 0000:01:0a.0[A] -> Link [APC1]
>>>>>>-> GSI 16 (level, high) -> IRQ 18
>>>>>>[17179578.408000] HPT372A: chipset revision 2
>>>>>>[17179578.412000] HPT372A: 100% native mode on irq 18
>>>>>>[17179578.416000] hpt: HPT372N detected, using 372N timing.
>>>>>>[17179578.420000] FREQ: 125 PLL: 45
>>>>>>[17179579.536000] No Clock Stabilization!!!
>>>>>>[17179579.540000] hpt: no known IDE timings, disabling DMA
>>>>>>[17179579.544000] hpt: HPT372N detected, using 372N timing.
>>>>>>[17179579.548000] FREQ: 156 PLL: 66
>>>>>>[17179579.664000] No Clock Stabilization!!!
>>>>> Please try my latest patches. This one should fix this (and oops
>>>>>should be gone):
>>>>>http://marc.theaimsgroup.com/?l=linux-ide&m=114677223914159&w=2
>>>>all patches applied, but I still get Kernel Oops :-(
>>>>some smal difference here:
>>>> HPT372A: IDE controller at PCI slot 0000:01:0a.0
>>>> ACPI: PCI Interrupt Link [APC1] enabled at IRQ 16
>>>> ACPI: PCI Interrupt 0000:01:0a.0[A] -> Link [APC1] -> GSI 16 (level,
>>>>high) -> IRQ 18
>>>> HPT372A: chipset revision 2
>>>> HPT372A: 100% native mode on irq 18
>>>>+ HPT37X: no clock data saved by BIOS
>>>>+ HPT3xxN detected, FREQ: 124, PLL: 45
>>>>+ HPT37xN unknown bus timing [48 4].
>>> Hm, the BIOS seems to behave nastier than expected -- looks like it
>>>reprograms DPLL but doesn't save the initial f_CNT (needed to determine
>>>the PCI clock). Well, I know that it always sets DPLL to 50 MHz, no matter
>>>what's the chip, so will try to work around this... :-/
>> OTOH, there might be another reason to that: the BIOS saves f_CNT but
>>the register it uses for this isn't mapped to the PCI config. space, only to
>>the I/O space (it's undocumented, after all). Andy Shaw's report seems to
>>confirm this -- his RAID BIOS seems to be modern enough to save the f_CNT but the
>>driver probably fails to read it (I don't have the full boot log yet).
>> So, try the attached patch please. Foli, if this won't help, can you
>>tell what version your HighPoint BIOS is?
> I can confirm that after applying your most recent patches my HighPoint card works. I have four disks attached to the two HPT IDE sockets and all four disks are picked up. I haven't been able to confirm whether DMA is supported yet but will update as soon as I get the chance.
> For anyone interested these patches have been applied to kernel 2.6.17-rc4-mm1. The lspci entry for the card looks like:
> 0000:03:01.0 RAID bus controller: Triones Technologies, Inc. HPT372A/372N (rev 02)
HPT372N, that is.
> Many thanks for your efforts.
Have you applied the patch I sent out this night? Was it this patch that
fixed the driver for you? This is indeed important.
> Rgds
> Andy
WBR, Sergei
next prev parent reply other threads:[~2006-05-19 18:00 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-14 19:10 [BUGREPORT 1/3] Kernel Oops with HPT372A IDE controller Foli Ayivoh
2006-05-15 14:54 ` Sergei Shtylyov
2006-05-16 22:59 ` Foli Ayivoh
2006-05-17 14:36 ` Sergei Shtylyov
2006-05-18 21:47 ` Sergei Shtylyov
2006-05-19 7:36 ` Andy Shaw
2006-05-19 16:58 ` Sergei Shtylyov [this message]
2006-06-09 9:51 ` Foli Ayivoh
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=446DF937.9010607@ru.mvista.com \
--to=sshtylyov@ru.mvista.com \
--cc=ashaw@seberg.co.uk \
--cc=linux-ide@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).