Date: Wed, 23 Sep 2020 23:19:13 +0000 From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 248659] random system freezes Message-ID: <bug-248659-227-qxBt8EAkK3@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-248659-227@https.bugs.freebsd.org/bugzilla/> References: <bug-248659-227@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
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.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-248659-227-qxBt8EAkK3>