sb
2016-09-21 / 17:10:07 ♒♒♒ ☺
- --
Ritesh Raj Sarraf
RESEARCHUT - http://www.researchut.com
"Necessity is the mother of invention."
-BEGIN PGP SIGNATURE-
iQIcBAEBCgAGBQJX4nIMAAoJEKY6WKPy4XVpg4gP/Rkp5Wje2vTUHwnrJZzAKd65
V1VWkTyCfpbCTw4nAyMbzDevyoXJf3P+ktrcyQo
ess.
Sep 21 16:19:41 learner kernel: usb 2-4: Device not responding to setup address.
Sep 21 16:19:41 learner kernel: usb 2-4: device not accepting address 18, error
- -71
Sep 21 16:19:41 learner kernel: usb 2-4: new high-speed USB device number 19
using xhci_hcd
- --
Ritesh Raj Sarraf
RESEARCHUT
ets. My guess is that it won't.
No. We tried it in the beginning. And the resets were still seen.
Thanks.
- --
Ritesh Raj Sarraf
RESEARCHUT - http://www.researchut.com
"Necessity is the mother of invention."
-BEGIN PGP SIGNATURE-
iQIcBAEBCgAGBQJX4Vr/AAoJEKY6WKPy
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Hello Alan,
On Tue, 2016-09-20 at 10:16 -0400, Alan Stern wrote:
> This is a lot better. No more I/O errors.
>
> We still have irregular suspends and resumes, but that's to be
> expected. More worrying are the spontaneous disconnects. They
dev(host));
> if (host->eject)
> break;
>
- --
Ritesh Raj Sarraf
RESEARCHUT - http://www.researchut.com
"Necessity is the mother of invention."
-BEGIN PGP SIGNATURE-
iQIcBAEBCgAGBQJX4S1BAAoJEKY6W
if (likely(status == 0)) {
> status = hcd->driver->urb_enqueue(hcd, urb,
> mem_flags);
> + if (status == -EHOSTUNREACH)
> + dump_stack();
> if (unlikely(status))
>
usb_storage driver; it uses the SCSI interface,
> not the MMC interface.
>
> > If neither of the above works, the next step could be to start
> > checking error codes in the mmc core and in the rtsx_usb_sdmmc driver,
> > from the calls to pm_ru
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Hello Ulf and Alan,
On Fri, 2016-09-09 at 19:34 +0530, Ritesh Raj Sarraf wrote:
> For #2, I'm building the 4.8-rc5 kernel with the following change. This build
> does not include the previous change you had suggested (related to
> PO
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On Fri, 2016-09-09 at 18:44 +0530, Ritesh Raj Sarraf wrote:
> On Fri, 2016-09-09 at 12:54 +0200, Ulf Hansson wrote:
> > This affects the way the core calls the host driver's ->set_ios()
> > callback. Earlier it was invoked fir
her of the above will actually solve the problem, so I guess we
> anyway need take a closer look to understand why the usb device is
> accessed when it is actually runtime suspended.
>
> BTW, Ritesh you could also run a git bisect to find out if/when this
> became broken.
What starti
able to hit the issue again, with your patch applied. I tried it on top of
the 4.8-rc5 kernel.
I ensured to capture usbmon trace.
https://people.debian.org/~rrs/tmp/usbmon-ulf.txt.gz
- --
Ritesh Raj Sarraf
RESEARCHUT - http://www.researchut.com
"Necessity is the mother of inve
does not say whether this was happening.
> One way to tell is to look at a usbmon trace (like we did before).
https://people.debian.org/~rrs/tmp/usbmon.txt.gz
This should have the logs you asked for, running on 4.8-rc4.
- --
Ritesh Raj Sarraf
RESEARCHUT - http://www.researchut.com
"Nec
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On Sun, 2016-09-04 at 17:02 +0530, Ritesh Raj Sarraf wrote:
> > Sorry for the delay! We have had some regressions for 4.8 rc1 in the
> > mmc block layer. Those problem should be resolved by now.
> >
> > By reading from t
is issue has been around with previous kernels too.
> Perhaps you can run a test on a 4.8 rc4 kernel, just to double check.
> The 4.8 rc4, contains the following fixes in the mmc block layer.
>
> commit 7afafc8a44bf ("block: Fix secure erase")
> commit 869c554808cc
logy Express, Inc.
>
> It's hard to tell what that means.
>
> There's a small possibility that the xhci-hcd debugging information
> might help, if you have it enabled when a reset occurs. But I won't be
> able to interpret it; you'll need help from Mathias.
I haven't noticed th
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Hello Alan,
On Thu, 2016-08-25 at 19:04 +0530, Ritesh Raj Sarraf wrote:
> > As you mentioned above, there's another aspect to power management
> > besides runtime PM, namely Link Power Management. Perhaps the device
> >
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Hello Alan,
On Wed, 2016-08-24 at 10:10 -0400, Alan Stern wrote:
> On Wed, 24 Aug 2016, Ritesh Raj Sarraf wrote:
>
> > -BEGIN PGP SIGNED MESSAGE-
> > Hash: SHA512
> >
> > On Tue, 2016-08-23 at 15:14 -0400
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Hello Alan,
Please find some findings below.
On Wed, 2016-08-24 at 15:01 +0530, Ritesh Raj Sarraf wrote:
> I have a question though. For power saving, I use Laptop Mode Tools. Based on
> power state (AC or BATT), it enables/disables power
= rtsx_usb_pre_reset,
> .post_reset = rtsx_usb_post_reset,
> .id_table = rtsx_usb_usb_ids,
> - .supports_autosuspend = 1,
> .soft_unbind= 1,
> };
>
- --
Ritesh Raj Sarraf
RESEARCHUT - http://www.researchut.com
"Nec
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On Tue, 2016-08-23 at 14:21 +0530, Ritesh Raj Sarraf wrote:
> In one of yesterday's email, I have shared the output of
> /sys/kernel/debug/usb/devices before the bug is triggered. The same I've
> pasted
> below.
>
> T: Bus=01 L
rot=50 Driver=rtsx_usb
E: Ad=01(O) Atr=02(Bulk) MxPS= 512 Ivl=0ms
E: Ad=82(I) Atr=02(Bulk) MxPS= 512 Ivl=0ms
E: Ad=83(I) Atr=03(Int.) MxPS= 3 Ivl=64ms
I'll pick the same again when I reboot.
- --
Ritesh Raj Sarraf
RESEARCHUT - http://www.researchut.com
"Necessity is the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On Mon, 2016-08-22 at 21:01 +0530, Ritesh Raj Sarraf wrote:
> >
> > Even after fresh unload/load, the acutal problematic devid "0bda:0129", does
> > not appear. I'll report back again after a fresh reboot.
> >
&
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Dropping Alan from To list.
On Mon, 2016-08-22 at 20:09 +0530, Ritesh Raj Sarraf wrote:
> On Mon, 2016-08-22 at 18:11 +0530, Ritesh Raj Sarraf wrote:
> >
> >
> > I'll post back again once I have captured the relevant log
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On Mon, 2016-08-22 at 18:11 +0530, Ritesh Raj Sarraf wrote:
>
> I'll post back again once I have captured the relevant logs.
>
> Thank you for looking into this.
It got more tricky to pick the logs.
When the bug is hit, the device v
gt; Aug 19 15:46:12 learner kernel: xhci_hcd :00:14.0: // Ding dong!
> Aug 19 15:46:12 learner kernel: xhci_hcd :00:14.0: Removing canceled TD
> starting at 0x9a2b2840 (dma).
>
> A usbmon log (together with a dmesg) could give some more clues
> see Documentation/usb/usbmon.txt
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
I am not sure if the logs ever reached the list. I've uploaded the logs here [1]
for convenience.
[1] https://people.debian.org/~rrs/tmp/usb-xhci-dmesg.txt.gz
On Fri, 2016-08-19 at 15:56 +0530, Ritesh Raj Sarraf wrote:
> Hello Mat
So I'll wait for Mathias' comment on this thread, hoping he can triage it
if a bug or not.
In case more information is required, please let me know on my email.
Thanks,
Ritesh
- --
Ritesh Raj Sarraf
RESEARCHUT - http://www.researchut.com
"Necessity is the mother of invention."
--
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Hello Alan,
On Thu, 2016-08-11 at 23:12 +0530, Ritesh Raj Sarraf wrote:
> On Thu, 2016-08-11 at 13:01 -0400, Alan Stern wrote:
> > > I guess so. I get frequent resets on my USB port for some of the hardware.
> > >
> > &g
gt; Probably not, but with no other information it's impossible to be
> certain.
- --
Ritesh Raj Sarraf
RESEARCHUT - http://www.researchut.com
"Necessity is the mother of invention."
-BEGIN PGP SIGNATURE-
iQIcBAEBCgAGBQJXrLkTAAoJEKY6WKPy4XVpBj4P/2SpNI/9OMQjt
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Hello Alan,
On Wed, 2016-08-10 at 17:20 -0400, Alan Stern wrote:
> On Wed, 10 Aug 2016, Ritesh Raj Sarraf wrote:
>
> The device was disconnected electronically.
>
> How often does this happen? After the disconnect occurs
., Ltd. RTL8723BE PCIe
Wireless Network Adapter
2016-08-10 / 17:49:40 ♒♒♒ ☺
--
Ritesh Raj Sarraf
RESEARCHUT - http://www.researchut.com
"Necessity is the mother of invention."Bus 003 Device 002: ID 8087:8000 Intel Corp.
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root h
31 matches
Mail list logo
