[Kernel-packages] [Bug 1678745] Comment bridged from LTC Bugzilla
--- Comment From cha...@us.ibm.com 2017-11-10 09:03 EDT--- (In reply to comment #11) > IBM, Could you please test the kernel mentioned in comment #3 ? Hi Manoj, Test team is trying to find an available system to recreate with but it may take a while as they have most of their machines tied up with ongoing tests. We appreciate your patience. -- 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/1678745 Title: Ubuntu17.04 KVM: Guest crashed @ xfs_perag_get_tag+0x6c Status in The Ubuntu-power-systems project: Incomplete Status in linux package in Ubuntu: Incomplete Bug description: == Comment: #0 - Lata Kuntal - 2017-03-30 09:44:23 == Ubuntu 17.04 KVM guest gusg8 was having ubuntu 16.04.2 and was running stress test IO, Base,TCP and NFS.The guest is having XFS as rootFS and after running few hours of regression test it dropped at xmon. Console logs : root@guskvm:~# virsh console gusg8 --force Connected to domain gusg8 Escape character is ^] 1:mon> r R00 = d288edf4 R16 = 024200ca R01 = c000378cb1f0 R17 = R02 = d2936080 R18 = 0020 R03 = 0001 R19 = c002734d1800 R04 = c000378cb190 R20 = R05 = R21 = R06 = 3c00d03fe056 R22 = c0027e26ccf0 R07 = R23 = R08 = c48492d0 R24 = R09 = 3c00d03fe056 R25 = R10 = 3c00d03fe062 R26 = 00024df4cd49 R11 = d28fa360 R27 = R12 = R28 = d28ac7b0 R13 = cfb80900 R29 = c4849000 R14 = R30 = R15 = c137ad08 R31 = pc = d288ee0c xfs_perag_get_tag+0x6c/0x170 [xfs] cfar= c096a494 perf_trace_mmc_request_start+0x104/0x440 lr = d288edf4 xfs_perag_get_tag+0x54/0x170 [xfs] msr = 80010280b033 cr = 82428424 ctr = c05e4950 xer = 2000 trap = 300 dar = 3c00d03fe062 dsisr = 4000 1:mon> t [c000378cb250] d28ac7b0 xfs_reclaim_inodes_count+0x70/0xa0 [xfs] [c000378cb290] d28c0ea8 xfs_fs_nr_cached_objects+0x28/0x40 [xfs] [c000378cb2b0] c03292d8 super_cache_count+0x68/0x120 [c000378cb2f0] c0271530 shrink_slab.part.14+0x150/0x4f0 [c000378cb430] c0276db8 shrink_node+0x158/0x3f0 [c000378cb4f0] c0277178 do_try_to_free_pages+0x128/0x460 [c000378cb590] c02775ac try_to_free_pages+0xfc/0x280 [c000378cb620] c0260158 __alloc_pages_nodemask+0x758/0xe30 [c000378cb7e0] c02dbb98 alloc_pages_vma+0x108/0x360 [c000378cb880] c029d080 wp_page_copy+0xf0/0x9d0 [c000378cb920] c02a0770 do_wp_page+0x210/0xb20 [c000378cb9b0] c02a656c handle_mm_fault+0x9cc/0x14c0 [c000378cba60] c0b511a0 do_page_fault+0x260/0x7d0 [c000378cbb10] c0008948 handle_page_fault+0x10/0x30 --- Exception: 301 (Data Access) at c010aec4 schedule_tail+0x84/0xb0 [c000378cbe30] c0009844 ret_from_fork+0x4/0x54 --- Exception: c00 (System Call) at 3fffa2b5bf44 1:mon> d || 1:mon> c cpus stopped: 0x0-0x3 1:mon> Kernel host build = root@guskvm:~# uname -r 4.10.0-13-generic root@guskvm:~# == Comment: #1 - Luciano Chavez - 2017-03-30 10:42:15 == At first glance, based on the following assembly from around the failure point: d288edd4 38c1 li r6,1 d288edd8 7f8802a6 mflrr28 d288eddc 78a70020 clrldi r7,r5,32 d288ede0 7c7d1b78 mr r29,r3 d288ede4 7c852378 mr r5,r4 d288ede8 386302c8 addir3,r3,712 d288edec 38810020 addir4,r1,32 d288edf0 4806b571 bl d28fa360# exit_xfs_fs+0x180c/0xfd44 [xfs] d288edf4 e8410018 ld r2,24(r1) d288edf8 2f83 cmpwi cr7,r3,0 d288edfc 409d0104 ble cr7,d288ef00# xfs_perag_get_tag+0x160/0x170 [xfs] d288ee00 7c0004ac sync d288ee04 e9210020 ld r9,32(r1) d288ee08 3949000c addir10,r9,12 d288ee0c 7fc05028 lwarx r30,0,r10 d288ee10 33de0001 addic r30,r30,1 d288ee14 7fc0512d stwcx. r30,0,r10 I believe the crash in fs_perag_get_tag() is after we come back from the radix_tree_gang_lookup_tag() call and are attempting the atomic_inc_return() and struct xfs_perag*pag is R09 = 3c00d03fe056 which is invalid. 85 rcu_read_loc
[Kernel-packages] [Bug 1678745] Comment bridged from LTC Bugzilla
--- Comment From cha...@us.ibm.com 2017-04-10 19:38 EDT--- Since we don't have an XFS developer in-house, does Canonical have any suggestions on what kernel config options or debug facilities we can use in the event this is reproducible? -- 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/1678745 Title: Ubuntu17.04 KVM: Guest crashed @ xfs_perag_get_tag+0x6c Status in linux package in Ubuntu: Incomplete Bug description: == Comment: #0 - Lata Kuntal - 2017-03-30 09:44:23 == Ubuntu 17.04 KVM guest gusg8 was having ubuntu 16.04.2 and was running stress test IO, Base,TCP and NFS.The guest is having XFS as rootFS and after running few hours of regression test it dropped at xmon. Console logs : root@guskvm:~# virsh console gusg8 --force Connected to domain gusg8 Escape character is ^] 1:mon> r R00 = d288edf4 R16 = 024200ca R01 = c000378cb1f0 R17 = R02 = d2936080 R18 = 0020 R03 = 0001 R19 = c002734d1800 R04 = c000378cb190 R20 = R05 = R21 = R06 = 3c00d03fe056 R22 = c0027e26ccf0 R07 = R23 = R08 = c48492d0 R24 = R09 = 3c00d03fe056 R25 = R10 = 3c00d03fe062 R26 = 00024df4cd49 R11 = d28fa360 R27 = R12 = R28 = d28ac7b0 R13 = cfb80900 R29 = c4849000 R14 = R30 = R15 = c137ad08 R31 = pc = d288ee0c xfs_perag_get_tag+0x6c/0x170 [xfs] cfar= c096a494 perf_trace_mmc_request_start+0x104/0x440 lr = d288edf4 xfs_perag_get_tag+0x54/0x170 [xfs] msr = 80010280b033 cr = 82428424 ctr = c05e4950 xer = 2000 trap = 300 dar = 3c00d03fe062 dsisr = 4000 1:mon> t [c000378cb250] d28ac7b0 xfs_reclaim_inodes_count+0x70/0xa0 [xfs] [c000378cb290] d28c0ea8 xfs_fs_nr_cached_objects+0x28/0x40 [xfs] [c000378cb2b0] c03292d8 super_cache_count+0x68/0x120 [c000378cb2f0] c0271530 shrink_slab.part.14+0x150/0x4f0 [c000378cb430] c0276db8 shrink_node+0x158/0x3f0 [c000378cb4f0] c0277178 do_try_to_free_pages+0x128/0x460 [c000378cb590] c02775ac try_to_free_pages+0xfc/0x280 [c000378cb620] c0260158 __alloc_pages_nodemask+0x758/0xe30 [c000378cb7e0] c02dbb98 alloc_pages_vma+0x108/0x360 [c000378cb880] c029d080 wp_page_copy+0xf0/0x9d0 [c000378cb920] c02a0770 do_wp_page+0x210/0xb20 [c000378cb9b0] c02a656c handle_mm_fault+0x9cc/0x14c0 [c000378cba60] c0b511a0 do_page_fault+0x260/0x7d0 [c000378cbb10] c0008948 handle_page_fault+0x10/0x30 --- Exception: 301 (Data Access) at c010aec4 schedule_tail+0x84/0xb0 [c000378cbe30] c0009844 ret_from_fork+0x4/0x54 --- Exception: c00 (System Call) at 3fffa2b5bf44 1:mon> d || 1:mon> c cpus stopped: 0x0-0x3 1:mon> Kernel host build = root@guskvm:~# uname -r 4.10.0-13-generic root@guskvm:~# == Comment: #1 - Luciano Chavez - 2017-03-30 10:42:15 == At first glance, based on the following assembly from around the failure point: d288edd4 38c1 li r6,1 d288edd8 7f8802a6 mflrr28 d288eddc 78a70020 clrldi r7,r5,32 d288ede0 7c7d1b78 mr r29,r3 d288ede4 7c852378 mr r5,r4 d288ede8 386302c8 addir3,r3,712 d288edec 38810020 addir4,r1,32 d288edf0 4806b571 bl d28fa360# exit_xfs_fs+0x180c/0xfd44 [xfs] d288edf4 e8410018 ld r2,24(r1) d288edf8 2f83 cmpwi cr7,r3,0 d288edfc 409d0104 ble cr7,d288ef00# xfs_perag_get_tag+0x160/0x170 [xfs] d288ee00 7c0004ac sync d288ee04 e9210020 ld r9,32(r1) d288ee08 3949000c addir10,r9,12 d288ee0c 7fc05028 lwarx r30,0,r10 d288ee10 33de0001 addic r30,r30,1 d288ee14 7fc0512d stwcx. r30,0,r10 I believe the crash in fs_perag_get_tag() is after we come back from the radix_tree_gang_lookup_tag() call and are attempting the atomic_inc_return() and struct xfs_perag*pag is R09 = 3c00d03fe056 which is invalid. 85 rcu_read_lock(); 86 found = radix_tree_gang_lookup_tag(&mp->m_p