From: Francisco Ayala Le Brun <francisco@videowindow.eu>
To: adrian.hunter@intel.com, ulf.hansson@linaro.org
Cc: linux-mmc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Bug report: probe of AMDI0040:00 failed with error -16
Date: Tue, 19 Mar 2024 15:43:18 +0100 [thread overview]
Message-ID: <CAN-StX1HqWqi+YW=t+V52-38Mfp5fAz7YHx4aH-CQjgyNiKx3g@mail.gmail.com> (raw)
Hello,
I would like to report a bug.
Issue description:
After updating a GHF51 SBC to a newer kernel version, the system was
no longer able to boot. Running the "lsblk" command in the recovery
console showed no mmc storage detected.
System Information:
OS: Fedora 40 x86_64
Kernel: 6.8.0-0.rc6.49.fc40.x86_64
Relevant Logs:
[ 10.920756] Call Trace:
[ 10.920763] <TASK>
[ 10.920771] dump_stack_lvl+0x4d/0x70
[ 10.920786] __setup_irq+0x530/0x6c0
[ 10.920801] request_threaded_irq+0xe5/0x180
[ 10.920813] ? __pfx_sdhci_thread_irq+0x10/0x10 [sdhci]
[ 10.920843] __sdhci_add_host+0x108/0x360 [sdhci]
[ 10.920871] sdhci_acpi_probe+0x3a8/0x500 [sdhci_acpi]
[ 10.920894] platform_probe+0x44/0xa0
[ 10.920908] really_probe+0x19e/0x3e0
[ 10.930244] __driver_probe_device+0x78/0x160
[ 10.930264] driver_probe_device+0x1f/0xa0
[ 10.930273] __driver_attach_async_helper+0x5e/0xe0
[ 10.930284] async_run_entry_fn+0x34/0x130
[ 10.930296] process_one_work+0x170/0x330
[ 10.930309] worker_thread+0x273/0x3c0
[ 10.934639] ? __pfx_worker_thread+0x10/0x10
[ 10.934654] kthread+0xe8/0x120
[ 10.934663] ? __pfx_kthread+0x10/0x10
[ 10.934671] ret_from_fork+0x34/0x50
[ 10.934681] ? __pfx_kthread+0x10/0x10
[ 10.934688] ret_from_fork_asm+0x1b/0x30
[ 10.934708] </TASK>
[ 10.940978] mmc0: Failed to request IRQ 7: -16
[ 10.943885] sdhci-acpi: probe of AMDI0040:00 failed with error -16
next reply other threads:[~2024-03-19 14:43 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-19 14:43 Francisco Ayala Le Brun [this message]
2024-03-19 16:20 ` Bug report: probe of AMDI0040:00 failed with error -16 Adrian Hunter
2024-03-20 19:29 ` Rafael J. Wysocki
2024-03-21 16:33 ` Rafael J. Wysocki
2024-03-22 14:28 ` Linus Walleij
2024-03-22 14:49 ` Rafael J. Wysocki
2024-03-22 20:07 ` Thomas Gleixner
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='CAN-StX1HqWqi+YW=t+V52-38Mfp5fAz7YHx4aH-CQjgyNiKx3g@mail.gmail.com' \
--to=francisco@videowindow.eu \
--cc=adrian.hunter@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=ulf.hansson@linaro.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).