On Mon, Jun 5, 2017 at 10:51 PM, Yasunori Goto <[email protected]> wrote:
> Hi,
>
>> > No, you're not doing anything wrong. This is a known issue that I am
>> > investigating. The reports of this usually come from distributions
>> > with older module loading infrastructure. If you can try with a recent
>> > Fedora that would mimic the environment I normally use to test,
>>
>> Oh, I see. Certainly, I used CentOS7.
>> Ok, I'll use Fedora environment.
>
> Hmmm, though I made Fedora 25 environment, this panic still occurs...
> I'll attach syslog and .config again.
>
>
[..]
> [ 117.804948] general protection fault: 0000 [#1] SMP
[..]
> [ 117.820866] Hardware name: Red Hat KVM, BIOS 0.5.1 01/01/2011
[..]
> [ 117.843262] Call Trace:
> [ 117.843985] release_nodes+0x76/0x260
> [ 117.845062] devres_release_all+0x3c/0x50
> [ 117.846225] device_release_driver_internal+0x159/0x200
> [ 117.847748] device_release_driver+0x12/0x20
> [ 117.849029] bus_remove_device+0xfd/0x170
> [ 117.850192] device_del+0x1e8/0x330
> [ 117.851284] platform_device_del+0x28/0x90
> [ 117.852485] platform_device_unregister+0x12/0x30
> [ 117.853846] nfit_test_exit+0x2a/0x93b [nfit_test]
> [ 117.855219] SyS_delete_module+0x171/0x250
> [ 117.856403] entry_SYSCALL_64_fastpath+0x1a/0xa5
Can you also attach the qemu-kvm command line you are using?
ps aux | grep qemu
_______________________________________________
Linux-nvdimm mailing list
[email protected]
https://lists.01.org/mailman/listinfo/linux-nvdimm
