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
On Sat, 26 Jan 2013, Piergiorgio Sartor wrote:
> 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
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 Fri, 25 Jan 2013, Piergiorgio Sartor wrote:
> 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.
Okay, good. I'll submit this for inclusion in the stable kernels.
> The only comment I've is tha
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 Tue, 22 Jan 2013, Piergiorgio Sartor wrote:
> 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.
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 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 earlier patch.
Alan Stern
Index: 3.7/drivers/usb/host/ehci-timer.c
=
On Fri, 18 Jan 2013, Piergiorgio Sartor wrote:
> I tried the patch below with kernel 3.7, I updated
> my local git copy to that version.
>
> I'm sorry to say it does not seem to fix the issue.
>
> Some explanation, I made three trials, with reboot
> inbetween, of course.
> The first one got the
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
On Mon, 14 Jan 2013, Piergiorgio Sartor wrote:
> > Okay, I figured out what the problem is. It really is a bug in
> > ehci-hcd; the driver doesn't do what the spec requires when unlinking
> > more than one QH at a time.
>
> Well, I'm happy to read this. Good that you find it!
>
> It puzzles m
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.
[...]
> > Next step?
>
> Okay, I figu
On Sun, 13 Jan 2013, Piergiorgio Sartor wrote:
> Hi Alan,
>
> Happy New Year!
I hope you had a good holiday break.
> I removed the previous short patch to ehci-q.c and applied
> this second one.
>
> After some extensive testing, I could not reproduce the
> issue and dmesg showed the ususl "asy
Hi Alan,
Happy New Year!
I removed the previous short patch to ehci-q.c and applied
this second one.
After some extensive testing, I could not reproduce the
issue and dmesg showed the ususl "async off" and "async on"
messages, the second as soon as I started to read the HDDs.
Performance wise,
On Tue, 18 Dec 2012, Piergiorgio Sartor wrote:
> Hi Alan,
>
> just one short question before holidays (and forgetting it...).
>
> Is this latest patch to be applied on top of all the others, or
> should I remove the previous one? Was same file, I think.
Remove the previous one and keep the othe
Hi Alan,
just one short question before holidays (and forgetting it...).
Is this latest patch to be applied on top of all the others, or
should I remove the previous one? Was same file, I think.
Thanks,
bye,
pg
On Mon, Dec 17, 2012 at 02:59:21PM -0500, Alan Stern wrote:
> On Mon, 17 Dec 2012,
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,
> but this is something I saw before (it happens ve
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,
but this is something I saw before (it happens very
seldom, maybe future debugging) and it was not really
locking
On Sun, 16 Dec 2012, Piergiorgio Sartor wrote:
> Hi Alan,
>
> I applied the modifications you suggested, this is the output:
>
> [ 110.922009] ehci_hcd :00:0b.1: async off
> [ 209.362134] ehci_hcd :00:0b.1: async on
> [ 241.794760] ehci_hcd :00:0b.1: alan start cur time 429490899
Hi Alan,
I applied the modifications you suggested, this is the output:
[ 110.922009] ehci_hcd :00:0b.1: async off
[ 209.362134] ehci_hcd :00:0b.1: async on
[ 241.794760] ehci_hcd :00:0b.1: alan start cur time 4294908992 last scan
4294878606
[ 241.794774] ehci_hcd :00:0b.1:
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 did not
> see any of the logs of this patch in the output, despite
> having seen the problem occuring (this time
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
> > > added to the schedule. The drive
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
> > added to the schedule. The driver could wait and add them after the
> > schedule was off. I didn't do
On Mon, 10 Dec 2012, Piergiorgio Sartor wrote:
> It might be useful.
> I tried quickly to put 5 instead of 20, but still
> the issue was difficult to reproduce (3.7.0-rc4+).
> It happened (again) only after I increased the CPU
> (or I/O) load by "make -j5" in "/usr/src/linux".
> And even not immed
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 Sun, 9 Dec 2012, Piergiorgio Sartor wrote:
> > Basically, this is a bug in nVidia's EHCI controller hardware. The
> > driver told the controller to turn off its async schedule, and 20 ms
> > later the schedule still was running. Although the EHCI specification
> > doesn't put any time limit o
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)
> > (prog-if 20 [EHCI])
> > Subsystem: ASUSTeK C
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)
> (prog-if 20 [EHCI])
> Subsystem: ASUSTeK Computer Inc. Device 81c0
> Flags: bus master, 66MHz, fast devsel, latency 0, IRQ
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?
> >
> > It's the latest from git?
>
> I think it should work with
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?
>
> It's the latest from git?
I think it should work with any fairly recent kernel. The patch was
written against linux-next from about six
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,
> >
> > I updated the bug repo
On Mon, 3 Dec 2012, Piergiorgio Sartor wrote:
> Hi Alan,
>
> I updated the bug report with dmesg dump.
>
> I hope this time it is correct...
Yes, it is. It shows a couple of strange things; I need more
information.
Below is a new test patch; try running the test with this patch in
place of
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 this point; maybe
> later on it will be
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 this point; maybe
later on it will be more useful.
Alan Stern
--
To unsubscribe from this list: send the line "
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
> > you provided (I hope I did it correctly).
>
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
> you provided (I hope I did it correctly).
This usbmon trace doesn't contain anything significantly different from
the p
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 files.
> >
> > Unfortunately, I cannot provide a "de
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 files.
>
> Unfortunately, I cannot provide a "deadline"
> (so to speak), I'm quite busy at the moment.
Don't worry about it; I'
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 give any details.
> All it sh
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 give any details.
All it showed was that at one point the computer stopped getting data
from the driv
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,
> Problem is, the file is 1.2MB, bizp2 reduces it to 200K.
> How do I pass it to you?
You could post it on a web site, or put it on pastebin.com. Or you
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:1:012:0 s 23 03 0004 0001 0
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:1:012:0 s 23 03 0004 0001 0
> 880130cd9000 816577053 C Co:1:012:0 -2 0
...
> 880026fb2780 8
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
> > Date: Wed Jul 11 11:22:53 2012 -0400
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
> > Date: Wed Jul 11 11:22:53 2012 -0400
On Sun, 18 Nov 2012, Piergiorgio Sartor wrote:
> 32830f207691176234b4c4dd17f0d7ab6d87d94b is the first bad commit
> commit 32830f207691176234b4c4dd17f0d7ab6d87d94b
> Author: Alan Stern
> Date: Wed Jul 11 11:22:53 2012 -0400
>
> USB: EHCI: use hrtimer for unlinking empty async QHs
>
>
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 Sat, Nov 17, 2012 at 08:19:34PM +0100, Piergiorgio Sartor wrote:
> 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_g
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 incorrect, is:
> >
> > Bisecting: a
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 incorrect, is:
>
> Bisecting: a merge base must be tested
> [28a33cbc24e4256c143dce96c7d93bf423229f92]
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 Wed, 14 Nov 2012, Piergiorgio Sartor wrote:
> 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
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
On Sun, 4 Nov 2012, Piergiorgio Sartor wrote:
> 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 wron
On Mon, Nov 5, 2012 at 4:17 AM, Piergiorgio Sartor
wrote:
>
> This seems a bit out of reach, for several reasons.
> I'll have to use a Fedora kernel, which might have its
> own patches and I suspect things will become complicated
> beyond my capability to manage them.
> I might try on a different
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
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, 4 Nov 2012, Piergiorgio Sartor wrote:
> 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_bu
58 matches
Mail list logo
