Jan 9 21:04:10 juliette kernel: i2c-proc.o version 2.8.1 (20031005) Jan 9 21:04:10 juliette kernel: i2c-viapro.o version 2.8.1 (20031005) Jan 9 21:04:10 juliette kernel: i2c-core.o: adapter registered as adapter 0. Jan 9 21:04:10 juliette kernel: i2c-isa.o version 2.8.1 (20031005) Jan 9 21:04:10 juliette kernel: i2c-core.o: adapter registered as adapter 1. Jan 9 21:04:10 juliette kernel: adm1021.o version 2.8.1 (20031005) Jan 9 21:04:10 juliette kernel: i2c-core.o: driver registered. Jan 9 21:04:10 juliette kernel: w83781d.o version 2.8.1 (20031005) Jan 9 21:04:10 juliette kernel: i2c-core.o: driver registered. Jan 9 21:04:10 juliette kernel: printing eip: Jan 9 21:04:10 juliette kernel: 00000001 Jan 9 21:04:10 juliette kernel: Oops: 0000 Jan 9 21:04:10 juliette kernel: CPU: 0 Jan 9 21:04:10 juliette kernel: EIP: 0010:[<00000001>] Tainted: P Jan 9 21:04:10 juliette kernel: EFLAGS: 00010286 Jan 9 21:04:10 juliette kernel: eax: e1249bc0 ebx: 00000000 ecx: e11ba404 edx: de351f7c Jan 9 21:04:10 juliette kernel: esi: e11ba404 edi: e236b060 ebp: e2367000 esp: cf853eec Jan 9 21:04:10 juliette kernel: ds: 0018 es: 0018 ss: 0018 Jan 9 21:04:10 juliette kernel: Process modprobe (pid: 31360, stackpage=cf853000) Jan 9 21:04:10 juliette kernel: Stack: e11b7493 e1249bc0 e236b060 dbdbba40 00000002 00000002 e236a56b e236b060 Jan 9 21:04:10 juliette kernel: e236a783 e236a77a c01d4a6d e2367060 080e4a00 00005d14 e236aa50 080e8322 Jan 9 21:04:10 juliette kernel: 00003982 00000060 00000060 00000007 00000246 ffffffea cce76000 cc1f0000 Jan 9 21:04:10 juliette kernel: Call Trace: [<e11b7493>] [<e1249bc0>] [<e236b060>] [<e236a56b>] [<e236b060>] Jan 9 21:04:10 juliette kernel: [<e236a783>] [<e236a77a>] [<c01d4a6d>] [<e2367060>] [<e236aa50>] [<e2367060>] Jan 9 21:04:10 juliette kernel: [<c01be553>] Jan 9 21:04:10 juliette kernel: Jan 9 21:04:10 juliette kernel: Code: Bad EIP value. Jan 9 21:05:29 juliette kernel: <1>ABORTED IN=ppp0 OUT= MAC= SRC=64.124.204.45 DST=212.202.40.59 LEN=40 TOS=0x00 PREC=0x00 TTL=52 ID=0 DF PROTO=TCP SPT=80 DPT=3321 SEQ=1506130633 ACK=0 WINDOW=0 RES=0x00 RST URGP=0 Jan 9 21:20:47 juliette kernel: printing eip: Jan 9 21:20:47 juliette kernel: e11b7a99 Jan 9 21:20:47 juliette kernel: Oops: 0000 Jan 9 21:20:47 juliette kernel: CPU: 0 Jan 9 21:20:47 juliette kernel: EIP: 0010:[<e11b7a99>] Tainted: P Jan 9 21:20:47 juliette kernel: EFLAGS: 00010206 Jan 9 21:20:47 juliette kernel: eax: 00040002 ebx: 00000006 ecx: e11b9c8e edx: e11b9c8d Jan 9 21:20:47 juliette kernel: esi: 00000000 edi: d614a000 ebp: 00000c00 esp: d51a5f38 Jan 9 21:20:47 juliette kernel: ds: 0018 es: 0018 ss: 0018 Jan 9 21:20:47 julieJan 9 21:20:47 juliette kernel: Stack: d614a000 e11b9c87 00000000 00000000 d51a5f80 00000c00 d614a000 00001000 Jan 9 21:20:47 juliette kernel: c0219b53 d614a000 d51a5f80 00000000 00000c00 d51a5f7c 00000000 dbdbd440 Jan 9 21:20:47 juliette kernel: 00000000 00000000 00000000 00000000 d42f8f40 ffffffea 00001000 c01f5293 Jan 9 21:20:47 juliette kernel: Call Trace: [<e11b9c87>] [<c0219b53>] [<c01f5293>] [<c01be553>] Jan 9 21:20:47 juliette kernel: Jan 9 21:20:47 juliette kernel: Code: 8b 50 28 85 d2 74 53 8b 40 24 85 c0 74 42 c7 44 24 04 8f 9c Jan 9 21:20:48 juliette kernel: <1>Unable to handle kernel paging request at virtual address 0004002a Jan 9 21:20:48 juliette kernel: printing eip: Jan 9 21:20:48 juliette kernel: e11b7a99tte kernel: Process ksensors (pid: 621, stackpage=d51a5000) lsmod says: Module Size Used by Tainted: P w83781d 23924 1 (initializing) Reproducible: Always Steps to Reproduce: 1. start lm-sensors 2. start ksensors Actual Results: ksensors crashes since it cannot access w83781d module Portage 2.0.49-r20 (default-x86-1.4, gcc-3.3.2, glibc-2.3.3_pre20031222-r0, 2.4. 23-grsec-2.0-rc4) ================================================================= System uname: 2.4.23-grsec-2.0-rc4 i686 AMD Athlon(tm) XP 1800+ Gentoo Base System version 1.4.3.12 ACCEPT_KEYWORDS="x86 ~x86" AUTOCLEAN="yes" CFLAGS="-mcpu=athlon-xp -O3 -pipe -fstack-protector" 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/dvipdfm/config/ /usr/share/texmf/dvips/config/ /usr/share/texmf/tex/generic/config/ /usr/share/texmf/tex/platex/config/ /usr/share/texmf/xdvi/ /var/qmail/control" CONFIG_PROTECT_MASK="/etc/gconf /etc/env.d" CXXFLAGS="-mcpu=athlon-xp -O3 -pipe -fstack-protector" DISTDIR="/usr/portage/distfiles" FEATURES="autoaddcvs ccache fixpackages sandbox" GENTOO_MIRRORS="http://gentoo.oregonstate.edu http://distro.ibiblio. org/pub/Linux/distributions/gentoo" MAKEOPTS="-j2" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="" SYNC="rsync://rsync.namerica.gentoo.org/gentoo-portage" USE="X aalib aavm acl acpi acpi4linux alsa apache2 apm arts artswrappersuid avi berkdb cdr cjk crypt cups dga doc dvd encode esd foomaticdb gdbm gif gnome gphoto2 gpm gps gtk gtk2 guile hbci imap imlib ipv6 java javascript jpeg kde lcms ldap libg++ libwww mad maildir mbox md5sum mikmod motif mozilla mpeg mule mysql nas ncurses nls oci8 odbc oggvorbis opengl oss pam pda pdflib perl pic plotutils png ppds python qt quicktime readline ruby sasl scanner sdl slang spell sse ssl svga tcltk tcpd tetex tiff truetype trusted type1 usb v4l videos wmf x86 xml xml2 xmms xosd xv xvid zlib"
Can you please emerge ksymoops, and do: ``ksymoops < file_with_OOPS > file_out'' on the kernel which is causing this and paste file_out into this bug? file_with_OOPS should contain the stack data from your initial post.
Created attachment 23535 [details] ksymoops output ksymoops output
Ok, I did as you said (see attachment above). Even though I saw ksymoops output for the first time, it looked rather dubious to me (lots of warnings). Therefore, I decided to reboot the box in order to reproduce the error and have a clean syslog to begin with. Funny thing: This error is NOT reproducible. I've rebooted a couple of times now, and everytime lm-sensors started (and worked) as advertised. Side note: Tonight the automated update has updated a couple of packages and init scripts on this box. So, while this mysteriously fixed my problem, I now caught bug #37375, but that's a different story... If no one else encountered my problem, I apologize for wasting your time. The good thing is, however, that next time I'll report a kernel hickup, I know now right away how to use ksymoops to make it more useful. Thank you for helping me out!
Those warnings may be the reason you got the OOPS - the symbols don't match for some reason in the running i2c-core and the one you have on disk - which may explain why it OOPSes as it can't manage to cooperate. Not sure how it randomly fixed itself, though. I'm resolving this as INVALID, if you get this again, please reopen this bug.