From mboxrd@z Thu Jan 1 00:00:00 1970 From: Konrad Rzeszutek Wilk Subject: Re: some recent xen kernel bugs in Fedora Date: Tue, 2 Oct 2012 10:00:03 -0400 Message-ID: <20121002140003.GC15735@phenom.dumpdata.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Content-Disposition: inline In-Reply-To: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: M A Young Cc: Stefano Stabellini , xen-devel@lists.xen.org List-Id: xen-devel@lists.xenproject.org On Mon, Oct 01, 2012 at 10:35:57PM +0100, M A Young wrote: > There have been a few xen kernel bug reported recently in Fedora. > > In https://bugzilla.redhat.com/show_bug.cgi?id=861977 someone is > getting the error WARNING: at arch/x86/xen/setup.c:88 > xen_memory_setup with the kernel 3.5.4-2.fc17.x86_64 (which is > roughly 3.5.4 plus patches from the 3.5.5 patch queue including the > backports of > xen/boot: Disable NUMA for PV guests 8d54db795dfb1049d45dc34f0dddbc5347ec5642 > xen/boot: Disable BIOS SMP MP table search bd49940a35ec7d488ae63bd625639893b3385b97 > xen/m2p: do not reuse kmap_op->dev_bus_addr 2fc136eecd0c647a6b13fcd00d0c41a1a28f35a5 > plus xen-pciback-restore-pci-config-space-after-FLR.patch Oh, so that WARN was suppose to catch rather weird cases - and it did! FYI, It was added by xen/setup: Fix one-off error when adding for-balloon PFNs to the P2M. Let me help figure out what the issue is. > > In https://bugzilla.redhat.com/show_bug.cgi?id=858893 there is a > NULL pointer dereference at xennet_poll+0x94e/0xf10 in > 3.6.0-0.rc2.git2.1.fc18.x86_64 That should be fixed with 3.6.0-rc5. > > There is also https://bugzilla.redhat.com/show_bug.cgi?id=859466 > where xen 4.2 does not boot on MacBook with a 3.5 kernel unless > xsave=off which seems to relate to > https://lists.fedoraproject.org/pipermail/xen/2012-August/005879.html There was another discussion and the Fedora kernel engineers mentioned they removed the patch that broke this. Here is the thread: https://bugzilla.redhat.com/show_bug.cgi?id=859466 > > Michael Young