Hi Alan,
thank you for your effort. I applied it to 4.6.0 and I haven't seen
the USBSAN message reported anymore about this (though I do for ext4
and IP stack for example).
Tested-By: Martin MOKREJŠ
Alan Stern wrote:
Several people have reported that UBSAN doesn't like t
Hi,
anyone has ever seen this?
[ 2477.001127] kmemleak: 8 new suspected memory leaks (see
/sys/kernel/debug/kmemleak)
[ 6249.251894] perf: interrupt took too long (2506 > 2500), lowering
kernel.perf_event_max_sample_rate to 79800
[ 9951.944091] perf: interrupt took too long (3136 > 3132), low
Greg KH wrote:
On Thu, Apr 21, 2016 at 11:18:16AM +0200, Martin MOKREJŠ wrote:
Hi Greg,
thank you for your answer.
Greg KH wrote:
On Thu, Apr 21, 2016 at 12:22:49AM +0200, Martin MOKREJŠ wrote:
Hi,
I am not certain to to forward this to, so I am trying linux-usb and ext4.
Please add
Hi Greg,
thank you for your answer.
Greg KH wrote:
On Thu, Apr 21, 2016 at 12:22:49AM +0200, Martin MOKREJŠ wrote:
Hi,
I am not certain to to forward this to, so I am trying linux-usb and ext4.
Please add relevant people/lists, thank you.
# dmesg | grep "UBSAN: Undefined beha
Hi,
I am not certain to to forward this to, so I am trying linux-usb and ext4.
Please add relevant people/lists, thank you.
# dmesg | grep "UBSAN: Undefined behaviour"
[2.638843] UBSAN: Undefined behaviour in drivers/usb/host/ehci-hub.c:873:47
[8.553620] UBSAN: Undefined behaviour in f
Nyman wrote:
On 25.11.2015 00:09, Martin MOKREJŠ wrote:
Hi,
I have relatively new 13port USB 3.0 HUB based on VIAlabs 812 chipset with
two power-only charging ports: 1x1.5A and 1x2.4A (AUKEY CB-H16, from Amazon).
Sometimes, the hub (actually four 4-port hubs stitched together) chokes and all
subscribe
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Mathias Nyman wrote:
Hi
There are some xhci resume related issues which might be related to this.
Host and device initiated resume functions race, and we end up with this
similar output:
Nov 26 02:24:18 vostro kernel: xhci_hcd :0b:00.0: suspend failed because a
port is resuming
Nov 26 0
sion='3.6.2'
Nov 26 02:24:51 vostro syslog-ng[3491]: syslog-ng shutting down; version='3.6.2'
#
grep -i Prolific *
#
I am sorry there is that much data but I hope you can concentrate using
timestamps easily on those parts which seem interesting enough.
Martin
Mathias N
Hi Xenia,
thank you. I tested this patch on 3.11 kernel and the messages don't appear
anymore
upon LPM-capable device disconnect (tested with ASMedia AS2105 devices).
Not much to show here, there is just no error/warning related to LPM
while handling these devices.
Probably better test is with
Martin MOKREJŠ wrote:
> Hi Xenia,
> I tried these 3 patches and ... I will rather leave it up to you to decide
> if everything went right. Attached is a diff of dmesg from unpatched and
> patched
> 3.10.9 kernel. USB3 devices were connected before cold bootup, sadly in
>
Xenia Ragiadakou wrote:
> On 08/29/2013 04:31 PM, Martin MOKREJŠ wrote:
>> Actually, there is some new bug I haven't seen before (this is 3.10.9
>> kernel).
>> First of all, I see my TI XHCI controller does not use MSI-X anymore, will
>> have
>> to check
Alan Stern wrote:
> On Thu, 29 Aug 2013, Martin MOKREJŠ wrote:
>
>>> Since this device is 4-2, the parent hub is usb4.
>>
>> Actually, even if that would be a another USB HUB and not a PCI device (root
>> hub),
>> I would be happy if it extracted somet
Alan Stern wrote:
> On Thu, 29 Aug 2013, Martin MOKREJŠ wrote:
>
>> Hi Xenia,
>> thank you, how about inclusion of the "parent hub" number in the
>> following message (as of now):
>>
>> Parent hub missing LPM exit latency info. Power managemen
Alan Stern wrote:
> On Thu, 29 Aug 2013, Martin MOKREJŠ wrote:
>
>> Alan Stern wrote:
>>> On Thu, 29 Aug 2013, Martin MOKREJŠ wrote:
>>>
>>>> Hi Xenia,
>>>> thank you, how about inclusion of the "parent hub" number in the
>
Alan Stern wrote:
> On Thu, 29 Aug 2013, Martin MOKREJŠ wrote:
>
>> Hi Xenia,
>> thank you, how about inclusion of the "parent hub" number in the
>> following message (as of now):
>>
>> Parent hub missing LPM exit latency info. Power managemen
XHCI controller. Funny! I would say this is linux-pci issue
but provided XHCI_HCD is special and manages interrupts somewhat on its own you
may
look into that first before we ask linux-pci developers.
Martin MOKREJŠ wrote:
> Hi Xenia,
> thank you, how about inclusion of the "parent hu
Hi Xenia,
thank you, how about inclusion of the "parent hub" number in the
following message (as of now):
Parent hub missing LPM exit latency info. Power management will be impacted.
I find it awkward to later on run manually lspci/lsusb to find what is the
parent.
I think I do NOT get the
Hi Xenia,
thank you for the patch. I tried to reproduce the error with patched 3.10.9
kernel but it seems the kmemleak is indeed gone. Provided I get only these lines
logged which used to be followed by kmemleak findings I believe the original
fixed:
[15885.206032] usb 4-2.1: reset SuperSpeed US
Hi,
I was asked by Greg to post this to linux-usb. Please Cc: linux-pci or
linux-acpi
if you think they should take of that.
-
Hi,
I reported in the past all kinds of PCI/ACPI-related issues with this Dell
Vostro 3550 laptop, in respect to USB also problems with XHCI ports fallin
Hi,
I get plenty of these in /sys/kernel/debug/kmemleak:
unreferenced object 0x88019f675268 (size 32):
comm "usb-storage", pid 11411, jiffies 4310515592 (age 1538.100s)
hex dump (first 32 bytes):
05 0f 16 00 02 07 10 02 02 00 00 00 0a 10 03 00
0e 00 01 0a ff 07
21 matches
Mail list logo
