From: Marko Kreen <marko@l-t.ee>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [OOPS] 2.4.22 / HPT372N
Date: Fri, 5 Sep 2003 17:54:53 +0300 [thread overview]
Message-ID: <20030905145452.GA24201@l-t.ee> (raw)
In-Reply-To: <1062712012.22550.72.camel@dhcp23.swansea.linux.org.uk>
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.
--
marko
next prev parent reply other threads:[~2003-09-05 14:55 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-04 19:07 [OOPS] 2.4.22 / HPT372N Marko Kreen
2003-09-04 21:46 ` Alan Cox
2003-09-05 14:54 ` Marko Kreen [this message]
2003-09-05 21:51 ` Alan Cox
-- strict thread matches above, loose matches on Subject: below --
2003-09-09 12:06 Ronny Buchmann
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
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=20030905145452.GA24201@l-t.ee \
--to=marko@l-t.ee \
--cc=alan@lxorguk.ukuu.org.uk \
--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