On 2014-12-18 17:10, Alan Stern wrote:
> On Thu, 18 Dec 2014, Udo van den Heuvel wrote:
>> In fact the airspy samples at 20 MSPS with 2 bytes per sample, but the
>> host converts that to the I/Q pairs at 10 MSPS, with 2 bytes for each I
>> and Q. (I was explained in #airspy)
&
On 2014-12-18 16:23, Alan Stern wrote:
>>> The bug report says there should be 10 M samples per second. How many
>>> bytes are in a sample? 2?
>>
>> I and Q samples are two bytes each.
>
> What is an I sample? What is a Q sample?
I and Q samples describe the radio signal received by the airs
On 2014-12-17 18:25, Alan Stern wrote:
>> Please let me know what info I should add to help find the root cause.
>
> What are we supposed to see? The lsusb output in the bug report lists
> a bunch of devices, but it's not clear which one is the airspy.
Perhaps bus 4, device 10?
Udo
--
To unsu
On 2014-12-17 18:25, Alan Stern wrote:
> On Sat, 13 Dec 2014, Udo van den Heuvel wrote:
> What are we supposed to see? The lsusb output in the bug report lists
> a bunch of devices, but it's not clear which one is the airspy.
I did not program the tools. But the other device
Hello,
I noticed an usb related issue when recording from my airspy device;
so I created a bug in the bugzilla:
https://bugzilla.kernel.org/show_bug.cgi?id=89671
Please let me know what info I should add to help find the root cause.
Kind regards,
Udo
--
To unsubscribe from this list: send the li
On 2014-08-14 15:23, Mathias Nyman wrote:
> The error:
> [53009.847233] xhci_hcd :02:00.0: ERROR: unexpected command completion
> code 0x11.
>
> Means we got a parameter error, one of the values the xhci driver sends to
> the controller
> in the configure endpoint command is invalid.
Are my
On 2014-08-12 17:07, Hans de Goede wrote:
> for you. Might be fixed by this commit:
> https://git.kernel.org/cgit/linux/kernel/git/gregkh/usb.git/commit/drivers/usb/host?h=usb-next&id=3213b151387df0b95f4eada104f68eb1c1409cb3
That commit already appears to be in my kernel tree.
Kind regards,
Udo
On 2014-08-12 18:27, Hans Verkuil wrote:
> It was a bit confusing, but he has two problems: one pwc, one (the warning)
> for
> uvc.
Indeed.
Do I need to provide additional info to help find the root cause(s)?
Kind regards,
Udo
--
To unsubscribe from this list: send the line "unsubscribe linux-u
On 2014-08-12 17:07, Hans de Goede wrote:
> lspci -nn
# lspci -nn
00:00.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Family
15h (Models 10h-1fh) Processor Root Complex [1022:1410]
00:00.2 IOMMU [0806]: Advanced Micro Devices, Inc. [AMD] Family 15h
(Models 10h-1fh) I/O Memory Management
On 2014-08-08 13:24, Udo van den Heuvel wrote:
> unexpected command
> completion code 0x11
Is bug https://bugzilla.kernel.org/show_bug.cgi?id=70531 relevant here?
Kind regards,
Udo
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a m
controller: Etron Technology, Inc. EJ168 USB 3.0 Host
Controller (rev 01)
03:06.0 Serial controller: MosChip Semiconductor Technology Ltd. PCI
9835 Multi-I/O Controller (rev 01)
And the Etron EJ168 is the only USB3 provider here?
How can we fix this issue?
Kind regards,
Udo
On 2014-08-08 05:4
On 2014-08-04 11:17, Laurent Pinchart wrote:
> (CC'ing Hans de Goede, the pwc maintainer, and the linux-media mailing list)
>
> On Saturday 02 August 2014 15:10:01 Udo van den Heuvel wrote:
>> Hello,
>>
>> I moved a PWC webcam to a USB3 port, and this happened:
I
Hello,
I moved a PWC webcam to a USB3 port, and this happened:
[53008.911811] usb 5-2: new full-speed USB device number 2 using xhci_hcd
[53009.213504] usb 5-2: New USB device found, idVendor=0471, idProduct=0311
[53009.213514] usb 5-2: New USB device strings: Mfr=0, Product=0,
SerialNumber=1
[53
On 2013-12-17 22:08, Sarah Sharp wrote:
> A simple fix is to turn off CONFIG_USB_DEBUG. That's what causes the
> xHCI dynamic debugging to be enabled by default.
3.12.6 with CONFIG_USB_DEBUG turned off fixes the xhci_hcd debugging.
Thanks,
Udo
--
To unsubscribe from this list: send the line "un
On 2013-12-10 16:03, Oliver Neukum wrote:
>> Thanks, but some of the messages look quite hardcoded.
>> Is there a patch to get rid of them?
>
> More patches concerning dynamic debugging are in the queue for 3.14
> It looks like on your system it is by default switched on. You
> can switch it off a
On 2013-12-09 08:53, Oliver Neukum wrote:
> You have XHCI debugging on. This is most likely a side effect
> of teh switch to dynamic debugging in 3.12. But this should be
> discussed on linux-usb.
Thanks, but some of the messages look quite hardcoded.
Is there a patch to get rid of them?
Kind re
On 2013-08-28 21:37, Alan Stern wrote:
>>> No, if you unload the ohci-hcd driver then the webcam won't be used.
>>> Are you certain that merely stopping the daemon program will prevent
>>> the problem?
>>
>> Quite certain but retesting can confirm that.
>
> Maybe without activity, the OHCI cont
On 2013-08-27 19:43, Alan Stern wrote:
>>> rmmod ohci-pci
>>> modprobe dummy-irq irq=18
>>>
>>> and see if the IRQ line gets disabled after that.
>>
>> Can I actually use that irq/ports that way? (as with no usage the
>> problem does not occur)
>
> No, if you unload the ohci-hcd driver
Hello Alan,
On 2013-08-23 21:33, Alan Stern wrote:
>> Well, I replaced the motherboard by one of the same type and same BIOS
>> version.
>> And the problem is still here.
>>
>>> kernel:[ 3013.199945] Disabling IRQ #18
>>
>> So what can we conclude?
>> Kernel bug?
>> Hardware bug?
>> Something else
On 2013-01-26 19:48, Alan Stern wrote:
>> Please explain.
>
> I can't. I don't know what's going on with your systems. But nobody
> else seems to be experiencing this problem.
Well, I replaced the motherboard by one of the same type and same BIOS
version.
And the problem is still here.
> kern
On 2013-03-28 15:35, Alan Stern wrote:
>>> When my dmesg gives me a growing number of lines like the one below,
>>> what is going on?
>>>
>>> ohci_hcd :00:12.0: urb 88023025c500 path 2 ep1in 6c16 cc 6
>>> --> status -71
>>>
>>> Please let me know!
>
> -71 errors indicate a low-level p
On 2013-01-26 15:56, Alan Stern wrote:
> That SF bit in the intrstatus register is the one causing the problem,
> I think. It is not set in the intrenable register, so the controller
> shouldn't issue any IRQs. But it does, nonetheless. Turning off SF
> apparently doesn't help -- the controller
On 2013-01-25 19:06, Alan Stern wrote:
> On Fri, 25 Jan 2013, Alan Stern wrote:
>
>> This isn't a software problem. I don't know of any way to fix it or
>> work around it in the driver. The only thing to do is stop using that
>> controller.
>
> Spoke too soon. Try this patch; maybe it will hel
On 2013-01-02 17:46, Alan Stern wrote:
> Or else leave those devices unplugged entirely -- use a network login
> instead of the USB keyboard and mouse.
When the motion service is off, i.e. the USB webcam isnt used, the
issue does not happen.
On the other hand:
If it is on, within a few days I
On 2013-01-02 17:46, Alan Stern wrote:
>> Can it be the webcam?
>> I can interchange it with another one of same type.
>
> If it's a USB webcam then it can't created unwanted IRQs. But you
> certainly should try removing it to see if that makes any difference.
Stopping the motion service help
On 2013-01-02 16:55, Alan Stern wrote:
> I don't understand. How can there be nothing more? Above you showed
> an "irq 18: nobody cared" message that appeared at 8:51 on Jan 1. It
> certainly ought to be in the dmesg log as of 9:00.
dmesg can only hold a certain amount of data.
The pwc errors t
On 2012-12-31 18:24, Alan Stern wrote:
> Can you provide the entire output? Two lines isn't enough.
It just happened again. Messages in edited form:
Jan 1 07:23:46 bobo dbus[3106]: [system] Rejected send message, 2
matched rules; type="method_return", sender=":1.1" (uid=0 pid=3076
comm="/usr/li
Hello Alan,
On 2012-12-31 18:24, Alan Stern wrote:
>> The patch works OK for the first few times:
>>
>> ohci_hcd :00:13.0: last IRQ repeated 22 times
>> ohci_hcd :00:13.0: IRQ: 24 805a
>
> Can you provide the entire output? Two lines isn't enough.
It's just the normal bootup, then t
On 2012-11-19 17:41, Alan Stern wrote:
> On Sat, 17 Nov 2012, Udo van den Heuvel wrote:
>> How to proceed next?
>
> Firstly, what does /proc/interrupts say?
>
> Secondly, try building a kernel with the patch below and
> CONFIG_USB_DEBUG enabled. Let's see wha
On 2012-11-19 17:41, Alan Stern wrote:
> Firstly, what does /proc/interrupts say?
# cat /proc/interrupts
CPU0 CPU1 CPU2 CPU3
0: 40 0 0 0 IO-APIC-edge timer
1:631640677734 IO-APIC-edge
On 2012-11-19 17:41, Alan Stern wrote:
>> How to proceed next?
>
> Firstly, what does /proc/interrupts say?
# cat /proc/interrupts
CPU0 CPU1 CPU2 CPU3
0: 39 0 0 0 IO-APIC-edge timer
1:716721730
On 2012-07-15 20:28, Alan Stern wrote:
> Um, I think you missed the point. The whole idea of the test is to see
> what happens while the controller is unbound from the driver. Binding
> it again defeats the purpose.
The problem still happens. irq 18 is dsiabled every now and then.
This time on
Well,
The issue appeared again.
irq 18 was disabled, one pwc webcam was on that irq.
This time on new hardware: Gigabyte F2A85X-UP4 with A10-5800K APU.
The box was busy with it's raid10 array, this time, by running bonnie++;
also a raid-check was in progress. (unknown at the time)
So what does t
On 2012-07-15 17:55, Udo van den Heuvel wrote:
> After doing this I could modprobe pwc and start mrtg without problem.
Euh: s/mrtg/motion/
Udo
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majord...@vger.kernel.org
More majo
On 2012-07-15 17:35, Alan Stern wrote:
> echo :00:13.1 >/sys/bus/pci/drivers/ohci_hcd/unbind
Afterwards I did:
> echo :00:13.1 >/sys/bus/pci/drivers/ohci_hcd/bind
And I saw:
Jul 15 17:50:30 surfplank2 kernel: ohci_hcd :00:13.1: remove, state 1
Jul 15 17:50:30 surfplank2 kernel: usb
On 2012-07-15 16:28, Udo van den Heuvel wrote:
> After disabling:
And somewhat later:
bus pci, device :00:12.0
OHCI Host Controller
ohci_hcd
OHCI 1.0, NO legacy support registers, rh state running
control 0x083 HCFS=operational CBSR=3
cmdstatus 0x0 SOC=0
intrstatus 0x0024 FNO
On 2012-07-12 16:54, Alan Stern wrote:
> On Thu, 12 Jul 2012, Udo van den Heuvel wrote:
>
>> # cat /proc/interrupts
(...)
>> 18: 25190 18052161 21311 IO-APIC-fasteoi
>> ohci_hcd:usb5, ohci_hcd:usb6, ohci_hcd:usb7
(...)
>> So what can we
On 2012-07-12 15:43, Jan Ceuleers wrote:
> On 07/12/2012 03:23 PM, Udo van den Heuvel wrote:
>> How to list what modules/programs are using that irq?
>
> cat /proc/interrupts
# cat /proc/interrupts
CPU0 CPU1 CPU2 CPU3
0: 40 0
On 2012-07-11 17:15, Alan Stern wrote:
> On Wed, 11 Jul 2012, Udo van den Heuvel wrote:
>
>> New occurrence:
>
>> Any clues and/or updates?
>
> Didn't you see the message I posted on Monday?
>
> http://marc.info/?l=linux-usb&m=134186054713868&am
On 2012-07-09 15:54, Clemens Ladisch wrote:
> (forwarded to linux-usb)
>
> Udo van den Heuvel wrote:
>>
>> One moment the box is runing OK.
>> One moment the 3.4.4 kernel decides to disable an interrupt.
>> Why?
>>
>> Jul 8 07:43:49 box3 ntpd[
On 2012-07-09 15:54, Clemens Ladisch wrote:
> (forwarded to linux-usb)
>
> Udo van den Heuvel wrote:
>> Hello,
>>
>> One moment the box is runing OK.
>> One moment the 3.4.4 kernel decides to disable an interrupt.
>> Why?
>>
>> Jul 8 07:43:49
41 matches
Mail list logo
