Re: Endless CAM messages with recent CURRENT
On 30.01.2011 16:22 (UTC+1), Hans Petter Selasky wrote: On Sunday 30 January 2011 16:15:02 Rainer Hurling wrote: Wouldn't it be useful to integrate the device info into the usb driver? You can check if your kernel is compiled with "options USB_VERBOSE". That should bring some more verbosity based on sys/dev/usb/usbdevs. Thanks for the hint. Now I am getting #usbconfig -u 3 -a 2 dump_device_desc ugen3.2: at usbus3, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=ON bLength = 0x0012 bDescriptorType = 0x0001 bcdUSB = 0x0200 bDeviceClass = 0x bDeviceSubClass = 0x bDeviceProtocol = 0x bMaxPacketSize0 = 0x0040 idVendor = 0x05e3 idProduct = 0x0716 bcdDevice = 0x9744 iManufacturer = 0x iProduct = 0x0001 iSerialNumber = 0x0002 <9744> bNumConfigurations = 0x0001 So it seems there already is some info about this device in the code. Rainer --HPS ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: Endless CAM messages with recent CURRENT
On Sunday 30 January 2011 16:15:02 Rainer Hurling wrote: > Wouldn't it be useful to integrate the device info into the usb driver? You can check if your kernel is compiled with "options USB_VERBOSE". That should bring some more verbosity based on sys/dev/usb/usbdevs. --HPS ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: Endless CAM messages with recent CURRENT
On 30.01.2011 15:13 (UTC+1), Hans Petter Selasky wrote: On Sunday 30 January 2011 14:57:37 Rainer Hurling wrote: On 14.01.2011 20:10 (UTC+1), Hans Petter Selasky wrote: Marcus, Can you have a look at this? Are there any news? I don't have any news, except it is a HAL problem and it needs to be solved there. Ok, I understand. Besides this I think that my device is not fully recognized by usb code. I only get 'Generic STORAGE DEVICE 9744' instead of something like 'Genesys Logic, Inc. USB2.0 Multislot Card Reader/Writer'. Wouldn't it be useful to integrate the device info into the usb driver? #lssub Bus 002 Device 002: ID05e3:0716 Genesys Logic, Inc. USB2.0 Multislot Card Reader/Writer idVendor 0x05e3 Genesys Logic, Inc. #usb-devices T: Bus=02 Lev=01 Prnt=01 Port=03 Cnt=01 Dev#= 2 Spd=480 MxCh= 0 D: Ver=2.00 Cls=00(>ifc ) Sub=00 Prot=00 MxPS=64 #Cfgs= 1 P: Vendor=05e3 ProdID=0176 Rev=97.44 S: Product=USB Storage S: SerialNumber=9744 C: #Ifs= 1 Cfg#= 1 Atr=80 MxPwr=500mA I: If#= 0 Alt= 0 #EPs= 2 Cls=08(stor.) Sub=06 Prot=50 Driver=usb-storage Rainer --HPS ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: Endless CAM messages with recent CURRENT
On Sunday 30 January 2011 14:57:37 Rainer Hurling wrote: > On 14.01.2011 20:10 (UTC+1), Hans Petter Selasky wrote: > > Marcus, > > > > Can you have a look at this? > > Are there any news? > I don't have any news, except it is a HAL problem and it needs to be solved there. --HPS ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: Endless CAM messages with recent CURRENT
On 14.01.2011 20:10 (UTC+1), Hans Petter Selasky wrote: Marcus, Can you have a look at this? Are there any news? Thanks, Rainer --HPS On Friday 14 January 2011 16:21:00 Rainer Hurling wrote: After looking around I had been able to localise the cause for the described messages, see below: On 14.01.2011 10:07 (UTC+1), Rainer Hurling wrote: Today I updated my 9.0-CURRENT system (amd64) to revision 199506: After rebooting I get the following messages two times per second in an endless run: - ... Jan 14 09:37:47 krabat kernel: (sg1:umass-sim0:0:0:0): cam_periph_release_locked: release 0xfe0009f41200 when refcount is zero Jan 14 09:37:47 krabat kernel: Jan 14 09:37:48 krabat kernel: (sg2:umass-sim0:0:0:1): cam_periph_release_locked: release 0xfe0009f41100 when refcount is zero Jan 14 09:37:48 krabat kernel: ... - When turning off hald no more of these messages appear. hald is trying to poll the card reader, but it does not like this. So prohibiting the polling in /usr/local/share/hal/fdi/preprobe/20thirdparty/ solves my problem: #cat 10-broken-usb-card-reader.fdi false sg1 and sg2 are devices from my front panel card reader Silverstone SST-FP35B: #camcontrol devlist [..snip..] at scbus6 target 0 lun 0 (sg1,pass3,da0) at scbus6 target 0 lun 1 (sg2,pass4,da1) Is it possible that the last changes in usb code (xhci) or in cam code are responsible for this? Does anyone else observe this behaviour? A more generic approach would be to integrate the polling info into /usr/local/share/hal/fdi/preprobe/10osvendor/20-broken-usb-sticks.fdi. Is anyone willing to integrate the code (.fdi file or some quirks) in the usb stuff? In that case Linux is offering some more info about this device: #lssub Bus 002 Device 002: ID05e3:0716 Genesys Logic, Inc. USB2.0 Multislot Card Reader/Writer idVendor 0x05e3 Genesys Logic, Inc. #usb-devices T: Bus=02 Lev=01 Prnt=01 Port=03 Cnt=01 Dev#= 2 Spd=480 MxCh= 0 D: Ver=2.00 Cls=00(>ifc ) Sub=00 Prot=00 MxPS=64 #Cfgs= 1 P: Vendor=05e3 ProdID=0176 Rev=97.44 S: Product=USB Storage S: SerialNumber=9744 C: #Ifs= 1 Cfg#= 1 Atr=80 MxPwr=500mA I: If#= 0 Alt= 0 #EPs= 2 Cls=08(stor.) Sub=06 Prot=50 Driver=usb-storage Note, that the card reader from Benesys Logic is only one device of some more (firewire, eSATA, USB slots ...), which are provided from the 'Silverstone SST-FP35B' front panel access unit. Please let me know if you need more info or if I can test something. ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: Endless CAM messages with recent CURRENT
Marcus, Can you have a look at this? --HPS On Friday 14 January 2011 16:21:00 Rainer Hurling wrote: > After looking around I had been able to localise the cause for the > described messages, see below: > > On 14.01.2011 10:07 (UTC+1), Rainer Hurling wrote: > > Today I updated my 9.0-CURRENT system (amd64) to revision 199506: After > > rebooting I get the following messages two times per second in an > > endless run: > > > > > > - > > ... > > Jan 14 09:37:47 krabat kernel: (sg1:umass-sim0:0:0:0): > > cam_periph_release_locked: release 0xfe0009f41200 when refcount is > > zero Jan 14 09:37:47 krabat kernel: > > Jan 14 09:37:48 krabat kernel: (sg2:umass-sim0:0:0:1): > > cam_periph_release_locked: release 0xfe0009f41100 when refcount is > > zero Jan 14 09:37:48 krabat kernel: > > ... > > - > > When turning off hald no more of these messages appear. hald is trying > to poll the card reader, but it does not like this. So prohibiting the > polling in /usr/local/share/hal/fdi/preprobe/20thirdparty/ solves my > problem: > > #cat 10-broken-usb-card-reader.fdi > > > > > > > > > > int="0x0716"> > type="bool">false > > > > > > > > > sg1 and sg2 are devices from my front panel card reader Silverstone > > SST-FP35B: > > > > #camcontrol devlist > > [..snip..] > > at scbus6 target 0 lun 0 (sg1,pass3,da0) > > at scbus6 target 0 lun 1 (sg2,pass4,da1) > > > > > > Is it possible that the last changes in usb code (xhci) or in cam code > > are responsible for this? Does anyone else observe this behaviour? > > A more generic approach would be to integrate the polling info into > /usr/local/share/hal/fdi/preprobe/10osvendor/20-broken-usb-sticks.fdi. > Is anyone willing to integrate the code (.fdi file or some quirks) in > the usb stuff? > > > In that case Linux is offering some more info about this device: > > #lssub > Bus 002 Device 002: ID05e3:0716 Genesys Logic, Inc. USB2.0 Multislot > Card Reader/Writer > idVendor 0x05e3 Genesys Logic, Inc. > > #usb-devices > T: Bus=02 Lev=01 Prnt=01 Port=03 Cnt=01 Dev#= 2 Spd=480 MxCh= 0 > D: Ver=2.00 Cls=00(>ifc ) Sub=00 Prot=00 MxPS=64 #Cfgs= 1 > P: Vendor=05e3 ProdID=0176 Rev=97.44 > S: Product=USB Storage > S: SerialNumber=9744 > C: #Ifs= 1 Cfg#= 1 Atr=80 MxPwr=500mA > I: If#= 0 Alt= 0 #EPs= 2 Cls=08(stor.) Sub=06 Prot=50 Driver=usb-storage > > > Note, that the card reader from Benesys Logic is only one device of some > more (firewire, eSATA, USB slots ...), which are provided from the > 'Silverstone SST-FP35B' front panel access unit. > > > Please let me know if you need more info or if I can test something. > > Thanks in advance, > Rainer Hurling > ___ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org" ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: Endless CAM messages with recent CURRENT
After looking around I had been able to localise the cause for the described messages, see below: On 14.01.2011 10:07 (UTC+1), Rainer Hurling wrote: Today I updated my 9.0-CURRENT system (amd64) to revision 199506: After rebooting I get the following messages two times per second in an endless run: - ... Jan 14 09:37:47 krabat kernel: (sg1:umass-sim0:0:0:0): cam_periph_release_locked: release 0xfe0009f41200 when refcount is zero Jan 14 09:37:47 krabat kernel: Jan 14 09:37:48 krabat kernel: (sg2:umass-sim0:0:0:1): cam_periph_release_locked: release 0xfe0009f41100 when refcount is zero Jan 14 09:37:48 krabat kernel: ... - When turning off hald no more of these messages appear. hald is trying to poll the card reader, but it does not like this. So prohibiting the polling in /usr/local/share/hal/fdi/preprobe/20thirdparty/ solves my problem: #cat 10-broken-usb-card-reader.fdi int="0x0716"> type="bool">false sg1 and sg2 are devices from my front panel card reader Silverstone SST-FP35B: #camcontrol devlist [..snip..] at scbus6 target 0 lun 0 (sg1,pass3,da0) at scbus6 target 0 lun 1 (sg2,pass4,da1) Is it possible that the last changes in usb code (xhci) or in cam code are responsible for this? Does anyone else observe this behaviour? A more generic approach would be to integrate the polling info into /usr/local/share/hal/fdi/preprobe/10osvendor/20-broken-usb-sticks.fdi. Is anyone willing to integrate the code (.fdi file or some quirks) in the usb stuff? In that case Linux is offering some more info about this device: #lssub Bus 002 Device 002: ID05e3:0716 Genesys Logic, Inc. USB2.0 Multislot Card Reader/Writer idVendor 0x05e3 Genesys Logic, Inc. #usb-devices T: Bus=02 Lev=01 Prnt=01 Port=03 Cnt=01 Dev#= 2 Spd=480 MxCh= 0 D: Ver=2.00 Cls=00(>ifc ) Sub=00 Prot=00 MxPS=64 #Cfgs= 1 P: Vendor=05e3 ProdID=0176 Rev=97.44 S: Product=USB Storage S: SerialNumber=9744 C: #Ifs= 1 Cfg#= 1 Atr=80 MxPwr=500mA I: If#= 0 Alt= 0 #EPs= 2 Cls=08(stor.) Sub=06 Prot=50 Driver=usb-storage Note, that the card reader from Benesys Logic is only one device of some more (firewire, eSATA, USB slots ...), which are provided from the 'Silverstone SST-FP35B' front panel access unit. Please let me know if you need more info or if I can test something. Thanks in advance, Rainer Hurling ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Endless CAM messages with recent CURRENT
Today I updated my 9.0-CURRENT system (amd64) to revision 199506: After rebooting I get the following messages two times per second in an endless run: - ... Jan 14 09:37:47 krabat kernel: (sg1:umass-sim0:0:0:0): cam_periph_release_locked: release 0xfe0009f41200 when refcount is zero Jan 14 09:37:47 krabat kernel: Jan 14 09:37:48 krabat kernel: (sg2:umass-sim0:0:0:1): cam_periph_release_locked: release 0xfe0009f41100 when refcount is zero Jan 14 09:37:48 krabat kernel: ... - sg1 and sg2 are devices from my front panel card reader Silverstone SST-FP35B: #camcontrol devlist [..snip..] at scbus6 target 0 lun 0 (sg1,pass3,da0) at scbus6 target 0 lun 1 (sg2,pass4,da1) Is it possible that the last changes in usb code (xhci) or in cam code are responsible for this? Does anyone else observe this behaviour? Please let me know if you need more info or if I can test something. Thank you for any hint, Rainer Hurling ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
