public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: David Brownell <david-b@pacbell.net>
To: Greg KH <gregkh@suse.de>
Cc: 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 15:53:38 -0800	[thread overview]
Message-ID: <200601231553.38995.david-b@pacbell.net> (raw)
In-Reply-To: <20060123210443.GA20944@suse.de>

On Monday 23 January 2006 1:04 pm, Greg KH wrote:

> Any thoughts?

Not particularly; clearly the EHCI driver enabled IRQs, since that's
not done until after the "USB 2.0 started, EHCI 1.00, driver 10 Dec 2004"
message prints.  And it shouldn't be an SMI issue, as might be improved
by that patch I sent this AM.

According to arch/i386/kernel/apic.c that "0x40" APIC error bit means
it got an illegal vector ... sounds to me like IRQ setup issues, since
USB code doesn't know about such things (they're not even exposed from
the arch irq handling code).

Try sticking a message where ehci_irq() returns IRQ_NONE and see what
IRQ status is being reported to EHCI.

- Dave

  parent reply	other threads:[~2006-01-24  0:29 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 [this message]
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=200601231553.38995.david-b@pacbell.net \
    --to=david-b@pacbell.net \
    --cc=ak@suse.de \
    --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