On 06/13/14 05:44, Thomas Mueller wrote:
Possibly increase the timing variables under:
sysctl hw.usb.timings
If they are not there, possibly the USB_DEBUG option has been removed from the
kernel config. Can you check that?
--HPS
What are the units for sysctl.hw.usb.timings? Seconds? Mi
> Possibly increase the timing variables under:
> sysctl hw.usb.timings
> If they are not there, possibly the USB_DEBUG option has been removed from the
> kernel config. Can you check that?
--HPS
What are the units for sysctl.hw.usb.timings? Seconds? Milliseconds?
I ran sysctl hw.usb.timing
Hans Petter Selasky wrote this message on Thu, Jun 12, 2014 at 21:06 +0200:
> On 06/12/14 20:52, John-Mark Gurney wrote:
> >So, I'm trying to get USB functional on an old i386 machine that only
> >supports USB 1.0... It works, but when I try to plug in a hub I get
> >the following:
> >uhub0: 2 por
On 06/12/14 20:52, John-Mark Gurney wrote:
So, I'm trying to get USB functional on an old i386 machine that only
supports USB 1.0... It works, but when I try to plug in a hub I get
the following:
uhub0: 2 ports with 2 removable, self powered
Root mount waiting for: usbus0
usb_alloc_device: set a
So, I'm trying to get USB functional on an old i386 machine that only
supports USB 1.0... It works, but when I try to plug in a hub I get
the following:
uhub0: 2 ports with 2 removable, self powered
Root mount waiting for: usbus0
usb_alloc_device: set address 2 failed (USB_ERR_IOERROR, ignored)
Ro
on 21/12/2011 18:38 Hans Petter Selasky said the following:
> On Wednesday 21 December 2011 12:29:49 Andriy Gapon wrote:
>> on 20/12/2011 14:25 Andriy Gapon said the following:
>>> I just wanted to draw your attention to the fact that obtaining any locks
>>> in the kdb context (or USB polling code
On Wednesday 21 December 2011 12:29:49 Andriy Gapon wrote:
> on 20/12/2011 14:25 Andriy Gapon said the following:
> > I just wanted to draw your attention to the fact that obtaining any locks
> > in the kdb context (or USB polling code in general, even) is not a good
> > idea. Chances of getting in
on 20/12/2011 14:25 Andriy Gapon said the following:
> I just wanted to draw your attention to the fact that obtaining any locks in
> the
> kdb context (or USB polling code in general, even) is not a good idea.
> Chances of getting into trouble on those locks are probably quite moderate or
> even
Now the juicy stuff :)
on 19/12/2011 16:30 Hans Petter Selasky said the following:
>> 3. Looking at usbd_transfer_poll I see that it touches a lot of locks,
>> including taking the bus lock. As we've discussed before, this is not safe
>> in a particular context where the polling is supposed to
on 19/12/2011 17:11 Hans Petter Selasky said the following:
> I will fix that. I see a missing wait there. Can I assume that we are allowed
> to sleep from device_shutdown() and that system timers still work?
I don't see any reason why either of these should be not true.
Oh, and I see that you've
On Monday 19 December 2011 16:06:13 Andriy Gapon wrote:
> First replying just to couple of points where there seems to be a
> misunderstanding.
>
> on 19/12/2011 16:30 Hans Petter Selasky said the following:
> >> 2. Somewhat related to the above. I think that because the USB
> >> subsystem imple
First replying just to couple of points where there seems to be a
misunderstanding.
on 19/12/2011 16:30 Hans Petter Selasky said the following:
>> 2. Somewhat related to the above. I think that because the USB subsystem
>> implements the shutdown method and detaches all its drivers, then the u
On Monday 19 December 2011 13:16:17 Andriy Gapon wrote:
> Hans Petter,
>
> I think that I see some issues in the USB code that could cause problems in
> some edge cases.
> From easiest to hardest:
>
Hi,
> 1. I think that currently there is a LOR in usb_bus_shutdown. I think
> that the followi
Hans Petter,
I think that I see some issues in the USB code that could cause problems in some
edge cases.
>From easiest to hardest:
1. I think that currently there is a LOR in usb_bus_shutdown. I think that the
following patch should fix it:
On Fri, Dec 24, 2010 at 1:56 AM, Hans Petter Selasky wrote:
> On Friday 24 December 2010 02:27:55 Justin V. wrote:
>> On Thu, 23 Dec 2010, Hans Petter Selasky wrote:
>>
>> Im not familiar with patching I guess.. any tips?
>
> Then try to copy usb_request.c and usb_request.h
Or the OP could ju
On Friday 24 December 2010 02:27:55 Justin V. wrote:
> On Thu, 23 Dec 2010, Hans Petter Selasky wrote:
>
> Im not familiar with patching I guess.. any tips?
Then try to copy usb_request.c and usb_request.h
--HPS
___
freebsd-current@freebsd.org mailing
On Thu, 23 Dec 2010, Hans Petter Selasky wrote:
On Thursday 23 December 2010 21:59:13 Justin V. wrote:
On Thu, 23 Dec 2010, Hans Petter Selasky wrote:
On Wednesday 22 December 2010 21:31:19 Kim Culhan wrote:
On Wed, December 22, 2010 3:00 am, Hans Petter Selasky wrote:
On Wednesday 22 Dece
On Thursday 23 December 2010 21:59:13 Justin V. wrote:
> On Thu, 23 Dec 2010, Hans Petter Selasky wrote:
> > On Wednesday 22 December 2010 21:31:19 Kim Culhan wrote:
> >> On Wed, December 22, 2010 3:00 am, Hans Petter Selasky wrote:
> >>> On Wednesday 22 December 2010 07:15:53 justin v wrote:
> >>>
On Thu, 23 Dec 2010, Hans Petter Selasky wrote:
On Wednesday 22 December 2010 21:31:19 Kim Culhan wrote:
On Wed, December 22, 2010 3:00 am, Hans Petter Selasky wrote:
On Wednesday 22 December 2010 07:15:53 justin v wrote:
Hi,
Any advice on how to deal with this USB trouble.. ?
This is sc
On Wed, Dec 22, 2010 at 6:11 PM, Hans Petter Selasky wrote:
> On Wednesday 22 December 2010 21:31:19 Kim Culhan wrote:
> > On Wed, December 22, 2010 3:00 am, Hans Petter Selasky wrote:
> > > On Wednesday 22 December 2010 07:15:53 justin v wrote:
> > >> Hi,
> > >>
> > >> Any advice on how to deal
On Wednesday 22 December 2010 21:31:19 Kim Culhan wrote:
> On Wed, December 22, 2010 3:00 am, Hans Petter Selasky wrote:
> > On Wednesday 22 December 2010 07:15:53 justin v wrote:
> >> Hi,
> >>
> >> Any advice on how to deal with this USB trouble.. ?
> >>
> >>
> >> This is scrolling through mess
On Wed, December 22, 2010 3:00 am, Hans Petter Selasky wrote:
> On Wednesday 22 December 2010 07:15:53 justin v wrote:
>> Hi,
>>
>> Any advice on how to deal with this USB trouble.. ?
>>
>>
>> This is scrolling through messages.. and when i plug in my USB device,
>> ANY, it is not recognized, when
On Wed, 22 Dec 2010, Hans Petter Selasky wrote:
On Wednesday 22 December 2010 07:15:53 justin v wrote:
Hi,
Any advice on how to deal with this USB trouble.. ?
This is scrolling through messages.. and when i plug in my USB device,
ANY, it is not recognized, when normally it is...
What v
On Wednesday 22 December 2010 07:15:53 justin v wrote:
> Hi,
>
> Any advice on how to deal with this USB trouble.. ?
>
>
> This is scrolling through messages.. and when i plug in my USB device,
> ANY, it is not recognized, when normally it is...
>
What version of FreeBSD are you using?
Have
Hi,
Any advice on how to deal with this USB trouble.. ?
This is scrolling through messages.. and when i plug in my USB device,
ANY, it is not recognized, when normally it is...
exit
[...@yeaguy ~]$ tail -f /var/log/messages
Dec 21 22:13:11 yeaguy kernel: uhub_reattach_port: port 3 reset
On Thu, Dec 12, 2002 at 07:27:07PM -0500, Brian F. Feldman wrote:
> Josef Karthauser <[EMAIL PROTECTED]> wrote:
> > Hi all,
> >
> > If you're an ohci user can you please test this patch out for inclusion
> > in 5.0. I need to know that it doesn't break anything - the reports are
> > that it fixes
Josef Karthauser <[EMAIL PROTECTED]> wrote:
> Hi all,
>
> If you're an ohci user can you please test this patch out for inclusion
> in 5.0. I need to know that it doesn't break anything - the reports are
> that it fixes broken ohci :).
For what it's worth, it doesn't fix the umass(4) crashing is
On Thu, 5 Dec 2002, Josef Karthauser wrote:
>
> If you're an ohci user can you please test this patch out for inclusion
> in 5.0. I need to know that it doesn't break anything - the reports are
> that it fixes broken ohci :).
I've been running it since you posted the patch a couple of days ago.
Hi all,
If you're an ohci user can you please test this patch out for inclusion
in 5.0. I need to know that it doesn't break anything - the reports are
that it fixes broken ohci :).
Joe
--
Josef Karthauser ([EMAIL PROTECTED]) http://www.josef-k.net/
FreeBSD (cvs meister, admin and
On Fri, 2002-12-06 at 10:04, Darryl Okahata wrote:
> > I have motherboards where this fix doesn't work :(
>
> You have tried -current, right? (I assume that you have, but I
> just want to make sure.) Cliff mentioned that -current works for him,
> but 4.7 doesn't.
Hmm, no.. It wasn't really
"Daniel O'Connor" <[EMAIL PROTECTED]> wrote:
> > Many (most? all?) KT133A-based motherboards have a known issue with
> > the PCI bus that often results in an IDE transfer problem. However,
> > this was fixed (IIRC) in FreeBSD around the 4.5/4.6 timeframe (maybe
> > earlier). [ Hmmm. You're
On Fri, 2002-12-06 at 02:48, Darryl Okahata wrote:
> > a rock under 5.0-DP2, which is why I'm sticking with it despite other
> > potential bugs. I can burn CDs now!
>
> Many (most? all?) KT133A-based motherboards have a known issue with
> the PCI bus that often results in an IDE transfer pr
"Cliff L. Biffle" <[EMAIL PROTECTED]> wrote:
> Could be. The ATA controller was also flaking out under 4.7, but is solid as
> a rock under 5.0-DP2, which is why I'm sticking with it despite other
> potential bugs. I can burn CDs now!
Many (most? all?) KT133A-based motherboards have a know
On Wednesday 04 December 2002 05:40 pm, Josef Karthauser wrote:
> Is it ohci? If so can you try this patch?
>
> Joe
Hey Joe -- fancy meeting you here. :-)
Nope, the KT133 has two UHCI controllers.
What I'm going to do next (which I should have done before) is try the
following variables:
1. Do
On Wednesday 04 December 2002 05:11 pm, Darryl Okahata wrote:
> 1. IIRC, USB ports on KT133A motherboards were buggy (???).
Could be. The ATA controller was also flaking out under 4.7, but is solid as
a rock under 5.0-DP2, which is why I'm sticking with it despite other
potential bugs. I can b
On Wed, Dec 04, 2002 at 04:00:15PM -0700, Cliff L. Biffle wrote:
> Hi all.
> I'm running 5.0-DP2 on a motherboard with the Apollo KT133A chipset. (I
> believe it's an ASUS, but it doesn't seem to be labelled.) The USB
> controller (described by dmesg as a VIA 83C572) periodically blows its brai
"Cliff L. Biffle" <[EMAIL PROTECTED]> wrote:
> More specifically, all USB devices lose power. The device nodes stay in /dev
> and there are no notices to dmesg about the loss until I unplug and replug
> them, at which time it says 'port error: restarting port N' where N is
> generally 0, depend
Hi all.
I'm running 5.0-DP2 on a motherboard with the Apollo KT133A chipset. (I
believe it's an ASUS, but it doesn't seem to be labelled.) The USB
controller (described by dmesg as a VIA 83C572) periodically blows its brains
out.
More specifically, all USB devices lose power. The device node
38 matches
Mail list logo
