All of lore.kernel.org
 help / color / mirror / Atom feed
From: Basavaraj Natikar <bnatikar@amd.com>
To: Jesper Dangaard Brouer <hawk@kernel.org>,
	Basavaraj Natikar <Basavaraj.Natikar@amd.com>
Cc: Vinod Koul <vkoul@kernel.org>,
	dmaengine@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
	kernel-team <kernel-team@cloudflare.com>
Subject: Re: Kernel module ae4dma caused my system to not boot
Date: Fri, 28 Feb 2025 21:19:34 +0530	[thread overview]
Message-ID: <38868fe1-9194-4346-b7fd-b8d56e410f1b@amd.com> (raw)
In-Reply-To: <45ddbb23-bf92-4d46-84b6-6c80886d4278@kernel.org>

Hi Jesper,

Could you please use below patch series which fixes below issue.

https://lore.kernel.org/all/20250203162511.911946-1-Basavaraj.Natikar@amd.com/


Thanks,
--
Basavaraj


On 2/28/2025 8:05 PM, Jesper Dangaard Brouer wrote:
> Hi Basavaraj,
>
> When rebasing my devel kernel to v6.14 (6.14.0-rc3-traits-009-bench+),
> my AMD testlab system didn't boot due to the kernel module: ae4dma.
> I disabled the kernel module via CONFIG_AMD_AE4DMA so I can boot my
> system again.
>
> CPU: AMD EPYC 9684X 96-Core Processor
>
> As a help for you to debug here are the kernel console messages that
> seems relevant:
>
> [   13.853689] ae4dma 0000:85:00.1: enabling device (0000 -> 0002)
> [   13.861287] genirq: Flags mismatch irq 0. 00000000 (0000:85:00.1) 
> vs. 00215a00 (timer)
> [   13.870123] CPU: 0 UID: 0 PID: 8 Comm: kworker/0:0 Not tainted 
> 6.14.0-rc3-traits-009-bench+ #32
> [   13.870125] Hardware name: Lenovo HR355M-V3-G12/HR355M_V3_HPM, BIOS 
> HR355M_V3.G.026 10/13/2023
> [   13.870126] Workqueue: events work_for_cpu_fn
> [   13.870132] Call Trace:
> [   13.870134]  <TASK>
> [   13.870136]  dump_stack_lvl+0x64/0x80
> [   13.870141]  __setup_irq+0x522/0x6d0
> [   13.870145]  request_threaded_irq+0x10d/0x180
> [   13.870146]  devm_request_threaded_irq+0x71/0xd0
> [   13.870149]  ? __pfx_ae4_core_irq_handler+0x10/0x10 [ae4dma]
> [   13.870153]  ae4_core_init+0x8f/0x2f0 [ae4dma]
> [   13.870155]  ae4_pci_probe+0x1f3/0x270 [ae4dma]
> [   13.870156]  local_pci_probe+0x42/0xa0
> [   13.870161]  work_for_cpu_fn+0x17/0x30
> [   13.870162]  process_one_work+0x181/0x3a0
> [   13.870165]  worker_thread+0x251/0x360
> [   13.870166]  ? __pfx_worker_thread+0x10/0x10
> [   13.870168]  kthread+0xee/0x240
> [   13.870170]  ? finish_task_switch.isra.0+0x88/0x2d0
> [   13.870173]  ? __pfx_kthread+0x10/0x10
> [   13.870174]  ret_from_fork+0x31/0x50
> [   13.870177]  ? __pfx_kthread+0x10/0x10
> [   13.870178]  ret_from_fork_asm+0x1a/0x30
> [   13.870182]  </TASK>
> [   14.010326] ccp 0000:03:00.5: SEV firmware updated from 1.55.32 to 
> 1.55.37
> [   16.565527] ae4dma 0000:85:00.1: probe with driver ae4dma failed 
> with error -16
> [   16.574958] ae4dma 0000:c1:00.1: enabling device (0000 -> 0002)
>
> Let me know if you need other data,
> --Jesper
>


      reply	other threads:[~2025-02-28 15:49 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-28 14:35 Kernel module ae4dma caused my system to not boot Jesper Dangaard Brouer
2025-02-28 15:49 ` Basavaraj Natikar [this message]

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=38868fe1-9194-4346-b7fd-b8d56e410f1b@amd.com \
    --to=bnatikar@amd.com \
    --cc=Basavaraj.Natikar@amd.com \
    --cc=dmaengine@vger.kernel.org \
    --cc=hawk@kernel.org \
    --cc=kernel-team@cloudflare.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=vkoul@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.