All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@suse.de>
To: Pete Zaitcev <zaitcev@redhat.com>
Cc: david-b@pacbell.net, ak@suse.de, linux-kernel@vger.kernel.org,
	linux-usb-devel@lists.sourceforge.net
Subject: Re: EHCI + APIC errors = no usb goodness
Date: Mon, 23 Jan 2006 13:41:15 -0800	[thread overview]
Message-ID: <20060123214115.GA15338@suse.de> (raw)
In-Reply-To: <20060123132554.13411a1d.zaitcev@redhat.com>

On Mon, Jan 23, 2006 at 01:25:54PM -0800, Pete Zaitcev wrote:
> On Mon, 23 Jan 2006 13:04:43 -0800, Greg KH <gregkh@suse.de> wrote:
> 
> > Now I'm down to the last problem, USB doesn't work, which is a bit of a
> > pain for me :)
> 
> > [   87.406180] APIC error on CPU0: 00(40)
> > [   87.426282] drivers/usb/core/inode.c: creating file '001'
> > [   87.426333] hub 1-0:1.0: state 5 ports 8 chg 0000 evt 0000
> > [   87.712002] APIC error on CPU0: 40(40)
> > [   87.774743] irq 16: nobody cared (try booting with the "irqpoll" option)
> 
> Why do you even enable APIC on an old laptop? We tried it a few times,
> it's just not possible. I'd say, about one in ten to one in five of 2002
> vintage laptops will not even boot, let alone work when APIC is enabled.
> Some of them are well known, like Dell Lattitude 610. I expect this to
> change with dual-core laptops, but for now the rule is: UP kernel,
> No APIC, for distro kernels at least.

Hm, it's a brand-new laptop, and all of my other boxes work with ioapic
on UP kernels.  I didn't think to turn it off, I'll go rebuild and see
if that helps.

oh, and 2.6.13 seems to work just fine, with ioapic enabled...

thanks,

greg k-h

  reply	other threads:[~2006-01-23 21:41 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 [this message]
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
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=20060123214115.GA15338@suse.de \
    --to=gregkh@suse.de \
    --cc=ak@suse.de \
    --cc=david-b@pacbell.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb-devel@lists.sourceforge.net \
    --cc=zaitcev@redhat.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.