On Saturday 21 May 2005 12:14 am, Glenn Maynard wrote:
> On Sat, May 21, 2005 at 12:07:15AM -0700, Pete Zaitcev wrote:
> > On Sat, 21 May 2005 02:08:47 -0400, Glenn Maynard <[EMAIL PROTECTED]> wrote:
> >
> > > [...] It's not a correct fix, but due to time constraints
> > > (and paranoia) I'm opti
On Sat, May 21, 2005 at 12:07:15AM -0700, Pete Zaitcev wrote:
> On Sat, 21 May 2005 02:08:47 -0400, Glenn Maynard <[EMAIL PROTECTED]> wrote:
>
> > [...] It's not a correct fix, but due to time constraints
> > (and paranoia) I'm opting for the simplest fix that works.
>
> > @@ -2791,6 +2791,7 @@
On Sat, 21 May 2005 02:08:47 -0400, Glenn Maynard <[EMAIL PROTECTED]> wrote:
> [...] It's not a correct fix, but due to time constraints
> (and paranoia) I'm opting for the simplest fix that works.
> @@ -2791,6 +2791,7 @@
> usb_unlock_device(hdev);
> usb_put_intf(intf
On Tue, May 17, 2005 at 03:45:40AM -0400, Glenn Maynard wrote:
> (Unfortunately, this is hard to test: sometimes we'll go a whole day without
> this happening, and the next day it'll happen every half hour. I wonder how
> I could simulate this ...)
Just to (hopefully) wrap this up:
I was finally
On Mon, May 02, 2005 at 10:24:08AM -0700, David Brownell wrote:
> > No it's not. When debouncing fails the hub driver turns off the
> > POST_STAT_C_CONNECTION feature and leaves the port disabled. There
> > shouldn't be any looping.
>
> Well, there _are_ such infinite-loop cases, and that trans
On Monday 02 May 2005 10:54 am, Alan Stern wrote:
> Admittedly, there _could_ be an infinite-loop type of behavior. If the
> connection kept getting made and broken, over and over, it would seem to
> khubd that someone was plugging and unplugging the device over and over.
> After debouncing fai
On Sun, 1 May 2005, David Brownell wrote:
> On Sunday 01 May 2005 1:43 pm, Glenn Maynard wrote:
> > We're hitting the "connect-debounce failed" message on a remote system,
> > in 2.6.12-rc3 (no changes).
>
> Which among other things is an "infinite loop during enumeration"
> problem.
No it's not
On Mon, 2 May 2005, David Brownell wrote:
> On Monday 02 May 2005 8:27 am, Alan Stern wrote:
> > On Sun, 1 May 2005, David Brownell wrote:
> >
> > > On Sunday 01 May 2005 1:43 pm, Glenn Maynard wrote:
> > > > We're hitting the "connect-debounce failed" message on a remote system,
> > > > in 2.6.1
On Monday 02 May 2005 8:27 am, Alan Stern wrote:
> On Sun, 1 May 2005, David Brownell wrote:
>
> > On Sunday 01 May 2005 1:43 pm, Glenn Maynard wrote:
> > > We're hitting the "connect-debounce failed" message on a remote system,
> > > in 2.6.12-rc3 (no changes).
> >
> > Which among other things i
On Mon, 2 May 2005, Glenn Maynard wrote:
> The site closed for the day, and I was able to poke at it more actively. I
> found a missing piece of the puzzle: if one of the lights is lit, the hub
> flakes out as in the previous logs, and it works fine if not lit. EMI issue,
> probably; it's a neon
On Sun, May 01, 2005 at 07:00:58PM -0700, David Brownell wrote:
> Sounds like that hub is making trouble. Does it work without the I/O
> board? How about on other hardware? There are some devices, including
> some hubs, that just don't work very well ... and hubs are often happier
> with power s
On Sunday 01 May 2005 1:43 pm, Glenn Maynard wrote:
> We're hitting the "connect-debounce failed" message on a remote system,
> in 2.6.12-rc3 (no changes).
Which among other things is an "infinite loop during enumeration"
problem. There are a few of those lurking still.
> There are two root hub
We're hitting the "connect-debounce failed" message on a remote system,
in 2.6.12-rc3 (no changes).
There are two root hubs. One has a simple USB I/O board attached, which
we access directly with usbfs. (It shows up as an HID, but hid.o is not
loaded.) The other has a bus-powered hub attached.
13 matches
Mail list logo
