Help on the new 2.6 test kernel With some additional information
Guo Yang
gxy3139 at njit.edu
Thu Oct 9 22:14:30 UTC 2003
lars wrote:
>thats not the way it should be.
>maybe zander, who wrote the nvidia 2.6 patches can help you with
>this... had a little chat on irc with him and he tried vanilla test6-bk8 on
>his laptop, worked ok for him and later for me too.
>you can reach him via irc @ irc.freenode.net #nvidia
>
>good luck!
>lars
>
>
>
>you wrote:
>Thanks for reply, lars. I am not so lucky. When it first happened I thought it
>might be because I didn't upgrade to the severn2. But today after I upgraded
>my system and tried the test7 it was still there :(
>
>Guo
>
>
>
>--
>fedora-test-list mailing list
>fedora-test-list at redhat.com
>http://www.redhat.com/mailman/listinfo/fedora-test-list
>
Thanks, lars.
This afternoon, I tried ksymoops to decode the oops and got the output
below. (unfortunately I don't know where the /proc/ksym is so it may not
be so useful) Hopefully it is useful to some experts.
ksymoops 2.4.9 on i686 2.6.0-0.test7.1.51. Options used
-V (default)
-k /proc/kallsyms (specified)
-l /proc/modules (default)
-o /lib/modules/2.6.0-0.test7.1.51/ (default)
-m /boot/System.map (specified)
Warning (read_ksyms): no kernel symbols in ksyms, is /proc/kallsyms a
valid ksyms file?
No modules in ksyms, skipping objects
No ksyms, skipping lsmod
Unable to handle kernel paging request at virtual address 49656e69
d0cacc11
*pde = 00000000
Oops: 0000 [#1]
CPU: 0
EIP: 0060:[<d0cacc11>] Tainted: PF
Using defaults from ksymoops -t elf32-i386 -a i386
EFLAGS: 00010246
eax: cb209f5c ebx: c02e06f0 ecx: 6c65746e edx: 49656e69
esi: cb209f5c edi: 49656e69 ebp: cb209f6c esp: cb209f3c
ds: 007b es: 007b ss: 0068
Stack: d0d06000 00000001 d0b83e39 cb209f5c d0cb3360 0000000c 00000000
00000002
756e6547 49656e69 6c65746e d0caae80 cb209f74 d0b83e90 cb209f7c
d0b85fd8
c02e06d8 d08630e1 00000000 d0cc2680 000000c3 c02d2414 b7c2a008
c02e06f0
Call Trace:
[<d0b83e39>] __nvsym00760+0x49/0x98 [nvidia]
[<d0caae80>] nv_kern_pm+0x0/0xf0 [nvidia]
[<d0b83e90>] __nvsym00763+0x8/0x50 [nvidia]
[<d0b85fd8>] rm_init_rm+0x8/0xc [nvidia]
[<d08630e1>] nvidia_init_module+0xe1/0x184 [nvidia]
[<c013114f>] sys_init_module+0xef/0x1d0
[<c010aeef>] syscall_call+0x7/0xb
Code: f3 a6 0f 92 c0 8b 34 24 8b 7c 24 04 0f 97 c2 83 c4 08 28 c2
>>EIP; d0cacc11 <__crc_mb_cache_entry_release+2a56e4/4823ea> <=====
>>eax; cb209f5c <__crc_tcp_openreq_cachep+2e34dc/6728d7>
>>ebx; c02e06f0 <notify_mutex+0/10>
>>ecx; 6c65746e <__crc_xtime_lock+37aae/52a57>
>>edx; 49656e69 <__crc_udp_hash+274888/880395>
>>esi; cb209f5c <__crc_tcp_openreq_cachep+2e34dc/6728d7>
>>edi; 49656e69 <__crc_udp_hash+274888/880395>
>>ebp; cb209f6c <__crc_tcp_openreq_cachep+2e34ec/6728d7>
>>esp; cb209f3c <__crc_tcp_openreq_cachep+2e34bc/6728d7>
Trace; d0b83e39 <__crc_mb_cache_entry_release+17c90c/4823ea>
Trace; d0caae80 <__crc_mb_cache_entry_release+2a3953/4823ea>
Trace; d0b83e90 <__crc_mb_cache_entry_release+17c963/4823ea>
Trace; d0b85fd8 <__crc_mb_cache_entry_release+17eaab/4823ea>
Trace; d08630e1 <__crc_in_dev_finish_destroy+216236/21e270>
Trace; c013114f <sys_init_module+ef/1d0>
Trace; c010aeef <syscall_call+7/b>
Code; d0cacc11 <__crc_mb_cache_entry_release+2a56e4/4823ea>
00000000 <_EIP>:
Code; d0cacc11 <__crc_mb_cache_entry_release+2a56e4/4823ea> <=====
0: f3 a6 repz cmpsb %es:(%edi),%ds:(%esi) <=====
Code; d0cacc13 <__crc_mb_cache_entry_release+2a56e6/4823ea>
2: 0f 92 c0 setb %al
Code; d0cacc16 <__crc_mb_cache_entry_release+2a56e9/4823ea>
5: 8b 34 24 mov (%esp,1),%esi
Code; d0cacc19 <__crc_mb_cache_entry_release+2a56ec/4823ea>
8: 8b 7c 24 04 mov 0x4(%esp,1),%edi
Code; d0cacc1d <__crc_mb_cache_entry_release+2a56f0/4823ea>
c: 0f 97 c2 seta %dl
Code; d0cacc20 <__crc_mb_cache_entry_release+2a56f3/4823ea>
f: 83 c4 08 add $0x8,%esp
Code; d0cacc23 <__crc_mb_cache_entry_release+2a56f6/4823ea>
12: 28 c2 sub %al,%dl
1 warning issued. Results may not be reliable.
More information about the test
mailing list