All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sergei Shtylyov <sshtylyov@mvista.com>
To: Philippe De Muyter <phdm@macqel.be>
Cc: Mark Lord <kernel@teksavvy.com>, Greg KH <greg@kroah.com>,
	Tejun Heo <tj@kernel.org>, Alan Cox <alan@lxorguk.ukuu.org.uk>,
	linux-ide@vger.kernel.org, Greg Kroah-Hartman <gregkh@suse.de>,
	linux-usb@vger.kernel.org
Subject: Re: XT-PIC interrupts blocked by usbserial ? [Was Re: Intel ICH9M bug	: sata unusable with usbserial]
Date: Thu, 03 Mar 2011 18:23:12 +0300	[thread overview]
Message-ID: <4D6FB260.6010402@ru.mvista.com> (raw)
In-Reply-To: <20110303145812.GA3489@frolo.macqel>

Hello.

Philippe De Muyter wrote:

> Summary :

> When I started to listen to a USB serial GPS receiver, the interrupts
> of my sata disk were blocked until reboot :(

> Switching in the BIOS from 'APIC disabled' to 'APIC enabled' made the problem
> disappear.

>>>>> previously we had all but one usb interrupts on the same line as ata_piix :
>>>>>   5:      17183    XT-PIC-XT-PIC    ata_piix, ata_piix, ehci_hcd:usb1, ehci_hcd:usb2, uhci_hcd:usb3, uhci_hcd:usb5, uhci_hcd:usb6, uhci_hcd:usb7, uhci_hcd:usb8
>>>>> while now they are spread on different lines : 16, 18, 19, 21 and 22

>>>>> So I wonder if there is still a bug, but that it is not triggered anymore.

>>>>> Is there a way to tell which interrupt line the USB GPS receiver is connected
>>>>> to ?
>>>> See which USB bus the device is on, using lsusb.  It should match up
>>>> with the usbX number in the above list.

>>> Given that I get :

>>>   tmp199:~ # lsusb
>>>   ...
>>>   Bus 007 Device 002: ID 067b:2303 Prolific Technology, Inc. PL2303 Serial Port
>>>   tmp199:~ # cat /proc/interrupts
>>> 	     CPU0       CPU1
>>>   ...
>>>    19:     996143     995511   IO-APIC-fasteoi   ata_piix, ata_piix, uhci_hcd:usb5, uhci_hcd:usb7
>>>   tmp199:~ #

>>> my USB GPS receiver and my sata disk still share the same interrupt, I assume ?

>>> What's changed now is that this interrupt line is now IO-APIC-fasteoi instead
>>> of XT-PIC-XT-PIC.  Maybe there's something to look at there ?

>>>> Glad enabling APIC in your BIOS fixed this.

>>> I am glad too :)

>> Nothing got "fixed" by doing that.
>> Swept under the rug, yes.

>> But the bug is still there.

> If it is a bug (what I also believe) it is not a new one :

> Before installing 2.6.37-20-desktop (opensuse 11.4) on this new hardware,
> I had the same problem with 2.6.31.14-0.6-desktop (opensuse 11.2) and
> with 2.6.22.18-0.2-default (opensuse 10.3)

> The only interesting file where I find the word 'XT-PIC' is
> 	arch/alpha/kernel/irq_i8259.c

    Why it's interesting if you're not really on Alpha? Because there is also 
arch/x86/kernel/i8259.c (and several others)...

> Best regards

> Philippe

WBR, Sergei

  reply	other threads:[~2011-03-03 15:24 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-28 14:01 Intel ICH9M bug : sata unusable with usbserial Philippe De Muyter
2011-02-28 15:05 ` Alan Cox
2011-02-28 15:16   ` Tejun Heo
2011-02-28 17:05     ` Philippe De Muyter
2011-02-28 17:36       ` Tejun Heo
2011-02-28 19:21         ` Philippe De Muyter
     [not found]         ` <20110228173634.GA23008-Gd/HAXX7CRxy/B6EtB590w@public.gmane.org>
2011-02-28 19:27           ` Greg KH
2011-03-01 12:34             ` Philippe De Muyter
2011-03-01 14:16               ` Greg KH
     [not found]                 ` <20110301141627.GB12881-U8xfFu+wG4EAvxtiuMwx3w@public.gmane.org>
2011-03-01 15:00                   ` Philippe De Muyter
     [not found]                     ` <20110301150018.GA17827-NqYOdiUDesgPnqCj3zZnUQ@public.gmane.org>
2011-03-02 13:34                       ` Mark Lord
     [not found]                         ` <4D6E477A.9020401-R6A+fiHC8nRWk0Htik3J/w@public.gmane.org>
2011-03-03 14:58                           ` XT-PIC interrupts blocked by usbserial ? [Was Re: Intel ICH9M bug : sata unusable with usbserial] Philippe De Muyter
2011-03-03 15:23                             ` Sergei Shtylyov [this message]
     [not found]                               ` <4D6FB260.6010402-hkdhdckH98+B+jHODAdFcQ@public.gmane.org>
2011-03-04 14:24                                 ` Philippe De Muyter
2011-03-03 18:10                             ` Mark Lord
2011-03-03 18:20                               ` Greg KH
2011-03-04 14:29                               ` Philippe De Muyter
     [not found]                               ` <4D6FD982.2050308-R6A+fiHC8nRWk0Htik3J/w@public.gmane.org>
2011-03-04 14:56                                 ` Philippe De Muyter
2011-03-03 18:20                             ` Mark Lord
2011-03-03 19:06                               ` Alan Stern
2011-03-03 19:39                                 ` Mark Lord
     [not found]                                   ` <4D6FEE56.4080006-R6A+fiHC8nRWk0Htik3J/w@public.gmane.org>
2011-03-03 19:51                                     ` Mark Lord
2011-03-03 20:11                                       ` Alan Stern
2011-03-03 21:48                                         ` Mark Lord
2011-03-03 21:56                                           ` Alan Stern
2011-03-04  1:53                                       ` Robert Hancock

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=4D6FB260.6010402@ru.mvista.com \
    --to=sshtylyov@mvista.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=greg@kroah.com \
    --cc=gregkh@suse.de \
    --cc=kernel@teksavvy.com \
    --cc=linux-ide@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=phdm@macqel.be \
    --cc=tj@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.