On Mon, 3 Jun 2019, Geoff Winkless wrote:
> On Mon, 3 Jun 2019 at 16:29, Alan Stern wrote:
> > On Mon, 3 Jun 2019, Geoff Winkless wrote:
> >
> > > Thanks (and also to Alan) for the help, apologies for wasting your time.
> >
> > Just goes to show we all have our blind spots. I didn't realize what
On Mon, 3 Jun 2019 at 16:29, Alan Stern wrote:
> On Mon, 3 Jun 2019, Geoff Winkless wrote:
>
> > Thanks (and also to Alan) for the help, apologies for wasting your time.
>
> Just goes to show we all have our blind spots. I didn't realize what
> was going on either, and I should have.
You're too
On Mon, 3 Jun 2019, Geoff Winkless wrote:
> On Fri, 31 May 2019 at 20:11, Greg KH wrote:
>
> > Can you run 'git bisect' to determine the exact commit that caused this
> > problem? That would be most helpful.
>
> Oh for goodness sake. Sorry, I was being an idiot. After half a day of
> building
On Fri, 31 May 2019 at 20:11, Greg KH wrote:
> Can you run 'git bisect' to determine the exact commit that caused this
> problem? That would be most helpful.
Oh for goodness sake. Sorry, I was being an idiot. After half a day of
building bisect scripts and another 3 hours of waiting for
compile
On Fri, 31 May 2019, Geoff Winkless wrote:
> Hi
>
> Apologies if this is the incorrect place to post this, if so please
> feel free to call me names and then suggest somewhere more appropriate
> :)
>
> We have an embedded device on an old EPIA Mini-ITX board that runs
> Linux 2.6. There are feat
On Fri, May 31, 2019 at 05:40:23PM +0100, Geoff Winkless wrote:
> Hi
>
> Apologies if this is the incorrect place to post this, if so please
> feel free to call me names and then suggest somewhere more appropriate
> :)
>
> We have an embedded device on an old EPIA Mini-ITX board that runs
> Linux
I did test double reads and always saw the same value both times.
Another piece of info: I tested this software on an older vortex86dx
and saw the same issue. It is plausible that a vortex86dx and
vortex86dx3 could have the same flawed EHCI. Or perhaps there's some
other systemic issue that I'm
From: Daniel Goertzen
> Sent: 24 October 2018 17:47
>
> I am developing a custom USB device that makes use of isochronous IN
> transfers. It works fine from my laptop (xHCI) however on an embedded
> target (vortex86dx3, EHCI) I am seeing mysterious EFBIG errors. After
> adding lots of debug to e
On Wed, 24 Oct 2018, Steve Calfee wrote:
> On Wed, Oct 24, 2018 at 9:48 AM Daniel Goertzen
> wrote:
> >
> > I am developing a custom USB device that makes use of isochronous IN
> > transfers. It works fine from my laptop (xHCI) however on an embedded
> > target (vortex86dx3, EHCI) I am seeing my
On Wed, 24 Oct 2018, Daniel Goertzen wrote:
> I am developing a custom USB device that makes use of isochronous IN
> transfers. It works fine from my laptop (xHCI) however on an embedded
> target (vortex86dx3, EHCI) I am seeing mysterious EFBIG errors. After
> adding lots of debug to ehci-sched
On Wed, Oct 24, 2018 at 9:48 AM Daniel Goertzen
wrote:
>
> I am developing a custom USB device that makes use of isochronous IN
> transfers. It works fine from my laptop (xHCI) however on an embedded
> target (vortex86dx3, EHCI) I am seeing mysterious EFBIG errors. After
> adding lots of debug t
On Sat, 5 May 2018, Souptick Joarder wrote:
> > What you can't see just from reading the patch is that in both cases
> > (ehci->itd_pool and ehci->sitd_pool) there are two allocation paths --
> > the two branches of an "if" statement -- and only one of the paths
> > calls dma_pool_[z]alloc. Howev
On Fri, May 04, 2018 at 10:39:07AM -0400, Alan Stern wrote:
> You should have CC'ed the author of the offending commit. Added.
>
> On Thu, 3 May 2018, Erick Cafferata wrote:
>
> > Starting from v4.17-rc1, I've been having problems with my laptop's
> > webcam. Immediately after attempting to open
You should have CC'ed the author of the offending commit. Added.
On Thu, 3 May 2018, Erick Cafferata wrote:
> Starting from v4.17-rc1, I've been having problems with my laptop's
> webcam. Immediately after attempting to open Guvcview(or any other camera
> software), the system just stops working
On Tue, Nov 28, 2017 at 02:59:32PM -0500, Alan Stern wrote:
> On Tue, 28 Nov 2017, Ladislav Michl wrote:
>
> > On Tue, Nov 28, 2017 at 01:09:45PM -0500, Alan Stern wrote:
> > > The EHCI debugging files require CONFIG_DYNAMIC_DEBUG to be enabled.
> > > Oddly enough, the OHCI debugging files do no
On Tue, 28 Nov 2017, Ladislav Michl wrote:
> On Tue, Nov 28, 2017 at 01:09:45PM -0500, Alan Stern wrote:
> > The EHCI debugging files require CONFIG_DYNAMIC_DEBUG to be enabled.
> > Oddly enough, the OHCI debugging files do not have the same
> > requirement. I don't know the reason for this di
On Tue, Nov 28, 2017 at 01:09:45PM -0500, Alan Stern wrote:
> The EHCI debugging files require CONFIG_DYNAMIC_DEBUG to be enabled.
> Oddly enough, the OHCI debugging files do not have the same
> requirement. I don't know the reason for this difference.
I see, thanks for suggestion.
USB cable
On Tue, 28 Nov 2017, Ladislav Michl wrote:
> On Tue, Nov 28, 2017 at 10:00:32AM -0500, Alan Stern wrote:
> > On Tue, 28 Nov 2017, Greg KH wrote:
> >
> > > On Mon, Nov 27, 2017 at 11:08:33PM +0100, Ladislav Michl wrote:
> > > > Hi there,
> > > >
> > > > USB hosts do not discover any connected dev
On Tue, Nov 28, 2017 at 06:39:13AM -0800, Tony Lindgren wrote:
> * Ladislav Michl [171128 14:31]:
> > On Tue, Nov 28, 2017 at 06:11:31AM -0800, Tony Lindgren wrote:
> > > * Ladislav Michl [171128 09:42]:
> > > > On Tue, Nov 28, 2017 at 10:30:54AM +0100, Greg KH wrote:
> > > > > bit-banging an ir
* Ladislav Michl [171128 17:01]:
> On Tue, Nov 28, 2017 at 06:39:13AM -0800, Tony Lindgren wrote:
> > Limiting things to C1 with cpuidle is probably what you need
> > for having USB also working.
>
> With echo 1 > /sys/devices/system/cpu/cpu0/cpuidle/state{1-6}/disable
> jitter is about 100us whi
On Tue, Nov 28, 2017 at 10:00:32AM -0500, Alan Stern wrote:
> On Tue, 28 Nov 2017, Greg KH wrote:
>
> > On Mon, Nov 27, 2017 at 11:08:33PM +0100, Ladislav Michl wrote:
> > > Hi there,
> > >
> > > USB hosts do not discover any connected device on OMAP3 based board
> > > with CONFIG_PM=n. Just enab
On Tue, 28 Nov 2017, Greg KH wrote:
> On Mon, Nov 27, 2017 at 11:08:33PM +0100, Ladislav Michl wrote:
> > Hi there,
> >
> > USB hosts do not discover any connected device on OMAP3 based board
> > with CONFIG_PM=n. Just enabling this option is enough to restore working
> > behaviour. Nothing unusu
* Ladislav Michl [171128 14:31]:
> On Tue, Nov 28, 2017 at 06:11:31AM -0800, Tony Lindgren wrote:
> > * Ladislav Michl [171128 09:42]:
> > > On Tue, Nov 28, 2017 at 10:30:54AM +0100, Greg KH wrote:
> > > > bit-banging an ir decoder, ugh, you are in for a world of hurt. Can't
> > > > you put a ch
On Tue, Nov 28, 2017 at 06:11:31AM -0800, Tony Lindgren wrote:
> * Ladislav Michl [171128 09:42]:
> > On Tue, Nov 28, 2017 at 10:30:54AM +0100, Greg KH wrote:
> > > bit-banging an ir decoder, ugh, you are in for a world of hurt. Can't
> > > you put a chip on the device that does this for you in h
* Ladislav Michl [171128 09:42]:
> On Tue, Nov 28, 2017 at 10:30:54AM +0100, Greg KH wrote:
> > bit-banging an ir decoder, ugh, you are in for a world of hurt. Can't
> > you put a chip on the device that does this for you in hardware?
>
> OMAP has DM timer which can be externally trigered on edg
On Tue, Nov 28, 2017 at 11:03:50AM +0200, Felipe Balbi wrote:
> Ladislav Michl writes:
> > On Tue, Nov 28, 2017 at 08:33:28AM +0100, Greg KH wrote:
> >> On Mon, Nov 27, 2017 at 11:08:33PM +0100, Ladislav Michl wrote:
> >> > Hi there,
> >> >
> >> > USB hosts do not discover any connected device on
On Tue, Nov 28, 2017 at 10:30:54AM +0100, Greg KH wrote:
> On Tue, Nov 28, 2017 at 09:57:51AM +0100, Ladislav Michl wrote:
> > Hi Greg,
> >
> > On Tue, Nov 28, 2017 at 08:33:28AM +0100, Greg KH wrote:
> > > On Mon, Nov 27, 2017 at 11:08:33PM +0100, Ladislav Michl wrote:
> > > > Hi there,
> > > >
On Tue, Nov 28, 2017 at 09:57:51AM +0100, Ladislav Michl wrote:
> Hi Greg,
>
> On Tue, Nov 28, 2017 at 08:33:28AM +0100, Greg KH wrote:
> > On Mon, Nov 27, 2017 at 11:08:33PM +0100, Ladislav Michl wrote:
> > > Hi there,
> > >
> > > USB hosts do not discover any connected device on OMAP3 based boa
Hi,
Ladislav Michl writes:
> On Tue, Nov 28, 2017 at 08:33:28AM +0100, Greg KH wrote:
>> On Mon, Nov 27, 2017 at 11:08:33PM +0100, Ladislav Michl wrote:
>> > Hi there,
>> >
>> > USB hosts do not discover any connected device on OMAP3 based board
>> > with CONFIG_PM=n. Just enabling this option
Hi Greg,
On Tue, Nov 28, 2017 at 08:33:28AM +0100, Greg KH wrote:
> On Mon, Nov 27, 2017 at 11:08:33PM +0100, Ladislav Michl wrote:
> > Hi there,
> >
> > USB hosts do not discover any connected device on OMAP3 based board
> > with CONFIG_PM=n. Just enabling this option is enough to restore workin
On Mon, Nov 27, 2017 at 11:08:33PM +0100, Ladislav Michl wrote:
> Hi there,
>
> USB hosts do not discover any connected device on OMAP3 based board
> with CONFIG_PM=n. Just enabling this option is enough to restore working
> behaviour. Nothing unusual in log. Tested 4.14.2 and 4.15-rc1. I know
> a
Hi,
> -Original Message-
> From: Alan Stern [mailto:st...@rowland.harvard.edu]
> Sent: Saturday, March 18, 2017 12:44 AM
> To: Lipengcheng
> Cc: gre...@linuxfoundation.org; linux-usb@vger.kernel.org;
> linux-ker...@vger.kernel.org
> Subject: Re: EHCI
>
> On Fr
On Fri, 17 Mar 2017, Lipengcheng wrote:
> Hi,
> In the ehci-hub.c,the ehci_handshake(ehci, status_reg, PORT_RESET, 0,
> 1000) use that the timeout is 1000us. The 1000us timeout can not
> satisfy all the chips. The EHCI protocol describes:A host controller
> must terminate the reset and stabilize t
On Wed, 14 Sep 2016, Arun Thiruvanantha wrote:
> Hi Alan ,
> We are using linux kernel 2.6.32 version
That's a very old kernel release. A lot of bugs have been fixed since
it came out.
Can you try using a more recent version, like 4.7? It will make
debugging a lot easier.
Alan Stern
--
To
Please use Reply-To-All so that your message gets sent to the mailing
list as well as to me.
On Tue, 13 Sep 2016, Arun Thiruvanantha wrote:
> Thanks Alan for your Help
>
> I have tried dyndbg="module ehci_hcd =p" in boot command line param, But
> No effect.
>
> Also enabled USB_DEBUG flag but
On Sun, 11 Sep 2016, Arun Thiruvanantha wrote:
> Thanks for your replay.
>
> Reload means reset the hardware.
>
> these are steps doing:
>
> 1 Booting
> 2 reset
> issue will occurring after doing above steps. for more than 5 times.
What kernel version are you using?
> Also some time EUSB chi
Questions like this should always be sent to the linux-usb mailing
list.
On Sun, 11 Sep 2016, Arun Thiruvanantha wrote:
> Hi Alan,
> I am working some USB driver Issue that when we do several reload , USB
> device is not detected .
What do you mean by "reload"?
What kernel version are you usin
yOn Sat, 4 Jun 2016, Greg KH wrote:
> On Sat, Jun 04, 2016 at 08:32:43PM +0200, Michał Pecio wrote:
> > Hi,
> >
> > Why high-bandwidth USB 1.1 isochronous devices don't work on 2.0 hosts?
You mean, on EHCI hosts -- they do work on other USB-2 host
controllers, as far as I know.
Basically, the
On Sat, Jun 04, 2016 at 08:32:43PM +0200, Michał Pecio wrote:
> Hi,
>
> Why high-bandwidth USB 1.1 isochronous devices don't work on 2.0 hosts?
>
> I have an ADSL modem of this kind which I would like to use on a
> companion-less 2.0 host in my router, but I can't because it fails with
> ENOSPC e
On 13 April 2016 at 17:25, Alan Stern wrote:
> On Wed, 13 Apr 2016, Rafał Miłecki wrote:
>> I'm trying to debug some EHCI issue so I enabled debugging by adding
>> ccflags-y := -DDEBUG
>> to the drivers/usb/host/Makefile
>>
>> Some of debugging lines contain random memory, e.g.:
>> ehci-platform e
On Wed, 13 Apr 2016, Rafał Miłecki wrote:
> Hi,
>
> I'm trying to debug some EHCI issue so I enabled debugging by adding
> ccflags-y := -DDEBUG
> to the drivers/usb/host/Makefile
>
> Some of debugging lines contain random memory, e.g.:
> ehci-platform ehci-platform.0: .|��`|���5P5@�3�.��*�.|��o
On Wed, Apr 13, 2016 at 08:44:25AM +0200, Rafał Miłecki wrote:
> Hi,
>
> I'm trying to debug some EHCI issue so I enabled debugging by adding
> ccflags-y := -DDEBUG
> to the drivers/usb/host/Makefile
>
> Some of debugging lines contain random memory, e.g.:
> ehci-platform ehci-platform.0: .|��`|�
On Wed, 30 Mar 2016, Lipengcheng wrote:
> Hi,
> > The ohci-platform and ehci-platform drivers already perform their own
> root-hub and bus resets.
> I don't understand the sentence clearly.
>
> Synopsis control VERSION： DesignWare Cores USB2.0 Host-AHB Controller,
> Version 2.98a
> The syno
Sent: Friday, March 18, 2016 1:52 AM
> To: Lipengcheng
> Cc: ba...@ti.com; chasemetzge...@gmail.com; baolu...@linux.intel.com;
> mj...@coreos.com; kbo...@gmail.com; jun...@freescale.com;
> robert.schlabb...@gmx.net; linux-usb@vger.kernel.org
> Subject: Re: ehci and ohci reset numb
On Thu, Mar 17, 2016 at 02:16:56AM +, Lipengcheng wrote:
>
>
> Hi,
Please resend in non-html format so that the mailing list does not
reject your messages.
thanks,
greg k-h
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majord...@vger
On Thu, 17 Mar 2016, Lipengcheng wrote:
> Hi,
>In the files of ohci-platform.c and ehci-platform.c, they have only a
> control reset. Can the files have one more controller reset?
Currently only one reset is allowed.
>Our usb2 controller using a synopsis, need bus reset, root hub reset,
On Wed, 2016-01-27 at 11:33 +0530, Muni Sekhar wrote:
> [ Please keep me in CC as I'm not subscribed to the list]
>
> Hello,
>
> My test system is having two USB1.1 (OHCI) controllers and one USB2
> (EHCI) controller.
>
> I am assuming When a High-Speed device is connected to the port, the
> EH
> One final update on this topic: the kernel config was missing the
> CONFIG_USB_EHCI_ROOT_HUB_TT option. It turns out that the USB IP embeded a
> Transaction Translator and there is a check in ehci_halt() that aborts the
> routine in case of a Transaction Translator in the ehci controller. The che
On 06/12/2015 01:37 PM, Valentin Longchamp wrote:
> On 06/08/2015 01:46 PM, Valentin Longchamp wrote:
>> On 06/06/2015 02:17 PM, Sebastian Hesselbarth wrote:
>>> On 05.06.2015 17:19, Andrew Lunn wrote:
On Fri, Jun 05, 2015 at 04:34:54PM +0200, Valentin Longchamp wrote:
> I am currently bri
On 06/08/2015 01:46 PM, Valentin Longchamp wrote:
> On 06/06/2015 02:17 PM, Sebastian Hesselbarth wrote:
>> On 05.06.2015 17:19, Andrew Lunn wrote:
>>> On Fri, Jun 05, 2015 at 04:34:54PM +0200, Valentin Longchamp wrote:
I am currently bringing up the USB 2.0 Host controller of the Bobcat's
>>
On 06/06/2015 02:17 PM, Sebastian Hesselbarth wrote:
> On 05.06.2015 17:19, Andrew Lunn wrote:
>> On Fri, Jun 05, 2015 at 04:34:54PM +0200, Valentin Longchamp wrote:
>>> I am currently bringing up the USB 2.0 Host controller of the Bobcat's
>>> (98DX4122
>>> Marvell switch) internal kirkwood CPU o
On 05.06.2015 17:19, Andrew Lunn wrote:
On Fri, Jun 05, 2015 at 04:34:54PM +0200, Valentin Longchamp wrote:
I am currently bringing up the USB 2.0 Host controller of the Bobcat's (98DX4122
Marvell switch) internal kirkwood CPU on a variation of Keymile's km_kirwood
hardware (kirkwood-km_kirkwood
On Fri, Jun 05, 2015 at 04:34:54PM +0200, Valentin Longchamp wrote:
> Hello,
>
> I am currently bringing up the USB 2.0 Host controller of the Bobcat's
> (98DX4122
> Marvell switch) internal kirkwood CPU on a variation of Keymile's km_kirwood
> hardware (kirkwood-km_kirkwood.dts).
>
> When the d
On 09.03.2015 13:10, Adrian-Ken Rueegsegger wrote:
> Hello,
>
> On 01/23/2015 12:54 PM, Mathias Nyman wrote:
>> I don't know what will happend if we try to write to xhci portswitching
>> registers
>> on platforms with xhci only, so just removing the ehci check is a bit risky
>> considering futur
Hello,
On 01/23/2015 12:54 PM, Mathias Nyman wrote:
> I don't know what will happend if we try to write to xhci portswitching
> registers
> on platforms with xhci only, so just removing the ehci check is a bit risky
> considering future platforms.
>
> I need to ask around internally and see if
Hi
On 23.01.2015 13:02, Adrian-Ken Rueegsegger wrote:
> Hello,
>
> We run Linux as a VM on top of the Muen Separation Kernel [1] where we
> have implemented PCI device passthrough using VT-d.
>
> I have come across an issue where USB ports of an assigned xHCI
> controller are no longer being ena
On Thu, 4 Sep 2014, Christian Melki wrote:
> Hi Alan.
>
> The machine has only two cameras inserted (no hids, nothing else).
> While the cameras have an interrupt endpoint, I disabled it in
> uvc_video. Still I don't get more than two cameras into the schedule.
> So there are no interrupt endpoin
.edu]
Sent: Wednesday, 03 September 2014 6:16 PM
To: Christian Melki
Cc: linux-usb@vger.kernel.org
Subject: Re: EHCI Isochronous schedule full?
On Wed, 3 Sep 2014, Christian Melki wrote:
> I've probably got this wrong...
>
> I try to run several cameras with compressed streams (MJPEG) using
On Wed, 3 Sep 2014, Christian Melki wrote:
> I've probably got this wrong...
>
> I try to run several cameras with compressed streams (MJPEG) using maxpacket
> 3*1024 isoc-endpoints.
> EHCI should be able to transmit 8 microframes * 1024 bytes * 3 packets of
> data per frame (approx 24MB/sec).
It does not matter if I reduce resolution to 640x480x1 fps.
I still can only use two cameras. maxpacket requirement for those streams drop
a bit, but it doesn't help.
Kernel is 3.6.4, powerpc 8347 machine.--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a mes
On Sat, May 24, 2014 at 11:18:31AM -0400, Alan Stern wrote:
> On Sat, 24 May 2014, Dr. Werner Fink wrote:
>
> >
> > During debugging and rebooting I've seen the problem again:
>
> What patch were you using when you saw the problem again?
The attached one (as it does not help I've attached it;)
On Sat, 24 May 2014, Dr. Werner Fink wrote:
> On Wed, May 14, 2014 at 10:32:21AM -0400, Alan Stern wrote:
> > On Tue, 13 May 2014, Dr. Werner Fink wrote:
> >
> > > On Tue, May 13, 2014 at 06:10:46PM +0200, Dr. Werner Fink wrote:
> > > > On Tue, May 13, 2014 at 11:59:38AM -0400, Alan Stern wrote:
On Wed, May 14, 2014 at 10:32:21AM -0400, Alan Stern wrote:
> On Tue, 13 May 2014, Dr. Werner Fink wrote:
>
> > On Tue, May 13, 2014 at 06:10:46PM +0200, Dr. Werner Fink wrote:
> > > On Tue, May 13, 2014 at 11:59:38AM -0400, Alan Stern wrote:
> > > >
> > > > What about something like this instead
On Tue, 13 May 2014, Dr. Werner Fink wrote:
> On Tue, May 13, 2014 at 06:10:46PM +0200, Dr. Werner Fink wrote:
> > On Tue, May 13, 2014 at 11:59:38AM -0400, Alan Stern wrote:
> > >
> > > What about something like this instead?
> > >
> > > masked_status = status & (INTR_MASK | STS_FLR);
> > >
On Tue, May 13, 2014 at 06:10:46PM +0200, Dr. Werner Fink wrote:
> On Tue, May 13, 2014 at 11:59:38AM -0400, Alan Stern wrote:
> >
> > What about something like this instead?
> >
> > masked_status = status & (INTR_MASK | STS_FLR);
> >
> > /* Shared IRQ? */
> > if (!masked_status ||
On Tue, May 13, 2014 at 11:59:38AM -0400, Alan Stern wrote:
>
> What about something like this instead?
>
> masked_status = status & (INTR_MASK | STS_FLR);
>
> /* Shared IRQ? */
> if (!masked_status || unlikely(ehci->rh_state == EHCI_RH_HALTED)) {
> + if (status &
On Tue, 13 May 2014, Dr. Werner Fink wrote:
> OK ... the patch was changed as I had been told that I should do it this
> way. In my original code I simply use
>
> masked_status = status & (INTR_MASK | STS_FLR | STS_RECL);
>
> /* Shared IRQ? */
> if (!masked_status || unlikely(
On Tue, May 13, 2014 at 11:08:27AM -0400, Alan Stern wrote:
> Please CC: your patches to the maintainer of the driver you are
> changing.
>
> On Tue, 13 May 2014, Dr. Werner Fink wrote:
>
> > Hi,
> >
> > this bug hits my system now a long time. I had found e.g. this
> >
> > speedy kernel: [
Please CC: your patches to the maintainer of the driver you are
changing.
On Tue, 13 May 2014, Dr. Werner Fink wrote:
> Hi,
>
> this bug hits my system now a long time. I had found e.g. this
>
> speedy kernel: [ 9575.033019] irq 16: nobody cared (try booting with the
> "irqpoll" option)
>
Sorry for the late response, as I do not follow linux-usb list very closely.
I have discussed recent Intel chipsets and EHCI debug in some detail on
the coreboot mailing list [1].
As for the discussion [2] that took place here in February, I noticed
you tried with early_printk=dbgp which only
Hi Alan,
the patch fix the issue. I tested it on a notebook with a cardbus
controller and on desktop machine with a thunderbolt interface. Both are
working.
Thunderbolt will sometimes crash but i think this is a issue with
dynamic added pci bridges, which cause a lot of trouble and headache to
m
On Sun, 13 Apr 2014, Stefani Seibold wrote:
> A hot plug of an USB 2.0 EHCI controller cardbus card will result in a
> kernel crash. This is the kernel log of a vanilla 3.14 x86_64 kernel. I
> will attach my kernel config.
> [ 70.419755] ehci-pci :04:00.2: EHCI Host Controller
> [ 70.4198
On Sat, 5 Apr 2014, Beralt Meppelink wrote:
> Since an update to kernel 3.13 my system suffers from a bug, probably
> in the EHCI scheduler. I have an em28xx based DVB USB stick which is
> connected to a EHCI host and uses an isochronous endpoint to transfer
> data from the device to the host.
On Wed, Feb 26, 2014 at 03:40:52PM -0500, Alan Stern wrote:
> On Wed, 26 Feb 2014, Stefani Seibold wrote:
>
> > Hi Alan,
> >
> > i just checked the current linux git tree and the 3.13 kernel.
> >
> > In both i miss your fix for the thread irq support in the ehci hcd which
> > you had promised.
>
On Wed, 26 Feb 2014, Stefani Seibold wrote:
> Hi Alan,
>
> i just checked the current linux git tree and the 3.13 kernel.
>
> In both i miss your fix for the thread irq support in the ehci hcd which
> you had promised.
The patch has not been merged yet. It was submitted here:
http://m
On Wed, 19 Feb 2014, David Laight wrote:
> > It is quite possible that the debug port on this motherboard is not
> > wired to a USB connector. If that's true, the only way you will get
> > the debug device to work is by connecting it directly to a header on
> > the motherboard.
>
> Is that likel
> It is quite possible that the debug port on this motherboard is not
> wired to a USB connector. If that's true, the only way you will get
> the debug device to work is by connecting it directly to a header on
> the motherboard.
Is that likely to be the single USB header on many motherboards?
On Wed, 19 Feb 2014, Lu, Baolu wrote:
> Thanks for reply and help. I attached an Ajays NET20DC to the USB port.
> It seems not help here.
>
> Below is the dmesg and lsusb output.
>
> [root@localhost ~]# uname -a
> Linux localhost.localdomain 3.12.8 #2 SMP Tue Feb 18 06:09:46 CST 2014
> x86_64
On Wed, Feb 19, 2014 at 04:45:57PM +0800, Lu, Baolu wrote:
> Thanks for reply and help. I attached an Ajays NET20DC to the USB port.
What is that device? Is it a EHCI debug device? Are you sure you
plugged the correct end in? (The devices I have don't say which way
they go, and I always reverse
Thanks for reply and help. I attached an Ajays NET20DC to the USB port.
It seems not help here.
Below is the dmesg and lsusb output.
[root@localhost ~]# uname -a
Linux localhost.localdomain 3.12.8 #2 SMP Tue Feb 18 06:09:46 CST 2014
x86_64 x86_64 x86_64 GNU/Linux
[root@localhost ~]# lsusb -t
On Tue, Feb 18, 2014 at 09:01:29AM -0800, Greg KH wrote:
> On Tue, Feb 18, 2014 at 02:46:00PM +0800, Lu, Baolu wrote:
> > Hi list,
> >
> > Linux kernel (3.12.8) fails to setup EHCI debug port on my Sandy Bridge
> > server. This seems to be a normal thing as I tried on other machines and got
> > th
On Tue, Feb 18, 2014 at 02:46:00PM +0800, Lu, Baolu wrote:
> Hi list,
>
> Linux kernel (3.12.8) fails to setup EHCI debug port on my Sandy Bridge
> server. This seems to be a normal thing as I tried on other machines and got
> the same result.
Do you have a EHCI debug connector to attach to it?
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 Wed, 29 Jan 2014, Denis Kirjanov wrote:
> Hi,
>
> Not sure if it's been posted already. I'm running the latest Linus tree.
>
> [ 10.636228] INFO: trying to register non-static key.
> [ 10.636782] the code is fine but needs lockdep annotation.
> [ 10.637271] turning off the locking corre
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
On Thu, 19 Dec 2013, Ken Harris wrote:
> David:
>
> I'm having trouble getting USB working on my Gateway LT41P laptop.
>
> I get an error message " EHCI: BIOS handoff failed (BIOS bug?)
> 01010001" and I wonder if you can suggest any fixes or workarounds.
> The EHCI controller works on MS Window
On Wed, Dec 18, 2013 at 12:00 AM, Ken Harris wrote:
> On Tue, Dec 17, 2013 at 6:47 PM, Ken Harris wrote:
>> On Tue, Dec 17, 2013 at 5:33 PM, Ken Harris wrote:
>>> On Tue, Dec 17, 2013 at 1:03 PM, Sarah Sharp
>>> wrote:
>>>
> On Tue, 17 Dec 2013, Ken Harris wrote:
>>>
> > Sebastien:
FYI, when I boot MS Windows 8.1, it says the USB controller is "Intel
EHCI 0F34" (w/ "usbehci.sys" driver).
On Tue, Dec 17, 2013 at 7:12 PM, Adam Williamson wrote:
> Ken Harris wrote:
>>On Tue, Dec 17, 2013 at 1:03 PM, Sarah Sharp
>> wrote:
>>
On Tue, 17 Dec 2013, Ken Harris wrote:
>>
Ken Harris wrote:
>On Tue, Dec 17, 2013 at 1:03 PM, Sarah Sharp
> wrote:
>
>>> On Tue, 17 Dec 2013, Ken Harris wrote:
>
>>> > Sebastien:
>>> >
>>> > Thanks for the info. I just tried Linux
>3.13.0-0.rc3.git5.1.fc21.i686
>>> > (from Fedora rawhide) and I still get the same error messages and
>USB
1 - 100 of 201 matches
Mail list logo
