From owner-freebsd-bugs@freebsd.org Wed Sep 23 23:19:14 2020 Return-Path: Delivered-To: freebsd-bugs@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 8CFDF3E197E for ; Wed, 23 Sep 2020 23:19:14 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mailman.nyi.freebsd.org (unknown [127.0.1.3]) by mx1.freebsd.org (Postfix) with ESMTP id 4BxYz63CLHz4W7L for ; Wed, 23 Sep 2020 23:19:14 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.nyi.freebsd.org (Postfix) id 6E11C3E1A74; Wed, 23 Sep 2020 23:19:14 +0000 (UTC) Delivered-To: bugs@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 6DD873E1A73 for ; Wed, 23 Sep 2020 23:19:14 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.nyi.freebsd.org (mxrelay.nyi.freebsd.org [IPv6:2610:1c1:1:606c::19:3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.nyi.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4BxYz62NkMz4W4n for ; Wed, 23 Sep 2020 23:19:14 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2610:1c1:1:606c::50:1d]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id 36E9818991 for ; Wed, 23 Sep 2020 23:19:14 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.5]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id 08NNJEdI018610 for ; Wed, 23 Sep 2020 23:19:14 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id 08NNJEvO018609 for bugs@FreeBSD.org; Wed, 23 Sep 2020 23:19:14 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 248659] random system freezes Date: Wed, 23 Sep 2020 23:19:13 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: CURRENT X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: rkoberman@gmail.com X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: bugs@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.33 Precedence: list List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 23 Sep 2020 23:19:14 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D248659 --- Comment #6 from rkoberman@gmail.com --- I had an epiphany yesterday and may have figured something that may help tr= ack this down. It appears that this is likely tied to the system disk which is = an ATAPI (SATA) drive. I can keep the system from freezing indefinitely by either typing or moving= the cursor. I realized that these two devices (kbd and psm) are , to the best o= f my knowledge, the last physical devices still GIANT locked ad the last ISA devices, as well. It is my suspicion that the GIANT lock happening now and = then causes something to clear out that will eventually livelock the system. I previously noted that the disk transfer rate would deteriorate over time, leading to a livelock. I can now report that, if I see the transfer rate declining, I can suspend the job and, after a few seconds, the system retur= ns to normal. If I let the problem continue for more than a few seconds, the keyboard will be locked up and the system will be livelocked and require a power down. I am unable to un-tar teh firefox source tarball or any other large tarball. Even with typing or moving the mouse, the transfer rate will start declinin= g. I can suspend tat, but it sems to start declining again very soon whne the ta= r is resumed and I was unable to complete the restore. I have seen similar behav= ior with other large tarballs. Oddly, when copying from USB disk to system disk= , I see similar issues, but a suspend seems to allow then to return to full spe= ed for a while upon resume. Copies on the system disk to the system disk seem = to be the worst problem. It also appears that an inactive system usually does not lock up. I can boo= t to the single-user or the login prompt and the system will remain usable for a long time. It does seem to eventually lock up, but it can take hours. It h= ad never locked until I left it at the single-user prompt after it finished fscking the system. When I get back to the system today, after about 13 hou= rs, it was frozen. Any suggestions on tracking this down would really be appreciated as this system is replacing an old one which has a failing fan and may become usele= ss at any time. --=20 You are receiving this mail because: You are the assignee for the bug.=