[Bug 1935583] Re: Kernel panic on Bionic 5.4.0-47-generic
** Changed in: kunpeng920 Status: Incomplete => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1935583 Title: Kernel panic on Bionic 5.4.0-47-generic To manage notifications about this bug go to: https://bugs.launchpad.net/kunpeng920/+bug/1935583/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1935583] Re: Kernel panic on Bionic 5.4.0-47-generic
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1935583 Title: Kernel panic on Bionic 5.4.0-47-generic To manage notifications about this bug go to: https://bugs.launchpad.net/kunpeng920/+bug/1935583/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1935583] Re: Kernel panic on Bionic 5.4.0-47-generic
** Changed in: kunpeng920 Status: In Progress => Incomplete ** Changed in: linux (Ubuntu) Status: In Progress => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1935583 Title: Kernel panic on Bionic 5.4.0-47-generic To manage notifications about this bug go to: https://bugs.launchpad.net/kunpeng920/+bug/1935583/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1935583] Re: Kernel panic on Bionic 5.4.0-47-generic
Hi Merlin, Thanks for the information. I will look into it. And can you provide us more information please? e.g. firmware ver, output of `lspci -vvnn`, what kind of operation you use to reproduce this issue. Thanks a lot. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1935583 Title: Kernel panic on Bionic 5.4.0-47-generic To manage notifications about this bug go to: https://bugs.launchpad.net/kunpeng920/+bug/1935583/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1935583] Re: Kernel panic on Bionic 5.4.0-47-generic
[1516299.566982] ACPI CPPC: PCC check channel failed for ss: 0. ret=-110 [1516299.582325] ACPI CPPC: PCC check channel failed for ss: 0. ret=-110 [1516299.601741] ACPI CPPC: PCC check channel failed for ss: 0. ret=-110 [1516299.606825] Unable to handle kernel paging request at virtual address 800011691ab0 [1516299.609605] ACPI CPPC: PCC check channel failed for ss: 0. ret=-110 [1516299.612022] Unhandled fault at 0x8944d9d0 [1516299.612031] Mem abort info: [1516299.612034] ESR = 0x8630 [1516299.612037] EC = 0x21: IABT (current EL), IL = 32 bits [1516299.612042] SET = 0, FnV = 0 [1516299.612044] EA = 0, S1PTW = 0 [1516299.612047] swapper pgtable: 4k pages, 48-bit VAs, pgdp=014ac000 [1516299.612049] [8944d9d0] pgd=2027f003, pud=2027e003, pmd=0027d1ed3003, pte= [1516299.612055] Internal error: TLB conflict abort: 8630 [#1] SMP [1516299.612057] Modules linked in: binfmt_misc xt_MASQUERADE iptable_nat nf_nat xt_tcpudp xt_multiport xt_conntrack nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 iptable_filter bpfilter rpcsec_gss_krb5 auth_rpcgss nfsv4 nfs lockd grace fscache bonding nls_iso8859_1 ipmi_ssif input_leds joydev hns_roce_hw_v2 hisi_dma spi_dw_mmio ipmi_si spi_dw ipmi_devintf ipmi_msghandler cppc_cpufreq sch_fq_codel ib_iser sunrpc rdma_cm iw_cm ib_cm 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 mlx5_ib ses enclosure ib_uverbs ib_core realtek hibmc_drm drm_vram_helper ttm hid_generic drm_kms_helper syscopyarea crct10dif_ce sysfillrect ghash_ce hisi_sas_v3_hw sha2_ce mlx5_core sysimgblt sha256_arm64 hns3 hisi_sas_main fb_sys_fops sha1_ce hclge libsas usbhid tls drm hid hnae3 megaraid_sas ahci scsi_transport_sas mlxfw gpio_dwapb [1516299.612109] aes_neon_bs aes_neon_blk aes_ce_blk crypto_simd cryptd aes_ce_cipher [1516299.612116] CPU: 3 PID: 0 Comm: swapper/3 Not tainted 5.4.0-47-generic #51~18.04.1-Ubuntu [1516299.612117] Hardware name: [About Privacy Deleted], BIOS 1.39 06/11/2020 [1516299.612118] pstate: 8049 (Nzcv daif +PAN -UAO) [1516299.612172] pc : mlx5e_features_check+0x0/0x490 [mlx5_core] [1516299.612178] lr : netif_skb_features+0xfc/0x248 [1516299.612179] sp : 80001001b140 [1516299.612180] x29: 80001001b140 x28: 001745f4 [1516299.612181] x27: 0027b157faac x26: [1516299.612183] x25: 0001 x24: 80001001b253 [1516299.612185] x23: 0027b4b8 x22: 0027b4b8 [1516299.612186] x21: 800011b78000 x20: 0027cea31c00 [1516299.612187] x19: 000850c21cd14ba9 x18: 800011254420 [1516299.612189] x17: x16: [1516299.612190] x15: 0001 x14: c178 [1516299.612192] x13: e238 x12: 088002c8 [1516299.612193] x11: 0027756dbe70 x10: 0070 [1516299.612195] x9 : 0001 x8 : 0001 [1516299.612196] x7 : f6576c61 x6 : 354623ec [1516299.612198] x5 : 0001 x4 : [1516299.612199] x3 : 8944d9d0 x2 : 000850c21cd14ba9 [1516299.612201] x1 : 0027b4b8 x0 : 0027cea31c00 [1516299.612202] Call trace: [1516299.612239] mlx5e_features_check+0x0/0x490 [mlx5_core] [1516299.612241] validate_xmit_skb+0x2c/0x2f8 [1516299.612242] validate_xmit_skb_list+0x50/0xb0 [1516299.612245] sch_direct_xmit+0xfc/0x528 [1516299.612246] __dev_queue_xmit+0x818/0x890 [1516299.612248] dev_queue_xmit+0x24/0x30 [1516299.612257] bond_dev_queue_xmit+0x44/0x98 [bonding] [1516299.612264] bond_do_alb_xmit+0xcc/0x1b0 [bonding] [1516299.612270] bond_alb_xmit+0xd0/0x660 [bonding] [1516299.612275] bond_start_xmit+0x154/0x4f8 [bonding] [1516299.612277] dev_hard_start_xmit+0xb4/0x268 [1516299.612278] __dev_queue_xmit+0x740/0x890 [1516299.612280] dev_queue_xmit+0x24/0x30 [1516299.612282] ip_finish_output2+0x31c/0x570 [1516299.612284] __ip_finish_output+0x128/0x200 [1516299.612285] ip_finish_output+0x38/0xd0 [1516299.612287] ip_output+0xb0/0x130 [1516299.612288] ip_local_out+0x58/0x68 [1516299.612290] __ip_queue_xmit+0x12c/0x368 [1516299.612294] ip_queue_xmit+0x10/0x18 [1516299.612295] __tcp_transmit_skb+0x4cc/0xa58 [1516299.612297] __tcp_send_ack.part.47+0xb0/0x128 [1516299.612299] tcp_send_ack+0x34/0x40 [1516299.612300] __tcp_ack_snd_check+0x50/0x1b8 [1516299.612302] tcp_rcv_established+0x338/0x6a0 [1516299.612304] tcp_v4_do_rcv+0x94/0x208 [1516299.612306] tcp_v4_rcv+0xa50/0xba8 [1516299.612307] ip_protocol_deliver_rcu+0x44/0x200 [1516299.612308] ip_local_deliver_finish+0x64/0x78 [1516299.612310] ip_local_deliver+0x90/0x108 [1516299.612311] ip_sublist_rcv_finish+0x5c/0x88 [1516299.612312] ip_sublist_rcv+0x1d0/0x260 [1516299.612314] ip_list_rcv+0x110/0x1b8 [1516299.612315]
[Bug 1935583] Re: Kernel panic on Bionic 5.4.0-47-generic
There are many ways to corrupt stack or pointers to stack. Since this issue happens in out-of-tree mlx5 modules, it looks to me that where you shall look at. Please let us know if you can reproduce this issue without any out-of- tree module. ** Changed in: linux (Ubuntu) Status: Incomplete => Invalid ** Changed in: kunpeng920 Status: Incomplete => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1935583 Title: Kernel panic on Bionic 5.4.0-47-generic To manage notifications about this bug go to: https://bugs.launchpad.net/kunpeng920/+bug/1935583/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1935583] Re: Kernel panic on Bionic 5.4.0-47-generic
I notice there is a traceback about mlx5, however, while I check vmcore, the STACK_END_MAGIC haven't been overridden (I mean $rd 'stack_address' print 0x57AC6E9D) how can? //kernel/sched/core.c static inline void schedule_debug(struct task_struct *prev) { #ifdef CONFIG_SCHED_STACK_END_CHECK if (task_stack_end_corrupted(prev)) panic("corrupted stack end detected inside scheduler\n"); #endif ** Changed in: kunpeng920 Status: Invalid => Incomplete ** Changed in: linux (Ubuntu) Status: Invalid => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1935583 Title: Kernel panic on Bionic 5.4.0-47-generic To manage notifications about this bug go to: https://bugs.launchpad.net/kunpeng920/+bug/1935583/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1935583] Re: Kernel panic on Bionic 5.4.0-47-generic
The log shows that you are running non-Ubuntu mlx5 modules, and the traceback is in those modules. Marking Invalid - you'll need to reach out to your mlx5 driver provider for support. ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Changed in: kunpeng920 Status: New => Incomplete ** Changed in: kunpeng920 Status: Incomplete => Triaged ** Changed in: kunpeng920 Status: Triaged => Invalid ** Changed in: linux (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1935583 Title: Kernel panic on Bionic 5.4.0-47-generic To manage notifications about this bug go to: https://bugs.launchpad.net/kunpeng920/+bug/1935583/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs