Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

kernel boot failed on APL and CNL #113

Closed
ZhendanYang opened this issue Sep 7, 2018 · 0 comments
Closed

kernel boot failed on APL and CNL #113

ZhendanYang opened this issue Sep 7, 2018 · 0 comments
Labels
bug Something isn't working P1 Blocker bugs or important features

Comments

@ZhendanYang
Copy link

Summary:
kernel boot failed on APL and CNL most of the time, in the remaining time, kernel boot succeeded but kernel panic(call trace in dmesg).

[ 5.293961] BUG: unable to handle kernel paging request at ffff98602fbb7000
[ 5.294017] PGD 14f9fc067 P4D 14f9fc067 PUD 17a140063 PMD 16f7ee063 PTE 800000016fbb7161
[ 5.294065] Oops: 0003 [#1] SMP NOPTI
[ 5.294089] CPU: 0 PID: 247 Comm: systemd-udevd Not tainted 4.18.0+ #1
[ 5.294124] Hardware name: AAEON UP-APL01/UP-APL01, BIOS UPA1AM36 04/10/2018
[ 5.294170] RIP: 0010:snd_sof_create_page_table+0xd4/0xf0 [snd_sof]
[ 5.294204] Code: ce ee 45 89 e0 4c 03 04 24 41 8b 10 89 d1 09 d9 c1 e3 04 09 d3 41 f6 c7 01 0f 44 d9 41 83 c7 01 49 81 c6 00 10 00 00 44 39 fd <41> 89 18 75 85 48 83 c4 10 89 e8 5b 5d 41 5c 41 5d 41 5e 41 5f c3
[ 5.294332] RSP: 0000:ffffa7b6c0b87828 EFLAGS: 00010216
[ 5.294362] RAX: 0000000000000000 RBX: 00000000666e0000 RCX: 00000000666e0000
[ 5.294400] RDX: 00000000666e0000 RSI: 0000000000000096 RDI: ffff98603fc165d0
[ 5.294438] RBP: 0000000000010000 R08: ffff98602fbb6ffe R09: 0000000000000004
[ 5.294476] R10: ffffa7b6c0b87830 R11: 0000000000000001 R12: 0000000000001ffe
[ 5.294514] R13: ffff986031f48320 R14: 0000000000ccd000 R15: 0000000000000ccd
[ 5.294553] FS: 00007fc893854400(0000) GS:ffff98603fc00000(0000) knlGS:0000000000000000
[ 5.294596] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[ 5.294627] CR2: ffff98602fbb7000 CR3: 0000000176c7e000 CR4: 00000000003406f0
[ 5.294664] Call Trace:
[ 5.294691] snd_sof_init_trace+0x7a/0x1b0 [snd_sof]
[ 5.294723] sof_probe+0x1d9/0x320 [snd_sof]
[ 5.294752] platform_drv_probe+0x3a/0x90
[ 5.294777] ? driver_sysfs_add+0x75/0xd0
[ 5.294801] driver_probe_device+0x2fa/0x470
[ 5.294827] ? __driver_attach+0x100/0x100

Environment:
sof-dev: eeb4f6c

I tried with commit 6f71197, it was also a bad point. But commit 7889a7a had no such issue.

Log:
rmbox, rmbox-t can't work so I only got dmesg log file.
dmesg-bootpanic-apl.log
dmesg-bootpanic-cnl.log

@ZhendanYang ZhendanYang added bug Something isn't working P1 Blocker bugs or important features labels Sep 7, 2018
lyakh added a commit to lyakh/linux that referenced this issue Sep 7, 2018
This reverts commit 41b8f5d and
fixes thesofproject#113.

Signed-off-by: Guennadi Liakhovetski <[email protected]>
@mengdonglin mengdonglin assigned xiulipan and unassigned xiulipan Sep 8, 2018
bardliao pushed a commit that referenced this issue Jun 11, 2019
…supported

BugLink: https://bugs.launchpad.net/bugs/1821607

commit f3e0269 upstream.

This patch fixes warning seen when BLK-MQ is enabled and hardware does not
support MQ. This will result into driver requesting MSIx vectors which are
equal or less than pre_desc via PCI IRQ Affinity infrastructure.

    [   19.746300] qla2xxx [0000:00:00.0]-0005: : QLogic Fibre Channel HBA Driver: 10.00.00.12-k.
    [   19.746599] qla2xxx [0000:02:00.0]-001d: : Found an ISP2432 irq 18 iobase 0x(____ptrval____).
    [   20.203186] ------------[ cut here ]------------
    [   20.203306] WARNING: CPU: 8 PID: 268 at drivers/pci/msi.c:1273 pci_irq_get_affinity+0xf4/0x120
    [   20.203481] Modules linked in: tg3 ptp qla2xxx(+) pps_core sg libphy scsi_transport_fc flash loop autofs4
    [   20.203700] CPU: 8 PID: 268 Comm: systemd-udevd Not tainted 5.0.0-rc5-00358-gdf3865f #113
    [   20.203830] Call Trace:
    [   20.203933]  [0000000000461bb0] __warn+0xb0/0xe0
    [   20.204090]  [00000000006c8f34] pci_irq_get_affinity+0xf4/0x120
    [   20.204219]  [000000000068c764] blk_mq_pci_map_queues+0x24/0x120
    [   20.204396]  [00000000007162f4] scsi_map_queues+0x14/0x40
    [   20.204626]  [0000000000673654] blk_mq_update_queue_map+0x94/0xe0
    [   20.204698]  [0000000000676ce0] blk_mq_alloc_tag_set+0x120/0x300
    [   20.204869]  [000000000071077c] scsi_add_host_with_dma+0x7c/0x300
    [   20.205419]  [00000000100ead54] qla2x00_probe_one+0x19d4/0x2640 [qla2xxx]
    [   20.205621]  [00000000006b3c88] pci_device_probe+0xc8/0x160
    [   20.205697]  [0000000000701c0c] really_probe+0x1ac/0x2e0
    [   20.205770]  [0000000000701f90] driver_probe_device+0x50/0x100
    [   20.205843]  [0000000000702134] __driver_attach+0xf4/0x120
    [   20.205913]  [0000000000700644] bus_for_each_dev+0x44/0x80
    [   20.206081]  [0000000000700c98] bus_add_driver+0x198/0x220
    [   20.206300]  [0000000000702950] driver_register+0x70/0x120
    [   20.206582]  [0000000010248224] qla2x00_module_init+0x224/0x284 [qla2xxx]
    [   20.206857] ---[ end trace b1de7a3f79fab2c2 ]---

The fix is to check if the hardware does not have Multi Queue capabiltiy,
use pci_alloc_irq_vectors() call instead of pci_alloc_irq_affinity().

Fixes: f664a3c ("scsi: kill off the legacy IO path")
Cc: [email protected] #4.19
Signed-off-by: Giridhar Malavali <[email protected]>
Signed-off-by: Himanshu Madhani <[email protected]>
Signed-off-by: Martin K. Petersen <[email protected]>
Signed-off-by: Greg Kroah-Hartman <[email protected]>

Signed-off-by: Seth Forshee <[email protected]>
aiChaoSONG pushed a commit to aiChaoSONG/linux that referenced this issue May 6, 2021
Add `LockedBy` to the `sync` module.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working P1 Blocker bugs or important features
Projects
None yet
Development

No branches or pull requests

2 participants