On 1/2/24 17:47, V, Narasimhan wrote:
[AMD Official Use Only - General]
No, we don't see this issue on linus' tree or on linux-next in the till
the previous week
Thanks, this indeed shows it's a regression coming from recent Andy's
patchset. Notes and questions below:
[ 6.245173] i2c_designware AMDI0010:00: Unknown Synopsys component type: 0xffffffff
This made me scratching my head since driver probing will fail in this
case with -ENODEV and I could not trigger runtime PM activity in such
case but perhaps this is timing specific which happens to happen in your
case.
Out of curiosity do you see this same "i2c_designware AMDI0010:00:
Unknown Synopsys component type: 0xffffffff" error on Vanilla or is it
also regression in linux-next?
[ 6.252683] BUG: kernel NULL pointer dereference, address: 00000000000001fc
[ 6.256551] #PF: supervisor read access in kernel mode
[ 6.256551] #PF: error_code(0x0000) - not-present page
[ 6.256551] PGD 0
[ 6.256551] Oops: 0000 [#1] PREEMPT SMP NOPTI
[ 6.256551] CPU: 32 PID: 211 Comm: kworker/32:0 Not tainted 6.7.0-rc6-next-20231222-1703820640818 #1
[ 6.256551] Workqueue: pm pm_runtime_work
[ 6.256551] RIP: 0010:regmap_read+0x12/0x70
[ 6.256551] Code: 00 00 00 00 0f 1f 40 00 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 f3 0f 1e fa 0f 1f 44 00 00 55 48 89 e5 41 55 41 54 53 <8b> 87 fc 01 00 00 83 e8 01 85 f0 75 42 48 89 fb 41 89 f4 49 89 d5
[ 6.256551] RSP: 0018:ff7fa5c740bcbc98 EFLAGS: 00010246
[ 6.256551] RAX: 0000000000000000 RBX: ff38ff5c159f1028 RCX: 0000000000000008
[ 6.256551] RDX: ff7fa5c740bcbcc4 RSI: 0000000000000034 RDI: 0000000000000000
[ 6.256551] RBP: ff7fa5c740bcbcb0 R08: ff38ff5c02ceb8b0 R09: ff38ff5c002a4500
[ 6.256551] R10: 0000000000000003 R11: 0000000000000003 R12: ff38ff5c159f1028
[ 6.256551] R13: 0000000000000000 R14: 0000000000000000 R15: ff38ff5c159ed8f4
[ 6.256551] FS: 0000000000000000(0000) GS:ff38ff6b0d200000(0000) knlGS:0000000000000000
[ 6.256551] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[ 6.256551] CR2: 00000000000001fc CR3: 000000007403c001 CR4: 0000000000771ef0
[ 6.256551] PKRU: 55555554
[ 6.256551] Call Trace:
[ 6.256551] <TASK>
[ 6.256551] ? show_regs+0x6d/0x80
[ 6.256551] ? __die+0x29/0x70
[ 6.256551] ? page_fault_oops+0x153/0x4a0
[ 6.256551] ? do_user_addr_fault+0x30f/0x6c0
[ 6.256551] ? exc_page_fault+0x7c/0x190
[ 6.256551] ? asm_exc_page_fault+0x2b/0x30
[ 6.256551] ? regmap_read+0x12/0x70
[ 6.256551] ? update_load_avg+0x82/0x7d0
[ 6.256551] __i2c_dw_disable+0x38/0x180
[ 6.256551] i2c_dw_disable+0x3f/0xb0
[ 6.256551] i2c_dw_runtime_suspend+0x33/0x50
I think this Oops comes because of the first commit in the patchset:
bd466a892612 ("i2c: designware: Fix PM calls order in dw_i2c_plat_probe()"
Do you see the issue if you test at that commit?
Before that commit when the i2c_dw_probe() path fails we explicitly
disable the runtime PM before returning but now let the managed calls to
do it. Perhaps there is some time window that runtime suspending occurs
in parallel while drivers base is executing post probe code?
dw_i2c_plat_probe
i2c_dw_probe
i2c_dw_probe_master
i2c_dw_init_regmap
-> failure and thus dev->map is not set
i2c_dw_runtime_suspend
i2c_dw_disable
__i2c_dw_disable
regmap_read(dev->map, ...)
-> Oops because dev->map is NULL
Other PM related commit in the patchset is commit 2347b8dc0d2e ("i2c:
designware: Consolidate PM ops") but I don't think that is the reason.
