Date: Mon, 02 Apr 2018 20:47:10 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-bugs@FreeBSD.org Subject: [Bug 227213] FreeBSD 10.4 kernel deadlocks with i7-7700 / ASUS PRIME H270M-PLUS Message-ID: <bug-227213-8@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D227213 Bug ID: 227213 Summary: FreeBSD 10.4 kernel deadlocks with i7-7700 / ASUS PRIME H270M-PLUS Product: Base System Version: 10.4-STABLE Hardware: amd64 OS: Any Status: New Severity: Affects Only Me Priority: --- Component: kern Assignee: freebsd-bugs@FreeBSD.org Reporter: markk@knigma.org When upgrading kernel from FreeBSD FreeBSD 10.3-RELEASE-p28 to FreeBSD 10.4-RELEASE or FreeBSD 10.4-RELEASE-p7 various user land programs hang. Sa= me problem with 10.3 or 10.4 user land, so simply upgrading the kernel triggers the issue. For example, I cannot login as myself on the console, or if I login as root= and try to su or sudo myself, the tty hangs (CTRL-C usually does nothing, CTRL-T shows [sysctl mem], and I have to login via another virtual tty. Sadly ther= e's nothing appearing in /var/log/all.log when the deadlock occurs. Another command that causes a hang is "killall -HUP syslogd" when logged in= as root. For additional information, see the similarly titled thread on freebsd-stab= le. Kernel boot log: http://www.knigma.org/scratch/010418.10.4.txt I created the following kernel dump shortly after a normal boot (booting ha= sn't been affected so far), and then immediately trying to login as my normal us= er and hitting Ctr-Alt-ESC after the tty hung. CTRL-T showed [sysctl-mem]. Ker= nel dump created with "call doadump": http://www.knigma.org/scratch/core.txt.0 http://www.knigma.org/scratch/vmcore.0.gz http://www.knigma.org/scratch/kernel.debug.gz Motherboard is running the latest BIOS and system has been rock solid on 10= .3 for months. All advise/assistance appreciated - thank you :) --=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-227213-8>