mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: nakai <nakai@neo.shinko.co.jp>
To: kernel <linux-kernel@vger.kernel.org>
Cc: Sven.Riedel@tu-clausthal.de
Subject: Re: 2.4.14 Oops during boot (KT133A Problem?)
Date: Thu, 15 Nov 2001 11:40:54 +0900	[thread overview]
Message-ID: <3BF32B36.8B1375D0@neo.shinko.co.jp> (raw)
In-Reply-To: <20011115021142.A12923@moog.heim1.tu-clausthal.de>

I think you'd be better compile kernel for K6, not for K7.  There is
something wrong with KT133 chip set and Athlon/Duron.

Sven.Riedel@tu-clausthal.de wrote:
> I get the following kernel oops when booting 2.4.14 vanilla on an Athlon
> 1200, KT133A Chipset Motherboard, 768MB RAM. Kernel has been compiled
> for Athlon CPUs, non-SMP. The next thing the kernel would have done
> after the oops would have been to start kswapd.
> Sidenote: booting the exact same kernel from floppy (debian rescue with
> kernels exchanged and booting with 'linux root=/dev/hda6') gives me a rather
> unstable system for a short while (uptime usually < 6 hours before oopsing).
> 
> Linux NET 4.0 for Linux 2.4
> Based upon Swansea University Computer Society Net 3.039
> Unable to handle kernel NULL pointer dereference at virtual address
> 00000003 printing eip:
> c0112073
> *pde = 00000000
> Oops: 0000
> CPU:    0
> EIP:    0010:[<c0112073>]  Not tainted
> Using defaults from ksymoops -t elf32-i386 -a i386
> EFLAGS: 00010286
> eax: f7efe000   ebx: f7efe000     ecx: 00000000 edx: ffffffff
> esi: c1e1a5a0 edi: fffffff5     ebp: 00000700       esp: c1e1bf50
> ds: 0018        es: 0018       ss:0018
> Process swapper (pid: 1, stackpage=c1e1b000)

-- 
-=-=-=-=  SHINKO ELECTRIC INDUSTRIES CO., LTD.           =-=-=-=-
=-=-=-=-    Core Technology Research & Laboratory,       -=-=-=-=
-=-=-=-=      Infomation Technology Research Dept.       =-=-=-=-
=-=-=-=-  Name:Hisakazu Nakai          TEL:026-283-2866  -=-=-=-=
-=-=-=-=  Mail:nakai@neo.shinko.co.jp  FAX:026-283-2820  =-=-=-=-

  reply	other threads:[~2001-11-15  2:41 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 [this message]
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
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=3BF32B36.8B1375D0@neo.shinko.co.jp \
    --to=nakai@neo.shinko.co.jp \
    --cc=Sven.Riedel@tu-clausthal.de \
    --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®