Messages in this thread |  | | | Date | Tue, 31 Aug 1999 22:40:23 -0400 (EDT) | | From | "Steven N. Hirsch" <> | | Subject | Re: NFSv3: Summary of recent bugfixes/updates to the NFSv3 patches... |
| |
On Tue, 31 Aug 1999, Steven N. Hirsch wrote:
> On 31 Aug 1999, Trond Myklebust wrote: > > > The current version of the NFSv3 patches is 0.11.6. It should patch > > cleanly against stock linux-2.2.10, 2.2.11 and 2.2.12. > > Will this apply cleanly to an otherwise-stock 2.2.12 kernel with HJ Lu's > server patches previously added?
Following up on my own post. After fixing three small conflicts, they do apply over HJ's. However, lockd still ooopses immediately when exercising locks against another server. This is the problem I reported weeks ago.
Unlike last time, I can't seem to get a reasonable decode of the oops. For what it's worth (even though it says it's obsolete, the latest from Keith does the same thing):
WARNING: This version of ksymoops is obsolete. WARNING: The current version can be obtained from ftp://ftp.ocs.com.au/pub/ksymoops Options used: -V (default) -o /lib/modules/2.2.13pre1nfs3/ (default) -k /proc/ksyms (default) -l /proc/modules (default) -m /usr/src/linux/System.map (default) -c 1 (default)
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.
Aug 31 22:20:02 pii kernel: Unable to handle kernel NULL pointer dereference at virtual address 0000000c Aug 31 22:20:02 pii kernel: current->tss.cr3 = 00101000, %cr3 = 00101000 Aug 31 22:20:02 pii kernel: *pde = 00000000 Aug 31 22:20:02 pii kernel: Oops: 0002 Aug 31 22:20:02 pii kernel: CPU: 1 Aug 31 22:20:02 pii kernel: EIP: 0010:[rpcauth_holdcred+56/84] Aug 31 22:20:02 pii kernel: EFLAGS: 00010202 Aug 31 22:20:02 pii kernel: eax: 00000004 ebx: c987f140 ecx: 00000000 edx: 00000004 Aug 31 22:20:02 pii kernel: esi: fffffff4 edi: c015788c ebp: 00000002 esp: cf493de8 Aug 31 22:20:02 pii kernel: ds: 0018 es: 0018 ss: 0018 Aug 31 22:20:02 pii kernel: Process lockd (pid: 1396, process nr: 13, stackpage=cf493000) Aug 31 22:20:02 pii kernel: Stack: c987f140 c9e73e80 ceb1c000 00000004 0000000f cf493e00 fffffeff ffffffff Aug 31 22:20:02 pii kernel: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 Aug 31 22:20:02 pii kernel: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 Aug 31 22:20:02 pii kernel: Call Trace: [nlmclnt_async_call+149/172] [nlmsvc_callback_exit+0/84] [nlmsvc_callback+112/136] [nlmsvc_callback_exit+0/84] [nlmsvc_proc_granted_msg+0/92] [nlmsvc_proc_granted_msg+79/92] [wake_up_process+82/104] Aug 31 22:20:02 pii kernel: Code: 66 ff 40 08 8b 43 14 8b 4b 1c 8b 50 18 a1 a0 69 21 c0 03 42 Code: 00000000 Before first symbol 00000000 <_IP>: <=== Code: 00000000 Before first symbol 0: 66 ff 40 08 incw 0x8(%eax) <=== Code: 00000004 Before first symbol 4: 8b 43 14 movl 0x14(%ebx),%eax Code: 00000007 Before first symbol 7: 8b 4b 1c movl 0x1c(%ebx),%ecx Code: 0000000a Before first symbol a: 8b 50 18 movl 0x18(%eax),%edx Code: 0000000d Before first symbol d: a1 a0 69 21 c0 movl 0xc02169a0,%eax Code: 00000012 Before first symbol 12: 03 42 00 addl 0x0(%edx),%eax
805 warnings issued. Results may not be reliable.
Can anything be done to make your NFSv3 patch and HJ's server patches cooperate?
Steve
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.tux.org/lkml/
|  |