Return-Path: <linux-kernel-owner@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
	id <S280606AbRKODsX>; Wed, 14 Nov 2001 22:48:23 -0500
Received: (majordomo@vger.kernel.org) by vger.kernel.org
	id <S280714AbRKODsN>; Wed, 14 Nov 2001 22:48:13 -0500
Received: from news.heim1.tu-clausthal.de ([139.174.234.200]:52843 "EHLO
	neuemuenze.heim1.tu-clausthal.de") by vger.kernel.org with ESMTP
	id <S280606AbRKODry>; Wed, 14 Nov 2001 22:47:54 -0500
Date: Thu, 15 Nov 2001 04:28:43 +0100
From: Sven.Riedel@tu-clausthal.de
To: nakai <nakai@neo.shinko.co.jp>
Cc: kernel <linux-kernel@vger.kernel.org>
Subject: Re: 2.4.14 Oops during boot (KT133A Problem?)
Message-ID: <20011115042843.A383@moog.heim1.tu-clausthal.de>
In-Reply-To: <20011115021142.A12923@moog.heim1.tu-clausthal.de> <3BF32B36.8B1375D0@neo.shinko.co.jp>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <3BF32B36.8B1375D0@neo.shinko.co.jp>
User-Agent: Mutt/1.3.23i
Sender: linux-kernel-owner@vger.kernel.org
X-Mailing-List: linux-kernel@vger.kernel.org

On Thu, Nov 15, 2001 at 11:40:54AM +0900, nakai 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.

I just tried it with K6 and plain old 386 CPU settings. In both cases
the same oops happened at the same place (+- a few bytes due to the
different opcodes generated by the compiler). 
If more machine info is needed, I'd be glad to provide it.

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 
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/