Date: Sun, 31 Jan 2021 10:35:10 +0100 From: "Hartmann, O." <ohartmann@walstatt.org> To: FreeBSD CURRENT <freebsd-current@freebsd.org> Cc: Guido Falsi <mad@madpilot.net>, junchoon@dec.sakura.ne.jp Subject: Re: (n244517-f17fc5439f5) svn stuck forever in /usr/ports? Message-ID: <20210131103510.30d9a322@hermann.fritz.box> In-Reply-To: <a5e18e3b-181c-c094-b98c-7e233cdac972@madpilot.net> References: <20210130073923.0b2a80c1@hermann.fritz.box> <20210130192520.e7cf7f680c0abd31b0771107@dec.sakura.ne.jp> <18e15d74-d95b-76b7-59a4-64a8f338ba73@madpilot.net> <a5e18e3b-181c-c094-b98c-7e233cdac972@madpilot.net>
next in thread | previous in thread | raw e-mail | index | archive | help
--Sig_/f_0J0jL1_ODKwjVqN1H1_9F Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable On Sat, 30 Jan 2021 16:22:50 +0100 Guido Falsi via freebsd-current <freebsd-current@freebsd.org> wrote: > On 30/01/21 12:34, Guido Falsi via freebsd-current wrote: > > On 30/01/21 11:25, Tomoaki AOKI wrote: =20 > >> On Sat, 30 Jan 2021 07:39:23 +0100 > >> "Hartmann, O." <ohartmann@walstatt.org> wrote: > >> =20 > >>> We recently updated to FreeBSD 14.0-CURRENT #9=20 > >>> main-n244517-f17fc5439f5: Fri Jan 29 > >>> 16:29:50 CET 2021=C2=A0 amd64. After make delete-oldfiles/delete-old-= libs,=20 > >>> the command > >>> > >>> make update > >>> > >>> issued in /usr/ports on those 14-CURRENT boxes remains stuck forever= =20 > >>> or it is working > >>> like a snail! > >>> Hitting Ctrl-t on the console gives: > >>> > >>> load: 0.06=C2=A0 cmd: svn 96552 [kqread] 2530.57r 270.92u 5.68s 10% 1= 0584k > >>> mi_switch+0xbe sleepq_catch_signals+0x324 sleepq_timedwait_sig+0x12=20 > >>> _sleep+0x188 > >>> kqueue_kevent+0x2d0 kern_kevent_fp+0x51 kern_kevent_generic+0xdd=20 > >>> sys_kevent+0x61 > >>> amd64_syscall+0x10c fast_syscall_common+0xf8 make: Working in:=20 > >>> /usr/ports > >>> > >>> > >>> The system is idle otherwise. > >>> > >>> How can this be resolved? Is this phenomenon known? > >>> > >>> Kind regards and thank you very much in advance, > >>> > >>> O. Hartmann > >>> =20 > >> > >> +1. > >> IIRC, d6327ae8c11b was OK, but ebc61c86b556 is not. > >> > >> Unfortunately, I currently don't have enough time to bisect > >> further. :-( =20 > >=20 > > I'm running 07d218f70c2f and it is affected, this restricts the range=20 > > slightly more. > > =20 >=20 > I tried bisecting the kernel only between d6327ae8c11b and 07d218f70c2f,= =20 > but got no results. >=20 > Looks like the problem is not in the kernel but somewhere else (libc? ssl= ?) >=20 > Bisecting the whole system is going to take longer. I'll try to find the= =20 > time. >=20 We also have running a 14-CURRENT-based webserver with www/apach24. After u= pgrading from an earlier (working) 14-CURRENT (FreeBSD 14.0-CURRENT #40 main-c256208-geb6= 1de5b787: Fri Jan 22 16:28:09 CET 2021 amd64), the reported phenomenon took place. I also= have to admit that after main-c256208-geb61de5b787, the whole system has been rebuilt fr= om a clean /usr/src (otherwise we use -DNO_CLEAN or its WITHOUT_CLEAN equivalent). Hopefully that helps. Kind regards, oh --Sig_/f_0J0jL1_ODKwjVqN1H1_9F Content-Type: application/pgp-signature Content-Description: OpenPGP digital signature -----BEGIN PGP SIGNATURE----- iHUEARYIAB0WIQSy8IBxAPDkqVBaTJ44N1ZZPba5RwUCYBZ5zgAKCRA4N1ZZPba5 R3xZAP0f3L4wzc0bBfQqa3vZKpbYeVE+NuL8IKpwmRQMflYt1AEAp2Am4jJ5hXg0 GzpNVdzpg1z/yyhRzgjc1WqvRDGntQk= =vhjK -----END PGP SIGNATURE----- --Sig_/f_0J0jL1_ODKwjVqN1H1_9F--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20210131103510.30d9a322>