Re: [Xen-devel] [BUG] PV domU Arch Linux kernel 4.12 with CONFIG_INTEL_ATOMISP=y guest crashes

[Juergen Gross <jgross@xxxxxxxx>]

On 08/09/17 05:40, John Thomson wrote:
> Hi,
> I get a PV domU kernel crash booting Arch Linux 4.12.
> 
> Not sure if this is more relevant to Xen, the Linux kernel or
> distributions.
> 
> Running xen-4.9.0 on Arch Linux x86_64 with kernel 4.12.10.
> Booting UEFI -> grub2 -> linux -> reboot -> grub2 multiboot2 -> xen
> 
> My test was booting the dom0 kernel and ramdisk in a domU PV guest.
> I compiled the 4.12.10 Linux kernel with and without
> CONFIG_INTEL_ATOMISP
> With CONFIG_INTEL_ATOMISP=n, my guest booted without issue.

Don't configure it. It is broken:

Instead of probing whether the device is installed or not the driver's
probe function just assumes the device is present and maps a hard coded
physical address and begins working on that, regardless whether the
mapped address belongs to the correct device type or not.


Juergen

> 
> XenParavirtOpsHelp needed files attached.
> 
> Easily reproduced for me by booting the 201708 Arch Linux ISO.
> http://mirror.rackspace.com/archlinux/iso/2017.08.01/archlinux-2017.08.01-x86_64.iso
> The Arch Linux 201707 install disk with kernel 4.11 boots.
> http://mirror.rackspace.com/archlinux/iso/2017.07.01/archlinux-2017.07.01-x86_64.iso
> 
> xl config:
> name = 'arch201708.cfg'
> memory = 512
> disk=['archlinux-2017.08.01-x86_64.iso, , xvdc, cdrom']
> bootloader='pygrub'
> kernel = 'arch/boot/x86_64/vmlinuz'
> ramdisk = 'arch/boot/x86_64/archiso.img'
> cmdline = 'archisobasedir=arch archisolabel=ARCH_201708'
> 
> Arch ISO 201708 guest console:
> 
> [    0.104674] xen:manage: Unable to read sysrq code in control/sysrq
> [    0.106995] dmi: Firmware registration failed.
> [    0.127871] intel_mid_msgbus_init: Error: msgbus PCI handle NULL
> [    2.986550] BUG: unable to handle kernel paging request at
> ffffc900400e5060
> [    2.986563] IP: vlv2_plat_configure_clock+0x3b/0xa0
> [    2.986565] PGD 1ff05067 
> [    2.986566] P4D 1ff05067 
> [    2.986567] PUD 1e982067 
> [    2.986569] PMD 1e983067 
> [    2.986578] PTE 0
> [    2.986580] 
> [    2.986583] Oops: 0000 [#1] PREEMPT SMP
> [    2.986585] Modules linked in:
> [    2.986588] CPU: 0 PID: 1 Comm: swapper/0 Not tainted 4.12.3-1-ARCH
> #1
> [    2.986591] task: ffff88001e9eb900 task.stack: ffffc900400c8000
> [    2.986595] RIP: e030:vlv2_plat_configure_clock+0x3b/0xa0
> [    2.986598] RSP: e02b:ffffc900400cbbe0 EFLAGS: 00010246
> [    2.986601] RAX: 0000000000000000 RBX: ffffc900400e5060 RCX:
> 0000000001d5dfff
> [    2.986604] RDX: ffff88001e9eb900 RSI: 0000000000000002 RDI:
> ffffffff81ac9980
> [    2.986607] RBP: ffffc900400cbbf0 R08: 0000000000001000 R09:
> ffffffff811d6101
> [    2.986610] R10: 0000000000007ff0 R11: ffffe8ffffffffff R12:
> 0000000000000002
> [    2.986613] R13: 0000000000000000 R14: 0000000000000000 R15:
> 0000000000000000
> [    2.986620] FS:  0000000000000000(0000) GS:ffff88001f800000(0000)
> knlGS:0000000000000000
> [    2.986623] CS:  e033 DS: 0000 ES: 0000 CR0: 0000000080050033
> [    2.986627] CR2: ffffc900400e5060 CR3: 0000000001a09000 CR4:
> 0000000000042660
> [    2.986632] Call Trace:
> [    2.986638]  vlv2_plat_clk_probe+0x3f/0x70
> [    2.986643]  platform_drv_probe+0x3b/0xa0
> [    2.986647]  driver_probe_device+0x2ff/0x450
> [    2.986651]  __device_attach_driver+0x83/0x100
> [    2.986655]  ? __driver_attach+0xe0/0xe0
> [    2.986659]  bus_for_each_drv+0x69/0xb0
> [    2.986663]  __device_attach+0xdd/0x160
> [    2.986667]  device_initial_probe+0x13/0x20
> [    2.986670]  bus_probe_device+0x92/0xa0
> [    2.986674]  device_add+0x451/0x690
> [    2.986678]  platform_device_add+0x10d/0x270
> [    2.986683]  ? set_debug_rodata+0x17/0x17
> [    2.986686]  platform_device_register_full+0xfe/0x110
> [    2.986692]  ? vlv2_plat_clk_init+0x19/0x19
> [    2.986696]  vlv2_plat_clk_init+0x48/0x82
> [    2.986700]  do_one_initcall+0x50/0x190
> [    2.986704]  kernel_init_freeable+0x186/0x214
> [    2.986709]  ? rest_init+0x90/0x90
> [    2.986713]  kernel_init+0xe/0x100
> [    2.986716]  ret_from_fork+0x25/0x30
> [    2.986720] Code: 47 83 fe 02 41 89 f4 77 67 48 8b 05 60 49 84 00 48
> 85 c0 74 48 c1 e7 02 48 63 ff 48 8d 1c 38 48 c7 c7 80 99 ac 81 e8 95 0f
> 15 00 <8b> 03 83 e0 fc 44 09 e0 89 03 48 c7 c7 80 99 ac 81 e8 6f 09 15 
> [    2.986745] RIP: vlv2_plat_configure_clock+0x3b/0xa0 RSP:
> ffffc900400cbbe0
> [    2.986749] CR2: ffffc900400e5060
> [    2.986755] ---[ end trace 1147de716422f210 ]---
> [    2.986763] Kernel panic - not syncing: Attempted to kill init!
> exitcode=0x00000009
> [    2.986763] 
> [    2.986771] Kernel Offset: disabled
> 
> 
> Arch Linux bug:
> https://bugs.archlinux.org/task/55447
> 
> This bug was also seen on Ubuntu:
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1711298
> 
> Thanks,
> --
>   John Thomson
> 
> 
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@xxxxxxxxxxxxx
> https://lists.xen.org/xen-devel
> 


_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
https://lists.xen.org/xen-devel