Re: what do jails map 127.0.0.1 to?

2019-02-12 Thread Rodney W. Grimes
[ Charset windows-1252 unsupported, converting... ]
> Bjoern A. Zeeb wrote:
> [good stuff snipped]
> >Yes, could do easily but wouldn?t work for my above case, would it?  I
> >can help you with the code for v4 and jails if you help me with the code
> >for IPv6?
> Well, not quite what you volunteered to do, but can you fill in the INET6 code
> for this code snippet? (It does what Alan suggested for INET.)
> 
> 
>   /*
>* Find out what IP# localhost maps to and whether or not use of
>* INET6 is required.  Jails will map 127.0.0.1 to another INET
>* address.
>*/
>   use_inet6 = 0;
>   s = socket(PF_INET, SOCK_DGRAM, 0);
>   if (s < 0) {
>   use_inet6 = 1;
>   s = socket(PF_INET6, SOCK_DGRAM, 0);
>   }
>   if (s < 0)
>   err(1, "Can't create a inet/inet6 socket");
>   if (use_inet6 != 0) {
>   ;   /* Needs code... */
>   } else {
>   memset(, 0, sizeof(sad));
>   sad.sin_len = sizeof(sad);
>   sad.sin_family = AF_INET;
>   sad.sin_addr.s_addr = inet_addr("127.0.0.1");
>   sad.sin_port = 0;
>   ret = bind(s, (struct sockaddr *), sizeof(sad));
>   if (ret > 0)
>   err(1, "Can't bind 127.0.0.1");
>   memset(, 0, sizeof(sad));
>   slen = sizeof(sad);
>   ret = getsockname(s, (struct sockaddr *), );
>   if (ret < 0)
>   err(1, "Can't get bound sockaddr");
>   printf("locaddr: %s\n", inet_ntoa(sad.sin_addr));
>   }
> 
> If the IPv4 code isn't sufficient, please let me know. (I think I know how to 
> make
> the RPC code use IPv6, but I need to know what IPv6 address to use. I get 
> confused
> by link local/site local/? It needs to be an address that is "this machine".

ipv4 127.0.0.1 == ipv6 ::1, see /etc/hosts

> 
> Thanks for your help with this, rick
> ___
> freebsd-current@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-current
> To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
> 
> 

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


Re: what do jails map 127.0.0.1 to?

2019-02-12 Thread Rick Macklem
Bjoern A. Zeeb wrote:
[good stuff snipped]
>Yes, could do easily but wouldn’t work for my above case, would it?  I
>can help you with the code for v4 and jails if you help me with the code
>for IPv6?
Well, not quite what you volunteered to do, but can you fill in the INET6 code
for this code snippet? (It does what Alan suggested for INET.)


/*
 * Find out what IP# localhost maps to and whether or not use of
 * INET6 is required.  Jails will map 127.0.0.1 to another INET
 * address.
 */
use_inet6 = 0;
s = socket(PF_INET, SOCK_DGRAM, 0);
if (s < 0) {
use_inet6 = 1;
s = socket(PF_INET6, SOCK_DGRAM, 0);
}
if (s < 0)
err(1, "Can't create a inet/inet6 socket");
if (use_inet6 != 0) {
;   /* Needs code... */
} else {
memset(, 0, sizeof(sad));
sad.sin_len = sizeof(sad);
sad.sin_family = AF_INET;
sad.sin_addr.s_addr = inet_addr("127.0.0.1");
sad.sin_port = 0;
ret = bind(s, (struct sockaddr *), sizeof(sad));
if (ret > 0)
err(1, "Can't bind 127.0.0.1");
memset(, 0, sizeof(sad));
slen = sizeof(sad);
ret = getsockname(s, (struct sockaddr *), );
if (ret < 0)
err(1, "Can't get bound sockaddr");
printf("locaddr: %s\n", inet_ntoa(sad.sin_addr));
}

