Re: [PATCH 1/2] target-i386: disable LINT0 after reset

From: Nadav Amit <namit@cs.technion.ac.il>
To: Jan Kiszka <jan.kiszka@siemens.com>
Cc: kvm@vger.kernel.org, Alex Williamson <alex.williamson@redhat.com>,
	qemu-devel@nongnu.org, Bandan Das <bsd@redhat.com>,
	avi.kivity@gmail.com, pbonzini@redhat.com
Subject: Re: [PATCH 1/2] target-i386: disable LINT0 after reset
Date: Wed, 16 Sep 2015 09:22:14 +0300	[thread overview]
Message-ID: <CAKLkAJ6NDtQTGhxdSgEn3hXwt1zXg_TXC+rqFv-+LM5-djDumA@mail.gmail.com> (raw)
In-Reply-To: <55F8FCD2.2000003@siemens.com>

[-- Attachment #1: Type: text/plain, Size: 1036 bytes --]

I'll try to reproduce the problem today.

Nadav
On Sep 16, 2015 8:23 AM, "Jan Kiszka" <jan.kiszka@siemens.com> wrote:

> On 2015-09-15 23:19, Alex Williamson wrote:
> > On Mon, 2015-04-13 at 02:32 +0300, Nadav Amit wrote:
> >> Due to old Seabios bug, QEMU reenable LINT0 after reset. This bug is
> long gone
> >> and therefore this hack is no longer needed.  Since it violates the
> >> specifications, it is removed.
> >>
> >> Signed-off-by: Nadav Amit <namit@cs.technion.ac.il>
> >> ---
> >>  hw/intc/apic_common.c | 9 ---------
> >>  1 file changed, 9 deletions(-)
> >
> > Please see bug: https://bugs.launchpad.net/qemu/+bug/1488363
> >
> > Is this bug perhaps not as long gone as we thought, or is there
> > something else going on here?  Thanks,
>
> I would say, someone needs to check if the SeaBIOS line that is supposed
> to enable LINT0 is actually executed on one of the broken systems and,
> if not, why not.
>
> Jan
>
> --
> Siemens AG, Corporate Technology, CT RTC ITP SES-DE
> Corporate Competence Center Embedded Linux
>

[-- Attachment #2: Type: text/html, Size: 1591 bytes --]