From: Len Brown <len.brown@intel.com>
To: Tony Lindgren <tony@atomide.com>
Cc: Chris Cheney <ccheney@cheney.cx>,
linux-kernel@vger.kernel.org,
acpi-devel-request@lists.sourceforge.net, patches@x86-64.org,
Andi Kleen <ak@suse.de>,
pavel@ucw.cz
Subject: Re: [PATCH] x86_64 VIA chipset IOAPIC fix
Date: 25 Mar 2004 23:21:51 -0500 [thread overview]
Message-ID: <1080274911.748.130.camel@dhcppc4> (raw)
In-Reply-To: <20040326033536.GA8057@atomide.com>
On Thu, 2004-03-25 at 22:35, Tony Lindgren wrote:
> * Chris Cheney <ccheney@cheney.cx> [040325 19:06]:
> > On Wed, Mar 24, 2004 at 07:34:34PM -0800, Tony Lindgren wrote:
> >
> > BTW - Does this also solve the problem with needing USB to be compiled
> > directly into the kernel in 64bit mode?
>
> OK, tried it and it does not help there. Also loding ACPI processor and
> thermal zone compiled in hangs the machine, but loading them as modules
> work.
where does it hang when processor and thermal are compiled-in?
> The power button still turns off the machine immedieately too with
> ACPI on.
Then ACPI is not on. what does dmesg show?
> So you still need to have both uchi and echi compiled. Ehci is needed for
> the hotplug to work properly at least on gentoo.
>
> Regards,
>
> Tony
>
>
next prev parent reply other threads:[~2004-03-26 4:22 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-25 3:34 [PATCH] x86_64 VIA chipset IOAPIC fix Tony Lindgren
2004-03-26 0:15 ` Len Brown
2004-03-26 0:47 ` Tony Lindgren
2004-03-26 3:04 ` Chris Cheney
2004-03-26 3:11 ` Tony Lindgren
2004-03-26 3:13 ` Len Brown
2004-03-26 3:20 ` Chris Cheney
2004-03-26 3:35 ` Tony Lindgren
2004-03-26 4:21 ` Len Brown [this message]
2004-03-26 4:34 ` Chris Cheney
2004-03-26 5:10 ` Tony Lindgren
[not found] ` <20040326043447.GD9248-4Ww5XsWutDyeZLLa646FqQ@public.gmane.org>
2004-03-30 3:17 ` Randy.Dunlap
2004-03-30 3:17 ` Randy.Dunlap
2004-03-26 5:02 ` Tony Lindgren
-- strict thread matches above, loose matches on Subject: below --
2004-04-16 10:53 HurryLin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1080274911.748.130.camel@dhcppc4 \
--to=len.brown@intel.com \
--cc=acpi-devel-request@lists.sourceforge.net \
--cc=ak@suse.de \
--cc=ccheney@cheney.cx \
--cc=linux-kernel@vger.kernel.org \
--cc=patches@x86-64.org \
--cc=pavel@ucw.cz \
--cc=tony@atomide.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.