weird kernel: EIP message. dunno if good or bad.. could you please have a look?

nass · 04-20-2007, 06:59 AM

i just recently bought a new pc and installed slack v11 on it.
of interest is that its a core 2 duo, with p965 north bridge and ICH8R southbridge.
i've connected on ICH8R, 4 drives .
a WDraptor sata1 40GB (for the OS) and 3x WDcaviar320GB but data.
i plan to make these 3HDs a raid5 soon.
i managed to find both the raptor HD (i had only connected that one during installation) and the dvd-rom (with the slack CDs) using kernel image 'test26.s' that came with the CDs.
notice that i enabled 'AHCI' option from BIOS and included the necessary driver in the kernel..
so far so good..
then i prepared a new kernel image based on v2.6.20.7, loading raid concerned modules , lan and audio (things that did not work with the test26.s image).

so now i have connected the other 3 drives as well.. i fdisked them and formated them.
and today ive been downloading some necessary packages from over the internet.

once i dled openoffice using wget (saved it on the raptor), i got the following messages
(its possible the downloading had nothing to do with the message, but im just mentioning it)

Quote:

Message from syslogd@Stargaze at Fri Apr 20 14:32:55 2007 ...
Stargaze kernel: Oops: 0000 [#1]

Message from syslogd@Stargaze at Fri Apr 20 14:32:55 2007 ...
Stargaze kernel: SMP

Message from syslogd@Stargaze at Fri Apr 20 14:32:55 2007 ...
Stargaze kernel: CPU: 0

Message from syslogd@Stargaze at Fri Apr 20 14:32:55 2007 ...
Stargaze kernel: EIP: 0060:[<c01b3649>] Tainted: P VLI

Message from syslogd@Stargaze at Fri Apr 20 14:32:55 2007 ...
Stargaze kernel: EFLAGS: 00010246 (2.6.20.7C2D6400,2x1GB_800MHz,P965,ICH8R,NV7100_128MB,Marv8056 #2)

Message from syslogd@Stargaze at Fri Apr 20 14:32:55 2007 ...
Stargaze kernel: EIP is at reiserfs_write_full_page+0x1b9/0x4d0

Message from syslogd@Stargaze at Fri Apr 20 14:32:55 2007 ...
Stargaze kernel: eax: 00000000 ebx: 00007d4e ecx: fff9f7da edx: 00000000

Message from syslogd@Stargaze at Fri Apr 20 14:32:55 2007 ...
Stargaze kernel: esi: 00000000 edi: 00000000 ebp: 000059c8 esp: c21ebd88

Message from syslogd@Stargaze at Fri Apr 20 14:32:55 2007 ...
Stargaze kernel: ds: 007b es: 007b ss: 0068

Message from syslogd@Stargaze at Fri Apr 20 14:32:55 2007 ...
Stargaze kernel: Process pdflush (pid: 276, ti=c21ea000 task=c220b030 task.ti=c21ea000)

Message from syslogd@Stargaze at Fri Apr 20 14:32:55 2007 ...
Stargaze kernel: Stack: 07d4e7e5 00000000 ef9d95f0 00000001 f7a21e00 00000000 00000000 ef9da390

Message from syslogd@Stargaze at Fri Apr 20 14:32:55 2007 ...
Stargaze kernel: 00000000 f4a92248 c21ebf58 c1e20c40 00000000 c21ebe38 f4a922ec c21ebe2c

Message from syslogd@Stargaze at Fri Apr 20 14:32:55 2007 ...
Stargaze kernel: 00000000 0000000e 00000000 c21ebe2c c21ebe30 00000296 c1e20c40 c21ebf58

Message from syslogd@Stargaze at Fri Apr 20 14:32:55 2007 ...
Stargaze kernel: Call Trace:

Message from syslogd@Stargaze at Fri Apr 20 14:32:55 2007 ...
Stargaze kernel: [<c0147ca7>] generic_writepages+0x217/0x360

Message from syslogd@Stargaze at Fri Apr 20 14:32:55 2007 ...
Stargaze kernel: [<c0182d48>] __wait_on_buffer+0x28/0x30

Message from syslogd@Stargaze at Fri Apr 20 14:32:55 2007 ...
Stargaze kernel: [<c01b3970>] reiserfs_writepage+0x0/0x40

Message from syslogd@Stargaze at Fri Apr 20 14:32:55 2007 ...
Stargaze kernel: [<c0147e39>] do_writepages+0x49/0x50

Message from syslogd@Stargaze at Fri Apr 20 14:32:55 2007 ...
Stargaze kernel: [<c017f39f>] __sync_single_inode+0x4f/0x1f0

Message from syslogd@Stargaze at Fri Apr 20 14:32:55 2007 ...
Stargaze kernel: [<c017f58f>] __writeback_single_inode+0x4f/0x1e0

Message from syslogd@Stargaze at Fri Apr 20 14:32:55 2007 ...
Stargaze kernel: [<c0117b19>] load_balance_newidle+0x69/0x170

Message from syslogd@Stargaze at Fri Apr 20 14:32:55 2007 ...
Stargaze kernel: [<c017f88d>] sync_sb_inodes+0x16d/0x290

Message from syslogd@Stargaze at Fri Apr 20 14:32:55 2007 ...
Stargaze kernel: [<c017fa4f>] writeback_inodes+0x9f/0xb0

Message from syslogd@Stargaze at Fri Apr 20 14:32:55 2007 ...
Stargaze kernel: [<c01478e5>] wb_kupdate+0x85/0x100

Message from syslogd@Stargaze at Fri Apr 20 14:32:55 2007 ...
Stargaze kernel: [<c01484c0>] pdflush+0x0/0x30

Message from syslogd@Stargaze at Fri Apr 20 14:32:55 2007 ...
Stargaze kernel: [<c01483fe>] __pdflush+0xce/0x190

Message from syslogd@Stargaze at Fri Apr 20 14:32:55 2007 ...
Stargaze kernel: [<c01484e8>] pdflush+0x28/0x30

Message from syslogd@Stargaze at Fri Apr 20 14:32:55 2007 ...
Stargaze kernel: [<c0147860>] wb_kupdate+0x0/0x100

Message from syslogd@Stargaze at Fri Apr 20 14:32:55 2007 ...
Stargaze kernel: [<c01484c0>] pdflush+0x0/0x30

Message from syslogd@Stargaze at Fri Apr 20 14:32:55 2007 ...
Stargaze kernel: [<c0131ef4>] kthread+0xa4/0xe0

Message from syslogd@Stargaze at Fri Apr 20 14:32:55 2007 ...
Stargaze kernel: [<c0131e50>] kthread+0x0/0xe0

Message from syslogd@Stargaze at Fri Apr 20 14:32:55 2007 ...
Stargaze kernel: [<c0103a93>] kernel_thread_helper+0x7/0x14

Message from syslogd@Stargaze at Fri Apr 20 14:32:55 2007 ...
Stargaze kernel: =======================

Message from syslogd@Stargaze at Fri Apr 20 14:32:55 2007 ...
Stargaze kernel: Code: f2 eb 1a 77 04 39 dd 76 1a f0 0f ba 37 01 f0 0f ba 2f 00 8b 7f 04 45 3b 7c 24 1c 74 4f 31 d2 39 f2 73 e0 8b 54 24 14 85 d2 75 06 <8b> 07 a8 02 74 e2 8b 07 a8 20 74 12 8b 07 a8 20 74 d6 8b 57 10

Message from syslogd@Stargaze at Fri Apr 20 14:32:55 2007 ...
Stargaze kernel: EIP: [<c01b3649>] reiserfs_write_full_page+0x1b9/0x4d0 SS:ESP 0068:c21ebd88

they look kind of scary but i don't know how to interpret them... anyone can please fill me in?
the system is still working... fine... i guess.. no prblem with opening files or saving new ones..

thank you in advance for your help
nass

syg00 · 04-21-2007, 12:17 AM

There is no such thing as a "good" oops - unless you're into (kernel) debugging.

I don't use reiser, but I'd be looking to do a filesystem check on that *real* soon. Followed by a full backup.

theoffset · 04-22-2007, 10:46 AM

You can also read <kernel-source-path>/Documentation/oops-tracing.txt (most of it, even in 2.6 kernel source, is for 2.4 and is made for developers) to get some insight on what it is and what it means.

Also, if you're willing to help (and maybe try to reproduce it) you can read REPORTING-BUGS in the kernel source directory and send a report to either viro (in charge of the filesystems in general) or to the reiserfs people. You can find their e-mail addresses in the MAINTAINERS file.