From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Farhad Alemi <farhad.alemi@berkeley.edu>
Cc: Thinh Nguyen <Thinh.Nguyen@synopsys.com>,
falemi@asu.edu, linux-usb@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [BUG] platform_get_irq_byname_optional -- dwc3-haps registers IRQ 0, WARN on first gadget init
Date: Fri, 28 Aug 2026 07:45:35 +0200 [thread overview]
Message-ID: <2026082856-exhume-footbath-5a28@gregkh> (raw)
In-Reply-To: <CA+0ovCh2o46zgc5Be_Z5=6NNJTKnd3W29zeMJ+gBCgL+4fFLAg@mail.gmail.com>
On Fri, Aug 28, 2026 at 05:34:05AM +0000, Farhad Alemi wrote:
> Hello,
>
> As part of the kernel research at ASU's SEFCOM
> lab, we hit the crash below. Crash reports can be found here:
>
> https://github.com/farhad-alemi/public_bug_reports/tree/main/149-usb-dwc3-haps-registers-irq-0/
Digging through random urls isn't that helpful to us, please include all
of the needed information in the email itself.
Remember, some of us get 1000+ emails a day to handle :(
>
> dwc3 dwc3.2.auto: Configuration mismatch. dr_mode forced to gadget
> 0 is an invalid IRQ number
> WARNING: drivers/base/platform.c:492 at
> platform_get_irq_byname_optional+0x1ed/0x220, CPU#1: repro/9498
> Call Trace:
> platform_get_irq_byname_optional+0x1ed/0x220
> dwc3_gadget_init+0x607/0x2170
> dwc3_core_init_mode+0x2f8/0x790
> dwc3_core_probe+0x2345/0x2850
> dwc3_probe+0x100/0x150
> platform_probe+0xf9/0x190
> really_probe+0x267/0xaf0
> __driver_probe_device+0x1e2/0x350
> driver_probe_device+0x4f/0x240
> __device_attach_driver+0x270/0x410
> bus_for_each_drv+0x258/0x2f0
> __device_attach+0x2c5/0x450
>
> Our reproducer.c is available upon request.
>
> Happy to test a patch if that would help.
Please send a patch.
thanks,
greg k-h
next prev parent reply other threads:[~2026-08-28 5:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-28 5:34 [BUG] platform_get_irq_byname_optional -- dwc3-haps registers IRQ 0, WARN on first gadget init Farhad Alemi
2026-08-28 5:45 ` Greg Kroah-Hartman [this message]
2026-08-28 6:12 ` Greg Kroah-Hartman
2026-08-28 6:16 ` Farhad Alemi
2026-08-28 6:32 ` Greg Kroah-Hartman
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=2026082856-exhume-footbath-5a28@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=Thinh.Nguyen@synopsys.com \
--cc=falemi@asu.edu \
--cc=farhad.alemi@berkeley.edu \
--cc=linux-kernel@vger.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox