On Tue, Nov 20, 2012 at 03:40:44PM -0500, Alan Stern wrote:
> On Tue, 20 Nov 2012, Piergiorgio Sartor wrote:
>
> > This is the output of usbmod just when the problem happened:
> >
> > 8801232fd6c0 815566692 C Co:1:012:0 -2 0
> > 880130cd9000 815566767 S Co:
On Mon, Nov 26, 2012 at 11:51:39AM -0500, Alan Stern wrote:
> On Thu, 22 Nov 2012, Piergiorgio Sartor wrote:
>
> > OK, I got a log with working and then non working system,
> > so there should be a transition,
>
> The trace attached to Kernel Bugzilla #50381 didn't
On Mon, Nov 26, 2012 at 03:46:38PM -0500, Alan Stern wrote:
> On Mon, 26 Nov 2012, Piergiorgio Sartor wrote:
>
> > Hi Alan,
> >
> > thanks for the patch.
> >
> > I'll try to apply it and report the results,
> > including the USB EHCI register fi
On Sun, Dec 02, 2012 at 01:03:22PM -0500, Alan Stern wrote:
> On Sat, 1 Dec 2012, Piergiorgio Sartor wrote:
>
> > Hi Alan,
> >
> > I updated the bugzilla entry with some attachments.
> >
> > One (split in two) is the log from usbmon with the patch
> &g
On Sun, Dec 02, 2012 at 03:54:39PM -0500, Alan Stern wrote:
> On Sun, 2 Dec 2012, Piergiorgio Sartor wrote:
>
> > I'll give it another round, with dmesg
> >
> > How about the registers? Any hint there?
>
> No, not really. At least, not that I can tell at th
Hi Alan,
thanks for the patch.
One question, which kernel version should I use
for this patch?
It's the latest from git?
Thanks,
bye,
pg
On Tue, Dec 04, 2012 at 11:45:14AM -0500, Alan Stern wrote:
> On Mon, 3 Dec 2012, Piergiorgio Sartor wrote:
>
> > Hi Alan,
> >
On Tue, Dec 04, 2012 at 04:55:26PM -0500, Alan Stern wrote:
> On Tue, 4 Dec 2012, Piergiorgio Sartor wrote:
>
> > Hi Alan,
> >
> > thanks for the patch.
> >
> > One question, which kernel version should I use
> > for this patch?
> >
> >
Hi alan,
On Sat, Dec 08, 2012 at 05:33:27PM -0500, Alan Stern wrote:
> On Sat, 8 Dec 2012, Piergiorgio Sartor wrote:
>
> > Hi Alan,
> >
> > the output of lspci:
> >
> > 00:0b.1 USB Controller: nVidia Corporation MCP51 USB Controller (rev a3)
> > (pro
Hi Alan,
On Sat, Dec 08, 2012 at 10:54:00PM -0500, Alan Stern wrote:
[...]
> > Is this the reason why the "ehci", after the problem
> > is triggered, it does not work anymore?
>
> Yes. Actually, it might have started working again if you unplugged
> all your high-speed devices and then plugged
On Fri, Dec 14, 2012 at 11:02:07AM -0500, Alan Stern wrote:
> On Mon, 10 Dec 2012, Piergiorgio Sartor wrote:
>
> > > Here's an idea. This just occurred to me. Maybe when the driver is
> > > waiting for the async schedule to turn off, new QH's should not be
15, 2012 at 03:53:09PM -0500, Alan Stern wrote:
> On Sat, 15 Dec 2012, Piergiorgio Sartor wrote:
>
> > Hi Alan,
> >
> > thanks for the patch, I applied it and tested.
> >
> > I've bad news...
> > Unless I made some mistake (which can always be), I d
;ll not be anymore with
my PC, until January, so we can take it easy.
In this respect, I wish you Merry Christmas and
Happy New Year.
bye,
pg
On Mon, Dec 17, 2012 at 10:57:48AM -0500, Alan Stern wrote:
> On Sun, 16 Dec 2012, Piergiorgio Sartor wrote:
>
> > Hi Alan,
> >
> &g
012, Piergiorgio Sartor wrote:
>
> > Hi Alan,
> >
> > I applied the latest patch, changing the unlinking
> > behavior of EHCI.
> >
> > I tested quite extensively and I could not see the
> > issue (as expected). At a certain point I lost 3 HDDs,
> &g
gt; On Mon, 17 Dec 2012, Piergiorgio Sartor wrote:
>
> > Hi Alan,
> >
> > I applied the latest patch, changing the unlinking
> > behavior of EHCI.
> >
> > I tested quite extensively and I could not see the
> > issue (as expected). At a certain point I lost 3 HDDs
Hi Alan,
On Mon, Jan 14, 2013 at 10:17:52AM -0500, Alan Stern wrote:
> On Sun, 13 Jan 2013, Piergiorgio Sartor wrote:
>
> > Hi Alan,
> >
> > Happy New Year!
>
> I hope you had a good holiday break.
thanks, holiday was fine, I trust you had some rest too.
[..
Hi Alan,
On Wed, Jan 16, 2013 at 10:55:50AM -0500, Alan Stern wrote:
[...]
> I changed my mind -- it turns out that adding the fix is somewhat
> easier than unlinking one QH at a time.
>
> So now we're ready for some serious testing. The patch below is based
> on the 3.7 kernel, and it doesn't
Hi Alan,
On Tue, Jan 22, 2013 at 11:09:43AM -0500, Alan Stern wrote:
> On Fri, 18 Jan 2013, Alan Stern wrote:
>
> > Well, I guess there's no choice but to go back to the one-at-a-time
> > approach. I'll write a proper patch for that.
>
> And here it is at last. This completely replaces the ea
On Tue, Jan 22, 2013 at 12:45:32PM -0500, Alan Stern wrote:
[...]
> Yes, remove all the previous patches before applying this one.
Hi Alan,
I tested the kernel with the latest patch you provide.
I was not able to reproduce the problem, so it seems
this change is fine.
The only comment I've is t
On Fri, Jan 25, 2013 at 03:43:38PM -0500, Alan Stern wrote:
[...]
> Okay, good. I'll submit this for inclusion in the stable kernels.
Hi Alan,
one more item.
How we do proceed from the administrative point of view?
There is a bug open in Fedora (Red Hat) Bugzilla and one
in the Linux kernel Bu
On Sat, Jan 26, 2013 at 10:00:28AM -0500, Alan Stern wrote:
[...]
> What's the kernel bugzilla entry number?
Hi Alan,
sorry, forgot that, here it is the link:
https://bugzilla.kernel.org/show_bug.cgi?id=50381
bye,
--
piergiorgio
--
To unsubscribe from this list: send the line "unsubscribe li
Hi all,
I've a strange problem with the USB subsystem, under
kernel 3.6, this was not happening under 3.5.
The system is Fedora, so I'll use their kernel numbers,
and the related bug report is this:
https://bugzilla.redhat.com/show_bug.cgi?id=866166
I've some USB hubs cascaded in order to have 1
On Sun, Nov 04, 2012 at 03:07:35PM -0500, Alan Stern wrote:
[...]
> The first thing you should do is test a 3.6 kernel with
> CONFIG_USB_DEBUG enabled and post the dmesg log showing the problem.
> That will help indicate what is going wrong.
I guess this is a compile time option.
Is it any run-
On Sun, Nov 04, 2012 at 03:07:35PM -0500, Alan Stern wrote:
[...]
> The first thing you should do is test a 3.6 kernel with
> CONFIG_USB_DEBUG enabled and post the dmesg log showing the problem.
> That will help indicate what is going wrong.
>
> If that doesn't suggest a solution, the next thin
Hi all again,
I would like just to re-state the issue and try
to rationalize a possible debugging strategy.
So my questions would be:
1) Is there any possibility, with a Fedora kernel,
to activate some run-time debugging/verbosity
option for the USB/ehci/usb-storage subsystem in
order to try to
Hi all,
I followed this instructions: http://wiki.gentoo.org/wiki/Kernel_git-bisect
The result, unless I did something incorrect, is:
Bisecting: a merge base must be tested
[28a33cbc24e4256c143dce96c7d93bf423229f92] Linux 3.5
Bisecting: 5128 revisions left to test after this (roughly 13 steps)
[b
On Sat, Nov 17, 2012 at 10:24:19AM -0800, Greg KH wrote:
> On Sat, Nov 17, 2012 at 06:40:07PM +0100, Piergiorgio Sartor wrote:
> > Hi all,
> >
> > I followed this instructions: http://wiki.gentoo.org/wiki/Kernel_git-bisect
> > The result, unless I did something incorr
On Sat, Nov 17, 2012 at 01:06:42PM -0800, Greg KH wrote:
[...]
> Yes, but again, that has nothing to do with the USB subsystem at all, so
> I think you got a false-positive here somehow.
>
Thanks for the feedback, I did it again.
So, it seems I've no beginners luck, in fact it looks like I took a
On Sun, Nov 18, 2012 at 12:44:37PM -0500, Alan Stern wrote:
> On Sun, 18 Nov 2012, Piergiorgio Sartor wrote:
>
> > 32830f207691176234b4c4dd17f0d7ab6d87d94b is the first bad commit
> > commit 32830f207691176234b4c4dd17f0d7ab6d87d94b
> > Author: Alan Stern
> > Da
On Sun, Nov 18, 2012 at 12:44:37PM -0500, Alan Stern wrote:
> On Sun, 18 Nov 2012, Piergiorgio Sartor wrote:
>
> > 32830f207691176234b4c4dd17f0d7ab6d87d94b is the first bad commit
> > commit 32830f207691176234b4c4dd17f0d7ab6d87d94b
> > Author: Alan Stern
> > Da
Hi all,
bug 204095 from bugzilla.kernel.org was closed,
but apparently something is left unfixed.
Ref.: https://bugzilla.kernel.org/show_bug.cgi?id=204095
Below the two last entries I did about the topic:
--- --- ---
I've Fedora 30 and there was an update, from kernel 5.1.20
to 5.2.5, and now
On Tue, Aug 20, 2019 at 09:23:26AM +0200, Christoph Hellwig wrote:
> On Mon, Aug 19, 2019 at 10:14:25AM -0400, Alan Stern wrote:
> > Let's bring this to the attention of some more people.
> >
> > It looks like the bug that was supposed to be fixed by commit
> > d74ffae8b8dd ("usb-storage: Add a li
On Tue, Aug 20, 2019 at 06:37:22PM +0200, Piergiorgio Sartor wrote:
> On Tue, Aug 20, 2019 at 09:23:26AM +0200, Christoph Hellwig wrote:
> > On Mon, Aug 19, 2019 at 10:14:25AM -0400, Alan Stern wrote:
> > > Let's bring this to the attention of some more people.
> > &
32 matches
Mail list logo
