Re: [Xen-devel] Regression in kernel 3.5 as Dom0 regarding PCI Passthrough?!

[Tobias Geiger <tobias.geiger@xxxxxxxxx>]

The dom0 panic when shutting down domu also happens with 

dom0_mem=4096M
and also with
dom0_mem=4096M,max:4096M

and both times:
pc:~# cat /etc/xen/xl.conf   | grep autoballoon
autoballoon=0


:(

FWIW here is the diff betwen dom0 kernel 3.5 and 3.4:

pc:~# diff /tmp/3.4.config /usr/src/3.5/linux-3.5/.config
3c3
< # Linux/x86_64 3.4.0 Kernel Configuration
---
> # Linux/x86_64 3.5.0 Kernel Configuration
12,16d11
< CONFIG_GENERIC_CMOS_UPDATE=y
< CONFIG_CLOCKSOURCE_WATCHDOG=y
< CONFIG_GENERIC_CLOCKEVENTS=y
< CONFIG_ARCH_CLOCKSOURCE_DATA=y
< CONFIG_GENERIC_CLOCKEVENTS_BROADCAST=y
31d25
< CONFIG_ARCH_HAS_CPU_IDLE_WAIT=y
33d26
< CONFIG_GENERIC_TIME_VSYSCALL=y
51d43
< # CONFIG_KTIME_SCALAR is not set
52a45
> CONFIG_ARCH_SUPPORTS_UPROBES=y
55a49
> CONFIG_BUILDTIME_EXTABLE_SORT=y
104a99,113
> CONFIG_CLOCKSOURCE_WATCHDOG=y
> CONFIG_ARCH_CLOCKSOURCE_DATA=y
> CONFIG_GENERIC_TIME_VSYSCALL=y
> CONFIG_GENERIC_CLOCKEVENTS=y
> CONFIG_GENERIC_CLOCKEVENTS_BUILD=y
> CONFIG_GENERIC_CLOCKEVENTS_BROADCAST=y
> CONFIG_GENERIC_CLOCKEVENTS_MIN_ADJUST=y
> CONFIG_GENERIC_CMOS_UPDATE=y
> 
> #
> # Timers subsystem
> #
> CONFIG_TICK_ONESHOT=y
> CONFIG_NO_HZ=y
> CONFIG_HIGH_RES_TIMERS=y
111a121
> CONFIG_RCU_FANOUT_LEAF=16
145d154
< CONFIG_USER_NS=y
188d196
< # CONFIG_PERF_COUNTERS is not set
210a219
> CONFIG_GENERIC_SMP_IDLE_THREAD=y
222a232,233
> CONFIG_HAVE_ARCH_SECCOMP_FILTER=y
> CONFIG_SECCOMP_FILTER=y
322,326d332
< CONFIG_TICK_ONESHOT=y
< CONFIG_NO_HZ=y
< CONFIG_HIGH_RES_TIMERS=y
< CONFIG_GENERIC_CLOCKEVENTS_BUILD=y
< CONFIG_GENERIC_CLOCKEVENTS_MIN_ADJUST=y
444a451
> CONFIG_CROSS_MEMORY_ATTACH=y
445a453
> CONFIG_FRONTSWAP=y
486a495,496
> # CONFIG_PM_AUTOSLEEP is not set
> # CONFIG_PM_WAKELOCKS is not set
504c514
< CONFIG_ACPI_PROCESSOR_AGGREGATOR=m
---
> # CONFIG_ACPI_PROCESSOR_AGGREGATOR is not set
540,543c550,553
< CONFIG_X86_PCC_CPUFREQ=m
< CONFIG_X86_ACPI_CPUFREQ=m
< CONFIG_X86_POWERNOW_K8=m
< CONFIG_X86_SPEEDSTEP_CENTRINO=m
---
> # CONFIG_X86_PCC_CPUFREQ is not set
> # CONFIG_X86_ACPI_CPUFREQ is not set
> # CONFIG_X86_POWERNOW_K8 is not set
> # CONFIG_X86_SPEEDSTEP_CENTRINO is not set
621a632
> CONFIG_X86_DEV_DMA_OPS=y
630a642
> CONFIG_XFRM_ALGO=y
773a786
> CONFIG_NETFILTER_XT_TARGET_HMARK=m
891d903
< CONFIG_IP6_NF_QUEUE=m
952d963
< # CONFIG_ECONET is not set
977a989,990
> CONFIG_NET_SCH_CODEL=m
> CONFIG_NET_SCH_FQ_CODEL=m
1018a1032
> CONFIG_BATMAN_ADV_BLA=y
1026d1039
< CONFIG_HAVE_BPF_JIT=y
1082a1096,1097
> CONFIG_NFC_HCI=m
> # CONFIG_NFC_SHDLC is not set
1090a1106
> CONFIG_HAVE_BPF_JIT=y
1253d1268
< # CONFIG_MTD_UBI_DEBUG is not set
1331c1346,1347
< CONFIG_BMP085=m
---
> CONFIG_BMP085=y
> CONFIG_BMP085_I2C=m
1358a1375
> CONFIG_INTEL_MEI=m
1535a1553
> CONFIG_SBP_TARGET=m
1558a1577
> CONFIG_NET_TEAM_MODE_LOADBALANCE=m
1695c1714
< CONFIG_STMMAC_PLATFORM=m
---
> CONFIG_STMMAC_PLATFORM=y
1712a1732,1734
> CONFIG_NET_VENDOR_WIZNET=y
> # CONFIG_WIZNET_W5100 is not set
> # CONFIG_WIZNET_W5300 is not set
1753d1774
< # CONFIG_TR is not set
1809a1831
> CONFIG_INPUT_MATRIXKMAP=m
1837a1860
> CONFIG_KEYBOARD_LM8333=m
1900a1924
> # CONFIG_INPUT_MC13783_PWRBUTTON is not set
2015d2038
< CONFIG_RAMOOPS=m
2139a2163
> CONFIG_GPIO_ICH=m
2321a2346
> CONFIG_SENSORS_INA2XX=m
2340a2366
> CONFIG_SENSORS_MC13783_ADC=m
2370a2397
> CONFIG_IE6XX_WDT=m
2421c2448
< CONFIG_MFD_CORE=m
---
> CONFIG_MFD_CORE=y
2427a2455
> CONFIG_MFD_LM3533=m
2442a2471
> # CONFIG_MFD_MAX77693 is not set
2447c2476
< CONFIG_MFD_WM8400=m
---
> # CONFIG_MFD_WM8400 is not set
2453a2483,2485
> CONFIG_MFD_MC13783=m
> CONFIG_MFD_MC13XXX=m
> CONFIG_MFD_MC13XXX_I2C=m
2457a2490
> CONFIG_LPC_ICH=y
2464a2498
> # CONFIG_MFD_PALMAS is not set
2472a2507,2509
> CONFIG_REGULATOR_MC13XXX_CORE=m
> CONFIG_REGULATOR_MC13783=m
> CONFIG_REGULATOR_MC13892=m
2485d2521
< CONFIG_REGULATOR_WM8400=m
2683c2719
< CONFIG_VIDEO_EM28XX_RC=y
---
> CONFIG_VIDEO_EM28XX_RC=m
2690d2725
< CONFIG_USB_ET61X251=m
2782a2818,2820
> CONFIG_DRM_AST=m
> # CONFIG_DRM_MGAG200 is not set
> CONFIG_DRM_CIRRUS_QEMU=m
2853a2892,2894
> CONFIG_FB_AUO_K190X=m
> CONFIG_FB_AUO_K1900=m
> CONFIG_FB_AUO_K1901=m
2859a2901
> CONFIG_BACKLIGHT_LM3533=m
2986d3027
< # CONFIG_SND_HDA_ENABLE_REALTEK_QUIRKS is not set
3050a3092
> CONFIG_SND_SOC_CS42L52=m
3058a3101
> CONFIG_SND_SOC_LM49453=m
3079d3121
< CONFIG_SND_SOC_WM8400=m
3117a3160,3161
> CONFIG_SND_SOC_MC13783=m
> CONFIG_SND_SOC_ML26124=m
3118a3163
> CONFIG_SND_SIMPLE_CARD=m
3137,3140d3181
< CONFIG_HID_SUPPORT=y
< CONFIG_HID=y
< # CONFIG_HID_BATTERY_STRENGTH is not set
< # CONFIG_HIDRAW is not set
3143c3184
< # USB Input Devices
---
> # HID support
3145,3147c3186,3189
< CONFIG_USB_HID=y
< # CONFIG_HID_PID is not set
< # CONFIG_USB_HIDDEV is not set
---
> CONFIG_HID=y
> # CONFIG_HID_BATTERY_STRENGTH is not set
> # CONFIG_HIDRAW is not set
> CONFIG_HID_GENERIC=m
3155a3198
> CONFIG_HID_AUREAL=m
3216a3260,3266
> 
> #
> # USB HID support
> #
> CONFIG_USB_HID=y
> # CONFIG_HID_PID is not set
> # CONFIG_USB_HIDDEV is not set
3230,3231d3279
< # CONFIG_USB_DEVICEFS is not set
< # CONFIG_USB_DEVICE_CLASS is not set
3269a3318,3321
> CONFIG_USB_CHIPIDEA=m
> # CONFIG_USB_CHIPIDEA_UDC is not set
> # CONFIG_USB_CHIPIDEA_HOST is not set
> # CONFIG_USB_CHIPIDEA_DEBUG is not set
3382a3435
> CONFIG_USB_SERIAL_QT2=m
3408a3462,3466
> 
> #
> # USB Physical Layer drivers
> #
> CONFIG_USB_ISP1301=m
3414a3473,3476
> 
> #
> # USB Peripheral Controller
> #
3419d3480
< CONFIG_USB_CI13XXX_PCI=m
3443a3505
> CONFIG_USB_GADGET_TARGET=m
3500a3563
> CONFIG_LEDS_LM3533=m
3514a3578
> CONFIG_LEDS_MC13783=m
3530a3595
> CONFIG_LEDS_TRIGGER_TRANSIENT=m
3618a3684
> CONFIG_RTC_DRV_MC13XXX=m
3654a3721
> # CONFIG_VIRTIO_MMIO_CMDLINE_DEVICES is not set
3699,3700d3765
< # CONFIG_USB_SERIAL_QUATECH_USB2 is not set
< # CONFIG_VME_BUS is not set
3702d3766
< # CONFIG_IIO is not set
3737d3800
< CONFIG_INTEL_MEI=m
3760a3824,3833
> CONFIG_IPACK_BUS=m
> CONFIG_BOARD_TPCI200=m
> CONFIG_SERIAL_IPOCTAL=m
> CONFIG_WIMAX_GDM72XX=m
> # CONFIG_WIMAX_GDM72XX_QOS is not set
> # CONFIG_WIMAX_GDM72XX_K_MODE is not set
> # CONFIG_WIMAX_GDM72XX_WIMAX2 is not set
> CONFIG_WIMAX_GDM72XX_USB=y
> # CONFIG_WIMAX_GDM72XX_SDIO is not set
> # CONFIG_WIMAX_GDM72XX_USB_PM is not set
3787c3860
< CONFIG_INTEL_MENLOW=m
---
> # CONFIG_INTEL_MENLOW is not set
3843a3917,3925
> CONFIG_EXTCON=m
> 
> #
> # Extcon Device Drivers
> #
> CONFIG_EXTCON_GPIO=m
> # CONFIG_MEMORY is not set
> # CONFIG_IIO is not set
> # CONFIG_VME_BUS is not set
3989d4070
< # CONFIG_UBIFS_FS_XATTR is not set
3993d4073
< # CONFIG_UBIFS_FS_DEBUG is not set
4015a4096
> CONFIG_NFS_V2=y
4087a4169,4179
> CONFIG_NLS_MAC_ROMAN=m
> CONFIG_NLS_MAC_CELTIC=m
> CONFIG_NLS_MAC_CENTEURO=m
> CONFIG_NLS_MAC_CROATIAN=m
> CONFIG_NLS_MAC_CYRILLIC=m
> CONFIG_NLS_MAC_GAELIC=m
> CONFIG_NLS_MAC_GREEK=m
> CONFIG_NLS_MAC_ICELAND=m
> CONFIG_NLS_MAC_INUIT=m
> CONFIG_NLS_MAC_ROMANIAN=m
> CONFIG_NLS_MAC_TURKISH=m
4102a4195
> # CONFIG_READABLE_ASM is not set
4110a4204,4205
> # CONFIG_PANIC_ON_OOPS is not set
> CONFIG_PANIC_ON_OOPS_VALUE=0
4188a4284,4285
> # CONFIG_UPROBE_EVENT is not set
> # CONFIG_PROBE_EVENTS is not set
4393a4491
> CONFIG_HAVE_KVM_MSI=y
4406a4505,4506
> CONFIG_GENERIC_STRNCPY_FROM_USER=y
> CONFIG_GENERIC_STRNLEN_USER=y
4460a4561
> # CONFIG_DDR is not set





Am Mittwoch 25 Juli 2012, 15:43:57 schrieb Konrad Rzeszutek Wilk:
> On Wed, Jul 25, 2012 at 02:30:00PM +0200, Tobias Geiger wrote:
> > Hi!
> > 
> > i notice a serious regression with 3.5 as Dom0 kernel (3.4 was rock
> > stable):
> > 
> > 1st: only the GPU PCI Passthrough works, the PCI USB Controller is
> > not recognized within the DomU (HVM Win7 64)
> > Dom0 cmdline is:
> > ro root=LABEL=dom0root
> > xen-pciback.hide=(08:00.0)(08:00.1)(00:1d.0)(00:1d.1)(00:1d.2)(00:1d.7)
> > security=apparmor noirqdebug nouveau.msi=1
> > 
> > Only 8:00.0 and 8:00.1 get passed through without problems, all the
> > USB Controller IDs are not correctly passed through and get a
> > exclamation mark within the win7 device manager ("could not be
> > started").
> 
> Ok, but they do get passed in though? As in, QEMU sees them.
> If you boot a Live Ubuntu/Fedora CD within the guest with the PCI
> passed in devices do you see them? Meaning lspci shows them?
> 
> 
> Is the lspci -vvv output in dom0 different from 3.4 vs 3.5?
> 
> > 2nd: After DomU shutdown , Dom0 panics (100% reproducable) - sorry
> > that i have no full stacktrace, all i have is a "screenshot" which i
> > uploaded here:
> > http://imageshack.us/photo/my-images/52/img20120724235921.jpg/
> 
> Ugh, that looks like somebody removed a large chunk of a pagetable.
> 
> Hmm. Are you using dom0_mem=max parameter? If not, can you try
> that and also disable ballooning in the xm/xl config file pls?
> 
> > With 3.4 both issues were not there - everything worked perfectly.
> > Tell me which debugging info you need, i may be able to re-install
> > my netconsole to get the full stacktrace (but i had not much luck
> > with netconsole regarding kernel panics - rarely this info gets sent
> > before the "panic"...)
> > 
> > Greetings
> > Tobias
> > 
> > _______________________________________________
> > Xen-devel mailing list
> > Xen-devel@xxxxxxxxxxxxx
> > http://lists.xen.org/xen-devel
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@xxxxxxxxxxxxx
> http://lists.xen.org/xen-devel


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