search for: subr_bus

...v=0xc0d8f700, type=1, rid=0xc0d8f994, start=0, end=4294967295, count=1, flags=6) at bus_if.h:263 #8 0xc00b54e6 in csa_attach (dev=0xc0d8f700) at bus.h:376 #9 0xc0169ecf in device_attach (dev=0xc0d8f700) at device_if.h:178 #10 0xc016a9f0 in device_probe_and_attach (dev=0xc0d8f700) at ../../../kern/subr_bus.c:2369 #11 0xc016aad9 in bus_generic_attach (dev=0xc0e04b00) at ../../../kern/subr_bus.c:2907 #12 0xc00ae8bf in pci_attach (dev=0xc0e04b00) at ../../../dev/pci/pci.c:2611 #13 0xc0169ecf in device_attach (dev=0xc0e04b00) at device_if.h:178 #14 0xc016a9f0 in device_probe_and_attach (dev=0xc0e04b00) a...

....c 1.8.2.1.16.2 src/sys/netinet/ip_divert.c 1.42.2.6.6.1 src/sys/netinet/raw_ip.c 1.64.2.18.4.1 src/sys/netinet/udp_usrreq.c 1.64.2.19.4.1 RELENG_5 src/sys/kern/subr_bus.c 1.156.2.7 src/sys/kern/vfs_subr.c 1.522.2.5 src/sys/net/if_mib.c 1.13.4.2 src/sys/netinet/ip_divert.c 1.98.2.3 src/sys/netinet/raw_ip.c...

..._divert.c 1.42.2.6.6.1 src/sys/netinet/raw_ip.c 1.64.2.18.4.1 src/sys/netinet/tcp_subr.c 1.73.2.33.2.1 src/sys/netinet/udp_usrreq.c 1.64.2.19.4.1 RELENG_5 src/sys/kern/subr_bus.c 1.156.2.7 src/sys/kern/uipc_usrreq.c 1.138.2.14 src/sys/kern/vfs_subr.c 1.522.2.5 src/sys/net/if_mib.c 1.13.4.2 src/sys/netinet/ip_divert...

..._divert.c 1.42.2.6.6.1 src/sys/netinet/raw_ip.c 1.64.2.18.4.1 src/sys/netinet/tcp_subr.c 1.73.2.33.2.1 src/sys/netinet/udp_usrreq.c 1.64.2.19.4.1 RELENG_5 src/sys/kern/subr_bus.c 1.156.2.7 src/sys/kern/uipc_usrreq.c 1.138.2.14 src/sys/kern/vfs_subr.c 1.522.2.5 src/sys/net/if_mib.c 1.13.4.2 src/sys/netinet/ip_divert...

....c 1.8.2.1.16.2 src/sys/netinet/ip_divert.c 1.42.2.6.6.1 src/sys/netinet/raw_ip.c 1.64.2.18.4.1 src/sys/netinet/udp_usrreq.c 1.64.2.19.4.1 RELENG_5 src/sys/kern/subr_bus.c 1.156.2.7 src/sys/kern/vfs_subr.c 1.522.2.5 src/sys/net/if_mib.c 1.13.4.2 src/sys/netinet/ip_divert.c 1.98.2.3 src/sys/netinet/raw_ip.c...

...(frame=0xfcb0aa7c, usermode=0, eva=40) at /usr/src/sys/i386/i386/trap.c:852 #5 0xc06d08a6 in trap (frame=0xfcb0aa7c) at /usr/src/sys/i386/i386/trap.c:530 #6 0xc06b5b1b in calltrap () at /usr/src/sys/i386/i386/exception.s:159 #7 0xc055b69c in device_attach (dev=0xcc58e480) at /usr/src/sys/kern/subr_bus.c:279 #8 0xc055c96d in device_probe_and_attach (dev=0xcc58e480) at /usr/src/sys/kern/subr_bus.c:2366 #9 0xc055ca59 in bus_generic_attach (dev=0xc5167100) at /usr/src/sys/kern/subr_bus.c:2905 #10 0xc04796f0 in ata_identify (dev=0xc5167100) at /usr/src/sys/dev/ata/ata-all.c:723 #11 0xc0479fe4 in...

Hi. I experimented a bit with collecting entropy from the time it takes for device_attach() to run (in CPU cycles). It seems that those times have enough variation that we can use it for entropy harvesting. It happens even before root is mounted, so pretty early. On the machine I'm testing it, which has minimal kernel plus NIC driver I see 75 device_attach() calls. I'm being very careful

I'm trying to make devd run an stty command whenever a USB serial device is attached. Unfortunately, $device-name is ucom[0-9] and the device names are /dev/cuaU[0-9] - how do I get the correct name in the device action? I haven't found a way to extract the number by itself, so I'm stuck with specifying a separate rule for each number, like so: attach 100 { device-name