From: Ronny Buchmann <ronny-lkml@vlugnet.org>
To: Marko Kreen <marko@l-t.ee>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>, linux-kernel@vger.kernel.org
Subject: Re: [OOPS] 2.4.22 / HPT372N
Date: Tue, 9 Sep 2003 14:06:56 +0200 [thread overview]
Message-ID: <200309091406.56334.ronny-lkml@vlugnet.org> (raw)
Marko Kreen wrote:
> On Thu, Sep 04, 2003 at 10:46:53PM +0100, Alan Cox wrote:
>> On Iau, 2003-09-04 at 20:07, Marko Kreen wrote:
>> > As i used the pen&paper method for oops tracking i dont have
>> > full oops.
>> >
>> > In hpt366.c function hpt372_tune_chipset line 427:
>> >
>> > list_conf = pci_bus_clock_list(speed,
>> > (struct chipset_bus_clock_list_entry *)
>>
>> I thought I'd fixed that crash case but it seems your system is over
>> clocked.
>>
>> FREQ: 85 PLL: 41
>> hpt: no known IDE timings,
>>
>> so your PCI bus is running at somewhere about 35Mhz and outside the
>> drivers safe threshold.
>
> Thats surprising, nobody has intentionally overclocked it.
>
> Now we did some experimenting with it and no BIOS settings seem
> to affect the FREQ numbers. (Lower CPU/mem speed, 50/25 AGP/PCI speed.)
> The FREQ still stays fixed at 85.
>
> Motherboard is EP-4PDA2+.
>
> Any idea how to remove the overclocking? Otherwise it seems
> like driver bug to me.
What bios version do you use? Have you tried a CMOS reset?
I have the same motherboard but a different problem with the hpt chip, only
the first channel is recognized. (see
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=97824)
part from dmesg (klogd) output
---
Sep 7 23:50:17 bserv kernel: HPT366: IDE controller at PCI slot 02:00.0
Sep 7 23:50:17 bserv kernel: HPT366: chipset revision 6
Sep 7 23:50:17 bserv kernel: HPT366: not 100%% native mode: will probe irqs
later
Sep 7 23:50:17 bserv kernel: hpt: HPT372N detected, using 372N timing.
Sep 7 23:50:17 bserv kernel: FREQ: 82 PLL: 35
Sep 7 23:50:17 bserv kernel: HPT37X: using 50MHz internal PLL
Sep 7 23:50:17 bserv kernel: ide2: BM-DMA at 0x8000-0x8007, BIOS
settings:
hde:DMA, hdf:pio
Sep 7 23:50:17 bserv kernel: HPT372N support is EXPERIMENTAL ONLY.
---
Currently the driver provided by highpoint
(http://www.highpoint-tech.com/hpt3xx-opensource-v131.tgz) is working ok for
me (apart from it's lack of s.ma.r.t. support).
Did you try this?
--
ronny
next reply other threads:[~2003-09-09 12:09 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-09 12:06 Ronny Buchmann [this message]
2003-09-11 12:34 ` Marko Kreen
2003-09-12 9:41 ` Ronny Buchmann
2003-09-12 10:48 ` Alan Cox
2003-09-12 12:32 ` Ronny Buchmann
2003-09-12 12:46 ` Alan Cox
2003-09-12 12:58 ` Bartlomiej Zolnierkiewicz
2003-09-12 14:24 ` Ronny Buchmann
2003-09-12 14:42 ` Bartlomiej Zolnierkiewicz
2003-09-12 15:26 ` Ronny Buchmann
2003-09-12 16:35 ` Bartlomiej Zolnierkiewicz
2003-09-12 20:32 ` Ronny Buchmann
-- strict thread matches above, loose matches on Subject: below --
2003-09-04 19:07 Marko Kreen
2003-09-04 21:46 ` Alan Cox
2003-09-05 14:54 ` Marko Kreen
2003-09-05 21:51 ` 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=200309091406.56334.ronny-lkml@vlugnet.org \
--to=ronny-lkml@vlugnet.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=marko@l-t.ee \
/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
all inboxes | Powered by JetHome®