From: Sven.Riedel@tu-clausthal.de
To: bill davidsen <davidsen@tmr.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.4.14 Oops during boot (KT133A Problem?)
Date: Mon, 19 Nov 2001 23:48:49 +0100 [thread overview]
Message-ID: <20011119234849.A320@moog.heim1.tu-clausthal.de> (raw)
In-Reply-To: <20011115021142.A12923@moog.heim1.tu-clausthal.de> <200111191611.fAJGBKQ30686@deathstar.prodigy.com>
In-Reply-To: <200111191611.fAJGBKQ30686@deathstar.prodigy.com>
On Mon, Nov 19, 2001 at 11:11:20AM -0500, bill davidsen wrote:
> In article <3BF32B36.8B1375D0@neo.shinko.co.jp> nakai@neo.shinko.co.jp wrote:
> >I think you'd be better compile kernel for K6, not for K7. There is
> >something wrong with KT133 chip set and Athlon/Duron.
>
> There is a patch for this chipset around, which AFAIK was never put in
> the kernel because the exact function of the patch was not known WRT the
> chipset internals.
I guess you mean Kurt Garloffs patch that turned certain features on and
off, since the bit 55 disable patch is in 2.4.14. Unfortunately, I still
get the Oops after applying this patch (and the quirk-fixes were
executed before the oops).
Regs,
Sven
--
Sven Riedel sr@gimp.org
Osteroeder Str. 6 / App. 13 sven.riedel@tu-clausthal.de
38678 Clausthal "Call me bored, but don't call me boring."
- Larry Wall
next prev parent reply other threads:[~2001-11-19 22:50 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-15 1:11 Sven.Riedel
2001-11-15 2:40 ` nakai
2001-11-15 3:28 ` Sven.Riedel
2001-11-15 8:03 ` nakai
2001-11-15 10:22 ` Sven.Riedel
2001-11-15 23:59 ` nakai
[not found] ` <20011116202230.A890@moog.heim1.tu-clausthal.de>
2001-11-19 23:31 ` nakai
2001-11-19 16:11 ` bill davidsen
2001-11-19 22:48 ` Sven.Riedel [this message]
2001-11-24 17:54 ` Sven.Riedel
2001-11-26 0:40 ` nakai
2001-11-22 15:47 Sven.Riedel
2001-11-28 10:50 PVotruba
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=20011119234849.A320@moog.heim1.tu-clausthal.de \
--to=sven.riedel@tu-clausthal.de \
--cc=davidsen@tmr.com \
--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
all inboxes | Powered by JetHome®