If the IPv4 code isn't sufficient, please let me know. (I think I know how to 
make
the RPC code use IPv6, but I need to know what IPv6 address to use. I get 
confused
by link local/site local/… It needs to be an address that is "this machine".

Thanks for your help with this, rick
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"


Re: Networking panic on 12 - found the cause

2019-02-12 Thread Pete French

Thanks guys! That was fast

On 12/02/2019 20:13, Kristof Provost wrote:

On 2019-02-12 13:54:21 (-0600), Eric van Gyzen  wrote:
 > I see the same behavior on head (and stable/12).
 >
 > (kgdb) f
 > #16 0x80ce5331 in ether_output_frame (ifp=0xf80003672800,
 > m=0xf8000c88b100) at /usr/src/sys/net/if_ethersubr.c:468
 > 468 switch (pfil_run_hooks(V_link_pfil_head, , ifp, PFIL_OUT,
 >
 > 0x80ce5321 <+81>: mov %gs:0x0,%rax
 > 0x80ce532a <+90>: mov 0x500(%rax),%rax
 > => 0x80ce5331 <+97>: mov 0x28(%rax),%rax
 >
 > I think this is part of the V_link_pfil_head. I'm not very familiar
 > with vnet. Does this need a CURVNET_SET(), maybe in garp_rexmit()?
 >
Yes. I posted a proposed patch in
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=235699 


Basically we get called through a timer, so there's no vnet context. It
needs to be set, and then we can safely use any V_ variables.

Regards,
Kristof

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


Re: what do jails map 127.0.0.1 to?

2019-02-12 Thread Rick Macklem
Bjoern A. Zeeb wrote:
>On 11 Feb 2019, at 0:50, Rick Macklem wrote:
>> I am finally back to looking at an old PR#205193.
>>
>> The problem is that the nfsuserd daemon expects upcalls from the
>> kernel
>> that are from localhost (127.0.0.1) and when jails are running on the
>> system,
>> 127.0.0.1 is mapped to some other IP#. (I think it might be the
>> address of the
>> first net interface on the machine, but I'm not sure?)
>
>And what does it do on system that have no 127.1 or no IPv4 at all
>anymore or don’t even support IPv4 anymore?
It doesn't work. It uses UDP over IPv4 for the upcalls.

>> Is there a way that nfsuserd.c can find out what this IP# is?
>
>Yes, could do easily but wouldn’t work for my above case, would it?  I
>can help you with the code for v4 and jails if you help me with the code
>for IPv6?
I suspect the main trick is how it can figure out that it needs to use IPv6 
instead of
IPv4? (If there is no easy way, I suppose it could be a command option.)

rick
ps: The kernel RPC knows what it calls "udp6". I never really understood how to
  tell when an IPv6 address is from the local machine? (I'll admit I never 
use
  IPv6, so I don't even know if NFS works on it. I just assume someone would
  complain if it didn't work.)
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"


Re: drm2 removed?

2019-02-12 Thread Steve Kargl
On Mon, Feb 11, 2019 at 08:20:20AM -0800, Steve Kargl wrote:
> On Mon, Feb 11, 2019 at 08:12:05AM -0800, Steve Kargl wrote:
> > Anyone have any idea which recent change broke the
> > drm-legacy-kmod port.  This is why I raised an issue
> > with removal of drm2 from src/sys.  How is suppose
> > to be fixed?
> > 
> 
> It was r343567.  The merging of PAE and NO PAE pmap.h
> by kib removed all of the missing macros. :(  
> 

Waed the white flag.

svn merge -r HEAD:343565 .

fixes the problem. :-)

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


Re: Networking panic on 12 - found the cause

2019-02-12 Thread Kristof Provost
On 2019-02-12 13:54:21 (-0600), Eric van Gyzen  wrote:
> I see the same behavior on head (and stable/12).
> 
> (kgdb) f
> #16 0x80ce5331 in ether_output_frame (ifp=0xf80003672800,
> m=0xf8000c88b100) at /usr/src/sys/net/if_ethersubr.c:468
> 468   switch (pfil_run_hooks(V_link_pfil_head, , ifp, 
> PFIL_OUT,
> 
>0x80ce5321 <+81>:  mov%gs:0x0,%rax
>0x80ce532a <+90>:  mov0x500(%rax),%rax
> => 0x80ce5331 <+97>:  mov0x28(%rax),%rax
> 
> I think this is part of the V_link_pfil_head.  I'm not very familiar
> with vnet.  Does this need a CURVNET_SET(), maybe in garp_rexmit()?
> 
Yes. I posted a proposed patch in
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=235699

Basically we get called through a timer, so there's no vnet context. It
needs to be set, and then we can safely use any V_ variables.

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


Re: Networking panic on 12 - found the cause

2019-02-12 Thread Eric van Gyzen
On 2/12/19 8:53 AM, Pete French wrote:
> I found my panic. If I take everything out of rc.conf and loader.conf
> and sysctl.conf and boot the system it works fine when I add an IP
> address. If I add this one line to sysctl.conf
> 
> net.link.ether.inet.garp_rexmit_count=2
> 
> Then I get a panic when I configure the interface:
> 
> root@serpentine-passive:~ #  ifconfig igb0 inet 10.32.10.4/16 up
> 
> 
> Fatal trap 12: page fault while in kernel mode
> cpuid = 0; apic id = 00
> fault virtual address   = 0x28
> fault code  = supervisor read data, page not present
> instruction pointer = 0x20:0x80c987f1
> stack pointer   = 0x28:0xfe4d5730
> frame pointer   = 0x28:0xfe4d5750
> code segment    = base 0x0, limit 0xf, type 0x1b
>     = DPL 0, pres 1, long 1, def32 0, gran 1
> processor eflags    = interrupt enabled, resume, IOPL = 0
> current process = 12 (swi4: clock (0))
> trap number = 12
> panic: page fault
> cpuid = 0
> time = 1549981620
> KDB: stack backtrace:
> #0 0x80bdfdc7 at kdb_backtrace+0x67
> #1 0x80b93fa3 at vpanic+0x1a3
> #2 0x80b93df3 at panic+0x43
> #3 0x8106a7bf at trap_fatal+0x35f
> #4 0x8106a819 at trap_pfault+0x49
> #5 0x81069e3e at trap+0x29e
> #6 0x810450c5 at calltrap+0x8
> #7 0x80c986f6 at ether_output+0x6b6
> #8 0x80d03354 at arprequest+0x4c4
> #9 0x80d0515c at garp_rexmit+0xbc
> #10 0x80bade19 at softclock_call_cc+0x129
> #11 0x80bae2f9 at softclock+0x79
> #12 0x80b57c57 at ithread_loop+0x1a7
> #13 0x80b54da2 at fork_exit+0x82
> #14 0x810460be at fork_trampoline+0xe

I see the same behavior on head (and stable/12).

(kgdb) f
#16 0x80ce5331 in ether_output_frame (ifp=0xf80003672800,
m=0xf8000c88b100) at /usr/src/sys/net/if_ethersubr.c:468
468 switch (pfil_run_hooks(V_link_pfil_head, , ifp, 
PFIL_OUT,

   0x80ce5321 <+81>:mov%gs:0x0,%rax
   0x80ce532a <+90>:mov0x500(%rax),%rax
=> 0x80ce5331 <+97>:mov0x28(%rax),%rax

I think this is part of the V_link_pfil_head.  I'm not very familiar
with vnet.  Does this need a CURVNET_SET(), maybe in garp_rexmit()?

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


Re: USB problems on -CURRENT (controller keeps getting reset)

2019-02-12 Thread Rebecca Cran
That works, thanks. 

Rebecca 

On February 12, 2019 at 1:24:15 AM, Hans Petter Selasky 
(h...@selasky.org(mailto:h...@selasky.org)) wrote:

> The USB timeout error might indicate an IRQ issue.
> 
> Can you try setting:
> 
> hw.usb.xhci.use_polling=1
> 
> In /boot/loader.conf and reboot.
> 
> --HPS
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"


Re: what do jails map 127.0.0.1 to?

2019-02-12 Thread Bjoern A. Zeeb

On 11 Feb 2019, at 0:50, Rick Macklem wrote:


I am finally back to looking at an old PR#205193.

The problem is that the nfsuserd daemon expects upcalls from the 
kernel
that are from localhost (127.0.0.1) and when jails are running on the 
system,
127.0.0.1 is mapped to some other IP#. (I think it might be the 
address of the

first net interface on the machine, but I'm not sure?)


And what does it do on system that have no 127.1 or no IPv4 at all 
anymore or don’t even support IPv4 anymore?




Is there a way that nfsuserd.c can find out what this IP# is?


Yes, could do easily but wouldn’t work for my above case, would it?  I 
can help you with the code for v4 and jails if you help me with the code 
for IPv6?



(I have a patch that converts nfsuserd.c to using an AF_LOCAL socket, 
but that
 breaks for some setups. I think it was when the directory the socket 
was being
 created in is NFSv4 mounted, but I can't remember exactly how it 
fails.)


Thanks for any help with this, rick
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to 
"freebsd-current-unsubscr...@freebsd.org"

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


Re: what do jails map 127.0.0.1 to?

2019-02-12 Thread Allan Jude
On 2019-02-10 19:50, Rick Macklem wrote:
> I am finally back to looking at an old PR#205193.
> 
> The problem is that the nfsuserd daemon expects upcalls from the kernel
> that are from localhost (127.0.0.1) and when jails are running on the system,
> 127.0.0.1 is mapped to some other IP#. (I think it might be the address of the
> first net interface on the machine, but I'm not sure?)
> 
> Is there a way that nfsuserd.c can find out what this IP# is?
> (I have a patch that converts nfsuserd.c to using an AF_LOCAL socket, but that
>  breaks for some setups. I think it was when the directory the socket was 
> being
>  created in is NFSv4 mounted, but I can't remember exactly how it fails.)
> 
> Thanks for any help with this, rick
> ___
> freebsd-current@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-current
> To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
> 

normal Jails map 127.0.0.1 to the first IP in the jail.

-- 
Allan Jude



signature.asc
Description: OpenPGP digital signature


Re: "Oddness" in head since around r343678 or so

2019-02-12 Thread Niclas Zeising

On 2/12/19 1:38 PM, David Wolfskill wrote:

On Thu, Feb 07, 2019 at 05:09:40AM -0800, David Wolfskill wrote:

...
The laptop is configured to run xdm; while running stable/11 or
stable/12, there's a period of about 5 seconds after xdm's login banner
shows up before either the mouse or keyboard responds.

Up to a few days ago, head was the same, but as of about last weekend (I
think), that period is about 40 seconds while running head.



I no longer observe the above-described delay in head, as of r343998.



Most likely because the coverage stuff were removed from GENERIC.
Regards
--
Nicals
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"


Re: IPv6 RFC3041 temporary address broken?

2019-02-12 Thread Renato Botelho
On 12/02/19 11:03, Shawn Webb wrote:
> Hey all,
> 
> I have net.inet6.ip6.use_tempaddr and net.inet6.ip6.prefer_tempaddr
> both set to 1. Yet, I'm not seeing temporary addresses created upon
> receipt of a router advertisement. I'm only seeing the HostID-based
> SLAAC IP be generated. Has something changed recently that would
> prevent RFC3041 from working in FreeBSD HEAD?
> 
> Thanks,
> 

It's working as expected here:

lagg0: flags=8843 metric 0 mtu 1500
ether 3c:97:0e:48:3f:f8
inet6 fe80::3e97:eff:fe48:3ff8%lagg0 prefixlen 64 scopeid 0x4
inet6 2804:f1c:800:e00:3e97:eff:fe48:3ff8 prefixlen 64 autoconf
inet6 2804:f1c:800:e00:30e9:88ac:84fc:ebea prefixlen 64 autoconf 
temporary
inet 172.21.4.121 netmask 0xff00 broadcast 172.21.4.255
laggproto failover lagghash l2,l3,l4
laggport: em0 flags=1
laggport: wlan0 flags=4
groups: lagg
media: Ethernet autoselect
status: active
nd6 options=23

❯ uname -a
FreeBSD x230 13.0-CURRENT FreeBSD 13.0-CURRENT #83 r344002: Mon Feb 11
11:54:18 -02 2019
root@x230:/usr/obj/usr/src/amd64.amd64/sys/GENERIC-NODEBUG  amd64

-- 
Renato Botelho



signature.asc
Description: OpenPGP digital signature


Re: IPv6 RFC3041 temporary address broken?

2019-02-12 Thread Shawn Webb
On Tue, Feb 12, 2019 at 11:44:42AM -0200, Renato Botelho wrote:
> On 12/02/19 11:03, Shawn Webb wrote:
> > Hey all,
> > 
> > I have net.inet6.ip6.use_tempaddr and net.inet6.ip6.prefer_tempaddr
> > both set to 1. Yet, I'm not seeing temporary addresses created upon
> > receipt of a router advertisement. I'm only seeing the HostID-based
> > SLAAC IP be generated. Has something changed recently that would
> > prevent RFC3041 from working in FreeBSD HEAD?
> > 
> > Thanks,
> > 
> 
> It's working as expected here:
> 
> lagg0: flags=8843 metric 0 mtu 1500
>   ether 3c:97:0e:48:3f:f8
>   inet6 fe80::3e97:eff:fe48:3ff8%lagg0 prefixlen 64 scopeid 0x4
>   inet6 2804:f1c:800:e00:3e97:eff:fe48:3ff8 prefixlen 64 autoconf
>   inet6 2804:f1c:800:e00:30e9:88ac:84fc:ebea prefixlen 64 autoconf 
> temporary
>   inet 172.21.4.121 netmask 0xff00 broadcast 172.21.4.255
>   laggproto failover lagghash l2,l3,l4
>   laggport: em0 flags=1
>   laggport: wlan0 flags=4
>   groups: lagg
>   media: Ethernet autoselect
>   status: active
>   nd6 options=23
> 
> ??? uname -a
> FreeBSD x230 13.0-CURRENT FreeBSD 13.0-CURRENT #83 r344002: Mon Feb 11
> 11:54:18 -02 2019
> root@x230:/usr/obj/usr/src/amd64.amd64/sys/GENERIC-NODEBUG  amd64

False alarm. Glitch in the matrix. I had a typo in a config file.
Sorry for the noise and thanks for the quick response!

Thanks,

-- 
Shawn Webb
Cofounder and Security Engineer
HardenedBSD

Tor-ified Signal:+1 443-546-8752
Tor+XMPP+OTR:latt...@is.a.hacker.sx
GPG Key ID:  0x6A84658F52456EEE
GPG Key Fingerprint: 2ABA B6BD EF6A F486 BE89  3D9E 6A84 658F 5245 6EEE


signature.asc
Description: PGP signature


IPv6 RFC3041 temporary address broken?

2019-02-12 Thread Shawn Webb
Hey all,

I have net.inet6.ip6.use_tempaddr and net.inet6.ip6.prefer_tempaddr
both set to 1. Yet, I'm not seeing temporary addresses created upon
receipt of a router advertisement. I'm only seeing the HostID-based
SLAAC IP be generated. Has something changed recently that would
prevent RFC3041 from working in FreeBSD HEAD?

Thanks,

-- 
Shawn Webb
Cofounder and Security Engineer
HardenedBSD

Tor-ified Signal:+1 443-546-8752
Tor+XMPP+OTR:latt...@is.a.hacker.sx
GPG Key ID:  0x6A84658F52456EEE
GPG Key Fingerprint: 2ABA B6BD EF6A F486 BE89  3D9E 6A84 658F 5245 6EEE


signature.asc
Description: PGP signature


Re: "Oddness" in head since around r343678 or so

2019-02-12 Thread David Wolfskill
On Thu, Feb 07, 2019 at 05:09:40AM -0800, David Wolfskill wrote:
> ...
> The laptop is configured to run xdm; while running stable/11 or
> stable/12, there's a period of about 5 seconds after xdm's login banner
> shows up before either the mouse or keyboard responds.
> 
> Up to a few days ago, head was the same, but as of about last weekend (I
> think), that period is about 40 seconds while running head.
> 

I no longer observe the above-described delay in head, as of r343998.

Peace,
david
-- 
David H. Wolfskill  da...@catwhisker.org
Westboro Baptist "Church" appears to delight in taking the name of God in vain.

See http://www.catwhisker.org/~david/publickey.gpg for my public key.


signature.asc
Description: PGP signature


Re: USB problems on -CURRENT (controller keeps getting reset)

2019-02-12 Thread Hans Petter Selasky

The USB timeout error might indicate an IRQ issue.

Can you try setting:

hw.usb.xhci.use_polling=1

In /boot/loader.conf and reboot.

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


USB problems on -CURRENT (controller keeps getting reset)

2019-02-12 Thread Rebecca Cran

I’m having problems with USB devices on -CURRENT on my ThreadRipper system. The 
controller keeps on getting reset. I thought it might be related to my iogear 
KVM, but disconnecting it doesn’t help.

Feb 12 00:59:47 photon kernel: xhci0: Resetting controller
Feb 12 00:59:47 photon kernel: usb_alloc_device: set address 2 failed 
(USB_ERR_TIMEOUT, ignored)
Feb 12 00:59:49 photon kernel: usbd_setup_device_desc: getting device 
descriptor at addr 2 failed, USB_ERR_TIMEOUT
Feb 12 00:59:51 photon kernel: usbd_req_re_enumerate: addr=2, set address 
failed! (USB_ERR_TIMEOUT, ignored)
Feb 12 00:59:52 photon kernel: usbd_setup_device_desc: getting device 
descriptor at addr 2 failed, USB_ERR_TIMEOUT
Feb 12 00:59:54 photon kernel: usbd_req_re_enumerate: addr=2, set address 
failed! (USB_ERR_TIMEOUT, ignored)
Feb 12 00:59:56 photon kernel: usbd_setup_device_desc: getting device 
descriptor at addr 2 failed, USB_ERR_TIMEOUT
Feb 12 00:59:57 photon kernel: usbd_req_re_enumerate: addr=2, set address 
failed! (USB_ERR_TIMEOUT, ignored)
Feb 12 00:59:59 photon kernel: usbd_setup_device_desc: getting device 
descriptor at addr 2 failed, USB_ERR_TIMEOUT
Feb 12 01:00:01 photon kernel: usbd_req_re_enumerate: addr=2, set address 
failed! (USB_ERR_TIMEOUT, ignored)
Feb 12 01:00:02 photon kernel: usbd_setup_device_desc: getting device 
descriptor at addr 2 failed, USB_ERR_TIMEOUT
Feb 12 01:00:02 photon kernel: ugen0.2:  at usbus0 (disconnected)
Feb 12 01:00:03 photon kernel: uhub_reattach_port: could not allocate new device
Feb 12 01:00:04 photon kernel: usb_alloc_device: device init 2 failed 
(USB_ERR_TIMEOUT, ignored)
Feb 12 01:00:04 photon kernel: ugen0.2:  at usbus0 (disconnected)
Feb 12 01:00:04 photon kernel: uhub_reattach_port: could not allocate new device
Feb 12 01:00:05 photon kernel: usb_alloc_device: device init 2 failed 
(USB_ERR_TIMEOUT, ignored)
Feb 12 01:00:05 photon kernel: ugen0.2:  at usbus0 (disconnected)
Feb 12 01:00:05 photon kernel: uhub_reattach_port: could not allocate new device
Feb 12 01:00:05 photon kernel: uhub0: at usbus0, port 1, addr 1 (disconnected)
Feb 12 01:00:05 photon kernel: uhub0: <0x1022 XHCI root HUB, class 9/0, rev 
3.00/1.00, addr 1> on usbus0
Feb 12 01:00:06 photon kernel: uhub0: 22 ports with 22 removable, self powered
Feb 12 01:00:08 photon kernel: xhci0: Resetting controller
Feb 12 01:00:08 photon kernel: usb_alloc_device: set address 2 failed 
(USB_ERR_TIMEOUT, ignored)
Feb 12 01:00:09 photon kernel: usbd_setup_device_desc: getting device 
descriptor at addr 2 failed, USB_ERR_TIMEOUT
Feb 12 01:00:11 photon kernel: usbd_req_re_enumerate: addr=2, set address 
failed! (USB_ERR_TIMEOUT, ignored)
Feb 12 01:00:13 photon kernel: usbd_setup_device_desc: getting device 
descriptor at addr 2 failed, USB_ERR_TIMEOUT
Feb 12 01:00:15 photon kernel: usbd_req_re_enumerate: addr=2, set address 
failed! (USB_ERR_TIMEOUT, ignored)
Feb 12 01:00:16 photon kernel: usbd_setup_device_desc: getting device 
descriptor at addr 2 failed, USB_ERR_TIMEOUT
Feb 12 01:00:18 photon kernel: usbd_req_re_enumerate: addr=2, set address 
failed! (USB_ERR_TIMEOUT, ignored)
Feb 12 01:00:19 photon kernel: usbd_setup_device_desc: getting device 
descriptor at addr 2 failed, USB_ERR_TIMEOUT
Feb 12 01:00:21 photon kernel: usbd_req_re_enumerate: addr=2, set address 
failed! (USB_ERR_TIMEOUT, ignored)
Feb 12 01:00:23 photon kernel: usbd_setup_device_desc: getting device 
descriptor at addr 2 failed, USB_ERR_TIMEOUT
Feb 12 01:00:23 photon kernel: ugen0.2:  at usbus0 (disconnected)
Feb 12 01:00:23 photon kernel: uhub_reattach_port: could not allocate new device
Feb 12 01:00:24 photon kernel: usb_alloc_device: device init 2 failed 
(USB_ERR_TIMEOUT, ignored)
Feb 12 01:00:24 photon kernel: ugen0.2:  at usbus0 (disconnected)
Feb 12 01:00:24 photon kernel: uhub_reattach_port: could not allocate new device
Feb 12 01:00:25 photon kernel: usb_alloc_device: device init 2 failed 
(USB_ERR_TIMEOUT, ignored)
Feb 12 01:00:25 photon kernel: ugen0.2:  at usbus0 (disconnected)
Feb 12 01:00:25 photon kernel: uhub_reattach_port: could not allocate new device
Feb 12 01:00:25 photon kernel: uhub0: at usbus0, port 1, addr 1 (disconnected)
Feb 12 01:00:25 photon kernel: uhub0: <0x1022 XHCI root HUB, class 9/0, rev 
3.00/1.00, addr 1> on usbus0
Feb 12 01:00:26 photon kernel: uhub0: 22 ports with 22 removable, self powered
Feb 12 01:00:28 photon kernel: xhci0: Resetting controller

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