From: Alberto Sentieri <22t@tripolho.com>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-usb@vger.kernel.org
Subject: Re: kernel locks due to USB I/O
Date: Wed, 16 Dec 2020 17:14:05 -0500 [thread overview]
Message-ID: <55bce71d-4282-2bff-009e-aea139e53315@tripolho.com> (raw)
In-Reply-To: <20201214171815.GA153671@rowland.harvard.edu>
This is just a quick status update. I am just checking if it rings any
bell. I am still doing more tests.
The machine where all these problems are happening is a HP Z4 G4, as
well as the other two in production. Until this morning it had BIOS
v01.76 dated 04/22/2019. Today I update the BIOS to v02.63 dated 10/28/2020.
After updating the BIOS, the behavior definitively changed. Now both
kernels (5.4.0-53-generic and 5.9.8) reboot unexpectedly instead of
locking. After re-enabling the console, expecting to capture something,
I could not see a lock or reboot. However the serial console, after
displaying the whole boot, locked, and I cannot use it to login.
Alberto Sentieri
On 12/14/20 12:18 PM, Alan Stern wrote:
> We'll have to wait and see what the tests and debugging tools reveal.
> As for the comment about the hardware being reliable -- in fact, you
> can't be certain of this. It may be that your test is stressing the
> hardware in a way that it never experienced during the prior six
> months.
>
> Alan Stern
next prev parent reply other threads:[~2020-12-16 22:15 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-10 19:20 kernel locks due to USB I/O Alberto Sentieri
2020-11-10 20:51 ` Alan Stern
2020-11-10 23:42 ` Alberto Sentieri
2020-11-11 7:51 ` Greg Kroah-Hartman
2020-11-11 15:51 ` Alan Stern
2020-11-11 19:31 ` Alberto Sentieri
2020-11-16 16:53 ` Alberto Sentieri
2020-11-16 17:06 ` Alan Stern
2020-11-16 18:42 ` Alberto Sentieri
2020-11-19 17:22 ` Alan Stern
2020-11-19 18:50 ` Alberto Sentieri
2020-11-19 20:01 ` Alan Stern
[not found] ` <4f8f545e-4846-45e0-b8f8-5c73876b150a@tripolho.com>
[not found] ` <20201119225144.GA590990@rowland.harvard.edu>
[not found] ` <3df90f9d-0af2-2aaa-9853-966f99e961a4@tripolho.com>
2020-12-14 17:18 ` Alan Stern
2020-12-16 22:14 ` Alberto Sentieri [this message]
2020-11-19 19:21 ` Alberto Sentieri
2020-11-19 19:43 ` Alan Stern
2020-11-19 22:14 ` Alberto Sentieri
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=55bce71d-4282-2bff-009e-aea139e53315@tripolho.com \
--to=22t@tripolho.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-usb@vger.kernel.org \
--cc=stern@rowland.harvard.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.