On 2018-05-02 23:21, Adrian Chadd wrote:
> CAn you try booting freebsd-head and see if it's any better?
At your advice, I created a boot image of 12.0-CURRENT r333017 but
see the same "could not map interrupt" in my dmesg that I got on 11.x
-tim
PS: thanks for the boot-from-a-memstick-snapshot
Hi!
I'm not sure. It should be able to map it as a shared interrupt because
plenty of things could be downstream of that using a legacy interrupt. I
wonder if it's being mapped as a shared interrupt.
CAn you try booting freebsd-head and see if it's any better?
-adrian
__
I just replaced my rubbish BCM in my Dell Inspiron Mini10 (Atom CPU)
with an Atheros mini-PCI and FreeBSD seems to have trouble bringing
it up:
# dmesg | grep ath0
ath0: mem 0xd800-0xd800 irq 17 at device 0.0 on pci2
ath0: could not map interrupt
device_attach: ath0 attach returned 6
Che
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=225728
--- Comment #1 from Thomas Merkel ---
I basically have the same issue on the Thinkpad X1 Carbon 6th Generation with
FreeBSD-12-CURRENT. But somehow the disconnect and issue happen more often than
only one time an hour, more like every 10 mi
