[DragonFlyBSD - Bug #2365] Hammer pfs-destroy and prune-everything can cause network loss
Issue #2365 has been updated by t_dfbsd. As recent as one month ago, this was still a problem. In fact, it happened very consistently with hammer prune-everything. Tonight, I ran it twice and network connections to the box didn't drop. Could recent commits have fixed this? Bug #2365: Hammer pfs-destroy and prune-everything can cause network loss http://bugs.dragonflybsd.org/issues/2365 Author: t_dfbsd Status: New Priority: Normal Assignee: Category: Target version: Fairly consistently, when I run hammer prune-everything, at some point in the process my ssh session will stop and not recover and the machine becomes unavailable on the network. It eventually returns to normal and I can reconnect to it. Today, I ran a hammer pfs-destroy on a 1.3TB pfs and the same thing happened. While the network was out, it was putting these messages in the log: swap_pager: indefinite wait buffer: offset: 6489661440, size: 4096 swap_pager: indefinite wait buffer: offset: 23187279872, size: 4096 swap_pager: indefinite wait buffer: offset: 6642294784, size: 4096 swap_pager: indefinite wait buffer: offset: 6536355840, size: 4096 swap_pager: indefinite wait buffer: offset: 6500122624, size: 4096 swap_pager: indefinite wait buffer: offset: 6489661440, size: 4096 swap_pager: indefinite wait buffer: offset: 6725648384, size: 4096 swap_pager: indefinite wait buffer: offset: 23187279872, size: 4096 swap_pager: indefinite wait buffer: offset: 6642294784, size: 4096 swap_pager: indefinite wait buffer: offset: 6536355840, size: 4096 swap_pager: indefinite wait buffer: offset: 6500122624, size: 4096 swap_pager: indefinite wait buffer: offset: 861982720, size: 4096 swap_pager: indefinite wait buffer: offset: 6489661440, size: 4096 swap_pager: indefinite wait buffer: offset: 6725648384, size: 4096 swap_pager: indefinite wait buffer: offset: 23187279872, size: 4096 swap_pager: indefinite wait buffer: offset: 6642294784, size: 4096 swap_pager: indefinite wait buffer: offset: 1027108864, size: 4096 swap_pager: indefinite wait buffer: offset: 6536355840, size: 4096 swap_pager: indefinite wait buffer: offset: 6500122624, size: 4096 -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://bugs.dragonflybsd.org/my/account
[DragonFlyBSD - Bug #2523] route show is stuck in an infinite loop
Issue #2523 has been reported by jorisgio. Bug #2523: route show is stuck in an infinite loop http://bugs.dragonflybsd.org/issues/2523 Author: jorisgio Status: New Priority: Normal Assignee: Category: Target version: netstat -r prints the routing table, but "route show" does not terminate. As far as i understand, netname is called with a host address instead of a network address, the ip of my nic. Here is a backtrace : Starting program: /usr/src/sbin/route/route show Routing tables Internet: Destination Gateway Flags ^C Program received signal SIGINT, Interrupt. netname (sa=0x80069d0a8) at route.c:465 465 mask = (long)mask >> subnetshift; (gdb) bt #0 netname (sa=0x80069d0a8) at route.c:465 #1 0x0040493e in p_sockaddr (sa=0x80069d0a8, flags=0, width=31) at show.c:343 #2 0x0040464f in p_rtentry (rtm=0x80069d000) at show.c:240 #3 0x0040444d in show (argc=1, argv=0x7798) at show.c:174 #4 0x004006ed in main (argc=1, argv=0x7798) at route.c:192 -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://bugs.dragonflybsd.org/my/account
[DragonFlyBSD - Bug #2522] (Closed) Re: panic: assertion "IS_SERIALIZED((ifp->if_serializer))" failed in if_default_serialize_assert at /usr/src/sys/net/if.c:437
Issue #2522 has been updated by ano. Status changed from New to Closed Bug #2522: Re: panic: assertion "IS_SERIALIZED((ifp->if_serializer))" failed in if_default_serialize_assert at /usr/src/sys/net/if.c:437 http://bugs.dragonflybsd.org/issues/2522 Author: ano Status: Closed Priority: Normal Assignee: Category: Target version: http://tt.bestmx.ru/coredump/coredump_ath_7.tbz -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://bugs.dragonflybsd.org/my/account
[DragonFlyBSD - Bug #2520] panic: assertion "IS_SERIALIZED((ifp->if_serializer))" failed in if_default_serialize_assert at /usr/src/sys/net/if.c:437
Issue #2520 has been updated by ano. Here is a coredump: http://tt.bestmx.ru/coredump/coredump_ath_7.tbz Bug #2520: panic: assertion "IS_SERIALIZED((ifp->if_serializer))" failed in if_default_serialize_assert at /usr/src/sys/net/if.c:437 http://bugs.dragonflybsd.org/issues/2520 Author: ano Status: New Priority: Normal Assignee: Category: Target version: Good day. I have a coredump on recent kernel (v3.3.0.1274.g6f2f8-DEVELOPMENT). -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://bugs.dragonflybsd.org/my/account