search for: device_attach

...at device 26.0 on pci0 ioapic0: routing intpin 23 (PCI IRQ 23) to lapic 0 vector 66 usbus0: EHCI version 1.0 usbus0 on ehci0 pcib7: <ACPI PCI-PCI bridge> at device 28.0 on pci0 pcib7: domain 0 pcib7: secondary bus 7 pcib7: subordinate bus 7 pcib7: no prefetched decode device_attach: pcib7 attach returned 6 pcib7: <ACPI PCI-PCI bridge> irq 19 at device 28.7 on pci0 panic: Bad tailq NEXT(0xffffffff80e52660->tqh_last) != NULL cpuid = 0 KDB: stack backtrace: db_trace_self_wrapper() at db_trace_self_wrapper+0x2a kdb_backtrace() at kdb_backtrace+0x37 panic() at panic+0x1d8...

..._data_load_cbfn() at tws_dmamap_data_load_cbfn+0xb7 bus_dmamap_load() at bus_dmamap_load+0x16c tws_map_request() at tws_map_request+0x78 tws_get_param() at tws_get_param+0xe1 tws_display_ctlr_info() at tws_display_ctlr_info+0x4c tws_init_ctlr() at tws_init_ctlr+0x6d tws_attach() at tws_attach+0x68c device_attach() at device_attach+0x72 bus_generic_attach() at bus_generic_attach+0x1a acpi_pci_attach() at acpi_pci_attach+0x164 device_attach() at device_attach+0x72 bus_generic_attach() at bus_generic_attach+0x1a acpi_pcib_attach() at acpi_pcib_attach+0x1a7 acpi_pcib_pci_attach() at acpi_pcib_pci_attach+0x9b d...

...wake_sysctl_walk() at acpi_wake_sysctl_walk+0x74 acpi_wake_sysctl_walk() at acpi_wake_sysctl_walk+0x74 acpi_wake_sysctl_walk() at acpi_wake_sysctl_walk+0x74 acpi_wake_sysctl_walk() at acpi_wake_sysctl_walk+0x74 acpi_wake_sysctl_walk() at acpi_wake_sysctl_walk+0x74 acpi_attach() at acpi_attach+0x984 device_attach() at device_attach+0x69 bus_generic_attach() at bus_generic_attach+0x1a nexus_attach() at nexus_attach+0x19 device_attach() at device_attach+0x69 root_bus_configure() at root_bus_configure+0x28 configure() at configure+0xa mi_startup() at mi_startup+0x59 btext() at btext+0x2c Fatal trap 9: gener...

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 ve...

...;ACPI PCI bus> on pcib6 Dec 2 17:37:21 nas kernel: re0: <RealTek 8168/8111B PCIe Gigabit Ethernet> port 0xc800-0xc8ff mem 0xfe5ff000-0xfe5fffff,0xfdef 0000-0xfdefffff irq 16 at device 0.0 on pci3 Dec 2 17:37:21 nas kernel: re0: Unknown H/W revision: 3c400000 Dec 2 17:37:21 nas kernel: device_attach: re0 attach returned 6 Dec 2 17:37:21 nas kernel: pcib7: <ACPI PCI-PCI bridge> irq 18 at device 28.5 on pci0 Dec 2 17:37:21 nas kernel: pci2: <ACPI PCI bus> on pcib7 Dec 2 17:37:21 nas kernel: re1: <RealTek 8168/8111B PCIe Gigabit Ethernet> port 0xb800-0xb8ff mem 0xfe4ff000...

...io dma-bufs > + */ > +int virtio_dma_buf_attach(struct dma_buf *dma_buf, > + struct dma_buf_attachment *attach) > +{ > + int ret; > + const struct virtio_dma_buf_ops *ops = container_of( > + dma_buf->ops, const struct virtio_dma_buf_ops, ops); > + > + if (ops->device_attach) { > + ret = ops->device_attach(dma_buf, attach); > + if (ret) > + return ret; > + } > + return 0; > +} > +EXPORT_SYMBOL(virtio_dma_buf_attach); > + > +/** > + * is_virtio_dma_buf - returns true if the given dma-buf is a virtio dma-buf > + * @dma_buf: buffer...

...io dma-bufs > + */ > +int virtio_dma_buf_attach(struct dma_buf *dma_buf, > + struct dma_buf_attachment *attach) > +{ > + int ret; > + const struct virtio_dma_buf_ops *ops = container_of( > + dma_buf->ops, const struct virtio_dma_buf_ops, ops); > + > + if (ops->device_attach) { > + ret = ops->device_attach(dma_buf, attach); > + if (ret) > + return ret; > + } > + return 0; > +} > +EXPORT_SYMBOL(virtio_dma_buf_attach); > + > +/** > + * is_virtio_dma_buf - returns true if the given dma-buf is a virtio dma-buf > + * @dma_buf: buffer...

...d8f994, start=0, end=4294967295, count=1, flags=6) at ../../../dev/pci/pci.c:3488 #7 0xc016ad1c in bus_alloc_resource (dev=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 0xc...

...> + */ > +int virtio_dma_buf_attach(struct dma_buf *dma_buf, > + struct dma_buf_attachment *attach) > +{ > + int ret; > + const struct virtio_dma_buf_ops *ops = > + container_of(dma_buf->ops, > + const struct virtio_dma_buf_ops, ops); > + > + if (ops->device_attach) { > + ret = ops->device_attach(dma_buf, attach); > + if (ret) > + return ret; > + } > + return 0; > +} > +EXPORT_SYMBOL(virtio_dma_buf_attach); > + > +/** > + * is_virtio_dma_buf - returns true if the given dma-buf is a virtio dma-buf > + * @dma_buf: buffer...

...neric ISA VGA> at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 ppc0: cannot reserve I/O port range ctl: CAM Target Layer loaded est0: <Enhanced SpeedStep Frequency Control> on cpu0 est: CPU supports Enhanced Speedstep, but is not recognized. est: cpu_vendor GenuineIntel, msr 23b500001b00 device_attach: est0 attach returned 6 p4tcc0: <CPU Frequency Thermal Control> on cpu0 est1: <Enhanced SpeedStep Frequency Control> on cpu1 est: CPU supports Enhanced Speedstep, but is not recognized. est: cpu_vendor GenuineIntel, msr 23b500001b00 device_attach: est1 attach returned 6 p4tcc1: <CPU...

...ent *attach) > > > > +{ > > > > + int ret; > > > > + const struct virtio_dma_buf_ops *ops = container_of( > > > > + dma_buf->ops, const struct virtio_dma_buf_ops, ops); > > > > + > > > > + if (ops->device_attach) { > > > > + ret = ops->device_attach(dma_buf, attach); > > > > + if (ret) > > > > + return ret; > > > > + } > > > > + return 0; > > > > +} > > > > +EXPORT_SYMBOL(virtio_...

...>From dmesg (bge related): bge0: <Broadcom BCM5722 A0, ASIC rev. 0xa200> mem 0xe8400000-0xe840ffff irq 16 at device 0.0 on pci2 bge0: firmware handshake timed out, found 0x4b657654 bge0: firmware handshake timed out, found 0x4b657654 bge0: EEPROM read timed out bge0: failed to read EEPROM device_attach: bge0 attach returned 6 bge1: <Broadcom BCM5703 B0, ASIC rev. 0x1100> mem 0xe8600000-0xe860ffff irq 21 at device 1.0 on pci3 miibus0: <MII bus> on bge1 brgphy0: <BCM5703 10/100/1000baseTX PHY> on miibus0 brgphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 1000base...

Hi, I have a server (Dell PowerEdge SC1435, ServerWorks HT1000) on which I'd like to try installing FreeBSD. I've already failed to make 7.0 work on this box and was wondering if you have information about the behavior of the upcoming 7.1 on this hardware. I've been following the "HT1000 chipset errata saga" thread, and the commits by sos@ to CVS (around Jan 2008), but have

...ile a custom kernel without any network drivers in it, and then kldload if_txp, the following appears (same message on all 4 versions): txp0: <3Com 3cR990B-TXM Etherlink with 3XP Processor> port 0xbc00-0xbc7f mem 0xfdcff000-0xfdcff07f irq 16 at device 8.0 on pci3 txp0: not waiting for boot device_attach: txp0 attach returned -1 If I reboot and load if_nve (on 6.2 and 6-stable), then I get: nve0: <NVIDIA nForce MCP13 Networking Adapter> port 0xdc00-0xdc07 mem 0xfe02d000-0xfe02dfff irq 22 at device 20.0 on pci0 nve0: Ethernet address 00:19:21:37:d5:60 Followed by the above messages for txp0...

...f0: <ACPI CPU Frequency Control> on cpu0 p4tcc0: <CPU Frequency Thermal Control> on cpu0 cpu1: <ACPI CPU> on acpi0 est1: <Enhanced SpeedStep Frequency Control> on cpu1 est: CPU supports Enhanced Speedstep, but is not recognized. est: cpu_vendor GenuineIntel, msr 132d0000132d device_attach: est1 attach returned 6 p4tcc1: <CPU Frequency Thermal Control> on cpu1 cpu2: <ACPI CPU> on acpi0 est2: <Enhanced SpeedStep Frequency Control> on cpu2 est: CPU supports Enhanced Speedstep, but is not recognized. est: cpu_vendor GenuineIntel, msr 132d0000132d device_attach: est2 at...

...my notebook when ACPI is enabled for a year. The problem still exists in 7.1-RELEASE. with ACPI: ... bge0: <Broadcom NetLink Gigabit Ethernet Controller, ASIC rev. 0xb002> irq 17 at device 0.0 on pci8 bge0: 0x10000 bytes of rid 0x10 res 3 failed (0, 0xffffffff). bge0: couldn't map memory device_attach: bge0 attach returned 6 ... without ACPI: ... bge0: <Broadcom NetLink Gigabit Ethernet Controller, ASIC rev. 0xb002> mem 0xf3000000-0xf300ffff irq 17 at device 0.0 on pci8 miibus0: <MII bus> on bge0 brgphy0: <BCM5787 10/100/1000baseTX PHY> PHY 1 on miibus0 brgphy0: 10baseT, 10ba...

Hi experts I use xen-4.0.0 and dom0 is 2.6.33 and domU is 2.6.34 #lspci ............... 01:00.0 Ethernet controller: Intel Corporation Unknown device 10a7 (rev 02) 01:00.1 Ethernet controller: Intel Corporation Unknown device 10a7 (rev 02) 05:00.0 Ethernet controller: Intel Corporation 82571EB Gigabit Ethernet Controller (rev 06) 05:00.1 Ethernet controller: Intel Corporation 82571EB Gigabit

...acpi0: Power Button (fixed) Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000 acpi_timer0: <24-bit timer at 3.579545MHz> port 0x408-0x40b on acpi0 cpu0: <ACPI CPU> on acpi0 acpi_perf0: <ACPI CPU Frequency Control> on cpu0 acpi_perf0: failed in PERF_STATUS attach device_attach: acpi_perf0 attach returned 6 acpi_perf0: <ACPI CPU Frequency Control> on cpu0 acpi_perf0: failed in PERF_STATUS attach device_attach: acpi_perf0 attach returned 6 cpu1: <ACPI CPU> on acpi0 acpi_perf1: <ACPI CPU Frequency Control> on cpu1 acpi_perf1: failed in PERF_STATUS attach d...

...ying to use the latest drm hook for i915, but I get this error: drmsub0: <Intel i915GM> port 0x1800-0x1807 mem 0xb0080000-0xb00fffff,0xc0000000-0xcfffffff,0xb0000000-0xb003ffff irq 16 at device 2.0 on pci0 error: [drm:pid0:drm_load] *ERROR* Card isn't AGP, or couldn't initialize AGP. device_attach: drmsub0 attach returned 12 pci0: <display> at device 2.1 (no driver attached) Any idea ? I have added to my kernel: device agp # support several AGP chipsets device drm # DRM core module required by DRM drivers device i915drm # I...

...e Sep 17 11:25:39 romulus kernel: est0: <Enhanced SpeedStep Frequency Control> on cpu0 Sep 17 11:25:39 romulus kernel: est: CPU supports Enhanced Speedstep, but is not recognized. Sep 17 11:25:39 romulus kernel: est: cpu_vendor GenuineIntel, msr 719071906000719 Sep 17 11:25:39 romulus kernel: device_attach: est0 attach returned 6 Sep 17 11:25:39 romulus kernel: est1: <Enhanced SpeedStep Frequency Control> on cpu1 Sep 17 11:25:39 romulus kernel: est: CPU supports Enhanced Speedstep, but is not recognized. Sep 17 11:25:39 romulus kernel: est: cpu_vendor GenuineIntel, msr 719071906000719 Sep 17 11...