Re: Rasberry Pi 4 has no USB

[Carl Johnson]

Carl Johnson  writes:

> Emmanuel Vadot  writes:
>
>> On Sun, 28 Feb 2021 09:26:23 -0800
>> Carl Johnson  wrote:
>>
>>> I have an 8GB RPi 4B that I am trying out, but it has no USB response at
>>> all. That means that I can't use a keyboard or mouse, but I can use a
>>> serial console and ethernet.  I can plug any USB device into any port,
>>> but there is nothing logged in /var/messages.  Running usbconfig as root
>>> just reports 'No device match or lack of permissions'.  Running
>>> 'dmesg | grep -i usb' reports only the following lines:
>>> 
>>>   usb_nop_xceiv0:  on ofwbus0
>>>   bcm_xhci0:  irq 81 at 
>>> device 0.0 on pci2
>>>   usb_needs_explore_all: no devclass
>>>   
>>> Running 'pciconf -lv' shows there is a VL805 USB controller present.  I
>>> tested this with Linux and everything worked properly.  This is a new
>>> computer that I bought only a couple of weeks ago.  Does anybody have
>>> any ideas on what this might be, or what I could do to try to figure it
>>> out?
>>> 
>>> Thanks in advance for any ideas.
>>> -- 
>>> Carl Johnsonca...@peak.org
>>
>>  Hello,
>>
>>  This is known, see
>> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=252971#c25
>>
>>  I wanted to wait that a tag was created on the rpi-firmware github
>> repo but it seems that they don't want to so I'll update the port next
>> week so RC1 will have the updated firmware.
>>
>>  Cheers,
>
> Thank you very much for that!  I will test that as soon as it comes
> out.

Just for the record, RC3 now works properly.  Thanks to everyone for
getting this fix in before the release.

-- 
Carl Johnsonca...@peak.org

___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: Rasberry Pi 4 has no USB

[Carl Johnson]

Peter Cornelius  writes:

> [Retransmssion, stupid HTML mails]
>
> G'day, Carl,
>  
> On 2/28/21 11:26 AM, Carl Johnson wrote:
>> I have an 8GB RPi 4B that I am trying out, but it has no USB response at
>> all.  [...]
>  
> I second the suggestion to do a brief trial with Raspbian or so.  I
> currently run mine under -current as below, but can confirm that I
> have been able to run it since 13 with USB keyboard and mouse. I
> currenly am logged in via the net, so without further USB devices, at
> least the hubs should be present:

I had tested it with Raspbian, and everything worked properly.

> [root@rpi4 ~]# usbconfig  
> ugen0.1: <0x1106 XHCI root HUB> at usbus0, cfg=0 md=HOST spd=SUPER (5.0Gbps) 
> pwr=SAVE (0mA)
> ugen0.2:  at usbus0, cfg=0 md=HOST spd=HIGH 
> (480Mbps) pwr=SAVE (100mA)
>  
> [root@rpi4 ~]# uname -a
> FreeBSD rpi4 14.0-CURRENT FreeBSD 14.0-CURRENT #1: Tue Feb 23 02:30:31
> UTC 2021 root@rpi4:/usr/obj/usr/src/arm64.aarch64/sys/GENERIC 
> arm64
>  
> I can share a 14.0 image I used to initially boot if you have
> somewhere to push it
> (FreeBSD-aarch64-14.0-GENERIC-a63eae65ff8-RaspberryPi4.img, seven and
> a half gig, roughly; an xz. I'd expect at around two).
>  
> I did, though, have to do a couple of tries with Raspbian initially to put a 
> recent firmware onto my RPI4B8GB.
>  
> HOWEVER.
>  
> I also have an odd observation which is that there is NO OTHER USB
> device BUT the above and my mouse/keyboard. This is quite odd since I
> do have more devices connected (most notably a umass
> JMicron-JMS561-based device [1]) and naively hoped that also on arm,
> USB devices would at least show up as ugen-something. Well, at least
> keyboard and mouse did work, did they not?
>  
> I did boot with rasbian, all comes to life instantly and
> beautifully. I even was able to update some firmware on the
> JMS-thingo, see the disks, all blinkenlights there. Back to FreeBSD --
> again, silence. I now really am scratching my head and also have run
> out of ideas... though kind of luxury, compared to you, I guess.
>  
> Any help appreciated, and Carl, as written, if you want my image, where 
> should I put it?
>  
> Cheers,
>  
> Peter.
>  
> [1] https://www.jmicron.com/file/download/1033/JMS561_Product+Brief.pdf

There is another response that states this is a known problem that will
be fixed in -RC1, so I will wait to test that one.  Maybe your problem
will be fixed with that one also.  Meanwhile, I will just go back to
Raspbian until -RC1 comes out.

Thanks for your information.

-- 
Carl Johnsonca...@peak.org

___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: Rasberry Pi 4 has no USB

[Carl Johnson]

Emmanuel Vadot  writes:

> On Sun, 28 Feb 2021 09:26:23 -0800
> Carl Johnson  wrote:
>
>> I have an 8GB RPi 4B that I am trying out, but it has no USB response at
>> all. That means that I can't use a keyboard or mouse, but I can use a
>> serial console and ethernet.  I can plug any USB device into any port,
>> but there is nothing logged in /var/messages.  Running usbconfig as root
>> just reports 'No device match or lack of permissions'.  Running
>> 'dmesg | grep -i usb' reports only the following lines:
>> 
>>   usb_nop_xceiv0:  on ofwbus0
>>   bcm_xhci0:  irq 81 at 
>> device 0.0 on pci2
>>   usb_needs_explore_all: no devclass
>>   
>> Running 'pciconf -lv' shows there is a VL805 USB controller present.  I
>> tested this with Linux and everything worked properly.  This is a new
>> computer that I bought only a couple of weeks ago.  Does anybody have
>> any ideas on what this might be, or what I could do to try to figure it
>> out?
>> 
>> Thanks in advance for any ideas.
>> -- 
>> Carl Johnson ca...@peak.org
>> 
>> ___
>> freebsd-stable@freebsd.org mailing list
>> https://lists.freebsd.org/mailman/listinfo/freebsd-stable
>> To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
>
>  Hello,
>
>  This is known, see
> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=252971#c25
>
>  I wanted to wait that a tag was created on the rpi-firmware github
> repo but it seems that they don't want to so I'll update the port next
> week so RC1 will have the updated firmware.
>
>  Cheers,

Thank you very much for that!  I will test that as soon as it comes
out.

-- 
Carl Johnsonca...@peak.org

___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: Rasberry Pi 4 has no USB

[Emmanuel Vadot]

On Sun, 28 Feb 2021 09:26:23 -0800
Carl Johnson  wrote:

> I have an 8GB RPi 4B that I am trying out, but it has no USB response at
> all. That means that I can't use a keyboard or mouse, but I can use a
> serial console and ethernet.  I can plug any USB device into any port,
> but there is nothing logged in /var/messages.  Running usbconfig as root
> just reports 'No device match or lack of permissions'.  Running
> 'dmesg | grep -i usb' reports only the following lines:
> 
>   usb_nop_xceiv0:  on ofwbus0
>   bcm_xhci0:  irq 81 at 
> device 0.0 on pci2
>   usb_needs_explore_all: no devclass
>   
> Running 'pciconf -lv' shows there is a VL805 USB controller present.  I
> tested this with Linux and everything worked properly.  This is a new
> computer that I bought only a couple of weeks ago.  Does anybody have
> any ideas on what this might be, or what I could do to try to figure it
> out?
> 
> Thanks in advance for any ideas.
> -- 
> Carl Johnson  ca...@peak.org
> 
> ___
> freebsd-stable@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-stable
> To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

 Hello,

 This is known, see
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=252971#c25

 I wanted to wait that a tag was created on the rpi-firmware github
repo but it seems that they don't want to so I'll update the port next
week so RC1 will have the updated firmware.

 Cheers,

-- 
Emmanuel Vadot  
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: Rasberry Pi 4 has no USB

[Carl Johnson]

Tim Daneliuk  writes:

> On 2/28/21 11:26 AM, Carl Johnson wrote:
>> I have an 8GB RPi 4B that I am trying out, but it has no USB response at
>> all. That means that I can't use a keyboard or mouse, but I can use a
>> serial console and ethernet.  I can plug any USB device into any port,
>> but there is nothing logged in /var/messages.  Running usbconfig as root
>> just reports 'No device match or lack of permissions'.  Running
>> 'dmesg | grep -i usb' reports only the following lines:
>> 
>>   usb_nop_xceiv0:  on ofwbus0
>>   bcm_xhci0:  irq 81 at 
>> device 0.0 on pci2
>>   usb_needs_explore_all: no devclass
>>   
>> Running 'pciconf -lv' shows there is a VL805 USB controller present.  I
>> tested this with Linux and everything worked properly.  This is a new
>> computer that I bought only a couple of weeks ago.  Does anybody have
>> any ideas on what this might be, or what I could do to try to figure it
>> out?
>> 
>> Thanks in advance for any ideas.
>> 
>
>
> Not to belabour the obvious, but have you booted the machine with Linux
> to see if USB works there?  (Just to avoid the possibility that you
> have bad hardware.)

I did verify that it works on Linux and everything worked properly
there.

-- 
Carl Johnsonca...@peak.org

___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: Rasberry Pi 4 has no USB

[Carl Johnson]

Mehmet Erol Sanliturk  writes:

> On Sun, Feb 28, 2021 at 8:26 PM Carl Johnson  wrote:
>
>> I have an 8GB RPi 4B that I am trying out, but it has no USB response at
>> all. That means that I can't use a keyboard or mouse, but I can use a
>> serial console and ethernet.  I can plug any USB device into any port,
>> but there is nothing logged in /var/messages.  Running usbconfig as root
>> just reports 'No device match or lack of permissions'.  Running
>> 'dmesg | grep -i usb' reports only the following lines:
>>
>>   usb_nop_xceiv0:  on ofwbus0
>>   bcm_xhci0:  irq 81 at
>> device 0.0 on pci2
>>   usb_needs_explore_all: no devclass
>>
>> Running 'pciconf -lv' shows there is a VL805 USB controller present.  I
>> tested this with Linux and everything worked properly.  This is a new
>> computer that I bought only a couple of weeks ago.  Does anybody have
>> any ideas on what this might be, or what I could do to try to figure it
>> out?
>>
>> Thanks in advance for any ideas.
>> --
>> Carl Johnsonca...@peak.org
>>
>> ___
>>
>
>
>
> You did not mention which FreeBSD  you are using  ( please use "uname -a" )
> .
>
> Personally , I do not know  anything about Raspberry Pi with FreeBSD , but
> , without knowing which FreeBSD you are using ,
> it is very likely that no one will be able to give you any information .

You are right that I forgot to mention that.  In this case this is the
binary 13.0-BETA4 image that I downloaded directly from the FreeBSD
website, and verified the checksum.  The output of uname -a is:

FreeBSD basil 13.0-BETA4 FreeBSD 13.0-BETA4 #0 releng/13.0-n244592-e32bc253629: 
Fri Feb 26 08:02:53 UTC 2021 
r...@releng1.nyi.freebsd.org:/usr/obj/usr/src/arm64.aarch64/sys/GENERIC  arm64

Thanks for reminding me.
-- 
Carl Johnsonca...@peak.org

___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: Rasberry Pi 4 has no USB

[Peter Cornelius]

[Retransmssion, stupid HTML mails]

G'day, Carl,
 
On 2/28/21 11:26 AM, Carl Johnson wrote:
> I have an 8GB RPi 4B that I am trying out, but it has no USB response at
> all.  [...]
 
I second the suggestion to do a brief trial with Raspbian or so.  I currently 
run mine under -current as below, but can confirm that I have been able to run 
it since 13 with USB keyboard and mouse. I currenly am logged in via the net, 
so without further USB devices, at least the hubs should be present:
 
[root@rpi4 ~]# usbconfig  
ugen0.1: <0x1106 XHCI root HUB> at usbus0, cfg=0 md=HOST spd=SUPER (5.0Gbps) 
pwr=SAVE (0mA)
ugen0.2:  at usbus0, cfg=0 md=HOST spd=HIGH (480Mbps) 
pwr=SAVE (100mA)
 
[root@rpi4 ~]# uname -a
FreeBSD rpi4 14.0-CURRENT FreeBSD 14.0-CURRENT #1: Tue Feb 23 02:30:31 UTC 2021 
    root@rpi4:/usr/obj/usr/src/arm64.aarch64/sys/GENERIC  arm64
 
I can share a 14.0 image I used to initially boot if you have somewhere to push 
it (FreeBSD-aarch64-14.0-GENERIC-a63eae65ff8-RaspberryPi4.img, seven and a half 
gig, roughly; an xz. I'd expect at around two).
 
I did, though, have to do a couple of tries with Raspbian initially to put a 
recent firmware onto my RPI4B8GB.
 
HOWEVER.
 
I also have an odd observation which is that there is NO OTHER USB device BUT 
the above and my mouse/keyboard. This is quite odd since I do have more devices 
connected (most notably a umass JMicron-JMS561-based device [1]) and naively 
hoped that also on arm, USB devices would at least show up as ugen-something. 
Well, at least keyboard and mouse did work, did they not?
 
I did boot with rasbian, all comes to life instantly and beautifully. I even 
was able to update some firmware on the JMS-thingo, see the disks, all 
blinkenlights there. Back to FreeBSD -- again, silence. I now really am 
scratching my head and also have run out of ideas... though kind of luxury, 
compared to you, I guess.
 
Any help appreciated, and Carl, as written, if you want my image, where should 
I put it?
 
Cheers,
 
Peter.
 
[1] https://www.jmicron.com/file/download/1033/JMS561_Product+Brief.pdf
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: Rasberry Pi 4 has no USB

[Mehmet Erol Sanliturk]

On Sun, Feb 28, 2021 at 8:26 PM Carl Johnson  wrote:

> I have an 8GB RPi 4B that I am trying out, but it has no USB response at
> all. That means that I can't use a keyboard or mouse, but I can use a
> serial console and ethernet.  I can plug any USB device into any port,
> but there is nothing logged in /var/messages.  Running usbconfig as root
> just reports 'No device match or lack of permissions'.  Running
> 'dmesg | grep -i usb' reports only the following lines:
>
>   usb_nop_xceiv0:  on ofwbus0
>   bcm_xhci0:  irq 81 at
> device 0.0 on pci2
>   usb_needs_explore_all: no devclass
>
> Running 'pciconf -lv' shows there is a VL805 USB controller present.  I
> tested this with Linux and everything worked properly.  This is a new
> computer that I bought only a couple of weeks ago.  Does anybody have
> any ideas on what this might be, or what I could do to try to figure it
> out?
>
> Thanks in advance for any ideas.
> --
> Carl Johnsonca...@peak.org
>
> ___
>



You did not mention which FreeBSD  you are using  ( please use "uname -a" )
.

Personally , I do not know  anything about Raspberry Pi with FreeBSD , but
, without knowing which FreeBSD you are using ,
it is very likely that no one will be able to give you any information .


Mehmet Erol Sanliturk
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: Rasberry Pi 4 has no USB

[Peter Cornelius]

___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: Rasberry Pi 4 has no USB

[Tim Daneliuk]

On 2/28/21 11:26 AM, Carl Johnson wrote:
> I have an 8GB RPi 4B that I am trying out, but it has no USB response at
> all. That means that I can't use a keyboard or mouse, but I can use a
> serial console and ethernet.  I can plug any USB device into any port,
> but there is nothing logged in /var/messages.  Running usbconfig as root
> just reports 'No device match or lack of permissions'.  Running
> 'dmesg | grep -i usb' reports only the following lines:
> 
>   usb_nop_xceiv0:  on ofwbus0
>   bcm_xhci0:  irq 81 at 
> device 0.0 on pci2
>   usb_needs_explore_all: no devclass
>   
> Running 'pciconf -lv' shows there is a VL805 USB controller present.  I
> tested this with Linux and everything worked properly.  This is a new
> computer that I bought only a couple of weeks ago.  Does anybody have
> any ideas on what this might be, or what I could do to try to figure it
> out?
> 
> Thanks in advance for any ideas.
> 


Not to belabour the obvious, but have you booted the machine with Linux
to see if USB works there?  (Just to avoid the possibility that you
have bad hardware.)
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Rasberry Pi 4 has no USB

[Carl Johnson]

I have an 8GB RPi 4B that I am trying out, but it has no USB response at
all. That means that I can't use a keyboard or mouse, but I can use a
serial console and ethernet.  I can plug any USB device into any port,
but there is nothing logged in /var/messages.  Running usbconfig as root
just reports 'No device match or lack of permissions'.  Running
'dmesg | grep -i usb' reports only the following lines:

  usb_nop_xceiv0:  on ofwbus0
  bcm_xhci0:  irq 81 at 
device 0.0 on pci2
  usb_needs_explore_all: no devclass
  
Running 'pciconf -lv' shows there is a VL805 USB controller present.  I
tested this with Linux and everything worked properly.  This is a new
computer that I bought only a couple of weeks ago.  Does anybody have
any ideas on what this might be, or what I could do to try to figure it
out?

Thanks in advance for any ideas.
-- 
Carl Johnsonca...@peak.org

___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

x1 gen3 long boot with usb errors

[Pavel Timofeev]

pports D0 D3  current D0
MSI supports 1 message
secbus=4, subbus=4
found-> vendor=0x8086, dev=0x9cc3, revid=0x03
domain=0, bus=0, slot=31, func=0
class=06-01-00, hdrtype=0x00, mfdev=1
cmdreg=0x0007, statreg=0x0210, cachelnsz=0 (dwords)
lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns)
found-> vendor=0x8086, dev=0x9c83, revid=0x03
domain=0, bus=0, slot=31, func=2
class=01-06-01, hdrtype=0x00, mfdev=0
cmdreg=0x0007, statreg=0x02b0, cachelnsz=0 (dwords)
lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns)
intpin=b, irq=255
powerspec 3  supports D0 D3  current D0
MSI supports 1 message
map[10]: type I/O Port, range 32, base 0x30a8, size  3, enabled
pcib0: allocated type 4 (0x30a8-0x30af) for rid 10 of pci0:0:31:2
map[14]: type I/O Port, range 32, base 0x30b4, size  2, enabled
pcib0: allocated type 4 (0x30b4-0x30b7) for rid 14 of pci0:0:31:2
map[18]: type I/O Port, range 32, base 0x30a0, size  3, enabled
pcib0: allocated type 4 (0x30a0-0x30a7) for rid 18 of pci0:0:31:2
map[1c]: type I/O Port, range 32, base 0x30b0, size  2, enabled
pcib0: allocated type 4 (0x30b0-0x30b3) for rid 1c of pci0:0:31:2
map[20]: type I/O Port, range 32, base 0x3060, size  5, enabled
pcib0: allocated type 4 (0x3060-0x307f) for rid 20 of pci0:0:31:2
map[24]: type Memory, range 32, base 0xe113c000, size 11, enabled
pcib0: allocated type 3 (0xe113c000-0xe113c7ff) for rid 24 of pci0:0:31:2
found-> vendor=0x8086, dev=0x9ca2, revid=0x03
domain=0, bus=0, slot=31, func=3
class=0c-05-00, hdrtype=0x00, mfdev=0
cmdreg=0x0003, statreg=0x0280, cachelnsz=0 (dwords)
lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns)
intpin=c, irq=255
map[10]: type Memory, range 64, base 0xe1138000, size  8, enabled
pcib0: allocated type 3 (0xe1138000-0xe11380ff) for rid 10 of pci0:0:31:3
map[20]: type I/O Port, range 32, base 0xefa0, size  5, enabled
pcib0: allocated type 4 (0xefa0-0xefbf) for rid 20 of pci0:0:31:3
found-> vendor=0x8086, dev=0x9ca4, revid=0x03
domain=0, bus=0, slot=31, func=6
class=11-80-00, hdrtype=0x00, mfdev=0
cmdreg=0x0002, statreg=0x0010, cachelnsz=0 (dwords)
lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns)
intpin=c, irq=255
powerspec 3  supports D0 D3  current D0
MSI supports 1 message
map[10]: type Memory, range 64, base 0xe113b000, size 12, enabled
pcib0: allocated type 3 (0xe113b000-0xe113bfff) for rid 10 of pci0:0:31:6
vgapci0:  port 0x3000-0x303f mem
0xe000-0xe0ff,0xc000-0xdfff at device 2.0 on pci0
vgapci0: Boot video device
hdac0:  mem 0xe113-0xe1133fff at device
3.0 on pci0
hdac0: PCI card vendor: 0x17aa, device: 0x2227
hdac0: HDA Driver Revision: 20120126_0002
hdac0: Config options: on=0x off=0x
hdac0: attempting to allocate 1 MSI vectors (1 supported)
msi: routing MSI IRQ 48 to local APIC 2 vector 50
hdac0: using IRQ 48 for MSI
hdac0: Caps: OSS 3, ISS 0, BSS 0, NSDO 1, 64bit, CORB 256, RIRB 256
xhci0:  mem
0xe112-0xe112 at device 20.0 on pci0
xhci0: 32 bytes context size, 64-bit DMA
xhci0: attempting to allocate 1 MSI vectors (8 supported)
msi: routing MSI IRQ 49 to local APIC 0 vector 55
xhci0: using IRQ 49 for MSI
xhci0: MSI enabled
xhci0: Port routing mask set to 0x
usbus0 on xhci0
xhci0: usbpf: Attached
usbus0: 5.0Gbps Super Speed USB v3.0
pci0:  at device 22.0 (no driver attached)
em0:  port 0x3080-0x309f mem
0xe110-0xe111,0xe113d000-0xe113dfff at device 25.0 on pci0
em0: attach_pre capping queues at 1
em0: Using 1024 TX descriptors and 1024 RX descriptors
em0: msix_init qsets capped at 1
em0: attempting to allocate 1 MSI vectors (1 supported)
msi: routing MSI IRQ 50 to local APIC 2 vector 51
em0: using IRQ 50 for MSI
em0: Using an MSI interrupt
em0: allocated for 1 tx_queues
em0: allocated for 1 rx_queues
msi: Assigning MSI IRQ 50 to local APIC 3 vector 49
msi: Assigning MSI IRQ 50 to local APIC 2 vector 51
em0: bpf attached
em0: Ethernet address: 54:ee:75:77:0b:ec
em0: netmap queues/slots: TX 1/1024, RX 1/1024
hdac1:  mem 0xe1134000-0xe1137fff at device
27.0 on pci0
hdac1: PCI card vendor: 0x17aa, device: 0x2227
hdac1: HDA Driver Revision: 20120126_0002
hdac1: Config options: on=0x off=0x
hdac1: attempting to allocate 1 MSI vectors (1 supported)
msi: routing MSI IRQ 51 to local APIC 0 vector 56
hdac1: using IRQ 51 for MSI
hdac1: Caps: OSS 4, ISS 4, BSS 0, NSDO 1, 64bit, CORB 256, RIRB 256
pcib1:  at device 28.0 on pci0
pcib1: attempting to allocate 1 MSI vectors (1 supported)
msi: routing MSI IRQ 52 to local APIC 2 vector 52
pcib1: using IRQ 52 for MSI
pcib1: HotPlug command:  -> 1028
pcib1:   domain0
pcib1:   secondary bus 3
pcib1:   subordinate bus   3
pcib2:  at device 28.1 on pci0
pcib0: allocated type 3 (0xe100-0xe10f) for rid 20 of pcib2
pcib2:   domain0
pcib2:   secondary bus 4
pcib2:   subordinate bus   4
pcib2:   memory decode 0xe100-0xe10f
pci1:  on pcib2
pcib2: allocated bus range (4-4) for rid 0 of pci1
pci1: domain=0, physical bus

Re: external USB drive on nas.naund.org

[Andreas Ott]

Hello,

the external USB drive recently stopped being recognized at all by this server.

FreeBSD files.local 11.4-RELEASE-p2 FreeBSD 11.4-RELEASE-p2 #0: Tue Aug  4 
19:21:02 UTC 2020 
r...@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC  amd64

This setup has worked for over 2 years, unfortunately I cannot tell to
which date, or to which update it correlates to.  This server is updated
with freebsd-update and pkg (binary packages only), typically a few days
after any security advisory comes out.

Currently nothing happens when I attach or remove the drive from tany USB port
of the Supermicor X8SIL motherboard. No BIOS changes were made in over a year.
At this time, neither dmesg, usbconfig devlist nor camcontrol show the disk.
I tried rollback from 11.3-RELEASE-p12 to 11.3-RELEASE-p11 and that did not 
work 
either, before upgrading all the way to 11.4-RELEASE-p2.

What debugging should I try next? 

The disk is recognized OK on a CentOS 7 server with similar hardware and on my 
MacbookPro.


I do have an older dmesg excerpt from when it had kernel 11.3-RELEASE-p11 and it
still worked:

ugen1.3:  at usbus1
umass0 on uhub2
umass0:  on usbus1
umass0:  SCSI over Bulk-Only; quirks = 0x8100
umass0:4:0: Attached to scbus4
da0 at umass-sim0 bus 0 scbus4 target 0 lun 0
da0:  Fixed Direct Access SPC-4 SCSI device
da0: Serial Number 24865351072710207E
da0: 40.000MB/s transfers
da0: 1144641MB (2344225968 512 byte sectors)
da0: quirks=0x2


Thanks, andreas
-- 
Andreas Ott   andr...@naund.org
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

watch(4) and [USB] serial

[O'Connor, Daniel via freebsd-stable]

Hi,
I have noticed that watch(4) does not pick up traffic coming from the USB 
serial port - it sees traffic going out but not the reverse.

I tested a pty and it sees traffic in both directions, this computer has a 
'real' serial port but I don't have anything to plug into it right now.

I think this is a bug but I am not sure how the snp stuff is hooked up to find 
the cause, any one know?

Thanks.

--
Daniel O'Connor
"The nice thing about standards is that there
are so many of them to choose from."
 -- Andrew Tanenbaum


___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: USB trouble on Ryzen 3/AsRock mobo.

[Bob Willcox]

Well, I replaced the Gigabyte MB with an ASUS PRIME A3201-K and it is so far
working fine. No USB_ERR_TIMEOUT spewing. The other MB never did stop spewing
the errors (left it on for over 24 hours spewing).

Bob

On Mon, Feb 10, 2020 at 07:32:27AM +0100, Phil Norman wrote:
> Hi.
> 
> I'm afraid the best I could come up with is that the motherboard I was
> using is not standards-compliant, and has a broken USB system. This might
> explain why they insist you install their special drivers on Windows.
> 
> My solution was to replace the motherboard with one that actually works
> properly.
> 
> Cheers,
> Phil
> 
> On Sun, 9 Feb 2020 at 18:05, Bob Willcox  wrote:
> 
> > Hi Phil,
> >
> > Did you ever determine the cause and solution to the USB_ERR_TIMEOUT errors
> > you were getting? I just installed a recent 12.1 snapshot on a system with
> > a
> > Gigabyte GA-AB350N Ryzen motherboard and am seeing similar USB_ERR_TIMEOUT
> > errors with this MB.
> >
> > The errors on this system appear to be continuing forever as they have been
> > going on for over 30 minutes so far with no end in sight. On this system
> > the
> > initial dmesg messages for the usb errors looks strikingly similar to
> > yours:
> >
> > Feb  9 18:46:57 han kernel: xhci0: Resetting controller
> > Feb  9 18:46:57 han kernel: usb_alloc_device: set address 3 failed
> > (USB_ERR_TIMEOUT, ignored)
> > Feb  9 18:46:57 han kernel: Root mount waiting for: usbus0
> > Feb  9 18:46:57 han syslogd: last message repeated 1 times
> > Feb  9 18:46:57 han kernel: usbd_setup_device_desc: getting device
> > descriptor at addr 3 failed, USB_ERR_TIMEOUT
> > Feb  9 18:46:57 han kernel: Root mount waiting for: usbus0
> > Feb  9 18:46:57 han kernel: usbd_req_re_enumerate: addr=3, set address
> > failed! (USB_ERR_TIMEOUT, ignored)
> > Feb  9 18:46:57 han kernel: Root mount waiting for: usbus0
> > Feb  9 18:46:57 han syslogd: last message repeated 1 times
> > Feb  9 18:46:57 han kernel: usbd_setup_device_desc: getting device
> > descriptor at addr 3 failed, USB_ERR_TIMEOUT
> > Feb  9 18:46:57 han kernel: Root mount waiting for: usbus0
> > Feb  9 18:46:57 han kernel: usbd_req_re_enumerate: addr=3, set address
> > failed! (USB_ERR_TIMEOUT, ignored)
> > Feb  9 18:46:57 han kernel: Root mount waiting for: usbus0
> > Feb  9 18:46:57 han syslogd: last message repeated 1 times
> > Feb  9 18:46:57 han kernel: usbd_setup_device_desc: getting device
> > descriptor at addr 3 failed, USB_ERR_TIMEOUT
> > Feb  9 18:46:57 han kernel: Root mount waiting for: usbus0
> > Feb  9 18:46:57 han kernel: usbd_req_re_enumerate: addr=3, set address
> > failed! (USB_ERR_TIMEOUT, ignored)
> > Feb  9 18:46:57 han kernel: Root mount waiting for: usbus0
> > Feb  9 18:46:57 han kernel: usbd_setup_device_desc: getting device
> > descriptor at addr 3 failed, USB_ERR_TIMEOUT
> > Feb  9 18:46:57 han kernel: Root mount waiting for: usbus0
> > Feb  9 18:46:57 han syslogd: last message repeated 1 times
> > Feb  9 18:46:57 han kernel: usbd_req_re_enumerate: addr=3, set address
> > failed! (USB_ERR_TIMEOUT, ignored)
> > Feb  9 18:46:57 han kernel: Root mount waiting for: usbus0
> >
> > Anyone have any advice on what I can do the get this to stop? The system is
> > fundamentally unusable as it is.
> >
> > Thanks,
> > Bob
> >
> > On Tue, Jun 19, 2018 at 09:38:17PM +0200, Phil Norman wrote:
> > > Hi.
> > >
> > > I've recently converted to FreeBSD, fleeing the Windowsification of
> > Ubuntu.
> > > I've been having some trouble with the USB system, which seems strange as
> > > FreeBSD's USB stack is, according to a friend, rock solid. I'd like to
> > > narrow down if this is a hardware (CPU or mobo) or software issue.
> > >
> > > I'm running a Ryzen 3 1200, plugged into a "Fatal1ty X370 Gaming-ITX/ac"
> > > motherboard (chosen because it supports ECC RAM and fits in an ITX case).
> > >
> > > On a cold boot (ie starting by flipping the physical PSU power switch),
> > BSD
> > > boots up nice and quickly, without errors, and then runs for days
> > without a
> > > single USB-related error on dmesg. However, any other kind of reboot
> > which
> > > doesn't interrupt the electricity supply yields a large number of USB
> > > errors (USB_ERR_TIMEOUTs every few seconds or so) and frequent resets of
> > > the xhci0 controller.
> > >
> > > On occasion, I also get problems with my keyboard randomly stopping
> > working
> > > (but then, if the USB subsyste

Re: USB trouble on Ryzen 3/AsRock mobo.

[Bob Willcox]

Hi Phil,

Thanks for the reply. I too have decided to replace the motherboard. Hopefully
the next one will behave better. I'm sure that these manufactures don't test
their products with FreeBSD.

Bob

On Mon, Feb 10, 2020 at 07:32:27AM +0100, Phil Norman wrote:
> Hi.
> 
> I'm afraid the best I could come up with is that the motherboard I was
> using is not standards-compliant, and has a broken USB system. This might
> explain why they insist you install their special drivers on Windows.
> 
> My solution was to replace the motherboard with one that actually works
> properly.
> 
> Cheers,
> Phil
> 
> On Sun, 9 Feb 2020 at 18:05, Bob Willcox  wrote:
> 
> > Hi Phil,
> >
> > Did you ever determine the cause and solution to the USB_ERR_TIMEOUT errors
> > you were getting? I just installed a recent 12.1 snapshot on a system with
> > a
> > Gigabyte GA-AB350N Ryzen motherboard and am seeing similar USB_ERR_TIMEOUT
> > errors with this MB.
> >
> > The errors on this system appear to be continuing forever as they have been
> > going on for over 30 minutes so far with no end in sight. On this system
> > the
> > initial dmesg messages for the usb errors looks strikingly similar to
> > yours:
> >
> > Feb  9 18:46:57 han kernel: xhci0: Resetting controller
> > Feb  9 18:46:57 han kernel: usb_alloc_device: set address 3 failed
> > (USB_ERR_TIMEOUT, ignored)
> > Feb  9 18:46:57 han kernel: Root mount waiting for: usbus0
> > Feb  9 18:46:57 han syslogd: last message repeated 1 times
> > Feb  9 18:46:57 han kernel: usbd_setup_device_desc: getting device
> > descriptor at addr 3 failed, USB_ERR_TIMEOUT
> > Feb  9 18:46:57 han kernel: Root mount waiting for: usbus0
> > Feb  9 18:46:57 han kernel: usbd_req_re_enumerate: addr=3, set address
> > failed! (USB_ERR_TIMEOUT, ignored)
> > Feb  9 18:46:57 han kernel: Root mount waiting for: usbus0
> > Feb  9 18:46:57 han syslogd: last message repeated 1 times
> > Feb  9 18:46:57 han kernel: usbd_setup_device_desc: getting device
> > descriptor at addr 3 failed, USB_ERR_TIMEOUT
> > Feb  9 18:46:57 han kernel: Root mount waiting for: usbus0
> > Feb  9 18:46:57 han kernel: usbd_req_re_enumerate: addr=3, set address
> > failed! (USB_ERR_TIMEOUT, ignored)
> > Feb  9 18:46:57 han kernel: Root mount waiting for: usbus0
> > Feb  9 18:46:57 han syslogd: last message repeated 1 times
> > Feb  9 18:46:57 han kernel: usbd_setup_device_desc: getting device
> > descriptor at addr 3 failed, USB_ERR_TIMEOUT
> > Feb  9 18:46:57 han kernel: Root mount waiting for: usbus0
> > Feb  9 18:46:57 han kernel: usbd_req_re_enumerate: addr=3, set address
> > failed! (USB_ERR_TIMEOUT, ignored)
> > Feb  9 18:46:57 han kernel: Root mount waiting for: usbus0
> > Feb  9 18:46:57 han kernel: usbd_setup_device_desc: getting device
> > descriptor at addr 3 failed, USB_ERR_TIMEOUT
> > Feb  9 18:46:57 han kernel: Root mount waiting for: usbus0
> > Feb  9 18:46:57 han syslogd: last message repeated 1 times
> > Feb  9 18:46:57 han kernel: usbd_req_re_enumerate: addr=3, set address
> > failed! (USB_ERR_TIMEOUT, ignored)
> > Feb  9 18:46:57 han kernel: Root mount waiting for: usbus0
> >
> > Anyone have any advice on what I can do the get this to stop? The system is
> > fundamentally unusable as it is.
> >
> > Thanks,
> > Bob
> >
> > On Tue, Jun 19, 2018 at 09:38:17PM +0200, Phil Norman wrote:
> > > Hi.
> > >
> > > I've recently converted to FreeBSD, fleeing the Windowsification of
> > Ubuntu.
> > > I've been having some trouble with the USB system, which seems strange as
> > > FreeBSD's USB stack is, according to a friend, rock solid. I'd like to
> > > narrow down if this is a hardware (CPU or mobo) or software issue.
> > >
> > > I'm running a Ryzen 3 1200, plugged into a "Fatal1ty X370 Gaming-ITX/ac"
> > > motherboard (chosen because it supports ECC RAM and fits in an ITX case).
> > >
> > > On a cold boot (ie starting by flipping the physical PSU power switch),
> > BSD
> > > boots up nice and quickly, without errors, and then runs for days
> > without a
> > > single USB-related error on dmesg. However, any other kind of reboot
> > which
> > > doesn't interrupt the electricity supply yields a large number of USB
> > > errors (USB_ERR_TIMEOUTs every few seconds or so) and frequent resets of
> > > the xhci0 controller.
> > >
> > > On occasion, I also get problems with my keyboard randomly stopping
> > working
> > > (but then, if the USB subsyste

Re: USB trouble on Ryzen 3/AsRock mobo.

[Bob Willcox]

Hi Phil,

Did you ever determine the cause and solution to the USB_ERR_TIMEOUT errors
you were getting? I just installed a recent 12.1 snapshot on a system with a
Gigabyte GA-AB350N Ryzen motherboard and am seeing similar USB_ERR_TIMEOUT
errors with this MB.

The errors on this system appear to be continuing forever as they have been
going on for over 30 minutes so far with no end in sight. On this system the
initial dmesg messages for the usb errors looks strikingly similar to yours:

Feb  9 18:46:57 han kernel: xhci0: Resetting controller
Feb  9 18:46:57 han kernel: usb_alloc_device: set address 3 failed 
(USB_ERR_TIMEOUT, ignored)
Feb  9 18:46:57 han kernel: Root mount waiting for: usbus0
Feb  9 18:46:57 han syslogd: last message repeated 1 times
Feb  9 18:46:57 han kernel: usbd_setup_device_desc: getting device descriptor 
at addr 3 failed, USB_ERR_TIMEOUT
Feb  9 18:46:57 han kernel: Root mount waiting for: usbus0
Feb  9 18:46:57 han kernel: usbd_req_re_enumerate: addr=3, set address failed! 
(USB_ERR_TIMEOUT, ignored)
Feb  9 18:46:57 han kernel: Root mount waiting for: usbus0
Feb  9 18:46:57 han syslogd: last message repeated 1 times
Feb  9 18:46:57 han kernel: usbd_setup_device_desc: getting device descriptor 
at addr 3 failed, USB_ERR_TIMEOUT
Feb  9 18:46:57 han kernel: Root mount waiting for: usbus0
Feb  9 18:46:57 han kernel: usbd_req_re_enumerate: addr=3, set address failed! 
(USB_ERR_TIMEOUT, ignored)
Feb  9 18:46:57 han kernel: Root mount waiting for: usbus0
Feb  9 18:46:57 han syslogd: last message repeated 1 times
Feb  9 18:46:57 han kernel: usbd_setup_device_desc: getting device descriptor 
at addr 3 failed, USB_ERR_TIMEOUT
Feb  9 18:46:57 han kernel: Root mount waiting for: usbus0
Feb  9 18:46:57 han kernel: usbd_req_re_enumerate: addr=3, set address failed! 
(USB_ERR_TIMEOUT, ignored)
Feb  9 18:46:57 han kernel: Root mount waiting for: usbus0
Feb  9 18:46:57 han kernel: usbd_setup_device_desc: getting device descriptor 
at addr 3 failed, USB_ERR_TIMEOUT
Feb  9 18:46:57 han kernel: Root mount waiting for: usbus0
Feb  9 18:46:57 han syslogd: last message repeated 1 times
Feb  9 18:46:57 han kernel: usbd_req_re_enumerate: addr=3, set address failed! 
(USB_ERR_TIMEOUT, ignored)
Feb  9 18:46:57 han kernel: Root mount waiting for: usbus0

Anyone have any advice on what I can do the get this to stop? The system is
fundamentally unusable as it is.

Thanks,
Bob

On Tue, Jun 19, 2018 at 09:38:17PM +0200, Phil Norman wrote:
> Hi.
> 
> I've recently converted to FreeBSD, fleeing the Windowsification of Ubuntu.
> I've been having some trouble with the USB system, which seems strange as
> FreeBSD's USB stack is, according to a friend, rock solid. I'd like to
> narrow down if this is a hardware (CPU or mobo) or software issue.
> 
> I'm running a Ryzen 3 1200, plugged into a "Fatal1ty X370 Gaming-ITX/ac"
> motherboard (chosen because it supports ECC RAM and fits in an ITX case).
> 
> On a cold boot (ie starting by flipping the physical PSU power switch), BSD
> boots up nice and quickly, without errors, and then runs for days without a
> single USB-related error on dmesg. However, any other kind of reboot which
> doesn't interrupt the electricity supply yields a large number of USB
> errors (USB_ERR_TIMEOUTs every few seconds or so) and frequent resets of
> the xhci0 controller.
> 
> On occasion, I also get problems with my keyboard randomly stopping working
> (but then, if the USB subsystem is continuously resetting, that's only to
> be expected). I also seem to get slow USB storage device read throughput
> (2MB/s from a USB3 SSD), although I can't rule out that being caused by the
> fuse ext4fs driver.
> 
> Here's what I see in dmesg when the USB system's in spam mode:
> 
> 
> xhci0: Resetting controller
> usb_alloc_device: set address 2 failed (USB_ERR_TIMEOUT, ignored)
> usbd_setup_device_desc: getting device descriptor at addr 2 failed,
> USB_ERR_TIMEOUT
> igb0: link state changed to UP
> usbd_req_re_enumerate: addr=2, set address failed! (USB_ERR_TIMEOUT,
> ignored)
> usbd_setup_device_desc: getting device descriptor at addr 2 failed,
> USB_ERR_TIMEOUT
> uhid0 on uhub3
> uhid0:  on
> usbus1
> uhid1 on uhub3
> uhid1:  1.10/1.22, addr 4> on usbus1
> ums0 on uhub2
> ums0:  on
> usbus1
> ums0: 3 buttons and [XYZ] coordinates ID=0
> usbd_req_re_enumerate: addr=2, set address failed! (USB_ERR_TIMEOUT,
> ignored)
> usbd_setup_device_desc: getting device descriptor at addr 2 failed,
> USB_ERR_TIMEOUT
> usbd_req_re_enumerate: addr=2, set address failed! (USB_ERR_TIMEOUT,
> ignored)
> usbd_setup_device_desc: getting device descriptor at addr 2 failed,
> USB_ERR_TIMEOUT
> usbd_req_re_enumerate: addr=2, set address failed! (USB_ERR_TIMEOUT,
> ignored)
> usbd_setup_device_desc: getting device descriptor at addr 2 failed,

Re: usb QR reader

[Daniel Braniss]

> On 16 Jan 2020, at 12:26, Hans Petter Selasky  wrote:
> 
> On 2020-01-16 11:23, Daniel Braniss wrote:
>> 63549 a.outCALL  openat(AT_FDCWD,0x1045b,0x2)
>> 63549 a.outNAMI  "/dev/ttyU0"
>> 63549 a.outRET   openat -1 errno 6 Device not configured
>> 63549 a.outCALL  nanosleep(0xbfbfec20,0xbfbfec10)
>> 63549 a.outRET   nanosleep 0
>> 63549 a.outCALL  writev(0x2,0xbfbfe408,0x4)
>> 63549 a.outGIO   fd 2 wrote 28 bytes
>>   "open: Device not configured
>> and the console:
>> Jan 16 12:17:14 neo-black-1 kernel: umodem_cfg_set_dtr: onoff=1
>> Jan 16 12:17:14 neo-black-1 kernel: umodem_cfg_set_rts: onoff=1
>> Jan 16 12:17:15 neo-black-1 kernel: umodem0: at uhub5, port 1, addr 2 
>> (disconnected)
>> Jan 16 12:17:15 neo-black-1 kernel: umodem_detach: sc=0xd494c400
>> Jan 16 12:17:16 neo-black-1 kernel: umodem_cfg_set_break: onoff=0
>> Jan 16 12:17:16 neo-black-1 kernel: umodem0: detached
>> Jan 16 12:17:23 neo-black-1 kernel: umodem_probe:
>> Jan 16 12:17:23 neo-black-1 syslogd: last message repeated 1 times
>> Jan 16 12:17:23 neo-black-1 kernel: umodem0 on uhub5
>> Jan 16 12:17:23 neo-black-1 kernel: umodem0: > class 2/0, rev 1.10/1.00, addr 2> on usbus5
>> Jan 16 12:17:23 neo-black-1 kernel: umodem0: data interface 1, has no CM 
>> over data, has no break
> 
> Also do:
> 
> ls /dev/cuaU*
looks fine
> 
> To make sure there are not multiple devices there!
> 
> Can you try to open up /dev/cuaU0 instead?
> 
> Same result?
> 

the open succeeds, but read returns 0, and the device is detached again.

i will now try the whole termcap stuff (speed, raw mode, etc)

danny



___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: usb QR reader

[Daniel Braniss]

> On 16 Jan 2020, at 12:26, Hans Petter Selasky  wrote:
> 
> On 2020-01-16 11:23, Daniel Braniss wrote:
>> 63549 a.outCALL  openat(AT_FDCWD,0x1045b,0x2)
>> 63549 a.outNAMI  "/dev/ttyU0"
>> 63549 a.outRET   openat -1 errno 6 Device not configured
>> 63549 a.outCALL  nanosleep(0xbfbfec20,0xbfbfec10)
>> 63549 a.outRET   nanosleep 0
>> 63549 a.outCALL  writev(0x2,0xbfbfe408,0x4)
>> 63549 a.outGIO   fd 2 wrote 28 bytes
>>   "open: Device not configured
>> and the console:
>> Jan 16 12:17:14 neo-black-1 kernel: umodem_cfg_set_dtr: onoff=1
>> Jan 16 12:17:14 neo-black-1 kernel: umodem_cfg_set_rts: onoff=1
>> Jan 16 12:17:15 neo-black-1 kernel: umodem0: at uhub5, port 1, addr 2 
>> (disconnected)
>> Jan 16 12:17:15 neo-black-1 kernel: umodem_detach: sc=0xd494c400
>> Jan 16 12:17:16 neo-black-1 kernel: umodem_cfg_set_break: onoff=0
>> Jan 16 12:17:16 neo-black-1 kernel: umodem0: detached
>> Jan 16 12:17:23 neo-black-1 kernel: umodem_probe:
>> Jan 16 12:17:23 neo-black-1 syslogd: last message repeated 1 times
>> Jan 16 12:17:23 neo-black-1 kernel: umodem0 on uhub5
>> Jan 16 12:17:23 neo-black-1 kernel: umodem0: > class 2/0, rev 1.10/1.00, addr 2> on usbus5
>> Jan 16 12:17:23 neo-black-1 kernel: umodem0: data interface 1, has no CM 
>> over data, has no break
> 
> Also do:
> 
> ls /dev/cuaU*
> 
> To make sure there are not multiple devices there!
> 
> Can you try to open up /dev/cuaU0 instead?
> 
> Same result?
> 
> --HPS

___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: usb QR reader

[Daniel Braniss]

> On 16 Jan 2020, at 12:12, Hans Petter Selasky  wrote:
> 
> On 2020-01-16 11:07, Daniel Braniss wrote:
>>> On 16 Jan 2020, at 11:16, Hans Petter Selasky  wrote:
>>> 
>>> ktracing
>> wrote a small c program, that just opens and tries to read, the open fails 
>> with
>>  ‘’open: Device not configured”
>> and the console shows:
>> Jan 16 11:59:09 neo-black-1 kernel: umodem0: detached
>> Jan 16 11:59:14 neo-black-1 kernel: ugen5.2:  at 
>> usbus5
>> Jan 16 11:59:14 neo-black-1 kernel: umodem_probe:
>> Jan 16 11:59:14 neo-black-1 syslogd: last message repeated 1 times
>> Jan 16 11:59:14 neo-black-1 kernel: umodem0 on uhub5
>> Jan 16 11:59:14 neo-black-1 kernel: umodem0: > class 2/0, rev 1.10/1.00, addr 2> on usbus5
>> Jan 16 11:59:14 neo-black-1 kernel: umodem0:
>> Jan 16 11:59:14 neo-black-1 kernel: data interface 1, has no CM over data, 
>> has no break
>> Jan 16 12:01:52 neo-black-1 kernel: umodem_cfg_set_dtr: onoff=1
>> Jan 16 12:01:52 neo-black-1 kernel: umodem_cfg_set_rts: onoff=1
>> Jan 16 12:01:53 neo-black-1 kernel: umodem0: at uhub5, port 1, addr 2 
>> (disconnected)
>> Jan 16 12:01:53 neo-black-1 kernel: umodem_detach: sc=0xd494c400
>> Jan 16 12:01:54 neo-black-1 kernel: umodem_cfg_set_break: onoff=0
>> Jan 16 12:01:54 neo-black-1 kernel: umodem0: detached
>> Jan 16 12:02:01 neo-black-1 kernel: umodem_probe:
>> Jan 16 12:02:01 neo-black-1 syslogd: last message repeated 1 times
>> Jan 16 12:02:01 neo-black-1 kernel: umodem0 on uhub5
>> Jan 16 12:02:01 neo-black-1 kernel: umodem0: > class 2/0, rev 1.10/1.00, addr 2> on usbus5
>> Jan 16 12:02:01 neo-black-1 kernel: umodem0: data interface 1, has no CM 
>> over data, has no break
> 
> Can you put a sleep call in your c-program, like 1 second?
> 
> --HPS
63549 a.outCALL  openat(AT_FDCWD,0x1045b,0x2)
63549 a.outNAMI  "/dev/ttyU0"
63549 a.outRET   openat -1 errno 6 Device not configured
63549 a.outCALL  nanosleep(0xbfbfec20,0xbfbfec10)
63549 a.outRET   nanosleep 0
63549 a.outCALL  writev(0x2,0xbfbfe408,0x4)
63549 a.outGIO   fd 2 wrote 28 bytes
  "open: Device not configured

and the console:
Jan 16 12:17:14 neo-black-1 kernel: umodem_cfg_set_dtr: onoff=1
Jan 16 12:17:14 neo-black-1 kernel: umodem_cfg_set_rts: onoff=1
Jan 16 12:17:15 neo-black-1 kernel: umodem0: at uhub5, port 1, addr 2 
(disconnected)
Jan 16 12:17:15 neo-black-1 kernel: umodem_detach: sc=0xd494c400
Jan 16 12:17:16 neo-black-1 kernel: umodem_cfg_set_break: onoff=0
Jan 16 12:17:16 neo-black-1 kernel: umodem0: detached
Jan 16 12:17:23 neo-black-1 kernel: umodem_probe: 
Jan 16 12:17:23 neo-black-1 syslogd: last message repeated 1 times
Jan 16 12:17:23 neo-black-1 kernel: umodem0 on uhub5
Jan 16 12:17:23 neo-black-1 kernel: umodem0:  on usbus5
Jan 16 12:17:23 neo-black-1 kernel: umodem0: data interface 1, has no CM over 
data, has no break

___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: usb QR reader

[Daniel Braniss]

> On 16 Jan 2020, at 11:16, Hans Petter Selasky  wrote:
> 
> ktracing

wrote a small c program, that just opens and tries to read, the open fails with
‘’open: Device not configured”

and the console shows:
Jan 16 11:59:09 neo-black-1 kernel: umodem0: detached
Jan 16 11:59:14 neo-black-1 kernel: ugen5.2:  at 
usbus5
Jan 16 11:59:14 neo-black-1 kernel: umodem_probe: 
Jan 16 11:59:14 neo-black-1 syslogd: last message repeated 1 times
Jan 16 11:59:14 neo-black-1 kernel: umodem0 on uhub5
Jan 16 11:59:14 neo-black-1 kernel: umodem0:  on usbus5
Jan 16 11:59:14 neo-black-1 kernel: umodem0: 
Jan 16 11:59:14 neo-black-1 kernel: data interface 1, has no CM over data, has 
no break
Jan 16 12:01:52 neo-black-1 kernel: umodem_cfg_set_dtr: onoff=1
Jan 16 12:01:52 neo-black-1 kernel: umodem_cfg_set_rts: onoff=1
Jan 16 12:01:53 neo-black-1 kernel: umodem0: at uhub5, port 1, addr 2 
(disconnected)
Jan 16 12:01:53 neo-black-1 kernel: umodem_detach: sc=0xd494c400
Jan 16 12:01:54 neo-black-1 kernel: umodem_cfg_set_break: onoff=0
Jan 16 12:01:54 neo-black-1 kernel: umodem0: detached
Jan 16 12:02:01 neo-black-1 kernel: umodem_probe: 
Jan 16 12:02:01 neo-black-1 syslogd: last message repeated 1 times
Jan 16 12:02:01 neo-black-1 kernel: umodem0 on uhub5
Jan 16 12:02:01 neo-black-1 kernel: umodem0:  on usbus5
Jan 16 12:02:01 neo-black-1 kernel: umodem0: data interface 1, has no CM over 
data, has no break
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: usb QR reader

[Daniel Braniss]

> On 6 Jan 2020, at 00:32, Hans Petter Selasky  wrote:
> 
> On 2020-01-05 18:03, Daniel Braniss wrote:
>>> On 5 Jan 2020, at 17:08, Hans Petter Selasky  wrote:
>>> 
>>> On 2020-01-05 15:32, Daniel Braniss wrote:
>>>> status 0x6a1a3 
>>>> 
>>>> 16:25:17.790304 usbus5.2 SUBM-CTRL-EP=,SPD=FULL,NFR=1,SLEN=8,IVAL=0
>>>> frame[0] WRITE 8 bytes
>>>>   21 22 03 00 00 00 00 00  -- -- -- -- -- -- -- --  |!"..|
>>>> flags 0x10 
>>>> status 0x4a1a3 
>>>> 
>>>> 16:25:17.790346 usbus5.2 
>>>> DONE-CTRL-EP=,SPD=FULL,NFR=0,SLEN=0,IVAL=50,ERR=TIMEOUT
>>>> flags 0 <0>
>>>> status 0x8a1a5 
>>>> 
>>>> 16:25:18.797312 usbus5.2 
>>>> DONE-CTRL-EP=,SPD=FULL,NFR=0,SLEN=0,IVAL=0,ERR=TIMEOUT
>>>> flags 0x10 
>>> 
>>> Hi,
>>> 
>>> There are some USB requests your USB device doesn't respond to. ERR=TIMEOUT
>>> 
>>> You might find the corresponding driver and enable .debug=16 under :
>>> 
>>> sysctl hw.usb | grep debug
>>> 
>>> To get more information what exactly goes wrong.
>>> 
> 
> Did you compile the kernel with options USB_DEBUG ?
> 
> Now hw.usb.debug, but hw.usb.umodem.debug, for example.
> 
> --HPS
real events took over, so now:

connecting the device:
Jan 16 11:05:28 neo-black-1 kernel: ugen5.2:  at 
usbus5 (disconnected)
Jan 16 11:05:28 neo-black-1 kernel: umodem0: at uhub5, port 1, addr 2 
(disconnected)
Jan 16 11:05:28 neo-black-1 kernel: umodem_detach: sc=0xd494c400
Jan 16 11:05:28 neo-black-1 kernel: umodem0: detached
Jan 16 11:05:36 neo-black-1 kernel: ugen5.2:  at 
usbus5
Jan 16 11:05:36 neo-black-1 kernel: umodem_probe: 
Jan 16 11:05:36 neo-black-1 syslogd: last message repeated 1 times
Jan 16 11:05:36 neo-black-1 kernel: umodem0 on uhub5
Jan 16 11:05:36 neo-black-1 kernel: umodem0:  on usbus5
Jan 16 11:05:36 neo-black-1 kernel: umodem0: 
Jan 16 11:05:36 neo-black-1 kernel: data interface 1, has no CM over data, has 
no break

trying to open it:
Jan 16 11:06:34 neo-black-1 kernel: umodem_cfg_set_dtr: onoff=1
Jan 16 11:06:34 neo-black-1 kernel: umodem_ioctl: cmd=0x402c7413
Jan 16 11:06:34 neo-black-1 kernel: umodem_ioctl: unknown
Jan 16 11:06:34 neo-black-1 kernel: umodem_cfg_set_rts: onoff=1
Jan 16 11:06:34 neo-black-1 kernel: umodem_ioctl: cmd=0x802c7416
Jan 16 11:06:34 neo-black-1 kernel: umodem_ioctl: unknown
Jan 16 11:06:34 neo-black-1 kernel: umodem_ioctl: cmd=0x2000740d
Jan 16 11:06:34 neo-black-1 kernel: umodem_ioctl: unknown
Jan 16 11:06:34 neo-black-1 kernel: umodem_ioctl: cmd=0x402c7413
Jan 16 11:06:34 neo-black-1 kernel: umodem_ioctl: unknown
Jan 16 11:06:34 neo-black-1 kernel: umodem_ioctl: cmd=0x802c7416
Jan 16 11:06:34 neo-black-1 kernel: umodem_ioctl: unknown
Jan 16 11:06:34 neo-black-1 kernel: umodem_ioctl: cmd=0x8004667e
Jan 16 11:06:34 neo-black-1 kernel: umodem_ioctl: unknown
Jan 16 11:06:34 neo-black-1 kernel: umodem_ioctl: cmd=0x8004667d
Jan 16 11:06:34 neo-black-1 kernel: umodem_ioctl: unknown
Jan 16 11:06:35 neo-black-1 kernel: umodem0: at uhub5, port 1, addr 2 
(disconnected)
Jan 16 11:06:35 neo-black-1 kernel: umodem_detach: sc=0xd494c400
Jan 16 11:06:36 neo-black-1 kernel: umodem_cfg_set_break: onoff=0
Jan 16 11:06:36 neo-black-1 kernel: umodem0: detached
Jan 16 11:06:42 neo-black-1 kernel: umodem_probe: 
Jan 16 11:06:42 neo-black-1 syslogd: last message repeated 1 times
Jan 16 11:06:42 neo-black-1 kernel: umodem0 on uhub5
Jan 16 11:06:42 neo-black-1 kernel: umodem0:  on usbus5
Jan 16 11:06:42 neo-black-1 kernel: umodem0: data interface 1, has no CM over 
data, has no break

cheers,
danny


___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: usb QR reader

[Daniel Braniss]

> On 5 Jan 2020, at 17:08, Hans Petter Selasky  wrote:
> 
> On 2020-01-05 15:32, Daniel Braniss wrote:
>> status 0x6a1a3 
>> 
>> 16:25:17.790304 usbus5.2 SUBM-CTRL-EP=,SPD=FULL,NFR=1,SLEN=8,IVAL=0
>> frame[0] WRITE 8 bytes
>>   21 22 03 00 00 00 00 00  -- -- -- -- -- -- -- --  |!"..|
>> flags 0x10 
>> status 0x4a1a3 
>> 
>> 16:25:17.790346 usbus5.2 
>> DONE-CTRL-EP=,SPD=FULL,NFR=0,SLEN=0,IVAL=50,ERR=TIMEOUT
>> flags 0 <0>
>> status 0x8a1a5 
>> 
>> 16:25:18.797312 usbus5.2 
>> DONE-CTRL-EP=00000000,SPD=FULL,NFR=0,SLEN=0,IVAL=0,ERR=TIMEOUT
>> flags 0x10 
> 
> Hi,
> 
> There are some USB requests your USB device doesn't respond to. ERR=TIMEOUT
> 
> You might find the corresponding driver and enable .debug=16 under :
> 
> sysctl hw.usb | grep debug
> 
> To get more information what exactly goes wrong.
> 
> —HPS

did that:
sysctl hw.usb.debug=16
but can’t see any changes, /var/log/messages seems the same as before,
BTW, the device works fine when I connect it to a mac, so it must be something 
in the umodem0

cheers,
danny
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: usb QR reader

[Daniel Braniss]

> On 3 Jan 2020, at 13:05, Hans Petter Selasky  wrote:
> 
> On 2020-01-03 11:56, Daniel Braniss wrote:
>> Hi Hans,
>> can you shed some light/help?
>> thanks,
>>  danny
>>> On 2 Jan 2020, at 11:11, Daniel Braniss  wrote:
>>> 
>>> Hi,
>>> after connecting this QR reader I see a new /dev/ttyU but as soon as I try 
>>> tip,
>>> the device disconnects. (BTW, it’s configured as a ‘Virtual Serial Port’)
>>> 
>>> dmsg:
>>> …
>>> Jan  2 10:54:57 pampero kernel: umodem0 on uhub1
>>> Jan  2 10:54:57 pampero kernel: umodem0: >> 2/0, rev 1.10/1.00, addr 38> on usbus0
>>> Jan  2 10:54:57 pampero kernel: umodem0: data interface 1, has no CM over 
>>> data, has no break
>>> Jan  2 10:56:01 pampero kernel: umodem0: at uhub1, port 2, addr 38 
>>> (disconnected)
>>> Jan  2 10:56:02 pampero kernel: umodem0:
>>> Jan  2 10:56:02 pampero kernel: detached
>>> Jan  2 10:56:03 pampero kernel: umodem0 on uhub1
>>> Jan  2 10:56:03 pampero kernel: umodem0: >> 2/0, rev 1.10/1.00, addr 38> on usbus0
>>> Jan  2 10:56:03 pampero kernel: umodem0: data interface 1, has no CM over 
>>> data, has no break
>>> …
>>> 
>>> and usbconfig:
>>> pampero# usbconfig
>>> ugen0.1: <0x8086 XHCI root HUB> at usbus0, cfg=0 md=HOST spd=SUPER 
>>> (5.0Gbps) pwr=SAVE (0mA)
>>> ugen0.2:  at usbus0, cfg=0 md=HOST spd=HIGH 
>>> (480Mbps) pwr=SAVE (500mA)
>>> ugen0.4:  at usbus0, cfg=0 md=HOST spd=FULL (12Mbps) 
>>> pwr=ON (98mA)
>>> ugen0.5:  at usbus0, cfg=0 
>>> md=HOST spd=FULL (12Mbps) pwr=ON (100mA)
>>> ugen0.6:  at usbus0, cfg=0 md=HOST spd=SUPER 
>>> (5.0Gbps) pwr=SAVE (0mA)
>>> ugen0.3:  at usbus0, 
>>> cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON (100mA)
>>> ugen0.7:  at usbus0, cfg=0 md=HOST spd=FULL 
>>> (12Mbps) pwr=ON (100mA) <— this is the QR
>>> 
>>> any ideas?
> 
> Can you run:
> 
> usbdump -i usbus0 -f 7 -s 65536 -vvv
> 
> Before attaching the device. Make sure numbers after ugen are 0 and 7. Look 
> for non ERR=0 .
> 
> —HPS


so I connected the QR reader to another host, running 12.1 stable.

neo-black-2# usbconfig
ugen0.1:  at usbus0, cfg=0 md=HOST spd=HIGH (480Mbps) 
pwr=SAVE (0mA)
ugen1.1:  at usbus1, cfg=0 md=HOST spd=FULL (12Mbps) 
pwr=SAVE (0mA)
ugen2.1:  at usbus2, cfg=0 md=HOST spd=HIGH (480Mbps) 
pwr=SAVE (0mA)
ugen3.1:  at usbus3, cfg=0 md=HOST spd=FULL (12Mbps) 
pwr=SAVE (0mA)
ugen4.1:  at usbus4, cfg=0 md=HOST spd=HIGH (480Mbps) 
pwr=SAVE (0mA)
ugen5.1:  at usbus5, cfg=0 md=HOST spd=FULL (12Mbps) 
pwr=SAVE (0mA)
ugen5.2:  at usbus5, cfg=0 md=HOST spd=FULL (12Mbps) 
pwr=ON (100mA)


and so i did 
neo-black-2# usbdump -i usbus5 -f2 -s 65536 -vvv

nothing happens, so this is what I get after typing ’tip usb’ and nothing else 
- i don’t know who is doing the chitchat and after a very short while it 
disconnects.

16:25:16.753606 usbus5.2 SUBM-INTR-EP=0082,SPD=FULL,NFR=1,SLEN=0,IVAL=5
frame[0] READ 64 bytes
flags 0x8a 
status 0xeb023 

16:25:16.753645 usbus5.2 SUBM-CTRL-EP=,SPD=FULL,NFR=1,SLEN=8,IVAL=0
frame[0] WRITE 8 bytes
  21 22 01 00 00 00 00 00  -- -- -- -- -- -- -- --  |!"..|
flags 0x10 
status 0xea1a3 

16:25:16.755271 usbus5.2 
DONE-CTRL-EP=,SPD=FULL,NFR=1,SLEN=0,IVAL=0,ERR=0
frame[0] WRITE 8 bytes
flags 0x10 
status 0xca1a1 

16:25:16.808281 usbus5.2 SUBM-CTRL-EP=,SPD=FULL,NFR=1,SLEN=8,IVAL=50
frame[0] WRITE 8 bytes
  02 01 00 00 81 00 00 00  -- -- -- -- -- -- -- --  ||
flags 0 <0>
status 0x6a1a3 

16:25:17.790304 usbus5.2 SUBM-CTRL-EP=,SPD=FULL,NFR=1,SLEN=8,IVAL=0
frame[0] WRITE 8 bytes
  21 22 03 00 00 00 00 00  -- -- -- -- -- -- -- --  |!"..|
flags 0x10 
status 0x4a1a3 

16:25:17.790346 usbus5.2 
DONE-CTRL-EP=,SPD=FULL,NFR=0,SLEN=0,IVAL=50,ERR=TIMEOUT
flags 0 <0>
status 0x8a1a5 

16:25:18.797312 usbus5.2 
DONE-CTRL-EP=,SPD=FULL,NFR=0,SLEN=0,IVAL=0,ERR=TIMEOUT
flags 0x10 
status 0xaa1a5 

16:25:18.850220 usbus5.2 SUBM-CTRL-EP=,SPD=FULL,NFR=1,SLEN=8,IVAL=50
frame[0] WRITE 8 bytes
  02 01 00 00 81 00 00 00  -- -- -- -- -- -- -- --  ||
flags 0 <0>
status 0x4a1a3 

16:25:18.867314 usbus5.2 
DONE-BULK-EP=0081,SPD=FULL,NFR=0,SLEN=0,IVAL=0,ERR=CANCELLED
flags 0xa 
status 0xab00c 

16:25:18.867332 usbus5.2 
DONE-INTR-EP=0082,SPD=FULL,NFR=0,SLEN=0,IVAL=5,ERR=CANCELLED
flags 0x8a 
status 0x8b01c 

16:25:19.854309 usbus5.2 SUBM-CTRL-EP=,SPD=FULL,NFR=1,SLEN=8,IVAL=0
frame[0] WRITE 8 bytes
  00 09 00 00 00 00 00 00  -- -- -- -- -- -- -- --  ||
flags 0x10 
status 0x6a1a3 

16:25:19.854355 usbus5.

Re: usb QR reader

[Daniel Braniss]

Hi Hans, 
can you shed some light/help?

thanks,
danny


> On 2 Jan 2020, at 11:11, Daniel Braniss  wrote:
> 
> Hi, 
> after connecting this QR reader I see a new /dev/ttyU but as soon as I try 
> tip,
> the device disconnects. (BTW, it’s configured as a ‘Virtual Serial Port’)
> 
> dmsg:
> …
> Jan  2 10:54:57 pampero kernel: umodem0 on uhub1
> Jan  2 10:54:57 pampero kernel: umodem0:  2/0, rev 1.10/1.00, addr 38> on usbus0
> Jan  2 10:54:57 pampero kernel: umodem0: data interface 1, has no CM over 
> data, has no break
> Jan  2 10:56:01 pampero kernel: umodem0: at uhub1, port 2, addr 38 
> (disconnected)
> Jan  2 10:56:02 pampero kernel: umodem0: 
> Jan  2 10:56:02 pampero kernel: detached
> Jan  2 10:56:03 pampero kernel: umodem0 on uhub1
> Jan  2 10:56:03 pampero kernel: umodem0:  2/0, rev 1.10/1.00, addr 38> on usbus0
> Jan  2 10:56:03 pampero kernel: umodem0: data interface 1, has no CM over 
> data, has no break
> …
> 
> and usbconfig:
> pampero# usbconfig
> ugen0.1: <0x8086 XHCI root HUB> at usbus0, cfg=0 md=HOST spd=SUPER (5.0Gbps) 
> pwr=SAVE (0mA)
> ugen0.2:  at usbus0, cfg=0 md=HOST spd=HIGH 
> (480Mbps) pwr=SAVE (500mA)
> ugen0.4:  at usbus0, cfg=0 md=HOST spd=FULL (12Mbps) 
> pwr=ON (98mA)
> ugen0.5:  at usbus0, cfg=0 
> md=HOST spd=FULL (12Mbps) pwr=ON (100mA)
> ugen0.6:  at usbus0, cfg=0 md=HOST spd=SUPER 
> (5.0Gbps) pwr=SAVE (0mA)
> ugen0.3:  at usbus0, cfg=0 
> md=HOST spd=FULL (12Mbps) pwr=ON (100mA)
> ugen0.7:  at usbus0, cfg=0 md=HOST spd=FULL 
> (12Mbps) pwr=ON (100mA) <— this is the QR
> 
> any ideas?
> 
> thanks,
>   danny
> 
> ___
> freebsd-stable@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-stable
> To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

usb QR reader

[Daniel Braniss]

Hi, 
after connecting this QR reader I see a new /dev/ttyU but as soon as I try tip,
the device disconnects. (BTW, it’s configured as a ‘Virtual Serial Port’)

dmsg:
…
Jan  2 10:54:57 pampero kernel: umodem0 on uhub1
Jan  2 10:54:57 pampero kernel: umodem0:  on usbus0
Jan  2 10:54:57 pampero kernel: umodem0: data interface 1, has no CM over data, 
has no break
Jan  2 10:56:01 pampero kernel: umodem0: at uhub1, port 2, addr 38 
(disconnected)
Jan  2 10:56:02 pampero kernel: umodem0: 
Jan  2 10:56:02 pampero kernel: detached
Jan  2 10:56:03 pampero kernel: umodem0 on uhub1
Jan  2 10:56:03 pampero kernel: umodem0:  on usbus0
Jan  2 10:56:03 pampero kernel: umodem0: data interface 1, has no CM over data, 
has no break
…

and usbconfig:
pampero# usbconfig
ugen0.1: <0x8086 XHCI root HUB> at usbus0, cfg=0 md=HOST spd=SUPER (5.0Gbps) 
pwr=SAVE (0mA)
ugen0.2:  at usbus0, cfg=0 md=HOST spd=HIGH (480Mbps) 
pwr=SAVE (500mA)
ugen0.4:  at usbus0, cfg=0 md=HOST spd=FULL (12Mbps) 
pwr=ON (98mA)
ugen0.5:  at usbus0, cfg=0 
md=HOST spd=FULL (12Mbps) pwr=ON (100mA)
ugen0.6:  at usbus0, cfg=0 md=HOST spd=SUPER (5.0Gbps) 
pwr=SAVE (0mA)
ugen0.3:  at usbus0, cfg=0 
md=HOST spd=FULL (12Mbps) pwr=ON (100mA)
ugen0.7:  at usbus0, cfg=0 md=HOST spd=FULL (12Mbps) 
pwr=ON (100mA) <— this is the QR

any ideas?

thanks,
danny

___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Boot fails with USB 3.0 external harddrive plugged in

[Freddie Cash]

[fcash@rogue /home/fcash]$ freebsd-version -ku
12.0-RELEASE-p8
12.0-RELEASE-p8

This system was previously running FreeBSD 11.2 and didn't have any issues
booting with the external USB drive plugged into the USB 3.0 ports on the
motherboard.

Ever since upgrading to 12.0, and through all the updates to -p8, booting
with the external drive plugged in fails.  It will eventually get through
the loader, start to load the kernel, then drop to a black screen, and
(after a few minutes) power off the system completely.

The boot process is *extremely* slow with the USB drive plugged in.  As in,
you can watch the loader cursor twirl at about 1 frame every few seconds.

However, if I am sitting at the computer, I can press any key on the
keyboard (even shift, ctrl, alt, or spacebar), and it will make the cursor
spin at a normal speed for a second or two.  So, if I hit a key on the
keyboard every other second, it will go through a normal boot process.

I seem to recall there was a similar issue on the mailing list a couple
months back, but my google-fu is failing me.  :(  I thought there was a
loader.conf setting that resolved that issue, but I can't seem to find it.

If I unplug the external drive, it boots normally without any user
intervention.  Connecting the drive after the login prompt appears,
everything works normally. It's only the boot process that is an issue.

This is an olded system, using an AMD Phenom-II quad-core CPU, but has 16
GB of RAM, and 6 harddrives in a ZFS pool.  Has been working great, up
until the 12.0 upgrade.

I have plans to upgrade this system to 12.1 later this month.  Just
wondering if this is a known issue that's fixed in that release, or
something new.

xhci0:  mem 0xfe80-0xfe807fff irq
46 at device 0.0 on pci2
xhci0: 32 bytes context size, 32-bit DMA
xhci0: Unable to map MSI-X table
usbus0 on xhci0
xhci1:  mem 0xfe60-0xfe607fff irq
50 at device 0.0 on pci4
xhci1: 32 bytes context size, 32-bit DMA
xhci1: Unable to map MSI-X table
usbus1 on xhci1
ohci0:  mem 0xfe90a000-0xfe90afff irq
18 at device 18.0 on pci0
usbus2 on ohci0
ehci0:  mem 0xfe909000-0xfe9090ff
irq 17 at device 18.2 on pci0
usbus3 on ehci0
ohci1:  mem 0xfe908000-0xfe908fff irq
20 at device 19.0 on pci0
usbus4 on ohci1
ehci1:  mem 0xfe907000-0xfe9070ff
irq 21 at device 19.2 on pci0
usbus5 on ehci1
ohci2:  mem 0xfe906000-0xfe906fff irq
18 at device 20.5 on pci0
usbus6 on ohci2
ohci3:  mem 0xfe905000-0xfe905fff irq
22 at device 22.0 on pci0
usbus7 on ohci3
ehci2:  mem 0xfe904000-0xfe9040ff
irq 23 at device 22.2 on pci0
usbus8 on ehci2
da0 at umass-sim0 bus 0 scbus12 target 0 lun 0
da0:  Fixed Direct Access SPC-3 SCSI device
da0: Serial Number Z297HW2Q
da0: 400.000MB/s transfers
da0: 2861588MB (5860533168 512 byte sectors)
da0: quirks=0x2

-- 
Freddie Cash
fjwc...@gmail.com
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: Can someone MFC usb/234503

[Warner Losh]

On Fri, Apr 19, 2019 at 2:55 AM Mel Pilgrim 
wrote:

> This is still waiting for MFC to stable/11 and stable/12.  Would someone
> please have a look at it?  Warner Losh has timed out.
>

Just merged it.

Warner
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: Can someone MFC usb/234503

[Mel Pilgrim]

This is still waiting for MFC to stable/11 and stable/12.  Would someone 
please have a look at it?  Warner Losh has timed out.

___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Can someone MFC usb/234503

[Mel Pilgrim]

The patch was committed to head on March 11 and flagged for MFC, but it 
hasn't be merged to stable yet.  I've been running this modification on 
11.2-R and 12.0-R using the affected devices as system disks for a 
little over two months without issue.  Can someone merge this into 
stable/11 and stable/12?  It's important (to me, at least) that it make 
it into 11.3-R, and the slush for it isn't far off.

___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Would someone commit the revised patch in usb/234503, please

[Mel Pilgrim]

usb/234503 contains a patch to broaden the scope of an existing scsi_da 
quirk (attachment labeled "Patch to broaden quirk coverage to all 
Chipfancier devices").  It's a minor change, but it's a showstopper for 
me and I need to see it get into 11-stable ahead of 11.3-R and 12-stable 
ahead of 12.1-R.


Would someone have a look at it and commit it?

Thank you
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: USB disks dropping off-line

[Kevin Oberman]

On Sat, Jan 12, 2019 at 9:12 AM Barney Wolff  wrote:

> I've had what may be the same problem for years, with a USB3 disk, on both
> 10-stable and 12.0-release. I've never found a cause, though power gitches
> might be responsible. As a pragmatic fix I have the backup disk as a zpool
> and run a daemon that simply does a zpool clear if it finds the pool
> unhealthy during the backup. That lets the backup complete every time - the
> pool is set to wait on error, so having the daemon check once a minute
> works with minuscule overhead.
>
> On Fri, Jan 11, 2019 at 11:31:55PM -0800, Kevin Oberman wrote:
> > Cue Twilight Zone theme. For your consideration: This started in
> December
> > when I was running 11.2-STABLE. Starting in December, when I try to
> backup
> > my laptop to a USB drive, it periodically dropped off-line (disconnected)
> > and immediately reconnected. This was originally using rsync. It seemed
> > fairly random and, eventually I got a successful backup. After I upgraded
> > to 12.0, it was much worse and I could no longer get a clean rsync.
> >
> > I assumed that the drive was failing and swapped it for an identical one,
> > re-partitioned, and used dd to copy each partition. The same thing
> > happened, but I noticed that it seemed to happen when the system was a
> bit
> > active. I then shutdown X and tried with nothing else running. It ran
> for a
> > few minutes until I did a sync from a different login while the dd was
> > running. Boom. Disk disconnected again.
> >
> > I finally got an almost complete backup of /usr. I had about 1-2 GB lest
> > when it happened again. I suspect that some background operation
> (periodic
> > sync?) triggered it again.
> >
> > Any suggestions?
> >
> > Here is my system info: Lenovo T520 now running FreeBSD 12.0-STABLE
> r342788
> > and GENERIC config except SCHED_4BSD. System is completely stable except
> > for the USB disk dropping off-line. Disk is a 2TB WD My Passport. It is a
> > USB 3.0 drive,but plugged intoa 2.0 port. (The T520 has no 3.0
> capability.
> >
> > Has anyone seen anything like this? Any ideas? I am REALLY nervous
> running
> > without a backup.
>

I have now confirmed that the dd runs with no issues when run in
stand-alone mode. As long as the system makes no other disk access, it
appears that the disk runs fine.  I will drop back to single-user and dd my
media (mostly music including music videos) later today and my 600 GB bulk
data disk overnight tonight. At about an hour per 100 gig, it will take a
while. I expect all to runs cleanly and I wish I had a USB3 port on this
system!
--
Kevin Oberman, Part time kid herder and retired Network Engineer
E-mail: rkober...@gmail.com
PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: USB disks dropping off-line

[Eugene Grosbein]

13.01.2019 0:12, Barney Wolff wrote:

> On Fri, Jan 11, 2019 at 11:31:55PM -0800, Kevin Oberman wrote:
>> Que Twilight Zone theme. For your consideration: This started in December
>> when I was running 11.2-STABLE. Starting in December, when I try to backup
>> my laptop to a USB drive, it periodically dropped off-line (disconnected)
>> and immediately reconnected. This was originally using rsync. It seemed
>> fairly random and, eventually I got a successful backup. After I upgraded
>> to 12.0, it was much worse and I could no longer get a clean rsync.
>>
>> I assumed that the drive was failing and swapped it for an identical one,
>> re-partitioned, and used dd to copy each partition. The same thing
>> happened, but I noticed that it seemed to happen when the system was a bit
>> active. I then shutdown X and tried with nothing else running. It ran for a
>> few minutes until I did a sync from a different login while the dd was
>> running. Boom. Disk disconnected again.
>>
>> I finally got an almost complete backup of /usr. I had about 1-2 GB lest
>> when it happened again. I suspect that some background operation (periodic
>> sync?) triggered it again.
>>
>> Any suggestions?
>>
>> Here is my system info: Lenovo T520 now running FreeBSD 12.0-STABLE r342788
>> and GENERIC config except SCHED_4BSD. System is completely stable except
>> for the USB disk dropping off-line. Disk is a 2TB WD My Passport. It is a
>> USB 3.0 drive,but plugged intoa 2.0 port. (The T520 has no 3.0 capability.
>>
>> Has anyone seen anything like this? Any ideas? I am REALLY nervous running
>> without a backup.

> I've had what may be the same problem for years, with a USB3 disk,
> on both 10-stable and 12.0-release. I've never found a cause, though power
> gitches might be responsible. As a pragmatic fix I have the backup disk as a 
> zpool
> and run a daemon that simply does a zpool clear if it finds the pool 
> unhealthy during the backup.
> That lets the backup complete every time - the pool is set to wait on error,
> so having the daemon check once a minute works with minuscule overhead.

I had same problem for several years with non-changing set of hardware
(integrated USB 2.0 controller and external USB HDD) and several FreeBSD 
versions
from 8.x and newer. It just stopped disappearing after one of software upgrades
so I presume instability of our USB stack for some edge cases. Now it works 
just fine
for my hardware and 11.2-STABLE.

Anyway, we have gmountver(8) for temporary work-around:

DESCRIPTION
 The gmountver utility is used to control the mount verification GEOM
 class.  When configured, it passes all the I/O requests to the underlying
 provider.  When the underlying provider disappears - for example because
 the disk device got disconnected - it queues all the I/O requests and
 waits for the provider to reappear.  When that happens, it attaches to it
 and sends the queued requests.

___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: USB disks dropping off-line

[Barney Wolff]

I've had what may be the same problem for years, with a USB3 disk, on both 
10-stable and 12.0-release. I've never found a cause, though power gitches 
might be responsible. As a pragmatic fix I have the backup disk as a zpool and 
run a daemon that simply does a zpool clear if it finds the pool unhealthy 
during the backup. That lets the backup complete every time - the pool is set 
to wait on error, so having the daemon check once a minute works with minuscule 
overhead.

On Fri, Jan 11, 2019 at 11:31:55PM -0800, Kevin Oberman wrote:
> Que Twilight Zone theme. For your consideration: This started in December
> when I was running 11.2-STABLE. Starting in December, when I try to backup
> my laptop to a USB drive, it periodically dropped off-line (disconnected)
> and immediately reconnected. This was originally using rsync. It seemed
> fairly random and, eventually I got a successful backup. After I upgraded
> to 12.0, it was much worse and I could no longer get a clean rsync.
> 
> I assumed that the drive was failing and swapped it for an identical one,
> re-partitioned, and used dd to copy each partition. The same thing
> happened, but I noticed that it seemed to happen when the system was a bit
> active. I then shutdown X and tried with nothing else running. It ran for a
> few minutes until I did a sync from a different login while the dd was
> running. Boom. Disk disconnected again.
> 
> I finally got an almost complete backup of /usr. I had about 1-2 GB lest
> when it happened again. I suspect that some background operation (periodic
> sync?) triggered it again.
> 
> Any suggestions?
> 
> Here is my system info: Lenovo T520 now running FreeBSD 12.0-STABLE r342788
> and GENERIC config except SCHED_4BSD. System is completely stable except
> for the USB disk dropping off-line. Disk is a 2TB WD My Passport. It is a
> USB 3.0 drive,but plugged intoa 2.0 port. (The T520 has no 3.0 capability.
> 
> Has anyone seen anything like this? Any ideas? I am REALLY nervous running
> without a backup.
> --
> Kevin Oberman, Part time kid herder and retired Network Engineer
> E-mail: rkober...@gmail.com
> PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683
> ___
> freebsd-stable@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-stable
> To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

-- 
Forcing a woman to bear a child against her will is the moral equivalent of 
rape.
Resist. Persist.
We shall overwhelm.
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

USB disks dropping off-line

[Kevin Oberman]

Que Twilight Zone theme. For your consideration: This started in December
when I was running 11.2-STABLE. Starting in December, when I try to backup
my laptop to a USB drive, it periodically dropped off-line (disconnected)
and immediately reconnected. This was originally using rsync. It seemed
fairly random and, eventually I got a successful backup. After I upgraded
to 12.0, it was much worse and I could no longer get a clean rsync.

I assumed that the drive was failing and swapped it for an identical one,
re-partitioned, and used dd to copy each partition. The same thing
happened, but I noticed that it seemed to happen when the system was a bit
active. I then shutdown X and tried with nothing else running. It ran for a
few minutes until I did a sync from a different login while the dd was
running. Boom. Disk disconnected again.

I finally got an almost complete backup of /usr. I had about 1-2 GB lest
when it happened again. I suspect that some background operation (periodic
sync?) triggered it again.

Any suggestions?

Here is my system info: Lenovo T520 now running FreeBSD 12.0-STABLE r342788
and GENERIC config except SCHED_4BSD. System is completely stable except
for the USB disk dropping off-line. Disk is a 2TB WD My Passport. It is a
USB 3.0 drive,but plugged intoa 2.0 port. (The T520 has no 3.0 capability.

Has anyone seen anything like this? Any ideas? I am REALLY nervous running
without a backup.
--
Kevin Oberman, Part time kid herder and retired Network Engineer
E-mail: rkober...@gmail.com
PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

11.2 regression USB mass storage device

[Philip Homburg]

Since upgrading to 11.2-RELEASE, my laptop doesn't fully recognize my Garmin 
GPSMAP 62s anymore. In mass storage mode, the Garmin presents two block
devices, one to access the internal flash and one for the micro-SD card.

When I connect the Garmin, only the first device appears. After a camcontrol
rescan, the second appears as well.

Here is the dmesg output of connecting the Garmin:
uhub_reattach_port: giving up port reset - device vanished
ugen0.6:  at usbus0
umass0 on uhub2
umass0:  on 
usbus0
umass0:  SCSI over Bulk-Only; quirks = 0xc000
umass0:5:0: Attached to scbus5
da0 at umass-sim0 bus 0 scbus5 target 0 lun 0
da0:  Removable Direct Access SPC-3 SCSI device
da0: 40.000MB/s transfers
da0: 1848MB (3784704 512 byte sectors)
da0: quirks=0x2

Then I run 
# camcontrol rescan 5:0:1

And the resulting dmesg output:
da1 at umass-sim0 bus 0 scbus5 target 0 lun 1
da1:  Removable Direct Access SPC-3 SCSI device
da1: 40.000MB/s transfers
da1: 7646MB (15659008 512 byte sectors)
da1: quirks=0x2
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: Passing through USB serial to bhyve VM

[Stefan Bethke]

FWIW, I’ve opened a bug: 
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=229712

> Am 11.07.2018 um 23:41 schrieb Stefan Bethke :
> 
> It’s been a while since I last dealt with serial devices. Apparently, when 
> passing through a serial device on the host to a COM port in the VM, CTS/RTS 
> are not (correctly) passed through. With
>set ctsrts off
> in ppp.conf I could get ppp to dial successfully.
> 
> 
> Stefan
> 
>> Am 11.07.2018 um 19:22 schrieb Stefan Bethke :
>> 
>> I’m trying to access a Huawei USB LTE stick from a Bhyve VM like so:
>> # cat /var/vm/mgmt/mgmt.conf 
>> loader="bhyveload"
>> cpu=1
>> memory=256M
>> network0_type="virtio-net"
>> network0_switch="lan"
>> disk0_type="virtio-blk"
>> disk0_name="disk0"
>> disk0_dev="sparse-zvol"
>> uuid="53854567-8358-11e8-9638-000db94be2cc"
>> network0_mac="58:9c:fc:04:1d:52"
>> bhyve_options="-lcom2,/dev/cuaU0“
>> 
>> On the host, I can connect ppp(8), but inside the VM, ppp(8) appears not to 
>> be able to talk to the USB device. Using cu(1), I can talk to it just fine 
>> though. I’m not sure how to debug this further. Is this supposed to just 
>> work, or am I missing some obvious configuration bit?
>> 
>> [root@mgmt ~]# cu -l cuau1 -s 115200
>> Connected
>> ATZ
>> OK
>> ATI
>> Manufacturer: huawei
>> Model: E3272
>> Revision: 22.436.07.02.1202
>> IMEI: 867503015nn
>> +GCAP: +CGSM,+DS,+ES
>> 
>> OK
>> ~
>> [EOT]
>> [root@mgmt ~]# ppp
>> Working in interactive mode
>> Using interface: tun0
>> Phase: PPP Started (interactive mode).
>> ppp ON mgmt> dial
>> Phase: bundle: Establish
>> Phase: deflink: closed -> opening
>> Phase: deflink: Connected!
>> Phase: deflink: opening -> dial
>> Chat: deflink: Dial attempt 1 of 1
>> ppp ON mgmt> Chat: Send: ATZ
>> Chat: Expect(5): OK
>> Chat: Expect timeout
>> Chat: Send: ATZ
>> Chat: Expect(5): OK
>> Chat: Expect timeout
>> Warning: Chat script failed
>> Phase: deflink: dial -> hangup
>> Phase: deflink: Disconnected!
>> Phase: deflink: Connect time: 11 secs: 0 octets in, 0 octets out
>> Phase: deflink: 0 packets in, 0 packets out
>> Phase:  total 0 bytes/sec, peak 0 bytes/sec on Wed Jul 11 21:14:43 2018
>> Phase: deflink: hangup -> closed
>> Phase: bundle: Dead
>> ppp ON mgmt> quit
>> [root@mgmt ~]# cat /etc/ppp/ppp.conf
>> default:
>>   enable dns
>>   set log local LCP IPCP Phase Chat
>>  set log all
>>   set timeout 0
>>   ident UMTS
>>   set authname eplus
>>   set authkey internet
>>   set cd off
>>   set device /dev/cuau1
>>   set speed 115200
>>   set dial "ABORT BUSY ABORT NO\\sCARRIER \
>>   ABORT VOICE ABORT NO\\sDIALTONE ABORT NO\\sDIAL\\sTONE ABORT ERROR \
>>   ABORT NO\\sANSWER ABORT DELAYED TIMEOUT 5 \
>>   \"\" ATZ OK-ATZ-OK \
>>   AT+CFUN=1 OK \
>>   AT+CREG? OK \
>>   AT+COPS? OK \
>>   AT+CSQ OK \
>>  AT^HCSQ? OK \
>>   AT+cgdcont=1,\\\"IP\\\",\\\"internet.eplus.de\\\" OK \
>>   ATDT*99***1# CONNECT"
>>   set ifaddr 10.0.0.1/0 10.0.0.2/0 255.255.255.0 0.0.0.0
>>   add default HISADDR
>> 
>> 
>> Stefan
>> 
>> -- 
>> Stefan BethkeFon +49 151 14070811
>> 
>> 
>> ___
>> freebsd-stable@freebsd.org mailing list
>> https://lists.freebsd.org/mailman/listinfo/freebsd-stable
>> To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
> 
> -- 
> Stefan BethkeFon +49 151 14070811
> 
> 
> ___
> freebsd-stable@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-stable
> To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

-- 
Stefan BethkeFon +49 151 14070811


___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: Passing through USB serial to bhyve VM

[Stefan Bethke]

It’s been a while since I last dealt with serial devices. Apparently, when 
passing through a serial device on the host to a COM port in the VM, CTS/RTS 
are not (correctly) passed through. With
set ctsrts off
in ppp.conf I could get ppp to dial successfully.


Stefan

> Am 11.07.2018 um 19:22 schrieb Stefan Bethke :
> 
> I’m trying to access a Huawei USB LTE stick from a Bhyve VM like so:
> # cat /var/vm/mgmt/mgmt.conf 
> loader="bhyveload"
> cpu=1
> memory=256M
> network0_type="virtio-net"
> network0_switch="lan"
> disk0_type="virtio-blk"
> disk0_name="disk0"
> disk0_dev="sparse-zvol"
> uuid="53854567-8358-11e8-9638-000db94be2cc"
> network0_mac="58:9c:fc:04:1d:52"
> bhyve_options="-lcom2,/dev/cuaU0“
> 
> On the host, I can connect ppp(8), but inside the VM, ppp(8) appears not to 
> be able to talk to the USB device. Using cu(1), I can talk to it just fine 
> though. I’m not sure how to debug this further. Is this supposed to just 
> work, or am I missing some obvious configuration bit?
> 
> [root@mgmt ~]# cu -l cuau1 -s 115200
> Connected
> ATZ
> OK
> ATI
> Manufacturer: huawei
> Model: E3272
> Revision: 22.436.07.02.1202
> IMEI: 867503015nn
> +GCAP: +CGSM,+DS,+ES
> 
> OK
> ~
> [EOT]
> [root@mgmt ~]# ppp
> Working in interactive mode
> Using interface: tun0
> Phase: PPP Started (interactive mode).
> ppp ON mgmt> dial
> Phase: bundle: Establish
> Phase: deflink: closed -> opening
> Phase: deflink: Connected!
> Phase: deflink: opening -> dial
> Chat: deflink: Dial attempt 1 of 1
> ppp ON mgmt> Chat: Send: ATZ
> Chat: Expect(5): OK
> Chat: Expect timeout
> Chat: Send: ATZ
> Chat: Expect(5): OK
> Chat: Expect timeout
> Warning: Chat script failed
> Phase: deflink: dial -> hangup
> Phase: deflink: Disconnected!
> Phase: deflink: Connect time: 11 secs: 0 octets in, 0 octets out
> Phase: deflink: 0 packets in, 0 packets out
> Phase:  total 0 bytes/sec, peak 0 bytes/sec on Wed Jul 11 21:14:43 2018
> Phase: deflink: hangup -> closed
> Phase: bundle: Dead
> ppp ON mgmt> quit
> [root@mgmt ~]# cat /etc/ppp/ppp.conf
> default:
>enable dns
>set log local LCP IPCP Phase Chat
>   set log all
>set timeout 0
>ident UMTS
>set authname eplus
>set authkey internet
>set cd off
>set device /dev/cuau1
>set speed 115200
>set dial "ABORT BUSY ABORT NO\\sCARRIER \
>ABORT VOICE ABORT NO\\sDIALTONE ABORT NO\\sDIAL\\sTONE ABORT ERROR \
>ABORT NO\\sANSWER ABORT DELAYED TIMEOUT 5 \
>\"\" ATZ OK-ATZ-OK \
>AT+CFUN=1 OK \
>AT+CREG? OK \
>AT+COPS? OK \
>AT+CSQ OK \
>   AT^HCSQ? OK \
>AT+cgdcont=1,\\\"IP\\\",\\\"internet.eplus.de\\\" OK \
>ATDT*99***1# CONNECT"
>set ifaddr 10.0.0.1/0 10.0.0.2/0 255.255.255.0 0.0.0.0
>add default HISADDR
> 
> 
> Stefan
> 
> -- 
> Stefan BethkeFon +49 151 14070811
> 
> 
> ___
> freebsd-stable@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-stable
> To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

-- 
Stefan BethkeFon +49 151 14070811


___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Passing through USB serial to bhyve VM

[Stefan Bethke]

I’m trying to access a Huawei USB LTE stick from a Bhyve VM like so:
# cat /var/vm/mgmt/mgmt.conf 
loader="bhyveload"
cpu=1
memory=256M
network0_type="virtio-net"
network0_switch="lan"
disk0_type="virtio-blk"
disk0_name="disk0"
disk0_dev="sparse-zvol"
uuid="53854567-8358-11e8-9638-000db94be2cc"
network0_mac="58:9c:fc:04:1d:52"
bhyve_options="-lcom2,/dev/cuaU0“

On the host, I can connect ppp(8), but inside the VM, ppp(8) appears not to be 
able to talk to the USB device. Using cu(1), I can talk to it just fine though. 
I’m not sure how to debug this further. Is this supposed to just work, or am I 
missing some obvious configuration bit?

[root@mgmt ~]# cu -l cuau1 -s 115200
Connected
ATZ
OK
ATI
Manufacturer: huawei
Model: E3272
Revision: 22.436.07.02.1202
IMEI: 867503015nn
+GCAP: +CGSM,+DS,+ES

OK
~
[EOT]
[root@mgmt ~]# ppp
Working in interactive mode
Using interface: tun0
Phase: PPP Started (interactive mode).
ppp ON mgmt> dial
Phase: bundle: Establish
Phase: deflink: closed -> opening
Phase: deflink: Connected!
Phase: deflink: opening -> dial
Chat: deflink: Dial attempt 1 of 1
ppp ON mgmt> Chat: Send: ATZ
Chat: Expect(5): OK
Chat: Expect timeout
Chat: Send: ATZ
Chat: Expect(5): OK
Chat: Expect timeout
Warning: Chat script failed
Phase: deflink: dial -> hangup
Phase: deflink: Disconnected!
Phase: deflink: Connect time: 11 secs: 0 octets in, 0 octets out
Phase: deflink: 0 packets in, 0 packets out
Phase:  total 0 bytes/sec, peak 0 bytes/sec on Wed Jul 11 21:14:43 2018
Phase: deflink: hangup -> closed
Phase: bundle: Dead
ppp ON mgmt> quit
[root@mgmt ~]# cat /etc/ppp/ppp.conf
default:
enable dns
set log local LCP IPCP Phase Chat
set log all
set timeout 0
ident UMTS
set authname eplus
set authkey internet
set cd off
set device /dev/cuau1
set speed 115200
set dial "ABORT BUSY ABORT NO\\sCARRIER \
ABORT VOICE ABORT NO\\sDIALTONE ABORT NO\\sDIAL\\sTONE ABORT ERROR \
ABORT NO\\sANSWER ABORT DELAYED TIMEOUT 5 \
\"\" ATZ OK-ATZ-OK \
AT+CFUN=1 OK \
AT+CREG? OK \
AT+COPS? OK \
AT+CSQ OK \
AT^HCSQ? OK \
AT+cgdcont=1,\\\"IP\\\",\\\"internet.eplus.de\\\" OK \
ATDT*99***1# CONNECT"
set ifaddr 10.0.0.1/0 10.0.0.2/0 255.255.255.0 0.0.0.0
add default HISADDR


Stefan

-- 
Stefan BethkeFon +49 151 14070811


___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

USB trouble on Ryzen 3/AsRock mobo.

[Phil Norman]

Hi.

I've recently converted to FreeBSD, fleeing the Windowsification of Ubuntu.
I've been having some trouble with the USB system, which seems strange as
FreeBSD's USB stack is, according to a friend, rock solid. I'd like to
narrow down if this is a hardware (CPU or mobo) or software issue.

I'm running a Ryzen 3 1200, plugged into a "Fatal1ty X370 Gaming-ITX/ac"
motherboard (chosen because it supports ECC RAM and fits in an ITX case).

On a cold boot (ie starting by flipping the physical PSU power switch), BSD
boots up nice and quickly, without errors, and then runs for days without a
single USB-related error on dmesg. However, any other kind of reboot which
doesn't interrupt the electricity supply yields a large number of USB
errors (USB_ERR_TIMEOUTs every few seconds or so) and frequent resets of
the xhci0 controller.

On occasion, I also get problems with my keyboard randomly stopping working
(but then, if the USB subsystem is continuously resetting, that's only to
be expected). I also seem to get slow USB storage device read throughput
(2MB/s from a USB3 SSD), although I can't rule out that being caused by the
fuse ext4fs driver.

Here's what I see in dmesg when the USB system's in spam mode:


xhci0: Resetting controller
usb_alloc_device: set address 2 failed (USB_ERR_TIMEOUT, ignored)
usbd_setup_device_desc: getting device descriptor at addr 2 failed,
USB_ERR_TIMEOUT
igb0: link state changed to UP
usbd_req_re_enumerate: addr=2, set address failed! (USB_ERR_TIMEOUT,
ignored)
usbd_setup_device_desc: getting device descriptor at addr 2 failed,
USB_ERR_TIMEOUT
uhid0 on uhub3
uhid0:  on
usbus1
uhid1 on uhub3
uhid1:  on usbus1
ums0 on uhub2
ums0:  on
usbus1
ums0: 3 buttons and [XYZ] coordinates ID=0
usbd_req_re_enumerate: addr=2, set address failed! (USB_ERR_TIMEOUT,
ignored)
usbd_setup_device_desc: getting device descriptor at addr 2 failed,
USB_ERR_TIMEOUT
usbd_req_re_enumerate: addr=2, set address failed! (USB_ERR_TIMEOUT,
ignored)
usbd_setup_device_desc: getting device descriptor at addr 2 failed,
USB_ERR_TIMEOUT
usbd_req_re_enumerate: addr=2, set address failed! (USB_ERR_TIMEOUT,
ignored)
usbd_setup_device_desc: getting device descriptor at addr 2 failed,
USB_ERR_TIMEOUT
ugen0.2:  at usbus0 (disconnected)
uhub_reattach_port: could not allocate new device
uhub1: at usbus0, port 1, addr 1 (disconnected)
uhub1: <0x1022 XHCI root HUB, class 9/0, rev 3.00/1.00, addr 1> on usbus0
uhub1: 22 ports with 22 removable, self powered
xhci0: Resetting controller
-


Here's the start of dmesg:

-
Copyright (c) 1992-2018 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 11.2-PRERELEASE #0 r335198: Fri Jun 15 20:55:02 CEST 2018
phil@bob:/usr/obj/usr/src/sys/BOB amd64
FreeBSD clang version 6.0.0 (tags/RELEASE_600/final 326565) (based on LLVM
6.0.0)
VT(efifb): resolution 1024x768
CPU: AMD Ryzen 3 1200 Quad-Core Processor(3094.26-MHz K8-class
CPU)
  Origin="AuthenticAMD"  Id=0x800f11  Family=0x17  Model=0x1  Stepping=1

Features=0x178bfbff

Features2=0x7ed8320b
  AMD Features=0x2e500800
  AMD
Features2=0x35c233ff
  Structured Extended
Features=0x209c01a9
  XSAVE Features=0xf
  AMD Extended Feature Extensions ID EBX=0x1007
  SVM: (disabled in BIOS) NP,NRIP,VClean,AFlush,DAssist,NAsids=32768
  TSC: P-state invariant, performance statistics
real memory  = 17179869184 (16384 MB)
avail memory = 16519221248 (15753 MB)
Event timer "LAPIC" quality 600
ACPI APIC Table: 
FreeBSD/SMP: Multiprocessor System Detected: 4 CPUs
FreeBSD/SMP: 1 package(s) x 4 core(s)
random: unblocking device.
Firmware Warning (ACPI): Optional FADT field Pm2ControlBlock has valid
Length but zero Address: 0x/0x1 (20171214/tbfadt-796)
ioapic0  irqs 0-23 on motherboard
ioapic1  irqs 24-55 on motherboard
SMP: AP CPU #3 Launched!
SMP: AP CPU #2 Launched!
SMP: AP CPU #1 Launched!
Timecounter "TSC-low" frequency 1547130097 Hz quality 1000
random: entropy device external interface
kbd0 at kbdmux0
netmap: loaded module
module_register_init: MOD_LOAD (vesa, 0x80a3bd40, 0) error 19
random: registering fast source Intel Secure Key RNG
random: fast provider: "Intel Secure Key RNG"
nvidia-modeset: Loading NVIDIA Kernel Mode Setting Driver for UNIX
platforms  390.59  Wed May  9 21:54:48 PDT 2018
nexus0
cryptosoft0:  on motherboard
aesni0:  on motherboard
acpi0:  on motherboard
acpi0: Power Button (fixed)
cpu0:  on acpi0
cpu1:  on acpi0
cpu2:  on acpi0
cpu3:  on acpi0
attimer0:  port 0x40-0x43 irq 0 on acpi0
Timecounter "i8254" frequency 1193182 Hz quality 0
Event timer "i8254" frequency 1193182 Hz quality 100
atrtc0:  port 0x70-0x71 on acpi0
atrtc0: registered as a time-of-day clock, resolution 1.00s
Event timer &q

Re: USB GSM still in trouble after upgrade to 11.1-RELEASE-p10

[Per olof Ljungmark]

On 05/14/18 16:35, Willem Jan Withagen wrote:
> Hi,
> 
> Yesterday evening I upgraded a system to 11.1-RELEASE-p10.
> But that sort of upset my GSM-dongle I use for alarming.
> 
> And it did not do that before the upgrade, where I was running -p9.
> 
> 
> This is what I find repeated at rather high frequency in the logs:
> +ugen1.3:  at usbus1
> +u3g0 on uhub3
> +u3g0:  on usbus1
> +u3g0: Found 2 ports.
> +umass0 on uhub3
> +umass0:  addr 3> on usbus1
> +umass0:  SCSI over Bulk-Only; quirks = 0x
> +umass0:3:0: Attached to scbus3
> +(probe0:umass-sim0:0:0:0): INQUIRY. CDB: 12 00 00 00 24 00
> +(probe0:umass-sim0:0:0:0): CAM status: CCB request completed with an error
> +(probe0:umass-sim0:0:0:0): Retrying command
> +(probe0:umass-sim0:0:0:0): INQUIRY. CDB: 12 00 00 00 24 00
> +(probe0:umass-sim0:0:0:0): CAM status: CCB request completed with an error
> +(probe0:umass-sim0:0:0:0): Retrying command
> +(probe0:umass-sim0:0:0:0): INQUIRY. CDB: 12 00 00 00 24 00
> +(probe0:umass-sim0:0:0:0): CAM status: CCB request completed with an error
> +(probe0:umass-sim0:0:0:0): Retrying command
> +(probe0:umass-sim0:0:0:0): INQUIRY. CDB: 12 00 00 00 24 00
> +(probe0:umass-sim0:0:0:0): CAM status: CCB request completed with an error
> +(probe0:umass-sim0:0:0:0): Retrying command
> +(probe0:umass-sim0:0:0:0): INQUIRY. CDB: 12 00 00 00 24 00
> +(probe0:umass-sim0:0:0:0): CAM status: CCB request completed with an error
> +(probe0:umass-sim0:0:0:0): Error 5, Retries exhausted
> +ugen1.3:  at usbus1 (disconnected)
> +u3g0: at uhub3, port 2, addr 3 (disconnected)
> +u3g0: detached
> +umass0: at uhub3, port 2, addr 3 (disconnected)
> +umass0: detached
> 
> So when I get home, I'm going to pull the stick.
> But what could be going on here?

I have identical behavior on a
FreeBSD 11.1-STABLE #0 r330526
system after it was restarted today.

It used to work with a Huawei E398 but after the reboot it does not,
just like your above.

Interestingly, I replaced it with a much older Huawei E1750 and that one
worked, but only after I rebooted again.

With the E398 after a reboot I only see /dev/cuau1, no cuaUX.X
If I pull it and replace with E1750 nothing happens
If I reboot with the E1750 in place, I get /dev/cuaUX.X

Fishy...


___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

USB GSM still in trouble after upgrade to 11.1-RELEASE-p10

[Willem Jan Withagen]

Hi,

Yesterday evening I upgraded a system to 11.1-RELEASE-p10.
But that sort of upset my GSM-dongle I use for alarming.

And it did not do that before the upgrade, where I was running -p9.


This is what I find repeated at rather high frequency in the logs:
+ugen1.3:  at usbus1
+u3g0 on uhub3
+u3g0:  on usbus1
+u3g0: Found 2 ports.
+umass0 on uhub3
+umass0:  on usbus1
+umass0:  SCSI over Bulk-Only; quirks = 0x
+umass0:3:0: Attached to scbus3
+(probe0:umass-sim0:0:0:0): INQUIRY. CDB: 12 00 00 00 24 00
+(probe0:umass-sim0:0:0:0): CAM status: CCB request completed with an error
+(probe0:umass-sim0:0:0:0): Retrying command
+(probe0:umass-sim0:0:0:0): INQUIRY. CDB: 12 00 00 00 24 00
+(probe0:umass-sim0:0:0:0): CAM status: CCB request completed with an error
+(probe0:umass-sim0:0:0:0): Retrying command
+(probe0:umass-sim0:0:0:0): INQUIRY. CDB: 12 00 00 00 24 00
+(probe0:umass-sim0:0:0:0): CAM status: CCB request completed with an error
+(probe0:umass-sim0:0:0:0): Retrying command
+(probe0:umass-sim0:0:0:0): INQUIRY. CDB: 12 00 00 00 24 00
+(probe0:umass-sim0:0:0:0): CAM status: CCB request completed with an error
+(probe0:umass-sim0:0:0:0): Retrying command
+(probe0:umass-sim0:0:0:0): INQUIRY. CDB: 12 00 00 00 24 00
+(probe0:umass-sim0:0:0:0): CAM status: CCB request completed with an error
+(probe0:umass-sim0:0:0:0): Error 5, Retries exhausted
+ugen1.3:  at usbus1 (disconnected)
+u3g0: at uhub3, port 2, addr 3 (disconnected)
+u3g0: detached
+umass0: at uhub3, port 2, addr 3 (disconnected)
+umass0: detached

So when I get home, I'm going to pull the stick.
But what could be going on here?

--WjW
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: Two USB 4 disk enclosure and a panic

[Ronald Klop]

On Wed, 25 Apr 2018 14:15:03 +0200, Nenhum_de_Nos  
<math...@eternamente.info> wrote:



On Mon, April 23, 2018 23:18, Nenhum_de_Nos wrote:

Hi,

I would like to know how to debug this. I have two 4 disk enclosures:

Mediasonic ProBox 4 Bay 3.5' SATA HDD Enclosure – USB 3.0 & eSATA
(HF2-SU3S2)
NexStar HX4 - NST-640SU3-BK

and both have 4 disk on them, and not all disk are equal.

The issue comes when I plug the probox usb3 enclosure on the system. I
can't even read the /var/log/message, it crashes very quickly.

I can see on the boot process up to the point where the second enclosure
comes to be loaded. The 4 disk are shown on the dmesg/console, and then  
a
core dump happens, the boot process goes to the debug screen and a  
restart

happens like a flash.

The motherboard is a Intel® Desktop Board D525MW running 8GB RAM.
All disk use ZFS, 4 or 5 zpools, one raidz, one mirror and two or three
single disk pools.
FreeBSD xxx 11.1-RELEASE-p7 FreeBSD 11.1-RELEASE-p7 #1 r330596: Thu  
Mar  8

06:45:59 -03 2018 root@xxx:/usr/obj/usr/src/sys/FreeBSD-11-amd64-PF
amd64

The kernel is a slightly modified generic, just to have altq.

How can I debug this? I have no idea. I have to use two machines to run
all those disks, and I would really like to have just one for it.

Can it be the amount of RAM? The other box is and APU2 from PCEngines  
and

have 4GB ram. apu2 uname -a: FreeBSD yyy 11.1-RELEASE-p4 FreeBSD
11.1-RELEASE-p4 #0: Tue Nov 14 06:12:40 UTC 2017
r...@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC  amd64

I tried to plug the Vantec hardware on the apu2 box, but there it would
not panic, but won't load all vantec disks neither. I really run out of
ideas here :(

thanks.

--
"We will call you Cygnus,
the God of balance you shall be."


Hi,

I found some logs on the daily security output:

+ZFS filesystem version: 5
+ZFS storage pool version: features support (5000)
+panic: Solaris(panic): blkptr at 0xf8000b93c848 DVA 1 has invalid  
VDEV 1

+cpuid = 0
+KDB: stack backtrace:
+#0 0x80ab65c7 at kdb_backtrace+0x67
+#1 0x80a746a6 at vpanic+0x186
+#2 0x80a74513 at panic+0x43
+#3 0x82623192 at vcmn_err+0xc2
+#4 0x824a73ba at zfs_panic_recover+0x5a
+#5 0x824ce893 at zfs_blkptr_verify+0x2d3
+#6 0x824ce8dc at zio_read+0x2c
+#7 0x82445fb4 at arc_read+0x6c4
+#8 0x824636a4 at dmu_objset_open_impl+0xd4
+#9 0x8247eafa at dsl_pool_init+0x2a
+#10 0x8249b093 at spa_load+0x823
+#11 0x8249a2de at spa_load_best+0x6e
+#12 0x82496a81 at spa_open_common+0x101
+#13 0x824e2879 at pool_status_check+0x29
+#14 0x824eba3d at zfsdev_ioctl+0x4ed
+#15 0x809429f8 at devfs_ioctl_f+0x128
+#16 0x80ad1f15 at kern_ioctl+0x255
+CPU: Intel(R) Atom(TM) CPU D525   @ 1.80GHz (1800.11-MHz K8-class CPU)
+avail memory = 8246845440 (7864 MB)
+Timecounter "TSC" frequency 1800110007 Hz quality 1000
+GEOM_PART: integrity check failed (ada0s1, BSD)
+GEOM_PART: integrity check failed (diskid/DISK-5LZ0ZDBBs1, BSD)


This error also looks interesting.



+ugen1.2:  at usbus1
+ukbd0 on uhub0
+ukbd0:  on usbus1
+kbd2 at ukbd0
+ZFS filesystem version: 5
+ZFS storage pool version: features support (5000)
+re0: link state changed to DOWN
+uhid0 on uhub0
+uhid0:  on usbus1
+ums0 on uhub0
+ums0:  on usbus1
+ums0: 3 buttons and [XYZ] coordinates ID=0
+re0: promiscuous mode enabled
+re0: link state changed to UP

For what I see can be ZFS related.

If anyone have any hints, please tell :)

I kinda got curious about this:

+ZFS storage pool version: features support (5000)

How can I figure out if my pools are from different versions and may this
be the culprit here?


zpool upgrade [-v]

But I think you can only run this if your machine does not panic. Maybe on  
another machine.


Can you get the output of the coredump? On reboot the /etc/rc.d/savecore  
script will look for a valid core dump in the dumpdev (see /etc/rc.conf,  
/etc/defaults/rc.conf) and write it to /var/crash/. That will contain  
information which can help people debug this.


Regards,
Ronald.




thanks,

matheus

___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: Two USB 4 disk enclosure and a panic

[Nenhum_de_Nos]

On Mon, April 23, 2018 23:18, Nenhum_de_Nos wrote:
> Hi,
>
> I would like to know how to debug this. I have two 4 disk enclosures:
>
> Mediasonic ProBox 4 Bay 3.5' SATA HDD Enclosure – USB 3.0 & eSATA
> (HF2-SU3S2)
> NexStar HX4 - NST-640SU3-BK
>
> and both have 4 disk on them, and not all disk are equal.
>
> The issue comes when I plug the probox usb3 enclosure on the system. I
> can't even read the /var/log/message, it crashes very quickly.
>
> I can see on the boot process up to the point where the second enclosure
> comes to be loaded. The 4 disk are shown on the dmesg/console, and then a
> core dump happens, the boot process goes to the debug screen and a restart
> happens like a flash.
>
> The motherboard is a Intel® Desktop Board D525MW running 8GB RAM.
> All disk use ZFS, 4 or 5 zpools, one raidz, one mirror and two or three
> single disk pools.
> FreeBSD xxx 11.1-RELEASE-p7 FreeBSD 11.1-RELEASE-p7 #1 r330596: Thu Mar  8
> 06:45:59 -03 2018 root@xxx:/usr/obj/usr/src/sys/FreeBSD-11-amd64-PF
> amd64
>
> The kernel is a slightly modified generic, just to have altq.
>
> How can I debug this? I have no idea. I have to use two machines to run
> all those disks, and I would really like to have just one for it.
>
> Can it be the amount of RAM? The other box is and APU2 from PCEngines and
> have 4GB ram. apu2 uname -a: FreeBSD yyy 11.1-RELEASE-p4 FreeBSD
> 11.1-RELEASE-p4 #0: Tue Nov 14 06:12:40 UTC 2017
> r...@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC  amd64
>
> I tried to plug the Vantec hardware on the apu2 box, but there it would
> not panic, but won't load all vantec disks neither. I really run out of
> ideas here :(
>
> thanks.
>
> --
> "We will call you Cygnus,
> the God of balance you shall be."

Hi,

I found some logs on the daily security output:

+ZFS filesystem version: 5
+ZFS storage pool version: features support (5000)
+panic: Solaris(panic): blkptr at 0xf8000b93c848 DVA 1 has invalid VDEV 1
+cpuid = 0
+KDB: stack backtrace:
+#0 0x80ab65c7 at kdb_backtrace+0x67
+#1 0x80a746a6 at vpanic+0x186
+#2 0x80a74513 at panic+0x43
+#3 0x82623192 at vcmn_err+0xc2
+#4 0x824a73ba at zfs_panic_recover+0x5a
+#5 0x824ce893 at zfs_blkptr_verify+0x2d3
+#6 0x824ce8dc at zio_read+0x2c
+#7 0x82445fb4 at arc_read+0x6c4
+#8 0x824636a4 at dmu_objset_open_impl+0xd4
+#9 0x8247eafa at dsl_pool_init+0x2a
+#10 0x8249b093 at spa_load+0x823
+#11 0x8249a2de at spa_load_best+0x6e
+#12 0x82496a81 at spa_open_common+0x101
+#13 0x824e2879 at pool_status_check+0x29
+#14 0x824eba3d at zfsdev_ioctl+0x4ed
+#15 0x809429f8 at devfs_ioctl_f+0x128
+#16 0x80ad1f15 at kern_ioctl+0x255
+CPU: Intel(R) Atom(TM) CPU D525   @ 1.80GHz (1800.11-MHz K8-class CPU)
+avail memory = 8246845440 (7864 MB)
+Timecounter "TSC" frequency 1800110007 Hz quality 1000
+GEOM_PART: integrity check failed (ada0s1, BSD)
+GEOM_PART: integrity check failed (diskid/DISK-5LZ0ZDBBs1, BSD)
+ugen1.2:  at usbus1
+ukbd0 on uhub0
+ukbd0:  on usbus1
+kbd2 at ukbd0
+ZFS filesystem version: 5
+ZFS storage pool version: features support (5000)
+re0: link state changed to DOWN
+uhid0 on uhub0
+uhid0:  on usbus1
+ums0 on uhub0
+ums0:  on usbus1
+ums0: 3 buttons and [XYZ] coordinates ID=0
+re0: promiscuous mode enabled
+re0: link state changed to UP

For what I see can be ZFS related.

If anyone have any hints, please tell :)

I kinda got curious about this:

+ZFS storage pool version: features support (5000)

How can I figure out if my pools are from different versions and may this
be the culprit here?

thanks,

matheus

-- 
"We will call you Cygnus,
the God of balance you shall be."

___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Two USB 4 disk enclosure and a panic

[Nenhum_de_Nos]

Hi,

I would like to know how to debug this. I have two 4 disk enclosures:

Mediasonic ProBox 4 Bay 3.5' SATA HDD Enclosure – USB 3.0 & eSATA (HF2-SU3S2)
NexStar HX4 - NST-640SU3-BK

and both have 4 disk on them, and not all disk are equal.

The issue comes when I plug the probox usb3 enclosure on the system. I
can't even read the /var/log/message, it crashes very quickly.

I can see on the boot process up to the point where the second enclosure
comes to be loaded. The 4 disk are shown on the dmesg/console, and then a
core dump happens, the boot process goes to the debug screen and a restart
happens like a flash.

The motherboard is a Intel® Desktop Board D525MW running 8GB RAM.
All disk use ZFS, 4 or 5 zpools, one raidz, one mirror and two or three
single disk pools.
FreeBSD xxx 11.1-RELEASE-p7 FreeBSD 11.1-RELEASE-p7 #1 r330596: Thu Mar  8
06:45:59 -03 2018 root@xxx:/usr/obj/usr/src/sys/FreeBSD-11-amd64-PF 
amd64

The kernel is a slightly modified generic, just to have altq.

How can I debug this? I have no idea. I have to use two machines to run
all those disks, and I would really like to have just one for it.

Can it be the amount of RAM? The other box is and APU2 from PCEngines and
have 4GB ram. apu2 uname -a: FreeBSD yyy 11.1-RELEASE-p4 FreeBSD
11.1-RELEASE-p4 #0: Tue Nov 14 06:12:40 UTC 2017
r...@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC  amd64

I tried to plug the Vantec hardware on the apu2 box, but there it would
not panic, but won't load all vantec disks neither. I really run out of
ideas here :(

thanks.

-- 
"We will call you Cygnus,
the God of balance you shall be."

___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: Problem with USB <---> UPS management connection

[Glen Barber]

On Mon, Mar 19, 2018 at 12:53:01PM -0700, John Baldwin wrote:
> On Thursday, March 08, 2018 01:16:46 AM Glen Barber wrote:
> > On Wed, Mar 07, 2018 at 08:04:47PM -0500, Mark Saad wrote:
> > > > On Mar 7, 2018, at 6:55 AM, wishmaster <artem...@ukr.net> wrote:
> > > > 
> > > > Hi, colleagues!
> > > > 
> > > > Something strange happens with a server. I am attempting to connect 
> > > > management interface of UPS with server via USB.
> > > > In console I see a lot of errors:
> > > > 
> > > > Mar  7 13:42:04 xxx kernel: ugen2.2:  
> > > > at usbus2
> > > > Mar  7 13:42:05 xxx kernel: uhid0 on uhub6
> > > > Mar  7 13:42:05 xxx kernel: uhid0:  > > > class 0/0, rev 1.10/0.02, addr 2> on usbus2
> > > > Mar  7 13:42:08 xxx kernel: ugen2.2:  
> > > > at usbus2 (disconnected)
> > > > Mar  7 13:42:08 xxx kernel: uhid0: at uhub6, port 3, addr 2 
> > > > (disconnected)
> > > > Mar  7 13:42:08 xxx kernel: uhid0: detached
> > > > Mar  7 13:42:12 xxx kernel: ugen2.2:  
> > > > at usbus2
> > > > Mar  7 13:42:12 xxx kernel: uhid0 on uhub6
> > > > Mar  7 13:42:12 xxx kernel: uhid0:  > > > class 0/0, rev 1.10/0.02, addr 2> on usbus2
> > > > Mar  7 13:42:16 xxx kernel: ugen2.2:  
> > > > at usbus2 (disconnected)
> > > > Mar  7 13:42:16 xxx kernel: uhid0: at uhub6, port 3, addr 2 
> > > > (disconnected)
> > > > Mar  7 13:42:16 xxx kernel: uhid0: detached
> > > > 
> > > > I have changed USB-cables, USB port on the server - without success.
> > > > On another server this problem is absent.
> > > > 
> > > > FreeBSD version: FreeBSD 11.1-STABLE #1 r329364M:
> > > > 
> > > > Any ideas?
> > > > 
> > > All
> > >  I lost power at home and noticed that nut didn’t work right . I
> > > had a similar dmesg . My box is running 11.1-stable amd64 built
> > > from svn 7-8 days ago . When I get power back I’ll post details .
> > > 
> > 
> > This seems suspiciously similar to an issue I am seeing with a USB mouse
> > on both stable/11 a patched build of releng/11.1.  In my case, the dmesg
> > shows:
> > 
> > ugen1.3:  at usbus1 (disconnected)
> > ugen1.3:  at usbus1
> > ugen1.3:  at usbus1 (disconnected)
> > ugen1.3:  at usbus1
> > 
> > What struck me as "suspiciously similar" is the 'ugen' reference.
> > Unfortunately, I do not have more information yet, but have been
> > pounding my head on my desk throughout the day.  Then, I saw this
> > thread.
> > 
> > Anyone else seeing at least USB mouse-related issues?  It could entirely
> > be a red herring.
> 
> I am definitely seeing issues with an APC USB I have on my desktop.  I have
> used this desktop + APC combination for at least 5 years now and only after
> my most recent upgrade to 11.1-STABLE at r326909.  I did not have issues on
> the previous 11.1-STABLE kernel at r321399, so it does seem like it could
> be a regression.
> 

I did figure out what the problem was with my mouse - the ums(4) driver
was not properly loading on releng/11.1.  It does appear to be fixed in
stable/11, so the issue I pointed out in this thread may not be related.

Glen



signature.asc
Description: PGP signature

Re: Problem with USB <---> UPS management connection

[John Baldwin]

On Thursday, March 08, 2018 01:16:46 AM Glen Barber wrote:
> On Wed, Mar 07, 2018 at 08:04:47PM -0500, Mark Saad wrote:
> > > On Mar 7, 2018, at 6:55 AM, wishmaster <artem...@ukr.net> wrote:
> > > 
> > > Hi, colleagues!
> > > 
> > > Something strange happens with a server. I am attempting to connect 
> > > management interface of UPS with server via USB.
> > > In console I see a lot of errors:
> > > 
> > > Mar  7 13:42:04 xxx kernel: ugen2.2:  
> > > at usbus2
> > > Mar  7 13:42:05 xxx kernel: uhid0 on uhub6
> > > Mar  7 13:42:05 xxx kernel: uhid0:  > > class 0/0, rev 1.10/0.02, addr 2> on usbus2
> > > Mar  7 13:42:08 xxx kernel: ugen2.2:  
> > > at usbus2 (disconnected)
> > > Mar  7 13:42:08 xxx kernel: uhid0: at uhub6, port 3, addr 2 (disconnected)
> > > Mar  7 13:42:08 xxx kernel: uhid0: detached
> > > Mar  7 13:42:12 xxx kernel: ugen2.2:  
> > > at usbus2
> > > Mar  7 13:42:12 xxx kernel: uhid0 on uhub6
> > > Mar  7 13:42:12 xxx kernel: uhid0:  > > class 0/0, rev 1.10/0.02, addr 2> on usbus2
> > > Mar  7 13:42:16 xxx kernel: ugen2.2:  
> > > at usbus2 (disconnected)
> > > Mar  7 13:42:16 xxx kernel: uhid0: at uhub6, port 3, addr 2 (disconnected)
> > > Mar  7 13:42:16 xxx kernel: uhid0: detached
> > > 
> > > I have changed USB-cables, USB port on the server - without success.
> > > On another server this problem is absent.
> > > 
> > > FreeBSD version: FreeBSD 11.1-STABLE #1 r329364M:
> > > 
> > > Any ideas?
> > > 
> > All
> >  I lost power at home and noticed that nut didn’t work right . I
> > had a similar dmesg . My box is running 11.1-stable amd64 built
> > from svn 7-8 days ago . When I get power back I’ll post details .
> > 
> 
> This seems suspiciously similar to an issue I am seeing with a USB mouse
> on both stable/11 a patched build of releng/11.1.  In my case, the dmesg
> shows:
> 
> ugen1.3:  at usbus1 (disconnected)
> ugen1.3:  at usbus1
> ugen1.3:  at usbus1 (disconnected)
> ugen1.3:  at usbus1
> 
> What struck me as "suspiciously similar" is the 'ugen' reference.
> Unfortunately, I do not have more information yet, but have been
> pounding my head on my desk throughout the day.  Then, I saw this
> thread.
> 
> Anyone else seeing at least USB mouse-related issues?  It could entirely
> be a red herring.

I am definitely seeing issues with an APC USB I have on my desktop.  I have
used this desktop + APC combination for at least 5 years now and only after
my most recent upgrade to 11.1-STABLE at r326909.  I did not have issues on
the previous 11.1-STABLE kernel at r321399, so it does seem like it could
be a regression.

-- 
John Baldwin
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: Problem with USB <---> UPS management connection

[Glen Barber]

On Wed, Mar 07, 2018 at 08:04:47PM -0500, Mark Saad wrote:
> > On Mar 7, 2018, at 6:55 AM, wishmaster <artem...@ukr.net> wrote:
> > 
> > Hi, colleagues!
> > 
> > Something strange happens with a server. I am attempting to connect 
> > management interface of UPS with server via USB.
> > In console I see a lot of errors:
> > 
> > Mar  7 13:42:04 xxx kernel: ugen2.2:  at 
> > usbus2
> > Mar  7 13:42:05 xxx kernel: uhid0 on uhub6
> > Mar  7 13:42:05 xxx kernel: uhid0:  > 0/0, rev 1.10/0.02, addr 2> on usbus2
> > Mar  7 13:42:08 xxx kernel: ugen2.2:  at 
> > usbus2 (disconnected)
> > Mar  7 13:42:08 xxx kernel: uhid0: at uhub6, port 3, addr 2 (disconnected)
> > Mar  7 13:42:08 xxx kernel: uhid0: detached
> > Mar  7 13:42:12 xxx kernel: ugen2.2:  at 
> > usbus2
> > Mar  7 13:42:12 xxx kernel: uhid0 on uhub6
> > Mar  7 13:42:12 xxx kernel: uhid0:  > 0/0, rev 1.10/0.02, addr 2> on usbus2
> > Mar  7 13:42:16 xxx kernel: ugen2.2:  at 
> > usbus2 (disconnected)
> > Mar  7 13:42:16 xxx kernel: uhid0: at uhub6, port 3, addr 2 (disconnected)
> > Mar  7 13:42:16 xxx kernel: uhid0: detached
> > 
> > I have changed USB-cables, USB port on the server - without success.
> > On another server this problem is absent.
> > 
> > FreeBSD version: FreeBSD 11.1-STABLE #1 r329364M:
> > 
> > Any ideas?
> > 
> All
>  I lost power at home and noticed that nut didn’t work right . I
> had a similar dmesg . My box is running 11.1-stable amd64 built
> from svn 7-8 days ago . When I get power back I’ll post details .
> 

This seems suspiciously similar to an issue I am seeing with a USB mouse
on both stable/11 a patched build of releng/11.1.  In my case, the dmesg
shows:

ugen1.3:  at usbus1 (disconnected)
ugen1.3:  at usbus1
ugen1.3:  at usbus1 (disconnected)
ugen1.3:  at usbus1

What struck me as "suspiciously similar" is the 'ugen' reference.
Unfortunately, I do not have more information yet, but have been
pounding my head on my desk throughout the day.  Then, I saw this
thread.

Anyone else seeing at least USB mouse-related issues?  It could entirely
be a red herring.

Glen



signature.asc
Description: PGP signature

Re: Problem with USB <---> UPS management connection

[Mark Saad]

All
 I lost power at home and noticed that nut didn’t work right . I had a similar 
dmesg . My box is running 11.1-stable amd64 built from svn 7-8 days ago . When 
I get power back I’ll post details . 

---
Mark Saad | nones...@longcount.org

> On Mar 7, 2018, at 6:55 AM, wishmaster <artem...@ukr.net> wrote:
> 
> Hi, colleagues!
> 
> Something strange happens with a server. I am attempting to connect 
> management interface of UPS with server via USB.
> In console I see a lot of errors:
> 
> Mar  7 13:42:04 xxx kernel: ugen2.2:  at 
> usbus2
> Mar  7 13:42:05 xxx kernel: uhid0 on uhub6
> Mar  7 13:42:05 xxx kernel: uhid0:  0/0, rev 1.10/0.02, addr 2> on usbus2
> Mar  7 13:42:08 xxx kernel: ugen2.2:  at 
> usbus2 (disconnected)
> Mar  7 13:42:08 xxx kernel: uhid0: at uhub6, port 3, addr 2 (disconnected)
> Mar  7 13:42:08 xxx kernel: uhid0: detached
> Mar  7 13:42:12 xxx kernel: ugen2.2:  at 
> usbus2
> Mar  7 13:42:12 xxx kernel: uhid0 on uhub6
> Mar  7 13:42:12 xxx kernel: uhid0:  0/0, rev 1.10/0.02, addr 2> on usbus2
> Mar  7 13:42:16 xxx kernel: ugen2.2:  at 
> usbus2 (disconnected)
> Mar  7 13:42:16 xxx kernel: uhid0: at uhub6, port 3, addr 2 (disconnected)
> Mar  7 13:42:16 xxx kernel: uhid0: detached
> 
> I have changed USB-cables, USB port on the server - without success.
> On another server this problem is absent.
> 
> FreeBSD version: FreeBSD 11.1-STABLE #1 r329364M:
> 
> Any ideas?
> 
> --
> Vitaliy
> ___
> freebsd-stable@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-stable
> To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re[2]: Problem with USB <---> UPS management connection

[wishmaster]

  

 --- Original message ---
From: "tech-lists" <tech-li...@zyxst.net>
Date: 7 March 2018, 20:12:13

 
> On 07/03/2018 11:55, wishmaster wrote:
> > I have changed USB-cables, USB port on the server - without success.
> > On another server this problem is absent.
> 
> It looks like a broken or shorting connection but you say you've tried
> different ports on the machine and changed cables. I dunno, maybe the
> usb subsystem/circuitry in that machine is at fault? The way I'd test is
> to install a usb card known to be good and test again.

3G USB modem is connected in another USB port on this server and works fine. 
The problem I described was appeared after a new MB had been installed into the 
server with fresh OS.
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: Problem with USB <---> UPS management connection

[tech-lists]

On 07/03/2018 11:55, wishmaster wrote:
> I have changed USB-cables, USB port on the server - without success.
> On another server this problem is absent.

It looks like a broken or shorting connection but you say you've tried
different ports on the machine and changed cables. I dunno, maybe the
usb subsystem/circuitry in that machine is at fault? The way I'd test is
to install a usb card known to be good and test again.
-- 
J.
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Problem with USB <---> UPS management connection

[wishmaster]

Hi, colleagues!

Something strange happens with a server. I am attempting to connect management 
interface of UPS with server via USB.
In console I see a lot of errors:

Mar  7 13:42:04 xxx kernel: ugen2.2:  at 
usbus2
Mar  7 13:42:05 xxx kernel: uhid0 on uhub6
Mar  7 13:42:05 xxx kernel: uhid0:  on usbus2
Mar  7 13:42:08 xxx kernel: ugen2.2:  at 
usbus2 (disconnected)
Mar  7 13:42:08 xxx kernel: uhid0: at uhub6, port 3, addr 2 (disconnected)
Mar  7 13:42:08 xxx kernel: uhid0: detached
Mar  7 13:42:12 xxx kernel: ugen2.2:  at 
usbus2
Mar  7 13:42:12 xxx kernel: uhid0 on uhub6
Mar  7 13:42:12 xxx kernel: uhid0:  on usbus2
Mar  7 13:42:16 xxx kernel: ugen2.2:  at 
usbus2 (disconnected)
Mar  7 13:42:16 xxx kernel: uhid0: at uhub6, port 3, addr 2 (disconnected)
Mar  7 13:42:16 xxx kernel: uhid0: detached

I have changed USB-cables, USB port on the server - without success.
On another server this problem is absent.

FreeBSD version: FreeBSD 11.1-STABLE #1 r329364M:

Any ideas?

--
Vitaliy
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: automount usb msdosfs no partition table

[Edward Napierala]

2017-10-09 0:10 GMT+01:00 Tomasz CEDRO <to...@cedro.info>:

> Hello world :-)
>
> I need to configure automount for a testing machine. It seems to work
> fine, except for two issues:
>
> 1. Mount point does not disappear after device disappears, what makes
> things harder to script when device is gone. automount -c does not
> remove the mountpoint, only restarting the service does. It is a bug
> or feature?
>

Bug, or perhaps a missing feature.  No known workaround at this point,
I'm afraid.


> 2. Automounter does not mount USB Pendrive / MSDOSFS devices that does
> not have a parition table. Some USB Drives does not have valid
> partition table, they appear as /dev/da0 and can be mounted with
> mount_msdosfs /dev/da0 /mnt, but they are not recognised by
> automounter.. how can I make it work with such devices?
>

It should just work:

[trasz@v2:~]% ll /media
total 5
drwxr-xr-x   3 root  wheel   512 Oct  6 15:38 .
drwxr-xr-x  21 root  wheel  1024 Oct  5 23:58 ..
[trasz@v2:~]% doas mdconfig -s1g
md0
trasz@v2:~]% doas newfs_msdos /dev/md0
newfs_msdos: cannot get number of sectors per track: Operation not supported
newfs_msdos: cannot get number of heads: Operation not supported
/dev/md0: 2096576 sectors in 65518 FAT16 clusters (16384 bytes/cluster)
BytesPerSec=512 SecPerClust=32 ResSectors=1 FATs=2 RootDirEnts=512
Media=0xf0 FATsecs=256 SecPerTrack=63 Heads=255 HiddenSecs=0
HugeSectors=2097152
[trasz@v2:~]% ll /media
total 5
drwxr-xr-x   3 root  wheel   512 Oct  6 15:38 .
drwxr-xr-x  21 root  wheel  1024 Oct  5 23:58 ..
drwxr-xr-x   3 root  wheel   512 Oct 10 06:50 md0
[trasz@v2:~]%

With the pendrive plugged in, can you do "gpart show",
"/etc/autofs/special_media" (as root), and paste the output?
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: automount usb msdosfs no partition table

[Tomoaki AOKI]

Does sysutils/automount (not sysutils/automounter) work as expected?

 *Need fix for head, though. The fix itself is easy, but I've stuck
  with version check to create extra patch for ports.

Attached patch for head. If you want to use sysutils/automount on head,
apply it as root AFTER install for now.


On Mon, 9 Oct 2017 21:07:29 +0200
Tomasz CEDRO  wrote:

> On Mon, Oct 9, 2017 at 8:59 PM, Scott Bennett  wrote:
> > Tomasz CEDRO  wrote:
> >> i cannot format that device, as its the "firmware feature" that it has no
> >> partition table.. i would have to fix the firmware.. but it would be nice
> >> to automount it anyway as macos, linux and windoze can :-)
> >  Well, put a partition table onto it, then.  You can use either gpart(8)
> > or fdisk(8) to do that and to create a slice, and then use newfs_msdos(8) to
> > create the file system.
> >  I understood from your previous message that you wanted to create a 
> > FAT32
> > file system on /dev/da0 rather than on /dev/da0s1, which meant on the bare
> > device rather than on a slice.  Otherwise, create the partition table, 
> > create
> > a slice, and proceed.
> 
> The problem is device has hardcoded filesystem, with no partition
> table, all this is created by firmware on device boot, cannot get
> formatted nor partitioned.. I can mount it by hand.. but it does not
> get automounted.. and exactly this part is the problem and quest here
> :-) :-)
> 
> -- 
> CeDeROM, SQ7MHZ, http://www.tomek.cedro.info
> ___
> freebsd-stable@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-stable
> To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
> 


-- 
Tomoaki AOKI
--- /usr/local/sbin/automount.orig	2015-09-21 16:10:07.114602000 +0900
+++ /usr/local/sbin/automount	2017-09-30 00:23:51.855577000 +0900
@@ -423,12 +423,12 @@ case ${2} in
   __log "${DEV}: fsck_msdosfs ${LINE}"
 done
 __wait_for_device ${DEV}
-if mount_msdosfs ${OPTS} -o large -o longnames -m 644 -M 755 \
+if mount_msdosfs ${OPTS} -o longnames -m 644 -M 755 \
  -D ${CODEPAGE} -L ${ENCODING} ${DEV} ${MNT}
 then
   ADD=1
 else
-  __log "${DEV}: mount failed (fat) 'mount_msdosfs ${OPTS} -o large -o longnames -D ${CODEPAGE} -L ${ENCODING} -m 644 -M 755 ${DEV} ${MNT}'"
+  __log "${DEV}: mount failed (fat) 'mount_msdosfs ${OPTS} -o longnames -D ${CODEPAGE} -L ${ENCODING} -m 644 -M 755 ${DEV} ${MNT}'"
   exit 1
 fi
 __log "${DEV}: mount (fat)"
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: automount usb msdosfs no partition table

[Tomasz CEDRO]

On Mon, Oct 9, 2017 at 8:59 PM, Scott Bennett  wrote:
> Tomasz CEDRO  wrote:
>> i cannot format that device, as its the "firmware feature" that it has no
>> partition table.. i would have to fix the firmware.. but it would be nice
>> to automount it anyway as macos, linux and windoze can :-)
>  Well, put a partition table onto it, then.  You can use either gpart(8)
> or fdisk(8) to do that and to create a slice, and then use newfs_msdos(8) to
> create the file system.
>  I understood from your previous message that you wanted to create a FAT32
> file system on /dev/da0 rather than on /dev/da0s1, which meant on the bare
> device rather than on a slice.  Otherwise, create the partition table, create
> a slice, and proceed.

The problem is device has hardcoded filesystem, with no partition
table, all this is created by firmware on device boot, cannot get
formatted nor partitioned.. I can mount it by hand.. but it does not
get automounted.. and exactly this part is the problem and quest here
:-) :-)

-- 
CeDeROM, SQ7MHZ, http://www.tomek.cedro.info
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: automount usb msdosfs no partition table

[Scott Bennett]

Tomasz CEDRO  wrote:

> i cannot format that device, as its the "firmware feature" that it has no
> partition table.. i would have to fix the firmware.. but it would be nice
> to automount it anyway as macos, linux and windoze can :-)
>
 Well, put a partition table onto it, then.  You can use either gpart(8)
or fdisk(8) to do that and to create a slice, and then use newfs_msdos(8) to
create the file system.
 I understood from your previous message that you wanted to create a FAT32
file system on /dev/da0 rather than on /dev/da0s1, which meant on the bare
device rather than on a slice.  Otherwise, create the partition table, create
a slice, and proceed.


  Scott Bennett, Comm. ASMELG, CFIAG
**
* Internet:   bennett at sdf.org   *xor*   bennett at freeshell.org  *
**
* "A well regulated and disciplined militia, is at all times a good  *
* objection to the introduction of that bane of all free governments *
* -- a standing army."   *
*-- Gov. John Hancock, New York Journal, 28 January 1790 *
**
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: automount usb msdosfs no partition table

[Tomasz CEDRO]

i cannot format that device, as its the "firmware feature" that it has no
partition table.. i would have to fix the firmware.. but it would be nice
to automount it anyway as macos, linux and windoze can :-)

--
CeDeROM, SQ7MHZ, http://www.tomek.cedro.info
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

automount usb msdosfs no partition table

[Scott Bennett]

On Date: Mon, 9 Oct 2017 01:10:19 +0200 Tomasz CEDRO <to...@cedro.info> wrote:

> I need to configure automount for a testing machine. It seems to work
> fine, except for two issues:

 I've never used the automounter, so I can't help you with that.
>
> 1. Mount point does not disappear after device disappears, what makes
> things harder to script when device is gone. automount -c does not
> remove the mountpoint, only restarting the service does. It is a bug
> or feature?
>
> 2. Automounter does not mount USB Pendrive / MSDOSFS devices that does
> not have a parition table. Some USB Drives does not have valid
> partition table, they appear as /dev/da0 and can be mounted with
> mount_msdosfs /dev/da0 /mnt, but they are not recognised by
> automounter.. how can I make it work with such devices?
>
 Try newfs_msdos(8).


  Scott Bennett, Comm. ASMELG, CFIAG
**
* Internet:   bennett at sdf.org   *xor*   bennett at freeshell.org  *
**
* "A well regulated and disciplined militia, is at all times a good  *
* objection to the introduction of that bane of all free governments *
* -- a standing army."   *
*-- Gov. John Hancock, New York Journal, 28 January 1790 *
**
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

automount usb msdosfs no partition table

[Tomasz CEDRO]

Hello world :-)

I need to configure automount for a testing machine. It seems to work
fine, except for two issues:

1. Mount point does not disappear after device disappears, what makes
things harder to script when device is gone. automount -c does not
remove the mountpoint, only restarting the service does. It is a bug
or feature?

2. Automounter does not mount USB Pendrive / MSDOSFS devices that does
not have a parition table. Some USB Drives does not have valid
partition table, they appear as /dev/da0 and can be mounted with
mount_msdosfs /dev/da0 /mnt, but they are not recognised by
automounter.. how can I make it work with such devices?

Any hints appreciated :-)
Tomek

-- 
CeDeROM, SQ7MHZ, http://www.tomek.cedro.info
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: [USB] hang after upgrade from 11.0 to 11.1, ZFS or callout() related?

[Michael Schmiedgen]

On 07.08.2017 19:21, Mark Martinec wrote:

But this is all for 11.0, on 11.1 it hangs and I cannot look it up:


Does it also hang if you choose 'Safe mode" in the loader dialog?


It hangs even with 'Safe mode' (multiuser):

https://imgur.com/a/fz3KB

Thanks,
  Michael

--
___

Michael Schmiedgen, BSc
Senior Software Engineer

Takwa GmbH
Friedrich-List-Str. 36
99096 Erfurt GERMANY

Tel  +49 361 6534096
Fax  +49 361 6534097
Mail schmied...@takwa.de
Web  http://www.takwa.de/
___


Amtsgericht Jena HRB 112964
Geschäftsführung: Ingo Buchholz
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: [USB] hang after upgrade from 11.0 to 11.1, ZFS or callout() related?

[Michael Schmiedgen]

On 07.08.2017 19:21, Mark Martinec wrote:

But this is all for 11.0, on 11.1 it hangs and I cannot look it up:


Does it also hang if you choose 'Safe mode" in the loader dialog?

   Mark


It hangs even with 'Safe mode' (multiuser):

https://imgur.com/a/fz3KB


I tried setting cam boot delay, as some people in web forums suggested:

kern.cam.boot_delay="1"

But then I get the 'ZFS error 5' with an 11.1 kernel.


Thanks,
  Michael

--
___

Michael Schmiedgen, BSc
Senior Software Engineer

Takwa GmbH
Friedrich-List-Str. 36
99096 Erfurt GERMANY

Tel  +49 361 6534096
Fax  +49 361 6534097
Mail schmied...@takwa.de
Web  http://www.takwa.de/
___


Amtsgericht Jena HRB 112964
Geschäftsführung: Ingo Buchholz
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: [USB] hang after upgrade from 11.0 to 11.1, ZFS or callout() related?

[Mark Martinec]

But this is all for 11.0, on 11.1 it hangs and I cannot look it up:


Does it also hang if you choose 'Safe mode" in the loader dialog?

  Mark
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: [USB] hang after upgrade from 11.0 to 11.1, ZFS or callout() related?

[Michael Schmiedgen]

On 07.08.2017 19:09, Hans Petter Selasky wrote:


Can you get dmesg without the USB debug enabled?



But this is all for 11.0, on 11.1 it hangs and I cannot look it up:


Copyright (c) 1992-2016 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 11.0-RELEASE-p1 #0 r306420: Thu Sep 29 01:43:23 UTC 2016
r...@releng2.nyi.freebsd.org:/usr/obj/usr/src/sys/GENERIC amd64
FreeBSD clang version 3.8.0 (tags/RELEASE_380/final 262564) (based on LLVM 
3.8.0)
VT(vga): resolution 640x480
CPU: Intel(R) Xeon(R) CPU E31245 @ 3.30GHz (3300.09-MHz K8-class CPU)
  Origin="GenuineIntel"  Id=0x206a7  Family=0x6  Model=0x2a  Stepping=7
  
Features=0xbfebfbff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE>

Features2=0x1fbae3ff<SSE3,PCLMULQDQ,DTES64,MON,DS_CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,POPCNT,TSCDLT,AESNI,XSAVE,OSXSAVE,AVX>
  AMD Features=0x28100800<SYSCALL,NX,RDTSCP,LM>
  AMD Features2=0x1
  XSAVE Features=0x1
  VT-x: PAT,HLT,MTF,PAUSE,EPT,UG,VPID
  TSC: P-state invariant, performance statistics
real memory  = 34359738368 (32768 MB)
avail memory = 33186914304 (31649 MB)
Event timer "LAPIC" quality 600
ACPI APIC Table: 
FreeBSD/SMP: Multiprocessor System Detected: 8 CPUs
FreeBSD/SMP: 1 package(s) x 4 core(s) x 2 hardware threads
random: unblocking device.
ioapic0  irqs 0-23 on motherboard
random: entropy device external interface
kbd1 at kbdmux0
netmap: loaded module
module_register_init: MOD_LOAD (vesa, 0x8101c950, 0) error 19
vtvga0:  on motherboard
cryptosoft0:  on motherboard
acpi0:  on motherboard
acpi0: Power Button (fixed)
cpu0:  on acpi0
cpu1:  on acpi0
cpu2:  on acpi0
cpu3:  on acpi0
cpu4:  on acpi0
cpu5:  on acpi0
cpu6:  on acpi0
cpu7:  on acpi0
hpet0:  iomem 0xfed0-0xfed003ff on acpi0
Timecounter "HPET" frequency 14318180 Hz quality 950
Event timer "HPET" frequency 14318180 Hz quality 550
atrtc0:  port 0x70-0x77 irq 8 on acpi0
atrtc0: Warning: Couldn't map I/O.
Event timer "RTC" frequency 32768 Hz quality 0
attimer0:  port 0x40-0x43,0x50-0x53 irq 0 on acpi0
Timecounter "i8254" frequency 1193182 Hz quality 0
Event timer "i8254" frequency 1193182 Hz quality 100
Timecounter "ACPI-fast" frequency 3579545 Hz quality 900
acpi_timer0: <24-bit timer at 3.579545MHz> port 0x408-0x40b on acpi0
pcib0:  port 0xcf8-0xcff on acpi0
pcib0: _OSC returned error 0x4
pci0:  on pcib0
pcib1:  irq 16 at device 1.0 on pci0
pci1:  on pcib1
vgapci0:  port 0xf000-0xf03f mem 
0xf780-0xf7bf,0xe000-0xefff irq 16 at device 2.0 on pci0
vgapci0: Boot video device
pcib2:  irq 19 at device 6.0 on pci0
pci2:  on pcib2
pci0:  at device 22.0 (no driver attached)
ehci0:  mem 0xf7e04000-0xf7e043ff irq 16 at 
device 26.0 on pci0
usbus0: EHCI version 1.0
usbus0 on ehci0
pcib3:  irq 16 at device 28.0 on pci0
pcib3: [GIANT-LOCKED]
pcib4:  irq 17 at device 28.5 on pci0
pci3:  on pcib4
em0: <Intel(R) PRO/1000 Network Connection 7.6.1-k> port 0xe000-0xe01f mem 
0xf7d0-0xf7d1,0xf7d2-0xf7d23fff irq 17 at device 0.0 on pci3
em0: Using MSIX interrupts with 3 vectors
em0: Ethernet address: 10:bf:48:d7:f1:29
em0: netmap queues/slots: TX 1/1024, RX 1/1024
pcib5:  irq 19 at device 28.7 on pci0
pci4:  on pcib5
xhci0:  mem 0xf7c0-0xf7c07fff irq 19 at 
device 0.0 on pci4
xhci0: 32 bytes context size, 32-bit DMA
xhci0: Unable to map MSI-X table
usbus1 on xhci0
ehci1:  mem 0xf7e03000-0xf7e033ff irq 23 at 
device 29.0 on pci0
usbus2: EHCI version 1.0
usbus2 on ehci1
pcib6:  at device 30.0 on pci0
pci5:  on pcib6
isab0:  at device 31.0 on pci0
isa0:  on isab0
ahci0:  port 0xf0b0-0xf0b7,0xf0a0-0xf0a3,0xf090-0xf097,0xf080-0xf083,0xf060-0xf07f mem 0xf7e02000-0xf7e027ff 
irq 19 at device 31.2 on pci0

ahci0: AHCI v1.30 with 6 6Gbps ports, Port Multiplier not supported
ahcich0:  at channel 0 on ahci0
ahcich1:  at channel 1 on ahci0
ahciem0:  on ahci0
acpi_button0:  on acpi0
acpi_tz0:  on acpi0
acpi_tz1:  on acpi0
atkbdc0:  port 0x60,0x64 irq 1 on acpi0
atkbd0:  irq 1 on atkbdc0
kbd0 at atkbd0
atkbd0: [GIANT-LOCKED]
orm0:  at iomem 0xce800-0xcf7ff on isa0
ppc0: cannot reserve I/O port range
est0:  on cpu0
est1:  on cpu1
est2:  on cpu2
est3:  on cpu3
est4:  on cpu4
est5:  on cpu5
est6:  on cpu6
est7:  on cpu7
usbus0: 480Mbps High Speed USB v2.0
ZFS filesystem version: 5
ZFS storage pool version: features support (5000)
Timecounters tick every 1.000 msec
nvme cam probe device init
usbus1: 5.0Gbps Super Speed USB v3.0
usbus2: 480Mbps High Speed USB v2.0
ugen0.1:  at usbus0
uhub0:  on usbus0
ugen1.1: <0x1b21> at usbus1
uhub1: <0x1b21 XHCI root HUB, class 9/0, rev 3.00/1.00, addr 1> on usbus1
ugen2.1:  at usbus2
uhub2:  on usbu

Re: [USB] hang after upgrade from 11.0 to 11.1, ZFS or callout() related?

[Hans Petter Selasky]

On 08/07/17 18:28, Michael Schmiedgen wrote:

dmesg:

Aug  7 18:26:34 antares kernel: usbd_pipe_enter: enter
Aug  7 18:26:34 antares kernel: usbd_pipe_enter: enter
Aug  7 18:26:34 antares kernel: usbd_pipe_start: start
Aug  7 18:26:34 antares kernel: usbd_pipe_start: start
Aug  7 18:26:34 antares kernel: usbd_transfer_done: 
err=USB_ERR_NORMAL_COMPLETION
Aug  7 18:26:34 antares kernel: usbd_transfer_done: 
err=USB_ERR_NORMAL_COMPLETION

Aug  7 18:26:34 antares kernel


Can you get dmesg without the USB debug enabled?

--HPS
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: [USB] hang after upgrade from 11.0 to 11.1, ZFS or callout() related?

[Michael Schmiedgen]

On 07.08.2017 18:10, Hans Petter Selasky wrote:


Are you sure you loaded all drivers, like XHCI, EHCI, OHCI, UHCI ? DOes the 
BIOS offer any USB options?



After enabling the 'USB hands off' in BIOS I got the strange 'error 5' with 
11.1,
disable_enumeration was not enabled BTW:

https://imgur.com/a/67jV1

Switching back to 11.0 but still with 'USB hands off' activated, everything is 
fine.

Michael


--
___

Michael Schmiedgen, BSc
Senior Software Engineer

Takwa GmbH
Friedrich-List-Str. 36
99096 Erfurt GERMANY

Tel  +49 361 6534096
Fax  +49 361 6534097
Mail schmied...@takwa.de
Web  http://www.takwa.de/
___


Amtsgericht Jena HRB 112964
Geschäftsführung: Ingo Buchholz
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: [USB] hang after upgrade from 10.0 to 10.1, ZFS or callout() related?

[Michael Schmiedgen]

On 07.08.2017 18:10, Hans Petter Selasky wrote:


Are you sure you loaded all drivers, like XHCI, EHCI, OHCI, UHCI ? DOes the 
BIOS offer any USB options?


https://imgur.com/a/YN428

It seems like some cheapo hardware.

BTW, after the hang I requested KVM access at our hoster, so there
is possible new USB interference with the (crappy) KVM hardware too.
But the hang exist before the KVM was attached.

Disabeling

dev.uhub.2.disable_enumeration="1"
dev.uhub.1.disable_enumeration="1"
dev.uhub.0.disable_enumeration="1"

leads to a hang and this console output:

https://imgur.com/a/WiiQW

Thanks,
  Michael

--
___

Michael Schmiedgen, BSc
Senior Software Engineer

Takwa GmbH
Friedrich-List-Str. 36
99096 Erfurt GERMANY

Tel  +49 361 6534096
Fax  +49 361 6534097
Mail schmied...@takwa.de
Web  http://www.takwa.de/
___


Amtsgericht Jena HRB 112964
Geschäftsführung: Ingo Buchholz
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: [USB] hang after upgrade from 11.0 to 11.1, ZFS or callout() related?

[Michael Schmiedgen]

On 07.08.2017 18:10, Hans Petter Selasky wrote:


Can you try getting the dmesg.

You can also disable USB enumeration setting these:

hw.usb.disable_enumeration: 0
dev.uhub.2.disable_enumeration: 0
dev.uhub.1.disable_enumeration: 0
dev.uhub.0.disable_enumeration: 0

Are you sure you loaded all drivers, like XHCI, EHCI, OHCI, UHCI ? DOes the 
BIOS offer any USB options?



It is a generic 11.1 kernel.

I already tried hw.usb.disable_enumeration="1" but that triggered the
strange 'ZFS error 5'.

Part of the debug dmesg with 11.0 kernel below.

Thanks,
  Michael


dmesg:

Aug  7 18:26:34 antares kernel: usbd_pipe_enter: enter
Aug  7 18:26:34 antares kernel: usbd_pipe_enter: enter
Aug  7 18:26:34 antares kernel: usbd_pipe_start: start
Aug  7 18:26:34 antares kernel: usbd_pipe_start: start
Aug  7 18:26:34 antares kernel: usbd_transfer_done: 
err=USB_ERR_NORMAL_COMPLETION
Aug  7 18:26:34 antares kernel: usbd_transfer_done: 
err=USB_ERR_NORMAL_COMPLETION
Aug  7 18:26:34 antares kernel: usbd_callback_wrapper_sub: 
xfer=0xf80023165148 endpoint=0xf800231640d8 sts=0 alen=12, slen=12, 
afrm=2, nfrm=2
Aug  7 18:26:34 antares kernel: usbd_do_request_callback: st=1
Aug  7 18:26:34 antares kernel: usbd_callback_wrapper_sub: 
xfer=0xf80023196148 endpoint=0xf8002318f0d8 sts=0 alen=12, slen=12, 
afrm=2, nfrm=2
Aug  7 18:26:34 antares kernel: usbd_do_request_callback: st=1
Aug  7 18:26:34 antares kernel: usbd_do_request_callback: st=0
Aug  7 18:26:34 antares kernel: usbd_transfer_submit: xfer=0xf80023165148, 
endpoint=0xf800231640d8, nframes=2, dir=read
Aug  7 18:26:34 antares kernel: usb_dump_endpoint: endpoint=0xf800231640d8 edesc=0xf80023164720 isoc_next=0 
toggle_next=0usbd_do_request_callback: st=0

Aug  7 18:26:34 antares kernel: bEndpointAddress=0x00usbd_transfer_submit: 
xfer=0xf80023196148, endpoint=0xf8002318f0d8, nframes=2, dir=read
Aug  7 18:26:34 antares kernel:
Aug  7 18:26:34 antares kernel: usb_dump_endpoint: endpoint=0xf8002318f0d8usb_dump_queue: endpoint=0xf800231640d8 xfer: 
edesc=0xf8002318f720 isoc_next=0 toggle_next=0

Aug  7 18:26:34 antares kernel: bEndpointAddress=0x00usbd_pipe_enter: enter
Aug  7 18:26:34 antares kernel:
Aug  7 18:26:34 antares kernel: usbd_pipe_start: start
Aug  7 18:26:34 antares kernel: usb_dump_queue: endpoint=0xf8002318f0d8 
xfer:
Aug  7 18:26:34 antares kernel: usbd_pipe_enter: enter
Aug  7 18:26:34 antares kernel: usbd_pipe_start: start
Aug  7 18:26:34 antares kernel: usbd_transfer_done: 
err=USB_ERR_NORMAL_COMPLETION
Aug  7 18:26:34 antares kernel: usbd_transfer_done: 
err=USB_ERR_NORMAL_COMPLETION
Aug  7 18:26:34 antares kernel: usbd_callback_wrapper_sub: 
xfer=0xf80023196148 endpoint=0xf8002318f0d8 sts=0 alen=12, slen=12, 
afrm=2, nfrm=2
Aug  7 18:26:34 antares kernel: usbd_callback_wrapper_sub: 
xfer=0xf80023165148 endpoint=0xf800231640d8 sts=0 alen=12, slen=12, 
afrm=2, nfrm=2
Aug  7 18:26:34 antares kernel: usbd_do_request_callback: st=1
Aug  7 18:26:34 antares kernel: usbd_do_request_callback: st=1
Aug  7 18:26:34 antares kernel: usbd_do_request_callback: st=0
Aug  7 18:26:34 antares kernel: usbd_transfer_submit: xfer=0xf80023165148, 
endpoint=0xf800231640d8, nframes=2, dir=read
Aug  7 18:26:34 antares kernel: usbd_do_request_callback: st=0
Aug  7 18:26:34 antares kernel: usb_dump_endpoint: endpoint=0xf800231640d8usbd_transfer_submit: xfer=0xf80023196148, 
endpoint=0xf8002318f0d8, nframes=2, dir=read
Aug  7 18:26:34 antares kernel: edesc=0xf80023164720 isoc_next=0 toggle_next=0usb_dump_endpoint: endpoint=0xf8002318f0d8 bEndpointAddress=0x00 
edesc=0xf8002318f720 isoc_next=0 toggle_next=0

Aug  7 18:26:34 antares kernel: bEndpointAddress=0x00usb_dump_queue: 
endpoint=0xf800231640d8 xfer:
Aug  7 18:26:34 antares kernel:
Aug  7 18:26:34 antares kernel: usb_dump_queue: endpoint=0xf8002318f0d8 
xfer: usbd_pipe_enter: enter
Aug  7 18:26:34 antares kernel:
Aug  7 18:26:34 antares kernel: usbd_pipe_start: start
Aug  7 18:26:34 antares kernel: usbd_pipe_enter: enter
Aug  7 18:26:34 antares kernel: usbd_pipe_start: start
Aug  7 18:26:34 antares kernel: usbd_transfer_done: 
err=USB_ERR_NORMAL_COMPLETION
Aug  7 18:26:34 antares kernel: usbd_callback_wrapper_sub: 
xfer=0xf80023196148 endpoint=0xf8002318f0d8 sts=0 alen=12, slen=12, 
afrm=2, nfrm=2
Aug  7 18:26:34 antares kernel: usbd_transfer_done: 
err=USB_ERR_NORMAL_COMPLETION
Aug  7 18:26:34 antares kernel: usbd_do_request_callback: st=1
Aug  7 18:26:34 antares kernel: usbd_callback_wrapper_sub: 
xfer=0xf80023165148 endpoint=0xf800231640d8 sts=0 alen=12, slen=12, 
afrm=2, nfrm=2
Aug  7 18:26:34 antares kernel: usbd_do_request_callback: st=0
Aug  7 18:26:34 antares kernel: usbd_do_request_callback: st=1
Aug  7 18:26:34 antares kernel: usbd_transfer_submit: xfer=0xf80023196148, 
endpoint=0xf8002318f0d8, nframes=2, dir=read
Aug  7 18:26:34 antares kernel: usbd_do_request_callback: st=0

Re: [USB] hang after upgrade from 10.0 to 10.1, ZFS or callout() related?

[Hans Petter Selasky]

On 08/07/17 17:59, Michael Schmiedgen wrote:

Hi list,

after upgrading kernel from 11.0 to 11.1 the boot process stopped,
waiting forever for some USB stuff. I tried to skip waiting with

hw.usb.no_boot_wait="1"

in /boot/loader.conf but then I got a very strange ZFS 'mount error 5',
which I had some time ago upgrading from 10.0 to 10.1. That error did
magically went away with 11.0, and now it seems to pop up again:

https://lists.freebsd.org/pipermail/freebsd-current/2014-October/052900.html 



https://lists.freebsd.org/pipermail/freebsd-stable/2014-December/081192.html 



Can you try getting the dmesg.

You can also disable USB enumeration setting these:

hw.usb.disable_enumeration: 0
dev.uhub.2.disable_enumeration: 0
dev.uhub.1.disable_enumeration: 0
dev.uhub.0.disable_enumeration: 0

Are you sure you loaded all drivers, like XHCI, EHCI, OHCI, UHCI ? DOes 
the BIOS offer any USB options?


--HPS





So I reset the boot wait option to default again and switched on some USB
debug options:

https://imgur.com/a/xzkrC


Anybody? Thanks,
   Michael



___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

[USB] hang after upgrade from 10.0 to 10.1, ZFS or callout() related?

[Michael Schmiedgen]

Hi list,

after upgrading kernel from 11.0 to 11.1 the boot process stopped,
waiting forever for some USB stuff. I tried to skip waiting with

hw.usb.no_boot_wait="1"

in /boot/loader.conf but then I got a very strange ZFS 'mount error 5',
which I had some time ago upgrading from 10.0 to 10.1. That error did
magically went away with 11.0, and now it seems to pop up again:

https://lists.freebsd.org/pipermail/freebsd-current/2014-October/052900.html

https://lists.freebsd.org/pipermail/freebsd-stable/2014-December/081192.html


So I reset the boot wait option to default again and switched on some USB
debug options:

https://imgur.com/a/xzkrC


Anybody? Thanks,
  Michael

--
___

Michael Schmiedgen, BSc
Senior Software Engineer

Takwa GmbH
Friedrich-List-Str. 36
99096 Erfurt GERMANY

Tel  +49 361 6534096
Fax  +49 361 6534097
Mail schmied...@takwa.de
Web  http://www.takwa.de/
___


Amtsgericht Jena HRB 112964
Geschäftsführung: Ingo Buchholz
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: USB problems after r316423 (LLVM-4.0)

[peter . blok]

Kevin,

Haven’t noticed anything unusual with USB. Just have tried other things like 
USB stick, USB cdrom and USB ethernet, both on USB2.0 and USB3.0 but no issues

xhci0:  mem 0xf750-0xf750 irq 16 
at device 20.0 on pci0
xhci0: 32 bytes context size, 64-bit DMA
xhci0: Port routing mask set to 0x
usbus0 on xhci0
ehci0:  mem 0xf7513000-0xf75133ff 
irq 16 at device 26.0 on pci0
usbus1 on ehci0
ehci1:  mem 0xf7512000-0xf75123ff 
irq 22 at device 29.0 on pci0
usbus2 on ehci1
xhci0:  mem 0xf750-0xf750 irq 16 
at device 20.0 on pci0
xhci0: 32 bytes context size, 64-bit DMA
xhci0: Port routing mask set to 0x
usbus0 on xhci0
ehci0:  mem 0xf7513000-0xf75133ff 
irq 16 at device 26.0 on pci0
usbus1 on ehci0
ehci1:  mem 0xf7512000-0xf75123ff 
irq 22 at device 29.0 on pci0
usbus2 on ehci1

Peter
> On 18 Apr 2017, at 21:53, Kevin Oberman <rkober...@gmail.com> wrote:
> 
> USB on my system (Lenovo T520-Cougar Point chipset) fails to initialize. I
> have reported this in
> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=218513
> 
> Can others running 11-STABLE at or after r316423 confirm the operation of
> USB ports? It seems unlikely that I am the only one seeing this as my
> system is pretty vanilla, but I have seen no other reports.
> 
> If you have such a system, can you either confirm that USB is working or
> test by plugging in any USB device and seeing if it shows up or check
> /var/run/dmesg for the errors reported in the ticket?
> 
> I am running GENERIC except for SCHED_4BSD. (I tried SCHED_ULE with no
> change.)
> CPU: Intel(R) Core(TM) i5-2520M CPU @ 2.50GHz (2491.97-MHz K8-class CPU)
>  Origin="GenuineIntel"  Id=0x206a7  Family=0x6  Model=0x2a  Stepping=7
> Other details are in the ticket.
> 
> Thanks so much.
> --
> Kevin Oberman, Part time kid herder and retired Network Engineer
> E-mail: rkober...@gmail.com
> PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683
> ___
> freebsd-stable@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-stable
> To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: USB problems after r316423 (LLVM-4.0)

[Philipp-Joachim Ost]

Kevin Oberman wrote:
> USB on my system (Lenovo T520-Cougar Point chipset) fails to initialize. I
> have reported this in
> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=218513
> 
> Can others running 11-STABLE at or after r316423 confirm the operation of
> USB ports? It seems unlikely that I am the only one seeing this as my
> system is pretty vanilla, but I have seen no other reports.
> 
> If you have such a system, can you either confirm that USB is working or
> test by plugging in any USB device and seeing if it shows up or check
> /var/run/dmesg for the errors reported in the ticket?

I'm running 11-STABLE r317090 and USB devices work just fine (keyboard,
mouse, memory sticks). I don't see the errors reported in your bug
report, either.

Not sure if it matters, but my system has an AMD/ATI chipset.
pciconf -lv reports the following:
...
ehci0@pci0:0:18:2:  class=0x0c0320 card=0x83891043 chip=0x43961002
rev=0x00
hdr=0x00
vendor = 'Advanced Micro Devices, Inc. [AMD/ATI]'
    device = 'SB7x0/SB8x0/SB9x0 USB EHCI Controller'
class      = serial bus
subclass   = USB
...

Philipp



smime.p7s
Description: S/MIME Cryptographic Signature

USB problems after r316423 (LLVM-4.0)

[Kevin Oberman]

USB on my system (Lenovo T520-Cougar Point chipset) fails to initialize. I
have reported this in
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=218513

Can others running 11-STABLE at or after r316423 confirm the operation of
USB ports? It seems unlikely that I am the only one seeing this as my
system is pretty vanilla, but I have seen no other reports.

If you have such a system, can you either confirm that USB is working or
test by plugging in any USB device and seeing if it shows up or check
/var/run/dmesg for the errors reported in the ticket?

I am running GENERIC except for SCHED_4BSD. (I tried SCHED_ULE with no
change.)
CPU: Intel(R) Core(TM) i5-2520M CPU @ 2.50GHz (2491.97-MHz K8-class CPU)
  Origin="GenuineIntel"  Id=0x206a7  Family=0x6  Model=0x2a  Stepping=7
Other details are in the ticket.

Thanks so much.
--
Kevin Oberman, Part time kid herder and retired Network Engineer
E-mail: rkober...@gmail.com
PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: Unsupported USB BT device causes high interrupt load

[Dominic Fandrey]

> I have an Interrupt load of 2000 interrupts/s from xhci0.
> 
> As the culprit I have identified the following device:
> 
> ugen0.6:  at usbus0, cfg=255 md=HOST spd=FULL 
> (12Mbps) pwr=ON (100mA)
> 
> …

The device spamms me with interrupts after every boot and resume
until I send it a power_off command.

For anyone else with a similar problem, I'm using the following devd
rule to mitigate the issue (https://pastebin.com/raw/HmDur3Le):

notify 100 {
match "system"  "USB";
match "subsystem"   "INTERFACE";
match "type""ATTACH";
match "vendor"  "0x8087";
match "product" "0x07dc";
action "usbconfig -d $cdev power_off";
};

-- 
A: Because it fouls the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing on usenet and in e-mail? 



pgp4T6dJTSgtT.pgp
Description: PGP signature

Re: Unsupported USB BT device causes high interrupt load

[Adrian Chadd]

can you capture a usb transfer dump from usbdump ?

I'd like to see if it's because the usb bluetooth code is trying to
attach and failing, or whether it really is just some broken transfer
/ notification loop.


-a


On 6 April 2017 at 03:16, Dominic Fandrey <k...@freebsd.org> wrote:
> I have an Interrupt load of 2000 interrupts/s from xhci0.
>
> As the culprit I have identified the following device:
>
> ugen0.6:  at usbus0, cfg=255 md=HOST spd=FULL 
> (12Mbps) pwr=ON (100mA)
>
> The impression I have from googling this is that it's an unsupported
> BT device sitting on board of my Intel Wireless AC 7260 card (I also
> have an unsupported SD/MMC card reader sitting on the mainboard).
>
> usbconfig -d 0.6 power_off
>
> Ends the interrupt spree.
>
> I'm running FreeBSD 11.0-STABLE #1 r316490 amd64.
>
> --
> A: Because it fouls the order in which people normally read text.
> Q: Why is top-posting such a bad thing?
> A: Top-posting.
> Q: What is the most annoying thing on usenet and in e-mail?
>
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: No USB?

[Kevin Oberman]

I have opened https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=218513 on
this issue.

Bi-section in a problem as the update to LLVM  a week ago breaks building
old kernels. Hoping I can buildworld with the current compiler and then
build the kernel. (Wonder if the new compiler could be the trigger for the
problem I'm seeing?)

Kevin Oberman, Part time kid herder and retired Network Engineer
E-mail: rkober...@gmail.com
PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683

On Sun, Apr 9, 2017 at 10:52 AM, Kevin Oberman <rkober...@gmail.com> wrote:

> On Sat, Apr 8, 2017 at 1:55 PM, Kevin Oberman <rkober...@gmail.com> wrote:
>
>> Today, for the first time in a couple of weeks, I plugged in a USB drive
>> to my 11-STABLE system (r316552). No device was created and usbconfig only
>> sees EHCI hubs:
>> ugen1.1:  at usbus1, cfg=0 md=HOST spd=HIGH
>> (480Mbps) pwr=SAVE (0mA)
>> ugen0.1:  at usbus0, cfg=0 md=HOST spd=HIGH
>> (480Mbps) pwr=SAVE (0mA)
>>
>> Seems like I should be seeing UHCI stuff, too. Even internal devices like
>> my webcam don't show up.
>>
>> I'm running a GENERIC kernel with the following exceptions:
>> nooptions SCHED_ULE   # ULE scheduler
>> options   SCHED_4BSD  # 4BSD scheduler
>> optionsIEEE80211_DEBUG
>>
>> I tried updating my system and that made no difference. I booted up
>> Windows and it sees the USB drive just fine.
>>
>> Any things I should try or look at to try to figure out what is
>> happening? I really want to get an image of my system before moving in
>> three days.
>>
>> This is looking more and more like a bug. I con't know why nobody else
> had seen it, but here is more information:
> Relevant limes from bot:
> ehci0:  mem 0xf252a000-0xf252a3ff irq
> 16 at device 26.0 on pci0
> usbus0: EHCI version 1.0
> usbus0 on ehci0
> ehci1:  mem 0xf2529000-0xf25293ff irq
> 23 at device 29.0 on pci0
> sbus1: EHCI version 1.0
> usbus1 on ehci1
> [...]
> usbus0: 480Mbps High Speed USB v2.0
> usbus1: 480Mbps High Speed USB v2.0
> ugen1.1:  at usbus1
> uhub0:  on usbus1
> ugen0.1:  at usbus0
> uhub1:  on usbus0
> uhub0: 3 ports with 3 removable, self powered
> uhub1: 3 ports with 3 removable, self powered
> usbus0: port reset timeout
> usbus1: port reset timeout
> uhub_reattach_port: port 1 reset failed, error=USB_ERR_TIMEOUT
> uhub_reattach_port: device problem (USB_ERR_TIMEOUT), disabling port 1
> uhub_reattach_port: port 1 reset failed, error=USB_ERR_TIMEOUT
> uhub_reattach_port: device problem (USB_ERR_TIMEOUT), disabling port 1
>
> usbconfig -d ugen1.1 reset produced:
> Apr  9 09:15:11 rogue kernel: uhub1: at usbus0, port 1, addr 1
> (disconnected)
> Apr  9 09:15:11 rogue kernel: uhub1:
> Apr  9 09:15:11 rogue kernel:  2.00/1.00, addr 1> on usbus0
> Apr  9 09:15:12 rogue kernel: uhub1: 3 ports with 3 removable, self powered
>
> Any ideas would be GREATLY appreciated as I can't backup or restore my
> system.
>
> I hope to boot a live version of 11-RELEASE if I can find one, and see if
> it works.
> --
> Kevin Oberman, Part time kid herder and retired Network Engineer
> E-mail: rkober...@gmail.com
> PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683
>
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: No USB?

[Kevin Oberman]

On Sat, Apr 8, 2017 at 1:55 PM, Kevin Oberman <rkober...@gmail.com> wrote:

> Today, for the first time in a couple of weeks, I plugged in a USB drive
> to my 11-STABLE system (r316552). No device was created and usbconfig only
> sees EHCI hubs:
> ugen1.1:  at usbus1, cfg=0 md=HOST spd=HIGH (480Mbps)
> pwr=SAVE (0mA)
> ugen0.1:  at usbus0, cfg=0 md=HOST spd=HIGH (480Mbps)
> pwr=SAVE (0mA)
>
> Seems like I should be seeing UHCI stuff, too. Even internal devices like
> my webcam don't show up.
>
> I'm running a GENERIC kernel with the following exceptions:
> nooptions SCHED_ULE   # ULE scheduler
> options   SCHED_4BSD  # 4BSD scheduler
> optionsIEEE80211_DEBUG
>
> I tried updating my system and that made no difference. I booted up
> Windows and it sees the USB drive just fine.
>
> Any things I should try or look at to try to figure out what is happening?
> I really want to get an image of my system before moving in three days.
>
> This is looking more and more like a bug. I con't know why nobody else had
seen it, but here is more information:
Relevant limes from bot:
ehci0:  mem 0xf252a000-0xf252a3ff irq 16
at device 26.0 on pci0
usbus0: EHCI version 1.0
usbus0 on ehci0
ehci1:  mem 0xf2529000-0xf25293ff irq 23
at device 29.0 on pci0
sbus1: EHCI version 1.0
usbus1 on ehci1
[...]
usbus0: 480Mbps High Speed USB v2.0
usbus1: 480Mbps High Speed USB v2.0
ugen1.1:  at usbus1
uhub0:  on usbus1
ugen0.1:  at usbus0
uhub1:  on usbus0
uhub0: 3 ports with 3 removable, self powered
uhub1: 3 ports with 3 removable, self powered
usbus0: port reset timeout
usbus1: port reset timeout
uhub_reattach_port: port 1 reset failed, error=USB_ERR_TIMEOUT
uhub_reattach_port: device problem (USB_ERR_TIMEOUT), disabling port 1
uhub_reattach_port: port 1 reset failed, error=USB_ERR_TIMEOUT
uhub_reattach_port: device problem (USB_ERR_TIMEOUT), disabling port 1

usbconfig -d ugen1.1 reset produced:
Apr  9 09:15:11 rogue kernel: uhub1: at usbus0, port 1, addr 1
(disconnected)
Apr  9 09:15:11 rogue kernel: uhub1:
Apr  9 09:15:11 rogue kernel:  on usbus0
Apr  9 09:15:12 rogue kernel: uhub1: 3 ports with 3 removable, self powered

Any ideas would be GREATLY appreciated as I can't backup or restore my
system.

I hope to boot a live version of 11-RELEASE if I can find one, and see if
it works.
--
Kevin Oberman, Part time kid herder and retired Network Engineer
E-mail: rkober...@gmail.com
PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

No USB?

[Kevin Oberman]

Today, for the first time in a couple of weeks, I plugged in a USB drive to
my 11-STABLE system (r316552). No device was created and usbconfig only
sees EHCI hubs:
ugen1.1:  at usbus1, cfg=0 md=HOST spd=HIGH (480Mbps)
pwr=SAVE (0mA)
ugen0.1:  at usbus0, cfg=0 md=HOST spd=HIGH (480Mbps)
pwr=SAVE (0mA)

Seems like I should be seeing UHCI stuff, too. Even internal devices like
my webcam don't show up.

I'm running a GENERIC kernel with the following exceptions:
nooptions SCHED_ULE   # ULE scheduler
options   SCHED_4BSD  # 4BSD scheduler
optionsIEEE80211_DEBUG

I tried updating my system and that made no difference. I booted up Windows
and it sees the USB drive just fine.

Any things I should try or look at to try to figure out what is happening?
I really want to get an image of my system before moving in three days.
--
Kevin Oberman, Part time kid herder and retired Network Engineer
E-mail: rkober...@gmail.com
PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Unsupported USB BT device causes high interrupt load

[Dominic Fandrey]

I have an Interrupt load of 2000 interrupts/s from xhci0.

As the culprit I have identified the following device:

ugen0.6:  at usbus0, cfg=255 md=HOST spd=FULL 
(12Mbps) pwr=ON (100mA)

The impression I have from googling this is that it's an unsupported
BT device sitting on board of my Intel Wireless AC 7260 card (I also
have an unsupported SD/MMC card reader sitting on the mainboard).

usbconfig -d 0.6 power_off

Ends the interrupt spree.

I'm running FreeBSD 11.0-STABLE #1 r316490 amd64.

-- 
A: Because it fouls the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing on usenet and in e-mail? 



pgpI2LqSYaWqd.pgp
Description: PGP signature

Re: how can I make freebsd wait for usb to become active? Or delay mountroot?

[tech-lists]

On 13/02/2017 19:10, Paul Mather wrote:
> 
> This topic cropped up on the freebsd-arm mailing list very recently.
> One solution is to add this to /boot/loader.conf:
> 
> kern.cam.boot_delay="1"
> 
> That instructs the system to wait 10 seconds (1 milliseconds)
> during boot to give time for the CAM subsystem probes to complete.
> (USB storage devices use the CAM subsystem.)

>> vfs.root_mount_always_wait=1 loader tunable.  The knob should be
>> merged to 11 in two weeks.

I'll try that second suggestion as I'm already past r313350

thanks for the advice

-- 
J.
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: how can I make freebsd wait for usb to become active? Or delay mountroot?

[Chris H]

On Mon, 13 Feb 2017 19:00:39 + tech-lists <tech-li...@zyxst.net> wrote

> Hello stable@,
> 
> system: 11-stable r313553
> 
> In the kernel there is an option for scsi delay.
It should be enough to bump the kern.cam.scsi_delay=
a couple hundred at a time, until you find the "sweet spot".
You might also try the autoboot_delay= option instead. It
might give your USB port enough time to come ready.

> Is there also one for
> usb? Perhaps not in the kernel but elsewhere. I can't find it.
> 
> The problem is seen especially where the bootable device is usb. The
> boot process starts and dumps me at mountroot where I wait for a short
> time until the usb stick is properly detected (bright white writing at
> the console). The usb stick is plugged into a usb3 port. For example:
> 
> [snip]
> 
> usbus0: 5.0Gbps Super Speed USB v3.0
> usbus1: 12Mbps Full Speed USB v1.0
> usbus2: 480Mbps High Speed USB v2.0
> usbus3: 12Mbps Full Speed USB v1.0
> ugen0.1: <0x1022 XHCI root HUB> at usbus0
> uhub0: <0x1022 XHCI root HUB, class 9/0, rev 3.00/1.00, addr 1> on usbus0
> ugen1.1:  at usbus1
> uhub1:  on usbus1
> ugen2.1:  at usbus2
> uhub2:  on usbus2
> ugen3.1:  at usbus3
> uhub3:  on usbus3
> usbus4: 480Mbps High Speed USB v2.0
> ugen4.1:  at usbus4
> uhub4:  on usbus4
> acpi_tz0: _CRT value is absurd, ignored (255.1C)
> ada0 at ahcich0 bus 0 scbus0 target 0 lun 0
> ada0:  ACS-2 ATA SATA 3.x device
> cd0 at ahcich1 bus 0 scbus1 target 0 lun 0
> cd0:  Removable CD-ROM SCSI device
> cd0: Serial Number 1415TP277450E0H6H
> cd0: 150.000MB/s transfers (SATA 1.x, UDMA5, ATAPI 12bytes, PIO 8192bytes)
> cd0: Attempt to query device size failed: NOT READY, Medium not present
> - tray open
> ada0: Serial Number JA1006103G0ALV
> ada0: 300.000MB/s transfers (SATA 2.x, UDMA6, PIO 8192bytes)
> ada0: Command Queueing enabled
> ada0: 953869MB (1953525168 512 byte sectors)
> SMP: AP CPU #3 Launched!
> SMP: AP CPU #1 Launched!
> SMP: AP CPU #2 Launched!
> Timecounter "TSC" frequency 1597045198 Hz quality 1000
> Trying to mount root from ufs:/dev/da0p2 [rw]...
> uhub3: 5 ports with 5 removable, self powered
> uhub1: 5 ports with 5 removable, self powered
> uhub0: 4 ports with 4 removable, self powered
> Root mount waiting for: usbus4 usbus2 usbus0
> ugen0.2:  at usbus0
> umass0 on uhub0
> umass0: 
> on usbus0
> umass0:  SCSI over Bulk-Only; quirks = 0x8100
> umass0:3:0: Attached to scbus3
> uhub2: 5 ports with 5 removable, self powered
> uhub4: 5 ports with 5 removable, self powered
> ugen0.3:  at usbus0
> ukbd0 on uhub0
> ukbd0:  on usbus0
> kbd2 at ukbd0
> Root mount waiting for: usbus4
> ugen4.2:  at usbus4
> mountroot: waiting for device /dev/da0p2...
> Mounting from ufs:/dev/da0p2 failed with error 19.
> 
> Loader variables:
>   vfs.root.mountfrom=ufs:/dev/da0p2
>   vfs.root.mountfrom.options=rw
> 
> Manual root filesystem specification:
>   : [options]
>   Mount  using filesystem 
>   and with the specified (optional) option list.
> 
> eg. ufs:/dev/da0s1a
> zfs:tank
> cd9660:/dev/cd0 ro
>   (which is equivalent to: mount -t cd9660 -o ro /dev/cd0 /)
> 
>   ?   List valid disk boot devices
>   .   Yield 1 second (for background tasks)
>   Abort manual input
> 
> mountroot> Trying to mount root from ufs:/dev/da0p2 []...
> mountroot: waiting for device /dev/da0p2...
> Mounting from ufs:/dev/da0p2 failed with error 19.
> 
> mountroot>
> 
> [snip]
> 
> Then this happens:
> 
> (probe0:umass-sim0:0:0:0): INQUIRY. CDB: 12 00 00 00 24 00
> (probe0:umass-sim0:0:0:0): CAM status: CCB request completed with an error
> (probe0:umass-sim0:0:0:0): Retrying command
> da0 at umass-sim0 bus 0 scbus3 target 0 lun 0
> da0: < USB DISK 3.0 PMAP> Removable Direct Access SPC-4 SCSI device
> da0: Serial Number 070B4722335D3288
> da0: 400.000MB/s transfers
> da0: 30176MB (61800448 512 byte sectors)
> da0: quirks=0x3<NO_SYNC_CACHE,NO_6_BYTE>
> 
> so now at the mountroot prompt I enter ufs:/dev/da0p2 (which is a value
> that mountroot already had) and carry on booting:
> 
> mountroot> Trying to mount root from ufs:/dev/da0p2 []...
> re0: link state changed to DOWN
> re0: link state changed to UP
> ums0 on uhub0
> ums0:  on usbus0
> ums0: 16 buttons and [XYZT] coordinates ID=2
> uhid0 on uhub0
> uhid0:  on usbus0
> 
> [...]
> 
> The same sort of thing happens on an 11-stable r313043 desktop, only
> this time I'm not booting from usb. The system comes up, I get a login
> prompt, then five or ten seconds later usb wakes up having detected the
> usb3 external HD.
> 
> 

Re: how can I make freebsd wait for usb to become active? Or delay mountroot?

[Paul Mather]

On Feb 13, 2017, at 2:00 PM, tech-lists <tech-li...@zyxst.net> wrote:

> Hello stable@,
> 
> system: 11-stable r313553
> 
> In the kernel there is an option for scsi delay. Is there also one for
> usb? Perhaps not in the kernel but elsewhere. I can't find it.
> 
> The problem is seen especially where the bootable device is usb. The
> boot process starts and dumps me at mountroot where I wait for a short
> time until the usb stick is properly detected (bright white writing at
> the console). The usb stick is plugged into a usb3 port. For example:
> 
> [snip]
> 
> usbus0: 5.0Gbps Super Speed USB v3.0
> usbus1: 12Mbps Full Speed USB v1.0
> usbus2: 480Mbps High Speed USB v2.0
> usbus3: 12Mbps Full Speed USB v1.0
> ugen0.1: <0x1022 XHCI root HUB> at usbus0
> uhub0: <0x1022 XHCI root HUB, class 9/0, rev 3.00/1.00, addr 1> on usbus0
> ugen1.1:  at usbus1
> uhub1:  on usbus1
> ugen2.1:  at usbus2
> uhub2:  on usbus2
> ugen3.1:  at usbus3
> uhub3:  on usbus3
> usbus4: 480Mbps High Speed USB v2.0
> ugen4.1:  at usbus4
> uhub4:  on usbus4
> acpi_tz0: _CRT value is absurd, ignored (255.1C)
> ada0 at ahcich0 bus 0 scbus0 target 0 lun 0
> ada0:  ACS-2 ATA SATA 3.x device
> cd0 at ahcich1 bus 0 scbus1 target 0 lun 0
> cd0:  Removable CD-ROM SCSI device
> cd0: Serial Number 1415TP277450E0H6H
> cd0: 150.000MB/s transfers (SATA 1.x, UDMA5, ATAPI 12bytes, PIO 8192bytes)
> cd0: Attempt to query device size failed: NOT READY, Medium not present
> - tray open
> ada0: Serial Number JA1006103G0ALV
> ada0: 300.000MB/s transfers (SATA 2.x, UDMA6, PIO 8192bytes)
> ada0: Command Queueing enabled
> ada0: 953869MB (1953525168 512 byte sectors)
> SMP: AP CPU #3 Launched!
> SMP: AP CPU #1 Launched!
> SMP: AP CPU #2 Launched!
> Timecounter "TSC" frequency 1597045198 Hz quality 1000
> Trying to mount root from ufs:/dev/da0p2 [rw]...
> uhub3: 5 ports with 5 removable, self powered
> uhub1: 5 ports with 5 removable, self powered
> uhub0: 4 ports with 4 removable, self powered
> Root mount waiting for: usbus4 usbus2 usbus0
> ugen0.2:  at usbus0
> umass0 on uhub0
> umass0: 
> on usbus0
> umass0:  SCSI over Bulk-Only; quirks = 0x8100
> umass0:3:0: Attached to scbus3
> uhub2: 5 ports with 5 removable, self powered
> uhub4: 5 ports with 5 removable, self powered
> ugen0.3:  at usbus0
> ukbd0 on uhub0
> ukbd0:  on usbus0
> kbd2 at ukbd0
> Root mount waiting for: usbus4
> ugen4.2:  at usbus4
> mountroot: waiting for device /dev/da0p2...
> Mounting from ufs:/dev/da0p2 failed with error 19.
> 
> Loader variables:
>  vfs.root.mountfrom=ufs:/dev/da0p2
>  vfs.root.mountfrom.options=rw
> 
> Manual root filesystem specification:
>  : [options]
>  Mount  using filesystem 
>  and with the specified (optional) option list.
> 
>eg. ufs:/dev/da0s1a
>zfs:tank
>cd9660:/dev/cd0 ro
>  (which is equivalent to: mount -t cd9660 -o ro /dev/cd0 /)
> 
>  ?   List valid disk boot devices
>  .   Yield 1 second (for background tasks)
>  Abort manual input
> 
> mountroot> Trying to mount root from ufs:/dev/da0p2 []...
> mountroot: waiting for device /dev/da0p2...
> Mounting from ufs:/dev/da0p2 failed with error 19.
> 
> mountroot>
> 
> [snip]
> 
> Then this happens:
> 
> (probe0:umass-sim0:0:0:0): INQUIRY. CDB: 12 00 00 00 24 00
> (probe0:umass-sim0:0:0:0): CAM status: CCB request completed with an error
> (probe0:umass-sim0:0:0:0): Retrying command
> da0 at umass-sim0 bus 0 scbus3 target 0 lun 0
> da0: < USB DISK 3.0 PMAP> Removable Direct Access SPC-4 SCSI device
> da0: Serial Number 070B4722335D3288
> da0: 400.000MB/s transfers
> da0: 30176MB (61800448 512 byte sectors)
> da0: quirks=0x3<NO_SYNC_CACHE,NO_6_BYTE>
> 
> so now at the mountroot prompt I enter ufs:/dev/da0p2 (which is a value
> that mountroot already had) and carry on booting:
> 
> mountroot> Trying to mount root from ufs:/dev/da0p2 []...
> re0: link state changed to DOWN
> re0: link state changed to UP
> ums0 on uhub0
> ums0:  on usbus0
> ums0: 16 buttons and [XYZT] coordinates ID=2
> uhid0 on uhub0
> uhid0:  on usbus0
> 
> [...]
> 
> The same sort of thing happens on an 11-stable r313043 desktop, only
> this time I'm not booting from usb. The system comes up, I get a login
> prompt, then five or ten seconds later usb wakes up having detected the
> usb3 external HD.
> 
> How can I fix this?


This topic cropped up on the freebsd-arm mailing list very recently.  One 
solution is to add this to /boot/loader.conf:

kern.cam.boot_delay="1"

That instructs the system to wait 10 seconds (1 milliseconds) du

how can I make freebsd wait for usb to become active? Or delay mountroot?

[tech-lists]

Hello stable@,

system: 11-stable r313553

In the kernel there is an option for scsi delay. Is there also one for
usb? Perhaps not in the kernel but elsewhere. I can't find it.

The problem is seen especially where the bootable device is usb. The
boot process starts and dumps me at mountroot where I wait for a short
time until the usb stick is properly detected (bright white writing at
the console). The usb stick is plugged into a usb3 port. For example:

[snip]

usbus0: 5.0Gbps Super Speed USB v3.0
usbus1: 12Mbps Full Speed USB v1.0
usbus2: 480Mbps High Speed USB v2.0
usbus3: 12Mbps Full Speed USB v1.0
ugen0.1: <0x1022 XHCI root HUB> at usbus0
uhub0: <0x1022 XHCI root HUB, class 9/0, rev 3.00/1.00, addr 1> on usbus0
ugen1.1:  at usbus1
uhub1:  on usbus1
ugen2.1:  at usbus2
uhub2:  on usbus2
ugen3.1:  at usbus3
uhub3:  on usbus3
usbus4: 480Mbps High Speed USB v2.0
ugen4.1:  at usbus4
uhub4:  on usbus4
acpi_tz0: _CRT value is absurd, ignored (255.1C)
ada0 at ahcich0 bus 0 scbus0 target 0 lun 0
ada0:  ACS-2 ATA SATA 3.x device
cd0 at ahcich1 bus 0 scbus1 target 0 lun 0
cd0:  Removable CD-ROM SCSI device
cd0: Serial Number 1415TP277450E0H6H
cd0: 150.000MB/s transfers (SATA 1.x, UDMA5, ATAPI 12bytes, PIO 8192bytes)
cd0: Attempt to query device size failed: NOT READY, Medium not present
- tray open
ada0: Serial Number JA1006103G0ALV
ada0: 300.000MB/s transfers (SATA 2.x, UDMA6, PIO 8192bytes)
ada0: Command Queueing enabled
ada0: 953869MB (1953525168 512 byte sectors)
SMP: AP CPU #3 Launched!
SMP: AP CPU #1 Launched!
SMP: AP CPU #2 Launched!
Timecounter "TSC" frequency 1597045198 Hz quality 1000
Trying to mount root from ufs:/dev/da0p2 [rw]...
uhub3: 5 ports with 5 removable, self powered
uhub1: 5 ports with 5 removable, self powered
uhub0: 4 ports with 4 removable, self powered
Root mount waiting for: usbus4 usbus2 usbus0
ugen0.2:  at usbus0
umass0 on uhub0
umass0: 
on usbus0
umass0:  SCSI over Bulk-Only; quirks = 0x8100
umass0:3:0: Attached to scbus3
uhub2: 5 ports with 5 removable, self powered
uhub4: 5 ports with 5 removable, self powered
ugen0.3:  at usbus0
ukbd0 on uhub0
ukbd0:  on usbus0
kbd2 at ukbd0
Root mount waiting for: usbus4
ugen4.2:  at usbus4
mountroot: waiting for device /dev/da0p2...
Mounting from ufs:/dev/da0p2 failed with error 19.

Loader variables:
  vfs.root.mountfrom=ufs:/dev/da0p2
  vfs.root.mountfrom.options=rw

Manual root filesystem specification:
  : [options]
  Mount  using filesystem 
  and with the specified (optional) option list.

eg. ufs:/dev/da0s1a
zfs:tank
cd9660:/dev/cd0 ro
  (which is equivalent to: mount -t cd9660 -o ro /dev/cd0 /)

  ?   List valid disk boot devices
  .   Yield 1 second (for background tasks)
  Abort manual input

mountroot> Trying to mount root from ufs:/dev/da0p2 []...
mountroot: waiting for device /dev/da0p2...
Mounting from ufs:/dev/da0p2 failed with error 19.

mountroot>

[snip]

Then this happens:

(probe0:umass-sim0:0:0:0): INQUIRY. CDB: 12 00 00 00 24 00
(probe0:umass-sim0:0:0:0): CAM status: CCB request completed with an error
(probe0:umass-sim0:0:0:0): Retrying command
da0 at umass-sim0 bus 0 scbus3 target 0 lun 0
da0: < USB DISK 3.0 PMAP> Removable Direct Access SPC-4 SCSI device
da0: Serial Number 070B4722335D3288
da0: 400.000MB/s transfers
da0: 30176MB (61800448 512 byte sectors)
da0: quirks=0x3<NO_SYNC_CACHE,NO_6_BYTE>

so now at the mountroot prompt I enter ufs:/dev/da0p2 (which is a value
that mountroot already had) and carry on booting:

mountroot> Trying to mount root from ufs:/dev/da0p2 []...
re0: link state changed to DOWN
re0: link state changed to UP
ums0 on uhub0
ums0:  on usbus0
ums0: 16 buttons and [XYZT] coordinates ID=2
uhid0 on uhub0
uhid0:  on usbus0

[...]

The same sort of thing happens on an 11-stable r313043 desktop, only
this time I'm not booting from usb. The system comes up, I get a login
prompt, then five or ten seconds later usb wakes up having detected the
usb3 external HD.

How can I fix this?

thanks,
-- 
J.
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: usb 3.0 thumb drive speed limit

[Marat N.Afanasyev]

Florian Ermisch wrote:



Am 2. Januar 2017 10:59:49 MEZ, schrieb "Marat N.Afanasyev" <ama...@li.ru>:

Ian Smith wrote:

On Mon, 2 Jan 2017 11:27:49 +0300, Marat N.Afanasyev wrote:
   > I wonder is there a speed limit on usb 3.0? I've bought
   >
   > ugen0.4:  at usbus0
   > umass2 on uhub7
   > umass2:  on

usbus0

   > da2 at umass-sim2 bus 2 scbus9 target 0 lun 0
   > da2:  Removable Direct Access SPC-4 SCSI

device

   > da2: Serial Number AA010808161609220143
   > da2: 40.000MB/s transfers
   > da2: 59840MB (122552320 512 byte sectors)
   > da2: quirks=0x2
   >
   > that claims 'Up to 245 MBytes/sec read speed'
   >
   > and dd shows:
   >
   > % dd if=/dev/da2 of=/dev/null bs=1m count=1000
   > 1000+0 records in
   > 1000+0 records out
   > 1048576000 bytes transferred in 25.688997 secs (40818098

bytes/sec)

   >
   > why we have such a limit?

Seems you've plugged it into a USB 2 port, not USB 3

At least you're getting full USB 2 performance (40MB/s)

Check if you have one or more USB 3 ports with 'dmesg | grep xhci'

cheers, Ian



afair, single usb 2.0 device can be as fast as 240 Mbits/sec, not 320
Mbits/sec:

% dd if=/dev/da2 of=/dev/null bs=1m count=1000
1000+0 records in
1000+0 records out
1048576000 bytes transferred in 34.026227 secs (30816699 bytes/sec)

it's the same drive in usb 2.0 port

And I do have usb 3.0:

% grep xhci /var/run/dmesg.boot
xhci0:  mem 0xfeaf8000-0xfeaf
irq
17 at device 0.0 on pci5
xhci0: 64 bytes context size, 64-bit DMA
usbus0 on xhci0
xhci0:  mem 0xfeaf8000-0xfeaf
irq
17 at device 0.0 on pci5
xhci0: 64 bytes context size, 64-bit DMA
usbus0 on xhci0

and I tried this thumb drive is in usb 3.0 port first, of course.


Are you running 10.x or 11.0?

When was running 10.1 I only got
~27 MB/s out of each of my two
external HDDs connected to the
same USB3 port (two disk enclosure,
speed according to `zpool iostat -v`
AFAIR).
They also attached as high-speed
devices.
Some time after upgrading to the
than current 11-CURRENT I've
noticed kernel messages mentioning
400 MB/s instead of 40 MB/s and
quite an improvement in throughput.

May be a quirk in the driver for your
paricular XHCI chip.

Regards, Florian
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"


11.0

I think that i have somehow buggy addon card :(

--
SY, Marat



smime.p7s
Description: S/MIME Cryptographic Signature

Re: usb 3.0 thumb drive speed limit

[Florian Ermisch]

Am 2. Januar 2017 10:59:49 MEZ, schrieb "Marat N.Afanasyev" <ama...@li.ru>:
> Ian Smith wrote:
> > On Mon, 2 Jan 2017 11:27:49 +0300, Marat N.Afanasyev wrote:
> >   > I wonder is there a speed limit on usb 3.0? I've bought
> >   >
> >   > ugen0.4:  at usbus0
> >   > umass2 on uhub7
> >   > umass2:  on
> usbus0
> >   > da2 at umass-sim2 bus 2 scbus9 target 0 lun 0
> >   > da2:  Removable Direct Access SPC-4 SCSI
> device
> >   > da2: Serial Number AA010808161609220143
> >   > da2: 40.000MB/s transfers
> >   > da2: 59840MB (122552320 512 byte sectors)
> >   > da2: quirks=0x2
> >   >
> >   > that claims 'Up to 245 MBytes/sec read speed'
> >   >
> >   > and dd shows:
> >   >
> >   > % dd if=/dev/da2 of=/dev/null bs=1m count=1000
> >   > 1000+0 records in
> >   > 1000+0 records out
> >   > 1048576000 bytes transferred in 25.688997 secs (40818098
> bytes/sec)
> >   >
> >   > why we have such a limit?
> >
> > Seems you've plugged it into a USB 2 port, not USB 3
> >
> > At least you're getting full USB 2 performance (40MB/s)
> >
> > Check if you have one or more USB 3 ports with 'dmesg | grep xhci'
> >
> > cheers, Ian
> > 
> >
> afair, single usb 2.0 device can be as fast as 240 Mbits/sec, not 320 
> Mbits/sec:
> 
> % dd if=/dev/da2 of=/dev/null bs=1m count=1000
> 1000+0 records in
> 1000+0 records out
> 1048576000 bytes transferred in 34.026227 secs (30816699 bytes/sec)
> 
> it's the same drive in usb 2.0 port
> 
> And I do have usb 3.0:
> 
> % grep xhci /var/run/dmesg.boot
> xhci0:  mem 0xfeaf8000-0xfeaf
> irq 
> 17 at device 0.0 on pci5
> xhci0: 64 bytes context size, 64-bit DMA
> usbus0 on xhci0
> xhci0:  mem 0xfeaf8000-0xfeaf
> irq 
> 17 at device 0.0 on pci5
> xhci0: 64 bytes context size, 64-bit DMA
> usbus0 on xhci0
> 
> and I tried this thumb drive is in usb 3.0 port first, of course.

Are you running 10.x or 11.0?

When was running 10.1 I only got 
~27 MB/s out of each of my two 
external HDDs connected to the
same USB3 port (two disk enclosure,
speed according to `zpool iostat -v`
AFAIR).
They also attached as high-speed
devices.
Some time after upgrading to the 
than current 11-CURRENT I've
noticed kernel messages mentioning
400 MB/s instead of 40 MB/s and 
quite an improvement in throughput.

May be a quirk in the driver for your
paricular XHCI chip.

Regards, Florian 
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: usb 3.0 thumb drive speed limit

[Marat N.Afanasyev]

Gary Palmer wrote:

On Mon, Jan 02, 2017 at 11:27:49AM +0300, Marat N.Afanasyev wrote:

I wonder is there a speed limit on usb 3.0? I've bought

ugen0.4:  at usbus0
umass2 on uhub7
umass2:  on usbus0
da2 at umass-sim2 bus 2 scbus9 target 0 lun 0
da2:  Removable Direct Access SPC-4 SCSI device
da2: Serial Number AA010808161609220143
da2: 40.000MB/s transfers
da2: 59840MB (122552320 512 byte sectors)
da2: quirks=0x2

that claims 'Up to 245 MBytes/sec read speed'


I don't think the speed reported by the SCSI layer (CAM) is correct
for USB, although it seems from an experiment here that if you
plug a USB3 drive into a USB2 port it reports "40.000MB/s transfers"
and on a USB3 port it reports "400.000MB/s transfers".  SCSI doesn't
really have any direct mapping to the USB speeds so I suspect the
USB stack uses the closest value.  The tests I did were with 10.3.
Other releases may behave differently.

Check with usbconfig what the negotiated USB speed is (the "spd=" value
with the Mbps or Gbps value in brackets afterwards)

FULL = USB1
HIGH = USB2
SUPER = USB3

Regards,

Gary
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"



it seems that drive doesn't attach as usb 3.0 even when plugged into 
pci-e card port directly, to say nothing about the hub. probably it's 
buggy firmware of addon card, I'll try to find newer firmware and flash 
it, if one exists


--
SY, Marat



smime.p7s
Description: S/MIME Cryptographic Signature

Re: usb 3.0 thumb drive speed limit

[Warner Losh]

On Mon, Jan 2, 2017 at 11:42 AM, Gary Palmer <gpal...@freebsd.org> wrote:
> On Mon, Jan 02, 2017 at 11:27:49AM +0300, Marat N.Afanasyev wrote:
>> I wonder is there a speed limit on usb 3.0? I've bought
>>
>> ugen0.4:  at usbus0
>> umass2 on uhub7
>> umass2:  on usbus0
>> da2 at umass-sim2 bus 2 scbus9 target 0 lun 0
>> da2:  Removable Direct Access SPC-4 SCSI device
>> da2: Serial Number AA010808161609220143
>> da2: 40.000MB/s transfers
>> da2: 59840MB (122552320 512 byte sectors)
>> da2: quirks=0x2
>>
>> that claims 'Up to 245 MBytes/sec read speed'
>
> I don't think the speed reported by the SCSI layer (CAM) is correct
> for USB, although it seems from an experiment here that if you
> plug a USB3 drive into a USB2 port it reports "40.000MB/s transfers"
> and on a USB3 port it reports "400.000MB/s transfers".  SCSI doesn't
> really have any direct mapping to the USB speeds so I suspect the
> USB stack uses the closest value.  The tests I did were with 10.3.
> Other releases may behave differently.
>
> Check with usbconfig what the negotiated USB speed is (the "spd=" value
> with the Mbps or Gbps value in brackets afterwards)
>
> FULL = USB1
> HIGH = USB2
> SUPER = USB3

40MB/s is just a number that's reported. It's not a speed limit.

Our USB stack reports that we understand SCSI protocol rev 2, but we
use the XPORT_USB for the transport. This means the code that prints
those numbers in scsi_xpt.c will use base_transfer_speed from the
XPT_PATH_INQ command. umass.c sets this to either 40MB/s or 400MB/s in
a decision that boils down to if that code thinks the transfer is over
USB 2.0 or 3.0. The fact that we're reporting 40MB/s rather than
400MB/s suggests to me that it was attached on a USB 2.0 hub rather
than a USB 3.0 hub, or it was attached with HIGH speed to a 3.0 hub
because the signals needed to do the SUPER speed were missing. On many
computers, only the "blue" USB ports are 3.0 speed, and only then when
wired correctly (as I discovered the hard way with a recent mobo I put
into service).

For reference, for USB connected umass devices, the driver returns
20kB/s for devices claiming to be floppies, 1MB/s for FULL speed
transfers, 40MB/s for HIGH speed and 400MB/s for SUPER speed.

Looking at the latest code, it sure looks like USB speeds are reported
correctly, or nearly correctly, up to the CAM layer as a good first
order estimate for how fast the drive can code. They do assume a 33%
overhead on USB (which is typical), so that's consistent with getting
just over 40MB/s from dd for a HIGH speed device.

Warner
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: usb 3.0 thumb drive speed limit

[Gary Palmer]

On Mon, Jan 02, 2017 at 11:27:49AM +0300, Marat N.Afanasyev wrote:
> I wonder is there a speed limit on usb 3.0? I've bought
> 
> ugen0.4:  at usbus0
> umass2 on uhub7
> umass2:  on usbus0
> da2 at umass-sim2 bus 2 scbus9 target 0 lun 0
> da2:  Removable Direct Access SPC-4 SCSI device
> da2: Serial Number AA010808161609220143
> da2: 40.000MB/s transfers
> da2: 59840MB (122552320 512 byte sectors)
> da2: quirks=0x2
> 
> that claims 'Up to 245 MBytes/sec read speed'

I don't think the speed reported by the SCSI layer (CAM) is correct
for USB, although it seems from an experiment here that if you 
plug a USB3 drive into a USB2 port it reports "40.000MB/s transfers"
and on a USB3 port it reports "400.000MB/s transfers".  SCSI doesn't
really have any direct mapping to the USB speeds so I suspect the
USB stack uses the closest value.  The tests I did were with 10.3.
Other releases may behave differently.

Check with usbconfig what the negotiated USB speed is (the "spd=" value
with the Mbps or Gbps value in brackets afterwards)

FULL = USB1
HIGH = USB2
SUPER = USB3

Regards,

Gary
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: usb 3.0 thumb drive speed limit

[Lowell Gilbert]

Ian Smith <smi...@nimnet.asn.au> writes:

> On Mon, 2 Jan 2017 12:59:49 +0300, Marat N.Afanasyev wrote:
>  > Ian Smith wrote:
>  > > 
>  > > Seems you've plugged it into a USB 2 port, not USB 3
>  > > 
>  > > At least you're getting full USB 2 performance (40MB/s)
>  > > 
>  > > Check if you have one or more USB 3 ports with 'dmesg | grep xhci'
>
>  > afair, single usb 2.0 device can be as fast as 240 Mbits/sec, not 320

280 Mbits/sec, actually.

>  > Mbits/sec:
>  > 
>  > % dd if=/dev/da2 of=/dev/null bs=1m count=1000
>  > 1000+0 records in
>  > 1000+0 records out
>  > 1048576000 bytes transferred in 34.026227 secs (30816699 bytes/sec)

30816699 bytes/sec is a little over 30 Megabytes per second. Which is
about right. Was someone misplacing a decimal? Or confusing bits with
bytes?

[Making things more confusing is that generally people refer to
megabytes as 10e6 for disks and 2e20 for memory. For flash, it's the
latter, but if you access it through a "disk" interface (like a thumb
drive), you'll generally get 10e6 type numbers.

>  > 
>  > it's the same drive in usb 2.0 port
>
> Ah, guess I've been taking "40.000MB/s transfers" for USB2 at its word.

The 40MB/s number includes overhead, so you'll never get quite that high.

> Testing 3 USB2 sticks in a USB2 port on my X200 (2.4GHz Core2Duo) I only 
> get about 18-20MB/s read for bs=1M count=1k, with little load although 
> 3k IRQ/s and 10k context switches/s, so I thought yours was good :)

These things will vary with your hardware; both the driver chips in the
computer and the flash stick itself. And some other things too, but I
can't recall exactly.
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: usb 3.0 thumb drive speed limit

[Ian Smith]

On Mon, 2 Jan 2017 12:59:49 +0300, Marat N.Afanasyev wrote:
 > Ian Smith wrote:
 > > On Mon, 2 Jan 2017 11:27:49 +0300, Marat N.Afanasyev wrote:
 > >   > I wonder is there a speed limit on usb 3.0? I've bought
 > >   >
 > >   > ugen0.4:  at usbus0
 > >   > umass2 on uhub7
 > >   > umass2:  on usbus0
 > >   > da2 at umass-sim2 bus 2 scbus9 target 0 lun 0
 > >   > da2:  Removable Direct Access SPC-4 SCSI device
 > >   > da2: Serial Number AA010808161609220143
 > >   > da2: 40.000MB/s transfers
 > >   > da2: 59840MB (122552320 512 byte sectors)
 > >   > da2: quirks=0x2
 > >   >
 > >   > that claims 'Up to 245 MBytes/sec read speed'
 > >   >
 > >   > and dd shows:
 > >   >
 > >   > % dd if=/dev/da2 of=/dev/null bs=1m count=1000
 > >   > 1000+0 records in
 > >   > 1000+0 records out
 > >   > 1048576000 bytes transferred in 25.688997 secs (40818098 bytes/sec)
 > >   >
 > >   > why we have such a limit?
 > > 
 > > Seems you've plugged it into a USB 2 port, not USB 3
 > > 
 > > At least you're getting full USB 2 performance (40MB/s)
 > > 
 > > Check if you have one or more USB 3 ports with 'dmesg | grep xhci'

 > afair, single usb 2.0 device can be as fast as 240 Mbits/sec, not 320
 > Mbits/sec:
 > 
 > % dd if=/dev/da2 of=/dev/null bs=1m count=1000
 > 1000+0 records in
 > 1000+0 records out
 > 1048576000 bytes transferred in 34.026227 secs (30816699 bytes/sec)
 > 
 > it's the same drive in usb 2.0 port

Ah, guess I've been taking "40.000MB/s transfers" for USB2 at its word.

Testing 3 USB2 sticks in a USB2 port on my X200 (2.4GHz Core2Duo) I only 
get about 18-20MB/s read for bs=1M count=1k, with little load although 
3k IRQ/s and 10k context switches/s, so I thought yours was good :)

 > And I do have usb 3.0:
 > 
 > % grep xhci /var/run/dmesg.boot
 > xhci0:  mem 0xfeaf8000-0xfeaf irq 17
 > at device 0.0 on pci5
 > xhci0: 64 bytes context size, 64-bit DMA
 > usbus0 on xhci0
 > xhci0:  mem 0xfeaf8000-0xfeaf irq 17
 > at device 0.0 on pci5
 > xhci0: 64 bytes context size, 64-bit DMA
 > usbus0 on xhci0
 > 
 > and I tried this thumb drive is in usb 3.0 port first, of course.

Sorry for the static, I know nothing .. and running now unsupported 9.3

cheers, Ian
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: usb 3.0 thumb drive speed limit

[Marat N.Afanasyev]

Ian Smith wrote:

On Mon, 2 Jan 2017 11:27:49 +0300, Marat N.Afanasyev wrote:
  > I wonder is there a speed limit on usb 3.0? I've bought
  >
  > ugen0.4:  at usbus0
  > umass2 on uhub7
  > umass2:  on usbus0
  > da2 at umass-sim2 bus 2 scbus9 target 0 lun 0
  > da2:  Removable Direct Access SPC-4 SCSI device
  > da2: Serial Number AA010808161609220143
  > da2: 40.000MB/s transfers
  > da2: 59840MB (122552320 512 byte sectors)
  > da2: quirks=0x2
  >
  > that claims 'Up to 245 MBytes/sec read speed'
  >
  > and dd shows:
  >
  > % dd if=/dev/da2 of=/dev/null bs=1m count=1000
  > 1000+0 records in
  > 1000+0 records out
  > 1048576000 bytes transferred in 25.688997 secs (40818098 bytes/sec)
  >
  > why we have such a limit?

Seems you've plugged it into a USB 2 port, not USB 3

At least you're getting full USB 2 performance (40MB/s)

Check if you have one or more USB 3 ports with 'dmesg | grep xhci'

cheers, Ian
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

afair, single usb 2.0 device can be as fast as 240 Mbits/sec, not 320 
Mbits/sec:


% dd if=/dev/da2 of=/dev/null bs=1m count=1000
1000+0 records in
1000+0 records out
1048576000 bytes transferred in 34.026227 secs (30816699 bytes/sec)

it's the same drive in usb 2.0 port

And I do have usb 3.0:

% grep xhci /var/run/dmesg.boot
xhci0:  mem 0xfeaf8000-0xfeaf irq 
17 at device 0.0 on pci5

xhci0: 64 bytes context size, 64-bit DMA
usbus0 on xhci0
xhci0:  mem 0xfeaf8000-0xfeaf irq 
17 at device 0.0 on pci5

xhci0: 64 bytes context size, 64-bit DMA
usbus0 on xhci0

and I tried this thumb drive is in usb 3.0 port first, of course.

--
SY, Marat



smime.p7s
Description: S/MIME Cryptographic Signature

Re: usb 3.0 thumb drive speed limit

[Ian Smith]

On Mon, 2 Jan 2017 11:27:49 +0300, Marat N.Afanasyev wrote:
 > I wonder is there a speed limit on usb 3.0? I've bought
 > 
 > ugen0.4:  at usbus0
 > umass2 on uhub7
 > umass2:  on usbus0
 > da2 at umass-sim2 bus 2 scbus9 target 0 lun 0
 > da2:  Removable Direct Access SPC-4 SCSI device
 > da2: Serial Number AA010808161609220143
 > da2: 40.000MB/s transfers
 > da2: 59840MB (122552320 512 byte sectors)
 > da2: quirks=0x2
 > 
 > that claims 'Up to 245 MBytes/sec read speed'
 > 
 > and dd shows:
 > 
 > % dd if=/dev/da2 of=/dev/null bs=1m count=1000
 > 1000+0 records in
 > 1000+0 records out
 > 1048576000 bytes transferred in 25.688997 secs (40818098 bytes/sec)
 > 
 > why we have such a limit?

Seems you've plugged it into a USB 2 port, not USB 3

At least you're getting full USB 2 performance (40MB/s)

Check if you have one or more USB 3 ports with 'dmesg | grep xhci'

cheers, Ian
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

usb 3.0 thumb drive speed limit

[Marat N.Afanasyev]

I wonder is there a speed limit on usb 3.0? I've bought

ugen0.4:  at usbus0
umass2 on uhub7
umass2:  on usbus0
da2 at umass-sim2 bus 2 scbus9 target 0 lun 0
da2:  Removable Direct Access SPC-4 SCSI device
da2: Serial Number AA010808161609220143
da2: 40.000MB/s transfers
da2: 59840MB (122552320 512 byte sectors)
da2: quirks=0x2

that claims 'Up to 245 MBytes/sec read speed'

and dd shows:

% dd if=/dev/da2 of=/dev/null bs=1m count=1000
1000+0 records in
1000+0 records out
1048576000 bytes transferred in 25.688997 secs (40818098 bytes/sec)

why we have such a limit?

--
SY, Marat



smime.p7s
Description: S/MIME Cryptographic Signature

Re: moxa uport 1110 RS232 USB to serial support?

[Marko Cupać]

On Fri, 18 Nov 2016 14:28:58 +0100
Arrigo Marchiori via freebsd-stable <freebsd-stable@freebsd.org> wrote:

> Hello,
> 
> I am resending this reply message to the freebsd-usb@ and
> freebsd-stable@ mailing list, because it bounced back to me after one
> day.
>
> I am afraid that the short answer is «no».
> 
> For what I could find on-line:
> 
>  - the Moxa UPort 1110 driver for Linux is the same as the Texas
>Instruments TUSB3410
>(source:
> https://git.kernel.org/cgit/linux/kernel/git/stable/linux-stable.git/commit/drivers/usb/serial?id=b923c6c62981cec5e2d2187fd700c2fc4386fc45)
> 
>  - the port comms/uticom was a driver for the TUSB3410, but it was
>deprecated, and removed three years ago.
>FreeBSD forum thread: https://forums.freebsd.org/threads/18151/
>Port information: http://www.freshports.org/comms/uticom
>SourceForge page: https://sourceforge.net/projects/uticom/
> 
> I hope this helps.

Arrigo,

it does help, thank you. I'm not subscribed to freebsd-usb, but I'm
gonna check archives to see if there are any follow-ups.

I am not sure, but I think I used this adapter on OpenBSD without the
need to install additional packages. Moxa Uport 1110 is also in
OpenBSD's usbdevs.h:
http://cvsweb.openbsd.org/cgi-bin/cvsweb/~checkout~/src/sys/dev/usb/usbdevs.h?rev=1.683=text/plain

Perhaps someone with much more knowledge than me would be able to port
this to FreeBSD?
-- 
Before enlightenment - chop wood, draw water.
After  enlightenment - chop wood, draw water.

Marko Cupać
https://www.mimar.rs/
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: moxa uport 1110 RS232 USB to serial support?

[Arrigo Marchiori via freebsd-stable]

Hello,

I am resending this reply message to the freebsd-usb@ and
freebsd-stable@ mailing list, because it bounced back to me after one
day.

On Thu, Nov 17, 2016 at 10:08:44AM +0100, Marko Cupać wrote:

> Hi,
> 
> is it possible to use Moxa Uport 1110 USB to serial adapter on FreeBSD
> 11.0?
> http://www.moxa.com/product/uport_1110.htm

I am afraid that the short answer is «no».

For what I could find on-line:

 - the Moxa UPort 1110 driver for Linux is the same as the Texas
   Instruments TUSB3410
   (source: 
https://git.kernel.org/cgit/linux/kernel/git/stable/linux-stable.git/commit/drivers/usb/serial?id=b923c6c62981cec5e2d2187fd700c2fc4386fc45)

 - the port comms/uticom was a driver for the TUSB3410, but it was
   deprecated, and removed three years ago.
   FreeBSD forum thread: https://forums.freebsd.org/threads/18151/
   Port information: http://www.freshports.org/comms/uticom
   SourceForge page: https://sourceforge.net/projects/uticom/

I hope this helps.
-- 
rigo

http://rigo.altervista.org
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

moxa uport 1110 RS232 USB to serial support?

[Marko Cupać]

Hi,

is it possible to use Moxa Uport 1110 USB to serial adapter on FreeBSD
11.0?
http://www.moxa.com/product/uport_1110.htm

Upon plugging in all I get in dmesg is:
ugen0.4:  at usbus0

No cuaUX devices appear in /dev.

Thank you in advance,
-- 
Before enlightenment - chop wood, draw water.
After  enlightenment - chop wood, draw water.

Marko Cupać
https://www.mimar.rs/
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: Problems with Dell external USB DVD drive

[Felix Johnson]

Hi Kevin,

The drive was plugged in when I used usbconfig.

When I plug the drive in, the drive makes a powering-up noise, as if it's
trying to align with a disk that may be inside it.
Unfortunately, there are no console messages. I've tried the USB 2 and USB
3 ports, with no change -
the device powers up but there is no console message.

Besides usbconfig, is there another command I can try to probe individual
USB ports?

Felix Johnson

On Sun, Nov 13, 2016 at 9:10 PM, Kevin Oberman <rkober...@gmail.com> wrote:

> On Sun, Nov 13, 2016 at 5:56 PM, Felix Johnson <felix.the@gmail.com>
> wrote:
>
>> Hello,
>>
>> I have a Dell Inspiron 7547, which lacks an internal CD/DVD drive.
>> I purchased a Dell DW514 external USB DVD drive, which works in Windows,
>> but can't be located in FreeBSD 11.0-p2. I am looking for help in getting
>> FreeBSD
>> to recognize the device.
>>
>> Any help is appreciated, since this is an important step to using this
>> laptop
>> full-time as a FreeBSD workstation.
>>
>> Here is the information I have on my system:
>>
>> [fjohnson@laptop /usr/home/fjohnson]$ uname -a
>> FreeBSD laptop 11.0-RELEASE-p2 FreeBSD 11.0-RELEASE-p2 #0: Mon Oct 24
>> 06:55:27 UTC 2016
>> r...@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC
>>  amd64
>>
>> [fjohnson@laptop /usr/home/fjohnson]$ sudo usbconfig
>> ugen0.1:  at usbus0, cfg=0 md=HOST spd=SUPER
>> (5.0Gbps) pwr=SAVE (0mA)
>> ugen1.1:  at usbus1, cfg=0 md=HOST spd=HIGH (480Mbps)
>> pwr=SAVE (0mA)
>> ugen0.2:  at usbus0, cfg=0 md=HOST spd=HIGH
>> (480Mbps) pwr=SAVE (100mA)
>> ugen1.2:  at usbus1, cfg=0 md=HOST spd=HIGH
>> (480Mbps) pwr=SAVE (0mA)
>> ugen0.3:  at usbus0, cfg=0 md=HOST spd=FULL
>> (12Mbps)
>> pwr=ON (98mA)
>> ugen0.4:  at usbus0, cfg=0 md=HOST spd=HIGH
>> (480Mbps) pwr=ON (450mA)
>> ugen0.5:  at usbus0, cfg=0 md=HOST spd=HIGH
>> (480Mbps) pwr=ON (500mA)
>> ugen0.6:  at usbus0, cfg=0 md=HOST spd=HIGH
>> (480Mbps) pwr=ON (500mA)
>> ugen0.7:  at usbus0, cfg=0 md=HOST spd=FULL (12Mbps)
>> pwr=ON (100mA)
>>
>> [...]
>>
>
>
>> Thank you!
>> Felix Johnson
>>
>
> Can I assume that the drive was plugged in when the usbconfig command was
> issued? I don't see any indication of it in the output. I was expecting a
> vendor/product that was not known to the system, but that does nto appear
> to be the case. the only two not identified have and the first in an Intel
> vendor ID and the second appears to be an Asix Ethernet controller, though
> the information on that is sketchy.
>
> When you plug in the drive, the console should show a message. A similar
> message should be sent when it is unplugged. Can you try that and report
> the message? It should include the vendor and product IDs.
> --
> Kevin Oberman, Part time kid herder and retired Network Engineer
> E-mail: rkober...@gmail.com
> PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683
>
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: Problems with Dell external USB DVD drive

[Kevin Oberman]

On Sun, Nov 13, 2016 at 5:56 PM, Felix Johnson <felix.the@gmail.com>
wrote:

> Hello,
>
> I have a Dell Inspiron 7547, which lacks an internal CD/DVD drive.
> I purchased a Dell DW514 external USB DVD drive, which works in Windows,
> but can't be located in FreeBSD 11.0-p2. I am looking for help in getting
> FreeBSD
> to recognize the device.
>
> Any help is appreciated, since this is an important step to using this
> laptop
> full-time as a FreeBSD workstation.
>
> Here is the information I have on my system:
>
> [fjohnson@laptop /usr/home/fjohnson]$ uname -a
> FreeBSD laptop 11.0-RELEASE-p2 FreeBSD 11.0-RELEASE-p2 #0: Mon Oct 24
> 06:55:27 UTC 2016
> r...@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC
>  amd64
>
> [fjohnson@laptop /usr/home/fjohnson]$ sudo usbconfig
> ugen0.1:  at usbus0, cfg=0 md=HOST spd=SUPER
> (5.0Gbps) pwr=SAVE (0mA)
> ugen1.1:  at usbus1, cfg=0 md=HOST spd=HIGH (480Mbps)
> pwr=SAVE (0mA)
> ugen0.2:  at usbus0, cfg=0 md=HOST spd=HIGH
> (480Mbps) pwr=SAVE (100mA)
> ugen1.2:  at usbus1, cfg=0 md=HOST spd=HIGH
> (480Mbps) pwr=SAVE (0mA)
> ugen0.3:  at usbus0, cfg=0 md=HOST spd=FULL (12Mbps)
> pwr=ON (98mA)
> ugen0.4:  at usbus0, cfg=0 md=HOST spd=HIGH
> (480Mbps) pwr=ON (450mA)
> ugen0.5:  at usbus0, cfg=0 md=HOST spd=HIGH
> (480Mbps) pwr=ON (500mA)
> ugen0.6:  at usbus0, cfg=0 md=HOST spd=HIGH
> (480Mbps) pwr=ON (500mA)
> ugen0.7:  at usbus0, cfg=0 md=HOST spd=FULL (12Mbps)
> pwr=ON (100mA)
>
> [...]
>


> Thank you!
> Felix Johnson
>

Can I assume that the drive was plugged in when the usbconfig command was
issued? I don't see any indication of it in the output. I was expecting a
vendor/product that was not known to the system, but that does nto appear
to be the case. the only two not identified have and the first in an Intel
vendor ID and the second appears to be an Asix Ethernet controller, though
the information on that is sketchy.

When you plug in the drive, the console should show a message. A similar
message should be sent when it is unplugged. Can you try that and report
the message? It should include the vendor and product IDs.
--
Kevin Oberman, Part time kid herder and retired Network Engineer
E-mail: rkober...@gmail.com
PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Problems with Dell external USB DVD drive

[Felix Johnson]

Hello,

I have a Dell Inspiron 7547, which lacks an internal CD/DVD drive.
I purchased a Dell DW514 external USB DVD drive, which works in Windows,
but can't be located in FreeBSD 11.0-p2. I am looking for help in getting
FreeBSD
to recognize the device.

Any help is appreciated, since this is an important step to using this
laptop
full-time as a FreeBSD workstation.

Here is the information I have on my system:

[fjohnson@laptop /usr/home/fjohnson]$ uname -a
FreeBSD laptop 11.0-RELEASE-p2 FreeBSD 11.0-RELEASE-p2 #0: Mon Oct 24
06:55:27 UTC 2016
r...@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC
 amd64

[fjohnson@laptop /usr/home/fjohnson]$ sudo usbconfig
ugen0.1:  at usbus0, cfg=0 md=HOST spd=SUPER
(5.0Gbps) pwr=SAVE (0mA)
ugen1.1:  at usbus1, cfg=0 md=HOST spd=HIGH (480Mbps)
pwr=SAVE (0mA)
ugen0.2:  at usbus0, cfg=0 md=HOST spd=HIGH
(480Mbps) pwr=SAVE (100mA)
ugen1.2:  at usbus1, cfg=0 md=HOST spd=HIGH
(480Mbps) pwr=SAVE (0mA)
ugen0.3:  at usbus0, cfg=0 md=HOST spd=FULL (12Mbps)
pwr=ON (98mA)
ugen0.4:  at usbus0, cfg=0 md=HOST spd=HIGH
(480Mbps) pwr=ON (450mA)
ugen0.5:  at usbus0, cfg=0 md=HOST spd=HIGH
(480Mbps) pwr=ON (500mA)
ugen0.6:  at usbus0, cfg=0 md=HOST spd=HIGH
(480Mbps) pwr=ON (500mA)
ugen0.7:  at usbus0, cfg=0 md=HOST spd=FULL (12Mbps)
pwr=ON (100mA)

[fjohnson@laptop /usr/home/fjohnson]$ dmesg | grep -i usb
xhci0:  mem 0xf7d0-0xf7d0
irq 16 at device 20.0 on pci0
usbus0 on xhci0
ehci0:  mem
0xf7d23000-0xf7d233ff irq 23 at device 29.0 on pci0
usbus1: EHCI version 1.0
usbus1 on ehci0
usbus0: 5.0Gbps Super Speed USB v3.0
usbus1: 480Mbps High Speed USB v2.0
ugen0.1: <0x8086> at usbus0
uhub0: <0x8086 XHCI root HUB, class 9/0, rev 3.00/1.00, addr 1> on usbus0
ugen1.1:  at usbus1
uhub1:  on usbus1
Root mount waiting for: usbus1 usbus0
Root mount waiting for: usbus1 usbus0
ugen0.2:  at usbus0
uhub2:  on
usbus0
ugen1.2:  at usbus1
uhub3:  on
usbus1
Root mount waiting for: usbus1 usbus0
ugen0.3:  at usbus0
ukbd0:  on usbus0
Root mount waiting for: usbus0
ugen0.4:  at usbus0
Root mount waiting for: usbus0
ugen0.5:  at usbus0
umass0:  on
usbus0
Root mount waiting for: usbus0
ugen0.6:  at usbus0
Root mount waiting for: usbus0
ugen0.7:  at usbus0
Root mount waiting for: usbus0
usb_alloc_device: set address 8 failed (USB_ERR_TIMEOUT, ignored)
Root mount waiting for: usbus0
usbd_setup_device_desc: getting device descriptor at addr 8 failed,
USB_ERR_TIMEOUT
Root mount waiting for: usbus0
usbd_req_re_enumerate: addr=8, set address failed! (USB_ERR_TIMEOUT,
ignored)
usbd_setup_device_desc: getting device descriptor at addr 8 failed,
USB_ERR_TIMEOUT
Root mount waiting for: usbus0
Root mount waiting for: usbus0
usbd_req_re_enumerate: addr=8, set address failed! (USB_ERR_TIMEOUT,
ignored)
Root mount waiting for: usbus0
usbd_setup_device_desc: getting device descriptor at addr 8 failed,
USB_ERR_TIMEOUT
Root mount waiting for: usbus0
usbd_req_re_enumerate: addr=8, set address failed! (USB_ERR_TIMEOUT,
ignored)
usbd_setup_device_desc: getting device descriptor at addr 8 failed,
USB_ERR_TIMEOUT
Root mount waiting for: usbus0
Root mount waiting for: usbus0
usbd_req_re_enumerate: addr=8, set address failed! (USB_ERR_TIMEOUT,
ignored)
usbd_setup_device_desc: getting device descriptor at addr 8 failed,
USB_ERR_TIMEOUT
ugen0.8:  at usbus0 (disconnected)
ums0:  on usbus0
uhid0:  on usbus0
uhid1:  on usbus0
axe0:  on usbus0
ue0:  on axe0
[fjohnson@laptop /usr/home/fjohnson]$

Thank you!
Felix Johnson
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

USB keyboard (wired) caps-lock takes for ever on 11-STABLE

[Aryeh Friedman]

After I did a wipe/reinstall going from 10.3 to 11 the same
machine/keyboard has gone from instantly registering the pressing of
caps-lock to causing a 2-3 second pause in keyboard i/o when pressing it
(on or off).

-- 
Aryeh M. Friedman, Lead Developer, http://www.PetiteCloud.org
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: Clandestine USB SD card slot

[George Mitchell]

On 10/17/16 11:02, George Mitchell wrote:
> [...]
> After setting hw.sdhci.debug=1 and hw.mmc.debug=1 in /etc/sysctl.conf
> and doing a verbose boot, then inserting and removing an SD card, all
> I get in "dmesg | egrep mmc\|sdhci" is:
> 
> sdhci_pci0:  mem 0xf0c6c000-0xf0c6c0ff irq 16 at device
> 20.7 on pci0
> sdhci_pci0: 1 slot(s) allocated
> sdhci_pci0:  mem 0xf0c6c000-0xf0c6c0ff irq 16 at device
> 20.7 on pci0
> sdhci_pci0-slot0: 50MHz 8bits 3.3V DMA
> sdhci_pci0-slot0: == REGISTER DUMP ==
> sdhci_pci0-slot0: Sys addr: 0x | Version:  0x1001
> sdhci_pci0-slot0: Blk size: 0x | Blk cnt:  0x
> sdhci_pci0-slot0: Argument: 0x | Trn mode: 0x
> sdhci_pci0-slot0: Present:  0x01f2 | Host ctl: 0x
> sdhci_pci0-slot0: Power:0x | Blk gap:  0x
> sdhci_pci0-slot0: Wake-up:  0x | Clock:0x
> sdhci_pci0-slot0: Timeout:  0x | Int stat: 0x
> sdhci_pci0-slot0: Int enab: 0x01ff00fb | Sig enab: 0x01ff00fb
> sdhci_pci0-slot0: AC12 err: 0x | Slot int: 0x00ff
> sdhci_pci0-slot0: Caps: 0x21de32b2 | Max curr: 0x00c80064
> sdhci_pci0-slot0: ===
> sdhci_pci0: 1 slot(s) allocated
> 
> (Same for "egrep mmc\|sdhci /var/log/messages".)
> 
> "pciconf -lv" suggests this is a:
> sdhci_pci0@pci0:0:20:7: class=0x080501 card=0x08651025 chip=0x78131022
> rev=0x01 hdr=0x00
> vendor = 'Advanced Micro Devices, Inc. [AMD]'
> device = 'FCH SD Flash Controller'
> class  = base peripheral
> subclass   = SD host controller
> 
> Are there some quirks I should define for this controller?  -- George
> 

For those coming in late:
FreeBSD 10.3-RELEASE-p7 #0: Thu Aug 11 18:38:15 UTC 2016 -- George
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"