[Kernel-packages] [Bug 1891288] Re: arm64 gcov in 5.8 breaks when trying to enable it
Upstream fix 40249c6962075c040fd071339acae524f18bfac9, this has already been picked up by Sash Levin for 5.8, 5.4, 4.19, 4.14, 4.9 and 4.8 on backport stable AUTOSEL. Lets wait for that fix to trickle into the SRU process. ** Changed in: linux (Ubuntu) Status: Won't Fix => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1891288 Title: arm64 gcov in 5.8 breaks when trying to enable it Status in Linux: Confirmed Status in linux package in Ubuntu: In Progress Bug description: Running: sudo lcov --zerocounters on a gcov enabled kernel causes a read-only splat: [ 139.798968] Unable to handle kernel write to read-only memory at virtual address b4511ee6bb10 [ 139.803325] Mem abort info: [ 139.804882] ESR = 0x964e [ 139.806265] EC = 0x25: DABT (current EL), IL = 32 bits [ 139.811261] SET = 0, FnV = 0 [ 139.814163] EA = 0, S1PTW = 0 [ 139.816545] Data abort info: [ 139.817852] ISV = 0, ISS = 0x004e [ 139.820023] CM = 0, WnR = 1 [ 139.821350] swapper pgtable: 4k pages, 48-bit VAs, pgdp=5086f000 [ 139.825005] [b4511ee6bb10] pgd=0001b6fff003, p4d=0001b6fff003, pud=0001b6ffe003, pmd=00404e200f91 [ 139.832061] Internal error: Oops: 964e [#1] SMP [ 139.835002] Modules linked in: nls_iso8859_1 dm_multipath scsi_dh_rdac scsi_dh_emc scsi_dh_alua efi_pstore qemu_fw_cfg sch_fq_codel drm virtio_rng ip_t ables x_tables autofs4 btrfs blake2b_generic raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor xor_neon raid6_pq libcrc32c rai d1 raid0 multipath linear crct10dif_ce ghash_ce sha2_ce sha256_arm64 sha1_ce virtio_net net_failover xhci_pci virtio_blk virtio_scsi failover xhci_pci_ren esas aes_neon_bs aes_neon_blk aes_ce_blk crypto_simd cryptd aes_ce_cipher [ 139.865929] CPU: 5 PID: 1235 Comm: lcov Tainted: GW 5.8.0-8-generic #9 [ 139.871293] Hardware name: QEMU KVM Virtual Machine, BIOS 0.0.0 02/06/2015 [ 139.876248] pstate: 2045 (nzCv daif +PAN -UAO BTYPE=--) [ 139.879993] pc : __memset+0x148/0x188 [ 139.882387] lr : gcov_info_reset+0xa0/0x110 [ 139.885404] sp : 8000122f3bf0 [ 139.887730] x29: 8000122f3bf0 x28: 000167480f40 [ 139.891129] x27: x26: b450e46bc060 [ 139.894688] x25: 0001 x24: b450e46bc040 [ 139.897391] x23: x22: b450e46bc0a8 [ 139.900064] x21: b45122ba5db8 x20: b450e46bc068 [ 139.902681] x19: b450e46bc068 x18: [ 139.905345] x17: x16: [ 139.908016] x15: x14: [ 139.910625] x13: x12: [ 139.913260] x11: x10: [ 139.915922] x9 : x8 : b4511ee6bb10 [ 139.918531] x7 : x6 : 003f [ 139.921196] x5 : 0040 x4 : 0030 [ 139.923852] x3 : 0007235d7fd0 x2 : 0007235d7fd0 [ 139.926460] x1 : x0 : b4511ee6bb10 [ 139.929126] Call trace: [ 139.930349] __memset+0x148/0x188 [ 139.932025] reset_node+0x70/0xc0 [ 139.933662] reset_write+0xc0/0x130 [ 139.935389] full_proxy_write+0x98/0x110 [ 139.937349] vfs_write+0x18c/0x3e0 [ 139.939031] ksys_write+0xc4/0x1f0 [ 139.940766] __arm64_sys_write+0x44/0x60 [ 139.942705] invoke_syscall+0x74/0x150 [ 139.944601] el0_svc_common.constprop.0+0x94/0x264 [ 139.946961] do_el0_svc+0x5c/0x7c [ 139.948651] el0_svc+0x70/0x114 [ 139.950206] el0_sync_handler+0x140/0x39c [ 139.952239] el0_sync+0x17c/0x180 [ 139.953894] Code: f101007f fa45a068 54fffc0b aa0303e2 (a9001d07) [ 139.956946] ---[ end trace 71e2f9cc3eaddf4e ]--- To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1891288/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1891288] Re: arm64 gcov in 5.8 breaks when trying to enable it
** Bug watch added: Linux Kernel Bug Tracker #208885 https://bugzilla.kernel.org/show_bug.cgi?id=208885 ** Also affects: linux via https://bugzilla.kernel.org/show_bug.cgi?id=208885 Importance: Unknown Status: Unknown ** Description changed: + Running: + + sudo lcov --zerocounters on a gcov enabled kernel causes a read-only + splat: + + [ 139.798968] Unable to handle kernel write to read-only memory at virtual address b4511ee6bb10 [ 139.803325] Mem abort info: [ 139.804882] ESR = 0x964e [ 139.806265] EC = 0x25: DABT (current EL), IL = 32 bits [ 139.811261] SET = 0, FnV = 0 [ 139.814163] EA = 0, S1PTW = 0 [ 139.816545] Data abort info: [ 139.817852] ISV = 0, ISS = 0x004e [ 139.820023] CM = 0, WnR = 1 [ 139.821350] swapper pgtable: 4k pages, 48-bit VAs, pgdp=5086f000 [ 139.825005] [b4511ee6bb10] pgd=0001b6fff003, p4d=0001b6fff003, pud=0001b6ffe003, pmd=00404e200f91 [ 139.832061] Internal error: Oops: 964e [#1] SMP [ 139.835002] Modules linked in: nls_iso8859_1 dm_multipath scsi_dh_rdac scsi_dh_emc scsi_dh_alua efi_pstore qemu_fw_cfg sch_fq_codel drm virtio_rng ip_t ables x_tables autofs4 btrfs blake2b_generic raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor xor_neon raid6_pq libcrc32c rai d1 raid0 multipath linear crct10dif_ce ghash_ce sha2_ce sha256_arm64 sha1_ce virtio_net net_failover xhci_pci virtio_blk virtio_scsi failover xhci_pci_ren esas aes_neon_bs aes_neon_blk aes_ce_blk crypto_simd cryptd aes_ce_cipher [ 139.865929] CPU: 5 PID: 1235 Comm: lcov Tainted: GW 5.8.0-8-generic #9 [ 139.871293] Hardware name: QEMU KVM Virtual Machine, BIOS 0.0.0 02/06/2015 [ 139.876248] pstate: 2045 (nzCv daif +PAN -UAO BTYPE=--) [ 139.879993] pc : __memset+0x148/0x188 [ 139.882387] lr : gcov_info_reset+0xa0/0x110 [ 139.885404] sp : 8000122f3bf0 - [ 139.887730] x29: 8000122f3bf0 x28: 000167480f40 - [ 139.891129] x27: x26: b450e46bc060 - [ 139.894688] x25: 0001 x24: b450e46bc040 - [ 139.897391] x23: x22: b450e46bc0a8 - [ 139.900064] x21: b45122ba5db8 x20: b450e46bc068 - [ 139.902681] x19: b450e46bc068 x18: - [ 139.905345] x17: x16: - [ 139.908016] x15: x14: - [ 139.910625] x13: x12: - [ 139.913260] x11: x10: - [ 139.915922] x9 : x8 : b4511ee6bb10 - [ 139.918531] x7 : x6 : 003f - [ 139.921196] x5 : 0040 x4 : 0030 - [ 139.923852] x3 : 0007235d7fd0 x2 : 0007235d7fd0 - [ 139.926460] x1 : x0 : b4511ee6bb10 + [ 139.887730] x29: 8000122f3bf0 x28: 000167480f40 + [ 139.891129] x27: x26: b450e46bc060 + [ 139.894688] x25: 0001 x24: b450e46bc040 + [ 139.897391] x23: x22: b450e46bc0a8 + [ 139.900064] x21: b45122ba5db8 x20: b450e46bc068 + [ 139.902681] x19: b450e46bc068 x18: + [ 139.905345] x17: x16: + [ 139.908016] x15: x14: + [ 139.910625] x13: x12: + [ 139.913260] x11: x10: + [ 139.915922] x9 : x8 : b4511ee6bb10 + [ 139.918531] x7 : x6 : 003f + [ 139.921196] x5 : 0040 x4 : 0030 + [ 139.923852] x3 : 0007235d7fd0 x2 : 0007235d7fd0 + [ 139.926460] x1 : x0 : b4511ee6bb10 [ 139.929126] Call trace: [ 139.930349] __memset+0x148/0x188 [ 139.932025] reset_node+0x70/0xc0 [ 139.933662] reset_write+0xc0/0x130 [ 139.935389] full_proxy_write+0x98/0x110 [ 139.937349] vfs_write+0x18c/0x3e0 [ 139.939031] ksys_write+0xc4/0x1f0 [ 139.940766] __arm64_sys_write+0x44/0x60 [ 139.942705] invoke_syscall+0x74/0x150 [ 139.944601] el0_svc_common.constprop.0+0x94/0x264 [ 139.946961] do_el0_svc+0x5c/0x7c [ 139.948651] el0_svc+0x70/0x114 [ 139.950206] el0_sync_handler+0x140/0x39c [ 139.952239] el0_sync+0x17c/0x180 - [ 139.953894] Code: f101007f fa45a068 54fffc0b aa0303e2 (a9001d07) + [ 139.953894] Code: f101007f fa45a068 54fffc0b aa0303e2 (a9001d07) [ 139.956946] ---[ end trace 71e2f9cc3eaddf4e ]--- -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1891288 Title: arm64 gcov in 5.8 breaks when trying to enable it Status in Linux: Unknown Status in linux package in Ubuntu: In Progress Bug description: Running: sudo lcov --zerocounters on a gcov enabled kernel causes a read-only splat:
[Kernel-packages] [Bug 1891288] Re: arm64 gcov in 5.8 breaks when trying to enable it
Ah, earlier on boot I'm seeing: [8.808508] virtio_blk virtio3: [vda] 209715200 512-byte logical blocks (107 GB/100 GiB) [8.808649] [ cut here ] [8.815777] vda: detected capacity change from 0 to 107374182400 [8.816623] WARNING: CPU: 3 PID: 212 at mm/page_alloc.c:4813 __alloc_pages_nodemask+0x540/0x694 [8.816630] Modules linked in: net_failover virtio_blk(+) xhci_pci_renesas virtio_scsi(+) failover fjes(-) aes_neon_bs aes_neon_blk aes_ce_blk crypto_s imd cryptd aes_ce_cipher [8.837701] CPU: 3 PID: 212 Comm: systemd-udevd Not tainted 5.8.0-8-generic #9 [8.842236] Hardware name: QEMU KVM Virtual Machine, BIOS 0.0.0 02/06/2015 [8.846585] pstate: 2045 (nzCv daif +PAN -UAO BTYPE=--) [8.850112] pc : __alloc_pages_nodemask+0x540/0x694 [8.853106] lr : alloc_pages_current+0xe0/0x17c [8.856024] sp : 8000106138c0 [8.858175] x29: 8000106138c0 x28: 000170252dc0 [8.861565] x27: x26: 0015 [8.865006] x25: 0001abcfef80 x24: 0015 [8.868466] x23: 000170252dc0 x22: [8.871794] x21: db2796703050 x20: 00040dc0 [8.875143] x19: db2796703250 x18: [8.878529] x17: x16: [8.881917] x15: x14: 73656a662f74656e [8.885218] x13: 2f73726576697264 x12: 2f636972656e6567 [8.888554] x11: 2d646c6975622f64 x10: 6c6975622f6e6169 [8.892032] x9 : db2792b6dfa4 x8 : 63672e7366677562 [8.895415] x7 : 65645f73656a662f x6 : 0001558ef353 [8.898814] x5 : 0018 x4 : 0dd5 [8.902124] x3 : db27966ea138 x2 : 0001 [8.905418] x1 : db27966ea030 x0 : 0001 [8.908698] Call trace: [8.910278] __alloc_pages_nodemask+0x540/0x694 [8.913278] alloc_pages_current+0xe0/0x17c [8.915967] kmalloc_order+0x48/0xec [8.918325] kmalloc_order_trace+0x54/0x21c [8.921165] __kmalloc+0x454/0x5c0 [8.923368] kmalloc_array.constprop.0+0x30/0x50 [8.926301] gcov_info_dup+0x98/0x2c0 [8.928557] remove_info+0x1e0/0x244 [8.930876] gcov_event+0xfc/0x170 [8.933097] gcov_module_notifier+0x164/0x174 [8.935848] notifier_call_chain+0xa0/0x110 [8.938435] blocking_notifier_call_chain+0x80/0xe0 [8.941579] do_init_module+0x360/0x43c [8.944198] load_module+0x8fc/0xa50 [8.946591] __do_sys_finit_module+0x190/0x1c0 [8.949485] __arm64_sys_finit_module+0x48/0x64 [8.952376] invoke_syscall+0x74/0x150 [8.954901] el0_svc_common.constprop.0+0x94/0x264 [8.956405] sr 0:0:0:0: Power-on or device reset occurred [8.957610] do_el0_svc+0x5c/0x7c [8.960983] sr 0:0:0:0: [sr0] scsi3-mmc drive: 16x/50x cd/rw xa/form2 cdda tray [8.962169] el0_svc+0x70/0x114 [8.965694] cdrom: Uniform CD-ROM driver Revision: 3.20 [8.967253] el0_sync_handler+0x140/0x39c [8.971738] el0_sync+0x17c/0x180 [8.973450] ---[ end trace 267579295e47a82a ]--- [8.976042] gcov: could not save data for '/home/cking/unstable/debian/build/build-generic/drivers/net/fjes/fjes_debugfs.gcda' (out of memory) [8.986263] gcov: could not save data for '/home/cking/unstable/debian/build/build-generic/drivers/net/fjes/fjes_trace.gcda' (out of memory) [8.996162] gcov: could not save data for '/home/cking/unstable/debian/build/build-generic/drivers/net/fjes/fjes_ethtool.gcda' (out of memory) [9.006231] gcov: could not save data for '/home/cking/unstable/debian/build/build-generic/drivers/net/fjes/fjes_hw.gcda' (out of memory) [9.010491] sr 0:0:0:0: Attached scsi CD-ROM sr0 [9.013246] sr 0:0:0:0: Attached scsi generic sg0 type 5 [9.014959] gcov: could not save data for '/home/cking/unstable/debian/build/build-generic/drivers/net/fjes/fjes_main.gcda' (out of memory) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1891288 Title: arm64 gcov in 5.8 breaks when trying to enable it Status in Linux: Unknown Status in linux package in Ubuntu: In Progress Bug description: Running: sudo lcov --zerocounters on a gcov enabled kernel causes a read-only splat: [ 139.798968] Unable to handle kernel write to read-only memory at virtual address b4511ee6bb10 [ 139.803325] Mem abort info: [ 139.804882] ESR = 0x964e [ 139.806265] EC = 0x25: DABT (current EL), IL = 32 bits [ 139.811261] SET = 0, FnV = 0 [ 139.814163] EA = 0, S1PTW = 0 [ 139.816545] Data abort info: [ 139.817852] ISV = 0, ISS = 0x004e [ 139.820023] CM = 0, WnR = 1 [ 139.821350] swapper pgtable: 4k pages, 48-bit VAs, pgdp=5086f000 [ 139.825005] [b4511ee6bb10] pgd=0001b6fff003, p4d=0001b6fff003, pud=0001b6ffe003, pmd=00404e200f91 [ 139.832061] Internal error: Oops: 964e [#1] SMP [
[Kernel-packages] [Bug 1891288] Re: arm64 gcov in 5.8 breaks when trying to enable it
Launchpad has imported 3 comments from the remote bug at https://bugzilla.kernel.org/show_bug.cgi?id=208885. If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at https://help.launchpad.net/InterBugTracking. On 2020-08-12T09:10:41+00:00 colin.king wrote: 5.8 kernel running on a QEMU KVM Virtual Machine, arm64, gcov enabled: CONFIG_GCOV_KERNEL=y CONFIG_ARCH_HAS_GCOV_PROFILE_ALL=y CONFIG_GCOV_PROFILE_ALL=y running: sudo lcov --zerocounters ..causes the following splat: [ 78.634926] Unable to handle kernel write to read-only memory at virtual address d764f255bb10 [ 78.639076] Mem abort info: [ 78.640313] ESR = 0x964e [ 78.641656] EC = 0x25: DABT (current EL), IL = 32 bits [ 78.644351] SET = 0, FnV = 0 [ 78.645766] EA = 0, S1PTW = 0 [ 78.649526] Data abort info: [ 78.654341] ISV = 0, ISS = 0x004e [ 78.656851] CM = 0, WnR = 1 [ 78.659043] swapper pgtable: 4k pages, 48-bit VAs, pgdp=b775f000 [ 78.665822] [d764f255bb10] pgd=0001b6fff003, p4d=0001b6fff003, pud=0001b6ffe003, pmd=0040b5000f91 [ 78.677367] Internal error: Oops: 964e [#1] SMP [ 78.681204] Modules linked in: nls_iso8859_1 dm_multipath scsi_dh_rdac scsi_dh_emc scsi_dh_alua efi_pstore qemu_fw_cfg sch_fq_codel drm virtio_rng ip_t ables x_tables autofs4 btrfs blake2b_generic raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor xor_neon raid6_pq libcrc32c rai d1 raid0 multipath linear crct10dif_ce ghash_ce sha2_ce sha256_arm64 sha1_ce virtio_net xhci_pci net_failover virtio_blk virtio_scsi failover xhci_pci_ren esas aes_neon_bs aes_neon_blk aes_ce_blk crypto_simd cryptd aes_ce_cipher [ 78.722642] CPU: 14 PID: 1175 Comm: lcov Tainted: GW 5.8.0-8-generic #9 [ 78.729364] Hardware name: QEMU KVM Virtual Machine, BIOS 0.0.0 02/06/2015 [ 78.733467] pstate: 2045 (nzCv daif +PAN -UAO BTYPE=--) [ 78.736219] pc : __memset+0x148/0x188 [ 78.737993] lr : gcov_info_reset+0xa0/0x110 [ 78.740037] sp : 800010e53bf0 [ 78.741624] x29: 800010e53bf0 x28: 00015a648000 [ 78.744181] x27: x26: d764e3df4060 [ 78.746776] x25: 0001 x24: d764e3df4040 [ 78.749310] x23: x22: d764e3df40a8 [ 78.751976] x21: d764f6295db8 x20: d764e3df4068 [ 78.754642] x19: d764e3df4068 x18: [ 78.757265] x17: x16: [ 78.759922] x15: x14: [ 78.762585] x13: x12: [ 78.765209] x11: x10: [ 78.767861] x9 : x8 : d764f255bb10 [ 78.770518] x7 : x6 : 003f [ 78.773135] x5 : 0040 x4 : 0030 [ 78.775793] x3 : 00071ef97fd0 x2 : 00071ef97fd0 [ 78.778449] x1 : x0 : d764f255bb10 [ 78.781075] Call trace: [ 78.782329] __memset+0x148/0x188 [ 78.783980] reset_node+0x70/0xc0 [ 78.785628] reset_write+0xc0/0x130 [ 78.787397] full_proxy_write+0x98/0x110 [ 78.789354] vfs_write+0x18c/0x3e0 [ 78.791086] ksys_write+0xc4/0x1f0 [ 78.792778] __arm64_sys_write+0x44/0x60 [ 78.794771] invoke_syscall+0x74/0x150 [ 78.796639] el0_svc_common.constprop.0+0x94/0x264 [ 78.799049] do_el0_svc+0x5c/0x7c [ 78.800702] el0_svc+0x70/0x114 [ 78.802311] el0_sync_handler+0x140/0x39c [ 78.804304] el0_sync+0x17c/0x180 [ 78.805967] Code: f101007f fa45a068 54fffc0b aa0303e2 (a9001d07) [ 78.809019] ---[ end trace b9a826b707c133e4 ]--- Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1891288/comments/1 On 2020-08-12T09:17:59+00:00 colin.king wrote: Just spotted that earlier in the boot we get: [8.808508] virtio_blk virtio3: [vda] 209715200 512-byte logical blocks (107 GB/100 GiB) [8.808649] [ cut here ] [8.815777] vda: detected capacity change from 0 to 107374182400 [8.816623] WARNING: CPU: 3 PID: 212 at mm/page_alloc.c:4813 __alloc_pages_nodemask+0x540/0x694 [8.816630] Modules linked in: net_failover virtio_blk(+) xhci_pci_renesas virtio_scsi(+) failover fjes(-) aes_neon_bs aes_neon_blk aes_ce_blk crypto_s imd cryptd aes_ce_cipher [8.837701] CPU: 3 PID: 212 Comm: systemd-udevd Not tainted 5.8.0-8-generic #9 [8.842236] Hardware name: QEMU KVM Virtual Machine, BIOS 0.0.0 02/06/2015 [8.846585] pstate: 2045 (nzCv daif +PAN -UAO BTYPE=--) [8.850112] pc : __alloc_pages_nodemask+0x540/0x694 [8.853106] lr : alloc_pages_current+0xe0/0x17c [8.856024] sp : 8000106138c0 [8.858175] x29: 8000106138c0 x28: 000170252dc0 [8.861565] x27
[Kernel-packages] [Bug 1891288] Re: arm64 gcov in 5.8 breaks when trying to enable it
Fix applied in risc-v groovy with commit 4fc484ffd959e0d897d073296cfcfafdf473e407 ** Changed in: linux (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1891288 Title: arm64 gcov in 5.8 breaks when trying to enable it Status in Linux: Confirmed Status in linux package in Ubuntu: Fix Released Bug description: Running: sudo lcov --zerocounters on a gcov enabled kernel causes a read-only splat: [ 139.798968] Unable to handle kernel write to read-only memory at virtual address b4511ee6bb10 [ 139.803325] Mem abort info: [ 139.804882] ESR = 0x964e [ 139.806265] EC = 0x25: DABT (current EL), IL = 32 bits [ 139.811261] SET = 0, FnV = 0 [ 139.814163] EA = 0, S1PTW = 0 [ 139.816545] Data abort info: [ 139.817852] ISV = 0, ISS = 0x004e [ 139.820023] CM = 0, WnR = 1 [ 139.821350] swapper pgtable: 4k pages, 48-bit VAs, pgdp=5086f000 [ 139.825005] [b4511ee6bb10] pgd=0001b6fff003, p4d=0001b6fff003, pud=0001b6ffe003, pmd=00404e200f91 [ 139.832061] Internal error: Oops: 964e [#1] SMP [ 139.835002] Modules linked in: nls_iso8859_1 dm_multipath scsi_dh_rdac scsi_dh_emc scsi_dh_alua efi_pstore qemu_fw_cfg sch_fq_codel drm virtio_rng ip_t ables x_tables autofs4 btrfs blake2b_generic raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor xor_neon raid6_pq libcrc32c rai d1 raid0 multipath linear crct10dif_ce ghash_ce sha2_ce sha256_arm64 sha1_ce virtio_net net_failover xhci_pci virtio_blk virtio_scsi failover xhci_pci_ren esas aes_neon_bs aes_neon_blk aes_ce_blk crypto_simd cryptd aes_ce_cipher [ 139.865929] CPU: 5 PID: 1235 Comm: lcov Tainted: GW 5.8.0-8-generic #9 [ 139.871293] Hardware name: QEMU KVM Virtual Machine, BIOS 0.0.0 02/06/2015 [ 139.876248] pstate: 2045 (nzCv daif +PAN -UAO BTYPE=--) [ 139.879993] pc : __memset+0x148/0x188 [ 139.882387] lr : gcov_info_reset+0xa0/0x110 [ 139.885404] sp : 8000122f3bf0 [ 139.887730] x29: 8000122f3bf0 x28: 000167480f40 [ 139.891129] x27: x26: b450e46bc060 [ 139.894688] x25: 0001 x24: b450e46bc040 [ 139.897391] x23: x22: b450e46bc0a8 [ 139.900064] x21: b45122ba5db8 x20: b450e46bc068 [ 139.902681] x19: b450e46bc068 x18: [ 139.905345] x17: x16: [ 139.908016] x15: x14: [ 139.910625] x13: x12: [ 139.913260] x11: x10: [ 139.915922] x9 : x8 : b4511ee6bb10 [ 139.918531] x7 : x6 : 003f [ 139.921196] x5 : 0040 x4 : 0030 [ 139.923852] x3 : 0007235d7fd0 x2 : 0007235d7fd0 [ 139.926460] x1 : x0 : b4511ee6bb10 [ 139.929126] Call trace: [ 139.930349] __memset+0x148/0x188 [ 139.932025] reset_node+0x70/0xc0 [ 139.933662] reset_write+0xc0/0x130 [ 139.935389] full_proxy_write+0x98/0x110 [ 139.937349] vfs_write+0x18c/0x3e0 [ 139.939031] ksys_write+0xc4/0x1f0 [ 139.940766] __arm64_sys_write+0x44/0x60 [ 139.942705] invoke_syscall+0x74/0x150 [ 139.944601] el0_svc_common.constprop.0+0x94/0x264 [ 139.946961] do_el0_svc+0x5c/0x7c [ 139.948651] el0_svc+0x70/0x114 [ 139.950206] el0_sync_handler+0x140/0x39c [ 139.952239] el0_sync+0x17c/0x180 [ 139.953894] Code: f101007f fa45a068 54fffc0b aa0303e2 (a9001d07) [ 139.956946] ---[ end trace 71e2f9cc3eaddf4e ]--- To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1891288/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1891288] Re: arm64 gcov in 5.8 breaks when trying to enable it
This is due to using gcc-10.2. Building with gcc-9 is fine. This compiler support for GCOV will be disabled, see https://lkml.org/lkml/2020/9/2/934 So, marking this as Won't Fix because there is a workaround and 10.2 is not looking favourably for GCOV support at the moment. ** Changed in: linux (Ubuntu) Status: In Progress => Won't Fix -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1891288 Title: arm64 gcov in 5.8 breaks when trying to enable it Status in Linux: Confirmed Status in linux package in Ubuntu: Won't Fix Bug description: Running: sudo lcov --zerocounters on a gcov enabled kernel causes a read-only splat: [ 139.798968] Unable to handle kernel write to read-only memory at virtual address b4511ee6bb10 [ 139.803325] Mem abort info: [ 139.804882] ESR = 0x964e [ 139.806265] EC = 0x25: DABT (current EL), IL = 32 bits [ 139.811261] SET = 0, FnV = 0 [ 139.814163] EA = 0, S1PTW = 0 [ 139.816545] Data abort info: [ 139.817852] ISV = 0, ISS = 0x004e [ 139.820023] CM = 0, WnR = 1 [ 139.821350] swapper pgtable: 4k pages, 48-bit VAs, pgdp=5086f000 [ 139.825005] [b4511ee6bb10] pgd=0001b6fff003, p4d=0001b6fff003, pud=0001b6ffe003, pmd=00404e200f91 [ 139.832061] Internal error: Oops: 964e [#1] SMP [ 139.835002] Modules linked in: nls_iso8859_1 dm_multipath scsi_dh_rdac scsi_dh_emc scsi_dh_alua efi_pstore qemu_fw_cfg sch_fq_codel drm virtio_rng ip_t ables x_tables autofs4 btrfs blake2b_generic raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor xor_neon raid6_pq libcrc32c rai d1 raid0 multipath linear crct10dif_ce ghash_ce sha2_ce sha256_arm64 sha1_ce virtio_net net_failover xhci_pci virtio_blk virtio_scsi failover xhci_pci_ren esas aes_neon_bs aes_neon_blk aes_ce_blk crypto_simd cryptd aes_ce_cipher [ 139.865929] CPU: 5 PID: 1235 Comm: lcov Tainted: GW 5.8.0-8-generic #9 [ 139.871293] Hardware name: QEMU KVM Virtual Machine, BIOS 0.0.0 02/06/2015 [ 139.876248] pstate: 2045 (nzCv daif +PAN -UAO BTYPE=--) [ 139.879993] pc : __memset+0x148/0x188 [ 139.882387] lr : gcov_info_reset+0xa0/0x110 [ 139.885404] sp : 8000122f3bf0 [ 139.887730] x29: 8000122f3bf0 x28: 000167480f40 [ 139.891129] x27: x26: b450e46bc060 [ 139.894688] x25: 0001 x24: b450e46bc040 [ 139.897391] x23: x22: b450e46bc0a8 [ 139.900064] x21: b45122ba5db8 x20: b450e46bc068 [ 139.902681] x19: b450e46bc068 x18: [ 139.905345] x17: x16: [ 139.908016] x15: x14: [ 139.910625] x13: x12: [ 139.913260] x11: x10: [ 139.915922] x9 : x8 : b4511ee6bb10 [ 139.918531] x7 : x6 : 003f [ 139.921196] x5 : 0040 x4 : 0030 [ 139.923852] x3 : 0007235d7fd0 x2 : 0007235d7fd0 [ 139.926460] x1 : x0 : b4511ee6bb10 [ 139.929126] Call trace: [ 139.930349] __memset+0x148/0x188 [ 139.932025] reset_node+0x70/0xc0 [ 139.933662] reset_write+0xc0/0x130 [ 139.935389] full_proxy_write+0x98/0x110 [ 139.937349] vfs_write+0x18c/0x3e0 [ 139.939031] ksys_write+0xc4/0x1f0 [ 139.940766] __arm64_sys_write+0x44/0x60 [ 139.942705] invoke_syscall+0x74/0x150 [ 139.944601] el0_svc_common.constprop.0+0x94/0x264 [ 139.946961] do_el0_svc+0x5c/0x7c [ 139.948651] el0_svc+0x70/0x114 [ 139.950206] el0_sync_handler+0x140/0x39c [ 139.952239] el0_sync+0x17c/0x180 [ 139.953894] Code: f101007f fa45a068 54fffc0b aa0303e2 (a9001d07) [ 139.956946] ---[ end trace 71e2f9cc3eaddf4e ]--- To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1891288/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
