Re: Crash in CentOS 7 kernel-3.10.0-514.16.1.el7.x86_64 in Xen PV mode

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Tue, Oct 24, 2017 at 12:53 PM, Karl Johnson <karljohnson.it@xxxxxxxxx> wrote:
On Tue, Oct 24, 2017 at 3:09 PM, Karl Johnson <karljohnson.it@xxxxxxxxx> wrote:
On Tue, Oct 24, 2017 at 3:36 AM, Akemi Yagi <amyagi@xxxxxxxxx> wrote:
On Mon, Oct 23, 2017 at 11:08 PM, Akemi Yagi <amyagi@xxxxxxxxx> wrote:
On Mon, Oct 23, 2017 at 12:57 PM, Karl Johnson <karljohnson.it@xxxxxxxxx> wrote:
On Sat, May 20, 2017 at 8:30 PM, Sarah Newman <srn@xxxxxxxxx> wrote:
I experienced a bug that is likely the same as https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1350373 . Commit
b7dd0e350e0bd4c0fddcc9b8958342700b00b168 , which is supposed to fix it, doesn't appear in this kernel and doesn't apply cleanly either.
Is there any point in trying to backport the patch?

I had the same kernel panic while booting a PV domU on 3.10.0-693.2.2.el7.centos.plus.x86_64. I had to start the domU again to boot correctly. Can this patch be added to the CentOS 7 kernel-plus?

Karl
 
​I can certainly add the patch (commit b7dd0e350e0bd4c0fddcc9b8958342700b00b168) to the Plus kernel.​ It would be best if you could file a request on http://bugs.centos.org so that we can track it better.

Akemi

​A CentOSPlus kernel ​set with the referenced patch applied is available for testing at:

https://people.centos.org/toracat/kernel/7/plus/xen/

Feedback appreciated,

Akemi

Thanks for the build Akemi. I will try to test this kernel in the next days however it will be hard to know if it fix the kernel panic because I can't reproduce it. It's seems to be random and pretty rare in my case.

The test kernel doesn't boot on my side:

[    0.077000] Call Trace:
[    0.077000]  [<ffffffff813f6e70>] ? gnttab_init+0x260/0x260
[    0.077000]  [<ffffffff813f6e93>] __gnttab_init+0x23/0x40
[    0.077000]  [<ffffffff810020e8>] do_one_initcall+0xb8/0x230
[    0.077000]  [<ffffffff81b5d1fb>] kernel_init_freeable+0x17a/0x219
[    0.077000]  [<ffffffff81b5c9d4>] ? initcall_blacklist+0xb0/0xb0
[    0.077000]  [<ffffffff816a3d20>] ? rest_init+0x80/0x80
[    0.077000]  [<ffffffff816a3d2e>] kernel_init+0xe/0xf0
[    0.077000]  [<ffffffff816c5f98>] ret_from_fork+0x58/0x90
[    0.077000]  [<ffffffff816a3d20>] ? rest_init+0x80/0x80
[    0.077000] Code: 00 00 66 2e 0f 1f 84 00 00 00 00 00 83 c3 01 41 39 dd 0f 86 84 00 00 00 4c 63 e3 31 f6 bf d0 00 00 00 4e 8d 34 e0 e8 01 09 d9 ff <49> 89 06 48 8b 05 37 0d bf 00 4a 83 3c e0 00 75 d0 48 89 c7 41
[    0.077000] RIP  [<ffffffff813f6d0f>] gnttab_init+0xff/0x260
[    0.077000]  RSP <ffff88003daa3df8>
[    0.077000] CR2: 0000000000000010
[    0.077000] ---[ end trace ad7a936cdeb5166e ]---
[    0.077000] Kernel panic - not syncing: Fatal exception

I switched back to 3.10.0-693.2.2.el7.centos.plus.x86_64.

​Looks as if the patch broke something before it could fix the problem...

Akemi​
 
_______________________________________________
CentOS-virt mailing list
CentOS-virt@xxxxxxxxxx
https://lists.centos.org/mailman/listinfo/centos-virt

[Index of Archives]     [CentOS Users]     [Linux Media]     [Asterisk]     [DCCP]     [Netdev]     [X.org]     [Xfree86]     [Linux USB]

  Powered by Linux