Rpciod Oops 2.1.111 on Alpha

Daryll Strauss (daryll@d2.com)
Thu, 30 Jul 1998 11:22:42 -0700


I can consistently get the rpciod thread to oops. It happens as soon as
I do a reasonably high NFS client load. This is a PC164 mainboard with a
466Mhz Alpha, 256MB ram, and SMC Ethercard.

Here's the Oops:

Jul 29 12:31:46 linux-62 kernel: Unable to handle kernel paging request
at virtual address 0000000000000010
Jul 29 12:31:46 linux-62 kernel: rpciod(281): Oops 0
Jul 29 12:31:46 linux-62 kernel: pc = [<fffffc00003c842c>] ra = [<fffffc00003c8f58>] ps = 0000
Jul 29 12:31:46 linux-62 kernel: r0 = 0000000000000000 r1 = 0000000000000000 r2 = 0000000000000000
Jul 29 12:31:46 linux-62 kernel: r3 = fffffc001f93c035 r4 = fffffc001f93c036 r5 = fffffc001f93c037
Jul 29 12:31:46 linux-62 kernel: r6 = fffffc001f93c038 r7 = 0000000000000002 r8 = fffffc001f3e4000
Jul 29 12:31:46 linux-62 kernel: r9 = fffffc001f9f7700 r10= fffffc001f93c020 r11= ffffffffffffeea0
Jul 29 12:31:46 linux-62 kernel: r12= fffffc001fc7fe80 r13= fffffc001ecde820 r14= 0000000000001174
Jul 29 12:31:46 linux-62 kernel: r15= 0000000000000014
Jul 29 12:31:46 linux-62 kernel: r16= fffffc001f9f7700 r17= 0000000093fa9171 r18= 0000000000002088
Jul 29 12:31:46 linux-62 kernel: r19= 0000000000001100 r20= 000000000000d8e5 r21= 0000000000000f3c
Jul 29 12:31:46 linux-62 kernel: r22= 0000000000001174 r23= fffffc001f93c03b r24= 0000882001081503
Jul 29 12:31:46 linux-62 kernel: r25= 0000000000008820 r27= fffffc00003c83f0 r28= 0000000000000001
Jul 29 12:31:46 linux-62 kernel: gp = fffffc0000504ea8 sp = fffffc001f3e7968
Jul 29 12:31:46 linux-62 kernel: Code: a02900a0 a4490050 483f9621
<a5620010> a5420058 44211401 b5690030 b02900a0 e540001f
Jul 29 12:31:46 linux-62 kernel: Trace: [<fffffc00003c8f58>]
[<fffffc00003c9048>] [<fffffc00003d9f88>] [<fffffc00003d9f88>]
[<fffffc00003da680>] [<fffffc00003da5b4>] [<fffffc0000315cdc>]
[<fffffc00003e1464>] [<fffffc00003b43dc>] [<fffffc00003f25cc>]
[<fffffc00003f0300>] [<fffffc00003f41f4>] [<fffffc00003f4530>]
[<fffffc00003f4eb0>] [<fffffc0000310728>] [<fffffc00003f4d70>]

If I've looked everything up in the System map correctly the trace is:

pc = [ip_output]
[ip_build_xmit_slow] [ip_build_xmit] [ip_ra_control] [ip_ra_control]
[udp_sendmsg] [udp_sendmsg] [do_entInt] [inet_sendmsg] [sock_sendmsg]
[xprt_transmit] [call_trnasmit] [__rpc_execute] [rpc_allocate] [rpciod]
[__kernel_thread] [rcpiod]

Here's the relevant parts of the System map (just in case)

fffffc00003c83f0 T ip_output
fffffc00003c8540 T ip_queue_xmit
fffffc00003c8a10 T ip_build_xmit_slow
fffffc00003c8fc8 T ip_build_xmit
fffffc00003c9380 T ip_fragment

fffffc00003c9f08 T ip_ra_control
fffffc00003ca080 T ip_setsockopt

fffffc00003da2f8 T udp_sendmsg
fffffc00003da740 T udp_ioctl

fffffc00003157d8 T do_entInt
fffffc0000315da0 T osf_sigprocmask

fffffc00003e1398 T inet_sendmsg
fffffc00003e1490 T inet_shutdown

fffffc00003b4330 T sock_sendmsg
fffffc00003b4420 T sock_recvmsg

fffffc00003f2360 T xprt_transmit
fffffc00003f27e0 t xprt_transmit_status

fffffc00003f02a0 t call_transmit
fffffc00003f0318 t call_receive

fffffc00003f4110 t __rpc_execute
fffffc00003f4380 T rpc_execute

fffffc00003f45a8 T rpc_allocate
fffffc00003f4718 T rpc_free

fffffc00003f4d70 t rpciod
fffffc00003f5000 t rpciod_killall

fffffc00003106d8 T __kernel_thread
fffffc0000310740 T __kernel_execve

-
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.altern.org/andrebalsa/doc/lkml-faq.html