Sigh. Someone's broken the bus or interrupt handling code between -9 and -head. Or ACPI, for all I know. It may even be something to do with RFKILL. Can you please boot verbosely, both on -9 and -head? you don't have to do anything - just capture the logfile /var/run/dmesg.boot and attach them
Ok, the relevant / interesting bit:s. John, any ideas? HEAD: pcib2: ACPI PCI-PCI bridge irq 18 at device 28.2 on pci0 pcib0: allocated type 3 (0xe050-0xe05f) for rid 20 of pcib2 pcib2: domain0 pcib2: secondary bus 10 pcib2: subordinate bus 10 pcib2: memory
On Thursday, April 18, 2013 11:22:38 am Adrian Chadd wrote: Ok, the relevant / interesting bit:s. John, any ideas? Only that this means absolutely nothing? These are the values the BIOS wrote into the registers which we use as hints about whether or not ACPI lies about which interrupts are
... Why would it differ for the same machine, different kernel? Adrian Sent from my Palm Pre on ATamp;T On Apr 18, 2013 8:40 AM, John Baldwin lt;j...@freebsd.orggt; wrote: On Thursday, April 18, 2013 11:22:38 am Adrian Chadd wrote: gt; Ok, the relevant / interesting bit:s. John, any ideas?
Is this with or without AH_DEBUG ? Sent from my Palm Pre on ATamp;T On Apr 18, 2013 6:43 PM, Mike lt;russian...@gmail.comgt; wrote: Hello! I just wanted to notice, that Adrian's ath-hal git repository still has one error, which prevents building of ath-hal with clang.