From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:33837) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1bL7ea-0002Ct-K5 for qemu-devel@nongnu.org; Thu, 07 Jul 2016 07:39:37 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1bL7eW-0005d6-EQ for qemu-devel@nongnu.org; Thu, 07 Jul 2016 07:39:35 -0400 Received: from mx-v6.kamp.de ([2a02:248:0:51::16]:56992 helo=mx01.kamp.de) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1bL7eW-0005cy-4x for qemu-devel@nongnu.org; Thu, 07 Jul 2016 07:39:32 -0400 References: <577A611E.3010204@kamp.de> <6fa89d4e-1a32-c28d-5133-5308ae30cdf6@redhat.com> From: Peter Lieven Message-ID: <577E3F72.4000706@kamp.de> Date: Thu, 7 Jul 2016 13:39:30 +0200 MIME-Version: 1.0 In-Reply-To: <6fa89d4e-1a32-c28d-5133-5308ae30cdf6@redhat.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] Qemu and PCI Interrupt Link? List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Paolo Bonzini , Laszlo Ersek , "qemu-devel@nongnu.org" Am 05.07.2016 um 22:53 schrieb Paolo Bonzini: > > On 05/07/2016 20:30, Laszlo Ersek wrote: >> On 07/04/16 15:14, Peter Lieven wrote: >>> Hi, >>> >>> i noticed that newer guest kernels emit the following message at startup: >>> >>> ACPI: No IRQ available for PCI Interrupt Link [LNKS]. Try pci=noacpi or >>> acpi=off >>> >>> Cmdline: >>> x86_64-softmmu/qemu-system-x86_64 -enable-kvm -m 2048 -cdrom >>> ~/Downloads/ubuntu-16.04-desktop-amd64.iso >>> >>> Is this expected? >> This seems to come from kernel commit 5ebc76035303. Thankfully the >> commit message is quite detailed. >> >> The commit message makes me think that the kernel patch is incorrect. It >> certainly seems to conflict with the following SeaBIOS commit: >> >> commit f64a472a481784231fbf8541825501df411b11d1 >> Author: Paolo Bonzini >> Date: Thu Dec 13 08:42:02 2012 +0100 >> >> acpi: reintroduce LNKS >> >> That SeaBIOS patch is where we have the identical functionality in QEMU >> from (see QEMU commits 74523b850189a and c35b6e8032105). > The error is harmless. LNKS has been there forever and I suspect no one > really knows why it was introduced in the first place. The link for the > device that uses LNKS probably can be changed back to LNKA since the SCI > is specified in the FADT, but again---who knows why it was changed. Okay, so just ignore this message for good or is there anything futher I can/should do? Peter