[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20070602155440.c1f8d1cb.akpm@linux-foundation.org>
Date: Sat, 2 Jun 2007 15:54:40 -0700
From: Andrew Morton <akpm@...ux-foundation.org>
To: Linus Torvalds <torvalds@...ux-foundation.org>
Cc: Tear <tarrqt@...oo.com>, mingo@...hat.com,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
"Brown, Len" <len.brown@...el.com>
Subject: Re: [RFC][PATCH] IO-APIC blacklist
On Sat, 2 Jun 2007 14:28:58 -0700 (PDT) Linus Torvalds <torvalds@...ux-foundation.org> wrote:
> That blacklist entry is _ancient_. It's entirely possible that it's just
> bogus: we've had so many ACPI fixes since it was added, that it's quite
> possible that the blacklist entry itself is bogus, and is the result of
> some old ACPI bug that triggered on that entry.
>
> The Dell GX240 entry was added by commit 68e4ad79294 in the historic Linux
> archive:
>
> Author: Len Brown <len.brown@...el.com>
> Date: Sat Aug 9 15:00:59 2003 -0400
>
> ACPI from 2.4:
> build: add ACPI_HT, delete ACPI_HT_ONLY
> boot: add acpi={force, off, ht}; delete "noht", "acpismp="
> add DMI blacklist from UnitedLinux
>
> and since it sounds like the machine _works_ with ACPI on, my real
> preference would be to just remove the black-list entry.
>
> In fact, I thought that patch already existed in the -mm tree?
It is. remove-dell-optiplex-gx240-from-the-acpi-blacklist.patch
> Len - do you have any archives back from 2003 and earlier to indicate why
> the Dell GX240 was blacklisted?
"add DMI blacklist from UnitedLinux". Lost in the mists of time, I expect.
I guess we can tag remove-dell-optiplex-gx240-from-the-acpi-blacklist.patch
as "backport to 2.6.22.x if it doesn't break anything in 2.6.23-rcX".
-
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