Alan,
Booted without loading NVdriver
After a few days, i again have a dmesg full of oopses
all seemingly (almost) identical
I have previously (about 2 months ago) run memtest86 for 24hours without
it finding any problems .. I'll try it again
the new non-tainted oops
ksymoops 2.4.4 on i686 2.4.19-rc1. Options used
-V (default)
-k /proc/ksyms (default)
-l /proc/modules (default)
-o /lib/modules/2.4.19-rc1/ (default)
-m /boot/System.map-2.4.19-rc1 (default)
Warning: You did not tell me where to find symbol information. I will
assume that the log matches the kernel and modules that are running
right now and I'll use the default options above for symbol resolution.
If the current kernel and/or modules do not match the log, you can get
more accurate output by telling me the kernel version and where to find
map, modules, ksyms etc. ksymoops -h explains the options.
Error (expand_objects): cannot stat(/lib/ext3.o) for ext3
Error (expand_objects): cannot stat(/lib/jbd.o) for jbd
Warning (map_ksym_to_module): cannot match loaded module ext3 to a unique
module object. Trace may not be reliable.
Unable to handle kernel paging request at virtual address 00120015
c0147154
*pde = 00000000
Oops: 0000
CPU: 0
EIP: 0010:[<c0147154>] Not tainted
Using defaults from ksymoops -t elf32-i386 -a i386
EFLAGS: 00010207
eax: cff80000 ebx: 00120005 ecx: 0000000f edx: 13ad5e39
esi: cbce5000 edi: c2ca7f9c ebp: 00120015 esp: c2ca7ef8
ds: 0018 es: 0018 ss: 0018
Process updatedb (pid: 3696, stackpage=c2ca7000)
Stack: cffbac80 cbce5000 13ad5e39 00000005 c2ca7f64 cbce5000 c2ca7f9c
cffc4180
c013ebbe cfbe83c0 c2ca7f64 c2ca7f64 c013f3ba cfbe83c0 c2ca7f64
00000000
00000008 cbce5005 00000000 00000312 00000000 00000000 00001000
fffffff4
Call Trace: [<c013ebbe>] [<c013f3ba>] [<c013e99d>] [<c013f9f3>]
[<c013c8a4>]
[<c01089ac>] [<c01088bb>]
Code: 8b 6d 00 39 53 44 0f 85 80 00 00 00 8b 44 24 24 39 43 0c 75
>>EIP; c0147154 <d_lookup+64/110> <=====
Trace; c013ebbe <cached_lookup+e/50>
Trace; c013f3ba <link_path_walk+5fa/890>
Trace; c013e99d <getname+5d/a0>
Trace; c013f9f3 <__user_walk+33/50>
Trace; c013c8a4 <sys_lstat64+14/70>
Trace; c01089ac <error_code+34/3c>
Trace; c01088bb <system_call+33/38>
Code; c0147154 <d_lookup+64/110>
00000000 <_EIP>:
Code; c0147154 <d_lookup+64/110> <=====
0: 8b 6d 00 mov 0x0(%ebp),%ebp <=====
Code; c0147157 <d_lookup+67/110>
3: 39 53 44 cmp %edx,0x44(%ebx)
Code; c014715a <d_lookup+6a/110>
6: 0f 85 80 00 00 00 jne 8c <_EIP+0x8c> c01471e0
<d_lookup+f0/110>
Code; c0147160 <d_lookup+70/110>
c: 8b 44 24 24 mov 0x24(%esp,1),%eax
Code; c0147164 <d_lookup+74/110>
10: 39 43 0c cmp %eax,0xc(%ebx)
Code; c0147167 <d_lookup+77/110>
13: 75 00 jne 15 <_EIP+0x15> c0147169
<d_lookup+79/110>
2 warnings and 2 errors issued. Results may not be reliable.
thanks,
/ Brett Pemberton
On Wed, 10 Jul 2002, Alan Cox wrote:
> > Yes, the kernel is tainted, thanks to NVdriver
> > I booted with it, changed X to use nv driver and restarted X, so kernel
> > stayed tainted, but module is no longer loaded.
>
> The module could have done the damage already. Do this from a cold
> boot never loading the NV driver. The crash looks like memory corruption
> so its important to do this and may also be worth running memtest86 a bit
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Tue Jul 23 2002 - 22:00:33 EST