mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Bagas Sanjaya <bagasdotme@gmail.com>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux Regressions <regressions@lists.linux.dev>,
	Linux USB <linux-usb@vger.kernel.org>
Cc: "Heikki Krogerus" <heikki.krogerus@linux.intel.com>,
	"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
	"Samuel Čavoj" <samuel@cavoj.net>,
	"Hans de Goede" <hdegoede@redhat.com>,
	"Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>,
	"Oleksii Shevchuk" <alxchk@gmail.com>
Subject: Fwd: Linux 6.5.5 - kernel BUG with ucsi_acpi
Date: Mon, 2 Oct 2023 07:11:08 +0700	[thread overview]
Message-ID: <bcfdaf76-8d0f-4365-9ad9-a8b285dc70dd@gmail.com> (raw)

Hi,

I notice a regression report on Bugzilla [1]. Quoting from it:

> After update to linux 6.5.5 I observed several crashes during bootup when USB drive connected to USB-C hub. To find out what has been crashed I enabled EFI pstore. Unfortunately there were no crashes after that. However, there are kernel BUG traces in dmesg. After several experiments I found strong correlation between ucsi_acpi driver and the crash.
> 
> I blacklisted:
> blacklist typec_ucsi
> blacklist ucsi_acpi
> blacklist roles
> blacklist typec
> 
> Two dmesgs are in attachment. 
> 
> The messages to search:
> ucsi_acpi USBC000:00: possible UCSI driver bug 2
> ucsi_acpi USBC000:00: error -EINVAL: PPM init failed

See Bugzilla for the full thread.

Anyway, I'm adding this regression to regzbot:

#regzbot introduced: v6.4..v6.5 https://bugzilla.kernel.org/show_bug.cgi?id=217960
#regzbot title: ucsi_acpi boot crash when USB drive is connected to USB-C port

Thanks.

[1]: https://bugzilla.kernel.org/show_bug.cgi?id=217960

-- 
An old man doll... just what I always wanted! - Clara

                 reply	other threads:[~2023-10-02  0:40 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=bcfdaf76-8d0f-4365-9ad9-a8b285dc70dd@gmail.com \
    --to=bagasdotme@gmail.com \
    --cc=alxchk@gmail.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=hdegoede@redhat.com \
    --cc=heikki.krogerus@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=regressions@lists.linux.dev \
    --cc=samuel@cavoj.net \
    --cc=u.kleine-koenig@pengutronix.de \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®