From hselasky at c2i.net Sun Feb 1 02:21:23 2009 From: hselasky at c2i.net (Hans Petter Selasky) Date: Sun Feb 1 02:21:30 2009 Subject: USB2 patches In-Reply-To: <20090131231957.GB31825@citylink.fud.org.nz> References: <20090131231957.GB31825@citylink.fud.org.nz> Message-ID: <200902011123.47690.hselasky@c2i.net> Hi Andrew, First of all thanks for helping out. I will spend some time now to go through your changes. One thing about the taskqueue. How does it work? I mean, if multiple events gets queued on the same handler, how will the events get executed? In parallell, in serial. I never fully understood that. --HPS On Sunday 01 February 2009, Andrew Thompson wrote: > Hi, > > > I have several patches in my svn user branch that I would like to see > committed to HEAD. Some of these change the usb2 core code so I am > interested in feedback or shootdowns. I am right behind the change to > USB2 and this is an effort to help. > > The patch can be found here, > http://people.freebsd.org/~thompsa/usb_head1.diff > 73 files changed, 9229 insertions(+), 13261 deletions(-) > > but its rather large so it may be easier to look at the various changes > via the svn web interface. > > http://svn.freebsd.org/viewvc/base/user/thompsa/usb/ > > > r187750 > http://svn.freebsd.org/viewvc/base?view=revision&revision=187750 > > Change over to using taskqueue(9) instead of hand rolled threads and > the config_td system. This removes the config_td code and makes the > API much simpler to use. > > r187751, r187752, r187753, r187754, r187755, r187756 > http://svn.freebsd.org/viewvc/base?view=revision&revision=187751 > > Change over to usb2_proc w/ taskqueues for the usb2/ethernet, > usb2/serial and usb2/wlan code. > > r187965 > http://svn.freebsd.org/viewvc/base?view=revision&revision=187965 > > Move most of the ifnet logic into the usb2_ethernet module, this > includes, - make all usb ethernet interfaces named ue%d > - handle all threading in usb2_ethernet > - provide default ioctl handler > - handle mbuf rx > - provide locked callbacks for init,start,stop,etc > > The drivers are not much more than data pushers now. > > > regards, > Andrew From hselasky at c2i.net Sun Feb 1 03:17:55 2009 From: hselasky at c2i.net (Hans Petter Selasky) Date: Sun Feb 1 03:18:02 2009 Subject: USB2 patches In-Reply-To: <20090201030628.GE65558@elvis.mu.org> References: <20090131231957.GB31825@citylink.fud.org.nz> <20090201030628.GE65558@elvis.mu.org> Message-ID: <200902011220.18745.hselasky@c2i.net> Hi Andrew, We need to go through your patches together, to work out some issues. 1) A nit. - if (usb2_proc_setup(&ssc->sc_config_td, p_mtx, USB_PRI_MED)) { - usb2_com_units_free(root_unit, sub_units); - return (ENOMEM); - } + + error = usb2_proc_create(&ssc->sc_tq, USB_PRI_MED, "ucom"); + if (error) < missing "usb2_com_units_free()" > + return (error); + 2) Please explain why you think that "usb2_proc_is_gone()" can be removed. - if (usb2_proc_is_gone(&ssc->sc_config_td)) { - DPRINTF("proc is gone\n"); - return; /* nothing to do */ - } If the taskqueue system does not provide a teardown mechanism so that we inside the callback can know if the taskqueue is being drained, then the taskqueue cannot replace the original "usb2_proc_xxx()" ! Maybe this means we need to extend the taskqueue system? 3) In general avoid more than a few synchronous USB transfer inside attach/detach. Always defer! Else there are corner cases where the device can hang waiting for the transfer timeout 1-5 seconds for every USB transfer, and that is unacceptable. With regard to the ethernet/wlan drivers, it is Ok to create the "if" instance in attach, but not to start programming the chip. This needs to be synchronised otherwise. I suggets you make a task called: zyd_first_time_configure() and kick this task before allocating ifnet instances. Then when everything is ready you queue another task to set the LINK flag, so that we don't start transmitting data during early chip configuration! In case of failure you just drain the taskqueue. 4) int onoff = USB_TASK_ARG(task); This won't work! You need to be able to handle N-phase here, where N goes to +infinity! If the DTR pin was toggled we should also see a toggle in the programming of the DTR pin, not just re-program the last state! If there is a USB_TASK_ARG() it must be constant and that is where I start seeing problems, or features missing in the taskqueue system. It is also very important that you somehow freeze the configuration at the moment a command is issued. For example in the WLAN drivers. If the command is queued when the channel is 5 then we should program channel 5 and not fetch the latest channel value from the softc! IMPORTANT! I'm not saying USB cannot use the taskqueue, but we have special requirements which I cannot see that the taskqueue is a full drop in replacement for! 5) Many of your other changes are good! --HPS On Sunday 01 February 2009, Alfred Perlstein wrote: > I'll defer to Hans if he feels confident or not about this. > > For what it's worth, we're about to switch GENERIC to use > usb4bsd. > > -Alfred > > * Andrew Thompson [090131 15:20] wrote: > > Hi, > > > > > > I have several patches in my svn user branch that I would like to see > > committed to HEAD. Some of these change the usb2 core code so I am > > interested in feedback or shootdowns. I am right behind the change to > > USB2 and this is an effort to help. > > > > The patch can be found here, > > http://people.freebsd.org/~thompsa/usb_head1.diff > > 73 files changed, 9229 insertions(+), 13261 deletions(-) > > > > but its rather large so it may be easier to look at the various changes > > via the svn web interface. > > > > http://svn.freebsd.org/viewvc/base/user/thompsa/usb/ > > > > > > r187750 > > http://svn.freebsd.org/viewvc/base?view=revision&revision=187750 > > > > Change over to using taskqueue(9) instead of hand rolled threads and > > the config_td system. This removes the config_td code and makes the > > API much simpler to use. > > > > r187751, r187752, r187753, r187754, r187755, r187756 > > http://svn.freebsd.org/viewvc/base?view=revision&revision=187751 > > > > Change over to usb2_proc w/ taskqueues for the usb2/ethernet, > > usb2/serial and usb2/wlan code. > > > > r187965 > > http://svn.freebsd.org/viewvc/base?view=revision&revision=187965 > > > > Move most of the ifnet logic into the usb2_ethernet module, this > > includes, - make all usb ethernet interfaces named ue%d > > - handle all threading in usb2_ethernet > > - provide default ioctl handler > > - handle mbuf rx > > - provide locked callbacks for init,start,stop,etc > > > > The drivers are not much more than data pushers now. > > > > > > regards, > > Andrew From Thomas.Sparrevohn at btinternet.com Sun Feb 1 06:43:56 2009 From: Thomas.Sparrevohn at btinternet.com (Thomas Sparrevohn) Date: Sun Feb 1 06:44:02 2009 Subject: USB2 patches In-Reply-To: <20090201030628.GE65558@elvis.mu.org> References: <20090131231957.GB31825@citylink.fud.org.nz> <20090201030628.GE65558@elvis.mu.org> Message-ID: <009401c9847b$81b38700$851a9500$@Sparrevohn@btinternet.com> Before we switch GENERIC - would it be possibly to have the bus dma issue committed as well? Without the patch manually added none of my umass devices work under amd64 -----Original Message----- From: owner-freebsd-usb@freebsd.org [mailto:owner-freebsd-usb@freebsd.org] On Behalf Of Alfred Perlstein Sent: 01 February 2009 03:06 To: Andrew Thompson Cc: freebsd-usb@freebsd.org Subject: Re: USB2 patches I'll defer to Hans if he feels confident or not about this. For what it's worth, we're about to switch GENERIC to use usb4bsd. -Alfred * Andrew Thompson [090131 15:20] wrote: > Hi, > > > I have several patches in my svn user branch that I would like to see > committed to HEAD. Some of these change the usb2 core code so I am > interested in feedback or shootdowns. I am right behind the change to > USB2 and this is an effort to help. > > The patch can be found here, > http://people.freebsd.org/~thompsa/usb_head1.diff > 73 files changed, 9229 insertions(+), 13261 deletions(-) > > but its rather large so it may be easier to look at the various changes > via the svn web interface. > > http://svn.freebsd.org/viewvc/base/user/thompsa/usb/ > > > r187750 > http://svn.freebsd.org/viewvc/base?view=revision&revision=187750 > > Change over to using taskqueue(9) instead of hand rolled threads and > the config_td system. This removes the config_td code and makes the > API much simpler to use. > > r187751, r187752, r187753, r187754, r187755, r187756 > http://svn.freebsd.org/viewvc/base?view=revision&revision=187751 > > Change over to usb2_proc w/ taskqueues for the usb2/ethernet, > usb2/serial and usb2/wlan code. > > r187965 > http://svn.freebsd.org/viewvc/base?view=revision&revision=187965 > > Move most of the ifnet logic into the usb2_ethernet module, this includes, > - make all usb ethernet interfaces named ue%d > - handle all threading in usb2_ethernet > - provide default ioctl handler > - handle mbuf rx > - provide locked callbacks for init,start,stop,etc > > The drivers are not much more than data pushers now. > > > regards, > Andrew -- - Alfred Perlstein _______________________________________________ freebsd-usb@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-usb To unsubscribe, send any mail to "freebsd-usb-unsubscribe@freebsd.org" From imp at bsdimp.com Sun Feb 1 09:09:09 2009 From: imp at bsdimp.com (M. Warner Losh) Date: Sun Feb 1 09:09:15 2009 Subject: USB2 patches In-Reply-To: <200902011123.47690.hselasky@c2i.net> References: <20090131231957.GB31825@citylink.fud.org.nz> <200902011123.47690.hselasky@c2i.net> Message-ID: <20090201.100736.-403077701.imp@bsdimp.com> In message: <200902011123.47690.hselasky@c2i.net> Hans Petter Selasky writes: : Hi Andrew, : : First of all thanks for helping out. I will spend some time now to go through : your changes. : : One thing about the taskqueue. How does it work? I mean, if multiple events : gets queued on the same handler, how will the events get executed? In : parallell, in serial. I never fully understood that. Serially. If they are the same task that's queued multiple times, you get a count of how many times it was queued to do something useful with. Warner : --HPS : : On Sunday 01 February 2009, Andrew Thompson wrote: : > Hi, : > : > : > I have several patches in my svn user branch that I would like to see : > committed to HEAD. Some of these change the usb2 core code so I am : > interested in feedback or shootdowns. I am right behind the change to : > USB2 and this is an effort to help. : > : > The patch can be found here, : > http://people.freebsd.org/~thompsa/usb_head1.diff : > 73 files changed, 9229 insertions(+), 13261 deletions(-) : > : > but its rather large so it may be easier to look at the various changes : > via the svn web interface. : > : > http://svn.freebsd.org/viewvc/base/user/thompsa/usb/ : > : > : > r187750 : > http://svn.freebsd.org/viewvc/base?view=revision&revision=187750 : > : > Change over to using taskqueue(9) instead of hand rolled threads and : > the config_td system. This removes the config_td code and makes the : > API much simpler to use. : > : > r187751, r187752, r187753, r187754, r187755, r187756 : > http://svn.freebsd.org/viewvc/base?view=revision&revision=187751 : > : > Change over to usb2_proc w/ taskqueues for the usb2/ethernet, : > usb2/serial and usb2/wlan code. : > : > r187965 : > http://svn.freebsd.org/viewvc/base?view=revision&revision=187965 : > : > Move most of the ifnet logic into the usb2_ethernet module, this : > includes, - make all usb ethernet interfaces named ue%d : > - handle all threading in usb2_ethernet : > - provide default ioctl handler : > - handle mbuf rx : > - provide locked callbacks for init,start,stop,etc : > : > The drivers are not much more than data pushers now. : > : > : > regards, : > Andrew : : : _______________________________________________ : freebsd-usb@freebsd.org mailing list : http://lists.freebsd.org/mailman/listinfo/freebsd-usb : To unsubscribe, send any mail to "freebsd-usb-unsubscribe@freebsd.org" : : From thompsa at FreeBSD.org Sun Feb 1 09:50:27 2009 From: thompsa at FreeBSD.org (Andrew Thompson) Date: Sun Feb 1 09:50:42 2009 Subject: USB2 patches In-Reply-To: <200902011220.18745.hselasky@c2i.net> References: <20090131231957.GB31825@citylink.fud.org.nz> <20090201030628.GE65558@elvis.mu.org> <200902011220.18745.hselasky@c2i.net> Message-ID: <20090201175021.GA32503@citylink.fud.org.nz> On Sun, Feb 01, 2009 at 12:20:17PM +0100, Hans Petter Selasky wrote: > Hi Andrew, > > We need to go through your patches together, to work out some issues. > > 1) A nit. > > - if (usb2_proc_setup(&ssc->sc_config_td, p_mtx, USB_PRI_MED)) { > - usb2_com_units_free(root_unit, sub_units); > - return (ENOMEM); > - } > + > + error = usb2_proc_create(&ssc->sc_tq, USB_PRI_MED, "ucom"); > + if (error) > > < missing "usb2_com_units_free()" > thanks. > + return (error); > + > > 2) Please explain why you think that "usb2_proc_is_gone()" can be removed. > > - if (usb2_proc_is_gone(&ssc->sc_config_td)) { > - DPRINTF("proc is gone\n"); > - return; /* nothing to do */ > - } > > If the taskqueue system does not provide a teardown mechanism so that we > inside the callback can know if the taskqueue is being drained, then the > taskqueue cannot replace the original "usb2_proc_xxx()" ! Maybe this means we > need to extend the taskqueue system? Possibly. Taskqueues will always complete the function callbacks before freeing so you dont need to worry about resources disappearing under you. The one reason would be to bail out of a long running task but, - Are there any tasks that actually run a long time? - If not, its easier just to wait on the drain > 3) > > In general avoid more than a few synchronous USB transfer inside > attach/detach. Always defer! Else there are corner cases where the device can > hang waiting for the transfer timeout 1-5 seconds for every USB transfer, and > that is unacceptable. I disagree. It hugely simplifies drivers to know all the resources are allocated after attach, you dont need to check for null pointers throughout the code. If programming commands fail/timeout in the attach routine then the driver needs to check this and abort the attach. You will wait one or two timeouts max. > > 4) > > int onoff = USB_TASK_ARG(task); > > This won't work! You need to be able to handle N-phase here, where N goes to > +infinity! If the DTR pin was toggled we should also see a toggle in the > programming of the DTR pin, not just re-program the last state! If there is a > USB_TASK_ARG() it must be constant and that is where I start seeing problems, > or features missing in the taskqueue system. > > It is also very important that you somehow freeze the configuration at the > moment a command is issued. For example in the WLAN drivers. If the command > is queued when the channel is 5 then we should program channel 5 and not > fetch the latest channel value from the softc! IMPORTANT! This isnt correct. Take your example of WLAN drivers, the net80211 layer will use ic_curchan for its logic so the driver needs to program the chip to this value at all times. You can _not_ queue channel changes as these will be out of sync. Tasks are very short lived and program the chipset to the current state where it otherwise could not have been done due to thread sleeping. Also, net80211 will soon have its own thread so you can do things like state/channel changes directly but in a sleepable context. > 5) Many of your other changes are good! Thanks! Andrew From hselasky at c2i.net Sun Feb 1 10:19:53 2009 From: hselasky at c2i.net (Hans Petter Selasky) Date: Sun Feb 1 10:20:01 2009 Subject: USB2 patches In-Reply-To: <20090201175021.GA32503@citylink.fud.org.nz> References: <20090131231957.GB31825@citylink.fud.org.nz> <200902011220.18745.hselasky@c2i.net> <20090201175021.GA32503@citylink.fud.org.nz> Message-ID: <200902011922.16810.hselasky@c2i.net> Hi Andrew, On Sunday 01 February 2009, Andrew Thompson wrote: > > 2) Please explain why you think that "usb2_proc_is_gone()" can be > > removed. > > > > - if (usb2_proc_is_gone(&ssc->sc_config_td)) { > > - DPRINTF("proc is gone\n"); > > - return; /* nothing to do */ > > - } > > > > If the taskqueue system does not provide a teardown mechanism so that we > > inside the callback can know if the taskqueue is being drained, then the > > taskqueue cannot replace the original "usb2_proc_xxx()" ! Maybe this > > means we need to extend the taskqueue system? > > Possibly. Taskqueues will always complete the function callbacks before > freeing so you dont need to worry about resources disappearing under you. > The one reason would be to bail out of a long running task but, > - Are there any tasks that actually run a long time? Yes, some of the wireless USB drivers can program hundreds of registers during startup. > - If not, its easier just to wait on the drain > > > 3) > > > > In general avoid more than a few synchronous USB transfer inside > > attach/detach. Always defer! Else there are corner cases where the device > > can hang waiting for the transfer timeout 1-5 seconds for every USB > > transfer, and that is unacceptable. > > I disagree. It hugely simplifies drivers to know all the resources are > allocated after attach, you dont need to check for null pointers > throughout the code. I think you misunderstand. The attach code that loads firmware, reads eeprom and performs other configuration must be handed off to another thread, or in your case a taskqueue, so that the USB attach thread can go on and do other things. In the [was configure-] thread you can attach things synchronously. In the case of network adapters you should not rely on the device_attach() event from devd to do something, but rather the event from if_attach(), if such exits. > If programming commands fail/timeout in the attach > routine then the driver needs to check this and abort the attach. You will > wait one or two timeouts max. If you compare the old USB code with the new USB code for if_zyd for example you see that there are dozens of error checks everywhere: if (error != 0) goto fail; In the new USB code I've factored out all those checks into 3 lines of code in every driver: if (usb2_config_td_is_gone(&sc->sc_config_td)) { goto error; } In your patch you remove all error checking! If the taskqueue system does not have an API function that can tell if the taskqueue is being drained from inside the taskqueue callback, the taskqueue system has to be modified! It cannot replace the existing system like it is now! > > 4) > > > > int onoff = USB_TASK_ARG(task); > > > > This won't work! You need to be able to handle N-phase here, where N goes > > to +infinity! If the DTR pin was toggled we should also see a toggle in > > the programming of the DTR pin, not just re-program the last state! If > > there is a USB_TASK_ARG() it must be constant and that is where I start > > seeing problems, or features missing in the taskqueue system. > > > > It is also very important that you somehow freeze the configuration at > > the moment a command is issued. For example in the WLAN drivers. If the > > command is queued when the channel is 5 then we should program channel 5 > > and not fetch the latest channel value from the softc! IMPORTANT! > > This isnt correct. Take your example of WLAN drivers, the net80211 layer > will use ic_curchan for its logic so the driver needs to program the > chip to this value at all times. You can _not_ queue channel changes as > these will be out of sync. Being a little off-sync is not the big problem. The big problem is if the channel value is changing during execution of the code. For example, in the beginning of the code the channel value is 5, then suddenly it becomes 6, and the programming just ends up crazy! xxx_set_channel() { hw_reg = array1[wlan->curchan]; write USB register; hw_reg = array2[wlan->curchan]; write USB register; } > Tasks are very short lived and program the > chipset to the current state where it otherwise could not have been done > due to thread sleeping. > > Also, net80211 will soon have its own thread so you can do things like > state/channel changes directly but in a sleepable context. Good! But until then I strongly suggest you keep things like is. > > > 5) Many of your other changes are good! > > Thanks! Can you explain one thing: How many threads are created to handle taskqueue events? As many as required? If three different taskqueues have three different events, then three threads are used to execute these events? --HPS From imp at bsdimp.com Sun Feb 1 10:27:21 2009 From: imp at bsdimp.com (M. Warner Losh) Date: Sun Feb 1 10:27:28 2009 Subject: USB2 patches In-Reply-To: <20090201175021.GA32503@citylink.fud.org.nz> References: <20090201030628.GE65558@elvis.mu.org> <200902011220.18745.hselasky@c2i.net> <20090201175021.GA32503@citylink.fud.org.nz> Message-ID: <20090201.112459.717301987.imp@bsdimp.com> In message: <20090201175021.GA32503@citylink.fud.org.nz> Andrew Thompson writes: : > 3) : > In general avoid more than a few synchronous USB transfer inside : > attach/detach. Always defer! Else there are corner cases where the device can : > hang waiting for the transfer timeout 1-5 seconds for every USB transfer, and : > that is unacceptable. : : I disagree. It hugely simplifies drivers to know all the resources are : allocated after attach, you dont need to check for null pointers : throughout the code. If programming commands fail/timeout in the attach routine : then the driver needs to check this and abort the attach. You will wait : one or two timeouts max. The only way that a 'deferred attach' makes sense is if the ifnet and other external resources are setup as part of that deferred attach. That way, you don't have the NULL pointer issue. However, doing that introduces races with devd, which are a pita to cope with... Even without deferring the setting up if ifnet, you have races with devd if you defer things in attach that can be hard to cope with in the code. Warner From imp at bsdimp.com Sun Feb 1 10:30:18 2009 From: imp at bsdimp.com (M. Warner Losh) Date: Sun Feb 1 10:30:29 2009 Subject: USB2 patches In-Reply-To: <200902011922.16810.hselasky@c2i.net> References: <200902011220.18745.hselasky@c2i.net> <20090201175021.GA32503@citylink.fud.org.nz> <200902011922.16810.hselasky@c2i.net> Message-ID: <20090201.112756.1320088159.imp@bsdimp.com> In message: <200902011922.16810.hselasky@c2i.net> Hans Petter Selasky writes: : In your patch you remove all error checking! If the taskqueue system does not : have an API function that can tell if the taskqueue is being drained from : inside the taskqueue callback, the taskqueue system has to be modified! It : cannot replace the existing system like it is now! Why does the taskqueue system need to provide that? Why can't the driver set a dying flag in the softc to communicate this fact to the taskqueue tasks? Warner From imp at bsdimp.com Sun Feb 1 10:30:20 2009 From: imp at bsdimp.com (M. Warner Losh) Date: Sun Feb 1 10:30:30 2009 Subject: USB2 patches In-Reply-To: <200902011922.16810.hselasky@c2i.net> References: <200902011220.18745.hselasky@c2i.net> <20090201175021.GA32503@citylink.fud.org.nz> <200902011922.16810.hselasky@c2i.net> Message-ID: <20090201.113013.267651064.imp@bsdimp.com> In message: <200902011922.16810.hselasky@c2i.net> Hans Petter Selasky writes: : In the [was configure-] thread you can attach things synchronously. In the : case of network adapters you should not rely on the device_attach() event : from devd to do something, but rather the event from if_attach(), if such : exits. # # Configure the interface on attach. Due to a historical accident, this # script is called pccard_ether. # notify 0 { match "system" "IFNET"; match "type" "ATTACH"; action "/etc/pccard_ether $subsystem start"; }; notify 0 { match "system" "IFNET"; match "type" "DETACH"; action "/etc/pccard_ether $subsystem stop"; }; Warner From imp at bsdimp.com Sun Feb 1 10:33:30 2009 From: imp at bsdimp.com (M. Warner Losh) Date: Sun Feb 1 10:33:36 2009 Subject: USB2 patches In-Reply-To: <20090201.112459.717301987.imp@bsdimp.com> References: <200902011220.18745.hselasky@c2i.net> <20090201175021.GA32503@citylink.fud.org.nz> <20090201.112459.717301987.imp@bsdimp.com> Message-ID: <20090201.113229.-1891351758.imp@bsdimp.com> In message: <20090201.112459.717301987.imp@bsdimp.com> "M. Warner Losh" writes: : In message: <20090201175021.GA32503@citylink.fud.org.nz> : Andrew Thompson writes: : : > 3) : : > In general avoid more than a few synchronous USB transfer inside : : > attach/detach. Always defer! Else there are corner cases where the device can : : > hang waiting for the transfer timeout 1-5 seconds for every USB transfer, and : : > that is unacceptable. : : : : I disagree. It hugely simplifies drivers to know all the resources are : : allocated after attach, you dont need to check for null pointers : : throughout the code. If programming commands fail/timeout in the attach routine : : then the driver needs to check this and abort the attach. You will wait : : one or two timeouts max. : : The only way that a 'deferred attach' makes sense is if the ifnet and : other external resources are setup as part of that deferred attach. : That way, you don't have the NULL pointer issue. : : However, doing that introduces races with devd, which are a pita to : cope with... Even without deferring the setting up if ifnet, you have : races with devd if you defer things in attach that can be hard to cope : with in the code. Scratch that. The race with devd is already closed since we use ifnet events and not newbus events to configure dynamic devices. There's still a small race on boot with deferring registration of ifnet if you want to synchronously boot.... But I think the default route script closes this race... Warner From hselasky at c2i.net Sun Feb 1 10:35:09 2009 From: hselasky at c2i.net (Hans Petter Selasky) Date: Sun Feb 1 10:35:15 2009 Subject: USB2 patches In-Reply-To: <20090201.112459.717301987.imp@bsdimp.com> References: <20090201030628.GE65558@elvis.mu.org> <20090201175021.GA32503@citylink.fud.org.nz> <20090201.112459.717301987.imp@bsdimp.com> Message-ID: <200902011937.32679.hselasky@c2i.net> Hi Warner, On Sunday 01 February 2009, M. Warner Losh wrote: > In message: <20090201175021.GA32503@citylink.fud.org.nz> > > Andrew Thompson writes: > The only way that a 'deferred attach' makes sense is > if the ifnet and other external resources are setup as part of > that deferred attach. That way, you don't have the NULL pointer issue. That was what the initial code did. > > However, doing that introduces races with devd, which are a pita to > cope with... Even without deferring the setting up if ifnet, you have > races with devd if you defer things in attach that can be hard to cope > with in the code. No, not if the ifnet attach is deferred too. My conclusion is: Do not make match rules for "rumX/uralX/zydX", instead match for the IFNET event in devd.conf. devctl_notify("IFNET", ifp->if_xname, "ATTACH", NULL); --HPS From hselasky at c2i.net Sun Feb 1 10:36:24 2009 From: hselasky at c2i.net (Hans Petter Selasky) Date: Sun Feb 1 10:36:30 2009 Subject: USB2 patches In-Reply-To: <20090201.112756.1320088159.imp@bsdimp.com> References: <200902011220.18745.hselasky@c2i.net> <200902011922.16810.hselasky@c2i.net> <20090201.112756.1320088159.imp@bsdimp.com> Message-ID: <200902011938.48670.hselasky@c2i.net> On Sunday 01 February 2009, M. Warner Losh wrote: > In message: <200902011922.16810.hselasky@c2i.net> > > Hans Petter Selasky writes: > : In your patch you remove all error checking! If the taskqueue system does > : not have an API function that can tell if the taskqueue is being drained > : from inside the taskqueue callback, the taskqueue system has to be > : modified! It cannot replace the existing system like it is now! > > Why does the taskqueue system need to provide that? Why can't the > driver set a dying flag in the softc to communicate this fact to the > taskqueue tasks? That's also possible. Thomas already made a "struct usb2_task" I think, where this flag could be added. --HPS From imp at bsdimp.com Sun Feb 1 10:39:18 2009 From: imp at bsdimp.com (M. Warner Losh) Date: Sun Feb 1 10:39:25 2009 Subject: USB2 patches In-Reply-To: <200902011937.32679.hselasky@c2i.net> References: <20090201175021.GA32503@citylink.fud.org.nz> <20090201.112459.717301987.imp@bsdimp.com> <200902011937.32679.hselasky@c2i.net> Message-ID: <20090201.113714.-887896087.imp@bsdimp.com> In message: <200902011937.32679.hselasky@c2i.net> Hans Petter Selasky writes: : Hi Warner, : : On Sunday 01 February 2009, M. Warner Losh wrote: : > In message: <20090201175021.GA32503@citylink.fud.org.nz> : > : > Andrew Thompson writes: : : > The only way that a 'deferred attach' makes sense is : : > if the ifnet and other external resources are setup as part of : > that deferred attach. That way, you don't have the NULL pointer issue. : : That was what the initial code did. : : > : > However, doing that introduces races with devd, which are a pita to : > cope with... Even without deferring the setting up if ifnet, you have : > races with devd if you defer things in attach that can be hard to cope : > with in the code. : : No, not if the ifnet attach is deferred too. : : My conclusion is: Do not make match rules for "rumX/uralX/zydX", instead match : for the IFNET event in devd.conf. : : devctl_notify("IFNET", ifp->if_xname, "ATTACH", NULL); Yes. We already do that. I was thinking of the geom/device race that we haven't closed rather than this race which we have. Warner From hselasky at c2i.net Sun Feb 1 10:58:43 2009 From: hselasky at c2i.net (Hans Petter Selasky) Date: Sun Feb 1 10:58:49 2009 Subject: USB2 patches In-Reply-To: <200902011938.48670.hselasky@c2i.net> References: <200902011220.18745.hselasky@c2i.net> <20090201.112756.1320088159.imp@bsdimp.com> <200902011938.48670.hselasky@c2i.net> Message-ID: <200902012001.06914.hselasky@c2i.net> Hi Andrew, Regarding using taskqueues. Yes - USB2 can use taskqueues, but I would very much like to have the original queueing mechanism intact. How about: struct task * tasqueue_enqueue_pair(struct taskqueue *queue, struct task *t0, struct task *t1); Which does something similar to this: void * usb2_proc_msignal(struct usb2_process *up, void *_pm0, void *_pm1) { struct usb2_proc_msg *pm0 = _pm0; struct usb2_proc_msg *pm1 = _pm1; struct usb2_proc_msg *pm2; uint32_t d; uint8_t t; mtx_assert(up->up_mtx, MA_OWNED); t = 0; if (pm0->pm_qentry.tqe_prev) { t |= 1; } if (pm1->pm_qentry.tqe_prev) { t |= 2; } if (t == 0) { /* * No entries are queued. Queue "pm0" and use the existing * message number. */ pm2 = pm0; } else if (t == 1) { /* Check if we need to increment the message number. */ if (pm0->pm_num == up->up_msg_num) { up->up_msg_num++; } pm2 = pm1; } else if (t == 2) { /* Check if we need to increment the message number. */ if (pm1->pm_num == up->up_msg_num) { up->up_msg_num++; } pm2 = pm0; } else if (t == 3) { /* * Both entries are queued. Re-queue the entry closest to * the end. */ d = (pm1->pm_num - pm0->pm_num); /* Check sign after subtraction */ if (d & 0x80000000) { pm2 = pm0; } else { pm2 = pm1; } TAILQ_REMOVE(&up->up_qhead, pm2, pm_qentry); } else { pm2 = NULL; /* panic - should not happen */ } DPRINTF(" t=%u, num=%u\n", t, up->up_msg_num); /* Put message last on queue */ pm2->pm_num = up->up_msg_num; TAILQ_INSERT_TAIL(&up->up_qhead, pm2, pm_qentry); /* Check if we need to wakeup the USB process. */ if (up->up_msleep) { up->up_msleep = 0; /* save "cv_signal()" calls */ usb2_cv_signal(&up->up_cv); } return (pm2); } --HPS From thompsa at FreeBSD.org Sun Feb 1 11:08:27 2009 From: thompsa at FreeBSD.org (Andrew Thompson) Date: Sun Feb 1 11:08:36 2009 Subject: USB2 patches In-Reply-To: <200902011922.16810.hselasky@c2i.net> References: <20090131231957.GB31825@citylink.fud.org.nz> <200902011220.18745.hselasky@c2i.net> <20090201175021.GA32503@citylink.fud.org.nz> <200902011922.16810.hselasky@c2i.net> Message-ID: <20090201190820.GB32503@citylink.fud.org.nz> On Sun, Feb 01, 2009 at 07:22:15PM +0100, Hans Petter Selasky wrote: > Hi Andrew, > > > > 3) > > > > > > In general avoid more than a few synchronous USB transfer inside > > > attach/detach. Always defer! Else there are corner cases where the device > > > can hang waiting for the transfer timeout 1-5 seconds for every USB > > > transfer, and that is unacceptable. > > > > I disagree. It hugely simplifies drivers to know all the resources are > > allocated after attach, you dont need to check for null pointers > > throughout the code. > > I think you misunderstand. The attach code that loads firmware, reads eeprom > and performs other configuration must be handed off to another thread, or in > your case a taskqueue, so that the USB attach thread can go on and do other > things. The attach routine allocates resources and attaches the hardware. Things like loading firmware and other configuration are done in the ifnet init routine. > > > It is also very important that you somehow freeze the configuration at > > > the moment a command is issued. For example in the WLAN drivers. If the > > > command is queued when the channel is 5 then we should program channel 5 > > > and not fetch the latest channel value from the softc! IMPORTANT! > > > > This isnt correct. Take your example of WLAN drivers, the net80211 layer > > will use ic_curchan for its logic so the driver needs to program the > > chip to this value at all times. You can _not_ queue channel changes as > > these will be out of sync. > > Being a little off-sync is not the big problem. The big problem is if the > channel value is changing during execution of the code. For example, in the > beginning of the code the channel value is 5, then suddenly it becomes 6, and > the programming just ends up crazy! > > xxx_set_channel() > { > hw_reg = array1[wlan->curchan]; > > write USB register; > > hw_reg = array2[wlan->curchan]; > > write USB register; > } The code should be, xxx_set_channel() { ieee80211_channel c = wlan->curchan; hw_reg = array1[c]; write USB register; hw_reg = array2[c]; write USB register; } cheers, Andrew From hselasky at c2i.net Sun Feb 1 11:12:11 2009 From: hselasky at c2i.net (Hans Petter Selasky) Date: Sun Feb 1 11:12:18 2009 Subject: USB2 patches In-Reply-To: <20090201190820.GB32503@citylink.fud.org.nz> References: <20090131231957.GB31825@citylink.fud.org.nz> <200902011922.16810.hselasky@c2i.net> <20090201190820.GB32503@citylink.fud.org.nz> Message-ID: <200902012014.32190.hselasky@c2i.net> Hi Andrew, On Sunday 01 February 2009, Andrew Thompson wrote: > On Sun, Feb 01, 2009 at 07:22:15PM +0100, Hans Petter Selasky wrote: > > The code should be, > That's what I'm doing already ... I pre-copy all channel & bssid stuff into a message structure ... > xxx_set_channel() > { > ieee80211_channel c = wlan->curchan; > > hw_reg = array1[c]; > write USB register; > hw_reg = array2[c]; > write USB register; > } And don't forget "volatile" ... --HPS From thompsa at FreeBSD.org Sun Feb 1 11:14:37 2009 From: thompsa at FreeBSD.org (Andrew Thompson) Date: Sun Feb 1 11:14:43 2009 Subject: USB2 patches In-Reply-To: <200902012001.06914.hselasky@c2i.net> References: <200902011220.18745.hselasky@c2i.net> <20090201.112756.1320088159.imp@bsdimp.com> <200902011938.48670.hselasky@c2i.net> <200902012001.06914.hselasky@c2i.net> Message-ID: <20090201191432.GD32503@citylink.fud.org.nz> On Sun, Feb 01, 2009 at 08:01:05PM +0100, Hans Petter Selasky wrote: > Hi Andrew, > > Regarding using taskqueues. > > Yes - USB2 can use taskqueues, but I would very much like to have the original > queueing mechanism intact. Can you explain this further? What is t0 vs t1? A taskqueue will execute tasks sequentially, why do you need to pass two tasks in at a time? > How about: > > struct task * > tasqueue_enqueue_pair(struct taskqueue *queue, struct task *t0, struct task > *t1); > > Which does something similar to this: > > void * > usb2_proc_msignal(struct usb2_process *up, void *_pm0, void *_pm1) > { > struct usb2_proc_msg *pm0 = _pm0; > struct usb2_proc_msg *pm1 = _pm1; > struct usb2_proc_msg *pm2; > uint32_t d; > uint8_t t; > > mtx_assert(up->up_mtx, MA_OWNED); > > t = 0; > > if (pm0->pm_qentry.tqe_prev) { > t |= 1; > } > if (pm1->pm_qentry.tqe_prev) { > t |= 2; > } > if (t == 0) { > /* > * No entries are queued. Queue "pm0" and use the existing > * message number. > */ > pm2 = pm0; > } else if (t == 1) { > /* Check if we need to increment the message number. */ > if (pm0->pm_num == up->up_msg_num) { > up->up_msg_num++; > } > pm2 = pm1; > } else if (t == 2) { > /* Check if we need to increment the message number. */ > if (pm1->pm_num == up->up_msg_num) { > up->up_msg_num++; > } > pm2 = pm0; > } else if (t == 3) { > /* > * Both entries are queued. Re-queue the entry closest to > * the end. > */ > d = (pm1->pm_num - pm0->pm_num); > > /* Check sign after subtraction */ > if (d & 0x80000000) { > pm2 = pm0; > } else { > pm2 = pm1; > } > > TAILQ_REMOVE(&up->up_qhead, pm2, pm_qentry); > } else { > pm2 = NULL; /* panic - should not happen */ > } > > DPRINTF(" t=%u, num=%u\n", t, up->up_msg_num); > > /* Put message last on queue */ > > pm2->pm_num = up->up_msg_num; > TAILQ_INSERT_TAIL(&up->up_qhead, pm2, pm_qentry); > > /* Check if we need to wakeup the USB process. */ > > if (up->up_msleep) { > up->up_msleep = 0; /* save "cv_signal()" calls */ > usb2_cv_signal(&up->up_cv); > } > return (pm2); > } > > --HPS > _______________________________________________ > freebsd-usb@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-usb > To unsubscribe, send any mail to "freebsd-usb-unsubscribe@freebsd.org" From thompsa at FreeBSD.org Sun Feb 1 11:18:56 2009 From: thompsa at FreeBSD.org (Andrew Thompson) Date: Sun Feb 1 11:19:02 2009 Subject: USB2 patches In-Reply-To: <200902012014.32190.hselasky@c2i.net> References: <20090131231957.GB31825@citylink.fud.org.nz> <200902011922.16810.hselasky@c2i.net> <20090201190820.GB32503@citylink.fud.org.nz> <200902012014.32190.hselasky@c2i.net> Message-ID: <20090201191851.GE32503@citylink.fud.org.nz> On Sun, Feb 01, 2009 at 08:14:29PM +0100, Hans Petter Selasky wrote: > Hi Andrew, > > On Sunday 01 February 2009, Andrew Thompson wrote: > > On Sun, Feb 01, 2009 at 07:22:15PM +0100, Hans Petter Selasky wrote: > > > > > The code should be, > > > > That's what I'm doing already ... I pre-copy all channel & bssid stuff into a > message structure ... Im saying you dont need to. When you get a channel change request, you fire off the channel task and the program the hardware with the current value from the ieee80211com channel pointer. > > xxx_set_channel() > > { > > ieee80211_channel c = wlan->curchan; > > > > hw_reg = array1[c]; > > write USB register; > > hw_reg = array2[c]; > > write USB register; > > } > > And don't forget "volatile" ... I dont understand this. c is a pointer to a valid net80211 channel which will never disappear. Andrew From thompsa at FreeBSD.org Sun Feb 1 11:26:42 2009 From: thompsa at FreeBSD.org (Andrew Thompson) Date: Sun Feb 1 11:26:49 2009 Subject: USB2 patches In-Reply-To: <200902011922.16810.hselasky@c2i.net> References: <20090131231957.GB31825@citylink.fud.org.nz> <200902011220.18745.hselasky@c2i.net> <20090201175021.GA32503@citylink.fud.org.nz> <200902011922.16810.hselasky@c2i.net> Message-ID: <20090201192637.GG32503@citylink.fud.org.nz> On Sun, Feb 01, 2009 at 07:22:15PM +0100, Hans Petter Selasky wrote: > > If you compare the old USB code with the new USB code for if_zyd for example > you see that there are dozens of error checks everywhere: > > if (error != 0) > goto fail; > > In the new USB code I've factored out all those checks into 3 lines of code in > every driver: > > if (usb2_config_td_is_gone(&sc->sc_config_td)) { > goto error; > } > > In your patch you remove all error checking! If the taskqueue system does not > have an API function that can tell if the taskqueue is being drained from > inside the taskqueue callback, the taskqueue system has to be modified! It > cannot replace the existing system like it is now! Things are still a work in progress, if I have missed some error checking then it can be fixed up. Andrew From hselasky at c2i.net Sun Feb 1 11:29:33 2009 From: hselasky at c2i.net (Hans Petter Selasky) Date: Sun Feb 1 11:29:40 2009 Subject: USB2 patches In-Reply-To: <20090201191432.GD32503@citylink.fud.org.nz> References: <200902011220.18745.hselasky@c2i.net> <200902012001.06914.hselasky@c2i.net> <20090201191432.GD32503@citylink.fud.org.nz> Message-ID: <200902012031.56899.hselasky@c2i.net> On Sunday 01 February 2009, Andrew Thompson wrote: > On Sun, Feb 01, 2009 at 08:01:05PM +0100, Hans Petter Selasky wrote: > > Hi Andrew, > > > > Regarding using taskqueues. > > > > Yes - USB2 can use taskqueues, but I would very much like to have the > > original queueing mechanism intact. > > Can you explain this further? What is t0 vs t1? > > A taskqueue will execute tasks sequentially, Hi Andrew, I've looked in the taskqueue code: if (task->ta_pending) { task->ta_pending++; TQ_UNLOCK(queue); return 0; } Take the following for example. Now you changed it a little bit, but I see similar issues where other commands are involved: 1) queue DTR on cmd 2) queue DTR off cmd 3) queue DTR on cmd Using the taskqueue there is no guarantee that the last command queued is the last command executed! That is dangerous! Because the existing taskqueue enqueue will only increment the pending count and return, if the command/task is already queued. In the example above you can end up like this: DTR on (pending = 2) DTR off (pending = 1) This is not correct. The queuing mechanism in USB2 guarantees that the last queued command is last executed: DTR on (first callback) DTR off (first callback) DTR on (second callback) Queuing: 1) queue DTR on cmd 2) queue DTR off cmd 3) queue DTR on cmd ... N) queue DTR XXX cmd Results in: 1) DTR on (first callback) 2) DTR off (first callback ... M) DTR XXX (second callback) If the user application is faster than USB "M" count is not the same like "N" count, of course. --HPS From imp at bsdimp.com Sun Feb 1 11:57:36 2009 From: imp at bsdimp.com (M. Warner Losh) Date: Sun Feb 1 11:57:41 2009 Subject: USB2 patches In-Reply-To: <20090201191851.GE32503@citylink.fud.org.nz> References: <20090201190820.GB32503@citylink.fud.org.nz> <200902012014.32190.hselasky@c2i.net> <20090201191851.GE32503@citylink.fud.org.nz> Message-ID: <20090201.125712.-1002120178.imp@bsdimp.com> In message: <20090201191851.GE32503@citylink.fud.org.nz> Andrew Thompson writes: : > > xxx_set_channel() : > > { : > > ieee80211_channel c = wlan->curchan; : > > : > > hw_reg = array1[c]; : > > write USB register; : > > hw_reg = array2[c]; : > > write USB register; : > > } : > : > And don't forget "volatile" ... : : I dont understand this. c is a pointer to a valid net80211 channel which : will never disappear. "volatile" would be a bug here. There's no reason to use it at all, since wlan->curchan doesn't match what ANSI-C says a volatile is for. In addition, since it is only loaded once, there wouldn't be a need for it even if it did meet the definition. You *CANNOT* rely on 'volatile' fixing locking issues. Warner From thompsa at FreeBSD.org Sun Feb 1 11:59:05 2009 From: thompsa at FreeBSD.org (Andrew Thompson) Date: Sun Feb 1 11:59:11 2009 Subject: USB2 patches In-Reply-To: <200902012031.56899.hselasky@c2i.net> References: <200902011220.18745.hselasky@c2i.net> <200902012001.06914.hselasky@c2i.net> <20090201191432.GD32503@citylink.fud.org.nz> <200902012031.56899.hselasky@c2i.net> Message-ID: <20090201195859.GH32503@citylink.fud.org.nz> On Sun, Feb 01, 2009 at 08:31:55PM +0100, Hans Petter Selasky wrote: > On Sunday 01 February 2009, Andrew Thompson wrote: > > On Sun, Feb 01, 2009 at 08:01:05PM +0100, Hans Petter Selasky wrote: > > > Hi Andrew, > > > > > > Regarding using taskqueues. > > > > > > Yes - USB2 can use taskqueues, but I would very much like to have the > > > original queueing mechanism intact. > > > > Can you explain this further? What is t0 vs t1? > > > > A taskqueue will execute tasks sequentially, > > Hi Andrew, > > I've looked in the taskqueue code: > > if (task->ta_pending) { > task->ta_pending++; > TQ_UNLOCK(queue); > return 0; > } > > Take the following for example. Now you changed it a little bit, but I see > similar issues where other commands are involved: > > 1) queue DTR on cmd > 2) queue DTR off cmd > 3) queue DTR on cmd > > Using the taskqueue there is no guarantee that the last command queued is the > last command executed! That is dangerous! Because the existing taskqueue > enqueue will only increment the pending count and return, if the command/task > is already queued. > > In the example above you can end up like this: > > DTR on (pending = 2) > DTR off (pending = 1) > > This is not correct. The queuing mechanism in USB2 guarantees that the last > queued command is last executed: There are a few options, - coalesce on a single task (on,off,on = on), the off never happened. - drain the task first then resubmit Those cover both scenarios, (1) you dont care about previous state or (2) you do care so ensure the previous state has executed. If for some reason those are not sufficient then the driver is free to implement its own queue. The current implementation in usb is quite clever but its important not to complicate the internals for situations that dont happen in real life. Andrew From imp at bsdimp.com Sun Feb 1 12:03:16 2009 From: imp at bsdimp.com (M. Warner Losh) Date: Sun Feb 1 12:03:22 2009 Subject: USB2 patches In-Reply-To: <200902012031.56899.hselasky@c2i.net> References: <200902012001.06914.hselasky@c2i.net> <20090201191432.GD32503@citylink.fud.org.nz> <200902012031.56899.hselasky@c2i.net> Message-ID: <20090201.130051.-2130550806.imp@bsdimp.com> In message: <200902012031.56899.hselasky@c2i.net> Hans Petter Selasky writes: : On Sunday 01 February 2009, Andrew Thompson wrote: : > On Sun, Feb 01, 2009 at 08:01:05PM +0100, Hans Petter Selasky wrote: : > > Hi Andrew, : > > : > > Regarding using taskqueues. : > > : > > Yes - USB2 can use taskqueues, but I would very much like to have the : > > original queueing mechanism intact. : > : > Can you explain this further? What is t0 vs t1? : > : > A taskqueue will execute tasks sequentially, : : Hi Andrew, : : I've looked in the taskqueue code: : : if (task->ta_pending) { : task->ta_pending++; : TQ_UNLOCK(queue); : return 0; : } : : Take the following for example. Now you changed it a little bit, but I see : similar issues where other commands are involved: : : 1) queue DTR on cmd : 2) queue DTR off cmd : 3) queue DTR on cmd This is a bad example. In this case, clearly you'd want to turn it on, wait for it to go on, wait a while, turn it off, wait for it to go off, wait a while, then repeat the on part. If you are trying to get a notch signal in DTR, you have to cope this way. If you are implementing an ioctl from userland to do this (as exposed by the tty system), then you'd need to wait for the DTR command to finish anyway before returning to userland, no? There's likely other reasons for wanting to do this, but DTR changes should be synchronous to the caller. Warner From hselasky at c2i.net Sun Feb 1 12:37:43 2009 From: hselasky at c2i.net (Hans Petter Selasky) Date: Sun Feb 1 12:37:50 2009 Subject: USB2 patches In-Reply-To: <20090201.130051.-2130550806.imp@bsdimp.com> References: <200902012001.06914.hselasky@c2i.net> <200902012031.56899.hselasky@c2i.net> <20090201.130051.-2130550806.imp@bsdimp.com> Message-ID: <200902012140.04180.hselasky@c2i.net> Hi Warner, > : Hi Andrew, > : > : I've looked in the taskqueue code: > : > : if (task->ta_pending) { > : task->ta_pending++; > : TQ_UNLOCK(queue); > : return 0; > : } > : > : Take the following for example. Now you changed it a little bit, but I > : see similar issues where other commands are involved: > : > : 1) queue DTR on cmd > : 2) queue DTR off cmd > : 3) queue DTR on cmd > > This is a bad example. The example is not the best. Let's pick another example: Assume you have a 3g modem and we are doing software flow control. Regularly modem status bits are transferred between host and device. Now, lets assume that the modem application has only got one thread. What will happen if transferring the RTS/CTS status bits to the modem is synchronous? Immediate data-loss! Especially at higher data rates. Let me elaborate: Assume it takes 3ms to handle a control request to program the DTR/RTS/CTS, because the device is slow. Then you have a 1024 byte buffer on a BULK endpoint which needs to be handled every 1ms. If DTR/RTS and CTS are not done async, you severely degrade the overall performance of the system, don't you agree about that, if every time you update the modem status have to wait 3ms, having to skip Rx'ed data? > In this case, clearly you'd want to turn it > on, wait for it to go on, wait a while, turn it off, wait for it to go > off, wait a while, then repeat the on part. If you are trying to get > a notch signal in DTR, you have to cope this way. According to your approach we will end up not knowing what state is programmed! It all depends on the sampling point of the softc's value, if I can express it like that. I think it is important to preserve the initial signal. If there was a level, we need to produce a level. It tells the peer something. > If you are > implementing an ioctl from userland to do this (as exposed by the tty > system), then you'd need to wait for the DTR command to finish anyway > before returning to userland, no? The MPSAFETTY API doesn't allow sleeping from what I know. All signalling via MPSAFETTY is made asynchronous. > > There's likely other reasons for wanting to do this, but DTR changes > should be synchronous to the caller. Yes and no. If the TTY device is setup for non-blocking operation, then setting the DTR should return as quick as possible. If the TTY/Modem device is setup for blocking operation, then the IOCTL should return once the DTR [for example] has been set ??? --HPS From hselasky at c2i.net Sun Feb 1 12:57:48 2009 From: hselasky at c2i.net (Hans Petter Selasky) Date: Sun Feb 1 12:57:54 2009 Subject: USB2 patches In-Reply-To: <20090201195859.GH32503@citylink.fud.org.nz> References: <200902011220.18745.hselasky@c2i.net> <200902012031.56899.hselasky@c2i.net> <20090201195859.GH32503@citylink.fud.org.nz> Message-ID: <200902012200.11499.hselasky@c2i.net> Hi Andrew, > > > > This is not correct. The queuing mechanism in USB2 guarantees that the > > last queued command is last executed: > > There are a few options, > > - coalesce on a single task (on,off,on = on), the off never happened. > - drain the task first then resubmit > > Those cover both scenarios, (1) you dont care about previous state or > (2) you do care so ensure the previous state has executed. > "2" is not an option. MPSAFETTY cannot sleep! And there is no IOCTL to drain the DTR command, if I'm not mistaken. > If for some reason those are not sufficient then the driver is free to > implement its own queue. We don't want per-driver queues. We want one queue mechanism for USB. Like I've pointed out, last queued is last executed is a good requirement. For simple things like DTR, sure you could coalesque state changes, but again, that is not optimal, because it is unpredictable. Also see my other e-mail with same subject to Warner. It's like with queues. There is SLIST, LIST, TAILQ, STAILQ. Different need needs different macro. The same should be the case with taskqueues. I have looked at the internals of the taskqueue and the only reordering mechanism is a priority mechanism. To some extent my implementation is about dynamic and efficient priority re-ordering of messages. The taskqueue_enqueue() can have a complexity of X squared, X*X, given the iteration accross the messages already queued, in some cases. Mine has a complexity of 1. What do you think? Is it impossible to add another queue function to the taskqueue system? > The current implementation in usb is quite > clever but its important not to complicate the internals for situations > that dont happen in real life. I would argue that the taskqueue approach is too simple for USB. --HPS From imp at bsdimp.com Sun Feb 1 13:09:22 2009 From: imp at bsdimp.com (M. Warner Losh) Date: Sun Feb 1 13:09:28 2009 Subject: USB2 patches In-Reply-To: <200902012200.11499.hselasky@c2i.net> References: <200902012031.56899.hselasky@c2i.net> <20090201195859.GH32503@citylink.fud.org.nz> <200902012200.11499.hselasky@c2i.net> Message-ID: <20090201.140815.-1322632562.imp@bsdimp.com> In message: <200902012200.11499.hselasky@c2i.net> Hans Petter Selasky writes: : "2" is not an option. MPSAFETTY cannot sleep! And there is no IOCTL to drain : the DTR command, if I'm not mistaken. MPSAFETTY can sleep in the ioctl() context. It does hold the tty lock, so when it wakes up it will know that the tty hasn't gone away... The policy is please don't sleep, but it isn't totally forbidden. It would certainly be an option to queue the first one, note it is pending in the softc and return, then block on subsequent ones until the first one finishes achieving a delayed synchronous behavior and avoiding the problems that you talked about. In this case, you avoid the sleep when you can, and sleep when you can't. But wouldn't the taskqueue run before the process that queued the task? Shouldn't it have a higher priority? And can't you arrange the taskqueue such that it processes 'modem state change queue' requests and have the counter be the number of requests on the queue? then it could do one at a time and you wouldn't have to worry about all this... Warner From alfred at freebsd.org Sun Feb 1 13:36:52 2009 From: alfred at freebsd.org (Alfred Perlstein) Date: Sun Feb 1 13:36:58 2009 Subject: USB2 patches Message-ID: <20090201213651.GK65558@elvis.mu.org> I'm still waiting for Scott Long to give me his decision about the direction to go on that one. Scott, can you comment? -Alfred * Thomas Sparrevohn [090201 06:43] wrote: > Before we switch GENERIC - would it be possibly to have the bus dma issue > committed as well? Without the patch manually added none of my umass devices > work under amd64 > > -----Original Message----- > From: owner-freebsd-usb@freebsd.org [mailto:owner-freebsd-usb@freebsd.org] > On Behalf Of Alfred Perlstein > Sent: 01 February 2009 03:06 > To: Andrew Thompson > Cc: freebsd-usb@freebsd.org > Subject: Re: USB2 patches > > I'll defer to Hans if he feels confident or not about this. > > For what it's worth, we're about to switch GENERIC to use > usb4bsd. > > -Alfred > > * Andrew Thompson [090131 15:20] wrote: > > Hi, > > > > > > I have several patches in my svn user branch that I would like to see > > committed to HEAD. Some of these change the usb2 core code so I am > > interested in feedback or shootdowns. I am right behind the change to > > USB2 and this is an effort to help. > > > > The patch can be found here, > > http://people.freebsd.org/~thompsa/usb_head1.diff > > 73 files changed, 9229 insertions(+), 13261 deletions(-) > > > > but its rather large so it may be easier to look at the various changes > > via the svn web interface. > > > > http://svn.freebsd.org/viewvc/base/user/thompsa/usb/ > > > > > > r187750 > > http://svn.freebsd.org/viewvc/base?view=revision&revision=187750 > > > > Change over to using taskqueue(9) instead of hand rolled threads and > > the config_td system. This removes the config_td code and makes the > > API much simpler to use. > > > > r187751, r187752, r187753, r187754, r187755, r187756 > > http://svn.freebsd.org/viewvc/base?view=revision&revision=187751 > > > > Change over to usb2_proc w/ taskqueues for the usb2/ethernet, > > usb2/serial and usb2/wlan code. > > > > r187965 > > http://svn.freebsd.org/viewvc/base?view=revision&revision=187965 > > > > Move most of the ifnet logic into the usb2_ethernet module, this > includes, > > - make all usb ethernet interfaces named ue%d > > - handle all threading in usb2_ethernet > > - provide default ioctl handler > > - handle mbuf rx > > - provide locked callbacks for init,start,stop,etc > > > > The drivers are not much more than data pushers now. > > > > > > regards, > > Andrew > > -- > - Alfred Perlstein > _______________________________________________ > freebsd-usb@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-usb > To unsubscribe, send any mail to "freebsd-usb-unsubscribe@freebsd.org" > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > -- - Alfred Perlstein From chris at young-alumni.com Sun Feb 1 14:38:39 2009 From: chris at young-alumni.com (Chris Ruiz) Date: Sun Feb 1 14:38:46 2009 Subject: USB2 patches In-Reply-To: <009401c9847b$81b38700$851a9500$@Sparrevohn@btinternet.com> References: <20090131231957.GB31825@citylink.fud.org.nz> <20090201030628.GE65558@elvis.mu.org> <009401c9847b$81b38700$851a9500$@Sparrevohn@btinternet.com> Message-ID: On Feb 1, 2009, at 8:43 AM, Thomas Sparrevohn wrote: > Before we switch GENERIC - would it be possibly to have the bus dma > issue > committed as well? Without the patch manually added none of my umass > devices > work under amd64 I just wanted to chime in with a "me too" here. I applied a patch from the wiki and it has fixed my umass problems on amd64. This needs to be committed before switching usb2 to be default. Thanks, Chris > > > -----Original Message----- > From: owner-freebsd-usb@freebsd.org [mailto:owner-freebsd-usb@freebsd.org > ] > On Behalf Of Alfred Perlstein > Sent: 01 February 2009 03:06 > To: Andrew Thompson > Cc: freebsd-usb@freebsd.org > Subject: Re: USB2 patches > > I'll defer to Hans if he feels confident or not about this. > > For what it's worth, we're about to switch GENERIC to use > usb4bsd. > > -Alfred > > * Andrew Thompson [090131 15:20] wrote: >> Hi, >> >> >> I have several patches in my svn user branch that I would like to see >> committed to HEAD. Some of these change the usb2 core code so I am >> interested in feedback or shootdowns. I am right behind the change to >> USB2 and this is an effort to help. >> >> The patch can be found here, >> http://people.freebsd.org/~thompsa/usb_head1.diff >> 73 files changed, 9229 insertions(+), 13261 deletions(-) >> >> but its rather large so it may be easier to look at the various >> changes >> via the svn web interface. >> >> http://svn.freebsd.org/viewvc/base/user/thompsa/usb/ >> >> >> r187750 >> http://svn.freebsd.org/viewvc/base?view=revision&revision=187750 >> >> Change over to using taskqueue(9) instead of hand rolled threads and >> the config_td system. This removes the config_td code and makes the >> API much simpler to use. >> >> r187751, r187752, r187753, r187754, r187755, r187756 >> http://svn.freebsd.org/viewvc/base?view=revision&revision=187751 >> >> Change over to usb2_proc w/ taskqueues for the usb2/ethernet, >> usb2/serial and usb2/wlan code. >> >> r187965 >> http://svn.freebsd.org/viewvc/base?view=revision&revision=187965 >> >> Move most of the ifnet logic into the usb2_ethernet module, this > includes, >> - make all usb ethernet interfaces named ue%d >> - handle all threading in usb2_ethernet >> - provide default ioctl handler >> - handle mbuf rx >> - provide locked callbacks for init,start,stop,etc >> >> The drivers are not much more than data pushers now. >> >> >> regards, >> Andrew > > -- > - Alfred Perlstein > _______________________________________________ > freebsd-usb@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-usb > To unsubscribe, send any mail to "freebsd-usb-unsubscribe@freebsd.org" > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > _______________________________________________ > freebsd-usb@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-usb > To unsubscribe, send any mail to "freebsd-usb-unsubscribe@freebsd.org" From thompsa at FreeBSD.org Sun Feb 1 20:24:55 2009 From: thompsa at FreeBSD.org (Andrew Thompson) Date: Sun Feb 1 20:25:01 2009 Subject: USB2 patches In-Reply-To: <200902011938.48670.hselasky@c2i.net> References: <200902011220.18745.hselasky@c2i.net> <200902011922.16810.hselasky@c2i.net> <20090201.112756.1320088159.imp@bsdimp.com> <200902011938.48670.hselasky@c2i.net> Message-ID: <20090202042450.GA45701@citylink.fud.org.nz> On Sun, Feb 01, 2009 at 07:38:47PM +0100, Hans Petter Selasky wrote: > On Sunday 01 February 2009, M. Warner Losh wrote: > > In message: <200902011922.16810.hselasky@c2i.net> > > > > Hans Petter Selasky writes: > > : In your patch you remove all error checking! If the taskqueue system does > > : not have an API function that can tell if the taskqueue is being drained > > : from inside the taskqueue callback, the taskqueue system has to be > > : modified! It cannot replace the existing system like it is now! > > > > Why does the taskqueue system need to provide that? Why can't the > > driver set a dying flag in the softc to communicate this fact to the > > taskqueue tasks? > > That's also possible. Thomas already made a "struct usb2_task" I think, where > this flag could be added. I have been thinking about this more. The main issue is usb requests timing out when the device is yanked, the udev structure should keep state on this and set it as detached before calling the device detach routine. This will allow usb requests that may be running in the taskqueue to abort gracefully and taskqueue should drain quite easily. If the device hasnt been yanked then it will have no issues draining as the queued tasks will happily run to completion. Andrew From bugmaster at FreeBSD.org Mon Feb 2 03:07:05 2009 From: bugmaster at FreeBSD.org (FreeBSD bugmaster) Date: Mon Feb 2 03:09:30 2009 Subject: Current problem reports assigned to freebsd-usb@FreeBSD.org Message-ID: <200902021107.n12B737p094601@freefall.freebsd.org> Note: to view an individual PR, use: http://www.freebsd.org/cgi/query-pr.cgi?pr=(number). The following is a listing of current problems submitted by FreeBSD users. These represent problem reports covering all versions including experimental development code and obsolete releases. S Tracker Resp. Description -------------------------------------------------------------------------------- f usb/131123 usb [patch] re-add UQ_ASSUME_CM_OVER_DATA USB quirk o usb/131074 usb no run-time detection of usb devices plugged into exte o usb/130736 usb Page fault unplugging USB stick o usb/130325 usb [usb] [patch] fix tools/tools/usb/print-usb-if-vids.sh o usb/130230 usb Samsung Electronics YP-U3 does not attach in 7.1-RELEA o usb/130208 usb Boot process severely hampered by umass0 error o usb/130122 usb [newusb] DVD drive detects as 'da' device o usb/130066 usb [newusb] Serial adaptor use fail with 'unsupported spe o usb/129964 usb [newusb] disconnection of ugen devices isn't logged o bin/129963 usb [newusb] usbconfig(8) fails with misleading error when o docs/129962 usb [newusb] usbconfig(8) refers to non-existant usb2_core o usb/129945 usb [usbdevs] [patch] add u3g support for Longcheer WM66 U o usb/129766 usb [usb] plugging in usb modem HUAWEI E226 panics system o usb/129758 usb [uftdi] [patch] add Pyramid LCD usb support o usb/129673 usb [uhci] uhci (uhub) confused on replugging USB 1.1 scan o usb/129522 usb [ubsa] [patch] add support for ZTE AC8700 modem o usb/129500 usb [umass] [panic] FreeBSD Crashes when connecting SanDis o usb/129311 usb [usb] [panic] Instant crash with an USB card reader o usb/129251 usb [usbdevs] [patch] Liebert UPS being assigned uhid and o usb/129173 usb [uplcom] [patch] Add support for Corega CG-USBRS232R a s usb/128990 usb [usb] u3g does not handle RTS/CTS available on for exa o usb/128977 usb [usb] [patch] uaudio is not full duplex o usb/128803 usb [usbdevs] [patch] Quirk for I-Tuner Networks USBLCD4X2 o usb/128590 usb [patch] [newusb] Updates to NOTES for new USB stack o usb/128485 usb [umodem] [patch] Nokia N80 modem support o usb/128425 usb [umass] Cannot Connect Maxtor Onetouch 4 USB drive f usb/128418 usb [panic] [rum] loading if_rum causes panic, looks like o usb/128324 usb [uplcom] [patch] remove baud rate restriction for PL23 o usb/127980 usb [umass] [patch] Fix Samsung YP U2 MP3 player on 7.x an o usb/127926 usb [boot] USB Timeout during bootup o usb/127549 usb [umass] [patch] Meizu MiniPlayer M6 (SL) requires some s usb/127453 usb [request] ubsa, uark, ubser, uftdi, and friends should o usb/127423 usb [boot] BTX halted on Gigabyte GA-MA69VM-S2 / AMD Sempr o usb/127342 usb [boot] cannot enable usb keyboard and mouse support in o kern/127222 usb [ohci]: Regression in 7.0 usb storage generic driver o usb/126884 usb [ugen] [patch] Bug in buffer handling in ugen.c f usb/126848 usb [usb]: USB Keyboard hangs during Installation o usb/126740 usb [ulpt] doesn't work on 7.0-RELEASE, 10 second stall be o usb/126519 usb [usb] [panic] panic when plugging in an iphone o kern/126396 usb [panic] kernel panic after unplug USB Bluetooth device o usb/125736 usb [ukbd] [hang] system hangs after AT keyboard detect if o usb/125631 usb [ums] [panic] kernel panic during bootup while 'Logite o usb/125510 usb [panic] repeated plug and unplug of USB mass storage d o usb/125450 usb [panic] Removing USB flash card while being accessed c o usb/125264 usb [patch] sysctl for set usb mouse rate (very useful for o usb/125238 usb [ums] Habu Mouse turns off in X o usb/125088 usb [keyboard] Touchpad not detected on Adesso AKB-430UG U o usb/125072 usb [uplcom] [patch] add Mobile Action MA-620 Infrared Ada o usb/124980 usb [panic] kernel panic on detaching unmounted umass devi o kern/124777 usb [ucom] USB cua devices don't revert to tty devices whe o usb/124758 usb [rum] [panic] rum panics SMP kernel o usb/124708 usb [panic] Kernel panic on USB KVM reattach o usb/124604 usb [ums] Microsoft combo wireless mouse doesn't work o usb/123969 usb [usb] Supermicro H8SMi-2 usb problem: port reset faile o usb/123714 usb [usb] [panic] Panic when hald-storage-probe runs with o usb/123691 usb usbd(8): usbd hangs o usb/123690 usb [usb] [panic] Panic on USB device insertion when usb l o usb/123611 usb [usb] BBB reset failed, STALLED from Imation/Mitsumi U o usb/123509 usb [umass] continuous reset Samsung SGH-G600 phone o usb/123352 usb [usbdevs] [patch] Add Option GTMAX3.6/7.2 and Quallcom o usb/123351 usb [usbdevs] [patch] Add Reiner SCT cyberJack, Omnikey [2 o usb/122992 usb [umass] [patch] MotoROKR Z6 Phone not recognised by um o usb/122956 usb [ubsa] [patch] add support for Novatel Wireless XU870 o usb/122936 usb [ucom] [ubsa] Device does not receive interrupt o usb/122905 usb [ubsa] [patch] add Huawei E220 to ubsa o usb/122819 usb [usb] [patch] Patch to provide dynamic additions to th o usb/122813 usb [udbp] [request] udbp driver should be removed in favo o usb/122621 usb [patch] [request] New driver for Sierra Wireless 3G US o usb/122547 usb [ehci] USB Printer not being recognized after reboot o usb/122539 usb [ohci] [panic] AnyDATA ADU-E1000D - kernel panic: ohci o usb/122483 usb [panic] [ulpt] Repeatable panic in 7.0-STABLE o usb/122119 usb [umass] umass device causes creation of daX but not da o usb/122025 usb [uscanner] [patch] uscanner does not attach to Epson R o usb/121755 usb [ohci] [patch] Fix panic after ohci/uhub cardbus devic o usb/121734 usb [ugen] ugen HP1022 printer device not working since up o usb/121708 usb [keyboard] nforce 650i mobo w/ usb keyboard infinite k o usb/121474 usb [cam] [patch] QUIRK: SAMSUNG HM250JI in LaCie usb hard o usb/121426 usb [patch] [uscanner] add HP ScanJet 3570C o usb/121275 usb [boot] FreeBSD fails to boot with usb legacy support e o usb/121232 usb [usb] [panic] USB CardBus card removal causes reboot s p usb/121184 usb [uipaq] [patch] add ids from linux ipaq driver (plus a o usb/121169 usb [umass] Issues with usb mp3 player o usb/121045 usb [uftdi] [patch] Add support for PC-OP-RS1 and KURO-RS o usb/120786 usb [usb] [panic] Kernel panic when forced umount of a det o usb/120729 usb [panic] fault while in kernel mode with connecting USB o usb/120572 usb [umass] [patch] quirk to support ASUS P535 as umass (a o usb/120321 usb [hang] System hangs when transferring data to WD MyBoo o usb/120283 usb [panic] Automation reboot with wireless keyboard & mou o usb/120034 usb [hang] 6.2 & 6.3 hangs on boot at usb0: OHCI with 1.5 o usb/120017 usb [ehci] [patch] CS5536 (AMD Geode) USB 2.0 quirk o usb/119981 usb [axe] [patch] add support for LOGITEC LAN-GTJ/U2 gigab o usb/119977 usb [ums] Mouse does not work in a Cherry-USB keyboard/mou o usb/119653 usb [cam] [patch] iriver s7 player sync cache error patch o usb/119633 usb [umass] umass0: BBB reset failed, IOERROR [regression] o usb/119513 usb [irq] inserting dlink dwl-g630 wireless card results i o usb/119509 usb [usb] USB flaky on Dell Optiplex 755 o usb/119481 usb [hang] FreeBSD not responding after connecting USB-Mas o usb/119389 usb [umass] Sony DSC-W1 CBI reset failed, STALLED [regress o usb/119227 usb [ubsa] [patch] ubsa buffer is too small; should be tun o usb/119201 usb [cam] [patch] Quirks for Olympus FE-210 camera, LG and o usb/118686 usb [usbdevs] [patch] teach usbdevs / ubsa(4) about Huawei o usb/118485 usb [usbdevs] [patch] Logitech Headset Workaround o usb/118480 usb [umass] Timeout in USB mass storage freezes vfs layer o usb/118353 usb [panic] [ppp] repeatable kernel panic during ppp(4) se o usb/118141 usb [ucom] usb serial and nokia phones ucomreadcb ucomread o usb/118140 usb [ucom] [patch] quick hack for ucom to get it behave wi o usb/118098 usb [umass] 6th gen iPod causes problems when disconnectin o usb/117955 usb [umass] [panic] inserting minolta dimage a2 crashes OS o usb/117946 usb [panic] D-Link DUB-E100 rev. B1 crashes FreeBSD 7.0-BE o usb/117938 usb [ums] [patch] Adding support for MS WL Natural and MS o usb/117911 usb [ums] [request] Mouse Gembird MUSWC not work o usb/117893 usb [umass] Lacie USB DVD writing failing o usb/117613 usb [uhci] [irq] uhci interrupt storm & USB leaked memory o usb/117598 usb [uaudio] [patch] Not possible to record with Plantroni o usb/117313 usb [umass] [panic] panic on usb camera insertion o usb/117200 usb [ugen] ugen0 prints strange string on attach if detach o usb/117185 usb [umodem] [patch] Add support for UNION interface descr o usb/117183 usb [panic] USB/fusefs -- panic while transferring large a o usb/116947 usb [ukbd] [patch] [regression] enable boot protocol on th o usb/116699 usb [usbhid] USB HID devices do not initialize at system b o usb/116561 usb [umodem] [panic] RELENG_6 umodem panic "trying to slee o usb/116282 usb [ulpt] Cannot print on USB HP LJ1018 or LJ1300 o usb/115935 usb [usbdevs] [patch] kernel counterproductively attaches o usb/115933 usb [uftdi] [patch] RATOC REX-USB60F (usb serial converter o usb/115400 usb [ehci] Problem with EHCI on ASUS M2N4-SLI o usb/115298 usb [ulpt] [panic] Turning off USB printer panics kernel o usb/114916 usb [umass] [patch] USB Maxtor drive (L300RO) requires qui o kern/114780 usb [uplcom] [panic] Panics while stress testing the uplco o usb/114682 usb [umass] generic USB media-card reader unusable o usb/114310 usb [libusb] [patch] [panic] USB hub attachment panics ker o usb/114068 usb [umass] [patch] Problems with connection of the umass o conf/114013 usb [patch] WITHOUT_USB allow to compil a lot of USB stuff s usb/113977 usb [request] Need a way to set mode of USB disk's write c o usb/113672 usb [ehci] [panic] Kernel panic with AEWIN CB6971 s usb/113629 usb [ukbd] Dropped USB keyboard events on Dell Latitude D6 o usb/113432 usb [ucom] WARNING: attempt to net_add_domain(netgraph) af a usb/113060 usb [usbdevs] [patch] Samsung printer not working in bidir o usb/112944 usb [ulpt] [patch] Bi-directional access to HP LaserJet 10 o usb/112640 usb [usb] [hang] Kernel freezes when writing a file to an o usb/112631 usb [panic] Problem with SONY DSC-S80 camera on umount s usb/112568 usb [umass] [request] USB mode may wrong when mounting Pla o usb/112463 usb [umass] problem with Samsung USB DVD writer, libscg an o usb/112461 usb [ehci] [request] ehci USB 2.0 doesn't work on nforce4 o usb/111753 usb [uhid] [panic] Replicable system panic involving UHID s usb/110991 usb [usbdevs] [patch] QUIRK: Super Top IDE DEVICE (depends o usb/110988 usb [umass] [patch] Handling of quirk IGNORE_RESIDUE is um o usb/110856 usb [ugen] [patch] interrupt in msgs are truncated when bu o usb/110197 usb [umass] Sony PSP umass device does not detach from EHC o usb/109397 usb [panic] on boot from USB flash o usb/109274 usb [usb] MCP55 USB Controller fails to attach in AMD64 Cu o usb/108513 usb [umass] Creative MuVo TX FM fails in 6.2-RELEASE [regr s usb/108344 usb [panic] kernel with atausb panics when unplugging USB o usb/108056 usb [ohci] Mouse gets powered off during device probe when o usb/107935 usb [uplcom] [panic] panic while accessing /dev/cuaU0 o usb/107924 usb [patch] usbd(8) does not call detach o usb/107848 usb [umass] [request] cannot access Samsung flash disk o usb/107827 usb [ohci] [panic] ohci_add_done addr not found o usb/107496 usb [uhub] USB device problem on RELENG_6_2 (SHORT_XFER) [ o usb/107446 usb [umass] umass problems (usb and fw disks) o usb/107388 usb [patch] [request] new driver: add utoppy device from N o usb/107248 usb [umass] [patch] scsi_da.c quirk for Cowon iAUDIO X5 MP o usb/107243 usb [cam] [patch] Apacer USB Flash Drive quirk o usb/106861 usb [usbdevs] [patch]: usbdevs update: Add product ACER Ze s usb/106832 usb [usb] USB HP printer is not detected by kernel when AC o usb/106648 usb [umass] [hang] USB Floppy on D1950 10 min Hang on Inse o usb/106621 usb [axe] [patch] DLINK DUB-E100 support broken o usb/106615 usb [uftdi] uftdi module does not automatically load with o usb/106041 usb [usb] [request] FreeBSD does not recognise Mustek Bear o usb/105361 usb [panic] Kernel panic during unmounting mass storage (C o usb/105186 usb [ehci] [panic] USB 2.0/ehci on FreeBSD 6.2-PRE/AMD64 c o usb/105065 usb [ata] [usb] SATA - USB Bridge o usb/104830 usb [umass] system crashes when copying data to umass devi o usb/104645 usb [umass] [request] Rave C-201 MP3 player does not commu o usb/104352 usb [ural] [patch] ural driver doesnt work o usb/104292 usb [umass] [hang] system lockup on forced umount of usb-s o usb/104290 usb [umass] [patch] quirk: TOSHIBA DVD-RAM drive (libretto o usb/103917 usb [uhub] USB driver reports "Addr 0 should never happen" o usb/103418 usb usbhidctl(1): [patch] [request] usbhidctl: add ability o usb/103289 usb [request] USB 2.0 problems on AMD LX-800 CPU and CS-55 o usb/103046 usb [ulpt] [patch] ulpt event driven I/O with select(2) an o usb/103025 usb [uhub] [panic] wrong detection of USB device for FreeB o usb/102976 usb [panic] Casio Exilim Digital Camera causes panic on in o usb/102678 usb [keyboard] Dell PowerEdge DRAC5 USB Keyboard does not o usb/102066 usb [ukbd] usb keyboard and multimedia keys don't work o usb/101775 usb [libusbhid] [patch] possible error in report descripto o usb/101761 usb [usb] [patch] [request] usb.h: increase maximal size o o usb/101752 usb [umass] [panic] 6.1-RELEASE kernel panic on usb device o usb/101448 usb [ohci] FBSD 6.1-STABLE/AMD64 crashes under heavy USB/O o usb/101096 usb [ural] [panic] USB WLAN occasionally causes kernel-pan o usb/100746 usb [keyboard] system does not boot due to USB keyboard pr o usb/99538 usb [keyboard] while using USB keyboard default params of o usb/99431 usb [keyboard] FreeBSD on MSI 6566E (Intel 845E motherboar o usb/98343 usb [boot] BBB reset failed errors with Creative Muvo MP3 o usb/97472 usb [cam] [patch] add support for Olympus C150,D390 s usb/97286 usb [mouse] [request] MS Wireless Intellimouse Explorer 2. o usb/97175 usb [umass] [hang] USB cardreader hangs system o usb/96457 usb [umass] [panic] fatback on umass = reboot o usb/96381 usb [cam] [patch] add a quirk table entry for a flash ram o usb/96224 usb [usb] [msdosfs] mount_msdosfs cause page fault in sync s usb/96120 usb [ums] [request] USB mouse not always detected s usb/95636 usb [umass] [boot] 5 minute delay at boot when using VT620 o usb/95562 usb [umass] Write Stress in USB Mass drive causes "vinvalb s usb/95348 usb [keyboard] USB keyboard unplug causes noise on screen o usb/95037 usb [umass] USB disk not recognized on hot-plug. o usb/94897 usb [panic] Kernel Panic when cleanly unmounting USB disk o usb/94717 usb [ulpt] Reading from /dev/ulpt can break work of a UHCI o usb/94384 usb [panic] kernel panic with usb2 hardware o usb/93872 usb [cam] [patch] SCSI quirk required for ELTA 8061 OL USB o usb/93828 usb [ohci] [panic] ohci causes panic on boot (HP Pavillion o usb/93408 usb [mouse] hw.acpi.cpu.cx_lowest=C3 on AMD Turion causes o usb/93389 usb [umass] [patch] Digital Camera Pentax S60 don't work o usb/93155 usb [ulpt] /dev/ulpt0: device busy, USB printer does not w o usb/92852 usb [ums] [patch] Vertical scroll not working properly on o usb/92171 usb [panic] panic unplugging Vodafone Mobile Connect (UMTS o usb/92142 usb [uhub] SET_ADDR_FAILED and SHORT_XFER errors from usb o usb/92083 usb [ural] [panic] panic using WPA on ural NIC in 6.0-RELE o usb/92052 usb [ulpt] usbd causes defunct process with busy file-hand o usb/91906 usb [ehci] [hang] FreeBSD hangs while booting with USB leg o usb/91896 usb camcontrol(8): Serial Number of USB Memory Sticks is n o usb/91811 usb [umass] Compact Flash in HP Photosmart 2610 return " o usb/91629 usb [usb] usbd_abort_pipe() may result in infinite loop o usb/91546 usb [umodem] [patch] Nokia 6630 mobile phone does not work o usb/91538 usb [ulpt] [patch] Unable to print to EPSON CX3500 o usb/91283 usb [boot] [regression] booting very slow with usb devices o usb/91238 usb [umass] USB tape unit fails to write a second tape fil o usb/90700 usb [umass] [panic] Kernel panic on connect/mount/use umas o usb/89954 usb [umass] [panic] USB Disk driver race condition? s usb/89003 usb [request] LaCie Firewire drive not properly supported o usb/88743 usb [hang] [regression] USB makes kernel hang at boot (reg o usb/88408 usb [axe] axe0 read PHY failed o usb/87648 usb [mouse] Logitech USB-optical mouse problem. o usb/87224 usb [usb] Cannot mount USB Zip750 o usb/86767 usb [umass] [patch] bogus "slice starts beyond end of the o usb/86298 usb [mouse] Known good USB mouse won't work with correct s s usb/85067 usb [uscanner] Cannot attach ScanJet 4300C to usb device f usb/84750 usb [hang] 6-BETA2 reboot/shutdown with root_fs on externa s usb/84336 usb [usb] [reboot] instant system reboot when unmounting a o usb/84326 usb [umass] Panic trying to connect SCSI tape drive via US o usb/83977 usb [ucom] [panic] ucom1: open bulk out error (addr 2): IN o usb/83863 usb [ugen] Communication problem between opensc/openct via o usb/83756 usb [ums] [patch] Microsoft Intellimouse Explorer 4.0A doe f usb/83677 usb [usb] [request] usb controller often not detected (Sun o usb/83563 usb [umass] [panic] Page Fault while detaching Mpman Usb d o usb/83504 usb [kernel] [patch] SpeedTouch USB stop working on recent o usb/82660 usb [ehci] [panic] EHCI: I/O stuck in state 'physrd'/panic s usb/82569 usb [umass] [panic] USB mass storage plug/unplug causes sy o usb/82520 usb [udbp] [reboot] Reboot when USL101 connected o usb/82350 usb [ucom] [panic] null pointer dereference in USB stack o usb/81621 usb [ehci] [hang] external hd hangs under load on ehci o usb/80935 usb [uvisor] [patch] uvisor.c is not work with CLIE TH55. o usb/80862 usb [patch] USB locking issues: missing some Giant calls o usb/80854 usb [patch] [request] suggestion for new iface-no-probe me o usb/80829 usb [modules] [panic] possible panic when loading USB-modu s usb/80777 usb [request] usb_rem_task() should wait for callback to c s usb/80776 usb [udav] [request] UDAV device driver shouldn't use usb_ o usb/80774 usb [patch] have "usbd_find_desc" in line with the other " o usb/80361 usb [umass] [patch] mounting of Dell usb-stick fails o usb/80040 usb [hang] Use of sound mixer causes system freeze with ua o usb/79723 usb [usb] [request] prepare for high speed isochronous tra o usb/79722 usb [ehci] wrong alignments in ehci.h a usb/79656 usb [ehci] RHSC interrupts lost o usb/79524 usb [ulpt] printing to Minolta PagePro 1[23]xxW via USB fa o usb/79287 usb [uhci] [hang] UHCI hang after interrupt transfer o usb/79269 usb [ohci] USB ohci da0 plug/unplug causes crashes and loc o usb/78984 usb [umass] [patch] Creative MUVO umass failure o usb/77294 usb [ucom] [panic] ucom + ulpcom panic o usb/77184 usb [umass] [panic] kernel panic on USB device disconnect, o usb/76732 usb [ums] Mouse problems with USB KVM Switch o usb/76653 usb [umass] [patch] Problem with Asahi Optical usb device o usb/76461 usb [umass] disklabel of umass(4)-CAM(4)-da(4) not used by o usb/76395 usb [uhci] USB printer does not work, usbdevs says "addr 0 s usb/75928 usb [umass] [request] Cytronix SmartMedia card (SMC) reade o usb/75800 usb [ucom] ucom1: init failed STALLED error in time of syn o usb/75797 usb [sound] 5.3-STABLE(2005 1/4) detect USB headset, But c o usb/75764 usb [umass] [patch] "umass0: Phase Error" - no device for o usb/75705 usb [umass] [panic] da0 attach / Optio S4 (with backtrace) o usb/74771 usb [umass] [hang] mounting write-protected umass device a s usb/74453 usb [umass] [patch] Q-lity CD-RW USB ECW-043 (ScanLogic SL o usb/74211 usb [umass] USB flash drive causes CAM status 0x4 on 4.10R o usb/73307 usb [panic] Kernel panics on USB disconnect s usb/72733 usb [ucom] [request] Kyocera 7135 Palm OS connection probl o usb/71455 usb [umass] Slow USB umass performance of 5.3 o usb/71417 usb [ugen] Cryptoflex e-gate USB token (ugen0) communicati o usb/71416 usb [ugen] Cryptoflex e-gate USB token (ugen0) detach is n o usb/71280 usb [aue] aue0 device (linksys usb100tx) doesn't work in 1 o usb/71155 usb [ulpt] misbehaving usb-printer hangs processes, causes o usb/70523 usb [umct] [patch] umct sending/receiving wrong characters o usb/69006 usb [usbdevs] [patch] Apple Cinema Display hangs USB ports o usb/68232 usb [ugen] [patch] ugen(4) isochronous handling correction o usb/67301 usb [uftdi] [panic] RTS and system panic o usb/66547 usb [ucom] Palm Tungsten T USB does not initialize correct o usb/63621 usb [umass] [panic] USB MemoryStick Reader stalls/crashes s usb/62257 usb [umass] [request] card reader UCR-61S2B is only half-s o usb/59698 usb [keyboard] [patch] Rework of ukbd HID to AT code trans s bin/57255 usb [patch] usbd(8) and multi-function devices s usb/52026 usb [usb] [request] umass driver support for InSystem ISD2 s usb/51958 usb [urio] [patch] update for urio driver o i386/46371 usb USB controller cannot be initialized on IBM Netfinity o usb/40948 usb [umass] [request] USB HP CDW8200 does not work o usb/30929 usb [usb] [patch] use usbd to initialize USB ADSL modem 300 problems total. From stevecalfee at gmail.com Mon Feb 2 11:36:29 2009 From: stevecalfee at gmail.com (Steve Calfee) Date: Mon Feb 2 11:36:36 2009 Subject: newusb/usb2 build breakage in tinybsd In-Reply-To: <200901311014.01419.hselasky@freebsd.org> References: <4a5ff6bc0901301732t7233335ch1077a74605fffb81@mail.gmail.com> <200901311014.01419.hselasky@freebsd.org> Message-ID: <4a5ff6bc0902021136w193c048am1f32c377de25d70e@mail.gmail.com> Hi Hans, On Sat, Jan 31, 2009 at 1:13 AM, Hans Petter Selasky wrote: > Hi Steve, > > On Saturday 31 January 2009, Steve Calfee wrote: >> Hi, >> >> I am trying to backport usb2 to freebsd7.0. I have followed the >> instructions at http://www.selasky.org/hans_petter/usb4bsd/index.html >> and things work ok on the install until I get to the recommended make >> step for me to manually handle (printed out by your make file). >> Incidentally, your web site should say to build in the FreeBSD.usb2 >> directory, I think. >> >> One complication is that I am crosscompiling with the tinybsd script - >> at least the target is an x86. >> >> I was held up for awhile because I missed the instruction echo'ed from >> the ..../FreeBSD.usb2/Makefile telling me to patch/change kmod.mk. >> Missing that causes the make to stop because usb2_if.h is missing. > > Are you building the kernel or Modules? > I tried both. But then I did a little RTFM of your website and the install makefile. When I used the make install, and changed kmod.mk the make succeeded except for a few USB2 routines (serial*, wlan*, bluetooth* and storage_rio) that must be using new kernel APIs because their build is broken in my FreeBSD7.0. I removed those broken module builds from the Makefile at ...modules/usb2/Makefile. For now I will ignore them and work on verifying the backport works. Thanks for your opinion on removing td_fpop. I'll let you know if removing that breaks things. Regards, Steve From gavin at FreeBSD.org Mon Feb 2 12:51:32 2009 From: gavin at FreeBSD.org (gavin@FreeBSD.org) Date: Mon Feb 2 12:51:43 2009 Subject: kern/107446: problems with usb and fw disks Message-ID: <200902022051.n12KpShb045098@freefall.freebsd.org> Old Synopsis: [umass] umass problems (usb and fw disks) New Synopsis: problems with usb and fw disks State-Changed-From-To: open->feedback State-Changed-By: gavin State-Changed-When: Mon Feb 2 20:46:56 UTC 2009 State-Changed-Why: To submitter: Sorry this PR has sat so long without a response. I wonder, are you able to provide two full copies of any output from the kernel (/var/log/messages), one while using these disks as firewire disks, and the other while using it as a USB disk? Also, if the machine panics, are you able to get a backtrace in both cases ? (you may need to recompile your kernel with the Kernel Debugger, see http://www.freebsd.org/doc/en/books/developers-handbook/kerneldebug.html for details). Thanks! Responsible-Changed-From-To: freebsd-usb->gavin Responsible-Changed-By: gavin Responsible-Changed-When: Mon Feb 2 20:46:56 UTC 2009 Responsible-Changed-Why: Not USB specific. Track. http://www.freebsd.org/cgi/query-pr.cgi?pr=107446 From thompsa at FreeBSD.org Tue Feb 3 10:40:17 2009 From: thompsa at FreeBSD.org (Andrew Thompson) Date: Tue Feb 3 10:40:23 2009 Subject: USB2 patches In-Reply-To: <200902012140.04180.hselasky@c2i.net> References: <200902012001.06914.hselasky@c2i.net> <200902012031.56899.hselasky@c2i.net> <20090201.130051.-2130550806.imp@bsdimp.com> <200902012140.04180.hselasky@c2i.net> Message-ID: <20090203184011.GA64941@citylink.fud.org.nz> On Sun, Feb 01, 2009 at 09:40:01PM +0100, Hans Petter Selasky wrote: > Hi Warner, > The example is not the best. Let's pick another example: > > Assume you have a 3g modem and we are doing software flow control. Regularly > modem status bits are transferred between host and device. Now, lets assume > that the modem application has only got one thread. What will happen if > transferring the RTS/CTS status bits to the modem is synchronous? Immediate > data-loss! Especially at higher data rates. > > Let me elaborate: Assume it takes 3ms to handle a control request to program > the DTR/RTS/CTS, because the device is slow. Then you have a 1024 byte buffer > on a BULK endpoint which needs to be handled every 1ms. If DTR/RTS and CTS > are not done async, you severely degrade the overall performance of the > system, don't you agree about that, if every time you update the modem status > have to wait 3ms, having to skip Rx'ed data? As Warner suggested, you would only drain if the previous DTR/RTS/etc command is still in flight so there is actually no delay. Say DTR is queued to turn on, its correct to drain this before allowing a subsequent command to turn it off. To queue this and have a thread execute a series of on/off/on/off in one go later isnt right IMHO. Andrew From devet at devet.org Tue Feb 3 11:41:22 2009 From: devet at devet.org (Arjan de Vet) Date: Tue Feb 3 11:41:53 2009 Subject: usb/128760: [ums] patch for Microsoft Comfort Optical Mouse 3000 (model 1043) In-Reply-To: <200811121333.mACDXYOZ095222@freefall.freebsd.org> References: <200811121333.mACDXYOZ095222@freefall.freebsd.org> Message-ID: <20090203185946.GA3498@adv.devet.org> >Responsible-Changed-From-To: freebsd-usb->cperciva >Responsible-Changed-By: cperciva >Responsible-Changed-When: Wed Nov 12 13:32:58 UTC 2008 >Responsible-Changed-Why: >Fixed in HEAD > >http://www.freebsd.org/cgi/query-pr.cgi?pr=128760 I've found some time to do more testing/debugging and it seems my previous patch is wrong. This mouse needs an sc->sc_isize = 6 instead of the usual 5. Therefore the quirk entry in my original patch should be removed and the attached patch (relative to RELENG_7_1) makes all buttons/wheel/etc. work. I'm not sure whether this is the best way to do this, please let me know if there's a more structural way to deal with the specific characteristics of this mouse. Arjan -------------- next part -------------- Index: ums.c =================================================================== RCS file: /home/freebsd/CVS/src/sys/dev/usb/ums.c,v retrieving revision 1.96.2.5.2.1 diff -u -r1.96.2.5.2.1 ums.c --- ums.c 25 Nov 2008 02:59:29 -0000 1.96.2.5.2.1 +++ ums.c 25 Nov 2008 18:53:29 -0000 @@ -404,6 +404,29 @@ sc->sc_loc_btn[2].pos = 2; } + /* + * The Microsoft Comfort Optical Mouse 3000 Model 1043 has a 4-way + * tilt wheel and 4 buttons. It reports size=2 and id=19 which seem + * bogus. + */ + if (uaa->vendor == USB_VENDOR_MICROSOFT && + uaa->product == USB_PRODUCT_MICROSOFT_COMFORT3000) { + sc->flags = UMS_T | UMS_Z; + sc->nbuttons = 4; + sc->sc_isize = 6; + sc->sc_iid = 0; + sc->sc_loc_x.pos = 16; + sc->sc_loc_y.pos = 24; + sc->sc_loc_z.pos = 32; + sc->sc_loc_t.pos = 40; + sc->sc_loc_t.size = 8; + sc->sc_loc_btn[0].pos = 8; + sc->sc_loc_btn[1].pos = 9; + sc->sc_loc_btn[2].pos = 10; + sc->sc_loc_btn[3].pos = 12; + sc->sc_loc_btn[3].size = 1; + } + sc->sc_ibuf = malloc(sc->sc_isize, M_USB, M_NOWAIT); if (!sc->sc_ibuf) { printf("%s: no memory\n", device_get_nameunit(sc->sc_dev)); Index: usbdevs =================================================================== RCS file: /home/freebsd/CVS/src/sys/dev/usb/usbdevs,v retrieving revision 1.328.2.21.2.1 diff -u -r1.328.2.21.2.1 usbdevs --- usbdevs 25 Nov 2008 02:59:29 -0000 1.328.2.21.2.1 +++ usbdevs 25 Nov 2008 18:53:29 -0000 @@ -1664,6 +1664,7 @@ product MICROSOFT MN110 0x007a 10/100 USB NIC product MICROSOFT WLINTELLIMOUSE 0x008c Wireless Optical IntelliMouse product MICROSOFT WLNOTEBOOK 0x00b9 Wireless Optical Mouse (Model 1023) +product MICROSOFT COMFORT3000 0x00d1 Comfort Optical Mouse 3000 (Model 1043) product MICROSOFT WLNOTEBOOK2 0x00e1 Wireless Optical Mouse 3000 (Model 1056) product MICROSOFT WLNOTEBOOK3 0x00d2 Wireless Optical Mouse 3000 (Model 1049) product MICROSOFT WLUSBMOUSE 0x00b9 Wireless USB Mouse From vova at fbsd.ru Wed Feb 4 00:36:31 2009 From: vova at fbsd.ru (Vladimir Grebenschikov) Date: Wed Feb 4 00:36:37 2009 Subject: USB2 - umass problem Message-ID: <1233734352.1767.55.camel@localhost> Hi USB2 team, thank you for really big effort on improving FreeBSD usb stack. I've tried it and found that ums, ubt, ukbd just work. u3g card was detected ohci0: mem 0x88000000-0x88000fff irq 16 at device 0.0 on cardbus0 ohci0: [ITHREAD] usbus5: on ohci0 usbus5: 12Mbps Full Speed USB v1.0 ohci1: mem 0x88001000-0x88001fff irq 16 at device 0.1 on cardbus0 ohci1: [ITHREAD] ugen5.1: at usbus5 ushub6: on usbus5 usbus6: on ohci1 usbus6: 12Mbps Full Speed USB v1.0 ugen6.1: at usbus6 ushub7: on usbus6 ushub6: 1 port with 1 removable, self powered ushub7: 1 port with 1 removable, self powered ugen5.2: at usbus5 u3g0: on usbus5 u3g1: on usbus5 u3g2: on usbus5 By some reason devfs semantic was changed: Instead of /dev/cuaU0.[0-2] and /dev/ttyU0.[0-2], I've get /dev/cuaU[0-2] /dev/ttyU[0-2] and! /dev/cuau1 /dev/ttyu1 What is reason for such change (additional port with lowercase 'u' and U[0-2] instead of more logical U0.[0-2]) ? Excellent news is that I've successfully removed PCMCI card with u3g USB controller from notebook and have no panic as it was with old USB stack. By some reason connection was failed but chat with modem was ok. Will try again. Simple umass device (WD external disk) works fine, but integrated to doc-station card-reader failed: First time card insertion, two umass devices appeared, both just do not work: ugen4.4: at usbus4 umass0: on usbus4 umass0: SCSI over Bulk-Only; quirks = 0x0000 umass0:5:0:-1: Attached to scbus5 (probe0:umass-sim0:0:0:0): TEST UNIT READY. CDB: 0 0 0 0 0 0 (probe0:umass-sim0:0:0:0): CAM Status: SCSI Status Error (probe0:umass-sim0:0:0:0): SCSI Status: Check Condition (probe0:umass-sim0:0:0:0): NOT READY asc:3a,0 (probe0:umass-sim0:0:0:0): Medium not present (probe0:umass-sim0:0:0:0): Unretryable error da0 at umass-sim0 bus 0 target 0 lun 0 da0: Removable Direct Access SCSI-0 device da0: 40.000MB/s transfers da0: Attempt to query device size failed: NOT READY, Medium not present (probe0:umass-sim0:0:0:1): TEST UNIT READY. CDB: 0 20 0 0 0 0 (probe0:umass-sim0:0:0:1): CAM Status: SCSI Status Error (probe0:umass-sim0:0:0:1): SCSI Status: Check Condition (probe0:umass-sim0:0:0:1): NOT READY asc:3a,0 (probe0:umass-sim0:0:0:1): Medium not present (probe0:umass-sim0:0:0:1): Unretryable error da1 at umass-sim0 bus 0 target 0 lun 1 da1: Removable Direct Access SCSI-0 device da1: 40.000MB/s transfers da1: Attempt to query device size failed: NOT READY, Medium not present Second time - a bit better, second device read correct card label, but still failed on mount: ugen4.4: at usbus4 umass0: on usbus4 umass0: SCSI over Bulk-Only; quirks = 0x0000 umass0:5:0:-1: Attached to scbus5 (probe0:umass-sim0:0:0:0): TEST UNIT READY. CDB: 0 0 0 0 0 0 (probe0:umass-sim0:0:0:0): CAM Status: SCSI Status Error (probe0:umass-sim0:0:0:0): SCSI Status: Check Condition (probe0:umass-sim0:0:0:0): UNIT ATTENTION asc:28,0 (probe0:umass-sim0:0:0:0): Not ready to ready change, medium may have changed (probe0:umass-sim0:0:0:0): Retrying Command (per Sense Data) da0 at umass-sim0 bus 0 target 0 lun 0 da0: Removable Direct Access SCSI-0 device da0: 40.000MB/s transfers da0: 980MB (2007040 512 byte sectors: 64H 32S/T 980C) (probe0:umass-sim0:0:0:1): TEST UNIT READY. CDB: 0 20 0 0 0 0 (probe0:umass-sim0:0:0:1): CAM Status: SCSI Status Error (probe0:umass-sim0:0:0:1): SCSI Status: Check Condition (probe0:umass-sim0:0:0:1): NOT READY asc:3a,0 (probe0:umass-sim0:0:0:1): Medium not present (probe0:umass-sim0:0:0:1): Unretryable error da1 at umass-sim0 bus 0 target 0 lun 1 da1: Removable Direct Access SCSI-0 device da1: 40.000MB/s transfers da1: Attempt to query device size failed: NOT READY, Medium not present GEOM_LABEL: Label for provider da0s1 is label/e60mmc. # /sbin/mount -t msdosfs /dev/da0s1 /mnt mount_msdosfs: /dev/da0s1: Input/output error # and dmesg has lots of: (da0:umass-sim0:0:0:0): MEDIUM ERROR asc:11,0 (da0:umass-sim0:0:0:0): Unrecovered read error (da0:umass-sim0:0:0:0): Retrying Command (per Sense Data) (da0:umass-sim0:0:0:0): READ(10). CDB: 28 0 0 0 8 80 0 0 10 0 (da0:umass-sim0:0:0:0): CAM Status: SCSI Status Error (da0:umass-sim0:0:0:0): SCSI Status: Check Condition (da0:umass-sim0:0:0:0): MEDIUM ERROR asc:11,0 (da0:umass-sim0:0:0:0): Unrecovered read error (da0:umass-sim0:0:0:0): Retrying Command (per Sense Data) (da0:umass-sim0:0:0:0): READ(10). CDB: 28 0 0 0 8 80 0 0 10 0 (da0:umass-sim0:0:0:0): CAM Status: SCSI Status Error (da0:umass-sim0:0:0:0): SCSI Status: Check Condition (da0:umass-sim0:0:0:0): MEDIUM ERROR asc:11,0 (da0:umass-sim0:0:0:0): Unrecovered read error (da0:umass-sim0:0:0:0): Retrying Command (per Sense Data) (da0:umass-sim0:0:0:0): READ(10). CDB: 28 0 0 0 8 80 0 0 10 0 (da0:umass-sim0:0:0:0): CAM Status: SCSI Status Error (da0:umass-sim0:0:0:0): SCSI Status: Check Condition # usbconfig ugen0.1: at usbus0, cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON ugen1.1: at usbus1, cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON ugen2.1: at usbus2, cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON ugen3.1: at usbus3, cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON ugen4.1: at usbus4, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=ON ugen4.2: at usbus4, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=SAVE ugen4.3: at usbus4, cfg=0 md=HOST spd=LOW (1.5Mbps) pwr=ON ugen3.2: at usbus3, cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON ugen3.3: at usbus3, cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON ugen4.4: <2228 SMSC> at usbus4, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=ON # With u3gcard: ... ugen5.1: at usbus5, cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON ugen6.1: at usbus6, cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON ugen5.2: at usbus5, cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON Any hints regarding issues above ? Side question, is there any way to ask usbconfig driver that attached to every device (as it was with usbdevs -d) ? # uname -a FreeBSD vbook.fbsd.ru 8.0-CURRENT FreeBSD 8.0-CURRENT #2: Mon Feb 2 16:46:22 MSK 2009 root@vbook.fbsd.ru:/usr/obj/usr/src/sys/VBOOK i386 -- Vladimir B. Grebenschikov vova@fbsd.ru From hselasky at c2i.net Wed Feb 4 01:42:09 2009 From: hselasky at c2i.net (Hans Petter Selasky) Date: Wed Feb 4 01:42:22 2009 Subject: USB2 - umass problem In-Reply-To: <1233734352.1767.55.camel@localhost> References: <1233734352.1767.55.camel@localhost> Message-ID: <200902041044.27663.hselasky@c2i.net> Hi, On Wednesday 04 February 2009, Vladimir Grebenschikov wrote: > Hi > > > By some reason devfs semantic was changed: > Instead of /dev/cuaU0.[0-2] and /dev/ttyU0.[0-2], I've get > /dev/cuaU[0-2] /dev/ttyU[0-2] and! /dev/cuau1 /dev/ttyu1 > What is reason for such change (additional port with lowercase 'u' and > U[0-2] instead of more logical U0.[0-2]) ? It is because we are attaching drivers per interface instead of per device. A new modem unit is allocated every time we find a modem, simply put. If the modem has multiple instances in an interface, /dev/cuaU0.[0...] will be created. Else /dev/cuaU... . > > Excellent news is that I've successfully removed PCMCI card with u3g USB > controller from notebook and have no panic as it was with old USB > stack. Great! > > By some reason connection was failed but chat with modem was ok. Will > try again. > > Simple umass device (WD external disk) works fine, but > integrated to doc-station card-reader failed: > > First time card insertion, two umass devices appeared, both just do not > work: > > ugen4.4: at usbus4 > umass0: on usbus4 > umass0: SCSI over Bulk-Only; quirks = 0x0000 > umass0:5:0:-1: Attached to scbus5 > (probe0:umass-sim0:0:0:0): TEST UNIT READY. CDB: 0 0 0 0 0 0 > (probe0:umass-sim0:0:0:0): CAM Status: SCSI Status Error > (probe0:umass-sim0:0:0:0): SCSI Status: Check Condition > (probe0:umass-sim0:0:0:0): NOT READY asc:3a,0 > (probe0:umass-sim0:0:0:0): Medium not present > (probe0:umass-sim0:0:0:0): Unretryable error > da0 at umass-sim0 bus 0 target 0 lun 0 > da0: Removable Direct Access SCSI-0 device > da0: 40.000MB/s transfers > da0: Attempt to query device size failed: NOT READY, Medium not present Have you tried "cat /dev/null > /dev/da0", to refresh the label on the disk? NOTE: /dev/null is not /dev/zero > da1 at umass-sim0 bus 0 target 0 lun 1 > da1: Removable Direct Access SCSI-0 device > da1: 40.000MB/s transfers > da1: Attempt to query device size failed: NOT READY, Medium not present Same with "da1" > > Second time - a bit better, second device read correct card label, but > still failed on mount: Maybe your device needs a quirk, because it hangs on one of the issues SCSI commands. Have you looked at: http://wiki.freebsd.org/USB > > # usbconfig > ugen0.1: at usbus0, cfg=0 md=HOST spd=FULL (12Mbps) > pwr=ON ugen1.1: at usbus1, cfg=0 md=HOST spd=FULL > (12Mbps) pwr=ON ugen2.1: at usbus2, cfg=0 md=HOST > spd=FULL (12Mbps) pwr=ON ugen3.1: at usbus3, cfg=0 > md=HOST spd=FULL (12Mbps) pwr=ON ugen4.1: at usbus4, > cfg=0 md=HOST spd=HIGH (480Mbps) pwr=ON ugen4.2: at > usbus4, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=SAVE ugen4.3: 5-Button Mouse with IntelliEye(TM) Microsoft> at usbus4, cfg=0 md=HOST > spd=LOW (1.5Mbps) pwr=ON ugen3.2: at usbus3, cfg=0 > md=HOST spd=FULL (12Mbps) pwr=ON ugen3.3: STMicroelectronics> at usbus3, cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON > ugen4.4: <2228 SMSC> at usbus4, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=ON # > > With u3gcard: > ... > ugen5.1: at usbus5, cfg=0 md=HOST spd=FULL (12Mbps) > pwr=ON ugen6.1: at usbus6, cfg=0 md=HOST spd=FULL > (12Mbps) pwr=ON ugen5.2: at usbus5, > cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON > > > Any hints regarding issues above ? > > Side question, is there any way to ask usbconfig driver that attached to > every device (as it was with usbdevs -d) ? No, but you can try the following command which gives a nice overview: devinfo > > # uname -a > FreeBSD vbook.fbsd.ru 8.0-CURRENT FreeBSD 8.0-CURRENT #2: Mon Feb 2 > 16:46:22 MSK 2009 root@vbook.fbsd.ru:/usr/obj/usr/src/sys/VBOOK i386 --HPS From vova at fbsd.ru Wed Feb 4 01:58:09 2009 From: vova at fbsd.ru (Vladimir Grebenschikov) Date: Wed Feb 4 01:58:20 2009 Subject: USB2 - umass problem In-Reply-To: <200902041044.27663.hselasky@c2i.net> References: <1233734352.1767.55.camel@localhost> <200902041044.27663.hselasky@c2i.net> Message-ID: <1233741482.1767.120.camel@localhost> On Wed, 2009-02-04 at 10:44 +0100, Hans Petter Selasky wrote: > > By some reason devfs semantic was changed: > > Instead of /dev/cuaU0.[0-2] and /dev/ttyU0.[0-2], I've get > > /dev/cuaU[0-2] /dev/ttyU[0-2] and! /dev/cuau1 /dev/ttyu1 > > What is reason for such change (additional port with lowercase 'u' and > > U[0-2] instead of more logical U0.[0-2]) ? > > It is because we are attaching drivers per interface instead of per device. A > new modem unit is allocated every time we find a modem, simply put. If the > modem has multiple instances in an interface, /dev/cuaU0.[0...] will be > created. Else /dev/cuaU... . What about /dev/cuau1 /dev/ttyu1 ? -- Vladimir B. Grebenschikov vova@fbsd.ru From vova at fbsd.ru Wed Feb 4 02:11:31 2009 From: vova at fbsd.ru (Vladimir Grebenschikov) Date: Wed Feb 4 02:11:43 2009 Subject: USB2 - umass problem In-Reply-To: <200902041044.27663.hselasky@c2i.net> References: <1233734352.1767.55.camel@localhost> <200902041044.27663.hselasky@c2i.net> Message-ID: <1233742285.1767.142.camel@localhost> On Wed, 2009-02-04 at 10:44 +0100, Hans Petter Selasky wrote: > > Simple umass device (WD external disk) works fine, but > > integrated to doc-station card-reader failed: > > > > First time card insertion, two umass devices appeared, both just do not > > work: > > > > ugen4.4: at usbus4 > > umass0: on usbus4 > > umass0: SCSI over Bulk-Only; quirks = 0x0000 > > umass0:5:0:-1: Attached to scbus5 > > (probe0:umass-sim0:0:0:0): TEST UNIT READY. CDB: 0 0 0 0 0 0 > > (probe0:umass-sim0:0:0:0): CAM Status: SCSI Status Error > > (probe0:umass-sim0:0:0:0): SCSI Status: Check Condition > > (probe0:umass-sim0:0:0:0): NOT READY asc:3a,0 > > (probe0:umass-sim0:0:0:0): Medium not present > > (probe0:umass-sim0:0:0:0): Unretryable error > > da0 at umass-sim0 bus 0 target 0 lun 0 > > da0: Removable Direct Access SCSI-0 device > > da0: 40.000MB/s transfers > > da0: Attempt to query device size failed: NOT READY, Medium not present > > Have you tried "cat /dev/null > /dev/da0", to refresh the label on the disk? > NOTE: /dev/null is not /dev/zero > > > da1 at umass-sim0 bus 0 target 0 lun 1 > > da1: Removable Direct Access SCSI-0 device > > da1: 40.000MB/s transfers > > da1: Attempt to query device size failed: NOT READY, Medium not present > > Same with "da1" > > > > > Second time - a bit better, second device read correct card label, but > > still failed on mount: > > Maybe your device needs a quirk, because it hangs on one of the issues SCSI > commands. Have you looked at: > > http://wiki.freebsd.org/USB Probably, did not tried yet, but old usb stack works as expected, did all usb1 quircks imported to usb2 ? -- Vladimir B. Grebenschikov vova@fbsd.ru From hselasky at c2i.net Wed Feb 4 02:18:17 2009 From: hselasky at c2i.net (Hans Petter Selasky) Date: Wed Feb 4 02:18:22 2009 Subject: USB2 - umass problem In-Reply-To: <1233742285.1767.142.camel@localhost> References: <1233734352.1767.55.camel@localhost> <200902041044.27663.hselasky@c2i.net> <1233742285.1767.142.camel@localhost> Message-ID: <200902041120.40833.hselasky@c2i.net> On Wednesday 04 February 2009, Vladimir Grebenschikov wrote: > > Probably, did not tried yet, > but old usb stack works as expected, did all usb1 quircks imported to > usb2 ? Yes, all UMASS quirks should have been imported. --HPS From hselasky at c2i.net Wed Feb 4 02:24:56 2009 From: hselasky at c2i.net (Hans Petter Selasky) Date: Wed Feb 4 02:25:08 2009 Subject: USB2 - umass problem In-Reply-To: <1233741482.1767.120.camel@localhost> References: <1233734352.1767.55.camel@localhost> <200902041044.27663.hselasky@c2i.net> <1233741482.1767.120.camel@localhost> Message-ID: <200902041127.20424.hselasky@c2i.net> On Wednesday 04 February 2009, Vladimir Grebenschikov wrote: > On Wed, 2009-02-04 at 10:44 +0100, Hans Petter Selasky wrote: > > > By some reason devfs semantic was changed: > > > Instead of /dev/cuaU0.[0-2] and /dev/ttyU0.[0-2], I've get > > > /dev/cuaU[0-2] /dev/ttyU[0-2] and! /dev/cuau1 /dev/ttyu1 > > > What is reason for such change (additional port with lowercase 'u' and > > > U[0-2] instead of more logical U0.[0-2]) ? > > > > It is because we are attaching drivers per interface instead of per > > device. A new modem unit is allocated every time we find a modem, simply > > put. If the modem has multiple instances in an interface, > > /dev/cuaU0.[0...] will be created. Else /dev/cuaU... . > > What about /dev/cuau1 /dev/ttyu1 ? TTYs follow the same naming convention like the cuaUxx . If the modem has got one modem in each interface and three interfaces: /dev/cuaU0 /dev/ttyU0 /dev/cuaU1 /dev/ttyU1 /dev/cuaU2 /dev/ttyU2 If the modem has got three modems in one interface: /dev/cuaU0.0 /dev/ttyU0.0 /dev/cuaU0.1 /dev/ttyU0.1 /dev/cuaU0.2 /dev/ttyU0.2 How this is configured is decided by the USB device manufacturer. --HPS From bst2006 at dva.dyndns.org Wed Feb 4 04:21:47 2009 From: bst2006 at dva.dyndns.org (Boris S.) Date: Wed Feb 4 04:21:53 2009 Subject: usb/125631: [usb][ums] kernel panic during bootup while 'Logitech USB receiver' (Logitech RX650 wireless mouse) is connected In-Reply-To: <200807151030.m6FAU0KL074679@freefall.freebsd.org> References: <200807151030.m6FAU0KL074679@freefall.freebsd.org> Message-ID: <49898442.7070904@dva.dyndns.org> This bug has been fixed with the new USB2 stack. Tested under FreeBSD-8 (current). PR can be closed. From bst2006 at dva.dyndns.org Wed Feb 4 04:30:03 2009 From: bst2006 at dva.dyndns.org (Boris S.) Date: Wed Feb 4 04:30:09 2009 Subject: usb/125631: [usb][ums] kernel panic during bootup while 'Logitech USB receiver' (Logitech RX650 wireless mouse) is connected Message-ID: <200902041230.n14CU3TR037465@freefall.freebsd.org> The following reply was made to PR usb/125631; it has been noted by GNATS. From: "Boris S." To: FreeBSD-gnats-submit@FreeBSD.org, freebsd-usb@FreeBSD.org Cc: "Boris S." Subject: Re: usb/125631: [usb][ums] kernel panic during bootup while 'Logitech USB receiver' (Logitech RX650 wireless mouse) is connected Date: Wed, 04 Feb 2009 13:04:18 +0100 This bug has been fixed with the new USB2 stack. Tested under FreeBSD-8 (current). PR can be closed. From jhb at freebsd.org Wed Feb 4 06:26:48 2009 From: jhb at freebsd.org (John Baldwin) Date: Wed Feb 4 06:26:55 2009 Subject: USB2 - umass problem In-Reply-To: <1233741482.1767.120.camel@localhost> References: <1233734352.1767.55.camel@localhost> <200902041044.27663.hselasky@c2i.net> <1233741482.1767.120.camel@localhost> Message-ID: <200902040922.16882.jhb@freebsd.org> On Wednesday 04 February 2009 4:58:02 am Vladimir Grebenschikov wrote: > On Wed, 2009-02-04 at 10:44 +0100, Hans Petter Selasky wrote: > > > > By some reason devfs semantic was changed: > > > Instead of /dev/cuaU0.[0-2] and /dev/ttyU0.[0-2], I've get > > > /dev/cuaU[0-2] /dev/ttyU[0-2] and! /dev/cuau1 /dev/ttyu1 > > > What is reason for such change (additional port with lowercase 'u' and > > > U[0-2] instead of more logical U0.[0-2]) ? > > > > It is because we are attaching drivers per interface instead of per device. A > > new modem unit is allocated every time we find a modem, simply put. If the > > modem has multiple instances in an interface, /dev/cuaU0.[0...] will be > > created. Else /dev/cuaU... . > > What about /dev/cuau1 /dev/ttyu1 ? You have a uart1 device. -- John Baldwin From vova at fbsd.ru Wed Feb 4 06:45:27 2009 From: vova at fbsd.ru (Vladimir Grebenschikov) Date: Wed Feb 4 06:45:33 2009 Subject: USB2 - umass problem In-Reply-To: <200902040922.16882.jhb@freebsd.org> References: <1233734352.1767.55.camel@localhost> <200902041044.27663.hselasky@c2i.net> <1233741482.1767.120.camel@localhost> <200902040922.16882.jhb@freebsd.org> Message-ID: <1233758721.1811.148.camel@localhost> On Wed, 2009-02-04 at 09:22 -0500, John Baldwin wrote: > On Wednesday 04 February 2009 4:58:02 am Vladimir Grebenschikov wrote: > > On Wed, 2009-02-04 at 10:44 +0100, Hans Petter Selasky wrote: > > > > > > By some reason devfs semantic was changed: > > > > Instead of /dev/cuaU0.[0-2] and /dev/ttyU0.[0-2], I've get > > > > /dev/cuaU[0-2] /dev/ttyU[0-2] and! /dev/cuau1 /dev/ttyu1 > > > > What is reason for such change (additional port with lowercase 'u' and > > > > U[0-2] instead of more logical U0.[0-2]) ? > > > > > > It is because we are attaching drivers per interface instead of per > device. A > > > new modem unit is allocated every time we find a modem, simply put. If the > > > modem has multiple instances in an interface, /dev/cuaU0.[0...] will be > > > created. Else /dev/cuaU... . > > > > What about /dev/cuau1 /dev/ttyu1 ? > > You have a uart1 device. Ahh, ok, now I understand, thanks. -- Vladimir B. Grebenschikov vova@fbsd.ru From imp at bsdimp.com Wed Feb 4 07:59:52 2009 From: imp at bsdimp.com (M. Warner Losh) Date: Wed Feb 4 07:59:58 2009 Subject: USB2 - umass problem In-Reply-To: <200902041044.27663.hselasky@c2i.net> References: <1233734352.1767.55.camel@localhost> <200902041044.27663.hselasky@c2i.net> Message-ID: <20090204.085606.1630229139.imp@bsdimp.com> In message: <200902041044.27663.hselasky@c2i.net> Hans Petter Selasky writes: : Hi, : : On Wednesday 04 February 2009, Vladimir Grebenschikov wrote: : > Hi : > : > : > By some reason devfs semantic was changed: : > Instead of /dev/cuaU0.[0-2] and /dev/ttyU0.[0-2], I've get : > /dev/cuaU[0-2] /dev/ttyU[0-2] and! /dev/cuau1 /dev/ttyu1 : > What is reason for such change (additional port with lowercase 'u' and : > U[0-2] instead of more logical U0.[0-2]) ? : : It is because we are attaching drivers per interface instead of per device. A : new modem unit is allocated every time we find a modem, simply put. If the : modem has multiple instances in an interface, /dev/cuaU0.[0...] will be : created. Else /dev/cuaU... . Generally, we try not to change the details of how a device attaches /dev entries from release to release. Why the change? Also to Vladimir, Are you sure that the 'u' devices are created with the USB modem? They should only be created for uart devices... Warner From hselasky at c2i.net Wed Feb 4 08:31:01 2009 From: hselasky at c2i.net (Hans Petter Selasky) Date: Wed Feb 4 08:31:13 2009 Subject: [was: USB2 - umass problem] U3G modem unit number changes In-Reply-To: <20090204.085606.1630229139.imp@bsdimp.com> References: <1233734352.1767.55.camel@localhost> <200902041044.27663.hselasky@c2i.net> <20090204.085606.1630229139.imp@bsdimp.com> Message-ID: <200902041733.23389.hselasky@c2i.net> Hi, On Wednesday 04 February 2009, M. Warner Losh wrote: > Why the change? Because u3g2.c is attaching to an USB interface and not the whole USB device. This is to allow other drivers to hook on the other interfaces. If you want to have exactly the same numbering like before, then the U3G interface driver instances on the same USB device need to peek at eachother to figure out the correct unit and sub-unit number. > > Also to Vladimir, Are you sure that the 'u' devices are created with > the USB modem? They should only be created for uart devices... --HPS From thompsa at FreeBSD.org Wed Feb 4 09:06:30 2009 From: thompsa at FreeBSD.org (Andrew Thompson) Date: Wed Feb 4 09:06:35 2009 Subject: [was: USB2 - umass problem] U3G modem unit number changes In-Reply-To: <200902041733.23389.hselasky@c2i.net> References: <1233734352.1767.55.camel@localhost> <200902041044.27663.hselasky@c2i.net> <20090204.085606.1630229139.imp@bsdimp.com> <200902041733.23389.hselasky@c2i.net> Message-ID: <20090204164305.GA77912@citylink.fud.org.nz> On Wed, Feb 04, 2009 at 05:33:22PM +0100, Hans Petter Selasky wrote: > Hi, > > On Wednesday 04 February 2009, M. Warner Losh wrote: > > > Why the change? > > Because u3g2.c is attaching to an USB interface and not the whole USB device. > This is to allow other drivers to hook on the other interfaces. u3g2 should claim the other interfaces in the one attachment and use the same tty semantics as oldusb u3g. Andrew From hsu at bbnetworks.net Wed Feb 4 09:26:31 2009 From: hsu at bbnetworks.net (Heikki Suonsivu) Date: Wed Feb 4 09:26:37 2009 Subject: kern/107446: problems with usb and fw disks In-Reply-To: <200902022051.n12KpShb045098@freefall.freebsd.org> References: <200902022051.n12KpShb045098@freefall.freebsd.org> Message-ID: <4989C952.6080701@bbnetworks.net> I have not seen the same errors lately, though I have dropped using USB disks to just random occasional use, so I do not know if this is still a problem or not. gavin@FreeBSD.org wrote: > Old Synopsis: [umass] umass problems (usb and fw disks) > New Synopsis: problems with usb and fw disks > > State-Changed-From-To: open->feedback > State-Changed-By: gavin > State-Changed-When: Mon Feb 2 20:46:56 UTC 2009 > State-Changed-Why: > To submitter: Sorry this PR has sat so long without a response. > I wonder, are you able to provide two full copies of any output > from the kernel (/var/log/messages), one while using these disks > as firewire disks, and the other while using it as a USB disk? > Also, if the machine panics, are you able to get a backtrace in > both cases ? (you may need to recompile your kernel with the > Kernel Debugger, see > http://www.freebsd.org/doc/en/books/developers-handbook/kerneldebug.html > for details). > > Thanks! > > > Responsible-Changed-From-To: freebsd-usb->gavin > Responsible-Changed-By: gavin > Responsible-Changed-When: Mon Feb 2 20:46:56 UTC 2009 > Responsible-Changed-Why: > Not USB specific. Track. > > http://www.freebsd.org/cgi/query-pr.cgi?pr=107446 From hselasky at c2i.net Wed Feb 4 09:30:14 2009 From: hselasky at c2i.net (Hans Petter Selasky) Date: Wed Feb 4 09:30:26 2009 Subject: [was: USB2 - umass problem] U3G modem unit number changes In-Reply-To: <200902041733.23389.hselasky@c2i.net> References: <1233734352.1767.55.camel@localhost> <20090204.085606.1630229139.imp@bsdimp.com> <200902041733.23389.hselasky@c2i.net> Message-ID: <200902041832.36833.hselasky@c2i.net> Hi Vladimir, You can try the following patch if you want: http://perforce.freebsd.org/chv.cgi?CH=157145 You probably need to apply by hand, but if you can wait a couple of days, this will be in -current . --HPS From vova at fbsd.ru Wed Feb 4 14:32:10 2009 From: vova at fbsd.ru (Vladimir Grebenschikov) Date: Wed Feb 4 14:32:23 2009 Subject: USB2 - umass problem In-Reply-To: <20090204.085606.1630229139.imp@bsdimp.com> References: <1233734352.1767.55.camel@localhost> <200902041044.27663.hselasky@c2i.net> <20090204.085606.1630229139.imp@bsdimp.com> Message-ID: <1233786661.2821.5.camel@localhost> On Wed, 2009-02-04 at 08:56 -0700, M. Warner Losh wrote: > In message: <200902041044.27663.hselasky@c2i.net> > Hans Petter Selasky writes: > : Hi, > : > : On Wednesday 04 February 2009, Vladimir Grebenschikov wrote: > : > Hi > : > > : > > : > By some reason devfs semantic was changed: > : > Instead of /dev/cuaU0.[0-2] and /dev/ttyU0.[0-2], I've get > : > /dev/cuaU[0-2] /dev/ttyU[0-2] and! /dev/cuau1 /dev/ttyu1 > : > What is reason for such change (additional port with lowercase 'u' and > : > U[0-2] instead of more logical U0.[0-2]) ? > : > : It is because we are attaching drivers per interface instead of per device. A > : new modem unit is allocated every time we find a modem, simply put. If the > : modem has multiple instances in an interface, /dev/cuaU0.[0...] will be > : created. Else /dev/cuaU... . > > Generally, we try not to change the details of how a device attaches > /dev entries from release to release. Why the change? > > Also to Vladimir, Are you sure that the 'u' devices are created with > the USB modem? They should only be created for uart devices... Yes, it is uart. > Warner -- Vladimir B. Grebenschikov vova@fbsd.ru From alfred at freebsd.org Thu Feb 5 21:12:30 2009 From: alfred at freebsd.org (Alfred Perlstein) Date: Thu Feb 5 21:12:36 2009 Subject: HEADSUP usb2/usb4bsd to become default in GENERIC Message-ID: <20090206045349.GQ78804@elvis.mu.org> Hello -current and -usb. We are in the final stages of bringing in the new usb stack. Features include: SMP, better device support, speed increases. We hope to make it in for 8.0. It will really take a unified effort to make this all work and I look forward to all contributors input. We have a few large steps ahead of us and I wanted to lay out the schedule so that people understand what is coming and what to expect. At this point we expect there to be no style or changes in usb2 that are not bugfixes until Phase 3 "Hand off". The reason for this is to prevent bugs from creeping in and allow the maintainer to focus 100% on bugs and feature parity with the oldusb stack. Here is the plan and timeline: Phase 1) Make usb2 the default, by enabling it in GENERIC. * Sunday 8 Feb 2009 -- Toggle the usb2 knob in GENERIC - Add all the usb2 options to NOTES, including commented documentation about recommended usb2 'sets' of options, and the usual NOTES-based hints about the options. - Update GENERIC to use usb2 device names. - Bump __FreeBSD_version and edit UPDATING to note usb2 is now the default. - Verify that it still possible to use the old usb code as a fallback, until we are ready to detach and remove it from /head * Sunday 22 Feb 2009 -- Go through quirks in old-usb code and port over any remaining bits to usb2 - Lock the oldusb code for 2 weeks, until the next usb2 checkpoint, to verify usb2 is a viable replacement without having to keep chasing a moving oldusb target. Phase 2) Removing the oldusb code. * Sunday 15 Mar 2009 -- usb2 bug busting weekend - Go through the open usb2 problem reports, and see if there are any usb2 blocker bugs that need fixing. - If the bug hunt shows we are ready to do away with oldusb, unlink the old usb code from the build, but leave it in for a few more days. * Sunday 22 Mar 2009 -- remove oldusb code. - old usb code will be removed. Phase 3) Hand-off. * Sunday 29 Mar 2009 -- usb2 hand over to src-committers - The switch from a private Hans-only repository to the main subversion tree. - At this point, the usb2 is handed over to the src-committers and Hans has to go through a mentor/committer before committing changes. Thank you! -- - Alfred Perlstein From sobomax at FreeBSD.org Fri Feb 6 01:50:24 2009 From: sobomax at FreeBSD.org (Maxim Sobolev) Date: Fri Feb 6 01:50:31 2009 Subject: HEADSUP usb2/usb4bsd to become default in GENERIC In-Reply-To: <20090206045349.GQ78804@elvis.mu.org> References: <20090206045349.GQ78804@elvis.mu.org> Message-ID: <498C013B.4000405@FreeBSD.org> Alfred Perlstein wrote: > - Update GENERIC to use usb2 device names. Wasn't there a plan to rename usb2 devices to match oldusb names (where applicable) once oldusb had been killed? I don't see it in the list. -Maxim From imp at bsdimp.com Fri Feb 6 07:21:46 2009 From: imp at bsdimp.com (M. Warner Losh) Date: Fri Feb 6 07:21:59 2009 Subject: HEADSUP usb2/usb4bsd to become default in GENERIC In-Reply-To: <20090206045349.GQ78804@elvis.mu.org> References: <20090206045349.GQ78804@elvis.mu.org> Message-ID: <20090206.081901.1923806177.imp@bsdimp.com> Doesn't the busdma issue need to be solved before we do this? usb2 currently doesn't work if you have memory above 4GB due to this issue. I thought we tagged it as a show stopper for making it the default. Warner In message: <20090206045349.GQ78804@elvis.mu.org> Alfred Perlstein writes: : Hello -current and -usb. : : We are in the final stages of bringing in the new usb : stack. : : Features include: SMP, better device support, speed increases. : : We hope to make it in for 8.0. It will really take a unified effort : to make this all work and I look forward to all contributors input. : : We have a few large steps ahead of us and I wanted to lay out the : schedule so that people understand what is coming and what to expect. : : At this point we expect there to be no style or changes in usb2 : that are not bugfixes until Phase 3 "Hand off". The reason for : this is to prevent bugs from creeping in and allow the maintainer : to focus 100% on bugs and feature parity with the oldusb stack. : : Here is the plan and timeline: : : Phase 1) Make usb2 the default, by enabling it in GENERIC. : : * Sunday 8 Feb 2009 -- Toggle the usb2 knob in GENERIC : : - Add all the usb2 options to NOTES, including commented : documentation about recommended usb2 'sets' of options, : and the usual NOTES-based hints about the options. : : - Update GENERIC to use usb2 device names. : : - Bump __FreeBSD_version and edit UPDATING to note usb2 is now the : default. : : - Verify that it still possible to use the old usb code as a : fallback, until we are ready to detach and remove it from /head : : * Sunday 22 Feb 2009 -- Go through quirks in old-usb code and port : over any remaining bits to usb2 : : - Lock the oldusb code for 2 weeks, until the next usb2 : checkpoint, to verify usb2 is a viable replacement without : having to keep chasing a moving oldusb target. : : Phase 2) Removing the oldusb code. : : * Sunday 15 Mar 2009 -- usb2 bug busting weekend : : - Go through the open usb2 problem reports, and see if there are : any usb2 blocker bugs that need fixing. : : - If the bug hunt shows we are ready to do away with oldusb, : unlink the old usb code from the build, but leave it in for : a few more days. : : * Sunday 22 Mar 2009 -- remove oldusb code. : : - old usb code will be removed. : : Phase 3) Hand-off. : : * Sunday 29 Mar 2009 -- usb2 hand over to src-committers : : - The switch from a private Hans-only repository to the main : subversion tree. : : - At this point, the usb2 is handed over to the src-committers : and Hans has to go through a mentor/committer before committing : changes. : : Thank you! : : -- : - Alfred Perlstein : _______________________________________________ : freebsd-current@freebsd.org mailing list : http://lists.freebsd.org/mailman/listinfo/freebsd-current : To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" : From mike at sentex.net Fri Feb 6 13:59:29 2009 From: mike at sentex.net (Mike Tancsa) Date: Fri Feb 6 13:59:36 2009 Subject: eToken and USB2 (ugen issue?) Message-ID: <200902062126.n16LQ0Gc013030@lava.sentex.ca> I was going to try out some of our apps on HEAD with USB2 kernel. dmesg shows ugen0.3: at usbus0 however, there is no ugen device ? 0[freebsd-current2]# ls -l /dev/u* lrwxr-xr-x 1 root wheel 6 Feb 6 15:34 /dev/urandom -> random crwxrwxrwx 1 root operator 0, 81 Feb 6 15:34 /dev/usb 0[freebsd-current2]# where as on RELENG_7, it comes up as ugen0: on uhub5 0[nanobsd2]# ls -l /dev/ugen0 crw-r--r-- 1 root operator - 0, 100 Feb 2 09:13 /dev/ugen0 0[nanobsd2]# which openct/opensc use to talk to the token. Is there something I need to add to the kernel ? I am using the USB2 kernel definition on AMD64 ---Mike -------------------------------------------------------------------- Mike Tancsa, tel +1 519 651 3400 Sentex Communications, mike@sentex.net Providing Internet since 1994 www.sentex.net Cambridge, Ontario Canada www.sentex.net/mike From mike at sentex.net Fri Feb 6 14:08:37 2009 From: mike at sentex.net (Mike Tancsa) Date: Fri Feb 6 14:08:44 2009 Subject: eToken and USB2 (ugen issue?) In-Reply-To: <200902062126.n16LQ0Gc013030@lava.sentex.ca> References: <200902062126.n16LQ0Gc013030@lava.sentex.ca> Message-ID: <200902062208.n16M8Xkr013205@lava.sentex.ca> At 04:26 PM 2/6/2009, Mike Tancsa wrote: >I was going to try out some of our apps on HEAD with USB2 kernel. > >dmesg shows > >ugen0.3: at usbus0 > >however, there is no ugen device ? > >0[freebsd-current2]# ls -l /dev/u* >lrwxr-xr-x 1 root wheel 6 Feb 6 15:34 /dev/urandom -> random >crwxrwxrwx 1 root operator 0, 81 Feb 6 15:34 /dev/usb >0[freebsd-current2]# > > >where as on RELENG_7, it comes up as > >ugen0: 2.7.195, class 0/0, rev 1.10/1.00, addr 4> on uhub5 >0[nanobsd2]# ls -l /dev/ugen0 >crw-r--r-- 1 root operator - 0, 100 Feb 2 09:13 /dev/ugen0 >0[nanobsd2]# > >which openct/opensc use to talk to the token. > >Is there something I need to add to the kernel ? I am using the >USB2 kernel definition on AMD64 I turned up the debugging and dumped out the following info usbconfig -u 0 -a 2 dump_curr_config_desc ugen0.2: at usbus0, cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON Configuration index 0 bLength = 0x0009 bDescriptorType = 0x0002 wTotalLength = 0x0014 bNumInterfaces = 0x0001 bConfigurationValue = 0x0001 iConfiguration = 0x0000 bmAttributes = 0x0080 bMaxPower = 0x0032 Interface 0 bLength = 0x0009 bDescriptorType = 0x0004 bInterfaceNumber = 0x0000 bAlternateSetting = 0x0000 bNumEndpoints = 0x0000 bInterfaceClass = 0x00ff bInterfaceSubClass = 0x0000 bInterfaceProtocol = 0x0000 iInterface = 0x0000 0[freebsd-current2]# usbconfig -u 0 -a 2 dump_access Global Access: root:operator 0660 ugen0.2: at usbus0, cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON Device Access: Interface 0 Access: 0[freebsd-current2]# ugen0.2: at usbus0 (disconnected) ugen0.2: at usbus0 ushub2: on usbus0 ushub2: 4 ports with 4 removable, self powered ugen0.3: at usbus0 ushub2: at ushub0, port 1, addr 2 (disconnected) ugen0.3: at usbus0 (disconnected) ugen0.2: at usbus0 (disconnected) ugen0.2: at usbus0 ugen_open:157: flag=0x1 ugen_open:157: flag=0x2 ugen_ioctl:1396: cmd=0x4004557e ugen_ioctl:1579: error=-3 ugen_ioctl_post:1977: cmd=0x4004557e ugen_ioctl_post:2178: error=0 ugen_ioctl:1396: cmd=0x40125569 ugen_ioctl:1579: error=-3 ugen_ioctl_post:1977: cmd=0x40125569 ugen_ioctl_post:2178: error=0 ugen_ioctl:1396: cmd=0x41705570 ugen_ioctl:1579: error=-3 ugen_ioctl_post:1977: cmd=0x41705570 ugen_ioctl_post:2178: error=0 ugen_close:187: flag=0x1 ugen_close:201: no FIFOs ugen_close:187: flag=0x2 ugen_close:201: no FIFOs ugen_open:157: flag=0x1 ugen_open:157: flag=0x2 ugen_ioctl:1396: cmd=0x4004557e ugen_ioctl:1579: error=-3 ugen_ioctl_post:1977: cmd=0x4004557e ugen_ioctl_post:2178: error=0 ugen_ioctl:1396: cmd=0x40125569 ugen_ioctl:1579: error=-3 ugen_ioctl_post:1977: cmd=0x40125569 ugen_ioctl_post:2178: error=0 ugen_ioctl:1396: cmd=0x41705570 ugen_ioctl:1579: error=-3 ugen_ioctl_post:1977: cmd=0x41705570 ugen_ioctl_post:2178: error=0 ugen_close:187: flag=0x1 ugen_close:201: no FIFOs ugen_close:187: flag=0x2 ugen_close:201: no FIFOs ugen_open:157: flag=0x1 ugen_open:157: flag=0x2 ugen_ioctl:1396: cmd=0x4004557e ugen_ioctl:1579: error=-3 ugen_ioctl_post:1977: cmd=0x4004557e ugen_ioctl_post:2178: error=0 ugen_ioctl:1396: cmd=0x40125569 ugen_ioctl:1579: error=-3 ugen_ioctl_post:1977: cmd=0x40125569 ugen_ioctl_post:2178: error=0 ugen_ioctl:1396: cmd=0x41705570 ugen_ioctl:1579: error=-3 ugen_ioctl_post:1977: cmd=0x41705570 ugen_ioctl_post:2178: error=0 ugen_close:187: flag=0x1 ugen_close:201: no FIFOs ugen_close:187: flag=0x2 ugen_close:201: no FIFOs ugen_open:157: flag=0x1 ugen_open:157: flag=0x2 ugen_ioctl:1396: cmd=0x4004557e ugen_ioctl:1579: error=-3 ugen_ioctl_post:1977: cmd=0x4004557e ugen_ioctl_post:2178: error=0 ugen_ioctl:1396: cmd=0x40125569 ugen_ioctl:1579: error=-3 ugen_ioctl_post:1977: cmd=0x40125569 ugen_ioctl_post:2178: error=0 ugen_ioctl:1396: cmd=0x41705570 ugen_ioctl:1579: error=-3 ugen_ioctl_post:1977: cmd=0x41705570 ugen_ioctl_post:2178: error=0 ugen_close:187: flag=0x1 ugen_close:201: no FIFOs ugen_close:187: flag=0x2 ugen_close:201: no FIFOs ugen_open:157: flag=0x1 ugen_open:157: flag=0x2 ugen_ioctl:1396: cmd=0x4004557e ugen_ioctl:1579: error=-3 ugen_ioctl_post:1977: cmd=0x4004557e ugen_ioctl_post:2178: error=0 ugen_ioctl:1396: cmd=0x40125569 ugen_ioctl:1579: error=-3 ugen_ioctl_post:1977: cmd=0x40125569 ugen_ioctl_post:2178: error=0 ugen_ioctl:1396: cmd=0x41705570 ugen_ioctl:1579: error=-3 ugen_ioctl_post:1977: cmd=0x41705570 ugen_ioctl_post:2178: error=0 ugen_close:187: flag=0x1 ugen_close:201: no FIFOs ugen_close:187: flag=0x2 ugen_close:201: no FIFOs ugen_open:157: flag=0x1 ugen_open:157: flag=0x2 ugen_ioctl:1396: cmd=0x4004557e ugen_ioctl:1579: error=-3 ugen_ioctl_post:1977: cmd=0x4004557e ugen_ioctl_post:2178: error=0 ugen_ioctl:1396: cmd=0x40125569 ugen_ioctl:1579: error=-3 ugen_ioctl_post:1977: cmd=0x40125569 ugen_ioctl_post:2178: error=0 ugen_ioctl:1396: cmd=0x41705570 ugen_ioctl:1579: error=-3 ugen_ioctl_post:1977: cmd=0x41705570 ugen_ioctl_post:2178: error=0 ugen_close:187: flag=0x1 ugen_close:201: no FIFOs ugen_close:187: flag=0x2 ugen_close:201: no FIFOs ugen_open:157: flag=0x1 ugen_open:157: flag=0x2 ugen_open:157: flag=0x1 ugen_open:157: flag=0x2 ugen_ioctl:1396: cmd=0x4004557e ugen_ioctl:1579: error=-3 ugen_ioctl_post:1977: cmd=0x4004557e ugen_ioctl_post:2178: error=0 ugen_ioctl:1396: cmd=0x40045592 ugen_ioctl:1579: error=-3 ugen_ioctl_post:1977: cmd=0x40045592 ugen_ioctl_post:2178: error=0 ugen_ioctl:1396: cmd=0x40045564 ugen_ioctl:1579: error=-3 ugen_ioctl_post:1977: cmd=0x40045564 ugen_ioctl_post:2178: error=0 ugen_ioctl:1396: cmd=0x40045564 ugen_ioctl:1579: error=-3 ugen_ioctl_post:1977: cmd=0x40045564 ugen_ioctl_post:2178: error=0 ugen_ioctl:1396: cmd=0xc020556d ugen_ioctl:1579: error=-3 ugen_ioctl_post:1977: cmd=0xc020556d ugen_get_cdesc:650: ugen_get_cdesc:677: len=9 ugen_ioctl_post:2178: error=0 ugen_ioctl:1396: cmd=0xc020556d ugen_ioctl:1579: error=-3 ugen_ioctl_post:1977: cmd=0xc020556d ugen_get_cdesc:650: ugen_get_cdesc:677: len=20 ugen_ioctl_post:2178: error=0 ugen_close:187: flag=0x1 ugen_close:201: no FIFOs ugen_close:187: flag=0x2 ugen_close:201: no FIFOs ugen_close:187: flag=0x1 ugen_close:201: no FIFOs ugen_close:187: flag=0x2 ugen_close:201: no FIFOs ugen_open:157: flag=0x1 ugen_open:157: flag=0x2 ugen_ioctl:1396: cmd=0x4004557e ugen_ioctl:1579: error=-3 ugen_ioctl_post:1977: cmd=0x4004557e ugen_ioctl_post:2178: error=0 ugen_ioctl:1396: cmd=0x40125569 ugen_ioctl:1579: error=-3 ugen_ioctl_post:1977: cmd=0x40125569 ugen_ioctl_post:2178: error=0 ugen_ioctl:1396: cmd=0x41705570 ugen_ioctl:1579: error=-3 ugen_ioctl_post:1977: cmd=0x41705570 ugen_ioctl_post:2178: error=0 ugen_close:187: flag=0x1 ugen_close:201: no FIFOs ugen_close:187: flag=0x2 ugen_close:201: no FIFOs ugen_open:157: flag=0x1 ugen_open:157: flag=0x2 ugen_ioctl:1396: cmd=0x4004557e ugen_ioctl:1579: error=-3 ugen_ioctl_post:1977: cmd=0x4004557e ugen_ioctl_post:2178: error=0 ugen_ioctl:1396: cmd=0x40125569 ugen_ioctl:1579: error=-3 ugen_ioctl_post:1977: cmd=0x40125569 ugen_ioctl_post:2178: error=0 ugen_ioctl:1396: cmd=0x41705570 ugen_ioctl:1579: error=-3 ugen_ioctl_post:1977: cmd=0x41705570 ugen_ioctl_post:2178: error=0 ugen_close:187: flag=0x1 ugen_close:201: no FIFOs ugen_close:187: flag=0x2 ugen_close:201: no FIFOs ugen_open:157: flag=0x1 ugen_open:157: flag=0x2 ugen_ioctl:1396: cmd=0x4004557e ugen_ioctl:1579: error=-3 ugen_ioctl_post:1977: cmd=0x4004557e ugen_ioctl_post:2178: error=0 ugen_ioctl:1396: cmd=0x40125569 ugen_ioctl:1579: error=-3 ugen_ioctl_post:1977: cmd=0x40125569 ugen_ioctl_post:2178: error=0 ugen_ioctl:1396: cmd=0x41705570 ugen_ioctl:1579: error=-3 ugen_ioctl_post:1977: cmd=0x41705570 ugen_ioctl_post:2178: error=0 ugen_close:187: flag=0x1 ugen_close:201: no FIFOs ugen_close:187: flag=0x2 ugen_close:201: no FIFOs ugen_open:157: flag=0x1 ugen_open:157: flag=0x2 ugen_open:157: flag=0x1 ugen_open:157: flag=0x2 ugen_ioctl:1396: cmd=0x4004557e ugen_ioctl:1579: error=-3 ugen_ioctl_post:1977: cmd=0x4004557e ugen_ioctl_post:2178: error=0 ugen_ioctl:1396: cmd=0x40045592 ugen_ioctl:1579: error=-3 ugen_ioctl_post:1977: cmd=0x40045592 ugen_ioctl_post:2178: error=0 ugen_ioctl:1396: cmd=0x40045564 ugen_ioctl:1579: error=-3 ugen_ioctl_post:1977: cmd=0x40045564 ugen_ioctl_post:2178: error=0 ugen_ioctl:1396: cmd=0x40045564 ugen_ioctl:1579: error=-3 ugen_ioctl_post:1977: cmd=0x40045564 ugen_ioctl_post:2178: error=0 ugen_ioctl:1396: cmd=0xc020556d ugen_ioctl:1579: error=-3 ugen_ioctl_post:1977: cmd=0xc020556d ugen_get_cdesc:650: ugen_get_cdesc:677: len=9 ugen_ioctl_post:2178: error=0 ugen_ioctl:1396: cmd=0xc020556d ugen_ioctl:1579: error=-3 ugen_ioctl_post:1977: cmd=0xc020556d ugen_get_cdesc:650: ugen_get_cdesc:677: len=20 ugen_ioctl_post:2178: error=0 ugen_close:187: flag=0x1 ugen_close:201: no FIFOs ugen_close:187: flag=0x2 ugen_close:201: no FIFOs ugen_close:187: flag=0x1 ugen_close:201: no FIFOs ugen_close:187: flag=0x2 ugen_close:201: no FIFOs From Thomas.Sparrevohn at btinternet.com Fri Feb 6 16:32:21 2009 From: Thomas.Sparrevohn at btinternet.com (Thomas Sparrevohn) Date: Fri Feb 6 16:32:28 2009 Subject: HEADSUP usb2/usb4bsd to become default in GENERIC In-Reply-To: <20090206.081901.1923806177.imp@bsdimp.com> References: <20090206045349.GQ78804@elvis.mu.org> <20090206.081901.1923806177.imp@bsdimp.com> Message-ID: <200902070032.18792.Thomas.Sparrevohn@btinternet.com> On Friday 06 February 2009 15:19:01 M. Warner Losh wrote: > Doesn't the busdma issue need to be solved before we do this? usb2 > currently doesn't work if you have memory above 4GB due to this > issue. I thought we tagged it as a show stopper for making it the > default. > > Warner To be honst - I stongly recommend that it's fixed before. I know the problem is not related to the USB2 stack as such - However the way the problem occurs e.g. a corruption in the ATA dma load make it far from clear that it's a USB bounce buffer problem and my error reports was generally ignored with the - there nothing wrong with the ATA code - quite correctly as it turned out but - it kept me using an old kernel before the old brain got around to thinking about USB So I would love to see it fixed and I am not quite sure what the hold up is? Last time I heard - we seemed to be caugth in between - a double "there nothing wrong with the dma code" and "that is the way USB works" ;-) I am sure there is more to it however ;-0) Regards T. From hselasky at c2i.net Sat Feb 7 01:34:10 2009 From: hselasky at c2i.net (Hans Petter Selasky) Date: Sat Feb 7 01:34:17 2009 Subject: eToken and USB2 (ugen issue?) In-Reply-To: <200902062208.n16M8Xkr013205@lava.sentex.ca> References: <200902062126.n16LQ0Gc013030@lava.sentex.ca> <200902062208.n16M8Xkr013205@lava.sentex.ca> Message-ID: <200902071036.32995.hselasky@c2i.net> Hi Mike, The ugen devices are invisible and dynamically created. Try open /dev/ugen0.2.0.0 (control endpoint) Also you need to re-link your application with "dev/usb2/include/usb2_ioctl.h" Format is /dev/ugen... I recommend using libusb20 to access your USB device. See "man libusb20". --HPS On Friday 06 February 2009, Mike Tancsa wrote: > At 04:26 PM 2/6/2009, Mike Tancsa wrote: > >I was going to try out some of our apps on HEAD with USB2 kernel. > > > >dmesg shows > > > >ugen0.3: at usbus0 > > > > usbconfig -u 0 -a 2 dump_curr_config_desc > ugen0.2: Ltd.> at usbus0, cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON > > > Configuration index 0 > > bLength = 0x0009 > bDescriptorType = 0x0002 > wTotalLength = 0x0014 > bNumInterfaces = 0x0001 > bConfigurationValue = 0x0001 > iConfiguration = 0x0000 > bmAttributes = 0x0080 > bMaxPower = 0x0032 > > Interface 0 > bLength = 0x0009 > bDescriptorType = 0x0004 > bInterfaceNumber = 0x0000 > bAlternateSetting = 0x0000 > bNumEndpoints = 0x0000 > bInterfaceClass = 0x00ff > bInterfaceSubClass = 0x0000 > bInterfaceProtocol = 0x0000 > iInterface = 0x0000 > > > > 0[freebsd-current2]# usbconfig -u 0 -a 2 dump_access > Global Access: root:operator 0660 > ugen0.2: Ltd.> at usbus0, cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON > > Device Access: > Interface 0 Access: > > 0[freebsd-current2]# > > ugen0.2: at usbus0 (disconnected) > ugen0.2: at usbus0 > ushub2: on usbus0 > ushub2: 4 ports with 4 removable, self powered > ugen0.3: at usbus0 > ushub2: at ushub0, port 1, addr 2 (disconnected) > ugen0.3: at usbus0 (disconnected) > ugen0.2: at usbus0 (disconnected) > ugen0.2: at usbus0 > ugen_open:157: flag=0x1 > ugen_open:157: flag=0x2 > ugen_ioctl:1396: cmd=0x4004557e > uge > n_ioctl:1579: error=-3 > ugen_ioctl_post:1977: cmd=0x4004557e > ugen_ioctl_post:2178: error=0 > ugen_ioctl:1396: cmd=0x40125569 > ugen_ioctl:1579: error=-3 > ugen_ioctl_post:1977: cmd=0x40125569 > ugen_ioctl_post:2178: error=0 > ugen_ioctl:1396: cmd=0x41705570 > ugen_ioctl:1579: error=-3 > ugen_ioctl_post:1977: cmd=0x41705570 > ugen_ioctl_post:2178: error=0 > ugen_close:187: flag=0x1 > ugen_close:201: no FIFOs > ugen_close:187: flag=0x2 > ugen_close:201: no FIFOs > ugen_open:157: flag=0x1 > ugen_open:157: flag=0x2 > ugen_ioctl:1396: cmd=0x4004557e > ugen_ioctl:1579: error=-3 > ugen_ioctl_post:1977: cmd=0x4004557e > ugen_ioctl_post:2178: error=0 > ugen_ioctl:1396: cmd=0x40125569 > ugen_ioctl:1579: error=-3 > ugen_ioctl_post:1977: cmd=0x40125569 > ugen_ioctl_post:2178: error=0 > ugen_ioctl:1396: cmd=0x41705570 > ugen_ioctl:1579: error=-3 > ugen_ioctl_post:1977: cmd=0x41705570 > ugen_ioctl_post:2178: error=0 > ugen_close:187: flag=0x1 > ugen_close:201: no FIFOs > ugen_close:187: flag=0x2 > ugen_close:201: no FIFOs > ugen_open:157: flag=0x1 > ugen_open:157: flag=0x2 > ugen_ioctl:1396: cmd=0x4004557e > ugen_ioctl:1579: error=-3 > ugen_ioctl_post:1977: cmd=0x4004557e > ugen_ioctl_post:2178: error=0 > ugen_ioctl:1396: cmd=0x40125569 > ugen_ioctl:1579: error=-3 > ugen_ioctl_post:1977: cmd=0x40125569 > ugen_ioctl_post:2178: error=0 > ugen_ioctl:1396: cmd=0x41705570 > ugen_ioctl:1579: error=-3 > ugen_ioctl_post:1977: cmd=0x41705570 > ugen_ioctl_post:2178: error=0 > ugen_close:187: flag=0x1 > ugen_close:201: no FIFOs > ugen_close:187: flag=0x2 > ugen_close:201: no FIFOs > ugen_open:157: flag=0x1 > ugen_open:157: flag=0x2 > ugen_ioctl:1396: cmd=0x4004557e > ugen_ioctl:1579: error=-3 > ugen_ioctl_post:1977: cmd=0x4004557e > ugen_ioctl_post:2178: error=0 > ugen_ioctl:1396: cmd=0x40125569 > ugen_ioctl:1579: error=-3 > ugen_ioctl_post:1977: cmd=0x40125569 > ugen_ioctl_post:2178: error=0 > ugen_ioctl:1396: cmd=0x41705570 > ugen_ioctl:1579: error=-3 > ugen_ioctl_post:1977: cmd=0x41705570 > ugen_ioctl_post:2178: error=0 > ugen_close:187: flag=0x1 > ugen_close:201: no FIFOs > ugen_close:187: flag=0x2 > ugen_close:201: no FIFOs > ugen_open:157: flag=0x1 > ugen_open:157: flag=0x2 > ugen_ioctl:1396: cmd=0x4004557e > ugen_ioctl:1579: error=-3 > ugen_ioctl_post:1977: cmd=0x4004557e > ugen_ioctl_post:2178: error=0 > ugen_ioctl:1396: cmd=0x40125569 > ugen_ioctl:1579: error=-3 > ugen_ioctl_post:1977: cmd=0x40125569 > ugen_ioctl_post:2178: error=0 > ugen_ioctl:1396: cmd=0x41705570 > ugen_ioctl:1579: error=-3 > ugen_ioctl_post:1977: cmd=0x41705570 > ugen_ioctl_post:2178: error=0 > ugen_close:187: flag=0x1 > ugen_close:201: no FIFOs > ugen_close:187: flag=0x2 > ugen_close:201: no FIFOs > ugen_open:157: flag=0x1 > ugen_open:157: flag=0x2 > ugen_ioctl:1396: cmd=0x4004557e > ugen_ioctl:1579: error=-3 > ugen_ioctl_post:1977: cmd=0x4004557e > ugen_ioctl_post:2178: error=0 > ugen_ioctl:1396: cmd=0x40125569 > ugen_ioctl:1579: error=-3 > ugen_ioctl_post:1977: cmd=0x40125569 > ugen_ioctl_post:2178: error=0 > ugen_ioctl:1396: cmd=0x41705570 > ugen_ioctl:1579: error=-3 > ugen_ioctl_post:1977: cmd=0x41705570 > ugen_ioctl_post:2178: error=0 > ugen_close:187: flag=0x1 > ugen_close:201: no FIFOs > ugen_close:187: flag=0x2 > ugen_close:201: no FIFOs > ugen_open:157: flag=0x1 > ugen_open:157: flag=0x2 > ugen_open:157: flag=0x1 > ugen_open:157: flag=0x2 > ugen_ioctl:1396: cmd=0x4004557e > ugen_ioctl:1579: error=-3 > ugen_ioctl_post:1977: cmd=0x4004557e > ugen_ioctl_post:2178: error=0 > ugen_ioctl:1396: cmd=0x40045592 > ugen_ioctl:1579: error=-3 > ugen_ioctl_post:1977: cmd=0x40045592 > ugen_ioctl_post:2178: error=0 > ugen_ioctl:1396: cmd=0x40045564 > ugen_ioctl:1579: error=-3 > ugen_ioctl_post:1977: cmd=0x40045564 > ugen_ioctl_post:2178: error=0 > ugen_ioctl:1396: cmd=0x40045564 > ugen_ioctl:1579: error=-3 > ugen_ioctl_post:1977: cmd=0x40045564 > ugen_ioctl_post:2178: error=0 > ugen_ioctl:1396: cmd=0xc020556d > ugen_ioctl:1579: error=-3 > ugen_ioctl_post:1977: cmd=0xc020556d > ugen_get_cdesc:650: > ugen_get_cdesc:677: len=9 > ugen_ioctl_post:2178: error=0 > ugen_ioctl:1396: cmd=0xc020556d > ugen_ioctl:1579: error=-3 > ugen_ioctl_post:1977: cmd=0xc020556d > ugen_get_cdesc:650: > ugen_get_cdesc:677: len=20 > ugen_ioctl_post:2178: error=0 > ugen_close:187: flag=0x1 > ugen_close:201: no FIFOs > ugen_close:187: flag=0x2 > ugen_close:201: no FIFOs > ugen_close:187: flag=0x1 > ugen_close:201: no FIFOs > ugen_close:187: flag=0x2 > ugen_close:201: no FIFOs > ugen_open:157: flag=0x1 > ugen_open:157: flag=0x2 > ugen_ioctl:1396: cmd=0x4004557e > ugen_ioctl:1579: error=-3 > ugen_ioctl_post:1977: cmd=0x4004557e > ugen_ioctl_post:2178: error=0 > ugen_ioctl:1396: cmd=0x40125569 > ugen_ioctl:1579: error=-3 > ugen_ioctl_post:1977: cmd=0x40125569 > ugen_ioctl_post:2178: error=0 > ugen_ioctl:1396: cmd=0x41705570 > ugen_ioctl:1579: error=-3 > ugen_ioctl_post:1977: cmd=0x41705570 > ugen_ioctl_post:2178: error=0 > ugen_close:187: flag=0x1 > ugen_close:201: no FIFOs > ugen_close:187: flag=0x2 > ugen_close:201: no FIFOs > ugen_open:157: flag=0x1 > ugen_open:157: flag=0x2 > ugen_ioctl:1396: cmd=0x4004557e > ugen_ioctl:1579: error=-3 > ugen_ioctl_post:1977: cmd=0x4004557e > ugen_ioctl_post:2178: error=0 > ugen_ioctl:1396: cmd=0x40125569 > ugen_ioctl:1579: error=-3 > ugen_ioctl_post:1977: cmd=0x40125569 > ugen_ioctl_post:2178: error=0 > ugen_ioctl:1396: cmd=0x41705570 > ugen_ioctl:1579: error=-3 > ugen_ioctl_post:1977: cmd=0x41705570 > ugen_ioctl_post:2178: error=0 > ugen_close:187: flag=0x1 > ugen_close:201: no FIFOs > ugen_close:187: flag=0x2 > ugen_close:201: no FIFOs > ugen_open:157: flag=0x1 > ugen_open:157: flag=0x2 > ugen_ioctl:1396: cmd=0x4004557e > ugen_ioctl:1579: error=-3 > ugen_ioctl_post:1977: cmd=0x4004557e > ugen_ioctl_post:2178: error=0 > ugen_ioctl:1396: cmd=0x40125569 > ugen_ioctl:1579: error=-3 > ugen_ioctl_post:1977: cmd=0x40125569 > ugen_ioctl_post:2178: error=0 > ugen_ioctl:1396: cmd=0x41705570 > ugen_ioctl:1579: error=-3 > ugen_ioctl_post:1977: cmd=0x41705570 > ugen_ioctl_post:2178: error=0 > ugen_close:187: flag=0x1 > ugen_close:201: no FIFOs > ugen_close:187: flag=0x2 > ugen_close:201: no FIFOs > ugen_open:157: flag=0x1 > ugen_open:157: flag=0x2 > ugen_open:157: flag=0x1 > ugen_open:157: flag=0x2 > ugen_ioctl:1396: cmd=0x4004557e > ugen_ioctl:1579: error=-3 > ugen_ioctl_post:1977: cmd=0x4004557e > ugen_ioctl_post:2178: error=0 > ugen_ioctl:1396: cmd=0x40045592 > ugen_ioctl:1579: error=-3 > ugen_ioctl_post:1977: cmd=0x40045592 > ugen_ioctl_post:2178: error=0 > ugen_ioctl:1396: cmd=0x40045564 > ugen_ioctl:1579: error=-3 > ugen_ioctl_post:1977: cmd=0x40045564 > ugen_ioctl_post:2178: error=0 > ugen_ioctl:1396: cmd=0x40045564 > ugen_ioctl:1579: error=-3 > ugen_ioctl_post:1977: cmd=0x40045564 > ugen_ioctl_post:2178: error=0 > ugen_ioctl:1396: cmd=0xc020556d > ugen_ioctl:1579: error=-3 > ugen_ioctl_post:1977: cmd=0xc020556d > ugen_get_cdesc:650: > ugen_get_cdesc:677: len=9 > ugen_ioctl_post:2178: error=0 > ugen_ioctl:1396: cmd=0xc020556d > ugen_ioctl:1579: error=-3 > ugen_ioctl_post:1977: cmd=0xc020556d > ugen_get_cdesc:650: > ugen_get_cdesc:677: len=20 > ugen_ioctl_post:2178: error=0 > ugen_close:187: flag=0x1 > ugen_close:201: no FIFOs > ugen_close:187: flag=0x2 > ugen_close:201: no FIFOs > ugen_close:187: flag=0x1 > ugen_close:201: no FIFOs > ugen_close:187: flag=0x2 > ugen_close:201: no FIFOs > > > _______________________________________________ > freebsd-usb@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-usb > To unsubscribe, send any mail to "freebsd-usb-unsubscribe@freebsd.org" From mike at sentex.net Sat Feb 7 03:54:19 2009 From: mike at sentex.net (Mike Tancsa) Date: Sat Feb 7 03:54:25 2009 Subject: eToken and USB2 (ugen issue?) In-Reply-To: <200902071036.32995.hselasky@c2i.net> References: <200902062126.n16LQ0Gc013030@lava.sentex.ca> <200902062208.n16M8Xkr013205@lava.sentex.ca> <200902071036.32995.hselasky@c2i.net> Message-ID: <200902071154.n17BsE2h016610@lava.sentex.ca> At 04:36 AM 2/7/2009, Hans Petter Selasky wrote: >Hi Mike, > >The ugen devices are invisible and dynamically created. > >Try open /dev/ugen0.2.0.0 (control endpoint) > >Also you need to re-link your application with "dev/usb2/include/usb2_ioctl.h" > >Format is /dev/ugen... > >I recommend using libusb20 to access your USB device. > >See "man libusb20". Hi, Thanks for the response. These are all out of the ports (openct,opensc). Are there any pointers somewhere on how to best teach old apps about the new USB2 world on FreeBSD ? ---Mike From hselasky at c2i.net Sat Feb 7 04:01:31 2009 From: hselasky at c2i.net (Hans Petter Selasky) Date: Sat Feb 7 04:01:37 2009 Subject: eToken and USB2 (ugen issue?) In-Reply-To: <200902071154.n17BsE2h016610@lava.sentex.ca> References: <200902062126.n16LQ0Gc013030@lava.sentex.ca> <200902071036.32995.hselasky@c2i.net> <200902071154.n17BsE2h016610@lava.sentex.ca> Message-ID: <200902071303.53394.hselasky@c2i.net> On Saturday 07 February 2009, Mike Tancsa wrote: > At 04:36 AM 2/7/2009, Hans Petter Selasky wrote: > >Hi Mike, > > > >The ugen devices are invisible and dynamically created. > > > >Try open /dev/ugen0.2.0.0 (control endpoint) > > > >Also you need to re-link your application with > > "dev/usb2/include/usb2_ioctl.h" > > > >Format is /dev/ugen... > > > >I recommend using libusb20 to access your USB device. > > > >See "man libusb20". > > Hi, > Thanks for the response. These are all out of the ports > (openct,opensc). Are there any pointers somewhere on how to best > teach old apps about the new USB2 world on FreeBSD ? > Hi Mike, Most commonly the following advice helps: Add to /etc/libmap.conf: libusb-0.1.so libusb20.so libusb-0.1.so.8 libusb20.so.1 Also see: http://wiki.freebsd.org/USB --HPS From hselasky at c2i.net Sat Feb 7 04:52:10 2009 From: hselasky at c2i.net (Hans Petter Selasky) Date: Sat Feb 7 04:52:30 2009 Subject: USB2/USB4BSD - code reference available Message-ID: <200902071354.28941.hselasky@c2i.net> Hi, I've taken the time to generate a doxygen code reference for the new USB stack. Result is available here: http://www.selasky.org/hans_petter/usb4bsd/ http://www.selasky.org/hans_petter/usb4bsd/html/index.html --HPS From bruce at cran.org.uk Sat Feb 7 06:02:42 2009 From: bruce at cran.org.uk (Bruce Cran) Date: Sat Feb 7 06:02:48 2009 Subject: usb_reset, libusb20_compat01 and USB2 Message-ID: <20090207140228.7d549c53@gluon> I've been working to port dfu-util, OpenMoko's USB DFU application, to FreeBSD to work under USB2. One problem I've found is that the device starts out in Runtime Mode so dfu-util calls usb_reset to put it into DFU mode; it seems to expect usb_reset to cause the system to detach and reattach the device, but this doesn't happen. As a result usb_find_devices always returns 0 which triggers a warning; also, since usb_reset causes the device to disappear on Linux dfu-util doesn't call usb_close after resetting since the handle has become invalid. A side-effect of this is that on FreeBSD a duplicate device appears when doing a second enumeration pass. Since dfu-util only expects to see a single DFU-capable device it bails out, and it becomes necessary to run it again for it to download the firmware (since the phone is now already in DFU mode). Is this a problem with the expectations of dfu-util, or should calling usb_reset invalidate the device handle and cause the device to re-attach? -- Bruce Cran From hselasky at c2i.net Sat Feb 7 06:17:59 2009 From: hselasky at c2i.net (Hans Petter Selasky) Date: Sat Feb 7 06:18:05 2009 Subject: usb_reset, libusb20_compat01 and USB2 In-Reply-To: <20090207140228.7d549c53@gluon> References: <20090207140228.7d549c53@gluon> Message-ID: <200902071520.24660.hselasky@c2i.net> On Saturday 07 February 2009, Bruce Cran wrote: > usb_close Hi, Try this patch to libusb20: http://perforce.freebsd.org/chv.cgi?CH=157335 Seems like there is different behaviour between libusb20 and libusb0.1.xx --HPS From bruce at cran.org.uk Sat Feb 7 06:39:56 2009 From: bruce at cran.org.uk (Bruce Cran) Date: Sat Feb 7 06:40:02 2009 Subject: usb_reset, libusb20_compat01 and USB2 In-Reply-To: <200902071520.24660.hselasky@c2i.net> References: <20090207140228.7d549c53@gluon> <200902071520.24660.hselasky@c2i.net> Message-ID: <20090207143950.737c8171@gluon> On Sat, 7 Feb 2009 15:20:24 +0100 Hans Petter Selasky wrote: > Try this patch to libusb20: > > http://perforce.freebsd.org/chv.cgi?CH=157335 > > Seems like there is different behaviour between libusb20 and > libusb0.1.xx That works - thanks! -- Bruce Cran From imp at bsdimp.com Sat Feb 7 09:00:41 2009 From: imp at bsdimp.com (M. Warner Losh) Date: Sat Feb 7 09:01:08 2009 Subject: eToken and USB2 (ugen issue?) In-Reply-To: <200902071303.53394.hselasky@c2i.net> References: <200902071036.32995.hselasky@c2i.net> <200902071154.n17BsE2h016610@lava.sentex.ca> <200902071303.53394.hselasky@c2i.net> Message-ID: <20090207.095745.-1987210212.imp@bsdimp.com> In message: <200902071303.53394.hselasky@c2i.net> Hans Petter Selasky writes: : On Saturday 07 February 2009, Mike Tancsa wrote: : > At 04:36 AM 2/7/2009, Hans Petter Selasky wrote: : > >Hi Mike, : > > : > >The ugen devices are invisible and dynamically created. : > > : > >Try open /dev/ugen0.2.0.0 (control endpoint) : > > : > >Also you need to re-link your application with : > > "dev/usb2/include/usb2_ioctl.h" : > > : > >Format is /dev/ugen... : > > : > >I recommend using libusb20 to access your USB device. : > > : > >See "man libusb20". : > : > Hi, : > Thanks for the response. These are all out of the ports : > (openct,opensc). Are there any pointers somewhere on how to best : > teach old apps about the new USB2 world on FreeBSD ? : > : : Hi Mike, : : Most commonly the following advice helps: : : Add to /etc/libmap.conf: : libusb-0.1.so libusb20.so : libusb-0.1.so.8 libusb20.so.1 : : Also see: : http://wiki.freebsd.org/USB What about for apps that don't use libusb? Warner From hselasky at c2i.net Sat Feb 7 09:06:25 2009 From: hselasky at c2i.net (Hans Petter Selasky) Date: Sat Feb 7 09:06:32 2009 Subject: eToken and USB2 (ugen issue?) In-Reply-To: <20090207.095745.-1987210212.imp@bsdimp.com> References: <200902071036.32995.hselasky@c2i.net> <200902071303.53394.hselasky@c2i.net> <20090207.095745.-1987210212.imp@bsdimp.com> Message-ID: <200902071808.48709.hselasky@c2i.net> On Saturday 07 February 2009, M. Warner Losh wrote: > In message: <200902071303.53394.hselasky@c2i.net> > > Hans Petter Selasky writes: > : On Saturday 07 February 2009, Mike Tancsa wrote: > : > At 04:36 AM 2/7/2009, Hans Petter Selasky wrote: > : > >Hi Mike, > : > > > : > >The ugen devices are invisible and dynamically created. > : > > > : > >Try open /dev/ugen0.2.0.0 (control endpoint) > : > > > : > >Also you need to re-link your application with > : > > "dev/usb2/include/usb2_ioctl.h" > : > > > : > >Format is /dev/ugen... > : > > > : > >I recommend using libusb20 to access your USB device. > : > > > : > >See "man libusb20". > : > > : > Hi, > : > Thanks for the response. These are all out of the ports > : > (openct,opensc). Are there any pointers somewhere on how to best > : > teach old apps about the new USB2 world on FreeBSD ? > : > : Hi Mike, > : > : Most commonly the following advice helps: > : > : Add to /etc/libmap.conf: > : libusb-0.1.so libusb20.so > : libusb-0.1.so.8 libusb20.so.1 > : > : Also see: > : http://wiki.freebsd.org/USB > > What about for apps that don't use libusb? > Hi Warner, Applications that use /dev/ugen, needs to be recompiled at least and modified to open /dev/ugenX.Y.A.B instead of /dev/ugenY.B . I recommend people using the libusb or libusb20 API. Using a library makes porting much easier! --HPS From imp at bsdimp.com Sat Feb 7 10:40:18 2009 From: imp at bsdimp.com (M. Warner Losh) Date: Sat Feb 7 10:40:25 2009 Subject: eToken and USB2 (ugen issue?) In-Reply-To: <200902071808.48709.hselasky@c2i.net> References: <200902071303.53394.hselasky@c2i.net> <20090207.095745.-1987210212.imp@bsdimp.com> <200902071808.48709.hselasky@c2i.net> Message-ID: <20090207.113850.454687644.imp@bsdimp.com> In message: <200902071808.48709.hselasky@c2i.net> Hans Petter Selasky writes: : On Saturday 07 February 2009, M. Warner Losh wrote: : > In message: <200902071303.53394.hselasky@c2i.net> : > : > Hans Petter Selasky writes: : > : On Saturday 07 February 2009, Mike Tancsa wrote: : > : > At 04:36 AM 2/7/2009, Hans Petter Selasky wrote: : > : > >Hi Mike, : > : > > : > : > >The ugen devices are invisible and dynamically created. : > : > > : > : > >Try open /dev/ugen0.2.0.0 (control endpoint) : > : > > : > : > >Also you need to re-link your application with : > : > > "dev/usb2/include/usb2_ioctl.h" : > : > > : > : > >Format is /dev/ugen... : > : > > : > : > >I recommend using libusb20 to access your USB device. : > : > > : > : > >See "man libusb20". : > : > : > : > Hi, : > : > Thanks for the response. These are all out of the ports : > : > (openct,opensc). Are there any pointers somewhere on how to best : > : > teach old apps about the new USB2 world on FreeBSD ? : > : : > : Hi Mike, : > : : > : Most commonly the following advice helps: : > : : > : Add to /etc/libmap.conf: : > : libusb-0.1.so libusb20.so : > : libusb-0.1.so.8 libusb20.so.1 : > : : > : Also see: : > : http://wiki.freebsd.org/USB : > : > What about for apps that don't use libusb? : > : : Hi Warner, : : Applications that use /dev/ugen, needs to be recompiled at least and modified : to open /dev/ugenX.Y.A.B instead of /dev/ugenY.B . Any reason not to provide the old name as an alias to the new? : I recommend people using the libusb or libusb20 API. Using a library makes : porting much easier! That's true. And very cool that it helps enable more technology... Warner From hselasky at c2i.net Sat Feb 7 11:42:30 2009 From: hselasky at c2i.net (Hans Petter Selasky) Date: Sat Feb 7 11:44:10 2009 Subject: eToken and USB2 (ugen issue?) In-Reply-To: <20090207.113850.454687644.imp@bsdimp.com> References: <200902071303.53394.hselasky@c2i.net> <200902071808.48709.hselasky@c2i.net> <20090207.113850.454687644.imp@bsdimp.com> Message-ID: <200902072044.53830.hselasky@c2i.net> On Saturday 07 February 2009, M. Warner Losh wrote: Hi, > : > : Applications that use /dev/ugen, needs to be recompiled at least and > : modified to open /dev/ugenX.Y.A.B instead of /dev/ugenY.B . > > Any reason not to provide the old name as an alias to the new? Technically it will complicate the ugen kernel code. > > : I recommend people using the libusb or libusb20 API. Using a library > : makes porting much easier! > > That's true. And very cool that it helps enable more technology... --HPS From imp at bsdimp.com Sat Feb 7 13:21:18 2009 From: imp at bsdimp.com (M. Warner Losh) Date: Sat Feb 7 13:21:25 2009 Subject: eToken and USB2 (ugen issue?) In-Reply-To: <200902072044.53830.hselasky@c2i.net> References: <200902071808.48709.hselasky@c2i.net> <20090207.113850.454687644.imp@bsdimp.com> <200902072044.53830.hselasky@c2i.net> Message-ID: <20090207.141924.1835128044.imp@bsdimp.com> In message: <200902072044.53830.hselasky@c2i.net> Hans Petter Selasky writes: : On Saturday 07 February 2009, M. Warner Losh wrote: : : Hi, : : > : : > : Applications that use /dev/ugen, needs to be recompiled at least and : > : modified to open /dev/ugenX.Y.A.B instead of /dev/ugenY.B . : > : > Any reason not to provide the old name as an alias to the new? : : Technically it will complicate the ugen kernel code. That's a very vague answer.. Warner From alfred at freebsd.org Sat Feb 7 21:21:11 2009 From: alfred at freebsd.org (Alfred Perlstein) Date: Sat Feb 7 21:21:19 2009 Subject: HEADSUP usb2/usb4bsd to become default in GENERIC In-Reply-To: <498C013B.4000405@FreeBSD.org> References: <20090206045349.GQ78804@elvis.mu.org> <498C013B.4000405@FreeBSD.org> Message-ID: <20090208052110.GY78804@elvis.mu.org> * Maxim Sobolev [090206 01:50] wrote: > Alfred Perlstein wrote: > > - Update GENERIC to use usb2 device names. > > Wasn't there a plan to rename usb2 devices to match oldusb names (where > applicable) once oldusb had been killed? I don't see it in the list. Probably, although coming from the other side as a user I find it pretty annoying when there's somewhat gratuitous changes to the kernel config files that I don't really care about that cause my kernels to break. Doing it once is probably enough, but let me know if this is really, really important... Basically, calling it usb2 isn't as bad as renaming it back to "usb" as it's less disruptive in my book. If a lot of people poke me about renaming it, we'll get it done, but I don't really believe in it. -- - Alfred Perlstein From hselasky at c2i.net Sun Feb 8 01:09:28 2009 From: hselasky at c2i.net (Hans Petter Selasky) Date: Sun Feb 8 01:09:35 2009 Subject: eToken and USB2 (ugen issue?) In-Reply-To: <20090207.141924.1835128044.imp@bsdimp.com> References: <200902071808.48709.hselasky@c2i.net> <200902072044.53830.hselasky@c2i.net> <20090207.141924.1835128044.imp@bsdimp.com> Message-ID: <200902081011.52747.hselasky@c2i.net> On Saturday 07 February 2009, M. Warner Losh wrote: > In message: <200902072044.53830.hselasky@c2i.net> > > Hans Petter Selasky writes: > : On Saturday 07 February 2009, M. Warner Losh wrote: > : > : Hi, > : > : > : Applications that use /dev/ugen, needs to be recompiled at least and > : > : modified to open /dev/ugenX.Y.A.B instead of /dev/ugenY.B . > : > > : > Any reason not to provide the old name as an alias to the new? > : > : Technically it will complicate the ugen kernel code. > > That's a very vague answer.. /dev/ugen is currently two dimensional with X.Y, where X is bus and Y is device index. This needs to be serialised into /dev/ugenZ if we are to be backwards compatible. --HPS From miwi at FreeBSD.org Sun Feb 8 05:59:31 2009 From: miwi at FreeBSD.org (Martin Wilke) Date: Sun Feb 8 05:59:43 2009 Subject: HEADSUP usb2/usb4bsd to become default in GENERIC In-Reply-To: <20090206045349.GQ78804@elvis.mu.org> References: <20090206045349.GQ78804@elvis.mu.org> Message-ID: <20090208134420.GA42242@bsdcrew.de> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 May be also a ports exp-run to make sure you don't break to many ports? - - Martin On Thu, Feb 05, 2009 at 08:53:49PM -0800, Alfred Perlstein wrote: > Hello -current and -usb. > > We are in the final stages of bringing in the new usb > stack. > > Features include: SMP, better device support, speed increases. > > We hope to make it in for 8.0. It will really take a unified effort > to make this all work and I look forward to all contributors input. > > We have a few large steps ahead of us and I wanted to lay out the > schedule so that people understand what is coming and what to expect. > > At this point we expect there to be no style or changes in usb2 > that are not bugfixes until Phase 3 "Hand off". The reason for > this is to prevent bugs from creeping in and allow the maintainer > to focus 100% on bugs and feature parity with the oldusb stack. > > Here is the plan and timeline: > > Phase 1) Make usb2 the default, by enabling it in GENERIC. > > * Sunday 8 Feb 2009 -- Toggle the usb2 knob in GENERIC > > - Add all the usb2 options to NOTES, including commented > documentation about recommended usb2 'sets' of options, > and the usual NOTES-based hints about the options. > > - Update GENERIC to use usb2 device names. > > - Bump __FreeBSD_version and edit UPDATING to note usb2 is now the > default. > > - Verify that it still possible to use the old usb code as a > fallback, until we are ready to detach and remove it from /head > > * Sunday 22 Feb 2009 -- Go through quirks in old-usb code and port > over any remaining bits to usb2 > > - Lock the oldusb code for 2 weeks, until the next usb2 > checkpoint, to verify usb2 is a viable replacement without > having to keep chasing a moving oldusb target. > > Phase 2) Removing the oldusb code. > > * Sunday 15 Mar 2009 -- usb2 bug busting weekend > > - Go through the open usb2 problem reports, and see if there are > any usb2 blocker bugs that need fixing. > > - If the bug hunt shows we are ready to do away with oldusb, > unlink the old usb code from the build, but leave it in for > a few more days. > > * Sunday 22 Mar 2009 -- remove oldusb code. > > - old usb code will be removed. > > Phase 3) Hand-off. > > * Sunday 29 Mar 2009 -- usb2 hand over to src-committers > > - The switch from a private Hans-only repository to the main > subversion tree. > > - At this point, the usb2 is handed over to the src-committers > and Hans has to go through a mentor/committer before committing > changes. > > Thank you! > > -- > - Alfred Perlstein > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" > - -- +-----------------------+-------------------------------+ | PGP : 0x05682353 | Jabber : miwi(at)BSDCrew.de | | ICQ : 169139903 | Mail : miwi(at)FreeBSD.org | +-----------------------+-------------------------------+ | Mess with the Best, Die like the Rest! | +-----------------------+-------------------------------+ -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (FreeBSD) iEYEARECAAYFAkmO4bQACgkQFwpycAVoI1NEcACeMQyjZGYPG1WO/pAT7ErFaKop pyYAnAuICJDTLDepTnLvvth1o+53m0nU =R3Om -----END PGP SIGNATURE----- From remko at FreeBSD.org Sun Feb 8 10:30:03 2009 From: remko at FreeBSD.org (Remko Lodder) Date: Sun Feb 8 10:30:16 2009 Subject: HEADSUP usb2/usb4bsd to become default in GENERIC In-Reply-To: <20090208052110.GY78804@elvis.mu.org> References: <20090206045349.GQ78804@elvis.mu.org> <498C013B.4000405@FreeBSD.org> <20090208052110.GY78804@elvis.mu.org> Message-ID: <8b3974a5f1b260fd438518f703aee2f5.squirrel@galain.elvandar.org> On Sun, February 8, 2009 6:21 am, Alfred Perlstein wrote: > * Maxim Sobolev [090206 01:50] wrote: >> Alfred Perlstein wrote: >> > - Update GENERIC to use usb2 device names. >> >> Wasn't there a plan to rename usb2 devices to match oldusb names (where >> applicable) once oldusb had been killed? I don't see it in the list. [snip] > > If a lot of people poke me about renaming it, we'll get it done, > but I don't really believe in it. > I would like to enfavor that it is being named "usb" at some point. We do not want to keep names like rcNG while at some point it's the defacto standard right? Also names like USB2 tell people that there might be a USB1 as well, which we no longer ship at some point. Please name it "usb_*". In addition; there is a request from Warner (if I remember correctly); which I do share; there is a manual regeneration needed if you add something to usbdevs, please make sure that that goes automatically like "usb1" does at the moment. Thanks, Remko -- /"\ Best regards, | remko@FreeBSD.org \ / Remko Lodder | remko@EFnet X http://www.evilcoder.org/ | / \ ASCII Ribbon Campaign | Against HTML Mail and News From thompsa at FreeBSD.org Sun Feb 8 10:38:27 2009 From: thompsa at FreeBSD.org (Andrew Thompson) Date: Sun Feb 8 10:38:33 2009 Subject: HEADSUP usb2/usb4bsd to become default in GENERIC In-Reply-To: <8b3974a5f1b260fd438518f703aee2f5.squirrel@galain.elvandar.org> References: <20090206045349.GQ78804@elvis.mu.org> <498C013B.4000405@FreeBSD.org> <20090208052110.GY78804@elvis.mu.org> <8b3974a5f1b260fd438518f703aee2f5.squirrel@galain.elvandar.org> Message-ID: <20090208183820.GA21343@citylink.fud.org.nz> On Sun, Feb 08, 2009 at 06:48:39PM +0100, Remko Lodder wrote: > On Sun, February 8, 2009 6:21 am, Alfred Perlstein wrote: > > * Maxim Sobolev [090206 01:50] wrote: > >> Alfred Perlstein wrote: > >> > - Update GENERIC to use usb2 device names. > >> > >> Wasn't there a plan to rename usb2 devices to match oldusb names (where > >> applicable) once oldusb had been killed? I don't see it in the list. > > [snip] > > > > > If a lot of people poke me about renaming it, we'll get it done, > > but I don't really believe in it. > > > > I would like to enfavor that it is being named "usb" at some point. We do > not want to keep names like rcNG while at some point it's the defacto > standard right? Also names like USB2 tell people that there might be a > USB1 as well, which we no longer ship at some point. > > Please name it "usb_*". > > In addition; there is a request from Warner (if I remember correctly); > which I do share; there is a manual regeneration needed if you add > something to usbdevs, please make sure that that goes automatically like > "usb1" does at the moment. I take it the stage (1) is to switch over GENERIC to the new usb2 code and will not involve renaming the config items. stage (2) moves the usb code around in svn and all USB2 kernel config items will assume their original names, ie. usb2_controller_echi -> ehci. I think this is what Alfred was getting about with only changing it once. Andrew From hselasky at c2i.net Sun Feb 8 10:48:53 2009 From: hselasky at c2i.net (Hans Petter Selasky) Date: Sun Feb 8 10:49:00 2009 Subject: HEADSUP usb2/usb4bsd to become default in GENERIC In-Reply-To: <20090208183820.GA21343@citylink.fud.org.nz> References: <20090206045349.GQ78804@elvis.mu.org> <8b3974a5f1b260fd438518f703aee2f5.squirrel@galain.elvandar.org> <20090208183820.GA21343@citylink.fud.org.nz> Message-ID: <200902081951.16823.hselasky@c2i.net> On Sunday 08 February 2009, Andrew Thompson wrote: > On Sun, Feb 08, 2009 at 06:48:39PM +0100, Remko Lodder wrote: > > On Sun, February 8, 2009 6:21 am, Alfred Perlstein wrote: > > > > Please name it "usb_*". Beware that if you rename everything from "usb2_" to "usb_" there will be symbol and structure clashes with the linux USB compat layer, which needs to be resolved. --HPS From gavin at FreeBSD.org Sun Feb 8 11:21:16 2009 From: gavin at FreeBSD.org (Gavin Atkinson) Date: Sun Feb 8 11:21:22 2009 Subject: HEADSUP usb2/usb4bsd to become default in GENERIC In-Reply-To: <20090208052110.GY78804@elvis.mu.org> References: <20090206045349.GQ78804@elvis.mu.org> <498C013B.4000405@FreeBSD.org> <20090208052110.GY78804@elvis.mu.org> Message-ID: <1234119008.7997.32.camel@buffy.york.ac.uk> On Sat, 2009-02-07 at 21:21 -0800, Alfred Perlstein wrote: > * Maxim Sobolev [090206 01:50] wrote: > > Alfred Perlstein wrote: > > > - Update GENERIC to use usb2 device names. > > > > Wasn't there a plan to rename usb2 devices to match oldusb names (where > > applicable) once oldusb had been killed? I don't see it in the list. > > Probably, although coming from the other side as a user I find it pretty > annoying when there's somewhat gratuitous changes to the kernel config > files that I don't really care about that cause my kernels to break. The vast majority of our users do not run -CURRENT, and so haven't had to change config files yet. One day, those users will be migrating from 7.x to 8.x, and shouldn't need to change their kernel config for a "somewhat gratuitous change". Your argument only works if people had already had to change their config files once (usb -> usb2), and that by renaming these back they will have to change their kernel config back. Only people running -CURRENT will end up having to do this twice (or indeed at all) if the rename takes place, end users will not need to do it at all. > Basically, calling it usb2 isn't as bad as renaming it back to "usb" > as it's less disruptive in my book. Again, I disagree. Gavin From lev at FreeBSD.org Sun Feb 8 11:40:57 2009 From: lev at FreeBSD.org (Lev Serebryakov) Date: Sun Feb 8 11:41:03 2009 Subject: Guide to porting old (usb) driver to new (usb2) framework? Message-ID: <1371503468.20090208222452@serebryakov.spb.ru> Hello, Freebsd-usb. I have some interesting device: USB2 4xSerial controller. It is based on MosChip 7840 chip, and provided with very ugly driver for FreeBSD 6/7 (open source!) I'm rewriting and cleanup driver right now, and want ot commit it to FreeBSD source tree. But as far as I understand, old-framework based driver is not actual for -CURRENT, and I need to provide version for new framework too. Is here any documentation on new (and old, to be honest) USB framework API? http://wiki.freebsd.org/USB doesn't give any useful information for developer. -- // Black Lion AKA Lev Serebryakov From sam at freebsd.org Sun Feb 8 11:45:27 2009 From: sam at freebsd.org (Sam Leffler) Date: Sun Feb 8 11:45:34 2009 Subject: HEADSUP usb2/usb4bsd to become default in GENERIC In-Reply-To: <1234119008.7997.32.camel@buffy.york.ac.uk> References: <20090206045349.GQ78804@elvis.mu.org> <498C013B.4000405@FreeBSD.org> <20090208052110.GY78804@elvis.mu.org> <1234119008.7997.32.camel@buffy.york.ac.uk> Message-ID: <498F2EBA.9000106@freebsd.org> Gavin Atkinson wrote: > On Sat, 2009-02-07 at 21:21 -0800, Alfred Perlstein wrote: > >> * Maxim Sobolev [090206 01:50] wrote: >> >>> Alfred Perlstein wrote: >>> >>>> - Update GENERIC to use usb2 device names. >>>> >>> Wasn't there a plan to rename usb2 devices to match oldusb names (where >>> applicable) once oldusb had been killed? I don't see it in the list. >>> >> Probably, although coming from the other side as a user I find it pretty >> annoying when there's somewhat gratuitous changes to the kernel config >> files that I don't really care about that cause my kernels to break. >> > > The vast majority of our users do not run -CURRENT, and so haven't had > to change config files yet. > > One day, those users will be migrating from 7.x to 8.x, and shouldn't > need to change their kernel config for a "somewhat gratuitous change". > > Your argument only works if people had already had to change their > config files once (usb -> usb2), and that by renaming these back they > will have to change their kernel config back. Only people running > -CURRENT will end up having to do this twice (or indeed at all) if the > rename takes place, end users will not need to do it at all. > > >> Basically, calling it usb2 isn't as bad as renaming it back to "usb" >> as it's less disruptive in my book. >> > > Again, I disagree. > I agree with your comments. And, as I've said previously, any name changes from usb1 will require _all_ documentation (manual pages, handbook, etc) to change; not a good idea. Sam From imp at bsdimp.com Sun Feb 8 11:48:49 2009 From: imp at bsdimp.com (M. Warner Losh) Date: Sun Feb 8 11:48:55 2009 Subject: HEADSUP usb2/usb4bsd to become default in GENERIC In-Reply-To: <200902081951.16823.hselasky@c2i.net> References: <8b3974a5f1b260fd438518f703aee2f5.squirrel@galain.elvandar.org> <20090208183820.GA21343@citylink.fud.org.nz> <200902081951.16823.hselasky@c2i.net> Message-ID: <20090208.124756.-942592244.imp@bsdimp.com> In message: <200902081951.16823.hselasky@c2i.net> Hans Petter Selasky writes: : On Sunday 08 February 2009, Andrew Thompson wrote: : > On Sun, Feb 08, 2009 at 06:48:39PM +0100, Remko Lodder wrote: : > > On Sun, February 8, 2009 6:21 am, Alfred Perlstein wrote: : : > > : > > Please name it "usb_*". : : Beware that if you rename everything from "usb2_" to "usb_" there will be : symbol and structure clashes with the linux USB compat layer, which needs to : be resolved. No. that's not the case. usb2_foo vs usb_foo in the kernel config files only affects what files config brings in, and we can easily tell it to bring the right ones in w/o any symbol issues. I'd leave everything else where it is now in the source tree. The rename is fairly trivial. Do people want me to float a patch? Warner From imp at bsdimp.com Sun Feb 8 11:54:17 2009 From: imp at bsdimp.com (M. Warner Losh) Date: Sun Feb 8 11:54:31 2009 Subject: HEADSUP usb2/usb4bsd to become default in GENERIC In-Reply-To: <20090208.124756.-942592244.imp@bsdimp.com> References: <20090208183820.GA21343@citylink.fud.org.nz> <200902081951.16823.hselasky@c2i.net> <20090208.124756.-942592244.imp@bsdimp.com> Message-ID: <20090208.125317.1170142000.imp@bsdimp.com> In message: <20090208.124756.-942592244.imp@bsdimp.com> "M. Warner Losh" writes: : In message: <200902081951.16823.hselasky@c2i.net> : Hans Petter Selasky writes: : : On Sunday 08 February 2009, Andrew Thompson wrote: : : > On Sun, Feb 08, 2009 at 06:48:39PM +0100, Remko Lodder wrote: : : > > On Sun, February 8, 2009 6:21 am, Alfred Perlstein wrote: : : : : > > : : > > Please name it "usb_*". : : : : Beware that if you rename everything from "usb2_" to "usb_" there will be : : symbol and structure clashes with the linux USB compat layer, which needs to : : be resolved. : : No. that's not the case. usb2_foo vs usb_foo in the kernel config : files only affects what files config brings in, and we can easily tell : it to bring the right ones in w/o any symbol issues. : : I'd leave everything else where it is now in the source tree. The : rename is fairly trivial. Do people want me to float a patch? Of course, the kernel config file names are just one aspect here. There's also the module names, that need to be considered. And also just because it can be done, doesn't mean we have to it. Warner From remko at elvandar.org Sun Feb 8 12:00:03 2009 From: remko at elvandar.org (Remko Lodder) Date: Sun Feb 8 12:00:10 2009 Subject: HEADSUP usb2/usb4bsd to become default in GENERIC In-Reply-To: <20090208183820.GA21343@citylink.fud.org.nz> References: <20090206045349.GQ78804@elvis.mu.org> <498C013B.4000405@FreeBSD.org> <20090208052110.GY78804@elvis.mu.org> <8b3974a5f1b260fd438518f703aee2f5.squirrel@galain.elvandar.org> <20090208183820.GA21343@citylink.fud.org.nz> Message-ID: >> > > I take it the stage (1) is to switch over GENERIC to the new usb2 code > and will not involve renaming the config items. > > stage (2) moves the usb code around in svn and all USB2 kernel config > items will assume their original names, ie. usb2_controller_echi -> > ehci. > > I think this is what Alfred was getting about with only changing it > once. > > Andrew That I would like :-) thnx for the additional comment :) -- /"\ Best regards, | remko@FreeBSD.org \ / Remko Lodder | remko@EFnet X http://www.evilcoder.org/ | / \ ASCII Ribbon Campaign | Against HTML Mail and News From hselasky at c2i.net Sun Feb 8 12:36:16 2009 From: hselasky at c2i.net (Hans Petter Selasky) Date: Sun Feb 8 12:36:21 2009 Subject: Guide to porting old (usb) driver to new (usb2) framework? In-Reply-To: <1371503468.20090208222452@serebryakov.spb.ru> References: <1371503468.20090208222452@serebryakov.spb.ru> Message-ID: <200902082138.39688.hselasky@c2i.net> On Sunday 08 February 2009, Lev Serebryakov wrote: > Hello, Freebsd-usb. > > I have some interesting device: USB2 4xSerial controller. It is > based on MosChip 7840 chip, and provided with very ugly driver for > FreeBSD 6/7 (open source!) > > I'm rewriting and cleanup driver right now, and want ot commit it to > FreeBSD source tree. > > But as far as I understand, old-framework based driver is not actual > for -CURRENT, and I need to provide version for new framework too. > > Is here any documentation on new (and old, to be honest) USB > framework API? > > http://wiki.freebsd.org/USB doesn't give any useful information for > developer. Hi, The only guide is to look at exisiting USB serial port drivers. With regard to MosChip there already exits a umoscom2.c The latest files which have not been merged into current can be found here: http://perforce.freebsd.org/depotTreeBrowser.cgi?FSPC=//depot/projects/usb/src/sys/dev/usb2/serial&HIDEDEL=NO Or here: svn --username anonsvn --password anonsvn \ checkout svn://svn.turbocat.net/i4b/trunk/i4b/src/sys/dev/usb2 Is your device multi port or single port? It should be quite trivial to make a device driver for a serial port device. --HPS From lev at FreeBSD.org Sun Feb 8 14:05:36 2009 From: lev at FreeBSD.org (Lev Serebryakov) Date: Sun Feb 8 14:05:42 2009 Subject: Guide to porting old (usb) driver to new (usb2) framework? In-Reply-To: <200902082138.39688.hselasky@c2i.net> References: <1371503468.20090208222452@serebryakov.spb.ru> <200902082138.39688.hselasky@c2i.net> Message-ID: <907967769.20090209010532@serebryakov.spb.ru> Hello, Hans. You wrote 8 ??????? 2009 ?., 23:38:38: > The only guide is to look at exisiting USB serial port drivers. With regard to > MosChip there already exits a umoscom2.c Great! Old stack doesn't have such driver. Maybe, my work is useless for -CURRENT, I need to try this driver with my device. > Is your device multi port or single port? 4 ports. > It should be quite trivial to make a device driver for a serial port device. Yep, cleanup of existing "driver" (it was ugly) was straightforward. This provided "driver" can't even send BREAK signal :) -- // Black Lion AKA Lev Serebryakov From lev at FreeBSD.org Sun Feb 8 14:19:49 2009 From: lev at FreeBSD.org (Lev Serebryakov) Date: Sun Feb 8 14:19:56 2009 Subject: Guide to porting old (usb) driver to new (usb2) framework? In-Reply-To: <200902082138.39688.hselasky@c2i.net> References: <1371503468.20090208222452@serebryakov.spb.ru> <200902082138.39688.hselasky@c2i.net> Message-ID: <1327395134.20090209011945@serebryakov.spb.ru> Hello, Hans. You wrote 8 ??????? 2009 ?., 23:38:38: > The only guide is to look at exisiting USB serial port drivers. With regard to > MosChip there already exits a umoscom2.c Yep, it is old, single-port chip, with different registers layout. BTW, datasheets on 7820/7840 chips are not complete, and some registers are left in driver as `magic' numbers. I don't like it, but Moschip doesn't answer on e-mails :( -- // Black Lion AKA Lev Serebryakov From imp at bsdimp.com Sun Feb 8 14:34:09 2009 From: imp at bsdimp.com (M. Warner Losh) Date: Sun Feb 8 14:34:20 2009 Subject: HEADSUP usb2/usb4bsd to become default in GENERIC In-Reply-To: References: <8b3974a5f1b260fd438518f703aee2f5.squirrel@galain.elvandar.org> <20090208183820.GA21343@citylink.fud.org.nz> Message-ID: <20090208.153233.1154625921.imp@bsdimp.com> In message: Remko Lodder writes: : >> : > : > I take it the stage (1) is to switch over GENERIC to the new usb2 code : > and will not involve renaming the config items. : > : > stage (2) moves the usb code around in svn and all USB2 kernel config : > items will assume their original names, ie. usb2_controller_echi -> : > ehci. : > : > I think this is what Alfred was getting about with only changing it : > once. : > : > Andrew : : : That I would like :-) : : thnx for the additional comment :) Also, keep in mind, once Alfred does the hand off, the project will be free to do #2. It really isn't a second change, if you think about it. Just because we change the default, that doesn't force people to use the new default... Warner From yanefbsd at gmail.com Sun Feb 8 17:29:09 2009 From: yanefbsd at gmail.com (Garrett Cooper) Date: Sun Feb 8 17:29:17 2009 Subject: Future of udbp in USB2? Message-ID: <7d6fde3d0902081703l71bc1de8g9bb7baf6b9b050c8@mail.gmail.com> Hi Hans, I was just preparing to test out the usb2 changes and I noted that one option in my old kernel configfile didn't have an analog in the USB2 config file: udbp. I don't use the option, but I was just checking to see whether or not an analog does exist, or the support will be completely phased out when USB2 becomes the default for FreeBSD. Thanks, -Garrett From yanefbsd at gmail.com Sun Feb 8 19:40:40 2009 From: yanefbsd at gmail.com (Garrett Cooper) Date: Sun Feb 8 19:40:52 2009 Subject: HEADSUP usb2/usb4bsd to become default in GENERIC In-Reply-To: References: <20090206045349.GQ78804@elvis.mu.org> <498C013B.4000405@FreeBSD.org> <20090208052110.GY78804@elvis.mu.org> <1234119008.7997.32.camel@buffy.york.ac.uk> <498F2EBA.9000106@freebsd.org> Message-ID: <7d6fde3d0902081940o3ffd8ea1m6f59d65ee59d57ff@mail.gmail.com> On Sun, Feb 8, 2009 at 7:17 PM, Maksim Yevmenkin wrote: > On Sun, Feb 8, 2009 at 11:12 AM, Sam Leffler wrote: > > [...] > >>>>>> - Update GENERIC to use usb2 device names. >>>>> >>>>> Wasn't there a plan to rename usb2 devices to match oldusb names (where >>>>> applicable) once oldusb had been killed? I don't see it in the list. >>>> >>>> Probably, although coming from the other side as a user I find it pretty >>>> annoying when there's somewhat gratuitous changes to the kernel config >>>> files that I don't really care about that cause my kernels to break. >>> >>> The vast majority of our users do not run -CURRENT, and so haven't had >>> to change config files yet. >>> >>> One day, those users will be migrating from 7.x to 8.x, and shouldn't >>> need to change their kernel config for a "somewhat gratuitous change". >>> >>> Your argument only works if people had already had to change their >>> config files once (usb -> usb2), and that by renaming these back they >>> will have to change their kernel config back. Only people running >>> -CURRENT will end up having to do this twice (or indeed at all) if the >>> rename takes place, end users will not need to do it at all. >>> >>>> Basically, calling it usb2 isn't as bad as renaming it back to "usb" >>>> as it's less disruptive in my book. >>> >>> Again, I disagree. >> >> I agree with your comments. And, as I've said previously, any name changes >> from usb1 will require _all_ documentation (manual pages, handbook, etc) to >> change; not a good idea. > > i second that. i would really like to see old module names to be > preserved as much as possible. > > thanks, > max In some cases I find the new module names to be more intuitive (uplcom -> usb2_serial_plcom), but I find having to add the additional modules required for USB4BSD (usb2_core, etc) to be a bit more annoying. Also, there's an issue with the example USB2 kernel config -- you need to have double-quotes around the include file otherwise config says `syntax error' and pukes. Thanks, -Garrett From maksim.yevmenkin at gmail.com Sun Feb 8 19:48:54 2009 From: maksim.yevmenkin at gmail.com (Maksim Yevmenkin) Date: Sun Feb 8 19:49:13 2009 Subject: HEADSUP usb2/usb4bsd to become default in GENERIC In-Reply-To: <498F2EBA.9000106@freebsd.org> References: <20090206045349.GQ78804@elvis.mu.org> <498C013B.4000405@FreeBSD.org> <20090208052110.GY78804@elvis.mu.org> <1234119008.7997.32.camel@buffy.york.ac.uk> <498F2EBA.9000106@freebsd.org> Message-ID: On Sun, Feb 8, 2009 at 11:12 AM, Sam Leffler wrote: [...] >>>>> - Update GENERIC to use usb2 device names. >>>> >>>> Wasn't there a plan to rename usb2 devices to match oldusb names (where >>>> applicable) once oldusb had been killed? I don't see it in the list. >>> >>> Probably, although coming from the other side as a user I find it pretty >>> annoying when there's somewhat gratuitous changes to the kernel config >>> files that I don't really care about that cause my kernels to break. >> >> The vast majority of our users do not run -CURRENT, and so haven't had >> to change config files yet. >> >> One day, those users will be migrating from 7.x to 8.x, and shouldn't >> need to change their kernel config for a "somewhat gratuitous change". >> >> Your argument only works if people had already had to change their >> config files once (usb -> usb2), and that by renaming these back they >> will have to change their kernel config back. Only people running >> -CURRENT will end up having to do this twice (or indeed at all) if the >> rename takes place, end users will not need to do it at all. >> >>> Basically, calling it usb2 isn't as bad as renaming it back to "usb" >>> as it's less disruptive in my book. >> >> Again, I disagree. > > I agree with your comments. And, as I've said previously, any name changes > from usb1 will require _all_ documentation (manual pages, handbook, etc) to > change; not a good idea. i second that. i would really like to see old module names to be preserved as much as possible. thanks, max From sobomax at FreeBSD.org Sun Feb 8 20:00:14 2009 From: sobomax at FreeBSD.org (Maxim Sobolev) Date: Sun Feb 8 20:00:21 2009 Subject: HEADSUP usb2/usb4bsd to become default in GENERIC In-Reply-To: <1234119008.7997.32.camel@buffy.york.ac.uk> References: <20090206045349.GQ78804@elvis.mu.org> <498C013B.4000405@FreeBSD.org> <20090208052110.GY78804@elvis.mu.org> <1234119008.7997.32.camel@buffy.york.ac.uk> Message-ID: <498FAA44.9050105@FreeBSD.org> Gavin Atkinson wrote: > On Sat, 2009-02-07 at 21:21 -0800, Alfred Perlstein wrote: >> * Maxim Sobolev [090206 01:50] wrote: >>> Alfred Perlstein wrote: >>>> - Update GENERIC to use usb2 device names. >>> Wasn't there a plan to rename usb2 devices to match oldusb names (where >>> applicable) once oldusb had been killed? I don't see it in the list. >> Probably, although coming from the other side as a user I find it pretty >> annoying when there's somewhat gratuitous changes to the kernel config >> files that I don't really care about that cause my kernels to break. > > The vast majority of our users do not run -CURRENT, and so haven't had > to change config files yet. > > One day, those users will be migrating from 7.x to 8.x, and shouldn't > need to change their kernel config for a "somewhat gratuitous change". > > Your argument only works if people had already had to change their > config files once (usb -> usb2), and that by renaming these back they > will have to change their kernel config back. Only people running > -CURRENT will end up having to do this twice (or indeed at all) if the > rename takes place, end users will not need to do it at all. That's exactly my point. Number of people running -CURRENT is much less than total number of people running FreeBSD. Therefore, I believe we should try to avoid introducing any superfluous changes upon those users. Not even to mention large body of USB-related documentation that will need to be altered to match the new USB world order. Users running -CURRENT should be prepared to make changes now and then, it's part of the game. I don't POLA is really applicable to them. -Maxim From ntai at smartfruit.com Sun Feb 8 22:00:18 2009 From: ntai at smartfruit.com (Naoyuki Tai) Date: Sun Feb 8 22:00:24 2009 Subject: usb/131521: Registering Belkin UPS to usb_quirks.c Message-ID: <200902090555.n195tHal059257@www.freebsd.org> >Number: 131521 >Category: usb >Synopsis: Registering Belkin UPS to usb_quirks.c >Confidential: no >Severity: serious >Priority: medium >Responsible: freebsd-usb >State: open >Quarter: >Keywords: >Date-Required: >Class: change-request >Submitter-Id: current-users >Arrival-Date: Mon Feb 09 06:00:16 UTC 2009 >Closed-Date: >Last-Modified: >Originator: Naoyuki Tai >Release: FreeBSD 7.1-RELEASE >Organization: >Environment: FreeBSD nile.smartfruit.com 7.1-RELEASE FreeBSD 7.1-RELEASE #1: Sat Feb 7 21:05:20 EST 2009 root@nile.smartfruit.com:/usr/obj/usr/src/sys/NILE i386 >Description: Please add more Belkin UPS USB connection to usb quirks. I tried to make nut (Network UPS Tool) to work with a Belkin UPS, and it did not work. I chased down from libusb to usb driver, and found that only one of many Belkin UPSes is registered in "/usr/src/sys/dev/usb/usb_quirks.c". I have taken the USB product IDs from nut's belkin-hid.c so that all Belkin UPSes appear as ugen instead of uhid. If I'm nice enough, I probably should go around all of nut's known USB UPSes and add them to usbdevs and usb_quirks.c, but I'm not. Sorry. FreeBSD's nut implementation requires that UPS via USB to appear as ugen device, not uhid, while many of USB UPSes appear as uhid. >How-To-Repeat: Connect a Belkin UPS via USB, and see it appears as "ugen", not "uhid". >Fix: # diff -c usbdevs.original usbdevs *** usbdevs.original Mon Nov 24 21:59:29 2008 --- usbdevs Mon Feb 9 00:37:07 2009 *************** *** 926,931 **** --- 926,937 ---- product BELKIN F5U257 0x0257 F5U257 Serial product BELKIN F5U409 0x0409 F5U409 Serial product BELKIN F6C550AVR 0x0551 F6C550-AVR UPS + product BELKIN F6C800UNV 0x0980 F6C800 Universal UPS + product BELKIN F6C100UNV 0x0910 F6C100 Universal UPS + product BELKIN F6C120UNV 0x0912 F6C120 Universal UPS + product BELKIN F6C1500TWRK 0x0751 F6C1500-TW-RK UPS + product BELKIN F6H375USB 0x0375 F6H375-USB + product BELKIN F6C1100UNV 0x1100 F6C1100-UNV, F6C1200-UNV product BELKIN F5U120 0x1203 F5U120-PC Hub product BELKIN ZD1211B 0x4050 ZD1211B product BELKIN F5D5055 0x5055 F5D5055 # diff -c usb_quirks.c.original usb_quirks.c *** usb_quirks.c.original Mon Feb 9 00:35:38 2009 --- usb_quirks.c Mon Feb 9 00:37:53 2009 *************** *** 98,103 **** --- 98,115 ---- ANY, { UQ_HID_IGNORE }}, { USB_VENDOR_BELKIN, USB_PRODUCT_BELKIN_F6C550AVR, ANY, { UQ_HID_IGNORE }}, + { USB_VENDOR_BELKIN, USB_PRODUCT_BELKIN_F6C800UNV, + ANY, { UQ_HID_IGNORE }}, + { USB_VENDOR_BELKIN, USB_PRODUCT_BELKIN_F6C100UNV, + ANY, { UQ_HID_IGNORE }}, + { USB_VENDOR_BELKIN, USB_PRODUCT_BELKIN_F6C120UNV, + ANY, { UQ_HID_IGNORE }}, + { USB_VENDOR_BELKIN, USB_PRODUCT_BELKIN_F6C1500TWRK, + ANY, { UQ_HID_IGNORE }}, + { USB_VENDOR_BELKIN, USB_PRODUCT_BELKIN_F6H375USB, + ANY, { UQ_HID_IGNORE }}, + { USB_VENDOR_BELKIN, USB_PRODUCT_BELKIN_F6C1100UNV, + ANY, { UQ_HID_IGNORE }}, { USB_VENDOR_DELORME, USB_PRODUCT_DELORME_EARTHMATE, ANY, { UQ_HID_IGNORE }}, { USB_VENDOR_ITUNERNET, USB_PRODUCT_ITUNERNET_USBLCD2X20, >Release-Note: >Audit-Trail: >Unformatted: From hselasky at c2i.net Mon Feb 9 00:24:40 2009 From: hselasky at c2i.net (Hans Petter Selasky) Date: Mon Feb 9 00:24:58 2009 Subject: HEADSUP usb2/usb4bsd to become default in GENERIC In-Reply-To: <7d6fde3d0902081940o3ffd8ea1m6f59d65ee59d57ff@mail.gmail.com> References: <20090206045349.GQ78804@elvis.mu.org> <7d6fde3d0902081940o3ffd8ea1m6f59d65ee59d57ff@mail.gmail.com> Message-ID: <200902090927.04378.hselasky@c2i.net> On Monday 09 February 2009, Garrett Cooper wrote: > On Sun, Feb 8, 2009 at 7:17 PM, Maksim Yevmenkin > > wrote: > > On Sun, Feb 8, 2009 at 11:12 AM, Sam Leffler wrote: > > > > [...] > > > >>>>>> - Update GENERIC to use usb2 device names. > >>>>> > >>>>> Wasn't there a plan to rename usb2 devices to match oldusb names > >>>>> (where applicable) once oldusb had been killed? I don't see it in the > >>>>> list. > >>>> > >>>> Probably, although coming from the other side as a user I find it > >>>> pretty annoying when there's somewhat gratuitous changes to the kernel > >>>> config files that I don't really care about that cause my kernels to > >>>> break. > >>> > >>> The vast majority of our users do not run -CURRENT, and so haven't had > >>> to change config files yet. > >>> > >>> One day, those users will be migrating from 7.x to 8.x, and shouldn't > >>> need to change their kernel config for a "somewhat gratuitous change". > >>> > >>> Your argument only works if people had already had to change their > >>> config files once (usb -> usb2), and that by renaming these back they > >>> will have to change their kernel config back. Only people running > >>> -CURRENT will end up having to do this twice (or indeed at all) if the > >>> rename takes place, end users will not need to do it at all. > >>> > >>>> Basically, calling it usb2 isn't as bad as renaming it back to "usb" > >>>> as it's less disruptive in my book. > >>> > >>> Again, I disagree. > >> > >> I agree with your comments. And, as I've said previously, any name > >> changes from usb1 will require _all_ documentation (manual pages, > >> handbook, etc) to change; not a good idea. > > > > i second that. i would really like to see old module names to be > > preserved as much as possible. > > > > thanks, > > max > > In some cases I find the new module names to be more intuitive > (uplcom -> usb2_serial_plcom), but I find having to add the additional > modules required for USB4BSD (usb2_core, etc) to be a bit more > annoying. > Also, there's an issue with the example USB2 kernel config -- you > need to have double-quotes around the include file otherwise config > says `syntax error' and pukes. How about symlinking the old module names with the new ones? And the same in the kernel, so that device uplcom Is equivalent to device usb2_serial_plcom From what I understand the "conf/files" syntax allows this. Not sure about KMODs, if there is a LINK option. --HPS From hselasky at c2i.net Mon Feb 9 01:14:32 2009 From: hselasky at c2i.net (Hans Petter Selasky) Date: Mon Feb 9 01:14:38 2009 Subject: Future of udbp in USB2? In-Reply-To: <7d6fde3d0902081703l71bc1de8g9bb7baf6b9b050c8@mail.gmail.com> References: <7d6fde3d0902081703l71bc1de8g9bb7baf6b9b050c8@mail.gmail.com> Message-ID: <200902090916.54896.hselasky@c2i.net> On Monday 09 February 2009, Garrett Cooper wrote: > Hi Hans, > I was just preparing to test out the usb2 changes and I noted that > one option in my old kernel configfile didn't have an analog in the > USB2 config file: udbp. > I don't use the option, but I was just checking to see whether or > not an analog does exist, or the support will be completely phased out > when USB2 becomes the default for FreeBSD. > Thanks, > -Garrett Hi, The udbp module is now called "misc_dbp" and it still connects via netgraph. Other similar devices just emulate USB ethernet devices. --HPS From nick at anywi.com Mon Feb 9 01:47:37 2009 From: nick at anywi.com (Nick Hibma) Date: Mon Feb 9 01:47:43 2009 Subject: USB2 - umass problem In-Reply-To: <20090204.085606.1630229139.imp@bsdimp.com> References: <1233734352.1767.55.camel@localhost> <200902041044.27663.hselasky@c2i.net> <20090204.085606.1630229139.imp@bsdimp.com> Message-ID: <200902091035.26738.nick@anywi.com> > : > By some reason devfs semantic was changed: > : > Instead of /dev/cuaU0.[0-2] and /dev/ttyU0.[0-2], I've get > : > /dev/cuaU[0-2] /dev/ttyU[0-2] and! /dev/cuau1 /dev/ttyu1 > : > What is reason for such change (additional port with lowercase 'u' > : > and U[0-2] instead of more logical U0.[0-2]) ? > : > : It is because we are attaching drivers per interface instead of per > : device. A new modem unit is allocated every time we find a modem, > : simply put. If the modem has multiple instances in an interface, > : /dev/cuaU0.[0...] will be created. Else /dev/cuaU... . > > Generally, we try not to change the details of how a device attaches > /dev entries from release to release. Why the change? The USB1 u3g driver also attaches to interfaces, but collects all interfaces in one go, leaving all unused interfaces available for other drivers (e.g. umass) or claims them (to hide the 'driver disks'). It is the main reason why I wrote a separate driver in the first place. Otherwise the UMTS cards could be treated as serial ports without any port singalling. It is important to be able to determine in an automated way the 2 or more serial ports that belong together. As an example: If you create a router box that automatically configures itself depending on the hardware it finds, we somehow need to find out which two serial ports are found on each GPRS/UMTS card, so we can assign the first one to PPP and the other one to our control application. Cheers, Nick -- AnyWi Technologies From keramida at ceid.upatras.gr Mon Feb 9 02:16:40 2009 From: keramida at ceid.upatras.gr (Giorgos Keramidas) Date: Mon Feb 9 02:16:46 2009 Subject: HEADSUP usb2/usb4bsd to become default in GENERIC In-Reply-To: <200902090927.04378.hselasky@c2i.net> (Hans Petter Selasky's message of "Mon, 9 Feb 2009 09:27:03 +0100") References: <20090206045349.GQ78804@elvis.mu.org> <7d6fde3d0902081940o3ffd8ea1m6f59d65ee59d57ff@mail.gmail.com> <200902090927.04378.hselasky@c2i.net> Message-ID: <87zlgwq6dd.fsf@kobe.laptop> On Mon, 9 Feb 2009 09:27:03 +0100, Hans Petter Selasky wrote: > On Monday 09 February 2009, Garrett Cooper wrote: >> In some cases I find the new module names to be more intuitive >> (uplcom -> usb2_serial_plcom), but I find having to add the additional >> modules required for USB4BSD (usb2_core, etc) to be a bit more >> annoying. >> >> Also, there's an issue with the example USB2 kernel config -- you >> need to have double-quotes around the include file otherwise config >> says `syntax error' and pukes. > > How about symlinking the old module names with the new ones? That may work as a temporary 'hack' for kldload, but it won't really work kldstat, kldunload and apropos(1) or the examples of these in the documentation. From hselasky at c2i.net Mon Feb 9 02:28:48 2009 From: hselasky at c2i.net (Hans Petter Selasky) Date: Mon Feb 9 02:28:55 2009 Subject: USB2 - umass problem In-Reply-To: <200902091035.26738.nick@anywi.com> References: <1233734352.1767.55.camel@localhost> <20090204.085606.1630229139.imp@bsdimp.com> <200902091035.26738.nick@anywi.com> Message-ID: <200902091131.12232.hselasky@c2i.net> On Monday 09 February 2009, Nick Hibma wrote: > > : > By some reason devfs semantic was changed: > > : > Instead of /dev/cuaU0.[0-2] and /dev/ttyU0.[0-2], I've get > > : > /dev/cuaU[0-2] /dev/ttyU[0-2] and! /dev/cuau1 /dev/ttyu1 > > : > What is reason for such change (additional port with lowercase 'u' > > : > and U[0-2] instead of more logical U0.[0-2]) ? > > : > > : It is because we are attaching drivers per interface instead of per > > : device. A new modem unit is allocated every time we find a modem, > > : simply put. If the modem has multiple instances in an interface, > > : /dev/cuaU0.[0...] will be created. Else /dev/cuaU... . > > > > Generally, we try not to change the details of how a device attaches > > /dev entries from release to release. Why the change? > > The USB1 u3g driver also attaches to interfaces, but collects all > interfaces in one go, leaving all unused interfaces available for other > drivers (e.g. umass) or claims them (to hide the 'driver disks'). It is the > main reason why I wrote a separate driver in the first place. Otherwise the > UMTS cards could be treated as serial ports without any port singalling. > > It is important to be able to determine in an automated way the 2 or more > serial ports that belong together. As an example: If you create a router > box that automatically configures itself depending on the hardware it > finds, we somehow need to find out which two serial ports are found on each > GPRS/UMTS card, so we can assign the first one to PPP and the other one to > our control application. > This has been fixed in P4 USB. --HPS From bugmaster at FreeBSD.org Mon Feb 9 03:07:01 2009 From: bugmaster at FreeBSD.org (FreeBSD bugmaster) Date: Mon Feb 9 03:09:36 2009 Subject: Current problem reports assigned to freebsd-usb@FreeBSD.org Message-ID: <200902091107.n19B70GP009292@freefall.freebsd.org> Note: to view an individual PR, use: http://www.freebsd.org/cgi/query-pr.cgi?pr=(number). The following is a listing of current problems submitted by FreeBSD users. These represent problem reports covering all versions including experimental development code and obsolete releases. S Tracker Resp. Description -------------------------------------------------------------------------------- o usb/131521 usb Registering Belkin UPS to usb_quirks.c f usb/131123 usb [patch] re-add UQ_ASSUME_CM_OVER_DATA USB quirk o usb/131074 usb no run-time detection of usb devices plugged into exte o usb/130736 usb Page fault unplugging USB stick o usb/130325 usb [usb] [patch] fix tools/tools/usb/print-usb-if-vids.sh o usb/130230 usb Samsung Electronics YP-U3 does not attach in 7.1-RELEA o usb/130208 usb Boot process severely hampered by umass0 error o usb/130122 usb [newusb] DVD drive detects as 'da' device o usb/130066 usb [newusb] Serial adaptor use fail with 'unsupported spe o usb/129964 usb [newusb] disconnection of ugen devices isn't logged o bin/129963 usb [newusb] usbconfig(8) fails with misleading error when o docs/129962 usb [newusb] usbconfig(8) refers to non-existant usb2_core o usb/129945 usb [usbdevs] [patch] add u3g support for Longcheer WM66 U o usb/129766 usb [usb] plugging in usb modem HUAWEI E226 panics system o usb/129758 usb [uftdi] [patch] add Pyramid LCD usb support o usb/129673 usb [uhci] uhci (uhub) confused on replugging USB 1.1 scan o usb/129522 usb [ubsa] [patch] add support for ZTE AC8700 modem o usb/129500 usb [umass] [panic] FreeBSD Crashes when connecting SanDis o usb/129311 usb [usb] [panic] Instant crash with an USB card reader o usb/129251 usb [usbdevs] [patch] Liebert UPS being assigned uhid and o usb/129173 usb [uplcom] [patch] Add support for Corega CG-USBRS232R a s usb/128990 usb [usb] u3g does not handle RTS/CTS available on for exa o usb/128977 usb [usb] [patch] uaudio is not full duplex o usb/128803 usb [usbdevs] [patch] Quirk for I-Tuner Networks USBLCD4X2 o usb/128590 usb [patch] [newusb] Updates to NOTES for new USB stack o usb/128485 usb [umodem] [patch] Nokia N80 modem support o usb/128425 usb [umass] Cannot Connect Maxtor Onetouch 4 USB drive f usb/128418 usb [panic] [rum] loading if_rum causes panic, looks like o usb/128324 usb [uplcom] [patch] remove baud rate restriction for PL23 o usb/127980 usb [umass] [patch] Fix Samsung YP U2 MP3 player on 7.x an o usb/127926 usb [boot] USB Timeout during bootup o usb/127549 usb [umass] [patch] Meizu MiniPlayer M6 (SL) requires some s usb/127453 usb [request] ubsa, uark, ubser, uftdi, and friends should o usb/127423 usb [boot] BTX halted on Gigabyte GA-MA69VM-S2 / AMD Sempr o usb/127342 usb [boot] cannot enable usb keyboard and mouse support in o kern/127222 usb [ohci]: Regression in 7.0 usb storage generic driver o usb/126884 usb [ugen] [patch] Bug in buffer handling in ugen.c f usb/126848 usb [usb]: USB Keyboard hangs during Installation o usb/126740 usb [ulpt] doesn't work on 7.0-RELEASE, 10 second stall be o usb/126519 usb [usb] [panic] panic when plugging in an iphone o kern/126396 usb [panic] kernel panic after unplug USB Bluetooth device o usb/125736 usb [ukbd] [hang] system hangs after AT keyboard detect if o usb/125631 usb [ums] [panic] kernel panic during bootup while 'Logite o usb/125510 usb [panic] repeated plug and unplug of USB mass storage d o usb/125450 usb [panic] Removing USB flash card while being accessed c o usb/125264 usb [patch] sysctl for set usb mouse rate (very useful for o usb/125238 usb [ums] Habu Mouse turns off in X o usb/125088 usb [keyboard] Touchpad not detected on Adesso AKB-430UG U o usb/125072 usb [uplcom] [patch] add Mobile Action MA-620 Infrared Ada o usb/124980 usb [panic] kernel panic on detaching unmounted umass devi o kern/124777 usb [ucom] USB cua devices don't revert to tty devices whe o usb/124758 usb [rum] [panic] rum panics SMP kernel o usb/124708 usb [panic] Kernel panic on USB KVM reattach o usb/124604 usb [ums] Microsoft combo wireless mouse doesn't work o usb/123969 usb [usb] Supermicro H8SMi-2 usb problem: port reset faile o usb/123714 usb [usb] [panic] Panic when hald-storage-probe runs with o usb/123691 usb usbd(8): usbd hangs o usb/123690 usb [usb] [panic] Panic on USB device insertion when usb l o usb/123611 usb [usb] BBB reset failed, STALLED from Imation/Mitsumi U o usb/123509 usb [umass] continuous reset Samsung SGH-G600 phone o usb/123352 usb [usbdevs] [patch] Add Option GTMAX3.6/7.2 and Quallcom o usb/123351 usb [usbdevs] [patch] Add Reiner SCT cyberJack, Omnikey [2 o usb/122992 usb [umass] [patch] MotoROKR Z6 Phone not recognised by um o usb/122956 usb [ubsa] [patch] add support for Novatel Wireless XU870 o usb/122936 usb [ucom] [ubsa] Device does not receive interrupt o usb/122905 usb [ubsa] [patch] add Huawei E220 to ubsa o usb/122819 usb [usb] [patch] Patch to provide dynamic additions to th o usb/122813 usb [udbp] [request] udbp driver should be removed in favo o usb/122621 usb [patch] [request] New driver for Sierra Wireless 3G US o usb/122547 usb [ehci] USB Printer not being recognized after reboot o usb/122539 usb [ohci] [panic] AnyDATA ADU-E1000D - kernel panic: ohci o usb/122483 usb [panic] [ulpt] Repeatable panic in 7.0-STABLE o usb/122119 usb [umass] umass device causes creation of daX but not da o usb/122025 usb [uscanner] [patch] uscanner does not attach to Epson R o usb/121755 usb [ohci] [patch] Fix panic after ohci/uhub cardbus devic o usb/121734 usb [ugen] ugen HP1022 printer device not working since up o usb/121708 usb [keyboard] nforce 650i mobo w/ usb keyboard infinite k o usb/121474 usb [cam] [patch] QUIRK: SAMSUNG HM250JI in LaCie usb hard o usb/121426 usb [patch] [uscanner] add HP ScanJet 3570C o usb/121275 usb [boot] FreeBSD fails to boot with usb legacy support e o usb/121232 usb [usb] [panic] USB CardBus card removal causes reboot s p usb/121184 usb [uipaq] [patch] add ids from linux ipaq driver (plus a o usb/121169 usb [umass] Issues with usb mp3 player o usb/121045 usb [uftdi] [patch] Add support for PC-OP-RS1 and KURO-RS o usb/120786 usb [usb] [panic] Kernel panic when forced umount of a det o usb/120729 usb [panic] fault while in kernel mode with connecting USB o usb/120572 usb [umass] [patch] quirk to support ASUS P535 as umass (a o usb/120321 usb [hang] System hangs when transferring data to WD MyBoo o usb/120283 usb [panic] Automation reboot with wireless keyboard & mou o usb/120034 usb [hang] 6.2 & 6.3 hangs on boot at usb0: OHCI with 1.5 o usb/120017 usb [ehci] [patch] CS5536 (AMD Geode) USB 2.0 quirk o usb/119981 usb [axe] [patch] add support for LOGITEC LAN-GTJ/U2 gigab o usb/119977 usb [ums] Mouse does not work in a Cherry-USB keyboard/mou o usb/119653 usb [cam] [patch] iriver s7 player sync cache error patch o usb/119633 usb [umass] umass0: BBB reset failed, IOERROR [regression] o usb/119513 usb [irq] inserting dlink dwl-g630 wireless card results i o usb/119509 usb [usb] USB flaky on Dell Optiplex 755 o usb/119481 usb [hang] FreeBSD not responding after connecting USB-Mas o usb/119389 usb [umass] Sony DSC-W1 CBI reset failed, STALLED [regress o usb/119227 usb [ubsa] [patch] ubsa buffer is too small; should be tun o usb/119201 usb [cam] [patch] Quirks for Olympus FE-210 camera, LG and o usb/118686 usb [usbdevs] [patch] teach usbdevs / ubsa(4) about Huawei o usb/118485 usb [usbdevs] [patch] Logitech Headset Workaround o usb/118480 usb [umass] Timeout in USB mass storage freezes vfs layer o usb/118353 usb [panic] [ppp] repeatable kernel panic during ppp(4) se o usb/118141 usb [ucom] usb serial and nokia phones ucomreadcb ucomread o usb/118140 usb [ucom] [patch] quick hack for ucom to get it behave wi o usb/118098 usb [umass] 6th gen iPod causes problems when disconnectin o usb/117955 usb [umass] [panic] inserting minolta dimage a2 crashes OS o usb/117946 usb [panic] D-Link DUB-E100 rev. B1 crashes FreeBSD 7.0-BE o usb/117938 usb [ums] [patch] Adding support for MS WL Natural and MS o usb/117911 usb [ums] [request] Mouse Gembird MUSWC not work o usb/117893 usb [umass] Lacie USB DVD writing failing o usb/117613 usb [uhci] [irq] uhci interrupt storm & USB leaked memory o usb/117598 usb [uaudio] [patch] Not possible to record with Plantroni o usb/117313 usb [umass] [panic] panic on usb camera insertion o usb/117200 usb [ugen] ugen0 prints strange string on attach if detach o usb/117185 usb [umodem] [patch] Add support for UNION interface descr o usb/117183 usb [panic] USB/fusefs -- panic while transferring large a o usb/116947 usb [ukbd] [patch] [regression] enable boot protocol on th o usb/116699 usb [usbhid] USB HID devices do not initialize at system b o usb/116561 usb [umodem] [panic] RELENG_6 umodem panic "trying to slee o usb/116282 usb [ulpt] Cannot print on USB HP LJ1018 or LJ1300 o usb/115935 usb [usbdevs] [patch] kernel counterproductively attaches o usb/115933 usb [uftdi] [patch] RATOC REX-USB60F (usb serial converter o usb/115400 usb [ehci] Problem with EHCI on ASUS M2N4-SLI o usb/115298 usb [ulpt] [panic] Turning off USB printer panics kernel o usb/114916 usb [umass] [patch] USB Maxtor drive (L300RO) requires qui o kern/114780 usb [uplcom] [panic] Panics while stress testing the uplco o usb/114682 usb [umass] generic USB media-card reader unusable o usb/114310 usb [libusb] [patch] [panic] USB hub attachment panics ker o usb/114068 usb [umass] [patch] Problems with connection of the umass o conf/114013 usb [patch] WITHOUT_USB allow to compil a lot of USB stuff s usb/113977 usb [request] Need a way to set mode of USB disk's write c o usb/113672 usb [ehci] [panic] Kernel panic with AEWIN CB6971 s usb/113629 usb [ukbd] Dropped USB keyboard events on Dell Latitude D6 o usb/113432 usb [ucom] WARNING: attempt to net_add_domain(netgraph) af a usb/113060 usb [usbdevs] [patch] Samsung printer not working in bidir o usb/112944 usb [ulpt] [patch] Bi-directional access to HP LaserJet 10 o usb/112640 usb [usb] [hang] Kernel freezes when writing a file to an o usb/112631 usb [panic] Problem with SONY DSC-S80 camera on umount s usb/112568 usb [umass] [request] USB mode may wrong when mounting Pla o usb/112463 usb [umass] problem with Samsung USB DVD writer, libscg an o usb/112461 usb [ehci] [request] ehci USB 2.0 doesn't work on nforce4 o usb/111753 usb [uhid] [panic] Replicable system panic involving UHID s usb/110991 usb [usbdevs] [patch] QUIRK: Super Top IDE DEVICE (depends o usb/110988 usb [umass] [patch] Handling of quirk IGNORE_RESIDUE is um o usb/110856 usb [ugen] [patch] interrupt in msgs are truncated when bu o usb/110197 usb [umass] Sony PSP umass device does not detach from EHC o usb/109397 usb [panic] on boot from USB flash o usb/109274 usb [usb] MCP55 USB Controller fails to attach in AMD64 Cu o usb/108513 usb [umass] Creative MuVo TX FM fails in 6.2-RELEASE [regr s usb/108344 usb [panic] kernel with atausb panics when unplugging USB o usb/108056 usb [ohci] Mouse gets powered off during device probe when o usb/107935 usb [uplcom] [panic] panic while accessing /dev/cuaU0 o usb/107924 usb [patch] usbd(8) does not call detach o usb/107848 usb [umass] [request] cannot access Samsung flash disk o usb/107827 usb [ohci] [panic] ohci_add_done addr not found o usb/107496 usb [uhub] USB device problem on RELENG_6_2 (SHORT_XFER) [ o usb/107388 usb [patch] [request] new driver: add utoppy device from N o usb/107248 usb [umass] [patch] scsi_da.c quirk for Cowon iAUDIO X5 MP o usb/107243 usb [cam] [patch] Apacer USB Flash Drive quirk o usb/106861 usb [usbdevs] [patch]: usbdevs update: Add product ACER Ze s usb/106832 usb [usb] USB HP printer is not detected by kernel when AC o usb/106648 usb [umass] [hang] USB Floppy on D1950 10 min Hang on Inse o usb/106621 usb [axe] [patch] DLINK DUB-E100 support broken o usb/106615 usb [uftdi] uftdi module does not automatically load with o usb/106041 usb [usb] [request] FreeBSD does not recognise Mustek Bear o usb/105361 usb [panic] Kernel panic during unmounting mass storage (C o usb/105186 usb [ehci] [panic] USB 2.0/ehci on FreeBSD 6.2-PRE/AMD64 c o usb/105065 usb [ata] [usb] SATA - USB Bridge o usb/104830 usb [umass] system crashes when copying data to umass devi o usb/104645 usb [umass] [request] Rave C-201 MP3 player does not commu o usb/104352 usb [ural] [patch] ural driver doesnt work o usb/104292 usb [umass] [hang] system lockup on forced umount of usb-s o usb/104290 usb [umass] [patch] quirk: TOSHIBA DVD-RAM drive (libretto o usb/103917 usb [uhub] USB driver reports "Addr 0 should never happen" o usb/103418 usb usbhidctl(1): [patch] [request] usbhidctl: add ability o usb/103289 usb [request] USB 2.0 problems on AMD LX-800 CPU and CS-55 o usb/103046 usb [ulpt] [patch] ulpt event driven I/O with select(2) an o usb/103025 usb [uhub] [panic] wrong detection of USB device for FreeB o usb/102976 usb [panic] Casio Exilim Digital Camera causes panic on in o usb/102678 usb [keyboard] Dell PowerEdge DRAC5 USB Keyboard does not o usb/102066 usb [ukbd] usb keyboard and multimedia keys don't work o usb/101775 usb [libusbhid] [patch] possible error in report descripto o usb/101761 usb [usb] [patch] [request] usb.h: increase maximal size o o usb/101752 usb [umass] [panic] 6.1-RELEASE kernel panic on usb device o usb/101448 usb [ohci] FBSD 6.1-STABLE/AMD64 crashes under heavy USB/O o usb/101096 usb [ural] [panic] USB WLAN occasionally causes kernel-pan o usb/100746 usb [keyboard] system does not boot due to USB keyboard pr o usb/99538 usb [keyboard] while using USB keyboard default params of o usb/99431 usb [keyboard] FreeBSD on MSI 6566E (Intel 845E motherboar o usb/98343 usb [boot] BBB reset failed errors with Creative Muvo MP3 o usb/97472 usb [cam] [patch] add support for Olympus C150,D390 s usb/97286 usb [mouse] [request] MS Wireless Intellimouse Explorer 2. o usb/97175 usb [umass] [hang] USB cardreader hangs system o usb/96457 usb [umass] [panic] fatback on umass = reboot o usb/96381 usb [cam] [patch] add a quirk table entry for a flash ram o usb/96224 usb [usb] [msdosfs] mount_msdosfs cause page fault in sync s usb/96120 usb [ums] [request] USB mouse not always detected s usb/95636 usb [umass] [boot] 5 minute delay at boot when using VT620 o usb/95562 usb [umass] Write Stress in USB Mass drive causes "vinvalb s usb/95348 usb [keyboard] USB keyboard unplug causes noise on screen o usb/95037 usb [umass] USB disk not recognized on hot-plug. o usb/94897 usb [panic] Kernel Panic when cleanly unmounting USB disk o usb/94717 usb [ulpt] Reading from /dev/ulpt can break work of a UHCI o usb/94384 usb [panic] kernel panic with usb2 hardware o usb/93872 usb [cam] [patch] SCSI quirk required for ELTA 8061 OL USB o usb/93828 usb [ohci] [panic] ohci causes panic on boot (HP Pavillion o usb/93408 usb [mouse] hw.acpi.cpu.cx_lowest=C3 on AMD Turion causes o usb/93389 usb [umass] [patch] Digital Camera Pentax S60 don't work o usb/93155 usb [ulpt] /dev/ulpt0: device busy, USB printer does not w o usb/92852 usb [ums] [patch] Vertical scroll not working properly on o usb/92171 usb [panic] panic unplugging Vodafone Mobile Connect (UMTS o usb/92142 usb [uhub] SET_ADDR_FAILED and SHORT_XFER errors from usb o usb/92083 usb [ural] [panic] panic using WPA on ural NIC in 6.0-RELE o usb/92052 usb [ulpt] usbd causes defunct process with busy file-hand o usb/91906 usb [ehci] [hang] FreeBSD hangs while booting with USB leg o usb/91896 usb camcontrol(8): Serial Number of USB Memory Sticks is n o usb/91811 usb [umass] Compact Flash in HP Photosmart 2610 return " o usb/91629 usb [usb] usbd_abort_pipe() may result in infinite loop o usb/91546 usb [umodem] [patch] Nokia 6630 mobile phone does not work o usb/91538 usb [ulpt] [patch] Unable to print to EPSON CX3500 o usb/91283 usb [boot] [regression] booting very slow with usb devices o usb/91238 usb [umass] USB tape unit fails to write a second tape fil o usb/90700 usb [umass] [panic] Kernel panic on connect/mount/use umas o usb/89954 usb [umass] [panic] USB Disk driver race condition? s usb/89003 usb [request] LaCie Firewire drive not properly supported o usb/88743 usb [hang] [regression] USB makes kernel hang at boot (reg o usb/88408 usb [axe] axe0 read PHY failed o usb/87648 usb [mouse] Logitech USB-optical mouse problem. o usb/87224 usb [usb] Cannot mount USB Zip750 o usb/86767 usb [umass] [patch] bogus "slice starts beyond end of the o usb/86298 usb [mouse] Known good USB mouse won't work with correct s s usb/85067 usb [uscanner] Cannot attach ScanJet 4300C to usb device f usb/84750 usb [hang] 6-BETA2 reboot/shutdown with root_fs on externa s usb/84336 usb [usb] [reboot] instant system reboot when unmounting a o usb/84326 usb [umass] Panic trying to connect SCSI tape drive via US o usb/83977 usb [ucom] [panic] ucom1: open bulk out error (addr 2): IN o usb/83863 usb [ugen] Communication problem between opensc/openct via o usb/83756 usb [ums] [patch] Microsoft Intellimouse Explorer 4.0A doe f usb/83677 usb [usb] [request] usb controller often not detected (Sun o usb/83563 usb [umass] [panic] Page Fault while detaching Mpman Usb d o usb/83504 usb [kernel] [patch] SpeedTouch USB stop working on recent o usb/82660 usb [ehci] [panic] EHCI: I/O stuck in state 'physrd'/panic s usb/82569 usb [umass] [panic] USB mass storage plug/unplug causes sy o usb/82520 usb [udbp] [reboot] Reboot when USL101 connected o usb/82350 usb [ucom] [panic] null pointer dereference in USB stack o usb/81621 usb [ehci] [hang] external hd hangs under load on ehci o usb/80935 usb [uvisor] [patch] uvisor.c is not work with CLIE TH55. o usb/80862 usb [patch] USB locking issues: missing some Giant calls o usb/80854 usb [patch] [request] suggestion for new iface-no-probe me o usb/80829 usb [modules] [panic] possible panic when loading USB-modu s usb/80777 usb [request] usb_rem_task() should wait for callback to c s usb/80776 usb [udav] [request] UDAV device driver shouldn't use usb_ o usb/80774 usb [patch] have "usbd_find_desc" in line with the other " o usb/80361 usb [umass] [patch] mounting of Dell usb-stick fails o usb/80040 usb [hang] Use of sound mixer causes system freeze with ua o usb/79723 usb [usb] [request] prepare for high speed isochronous tra o usb/79722 usb [ehci] wrong alignments in ehci.h a usb/79656 usb [ehci] RHSC interrupts lost o usb/79524 usb [ulpt] printing to Minolta PagePro 1[23]xxW via USB fa o usb/79287 usb [uhci] [hang] UHCI hang after interrupt transfer o usb/79269 usb [ohci] USB ohci da0 plug/unplug causes crashes and loc o usb/78984 usb [umass] [patch] Creative MUVO umass failure o usb/77294 usb [ucom] [panic] ucom + ulpcom panic o usb/77184 usb [umass] [panic] kernel panic on USB device disconnect, o usb/76732 usb [ums] Mouse problems with USB KVM Switch o usb/76653 usb [umass] [patch] Problem with Asahi Optical usb device o usb/76461 usb [umass] disklabel of umass(4)-CAM(4)-da(4) not used by o usb/76395 usb [uhci] USB printer does not work, usbdevs says "addr 0 s usb/75928 usb [umass] [request] Cytronix SmartMedia card (SMC) reade o usb/75800 usb [ucom] ucom1: init failed STALLED error in time of syn o usb/75797 usb [sound] 5.3-STABLE(2005 1/4) detect USB headset, But c o usb/75764 usb [umass] [patch] "umass0: Phase Error" - no device for o usb/75705 usb [umass] [panic] da0 attach / Optio S4 (with backtrace) o usb/74771 usb [umass] [hang] mounting write-protected umass device a s usb/74453 usb [umass] [patch] Q-lity CD-RW USB ECW-043 (ScanLogic SL o usb/74211 usb [umass] USB flash drive causes CAM status 0x4 on 4.10R o usb/73307 usb [panic] Kernel panics on USB disconnect s usb/72733 usb [ucom] [request] Kyocera 7135 Palm OS connection probl o usb/71455 usb [umass] Slow USB umass performance of 5.3 o usb/71417 usb [ugen] Cryptoflex e-gate USB token (ugen0) communicati o usb/71416 usb [ugen] Cryptoflex e-gate USB token (ugen0) detach is n o usb/71280 usb [aue] aue0 device (linksys usb100tx) doesn't work in 1 o usb/71155 usb [ulpt] misbehaving usb-printer hangs processes, causes o usb/70523 usb [umct] [patch] umct sending/receiving wrong characters o usb/69006 usb [usbdevs] [patch] Apple Cinema Display hangs USB ports o usb/68232 usb [ugen] [patch] ugen(4) isochronous handling correction o usb/67301 usb [uftdi] [panic] RTS and system panic o usb/66547 usb [ucom] Palm Tungsten T USB does not initialize correct o usb/63621 usb [umass] [panic] USB MemoryStick Reader stalls/crashes s usb/62257 usb [umass] [request] card reader UCR-61S2B is only half-s o usb/59698 usb [keyboard] [patch] Rework of ukbd HID to AT code trans s bin/57255 usb [patch] usbd(8) and multi-function devices s usb/52026 usb [usb] [request] umass driver support for InSystem ISD2 s usb/51958 usb [urio] [patch] update for urio driver o i386/46371 usb USB controller cannot be initialized on IBM Netfinity o usb/40948 usb [umass] [request] USB HP CDW8200 does not work o usb/30929 usb [usb] [patch] use usbd to initialize USB ADSL modem 300 problems total. From christoph.mallon at gmx.de Mon Feb 9 03:36:15 2009 From: christoph.mallon at gmx.de (Christoph Mallon) Date: Mon Feb 9 03:36:22 2009 Subject: HEADSUP usb2/usb4bsd to become default in GENERIC In-Reply-To: <49901276.5040604@gmx.de> References: <20090206045349.GQ78804@elvis.mu.org> <49901276.5040604@gmx.de> Message-ID: <49901399.8070409@gmx.de> Christoph Mallon schrieb: > are named "err" or "error". This should be investigated, so here's the > complete list: Sorry, my MUA seems to have damaged the list. You can get the list here: http://tron.homeunix.org/usb2.unread.log From christoph.mallon at gmx.de Mon Feb 9 03:51:22 2009 From: christoph.mallon at gmx.de (Christoph Mallon) Date: Mon Feb 9 03:51:29 2009 Subject: HEADSUP usb2/usb4bsd to become default in GENERIC In-Reply-To: <20090206045349.GQ78804@elvis.mu.org> References: <20090206045349.GQ78804@elvis.mu.org> Message-ID: <49901276.5040604@gmx.de> Alfred Perlstein schrieb: > Hello -current and -usb. > > We are in the final stages of bringing in the new usb > stack. [...] > At this point we expect there to be no style or changes in usb2 > that are not bugfixes until Phase 3 "Hand off". The reason for > this is to prevent bugs from creeping in and allow the maintainer > to focus 100% on bugs and feature parity with the oldusb stack. cparser identifies 40 variables in libusb20 and the usb2 code, which are only assigned, but never read. I think it's worrisome that 12 of these are named "err" or "error". This should be investigated, so here's the complete list: > lib/libusb20/libusb20_desc.c:509: warning: variable 'dummy' is never read > lib/libusb20/libusb20_desc.c:665: warning: variable 'dummy' is never read > sys/dev/usb2/controller/at91dci.c:1829: warning: variable 'use_polling' is never read > sys/dev/usb2/controller/at91dci_atmelarm.c:77: warning: variable 'temp' is never read > sys/dev/usb2/controller/at91dci_atmelarm.c:250: warning: variable 'err' is never read > sys/dev/usb2/controller/atmegadci.c:777: warning: variable 'sc' is never read > sys/dev/usb2/controller/atmegadci.c:780: warning: variable 'ep_no' is never read > sys/dev/usb2/controller/atmegadci.c:1698: warning: variable 'use_polling' is never read > sys/dev/usb2/controller/atmegadci.c:2151: warning: variable 'sc' is never read > sys/dev/usb2/controller/ehci2.c:2308: warning: variable 'slot' is never read > sys/dev/usb2/controller/musb2_otg.c:899: warning: variable 'sc' is never read > sys/dev/usb2/controller/musb2_otg.c:1124: warning: variable 'sc' is never read > sys/dev/usb2/controller/musb2_otg.c:1127: warning: variable 'ep_no' is never read > sys/dev/usb2/controller/musb2_otg.c:2235: warning: variable 'use_polling' is never read > sys/dev/usb2/controller/musb2_otg.c:2697: warning: variable 'sc' is never read > sys/dev/usb2/controller/musb2_otg_atmelarm.c:165: warning: variable 'err' is never read > sys/dev/usb2/controller/ohci2.c:2501: warning: variable 'sc' is never read > sys/dev/usb2/controller/ohci2_atmelarm.c:151: warning: variable 'err' is never read > sys/dev/usb2/controller/uhci2.c:1297: warning: variable 'token' is never read > sys/dev/usb2/controller/uhci2.c:2986: warning: variable 'sc' is never read > sys/dev/usb2/controller/uss820dci.c:821: warning: variable 'sc' is never read > sys/dev/usb2/controller/uss820dci.c:824: warning: variable 'ep_no' is never read > sys/dev/usb2/controller/uss820dci.c:1847: warning: variable 'use_polling' is never read > sys/dev/usb2/controller/uss820dci_atmelarm.c:206: warning: variable 'err' is never read > sys/dev/usb2/core/usb2_busdma.c:202: warning: variable 'error' is never read > sys/dev/usb2/core/usb2_compat_linux.c:337: warning: variable 'err' is never read > sys/dev/usb2/core/usb2_compat_linux.c:355: warning: variable 'err' is never read > sys/dev/usb2/core/usb2_compat_linux.c:1181: warning: variable 'err' is never read > sys/dev/usb2/core/usb2_compat_linux.c:1274: warning: variable 'err' is never read > sys/dev/usb2/core/usb2_dev.c:1753: warning: variable 'resid' is never read > sys/dev/usb2/core/usb2_dev.c:1896: warning: variable 'resid' is never read > sys/dev/usb2/core/usb2_device.c:925: warning: variable 'err' is never read > sys/dev/usb2/core/usb2_util.c:275: warning: variable 'err' is never read > sys/dev/usb2/serial/umoscom2.c:525: warning: variable 'lsr' is never read > sys/dev/usb2/sound/uaudio2.c:795: warning: variable 'ep_sync' is never read > sys/dev/usb2/sound/uaudio2.c:2001: warning: variable 'd1' is never read > sys/dev/usb2/storage/ata-usb2.c:328: warning: variable 'has_intr' is never read > sys/dev/usb2/storage/umass2.c:1636: warning: variable 'err' is never read > sys/dev/usb2/storage/ustorage2_fs.c:906: warning: variable 'file_offset' is never read > sys/dev/usb2/storage/ustorage2_fs.c:907: warning: variable 'amount_left' is never read (For easy processing copy the list into $FILE and use "vim -q $FILE") Regards Christoph From hselasky at c2i.net Mon Feb 9 05:47:42 2009 From: hselasky at c2i.net (Hans Petter Selasky) Date: Mon Feb 9 05:47:55 2009 Subject: HEADSUP usb2/usb4bsd to become default in GENERIC In-Reply-To: <49901399.8070409@gmx.de> References: <20090206045349.GQ78804@elvis.mu.org> <49901276.5040604@gmx.de> <49901399.8070409@gmx.de> Message-ID: <200902091450.07014.hselasky@c2i.net> On Monday 09 February 2009, Christoph Mallon wrote: > Christoph Mallon schrieb: > > are named "err" or "error". This should be investigated, so here's the > > complete list: > > Sorry, my MUA seems to have damaged the list. You can get the list here: > http://tron.homeunix.org/usb2.unread.log I think some of these errors depend if you have USB debugging compiled or not. At least GCC does not warn? --HPS From christoph.mallon at gmx.de Mon Feb 9 06:08:34 2009 From: christoph.mallon at gmx.de (Christoph Mallon) Date: Mon Feb 9 06:08:41 2009 Subject: HEADSUP usb2/usb4bsd to become default in GENERIC In-Reply-To: <200902091450.07014.hselasky@c2i.net> References: <20090206045349.GQ78804@elvis.mu.org> <49901276.5040604@gmx.de> <49901399.8070409@gmx.de> <200902091450.07014.hselasky@c2i.net> Message-ID: <499038DE.3050501@gmx.de> Hans Petter Selasky schrieb: > On Monday 09 February 2009, Christoph Mallon wrote: >> Christoph Mallon schrieb: >>> are named "err" or "error". This should be investigated, so here's the >>> complete list: >> Sorry, my MUA seems to have damaged the list. You can get the list here: >> http://tron.homeunix.org/usb2.unread.log > > I think some of these errors depend if you have USB debugging compiled or not. > At least GCC does not warn? No, it does not depend on USB debugging. GCC has no warning at all for variables which are only assigned to. It only can warn about variables, which are only initialised. { int x = 23; // GCC warns here ... int y; // ... but not here - cparser does y = 42; y++; } cparser has an analysis, which can warn about "y", too. I manually verified all 40 warnings and I cannot find any users (i.e. readers) for these variables. From bholman at focusfcu.org Mon Feb 9 06:18:03 2009 From: bholman at focusfcu.org (Bradford L. Holman) Date: Mon Feb 9 06:18:16 2009 Subject: TUSB3410 / uticom-.3 Problem Message-ID: <0CF0BD39CCE55942A18E908919C32B7B2CBB84@focus-srv6.focusfcu.org> I am trying to use a USB to Serial adapter & it is being recognized by the system. However, when I go to install the uticom port, I get the error: ? # make install ===> Vulnerability check disabled, database not found => uticom-0.3.tar.gz doesn't seem to exist in /usr/ports/distfiles/. => Attempting to fetch from http://heanet.dl.sourceforge.net/sourceforge/uticom/. uticom-0.3.tar.gz 100% of 13 kB 30 kBps ===> Extracting for uticom-0.3 => MD5 Checksum OK for uticom-0.3.tar.gz. => No SHA256 checksum recorded for uticom-0.3.tar.gz. ===> Patching for uticom-0.3 ===> Configuring for uticom-0.3 ===> Building for uticom-0.3 Warning: Object directory not changed from original /usr/ports/comms/uticom/work/uticom-0.3 @ -> /usr/src/sys machine -> /usr/src/sys/i386/include awk -f @/tools/makeobjops.awk @/kern/device_if.m -h awk -f @/tools/makeobjops.awk @/kern/bus_if.m -h awk -f @/tools/makeobjops.awk @/dev/pci/pci_if.m -h awk -f @/tools/vnode_if.awk @/kern/vnode_if.src -p awk -f @/tools/vnode_if.awk @/kern/vnode_if.src -q awk -f @/tools/vnode_if.awk @/kern/vnode_if.src -h :> opt_uticom.h :> opt_usb.h awk -f @/tools/usbdevs2h.awk @/dev/usb/usbdevs -h cc -O2 -fno-strict-aliasing -pipe -D_KERNEL -DKLD_MODULE -std=c99 -nostdinc -I. -I@ -I@/contrib/altq -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -fno-common -mno-align-long-strings -mpreferred-stack-boundary=2 -mno-mmx -mno-3dnow -mno-sse -mno-sse2 -mno-sse3 -ffreestanding -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -c uticom.c uticom.c:102:20: error: unistd.h: No such file or directory uticom.c:206: error: expected '=', ',', ';', 'asm' or '__attribute__' before 'usbd_status' uticom.c:207: error: expected '=', ',', ';', 'asm' or '__attribute__' before 'usbd_status' uticom.c:209: error: expected '=', ',', ';', 'asm' or '__attribute__' before 'usbd_status' uticom.c:210: error: expected '=', ',', ';', 'asm' or '__attribute__' before 'void' uticom.c:212: error: expected '=', ',', ';', 'asm' or '__attribute__' before 'void' uticom.c:213: error: expected '=', ',', ';', 'asm' or '__attribute__' before 'void' uticom.c:214: error: expected '=', ',', ';', 'asm' or '__attribute__' before 'void' uticom.c:215: error: expected '=', ',', ';', 'asm' or '__attribute__' before 'void' uticom.c:216: error: expected '=', ',', ';', 'asm' or '__attribute__' before 'void' uticom.c:217:5: warning: "TODO" is not defined uticom.c:220: error: expected '=', ',', ';', 'asm' or '__attribute__' before 'int' uticom.c:221: error: expected '=', ',', ';', 'asm' or '__attribute__' before 'int' uticom.c:222: error: expected '=', ',', ';', 'asm' or '__attribute__' before 'void' uticom.c:228: error: 'uticom_get_status' undeclared here (not in a function) uticom.c:229: error: 'uticom_set' undeclared here (not in a function) uticom.c:230: error: 'uticom_param' undeclared here (not in a function) uticom.c:232: error: 'uticom_open' undeclared here (not in a function) uticom.c:233: error: 'uticom_close' undeclared here (not in a function) uticom.c:249: error: expected '=', ',', ';', 'asm' or '__attribute__' before 'device_probe_t' uticom.c:250: error: expected '=', ',', ';', 'asm' or '__attribute__' before 'device_attach_t' uticom.c:251: error: expected '=', ',', ';', 'asm' or '__attribute__' before 'device_detach_t' uticom.c:253: error: expected '=', ',', ';', 'asm' or '__attribute__' before 'kobj_method_t' uticom.c:261: error: expected '=', ',', ';', 'asm' or '__attribute__' before 'driver_t' uticom.c:267: error: 'uticom_driver' undeclared here (not in a function) uticom.c:324: warning: return type defaults to 'int' uticom.c:324: warning: function declaration isn't a prototype uticom.c: In function 'USB_MATCH': uticom.c:324: warning: type of 'uticom' defaults to 'int' uticom.c:326: warning: implicit declaration of function 'USB_MATCH_START' uticom.c:326: warning: nested extern declaration of 'USB_MATCH_START' uticom.c:326: error: 'uaa' undeclared (first use in this function) uticom.c:326: error: (Each undeclared identifier is reported only once uticom.c:326: error: for each function it appears in.) uticom.c: At top level: uticom.c:343: warning: return type defaults to 'int' uticom.c:343: warning: function declaration isn't a prototype uticom.c: In function 'USB_ATTACH': uticom.c:343: warning: type of 'uticom' defaults to 'int' uticom.c:345: warning: implicit declaration of function 'USB_ATTACH_START' uticom.c:345: warning: nested extern declaration of 'USB_ATTACH_START' uticom.c:345: error: 'sc' undeclared (first use in this function) uticom.c:345: error: 'uaa' undeclared (first use in this function) uticom.c:368: error: 'self' undeclared (first use in this function) uticom.c:376: warning: implicit declaration of function 'USBDEVNAME' uticom.c:376: warning: nested extern declaration of 'USBDEVNAME' uticom.c:376: warning: assignment makes pointer from integer without a cast uticom.c:413: warning: format '%s' expects type 'char *', but argument 2 has type 'int' uticom.c:437: warning: format '%s' expects type 'char *', but argument 2 has type 'int' uticom.c:451: warning: format '%s' expects type 'char *', but argument 2 has type 'int' uticom.c:482: warning: assignment makes pointer from integer without a cast uticom.c:503: warning: format '%s' expects type 'char *', but argument 2 has type 'int' uticom.c:510: warning: assignment makes pointer from integer without a cast uticom.c:536: warning: format '%s' expects type 'char *', but argument 2 has type 'int' uticom.c:553: warning: format '%s' expects type 'char *', but argument 2 has type 'int' uticom.c:585: warning: format '%s' expects type 'char *', but argument 2 has type 'int' uticom.c:601: warning: format '%s' expects type 'char *', but argument 2 has type 'int' uticom.c:608: warning: format '%s' expects type 'char *', but argument 2 has type 'int' uticom.c:625: warning: implicit declaration of function 'uticom_reset' uticom.c:625: warning: nested extern declaration of 'uticom_reset' uticom.c:629: warning: format '%s' expects type 'char *', but argument 2 has type 'int' uticom.c:641: error: 'USB_ATTACH_SUCCESS_RETURN' undeclared (first use in this function) uticom.c:645: error: 'USB_ATTACH_ERROR_RETURN' undeclared (first use in this function) uticom.c: At top level: uticom.c:650: warning: return type defaults to 'int' uticom.c:650: warning: function declaration isn't a prototype uticom.c: In function 'USB_DETACH': uticom.c:650: warning: type of 'uticom' defaults to 'int' uticom.c:652: warning: implicit declaration of function 'USB_DETACH_START' uticom.c:652: warning: nested extern declaration of 'USB_DETACH_START' uticom.c:652: error: 'sc' undeclared (first use in this function) uticom.c: At top level: uticom.c:672: error: expected '=', ',', ';', 'asm' or '__attribute__' before 'usbd_status' uticom.c:697: error: expected '=', ',', ';', 'asm' or '__attribute__' before 'void' uticom.c:719: error: expected '=', ',', ';', 'asm' or '__attribute__' before 'void' uticom.c:747: error: expected '=', ',', ';', 'asm' or '__attribute__' before 'void' uticom.c:777: error: expected '=', ',', ';', 'asm' or '__attribute__' before 'void' uticom.c:800: error: expected '=', ',', ';', 'asm' or '__attribute__' before 'usbd_status' uticom.c:825: error: expected '=', ',', ';', 'asm' or '__attribute__' before 'usbd_status' uticom.c:922: error: expected '=', ',', ';', 'asm' or '__attribute__' before 'int' uticom.c:973: error: expected '=', ',', ';', 'asm' or '__attribute__' before 'int' uticom.c:1017: error: expected '=', ',', ';', 'asm' or '__attribute__' before 'void' uticom.c:1062: error: expected '=', ',', ';', 'asm' or '__attribute__' before 'void' uticom.c:1137: error: expected '=', ',', ';', 'asm' or '__attribute__' before 'void' uticom.c:1154:5: warning: "TODO" is not defined uticom.c: In function 'ti_download_firmware': uticom.c:1230: warning: format '%s' expects type 'char *', but argument 2 has type 'int' *** Error code 1 Stop in /usr/ports/comms/uticom/work/uticom-0.3. *** Error code 1 Stop in /usr/ports/comms/uticom. ? The output of usbdevs -v is: # usbdevs -v Controller /dev/usb0: addr 1: full speed, self powered, config 1, UHCI root hub(0x0000), Intel(0x0000), rev 1.00 port 1 powered port 2 addr 2: low speed, power 98 mA, config 1, KVM(0x5a08), No brand(0x10d5), rev 0.00 Controller /dev/usb1: addr 1: full speed, self powered, config 1, UHCI root hub(0x0000), Intel(0x0000), rev 1.00 port 1 addr 2: full speed, power 100 mA, config 1, TUSB3410 Serial Port(0xf111), Texas Instruments(0x06e0), rev 1.01 port 2 powered It seems like the port is missing a header or something. I noticed the missing file warning for unistd.h, and could repair it by adding "sys/" to its reference in uticom.c, but the rest of the errors persist. Any ideas? Please advise. Thanks. Bradford L. Holman, MBA Director of IT http://focusfcu.org/ E: bholman@focusfcu.org P: (405) 230-1328 ext. 118 F: (405) 235-0067 EVERY MEMBER. EVERY ACCOUNT. EVERY TIME! CONFIDENTIALITY NOTICE: The information contained in this message is intended only for the recipient and may contain information that is confidential. If you are not the intended recipient or an employee or agent responsible for delivering this message to the intended recipient; please be aware that any dissemination, forwarding, printing, copying, disclosure or distribution of this communication is strictly prohibited. If you have received this communication in error, please immediately notify the sender by replying to the message and deleting all copies, including attachments, from your system. From hselasky at c2i.net Mon Feb 9 06:31:47 2009 From: hselasky at c2i.net (Hans Petter Selasky) Date: Mon Feb 9 06:32:08 2009 Subject: HEADSUP usb2/usb4bsd to become default in GENERIC In-Reply-To: <499038DE.3050501@gmx.de> References: <20090206045349.GQ78804@elvis.mu.org> <200902091450.07014.hselasky@c2i.net> <499038DE.3050501@gmx.de> Message-ID: <200902091534.12506.hselasky@c2i.net> On Monday 09 February 2009, Christoph Mallon wrote: > Hans Petter Selasky schrieb: > > On Monday 09 February 2009, Christoph Mallon wrote: > >> Christoph Mallon schrieb: > >>> are named "err" or "error". This should be investigated, so here's the > >>> complete list: > >> > >> Sorry, my MUA seems to have damaged the list. You can get the list here: > >> http://tron.homeunix.org/usb2.unread.log > > > > I think some of these errors depend if you have USB debugging compiled or > > not. At least GCC does not warn? > > No, it does not depend on USB debugging. > GCC has no warning at all for variables which are only assigned to. > It only can warn about variables, which are only initialised. > > { > int x = 23; // GCC warns here ... > int y; // ... but not here - cparser does > y = 42; > y++; > } > > cparser has an analysis, which can warn about "y", too. > > I manually verified all 40 warnings and I cannot find any users (i.e. > readers) for these variables. What is the correct way to discard the return argument of a function? That's basically what most of the warnings are about. 1) (void)my_fn() cast 2) if (my_fn()) { } 3) err = my_fn(); 4) my_fn(); --HPS From christoph.mallon at gmx.de Mon Feb 9 06:48:30 2009 From: christoph.mallon at gmx.de (Christoph Mallon) Date: Mon Feb 9 06:48:46 2009 Subject: HEADSUP usb2/usb4bsd to become default in GENERIC In-Reply-To: <200902091534.12506.hselasky@c2i.net> References: <20090206045349.GQ78804@elvis.mu.org> <200902091450.07014.hselasky@c2i.net> <499038DE.3050501@gmx.de> <200902091534.12506.hselasky@c2i.net> Message-ID: <49904238.50505@gmx.de> Hans Petter Selasky schrieb: > On Monday 09 February 2009, Christoph Mallon wrote: >> Hans Petter Selasky schrieb: >>> On Monday 09 February 2009, Christoph Mallon wrote: >>>> Christoph Mallon schrieb: >>>>> are named "err" or "error". This should be investigated, so here's the >>>>> complete list: >>>> Sorry, my MUA seems to have damaged the list. You can get the list here: >>>> http://tron.homeunix.org/usb2.unread.log >>> I think some of these errors depend if you have USB debugging compiled or >>> not. At least GCC does not warn? >> No, it does not depend on USB debugging. >> GCC has no warning at all for variables which are only assigned to. >> It only can warn about variables, which are only initialised. >> >> { >> int x = 23; // GCC warns here ... >> int y; // ... but not here - cparser does >> y = 42; >> y++; >> } >> >> cparser has an analysis, which can warn about "y", too. >> >> I manually verified all 40 warnings and I cannot find any users (i.e. >> readers) for these variables. > > What is the correct way to discard the return argument of a function? That's > basically what most of the warnings are about. > > 1) (void)my_fn() cast > 2) if (my_fn()) { } > 3) err = my_fn(); > 4) my_fn(); Just to understand this correctly: You want to discard error codes? Basically I see four categories: 1) Getting the softc and not using it. This can be removed completely. Example: sc = ATMEGA_BUS2SC(xfer->xroot->bus); 2) calling mtx_owned() and discarding the return value. Can be removed, too, after checking that the value is really unnecessary. Example: use_polling = mtx_owned(xfer->xroot->xfer_mtx) ? 1 : 0; 3) Getting some value and not using it. Can be removed, too, after checking that the value is really unnecessary. Example: ep_no = (xfer->endpoint & UE_ADDR); 4) The rest are return values of functions, which contain error codes. Discarding them is questionable at best. Example: (err is not read) if (udev->flags.suspended) { err = DEVICE_SUSPEND(iface->subdev); device_printf(iface->subdev, "Suspend failed\n"); } return (0); /* success */ From imp at bsdimp.com Mon Feb 9 07:58:19 2009 From: imp at bsdimp.com (M. Warner Losh) Date: Mon Feb 9 07:58:26 2009 Subject: USB2 - umass problem In-Reply-To: <200902091035.26738.nick@anywi.com> References: <200902041044.27663.hselasky@c2i.net> <20090204.085606.1630229139.imp@bsdimp.com> <200902091035.26738.nick@anywi.com> Message-ID: <20090209.085417.1342145568.imp@bsdimp.com> In message: <200902091035.26738.nick@anywi.com> Nick Hibma writes: : > : > By some reason devfs semantic was changed: : > : > Instead of /dev/cuaU0.[0-2] and /dev/ttyU0.[0-2], I've get : > : > /dev/cuaU[0-2] /dev/ttyU[0-2] and! /dev/cuau1 /dev/ttyu1 : > : > What is reason for such change (additional port with lowercase 'u' : > : > and U[0-2] instead of more logical U0.[0-2]) ? : > : : > : It is because we are attaching drivers per interface instead of per : > : device. A new modem unit is allocated every time we find a modem, : > : simply put. If the modem has multiple instances in an interface, : > : /dev/cuaU0.[0...] will be created. Else /dev/cuaU... . : > : > Generally, we try not to change the details of how a device attaches : > /dev entries from release to release. Why the change? : : The USB1 u3g driver also attaches to interfaces, but collects all interfaces : in one go, leaving all unused interfaces available for other drivers (e.g. : umass) or claims them (to hide the 'driver disks'). It is the main reason : why I wrote a separate driver in the first place. Otherwise the UMTS cards : could be treated as serial ports without any port singalling. : : It is important to be able to determine in an automated way the 2 or more : serial ports that belong together. As an example: If you create a router : box that automatically configures itself depending on the hardware it : finds, we somehow need to find out which two serial ports are found on each : GPRS/UMTS card, so we can assign the first one to PPP and the other one to : our control application. If the devices have serial numbers, then I think that's published in the sysctl tree... Warner From hselasky at c2i.net Mon Feb 9 08:06:11 2009 From: hselasky at c2i.net (Hans Petter Selasky) Date: Mon Feb 9 08:06:17 2009 Subject: HEADSUP usb2/usb4bsd to become default in GENERIC In-Reply-To: <49904238.50505@gmx.de> References: <20090206045349.GQ78804@elvis.mu.org> <200902091534.12506.hselasky@c2i.net> <49904238.50505@gmx.de> Message-ID: <200902091608.34376.hselasky@c2i.net> On Monday 09 February 2009, Christoph Mallon wrote: > Hans Petter Selasky schrieb: > > On Monday 09 February 2009, Christoph Mallon wrote: > >> Hans Petter Selasky schrieb: > >>> On Monday 09 February 2009, Christoph Mallon wrote: > >>>> Christoph Mallon schrieb: > >>>>> are named "err" or "error". This should be investigated, so here's > >>>>> the complete list: > >>>> > >>>> Sorry, my MUA seems to have damaged the list. You can get the list > >>>> here: http://tron.homeunix.org/usb2.unread.log > >>> > >>> I think some of these errors depend if you have USB debugging compiled > >>> or not. At least GCC does not warn? > >> > >> No, it does not depend on USB debugging. > >> GCC has no warning at all for variables which are only assigned to. > >> It only can warn about variables, which are only initialised. > >> > >> { > >> int x = 23; // GCC warns here ... > >> int y; // ... but not here - cparser does > >> y = 42; > >> y++; > >> } > >> > >> cparser has an analysis, which can warn about "y", too. > >> > >> I manually verified all 40 warnings and I cannot find any users (i.e. > >> readers) for these variables. > > > > What is the correct way to discard the return argument of a function? > > That's basically what most of the warnings are about. > > > > 1) (void)my_fn() cast > > 2) if (my_fn()) { } > > 3) err = my_fn(); > > 4) my_fn(); > > Just to understand this correctly: You want to discard error codes? > > > Basically I see four categories: > > 1) Getting the softc and not using it. > This can be removed completely. > Example: > sc = ATMEGA_BUS2SC(xfer->xroot->bus); > > 2) calling mtx_owned() and discarding the return value. > Can be removed, too, after checking that the value is really unnecessary. > Example: > use_polling = mtx_owned(xfer->xroot->xfer_mtx) ? 1 : 0; > > 3) Getting some value and not using it. > Can be removed, too, after checking that the value is really unnecessary. > Example: > ep_no = (xfer->endpoint & UE_ADDR); > > 4) The rest are return values of functions, which contain error codes. > Discarding them is questionable at best. > Example: (err is not read) > if (udev->flags.suspended) { > err = DEVICE_SUSPEND(iface->subdev); > device_printf(iface->subdev, "Suspend failed\n"); > } > return (0); /* success */ Hi, Can you wait some days and re-run the analysis on -current, because there is a bulk of patches going in to some of the code you have analysed, so the line numbers are likely to not match. Then we fix those warnings! --HPS From keramida at ceid.upatras.gr Mon Feb 9 10:18:07 2009 From: keramida at ceid.upatras.gr (Giorgos Keramidas) Date: Mon Feb 9 10:18:15 2009 Subject: HEADSUP usb2/usb4bsd to become default in GENERIC In-Reply-To: <200902091534.12506.hselasky@c2i.net> (Hans Petter Selasky's message of "Mon, 9 Feb 2009 15:34:11 +0100") References: <20090206045349.GQ78804@elvis.mu.org> <200902091450.07014.hselasky@c2i.net> <499038DE.3050501@gmx.de> <200902091534.12506.hselasky@c2i.net> Message-ID: <87ocxbpj8t.fsf@kobe.laptop> On Mon, 9 Feb 2009 15:34:11 +0100, Hans Petter Selasky wrote: > On Monday 09 February 2009, Christoph Mallon wrote: >> Hans Petter Selasky schrieb: >> > On Monday 09 February 2009, Christoph Mallon wrote: >> >> Christoph Mallon schrieb: >> >>> are named "err" or "error". This should be investigated, so here's the >> >>> complete list: >> >> >> >> Sorry, my MUA seems to have damaged the list. You can get the list here: >> >> http://tron.homeunix.org/usb2.unread.log >> > >> > I think some of these errors depend if you have USB debugging compiled or >> > not. At least GCC does not warn? >> >> No, it does not depend on USB debugging. >> GCC has no warning at all for variables which are only assigned to. >> It only can warn about variables, which are only initialised. >> >> { >> int x = 23; // GCC warns here ... >> int y; // ... but not here - cparser does >> y = 42; >> y++; >> } >> >> cparser has an analysis, which can warn about "y", too. >> >> I manually verified all 40 warnings and I cannot find any users (i.e. >> readers) for these variables. > > What is the correct way to discard the return argument of a function? > That's basically what most of the warnings are about. > > 1) (void)my_fn() cast > 2) if (my_fn()) { } > 3) err = my_fn(); > 4) my_fn(); If you *really* don't care about the returned error code: (void)function(arg1, arg2, ...); From yanefbsd at gmail.com Mon Feb 9 11:20:43 2009 From: yanefbsd at gmail.com (Garrett Cooper) Date: Mon Feb 9 11:20:49 2009 Subject: Future of udbp in USB2? In-Reply-To: <200902090916.54896.hselasky@c2i.net> References: <7d6fde3d0902081703l71bc1de8g9bb7baf6b9b050c8@mail.gmail.com> <200902090916.54896.hselasky@c2i.net> Message-ID: <7d6fde3d0902091120w33c2909bma1d397114c404c1d@mail.gmail.com> On Mon, Feb 9, 2009 at 12:16 AM, Hans Petter Selasky wrote: > On Monday 09 February 2009, Garrett Cooper wrote: >> Hi Hans, >> I was just preparing to test out the usb2 changes and I noted that >> one option in my old kernel configfile didn't have an analog in the >> USB2 config file: udbp. >> I don't use the option, but I was just checking to see whether or >> not an analog does exist, or the support will be completely phased out >> when USB2 becomes the default for FreeBSD. >> Thanks, >> -Garrett > > Hi, > > The udbp module is now called "misc_dbp" and it still connects via netgraph. > Other similar devices just emulate USB ethernet devices. > > --HPS Ok... is that going to be documented in the release notes for the new functionality? -Garrett From thompsa at FreeBSD.org Mon Feb 9 11:58:34 2009 From: thompsa at FreeBSD.org (Andrew Thompson) Date: Mon Feb 9 11:58:40 2009 Subject: Future of udbp in USB2? In-Reply-To: <7d6fde3d0902091120w33c2909bma1d397114c404c1d@mail.gmail.com> References: <7d6fde3d0902081703l71bc1de8g9bb7baf6b9b050c8@mail.gmail.com> <200902090916.54896.hselasky@c2i.net> <7d6fde3d0902091120w33c2909bma1d397114c404c1d@mail.gmail.com> Message-ID: <20090209195827.GB67127@citylink.fud.org.nz> On Mon, Feb 09, 2009 at 11:20:42AM -0800, Garrett Cooper wrote: > On Mon, Feb 9, 2009 at 12:16 AM, Hans Petter Selasky wrote: > > On Monday 09 February 2009, Garrett Cooper wrote: > >> Hi Hans, > >> I was just preparing to test out the usb2 changes and I noted that > >> one option in my old kernel configfile didn't have an analog in the > >> USB2 config file: udbp. > >> I don't use the option, but I was just checking to see whether or > >> not an analog does exist, or the support will be completely phased out > >> when USB2 becomes the default for FreeBSD. > >> Thanks, > >> -Garrett > > > > Hi, > > > > The udbp module is now called "misc_dbp" and it still connects via netgraph. > > Other similar devices just emulate USB ethernet devices. > > > > --HPS > > Ok... is that going to be documented in the release notes for the new > functionality? All the modules should go back to their original names as part of the removal/replacement process of oldusb->newusb. Andrew From thompsa at FreeBSD.org Mon Feb 9 12:00:21 2009 From: thompsa at FreeBSD.org (Andrew Thompson) Date: Mon Feb 9 12:00:27 2009 Subject: Future of udbp in USB2? In-Reply-To: <20090209195827.GB67127@citylink.fud.org.nz> References: <7d6fde3d0902081703l71bc1de8g9bb7baf6b9b050c8@mail.gmail.com> <200902090916.54896.hselasky@c2i.net> <7d6fde3d0902091120w33c2909bma1d397114c404c1d@mail.gmail.com> <20090209195827.GB67127@citylink.fud.org.nz> Message-ID: <20090209200016.GC67127@citylink.fud.org.nz> On Mon, Feb 09, 2009 at 11:58:28AM -0800, Andrew Thompson wrote: > On Mon, Feb 09, 2009 at 11:20:42AM -0800, Garrett Cooper wrote: > > On Mon, Feb 9, 2009 at 12:16 AM, Hans Petter Selasky wrote: > > > On Monday 09 February 2009, Garrett Cooper wrote: > > >> Hi Hans, > > >> I was just preparing to test out the usb2 changes and I noted that > > >> one option in my old kernel configfile didn't have an analog in the > > >> USB2 config file: udbp. > > >> I don't use the option, but I was just checking to see whether or > > >> not an analog does exist, or the support will be completely phased out > > >> when USB2 becomes the default for FreeBSD. > > >> Thanks, > > >> -Garrett > > > > > > Hi, > > > > > > The udbp module is now called "misc_dbp" and it still connects via netgraph. > > > Other similar devices just emulate USB ethernet devices. > > > > > > --HPS > > > > Ok... is that going to be documented in the release notes for the new > > functionality? > > All the modules should go back to their original names as part of the > removal/replacement process of oldusb->newusb. I meant to say /will/. From alfred at freebsd.org Mon Feb 9 12:19:15 2009 From: alfred at freebsd.org (Alfred Perlstein) Date: Mon Feb 9 12:19:21 2009 Subject: HEADSUP usb2/usb4bsd to become default in GENERIC In-Reply-To: <20090208.124756.-942592244.imp@bsdimp.com> References: <8b3974a5f1b260fd438518f703aee2f5.squirrel@galain.elvandar.org> <20090208183820.GA21343@citylink.fud.org.nz> <200902081951.16823.hselasky@c2i.net> <20090208.124756.-942592244.imp@bsdimp.com> Message-ID: <20090209201914.GM68801@elvis.mu.org> * M. Warner Losh [090208 11:48] wrote: > In message: <200902081951.16823.hselasky@c2i.net> > Hans Petter Selasky writes: > : On Sunday 08 February 2009, Andrew Thompson wrote: > : > On Sun, Feb 08, 2009 at 06:48:39PM +0100, Remko Lodder wrote: > : > > On Sun, February 8, 2009 6:21 am, Alfred Perlstein wrote: > : > : > > > : > > Please name it "usb_*". > : > : Beware that if you rename everything from "usb2_" to "usb_" there will be > : symbol and structure clashes with the linux USB compat layer, which needs to > : be resolved. > > No. that's not the case. usb2_foo vs usb_foo in the kernel config > files only affects what files config brings in, and we can easily tell > it to bring the right ones in w/o any symbol issues. > > I'd leave everything else where it is now in the source tree. The > rename is fairly trivial. Do people want me to float a patch? That would be useful, but it might be premature as there might be changes that conflict shortly (not trying to hide information, just don't know what changes might happen). If you can schedule to do this at the time for the rename (when the remove happens) that would be best. -Alfred From alfred at freebsd.org Mon Feb 9 12:21:13 2009 From: alfred at freebsd.org (Alfred Perlstein) Date: Mon Feb 9 12:21:32 2009 Subject: HEADSUP usb2/usb4bsd to become default in GENERIC In-Reply-To: <1234119008.7997.32.camel@buffy.york.ac.uk> References: <20090206045349.GQ78804@elvis.mu.org> <498C013B.4000405@FreeBSD.org> <20090208052110.GY78804@elvis.mu.org> <1234119008.7997.32.camel@buffy.york.ac.uk> Message-ID: <20090209202112.GN68801@elvis.mu.org> * Gavin Atkinson [090208 10:50] wrote: > On Sat, 2009-02-07 at 21:21 -0800, Alfred Perlstein wrote: > > * Maxim Sobolev [090206 01:50] wrote: > > > Alfred Perlstein wrote: > > > > - Update GENERIC to use usb2 device names. > > > > > > Wasn't there a plan to rename usb2 devices to match oldusb names (where > > > applicable) once oldusb had been killed? I don't see it in the list. > > > > Probably, although coming from the other side as a user I find it pretty > > annoying when there's somewhat gratuitous changes to the kernel config > > files that I don't really care about that cause my kernels to break. > > The vast majority of our users do not run -CURRENT, and so haven't had > to change config files yet. > > One day, those users will be migrating from 7.x to 8.x, and shouldn't > need to change their kernel config for a "somewhat gratuitous change". > > Your argument only works if people had already had to change their > config files once (usb -> usb2), and that by renaming these back they > will have to change their kernel config back. Only people running > -CURRENT will end up having to do this twice (or indeed at all) if the > rename takes place, end users will not need to do it at all. > > > Basically, calling it usb2 isn't as bad as renaming it back to "usb" > > as it's less disruptive in my book. > > Again, I disagree. Your point is very good! I hadn't thought about 7 users coming to 8 and having the rename actually be a nice thing for them. I was a bit more concerned with backlash from developers for churn, but your point makes a lot of sense. thanks, -- - Alfred Perlstein From matheus at eternamente.info Mon Feb 9 20:42:07 2009 From: matheus at eternamente.info (Nenhum_de_Nos) Date: Mon Feb 9 20:42:13 2009 Subject: ADMtek USB To LAN Converter Message-ID: <3a417368cbade2b459503d6bcbaa0601.squirrel@10.1.1.10> hail, I have two of these and cant make them ping. module loads ok, ifconfig sees ok, but cant send any data. tcpdump can get info though. aue0: on uhub1 miibus3: on aue0 ukphy1: PHY 1 on miibus3 ukphy1: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto aue0: Ethernet address: 00:60:6e:00:05:d2 aue0: link state changed to DOWN aue0: link state changed to UP aue0: usb error on rx: IOERROR FreeBSD xxx 7.1-PRERELEASE FreeBSD 7.1-PRERELEASE #2: Tue Dec 30 00:41:39 BRT 2008 root@xxx:/usr/obj/usr/src/sys/xxx i386 if anyone has any clues, thanks, matheus -- We will call you cygnus, The God of balance you shall be From matheus at eternamente.info Tue Feb 10 04:28:53 2009 From: matheus at eternamente.info (Nenhum_de_Nos) Date: Tue Feb 10 04:29:03 2009 Subject: ADMtek USB To LAN Converter Message-ID: <92fe476d6c450c162b8bcde16c6e43bd.squirrel@cygnus.homeunix.com> hail, I have two of these and cant make them ping. module loads ok, ifconfig sees ok, but cant send any data. tcpdump can get info though. aue0: on uhub1 miibus3: on aue0 ukphy1: PHY 1 on miibus3 ukphy1: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto aue0: Ethernet address: 00:60:6e:00:05:d2 aue0: link state changed to DOWN aue0: link state changed to UP aue0: usb error on rx: IOERROR FreeBSD xxx 7.1-PRERELEASE FreeBSD 7.1-PRERELEASE #2: Tue Dec 30 00:41:39 BRT 2008 root@xxx:/usr/obj/usr/src/sys/xxx i386 if anyone has any clues, thanks, matheus -- We will call you cygnus, The God of balance you shall be -- We will call you cygnus, The God of balance you shall be From matheus at eternamente.info Tue Feb 10 06:39:54 2009 From: matheus at eternamente.info (Nenhum_de_Nos) Date: Tue Feb 10 06:40:01 2009 Subject: ADMtek USB To LAN Converter Message-ID: <09da8c63d4de0f47726e524abaa6a1f6.squirrel@cygnus.homeunix.com> hail, first of all I apologize for two messages, but I'm not receiving usb@ msgs. but to the point, this adapter: aue0: on uhub1 miibus3: on aue0 ukphy1: PHY 1 on miibus3 ukphy1: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto aue0: Ethernet address: 00:60:6e:00:05:d2 aue0: link state changed to DOWN aue0: link state changed to UP aue0: usb error on rx: IOERROR in current using usb1 never got to send a byte on the wire. So I tested USB2: ugen0.2: at usbus0 aue0: on usbus0 miibus1: on aue0 ukphy0: PHY 1 on miibus1 ukphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto ue0: on aue0 ue0: Ethernet address: 00:60:6e:00:05:d2 ue0: link state changed to DOWN and after a ifconfig ue0 $ip, it did work :) as I have no clue why this, I'm here asking. I'd like to have this nic in a router and planned to run STABLE or any RELEASE, nor CURRENT. so is this possible ? and at last but not least, thanks for usb2 code :) matheus -- We will call you cygnus, The God of balance you shall be From hselasky at c2i.net Tue Feb 10 06:59:10 2009 From: hselasky at c2i.net (Hans Petter Selasky) Date: Tue Feb 10 06:59:17 2009 Subject: ADMtek USB To LAN Converter In-Reply-To: <09da8c63d4de0f47726e524abaa6a1f6.squirrel@cygnus.homeunix.com> References: <09da8c63d4de0f47726e524abaa6a1f6.squirrel@cygnus.homeunix.com> Message-ID: <200902101601.35722.hselasky@c2i.net> On Tuesday 10 February 2009, Nenhum_de_Nos wrote: > > first of all I apologize for two messages, but I'm not receiving usb@ msgs. > > but to the point, this adapter: > Hi, > aue0: usb error on rx: IOERROR Probably the old USB aue0 driver does not handle the clear-stall correctly. > So is this possible ? It will require some work. What is the target version of FreeBSD where you want to backport the aue0 driver? > > and at last but not least, thanks for usb2 code :) Great to hear it's working! --HPS From matheus at eternamente.info Tue Feb 10 11:00:39 2009 From: matheus at eternamente.info (Nenhum_de_Nos) Date: Tue Feb 10 11:00:46 2009 Subject: ADMtek USB To LAN Converter In-Reply-To: <200902101601.35722.hselasky@c2i.net> References: <09da8c63d4de0f47726e524abaa6a1f6.squirrel@cygnus.homeunix.com> <200902101601.35722.hselasky@c2i.net> Message-ID: On Tue, February 10, 2009 13:01, Hans Petter Selasky wrote: > On Tuesday 10 February 2009, Nenhum_de_Nos wrote: >> >> first of all I apologize for two messages, but I'm not receiving usb@ >> msgs. >> >> but to the point, this adapter: >> > > Hi, > >> aue0: usb error on rx: IOERROR > > Probably the old USB aue0 driver does not handle the clear-stall > correctly. this error appeared just once, but I tried for quite long time (some hours yesterday), and using 7.1R/STABLE/CURRENT >> So is this possible ? > > It will require some work. What is the target version of FreeBSD where you > want to backport the aue0 driver? well, STABLE would be much of enough :) as it'll be in future releases :) >> >> and at last but not least, thanks for usb2 code :) > > Great to hear it's working! yep, and is ok. just noticed u3g stopped working :) I was about to send nick a message about this, or is all about you ? ;) thanks again, matheus > --HPS > -- We will call you cygnus, The God of balance you shall be From hselasky at c2i.net Tue Feb 10 11:06:35 2009 From: hselasky at c2i.net (Hans Petter Selasky) Date: Tue Feb 10 11:06:41 2009 Subject: ADMtek USB To LAN Converter In-Reply-To: References: <09da8c63d4de0f47726e524abaa6a1f6.squirrel@cygnus.homeunix.com> <200902101601.35722.hselasky@c2i.net> Message-ID: <200902102008.59847.hselasky@c2i.net> On Tuesday 10 February 2009, Nenhum_de_Nos wrote: > On Tue, February 10, 2009 13:01, Hans Petter Selasky wrote: > > On Tuesday 10 February 2009, Nenhum_de_Nos wrote: > >> first of all I apologize for two messages, but I'm not receiving usb@ > >> msgs. > >> > >> but to the point, this adapter: > > > > Hi, > > > >> aue0: usb error on rx: IOERROR > > > > Probably the old USB aue0 driver does not handle the clear-stall > > correctly. > > this error appeared just once, but I tried for quite long time (some hours > yesterday), and using 7.1R/STABLE/CURRENT > > >> So is this possible ? > > > > It will require some work. What is the target version of FreeBSD where > > you want to backport the aue0 driver? > > well, STABLE would be much of enough :) as it'll be in future releases :) > > >> and at last but not least, thanks for usb2 code :) > > > > Great to hear it's working! > > yep, and is ok. just noticed u3g stopped working :) > I was about to send nick a message about this, or is all about you ? ;) Hi, If you have some debug prints you can send them to me or Andrew Thompson. There has been some changes to u3g recently. Maybe something is broken? kldload usb2_serial_3g And dmesg output. --HPS From matheus at eternamente.info Tue Feb 10 11:41:15 2009 From: matheus at eternamente.info (Nenhum_de_Nos) Date: Tue Feb 10 11:41:20 2009 Subject: ADMtek USB To LAN Converter In-Reply-To: <200902102008.59847.hselasky@c2i.net> References: <09da8c63d4de0f47726e524abaa6a1f6.squirrel@cygnus.homeunix.com> <200902101601.35722.hselasky@c2i.net> <200902102008.59847.hselasky@c2i.net> Message-ID: <02bc424a29f2cad2310599f352b232f7.squirrel@cygnus.homeunix.com> On Tue, February 10, 2009 17:08, Hans Petter Selasky wrote: > On Tuesday 10 February 2009, Nenhum_de_Nos wrote: >> On Tue, February 10, 2009 13:01, Hans Petter Selasky wrote: >> > On Tuesday 10 February 2009, Nenhum_de_Nos wrote: >> >> first of all I apologize for two messages, but I'm not receiving usb@ >> >> msgs. >> >> >> >> but to the point, this adapter: >> > >> > Hi, >> > >> >> aue0: usb error on rx: IOERROR >> > >> > Probably the old USB aue0 driver does not handle the clear-stall >> > correctly. >> >> this error appeared just once, but I tried for quite long time (some >> hours >> yesterday), and using 7.1R/STABLE/CURRENT >> >> >> So is this possible ? >> > >> > It will require some work. What is the target version of FreeBSD where >> > you want to backport the aue0 driver? >> >> well, STABLE would be much of enough :) as it'll be in future releases >> :) >> >> >> and at last but not least, thanks for usb2 code :) >> > >> > Great to hear it's working! >> >> yep, and is ok. just noticed u3g stopped working :) >> I was about to send nick a message about this, or is all about you ? ;) > > Hi, > > If you have some debug prints you can send them to me or Andrew Thompson. > There has been some changes to u3g recently. Maybe something is broken? > > kldload usb2_serial_3g > > And dmesg output. > > --HPS well, sorry for my mistake. I did kldluad u3g and it loaded, but my Huawei E226 got ugen for it. I'll try this though. thanks, matheus -- We will call you cygnus, The God of balance you shall be From Thomas.Sparrevohn at btinternet.com Tue Feb 10 13:32:31 2009 From: Thomas.Sparrevohn at btinternet.com (Thomas Sparrevohn) Date: Tue Feb 10 13:32:38 2009 Subject: Recent Changes to Rum driver - seems to have.. Message-ID: <012401c98bc7$123648b0$36a2da10$@Sparrevohn@btinternet.com> Reintroduced panics when the device is used heavily - it also reports the "needs callback" in dmesg - Unless this is known I can post a dmesg From matheus at eternamente.info Tue Feb 10 17:20:01 2009 From: matheus at eternamente.info (Matheus) Date: Tue Feb 10 17:20:07 2009 Subject: usb/131576: ADMtek USB To LAN Converter can't send data Message-ID: <200902110114.n1B1ET1A026162@www.freebsd.org> >Number: 131576 >Category: usb >Synopsis: ADMtek USB To LAN Converter can't send data >Confidential: no >Severity: non-critical >Priority: low >Responsible: freebsd-usb >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Wed Feb 11 01:20:00 UTC 2009 >Closed-Date: >Last-Modified: >Originator: Matheus >Release: 7.1-PRERELEASE >Organization: >Environment: FreeBSD lamneth 7.1-PRERELEASE FreeBSD 7.1-PRERELEASE #2: Tue Dec 30 00:41:39 BRT 2008 root@lamneth:/usr/obj/usr/src/sys/Lamneth_7-3G i386 >Description: I have an aue device that detects ok, but can't send data. tcpdump can read from wire though. the dmesg: aue0: on uhub1 miibus3: on aue0 ukphy1: PHY 1 on miibus3 ukphy1: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto aue0: Ethernet address: 00:60:6e:00:05:d2 aue0: link state changed to DOWN aue0: link state changed to UP aue0: usb error on rx: IOERROR aue0: at uhub1 port 1 (addr 2) disconnected aue0: detached usbdevs -v: Controller /dev/usb0: addr 1: full speed, self powered, config 1, UHCI root hub(0x0000), VIA(0x0000), rev 1.00 port 1 powered port 2 addr 2: full speed, power 160 mA, config 1, USB To LAN Converter(0x8513), ADMtek(0x07a6), rev 2.01 I read from 4.9 days in mailing lists a problem quite close to this, but on ADM8511, this is ADM8513 >How-To-Repeat: Just plug the adapter. >Fix: Use usb2 code. >Release-Note: >Audit-Trail: >Unformatted: From schmidt at ze.tum.de Tue Feb 10 23:30:04 2009 From: schmidt at ze.tum.de (Gerhard Schmidt) Date: Tue Feb 10 23:30:10 2009 Subject: usb/131583: Failure when detaching umass Device Message-ID: <200902110648.n1B6mK6n084870@etustar.ze.tum.de> >Number: 131583 >Category: usb >Synopsis: Failure when detaching umass Device >Confidential: no >Severity: serious >Priority: medium >Responsible: freebsd-usb >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Wed Feb 11 07:30:02 UTC 2009 >Closed-Date: >Last-Modified: >Originator: Gerhard Schmidt >Release: FreeBSD 7.1-STABLE amd64 >Organization: Technische Universität München >Environment: System: FreeBSD etustar.ze.tum.de 7.1-STABLE FreeBSD 7.1-STABLE #9: Mon Feb 9 09:13:59 CET 2009 root@etustar.ze.tum.de:/usr/src/sys/amd64/compile/ETUSTAR amd64 >Description: I've a Sandisk Sansa e280 MP3 Player. The Mplayer is charged via USB cable. To charge the player I've connected the Player to my FreeBSD Workstation. After charging the Player (ca 2h) I disconnected the Player and get the following Message umass0: BBB reset failed, IOERROR umass0: BBB bulk-in clear stall failed, IOERROR umass0: BBB bulk-out clear stall failed, IOERROR repeating every two secounds. The umass device has never been mounted during the charge time. The player is an MTP device and has an entry in my hal policies. portable_audio_player SanDisk Sansa e200/e250/e260/e270/e280 portable_audio_player user mtp libmtp audio/mpeg audio/x-ms-wma mtp portable_audio_player SanDisk Sansa e280 portable_audio_player user mtp libmtp audio/mpeg audio/x-ms-wma mtp portable_audio_player SanDisk Sansa e280 v2 portable_audio_player user mtp libmtp audio/mpeg audio/x-ms-wma mtp >How-To-Repeat: connect and disconnect the player >Fix: n/k >Release-Note: >Audit-Trail: >Unformatted: From tamaru at myn.rcast.u-tokyo.ac.jp Tue Feb 10 23:41:08 2009 From: tamaru at myn.rcast.u-tokyo.ac.jp (Hiroharu Tamaru) Date: Tue Feb 10 23:41:14 2009 Subject: USB2: umass not detected correctly, axe not transmitting Message-ID: Hi, I have an Atom Z530 semi-embedded system and tried the new USB2 stack. I found some oddities and decided to report here. It is running 8.0-CURRENT as of yesterday, and I have GENERIC and USB2 kernels to test with. I am testing with two usb devices: umass0: on usbus3 axe0: on usbus3 First about the USB memory stick: 1) I setup a bootable USB memory stick, and this system boots off umass da0 if I have the old USB1 kernel. However, with USB2 kernel, it does not detect da0 at its final stage, and fails to find the root filesystem. I mean that the 'da0 at umass-sim0 bus 0 target 0 lun 0' message is not shown, and it is not listed in the kernel detected list of disks at 'mountroot>' prompt (shown by typing '?'). 2) If I boot from the internal ad0, and plug in this stick it gets detected: ugen3.2: at usbus3 umass0: on usbus3 umass0: SCSI over Bulk-Only; quirks = 0x0100 umass0:0:0:-1: Attached to scbus0 (probe0:umass-sim0:0:0:0): TEST UNIT READY. CDB: 0 0 0 0 0 0 (probe0:umass-sim0:0:0:0): CAM Status: SCSI Status Error (probe0:umass-sim0:0:0:0): SCSI Status: Check Condition (probe0:umass-sim0:0:0:0): UNIT ATTENTION asc:28,0 (probe0:umass-sim0:0:0:0): Not ready to ready change, medium may have changed (probe0:umass-sim0:0:0:0): Retrying Command (per Sense Data) da0 at umass-sim0 bus 0 target 0 lun 0 da0: Removable Direct Access SCSI-2 device da0: 40.000MB/s transfers da0: 3830MB (7843840 512 byte sectors: 255H 63S/T 488C) however, it does not give the correct contents when read; it does not detect the slices and all. # ls /dev/da0* /dev/da0 # dd if=/dev/da0 count=1 | hexdump -C 1+0 records in 1+0 records out 00000000 55 53 42 43 24 00 00 00 00 02 00 00 80 00 0a 28 |USBC$..........(| 00000010 00 00 00 00 00 00 00 01 00 00 00 00 00 00 00 c4 |................| 00000020 00 c4 30 37 8a aa 55 00 28 03 4d 00 61 00 73 00 |..07..U.(.M.a.s.| 00000030 73 00 20 00 53 00 74 00 6f 00 72 00 61 00 67 00 |s. .S.t.o.r.a.g.| 00000040 65 00 20 00 44 00 65 00 76 00 69 00 63 00 65 00 |e. .D.e.v.i.c.e.| 00000050 4a 65 74 46 6c 61 73 68 54 72 61 6e 73 63 65 6e |JetFlashTranscen| 00000060 64 20 34 47 42 20 20 20 38 2e 30 31 8a aa 55 00 |d 4GB 8.01..U.| 00000070 00 00 00 00 00 00 00 00 00 00 00 00 00 00 3c c3 |..............<.| 00000080 12 03 38 00 4c 00 4f 00 31 00 4d 00 43 00 42 00 |..8.L.O.1.M.C.B.| 00000090 52 00 3d 00 00 00 00 00 00 00 00 00 00 00 00 00 |R.=.............| 000000a0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................| * 000000d0 00 00 00 00 68 50 51 49 00 00 00 00 00 00 00 00 |....hPQI........| 000000e0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................| * 00000160 00 0d 09 51 01 01 21 00 ff ff 01 0d 01 00 18 03 |...Q..!.........| 00000170 08 0c 14 01 01 03 b4 ff 01 00 00 a0 ff 00 07 e7 |................| 00000180 70 54 53 34 47 4a 46 56 33 35 00 00 00 00 00 00 |pTS4GJFV35......| 00000190 ca 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................| 000001a0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................| * 512 bytes transferred in 0.000506 secs (1012009 bytes/sec) 00000200 It gives the correct mbr and slice table when the USB1 kernel (GENERIC) is used, of course. Next about the ethernet device: This device is detected correctly. ugen3.3: at usbus3 axe0: on usbus3 axe0: PHYADDR 0xe0:0x18 miibus0: on axe0 ciphy0: PHY 24 on miibus0 ciphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 1000baseT-FDX, auto ue0: on axe0 ue0: Ethernet address: 00:90:cc:xx:xx:xx ue0: link state changed to DOWN ue0: link state changed to UP # ifconfg ue0 ue0: flags=8843 metric 0 mtu 1500 ether 00:90:cc:xx:xx:xx inet 0.0.0.0 netmask 0xff000000 broadcast 255.255.255.255 media: Ethernet autoselect (100baseTX ) status: active However it cannot transmit packets. 'tcpdump -i ue0 -n' shows traffic, so it can recive packets. But by watching the wire from another host, no packet leaves this interface. So, which details should I start reporting with? Thanks. Hiroharu From hselasky at c2i.net Wed Feb 11 00:52:12 2009 From: hselasky at c2i.net (Hans Petter Selasky) Date: Wed Feb 11 00:52:19 2009 Subject: USB2: umass not detected correctly, axe not transmitting In-Reply-To: References: Message-ID: <200902110954.37659.hselasky@c2i.net> Hi, On Wednesday 11 February 2009, Hiroharu Tamaru wrote: > Hi, > > I have an Atom Z530 semi-embedded system and tried the new USB2 stack. > I found some oddities and decided to report here. > > It is running 8.0-CURRENT as of yesterday, and I have GENERIC and USB2 > kernels to test with. I am testing with two usb devices: > > umass0: on > usbus3 axe0: on usbus3 > > First about the USB memory stick: > > 1) I setup a bootable USB memory stick, and this system > boots off umass da0 if I have the old USB1 kernel. > However, with USB2 kernel, it does not detect da0 at its final stage, > and fails to find the root filesystem. > I mean that the 'da0 at umass-sim0 bus 0 target 0 lun 0' message is not > shown, and it is not listed in the kernel detected list of disks at > 'mountroot>' prompt (shown by typing '?'). This is a known issue, see: http://wiki.freebsd.org/USB > > > 2) If I boot from the internal ad0, and plug in this stick it gets > detected: > > > however, it does not give the correct contents when read; it does not > detect the slices and all. > Could you repeat the same "cat" operation with UMASS debugging turned on? sysctl hw.usb2.umass.debug=-1 > > Next about the ethernet device: > > This device is detected correctly. > > ugen3.3: at usbus3 > axe0: on usbus3 > axe0: PHYADDR 0xe0:0x18 > miibus0: on axe0 > ciphy0: PHY 24 on miibus0 > ciphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, > 1000baseT-FDX, auto ue0: on axe0 > ue0: Ethernet address: 00:90:cc:xx:xx:xx > ue0: link state changed to DOWN > ue0: link state changed to UP > > # ifconfg ue0 > ue0: flags=8843 metric 0 mtu 1500 > ether 00:90:cc:xx:xx:xx > inet 0.0.0.0 netmask 0xff000000 broadcast 255.255.255.255 > media: Ethernet autoselect (100baseTX ) > status: active Turn on debugging: sysctl hw.usb2.axe.debug=15 And repeat test. --HPS From hselasky at c2i.net Wed Feb 11 00:58:20 2009 From: hselasky at c2i.net (Hans Petter Selasky) Date: Wed Feb 11 00:58:27 2009 Subject: Recent Changes to Rum driver - seems to have.. In-Reply-To: <012401c98bc7$123648b0$36a2da10$@Sparrevohn@btinternet.com> References: <012401c98bc7$123648b0$36a2da10$@Sparrevohn@btinternet.com> Message-ID: <200902111000.46643.hselasky@c2i.net> On Tuesday 10 February 2009, Thomas Sparrevohn wrote: > Reintroduced panics when the device is used heavily - it also reports the > "needs callback" in dmesg - Unless this is known I can post a dmesg > Hi Thomas, Andrew Thompson decided to re-port the driver from USB1. I've tried to fix most of the bugs now. If the fixes are not in -current yet you can fetch if_rum*[ch] from: svn --username anonsvn --password anonsvn \ checkout svn://svn.turbocat.net/i4b/trunk/i4b/src/sys/dev/usb2 Do you have a backtrace of the panics ? Sorry about the inconvenience. --HPS From hselasky at c2i.net Wed Feb 11 01:24:55 2009 From: hselasky at c2i.net (Hans Petter Selasky) Date: Wed Feb 11 01:25:02 2009 Subject: Recent Changes to Rum driver - seems to have.. In-Reply-To: <200902111000.46643.hselasky@c2i.net> References: <012401c98bc7$123648b0$36a2da10$@Sparrevohn@btinternet.com> <200902111000.46643.hselasky@c2i.net> Message-ID: <200902111027.19021.hselasky@c2i.net> On Wednesday 11 February 2009, Hans Petter Selasky wrote: > On Tuesday 10 February 2009, Thomas Sparrevohn wrote: > > Reintroduced panics when the device is used heavily - it also reports the > > "needs callback" in dmesg - Unless this is known I can post a dmesg > > Hi Thomas, > > Andrew Thompson decided to re-port the driver from USB1. I've tried to fix > most of the bugs now. If the fixes are not in -current yet you can fetch > if_rum*[ch] from: > > svn --username anonsvn --password anonsvn \ > checkout svn://svn.turbocat.net/i4b/trunk/i4b/src/sys/dev/usb2 > > > Do you have a backtrace of the panics ? > > Sorry about the inconvenience. And also update: usb2_process.[ch] --HPS From hselasky at c2i.net Wed Feb 11 02:52:22 2009 From: hselasky at c2i.net (Hans Petter Selasky) Date: Wed Feb 11 02:52:29 2009 Subject: Recent Changes to Rum driver - seems to have.. In-Reply-To: <012401c98bc7$123648b0$36a2da10$@Sparrevohn@btinternet.com> References: <012401c98bc7$123648b0$36a2da10$@Sparrevohn@btinternet.com> Message-ID: <200902111154.47314.hselasky@c2i.net> On Tuesday 10 February 2009, Thomas Sparrevohn wrote: > Reintroduced panics when the device is used heavily - it also reports the > "needs callback" in dmesg - Unless this is known I can post a dmesg > Hi Thomas, Here are some more patches. I cannot promise if this is the last round of RUM patching. http://perforce.freebsd.org/chv.cgi?CH=157533 --HPS PS: My private SVN has been updated with these changes. From tamaru at myn.rcast.u-tokyo.ac.jp Wed Feb 11 04:46:16 2009 From: tamaru at myn.rcast.u-tokyo.ac.jp (Hiroharu Tamaru) Date: Wed Feb 11 04:46:23 2009 Subject: USB2: umass not detected correctly, axe not transmitting In-Reply-To: <200902110954.37659.hselasky@c2i.net> <200902111007.20279.hselasky@c2i.net> References: <200902110954.37659.hselasky@c2i.net> Message-ID: Thank you, Hans, At Wed, 11 Feb 2009 09:54:36 +0100, Hans Petter Selasky wrote: > Hi, > > On Wednesday 11 February 2009, Hiroharu Tamaru wrote: > > Hi, > > > > I have an Atom Z530 semi-embedded system and tried the new USB2 stack. > > I found some oddities and decided to report here. > > > > It is running 8.0-CURRENT as of yesterday, and I have GENERIC and USB2 > > kernels to test with. I am testing with two usb devices: > > > > umass0: on > > usbus3 axe0: on usbus3 > > > > First about the USB memory stick: > > > > 1) I setup a bootable USB memory stick, and this system > > boots off umass da0 if I have the old USB1 kernel. > > However, with USB2 kernel, it does not detect da0 at its final stage, > > and fails to find the root filesystem. > > I mean that the 'da0 at umass-sim0 bus 0 target 0 lun 0' message is not > > shown, and it is not listed in the kernel detected list of disks at > > 'mountroot>' prompt (shown by typing '?'). > > This is a known issue, see: > > http://wiki.freebsd.org/USB OK. I missed that. Thanks. Now rebuilding... but will take some while. I will be back with the hw.usb2.umass.debug and hw.usb2.axe.dubug set, too. > What platform are you using? It's called 'Low enegy profile FA PC: SFC-A016(L)' from Interface Corp., but, there're only Japanese pages at the moment. Probably you can get some idea though: http://www.interface.co.jp/sfc/sfc_spec.asp They started making English pages but it is still quite empty: https://www5.interface-world.com/ FWIW, it has a mini AB connecter, aside from the normal A connectors, and they say that they have an USB client-side driver for it on Windows XP embeded. Can we make use of this part of the hardware on FreeBSD as well? Hiroharu From hselasky at c2i.net Wed Feb 11 04:50:56 2009 From: hselasky at c2i.net (Hans Petter Selasky) Date: Wed Feb 11 04:51:03 2009 Subject: USB2: umass not detected correctly, axe not transmitting In-Reply-To: References: <200902110954.37659.hselasky@c2i.net> Message-ID: <200902111353.21355.hselasky@c2i.net> Hi, On Wednesday 11 February 2009, Hiroharu Tamaru wrote: > Thank you, Hans, > > I will be back with the hw.usb2.umass.debug and hw.usb2.axe.dubug set, too. > > > What platform are you using? > > It's called 'Low enegy profile FA PC: SFC-A016(L)' from > Interface Corp., but, there're only Japanese pages at the > moment. Probably you can get some idea though: > http://www.interface.co.jp/sfc/sfc_spec.asp What architecture is this? ARM? Recently there was added a BIGENDIAN descriptor flag to the EHCI driver. Do you know if your hardware is big-endian? > > They started making English pages but it is still quite empty: > https://www5.interface-world.com/ > > FWIW, it has a mini AB connecter, aside from the normal A > connectors, and they say that they have an USB client-side > driver for it on Windows XP embeded. Can we make use of > this part of the hardware on FreeBSD as well? Yes you can, if you have the docs for the USB client-side chip. --HPS From onemda at gmail.com Wed Feb 11 04:58:33 2009 From: onemda at gmail.com (Paul B. Mahol) Date: Wed Feb 11 04:58:40 2009 Subject: Recent Changes to Rum driver - seems to have.. In-Reply-To: <3285005830759497018@unknownmsgid> References: <3285005830759497018@unknownmsgid> Message-ID: <3a142e750902110438g33fbb556g53e136ae31453b6d@mail.gmail.com> On 2/10/09, Thomas Sparrevohn wrote: > Reintroduced panics when the device is used heavily - it also reports the > "needs callback" in dmesg - Unless this is known I can post a dmesg "needs callback" is proper behaviour, previous versions wrongly assumed that code should do nothing when such callbacks are called .... > > _______________________________________________ > freebsd-usb@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-usb > To unsubscribe, send any mail to "freebsd-usb-unsubscribe@freebsd.org" > -- Paul From tamaru at myn.rcast.u-tokyo.ac.jp Wed Feb 11 05:31:45 2009 From: tamaru at myn.rcast.u-tokyo.ac.jp (Hiroharu Tamaru) Date: Wed Feb 11 05:31:53 2009 Subject: USB2: umass not detected correctly, axe not transmitting In-Reply-To: <200902111353.21355.hselasky@c2i.net> References: <200902110954.37659.hselasky@c2i.net> <200902111353.21355.hselasky@c2i.net> Message-ID: Hi, At Wed, 11 Feb 2009 13:53:20 +0100, Hans Petter Selasky wrote: > > Hi, > > On Wednesday 11 February 2009, Hiroharu Tamaru wrote: > > Thank you, Hans, > > > > > I will be back with the hw.usb2.umass.debug and hw.usb2.axe.dubug set, too. > > > > > What platform are you using? > > It's called 'Low enegy profile FA PC: SFC-A016(L)' from > > Interface Corp., but, there're only Japanese pages at the > > moment. Probably you can get some idea though: > > http://www.interface.co.jp/sfc/sfc_spec.asp > > What architecture is this? ARM? Recently there was added a BIGENDIAN > descriptor flag to the EHCI driver. Do you know if your hardware is > big-endian? This is an Intel Atom Z530, and I am running i386 kernel. CPU: Intel(R) Atom(TM) CPU Z530 @ 1.60GHz (1596.00-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x106c2 Stepping = 2 Features=0xbfe9fbff Features2=0x40c3bd> AMD Features=0x100000 AMD Features2=0x1 TSC: P-state invariant Logical CPUs per core: 2 real memory = 1063976960 (1014 MB) > > They started making English pages but it is still quite empty: > > https://www5.interface-world.com/ > > > > FWIW, it has a mini AB connecter, aside from the normal A > > connectors, and they say that they have an USB client-side > > driver for it on Windows XP embeded. Can we make use of > > this part of the hardware on FreeBSD as well? > > Yes you can, if you have the docs for the USB client-side chip. So, probably, you mean if there's a doc for this one? none0@pci0:0:26:0: class=0x0c0380 card=0x00011147 chip=0x81188086 rev=0x07 hdr=0x00 vendor = 'Intel Corporation' class = serial bus subclass = USB uhci0@pci0:0:29:0: class=0x0c0300 card=0x00011147 chip=0x81148086 rev=0x07 hdr=0x00 vendor = 'Intel Corporation' class = serial bus subclass = USB uhci1@pci0:0:29:1: class=0x0c0300 card=0x00011147 chip=0x81158086 rev=0x07 hdr=0x00 vendor = 'Intel Corporation' class = serial bus subclass = USB uhci2@pci0:0:29:2: class=0x0c0300 card=0x00011147 chip=0x81168086 rev=0x07 hdr=0x00 vendor = 'Intel Corporation' class = serial bus subclass = USB ehci0@pci0:0:29:7: class=0x0c0320 card=0x00011147 chip=0x81178086 rev=0x07 hdr=0x00 vendor = 'Intel Corporation' class = serial bus subclass = USB Hiroharu From hselasky at c2i.net Wed Feb 11 05:42:21 2009 From: hselasky at c2i.net (Hans Petter Selasky) Date: Wed Feb 11 05:42:28 2009 Subject: USB2: umass not detected correctly, axe not transmitting In-Reply-To: References: <200902111353.21355.hselasky@c2i.net> Message-ID: <200902111444.45474.hselasky@c2i.net> Hi, On Wednesday 11 February 2009, Hiroharu Tamaru wrote: > Hi, > > At Wed, 11 Feb 2009 13:53:20 +0100, Hans Petter Selasky wrote: > > Hi, > > > > On Wednesday 11 February 2009, Hiroharu Tamaru wrote: > > > Thank you, Hans, > > > > > > > > > I will be back with the hw.usb2.umass.debug and hw.usb2.axe.dubug set, > > > too. > > > > > > > What platform are you using? > > > > > > It's called 'Low enegy profile FA PC: SFC-A016(L)' from > > > Interface Corp., but, there're only Japanese pages at the > > > moment. Probably you can get some idea though: > > > http://www.interface.co.jp/sfc/sfc_spec.asp > > The dmesg you sent looks good. I need some debug information to debug this issue. BTW: Do other memory sticks or USB devices work? > > > > Yes you can, if you have the docs for the USB client-side chip. > > So, probably, you mean if there's a doc for this one? Yes. There is a couple of example device side drivers in the tree now, so it should be possible to anyone with good programming skills to manage writing a driver for this chip. > > none0@pci0:0:26:0: class=0x0c0380 card=0x00011147 chip=0x81188086 rev=0x07 > hdr=0x00 vendor = 'Intel Corporation' > class = serial bus > subclass = USB > --HPS From Thomas.Sparrevohn at btinternet.com Wed Feb 11 05:56:35 2009 From: Thomas.Sparrevohn at btinternet.com (Thomas Sparrevohn) Date: Wed Feb 11 05:56:43 2009 Subject: Recent Changes to Rum driver - seems to have.. In-Reply-To: <200902111000.46643.hselasky@c2i.net> References: <012401c98bc7$123648b0$36a2da10$@Sparrevohn@btinternet.com> <200902111000.46643.hselasky@c2i.net> Message-ID: <002e01c98c50$8bd1bae0$a37530a0$@Sparrevohn@btinternet.com> That explains it - Here you go -----Original Message----- From: Hans Petter Selasky [mailto:hselasky@c2i.net] Sent: 11 February 2009 09:01 To: freebsd-usb@freebsd.org; Andrew Thompson Cc: Thomas Sparrevohn Subject: Re: Recent Changes to Rum driver - seems to have.. On Tuesday 10 February 2009, Thomas Sparrevohn wrote: > Reintroduced panics when the device is used heavily - it also reports the > "needs callback" in dmesg - Unless this is known I can post a dmesg > Hi Thomas, Andrew Thompson decided to re-port the driver from USB1. I've tried to fix most of the bugs now. If the fixes are not in -current yet you can fetch if_rum*[ch] from: svn --username anonsvn --password anonsvn \ checkout svn://svn.turbocat.net/i4b/trunk/i4b/src/sys/dev/usb2 Do you have a backtrace of the panics ? Sorry about the inconvenience. --HPS -------------- next part -------------- A non-text attachment was scrubbed... Name: core.txt.46.bz2 Type: application/octet-stream Size: 19712 bytes Desc: not available Url : http://lists.freebsd.org/pipermail/freebsd-usb/attachments/20090211/7fce61ae/core.txt.46.obj From tamaru at myn.rcast.u-tokyo.ac.jp Wed Feb 11 06:19:28 2009 From: tamaru at myn.rcast.u-tokyo.ac.jp (Hiroharu Tamaru) Date: Wed Feb 11 06:19:39 2009 Subject: USB2: umass not detected correctly, axe not transmitting In-Reply-To: <200902110954.37659.hselasky@c2i.net> References: <200902110954.37659.hselasky@c2i.net> Message-ID: Hi, Hans I'm back with test results. At Wed, 11 Feb 2009 09:54:36 +0100, Hans Petter Selasky wrote: > > Hi, > > On Wednesday 11 February 2009, Hiroharu Tamaru wrote: > > Hi, > > > > I have an Atom Z530 semi-embedded system and tried the new USB2 stack. > > I found some oddities and decided to report here. > > > > It is running 8.0-CURRENT as of yesterday, and I have GENERIC and USB2 > > kernels to test with. I am testing with two usb devices: > > > > umass0: on > > usbus3 axe0: on usbus3 > > > > First about the USB memory stick: > > > > 1) I setup a bootable USB memory stick, and this system > > boots off umass da0 if I have the old USB1 kernel. > > However, with USB2 kernel, it does not detect da0 at its final stage, > > and fails to find the root filesystem. > > I mean that the 'da0 at umass-sim0 bus 0 target 0 lun 0' message is not > > shown, and it is not listed in the kernel detected list of disks at > > 'mountroot>' prompt (shown by typing '?'). > > This is a known issue, see: > > http://wiki.freebsd.org/USB This worked very well. Thanks. I assume it will be committed to the tree sometime near in the future, right? > > 2) If I boot from the internal ad0, and plug in this stick it gets > > detected: > > > > > > however, it does not give the correct contents when read; it does not > > detect the slices and all. > > > > Could you repeat the same "cat" operation with UMASS debugging turned on? > > sysctl hw.usb2.umass.debug=-1 I'm not sure why, but now I cannot reproduce this any more. The patched (as above) kernel detects da0 correctly, And the original kernel (that gave that symptom multiple times before I wrote the original mail) also gives the correct result now.. Strange, but since I'm fine now, I leave it for now. I will be back with the results if it happens again. Thanks for the help. > > Next about the ethernet device: > > > > This device is detected correctly. > > > > ugen3.3: at usbus3 > > axe0: on usbus3 > > axe0: PHYADDR 0xe0:0x18 > > miibus0: on axe0 > > ciphy0: PHY 24 on miibus0 > > ciphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, > > 1000baseT-FDX, auto ue0: on axe0 > > ue0: Ethernet address: 00:90:cc:xx:xx:xx > > ue0: link state changed to DOWN > > ue0: link state changed to UP > > > > # ifconfg ue0 > > ue0: flags=8843 metric 0 mtu 1500 > > ether 00:90:cc:xx:xx:xx > > inet 0.0.0.0 netmask 0xff000000 broadcast 255.255.255.255 > > media: Ethernet autoselect (100baseTX ) > > status: active > > Turn on debugging: > > sysctl hw.usb2.axe.debug=15 > > And repeat test. with hw.usb2.axe.debug=15, I have: ugen3.3: at usbus3 (disconnected) pid 3244 (dhclient), uid 65: exited on signal 11 ugen3.3: at usbus3 axe0: on usbus3 axe0: PHYADDR 0xe0:0x18 miibus0: on axe0 ciphy0: PHY 24 on miibus0 ciphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 1000baseT-FDX, auto ue0: on axe0 ue0: Ethernet address: 00:90:cc:f7:bc:2e ue0: link state changed to DOWN ue0: link state changed to UP and when dhclient runs ifconfig, I get axe_bulk_read_callback:796: bulk read error, USB_ERR_CANCELLED axe_bulk_write_callback:823: transfer complete and then for every DCHP request packet sent I get axe_bulk_write_callback:823: transfer complete and that's all. If I manually setup an address and run tcpdump -i ue0 -n, I can see the traffic on wire as before. I get no console messages meanwhile. If I try to ping an address from this machine, I see arp request on tcpdump result on this machine, but not on the receiving machine: the out going packet is not on the wire. I get one of this message for every arp packet sent: axe_bulk_write_callback:823: transfer complete If I try to ping this machine from another, I see arp request and arp reply on the tcpdump on this side, but I only see arp request on the other side, again. So everything is consistent that it is receiving packets but not sending. The hardware is a PLANEX GU-1000T ethernet adapter. What can I do now? > --HPS Hiroharu From hselasky at c2i.net Wed Feb 11 07:30:58 2009 From: hselasky at c2i.net (Hans Petter Selasky) Date: Wed Feb 11 07:31:06 2009 Subject: Recent Changes to Rum driver - seems to have.. In-Reply-To: <002e01c98c50$8bd1bae0$a37530a0$@Sparrevohn@btinternet.com> References: <012401c98bc7$123648b0$36a2da10$@Sparrevohn@btinternet.com> <200902111000.46643.hselasky@c2i.net> <002e01c98c50$8bd1bae0$a37530a0$@Sparrevohn@btinternet.com> Message-ID: <200902111617.04096.hselasky@c2i.net> Hi Thomas, Thanks for reporting this bug! I've analysed your panic and have made the following patch: http://perforce.freebsd.org/chv.cgi?CH=157544 Accumulated patches are available from my private SVN. I recommend updating all files in the "usb2" directory. > svn --username anonsvn --password anonsvn \ > checkout svn://svn.turbocat.net/i4b/trunk/i4b/src/sys/dev/usb2 > --HPS From hselasky at c2i.net Wed Feb 11 07:55:13 2009 From: hselasky at c2i.net (Hans Petter Selasky) Date: Wed Feb 11 07:55:20 2009 Subject: USB2: [was: umass not detected correctly, axe not transmitting] AXE problems In-Reply-To: References: <200902110954.37659.hselasky@c2i.net> Message-ID: <200902111657.38129.hselasky@c2i.net> On Wednesday 11 February 2009, Hiroharu Tamaru wrote: > Hi, Hans > > > > > This is a known issue, see: > > > > http://wiki.freebsd.org/USB > > This worked very well. Thanks. > I assume it will be committed to the tree sometime near > in the future, right? I suspect so. > > > > > > ugen3.3: at usbus3 > > > axe0: on usbus3 > > > axe0: PHYADDR 0xe0:0x18 > > > miibus0: on axe0 > > > ciphy0: PHY 24 on miibus0 > > > ciphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, > > > 1000baseT-FDX, auto ue0: on axe0 > > > ue0: Ethernet address: 00:90:cc:xx:xx:xx > > > ue0: link state changed to DOWN > > > ue0: link state changed to UP > > > > > > > Turn on debugging: > > > > sysctl hw.usb2.axe.debug=15 > > > > And repeat test. > > with hw.usb2.axe.debug=15, I have: > > ugen3.3: at usbus3 (disconnected) > pid 3244 (dhclient), uid 65: exited on signal 11 > ugen3.3: at usbus3 > axe0: on usbus3 > axe0: PHYADDR 0xe0:0x18 > miibus0: on axe0 > ciphy0: PHY 24 on miibus0 > ciphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, > 1000baseT-FDX, auto ue0: on axe0 > ue0: Ethernet address: 00:90:cc:f7:bc:2e > ue0: link state changed to DOWN > ue0: link state changed to UP > > The hardware is a PLANEX GU-1000T ethernet adapter. > > What can I do now? Does netstat indicate any receive errors on the AXE interface? netstat -i Maybe "Pyun YongHyeon" should have a look at this. And you are running the latest current? --HPS From Thomas.Sparrevohn at btinternet.com Wed Feb 11 08:28:48 2009 From: Thomas.Sparrevohn at btinternet.com (Thomas Sparrevohn) Date: Wed Feb 11 08:28:55 2009 Subject: Recent Changes to Rum driver - seems to have.. In-Reply-To: <200902111617.04096.hselasky@c2i.net> References: <012401c98bc7$123648b0$36a2da10$@Sparrevohn@btinternet.com> <200902111000.46643.hselasky@c2i.net> <002e01c98c50$8bd1bae0$a37530a0$@Sparrevohn@btinternet.com> <200902111617.04096.hselasky@c2i.net> Message-ID: <003d01c98c65$d07edb90$717c92b0$@Sparrevohn@btinternet.com> Ok will do - Just need to get out of "Vista land" - so it will take a little while -----Original Message----- From: Hans Petter Selasky [mailto:hselasky@c2i.net] Sent: 11 February 2009 15:17 To: Thomas Sparrevohn Cc: freebsd-usb@freebsd.org; 'Andrew Thompson' Subject: Re: Recent Changes to Rum driver - seems to have.. Hi Thomas, Thanks for reporting this bug! I've analysed your panic and have made the following patch: http://perforce.freebsd.org/chv.cgi?CH=157544 Accumulated patches are available from my private SVN. I recommend updating all files in the "usb2" directory. > svn --username anonsvn --password anonsvn \ > checkout svn://svn.turbocat.net/i4b/trunk/i4b/src/sys/dev/usb2 > --HPS From lev at FreeBSD.org Wed Feb 11 08:30:23 2009 From: lev at FreeBSD.org (Lev Serebryakov) Date: Wed Feb 11 08:30:29 2009 Subject: Guide to porting old (usb) driver to new (usb2) framework? In-Reply-To: <200902082138.39688.hselasky@c2i.net> References: <1371503468.20090208222452@serebryakov.spb.ru> <200902082138.39688.hselasky@c2i.net> Message-ID: <1812245731.20090211193015@serebryakov.spb.ru> Hello, Hans. You wrote 8 ??????? 2009 ?., 23:38:38: > The only guide is to look at exisiting USB serial port drivers. With regard to > MosChip there already exits a umoscom2.c Yep, it is old, single-port chip, with different registers layout. BTW, datasheets on 7820/7840 chips are not complete, and some registers are left in driver as `magic' numbers. I don't like it, but Moschip doesn't answer on e-mails :( > Is your device multi port or single port? 4 ports. > It should be quite trivial to make a device driver for a serial port device. Yep, cleanup of existing "driver" (it was ugly) was straightforward. This provided "driver" can't even send BREAK signal :) -- // Black Lion AKA Lev Serebryakov From tamaru at myn.rcast.u-tokyo.ac.jp Wed Feb 11 08:52:06 2009 From: tamaru at myn.rcast.u-tokyo.ac.jp (Hiroharu Tamaru) Date: Wed Feb 11 08:52:14 2009 Subject: USB2: [was: umass not detected correctly, axe not transmitting] AXE problems In-Reply-To: <200902111657.38129.hselasky@c2i.net> References: <200902110954.37659.hselasky@c2i.net> <200902111657.38129.hselasky@c2i.net> Message-ID: At Wed, 11 Feb 2009 16:57:36 +0100, Hans Petter Selasky wrote: > > > > ugen3.3: at usbus3 > > > > axe0: on usbus3 > > > > axe0: PHYADDR 0xe0:0x18 > > > > miibus0: on axe0 > > > > ciphy0: PHY 24 on miibus0 > > > > ciphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, > > > > 1000baseT-FDX, auto ue0: on axe0 > > > > ue0: Ethernet address: 00:90:cc:xx:xx:xx > > > > ue0: link state changed to DOWN > > > > ue0: link state changed to UP > > > > > > > > > > > Turn on debugging: > > > > > > sysctl hw.usb2.axe.debug=15 > > > > > > And repeat test. > > > > with hw.usb2.axe.debug=15, I have: > > > > ugen3.3: at usbus3 (disconnected) > > pid 3244 (dhclient), uid 65: exited on signal 11 > > ugen3.3: at usbus3 > > axe0: on usbus3 > > axe0: PHYADDR 0xe0:0x18 > > miibus0: on axe0 > > ciphy0: PHY 24 on miibus0 > > ciphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, > > 1000baseT-FDX, auto ue0: on axe0 > > ue0: Ethernet address: 00:90:cc:f7:bc:2e > > ue0: link state changed to DOWN > > ue0: link state changed to UP > > > > > The hardware is a PLANEX GU-1000T ethernet adapter. > > > > What can I do now? > > Does netstat indicate any receive errors on the AXE interface? > > netstat -i Nope. Name Mtu Network Address Ipkts Ierrs Opkts Oerrs Coll ... ue0 1500 00:90:cc:f7:bc:2e 52 0 12 0 0 ue0 1500 192.168.1.0 192.168.1.3 0 - 4 - - The latter line is the result of statically asigning an address, and then 'ping -n 192.168.1.1'ing for four seconds. > Maybe "Pyun YongHyeon" should have a look at this. > > And you are running the latest current? I updated to -current as of about an hour or two ago. > --HPS Hiroharu From alfred at freebsd.org Wed Feb 11 14:57:02 2009 From: alfred at freebsd.org (Alfred Perlstein) Date: Wed Feb 11 14:57:08 2009 Subject: USB2: umass not detected correctly, axe not transmitting In-Reply-To: <200902110954.37659.hselasky@c2i.net> References: <200902110954.37659.hselasky@c2i.net> Message-ID: <20090211225701.GL68801@elvis.mu.org> * Hans Petter Selasky [090211 00:52] wrote: > Hi, > > On Wednesday 11 February 2009, Hiroharu Tamaru wrote: > > Hi, > > > > I have an Atom Z530 semi-embedded system and tried the new USB2 stack. > > I found some oddities and decided to report here. > > > > It is running 8.0-CURRENT as of yesterday, and I have GENERIC and USB2 > > kernels to test with. I am testing with two usb devices: > > > > umass0: on > > usbus3 axe0: on usbus3 > > > > First about the USB memory stick: > > > > 1) I setup a bootable USB memory stick, and this system > > boots off umass da0 if I have the old USB1 kernel. > > However, with USB2 kernel, it does not detect da0 at its final stage, > > and fails to find the root filesystem. > > I mean that the 'da0 at umass-sim0 bus 0 target 0 lun 0' message is not > > shown, and it is not listed in the kernel detected list of disks at > > 'mountroot>' prompt (shown by typing '?'). > > This is a known issue, see: > > http://wiki.freebsd.org/USB Is this the "delay in mountroot patch"? If so, I think it should go in. Can you send to Andrew for commit? If he's not available, please remind me to commit it. -- - Alfred Perlstein From imp at bsdimp.com Wed Feb 11 15:37:01 2009 From: imp at bsdimp.com (M. Warner Losh) Date: Wed Feb 11 15:37:07 2009 Subject: USB2: umass not detected correctly, axe not transmitting In-Reply-To: <20090211225701.GL68801@elvis.mu.org> References: <200902110954.37659.hselasky@c2i.net> <20090211225701.GL68801@elvis.mu.org> Message-ID: <20090211.163454.1678771438.imp@bsdimp.com> In message: <20090211225701.GL68801@elvis.mu.org> Alfred Perlstein writes: : * Hans Petter Selasky [090211 00:52] wrote: : > Hi, : > : > On Wednesday 11 February 2009, Hiroharu Tamaru wrote: : > > Hi, : > > : > > I have an Atom Z530 semi-embedded system and tried the new USB2 stack. : > > I found some oddities and decided to report here. : > > : > > It is running 8.0-CURRENT as of yesterday, and I have GENERIC and USB2 : > > kernels to test with. I am testing with two usb devices: : > > : > > umass0: on : > > usbus3 axe0: on usbus3 : > > : > > First about the USB memory stick: : > > : > > 1) I setup a bootable USB memory stick, and this system : > > boots off umass da0 if I have the old USB1 kernel. : > > However, with USB2 kernel, it does not detect da0 at its final stage, : > > and fails to find the root filesystem. : > > I mean that the 'da0 at umass-sim0 bus 0 target 0 lun 0' message is not : > > shown, and it is not listed in the kernel detected list of disks at : > > 'mountroot>' prompt (shown by typing '?'). : > : > This is a known issue, see: : > : > http://wiki.freebsd.org/USB : : Is this the "delay in mountroot patch"? If so, I think it should go : in. Can you send to Andrew for commit? If he's not available, please : remind me to commit it. That patch needs comments that say it is a workaround because we don't have a way to signal the mountroot code that all my configuration is done. This is a problem for all hot-plug technologies... but other than a comment, I'm cool with that patch going in. Warner From alfred at freebsd.org Wed Feb 11 16:29:38 2009 From: alfred at freebsd.org (Alfred Perlstein) Date: Wed Feb 11 16:29:45 2009 Subject: USB2: umass not detected correctly, axe not transmitting In-Reply-To: <20090211.163454.1678771438.imp@bsdimp.com> References: <200902110954.37659.hselasky@c2i.net> <20090211225701.GL68801@elvis.mu.org> <20090211.163454.1678771438.imp@bsdimp.com> Message-ID: <20090212002938.GM68801@elvis.mu.org> * M. Warner Losh [090211 15:37] wrote: > In message: <20090211225701.GL68801@elvis.mu.org> > Alfred Perlstein writes: > : * Hans Petter Selasky [090211 00:52] wrote: > : > Hi, > : > > : > On Wednesday 11 February 2009, Hiroharu Tamaru wrote: > : > > Hi, > : > > > : > > I have an Atom Z530 semi-embedded system and tried the new USB2 stack. > : > > I found some oddities and decided to report here. > : > > > : > > It is running 8.0-CURRENT as of yesterday, and I have GENERIC and USB2 > : > > kernels to test with. I am testing with two usb devices: > : > > > : > > umass0: on > : > > usbus3 axe0: on usbus3 > : > > > : > > First about the USB memory stick: > : > > > : > > 1) I setup a bootable USB memory stick, and this system > : > > boots off umass da0 if I have the old USB1 kernel. > : > > However, with USB2 kernel, it does not detect da0 at its final stage, > : > > and fails to find the root filesystem. > : > > I mean that the 'da0 at umass-sim0 bus 0 target 0 lun 0' message is not > : > > shown, and it is not listed in the kernel detected list of disks at > : > > 'mountroot>' prompt (shown by typing '?'). > : > > : > This is a known issue, see: > : > > : > http://wiki.freebsd.org/USB > : > : Is this the "delay in mountroot patch"? If so, I think it should go > : in. Can you send to Andrew for commit? If he's not available, please > : remind me to commit it. > > That patch needs comments that say it is a workaround because we don't > have a way to signal the mountroot code that all my configuration is > done. This is a problem for all hot-plug technologies... > > but other than a comment, I'm cool with that patch going in. Agreed. Will do. -- - Alfred Perlstein From pyunyh at gmail.com Wed Feb 11 18:56:52 2009 From: pyunyh at gmail.com (Pyun YongHyeon) Date: Wed Feb 11 18:56:59 2009 Subject: USB2: [was: umass not detected correctly, axe not transmitting] AXE problems In-Reply-To: References: <200902110954.37659.hselasky@c2i.net> <200902111657.38129.hselasky@c2i.net> Message-ID: <20090212023723.GA6313@michelle.cdnetworks.co.kr> On Thu, Feb 12, 2009 at 01:51:47AM +0900, Hiroharu Tamaru wrote: > > At Wed, 11 Feb 2009 16:57:36 +0100, Hans Petter Selasky wrote: > > > > > ugen3.3: at usbus3 > > > > > axe0: on usbus3 > > > > > axe0: PHYADDR 0xe0:0x18 > > > > > miibus0: on axe0 > > > > > ciphy0: PHY 24 on miibus0 > > > > > ciphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, > > > > > 1000baseT-FDX, auto ue0: on axe0 > > > > > ue0: Ethernet address: 00:90:cc:xx:xx:xx > > > > > ue0: link state changed to DOWN > > > > > ue0: link state changed to UP > > > > > > > > > > > > > > > Turn on debugging: > > > > > > > > sysctl hw.usb2.axe.debug=15 > > > > > > > > And repeat test. > > > > > > with hw.usb2.axe.debug=15, I have: > > > > > > ugen3.3: at usbus3 (disconnected) > > > pid 3244 (dhclient), uid 65: exited on signal 11 > > > ugen3.3: at usbus3 > > > axe0: on usbus3 > > > axe0: PHYADDR 0xe0:0x18 > > > miibus0: on axe0 > > > ciphy0: PHY 24 on miibus0 > > > ciphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, > > > 1000baseT-FDX, auto ue0: on axe0 > > > ue0: Ethernet address: 00:90:cc:f7:bc:2e > > > ue0: link state changed to DOWN > > > ue0: link state changed to UP > > > > > > > > The hardware is a PLANEX GU-1000T ethernet adapter. > > > I have the same USB controller and latest CURRENT works. axe0: on usbus1 axe0: PHYADDR 0xe0:0x18 miibus2: on axe0 ciphy0: PHY 24 on miibus2 ciphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 1000baseT-FDX, auto ue0: on axe0 ue0: Ethernet address: 00:90:cc:ef:b9:f6 ue0: link state changed to DOWN I manually loaded necessary kernel modules as my kernel does not have any USB device entries. The only regression since I tried USB2 axe(4) was failure of symbol resolving of link_elf in usb2_ethernet.ko module. Attached simple patch seems to fix that. To Hans, I think MODULE_DEPEND should come first before any reference to the module in usb2_ethernet.c. Since mii_phy_probe live in miibus(4) I added it too. > > > What can I do now? > > Hiroharu, if you unplug/replug UTP cable, does it make any difference? > > Does netstat indicate any receive errors on the AXE interface? > > > > netstat -i > > Nope. > > Name Mtu Network Address Ipkts Ierrs Opkts Oerrs Coll > ... > ue0 1500 00:90:cc:f7:bc:2e 52 0 12 0 0 > ue0 1500 192.168.1.0 192.168.1.3 0 - 4 - - > > The latter line is the result of statically asigning an address, > and then 'ping -n 192.168.1.1'ing for four seconds. > > > Maybe "Pyun YongHyeon" should have a look at this. > > > > And you are running the latest current? > > I updated to -current as of about an hour or two ago. > PS. Please CC to me I'm not subscribed to the list. From pyunyh at gmail.com Wed Feb 11 19:40:16 2009 From: pyunyh at gmail.com (Pyun YongHyeon) Date: Wed Feb 11 19:40:23 2009 Subject: USB2: [was: umass not detected correctly, axe not transmitting] AXE problems In-Reply-To: <20090212023723.GA6313@michelle.cdnetworks.co.kr> References: <200902110954.37659.hselasky@c2i.net> <200902111657.38129.hselasky@c2i.net> <20090212023723.GA6313@michelle.cdnetworks.co.kr> Message-ID: <20090212034251.GB6313@michelle.cdnetworks.co.kr> On Thu, Feb 12, 2009 at 11:37:23AM +0900, Pyun YongHyeon wrote: > On Thu, Feb 12, 2009 at 01:51:47AM +0900, Hiroharu Tamaru wrote: > > > > At Wed, 11 Feb 2009 16:57:36 +0100, Hans Petter Selasky wrote: > > > > > > ugen3.3: at usbus3 > > > > > > axe0: on usbus3 > > > > > > axe0: PHYADDR 0xe0:0x18 > > > > > > miibus0: on axe0 > > > > > > ciphy0: PHY 24 on miibus0 > > > > > > ciphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, > > > > > > 1000baseT-FDX, auto ue0: on axe0 > > > > > > ue0: Ethernet address: 00:90:cc:xx:xx:xx > > > > > > ue0: link state changed to DOWN > > > > > > ue0: link state changed to UP > > > > > > > > > > > > > > > > > > > Turn on debugging: > > > > > > > > > > sysctl hw.usb2.axe.debug=15 > > > > > > > > > > And repeat test. > > > > > > > > with hw.usb2.axe.debug=15, I have: > > > > > > > > ugen3.3: at usbus3 (disconnected) > > > > pid 3244 (dhclient), uid 65: exited on signal 11 > > > > ugen3.3: at usbus3 > > > > axe0: on usbus3 > > > > axe0: PHYADDR 0xe0:0x18 > > > > miibus0: on axe0 > > > > ciphy0: PHY 24 on miibus0 > > > > ciphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, > > > > 1000baseT-FDX, auto ue0: on axe0 > > > > ue0: Ethernet address: 00:90:cc:f7:bc:2e > > > > ue0: link state changed to DOWN > > > > ue0: link state changed to UP > > > > > > > > > > > The hardware is a PLANEX GU-1000T ethernet adapter. > > > > > > > I have the same USB controller and latest CURRENT works. > > axe0: on usbus1 > axe0: PHYADDR 0xe0:0x18 > miibus2: on axe0 > ciphy0: PHY 24 on miibus2 > ciphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 1000baseT-FDX, auto > ue0: on axe0 > ue0: Ethernet address: 00:90:cc:ef:b9:f6 > ue0: link state changed to DOWN > > I manually loaded necessary kernel modules as my kernel does not > have any USB device entries. The only regression since I tried USB2 > axe(4) was failure of symbol resolving of link_elf in > usb2_ethernet.ko module. Attached simple patch seems to fix that. > > To Hans, > I think MODULE_DEPEND should come first before any reference to > the module in usb2_ethernet.c. Since mii_phy_probe live in > miibus(4) I added it too. > Hans, I managed to track down Hiroharu's issue in axe(4). It seems Andrew removed link handling code that ensures correct state of established link in r188412. I believe we have to revert changes made in axe_cfg_mii_statchg() and axe_tick(). I have no idea what was happend in P4, you checked in the link handling code I submitted. From tamaru at myn.rcast.u-tokyo.ac.jp Wed Feb 11 19:51:22 2009 From: tamaru at myn.rcast.u-tokyo.ac.jp (Hiroharu Tamaru) Date: Wed Feb 11 19:51:28 2009 Subject: USB2: [was: umass not detected correctly, axe not transmitting] AXE problems In-Reply-To: <20090212023723.GA6313@michelle.cdnetworks.co.kr> References: <200902110954.37659.hselasky@c2i.net> <200902111657.38129.hselasky@c2i.net> <20090212023723.GA6313@michelle.cdnetworks.co.kr> Message-ID: Hello Pyun, At Thu, 12 Feb 2009 11:37:23 +0900, Pyun YongHyeon wrote: > > [1 ] > On Thu, Feb 12, 2009 at 01:51:47AM +0900, Hiroharu Tamaru wrote: > > > > At Wed, 11 Feb 2009 16:57:36 +0100, Hans Petter Selasky wrote: > > > > > > ugen3.3: at usbus3 > > > > > > axe0: on usbus3 > > > > > > axe0: PHYADDR 0xe0:0x18 > > > > > > miibus0: on axe0 > > > > > > ciphy0: PHY 24 on miibus0 > > > > > > ciphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, > > > > > > 1000baseT-FDX, auto ue0: on axe0 > > > > > > ue0: Ethernet address: 00:90:cc:xx:xx:xx > > > > > > ue0: link state changed to DOWN > > > > > > ue0: link state changed to UP > > > > > > > > > > > > > > > > > > > Turn on debugging: > > > > > > > > > > sysctl hw.usb2.axe.debug=15 > > > > > > > > > > And repeat test. > > > > > > > > with hw.usb2.axe.debug=15, I have: > > > > > > > > ugen3.3: at usbus3 (disconnected) > > > > pid 3244 (dhclient), uid 65: exited on signal 11 > > > > ugen3.3: at usbus3 > > > > axe0: on usbus3 > > > > axe0: PHYADDR 0xe0:0x18 > > > > miibus0: on axe0 > > > > ciphy0: PHY 24 on miibus0 > > > > ciphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, > > > > 1000baseT-FDX, auto ue0: on axe0 > > > > ue0: Ethernet address: 00:90:cc:f7:bc:2e > > > > ue0: link state changed to DOWN > > > > ue0: link state changed to UP > > > > > > > > > > > The hardware is a PLANEX GU-1000T ethernet adapter. > > > > > > > I have the same USB controller and latest CURRENT works. > > axe0: on usbus1 > axe0: PHYADDR 0xe0:0x18 > miibus2: on axe0 > ciphy0: PHY 24 on miibus2 > ciphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 1000baseT-FDX, auto > ue0: on axe0 > ue0: Ethernet address: 00:90:cc:ef:b9:f6 > ue0: link state changed to DOWN > > I manually loaded necessary kernel modules as my kernel does not > have any USB device entries. The only regression since I tried USB2 > axe(4) was failure of symbol resolving of link_elf in > usb2_ethernet.ko module. Attached simple patch seems to fix that. > > To Hans, > I think MODULE_DEPEND should come first before any reference to > the module in usb2_ethernet.c. Since mii_phy_probe live in > miibus(4) I added it too. > > > > > What can I do now? > > > > > Hiroharu, if you unplug/replug UTP cable, does it make any difference? No, I tried combinations of repluging UTP cable and repluging the device itself, but the resuts are always the same. It receives packets from the wire, but it cannot send one. But I noticed one thing now. I also have em0/em1 interfaces, and I am switching with ue0 when I test AXE. It turned out that although I 'ifconfig em0 inet delete down' those unused interfaces, the arp table entries remain. 'arp -nda' shows 'delete: cannot locate 192.168.1.1' and the like for every entry in the table, and they are infact not deleted. Deletion fails both when em0 is up and down. Then again, this time I booted with a configuration such that em0/em1 are not touched at all, and axe device plugged with UTP cable from the very start (before powering on), and the symptom is the same (recive OK, send NG), and this time the arp table has the single line which corresponds to self address of ue0/AXE. I am rebuilding my userland world now, just to make sure (it used to be Dec. 2008 snapshot), but are there anything that may be out of sync in the December-Feburary time slot? Anyway, this should take some good while. After that, I will try a kernel without USB1 nor USB2 configured, and will load the modules manually as you have done, with your attached patches. > > > Does netstat indicate any receive errors on the AXE interface? > > > > > > netstat -i > > > > Nope. > > > > Name Mtu Network Address Ipkts Ierrs Opkts Oerrs Coll > > ... > > ue0 1500 00:90:cc:f7:bc:2e 52 0 12 0 0 > > ue0 1500 192.168.1.0 192.168.1.3 0 - 4 - - > > > > The latter line is the result of statically asigning an address, > > and then 'ping -n 192.168.1.1'ing for four seconds. > > > > > Maybe "Pyun YongHyeon" should have a look at this. > > > > > > And you are running the latest current? > > > > I updated to -current as of about an hour or two ago. > > > > PS. Please CC to me I'm not subscribed to the list. > [2 usb2_ethernet.patch ] > Index: sys/dev/usb2/ethernet/usb2_ethernet.c > =================================================================== > --- sys/dev/usb2/ethernet/usb2_ethernet.c (revision 188507) > +++ sys/dev/usb2/ethernet/usb2_ethernet.c (working copy) > @@ -43,6 +43,9 @@ > #define UE_UNLOCK(_ue) mtx_unlock((_ue)->ue_mtx) > #define UE_LOCK_ASSERT(_ue, t) mtx_assert((_ue)->ue_mtx, t) > > +MODULE_DEPEND(usb2_ethernet, usb2_core, 1, 1, 1); > +MODULE_DEPEND(usb2_ethernet, miibus, 1, 1, 1); > + > static struct unrhdr *ueunit; > > static usb2_proc_callback_t ue_attach_post_task; > @@ -582,4 +585,3 @@ > > DECLARE_MODULE(usb2_ethernet, usb2_ether_mod, SI_SUB_PSEUDO, SI_ORDER_ANY); > MODULE_VERSION(usb2_ethernet, 1); > -MODULE_DEPEND(usb2_ethernet, usb2_core, 1, 1, 1); Thanks, Hiroharu From thompsa at FreeBSD.org Wed Feb 11 19:57:59 2009 From: thompsa at FreeBSD.org (Andrew Thompson) Date: Wed Feb 11 19:58:05 2009 Subject: USB2: [was: umass not detected correctly, axe not transmitting] AXE problems In-Reply-To: <20090212034251.GB6313@michelle.cdnetworks.co.kr> References: <200902110954.37659.hselasky@c2i.net> <200902111657.38129.hselasky@c2i.net> <20090212023723.GA6313@michelle.cdnetworks.co.kr> <20090212034251.GB6313@michelle.cdnetworks.co.kr> Message-ID: <20090212035752.GC74077@citylink.fud.org.nz> On Thu, Feb 12, 2009 at 12:42:51PM +0900, Pyun YongHyeon wrote: > > > > I have the same USB controller and latest CURRENT works. > > > > axe0: on usbus1 > > axe0: PHYADDR 0xe0:0x18 > > miibus2: on axe0 > > ciphy0: PHY 24 on miibus2 > > ciphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 1000baseT-FDX, auto > > ue0: on axe0 > > ue0: Ethernet address: 00:90:cc:ef:b9:f6 > > ue0: link state changed to DOWN > > > > I manually loaded necessary kernel modules as my kernel does not > > have any USB device entries. The only regression since I tried USB2 > > axe(4) was failure of symbol resolving of link_elf in > > usb2_ethernet.ko module. Attached simple patch seems to fix that. > > > > To Hans, > > I think MODULE_DEPEND should come first before any reference to > > the module in usb2_ethernet.c. Since mii_phy_probe live in > > miibus(4) I added it too. > > > > Hans, I managed to track down Hiroharu's issue in axe(4). It seems > Andrew removed link handling code that ensures correct state of > established link in r188412. > I believe we have to revert changes made in axe_cfg_mii_statchg() > and axe_tick(). I have no idea what was happend in P4, you > checked in the link handling code I submitted. Thanks for finding this Pyun, an unintentional breakage due to the code reshuffle. Have you committed the fix, I dont see it? Andrew From tamaru at myn.rcast.u-tokyo.ac.jp Wed Feb 11 19:59:34 2009 From: tamaru at myn.rcast.u-tokyo.ac.jp (Hiroharu Tamaru) Date: Wed Feb 11 19:59:40 2009 Subject: USB2: [was: umass not detected correctly, axe not transmitting] AXE problems In-Reply-To: <20090212034251.GB6313@michelle.cdnetworks.co.kr> References: <200902110954.37659.hselasky@c2i.net> <200902111657.38129.hselasky@c2i.net> <20090212023723.GA6313@michelle.cdnetworks.co.kr> <20090212034251.GB6313@michelle.cdnetworks.co.kr> Message-ID: I've just sent another message before reading this. At Thu, 12 Feb 2009 12:42:51 +0900, Pyun YongHyeon wrote: > On Thu, Feb 12, 2009 at 11:37:23AM +0900, Pyun YongHyeon wrote: > > On Thu, Feb 12, 2009 at 01:51:47AM +0900, Hiroharu Tamaru wrote: > > > > > > At Wed, 11 Feb 2009 16:57:36 +0100, Hans Petter Selasky wrote: > > > > > > > ugen3.3: at usbus3 > > > > > > > axe0: on usbus3 > > > > > > > axe0: PHYADDR 0xe0:0x18 > > > > > > > miibus0: on axe0 > > > > > > > ciphy0: PHY 24 on miibus0 > > > > > > > ciphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, > > > > > > > 1000baseT-FDX, auto ue0: on axe0 > > > > > > > ue0: Ethernet address: 00:90:cc:xx:xx:xx > > > > > > > ue0: link state changed to DOWN > > > > > > > ue0: link state changed to UP > > > > > > > > > > > > > > > > > > > > > > > Turn on debugging: > > > > > > > > > > > > sysctl hw.usb2.axe.debug=15 > > > > > > > > > > > > And repeat test. > > > > > > > > > > with hw.usb2.axe.debug=15, I have: > > > > > > > > > > ugen3.3: at usbus3 (disconnected) > > > > > pid 3244 (dhclient), uid 65: exited on signal 11 > > > > > ugen3.3: at usbus3 > > > > > axe0: on usbus3 > > > > > axe0: PHYADDR 0xe0:0x18 > > > > > miibus0: on axe0 > > > > > ciphy0: PHY 24 on miibus0 > > > > > ciphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, > > > > > 1000baseT-FDX, auto ue0: on axe0 > > > > > ue0: Ethernet address: 00:90:cc:f7:bc:2e > > > > > ue0: link state changed to DOWN > > > > > ue0: link state changed to UP > > > > > > > > > > > > > > The hardware is a PLANEX GU-1000T ethernet adapter. > > > > > > > > > > > I have the same USB controller and latest CURRENT works. > > > > axe0: on usbus1 > > axe0: PHYADDR 0xe0:0x18 > > miibus2: on axe0 > > ciphy0: PHY 24 on miibus2 > > ciphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 1000baseT-FDX, auto > > ue0: on axe0 > > ue0: Ethernet address: 00:90:cc:ef:b9:f6 > > ue0: link state changed to DOWN > > > > I manually loaded necessary kernel modules as my kernel does not > > have any USB device entries. The only regression since I tried USB2 > > axe(4) was failure of symbol resolving of link_elf in > > usb2_ethernet.ko module. Attached simple patch seems to fix that. > > > > To Hans, > > I think MODULE_DEPEND should come first before any reference to > > the module in usb2_ethernet.c. Since mii_phy_probe live in > > miibus(4) I added it too. > > > > Hans, I managed to track down Hiroharu's issue in axe(4). It seems > Andrew removed link handling code that ensures correct state of > established link in r188412. > I believe we have to revert changes made in axe_cfg_mii_statchg() > and axe_tick(). I have no idea what was happend in P4, you > checked in the link handling code I submitted. Thanks for looking into this. So, can I just be waiting for a patch to test, or a CVS revision of files to revert to? Meanwhile, I'll bring the userland to the latest current, as I mentioned on the other mail. Hiroharu From thompsa at FreeBSD.org Wed Feb 11 20:23:59 2009 From: thompsa at FreeBSD.org (Andrew Thompson) Date: Wed Feb 11 20:24:14 2009 Subject: Recent Changes to Rum driver - seems to have.. In-Reply-To: <200902111000.46643.hselasky@c2i.net> References: <200902111000.46643.hselasky@c2i.net> Message-ID: <20090212042350.GE74077@citylink.fud.org.nz> On Wed, Feb 11, 2009 at 10:00:45AM +0100, Hans Petter Selasky wrote: > On Tuesday 10 February 2009, Thomas Sparrevohn wrote: > > Reintroduced panics when the device is used heavily - it also reports the > > "needs callback" in dmesg - Unless this is known I can post a dmesg > > > > Hi Thomas, > > Andrew Thompson decided to re-port the driver from USB1. I've tried to fix > most of the bugs now. If the fixes are not in -current yet you can fetch > if_rum*[ch] from: > > svn --username anonsvn --password anonsvn \ > checkout svn://svn.turbocat.net/i4b/trunk/i4b/src/sys/dev/usb2 > > > Do you have a backtrace of the panics ? > > Sorry about the inconvenience. Please watch the mud slinging, there were very good reasons for changing the wlan code back to the USB1 state (bugs and all). Each regression will be investigated and fixed. From pyunyh at gmail.com Wed Feb 11 20:28:00 2009 From: pyunyh at gmail.com (Pyun YongHyeon) Date: Wed Feb 11 20:28:06 2009 Subject: USB2: [was: umass not detected correctly, axe not transmitting] AXE problems In-Reply-To: References: <200902110954.37659.hselasky@c2i.net> <200902111657.38129.hselasky@c2i.net> <20090212023723.GA6313@michelle.cdnetworks.co.kr> <20090212034251.GB6313@michelle.cdnetworks.co.kr> Message-ID: <20090212043033.GC6313@michelle.cdnetworks.co.kr> On Thu, Feb 12, 2009 at 12:59:13PM +0900, Hiroharu Tamaru wrote: > I've just sent another message before reading this. > > At Thu, 12 Feb 2009 12:42:51 +0900, Pyun YongHyeon wrote: > > On Thu, Feb 12, 2009 at 11:37:23AM +0900, Pyun YongHyeon wrote: > > > On Thu, Feb 12, 2009 at 01:51:47AM +0900, Hiroharu Tamaru wrote: > > > > > > > > At Wed, 11 Feb 2009 16:57:36 +0100, Hans Petter Selasky wrote: > > > > > > > > ugen3.3: at usbus3 > > > > > > > > axe0: on usbus3 > > > > > > > > axe0: PHYADDR 0xe0:0x18 > > > > > > > > miibus0: on axe0 > > > > > > > > ciphy0: PHY 24 on miibus0 > > > > > > > > ciphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, > > > > > > > > 1000baseT-FDX, auto ue0: on axe0 > > > > > > > > ue0: Ethernet address: 00:90:cc:xx:xx:xx > > > > > > > > ue0: link state changed to DOWN > > > > > > > > ue0: link state changed to UP > > > > > > > > > > > > > > > > > > > > > > > > > > > Turn on debugging: > > > > > > > > > > > > > > sysctl hw.usb2.axe.debug=15 > > > > > > > > > > > > > > And repeat test. > > > > > > > > > > > > with hw.usb2.axe.debug=15, I have: > > > > > > > > > > > > ugen3.3: at usbus3 (disconnected) > > > > > > pid 3244 (dhclient), uid 65: exited on signal 11 > > > > > > ugen3.3: at usbus3 > > > > > > axe0: on usbus3 > > > > > > axe0: PHYADDR 0xe0:0x18 > > > > > > miibus0: on axe0 > > > > > > ciphy0: PHY 24 on miibus0 > > > > > > ciphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, > > > > > > 1000baseT-FDX, auto ue0: on axe0 > > > > > > ue0: Ethernet address: 00:90:cc:f7:bc:2e > > > > > > ue0: link state changed to DOWN > > > > > > ue0: link state changed to UP > > > > > > > > > > > > > > > > > The hardware is a PLANEX GU-1000T ethernet adapter. > > > > > > > > > > > > > > > I have the same USB controller and latest CURRENT works. > > > > > > axe0: on usbus1 > > > axe0: PHYADDR 0xe0:0x18 > > > miibus2: on axe0 > > > ciphy0: PHY 24 on miibus2 > > > ciphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 1000baseT-FDX, auto > > > ue0: on axe0 > > > ue0: Ethernet address: 00:90:cc:ef:b9:f6 > > > ue0: link state changed to DOWN > > > > > > I manually loaded necessary kernel modules as my kernel does not > > > have any USB device entries. The only regression since I tried USB2 > > > axe(4) was failure of symbol resolving of link_elf in > > > usb2_ethernet.ko module. Attached simple patch seems to fix that. > > > > > > To Hans, > > > I think MODULE_DEPEND should come first before any reference to > > > the module in usb2_ethernet.c. Since mii_phy_probe live in > > > miibus(4) I added it too. > > > > > > > Hans, I managed to track down Hiroharu's issue in axe(4). It seems > > Andrew removed link handling code that ensures correct state of > > established link in r188412. > > I believe we have to revert changes made in axe_cfg_mii_statchg() > > and axe_tick(). I have no idea what was happend in P4, you > > checked in the link handling code I submitted. > > Thanks for looking into this. > > So, can I just be waiting for a patch to test, or a CVS > revision of files to revert to? > > Meanwhile, I'll bring the userland to the latest current, as > I mentioned on the other mail. > Ok, try this one after installword. Attached one restores previous link handle code. Note, it was just compile tested. > Hiroharu -------------- next part -------------- Index: sys/dev/usb2/ethernet/usb2_ethernet.c =================================================================== --- sys/dev/usb2/ethernet/usb2_ethernet.c (revision 188507) +++ sys/dev/usb2/ethernet/usb2_ethernet.c (working copy) @@ -43,6 +43,9 @@ #define UE_UNLOCK(_ue) mtx_unlock((_ue)->ue_mtx) #define UE_LOCK_ASSERT(_ue, t) mtx_assert((_ue)->ue_mtx, t) +MODULE_DEPEND(usb2_ethernet, usb2_core, 1, 1, 1); +MODULE_DEPEND(usb2_ethernet, miibus, 1, 1, 1); + static struct unrhdr *ueunit; static usb2_proc_callback_t ue_attach_post_task; @@ -582,4 +585,3 @@ DECLARE_MODULE(usb2_ethernet, usb2_ether_mod, SI_SUB_PSEUDO, SI_ORDER_ANY); MODULE_VERSION(usb2_ethernet, 1); -MODULE_DEPEND(usb2_ethernet, usb2_core, 1, 1, 1); Index: sys/dev/usb2/ethernet/if_axe2.c =================================================================== --- sys/dev/usb2/ethernet/if_axe2.c (revision 188507) +++ sys/dev/usb2/ethernet/if_axe2.c (working copy) @@ -341,6 +341,7 @@ { struct axe_softc *sc = device_get_softc(dev); struct mii_data *mii = GET_MII(sc); + struct ifnet *ifp; uint16_t val; int err, locked; @@ -348,11 +349,40 @@ if (!locked) AXE_LOCK(sc); - val = (mii->mii_media_active & IFM_GMASK) == IFM_FDX ? - AXE_MEDIA_FULL_DUPLEX : 0; + ifp = usb2_ether_getifp(&sc->sc_ue); + if (mii == NULL || ifp == NULL || + (ifp->if_drv_flags & IFF_DRV_RUNNING) == 0) + goto done; + + sc->sc_flags &= ~AXE_FLAG_LINK; + if ((mii->mii_media_status & (IFM_ACTIVE | IFM_AVALID)) == + (IFM_ACTIVE | IFM_AVALID)) { + switch (IFM_SUBTYPE(mii->mii_media_active)) { + case IFM_10_T: + case IFM_100_TX: + sc->sc_flags |= AXE_FLAG_LINK; + break; + case IFM_1000_T: + if ((sc->sc_flags & AXE_FLAG_178) == 0) + break; + sc->sc_flags |= AXE_FLAG_LINK; + break; + default: + break; + } + } + + /* Lost link, do nothing. */ + if ((sc->sc_flags & AXE_FLAG_LINK) == 0) + goto done; + + val = 0; + if ((IFM_OPTIONS(mii->mii_media_active) & IFM_FDX) != 0) + val |= AXE_MEDIA_FULL_DUPLEX; if (sc->sc_flags & (AXE_FLAG_178 | AXE_FLAG_772)) { val |= AXE_178_MEDIA_RX_EN | AXE_178_MEDIA_MAGIC; - + if ((sc->sc_flags & AXE_FLAG_178) != 0) + val |= AXE_178_MEDIA_ENCK; switch (IFM_SUBTYPE(mii->mii_media_active)) { case IFM_1000_T: val |= AXE_178_MEDIA_GMII | AXE_178_MEDIA_ENCK; @@ -368,7 +398,7 @@ err = axe_cmd(sc, AXE_CMD_WRITE_MEDIA, 0, val, NULL); if (err) device_printf(dev, "media change failed, error %d\n", err); - +done: if (!locked) AXE_UNLOCK(sc); } @@ -381,18 +411,18 @@ { struct axe_softc *sc = ifp->if_softc; struct mii_data *mii = GET_MII(sc); + int error; AXE_LOCK_ASSERT(sc, MA_OWNED); - sc->sc_flags &= ~AXE_FLAG_LINK; if (mii->mii_instance) { struct mii_softc *miisc; LIST_FOREACH(miisc, &mii->mii_phys, mii_list) mii_phy_reset(miisc); } - mii_mediachg(mii); - return (0); + error = mii_mediachg(mii); + return (error); } /* @@ -915,11 +945,10 @@ AXE_LOCK_ASSERT(sc, MA_OWNED); mii_tick(mii); - if ((sc->sc_flags & AXE_FLAG_LINK) == 0 - && mii->mii_media_status & IFM_ACTIVE && - IFM_SUBTYPE(mii->mii_media_active) != IFM_NONE) { - sc->sc_flags |= AXE_FLAG_LINK; - axe_start(ue); + if ((sc->sc_flags & AXE_FLAG_LINK) == 0) { + axe_miibus_statchg(ue->ue_dev); + if ((sc->sc_flags & AXE_FLAG_LINK) != 0) + axe_start(ue); } } From pyunyh at gmail.com Wed Feb 11 20:31:18 2009 From: pyunyh at gmail.com (Pyun YongHyeon) Date: Wed Feb 11 20:31:26 2009 Subject: USB2: [was: umass not detected correctly, axe not transmitting] AXE problems In-Reply-To: <20090212035752.GC74077@citylink.fud.org.nz> References: <200902110954.37659.hselasky@c2i.net> <200902111657.38129.hselasky@c2i.net> <20090212023723.GA6313@michelle.cdnetworks.co.kr> <20090212034251.GB6313@michelle.cdnetworks.co.kr> <20090212035752.GC74077@citylink.fud.org.nz> Message-ID: <20090212043351.GD6313@michelle.cdnetworks.co.kr> On Wed, Feb 11, 2009 at 07:57:52PM -0800, Andrew Thompson wrote: > On Thu, Feb 12, 2009 at 12:42:51PM +0900, Pyun YongHyeon wrote: > > > > > > I have the same USB controller and latest CURRENT works. > > > > > > axe0: on usbus1 > > > axe0: PHYADDR 0xe0:0x18 > > > miibus2: on axe0 > > > ciphy0: PHY 24 on miibus2 > > > ciphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 1000baseT-FDX, auto > > > ue0: on axe0 > > > ue0: Ethernet address: 00:90:cc:ef:b9:f6 > > > ue0: link state changed to DOWN > > > > > > I manually loaded necessary kernel modules as my kernel does not > > > have any USB device entries. The only regression since I tried USB2 > > > axe(4) was failure of symbol resolving of link_elf in > > > usb2_ethernet.ko module. Attached simple patch seems to fix that. > > > > > > To Hans, > > > I think MODULE_DEPEND should come first before any reference to > > > the module in usb2_ethernet.c. Since mii_phy_probe live in > > > miibus(4) I added it too. > > > > > > > Hans, I managed to track down Hiroharu's issue in axe(4). It seems > > Andrew removed link handling code that ensures correct state of > > established link in r188412. > > I believe we have to revert changes made in axe_cfg_mii_statchg() > > and axe_tick(). I have no idea what was happend in P4, you > > checked in the link handling code I submitted. > > Thanks for finding this Pyun, an unintentional breakage due to the code > reshuffle. Have you committed the fix, I dont see it? > Not yet. I've posted possible fix for axe(4) so let's see how it goes first. From tamaru at myn.rcast.u-tokyo.ac.jp Wed Feb 11 20:38:07 2009 From: tamaru at myn.rcast.u-tokyo.ac.jp (Hiroharu Tamaru) Date: Wed Feb 11 20:38:14 2009 Subject: USB2: [was: umass not detected correctly, axe not transmitting] AXE problems In-Reply-To: <20090212043033.GC6313@michelle.cdnetworks.co.kr> References: <200902110954.37659.hselasky@c2i.net> <200902111657.38129.hselasky@c2i.net> <20090212023723.GA6313@michelle.cdnetworks.co.kr> <20090212034251.GB6313@michelle.cdnetworks.co.kr> <20090212043033.GC6313@michelle.cdnetworks.co.kr> Message-ID: At Thu, 12 Feb 2009 13:30:33 +0900, Pyun YongHyeon wrote: > [1 ] > On Thu, Feb 12, 2009 at 12:59:13PM +0900, Hiroharu Tamaru wrote: > > I've just sent another message before reading this. > > > > At Thu, 12 Feb 2009 12:42:51 +0900, Pyun YongHyeon wrote: > > > On Thu, Feb 12, 2009 at 11:37:23AM +0900, Pyun YongHyeon wrote: > > > > On Thu, Feb 12, 2009 at 01:51:47AM +0900, Hiroharu Tamaru wrote: > > > > > > > > > > At Wed, 11 Feb 2009 16:57:36 +0100, Hans Petter Selasky wrote: > > > > > > > > > ugen3.3: at usbus3 > > > > > > > > > axe0: on usbus3 > > > > > > > > > axe0: PHYADDR 0xe0:0x18 > > > > > > > > > miibus0: on axe0 > > > > > > > > > ciphy0: PHY 24 on miibus0 > > > > > > > > > ciphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, > > > > > > > > > 1000baseT-FDX, auto ue0: on axe0 > > > > > > > > > ue0: Ethernet address: 00:90:cc:xx:xx:xx > > > > > > > > > ue0: link state changed to DOWN > > > > > > > > > ue0: link state changed to UP > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > Turn on debugging: > > > > > > > > > > > > > > > > sysctl hw.usb2.axe.debug=15 > > > > > > > > > > > > > > > > And repeat test. > > > > > > > > > > > > > > with hw.usb2.axe.debug=15, I have: > > > > > > > > > > > > > > ugen3.3: at usbus3 (disconnected) > > > > > > > pid 3244 (dhclient), uid 65: exited on signal 11 > > > > > > > ugen3.3: at usbus3 > > > > > > > axe0: on usbus3 > > > > > > > axe0: PHYADDR 0xe0:0x18 > > > > > > > miibus0: on axe0 > > > > > > > ciphy0: PHY 24 on miibus0 > > > > > > > ciphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, > > > > > > > 1000baseT-FDX, auto ue0: on axe0 > > > > > > > ue0: Ethernet address: 00:90:cc:f7:bc:2e > > > > > > > ue0: link state changed to DOWN > > > > > > > ue0: link state changed to UP > > > > > > > > > > > > > > > > > > > > The hardware is a PLANEX GU-1000T ethernet adapter. > > > > > > > > > > > > > > > > > > > I have the same USB controller and latest CURRENT works. > > > > > > > > axe0: on usbus1 > > > > axe0: PHYADDR 0xe0:0x18 > > > > miibus2: on axe0 > > > > ciphy0: PHY 24 on miibus2 > > > > ciphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 1000baseT-FDX, auto > > > > ue0: on axe0 > > > > ue0: Ethernet address: 00:90:cc:ef:b9:f6 > > > > ue0: link state changed to DOWN > > > > > > > > I manually loaded necessary kernel modules as my kernel does not > > > > have any USB device entries. The only regression since I tried USB2 > > > > axe(4) was failure of symbol resolving of link_elf in > > > > usb2_ethernet.ko module. Attached simple patch seems to fix that. > > > > > > > > To Hans, > > > > I think MODULE_DEPEND should come first before any reference to > > > > the module in usb2_ethernet.c. Since mii_phy_probe live in > > > > miibus(4) I added it too. > > > > > > > > > > Hans, I managed to track down Hiroharu's issue in axe(4). It seems > > > Andrew removed link handling code that ensures correct state of > > > established link in r188412. > > > I believe we have to revert changes made in axe_cfg_mii_statchg() > > > and axe_tick(). I have no idea what was happend in P4, you > > > checked in the link handling code I submitted. > > > > Thanks for looking into this. > > > > So, can I just be waiting for a patch to test, or a CVS > > revision of files to revert to? > > > > Meanwhile, I'll bring the userland to the latest current, as > > I mentioned on the other mail. > > > > Ok, try this one after installword. Attached one restores previous > link handle code. Note, it was just compile tested. Thanks, will do. Could take half a day or so building the world and all on this host, though. I'll be back with the results. > > Hiroharu > [2 usb2_ethernet.patch2 ] > Index: sys/dev/usb2/ethernet/usb2_ethernet.c > =================================================================== > --- sys/dev/usb2/ethernet/usb2_ethernet.c (revision 188507) > +++ sys/dev/usb2/ethernet/usb2_ethernet.c (working copy) > @@ -43,6 +43,9 @@ > #define UE_UNLOCK(_ue) mtx_unlock((_ue)->ue_mtx) > #define UE_LOCK_ASSERT(_ue, t) mtx_assert((_ue)->ue_mtx, t) > > +MODULE_DEPEND(usb2_ethernet, usb2_core, 1, 1, 1); > +MODULE_DEPEND(usb2_ethernet, miibus, 1, 1, 1); > + > static struct unrhdr *ueunit; > > static usb2_proc_callback_t ue_attach_post_task; > @@ -582,4 +585,3 @@ > > DECLARE_MODULE(usb2_ethernet, usb2_ether_mod, SI_SUB_PSEUDO, SI_ORDER_ANY); > MODULE_VERSION(usb2_ethernet, 1); > -MODULE_DEPEND(usb2_ethernet, usb2_core, 1, 1, 1); > Index: sys/dev/usb2/ethernet/if_axe2.c > =================================================================== > --- sys/dev/usb2/ethernet/if_axe2.c (revision 188507) > +++ sys/dev/usb2/ethernet/if_axe2.c (working copy) > @@ -341,6 +341,7 @@ > { > struct axe_softc *sc = device_get_softc(dev); > struct mii_data *mii = GET_MII(sc); > + struct ifnet *ifp; > uint16_t val; > int err, locked; > > @@ -348,11 +349,40 @@ > if (!locked) > AXE_LOCK(sc); > > - val = (mii->mii_media_active & IFM_GMASK) == IFM_FDX ? > - AXE_MEDIA_FULL_DUPLEX : 0; > + ifp = usb2_ether_getifp(&sc->sc_ue); > + if (mii == NULL || ifp == NULL || > + (ifp->if_drv_flags & IFF_DRV_RUNNING) == 0) > + goto done; > + > + sc->sc_flags &= ~AXE_FLAG_LINK; > + if ((mii->mii_media_status & (IFM_ACTIVE | IFM_AVALID)) == > + (IFM_ACTIVE | IFM_AVALID)) { > + switch (IFM_SUBTYPE(mii->mii_media_active)) { > + case IFM_10_T: > + case IFM_100_TX: > + sc->sc_flags |= AXE_FLAG_LINK; > + break; > + case IFM_1000_T: > + if ((sc->sc_flags & AXE_FLAG_178) == 0) > + break; > + sc->sc_flags |= AXE_FLAG_LINK; > + break; > + default: > + break; > + } > + } > + > + /* Lost link, do nothing. */ > + if ((sc->sc_flags & AXE_FLAG_LINK) == 0) > + goto done; > + > + val = 0; > + if ((IFM_OPTIONS(mii->mii_media_active) & IFM_FDX) != 0) > + val |= AXE_MEDIA_FULL_DUPLEX; > if (sc->sc_flags & (AXE_FLAG_178 | AXE_FLAG_772)) { > val |= AXE_178_MEDIA_RX_EN | AXE_178_MEDIA_MAGIC; > - > + if ((sc->sc_flags & AXE_FLAG_178) != 0) > + val |= AXE_178_MEDIA_ENCK; > switch (IFM_SUBTYPE(mii->mii_media_active)) { > case IFM_1000_T: > val |= AXE_178_MEDIA_GMII | AXE_178_MEDIA_ENCK; > @@ -368,7 +398,7 @@ > err = axe_cmd(sc, AXE_CMD_WRITE_MEDIA, 0, val, NULL); > if (err) > device_printf(dev, "media change failed, error %d\n", err); > - > +done: > if (!locked) > AXE_UNLOCK(sc); > } > @@ -381,18 +411,18 @@ > { > struct axe_softc *sc = ifp->if_softc; > struct mii_data *mii = GET_MII(sc); > + int error; > > AXE_LOCK_ASSERT(sc, MA_OWNED); > > - sc->sc_flags &= ~AXE_FLAG_LINK; > if (mii->mii_instance) { > struct mii_softc *miisc; > > LIST_FOREACH(miisc, &mii->mii_phys, mii_list) > mii_phy_reset(miisc); > } > - mii_mediachg(mii); > - return (0); > + error = mii_mediachg(mii); > + return (error); > } > > /* > @@ -915,11 +945,10 @@ > AXE_LOCK_ASSERT(sc, MA_OWNED); > > mii_tick(mii); > - if ((sc->sc_flags & AXE_FLAG_LINK) == 0 > - && mii->mii_media_status & IFM_ACTIVE && > - IFM_SUBTYPE(mii->mii_media_active) != IFM_NONE) { > - sc->sc_flags |= AXE_FLAG_LINK; > - axe_start(ue); > + if ((sc->sc_flags & AXE_FLAG_LINK) == 0) { > + axe_miibus_statchg(ue->ue_dev); > + if ((sc->sc_flags & AXE_FLAG_LINK) != 0) > + axe_start(ue); > } > } > Hiroharu From tamaru at myn.rcast.u-tokyo.ac.jp Thu Feb 12 09:17:37 2009 From: tamaru at myn.rcast.u-tokyo.ac.jp (Hiroharu Tamaru) Date: Thu Feb 12 09:17:44 2009 Subject: USB2: [was: umass not detected correctly, axe not transmitting] AXE problems In-Reply-To: References: <200902110954.37659.hselasky@c2i.net> <200902111657.38129.hselasky@c2i.net> <20090212023723.GA6313@michelle.cdnetworks.co.kr> <20090212034251.GB6313@michelle.cdnetworks.co.kr> <20090212043033.GC6313@michelle.cdnetworks.co.kr> Message-ID: Hi, I'm back with the results. And to make it short, everything works now. Thank you, Hans and Pyun, and all others who looked into this for me. Some notes inline: At Thu, 12 Feb 2009 13:37:51 +0900, Hiroharu Tamaru wrote: > At Thu, 12 Feb 2009 13:30:33 +0900, Pyun YongHyeon wrote: > > [1 ] > > On Thu, Feb 12, 2009 at 12:59:13PM +0900, Hiroharu Tamaru wrote: > > > I've just sent another message before reading this. > > > > > > At Thu, 12 Feb 2009 12:42:51 +0900, Pyun YongHyeon wrote: > > > > On Thu, Feb 12, 2009 at 11:37:23AM +0900, Pyun YongHyeon wrote: > > > > > On Thu, Feb 12, 2009 at 01:51:47AM +0900, Hiroharu Tamaru wrote: > > > > > > > > > > > > At Wed, 11 Feb 2009 16:57:36 +0100, Hans Petter Selasky wrote: > > > > > > > > > > ugen3.3: at usbus3 > > > > > > > > > > axe0: on usbus3 > > > > > > > > > > axe0: PHYADDR 0xe0:0x18 > > > > > > > > > > miibus0: on axe0 > > > > > > > > > > ciphy0: PHY 24 on miibus0 > > > > > > > > > > ciphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, > > > > > > > > > > 1000baseT-FDX, auto ue0: on axe0 > > > > > > > > > > ue0: Ethernet address: 00:90:cc:xx:xx:xx > > > > > > > > > > ue0: link state changed to DOWN > > > > > > > > > > ue0: link state changed to UP > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > Turn on debugging: > > > > > > > > > > > > > > > > > > sysctl hw.usb2.axe.debug=15 > > > > > > > > > > > > > > > > > > And repeat test. > > > > > > > > > > > > > > > > with hw.usb2.axe.debug=15, I have: > > > > > > > > > > > > > > > > ugen3.3: at usbus3 (disconnected) > > > > > > > > pid 3244 (dhclient), uid 65: exited on signal 11 > > > > > > > > ugen3.3: at usbus3 > > > > > > > > axe0: on usbus3 > > > > > > > > axe0: PHYADDR 0xe0:0x18 > > > > > > > > miibus0: on axe0 > > > > > > > > ciphy0: PHY 24 on miibus0 > > > > > > > > ciphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, > > > > > > > > 1000baseT-FDX, auto ue0: on axe0 > > > > > > > > ue0: Ethernet address: 00:90:cc:f7:bc:2e > > > > > > > > ue0: link state changed to DOWN > > > > > > > > ue0: link state changed to UP > > > > > > > > > > > > > > > > > > > > > > > The hardware is a PLANEX GU-1000T ethernet adapter. > > > > > > > > > > > > > > > > > > > > > > > I have the same USB controller and latest CURRENT works. > > > > > > > > > > axe0: on usbus1 > > > > > axe0: PHYADDR 0xe0:0x18 > > > > > miibus2: on axe0 > > > > > ciphy0: PHY 24 on miibus2 > > > > > ciphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 1000baseT-FDX, auto > > > > > ue0: on axe0 > > > > > ue0: Ethernet address: 00:90:cc:ef:b9:f6 > > > > > ue0: link state changed to DOWN > > > > > > > > > > I manually loaded necessary kernel modules as my kernel does not > > > > > have any USB device entries. The only regression since I tried USB2 > > > > > axe(4) was failure of symbol resolving of link_elf in > > > > > usb2_ethernet.ko module. Attached simple patch seems to fix that. > > > > > > > > > > To Hans, > > > > > I think MODULE_DEPEND should come first before any reference to > > > > > the module in usb2_ethernet.c. Since mii_phy_probe live in > > > > > miibus(4) I added it too. > > > > > > > > > > > > > Hans, I managed to track down Hiroharu's issue in axe(4). It seems > > > > Andrew removed link handling code that ensures correct state of > > > > established link in r188412. > > > > I believe we have to revert changes made in axe_cfg_mii_statchg() > > > > and axe_tick(). I have no idea what was happend in P4, you > > > > checked in the link handling code I submitted. > > > > > > Thanks for looking into this. > > > > > > So, can I just be waiting for a patch to test, or a CVS > > > revision of files to revert to? > > > > > > Meanwhile, I'll bring the userland to the latest current, as > > > I mentioned on the other mail. > > > > > > > Ok, try this one after installword. Attached one restores previous > > link handle code. Note, it was just compile tested. > > Thanks, will do. Could take half a day or so building the world and > all on this host, though. > I'll be back with the results. OK, the patch usb2_ethernet.patch2 in <20090212043033.GC6313@michelle.cdnetworks.co.kr> worked, and now the ue0/AXE interface is working fine. Though I have only tested in 100BaseTX/full-duplex mode, ping -f over a 100Mbps switch run without any packet loss (sysctl net.inet.icmp.icmplim=0, of course), and the interface statics shows no errors too: Name Mtu Network Address Ipkts Ierrs Opkts Oerrs Coll ue0 1500 00:90:cc:xx:xx:xx 32634 0 32192 0 0 ue0 1500 192.168.1.0 192.168.1.3 32553 - 32190 - - Also, At Thu, 12 Feb 2009 12:51:00 +0900, Hiroharu Tamaru wrote: > I also have em0/em1 interfaces, and I am switching with ue0 > when I test AXE. > > It turned out that although I 'ifconfig em0 inet delete > down' those unused interfaces, the arp table entries remain. > 'arp -nda' shows 'delete: cannot locate 192.168.1.1' and the > like for every entry in the table, and they are infact not > deleted. Deletion fails both when em0 is up and down. This symptom was solved after I have brought my userland in sync with the kernel. So here I am, with all my USB2 problems solved! Thank you all for this quick assistance! And finally, I'd appreciate if you could send me or the list the 'commit done' message on this ethernet patch and the mountroot delay patch, so that I can mark to forget about patching the kernel as I cvsup it. Thanks. Hiroharu From pyunyh at gmail.com Thu Feb 12 17:55:26 2009 From: pyunyh at gmail.com (Pyun YongHyeon) Date: Thu Feb 12 17:55:33 2009 Subject: USB2: [was: umass not detected correctly, axe not transmitting] AXE problems In-Reply-To: References: <200902110954.37659.hselasky@c2i.net> <200902111657.38129.hselasky@c2i.net> <20090212023723.GA6313@michelle.cdnetworks.co.kr> <20090212034251.GB6313@michelle.cdnetworks.co.kr> <20090212043033.GC6313@michelle.cdnetworks.co.kr> Message-ID: <20090213015812.GA12653@michelle.cdnetworks.co.kr> On Fri, Feb 13, 2009 at 02:17:16AM +0900, Hiroharu Tamaru wrote: > Hi, I'm back with the results. > And to make it short, everything works now. > Thank you, Hans and Pyun, and all others who looked into this for me. > Great! Andrew, would you commit the patch? > Some notes inline: > [...] > OK, the patch usb2_ethernet.patch2 in > <20090212043033.GC6313@michelle.cdnetworks.co.kr> worked, and now the > ue0/AXE interface is working fine. > > Though I have only tested in 100BaseTX/full-duplex mode, > ping -f over a 100Mbps switch run without any packet loss > (sysctl net.inet.icmp.icmplim=0, of course), and the interface > statics shows no errors too: > > Name Mtu Network Address Ipkts Ierrs Opkts Oerrs Coll > ue0 1500 00:90:cc:xx:xx:xx 32634 0 32192 0 0 > ue0 1500 192.168.1.0 192.168.1.3 32553 - 32190 - - > > > Also, > At Thu, 12 Feb 2009 12:51:00 +0900, Hiroharu Tamaru wrote: > > I also have em0/em1 interfaces, and I am switching with ue0 > > when I test AXE. > > > > It turned out that although I 'ifconfig em0 inet delete > > down' those unused interfaces, the arp table entries remain. > > 'arp -nda' shows 'delete: cannot locate 192.168.1.1' and the > > like for every entry in the table, and they are infact not > > deleted. Deletion fails both when em0 is up and down. > > This symptom was solved after I have brought my userland in > sync with the kernel. > > So here I am, with all my USB2 problems solved! > Thank you all for this quick assistance! > > And finally, I'd appreciate if you could send me or the list > the 'commit done' message on this ethernet patch and the > mountroot delay patch, so that I can mark to forget about > patching the kernel as I cvsup it. Thanks. > Will do. Thanks for testing! From bowie at nrik.jp Thu Feb 12 19:33:47 2009 From: bowie at nrik.jp (Noriyoshi Kawano) Date: Thu Feb 12 19:33:53 2009 Subject: USB2 & apcupsd Message-ID: <86y6wbf2nc.wl%bowie@nrik.jp> Hi, I want to use apcupsd under USB2. [dmesg] ugen0.2: at usbus0 uhid0: on usbus0 Symlink: uhid0 -> usb0.2.0.16 1. I recompile apcupsd to use the generic USB drvier. --- /usr/ports/sysutils/apcupsd/Makefile: line 109 ---- CONFIGURE_ARGS+= --enable-usb --with-generic-usb -------------------------------------------------------- 2. I use libmap.conf to make apcupsd use libusb20. --- /etc/libmap.conf ------- [apcupsd] libusb-0.1.so.8 libusb20.so [apctest] libusb-0.1.so.8 libusb20.so [apcaccess] libusb-0.1.so.8 libusb20.so ---------------------------- It seems to work. But ups communication is interrupted repeatedly. [/var/log/message] Feb 13 11:20:33 brain kernel: uhid0: at ushub0, port 1, addr 2 (disconnected) Feb 13 11:20:34 brain kernel: uhid0: on usbus0 Feb 13 11:20:34 brain kernel: Symlink: uhid0 -> usb0.2.0.16 Feb 13 11:20:35 brain apcupsd[5846]: Communications with UPS restored. Feb 13 11:21:41 brain kernel: uhid0: at ushub0, port 1, addr 2 (disconnected) Feb 13 11:21:42 brain kernel: uhid0: on usbus0 Feb 13 11:21:42 brain kernel: Symlink: uhid0 -> usb0.2.0.16 Feb 13 11:21:43 brain apcupsd[5846]: Communications with UPS restored. Of course, it works fine under old usb stack. Any suggestion ? Noriyoshi Kawano From pyunyh at gmail.com Thu Feb 12 19:51:08 2009 From: pyunyh at gmail.com (Pyun YongHyeon) Date: Thu Feb 12 19:51:14 2009 Subject: USB2: [was: umass not detected correctly, axe not transmitting] AXE problems In-Reply-To: <20090213015812.GA12653@michelle.cdnetworks.co.kr> References: <200902111657.38129.hselasky@c2i.net> <20090212023723.GA6313@michelle.cdnetworks.co.kr> <20090212034251.GB6313@michelle.cdnetworks.co.kr> <20090212043033.GC6313@michelle.cdnetworks.co.kr> <20090213015812.GA12653@michelle.cdnetworks.co.kr> Message-ID: <20090213035355.GC12653@michelle.cdnetworks.co.kr> On Fri, Feb 13, 2009 at 10:58:12AM +0900, Pyun YongHyeon wrote: > On Fri, Feb 13, 2009 at 02:17:16AM +0900, Hiroharu Tamaru wrote: [...] > > This symptom was solved after I have brought my userland in > > sync with the kernel. > > > > So here I am, with all my USB2 problems solved! > > Thank you all for this quick assistance! > > > > And finally, I'd appreciate if you could send me or the list > > the 'commit done' message on this ethernet patch and the > > mountroot delay patch, so that I can mark to forget about > > patching the kernel as I cvsup it. Thanks. > > > > Will do. > FYI: Andrew committed the fix, r188553. From hselasky at c2i.net Fri Feb 13 01:58:57 2009 From: hselasky at c2i.net (Hans Petter Selasky) Date: Fri Feb 13 01:59:04 2009 Subject: USB2 & apcupsd In-Reply-To: <86y6wbf2nc.wl%bowie@nrik.jp> References: <86y6wbf2nc.wl%bowie@nrik.jp> Message-ID: <200902131101.22522.hselasky@c2i.net> On Friday 13 February 2009, Noriyoshi Kawano wrote: > Hi, > > I want to use apcupsd under USB2. > > [dmesg] > ugen0.2: at usbus0 > uhid0: rev 1.10/1.06, addr 2> on usbus0 Symlink: uhid0 -> usb0.2.0.16 > > 1. I recompile apcupsd to use the generic USB drvier. > > --- /usr/ports/sysutils/apcupsd/Makefile: line 109 ---- > CONFIGURE_ARGS+= --enable-usb --with-generic-usb > -------------------------------------------------------- > > 2. I use libmap.conf to make apcupsd use libusb20. > > --- /etc/libmap.conf ------- > [apcupsd] > libusb-0.1.so.8 libusb20.so > > [apctest] > libusb-0.1.so.8 libusb20.so > > [apcaccess] > libusb-0.1.so.8 libusb20.so > ---------------------------- > > It seems to work. But ups communication is interrupted repeatedly. > > [/var/log/message] > Feb 13 11:20:33 brain kernel: uhid0: at ushub0, port 1, addr 2 > (disconnected) Feb 13 11:20:34 brain kernel: uhid0: Conversion Uninterruptible Power Supply, class 0/0, rev 1.10/1.06, addr 2> > on usbus0 Feb 13 11:20:34 brain kernel: Symlink: uhid0 -> usb0.2.0.16 > Feb 13 11:20:35 brain apcupsd[5846]: Communications with UPS restored. > Feb 13 11:21:41 brain kernel: uhid0: at ushub0, port 1, addr 2 > (disconnected) Feb 13 11:21:42 brain kernel: uhid0: Conversion Uninterruptible Power Supply, class 0/0, rev 1.10/1.06, addr 2> > on usbus0 Feb 13 11:21:42 brain kernel: Symlink: uhid0 -> usb0.2.0.16 > Feb 13 11:21:43 brain apcupsd[5846]: Communications with UPS restored. > > > Of course, it works fine under old usb stack. > Any suggestion ? Turn on debugging: sysctl hw.usb2.uhid.debug=15 sysctl hw.usb2.uhub.debug=15 And send me dmesg. I see that the interval is relativly long, so it might be problem to trace. --HPS From bowie at nrik.jp Fri Feb 13 18:24:08 2009 From: bowie at nrik.jp (Noriyoshi Kawano) Date: Fri Feb 13 18:24:16 2009 Subject: USB2 & apcupsd In-Reply-To: <200902131101.22522.hselasky@c2i.net> References: <86y6wbf2nc.wl%bowie@nrik.jp> <200902131101.22522.hselasky@c2i.net> Message-ID: <86fxihiwn2.wl%bowie@nrik.jp> At Fri, 13 Feb 2009 11:01:21 +0100, Hans Petter Selasky wrote: > > On Friday 13 February 2009, Noriyoshi Kawano wrote: > > Hi, > > > > I want to use apcupsd under USB2. > > > > [dmesg] > > ugen0.2: at usbus0 > > uhid0: > rev 1.10/1.06, addr 2> on usbus0 Symlink: uhid0 -> usb0.2.0.16 > > > > 1. I recompile apcupsd to use the generic USB drvier. > > > > --- /usr/ports/sysutils/apcupsd/Makefile: line 109 ---- > > CONFIGURE_ARGS+= --enable-usb --with-generic-usb > > -------------------------------------------------------- > > > > 2. I use libmap.conf to make apcupsd use libusb20. > > > > --- /etc/libmap.conf ------- > > [apcupsd] > > libusb-0.1.so.8 libusb20.so > > > > [apctest] > > libusb-0.1.so.8 libusb20.so > > > > [apcaccess] > > libusb-0.1.so.8 libusb20.so > > ---------------------------- > > > > It seems to work. But ups communication is interrupted repeatedly. > > > > [/var/log/message] > > Feb 13 11:20:33 brain kernel: uhid0: at ushub0, port 1, addr 2 > > (disconnected) Feb 13 11:20:34 brain kernel: uhid0: > Conversion Uninterruptible Power Supply, class 0/0, rev 1.10/1.06, addr 2> > > on usbus0 Feb 13 11:20:34 brain kernel: Symlink: uhid0 -> usb0.2.0.16 > > Feb 13 11:20:35 brain apcupsd[5846]: Communications with UPS restored. > > Feb 13 11:21:41 brain kernel: uhid0: at ushub0, port 1, addr 2 > > (disconnected) Feb 13 11:21:42 brain kernel: uhid0: > Conversion Uninterruptible Power Supply, class 0/0, rev 1.10/1.06, addr 2> > > on usbus0 Feb 13 11:21:42 brain kernel: Symlink: uhid0 -> usb0.2.0.16 > > Feb 13 11:21:43 brain apcupsd[5846]: Communications with UPS restored. > > > > > > Of course, it works fine under old usb stack. > > Any suggestion ? > > Turn on debugging: > > sysctl hw.usb2.uhid.debug=15 > sysctl hw.usb2.uhub.debug=15 > > And send me dmesg. > > I see that the interval is relativly long, so it might be problem to trace. > > --HPS Hi, Hans. Thank you. dmesg is below. usb2_needs_explore:1345: usb2_bus_powerd:1516: bus=0xfffffffe402eac90 usb2_bus_powerd:1599: Recomputing power masks uhub_explore:522: udev=0xfffffffe4057f000 addr=1 uhub_read_port_status:259: port 1, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 2, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 3, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 4, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 5, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 6, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 7, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 8, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION usb2_needs_explore:1345: usb2_bus_powerd:1516: bus=0xfffffffe402c6db0 usb2_bus_powerd:1599: Recomputing power masks uhub_explore:522: udev=0xfffffffe40577000 addr=1 usb2_needs_exploure:1345: hub_read_port_status:259: port 1, wPortStatus=0x0303, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION usb2_bus_powerd:1516: bus=0xfffffffe402cfdb0 usb2_bus_powerd:1599: Recomputing power masks uhub_explore:522: udev=0xfffffffe40579000 addr=1 uhub_read_port_status:259: port 2, wPortStatus=0x0100, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 1, wPortStatus=0x0100, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 2, wPortStatus=0x0100, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION usb2_needs_explore:1345: usb2_bus_powerd:1516: bus=0xfffffffe402d8db0 usb2_bus_powerd:1599: Recomputing power masks uhub_explore:522: udev=0xfffffffe4057b000 addr=1 uhub_read_port_status:259: port 1, wPortStatus=0x0100, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 2, wPortStatus=0x0100, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION usb2_needs_explore:1345: usb2_bus_powerd:1516: bus=0xfffffffe402e1db0 usb2_bus_powerd:1599: Recomputing power masks uhub_explore:522: udev=0xfffffffe4057d000 addr=1 uhub_read_port_status:259: port 1, wPortStatus=0x0103, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 2, wPortStatus=0x0100, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION usb2_needs_explore:1345: usb2_bus_powerd:1516: bus=0xfffffffe402eac90 usb2_bus_powerd:1599: Recomputing power masks uhub_explore:522: udev=0xfffffffe4057f000 addr=1 uhub_read_port_status:259: port 1, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 2, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 3, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 4, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 5, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 6, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 7, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 8, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION usb2_needs_explore:1345: usb2_bus_powerd:1516: bus=0xfffffffe402c6db0 usb2_bus_powerd:1599: Recomputing power masks uhub_explore:522: udev=0xfffffffe40577000 adusb2_needsd_explore:1345: r=1 usb2_bus_powerd:1516: bus=0xfffffffe402cfdb0 usb2_bus_powerd:1599: Recomputing power masks uhub_explore:522: udev=0xfffffffe40579000 addr=1 uhub_read_port_status:259: port 1, wPortStatus=0x0303, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 1, wPortStatus=0x0100, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 2, wPortStatus=0x0100, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 2, wPortStatus=0x0100, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION usb2_needs_explore:1345: usb2_bus_powerd:1516: bus=0xfffffffe402d8db0 usb2_bus_powerd:1599: Recomputing power masks uhub_explore:522: udev=0xfffffffe4057b000 addr=1 uhub_read_port_status:259: port 1, wPortStatus=0x0100, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 2, wPortStatus=0x0100, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION usb2_needs_explore:1345: usb2_bus_powerd:1516: bus=0xfffffffe402e1db0 usb2_bus_powerd:1599: Recomputing power masks uhub_explore:522: udev=0xfffffffe4057d000 addr=1 uhub_read_port_status:259: port 1, wPortStatus=0x0103, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 2, wPortStatus=0x0100, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION usb2_needs_explore:1345: usb2_bus_powerd:1516: bus=0xfffffffe402eac90 usb2_bus_powerd:1599: Recomputing power masks uhub_explore:522: udev=0xfffffffe4057f000 addr=1 uhub_read_port_status:259: port 1, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 2, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 3, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 4, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 5, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 6, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 7, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 8, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION usb2_needs_explore:1345: usb2_bus_powerd:1516: bus=0xfffffffe402c6db0 usb2_bus_powerd:1599: Recomputing power masks uhub_explore:522: udev=0xfffffffe40577000 addr=1 usb2_neeuds_exphlore:1345: ub_read_port_status:259: port 1, wPortStatus=0x0303, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION usb2_bus_powerd:1516: bus=0xfffffffe402cfdb0 usb2_bus_powerd:1599: Recomputing power masks uhub_explore:522: udev=0xfffffffe40579000 addr=1 uhub_read_port_status:259: port 2, wPortStatus=0x0100, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 1, wPortStatus=0x0100, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 2, wPortStatus=0x0100, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION usb2_needs_explore:1345: usb2_bus_powerd:1516: bus=0xfffffffe402d8db0 usb2_bus_powerd:1599: Recomputing power masks uhub_explore:522: udev=0xfffffffe4057b000 addr=1 uhub_read_port_status:259: port 1, wPortStatus=0x0100, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 2, wPortStatus=0x0100, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION usb2_needs_explore:1345: usb2_bus_powerd:1516: bus=0xfffffffe402e1db0 usb2_bus_powerd:1599: Recomputing power masks uhub_explore:522: udev=0xfffffffe4057d000 addr=1 uhub_read_port_status:259: port 1, wPortStatus=0x0103, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 2, wPortStatus=0x0100, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION usb2_needs_explore:1345: usb2_bus_powerd:1516: bus=0xfffffffe402eac90 usb2_bus_powerd:1599: Recomputing power masks uhub_explore:522: udev=0xfffffffe4057f000 addr=1 uhub_read_port_status:259: port 1, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 2, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 3, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 4, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 5, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 6, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 7, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 8, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION usb2_needs_explore:1345: usb2_bus_powerd:1516: bus=0xfffffffe402c6db0 usb2_bus_powerd:1599: Recomputing power masks uhub_explore:522: udev=0xfffffffe40577000 addr=1 uuhub_read_port_status:259: port 1, wPortStatus=0x030s3, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETbION 2_needs_uexplore:1345: hub_read_port_status:259: port 2, wPortStatus=0x0100, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION usb2_bus_powerd:1516: bus=0xfffffffe402cfdb0 usb2_bus_powerd:1599: Recomputing power masks uhub_explore:522: udev=0xfffffffe40579000 addr=1 uhub_read_port_status:259: port 1, wPortStatus=0x0100, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 2, wPortStatus=0x0100, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION usb2_needs_explore:1345: usb2_bus_powerd:1516: bus=0xfffffffe402d8db0 usb2_bus_powerd:1599: Recomputing power masks uhub_explore:522: udev=0xfffffffe4057b000 addr=1 uhub_read_port_status:259: port 1, wPortStatus=0x0100, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 2, wPortStatus=0x0100, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION usb2_needs_explore:1345: usb2_bus_powerd:1516: bus=0xfffffffe402e1db0 usb2_bus_powerd:1599: Recomputing power masks uhub_explore:522: udev=0xfffffffe4057d000 addr=1 uhub_read_port_status:259: port 1, wPortStatus=0x0103, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 2, wPortStatus=0x0100, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION usb2_needs_explore:1345: usb2_bus_powerd:1516: bus=0xfffffffe402eac90 usb2_bus_powerd:1599: Recomputing power masks uhub_explore:522: udev=0xfffffffe4057f000 addr=1 uhub_read_port_status:259: port 1, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 2, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 3, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 4, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 5, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 6, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 7, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 8, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION usb2_needs_explore:1345: usb2_bus_powerd:1516: bus=0xfffffffe402c6db0 usb2_bus_powerd:1599: Recomputing power masks uhub_explore:522: udev=0xfffffffe40577000 adusb2_needs_explore:1345: dr=1 usb2_bus_powerd:1516: bus=0xfffffffe402cfdb0 usb2_bus_powerd:1599: Recomputing power masks uhub_explore:522: udev=0xfffffffe40579000 addr=1 uhub_read_port_status:259: port 1, wPortStatus=0x0303, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 1, wPortStatus=0x0100, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 2, wPortStatus=0x0100, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 2, wPortStatus=0x0100, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION usb2_needs_explore:1345: usb2_bus_powerd:1516: bus=0xfffffffe402d8db0 usb2_bus_powerd:1599: Recomputing power masks uhub_explore:522: udev=0xfffffffe4057b000 addr=1 uhub_read_port_status:259: port 1, wPortStatus=0x0100, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 2, wPortStatus=0x0100, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION usb2_needs_explore:1345: usb2_bus_powerd:1516: bus=0xfffffffe402e1db0 usb2_bus_powerd:1599: Recomputing power masks uhub_explore:522: udev=0xfffffffe4057d000 addr=1 uhub_read_port_status:259: port 1, wPortStatus=0x0103, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 2, wPortStatus=0x0100, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION usb2_needs_explore:1345: usb2_bus_powerd:1516: bus=0xfffffffe402eac90 usb2_bus_powerd:1599: Recomputing power masks uhub_explore:522: udev=0xfffffffe4057f000 addr=1 uhub_read_port_status:259: port 1, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 2, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 3, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 4, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 5, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 6, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 7, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 8, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION usb2_needs_explore:1345: usb2_bus_powerd:1516: bus=0xfffffffe402c6db0 usb2_bus_powerd:1599: Recomputing power masks uhub_explore:522: udev=0xfffffffe40577000 addr=1 uuhub_read_port_status:259: port 1, wPortStatus=0x030s3, wPortChange=0bx0000, err=USB_ERR_NORMAL_COMPLETI2ON _nueedsh_explore:1345: ub_read_port_status:259: port 2, wPortStatus=0x0100, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION usb2_bus_powerd:1516: bus=0xfffffffe402cfdb0 usb2_bus_powerd:1599: Recomputing power masks uhub_explore:522: udev=0xfffffffe40579000 addr=1 uhub_read_port_status:259: port 1, wPortStatus=0x0100, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 2, wPortStatus=0x0100, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION usb2_needs_explore:1345: usb2_bus_powerd:1516: bus=0xfffffffe402d8db0 usb2_bus_powerd:1599: Recomputing power masks uhub_explore:522: udev=0xfffffffe4057b000 addr=1 uhub_read_port_status:259: port 1, wPortStatus=0x0100, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 2, wPortStatus=0x0100, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION usb2_needs_explore:1345: usb2_bus_powerd:1516: bus=0xfffffffe402e1db0 usb2_bus_powerd:1599: Recomputing power masks uhub_explore:522: udev=0xfffffffe4057d000 addr=1 uhub_read_port_status:259: port 1, wPortStatus=0x0103, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 2, wPortStatus=0x0100, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION usb2_needs_explore:1345: usb2_bus_powerd:1516: bus=0xfffffffe402eac90 usb2_bus_powerd:1599: Recomputing power masks uhub_explore:522: udev=0xfffffffe4057f000 addr=1 uhub_read_port_status:259: port 1, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 2, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 3, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 4, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 5, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 6, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 7, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 8, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION usb2_needs_explore:1345: usb2_bus_powerd:1516: bus=0xfffffffe402c6db0 usb2_bus_powerd:1599: Recomputing power masks uhub_explore:522: udev=0xfffffffe40577000 addr=1 usuhub_read_port_status:259: port 1, wPorbtSt2atus=0x0303, wPortChange=0x0000, err=USB_ERR__NORMAL_COMPLETION nuhub_read_port_statues:259:e port 2, wPortStatus=0x0100, wPortChadnge=s0x0000, err=USB_ERR_NORMAL_COMPLE_TION explore:1345: usb2_bus_powerd:1516: bus=0xfffffffe402cfdb0 usb2_bus_powerd:1599: Recomputing power masks uhub_explore:522: udev=0xfffffffe40579000 addr=1 uhub_read_port_status:259: port 1, wPortStatus=0x0100, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 2, wPortStatus=0x0100, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION usb2_needs_explore:1345: usb2_bus_powerd:1516: bus=0xfffffffe402d8db0 usb2_bus_powerd:1599: Recomputing power masks uhub_explore:522: udev=0xfffffffe4057b000 addr=1 uhub_read_port_status:259: port 1, wPortStatus=0x0100, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 2, wPortStatus=0x0100, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION usb2_needs_explore:1345: usb2_bus_powerd:1516: bus=0xfffffffe402e1db0 usb2_bus_powerd:1599: Recomputing power masks uhub_explore:522: udev=0xfffffffe4057d000 addr=1 uhub_read_port_status:259: port 1, wPortStatus=0x0103, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 2, wPortStatus=0x0100, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION usb2_needs_explore:1345: usb2_bus_powerd:1516: bus=0xfffffffe402eac90 usb2_bus_powerd:1599: Recomputing power masks uhub_explore:522: udev=0xfffffffe4057f000 addr=1 uhub_read_port_status:259: port 1, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 2, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 3, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 4, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 5, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 6, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 7, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 8, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION usb2_needs_explore:1345: usb2_bus_powerd:1516: bus=0xfffffffe402c6db0 usb2_bus_powerd:1599: Recomputing power masks uhub_explore:522: udev=0xfffffffe40577000 addr=1 usb2_needs_explore:1345: uhub_read_port_status:259: port 1, wPortStatus=0x0303, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION usb2_bus_powerd:1516: bus=0xfffffffe402cfdb0 usb2_bus_powerd:1599: Recomputing power masks uhub_explore:522: udev=0xfffffffe40579000 addr=1 uhub_read_port_status:259: port 2, wPortStatus=0x0100, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 1, wPortStatus=0x0100, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 2, wPortStatus=0x0100, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION usb2_needs_explore:1345: usb2_bus_powerd:1516: bus=0xfffffffe402d8db0 usb2_bus_powerd:1599: Recomputing power masks uhub_explore:522: udev=0xfffffffe4057b000 addr=1 uhub_read_port_status:259: port 1, wPortStatus=0x0100, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 2, wPortStatus=0x0100, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION usb2_needs_explore:1345: usb2_bus_powerd:1516: bus=0xfffffffe402e1db0 usb2_bus_powerd:1599: Recomputing power masks uhub_explore:522: udev=0xfffffffe4057d000 addr=1 uhub_read_port_status:259: port 1, wPortStatus=0x0103, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 2, wPortStatus=0x0100, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION usb2_needs_explore:1345: usb2_bus_powerd:1516: bus=0xfffffffe402eac90 usb2_bus_powerd:1599: Recomputing power masks uhub_explore:522: udev=0xfffffffe4057f000 addr=1 uhub_read_port_status:259: port 1, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 2, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 3, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 4, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 5, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 6, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 7, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 8, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION usb2_needs_explore:1345: usb2_bus_powerd:1516: bus=0xfffffffe402c6db0 usb2_bus_powerd:1599: Recomputing power masks uhub_explore:522: udev=0xfffffffe40577000 adusb2_needds_explore:1345: r=1 usb2_bus_powerd:1516: bus=0xfffffffe402cfdb0 usb2_bus_powerd:1599: Recomputing power masks uhub_explore:522: udev=0xfffffffe40579000 addr=1 uhub_read_port_status:259: port 1, wPortStatus=0x0303, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 1, wPortStatus=0x0100, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 2, wPortStatus=0x0100, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 2, wPortStatus=0x0100, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION usb2_needs_explore:1345: usb2_bus_powerd:1516: bus=0xfffffffe402d8db0 usb2_bus_powerd:1599: Recomputing power masks uhub_explore:522: udev=0xfffffffe4057b000 addr=1 uhub_read_port_status:259: port 1, wPortStatus=0x0100, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 2, wPortStatus=0x0100, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION usb2_needs_explore:1345: usb2_bus_powerd:1516: bus=0xfffffffe402e1db0 usb2_bus_powerd:1599: Recomputing power masks uhub_explore:522: udev=0xfffffffe4057d000 addr=1 uhub_read_port_status:259: port 1, wPortStatus=0x0103, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 2, wPortStatus=0x0100, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION usb2_needs_explore:1345: usb2_bus_powerd:1516: bus=0xfffffffe402eac90 usb2_bus_powerd:1599: Recomputing power masks uhub_explore:522: udev=0xfffffffe4057f000 addr=1 uhub_read_port_status:259: port 1, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 2, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 3, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 4, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 5, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 6, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 7, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 8, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION usb2_needs_explore:1345: usb2_bus_powerd:1516: bus=0xfffffffe402c6db0 usb2_bus_powerd:1599: Recomputing power masks uhub_explore:522: udev=0xfffffffe40577000 adusb2_needs_dexplore:1345: r=1 usb2_bus_powerd:1516: bus=0xfffffffe402cfdb0 usb2_bus_powerd:1599: Recomputing power masks uhub_explore:522: udev=0xfffffffe40579000 addr=1 uhub_read_port_status:259: port 1, wPortStatus=0x0303, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 1, wPortStatus=0x0100, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 2, wPortStatus=0x0100, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 2, wPortStatus=0x0100, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION usb2_needs_explore:1345: usb2_bus_powerd:1516: bus=0xfffffffe402d8db0 usb2_bus_powerd:1599: Recomputing power masks uhub_explore:522: udev=0xfffffffe4057b000 addr=1 uhub_read_port_status:259: port 1, wPortStatus=0x0100, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 2, wPortStatus=0x0100, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION usb2_needs_explore:1345: usb2_bus_powerd:1516: bus=0xfffffffe402e1db0 usb2_bus_powerd:1599: Recomputing power masks uhub_explore:522: udev=0xfffffffe4057d000 addr=1 uhub_read_port_status:259: port 1, wPortStatus=0x0103, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 2, wPortStatus=0x0100, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION usb2_needs_explore:1345: usb2_bus_powerd:1516: bus=0xfffffffe402eac90 usb2_bus_powerd:1599: Recomputing power masks uhub_explore:522: udev=0xfffffffe4057f000 addr=1 uhub_read_port_status:259: port 1, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 2, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 3, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 4, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 5, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 6, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 7, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 8, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION usb2_needs_explore:1345: usb2_bus_powerd:1516: bus=0xfffffffe402c6db0 usb2_bus_powerd:1599: Recomputing power masks uhub_explore:522: udev=0xfffffffe40577000 addr=1 uuhub_read_port_status:259: port 1, wPortStatus=0x0s303, wPortChange=0x0000, erbr=USB_ERR_NORMAL_COMPLETION 2_uhub_read_port_status:259: port 2, wPortStatus=0x0100, wPortChannge=0x0000, err=USB_ERR_NORMAL_COMPLETION eeds_explore:1345: usb2_bus_powerd:1516: bus=0xfffffffe402cfdb0 usb2_bus_powerd:1599: Recomputing power masks uhub_explore:522: udev=0xfffffffe40579000 addr=1 uhub_read_port_status:259: port 1, wPortStatus=0x0100, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 2, wPortStatus=0x0100, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION usb2_needs_explore:1345: usb2_bus_powerd:1516: bus=0xfffffffe402d8db0 usb2_bus_powerd:1599: Recomputing power masks uhub_explore:522: udev=0xfffffffe4057b000 addr=1 uhub_read_port_status:259: port 1, wPortStatus=0x0100, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 2, wPortStatus=0x0100, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION usb2_needs_explore:1345: usb2_bus_powerd:1516: bus=0xfffffffe402e1db0 usb2_bus_powerd:1599: Recomputing power masks uhub_explore:522: udev=0xfffffffe4057d000 addr=1 uhub_read_port_status:259: port 1, wPortStatus=0x0103, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 2, wPortStatus=0x0100, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION usb2_needs_explore:1345: usb2_bus_powerd:1516: bus=0xfffffffe402eac90 usb2_bus_powerd:1599: Recomputing power masks uhub_explore:522: udev=0xfffffffe4057f000 addr=1 uhub_read_port_status:259: port 1, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 2, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 3, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 4, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 5, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 6, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 7, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 8, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION usb2_needs_explore:1345: usb2_bus_powerd:1516: bus=0xfffffffe402c6db0 usb2_bus_powerd:1599: Recomputing power masks uhub_explore:522: udev=0xfffffffe40577000 adusb2_needds_explrore:1345: =1 usb2_bus_powerd:1516: bus=0xfffffffe402cfdb0 usb2_bus_powerd:1599: Recomputing power masks uhub_explore:522: udev=0xfffffffe40579000 addr=1 uhub_read_port_status:259: port 1, wPortStatus=0x0303, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 1, wPortStatus=0x0100, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 2, wPortStatus=0x0100, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 2, wPortStatus=0x0100, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION usb2_needs_explore:1345: usb2_bus_powerd:1516: bus=0xfffffffe402d8db0 usb2_bus_powerd:1599: Recomputing power masks uhub_explore:522: udev=0xfffffffe4057b000 addr=1 uhub_read_port_status:259: port 1, wPortStatus=0x0100, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 2, wPortStatus=0x0100, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION usb2_needs_explore:1345: usb2_bus_powerd:1516: bus=0xfffffffe402e1db0 usb2_bus_powerd:1599: Recomputing power masks uhub_explore:522: udev=0xfffffffe4057d000 addr=1 uhub_read_port_status:259: port 1, wPortStatus=0x0103, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 2, wPortStatus=0x0100, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION usb2_needs_explore:1345: usb2_bus_powerd:1516: bus=0xfffffffe402eac90 usb2_bus_powerd:1599: Recomputing power masks uhub_explore:522: udev=0xfffffffe4057f000 addr=1 uhub_read_port_status:259: port 1, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 2, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 3, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 4, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 5, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 6, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 7, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 8, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION usb2_needs_explore:1345: usb2_bus_powerd:1516: bus=0xfffffffe402c6db0 usb2_bus_powerd:1599: Recomputing power masks uhub_explore:522: udev=0xfffffffe40577000 addr=1 uuhub_read_port_status:259: port 1, wPorstStatus=0x0303, wPbo2rtChange=0x0000_, err=USB_ERR_NORMAL_COMPLETION nuhub_read_port_status:25e9: port 2, wPortStatus=0x0e100, wPortChange=0x0000, err=USB_ERR_NdORMAsL_COMPLET_ION explore:1345: usb2_bus_powerd:1516: bus=0xfffffffe402cfdb0 usb2_bus_powerd:1599: Recomputing power masks uhub_explore:522: udev=0xfffffffe40579000 addr=1 uhub_read_port_status:259: port 1, wPortStatus=0x0100, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 2, wPortStatus=0x0100, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION usb2_needs_explore:1345: usb2_bus_powerd:1516: bus=0xfffffffe402d8db0 usb2_bus_powerd:1599: Recomputing power masks uhub_explore:522: udev=0xfffffffe4057b000 addr=1 uhub_read_port_status:259: port 1, wPortStatus=0x0100, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 2, wPortStatus=0x0100, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION usb2_needs_explore:1345: usb2_bus_powerd:1516: bus=0xfffffffe402e1db0 usb2_bus_powerd:1599: Recomputing power masks uhub_explore:522: udev=0xfffffffe4057d000 addr=1 uhub_read_port_status:259: port 1, wPortStatus=0x0103, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 2, wPortStatus=0x0100, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION usb2_needs_explore:1345: usb2_bus_powerd:1516: bus=0xfffffffe402eac90 usb2_bus_powerd:1599: Recomputing power masks uhub_explore:522: udev=0xfffffffe4057f000 addr=1 uhub_read_port_status:259: port 1, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 2, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 3, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 4, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 5, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 6, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 7, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 8, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION usb2_needs_explore:1345: usb2_bus_powerd:1516: bus=0xfffffffe402c6db0 usb2_bus_powerd:1599: Recomputing power masks uhub_explore:522: udev=0xfffffffe40577000 addr=1 usb2_needs_explore:1345:u hub_read_port_status:259: port 1, wPortStatus=0x0303, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION usb2_bus_powerd:1516: bus=0xfffffffe402cfdb0 usb2_bus_powerd:1599: Recomputing power masks uhub_explore:522: udev=0xfffffffe40579000 addr=1 uhub_read_port_status:259: port 2, wPortStatus=0x0100, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 1, wPortStatus=0x0100, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 2, wPortStatus=0x0100, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION usb2_needs_explore:1345: usb2_bus_powerd:1516: bus=0xfffffffe402d8db0 usb2_bus_powerd:1599: Recomputing power masks uhub_explore:522: udev=0xfffffffe4057b000 addr=1 uhub_read_port_status:259: port 1, wPortStatus=0x0100, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 2, wPortStatus=0x0100, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION usb2_needs_explore:1345: usb2_bus_powerd:1516: bus=0xfffffffe402e1db0 usb2_bus_powerd:1599: Recomputing power masks uhub_explore:522: udev=0xfffffffe4057d000 addr=1 uhub_read_port_status:259: port 1, wPortStatus=0x0103, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 2, wPortStatus=0x0100, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION usb2_needs_explore:1345: usb2_bus_powerd:1516: bus=0xfffffffe402eac90 usb2_bus_powerd:1599: Recomputing power masks uhub_explore:522: udev=0xfffffffe4057f000 addr=1 uhub_read_port_status:259: port 1, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 2, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 3, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 4, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 5, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 6, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 7, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 8, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION usb2_needs_explore:1345: usb2_bus_powerd:1516: bus=0xfffffffe402c6db0 usb2_bus_powerd:1599: Recomputing power masks uhub_explore:522: udev=0xfffffffe40577000 adusb2_needs_explodrre:1345: =1 usb2_bus_powerd:1516: bus=0xfffffffe402cfdb0 usb2_bus_powerd:1599: Recomputing power masks uhub_explore:522: udev=0xfffffffe40579000 addr=1 uhub_read_port_status:259: port 1, wPortStatus=0x0303, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 1, wPortStatus=0x0100, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 2, wPortStatus=0x0100, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 2, wPortStatus=0x0100, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION usb2_needs_explore:1345: usb2_bus_powerd:1516: bus=0xfffffffe402d8db0 usb2_bus_powerd:1599: Recomputing power masks uhub_explore:522: udev=0xfffffffe4057b000 addr=1 uhub_read_port_status:259: port 1, wPortStatus=0x0100, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 2, wPortStatus=0x0100, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION usb2_needs_explore:1345: usb2_bus_powerd:1516: bus=0xfffffffe402e1db0 usb2_bus_powerd:1599: Recomputing power masks uhub_explore:522: udev=0xfffffffe4057d000 addr=1 uhub_read_port_status:259: port 1, wPortStatus=0x0103, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 2, wPortStatus=0x0100, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION usb2_needs_explore:1345: usb2_bus_powerd:1516: bus=0xfffffffe402eac90 usb2_bus_powerd:1599: Recomputing power masks uhub_explore:522: udev=0xfffffffe4057f000 addr=1 uhub_read_port_status:259: port 1, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 2, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 3, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 4, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 5, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 6, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 7, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 8, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION usb2_needs_explore:1345: usb2_bus_powerd:1516: bus=0xfffffffe402c6db0 usb2_bus_powerd:1599: Recomputing power masks uhub_explore:522: udev=0xfffffffe40577000 adusb2_needs_explore:1345: dr=1 usb2_bus_powerd:1516: bus=0xfffffffe402cfdb0 usb2_bus_powerd:1599: Recomputing power masks uhub_explore:522: udev=0xfffffffe40579000 addr=1 uhub_read_port_status:259: port 1, wPortStatus=0x0303, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 1, wPortStatus=0x0100, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 2, wPortStatus=0x0100, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 2, wPortStatus=0x0100, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION usb2_needs_explore:1345: usb2_bus_powerd:1516: bus=0xfffffffe402d8db0 usb2_bus_powerd:1599: Recomputing power masks uhub_explore:522: udev=0xfffffffe4057b000 addr=1 uhub_read_port_status:259: port 1, wPortStatus=0x0100, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 2, wPortStatus=0x0100, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION usb2_needs_explore:1345: usb2_bus_powerd:1516: bus=0xfffffffe402e1db0 usb2_bus_powerd:1599: Recomputing power masks uhub_explore:522: udev=0xfffffffe4057d000 addr=1 uhub_read_port_status:259: port 1, wPortStatus=0x0103, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 2, wPortStatus=0x0100, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION usb2_needs_explore:1345: usb2_bus_powerd:1516: bus=0xfffffffe402eac90 usb2_bus_powerd:1599: Recomputing power masks uhub_explore:522: udev=0xfffffffe4057f000 addr=1 uhub_read_port_status:259: port 1, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 2, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 3, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 4, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 5, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 6, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 7, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 8, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION usb2_needs_explore:1345: usb2_bus_powerd:1516: bus=0xfffffffe402c6db0 usb2_bus_powerd:1599: Recomputing power masks uhub_explore:522: udev=0xfffffffe40577000 addr=1 usb2_needsu_explore:134h5: ub_read_port_status:259: port 1, wPortStatus=0x0303, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION usb2_bus_powerd:1516: bus=0xfffffffe402cfdb0 usb2_bus_powerd:1599: Recomputing power masks uhub_explore:522: udev=0xfffffffe40579000 addr=1 uhub_read_port_status:259: port 2, wPortStatus=0x0100, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 1, wPortStatus=0x0100, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 2, wPortStatus=0x0100, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETIOusb2_neNeds_explore:1345: usb2_bus_powerd:1516: bus=0xfffffffe402d8db0 usb2_bus_powerd:1599: Recomputing power masks uhub_explore:522: udev=0xfffffffe4057b000 addr=1 uhub_read_port_status:259: port 1, wPortStatus=0x0100, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 2, wPortStatus=0x0100, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION usb2_needs_explore:1345: usb2_bus_powerd:1516: bus=0xfffffffe402e1db0 usb2_bus_powerd:1599: Recomputing power masks uhub_explore:522: udev=0xfffffffe4057d000 addr=1 uhub_read_port_status:259: port 1, wPortStatus=0x0103, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 2, wPortStatus=0x0100, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION usb2_needs_explore:1345: usb2_bus_powerd:1516: bus=0xfffffffe402eac90 usb2_bus_powerd:1599: Recomputing power masks uhub_explore:522: udev=0xfffffffe4057f000 addr=1 uhub_read_port_status:259: port 1, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 2, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 3, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 4, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 5, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 6, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 7, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 8, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION usb2_needs_explore:1345: usb2_bus_powerd:1516: bus=0xfffffffe402c6db0 usb2_bus_powerd:1599: Recomputing power masks uhub_explore:522: udev=0xfffffffe40577000 addr=1 uuhub_read_port_statsus:259: pbort 1, wPortStatus=0x0303, wPortC2hange=0x0000, _err=USB_ERR_NORMAL_COMPLETION neuhub_read_port_status:259: poret 2, wPortStatus=0x0100, wPortChange=0x0000, err=USB_ERRd_NORMAL_COMPLETION s_explore:1345: usb2_bus_powerd:1516: bus=0xfffffffe402cfdb0 usb2_bus_powerd:1599: Recomputing power masks uhub_explore:522: udev=0xfffffffe40579000 addr=1 uhub_read_port_status:259: port 1, wPortStatus=0x0100, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 2, wPortStatus=0x0100, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION usb2_needs_explore:1345: usb2_bus_powerd:1516: bus=0xfffffffe402d8db0 usb2_bus_powerd:1599: Recomputing power masks uhub_explore:522: udev=0xfffffffe4057b000 addr=1 uhub_read_port_status:259: port 1, wPortStatus=0x0100, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 2, wPortStatus=0x0100, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION usb2_needs_explore:1345: usb2_bus_powerd:1516: bus=0xfffffffe402e1db0 usb2_bus_powerd:1599: Recomputing power masks uhub_explore:522: udev=0xfffffffe4057d000 addr=1 uhub_read_port_status:259: port 1, wPortStatus=0x0103, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 2, wPortStatus=0x0100, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION usb2_needs_explore:1345: usb2_bus_powerd:1516: bus=0xfffffffe402eac90 usb2_bus_powerd:1599: Recomputing power masks uhub_explore:522: udev=0xfffffffe4057f000 addr=1 uhub_read_port_status:259: port 1, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 2, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 3, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 4, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 5, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 6, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 7, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 8, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION usb2_needs_explore:1345: usb2_bus_powerd:1516: bus=0xfffffffe402c6db0 usb2_bus_powerd:1599: Recomputing power masks uhub_explore:522: udev=0xfffffffe40577000 addr=1 usuhub_read_port_status:259: port 1, wPortStatus=0x0303, wPortChange=0x0000, err=USB_ERR_NORMAbL_COMPLETION 2uhub_read_port_st_atus:259: port 2, wPonrtSteatus=0x0100, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION eds_explore:1345: usb2_bus_powerd:1516: bus=0xfffffffe402cfdb0 usb2_bus_powerd:1599: Recomputing power masks uhub_explore:522: udev=0xfffffffe40579000 addr=1 uhub_read_port_status:259: port 1, wPortStatus=0x0100, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 2, wPortStatus=0x0100, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION usb2_needs_explore:1345: usb2_bus_powerd:1516: bus=0xfffffffe402d8db0 usb2_bus_powerd:1599: Recomputing power masks uhub_explore:522: udev=0xfffffffe4057b000 addr=1 uhub_read_port_status:259: port 1, wPortStatus=0x0100, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 2, wPortStatus=0x0100, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION usb2_needs_explore:1345: usb2_bus_powerd:1516: bus=0xfffffffe402e1db0 usb2_bus_powerd:1599: Recomputing power masks uhub_explore:522: udev=0xfffffffe4057d000 addr=1 uhub_read_port_status:259: port 1, wPortStatus=0x0103, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 2, wPortStatus=0x0100, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION usb2_needs_explore:1345: usb2_bus_powerd:1516: bus=0xfffffffe402eac90 usb2_bus_powerd:1599: Recomputing power masks uhub_explore:522: udev=0xfffffffe4057f000 addr=1 uhub_read_port_status:259: port 1, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 2, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 3, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 4, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 5, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 6, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 7, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 8, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION usb2_needs_explore:1345: usb2_bus_powerd:1516: bus=0xfffffffe402c6db0 usb2_bus_powerd:1599: Recomputing power masks uhub_explore:522: udev=0xfffffffe40577000 addr=1 uuhub_read_port_statsus:259: bport 1, wP2ortStatus=0x0303, wP_ortChange=0x0000, enrr=USB_ERR_NORMAL_COMPLETION euhub_read_port_status:259: port 2, wPortStatus=0x0100, wPortChange=0x0000, err=USB_ERR_eNORMAL_COMPLETION ds_explore:1345: usb2_bus_powerd:1516: bus=0xfffffffe402cfdb0 usb2_bus_powerd:1599: Recomputing power masks uhub_explore:522: udev=0xfffffffe40579000 addr=1 uhub_read_port_status:259: port 1, wPortStatus=0x0100, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 2, wPortStatus=0x0100, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION usb2_needs_explore:1345: usb2_bus_powerd:1516: bus=0xfffffffe402d8db0 usb2_bus_powerd:1599: Recomputing power masks uhub_explore:522: udev=0xfffffffe4057b000 addr=1 uhub_read_port_status:259: port 1, wPortStatus=0x0100, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 2, wPortStatus=0x0100, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION usb2_needs_explore:1345: usb2_bus_powerd:1516: bus=0xfffffffe402e1db0 usb2_bus_powerd:1599: Recomputing power masks uhub_explore:522: udev=0xfffffffe4057d000 addr=1 uhub_read_port_status:259: port 1, wPortStatus=0x0103, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 2, wPortStatus=0x0100, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION usb2_needs_explore:1345: usb2_bus_powerd:1516: bus=0xfffffffe402eac90 usb2_bus_powerd:1599: Recomputing power masks uhub_explore:522: udev=0xfffffffe4057f000 addr=1 uhub_read_port_status:259: port 1, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 2, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 3, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 4, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 5, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 6, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 7, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 8, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION usb2_needs_explore:1345: usb2_bus_powerd:1516: bus=0xfffffffe402c6db0 usb2_bus_powerd:1599: Recomputing power masks uhub_explore:522: udev=0xfffffffe40577000 addr=1 usb2_needs_explore:1345: uhub_read_port_status:259: port 1, wPortStatus=0x0303, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION usb2_bus_powerd:1516: bus=0xfffffffe402cfdb0 usb2_bus_powerd:1599: Recomputing power masks uhub_explore:522: udev=0xfffffffe40579000 addr=1 uhub_read_port_status:259: port 2, wPortStatus=0x0100, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 1, wPortStatus=0x0100, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 2, wPortStatus=0x0100, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION usb2_needs_explore:1345: usb2_bus_powerd:1516: bus=0xfffffffe402d8db0 usb2_bus_powerd:1599: Recomputing power masks uhub_explore:522: udev=0xfffffffe4057b000 addr=1 uhub_read_port_status:259: port 1, wPortStatus=0x0100, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 2, wPortStatus=0x0100, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION usb2_needs_explore:1345: usb2_bus_powerd:1516: bus=0xfffffffe402e1db0 usb2_bus_powerd:1599: Recomputing power masks uhub_explore:522: udev=0xfffffffe4057d000 addr=1 uhub_read_port_status:259: port 1, wPortStatus=0x0103, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 2, wPortStatus=0x0100, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION usb2_needs_explore:1345: usb2_bus_powerd:1516: bus=0xfffffffe402eac90 usb2_bus_powerd:1599: Recomputing power masks uhub_explore:522: udev=0xfffffffe4057f000 addr=1 uhub_read_port_status:259: port 1, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 2, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 3, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 4, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 5, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 6, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 7, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 8, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION usb2_needs_explore:1345: usb2_bus_powerd:1516: bus=0xfffffffe402c6db0 usb2_bus_powerd:1599: Recomputing power masks uhub_explore:522: udev=0xfffffffe40577000 addr=1 uushub_read_port_status:259: port 1, wPortStatus=0x0303, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION b2uhub_read_port_status:259: port 2, wPortStat_us=0x0n100, wPortChange=0x00e00, erer=USB_ERRd_NORMAL_COMPLETION s_explore:1345: usb2_bus_powerd:1516: bus=0xfffffffe402cfdb0 usb2_bus_powerd:1599: Recomputing power masks uhub_explore:522: udev=0xfffffffe40579000 addr=1 uhub_read_port_status:259: port 1, wPortStatus=0x0100, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 2, wPortStatus=0x0100, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETIusb2O_needs_explore:1345: N usb2_bus_powerd:1516: bus=0xfffffffe402d8db0 usb2_bus_powerd:1599: Recomputing power masks uhub_explore:522: udev=0xfffffffe4057b000 addr=1 uhub_read_port_status:259: port 1, wPortStatus=0x0100, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 2, wPortStatus=0x0100, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION usb2_needs_explore:1345: usb2_bus_powerd:1516: bus=0xfffffffe402e1db0 usb2_bus_powerd:1599: Recomputing power masks uhub_explore:522: udev=0xfffffffe4057d000 addr=1 uhub_read_port_status:259: port 1, wPortStatus=0x0103, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 2, wPortStatus=0x0100, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION usb2_needs_explore:1345: usb2_bus_powerd:1516: bus=0xfffffffe402eac90 usb2_bus_powerd:1599: Recomputing power masks uhub_explore:522: udev=0xfffffffe4057f000 addr=1 uhub_read_port_status:259: port 1, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 2, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 3, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 4, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 5, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 6, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 7, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 8, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION usb2_needs_explore:1345: usb2_bus_powerd:1516: bus=0xfffffffe402c6db0 usb2_bus_powerd:1599: Recomputing power masks uhub_explore:522: udev=0xfffffffe40577000 addr=1 uuhub_read_port_status:259: posrt 1, wPortStatus=0x0303, wPorbtChange=02x0000, err_=USB_ERR_NORMAL_COMPLETION needsu_exhplore:1345: ub_read_port_status:259: port 2, wPortStatus=0x0100, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION usb2_bus_powerd:1516: bus=0xfffffffe402cfdb0 usb2_bus_powerd:1599: Recomputing power masks uhub_explore:522: udev=0xfffffffe40579000 addr=1 uhub_read_port_status:259: port 1, wPortStatus=0x0100, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 2, wPortStatus=0x0100, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETIONusb2_needs_ explore:1345: usb2_bus_powerd:1516: bus=0xfffffffe402d8db0 usb2_bus_powerd:1599: Recomputing power masks uhub_explore:522: udev=0xfffffffe4057b000 addr=1 uhub_read_port_status:259: port 1, wPortStatus=0x0100, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 2, wPortStatus=0x0100, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION usb2_needs_explore:1345: usb2_bus_powerd:1516: bus=0xfffffffe402e1db0 usb2_bus_powerd:1599: Recomputing power masks uhub_explore:522: udev=0xfffffffe4057d000 addr=1 uhub_read_port_status:259: port 1, wPortStatus=0x0103, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 2, wPortStatus=0x0100, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION usb2_needs_explore:1345: usb2_bus_powerd:1516: bus=0xfffffffe402eac90 usb2_bus_powerd:1599: Recomputing power masks uhub_explore:522: udev=0xfffffffe4057f000 addr=1 uhub_read_port_status:259: port 1, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 2, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 3, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 4, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 5, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 6, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 7, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 8, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION usb2_needs_explore:1345: usb2_bus_powerd:1516: bus=0xfffffffe402c6db0 usb2_bus_powerd:1599: Recomputing power masks uhub_explore:522: udev=0xfffffffe40577000 addr=1 uuhub_read_port_status:259: port 1, wPortStatus=0x0303, wPortChange=0x0000,s errb=USB_ERR_NORMAL_COM2PLETION _uhub_renad_port_stateus:259: port e2, wPortStatuds=0x0100, wPortChange=0x0000, ersr=USB__ERR_NORMAL_COMPLETION explore:1345: usb2_bus_powerd:1516: bus=0xfffffffe402cfdb0 usb2_bus_powerd:1599: Recomputing power masks uhub_explore:522: udev=0xfffffffe40579000 addr=1 uhub_read_port_status:259: port 1, wPortStatus=0x0100, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 2, wPortStatus=0x0100, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETIONusb2_needs _explore:1345: usb2_bus_powerd:1516: bus=0xfffffffe402d8db0 usb2_bus_powerd:1599: Recomputing power masks uhub_explore:522: udev=0xfffffffe4057b000 addr=1 uhub_read_port_status:259: port 1, wPortStatus=0x0100, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 2, wPortStatus=0x0100, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION usb2_needs_explore:1345: usb2_bus_powerd:1516: bus=0xfffffffe402e1db0 usb2_bus_powerd:1599: Recomputing power masks uhub_explore:522: udev=0xfffffffe4057d000 addr=1 uhub_read_port_status:259: port 1, wPortStatus=0x0103, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 2, wPortStatus=0x0100, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION usb2_needs_explore:1345: usb2_bus_powerd:1516: bus=0xfffffffe402eac90 usb2_bus_powerd:1599: Recomputing power masks uhub_explore:522: udev=0xfffffffe4057f000 addr=1 uhub_read_port_status:259: port 1, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 2, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 3, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 4, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 5, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 6, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 7, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 8, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION usb2_needs_explore:1345: usb2_bus_powerd:1516: bus=0xfffffffe402c6db0 usb2_bus_powerd:1599: Recomputing power masks uhub_explore:522: udev=0xfffffffe40577000 addr=1 uuhub_read_port_status:259: port 1, wsPortStatus=0x0303, wPortChangeb=0x0000, err=USB_ERR_NORMAL_COMPLETIO2N _uhub_read_port_status:259: port 2, wPortStatus=0x0100, wPortChange=0x0000, err=USB_EnRR_NORMAL_COMPLETION eeds_explore:1345: usb2_bus_powerd:1516: bus=0xfffffffe402cfdb0 usb2_bus_powerd:1599: Recomputing power masks uhub_explore:522: udev=0xfffffffe40579000 addr=1 uhub_read_port_status:259: port 1, wPortStatus=0x0100, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 2, wPortStatus=0x0100, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION usb2_needs_explore:1345: usb2_bus_powerd:1516: bus=0xfffffffe402d8db0 usb2_bus_powerd:1599: Recomputing power masks uhub_explore:522: udev=0xfffffffe4057b000 addr=1 uhub_read_port_status:259: port 1, wPortStatus=0x0100, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 2, wPortStatus=0x0100, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION usb2_needs_explore:1345: usb2_bus_powerd:1516: bus=0xfffffffe402e1db0 usb2_bus_powerd:1599: Recomputing power masks uhub_explore:522: udev=0xfffffffe4057d000 addr=1 uhub_read_port_status:259: port 1, wPortStatus=0x0103, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 2, wPortStatus=0x0100, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION usb2_needs_explore:1345: usb2_bus_powerd:1516: bus=0xfffffffe402eac90 usb2_bus_powerd:1599: Recomputing power masks uhub_explore:522: udev=0xfffffffe4057f000 addr=1 uhub_read_port_status:259: port 1, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 2, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 3, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 4, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 5, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 6, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 7, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 8, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION usb2_needs_explore:1345: usb2_bus_powerd:1516: bus=0xfffffffe402c6db0 usb2_bus_powerd:1599: Recomputing power masks uhub_explore:522: udev=0xfffffffe40577000 addr=1 uusb2_needs_explore:1345: hub_read_port_status:259: port 1, wPortStatus=0x0303, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION usb2_bus_powerd:1516: bus=0xfffffffe402cfdb0 usb2_bus_powerd:1599: Recomputing power masks uhub_explore:522: udev=0xfffffffe40579000 addr=1 uhub_read_port_status:259: port 2, wPortStatus=0x0100, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 1, wPortStatus=0x0100, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 2, wPortStatus=0x0100, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION usb2_needs_explore:1345: usb2_bus_powerd:1516: bus=0xfffffffe402d8db0 usb2_bus_powerd:1599: Recomputing power masks uhub_explore:522: udev=0xfffffffe4057b000 addr=1 uhub_read_port_status:259: port 1, wPortStatus=0x0100, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 2, wPortStatus=0x0100, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION usb2_needs_explore:1345: usb2_bus_powerd:1516: bus=0xfffffffe402e1db0 usb2_bus_powerd:1599: Recomputing power masks uhub_explore:522: udev=0xfffffffe4057d000 addr=1 uhub_read_port_status:259: port 1, wPortStatus=0x0103, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 2, wPortStatus=0x0100, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION From bowie at nrik.jp Fri Feb 13 18:57:10 2009 From: bowie at nrik.jp (Noriyoshi Kawano) Date: Fri Feb 13 18:57:19 2009 Subject: USB2 & apcupsd In-Reply-To: <86fxihiwn2.wl%bowie@nrik.jp> References: <86y6wbf2nc.wl%bowie@nrik.jp> <200902131101.22522.hselasky@c2i.net> <86fxihiwn2.wl%bowie@nrik.jp> Message-ID: <86eiy1iv3x.wl%bowie@nrik.jp> Hi, Hans. I'm sorry. dmesg of the former email disabled apcupsd. dmesg which enabled apcupsd is follows. usb2_needs_explore:1345: usb2_bus_powerd:1516: bus=0xfffffffe402c6db0 usb2_bus_powerd:1599: Recomputing power masks uhub_explore:522: udev=0xfffffffe40577000 addr=1 uhub_read_port_status:259: port 1, wPortStatus=0x0303, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 2, wPortStatus=0x0100, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLEusb2_neTeds_explore:1I345: ON usb2_bus_powerd:1516: bus=0xfffffffe402cfdb0 usb2_bus_powerd:1599: Recomputing power masks uhub_explore:522: udev=0xfffffffe40579000 addr=1 uhub_read_port_status:259: port 1, wPortStatus=0x0100, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 2, wPortStatus=0x0100, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION usb2_needs_explore:1345: usb2_bus_powerd:1516: bus=0xfffffffe402d8db0 usb2_bus_powerd:1599: Recomputing power masks uhub_explore:522: udev=0xfffffffe4057b000 addr=1 uhub_read_port_status:259: port 1, wPortStatus=0x0100, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 2, wPortStatus=0x0100, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION usb2_needs_explore:1345: usb2_bus_powerd:1516: bus=0xfffffffe402e1db0 usb2_bus_powerd:1599: Recomputing power masks uhub_explore:522: udev=0xfffffffe4057d000 addr=1 uhub_read_port_status:259: port 1, wPortStatus=0x0103, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 2, wPortStatus=0x0100, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION usb2_needs_explore:1345: usb2_bus_powerd:1516: bus=0xfffffffe402eac90 usb2_bus_powerd:1599: Recomputing power masks uhub_explore:522: udev=0xfffffffe4057f000 addr=1 uhub_read_port_status:259: port 1, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 2, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 3, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 4, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 5, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 6, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 7, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 8, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION usb2_needs_explore:1345: usb2_bus_powerd:1516: bus=0xfffffffe402c6db0 usb2_bus_powerd:1599: Recomputing power masks uhub_explore:522: udev=0xfffffffe40577000 addr=1 uhub_read_port_status:259: port 1, wPortStatus=0x0303, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 2, wPortStatus=0x0100, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION usb2_needs_explore:1345: usb2_bus_powerd:1516: bus=0xfffffffe402cfdb0 usb2_bus_powerd:1599: Recomputing power masks uhub_explore:522: udev=0xfffffffe40579000 addr=1 uhub_read_port_status:259: port 1, wPortStatus=0x0100, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 2, wPortStatus=0x0100, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION usb2_needs_explore:1345: usb2_bus_powerd:1516: bus=0xfffffffe402d8db0 usb2_bus_powerd:1599: Recomputing power masks uhub_explore:522: udev=0xfffffffe4057b000 addr=1 uhub_read_port_status:259: port 1, wPortStatus=0x0100, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 2, wPortStatus=0x0100, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION usb2_needs_explore:1345: usb2_bus_powerd:1516: bus=0xfffffffe402e1db0 usb2_bus_powerd:1599: Recomputing power masks uhub_explore:522: udev=0xfffffffe4057d000 addr=1 uhub_read_port_status:259: port 1, wPortStatus=0x0103, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 2, wPortStatus=0x0100, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION usb2_needs_explore:1345: usb2_bus_powerd:1516: bus=0xfffffffe402eac90 usb2_bus_powerd:1599: Recomputing power masks uhub_explore:522: udev=0xfffffffe4057f000 addr=1 uhub_read_port_status:259: port 1, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 2, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 3, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhid0: at ushub0, port 1, addr 2 (disconnected) uhub_read_port_status:259: port 4, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_child_pnpinfo_string:966: device not on hub uhub_child_location_string:940: device not on hub uhub_child_pnpinfo_string:966: device not on hub uhub_read_port_status:259: port 5, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION usb2_transfer_power_ref:1470: Adding type u0 to power state usb2_transfer_power_href:u1483b: needs p_ower read_port_status:259: port 6, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 7, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 8, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhid_probe:601: usb2_needs_explore:1345: usb2_bus_powerd:1516: bus=0xfffffffe402c6db0 uhub_explore:522: udev=0xfffffffe40577000 addr=1 uhub_read_port_status:259: port 1, wPortStatus=0x0303, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 2, wPortStatus=0x0100, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION usb2_needs_explore:1345: usb2_bus_powerd:1516: bus=0xfffffffe402cfdb0 usb2_bus_powerd:1599: Recomputing power masks uhub_explore:522: udev=0xfffffffe40579000 addr=1 uhub_read_port_status:259: port 1, wPortStatus=0x0100, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 2, wPortStatus=0x0100, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION usb2_needs_explore:1345: uhid_probe:601: uhid_attach:634: sc=0xffffff0004d8a280 uhid0: on usbus0 usb2_bus_powerd:1516: bus=0xfffffffe402d8db0 usb2_bus_powerd:1599: Recomputing power masks uhub_explore:522: udev=0xfffffffe4057b000 addr=1 uhub_read_port_status:259: port 1, wPortStautus=s0x0100, wPortChange=0x0000b, err=USB_ERR2_NORMAL_COMPLETION _nuhub_reead_port_status:259: port 2, wPeortStatus=0x0100, wPortChange=0x0000, err=USB_ERR_NOdRMAsL_COMPLETION _explore:1345: usb2_bus_powerd:1516: bus=0xfffffffe402e1db0 usb2_bus_powerd:1599: Recomputing power masks uhub_explore:522: udev=0xfffffffe4057d000 addr=1 uhub_read_port_status:259: port 1, wPortStatus=0x0103, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 2, wPortStatus=0x0100, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhid_attach:709: set idle failed, error=USB_ERR_STALLED (ignored) Symlink: uhid0 -> usb0.2.0.16 usb2_transfer_power_ref:1470: Adding type 3 to power state usb2_transfer_power_ref:1483: needs power usb2_needs_explore:1345: usb2_bus_powerd:1516: bus=0xfffffffe402eac90 usb2_bus_powerd:1599: Recomputing power masks uhub_explore:522: udev=0xfffffffe4057f000 addr=1 uhub_read_port_status:259: port 1, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 2, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 3, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 4, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 5, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 6, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 7, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 8, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION usb2_needs_explore:1345: usb2_bus_powerd:1516: bus=0xfffffffe402c6db0 uhub_explore:522: udev=0xfffffffe40577000 addr=1 uhub_read_port_status:259: port 1, wPortStatus=0x0303, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 2, wPortStatus=0x0100, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION usb2_needs_explore:1345: usb2_bus_powerd:1516: bus=0xfffffffe402cfdb0 usb2_bus_powerd:1599: Recomputing power masks uhub_explore:522: udev=0xfffffffe40579000 addr=1 uhub_read_port_status:259: port 1, wPortStatus=0x0100, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 2, wPortStatus=0x0100, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION usb2_needs_explore:1345: usb2_bus_powerd:1516: bus=0xfffffffe402d8db0 usb2_bus_powerd:1599: Recomputing power masks uhub_explore:522: udev=0xfffffffe4057b000 addr=1 uhub_read_port_status:259: port 1, wPortStatus=0x0100, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 2, wPortStatus=0x0100, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION usb2_needs_explore:1345: usb2_bus_powerd:1516: bus=0xfffffffe402e1db0 usb2_bus_powerd:1599: Recomputing power masks uhub_explore:522: udev=0xfffffffe4057d000 addr=1 uhub_read_port_status:259: port 1, wPortStatus=0x0103, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 2, wPortStatus=0x0100, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION usb2_needs_explore:1345: usb2_bus_powerd:1516: bus=0xfffffffe402eac90 usb2_bus_powerd:1599: Recomputing power masks uhub_explore:522: udev=0xfffffffe4057f000 addr=1 uhub_read_port_status:259: port 1, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 2, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 3, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 4, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 5, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 6, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 7, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 8, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION usb2_needs_explore:1345: usb2_bus_powerd:1516: bus=0xfffffffe402c6db0 usb2_bus_powerd:1599: Recomputing power masks uhub_explore:522: udev=0xfffffffe40577000 addr=1 uhub_read_port_status:259: port 1, wPortStatus=0x0303, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 2, wPortStatus=0x0100, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION usb2_needs_explore:1345: usb2_bus_powerd:1516: bus=0xfffffffe402cfdb0 usb2_bus_powerd:1599: Recomputing power masks uhub_explore:522: udev=0xfffffffe40579000 addr=1 uhub_read_port_status:259: port 1, wPortStatus=0x0100, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 2, wPortStatus=0x0100, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION usb2_needs_explore:1345: usb2_bus_powerd:1516: bus=0xfffffffe402d8db0 usb2_bus_powerd:1599: Recomputing power masks uhub_explore:522: udev=0xfffffffe4057b000 addr=1 uhub_read_port_status:259: port 1, wPortStatus=0x0100, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 2, wPortStatus=0x0100, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION usb2_needs_explore:1345: usb2_bus_powerd:1516: bus=0xfffffffe402e1db0 usb2_bus_powerd:1599: Recomputing power masks uhub_explore:522: udev=0xfffffffe4057d000 addr=1 uhub_read_port_status:259: port 1, wPortStatus=0x0103, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 2, wPortStatus=0x0100, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION usb2_needs_explore:1345: usb2_bus_powerd:1516: bus=0xfffffffe402eac90 usb2_bus_powerd:1599: Recomputing power masks uhub_explore:522: udev=0xfffffffe4057f000 addr=1 uhub_read_port_status:259: port 1, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 2, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 3, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 4, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 5, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 6, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 7, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 8, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION usb2_needs_explore:1345: usb2_bus_powerd:1516: bus=0xfffffffe402c6db0 usb2_bus_powerd:1599: Recomputing power masks uhub_explore:522: udev=0xfffffffe40577000 addr=1 uhub_read_port_status:259: port 1, wPortStatus=0x0303, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 2, wPortStatus=0x0100, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION usb2_needs_explore:1345: usb2_bus_powerd:1516: bus=0xfffffffe402cfdb0 usb2_bus_powerd:1599: Recomputing power masks uhub_explore:522: udev=0xfffffffe40579000 addr=1 uhub_read_port_status:259: port 1, wPortStatus=0x0100, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 2, wPortStatus=0x0100, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION usb2_needs_explore:1345: usb2_bus_powerd:1516: bus=0xfffffffe402d8db0 usb2_bus_powerd:1599: Recomputing power masks uhub_explore:522: udev=0xfffffffe4057b000 addr=1 uhub_read_port_status:259: port 1, wPortStatus=0x0100, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 2, wPortStatus=0x0100, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION usb2_needs_explore:1345: usb2_bus_powerd:1516: bus=0xfffffffe402e1db0 usb2_bus_powerd:1599: Recomputing power masks uhub_explore:522: udev=0xfffffffe4057d000 addr=1 uhub_read_port_status:259: port 1, wPortStatus=0x0103, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 2, wPortStatus=0x0100, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION usb2_needs_explore:1345: usb2_bus_powerd:1516: bus=0xfffffffe402eac90 usb2_bus_powerd:1599: Recomputing power masks uhub_explore:522: udev=0xfffffffe4057f000 addr=1 uhub_read_port_status:259: port 1, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 2, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 3, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 4, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 5, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 6, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 7, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 8, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION usb2_needs_explore:1345: usb2_bus_powerd:1516: bus=0xfffffffe402c6db0 usb2_bus_powerd:1599: Recomputing power masks uhub_explore:522: udev=0xfffffffe40577000 addr=1 uhub_read_port_status:259: port 1, wPortStatus=0x0303, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 2, wPortStatus=0x0100, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION usb2_needs_explore:1345: usb2_bus_powerd:1516: bus=0xfffffffe402cfdb0 usb2_bus_powerd:1599: Recomputing power masks uhub_explore:522: udev=0xfffffffe40579000 addr=1 uhub_read_port_status:259: port 1, wPortStatus=0x0100, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 2, wPortStatus=0x0100, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION usb2_needs_explore:1345: usb2_bus_powerd:1516: bus=0xfffffffe402d8db0 usb2_bus_powerd:1599: Recomputing power masks uhub_explore:522: udev=0xfffffffe4057b000 addr=1 uhub_read_port_status:259: port 1, wPortStatus=0x0100, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 2, wPortStatus=0x0100, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION usb2_needs_explore:1345: usb2_bus_powerd:1516: bus=0xfffffffe402e1db0 usb2_bus_powerd:1599: Recomputing power masks uhub_explore:522: udev=0xfffffffe4057d000 addr=1 uhub_read_port_status:259: port 1, wPortStatus=0x0103, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 2, wPortStatus=0x0100, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION usb2_needs_explore:1345: usb2_bus_powerd:1516: bus=0xfffffffe402eac90 usb2_bus_powerd:1599: Recomputing power masks uhub_explore:522: udev=0xfffffffe4057f000 addr=1 uhub_read_port_status:259: port 1, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 2, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 3, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 4, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 5, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 6, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 7, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 8, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION usb2_needs_explore:1345: usb2_bus_powerd:1516: bus=0xfffffffe402c6db0 usb2_bus_powerd:1599: Recomputing power masks uhub_explore:522: udev=0xfffffffe40577000 addr=1 uhub_read_port_status:259: port 1, wPortStatus=0x0303, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 2, wPortStatus=0x0100, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION usb2_needs_explore:1345: usb2_bus_powerd:1516: bus=0xfffffffe402cfdb0 usb2_bus_powerd:1599: Recomputing power masks uhub_explore:522: udev=0xfffffffe40579000 addr=1 uhub_read_port_status:259: port 1, wPortStatus=0x0100, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 2, wPortStatus=0x0100, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION usb2_needs_explore:1345: usb2_bus_powerd:1516: bus=0xfffffffe402d8db0 usb2_bus_powerd:1599: Recomputing power masks uhub_explore:522: udev=0xfffffffe4057b000 addr=1 uhub_read_port_status:259: port 1, wPortStatus=0x0100, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 2, wPortStatus=0x0100, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION usb2_needs_explore:1345: usb2_bus_powerd:1516: bus=0xfffffffe402e1db0 usb2_bus_powerd:1599: Recomputing power masks uhub_explore:522: udev=0xfffffffe4057d000 addr=1 uhub_read_port_status:259: port 1, wPortStatus=0x0103, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 2, wPortStatus=0x0100, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION usb2_needs_explore:1345: usb2_bus_powerd:1516: bus=0xfffffffe402eac90 usb2_bus_powerd:1599: Recomputing power masks uhub_explore:522: udev=0xfffffffe4057f000 addr=1 uhub_read_port_status:259: port 1, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 2, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 3, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 4, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 5, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 6, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 7, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 8, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION usb2_needs_explore:1345: usb2_bus_powerd:1516: bus=0xfffffffe402c6db0 uhub_explore:522: udev=0xfffffffe40577000 addr=1 uhub_read_port_status:259: port 1, wPortStatus=0x0303, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 2, wPortStatus=0x0100, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION usb2_needs_explore:1345: usb2_bus_powerd:1516: bus=0xfffffffe402cfdb0 usb2_bus_powerd:1599: Recomputing power masks uhub_explore:522: udev=0xfffffffe40579000 addr=1 uhub_read_port_status:259: port 1, wPortStatus=0x0100, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 2, wPortStatus=0x0100, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION usb2_needs_explore:1345: usb2_bus_powerd:1516: bus=0xfffffffe402d8db0 usb2_bus_powerd:1599: Recomputing power masks uhub_explore:522: udev=0xfffffffe4057b000 addr=1 uhub_read_port_status:259: port 1, wPortStatus=0x0100, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 2, wPortStatus=0x0100, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION usb2_needs_explore:1345: usb2_bus_powerd:1516: bus=0xfffffffe402e1db0 usb2_bus_powerd:1599: Recomputing power masks uhub_explore:522: udev=0xfffffffe4057d000 addr=1 uhub_read_port_status:259: port 1, wPortStatus=0x0103, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 2, wPortStatus=0x0100, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION usb2_needs_explore:1345: usb2_bus_powerd:1516: bus=0xfffffffe402eac90 usb2_bus_powerd:1599: Recomputing power masks uhub_explore:522: udev=0xfffffffe4057f000 addr=1 uhub_read_port_status:259: port 1, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 2, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 3, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 4, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 5, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 6, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 7, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 8, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION usb2_needs_explore:1345: usb2_bus_powerd:1516: bus=0xfffffffe402c6db0 usb2_bus_powerd:1599: Recomputing power masks uhub_explore:522: udev=0xfffffffe40577000 addr=1 uhub_read_port_status:259: port 1, wPortStatus=0x0303, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 2, wPortStatus=0x0100, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION usb2_needs_explore:1345: usb2_bus_powerd:1516: bus=0xfffffffe402cfdb0 usb2_bus_powerd:1599: Recomputing power masks uhub_explore:522: udev=0xfffffffe40579000 addr=1 uhub_read_port_status:259: port 1, wPortStatus=0x0100, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 2, wPortStatus=0x0100, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION usb2_needs_explore:1345: usb2_bus_powerd:1516: bus=0xfffffffe402d8db0 usb2_bus_powerd:1599: Recomputing power masks uhub_explore:522: udev=0xfffffffe4057b000 addr=1 uhub_read_port_status:259: port 1, wPortStatus=0x0100, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 2, wPortStatus=0x0100, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION usb2_needs_explore:1345: usb2_bus_powerd:1516: bus=0xfffffffe402e1db0 usb2_bus_powerd:1599: Recomputing power masks uhub_explore:522: udev=0xfffffffe4057d000 addr=1 uhub_read_port_status:259: port 1, wPortStatus=0x0103, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 2, wPortStatus=0x0100, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION usb2_needs_explore:1345: usb2_bus_powerd:1516: bus=0xfffffffe402eac90 usb2_bus_powerd:1599: Recomputing power masks uhub_explore:522: udev=0xfffffffe4057f000 addr=1 uhub_read_port_status:259: port 1, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 2, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 3, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 4, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 5, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 6, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 7, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 8, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION usb2_needs_explore:1345: usb2_bus_powerd:1516: bus=0xfffffffe402c6db0 usb2_bus_powerd:1599: Recomputing power masks uhub_explore:522: udev=0xfffffffe40577000 addr=1 uhub_read_port_status:259: port 1, wPortStatus=0x0303, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 2, wPortStatus=0x0100, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION usb2_needs_explore:1345: usb2_bus_powerd:1516: bus=0xfffffffe402cfdb0 usb2_bus_powerd:1599: Recomputing power masks uhub_explore:522: udev=0xfffffffe40579000 addr=1 uhub_read_port_status:259: port 1, wPortStatus=0x0100, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 2, wPortStatus=0x0100, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION usb2_needs_explore:1345: usb2_bus_powerd:1516: bus=0xfffffffe402d8db0 usb2_bus_powerd:1599: Recomputing power masks uhub_explore:522: udev=0xfffffffe4057b000 addr=1 uhub_read_port_status:259: port 1, wPortStatus=0x0100, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 2, wPortStatus=0x0100, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION usb2_needs_explore:1345: usb2_bus_powerd:1516: bus=0xfffffffe402e1db0 usb2_bus_powerd:1599: Recomputing power masks uhub_explore:522: udev=0xfffffffe4057d000 addr=1 uhub_read_port_status:259: port 1, wPortStatus=0x0103, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 2, wPortStatus=0x0100, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION usb2_needs_explore:1345: usb2_bus_powerd:1516: bus=0xfffffffe402eac90 usb2_bus_powerd:1599: Recomputing power masks uhub_explore:522: udev=0xfffffffe4057f000 addr=1 uhub_read_port_status:259: port 1, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 2, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 3, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 4, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 5, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 6, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 7, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 8, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION usb2_needs_explore:1345: usb2_bus_powerd:1516: bus=0xfffffffe402c6db0 usb2_bus_powerd:1599: Recomputing power masks uhub_explore:522: udev=0xfffffffe40577000 addr=1 uhub_read_port_status:259: port 1, wPortStatus=0x0303, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 2, wPortStatus=0x0100, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION usb2_needs_explore:1345: usb2_bus_powerd:1516: bus=0xfffffffe402cfdb0 usb2_bus_powerd:1599: Recomputing power masks uhub_explore:522: udev=0xfffffffe40579000 addr=1 uhub_read_port_status:259: port 1, wPortStatus=0x0100, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 2, wPortStatus=0x0100, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION usb2_needs_explore:1345: usb2_bus_powerd:1516: bus=0xfffffffe402d8db0 usb2_bus_powerd:1599: Recomputing power masks uhub_explore:522: udev=0xfffffffe4057b000 addr=1 uhub_read_port_status:259: port 1, wPortStatus=0x0100, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 2, wPortStatus=0x0100, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION usb2_needs_explore:1345: usb2_bus_powerd:1516: bus=0xfffffffe402e1db0 usb2_bus_powerd:1599: Recomputing power masks uhub_explore:522: udev=0xfffffffe4057d000 addr=1 uhub_read_port_status:259: port 1, wPortStatus=0x0103, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 2, wPortStatus=0x0100, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION usb2_needs_explore:1345: usb2_bus_powerd:1516: bus=0xfffffffe402eac90 usb2_bus_powerd:1599: Recomputing power masks uhub_explore:522: udev=0xfffffffe4057f000 addr=1 uhub_read_port_status:259: port 1, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 2, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 3, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 4, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 5, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 6, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 7, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 8, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION usb2_needs_explore:1345: usb2_bus_powerd:1516: bus=0xfffffffe402c6db0 usb2_bus_powerd:1599: Recomputing power masks uhub_explore:522: udev=0xfffffffe40577000 addr=1 uhub_read_port_status:259: port 1, wPortStatus=0x0303, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 2, wPortStatus=0x0100, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION usb2_needs_explore:1345: usb2_bus_powerd:1516: bus=0xfffffffe402cfdb0 usb2_bus_powerd:1599: Recomputing power masks uhub_explore:522: udev=0xfffffffe40579000 addr=1 uhub_read_port_status:259: port 1, wPortStatus=0x0100, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 2, wPortStatus=0x0100, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION usb2_needs_explore:1345: usb2_bus_powerd:1516: bus=0xfffffffe402d8db0 usb2_bus_powerd:1599: Recomputing power masks uhub_explore:522: udev=0xfffffffe4057b000 addr=1 uhub_read_port_status:259: port 1, wPortStatus=0x0100, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 2, wPortStatus=0x0100, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION usb2_needs_explore:1345: usb2_bus_powerd:1516: bus=0xfffffffe402e1db0 usb2_bus_powerd:1599: Recomputing power masks uhub_explore:522: udev=0xfffffffe4057d000 addr=1 uhub_read_port_status:259: port 1, wPortStatus=0x0103, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 2, wPortStatus=0x0100, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION usb2_needs_explore:1345: usb2_bus_powerd:1516: bus=0xfffffffe402eac90 usb2_bus_powerd:1599: Recomputing power masks uhub_explore:522: udev=0xfffffffe4057f000 addr=1 uhub_read_port_status:259: port 1, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 2, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 3, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 4, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 5, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 6, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 7, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 8, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION usb2_needs_explore:1345: usb2_bus_powerd:1516: bus=0xfffffffe402c6db0 uhub_explore:522: udev=0xfffffffe40577000 addr=1 uhub_read_port_status:259: port 1, wPortStatus=0x0303, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 2, wPortStatus=0x0100, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION usb2_needs_explore:1345: usb2_bus_powerd:1516: bus=0xfffffffe402cfdb0 usb2_bus_powerd:1599: Recomputing power masks uhub_explore:522: udev=0xfffffffe40579000 addr=1 uhub_read_port_status:259: port 1, wPortStatus=0x0100, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 2, wPortStatus=0x0100, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION usb2_needs_explore:1345: usb2_bus_powerd:1516: bus=0xfffffffe402d8db0 usb2_bus_powerd:1599: Recomputing power masks uhub_explore:522: udev=0xfffffffe4057b000 addr=1 uhub_read_port_status:259: port 1, wPortStatus=0x0100, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 2, wPortStatus=0x0100, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION usb2_needs_explore:1345: usb2_bus_powerd:1516: bus=0xfffffffe402e1db0 usb2_bus_powerd:1599: Recomputing power masks uhub_explore:522: udev=0xfffffffe4057d000 addr=1 uhub_read_port_status:259: port 1, wPortStatus=0x0103, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 2, wPortStatus=0x0100, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION usb2_needs_explore:1345: usb2_bus_powerd:1516: bus=0xfffffffe402eac90 usb2_bus_powerd:1599: Recomputing power masks uhub_explore:522: udev=0xfffffffe4057f000 addr=1 uhub_read_port_status:259: port 1, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 2, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 3, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 4, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 5, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 6, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 7, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 8, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION usb2_needs_explore:1345: usb2_bus_powerd:1516: bus=0xfffffffe402c6db0 usb2_bus_powerd:1599: Recomputing power masks uhub_explore:522: udev=0xfffffffe40577000 addr=1 uhub_read_port_status:259: port 1, wPortStatus=0x0303, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 2, wPortStatus=0x0100, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION usb2_needs_explore:1345: usb2_bus_powerd:1516: bus=0xfffffffe402cfdb0 usb2_bus_powerd:1599: Recomputing power masks uhub_explore:522: udev=0xfffffffe40579000 addr=1 uhub_read_port_status:259: port 1, wPortStatus=0x0100, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 2, wPortStatus=0x0100, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION usb2_needs_explore:1345: usb2_bus_powerd:1516: bus=0xfffffffe402d8db0 usb2_bus_powerd:1599: Recomputing power masks uhub_explore:522: udev=0xfffffffe4057b000 addr=1 uhub_read_port_status:259: port 1, wPortStatus=0x0100, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 2, wPortStatus=0x0100, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION usb2_needs_explore:1345: usb2_bus_powerd:1516: bus=0xfffffffe402e1db0 usb2_bus_powerd:1599: Recomputing power masks uhub_explore:522: udev=0xfffffffe4057d000 addr=1 uhub_read_port_status:259: port 1, wPortStatus=0x0103, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 2, wPortStatus=0x0100, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION usb2_needs_explore:1345: usb2_bus_powerd:1516: bus=0xfffffffe402eac90 usb2_bus_powerd:1599: Recomputing power masks uhub_explore:522: udev=0xfffffffe4057f000 addr=1 uhub_read_port_status:259: port 1, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 2, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 3, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 4, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 5, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 6, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 7, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 8, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION usb2_needs_explore:1345: usb2_bus_powerd:1516: bus=0xfffffffe402c6db0 usb2_bus_powerd:1599: Recomputing power masks uhub_explore:522: udev=0xfffffffe40577000 addr=1 uhub_read_port_status:259: port 1, wPortStatus=0x0303, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 2, wPortStatus=0x0100, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION usb2_needs_explore:1345: usb2_bus_powerd:1516: bus=0xfffffffe402cfdb0 usb2_bus_powerd:1599: Recomputing power masks uhub_explore:522: udev=0xfffffffe40579000 addr=1 uhub_read_port_status:259: port 1, wPortStatus=0x0100, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 2, wPortStatus=0x0100, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION usb2_needs_explore:1345: usb2_bus_powerd:1516: bus=0xfffffffe402d8db0 usb2_bus_powerd:1599: Recomputing power masks uhub_explore:522: udev=0xfffffffe4057b000 addr=1 uhub_read_port_status:259: port 1, wPortStatus=0x0100, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 2, wPortStatus=0x0100, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION usb2_needs_explore:1345: usb2_bus_powerd:1516: bus=0xfffffffe402e1db0 usb2_bus_powerd:1599: Recomputing power masks uhub_explore:522: udev=0xfffffffe4057d000 addr=1 uhub_read_port_status:259: port 1, wPortStatus=0x0103, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 2, wPortStatus=0x0100, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION usb2_needs_explore:1345: usb2_bus_powerd:1516: bus=0xfffffffe402eac90 usb2_bus_powerd:1599: Recomputing power masks uhub_explore:522: udev=0xfffffffe4057f000 addr=1 uhub_read_port_status:259: port 1, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 2, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 3, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 4, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 5, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 6, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 7, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 8, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION usb2_needs_explore:1345: usb2_bus_powerd:1516: bus=0xfffffffe402c6db0 usb2_bus_powerd:1599: Recomputing power masks uhub_explore:522: udev=0xfffffffe40577000 addr=1 uhub_read_port_status:259: port 1, wPortStatus=0x0303, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 2, wPortStatus=0x0100, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION usb2_needs_explore:1345: usb2_bus_powerd:1516: bus=0xfffffffe402cfdb0 usb2_bus_powerd:1599: Recomputing power masks uhub_explore:522: udev=0xfffffffe40579000 addr=1 uhub_read_port_status:259: port 1, wPortStatus=0x0100, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 2, wPortStatus=0x0100, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION usb2_needs_explore:1345: usb2_bus_powerd:1516: bus=0xfffffffe402d8db0 usb2_bus_powerd:1599: Recomputing power masks uhub_explore:522: udev=0xfffffffe4057b000 addr=1 uhub_read_port_status:259: port 1, wPortStatus=0x0100, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 2, wPortStatus=0x0100, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION usb2_needs_explore:1345: usb2_bus_powerd:1516: bus=0xfffffffe402e1db0 usb2_bus_powerd:1599: Recomputing power masks uhub_explore:522: udev=0xfffffffe4057d000 addr=1 uhub_read_port_status:259: port 1, wPortStatus=0x0103, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 2, wPortStatus=0x0100, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION usb2_needs_explore:1345: usb2_bus_powerd:1516: bus=0xfffffffe402eac90 usb2_bus_powerd:1599: Recomputing power masks uhub_explore:522: udev=0xfffffffe4057f000 addr=1 uhub_read_port_status:259: port 1, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 2, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 3, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 4, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 5, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 6, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 7, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 8, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION usb2_needs_explore:1345: usb2_bus_powerd:1516: bus=0xfffffffe402c6db0 uhub_explore:522: udev=0xfffffffe40577000 addr=1 uhub_read_port_status:259: port 1, wPortStatus=0x0303, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 2, wPortStatus=0x0100, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION usb2_needs_explore:1345: usb2_bus_powerd:1516: bus=0xfffffffe402cfdb0 usb2_bus_powerd:1599: Recomputing power masks uhub_explore:522: udev=0xfffffffe40579000 addr=1 uhub_read_port_status:259: port 1, wPortStatus=0x0100, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 2, wPortStatus=0x0100, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION usb2_needs_explore:1345: usb2_bus_powerd:1516: bus=0xfffffffe402d8db0 usb2_bus_powerd:1599: Recomputing power masks uhub_explore:522: udev=0xfffffffe4057b000 addr=1 uhub_read_port_status:259: port 1, wPortStatus=0x0100, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 2, wPortStatus=0x0100, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION usb2_needs_explore:1345: usb2_bus_powerd:1516: bus=0xfffffffe402e1db0 usb2_bus_powerd:1599: Recomputing power masks uhub_explore:522: udev=0xfffffffe4057d000 addr=1 uhub_read_port_status:259: port 1, wPortStatus=0x0103, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 2, wPortStatus=0x0100, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION usb2_needs_explore:1345: usb2_bus_powerd:1516: bus=0xfffffffe402eac90 usb2_bus_powerd:1599: Recomputing power masks uhub_explore:522: udev=0xfffffffe4057f000 addr=1 uhub_read_port_status:259: port 1, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 2, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 3, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 4, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 5, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 6, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 7, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 8, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION usb2_needs_explore:1345: usb2_bus_powerd:1516: bus=0xfffffffe402c6db0 usb2_bus_powerd:1599: Recomputing power masks uhub_explore:522: udev=0xfffffffe40577000 addr=1 uhub_read_port_status:259: port 1, wPortStatus=0x0303, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 2, wPortStatus=0x0100, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION usb2_needs_explore:1345: usb2_bus_powerd:1516: bus=0xfffffffe402cfdb0 usb2_bus_powerd:1599: Recomputing power masks uhub_explore:522: udev=0xfffffffe40579000 addr=1 uhub_read_port_status:259: port 1, wPortStatus=0x0100, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 2, wPortStatus=0x0100, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION usb2_needs_explore:1345: usb2_bus_powerd:1516: bus=0xfffffffe402d8db0 usb2_bus_powerd:1599: Recomputing power masks uhub_explore:522: udev=0xfffffffe4057b000 addr=1 uhub_read_port_status:259: port 1, wPortStatus=0x0100, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 2, wPortStatus=0x0100, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETIONusb2_needs_explore:1345: usb2_bus_powerd:1516: bus=0xfffffffe402e1db0 usb2_bus_powerd:1599: Recomputing power masks uhub_explore:522: udev=0xfffffffe4057d000 addr=1 uhub_read_port_status:259: port 1, wPortStatus=0x0103, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 2, wPortStatus=0x0100, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhid0: at ushub0, port 1, addr 2 (disconnected) uhub_child_pnpinfo_string:966: device not on hub uhub_child_location_string:940: device not on hub uhub_child_pnpinfo_string:966: device not on hub usb2_transfer_power_ref:1470: Adding type 0 to power state usb2_transfer_power_ref:1483: needs power uhid_probe:601: uhid_probe:601: uhid_attach:634: sc=0xffffff0004d8d000 uhid0: on usbus0 uhid_attach:709: set idle failed, error=USB_ERR_STALLED (ignored) Symlink: uhid0 -> usb0.2.0.16 usb2_needs_explore:1345: usb2_bus_powerd:1516: bus=0xfffffffe402eac90 usb2_bus_powerd:1599: Recomputing power masks uhub_explore:522: udev=0xfffffffe4057f000 addr=1 uhub_read_port_status:259: port 1, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 2, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 3, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 4, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 5, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 6, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 7, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 8, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION usb2_needs_explore:1345: usb2_bus_powerd:1516: bus=0xfffffffe402c6db0 usb2_bus_powerd:1599: Recomputing power masks uhub_explore:522: udev=0xfffffffe40577000 addr=1 uhub_read_port_status:259: port 1, wPortStatus=0x0303, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 2, wPortStatus=0x0100, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION usb2_needs_explore:1345: usb2_bus_powerd:1516: bus=0xfffffffe402cfdb0 usb2_bus_powerd:1599: Recomputing power masks uhub_explore:522: udev=0xfffffffe40579000 addr=1 uhub_read_port_status:259: port 1, wPortStatus=0x0100, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 2, wPortStatus=0x0100, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION usb2_needs_explore:1345: usb2_bus_powerd:1516: bus=0xfffffffe402d8db0 usb2_bus_powerd:1599: Recomputing power masks uhub_explore:522: udev=0xfffffffe4057b000 addr=1 uhub_read_port_status:259: port 1, wPortStatus=0x0100, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 2, wPortStatus=0x0100, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION usb2_needs_explore:1345: usb2_bus_powerd:1516: bus=0xfffffffe402e1db0 usb2_bus_powerd:1599: Recomputing power masks uhub_explore:522: udev=0xfffffffe4057d000 addr=1 uhub_read_port_status:259: port 1, wPortStatus=0x0103, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 2, wPortStatus=0x0100, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION usb2_needs_explore:1345: usb2_bus_powerd:1516: bus=0xfffffffe402eac90 usb2_bus_powerd:1599: Recomputing power masks uhub_explore:522: udev=0xfffffffe4057f000 addr=1 uhub_read_port_status:259: port 1, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 2, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 3, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 4, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 5, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 6, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 7, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 8, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION usb2_needs_explore:1345: usb2_bus_powerd:1516: bus=0xfffffffe402c6db0 uhub_explore:522: udev=0xfffffffe40577000 addr=1 uhub_read_port_status:259: port 1, wPortStatus=0x0303, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 2, wPortStatus=0x0100, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION usb2_needs_explore:1345: usb2_bus_powerd:1516: bus=0xfffffffe402cfdb0 usb2_bus_powerd:1599: Recomputing power masks uhub_explore:522: udev=0xfffffffe40579000 addr=1 uhub_read_port_status:259: port 1, wPortStatus=0x0100, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 2, wPortStatus=0x0100, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION usb2_needs_explore:1345: usb2_bus_powerd:1516: bus=0xfffffffe402d8db0 usb2_bus_powerd:1599: Recomputing power masks uhub_explore:522: udev=0xfffffffe4057b000 addr=1 uhub_read_port_status:259: port 1, wPortStatus=0x0100, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 2, wPortStatus=0x0100, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION usb2_needs_explore:1345: usb2_bus_powerd:1516: bus=0xfffffffe402e1db0 usb2_bus_powerd:1599: Recomputing power masks uhub_explore:522: udev=0xfffffffe4057d000 addr=1 uhub_read_port_status:259: port 1, wPortStatus=0x0103, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 2, wPortStatus=0x0100, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION usb2_transfer_power_ref:1470: Adding type 3 to power state usb2_transfer_power_ref:1483: needs power usb2_needs_explore:1345: usb2_bus_powerd:1516: bus=0xfffffffe402eac90 usb2_bus_powerd:1599: Recomputing power masks uhub_explore:522: udev=0xfffffffe4057f000 addr=1 uhub_read_port_status:259: port 1, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 2, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 3, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 4, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 5, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 6, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 7, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 8, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION usb2_needs_explore:1345: usb2_bus_powerd:1516: bus=0xfffffffe402c6db0 usb2_bus_powerd:1599: Recomputing power masks uhub_explore:522: udev=0xfffffffe40577000 addr=1 uhub_read_port_status:259: port 1, wPortStatus=0x0303, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 2, wPortStatus=0x0100, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLusb2_needs_explore:E1345: TION usb2_bus_powerd:1516: bus=0xfffffffe402cfdb0 usb2_bus_powerd:1599: Recomputing power masks uhub_explore:522: udev=0xfffffffe40579000 addr=1 uhub_read_port_status:259: port 1, wPortStatus=0x0100, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 2, wPortStatus=0x0100, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION usb2_needs_explore:1345: usb2_bus_powerd:1516: bus=0xfffffffe402d8db0 usb2_bus_powerd:1599: Recomputing power masks uhub_explore:522: udev=0xfffffffe4057b000 addr=1 uhub_read_port_status:259: port 1, wPortStatus=0x0100, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 2, wPortStatus=0x0100, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION usb2_needs_explore:1345: usb2_bus_powerd:1516: bus=0xfffffffe402e1db0 usb2_bus_powerd:1599: Recomputing power masks uhub_explore:522: udev=0xfffffffe4057d000 addr=1 uhub_read_port_status:259: port 1, wPortStatus=0x0103, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 2, wPortStatus=0x0100, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION usb2_needs_explore:1345: usb2_bus_powerd:1516: bus=0xfffffffe402eac90 usb2_bus_powerd:1599: Recomputing power masks uhub_explore:522: udev=0xfffffffe4057f000 addr=1 uhub_read_port_status:259: port 1, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 2, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 3, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 4, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 5, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 6, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 7, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 8, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION usb2_needs_explore:1345: usb2_bus_powerd:1516: bus=0xfffffffe402c6db0 usb2_bus_powerd:1599: Recomputing power masks uhub_explore:522: udev=0xfffffffe40577000 addr=1 uhub_read_port_status:259: port 1, wPortStatus=0x0303, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 2, wPortStatus=0x0100, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION usb2_needs_explore:1345: usb2_bus_powerd:1516: bus=0xfffffffe402cfdb0 usb2_bus_powerd:1599: Recomputing power masks uhub_explore:522: udev=0xfffffffe40579000 addr=1 uhub_read_port_status:259: port 1, wPortStatus=0x0100, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 2, wPortStatus=0x0100, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION usb2_needs_explore:1345: usb2_bus_powerd:1516: bus=0xfffffffe402d8db0 usb2_bus_powerd:1599: Recomputing power masks uhub_explore:522: udev=0xfffffffe4057b000 addr=1 uhub_read_port_status:259: port 1, wPortStatus=0x0100, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 2, wPortStatus=0x0100, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION usb2_needs_explore:1345: usb2_bus_powerd:1516: bus=0xfffffffe402e1db0 usb2_bus_powerd:1599: Recomputing power masks uhub_explore:522: udev=0xfffffffe4057d000 addr=1 uhub_read_port_status:259: port 1, wPortStatus=0x0103, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 2, wPortStatus=0x0100, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION usb2_needs_explore:1345: usb2_bus_powerd:1516: bus=0xfffffffe402eac90 usb2_bus_powerd:1599: Recomputing power masks uhub_explore:522: udev=0xfffffffe4057f000 addr=1 uhub_read_port_status:259: port 1, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 2, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 3, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 4, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 5, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 6, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 7, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 8, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION usb2_needs_explore:1345: usb2_bus_powerd:1516: bus=0xfffffffe402c6db0 usb2_bus_powerd:1599: Recomputing power masks uhub_explore:522: udev=0xfffffffe40577000 addr=1 uhub_read_port_status:259: port 1, wPortStatus=0x0303, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 2, wPortStatus=0x0100, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION usb2_needs_explore:1345: usb2_bus_powerd:1516: bus=0xfffffffe402cfdb0 usb2_bus_powerd:1599: Recomputing power masks uhub_explore:522: udev=0xfffffffe40579000 addr=1 uhub_read_port_status:259: port 1, wPortStatus=0x0100, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 2, wPortStatus=0x0100, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION usb2_needs_explore:1345: usb2_bus_powerd:1516: bus=0xfffffffe402d8db0 usb2_bus_powerd:1599: Recomputing power masks uhub_explore:522: udev=0xfffffffe4057b000 addr=1 uhub_read_port_status:259: port 1, wPortStatus=0x0100, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 2, wPortStatus=0x0100, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION usb2_needs_explore:1345: usb2_bus_powerd:1516: bus=0xfffffffe402e1db0 usb2_bus_powerd:1599: Recomputing power masks uhub_explore:522: udev=0xfffffffe4057d000 addr=1 uhub_read_port_status:259: port 1, wPortStatus=0x0103, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 2, wPortStatus=0x0100, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION usb2_needs_explore:1345: usb2_bus_powerd:1516: bus=0xfffffffe402eac90 usb2_bus_powerd:1599: Recomputing power masks uhub_explore:522: udev=0xfffffffe4057f000 addr=1 uhub_read_port_status:259: port 1, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 2, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 3, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 4, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 5, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 6, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 7, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 8, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION usb2_needs_explore:1345: usb2_bus_powerd:1516: bus=0xfffffffe402c6db0 uhub_explore:522: udev=0xfffffffe40577000 addr=1 uhub_read_port_status:259: port 1, wPortStatus=0x0303, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 2, wPortStatus=0x0100, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION usb2_needs_explore:1345: usb2_bus_powerd:1516: bus=0xfffffffe402cfdb0 usb2_bus_powerd:1599: Recomputing power masks uhub_explore:522: udev=0xfffffffe40579000 addr=1 uhub_read_port_status:259: port 1, wPortStatus=0x0100, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 2, wPortStatus=0x0100, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION usb2_needs_explore:1345: usb2_bus_powerd:1516: bus=0xfffffffe402d8db0 usb2_bus_powerd:1599: Recomputing power masks uhub_explore:522: udev=0xfffffffe4057b000 addr=1 uhub_read_port_status:259: port 1, wPortStatus=0x0100, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 2, wPortStatus=0x0100, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION usb2_needs_explore:1345: usb2_bus_powerd:1516: bus=0xfffffffe402e1db0 usb2_bus_powerd:1599: Recomputing power masks uhub_explore:522: udev=0xfffffffe4057d000 addr=1 uhub_read_port_status:259: port 1, wPortStatus=0x0103, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 2, wPortStatus=0x0100, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION usb2_needs_explore:1345: usb2_bus_powerd:1516: bus=0xfffffffe402eac90 usb2_bus_powerd:1599: Recomputing power masks uhub_explore:522: udev=0xfffffffe4057f000 addr=1 uhub_read_port_status:259: port 1, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 2, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 3, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 4, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 5, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 6, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 7, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 8, wPortStatus=0x0500, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION usb2_needs_explore:1345: usb2_bus_powerd:1516: bus=0xfffffffe402c6db0 usb2_bus_powerd:1599: Recomputing power masks uhub_explore:522: udev=0xfffffffe40577000 addr=1 uhub_read_port_status:259: port 1, wPortStatus=0x0303, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 2, wPortStatus=0x0100, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION usb2_needs_explore:1345: usb2_bus_powerd:1516: bus=0xfffffffe402cfdb0 usb2_bus_powerd:1599: Recomputing power masks uhub_explore:522: udev=0xfffffffe40579000 addr=1 uhub_read_port_status:259: port 1, wPortStatus=0x0100, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 2, wPortStatus=0x0100, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION usb2_needs_explore:1345: usb2_bus_powerd:1516: bus=0xfffffffe402d8db0 usb2_bus_powerd:1599: Recomputing power masks uhub_explore:522: udev=0xfffffffe4057b000 addr=1 uhub_read_port_status:259: port 1, wPortStatus=0x0100, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 2, wPortStatus=0x0100, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION usb2_needs_explore:1345: usb2_bus_powerd:1516: bus=0xfffffffe402e1db0 usb2_bus_powerd:1599: Recomputing power masks uhub_explore:522: udev=0xfffffffe4057d000 addr=1 uhub_read_port_status:259: port 1, wPortStatus=0x0103, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION uhub_read_port_status:259: port 2, wPortStatus=0x0100, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION From hselasky at c2i.net Sat Feb 14 01:34:29 2009 From: hselasky at c2i.net (Hans Petter Selasky) Date: Sat Feb 14 01:34:36 2009 Subject: USB2 & apcupsd In-Reply-To: <86eiy1iv3x.wl%bowie@nrik.jp> References: <86y6wbf2nc.wl%bowie@nrik.jp> <86fxihiwn2.wl%bowie@nrik.jp> <86eiy1iv3x.wl%bowie@nrik.jp> Message-ID: <200902141036.54246.hselasky@c2i.net> On Saturday 14 February 2009, Noriyoshi Kawano wrote: > Hi, Hans. > > I'm sorry. dmesg of the former email disabled apcupsd. > dmesg which enabled apcupsd is follows. Hi, As long as you don't see ugenX.Y attach/detach messages, it means that the Apcupsd daemon is doing something. Probably it is the "usb_link_check()" procedure that is executing and the connection is reset by the following code: if (my_data->fd) { usb_reset(my_data->fd); /* XXX: usb_close() not needed according to libusb0.1 refdocs */ usb_close(my_data->fd); Could you enable debugging in Apcupsd ? What speed is your device reported like by usbconfig ? --HPS From Thomas.Sparrevohn at btinternet.com Sat Feb 14 06:24:41 2009 From: Thomas.Sparrevohn at btinternet.com (Thomas Sparrevohn) Date: Sat Feb 14 06:24:48 2009 Subject: Recent Changes to Rum driver - seems to have.. In-Reply-To: <20090212042350.GE74077@citylink.fud.org.nz> References: <200902111000.46643.hselasky@c2i.net> <20090212042350.GE74077@citylink.fud.org.nz> Message-ID: <010e01c98eaf$f80c5ab0$e8251010$@Sparrevohn@btinternet.com> I am sure you're right Andrew I would not have expected the change unless there was a good reason for it - I find some time to do some testing and give feedback -----Original Message----- From: Andrew Thompson [mailto:thompsa@FreeBSD.org] Sent: 12 February 2009 04:24 To: Hans Petter Selasky Cc: freebsd-usb@freebsd.org; Thomas Sparrevohn Subject: Re: Recent Changes to Rum driver - seems to have.. On Wed, Feb 11, 2009 at 10:00:45AM +0100, Hans Petter Selasky wrote: > On Tuesday 10 February 2009, Thomas Sparrevohn wrote: > > Reintroduced panics when the device is used heavily - it also reports the > > "needs callback" in dmesg - Unless this is known I can post a dmesg > > > > Hi Thomas, > > Andrew Thompson decided to re-port the driver from USB1. I've tried to fix > most of the bugs now. If the fixes are not in -current yet you can fetch > if_rum*[ch] from: > > svn --username anonsvn --password anonsvn \ > checkout svn://svn.turbocat.net/i4b/trunk/i4b/src/sys/dev/usb2 > > > Do you have a backtrace of the panics ? > > Sorry about the inconvenience. Please watch the mud slinging, there were very good reasons for changing the wlan code back to the USB1 state (bugs and all). Each regression will be investigated and fixed. From mah at jump-ing.de Sun Feb 15 03:10:05 2009 From: mah at jump-ing.de (Markus Hitter) Date: Sun Feb 15 03:10:11 2009 Subject: usb/98343: [boot] BBB reset failed errors with Creative Muvo MP3 player; can't boot with external USB 2.0 drive powered up Message-ID: <200902151110.n1FBA2rx042039@freefall.freebsd.org> The following reply was made to PR usb/98343; it has been noted by GNATS. From: Markus Hitter To: bug-followup@FreeBSD.org, wtd@pobox.com Cc: Subject: Re: usb/98343: [boot] BBB reset failed errors with Creative Muvo MP3 player; can't boot with external USB 2.0 drive powered up Date: Sun, 15 Feb 2009 12:04:45 +0100 All my USB pen drive trouble disappeared after installing (parts of) Hans Petter Selasky's i4b package (which is currently introduced as usb2 into Current/8): cd /usr svn --username anonsvn --password anonsvn \ checkout svn://svn.turbocat.net/i4b/trunk/i4b cd i4b/FreeBSD.usb2 make S=../src package make install Then build a new kernel (same kernel config), install it and you should be done. I've tested OHCI and EHCI, both didn't show a single mistake after an hour of formatting and shuffling hundreds of megabytes of files around. Thanks a lot to Hans Petter. From thompsa at FreeBSD.org Sun Feb 15 14:41:06 2009 From: thompsa at FreeBSD.org (Andrew Thompson) Date: Sun Feb 15 14:41:12 2009 Subject: HEADSUP: USB2 now default in GENERIC kernels Message-ID: <20090215224104.GC74071@citylink.fud.org.nz> Hi, The GENERIC kernels for all architectures now default to the new USB2 stack. No kernel config options or code have been removed so if a problem arises please report it and optionally revert to the old USB stack. IMPORTANT NOTES: 1. If you are loading USB kernel modules then ensure that these are also changed over, eg uftdi.ko -> usb2_serial_ftdi.ko. You can not load oldUSB modules with the GENERIC kernels. 2. If you have a custom kernel that includes GENERIC as a base, you need to ensure that any additional usb devices that you specify are changed over. 3. The USB2 kernel options and module names are _temporary_. The next stage is to move the USB2 code into its permanent location in the source tree and at that point will take over the well established naming. (ie, usb, ehci, ohci, uftdi). There will be no changes going from FreeBSD 7.x -> 8.0 4. Once (3) is complete the oldUSB code will still be usable until much closer to the 8.0 branch. Please report any issues to the mailing lists. regards, Andrew From bowie at nrik.jp Sun Feb 15 23:15:52 2009 From: bowie at nrik.jp (Noriyoshi Kawano) Date: Sun Feb 15 23:15:58 2009 Subject: USB2 & apcupsd In-Reply-To: <200902141036.54246.hselasky@c2i.net> References: <86y6wbf2nc.wl%bowie@nrik.jp> <86fxihiwn2.wl%bowie@nrik.jp> <86eiy1iv3x.wl%bowie@nrik.jp> <200902141036.54246.hselasky@c2i.net> Message-ID: <86d4dij1i2.wl%bowie@nrik.jp> At Sat, 14 Feb 2009 10:36:53 +0100, Hans Petter Selasky wrote: > Hi, > > As long as you don't see ugenX.Y attach/detach messages, it means that the > Apcupsd daemon is doing something. Probably it is the "usb_link_check()" > procedure that is executing and the connection is reset by the following > code: > > if (my_data->fd) { > usb_reset(my_data->fd); > /* XXX: usb_close() not needed according to libusb0.1 refdocs */ > usb_close(my_data->fd); > > Could you enable debugging in Apcupsd ? > > What speed is your device reported like by usbconfig ? > > --HPS Hi, I enabled debugging in apcupsd. Because the "usb_interrupt_read()" becomes the error, the "usb_link_check()" is called. # apcupsd -d 500 --- snip --- 61.689 apcupsd: generic-usb.c:538 Timeout=539 62.232 apcupsd: generic-usb.c:549 usb_interrupt_read error: (-1) Operation not permitted 62.232 apcupsd: generic-usb.c:458 link_check comm lost 68.538 apcupsd: generic-usb.c:300 Reinitializing private structure. 68.539 apcupsd: generic-usb.c:398 Initializing libusb 68.539 apcupsd: generic-usb.c:403 Found 0 USB busses 68.539 apcupsd: generic-usb.c:405 Found 0 USB devices 68.539 apcupsd: generic-usb.c:416 /dev/usb:/dev/ugen3.2 - 0000:0000 68.539 apcupsd: generic-usb.c:416 /dev/usb:/dev/ugen0.2 - 051d:0002 --- snip --- # usbconfig -u 0 -a 2 ugen0.2: at usbus0, cfg=0 md=HOST spd=LOW (1.5Mbps) pwr=ON Noriyoshi Kawano From hselasky at c2i.net Sun Feb 15 23:33:31 2009 From: hselasky at c2i.net (Hans Petter Selasky) Date: Sun Feb 15 23:33:37 2009 Subject: USB2 & apcupsd In-Reply-To: <86d4dij1i2.wl%bowie@nrik.jp> References: <86y6wbf2nc.wl%bowie@nrik.jp> <200902141036.54246.hselasky@c2i.net> <86d4dij1i2.wl%bowie@nrik.jp> Message-ID: <200902160835.55330.hselasky@c2i.net> On Monday 16 February 2009, Noriyoshi Kawano wrote: > At Sat, 14 Feb 2009 10:36:53 +0100, > > Hans Petter Selasky wrote: > > Hi, > > > > As long as you don't see ugenX.Y attach/detach messages, it means that > > the Apcupsd daemon is doing something. Probably it is the > > "usb_link_check()" procedure that is executing and the connection is > > reset by the following code: > > > > if (my_data->fd) { > > usb_reset(my_data->fd); > > /* XXX: usb_close() not needed according to libusb0.1 refdocs */ > > usb_close(my_data->fd); > > > > Could you enable debugging in Apcupsd ? > > > > What speed is your device reported like by usbconfig ? > > > > --HPS > > Hi, > > I enabled debugging in apcupsd. > > Because the "usb_interrupt_read()" becomes the error, > the "usb_link_check()" is called. > > # apcupsd -d 500 > --- snip --- > 61.689 apcupsd: generic-usb.c:538 Timeout=539 > 62.232 apcupsd: generic-usb.c:549 usb_interrupt_read error: (-1) Operation > not permitted 62.232 apcupsd: generic-usb.c:458 link_check comm lost > 68.538 apcupsd: generic-usb.c:300 Reinitializing private structure. > 68.539 apcupsd: generic-usb.c:398 Initializing libusb > 68.539 apcupsd: generic-usb.c:403 Found 0 USB busses > 68.539 apcupsd: generic-usb.c:405 Found 0 USB devices > 68.539 apcupsd: generic-usb.c:416 /dev/usb:/dev/ugen3.2 - 0000:0000 > 68.539 apcupsd: generic-usb.c:416 /dev/usb:/dev/ugen0.2 - 051d:0002 > --- snip --- > > # usbconfig -u 0 -a 2 > ugen0.2: at > usbus0, cfg=0 md=HOST spd=LOW (1.5Mbps) pwr=ON Does ugen0.2 have the correct permissions? usbconfig -u 0 -a 2 set_owner xxx:yyy set_perm 0660 --HPS From bowie at nrik.jp Mon Feb 16 00:10:16 2009 From: bowie at nrik.jp (Noriyoshi Kawano) Date: Mon Feb 16 00:10:32 2009 Subject: USB2 & apcupsd In-Reply-To: <200902160835.55330.hselasky@c2i.net> References: <86y6wbf2nc.wl%bowie@nrik.jp> <200902141036.54246.hselasky@c2i.net> <86d4dij1i2.wl%bowie@nrik.jp> <200902160835.55330.hselasky@c2i.net> Message-ID: <86ab8mree6.wl%bowie@nrik.jp> At Mon, 16 Feb 2009 08:35:54 +0100, Hans Petter Selasky wrote: > > On Monday 16 February 2009, Noriyoshi Kawano wrote: > > At Sat, 14 Feb 2009 10:36:53 +0100, > > > > Hans Petter Selasky wrote: > > > Hi, > > > > > > As long as you don't see ugenX.Y attach/detach messages, it means that > > > the Apcupsd daemon is doing something. Probably it is the > > > "usb_link_check()" procedure that is executing and the connection is > > > reset by the following code: > > > > > > if (my_data->fd) { > > > usb_reset(my_data->fd); > > > /* XXX: usb_close() not needed according to libusb0.1 refdocs */ > > > usb_close(my_data->fd); > > > > > > Could you enable debugging in Apcupsd ? > > > > > > What speed is your device reported like by usbconfig ? > > > > > > --HPS > > > > Hi, > > > > I enabled debugging in apcupsd. > > > > Because the "usb_interrupt_read()" becomes the error, > > the "usb_link_check()" is called. > > > > # apcupsd -d 500 > > --- snip --- > > 61.689 apcupsd: generic-usb.c:538 Timeout=539 > > 62.232 apcupsd: generic-usb.c:549 usb_interrupt_read error: (-1) Operation > > not permitted 62.232 apcupsd: generic-usb.c:458 link_check comm lost > > 68.538 apcupsd: generic-usb.c:300 Reinitializing private structure. > > 68.539 apcupsd: generic-usb.c:398 Initializing libusb > > 68.539 apcupsd: generic-usb.c:403 Found 0 USB busses > > 68.539 apcupsd: generic-usb.c:405 Found 0 USB devices > > 68.539 apcupsd: generic-usb.c:416 /dev/usb:/dev/ugen3.2 - 0000:0000 > > 68.539 apcupsd: generic-usb.c:416 /dev/usb:/dev/ugen0.2 - 051d:0002 > > --- snip --- > > > > # usbconfig -u 0 -a 2 > > ugen0.2: at > > usbus0, cfg=0 md=HOST spd=LOW (1.5Mbps) pwr=ON > > Does ugen0.2 have the correct permissions? > > usbconfig -u 0 -a 2 set_owner xxx:yyy set_perm 0660 > > --HPS I think that ugen0.2 have the correct permissions. Of course, I tried to set permissions. # usbconfig -u 0 -a 2 set_owner root:wheel set_perm 0660 But the result was the same. The "usb_interrupt_read()" is executed many time, and the most succeed. The "usb_interrupt_read()" is executed it after indication "generic-usb.c:538 Timeout=xxxxx". See attached log file and follow codes. ---- genric-usb.c ---- 538 Dmsg1(200, "Timeout=%d\n", timeout); 539 retval = usb_interrupt_read(my_data->fd, USB_ENDPOINT_IN|1, (char*)buf, sizeof(buf), timeout); 540 541 if (retval == 0 || retval == -LIBUSB_ETIMEDOUT) { 542 /* No events available in ups->wait_time seconds. */ 543 return 0; 544 } else if (retval == -EINTR || retval == -EAGAIN) { 545 /* assume SIGCHLD */ 546 continue; 547 } else if (retval < 0) { 548 /* Hard error */ 549 Dmsg2(200, "usb_interrupt_read error: (%d) %s\n", retval, strer ror(-retval)); 550 usb_link_check(ups); /* link is down, wait */ 551 return 0; 552 } 553 554 if (debug_level >= 300) { 555 logf("Interrupt data: "); 556 for (i = 0; i < retval; i++) 557 logf("%02x, ", buf[i]); 558 logf("\n"); 559 } ---- generic-usb.c ---- Noriyoshi Kawano From bowie at nrik.jp Mon Feb 16 00:13:56 2009 From: bowie at nrik.jp (Noriyoshi Kawano) Date: Mon Feb 16 00:14:06 2009 Subject: USB2 & apcupsd In-Reply-To: <86ab8mree6.wl%bowie@nrik.jp> References: <86y6wbf2nc.wl%bowie@nrik.jp> <200902141036.54246.hselasky@c2i.net> <86d4dij1i2.wl%bowie@nrik.jp> <200902160835.55330.hselasky@c2i.net> <86ab8mree6.wl%bowie@nrik.jp> Message-ID: <868wo6re81.wl%bowie@nrik.jp> At Mon, 16 Feb 2009 17:10:09 +0900, Noriyoshi Kawano wrote: > > At Mon, 16 Feb 2009 08:35:54 +0100, > Hans Petter Selasky wrote: > > > > On Monday 16 February 2009, Noriyoshi Kawano wrote: > > > At Sat, 14 Feb 2009 10:36:53 +0100, > > > > > > Hans Petter Selasky wrote: > > > > Hi, > > > > > > > > As long as you don't see ugenX.Y attach/detach messages, it means that > > > > the Apcupsd daemon is doing something. Probably it is the > > > > "usb_link_check()" procedure that is executing and the connection is > > > > reset by the following code: > > > > > > > > if (my_data->fd) { > > > > usb_reset(my_data->fd); > > > > /* XXX: usb_close() not needed according to libusb0.1 refdocs */ > > > > usb_close(my_data->fd); > > > > > > > > Could you enable debugging in Apcupsd ? > > > > > > > > What speed is your device reported like by usbconfig ? > > > > > > > > --HPS > > > > > > Hi, > > > > > > I enabled debugging in apcupsd. > > > > > > Because the "usb_interrupt_read()" becomes the error, > > > the "usb_link_check()" is called. > > > > > > # apcupsd -d 500 > > > --- snip --- > > > 61.689 apcupsd: generic-usb.c:538 Timeout=539 > > > 62.232 apcupsd: generic-usb.c:549 usb_interrupt_read error: (-1) Operation > > > not permitted 62.232 apcupsd: generic-usb.c:458 link_check comm lost > > > 68.538 apcupsd: generic-usb.c:300 Reinitializing private structure. > > > 68.539 apcupsd: generic-usb.c:398 Initializing libusb > > > 68.539 apcupsd: generic-usb.c:403 Found 0 USB busses > > > 68.539 apcupsd: generic-usb.c:405 Found 0 USB devices > > > 68.539 apcupsd: generic-usb.c:416 /dev/usb:/dev/ugen3.2 - 0000:0000 > > > 68.539 apcupsd: generic-usb.c:416 /dev/usb:/dev/ugen0.2 - 051d:0002 > > > --- snip --- > > > > > > # usbconfig -u 0 -a 2 > > > ugen0.2: at > > > usbus0, cfg=0 md=HOST spd=LOW (1.5Mbps) pwr=ON > > > > Does ugen0.2 have the correct permissions? > > > > usbconfig -u 0 -a 2 set_owner xxx:yyy set_perm 0660 > > > > --HPS > > I think that ugen0.2 have the correct permissions. > > Of course, I tried to set permissions. > > # usbconfig -u 0 -a 2 set_owner root:wheel set_perm 0660 > > But the result was the same. > > The "usb_interrupt_read()" is executed many time, and the most succeed. > The "usb_interrupt_read()" is executed it after indication > "generic-usb.c:538 Timeout=xxxxx". See attached log file and follow codes. > > ---- genric-usb.c ---- > 538 Dmsg1(200, "Timeout=%d\n", timeout); > 539 retval = usb_interrupt_read(my_data->fd, USB_ENDPOINT_IN|1, (char*)buf, sizeof(buf), timeout); > 540 > 541 if (retval == 0 || retval == -LIBUSB_ETIMEDOUT) { > 542 /* No events available in ups->wait_time seconds. */ > 543 return 0; > 544 } else if (retval == -EINTR || retval == -EAGAIN) { > 545 /* assume SIGCHLD */ > 546 continue; > 547 } else if (retval < 0) { > 548 /* Hard error */ > 549 Dmsg2(200, "usb_interrupt_read error: (%d) %s\n", retval, strer > ror(-retval)); > 550 usb_link_check(ups); /* link is down, wait */ > 551 return 0; > 552 } > 553 > 554 if (debug_level >= 300) { > 555 logf("Interrupt data: "); > 556 for (i = 0; i < retval; i++) > 557 logf("%02x, ", buf[i]); > 558 logf("\n"); > 559 } > ---- generic-usb.c ---- > > Noriyoshi Kawano I'm sorry. I did not attach a log file. -------------- next part -------------- 0.000 apcupsd: apcupsd.c:219 Options parsed. 0.000 apcupsd: apcconfig.c:803 After config scriptdir: "/usr/local/etc/apcupsd" 0.000 apcupsd: apcconfig.c:804 After config pwrfailpath: "/var/run" 0.000 apcupsd: apcconfig.c:805 After config nologinpath: "/var/run" 0.000 apcupsd: apcupsd.c:242 Config file /usr/local/etc/apcupsd/apcupsd.conf processed. 0.000 apcupsd: newups.c:102 write_lock at drivers.c:181 0.000 apcupsd: drivers.c:183 Looking for driver: usb 0.000 apcupsd: drivers.c:187 Driver dumb is configured. 0.000 apcupsd: drivers.c:187 Driver apcsmart is configured. 0.000 apcupsd: drivers.c:187 Driver net is configured. 0.000 apcupsd: drivers.c:187 Driver usb is configured. 0.000 apcupsd: drivers.c:190 Driver usb found and attached. 0.000 apcupsd: newups.c:108 write_unlock at drivers.c:207 0.000 apcupsd: drivers.c:209 Driver ptr=0x438768 0.000 apcupsd: apcupsd.c:261 Attached to driver: usb 0.011 apcupsd: newups.c:102 write_lock at generic-usb.c:614 0.011 apcupsd: generic-usb.c:398 Initializing libusb 0.011 apcupsd: generic-usb.c:403 Found 0 USB busses 0.012 apcupsd: generic-usb.c:405 Found 0 USB devices 0.012 apcupsd: generic-usb.c:416 /dev/usb:/dev/ugen3.2 - 0000:0000 0.012 apcupsd: generic-usb.c:416 /dev/usb:/dev/ugen0.2 - 051d:0002 0.012 apcupsd: generic-usb.c:419 Trying device /dev/usb:/dev/ugen0.2 Report descriptor (length=840): 05, 84, 09, 04, a1, 01, 09, 24, a1, 00, 85, 01, 09, fe, 79, 01, 75, 08, 95, 01, 15, 00, 26, ff, 00, b1, 22, 85, 02, 09, ff, 79, 02, b1, 22, 85, 03, 05, 85, 09, 89, 79, 04, b1, 22, 85, 04, 09, 8f, 79, 03, b1, 22, 85, 05, 09, 8b, b1, 22, 85, 06, 06, 86, ff, 09, 60, 81, a2, 09, 60, b1, a2, 85, 07, 05, 85, 09, 85, 75, 10, 27, ff, ff, 00, 00, b1, a2, 85, 08, 05, 84, 09, 40, 67, 21, d1, f0, 00, 55, 05, b1, 22, 85, 09, 09, 30, b1, a2, 85, 0a, 09, fd, 75, 08, 26, ff, 00, 65, 00, 55, 00, 79, 03, b1, 22, 85, 0b, 05, 85, 09, 2c, b1, 22, 85, 0c, 09, 66, 25, 64, 81, a2, 09, 66, b1, a2, 09, 68, 75, 10, 27, ff, ff, 00, 00, 66, 01, 10, 81, a2, 09, 68, b1, a2, 85, 0d, 09, 83, 75, 08, 25, 64, 65, 00, b1, 22, 85, 0e, 09, 67, b1, 22, 85, 0f, 09, 8c, b1, 22, 85, 10, 09, 8e, b1, 22, 85, 11, 09, 29, 15, 01, b1, a2, 85, 12, 09, 8d, 15, 00, b1, 22, 05, 84, 09, 02, a1, 02, 85, 16, 05, 85, 75, 01, 25, 01, 09, 44, 81, a2, 09, 44, b1, a2, 09, 45, 81, a2, 09, 45, b1, a2, 09, d0, 81, a2, 09, d0, b1, a2, 09, d1, 81, a2, 09, d1, b1, a2, 09, 42, 81, a2, 09, 42, b1, a2, 05, 84, 09, 69, 81, a2, 09, 69, b1, a2, 05, 85, 09, 43, 81, a2, 09, 43, b1, a2, 09, 4b, 81, a2, 09, 4b, b1, a2, 05, 84, 09, 65, 81, a2, 09, 65, b1, a2, 95, 17, 81, 01, b1, 01, c0, 85, 17, 05, 85, 09, 2a, 95, 01, 75, 10, 27, ff, ff, 00, 00, 66, 01, 10, b1, a2, 85, 18, 05, 84, 09, 5a, 75, 08, 15, 01, 25, 03, 65, 00, b1, a2, c0, 09, 12, a1, 00, 85, 1c, 06, 86, ff, 09, 16, 75, 18, 15, 00, 27, ff, ff, ff, 00, b2, a2, 01, 85, 20, 05, 85, 09, 85, 75, 10, 27, ff, ff, 00, 00, b1, a2, 85, 22, 09, 66, 75, 08, 25, 64, b1, a2, 85, 23, 09, 68, 75, 10, 27, ff, ff, 00, 00, 66, 01, 10, b1, a2, 85, 24, 09, 2a, b1, a2, 85, 25, 05, 84, 09, 40, 67, 21, d1, f0, 00, 55, 05, b1, 22, 85, 26, 09, 30, b1, a2, 85, 27, 06, 86, ff, 09, 24, 75, 08, 16, e8, 00, 26, fe, 00, 65, 00, 55, 00, b1, a2, 85, 28, 09, 18, 75, 20, 17, 01, 00, 00, 80, 27, ff, ff, ff, 7f, b2, a2, 01, c0, 05, 84, 09, 1a, a1, 00, 85, 30, 05, 84, 09, 40, 75, 08, 15, 00, 26, ff, 00, 67, 21, d1, f0, 00, 55, 07, b1, 22, 85, 31, 09, 30, b1, a2, 85, 32, 09, 53, 15, 57, 25, 5d, b1, a2, 85, 33, 09, 54, 15, 6b, 26, 71, 00, b1, a2, 85, 34, 06, 86, ff, 09, 24, 16, aa, 00, 26, fe, 00, 65, 00, 55, 00, b1, a2, 85, 35, 09, 61, 15, 00, 25, 02, b1, a2, 85, 36, 09, 52, 25, 0d, b1, a2, c0, 09, 05, a1, 00, 85, 40, 09, 7c, 25, 01, b1, a2, 85, 41, 09, 7d, 75, 10, 16, ff, ff, 26, ff, 7f, 66, 01, 10, b1, a2, c0, 05, 84, 09, 16, a1, 00, 85, 50, 09, 35, 75, 08, 15, 00, 25, 64, 65, 00, b1, a2, 85, 51, 06, 86, ff, 09, 24, 16, 6d, 00, 26, b8, 00, b1, a2, c0, 06, 86, ff, 09, 01, a1, 00, 85, 60, 09, 23, 75, 10, 15, 00, 27, ff, ff, 00, 00, b1, a2, 85, 61, 09, 26, 75, 08, 15, 84, 25, 8c, b1, a2, 85, 62, 09, 25, 75, 20, 17, 01, 00, 00, 80, 27, ff, ff, ff, 7f, b2, a2, 01, c0, 85, 7f, 05, 84, 09, fe, 79, 05, 75, 08, 95, 01, 15, 00, 26, ff, 00, b1, 22, 85, 7e, 06, 86, ff, 09, 42, 79, 06, b1, 22, 85, 7d, 05, 84, 09, ff, 79, 02, b1, 22, 85, 7c, 09, fd, 79, 03, b1, 22, 85, 7b, 05, 85, 09, 85, 75, 10, 27, ff, ff, 00, 00, b1, a2, 05, 84, 09, 02, a1, 02, 85, 7a, 05, 85, 09, 44, 75, 01, 25, 01, b1, a2, 09, 45, b1, a2, 09, d0, b1, a2, 09, d1, b1, a2, 09, 42, b1, a2, 05, 84, 09, 69, b1, a2, 05, 85, 09, 43, b1, a2, 09, 4b, b1, a2, 05, 84, 09, 65, b1, a2, 95, 17, b1, 01, c0, 85, 79, 06, 86, ff, 09, 72, 75, 08, 95, 01, b1, a2, 85, 78, 05, 84, 09, 5a, 15, 01, 25, 03, b1, a2, c0, 0.159 apcupsd: newups.c:108 write_unlock at generic-usb.c:649 0.159 apcupsd: newups.c:102 write_lock at generic-usb.c:69 0.159 apcupsd: generic-usb.c:129 Got READ ci=5, rpt=49 (len=2), usage=0x840030 (len=8), kind=0x02 0.159 apcupsd: generic-usb.c:136 Got WRITE ci=5, rpt=49 (len=2), usage=0x840030 (len=8), kind=0x02 0.159 apcupsd: generic-usb.c:129 Got READ ci=10, rpt=38 (len=3), usage=0x840030 (len=16), kind=0x02 0.159 apcupsd: generic-usb.c:136 Got WRITE ci=10, rpt=38 (len=3), usage=0x840030 (len=16), kind=0x02 0.159 apcupsd: generic-usb.c:129 Got READ ci=11, rpt=80 (len=2), usage=0x840035 (len=8), kind=0x02 0.159 apcupsd: generic-usb.c:136 Got WRITE ci=11, rpt=80 (len=2), usage=0x840035 (len=8), kind=0x02 0.160 apcupsd: generic-usb.c:129 Got READ ci=29, rpt=37 (len=3), usage=0x840040 (len=16), kind=0x02 0.160 apcupsd: generic-usb.c:136 Got WRITE ci=29, rpt=37 (len=3), usage=0x840040 (len=16), kind=0x02 0.160 apcupsd: generic-usb.c:129 Got READ ci=66, rpt=48 (len=2), usage=0x840040 (len=8), kind=0x02 0.160 apcupsd: generic-usb.c:136 Got WRITE ci=66, rpt=48 (len=2), usage=0x840040 (len=8), kind=0x02 0.160 apcupsd: generic-usb.c:129 Got READ ci=19, rpt=50 (len=2), usage=0x840053 (len=8), kind=0x02 0.160 apcupsd: generic-usb.c:136 Got WRITE ci=19, rpt=50 (len=2), usage=0x840053 (len=8), kind=0x02 0.160 apcupsd: generic-usb.c:129 Got READ ci=20, rpt=51 (len=2), usage=0x840054 (len=8), kind=0x02 0.160 apcupsd: generic-usb.c:136 Got WRITE ci=20, rpt=51 (len=2), usage=0x840054 (len=8), kind=0x02 0.160 apcupsd: generic-usb.c:129 Got READ ci=22, rpt=24 (len=2), usage=0x84005a (len=8), kind=0x02 0.160 apcupsd: generic-usb.c:136 Got WRITE ci=22, rpt=24 (len=2), usage=0x84005a (len=8), kind=0x02 0.160 apcupsd: generic-usb.c:129 Got READ ci=58, rpt=22 (len=5), usage=0x840065 (len=1), kind=0x00 0.160 apcupsd: generic-usb.c:136 Got WRITE ci=58, rpt=22 (len=5), usage=0x840065 (len=1), kind=0x02 0.161 apcupsd: generic-usb.c:129 Got READ ci=43, rpt=22 (len=5), usage=0x840069 (len=1), kind=0x00 0.161 apcupsd: generic-usb.c:136 Got WRITE ci=43, rpt=22 (len=5), usage=0x840069 (len=1), kind=0x02 0.161 apcupsd: generic-usb.c:129 Got READ ci=41, rpt=10 (len=2), usage=0x8400fd (len=8), kind=0x02 0.161 apcupsd: generic-usb.c:136 Got WRITE ci=41, rpt=10 (len=2), usage=0x8400fd (len=8), kind=0x02 0.161 apcupsd: generic-usb.c:129 Got READ ci=0, rpt=1 (len=2), usage=0x8400fe (len=8), kind=0x02 0.161 apcupsd: generic-usb.c:136 Got WRITE ci=0, rpt=1 (len=2), usage=0x8400fe (len=8), kind=0x02 0.161 apcupsd: generic-usb.c:129 Got READ ci=27, rpt=2 (len=2), usage=0x8400ff (len=8), kind=0x02 0.161 apcupsd: generic-usb.c:136 Got WRITE ci=27, rpt=2 (len=2), usage=0x8400ff (len=8), kind=0x02 0.161 apcupsd: generic-usb.c:129 Got READ ci=26, rpt=7 (len=3), usage=0x850085 (len=16), kind=0x02 0.161 apcupsd: generic-usb.c:136 Got WRITE ci=26, rpt=7 (len=3), usage=0x850085 (len=16), kind=0x02 0.161 apcupsd: generic-usb.c:129 Got READ ci=49, rpt=17 (len=2), usage=0x850029 (len=8), kind=0x02 0.161 apcupsd: generic-usb.c:136 Got WRITE ci=49, rpt=17 (len=2), usage=0x850029 (len=8), kind=0x02 0.161 apcupsd: generic-usb.c:129 Got READ ci=50, rpt=23 (len=3), usage=0x85002a (len=16), kind=0x02 0.161 apcupsd: generic-usb.c:136 Got WRITE ci=50, rpt=23 (len=3), usage=0x85002a (len=16), kind=0x02 0.161 apcupsd: generic-usb.c:129 Got READ ci=45, rpt=22 (len=5), usage=0x850042 (len=1), kind=0x00 0.161 apcupsd: generic-usb.c:136 Got WRITE ci=45, rpt=22 (len=5), usage=0x850042 (len=1), kind=0x02 0.161 apcupsd: generic-usb.c:129 Got READ ci=46, rpt=22 (len=5), usage=0x850043 (len=1), kind=0x00 0.161 apcupsd: generic-usb.c:136 Got WRITE ci=46, rpt=22 (len=5), usage=0x850043 (len=1), kind=0x02 0.161 apcupsd: generic-usb.c:129 Got READ ci=47, rpt=22 (len=5), usage=0x850044 (len=1), kind=0x00 0.161 apcupsd: generic-usb.c:136 Got WRITE ci=47, rpt=22 (len=5), usage=0x850044 (len=1), kind=0x02 0.162 apcupsd: generic-usb.c:129 Got READ ci=48, rpt=22 (len=5), usage=0x850045 (len=1), kind=0x00 0.162 apcupsd: generic-usb.c:136 Got WRITE ci=48, rpt=22 (len=5), usage=0x850045 (len=1), kind=0x02 0.162 apcupsd: generic-usb.c:129 Got READ ci=59, rpt=22 (len=5), usage=0x85004b (len=1), kind=0x00 0.162 apcupsd: generic-usb.c:136 Got WRITE ci=59, rpt=22 (len=5), usage=0x85004b (len=1), kind=0x02 0.162 apcupsd: generic-usb.c:129 Got READ ci=9, rpt=12 (len=4), usage=0x850066 (len=8), kind=0x00 0.162 apcupsd: generic-usb.c:136 Got WRITE ci=9, rpt=12 (len=4), usage=0x850066 (len=8), kind=0x02 0.162 apcupsd: generic-usb.c:129 Got READ ci=13, rpt=12 (len=4), usage=0x850068 (len=16), kind=0x00 0.162 apcupsd: generic-usb.c:136 Got WRITE ci=13, rpt=12 (len=4), usage=0x850068 (len=16), kind=0x02 0.162 apcupsd: generic-usb.c:129 Got READ ci=28, rpt=32 (len=3), usage=0x850085 (len=16), kind=0x02 0.162 apcupsd: generic-usb.c:136 Got WRITE ci=28, rpt=32 (len=3), usage=0x850085 (len=16), kind=0x02 0.162 apcupsd: generic-usb.c:129 Got READ ci=51, rpt=15 (len=2), usage=0x85008c (len=8), kind=0x02 0.162 apcupsd: generic-usb.c:136 Got WRITE ci=51, rpt=15 (len=2), usage=0x85008c (len=8), kind=0x02 0.162 apcupsd: generic-usb.c:129 Got READ ci=55, rpt=22 (len=5), usage=0x8500d0 (len=1), kind=0x00 0.162 apcupsd: generic-usb.c:136 Got WRITE ci=55, rpt=22 (len=5), usage=0x8500d0 (len=1), kind=0x02 0.162 apcupsd: generic-usb.c:129 Got READ ci=82, rpt=22 (len=5), usage=0x8500d1 (len=1), kind=0x00 0.162 apcupsd: generic-usb.c:136 Got WRITE ci=82, rpt=22 (len=5), usage=0x8500d1 (len=1), kind=0x02 0.162 apcupsd: generic-usb.c:129 Got READ ci=1, rpt=6 (len=2), usage=0xff860060 (len=8), kind=0x00 0.162 apcupsd: generic-usb.c:136 Got WRITE ci=1, rpt=6 (len=2), usage=0xff860060 (len=8), kind=0x02 0.163 apcupsd: generic-usb.c:129 Got READ ci=61, rpt=64 (len=2), usage=0xff86007c (len=8), kind=0x02 0.163 apcupsd: generic-usb.c:136 Got WRITE ci=61, rpt=64 (len=2), usage=0xff86007c (len=8), kind=0x02 0.163 apcupsd: generic-usb.c:129 Got READ ci=60, rpt=28 (len=4), usage=0xff860016 (len=24), kind=0x02 0.163 apcupsd: generic-usb.c:136 Got WRITE ci=60, rpt=28 (len=4), usage=0xff860016 (len=24), kind=0x02 0.163 apcupsd: generic-usb.c:129 Got READ ci=64, rpt=65 (len=3), usage=0xff86007d (len=16), kind=0x02 0.163 apcupsd: generic-usb.c:136 Got WRITE ci=64, rpt=65 (len=3), usage=0xff86007d (len=16), kind=0x02 0.163 apcupsd: generic-usb.c:129 Got READ ci=65, rpt=54 (len=2), usage=0xff860052 (len=8), kind=0x02 0.163 apcupsd: generic-usb.c:136 Got WRITE ci=65, rpt=54 (len=2), usage=0xff860052 (len=8), kind=0x02 0.163 apcupsd: generic-usb.c:129 Got READ ci=16, rpt=53 (len=2), usage=0xff860061 (len=8), kind=0x02 0.163 apcupsd: generic-usb.c:136 Got WRITE ci=16, rpt=53 (len=2), usage=0xff860061 (len=8), kind=0x02 0.163 apcupsd: newups.c:108 write_unlock at generic-usb.c:142 0.163 apcupsd: hidutils.c:203 get_report: id=0x01, kind=2, length=2 pos=0 01: 01,01, 0.189 apcupsd: hidutils.c:273 Got string of length=34 0.189 apcupsd: generic-usb.c:172 Def val=1 exp=0 sVal="APC ES 725 FW:821.y2 .A USB FW:y2 " ci=0 0.189 apcupsd: usb.c:302 Checking for BackUPS Pro quirk "APC ES 725 FW:821.y2 .A USB FW:y2 " 0.189 apcupsd: newups.c:102 write_lock at usb.c:864 0.189 apcupsd: hidutils.c:203 get_report: id=0x25, kind=2, length=3 pos=0 25: 25,b0,04, 0.192 apcupsd: generic-usb.c:222 Def val=1200 exp=-2 dVal=12.000000 ci=29 0.234 apcupsd: hidutils.c:203 get_report: id=0x30, kind=2, length=2 pos=0 30: 30,64, 0.237 apcupsd: generic-usb.c:222 Def val=100 exp=0 dVal=100.000000 ci=66 0.280 apcupsd: hidutils.c:203 get_report: id=0x32, kind=2, length=2 pos=0 32: 32,5a, 0.284 apcupsd: generic-usb.c:222 Def val=90 exp=0 dVal=90.000000 ci=19 0.303 apcupsd: hidutils.c:203 get_report: id=0x33, kind=2, length=2 pos=0 33: 33,6e, 0.305 apcupsd: generic-usb.c:222 Def val=110 exp=0 dVal=110.000000 ci=20 0.576 apcupsd: hidutils.c:203 get_report: id=0x0a, kind=2, length=2 pos=0 0a: 0a,03, 0.592 apcupsd: hidutils.c:273 Got string of length=3 0.592 apcupsd: generic-usb.c:172 Def val=3 exp=0 sVal="APC" ci=41 0.598 apcupsd: hidutils.c:203 get_report: id=0x01, kind=2, length=2 pos=0 01: 01,01, 0.627 apcupsd: hidutils.c:273 Got string of length=34 0.627 apcupsd: generic-usb.c:172 Def val=1 exp=0 sVal="APC ES 725 FW:821.y2 .A USB FW:y2 " ci=0 0.627 apcupsd: hidutils.c:203 get_report: id=0x02, kind=2, length=2 pos=0 02: 02,02, 0.649 apcupsd: hidutils.c:273 Got string of length=14 0.649 apcupsd: generic-usb.c:172 Def val=2 exp=0 sVal="3B0634X51015 " ci=27 0.649 apcupsd: hidutils.c:203 get_report: id=0x07, kind=2, length=3 pos=0 07: 07,12,35, 0.652 apcupsd: generic-usb.c:235 Def val=13586 exp=0 dVal=13586.000000 ci=26 0.672 apcupsd: hidutils.c:203 get_report: id=0x11, kind=2, length=2 pos=0 11: 11,0a, 0.674 apcupsd: generic-usb.c:235 Def val=10 exp=0 dVal=10.000000 ci=49 0.694 apcupsd: hidutils.c:203 get_report: id=0x17, kind=2, length=3 pos=0 17: 17,78,00, 0.697 apcupsd: generic-usb.c:222 Def val=120 exp=0 dVal=120.000000 ci=50 0.717 apcupsd: hidutils.c:203 get_report: id=0x16, kind=0, length=5 pos=0 16: 16,0c,00,00,00, 0.721 apcupsd: generic-usb.c:235 Def val=0 exp=0 dVal=0.000000 ci=47 0.786 apcupsd: hidutils.c:203 get_report: id=0x20, kind=2, length=3 pos=0 20: 20,56,36, 0.789 apcupsd: generic-usb.c:235 Def val=13910 exp=0 dVal=13910.000000 ci=28 0.831 apcupsd: hidutils.c:203 get_report: id=0x0f, kind=2, length=2 pos=0 0f: 0f,32, 0.834 apcupsd: generic-usb.c:235 Def val=50 exp=0 dVal=50.000000 ci=51 0.968 apcupsd: hidutils.c:203 get_report: id=0x40, kind=2, length=2 pos=0 40: 40,00, 0.972 apcupsd: generic-usb.c:235 Def val=0 exp=0 dVal=0.000000 ci=61 0.991 apcupsd: hidutils.c:203 get_report: id=0x1c, kind=2, length=4 pos=0 1c: 1c,00,00,00, 0.994 apcupsd: generic-usb.c:235 Def val=0 exp=0 dVal=0.000000 ci=60 1.059 apcupsd: hidutils.c:203 get_report: id=0x41, kind=2, length=3 pos=0 41: 41,ff,ff, 1.064 apcupsd: generic-usb.c:222 Def val=-1 exp=0 dVal=-1.000000 ci=64 1.082 apcupsd: hidutils.c:203 get_report: id=0x35, kind=2, length=2 pos=0 35: 35,02, 1.084 apcupsd: generic-usb.c:235 Def val=2 exp=0 dVal=2.000000 ci=16 1.173 apcupsd: newups.c:108 write_unlock at usb.c:872 1.173 apcupsd: apcupsd.c:310 NIS thread started. 1.173 apcupsd: apclog.c:42 apcupsd 3.14.4 (18 May 2008) freebsd startup succeeded 1.173 apcupsd: usb.c:828 Enter usb_ups_read_volatile_data 1.173 apcupsd: newups.c:102 write_lock at usb.c:840 1.173 apcupsd: apclog.c:42 NIS server startup succeeded 1.196 apcupsd: hidutils.c:203 get_report: id=0x31, kind=2, length=2 pos=0 31: 31,65, 1.199 apcupsd: generic-usb.c:222 Def val=101 exp=0 dVal=101.000000 ci=5 1.199 apcupsd: usb.c:468 LineVoltage = 101 1.242 apcupsd: hidutils.c:203 get_report: id=0x26, kind=2, length=3 pos=0 26: 26,4f,05, 1.245 apcupsd: generic-usb.c:222 Def val=1359 exp=-2 dVal=13.590000 ci=10 1.245 apcupsd: usb.c:486 BattVoltage = 13 1.288 apcupsd: hidutils.c:203 get_report: id=0x50, kind=2, length=2 pos=0 50: 50,12, 1.290 apcupsd: generic-usb.c:222 Def val=18 exp=0 dVal=18.000000 ci=11 1.290 apcupsd: usb.c:492 UPSLoad = 18 1.379 apcupsd: hidutils.c:203 get_report: id=0x18, kind=2, length=2 pos=0 18: 18,02, 1.383 apcupsd: generic-usb.c:235 Def val=2 exp=0 dVal=2.000000 ci=22 1.402 apcupsd: hidutils.c:203 get_report: id=0x16, kind=0, length=5 pos=8 16: 16,0c,00,00,00, 1.405 apcupsd: generic-usb.c:235 Def val=0 exp=0 dVal=0.000000 ci=58 1.405 apcupsd: usb.c:456 Overload=0 1.425 apcupsd: hidutils.c:203 get_report: id=0x16, kind=0, length=5 pos=5 16: 16,0c,00,00,00, 1.428 apcupsd: generic-usb.c:235 Def val=0 exp=0 dVal=0.000000 ci=43 1.428 apcupsd: usb.c:438 ShutdownImminent=0 1.492 apcupsd: hidutils.c:203 get_report: id=0x16, kind=0, length=5 pos=4 16: 16,0c,00,00,00, 1.495 apcupsd: generic-usb.c:235 Def val=0 exp=0 dVal=0.000000 ci=45 1.495 apcupsd: usb.c:426 BelowRemCapLimit=0 1.515 apcupsd: hidutils.c:203 get_report: id=0x16, kind=0, length=5 pos=6 16: 16,0c,00,00,00, 1.518 apcupsd: generic-usb.c:235 Def val=0 exp=0 dVal=0.000000 ci=46 1.518 apcupsd: usb.c:432 RemTimeLimitExpired=0 1.538 apcupsd: hidutils.c:203 get_report: id=0x16, kind=0, length=5 pos=1 16: 16,0c,00,00,00, 1.541 apcupsd: generic-usb.c:235 Def val=0 exp=0 dVal=0.000000 ci=48 1.541 apcupsd: usb.c:420 Discharging=0 1.561 apcupsd: hidutils.c:203 get_report: id=0x16, kind=0, length=5 pos=7 16: 16,0c,00,00,00, 1.563 apcupsd: generic-usb.c:235 Def val=0 exp=0 dVal=0.000000 ci=59 1.563 apcupsd: usb.c:462 ReplaceBatt=0 1.584 apcupsd: hidutils.c:203 get_report: id=0x0c, kind=0, length=4 pos=0 0c: 0c,64,f8,07, 1.586 apcupsd: generic-usb.c:235 Def val=100 exp=0 dVal=100.000000 ci=9 1.586 apcupsd: usb.c:480 BattCharge = 100 1.607 apcupsd: hidutils.c:203 get_report: id=0x0c, kind=0, length=4 pos=8 0c: 0c,64,f8,07, 1.610 apcupsd: generic-usb.c:222 Def val=2040 exp=0 dVal=2040.000000 ci=13 1.610 apcupsd: usb.c:504 TimeLeft = 34 1.653 apcupsd: hidutils.c:203 get_report: id=0x16, kind=0, length=5 pos=3 16: 16,0c,00,00,00, 1.655 apcupsd: generic-usb.c:235 Def val=1 exp=0 dVal=1.000000 ci=82 1.655 apcupsd: usb.c:615 BatteryPresent=1 1.675 apcupsd: hidutils.c:203 get_report: id=0x06, kind=0, length=2 pos=0 06: 06,08, 1.678 apcupsd: generic-usb.c:235 Def val=8 exp=0 dVal=8.000000 ci=1 1.678 apcupsd: usb.c:409 Status=0x07000008 1.698 apcupsd: hidutils.c:203 get_report: id=0x36, kind=2, length=2 pos=0 36: 36,0d, 1.701 apcupsd: generic-usb.c:235 Def val=13 exp=0 dVal=13.000000 ci=65 1.701 apcupsd: usb.c:552 CI_APCLineFailCause=13 1.701 apcupsd: newups.c:108 write_unlock at usb.c:852 1.701 apcupsd: device.c:204 Before do_action: 0x7000008 (OB:0). 1.701 apcupsd: newups.c:102 write_lock at action.c:351 1.701 apcupsd: newups.c:108 write_unlock at action.c:644 1.701 apcupsd: device.c:210 Before fillUPS: 0x7000008 (OB:0). 1.701 apcupsd: usb.c:828 Enter usb_ups_read_volatile_data 1.701 apcupsd: newups.c:102 write_lock at usb.c:840 1.721 apcupsd: hidutils.c:203 get_report: id=0x31, kind=2, length=2 pos=0 31: 31,66, 1.723 apcupsd: generic-usb.c:222 Def val=102 exp=0 dVal=102.000000 ci=5 1.723 apcupsd: usb.c:468 LineVoltage = 102 1.767 apcupsd: hidutils.c:203 get_report: id=0x26, kind=2, length=3 pos=0 26: 26,47,05, 1.770 apcupsd: generic-usb.c:222 Def val=1351 exp=-2 dVal=13.510000 ci=10 1.770 apcupsd: usb.c:486 BattVoltage = 13 1.812 apcupsd: hidutils.c:203 get_report: id=0x50, kind=2, length=2 pos=0 50: 50,12, 1.815 apcupsd: generic-usb.c:222 Def val=18 exp=0 dVal=18.000000 ci=11 1.815 apcupsd: usb.c:492 UPSLoad = 18 1.903 apcupsd: hidutils.c:203 get_report: id=0x18, kind=2, length=2 pos=0 18: 18,02, 1.906 apcupsd: generic-usb.c:235 Def val=2 exp=0 dVal=2.000000 ci=22 1.926 apcupsd: hidutils.c:203 get_report: id=0x16, kind=0, length=5 pos=8 16: 16,0c,00,00,00, 1.929 apcupsd: generic-usb.c:235 Def val=0 exp=0 dVal=0.000000 ci=58 1.929 apcupsd: usb.c:456 Overload=0 1.949 apcupsd: hidutils.c:203 get_report: id=0x16, kind=0, length=5 pos=5 16: 16,0c,00,00,00, 1.953 apcupsd: generic-usb.c:235 Def val=0 exp=0 dVal=0.000000 ci=43 1.953 apcupsd: usb.c:438 ShutdownImminent=0 2.017 apcupsd: hidutils.c:203 get_report: id=0x16, kind=0, length=5 pos=4 16: 16,0c,00,00,00, 2.020 apcupsd: generic-usb.c:235 Def val=0 exp=0 dVal=0.000000 ci=45 2.020 apcupsd: usb.c:426 BelowRemCapLimit=0 2.039 apcupsd: hidutils.c:203 get_report: id=0x16, kind=0, length=5 pos=6 16: 16,0c,00,00,00, 2.042 apcupsd: generic-usb.c:235 Def val=0 exp=0 dVal=0.000000 ci=46 2.042 apcupsd: usb.c:432 RemTimeLimitExpired=0 2.063 apcupsd: hidutils.c:203 get_report: id=0x16, kind=0, length=5 pos=1 16: 16,0c,00,00,00, 2.067 apcupsd: generic-usb.c:235 Def val=0 exp=0 dVal=0.000000 ci=48 2.067 apcupsd: usb.c:420 Discharging=0 2.086 apcupsd: hidutils.c:203 get_report: id=0x16, kind=0, length=5 pos=7 16: 16,0c,00,00,00, 2.089 apcupsd: generic-usb.c:235 Def val=0 exp=0 dVal=0.000000 ci=59 2.089 apcupsd: usb.c:462 ReplaceBatt=0 2.109 apcupsd: hidutils.c:203 get_report: id=0x0c, kind=0, length=4 pos=0 0c: 0c,64,f8,07, 2.112 apcupsd: generic-usb.c:235 Def val=100 exp=0 dVal=100.000000 ci=9 2.112 apcupsd: usb.c:480 BattCharge = 100 2.132 apcupsd: hidutils.c:203 get_report: id=0x0c, kind=0, length=4 pos=8 0c: 0c,64,f8,07, 2.134 apcupsd: generic-usb.c:222 Def val=2040 exp=0 dVal=2040.000000 ci=13 2.134 apcupsd: usb.c:504 TimeLeft = 34 2.177 apcupsd: hidutils.c:203 get_report: id=0x16, kind=0, length=5 pos=3 16: 16,0c,00,00,00, 2.181 apcupsd: generic-usb.c:235 Def val=1 exp=0 dVal=1.000000 ci=82 2.181 apcupsd: usb.c:615 BatteryPresent=1 2.200 apcupsd: hidutils.c:203 get_report: id=0x06, kind=0, length=2 pos=0 06: 06,08, 2.203 apcupsd: generic-usb.c:235 Def val=8 exp=0 dVal=8.000000 ci=1 2.203 apcupsd: usb.c:409 Status=0x07000008 2.223 apcupsd: hidutils.c:203 get_report: id=0x36, kind=2, length=2 pos=0 36: 36,0d, 2.227 apcupsd: generic-usb.c:235 Def val=13 exp=0 dVal=13.000000 ci=65 2.227 apcupsd: usb.c:552 CI_APCLineFailCause=13 2.227 apcupsd: newups.c:108 write_unlock at usb.c:852 2.227 apcupsd: device.c:216 Before do_action: 0x7000008 (OB:0). 2.227 apcupsd: newups.c:102 write_lock at action.c:351 2.227 apcupsd: newups.c:108 write_unlock at action.c:644 2.227 apcupsd: device.c:222 Before do_reports: 0x7000008 (OB:0). 2.227 apcupsd: device.c:230 Before device_check_state: 0x7000008 (OB:0). 2.227 apcupsd: generic-usb.c:538 Timeout=60000 Interrupt data: 06, 08, 2.232 apcupsd: newups.c:102 write_lock at generic-usb.c:561 2.232 apcupsd: generic-usb.c:575 Ignoring unchanged value (ci=1, rpt=6, val=8) 2.232 apcupsd: newups.c:108 write_unlock at generic-usb.c:595 2.232 apcupsd: generic-usb.c:538 Timeout=59996 Interrupt data: 06, 08, 2.240 apcupsd: newups.c:102 write_lock at generic-usb.c:561 2.240 apcupsd: generic-usb.c:575 Ignoring unchanged value (ci=1, rpt=6, val=8) 2.240 apcupsd: newups.c:108 write_unlock at generic-usb.c:595 2.240 apcupsd: generic-usb.c:538 Timeout=59988 Interrupt data: 0c, 64, f8, 07, 2.248 apcupsd: newups.c:102 write_lock at generic-usb.c:561 2.248 apcupsd: generic-usb.c:575 Ignoring unchanged value (ci=9, rpt=12, val=100) 2.248 apcupsd: generic-usb.c:575 Ignoring unchanged value (ci=13, rpt=12, val=2040) 2.248 apcupsd: newups.c:108 write_unlock at generic-usb.c:595 2.248 apcupsd: generic-usb.c:538 Timeout=59980 Interrupt data: 16, 0c, 00, 00, 00, 2.256 apcupsd: newups.c:102 write_lock at generic-usb.c:561 2.256 apcupsd: generic-usb.c:575 Ignoring unchanged value (ci=43, rpt=22, val=0) 2.256 apcupsd: generic-usb.c:575 Ignoring unchanged value (ci=45, rpt=22, val=0) 2.256 apcupsd: generic-usb.c:575 Ignoring unchanged value (ci=46, rpt=22, val=0) 2.256 apcupsd: generic-usb.c:575 Ignoring unchanged value (ci=47, rpt=22, val=0) 2.256 apcupsd: generic-usb.c:575 Ignoring unchanged value (ci=48, rpt=22, val=0) 2.256 apcupsd: generic-usb.c:575 Ignoring unchanged value (ci=58, rpt=22, val=0) 2.256 apcupsd: generic-usb.c:575 Ignoring unchanged value (ci=59, rpt=22, val=0) 2.256 apcupsd: generic-usb.c:575 Ignoring unchanged value (ci=82, rpt=22, val=1) 2.256 apcupsd: newups.c:108 write_unlock at generic-usb.c:595 2.256 apcupsd: generic-usb.c:538 Timeout=59971 Interrupt data: 06, 08, 5.360 apcupsd: newups.c:102 write_lock at generic-usb.c:561 5.360 apcupsd: generic-usb.c:575 Ignoring unchanged value (ci=1, rpt=6, val=8) 5.360 apcupsd: newups.c:108 write_unlock at generic-usb.c:595 5.360 apcupsd: generic-usb.c:538 Timeout=56868 Interrupt data: 0c, 64, f8, 07, 5.368 apcupsd: newups.c:102 write_lock at generic-usb.c:561 5.368 apcupsd: generic-usb.c:575 Ignoring unchanged value (ci=9, rpt=12, val=100) 5.368 apcupsd: generic-usb.c:575 Ignoring unchanged value (ci=13, rpt=12, val=2040) 5.368 apcupsd: newups.c:108 write_unlock at generic-usb.c:595 5.368 apcupsd: generic-usb.c:538 Timeout=56860 Interrupt data: 16, 0c, 00, 00, 00, 5.376 apcupsd: newups.c:102 write_lock at generic-usb.c:561 5.376 apcupsd: generic-usb.c:575 Ignoring unchanged value (ci=43, rpt=22, val=0) 5.376 apcupsd: generic-usb.c:575 Ignoring unchanged value (ci=45, rpt=22, val=0) 5.376 apcupsd: generic-usb.c:575 Ignoring unchanged value (ci=46, rpt=22, val=0) 5.376 apcupsd: generic-usb.c:575 Ignoring unchanged value (ci=47, rpt=22, val=0) 5.376 apcupsd: generic-usb.c:575 Ignoring unchanged value (ci=48, rpt=22, val=0) 5.376 apcupsd: generic-usb.c:575 Ignoring unchanged value (ci=58, rpt=22, val=0) 5.376 apcupsd: generic-usb.c:575 Ignoring unchanged value (ci=59, rpt=22, val=0) 5.376 apcupsd: generic-usb.c:575 Ignoring unchanged value (ci=82, rpt=22, val=1) 5.376 apcupsd: newups.c:108 write_unlock at generic-usb.c:595 5.376 apcupsd: generic-usb.c:538 Timeout=56851 Interrupt data: 06, 08, 10.472 apcupsd: newups.c:102 write_lock at generic-usb.c:561 10.472 apcupsd: generic-usb.c:575 Ignoring unchanged value (ci=1, rpt=6, val=8) 10.472 apcupsd: newups.c:108 write_unlock at generic-usb.c:595 10.472 apcupsd: generic-usb.c:538 Timeout=51755 Interrupt data: 0c, 64, f8, 07, 10.480 apcupsd: newups.c:102 write_lock at generic-usb.c:561 10.480 apcupsd: generic-usb.c:575 Ignoring unchanged value (ci=9, rpt=12, val=100) 10.480 apcupsd: generic-usb.c:575 Ignoring unchanged value (ci=13, rpt=12, val=2040) 10.480 apcupsd: newups.c:108 write_unlock at generic-usb.c:595 10.480 apcupsd: generic-usb.c:538 Timeout=51747 Interrupt data: 16, 0c, 00, 00, 00, 10.488 apcupsd: newups.c:102 write_lock at generic-usb.c:561 10.488 apcupsd: generic-usb.c:575 Ignoring unchanged value (ci=43, rpt=22, val=0) 10.488 apcupsd: generic-usb.c:575 Ignoring unchanged value (ci=45, rpt=22, val=0) 10.488 apcupsd: generic-usb.c:575 Ignoring unchanged value (ci=46, rpt=22, val=0) 10.488 apcupsd: generic-usb.c:575 Ignoring unchanged value (ci=47, rpt=22, val=0) 10.488 apcupsd: generic-usb.c:575 Ignoring unchanged value (ci=48, rpt=22, val=0) 10.488 apcupsd: generic-usb.c:575 Ignoring unchanged value (ci=58, rpt=22, val=0) 10.488 apcupsd: generic-usb.c:575 Ignoring unchanged value (ci=59, rpt=22, val=0) 10.488 apcupsd: generic-usb.c:575 Ignoring unchanged value (ci=82, rpt=22, val=1) 10.488 apcupsd: newups.c:108 write_unlock at generic-usb.c:595 10.488 apcupsd: generic-usb.c:538 Timeout=51739 Interrupt data: 06, 08, 15.592 apcupsd: newups.c:102 write_lock at generic-usb.c:561 15.592 apcupsd: generic-usb.c:575 Ignoring unchanged value (ci=1, rpt=6, val=8) 15.592 apcupsd: newups.c:108 write_unlock at generic-usb.c:595 15.592 apcupsd: generic-usb.c:538 Timeout=46635 Interrupt data: 0c, 64, f8, 07, 15.600 apcupsd: newups.c:102 write_lock at generic-usb.c:561 15.600 apcupsd: generic-usb.c:575 Ignoring unchanged value (ci=9, rpt=12, val=100) 15.600 apcupsd: generic-usb.c:575 Ignoring unchanged value (ci=13, rpt=12, val=2040) 15.600 apcupsd: newups.c:108 write_unlock at generic-usb.c:595 15.600 apcupsd: generic-usb.c:538 Timeout=46627 Interrupt data: 16, 0c, 00, 00, 00, 15.608 apcupsd: newups.c:102 write_lock at generic-usb.c:561 15.608 apcupsd: generic-usb.c:575 Ignoring unchanged value (ci=43, rpt=22, val=0) 15.608 apcupsd: generic-usb.c:575 Ignoring unchanged value (ci=45, rpt=22, val=0) 15.608 apcupsd: generic-usb.c:575 Ignoring unchanged value (ci=46, rpt=22, val=0) 15.608 apcupsd: generic-usb.c:575 Ignoring unchanged value (ci=47, rpt=22, val=0) 15.608 apcupsd: generic-usb.c:575 Ignoring unchanged value (ci=48, rpt=22, val=0) 15.608 apcupsd: generic-usb.c:575 Ignoring unchanged value (ci=58, rpt=22, val=0) 15.608 apcupsd: generic-usb.c:575 Ignoring unchanged value (ci=59, rpt=22, val=0) 15.608 apcupsd: generic-usb.c:575 Ignoring unchanged value (ci=82, rpt=22, val=1) 15.608 apcupsd: newups.c:108 write_unlock at generic-usb.c:595 15.608 apcupsd: generic-usb.c:538 Timeout=46619 Interrupt data: 06, 08, 20.704 apcupsd: newups.c:102 write_lock at generic-usb.c:561 20.704 apcupsd: generic-usb.c:575 Ignoring unchanged value (ci=1, rpt=6, val=8) 20.704 apcupsd: newups.c:108 write_unlock at generic-usb.c:595 20.704 apcupsd: generic-usb.c:538 Timeout=41523 Interrupt data: 0c, 64, f8, 07, 20.712 apcupsd: newups.c:102 write_lock at generic-usb.c:561 20.712 apcupsd: generic-usb.c:575 Ignoring unchanged value (ci=9, rpt=12, val=100) 20.712 apcupsd: generic-usb.c:575 Ignoring unchanged value (ci=13, rpt=12, val=2040) 20.712 apcupsd: newups.c:108 write_unlock at generic-usb.c:595 20.712 apcupsd: generic-usb.c:538 Timeout=41515 Interrupt data: 16, 0c, 00, 00, 00, 20.720 apcupsd: newups.c:102 write_lock at generic-usb.c:561 20.720 apcupsd: generic-usb.c:575 Ignoring unchanged value (ci=43, rpt=22, val=0) 20.720 apcupsd: generic-usb.c:575 Ignoring unchanged value (ci=45, rpt=22, val=0) 20.720 apcupsd: generic-usb.c:575 Ignoring unchanged value (ci=46, rpt=22, val=0) 20.720 apcupsd: generic-usb.c:575 Ignoring unchanged value (ci=47, rpt=22, val=0) 20.720 apcupsd: generic-usb.c:575 Ignoring unchanged value (ci=48, rpt=22, val=0) 20.720 apcupsd: generic-usb.c:575 Ignoring unchanged value (ci=58, rpt=22, val=0) 20.720 apcupsd: generic-usb.c:575 Ignoring unchanged value (ci=59, rpt=22, val=0) 20.720 apcupsd: generic-usb.c:575 Ignoring unchanged value (ci=82, rpt=22, val=1) 20.720 apcupsd: newups.c:108 write_unlock at generic-usb.c:595 20.720 apcupsd: generic-usb.c:538 Timeout=41507 Interrupt data: 06, 08, 25.824 apcupsd: newups.c:102 write_lock at generic-usb.c:561 25.824 apcupsd: generic-usb.c:575 Ignoring unchanged value (ci=1, rpt=6, val=8) 25.824 apcupsd: newups.c:108 write_unlock at generic-usb.c:595 25.824 apcupsd: generic-usb.c:538 Timeout=36403 Interrupt data: 0c, 64, f8, 07, 25.832 apcupsd: newups.c:102 write_lock at generic-usb.c:561 25.832 apcupsd: generic-usb.c:575 Ignoring unchanged value (ci=9, rpt=12, val=100) 25.832 apcupsd: generic-usb.c:575 Ignoring unchanged value (ci=13, rpt=12, val=2040) 25.832 apcupsd: newups.c:108 write_unlock at generic-usb.c:595 25.832 apcupsd: generic-usb.c:538 Timeout=36395 Interrupt data: 16, 0c, 00, 00, 00, 25.840 apcupsd: newups.c:102 write_lock at generic-usb.c:561 25.840 apcupsd: generic-usb.c:575 Ignoring unchanged value (ci=43, rpt=22, val=0) 25.840 apcupsd: generic-usb.c:575 Ignoring unchanged value (ci=45, rpt=22, val=0) 25.840 apcupsd: generic-usb.c:575 Ignoring unchanged value (ci=46, rpt=22, val=0) 25.840 apcupsd: generic-usb.c:575 Ignoring unchanged value (ci=47, rpt=22, val=0) 25.840 apcupsd: generic-usb.c:575 Ignoring unchanged value (ci=48, rpt=22, val=0) 25.840 apcupsd: generic-usb.c:575 Ignoring unchanged value (ci=58, rpt=22, val=0) 25.840 apcupsd: generic-usb.c:575 Ignoring unchanged value (ci=59, rpt=22, val=0) 25.840 apcupsd: generic-usb.c:575 Ignoring unchanged value (ci=82, rpt=22, val=1) 25.840 apcupsd: newups.c:108 write_unlock at generic-usb.c:595 25.840 apcupsd: generic-usb.c:538 Timeout=36387 Interrupt data: 06, 08, 30.944 apcupsd: newups.c:102 write_lock at generic-usb.c:561 30.944 apcupsd: generic-usb.c:575 Ignoring unchanged value (ci=1, rpt=6, val=8) 30.944 apcupsd: newups.c:108 write_unlock at generic-usb.c:595 30.944 apcupsd: generic-usb.c:538 Timeout=31283 Interrupt data: 0c, 64, f8, 07, 30.952 apcupsd: newups.c:102 write_lock at generic-usb.c:561 30.952 apcupsd: generic-usb.c:575 Ignoring unchanged value (ci=9, rpt=12, val=100) 30.952 apcupsd: generic-usb.c:575 Ignoring unchanged value (ci=13, rpt=12, val=2040) 30.952 apcupsd: newups.c:108 write_unlock at generic-usb.c:595 30.952 apcupsd: generic-usb.c:538 Timeout=31275 Interrupt data: 16, 0c, 00, 00, 00, 30.960 apcupsd: newups.c:102 write_lock at generic-usb.c:561 30.960 apcupsd: generic-usb.c:575 Ignoring unchanged value (ci=43, rpt=22, val=0) 30.960 apcupsd: generic-usb.c:575 Ignoring unchanged value (ci=45, rpt=22, val=0) 30.960 apcupsd: generic-usb.c:575 Ignoring unchanged value (ci=46, rpt=22, val=0) 30.960 apcupsd: generic-usb.c:575 Ignoring unchanged value (ci=47, rpt=22, val=0) 30.960 apcupsd: generic-usb.c:575 Ignoring unchanged value (ci=48, rpt=22, val=0) 30.960 apcupsd: generic-usb.c:575 Ignoring unchanged value (ci=58, rpt=22, val=0) 30.960 apcupsd: generic-usb.c:575 Ignoring unchanged value (ci=59, rpt=22, val=0) 30.960 apcupsd: generic-usb.c:575 Ignoring unchanged value (ci=82, rpt=22, val=1) 30.960 apcupsd: newups.c:108 write_unlock at generic-usb.c:595 30.960 apcupsd: generic-usb.c:538 Timeout=31267 Interrupt data: 06, 08, 36.064 apcupsd: newups.c:102 write_lock at generic-usb.c:561 36.064 apcupsd: generic-usb.c:575 Ignoring unchanged value (ci=1, rpt=6, val=8) 36.064 apcupsd: newups.c:108 write_unlock at generic-usb.c:595 36.064 apcupsd: generic-usb.c:538 Timeout=26162 Interrupt data: 0c, 64, f8, 07, 36.072 apcupsd: newups.c:102 write_lock at generic-usb.c:561 36.072 apcupsd: generic-usb.c:575 Ignoring unchanged value (ci=9, rpt=12, val=100) 36.072 apcupsd: generic-usb.c:575 Ignoring unchanged value (ci=13, rpt=12, val=2040) 36.072 apcupsd: newups.c:108 write_unlock at generic-usb.c:595 36.072 apcupsd: generic-usb.c:538 Timeout=26154 Interrupt data: 16, 0c, 00, 00, 00, 36.080 apcupsd: newups.c:102 write_lock at generic-usb.c:561 36.080 apcupsd: generic-usb.c:575 Ignoring unchanged value (ci=43, rpt=22, val=0) 36.080 apcupsd: generic-usb.c:575 Ignoring unchanged value (ci=45, rpt=22, val=0) 36.080 apcupsd: generic-usb.c:575 Ignoring unchanged value (ci=46, rpt=22, val=0) 36.080 apcupsd: generic-usb.c:575 Ignoring unchanged value (ci=47, rpt=22, val=0) 36.080 apcupsd: generic-usb.c:575 Ignoring unchanged value (ci=48, rpt=22, val=0) 36.080 apcupsd: generic-usb.c:575 Ignoring unchanged value (ci=58, rpt=22, val=0) 36.080 apcupsd: generic-usb.c:575 Ignoring unchanged value (ci=59, rpt=22, val=0) 36.080 apcupsd: generic-usb.c:575 Ignoring unchanged value (ci=82, rpt=22, val=1) 36.080 apcupsd: newups.c:108 write_unlock at generic-usb.c:595 36.081 apcupsd: generic-usb.c:538 Timeout=26146 Interrupt data: 06, 08, 41.184 apcupsd: newups.c:102 write_lock at generic-usb.c:561 41.184 apcupsd: generic-usb.c:575 Ignoring unchanged value (ci=1, rpt=6, val=8) 41.184 apcupsd: newups.c:108 write_unlock at generic-usb.c:595 41.185 apcupsd: generic-usb.c:538 Timeout=21042 Interrupt data: 0c, 64, f8, 07, 41.192 apcupsd: newups.c:102 write_lock at generic-usb.c:561 41.192 apcupsd: generic-usb.c:575 Ignoring unchanged value (ci=9, rpt=12, val=100) 41.192 apcupsd: generic-usb.c:575 Ignoring unchanged value (ci=13, rpt=12, val=2040) 41.192 apcupsd: newups.c:108 write_unlock at generic-usb.c:595 41.192 apcupsd: generic-usb.c:538 Timeout=21034 Interrupt data: 16, 0c, 00, 00, 00, 41.200 apcupsd: newups.c:102 write_lock at generic-usb.c:561 41.200 apcupsd: generic-usb.c:575 Ignoring unchanged value (ci=43, rpt=22, val=0) 41.200 apcupsd: generic-usb.c:575 Ignoring unchanged value (ci=45, rpt=22, val=0) 41.200 apcupsd: generic-usb.c:575 Ignoring unchanged value (ci=46, rpt=22, val=0) 41.200 apcupsd: generic-usb.c:575 Ignoring unchanged value (ci=47, rpt=22, val=0) 41.201 apcupsd: generic-usb.c:575 Ignoring unchanged value (ci=48, rpt=22, val=0) 41.201 apcupsd: generic-usb.c:575 Ignoring unchanged value (ci=58, rpt=22, val=0) 41.201 apcupsd: generic-usb.c:575 Ignoring unchanged value (ci=59, rpt=22, val=0) 41.201 apcupsd: generic-usb.c:575 Ignoring unchanged value (ci=82, rpt=22, val=1) 41.201 apcupsd: newups.c:108 write_unlock at generic-usb.c:595 41.201 apcupsd: generic-usb.c:538 Timeout=21026 Interrupt data: 06, 08, 46.305 apcupsd: newups.c:102 write_lock at generic-usb.c:561 46.305 apcupsd: generic-usb.c:575 Ignoring unchanged value (ci=1, rpt=6, val=8) 46.305 apcupsd: newups.c:108 write_unlock at generic-usb.c:595 46.305 apcupsd: generic-usb.c:538 Timeout=15923 Interrupt data: 0c, 64, f8, 07, 46.312 apcupsd: newups.c:102 write_lock at generic-usb.c:561 46.313 apcupsd: generic-usb.c:575 Ignoring unchanged value (ci=9, rpt=12, val=100) 46.313 apcupsd: generic-usb.c:575 Ignoring unchanged value (ci=13, rpt=12, val=2040) 46.313 apcupsd: newups.c:108 write_unlock at generic-usb.c:595 46.313 apcupsd: generic-usb.c:538 Timeout=15915 Interrupt data: 16, 0c, 00, 00, 00, 46.321 apcupsd: newups.c:102 write_lock at generic-usb.c:561 46.321 apcupsd: generic-usb.c:575 Ignoring unchanged value (ci=43, rpt=22, val=0) 46.321 apcupsd: generic-usb.c:575 Ignoring unchanged value (ci=45, rpt=22, val=0) 46.321 apcupsd: generic-usb.c:575 Ignoring unchanged value (ci=46, rpt=22, val=0) 46.321 apcupsd: generic-usb.c:575 Ignoring unchanged value (ci=47, rpt=22, val=0) 46.321 apcupsd: generic-usb.c:575 Ignoring unchanged value (ci=48, rpt=22, val=0) 46.321 apcupsd: generic-usb.c:575 Ignoring unchanged value (ci=58, rpt=22, val=0) 46.321 apcupsd: generic-usb.c:575 Ignoring unchanged value (ci=59, rpt=22, val=0) 46.321 apcupsd: generic-usb.c:575 Ignoring unchanged value (ci=82, rpt=22, val=1) 46.321 apcupsd: newups.c:108 write_unlock at generic-usb.c:595 46.321 apcupsd: generic-usb.c:538 Timeout=15907 Interrupt data: 06, 08, 51.425 apcupsd: newups.c:102 write_lock at generic-usb.c:561 51.425 apcupsd: generic-usb.c:575 Ignoring unchanged value (ci=1, rpt=6, val=8) 51.425 apcupsd: newups.c:108 write_unlock at generic-usb.c:595 51.425 apcupsd: generic-usb.c:538 Timeout=10803 Interrupt data: 0c, 64, f8, 07, 51.433 apcupsd: newups.c:102 write_lock at generic-usb.c:561 51.433 apcupsd: generic-usb.c:575 Ignoring unchanged value (ci=9, rpt=12, val=100) 51.433 apcupsd: generic-usb.c:575 Ignoring unchanged value (ci=13, rpt=12, val=2040) 51.433 apcupsd: newups.c:108 write_unlock at generic-usb.c:595 51.433 apcupsd: generic-usb.c:538 Timeout=10795 Interrupt data: 16, 0c, 00, 00, 00, 51.441 apcupsd: newups.c:102 write_lock at generic-usb.c:561 51.441 apcupsd: generic-usb.c:575 Ignoring unchanged value (ci=43, rpt=22, val=0) 51.441 apcupsd: generic-usb.c:575 Ignoring unchanged value (ci=45, rpt=22, val=0) 51.441 apcupsd: generic-usb.c:575 Ignoring unchanged value (ci=46, rpt=22, val=0) 51.441 apcupsd: generic-usb.c:575 Ignoring unchanged value (ci=47, rpt=22, val=0) 51.441 apcupsd: generic-usb.c:575 Ignoring unchanged value (ci=48, rpt=22, val=0) 51.441 apcupsd: generic-usb.c:575 Ignoring unchanged value (ci=58, rpt=22, val=0) 51.441 apcupsd: generic-usb.c:575 Ignoring unchanged value (ci=59, rpt=22, val=0) 51.441 apcupsd: generic-usb.c:575 Ignoring unchanged value (ci=82, rpt=22, val=1) 51.441 apcupsd: newups.c:108 write_unlock at generic-usb.c:595 51.441 apcupsd: generic-usb.c:538 Timeout=10787 Interrupt data: 06, 08, 56.545 apcupsd: newups.c:102 write_lock at generic-usb.c:561 56.545 apcupsd: generic-usb.c:575 Ignoring unchanged value (ci=1, rpt=6, val=8) 56.545 apcupsd: newups.c:108 write_unlock at generic-usb.c:595 56.545 apcupsd: generic-usb.c:538 Timeout=5683 Interrupt data: 0c, 64, f8, 07, 56.553 apcupsd: newups.c:102 write_lock at generic-usb.c:561 56.553 apcupsd: generic-usb.c:575 Ignoring unchanged value (ci=9, rpt=12, val=100) 56.553 apcupsd: generic-usb.c:575 Ignoring unchanged value (ci=13, rpt=12, val=2040) 56.553 apcupsd: newups.c:108 write_unlock at generic-usb.c:595 56.553 apcupsd: generic-usb.c:538 Timeout=5675 Interrupt data: 16, 0c, 00, 00, 00, 56.561 apcupsd: newups.c:102 write_lock at generic-usb.c:561 56.561 apcupsd: generic-usb.c:575 Ignoring unchanged value (ci=43, rpt=22, val=0) 56.561 apcupsd: generic-usb.c:575 Ignoring unchanged value (ci=45, rpt=22, val=0) 56.561 apcupsd: generic-usb.c:575 Ignoring unchanged value (ci=46, rpt=22, val=0) 56.561 apcupsd: generic-usb.c:575 Ignoring unchanged value (ci=47, rpt=22, val=0) 56.561 apcupsd: generic-usb.c:575 Ignoring unchanged value (ci=48, rpt=22, val=0) 56.561 apcupsd: generic-usb.c:575 Ignoring unchanged value (ci=58, rpt=22, val=0) 56.561 apcupsd: generic-usb.c:575 Ignoring unchanged value (ci=59, rpt=22, val=0) 56.561 apcupsd: generic-usb.c:575 Ignoring unchanged value (ci=82, rpt=22, val=1) 56.561 apcupsd: newups.c:108 write_unlock at generic-usb.c:595 56.561 apcupsd: generic-usb.c:538 Timeout=5667 Interrupt data: 06, 08, 61.673 apcupsd: newups.c:102 write_lock at generic-usb.c:561 61.673 apcupsd: generic-usb.c:575 Ignoring unchanged value (ci=1, rpt=6, val=8) 61.673 apcupsd: newups.c:108 write_unlock at generic-usb.c:595 61.673 apcupsd: generic-usb.c:538 Timeout=555 Interrupt data: 0c, 64, f8, 07, 61.681 apcupsd: newups.c:102 write_lock at generic-usb.c:561 61.681 apcupsd: generic-usb.c:575 Ignoring unchanged value (ci=9, rpt=12, val=100) 61.681 apcupsd: generic-usb.c:575 Ignoring unchanged value (ci=13, rpt=12, val=2040) 61.681 apcupsd: newups.c:108 write_unlock at generic-usb.c:595 61.681 apcupsd: generic-usb.c:538 Timeout=547 Interrupt data: 16, 0c, 00, 00, 00, 61.689 apcupsd: newups.c:102 write_lock at generic-usb.c:561 61.689 apcupsd: generic-usb.c:575 Ignoring unchanged value (ci=43, rpt=22, val=0) 61.689 apcupsd: generic-usb.c:575 Ignoring unchanged value (ci=45, rpt=22, val=0) 61.689 apcupsd: generic-usb.c:575 Ignoring unchanged value (ci=46, rpt=22, val=0) 61.689 apcupsd: generic-usb.c:575 Ignoring unchanged value (ci=47, rpt=22, val=0) 61.689 apcupsd: generic-usb.c:575 Ignoring unchanged value (ci=48, rpt=22, val=0) 61.689 apcupsd: generic-usb.c:575 Ignoring unchanged value (ci=58, rpt=22, val=0) 61.689 apcupsd: generic-usb.c:575 Ignoring unchanged value (ci=59, rpt=22, val=0) 61.689 apcupsd: generic-usb.c:575 Ignoring unchanged value (ci=82, rpt=22, val=1) 61.689 apcupsd: newups.c:108 write_unlock at generic-usb.c:595 61.689 apcupsd: generic-usb.c:538 Timeout=539 62.239 apcupsd: generic-usb.c:549 usb_interrupt_read error: (-1) Operation not permitted 62.239 apcupsd: generic-usb.c:458 link_check comm lost 68.484 apcupsd: generic-usb.c:300 Reinitializing private structure. 68.484 apcupsd: generic-usb.c:398 Initializing libusb 68.484 apcupsd: generic-usb.c:403 Found 0 USB busses 68.485 apcupsd: generic-usb.c:405 Found 0 USB devices 68.485 apcupsd: generic-usb.c:416 /dev/usb:/dev/ugen3.2 - 0000:0000 68.485 apcupsd: generic-usb.c:416 /dev/usb:/dev/ugen0.2 - 051d:0002 68.485 apcupsd: generic-usb.c:419 Trying device /dev/usb:/dev/ugen0.2 Report descriptor (length=840): 05, 84, 09, 04, a1, 01, 09, 24, a1, 00, 85, 01, 09, fe, 79, 01, 75, 08, 95, 01, 15, 00, 26, ff, 00, b1, 22, 85, 02, 09, ff, 79, 02, b1, 22, 85, 03, 05, 85, 09, 89, 79, 04, b1, 22, 85, 04, 09, 8f, 79, 03, b1, 22, 85, 05, 09, 8b, b1, 22, 85, 06, 06, 86, ff, 09, 60, 81, a2, 09, 60, b1, a2, 85, 07, 05, 85, 09, 85, 75, 10, 27, ff, ff, 00, 00, b1, a2, 85, 08, 05, 84, 09, 40, 67, 21, d1, f0, 00, 55, 05, b1, 22, 85, 09, 09, 30, b1, a2, 85, 0a, 09, fd, 75, 08, 26, ff, 00, 65, 00, 55, 00, 79, 03, b1, 22, 85, 0b, 05, 85, 09, 2c, b1, 22, 85, 0c, 09, 66, 25, 64, 81, a2, 09, 66, b1, a2, 09, 68, 75, 10, 27, ff, ff, 00, 00, 66, 01, 10, 81, a2, 09, 68, b1, a2, 85, 0d, 09, 83, 75, 08, 25, 64, 65, 00, b1, 22, 85, 0e, 09, 67, b1, 22, 85, 0f, 09, 8c, b1, 22, 85, 10, 09, 8e, b1, 22, 85, 11, 09, 29, 15, 01, b1, a2, 85, 12, 09, 8d, 15, 00, b1, 22, 05, 84, 09, 02, a1, 02, 85, 16, 05, 85, 75, 01, 25, 01, 09, 44, 81, a2, 09, 44, b1, a2, 09, 45, 81, a2, 09, 45, b1, a2, 09, d0, 81, a2, 09, d0, b1, a2, 09, d1, 81, a2, 09, d1, b1, a2, 09, 42, 81, a2, 09, 42, b1, a2, 05, 84, 09, 69, 81, a2, 09, 69, b1, a2, 05, 85, 09, 43, 81, a2, 09, 43, b1, a2, 09, 4b, 81, a2, 09, 4b, b1, a2, 05, 84, 09, 65, 81, a2, 09, 65, b1, a2, 95, 17, 81, 01, b1, 01, c0, 85, 17, 05, 85, 09, 2a, 95, 01, 75, 10, 27, ff, ff, 00, 00, 66, 01, 10, b1, a2, 85, 18, 05, 84, 09, 5a, 75, 08, 15, 01, 25, 03, 65, 00, b1, a2, c0, 09, 12, a1, 00, 85, 1c, 06, 86, ff, 09, 16, 75, 18, 15, 00, 27, ff, ff, ff, 00, b2, a2, 01, 85, 20, 05, 85, 09, 85, 75, 10, 27, ff, ff, 00, 00, b1, a2, 85, 22, 09, 66, 75, 08, 25, 64, b1, a2, 85, 23, 09, 68, 75, 10, 27, ff, ff, 00, 00, 66, 01, 10, b1, a2, 85, 24, 09, 2a, b1, a2, 85, 25, 05, 84, 09, 40, 67, 21, d1, f0, 00, 55, 05, b1, 22, 85, 26, 09, 30, b1, a2, 85, 27, 06, 86, ff, 09, 24, 75, 08, 16, e8, 00, 26, fe, 00, 65, 00, 55, 00, b1, a2, 85, 28, 09, 18, 75, 20, 17, 01, 00, 00, 80, 27, ff, ff, ff, 7f, b2, a2, 01, c0, 05, 84, 09, 1a, a1, 00, 85, 30, 05, 84, 09, 40, 75, 08, 15, 00, 26, ff, 00, 67, 21, d1, f0, 00, 55, 07, b1, 22, 85, 31, 09, 30, b1, a2, 85, 32, 09, 53, 15, 57, 25, 5d, b1, a2, 85, 33, 09, 54, 15, 6b, 26, 71, 00, b1, a2, 85, 34, 06, 86, ff, 09, 24, 16, aa, 00, 26, fe, 00, 65, 00, 55, 00, b1, a2, 85, 35, 09, 61, 15, 00, 25, 02, b1, a2, 85, 36, 09, 52, 25, 0d, b1, a2, c0, 09, 05, a1, 00, 85, 40, 09, 7c, 25, 01, b1, a2, 85, 41, 09, 7d, 75, 10, 16, ff, ff, 26, ff, 7f, 66, 01, 10, b1, a2, c0, 05, 84, 09, 16, a1, 00, 85, 50, 09, 35, 75, 08, 15, 00, 25, 64, 65, 00, b1, a2, 85, 51, 06, 86, ff, 09, 24, 16, 6d, 00, 26, b8, 00, b1, a2, c0, 06, 86, ff, 09, 01, a1, 00, 85, 60, 09, 23, 75, 10, 15, 00, 27, ff, ff, 00, 00, b1, a2, 85, 61, 09, 26, 75, 08, 15, 84, 25, 8c, b1, a2, 85, 62, 09, 25, 75, 20, 17, 01, 00, 00, 80, 27, ff, ff, ff, 7f, b2, a2, 01, c0, 85, 7f, 05, 84, 09, fe, 79, 05, 75, 08, 95, 01, 15, 00, 26, ff, 00, b1, 22, 85, 7e, 06, 86, ff, 09, 42, 79, 06, b1, 22, 85, 7d, 05, 84, 09, ff, 79, 02, b1, 22, 85, 7c, 09, fd, 79, 03, b1, 22, 85, 7b, 05, 85, 09, 85, 75, 10, 27, ff, ff, 00, 00, b1, a2, 05, 84, 09, 02, a1, 02, 85, 7a, 05, 85, 09, 44, 75, 01, 25, 01, b1, a2, 09, 45, b1, a2, 09, d0, b1, a2, 09, d1, b1, a2, 09, 42, b1, a2, 05, 84, 09, 69, b1, a2, 05, 85, 09, 43, b1, a2, 09, 4b, b1, a2, 05, 84, 09, 65, b1, a2, 95, 17, b1, 01, c0, 85, 79, 06, 86, ff, 09, 72, 75, 08, 95, 01, b1, a2, 85, 78, 05, 84, 09, 5a, 15, 01, 25, 03, b1, a2, c0, 68.625 apcupsd: newups.c:102 write_lock at generic-usb.c:69 68.625 apcupsd: generic-usb.c:129 Got READ ci=5, rpt=49 (len=2), usage=0x840030 (len=8), kind=0x02 68.625 apcupsd: generic-usb.c:136 Got WRITE ci=5, rpt=49 (len=2), usage=0x840030 (len=8), kind=0x02 68.625 apcupsd: generic-usb.c:129 Got READ ci=10, rpt=38 (len=3), usage=0x840030 (len=16), kind=0x02 68.625 apcupsd: generic-usb.c:136 Got WRITE ci=10, rpt=38 (len=3), usage=0x840030 (len=16), kind=0x02 68.625 apcupsd: generic-usb.c:129 Got READ ci=11, rpt=80 (len=2), usage=0x840035 (len=8), kind=0x02 68.625 apcupsd: generic-usb.c:136 Got WRITE ci=11, rpt=80 (len=2), usage=0x840035 (len=8), kind=0x02 68.626 apcupsd: generic-usb.c:129 Got READ ci=29, rpt=37 (len=3), usage=0x840040 (len=16), kind=0x02 68.626 apcupsd: generic-usb.c:136 Got WRITE ci=29, rpt=37 (len=3), usage=0x840040 (len=16), kind=0x02 68.626 apcupsd: generic-usb.c:129 Got READ ci=66, rpt=48 (len=2), usage=0x840040 (len=8), kind=0x02 68.626 apcupsd: generic-usb.c:136 Got WRITE ci=66, rpt=48 (len=2), usage=0x840040 (len=8), kind=0x02 68.626 apcupsd: generic-usb.c:129 Got READ ci=19, rpt=50 (len=2), usage=0x840053 (len=8), kind=0x02 68.626 apcupsd: generic-usb.c:136 Got WRITE ci=19, rpt=50 (len=2), usage=0x840053 (len=8), kind=0x02 68.626 apcupsd: generic-usb.c:129 Got READ ci=20, rpt=51 (len=2), usage=0x840054 (len=8), kind=0x02 68.626 apcupsd: generic-usb.c:136 Got WRITE ci=20, rpt=51 (len=2), usage=0x840054 (len=8), kind=0x02 68.626 apcupsd: generic-usb.c:129 Got READ ci=22, rpt=24 (len=2), usage=0x84005a (len=8), kind=0x02 68.626 apcupsd: generic-usb.c:136 Got WRITE ci=22, rpt=24 (len=2), usage=0x84005a (len=8), kind=0x02 68.626 apcupsd: generic-usb.c:129 Got READ ci=58, rpt=22 (len=5), usage=0x840065 (len=1), kind=0x00 68.626 apcupsd: generic-usb.c:136 Got WRITE ci=58, rpt=22 (len=5), usage=0x840065 (len=1), kind=0x02 68.627 apcupsd: generic-usb.c:129 Got READ ci=43, rpt=22 (len=5), usage=0x840069 (len=1), kind=0x00 68.627 apcupsd: generic-usb.c:136 Got WRITE ci=43, rpt=22 (len=5), usage=0x840069 (len=1), kind=0x02 68.627 apcupsd: generic-usb.c:129 Got READ ci=41, rpt=10 (len=2), usage=0x8400fd (len=8), kind=0x02 68.627 apcupsd: generic-usb.c:136 Got WRITE ci=41, rpt=10 (len=2), usage=0x8400fd (len=8), kind=0x02 68.627 apcupsd: generic-usb.c:129 Got READ ci=0, rpt=1 (len=2), usage=0x8400fe (len=8), kind=0x02 68.627 apcupsd: generic-usb.c:136 Got WRITE ci=0, rpt=1 (len=2), usage=0x8400fe (len=8), kind=0x02 68.627 apcupsd: generic-usb.c:129 Got READ ci=27, rpt=2 (len=2), usage=0x8400ff (len=8), kind=0x02 68.627 apcupsd: generic-usb.c:136 Got WRITE ci=27, rpt=2 (len=2), usage=0x8400ff (len=8), kind=0x02 68.627 apcupsd: generic-usb.c:129 Got READ ci=26, rpt=7 (len=3), usage=0x850085 (len=16), kind=0x02 68.627 apcupsd: generic-usb.c:136 Got WRITE ci=26, rpt=7 (len=3), usage=0x850085 (len=16), kind=0x02 68.627 apcupsd: generic-usb.c:129 Got READ ci=49, rpt=17 (len=2), usage=0x850029 (len=8), kind=0x02 68.627 apcupsd: generic-usb.c:136 Got WRITE ci=49, rpt=17 (len=2), usage=0x850029 (len=8), kind=0x02 68.627 apcupsd: generic-usb.c:129 Got READ ci=50, rpt=23 (len=3), usage=0x85002a (len=16), kind=0x02 68.627 apcupsd: generic-usb.c:136 Got WRITE ci=50, rpt=23 (len=3), usage=0x85002a (len=16), kind=0x02 68.627 apcupsd: generic-usb.c:129 Got READ ci=45, rpt=22 (len=5), usage=0x850042 (len=1), kind=0x00 68.627 apcupsd: generic-usb.c:136 Got WRITE ci=45, rpt=22 (len=5), usage=0x850042 (len=1), kind=0x02 68.627 apcupsd: generic-usb.c:129 Got READ ci=46, rpt=22 (len=5), usage=0x850043 (len=1), kind=0x00 68.627 apcupsd: generic-usb.c:136 Got WRITE ci=46, rpt=22 (len=5), usage=0x850043 (len=1), kind=0x02 68.627 apcupsd: generic-usb.c:129 Got READ ci=47, rpt=22 (len=5), usage=0x850044 (len=1), kind=0x00 68.627 apcupsd: generic-usb.c:136 Got WRITE ci=47, rpt=22 (len=5), usage=0x850044 (len=1), kind=0x02 68.627 apcupsd: generic-usb.c:129 Got READ ci=48, rpt=22 (len=5), usage=0x850045 (len=1), kind=0x00 68.627 apcupsd: generic-usb.c:136 Got WRITE ci=48, rpt=22 (len=5), usage=0x850045 (len=1), kind=0x02 68.627 apcupsd: generic-usb.c:129 Got READ ci=59, rpt=22 (len=5), usage=0x85004b (len=1), kind=0x00 68.627 apcupsd: generic-usb.c:136 Got WRITE ci=59, rpt=22 (len=5), usage=0x85004b (len=1), kind=0x02 68.628 apcupsd: generic-usb.c:129 Got READ ci=9, rpt=12 (len=4), usage=0x850066 (len=8), kind=0x00 68.628 apcupsd: generic-usb.c:136 Got WRITE ci=9, rpt=12 (len=4), usage=0x850066 (len=8), kind=0x02 68.628 apcupsd: generic-usb.c:129 Got READ ci=13, rpt=12 (len=4), usage=0x850068 (len=16), kind=0x00 68.628 apcupsd: generic-usb.c:136 Got WRITE ci=13, rpt=12 (len=4), usage=0x850068 (len=16), kind=0x02 68.628 apcupsd: generic-usb.c:129 Got READ ci=28, rpt=32 (len=3), usage=0x850085 (len=16), kind=0x02 68.628 apcupsd: generic-usb.c:136 Got WRITE ci=28, rpt=32 (len=3), usage=0x850085 (len=16), kind=0x02 68.628 apcupsd: generic-usb.c:129 Got READ ci=51, rpt=15 (len=2), usage=0x85008c (len=8), kind=0x02 68.628 apcupsd: generic-usb.c:136 Got WRITE ci=51, rpt=15 (len=2), usage=0x85008c (len=8), kind=0x02 68.628 apcupsd: generic-usb.c:129 Got READ ci=55, rpt=22 (len=5), usage=0x8500d0 (len=1), kind=0x00 68.628 apcupsd: generic-usb.c:136 Got WRITE ci=55, rpt=22 (len=5), usage=0x8500d0 (len=1), kind=0x02 68.628 apcupsd: generic-usb.c:129 Got READ ci=82, rpt=22 (len=5), usage=0x8500d1 (len=1), kind=0x00 68.628 apcupsd: generic-usb.c:136 Got WRITE ci=82, rpt=22 (len=5), usage=0x8500d1 (len=1), kind=0x02 68.628 apcupsd: generic-usb.c:129 Got READ ci=1, rpt=6 (len=2), usage=0xff860060 (len=8), kind=0x00 68.628 apcupsd: generic-usb.c:136 Got WRITE ci=1, rpt=6 (len=2), usage=0xff860060 (len=8), kind=0x02 68.628 apcupsd: generic-usb.c:129 Got READ ci=61, rpt=64 (len=2), usage=0xff86007c (len=8), kind=0x02 68.628 apcupsd: generic-usb.c:136 Got WRITE ci=61, rpt=64 (len=2), usage=0xff86007c (len=8), kind=0x02 68.628 apcupsd: generic-usb.c:129 Got READ ci=60, rpt=28 (len=4), usage=0xff860016 (len=24), kind=0x02 68.628 apcupsd: generic-usb.c:136 Got WRITE ci=60, rpt=28 (len=4), usage=0xff860016 (len=24), kind=0x02 68.629 apcupsd: generic-usb.c:129 Got READ ci=64, rpt=65 (len=3), usage=0xff86007d (len=16), kind=0x02 68.629 apcupsd: generic-usb.c:136 Got WRITE ci=64, rpt=65 (len=3), usage=0xff86007d (len=16), kind=0x02 68.629 apcupsd: generic-usb.c:129 Got READ ci=65, rpt=54 (len=2), usage=0xff860052 (len=8), kind=0x02 68.629 apcupsd: generic-usb.c:136 Got WRITE ci=65, rpt=54 (len=2), usage=0xff860052 (len=8), kind=0x02 68.629 apcupsd: generic-usb.c:129 Got READ ci=16, rpt=53 (len=2), usage=0xff860061 (len=8), kind=0x02 68.629 apcupsd: generic-usb.c:136 Got WRITE ci=16, rpt=53 (len=2), usage=0xff860061 (len=8), kind=0x02 68.629 apcupsd: newups.c:108 write_unlock at generic-usb.c:142 68.629 apcupsd: hidutils.c:203 get_report: id=0x01, kind=2, length=2 pos=0 01: 01,01, 68.655 apcupsd: hidutils.c:273 Got string of length=34 68.655 apcupsd: generic-usb.c:172 Def val=1 exp=0 sVal="APC ES 725 FW:821.y2 .A USB FW:y2 " ci=0 68.655 apcupsd: usb.c:302 Checking for BackUPS Pro quirk "APC ES 725 FW:821.y2 .A USB FW:y2 " 68.655 apcupsd: newups.c:102 write_lock at usb.c:864 68.655 apcupsd: hidutils.c:203 get_report: id=0x25, kind=2, length=3 pos=0 25: 25,b0,04, 68.658 apcupsd: generic-usb.c:222 Def val=1200 exp=-2 dVal=12.000000 ci=29 68.700 apcupsd: hidutils.c:203 get_report: id=0x30, kind=2, length=2 pos=0 30: 30,64, 68.703 apcupsd: generic-usb.c:222 Def val=100 exp=0 dVal=100.000000 ci=66 68.745 apcupsd: hidutils.c:203 get_report: id=0x32, kind=2, length=2 pos=0 32: 32,5a, 68.748 apcupsd: generic-usb.c:222 Def val=90 exp=0 dVal=90.000000 ci=19 68.768 apcupsd: hidutils.c:203 get_report: id=0x33, kind=2, length=2 pos=0 33: 33,6e, 68.771 apcupsd: generic-usb.c:222 Def val=110 exp=0 dVal=110.000000 ci=20 69.041 apcupsd: hidutils.c:203 get_report: id=0x0a, kind=2, length=2 pos=0 0a: 0a,03, 69.058 apcupsd: hidutils.c:273 Got string of length=3 69.058 apcupsd: generic-usb.c:172 Def val=3 exp=0 sVal="APC" ci=41 69.064 apcupsd: hidutils.c:203 get_report: id=0x01, kind=2, length=2 pos=0 01: 01,01, 69.094 apcupsd: hidutils.c:273 Got string of length=34 69.094 apcupsd: generic-usb.c:172 Def val=1 exp=0 sVal="APC ES 725 FW:821.y2 .A USB FW:y2 " ci=0 69.094 apcupsd: hidutils.c:203 get_report: id=0x02, kind=2, length=2 pos=0 02: 02,02, 69.116 apcupsd: hidutils.c:273 Got string of length=14 69.116 apcupsd: generic-usb.c:172 Def val=2 exp=0 sVal="3B0634X51015 " ci=27 69.116 apcupsd: hidutils.c:203 get_report: id=0x07, kind=2, length=3 pos=0 07: 07,12,35, 69.119 apcupsd: generic-usb.c:235 Def val=13586 exp=0 dVal=13586.000000 ci=26 69.138 apcupsd: hidutils.c:203 get_report: id=0x11, kind=2, length=2 pos=0 11: 11,0a, 69.141 apcupsd: generic-usb.c:235 Def val=10 exp=0 dVal=10.000000 ci=49 69.161 apcupsd: hidutils.c:203 get_report: id=0x17, kind=2, length=3 pos=0 17: 17,78,00, 69.164 apcupsd: generic-usb.c:222 Def val=120 exp=0 dVal=120.000000 ci=50 69.183 apcupsd: hidutils.c:203 get_report: id=0x16, kind=0, length=5 pos=0 16: 16,0c,00,00,00, 69.186 apcupsd: generic-usb.c:235 Def val=0 exp=0 dVal=0.000000 ci=47 69.251 apcupsd: hidutils.c:203 get_report: id=0x20, kind=2, length=3 pos=0 20: 20,56,36, 69.254 apcupsd: generic-usb.c:235 Def val=13910 exp=0 dVal=13910.000000 ci=28 69.297 apcupsd: hidutils.c:203 get_report: id=0x0f, kind=2, length=2 pos=0 0f: 0f,32, 69.301 apcupsd: generic-usb.c:235 Def val=50 exp=0 dVal=50.000000 ci=51 69.434 apcupsd: hidutils.c:203 get_report: id=0x40, kind=2, length=2 pos=0 40: 40,00, 69.438 apcupsd: generic-usb.c:235 Def val=0 exp=0 dVal=0.000000 ci=61 69.457 apcupsd: hidutils.c:203 get_report: id=0x1c, kind=2, length=4 pos=0 1c: 1c,00,00,00, 69.459 apcupsd: generic-usb.c:235 Def val=0 exp=0 dVal=0.000000 ci=60 69.525 apcupsd: hidutils.c:203 get_report: id=0x41, kind=2, length=3 pos=0 41: 41,ff,ff, 69.528 apcupsd: generic-usb.c:222 Def val=-1 exp=0 dVal=-1.000000 ci=64 69.548 apcupsd: hidutils.c:203 get_report: id=0x35, kind=2, length=2 pos=0 35: 35,02, 69.551 apcupsd: generic-usb.c:235 Def val=2 exp=0 dVal=2.000000 ci=16 69.639 apcupsd: newups.c:108 write_unlock at usb.c:872 69.639 apcupsd: apclog.c:42 Communications with UPS restored. 69.639 apcupsd: action.c:89 calling execute_ups_event commok event=0 69.640 apcupsd: generic-usb.c:495 link check comm OK. 69.640 apcupsd: device.c:204 Before do_action: 0x7000008 (OB:0). 69.640 apcupsd: newups.c:102 write_lock at action.c:351 69.640 apcupsd: apcexec.c:182 exec closed fd 3 69.640 apcupsd: newups.c:108 write_unlock at action.c:644 69.640 apcupsd: apcexec.c:182 exec closed fd 4 69.640 apcupsd: device.c:210 Before fillUPS: 0x7000008 (OB:0). 69.640 apcupsd: apcexec.c:182 exec closed fd 5 69.640 apcupsd: usb.c:828 Enter usb_ups_read_volatile_data 69.640 apcupsd: apcexec.c:182 exec closed fd 6 69.640 apcupsd: newups.c:102 write_lock at usb.c:840 69.640 apcupsd: apcexec.c:182 exec closed fd 7 69.661 apcupsd: hidutils.c:203 get_report: id=0x31, kind=2, length=2 pos=0 31: 31,65, 69.664 apcupsd: generic-usb.c:222 Def val=101 exp=0 dVal=101.000000 ci=5 69.664 apcupsd: usb.c:468 LineVoltage = 101 69.708 apcupsd: hidutils.c:203 get_report: id=0x26, kind=2, length=3 pos=0 26: 26,4f,05, 69.711 apcupsd: generic-usb.c:222 Def val=1359 exp=-2 dVal=13.590000 ci=10 69.711 apcupsd: usb.c:486 BattVoltage = 13 69.753 apcupsd: hidutils.c:203 get_report: id=0x50, kind=2, length=2 pos=0 50: 50,12, 69.756 apcupsd: generic-usb.c:222 Def val=18 exp=0 dVal=18.000000 ci=11 69.756 apcupsd: usb.c:492 UPSLoad = 18 69.845 apcupsd: hidutils.c:203 get_report: id=0x18, kind=2, length=2 pos=0 18: 18,02, 69.848 apcupsd: generic-usb.c:235 Def val=2 exp=0 dVal=2.000000 ci=22 69.867 apcupsd: hidutils.c:203 get_report: id=0x16, kind=0, length=5 pos=8 16: 16,0c,00,00,00, 69.871 apcupsd: generic-usb.c:235 Def val=0 exp=0 dVal=0.000000 ci=58 69.871 apcupsd: usb.c:456 Overload=0 69.890 apcupsd: hidutils.c:203 get_report: id=0x16, kind=0, length=5 pos=5 16: 16,0c,00,00,00, 69.893 apcupsd: generic-usb.c:235 Def val=0 exp=0 dVal=0.000000 ci=43 69.893 apcupsd: usb.c:438 ShutdownImminent=0 69.958 apcupsd: hidutils.c:203 get_report: id=0x16, kind=0, length=5 pos=4 16: 16,0c,00,00,00, 69.961 apcupsd: generic-usb.c:235 Def val=0 exp=0 dVal=0.000000 ci=45 69.961 apcupsd: usb.c:426 BelowRemCapLimit=0 69.981 apcupsd: hidutils.c:203 get_report: id=0x16, kind=0, length=5 pos=6 16: 16,0c,00,00,00, 69.984 apcupsd: generic-usb.c:235 Def val=0 exp=0 dVal=0.000000 ci=46 69.984 apcupsd: usb.c:432 RemTimeLimitExpired=0 70.003 apcupsd: hidutils.c:203 get_report: id=0x16, kind=0, length=5 pos=1 16: 16,0c,00,00,00, 70.006 apcupsd: generic-usb.c:235 Def val=0 exp=0 dVal=0.000000 ci=48 70.006 apcupsd: usb.c:420 Discharging=0 70.026 apcupsd: hidutils.c:203 get_report: id=0x16, kind=0, length=5 pos=7 16: 16,0c,00,00,00, 70.030 apcupsd: generic-usb.c:235 Def val=0 exp=0 dVal=0.000000 ci=59 70.030 apcupsd: usb.c:462 ReplaceBatt=0 70.049 apcupsd: hidutils.c:203 get_report: id=0x0c, kind=0, length=4 pos=0 0c: 0c,64,f8,07, 70.052 apcupsd: generic-usb.c:235 Def val=100 exp=0 dVal=100.000000 ci=9 70.052 apcupsd: usb.c:480 BattCharge = 100 70.073 apcupsd: hidutils.c:203 get_report: id=0x0c, kind=0, length=4 pos=8 0c: 0c,64,f8,07, 70.076 apcupsd: generic-usb.c:222 Def val=2040 exp=0 dVal=2040.000000 ci=13 70.076 apcupsd: usb.c:504 TimeLeft = 34 70.118 apcupsd: hidutils.c:203 get_report: id=0x16, kind=0, length=5 pos=3 16: 16,0c,00,00,00, 70.121 apcupsd: generic-usb.c:235 Def val=1 exp=0 dVal=1.000000 ci=82 70.121 apcupsd: usb.c:615 BatteryPresent=1 70.141 apcupsd: hidutils.c:203 get_report: id=0x06, kind=0, length=2 pos=0 06: 06,08, 70.144 apcupsd: generic-usb.c:235 Def val=8 exp=0 dVal=8.000000 ci=1 70.144 apcupsd: usb.c:409 Status=0x07000008 70.163 apcupsd: hidutils.c:203 get_report: id=0x36, kind=2, length=2 pos=0 36: 36,0d, 70.166 apcupsd: generic-usb.c:235 Def val=13 exp=0 dVal=13.000000 ci=65 70.166 apcupsd: usb.c:552 CI_APCLineFailCause=13 70.166 apcupsd: newups.c:108 write_unlock at usb.c:852 70.166 apcupsd: device.c:216 Before do_action: 0x7000008 (OB:0). 70.166 apcupsd: newups.c:102 write_lock at action.c:351 70.166 apcupsd: newups.c:108 write_unlock at action.c:644 70.166 apcupsd: device.c:222 Before do_reports: 0x7000008 (OB:0). 70.166 apcupsd: device.c:230 Before device_check_state: 0x7000008 (OB:0). 70.166 apcupsd: generic-usb.c:538 Timeout=60000 70.166 apcupsd: newups.c:90 read_lock at apcstatus.c:51 70.166 apcupsd: newups.c:96 read_unlock at apcstatus.c:457 Interrupt data: 0c, 64, f8, 07, 70.169 apcupsd: newups.c:102 write_lock at generic-usb.c:561 70.169 apcupsd: generic-usb.c:575 Ignoring unchanged value (ci=9, rpt=12, val=100) 70.169 apcupsd: generic-usb.c:575 Ignoring unchanged value (ci=13, rpt=12, val=2040) 70.169 apcupsd: newups.c:108 write_unlock at generic-usb.c:595 70.169 apcupsd: generic-usb.c:538 Timeout=59998 Interrupt data: 16, 0c, 00, 00, 00, 70.177 apcupsd: newups.c:102 write_lock at generic-usb.c:561 70.177 apcupsd: generic-usb.c:575 Ignoring unchanged value (ci=43, rpt=22, val=0) 70.177 apcupsd: generic-usb.c:575 Ignoring unchanged value (ci=45, rpt=22, val=0) 70.177 apcupsd: generic-usb.c:575 Ignoring unchanged value (ci=46, rpt=22, val=0) 70.177 apcupsd: generic-usb.c:575 Ignoring unchanged value (ci=47, rpt=22, val=0) 70.177 apcupsd: generic-usb.c:575 Ignoring unchanged value (ci=48, rpt=22, val=0) 70.177 apcupsd: generic-usb.c:575 Ignoring unchanged value (ci=58, rpt=22, val=0) 70.177 apcupsd: generic-usb.c:575 Ignoring unchanged value (ci=59, rpt=22, val=0) 70.177 apcupsd: generic-usb.c:575 Ignoring unchanged value (ci=82, rpt=22, val=1) 70.177 apcupsd: newups.c:108 write_unlock at generic-usb.c:595 70.177 apcupsd: generic-usb.c:538 Timeout=59990 Interrupt data: 06, 08, 71.913 apcupsd: newups.c:102 write_lock at generic-usb.c:561 71.913 apcupsd: generic-usb.c:575 Ignoring unchanged value (ci=1, rpt=6, val=8) 71.913 apcupsd: newups.c:108 write_unlock at generic-usb.c:595 71.913 apcupsd: generic-usb.c:538 Timeout=58254 Interrupt data: 0c, 64, f8, 07, 71.921 apcupsd: newups.c:102 write_lock at generic-usb.c:561 71.921 apcupsd: generic-usb.c:575 Ignoring unchanged value (ci=9, rpt=12, val=100) 71.921 apcupsd: generic-usb.c:575 Ignoring unchanged value (ci=13, rpt=12, val=2040) 71.921 apcupsd: newups.c:108 write_unlock at generic-usb.c:595 71.921 apcupsd: generic-usb.c:538 Timeout=58246 Interrupt data: 16, 0c, 00, 00, 00, 71.929 apcupsd: newups.c:102 write_lock at generic-usb.c:561 71.929 apcupsd: generic-usb.c:575 Ignoring unchanged value (ci=43, rpt=22, val=0) 71.929 apcupsd: generic-usb.c:575 Ignoring unchanged value (ci=45, rpt=22, val=0) 71.929 apcupsd: generic-usb.c:575 Ignoring unchanged value (ci=46, rpt=22, val=0) 71.929 apcupsd: generic-usb.c:575 Ignoring unchanged value (ci=47, rpt=22, val=0) 71.929 apcupsd: generic-usb.c:575 Ignoring unchanged value (ci=48, rpt=22, val=0) 71.929 apcupsd: generic-usb.c:575 Ignoring unchanged value (ci=58, rpt=22, val=0) 71.929 apcupsd: generic-usb.c:575 Ignoring unchanged value (ci=59, rpt=22, val=0) 71.929 apcupsd: generic-usb.c:575 Ignoring unchanged value (ci=82, rpt=22, val=1) 71.929 apcupsd: newups.c:108 write_unlock at generic-usb.c:595 71.929 apcupsd: generic-usb.c:538 Timeout=58238 Interrupt data: 06, 08, 77.040 apcupsd: newups.c:102 write_lock at generic-usb.c:561 77.040 apcupsd: generic-usb.c:575 Ignoring unchanged value (ci=1, rpt=6, val=8) 77.040 apcupsd: newups.c:108 write_unlock at generic-usb.c:595 77.040 apcupsd: generic-usb.c:538 Timeout=53126 Interrupt data: 0c, 64, f8, 07, 77.048 apcupsd: newups.c:102 write_lock at generic-usb.c:561 77.048 apcupsd: generic-usb.c:575 Ignoring unchanged value (ci=9, rpt=12, val=100) 77.048 apcupsd: generic-usb.c:575 Ignoring unchanged value (ci=13, rpt=12, val=2040) 77.048 apcupsd: newups.c:108 write_unlock at generic-usb.c:595 77.048 apcupsd: generic-usb.c:538 Timeout=53118 Interrupt data: 16, 0c, 00, 00, 00, 77.056 apcupsd: newups.c:102 write_lock at generic-usb.c:561 77.056 apcupsd: generic-usb.c:575 Ignoring unchanged value (ci=43, rpt=22, val=0) 77.056 apcupsd: generic-usb.c:575 Ignoring unchanged value (ci=45, rpt=22, val=0) 77.056 apcupsd: generic-usb.c:575 Ignoring unchanged value (ci=46, rpt=22, val=0) 77.056 apcupsd: generic-usb.c:575 Ignoring unchanged value (ci=47, rpt=22, val=0) 77.056 apcupsd: generic-usb.c:575 Ignoring unchanged value (ci=48, rpt=22, val=0) 77.056 apcupsd: generic-usb.c:575 Ignoring unchanged value (ci=58, rpt=22, val=0) 77.056 apcupsd: generic-usb.c:575 Ignoring unchanged value (ci=59, rpt=22, val=0) 77.056 apcupsd: generic-usb.c:575 Ignoring unchanged value (ci=82, rpt=22, val=1) 77.056 apcupsd: newups.c:108 write_unlock at generic-usb.c:595 77.056 apcupsd: generic-usb.c:538 Timeout=53109 Interrupt data: 06, 08, 82.161 apcupsd: newups.c:102 write_lock at generic-usb.c:561 82.161 apcupsd: generic-usb.c:575 Ignoring unchanged value (ci=1, rpt=6, val=8) 82.161 apcupsd: newups.c:108 write_unlock at generic-usb.c:595 82.161 apcupsd: generic-usb.c:538 Timeout=48004 Interrupt data: 0c, 64, f8, 07, 82.169 apcupsd: newups.c:102 write_lock at generic-usb.c:561 82.169 apcupsd: generic-usb.c:575 Ignoring unchanged value (ci=9, rpt=12, val=100) 82.169 apcupsd: generic-usb.c:575 Ignoring unchanged value (ci=13, rpt=12, val=2040) 82.169 apcupsd: newups.c:108 write_unlock at generic-usb.c:595 82.169 apcupsd: generic-usb.c:538 Timeout=47997 Interrupt data: 16, 0c, 00, 00, 00, 82.177 apcupsd: newups.c:102 write_lock at generic-usb.c:561 82.177 apcupsd: generic-usb.c:575 Ignoring unchanged value (ci=43, rpt=22, val=0) 82.177 apcupsd: generic-usb.c:575 Ignoring unchanged value (ci=45, rpt=22, val=0) 82.177 apcupsd: generic-usb.c:575 Ignoring unchanged value (ci=46, rpt=22, val=0) 82.177 apcupsd: generic-usb.c:575 Ignoring unchanged value (ci=47, rpt=22, val=0) 82.177 apcupsd: generic-usb.c:575 Ignoring unchanged value (ci=48, rpt=22, val=0) 82.177 apcupsd: generic-usb.c:575 Ignoring unchanged value (ci=58, rpt=22, val=0) 82.177 apcupsd: generic-usb.c:575 Ignoring unchanged value (ci=59, rpt=22, val=0) 82.177 apcupsd: generic-usb.c:575 Ignoring unchanged value (ci=82, rpt=22, val=1) 82.177 apcupsd: newups.c:108 write_unlock at generic-usb.c:595 82.177 apcupsd: generic-usb.c:538 Timeout=47989 Interrupt data: 06, 08, 87.281 apcupsd: newups.c:102 write_lock at generic-usb.c:561 87.281 apcupsd: generic-usb.c:575 Ignoring unchanged value (ci=1, rpt=6, val=8) 87.281 apcupsd: newups.c:108 write_unlock at generic-usb.c:595 87.281 apcupsd: generic-usb.c:538 Timeout=42885 Interrupt data: 0c, 64, f8, 07, 87.289 apcupsd: newups.c:102 write_lock at generic-usb.c:561 87.289 apcupsd: generic-usb.c:575 Ignoring unchanged value (ci=9, rpt=12, val=100) 87.289 apcupsd: generic-usb.c:575 Ignoring unchanged value (ci=13, rpt=12, val=2040) 87.289 apcupsd: newups.c:108 write_unlock at generic-usb.c:595 87.289 apcupsd: generic-usb.c:538 Timeout=42877 Interrupt data: 16, 0c, 00, 00, 00, 87.297 apcupsd: newups.c:102 write_lock at generic-usb.c:561 87.297 apcupsd: generic-usb.c:575 Ignoring unchanged value (ci=43, rpt=22, val=0) 87.297 apcupsd: generic-usb.c:575 Ignoring unchanged value (ci=45, rpt=22, val=0) 87.297 apcupsd: generic-usb.c:575 Ignoring unchanged value (ci=46, rpt=22, val=0) 87.297 apcupsd: generic-usb.c:575 Ignoring unchanged value (ci=47, rpt=22, val=0) 87.297 apcupsd: generic-usb.c:575 Ignoring unchanged value (ci=48, rpt=22, val=0) 87.297 apcupsd: generic-usb.c:575 Ignoring unchanged value (ci=58, rpt=22, val=0) 87.297 apcupsd: generic-usb.c:575 Ignoring unchanged value (ci=59, rpt=22, val=0) 87.297 apcupsd: generic-usb.c:575 Ignoring unchanged value (ci=82, rpt=22, val=1) 87.297 apcupsd: newups.c:108 write_unlock at generic-usb.c:595 87.297 apcupsd: generic-usb.c:538 Timeout=42869 Interrupt data: 06, 08, 92.401 apcupsd: newups.c:102 write_lock at generic-usb.c:561 92.401 apcupsd: generic-usb.c:575 Ignoring unchanged value (ci=1, rpt=6, val=8) 92.401 apcupsd: newups.c:108 write_unlock at generic-usb.c:595 92.401 apcupsd: generic-usb.c:538 Timeout=37765 Interrupt data: 0c, 64, f8, 07, 92.409 apcupsd: newups.c:102 write_lock at generic-usb.c:561 92.409 apcupsd: generic-usb.c:575 Ignoring unchanged value (ci=9, rpt=12, val=100) 92.409 apcupsd: generic-usb.c:575 Ignoring unchanged value (ci=13, rpt=12, val=2040) 92.409 apcupsd: newups.c:108 write_unlock at generic-usb.c:595 92.409 apcupsd: generic-usb.c:538 Timeout=37757 Interrupt data: 16, 0c, 00, 00, 00, 92.417 apcupsd: newups.c:102 write_lock at generic-usb.c:561 92.417 apcupsd: generic-usb.c:575 Ignoring unchanged value (ci=43, rpt=22, val=0) 92.417 apcupsd: generic-usb.c:575 Ignoring unchanged value (ci=45, rpt=22, val=0) 92.417 apcupsd: generic-usb.c:575 Ignoring unchanged value (ci=46, rpt=22, val=0) 92.417 apcupsd: generic-usb.c:575 Ignoring unchanged value (ci=47, rpt=22, val=0) 92.417 apcupsd: generic-usb.c:575 Ignoring unchanged value (ci=48, rpt=22, val=0) 92.417 apcupsd: generic-usb.c:575 Ignoring unchanged value (ci=58, rpt=22, val=0) 92.417 apcupsd: generic-usb.c:575 Ignoring unchanged value (ci=59, rpt=22, val=0) 92.417 apcupsd: generic-usb.c:575 Ignoring unchanged value (ci=82, rpt=22, val=1) 92.417 apcupsd: newups.c:108 write_unlock at generic-usb.c:595 92.417 apcupsd: generic-usb.c:538 Timeout=37749 Interrupt data: 06, 08, 97.521 apcupsd: newups.c:102 write_lock at generic-usb.c:561 97.521 apcupsd: generic-usb.c:575 Ignoring unchanged value (ci=1, rpt=6, val=8) 97.521 apcupsd: newups.c:108 write_unlock at generic-usb.c:595 97.521 apcupsd: generic-usb.c:538 Timeout=32645 Interrupt data: 0c, 64, f8, 07, 97.529 apcupsd: newups.c:102 write_lock at generic-usb.c:561 97.529 apcupsd: generic-usb.c:575 Ignoring unchanged value (ci=9, rpt=12, val=100) 97.529 apcupsd: generic-usb.c:575 Ignoring unchanged value (ci=13, rpt=12, val=2040) 97.529 apcupsd: newups.c:108 write_unlock at generic-usb.c:595 97.529 apcupsd: generic-usb.c:538 Timeout=32637 Interrupt data: 16, 0c, 00, 00, 00, 97.537 apcupsd: newups.c:102 write_lock at generic-usb.c:561 97.537 apcupsd: generic-usb.c:575 Ignoring unchanged value (ci=43, rpt=22, val=0) 97.537 apcupsd: generic-usb.c:575 Ignoring unchanged value (ci=45, rpt=22, val=0) 97.537 apcupsd: generic-usb.c:575 Ignoring unchanged value (ci=46, rpt=22, val=0) 97.537 apcupsd: generic-usb.c:575 Ignoring unchanged value (ci=47, rpt=22, val=0) 97.537 apcupsd: generic-usb.c:575 Ignoring unchanged value (ci=48, rpt=22, val=0) 97.537 apcupsd: generic-usb.c:575 Ignoring unchanged value (ci=58, rpt=22, val=0) 97.537 apcupsd: generic-usb.c:575 Ignoring unchanged value (ci=59, rpt=22, val=0) 97.537 apcupsd: generic-usb.c:575 Ignoring unchanged value (ci=82, rpt=22, val=1) 97.537 apcupsd: newups.c:108 write_unlock at generic-usb.c:595 97.537 apcupsd: generic-usb.c:538 Timeout=32629 Interrupt data: 06, 08, 102.641 apcupsd: newups.c:102 write_lock at generic-usb.c:561 102.641 apcupsd: generic-usb.c:575 Ignoring unchanged value (ci=1, rpt=6, val=8) 102.641 apcupsd: newups.c:108 write_unlock at generic-usb.c:595 102.641 apcupsd: generic-usb.c:538 Timeout=27525 Interrupt data: 0c, 64, f8, 07, 102.649 apcupsd: newups.c:102 write_lock at generic-usb.c:561 102.649 apcupsd: generic-usb.c:575 Ignoring unchanged value (ci=9, rpt=12, val=100) 102.649 apcupsd: generic-usb.c:575 Ignoring unchanged value (ci=13, rpt=12, val=2040) 102.649 apcupsd: newups.c:108 write_unlock at generic-usb.c:595 102.649 apcupsd: generic-usb.c:538 Timeout=27517 Interrupt data: 16, 0c, 00, 00, 00, 102.657 apcupsd: newups.c:102 write_lock at generic-usb.c:561 102.657 apcupsd: generic-usb.c:575 Ignoring unchanged value (ci=43, rpt=22, val=0) 102.657 apcupsd: generic-usb.c:575 Ignoring unchanged value (ci=45, rpt=22, val=0) 102.657 apcupsd: generic-usb.c:575 Ignoring unchanged value (ci=46, rpt=22, val=0) 102.657 apcupsd: generic-usb.c:575 Ignoring unchanged value (ci=47, rpt=22, val=0) 102.657 apcupsd: generic-usb.c:575 Ignoring unchanged value (ci=48, rpt=22, val=0) 102.657 apcupsd: generic-usb.c:575 Ignoring unchanged value (ci=58, rpt=22, val=0) 102.657 apcupsd: generic-usb.c:575 Ignoring unchanged value (ci=59, rpt=22, val=0) 102.657 apcupsd: generic-usb.c:575 Ignoring unchanged value (ci=82, rpt=22, val=1) 102.657 apcupsd: newups.c:108 write_unlock at generic-usb.c:595 102.657 apcupsd: generic-usb.c:538 Timeout=27509 Interrupt data: 06, 08, 107.761 apcupsd: newups.c:102 write_lock at generic-usb.c:561 107.761 apcupsd: generic-usb.c:575 Ignoring unchanged value (ci=1, rpt=6, val=8) 107.761 apcupsd: newups.c:108 write_unlock at generic-usb.c:595 107.761 apcupsd: generic-usb.c:538 Timeout=22405 Interrupt data: 0c, 64, f8, 07, 107.769 apcupsd: newups.c:102 write_lock at generic-usb.c:561 107.769 apcupsd: generic-usb.c:575 Ignoring unchanged value (ci=9, rpt=12, val=100) 107.769 apcupsd: generic-usb.c:575 Ignoring unchanged value (ci=13, rpt=12, val=2040) 107.769 apcupsd: newups.c:108 write_unlock at generic-usb.c:595 107.769 apcupsd: generic-usb.c:538 Timeout=22397 Interrupt data: 16, 0c, 00, 00, 00, 107.777 apcupsd: newups.c:102 write_lock at generic-usb.c:561 107.777 apcupsd: generic-usb.c:575 Ignoring unchanged value (ci=43, rpt=22, val=0) 107.777 apcupsd: generic-usb.c:575 Ignoring unchanged value (ci=45, rpt=22, val=0) 107.777 apcupsd: generic-usb.c:575 Ignoring unchanged value (ci=46, rpt=22, val=0) 107.777 apcupsd: generic-usb.c:575 Ignoring unchanged value (ci=47, rpt=22, val=0) 107.777 apcupsd: generic-usb.c:575 Ignoring unchanged value (ci=48, rpt=22, val=0) 107.777 apcupsd: generic-usb.c:575 Ignoring unchanged value (ci=58, rpt=22, val=0) 107.777 apcupsd: generic-usb.c:575 Ignoring unchanged value (ci=59, rpt=22, val=0) 107.777 apcupsd: generic-usb.c:575 Ignoring unchanged value (ci=82, rpt=22, val=1) 107.777 apcupsd: newups.c:108 write_unlock at generic-usb.c:595 107.777 apcupsd: generic-usb.c:538 Timeout=22389 Interrupt data: 06, 08, 112.881 apcupsd: newups.c:102 write_lock at generic-usb.c:561 112.881 apcupsd: generic-usb.c:575 Ignoring unchanged value (ci=1, rpt=6, val=8) 112.881 apcupsd: newups.c:108 write_unlock at generic-usb.c:595 112.881 apcupsd: generic-usb.c:538 Timeout=17285 Interrupt data: 0c, 64, f8, 07, 112.889 apcupsd: newups.c:102 write_lock at generic-usb.c:561 112.889 apcupsd: generic-usb.c:575 Ignoring unchanged value (ci=9, rpt=12, val=100) 112.889 apcupsd: generic-usb.c:575 Ignoring unchanged value (ci=13, rpt=12, val=2040) 112.889 apcupsd: newups.c:108 write_unlock at generic-usb.c:595 112.889 apcupsd: generic-usb.c:538 Timeout=17277 Interrupt data: 16, 0c, 00, 00, 00, 112.897 apcupsd: newups.c:102 write_lock at generic-usb.c:561 112.897 apcupsd: generic-usb.c:575 Ignoring unchanged value (ci=43, rpt=22, val=0) 112.897 apcupsd: generic-usb.c:575 Ignoring unchanged value (ci=45, rpt=22, val=0) 112.897 apcupsd: generic-usb.c:575 Ignoring unchanged value (ci=46, rpt=22, val=0) 112.897 apcupsd: generic-usb.c:575 Ignoring unchanged value (ci=47, rpt=22, val=0) 112.897 apcupsd: generic-usb.c:575 Ignoring unchanged value (ci=48, rpt=22, val=0) 112.897 apcupsd: generic-usb.c:575 Ignoring unchanged value (ci=58, rpt=22, val=0) 112.897 apcupsd: generic-usb.c:575 Ignoring unchanged value (ci=59, rpt=22, val=0) 112.897 apcupsd: generic-usb.c:575 Ignoring unchanged value (ci=82, rpt=22, val=1) 112.897 apcupsd: newups.c:108 write_unlock at generic-usb.c:595 112.897 apcupsd: generic-usb.c:538 Timeout=17269 Interrupt data: 06, 08, 118.000 apcupsd: newups.c:102 write_lock at generic-usb.c:561 118.000 apcupsd: generic-usb.c:575 Ignoring unchanged value (ci=1, rpt=6, val=8) 118.000 apcupsd: newups.c:108 write_unlock at generic-usb.c:595 118.000 apcupsd: generic-usb.c:538 Timeout=12165 Interrupt data: 0c, 64, f8, 07, 118.008 apcupsd: newups.c:102 write_lock at generic-usb.c:561 118.008 apcupsd: generic-usb.c:575 Ignoring unchanged value (ci=9, rpt=12, val=100) 118.008 apcupsd: generic-usb.c:575 Ignoring unchanged value (ci=13, rpt=12, val=2040) 118.008 apcupsd: newups.c:108 write_unlock at generic-usb.c:595 118.008 apcupsd: generic-usb.c:538 Timeout=12157 Interrupt data: 16, 0c, 00, 00, 00, 118.016 apcupsd: newups.c:102 write_lock at generic-usb.c:561 118.016 apcupsd: generic-usb.c:575 Ignoring unchanged value (ci=43, rpt=22, val=0) 118.016 apcupsd: generic-usb.c:575 Ignoring unchanged value (ci=45, rpt=22, val=0) 118.016 apcupsd: generic-usb.c:575 Ignoring unchanged value (ci=46, rpt=22, val=0) 118.016 apcupsd: generic-usb.c:575 Ignoring unchanged value (ci=47, rpt=22, val=0) 118.016 apcupsd: generic-usb.c:575 Ignoring unchanged value (ci=48, rpt=22, val=0) 118.016 apcupsd: generic-usb.c:575 Ignoring unchanged value (ci=58, rpt=22, val=0) 118.016 apcupsd: generic-usb.c:575 Ignoring unchanged value (ci=59, rpt=22, val=0) 118.016 apcupsd: generic-usb.c:575 Ignoring unchanged value (ci=82, rpt=22, val=1) 118.016 apcupsd: newups.c:108 write_unlock at generic-usb.c:595 118.016 apcupsd: generic-usb.c:538 Timeout=12149 Interrupt data: 06, 08, 123.121 apcupsd: newups.c:102 write_lock at generic-usb.c:561 123.121 apcupsd: generic-usb.c:575 Ignoring unchanged value (ci=1, rpt=6, val=8) 123.121 apcupsd: newups.c:108 write_unlock at generic-usb.c:595 123.121 apcupsd: generic-usb.c:538 Timeout=7044 Interrupt data: 0c, 64, f8, 07, 123.129 apcupsd: newups.c:102 write_lock at generic-usb.c:561 123.129 apcupsd: generic-usb.c:575 Ignoring unchanged value (ci=9, rpt=12, val=100) 123.129 apcupsd: generic-usb.c:575 Ignoring unchanged value (ci=13, rpt=12, val=2040) 123.129 apcupsd: newups.c:108 write_unlock at generic-usb.c:595 123.129 apcupsd: generic-usb.c:538 Timeout=7036 Interrupt data: 16, 0c, 00, 00, 00, 123.137 apcupsd: newups.c:102 write_lock at generic-usb.c:561 123.137 apcupsd: generic-usb.c:575 Ignoring unchanged value (ci=43, rpt=22, val=0) 123.137 apcupsd: generic-usb.c:575 Ignoring unchanged value (ci=45, rpt=22, val=0) 123.137 apcupsd: generic-usb.c:575 Ignoring unchanged value (ci=46, rpt=22, val=0) 123.137 apcupsd: generic-usb.c:575 Ignoring unchanged value (ci=47, rpt=22, val=0) 123.137 apcupsd: generic-usb.c:575 Ignoring unchanged value (ci=48, rpt=22, val=0) 123.137 apcupsd: generic-usb.c:575 Ignoring unchanged value (ci=58, rpt=22, val=0) 123.137 apcupsd: generic-usb.c:575 Ignoring unchanged value (ci=59, rpt=22, val=0) 123.137 apcupsd: generic-usb.c:575 Ignoring unchanged value (ci=82, rpt=22, val=1) 123.137 apcupsd: newups.c:108 write_unlock at generic-usb.c:595 123.137 apcupsd: generic-usb.c:538 Timeout=7028 Interrupt data: 06, 08, 128.241 apcupsd: newups.c:102 write_lock at generic-usb.c:561 128.241 apcupsd: generic-usb.c:575 Ignoring unchanged value (ci=1, rpt=6, val=8) 128.241 apcupsd: newups.c:108 write_unlock at generic-usb.c:595 128.241 apcupsd: generic-usb.c:538 Timeout=1925 Interrupt data: 0c, 64, f8, 07, 128.249 apcupsd: newups.c:102 write_lock at generic-usb.c:561 128.249 apcupsd: generic-usb.c:575 Ignoring unchanged value (ci=9, rpt=12, val=100) 128.249 apcupsd: generic-usb.c:575 Ignoring unchanged value (ci=13, rpt=12, val=2040) 128.249 apcupsd: newups.c:108 write_unlock at generic-usb.c:595 128.249 apcupsd: generic-usb.c:538 Timeout=1917 Interrupt data: 16, 0c, 00, 00, 00, 128.257 apcupsd: newups.c:102 write_lock at generic-usb.c:561 128.257 apcupsd: generic-usb.c:575 Ignoring unchanged value (ci=43, rpt=22, val=0) 128.257 apcupsd: generic-usb.c:575 Ignoring unchanged value (ci=45, rpt=22, val=0) 128.257 apcupsd: generic-usb.c:575 Ignoring unchanged value (ci=46, rpt=22, val=0) 128.257 apcupsd: generic-usb.c:575 Ignoring unchanged value (ci=47, rpt=22, val=0) 128.257 apcupsd: generic-usb.c:575 Ignoring unchanged value (ci=48, rpt=22, val=0) 128.257 apcupsd: generic-usb.c:575 Ignoring unchanged value (ci=58, rpt=22, val=0) 128.257 apcupsd: generic-usb.c:575 Ignoring unchanged value (ci=59, rpt=22, val=0) 128.257 apcupsd: generic-usb.c:575 Ignoring unchanged value (ci=82, rpt=22, val=1) 128.257 apcupsd: newups.c:108 write_unlock at generic-usb.c:595 128.257 apcupsd: generic-usb.c:538 Timeout=1909 130.194 apcupsd: generic-usb.c:549 usb_interrupt_read error: (-1) Operation not permitted 130.194 apcupsd: generic-usb.c:458 link_check comm lost 136.498 apcupsd: generic-usb.c:300 Reinitializing private structure. 136.498 apcupsd: generic-usb.c:398 Initializing libusb 136.498 apcupsd: generic-usb.c:403 Found 0 USB busses 136.499 apcupsd: generic-usb.c:405 Found 0 USB devices 136.499 apcupsd: generic-usb.c:416 /dev/usb:/dev/ugen3.2 - 0000:0000 136.499 apcupsd: generic-usb.c:416 /dev/usb:/dev/ugen0.2 - 051d:0002 136.499 apcupsd: generic-usb.c:419 Trying device /dev/usb:/dev/ugen0.2 Report descriptor (length=840): 05, 84, 09, 04, a1, 01, 09, 24, a1, 00, 85, 01, 09, fe, 79, 01, 75, 08, 95, 01, 15, 00, 26, ff, 00, b1, 22, 85, 02, 09, ff, 79, 02, b1, 22, 85, 03, 05, 85, 09, 89, 79, 04, b1, 22, 85, 04, 09, 8f, 79, 03, b1, 22, 85, 05, 09, 8b, b1, 22, 85, 06, 06, 86, ff, 09, 60, 81, a2, 09, 60, b1, a2, 85, 07, 05, 85, 09, 85, 75, 10, 27, ff, ff, 00, 00, b1, a2, 85, 08, 05, 84, 09, 40, 67, 21, d1, f0, 00, 55, 05, b1, 22, 85, 09, 09, 30, b1, a2, 85, 0a, 09, fd, 75, 08, 26, ff, 00, 65, 00, 55, 00, 79, 03, b1, 22, 85, 0b, 05, 85, 09, 2c, b1, 22, 85, 0c, 09, 66, 25, 64, 81, a2, 09, 66, b1, a2, 09, 68, 75, 10, 27, ff, ff, 00, 00, 66, 01, 10, 81, a2, 09, 68, b1, a2, 85, 0d, 09, 83, 75, 08, 25, 64, 65, 00, b1, 22, 85, 0e, 09, 67, b1, 22, 85, 0f, 09, 8c, b1, 22, 85, 10, 09, 8e, b1, 22, 85, 11, 09, 29, 15, 01, b1, a2, 85, 12, 09, 8d, 15, 00, b1, 22, 05, 84, 09, 02, a1, 02, 85, 16, 05, 85, 75, 01, 25, 01, 09, 44, 81, a2, 09, 44, b1, a2, 09, 45, 81, a2, 09, 45, b1, a2, 09, d0, 81, a2, 09, d0, b1, a2, 09, d1, 81, a2, 09, d1, b1, a2, 09, 42, 81, a2, 09, 42, b1, a2, 05, 84, 09, 69, 81, a2, 09, 69, b1, a2, 05, 85, 09, 43, 81, a2, 09, 43, b1, a2, 09, 4b, 81, a2, 09, 4b, b1, a2, 05, 84, 09, 65, 81, a2, 09, 65, b1, a2, 95, 17, 81, 01, b1, 01, c0, 85, 17, 05, 85, 09, 2a, 95, 01, 75, 10, 27, ff, ff, 00, 00, 66, 01, 10, b1, a2, 85, 18, 05, 84, 09, 5a, 75, 08, 15, 01, 25, 03, 65, 00, b1, a2, c0, 09, 12, a1, 00, 85, 1c, 06, 86, ff, 09, 16, 75, 18, 15, 00, 27, ff, ff, ff, 00, b2, a2, 01, 85, 20, 05, 85, 09, 85, 75, 10, 27, ff, ff, 00, 00, b1, a2, 85, 22, 09, 66, 75, 08, 25, 64, b1, a2, 85, 23, 09, 68, 75, 10, 27, ff, ff, 00, 00, 66, 01, 10, b1, a2, 85, 24, 09, 2a, b1, a2, 85, 25, 05, 84, 09, 40, 67, 21, d1, f0, 00, 55, 05, b1, 22, 85, 26, 09, 30, b1, a2, 85, 27, 06, 86, ff, 09, 24, 75, 08, 16, e8, 00, 26, fe, 00, 65, 00, 55, 00, b1, a2, 85, 28, 09, 18, 75, 20, 17, 01, 00, 00, 80, 27, ff, ff, ff, 7f, b2, a2, 01, c0, 05, 84, 09, 1a, a1, 00, 85, 30, 05, 84, 09, 40, 75, 08, 15, 00, 26, ff, 00, 67, 21, d1, f0, 00, 55, 07, b1, 22, 85, 31, 09, 30, b1, a2, 85, 32, 09, 53, 15, 57, 25, 5d, b1, a2, 85, 33, 09, 54, 15, 6b, 26, 71, 00, b1, a2, 85, 34, 06, 86, ff, 09, 24, 16, aa, 00, 26, fe, 00, 65, 00, 55, 00, b1, a2, 85, 35, 09, 61, 15, 00, 25, 02, b1, a2, 85, 36, 09, 52, 25, 0d, b1, a2, c0, 09, 05, a1, 00, 85, 40, 09, 7c, 25, 01, b1, a2, 85, 41, 09, 7d, 75, 10, 16, ff, ff, 26, ff, 7f, 66, 01, 10, b1, a2, c0, 05, 84, 09, 16, a1, 00, 85, 50, 09, 35, 75, 08, 15, 00, 25, 64, 65, 00, b1, a2, 85, 51, 06, 86, ff, 09, 24, 16, 6d, 00, 26, b8, 00, b1, a2, c0, 06, 86, ff, 09, 01, a1, 00, 85, 60, 09, 23, 75, 10, 15, 00, 27, ff, ff, 00, 00, b1, a2, 85, 61, 09, 26, 75, 08, 15, 84, 25, 8c, b1, a2, 85, 62, 09, 25, 75, 20, 17, 01, 00, 00, 80, 27, ff, ff, ff, 7f, b2, a2, 01, c0, 85, 7f, 05, 84, 09, fe, 79, 05, 75, 08, 95, 01, 15, 00, 26, ff, 00, b1, 22, 85, 7e, 06, 86, ff, 09, 42, 79, 06, b1, 22, 85, 7d, 05, 84, 09, ff, 79, 02, b1, 22, 85, 7c, 09, fd, 79, 03, b1, 22, 85, 7b, 05, 85, 09, 85, 75, 10, 27, ff, ff, 00, 00, b1, a2, 05, 84, 09, 02, a1, 02, 85, 7a, 05, 85, 09, 44, 75, 01, 25, 01, b1, a2, 09, 45, b1, a2, 09, d0, b1, a2, 09, d1, b1, a2, 09, 42, b1, a2, 05, 84, 09, 69, b1, a2, 05, 85, 09, 43, b1, a2, 09, 4b, b1, a2, 05, 84, 09, 65, b1, a2, 95, 17, b1, 01, c0, 85, 79, 06, 86, ff, 09, 72, 75, 08, 95, 01, b1, a2, 85, 78, 05, 84, 09, 5a, 15, 01, 25, 03, b1, a2, c0, 136.682 apcupsd: newups.c:102 write_lock at generic-usb.c:69 136.682 apcupsd: generic-usb.c:129 Got READ ci=5, rpt=49 (len=2), usage=0x840030 (len=8), kind=0x02 136.682 apcupsd: generic-usb.c:136 Got WRITE ci=5, rpt=49 (len=2), usage=0x840030 (len=8), kind=0x02 136.682 apcupsd: generic-usb.c:129 Got READ ci=10, rpt=38 (len=3), usage=0x840030 (len=16), kind=0x02 136.682 apcupsd: generic-usb.c:136 Got WRITE ci=10, rpt=38 (len=3), usage=0x840030 (len=16), kind=0x02 136.683 apcupsd: generic-usb.c:129 Got READ ci=11, rpt=80 (len=2), usage=0x840035 (len=8), kind=0x02 136.683 apcupsd: generic-usb.c:136 Got WRITE ci=11, rpt=80 (len=2), usage=0x840035 (len=8), kind=0x02 136.683 apcupsd: generic-usb.c:129 Got READ ci=29, rpt=37 (len=3), usage=0x840040 (len=16), kind=0x02 136.683 apcupsd: generic-usb.c:136 Got WRITE ci=29, rpt=37 (len=3), usage=0x840040 (len=16), kind=0x02 136.683 apcupsd: generic-usb.c:129 Got READ ci=66, rpt=48 (len=2), usage=0x840040 (len=8), kind=0x02 136.683 apcupsd: generic-usb.c:136 Got WRITE ci=66, rpt=48 (len=2), usage=0x840040 (len=8), kind=0x02 136.683 apcupsd: generic-usb.c:129 Got READ ci=19, rpt=50 (len=2), usage=0x840053 (len=8), kind=0x02 136.683 apcupsd: generic-usb.c:136 Got WRITE ci=19, rpt=50 (len=2), usage=0x840053 (len=8), kind=0x02 136.683 apcupsd: generic-usb.c:129 Got READ ci=20, rpt=51 (len=2), usage=0x840054 (len=8), kind=0x02 136.683 apcupsd: generic-usb.c:136 Got WRITE ci=20, rpt=51 (len=2), usage=0x840054 (len=8), kind=0x02 136.683 apcupsd: generic-usb.c:129 Got READ ci=22, rpt=24 (len=2), usage=0x84005a (len=8), kind=0x02 136.683 apcupsd: generic-usb.c:136 Got WRITE ci=22, rpt=24 (len=2), usage=0x84005a (len=8), kind=0x02 136.684 apcupsd: generic-usb.c:129 Got READ ci=58, rpt=22 (len=5), usage=0x840065 (len=1), kind=0x00 136.684 apcupsd: generic-usb.c:136 Got WRITE ci=58, rpt=22 (len=5), usage=0x840065 (len=1), kind=0x02 136.684 apcupsd: generic-usb.c:129 Got READ ci=43, rpt=22 (len=5), usage=0x840069 (len=1), kind=0x00 136.684 apcupsd: generic-usb.c:136 Got WRITE ci=43, rpt=22 (len=5), usage=0x840069 (len=1), kind=0x02 136.684 apcupsd: generic-usb.c:129 Got READ ci=41, rpt=10 (len=2), usage=0x8400fd (len=8), kind=0x02 136.684 apcupsd: generic-usb.c:136 Got WRITE ci=41, rpt=10 (len=2), usage=0x8400fd (len=8), kind=0x02 136.684 apcupsd: generic-usb.c:129 Got READ ci=0, rpt=1 (len=2), usage=0x8400fe (len=8), kind=0x02 136.684 apcupsd: generic-usb.c:136 Got WRITE ci=0, rpt=1 (len=2), usage=0x8400fe (len=8), kind=0x02 136.684 apcupsd: generic-usb.c:129 Got READ ci=27, rpt=2 (len=2), usage=0x8400ff (len=8), kind=0x02 136.684 apcupsd: generic-usb.c:136 Got WRITE ci=27, rpt=2 (len=2), usage=0x8400ff (len=8), kind=0x02 136.684 apcupsd: generic-usb.c:129 Got READ ci=26, rpt=7 (len=3), usage=0x850085 (len=16), kind=0x02 136.684 apcupsd: generic-usb.c:136 Got WRITE ci=26, rpt=7 (len=3), usage=0x850085 (len=16), kind=0x02 136.684 apcupsd: generic-usb.c:129 Got READ ci=49, rpt=17 (len=2), usage=0x850029 (len=8), kind=0x02 136.684 apcupsd: generic-usb.c:136 Got WRITE ci=49, rpt=17 (len=2), usage=0x850029 (len=8), kind=0x02 136.684 apcupsd: generic-usb.c:129 Got READ ci=50, rpt=23 (len=3), usage=0x85002a (len=16), kind=0x02 136.684 apcupsd: generic-usb.c:136 Got WRITE ci=50, rpt=23 (len=3), usage=0x85002a (len=16), kind=0x02 136.685 apcupsd: generic-usb.c:129 Got READ ci=45, rpt=22 (len=5), usage=0x850042 (len=1), kind=0x00 136.685 apcupsd: generic-usb.c:136 Got WRITE ci=45, rpt=22 (len=5), usage=0x850042 (len=1), kind=0x02 136.685 apcupsd: generic-usb.c:129 Got READ ci=46, rpt=22 (len=5), usage=0x850043 (len=1), kind=0x00 136.685 apcupsd: generic-usb.c:136 Got WRITE ci=46, rpt=22 (len=5), usage=0x850043 (len=1), kind=0x02 136.685 apcupsd: generic-usb.c:129 Got READ ci=47, rpt=22 (len=5), usage=0x850044 (len=1), kind=0x00 136.685 apcupsd: generic-usb.c:136 Got WRITE ci=47, rpt=22 (len=5), usage=0x850044 (len=1), kind=0x02 136.685 apcupsd: generic-usb.c:129 Got READ ci=48, rpt=22 (len=5), usage=0x850045 (len=1), kind=0x00 136.685 apcupsd: generic-usb.c:136 Got WRITE ci=48, rpt=22 (len=5), usage=0x850045 (len=1), kind=0x02 136.685 apcupsd: generic-usb.c:129 Got READ ci=59, rpt=22 (len=5), usage=0x85004b (len=1), kind=0x00 136.685 apcupsd: generic-usb.c:136 Got WRITE ci=59, rpt=22 (len=5), usage=0x85004b (len=1), kind=0x02 136.685 apcupsd: generic-usb.c:129 Got READ ci=9, rpt=12 (len=4), usage=0x850066 (len=8), kind=0x00 136.685 apcupsd: generic-usb.c:136 Got WRITE ci=9, rpt=12 (len=4), usage=0x850066 (len=8), kind=0x02 136.685 apcupsd: generic-usb.c:129 Got READ ci=13, rpt=12 (len=4), usage=0x850068 (len=16), kind=0x00 136.685 apcupsd: generic-usb.c:136 Got WRITE ci=13, rpt=12 (len=4), usage=0x850068 (len=16), kind=0x02 136.685 apcupsd: generic-usb.c:129 Got READ ci=28, rpt=32 (len=3), usage=0x850085 (len=16), kind=0x02 136.685 apcupsd: generic-usb.c:136 Got WRITE ci=28, rpt=32 (len=3), usage=0x850085 (len=16), kind=0x02 136.685 apcupsd: generic-usb.c:129 Got READ ci=51, rpt=15 (len=2), usage=0x85008c (len=8), kind=0x02 136.685 apcupsd: generic-usb.c:136 Got WRITE ci=51, rpt=15 (len=2), usage=0x85008c (len=8), kind=0x02 136.685 apcupsd: generic-usb.c:129 Got READ ci=55, rpt=22 (len=5), usage=0x8500d0 (len=1), kind=0x00 136.685 apcupsd: generic-usb.c:136 Got WRITE ci=55, rpt=22 (len=5), usage=0x8500d0 (len=1), kind=0x02 136.685 apcupsd: generic-usb.c:129 Got READ ci=82, rpt=22 (len=5), usage=0x8500d1 (len=1), kind=0x00 136.685 apcupsd: generic-usb.c:136 Got WRITE ci=82, rpt=22 (len=5), usage=0x8500d1 (len=1), kind=0x02 136.686 apcupsd: generic-usb.c:129 Got READ ci=1, rpt=6 (len=2), usage=0xff860060 (len=8), kind=0x00 136.686 apcupsd: generic-usb.c:136 Got WRITE ci=1, rpt=6 (len=2), usage=0xff860060 (len=8), kind=0x02 136.686 apcupsd: generic-usb.c:129 Got READ ci=61, rpt=64 (len=2), usage=0xff86007c (len=8), kind=0x02 136.686 apcupsd: generic-usb.c:136 Got WRITE ci=61, rpt=64 (len=2), usage=0xff86007c (len=8), kind=0x02 136.686 apcupsd: generic-usb.c:129 Got READ ci=60, rpt=28 (len=4), usage=0xff860016 (len=24), kind=0x02 136.686 apcupsd: generic-usb.c:136 Got WRITE ci=60, rpt=28 (len=4), usage=0xff860016 (len=24), kind=0x02 136.686 apcupsd: generic-usb.c:129 Got READ ci=64, rpt=65 (len=3), usage=0xff86007d (len=16), kind=0x02 136.686 apcupsd: generic-usb.c:136 Got WRITE ci=64, rpt=65 (len=3), usage=0xff86007d (len=16), kind=0x02 136.686 apcupsd: generic-usb.c:129 Got READ ci=65, rpt=54 (len=2), usage=0xff860052 (len=8), kind=0x02 136.686 apcupsd: generic-usb.c:136 Got WRITE ci=65, rpt=54 (len=2), usage=0xff860052 (len=8), kind=0x02 136.686 apcupsd: generic-usb.c:129 Got READ ci=16, rpt=53 (len=2), usage=0xff860061 (len=8), kind=0x02 136.686 apcupsd: generic-usb.c:136 Got WRITE ci=16, rpt=53 (len=2), usage=0xff860061 (len=8), kind=0x02 136.686 apcupsd: newups.c:108 write_unlock at generic-usb.c:142 136.686 apcupsd: hidutils.c:203 get_report: id=0x01, kind=2, length=2 pos=0 01: 01,01, 136.715 apcupsd: hidutils.c:273 Got string of length=34 136.715 apcupsd: generic-usb.c:172 Def val=1 exp=0 sVal="APC ES 725 FW:821.y2 .A USB FW:y2 " ci=0 136.715 apcupsd: usb.c:302 Checking for BackUPS Pro quirk "APC ES 725 FW:821.y2 .A USB FW:y2 " 136.715 apcupsd: newups.c:102 write_lock at usb.c:864 136.715 apcupsd: hidutils.c:203 get_report: id=0x25, kind=2, length=3 pos=0 25: 25,b0,04, 136.719 apcupsd: generic-usb.c:222 Def val=1200 exp=-2 dVal=12.000000 ci=29 136.760 apcupsd: hidutils.c:203 get_report: id=0x30, kind=2, length=2 pos=0 30: 30,64, 136.764 apcupsd: generic-usb.c:222 Def val=100 exp=0 dVal=100.000000 ci=66 136.806 apcupsd: hidutils.c:203 get_report: id=0x32, kind=2, length=2 pos=0 32: 32,5a, 136.809 apcupsd: generic-usb.c:222 Def val=90 exp=0 dVal=90.000000 ci=19 136.828 apcupsd: hidutils.c:203 get_report: id=0x33, kind=2, length=2 pos=0 33: 33,6e, 136.832 apcupsd: generic-usb.c:222 Def val=110 exp=0 dVal=110.000000 ci=20 137.102 apcupsd: hidutils.c:203 get_report: id=0x0a, kind=2, length=2 pos=0 0a: 0a,03, 137.117 apcupsd: hidutils.c:273 Got string of length=3 137.117 apcupsd: generic-usb.c:172 Def val=3 exp=0 sVal="APC" ci=41 137.124 apcupsd: hidutils.c:203 get_report: id=0x01, kind=2, length=2 pos=0 01: 01,01, 137.154 apcupsd: hidutils.c:273 Got string of length=34 137.154 apcupsd: generic-usb.c:172 Def val=1 exp=0 sVal="APC ES 725 FW:821.y2 .A USB FW:y2 " ci=0 137.154 apcupsd: hidutils.c:203 get_report: id=0x02, kind=2, length=2 pos=0 02: 02,02, 137.175 apcupsd: hidutils.c:273 Got string of length=14 137.175 apcupsd: generic-usb.c:172 Def val=2 exp=0 sVal="3B0634X51015 " ci=27 137.175 apcupsd: hidutils.c:203 get_report: id=0x07, kind=2, length=3 pos=0 07: 07,12,35, 137.179 apcupsd: generic-usb.c:235 Def val=13586 exp=0 dVal=13586.000000 ci=26 137.198 apcupsd: hidutils.c:203 get_report: id=0x11, kind=2, length=2 pos=0 11: 11,0a, 137.200 apcupsd: generic-usb.c:235 Def val=10 exp=0 dVal=10.000000 ci=49 137.221 apcupsd: hidutils.c:203 get_report: id=0x17, kind=2, length=3 pos=0 17: 17,78,00, 137.224 apcupsd: generic-usb.c:222 Def val=120 exp=0 dVal=120.000000 ci=50 137.244 apcupsd: hidutils.c:203 get_report: id=0x16, kind=0, length=5 pos=0 16: 16,0c,00,00,00, 137.247 apcupsd: generic-usb.c:235 Def val=0 exp=0 dVal=0.000000 ci=47 137.312 apcupsd: hidutils.c:203 get_report: id=0x20, kind=2, length=3 pos=0 20: 20,56,36, 137.314 apcupsd: generic-usb.c:235 Def val=13910 exp=0 dVal=13910.000000 ci=28 137.358 apcupsd: hidutils.c:203 get_report: id=0x0f, kind=2, length=2 pos=0 0f: 0f,32, 137.360 apcupsd: generic-usb.c:235 Def val=50 exp=0 dVal=50.000000 ci=51 137.495 apcupsd: hidutils.c:203 get_report: id=0x40, kind=2, length=2 pos=0 40: 40,00, 137.497 apcupsd: generic-usb.c:235 Def val=0 exp=0 dVal=0.000000 ci=61 137.517 apcupsd: hidutils.c:203 get_report: id=0x1c, kind=2, length=4 pos=0 1c: 1c,00,00,00, 137.520 apcupsd: generic-usb.c:235 Def val=0 exp=0 dVal=0.000000 ci=60 137.585 apcupsd: hidutils.c:203 get_report: id=0x41, kind=2, length=3 pos=0 41: 41,ff,ff, 137.587 apcupsd: generic-usb.c:222 Def val=-1 exp=0 dVal=-1.000000 ci=64 137.608 apcupsd: hidutils.c:203 get_report: id=0x35, kind=2, length=2 pos=0 35: 35,02, 137.610 apcupsd: generic-usb.c:235 Def val=2 exp=0 dVal=2.000000 ci=16 137.699 apcupsd: newups.c:108 write_unlock at usb.c:872 137.699 apcupsd: apclog.c:42 Communications with UPS restored. 137.699 apcupsd: action.c:89 calling execute_ups_event commok event=0 137.700 apcupsd: generic-usb.c:495 link check comm OK. 137.700 apcupsd: device.c:204 Before do_action: 0x7000008 (OB:0). 137.700 apcupsd: newups.c:102 write_lock at action.c:351 137.700 apcupsd: newups.c:108 write_unlock at action.c:644 137.700 apcupsd: apcexec.c:182 exec closed fd 3 137.700 apcupsd: device.c:210 Before fillUPS: 0x7000008 (OB:0). 137.700 apcupsd: apcexec.c:182 exec closed fd 4 137.700 apcupsd: usb.c:828 Enter usb_ups_read_volatile_data 137.700 apcupsd: apcexec.c:182 exec closed fd 5 137.700 apcupsd: newups.c:102 write_lock at usb.c:840 137.700 apcupsd: apcexec.c:182 exec closed fd 6 137.700 apcupsd: apcexec.c:182 exec closed fd 7 137.722 apcupsd: hidutils.c:203 get_report: id=0x31, kind=2, length=2 pos=0 31: 31,65, 137.725 apcupsd: generic-usb.c:222 Def val=101 exp=0 dVal=101.000000 ci=5 137.725 apcupsd: usb.c:468 LineVoltage = 101 137.768 apcupsd: hidutils.c:203 get_report: id=0x26, kind=2, length=3 pos=0 26: 26,47,05, 137.770 apcupsd: generic-usb.c:222 Def val=1351 exp=-2 dVal=13.510000 ci=10 137.770 apcupsd: usb.c:486 BattVoltage = 13 137.814 apcupsd: hidutils.c:203 get_report: id=0x50, kind=2, length=2 pos=0 50: 50,12, 137.817 apcupsd: generic-usb.c:222 Def val=18 exp=0 dVal=18.000000 ci=11 137.817 apcupsd: usb.c:492 UPSLoad = 18 137.905 apcupsd: hidutils.c:203 get_report: id=0x18, kind=2, length=2 pos=0 18: 18,02, 137.909 apcupsd: generic-usb.c:235 Def val=2 exp=0 dVal=2.000000 ci=22 137.928 apcupsd: hidutils.c:203 get_report: id=0x16, kind=0, length=5 pos=8 16: 16,0c,00,00,00, 137.930 apcupsd: generic-usb.c:235 Def val=0 exp=0 dVal=0.000000 ci=58 137.930 apcupsd: usb.c:456 Overload=0 137.951 apcupsd: hidutils.c:203 get_report: id=0x16, kind=0, length=5 pos=5 16: 16,0c,00,00,00, 137.954 apcupsd: generic-usb.c:235 Def val=0 exp=0 dVal=0.000000 ci=43 137.954 apcupsd: usb.c:438 ShutdownImminent=0 138.018 apcupsd: hidutils.c:203 get_report: id=0x16, kind=0, length=5 pos=4 16: 16,0c,00,00,00, 138.021 apcupsd: generic-usb.c:235 Def val=0 exp=0 dVal=0.000000 ci=45 138.021 apcupsd: usb.c:426 BelowRemCapLimit=0 138.041 apcupsd: hidutils.c:203 get_report: id=0x16, kind=0, length=5 pos=6 16: 16,0c,00,00,00, 138.044 apcupsd: generic-usb.c:235 Def val=0 exp=0 dVal=0.000000 ci=46 138.044 apcupsd: usb.c:432 RemTimeLimitExpired=0 138.065 apcupsd: hidutils.c:203 get_report: id=0x16, kind=0, length=5 pos=1 16: 16,0c,00,00,00, 138.067 apcupsd: generic-usb.c:235 Def val=0 exp=0 dVal=0.000000 ci=48 138.067 apcupsd: usb.c:420 Discharging=0 138.088 apcupsd: hidutils.c:203 get_report: id=0x16, kind=0, length=5 pos=7 16: 16,0c,00,00,00, 138.090 apcupsd: generic-usb.c:235 Def val=0 exp=0 dVal=0.000000 ci=59 138.090 apcupsd: usb.c:462 ReplaceBatt=0 138.111 apcupsd: hidutils.c:203 get_report: id=0x0c, kind=0, length=4 pos=0 0c: 0c,64,f8,07, 138.114 apcupsd: generic-usb.c:235 Def val=100 exp=0 dVal=100.000000 ci=9 138.114 apcupsd: usb.c:480 BattCharge = 100 138.133 apcupsd: hidutils.c:203 get_report: id=0x0c, kind=0, length=4 pos=8 0c: 0c,64,f8,07, 138.137 apcupsd: generic-usb.c:222 Def val=2040 exp=0 dVal=2040.000000 ci=13 138.137 apcupsd: usb.c:504 TimeLeft = 34 138.179 apcupsd: hidutils.c:203 get_report: id=0x16, kind=0, length=5 pos=3 16: 16,0c,00,00,00, 138.182 apcupsd: generic-usb.c:235 Def val=1 exp=0 dVal=1.000000 ci=82 138.182 apcupsd: usb.c:615 BatteryPresent=1 138.202 apcupsd: hidutils.c:203 get_report: id=0x06, kind=0, length=2 pos=0 06: 06,08, 138.205 apcupsd: generic-usb.c:235 Def val=8 exp=0 dVal=8.000000 ci=1 138.205 apcupsd: usb.c:409 Status=0x07000008 138.225 apcupsd: hidutils.c:203 get_report: id=0x36, kind=2, length=2 pos=0 36: 36,0d, 138.227 apcupsd: generic-usb.c:235 Def val=13 exp=0 dVal=13.000000 ci=65 138.227 apcupsd: usb.c:552 CI_APCLineFailCause=13 138.227 apcupsd: newups.c:108 write_unlock at usb.c:852 138.227 apcupsd: device.c:216 Before do_action: 0x7000008 (OB:0). 138.227 apcupsd: newups.c:102 write_lock at action.c:351 138.227 apcupsd: newups.c:108 write_unlock at action.c:644 138.227 apcupsd: device.c:222 Before do_reports: 0x7000008 (OB:0). 138.228 apcupsd: newups.c:90 read_lock at apcstatus.c:51 138.228 apcupsd: device.c:230 Before device_check_state: 0x7000008 (OB:0). 138.228 apcupsd: generic-usb.c:538 Timeout=60000 138.228 apcupsd: newups.c:96 read_unlock at apcstatus.c:457 Interrupt data: 0c, 64, f8, 07, 138.233 apcupsd: newups.c:102 write_lock at generic-usb.c:561 138.233 apcupsd: generic-usb.c:575 Ignoring unchanged value (ci=9, rpt=12, val=100) 138.233 apcupsd: generic-usb.c:575 Ignoring unchanged value (ci=13, rpt=12, val=2040) 138.233 apcupsd: newups.c:108 write_unlock at generic-usb.c:595 138.233 apcupsd: generic-usb.c:538 Timeout=59995 Interrupt data: 16, 0c, 00, 00, 00, 138.241 apcupsd: newups.c:102 write_lock at generic-usb.c:561 138.241 apcupsd: generic-usb.c:575 Ignoring unchanged value (ci=43, rpt=22, val=0) 138.241 apcupsd: generic-usb.c:575 Ignoring unchanged value (ci=45, rpt=22, val=0) 138.241 apcupsd: generic-usb.c:575 Ignoring unchanged value (ci=46, rpt=22, val=0) 138.241 apcupsd: generic-usb.c:575 Ignoring unchanged value (ci=47, rpt=22, val=0) 138.241 apcupsd: generic-usb.c:575 Ignoring unchanged value (ci=48, rpt=22, val=0) 138.241 apcupsd: generic-usb.c:575 Ignoring unchanged value (ci=58, rpt=22, val=0) 138.242 apcupsd: generic-usb.c:575 Ignoring unchanged value (ci=59, rpt=22, val=0) 138.242 apcupsd: generic-usb.c:575 Ignoring unchanged value (ci=82, rpt=22, val=1) 138.242 apcupsd: newups.c:108 write_unlock at generic-usb.c:595 138.242 apcupsd: generic-usb.c:538 Timeout=59987 Interrupt data: 06, 08, 138.473 apcupsd: newups.c:102 write_lock at generic-usb.c:561 138.473 apcupsd: generic-usb.c:575 Ignoring unchanged value (ci=1, rpt=6, val=8) 138.473 apcupsd: newups.c:108 write_unlock at generic-usb.c:595 138.473 apcupsd: generic-usb.c:538 Timeout=59755 Interrupt data: 0c, 64, f8, 07, 138.481 apcupsd: newups.c:102 write_lock at generic-usb.c:561 138.481 apcupsd: generic-usb.c:575 Ignoring unchanged value (ci=9, rpt=12, val=100) 138.481 apcupsd: generic-usb.c:575 Ignoring unchanged value (ci=13, rpt=12, val=2040) 138.481 apcupsd: newups.c:108 write_unlock at generic-usb.c:595 138.481 apcupsd: generic-usb.c:538 Timeout=59747 Interrupt data: 16, 0c, 00, 00, 00, 138.489 apcupsd: newups.c:102 write_lock at generic-usb.c:561 138.489 apcupsd: generic-usb.c:575 Ignoring unchanged value (ci=43, rpt=22, val=0) 138.489 apcupsd: generic-usb.c:575 Ignoring unchanged value (ci=45, rpt=22, val=0) 138.489 apcupsd: generic-usb.c:575 Ignoring unchanged value (ci=46, rpt=22, val=0) 138.489 apcupsd: generic-usb.c:575 Ignoring unchanged value (ci=47, rpt=22, val=0) 138.489 apcupsd: generic-usb.c:575 Ignoring unchanged value (ci=48, rpt=22, val=0) 138.489 apcupsd: generic-usb.c:575 Ignoring unchanged value (ci=58, rpt=22, val=0) 138.490 apcupsd: generic-usb.c:575 Ignoring unchanged value (ci=59, rpt=22, val=0) 138.490 apcupsd: generic-usb.c:575 Ignoring unchanged value (ci=82, rpt=22, val=1) 138.490 apcupsd: newups.c:108 write_unlock at generic-usb.c:595 138.490 apcupsd: generic-usb.c:538 Timeout=59739 Interrupt data: 06, 08, 143.594 apcupsd: newups.c:102 write_lock at generic-usb.c:561 143.594 apcupsd: generic-usb.c:575 Ignoring unchanged value (ci=1, rpt=6, val=8) 143.594 apcupsd: newups.c:108 write_unlock at generic-usb.c:595 143.594 apcupsd: generic-usb.c:538 Timeout=54634 Interrupt data: 0c, 64, f8, 07, 143.601 apcupsd: newups.c:102 write_lock at generic-usb.c:561 143.601 apcupsd: generic-usb.c:575 Ignoring unchanged value (ci=9, rpt=12, val=100) 143.602 apcupsd: generic-usb.c:575 Ignoring unchanged value (ci=13, rpt=12, val=2040) 143.602 apcupsd: newups.c:108 write_unlock at generic-usb.c:595 143.602 apcupsd: generic-usb.c:538 Timeout=54627 Interrupt data: 16, 0c, 00, 00, 00, 143.609 apcupsd: newups.c:102 write_lock at generic-usb.c:561 143.610 apcupsd: generic-usb.c:575 Ignoring unchanged value (ci=43, rpt=22, val=0) 143.610 apcupsd: generic-usb.c:575 Ignoring unchanged value (ci=45, rpt=22, val=0) 143.610 apcupsd: generic-usb.c:575 Ignoring unchanged value (ci=46, rpt=22, val=0) 143.610 apcupsd: generic-usb.c:575 Ignoring unchanged value (ci=47, rpt=22, val=0) 143.610 apcupsd: generic-usb.c:575 Ignoring unchanged value (ci=48, rpt=22, val=0) 143.610 apcupsd: generic-usb.c:575 Ignoring unchanged value (ci=58, rpt=22, val=0) 143.610 apcupsd: generic-usb.c:575 Ignoring unchanged value (ci=59, rpt=22, val=0) 143.610 apcupsd: generic-usb.c:575 Ignoring unchanged value (ci=82, rpt=22, val=1) 143.610 apcupsd: newups.c:108 write_unlock at generic-usb.c:595 143.610 apcupsd: generic-usb.c:538 Timeout=54618 Interrupt data: 06, 08, 148.714 apcupsd: newups.c:102 write_lock at generic-usb.c:561 148.714 apcupsd: generic-usb.c:575 Ignoring unchanged value (ci=1, rpt=6, val=8) 148.714 apcupsd: newups.c:108 write_unlock at generic-usb.c:595 148.714 apcupsd: generic-usb.c:538 Timeout=49514 Interrupt data: 0c, 64, f8, 07, 148.722 apcupsd: newups.c:102 write_lock at generic-usb.c:561 148.722 apcupsd: generic-usb.c:575 Ignoring unchanged value (ci=9, rpt=12, val=100) 148.722 apcupsd: generic-usb.c:575 Ignoring unchanged value (ci=13, rpt=12, val=2040) 148.722 apcupsd: newups.c:108 write_unlock at generic-usb.c:595 148.722 apcupsd: generic-usb.c:538 Timeout=49506 Interrupt data: 16, 0c, 00, 00, 00, 148.730 apcupsd: newups.c:102 write_lock at generic-usb.c:561 148.730 apcupsd: generic-usb.c:575 Ignoring unchanged value (ci=43, rpt=22, val=0) 148.730 apcupsd: generic-usb.c:575 Ignoring unchanged value (ci=45, rpt=22, val=0) 148.730 apcupsd: generic-usb.c:575 Ignoring unchanged value (ci=46, rpt=22, val=0) 148.730 apcupsd: generic-usb.c:575 Ignoring unchanged value (ci=47, rpt=22, val=0) 148.730 apcupsd: generic-usb.c:575 Ignoring unchanged value (ci=48, rpt=22, val=0) 148.730 apcupsd: generic-usb.c:575 Ignoring unchanged value (ci=58, rpt=22, val=0) 148.730 apcupsd: generic-usb.c:575 Ignoring unchanged value (ci=59, rpt=22, val=0) 148.730 apcupsd: generic-usb.c:575 Ignoring unchanged value (ci=82, rpt=22, val=1) 148.730 apcupsd: newups.c:108 write_unlock at generic-usb.c:595 148.730 apcupsd: generic-usb.c:538 Timeout=49498 152.679 apcupsd: apclog.c:42 apcupsd exiting, signal 15 152.679 apcupsd: newups.c:102 write_lock at generic-usb.c:656 152.679 apcupsd: newups.c:108 write_unlock at generic-usb.c:663 152.679 apcupsd: apclog.c:42 apcupsd shutdown succeeded -------------- next part -------------- From hselasky at c2i.net Mon Feb 16 02:27:54 2009 From: hselasky at c2i.net (Hans Petter Selasky) Date: Mon Feb 16 02:28:01 2009 Subject: USB2 & apcupsd In-Reply-To: <868wo6re81.wl%bowie@nrik.jp> References: <86y6wbf2nc.wl%bowie@nrik.jp> <86ab8mree6.wl%bowie@nrik.jp> <868wo6re81.wl%bowie@nrik.jp> Message-ID: <200902161130.19762.hselasky@c2i.net> On Monday 16 February 2009, Noriyoshi Kawano wrote: > -LIBUSB_ETIMEDOUT The following patch to libusb20 should resolve your problem: http://perforce.freebsd.org/chv.cgi?CH=157783 --HPS From bugmaster at FreeBSD.org Mon Feb 16 03:07:03 2009 From: bugmaster at FreeBSD.org (FreeBSD bugmaster) Date: Mon Feb 16 03:09:27 2009 Subject: Current problem reports assigned to freebsd-usb@FreeBSD.org Message-ID: <200902161107.n1GB700B096302@freefall.freebsd.org> Note: to view an individual PR, use: http://www.freebsd.org/cgi/query-pr.cgi?pr=(number). The following is a listing of current problems submitted by FreeBSD users. These represent problem reports covering all versions including experimental development code and obsolete releases. S Tracker Resp. Description -------------------------------------------------------------------------------- o usb/131583 usb [umass] Failure when detaching umass Device o usb/131576 usb [aue] ADMtek USB To LAN Converter can't send data o usb/131521 usb Registering Belkin UPS to usb_quirks.c f usb/131123 usb [patch] re-add UQ_ASSUME_CM_OVER_DATA USB quirk o usb/131074 usb no run-time detection of usb devices plugged into exte o usb/130736 usb Page fault unplugging USB stick o usb/130325 usb [usb] [patch] fix tools/tools/usb/print-usb-if-vids.sh o usb/130230 usb Samsung Electronics YP-U3 does not attach in 7.1-RELEA o usb/130208 usb Boot process severely hampered by umass0 error o usb/130122 usb [newusb] DVD drive detects as 'da' device o usb/130066 usb [newusb] Serial adaptor use fail with 'unsupported spe o usb/129964 usb [newusb] disconnection of ugen devices isn't logged o bin/129963 usb [newusb] usbconfig(8) fails with misleading error when o docs/129962 usb [newusb] usbconfig(8) refers to non-existant usb2_core o usb/129945 usb [usbdevs] [patch] add u3g support for Longcheer WM66 U o usb/129766 usb [usb] plugging in usb modem HUAWEI E226 panics system o usb/129758 usb [uftdi] [patch] add Pyramid LCD usb support o usb/129673 usb [uhci] uhci (uhub) confused on replugging USB 1.1 scan o usb/129522 usb [ubsa] [patch] add support for ZTE AC8700 modem o usb/129500 usb [umass] [panic] FreeBSD Crashes when connecting SanDis o usb/129311 usb [usb] [panic] Instant crash with an USB card reader o usb/129251 usb [usbdevs] [patch] Liebert UPS being assigned uhid and o usb/129173 usb [uplcom] [patch] Add support for Corega CG-USBRS232R a s usb/128990 usb [usb] u3g does not handle RTS/CTS available on for exa o usb/128977 usb [usb] [patch] uaudio is not full duplex o usb/128803 usb [usbdevs] [patch] Quirk for I-Tuner Networks USBLCD4X2 o usb/128590 usb [patch] [newusb] Updates to NOTES for new USB stack o usb/128485 usb [umodem] [patch] Nokia N80 modem support o usb/128425 usb [umass] Cannot Connect Maxtor Onetouch 4 USB drive f usb/128418 usb [panic] [rum] loading if_rum causes panic, looks like o usb/128324 usb [uplcom] [patch] remove baud rate restriction for PL23 o usb/127980 usb [umass] [patch] Fix Samsung YP U2 MP3 player on 7.x an o usb/127926 usb [boot] USB Timeout during bootup o usb/127549 usb [umass] [patch] Meizu MiniPlayer M6 (SL) requires some s usb/127453 usb [request] ubsa, uark, ubser, uftdi, and friends should o usb/127423 usb [boot] BTX halted on Gigabyte GA-MA69VM-S2 / AMD Sempr o usb/127342 usb [boot] cannot enable usb keyboard and mouse support in o kern/127222 usb [ohci]: Regression in 7.0 usb storage generic driver o usb/126884 usb [ugen] [patch] Bug in buffer handling in ugen.c f usb/126848 usb [usb]: USB Keyboard hangs during Installation o usb/126740 usb [ulpt] doesn't work on 7.0-RELEASE, 10 second stall be o usb/126519 usb [usb] [panic] panic when plugging in an iphone o kern/126396 usb [panic] kernel panic after unplug USB Bluetooth device o usb/125736 usb [ukbd] [hang] system hangs after AT keyboard detect if o usb/125631 usb [ums] [panic] kernel panic during bootup while 'Logite o usb/125510 usb [panic] repeated plug and unplug of USB mass storage d o usb/125450 usb [panic] Removing USB flash card while being accessed c o usb/125264 usb [patch] sysctl for set usb mouse rate (very useful for o usb/125238 usb [ums] Habu Mouse turns off in X o usb/125088 usb [keyboard] Touchpad not detected on Adesso AKB-430UG U o usb/125072 usb [uplcom] [patch] add Mobile Action MA-620 Infrared Ada o usb/124980 usb [panic] kernel panic on detaching unmounted umass devi o kern/124777 usb [ucom] USB cua devices don't revert to tty devices whe o usb/124758 usb [rum] [panic] rum panics SMP kernel o usb/124708 usb [panic] Kernel panic on USB KVM reattach o usb/124604 usb [ums] Microsoft combo wireless mouse doesn't work o usb/123969 usb [usb] Supermicro H8SMi-2 usb problem: port reset faile o usb/123714 usb [usb] [panic] Panic when hald-storage-probe runs with o usb/123691 usb usbd(8): usbd hangs o usb/123690 usb [usb] [panic] Panic on USB device insertion when usb l o usb/123611 usb [usb] BBB reset failed, STALLED from Imation/Mitsumi U o usb/123509 usb [umass] continuous reset Samsung SGH-G600 phone o usb/123352 usb [usbdevs] [patch] Add Option GTMAX3.6/7.2 and Quallcom o usb/123351 usb [usbdevs] [patch] Add Reiner SCT cyberJack, Omnikey [2 o usb/122992 usb [umass] [patch] MotoROKR Z6 Phone not recognised by um o usb/122956 usb [ubsa] [patch] add support for Novatel Wireless XU870 o usb/122936 usb [ucom] [ubsa] Device does not receive interrupt o usb/122905 usb [ubsa] [patch] add Huawei E220 to ubsa o usb/122819 usb [usb] [patch] Patch to provide dynamic additions to th o usb/122813 usb [udbp] [request] udbp driver should be removed in favo o usb/122621 usb [patch] [request] New driver for Sierra Wireless 3G US o usb/122547 usb [ehci] USB Printer not being recognized after reboot o usb/122539 usb [ohci] [panic] AnyDATA ADU-E1000D - kernel panic: ohci o usb/122483 usb [panic] [ulpt] Repeatable panic in 7.0-STABLE o usb/122119 usb [umass] umass device causes creation of daX but not da o usb/122025 usb [uscanner] [patch] uscanner does not attach to Epson R o usb/121755 usb [ohci] [patch] Fix panic after ohci/uhub cardbus devic o usb/121734 usb [ugen] ugen HP1022 printer device not working since up o usb/121708 usb [keyboard] nforce 650i mobo w/ usb keyboard infinite k o usb/121474 usb [cam] [patch] QUIRK: SAMSUNG HM250JI in LaCie usb hard o usb/121426 usb [patch] [uscanner] add HP ScanJet 3570C o usb/121275 usb [boot] FreeBSD fails to boot with usb legacy support e o usb/121232 usb [usb] [panic] USB CardBus card removal causes reboot s p usb/121184 usb [uipaq] [patch] add ids from linux ipaq driver (plus a o usb/121169 usb [umass] Issues with usb mp3 player o usb/121045 usb [uftdi] [patch] Add support for PC-OP-RS1 and KURO-RS o usb/120786 usb [usb] [panic] Kernel panic when forced umount of a det o usb/120729 usb [panic] fault while in kernel mode with connecting USB o usb/120572 usb [umass] [patch] quirk to support ASUS P535 as umass (a o usb/120321 usb [hang] System hangs when transferring data to WD MyBoo o usb/120283 usb [panic] Automation reboot with wireless keyboard & mou o usb/120034 usb [hang] 6.2 & 6.3 hangs on boot at usb0: OHCI with 1.5 o usb/120017 usb [ehci] [patch] CS5536 (AMD Geode) USB 2.0 quirk o usb/119981 usb [axe] [patch] add support for LOGITEC LAN-GTJ/U2 gigab o usb/119977 usb [ums] Mouse does not work in a Cherry-USB keyboard/mou o usb/119653 usb [cam] [patch] iriver s7 player sync cache error patch o usb/119633 usb [umass] umass0: BBB reset failed, IOERROR [regression] o usb/119513 usb [irq] inserting dlink dwl-g630 wireless card results i o usb/119509 usb [usb] USB flaky on Dell Optiplex 755 o usb/119481 usb [hang] FreeBSD not responding after connecting USB-Mas o usb/119389 usb [umass] Sony DSC-W1 CBI reset failed, STALLED [regress o usb/119227 usb [ubsa] [patch] ubsa buffer is too small; should be tun o usb/119201 usb [cam] [patch] Quirks for Olympus FE-210 camera, LG and o usb/118686 usb [usbdevs] [patch] teach usbdevs / ubsa(4) about Huawei o usb/118485 usb [usbdevs] [patch] Logitech Headset Workaround o usb/118480 usb [umass] Timeout in USB mass storage freezes vfs layer o usb/118353 usb [panic] [ppp] repeatable kernel panic during ppp(4) se o usb/118141 usb [ucom] usb serial and nokia phones ucomreadcb ucomread o usb/118140 usb [ucom] [patch] quick hack for ucom to get it behave wi o usb/118098 usb [umass] 6th gen iPod causes problems when disconnectin o usb/117955 usb [umass] [panic] inserting minolta dimage a2 crashes OS o usb/117946 usb [panic] D-Link DUB-E100 rev. B1 crashes FreeBSD 7.0-BE o usb/117938 usb [ums] [patch] Adding support for MS WL Natural and MS o usb/117911 usb [ums] [request] Mouse Gembird MUSWC not work o usb/117893 usb [umass] Lacie USB DVD writing failing o usb/117613 usb [uhci] [irq] uhci interrupt storm & USB leaked memory o usb/117598 usb [uaudio] [patch] Not possible to record with Plantroni o usb/117313 usb [umass] [panic] panic on usb camera insertion o usb/117200 usb [ugen] ugen0 prints strange string on attach if detach o usb/117185 usb [umodem] [patch] Add support for UNION interface descr o usb/117183 usb [panic] USB/fusefs -- panic while transferring large a o usb/116947 usb [ukbd] [patch] [regression] enable boot protocol on th o usb/116699 usb [usbhid] USB HID devices do not initialize at system b o usb/116561 usb [umodem] [panic] RELENG_6 umodem panic "trying to slee o usb/116282 usb [ulpt] Cannot print on USB HP LJ1018 or LJ1300 o usb/115935 usb [usbdevs] [patch] kernel counterproductively attaches o usb/115933 usb [uftdi] [patch] RATOC REX-USB60F (usb serial converter o usb/115400 usb [ehci] Problem with EHCI on ASUS M2N4-SLI o usb/115298 usb [ulpt] [panic] Turning off USB printer panics kernel o usb/114916 usb [umass] [patch] USB Maxtor drive (L300RO) requires qui o kern/114780 usb [uplcom] [panic] Panics while stress testing the uplco o usb/114682 usb [umass] generic USB media-card reader unusable o usb/114310 usb [libusb] [patch] [panic] USB hub attachment panics ker o usb/114068 usb [umass] [patch] Problems with connection of the umass o conf/114013 usb [patch] WITHOUT_USB allow to compil a lot of USB stuff s usb/113977 usb [request] Need a way to set mode of USB disk's write c o usb/113672 usb [ehci] [panic] Kernel panic with AEWIN CB6971 s usb/113629 usb [ukbd] Dropped USB keyboard events on Dell Latitude D6 o usb/113432 usb [ucom] WARNING: attempt to net_add_domain(netgraph) af a usb/113060 usb [usbdevs] [patch] Samsung printer not working in bidir o usb/112944 usb [ulpt] [patch] Bi-directional access to HP LaserJet 10 o usb/112640 usb [usb] [hang] Kernel freezes when writing a file to an o usb/112631 usb [panic] Problem with SONY DSC-S80 camera on umount s usb/112568 usb [umass] [request] USB mode may wrong when mounting Pla o usb/112463 usb [umass] problem with Samsung USB DVD writer, libscg an o usb/112461 usb [ehci] [request] ehci USB 2.0 doesn't work on nforce4 o usb/111753 usb [uhid] [panic] Replicable system panic involving UHID s usb/110991 usb [usbdevs] [patch] QUIRK: Super Top IDE DEVICE (depends o usb/110988 usb [umass] [patch] Handling of quirk IGNORE_RESIDUE is um o usb/110856 usb [ugen] [patch] interrupt in msgs are truncated when bu o usb/110197 usb [umass] Sony PSP umass device does not detach from EHC o usb/109397 usb [panic] on boot from USB flash o usb/109274 usb [usb] MCP55 USB Controller fails to attach in AMD64 Cu o usb/108513 usb [umass] Creative MuVo TX FM fails in 6.2-RELEASE [regr s usb/108344 usb [panic] kernel with atausb panics when unplugging USB o usb/108056 usb [ohci] Mouse gets powered off during device probe when o usb/107935 usb [uplcom] [panic] panic while accessing /dev/cuaU0 o usb/107924 usb [patch] usbd(8) does not call detach o usb/107848 usb [umass] [request] cannot access Samsung flash disk o usb/107827 usb [ohci] [panic] ohci_add_done addr not found o usb/107496 usb [uhub] USB device problem on RELENG_6_2 (SHORT_XFER) [ o usb/107388 usb [patch] [request] new driver: add utoppy device from N o usb/107248 usb [umass] [patch] scsi_da.c quirk for Cowon iAUDIO X5 MP o usb/107243 usb [cam] [patch] Apacer USB Flash Drive quirk o usb/106861 usb [usbdevs] [patch]: usbdevs update: Add product ACER Ze s usb/106832 usb [usb] USB HP printer is not detected by kernel when AC o usb/106648 usb [umass] [hang] USB Floppy on D1950 10 min Hang on Inse o usb/106621 usb [axe] [patch] DLINK DUB-E100 support broken o usb/106615 usb [uftdi] uftdi module does not automatically load with o usb/106041 usb [usb] [request] FreeBSD does not recognise Mustek Bear o usb/105361 usb [panic] Kernel panic during unmounting mass storage (C o usb/105186 usb [ehci] [panic] USB 2.0/ehci on FreeBSD 6.2-PRE/AMD64 c o usb/105065 usb [ata] [usb] SATA - USB Bridge o usb/104830 usb [umass] system crashes when copying data to umass devi o usb/104645 usb [umass] [request] Rave C-201 MP3 player does not commu o usb/104352 usb [ural] [patch] ural driver doesnt work o usb/104292 usb [umass] [hang] system lockup on forced umount of usb-s o usb/104290 usb [umass] [patch] quirk: TOSHIBA DVD-RAM drive (libretto o usb/103917 usb [uhub] USB driver reports "Addr 0 should never happen" o usb/103418 usb usbhidctl(1): [patch] [request] usbhidctl: add ability o usb/103289 usb [request] USB 2.0 problems on AMD LX-800 CPU and CS-55 o usb/103046 usb [ulpt] [patch] ulpt event driven I/O with select(2) an o usb/103025 usb [uhub] [panic] wrong detection of USB device for FreeB o usb/102976 usb [panic] Casio Exilim Digital Camera causes panic on in o usb/102678 usb [keyboard] Dell PowerEdge DRAC5 USB Keyboard does not o usb/102066 usb [ukbd] usb keyboard and multimedia keys don't work o usb/101775 usb [libusbhid] [patch] possible error in report descripto o usb/101761 usb [usb] [patch] [request] usb.h: increase maximal size o o usb/101752 usb [umass] [panic] 6.1-RELEASE kernel panic on usb device o usb/101448 usb [ohci] FBSD 6.1-STABLE/AMD64 crashes under heavy USB/O o usb/101096 usb [ural] [panic] USB WLAN occasionally causes kernel-pan o usb/100746 usb [keyboard] system does not boot due to USB keyboard pr o usb/99538 usb [keyboard] while using USB keyboard default params of o usb/99431 usb [keyboard] FreeBSD on MSI 6566E (Intel 845E motherboar o usb/98343 usb [boot] BBB reset failed errors with Creative Muvo MP3 o usb/97472 usb [cam] [patch] add support for Olympus C150,D390 s usb/97286 usb [mouse] [request] MS Wireless Intellimouse Explorer 2. o usb/97175 usb [umass] [hang] USB cardreader hangs system o usb/96457 usb [umass] [panic] fatback on umass = reboot o usb/96381 usb [cam] [patch] add a quirk table entry for a flash ram o usb/96224 usb [usb] [msdosfs] mount_msdosfs cause page fault in sync s usb/96120 usb [ums] [request] USB mouse not always detected s usb/95636 usb [umass] [boot] 5 minute delay at boot when using VT620 o usb/95562 usb [umass] Write Stress in USB Mass drive causes "vinvalb s usb/95348 usb [keyboard] USB keyboard unplug causes noise on screen o usb/95037 usb [umass] USB disk not recognized on hot-plug. o usb/94897 usb [panic] Kernel Panic when cleanly unmounting USB disk o usb/94717 usb [ulpt] Reading from /dev/ulpt can break work of a UHCI o usb/94384 usb [panic] kernel panic with usb2 hardware o usb/93872 usb [cam] [patch] SCSI quirk required for ELTA 8061 OL USB o usb/93828 usb [ohci] [panic] ohci causes panic on boot (HP Pavillion o usb/93408 usb [mouse] hw.acpi.cpu.cx_lowest=C3 on AMD Turion causes o usb/93389 usb [umass] [patch] Digital Camera Pentax S60 don't work o usb/93155 usb [ulpt] /dev/ulpt0: device busy, USB printer does not w o usb/92852 usb [ums] [patch] Vertical scroll not working properly on o usb/92171 usb [panic] panic unplugging Vodafone Mobile Connect (UMTS o usb/92142 usb [uhub] SET_ADDR_FAILED and SHORT_XFER errors from usb o usb/92083 usb [ural] [panic] panic using WPA on ural NIC in 6.0-RELE o usb/92052 usb [ulpt] usbd causes defunct process with busy file-hand o usb/91906 usb [ehci] [hang] FreeBSD hangs while booting with USB leg o usb/91896 usb camcontrol(8): Serial Number of USB Memory Sticks is n o usb/91811 usb [umass] Compact Flash in HP Photosmart 2610 return " o usb/91629 usb [usb] usbd_abort_pipe() may result in infinite loop o usb/91546 usb [umodem] [patch] Nokia 6630 mobile phone does not work o usb/91538 usb [ulpt] [patch] Unable to print to EPSON CX3500 o usb/91283 usb [boot] [regression] booting very slow with usb devices o usb/91238 usb [umass] USB tape unit fails to write a second tape fil o usb/90700 usb [umass] [panic] Kernel panic on connect/mount/use umas o usb/89954 usb [umass] [panic] USB Disk driver race condition? s usb/89003 usb [request] LaCie Firewire drive not properly supported o usb/88743 usb [hang] [regression] USB makes kernel hang at boot (reg o usb/88408 usb [axe] axe0 read PHY failed o usb/87648 usb [mouse] Logitech USB-optical mouse problem. o usb/87224 usb [usb] Cannot mount USB Zip750 o usb/86767 usb [umass] [patch] bogus "slice starts beyond end of the o usb/86298 usb [mouse] Known good USB mouse won't work with correct s s usb/85067 usb [uscanner] Cannot attach ScanJet 4300C to usb device f usb/84750 usb [hang] 6-BETA2 reboot/shutdown with root_fs on externa s usb/84336 usb [usb] [reboot] instant system reboot when unmounting a o usb/84326 usb [umass] Panic trying to connect SCSI tape drive via US o usb/83977 usb [ucom] [panic] ucom1: open bulk out error (addr 2): IN o usb/83863 usb [ugen] Communication problem between opensc/openct via o usb/83756 usb [ums] [patch] Microsoft Intellimouse Explorer 4.0A doe f usb/83677 usb [usb] [request] usb controller often not detected (Sun o usb/83563 usb [umass] [panic] Page Fault while detaching Mpman Usb d o usb/83504 usb [kernel] [patch] SpeedTouch USB stop working on recent o usb/82660 usb [ehci] [panic] EHCI: I/O stuck in state 'physrd'/panic s usb/82569 usb [umass] [panic] USB mass storage plug/unplug causes sy o usb/82520 usb [udbp] [reboot] Reboot when USL101 connected o usb/82350 usb [ucom] [panic] null pointer dereference in USB stack o usb/81621 usb [ehci] [hang] external hd hangs under load on ehci o usb/80935 usb [uvisor] [patch] uvisor.c is not work with CLIE TH55. o usb/80862 usb [patch] USB locking issues: missing some Giant calls o usb/80854 usb [patch] [request] suggestion for new iface-no-probe me o usb/80829 usb [modules] [panic] possible panic when loading USB-modu s usb/80777 usb [request] usb_rem_task() should wait for callback to c s usb/80776 usb [udav] [request] UDAV device driver shouldn't use usb_ o usb/80774 usb [patch] have "usbd_find_desc" in line with the other " o usb/80361 usb [umass] [patch] mounting of Dell usb-stick fails o usb/80040 usb [hang] Use of sound mixer causes system freeze with ua o usb/79723 usb [usb] [request] prepare for high speed isochronous tra o usb/79722 usb [ehci] wrong alignments in ehci.h a usb/79656 usb [ehci] RHSC interrupts lost o usb/79524 usb [ulpt] printing to Minolta PagePro 1[23]xxW via USB fa o usb/79287 usb [uhci] [hang] UHCI hang after interrupt transfer o usb/79269 usb [ohci] USB ohci da0 plug/unplug causes crashes and loc o usb/78984 usb [umass] [patch] Creative MUVO umass failure o usb/77294 usb [ucom] [panic] ucom + ulpcom panic o usb/77184 usb [umass] [panic] kernel panic on USB device disconnect, o usb/76732 usb [ums] Mouse problems with USB KVM Switch o usb/76653 usb [umass] [patch] Problem with Asahi Optical usb device o usb/76461 usb [umass] disklabel of umass(4)-CAM(4)-da(4) not used by o usb/76395 usb [uhci] USB printer does not work, usbdevs says "addr 0 s usb/75928 usb [umass] [request] Cytronix SmartMedia card (SMC) reade o usb/75800 usb [ucom] ucom1: init failed STALLED error in time of syn o usb/75797 usb [sound] 5.3-STABLE(2005 1/4) detect USB headset, But c o usb/75764 usb [umass] [patch] "umass0: Phase Error" - no device for o usb/75705 usb [umass] [panic] da0 attach / Optio S4 (with backtrace) o usb/74771 usb [umass] [hang] mounting write-protected umass device a s usb/74453 usb [umass] [patch] Q-lity CD-RW USB ECW-043 (ScanLogic SL o usb/74211 usb [umass] USB flash drive causes CAM status 0x4 on 4.10R o usb/73307 usb [panic] Kernel panics on USB disconnect s usb/72733 usb [ucom] [request] Kyocera 7135 Palm OS connection probl o usb/71455 usb [umass] Slow USB umass performance of 5.3 o usb/71417 usb [ugen] Cryptoflex e-gate USB token (ugen0) communicati o usb/71416 usb [ugen] Cryptoflex e-gate USB token (ugen0) detach is n o usb/71280 usb [aue] aue0 device (linksys usb100tx) doesn't work in 1 o usb/71155 usb [ulpt] misbehaving usb-printer hangs processes, causes o usb/70523 usb [umct] [patch] umct sending/receiving wrong characters o usb/69006 usb [usbdevs] [patch] Apple Cinema Display hangs USB ports o usb/68232 usb [ugen] [patch] ugen(4) isochronous handling correction o usb/67301 usb [uftdi] [panic] RTS and system panic o usb/66547 usb [ucom] Palm Tungsten T USB does not initialize correct o usb/63621 usb [umass] [panic] USB MemoryStick Reader stalls/crashes s usb/62257 usb [umass] [request] card reader UCR-61S2B is only half-s o usb/59698 usb [keyboard] [patch] Rework of ukbd HID to AT code trans s bin/57255 usb [patch] usbd(8) and multi-function devices s usb/52026 usb [usb] [request] umass driver support for InSystem ISD2 s usb/51958 usb [urio] [patch] update for urio driver o i386/46371 usb USB controller cannot be initialized on IBM Netfinity o usb/40948 usb [umass] [request] USB HP CDW8200 does not work o usb/30929 usb [usb] [patch] use usbd to initialize USB ADSL modem 302 problems total. From rwatson at FreeBSD.org Mon Feb 16 03:33:20 2009 From: rwatson at FreeBSD.org (Robert Watson) Date: Mon Feb 16 03:33:26 2009 Subject: USB support in NDIS -- IFF_NEEDSGIANT? Message-ID: Dear all: As you know, I've been gradually working to eliminate all non-MPSAFE network device driver infrastructure for 8.0, having removed non-MPSAFE network protocol infrastructure in 7.0. In reviewing remaining drivers using IFF_NEEDSGIANT, I spotted this in the NDIS code: 718 if_initname(ifp, device_get_name(dev), device_get_unit(dev)); 719 ifp->if_mtu = ETHERMTU; 720 ifp->if_flags = IFF_BROADCAST | IFF_SIMPLEX | IFF_MULTICAST; 721 if (sc->ndis_iftype == PNPBus) 722 ifp->if_flags |= IFF_NEEDSGIANT; 723 ifp->if_ioctl = ndis_ioctl; 724 ifp->if_start = ndis_start; 725 ifp->if_init = ndis_init; Having taken a glance, it looks like this was added specifically to support USB devices attached via NDIS. With the new USB code, are NDIS drivers still supported? And in the new world order, is this IFF_NEEDSGIANT still required? Can I simply remove it once the old USB code is on the way out the door? (Note that the plan is to remove all device drivers that still require IFF_NEEDSGIANT some time before 8.0, probably starting with disabling them from the build in about 2-3 weeks). Thanks, Robert N M Watson Computer Laboratory University of Cambridge From thompsa at FreeBSD.org Mon Feb 16 07:32:52 2009 From: thompsa at FreeBSD.org (Andrew Thompson) Date: Mon Feb 16 07:32:58 2009 Subject: USB2 & apcupsd In-Reply-To: <200902161130.19762.hselasky@c2i.net> References: <86y6wbf2nc.wl%bowie@nrik.jp> <86ab8mree6.wl%bowie@nrik.jp> <868wo6re81.wl%bowie@nrik.jp> <200902161130.19762.hselasky@c2i.net> Message-ID: <20090216153245.GA4723@citylink.fud.org.nz> On Mon, Feb 16, 2009 at 11:30:18AM +0100, Hans Petter Selasky wrote: > On Monday 16 February 2009, Noriyoshi Kawano wrote: > > -LIBUSB_ETIMEDOUT > > The following patch to libusb20 should resolve your problem: > > http://perforce.freebsd.org/chv.cgi?CH=157783 And now in HEAD as at r188678. From thompsa at FreeBSD.org Mon Feb 16 07:35:25 2009 From: thompsa at FreeBSD.org (Andrew Thompson) Date: Mon Feb 16 07:35:30 2009 Subject: USB support in NDIS -- IFF_NEEDSGIANT? In-Reply-To: References: Message-ID: <20090216153519.GB4723@citylink.fud.org.nz> On Mon, Feb 16, 2009 at 11:33:18AM +0000, Robert Watson wrote: > > Dear all: > > As you know, I've been gradually working to eliminate all non-MPSAFE > network device driver infrastructure for 8.0, having removed non-MPSAFE > network protocol infrastructure in 7.0. In reviewing remaining drivers > using IFF_NEEDSGIANT, I spotted this in the NDIS code: > > 718 if_initname(ifp, device_get_name(dev), device_get_unit(dev)); > 719 ifp->if_mtu = ETHERMTU; > 720 ifp->if_flags = IFF_BROADCAST | IFF_SIMPLEX | IFF_MULTICAST; > 721 if (sc->ndis_iftype == PNPBus) > 722 ifp->if_flags |= IFF_NEEDSGIANT; > 723 ifp->if_ioctl = ndis_ioctl; > 724 ifp->if_start = ndis_start; > 725 ifp->if_init = ndis_init; > > Having taken a glance, it looks like this was added specifically to support > USB devices attached via NDIS. With the new USB code, are NDIS drivers > still supported? And in the new world order, is this IFF_NEEDSGIANT still > required? Can I simply remove it once the old USB code is on the way out > the door? I had promised Weongyo that I would convert ndis to USB2 but have been a bit busy. Anyone else welcome to pick this up in the mean time. Andrew From hselasky at freebsd.org Mon Feb 16 08:52:42 2009 From: hselasky at freebsd.org (Hans Petter Selasky) Date: Mon Feb 16 08:53:13 2009 Subject: USB support in NDIS -- IFF_NEEDSGIANT? In-Reply-To: <20090216153519.GB4723@citylink.fud.org.nz> References: <20090216153519.GB4723@citylink.fud.org.nz> Message-ID: <200902161755.07491.hselasky@freebsd.org> On Monday 16 February 2009, Andrew Thompson wrote: > On Mon, Feb 16, 2009 at 11:33:18AM +0000, Robert Watson wrote: > > Dear all: > > > > I had promised Weongyo that I would convert ndis to USB2 but have been a > bit busy. Anyone else welcome to pick this up in the mean time. I can take care of it. Will be back in some hours or tomorrow with patches. How can I test the if_ndis is working USB-wise? I assume the latest files are in -current. --HPS From torfinn.ingolfsen at broadpark.no Mon Feb 16 08:58:27 2009 From: torfinn.ingolfsen at broadpark.no (Torfinn Ingolfsen) Date: Mon Feb 16 08:58:35 2009 Subject: HEADSUP: USB2 now default in GENERIC kernels In-Reply-To: <20090215224104.GC74071@citylink.fud.org.nz> References: <20090215224104.GC74071@citylink.fud.org.nz> Message-ID: <20090216165814.d03fd8f1.torfinn.ingolfsen@broadpark.no> On Sun, 15 Feb 2009 14:41:04 -0800 Andrew Thompson wrote: > The GENERIC kernels for all architectures now default to the new USB2 > stack. To avoid confusion: Is this only for -current (ie RELENG_8)? Or laso for RELENG_7 and / or other branches? -- Regards, Torfinn Ingolfsen From imp at bsdimp.com Mon Feb 16 09:06:39 2009 From: imp at bsdimp.com (M. Warner Losh) Date: Mon Feb 16 09:06:45 2009 Subject: HEADSUP: USB2 now default in GENERIC kernels In-Reply-To: <20090216165814.d03fd8f1.torfinn.ingolfsen@broadpark.no> References: <20090215224104.GC74071@citylink.fud.org.nz> <20090216165814.d03fd8f1.torfinn.ingolfsen@broadpark.no> Message-ID: <20090216.100544.-165352397.imp@bsdimp.com> In message: <20090216165814.d03fd8f1.torfinn.ingolfsen@broadpark.no> Torfinn Ingolfsen writes: : On Sun, 15 Feb 2009 14:41:04 -0800 : Andrew Thompson wrote: : : > The GENERIC kernels for all architectures now default to the new USB2 : > stack. : : To avoid confusion: : Is this only for -current (ie RELENG_8)? Or laso for RELENG_7 and / or : other branches? Just for -current. usb2 isn't even in older branches. Warner From thompsa at FreeBSD.org Mon Feb 16 09:22:43 2009 From: thompsa at FreeBSD.org (Andrew Thompson) Date: Mon Feb 16 09:22:49 2009 Subject: HEADSUP: USB2 now default in GENERIC kernels In-Reply-To: <20090215223428.GA74071@citylink.fud.org.nz> References: <20090215223428.GA74071@citylink.fud.org.nz> Message-ID: <20090216172237.GD4723@citylink.fud.org.nz> On Sun, Feb 15, 2009 at 02:34:28PM -0800, Andrew Thompson wrote: > Hi, > > > The GENERIC kernels for all architectures now default to the new USB2 stack. No > kernel config options or code have been removed so if a problem arises please > report it and optionally revert to the old USB stack. > > IMPORTANT NOTES: > > 1. If you are loading USB kernel modules then ensure that these are also > changed over, eg uftdi.ko -> usb2_serial_ftdi.ko. You can not load oldUSB > modules with the GENERIC kernels. > > 2. If you have a custom kernel that includes GENERIC as a base, you need to > ensure that any additional usb devices that you specify are changed over. > > 3. The USB2 kernel options and module names are _temporary_. The next stage is > to move the USB2 code into its permanent location in the source tree and at > that point will take over the well established naming. (ie, usb, ehci, ohci, > uftdi). There will be no changes going from FreeBSD 7.x -> 8.0 > > 4. Once (3) is complete the oldUSB code will still be usable until much closer > to the 8.0 branch. 5. Some people have noted that the latest xorg 7.4 requires the hal daemon to enumerate the input devices. hal does not (yet) work with USB2 so if you find that the keyboard/mouse are not working in X then try adding the following line to the ServerLayout section in xorg.conf Option "AllowEmptyInput" "off" regards, Andrew From haro at kgt.co.jp Mon Feb 16 10:31:46 2009 From: haro at kgt.co.jp (Munehiro Matsuda) Date: Mon Feb 16 10:31:52 2009 Subject: HEADSUP: USB2 now default in GENERIC kernels In-Reply-To: <20090216172237.GD4723@citylink.fud.org.nz> References: <20090215223428.GA74071@citylink.fud.org.nz> <20090216172237.GD4723@citylink.fud.org.nz> Message-ID: <20090217.030501.240656213.haro@h4.dion.ne.jp> From: Andrew Thompson Date: Mon, 16 Feb 2009 09:22:37 -0800 ::On Sun, Feb 15, 2009 at 02:34:28PM -0800, Andrew Thompson wrote: ::> Hi, ::> ::> ::> The GENERIC kernels for all architectures now default to the new USB2 stack. No ::> kernel config options or code have been removed so if a problem arises please ::> report it and optionally revert to the old USB stack. ::> ::> IMPORTANT NOTES: ::> ::> 1. If you are loading USB kernel modules then ensure that these are also ::> changed over, eg uftdi.ko -> usb2_serial_ftdi.ko. You can not load oldUSB ::> modules with the GENERIC kernels. ::> ::> 2. If you have a custom kernel that includes GENERIC as a base, you need to ::> ensure that any additional usb devices that you specify are changed over. ::> ::> 3. The USB2 kernel options and module names are _temporary_. The next stage is ::> to move the USB2 code into its permanent location in the source tree and at ::> that point will take over the well established naming. (ie, usb, ehci, ohci, ::> uftdi). There will be no changes going from FreeBSD 7.x -> 8.0 ::> ::> 4. Once (3) is complete the oldUSB code will still be usable until much closer ::> to the 8.0 branch. :: ::5. Some people have noted that the latest xorg 7.4 requires the hal ::daemon to enumerate the input devices. hal does not (yet) work with USB2 ::so if you find that the keyboard/mouse are not working in X then try ::adding the following line to the ServerLayout section in xorg.conf :: :: Option "AllowEmptyInput" "off" Hi Andrew, As I wrote in other thread, the description in /usr/ports/UPDATING is wrong. It's not "ServerLayout" section, but shuold be "ServerFlags" section as follows: Section "ServerFlags" Option "AllowEmptyInput" "off" EndSection Hope this helps, Haro =------------------------------------------------------------------------------ _ _ Munehiro (haro) Matsuda -|- /_\ |_|_| Internet Solution Dept., KGT Inc. /|\ |_| |_|_| From thompsa at FreeBSD.org Mon Feb 16 10:53:52 2009 From: thompsa at FreeBSD.org (Andrew Thompson) Date: Mon Feb 16 10:54:05 2009 Subject: HEADSUP: USB2 now default in GENERIC kernels In-Reply-To: <20090217.030501.240656213.haro@h4.dion.ne.jp> References: <20090215223428.GA74071@citylink.fud.org.nz> <20090216172237.GD4723@citylink.fud.org.nz> <20090217.030501.240656213.haro@h4.dion.ne.jp> Message-ID: <20090216185347.GB12555@citylink.fud.org.nz> On Tue, Feb 17, 2009 at 03:05:01AM +0900, Munehiro Matsuda wrote: > ::5. Some people have noted that the latest xorg 7.4 requires the hal > ::daemon to enumerate the input devices. hal does not (yet) work with USB2 > ::so if you find that the keyboard/mouse are not working in X then try > ::adding the following line to the ServerLayout section in xorg.conf > :: > :: Option "AllowEmptyInput" "off" > > Hi Andrew, > > As I wrote in other thread, the description in /usr/ports/UPDATING is wrong. > It's not "ServerLayout" section, but shuold be "ServerFlags" section as > follows: > > Section "ServerFlags" > Option "AllowEmptyInput" "off" > EndSection Actually if you look at xorg.conf(5) it can be either. I'll keep the same as the ports UPDATING file for consistency. Andrew From hselasky at freebsd.org Mon Feb 16 11:52:45 2009 From: hselasky at freebsd.org (Hans Petter Selasky) Date: Mon Feb 16 11:52:51 2009 Subject: USB support in NDIS -- IFF_NEEDSGIANT? In-Reply-To: <20090216153519.GB4723@citylink.fud.org.nz> References: <20090216153519.GB4723@citylink.fud.org.nz> Message-ID: <200902161755.07491.hselasky@freebsd.org> On Monday 16 February 2009, Andrew Thompson wrote: > On Mon, Feb 16, 2009 at 11:33:18AM +0000, Robert Watson wrote: > > Dear all: > > > > I had promised Weongyo that I would convert ndis to USB2 but have been a > bit busy. Anyone else welcome to pick this up in the mean time. I can take care of it. Will be back in some hours or tomorrow with patches. How can I test the if_ndis is working USB-wise? I assume the latest files are in -current. --HPS From hselasky at c2i.net Mon Feb 16 12:24:48 2009 From: hselasky at c2i.net (Hans Petter Selasky) Date: Mon Feb 16 12:25:02 2009 Subject: USB support in NDIS -- IFF_NEEDSGIANT? In-Reply-To: <200902161755.07491.hselasky@freebsd.org> References: <20090216153519.GB4723@citylink.fud.org.nz> <200902161755.07491.hselasky@freebsd.org> Message-ID: <200902162127.12209.hselasky@c2i.net> Hi, As long as there are locking mechanisms like this: void KeAcquireSpinLockAtDpcLevel(kspin_lock *lock) { while (atomic_cmpset_acq_int((volatile u_int *)lock, 0, 1) == 0) /* sit and spin */; return; } inside if_ndis, the whole of NDIS needs to run under one lock. What is the name of the "NDIS Giant Lock" after that "Giant" is removed from NDIS? --HPS On Monday 16 February 2009, Hans Petter Selasky wrote: > On Monday 16 February 2009, Andrew Thompson wrote: > > On Mon, Feb 16, 2009 at 11:33:18AM +0000, Robert Watson wrote: > > > Dear all: > > > > I had promised Weongyo that I would convert ndis to USB2 but have been a > > bit busy. Anyone else welcome to pick this up in the mean time. > > I can take care of it. Will be back in some hours or tomorrow with patches. > > How can I test the if_ndis is working USB-wise? > > I assume the latest files are in -current. > > --HPS From hselasky at c2i.net Mon Feb 16 12:24:48 2009 From: hselasky at c2i.net (Hans Petter Selasky) Date: Mon Feb 16 12:25:02 2009 Subject: USB support in NDIS -- IFF_NEEDSGIANT? In-Reply-To: <200902161755.07491.hselasky@freebsd.org> References: <20090216153519.GB4723@citylink.fud.org.nz> <200902161755.07491.hselasky@freebsd.org> Message-ID: <200902162127.12209.hselasky@c2i.net> Hi, As long as there are locking mechanisms like this: void KeAcquireSpinLockAtDpcLevel(kspin_lock *lock) { while (atomic_cmpset_acq_int((volatile u_int *)lock, 0, 1) == 0) /* sit and spin */; return; } inside if_ndis, the whole of NDIS needs to run under one lock. What is the name of the "NDIS Giant Lock" after that "Giant" is removed from NDIS? --HPS On Monday 16 February 2009, Hans Petter Selasky wrote: > On Monday 16 February 2009, Andrew Thompson wrote: > > On Mon, Feb 16, 2009 at 11:33:18AM +0000, Robert Watson wrote: > > > Dear all: > > > > I had promised Weongyo that I would convert ndis to USB2 but have been a > > bit busy. Anyone else welcome to pick this up in the mean time. > > I can take care of it. Will be back in some hours or tomorrow with patches. > > How can I test the if_ndis is working USB-wise? > > I assume the latest files are in -current. > > --HPS From onemda at gmail.com Mon Feb 16 14:32:35 2009 From: onemda at gmail.com (Paul B. Mahol) Date: Mon Feb 16 14:32:43 2009 Subject: USB support in NDIS -- IFF_NEEDSGIANT? In-Reply-To: <200902162127.12209.hselasky@c2i.net> References: <20090216153519.GB4723@citylink.fud.org.nz> <200902161755.07491.hselasky@freebsd.org> <200902162127.12209.hselasky@c2i.net> Message-ID: <3a142e750902161432m15d8c316g6a409d216e9c7053@mail.gmail.com> On 2/16/09, Hans Petter Selasky wrote: > Hi, > > As long as there are locking mechanisms like this: > > void > KeAcquireSpinLockAtDpcLevel(kspin_lock *lock) > { > while (atomic_cmpset_acq_int((volatile u_int *)lock, 0, 1) == 0) > /* sit and spin */; > > return; > } > > inside if_ndis, the whole of NDIS needs to run under one lock. What is the > name of the "NDIS Giant Lock" after that "Giant" is removed from NDIS? > > --HPS > > On Monday 16 February 2009, Hans Petter Selasky wrote: >> On Monday 16 February 2009, Andrew Thompson wrote: >> > On Mon, Feb 16, 2009 at 11:33:18AM +0000, Robert Watson wrote: >> > > Dear all: >> > >> > I had promised Weongyo that I would convert ndis to USB2 but have been a >> > bit busy. Anyone else welcome to pick this up in the mean time. >> >> I can take care of it. Will be back in some hours or tomorrow with >> patches. >> >> How can I test the if_ndis is working USB-wise? >> >> I assume the latest files are in -current. >> >> --HPS > > > _______________________________________________ > freebsd-usb@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-usb > To unsubscribe, send any mail to "freebsd-usb-unsubscribe@freebsd.org" > The whole purpose of IFF_NEEDSGIANT is because usb1 *needs* it. I'm currenly using my own custom if_ndis/ndis code with usb stuff removed and it works fine without that flag. Anyway, usb2 is going to replace usb1 very soon and in that case if_ndis & ndis will stop working. So comment out whole ndisulator from build until it get ported to usb2. -- Paul From bowie at nrik.jp Mon Feb 16 14:42:53 2009 From: bowie at nrik.jp (Noriyoshi Kawano) Date: Mon Feb 16 14:43:00 2009 Subject: USB2 & apcupsd In-Reply-To: <200902161130.19762.hselasky@c2i.net> References: <86y6wbf2nc.wl%bowie@nrik.jp> <86ab8mree6.wl%bowie@nrik.jp> <868wo6re81.wl%bowie@nrik.jp> <200902161130.19762.hselasky@c2i.net> Message-ID: <867i3qq9zv.wl%bowie@nrik.jp> At Mon, 16 Feb 2009 11:30:18 +0100, Hans Petter Selasky wrote: > > On Monday 16 February 2009, Noriyoshi Kawano wrote: > > -LIBUSB_ETIMEDOUT > > The following patch to libusb20 should resolve your problem: > > http://perforce.freebsd.org/chv.cgi?CH=157783 > > --HPS That works fine. Thank you. Noriyoshi Kawano From xcllnt at mac.com Mon Feb 16 14:53:41 2009 From: xcllnt at mac.com (Marcel Moolenaar) Date: Mon Feb 16 14:53:46 2009 Subject: USB2+umass: root mount fails Message-ID: Context: MACHINE=arm, CPU=Marvell It appears that the root mount isn't serialized with USB discovery in the same way it was under USB1. When the root mount is forcibly delayed, everything is fine though: \begin{log} ... FreeBSD 8.0-CURRENT #9: Mon Feb 16 21:35:51 UTC 2009 marcel@orion.xcllnt.net:/usr/obj/nfs/freebsd/base/head/sys/ORION ... SOC: Marvell 88F5281 rev D0, TClock 166MHz mbus0: on motherboard ... ehci0: at mem 0xf1050000-0xf1050fff irq 16,17 on mbus0 ehci0: [FILTER] ehci0: [ITHREAD] usbus0: EHCI version 1.0 usbus0: on ehci0 ... usbus0: 480Mbps High Speed USB v2.0 ... *** BEGIN: forced root mount delay of 10s *** ... ugen0.1: at usbus0 ushub0: on usbus0 ushub0: 1 port with 1 removable, self powered ugen0.2: at usbus0 ushub1: on usbus0 ushub1: 7 ports with 7 removable, self powered ugen0.3: at usbus0 umass0: on usbus0 umass0: SCSI over Bulk-Only; quirks = 0x0000 umass0:0:0:-1: Attached to scbus0 da0 at umass-sim0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI-2 device da0: 40.000MB/s transfers da0: 476940MB (976773168 512 byte sectors: 255H 63S/T 60801C) ... *** END: forced root mount delay of 10s *** ... Trying to mount root from ufs:/dev/da0p1 No suitable dump device was found. Entropy harvesting: interrupts ethernet point_to_point kickstart. /dev/da0p1: FILE SYSTEM CLEAN; SKIPPING CHECKS /dev/da0p1: clean, 17803769 free (6465 frags, 2224663 blocks, 0.0% fragmentation) ... \end{log} Before I dig into the code, what's the current status of root mounts on USB mass storage devices? -- Marcel Moolenaar xcllnt@mac.com From onemda at gmail.com Mon Feb 16 14:54:10 2009 From: onemda at gmail.com (Paul B. Mahol) Date: Mon Feb 16 14:54:17 2009 Subject: USB support in NDIS -- IFF_NEEDSGIANT? In-Reply-To: <200902162127.12209.hselasky@c2i.net> References: <20090216153519.GB4723@citylink.fud.org.nz> <200902161755.07491.hselasky@freebsd.org> <200902162127.12209.hselasky@c2i.net> Message-ID: <3a142e750902161432m15d8c316g6a409d216e9c7053@mail.gmail.com> On 2/16/09, Hans Petter Selasky wrote: > Hi, > > As long as there are locking mechanisms like this: > > void > KeAcquireSpinLockAtDpcLevel(kspin_lock *lock) > { > while (atomic_cmpset_acq_int((volatile u_int *)lock, 0, 1) == 0) > /* sit and spin */; > > return; > } > > inside if_ndis, the whole of NDIS needs to run under one lock. What is the > name of the "NDIS Giant Lock" after that "Giant" is removed from NDIS? > > --HPS > > On Monday 16 February 2009, Hans Petter Selasky wrote: >> On Monday 16 February 2009, Andrew Thompson wrote: >> > On Mon, Feb 16, 2009 at 11:33:18AM +0000, Robert Watson wrote: >> > > Dear all: >> > >> > I had promised Weongyo that I would convert ndis to USB2 but have been a >> > bit busy. Anyone else welcome to pick this up in the mean time. >> >> I can take care of it. Will be back in some hours or tomorrow with >> patches. >> >> How can I test the if_ndis is working USB-wise? >> >> I assume the latest files are in -current. >> >> --HPS > > > _______________________________________________ > freebsd-usb@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-usb > To unsubscribe, send any mail to "freebsd-usb-unsubscribe@freebsd.org" > The whole purpose of IFF_NEEDSGIANT is because usb1 *needs* it. I'm currenly using my own custom if_ndis/ndis code with usb stuff removed and it works fine without that flag. Anyway, usb2 is going to replace usb1 very soon and in that case if_ndis & ndis will stop working. So comment out whole ndisulator from build until it get ported to usb2. -- Paul From imp at bsdimp.com Mon Feb 16 15:15:53 2009 From: imp at bsdimp.com (M. Warner Losh) Date: Mon Feb 16 15:18:43 2009 Subject: USB2+umass: root mount fails In-Reply-To: References: Message-ID: <20090216.161346.1176917525.imp@bsdimp.com> In message: Marcel Moolenaar writes: : Before I dig into the code, what's the current status of : root mounts on USB mass storage devices? First, there's a kludge-o-round that is similar to your "sleep 10" that you've added. It loops waiting for more devices to show up if the desired root file system hasn't appeared yet. There's no way for hot-plug busses to tell the kernel "I've tried my best to enumerate everything on my bus, and I'm done" Warner From xcllnt at mac.com Mon Feb 16 15:52:11 2009 From: xcllnt at mac.com (Marcel Moolenaar) Date: Mon Feb 16 15:52:17 2009 Subject: USB2+umass: root mount fails In-Reply-To: <20090216.161346.1176917525.imp@bsdimp.com> References: <20090216.161346.1176917525.imp@bsdimp.com> Message-ID: <741FAA3B-B91A-4A23-B47F-21141A8D0B5D@mac.com> On Feb 16, 2009, at 3:13 PM, M. Warner Losh wrote: > In message: > Marcel Moolenaar writes: > : Before I dig into the code, what's the current status of > : root mounts on USB mass storage devices? > > First, there's a kludge-o-round that is similar to your "sleep 10" > that you've added. It loops waiting for more devices to show up if > the desired root file system hasn't appeared yet. > > There's no way for hot-plug busses to tell the kernel "I've tried my > best to enumerate everything on my bus, and I'm done" Of course there is. Any and all USB hubs have a certain number of ports. You can trivially iterate over all of them and declare completion when you've tried them all. Recursion is also not a big deal. When you find a HUB underneath a port, you iterate over all the ports of that downstream hub before you declare completion of the USB discovery process. When the USB discovery process is done, you release the root mount lock... So what's the problem? -- Marcel Moolenaar xcllnt@mac.com From xcllnt at mac.com Mon Feb 16 16:21:05 2009 From: xcllnt at mac.com (Marcel Moolenaar) Date: Mon Feb 16 16:21:12 2009 Subject: USB2+umass: timing related bug (machine check abort) Message-ID: Context: MACHINE=ia64, CPU=Montecito I'm running into a timing related MCA. In short: ... umass0: on usbus2 umass0: SCSI over Bulk-Only; quirks = 0x0000 umass0:2:0:-1: Attached to scbus2 *** machine check abort *** *********************************************************** * ROM Version : 01.05 * ROM Date : 11/06/2006 * BMC Version : 05.06 *********************************************************** ... When I enable EHCI debugging (level 99) this does not happen and between the debug output, I see: ... (probe0:umass-sim0:0:0:0): TEST UNIT READY. CDB: 0 0 0 0 0 0 (probe0:umass-sim0:0:0:0): CAM Status: SCSI Status Error (probe0:umass-sim0:0:0:0): SCSI Status: Check Condition (probe0:umass-sim0:0:0:0): UNIT ATTENTION asc:29,0 (probe0:umass-sim0:0:0:0): Power on, reset, or bus device reset occurred (probe0:umass-sim0:0:0:0): Retrying Command (per Sense Data) ... (probe0:umass-sim0:0:0:0): TEST UNIT READY. CDB: 0 0 0 0 0 0 (probe0:umass-sim0:0:0:0): CAM Status: SCSI Status Error (probe0:umass-sim0:0:0:0): SCSI Status: Check Condition (probe0:umass-sim0:0:0:0): NOT READY asc:3a,0 (probe0:umass-sim0:0:0:0): Medium not present (probe0:umass-sim0:0:0:0): Unretryable error ... ehcd0 at umass-sim0 bus 0 target 0 lun 0 cd0: Removable CD-ROM SCSI-0 device cd0: 40.000MB/s transfers cd0: Attempt to query device size failed: NOT READY, Medium not present ... MCA error dumps tells me that it's PCI related. I suspect it's a race condition caused by the HCD writing/updating operational state at the same time that the HC is accessing it. I have 2 instruction pointers. The first is one where an interrupt last occured: IP=0xe0000000041cf810 (gdb) l *0xe0000000041cf810 0xe0000000041cf810 is in ehci_root_ctrl_done (/nfs/freebsd/base/head/ sys/dev/usb2/controller/ehci2.c:3307). 3302 std->err = USB_ERR_IOERROR; 3303 goto done; 3304 } 3305 v = EOREAD4(sc, EHCI_PORTSC(index)); 3306 DPRINTFN(9, "port status=0x%04x\n", v); 3307 if (sc->sc_flags & EHCI_SCFLG_FORCESPEED) { 3308 if ((v & 0xc000000) == 0x8000000) 3309 i = UPS_HIGH_SPEED; 3310 else if ((v & 0xc000000) == 0x4000000) 3311 i = UPS_LOW_SPEED; The second is when the MCA happened: IP=0xe00000000420d8b0 (gdb) l *0xe00000000420d8b0 0xe00000000420d8b0 is in usb2_transfer_start (/nfs/freebsd/base/head/ sys/dev/usb2/core/usb2_transfer.c:1577). 1572 { 1573 if (xfer == NULL) { 1574 /* transfer is gone */ 1575 return; 1576 } 1577 USB_XFER_LOCK_ASSERT(xfer, MA_OWNED); 1578 1579 /* mark the USB transfer started */ 1580 1581 if (!xfer->flags_int.started) { The last access to the EHCI registers was through register 0x6c, which corresponds to PORTSC(3). This matches the first IP. The MCA is caused by an error on the PCI bus, most likely an invalid inbound address: **** MEMORY ERROR STRUCTURE **** MEM_ERR_STRUCT_VALID 0x0000000000000201 **** PLATFORM_SPECIFIC_ERROR_INFO **** VALIDATION_BITS 0x000000000000007b PLATFORM_ERROR_STATUS 0x0000000000421200 PLATFORM_REQUESTOR_ID 0x0000000000000000 PLATFORM_RESPONDER_ID 0x0000000000000000 PLATFORM_TARGET_ID 0x000000003fde6000 PLATFORM_BUS_SPECIFIC_DATA 0x0000000000107628 PLATFORM_OEM_COMPONENT_ID[0] 0x000000004033103c PLATFORM_OEM_COMPONENT_ID[1] 0x0000000000000000 PLATFORM_OEM_DEVICE_PATH 0x0000000000000000 .... HP_TITAN_PLATFORM_DATA ..... ERROR_LOG_EN 0x0000008000003dff ERROR_SIG_EN 0x0000200000002117 ERROR_STATUS 0x0000000000001000 ERROR_OVFL 0x0000000000001000 ERROR_FIRST 0x0000000000000000 AP_ADDRa 0x0000000000000000 AP_ADDRb 0x0000000000000000 ST_ADDRa 0x0000000000000000 ST_ADDRb 0x0000000000000000 RT_ADDRa 0x0000000000000000 RT_ADDRb 0x0000000000000000 RP_ADDRa 0x0000000000000000 RP_ADDRb 0x0000000000000000 LE_ADDRa 0x503800003fde6000 LE_ADDRb 0xc020000000030118 ST_TO 0x00000000fffffff3 PT_TO 0x00000000ffffffff RT_TO 0x000000009e8c6100 **** PCI BUS REGISTERS **** PCI_BUS_ERROR_VALID 0x0000000000000001 **** PLATFORM_PCI_BUS_ERROR_INFO **** VALIDATION_BITS 0x00000000000007cf PCI_BUS_ERROR_STATUS 0x0000000000091200 PCI_BUS_ERROR_TYPE 0x0000000000000000 PCI_BUS_ID 0x0000000000000000 PCI_BUS_ADDRESS 0x00000000fc2fa5d0 PCI_BUS_DATA 0x0000000000000000 PCI_BUS_CMD 0x0000000000000000 PCI_BUS_REQUESTOR_ID 0x0000000000001000 PCI_BUS_COMPLETER_ID 0x00000000fed20000 PCI_BUS_TARGET_ID 0x00000000fc2fa5d0 PCI_BUS_OEM_ID[0] 0x000000000000122e PCI_BUS_OEM_ID[1] 0x0000000000000000 .... HP_MERCURY_DATA .... CELL_NUMBER 0x0000000000000000 SBA_NUMBER 0x0000000000000000 ROPE_NUMBER 0x0000000000000000 ERROR_STATUS 0x000000010000021a ERROR_MASTER_ID_LOG 0x0000000000000008 INBOUND_ERR_ADDRESS 0x00000000fc2fa5d0 INBOUND_ERR_ATTRIBUTE 0x2000000000000000 COMPLETION_MESSAGE_LOG 0x0000000000000000 OUTBOUND_ERR_ADDRESS 0x0000000000000000 ERROR_CONFIG 0x0000000000001d50 STATUS_INFO_CONTROL 0x0000000000000048 FUNC_ID 0x0ab00146122e103c CAPABILITIES_LIST 0x0f00023700200002 AGP_COMMAND 0x0000000000000000 PCIX_CAPABILITIES 0x0013ff0000010007 OLR_CONTROL 0x00023e1b00032403 CLOCK_CONTROL 0x0000000000000048 BUS_MODE 0x9da874ae36d58460 Some more background information: \begin{log} ... FreeBSD 8.0-CURRENT #28 r188699M: Mon Feb 16 14:51:49 PST 2009 marcel@hob.lan.xcllnt.net:/usr/obj/nfs/freebsd/base/head/sys/HOB ... CPU: Montecito (1594.66-Mhz Itanium 2) ... ohci0: mem 0x88032000-0x88032fff irq 17 at device 2.0 on pci0 ohci0: [ITHREAD] usbus0: on ohci0 ohci1: mem 0x88031000-0x88031fff irq 18 at device 2.1 on pci0 ohci1: [ITHREAD] usbus1: on ohci1 ehci0: mem 0x88030000-0x880300ff irq 19 at device 2.2 on pci0 ehci0: [ITHREAD] usbus2: EHCI version 1.0 usbus2: on ehci0 ... usbus0: 12Mbps Full Speed USB v1.0 usbus1: 12Mbps Full Speed USB v1.0 usbus2: 480Mbps High Speed USB v2.0 ugen0.1: at usbus0 ushub0: on usbus0 ugen1.1: at usbus1 ushub1: on usbus1 ugen2.1: at usbus2 ushub2: on usbus2 ushub1: 2 ports with 2 removable, self powered ushub0: 3 ports with 3 removable, self powered ... ushub2: 5 ports with 5 removable, self powered ugen0.2: at usbus0 uhid0: on usbus0 Symlink: uhid0 -> usb0.2.0.16 ums0: on usbus0 ugen2.2: at usbus2 ums0: 3 buttons and [] coordinates Symlink: ums0 -> usb0.2.1.17 ... \end{log} -- Marcel Moolenaar xcllnt@mac.com From imp at bsdimp.com Mon Feb 16 16:37:04 2009 From: imp at bsdimp.com (M. Warner Losh) Date: Mon Feb 16 16:37:10 2009 Subject: USB2+umass: root mount fails In-Reply-To: <741FAA3B-B91A-4A23-B47F-21141A8D0B5D@mac.com> References: <20090216.161346.1176917525.imp@bsdimp.com> <741FAA3B-B91A-4A23-B47F-21141A8D0B5D@mac.com> Message-ID: <20090216.173544.1555327603.imp@bsdimp.com> In message: <741FAA3B-B91A-4A23-B47F-21141A8D0B5D@mac.com> Marcel Moolenaar writes: : : On Feb 16, 2009, at 3:13 PM, M. Warner Losh wrote: : : > In message: : > Marcel Moolenaar writes: : > : Before I dig into the code, what's the current status of : > : root mounts on USB mass storage devices? : > : > First, there's a kludge-o-round that is similar to your "sleep 10" : > that you've added. It loops waiting for more devices to show up if : > the desired root file system hasn't appeared yet. : > : > There's no way for hot-plug busses to tell the kernel "I've tried my : > best to enumerate everything on my bus, and I'm done" : : Of course there is. Any and all USB hubs have a certain : number of ports. You can trivially iterate over all of : them and declare completion when you've tried them all. The hot-plug busses know. The mountroot code doesn't have a way to wait for the hot-plug busses. : Recursion is also not a big deal. When you find a HUB : underneath a port, you iterate over all the ports of : that downstream hub before you declare completion of : the USB discovery process. : : When the USB discovery process is done, you release : the root mount lock... : : So what's the problem? You're looking on the wrong side of the problem. Warner From xcllnt at mac.com Mon Feb 16 17:37:25 2009 From: xcllnt at mac.com (Marcel Moolenaar) Date: Mon Feb 16 17:37:30 2009 Subject: USB2+umass: root mount fails In-Reply-To: <20090216.173544.1555327603.imp@bsdimp.com> References: <20090216.161346.1176917525.imp@bsdimp.com> <741FAA3B-B91A-4A23-B47F-21141A8D0B5D@mac.com> <20090216.173544.1555327603.imp@bsdimp.com> Message-ID: <6E9B5FF6-685B-427C-87A7-C95850DA5B6F@mac.com> On Feb 16, 2009, at 4:35 PM, M. Warner Losh wrote: > In message: <741FAA3B-B91A-4A23-B47F-21141A8D0B5D@mac.com> > Marcel Moolenaar writes: > : > : On Feb 16, 2009, at 3:13 PM, M. Warner Losh wrote: > : > : > In message: > : > Marcel Moolenaar writes: > : > : Before I dig into the code, what's the current status of > : > : root mounts on USB mass storage devices? > : > > : > First, there's a kludge-o-round that is similar to your "sleep 10" > : > that you've added. It loops waiting for more devices to show up > if > : > the desired root file system hasn't appeared yet. > : > > : > There's no way for hot-plug busses to tell the kernel "I've > tried my > : > best to enumerate everything on my bus, and I'm done" > : > : Of course there is. Any and all USB hubs have a certain > : number of ports. You can trivially iterate over all of > : them and declare completion when you've tried them all. > > The hot-plug busses know. The mountroot code doesn't have a way to > wait for the hot-plug busses. Huh? root_mount_hold() and root_mount_rel() are specifically designed to inform the mountroot code that it needs to wait (or that it should go ahead and mount root). -- Marcel Moolenaar xcllnt@mac.com From imp at bsdimp.com Mon Feb 16 17:57:31 2009 From: imp at bsdimp.com (M. Warner Losh) Date: Mon Feb 16 17:57:37 2009 Subject: USB2+umass: root mount fails In-Reply-To: <6E9B5FF6-685B-427C-87A7-C95850DA5B6F@mac.com> References: <741FAA3B-B91A-4A23-B47F-21141A8D0B5D@mac.com> <20090216.173544.1555327603.imp@bsdimp.com> <6E9B5FF6-685B-427C-87A7-C95850DA5B6F@mac.com> Message-ID: <20090216.185655.1306322018.imp@bsdimp.com> In message: <6E9B5FF6-685B-427C-87A7-C95850DA5B6F@mac.com> Marcel Moolenaar writes: : : On Feb 16, 2009, at 4:35 PM, M. Warner Losh wrote: : : > In message: <741FAA3B-B91A-4A23-B47F-21141A8D0B5D@mac.com> : > Marcel Moolenaar writes: : > : : > : On Feb 16, 2009, at 3:13 PM, M. Warner Losh wrote: : > : : > : > In message: : > : > Marcel Moolenaar writes: : > : > : Before I dig into the code, what's the current status of : > : > : root mounts on USB mass storage devices? : > : > : > : > First, there's a kludge-o-round that is similar to your "sleep 10" : > : > that you've added. It loops waiting for more devices to show up : > if : > : > the desired root file system hasn't appeared yet. : > : > : > : > There's no way for hot-plug busses to tell the kernel "I've : > tried my : > : > best to enumerate everything on my bus, and I'm done" : > : : > : Of course there is. Any and all USB hubs have a certain : > : number of ports. You can trivially iterate over all of : > : them and declare completion when you've tried them all. : > : > The hot-plug busses know. The mountroot code doesn't have a way to : > wait for the hot-plug busses. : : Huh? : root_mount_hold() and root_mount_rel() are specifically : designed to inform the mountroot code that it needs to : wait (or that it should go ahead and mount root). Those must be new :-) Last time I went looking for these, I found #defines that did nothing... usb2 just needs to use them. And cardbus/pccard event loops too... Warner From imp at bsdimp.com Mon Feb 16 18:03:32 2009 From: imp at bsdimp.com (M. Warner Losh) Date: Mon Feb 16 18:04:24 2009 Subject: USB2+umass: root mount fails In-Reply-To: <6E9B5FF6-685B-427C-87A7-C95850DA5B6F@mac.com> References: <741FAA3B-B91A-4A23-B47F-21141A8D0B5D@mac.com> <20090216.173544.1555327603.imp@bsdimp.com> <6E9B5FF6-685B-427C-87A7-C95850DA5B6F@mac.com> Message-ID: <20090216.190312.1756925299.imp@bsdimp.com> In message: <6E9B5FF6-685B-427C-87A7-C95850DA5B6F@mac.com> Marcel Moolenaar writes: : : On Feb 16, 2009, at 4:35 PM, M. Warner Losh wrote: : : > In message: <741FAA3B-B91A-4A23-B47F-21141A8D0B5D@mac.com> : > Marcel Moolenaar writes: : > : : > : On Feb 16, 2009, at 3:13 PM, M. Warner Losh wrote: : > : : > : > In message: : > : > Marcel Moolenaar writes: : > : > : Before I dig into the code, what's the current status of : > : > : root mounts on USB mass storage devices? : > : > : > : > First, there's a kludge-o-round that is similar to your "sleep 10" : > : > that you've added. It loops waiting for more devices to show up : > if : > : > the desired root file system hasn't appeared yet. : > : > : > : > There's no way for hot-plug busses to tell the kernel "I've : > tried my : > : > best to enumerate everything on my bus, and I'm done" : > : : > : Of course there is. Any and all USB hubs have a certain : > : number of ports. You can trivially iterate over all of : > : them and declare completion when you've tried them all. : > : > The hot-plug busses know. The mountroot code doesn't have a way to : > wait for the hot-plug busses. : : Huh? : root_mount_hold() and root_mount_rel() are specifically : designed to inform the mountroot code that it needs to : wait (or that it should go ahead and mount root). r145250 | phk | 2005-04-18 15:21:26 -0600 (Mon, 18 Apr 2005) | 12 lines Add a named reference-count KPI to hold off mounting of the root filesystem. While we wait for holds to be released, print a list of who holds us back once per second. Use the new KPI from GEOM instead of vfs_mount.c calling g_waitidle(). Use the new KPI also from ata. With ATAmkIII's newbusification, ata could narrowly miss the window and ad0 would not exist when we tried to mount root. ---- But it looks like the old usb code didn't call it either... I think old code enumerated right away during boot, while the new code defers the enumeration until events can be processed... Warner From xcllnt at mac.com Mon Feb 16 18:34:21 2009 From: xcllnt at mac.com (Marcel Moolenaar) Date: Mon Feb 16 18:34:27 2009 Subject: USB2+umass: root mount fails In-Reply-To: <20090216.190312.1756925299.imp@bsdimp.com> References: <741FAA3B-B91A-4A23-B47F-21141A8D0B5D@mac.com> <20090216.173544.1555327603.imp@bsdimp.com> <6E9B5FF6-685B-427C-87A7-C95850DA5B6F@mac.com> <20090216.190312.1756925299.imp@bsdimp.com> Message-ID: <7F91349C-7E58-47C8-BB69-3B2F391B4E73@mac.com> On Feb 16, 2009, at 6:03 PM, M. Warner Losh wrote: > : root_mount_hold() and root_mount_rel() are specifically > : designed to inform the mountroot code that it needs to > : wait (or that it should go ahead and mount root). > > But it looks like the old usb code didn't call it either... I think > old code enumerated right away during boot, while the new code defers > the enumeration until events can be processed... Yes, you're right. USB1 used the following: SYSINIT(usb_cold_explore, SI_SUB_CONFIGURE, SI_ORDER_MIDDLE, usb_cold_explore, NULL); SI_SUB_CONFIGURE didn't complete before all USB busses were enumerated. -- Marcel Moolenaar xcllnt@mac.com From weongyo.jeong at gmail.com Mon Feb 16 21:43:47 2009 From: weongyo.jeong at gmail.com (Weongyo Jeong) Date: Mon Feb 16 21:43:58 2009 Subject: USB support in NDIS -- IFF_NEEDSGIANT? In-Reply-To: References: Message-ID: <20090217052121.GB86244@weongyo.cdnetworks.kr> On Mon, Feb 16, 2009 at 11:33:18AM +0000, Robert Watson wrote: > > Dear all: > > As you know, I've been gradually working to eliminate all non-MPSAFE > network device driver infrastructure for 8.0, having removed non-MPSAFE > network protocol infrastructure in 7.0. In reviewing remaining drivers > using IFF_NEEDSGIANT, I spotted this in the NDIS code: > > 718 if_initname(ifp, device_get_name(dev), device_get_unit(dev)); > 719 ifp->if_mtu = ETHERMTU; > 720 ifp->if_flags = IFF_BROADCAST | IFF_SIMPLEX | IFF_MULTICAST; > 721 if (sc->ndis_iftype == PNPBus) > 722 ifp->if_flags |= IFF_NEEDSGIANT; > 723 ifp->if_ioctl = ndis_ioctl; > 724 ifp->if_start = ndis_start; > 725 ifp->if_init = ndis_init; > > Having taken a glance, it looks like this was added specifically to support > USB devices attached via NDIS. AFAIK all of usb wireless drivers had it so I couldn't avoid it when I had implemented. > With the new USB code, are NDIS drivers still supported? I think that it would be supported at 8.0 > And in the new world order, is this IFF_NEEDSGIANT still required? Probably we can remove the IFF_NEEDSGIANT flags at the new USB code. > Can I simply remove it once the old USB code is on the way out the > door? IMHO yes I think. > (Note that the plan is to remove all device drivers that still require > IFF_NEEDSGIANT some time before 8.0, probably starting with disabling them > from the build in about 2-3 weeks). regards, Weongyo Jeong From hselasky at c2i.net Mon Feb 16 23:53:45 2009 From: hselasky at c2i.net (Hans Petter Selasky) Date: Mon Feb 16 23:53:52 2009 Subject: USB2+umass: root mount fails In-Reply-To: <7F91349C-7E58-47C8-BB69-3B2F391B4E73@mac.com> References: <741FAA3B-B91A-4A23-B47F-21141A8D0B5D@mac.com> <20090216.190312.1756925299.imp@bsdimp.com> <7F91349C-7E58-47C8-BB69-3B2F391B4E73@mac.com> Message-ID: <200902170856.11631.hselasky@c2i.net> On Tuesday 17 February 2009, Marcel Moolenaar wrote: > On Feb 16, 2009, at 6:03 PM, M. Warner Losh wrote: > > : root_mount_hold() and root_mount_rel() are specifically > > : designed to inform the mountroot code that it needs to > > : wait (or that it should go ahead and mount root). > > > > But it looks like the old usb code didn't call it either... I think > > old code enumerated right away during boot, while the new code defers > > the enumeration until events can be processed... > > Yes, you're right. USB1 used the following: > > SYSINIT(usb_cold_explore, SI_SUB_CONFIGURE, SI_ORDER_MIDDLE, > usb_cold_explore, NULL); > > SI_SUB_CONFIGURE didn't complete before all USB busses > were enumerated. I would really prefer that first time USB enumeration is not synchronous. This has to do with startup timing. It simply wastes a lot of time to wait for all the busses to be probed in serial. Sure it works nice with a USB keyboard and a USB mouse, but when you have a couple of USB HUBs and +8 devices connected, it simply speeds up the boot time so that you reach the root prompt by the time you would else have done the mount root mfs. If the mountroot code cannot find the disk, it should sleep and loop. --HPS From hselasky at c2i.net Tue Feb 17 00:04:46 2009 From: hselasky at c2i.net (Hans Petter Selasky) Date: Tue Feb 17 00:04:52 2009 Subject: USB2+umass: timing related bug (machine check abort) In-Reply-To: References: Message-ID: <200902170907.12043.hselasky@c2i.net> On Tuesday 17 February 2009, Marcel Moolenaar wrote: > Context: MACHINE=ia64, CPU=Montecito > > I'm running into a timing related MCA. In short: > ... > umass0: addr 2> on usbus2 > umass0: SCSI over Bulk-Only; quirks = 0x0000 > umass0:2:0:-1: Attached to scbus2 > *** machine check abort *** > *********************************************************** > * ROM Version : 01.05 > * ROM Date : 11/06/2006 > * BMC Version : 05.06 > *********************************************************** > ... > > When I enable EHCI debugging (level 99) this does not happen > and between the debug output, I see: > It looks like there is a timing issue there. I suspect that someone is trying to setup a USB transfer before usb2_transfer_setup() has returned. Could you get into the kernel debugger and dump "xfer->xroot" and "xfer->xroot->xfer_mtx". --HPS From imp at bsdimp.com Tue Feb 17 07:55:21 2009 From: imp at bsdimp.com (M. Warner Losh) Date: Tue Feb 17 07:55:27 2009 Subject: USB2+umass: root mount fails In-Reply-To: <200902170856.11631.hselasky@c2i.net> References: <20090216.190312.1756925299.imp@bsdimp.com> <7F91349C-7E58-47C8-BB69-3B2F391B4E73@mac.com> <200902170856.11631.hselasky@c2i.net> Message-ID: <20090217.085424.775975548.imp@bsdimp.com> In message: <200902170856.11631.hselasky@c2i.net> Hans Petter Selasky writes: : On Tuesday 17 February 2009, Marcel Moolenaar wrote: : > On Feb 16, 2009, at 6:03 PM, M. Warner Losh wrote: : > > : root_mount_hold() and root_mount_rel() are specifically : > > : designed to inform the mountroot code that it needs to : > > : wait (or that it should go ahead and mount root). : > > : > > But it looks like the old usb code didn't call it either... I think : > > old code enumerated right away during boot, while the new code defers : > > the enumeration until events can be processed... : > : > Yes, you're right. USB1 used the following: : > : > SYSINIT(usb_cold_explore, SI_SUB_CONFIGURE, SI_ORDER_MIDDLE, : > usb_cold_explore, NULL); : > : > SI_SUB_CONFIGURE didn't complete before all USB busses : > were enumerated. : : I would really prefer that first time USB enumeration is not synchronous. This : has to do with startup timing. It simply wastes a lot of time to wait for all : the busses to be probed in serial. Sure it works nice with a USB keyboard and : a USB mouse, but when you have a couple of USB HUBs and +8 devices connected, : it simply speeds up the boot time so that you reach the root prompt by the : time you would else have done the mount root mfs. : : If the mountroot code cannot find the disk, it should sleep and loop. I think this is a weak argument. I'm strongly in favor of the usb1 behavior here. Warner From hselasky at c2i.net Tue Feb 17 08:22:36 2009 From: hselasky at c2i.net (Hans Petter Selasky) Date: Tue Feb 17 08:22:42 2009 Subject: USB2+umass: timing related bug (machine check abort) In-Reply-To: References: Message-ID: <200902171725.00271.hselasky@c2i.net> On Tuesday 17 February 2009, Marcel Moolenaar wrote: > Context: MACHINE=ia64, CPU=Montecito > > I'm running into a timing related MCA. In short: > ... > umass0: addr 2> on usbus2 > umass0: SCSI over Bulk-Only; quirks = 0x0000 > umass0:2:0:-1: Attached to scbus2 > *** machine check abort *** > *********************************************************** > * ROM Version : 01.05 > * ROM Date : 11/06/2006 > * BMC Version : 05.06 > *********************************************************** > ... > > When I enable EHCI debugging (level 99) this does not happen > and between the debug output, I see: > Hi, I think that the problem is not USB related, but it happens at a point in time where the UMASS USB transfer is half-setup. When the UMASS poll callback is called at the wrong time, then you will get a NULL pointer access. Try the following patch and report back: http://perforce.freebsd.org/chv.cgi?CH=157847 --HPS From xcllnt at mac.com Tue Feb 17 10:36:48 2009 From: xcllnt at mac.com (Marcel Moolenaar) Date: Tue Feb 17 10:36:54 2009 Subject: USB2+umass: root mount fails In-Reply-To: <200902170856.11631.hselasky@c2i.net> References: <741FAA3B-B91A-4A23-B47F-21141A8D0B5D@mac.com> <20090216.190312.1756925299.imp@bsdimp.com> <7F91349C-7E58-47C8-BB69-3B2F391B4E73@mac.com> <200902170856.11631.hselasky@c2i.net> Message-ID: <55BE8F46-B338-4609-B0DC-F1C90350029D@mac.com> On Feb 16, 2009, at 11:56 PM, Hans Petter Selasky wrote: > On Tuesday 17 February 2009, Marcel Moolenaar wrote: >> On Feb 16, 2009, at 6:03 PM, M. Warner Losh wrote: >>> : root_mount_hold() and root_mount_rel() are specifically >>> : designed to inform the mountroot code that it needs to >>> : wait (or that it should go ahead and mount root). >>> >>> But it looks like the old usb code didn't call it either... I think >>> old code enumerated right away during boot, while the new code >>> defers >>> the enumeration until events can be processed... >> >> Yes, you're right. USB1 used the following: >> >> SYSINIT(usb_cold_explore, SI_SUB_CONFIGURE, SI_ORDER_MIDDLE, >> usb_cold_explore, NULL); >> >> SI_SUB_CONFIGURE didn't complete before all USB busses >> were enumerated. > > I would really prefer that first time USB enumeration is not > synchronous. You misunderstand. I wasn't suggesting you changed USB2 to do the same thing as USB1. I was merely pointing out how USB1 did it and why root mounts worked. I think the USB2 approacj is better and as you say, we just need to hold the root mount until we're done. -- Marcel Moolenaar xcllnt@mac.com From xcllnt at mac.com Wed Feb 18 19:17:03 2009 From: xcllnt at mac.com (Marcel Moolenaar) Date: Wed Feb 18 19:17:10 2009 Subject: USB2+umass: timing related bug (machine check abort) In-Reply-To: <200902171725.00271.hselasky@c2i.net> References: <200902171725.00271.hselasky@c2i.net> Message-ID: <2E17A9B1-A09D-473C-92A7-6E30B646B3C4@mac.com> On Feb 17, 2009, at 8:24 AM, Hans Petter Selasky wrote: > On Tuesday 17 February 2009, Marcel Moolenaar wrote: >> Context: MACHINE=ia64, CPU=Montecito >> >> I'm running into a timing related MCA. In short: >> ... >> umass0: > addr 2> on usbus2 >> umass0: SCSI over Bulk-Only; quirks = 0x0000 >> umass0:2:0:-1: Attached to scbus2 >> *** machine check abort *** >> *********************************************************** >> * ROM Version : 01.05 >> * ROM Date : 11/06/2006 >> * BMC Version : 05.06 >> *********************************************************** >> ... >> >> When I enable EHCI debugging (level 99) this does not happen >> and between the debug output, I see: >> > > Hi, > > I think that the problem is not USB related, but it happens at a > point in time > where the UMASS USB transfer is half-setup. When the UMASS poll > callback is > called at the wrong time, then you will get a NULL pointer access. > Try the > following patch and report back: > > http://perforce.freebsd.org/chv.cgi?CH=157847 No change. -- Marcel Moolenaar xcllnt@mac.com From thompsa at FreeBSD.org Wed Feb 18 21:02:06 2009 From: thompsa at FreeBSD.org (Andrew Thompson) Date: Wed Feb 18 21:02:13 2009 Subject: USB2+umass: root mount fails In-Reply-To: <20090217.085424.775975548.imp@bsdimp.com> References: <20090216.190312.1756925299.imp@bsdimp.com> <7F91349C-7E58-47C8-BB69-3B2F391B4E73@mac.com> <200902170856.11631.hselasky@c2i.net> <20090217.085424.775975548.imp@bsdimp.com> Message-ID: <20090219050200.GA84647@citylink.fud.org.nz> On Tue, Feb 17, 2009 at 08:54:24AM -0700, M. Warner Losh wrote: > In message: <200902170856.11631.hselasky@c2i.net> > Hans Petter Selasky writes: > : On Tuesday 17 February 2009, Marcel Moolenaar wrote: > : > > But it looks like the old usb code didn't call it either... I think > : > > old code enumerated right away during boot, while the new code defers > : > > the enumeration until events can be processed... > : > > : > Yes, you're right. USB1 used the following: > : > > : > SYSINIT(usb_cold_explore, SI_SUB_CONFIGURE, SI_ORDER_MIDDLE, > : > usb_cold_explore, NULL); > : > > : > SI_SUB_CONFIGURE didn't complete before all USB busses > : > were enumerated. > : > : I would really prefer that first time USB enumeration is not synchronous. This > : has to do with startup timing. It simply wastes a lot of time to wait for all > : the busses to be probed in serial. Sure it works nice with a USB keyboard and > : a USB mouse, but when you have a couple of USB HUBs and +8 devices connected, > : it simply speeds up the boot time so that you reach the root prompt by the > : time you would else have done the mount root mfs. > : > : If the mountroot code cannot find the disk, it should sleep and loop. > > I think this is a weak argument. I'm strongly in favor of the usb1 > behavior here. I think its slightly more complex that adding a cold explore task. Most of the USB2 periperhel drivers defer a portion of their attach to a thread task, a change which needs to be reverted first. As others have said both the probe and attach must be synchronous. Andrew From imp at bsdimp.com Wed Feb 18 21:25:31 2009 From: imp at bsdimp.com (M. Warner Losh) Date: Wed Feb 18 21:25:37 2009 Subject: USB2+umass: root mount fails In-Reply-To: <20090219050200.GA84647@citylink.fud.org.nz> References: <200902170856.11631.hselasky@c2i.net> <20090217.085424.775975548.imp@bsdimp.com> <20090219050200.GA84647@citylink.fud.org.nz> Message-ID: <20090218.222301.1655042223.imp@bsdimp.com> In message: <20090219050200.GA84647@citylink.fud.org.nz> Andrew Thompson writes: : On Tue, Feb 17, 2009 at 08:54:24AM -0700, M. Warner Losh wrote: : > In message: <200902170856.11631.hselasky@c2i.net> : > Hans Petter Selasky writes: : > : On Tuesday 17 February 2009, Marcel Moolenaar wrote: : > : > > But it looks like the old usb code didn't call it either... I think : > : > > old code enumerated right away during boot, while the new code defers : > : > > the enumeration until events can be processed... : > : > : > : > Yes, you're right. USB1 used the following: : > : > : > : > SYSINIT(usb_cold_explore, SI_SUB_CONFIGURE, SI_ORDER_MIDDLE, : > : > usb_cold_explore, NULL); : > : > : > : > SI_SUB_CONFIGURE didn't complete before all USB busses : > : > were enumerated. : > : : > : I would really prefer that first time USB enumeration is not synchronous. This : > : has to do with startup timing. It simply wastes a lot of time to wait for all : > : the busses to be probed in serial. Sure it works nice with a USB keyboard and : > : a USB mouse, but when you have a couple of USB HUBs and +8 devices connected, : > : it simply speeds up the boot time so that you reach the root prompt by the : > : time you would else have done the mount root mfs. : > : : > : If the mountroot code cannot find the disk, it should sleep and loop. : > : > I think this is a weak argument. I'm strongly in favor of the usb1 : > behavior here. : : I think its slightly more complex that adding a cold explore task. Most : of the USB2 periperhel drivers defer a portion of their attach to a : thread task, a change which needs to be reverted first. As others have : said both the probe and attach must be synchronous. That's true too. The point I was trying to make wasn't that we needed a cold explore task, but more that usb should know when it is done with the probe phase and then do what other hot-plug busses have started doing. See my recent changes to dev/pccbb for one example. Warner From hselasky at c2i.net Thu Feb 19 00:24:16 2009 From: hselasky at c2i.net (Hans Petter Selasky) Date: Thu Feb 19 00:24:22 2009 Subject: USB2+umass: root mount fails In-Reply-To: <20090219050200.GA84647@citylink.fud.org.nz> References: <20090216.190312.1756925299.imp@bsdimp.com> <20090217.085424.775975548.imp@bsdimp.com> <20090219050200.GA84647@citylink.fud.org.nz> Message-ID: <200902190926.42992.hselasky@c2i.net> Hi, On Thursday 19 February 2009, Andrew Thompson wrote: > I think its slightly more complex that adding a cold explore task. Cold explore is not possible any more and adds unneccesary complexity to the USB code. USB is dependant on processes/threads/tasks to execute. > Most of the USB2 periperhel drivers defer a portion of their attach to a > thread task, a change which needs to be reverted first. As others have > said both the probe and attach must be synchronous. Do you understand why probe and attach is currently partially deferred in some drivers? It has to do with the ability to quickly recover if a device is suddenly detached when doing multiple sequential USB operations towards a USB device. I have the impression that you are not thinking about failure cases like constant timeouts. What makes the picture additionaly complicated is that there are multiple sources of detach, that do not all go through the USB stack. kldunload does not go through the USB stack. set_config does. device_detach does. Another point I have is that we want to do operations in parallell. I see no reason at all to slow down the USB enumeration at boot. We are talking about a considerable amount of time! Instead the system needs to be changed. If you try to mount a device which is not present, then you need to retry mounting that device if some re-try flag is set. Adding some flag to "struct usb2_device" saying that the device is gone will almost solve the problem, but it does not cover the kldunload case. Also it can be quite dangerous if attach is hanging and we do a kldunload. Then I don't know what will happen. And we don't want to open that window by making USB attach always synchronous. Neither should we depend on the EHCI/OHCI/UHCI hardware to simply eject transfers on dissappeared devices, see three strikes and you are gone rule. --HPS From alfred at freebsd.org Thu Feb 19 07:39:09 2009 From: alfred at freebsd.org (Alfred Perlstein) Date: Thu Feb 19 07:39:22 2009 Subject: USB2+umass: root mount fails In-Reply-To: <200902190926.42992.hselasky@c2i.net> References: <20090216.190312.1756925299.imp@bsdimp.com> <20090217.085424.775975548.imp@bsdimp.com> <20090219050200.GA84647@citylink.fud.org.nz> <200902190926.42992.hselasky@c2i.net> Message-ID: <20090219153909.GK75810@elvis.mu.org> I really don't understand why it can't be made an option. The cold probe can be done right before mountroot where threads are available. Not doing this deterministically is bad, but forcing slow behavior as the only option seems equally bad. Offering choice seems to be the right solution. -Alfred * Hans Petter Selasky [090219 00:24] wrote: > Hi, > > On Thursday 19 February 2009, Andrew Thompson wrote: > > > I think its slightly more complex that adding a cold explore task. > > Cold explore is not possible any more and adds unneccesary complexity to the > USB code. USB is dependant on processes/threads/tasks to execute. > > > Most of the USB2 periperhel drivers defer a portion of their attach to a > > thread task, a change which needs to be reverted first. As others have > > said both the probe and attach must be synchronous. > > Do you understand why probe and attach is currently partially deferred in some > drivers? It has to do with the ability to quickly recover if a device is > suddenly detached when doing multiple sequential USB operations towards a USB > device. I have the impression that you are not thinking about failure cases > like constant timeouts. What makes the picture additionaly complicated is > that there are multiple sources of detach, that do not all go through the USB > stack. > > kldunload does not go through the USB stack. > set_config does. > device_detach does. > > Another point I have is that we want to do operations in parallell. I see no > reason at all to slow down the USB enumeration at boot. We are talking about > a considerable amount of time! Instead the system needs to be changed. If you > try to mount a device which is not present, then you need to retry mounting > that device if some re-try flag is set. > > Adding some flag to "struct usb2_device" saying that the device is gone will > almost solve the problem, but it does not cover the kldunload case. Also it > can be quite dangerous if attach is hanging and we do a kldunload. Then I > don't know what will happen. And we don't want to open that window by making > USB attach always synchronous. Neither should we depend on the EHCI/OHCI/UHCI > hardware to simply eject transfers on dissappeared devices, see three strikes > and you are gone rule. > > --HPS > _______________________________________________ > freebsd-usb@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-usb > To unsubscribe, send any mail to "freebsd-usb-unsubscribe@freebsd.org" -- - Alfred Perlstein From imp at bsdimp.com Thu Feb 19 08:07:13 2009 From: imp at bsdimp.com (M. Warner Losh) Date: Thu Feb 19 08:07:19 2009 Subject: USB2+umass: root mount fails In-Reply-To: <200902190926.42992.hselasky@c2i.net> References: <20090217.085424.775975548.imp@bsdimp.com> <20090219050200.GA84647@citylink.fud.org.nz> <200902190926.42992.hselasky@c2i.net> Message-ID: <20090219.090621.-786048162.imp@bsdimp.com> In message: <200902190926.42992.hselasky@c2i.net> Hans Petter Selasky writes: : Do you understand why probe and attach is currently partially deferred in some : drivers? It has to do with the ability to quickly recover if a device is : suddenly detached when doing multiple sequential USB operations towards a USB : device. I have the impression that you are not thinking about failure cases : like constant timeouts. What makes the picture additionaly complicated is : that there are multiple sources of detach, that do not all go through the USB : stack. : : kldunload does not go through the USB stack. : set_config does. : device_detach does. You are doing something wrong then. All of these *DO* go through newbus for proper drivers. If not, then that's a bug in newbus and should be fixed there, not kludged around. What, exactly, is the problem with kldunload? : Another point I have is that we want to do operations in parallell. I see no : reason at all to slow down the USB enumeration at boot. We are talking about : a considerable amount of time! Instead the system needs to be changed. If you : try to mount a device which is not present, then you need to retry mounting : that device if some re-try flag is set. None of this prevents the usb stack from signaling when the probe/attach is done. You can't expect mountroot to wait forever. Also, there are times when there's multiple disks available that could be root. Just waiting for root is also bad because that root might not ever get there. There has to be some sanity timeout. By properly signaling that the operation is complete, you can have better semantics. All the other drivers in the system can accommodate this paradigm. What makes usb so special? : Adding some flag to "struct usb2_device" saying that the device is gone will : almost solve the problem, but it does not cover the kldunload case. Also it : can be quite dangerous if attach is hanging and we do a kldunload. Then I : don't know what will happen. And we don't want to open that window by making : USB attach always synchronous. Neither should we depend on the EHCI/OHCI/UHCI : hardware to simply eject transfers on dissappeared devices, see three strikes : and you are gone rule. These sound like they might be bugs in newbus. Can you elaborate on the details? Warner From hselasky at c2i.net Thu Feb 19 08:26:57 2009 From: hselasky at c2i.net (Hans Petter Selasky) Date: Thu Feb 19 08:27:04 2009 Subject: USB2+umass: root mount fails In-Reply-To: <20090219.090621.-786048162.imp@bsdimp.com> References: <20090217.085424.775975548.imp@bsdimp.com> <200902190926.42992.hselasky@c2i.net> <20090219.090621.-786048162.imp@bsdimp.com> Message-ID: <200902191729.18715.hselasky@c2i.net> Hi Warner, On Thursday 19 February 2009, M. Warner Losh wrote: > In message: <200902190926.42992.hselasky@c2i.net> > > Hans Petter Selasky writes: > : Do you understand why probe and attach is currently partially deferred in > : some drivers? It has to do with the ability to quickly recover if a > : device is suddenly detached when doing multiple sequential USB operations > : towards a USB device. I have the impression that you are not thinking > : about failure cases like constant timeouts. What makes the picture > : additionaly complicated is that there are multiple sources of detach, > : that do not all go through the USB stack. > : > : kldunload does not go through the USB stack. > : set_config does. > : device_detach does. > > You are doing something wrong then. All of these *DO* go through > newbus for proper drivers. If not, then that's a bug in newbus and > should be fixed there, not kludged around. Yes, but they do not go through the USB stack [thread]. When you are running kldunload then the kldunload process is doing the detach(). This can crash with the USB explore thread adding and removing devices. Last time I checked the newbus attach/detach was only protected by "Giant" which is exited when an operation is sleeping. This Giant needs to be replaced by a sleep-enabled lock, like a SX lock, which will not get exited when we are calling msleep(), pause() or cv_wait(). > > None of this prevents the usb stack from signaling when the > probe/attach is done. It is not a problem to do a synchronous enumeration of the USB stack before mountroot. It just wastes time in my opinion. > You can't expect mountroot to wait forever. > Also, there are times when there's multiple disks available that could > be root. Just waiting for root is also bad because that root might > not ever get there. There has to be some sanity timeout. Yes, you have a point there. I think that fallback options should only kick in after a reasonable timeout. The first non-fallback disk to present itself is selected within a tuneable delay. > By properly > signaling that the operation is complete, you can have better > semantics. Yes, I can make such a function for USB. We know how many USB busses there are after attach and we can keep a refcount which cause a callback when the refcount reaches zero. Does such a function or API already exist that USB can call? And what should such a function do? Should it just signal that it is time to go trying secondary boot options? > All the other drivers in the system can accommodate this > paradigm. What makes usb so special? There is nothing special about USB. > > These sound like they might be bugs in newbus. Can you elaborate on > the details? See top of e-mail. --HPS From thompsa at FreeBSD.org Thu Feb 19 19:37:45 2009 From: thompsa at FreeBSD.org (Andrew Thompson) Date: Thu Feb 19 19:37:58 2009 Subject: CFR: usb switchover patches Message-ID: <20090220033740.GA903@citylink.fud.org.nz> Hi, I have put together a proposed set of changes for moving USB2 to its permanent location. The layout has some differences to how it is right now so I am looking for feedback. The changeover requires that the old usb stack be available until 8.0 is branched and moves it from sys/dev/usb to sys/legacy/dev/usb. The reason for this location is to reduce the changes in #includes (using -I compiler hacks). The patch doesnt show userland changes required for usbdevs and friends but they will be done. Some ports will break. Any that exist solely for the old usb stack can be marked broken (like udesc_dump). I dont know that the fallout will be like for the others, maybe portmgr would be interested in doing a build test. The change roughly goes svn move sys/dev/usb -> sys/legacy/dev/usb svn move sys/dev/usb2 -> sys/dev/usb (with fixups, see below) The patch for the build system can be viewed here, http://people.freebsd.org/~thompsa/usb_layout/usb_xover.diff Now the changes... For starters the '2' will be removed from the filenames but furthermore I want to flatten dev/usb2/core and dev/usb2/include into just dev/usb, keeping the peripheral drivers in their subdirs. Its hard to show with a diff so simply browse the layout here, http://people.freebsd.org/~thompsa/usb_layout/dev/ Please send any minor/nitpick changes to me privately, keeping any list replies to the overall changes. regards, Andrew From thompsa at FreeBSD.org Thu Feb 19 19:51:16 2009 From: thompsa at FreeBSD.org (Andrew Thompson) Date: Thu Feb 19 19:51:23 2009 Subject: CFR: usb switchover patches In-Reply-To: <499E278D.7060406@freebsd.org> References: <20090220033740.GA903@citylink.fud.org.nz> <499E278D.7060406@freebsd.org> Message-ID: <20090220035110.GA3444@citylink.fud.org.nz> On Thu, Feb 19, 2009 at 10:46:21PM -0500, Joe Marcus Clarke wrote: > Andrew Thompson wrote: > > Hi, > > > > > > I have put together a proposed set of changes for moving USB2 to its > > permanent location. The layout has some differences to how it is right > > now so I am looking for feedback. > > What about libusb20? Will this name change, or is this the final name > (same question for the libusb20 functions)? I need to know for hal. > Thanks. As far as I know libusb20 will not change at all. Andrew From marcus at freebsd.org Thu Feb 19 20:08:31 2009 From: marcus at freebsd.org (Joe Marcus Clarke) Date: Thu Feb 19 20:08:37 2009 Subject: CFR: usb switchover patches In-Reply-To: <20090220033740.GA903@citylink.fud.org.nz> References: <20090220033740.GA903@citylink.fud.org.nz> Message-ID: <499E278D.7060406@freebsd.org> Andrew Thompson wrote: > Hi, > > > I have put together a proposed set of changes for moving USB2 to its > permanent location. The layout has some differences to how it is right > now so I am looking for feedback. > > The changeover requires that the old usb stack be available until 8.0 is > branched and moves it from sys/dev/usb to sys/legacy/dev/usb. The reason > for this location is to reduce the changes in #includes (using -I > compiler hacks). The patch doesnt show userland changes required for > usbdevs and friends but they will be done. > > Some ports will break. Any that exist solely for the old usb stack can > be marked broken (like udesc_dump). I dont know that the fallout will be > like for the others, maybe portmgr would be interested in doing a build > test. > > The change roughly goes > > svn move sys/dev/usb -> sys/legacy/dev/usb > svn move sys/dev/usb2 -> sys/dev/usb (with fixups, see below) > > > The patch for the build system can be viewed here, > http://people.freebsd.org/~thompsa/usb_layout/usb_xover.diff > > Now the changes... For starters the '2' will be removed from the > filenames but furthermore I want to flatten dev/usb2/core and > dev/usb2/include into just dev/usb, keeping the peripheral drivers in > their subdirs. Its hard to show with a diff so simply browse the layout > here, http://people.freebsd.org/~thompsa/usb_layout/dev/ > > Please send any minor/nitpick changes to me privately, keeping any list > replies to the overall changes. What about libusb20? Will this name change, or is this the final name (same question for the libusb20 functions)? I need to know for hal. Thanks. Joe -- Joe Marcus Clarke FreeBSD GNOME Team :: gnome@FreeBSD.org FreeNode / #freebsd-gnome http://www.FreeBSD.org/gnome From imp at bsdimp.com Thu Feb 19 20:18:50 2009 From: imp at bsdimp.com (M. Warner Losh) Date: Thu Feb 19 20:18:56 2009 Subject: CFR: usb switchover patches In-Reply-To: <20090220033740.GA903@citylink.fud.org.nz> References: <20090220033740.GA903@citylink.fud.org.nz> Message-ID: <20090219.211735.1528532921.imp@bsdimp.com> In message: <20090220033740.GA903@citylink.fud.org.nz> Andrew Thompson writes: : Hi, : : : I have put together a proposed set of changes for moving USB2 to its : permanent location. The layout has some differences to how it is right : now so I am looking for feedback. : : The changeover requires that the old usb stack be available until 8.0 is : branched and moves it from sys/dev/usb to sys/legacy/dev/usb. The reason : for this location is to reduce the changes in #includes (using -I : compiler hacks). The patch doesnt show userland changes required for : usbdevs and friends but they will be done. : : Some ports will break. Any that exist solely for the old usb stack can : be marked broken (like udesc_dump). I dont know that the fallout will be : like for the others, maybe portmgr would be interested in doing a build : test. : : The change roughly goes : : svn move sys/dev/usb -> sys/legacy/dev/usb : svn move sys/dev/usb2 -> sys/dev/usb (with fixups, see below) : : : The patch for the build system can be viewed here, : http://people.freebsd.org/~thompsa/usb_layout/usb_xover.diff : : Now the changes... For starters the '2' will be removed from the : filenames but furthermore I want to flatten dev/usb2/core and : dev/usb2/include into just dev/usb, keeping the peripheral drivers in : their subdirs. Its hard to show with a diff so simply browse the layout : here, http://people.freebsd.org/~thompsa/usb_layout/dev/ : : Please send any minor/nitpick changes to me privately, keeping any list : replies to the overall changes. While I might want to nitpick here, I'm going to refrain from doing so and just say "Close enough for my tastes, please go ahead." I could argue that there are a number of inconsistencies with historic practice that this (or the original usb2 commit) introduces, we shouldn't hold up this commit on those grounds. Instead, we should get experience with this layout and look to socialize ideas for a reorg post 8.0 that is more comprehensive in nature. This will give people plenty of time to think about it, and a chance for people with competing ideas to flesh them out. Warner From thompsa at FreeBSD.org Thu Feb 19 22:21:33 2009 From: thompsa at FreeBSD.org (Andrew Thompson) Date: Thu Feb 19 22:21:45 2009 Subject: CFR: usb switchover patches In-Reply-To: <20090220033740.GA903@citylink.fud.org.nz> References: <20090220033740.GA903@citylink.fud.org.nz> Message-ID: <20090220062126.GA4137@citylink.fud.org.nz> On Thu, Feb 19, 2009 at 07:37:40PM -0800, Andrew Thompson wrote: > Hi, > > > I have put together a proposed set of changes for moving USB2 to its > permanent location. The layout has some differences to how it is right > now so I am looking for feedback. > > The changeover requires that the old usb stack be available until 8.0 is > branched and moves it from sys/dev/usb to sys/legacy/dev/usb. The reason > for this location is to reduce the changes in #includes (using -I > compiler hacks). The patch doesnt show userland changes required for > usbdevs and friends but they will be done. Also, I wasnt planning on keeping the old usb kernel modules hooked into the build unless someone particularly wants them. They can all still be built into the kernel. Andrew From kazemzad at usc.edu Thu Feb 19 23:00:07 2009 From: kazemzad at usc.edu (abe kazemzadeh) Date: Thu Feb 19 23:00:13 2009 Subject: usb/107827: [ohci] [panic] ohci_add_done addr not found Message-ID: <200902200700.n1K705th054755@freefall.freebsd.org> The following reply was made to PR usb/107827; it has been noted by GNATS. From: abe kazemzadeh To: bug-followup@FreeBSD.org, fstoffel@gmx.de Cc: Subject: Re: usb/107827: [ohci] [panic] ohci_add_done addr not found Date: Thu, 19 Feb 2009 22:28:38 -0800 This isn't really a solution to the bug per se, but a work-around I found was to disable usb keyboard in my bios (I'm using a jetway a210gdms mobo). This gets me passed the initial boot and the keyboard actually works in the installer. I haven't gone thru w/ the installer, but if you'd like a follow up, let me know. Abe From bzeeb-lists at lists.zabbadoz.net Fri Feb 20 02:21:37 2009 From: bzeeb-lists at lists.zabbadoz.net (Bjoern A. Zeeb) Date: Fri Feb 20 02:21:43 2009 Subject: CFR: usb switchover patches In-Reply-To: <20090220062126.GA4137@citylink.fud.org.nz> References: <20090220033740.GA903@citylink.fud.org.nz> <20090220062126.GA4137@citylink.fud.org.nz> Message-ID: <20090220100115.R53478@maildrop.int.zabbadoz.net> On Thu, 19 Feb 2009, Andrew Thompson wrote: > On Thu, Feb 19, 2009 at 07:37:40PM -0800, Andrew Thompson wrote: >> Hi, >> >> >> I have put together a proposed set of changes for moving USB2 to its >> permanent location. The layout has some differences to how it is right >> now so I am looking for feedback. >> >> The changeover requires that the old usb stack be available until 8.0 is >> branched and moves it from sys/dev/usb to sys/legacy/dev/usb. The reason >> for this location is to reduce the changes in #includes (using -I >> compiler hacks). The patch doesnt show userland changes required for >> usbdevs and friends but they will be done. > > Also, I wasnt planning on keeping the old usb kernel modules hooked into > the build unless someone particularly wants them. They can all still be > built into the kernel. what about renaming it to dev/usb1 instead of starting another top level directory in sys/ ? I mean I like legacy and would prefer to move netinet/ in there asap but;-)) /bz -- Bjoern A. Zeeb The greatest risk is not taking one. From IZ-FreeBSD0902-nospam at hs-karlsruhe.de Fri Feb 20 03:40:02 2009 From: IZ-FreeBSD0902-nospam at hs-karlsruhe.de (Ralf Wenk) Date: Fri Feb 20 03:40:08 2009 Subject: usb/131900: Additional product identification code for Logitech QuickCam Pro Message-ID: >Number: 131900 >Category: usb >Synopsis: Additional product identification code for Logitech QuickCam Pro >Confidential: no >Severity: non-critical >Priority: low >Responsible: freebsd-usb >State: open >Quarter: >Keywords: >Date-Required: >Class: update >Submitter-Id: current-users >Arrival-Date: Fri Feb 20 11:40:01 UTC 2009 >Closed-Date: >Last-Modified: >Originator: Ralf Wenk >Release: FreeBSD 7.1-PRERELEASE i386 >Organization: Hochschule Karlsruhe Technik und Wirtschaft - University of Applied Sciences >Environment: System: FreeBSD RZ-FreeBSD1 7.1-PRERELEASE FreeBSD 7.1-PRERELEASE #10: Tue Dec 23 11:36:05 CET 2008 wera0003@RZ-FreeBSD1:/usr/obj/usr/src/sys/fsc-t-diskless i386 >Description: A Logitech QuickCam Pro 9000 gives a product identication code which is not listed in src/sys/dev/usb/usbdevs,v 1.328.2.23. >How-To-Repeat: Plug in the the device. Search in /usr/src/sys/dev/usb/usbdevs after it. ugen0: on uhub0 >Fix: --- usbdevs.diff begins here --- --- /sys/dev/usb/usbdevs 2009-02-19 15:09:51.145275825 +0100 +++ usbdevs 2009-02-20 11:48:37.000000000 +0100 @@ -1599,6 +1599,7 @@ product LOGITECH RB6 0xc503 Cordless keyboard product LOGITECH MX700 0xc506 Cordless optical mouse product LOGITECH QUICKCAMPRO2 0xd001 QuickCam Pro +product LOGITECH QUICKCAMPRO3 0x0990 QuickCam Pro /* Logitec Corp. products */ product LOGITEC LDR_H443SU2 0x0033 DVD Multi-plus unit LDR-H443SU2 --- usbdevs.diff ends here --- >Release-Note: >Audit-Trail: >Unformatted: From imp at bsdimp.com Fri Feb 20 07:31:05 2009 From: imp at bsdimp.com (M. Warner Losh) Date: Fri Feb 20 07:31:12 2009 Subject: CFR: usb switchover patches In-Reply-To: <20090220100115.R53478@maildrop.int.zabbadoz.net> References: <20090220033740.GA903@citylink.fud.org.nz> <20090220062126.GA4137@citylink.fud.org.nz> <20090220100115.R53478@maildrop.int.zabbadoz.net> Message-ID: <20090220.082843.517086508.imp@bsdimp.com> In message: <20090220100115.R53478@maildrop.int.zabbadoz.net> "Bjoern A. Zeeb" writes: : On Thu, 19 Feb 2009, Andrew Thompson wrote: : : > On Thu, Feb 19, 2009 at 07:37:40PM -0800, Andrew Thompson wrote: : >> Hi, : >> : >> : >> I have put together a proposed set of changes for moving USB2 to its : >> permanent location. The layout has some differences to how it is right : >> now so I am looking for feedback. : >> : >> The changeover requires that the old usb stack be available until 8.0 is : >> branched and moves it from sys/dev/usb to sys/legacy/dev/usb. The reason : >> for this location is to reduce the changes in #includes (using -I : >> compiler hacks). The patch doesnt show userland changes required for : >> usbdevs and friends but they will be done. : > : > Also, I wasnt planning on keeping the old usb kernel modules hooked into : > the build unless someone particularly wants them. They can all still be : > built into the kernel. : : what about renaming it to dev/usb1 instead of starting another top : level directory in sys/ ? I mean I like legacy and would prefer to : move netinet/ in there asap but;-)) We'd have to hack all the old usb1 drivers. Moving to sys/legacy/dev/usb means minimal frobbing of the code. From bzeeb-lists at lists.zabbadoz.net Fri Feb 20 07:45:09 2009 From: bzeeb-lists at lists.zabbadoz.net (Bjoern A. Zeeb) Date: Fri Feb 20 07:45:16 2009 Subject: CFR: usb switchover patches In-Reply-To: <20090220.082843.517086508.imp@bsdimp.com> References: <20090220033740.GA903@citylink.fud.org.nz> <20090220062126.GA4137@citylink.fud.org.nz> <20090220100115.R53478@maildrop.int.zabbadoz.net> <20090220.082843.517086508.imp@bsdimp.com> Message-ID: <20090220154049.H53478@maildrop.int.zabbadoz.net> On Fri, 20 Feb 2009, M. Warner Losh wrote: > In message: <20090220100115.R53478@maildrop.int.zabbadoz.net> > "Bjoern A. Zeeb" writes: > : On Thu, 19 Feb 2009, Andrew Thompson wrote: > : > : > On Thu, Feb 19, 2009 at 07:37:40PM -0800, Andrew Thompson wrote: > : >> Hi, > : >> > : >> > : >> I have put together a proposed set of changes for moving USB2 to its > : >> permanent location. The layout has some differences to how it is right > : >> now so I am looking for feedback. > : >> > : >> The changeover requires that the old usb stack be available until 8.0 is > : >> branched and moves it from sys/dev/usb to sys/legacy/dev/usb. The reason > : >> for this location is to reduce the changes in #includes (using -I > : >> compiler hacks). The patch doesnt show userland changes required for > : >> usbdevs and friends but they will be done. > : > > : > Also, I wasnt planning on keeping the old usb kernel modules hooked into > : > the build unless someone particularly wants them. They can all still be > : > built into the kernel. > : > : what about renaming it to dev/usb1 instead of starting another top > : level directory in sys/ ? I mean I like legacy and would prefer to > : move netinet/ in there asap but;-)) > > We'd have to hack all the old usb1 drivers. Moving to > sys/legacy/dev/usb means minimal frobbing of the code. ok, that explains. #include . -- Bjoern A. Zeeb The greatest risk is not taking one. From thompsa at FreeBSD.org Fri Feb 20 12:33:56 2009 From: thompsa at FreeBSD.org (Andrew Thompson) Date: Fri Feb 20 12:34:02 2009 Subject: CFR: usb switchover patches In-Reply-To: <20090220033740.GA903@citylink.fud.org.nz> References: <20090220033740.GA903@citylink.fud.org.nz> Message-ID: <20090220203350.GF4265@citylink.fud.org.nz> On Thu, Feb 19, 2009 at 07:37:40PM -0800, Andrew Thompson wrote: > Hi, > > > I have put together a proposed set of changes for moving USB2 to its > permanent location. The layout has some differences to how it is right > now so I am looking for feedback. I should have said the attached patch was to illustrate the changes and I didnt expect anyone to test a build with them. Andrew From linimon at FreeBSD.org Fri Feb 20 19:27:08 2009 From: linimon at FreeBSD.org (linimon@FreeBSD.org) Date: Fri Feb 20 19:27:20 2009 Subject: usb/131912: [uslcom] [patch] New devices using Silicon Labs chips - patches enclosed Message-ID: <200902210327.n1L3R82C005385@freefall.freebsd.org> Old Synopsis: New devices using Silicon Labs chips - patches enclosed New Synopsis: [uslcom] [patch] New devices using Silicon Labs chips - patches enclosed Responsible-Changed-From-To: freebsd-bugs->freebsd-usb Responsible-Changed-By: linimon Responsible-Changed-When: Sat Feb 21 03:26:24 UTC 2009 Responsible-Changed-Why: Over to maintainer(s). http://www.freebsd.org/cgi/query-pr.cgi?pr=131912 From thompsa at FreeBSD.org Sat Feb 21 16:08:46 2009 From: thompsa at FreeBSD.org (Andrew Thompson) Date: Sat Feb 21 16:08:52 2009 Subject: USB2+umass: root mount fails In-Reply-To: <200902191729.18715.hselasky@c2i.net> References: <20090217.085424.775975548.imp@bsdimp.com> <200902190926.42992.hselasky@c2i.net> <20090219.090621.-786048162.imp@bsdimp.com> <200902191729.18715.hselasky@c2i.net> Message-ID: <20090222000839.GA29083@citylink.fud.org.nz> Whatever the solution may be (root_mount_hold/root_mount_rel, sync/async explore, ...), I will commit the patch from http://wiki.freebsd.org/USB for the moment so people can still boot. Andrew From thompsa at FreeBSD.org Sat Feb 21 17:05:15 2009 From: thompsa at FreeBSD.org (Andrew Thompson) Date: Sat Feb 21 17:05:20 2009 Subject: USB2+umass: root mount fails In-Reply-To: <20090222000839.GA29083@citylink.fud.org.nz> References: <20090217.085424.775975548.imp@bsdimp.com> <200902190926.42992.hselasky@c2i.net> <20090219.090621.-786048162.imp@bsdimp.com> <200902191729.18715.hselasky@c2i.net> <20090222000839.GA29083@citylink.fud.org.nz> Message-ID: <20090222010509.GB29083@citylink.fud.org.nz> On Sat, Feb 21, 2009 at 04:08:39PM -0800, Andrew Thompson wrote: > > > Whatever the solution may be (root_mount_hold/root_mount_rel, sync/async > explore, ...), I will commit the patch from http://wiki.freebsd.org/USB > for the moment so people can still boot. Scratch that, I used root_mount_hold (r188907). This is by no means final but just pushed through to help people boot since the stack is now default. Andrew From simon at FreeBSD.org Sun Feb 22 06:18:16 2009 From: simon at FreeBSD.org (simon@FreeBSD.org) Date: Sun Feb 22 06:18:24 2009 Subject: usb/130066: [newusb] Serial adaptor use fail with 'unsupported speed XXX' Message-ID: <200902221418.n1MEIGep063192@freefall.freebsd.org> Synopsis: [newusb] Serial adaptor use fail with 'unsupported speed XXX' State-Changed-From-To: open->closed State-Changed-By: simon State-Changed-When: Sun Feb 22 14:15:31 UTC 2009 State-Changed-Why: Both my serial adaptors now work, thanks! http://www.freebsd.org/cgi/query-pr.cgi?pr=130066 From thompsa at FreeBSD.org Sun Feb 22 17:08:58 2009 From: thompsa at FreeBSD.org (Andrew Thompson) Date: Sun Feb 22 17:09:09 2009 Subject: CFR: usb switchover patches In-Reply-To: <20090220033740.GA903@citylink.fud.org.nz> References: <20090220033740.GA903@citylink.fud.org.nz> Message-ID: <20090223010850.GB40325@citylink.fud.org.nz> On Thu, Feb 19, 2009 at 07:37:40PM -0800, Andrew Thompson wrote: > Hi, > > > I have put together a proposed set of changes for moving USB2 to its > permanent location. The layout has some differences to how it is right > now so I am looking for feedback. > > The changeover requires that the old usb stack be available until 8.0 is > branched and moves it from sys/dev/usb to sys/legacy/dev/usb. The reason > for this location is to reduce the changes in #includes (using -I > compiler hacks). The patch doesnt show userland changes required for > usbdevs and friends but they will be done. > > Some ports will break. Any that exist solely for the old usb stack can > be marked broken (like udesc_dump). I dont know that the fallout will be > like for the others, maybe portmgr would be interested in doing a build > test. > > The change roughly goes > > svn move sys/dev/usb -> sys/legacy/dev/usb > svn move sys/dev/usb2 -> sys/dev/usb (with fixups, see below) I plan to do this tomorrow. The commit can not be done in one since it involves svn moves to/from the same location but it should only take a few mins. Andrew From bugmaster at FreeBSD.org Mon Feb 23 03:07:02 2009 From: bugmaster at FreeBSD.org (FreeBSD bugmaster) Date: Mon Feb 23 03:09:57 2009 Subject: Current problem reports assigned to freebsd-usb@FreeBSD.org Message-ID: <200902231107.n1NB71RT055681@freefall.freebsd.org> Note: to view an individual PR, use: http://www.freebsd.org/cgi/query-pr.cgi?pr=(number). The following is a listing of current problems submitted by FreeBSD users. These represent problem reports covering all versions including experimental development code and obsolete releases. S Tracker Resp. Description -------------------------------------------------------------------------------- o usb/131912 usb [uslcom] [patch] New devices using Silicon Labs chips o usb/131900 usb Additional product identification code for Logitech Qu o usb/131583 usb [umass] Failure when detaching umass Device o usb/131576 usb [aue] ADMtek USB To LAN Converter can't send data o usb/131521 usb Registering Belkin UPS to usb_quirks.c f usb/131123 usb [patch] re-add UQ_ASSUME_CM_OVER_DATA USB quirk o usb/131074 usb no run-time detection of usb devices plugged into exte o usb/130736 usb Page fault unplugging USB stick o usb/130325 usb [usb] [patch] fix tools/tools/usb/print-usb-if-vids.sh o usb/130230 usb Samsung Electronics YP-U3 does not attach in 7.1-RELEA o usb/130208 usb Boot process severely hampered by umass0 error o usb/130122 usb [newusb] DVD drive detects as 'da' device o usb/129964 usb [newusb] disconnection of ugen devices isn't logged o bin/129963 usb [newusb] usbconfig(8) fails with misleading error when o docs/129962 usb [newusb] usbconfig(8) refers to non-existant usb2_core o usb/129945 usb [usbdevs] [patch] add u3g support for Longcheer WM66 U o usb/129766 usb [usb] plugging in usb modem HUAWEI E226 panics system o usb/129758 usb [uftdi] [patch] add Pyramid LCD usb support o usb/129673 usb [uhci] uhci (uhub) confused on replugging USB 1.1 scan o usb/129522 usb [ubsa] [patch] add support for ZTE AC8700 modem o usb/129500 usb [umass] [panic] FreeBSD Crashes when connecting SanDis o usb/129311 usb [usb] [panic] Instant crash with an USB card reader o usb/129251 usb [usbdevs] [patch] Liebert UPS being assigned uhid and o usb/129173 usb [uplcom] [patch] Add support for Corega CG-USBRS232R a s usb/128990 usb [usb] u3g does not handle RTS/CTS available on for exa o usb/128977 usb [usb] [patch] uaudio is not full duplex o usb/128803 usb [usbdevs] [patch] Quirk for I-Tuner Networks USBLCD4X2 o usb/128590 usb [patch] [newusb] Updates to NOTES for new USB stack o usb/128485 usb [umodem] [patch] Nokia N80 modem support o usb/128425 usb [umass] Cannot Connect Maxtor Onetouch 4 USB drive f usb/128418 usb [panic] [rum] loading if_rum causes panic, looks like o usb/128324 usb [uplcom] [patch] remove baud rate restriction for PL23 o usb/127980 usb [umass] [patch] Fix Samsung YP U2 MP3 player on 7.x an o usb/127926 usb [boot] USB Timeout during bootup o usb/127549 usb [umass] [patch] Meizu MiniPlayer M6 (SL) requires some s usb/127453 usb [request] ubsa, uark, ubser, uftdi, and friends should o usb/127423 usb [boot] BTX halted on Gigabyte GA-MA69VM-S2 / AMD Sempr o usb/127342 usb [boot] cannot enable usb keyboard and mouse support in o kern/127222 usb [ohci]: Regression in 7.0 usb storage generic driver o usb/126884 usb [ugen] [patch] Bug in buffer handling in ugen.c f usb/126848 usb [usb]: USB Keyboard hangs during Installation o usb/126740 usb [ulpt] doesn't work on 7.0-RELEASE, 10 second stall be o usb/126519 usb [usb] [panic] panic when plugging in an iphone o kern/126396 usb [panic] kernel panic after unplug USB Bluetooth device o usb/125736 usb [ukbd] [hang] system hangs after AT keyboard detect if o usb/125631 usb [ums] [panic] kernel panic during bootup while 'Logite o usb/125510 usb [panic] repeated plug and unplug of USB mass storage d o usb/125450 usb [panic] Removing USB flash card while being accessed c o usb/125264 usb [patch] sysctl for set usb mouse rate (very useful for o usb/125238 usb [ums] Habu Mouse turns off in X o usb/125088 usb [keyboard] Touchpad not detected on Adesso AKB-430UG U o usb/125072 usb [uplcom] [patch] add Mobile Action MA-620 Infrared Ada o usb/124980 usb [panic] kernel panic on detaching unmounted umass devi o kern/124777 usb [ucom] USB cua devices don't revert to tty devices whe o usb/124758 usb [rum] [panic] rum panics SMP kernel o usb/124708 usb [panic] Kernel panic on USB KVM reattach o usb/124604 usb [ums] Microsoft combo wireless mouse doesn't work o usb/123969 usb [usb] Supermicro H8SMi-2 usb problem: port reset faile o usb/123714 usb [usb] [panic] Panic when hald-storage-probe runs with o usb/123691 usb usbd(8): usbd hangs o usb/123690 usb [usb] [panic] Panic on USB device insertion when usb l o usb/123611 usb [usb] BBB reset failed, STALLED from Imation/Mitsumi U o usb/123509 usb [umass] continuous reset Samsung SGH-G600 phone o usb/123352 usb [usbdevs] [patch] Add Option GTMAX3.6/7.2 and Quallcom o usb/123351 usb [usbdevs] [patch] Add Reiner SCT cyberJack, Omnikey [2 o usb/122992 usb [umass] [patch] MotoROKR Z6 Phone not recognised by um o usb/122956 usb [ubsa] [patch] add support for Novatel Wireless XU870 o usb/122936 usb [ucom] [ubsa] Device does not receive interrupt o usb/122905 usb [ubsa] [patch] add Huawei E220 to ubsa o usb/122819 usb [usb] [patch] Patch to provide dynamic additions to th o usb/122813 usb [udbp] [request] udbp driver should be removed in favo o usb/122621 usb [patch] [request] New driver for Sierra Wireless 3G US o usb/122547 usb [ehci] USB Printer not being recognized after reboot o usb/122539 usb [ohci] [panic] AnyDATA ADU-E1000D - kernel panic: ohci o usb/122483 usb [panic] [ulpt] Repeatable panic in 7.0-STABLE o usb/122119 usb [umass] umass device causes creation of daX but not da o usb/122025 usb [uscanner] [patch] uscanner does not attach to Epson R o usb/121755 usb [ohci] [patch] Fix panic after ohci/uhub cardbus devic o usb/121734 usb [ugen] ugen HP1022 printer device not working since up o usb/121708 usb [keyboard] nforce 650i mobo w/ usb keyboard infinite k o usb/121474 usb [cam] [patch] QUIRK: SAMSUNG HM250JI in LaCie usb hard o usb/121426 usb [patch] [uscanner] add HP ScanJet 3570C o usb/121275 usb [boot] FreeBSD fails to boot with usb legacy support e o usb/121232 usb [usb] [panic] USB CardBus card removal causes reboot s p usb/121184 usb [uipaq] [patch] add ids from linux ipaq driver (plus a o usb/121169 usb [umass] Issues with usb mp3 player o usb/121045 usb [uftdi] [patch] Add support for PC-OP-RS1 and KURO-RS o usb/120786 usb [usb] [panic] Kernel panic when forced umount of a det o usb/120729 usb [panic] fault while in kernel mode with connecting USB o usb/120572 usb [umass] [patch] quirk to support ASUS P535 as umass (a o usb/120321 usb [hang] System hangs when transferring data to WD MyBoo o usb/120283 usb [panic] Automation reboot with wireless keyboard & mou o usb/120034 usb [hang] 6.2 & 6.3 hangs on boot at usb0: OHCI with 1.5 o usb/120017 usb [ehci] [patch] CS5536 (AMD Geode) USB 2.0 quirk o usb/119981 usb [axe] [patch] add support for LOGITEC LAN-GTJ/U2 gigab o usb/119977 usb [ums] Mouse does not work in a Cherry-USB keyboard/mou o usb/119653 usb [cam] [patch] iriver s7 player sync cache error patch o usb/119633 usb [umass] umass0: BBB reset failed, IOERROR [regression] o usb/119513 usb [irq] inserting dlink dwl-g630 wireless card results i o usb/119509 usb [usb] USB flaky on Dell Optiplex 755 o usb/119481 usb [hang] FreeBSD not responding after connecting USB-Mas o usb/119389 usb [umass] Sony DSC-W1 CBI reset failed, STALLED [regress o usb/119227 usb [ubsa] [patch] ubsa buffer is too small; should be tun o usb/119201 usb [cam] [patch] Quirks for Olympus FE-210 camera, LG and o usb/118686 usb [usbdevs] [patch] teach usbdevs / ubsa(4) about Huawei o usb/118485 usb [usbdevs] [patch] Logitech Headset Workaround o usb/118480 usb [umass] Timeout in USB mass storage freezes vfs layer o usb/118353 usb [panic] [ppp] repeatable kernel panic during ppp(4) se o usb/118141 usb [ucom] usb serial and nokia phones ucomreadcb ucomread o usb/118140 usb [ucom] [patch] quick hack for ucom to get it behave wi o usb/118098 usb [umass] 6th gen iPod causes problems when disconnectin o usb/117955 usb [umass] [panic] inserting minolta dimage a2 crashes OS o usb/117946 usb [panic] D-Link DUB-E100 rev. B1 crashes FreeBSD 7.0-BE o usb/117938 usb [ums] [patch] Adding support for MS WL Natural and MS o usb/117911 usb [ums] [request] Mouse Gembird MUSWC not work o usb/117893 usb [umass] Lacie USB DVD writing failing o usb/117613 usb [uhci] [irq] uhci interrupt storm & USB leaked memory o usb/117598 usb [uaudio] [patch] Not possible to record with Plantroni o usb/117313 usb [umass] [panic] panic on usb camera insertion o usb/117200 usb [ugen] ugen0 prints strange string on attach if detach o usb/117185 usb [umodem] [patch] Add support for UNION interface descr o usb/117183 usb [panic] USB/fusefs -- panic while transferring large a o usb/116947 usb [ukbd] [patch] [regression] enable boot protocol on th o usb/116699 usb [usbhid] USB HID devices do not initialize at system b o usb/116561 usb [umodem] [panic] RELENG_6 umodem panic "trying to slee o usb/116282 usb [ulpt] Cannot print on USB HP LJ1018 or LJ1300 o usb/115935 usb [usbdevs] [patch] kernel counterproductively attaches o usb/115933 usb [uftdi] [patch] RATOC REX-USB60F (usb serial converter o usb/115400 usb [ehci] Problem with EHCI on ASUS M2N4-SLI o usb/115298 usb [ulpt] [panic] Turning off USB printer panics kernel o usb/114916 usb [umass] [patch] USB Maxtor drive (L300RO) requires qui o kern/114780 usb [uplcom] [panic] Panics while stress testing the uplco o usb/114682 usb [umass] generic USB media-card reader unusable o usb/114310 usb [libusb] [patch] [panic] USB hub attachment panics ker o usb/114068 usb [umass] [patch] Problems with connection of the umass o conf/114013 usb [patch] WITHOUT_USB allow to compil a lot of USB stuff s usb/113977 usb [request] Need a way to set mode of USB disk's write c o usb/113672 usb [ehci] [panic] Kernel panic with AEWIN CB6971 s usb/113629 usb [ukbd] Dropped USB keyboard events on Dell Latitude D6 o usb/113432 usb [ucom] WARNING: attempt to net_add_domain(netgraph) af a usb/113060 usb [usbdevs] [patch] Samsung printer not working in bidir o usb/112944 usb [ulpt] [patch] Bi-directional access to HP LaserJet 10 o usb/112640 usb [usb] [hang] Kernel freezes when writing a file to an o usb/112631 usb [panic] Problem with SONY DSC-S80 camera on umount s usb/112568 usb [umass] [request] USB mode may wrong when mounting Pla o usb/112463 usb [umass] problem with Samsung USB DVD writer, libscg an o usb/112461 usb [ehci] [request] ehci USB 2.0 doesn't work on nforce4 o usb/111753 usb [uhid] [panic] Replicable system panic involving UHID s usb/110991 usb [usbdevs] [patch] QUIRK: Super Top IDE DEVICE (depends o usb/110988 usb [umass] [patch] Handling of quirk IGNORE_RESIDUE is um o usb/110856 usb [ugen] [patch] interrupt in msgs are truncated when bu o usb/110197 usb [umass] Sony PSP umass device does not detach from EHC o usb/109397 usb [panic] on boot from USB flash o usb/109274 usb [usb] MCP55 USB Controller fails to attach in AMD64 Cu o usb/108513 usb [umass] Creative MuVo TX FM fails in 6.2-RELEASE [regr s usb/108344 usb [panic] kernel with atausb panics when unplugging USB o usb/108056 usb [ohci] Mouse gets powered off during device probe when o usb/107935 usb [uplcom] [panic] panic while accessing /dev/cuaU0 o usb/107924 usb [patch] usbd(8) does not call detach o usb/107848 usb [umass] [request] cannot access Samsung flash disk o usb/107827 usb [ohci] [panic] ohci_add_done addr not found o usb/107496 usb [uhub] USB device problem on RELENG_6_2 (SHORT_XFER) [ o usb/107388 usb [patch] [request] new driver: add utoppy device from N o usb/107248 usb [umass] [patch] scsi_da.c quirk for Cowon iAUDIO X5 MP o usb/107243 usb [cam] [patch] Apacer USB Flash Drive quirk o usb/106861 usb [usbdevs] [patch]: usbdevs update: Add product ACER Ze s usb/106832 usb [usb] USB HP printer is not detected by kernel when AC o usb/106648 usb [umass] [hang] USB Floppy on D1950 10 min Hang on Inse o usb/106621 usb [axe] [patch] DLINK DUB-E100 support broken o usb/106615 usb [uftdi] uftdi module does not automatically load with o usb/106041 usb [usb] [request] FreeBSD does not recognise Mustek Bear o usb/105361 usb [panic] Kernel panic during unmounting mass storage (C o usb/105186 usb [ehci] [panic] USB 2.0/ehci on FreeBSD 6.2-PRE/AMD64 c o usb/105065 usb [ata] [usb] SATA - USB Bridge o usb/104830 usb [umass] system crashes when copying data to umass devi o usb/104645 usb [umass] [request] Rave C-201 MP3 player does not commu o usb/104352 usb [ural] [patch] ural driver doesnt work o usb/104292 usb [umass] [hang] system lockup on forced umount of usb-s o usb/104290 usb [umass] [patch] quirk: TOSHIBA DVD-RAM drive (libretto o usb/103917 usb [uhub] USB driver reports "Addr 0 should never happen" o usb/103418 usb usbhidctl(1): [patch] [request] usbhidctl: add ability o usb/103289 usb [request] USB 2.0 problems on AMD LX-800 CPU and CS-55 o usb/103046 usb [ulpt] [patch] ulpt event driven I/O with select(2) an o usb/103025 usb [uhub] [panic] wrong detection of USB device for FreeB o usb/102976 usb [panic] Casio Exilim Digital Camera causes panic on in o usb/102678 usb [keyboard] Dell PowerEdge DRAC5 USB Keyboard does not o usb/102066 usb [ukbd] usb keyboard and multimedia keys don't work o usb/101775 usb [libusbhid] [patch] possible error in report descripto o usb/101761 usb [usb] [patch] [request] usb.h: increase maximal size o o usb/101752 usb [umass] [panic] 6.1-RELEASE kernel panic on usb device o usb/101448 usb [ohci] FBSD 6.1-STABLE/AMD64 crashes under heavy USB/O o usb/101096 usb [ural] [panic] USB WLAN occasionally causes kernel-pan o usb/100746 usb [keyboard] system does not boot due to USB keyboard pr o usb/99538 usb [keyboard] while using USB keyboard default params of o usb/99431 usb [keyboard] FreeBSD on MSI 6566E (Intel 845E motherboar o usb/98343 usb [boot] BBB reset failed errors with Creative Muvo MP3 o usb/97472 usb [cam] [patch] add support for Olympus C150,D390 s usb/97286 usb [mouse] [request] MS Wireless Intellimouse Explorer 2. o usb/97175 usb [umass] [hang] USB cardreader hangs system o usb/96457 usb [umass] [panic] fatback on umass = reboot o usb/96381 usb [cam] [patch] add a quirk table entry for a flash ram o usb/96224 usb [usb] [msdosfs] mount_msdosfs cause page fault in sync s usb/96120 usb [ums] [request] USB mouse not always detected s usb/95636 usb [umass] [boot] 5 minute delay at boot when using VT620 o usb/95562 usb [umass] Write Stress in USB Mass drive causes "vinvalb s usb/95348 usb [keyboard] USB keyboard unplug causes noise on screen o usb/95037 usb [umass] USB disk not recognized on hot-plug. o usb/94897 usb [panic] Kernel Panic when cleanly unmounting USB disk o usb/94717 usb [ulpt] Reading from /dev/ulpt can break work of a UHCI o usb/94384 usb [panic] kernel panic with usb2 hardware o usb/93872 usb [cam] [patch] SCSI quirk required for ELTA 8061 OL USB o usb/93828 usb [ohci] [panic] ohci causes panic on boot (HP Pavillion o usb/93408 usb [mouse] hw.acpi.cpu.cx_lowest=C3 on AMD Turion causes o usb/93389 usb [umass] [patch] Digital Camera Pentax S60 don't work o usb/93155 usb [ulpt] /dev/ulpt0: device busy, USB printer does not w o usb/92852 usb [ums] [patch] Vertical scroll not working properly on o usb/92171 usb [panic] panic unplugging Vodafone Mobile Connect (UMTS o usb/92142 usb [uhub] SET_ADDR_FAILED and SHORT_XFER errors from usb o usb/92083 usb [ural] [panic] panic using WPA on ural NIC in 6.0-RELE o usb/92052 usb [ulpt] usbd causes defunct process with busy file-hand o usb/91906 usb [ehci] [hang] FreeBSD hangs while booting with USB leg o usb/91896 usb camcontrol(8): Serial Number of USB Memory Sticks is n o usb/91811 usb [umass] Compact Flash in HP Photosmart 2610 return " o usb/91629 usb [usb] usbd_abort_pipe() may result in infinite loop o usb/91546 usb [umodem] [patch] Nokia 6630 mobile phone does not work o usb/91538 usb [ulpt] [patch] Unable to print to EPSON CX3500 o usb/91283 usb [boot] [regression] booting very slow with usb devices o usb/91238 usb [umass] USB tape unit fails to write a second tape fil o usb/90700 usb [umass] [panic] Kernel panic on connect/mount/use umas o usb/89954 usb [umass] [panic] USB Disk driver race condition? s usb/89003 usb [request] LaCie Firewire drive not properly supported o usb/88743 usb [hang] [regression] USB makes kernel hang at boot (reg o usb/88408 usb [axe] axe0 read PHY failed o usb/87648 usb [mouse] Logitech USB-optical mouse problem. o usb/87224 usb [usb] Cannot mount USB Zip750 o usb/86767 usb [umass] [patch] bogus "slice starts beyond end of the o usb/86298 usb [mouse] Known good USB mouse won't work with correct s s usb/85067 usb [uscanner] Cannot attach ScanJet 4300C to usb device f usb/84750 usb [hang] 6-BETA2 reboot/shutdown with root_fs on externa s usb/84336 usb [usb] [reboot] instant system reboot when unmounting a o usb/84326 usb [umass] Panic trying to connect SCSI tape drive via US o usb/83977 usb [ucom] [panic] ucom1: open bulk out error (addr 2): IN o usb/83863 usb [ugen] Communication problem between opensc/openct via o usb/83756 usb [ums] [patch] Microsoft Intellimouse Explorer 4.0A doe f usb/83677 usb [usb] [request] usb controller often not detected (Sun o usb/83563 usb [umass] [panic] Page Fault while detaching Mpman Usb d o usb/83504 usb [kernel] [patch] SpeedTouch USB stop working on recent o usb/82660 usb [ehci] [panic] EHCI: I/O stuck in state 'physrd'/panic s usb/82569 usb [umass] [panic] USB mass storage plug/unplug causes sy o usb/82520 usb [udbp] [reboot] Reboot when USL101 connected o usb/82350 usb [ucom] [panic] null pointer dereference in USB stack o usb/81621 usb [ehci] [hang] external hd hangs under load on ehci o usb/80935 usb [uvisor] [patch] uvisor.c is not work with CLIE TH55. o usb/80862 usb [patch] USB locking issues: missing some Giant calls o usb/80854 usb [patch] [request] suggestion for new iface-no-probe me o usb/80829 usb [modules] [panic] possible panic when loading USB-modu s usb/80777 usb [request] usb_rem_task() should wait for callback to c s usb/80776 usb [udav] [request] UDAV device driver shouldn't use usb_ o usb/80774 usb [patch] have "usbd_find_desc" in line with the other " o usb/80361 usb [umass] [patch] mounting of Dell usb-stick fails o usb/80040 usb [hang] Use of sound mixer causes system freeze with ua o usb/79723 usb [usb] [request] prepare for high speed isochronous tra o usb/79722 usb [ehci] wrong alignments in ehci.h a usb/79656 usb [ehci] RHSC interrupts lost o usb/79524 usb [ulpt] printing to Minolta PagePro 1[23]xxW via USB fa o usb/79287 usb [uhci] [hang] UHCI hang after interrupt transfer o usb/79269 usb [ohci] USB ohci da0 plug/unplug causes crashes and loc o usb/78984 usb [umass] [patch] Creative MUVO umass failure o usb/77294 usb [ucom] [panic] ucom + ulpcom panic o usb/77184 usb [umass] [panic] kernel panic on USB device disconnect, o usb/76732 usb [ums] Mouse problems with USB KVM Switch o usb/76653 usb [umass] [patch] Problem with Asahi Optical usb device o usb/76461 usb [umass] disklabel of umass(4)-CAM(4)-da(4) not used by o usb/76395 usb [uhci] USB printer does not work, usbdevs says "addr 0 s usb/75928 usb [umass] [request] Cytronix SmartMedia card (SMC) reade o usb/75800 usb [ucom] ucom1: init failed STALLED error in time of syn o usb/75797 usb [sound] 5.3-STABLE(2005 1/4) detect USB headset, But c o usb/75764 usb [umass] [patch] "umass0: Phase Error" - no device for o usb/75705 usb [umass] [panic] da0 attach / Optio S4 (with backtrace) o usb/74771 usb [umass] [hang] mounting write-protected umass device a s usb/74453 usb [umass] [patch] Q-lity CD-RW USB ECW-043 (ScanLogic SL o usb/74211 usb [umass] USB flash drive causes CAM status 0x4 on 4.10R o usb/73307 usb [panic] Kernel panics on USB disconnect s usb/72733 usb [ucom] [request] Kyocera 7135 Palm OS connection probl o usb/71455 usb [umass] Slow USB umass performance of 5.3 o usb/71417 usb [ugen] Cryptoflex e-gate USB token (ugen0) communicati o usb/71416 usb [ugen] Cryptoflex e-gate USB token (ugen0) detach is n o usb/71280 usb [aue] aue0 device (linksys usb100tx) doesn't work in 1 o usb/71155 usb [ulpt] misbehaving usb-printer hangs processes, causes o usb/70523 usb [umct] [patch] umct sending/receiving wrong characters o usb/69006 usb [usbdevs] [patch] Apple Cinema Display hangs USB ports o usb/68232 usb [ugen] [patch] ugen(4) isochronous handling correction o usb/67301 usb [uftdi] [panic] RTS and system panic o usb/66547 usb [ucom] Palm Tungsten T USB does not initialize correct o usb/63621 usb [umass] [panic] USB MemoryStick Reader stalls/crashes s usb/62257 usb [umass] [request] card reader UCR-61S2B is only half-s o usb/59698 usb [keyboard] [patch] Rework of ukbd HID to AT code trans s bin/57255 usb [patch] usbd(8) and multi-function devices s usb/52026 usb [usb] [request] umass driver support for InSystem ISD2 s usb/51958 usb [urio] [patch] update for urio driver o i386/46371 usb USB controller cannot be initialized on IBM Netfinity o usb/40948 usb [umass] [request] USB HP CDW8200 does not work o usb/30929 usb [usb] [patch] use usbd to initialize USB ADSL modem 303 problems total. From w8hdkim at gmail.com Mon Feb 23 10:31:49 2009 From: w8hdkim at gmail.com (Kim Culhan) Date: Mon Feb 23 10:32:13 2009 Subject: reattach 3g0 device: could not allocate new device Message-ID: <89dbfdc30902231031j4407614vdce09e8e58cdc346@mail.gmail.com> Running 8.0-CURRENT as of 2-22-09 The 3g0 device is a Novatel U727 EVDO wireless radio. If the machine boots with the device attached, dmesg reads: u3g0: on usbus2 Remove the device and this is logged: u3g0: at ushub2, port 2, addr 2 (disconnected) Reattach the device and there is this message: uhub_reattach_port:414: could not allocate new device! kernel config has: device usb2_serial_3g Any help is greatly appreciated thanks -kim -- From thompsa at FreeBSD.org Mon Feb 23 10:52:16 2009 From: thompsa at FreeBSD.org (Andrew Thompson) Date: Mon Feb 23 10:52:23 2009 Subject: HEADSUP: USB2 now fully default Message-ID: <20090223185209.GA46663@citylink.fud.org.nz> Hi, As per my previous emails, the USB2 stack has been moved in permanently to sys/dev/usb. The temporary kernel device (and module) naming has been reverted, all the names are back to how they have been in previous releases (usb,ehci,ohci,ums,...). This means that if you are using a custom kernel and were using the USB2 stack via 'usb2_core' and friends then you will need to change these. Please see the GENERIC kernel for a further example. The only casualty is the 'ugen' option, this is now built in by default and no longer a kernel config entry. Please remove this. Also, all usb modules now live under sys/modules/usb. Please report any problems to the mailing list. Andrew From hselasky at c2i.net Mon Feb 23 12:53:49 2009 From: hselasky at c2i.net (Hans Petter Selasky) Date: Mon Feb 23 12:53:56 2009 Subject: reattach 3g0 device: could not allocate new device In-Reply-To: <89dbfdc30902231031j4407614vdce09e8e58cdc346@mail.gmail.com> References: <89dbfdc30902231031j4407614vdce09e8e58cdc346@mail.gmail.com> Message-ID: <200902232156.14845.hselasky@c2i.net> On Monday 23 February 2009, Kim Culhan wrote: > Running 8.0-CURRENT as of 2-22-09 > > The 3g0 device is a Novatel U727 EVDO wireless radio. > > If the machine boots with the device attached, dmesg reads: > > u3g0: on usbus2 > > Remove the device and this is logged: > > u3g0: at ushub2, port 2, addr 2 (disconnected) > > Reattach the device and there is this message: > > uhub_reattach_port:414: could not allocate new device! > > kernel config has: > > device usb2_serial_3g > > Any help is greatly appreciated > Hi, Can you turn on USB HUB debugging: sysctl hw.usb2.uhub.debug=15 sysctl hw.usb.uhub.debug=15 --HPS From w8hdkim at gmail.com Mon Feb 23 14:58:57 2009 From: w8hdkim at gmail.com (Kim Culhan) Date: Mon Feb 23 14:59:02 2009 Subject: reattach 3g0 device: could not allocate new device In-Reply-To: <200902232156.14845.hselasky@c2i.net> References: <89dbfdc30902231031j4407614vdce09e8e58cdc346@mail.gmail.com> <200902232156.14845.hselasky@c2i.net> Message-ID: <89dbfdc30902231458s2c8a1534kb2180c8cd0ddd290@mail.gmail.com> On Mon, Feb 23, 2009 at 3:56 PM, Hans Petter Selasky wrote: > On Monday 23 February 2009, Kim Culhan wrote: >> Running 8.0-CURRENT as of 2-22-09 >> >> The 3g0 device is a Novatel U727 EVDO wireless radio. >> >> If the machine boots with the device attached, dmesg reads: >> >> u3g0: on usbus2 >> >> Remove the device and this is logged: >> >> u3g0: at ushub2, port 2, addr 2 (disconnected) >> >> Reattach the device and there is this message: >> >> uhub_reattach_port:414: could not allocate new device! >> >> kernel config has: >> >> device usb2_serial_3g >> >> Any help is greatly appreciated >> > > Hi, > > Can you turn on USB HUB debugging: > > sysctl hw.usb2.uhub.debug=15 > sysctl hw.usb.uhub.debug=15 Sure here is dmesg with sysctl hw.usb2.uhub.debug=15 uhub_read_port_status:259: port 2, wPortStatus=0x0103, wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION usb2_transfer_power_ref:1470: Adding type 0 to power state usb2_transfer_power_ref:1483: needs power u3g_huawei_init:278: usb2_alloc_device:1618: Found Huawei auto-install disk! usb2_bus_port_set_device:1334: bus 0xc6733cf0 devices[2] = 0xc6bc6000 ugen2.2: at usbus2 ugen2.2: at usbus2 (disconnected) usb2_bus_port_set_device:1334: bus 0xc6733cf0 devices[2] = 0 uhub_reattach_port:414: could not allocate new device! usb2_needs_explore:1345: usb2_bus_powerd:1516: bus=0xc670bcf0 usb2_bus_powerd:1599: Recomputing power masks uhub_explore:522: udev=0xc6a93000 addr=1 With the old usb, this was returned: Feb 22 10:38:37 smallster kernel: ugen2.2: at usbus2 Feb 22 10:38:37 smallster kernel: umass0: on usbus2 Feb 22 10:38:37 smallster kernel: umass0: SCSI over Bulk-Only; quirks = 0x0000 Feb 22 10:38:38 smallster kernel: umass0:1:0:-1: Attached to scbus1 Feb 22 10:38:39 smallster kernel: (probe0:umass-sim0:0:0:0): TEST UNIT READY. CDB: 0 0 0 0 0 0 Feb 22 10:38:39 smallster kernel: (probe0:umass-sim0:0:0:0): CAM Status: SCSI Status Error Feb 22 10:38:39 smallster kernel: (probe0:umass-sim0:0:0:0): SCSI Status: Check Condition Feb 22 10:38:39 smallster kernel: (probe0:umass-sim0:0:0:0): NOT READY asc:3a,0 Feb 22 10:38:39 smallster kernel: (probe0:umass-sim0:0:0:0): Medium not present Feb 22 10:38:39 smallster kernel: (probe0:umass-sim0:0:0:0): Unretryable error Feb 22 10:38:39 smallster kernel: cd0 at umass-sim0 bus 0 target 0 lun 0 Feb 22 10:38:39 smallster kernel: cd0: Removable CD-ROM SCSI-2 device Feb 22 10:38:39 smallster kernel: cd0: 1.000MB/s transfers Feb 22 10:38:39 smallster kernel: cd0: Attempt to query device size failed: NOT READY, Medium not present Feb 22 10:40:27 smallster kernel: g_vfs_done():cd0[READ(offset=65536, length=8192)]error = 5 Feb 22 10:43:39 smallster kernel: umass0: at ushub2, port 1, addr 2 (disconnected) Feb 22 10:43:39 smallster kernel: (cd0:umass-sim0:0:0:0): lost device Feb 22 10:43:39 smallster kernel: (cd0:umass-sim0:0:0:0): removing device entry Feb 22 10:43:39 smallster kernel: ugen2.2: at usbus2 (disconnected) The device initially attempts to simulate the presence of a cdrom. Maybe this is creating the problem for usb2. -kim From marcus at marcuscom.com Mon Feb 23 15:36:56 2009 From: marcus at marcuscom.com (Joe Marcus Clarke) Date: Mon Feb 23 15:37:09 2009 Subject: CFR: usb switchover patches In-Reply-To: <20090220033740.GA903@citylink.fud.org.nz> References: <20090220033740.GA903@citylink.fud.org.nz> Message-ID: <1235432234.91306.9.camel@shumai.marcuscom.com> On Thu, 2009-02-19 at 19:37 -0800, Andrew Thompson wrote: > Hi, > > > I have put together a proposed set of changes for moving USB2 to its > permanent location. The layout has some differences to how it is right > now so I am looking for feedback. > > The changeover requires that the old usb stack be available until 8.0 is > branched and moves it from sys/dev/usb to sys/legacy/dev/usb. The reason > for this location is to reduce the changes in #includes (using -I > compiler hacks). The patch doesnt show userland changes required for > usbdevs and friends but they will be done. > > Some ports will break. Any that exist solely for the old usb stack can > be marked broken (like udesc_dump). I dont know that the fallout will be > like for the others, maybe portmgr would be interested in doing a build > test. > > The change roughly goes > > svn move sys/dev/usb -> sys/legacy/dev/usb > svn move sys/dev/usb2 -> sys/dev/usb (with fixups, see below) The headers for usb are no longer installed. This rebreaks hal as I attempt to build both backends. Can you make sure the old usb headers are also installed (/usr/include/dev/legacy/usb)? Without this, I will have to redo the hal build code. Joe > > > The patch for the build system can be viewed here, > http://people.freebsd.org/~thompsa/usb_layout/usb_xover.diff > > Now the changes... For starters the '2' will be removed from the > filenames but furthermore I want to flatten dev/usb2/core and > dev/usb2/include into just dev/usb, keeping the peripheral drivers in > their subdirs. Its hard to show with a diff so simply browse the layout > here, http://people.freebsd.org/~thompsa/usb_layout/dev/ > > Please send any minor/nitpick changes to me privately, keeping any list > replies to the overall changes. > > > regards, > Andrew > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" > -- PGP Key : http://www.marcuscom.com/pgp.asc -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 195 bytes Desc: This is a digitally signed message part Url : http://lists.freebsd.org/pipermail/freebsd-usb/attachments/20090223/c1471b39/attachment.pgp From thompsa at FreeBSD.org Mon Feb 23 15:43:13 2009 From: thompsa at FreeBSD.org (Andrew Thompson) Date: Mon Feb 23 15:43:19 2009 Subject: CFR: usb switchover patches In-Reply-To: <1235432234.91306.9.camel@shumai.marcuscom.com> References: <20090220033740.GA903@citylink.fud.org.nz> <1235432234.91306.9.camel@shumai.marcuscom.com> Message-ID: <20090223234307.GA999@citylink.fud.org.nz> On Mon, Feb 23, 2009 at 06:37:14PM -0500, Joe Marcus Clarke wrote: > On Thu, 2009-02-19 at 19:37 -0800, Andrew Thompson wrote: > > Hi, > > > > > > I have put together a proposed set of changes for moving USB2 to its > > permanent location. The layout has some differences to how it is right > > now so I am looking for feedback. > > > > The changeover requires that the old usb stack be available until 8.0 is > > branched and moves it from sys/dev/usb to sys/legacy/dev/usb. The reason > > for this location is to reduce the changes in #includes (using -I > > compiler hacks). The patch doesnt show userland changes required for > > usbdevs and friends but they will be done. > > > > Some ports will break. Any that exist solely for the old usb stack can > > be marked broken (like udesc_dump). I dont know that the fallout will be > > like for the others, maybe portmgr would be interested in doing a build > > test. > > > > The change roughly goes > > > > svn move sys/dev/usb -> sys/legacy/dev/usb > > svn move sys/dev/usb2 -> sys/dev/usb (with fixups, see below) > > The headers for usb are no longer installed. This rebreaks hal as I > attempt to build both backends. Can you make sure the old usb headers > are also installed (/usr/include/dev/legacy/usb)? Without this, I will > have to redo the hal build code. I was hoping I wouldnt have to do this as it breaks kdump since they both define the same typedefs. kdump builds its tables from trolling /usr/include. I will have a look at this. Andrew From marcus at marcuscom.com Mon Feb 23 15:46:06 2009 From: marcus at marcuscom.com (Joe Marcus Clarke) Date: Mon Feb 23 15:46:12 2009 Subject: CFR: usb switchover patches In-Reply-To: <20090223234307.GA999@citylink.fud.org.nz> References: <20090220033740.GA903@citylink.fud.org.nz> <1235432234.91306.9.camel@shumai.marcuscom.com> <20090223234307.GA999@citylink.fud.org.nz> Message-ID: <1235432783.91306.10.camel@shumai.marcuscom.com> On Mon, 2009-02-23 at 15:43 -0800, Andrew Thompson wrote: > On Mon, Feb 23, 2009 at 06:37:14PM -0500, Joe Marcus Clarke wrote: > > On Thu, 2009-02-19 at 19:37 -0800, Andrew Thompson wrote: > > > Hi, > > > > > > > > > I have put together a proposed set of changes for moving USB2 to its > > > permanent location. The layout has some differences to how it is right > > > now so I am looking for feedback. > > > > > > The changeover requires that the old usb stack be available until 8.0 is > > > branched and moves it from sys/dev/usb to sys/legacy/dev/usb. The reason > > > for this location is to reduce the changes in #includes (using -I > > > compiler hacks). The patch doesnt show userland changes required for > > > usbdevs and friends but they will be done. > > > > > > Some ports will break. Any that exist solely for the old usb stack can > > > be marked broken (like udesc_dump). I dont know that the fallout will be > > > like for the others, maybe portmgr would be interested in doing a build > > > test. > > > > > > The change roughly goes > > > > > > svn move sys/dev/usb -> sys/legacy/dev/usb > > > svn move sys/dev/usb2 -> sys/dev/usb (with fixups, see below) > > > > The headers for usb are no longer installed. This rebreaks hal as I > > attempt to build both backends. Can you make sure the old usb headers > > are also installed (/usr/include/dev/legacy/usb)? Without this, I will > > have to redo the hal build code. > > I was hoping I wouldnt have to do this as it breaks kdump since they > both define the same typedefs. kdump builds its tables from trolling > /usr/include. Can the legacy directory be ignored? > > I will have a look at this. Thanks. I know I'm going to start get build error reports soon. I'd like to put this to bed. Joe > > Andrew > -- PGP Key : http://www.marcuscom.com/pgp.asc -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 195 bytes Desc: This is a digitally signed message part Url : http://lists.freebsd.org/pipermail/freebsd-usb/attachments/20090223/7ed3c026/attachment.pgp From david at usermode.org Mon Feb 23 17:10:02 2009 From: david at usermode.org (David Johnson) Date: Mon Feb 23 17:10:08 2009 Subject: usb/132036: page fault when connecting Olympus C740 camera Message-ID: <200902240102.n1O12kXa042367@www.freebsd.org> >Number: 132036 >Category: usb >Synopsis: page fault when connecting Olympus C740 camera >Confidential: no >Severity: critical >Priority: high >Responsible: freebsd-usb >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Tue Feb 24 01:10:01 UTC 2009 >Closed-Date: >Last-Modified: >Originator: David Johnson >Release: 7.1-STABLE >Organization: >Environment: FreeBSD radagast.usermode.org 7.1-STABLE FreeBSD 7.1-STABLE #1: Sun Feb 15 14:58:30 PST 2009 david@radagast.usermode.org:/usr/obj/usr/src/sys/RADAGAST i386 >Description: FreeBSD page faults and panics when connecting an Olympus C740 camera. This happens every time on two separate systems with 7.1-STABLE. I have had this camera a few years, and this is new behavior. It was definitely not doing this the last time I connected the camera in November with 7.0-RELEASE. >From log/messages: Feb 23 16:27:06 radagast root: Unknown USB device: vendor 0x07b4 product 0x0105 bus uhub4 Feb 23 16:27:06 radagast kernel: umass0: on uhub4 >From crash/info.0: Dump header from device /dev/ad8s1b Architecture: i386 Architecture Version: 2 Dump Length: 239534080B (228 MB) Blocksize: 512 Dumptime: Mon Feb 23 16:27:06 2009 Hostname: radagast.usermode.org Magic: FreeBSD Kernel Dump Version String: FreeBSD 7.1-STABLE #1: Sun Feb 15 14:58:30 PST 2009 david@radagast.usermode.org:/usr/obj/usr/src/sys/RADAGAST Panic String: page fault Dump Parity: 2507188485 Bounds: 0 Dump Status: good I can provide a core if necessary. >How-To-Repeat: Connect camera to USB port. >Fix: >Release-Note: >Audit-Trail: >Unformatted: From christoph.mallon at gmx.de Mon Feb 23 22:09:23 2009 From: christoph.mallon at gmx.de (Christoph Mallon) Date: Mon Feb 23 22:09:36 2009 Subject: HEADSUP usb2/usb4bsd to become default in GENERIC In-Reply-To: <200902091608.34376.hselasky@c2i.net> References: <20090206045349.GQ78804@elvis.mu.org> <200902091534.12506.hselasky@c2i.net> <49904238.50505@gmx.de> <200902091608.34376.hselasky@c2i.net> Message-ID: <49A38F0F.8040008@gmx.de> Hans Petter Selasky schrieb: > On Monday 09 February 2009, Christoph Mallon wrote: >> Hans Petter Selasky schrieb: >>> On Monday 09 February 2009, Christoph Mallon wrote: >>>> Hans Petter Selasky schrieb: >>>>> On Monday 09 February 2009, Christoph Mallon wrote: >>>>>> Christoph Mallon schrieb: >>>>>>> are named "err" or "error". This should be investigated, so here's >>>>>>> the complete list: >>>>>> Sorry, my MUA seems to have damaged the list. You can get the list >>>>>> here: http://tron.homeunix.org/usb2.unread.log >>>>> I think some of these errors depend if you have USB debugging compiled >>>>> or not. At least GCC does not warn? >>>> No, it does not depend on USB debugging. >>>> GCC has no warning at all for variables which are only assigned to. >>>> It only can warn about variables, which are only initialised. >>>> >>>> { >>>> int x = 23; // GCC warns here ... >>>> int y; // ... but not here - cparser does >>>> y = 42; >>>> y++; >>>> } >>>> >>>> cparser has an analysis, which can warn about "y", too. >>>> >>>> I manually verified all 40 warnings and I cannot find any users (i.e. >>>> readers) for these variables. >>> What is the correct way to discard the return argument of a function? >>> That's basically what most of the warnings are about. >>> >>> 1) (void)my_fn() cast >>> 2) if (my_fn()) { } >>> 3) err = my_fn(); >>> 4) my_fn(); >> Just to understand this correctly: You want to discard error codes? >> >> >> Basically I see four categories: >> >> 1) Getting the softc and not using it. >> This can be removed completely. >> Example: >> sc = ATMEGA_BUS2SC(xfer->xroot->bus); >> >> 2) calling mtx_owned() and discarding the return value. >> Can be removed, too, after checking that the value is really unnecessary. >> Example: >> use_polling = mtx_owned(xfer->xroot->xfer_mtx) ? 1 : 0; >> >> 3) Getting some value and not using it. >> Can be removed, too, after checking that the value is really unnecessary. >> Example: >> ep_no = (xfer->endpoint & UE_ADDR); >> >> 4) The rest are return values of functions, which contain error codes. >> Discarding them is questionable at best. >> Example: (err is not read) >> if (udev->flags.suspended) { >> err = DEVICE_SUSPEND(iface->subdev); >> device_printf(iface->subdev, "Suspend failed\n"); >> } >> return (0); /* success */ > > Hi, > > Can you wait some days and re-run the analysis on -current, because there is a > bulk of patches going in to some of the code you have analysed, so the line > numbers are likely to not match. Then we fix those warnings! Here's the updated list: http://tron.homeunix.org/usb2.unread.20090224.log It contains 33 items. 12 of the variables are named "err" or "error". From hselasky at c2i.net Tue Feb 24 00:03:14 2009 From: hselasky at c2i.net (Hans Petter Selasky) Date: Tue Feb 24 00:03:20 2009 Subject: reattach 3g0 device: could not allocate new device In-Reply-To: <89dbfdc30902231458s2c8a1534kb2180c8cd0ddd290@mail.gmail.com> References: <89dbfdc30902231031j4407614vdce09e8e58cdc346@mail.gmail.com> <200902232156.14845.hselasky@c2i.net> <89dbfdc30902231458s2c8a1534kb2180c8cd0ddd290@mail.gmail.com> Message-ID: <200902240905.42406.hselasky@c2i.net> On Monday 23 February 2009, Kim Culhan wrote: > On Mon, Feb 23, 2009 at 3:56 PM, Hans Petter Selasky wrote: > > On Monday 23 February 2009, Kim Culhan wrote: > >> Running 8.0-CURRENT as of 2-22-09 > >> > >> The 3g0 device is a Novatel U727 EVDO wireless radio. > >> > >> If the machine boots with the device attached, dmesg reads: > >> > >> u3g0: on usbus2 > >> > >> Remove the device and this is logged: > >> > >> u3g0: at ushub2, port 2, addr 2 (disconnected) > >> > >> Reattach the device and there is this message: > >> > >> uhub_reattach_port:414: could not allocate new device! > >> > >> kernel config has: > >> > >> device usb2_serial_3g > >> > >> Any help is greatly appreciated > > > > Hi, > > > > Can you turn on USB HUB debugging: > > > > sysctl hw.usb2.uhub.debug=15 > > sysctl hw.usb.uhub.debug=15 > Hi Kim, In the latter case you don't have the U3G driver loaded. The U3G driver will detect the CD-ROM and send an eject or propritary command. After some while the device should show up like a u3g0 device. The error message you get is like it should be when CD-ROM detection is enabled. --HPS > Sure here is dmesg with sysctl hw.usb2.uhub.debug=15 > > uhub_read_port_status:259: port 2, wPortStatus=0x0103, > wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION > usb2_transfer_power_ref:1470: Adding type 0 to power state > usb2_transfer_power_ref:1483: needs power > u3g_huawei_init:278: > usb2_alloc_device:1618: Found Huawei auto-install disk! > usb2_bus_port_set_device:1334: bus 0xc6733cf0 devices[2] = 0xc6bc6000 > ugen2.2: at usbus2 > ugen2.2: at usbus2 (disconnected) > usb2_bus_port_set_device:1334: bus 0xc6733cf0 devices[2] = 0 > uhub_reattach_port:414: could not allocate new device! > usb2_needs_explore:1345: > usb2_bus_powerd:1516: bus=0xc670bcf0 > usb2_bus_powerd:1599: Recomputing power masks > uhub_explore:522: udev=0xc6a93000 addr=1 > > With the old usb, this was returned: > > Feb 22 10:38:37 smallster kernel: ugen2.2: at > usbus2 Feb 22 10:38:37 smallster kernel: umass0: Novatel Wireless CDMA, class 0/0, rev 1.10/0.00, addr 2> on usbus2 > Feb 22 10:38:37 smallster kernel: umass0: SCSI over Bulk-Only; quirks = > 0x0000 Feb 22 10:38:38 smallster kernel: umass0:1:0:-1: Attached to scbus1 > Feb 22 10:38:39 smallster kernel: (probe0:umass-sim0:0:0:0): TEST UNIT > READY. CDB: 0 0 0 0 0 0 > Feb 22 10:38:39 smallster kernel: (probe0:umass-sim0:0:0:0): CAM > Status: SCSI Status Error > Feb 22 10:38:39 smallster kernel: (probe0:umass-sim0:0:0:0): SCSI > Status: Check Condition > Feb 22 10:38:39 smallster kernel: (probe0:umass-sim0:0:0:0): NOT READY > asc:3a,0 Feb 22 10:38:39 smallster kernel: (probe0:umass-sim0:0:0:0): > Medium not present Feb 22 10:38:39 smallster kernel: > (probe0:umass-sim0:0:0:0): Unretryable error Feb 22 10:38:39 smallster > kernel: cd0 at umass-sim0 bus 0 target 0 lun 0 Feb 22 10:38:39 smallster > kernel: cd0: Removable CD-ROM SCSI-2 device > Feb 22 10:38:39 smallster kernel: cd0: 1.000MB/s transfers > Feb 22 10:38:39 smallster kernel: cd0: Attempt to query device size > failed: NOT READY, Medium not present > Feb 22 10:40:27 smallster kernel: g_vfs_done():cd0[READ(offset=65536, > length=8192)]error = 5 > Feb 22 10:43:39 smallster kernel: umass0: at ushub2, port 1, addr 2 > (disconnected) > Feb 22 10:43:39 smallster kernel: (cd0:umass-sim0:0:0:0): lost device > Feb 22 10:43:39 smallster kernel: (cd0:umass-sim0:0:0:0): removing device > entry Feb 22 10:43:39 smallster kernel: ugen2.2: at > usbus2 (disconnected) > > The device initially attempts to simulate the presence of a cdrom. > > Maybe this is creating the problem for usb2. > > -kim From w8hdkim at gmail.com Tue Feb 24 01:17:39 2009 From: w8hdkim at gmail.com (Kim Culhan) Date: Tue Feb 24 01:17:45 2009 Subject: reattach 3g0 device: could not allocate new device In-Reply-To: <200902240905.42406.hselasky@c2i.net> References: <89dbfdc30902231031j4407614vdce09e8e58cdc346@mail.gmail.com> <200902232156.14845.hselasky@c2i.net> <89dbfdc30902231458s2c8a1534kb2180c8cd0ddd290@mail.gmail.com> <200902240905.42406.hselasky@c2i.net> Message-ID: <89dbfdc30902240117k7368d60did8bb0e7e6230d5f8@mail.gmail.com> On Tue, Feb 24, 2009 at 3:05 AM, Hans Petter Selasky wrote: > On Monday 23 February 2009, Kim Culhan wrote: >> On Mon, Feb 23, 2009 at 3:56 PM, Hans Petter Selasky > wrote: >> > On Monday 23 February 2009, Kim Culhan wrote: >> >> Running 8.0-CURRENT as of 2-22-09 >> >> >> >> The 3g0 device is a Novatel U727 EVDO wireless radio. >> >> >> >> If the machine boots with the device attached, dmesg reads: >> >> >> >> u3g0: on usbus2 >> >> >> >> Remove the device and this is logged: >> >> >> >> u3g0: at ushub2, port 2, addr 2 (disconnected) >> >> >> >> Reattach the device and there is this message: >> >> >> >> uhub_reattach_port:414: could not allocate new device! >> >> >> >> kernel config has: >> >> >> >> device ? usb2_serial_3g >> >> >> >> Any help is greatly appreciated >> > >> > Hi, >> > >> > Can you turn on USB HUB debugging: >> > >> > sysctl hw.usb2.uhub.debug=15 >> > sysctl hw.usb.uhub.debug=15 >> >> Sure here is dmesg with sysctl hw.usb2.uhub.debug=15 >> >> uhub_read_port_status:259: port 2, wPortStatus=0x0103, >> wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION >> usb2_transfer_power_ref:1470: Adding type 0 to power state >> usb2_transfer_power_ref:1483: needs power >> u3g_huawei_init:278: >> usb2_alloc_device:1618: Found Huawei auto-install disk! >> usb2_bus_port_set_device:1334: bus 0xc6733cf0 devices[2] = 0xc6bc6000 >> ugen2.2: at usbus2 >> ugen2.2: at usbus2 (disconnected) >> usb2_bus_port_set_device:1334: bus 0xc6733cf0 devices[2] = 0 >> uhub_reattach_port:414: could not allocate new device! >> usb2_needs_explore:1345: >> usb2_bus_powerd:1516: bus=0xc670bcf0 >> usb2_bus_powerd:1599: Recomputing power masks >> uhub_explore:522: udev=0xc6a93000 addr=1 >> >> With the old usb, this was returned: >> >> Feb 22 10:38:37 smallster kernel: ugen2.2: at >> usbus2 Feb 22 10:38:37 smallster kernel: umass0: > Novatel Wireless CDMA, class 0/0, rev 1.10/0.00, addr 2> on usbus2 >> Feb 22 10:38:37 smallster kernel: umass0: ?SCSI over Bulk-Only; quirks = >> 0x0000 Feb 22 10:38:38 smallster kernel: umass0:1:0:-1: Attached to scbus1 >> Feb 22 10:38:39 smallster kernel: (probe0:umass-sim0:0:0:0): TEST UNIT >> READY. CDB: 0 0 0 0 0 0 >> Feb 22 10:38:39 smallster kernel: (probe0:umass-sim0:0:0:0): CAM >> Status: SCSI Status Error >> Feb 22 10:38:39 smallster kernel: (probe0:umass-sim0:0:0:0): SCSI >> Status: Check Condition >> Feb 22 10:38:39 smallster kernel: (probe0:umass-sim0:0:0:0): NOT READY >> asc:3a,0 Feb 22 10:38:39 smallster kernel: (probe0:umass-sim0:0:0:0): >> Medium not present Feb 22 10:38:39 smallster kernel: >> (probe0:umass-sim0:0:0:0): Unretryable error Feb 22 10:38:39 smallster >> kernel: cd0 at umass-sim0 bus 0 target 0 lun 0 Feb 22 10:38:39 smallster >> kernel: cd0: Removable CD-ROM SCSI-2 device >> Feb 22 10:38:39 smallster kernel: cd0: 1.000MB/s transfers >> Feb 22 10:38:39 smallster kernel: cd0: Attempt to query device size >> failed: NOT READY, Medium not present >> Feb 22 10:40:27 smallster kernel: g_vfs_done():cd0[READ(offset=65536, >> length=8192)]error = 5 >> Feb 22 10:43:39 smallster kernel: umass0: at ushub2, port 1, addr 2 >> (disconnected) >> Feb 22 10:43:39 smallster kernel: (cd0:umass-sim0:0:0:0): lost device >> Feb 22 10:43:39 smallster kernel: (cd0:umass-sim0:0:0:0): removing device >> entry Feb 22 10:43:39 smallster kernel: ugen2.2: at >> usbus2 (disconnected) >> >> The device initially attempts to simulate the presence of a cdrom. >> >> Maybe this is creating the problem for usb2. >> >> -kim > Hi Kim, > > In the latter case you don't have the U3G driver loaded. The U3G driver will > detect the CD-ROM and send an eject or propritary command. After some while > the device should show up like a u3g0 device. The error message you get is > like it should be when CD-ROM detection is enabled. > > --HPS > The latter case is for the obsolete usb driver but I included it for information RE the CD-ROM eject action. How would it work in the case of the new usb2 driver? -kim From hselasky at c2i.net Tue Feb 24 01:32:05 2009 From: hselasky at c2i.net (Hans Petter Selasky) Date: Tue Feb 24 01:32:13 2009 Subject: reattach 3g0 device: could not allocate new device In-Reply-To: <89dbfdc30902240117k7368d60did8bb0e7e6230d5f8@mail.gmail.com> References: <89dbfdc30902231031j4407614vdce09e8e58cdc346@mail.gmail.com> <200902240905.42406.hselasky@c2i.net> <89dbfdc30902240117k7368d60did8bb0e7e6230d5f8@mail.gmail.com> Message-ID: <200902241034.31298.hselasky@c2i.net> On Tuesday 24 February 2009, Kim Culhan wrote: > On Tue, Feb 24, 2009 at 3:05 AM, Hans Petter Selasky wrote: > > On Monday 23 February 2009, Kim Culhan wrote: > >> On Mon, Feb 23, 2009 at 3:56 PM, Hans Petter Selasky > > > > wrote: > >> > On Monday 23 February 2009, Kim Culhan wrote: > >> >> Running 8.0-CURRENT as of 2-22-09 > >> >> > >> >> The 3g0 device is a Novatel U727 EVDO wireless radio. > >> >> > >> >> If the machine boots with the device attached, dmesg reads: > >> >> > >> >> u3g0: on usbus2 > >> >> > >> >> Remove the device and this is logged: > >> >> > >> >> u3g0: at ushub2, port 2, addr 2 (disconnected) > >> >> > >> >> Reattach the device and there is this message: > >> >> > >> >> uhub_reattach_port:414: could not allocate new device! > >> >> > >> >> kernel config has: > >> >> > >> >> device ? usb2_serial_3g > >> >> > >> >> Any help is greatly appreciated > >> > > >> > Hi, > >> > > >> > Can you turn on USB HUB debugging: > >> > > >> > sysctl hw.usb2.uhub.debug=15 > >> > sysctl hw.usb.uhub.debug=15 > >> > >> Sure here is dmesg with sysctl hw.usb2.uhub.debug=15 > >> > >> uhub_read_port_status:259: port 2, wPortStatus=0x0103, > >> wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION > >> usb2_transfer_power_ref:1470: Adding type 0 to power state > >> usb2_transfer_power_ref:1483: needs power > >> u3g_huawei_init:278: > >> usb2_alloc_device:1618: Found Huawei auto-install disk! > >> usb2_bus_port_set_device:1334: bus 0xc6733cf0 devices[2] = 0xc6bc6000 > >> ugen2.2: at usbus2 > >> ugen2.2: at usbus2 (disconnected) > >> usb2_bus_port_set_device:1334: bus 0xc6733cf0 devices[2] = 0 > >> uhub_reattach_port:414: could not allocate new device! > >> usb2_needs_explore:1345: > >> usb2_bus_powerd:1516: bus=0xc670bcf0 > >> usb2_bus_powerd:1599: Recomputing power masks > >> uhub_explore:522: udev=0xc6a93000 addr=1 > >> > >> With the old usb, this was returned: > >> > >> Feb 22 10:38:37 smallster kernel: ugen2.2: at > >> usbus2 Feb 22 10:38:37 smallster kernel: umass0: >> Novatel Wireless CDMA, class 0/0, rev 1.10/0.00, addr 2> on usbus2 > >> Feb 22 10:38:37 smallster kernel: umass0: ?SCSI over Bulk-Only; quirks = > >> 0x0000 Feb 22 10:38:38 smallster kernel: umass0:1:0:-1: Attached to > >> scbus1 Feb 22 10:38:39 smallster kernel: (probe0:umass-sim0:0:0:0): TEST > >> UNIT READY. CDB: 0 0 0 0 0 0 > >> Feb 22 10:38:39 smallster kernel: (probe0:umass-sim0:0:0:0): CAM > >> Status: SCSI Status Error > >> Feb 22 10:38:39 smallster kernel: (probe0:umass-sim0:0:0:0): SCSI > >> Status: Check Condition > >> Feb 22 10:38:39 smallster kernel: (probe0:umass-sim0:0:0:0): NOT READY > >> asc:3a,0 Feb 22 10:38:39 smallster kernel: (probe0:umass-sim0:0:0:0): > >> Medium not present Feb 22 10:38:39 smallster kernel: > >> (probe0:umass-sim0:0:0:0): Unretryable error Feb 22 10:38:39 smallster > >> kernel: cd0 at umass-sim0 bus 0 target 0 lun 0 Feb 22 10:38:39 smallster > >> kernel: cd0: Removable CD-ROM SCSI-2 device > >> Feb 22 10:38:39 smallster kernel: cd0: 1.000MB/s transfers > >> Feb 22 10:38:39 smallster kernel: cd0: Attempt to query device size > >> failed: NOT READY, Medium not present > >> Feb 22 10:40:27 smallster kernel: g_vfs_done():cd0[READ(offset=65536, > >> length=8192)]error = 5 > >> Feb 22 10:43:39 smallster kernel: umass0: at ushub2, port 1, addr 2 > >> (disconnected) > >> Feb 22 10:43:39 smallster kernel: (cd0:umass-sim0:0:0:0): lost device > >> Feb 22 10:43:39 smallster kernel: (cd0:umass-sim0:0:0:0): removing > >> device entry Feb 22 10:43:39 smallster kernel: ugen2.2: >> Wireless Inc.> at usbus2 (disconnected) > >> > >> The device initially attempts to simulate the presence of a cdrom. > >> > >> Maybe this is creating the problem for usb2. > >> > >> -kim > > > > Hi Kim, > > > > In the latter case you don't have the U3G driver loaded. The U3G driver > > will detect the CD-ROM and send an eject or propritary command. After > > some while the device should show up like a u3g0 device. The error > > message you get is like it should be when CD-ROM detection is enabled. > > > > --HPS > > The latter case is for the obsolete usb driver but I included it for > information RE > the CD-ROM eject action. > > How would it work in the case of the new usb2 driver? Hi, It works the same like in the old driver, if you unload the u3g module (which takes around 16 seconds) --HPS From gavin at FreeBSD.org Tue Feb 24 08:31:12 2009 From: gavin at FreeBSD.org (gavin@FreeBSD.org) Date: Tue Feb 24 08:31:24 2009 Subject: usb/132066: [ukbd] Keyboard failure USB keyboard DELL 760 Message-ID: <200902241631.n1OGVAJK045547@freefall.freebsd.org> Old Synopsis: Keyboard failure USB keyboard DELL 760 New Synopsis: [ukbd] Keyboard failure USB keyboard DELL 760 Responsible-Changed-From-To: freebsd-i386->freebsd-usb Responsible-Changed-By: gavin Responsible-Changed-When: Tue Feb 24 16:29:54 UTC 2009 Responsible-Changed-Why: Over to maintainer(s) http://www.freebsd.org/cgi/query-pr.cgi?pr=132066 From gavin at FreeBSD.org Tue Feb 24 08:34:05 2009 From: gavin at FreeBSD.org (gavin@FreeBSD.org) Date: Tue Feb 24 08:34:12 2009 Subject: usb/132066: [ukbd] Keyboard failure USB keyboard DELL 760 Message-ID: <200902241634.n1OGY4MO046761@freefall.freebsd.org> Synopsis: [ukbd] Keyboard failure USB keyboard DELL 760 State-Changed-From-To: open->feedback State-Changed-By: gavin State-Changed-When: Tue Feb 24 16:32:42 UTC 2009 State-Changed-Why: To submitter: Can you please give the output of "usbdevs -v"? Also, please reboot and select the "verbose logging" option from the menu, and supply the output of "dmesg |grep -A 2 -B 2 kbd" http://www.freebsd.org/cgi/query-pr.cgi?pr=132066 From w8hdkim at gmail.com Tue Feb 24 13:38:22 2009 From: w8hdkim at gmail.com (Kim Culhan) Date: Tue Feb 24 13:38:28 2009 Subject: Novatel U727 not recognized Message-ID: <89dbfdc30902241338h2e56af93q5d8fb3905454ea36@mail.gmail.com> On Tue, Feb 24, 2009 at 4:34 AM, Hans Petter Selasky wrote: > On Tuesday 24 February 2009, Kim Culhan wrote: >> On Tue, Feb 24, 2009 at 3:05 AM, Hans Petter Selasky > wrote: >> > On Monday 23 February 2009, Kim Culhan wrote: >> >> On Mon, Feb 23, 2009 at 3:56 PM, Hans Petter Selasky >> > >> > wrote: >> >> > On Monday 23 February 2009, Kim Culhan wrote: >> >> >> Running 8.0-CURRENT as of 2-22-09 >> >> >> >> >> >> The 3g0 device is a Novatel U727 EVDO wireless radio. >> >> >> >> >> >> If the machine boots with the device attached, dmesg reads: >> >> >> >> >> >> u3g0: on usbus2 >> >> >> >> >> >> Remove the device and this is logged: >> >> >> >> >> >> u3g0: at ushub2, port 2, addr 2 (disconnected) >> >> >> >> >> >> Reattach the device and there is this message: >> >> >> >> >> >> uhub_reattach_port:414: could not allocate new device! >> >> >> >> >> >> kernel config has: >> >> >> >> >> >> device ? usb2_serial_3g >> >> >> >> >> >> Any help is greatly appreciated >> >> > >> >> > Hi, >> >> > >> >> > Can you turn on USB HUB debugging: >> >> > >> >> > sysctl hw.usb2.uhub.debug=15 >> >> > sysctl hw.usb.uhub.debug=15 >> >> >> >> Sure here is dmesg with sysctl hw.usb2.uhub.debug=15 >> >> >> >> uhub_read_port_status:259: port 2, wPortStatus=0x0103, >> >> wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION >> >> usb2_transfer_power_ref:1470: Adding type 0 to power state >> >> usb2_transfer_power_ref:1483: needs power >> >> u3g_huawei_init:278: >> >> usb2_alloc_device:1618: Found Huawei auto-install disk! >> >> usb2_bus_port_set_device:1334: bus 0xc6733cf0 devices[2] = 0xc6bc6000 >> >> ugen2.2: at usbus2 >> >> ugen2.2: at usbus2 (disconnected) >> >> usb2_bus_port_set_device:1334: bus 0xc6733cf0 devices[2] = 0 >> >> uhub_reattach_port:414: could not allocate new device! >> >> usb2_needs_explore:1345: >> >> usb2_bus_powerd:1516: bus=0xc670bcf0 >> >> usb2_bus_powerd:1599: Recomputing power masks >> >> uhub_explore:522: udev=0xc6a93000 addr=1 >> >> >> >> With the old usb, this was returned: >> >> >> >> Feb 22 10:38:37 smallster kernel: ugen2.2: at >> >> usbus2 Feb 22 10:38:37 smallster kernel: umass0: > >> Novatel Wireless CDMA, class 0/0, rev 1.10/0.00, addr 2> on usbus2 >> >> Feb 22 10:38:37 smallster kernel: umass0: ?SCSI over Bulk-Only; quirks = >> >> 0x0000 Feb 22 10:38:38 smallster kernel: umass0:1:0:-1: Attached to >> >> scbus1 Feb 22 10:38:39 smallster kernel: (probe0:umass-sim0:0:0:0): TEST >> >> UNIT READY. CDB: 0 0 0 0 0 0 >> >> Feb 22 10:38:39 smallster kernel: (probe0:umass-sim0:0:0:0): CAM >> >> Status: SCSI Status Error >> >> Feb 22 10:38:39 smallster kernel: (probe0:umass-sim0:0:0:0): SCSI >> >> Status: Check Condition >> >> Feb 22 10:38:39 smallster kernel: (probe0:umass-sim0:0:0:0): NOT READY >> >> asc:3a,0 Feb 22 10:38:39 smallster kernel: (probe0:umass-sim0:0:0:0): >> >> Medium not present Feb 22 10:38:39 smallster kernel: >> >> (probe0:umass-sim0:0:0:0): Unretryable error Feb 22 10:38:39 smallster >> >> kernel: cd0 at umass-sim0 bus 0 target 0 lun 0 Feb 22 10:38:39 smallster >> >> kernel: cd0: Removable CD-ROM SCSI-2 device >> >> Feb 22 10:38:39 smallster kernel: cd0: 1.000MB/s transfers >> >> Feb 22 10:38:39 smallster kernel: cd0: Attempt to query device size >> >> failed: NOT READY, Medium not present >> >> Feb 22 10:40:27 smallster kernel: g_vfs_done():cd0[READ(offset=65536, >> >> length=8192)]error = 5 >> >> Feb 22 10:43:39 smallster kernel: umass0: at ushub2, port 1, addr 2 >> >> (disconnected) >> >> Feb 22 10:43:39 smallster kernel: (cd0:umass-sim0:0:0:0): lost device >> >> Feb 22 10:43:39 smallster kernel: (cd0:umass-sim0:0:0:0): removing >> >> device entry Feb 22 10:43:39 smallster kernel: ugen2.2: > >> Wireless Inc.> at usbus2 (disconnected) >> >> >> >> The device initially attempts to simulate the presence of a cdrom. >> >> >> >> Maybe this is creating the problem for usb2. >> >> >> >> -kim >> > >> > Hi Kim, >> > >> > In the latter case you don't have the U3G driver loaded. The U3G driver >> > will detect the CD-ROM and send an eject or propritary command. After >> > some while the device should show up like a u3g0 device. The error >> > message you get is like it should be when CD-ROM detection is enabled. AFAIK there is no seperate CD-ROM detection which can be enabled/disabled. The device does not show up as a u3g0 device unless the u3g module is loaded after the system is booted with _u3g commented out of the kernel config_ After boot: kldload u3g returns u3g0: on usbus2 u3g0: Found 4 ports. If I remove the usb device it reports: u3g0: at ushub2, port 2, addr 2 (disconnected) umass0: at ushub2, port 2, addr 2 (disconnected) (da0:umass-sim0:0:0:0): lost device (da0:umass-sim0:0:0:0): removing device entry ugen2.2: at usbus2 (disconnected) If I reattach the device it reports: u3g_huawei_init:278: usb2_alloc_device:1618: Found Huawei auto-install disk! ugen2.2: at usbus2 ugen2.2: at usbus2 (disconnected) uhub_reattach_port:414: could not allocate new device! Any info is very greatly appreciated. -kim From melkov at comptek.ru Tue Feb 24 17:20:03 2009 From: melkov at comptek.ru (Alexander Melkov) Date: Tue Feb 24 17:20:10 2009 Subject: usb/132080: [patch] [usb] Kernel panic after NOMEM caused by rum card Message-ID: <200902250112.n1P1CQGK027474@www.freebsd.org> >Number: 132080 >Category: usb >Synopsis: [patch] [usb] Kernel panic after NOMEM caused by rum card >Confidential: no >Severity: serious >Priority: medium >Responsible: freebsd-usb >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Wed Feb 25 01:20:02 UTC 2009 >Closed-Date: >Last-Modified: >Originator: Alexander Melkov >Release: 7.1-STABLE >Organization: >Environment: FreeBSD melkov.ru 7.1-STABLE FreeBSD 7.1-STABLE #14: Tue Feb 24 06:28:45 MSK 2009 root_at_melkov.ru:/usr/obj/usr/src/sys/MELKOV amd64 >Description: I have device which is Cisco-Linksys Compact Wireless-G USB Adapter that runs in hostap mode (i.e. wifi access point). Sometimes it malfunctions (that may happen several times a day), at that moment I have message "rum0: could not transmit buffer: NOMEM" from kernel. Right after the message kernel crashes upon read from (nearly) null address. System log: Feb 23 19:46:22 melkov kernel: rum0: could not transmit buffer: NOMEM Feb 23 19:46:22 melkov kernel: Feb 23 19:46:22 melkov kernel: Feb 23 19:46:22 melkov kernel: Fatal trap 12: page fault while in kernel mode Feb 23 19:46:22 melkov kernel: fault virtual address = 0x290 Feb 23 19:46:22 melkov kernel: fault code = supervisor read data, page not present Feb 23 19:46:22 melkov kernel: instruction pointer = 0x8:0xffffffff80430b0d Feb 23 19:46:22 melkov kernel: stack pointer = 0x10:0xfffffffef21caa80 Feb 23 19:46:22 melkov kernel: frame pointer = 0x10:0xffffff00430cd080 Feb 23 19:46:22 melkov kernel: code segment = base 0x0, limit 0xfffff, type 0x1b Feb 23 19:46:22 melkov kernel: = DPL 0, pres 1, long 1, def32 0, gran 1 Feb 23 19:46:22 melkov kernel: processor eflags = interrupt enabled, resume, IOPL = 0 Feb 23 19:46:22 melkov kernel: current process = 20 (swi6: Giant taskq) Feb 23 19:46:22 melkov kernel: trap number = 12 Feb 23 19:46:22 melkov kernel: panic: page fault (kgdb) bt 12 #0 doadump () at pcpu.h:195 #1 0x0000000000000004 in ?? () #2 0xffffffff804c8fc4 in boot (howto=260) at /usr/src/sys/kern/kern_shutdown.c:418 #3 0xffffffff804c937c in panic (fmt=0xffffffff8081f82b "%s") at /usr/src/sys/kern/kern_shutdown.c:574 #4 0xffffffff8077b48f in trap_fatal (frame=0xffffff0001514000, eva=Variable "eva" is not available. ) at /usr/src/sys/amd64/amd64/trap.c:764 #5 0xffffffff8077b865 in trap_pfault (frame=0xfffffffef21ca9d0, usermode=0) at /usr/src/sys/amd64/amd64/trap.c:680 #6 0xffffffff8077c195 in trap (frame=0xfffffffef21ca9d0) at /usr/src/sys/amd64/amd64/trap.c:449 #7 0xffffffff80764fee in calltrap () at /usr/src/sys/amd64/amd64/exception.S:209 #8 0xffffffff80430b0d in usb_transfer_complete (xfer=0xffffff0004d83800) at /usr/src/sys/dev/usb/usbdi.c:949 #9 0xffffffff8043119b in usbd_transfer (xfer=0xffffff0004d83800) at /usr/src/sys/dev/usb/usbdi.c:320 #10 0xffffffff804127d1 in rum_start (ifp=0xffffff0004e12000) at /usr/src/sys/dev/usb/if_rum.c:1360 #11 0xffffffff804fdb60 in taskqueue_run (queue=0xffffff00014d6780) at /usr/src/sys/kern/subr_taskqueue.c:282 (More stack frames follow...) #8 0xffffffff80430b0d in usb_transfer_complete (xfer=0xffffff0004d83800) at /usr/src/sys/dev/usb/usbdi.c:949 949 STAILQ_REMOVE_HEAD(&pipe->queue, next); (kgdb) p pipe->queue $12 = {stqh_first = 0x0, stqh_last = 0xffffff00430cd0a0} Apparently there's an attempt to STAILQ_REMOVE_HEAD from an empty pipe->queue, within usb_transfer_complete(). The USBD_NOMEM error code that rum_txeof() complains about probably comes from unsuccessful call to bus_dmamap_create() within usbd_transfer(), which I didn't investigate. >How-To-Repeat: Insert ralink-based card into usb slot and set up WPA2 PSK access point according to The Handbook. Connect to this access point from another station, perform heavy activity, periodically conecting and disconnecting. >Fix: usbd_start_transfer() has two error-handling branches first of whose called usb_insert_transfer() that ensured the pipe->queue to be non-empty later in usb_transfer_complete(). I've added similar call to the second error-handling branch. ==> usbdi.c.patch <== --- sys/dev/usb/usbdi.c.orig 2009-02-24 06:23:54.000000000 +0300 +++ sys/dev/usb/usbdi.c 2009-02-24 07:01:27.000000000 +0300 @@ -394,6 +394,8 @@ bus_dmamap_destroy(tag, dmap->map); xfer->rqflags &= ~URQ_AUTO_DMABUF; } + /* XXX: usb_transfer_complete crashes unless we call usb_insert_transfer */ + usb_insert_transfer(xfer); xfer->status = err; usb_transfer_complete(xfer); return; >Release-Note: >Audit-Trail: >Unformatted: From hselasky at c2i.net Tue Feb 24 22:57:32 2009 From: hselasky at c2i.net (Hans Petter Selasky) Date: Tue Feb 24 22:57:39 2009 Subject: Novatel U727 not recognized In-Reply-To: <89dbfdc30902241338h2e56af93q5d8fb3905454ea36@mail.gmail.com> References: <89dbfdc30902241338h2e56af93q5d8fb3905454ea36@mail.gmail.com> Message-ID: <200902250800.00365.hselasky@c2i.net> On Tuesday 24 February 2009, Kim Culhan wrote: > On Tue, Feb 24, 2009 at 4:34 AM, Hans Petter Selasky wrote: > > On Tuesday 24 February 2009, Kim Culhan wrote: > >> On Tue, Feb 24, 2009 at 3:05 AM, Hans Petter Selasky > > > > wrote: > >> > On Monday 23 February 2009, Kim Culhan wrote: > >> >> On Mon, Feb 23, 2009 at 3:56 PM, Hans Petter Selasky > >> >> > >> > > >> > wrote: > >> >> > On Monday 23 February 2009, Kim Culhan wrote: > >> >> >> Running 8.0-CURRENT as of 2-22-09 > >> >> >> > >> >> >> The 3g0 device is a Novatel U727 EVDO wireless radio. > >> >> >> > >> >> >> If the machine boots with the device attached, dmesg reads: > >> >> >> > >> >> >> u3g0: on usbus2 > >> >> >> > >> >> >> Remove the device and this is logged: > >> >> >> > >> >> >> u3g0: at ushub2, port 2, addr 2 (disconnected) > >> >> >> > >> >> >> Reattach the device and there is this message: > >> >> >> > >> >> >> uhub_reattach_port:414: could not allocate new device! > >> >> >> > >> >> >> kernel config has: > >> >> >> > >> >> >> device ? usb2_serial_3g > >> >> >> > >> >> >> Any help is greatly appreciated > >> >> > > >> >> > Hi, > >> >> > > >> >> > Can you turn on USB HUB debugging: > >> >> > > >> >> > sysctl hw.usb2.uhub.debug=15 > >> >> > sysctl hw.usb.uhub.debug=15 > >> >> > >> >> Sure here is dmesg with sysctl hw.usb2.uhub.debug=15 > >> >> > >> >> uhub_read_port_status:259: port 2, wPortStatus=0x0103, > >> >> wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION > >> >> usb2_transfer_power_ref:1470: Adding type 0 to power state > >> >> usb2_transfer_power_ref:1483: needs power > >> >> u3g_huawei_init:278: > >> >> usb2_alloc_device:1618: Found Huawei auto-install disk! > >> >> usb2_bus_port_set_device:1334: bus 0xc6733cf0 devices[2] = 0xc6bc6000 > >> >> ugen2.2: at usbus2 > >> >> ugen2.2: at usbus2 (disconnected) > >> >> usb2_bus_port_set_device:1334: bus 0xc6733cf0 devices[2] = 0 > >> >> uhub_reattach_port:414: could not allocate new device! > >> >> usb2_needs_explore:1345: > >> >> usb2_bus_powerd:1516: bus=0xc670bcf0 > >> >> usb2_bus_powerd:1599: Recomputing power masks > >> >> uhub_explore:522: udev=0xc6a93000 addr=1 > >> >> > >> >> With the old usb, this was returned: > >> >> > >> >> Feb 22 10:38:37 smallster kernel: ugen2.2: at > >> >> usbus2 Feb 22 10:38:37 smallster kernel: umass0: >> >> Inc. Novatel Wireless CDMA, class 0/0, rev 1.10/0.00, addr 2> on > >> >> usbus2 Feb 22 10:38:37 smallster kernel: umass0: ?SCSI over > >> >> Bulk-Only; quirks = 0x0000 Feb 22 10:38:38 smallster kernel: > >> >> umass0:1:0:-1: Attached to scbus1 Feb 22 10:38:39 smallster kernel: > >> >> (probe0:umass-sim0:0:0:0): TEST UNIT READY. CDB: 0 0 0 0 0 0 > >> >> Feb 22 10:38:39 smallster kernel: (probe0:umass-sim0:0:0:0): CAM > >> >> Status: SCSI Status Error > >> >> Feb 22 10:38:39 smallster kernel: (probe0:umass-sim0:0:0:0): SCSI > >> >> Status: Check Condition > >> >> Feb 22 10:38:39 smallster kernel: (probe0:umass-sim0:0:0:0): NOT > >> >> READY asc:3a,0 Feb 22 10:38:39 smallster kernel: > >> >> (probe0:umass-sim0:0:0:0): Medium not present Feb 22 10:38:39 > >> >> smallster kernel: > >> >> (probe0:umass-sim0:0:0:0): Unretryable error Feb 22 10:38:39 > >> >> smallster kernel: cd0 at umass-sim0 bus 0 target 0 lun 0 Feb 22 > >> >> 10:38:39 smallster kernel: cd0: Removable > >> >> CD-ROM SCSI-2 device Feb 22 10:38:39 smallster kernel: cd0: 1.000MB/s > >> >> transfers > >> >> Feb 22 10:38:39 smallster kernel: cd0: Attempt to query device size > >> >> failed: NOT READY, Medium not present > >> >> Feb 22 10:40:27 smallster kernel: g_vfs_done():cd0[READ(offset=65536, > >> >> length=8192)]error = 5 > >> >> Feb 22 10:43:39 smallster kernel: umass0: at ushub2, port 1, addr 2 > >> >> (disconnected) > >> >> Feb 22 10:43:39 smallster kernel: (cd0:umass-sim0:0:0:0): lost device > >> >> Feb 22 10:43:39 smallster kernel: (cd0:umass-sim0:0:0:0): removing > >> >> device entry Feb 22 10:43:39 smallster kernel: ugen2.2: >> >> Wireless Inc.> at usbus2 (disconnected) > >> >> > >> >> The device initially attempts to simulate the presence of a cdrom. > >> >> > >> >> Maybe this is creating the problem for usb2. > >> >> > >> >> -kim > >> > > >> > Hi Kim, > >> > > >> > In the latter case you don't have the U3G driver loaded. The U3G > >> > driver will detect the CD-ROM and send an eject or propritary command. > >> > After some while the device should show up like a u3g0 device. The > >> > error message you get is like it should be when CD-ROM detection is > >> > enabled. > > AFAIK there is no seperate CD-ROM detection which can be enabled/disabled. > > The device does not show up as a u3g0 device unless the u3g module is > loaded after the system is booted with _u3g commented out of the kernel > config_ > > After boot: > > kldload u3g > > returns > > u3g0: on usbus2 > u3g0: Found 4 ports. > > If I remove the usb device it reports: > > u3g0: at ushub2, port 2, addr 2 (disconnected) > umass0: at ushub2, port 2, addr 2 (disconnected) > (da0:umass-sim0:0:0:0): lost device > (da0:umass-sim0:0:0:0): removing device entry > ugen2.2: at usbus2 (disconnected) > > If I reattach the device it reports: > > u3g_huawei_init:278: > usb2_alloc_device:1618: Found Huawei auto-install disk! > ugen2.2: at usbus2 > ugen2.2: at usbus2 (disconnected) > uhub_reattach_port:414: could not allocate new device! > If your device does not re-appear within 10 seconds, then try this: 1) Add a quirk: kldload usb_quirk kldload usb2_quirk usbconfig add_dev_quirk_vplh vid pid 0 0xFFFF UQ_CFG_INDEX_0 Replace vid and pid by the info provided by "usbconfig -u 2 -a 2 dump_device_desc". 2) Dump USB configuration: usbconfig -u 2 -a 2 dump_curr_config_desc --HPS From hselasky at c2i.net Tue Feb 24 23:08:24 2009 From: hselasky at c2i.net (Hans Petter Selasky) Date: Tue Feb 24 23:08:31 2009 Subject: usb/132080: [patch] [usb] Kernel panic after NOMEM caused by rum card In-Reply-To: <200902250112.n1P1CQGK027474@www.freebsd.org> References: <200902250112.n1P1CQGK027474@www.freebsd.org> Message-ID: <200902250810.51822.hselasky@c2i.net> Hi, The RUM timeouts you are seeing I am aware about. They happen most likely because the WLAN channel is set when the device is in the running state on the RUM device due to WLAN re-keying or something like that. Maybe you can confirm that the time from start of device with heavy download until it gets the first timeout is 10minutes? This issue is actually a RUM firmware issue. If it has frames pending for TX and we set the channel, the chip will simply reset or do strange things. Possible RUM workaround: Set the same WLAN channel only once. I think Andrew Thompson is working on this. I have some patches in the USB P4 project for 8-current which fix the problem to a level where TX will dissappear for 4 seconds every 10 minutes, but there will be no device timeout! The final patch should solve the problem completely, but I need some help to figure out when we should ignore set_channel requests. --HPS On Wednesday 25 February 2009, Alexander Melkov wrote: > >Number: 132080 > >Category: usb > >Synopsis: [patch] [usb] Kernel panic after NOMEM caused by rum card > >Confidential: no > >Severity: serious > >Priority: medium > >Responsible: freebsd-usb > >State: open > >Quarter: > >Keywords: > >Date-Required: > >Class: sw-bug > >Submitter-Id: current-users > >Arrival-Date: Wed Feb 25 01:20:02 UTC 2009 > >Closed-Date: > >Last-Modified: > >Originator: Alexander Melkov > >Release: 7.1-STABLE > >Organization: > >Environment: > > FreeBSD melkov.ru 7.1-STABLE FreeBSD 7.1-STABLE #14: Tue Feb 24 06:28:45 > MSK 2009 root_at_melkov.ru:/usr/obj/usr/src/sys/MELKOV amd64 > > >Description: > > I have device which is Cisco-Linksys Compact Wireless-G USB Adapter > that runs in hostap mode (i.e. wifi access point). Sometimes it > malfunctions (that may happen several times a day), at that moment I have > message "rum0: could not transmit buffer: NOMEM" from kernel. Right after > the message kernel crashes upon read from (nearly) null address. > From hselasky at c2i.net Wed Feb 25 00:10:05 2009 From: hselasky at c2i.net (Hans Petter Selasky) Date: Wed Feb 25 00:10:16 2009 Subject: usb/132080: [patch] [usb] Kernel panic after NOMEM caused by rum card Message-ID: <200902250810.n1P8A5Ij077287@freefall.freebsd.org> The following reply was made to PR usb/132080; it has been noted by GNATS. From: Hans Petter Selasky To: freebsd-usb@freebsd.org, Andrew Thompson , Sam Leffler Cc: Alexander Melkov , freebsd-gnats-submit@freebsd.org Subject: Re: usb/132080: [patch] [usb] Kernel panic after NOMEM caused by rum card Date: Wed, 25 Feb 2009 08:10:50 +0100 Hi, The RUM timeouts you are seeing I am aware about. They happen most likely because the WLAN channel is set when the device is in the running state on the RUM device due to WLAN re-keying or something like that. Maybe you can confirm that the time from start of device with heavy download until it gets the first timeout is 10minutes? This issue is actually a RUM firmware issue. If it has frames pending for TX and we set the channel, the chip will simply reset or do strange things. Possible RUM workaround: Set the same WLAN channel only once. I think Andrew Thompson is working on this. I have some patches in the USB P4 project for 8-current which fix the problem to a level where TX will dissappear for 4 seconds every 10 minutes, but there will be no device timeout! The final patch should solve the problem completely, but I need some help to figure out when we should ignore set_channel requests. --HPS On Wednesday 25 February 2009, Alexander Melkov wrote: > >Number: 132080 > >Category: usb > >Synopsis: [patch] [usb] Kernel panic after NOMEM caused by rum card > >Confidential: no > >Severity: serious > >Priority: medium > >Responsible: freebsd-usb > >State: open > >Quarter: > >Keywords: > >Date-Required: > >Class: sw-bug > >Submitter-Id: current-users > >Arrival-Date: Wed Feb 25 01:20:02 UTC 2009 > >Closed-Date: > >Last-Modified: > >Originator: Alexander Melkov > >Release: 7.1-STABLE > >Organization: > >Environment: > > FreeBSD melkov.ru 7.1-STABLE FreeBSD 7.1-STABLE #14: Tue Feb 24 06:28:45 > MSK 2009 root_at_melkov.ru:/usr/obj/usr/src/sys/MELKOV amd64 > > >Description: > > I have device which is Cisco-Linksys Compact Wireless-G USB Adapter > that runs in hostap mode (i.e. wifi access point). Sometimes it > malfunctions (that may happen several times a day), at that moment I have > message "rum0: could not transmit buffer: NOMEM" from kernel. Right after > the message kernel crashes upon read from (nearly) null address. > From melkov at yandex-team.ru Wed Feb 25 01:44:12 2009 From: melkov at yandex-team.ru (Alexander Melkov) Date: Wed Feb 25 01:44:21 2009 Subject: usb/132080: [patch] [usb] Kernel panic after NOMEM caused by rum card References: <200902250112.n1P1CQGK027474@www.freebsd.org> <200902250810.51822.hselasky@c2i.net> Message-ID: Hello! > Maybe you can > confirm that the time from start of device with heavy download until it gets > the first timeout is 10minutes? I've unplugged and reinserted the usb card, then restarted wifi and started network activity. There doesn't seem to be any timeout within 21 minutes. There were 3 consecutive device timeouts yesterday (since my system doesn't reboot any more). Feb 24 10:42:49 melkov kernel: rum0: could not transmit buffer: NOMEM Feb 24 10:42:49 melkov kernel: rum0: could not transmit buffer: NOMEM Feb 24 10:42:54 melkov kernel: rum0: device timeout Feb 24 10:57:26 melkov kernel: rum0: could not transmit buffer: NOMEM Feb 24 10:57:26 melkov kernel: rum0: could not transmit buffer: NOMEM Feb 24 10:57:31 melkov kernel: rum0: device timeout Feb 24 11:05:02 melkov kernel: rum0: could not transmit buffer: NOMEM Feb 24 11:05:02 melkov kernel: rum0: could not transmit buffer: NOMEM Feb 24 11:05:06 melkov kernel: rum0: device timeout Between the timeouts I've restarted hostapd daemon (manually) to get wifi service working again. Notably timeout #3 comes 7.5 minutes after #2. --Alexander From: "Hans Petter Selasky" , Wednesday, February 25, 2009 10:10 > Hi, > > The RUM timeouts you are seeing I am aware about. They happen most likely > because the WLAN channel is set when the device is in the running state on > the RUM device due to WLAN re-keying or something like that. Maybe you can > confirm that the time from start of device with heavy download until it gets > the first timeout is 10minutes? > > This issue is actually a RUM firmware issue. If it has frames pending for TX > and we set the channel, the chip will simply reset or do strange things. > > Possible RUM workaround: Set the same WLAN channel only once. > > I think Andrew Thompson is working on this. I have some patches in the USB P4 > project for 8-current which fix the problem to a level where TX will > dissappear for 4 seconds every 10 minutes, but there will be no device > timeout! The final patch should solve the problem completely, but I need some > help to figure out when we should ignore set_channel requests. > > --HPS > > On Wednesday 25 February 2009, Alexander Melkov wrote: >> >Number: 132080 >> >Category: usb >> >Synopsis: [patch] [usb] Kernel panic after NOMEM caused by rum card >> >Confidential: no >> >Severity: serious >> >Priority: medium >> >Responsible: freebsd-usb >> >State: open >> >Quarter: >> >Keywords: >> >Date-Required: >> >Class: sw-bug >> >Submitter-Id: current-users >> >Arrival-Date: Wed Feb 25 01:20:02 UTC 2009 >> >Closed-Date: >> >Last-Modified: >> >Originator: Alexander Melkov >> >Release: 7.1-STABLE >> >Organization: >> >Environment: >> >> FreeBSD melkov.ru 7.1-STABLE FreeBSD 7.1-STABLE #14: Tue Feb 24 06:28:45 >> MSK 2009 root_at_melkov.ru:/usr/obj/usr/src/sys/MELKOV amd64 >> >> >Description: >> >> I have device which is Cisco-Linksys Compact Wireless-G USB Adapter >> that runs in hostap mode (i.e. wifi access point). Sometimes it >> malfunctions (that may happen several times a day), at that moment I have >> message "rum0: could not transmit buffer: NOMEM" from kernel. Right after >> the message kernel crashes upon read from (nearly) null address. >> From melkov at yandex-team.ru Wed Feb 25 01:50:05 2009 From: melkov at yandex-team.ru (Alexander Melkov) Date: Wed Feb 25 01:50:11 2009 Subject: usb/132080: [patch] [usb] Kernel panic after NOMEM caused by rum card Message-ID: <200902250950.n1P9o3IN057908@freefall.freebsd.org> The following reply was made to PR usb/132080; it has been noted by GNATS. From: "Alexander Melkov" To: "Hans Petter Selasky" , , "Andrew Thompson" , "Sam Leffler" Cc: Subject: Re: usb/132080: [patch] [usb] Kernel panic after NOMEM caused by rum card Date: Wed, 25 Feb 2009 12:25:34 +0300 Hello! > Maybe you can > confirm that the time from start of device with heavy download until it gets > the first timeout is 10minutes? I've unplugged and reinserted the usb card, then restarted wifi and started network activity. There doesn't seem to be any timeout within 21 minutes. There were 3 consecutive device timeouts yesterday (since my system doesn't reboot any more). Feb 24 10:42:49 melkov kernel: rum0: could not transmit buffer: NOMEM Feb 24 10:42:49 melkov kernel: rum0: could not transmit buffer: NOMEM Feb 24 10:42:54 melkov kernel: rum0: device timeout Feb 24 10:57:26 melkov kernel: rum0: could not transmit buffer: NOMEM Feb 24 10:57:26 melkov kernel: rum0: could not transmit buffer: NOMEM Feb 24 10:57:31 melkov kernel: rum0: device timeout Feb 24 11:05:02 melkov kernel: rum0: could not transmit buffer: NOMEM Feb 24 11:05:02 melkov kernel: rum0: could not transmit buffer: NOMEM Feb 24 11:05:06 melkov kernel: rum0: device timeout Between the timeouts I've restarted hostapd daemon (manually) to get wifi service working again. Notably timeout #3 comes 7.5 minutes after #2. --Alexander From: "Hans Petter Selasky" , Wednesday, February 25, 2009 10:10 > Hi, > > The RUM timeouts you are seeing I am aware about. They happen most likely > because the WLAN channel is set when the device is in the running state on > the RUM device due to WLAN re-keying or something like that. Maybe you can > confirm that the time from start of device with heavy download until it gets > the first timeout is 10minutes? > > This issue is actually a RUM firmware issue. If it has frames pending for TX > and we set the channel, the chip will simply reset or do strange things. > > Possible RUM workaround: Set the same WLAN channel only once. > > I think Andrew Thompson is working on this. I have some patches in the USB P4 > project for 8-current which fix the problem to a level where TX will > dissappear for 4 seconds every 10 minutes, but there will be no device > timeout! The final patch should solve the problem completely, but I need some > help to figure out when we should ignore set_channel requests. > > --HPS > > On Wednesday 25 February 2009, Alexander Melkov wrote: >> >Number: 132080 >> >Category: usb >> >Synopsis: [patch] [usb] Kernel panic after NOMEM caused by rum card >> >Confidential: no >> >Severity: serious >> >Priority: medium >> >Responsible: freebsd-usb >> >State: open >> >Quarter: >> >Keywords: >> >Date-Required: >> >Class: sw-bug >> >Submitter-Id: current-users >> >Arrival-Date: Wed Feb 25 01:20:02 UTC 2009 >> >Closed-Date: >> >Last-Modified: >> >Originator: Alexander Melkov >> >Release: 7.1-STABLE >> >Organization: >> >Environment: >> >> FreeBSD melkov.ru 7.1-STABLE FreeBSD 7.1-STABLE #14: Tue Feb 24 06:28:45 >> MSK 2009 root_at_melkov.ru:/usr/obj/usr/src/sys/MELKOV amd64 >> >> >Description: >> >> I have device which is Cisco-Linksys Compact Wireless-G USB Adapter >> that runs in hostap mode (i.e. wifi access point). Sometimes it >> malfunctions (that may happen several times a day), at that moment I have >> message "rum0: could not transmit buffer: NOMEM" from kernel. Right after >> the message kernel crashes upon read from (nearly) null address. >> From gavin at FreeBSD.org Wed Feb 25 02:44:05 2009 From: gavin at FreeBSD.org (gavin@FreeBSD.org) Date: Wed Feb 25 02:44:12 2009 Subject: usb/128590: [patch] [newusb] Updates to NOTES for new USB stack Message-ID: <200902251044.n1PAi5s9002454@freefall.freebsd.org> Synopsis: [patch] [newusb] Updates to NOTES for new USB stack State-Changed-From-To: open->closed State-Changed-By: gavin State-Changed-When: Wed Feb 25 10:41:16 UTC 2009 State-Changed-Why: Thanks for the submission, however now that USB2 is in it's permeanant location and has been renamed to match the old naming system, I seen no need for this patch, as the existing contents of NOTES covers the new USB stack. http://www.freebsd.org/cgi/query-pr.cgi?pr=128590 From gavin at FreeBSD.org Wed Feb 25 02:49:33 2009 From: gavin at FreeBSD.org (gavin@FreeBSD.org) Date: Wed Feb 25 02:49:39 2009 Subject: usb/132066: [ukbd] Keyboard failure USB keyboard DELL 760 Message-ID: <200902251049.n1PAnWXo002536@freefall.freebsd.org> Synopsis: [ukbd] Keyboard failure USB keyboard DELL 760 State-Changed-From-To: feedback->open State-Changed-By: gavin State-Changed-When: Wed Feb 25 10:49:12 UTC 2009 State-Changed-Why: Feedback received, thanks! http://www.freebsd.org/cgi/query-pr.cgi?pr=132066 From gavin at FreeBSD.org Wed Feb 25 02:50:03 2009 From: gavin at FreeBSD.org (Gavin Atkinson) Date: Wed Feb 25 02:50:09 2009 Subject: usb/132066: [ukbd] Keyboard failure USB keyboard DELL 760 Message-ID: <200902251050.n1PAo3Vs002602@freefall.freebsd.org> The following reply was made to PR usb/132066; it has been noted by GNATS. From: Gavin Atkinson To: bug-followup@FreeBSD.org Cc: Subject: Re: usb/132066: [ukbd] Keyboard failure USB keyboard DELL 760 Date: Wed, 25 Feb 2009 10:49:35 +0000 -------- Forwarded Message -------- From: Judah Levine Date: Tue, 24 Feb 2009 10:53:40 -0700 Hello, >To submitter: Can you please give the output of "usbdevs -v"? Controller /dev/usb0: addr 1: full speed, self powered, config 1, UHCI root hub(0x0000), Intel(0x0000), rev 1.00 port 1 powered port 2 powered Controller /dev/usb1: addr 1: full speed, self powered, config 1, UHCI root hub(0x0000), Intel(0x0000), rev 1.00 port 1 powered port 2 powered Controller /dev/usb2: addr 1: full speed, self powered, config 1, UHCI root hub(0x0000), Intel(0x0000), rev 1.00 port 1 powered port 2 powered Controller /dev/usb3: addr 1: high speed, self powered, config 1, EHCI root hub(0x0000), Intel(0x0000), rev 1.00 port 1 powered port 2 powered port 3 powered port 4 powered port 5 powered port 6 powered Controller /dev/usb4: addr 1: full speed, self powered, config 1, UHCI root hub(0x0000), Intel(0x0000), rev 1.00 port 1 addr 2: low speed, power 70 mA, config 1, Dell USB Keyboard(0x2105), Dell(0x413c), rev 3.52 port 2 addr 3: low speed, power 100 mA, config 1, Optical USB Mouse(0xc016), Logitech(0x046d), rev 3.40 Controller /dev/usb5: addr 1: full speed, self powered, config 1, UHCI root hub(0x0000), Intel(0x0000), rev 1.00 port 1 powered port 2 powered Controller /dev/usb6: addr 1: full speed, self powered, config 1, UHCI root hub(0x0000), Intel(0x0000), rev 1.00 port 1 powered port 2 powered Controller /dev/usb7: addr 1: high speed, self powered, config 1, EHCI root hub(0x0000), Intel(0x0000), rev 1.00 port 1 powered port 2 powered port 3 powered port 4 powered port 5 powered port 6 powered >and supply the output of "dmesg |grep -A 2 -B 2 kbd" ioapic0 irqs 0-23 on motherboard lapic0: Forcing LINT1 to edge trigger kbd1 at kbdmux0 ath_hal: 0.9.17.2 (AR5210, AR5211, AR5212, RF5111, RF5112, RF2413, RF5413) acpi0: on motherboard -- pmtimer0 on isa0 orm0: at iomem 0xc0000-0xcc7ff,0xcc800-0xce7ff,0xce800-0xcffff on isa0 atkbdc0: at port 0x60,0x64 on isa0 atkbd0: irq 1 on atkbdc0 kbd0 at atkbd0 atkbd0: [GIANT-LOCKED] psm0: irq 12 on atkbdc0 psm0: [GIANT-LOCKED] psm0: model Generic PS/2 mouse, device ID 0 -- sio1: port may not be enabled vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 ukbd0: Dell Dell USB Keyboard, rev 1.10/3.52, addr 2, iclass 3/1 kbd2 at ukbd0 ums0: Logitech Optical USB Mouse, rev 2.00/3.40, addr 3, iclass 3/1 ums0: 3 buttons and Z dir. Judah Levine Time and Frequency Division NIST Boulder From eculp at encontacto.net Wed Feb 25 04:20:43 2009 From: eculp at encontacto.net (eculp) Date: Wed Feb 25 04:20:50 2009 Subject: Current - USB2 - cups and u[n]lpt devices. Message-ID: <20090225061037.10896uy7ft1kgu80@econet.encontacto.net> I just rebooted my laptop that I have today's USB2 hopefully with the latest USB compatibility, if I understood the GENERIC kernel correctly. I'm using i386 version, up to date as of this morning. Ports are completely up to date. all etc/dev* stuff is as it was with USB1. From the dmesg I get: +ugen0.2: at usbus0 +ulpt0: on usbus0 +ulpt0: using bi-directional mode +Symlink: ulpt0 -> usb0.2.1.16 +Symlink: unlpt0 -> usb0.2.1.17 With localhost:631 I see Unable to open device file "/dev/ulpt0": Operation not permitted. Probably because, there ain't none. Is there something else that I need to do that I didn't do before? This isn't critical. I probably print only a few pages a week but I do want it to work when something is critical. Thanks, ed P.S. Maybe this should be posted on another list rather than questions? _______________________________________________ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscribe@freebsd.org" From hselasky at c2i.net Wed Feb 25 04:38:52 2009 From: hselasky at c2i.net (Hans Petter Selasky) Date: Wed Feb 25 04:38:59 2009 Subject: Current - USB2 - cups and u[n]lpt devices. In-Reply-To: <20090225061037.10896uy7ft1kgu80@econet.encontacto.net> References: <20090225061037.10896uy7ft1kgu80@econet.encontacto.net> Message-ID: <200902251326.19416.hselasky@c2i.net> On Wednesday 25 February 2009, eculp wrote: > I just rebooted my laptop that I have today's USB2 hopefully with the > latest USB compatibility, if I understood the GENERIC kernel > correctly. I'm using i386 version, up to date as of this morning. > Ports are completely up to date. all etc/dev* stuff is as it was with > USB1. > > From the dmesg I get: > > +ugen0.2: at usbus0 > +ulpt0: on usbus0 > +ulpt0: using bi-directional mode > +Symlink: ulpt0 -> usb0.2.1.16 > +Symlink: unlpt0 -> usb0.2.1.17 > > With localhost:631 I see Unable to open device file "/dev/ulpt0": > Operation not permitted. Probably because, there ain't none. Is > there something else that I need to do that I didn't do before? > > This isn't critical. I probably print only a few pages a week but I > do want it to work when something is critical. > The devices are there, but invisible. Also check "usbconfig dump_access" that the ulpt port is reachable by cupsd. cat /dev/ulpt0 should work --HPS From thompsa at FreeBSD.org Wed Feb 25 07:24:23 2009 From: thompsa at FreeBSD.org (Andrew Thompson) Date: Wed Feb 25 07:24:28 2009 Subject: Current - USB2 - cups and u[n]lpt devices. In-Reply-To: <20090225061037.10896uy7ft1kgu80@econet.encontacto.net> References: <20090225061037.10896uy7ft1kgu80@econet.encontacto.net> Message-ID: <20090225152412.GA25211@citylink.fud.org.nz> On Wed, Feb 25, 2009 at 06:10:37AM -0600, eculp wrote: > I just rebooted my laptop that I have today's USB2 hopefully with the > latest USB compatibility, if I understood the GENERIC kernel correctly. > I'm using i386 version, up to date as of this morning. Ports are > completely up to date. all etc/dev* stuff is as it was with USB1. > > From the dmesg I get: > > +ugen0.2: at usbus0 > +ulpt0: on usbus0 > +ulpt0: using bi-directional mode > +Symlink: ulpt0 -> usb0.2.1.16 > +Symlink: unlpt0 -> usb0.2.1.17 > > With localhost:631 I see Unable to open device file "/dev/ulpt0": Operation > not permitted. Probably because, there ain't none. Is there something > else that I need to do that I didn't do before? > > This isn't critical. I probably print only a few pages a week but I do > want it to work when something is critical. Im working on a patch (from Rink) to create proper device nodes, should be ready shortly. Andrew From eculp at encontacto.net Wed Feb 25 07:43:13 2009 From: eculp at encontacto.net (eculp) Date: Wed Feb 25 07:43:20 2009 Subject: Current - USB2 - cups and u[n]lpt devices. In-Reply-To: <20090225152412.GA25211@citylink.fud.org.nz> References: <20090225061037.10896uy7ft1kgu80@econet.encontacto.net> <20090225152412.GA25211@citylink.fud.org.nz> Message-ID: <20090225094309.19235ixnswzkz5kw@econet.encontacto.net> Quoting Andrew Thompson : > On Wed, Feb 25, 2009 at 06:10:37AM -0600, eculp wrote: >> I just rebooted my laptop that I have today's USB2 hopefully with the >> latest USB compatibility, if I understood the GENERIC kernel correctly. >> I'm using i386 version, up to date as of this morning. Ports are >> completely up to date. all etc/dev* stuff is as it was with USB1. >> >> From the dmesg I get: >> >> +ugen0.2: at usbus0 >> +ulpt0: on usbus0 >> +ulpt0: using bi-directional mode >> +Symlink: ulpt0 -> usb0.2.1.16 >> +Symlink: unlpt0 -> usb0.2.1.17 >> >> With localhost:631 I see Unable to open device file "/dev/ulpt0": Operation >> not permitted. Probably because, there ain't none. Is there something >> else that I need to do that I didn't do before? >> >> This isn't critical. I probably print only a few pages a week but I do >> want it to work when something is critical. > > Im working on a patch (from Rink) to create proper device nodes, should > be ready shortly. Thanks, Andrew. I'm in no rush. I just wanted to see if I had missed something. Thanks again, ed > > > Andrew > From thompsa at FreeBSD.org Wed Feb 25 18:03:36 2009 From: thompsa at FreeBSD.org (Andrew Thompson) Date: Wed Feb 25 18:03:48 2009 Subject: USB devfs patch Message-ID: <20090226020330.GC25211@citylink.fud.org.nz> Hi, Below is a patch from Rink Springer to change the new USB stack to use devfs device nodes. I have tested this with a usb mouse and I am hoping people with other devices can test too, in particular scanners (sane app) and lpt ports. This also removes the custom permissions from usb and usbconfig. http://people.freebsd.org/~thompsa/usb-cdevs.diff cheers, Andrew From phk at phk.freebsd.dk Thu Feb 26 00:41:43 2009 From: phk at phk.freebsd.dk (Poul-Henning Kamp) Date: Thu Feb 26 00:41:51 2009 Subject: USB devfs patch In-Reply-To: Your message of "Wed, 25 Feb 2009 18:03:30 PST." <20090226020330.GC25211@citylink.fud.org.nz> Message-ID: <12757.1235636742@critter.freebsd.dk> In message <20090226020330.GC25211@citylink.fud.org.nz>, Andrew Thompson writes : >Hi, > > >Below is a patch from Rink Springer to change the new USB stack to use >devfs device nodes. I have tested this with a usb mouse and I am hoping >people with other devices can test too, in particular scanners (sane >app) and lpt ports. > >This also removes the custom permissions from usb and usbconfig. > >http://people.freebsd.org/~thompsa/usb-cdevs.diff I really like that this patch is mostly minus-lines. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. From ed at 80386.nl Thu Feb 26 00:45:31 2009 From: ed at 80386.nl (Ed Schouten) Date: Thu Feb 26 00:45:37 2009 Subject: USB devfs patch In-Reply-To: <20090226020330.GC25211@citylink.fud.org.nz> References: <20090226020330.GC25211@citylink.fud.org.nz> Message-ID: <20090226084528.GU19161@hoeg.nl> Hi Andrew, * Andrew Thompson wrote: > Below is a patch from Rink Springer to change the new USB stack to use > devfs device nodes. I have tested this with a usb mouse and I am hoping > people with other devices can test too, in particular scanners (sane > app) and lpt ports. I also mentioned this on IRC, but just to make sure it won't get lost. I really like the patch. I just tried it and it seems to work as advertised. What's your opinion on this patch? http://80386.nl/pub/usb-cdev.diff It turns the d_fdopen() function to a regular d_open(). I think we should only use d_fdopen() in cases where we really need access to the file descriptor (like ptmx). -- Ed Schouten WWW: http://80386.nl/ -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 195 bytes Desc: not available Url : http://lists.freebsd.org/pipermail/freebsd-usb/attachments/20090226/30a8dc26/attachment.pgp From rink at FreeBSD.org Thu Feb 26 00:55:34 2009 From: rink at FreeBSD.org (Rink Springer) Date: Thu Feb 26 00:55:58 2009 Subject: USB devfs patch In-Reply-To: <20090226020330.GC25211@citylink.fud.org.nz> References: <20090226020330.GC25211@citylink.fud.org.nz> Message-ID: <20090226083938.GB14479@rink.nu> Hi Andrew, On Wed, Feb 25, 2009 at 06:03:30PM -0800, Andrew Thompson wrote: > > Below is a patch from Rink Springer to change the new USB stack to use > devfs device nodes. I have tested this with a usb mouse and I am hoping > people with other devices can test too, in particular scanners (sane > app) and lpt ports. > > This also removes the custom permissions from usb and usbconfig. > > http://people.freebsd.org/~thompsa/usb-cdevs.diff I've mostly browsed it, but I think your modifications are correct. Thank you for taking care of this! Regards, -- Rink P.W. Springer - http://rink.nu "Chance favours the prepared mind" - Penn From rwatson at FreeBSD.org Thu Feb 26 01:37:41 2009 From: rwatson at FreeBSD.org (Robert Watson) Date: Thu Feb 26 01:37:47 2009 Subject: USB devfs patch In-Reply-To: <20090226020330.GC25211@citylink.fud.org.nz> References: <20090226020330.GC25211@citylink.fud.org.nz> Message-ID: On Wed, 25 Feb 2009, Andrew Thompson wrote: > Below is a patch from Rink Springer to change the new USB stack to use devfs > device nodes. I have tested this with a usb mouse and I am hoping people > with other devices can test too, in particular scanners (sane app) and lpt > ports. > > This also removes the custom permissions from usb and usbconfig. > > http://people.freebsd.org/~thompsa/usb-cdevs.diff This seems to address my concerns, including eliminating the new use if PRIV_ROOT that got added. Once this is in the tree I can remove PRIV_ROOT entirely, so with any luck we can get a new fine-grained privilege model done by 8.0. Robert N M Watson Computer Laboratory University of Cambridge From w8hdkim at gmail.com Thu Feb 26 06:40:00 2009 From: w8hdkim at gmail.com (Kim Culhan) Date: Thu Feb 26 06:40:07 2009 Subject: Novatel U727 not recognized In-Reply-To: <200902250800.00365.hselasky@c2i.net> References: <89dbfdc30902241338h2e56af93q5d8fb3905454ea36@mail.gmail.com> <200902250800.00365.hselasky@c2i.net> Message-ID: <89dbfdc30902260639q44372d37xf702b3e023ebb8a5@mail.gmail.com> On Wed, Feb 25, 2009 at 1:59 AM, Hans Petter Selasky wrote: > On Tuesday 24 February 2009, Kim Culhan wrote: >> On Tue, Feb 24, 2009 at 4:34 AM, Hans Petter Selasky > wrote: >> > On Tuesday 24 February 2009, Kim Culhan wrote: >> >> On Tue, Feb 24, 2009 at 3:05 AM, Hans Petter Selasky >> > >> > wrote: >> >> > On Monday 23 February 2009, Kim Culhan wrote: >> >> >> On Mon, Feb 23, 2009 at 3:56 PM, Hans Petter Selasky >> >> >> >> >> > >> >> > wrote: >> >> >> > On Monday 23 February 2009, Kim Culhan wrote: >> >> >> >> Running 8.0-CURRENT as of 2-22-09 >> >> >> >> >> >> >> >> The 3g0 device is a Novatel U727 EVDO wireless radio. >> >> >> >> >> >> >> >> If the machine boots with the device attached, dmesg reads: >> >> >> >> >> >> >> >> u3g0: on usbus2 >> >> >> >> >> >> >> >> Remove the device and this is logged: >> >> >> >> >> >> >> >> u3g0: at ushub2, port 2, addr 2 (disconnected) >> >> >> >> >> >> >> >> Reattach the device and there is this message: >> >> >> >> >> >> >> >> uhub_reattach_port:414: could not allocate new device! >> >> >> >> >> >> >> >> kernel config has: >> >> >> >> >> >> >> >> device ? usb2_serial_3g >> >> >> >> >> >> >> >> Any help is greatly appreciated >> >> >> > >> >> >> > Hi, >> >> >> > >> >> >> > Can you turn on USB HUB debugging: >> >> >> > >> >> >> > sysctl hw.usb2.uhub.debug=15 >> >> >> > sysctl hw.usb.uhub.debug=15 >> >> >> >> >> >> Sure here is dmesg with sysctl hw.usb2.uhub.debug=15 >> >> >> >> >> >> uhub_read_port_status:259: port 2, wPortStatus=0x0103, >> >> >> wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION >> >> >> usb2_transfer_power_ref:1470: Adding type 0 to power state >> >> >> usb2_transfer_power_ref:1483: needs power >> >> >> u3g_huawei_init:278: >> >> >> usb2_alloc_device:1618: Found Huawei auto-install disk! >> >> >> usb2_bus_port_set_device:1334: bus 0xc6733cf0 devices[2] = 0xc6bc6000 >> >> >> ugen2.2: at usbus2 >> >> >> ugen2.2: at usbus2 (disconnected) >> >> >> usb2_bus_port_set_device:1334: bus 0xc6733cf0 devices[2] = 0 >> >> >> uhub_reattach_port:414: could not allocate new device! >> >> >> usb2_needs_explore:1345: >> >> >> usb2_bus_powerd:1516: bus=0xc670bcf0 >> >> >> usb2_bus_powerd:1599: Recomputing power masks >> >> >> uhub_explore:522: udev=0xc6a93000 addr=1 >> >> >> >> >> >> With the old usb, this was returned: >> >> >> >> >> >> Feb 22 10:38:37 smallster kernel: ugen2.2: at >> >> >> usbus2 Feb 22 10:38:37 smallster kernel: umass0: > >> >> Inc. Novatel Wireless CDMA, class 0/0, rev 1.10/0.00, addr 2> on >> >> >> usbus2 Feb 22 10:38:37 smallster kernel: umass0: ?SCSI over >> >> >> Bulk-Only; quirks = 0x0000 Feb 22 10:38:38 smallster kernel: >> >> >> umass0:1:0:-1: Attached to scbus1 Feb 22 10:38:39 smallster kernel: >> >> >> (probe0:umass-sim0:0:0:0): TEST UNIT READY. CDB: 0 0 0 0 0 0 >> >> >> Feb 22 10:38:39 smallster kernel: (probe0:umass-sim0:0:0:0): CAM >> >> >> Status: SCSI Status Error >> >> >> Feb 22 10:38:39 smallster kernel: (probe0:umass-sim0:0:0:0): SCSI >> >> >> Status: Check Condition >> >> >> Feb 22 10:38:39 smallster kernel: (probe0:umass-sim0:0:0:0): NOT >> >> >> READY asc:3a,0 Feb 22 10:38:39 smallster kernel: >> >> >> (probe0:umass-sim0:0:0:0): Medium not present Feb 22 10:38:39 >> >> >> smallster kernel: >> >> >> (probe0:umass-sim0:0:0:0): Unretryable error Feb 22 10:38:39 >> >> >> smallster kernel: cd0 at umass-sim0 bus 0 target 0 lun 0 Feb 22 >> >> >> 10:38:39 smallster kernel: cd0: Removable >> >> >> CD-ROM SCSI-2 device Feb 22 10:38:39 smallster kernel: cd0: 1.000MB/s >> >> >> transfers >> >> >> Feb 22 10:38:39 smallster kernel: cd0: Attempt to query device size >> >> >> failed: NOT READY, Medium not present >> >> >> Feb 22 10:40:27 smallster kernel: g_vfs_done():cd0[READ(offset=65536, >> >> >> length=8192)]error = 5 >> >> >> Feb 22 10:43:39 smallster kernel: umass0: at ushub2, port 1, addr 2 >> >> >> (disconnected) >> >> >> Feb 22 10:43:39 smallster kernel: (cd0:umass-sim0:0:0:0): lost device >> >> >> Feb 22 10:43:39 smallster kernel: (cd0:umass-sim0:0:0:0): removing >> >> >> device entry Feb 22 10:43:39 smallster kernel: ugen2.2: > >> >> Wireless Inc.> at usbus2 (disconnected) >> >> >> >> >> >> The device initially attempts to simulate the presence of a cdrom. >> >> >> >> >> >> Maybe this is creating the problem for usb2. >> >> >> >> >> >> -kim >> >> > >> >> > Hi Kim, >> >> > >> >> > In the latter case you don't have the U3G driver loaded. The U3G >> >> > driver will detect the CD-ROM and send an eject or propritary command. >> >> > After some while the device should show up like a u3g0 device. The >> >> > error message you get is like it should be when CD-ROM detection is >> >> > enabled. >> >> AFAIK there is no seperate CD-ROM detection which can be enabled/disabled. >> >> The device does not show up as a u3g0 device unless the u3g module is >> loaded after the system is booted with _u3g commented out of the kernel >> config_ >> >> After boot: >> >> kldload u3g >> >> returns >> >> u3g0: on usbus2 >> u3g0: Found 4 ports. >> >> If I remove the usb device it reports: >> >> u3g0: at ushub2, port 2, addr 2 (disconnected) >> umass0: at ushub2, port 2, addr 2 (disconnected) >> (da0:umass-sim0:0:0:0): lost device >> (da0:umass-sim0:0:0:0): removing device entry >> ugen2.2: at usbus2 (disconnected) >> >> If I reattach the device it reports: >> >> u3g_huawei_init:278: >> usb2_alloc_device:1618: Found Huawei auto-install disk! >> ugen2.2: at usbus2 >> ugen2.2: at usbus2 (disconnected) >> uhub_reattach_port:414: could not allocate new device! >> > > If your device does not re-appear within 10 seconds, then try this: > > 1) Add a quirk: > > kldload usb_quirk > kldload usb2_quirk > > usbconfig add_dev_quirk_vplh vid pid 0 0xFFFF UQ_CFG_INDEX_0 > > Replace vid and pid by the info provided by "usbconfig -u 2 -a 2 > dump_device_desc". > > 2) Dump USB configuration: > > usbconfig -u 2 -a 2 dump_curr_config_desc running this on 8-CURRENT of Feb 25 2008 ~ 2100 UTC # usbconfig -u 2 -a 2 dump_device_desc returns No device match or lack of permissions. # usbconfig -u 2 -a 2 dump_curr_config_desc returns the same Also, at this point booting without u3g in the kernel then inserting the Novatel U727 device returns the usual output relating to the cd0 device: ugen2.2: at usbus2 umass0: on usbus2 umass0: SCSI over Bulk-Only; quirks = 0x0000 umass0:1:0:-1: Attached to scbus1 (probe0:umass-sim0:0:0:0): TEST UNIT READY. CDB: 0 0 0 0 0 0 [deleted] Then on loading the u3g module: kldload u3g Now returns nothing, no output to dmesg kldunload u3g returns a LOR and backtrace: lock order reversal: 1st 0xc0d66da0 kernel linker (kernel linker) @ kern/kern_linker.c:1059 2nd 0xc0d68804 sysctl lock (sysctl lock) @ kern/kern_sysctl.c:250 KDB: stack backtrace: db_trace_self_wrapper(c0c1af34,e9595ac8,c0891525,4,c0c16550,...) at db_trace_self_wrapper+0x26 kdb_backtrace(4,c0c16550,c6523740,c6521ad0,e9595b24,...) at kdb_backtrace+0x29 _witness_debugger(c0c1dc29,c0d68804,c0c18a34,c6521ad0,c0c18953,...) at _witness_debugger+0x25 witness_checkorder(c0d68804,9,c0c1894a,fa,0,...) at witness_checkorder+0x839 _sx_xlock(c0d68804,0,c0c1894a,fa,c7164b80,...) at _sx_xlock+0x85 sysctl_ctx_free(c7164bcc,c7164b80,e9595bac,c0879d35,c7164b80,...) at sysctl_ctx_free+0x30 device_sysctl_fini(c7164b80,0,c0c1d176,c6b23ac0,c6ae9800,...) at device_sysctl_fini+0x1a device_detach(c7164b80,40088,c70ebb80,1,c717215c,...) at device_detach+0x1f5 devclass_delete_driver(c66398c0,c7172170,c0c16366,109,0,...) at devclass_delete_driver+0x91 driver_module_handler(c70ebbc0,1,c717215c,109,0,...) at driver_module_handler+0xd5 module_unload(c70ebbc0,c0c148cf,273,270,c0837376,...) at module_unload+0x43 linker_file_unload(c716c800,0,c0c148cf,423,c716f000,...) at linker_file_unload+0x15e kern_kldunload(c6b7d6c0,3,0,e9595d2c,c0b55ca3,...) at kern_kldunload+0xd5 kldunloadf(c6b7d6c0,e9595cf8,8,c0c1ec53,c0cfc720,...) at kldunloadf+0x2b syscall(e9595d38) at syscall+0x2a3 Xint0x80_syscall() at Xint0x80_syscall+0x20 --- syscall (444, FreeBSD ELF32, kldunloadf), eip = 0x280ce6ab, esp = 0xbfbfe48c, ebp = 0xbfbfecd8 --- Hope this helps regards -kim From hselasky at c2i.net Thu Feb 26 06:47:47 2009 From: hselasky at c2i.net (Hans Petter Selasky) Date: Thu Feb 26 06:47:54 2009 Subject: Novatel U727 not recognized In-Reply-To: <89dbfdc30902260639q44372d37xf702b3e023ebb8a5@mail.gmail.com> References: <89dbfdc30902241338h2e56af93q5d8fb3905454ea36@mail.gmail.com> <200902250800.00365.hselasky@c2i.net> <89dbfdc30902260639q44372d37xf702b3e023ebb8a5@mail.gmail.com> Message-ID: <200902261550.10055.hselasky@c2i.net> On Thursday 26 February 2009, Kim Culhan wrote: Hi, You need to plug your device before running the commands below. And the -u and -a numbers must match those after ugen :-) --HPS > > 2) Dump USB configuration: > > > > usbconfig -u 2 -a 2 dump_curr_config_desc > > running this on 8-CURRENT of Feb 25 2008 ~ 2100 UTC > > # usbconfig -u 2 -a 2 dump_device_desc > > returns > > No device match or lack of permissions. > > # usbconfig -u 2 -a 2 dump_curr_config_desc > > returns the same > From w8hdkim at gmail.com Thu Feb 26 07:07:57 2009 From: w8hdkim at gmail.com (Kim Culhan) Date: Thu Feb 26 07:08:04 2009 Subject: Novatel U727 not recognized In-Reply-To: <200902250800.00365.hselasky@c2i.net> References: <89dbfdc30902241338h2e56af93q5d8fb3905454ea36@mail.gmail.com> <200902250800.00365.hselasky@c2i.net> Message-ID: <89dbfdc30902260707h36d4c7d4u988d1c490aae2243@mail.gmail.com> On Wed, Feb 25, 2009 at 1:59 AM, Hans Petter Selasky wrote: > On Tuesday 24 February 2009, Kim Culhan wrote: >> On Tue, Feb 24, 2009 at 4:34 AM, Hans Petter Selasky > wrote: >> > On Tuesday 24 February 2009, Kim Culhan wrote: >> >> On Tue, Feb 24, 2009 at 3:05 AM, Hans Petter Selasky >> > >> > wrote: >> >> > On Monday 23 February 2009, Kim Culhan wrote: >> >> >> On Mon, Feb 23, 2009 at 3:56 PM, Hans Petter Selasky >> >> >> >> >> > >> >> > wrote: >> >> >> > On Monday 23 February 2009, Kim Culhan wrote: >> >> >> >> Running 8.0-CURRENT as of 2-22-09 >> >> >> >> >> >> >> >> The 3g0 device is a Novatel U727 EVDO wireless radio. >> >> >> >> >> >> >> >> If the machine boots with the device attached, dmesg reads: >> >> >> >> >> >> >> >> u3g0: on usbus2 >> >> >> >> >> >> >> >> Remove the device and this is logged: >> >> >> >> >> >> >> >> u3g0: at ushub2, port 2, addr 2 (disconnected) >> >> >> >> >> >> >> >> Reattach the device and there is this message: >> >> >> >> >> >> >> >> uhub_reattach_port:414: could not allocate new device! >> >> >> >> >> >> >> >> kernel config has: >> >> >> >> >> >> >> >> device ? usb2_serial_3g >> >> >> >> >> >> >> >> Any help is greatly appreciated >> >> >> > >> >> >> > Hi, >> >> >> > >> >> >> > Can you turn on USB HUB debugging: >> >> >> > >> >> >> > sysctl hw.usb2.uhub.debug=15 >> >> >> > sysctl hw.usb.uhub.debug=15 >> >> >> >> >> >> Sure here is dmesg with sysctl hw.usb2.uhub.debug=15 >> >> >> >> >> >> uhub_read_port_status:259: port 2, wPortStatus=0x0103, >> >> >> wPortChange=0x0000, err=USB_ERR_NORMAL_COMPLETION >> >> >> usb2_transfer_power_ref:1470: Adding type 0 to power state >> >> >> usb2_transfer_power_ref:1483: needs power >> >> >> u3g_huawei_init:278: >> >> >> usb2_alloc_device:1618: Found Huawei auto-install disk! >> >> >> usb2_bus_port_set_device:1334: bus 0xc6733cf0 devices[2] = 0xc6bc6000 >> >> >> ugen2.2: at usbus2 >> >> >> ugen2.2: at usbus2 (disconnected) >> >> >> usb2_bus_port_set_device:1334: bus 0xc6733cf0 devices[2] = 0 >> >> >> uhub_reattach_port:414: could not allocate new device! >> >> >> usb2_needs_explore:1345: >> >> >> usb2_bus_powerd:1516: bus=0xc670bcf0 >> >> >> usb2_bus_powerd:1599: Recomputing power masks >> >> >> uhub_explore:522: udev=0xc6a93000 addr=1 >> >> >> >> >> >> With the old usb, this was returned: >> >> >> >> >> >> Feb 22 10:38:37 smallster kernel: ugen2.2: at >> >> >> usbus2 Feb 22 10:38:37 smallster kernel: umass0: > >> >> Inc. Novatel Wireless CDMA, class 0/0, rev 1.10/0.00, addr 2> on >> >> >> usbus2 Feb 22 10:38:37 smallster kernel: umass0: ?SCSI over >> >> >> Bulk-Only; quirks = 0x0000 Feb 22 10:38:38 smallster kernel: >> >> >> umass0:1:0:-1: Attached to scbus1 Feb 22 10:38:39 smallster kernel: >> >> >> (probe0:umass-sim0:0:0:0): TEST UNIT READY. CDB: 0 0 0 0 0 0 >> >> >> Feb 22 10:38:39 smallster kernel: (probe0:umass-sim0:0:0:0): CAM >> >> >> Status: SCSI Status Error >> >> >> Feb 22 10:38:39 smallster kernel: (probe0:umass-sim0:0:0:0): SCSI >> >> >> Status: Check Condition >> >> >> Feb 22 10:38:39 smallster kernel: (probe0:umass-sim0:0:0:0): NOT >> >> >> READY asc:3a,0 Feb 22 10:38:39 smallster kernel: >> >> >> (probe0:umass-sim0:0:0:0): Medium not present Feb 22 10:38:39 >> >> >> smallster kernel: >> >> >> (probe0:umass-sim0:0:0:0): Unretryable error Feb 22 10:38:39 >> >> >> smallster kernel: cd0 at umass-sim0 bus 0 target 0 lun 0 Feb 22 >> >> >> 10:38:39 smallster kernel: cd0: Removable >> >> >> CD-ROM SCSI-2 device Feb 22 10:38:39 smallster kernel: cd0: 1.000MB/s >> >> >> transfers >> >> >> Feb 22 10:38:39 smallster kernel: cd0: Attempt to query device size >> >> >> failed: NOT READY, Medium not present >> >> >> Feb 22 10:40:27 smallster kernel: g_vfs_done():cd0[READ(offset=65536, >> >> >> length=8192)]error = 5 >> >> >> Feb 22 10:43:39 smallster kernel: umass0: at ushub2, port 1, addr 2 >> >> >> (disconnected) >> >> >> Feb 22 10:43:39 smallster kernel: (cd0:umass-sim0:0:0:0): lost device >> >> >> Feb 22 10:43:39 smallster kernel: (cd0:umass-sim0:0:0:0): removing >> >> >> device entry Feb 22 10:43:39 smallster kernel: ugen2.2: > >> >> Wireless Inc.> at usbus2 (disconnected) >> >> >> >> >> >> The device initially attempts to simulate the presence of a cdrom. >> >> >> >> >> >> Maybe this is creating the problem for usb2. >> >> >> >> >> >> -kim >> >> > >> >> > Hi Kim, >> >> > >> >> > In the latter case you don't have the U3G driver loaded. The U3G >> >> > driver will detect the CD-ROM and send an eject or propritary command. >> >> > After some while the device should show up like a u3g0 device. The >> >> > error message you get is like it should be when CD-ROM detection is >> >> > enabled. >> >> AFAIK there is no seperate CD-ROM detection which can be enabled/disabled. >> >> The device does not show up as a u3g0 device unless the u3g module is >> loaded after the system is booted with _u3g commented out of the kernel >> config_ >> >> After boot: >> >> kldload u3g >> >> returns >> >> u3g0: on usbus2 >> u3g0: Found 4 ports. >> >> If I remove the usb device it reports: >> >> u3g0: at ushub2, port 2, addr 2 (disconnected) >> umass0: at ushub2, port 2, addr 2 (disconnected) >> (da0:umass-sim0:0:0:0): lost device >> (da0:umass-sim0:0:0:0): removing device entry >> ugen2.2: at usbus2 (disconnected) >> >> If I reattach the device it reports: >> >> u3g_huawei_init:278: >> usb2_alloc_device:1618: Found Huawei auto-install disk! >> ugen2.2: at usbus2 >> ugen2.2: at usbus2 (disconnected) >> uhub_reattach_port:414: could not allocate new device! >> > > If your device does not re-appear within 10 seconds, then try this: > > 1) Add a quirk: > > kldload usb_quirk > kldload usb2_quirk > > usbconfig add_dev_quirk_vplh vid pid 0 0xFFFF UQ_CFG_INDEX_0 > > Replace vid and pid by the info provided by "usbconfig -u 2 -a 2 > dump_device_desc". > > 2) Dump USB configuration: > > usbconfig -u 2 -a 2 dump_curr_config_desc Taking another pass at this, loading u3g after waiting a minute: # usbconfig -u 2 -a 2 dump_device_desc returns: ugen2.2: at usbus2, cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON bLength = 0x0012 bDescriptorType = 0x0001 bcdUSB = 0x0110 bDeviceClass = 0x0000 bDeviceSubClass = 0x0000 bDeviceProtocol = 0x0000 bMaxPacketSize0 = 0x0040 idVendor = 0x1410 idProduct = 0x5010 bcdDevice = 0x0000 iManufacturer = 0x0001 iProduct = 0x0002 iSerialNumber = 0x0004 <091050639170000> bNumConfigurations = 0x0001 Then we say: usbconfig add_dev_quirk_vplh 0x1410 0x5010 0 0xFFFF UQ_CFG_INDEX_0 and it returns: # usbconfig -u 2 -a 2 dump_curr_config_desc ugen2.2: at usbus2, cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON Configuration index 0 bLength = 0x0009 bDescriptorType = 0x0002 wTotalLength = 0x0083 bNumInterfaces = 0x0005 bConfigurationValue = 0x0001 iConfiguration = 0x0000 bmAttributes = 0x00a0 bMaxPower = 0x00fa Interface 0 bLength = 0x0009 bDescriptorType = 0x0004 bInterfaceNumber = 0x0000 bAlternateSetting = 0x0000 bNumEndpoints = 0x0003 bInterfaceClass = 0x00ff bInterfaceSubClass = 0x00ff bInterfaceProtocol = 0x00ff iInterface = 0x0003 Endpoint 0 bLength = 0x0007 bDescriptorType = 0x0005 bEndpointAddress = 0x0081 bmAttributes = 0x0003 wMaxPacketSize = 0x0010 bInterval = 0x0080 bRefresh = 0x0000 bSynchAddress = 0x0000 Endpoint 1 bLength = 0x0007 bDescriptorType = 0x0005 bEndpointAddress = 0x0082 bmAttributes = 0x0002 wMaxPacketSize = 0x0040 bInterval = 0x0000 bRefresh = 0x0000 bSynchAddress = 0x0000 Endpoint 2 bLength = 0x0007 bDescriptorType = 0x0005 bEndpointAddress = 0x0002 bmAttributes = 0x0002 wMaxPacketSize = 0x0040 bInterval = 0x0000 bRefresh = 0x0000 bSynchAddress = 0x0000 Interface 1 bLength = 0x0009 bDescriptorType = 0x0004 bInterfaceNumber = 0x0001 bAlternateSetting = 0x0000 bNumEndpoints = 0x0002 bInterfaceClass = 0x00ff bInterfaceSubClass = 0x00ff bInterfaceProtocol = 0x00ff iInterface = 0x0003 Endpoint 0 bLength = 0x0007 bDescriptorType = 0x0005 bEndpointAddress = 0x0084 bmAttributes = 0x0002 wMaxPacketSize = 0x0040 bInterval = 0x0000 bRefresh = 0x0000 bSynchAddress = 0x0000 Endpoint 1 bLength = 0x0007 bDescriptorType = 0x0005 bEndpointAddress = 0x0004 bmAttributes = 0x0002 wMaxPacketSize = 0x0040 bInterval = 0x0000 bRefresh = 0x0000 bSynchAddress = 0x0000 Interface 2 bLength = 0x0009 bDescriptorType = 0x0004 bInterfaceNumber = 0x0002 bAlternateSetting = 0x0000 bNumEndpoints = 0x0002 bInterfaceClass = 0x00ff bInterfaceSubClass = 0x00ff bInterfaceProtocol = 0x00ff iInterface = 0x0003 Endpoint 0 bLength = 0x0007 bDescriptorType = 0x0005 bEndpointAddress = 0x0089 bmAttributes = 0x0002 wMaxPacketSize = 0x0040 bInterval = 0x0000 bRefresh = 0x0000 bSynchAddress = 0x0000 Endpoint 1 bLength = 0x0007 bDescriptorType = 0x0005 bEndpointAddress = 0x0009 bmAttributes = 0x0002 wMaxPacketSize = 0x0040 bInterval = 0x0000 bRefresh = 0x0000 bSynchAddress = 0x0000 Interface 3 bLength = 0x0009 bDescriptorType = 0x0004 bInterfaceNumber = 0x0003 bAlternateSetting = 0x0000 bNumEndpoints = 0x0002 bInterfaceClass = 0x00ff bInterfaceSubClass = 0x00ff bInterfaceProtocol = 0x00ff iInterface = 0x0003 Endpoint 0 bLength = 0x0007 bDescriptorType = 0x0005 bEndpointAddress = 0x008a bmAttributes = 0x0002 wMaxPacketSize = 0x0040 bInterval = 0x0000 bRefresh = 0x0000 bSynchAddress = 0x0000 Endpoint 1 bLength = 0x0007 bDescriptorType = 0x0005 bEndpointAddress = 0x000a bmAttributes = 0x0002 wMaxPacketSize = 0x0040 bInterval = 0x0000 bRefresh = 0x0000 bSynchAddress = 0x0000 Interface 4 bLength = 0x0009 bDescriptorType = 0x0004 bInterfaceNumber = 0x0004 bAlternateSetting = 0x0000 bNumEndpoints = 0x0002 bInterfaceClass = 0x0008 bInterfaceSubClass = 0x0006 bInterfaceProtocol = 0x0050 iInterface = 0x0000 Endpoint 0 bLength = 0x0007 bDescriptorType = 0x0005 bEndpointAddress = 0x0085 bmAttributes = 0x0002 wMaxPacketSize = 0x0040 bInterval = 0x0000 bRefresh = 0x0000 bSynchAddress = 0x0000 Endpoint 1 bLength = 0x0007 bDescriptorType = 0x0005 bEndpointAddress = 0x0006 bmAttributes = 0x0002 wMaxPacketSize = 0x0040 bInterval = 0x0000 bRefresh = 0x0000 bSynchAddress = 0x0000 Hope _this_ helps :) -kim From hselasky at c2i.net Thu Feb 26 07:19:49 2009 From: hselasky at c2i.net (Hans Petter Selasky) Date: Thu Feb 26 07:19:55 2009 Subject: Novatel U727 not recognized In-Reply-To: <89dbfdc30902260707h36d4c7d4u988d1c490aae2243@mail.gmail.com> References: <89dbfdc30902241338h2e56af93q5d8fb3905454ea36@mail.gmail.com> <200902250800.00365.hselasky@c2i.net> <89dbfdc30902260707h36d4c7d4u988d1c490aae2243@mail.gmail.com> Message-ID: <200902261622.17677.hselasky@c2i.net> On Thursday 26 February 2009, Kim Culhan wrote: > On Wed, Feb 25, 2009 at 1:59 AM, Hans Petter Selasky Hi, I've checked the device tables and your device is listed in the U3G driver. Try: sysctl hw.usb2.u3g.debug=15 sysctl hw.usb.u3g.debug=15 kldload usb2_serial_3g kldload u3g Then re-plug your device, wait up to 30 seconds having it plugged and send dmesg. --HPS From w8hdkim at gmail.com Thu Feb 26 12:28:07 2009 From: w8hdkim at gmail.com (Kim Culhan) Date: Thu Feb 26 12:28:15 2009 Subject: Novatel U727 not recognized In-Reply-To: <200902261622.17677.hselasky@c2i.net> References: <89dbfdc30902241338h2e56af93q5d8fb3905454ea36@mail.gmail.com> <200902250800.00365.hselasky@c2i.net> <89dbfdc30902260707h36d4c7d4u988d1c490aae2243@mail.gmail.com> <200902261622.17677.hselasky@c2i.net> Message-ID: <89dbfdc30902261228k1e56e18dufb8caa46ef663747@mail.gmail.com> On Thu, Feb 26, 2009 at 10:22 AM, Hans Petter Selasky wrote: > On Thursday 26 February 2009, Kim Culhan wrote: >> On Wed, Feb 25, 2009 at 1:59 AM, Hans Petter Selasky > > Hi, > > I've checked the device tables and your device is listed in the U3G driver. > > Try: > > sysctl hw.usb2.u3g.debug=15 > sysctl hw.usb.u3g.debug=15 > > kldload usb2_serial_3g > kldload u3g > > Then re-plug your device, wait up to 30 seconds having it plugged and send > dmesg. Ok, in this order after a fresh reboot: # kldload usb2_serial_3g kldload: can't load usb2_serial_3g: No such file or directory # kldload u3g # sysctl hw.usb2.u3g.debug=15 hw.usb2.u3g.debug: 0 -> 15 [plug in the device and wait 1 minute] # dmesg Copyright (c) 1992-2009 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD is a registered trademark of The FreeBSD Foundation. FreeBSD 8.0-CURRENT #1: Wed Feb 25 17:25:14 EST 2009 kimc@smallster:/usr/src/sys/i386/compile/smallster_no3g WARNING: WITNESS option enabled, expect reduced performance. Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: Intel(R) Core(TM)2 CPU 6600 @ 2.40GHz (2400.10-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x6f6 Stepping = 6 Features=0xbfebfbff Features2=0xe3bd AMD Features=0x20100000 AMD Features2=0x1 TSC: P-state invariant Cores per package: 2 real memory = 3184525312 (3037 MB) avail memory = 3106189312 (2962 MB) ACPI APIC Table: FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC ID: 1 ioapic0 irqs 0-23 on motherboard kbd1 at kbdmux0 acpi0: on motherboard acpi0: [ITHREAD] acpi0: Power Button (fixed) Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000 acpi_timer0: <24-bit timer at 3.579545MHz> port 0x408-0x40b on acpi0 acpi_hpet0: iomem 0xfed00000-0xfed003ff on acpi0 Timecounter "HPET" frequency 14318180 Hz quality 900 pcib0: port 0xcf8-0xcff on acpi0 pci0: on pcib0 vgapci0: port 0xf1c0-0xf1c7 mem 0xff000000-0xff3fffff,0xd0000000-0xdfffffff irq 16 at device 2.0 on pci0 agp0: on vgapci0 agp0: detected 32764k stolen memory agp0: aperture size is 256M vgapci1: mem 0xff400000-0xff4fffff at device 2.1 on pci0 pci0: at device 3.0 (no driver attached) em0: port 0xf100-0xf11f mem 0xff600000-0xff61ffff,0xff624000-0xff624fff irq 20 at device 25.0 on pci0 em0: Using MSI interrupt em0: [FILTER] em0: Ethernet address: 00:1c:c0:7d:91:f5 uhci0: port 0xf0e0-0xf0ff irq 16 at device 26.0 on pci0 uhci0: [ITHREAD] uhci0: LegSup = 0x1f30 usbus0: on uhci0 uhci1: port 0xf0c0-0xf0df irq 21 at device 26.1 on pci0 uhci1: [ITHREAD] uhci1: LegSup = 0x0f30 usbus1: on uhci1 uhci2: port 0xf0a0-0xf0bf irq 18 at device 26.2 on pci0 uhci2: [ITHREAD] uhci2: LegSup = 0x0f30 usbus2: on uhci2 ehci0: mem 0xff625c00-0xff625fff irq 18 at device 26.7 on pci0 ehci0: [ITHREAD] usbus3: waiting for BIOS to give up control usbus3: timed out waiting for BIOS usbus3: EHCI version 1.0 usbus3: on ehci0 pci0: at device 27.0 (no driver attached) uhci3: port 0xf080-0xf09f irq 23 at device 29.0 on pci0 uhci3: [ITHREAD] uhci3: LegSup = 0x0f30 usbus4: on uhci3 uhci4: port 0xf060-0xf07f irq 19 at device 29.1 on pci0 uhci4: [ITHREAD] uhci4: LegSup = 0x0f30 usbus5: on uhci4 uhci5: port 0xf040-0xf05f irq 18 at device 29.2 on pci0 uhci5: [ITHREAD] uhci5: LegSup = 0x0f30 usbus6: on uhci5 ehci1: mem 0xff625800-0xff625bff irq 23 at device 29.7 on pci0 ehci1: [ITHREAD] usbus7: waiting for BIOS to give up control usbus7: timed out waiting for BIOS usbus7: EHCI version 1.0 usbus7: on ehci1 pcib1: at device 30.0 on pci0 pci1: on pcib1 fwohci0: mem 0xff500000-0xff500fff,0xff501000-0xff5010ff irq 22 at device 1.0 on pci1 fwohci0: [ITHREAD] fwohci0: OHCI version 1.0 (ROM=0) fwohci0: No. of Isochronous channels is 8. fwohci0: EUI64 00:90:27:00:02:29:cb:25 fwohci0: Phy 1394a available S400, 2 ports. fwohci0: Link S400, max_rec 2048 bytes. firewire0: on fwohci0 dcons_crom0: on firewire0 dcons_crom0: bus_addr 0xbdcd8000 fwe0: on firewire0 if_fwe0: Fake Ethernet address: 02:90:27:29:cb:25 fwe0: Ethernet address: 02:90:27:29:cb:25 fwip0: on firewire0 fwip0: Firewire address: 00:90:27:00:02:29:cb:25 @ 0xfffe00000000, S400, maxrec 2048 sbp0: on firewire0 fwohci0: Initiate bus reset fwohci0: fwohci_intr_core: BUS reset fwohci0: fwohci_intr_core: node_id=0x00000000, SelfID Count=1, CYCLEMASTER mode isab0: at device 31.0 on pci0 isa0: on isab0 atapci0: port 0xf1b0-0xf1b7,0xf1a0-0xf1a3,0xf190-0xf197,0xf180-0xf183,0xf020-0xf03f mem 0xff625000-0xff6257ff irq 19 at device 31.2 on pci0 atapci0: [ITHREAD] atapci0: AHCI Version 01.20 controller with 6 ports PM not supported ata2: on atapci0 ata2: [ITHREAD] ata3: on atapci0 ata3: [ITHREAD] ata4: on atapci0 ata4: [ITHREAD] ata5: on atapci0 ata5: [ITHREAD] ata6: on atapci0 ata6: [ITHREAD] ata7: on atapci0 ata7: [ITHREAD] pci0: at device 31.3 (no driver attached) atapci1: port 0xf170-0xf177,0xf160-0xf163,0xf150-0xf157,0xf140-0xf143,0xf130-0xf13f,0xf120-0xf12f irq 19 at device 31.5 on pci0 atapci1: [ITHREAD] ata8: on atapci1 ata8: [ITHREAD] ata9: on atapci1 ata9: [ITHREAD] acpi_button0: on acpi0 uart0: <16550 or compatible> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0 uart0: [FILTER] atrtc0: port 0x70-0x71 irq 8 on acpi0 cpu0: on acpi0 est0: on cpu0 est: CPU supports Enhanced Speedstep, but is not recognized. est: cpu_vendor GenuineIntel, msr 92a092a0600092a device_attach: est0 attach returned 6 p4tcc0: on cpu0 cpu1: on acpi0 est1: on cpu1 est: CPU supports Enhanced Speedstep, but is not recognized. est: cpu_vendor GenuineIntel, msr 92a092a0600092a device_attach: est1 attach returned 6 p4tcc1: on cpu1 pmtimer0 on isa0 sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x300> vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 ata0 at port 0x1f0-0x1f7,0x3f6 irq 14 on isa0 ata0: [ITHREAD] ata1 at port 0x170-0x177,0x376 irq 15 on isa0 ata1: [ITHREAD] atkbdc0: at port 0x60,0x64 on isa0 atkbd0: irq 1 on atkbdc0 kbd0 at atkbd0 atkbd0: [GIANT-LOCKED] atkbd0: [ITHREAD] ppc0: at port 0x378-0x37f irq 7 on isa0 ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode ppc0: FIFO with 16/16/8 bytes threshold ppc0: [ITHREAD] ppbus0: on ppc0 plip0: on ppbus0 plip0: [ITHREAD] lpt0: on ppbus0 lpt0: [ITHREAD] lpt0: Interrupt-driven port ppi0: on ppbus0 Timecounters tick every 1.000 msec firewire0: 1 nodes, maxhop <= 0 cable IRM irm(0) (me) firewire0: bus manager 0 usbus0: 12Mbps Full Speed USB v1.0 usbus1: 12Mbps Full Speed USB v1.0 usbus2: 12Mbps Full Speed USB v1.0 usbus3: 480Mbps High Speed USB v2.0 usbus4: 12Mbps Full Speed USB v1.0 usbus5: 12Mbps Full Speed USB v1.0 usbus6: 12Mbps Full Speed USB v1.0 usbus7: 480Mbps High Speed USB v2.0 ad4: 476940MB at ata2-master SATA300 ugen0.1: at usbus0 ushub0: on usbus0 ugen1.1: at usbus1 ushub1: on usbus1 ugen2.1: at usbus2 ushub2: on usbus2 ugen3.1: at usbus3 ushub3: on usbus3 ugen4.1: at usbus4 ushub4: on usbus4 ugen5.1: at usbus5 ushub5: on usbus5 ugen6.1: at usbus6 ushub6: on usbus6 ugen7.1: at usbus7 ushub7: on usbus7 GEOM: ad4: partition 3 does not start on a track boundary. GEOM: ad4: partition 3 does not end on a track boundary. GEOM: ad4: partition 2 does not start on a track boundary. GEOM: ad4: partition 2 does not end on a track boundary. GEOM: ad4: partition 1 does not start on a track boundary. GEOM: ad4: partition 1 does not end on a track boundary. acd0: DVDR at ata3-master SATA150 GEOM: ad4s3: geometry does not match label (255h,63s != 16h,63s). ushub0: 2 ports with 2 removable, self powered ushub1: 2 ports with 2 removable, self powered ushub2: 2 ports with 2 removable, self powered ushub4: 2 ports with 2 removable, self powered ushub5: 2 ports with 2 removable, self powered ushub6: 2 ports with 2 removable, self powered ushub3: 6 ports with 6 removable, self powered ushub7: 6 ports with 6 removable, self powered ugen0.2: at usbus0 ukbd0: on usbus0 kbd2 at ukbd0 ugen1.2: at usbus1 ums0: on usbus1 ums0: 3 buttons and [XYZ] coordinates Symlink: ums0 -> usb1.2.0.16 SMP: AP CPU #1 Launched! WARNING: WITNESS option enabled, expect reduced performance. Trying to mount root from ufs:/dev/ad4s3a module_register: module ushub/ums already exists! Module ushub/ums failed to register: 17 em0: link state changed to UP usb2_test_autoinstall:559: Eject CD command status: USB_ERR_NORMAL_COMPLETION usb2_alloc_device:1662: Found Huawei auto-install disk! ugen2.2: at usbus2 ugen2.2: at usbus2 (disconnected) uhub_reattach_port:414: could not allocate new device! -kim From hselasky at c2i.net Thu Feb 26 12:38:24 2009 From: hselasky at c2i.net (Hans Petter Selasky) Date: Thu Feb 26 12:38:30 2009 Subject: Novatel U727 not recognized In-Reply-To: <89dbfdc30902261228k1e56e18dufb8caa46ef663747@mail.gmail.com> References: <89dbfdc30902241338h2e56af93q5d8fb3905454ea36@mail.gmail.com> <200902261622.17677.hselasky@c2i.net> <89dbfdc30902261228k1e56e18dufb8caa46ef663747@mail.gmail.com> Message-ID: <200902262140.52560.hselasky@c2i.net> On Thursday 26 February 2009, Kim Culhan wrote: > On Thu, Feb 26, 2009 at 10:22 AM, Hans Petter Selasky wrote: > > On Thursday 26 February 2009, Kim Culhan wrote: > >> On Wed, Feb 25, 2009 at 1:59 AM, Hans Petter Selasky > usb2_test_autoinstall:559: Eject CD command status: > USB_ERR_NORMAL_COMPLETION usb2_alloc_device:1662: Found Huawei auto-install > disk! > ugen2.2: at usbus2 > ugen2.2: at usbus2 (disconnected) > uhub_reattach_port:414: could not allocate new device! And if you do like this: boot kernel without u3g loaded. When kernel is booted, and card is plugged in, load u3g. What does it output then? I think that there might be a USB port race. Could you try editing: /sys/dev/usb/usb_device.c Lookup: } else if (usb2_test_huawei_autoinst_p(udev, &uaa) == 0) { DPRINTFN(0, "Found Huawei auto-install disk!\n"); err = USB_ERR_STALLED; /* fake an error */ } Change it into: } else if (usb2_test_huawei_autoinst_p(udev, &uaa) == 0) { DPRINTFN(0, "Found Huawei auto-install disk!\n"); err = usb2_set_config_index(udev, USB_UNCONFIG_INDEX); err = 0; /* force success */ } And recompile kernel or only usb_core module. --HPS From w8hdkim at gmail.com Thu Feb 26 14:25:47 2009 From: w8hdkim at gmail.com (Kim Culhan) Date: Thu Feb 26 14:27:17 2009 Subject: Novatel U727 not recognized In-Reply-To: <200902262140.52560.hselasky@c2i.net> References: <89dbfdc30902241338h2e56af93q5d8fb3905454ea36@mail.gmail.com> <200902261622.17677.hselasky@c2i.net> <89dbfdc30902261228k1e56e18dufb8caa46ef663747@mail.gmail.com> <200902262140.52560.hselasky@c2i.net> Message-ID: <89dbfdc30902261425p7f933721sfdf47099fae2ef0a@mail.gmail.com> On Thu, Feb 26, 2009 at 3:40 PM, Hans Petter Selasky wrote: > On Thursday 26 February 2009, Kim Culhan wrote: >> On Thu, Feb 26, 2009 at 10:22 AM, Hans Petter Selasky > wrote: >> > On Thursday 26 February 2009, Kim Culhan wrote: >> >> On Wed, Feb 25, 2009 at 1:59 AM, Hans Petter Selasky > >> usb2_test_autoinstall:559: Eject CD command status: >> USB_ERR_NORMAL_COMPLETION usb2_alloc_device:1662: Found Huawei auto-install >> disk! >> ugen2.2: at usbus2 >> ugen2.2: at usbus2 (disconnected) >> uhub_reattach_port:414: could not allocate new device! > > And if you do like this: > > boot kernel without u3g loaded. > > When kernel is booted, and card is plugged in, load u3g. What does it output > then? There is no change now when loading the u3g module. u3g.c here is now svn commit: r188989 $FreeBSD: src/sys/dev/usb/serial/u3g.c,v 1.2 2009/02/24 05:35:48 thompsa Exp $ > I think that there might be a USB port race. Could you try editing: > > /sys/dev/usb/usb_device.c > > Lookup: > > ? ? ? ? ? ? ? ?} else if (usb2_test_huawei_autoinst_p(udev, &uaa) == 0) { > ? ? ? ? ? ? ? ? ? ? ? ?DPRINTFN(0, "Found Huawei auto-install disk!\n"); > ? ? ? ? ? ? ? ? ? ? ? ?err = USB_ERR_STALLED; ?/* fake an error */ > ? ? ? ? ? ? ? ?} > > Change it into: > > ? ? ? ? ? ? ? ?} else if (usb2_test_huawei_autoinst_p(udev, &uaa) == 0) { > ? ? ? ? ? ? ? ? ? ? ? ?DPRINTFN(0, "Found Huawei auto-install disk!\n"); > ? ? ? ? ? ? ? ?err = usb2_set_config_index(udev, USB_UNCONFIG_INDEX); > ? ? ? ? ? ? ? ?err = 0; /* force success */ > ? ? ? ? ? ? ? ?} > > And recompile kernel or only usb_core module. Changed as above, dmesg after attachment of device then loading u3g follows. ugen2.2: at usbus2 umass0: on usbus2 umass0: SCSI over Bulk-Only; quirks = 0x0000 umass0:1:0:-1: Attached to scbus1 (probe0:umass-sim0:0:0:0): TEST UNIT READY. CDB: 0 0 0 0 0 0 (probe0:umass-sim0:0:0:0): CAM Status: SCSI Status Error (probe0:umass-sim0:0:0:0): SCSI Status: Check Condition (probe0:umass-sim0:0:0:0): NOT READY asc:3a,0 (probe0:umass-sim0:0:0:0): Medium not present (probe0:umass-sim0:0:0:0): Unretryable error cd0 at umass-sim0 bus 0 target 0 lun 0 cd0: Removable CD-ROM SCSI-2 device cd0: 1.000MB/s transfers cd0: Attempt to query device size failed: NOT READY, Medium not present (cd0:umass-sim0:0:0:0): READ(10). CDB: 28 0 0 0 9 e0 0 0 1 0 (cd0:umass-sim0:0:0:0): CAM Status: SCSI Status Error (cd0:umass-sim0:0:0:0): SCSI Status: Check Condition (cd0:umass-sim0:0:0:0): UNIT ATTENTION asc:0,0 (cd0:umass-sim0:0:0:0): No additional sense information (cd0:umass-sim0:0:0:0): Retrying Command (per Sense Data) (cd0:umass-sim0:0:0:0): READ(10). CDB: 28 0 0 0 9 e0 0 0 1 0 (cd0:umass-sim0:0:0:0): CAM Status: SCSI Status Error (cd0:umass-sim0:0:0:0): SCSI Status: Check Condition (cd0:umass-sim0:0:0:0): UNIT ATTENTION asc:0,0 (cd0:umass-sim0:0:0:0): No additional sense information (cd0:umass-sim0:0:0:0): Retrying Command (per Sense Data) (cd0:umass-sim0:0:0:0): READ(10). CDB: 28 0 0 0 9 e0 0 0 1 0 (cd0:umass-sim0:0:0:0): CAM Status: SCSI Status Error (cd0:umass-sim0:0:0:0): SCSI Status: Check Condition (cd0:umass-sim0:0:0:0): UNIT ATTENTION asc:0,0 (cd0:umass-sim0:0:0:0): No additional sense information (cd0:umass-sim0:0:0:0): Retrying Command (per Sense Data) (cd0:umass-sim0:0:0:0): READ(10). CDB: 28 0 0 0 9 e0 0 0 1 0 (cd0:umass-sim0:0:0:0): CAM Status: SCSI Status Error (cd0:umass-sim0:0:0:0): SCSI Status: Check Condition (cd0:umass-sim0:0:0:0): UNIT ATTENTION asc:0,0 (cd0:umass-sim0:0:0:0): No additional sense information (cd0:umass-sim0:0:0:0): Retrying Command (per Sense Data) (cd0:umass-sim0:0:0:0): READ(10). CDB: 28 0 0 0 9 e0 0 0 1 0 (cd0:umass-sim0:0:0:0): CAM Status: SCSI Status Error (cd0:umass-sim0:0:0:0): SCSI Status: Check Condition (cd0:umass-sim0:0:0:0): UNIT ATTENTION asc:0,0 (cd0:umass-sim0:0:0:0): No additional sense information (cd0:umass-sim0:0:0:0): Retries Exhausted (cd0:umass-sim0:0:0:0): cddone: got error 0x6 back (cd0:umass-sim0:0:0:0): READ(10). CDB: 28 0 0 0 9 fc 0 0 1 0 (cd0:umass-sim0:0:0:0): CAM Status: SCSI Status Error (cd0:umass-sim0:0:0:0): SCSI Status: Check Condition (cd0:umass-sim0:0:0:0): UNIT ATTENTION asc:0,0 (cd0:umass-sim0:0:0:0): No additional sense information (cd0:umass-sim0:0:0:0): Retrying Command (per Sense Data) (cd0:umass-sim0:0:0:0): READ(10). CDB: 28 0 0 0 9 fc 0 0 1 0 (cd0:umass-sim0:0:0:0): CAM Status: SCSI Status Error (cd0:umass-sim0:0:0:0): SCSI Status: Check Condition (cd0:umass-sim0:0:0:0): UNIT ATTENTION asc:0,0 (cd0:umass-sim0:0:0:0): No additional sense information (cd0:umass-sim0:0:0:0): Retrying Command (per Sense Data) (cd0:umass-sim0:0:0:0): READ(10). CDB: 28 0 0 0 9 fc 0 0 1 0 (cd0:umass-sim0:0:0:0): CAM Status: SCSI Status Error (cd0:umass-sim0:0:0:0): SCSI Status: Check Condition (cd0:umass-sim0:0:0:0): UNIT ATTENTION asc:0,0 (cd0:umass-sim0:0:0:0): No additional sense information (cd0:umass-sim0:0:0:0): Retrying Command (per Sense Data) (cd0:umass-sim0:0:0:0): READ(10). CDB: 28 0 0 0 9 fc 0 0 1 0 (cd0:umass-sim0:0:0:0): CAM Status: SCSI Status Error (cd0:umass-sim0:0:0:0): SCSI Status: Check Condition (cd0:umass-sim0:0:0:0): UNIT ATTENTION asc:0,0 (cd0:umass-sim0:0:0:0): No additional sense information (cd0:umass-sim0:0:0:0): Retrying Command (per Sense Data) (cd0:umass-sim0:0:0:0): READ(10). CDB: 28 0 0 0 9 fc 0 0 1 0 (cd0:umass-sim0:0:0:0): CAM Status: SCSI Status Error (cd0:umass-sim0:0:0:0): SCSI Status: Check Condition (cd0:umass-sim0:0:0:0): UNIT ATTENTION asc:0,0 (cd0:umass-sim0:0:0:0): No additional sense information (cd0:umass-sim0:0:0:0): Retries Exhausted (cd0:umass-sim0:0:0:0): cddone: got error 0x6 back -kim From w8hdkim at gmail.com Thu Feb 26 14:36:52 2009 From: w8hdkim at gmail.com (Kim Culhan) Date: Thu Feb 26 14:36:58 2009 Subject: Novatel U727 not recognized In-Reply-To: <89dbfdc30902261425p7f933721sfdf47099fae2ef0a@mail.gmail.com> References: <89dbfdc30902241338h2e56af93q5d8fb3905454ea36@mail.gmail.com> <200902261622.17677.hselasky@c2i.net> <89dbfdc30902261228k1e56e18dufb8caa46ef663747@mail.gmail.com> <200902262140.52560.hselasky@c2i.net> <89dbfdc30902261425p7f933721sfdf47099fae2ef0a@mail.gmail.com> Message-ID: <89dbfdc30902261436o4ed73ab1l6877245c33c1cd7e@mail.gmail.com> On Thu, Feb 26, 2009 at 5:25 PM, Kim Culhan wrote: > On Thu, Feb 26, 2009 at 3:40 PM, Hans Petter Selasky wrote: >> On Thursday 26 February 2009, Kim Culhan wrote: >>> On Thu, Feb 26, 2009 at 10:22 AM, Hans Petter Selasky >> wrote: >>> > On Thursday 26 February 2009, Kim Culhan wrote: >>> >> On Wed, Feb 25, 2009 at 1:59 AM, Hans Petter Selasky >> >>> usb2_test_autoinstall:559: Eject CD command status: >>> USB_ERR_NORMAL_COMPLETION usb2_alloc_device:1662: Found Huawei auto-install >>> disk! >>> ugen2.2: at usbus2 >>> ugen2.2: at usbus2 (disconnected) >>> uhub_reattach_port:414: could not allocate new device! >> >> And if you do like this: >> >> boot kernel without u3g loaded. >> >> When kernel is booted, and card is plugged in, load u3g. What does it output >> then? > > There is no change now when loading the u3g module. > > u3g.c here is now svn commit: r188989 > > $FreeBSD: src/sys/dev/usb/serial/u3g.c,v 1.2 2009/02/24 05:35:48 thompsa Exp $ This info just in, the u3g0 device appeared several minutes after loading the u3g module. dmesg now has added: u3g0: on usbus2 u3g0: Found 4 ports. umass0: on usbus2 umass0: SCSI over Bulk-Only; quirks = 0x0000 umass0:1:0:-1: Attached to scbus1 (probe0:umass-sim0:0:0:0): TEST UNIT READY. CDB: 0 0 0 0 0 0 (probe0:umass-sim0:0:0:0): CAM Status: SCSI Status Error (probe0:umass-sim0:0:0:0): SCSI Status: Check Condition (probe0:umass-sim0:0:0:0): NOT READY asc:3a,0 (probe0:umass-sim0:0:0:0): Medium not present (probe0:umass-sim0:0:0:0): Unretryable error da0 at umass-sim0 bus 0 target 0 lun 0 da0: Removable Direct Access SCSI-2 device da0: 1.000MB/s transfers da0: Attempt to query device size failed: NOT READY, Medium not present -kim From mike at sentex.net Thu Feb 26 14:40:13 2009 From: mike at sentex.net (Mike Tancsa) Date: Thu Feb 26 14:40:19 2009 Subject: Novatel U727 not recognized In-Reply-To: <89dbfdc30902261436o4ed73ab1l6877245c33c1cd7e@mail.gmail.co m> References: <89dbfdc30902241338h2e56af93q5d8fb3905454ea36@mail.gmail.com> <200902261622.17677.hselasky@c2i.net> <89dbfdc30902261228k1e56e18dufb8caa46ef663747@mail.gmail.com> <200902262140.52560.hselasky@c2i.net> <89dbfdc30902261425p7f933721sfdf47099fae2ef0a@mail.gmail.com> <89dbfdc30902261436o4ed73ab1l6877245c33c1cd7e@mail.gmail.com> Message-ID: <200902262240.n1QMe9Vn006048@lava.sentex.ca> At 05:36 PM 2/26/2009, Kim Culhan wrote: >u3g0: on usbus2 >u3g0: Found 4 ports. >umass0: 1.10/0.00, addr 2> on usbus2 >umass0: SCSI over Bulk-Only; quirks = 0x0000 >umass0:1:0:-1: Attached to scbus1 >(probe0:umass-sim0:0:0:0): TEST UNIT READY. CDB: 0 0 0 0 0 0 >(probe0:umass-sim0:0:0:0): CAM Status: SCSI Status Error >(probe0:umass-sim0:0:0:0): SCSI Status: Check Condition >(probe0:umass-sim0:0:0:0): NOT READY asc:3a,0 >(probe0:umass-sim0:0:0:0): Medium not present >(probe0:umass-sim0:0:0:0): Unretryable error >da0 at umass-sim0 bus 0 target 0 lun 0 >da0: Removable Direct Access SCSI-2 device >da0: 1.000MB/s transfers >da0: Attempt to query device size failed: NOT READY, Medium not present If you do a camcontrol eject pass0 does /dev/cuaU* now show up ? I have a different Novatel unit where I have to do that to get it to work. umass0: on uhub0 vr0: vr_stop: Rx shutdown error vr0: Using force reset command. umass0: at uhub0 port 1 (addr 2) disconnected umass0: detached ucom0: on uhub0 ucom0: configured 2 serial ports (U0.%d) ---Mike >-kim >_______________________________________________ >freebsd-usb@freebsd.org mailing list >http://lists.freebsd.org/mailman/listinfo/freebsd-usb >To unsubscribe, send any mail to "freebsd-usb-unsubscribe@freebsd.org" From jlevine at boulder.nist.gov Thu Feb 26 16:46:23 2009 From: jlevine at boulder.nist.gov (Judah Levine) Date: Thu Feb 26 16:46:55 2009 Subject: usb/132066: [ukbd] Keyboard failure USB keyboard DELL 760 In-Reply-To: <200902251049.n1PAnWXo002536@freefall.freebsd.org> References: <200902251049.n1PAnWXo002536@freefall.freebsd.org> Message-ID: <7.0.0.16.2.20090226170327.023e68c0@boulder.nist.gov> Hello, I have done some additional playing around and I am writing to tell you my results: 1. All keys except for Caps lock and num lock seem to work properly. The combination Control-Z is recognized correctly. Also Shift + key gives the correct shift to upper case on both the letters and the numbers. 2. Holding down a letter key causes the letter to repeat as expected. 3. The numeric keypad and the arrow keys work as expected. 4. When you push caps lock, the corresponding light on the keyboard goes on for about 1 second, goes off, goes on again, goes off again and stays off. The num lock light does the same thing. 5. The system boots up with num lock on. If you push the num lock key, the corresponding light goes off and stays off. In both cases 4 and 5, the keyboard is disabled -- I cannot find any key combination that does anything. This includes control-alt-delete. The only fix is to push the power button. The same system works ok with Win XP. (The system is dual-boot). I have upgraded the BIOS firmware from A01 to A02. No change. Finally, it looks like Debian Linux has some problems with the same hardware. Are these troubles related? ------------------------------------------------------------------- At 03:49 AM 2/25/2009, gavin@FreeBSD.org wrote: >Synopsis: [ukbd] Keyboard failure USB keyboard DELL 760 > >State-Changed-From-To: feedback->open >State-Changed-By: gavin >State-Changed-When: Wed Feb 25 10:49:12 UTC 2009 >State-Changed-Why: >Feedback received, thanks! > >http://www.freebsd.org/cgi/query-pr.cgi?pr=132066 Judah Levine Time and Frequency Division NIST Boulder From thompsa at FreeBSD.org Thu Feb 26 17:14:40 2009 From: thompsa at FreeBSD.org (Andrew Thompson) Date: Thu Feb 26 17:14:46 2009 Subject: USB devfs patch In-Reply-To: <20090226020330.GC25211@citylink.fud.org.nz> References: <20090226020330.GC25211@citylink.fud.org.nz> Message-ID: <20090227011434.GA52500@citylink.fud.org.nz> On Wed, Feb 25, 2009 at 06:03:30PM -0800, Andrew Thompson wrote: > Hi, > > > Below is a patch from Rink Springer to change the new USB stack to use > devfs device nodes. I have tested this with a usb mouse and I am hoping > people with other devices can test too, in particular scanners (sane > app) and lpt ports. The patch has been updated thanks to feedback http://people.freebsd.org/~thompsa/usb-cdevs2.diff It now uses d_open instead of d_fdopen, uses an updated /dev layout, and of course bugfixes. I plan to commit tomorrow. Andrew From linimon at lonesome.com Thu Feb 26 17:59:15 2009 From: linimon at lonesome.com (Mark Linimon) Date: Thu Feb 26 17:59:22 2009 Subject: list of ports broken by USB switchover? Message-ID: <20090227014400.GA27047@lonesome.com> Does anyone have a list of these ports handy? I am trying to come up with a list of ports that have recently become broken in -CURRENT and I don't have any notes on these yet. mcl From hselasky at c2i.net Thu Feb 26 23:40:45 2009 From: hselasky at c2i.net (Hans Petter Selasky) Date: Thu Feb 26 23:41:08 2009 Subject: USB devfs patch In-Reply-To: <20090227011434.GA52500@citylink.fud.org.nz> References: <20090226020330.GC25211@citylink.fud.org.nz> <20090227011434.GA52500@citylink.fud.org.nz> Message-ID: <200902270843.12291.hselasky@c2i.net> Hi Andrew, > The patch has been updated thanks to feedback > http://people.freebsd.org/~thompsa/usb-cdevs2.diff I cannot see that you have looked at the 11 issues I repored on the last patch. Can you have a look at the following issues again: Here is a list of comments and bugs. The comments follow the diff from top to bottom. 1) There is a redundant setting of "is_uref = 1" ? - ? ? ? if (ploc->is_uref) { + ? ? ? if (cpd->is_uref) { ? ? ? ? ? ? ? ? /* ? ? ? ? ? ? ? ? ?* We are about to alter the bus-state. Apply the ? ? ? ? ? ? ? ? ?* required locks. ? ? ? ? ? ? ? ? ?*/ - ? ? ? ? ? ? ? sx_xlock(ploc->udev->default_sx + 1); + ? ? ? ? ? ? ? sx_xlock(cpd->udev->default_sx + 1); ? ? ? ? ? ? ? ? mtx_lock(&Giant); ? ? ? /* XXX */ + ? ? ? ? ? ? ? cpd->is_uref = 1; ? ? ? ? } 2) Should gid_t uid_t and mode_t be used? + ? ?uint8_t iface_index, uint32_t uid, uint32_t gid, uint16_t mode) 3) This comment should be: /* Now, create the device itself and an alias */ /* Now, create the device */ Because the alias is not needed - right. 4) Probably you can just remove the src_path stuff: + ? ? ? /* XXX no longer needed */ + ? ? ? strlcpy(ps->src_path, target, sizeof(ps->src_path)); + ? ? ? ps->src_len = strlen(ps->src_path); 5) There is no reason to use 32-bit int, except for fflags? uint16_t bus_index; uint8_t dev_index; uint8_t iface_index; uint8_t ep_addr; #define?EP_NO_ADDR 0xff /* instead of ep_addr = -1 */ ?/* + * Private per-device information. + */ +struct usb2_cdev_privdata { + ? ? ? struct usb2_bus ? ? ? ? *bus; + ? ? ? struct usb2_device ? ? ?*udev; + ? ? ? struct usb2_interface ? *iface; + ? ? ? struct usb2_fifo ? ? ? ?*rxfifo; + ? ? ? struct usb2_fifo ? ? ? ?*txfifo; + ? ? ? int ? ? ? ? ? ? ? ? ? ? bus_index; ? ? ?/* bus index */ + ? ? ? int ? ? ? ? ? ? ? ? ? ? dev_index; ? ? ?/* device index */ + ? ? ? int ? ? ? ? ? ? ? ? ? ? iface_index; ? ?/* interface index */ + ? ? ? int ? ? ? ? ? ? ? ? ? ? ep_addr; ? ? ? ?/* endpoint address */ + ? ? ? uint8_t ? ? ? ? ? ? ? ? fifo_index; ? ? /* FIFO index */ + ? ? ? uint8_t ? ? ? ? ? ? ? ? is_read; ? ? ? ?/* location has read access */ + ? ? ? uint8_t ? ? ? ? ? ? ? ? is_write; ? ? ? /* location has write access */ + ? ? ? uint8_t ? ? ? ? ? ? ? ? is_uref; ? ? ? ?/* USB refcount decr. needed */ + ? ? ? uint8_t ? ? ? ? ? ? ? ? is_usbfs; ? ? ? /* USB-FS is active */ + ? ? ? int ? ? ? ? ? ? ? ? ? ? fflags; +}; For usb2_fs_privdata probably you are justified. I would have used "unsigned int" for the fields that are unsigned. It has something to do with range checks in the code not checking for values less than zero. Like: if (fifo_index < max) ok; else failure; With int's we have to think more: if (fifo_index >= 0 && fifo_index < max) ok; else failure; 6) Some non-gcc compilers will complain unless you do 0-1 when the destination variable is unsigned. - ? ? ? usb2_free_pipe_data(udev, iface_index, 0 - 1); + ? ? ? usb2_free_pipe_data(udev, iface_index, -1); 7) Watch out!! Maybe using the word "in" and "out" is bad idea. If this means "read" and "write", then use "rd" and "wr", because in USB device mode the endpoint direction is exactly the opposide like in USB host mode: + ? ? ? ? ? ? ? /* Fill in the endpoint bitmasks */ + ? ? ? ? ? ? ? if (ed->bEndpointAddress & UE_DIR_IN) + ? ? ? ? ? ? ? ? ? ? ? iface->ep_in_mask |= + ? ? ? ? ? ? ? ? ? ? ? ? ? 1 << UE_GET_ADDR(ed->bEndpointAddress); + ? ? ? ? ? ? ? else + ? ? ? ? ? ? ? ? ? ? ? iface->ep_out_mask |= + ? ? ? ? ? ? ? ? ? ? ? ? ? 1 << UE_GET_ADDR(ed->bEndpointAddress); Use the the following macro for reference when computing if an endpoint is read or write! #define USB_GET_DATA_ISREAD(xfer) (((xfer)->flags_int.usb2_mode == \ ? ? ? ? USB_MODE_DEVICE) ? ((xfer->endpoint & UE_DIR_IN) ? 0 : 1) : \ ? ? ? ? ((xfer->endpoint & UE_DIR_IN) ? 1 : 0)) Change: + ? ? ? uint16_t ep_in_mask; ? ? ? ? ? ?/* bitmask of IN endpoints */ + ? ? ? uint16_t ep_out_mask; ? ? ? ? ? /* bitmask of OUT endpoints */ Into: + ? ? ? uint16_t ep_rx_mask; ? ? ? ? ? ?/* bitmask of RX endpoints */ + ? ? ? uint16_t ep_tx_mask; ? ? ? ? ? /* bitmask of TX endpoints */ 8) The following won't work?? Freeing the cdevs have to be done in multiple steps. Please keep the semantics of the "usb2_fifo_free_wrap" function. When setting the configuration we have a cdev handle on EP0. If that is closed during set_config we are recursivly killing our own handle! Therefore there are some extra checks so that at some points we only free non-EP0 handles, at some point only a specific interface and so on. + ? ? ? usb2_cdev_free(udev); ? ? ? ? usb2_fifo_free_wrap(udev, iface_index, 0); 9) Regarding the device nodes, how about organising into sub-folders? Before: + ? ? ? ? ? ? ? ? ? ? ? /* Now, create the device itself */ + ? ? ? ? ? ? ? ? ? ? ? snprintf(devname, sizeof(devname), USB_DEVICE_NAME + ? ? ? ? ? ? ? ? ? ? ? ? ? "%u.%u.%u.%u", pd->bus_index, pd->dev_index, + ? ? ? ? ? ? ? ? ? ? ? ? ? pd->iface_index, pd->ep_addr); + After: + ? ? ? ? ? ? ? ? ? ? ? /* Now, create the device itself */ + ? ? ? ? ? ? ? ? ? ? ? snprintf(devname, sizeof(devname), USB_DEVICE_NAME + ? ? ? ? ? ? ? ? ? ? ? ? ? "%u/%u/%u/%u", pd->bus_index, pd->dev_index, + ? ? ? ? ? ? ? ? ? ? ? ? ? pd->iface_index, pd->ep_addr); + You would also have to update libusb20. 10) Can you show me the implementation of the following function: + ? ? ? devfs_set_cdevpriv(cpd, usb2_close); --HPS From w8hdkim at gmail.com Fri Feb 27 04:32:33 2009 From: w8hdkim at gmail.com (Kim Culhan) Date: Fri Feb 27 04:32:39 2009 Subject: Novatel U727 not recognized In-Reply-To: <200902262240.n1QMe9Vn006048@lava.sentex.ca> References: <89dbfdc30902241338h2e56af93q5d8fb3905454ea36@mail.gmail.com> <200902261622.17677.hselasky@c2i.net> <89dbfdc30902261228k1e56e18dufb8caa46ef663747@mail.gmail.com> <200902262140.52560.hselasky@c2i.net> <89dbfdc30902261425p7f933721sfdf47099fae2ef0a@mail.gmail.com> <89dbfdc30902261436o4ed73ab1l6877245c33c1cd7e@mail.gmail.com> <200902262240.n1QMe9Vn006048@lava.sentex.ca> Message-ID: <89dbfdc30902270432x24487790p7b0f8ffe99d2bb@mail.gmail.com> On Thu, Feb 26, 2009 at 5:40 PM, Mike Tancsa wrote: > At 05:36 PM 2/26/2009, Kim Culhan wrote: > >> u3g0: on usbus2 >> u3g0: Found 4 ports. >> umass0: > 1.10/0.00, addr 2> on usbus2 >> umass0: ?SCSI over Bulk-Only; quirks = 0x0000 >> umass0:1:0:-1: Attached to scbus1 >> (probe0:umass-sim0:0:0:0): TEST UNIT READY. CDB: 0 0 0 0 0 0 >> (probe0:umass-sim0:0:0:0): CAM Status: SCSI Status Error >> (probe0:umass-sim0:0:0:0): SCSI Status: Check Condition >> (probe0:umass-sim0:0:0:0): NOT READY asc:3a,0 >> (probe0:umass-sim0:0:0:0): Medium not present >> (probe0:umass-sim0:0:0:0): Unretryable error >> da0 at umass-sim0 bus 0 target 0 lun 0 >> da0: Removable Direct Access SCSI-2 device >> da0: 1.000MB/s transfers >> da0: Attempt to query device size failed: NOT READY, Medium not present > > If you do a > camcontrol eject pass0 > > does /dev/cuaU* now show up ? > > I have a different Novatel unit where I have to do that to get it to work. > > umass0: 1.10/0.00, addr 2> on uhub0 > vr0: vr_stop: Rx shutdown error > vr0: Using force reset command. > umass0: at uhub0 port 1 (addr 2) disconnected > umass0: detached > ucom0: 1.10/0.00, addr 2> on uhub0 > ucom0: configured 2 serial ports (U0.%d) Yes, ejecting the 'cd0' appears to 'solve the problem' The order of events was: Boot the machine without u3g in the kernel Insert the device Issue the eject command: camcontrol eject pass0 the following appears in /dev cuaU0.0 cuaU0.0.init cuaU0.0.lock cuaU0.1 cuaU0.1.init cuaU0.1.lock cuaU0.2 cuaU0.2.init cuaU0.2.lock cuaU0.3 cuaU0.3.init cuaU0.3.lock Removing the device produces: u3g0: at ushub2, port 2, addr 2 (disconnected) umass0: at ushub2, port 2, addr 2 (disconnected) (da0:umass-sim0:0:0:0): lost device (da0:umass-sim0:0:0:0): removing device entry ugen2.2: at usbus2 (disconnected) Reinserting the device produces: ugen2.2: at usbus2 u3g0: on usbus2 u3g0: Found 4 ports. umass0: on usbus2 umass0: SCSI over Bulk-Only; quirks = 0x0000 umass0:1:0:-1: Attached to scbus1 (probe0:umass-sim0:0:0:0): TEST UNIT READY. CDB: 0 0 0 0 0 0 (probe0:umass-sim0:0:0:0): CAM Status: SCSI Status Error (probe0:umass-sim0:0:0:0): SCSI Status: Check Condition (probe0:umass-sim0:0:0:0): NOT READY asc:3a,0 (probe0:umass-sim0:0:0:0): Medium not present (probe0:umass-sim0:0:0:0): Unretryable error da0 at umass-sim0 bus 0 target 0 lun 0 da0: Removable Direct Access SCSI-2 device da0: 1.000MB/s transfers da0: Attempt to query device size failed: NOT READY, Medium not present remove it: u3g0: at ushub2, port 2, addr 2 (disconnected) umass0: at ushub2, port 2, addr 2 (disconnected) (da0:umass-sim0:0:0:0): lost device (da0:umass-sim0:0:0:0): removing device entry ugen2.2: at usbus2 (disconnected) re-reattach it: ugen2.2: at usbus2 u3g0: on usbus2 u3g0: Found 4 ports. umass0: on usbus2 umass0: SCSI over Bulk-Only; quirks = 0x0000 umass0:1:0:-1: Attached to scbus1 (probe0:umass-sim0:0:0:0): TEST UNIT READY. CDB: 0 0 0 0 0 0 (probe0:umass-sim0:0:0:0): CAM Status: SCSI Status Error (probe0:umass-sim0:0:0:0): SCSI Status: Check Condition (probe0:umass-sim0:0:0:0): NOT READY asc:3a,0 (probe0:umass-sim0:0:0:0): Medium not present (probe0:umass-sim0:0:0:0): Unretryable error da0 at umass-sim0 bus 0 target 0 lun 0 da0: Removable Direct Access SCSI-2 device da0: 1.000MB/s transfers da0: Attempt to query device size failed: NOT READY, Medium not present The U727 has a 'MicroSD' memory card slot which in this case has a 4gb card installed. If the SD card never worked i wouldn't mind a bit :) -kim From w8hdkim at gmail.com Fri Feb 27 04:38:28 2009 From: w8hdkim at gmail.com (Kim Culhan) Date: Fri Feb 27 04:38:35 2009 Subject: Novatel U727 not recognized -breakthrough and a correction Message-ID: <89dbfdc30902270438y793998c3yac87adb849c4f462@mail.gmail.com> On Fri, Feb 27, 2009 at 7:32 AM, Kim Culhan wrote: > On Thu, Feb 26, 2009 at 5:40 PM, Mike Tancsa wrote: >> At 05:36 PM 2/26/2009, Kim Culhan wrote: >> >>> u3g0: on usbus2 >>> u3g0: Found 4 ports. >>> umass0: >> 1.10/0.00, addr 2> on usbus2 >>> umass0: ?SCSI over Bulk-Only; quirks = 0x0000 >>> umass0:1:0:-1: Attached to scbus1 >>> (probe0:umass-sim0:0:0:0): TEST UNIT READY. CDB: 0 0 0 0 0 0 >>> (probe0:umass-sim0:0:0:0): CAM Status: SCSI Status Error >>> (probe0:umass-sim0:0:0:0): SCSI Status: Check Condition >>> (probe0:umass-sim0:0:0:0): NOT READY asc:3a,0 >>> (probe0:umass-sim0:0:0:0): Medium not present >>> (probe0:umass-sim0:0:0:0): Unretryable error >>> da0 at umass-sim0 bus 0 target 0 lun 0 >>> da0: Removable Direct Access SCSI-2 device >>> da0: 1.000MB/s transfers >>> da0: Attempt to query device size failed: NOT READY, Medium not present >> >> If you do a >> camcontrol eject pass0 >> >> does /dev/cuaU* now show up ? >> >> I have a different Novatel unit where I have to do that to get it to work. >> >> umass0: > 1.10/0.00, addr 2> on uhub0 >> vr0: vr_stop: Rx shutdown error >> vr0: Using force reset command. >> umass0: at uhub0 port 1 (addr 2) disconnected >> umass0: detached >> ucom0: > 1.10/0.00, addr 2> on uhub0 >> ucom0: configured 2 serial ports (U0.%d) > > Yes, ejecting the 'cd0' appears to 'solve the problem' > > The order of events was: > > Boot the machine without u3g in the kernel > Insert the device > Issue the eject command: camcontrol eject pass0 Correction: Left this out the first time: kldload u3g > the following appears in /dev > > cuaU0.0 > cuaU0.0.init > cuaU0.0.lock > cuaU0.1 > cuaU0.1.init > cuaU0.1.lock > cuaU0.2 > cuaU0.2.init > cuaU0.2.lock > cuaU0.3 > cuaU0.3.init > cuaU0.3.lock > > Removing the device produces: > > u3g0: at ushub2, port 2, addr 2 (disconnected) > umass0: at ushub2, port 2, addr 2 (disconnected) > (da0:umass-sim0:0:0:0): lost device > (da0:umass-sim0:0:0:0): removing device entry > ugen2.2: at usbus2 (disconnected) > > Reinserting the device produces: > > ugen2.2: at usbus2 > u3g0: on usbus2 > u3g0: Found 4 ports. > umass0: 1.10/0.00, addr 2> on usbus2 > umass0: ?SCSI over Bulk-Only; quirks = 0x0000 > umass0:1:0:-1: Attached to scbus1 > (probe0:umass-sim0:0:0:0): TEST UNIT READY. CDB: 0 0 0 0 0 0 > (probe0:umass-sim0:0:0:0): CAM Status: SCSI Status Error > (probe0:umass-sim0:0:0:0): SCSI Status: Check Condition > (probe0:umass-sim0:0:0:0): NOT READY asc:3a,0 > (probe0:umass-sim0:0:0:0): Medium not present > (probe0:umass-sim0:0:0:0): Unretryable error > da0 at umass-sim0 bus 0 target 0 lun 0 > da0: Removable Direct Access SCSI-2 device > da0: 1.000MB/s transfers > da0: Attempt to query device size failed: NOT READY, Medium not present > > remove it: > > u3g0: at ushub2, port 2, addr 2 (disconnected) > umass0: at ushub2, port 2, addr 2 (disconnected) > (da0:umass-sim0:0:0:0): lost device > (da0:umass-sim0:0:0:0): removing device entry > ugen2.2: at usbus2 (disconnected) > > re-reattach it: > > ugen2.2: at usbus2 > u3g0: on usbus2 > u3g0: Found 4 ports. > umass0: 1.10/0.00, addr 2> on usbus2 > umass0: ?SCSI over Bulk-Only; quirks = 0x0000 > umass0:1:0:-1: Attached to scbus1 > (probe0:umass-sim0:0:0:0): TEST UNIT READY. CDB: 0 0 0 0 0 0 > (probe0:umass-sim0:0:0:0): CAM Status: SCSI Status Error > (probe0:umass-sim0:0:0:0): SCSI Status: Check Condition > (probe0:umass-sim0:0:0:0): NOT READY asc:3a,0 > (probe0:umass-sim0:0:0:0): Medium not present > (probe0:umass-sim0:0:0:0): Unretryable error > da0 at umass-sim0 bus 0 target 0 lun 0 > da0: Removable Direct Access SCSI-2 device > da0: 1.000MB/s transfers > da0: Attempt to query device size failed: NOT READY, Medium not present > > The U727 has a 'MicroSD' memory card slot which in this case > has a 4gb card installed. > > If the SD card never worked i wouldn't mind a bit :) > > -kim > From thompsa at FreeBSD.org Fri Feb 27 05:43:13 2009 From: thompsa at FreeBSD.org (Andrew Thompson) Date: Fri Feb 27 05:43:19 2009 Subject: USB devfs patch In-Reply-To: <200902270843.12291.hselasky@c2i.net> References: <20090226020330.GC25211@citylink.fud.org.nz> <20090227011434.GA52500@citylink.fud.org.nz> <200902270843.12291.hselasky@c2i.net> Message-ID: <20090227134305.GA53460@citylink.fud.org.nz> On Fri, Feb 27, 2009 at 08:43:11AM +0100, Hans Petter Selasky wrote: > Hi Andrew, > > > The patch has been updated thanks to feedback > > http://people.freebsd.org/~thompsa/usb-cdevs2.diff > > I cannot see that you have looked at the 11 issues I repored on the last > patch. Can you have a look at the following issues again: Yes I have, 1, 2, 3, 6, 7 & 8 have all been fixed. For #10 use http://fxr.watson.org Andrew > Here is a list of comments and bugs. > The comments follow the diff from top to bottom. > > 1) There is a redundant setting of "is_uref = 1" ? > > - ? ? ? if (ploc->is_uref) { > + ? ? ? if (cpd->is_uref) { > ? ? ? ? ? ? ? ? /* > ? ? ? ? ? ? ? ? ?* We are about to alter the bus-state. Apply the > ? ? ? ? ? ? ? ? ?* required locks. > ? ? ? ? ? ? ? ? ?*/ > - ? ? ? ? ? ? ? sx_xlock(ploc->udev->default_sx + 1); > + ? ? ? ? ? ? ? sx_xlock(cpd->udev->default_sx + 1); > ? ? ? ? ? ? ? ? mtx_lock(&Giant); ? ? ? /* XXX */ > + ? ? ? ? ? ? ? cpd->is_uref = 1; > ? ? ? ? } > > > 2) Should gid_t uid_t and mode_t be used? > > + ? ?uint8_t iface_index, uint32_t uid, uint32_t gid, uint16_t mode) > > > 3) This comment should be: > > /* Now, create the device itself and an alias */ > > /* Now, create the device */ > > Because the alias is not needed - right. > > > 4) Probably you can just remove the src_path stuff: > > + ? ? ? /* XXX no longer needed */ > + ? ? ? strlcpy(ps->src_path, target, sizeof(ps->src_path)); > + ? ? ? ps->src_len = strlen(ps->src_path); > > 5) There is no reason to use 32-bit int, except for fflags? > > uint16_t bus_index; > uint8_t dev_index; > uint8_t iface_index; > uint8_t ep_addr; > #define?EP_NO_ADDR 0xff /* instead of ep_addr = -1 */ > > ?/* > + * Private per-device information. > + */ > +struct usb2_cdev_privdata { > + ? ? ? struct usb2_bus ? ? ? ? *bus; > + ? ? ? struct usb2_device ? ? ?*udev; > + ? ? ? struct usb2_interface ? *iface; > + ? ? ? struct usb2_fifo ? ? ? ?*rxfifo; > + ? ? ? struct usb2_fifo ? ? ? ?*txfifo; > + ? ? ? int ? ? ? ? ? ? ? ? ? ? bus_index; ? ? ?/* bus index */ > + ? ? ? int ? ? ? ? ? ? ? ? ? ? dev_index; ? ? ?/* device index */ > + ? ? ? int ? ? ? ? ? ? ? ? ? ? iface_index; ? ?/* interface index */ > + ? ? ? int ? ? ? ? ? ? ? ? ? ? ep_addr; ? ? ? ?/* endpoint address */ > + ? ? ? uint8_t ? ? ? ? ? ? ? ? fifo_index; ? ? /* FIFO index */ > + ? ? ? uint8_t ? ? ? ? ? ? ? ? is_read; ? ? ? ?/* location has read access */ > + ? ? ? uint8_t ? ? ? ? ? ? ? ? is_write; ? ? ? /* location has write access > */ > + ? ? ? uint8_t ? ? ? ? ? ? ? ? is_uref; ? ? ? ?/* USB refcount decr. needed > */ > + ? ? ? uint8_t ? ? ? ? ? ? ? ? is_usbfs; ? ? ? /* USB-FS is active */ > + ? ? ? int ? ? ? ? ? ? ? ? ? ? fflags; > +}; > > For usb2_fs_privdata probably you are justified. I would have used > "unsigned int" for the fields that are unsigned. It has something to do with > range checks in the code not checking for values less than zero. Like: > > if (fifo_index < max) > ok; > else > failure; > > With int's we have to think more: > > if (fifo_index >= 0 && fifo_index < max) > ok; > else > failure; > > 6) Some non-gcc compilers will complain unless you do 0-1 when the > destination variable is unsigned. > > - ? ? ? usb2_free_pipe_data(udev, iface_index, 0 - 1); > + ? ? ? usb2_free_pipe_data(udev, iface_index, -1); > > > 7) Watch out!! Maybe using the word "in" and "out" is bad idea. If > this means "read" and "write", then use "rd" and "wr", because in USB > device mode the endpoint direction is exactly the opposide like in USB > host mode: > > + ? ? ? ? ? ? ? /* Fill in the endpoint bitmasks */ > + ? ? ? ? ? ? ? if (ed->bEndpointAddress & UE_DIR_IN) > + ? ? ? ? ? ? ? ? ? ? ? iface->ep_in_mask |= > + ? ? ? ? ? ? ? ? ? ? ? ? ? 1 << UE_GET_ADDR(ed->bEndpointAddress); > + ? ? ? ? ? ? ? else > + ? ? ? ? ? ? ? ? ? ? ? iface->ep_out_mask |= > + ? ? ? ? ? ? ? ? ? ? ? ? ? 1 << UE_GET_ADDR(ed->bEndpointAddress); > > Use the the following macro for reference when computing if an > endpoint is read or write! > > #define USB_GET_DATA_ISREAD(xfer) (((xfer)->flags_int.usb2_mode == \ > ? ? ? ? USB_MODE_DEVICE) ? ((xfer->endpoint & UE_DIR_IN) ? 0 : 1) : \ > ? ? ? ? ((xfer->endpoint & UE_DIR_IN) ? 1 : 0)) > > Change: > > + ? ? ? uint16_t ep_in_mask; ? ? ? ? ? ?/* bitmask of IN endpoints */ > + ? ? ? uint16_t ep_out_mask; ? ? ? ? ? /* bitmask of OUT endpoints */ > > Into: > > + ? ? ? uint16_t ep_rx_mask; ? ? ? ? ? ?/* bitmask of RX endpoints */ > + ? ? ? uint16_t ep_tx_mask; ? ? ? ? ? /* bitmask of TX endpoints */ > > > 8) The following won't work?? Freeing the cdevs have to be done in multiple > steps. Please keep the semantics of the "usb2_fifo_free_wrap" function. > > When setting the configuration we have a cdev handle on EP0. If that > is closed during set_config we are recursivly killing our own handle! > Therefore there are some extra checks so that at some points we only > free non-EP0 handles, at some point only a specific interface and so > on. > > + ? ? ? usb2_cdev_free(udev); > ? ? ? ? usb2_fifo_free_wrap(udev, iface_index, 0); > > 9) Regarding the device nodes, how about organising into sub-folders? > > Before: > > + ? ? ? ? ? ? ? ? ? ? ? /* Now, create the device itself */ > + ? ? ? ? ? ? ? ? ? ? ? snprintf(devname, sizeof(devname), USB_DEVICE_NAME > + ? ? ? ? ? ? ? ? ? ? ? ? ? "%u.%u.%u.%u", pd->bus_index, pd->dev_index, > + ? ? ? ? ? ? ? ? ? ? ? ? ? pd->iface_index, pd->ep_addr); > + > > After: > > + ? ? ? ? ? ? ? ? ? ? ? /* Now, create the device itself */ > + ? ? ? ? ? ? ? ? ? ? ? snprintf(devname, sizeof(devname), USB_DEVICE_NAME > + ? ? ? ? ? ? ? ? ? ? ? ? ? "%u/%u/%u/%u", pd->bus_index, pd->dev_index, > + ? ? ? ? ? ? ? ? ? ? ? ? ? pd->iface_index, pd->ep_addr); > + > > You would also have to update libusb20. > > 10) Can you show me the implementation of the following function: > > + ? ? ? devfs_set_cdevpriv(cpd, usb2_close); > > --HPS From eculp at encontacto.net Sat Feb 28 09:55:12 2009 From: eculp at encontacto.net (eculp) Date: Sat Feb 28 09:55:19 2009 Subject: Current - USB2 - cups and u[n]lpt devices. In-Reply-To: <200902251326.19416.hselasky@c2i.net> References: <20090225061037.10896uy7ft1kgu80@econet.encontacto.net> <200902251326.19416.hselasky@c2i.net> Message-ID: <20090228115508.81775n96b4f851gk@econet.encontacto.net> Quoting Hans Petter Selasky : > On Wednesday 25 February 2009, eculp wrote: >> I just rebooted my laptop that I have today's USB2 hopefully with the >> latest USB compatibility, if I understood the GENERIC kernel >> correctly. I'm using i386 version, up to date as of this morning. >> Ports are completely up to date. all etc/dev* stuff is as it was with >> USB1. >> >> From the dmesg I get: >> >> +ugen0.2: at usbus0 >> +ulpt0: on usbus0 >> +ulpt0: using bi-directional mode >> +Symlink: ulpt0 -> usb0.2.1.16 >> +Symlink: unlpt0 -> usb0.2.1.17 >> >> With localhost:631 I see Unable to open device file "/dev/ulpt0": >> Operation not permitted. Probably because, there ain't none. Is >> there something else that I need to do that I didn't do before? >> >> This isn't critical. I probably print only a few pages a week but I >> do want it to work when something is critical. >> > The devices are there, but invisible. > > Also check "usbconfig dump_access" that the ulpt port is reachable by cupsd. > I think not. # usbconfig dump_access Global Access: root:operator 0660 ugen0.1: at usbus0, cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON Device Access: Interface 0 Access: ugen1.1: at usbus1, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=ON Device Access: Interface 0 Access: ugen2.1: at usbus2, cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON Device Access: Interface 0 Access: ugen3.1: at usbus3, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=ON Device Access: Interface 0 Access: ugen0.2: at usbus0, cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON Device Access: Interface 0 Access: Interface 1 Access: root:operator 0644 ugen1.2: at usbus1, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=ON Device Access: Interface 0 Access: Interface 1 Access: > cat /dev/ulpt0 # cat /dev/ulpt0 ed.local.net.mx > > should work What confuses me is that with dmesg or disconnecting and reconnecting I see: Feb 28 11:50:35 ed kernel: ulpt0: at ushub0, port 2, addr 2 (disconnected) Feb 28 11:50:35 ed kernel: ugen0.2: at usbus0 (disconnected) Feb 28 11:50:39 ed kernel: ugen0.2: at usbus0 Feb 28 11:50:39 ed kernel: ulpt0: on usbus0 Feb 28 11:50:39 ed kernel: ulpt0: using bi-directional mode Feb 28 11:50:39 ed kernel: Symlink: ulpt0 -> usb0.2.1.16 Feb 28 11:50:39 ed kernel: Symlink: unlpt0 -> usb0.2.1.17 But cups still says: Unable to open device file "/dev/ulpt0": Operation not permitted" and there are no lpt devices in /dev or subdirectories. Any additional suggestins apreciated. ed > > --HPS > From eculp at encontacto.net Sat Feb 28 09:57:36 2009 From: eculp at encontacto.net (eculp) Date: Sat Feb 28 09:57:42 2009 Subject: Current - USB2 - cups and u[n]lpt devices. In-Reply-To: <20090225152412.GA25211@citylink.fud.org.nz> References: <20090225061037.10896uy7ft1kgu80@econet.encontacto.net> <20090225152412.GA25211@citylink.fud.org.nz> Message-ID: <20090228115733.1493146fclj807pc@econet.encontacto.net> Quoting Andrew Thompson : > On Wed, Feb 25, 2009 at 06:10:37AM -0600, eculp wrote: >> I just rebooted my laptop that I have today's USB2 hopefully with the >> latest USB compatibility, if I understood the GENERIC kernel correctly. >> I'm using i386 version, up to date as of this morning. Ports are >> completely up to date. all etc/dev* stuff is as it was with USB1. >> >> From the dmesg I get: >> >> +ugen0.2: at usbus0 >> +ulpt0: on usbus0 >> +ulpt0: using bi-directional mode >> +Symlink: ulpt0 -> usb0.2.1.16 >> +Symlink: unlpt0 -> usb0.2.1.17 >> >> With localhost:631 I see Unable to open device file "/dev/ulpt0": Operation >> not permitted. Probably because, there ain't none. Is there something >> else that I need to do that I didn't do before? >> >> This isn't critical. I probably print only a few pages a week but I do >> want it to work when something is critical. > > Im working on a patch (from Rink) to create proper device nodes, should > be ready shortly. I'm just curious. Has this patch been committed yet? Thanks, ed > > > Andrew > From hselasky at c2i.net Sat Feb 28 09:59:00 2009 From: hselasky at c2i.net (Hans Petter Selasky) Date: Sat Feb 28 09:59:08 2009 Subject: Current - USB2 - cups and u[n]lpt devices. In-Reply-To: <20090228115508.81775n96b4f851gk@econet.encontacto.net> References: <20090225061037.10896uy7ft1kgu80@econet.encontacto.net> <200902251326.19416.hselasky@c2i.net> <20090228115508.81775n96b4f851gk@econet.encontacto.net> Message-ID: <200902281901.25043.hselasky@c2i.net> On Saturday 28 February 2009, eculp wrote: > Quoting Hans Petter Selasky : > > On Wednesday 25 February 2009, eculp wrote: > >> I just rebooted my laptop that I have today's USB2 hopefully with the > >> latest USB compatibility, if I understood the GENERIC kernel > >> correctly. I'm using i386 version, up to date as of this morning. > >> Ports are completely up to date. all etc/dev* stuff is as it was with > >> USB1. > >> > >> From the dmesg I get: > >> > >> +ugen0.2: at usbus0 > >> +ulpt0: on usbus0 > >> +ulpt0: using bi-directional mode > >> +Symlink: ulpt0 -> usb0.2.1.16 > >> +Symlink: unlpt0 -> usb0.2.1.17 > >> > >> With localhost:631 I see Unable to open device file "/dev/ulpt0": > >> Operation not permitted. Probably because, there ain't none. Is > >> there something else that I need to do that I didn't do before? > >> > >> This isn't critical. I probably print only a few pages a week but I > >> do want it to work when something is critical. > > > > The devices are there, but invisible. > > > > Also check "usbconfig dump_access" that the ulpt port is reachable by > > cupsd. > > I think not. > > # usbconfig dump_access > Global Access: root:operator 0660 > ugen0.1: at usbus0, cfg=0 md=HOST spd=FULL > (12Mbps) pwr=ON > > Device Access: > Interface 0 Access: > > ugen1.1: at usbus1, cfg=0 md=HOST spd=HIGH > (480Mbps) pwr=ON > > Device Access: > Interface 0 Access: > > ugen2.1: at usbus2, cfg=0 md=HOST spd=FULL > (12Mbps) pwr=ON > > Device Access: > Interface 0 Access: > > ugen3.1: at usbus3, cfg=0 md=HOST spd=HIGH > (480Mbps) pwr=ON > > Device Access: > Interface 0 Access: > > ugen0.2: at usbus0, cfg=0 md=HOST > spd=FULL (12Mbps) pwr=ON > > Device Access: > Interface 0 Access: > Interface 1 Access: root:operator 0644 > > ugen1.2: at usbus1, cfg=0 md=HOST > spd=HIGH (480Mbps) pwr=ON > > Device Access: > Interface 0 Access: > Interface 1 Access: > > > cat /dev/ulpt0 > > # cat /dev/ulpt0 > ed.local.net.mx > > > should work > > What confuses me is that with dmesg or disconnecting and reconnecting I > see: > > Feb 28 11:50:35 ed kernel: ulpt0: at ushub0, port 2, addr 2 (disconnected) > Feb 28 11:50:35 ed kernel: ugen0.2: at usbus0 (disconnected) > Feb 28 11:50:39 ed kernel: ugen0.2: at usbus0 > Feb 28 11:50:39 ed kernel: ulpt0: on usbus0 > Feb 28 11:50:39 ed kernel: ulpt0: using bi-directional mode > Feb 28 11:50:39 ed kernel: Symlink: ulpt0 -> usb0.2.1.16 > Feb 28 11:50:39 ed kernel: Symlink: unlpt0 -> usb0.2.1.17 > > But cups still says: > > Unable to open device file "/dev/ulpt0": Operation not permitted" > > and there are no lpt devices in /dev or subdirectories. > > Any additional suggestins apreciated. > Try to cvsup. Then you will get a device which you can chmod . --HPS From thompsa at FreeBSD.org Sat Feb 28 10:01:01 2009 From: thompsa at FreeBSD.org (Andrew Thompson) Date: Sat Feb 28 10:01:09 2009 Subject: Current - USB2 - cups and u[n]lpt devices. In-Reply-To: <20090228115733.1493146fclj807pc@econet.encontacto.net> References: <20090225061037.10896uy7ft1kgu80@econet.encontacto.net> <20090225152412.GA25211@citylink.fud.org.nz> <20090228115733.1493146fclj807pc@econet.encontacto.net> Message-ID: <20090228180054.GA86623@citylink.fud.org.nz> On Sat, Feb 28, 2009 at 11:57:33AM -0600, eculp wrote: > Quoting Andrew Thompson : > >> On Wed, Feb 25, 2009 at 06:10:37AM -0600, eculp wrote: >>> I just rebooted my laptop that I have today's USB2 hopefully with the >>> latest USB compatibility, if I understood the GENERIC kernel correctly. >>> I'm using i386 version, up to date as of this morning. Ports are >>> completely up to date. all etc/dev* stuff is as it was with USB1. >>> >>> From the dmesg I get: >>> >>> +ugen0.2: at usbus0 >>> +ulpt0: on usbus0 >>> +ulpt0: using bi-directional mode >>> +Symlink: ulpt0 -> usb0.2.1.16 >>> +Symlink: unlpt0 -> usb0.2.1.17 >>> >>> With localhost:631 I see Unable to open device file "/dev/ulpt0": Operation >>> not permitted. Probably because, there ain't none. Is there something >>> else that I need to do that I didn't do before? >>> >>> This isn't critical. I probably print only a few pages a week but I do >>> want it to work when something is critical. >> >> Im working on a patch (from Rink) to create proper device nodes, should >> be ready shortly. > > I'm just curious. Has this patch been committed yet? Yes, it was yesterday. From eculp at encontacto.net Sat Feb 28 10:56:20 2009 From: eculp at encontacto.net (eculp) Date: Sat Feb 28 10:56:27 2009 Subject: Current - USB2 - cups and u[n]lpt devices. In-Reply-To: <20090228180054.GA86623@citylink.fud.org.nz> References: <20090225061037.10896uy7ft1kgu80@econet.encontacto.net> <20090225152412.GA25211@citylink.fud.org.nz> <20090228115733.1493146fclj807pc@econet.encontacto.net> <20090228180054.GA86623@citylink.fud.org.nz> Message-ID: <20090228125617.1392434c7vmomp4w@econet.encontacto.net> Quoting Andrew Thompson : > On Sat, Feb 28, 2009 at 11:57:33AM -0600, eculp wrote: >> Quoting Andrew Thompson : >> >>> On Wed, Feb 25, 2009 at 06:10:37AM -0600, eculp wrote: >>>> I just rebooted my laptop that I have today's USB2 hopefully with the >>>> latest USB compatibility, if I understood the GENERIC kernel correctly. >>>> I'm using i386 version, up to date as of this morning. Ports are >>>> completely up to date. all etc/dev* stuff is as it was with USB1. >>>> >>>> From the dmesg I get: >>>> >>>> +ugen0.2: at usbus0 >>>> +ulpt0: on usbus0 >>>> +ulpt0: using bi-directional mode >>>> +Symlink: ulpt0 -> usb0.2.1.16 >>>> +Symlink: unlpt0 -> usb0.2.1.17 >>>> >>>> With localhost:631 I see Unable to open device file "/dev/ulpt0": >>>> Operation >>>> not permitted. Probably because, there ain't none. Is there something >>>> else that I need to do that I didn't do before? >>>> >>>> This isn't critical. I probably print only a few pages a week but I do >>>> want it to work when something is critical. >>> >>> Im working on a patch (from Rink) to create proper device nodes, should >>> be ready shortly. >> >> I'm just curious. Has this patch been committed yet? > > Yes, it was yesterday. I rebooted last night and then rebuilt all so I probably just need to reboot. Thanks, ed > From man at email.com.ua Sat Feb 28 14:57:19 2009 From: man at email.com.ua (Artyom Mirgorodsky) Date: Sat Feb 28 14:57:38 2009 Subject: Low perfomance when read from usb flash drive Message-ID: <200903010045.44904.man@email.com.ua> Read speed when copy from usb flash drive decreased from 20MB/s (old usb stack) to 12MB/s. (on windows above 22Mb/s). kernel config "Work" (see attachment) kldstat Id Refs Address Size Name 1 145 0xc0400000 3c0d5c kernel 2 2 0xc07c1000 a44c cd9660.ko 3 2 0xc07cc000 11f78 msdosfs.ko 4 1 0xc07de000 d39c if_nfe.ko 5 2 0xc07ec000 267d0 miibus.ko 6 1 0xc0813000 1b5c8 snd_hda.ko 7 2 0xc082f000 4a558 sound.ko 8 1 0xc087a000 44dc uhid.ko 9 6 0xc087f000 3f2ac usb.ko 10 1 0xc08bf000 4c48 ums.ko 11 1 0xc08c4000 b388 umass.ko 12 3 0xc08d0000 4a45c cam.ko 13 1 0xc091b000 4eac atapicam.ko 14 1 0xc0920000 75c824 nvidia.ko 15 2 0xc107d000 2b188 linux.ko 16 1 0xc10a9000 7acc udf.ko 17 1 0xc10b1000 1e94 cd9660_iconv.ko 18 3 0xc10b3000 5230 libiconv.ko 19 1 0xc10b9000 1ea8 msdosfs_iconv.ko 20 1 0xc10bb000 bebc ohci.ko 21 1 0xc10c7000 e63c ehci.ko 22 1 0xc10d6000 6c990 acpi.ko 23 1 0xc52fb000 d000 ipfw.ko 24 1 0xc540d000 4000 ng_socket.ko 25 7 0xc5411000 b000 netgraph.ko 26 1 0xc54fb000 4000 ng_mppc.ko 27 1 0xc54ff000 2000 rc4.ko 28 1 0xc5502000 3000 ng_iface.ko 29 1 0xc5506000 7000 ng_ppp.ko 30 1 0xc5516000 3000 ng_tee.ko 31 1 0xc551b000 4000 ng_ether.ko 32 1 0xc5525000 6000 ng_pppoe.ko -------------- next part -------------- Feb 28 20:16:30 home syslogd: kernel boot file is /boot/kernel/kernel Feb 28 20:16:30 home kernel: found-> vendor=0x10de, dev=0x0240, revid=0xa2 Feb 28 20:16:30 home kernel: domain=0, bus=0, slot=5, func=0 Feb 28 20:16:30 home kernel: class=03-00-00, hdrtype=0x00, mfdev=0 Feb 28 20:16:30 home kernel: cmdreg=0x0007, statreg=0x00b0, cachelnsz=0 (dwords) Feb 28 20:16:30 home kernel: lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) Feb 28 20:16:30 home kernel: intpin=a, irq=11 Feb 28 20:16:30 home kernel: powerspec 2 supports D0 D3 current D0 Feb 28 20:16:30 home kernel: MSI supports 1 message, 64 bit Feb 28 20:16:30 home kernel: map[10]: type Memory, range 32, base 0xfd000000, size 24, enabled Feb 28 20:16:30 home kernel: map[14]: type Prefetchable Memory, range 64, base 0xd0000000, size 28, enabled Feb 28 20:16:30 home kernel: map[1c]: type Memory, range 64, base 0xfc000000, size 24, enabled Feb 28 20:16:30 home kernel: pcib0: matched entry for 0.5.INTA (src \_SB_.LNEC:0) Feb 28 20:16:30 home kernel: pci_link6: Picked IRQ 16 with weight 0 Feb 28 20:16:30 home kernel: pcib0: slot 5 INTA routed to irq 16 via \_SB_.LNEC Feb 28 20:16:30 home kernel: found-> vendor=0x10de, dev=0x0270, revid=0xa2 Feb 28 20:16:30 home kernel: domain=0, bus=0, slot=9, func=0 Feb 28 20:16:30 home kernel: class=05-00-00, hdrtype=0x00, mfdev=0 Feb 28 20:16:30 home kernel: cmdreg=0x0006, statreg=0x00b0, cachelnsz=0 (dwords) Feb 28 20:16:30 home kernel: lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) Feb 28 20:16:30 home kernel: found-> vendor=0x10de, dev=0x0260, revid=0xa2 Feb 28 20:16:30 home kernel: domain=0, bus=0, slot=10, func=0 Feb 28 20:16:30 home kernel: class=06-01-00, hdrtype=0x00, mfdev=1 Feb 28 20:16:30 home kernel: cmdreg=0x000f, statreg=0x00a0, cachelnsz=0 (dwords) Feb 28 20:16:30 home kernel: lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) Feb 28 20:16:30 home kernel: found-> vendor=0x10de, dev=0x0264, revid=0xa2 Feb 28 20:16:30 home kernel: domain=0, bus=0, slot=10, func=1 Feb 28 20:16:30 home kernel: class=0c-05-00, hdrtype=0x00, mfdev=1 Feb 28 20:16:30 home kernel: cmdreg=0x0001, statreg=0x00b0, cachelnsz=0 (dwords) Feb 28 20:16:30 home kernel: lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) Feb 28 20:16:30 home kernel: intpin=a, irq=5 Feb 28 20:16:30 home kernel: powerspec 2 supports D0 D3 current D0 Feb 28 20:16:30 home kernel: map[20]: type I/O Port, range 32, base 0x600, size 6, enabled Feb 28 20:16:30 home kernel: map[24]: type I/O Port, range 32, base 0x700, size 6, enabled Feb 28 20:16:30 home kernel: pcib0: matched entry for 0.10.INTA (src \_SB_.LSMB:0) Feb 28 20:16:30 home kernel: pci_link14: Picked IRQ 20 with weight 0 Feb 28 20:16:30 home kernel: pcib0: slot 10 INTA routed to irq 20 via \_SB_.LSMB Feb 28 20:16:30 home kernel: found-> vendor=0x10de, dev=0x026d, revid=0xa2 Feb 28 20:16:30 home kernel: domain=0, bus=0, slot=11, func=0 Feb 28 20:16:30 home kernel: class=0c-03-10, hdrtype=0x00, mfdev=1 Feb 28 20:16:30 home kernel: cmdreg=0x0007, statreg=0x00b0, cachelnsz=0 (dwords) Feb 28 20:16:30 home kernel: lattimer=0x00 (0 ns), mingnt=0x03 (750 ns), maxlat=0x01 (250 ns) Feb 28 20:16:30 home kernel: intpin=a, irq=5 Feb 28 20:16:30 home kernel: powerspec 2 supports D0 D1 D2 D3 current D0 Feb 28 20:16:30 home kernel: map[10]: type Memory, range 32, base 0xfebde000, size 12, enabled Feb 28 20:16:30 home kernel: pcib0: matched entry for 0.11.INTA (src \_SB_.LUB0:0) Feb 28 20:16:30 home kernel: pci_link8: Picked IRQ 21 with weight 0 Feb 28 20:16:30 home kernel: pcib0: slot 11 INTA routed to irq 21 via \_SB_.LUB0 Feb 28 20:16:30 home kernel: found-> vendor=0x10de, dev=0x026e, revid=0xa2 Feb 28 20:16:30 home kernel: domain=0, bus=0, slot=11, func=1 Feb 28 20:16:30 home kernel: class=0c-03-20, hdrtype=0x00, mfdev=1 Feb 28 20:16:30 home kernel: cmdreg=0x0006, statreg=0x00b0, cachelnsz=0 (dwords) Feb 28 20:16:30 home kernel: lattimer=0x00 (0 ns), mingnt=0x03 (750 ns), maxlat=0x01 (250 ns) Feb 28 20:16:30 home kernel: intpin=b, irq=7 Feb 28 20:16:30 home kernel: powerspec 2 supports D0 D1 D2 D3 current D0 Feb 28 20:16:30 home kernel: map[10]: type Memory, range 32, base 0xfebdfc00, size 8, enabled Feb 28 20:16:30 home kernel: pcib0: matched entry for 0.11.INTB (src \_SB_.LUB2:0) Feb 28 20:16:30 home kernel: pci_link9: Picked IRQ 22 with weight 0 Feb 28 20:16:30 home kernel: pcib0: slot 11 INTB routed to irq 22 via \_SB_.LUB2 Feb 28 20:16:30 home kernel: found-> vendor=0x10de, dev=0x0265, revid=0xa1 Feb 28 20:16:30 home kernel: domain=0, bus=0, slot=13, func=0 Feb 28 20:16:30 home kernel: class=01-01-8a, hdrtype=0x00, mfdev=0 Feb 28 20:16:30 home kernel: cmdreg=0x0005, statreg=0x00b0, cachelnsz=0 (dwords) Feb 28 20:16:30 home kernel: lattimer=0x00 (0 ns), mingnt=0x03 (750 ns), maxlat=0x01 (250 ns) Feb 28 20:16:30 home kernel: powerspec 2 supports D0 D3 current D0 Feb 28 20:16:30 home kernel: map[20]: type I/O Port, range 32, base 0xffa0, size 4, enabled Feb 28 20:16:30 home kernel: found-> vendor=0x10de, dev=0x0266, revid=0xa1 Feb 28 20:16:30 home kernel: domain=0, bus=0, slot=14, func=0 Feb 28 20:16:30 home kernel: class=01-01-85, hdrtype=0x00, mfdev=0 Feb 28 20:16:30 home kernel: cmdreg=0x0007, statreg=0x00b0, cachelnsz=0 (dwords) Feb 28 20:16:30 home kernel: lattimer=0x00 (0 ns), mingnt=0x03 (750 ns), maxlat=0x01 (250 ns) Feb 28 20:16:30 home kernel: intpin=a, irq=11 Feb 28 20:16:30 home kernel: powerspec 2 supports D0 D3 current D0 Feb 28 20:16:30 home kernel: MSI supports 4 messages, 64 bit Feb 28 20:16:30 home kernel: map[10]: type I/O Port, range 32, base 0xe800, size 3, enabled Feb 28 20:16:30 home kernel: map[14]: type I/O Port, range 32, base 0xe480, size 2, enabled Feb 28 20:16:30 home kernel: map[18]: type I/O Port, range 32, base 0xe400, size 3, enabled Feb 28 20:16:30 home kernel: map[1c]: type I/O Port, range 32, base 0xe080, size 2, enabled Feb 28 20:16:30 home kernel: map[20]: type I/O Port, range 32, base 0xe000, size 4, enabled Feb 28 20:16:30 home kernel: map[24]: type Memory, range 32, base 0xfebdd000, size 12, enabled Feb 28 20:16:30 home kernel: pcib0: matched entry for 0.14.INTA (src \_SB_.LSA0:0) Feb 28 20:16:30 home kernel: pci_link16: Picked IRQ 23 with weight 0 Feb 28 20:16:30 home kernel: pcib0: slot 14 INTA routed to irq 23 via \_SB_.LSA0 Feb 28 20:16:30 home kernel: found-> vendor=0x10de, dev=0x0267, revid=0xa1 Feb 28 20:16:30 home kernel: domain=0, bus=0, slot=15, func=0 Feb 28 20:16:30 home kernel: class=01-01-85, hdrtype=0x00, mfdev=0 Feb 28 20:16:30 home kernel: cmdreg=0x0007, statreg=0x00b0, cachelnsz=0 (dwords) Feb 28 20:16:30 home kernel: lattimer=0x00 (0 ns), mingnt=0x03 (750 ns), maxlat=0x01 (250 ns) Feb 28 20:16:30 home kernel: intpin=a, irq=10 Feb 28 20:16:30 home kernel: powerspec 2 supports D0 D3 current D0 Feb 28 20:16:30 home kernel: MSI supports 4 messages, 64 bit Feb 28 20:16:30 home kernel: map[10]: type I/O Port, range 32, base 0xdc00, size 3, enabled Feb 28 20:16:30 home kernel: map[14]: type I/O Port, range 32, base 0xd880, size 2, enabled Feb 28 20:16:30 home kernel: map[18]: type I/O Port, range 32, base 0xd800, size 3, enabled Feb 28 20:16:30 home kernel: map[1c]: type I/O Port, range 32, base 0xd480, size 2, enabled Feb 28 20:16:30 home kernel: map[20]: type I/O Port, range 32, base 0xd400, size 4, enabled Feb 28 20:16:30 home kernel: map[24]: type Memory, range 32, base 0xfebdc000, size 12, enabled Feb 28 20:16:30 home kernel: pcib0: matched entry for 0.15.INTA (src \_SB_.LSA1:0) Feb 28 20:16:30 home kernel: pci_link17: Picked IRQ 20 with weight 1 Feb 28 20:16:30 home kernel: pcib0: slot 15 INTA routed to irq 20 via \_SB_.LSA1 Feb 28 20:16:30 home kernel: found-> vendor=0x10de, dev=0x026f, revid=0xa2 Feb 28 20:16:30 home kernel: domain=0, bus=0, slot=16, func=0 Feb 28 20:16:30 home kernel: class=06-04-01, hdrtype=0x01, mfdev=1 Feb 28 20:16:30 home kernel: cmdreg=0x0004, statreg=0x00b0, cachelnsz=0 (dwords) Feb 28 20:16:30 home kernel: lattimer=0x00 (0 ns), mingnt=0x02 (500 ns), maxlat=0x02 (500 ns) Feb 28 20:16:30 home kernel: found-> vendor=0x10de, dev=0x026c, revid=0xa2 Feb 28 20:16:30 home kernel: domain=0, bus=0, slot=16, func=1 Feb 28 20:16:30 home kernel: class=04-03-00, hdrtype=0x00, mfdev=1 Feb 28 20:16:30 home kernel: cmdreg=0x0006, statreg=0x00b0, cachelnsz=0 (dwords) Feb 28 20:16:30 home kernel: lattimer=0x00 (0 ns), mingnt=0x02 (500 ns), maxlat=0x05 (1250 ns) Feb 28 20:16:30 home kernel: intpin=b, irq=5 Feb 28 20:16:30 home kernel: powerspec 2 supports D0 D3 current D0 Feb 28 20:16:30 home kernel: MSI supports 1 message, 64 bit, vector masks Feb 28 20:16:30 home kernel: map[10]: type Memory, range 32, base 0xfebd8000, size 14, enabled Feb 28 20:16:30 home kernel: pcib0: matched entry for 0.16.INTB (src \_SB_.LAZA:0) Feb 28 20:16:30 home kernel: pci_link11: Picked IRQ 21 with weight 1 Feb 28 20:16:30 home kernel: pcib0: slot 16 INTB routed to irq 21 via \_SB_.LAZA Feb 28 20:16:30 home kernel: found-> vendor=0x10de, dev=0x0269, revid=0xa1 Feb 28 20:16:30 home kernel: domain=0, bus=0, slot=20, func=0 Feb 28 20:16:30 home kernel: class=06-80-00, hdrtype=0x00, mfdev=0 Feb 28 20:16:30 home kernel: cmdreg=0x0007, statreg=0x00b0, cachelnsz=0 (dwords) Feb 28 20:16:30 home kernel: lattimer=0x00 (0 ns), mingnt=0x01 (250 ns), maxlat=0x14 (5000 ns) Feb 28 20:16:30 home kernel: intpin=a, irq=7 Feb 28 20:16:30 home kernel: powerspec 2 supports D0 D1 D2 D3 current D0 Feb 28 20:16:30 home kernel: map[10]: type Memory, range 32, base 0xfebd7000, size 12, enabled Feb 28 20:16:30 home kernel: map[14]: type I/O Port, range 32, base 0xd080, size 3, enabled Feb 28 20:16:30 home kernel: pcib0: matched entry for 0.20.INTA (src \_SB_.LMAC:0) Feb 28 20:16:30 home kernel: pci_link10: Picked IRQ 22 with weight 1 Feb 28 20:16:30 home kernel: pcib0: slot 20 INTA routed to irq 22 via \_SB_.LMAC Feb 28 20:16:30 home kernel: found-> vendor=0x1022, dev=0x1100, revid=0x00 Feb 28 20:16:30 home kernel: domain=0, bus=0, slot=24, func=0 Feb 28 20:16:30 home kernel: class=06-00-00, hdrtype=0x00, mfdev=1 Feb 28 20:16:30 home kernel: cmdreg=0x0000, statreg=0x0010, cachelnsz=0 (dwords) Feb 28 20:16:30 home kernel: lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) Feb 28 20:16:30 home kernel: found-> vendor=0x1022, dev=0x1101, revid=0x00 Feb 28 20:16:30 home kernel: domain=0, bus=0, slot=24, func=1 Feb 28 20:16:30 home kernel: class=06-00-00, hdrtype=0x00, mfdev=1 Feb 28 20:16:30 home kernel: cmdreg=0x0000, statreg=0x0000, cachelnsz=0 (dwords) Feb 28 20:16:30 home kernel: lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) Feb 28 20:16:30 home kernel: found-> vendor=0x1022, dev=0x1102, revid=0x00 Feb 28 20:16:30 home kernel: domain=0, bus=0, slot=24, func=2 Feb 28 20:16:30 home kernel: class=06-00-00, hdrtype=0x00, mfdev=1 Feb 28 20:16:30 home kernel: cmdreg=0x0000, statreg=0x0000, cachelnsz=0 (dwords) Feb 28 20:16:30 home kernel: lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) Feb 28 20:16:30 home kernel: found-> vendor=0x1022, dev=0x1103, revid=0x00 Feb 28 20:16:30 home kernel: domain=0, bus=0, slot=24, func=3 Feb 28 20:16:30 home kernel: class=06-00-00, hdrtype=0x00, mfdev=1 Feb 28 20:16:30 home kernel: cmdreg=0x0000, statreg=0x0000, cachelnsz=0 (dwords) Feb 28 20:16:30 home kernel: lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) Feb 28 20:16:30 home kernel: pci0: at device 0.0 (no driver attached) Feb 28 20:16:30 home kernel: pci0: at device 0.1 (no driver attached) Feb 28 20:16:30 home kernel: pci0: at device 0.2 (no driver attached) Feb 28 20:16:30 home kernel: pci0: at device 0.3 (no driver attached) Feb 28 20:16:30 home kernel: pci0: at device 0.4 (no driver attached) Feb 28 20:16:30 home kernel: pci0: at device 0.5 (no driver attached) Feb 28 20:16:30 home kernel: pci0: at device 0.6 (no driver attached) Feb 28 20:16:30 home kernel: pci0: at device 0.7 (no driver attached) Feb 28 20:16:30 home kernel: pcib1: at device 2.0 on pci0 Feb 28 20:16:30 home kernel: pcib1: domain 0 Feb 28 20:16:30 home kernel: pcib1: secondary bus 1 Feb 28 20:16:30 home kernel: pcib1: subordinate bus 1 Feb 28 20:16:30 home kernel: pcib1: I/O decode 0x0-0x0 Feb 28 20:16:30 home kernel: pcib1: no prefetched decode Feb 28 20:16:30 home kernel: pci1: on pcib1 Feb 28 20:16:30 home kernel: pci1: domain=0, physical bus=1 Feb 28 20:16:30 home kernel: pcib2: at device 3.0 on pci0 Feb 28 20:16:30 home kernel: pcib2: domain 0 Feb 28 20:16:30 home kernel: pcib2: secondary bus 2 Feb 28 20:16:30 home kernel: pcib2: subordinate bus 2 Feb 28 20:16:30 home kernel: pcib2: I/O decode 0x0-0x0 Feb 28 20:16:30 home kernel: pcib2: no prefetched decode Feb 28 20:16:30 home kernel: pci2: on pcib2 Feb 28 20:16:30 home kernel: pci2: domain=0, physical bus=2 Feb 28 20:16:30 home kernel: pcib3: at device 4.0 on pci0 Feb 28 20:16:30 home kernel: pcib3: domain 0 Feb 28 20:16:30 home kernel: pcib3: secondary bus 3 Feb 28 20:16:30 home kernel: pcib3: subordinate bus 3 Feb 28 20:16:30 home kernel: pcib3: I/O decode 0x0-0x0 Feb 28 20:16:30 home kernel: pcib3: no prefetched decode Feb 28 20:16:30 home kernel: pci3: on pcib3 Feb 28 20:16:30 home kernel: pci3: domain=0, physical bus=3 Feb 28 20:16:30 home kernel: vgapci0: mem 0xfd000000-0xfdffffff,0xd0000000-0xdfffffff,0xfc000000-0xfcffffff irq 16 at device 5.0 on pci0 Feb 28 20:16:30 home kernel: nvidia0: on vgapci0 Feb 28 20:16:30 home kernel: vgapci0: child nvidia0 requested pci_enable_busmaster Feb 28 20:16:30 home kernel: vgapci0: child nvidia0 requested pci_enable_io Feb 28 20:16:30 home kernel: vgapci0: Reserved 0x1000000 bytes for rid 0x10 type 3 at 0xfd000000 Feb 28 20:16:30 home kernel: vgapci0: Reserved 0x10000000 bytes for rid 0x14 type 3 at 0xd0000000 Feb 28 20:16:30 home kernel: vgapci0: Reserved 0x1000000 bytes for rid 0x1c type 3 at 0xfc000000 Feb 28 20:16:30 home kernel: vgapci0: child nvidia0 requested pci_enable_io Feb 28 20:16:30 home kernel: ioapic0: routing intpin 16 (PCI IRQ 16) to lapic 0 vector 49 Feb 28 20:16:30 home kernel: nvidia0: [GIANT-LOCKED] Feb 28 20:16:30 home kernel: nvidia0: [ITHREAD] Feb 28 20:16:30 home kernel: pci0: at device 9.0 (no driver attached) Feb 28 20:16:30 home kernel: isab0: at device 10.0 on pci0 Feb 28 20:16:30 home kernel: isa0: on isab0 Feb 28 20:16:30 home kernel: pci0: at device 10.1 (no driver attached) Feb 28 20:16:30 home kernel: ohci0: mem 0xfebde000-0xfebdefff irq 21 at device 11.0 on pci0 Feb 28 20:16:30 home kernel: ohci0: Reserved 0x1000 bytes for rid 0x10 type 3 at 0xfebde000 Feb 28 20:16:30 home kernel: ioapic0: routing intpin 21 (PCI IRQ 21) to lapic 0 vector 50 Feb 28 20:16:30 home kernel: ohci0: [MPSAFE] Feb 28 20:16:30 home kernel: ohci0: [ITHREAD] Feb 28 20:16:30 home kernel: usbus0: on ohci0 Feb 28 20:16:30 home kernel: ehci0: mem 0xfebdfc00-0xfebdfcff irq 22 at device 11.1 on pci0 Feb 28 20:16:30 home kernel: ehci0: Reserved 0x100 bytes for rid 0x10 type 3 at 0xfebdfc00 Feb 28 20:16:30 home kernel: ioapic0: routing intpin 22 (PCI IRQ 22) to lapic 0 vector 51 Feb 28 20:16:30 home kernel: ehci0: [MPSAFE] Feb 28 20:16:30 home kernel: ehci0: [ITHREAD] Feb 28 20:16:30 home kernel: usbus1: waiting for BIOS to give up control Feb 28 20:16:30 home kernel: usbus1: timed out waiting for BIOS Feb 28 20:16:30 home kernel: usbus1: EHCI version 1.0 Feb 28 20:16:30 home kernel: usbus1: on ehci0 Feb 28 20:16:30 home kernel: atapci0: port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xffa0-0xffaf at device 13.0 on pci0 Feb 28 20:16:30 home kernel: atapci0: Reserved 0x10 bytes for rid 0x20 type 4 at 0xffa0 Feb 28 20:16:30 home kernel: ata0: on atapci0 Feb 28 20:16:30 home kernel: atapci0: Reserved 0x8 bytes for rid 0x10 type 4 at 0x1f0 Feb 28 20:16:30 home kernel: atapci0: Reserved 0x1 bytes for rid 0x14 type 4 at 0x3f6 Feb 28 20:16:30 home kernel: ata0: reset tp1 mask=03 ostat0=50 ostat1=00 Feb 28 20:16:30 home kernel: ata0: stat0=0x00 err=0x01 lsb=0x14 msb=0xeb Feb 28 20:16:30 home kernel: ata0: stat1=0x00 err=0x00 lsb=0x00 msb=0x00 Feb 28 20:16:30 home kernel: ata0: reset tp2 stat0=00 stat1=00 devices=0x10000 Feb 28 20:16:30 home kernel: ioapic0: routing intpin 14 (ISA IRQ 14) to lapic 0 vector 52 Feb 28 20:16:30 home kernel: ata0: [MPSAFE] Feb 28 20:16:30 home kernel: ata0: [ITHREAD] Feb 28 20:16:30 home kernel: ata1: on atapci0 Feb 28 20:16:30 home kernel: atapci0: Reserved 0x8 bytes for rid 0x18 type 4 at 0x170 Feb 28 20:16:30 home kernel: atapci0: Reserved 0x1 bytes for rid 0x1c type 4 at 0x376 Feb 28 20:16:30 home kernel: ata1: reset tp1 mask=03 ostat0=60 ostat1=70 Feb 28 20:16:30 home kernel: ata1: stat0=0x20 err=0x20 lsb=0x20 msb=0x20 Feb 28 20:16:30 home kernel: ata1: stat1=0x30 err=0x30 lsb=0x30 msb=0x30 Feb 28 20:16:30 home kernel: ata1: reset tp2 stat0=20 stat1=30 devices=0x0 Feb 28 20:16:30 home kernel: ioapic0: routing intpin 15 (ISA IRQ 15) to lapic 0 vector 53 Feb 28 20:16:30 home kernel: ata1: [MPSAFE] Feb 28 20:16:30 home kernel: ata1: [ITHREAD] Feb 28 20:16:30 home kernel: atapci1: port 0xe800-0xe807,0xe480-0xe483,0xe400-0xe407,0xe080-0xe083,0xe000-0xe00f mem 0xfebdd000-0xfebddfff irq 23 at device 14.0 on pci0 Feb 28 20:16:30 home kernel: atapci1: Reserved 0x10 bytes for rid 0x20 type 4 at 0xe000 Feb 28 20:16:30 home kernel: ioapic0: routing intpin 23 (PCI IRQ 23) to lapic 0 vector 54 Feb 28 20:16:30 home kernel: atapci1: [MPSAFE] Feb 28 20:16:30 home kernel: atapci1: [ITHREAD] Feb 28 20:16:30 home kernel: atapci1: Reserved 0x1000 bytes for rid 0x24 type 3 at 0xfebdd000 Feb 28 20:16:30 home kernel: ata2: on atapci1 Feb 28 20:16:30 home kernel: atapci1: Reserved 0x8 bytes for rid 0x10 type 4 at 0xe800 Feb 28 20:16:30 home kernel: atapci1: Reserved 0x4 bytes for rid 0x14 type 4 at 0xe480 Feb 28 20:16:30 home kernel: ata2: SATA connect time=0ms Feb 28 20:16:30 home kernel: ata2: reset tp1 mask=01 ostat0=50 ostat1=00 Feb 28 20:16:30 home kernel: ata2: stat0=0x50 err=0x01 lsb=0x00 msb=0x00 Feb 28 20:16:30 home kernel: ata2: reset tp2 stat0=50 stat1=00 devices=0x1 Feb 28 20:16:30 home kernel: ata2: [MPSAFE] Feb 28 20:16:30 home kernel: ata2: [ITHREAD] Feb 28 20:16:30 home kernel: ata3: on atapci1 Feb 28 20:16:30 home kernel: atapci1: Reserved 0x8 bytes for rid 0x18 type 4 at 0xe400 Feb 28 20:16:30 home kernel: atapci1: Reserved 0x4 bytes for rid 0x1c type 4 at 0xe080 Feb 28 20:16:30 home kernel: ata3: SATA connect time=0ms Feb 28 20:16:30 home kernel: ata3: reset tp1 mask=01 ostat0=50 ostat1=00 Feb 28 20:16:30 home kernel: ata3: stat0=0x50 err=0x01 lsb=0x00 msb=0x00 Feb 28 20:16:30 home kernel: ata3: reset tp2 stat0=50 stat1=00 devices=0x1 Feb 28 20:16:30 home kernel: ata3: [MPSAFE] Feb 28 20:16:30 home kernel: ata3: [ITHREAD] Feb 28 20:16:30 home kernel: atapci2: port 0xdc00-0xdc07,0xd880-0xd883,0xd800-0xd807,0xd480-0xd483,0xd400-0xd40f mem 0xfebdc000-0xfebdcfff irq 20 at device 15.0 on pci0 Feb 28 20:16:30 home kernel: atapci2: Reserved 0x10 bytes for rid 0x20 type 4 at 0xd400 Feb 28 20:16:30 home kernel: ioapic0: routing intpin 20 (PCI IRQ 20) to lapic 0 vector 55 Feb 28 20:16:30 home kernel: atapci2: [MPSAFE] Feb 28 20:16:30 home kernel: atapci2: [ITHREAD] Feb 28 20:16:30 home kernel: atapci2: Reserved 0x1000 bytes for rid 0x24 type 3 at 0xfebdc000 Feb 28 20:16:30 home kernel: ata4: on atapci2 Feb 28 20:16:30 home kernel: atapci2: Reserved 0x8 bytes for rid 0x10 type 4 at 0xdc00 Feb 28 20:16:30 home kernel: atapci2: Reserved 0x4 bytes for rid 0x14 type 4 at 0xd880 Feb 28 20:16:30 home kernel: ata4: SATA connect status=00000000 Feb 28 20:16:30 home kernel: ata4: [MPSAFE] Feb 28 20:16:30 home kernel: ata4: [ITHREAD] Feb 28 20:16:30 home kernel: ata5: on atapci2 Feb 28 20:16:30 home kernel: atapci2: Reserved 0x8 bytes for rid 0x18 type 4 at 0xd800 Feb 28 20:16:30 home kernel: atapci2: Reserved 0x4 bytes for rid 0x1c type 4 at 0xd480 Feb 28 20:16:30 home kernel: ata5: SATA connect status=00000000 Feb 28 20:16:30 home kernel: ata5: [MPSAFE] Feb 28 20:16:30 home kernel: ata5: [ITHREAD] Feb 28 20:16:30 home kernel: pcib4: at device 16.0 on pci0 Feb 28 20:16:30 home kernel: pcib4: domain 0 Feb 28 20:16:30 home kernel: pcib4: secondary bus 4 Feb 28 20:16:30 home kernel: pcib4: subordinate bus 4 Feb 28 20:16:30 home kernel: pcib4: I/O decode 0x0-0x0 Feb 28 20:16:30 home kernel: pcib4: no prefetched decode Feb 28 20:16:30 home kernel: pcib4: Subtractively decoded bridge. Feb 28 20:16:30 home kernel: pci4: on pcib4 Feb 28 20:16:30 home kernel: pci4: domain=0, physical bus=4 Feb 28 20:16:30 home kernel: hdac0: mem 0xfebd8000-0xfebdbfff irq 21 at device 16.1 on pci0 Feb 28 20:16:30 home kernel: hdac0: HDA Driver Revision: 20090226_0129 Feb 28 20:16:30 home kernel: hdac0: DMA Coherency: Uncacheable / vendor=0x10de Feb 28 20:16:30 home kernel: hdac0: Reserved 0x4000 bytes for rid 0x10 type 3 at 0xfebd8000 Feb 28 20:16:30 home kernel: hdac0: [MPSAFE] Feb 28 20:16:30 home kernel: hdac0: [ITHREAD] Feb 28 20:16:30 home kernel: hdac0: CORB size: 256 Feb 28 20:16:30 home kernel: hdac0: RIRB size: 256 Feb 28 20:16:30 home kernel: hdac0: Streams: ISS=4 OSS=4 BSS=0 Feb 28 20:16:30 home kernel: hdac0: hdac_dma_alloc: size=1024 -> roundsz=1024 Feb 28 20:16:30 home kernel: hdac0: hdac_dma_alloc: size=2048 -> roundsz=2048 Feb 28 20:16:30 home kernel: hdac0: Reset controller... Feb 28 20:16:30 home kernel: nfe0: port 0xd080-0xd087 mem 0xfebd7000-0xfebd7fff irq 22 at device 20.0 on pci0 Feb 28 20:16:30 home kernel: nfe0: Reserved 0x1000 bytes for rid 0x10 type 3 at 0xfebd7000 Feb 28 20:16:30 home kernel: miibus0: on nfe0 Feb 28 20:16:30 home kernel: e1000phy0: PHY 1 on miibus0 Feb 28 20:16:30 home kernel: e1000phy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseTX-FDX, auto Feb 28 20:16:30 home kernel: nfe0: bpf attached Feb 28 20:16:30 home kernel: nfe0: Ethernet address: 00:15:f2:5b:84:1a Feb 28 20:16:30 home kernel: nfe0: [MPSAFE] Feb 28 20:16:30 home kernel: nfe0: [FILTER] Feb 28 20:16:30 home kernel: acpi_button0: on acpi0 Feb 28 20:16:30 home kernel: atrtc0: port 0x70-0x71 irq 8 on acpi0 Feb 28 20:16:30 home kernel: atrtc0: registered as a time-of-day clock (resolution 1000000us) Feb 28 20:16:30 home kernel: atkbdc0: port 0x60,0x64 irq 1 on acpi0 Feb 28 20:16:30 home kernel: atkbd0: irq 1 on atkbdc0 Feb 28 20:16:30 home kernel: atkbd: the current kbd controller command byte 0065 Feb 28 20:16:30 home kernel: atkbd: keyboard ID 0x41ab (2) Feb 28 20:16:30 home kernel: kbd0: atkbd0, AT 101/102 (2), config:0x0, flags:0x3d0000 Feb 28 20:16:30 home kernel: ioapic0: routing intpin 1 (ISA IRQ 1) to lapic 0 vector 56 Feb 28 20:16:30 home kernel: atkbd0: [GIANT-LOCKED] Feb 28 20:16:30 home kernel: atkbd0: [ITHREAD] Feb 28 20:16:30 home kernel: psm0: unable to allocate IRQ Feb 28 20:16:30 home kernel: cpu0: on acpi0 Feb 28 20:16:30 home kernel: cpu0: switching to generic Cx mode Feb 28 20:16:30 home kernel: powernow0: on cpu0 Feb 28 20:16:30 home kernel: cpu1: on acpi0 Feb 28 20:16:30 home kernel: powernow1: on cpu1 Feb 28 20:16:30 home kernel: pnp_identify: Trying Read_Port at 203 Feb 28 20:16:30 home kernel: pnp_identify: Trying Read_Port at 243 Feb 28 20:16:30 home kernel: pnp_identify: Trying Read_Port at 283 Feb 28 20:16:30 home kernel: pnp_identify: Trying Read_Port at 2c3 Feb 28 20:16:30 home kernel: pnp_identify: Trying Read_Port at 303 Feb 28 20:16:30 home kernel: pnp_identify: Trying Read_Port at 343 Feb 28 20:16:30 home kernel: pnp_identify: Trying Read_Port at 383 Feb 28 20:16:30 home kernel: pnp_identify: Trying Read_Port at 3c3 Feb 28 20:16:30 home kernel: PNP Identify complete Feb 28 20:16:30 home kernel: isa_probe_children: disabling PnP devices Feb 28 20:16:30 home kernel: pmtimer0 on isa0 Feb 28 20:16:30 home kernel: ata: ata0 already exists; skipping it Feb 28 20:16:30 home kernel: ata: ata1 already exists; skipping it Feb 28 20:16:30 home kernel: atkbdc: atkbdc0 already exists; skipping it Feb 28 20:16:30 home kernel: atrtc: atrtc0 already exists; skipping it Feb 28 20:16:30 home kernel: sc: sc0 already exists; skipping it Feb 28 20:16:30 home kernel: vga: vga0 already exists; skipping it Feb 28 20:16:30 home kernel: isa_probe_children: probing non-PnP devices Feb 28 20:16:30 home kernel: sc0: at flags 0x100 on isa0 Feb 28 20:16:30 home kernel: sc0: VGA <16 virtual consoles, flags=0x300> Feb 28 20:16:30 home kernel: sc0: fb0, kbd0, terminal emulator: scteken (teken terminal) Feb 28 20:16:30 home kernel: vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 Feb 28 20:16:30 home kernel: adv0: not probed (disabled) Feb 28 20:16:30 home kernel: aha0: not probed (disabled) Feb 28 20:16:30 home kernel: aic0: not probed (disabled) Feb 28 20:16:30 home kernel: bt0: not probed (disabled) Feb 28 20:16:30 home kernel: cs0: not probed (disabled) Feb 28 20:16:30 home kernel: ed0: not probed (disabled) Feb 28 20:16:30 home kernel: fdc0 failed to probe at port 0x3f0 irq 6 drq 2 on isa0 Feb 28 20:16:30 home kernel: fe0: not probed (disabled) Feb 28 20:16:30 home kernel: ie0: not probed (disabled) Feb 28 20:16:30 home kernel: le0: not probed (disabled) Feb 28 20:16:30 home kernel: ppc0 failed to probe at irq 7 on isa0 Feb 28 20:16:30 home kernel: sn0: not probed (disabled) Feb 28 20:16:30 home kernel: uart0 failed to probe at port 0x3f8 irq 4 on isa0 Feb 28 20:16:30 home kernel: uart1 failed to probe at port 0x2f8 irq 3 on isa0 Feb 28 20:16:30 home kernel: uart2: not probed (disabled) Feb 28 20:16:30 home kernel: uart3: not probed (disabled) Feb 28 20:16:30 home kernel: isa_probe_children: probing PnP devices Feb 28 20:16:30 home kernel: Device configuration finished. Feb 28 20:16:30 home kernel: lapic: Divisor 2, Frequency 100558264 hz Feb 28 20:16:30 home kernel: Timecounter "TSC" frequency 2011164995 Hz quality -100 Feb 28 20:16:30 home kernel: Timecounters tick every 1.000 msec Feb 28 20:16:30 home kernel: Linux ELF exec handler installed Feb 28 20:16:30 home kernel: lo0: bpf attached Feb 28 20:16:30 home kernel: ata0: Identifying devices: 00010000 Feb 28 20:16:30 home kernel: ata0: New devices: 00010000 Feb 28 20:16:30 home kernel: usbus0: 12Mbps Full Speed USB v1.0 Feb 28 20:16:30 home kernel: usbus1: 480Mbps High Speed USB v2.0 Feb 28 20:16:30 home kernel: ata0-master: pio=PIO4 wdma=WDMA2 udma=UDMA66 cable=80 wire Feb 28 20:16:30 home kernel: acd0: setting PIO4 on nForce MCP51 chip Feb 28 20:16:30 home kernel: acd0: setting UDMA66 on nForce MCP51 chip Feb 28 20:16:30 home kernel: ugen0.1: at usbus0 Feb 28 20:16:30 home kernel: ushub0: on usbus0 Feb 28 20:16:30 home kernel: ugen1.1: at usbus1 Feb 28 20:16:30 home kernel: ushub1: on usbus1 Feb 28 20:16:30 home kernel: acd0: DVDR drive at ata0 as master Feb 28 20:16:30 home kernel: acd0: read 8268KB/s (8268KB/s) write 8268KB/s (8268KB/s), 2048KB buffer, UDMA66 Feb 28 20:16:30 home kernel: acd0: Reads: CDR, CDRW, CDDA stream, DVDROM, DVDR, DVDRAM, packet Feb 28 20:16:30 home kernel: acd0: Writes: CDR, CDRW, DVDR, DVDRAM, test write, burnproof Feb 28 20:16:30 home kernel: acd0: Audio: play, 256 volume levels Feb 28 20:16:30 home kernel: acd0: Mechanism: ejectable tray, unlocked Feb 28 20:16:30 home kernel: acd0: Medium: no/blank disc Feb 28 20:16:30 home kernel: ata1: Identifying devices: 00000000 Feb 28 20:16:30 home kernel: ata1: New devices: 00000000 Feb 28 20:16:30 home kernel: ata2: Identifying devices: 00000001 Feb 28 20:16:30 home kernel: ata2: New devices: 00000001 Feb 28 20:16:30 home kernel: ata2-master: pio=PIO4 wdma=WDMA2 udma=UDMA133 cable=40 wire Feb 28 20:16:30 home kernel: ad4: 194481MB at ata2-master SATA300 Feb 28 20:16:30 home kernel: ad4: 398297088 sectors [395136C/16H/63S] 16 sectors/interrupt 1 depth queue Feb 28 20:16:30 home kernel: ata3: Identifying devices: 00000001 Feb 28 20:16:30 home kernel: ata3: New devices: 00000001 Feb 28 20:16:30 home kernel: ata3-master: pio=PIO4 wdma=WDMA2 udma=UDMA133 cable=40 wire Feb 28 20:16:30 home kernel: ad6: 381554MB at ata3-master SATA300 Feb 28 20:16:30 home kernel: ad6: 781422768 sectors [775221C/16H/63S] 16 sectors/interrupt 1 depth queue Feb 28 20:16:30 home kernel: ata4: Identifying devices: 00000000 Feb 28 20:16:30 home kernel: ata4: New devices: 00000000 Feb 28 20:16:30 home kernel: ata5: Identifying devices: 00000000 Feb 28 20:16:30 home kernel: ata5: New devices: 00000000 Feb 28 20:16:30 home kernel: hdac0: HDA Config: on=0x00000000 off=0x00000000 Feb 28 20:16:30 home kernel: hdac0: Starting CORB Engine... Feb 28 20:16:30 home kernel: hdac0: Starting RIRB Engine... Feb 28 20:16:30 home kernel: hdac0: Enabling controller interrupt... Feb 28 20:16:30 home kernel: hdac0: Scanning HDA codecs ... Feb 28 20:16:30 home kernel: hdac0: Probing codec #0... Feb 28 20:16:30 home kernel: hdac0: HDA Codec #0: Analog Devices AD1986A Feb 28 20:16:30 home kernel: hdac0: HDA Codec ID: 0x11d41986 Feb 28 20:16:30 home kernel: hdac0: Vendor: 0x11d4 Feb 28 20:16:30 home kernel: hdac0: Device: 0x1986 Feb 28 20:16:30 home kernel: hdac0: Revision: 0x05 Feb 28 20:16:30 home kernel: hdac0: Stepping: 0x00 Feb 28 20:16:30 home kernel: hdac0: PCI Subvendor: 0xcb8410de Feb 28 20:16:30 home kernel: hdac0: startnode=1 endnode=2 Feb 28 20:16:30 home kernel: hdac0: Found audio FG nid=1 startnode=2 endnode=44 total=42 Feb 28 20:16:30 home kernel: hdac0: Feb 28 20:16:30 home kernel: hdac0: Processing audio FG cad=0 nid=1... Feb 28 20:16:30 home kernel: hdac0: Powering up... Feb 28 20:16:30 home kernel: hdac0: Parsing audio FG... Feb 28 20:16:30 home kernel: hdac0: GPIO: 0x00000100 NumGPIO=0 NumGPO=1 NumGPI=0 GPIWake=0 GPIUnsol=0 Feb 28 20:16:30 home kernel: hdac0: GHOST: nid=2 j=0 entnum=4 index=0 res=0x00000601 Feb 28 20:16:30 home kernel: hdac0: hdac_widget_connection_parse: nid=18 WARNING: zero cnid entnum=4 j=2 index=0 entries=8 found=2 res=0x21002211 Feb 28 20:16:30 home kernel: hdac0: GHOST: nid=18 j=2 entnum=4 index=0 res=0x21002211 Feb 28 20:16:30 home kernel: hdac0: nid 26 0x02214021 as 2 seq 1 Headphones Jack jack 1 loc 2 color Green misc 0 Feb 28 20:16:30 home kernel: hdac0: nid 27 0x01014011 as 1 seq 1 Line-out Jack jack 1 loc 1 color Green misc 0 Feb 28 20:16:30 home kernel: hdac0: nid 28 0x01013012 as 1 seq 2 Line-out Jack jack 1 loc 1 color Blue misc 0 Feb 28 20:16:30 home kernel: hdac0: Patching pin config nid=28 0x01013012 -> 0x01813081 Feb 28 20:16:30 home kernel: hdac0: nid 29 0x01019015 as 1 seq 5 Line-out Jack jack 1 loc 1 color Pink misc 0 Feb 28 20:16:30 home kernel: hdac0: Patching pin config nid=29 0x01019015 -> 0x01a19082 Feb 28 20:16:30 home kernel: hdac0: nid 30 0x501700f0 as 15 seq 0 Speaker None jack 7 loc 16 color Unknown misc 0 Feb 28 20:16:30 home kernel: hdac0: nid 31 0x02a190f0 as 15 seq 0 Mic Jack jack 1 loc 2 color Pink misc 0 Feb 28 20:16:30 home kernel: hdac0: Patching pin config nid=31 0x02a190f0 -> 0x02a19083 Feb 28 20:16:30 home kernel: hdac0: nid 32 0x018130f0 as 15 seq 0 Line-in Jack jack 1 loc 1 color Blue misc 0 Feb 28 20:16:30 home kernel: hdac0: Patching pin config nid=32 0x018130f0 -> 0x01813084 Feb 28 20:16:30 home kernel: hdac0: nid 33 0x509700f0 as 15 seq 0 AUX None jack 7 loc 16 color Unknown misc 0 Feb 28 20:16:30 home kernel: hdac0: nid 34 0x993310f0 as 15 seq 0 CD Fixed jack 3 loc 25 color Black misc 0 Feb 28 20:16:30 home kernel: hdac0: Patching pin config nid=34 0x993310f0 -> 0x99331085 Feb 28 20:16:30 home kernel: hdac0: nid 35 0x50b700f0 as 15 seq 0 Telephony None jack 7 loc 16 color Unknown misc 0 Feb 28 20:16:30 home kernel: hdac0: nid 36 0x50f700f0 as 15 seq 0 Other None jack 7 loc 16 color Unknown misc 0 Feb 28 20:16:30 home kernel: hdac0: Patching pin config nid=36 0x50f700f0 -> 0x50f70086 Feb 28 20:16:30 home kernel: hdac0: nid 37 0x0145f0f0 as 15 seq 0 SPDIF-out Jack jack 5 loc 1 color Other misc 0 Feb 28 20:16:30 home kernel: hdac0: Parsing Ctls... Feb 28 20:16:30 home kernel: hdac0: Parsing vendor patch... Feb 28 20:16:30 home kernel: hdac0: Disabling nonaudio... Feb 28 20:16:30 home kernel: hdac0: Disabling nid 38 due to it's non-audio type. Feb 28 20:16:30 home kernel: hdac0: Disabling useless... Feb 28 20:16:30 home kernel: hdac0: Disabling pin nid 30 due to None connectivity. Feb 28 20:16:30 home kernel: hdac0: Disabling pin nid 33 due to None connectivity. Feb 28 20:16:30 home kernel: hdac0: Disabling pin nid 35 due to None connectivity. Feb 28 20:16:30 home kernel: hdac0: Disabling pin nid 36 due to None connectivity. Feb 28 20:16:30 home kernel: hdac0: Disabling ctl 19 nid 30 cnid -1 due to disabled widget. Feb 28 20:16:30 home kernel: hdac0: Disabling nid 2 connection 0 due to disabled child widget. Feb 28 20:16:30 home kernel: hdac0: Disabling nid 14 due to all it's consumers disabled. Feb 28 20:16:30 home kernel: hdac0: Disabling nid 15 connection 4 due to disabled child widget. Feb 28 20:16:30 home kernel: hdac0: Disabling nid 15 connection 5 due to disabled child widget. Feb 28 20:16:30 home kernel: hdac0: Disabling nid 15 connection 6 due to disabled child widget. Feb 28 20:16:30 home kernel: hdac0: Disabling nid 15 connection 7 due to disabled child widget. Feb 28 20:16:30 home kernel: hdac0: Disabling nid 17 connection 1 due to disabled child widget. Feb 28 20:16:30 home kernel: hdac0: Disabling nid 18 connection 2 due to disabled child widget. Feb 28 20:16:30 home kernel: hdac0: Disabling nid 18 connection 3 due to disabled child widget. Feb 28 20:16:30 home kernel: hdac0: Disabling nid 18 connection 7 due to disabled child widget. Feb 28 20:16:30 home kernel: hdac0: Disabling nid 20 connection 0 due to disabled child widget. Feb 28 20:16:30 home kernel: hdac0: Disabling nid 20 due to all it's inputs disabled. Feb 28 20:16:30 home kernel: hdac0: Disabling nid 22 connection 0 due to disabled child widget. Feb 28 20:16:30 home kernel: hdac0: Disabling nid 22 due to all it's inputs disabled. Feb 28 20:16:30 home kernel: hdac0: Disabling nid 24 connection 1 due to disabled child widget. Feb 28 20:16:30 home kernel: hdac0: Disabling ctl 10 nid 20 cnid -1 due to disabled widget. Feb 28 20:16:30 home kernel: hdac0: Disabling ctl 12 nid 22 cnid -1 due to disabled widget. Feb 28 20:16:30 home kernel: hdac0: Disabling nid 7 connection 3 due to disabled child widget. Feb 28 20:16:30 home kernel: hdac0: Disabling nid 7 connection 5 due to disabled child widget. Feb 28 20:16:30 home kernel: hdac0: Patched pins configuration: Feb 28 20:16:30 home kernel: hdac0: nid 26 0x02214021 as 2 seq 1 Headphones Jack jack 1 loc 2 color Green misc 0 Feb 28 20:16:30 home kernel: hdac0: nid 27 0x01014011 as 1 seq 1 Line-out Jack jack 1 loc 1 color Green misc 0 Feb 28 20:16:30 home kernel: hdac0: nid 28 0x01813081 as 8 seq 1 Line-in Jack jack 1 loc 1 color Blue misc 0 Feb 28 20:16:30 home kernel: hdac0: nid 29 0x01a19082 as 8 seq 2 Mic Jack jack 1 loc 1 color Pink misc 0 Feb 28 20:16:30 home kernel: hdac0: nid 30 0x501700f0 as 15 seq 0 Speaker None jack 7 loc 16 color Unknown misc 0 [DISABLED] Feb 28 20:16:30 home kernel: hdac0: nid 31 0x02a19083 as 8 seq 3 Mic Jack jack 1 loc 2 color Pink misc 0 Feb 28 20:16:30 home kernel: hdac0: nid 32 0x01813084 as 8 seq 4 Line-in Jack jack 1 loc 1 color Blue misc 0 Feb 28 20:16:30 home kernel: hdac0: nid 33 0x509700f0 as 15 seq 0 AUX None jack 7 loc 16 color Unknown misc 0 [DISABLED] Feb 28 20:16:30 home kernel: hdac0: nid 34 0x99331085 as 8 seq 5 CD Fixed jack 3 loc 25 color Black misc 0 Feb 28 20:16:30 home kernel: hdac0: nid 35 0x50b700f0 as 15 seq 0 Telephony None jack 7 loc 16 color Unknown misc 0 [DISABLED] Feb 28 20:16:30 home kernel: hdac0: nid 36 0x50f70086 as 8 seq 6 Other None jack 7 loc 16 color Unknown misc 0 [DISABLED] Feb 28 20:16:30 home kernel: hdac0: nid 37 0x0145f0f0 as 15 seq 0 SPDIF-out Jack jack 5 loc 1 color Other misc 0 Feb 28 20:16:30 home kernel: hdac0: Parsing pin associations... Feb 28 20:16:30 home kernel: hdac0: 4 associations found: Feb 28 20:16:30 home kernel: hdac0: Association 0 (1) out: Feb 28 20:16:30 home kernel: hdac0: Pin nid=27 seq=1 Feb 28 20:16:30 home kernel: hdac0: Association 1 (2) out: Feb 28 20:16:30 home kernel: hdac0: Pin nid=26 seq=1 Feb 28 20:16:30 home kernel: hdac0: Association 2 (8) in: Feb 28 20:16:30 home kernel: hdac0: Pin nid=28 seq=1 Feb 28 20:16:30 home kernel: hdac0: Pin nid=29 seq=2 Feb 28 20:16:30 home kernel: hdac0: Pin nid=31 seq=3 Feb 28 20:16:30 home kernel: hdac0: Pin nid=32 seq=4 Feb 28 20:16:30 home kernel: hdac0: Pin nid=34 seq=5 Feb 28 20:16:30 home kernel: hdac0: Association 3 (15) out: Feb 28 20:16:30 home kernel: hdac0: Pin nid=37 seq=0 Feb 28 20:16:30 home kernel: hdac0: Building AFG tree... Feb 28 20:16:30 home kernel: hdac0: Tracing association 0 (1) Feb 28 20:16:30 home kernel: hdac0: Tracing pin 27 with min nid 0 Feb 28 20:16:30 home kernel: hdac0: tracing via nid 27 Feb 28 20:16:30 home kernel: hdac0: tracing via nid 11 Feb 28 20:16:30 home kernel: hdac0: tracing via nid 7 Feb 28 20:16:30 home kernel: hdac0: tracing via nid 3 Feb 28 20:16:30 home kernel: hdac0: nid 3 returned 3 Feb 28 20:16:30 home kernel: hdac0: tracing via nid 9 Feb 28 20:16:30 home kernel: hdac0: tracing via nid 4 Feb 28 20:16:30 home kernel: hdac0: nid 4 returned 4 Feb 28 20:16:30 home kernel: hdac0: tracing via nid 5 Feb 28 20:16:30 home kernel: hdac0: nid 5 returned 5 Feb 28 20:16:30 home kernel: hdac0: nid 9 returned 4 Feb 28 20:16:30 home kernel: hdac0: tracing via nid 19 Feb 28 20:16:30 home kernel: hdac0: tracing via nid 17 Feb 28 20:16:30 home kernel: hdac0: tracing via nid 15 Feb 28 20:16:30 home kernel: hdac0: tracing via nid 31 Feb 28 20:16:30 home kernel: hdac0: nid 31 returned 0 Feb 28 20:16:30 home kernel: hdac0: tracing via nid 32 Feb 28 20:16:30 home kernel: hdac0: nid 32 returned 0 Feb 28 20:16:30 home kernel: hdac0: tracing via nid 29 Feb 28 20:16:30 home kernel: hdac0: nid 29 returned 0 Feb 28 20:16:30 home kernel: hdac0: nid 15 returned 0 Feb 28 20:16:30 home kernel: hdac0: nid 17 returned 0 Feb 28 20:16:30 home kernel: hdac0: nid 19 returned 0 Feb 28 20:16:30 home kernel: hdac0: tracing via nid 21 Feb 28 20:16:30 home kernel: hdac0: tracing via nid 34 Feb 28 20:16:30 home kernel: hdac0: nid 34 returned 0 Feb 28 20:16:30 home kernel: hdac0: nid 21 returned 0 Feb 28 20:16:30 home kernel: hdac0: tracing via nid 23 Feb 28 20:16:30 home kernel: hdac0: tracing via nid 16 Feb 28 20:16:30 home kernel: hdac0: tracing via nid 32 Feb 28 20:16:30 home kernel: hdac0: nid 32 returned 0 Feb 28 20:16:30 home kernel: hdac0: tracing via nid 28 Feb 28 20:16:30 home kernel: hdac0: nid 28 returned 0 Feb 28 20:16:30 home kernel: hdac0: tracing via nid 31 Feb 28 20:16:30 home kernel: hdac0: nid 31 returned 0 Feb 28 20:16:30 home kernel: hdac0: nid 16 returned 0 Feb 28 20:16:30 home kernel: hdac0: nid 23 returned 0 Feb 28 20:16:30 home kernel: hdac0: tracing via nid 24 Feb 28 20:16:30 home kernel: hdac0: tracing via nid 25 Feb 28 20:16:30 home kernel: hdac0: nid 25 returned 0 Feb 28 20:16:30 home kernel: hdac0: nid 24 returned 0 Feb 28 20:16:30 home kernel: hdac0: nid 7 returned 3 Feb 28 20:16:30 home kernel: hdac0: tracing via nid 4 Feb 28 20:16:30 home kernel: hdac0: nid 4 returned 4 Feb 28 20:16:30 home kernel: hdac0: nid 11 returned 3 Feb 28 20:16:30 home kernel: hdac0: nid 27 returned 3 Feb 28 20:16:30 home kernel: hdac0: Pin 27 traced to DAC 3 Feb 28 20:16:30 home kernel: hdac0: Association 0 (1) trace succeeded Feb 28 20:16:30 home kernel: hdac0: Tracing association 1 (2) Feb 28 20:16:30 home kernel: hdac0: Tracing pin 26 with min nid 0 Feb 28 20:16:30 home kernel: hdac0: tracing via nid 26 Feb 28 20:16:30 home kernel: hdac0: tracing via nid 10 Feb 28 20:16:30 home kernel: hdac0: tracing via nid 7 Feb 28 20:16:30 home kernel: hdac0: nid 7 busy by association 0 Feb 28 20:16:30 home kernel: hdac0: tracing via nid 4 Feb 28 20:16:30 home kernel: hdac0: nid 4 returned 4 Feb 28 20:16:30 home kernel: hdac0: tracing via nid 5 Feb 28 20:16:30 home kernel: hdac0: nid 5 returned 5 Feb 28 20:16:30 home kernel: hdac0: nid 10 returned 4 Feb 28 20:16:30 home kernel: hdac0: nid 26 returned 4 Feb 28 20:16:30 home kernel: hdac0: Pin 26 traced to DAC 4 Feb 28 20:16:30 home kernel: hdac0: Association 1 (2) trace succeeded Feb 28 20:16:30 home kernel: hdac0: Tracing association 2 (8) Feb 28 20:16:30 home kernel: hdac0: Tracing pin 28 to ADC 6 Feb 28 20:16:30 home kernel: hdac0: tracing via nid 28 Feb 28 20:16:30 home kernel: hdac0: tracing via nid 16 Feb 28 20:16:30 home kernel: hdac0: tracing via nid 18 Feb 28 20:16:30 home kernel: hdac0: tracing via nid 6 Feb 28 20:16:30 home kernel: hdac0: nid 6 returned 1 Feb 28 20:16:30 home kernel: hdac0: nid 18 returned 1 Feb 28 20:16:30 home kernel: hdac0: tracing via nid 23 Feb 28 20:16:30 home kernel: hdac0: tracing via nid 7 Feb 28 20:16:30 home kernel: hdac0: nid 7 busy by association 0 Feb 28 20:16:30 home kernel: hdac0: nid 23 returned 0 Feb 28 20:16:30 home kernel: hdac0: nid 16 returned 1 Feb 28 20:16:30 home kernel: hdac0: nid 28 returned 1 Feb 28 20:16:30 home kernel: hdac0: Pin 28 traced to ADC 6 Feb 28 20:16:30 home kernel: hdac0: Tracing pin 29 to ADC 6 Feb 28 20:16:30 home kernel: hdac0: tracing via nid 29 Feb 28 20:16:30 home kernel: hdac0: tracing via nid 15 Feb 28 20:16:30 home kernel: hdac0: tracing via nid 17 Feb 28 20:16:30 home kernel: hdac0: tracing via nid 18 Feb 28 20:16:30 home kernel: hdac0: tracing via nid 6 Feb 28 20:16:30 home kernel: hdac0: nid 6 returned 1 Feb 28 20:16:30 home kernel: hdac0: nid 18 returned 1 Feb 28 20:16:30 home kernel: hdac0: tracing via nid 19 Feb 28 20:16:30 home kernel: hdac0: tracing via nid 7 Feb 28 20:16:30 home kernel: hdac0: nid 7 busy by association 0 Feb 28 20:16:30 home kernel: hdac0: nid 19 returned 0 Feb 28 20:16:30 home kernel: hdac0: nid 17 returned 1 Feb 28 20:16:30 home kernel: hdac0: nid 15 returned 1 Feb 28 20:16:30 home kernel: hdac0: nid 29 returned 1 Feb 28 20:16:30 home kernel: hdac0: Pin 29 traced to ADC 6 Feb 28 20:16:30 home kernel: hdac0: Tracing pin 31 to ADC 6 Feb 28 20:16:30 home kernel: hdac0: tracing via nid 31 Feb 28 20:16:30 home kernel: hdac0: tracing via nid 15 Feb 28 20:16:30 home kernel: hdac0: tracing via nid 17 Feb 28 20:16:30 home kernel: hdac0: tracing via nid 18 Feb 28 20:16:30 home kernel: hdac0: tracing via nid 6 Feb 28 20:16:30 home kernel: hdac0: nid 6 returned 1 Feb 28 20:16:30 home kernel: hdac0: nid 18 returned 1 Feb 28 20:16:30 home kernel: hdac0: tracing via nid 19 Feb 28 20:16:30 home kernel: hdac0: tracing via nid 7 Feb 28 20:16:30 home kernel: hdac0: nid 7 busy by association 0 Feb 28 20:16:30 home kernel: hdac0: nid 19 returned 0 Feb 28 20:16:30 home kernel: hdac0: nid 17 returned 1 Feb 28 20:16:30 home kernel: hdac0: nid 15 returned 1 Feb 28 20:16:30 home kernel: hdac0: tracing via nid 16 Feb 28 20:16:30 home kernel: hdac0: tracing via nid 18 Feb 28 20:16:30 home kernel: hdac0: tracing via nid 6 Feb 28 20:16:30 home kernel: hdac0: nid 6 returned 1 Feb 28 20:16:30 home kernel: hdac0: nid 18 returned 1 Feb 28 20:16:30 home kernel: hdac0: tracing via nid 23 Feb 28 20:16:30 home kernel: hdac0: tracing via nid 7 Feb 28 20:16:30 home kernel: hdac0: nid 7 busy by association 0 Feb 28 20:16:30 home kernel: hdac0: nid 23 returned 0 Feb 28 20:16:30 home kernel: hdac0: nid 16 returned 1 Feb 28 20:16:30 home kernel: hdac0: nid 31 returned 1 Feb 28 20:16:30 home kernel: hdac0: Pin 31 traced to ADC 6 Feb 28 20:16:30 home kernel: hdac0: Tracing pin 32 to ADC 6 Feb 28 20:16:30 home kernel: hdac0: tracing via nid 32 Feb 28 20:16:30 home kernel: hdac0: tracing via nid 15 Feb 28 20:16:30 home kernel: hdac0: tracing via nid 17 Feb 28 20:16:30 home kernel: hdac0: tracing via nid 18 Feb 28 20:16:30 home kernel: hdac0: tracing via nid 6 Feb 28 20:16:30 home kernel: hdac0: nid 6 returned 1 Feb 28 20:16:30 home kernel: hdac0: nid 18 returned 1 Feb 28 20:16:30 home kernel: hdac0: tracing via nid 19 Feb 28 20:16:30 home kernel: hdac0: tracing via nid 7 Feb 28 20:16:30 home kernel: hdac0: nid 7 busy by association 0 Feb 28 20:16:30 home kernel: hdac0: nid 19 returned 0 Feb 28 20:16:30 home kernel: hdac0: nid 17 returned 1 Feb 28 20:16:30 home kernel: hdac0: nid 15 returned 1 Feb 28 20:16:30 home kernel: hdac0: tracing via nid 16 Feb 28 20:16:30 home kernel: hdac0: tracing via nid 18 Feb 28 20:16:30 home kernel: hdac0: tracing via nid 6 Feb 28 20:16:30 home kernel: hdac0: nid 6 returned 1 Feb 28 20:16:30 home kernel: hdac0: nid 18 returned 1 Feb 28 20:16:30 home kernel: hdac0: tracing via nid 23 Feb 28 20:16:30 home kernel: hdac0: tracing via nid 7 Feb 28 20:16:30 home kernel: hdac0: nid 7 busy by association 0 Feb 28 20:16:30 home kernel: hdac0: nid 23 returned 0 Feb 28 20:16:30 home kernel: hdac0: nid 16 returned 1 Feb 28 20:16:30 home kernel: hdac0: nid 32 returned 1 Feb 28 20:16:30 home kernel: hdac0: Pin 32 traced to ADC 6 Feb 28 20:16:30 home kernel: hdac0: Tracing pin 34 to ADC 6 Feb 28 20:16:30 home kernel: hdac0: tracing via nid 34 Feb 28 20:16:30 home kernel: hdac0: tracing via nid 18 Feb 28 20:16:30 home kernel: hdac0: tracing via nid 6 Feb 28 20:16:30 home kernel: hdac0: nid 6 returned 1 Feb 28 20:16:30 home kernel: hdac0: nid 18 returned 1 Feb 28 20:16:30 home kernel: hdac0: tracing via nid 21 Feb 28 20:16:30 home kernel: hdac0: tracing via nid 7 Feb 28 20:16:30 home kernel: hdac0: nid 7 busy by association 0 Feb 28 20:16:30 home kernel: hdac0: nid 21 returned 0 Feb 28 20:16:30 home kernel: hdac0: nid 34 returned 1 Feb 28 20:16:30 home kernel: hdac0: Pin 34 traced to ADC 6 Feb 28 20:16:30 home kernel: hdac0: Association 2 (8) trace succeeded Feb 28 20:16:30 home kernel: hdac0: Tracing association 3 (15) Feb 28 20:16:30 home kernel: hdac0: Tracing pin 37 with min nid 0 Feb 28 20:16:30 home kernel: hdac0: tracing via nid 37 Feb 28 20:16:30 home kernel: hdac0: tracing via nid 2 Feb 28 20:16:30 home kernel: hdac0: nid 2 returned 2 Feb 28 20:16:30 home kernel: hdac0: nid 37 returned 2 Feb 28 20:16:30 home kernel: hdac0: Pin 37 traced to DAC 2 Feb 28 20:16:30 home kernel: hdac0: Association 3 (15) trace succeeded Feb 28 20:16:30 home kernel: hdac0: Tracing input monitor Feb 28 20:16:30 home kernel: hdac0: Tracing beeper Feb 28 20:16:30 home kernel: hdac0: Tracing nid 25 to out Feb 28 20:16:30 home kernel: hdac0: tracing via nid 25 Feb 28 20:16:30 home kernel: hdac0: tracing via nid 24 Feb 28 20:16:30 home kernel: hdac0: tracing via nid 7 Feb 28 20:16:30 home kernel: hdac0: nid 7 found output association 0 Feb 28 20:16:30 home kernel: hdac0: nid 24 returned 1 Feb 28 20:16:30 home kernel: hdac0: nid 25 returned 1 Feb 28 20:16:30 home kernel: hdac0: nid 25 traced to out Feb 28 20:16:30 home kernel: hdac0: Disabling unassociated widgets... Feb 28 20:16:30 home kernel: hdac0: Disabling unassociated nid 5. Feb 28 20:16:30 home kernel: hdac0: Disabling unassociated nid 8. Feb 28 20:16:30 home kernel: hdac0: Disabling unassociated nid 9. Feb 28 20:16:30 home kernel: hdac0: Disabling unassociated nid 12. Feb 28 20:16:30 home kernel: hdac0: Disabling unassociated nid 13. Feb 28 20:16:30 home kernel: hdac0: Disabling unassociated nid 19. Feb 28 20:16:30 home kernel: hdac0: Disabling unassociated nid 21. Feb 28 20:16:30 home kernel: hdac0: Disabling unassociated nid 23. Feb 28 20:16:30 home kernel: hdac0: Disabling connection to input pin nid 28 conn 0. Feb 28 20:16:30 home kernel: hdac0: Disabling connection to input pin nid 29 conn 0. Feb 28 20:16:30 home kernel: hdac0: Disabling nonselected inputs... Feb 28 20:16:30 home kernel: hdac0: Disabling unselected connection nid 10 conn 0. Feb 28 20:16:30 home kernel: hdac0: Disabling unselected connection nid 10 conn 2. Feb 28 20:16:30 home kernel: hdac0: Disabling unselected connection nid 11 conn 1. Feb 28 20:16:30 home kernel: hdac0: Disabling useless... Feb 28 20:16:30 home kernel: hdac0: Disabling ctl 3 nid 5 cnid -1 due to disabled widget. Feb 28 20:16:30 home kernel: hdac0: Disabling ctl 4 nid 9 cnid -1 due to disabled widget. Feb 28 20:16:30 home kernel: hdac0: Disabling ctl 5 nid 9 cnid 4 due to disabled widget. Feb 28 20:16:30 home kernel: hdac0: Disabling ctl 6 nid 9 cnid 5 due to disabled widget. Feb 28 20:16:30 home kernel: hdac0: Disabling ctl 9 nid 19 cnid -1 due to disabled widget. Feb 28 20:16:30 home kernel: hdac0: Disabling ctl 11 nid 21 cnid -1 due to disabled widget. Feb 28 20:16:30 home kernel: hdac0: Disabling ctl 13 nid 23 cnid -1 due to disabled widget. Feb 28 20:16:30 home kernel: hdac0: Disabling nid 7 connection 1 due to disabled child widget. Feb 28 20:16:30 home kernel: hdac0: Disabling nid 7 connection 2 due to disabled child widget. Feb 28 20:16:30 home kernel: hdac0: Disabling nid 7 connection 4 due to disabled child widget. Feb 28 20:16:30 home kernel: hdac0: Disabling nid 7 connection 6 due to disabled child widget. Feb 28 20:16:30 home kernel: hdac0: Disabling nid 18 connection 6 due to disabled child widget. Feb 28 20:16:30 home kernel: hdac0: Disabling crossassociatement connections... Feb 28 20:16:30 home kernel: hdac0: Disabling crossassociatement connection nid 2 conn 1 cnid 6. Feb 28 20:16:30 home kernel: hdac0: Disabling crossassociatement connection nid 18 conn 5 cnid 7. Feb 28 20:16:30 home kernel: hdac0: Disabling useless... Feb 28 20:16:30 home kernel: hdac0: Binding associations to channels... Feb 28 20:16:30 home kernel: hdac0: Assigning names to signal sources... Feb 28 20:16:30 home kernel: hdac0: Assigning mixers to the tree... Feb 28 20:16:30 home kernel: hdac0: Preparing pin controls... Feb 28 20:16:30 home kernel: hdac0: AFG commit... Feb 28 20:16:30 home kernel: hdac0: HP switch init... Feb 28 20:16:30 home kernel: hdac0: Creating PCM devices... Feb 28 20:16:30 home kernel: hdac0: FG config/quirks: forcestereo ivref50 ivref80 ivref100 ivref Feb 28 20:16:30 home kernel: hdac0: Feb 28 20:16:30 home kernel: hdac0: +-------------------+ Feb 28 20:16:30 home kernel: hdac0: | DUMPING HDA NODES | Feb 28 20:16:30 home kernel: hdac0: +-------------------+ Feb 28 20:16:30 home kernel: hdac0: Feb 28 20:16:30 home kernel: hdac0: Default Parameter Feb 28 20:16:30 home kernel: hdac0: ----------------- Feb 28 20:16:30 home kernel: hdac0: Stream cap: 0x00000001 Feb 28 20:16:30 home kernel: hdac0: PCM Feb 28 20:16:30 home kernel: hdac0: PCM cap: 0x000e007f Feb 28 20:16:30 home kernel: hdac0: 16 20 24 bits, 8 11 16 22 32 44 48 KHz Feb 28 20:16:30 home kernel: hdac0: IN amp: 0x80000000 Feb 28 20:16:30 home kernel: hdac0: OUT amp: 0x80051f1f Feb 28 20:16:30 home kernel: hdac0: Feb 28 20:16:30 home kernel: hdac0: nid: 2 Feb 28 20:16:30 home kernel: hdac0: Name: audio output Feb 28 20:16:30 home kernel: hdac0: Widget cap: 0x00030311 Feb 28 20:16:30 home kernel: hdac0: DIGITAL STEREO Feb 28 20:16:30 home kernel: hdac0: Association: 3 (0x00000001) Feb 28 20:16:30 home kernel: hdac0: OSS: pcm (pcm) Feb 28 20:16:30 home kernel: hdac0: Stream cap: 0x00000005 Feb 28 20:16:30 home kernel: hdac0: AC3 PCM Feb 28 20:16:30 home kernel: hdac0: PCM cap: 0x00020060 Feb 28 20:16:30 home kernel: hdac0: 16 bits, 44 48 KHz Feb 28 20:16:30 home kernel: hdac0: connections: 2 Feb 28 20:16:30 home kernel: hdac0: | Feb 28 20:16:30 home kernel: hdac0: + [DISABLED] <- nid=1 [GHOST!] [UNKNOWN] (selected) Feb 28 20:16:30 home kernel: hdac0: + [DISABLED] <- nid=6 [audio input] Feb 28 20:16:30 home kernel: hdac0: Feb 28 20:16:30 home kernel: hdac0: nid: 3 Feb 28 20:16:30 home kernel: hdac0: Name: audio output Feb 28 20:16:30 home kernel: hdac0: Widget cap: 0x0000044d Feb 28 20:16:30 home kernel: hdac0: PWR PROC STEREO Feb 28 20:16:30 home kernel: hdac0: Association: 0 (0x00000002) Feb 28 20:16:30 home kernel: hdac0: OSS: pcm (pcm) Feb 28 20:16:30 home kernel: hdac0: Stream cap: 0x00000001 Feb 28 20:16:30 home kernel: hdac0: PCM Feb 28 20:16:30 home kernel: hdac0: PCM cap: 0x000e007f Feb 28 20:16:30 home kernel: hdac0: 16 20 24 bits, 8 11 16 22 32 44 48 KHz Feb 28 20:16:30 home kernel: hdac0: Output amp: 0x80051f17 Feb 28 20:16:30 home kernel: hdac0: mute=1 step=31 size=5 offset=23 Feb 28 20:16:30 home kernel: hdac0: Feb 28 20:16:30 home kernel: hdac0: nid: 4 Feb 28 20:16:30 home kernel: hdac0: Name: audio output Feb 28 20:16:30 home kernel: hdac0: Widget cap: 0x0000040d Feb 28 20:16:30 home kernel: hdac0: PWR STEREO Feb 28 20:16:30 home kernel: hdac0: Association: 1 (0x00000002) Feb 28 20:16:30 home kernel: hdac0: OSS: pcm (pcm) Feb 28 20:16:30 home kernel: hdac0: Stream cap: 0x00000001 Feb 28 20:16:30 home kernel: hdac0: PCM Feb 28 20:16:30 home kernel: hdac0: PCM cap: 0x000e007f Feb 28 20:16:30 home kernel: hdac0: 16 20 24 bits, 8 11 16 22 32 44 48 KHz Feb 28 20:16:30 home kernel: hdac0: Output amp: 0x80051f17 Feb 28 20:16:30 home kernel: hdac0: mute=1 step=31 size=5 offset=23 Feb 28 20:16:30 home kernel: hdac0: Feb 28 20:16:30 home kernel: hdac0: nid: 5 [DISABLED] Feb 28 20:16:30 home kernel: hdac0: Name: audio output Feb 28 20:16:30 home kernel: hdac0: Widget cap: 0x0000040d Feb 28 20:16:30 home kernel: hdac0: PWR STEREO Feb 28 20:16:30 home kernel: hdac0: Stream cap: 0x00000001 Feb 28 20:16:30 home kernel: hdac0: PCM Feb 28 20:16:30 home kernel: hdac0: PCM cap: 0x000e007f Feb 28 20:16:30 home kernel: hdac0: 16 20 24 bits, 8 11 16 22 32 44 48 KHz Feb 28 20:16:30 home kernel: hdac0: Output amp: 0x80051f17 Feb 28 20:16:30 home kernel: hdac0: mute=1 step=31 size=5 offset=23 Feb 28 20:16:30 home kernel: hdac0: Feb 28 20:16:30 home kernel: hdac0: nid: 6 Feb 28 20:16:30 home kernel: hdac0: Name: audio input Feb 28 20:16:30 home kernel: hdac0: Widget cap: 0x00100511 Feb 28 20:16:30 home kernel: hdac0: PWR STEREO Feb 28 20:16:30 home kernel: hdac0: Association: 2 (0x0000003e) Feb 28 20:16:30 home kernel: hdac0: Stream cap: 0x00000001 Feb 28 20:16:30 home kernel: hdac0: PCM Feb 28 20:16:30 home kernel: hdac0: PCM cap: 0x0006007f Feb 28 20:16:30 home kernel: hdac0: 16 20 bits, 8 11 16 22 32 44 48 KHz Feb 28 20:16:30 home kernel: hdac0: connections: 1 Feb 28 20:16:30 home kernel: hdac0: | Feb 28 20:16:30 home kernel: hdac0: + <- nid=18 [audio selector] Feb 28 20:16:30 home kernel: hdac0: Feb 28 20:16:30 home kernel: hdac0: nid: 7 Feb 28 20:16:30 home kernel: hdac0: Name: audio mixer Feb 28 20:16:30 home kernel: hdac0: Widget cap: 0x00200101 Feb 28 20:16:30 home kernel: hdac0: STEREO Feb 28 20:16:30 home kernel: hdac0: Association: 0 (0x00000002) Feb 28 20:16:30 home kernel: hdac0: OSS: pcm, speaker Feb 28 20:16:30 home kernel: hdac0: connections: 8 Feb 28 20:16:30 home kernel: hdac0: | Feb 28 20:16:30 home kernel: hdac0: + <- nid=3 [audio output] Feb 28 20:16:30 home kernel: hdac0: + [DISABLED] <- nid=9 [audio mixer] [DISABLED] Feb 28 20:16:30 home kernel: hdac0: + [DISABLED] <- nid=19 [audio selector] [DISABLED] Feb 28 20:16:30 home kernel: hdac0: + [DISABLED] <- nid=20 [audio selector] [DISABLED] Feb 28 20:16:30 home kernel: hdac0: + [DISABLED] <- nid=21 [audio selector] [DISABLED] Feb 28 20:16:30 home kernel: hdac0: + [DISABLED] <- nid=22 [audio selector] [DISABLED] Feb 28 20:16:30 home kernel: hdac0: + [DISABLED] <- nid=23 [audio selector] [DISABLED] Feb 28 20:16:30 home kernel: hdac0: + <- nid=24 [audio selector] Feb 28 20:16:30 home kernel: hdac0: Feb 28 20:16:30 home kernel: hdac0: nid: 8 [DISABLED] Feb 28 20:16:30 home kernel: hdac0: Name: audio mixer Feb 28 20:16:30 home kernel: hdac0: Widget cap: 0x00200100 Feb 28 20:16:30 home kernel: hdac0: connections: 1 Feb 28 20:16:30 home kernel: hdac0: | Feb 28 20:16:30 home kernel: hdac0: + <- nid=7 [audio mixer] Feb 28 20:16:30 home kernel: hdac0: Feb 28 20:16:30 home kernel: hdac0: nid: 9 [DISABLED] Feb 28 20:16:30 home kernel: hdac0: Name: audio mixer Feb 28 20:16:30 home kernel: hdac0: Widget cap: 0x0020010e Feb 28 20:16:30 home kernel: hdac0: Output amp: 0x80000000 Feb 28 20:16:30 home kernel: hdac0: mute=1 step=0 size=0 offset=0 Feb 28 20:16:30 home kernel: hdac0: Input amp: 0x80000000 Feb 28 20:16:30 home kernel: hdac0: mute=1 step=0 size=0 offset=0 Feb 28 20:16:30 home kernel: hdac0: connections: 2 Feb 28 20:16:30 home kernel: hdac0: | Feb 28 20:16:30 home kernel: hdac0: + [DISABLED] <- nid=4 [audio output] Feb 28 20:16:30 home kernel: hdac0: + [DISABLED] <- nid=5 [audio output] [DISABLED] Feb 28 20:16:30 home kernel: hdac0: Feb 28 20:16:30 home kernel: hdac0: nid: 10 Feb 28 20:16:30 home kernel: hdac0: Name: audio selector Feb 28 20:16:30 home kernel: hdac0: Widget cap: 0x00300101 Feb 28 20:16:30 home kernel: hdac0: STEREO Feb 28 20:16:30 home kernel: hdac0: Association: 1 (0x00000002) Feb 28 20:16:30 home kernel: hdac0: OSS: pcm Feb 28 20:16:30 home kernel: hdac0: connections: 3 Feb 28 20:16:30 home kernel: hdac0: | Feb 28 20:16:30 home kernel: hdac0: + [DISABLED] <- nid=7 [audio mixer] Feb 28 20:16:30 home kernel: hdac0: + <- nid=4 [audio output] (selected) Feb 28 20:16:30 home kernel: hdac0: + [DISABLED] <- nid=5 [audio output] [DISABLED] Feb 28 20:16:30 home kernel: hdac0: Feb 28 20:16:30 home kernel: hdac0: nid: 11 Feb 28 20:16:30 home kernel: hdac0: Name: audio selector Feb 28 20:16:30 home kernel: hdac0: Widget cap: 0x00300101 Feb 28 20:16:30 home kernel: hdac0: STEREO Feb 28 20:16:30 home kernel: hdac0: Association: 0 (0x00000002) Feb 28 20:16:30 home kernel: hdac0: OSS: pcm, speaker Feb 28 20:16:30 home kernel: hdac0: connections: 2 Feb 28 20:16:30 home kernel: hdac0: | Feb 28 20:16:30 home kernel: hdac0: + <- nid=7 [audio mixer] (selected) Feb 28 20:16:30 home kernel: hdac0: + [DISABLED] <- nid=4 [audio output] Feb 28 20:16:30 home kernel: hdac0: Feb 28 20:16:30 home kernel: hdac0: nid: 12 [DISABLED] Feb 28 20:16:30 home kernel: hdac0: Name: audio selector Feb 28 20:16:30 home kernel: hdac0: Widget cap: 0x00300101 Feb 28 20:16:30 home kernel: hdac0: STEREO Feb 28 20:16:30 home kernel: hdac0: connections: 2 Feb 28 20:16:30 home kernel: hdac0: | Feb 28 20:16:30 home kernel: hdac0: + <- nid=4 [audio output] (selected) Feb 28 20:16:30 home kernel: hdac0: + <- nid=7 [audio mixer] Feb 28 20:16:30 home kernel: hdac0: Feb 28 20:16:30 home kernel: hdac0: nid: 13 [DISABLED] Feb 28 20:16:30 home kernel: hdac0: Name: audio selector Feb 28 20:16:30 home kernel: hdac0: Widget cap: 0x00300101 Feb 28 20:16:30 home kernel: hdac0: STEREO Feb 28 20:16:30 home kernel: hdac0: connections: 2 Feb 28 20:16:30 home kernel: hdac0: | Feb 28 20:16:30 home kernel: hdac0: + <- nid=5 [audio output] [DISABLED] (selected) Feb 28 20:16:30 home kernel: hdac0: + <- nid=8 [audio mixer] [DISABLED] Feb 28 20:16:30 home kernel: hdac0: Feb 28 20:16:30 home kernel: hdac0: nid: 14 [DISABLED] Feb 28 20:16:30 home kernel: hdac0: Name: audio selector Feb 28 20:16:30 home kernel: hdac0: Widget cap: 0x00300100 Feb 28 20:16:30 home kernel: hdac0: connections: 2 Feb 28 20:16:30 home kernel: hdac0: | Feb 28 20:16:30 home kernel: hdac0: + <- nid=8 [audio mixer] [DISABLED] (selected) Feb 28 20:16:30 home kernel: hdac0: + <- nid=17 [audio selector] Feb 28 20:16:30 home kernel: hdac0: Feb 28 20:16:30 home kernel: hdac0: nid: 15 Feb 28 20:16:30 home kernel: hdac0: Name: audio selector Feb 28 20:16:30 home kernel: hdac0: Widget cap: 0x0030010d Feb 28 20:16:30 home kernel: hdac0: STEREO Feb 28 20:16:30 home kernel: hdac0: Association: 2 (0x0000001c) Feb 28 20:16:30 home kernel: hdac0: OSS: mic, line1, monitor Feb 28 20:16:30 home kernel: hdac0: Output amp: 0x00270300 Feb 28 20:16:30 home kernel: hdac0: mute=0 step=3 size=39 offset=0 Feb 28 20:16:30 home kernel: hdac0: connections: 8 Feb 28 20:16:30 home kernel: hdac0: | Feb 28 20:16:30 home kernel: hdac0: + <- nid=31 [pin: Mic (Pink Jack)] Feb 28 20:16:30 home kernel: hdac0: + <- nid=32 [pin: Line-in (Blue Jack)] Feb 28 20:16:30 home kernel: hdac0: + <- nid=29 [pin: Mic (Pink Jack)] (selected) Feb 28 20:16:30 home kernel: hdac0: + [DISABLED] <- nid=29 [pin: Mic (Pink Jack)] Feb 28 20:16:30 home kernel: hdac0: + [DISABLED] <- nid=39 [audio mixer] [DISABLED] Feb 28 20:16:30 home kernel: hdac0: + [DISABLED] <- nid=40 [audio mixer] [DISABLED] Feb 28 20:16:30 home kernel: hdac0: + [DISABLED] <- nid=41 [audio mixer] [DISABLED] Feb 28 20:16:30 home kernel: hdac0: + [DISABLED] <- nid=42 [audio mixer] [DISABLED] Feb 28 20:16:30 home kernel: hdac0: Feb 28 20:16:30 home kernel: hdac0: nid: 16 Feb 28 20:16:30 home kernel: hdac0: Name: audio selector Feb 28 20:16:30 home kernel: hdac0: Widget cap: 0x00300101 Feb 28 20:16:30 home kernel: hdac0: STEREO Feb 28 20:16:30 home kernel: hdac0: Association: 2 (0x0000001a) Feb 28 20:16:30 home kernel: hdac0: OSS: line, line1, monitor Feb 28 20:16:30 home kernel: hdac0: connections: 3 Feb 28 20:16:30 home kernel: hdac0: | Feb 28 20:16:30 home kernel: hdac0: + <- nid=32 [pin: Line-in (Blue Jack)] Feb 28 20:16:30 home kernel: hdac0: + <- nid=28 [pin: Line-in (Blue Jack)] (selected) Feb 28 20:16:30 home kernel: hdac0: + <- nid=31 [pin: Mic (Pink Jack)] Feb 28 20:16:30 home kernel: hdac0: Feb 28 20:16:30 home kernel: hdac0: nid: 17 Feb 28 20:16:30 home kernel: hdac0: Name: audio selector Feb 28 20:16:30 home kernel: hdac0: Widget cap: 0x00300941 Feb 28 20:16:30 home kernel: hdac0: LRSWAP PROC STEREO Feb 28 20:16:30 home kernel: hdac0: Association: 2 (0x0000001c) Feb 28 20:16:30 home kernel: hdac0: OSS: mic, line1, monitor Feb 28 20:16:30 home kernel: hdac0: connections: 2 Feb 28 20:16:30 home kernel: hdac0: | Feb 28 20:16:30 home kernel: hdac0: + <- nid=15 [audio selector] (selected) Feb 28 20:16:30 home kernel: hdac0: + [DISABLED] <- nid=43 [audio mixer] [DISABLED] Feb 28 20:16:30 home kernel: hdac0: Feb 28 20:16:30 home kernel: hdac0: nid: 18 Feb 28 20:16:30 home kernel: hdac0: Name: audio selector Feb 28 20:16:30 home kernel: hdac0: Widget cap: 0x0030010d Feb 28 20:16:30 home kernel: hdac0: STEREO Feb 28 20:16:30 home kernel: hdac0: Association: 2 (0x0000003e) Feb 28 20:16:30 home kernel: hdac0: OSS: line, mic, cd, line1, monitor Feb 28 20:16:30 home kernel: hdac0: Output amp: 0x80050f00 Feb 28 20:16:30 home kernel: hdac0: mute=1 step=15 size=5 offset=0 Feb 28 20:16:30 home kernel: hdac0: connections: 8 Feb 28 20:16:30 home kernel: hdac0: | Feb 28 20:16:30 home kernel: hdac0: + <- nid=17 [audio selector] Feb 28 20:16:30 home kernel: hdac0: + <- nid=34 [pin: CD (Fixed)] Feb 28 20:16:30 home kernel: hdac0: + [DISABLED] <- nid=0 [GHOST!] [UNKNOWN] Feb 28 20:16:30 home kernel: hdac0: + [DISABLED] <- nid=33 [pin: AUX (None)] [DISABLED] Feb 28 20:16:30 home kernel: hdac0: + <- nid=16 [audio selector] (selected) Feb 28 20:16:30 home kernel: hdac0: + [DISABLED] <- nid=7 [audio mixer] Feb 28 20:16:30 home kernel: hdac0: + [DISABLED] <- nid=8 [audio mixer] [DISABLED] Feb 28 20:16:30 home kernel: hdac0: + [DISABLED] <- nid=35 [pin: Telephony (None)] [DISABLED] Feb 28 20:16:30 home kernel: hdac0: Feb 28 20:16:30 home kernel: hdac0: nid: 19 [DISABLED] Feb 28 20:16:30 home kernel: hdac0: Name: audio selector Feb 28 20:16:30 home kernel: hdac0: Widget cap: 0x0030010d Feb 28 20:16:30 home kernel: hdac0: STEREO Feb 28 20:16:30 home kernel: hdac0: Output amp: 0x80051f17 Feb 28 20:16:30 home kernel: hdac0: mute=1 step=31 size=5 offset=23 Feb 28 20:16:30 home kernel: hdac0: connections: 1 Feb 28 20:16:30 home kernel: hdac0: | Feb 28 20:16:30 home kernel: hdac0: + <- nid=17 [audio selector] Feb 28 20:16:30 home kernel: hdac0: Feb 28 20:16:30 home kernel: hdac0: nid: 20 [DISABLED] Feb 28 20:16:30 home kernel: hdac0: Name: audio selector Feb 28 20:16:30 home kernel: hdac0: Widget cap: 0x0030010c Feb 28 20:16:30 home kernel: hdac0: Output amp: 0x80051f17 Feb 28 20:16:30 home kernel: hdac0: mute=1 step=31 size=5 offset=23 Feb 28 20:16:30 home kernel: hdac0: connections: 1 Feb 28 20:16:30 home kernel: hdac0: | Feb 28 20:16:30 home kernel: hdac0: + [DISABLED] <- nid=35 [pin: Telephony (None)] [DISABLED] Feb 28 20:16:30 home kernel: hdac0: Feb 28 20:16:30 home kernel: hdac0: nid: 21 [DISABLED] Feb 28 20:16:30 home kernel: hdac0: Name: audio selector Feb 28 20:16:30 home kernel: hdac0: Widget cap: 0x0030010d Feb 28 20:16:30 home kernel: hdac0: STEREO Feb 28 20:16:30 home kernel: hdac0: Output amp: 0x80051f17 Feb 28 20:16:30 home kernel: hdac0: mute=1 step=31 size=5 offset=23 Feb 28 20:16:30 home kernel: hdac0: connections: 1 Feb 28 20:16:30 home kernel: hdac0: | Feb 28 20:16:30 home kernel: hdac0: + <- nid=34 [pin: CD (Fixed)] Feb 28 20:16:30 home kernel: hdac0: Feb 28 20:16:30 home kernel: hdac0: nid: 22 [DISABLED] Feb 28 20:16:30 home kernel: hdac0: Name: audio selector Feb 28 20:16:30 home kernel: hdac0: Widget cap: 0x0030010d Feb 28 20:16:30 home kernel: hdac0: STEREO Feb 28 20:16:30 home kernel: hdac0: Output amp: 0x80051f17 Feb 28 20:16:30 home kernel: hdac0: mute=1 step=31 size=5 offset=23 Feb 28 20:16:30 home kernel: hdac0: connections: 1 Feb 28 20:16:30 home kernel: hdac0: | Feb 28 20:16:30 home kernel: hdac0: + [DISABLED] <- nid=33 [pin: AUX (None)] [DISABLED] Feb 28 20:16:30 home kernel: hdac0: Feb 28 20:16:30 home kernel: hdac0: nid: 23 [DISABLED] Feb 28 20:16:30 home kernel: hdac0: Name: audio selector Feb 28 20:16:30 home kernel: hdac0: Widget cap: 0x0030010d Feb 28 20:16:30 home kernel: hdac0: STEREO Feb 28 20:16:30 home kernel: hdac0: Output amp: 0x80051f17 Feb 28 20:16:30 home kernel: hdac0: mute=1 step=31 size=5 offset=23 Feb 28 20:16:30 home kernel: hdac0: connections: 1 Feb 28 20:16:30 home kernel: hdac0: | Feb 28 20:16:30 home kernel: hdac0: + <- nid=16 [audio selector] Feb 28 20:16:30 home kernel: hdac0: Feb 28 20:16:30 home kernel: hdac0: nid: 24 Feb 28 20:16:30 home kernel: hdac0: Name: audio selector Feb 28 20:16:30 home kernel: hdac0: Widget cap: 0x0030010c Feb 28 20:16:30 home kernel: hdac0: Association: -2 (0x00000000) Feb 28 20:16:30 home kernel: hdac0: OSS: speaker Feb 28 20:16:30 home kernel: hdac0: Output amp: 0x800b0f0f Feb 28 20:16:30 home kernel: hdac0: mute=1 step=15 size=11 offset=15 Feb 28 20:16:30 home kernel: hdac0: connections: 2 Feb 28 20:16:30 home kernel: hdac0: | Feb 28 20:16:30 home kernel: hdac0: + <- nid=25 [beep widget] (selected) Feb 28 20:16:30 home kernel: hdac0: + [DISABLED] <- nid=36 [pin: Other (None)] [DISABLED] Feb 28 20:16:30 home kernel: hdac0: Feb 28 20:16:30 home kernel: hdac0: nid: 25 Feb 28 20:16:30 home kernel: hdac0: Name: beep widget Feb 28 20:16:30 home kernel: hdac0: Widget cap: 0x00700000 Feb 28 20:16:30 home kernel: hdac0: Association: -2 (0x00000000) Feb 28 20:16:30 home kernel: hdac0: OSS: speaker (speaker) Feb 28 20:16:30 home kernel: hdac0: Feb 28 20:16:30 home kernel: hdac0: nid: 26 Feb 28 20:16:30 home kernel: hdac0: Name: pin: Headphones (Green Jack) Feb 28 20:16:30 home kernel: hdac0: Widget cap: 0x00400185 Feb 28 20:16:30 home kernel: hdac0: UNSOL STEREO Feb 28 20:16:30 home kernel: hdac0: Association: 1 (0x00000002) Feb 28 20:16:30 home kernel: hdac0: Pin cap: 0x0000001f Feb 28 20:16:30 home kernel: hdac0: ISC TRQD PDC HP OUT Feb 28 20:16:30 home kernel: hdac0: Pin config: 0x02214021 Feb 28 20:16:30 home kernel: hdac0: Pin control: 0x000000c0 HP OUT Feb 28 20:16:30 home kernel: hdac0: Output amp: 0x80051f1f Feb 28 20:16:30 home kernel: hdac0: mute=1 step=31 size=5 offset=31 Feb 28 20:16:30 home kernel: hdac0: connections: 1 Feb 28 20:16:30 home kernel: hdac0: | Feb 28 20:16:30 home kernel: hdac0: + <- nid=10 [audio selector] Feb 28 20:16:30 home kernel: hdac0: Feb 28 20:16:30 home kernel: hdac0: nid: 27 Feb 28 20:16:30 home kernel: hdac0: Name: pin: Line-out (Green Jack) Feb 28 20:16:30 home kernel: hdac0: Widget cap: 0x00400185 Feb 28 20:16:30 home kernel: hdac0: UNSOL STEREO Feb 28 20:16:30 home kernel: hdac0: Association: 0 (0x00000002) Feb 28 20:16:30 home kernel: hdac0: Pin cap: 0x0001001f Feb 28 20:16:30 home kernel: hdac0: ISC TRQD PDC HP OUT EAPD Feb 28 20:16:30 home kernel: hdac0: Pin config: 0x01014011 Feb 28 20:16:30 home kernel: hdac0: Pin control: 0x00000040 OUT Feb 28 20:16:30 home kernel: hdac0: EAPD: 0x00000002 Feb 28 20:16:30 home kernel: hdac0: Output amp: 0x80051f1f Feb 28 20:16:30 home kernel: hdac0: mute=1 step=31 size=5 offset=31 Feb 28 20:16:30 home kernel: hdac0: connections: 1 Feb 28 20:16:30 home kernel: hdac0: | Feb 28 20:16:30 home kernel: hdac0: + <- nid=11 [audio selector] Feb 28 20:16:30 home kernel: hdac0: Feb 28 20:16:30 home kernel: hdac0: nid: 28 Feb 28 20:16:30 home kernel: hdac0: Name: pin: Line-in (Blue Jack) Feb 28 20:16:30 home kernel: hdac0: Widget cap: 0x00400185 Feb 28 20:16:30 home kernel: hdac0: UNSOL STEREO Feb 28 20:16:30 home kernel: hdac0: Association: 2 (0x00000002) Feb 28 20:16:30 home kernel: hdac0: OSS: line (line) Feb 28 20:16:30 home kernel: hdac0: Pin cap: 0x00000037 Feb 28 20:16:30 home kernel: hdac0: ISC TRQD PDC OUT IN Feb 28 20:16:30 home kernel: hdac0: Pin config: 0x01813081 Feb 28 20:16:30 home kernel: hdac0: Pin control: 0x00000020 IN Feb 28 20:16:30 home kernel: hdac0: Output amp: 0x80051f1f Feb 28 20:16:30 home kernel: hdac0: mute=1 step=31 size=5 offset=31 Feb 28 20:16:30 home kernel: hdac0: connections: 1 Feb 28 20:16:30 home kernel: hdac0: | Feb 28 20:16:30 home kernel: hdac0: + [DISABLED] <- nid=12 [audio selector] [DISABLED] Feb 28 20:16:30 home kernel: hdac0: Feb 28 20:16:30 home kernel: hdac0: nid: 29 Feb 28 20:16:30 home kernel: hdac0: Name: pin: Mic (Pink Jack) Feb 28 20:16:30 home kernel: hdac0: Widget cap: 0x00400985 Feb 28 20:16:30 home kernel: hdac0: LRSWAP UNSOL STEREO Feb 28 20:16:30 home kernel: hdac0: Association: 2 (0x00000004) Feb 28 20:16:30 home kernel: hdac0: OSS: mic (mic) Feb 28 20:16:30 home kernel: hdac0: Pin cap: 0x00001737 Feb 28 20:16:30 home kernel: hdac0: ISC TRQD PDC OUT IN VREF[ 50 80 GROUND HIZ ] Feb 28 20:16:30 home kernel: hdac0: Pin config: 0x01a19082 Feb 28 20:16:30 home kernel: hdac0: Pin control: 0x00000024 IN VREFs Feb 28 20:16:30 home kernel: hdac0: Output amp: 0x80051f1f Feb 28 20:16:30 home kernel: hdac0: mute=1 step=31 size=5 offset=31 Feb 28 20:16:30 home kernel: hdac0: connections: 1 Feb 28 20:16:30 home kernel: hdac0: | Feb 28 20:16:30 home kernel: hdac0: + [DISABLED] <- nid=13 [audio selector] [DISABLED] Feb 28 20:16:30 home kernel: hdac0: Feb 28 20:16:30 home kernel: hdac0: nid: 30 [DISABLED] Feb 28 20:16:30 home kernel: hdac0: Name: pin: Speaker (None) Feb 28 20:16:30 home kernel: hdac0: Widget cap: 0x00400104 Feb 28 20:16:30 home kernel: hdac0: Pin cap: 0x00000010 Feb 28 20:16:30 home kernel: hdac0: OUT Feb 28 20:16:30 home kernel: hdac0: Pin config: 0x501700f0 Feb 28 20:16:30 home kernel: hdac0: Pin control: 0x00000000 Feb 28 20:16:30 home kernel: hdac0: Output amp: 0x80051f1f Feb 28 20:16:30 home kernel: hdac0: mute=1 step=31 size=5 offset=31 Feb 28 20:16:30 home kernel: hdac0: connections: 1 Feb 28 20:16:30 home kernel: hdac0: | Feb 28 20:16:30 home kernel: hdac0: + [DISABLED] <- nid=14 [audio selector] [DISABLED] Feb 28 20:16:30 home kernel: hdac0: Feb 28 20:16:30 home kernel: hdac0: nid: 31 Feb 28 20:16:30 home kernel: hdac0: Name: pin: Mic (Pink Jack) Feb 28 20:16:30 home kernel: hdac0: Widget cap: 0x00400081 Feb 28 20:16:30 home kernel: hdac0: UNSOL STEREO Feb 28 20:16:30 home kernel: hdac0: Association: 2 (0x00000008) Feb 28 20:16:30 home kernel: hdac0: OSS: monitor (monitor) Feb 28 20:16:30 home kernel: hdac0: Pin cap: 0x00001727 Feb 28 20:16:30 home kernel: hdac0: ISC TRQD PDC IN VREF[ 50 80 GROUND HIZ ] Feb 28 20:16:30 home kernel: hdac0: Pin config: 0x02a19083 Feb 28 20:16:30 home kernel: hdac0: Pin control: 0x00000024 IN VREFs Feb 28 20:16:30 home kernel: hdac0: Feb 28 20:16:30 home kernel: hdac0: nid: 32 Feb 28 20:16:30 home kernel: hdac0: Name: pin: Line-in (Blue Jack) Feb 28 20:16:30 home kernel: hdac0: Widget cap: 0x00400081 Feb 28 20:16:30 home kernel: hdac0: UNSOL STEREO Feb 28 20:16:30 home kernel: hdac0: Association: 2 (0x00000010) Feb 28 20:16:30 home kernel: hdac0: OSS: line1 (line1) Feb 28 20:16:30 home kernel: hdac0: Pin cap: 0x00001727 Feb 28 20:16:30 home kernel: hdac0: ISC TRQD PDC IN VREF[ 50 80 GROUND HIZ ] Feb 28 20:16:30 home kernel: hdac0: Pin config: 0x01813084 Feb 28 20:16:30 home kernel: hdac0: Pin control: 0x00000024 IN VREFs Feb 28 20:16:30 home kernel: hdac0: Feb 28 20:16:30 home kernel: hdac0: nid: 33 [DISABLED] Feb 28 20:16:30 home kernel: hdac0: Name: pin: AUX (None) Feb 28 20:16:30 home kernel: hdac0: Widget cap: 0x00400081 Feb 28 20:16:30 home kernel: hdac0: UNSOL STEREO Feb 28 20:16:30 home kernel: hdac0: Pin cap: 0x00000027 Feb 28 20:16:30 home kernel: hdac0: ISC TRQD PDC IN Feb 28 20:16:30 home kernel: hdac0: Pin config: 0x509700f0 Feb 28 20:16:30 home kernel: hdac0: Pin control: 0x00000000 Feb 28 20:16:30 home kernel: hdac0: Feb 28 20:16:30 home kernel: hdac0: nid: 34 Feb 28 20:16:30 home kernel: hdac0: Name: pin: CD (Fixed) Feb 28 20:16:30 home kernel: hdac0: Widget cap: 0x00400001 Feb 28 20:16:30 home kernel: hdac0: STEREO Feb 28 20:16:30 home kernel: hdac0: Association: 2 (0x00000020) Feb 28 20:16:30 home kernel: hdac0: OSS: cd (cd) Feb 28 20:16:30 home kernel: hdac0: Pin cap: 0x00000020 Feb 28 20:16:30 home kernel: hdac0: IN Feb 28 20:16:30 home kernel: hdac0: Pin config: 0x99331085 Feb 28 20:16:30 home kernel: hdac0: Pin control: 0x00000020 IN Feb 28 20:16:30 home kernel: hdac0: Feb 28 20:16:30 home kernel: hdac0: nid: 35 [DISABLED] Feb 28 20:16:30 home kernel: hdac0: Name: pin: Telephony (None) Feb 28 20:16:30 home kernel: hdac0: Widget cap: 0x00400000 Feb 28 20:16:30 home kernel: hdac0: Pin cap: 0x00000020 Feb 28 20:16:30 home kernel: hdac0: IN Feb 28 20:16:30 home kernel: hdac0: Pin config: 0x50b700f0 Feb 28 20:16:30 home kernel: hdac0: Pin control: 0x00000000 Feb 28 20:16:30 home kernel: hdac0: Feb 28 20:16:30 home kernel: hdac0: nid: 36 [DISABLED] Feb 28 20:16:30 home kernel: hdac0: Name: pin: Other (None) Feb 28 20:16:30 home kernel: hdac0: Widget cap: 0x00400000 Feb 28 20:16:30 home kernel: hdac0: Pin cap: 0x00000020 Feb 28 20:16:30 home kernel: hdac0: IN Feb 28 20:16:30 home kernel: hdac0: Pin config: 0x50f70086 Feb 28 20:16:30 home kernel: hdac0: Pin control: 0x00000000 Feb 28 20:16:30 home kernel: hdac0: Feb 28 20:16:30 home kernel: hdac0: nid: 37 Feb 28 20:16:30 home kernel: hdac0: Name: pin: SPDIF-out (Jack) Feb 28 20:16:30 home kernel: hdac0: Widget cap: 0x00400301 Feb 28 20:16:30 home kernel: hdac0: DIGITAL STEREO Feb 28 20:16:30 home kernel: hdac0: Association: 3 (0x00000001) Feb 28 20:16:30 home kernel: hdac0: Pin cap: 0x00000010 Feb 28 20:16:30 home kernel: hdac0: OUT Feb 28 20:16:30 home kernel: hdac0: Pin config: 0x0145f0f0 Feb 28 20:16:30 home kernel: hdac0: Pin control: 0x00000040 OUT Feb 28 20:16:30 home kernel: hdac0: connections: 1 Feb 28 20:16:30 home kernel: hdac0: | Feb 28 20:16:30 home kernel: hdac0: + <- nid=2 [audio output] Feb 28 20:16:30 home kernel: hdac0: Feb 28 20:16:30 home kernel: hdac0: nid: 38 [DISABLED] Feb 28 20:16:30 home kernel: hdac0: Name: power widget Feb 28 20:16:30 home kernel: hdac0: Widget cap: 0x00500500 Feb 28 20:16:30 home kernel: hdac0: PWR Feb 28 20:16:30 home kernel: hdac0: connections: 8 Feb 28 20:16:30 home kernel: hdac0: | Feb 28 20:16:30 home kernel: hdac0: + <- nid=7 [audio mixer] (selected) Feb 28 20:16:30 home kernel: hdac0: + <- nid=8 [audio mixer] [DISABLED] Feb 28 20:16:30 home kernel: hdac0: + <- nid=19 [audio selector] [DISABLED] Feb 28 20:16:30 home kernel: hdac0: + <- nid=20 [audio selector] [DISABLED] Feb 28 20:16:30 home kernel: hdac0: + <- nid=21 [audio selector] [DISABLED] Feb 28 20:16:30 home kernel: hdac0: + <- nid=22 [audio selector] [DISABLED] Feb 28 20:16:30 home kernel: hdac0: + <- nid=23 [audio selector] [DISABLED] Feb 28 20:16:30 home kernel: hdac0: + <- nid=24 [audio selector] Feb 28 20:16:30 home kernel: hdac0: Feb 28 20:16:30 home kernel: hdac0: nid: 39 [DISABLED] Feb 28 20:16:30 home kernel: hdac0: Name: audio mixer Feb 28 20:16:30 home kernel: hdac0: Widget cap: 0x00200101 Feb 28 20:16:30 home kernel: hdac0: STEREO Feb 28 20:16:30 home kernel: hdac0: connections: 2 Feb 28 20:16:30 home kernel: hdac0: | Feb 28 20:16:30 home kernel: hdac0: + <- nid=31 [pin: Mic (Pink Jack)] Feb 28 20:16:30 home kernel: hdac0: + <- nid=29 [pin: Mic (Pink Jack)] Feb 28 20:16:30 home kernel: hdac0: Feb 28 20:16:30 home kernel: hdac0: nid: 40 [DISABLED] Feb 28 20:16:30 home kernel: hdac0: Name: audio mixer Feb 28 20:16:30 home kernel: hdac0: Widget cap: 0x00200101 Feb 28 20:16:30 home kernel: hdac0: STEREO Feb 28 20:16:30 home kernel: hdac0: connections: 2 Feb 28 20:16:30 home kernel: hdac0: | Feb 28 20:16:30 home kernel: hdac0: + <- nid=31 [pin: Mic (Pink Jack)] Feb 28 20:16:30 home kernel: hdac0: + <- nid=32 [pin: Line-in (Blue Jack)] Feb 28 20:16:30 home kernel: hdac0: Feb 28 20:16:30 home kernel: hdac0: nid: 41 [DISABLED] Feb 28 20:16:30 home kernel: hdac0: Name: audio mixer Feb 28 20:16:30 home kernel: hdac0: Widget cap: 0x00200101 Feb 28 20:16:30 home kernel: hdac0: STEREO Feb 28 20:16:30 home kernel: hdac0: connections: 2 Feb 28 20:16:30 home kernel: hdac0: | Feb 28 20:16:30 home kernel: hdac0: + <- nid=29 [pin: Mic (Pink Jack)] Feb 28 20:16:30 home kernel: hdac0: + <- nid=32 [pin: Line-in (Blue Jack)] Feb 28 20:16:30 home kernel: hdac0: Feb 28 20:16:30 home kernel: hdac0: nid: 42 [DISABLED] Feb 28 20:16:30 home kernel: hdac0: Name: audio mixer Feb 28 20:16:30 home kernel: hdac0: Widget cap: 0x00200101 Feb 28 20:16:30 home kernel: hdac0: STEREO Feb 28 20:16:30 home kernel: hdac0: connections: 3 Feb 28 20:16:30 home kernel: hdac0: | Feb 28 20:16:30 home kernel: hdac0: + <- nid=31 [pin: Mic (Pink Jack)] Feb 28 20:16:30 home kernel: hdac0: + <- nid=29 [pin: Mic (Pink Jack)] Feb 28 20:16:30 home kernel: hdac0: + <- nid=32 [pin: Line-in (Blue Jack)] Feb 28 20:16:30 home kernel: hdac0: Feb 28 20:16:30 home kernel: hdac0: nid: 43 [DISABLED] Feb 28 20:16:30 home kernel: hdac0: Name: audio mixer Feb 28 20:16:30 home kernel: hdac0: Widget cap: 0x00200100 Feb 28 20:16:30 home kernel: hdac0: connections: 1 Feb 28 20:16:30 home kernel: hdac0: | Feb 28 20:16:30 home kernel: hdac0: + <- nid=15 [audio selector] Feb 28 20:16:30 home kernel: hdac0: Feb 28 20:16:30 home kernel: hdac0: +------------------------+ Feb 28 20:16:30 home kernel: hdac0: | DUMPING HDA AMPLIFIERS | Feb 28 20:16:30 home kernel: hdac0: +------------------------+ Feb 28 20:16:30 home kernel: hdac0: Feb 28 20:16:30 home kernel: hdac0: 1: nid 3 out (out) index 0 ossmask=0x00000010 Feb 28 20:16:30 home kernel: hdac0: mute: 1 step: 31 size: 5 off: 23 Feb 28 20:16:30 home kernel: hdac0: 2: nid 4 out (out) index 0 ossmask=0x00000010 Feb 28 20:16:30 home kernel: hdac0: mute: 1 step: 31 size: 5 off: 23 Feb 28 20:16:30 home kernel: hdac0: 3: nid 5 out (out) index 0 ossmask=0x00000000 Feb 28 20:16:30 home kernel: hdac0: mute: 1 step: 31 size: 5 off: 23 [DISABLED] Feb 28 20:16:30 home kernel: hdac0: 4: nid 9 out (out) index 0 ossmask=0x00000000 Feb 28 20:16:30 home kernel: hdac0: mute: 1 step: 0 size: 0 off: 0 [DISABLED] Feb 28 20:16:30 home kernel: hdac0: 5: nid 9 in (in ) index 0 cnid 4 ossmask=0x00000000 Feb 28 20:16:30 home kernel: hdac0: mute: 1 step: 0 size: 0 off: 0 [DISABLED] Feb 28 20:16:30 home kernel: hdac0: 6: nid 9 in (in ) index 1 cnid 5 ossmask=0x00000000 Feb 28 20:16:30 home kernel: hdac0: mute: 1 step: 0 size: 0 off: 0 [DISABLED] Feb 28 20:16:30 home kernel: hdac0: 7: nid 15 out (out) index 0 ossmask=0x00000800 Feb 28 20:16:30 home kernel: hdac0: mute: 0 step: 3 size: 39 off: 0 Feb 28 20:16:30 home kernel: hdac0: 8: nid 18 out (out) index 0 ossmask=0x00000800 Feb 28 20:16:30 home kernel: hdac0: mute: 1 step: 15 size: 5 off: 0 Feb 28 20:16:30 home kernel: hdac0: 9: nid 19 out (out) index 0 ossmask=0x00000000 Feb 28 20:16:30 home kernel: hdac0: mute: 1 step: 31 size: 5 off: 23 [DISABLED] Feb 28 20:16:30 home kernel: hdac0: 10: nid 20 out (out) index 0 ossmask=0x00000000 Feb 28 20:16:30 home kernel: hdac0: mute: 1 step: 31 size: 5 off: 23 [DISABLED] Feb 28 20:16:30 home kernel: hdac0: 11: nid 21 out (out) index 0 ossmask=0x00000000 Feb 28 20:16:30 home kernel: hdac0: mute: 1 step: 31 size: 5 off: 23 [DISABLED] Feb 28 20:16:30 home kernel: hdac0: 12: nid 22 out (out) index 0 ossmask=0x00000000 Feb 28 20:16:30 home kernel: hdac0: mute: 1 step: 31 size: 5 off: 23 [DISABLED] Feb 28 20:16:30 home kernel: hdac0: 13: nid 23 out (out) index 0 ossmask=0x00000000 Feb 28 20:16:30 home kernel: hdac0: mute: 1 step: 31 size: 5 off: 23 [DISABLED] Feb 28 20:16:30 home kernel: hdac0: 14: nid 24 out (out) index 0 ossmask=0x00000020 Feb 28 20:16:30 home kernel: hdac0: mute: 1 step: 15 size: 11 off: 15 Feb 28 20:16:30 home kernel: hdac0: 15: nid 26 in (out) index 0 ossmask=0x00000001 Feb 28 20:16:30 home kernel: hdac0: mute: 1 step: 31 size: 5 off: 31 Feb 28 20:16:30 home kernel: hdac0: 16: nid 27 in (out) index 0 ossmask=0x00000001 Feb 28 20:16:30 home kernel: hdac0: mute: 1 step: 31 size: 5 off: 31 Feb 28 20:16:30 home kernel: hdac0: 17: nid 28 in (out) index 0 ossmask=0x00000000 Feb 28 20:16:30 home kernel: hdac0: mute: 1 step: 31 size: 5 off: 31 [DISABLED] Feb 28 20:16:30 home kernel: hdac0: 18: nid 29 in (out) index 0 ossmask=0x00000000 Feb 28 20:16:30 home kernel: hdac0: mute: 1 step: 31 size: 5 off: 31 [DISABLED] Feb 28 20:16:30 home kernel: hdac0: 19: nid 30 in (out) index 0 ossmask=0x00000000 Feb 28 20:16:30 home kernel: hdac0: mute: 1 step: 31 size: 5 off: 31 [DISABLED] Feb 28 20:16:30 home kernel: hdac0: Feb 28 20:16:30 home kernel: pcm0: at cad 0 nid 1 on hdac0 Feb 28 20:16:30 home kernel: pcm0: +--------------------------------------+ Feb 28 20:16:30 home kernel: pcm0: | DUMPING PCM Playback/Record Channels | Feb 28 20:16:30 home kernel: pcm0: +--------------------------------------+ Feb 28 20:16:30 home kernel: pcm0: Feb 28 20:16:30 home kernel: pcm0: Playback: Feb 28 20:16:30 home kernel: pcm0: Feb 28 20:16:30 home kernel: pcm0: Stream cap: 0x00000001 Feb 28 20:16:30 home kernel: pcm0: PCM Feb 28 20:16:30 home kernel: pcm0: PCM cap: 0x000e007f Feb 28 20:16:30 home kernel: pcm0: 16 20 24 bits, 8 11 16 22 32 44 48 KHz Feb 28 20:16:30 home kernel: pcm0: DAC: 3 Feb 28 20:16:30 home kernel: pcm0: Feb 28 20:16:30 home kernel: pcm0: Record: Feb 28 20:16:30 home kernel: pcm0: Feb 28 20:16:30 home kernel: pcm0: Stream cap: 0x00000001 Feb 28 20:16:30 home kernel: pcm0: PCM Feb 28 20:16:30 home kernel: pcm0: PCM cap: 0x0006007f Feb 28 20:16:30 home kernel: pcm0: 16 20 bits, 8 11 16 22 32 44 48 KHz Feb 28 20:16:30 home kernel: pcm0: ADC: 6 Feb 28 20:16:30 home kernel: pcm0: Feb 28 20:16:30 home kernel: pcm0: +--------------------------------+ Feb 28 20:16:30 home kernel: pcm0: | DUMPING Playback/Record Pathes | Feb 28 20:16:30 home kernel: pcm0: +--------------------------------+ Feb 28 20:16:30 home kernel: pcm0: Feb 28 20:16:30 home kernel: pcm0: Playback: Feb 28 20:16:30 home kernel: pcm0: Feb 28 20:16:30 home kernel: pcm0: nid=27 [pin: Line-out (Green Jack)] Feb 28 20:16:30 home kernel: pcm0: | Feb 28 20:16:30 home kernel: pcm0: + <- nid=11 [audio selector] [src: pcm, speaker] Feb 28 20:16:30 home kernel: pcm0: | Feb 28 20:16:30 home kernel: pcm0: + <- nid=7 [audio mixer] [src: pcm, speaker] Feb 28 20:16:30 home kernel: pcm0: | Feb 28 20:16:30 home kernel: pcm0: + <- nid=3 [audio output] [src: pcm] Feb 28 20:16:30 home kernel: pcm0: + <- nid=24 [audio selector] [src: speaker] Feb 28 20:16:30 home kernel: pcm0: | Feb 28 20:16:30 home kernel: pcm0: + <- nid=25 [beep widget] [src: speaker] Feb 28 20:16:30 home kernel: pcm0: Feb 28 20:16:30 home kernel: pcm0: Record: Feb 28 20:16:30 home kernel: pcm0: Feb 28 20:16:30 home kernel: pcm0: nid=6 [audio input] Feb 28 20:16:30 home kernel: pcm0: | Feb 28 20:16:30 home kernel: pcm0: + <- nid=18 [audio selector] [src: line, mic, cd, line1, monitor] Feb 28 20:16:30 home kernel: pcm0: | Feb 28 20:16:30 home kernel: pcm0: + <- nid=17 [audio selector] [src: mic, line1, monitor] Feb 28 20:16:30 home kernel: pcm0: | Feb 28 20:16:30 home kernel: pcm0: + <- nid=15 [audio selector] [src: mic, line1, monitor] Feb 28 20:16:30 home kernel: pcm0: | Feb 28 20:16:30 home kernel: pcm0: + <- nid=31 [pin: Mic (Pink Jack)] [src: monitor] Feb 28 20:16:30 home kernel: pcm0: + <- nid=32 [pin: Line-in (Blue Jack)] [src: line1] Feb 28 20:16:30 home kernel: pcm0: + <- nid=29 [pin: Mic (Pink Jack)] [src: mic] Feb 28 20:16:30 home kernel: pcm0: + <- nid=34 [pin: CD (Fixed)] [src: cd] Feb 28 20:16:30 home kernel: pcm0: + <- nid=16 [audio selector] [src: line, line1, monitor] Feb 28 20:16:30 home kernel: pcm0: | Feb 28 20:16:30 home kernel: pcm0: + <- nid=32 [pin: Line-in (Blue Jack)] [src: line1] Feb 28 20:16:30 home kernel: pcm0: + <- nid=28 [pin: Line-in (Blue Jack)] [src: line] Feb 28 20:16:30 home kernel: pcm0: + <- nid=31 [pin: Mic (Pink Jack)] [src: monitor] Feb 28 20:16:30 home kernel: pcm0: Feb 28 20:16:30 home kernel: pcm0: +-------------------------+ Feb 28 20:16:30 home kernel: pcm0: | DUMPING Volume Controls | Feb 28 20:16:30 home kernel: pcm0: +-------------------------+ Feb 28 20:16:30 home kernel: pcm0: Feb 28 20:16:30 home kernel: pcm0: Master Volume (OSS: vol) Feb 28 20:16:30 home kernel: pcm0: | Feb 28 20:16:30 home kernel: pcm0: +- ctl 16 (nid 27 in ): -46/0dB (32 steps) + mute Feb 28 20:16:30 home kernel: pcm0: Feb 28 20:16:30 home kernel: pcm0: PCM Volume (OSS: pcm) Feb 28 20:16:30 home kernel: pcm0: | Feb 28 20:16:30 home kernel: pcm0: +- ctl 1 (nid 3 out): -34/12dB (32 steps) + mute Feb 28 20:16:30 home kernel: pcm0: Feb 28 20:16:30 home kernel: pcm0: Speaker/Beep Volume (OSS: speaker) Feb 28 20:16:30 home kernel: pcm0: | Feb 28 20:16:30 home kernel: pcm0: +- ctl 14 (nid 24 out): -45/0dB (16 steps) + mute Feb 28 20:16:30 home kernel: pcm0: Feb 28 20:16:30 home kernel: pcm0: Recording Level (OSS: rec) Feb 28 20:16:30 home kernel: pcm0: | Feb 28 20:16:30 home kernel: pcm0: +- ctl 7 (nid 15 out): 0/30dB (4 steps) Feb 28 20:16:30 home kernel: pcm0: +- ctl 8 (nid 18 out): 0/22dB (16 steps) + mute Feb 28 20:16:30 home kernel: pcm0: Feb 28 20:16:30 home kernel: pcm0: OSS mixer initialization... Feb 28 20:16:30 home kernel: pcm0: Recsel (mic): nid 15 source 2 select Feb 28 20:16:30 home kernel: pcm0: Recsel (mic): nid 17 source 0 select Feb 28 20:16:30 home kernel: pcm0: Recsel (mic): nid 18 source 0 select Feb 28 20:16:30 home kernel: pcm0: Mixer "vol": Feb 28 20:16:30 home kernel: pcm0: Mixer "pcm": Feb 28 20:16:30 home kernel: pcm0: Mixer "speaker": Feb 28 20:16:30 home kernel: pcm0: Mixer "rec": Feb 28 20:16:30 home kernel: pcm0: Mixer "ogain": Feb 28 20:16:30 home kernel: pcm0: Registering PCM channels... Feb 28 20:16:30 home kernel: pcm0: clone manager: deadline=750ms flags=0x8000001e Feb 28 20:16:30 home kernel: sndbuf_resize(): b=0xc50c6b00 0 -> 0xc5074000 [0 -> 4096 : 4096] Feb 28 20:16:30 home kernel: hdac0: hdac_dma_alloc: size=4096 -> roundsz=4096 Feb 28 20:16:30 home kernel: pcm0: sndbuf_setmap 2250000, 4000; 0xe5137000 -> 2250000 Feb 28 20:16:30 home kernel: sndbuf_resize(): b=0xc50c6800 0 -> 0xc50e0000 [0 -> 16384 : 16384] Feb 28 20:16:30 home kernel: hdac0: hdac_dma_alloc: size=4096 -> roundsz=4096 Feb 28 20:16:30 home kernel: pcm0: sndbuf_setmap 2260000, 4000; 0xe5147000 -> 2260000 Feb 28 20:16:30 home kernel: sndbuf_resize(): b=0xc50c6500 0 -> 0xc50e4000 [0 -> 16384 : 16384] Feb 28 20:16:30 home kernel: sndbuf_resize(): b=0xc50c6800 16384 [16384] NOCHANGE Feb 28 20:16:30 home kernel: sndbuf_remalloc(): b=0xc50c6700 0 -> 4096 [1024] Feb 28 20:16:30 home kernel: chn_resizebuf: PCMDIR_PLAY (hardware) timeout=32 b[1024/512/2] bs[1024/512/2] limit=0 Feb 28 20:16:30 home last message repeated 2 times Feb 28 20:16:30 home kernel: sndbuf_resize(): b=0xc50c6800 16384 [1024] NOCHANGE Feb 28 20:16:30 home kernel: sndbuf_remalloc(): b=0xc50c6700 4096 [1024] NOCHANGE Feb 28 20:16:30 home kernel: chn_resizebuf: PCMDIR_PLAY (hardware) timeout=21 b[4096/2048/2] bs[4096/2048/2] limit=0 Feb 28 20:16:30 home kernel: sndbuf_resize(): b=0xc50c6500 16384 [16384] NOCHANGE Feb 28 20:16:30 home kernel: sndbuf_remalloc(): b=0xc50c6400 0 -> 4096 [1024] Feb 28 20:16:30 home kernel: chn_resizebuf: PCMDIR_REC (hardware) timeout=32 b[1024/512/2] bs[1024/512/2] limit=0 Feb 28 20:16:30 home last message repeated 2 times Feb 28 20:16:30 home kernel: sndbuf_resize(): b=0xc50c6500 16384 [1024] NOCHANGE Feb 28 20:16:30 home kernel: sndbuf_remalloc(): b=0xc50c6400 4096 [1024] NOCHANGE Feb 28 20:16:30 home kernel: chn_resizebuf: PCMDIR_REC (hardware) timeout=21 b[4096/2048/2] bs[4096/2048/2] limit=0 Feb 28 20:16:30 home kernel: pcm1: at cad 0 nid 1 on hdac0 Feb 28 20:16:30 home kernel: pcm1: +--------------------------------------+ Feb 28 20:16:30 home kernel: pcm1: | DUMPING PCM Playback/Record Channels | Feb 28 20:16:30 home kernel: pcm1: +--------------------------------------+ Feb 28 20:16:30 home kernel: pcm1: Feb 28 20:16:30 home kernel: pcm1: Playback: Feb 28 20:16:30 home kernel: pcm1: Feb 28 20:16:30 home kernel: pcm1: Stream cap: 0x00000001 Feb 28 20:16:30 home kernel: pcm1: PCM Feb 28 20:16:30 home kernel: pcm1: PCM cap: 0x000e007f Feb 28 20:16:30 home kernel: pcm1: 16 20 24 bits, 8 11 16 22 32 44 48 KHz Feb 28 20:16:30 home kernel: pcm1: DAC: 4 Feb 28 20:16:30 home kernel: pcm1: Feb 28 20:16:30 home kernel: pcm1: +--------------------------------+ Feb 28 20:16:30 home kernel: pcm1: | DUMPING Playback/Record Pathes | Feb 28 20:16:30 home kernel: pcm1: +--------------------------------+ Feb 28 20:16:30 home kernel: pcm1: Feb 28 20:16:30 home kernel: pcm1: Playback: Feb 28 20:16:30 home kernel: pcm1: Feb 28 20:16:30 home kernel: pcm1: nid=26 [pin: Headphones (Green Jack)] Feb 28 20:16:30 home kernel: pcm1: | Feb 28 20:16:30 home kernel: pcm1: + <- nid=10 [audio selector] [src: pcm] Feb 28 20:16:30 home kernel: pcm1: | Feb 28 20:16:30 home kernel: pcm1: + <- nid=4 [audio output] [src: pcm] Feb 28 20:16:30 home kernel: pcm1: Feb 28 20:16:30 home kernel: pcm1: +-------------------------+ Feb 28 20:16:30 home kernel: pcm1: | DUMPING Volume Controls | Feb 28 20:16:30 home kernel: pcm1: +-------------------------+ Feb 28 20:16:30 home kernel: pcm1: Feb 28 20:16:30 home kernel: pcm1: Master Volume (OSS: vol) Feb 28 20:16:30 home kernel: pcm1: | Feb 28 20:16:30 home kernel: pcm1: +- ctl 15 (nid 26 in ): -46/0dB (32 steps) + mute Feb 28 20:16:30 home kernel: pcm1: Feb 28 20:16:30 home kernel: pcm1: PCM Volume (OSS: pcm) Feb 28 20:16:30 home kernel: pcm1: | Feb 28 20:16:30 home kernel: pcm1: +- ctl 2 (nid 4 out): -34/12dB (32 steps) + mute Feb 28 20:16:30 home kernel: pcm1: Feb 28 20:16:30 home kernel: pcm1: OSS mixer initialization... Feb 28 20:16:30 home kernel: pcm1: Mixer "vol": Feb 28 20:16:30 home kernel: pcm1: Mixer "pcm": Feb 28 20:16:30 home kernel: pcm1: Registering PCM channels... Feb 28 20:16:30 home kernel: pcm1: clone manager: deadline=750ms flags=0x8000001e Feb 28 20:16:30 home kernel: sndbuf_resize(): b=0xc50c5a00 0 -> 0xc5104000 [0 -> 4096 : 4096] Feb 28 20:16:30 home kernel: hdac0: hdac_dma_alloc: size=4096 -> roundsz=4096 Feb 28 20:16:30 home kernel: pcm1: sndbuf_setmap 2270000, 4000; 0xe5157000 -> 2270000 Feb 28 20:16:30 home kernel: sndbuf_resize(): b=0xc50c5700 0 -> 0xc510b000 [0 -> 16384 : 16384] Feb 28 20:16:30 home kernel: sndbuf_resize(): b=0xc50c5700 16384 [16384] NOCHANGE Feb 28 20:16:30 home kernel: sndbuf_remalloc(): b=0xc50c5600 0 -> 4096 [1024] Feb 28 20:16:30 home kernel: chn_resizebuf: PCMDIR_PLAY (hardware) timeout=32 b[1024/512/2] bs[1024/512/2] limit=0 Feb 28 20:16:30 home last message repeated 2 times Feb 28 20:16:30 home kernel: sndbuf_resize(): b=0xc50c5700 16384 [1024] NOCHANGE Feb 28 20:16:30 home kernel: sndbuf_remalloc(): b=0xc50c5600 4096 [1024] NOCHANGE Feb 28 20:16:30 home kernel: chn_resizebuf: PCMDIR_PLAY (hardware) timeout=21 b[4096/2048/2] bs[4096/2048/2] limit=0 Feb 28 20:16:30 home kernel: pcm2: at cad 0 nid 1 on hdac0 Feb 28 20:16:30 home kernel: pcm2: +--------------------------------------+ Feb 28 20:16:30 home kernel: pcm2: | DUMPING PCM Playback/Record Channels | Feb 28 20:16:30 home kernel: pcm2: +--------------------------------------+ Feb 28 20:16:30 home kernel: pcm2: Feb 28 20:16:30 home kernel: pcm2: Playback: Feb 28 20:16:30 home kernel: pcm2: Feb 28 20:16:30 home kernel: pcm2: Stream cap: 0x00000005 Feb 28 20:16:30 home kernel: pcm2: AC3 PCM Feb 28 20:16:30 home kernel: pcm2: PCM cap: 0x00020060 Feb 28 20:16:30 home kernel: pcm2: 16 bits, 44 48 KHz Feb 28 20:16:30 home kernel: pcm2: DAC: 2 Feb 28 20:16:30 home kernel: pcm2: Feb 28 20:16:30 home kernel: pcm2: +--------------------------------+ Feb 28 20:16:30 home kernel: pcm2: | DUMPING Playback/Record Pathes | Feb 28 20:16:30 home kernel: pcm2: +--------------------------------+ Feb 28 20:16:30 home kernel: pcm2: Feb 28 20:16:30 home kernel: pcm2: Playback: Feb 28 20:16:30 home kernel: pcm2: Feb 28 20:16:30 home kernel: pcm2: nid=37 [pin: SPDIF-out (Jack)] Feb 28 20:16:30 home kernel: pcm2: | Feb 28 20:16:30 home kernel: pcm2: + <- nid=2 [audio output] [src: pcm] Feb 28 20:16:30 home kernel: pcm2: Feb 28 20:16:30 home kernel: pcm2: +-------------------------+ Feb 28 20:16:30 home kernel: pcm2: | DUMPING Volume Controls | Feb 28 20:16:30 home kernel: pcm2: +-------------------------+ Feb 28 20:16:30 home kernel: pcm2: Feb 28 20:16:30 home kernel: pcm2: OSS mixer initialization... Feb 28 20:16:30 home kernel: pcm2: Registering PCM channels... Feb 28 20:16:30 home kernel: pcm2: clone manager: deadline=750ms flags=0x8000001e Feb 28 20:16:30 home kernel: sndbuf_resize(): b=0xc50c5000 0 -> 0xc50fe000 [0 -> 4096 : 4096] Feb 28 20:16:30 home kernel: hdac0: hdac_dma_alloc: size=4096 -> roundsz=4096 Feb 28 20:16:30 home kernel: pcm2: sndbuf_setmap 2280000, 4000; 0xe5167000 -> 2280000 Feb 28 20:16:30 home kernel: sndbuf_resize(): b=0xc4f09c00 0 -> 0xc5113000 [0 -> 16384 : 16384] Feb 28 20:16:30 home kernel: sndbuf_resize(): b=0xc4f09c00 16384 [16384] NOCHANGE Feb 28 20:16:30 home kernel: sndbuf_remalloc(): b=0xc5112300 0 -> 4096 [4096] Feb 28 20:16:30 home kernel: chn_resizebuf: PCMDIR_PLAY (hardware) timeout=23 b[4096/2048/2] bs[4096/2048/2] limit=0 Feb 28 20:16:30 home last message repeated 2 times Feb 28 20:16:30 home kernel: chn_resizebuf: PCMDIR_PLAY (hardware) timeout=21 b[4096/2048/2] bs[4096/2048/2] limit=0 Feb 28 20:16:30 home kernel: GEOM: new disk ad4 Feb 28 20:16:30 home kernel: GEOM: new disk ad6 Feb 28 20:16:30 home kernel: GEOM_JOURNAL: Journal 2324325294: ad4d contains data. Feb 28 20:16:30 home kernel: GEOM_JOURNAL: Journal 2324325294: ad4d contains journal. Feb 28 20:16:30 home kerne