badness in umount? FC4

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



I have just installed FC4 on an older machine and I seem to get a kernel error when a umount is done by the automounter after a user logs out:

Nov 22 18:53:30 tdb3 su(pam_unix)[3502]: session opened for user mganes by (uid=0)
Nov 22 18:53:35 tdb3 su(pam_unix)[3502]: session closed for user mganes

(automounter unmounts home and other directories)

Nov 22 18:54:39 tdb3 kernel: Badness in interruptible_sleep_on_timeout at kernel/sched.c:3403 (Not tainted) Nov 22 18:54:39 tdb3 kernel: [<c031d2b2>] interruptible_sleep_on_timeout+0xf7/0x114
Nov 22 18:54:39 tdb3 kernel:  [<c012b213>] group_send_sig_info+0x59/0x63
Nov 22 18:54:39 tdb3 kernel:  [<c011c4de>] default_wake_function+0x0/0xc
Nov 22 18:54:39 tdb3 kernel:  [<f9bca4fb>] lockd_down+0xbe/0x120 [lockd]
Nov 22 18:54:39 tdb3 kernel:  [<f9c8bcf7>] nfs_kill_super+0x5c/0x5e [nfs]
Nov 22 18:54:39 tdb3 kernel:  [<c01699ed>] deactivate_super+0x60/0x71
Nov 22 18:54:39 tdb3 kernel:  [<c017eb4e>] sys_umount+0x33/0x73
Nov 22 18:54:39 tdb3 kernel:  [<c0107dc6>] do_syscall_trace+0x1e4/0x1f6
Nov 22 18:54:39 tdb3 kernel:  [<c017eba5>] sys_oldumount+0x17/0x1b
Nov 22 18:54:39 tdb3 kernel:  [<c01039e1>] syscall_call+0x7/0xb

System is: Linux tdb3 2.6.14-1.1637_FC4smp #1 SMP Wed Nov 9 18:34:11 EST 2005 i686 i686 i386 GNU/Linux

It doesn't seem to be panicking; just this dump. Seems to happen every time. This particular user gets about 5 mounts whenever he logs in, but it did the same thing for me and my login only mounts my home directory.

Hugh

--
Hugh Caley | Unix Systems Administrator | CIS
AFFYMETRIX, INC. | 6550 Vallejo St. Ste 100 | Emeryville, CA 94608
Tel: 510-428-8537 | Hugh_Caley@xxxxxxxxxxxxxx


[Index of Archives]     [Current Fedora Users]     [Fedora Desktop]     [Fedora SELinux]     [Yosemite News]     [Yosemite Photos]     [KDE Users]     [Fedora Tools]     [Fedora Docs]

  Powered by Linux