Hi folks,
I am not sure if its righ to send BUG report to the ML, if not, please correct me, and help me forward it to right ML. I download a fedora23 Base cloud image from https://getfedora.org/en/cloud/download/, but after I install it via virt-install, I find the system cannot boot up as the following calltrace. Seems it should be fixed! :-)
Wei
0.859821] CPU: 1 PID: 124 Comm: cryptomgr_test Not tainted 4.2.3-300.fc23.x86_64 #1 [ 0.859821] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.8.0-0-g4c59f5d-20150219_092859-nilsson.home.kraxel.org 04/01/2014 [ 0.859821] task: ffff88007c0ad4c0 ti: ffff880079bec000 task.ti: ffff880079bec000 [ 0.859821] RIP: 0010:[<ffffffff8108ebaa>] [<ffffffff8108ebaa>] aes_ctr_enc_128_avx_by8+0xa/0x1250 [ 0.859821] RSP: 0018:ffff880079bef8a0 EFLAGS: 00010206 [ 0.859821] RAX: 0000000000000010 RBX: 0000000000000000 RCX: ffff880079af0000 [ 0.859821] RDX: ffff880079bd1850 RSI: ffff880079befd40 RDI: ffff880079af0000 [ 0.859821] RBP: ffff880079bef8a8 R08: 0000000000000040 R09: ffff880079af0000 [ 0.859821] R10: ffff880079af0000 R11: ffffffff81a5fe01 R12: ffff880079bd1850 [ 0.859821] R13: ffff880079bef9a8 R14: ffffffff81ca7d80 R15: ffff880079af0000 [ 0.859821] FS: 0000000000000000(0000) GS:ffff88007fd00000(0000) knlGS:0000000000000000 [ 0.859821] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [ 0.859821] CR2: 00007fc6e2d73944 CR3: 0000000001c0b000 CR4: 00000000001006e0 [ 0.859821] Stack: [ 0.859821] ffffffff81078881 ffff880079bef998 ffffffff81078052 0000000000000001 [ 0.859821] 0000000000000000 ffffea0001e6bc00 ffff880079af0000 ffffea0001e6bc00 [ 0.859821] ffff880079af0000 ffff880079befb40 0000000000000000 0000000000000040 [ 0.859821] Call Trace: [ 0.859821] [<ffffffff81078881>] ? aesni_ctr_enc_avx_tfm+0x41/0x50 [ 0.859821] [<ffffffff81078052>] ctr_crypt+0xa2/0x1f0 [ 0.859821] [<ffffffff813667d2>] __ablk_encrypt+0x52/0x70 [ 0.859821] [<ffffffff81366814>] ablk_encrypt+0x24/0xa0 [ 0.859821] [<ffffffff8134d6b0>] __test_skcipher+0x290/0xbf0 [ 0.859821] [<ffffffff81775c1c>] ? wait_for_completion_interruptible+0x17c/0x1a0 [ 0.859821] [<ffffffff81343a25>] ? crypto_spawn_tfm+0x45/0x80 [ 0.859821] [<ffffffff813422b7>] ? __crypto_alloc_tfm+0xe7/0x150 [ 0.859821] [<ffffffff8134236c>] ? crypto_alloc_base+0x4c/0xd0 [ 0.859821] [<ffffffff81357183>] ? cryptd_alloc_ablkcipher+0x83/0xc0 [ 0.859821] [<ffffffff8135aec3>] ? drbg_generate+0xc3/0x150 [ 0.859821] [<ffffffff813669c3>] ? ablk_init_common+0x23/0x50 [ 0.859821] [<ffffffff81077f65>] ? ablk_ctr_init+0x15/0x20 [ 0.859821] [<ffffffff813422b7>] ? __crypto_alloc_tfm+0xe7/0x150 [ 0.859821] [<ffffffff81343a25>] ? crypto_spawn_tfm+0x45/0x80 [ 0.859821] [<ffffffff8134734b>] ? skcipher_geniv_init+0x2b/0x50 [ 0.859821] [<ffffffff8134825f>] ? chainiv_init_common+0x4f/0x60 [ 0.859821] [<ffffffff813482e9>] ? async_chainiv_init+0x79/0x80 [ 0.859821] [<ffffffff8134e037>] test_skcipher+0x27/0xa0 [ 0.859821] [<ffffffff8134e0ff>] alg_test_skcipher+0x4f/0xb0 [ 0.859821] [<ffffffff8134d1d6>] alg_test+0x186/0x3d0 [ 0.859821] [<ffffffff817742f1>] ? __schedule+0x371/0x950 [ 0.859821] [<ffffffff8134b940>] ? crypto_unregister_akcipher+0x20/0x20 [ 0.859821] [<ffffffff8134b985>] cryptomgr_test+0x45/0x50 [ 0.859821] [<ffffffff810bc8a8>] kthread+0xd8/0xf0 [ 0.859821] [<ffffffff810bc7d0>] ? kthread_worker_fn+0x160/0x160 [ 0.859821] [<ffffffff81778d9f>] ret_from_fork+0x3f/0x70 [ 0.859821] [<ffffffff810bc7d0>] ? kthread_worker_fn+0x160/0x160 [ 0.859821] Code: c1 31 73 d9 08 c5 79 7e c8 41 89 42 08 eb 05 c4 41 7a 7f 0a 4c 89 f4 41 5f 41 5e 41 5d 41 5c c3 90 49 83 f8 10 0f 82 31 12 00 00 <c5> 79 6f 0d de a4 77 00 c5 7a 6f 06 c4 42 39 00 c1 4d 89 c2 49 [ 0.859821] RIP [<ffffffff8108ebaa>] aes_ctr_enc_128_avx_by8+0xa/0x1250 [ 0.859821] RSP <ffff880079bef8a0> [ 0.911709] ---[ end trace 0d09c2c6ad768d3c ]
On Mon, Apr 18, 2016 at 1:35 AM, wyang w90p710@gmail.com wrote:
Hi folks,
I am not sure if its righ to send BUG report to the ML, if not, please correct me, and help me forward it to right ML.
Bug reports are best submitted at https://bugzilla.redhat.com. That way they are tracked.
I download a fedora23 Base cloud image from https://getfedora.org/en/cloud/download/, but after I install it via virt-install, I find the system cannot boot up as the following calltrace. Seems it should be fixed! :-)
I'm not sure if the cloud images are ever respun, but if they are then using the latest is recommended. The kernel in the original release image is rather old, and I believe the backtrace you submitted is already fixed in newer kernels.
josh
kernel@lists.fedoraproject.org