Re: [Kernel-packages] [Bug 1822871] Re: enabling ftrace on Hi1620 CS causes an Oops
On Tue, 9 Apr 2019 at 16:30, dann frazier wrote: > > Yeah, no crash anymore - thanks Ard! > > ubuntu@d06-4:~$ echo function | sudo tee > /sys/kernel/debug/tracing/current_tracer > function > [ 72.778123] ftrace: far branches to multiple entry points unsupported > inside a single module > > ^ I assume this is expected > Uhm, not really. You don't have any out of tree live patching code in your kernel, right? > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1822871 > > Title: > enabling ftrace on Hi1620 CS causes an Oops > > Status in linux package in Ubuntu: > Confirmed > > Bug description: > [Impact] > Attempting to enable the function tracer causes an Oops. This impacts the > current disco kernel, as well as latest upstream > (@5e7a8ca319268a70a6c7c3c1fde5bea38e1e5539). > > This is 100% reproducible on D06 CS systems, but not reproducible on > D06 ES systems (the previous silicon rev). > > [Test Case] > $ echo function | sudo tee /sys/kernel/debug/tracing/current_tracer > > [ 3125.651453] kernel BUG at arch/arm64/kernel/insn.c:1325! > [ 3125.656766] Internal error: Oops - BUG: 0 [#1] SMP > [ 3125.661551] Modules linked in: nls_iso8859_1 ipmi_ssif joydev input_leds > tpm_tis_spi hns_roce_hw_v2 hns_roce ib_uverbs spi_dw_mmio ipmi_si spi_dw > ipmi_devintf ipmi_msghandler cppc_cpufreq sch_fq_codel ib_iser rdma_cm iw_cm > ib_cm ib_core iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi ip_tables > x_tables autofs4 btrfs zstd_compress raid10 raid456 async_raid6_recov > async_memcpy async_pq async_xor async_tx xor xor_neon raid6_pq libcrc32c > raid1 raid0 multipath linear ses enclosure marvell aes_ce_blk aes_ce_cipher > hibmc_drm hid_generic ttm crct10dif_ce drm_kms_helper ghash_ce sha2_ce > syscopyarea sha256_arm64 sysfillrect ixgbe igb sha1_ce hns3 sysimgblt usbhid > fb_sys_fops hisi_sas_v3_hw hclge i2c_algo_bit xfrm_algo hisi_sas_main mdio > hid drm hnae3 libsas ahci scsi_transport_sas hinic gpio_dwapb aes_neon_bs > aes_neon_blk crypto_simd cryptd aes_arm64 > [ 3125.736544] CPU: 124 PID: 3306 Comm: tee Not tainted 5.0.0-rc4+ #12 > [ 3125.742802] Hardware name: Huawei TaiShan 2280 V2/BC82AMDA, BIOS TA BIOS > 2280-A CS V2.16.01 03/16/2019 > [ 3125.752099] pstate: 0049 (nzcv daif +PAN -UAO) > [ 3125.756893] pc : aarch64_insn_adrp_get_offset+0x34/0x38 > [ 3125.762111] lr : plt_entries_equal.part.3+0x40/0x80 > [ 3125.766979] sp : 2837b9f0 > [ 3125.770286] x29: 2837b9f0 x28: bef4fd20d880 > [ 3125.775591] x27: x26: > [ 3125.780896] x25: dea2a7e8 x24: 3dceb8413000 > [ 3125.786200] x23: 0002 x22: 3dce9d2289a4 > [ 3125.791504] x21: 2837ba8c x20: 2837b000 > [ 3125.796808] x19: 3dce9d228000 x18: > [ 3125.802112] x17: x16: 3dceb7742780 > [ 3125.807416] x15: 3dceb7ce7c38 x14: 0001 > [ 3125.812720] x13: bef50bb9e188 x12: > [ 3125.818023] x11: 7efba3e79608 x10: 0a70 > [ 3125.823327] x9 : 3dceb6deeacc x8 : > [ 3125.828631] x7 : 0005 x6 : 3dceb8413f10 > [ 3125.833935] x5 : 002b3000 x4 : 3dceb6f4f4b8 > [ 3125.839239] x3 : x2 : 9000 > [ 3125.844543] x1 : x0 : > [ 3125.849850] Process tee (pid: 3306, stack limit = 0x262bb476) > [ 3125.856281] Call trace: > [ 3125.858723] aarch64_insn_adrp_get_offset+0x34/0x38 > [ 3125.863593] plt_entries_equal.part.3+0x40/0x80 > [ 3125.868115] plt_entries_equal+0x5c/0x70 > [ 3125.872031] ftrace_make_call+0xf0/0x150 > [ 3125.875950] __ftrace_replace_code+0xe8/0xf8 > [ 3125.880212] ftrace_replace_code+0x64/0xc0 > [ 3125.884301] ftrace_modify_all_code+0xb0/0x148 > [ 3125.888738] arch_ftrace_update_code+0x10/0x18 > [ 3125.893174] ftrace_run_update_code+0x20/0x70 > [ 3125.897524] ftrace_startup_enable+0x4c/0x58 > [ 3125.901788] ftrace_startup+0xa4/0x140 > [ 3125.905531] register_ftrace_function+0x64/0x80 > [ 3125.910059] function_trace_init+0x50/0x98 > [ 3125.914149] tracing_set_tracer+0xf4/0x1c0 > [ 3125.918238] tracing_set_trace_write+0x10c/0x168 > [ 3125.922852] __vfs_write+0x60/0x1a8 > [ 3125.926333] vfs_write+0xac/0x1b8 > [ 3125.929641] ksys_write+0x6c/0xd8 > [ 3125.932949] __arm64_sys_write+0x24/0x30 > [ 3125.936866] el0_svc_common+0x78/0x120 > [ 3125.940608] el0_svc_handler+0x38/0x78 > [ 3125.944349] el0_svc+0x8/0xc > [ 3125.947224] Code: 97fffb33 53144c00 a8c17bfd d65f03c0 (d421) > [ 3125.953312] ---[ end trace 0872d3e5933385e2 ]--- > > [Fix] > TBD > > [Regression Risk] > TBD > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1822871/+subscriptions -- You received this bug notification because you are a
[Kernel-packages] [Bug 1822871] Re: enabling ftrace on Hi1620 CS causes an Oops
Does this fix the issue? https://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git/commit/?h =for-next/fixes=5a3ae7b314a2259b1188b22b392f5eba01e443ee -- 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/1822871 Title: enabling ftrace on Hi1620 CS causes an Oops Status in linux package in Ubuntu: Confirmed Bug description: [Impact] Attempting to enable the function tracer causes an Oops. This impacts the current disco kernel, as well as latest upstream (@5e7a8ca319268a70a6c7c3c1fde5bea38e1e5539). This is 100% reproducible on D06 CS systems, but not reproducible on D06 ES systems (the previous silicon rev). [Test Case] $ echo function | sudo tee /sys/kernel/debug/tracing/current_tracer [ 3125.651453] kernel BUG at arch/arm64/kernel/insn.c:1325! [ 3125.656766] Internal error: Oops - BUG: 0 [#1] SMP [ 3125.661551] Modules linked in: nls_iso8859_1 ipmi_ssif joydev input_leds tpm_tis_spi hns_roce_hw_v2 hns_roce ib_uverbs spi_dw_mmio ipmi_si spi_dw ipmi_devintf ipmi_msghandler cppc_cpufreq sch_fq_codel ib_iser rdma_cm iw_cm ib_cm ib_core iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi ip_tables x_tables autofs4 btrfs zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor xor_neon raid6_pq libcrc32c raid1 raid0 multipath linear ses enclosure marvell aes_ce_blk aes_ce_cipher hibmc_drm hid_generic ttm crct10dif_ce drm_kms_helper ghash_ce sha2_ce syscopyarea sha256_arm64 sysfillrect ixgbe igb sha1_ce hns3 sysimgblt usbhid fb_sys_fops hisi_sas_v3_hw hclge i2c_algo_bit xfrm_algo hisi_sas_main mdio hid drm hnae3 libsas ahci scsi_transport_sas hinic gpio_dwapb aes_neon_bs aes_neon_blk crypto_simd cryptd aes_arm64 [ 3125.736544] CPU: 124 PID: 3306 Comm: tee Not tainted 5.0.0-rc4+ #12 [ 3125.742802] Hardware name: Huawei TaiShan 2280 V2/BC82AMDA, BIOS TA BIOS 2280-A CS V2.16.01 03/16/2019 [ 3125.752099] pstate: 0049 (nzcv daif +PAN -UAO) [ 3125.756893] pc : aarch64_insn_adrp_get_offset+0x34/0x38 [ 3125.762111] lr : plt_entries_equal.part.3+0x40/0x80 [ 3125.766979] sp : 2837b9f0 [ 3125.770286] x29: 2837b9f0 x28: bef4fd20d880 [ 3125.775591] x27: x26: [ 3125.780896] x25: dea2a7e8 x24: 3dceb8413000 [ 3125.786200] x23: 0002 x22: 3dce9d2289a4 [ 3125.791504] x21: 2837ba8c x20: 2837b000 [ 3125.796808] x19: 3dce9d228000 x18: [ 3125.802112] x17: x16: 3dceb7742780 [ 3125.807416] x15: 3dceb7ce7c38 x14: 0001 [ 3125.812720] x13: bef50bb9e188 x12: [ 3125.818023] x11: 7efba3e79608 x10: 0a70 [ 3125.823327] x9 : 3dceb6deeacc x8 : [ 3125.828631] x7 : 0005 x6 : 3dceb8413f10 [ 3125.833935] x5 : 002b3000 x4 : 3dceb6f4f4b8 [ 3125.839239] x3 : x2 : 9000 [ 3125.844543] x1 : x0 : [ 3125.849850] Process tee (pid: 3306, stack limit = 0x262bb476) [ 3125.856281] Call trace: [ 3125.858723] aarch64_insn_adrp_get_offset+0x34/0x38 [ 3125.863593] plt_entries_equal.part.3+0x40/0x80 [ 3125.868115] plt_entries_equal+0x5c/0x70 [ 3125.872031] ftrace_make_call+0xf0/0x150 [ 3125.875950] __ftrace_replace_code+0xe8/0xf8 [ 3125.880212] ftrace_replace_code+0x64/0xc0 [ 3125.884301] ftrace_modify_all_code+0xb0/0x148 [ 3125.888738] arch_ftrace_update_code+0x10/0x18 [ 3125.893174] ftrace_run_update_code+0x20/0x70 [ 3125.897524] ftrace_startup_enable+0x4c/0x58 [ 3125.901788] ftrace_startup+0xa4/0x140 [ 3125.905531] register_ftrace_function+0x64/0x80 [ 3125.910059] function_trace_init+0x50/0x98 [ 3125.914149] tracing_set_tracer+0xf4/0x1c0 [ 3125.918238] tracing_set_trace_write+0x10c/0x168 [ 3125.922852] __vfs_write+0x60/0x1a8 [ 3125.926333] vfs_write+0xac/0x1b8 [ 3125.929641] ksys_write+0x6c/0xd8 [ 3125.932949] __arm64_sys_write+0x24/0x30 [ 3125.936866] el0_svc_common+0x78/0x120 [ 3125.940608] el0_svc_handler+0x38/0x78 [ 3125.944349] el0_svc+0x8/0xc [ 3125.947224] Code: 97fffb33 53144c00 a8c17bfd d65f03c0 (d421) [ 3125.953312] ---[ end trace 0872d3e5933385e2 ]--- [Fix] TBD [Regression Risk] TBD To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1822871/+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 1775884] Re: Network installs fail on SocioNext board
Thanks Dann. I can HTTP boot that mini.iso fine on my rev 0.2 Developerbox. ** Tags removed: verification-needed-bionic ** Tags added: verification-done-bionic -- 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/1775884 Title: Network installs fail on SocioNext board Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: Fix Committed Bug description: [Impact] It is not possible to perform a network install over the onboard NIC. [Test Case] Perform a d-i network install. [Fix] There are fixes for this upstream that cleanly cherry-pick back to bionic's kernel. [Regression Risk] Fixes are restricted to the netsec driver that is only currently used for the NIC on this system. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1775884/+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
Re: [Kernel-packages] [Bug 1775884] Re: Network installs fail on SocioNext board
On 14 June 2018 at 13:02, Brad Figg wrote: > This bug is awaiting verification that the kernel in -proposed solves > the problem. Please test the kernel and update this bug with the > results. If the problem is solved, change the tag 'verification-needed- > bionic' to 'verification-done-bionic'. If the problem still exists, > change the tag 'verification-needed-bionic' to 'verification-failed- > bionic'. > > If verification is not done by 5 working days from today, this fix will > be dropped from the source code, and this bug will be closed. > Thanks for the head's up. Where can I find a mini.iso installer that incorporates these fixes? > See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how > to enable and use -proposed. Thank you! > > > ** Tags added: verification-needed-bionic > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1775884 > > Title: > Network installs fail on SocioNext board > > Status in linux package in Ubuntu: > In Progress > Status in linux source package in Bionic: > Fix Committed > > Bug description: > [Impact] > It is not possible to perform a network install over the onboard NIC. > > [Test Case] > Perform a d-i network install. > > [Fix] > There are fixes for this upstream that cleanly cherry-pick back to bionic's > kernel. > > [Regression Risk] > Fixes are restricted to the netsec driver that is only currently used for > the NIC on this system. > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1775884/+subscriptions -- 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/1775884 Title: Network installs fail on SocioNext board Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: Fix Committed Bug description: [Impact] It is not possible to perform a network install over the onboard NIC. [Test Case] Perform a d-i network install. [Fix] There are fixes for this upstream that cleanly cherry-pick back to bionic's kernel. [Regression Risk] Fixes are restricted to the netsec driver that is only currently used for the NIC on this system. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1775884/+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 1692548] Re: Marvell MacchiatoBin crashes in fintek_8250_probe()
Previous kernels produced a crash like this one: Serial: 8250/16550 driver, 32 ports, IRQ sharing enabled console [ttyS0] disabled Unable to handle kernel paging request at virtual address 7dfffee0004e pgd = 1f2542365000 [7dfffee0004e] *pgd=00013745c003, *pud=00013745d003, *pmd= Internal error: Oops: 9646 [#1] SMP Modules linked in: CPU: 2 PID: 1 Comm: swapper/0 Not tainted 4.10.0-21-generic #23-Ubuntu Hardware name: Marvell 8040 MACHIATOBin (DT) task: a360ec97c600 task.stack: a360eca0 PC is at fintek_8250_enter_key+0x58/0x80 LR is at fintek_8250_enter_key+0x40/0x80 This is no longer the case with the fix applied. ** Tags removed: verification-needed-zesty ** Tags added: verification-done-zesty -- 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/1692548 Title: Marvell MacchiatoBin crashes in fintek_8250_probe() Status in linux package in Ubuntu: Fix Committed Status in linux source package in Zesty: Fix Committed Bug description: [Impact] The Marvell MacchiatoBin community board fails to boot with Ubuntu 17.04 due to a crash in the Fintek 8250 driver. [Test Case] Boot Ubuntu 17.04 on a Marvell MacchiatoBin board in UEFI/ACPI mode, check for crash. [Regression Risk] Fix looks straightforward to me - it avoids probing a PIO-only driver if the port is non-PIO, thus avoiding a crash on platforms where native PIO is unsupported. The fix is upstream and CC'd for stable, so there should be upstream support for any regressions it were to cause. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1692548/+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 1692548] Re: Marvell MacchiatoBin crashes in fintek_8250_probe()
For the record, DT boot is equally affected, even though the fix mentions ACPI _HIDs etc -- 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/1692548 Title: Marvell MacchiatoBin crashes in fintek_8250_probe() Status in linux package in Ubuntu: In Progress Status in linux source package in Zesty: In Progress Bug description: [Impact] The Marvell MacchiatoBin community board fails to boot with Ubuntu 17.04 due to a crash in the Fintek 8250 driver. [Test Case] Boot Ubuntu 17.04 on a Marvell MacchiatoBin board in UEFI/ACPI mode, check for crash. [Regression Risk] Fix looks straightforward to me - it avoids probing a PIO-only driver if the port is non-PIO, thus avoiding a crash on platforms where native PIO is unsupported. The fix is upstream and CC'd for stable, so there should be upstream support for any regressions it were to cause. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1692548/+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
