You are not logged in.
Here's an extract from dmesg -t:
WARNING: CPU: 4 PID: 127 at drivers/pci/msi.c:1259 pci_irq_get_affinity+0x66/0x80
Modules linked in:
CPU: 4 PID: 127 Comm: kworker/u16:2 Not tainted 4.17.5-1-ARCH #1
Hardware name: Apple Inc. MacBookPro14,3/Mac-551B86E5744E2388, BIOS MBP143.88Z.0178.B00.1806261159 06/26/2018
Workqueue: nvme-reset-wq nvme_reset_work
RIP: 0010:pci_irq_get_affinity+0x66/0x80
RSP: 0000:ffff9f7d81fdbd20 EFLAGS: 00010246
RAX: ffff96876bd89720 RBX: 0000000000000000 RCX: 0000000000000140
RDX: 0000000000000000 RSI: 0000000000000000 RDI: ffff96876b85a000
RBP: ffff968768227008 R08: ffff96876bd8d8a8 R09: ffff96876e003980
R10: ffff96876bd835e0 R11: 0000000000000cc0 R12: ffff968768227008
R13: 0000000000000000 R14: ffff96876b85a000 R15: 00000000ffffffff
FS: 0000000000000000(0000) GS:ffff96877ed00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000000000000000 CR3: 000000045000a001 CR4: 00000000003606e0
Call Trace:
blk_mq_pci_map_queues+0x37/0xc0
blk_mq_alloc_tag_set+0xe3/0x210
nvme_reset_work+0xee7/0x1840
? enqueue_task_fair+0x99/0x730
? resched_curr+0x23/0xd0
? check_preempt_curr+0x7a/0x90
process_one_work+0x1d1/0x3b0
worker_thread+0x2b/0x3d0
? process_one_work+0x3b0/0x3b0
kthread+0x112/0x130
? kthread_flush_work_fn+0x10/0x10
ret_from_fork+0x35/0x40
Code: 0f 0b 31 c0 c3 83 e2 04 48 c7 c0 e0 a0 13 a9 74 2a 48 8b 87 98 02 00 00 48 85 c0 74 0e 48 8b 50 30 48 85 d2 74 05 39 70 14 77 05 <0f> 0b 31 c0 c3 48 63 f6 48 8d 04 b6 48 8d 04 c2 c3 48 8b 40 30
---[ end trace 938bbfe5ae9b4dab ]---The system then boots and seems to work fine (as fine as the hardware from these macbooks is supported).
My questions is whether a warning like this is actionable in any way? If there's a way to debug, then how? If it can be reported, should it be Arch or the kernel's bug tracker? Also, is this warning called a kernel oops?
Last edited by melentye (2018-07-12 05:38:40)
Offline