From: Greg KH <greg@kroah.com>
To: Guennadi Liakhovetski <g.liakhovetski@gmx.de>
Cc: linux-kernel@vger.kernel.org, linux-usb-devel@lists.sourceforge.net
Subject: Re: [SMP, USB] UHCI interrupt wrongly routed?
Date: Wed, 24 Nov 2004 17:26:29 -0800 [thread overview]
Message-ID: <20041125012629.GA21569@kroah.com> (raw)
In-Reply-To: <Pine.LNX.4.60.0411242352370.3896@poirot.grange>
On Wed, Nov 24, 2004 at 11:57:15PM +0100, Guennadi Liakhovetski wrote:
> Hello
>
> I guess, it is not a USB problem, really, it just appeared with USB. On a
> 2-way running 2.6.9 the onboard UHCI device is configured to IRQ 9 via
> XT-PIC???
>
> CPU0 CPU1
> 0: 588054 123 IO-APIC-edge timer
> 1: 360 0 IO-APIC-edge i8042
> 2: 0 0 XT-PIC cascade
> 8: 4 0 IO-APIC-edge rtc
> 9: 0 0 IO-APIC-edge acpi
> 11: 0 0 XT-PIC uhci_hcd
> 15: 2 0 IO-APIC-edge ide1
> 16: 173 1 IO-APIC-level ehci_hcd
> 17: 0 0 IO-APIC-level ohci_hcd
> 18: 0 0 IO-APIC-level ohci_hcd
> 19: 99999 1 IO-APIC-level ohci_hcd
> 20: 332 0 IO-APIC-level eth0
> 21: 2576 0 IO-APIC-level sym53c8xx
> NMI: 0 0
> LOC: 587726 587988
> ERR: 0
> MIS: 0
>
> Non-surprisingly, it doesn't work. Below is a complete dmesg (I first
> connected the card-reader to an ohci / ehci PCI board, and then
> re-connected it to an on-board UHCI port.
>
> Thanks
> Guennadi
> ---
> Guennadi Liakhovetski
>
> Linux version 2.6.9-rc4-tmscsim (lyakh@poirot.grange) (gcc version 3.3.2 (Debian)) #1 SMP Mon Oct 25 23:38:23 CEST 2004
Can you try 2.6.10-rc2 or the latest -bk snapshot? Hopefully this is
fixed there.
thanks,
greg k-h
next prev parent reply other threads:[~2004-11-25 3:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-24 22:57 [SMP, USB] UHCI interrupt wrongly routed? Guennadi Liakhovetski
2004-11-25 1:26 ` Greg KH [this message]
2004-11-25 21:41 ` Guennadi Liakhovetski
2004-11-26 22:21 ` Guennadi Liakhovetski
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=20041125012629.GA21569@kroah.com \
--to=greg@kroah.com \
--cc=g.liakhovetski@gmx.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