off-topic.
Windows sucks. ;)
Jan
Am 08.06.2015 um 19:15 schrieb JPT:
> Hi,
>
> whenever I connect my Samsung Galaxy Express in Download Mode to my PC,
> the following happens:
> this repeats until cdc runs out of some handles (64)
> currently it's 8:
> $ lsmod|gre
Hi,
whenever I connect my Samsung Galaxy Express in Download Mode to my PC,
the following happens:
> kernel: [ 93.200732] usb 1-5.1: new high-speed USB device number 11 using
> xhci_hcd
> kernel: [ 93.289458] usb 1-5.1: New USB device found, idVendor=04e8,
> idProduct=685d
> kernel: [ 93.
Hi,
I got a similar crash now with USB-2.0.
Took longer to happen, but did, see attached log.
This makes it more likely the problem is located in DVB code not USB.
Will try it on my PC now.
At least I already get messages like
kernel: [680947.641704] technisat-usb2: i2c-error: 60 = 7
If it cras
Am 06.01.2015 um 18:38 schrieb Greg KH:
> On Tue, Jan 06, 2015 at 11:47:29AM +0100, JPT wrote:
>> Hi Greg
>>
>> Am 06.01.2015 um 02:54 schrieb Greg KH:
>>>
>>> Is that where the kernel panics show the problem happens? Without them,
>>> there'
Hi Greg
Am 06.01.2015 um 02:54 schrieb Greg KH:
>
> Is that where the kernel panics show the problem happens? Without them,
> there's nothing we can do to help out except randomly guess, sorry.
well. at least xhci is contained in the call stack:
> [] (crc32_be) from [] (dvb_dmx_crc32+0x10/0x18
Hi,
would you like to trouble-shoot the kernel USB3/xhci code?
I had a lot of struggle with the following set up:
- Netgear ReadyNAS rn104 (ARMv7) running plain debian
- Fresco Logic FL1009 USB3 controller
- selfbuilt kernel.org kernel 3.18.1
- Technisat SkyStar USB HD (DVB-S/S2) - USB 2.0 Highs
