linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Todd R. Eigenschink" <todd@tekinteractive.com>
To: linux-kernel@vger.kernel.org
Subject: Re: kswapd OOPS under 2.4.19-pre8 (ext3, Reiserfs + (soft)raid0)
Date: Tue, 14 May 2002 10:09:10 -0500	[thread overview]
Message-ID: <15585.10390.825902.226132@rtfm.ofc.tekinteractive.com> (raw)
In-Reply-To: <15577.5431.625191.582701@rtfm.ofc.tekinteractive.com>

I never saw any reponses to my oops post...but now I've narrowed
things further, to a point that makes it seem more serious.

I thought the problem might be reiserfs, so I copied everything
elsewhere (which killed the machine a number of times) and reformatted
the two reiserfs partitions as ext3.  At the same time, I reduced the
raid partition from four disks to just two.

In particular, it had died at least once while it shouldn't have been
*touching* the raid partition--that partition only handles web stats,
and no web stats processing was running.  The oops was in an rcp that
was copying a file to the smaller, non-raid ext3 partition.

In the process of copying everyting back, the machine died several
more times.  OK, so that rules out reiserfs.  I reconfigured to mount
everything as ext2.  It lasted an awful lot longer (~ 36 hours), but
still died.  Here's the latest oops.  It looks a lot like the rest of
them.

I was considering going back to 2.2.20 when I thought it was the
combination of reiserfs + raid, since the machine ran 2.x flawlessly
for the longest time.  But now that (in my mind) ext3, reiser, and
raid have all been ruled out, what's left seems like a pretty serious
problem.  What else could/should I try to narrow the problem?

Dual P3/500, 2 GB RAM, Intel L440-GXC mainboard.


----------------------------------------------------------------------
ksymoops 2.4.5 on i686 2.4.19-pre8.  Options used
     -V (default)
     -k /proc/ksyms (default)
     -l /proc/modules (default)
     -o /lib/modules/2.4.19-pre8/ (default)
     -m /boot/System.map-2.4.19-pre8 (specified)

No modules in ksyms, skipping objects
Warning (read_lsmod): no symbols in lsmod, is /proc/modules a valid lsmod file?
Warning (compare_maps): ksyms_base symbol vmalloc_to_page_R__ver_vmalloc_to_page
 not found in System.map.  Ignoring ksyms_base entry
Oops: 0000
CPU:    0
EIP:    0010:[<c0115ba8>]    Not tainted
Using defaults from ksymoops -t elf32-i386 -a i386
EFLAGS: 00010087
eax: c2802db4   ebx: c2002db4   ecx: 00000000   edx: 00000003
esi: c2802db0   edi: c2802db0   ebp: cd2fdf48   esp: cd2fdf2c
ds: 0018   es: 0018   ss: 0018
Process ld-linux.so.2 (pid: 18110, stackpage=cd2fd000)
Stack: c1095000 c2802db0 00000000 c2802db4 00000000 00000282 00000003 00000000
       c01295fe c1095000 00001000 c012bef0 00000000 ce03f5c0 ffffffea 00001000
       e0855de8 00001000 00000000 00001000 00001000 00001000 00004000 00000000
Call Trace: [<c01295fe>] [<c012bef0>] [<c0136d57>] [<c010889b>]
Code: 8b 01 85 45 fc 74 69 31 c0 9c 5e fa f0 fe 0d 80 a9 30 c0 0f


>>EIP; c0115ba8 <__wake_up+40/d0>   <=====

>>eax; c2802db4 <END_OF_CODE+249a758/????>
>>ebx; c2002db4 <END_OF_CODE+1c9a758/????>
>>esi; c2802db0 <END_OF_CODE+249a754/????>
>>edi; c2802db0 <END_OF_CODE+249a754/????>
>>ebp; cd2fdf48 <END_OF_CODE+cf958ec/????>
>>esp; cd2fdf2c <END_OF_CODE+cf958d0/????>

Trace; c01295fe <unlock_page+62/68>
Trace; c012bef0 <generic_file_write+578/778>
Trace; c0136d57 <sys_write+8f/100>
Trace; c010889b <system_call+33/38>

Code;  c0115ba8 <__wake_up+40/d0>
00000000 <_EIP>:
Code;  c0115ba8 <__wake_up+40/d0>   <=====
   0:   8b 01                     mov    (%ecx),%eax   <=====
Code;  c0115baa <__wake_up+42/d0>
   2:   85 45 fc                  test   %eax,0xfffffffc(%ebp)
Code;  c0115bad <__wake_up+45/d0>
   5:   74 69                     je     70 <_EIP+0x70> c0115c18 <__wake_up+b0/d
0>
Code;  c0115baf <__wake_up+47/d0>
   7:   31 c0                     xor    %eax,%eax
Code;  c0115bb1 <__wake_up+49/d0>
   9:   9c                        pushf  
Code;  c0115bb2 <__wake_up+4a/d0>
   a:   5e                        pop    %esi
Code;  c0115bb3 <__wake_up+4b/d0>
   b:   fa                        cli    
Code;  c0115bb4 <__wake_up+4c/d0>
   c:   f0 fe 0d 80 a9 30 c0      lock decb 0xc030a980
Code;  c0115bbb <__wake_up+53/d0>
  13:   0f 00 00                  sldt   (%eax)


2 warnings issued.  Results may not be reliable.

----------------------------------------------------------------------


  reply	other threads:[~2002-05-14 15:09 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-05-08 12:08 kswapd OOPS under 2.4.19-pre8 (ext3, Reiserfs + (soft)raid0) Todd R. Eigenschink
2002-05-14 15:09 ` Todd R. Eigenschink [this message]
2002-05-15 13:51   ` Denis Vlasenko
2002-05-16  0:16     ` Todd R. Eigenschink
2002-05-17 17:15       ` Mike Fedyk

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=15585.10390.825902.226132@rtfm.ofc.tekinteractive.com \
    --to=todd@tekinteractive.com \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).