On Wed, 9 Nov 2016 sonofa...@openmailbox.org wrote:
> Back to our subject, I think there is something we can do for intel dual
> EHCI chipsets so that it is easier to debug similar issues in the
> future. PCI dumps from the machine that had the issue are needed.
I don't see how PCI dumps would
Why didn't you say so (given that you were replying to a message that I
sent)?
Because I thought it would go to the correct existing subject on the
first place.
I don't know. What new subject are you referring to?
Some days ago, the first two messages I have sent were not linked there:
On Tue, 8 Nov 2016 sonofa...@openmailbox.org wrote:
>
> > I never had them in the first place.
> Yes I know, the question was asked to the thread creator!
Why didn't you say so (given that you were replying to a message that I
sent)?
> Why did the messages move to a new subject and were not
I never had them in the first place.
Yes I know, the question was asked to the thread creator!
Why did the messages move to a new subject and were not added to the
original subject?
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to
On Thu, 3 Nov 2016 sonofa...@openmailbox.org wrote:
> Hello guys! Did you have any progress on this?
In a word: No.
> Do you still have the
> affected machine and devices?
I never had them in the first place.
Alan Stern
--
To unsubscribe from this list: send the line "unsubscribe linux-usb"
Second try...
Hello guys! Did you have any progress on this? Do you still have the
affected machine and devices?
--
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
Hello guys! Did you have any progress on this? Do you still have the
affected machine and devices?
--
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
On Sun, 12 Jun 2016, Sean M. Pappalardo wrote:
>
>
> On 06/12/2016 06:05 PM, Alan Stern wrote:
> > Okay, thanks. I just wanted to be sure the patch was behaving as
> > intended. It was, but since it didn't fix your problem the whole
> > thing's a moot point.
>
> Anything else you'd like me
On 06/12/2016 06:05 PM, Alan Stern wrote:
> Okay, thanks. I just wanted to be sure the patch was behaving as
> intended. It was, but since it didn't fix your problem the whole
> thing's a moot point.
Anything else you'd like me to try or gather if you're interested in
fixing the underlying
On Sun, 12 Jun 2016, Sean M. Pappalardo wrote:
> Hello again.
>
> On 06/12/2016 07:57 AM, Alan Stern wrote:
> > Would you mind posting the contents of
> > /sys/kernel/debug/usb/ehci/:00:1d.0/periodic, for the patched
> > kernel, while the test is running?
>
> Sure, attached. Sorry I
Hello again.
On 06/12/2016 07:57 AM, Alan Stern wrote:
> Would you mind posting the contents of
> /sys/kernel/debug/usb/ehci/:00:1d.0/periodic, for the patched
> kernel, while the test is running?
Sure, attached. Sorry I didn't think to gather that before.
Sincerely,
Sean M. Pappalardo
On Sat, 11 Jun 2016, Sean M. Pappalardo wrote:
>
>
> On 06/10/2016 02:18 PM, Alan Stern wrote:
> > Actually, after reviewing the data files you sent I did have a thought.
> > Can you try out the patch below and see if it makes any difference?
>
> It did not, sorry.
Would you mind posting
On 06/10/2016 02:18 PM, Alan Stern wrote:
> Actually, after reviewing the data files you sent I did have a thought.
> Can you try out the patch below and see if it makes any difference?
It did not, sorry.
Sincerely,
Sean M. Pappalardo
smime.p7s
Description: S/MIME Cryptographic Signature
On Fri, 10 Jun 2016, Alan Stern wrote:
> On Fri, 10 Jun 2016, Sean M. Pappalardo wrote:
>
> >
> >
> > On 06/10/2016 11:06 AM, Alan Stern wrote:
> > > Have you tried plugging the audio
> > > devices into a USB-2 hub and plugging the hub into bus 2?
> >
> > That works!! (I forgot, my monitor
On Fri, 10 Jun 2016, Sean M. Pappalardo wrote:
>
>
> On 06/10/2016 11:06 AM, Alan Stern wrote:
> > Have you tried plugging the audio
> > devices into a USB-2 hub and plugging the hub into bus 2?
>
> That works!! (I forgot, my monitor has a built-in 2-port USB2.0 hub.)
Great!
> So what's
On 06/10/2016 11:06 AM, Alan Stern wrote:
> Have you tried plugging the audio
> devices into a USB-2 hub and plugging the hub into bus 2?
That works!! (I forgot, my monitor has a built-in 2-port USB2.0 hub.)
So what's going on here? How does adding another hub layer help??
Sincerely,
Sean M.
On 06/10/2016 11:06 AM, Alan Stern wrote:
> I suppose it might have something to do with the fact that the docking
> station contains its own hub. Have you tried plugging the audio
> devices into a USB-2 hub and plugging the hub into bus 2?
No, but I can go buy one and try that.
> That sort
On Fri, 10 Jun 2016, Sean M. Pappalardo wrote:
> Hello.
>
> I have a longstanding issue with multiple chatty USB devices on USB bus
> 02 acting erratic when activated simultaneously. As soon as the second
> device is closed, the first continues communication normally. The
> problem does NOT
Hello.
I have a longstanding issue with multiple chatty USB devices on USB bus
02 acting erratic when activated simultaneously. As soon as the second
device is closed, the first continues communication normally. The
problem does NOT occur on Bus 01 (which has many other devices attached
as well.)
19 matches
Mail list logo
