From owner-freebsd-virtualization@freebsd.org Fri Aug 23 04:55:43 2019 Return-Path: Delivered-To: freebsd-virtualization@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 4F464DA426 for ; Fri, 23 Aug 2019 04:55:43 +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 46F8H31RX6z4JQj for ; Fri, 23 Aug 2019 04:55:43 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.nyi.freebsd.org (Postfix) id 2F59ADA425; Fri, 23 Aug 2019 04:55:43 +0000 (UTC) Delivered-To: virtualization@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 2DED1DA424 for ; Fri, 23 Aug 2019 04:55:43 +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) server-signature RSA-PSS (4096 bits) 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 46F8H30FWXz4JQh for ; Fri, 23 Aug 2019 04:55:43 +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.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id DA3A8F7F5 for ; Fri, 23 Aug 2019 04:55:42 +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 x7N4tgrm041727 for ; Fri, 23 Aug 2019 04:55:42 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id x7N4tg0K041726 for virtualization@FreeBSD.org; Fri, 23 Aug 2019 04:55:42 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: virtualization@FreeBSD.org Subject: [Bug 240050] Keyboard Function Lost Post Kernel Intense Swapping after Application Process Killed by Kernel Date: Fri, 23 Aug 2019 04:55:41 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: bhyve X-Bugzilla-Version: 11.3-STABLE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: jlmales@gmail.com X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: virtualization@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_id short_desc product version rep_platform op_sys bug_status bug_severity priority component assigned_to reporter attachments.created Message-ID: 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-virtualization@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Discussion of various virtualization techniques FreeBSD supports." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 23 Aug 2019 04:55:43 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D240050 Bug ID: 240050 Summary: Keyboard Function Lost Post Kernel Intense Swapping after Application Process Killed by Kernel Product: Base System Version: 11.3-STABLE Hardware: amd64 OS: Any Status: New Severity: Affects Some People Priority: --- Component: bhyve Assignee: virtualization@FreeBSD.org Reporter: jlmales@gmail.com Created attachment 206810 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=3D206810&action= =3Dedit Various Information On Clean Boot of System I am not new to Unix having used Unix since 1995, and as my only OS since 1= 999. I am new to FreeBSD mostly since mid July 2019, and on/off attempts over l= ast 15 years. This problem is serious, but likely I or only a few unique types of users w= ill experience this serious problem. What makes this bug unique from information gathering and debugging point of view is the complete loss of the keyboard. Complete loss does mean no input from the keyboard is accepted not is any input from the keyboard result in a beep. At the time of this FreeBSD Kernel condition I had been and still was in my XFCE4 DE environment. The mouse was responsive and applications would resp= ond to the mouse, but application would respond to any keyboard input. The CTL-Alt-Fn keyboard sequence was also unresponsive. For reasons unknown the only XFCE4 functions not greyed out was "Log Out". Various applications were successfully and normally exited via the use of t= he DE mouse by selecting the application menu to exit the application. Upon "Log Out" of XFCE DE the command line appeared as is how my system is = so configured. I did not install SLIM nor any other DE GUI based login manage= r.=20 The command line would not accept any keyboard input and likewise no error messages not keyboard beeps. Two additional observations were also made. The first and most important is I believe the condition of the keyboard was directly related to the FreeBSD Kernel in a intense swap file activity for about 15 minutes before the base system killed Firefox as the almost certain object of the intense swap file activity. Be aware I have far more than li= kely to ever be needed at present of swap file space. That means the swap file capacity would not have been reached. At the time of the intense swap acti= vity about 4.78GB of swap was being used as it so happens htop was already runni= ng on a terminal as well as XOSview at time of intense swap file use. When the base system killed firefox the swap file use dropped to about 678Mb per hto= p.=20 htop could not be exited via the keyboard "q" normally used to exit htop. The second by pure chance of circumstance occurred at the terminal prompt a= fter the successful exit from XFCE DE unresponsive to any keyboard input. I happened to plug my phone in to charge via USB cable left in the laptop ong= oing for that purpose. The Android phone in question has no USB access by desig= n of the phone (long story, but Samsung disabled any USB access on this specific version of the phone). Despite the phone not having USB access to files on= the phone FreeBSD Kernel did issue messages to the terminal when the phone was connected to the USB port. I tried the keyboard again out of curiosity, and found he keyboard was responsive! This allowed me to shutdown FreeBSD norm= ally vs the only other option I did not wish to use being a power off. Despite issuing a "poweroff" command and then powering on the laptop after there appeared to be a number of file system repairs done, but I have not b= een able to find where FreeBSD keeps the messages that flash by on the booting = of the FreeBSD kernel to save those messages and look at them in more detail. I had a long career in IT and much of that career was working on bugs that = were often very difficult to find, including difficult to duplicate. So I know = more information will be needed for when this FreeBSD Kernel bug occurs again. I know it will, but I do not know when. In the process of first sorts of software I like to have on a Unix system=20 bsdsar was at top of list after some basic research. Sadly bsdsar seems to have been an inactive project for a long time. I have been unable to find a alternative to bsdsar that would have at least provided some metrics on th paging activity, extent, how much and how long before firefox was killed by= the base system. Wat I need to know is based on the likely limitation of no keyboard access what can I do that will collect information about this issue that can be looked at even after I may have to hard power off the laptop vs using "shutdown" or "poweroff" or "reboot" CLI commands? --=20 You are receiving this mail because: You are the assignee for the bug.=