Re: Unkillable process in "vm map (user)"
On Mon, Dec 11, 2017 at 07:09:31AM +1100, Peter Jeremy wrote: > I was experimenting with ports/devel/libmill (which is a library that > provides Go-styly functionality for C programs) and managed to create > an unkillable process by spawning 100 "goroutines" (think very > cheap "thread" or "coroutine") joined by "channels" (think message > passing pipes). (The program ran basically instantaneously with 1 > or 10 "goroutines", and the Go version has no problems with 100 > goroutines on a much smaller system). > > According to SIGINFO, it's blocked on "vm map (user)" but I can't kill > it. Can anyone suggest a way to unwedge it? > > This is on a system running FreeBSD/amd64 11.1-STABLE r324494. Ensure that you use at least r326188. > > server% procstat -kk 452 > PIDTID COMMTDNAME KSTACK > 452 102382 chain - mi_switch+0x17c > sleepq_switch+0x118 sleepq_wait+0x43 _sx_slock_hard+0x34e _sx_slock+0xd4 > vm_map_lookup+0xbd vm_fault_hold+0x194b vm_fault+0x75 trap_pfault+0x107 > trap+0x382 calltrap+0x8 There is another thread owning the map lock, and seeing what that thread does is the next step. Can you provide a binary to reproduce which does not depend on any library except the base libs ? ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Unkillable process in "vm map (user)"
I was experimenting with ports/devel/libmill (which is a library that
provides Go-styly functionality for C programs) and managed to create
an unkillable process by spawning 100 "goroutines" (think very
cheap "thread" or "coroutine") joined by "channels" (think message
passing pipes). (The program ran basically instantaneously with 1
or 10 "goroutines", and the Go version has no problems with 100
goroutines on a much smaller system).
According to SIGINFO, it's blocked on "vm map (user)" but I can't kill
it. Can anyone suggest a way to unwedge it?
This is on a system running FreeBSD/amd64 11.1-STABLE r324494.
server% procstat -kk 452
PIDTID COMMTDNAME KSTACK
452 102382 chain - mi_switch+0x17c
sleepq_switch+0x118 sleepq_wait+0x43 _sx_slock_hard+0x34e _sx_slock+0xd4
vm_map_lookup+0xbd vm_fault_hold+0x194b vm_fault+0x75 trap_pfault+0x107
trap+0x382 calltrap+0x8
server% ps -wal -p 452
UID PID PPID CPU PRI NI VSZ RSS MWCHAN STAT TT TIME COMMAND
204 452 53567 0 20 0 244064932 2180 vm map ( DL+ 13 0:10.31 ./chain
100
server% cat src/mill/chain.c
#include
#include
#include
coroutine void f(chan left, chan right) {
chs(left, int, 1 + chr(right, int));
}
int main(int argc, char **argv) {
int i, n = argv[1] ? atoi(argv[1]) : 1;
chan leftmost = chmake(int, 0);
chan left = NULL;
chan right = leftmost;
for (i = 0; i < n; i++) {
left = right;
right = chmake(int, 0);
go(f(left, right));
}
chs(right, int, 0);
i = chr(leftmost, int);
printf("result = %d\n", i);
return 0;
}
server%
--
Peter Jeremy
signature.asc
Description: PGP signature
Re: Two problems about ASUS N3150I-C
Without more info it's likely going to be hard for anyone to help but both these symptoms you mention could be possibly related to processes that depend on the system clock not being messed with. Some people these days try to cheat on games and stuff like that by using hacks that mess with the system clock. Those symptoms you are observing could be a way of your system letting you know it won't work right if you let apps mess with the system clock. Maybe not. If others have the same motherboard and use the same Realtek NIC but are not having problems I'd guess it's related programs on your system adjusting the system clock. If that's not the case you may want to make sure ntp is working and maybe chose a different ntp server. Maybe it's something else. You'll likely be asked for more technical feedback from log files though if you want help with this issue. You also could try disabling the onboard NIC and by a new NIC. Ryan Sent from BlueMail On Dec 10, 2017, 4:02 AM, at 4:02 AM, Yasuhiro KIMURA wrote: >Hello. > >I have two 11.1-RELEASE amd64 boxes working as my home servers. Their >hardware spec are same and ASUS N3150I-C is used as motherboad. And >there are two problems about it. > >1. 'shutdown -r now' doesn't work after system has been up for a while > >If I try 'shutdown -r now' just after system is up or after few hours, >it works as is expected. But, for example, if I try it after one week >of uptime, then it doesn't work anymore. OS is shutdown successfully >but reset never happens. I updated BIOS of motherboard to latest one >but it didn't fix the problem. And this problem happens on both boxes. > >2. NIC gets no response with 're0: watchdog timeout' kernel message > >Realtek RTL8111H is used as NIC of this motherboad. Sometime it gets >no response after following kernel messages are displayed some times. > >Dec 10 01:11:37 maybe kernel: re0: watchdog timeout >Dec 10 01:11:37 maybe kernel: re0: link state changed to DOWN >Dec 10 01:11:41 maybe kernel: re0: link state changed to UP > >If this happens system need to be rebooted. It is very variable when >NIC get this status. Sometime it happens after few hours system is up, >but sometimes it doesn't happen after a month of uptime. And this >problem happens only one of two boxes. One box is used for internal >services and the other is used for external ones. The problem only >happens on the latter. As is explaind above they have same hardware >spec, but OS settings and/or installed applications are differnt. So >it seems some of them specific to the latter are cause of NIC hangup. > >Then, are there any way to fix these problems or investigate why they >happens? Any suggestions or comments are welcome. > >--- >Yasuhiro KIMURA >___ >freebsd-stable@freebsd.org mailing list >https://lists.freebsd.org/mailman/listinfo/freebsd-stable >To unsubscribe, send any mail to >"freebsd-stable-unsubscr...@freebsd.org" ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Two problems about ASUS N3150I-C
Hello. I have two 11.1-RELEASE amd64 boxes working as my home servers. Their hardware spec are same and ASUS N3150I-C is used as motherboad. And there are two problems about it. 1. 'shutdown -r now' doesn't work after system has been up for a while If I try 'shutdown -r now' just after system is up or after few hours, it works as is expected. But, for example, if I try it after one week of uptime, then it doesn't work anymore. OS is shutdown successfully but reset never happens. I updated BIOS of motherboard to latest one but it didn't fix the problem. And this problem happens on both boxes. 2. NIC gets no response with 're0: watchdog timeout' kernel message Realtek RTL8111H is used as NIC of this motherboad. Sometime it gets no response after following kernel messages are displayed some times. Dec 10 01:11:37 maybe kernel: re0: watchdog timeout Dec 10 01:11:37 maybe kernel: re0: link state changed to DOWN Dec 10 01:11:41 maybe kernel: re0: link state changed to UP If this happens system need to be rebooted. It is very variable when NIC get this status. Sometime it happens after few hours system is up, but sometimes it doesn't happen after a month of uptime. And this problem happens only one of two boxes. One box is used for internal services and the other is used for external ones. The problem only happens on the latter. As is explaind above they have same hardware spec, but OS settings and/or installed applications are differnt. So it seems some of them specific to the latter are cause of NIC hangup. Then, are there any way to fix these problems or investigate why they happens? Any suggestions or comments are welcome. --- Yasuhiro KIMURA ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
hw.vga.textmode=1 and the installation media
Hi, would be really nice if the 11.2 and subsequent versions would come with the hw.vga.textmode=1 as the default in the installation media. Because you know, there's a problem with some vendors (like HP) who's servers are incapable of showing graphics in IPMI with the default hw.vga.textmode=0 (yeah, I'm aware that most of the vendors don't have this issue), and there's still a bug that prevents this from being set from a loader prompt - USB keyboard doesn't work at least in 11.0 there (seems to be some sort of FreeBSD "holy cow", along with sshd starting last, after all the local daemons. I would ask again to fix the latter as I did last years, but it really seems to be a cornerstone which the FreeBSD is built upon). Thanks. Eugene. ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Cannot build 11-STABLE from 12-CURRENT due to missing lint
On 11/26, Shawn Webb wrote: > On Sun, Nov 26, 2017 at 05:33:26PM -0500, Shawn Webb wrote: > > Now that `lint` was removed from 12-CURRENT base, 12-CURRENT now > > cannot build 11-STABLE. Building usr.bin/xlint/llib in 11-STABLE > > depends on `lint`. > > > > https://github.com/freebsd/freebsd/blob/stable/11/usr.bin/xlint/llib/Makefile > > Bug filed: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=223892 Seconded. It breaks 'poudriere jail -u' functionality as well. K. signature.asc Description: PGP signature
