All the mail mirrored from lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@kernel.org
To: linux-usb@vger.kernel.org
Subject: [Bug 217960] New: Linux 6.5.5 - kernel BUG with ucsi_acpi
Date: Sun, 01 Oct 2023 12:43:35 +0000	[thread overview]
Message-ID: <bug-217960-208809@https.bugzilla.kernel.org/> (raw)

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

            Bug ID: 217960
           Summary: Linux 6.5.5 - kernel BUG with ucsi_acpi
           Product: Drivers
           Version: 2.5
          Hardware: Intel
                OS: Linux
            Status: NEW
          Severity: normal
          Priority: P3
         Component: USB
          Assignee: drivers_usb@kernel-bugs.kernel.org
          Reporter: alxchk@gmail.com
        Regression: No

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

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are watching the assignee of the bug.

             reply	other threads:[~2023-10-01 12:43 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-01 12:43 bugzilla-daemon [this message]
2023-10-01 12:43 ` [Bug 217960] Linux 6.5.5 - kernel BUG with ucsi_acpi bugzilla-daemon
2023-10-01 12:44 ` bugzilla-daemon
2023-10-01 14:06 ` bugzilla-daemon
2023-10-01 14:25 ` bugzilla-daemon
2023-10-01 14:25 ` bugzilla-daemon
2023-10-01 23:40 ` bugzilla-daemon

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=bug-217960-208809@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@kernel.org \
    --cc=linux-usb@vger.kernel.org \
    /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.