From: "Robert W. Fuller" <orangemagicbus@sbcglobal.net>
To: Andrew Morton <akpm@osdl.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6.11 USB broken on VIA computer (not just ACPI)
Date: Wed, 16 Mar 2005 00:28:44 -0500 [thread overview]
Message-ID: <4237C40C.6090903@sbcglobal.net> (raw)
In-Reply-To: <20050315203914.223771b2.akpm@osdl.org>
I never actually saw it work until I added the noapic option to the
2.6.11.2 boot. Now I can usually my USB mouse! Of course the downside
to specifying noapic is only one CPU is servicing interrupts on my SMP
system.
It certainly doesn't work under 2.4.28, but I haven't tried specifying
noapic to that kernel. Would that be useful information?
Andrew Morton wrote:
> "Robert W. Fuller" <orangemagicbus@sbcglobal.net> wrote:
>
>>This isn't limited to the ACPI case. My BIOS is old enough that ACPI is
>> not supported because the kernel can't find RSDP. I found that the USB
>> works if I boot with "noapic." This is probably sub-optimal on an SMP
>> machine. If don't boot with "noapic" I get the following errors:
>
>
> Did it work OK under previous kernels? If so, which versions?
>
next prev parent reply other threads:[~2005-03-16 5:31 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-16 3:19 2.6.11 USB broken on VIA computer (not just ACPI) Robert W. Fuller
2005-03-16 4:39 ` Andrew Morton
2005-03-16 5:28 ` Robert W. Fuller [this message]
2005-03-16 5:31 ` Andrew Morton
2005-03-16 5:37 ` Robert W. Fuller
2005-03-16 5:54 ` Andrew Morton
2005-03-16 6:58 ` Robert W. Fuller
2005-03-16 17:19 ` Greg KH
2005-03-16 17:50 ` Robert W. Fuller
2005-03-16 17:56 ` Greg KH
2005-03-16 10:00 ` Documentation/i386/IO-APIC.txt (Re: 2.6.11 USB broken on VIA computer (not just ACPI)) Xavier Bestel
2005-03-16 10:08 ` Xavier Bestel
2005-03-16 17:17 ` 2.6.11 USB broken on VIA computer (not just ACPI) Greg KH
-- strict thread matches above, loose matches on Subject: below --
2005-05-12 8:47 paul
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=4237C40C.6090903@sbcglobal.net \
--to=orangemagicbus@sbcglobal.net \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
/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.