Date: Tue, 13 Aug 2019 15:59:45 +0000 From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 239822] deadlock Message-ID: <bug-239822-227@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D239822 Bug ID: 239822 Summary: deadlock Product: Base System Version: 12.0-RELEASE Hardware: Any OS: Any Status: New Severity: Affects Only Me Priority: --- Component: kern Assignee: bugs@FreeBSD.org Reporter: d8zNeCFG@aon.at Scenario: - FreeBSD releng/12.0 updated via SVN - recompiled (using -DNO_CLEAN) after FreeBSD-EN-19:14.epoch - Running on 3 machines - I have not recompiled the following ports with files in /boot/modules: . Machine 1: intel-em-kmod-7.7.5, nvidia-driver-390.87_3, virtualbox-ose-kmod-5.2.32_1 . Machine 2: drm-fbsd12.0-kmod-4.16.g20190722_1, gpu-firmware-kmod-g20190= 620, virtualbox-ose-kmod-5.2.32_1 - uname -a: FreeBSD hal.xyzzy 12.0-RELEASE-p9 FreeBSD 12.0-RELEASE-p9 #9 r350677M: Wed Aug 7 18:35:55 CEST 2019=20=20=20=20 root@v908.xyzzy:/.../hal/z/OBJ/FreeBSD/amd64/releng/12.0/amd64.amd64/sys/XY= ZZY_SMP amd64 Result: - On two of the three machines I have now experienced something which seems like a livelock: Some processes are stuck, others still progress and can be terminated (e.g., EOF in shells). - Rebooting the machines never succeeds completely: At some point there is = no progress anymore and the machines have to be hard reset. - In the first livelock, two tabs of Firefox seemed to be "stuck" against e= ach other; 100% CPU was used (1 out of 4 cores). - In the second livelock, VirtualBox (VBoxHeadless) was spinning at 100% (1= out of 4 cores), and a running svn command was stuck. I have the impression that this started with -p9. Before, I mostly got pani= cs with immediate reboots (no kernel dumps although configured; see bug report #235865). -- Martin --=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-239822-227>