OK...I removed my qla2x00 module and now I'm seeing another oops that I've
seen before. This only oopsed the raid5d daemon (the machine was still
functional). So now I'm going to disable NFS while this is resyncing.
ksymoops 2.4.5 on i686 2.4.19-pre4. Options used
-V (default)
-k /proc/ksyms (default)
-l /proc/modules (default)
-o /lib/modules/2.4.19-pre4/ (default)
-m /System.map (specified)
Mar 22 11:19:01 yeti kernel: CPU: 1
Mar 22 11:19:01 yeti kernel: EIP:
0010:[nfs:__insmod_nfs_O/lib/modules/2.4.19-pre4/kernel/fs/nfs/nfs.o_+-29438
7/96] Tainted: P
Mar 22 11:19:01 yeti kernel: EFLAGS: 00010a86
Mar 22 11:19:01 yeti kernel: eax: e246dde0 ebx: e17af000 ecx: 00000010
edx: 8005003b
Mar 22 11:19:01 yeti kernel: esi: e17ae000 edi: e17e7000 ebp: e17eb000
esp: e246ddc8
Mar 22 11:19:01 yeti kernel: ds: 0018 es: 0018 ss: 0018
Mar 22 11:19:01 yeti kernel: Process raid5d (pid: 6337, stackpage=e246d000)
Mar 22 11:19:01 yeti kernel: Stack: e17e7000 e17e7000 e17e7000 e17eb000
e17af000 00001000 000000e0 00000000
Mar 22 11:19:01 yeti kernel: 00000000 00000000 00000000 00000000
00000000 00000000 00000000 00000000
Mar 22 11:19:01 yeti kernel: 00000000 00000000 00000000 00000000
00000000 00000000 f8821d0c 00001000
Mar 22 11:19:01 yeti kernel: Call Trace:
[nfs:__insmod_nfs_O/lib/modules/2.4.19-pre4/kernel/fs/nfs/nfs.o_+-291572/96]
[nfs:__insmod_nfs_O/lib/modules/2.4.19-pre4/kernel/fs/nfs/nfs.o_+-278260/96]
[nfs:__insmod_nfs_O/lib/modules/2.4.19-pre4/kernel/fs/nfs/nfs.o_+-273695/96]
[scsi_bottom_half_handler+194/216]
[nfs:__insmod_nfs_O/lib/modules/2.4.19-pre4/kernel/fs/nfs/nfs.o_+-271929/96]
Mar 22 11:19:01 yeti kernel: Code: 8e d0 00 00 00 0f 57 96 e0 00 00 00 0f 57
9e f0 00 00 00 00
Using defaults from ksymoops -t elf32-i386 -a i386
>>eax; e246dde0 <_end+221415ac/384f07cc>
>>ebx; e17af000 <_end+214827cc/384f07cc>
>>edx; 8005003b Before first symbol
>>esi; e17ae000 <_end+214817cc/384f07cc>
>>edi; e17e7000 <_end+214ba7cc/384f07cc>
>>ebp; e17eb000 <_end+214be7cc/384f07cc>
>>esp; e246ddc8 <_end+22141594/384f07cc>
Code; 00000000 Before first symbol
00000000 <_EIP>:
Code; 00000000 Before first symbol
0: 8e d0 mov %eax,%ss
Code; 00000002 Before first symbol
2: 00 00 add %al,(%eax)
Code; 00000004 Before first symbol
4: 00 0f add %cl,(%edi)
Code; 00000006 Before first symbol
6: 57 push %edi
Code; 00000007 Before first symbol
7: 96 xchg %eax,%esi
Code; 00000008 Before first symbol
8: e0 00 loopne a <_EIP+0xa> 0000000a Before first
symbol
Code; 0000000a Before first symbol
a: 00 00 add %al,(%eax)
Code; 0000000c Before first symbol
c: 0f 57 9e f0 00 00 00 xorps 0xf0(%esi),%xmm3
________________________________________
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: "Alan Cox" <alan@lxorguk.ukuu.org.uk>
To: <mblack@csihq.com>
Cc: "Alan Cox" <alan@lxorguk.ukuu.org.uk>; "linux-kernel"
<linux-kernel@vger.kernel.org>; "raid" <linux-raid@vger.kernel.org>; "John
Graves" <jgraves@csihq.com>
Sent: Friday, March 22, 2002 11:17 AM
Subject: Re: 2.4.19-pre4 aic7xxx problems
> The "Tainted" is a qlogic fibre channel driver qla2x00 -- which by the way
> just finished resyncing OK on my 200GB 7-drive fibre channel array (and
has
> been running fine for months).
> qla2x00src-v4.27Beta.tgz
>
> Do you think this could be interfering?
Its always possible but I've no reason to assume that or believe it to be
the cause. I was just checking what else was loaded
-
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
