to look for.
Alan Stern
Index: usb-2.6/drivers/usb/host/ohci-mem.c
===
--- usb-2.6.orig/drivers/usb/host/ohci-mem.c
+++ usb-2.6/drivers/usb/host/ohci-mem.c
@@ -98,17 +98,56 @@ td_alloc (struct ohci_hcd *hc, gfp_t mem
return td
then we'll know for certain. (Or maybe the presence of the
barrier() will cause the object code to change in a way that prevents
the error from occurring.)
Alan Stern
--
To unsubscribe from this list: send the line unsubscribe linux-media in
the body of a message to majord...@vger.kernel.org
More
an enhanced
version of the patch. It will provide more information and perhaps a
smoking gun.
Alan Stern
Index: usb-2.6/drivers/usb/host/ohci-hcd.c
===
--- usb-2.6.orig/drivers/usb/host/ohci-hcd.c
+++ usb-2.6/drivers/usb/host/ohci-hcd.c
printing the debug messages when an error is first
detected so maybe it won't overrun your log buffer.
Alan Stern
Index: usb-2.6/drivers/usb/host/ohci-hcd.c
===
--- usb-2.6.orig/drivers/usb/host/ohci-hcd.c
+++ usb-2.6/drivers/usb/host
, but including it anyway is
worthwhile.
Alan Stern
--
To unsubscribe from this list: send the line unsubscribe linux-media in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
On Wed, 2 Dec 2009, Sean wrote:
Is there anything I can do to help? This is a show stopping bug for me.
Here's a patch you can try. It will add a _lot_ of debugging
information to the system log. Maybe it will help pin down the source
of the problem.
Alan Stern
Index: 2.6.31/drivers/usb
On Sat, 24 Oct 2009, [UTF-8] Ozan ÃaÄlayan wrote:
Alan Stern wrote:
Okay, that proves this really is a timing bug in the hardware. But we
can't go around putting 2-millisecond delays in the kernel! Maybe you
can test to see if smaller delays will fix the problem. If 50
microseconds
this really is a timing bug in the hardware. But we
can't go around putting 2-millisecond delays in the kernel! Maybe you
can test to see if smaller delays will fix the problem. If 50
microseconds or less doesn't work then it will be necessary to add a
new timer to ehci-hcd.
Alan Stern
-sched.c: Add
udelay(2000);
just before the final return 0; line. Let's see if that prevents the
problem from occurring.
Alan Stern
--- usb-2.6.orig/drivers/usb/host/ehci-dbg.c
+++ usb-2.6/drivers/usb/host/ehci-dbg.c
@@ -591,18 +591,21 @@ static ssize_t fill_periodic_buffer(stru
On Thu, 22 Oct 2009, [UTF-8] Ozan ÃaÄlayan wrote:
Alan Stern wrote:
On Thu, 22 Oct 2009, [UTF-8] Ozan Ãâ¡aßlayan wrote:
Here's the outputs from /sys/kernel/debug/usb/ehci:
periodic:
size = 1024
1: qh1024-0001/f6ffe280 (h2 ep2 [1/0] q0 p8
with any earlier kernels?
A little more debugging information could confirm this. After the
error occurs, go into /sys/kernel/debug/usb/ehci/:00:1d.7 and post
a copy of the registers file. If there's anything of interest in the
other files, post them too.
Alan Stern
--
To unsubscribe from
why it shows up only occasionally. But if it isn't, I
have no idea what the underlying cause is or how to fix it.
Alan Stern
--
To unsubscribe from this list: send the line unsubscribe linux-media in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org
below might help. If it doesn't, send another dmesg log but this time
with CONFIG_USB_DEBUG enabled in the kernel.
Alan Stern
Index: usb-2.6/drivers/usb/host/ehci-q.c
===
--- usb-2.6.orig/drivers/usb/host/ehci-q.c
+++ usb-2.6
collect a
usbmon trace.
Alan Stern
--
To unsubscribe from this list: send the line unsubscribe linux-media in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
, the issue does not
occur here, so I'm at a loss for the moment. But I'll have to
tackle it somehow. Not sure how though. Any suggestions are welcome.
Try asking the people responsible for maintaining DMA support for help.
And David is very good about testing new patches.
Alan Stern
On Mon, 25 May 2009, David wrote:
David wrote:
Alan Stern wrote:
Okay, here's a patch for you to try. It refreshes the toggle setting
in a linked but otherwise idle QH when a new URB is queued.
Alan Stern
Index: usb-2.6/drivers/usb/host/ehci-q.c
over an ssh connection --
you end up dumping the packets containing the dump output!
But if not then this is a genuine bug and it should be reported
separately on the linux-usb mailing list.
Alan Stern
--
To unsubscribe from this list: send the line unsubscribe linux-media in
the body of a message
On Sun, 24 May 2009, David wrote:
Alan Stern wrote:
It's not obvious what could be causing this, so let's start out easy.
Try collecting two usbmon traces (instructions are in
Documentation/usb/usbmon.txt), showing what happens with and without
the reversion. Maybe some difference
On Sun, 24 May 2009, David wrote:
Alan Stern wrote:
But if not then this is a genuine bug and it should be reported
separately on the linux-usb mailing list.
Stranger and stranger. I started usbmon on the quad core and (at the
console) cat /sys/kernel/debug/usbmon/0u worked fine
. Maybe some difference will stick out.
Alan Stern
--
To unsubscribe from this list: send the line unsubscribe linux-media in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
happened on that boot and I haven't seen those ehci_hcd/khubd errors
again since.
I have no idea what caused that. Some brief glitch, apparently.
Okay, here's a diagnostic patch meant to apply on top of
gregkh-all-2.6.29-rc7. Let's see what it says...
Alan Stern
Index: usb-2.6/drivers/usb
before
the memory image was written out to the disk.
Is there some other method I missed of testing?
How about echo disk /sys/power/state with various settings in
/sys/power/disk?
Alan Stern
--
To unsubscribe from this list: send the line unsubscribe linux-media in
the body of a message
.
BTW, all those extra debugging messages in your log made it very
difficult to read, and they didn't help much in pinpointing the
problem. You should remove all of them before doing the next test.
Instead you could use usbmon to capture the USB traffic.
Alan Stern
--
To unsubscribe from
simply a matter of how you create your workqueue. In
the code you sent me, you call create_workqueue(). Instead, just call
create_singlethread_workqueue(). Or maybe even
create_freezeable_workqueue().
Alan Stern
--
To unsubscribe from this list: send the line unsubscribe linux-media in
the body
a mutex.
Alan Stern
--
To unsubscribe from this list: send the line unsubscribe linux-media in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
immediately. Then when gspca_stream_off() calls
destroy_urbs() again there would be no more work left to do.
Alan Stern
--
To unsubscribe from this list: send the line unsubscribe linux-media in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org
resources
immediately.
Alan Stern
--
To unsubscribe from this list: send the line unsubscribe linux-media in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
101 - 127 of 127 matches
Mail list logo
