3.9-rc1: crash kernel panic - not syncing: Can not allocate SWIOTLB buffer earlier and can't now provide you with the DMA bounce buffer

_events+0x2ea/0x910 [3.088981] [] ? __schedule+0x3de/0x7e0 [3.094451] [] hub_thread+0x35/0x1e0 [3.099661] [] ? wake_up_bit+0x40/0x40 [3.105045] [] ? hub_events+0x910/0x910 [3.110514] [] kthread+0xc0/0xd0 [3.115378] [] ? kthread_create_on_node+0x120/0x120 [ 3.121887] [] ret_fro

vmlinux symtab matching kallsyms fails: diff end addr for aesni_gcm_dec/aesni_gcm_enc

: Maps only in kallsyms: end vmlinux symtab matches kallsyms: FAILED! The end addr of aesni_gcm_dec/aesni_gcm_enc in vmlinux symtab and kallsyms is wrong beyond 4K. I think that's a problem or am I missing some changes for these days? -- Thanks, WANG Chao -- To unsubscribe from this

Re: [PATCH V2 0/5] x86: Create direct mappings for E820_RAM only

x86_64 kvm guest, it was booting successfully and the issue mentioned is gone. -WANG Chao -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Pl

<    1   2