On Fri, Feb 14, 2014 at 3:27 PM, Sarah Sharp
wrote:
> On Fri, Feb 14, 2014 at 01:47:48PM -0700, Bjorn Helgaas wrote:
>> On Fri, Feb 14, 2014 at 9:36 AM, Chen, Jamie wrote:
>> > Sorry for late response.
>> >
>> > The dmesg attach in the mail.
>>
>> Thanks, I put this info in
>> https://bugzilla.ke
On Fri, Feb 14, 2014 at 01:47:48PM -0700, Bjorn Helgaas wrote:
> On Fri, Feb 14, 2014 at 9:36 AM, Chen, Jamie wrote:
> > Sorry for late response.
> >
> > The dmesg attach in the mail.
>
> Thanks, I put this info in
> https://bugzilla.kernel.org/show_bug.cgi?id=70601 and applied the
> patch to pci
#x27;ll
cherry-pick it into for-linus for v3.14.
Bjorn
>> -Original Message-
>> From: Bjorn Helgaas [mailto:bhelg...@google.com]
>> Sent: Wednesday, February 12, 2014 7:24 AM
>> To: Chen, Jamie
>> Cc: Alan Stern; Sarah Sharp; USB list; Tsai, Gaggery;
>> l
On Wed, Jan 29, 2014 at 5:04 PM, Bjorn Helgaas wrote:
> On Mon, Jan 20, 2014 at 5:15 AM, 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.
>
> Thanks
On Mon, Jan 20, 2014 at 5:15 AM, 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.
Thanks for testing it. Can you collect the complete dmesg output or
dmi
On Mon, Jan 20, 2014 at 11:39:18AM -0800, Sarah Sharp wrote:
> On Mon, Jan 20, 2014 at 12:15:47PM +, 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
On Mon, Jan 20, 2014 at 12:15:47PM +, 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 t
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.
#lspci -vv
00:1d.0 USB controller: Intel Corporation Device 0f34 (rev 0a) (prog-if 20
[EHCI])
Subsystem: Intel Corporation De
On Thu, Jan 16, 2014 at 02:40:35PM -0500, Alan Stern wrote:
> On Thu, 16 Jan 2014, Bjorn Helgaas wrote:
>
> > I think dev->irq is supposed to be valid after pci_enable_device(), so
> > it seems like it would make sense to clear PCI_COMMAND_INTX_DISABLE
> > there.
>
> Okay.
>
> > I don't know why
On Thu, 16 Jan 2014, Bjorn Helgaas wrote:
> I think dev->irq is supposed to be valid after pci_enable_device(), so
> it seems like it would make sense to clear PCI_COMMAND_INTX_DISABLE
> there.
Okay.
> I don't know why a BIOS would leave PCI_COMMAND_INTX_DISABLE set for
> the EHCI device. Does
[+cc linux-pci]
On Tue, Jan 14, 2014 at 11:47 AM, Alan Stern wrote:
> On Tue, 14 Jan 2014, Sarah Sharp wrote:
>
>> Hi Alan,
>
> I'm not a good person to ask about this. Maybe Bjorn can help.
>
>> All this info is second- or third-hand, so please excuse the extremely
>> vague bug report.
>>
>> A
On Tue, 14 Jan 2014, Sarah Sharp wrote:
> Hi Alan,
I'm not a good person to ask about this. Maybe Bjorn can help.
> All this info is second- or third-hand, so please excuse the extremely
> vague bug report.
>
> A new Intel Atom system (Baytrail) comes with both an xHCI host and an
> EHCI host,
On Tue, Jan 14, 2014 at 10:17:21AM -0800, Sarah Sharp wrote:
> Hi Alan,
>
> All this info is second- or third-hand, so please excuse the extremely
> vague bug report.
>
> A new Intel Atom system (Baytrail) comes with both an xHCI host and an
> EHCI host, but the BIOS has an "EHCI only" option tha
13 matches
Mail list logo
