All of lore.kernel.org
 help / color / mirror / Atom feed
From: Wang Yugui <wangyugui@e16-tech.com>
To: stable@vger.kernel.org
Cc: Wang Yugui <wangyugui@e16-tech.com>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Subject: Re: [6.12.y] WARNING: CPU: 0 PID: 681 at block/blk-mq-cpumap.c:90 blk_mq_map_hw_queues+0xcf/0xe0
Date: Sat, 03 May 2025 10:05:29 +0800	[thread overview]
Message-ID: <20250503100528.C7F9.409509F4@e16-tech.com> (raw)
In-Reply-To: <20250503091422.0389.409509F4@e16-tech.com>

Hi,
Cc: Greg Kroah-Hartman

> Hi,
> 
> I noticed a WARNING in recent 6.12.y kernel.
> 
> This WARNING happen on 6.12.26/6.12.25, but not happen on 6.12.20.
> 
> More bisect job need to be done, but reporti it firstly.
> 
> [   13.288365] ------------[ cut here ]------------
> [   13.288366] WARNING: CPU: 0 PID: 681 at block/blk-mq-cpumap.c:90 blk_mq_map_hw_queues+0xcf/0xe0
> void blk_mq_map_hw_queues(struct blk_mq_queue_map *qmap,
>               struct device *dev, unsigned int offset)
> {
> ...
> ...
> fallback:
> L90:    WARN_ON_ONCE(qmap->nr_queues > 1);
>     blk_mq_clear_mq_map(qmap);
> }
> 

The following patch fixed this WARNING.

From a9ae6fe1c319c4776c2b11e85e15109cd3f04076 Mon Sep 17 00:00:00 2001
From: Daniel Wagner <wagi@kernel.org>
Date: Thu, 23 Jan 2025 14:08:29 +0100
Subject: [PATCH] blk-mq: create correct map for fallback case

please pull it to 6.12.y.

Best Regards
Wang Yugui (wangyugui@e16-tech.com)
2025/05/03


> [   13.288373] Modules linked in: ahci(+) mlxfw libahci pci_hyperv_intf bnx2x(+) i40e(+) mpi3mr(+) psample bnxt_en(+) libata mgag200(+) tls megaraid_sas(+) crc32c_intel scsi_transport_sas mdio libie i2c_algo_bit wmi dm_mirror dm_region_hash dm_log dm_mod
> [   13.288386] CPU: 0 UID: 0 PID: 681 Comm: kworker/0:2 Not tainted 6.12.26-1.el7.x86_64 #1
> [   13.288388] Hardware name: Dell Inc. PowerEdge T640/0TWW5Y, BIOS 2.22.1 09/12/2024
> [   13.288390] Workqueue: events work_for_cpu_fn
> [   13.288394] RIP: 0010:blk_mq_map_hw_queues+0xcf/0xe0
> [   13.288396] Code: 8b 35 85 e4 9a 02 48 63 d0 48 c7 c7 e0 e5 78 94 e8 26 0b 07 00 39 05 70 e4 9a 02 77 d3 5b 5d 41 5c 41 5d 41 5e c3 cc cc cc cc <0f> 0b eb d2 66 66 2e 0f 1f 84 00 00 00 00 00 66 90 90 90 90 90 90
> [   13.288398] RSP: 0018:ffffc0e11b83bd38 EFLAGS: 00010212
> [   13.288400] RAX: 0000000000000000 RBX: ffffa0804ad58000 RCX: 0000000000000050
> [   13.288402] RDX: 0000000000000050 RSI: ffffa07f8f24d0c8 RDI: ffffa0804ad580e8
> [   13.288403] RBP: ffffa0804ad580e0 R08: 000000000000004f R09: 0000000000000000
> [   13.288404] R10: ffffc0e11b83bd78 R11: ffffa07f9039da00 R12: 0000000000000000
> [   13.288405] R13: 0000000000000001 R14: ffffa0804ad580e8 R15: 0000000000000000
> [   13.288406] FS:  0000000000000000(0000) GS:ffffa0dd3fe00000(0000) knlGS:0000000000000000
> [   13.288407] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
> [   13.288408] CR2: 00007f1f3226ba20 CR3: 00000002f9780005 CR4: 00000000007706f0
> [   13.288409] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
> [   13.288410] DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
> [   13.288411] PKRU: 55555554
> [   13.288412] Call Trace:
> [   13.288413]  <TASK>
> [   13.288415]  megasas_map_queues+0x49/0x90 [megaraid_sas]
> [   13.288431]  blk_mq_alloc_tag_set+0x150/0x3b0
> [   13.288436]  scsi_add_host_with_dma+0xd0/0x350
> [   13.288440]  megasas_io_attach+0x15c/0x220 [megaraid_sas]
> [   13.288456]  megasas_probe_one+0x1cb/0x570 [megaraid_sas]
> [   13.288468]  local_pci_probe+0x47/0xa0
> [   13.288474]  work_for_cpu_fn+0x17/0x30
> [   13.288475]  process_one_work+0x179/0x3a0
> [   13.288480]  worker_thread+0x24b/0x350
> [   13.288483]  ? __pfx_worker_thread+0x10/0x10
> [   13.288485]  kthread+0xde/0x110
> [   13.288489]  ? __pfx_kthread+0x10/0x10
> [   13.288491]  ret_from_fork+0x31/0x50
> [   13.288494]  ? __pfx_kthread+0x10/0x10
> [   13.288496]  ret_from_fork_asm+0x1a/0x30
> [   13.288502]  </TASK>
> [   13.288502] ---[ end trace 0000000000000000 ]---
> 
> 
> Best Regards
> Wang Yugui (wangyugui@e16-tech.com)
> 2025/05/03
> 



  reply	other threads:[~2025-05-03  2:36 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-03  1:14 [6.12.y] WARNING: CPU: 0 PID: 681 at block/blk-mq-cpumap.c:90 blk_mq_map_hw_queues+0xcf/0xe0 Wang Yugui
2025-05-03  2:05 ` Wang Yugui [this message]
2025-05-05  9:24   ` Greg Kroah-Hartman
2025-05-05 11:36     ` Jack Wang
2025-05-05 13:28       ` Greg KH
2025-05-05 13:40         ` Daniel Wagner
2025-05-05 13:52           ` Greg KH
2025-05-05 14:05             ` Daniel Wagner
2025-05-05 14:21               ` Greg KH
2025-05-05 13:41         ` Jinpu Wang

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=20250503100528.C7F9.409509F4@e16-tech.com \
    --to=wangyugui@e16-tech.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=stable@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.