Re: r315684 panic: sleepq_add: td 0xfffff80003c01a40 to sleep on wchan 0xfffff80006f0873c with sleeping prohibited
Darren, On Sat, Mar 25, 2017 at 03:03:14AM +0200, Konstantin Belousov wrote: K> On Fri, Mar 24, 2017 at 05:40:15PM +, Darren wrote: K> > I am getting this panic every hour to every couple of hours. K> > K> > FreeBSD asrock 12.0-CURRENT FreeBSD 12.0-CURRENT #0 r315684: Thu Mar 23 14:56:45 EDT 2017 darren@asrock:/usr/obj/usr/src/sys/GENERIC amd64 K> > I manually typed out the following, apologize for any typos. K> > K> > K> > panic: sleepq_add: td 0xf80003c01a40 to sleep on wchan 0xf80006f0873c with sleeping prohibited K> > cpuid = 0 K> > time = 1490372797 K> > KDB: stack backtrace: K> > db_trace_self_wrapper() at db_trace_self_wrapper+0x2b/frame 0xfe0072e33690 K> > vpanic() at vpanic+0x19c/frame 0xfe0072e33710 K> > kassert_panic() at kassert_panic+0x126/frame 0xfe0072e33780 K> > sleepq_add() at sleepq_add+0x34f/frame 0xfe0072337d0 K> > _sleep() at _sleep+0x28d/frame 0xfe0072e33870 K> > soclose() at soclose+0xda/frame 0xfe0072e338b0 K> > _fdrop() at _fdrop+0x1a/frame 0xfe0072e338d0 K> > sendfile_iodone() at sendfile_iodone+0x19d/frame 0xfe0072e33910 K> > vnode_pager_generic_getpages_done_async() at vnode_pager_generic_getpages_done_async+037/frame 0xfe0072e33930 K> > bufdone() at bufdone+0x64/frame 0xfe0072e33960 K> > g_io_deliver() at g_io_deliver+0x276/frame 0xfe0072e339b0 K> > g_io_deliver() at g_io_deliver+0x276/frame 0xfe0072e33a00 K> > g_disk_done() at g_disk_done+0x104/frame 0xfe0072e33a40 K> > xpt_done_process() at xpt_done_process+0x35f/frame 0xfe0072e33a80 K> > xpt_done_direct() at ahci_ch_intr_direct+0xd5/frame 0xfe0072e33af0 K> > ahci_itr() at ahci_intr+0x102/frame 0xfe0072e33b20 K> > intr_event_execute_handlers() at intr_event_execute_handlers+0x99/frame 0xfe0072e33b60 K> > ithread_loop() at ithread_loop+0xb6/frame 0xfe0072e33bb0 K> > fork_exit() at fork_exit+0x84/frame 0xfe0072e33bf0 K> > fork_trampoline() at fork_trampoline+0xe/frame 0xfe0072e33bf0 K> > --- trap 0, rip = 0, rsp = 0, rbp = 0 --- K> > KDB: enter: panic K> > [ thread pid 12 tid 100038 ] K> > Stopped at kdb_enter+0x3b: movq $0,kdb_why K> > db> K> K> Indeed, the context where sendfile_iodone() is executed, cannot call fdrop(). Can you please test the attached patch? -- Totus tuus, Glebius. Index: sys/kern/kern_sendfile.c === --- sys/kern/kern_sendfile.c (revision 315926) +++ sys/kern/kern_sendfile.c (working copy) @@ -296,8 +296,9 @@ sendfile_iodone(void *arg, vm_page_t *pg, int coun CURVNET_RESTORE(); } - /* XXXGL: curthread */ - fdrop(sfio->sock_fp, curthread); + ACCEPT_LOCK(); + SOCK_LOCK(so); + sorele(so); free(sfio, M_TEMP); } @@ -860,7 +861,9 @@ prepend_header: } else { sfio->sock_fp = sock_fp; sfio->npages = npages; - fhold(sock_fp); + SOCK_LOCK(so); + soref(so); + SOCK_UNLOCK(so); error = (*so->so_proto->pr_usrreqs->pru_send) (so, PRUS_NOTREADY, m, NULL, NULL, td); sendfile_iodone(sfio, NULL, 0, 0); ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: r315684 panic: sleepq_add: td 0xfffff80003c01a40 to sleep on wchan 0xfffff80006f0873c with sleeping prohibited
On Fri, Mar 24, 2017 at 05:40:15PM +, Darren wrote: > I am getting this panic every hour to every couple of hours. > > FreeBSD asrock 12.0-CURRENT FreeBSD 12.0-CURRENT #0 r315684: Thu Mar 23 > 14:56:45 EDT 2017 darren@asrock:/usr/obj/usr/src/sys/GENERIC amd64 > I manually typed out the following, apologize for any typos. > > > panic: sleepq_add: td 0xf80003c01a40 to sleep on wchan 0xf80006f0873c > with sleeping prohibited > cpuid = 0 > time = 1490372797 > KDB: stack backtrace: > db_trace_self_wrapper() at db_trace_self_wrapper+0x2b/frame 0xfe0072e33690 > vpanic() at vpanic+0x19c/frame 0xfe0072e33710 > kassert_panic() at kassert_panic+0x126/frame 0xfe0072e33780 > sleepq_add() at sleepq_add+0x34f/frame 0xfe0072337d0 > _sleep() at _sleep+0x28d/frame 0xfe0072e33870 > soclose() at soclose+0xda/frame 0xfe0072e338b0 > _fdrop() at _fdrop+0x1a/frame 0xfe0072e338d0 > sendfile_iodone() at sendfile_iodone+0x19d/frame 0xfe0072e33910 > vnode_pager_generic_getpages_done_async() at > vnode_pager_generic_getpages_done_async+037/frame 0xfe0072e33930 > bufdone() at bufdone+0x64/frame 0xfe0072e33960 > g_io_deliver() at g_io_deliver+0x276/frame 0xfe0072e339b0 > g_io_deliver() at g_io_deliver+0x276/frame 0xfe0072e33a00 > g_disk_done() at g_disk_done+0x104/frame 0xfe0072e33a40 > xpt_done_process() at xpt_done_process+0x35f/frame 0xfe0072e33a80 > xpt_done_direct() at ahci_ch_intr_direct+0xd5/frame 0xfe0072e33af0 > ahci_itr() at ahci_intr+0x102/frame 0xfe0072e33b20 > intr_event_execute_handlers() at intr_event_execute_handlers+0x99/frame > 0xfe0072e33b60 > ithread_loop() at ithread_loop+0xb6/frame 0xfe0072e33bb0 > fork_exit() at fork_exit+0x84/frame 0xfe0072e33bf0 > fork_trampoline() at fork_trampoline+0xe/frame 0xfe0072e33bf0 > --- trap 0, rip = 0, rsp = 0, rbp = 0 --- > KDB: enter: panic > [ thread pid 12 tid 100038 ] > Stopped at kdb_enter+0x3b: movq $0,kdb_why > db> Indeed, the context where sendfile_iodone() is executed, cannot call fdrop(). ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: process killed: text file modification
I can't do commits until I get home in mid-April. That's why it will be waiting until then. It should make it into stable/11 in plenty of time for 11.1. Thanks for your help with this, rick From: owner-freebsd-curr...@freebsd.org on behalf of Konstantin Belousov Sent: Friday, March 24, 2017 3:01:41 AM To: Rick Macklem Cc: Gergely Czuczy; Dimitry Andric; Ian Lepore; FreeBSD Current Subject: Re: process killed: text file modification On Thu, Mar 23, 2017 at 09:39:00PM +, Rick Macklem wrote: > Try whatever you like. However, if the case that failed before doesn't fail > now, > I'd call the test a success. > > Thanks, rick > ps: It looks like Kostik is going to work on converting the NFS > vop_putpages() to > using the buffer cache. However, if this isn't ready for head/current > by mid-April, > I will commit this patch to help fix things in the meantime. I do not see a reason to wait for my work before committing your patch. IMO, instead, it should be committed ASAP and merged into stable/11 for upcoming 11.1. I will do required adjustments if/when _putpages() patch progresses enough. ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org" ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: crash: umount_nfs: Current
Ok, thanks for testing it. Unless I hear of problems with the patch, I'll commit it to head in mid-April. Thanks again for reporting this and doing the testing, rick From: owner-freebsd-curr...@freebsd.org on behalf of Larry Rosenman Sent: Friday, March 24, 2017 11:21:39 AM To: Rick Macklem; freebsd...@freebsd.org Cc: freebsd-current@FreeBSD.org Subject: Re: crash: umount_nfs: Current I tried my test (umount –t nfs –a && mount –t nfs –a) and no crash. (with ~84G inact cached NFS data). I suspect it helped. -- Larry Rosenman http://www.lerctr.org/~ler Phone: +1 214-642-9640 E-Mail: l...@lerctr.org US Mail: 17716 Limpia Crk, Round Rock, TX 78664-7281 ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org" ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: r315684 panic: sleepq_add: td 0xfffff80003c01a40 to sleep on wchan 0xfffff80006f0873c with sleeping prohibited
On Fri, 24 Mar 2017 17:40:15 + (UTC), Darren wrote: > I am getting this panic every hour to every couple of hours. > > FreeBSD asrock 12.0-CURRENT FreeBSD 12.0-CURRENT #0 r315684: Thu Mar 23 > 14:56:45 EDT 2017 darren@asrock:/usr/obj/usr/src/sys/GENERIC amd64 > I manually typed out the following, apologize for any typos. > > > panic: sleepq_add: td 0xf80003c01a40 to sleep on wchan 0xf80006f0873c > with sleeping prohibited > cpuid = 0 > time = 1490372797 > KDB: stack backtrace: > db_trace_self_wrapper() at db_trace_self_wrapper+0x2b/frame 0xfe0072e33690 > vpanic() at vpanic+0x19c/frame 0xfe0072e33710 > kassert_panic() at kassert_panic+0x126/frame 0xfe0072e33780 > sleepq_add() at sleepq_add+0x34f/frame 0xfe0072337d0 > _sleep() at _sleep+0x28d/frame 0xfe0072e33870 > soclose() at soclose+0xda/frame 0xfe0072e338b0 > _fdrop() at _fdrop+0x1a/frame 0xfe0072e338d0 > sendfile_iodone() at sendfile_iodone+0x19d/frame 0xfe0072e33910 > vnode_pager_generic_getpages_done_async() at > vnode_pager_generic_getpages_done_async+037/frame 0xfe0072e33930 > bufdone() at bufdone+0x64/frame 0xfe0072e33960 > g_io_deliver() at g_io_deliver+0x276/frame 0xfe0072e339b0 > g_io_deliver() at g_io_deliver+0x276/frame 0xfe0072e33a00 > g_disk_done() at g_disk_done+0x104/frame 0xfe0072e33a40 > xpt_done_process() at xpt_done_process+0x35f/frame 0xfe0072e33a80 > xpt_done_direct() at ahci_ch_intr_direct+0xd5/frame 0xfe0072e33af0 > ahci_itr() at ahci_intr+0x102/frame 0xfe0072e33b20 > intr_event_execute_handlers() at intr_event_execute_handlers+0x99/frame > 0xfe0072e33b60 > ithread_loop() at ithread_loop+0xb6/frame 0xfe0072e33bb0 > fork_exit() at fork_exit+0x84/frame 0xfe0072e33bf0 > fork_trampoline() at fork_trampoline+0xe/frame 0xfe0072e33bf0 > --- trap 0, rip = 0, rsp = 0, rbp = 0 --- > KDB: enter: panic > [ thread pid 12 tid 100038 ] > Stopped at kdb_enter+0x3b: movq $0,kdb_why > db> > > > > ___ > freebsd-current@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org" Will there ever be an auto-save to .txt upon break to debugger or lock reversal or similar in code? or is beyond the capability of the OS once the occurance has taken place, I wonder. ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
r315684 panic: sleepq_add: td 0xfffff80003c01a40 to sleep on wchan 0xfffff80006f0873c with sleeping prohibited
I am getting this panic every hour to every couple of hours. FreeBSD asrock 12.0-CURRENT FreeBSD 12.0-CURRENT #0 r315684: Thu Mar 23 14:56:45 EDT 2017 darren@asrock:/usr/obj/usr/src/sys/GENERIC amd64 I manually typed out the following, apologize for any typos. panic: sleepq_add: td 0xf80003c01a40 to sleep on wchan 0xf80006f0873c with sleeping prohibited cpuid = 0 time = 1490372797 KDB: stack backtrace: db_trace_self_wrapper() at db_trace_self_wrapper+0x2b/frame 0xfe0072e33690 vpanic() at vpanic+0x19c/frame 0xfe0072e33710 kassert_panic() at kassert_panic+0x126/frame 0xfe0072e33780 sleepq_add() at sleepq_add+0x34f/frame 0xfe0072337d0 _sleep() at _sleep+0x28d/frame 0xfe0072e33870 soclose() at soclose+0xda/frame 0xfe0072e338b0 _fdrop() at _fdrop+0x1a/frame 0xfe0072e338d0 sendfile_iodone() at sendfile_iodone+0x19d/frame 0xfe0072e33910 vnode_pager_generic_getpages_done_async() at vnode_pager_generic_getpages_done_async+037/frame 0xfe0072e33930 bufdone() at bufdone+0x64/frame 0xfe0072e33960 g_io_deliver() at g_io_deliver+0x276/frame 0xfe0072e339b0 g_io_deliver() at g_io_deliver+0x276/frame 0xfe0072e33a00 g_disk_done() at g_disk_done+0x104/frame 0xfe0072e33a40 xpt_done_process() at xpt_done_process+0x35f/frame 0xfe0072e33a80 xpt_done_direct() at ahci_ch_intr_direct+0xd5/frame 0xfe0072e33af0 ahci_itr() at ahci_intr+0x102/frame 0xfe0072e33b20 intr_event_execute_handlers() at intr_event_execute_handlers+0x99/frame 0xfe0072e33b60 ithread_loop() at ithread_loop+0xb6/frame 0xfe0072e33bb0 fork_exit() at fork_exit+0x84/frame 0xfe0072e33bf0 fork_trampoline() at fork_trampoline+0xe/frame 0xfe0072e33bf0 --- trap 0, rip = 0, rsp = 0, rbp = 0 --- KDB: enter: panic [ thread pid 12 tid 100038 ] Stopped at kdb_enter+0x3b: movq $0,kdb_why db> ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: dchlient does not autostart anymore?
On Fri, Mar 24, 2017 at 10:53 AM, Vladimir Zakharov wrote: > On Fri, Mar 24, 2017, Jung-uk Kim wrote: >> On 03/24/2017 11:20, Kirill Ponomarev wrote: >> > On 03/24, Vladimir Zakharov wrote: >> >> Hello! >> >> >> >> After upgrading from r315544 to r315880 network interface doesn't get IP >> >> address using DHCP on boot anymore. >> >> >> >> $ grep re0 /etc/rc.conf | grep -v "^#" >> >> ifconfig_re0="DHCP" >> >> >> >> "service netif restart" doesn't help either. Only manual dhclient >> >> starting. >> > >> > Same issues here with today CURRENT, r315896. >> >> FYI, r315901 fixed the issue for me. > > For me too. Thanks. Yea, sorry about the brief breakage... I didn't notice until after I'd committed Ian's much improved version there'd been a problem. Stupid mistake on my part committing out of the wrong tree for the change that caused problems. Warner ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: r315900: /usr/bin/ssh: Undefined symbol "msetlocale"
Am Fri, 24 Mar 2017 15:28:31 +0100 Andreas Nilsson schrieb: > On Fri, Mar 24, 2017 at 2:37 PM, O. Hartmann wrote: > > > Having just updated CURRENT to CURRENT 12.0-CURRENT FreeBSD 12.0-CURRENT #1 > > r315900: Fri Mar 24 14:17:22 CET 2017 amd64, I can not connect to remote > > systems via ssh anymore: > > > > /usr/bin/ssh: Undefined symbol "msetlocale" > > > > Google suggests for this kind of error a miscompilation of the binary. > > > > I had a crash, again (SSDs and CURRENT have a serious problem!), had to > > improvise with the USB flash ISO image of CURRENT found on FreeBSD.org from > > 23.03.2017, ~ 18 o'clock, but have rebuilt and installed world and kernel > > from a > > clean /usr/obj two times. Still being bugged by this mysterious error. > > > > Can somebody help, please? > > > > Thanks in advance, > > Oliver > > ___ > > freebsd-current@freebsd.org mailing list > > https://lists.freebsd.org/mailman/listinfo/freebsd-current > > To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org" > > > > > I haven't upgraded myself yet, but I fetched the sources. > > Could you check ldd /usr/bin/ssh ? > If you have libprivatessh in there, could you do nm -D > /usr/lib/libprivatessh.so | grep msetlocale and see if you get any output ( > I think you should get one line ) > > Otherwise it would seem that either libprivatessh is not built correctly or > that it is not installed correctly. But these are just my guesses. > > Best regards > Andreas > ___ I'm in the office on Monday and I'll check this. I have just updated and built world on servers in my lab and homeoffice and I do not face this strange error on the servers there, it's r315905 here, if this matters ... Kind regards, oh -- O. Hartmann Ich widerspreche der Nutzung oder Übermittlung meiner Daten für Werbezwecke oder für die Markt- oder Meinungsforschung (§ 28 Abs. 4 BDSG). pgpgArb03xGk4.pgp Description: OpenPGP digital signature
Re: dchlient does not autostart anymore?
On Fri, Mar 24, 2017, Jung-uk Kim wrote: > On 03/24/2017 11:20, Kirill Ponomarev wrote: > > On 03/24, Vladimir Zakharov wrote: > >> Hello! > >> > >> After upgrading from r315544 to r315880 network interface doesn't get IP > >> address using DHCP on boot anymore. > >> > >> $ grep re0 /etc/rc.conf | grep -v "^#" > >> ifconfig_re0="DHCP" > >> > >> "service netif restart" doesn't help either. Only manual dhclient > >> starting. > > > > Same issues here with today CURRENT, r315896. > > FYI, r315901 fixed the issue for me. For me too. Thanks. -- Regards, | "In theory there is no difference between theory Vladimir Zakharov | and practice. In practice there is."- Yogi Berra ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: dchlient does not autostart anymore?
On 03/24, Vladimir Zakharov wrote: > Hello! > > After upgrading from r315544 to r315880 network interface doesn't get IP > address using DHCP on boot anymore. > > $ grep re0 /etc/rc.conf | grep -v "^#" > ifconfig_re0="DHCP" > > "service netif restart" doesn't help either. Only manual dhclient > starting. Same issues here with today CURRENT, r315896. K. signature.asc Description: PGP signature
Re: dchlient does not autostart anymore?
On 03/24/2017 11:20, Kirill Ponomarev wrote: > On 03/24, Vladimir Zakharov wrote: >> Hello! >> >> After upgrading from r315544 to r315880 network interface doesn't get IP >> address using DHCP on boot anymore. >> >> $ grep re0 /etc/rc.conf | grep -v "^#" >> ifconfig_re0="DHCP" >> >> "service netif restart" doesn't help either. Only manual dhclient >> starting. > > Same issues here with today CURRENT, r315896. FYI, r315901 fixed the issue for me. Jung-uk Kim signature.asc Description: OpenPGP digital signature
Re: crash: umount_nfs: Current
I tried my test (umount –t nfs –a && mount –t nfs –a) and no crash. (with ~84G inact cached NFS data). I suspect it helped. -- Larry Rosenman http://www.lerctr.org/~ler Phone: +1 214-642-9640 E-Mail: l...@lerctr.org US Mail: 17716 Limpia Crk, Round Rock, TX 78664-7281 ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: dchlient does not autostart anymore?
On 03/24, Vladimir Zakharov wrote: > Hello! > > After upgrading from r315544 to r315880 network interface doesn't get IP > address using DHCP on boot anymore. > > $ grep re0 /etc/rc.conf | grep -v "^#" > ifconfig_re0="DHCP" > > "service netif restart" doesn't help either. Only manual dhclient > starting. Same issues here with today CURRENT, r315896. K. signature.asc Description: PGP signature
Re: r315900: /usr/bin/ssh: Undefined symbol "msetlocale"
On Fri, Mar 24, 2017 at 2:37 PM, O. Hartmann wrote: > Having just updated CURRENT to CURRENT 12.0-CURRENT FreeBSD 12.0-CURRENT #1 > r315900: Fri Mar 24 14:17:22 CET 2017 amd64, I can not connect to remote > systems via ssh anymore: > > /usr/bin/ssh: Undefined symbol "msetlocale" > > Google suggests for this kind of error a miscompilation of the binary. > > I had a crash, again (SSDs and CURRENT have a serious problem!), had to > improvise with the USB flash ISO image of CURRENT found on FreeBSD.org from > 23.03.2017, ~ 18 o'clock, but have rebuilt and installed world and kernel > from a > clean /usr/obj two times. Still being bugged by this mysterious error. > > Can somebody help, please? > > Thanks in advance, > Oliver > ___ > freebsd-current@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org" > I haven't upgraded myself yet, but I fetched the sources. Could you check ldd /usr/bin/ssh ? If you have libprivatessh in there, could you do nm -D /usr/lib/libprivatessh.so | grep msetlocale and see if you get any output ( I think you should get one line ) Otherwise it would seem that either libprivatessh is not built correctly or that it is not installed correctly. But these are just my guesses. Best regards Andreas ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: dchlient does not autostart anymore?
On Fri, Mar 24, 2017 at 01:56:38AM -0700, Mark Millard wrote: > Vladimir Zakharov zakharov.vv at gmail.com wrote on Fri Mar 24 08:20:34 UTC > 2017: > > > After upgrading from r315544 to r315880 network interface doesn't get IP > > address using DHCP on boot anymore. > > > > $ grep re0 /etc/rc.conf | grep -v "^#" > > ifconfig_re0="DHCP" > > > > "service netif restart" doesn't help either. Only manual dhclient > > starting. > > I have just updated two contexts to -r315870 just a bit ago > and they both got that behavior as well: > > A) An amd64 context (FreeBSD client in VirtualBox under macOS) > B) An arm64 context (pine64+ 2GB with -mcpu=cortex-a53 ) > > Later I'll be updating powerpc64, powerpc, and armv6 (with > -mcpu=cortex-a7 ) contexts but I'd expect they will all match > the behavior. > > (I started from earlier than -r315544 so your report provides > a better lower bound -r315544. I ended earlier and so my > report provides a better upper bound -r315870.) > Well, I just updated my (amd64) laptop from: FreeBSD g1-252.catwhisker.org 12.0-CURRENT FreeBSD 12.0-CURRENT #293 r315853M/315854:1200027: Thu Mar 23 06:41:30 PDT 2017 r...@g1-252.catwhisker.org:/common/S4/obj/usr/src/sys/CANARY amd64 to: FreeBSD g1-252.catwhisker.org 12.0-CURRENT FreeBSD 12.0-CURRENT #294 r315896M/315899:1200027: Fri Mar 24 06:36:28 PDT 2017 r...@g1-252.catwhisker.org:/common/S4/obj/usr/src/sys/CANARY amd64 ... and had no issues (with dhclient, mouse, or anything else). Peace, david -- David H. Wolfskill da...@catwhisker.org Who would have thought that a "hotelier" would be so ... unwelcoming? Sad. See http://www.catwhisker.org/~david/publickey.gpg for my public key. signature.asc Description: PGP signature
Re: dchlient does not autostart anymore?
M&S - Krasznai András wrote on 03/24/2017 14:14: It seems that usb mouse port has been changed from /dev/psm0 to /dev/ums0; loading ums.ko with kldload and restarting the mouse with moused -p /dev/ums0 makes the mouse work again (but now the touchpad is not working; I can survive that). rgds András Krasznai I did kldload ums; service devd restart; dhclient wlan0 to solve both the problems. Btw, both mouse and touchpad are working. Thank you for the temporary solution! -- Regards, Ruslan T.O.S. Of Reality ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
r315900: /usr/bin/ssh: Undefined symbol "msetlocale"
Having just updated CURRENT to CURRENT 12.0-CURRENT FreeBSD 12.0-CURRENT #1 r315900: Fri Mar 24 14:17:22 CET 2017 amd64, I can not connect to remote systems via ssh anymore: /usr/bin/ssh: Undefined symbol "msetlocale" Google suggests for this kind of error a miscompilation of the binary. I had a crash, again (SSDs and CURRENT have a serious problem!), had to improvise with the USB flash ISO image of CURRENT found on FreeBSD.org from 23.03.2017, ~ 18 o'clock, but have rebuilt and installed world and kernel from a clean /usr/obj two times. Still being bugged by this mysterious error. Can somebody help, please? Thanks in advance, Oliver ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: dchlient does not autostart anymore?
+1 Need to manualy kldload ums.ko and start dhclient. 24.03.2017 12:38, Lev Serebryakov пишет: On 24.03.2017 12:28, M&S - Krasznai András wrote: devd problems? Now dhclient and moused are started by devd. Hi, FreeBSD-current, r315895 also experiences the same problem. The problem started after updating my laptop yesterday morning. I can get an IP address after manually starting dhclient. I have an additional anomaly: the USB mouse does not work (touchpad works) on a Lenovo T510 laptop. dmesg shows the correct vendor and type for the mouse. rgds András Krasznai -Eredeti üzenet- Feladó: owner-freebsd-curr...@freebsd.org [mailto:owner-freebsd-curr...@freebsd.org] Meghatalmazó Mark Millard Küldve: 2017. március 24. 9:57 Címzett: zakharov...@gmail.com; FreeBSD Current Tárgy: Re: dchlient does not autostart anymore? Vladimir Zakharov zakharov.vv at gmail.com wrote on Fri Mar 24 08:20:34 UTC 2017: After upgrading from r315544 to r315880 network interface doesn't get IP address using DHCP on boot anymore. $ grep re0 /etc/rc.conf | grep -v "^#" ifconfig_re0="DHCP" "service netif restart" doesn't help either. Only manual dhclient starting. I have just updated two contexts to -r315870 just a bit ago and they both got that behavior as well: A) An amd64 context (FreeBSD client in VirtualBox under macOS) B) An arm64 context (pine64+ 2GB with -mcpu=cortex-a53 ) Later I'll be updating powerpc64, powerpc, and armv6 (with -mcpu=cortex-a7 ) contexts but I'd expect they will all match the behavior. (I started from earlier than -r315544 so your report provides a better lower bound -r315544. I ended earlier and so my report provides a better upper bound -r315870.) === Mark Millard markmi at dsl-only.net ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org" ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org" -- ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: alloc/free abort/kill in 12 snapshot
Forgot to post the console message when application crashed: Most times : jemalloc_arena.c:353: Failed assertion: "p[i] == 0" Some times : jemalloc_arena.c:1648: Failed assertion: "pageind + npages <= chunk_npages" On Thursday, March 23, 2017 9:15 PM, Jin Guojun wrote: A X11 based program works fine on 11 and all previous FreeBSD release and Linux.When build on FreeBSD-12.0-CURRENT-amd64-20170316-r315413, it gets weird crashes on either alloc and free.Both cases seem related to _pthread_mutex_init_calloc_cb ().Is this a known issue? Is possible to determine why _pthread_mutex_init_calloc_cb () not happy? -Jin 1) calloc#0 0x00080134322a in thr_kill () from /lib/libc.so.7 #1 0x0008013431f4 in raise () from /lib/libc.so.7 #2 0x000801343169 in abort () from /lib/libc.so.7 #3 0x00080133ae1f in _pthread_mutex_init_calloc_cb () from /lib/libc.so.7 #4 0x000801333b99 in _pthread_mutex_init_calloc_cb () from /lib/libc.so.7 #5 0x000801333851 in _pthread_mutex_init_calloc_cb () from /lib/libc.so.7 #6 0x000801315e0d in _malloc_thread_cleanup () from /lib/libc.so.7 #7 0x00080133e35a in malloc () from /lib/libc.so.7 #8 0x00080133e8b1 in calloc () from /lib/libc.so.7 #9 0x000800b9ad41 in _XkbReadGetMapReply () from /usr/local/lib/libX11.so.6 #10 0x000800b9ba1a in XkbGetUpdatedMap () from /usr/local/lib/libX11.so.6 #11 0x000800b9babb in XkbGetMap () from /usr/local/lib/libX11.so.6 #12 0x000800b9837b in XkbKeycodeToKeysym () from /usr/local/lib/libX11.so.6 #13 0x000800b98ac3 in XkbLookupKeySym () from /usr/local/lib/libX11.so.6 #14 0x000800b994d4 in XLookupString () from /usr/local/lib/libX11.so.6 #15 0x00406a12 in update_pic (movie=0, movie_frams_sec=0, case KeyPress: { char string[256]; KeySym keysym; XComposeStatus stat; x_bool shifted_key; int handled_key = keysym, length = XLookupString(&event, string, sizeof(string) - 1, &keysym, &stat); ... }This happens when some key pressed (likely a CTRL key). This function is doing input, so issue should not be in the caller. 2) freeWhen exit the application, it crah on free:#0 0x00080134322a in thr_kill () from /lib/libc.so.7 #1 0x0008013431f4 in raise () from /lib/libc.so.7 #2 0x000801343169 in abort () from /lib/libc.so.7 #3 0x000801333198 in _pthread_mutex_init_calloc_cb () from /lib/libc.so.7 #4 0x0008013321ab in _pthread_mutex_init_calloc_cb () from /lib/libc.so.7 #5 0x0008013316fd in _pthread_mutex_init_calloc_cb () from /lib/libc.so.7 #6 0x00080132350d in _pthread_mutex_init_calloc_cb () from /lib/libc.so.7 #7 0x00080133ee10 in free () from /lib/libc.so.7 #8 0x0045d67b in ccs_free (p=0x80320) at zalloc.c:294 ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
alloc/free abort/kill in 12 snapshot
A X11 based program works fine on 11 and all previous FreeBSD release and Linux.When build on FreeBSD-12.0-CURRENT-amd64-20170316-r315413, it gets weird crashes on either alloc and free.Both cases seem related to _pthread_mutex_init_calloc_cb ().Is this a known issue? Is possible to determine why _pthread_mutex_init_calloc_cb () not happy? -Jin 1) calloc#0 0x00080134322a in thr_kill () from /lib/libc.so.7 #1 0x0008013431f4 in raise () from /lib/libc.so.7 #2 0x000801343169 in abort () from /lib/libc.so.7 #3 0x00080133ae1f in _pthread_mutex_init_calloc_cb () from /lib/libc.so.7 #4 0x000801333b99 in _pthread_mutex_init_calloc_cb () from /lib/libc.so.7 #5 0x000801333851 in _pthread_mutex_init_calloc_cb () from /lib/libc.so.7 #6 0x000801315e0d in _malloc_thread_cleanup () from /lib/libc.so.7 #7 0x00080133e35a in malloc () from /lib/libc.so.7 #8 0x00080133e8b1 in calloc () from /lib/libc.so.7 #9 0x000800b9ad41 in _XkbReadGetMapReply () from /usr/local/lib/libX11.so.6 #10 0x000800b9ba1a in XkbGetUpdatedMap () from /usr/local/lib/libX11.so.6 #11 0x000800b9babb in XkbGetMap () from /usr/local/lib/libX11.so.6 #12 0x000800b9837b in XkbKeycodeToKeysym () from /usr/local/lib/libX11.so.6 #13 0x000800b98ac3 in XkbLookupKeySym () from /usr/local/lib/libX11.so.6 #14 0x000800b994d4 in XLookupString () from /usr/local/lib/libX11.so.6 #15 0x00406a12 in update_pic (movie=0, movie_frams_sec=0, case KeyPress: { char string[256]; KeySym keysym; XComposeStatus stat; x_bool shifted_key; int handled_key = keysym, length = XLookupString(&event, string, sizeof(string) - 1, &keysym, &stat); ... }This happens when some key pressed (likely a CTRL key). This function is doing input, so issue should not be in the caller. 2) freeWhen exit the application, it crah on free:#0 0x00080134322a in thr_kill () from /lib/libc.so.7 #1 0x0008013431f4 in raise () from /lib/libc.so.7 #2 0x000801343169 in abort () from /lib/libc.so.7 #3 0x000801333198 in _pthread_mutex_init_calloc_cb () from /lib/libc.so.7 #4 0x0008013321ab in _pthread_mutex_init_calloc_cb () from /lib/libc.so.7 #5 0x0008013316fd in _pthread_mutex_init_calloc_cb () from /lib/libc.so.7 #6 0x00080132350d in _pthread_mutex_init_calloc_cb () from /lib/libc.so.7 #7 0x00080133ee10 in free () from /lib/libc.so.7 #8 0x0045d67b in ccs_free (p=0x80320) at zalloc.c:294 ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
RE: dchlient does not autostart anymore?
It seems that usb mouse port has been changed from /dev/psm0 to /dev/ums0; loading ums.ko with kldload and restarting the mouse with moused -p /dev/ums0 makes the mouse work again (but now the touchpad is not working; I can survive that). rgds András Krasznai -Eredeti üzenet- Feladó: Ruslan Makhmatkhanov [mailto:r...@freebsd.org] Küldve: 2017. március 24. 12:04 Címzett: FreeBSD Current Másolatot kap: M&S - Krasznai András Tárgy: Re: dchlient does not autostart anymore? The same for me (usb mouse + dhclient) on r315874. Touchpad is working. -- Regards, Ruslan T.O.S. Of Reality ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: dchlient does not autostart anymore?
The same for me (usb mouse + dhclient) on r315874. Touchpad is working. -- Regards, Ruslan T.O.S. Of Reality ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: dchlient does not autostart anymore?
On 24.03.2017 12:28, M&S - Krasznai András wrote: devd problems? Now dhclient and moused are started by devd. > Hi, > > FreeBSD-current, r315895 also experiences the same problem. The problem > started after updating my laptop yesterday morning. I can get an IP address > after manually starting dhclient. > > I have an additional anomaly: the USB mouse does not work (touchpad works) on > a Lenovo T510 laptop. dmesg shows the correct vendor and type for the mouse. > > rgds > > András Krasznai > > > > -Eredeti üzenet- > Feladó: owner-freebsd-curr...@freebsd.org > [mailto:owner-freebsd-curr...@freebsd.org] Meghatalmazó Mark Millard > Küldve: 2017. március 24. 9:57 > Címzett: zakharov...@gmail.com; FreeBSD Current > Tárgy: Re: dchlient does not autostart anymore? > > Vladimir Zakharov zakharov.vv at gmail.com wrote on Fri Mar 24 08:20:34 UTC > 2017: > >> After upgrading from r315544 to r315880 network interface doesn't get >> IP address using DHCP on boot anymore. >> >> $ grep re0 /etc/rc.conf | grep -v "^#" >> ifconfig_re0="DHCP" >> >> "service netif restart" doesn't help either. Only manual dhclient >> starting. > > I have just updated two contexts to -r315870 just a bit ago and they both got > that behavior as well: > > A) An amd64 context (FreeBSD client in VirtualBox under macOS) > B) An arm64 context (pine64+ 2GB with -mcpu=cortex-a53 ) > > Later I'll be updating powerpc64, powerpc, and armv6 (with > -mcpu=cortex-a7 ) contexts but I'd expect they will all match the behavior. > > (I started from earlier than -r315544 so your report provides a better lower > bound -r315544. I ended earlier and so my report provides a better upper > bound -r315870.) > > === > Mark Millard > markmi at dsl-only.net > > ___ > freebsd-current@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org" > ___ > freebsd-current@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org" > -- // Lev Serebryakov ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
RE: dchlient does not autostart anymore?
Hi, FreeBSD-current, r315895 also experiences the same problem. The problem started after updating my laptop yesterday morning. I can get an IP address after manually starting dhclient. I have an additional anomaly: the USB mouse does not work (touchpad works) on a Lenovo T510 laptop. dmesg shows the correct vendor and type for the mouse. rgds András Krasznai -Eredeti üzenet- Feladó: owner-freebsd-curr...@freebsd.org [mailto:owner-freebsd-curr...@freebsd.org] Meghatalmazó Mark Millard Küldve: 2017. március 24. 9:57 Címzett: zakharov...@gmail.com; FreeBSD Current Tárgy: Re: dchlient does not autostart anymore? Vladimir Zakharov zakharov.vv at gmail.com wrote on Fri Mar 24 08:20:34 UTC 2017: > After upgrading from r315544 to r315880 network interface doesn't get > IP address using DHCP on boot anymore. > > $ grep re0 /etc/rc.conf | grep -v "^#" > ifconfig_re0="DHCP" > > "service netif restart" doesn't help either. Only manual dhclient > starting. I have just updated two contexts to -r315870 just a bit ago and they both got that behavior as well: A) An amd64 context (FreeBSD client in VirtualBox under macOS) B) An arm64 context (pine64+ 2GB with -mcpu=cortex-a53 ) Later I'll be updating powerpc64, powerpc, and armv6 (with -mcpu=cortex-a7 ) contexts but I'd expect they will all match the behavior. (I started from earlier than -r315544 so your report provides a better lower bound -r315544. I ended earlier and so my report provides a better upper bound -r315870.) === Mark Millard markmi at dsl-only.net ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org" ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: dchlient does not autostart anymore?
Vladimir Zakharov zakharov.vv at gmail.com wrote on Fri Mar 24 08:20:34 UTC 2017: > After upgrading from r315544 to r315880 network interface doesn't get IP > address using DHCP on boot anymore. > > $ grep re0 /etc/rc.conf | grep -v "^#" > ifconfig_re0="DHCP" > > "service netif restart" doesn't help either. Only manual dhclient > starting. I have just updated two contexts to -r315870 just a bit ago and they both got that behavior as well: A) An amd64 context (FreeBSD client in VirtualBox under macOS) B) An arm64 context (pine64+ 2GB with -mcpu=cortex-a53 ) Later I'll be updating powerpc64, powerpc, and armv6 (with -mcpu=cortex-a7 ) contexts but I'd expect they will all match the behavior. (I started from earlier than -r315544 so your report provides a better lower bound -r315544. I ended earlier and so my report provides a better upper bound -r315870.) === Mark Millard markmi at dsl-only.net ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
dchlient does not autostart anymore?
Hello! After upgrading from r315544 to r315880 network interface doesn't get IP address using DHCP on boot anymore. $ grep re0 /etc/rc.conf | grep -v "^#" ifconfig_re0="DHCP" "service netif restart" doesn't help either. Only manual dhclient starting. -- Regards, | "In theory there is no difference between theory Vladimir Zakharov | and practice. In practice there is."- Yogi Berra ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: process killed: text file modification
On Thu, Mar 23, 2017 at 09:39:00PM +, Rick Macklem wrote: > Try whatever you like. However, if the case that failed before doesn't fail > now, > I'd call the test a success. > > Thanks, rick > ps: It looks like Kostik is going to work on converting the NFS > vop_putpages() to > using the buffer cache. However, if this isn't ready for head/current > by mid-April, > I will commit this patch to help fix things in the meantime. I do not see a reason to wait for my work before committing your patch. IMO, instead, it should be committed ASAP and merged into stable/11 for upcoming 11.1. I will do required adjustments if/when _putpages() patch progresses enough. ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"