[Bug 1956519] Re: amd_sfh: Null pointer dereference on early device init causes early panic and fails to boot

2022-01-19 Thread Iestyn Elfick
Same here, problem resolved. Great job, amazing turnaround.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1956519

Title:
  amd_sfh: Null pointer dereference on early device init causes early
  panic and fails to boot

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1956519/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1956519] Re: kernel panic after upgrading to kernel 5.13.0-23

2022-01-11 Thread Iestyn Elfick
FYI - still occurs in 5.13.0-25.

Linux version 5.13.0-25-generic (buildd@lgw01-amd64-047) (gcc (Ubuntu
11.2.0-7ubuntu2) 11.2.0, GNU ld (GNU Binutils for Ubuntu) 2.37)
#26-Ubuntu SMP Fri Jan 7 15:48:31 UTC 2022

BUG: kernel NULL pointer dereference, address: 000c
#PF: supervisor write access in kernel mode
#PF: error_code(0x0002) - not-present page
PGD 0 P4D 0 
Oops: 0002 [#1] SMP NOPTI
CPU: 0 PID: 191 Comm: systemd-udevd Not tainted 5.13.0-25-generic #26-Ubuntu
Hardware name: ASUSTeK COMPUTER INC. MINIPC PN50/PN50, BIOS 0620 03/18/2021
RIP: 0010:amd_sfh_hid_client_init+0x47/0x350 [amd_sfh]
Code: 00 53 48 83 ec 20 48 8b 5f 08 48 8b 07 48 8d b3 22 01 00 00 4c 8d b0 c8 
00 00 00 e8 23 07 00 00 45 31 c0 31 c9 ba 00 00 20 00 <89> 43 0c 48 8d 83 68 01 
00 00 48 8d bb 80 01 00 00 48 c7 c6 20 6d
RSP: 0018:a431c0a2fa60 EFLAGS: 00010246
RAX:  RBX:  RCX: 
RDX: 0020 RSI: c0415249 RDI: 9560004c
RBP: a431c0a2faa8 R08:  R09: 0006
R10: a431c0d0 R11: 0007 R12: 000fffe0
R13: 91d1170ead98 R14: 91d1014bb0c8 R15: 91d1170ead98
FS:  7fa5fe59d8c0() GS:91d7ef60() knlGS:
CS:  0010 DS:  ES:  CR0: 80050033
CR2: 000c CR3: 00011785 CR4: 00350ef0
Call Trace:
 ? __pci_set_master+0x5f/0xe0
 amd_mp2_pci_probe+0xad/0x160 [amd_sfh]
 local_pci_probe+0x48/0x80
 pci_device_probe+0x105/0x1c0
 really_probe+0x24b/0x4c0
 driver_probe_device+0xf0/0x160
 device_driver_attach+0xab/0xb0
 __driver_attach+0xb2/0x140
 ? device_driver_attach+0xb0/0xb0
 bus_for_each_dev+0x7e/0xc0
 driver_attach+0x1e/0x20
 bus_add_driver+0x135/0x1f0
 driver_register+0x95/0xf0
 ? 0xc041a000
 __pci_register_driver+0x57/0x60
 amd_mp2_pci_driver_init+0x23/0x1000 [amd_sfh]
 do_one_initcall+0x48/0x1d0
 ? kmem_cache_alloc_trace+0xfb/0x240
 do_init_module+0x62/0x290
 load_module+0xa8f/0xb10
 __do_sys_finit_module+0xc2/0x120
 __x64_sys_finit_module+0x18/0x20
 do_syscall_64+0x61/0xb0
 ? exit_to_user_mode_prepare+0x37/0xb0
 ? syscall_exit_to_user_mode+0x27/0x50
 ? __x64_sys_newfstatat+0x1c/0x20
 ? do_syscall_64+0x6e/0xb0
 entry_SYSCALL_64_after_hwframe+0x44/0xae
RIP: 0033:0x7fa5feb3394d
Code: 5b 41 5c c3 66 0f 1f 84 00 00 00 00 00 f3 0f 1e fa 48 89 f8 48 89 f7 48 
89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 
c3 48 8b 0d b3 64 0f 00 f7 d8 64 89 01 48
RSP: 002b:7ffc5ce60ba8 EFLAGS: 0246 ORIG_RAX: 0139
RAX: ffda RBX: 56027b85af40 RCX: 7fa5feb3394d
RDX:  RSI: 7fa5fecc33fe RDI: 000c
RBP: 0002 R08:  R09: 
R10: 000c R11: 0246 R12: 7fa5fecc33fe
R13: 56027b845ed0 R14: 56027b85b030 R15: 56027b84a330
Modules linked in: amd_sfh(+) i2c_hid_acpi libahci i2c_hid i2c_piix4(+) 
xhci_pci_renesas(+) nvme_core(+) wmi(+) video(+) fjes(+) hid
CR2: 000c
---[ end trace cc368d63aaf78960 ]---
RIP: 0010:amd_sfh_hid_client_init+0x47/0x350 [amd_sfh]
Code: 00 53 48 83 ec 20 48 8b 5f 08 48 8b 07 48 8d b3 22 01 00 00 4c 8d b0 c8 
00 00 00 e8 23 07 00 00 45 31 c0 31 c9 ba 00 00 20 00 <89> 43 0c 48 8d 83 68 01 
00 00 48 8d bb 80 01 00 00 48 c7 c6 20 6d
RSP: 0018:a431c0a2fa60 EFLAGS: 00010246
RAX:  RBX:  RCX: 
RDX: 0020 RSI: c0415249 RDI: 9560004c
RBP: a431c0a2faa8 R08:  R09: 0006
R10: a431c0d0 R11: 0007 R12: 000fffe0
R13: 91d1170ead98 R14: 91d1014bb0c8 R15: 91d1170ead98
FS:  7fa5fe59d8c0() GS:91d7ef60() knlGS:
CS:  0010 DS:  ES:  CR0: 80050033
CR2: 000c CR3: 00011785 CR4: 00350ef0

Still fails to boot (systemd-udev-settle hangs so ZFS BOOT fails to mount).
Can mount ZFS BOOT manually in emergency mode (after importing the pool).
But systemd does not recover complaining about a dependency cycle in its 
current transaction.
Couldn't figure out how to resolve that...

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1956519

Title:
  kernel panic after upgrading to kernel 5.13.0-23

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1956519/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs