mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Mike Black" <mblack@csihq.com>
To: "linux-kernel" <linux-kernel@vger.kernel.org>
Subject: Re: 2.4.17-pre7 oops
Date: Thu, 18 Apr 2002 12:40:59 -0400	[thread overview]
Message-ID: <007401c1e6f7$d213d430$e1de11cc@csihq.com> (raw)

Without device even mounted or exported this time:
ksymoops 2.4.5 on i686 2.4.19-pre7.  Options used
     -V (default)
     -k /proc/ksyms (default)
     -l /proc/modules (default)
     -o /lib/modules/2.4.19-pre7/ (default)
     -m /System.map (specified)

Apr 18 12:08:32 yeti kernel: Unable to handle kernel NULL pointer
dereference at virtual address 00000006
Apr 18 12:08:32 yeti kernel: f8826437
Apr 18 12:08:32 yeti kernel: *pde = 00000000
Apr 18 12:08:32 yeti kernel: Oops: 0000
Apr 18 12:08:32 yeti kernel: CPU:    1
Apr 18 12:08:32 yeti kernel: EIP:
0010:[nfs:__insmod_nfs_O/lib/modules/2.4.19-pre7/kernel/fs/nfs/nfs.o_+-27744
9/96]    Tainted: P
Apr 18 12:08:32 yeti kernel: EFLAGS: 00010246
Apr 18 12:08:32 yeti kernel: eax: 00000000   ebx: f5870dc0   ecx: 00000002
edx: f5daed60
Apr 18 12:08:32 yeti kernel: esi: f5ab7c00   edi: f5daec00   ebp: f5daec00
esp: f59fbe88
Apr 18 12:08:32 yeti kernel: ds: 0018   es: 0018   ss: 0018
Apr 18 12:08:32 yeti kernel: Process raid5d (pid: 17544, stackpage=f59fb000)
Apr 18 12:08:32 yeti kernel: Stack: 00000000 f5daec00 f5ab7c00 f5fa1de0
00000001 00000001 000000f8 c011cf73
Apr 18 12:08:32 yeti kernel:        00000000 c009ec00 f5ab7d58 f59fbf24
f5ab7cec f5ab7c80 f5daec14 00000000
Apr 18 12:08:32 yeti kernel:        f5ab7c14 00000000 00000001 00000001
00000001 0000000c 00000001 ffffffff
Apr 18 12:08:32 yeti kernel: Call Trace: [tasklet_hi_action+103/160]
[nfs:__insmod_nfs_O/lib/modules/2.4.19-pre7/kernel/fs/nfs/nfs.o_+-275842/96]
[md_thread+341/440] [kernel_thread+40/56]
Apr 18 12:08:32 yeti kernel: Code: 8b 41 04 50 e8 d8 5a 9a c7 00 00 00 00 74
51 83 7c 24 7c 00
Using defaults from ksymoops -t elf32-i386 -a i386


>>ebx; f5870dc0 <_end+3553350c/384df74c>
>>edx; f5daed60 <_end+35a714ac/384df74c>
>>esi; f5ab7c00 <_end+3577a34c/384df74c>
>>edi; f5daec00 <_end+35a7134c/384df74c>
>>ebp; f5daec00 <_end+35a7134c/384df74c>
>>esp; f59fbe88 <_end+356be5d4/384df74c>

Code;  00000000 Before first symbol
00000000 <_EIP>:
Code;  00000000 Before first symbol
   0:   8b 41 04                  mov    0x4(%ecx),%eax
Code;  00000003 Before first symbol
   3:   50                        push   %eax
Code;  00000004 Before first symbol
   4:   e8 d8 5a 9a c7            call   c79a5ae1 <_EIP+0xc79a5ae1> c79a5ae1
<_end+766822d/384df74c>
Code;  00000009 Before first symbol
   9:   00 00                     add    %al,(%eax)
Code;  0000000b Before first symbol
   b:   00 00                     add    %al,(%eax)
Code;  0000000d Before first symbol
   d:   74 51                     je     60 <_EIP+0x60> 00000060 Before
first symbol
Code;  0000000f Before first symbol
   f:   83 7c 24 7c 00            cmpl   $0x0,0x7c(%esp,1)

________________________________________
Michael D. Black   Principal Engineer
mblack@csihq.com  321-676-2923,x203
http://www.csihq.com  Computer Science Innovations
http://www.csihq.com/~mike  My home page
FAX 321-676-2355
----- Original Message -----
From: "Mike Black" <mblack@csihq.com>
To: "linux-kernel" <linux-kernel@vger.kernel.org>
Sent: Thursday, April 18, 2002 7:56 AM
Subject: 2.4.17-pre7 oops


I've been having problems resyncing my 2TB RAID5 Ultra160 array for every
kernel version I've tried.  Here's the latest.
The drive being resynced is mounted and exported via NFS while it's
resyncing.
I'll try it one more time while it's not exported.




             reply	other threads:[~2002-04-18 16:41 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-18 16:40 Mike Black [this message]
2002-04-18 23:08 ` Keith Owens
  -- strict thread matches above, loose matches on Subject: below --
2002-04-18 11:56 Mike Black

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='007401c1e6f7$d213d430$e1de11cc@csihq.com' \
    --to=mblack@csihq.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

all inboxes | Powered by JetHome®