2.4.14 Oops during boot (KT133A Problem?)

2.4.14 Oops during boot (KT133A Problem?)

Post by naka » Fri, 16 Nov 2001 11:50:10

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 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  -=-=-=-=

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in

More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

1. 2.4.14 Oops during boot (KT133A Problem?)

Well, the problem got solved (although not in a way I'd consider
satisfactory). After my machine started random segfaulting the day
before yesterday, I memcheck86'ed it again (the last check is a mere two
months ago), and lo - all three RAM chips were broken. Unfortunately, I
discovered this, after this broken RAM caused my /usr partition to go
fubar, resulting in me spending yesterday with a nice little reinstall.
After the reinstall, 2.4.14 booted fine off the harddisk. No more
As to the cause of the problem: I think I can rule out the possibility
of getting a bad kernel compiled due to the bad ram, as I booted once
well below the problem zones with mem=32m and recompiled a kernel with
that and tried to boot - same symptoms.
Maybe lilo was broken or didn't like the MBR it was written to, or
something along those lines.
Thanks to all who tried to help me!


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

More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

2. Newbie gnome upgrade questions

3. Unwanted Swapping in 2.4.14-pre8, no swapping in 2.4.14-pre6aa1

4. SuSE: Printer Margins

5. OOPS on boot in 2.4.13-ac5 & 2.4.14-pre6

6. LInux + ST15230WC = ARGH!

7. Memory accounting problem in 2.4.13, 2.4.14pre, and possibly 2.4.14

8. Capturing keystokes in Korn Shell script

9. Oops in kmem_cache_free with 2.4.14

10. 2.4.15 oops (2.4.14 freeze continuation)

11. Oops on 2.4.14-pre3

12. 2.4.14-pre4 tainted + preempt oops...

13. oops in 2.4.14-xfs (xfs release 1.0.2)