From owner-freebsd-current@freebsd.org Mon Nov 18 19:53:43 2019 Return-Path: Delivered-To: freebsd-current@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 CF6B61C83D1 for ; Mon, 18 Nov 2019 19:53:43 +0000 (UTC) (envelope-from thj@freebsd.org) Received: from out5-smtp.messagingengine.com (out5-smtp.messagingengine.com [66.111.4.29]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 47H0533YnTz4SZ2; Mon, 18 Nov 2019 19:53:43 +0000 (UTC) (envelope-from thj@freebsd.org) Received: from compute2.internal (compute2.nyi.internal [10.202.2.42]) by mailout.nyi.internal (Postfix) with ESMTP id 6450522335; Mon, 18 Nov 2019 14:53:42 -0500 (EST) Received: from mailfrontend2 ([10.202.2.163]) by compute2.internal (MEProxy); Mon, 18 Nov 2019 14:53:42 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm1; bh=oIEalPzStN/+2TIMWMXwqhsl3gzddAIjFdXqeUfCA b8=; b=GZPYagiBdw5vw11oOHa0a8x5I0FlKmlrzhHvTumnWlEf1jbH2vhdNirwz cJekk0OYg4cN4IJraTUDY+zQN2/YV1GxuVFrCt1uwYfcZuHYXRIx14PnMxlcCxDg 9jgoubb2SwYnxK4NbKXntm5tK6Y8yXrOxFdpngT7U6mpO8zs+6ZdYp8wV8AJCSyg +Zvac2KLVrOKtt/UV0QylKeZo5LVnZNfaRGJGELgOIw5wgmNjnrqKlilO3TJWdMZ RU1nF+8g9+Tl3guPaNilaI1FEV2xyEhgoVwt0DgGY3bTj5gxmoJSh+rWRD4df5xK dKs5gP2EuKj5DRp9QbLV6irv6Fwxg== X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedufedrudegiedguddtlecutefuodetggdotefrod ftvfcurfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfgh necuuegrihhlohhuthemuceftddtnecunecujfgurhepfffhvffukfhfgggtugfgjggfse htkeertddtreejnecuhfhrohhmpefvohhmucflohhnvghsuceothhhjhesfhhrvggvsghs ugdrohhrgheqnecukfhppedufeejrdehtddrudejrdduvdenucfrrghrrghmpehmrghilh hfrhhomhepthhhjhesfhhrvggvsghsugdrohhrghenucevlhhushhtvghrufhiiigvpedt X-ME-Proxy: Received: from tom-desk.erg.abdn.ac.uk (tom-desk.erg.abdn.ac.uk [137.50.17.12]) by mail.messagingengine.com (Postfix) with ESMTPA id 887A3306005B; Mon, 18 Nov 2019 14:53:39 -0500 (EST) Date: Mon, 18 Nov 2019 19:53:47 +0000 From: Tom Jones To: Oleksandr Tymoshenko Cc: "Bjoern A. Zeeb" , d@delphij.net, freebsd-current@freebsd.org, delphij@freebsd.org, jkim@freebsd.org Subject: Re: ThinkPad: reboots after successful shutdown -p Message-ID: <20191118195347.GA23184@tom-desk.erg.abdn.ac.uk> References: <4E1A221E-DC9B-4F11-9E26-08B532286580@lists.zabbadoz.net> <20191118194718.GA29340@bluezbox.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <20191118194718.GA29340@bluezbox.com> User-Agent: Mutt/1.12.2 (2019-09-21) X-Rspamd-Queue-Id: 47H0533YnTz4SZ2 X-Spamd-Bar: / Authentication-Results: mx1.freebsd.org; none X-Spamd-Result: default: False [-0.46 / 15.00]; local_wl_from(0.00)[freebsd.org]; NEURAL_HAM_LONG(-0.63)[-0.629,0]; NEURAL_SPAM_MEDIUM(0.17)[0.166,0]; ASN(0.00)[asn:11403, ipnet:66.111.4.0/24, country:US] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 18 Nov 2019 19:53:43 -0000 On Mon, Nov 18, 2019 at 11:47:18AM -0800, Oleksandr Tymoshenko wrote: > Bjoern A. Zeeb (bzeeb-lists@lists.zabbadoz.net) wrote: > > On 18 Nov 2019, at 7:14, Xin Li wrote: > > > > > Hi, > > > > > > I recently noticed that if I do a 'shutdown -p' from -CURRENT, the > > > system would shut down and seemingly powered off, then it would > > > restart > > > after about 5-10 seconds. > > > > Interesting. I have the opposite problem that a reboot does a shutdown > > but never resets (also no reset from ddb>). I’ve seen this on the > > X270 and the T480. > > I had this issue on my Thinkpad too. The "solution" was to disable > bluetooth chip in BIOS. I didn't try to find the root cause of this > behavior. There was a related bluetooth update in September after which my x270 was able to reboot. You might want to reenable and try again - [tj]