> So if you have seen NFS problems in 2.1.117 please try and replicate
> then with this patch.
> When an RPC is interrupted by a signal (this should be kill -9 only
> or ^C ^\ or kill -9 if its mounted "intr") the kernel will dump
> a logging entry like this
> RPC terminated by signal
> RPC process was cp (pid 665)
> RPC signal block is FFFFFEF9 pending = 2
> If Linus theory is right people with the mysterious failures and
> hangs will see something similar when the hang/fail in emacs etc
> occurs. The dump from that will let me see whats up. With that I
> can fix the real bug properly.
I'm seeing a lot of the following:
Aug 24 12:00:07 charged kernel: RPC terminated by signal
Aug 24 12:00:07 charged kernel: RPC process was xemacs (pid 927)
Aug 24 12:00:07 charged kernel: RPC signal block is 0 pending = 10000000
(which sometimes coincides with the abort of my backup)
and
Aug 24 11:56:45 charged kernel: RPC terminated by signal
Aug 24 11:56:45 charged kernel: RPC process was netscape-commun (pid 945)
Aug 24 11:56:45 charged kernel: RPC signal block is 0 pending = 2000
(no obvious effects on the running netscape)
Cheers,
Trond
-
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