NetBSD-Bugs archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]

Re: kern/56209: erratic usb operation



The following reply was made to PR kern/56209; it has been noted by GNATS.

From: Joseph Sarkes <jsarkes%gmail.com@localhost>
To: Paul Goyette <paul%whooppee.com@localhost>
Cc: gnats-bugs%netbsd.org@localhost
Subject: Re: kern/56209: erratic usb operation
Date: Fri, 28 May 2021 10:24:28 -0400

 ok, just for my edification here, you seem to have run with the mouse
 timeouts with this pr, which was intended to be regarding the prologix
 usb-gpib device. the disconnects were related info that i thought
 might apply, and not my intended pr.
 
 do i need to create a different pr with just the prologix devce
 mentioned and nothing else? i've been searching for my old usr modem
 that had a usb connection along with serial to see if the help screen
 on that was also corrupted but can't locate it atm.
 
 i apologize if i offended the sensibilities of people here. i just
 managed to figure out it was netbsd and not the device that was
 causing my problem as linux works with the device and i never expected
 a problem with the netbsd serial stuff. I spent a couple of weeks
 fighting with the damn thing and then started looking at the
 improbable.
 
 the upshot is that the prologix usb-gpib device doesn't work somehow
 with netbsd. not sure if it is some flow control issue or corruption,
 and i personally don't have the ability any more to hold onto enough
 details to have a chance of fixing it. I generally fight with things
 until i get them working but established this was beyond my
 capabilities.
 
 I'd like to reiterate that i included the timeout info as amplifying
 details, as i considered that it was not an issue for others, but
 might help point in some sort of crack one might pry into. I never
 expected to have multiple whacks with a stick when sending the pr. My
 assumption was that the problem report would be appreciated as a
 pointer to something perhaps needing attention, and not as a reason to
 strike swiftly with a stick.
 
 feel free to delete this mail once it is absorbed. no need to perturb
 people perpetually with a bit of feedback.
 
 On 5/25/21, Paul Goyette <paul%whooppee.com@localhost> wrote:
 > On Tue, 25 May 2021, Martin Husemann wrote:
 >
 >> There is nothing wrong with the mice timeouts - the mice themselves do
 >> that. Typical fix:
 >>
 >>  - run X (so the X server opens the mouse device)
 >>  - run wsmoused (like: add wsmoused=YES to /etc/rc.conf)
 >
 > I can copnfirm that this fixes the problem - many of us have seen
 > and reported this before.
 >
 >> Please do not mix totaly unrelated issues in one PR.
 >
 > Also please try not to mischaracterise the problem.  It's not
 > really "erratic" - the detach/disconnect happens approximately
 > 62 seconds after the previous attach;  once disconnected, it
 > will re-attach in a couple of seconds.  The time intervals are
 > quite consistent.
 >
 >
 > +--------------------+--------------------------+-----------------------+
 > | Paul Goyette       | PGP Key fingerprint:     | E-mail addresses:     |
 > | (Retired)          | FA29 0E3B 35AF E8AE 6651 | paul%whooppee.com@localhost     |
 > | Software Developer | 0786 F758 55DE 53BA 7731 | pgoyette%netbsd.org@localhost   |
 > +--------------------+--------------------------+-----------------------+
 >
 



Home | Main Index | Thread Index | Old Index