AW: strange error codes on fedora4 (dmesg)
Sebastian Kösters
skoesters at sino.de
Wed Nov 9 08:29:07 UTC 2005
Thanks!
But do you know what this error means and from where it comes?
Maybe it is the nfslockd? On every shutdown fedora 4 is not able to Stopp
it?!
-----Ursprüngliche Nachricht-----
Von: fedora-list-bounces at redhat.com [mailto:fedora-list-bounces at redhat.com]
Im Auftrag von Gilboa Davara
Gesendet: Dienstag, 8. November 2005 16:42
An: For users of Fedora Core releases
Betreff: Re: strange error codes on fedora4 (dmesg)
I assume that message started with
"Badness in interruptible_sleep_on_timeout"
You can open a bugzilla report about it.
But as long as your machine remains stable, you can ignore it.
Gilboa
On Tue, 2005-11-08 at 16:15 +0100, Sebastian Kösters wrote:
> Hi,
>
>
>
> i found this error codes on a fedora 4 Machine:
>
>
>
> dmesg:
>
>
>
> [<c031746f>] interruptible_sleep_on_timeout+0xf7/0x113
>
> [<c012b9e1>] group_send_sig_info+0x59/0x63
>
> [<c011d046>] default_wake_function+0x0/0xc
>
> [<f8a5f48b>] lockd_down+0xbe/0x120 [lockd]
>
> [<f8aeecbe>] nfs_kill_super+0x5e/0x62 [nfs]
>
> [<c0169fd8>] deactivate_super+0x5d/0x6e
>
> [<c017ef34>] sys_umount+0x33/0x73
>
> [<c017bf5b>] destroy_inode+0x3f/0x4e
>
> [<c0108055>] do_syscall_trace+0xef/0x123
>
> [<c017ef8b>] sys_oldumount+0x17/0x1b
>
> [<c010395d>] syscall_call+0x7/0xb
>
>
>
> Does someone know what that means?
>
>
>
> Regards
>
> Sebastian
>
>
--
fedora-list mailing list
fedora-list at redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
More information about the fedora-list
mailing list