search for: device_probe_and_attach

...ev/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 0xc0169ecf in device_attach (dev=0xc0e04b00) at device_if.h:178 #14 0xc016a9f0 in...

...hen the 'nvidia.ko' kernel module is loaded I got this message: nvidia0: <GeForce4 MX 440> mem 0xdda80000-0xddafffff,0xd0000000-0xd7ffffff,0xde0 00000-0xdeffffff irq 0 at device 0.0 on pci1 pci_cfgintr: can't route an interrupt to 1:0 INTA nvidia0: Interrupt handler setup failed. device_probe_and_attach: nvidia0 attach returned 22 I have tested my card under 4.7-STABLE, 4.8-STABLE and CURRENT and it is always the same message, what is wrong ? :/ Thanks.

...uestions but I have not get feed back. My laptop has an ALi M5451 Sound Card. I am using FreeBSD4.8-STABLE with the "device pcm" activated in the kernel. At boot time I get this output from the kernel: pcm0: <Acer Labs M5451> at device 4.0 on pci0 pcm0: unable to map register space device_probe_and_attach: pcm0 attach returned 6 Searching the Net I have found a URL where there is a FreeBSD driver for this card. I have tried without success to contact by email with the author. My questions are: - Is this sound card supported on FreeBSD? - If yes, which driver do I have to use? P.S: URL info ab...

...82443BX (440 BX) PCI-PCI (AGP) bridge> at device 1.0 on pci0 pci1: <PCI bus> on pcib1 drm0: <Matrox G400/G450 (AGP)> mem 0xe5000000-0xe57fffff,0xe4000000-0xe4003fff,0xe8000000-0xe9ffffff irq 11 at device 0.0 on pci1 error: [drm:mga_init] *ERROR* Cannot initialize the agpgart module. device_probe_and_attach: drm0 attach returned 12 System is running a world and kernel CVSUP'd today. The agpgart device exists: -bash-2.05b$ ls -lad /dev/agpgart crw------- 1 root wheel 148, 0 May 8 11:06 /dev/agpgart Kernel Configuration also includes "agp" -bash-2.05b$ kldstat Id Refs Address...

Hello, I am having a problem with a new server running FreeBSD 4.9-PRERELEASE. Once every two days or so, it reboots itself.. there is no exact time of the day it reboots.. It rebooted itself at 4:25 PM EDT on 9/25, and 3:05 AM EDT on 9/29 (today). I thought it's the bad memory or some sort, so I've been running memtest today and memtest reports no sign of trouble with the memory...

...n pci0 isa0: <ISA bus> on isab0 atapci0: <ServerWorks ROSB4 ATA33 controller> port 0xffa0-0xffaf at device 15.1 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ata1: at 0x170 irq 15 on atapci0 ohci0: <OHCI (generic) USB controller> irq 0 at device 15.2 on pci0 ohci0: Could not map memory device_probe_and_attach: ohci0 attach returned 6 pcib1: <ServerWorks NB6635 3.0LE host to PCI bridge> on motherboard pci2: <PCI bus> on pcib1 pcib2: <ServerWorks host to PCI bridge> on motherboard pci3: <PCI bus> on pcib2 pcib3: <ServerWorks host to PCI bridge> on motherboard pci4: <PCI bu...

...e 16550A sio3: type 16550A sio4: type 16550A sio5: type 16550A pci0: <unknown card> (vendor=0x1415, dev=0x9500) at 11.1 irq 10 viapropm0: SMBus I/O base at 0x400 viapropm0: <VIA VT8233 Power Management Unit> port 0x400-0x40f at device 17.0 on pci0 viapropm0: could not allocate bus space device_probe_and_attach: viapropm0 attach returned 6 atapci0: <VIA 8233 ATA133 controller> port 0xfc00-0xfc0f at device 17.1 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ata1: at 0x170 irq 15 on atapci0 uhci0: <VIA 83C572 USB controller> port 0xd400-0xd41f irq 10 at device 17.2 on pci0 usb0: <VIA 83C572 USB con...

...oller> port 0x2c00-0x2c0f at device 15.1 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ata1: at 0x170 irq 15 on atapci0 uhci0: <Intel 82371AB/EB (PIIX4) USB controller> port 0x2c20-0x2c3f at device 15.2 on pci0 pci_cfgintr: can't route an interrupt to 0:15 INTD uhci0: Could not allocate irq device_probe_and_attach: uhci0 attach returned 6 Timecounter "PIIX" frequency 3579545 Hz chip0: <Intel 82371AB Power management controller> port 0x1240-0x124f at device 15.3 on pci0 pcib2: <Intel 82454NX PCI Expander Bridge> at device 18.0 on pci0 pcib3: <Intel 82454NX PCI Expander Bridge> at...

...0x1f0 irq 14 on atapci0 > > ata1: at 0x170 irq 15 on atapci0 > > uhci0: <Intel 82371AB/EB (PIIX4) USB controller> port > > 0x2c20-0x2c3f at device 15.2 on pci0 > > pci_cfgintr: can't route an interrupt to 0:15 INTD > > uhci0: Could not allocate irq > > device_probe_and_attach: uhci0 attach returned 6 > > Timecounter "PIIX" frequency 3579545 Hz > > chip0: <Intel 82371AB Power management controller> port > > 0x1240-0x124f at device 15.3 on pci0 > > pcib2: <Intel 82454NX PCI Expander Bridge> at device 18.0 > on > > pc...

...va=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 ata_attach (dev=0xc5167100) at /usr/src/sys/de...

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