Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 73967 - Random kernel oopses on 2.6.9-gentoo-r4no on epia motherboard
Summary: Random kernel oopses on 2.6.9-gentoo-r4no on epia motherboard
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: [OLD] Core system (show other bugs)
Hardware: All Linux
: High critical (vote)
Assignee: Gentoo Kernel Bug Wranglers and Kernel Maintainers
Depends on:
Reported: 2004-12-09 17:31 UTC by Vadim
Modified: 2004-12-25 04:47 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---

Kernel oops (CRASH,2.32 KB, text/plain)
2004-12-09 17:32 UTC, Vadim
Another kernel oops (CRASH2,2.16 KB, text/plain)
2004-12-09 17:33 UTC, Vadim
Kernel config (config,33.18 KB, text/plain)
2004-12-09 17:34 UTC, Vadim

Note You need to log in before you can comment on or make changes to this bug.
Description Vadim 2004-12-09 17:31:01 UTC
This happens consistently once every few days. However, I haven't found yet a way of reproducing it. It works fine for some time, then crashes. The crash seems to be related to load, since it seems that I can make it oops quite easily by emerging stuff, but this still can take more than an hour.

It doesn't seem to be overheating, at least the heatsink is quite cold to the touch. It doesn't look like a memory problem either, memtest86 didn't find anything.

The only thing I think it might be related to is hardware. I have went through several kernel versions on this machine, and this one seems to be more stable than the previous ones. I have no oopses at all on my other gentoo computers.

Reproducible: Sometimes
Steps to Reproduce:
1. Have the system running.
2. Under low load it seems to oops in 2 or 3 days, while compiling it can happen within an hour or two.
Actual Results:  
Kernel oops 

Expected Results:  
Continue working normally 

Portage 2.0.51-r3 (default-linux/x86/2004.0, gcc-3.3.4, 
glibc-, 2.6.9-gentoo-r4no i686) 
System uname: 2.6.9-gentoo-r4no i686 VIA Nehemiah 
Gentoo Base System version 1.4.16 
ccache version 2.3 [enabled] 
Autoconf: sys-devel/autoconf-2.59-r5 
Automake: sys-devel/automake-1.8.5-r1 
Binutils: sys-devel/binutils- 
Headers:  sys-kernel/linux-headers-2.4.21-r1 
Libtools: sys-devel/libtool-1.5.2-r7 
CFLAGS="-Os  -march=i686 -msse -mmmx -mfpmath=sse -pipe -fomit-frame-pointer 
CONFIG_PROTECT="/etc /usr/kde/2/share/config /usr/kde/3/share/config /usr/share/config /var/qmail/control" 
CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d" 
CXXFLAGS="-Os  -march=i686 -msse -mmmx -mfpmath=sse -pipe -fomit-frame-pointer 
FEATURES="autoaddcvs autoconfig ccache distlocks fixpackages loadpolicy 
sandbox sfperms userpriv usersandbox" 
USE="aalib apache2 apm avi berkdb bitmap-fonts crypt cups curl encode f77 
foomaticdb fortran gdbm gif gpm gtk2 imap imlib innodb jpeg libg++ libwww mad 
maildir mikmod mmx motif mpeg mysql ncurses nls oggvorbis pam pdflib perl png 
postgres pythonquicktime readline sdl slang spell sse ssl tcpd tiff truetype 
x86 xml2 xmms zlib"
Comment 1 Vadim 2004-12-09 17:32:39 UTC
Created attachment 45654 [details]
Kernel oops
Comment 2 Vadim 2004-12-09 17:33:41 UTC
Created attachment 45655 [details]
Another kernel oops

Seems to be the same problem as above, but with slightly different data.
Attaching this one too in case it helps.
Comment 3 Vadim 2004-12-09 17:34:48 UTC
Created attachment 45656 [details]
Kernel config
Comment 4 Daniel Drake (RETIRED) gentoo-dev 2004-12-15 02:50:26 UTC
Can you please test development-sources-2.6.10_rc3 ?
Comment 5 Vadim 2004-12-15 05:23:57 UTC
Okay, will do.

Currently I'm running vanilla 2.6.9 with the same configuration.
It's been up for 5 days, and had another oops in elf_map. I suppose
I should submit that one instead to lkml, since it's the vanilla version.

The oops I reported didn't happen yet though. Will try 2.6.10_rc3 later
Comment 6 Daniel Drake (RETIRED) gentoo-dev 2004-12-22 16:06:55 UTC
Please reopen with test results.
Comment 7 Vadim 2004-12-25 04:47:07 UTC
Okay, it's been running here for a while, without any
oopses so far!

I still have no idea of how to reproduce it for certain,
but the load was quite high, so I think it should have
crashed already.