From owner-freebsd-current@freebsd.org Mon Jan 20 13:59:08 2020 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 82C431FAC54 for ; Mon, 20 Jan 2020 13:59:08 +0000 (UTC) (envelope-from hps@selasky.org) Received: from mail.turbocat.net (turbocat.net [88.99.82.50]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 481YDq4fz4z4Xhy for ; Mon, 20 Jan 2020 13:59:07 +0000 (UTC) (envelope-from hps@selasky.org) Received: from hps2020.home.selasky.org (unknown [62.141.129.235]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits)) (No client certificate requested) by mail.turbocat.net (Postfix) with ESMTPSA id 6CB692601D7; Mon, 20 Jan 2020 14:59:00 +0100 (CET) Subject: Re: Can't reattach USB devices (Lenovo bug?) To: Evilham , "freebsd-current@freebsd.org" References: <413e73db-3e1d-42b6-b237-30174e1b3f03@yggdrasil.evilham.com> From: Hans Petter Selasky Message-ID: <0c8cc21e-9530-7b89-7655-e11fe2bb373e@selasky.org> Date: Mon, 20 Jan 2020 14:57:58 +0100 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:68.0) Gecko/20100101 Thunderbird/68.3.1 MIME-Version: 1.0 In-Reply-To: <413e73db-3e1d-42b6-b237-30174e1b3f03@yggdrasil.evilham.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-Rspamd-Queue-Id: 481YDq4fz4z4Xhy X-Spamd-Bar: ----- Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=pass (mx1.freebsd.org: domain of hps@selasky.org designates 88.99.82.50 as permitted sender) smtp.mailfrom=hps@selasky.org X-Spamd-Result: default: False [-5.42 / 15.00]; ARC_NA(0.00)[]; TO_DN_EQ_ADDR_SOME(0.00)[]; RCVD_TLS_ALL(0.00)[]; FROM_HAS_DN(0.00)[]; TO_DN_SOME(0.00)[]; R_SPF_ALLOW(-0.20)[+a:mail.turbocat.net]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; MIME_GOOD(-0.10)[text/plain]; DMARC_NA(0.00)[selasky.org]; RCVD_VIA_SMTP_AUTH(0.00)[]; TO_MATCH_ENVRCPT_SOME(0.00)[]; RCPT_COUNT_TWO(0.00)[2]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; IP_SCORE(-3.12)[ip: (-9.34), ipnet: 88.99.0.0/16(-4.71), asn: 24940(-1.53), country: DE(-0.02)]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:24940, ipnet:88.99.0.0/16, country:DE]; MID_RHS_MATCH_FROM(0.00)[]; SUBJECT_HAS_QUESTION(0.00)[]; RCVD_COUNT_TWO(0.00)[2] 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, 20 Jan 2020 13:59:08 -0000 On 2020-01-20 13:12, Evilham wrote: > Hello, > > at first I thought I had found a regression in CURRENT (2020-01-19), and > now I'm not so sure since, before reporting I rolled back a recent BIOS > upgrade and that got rid of the issue. > > First of all, the hardware: Lenovo ThinkPad A485 (AMD Ryzen processor). > > The issue (BIOS v1.28[1]) being that any USB device: would work on first > plug, but if unplugged and plugged again, it wouldn't work (see dmesg > below). > > Downgrading to BIOS v1.24 results in the issue disappearing. > > How should this be dealt with? Could this be something FreeBSD needs > better support for? or is it entirely on Lenovo? > If the former, how can I help provide more information/testing(*)? > If the latter, should I inform Lenovo of the issue? If anyone has > experience with that, I'd appreciate pointers as to how to provide them > with information in a way that makes it somewhat likely that things get > solved. > > [1]: BIOS Release notes: > https://download.lenovo.com/pccbbs/mobiles/r0wuj60w.txt > (*): Helping spot bugs and provide information/testing is why I'm > running CURRENT after all > > Just FTR: I also experienced random kernel panics [2] with versions > v1.22 and v1.16 of the BIOS, so maybe Lenovo is being > unreasonable/unreliable about BIOS upgrades. > In any case I am curious as to how other OS deal with this class of > issues and how FreeBSD could (if possible at all) work better in these > cases. > > [2]: Kernel panic solved by BIOS upgrade (to v1.24) see: > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=239351 > > Also FTR, this was the contents of dmesg with BIOS v1.28 and CURRENT as > of 2020-01-19: > (notice there are multiple disconnect and reconnect attempts of > different devices) > > ugen1.2: at usbus1 (disconnected) > uhub4: at uhub1, port 1, addr 1 (disconnected) > ugen1.3: at usbus1 (disconnected) > ukbd0: at uhub4, port 2, addr 2 (disconnected) > ukbd0: detached > uhid0: at uhub4, port 2, addr 2 (disconnected) > uhid0: detached > ugen1.4: at usbus1 (disconnected) > uhub5: at uhub4, port 4, addr 3 (disconnected) > ugen1.5: at usbus1 > (disconnected) > uhid1: at uhub5, port 1, addr 4 (disconnected) > uhid1: detached > ums0: at uhub5, port 1, addr 4 (disconnected) > ums0: detached > ukbd1: at uhub5, port 1, addr 4 (disconnected) > ukbd1: detached > uhub5: detached > uhub4: detached > ugen1.2: at usbus1 > uhub4 on uhub1 > uhub4: on usbus1 > acpi_ec0: EcCommand: no response to 0x84 > uhub4: 4 ports with 4 removable, self powered > acpi_ec0: EcCommand: no response to 0x84 > acpi_ec0: EcCommand: no response to 0x84 > acpi_ec0: GPE query failed: AE_NO_HARDWARE_RESPONSE ^^^ my best guess is this is ACPI related :-( ACPI has own debugging flags and options. --HPS