Bug 43912

Summary:	kernel oops when doing an emerge
Product:	Gentoo Linux	Reporter:	Steve <spatz>
Component:	[OLD] Core system	Assignee:	x86-kernel (DEPRECATED) <x86-kernel>
Status:	RESOLVED CANTFIX
Severity:	critical	CC:	steel300
Priority:	High
Version:	unspecified
Hardware:	x86
OS:	Linux
Whiteboard:
Package list:		Runtime testing required:	---
Attachments:	My current kernel Config everything.log critical.log

Description Steve 2004-03-06 13:30:58 UTC

When I attempt to do an emerge ( any app that needs updated/installed ) my kernel oops.  Either the box freezes and nothing but a reset helps, or I get a OOPS to the console.  I have attempted to gather info to run ksymoops, but the last 10 times the OOPS info scrolls off the screen.  I have the Magic Sysrq enabled but using it has no effect.  I then have to do a hard reboot.


Reproducible: Always
Steps to Reproduce:
1. Dial Out with wvdial
2. Run pmfirewall ( ipchains firewall script )
3. Do an emerge.
4. Within 10 minutes the lockup or OOPS occurs.

Actual Results:  
The kernel crashes, not recoverable.

Expected Results:  
Should not OOPS.  

Gentoo Base System version 1.4.3.13
Portage 2.0.50-r1 (default-x86-1.4, gcc-3.3.2, glibc-2.2.5-r2,2.3.2-r9, 2.4.23-ck1)
=================================================================
System uname: 2.4.23-ck1 i686 Pentium III (Coppermine)
distcc 2.11.1 i686-pc-linux-gnu (protocols 1 and 2) (default port 3632) [enabled]
Autoconf: sys-devel/autoconf-2.58-r1
Automake: sys-devel/automake-1.7.7
ACCEPT_KEYWORDS="x86"
AUTOCLEAN="yes"
CFLAGS="-march=pentium3 -O3 -pipe -frerun-cse-after-loop -msse -mmmx
-fomit-frame-pointer"
CHOST="i686-pc-linux-gnu"
COMPILER="gcc3"
CONFIG_PROTECT="/etc /usr/X11R6/lib/X11/xkb /usr/kde/2/share/config
/usr/kde/3.1/share/config /usr/kde/3/share/config /usr/share/config
/usr/share/texmf/tex/generic/config/ /usr/share/texmf/tex/platex/config/
/var/qmail/control"
CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d"
CXXFLAGS="-march=pentium3 -O3 -pipe -frerun-cse-after-loop -msse -mmmx
-fomit-frame-pointer"
DISTDIR="/usr/portage/distfiles"
FEATURES="autoaddcvs ccache distcc sandbox"
GENTOO_MIRRORS="http://10.0.0.2 ftp://ftp.ussg.iu.edu/pub/linux/gentoo
http://mirrors.tds.net/gentoo ftp://ftp.gtlib.cc.gatech.edu/pub/gentoo
ftp://mirrors.tds.net/gentoo"
MAKEOPTS="-j6"
PKGDIR="/usr/portage/packages"
PORTAGE_TMPDIR="/var/tmp"
PORTDIR="/usr/portage"
PORTDIR_OVERLAY="/usr/local/portage"
SYNC="rsync://rsync.namerica.gentoo.org/gentoo-portage"
USE="alsa apache2 apm arts avi berkdb cdr crypt cups encode esd foomaticdb gdbm
gif gpm gtk2 imlib jpeg kde libg++ libwww mad mikmod motif mozilla mpeg mysql
ncurses nls odbc oggvorbis opengl oss pam pdflib perl png postgres python qt
quicktime readline scanner sdl slang snmp spell sse ssl svga tcltk tcpd tetex
truetype usb x86 xml2 xmms xv zlib"

Comment 1 Steve 2004-03-06 13:33:15 UTC

Created attachment 26959 [details]
My current kernel Config

Comment 2 Tim Yamin (RETIRED) gentoo-dev

2004-03-10 10:13:25 UTC

OOPSes should be logged to at least dmesg, as well as your system logs. Try to run ksymoops on those. We can't do that much, if anything, without any traces.

Comment 3 Steve 2004-03-10 17:53:15 UTC

I am a newbie when it coems to the kernel and system logs but after tonite's latest oops I rebooted and looked in my dmesg output as well as everything.log and critical.log.  I have attached what they contain, no trace info though.   I am using metalog.  Any tips on using a serial console would be a great help.

Comment 4 Steve 2004-03-10 17:56:30 UTC

Created attachment 27183 [details]
everything.log

Comment 5 Steve 2004-03-10 18:00:51 UTC

Created attachment 27184 [details]
critical.log

Comment 6 Tim Yamin (RETIRED) gentoo-dev

2004-03-11 09:22:24 UTC

Ah; I thought it was OOPSing but not freezing. Since dmesg resets when you reboot and metalog commits data at intervals; you won't find much - if anything.

For a serial console:

1) Add ``Support for console on serial port'' to the kernel configuration in ``Character devices''.
2) Boot; adding ``console=ttyS%X console=tty0'' to the kernel boot parameters - replace %X with 0 for COM1; with 1 for COM2; etc.
3) That should dump data [ and OOPSes ] to both the screen and serial console.
4) If you manage to grab an OOPS but no backtrace; run ``ksymoops < fileContainingOOPS'' on the buggy kernel to generate a backtrace. You might need to merge ksymoops.

If that doesn't work; the first couple paragraphs of /usr/src/linux/Documentation/serial-console.txt might be of help.

Thanks!

Comment 7 Jason Cox (RETIRED) gentoo-dev

2004-04-16 17:48:56 UTC

This bug has passed its prime.