From: Sarah Sharp <sarah.a.sharp@linux.intel.com>
To: "Chen, Jamie" <jamie.chen@intel.com>
Cc: Bjorn Helgaas <bhelgaas@google.com>,
Alan Stern <stern@rowland.harvard.edu>,
USB list <linux-usb@vger.kernel.org>,
"Tsai, Gaggery" <gaggery.tsai@intel.com>,
"linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>
Subject: Re: EHCI host broken -- interrupts disabled
Date: Mon, 20 Jan 2014 11:39:18 -0800 [thread overview]
Message-ID: <20140120193918.GD5545@xanatos> (raw)
In-Reply-To: <F01C6967BCFFB14E8DF7F5D2FD1053EB1A18C3@PGSMSX103.gar.corp.intel.com>
On Mon, Jan 20, 2014 at 12:15:47PM +0000, Chen, Jamie wrote:
> Try to apply this patch to kernel 3.8.0.
>
> Make sure the ehci can work fine and lspci show that PCI_COMMAND_INTX_DISABLE is 0.
>
> The patch can resolved this issue.
Great! Thanks for testing, Jamie.
Bjorn, can you add me to the Cc list for this patch? I'd like to notify
other Linux distros when it lands so they can pick it up.
Sarah Sharp
>
> #lspci -vv
>
> 00:1d.0 USB controller: Intel Corporation Device 0f34 (rev 0a) (prog-if 20 [EHCI])
> Subsystem: Intel Corporation Device 7270
> Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
> Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
> Latency: 0
> Interrupt: pin A routed to IRQ 23
> Region 0: Memory at 90612000 (32-bit, non-prefetchable) [size=1K]
> Capabilities: [50] Power Management version 3
> Flags: PMEClk- DSI- D1- D2- AuxCurrent=375mA PME(D0+,D1-,D2-,D3hot+,D3cold+)
> Status: D0 NoSoftRst+ PME-Enable- DSel=0 DScale=0 PME-
> Capabilities: [58] Debug port: BAR=1 offset=00a0
> Capabilities: [98] PCI Advanced Features
> AFCap: TP+ FLR+
> AFCtrl: FLR-
> AFStatus: TP-
> Kernel driver in use: ehci-pci
>
> dmesg:
> [ 1.014556] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
> [ 1.014559] ehci-pci: EHCI PCI platform driver
> [ 1.014612] ehci-pci 0000:00:1d.0: setting latency timer to 64
> [ 1.014618] ehci-pci 0000:00:1d.0: EHCI Host Controller
> [ 1.014629] ehci-pci 0000:00:1d.0: new USB bus registered, assigned bus number 1
> [ 1.014652] ehci-pci 0000:00:1d.0: debug port 2
> [ 1.018562] ehci-pci 0000:00:1d.0: cache line size of 64 is not supported
> [ 1.018594] ehci-pci 0000:00:1d.0: irq 23, io mem 0x90612000
> [ 1.029238] ehci-pci 0000:00:1d.0: USB 2.0 started, EHCI 1.00
> [ 1.029274] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
> [ 1.029279] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
> [ 1.029283] usb usb1: Product: EHCI Host Controller
> [ 1.029286] usb usb1: Manufacturer: Linux 3.8.13.13-pci ehci_hcd
> [ 1.029290] usb usb1: SerialNumber: 0000:00:1d.0
> [ 1.029469] hub 1-0:1.0: USB hub found
> [ 1.029785] ehci-platform: EHCI generic platform driver
> [ 1.340641] usb 1-1: new high-speed USB device number 2 using ehci-pci
> [ 1.473442] usb 1-1: New USB device found, idVendor=8087, idProduct=07e6
> [ 1.473447] usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
> [ 1.475095] hub 1-1:1.0: USB hub found
> [ 1.749587] usb 1-1.2: new high-speed USB device number 3 using ehci-pci
> [ 1.841046] usb 1-1.2: New USB device found, idVendor=05e3, idProduct=0608
> [ 1.841052] usb 1-1.2: New USB device strings: Mfr=0, Product=1, SerialNumber=0
> [ 1.841056] usb 1-1.2: Product: USB2.0 Hub
> [ 1.841469] hub 1-1.2:1.0: USB hub found
> [ 2.115558] usb 1-1.2.1: new high-speed USB device number 4 using ehci-pci
> [ 2.208321] usb 1-1.2.1: New USB device found, idVendor=05e3, idProduct=0608
> [ 2.208327] usb 1-1.2.1: New USB device strings: Mfr=0, Product=1, SerialNumber=0
> [ 2.208331] usb 1-1.2.1: Product: USB2.0 Hub
> [ 2.209113] hub 1-1.2.1:1.0: USB hub found
> [ 2.283104] usb 1-1.2.3: new low-speed USB device number 5 using ehci-pci
> [ 2.378487] usb 1-1.2.3: New USB device found, idVendor=03f0, idProduct=0c4a
> [ 2.378492] usb 1-1.2.3: New USB device strings: Mfr=1, Product=2, SerialNumber=0
> [ 2.378496] usb 1-1.2.3: Product: HP
> [ 2.378500] usb 1-1.2.3: Manufacturer: HP
> [ 2.385945] usbcore: registered new interface driver usbhid
> [ 2.385950] usbhid: USB HID core driver
> [ 11.550722] input: HP HP as /devices/pci0000:00/0000:00:1d.0/usb1/1-1/1-1.2/1-1.2.3/1-1.2.3:1.0/input/input5
> [ 11.550963] hid-generic 0003:03F0:0C4A.0001: input,hidraw0: USB HID v1.11 Mouse [HP HP] on usb-0000:00:1d.0-1.2.3/input0
>
>
> Jamie
next prev parent reply other threads:[~2014-01-20 19:39 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20140114181721.GC12126@xanatos>
[not found] ` <Pine.LNX.4.44L0.1401141336020.1310-100000@iolanthe.rowland.org>
2014-01-16 17:32 ` EHCI host broken -- interrupts disabled Bjorn Helgaas
2014-01-16 19:40 ` Alan Stern
2014-01-17 18:22 ` Bjorn Helgaas
2014-01-20 12:15 ` Chen, Jamie
2014-01-20 19:39 ` Sarah Sharp [this message]
2014-01-20 20:36 ` Greg KH
2014-01-30 0:04 ` Bjorn Helgaas
2014-02-11 23:24 ` Bjorn Helgaas
[not found] ` <F01C6967BCFFB14E8DF7F5D2FD1053EB1ECC22@PGSMSX103.gar.corp.intel.com>
2014-02-14 20:47 ` Bjorn Helgaas
2014-02-14 22:27 ` Sarah Sharp
2014-02-14 22:37 ` Bjorn Helgaas
2014-01-21 19:15 ` USB EHCI broken on Celeron N2920 (Bay Trail) Sarah Sharp
2014-01-22 1:41 ` Chris Cheng
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=20140120193918.GD5545@xanatos \
--to=sarah.a.sharp@linux.intel.com \
--cc=bhelgaas@google.com \
--cc=gaggery.tsai@intel.com \
--cc=jamie.chen@intel.com \
--cc=linux-pci@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=stern@rowland.harvard.edu \
/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.