[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20080629200210.GB31633@elte.hu>
Date: Sun, 29 Jun 2008 22:02:10 +0200
From: Ingo Molnar <mingo@...e.hu>
To: "Maciej W. Rozycki" <macro@...ux-mips.org>
Cc: "Rafael J. Wysocki" <rjw@...k.pl>,
Matthew Garrett <mjg59@...f.ucam.org>,
Stephen Rothwell <sfr@...b.auug.org.au>,
linux-next@...r.kernel.org, LKML <linux-kernel@...r.kernel.org>,
Thomas Gleixner <tglx@...utronix.de>,
ACPI Devel Maling List <linux-acpi@...r.kernel.org>,
Len Brown <lenb@...nel.org>,
Andi Kleen <andi-suse@...stfloor.org>
Subject: Re: linux-next: Tree for June 13: IO APIC breakage on HP nx6325
* Maciej W. Rozycki <macro@...ux-mips.org> wrote:
> You may argue this is a regression, but this is simply the cost paid
> for progress -- the kernel stays within the spec as defined both by
> ACPI and MPS, we have just started using a different configuration now
> and an interrupt source override provided by the manufacturer
> explicitly states INTIN2 is good to use. In a sense you were simply
> lucky previously the kernel was bad enough with the way it configured
> the timer through the I/O APIC it failed completely avoiding the bug
> in your firmware. Now the bug has got uncovered.
well as long as we eliminate the bad effects around via DMI exceptions
nobody will feel the need to argue whether it's a regression ;-) [this
problem could be argued to be a regression, even if it's caused by prior
luck/stupidity of Linux. We have to live with the effects of our
mistakes.]
Ingo
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists