From: Andi Kleen <ak@suse.de>
To: Greg KH <gregkh@suse.de>
Cc: David Brownell <david-b@pacbell.net>,
linux-kernel@vger.kernel.org,
linux-usb-devel@lists.sourceforge.net
Subject: Re: EHCI + APIC errors = no usb goodness
Date: Tue, 24 Jan 2006 07:22:20 +0100 [thread overview]
Message-ID: <200601240722.21108.ak@suse.de> (raw)
In-Reply-To: <20060123210443.GA20944@suse.de>
On Monday 23 January 2006 22:04, Greg KH wrote:
> I've had a laptop here that has had some "issues" in the past (time
> running double speed, XFree doesn't work, etc.)
>
> Now I'm down to the last problem, USB doesn't work, which is a bit of a
> pain for me :)
>
> Anyway, below is the kernel log from 2.6.16-rc1-mm2 (contains the latest
> acpi tree, which I thought might help out.) This log is when I modprobe
> ehci-hcd. The interesting thing is the APIC error,
That was the laptop with ATI chipset right? Most of them have routing
troubles with the timer interrupt. I finally gave up trying to fix
them and just switched over to using the APIC timer which is run
by the CPU and not dependent on chipsets. Use the latest
patch from my x86-64 queue ftp://ftp.firstfloor.org/pub/ak/x86_64/quilt/
This should both eliminate the APIC errors and likely any timing problems
for 64bit kernels.
> Andi, I know you have been doing some apic rework for x86-64 (which this
> processor is, but I'm still running it in 32bit mode.) Do you happen to
> have any patch that I could test out?
Ah, 32bit? For that just run without APIC.
-Andi
next prev parent reply other threads:[~2006-01-24 6:35 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-23 21:04 EHCI + APIC errors = no usb goodness Greg KH
2006-01-23 21:25 ` Pete Zaitcev
2006-01-23 21:41 ` Greg KH
2006-01-23 21:50 ` Pete Zaitcev
2006-01-23 21:56 ` Greg KH
2006-01-23 22:01 ` Greg KH
2006-01-23 23:53 ` David Brownell
2006-01-24 6:22 ` Andi Kleen [this message]
2006-01-25 3:10 ` Kurt Wall
2006-01-25 4:43 ` Greg KH
-- strict thread matches above, loose matches on Subject: below --
2006-01-23 22:16 Brown, Len
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=200601240722.21108.ak@suse.de \
--to=ak@suse.de \
--cc=david-b@pacbell.net \
--cc=gregkh@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb-devel@lists.sourceforge.net \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox