Home | Docs | Forums | Lists | Bugs | Planet | Store | GMN | Get Gentoo!

Full Text Bug Listing

I use the vanilla-sources-2.6.21 and get a Kernel Panic if I try to ping an
other computer. I have a ethernet card with a sis900 chip and use this kernel
module. I have tried with the tickless option and without it but it panics in
both cases. The 2.6.20 vanilla-sources work for me.

Reproducible: Always

Steps to Reproduce:
1. Compile vanilla-source-2.6.21 with sis900 kernel module
2. Boot the system with it
3. Ping a different computer.

Portage 2.1.2.2 (default-linux/x86/2006.1/desktop, gcc-4.1.1, glibc-2.5-r0,
2.6.20.3 i686)
=================================================================
System uname: 2.6.20.3 i686 AMD Athlon(tm) XP 2000+
Gentoo Base System release 1.12.9
Timestamp of tree: Fri, 27 Apr 2007 15:30:01 +0000
distcc 2.18.3 i686-pc-linux-gnu (protocols 1 and 2) (default port 3632)
[disabled]
dev-java/java-config: 1.3.7, 2.0.31-r5
dev-lang/python:     2.4.3-r4
dev-python/pycrypto: 2.0.1-r5
sys-apps/sandbox:    1.2.17
sys-devel/autoconf:  2.13, 2.61
sys-devel/automake:  1.4_p6, 1.5, 1.6.3, 1.7.9-r1, 1.8.5-r3, 1.9.6-r2, 1.10
sys-devel/binutils:  2.16.1-r3
sys-devel/gcc-config: 1.3.15-r1
sys-devel/libtool:   1.5.22
virtual/os-headers:  2.6.17-r2
ACCEPT_KEYWORDS="x86"
AUTOCLEAN="yes"
CBUILD="i686-pc-linux-gnu"
CFLAGS="-O2 -march=athlon-xp -pipe -mfpmath=sse,387 -mmmx -msse
-fomit-frame-pointer"
CHOST="i686-pc-linux-gnu"
CONFIG_PROTECT="/etc /usr/kde/3.5/env /usr/kde/3.5/share/config
/usr/kde/3.5/shutdown /usr/share/X11/xkb /usr/share/config"
CONFIG_PROTECT_MASK="/etc/env.d /etc/env.d/java/ /etc/gconf
/etc/java-config/vms/ /etc/revdep-rebuild /etc/terminfo"
CXXFLAGS="-O2 -march=athlon-xp -pipe -mfpmath=sse,387 -mmmx -msse
-fomit-frame-pointer"
DISTDIR="/usr/portage/distfiles"
FEATURES="distlocks metadata-transfer sandbox sfperms strict"
GENTOO_MIRRORS="http://distfiles.gentoo.org
http://distro.ibiblio.org/pub/linux/distributions/gentoo"
MAKEOPTS="-j2"
PKGDIR="/usr/portage/packages"
PORTAGE_RSYNC_OPTS="--recursive --links --safe-links --perms --times --compress
--force --whole-file --delete --delete-after --stats --timeout=180
--exclude=/distfiles --exclude=/local --exclude=/packages
--filter=H_**/files/digest-*"
PORTAGE_TMPDIR="/var/tmp"
PORTDIR="/usr/portage"
SYNC="rsync://rsync.gentoo.org/gentoo-portage"
USE="X alsa arts berkdb bitmap-fonts bzip2 cairo cdr cli cracklib crypt cups
dbus dri dvd dvdr eds emboss encode esd fam firefox fortran gdbm gif gpm
gstreamer gtk hal iconv imap ipv6 isdnlog java jpeg kde ldap libg++ mad midi
mikmod mp3 mpeg ncurses nls nptl nptlonly odbc ogg opengl oss pam pcre pdf perl
png ppds pppd python qt3 qt4 quicktime readline reflection sdl session spell
spl sqlite ssl svg tcpd truetype truetype-fonts type1-fonts unicode usb vorbis
win32codecs x86 xml xorg xv zlib" ALSA_CARDS="ali5451 als4000 atiixp
atiixp-modem bt87x ca0106 cmipci emu10k1 emu10k1x ens1370 ens1371 es1938 es1968
fm801 hda-intel intel8x0 intel8x0m maestro3 trident usb-audio via82xx
via82xx-modem ymfpci" ALSA_PCM_PLUGINS="adpcm alaw asym copy dmix dshare dsnoop
empty extplug file hooks iec958 ioplug ladspa lfloat linear meter mulaw multi
null plug rate route share shm softvol" ELIBC="glibc" INPUT_DEVICES="keyboard
mouse evdev" KERNEL="linux" LCD_DEVICES="bayrad cfontz cfontz633 glk hd44780
lb216 lcdm001 mtxorb ncurses text" USERLAND="GNU" VIDEO_CARDS="apm ark ati
chips cirrus cyrix dummy fbdev glint i128 i740 i810 imstt mga neomagic nsc nv
rendition s3 s3virge savage siliconmotion sis sisusb tdfx tga trident tseng v4l
vesa vga via vmware voodoo"
Unset:  CTARGET, EMERGE_DEFAULT_OPTS, INSTALL_MASK, LANG, LC_ALL, LDFLAGS,
LINGUAS, PORTAGE_COMPRESS, PORTAGE_COMPRESS_FLAGS, PORTAGE_RSYNC_EXTRA_OPTS,
PORTDIR_OVERLAY

We need more information on this panic. I assume the panic hardlocks your
system so you're unable to save it to a log file using conventional means?

If so, you could use a serial console to capture the exact crash dump. If you
don't know what this is, or don't have the hardware, then perhaps you could
take a photo of the kernel panic and upload it here. Alternatively, you could
type out the human-readable parts of the panic message, excluding magic numbers
like [<a094021d>]

Created an attachment (id=117694) [details]
patch

Don't worry about capturing the panic. I think it's very likely to be identical
to another which was already reported upstream.

Please apply this patch, and see if it fixes it. If not, please continue to
capture the panic as detailed above.

The fix works for me. 
I have patched 2.6.21.1 build it and am working on it right now. Thank you very
much for the fast response to the problem. 

Sven

I've also just had this kernel panic too, I've reverted back to
2.6.20-hardened-r2 and all is ok :-)

Fixed in gentoo-sources-2.6.21-r1 (genpatches-2.6.21-2)

(In reply to comment #6)
> Fixed in gentoo-sources-2.6.21-r1 (genpatches-2.6.21-2)

Will this fix get into the hardened-sources ebuild too?