From: Bartlomiej Zolnierkiewicz <B.Zolnierkiewicz@elka.pw.edu.pl>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Jindrich Makovicka <makovick@kmlinux.fjfi.cvut.cz>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] HPT374 kernel panic - regression in 2.6.8
Date: Tue, 17 Aug 2004 00:30:45 +0200 [thread overview]
Message-ID: <200408170030.45553.bzolnier@elka.pw.edu.pl> (raw)
In-Reply-To: <1092496584.27144.3.camel@localhost.localdomain>
On Saturday 14 August 2004 17:16, Alan Cox wrote:
> On Sad, 2004-08-14 at 12:14, Jindrich Makovicka wrote:
> > Hello,
> >
> > HighPoint 374 driver in 2.6.8 can cause kernel panic on boot with
> > non-33MHz timings because some lines from an older version have been
> > included in the source again. After removing the check, HPT374 works
> > just fine using internal PLL.
>
> The HPT374 only supports 33Mhz timings. If you are overclocking it then
> its probably going to mostly work. The lines added are not "from an
> older source file" but form a port forwards of long missing and
> important fixes from 2.4 that have been there for a long long time.
2.4 driver also misses some fixes...
> So the first question is why does your late series HPT37x think its
> running at > 33Mhz ? Are you overclocking it ?
http://linus.bkbits.net:8080/linux-2.5/cset@40586b50zsHhQgPLGTlje7g_f5wGTw?nav=index.html|
src/|src/drivers|src/drivers/ide|src/drivers/ide/pci|
related/drivers/ide/pci/hpt366.c
please read bugzilla bugs mentioned in the changelong and fix this
next prev parent reply other threads:[~2004-08-16 22:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-14 11:14 Jindrich Makovicka
2004-08-14 15:16 ` Alan Cox
2004-08-16 22:30 ` Bartlomiej Zolnierkiewicz [this message]
2004-08-16 22:00 ` Alan Cox
2004-08-17 12:25 ` Marcelo Tosatti
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=200408170030.45553.bzolnier@elka.pw.edu.pl \
--to=b.zolnierkiewicz@elka.pw.edu.pl \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=makovick@kmlinux.fjfi.cvut.cz \
/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®