Re: ath0: could not map interrupt (again?)

2018-05-02 Thread Tim Chase
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 suggestion...much
faster than the svn+buildworld+buildkernel I'd been trying.
___
freebsd-wireless@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-wireless
To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"


Re: ath0: could not map interrupt (again?)

2018-05-02 Thread Adrian Chadd
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
___
freebsd-wireless@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-wireless
To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"


ath0: could not map interrupt (again?)

2018-05-02 Thread Tim Chase
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

Checking for "irq 17" suggests that my pcib1 is already using that
interrupt:

# dmesg | grep "irq 17"
pcib1:  irq 17 at device 28.0 on pci0
ath0:  mem 0xd800-0xd800 irq 17 at device 0.0 on pci2

I found a similar issue from back in 2013:

https://lists.freebsd.org/pipermail/freebsd-wireless/2013-January/002736.html

but it seems to be on a Mikrotik MIPS board.

An OpenBSD install on the same machine seems to find it well enough
to bring up the interface in case that helps.

Full dmesg below in case there are other details I missed.

Any suggestions on where I should go from here?

Thanks!

-tkc

Copyright (c) 1992-2017 The FreeBSD Project.
Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
The Regents of the University of California. All rights reserved.
FreeBSD is a registered trademark of The FreeBSD Foundation.
FreeBSD 11.1-RELEASE #0 r321309: Fri Jul 21 04:10:47 UTC 2017
r...@releng2.nyi.freebsd.org:/usr/obj/usr/src/sys/GENERIC i386
FreeBSD clang version 4.0.0 (tags/RELEASE_400/final 297347) (based on LLVM 
4.0.0)
VT(vga): resolution 640x480
CPU: Intel(R) Atom(TM) CPU Z520   @ 1.33GHz (1330.03-MHz 686-class CPU)
  Origin="GenuineIntel"  Id=0x106c2  Family=0x6  Model=0x1c  Stepping=2
  
Features=0xbfe9fbff
  Features2=0x40c3bd
  AMD Features=0x10
  AMD Features2=0x1
  VT-x: (disabled in BIOS) HLT,PAUSE
  TSC: P-state invariant, performance statistics
real memory  = 2147483648 (2048 MB)
avail memory = 2067849216 (1972 MB)
Event timer "LAPIC" quality 100
ACPI APIC Table: 
FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs
FreeBSD/SMP: 1 package(s) x 2 hardware threads
random: unblocking device.
ioapic0  irqs 0-23 on motherboard
SMP: AP CPU #1 Launched!
Timecounter "TSC" frequency 1330025320 Hz quality 1000
random: entropy device external interface
kbd1 at kbdmux0
module_register_init: MOD_LOAD (vesa, 0xc10123d0, 0) error 19
nexus0
vtvga0:  on motherboard
cryptosoft0:  on motherboard
aesni0: No AESNI support.
acpi0:  on motherboard
ACPI Error: Could not enable PowerButton event (20170303/evxfevnt-339)
ACPI Warning: Could not enable fixed event - PowerButton (2) 
(20170303/evxface-855)
acpi0: Power Button (fixed)
hpet0:  iomem 0xfed0-0xfed003ff irq 0,8 on acpi0
Timecounter "HPET" frequency 14318180 Hz quality 950
Event timer "HPET" frequency 14318180 Hz quality 450
Event timer "HPET1" frequency 14318180 Hz quality 440
Event timer "HPET2" frequency 14318180 Hz quality 440
cpu0:  on acpi0
cpu1:  on acpi0
atrtc0:  port 0x70-0x73 on acpi0
atrtc0: Warning: Couldn't map I/O.
Event timer "RTC" frequency 32768 Hz quality 0
attimer0:  port 0x40-0x43 on acpi0
Timecounter "i8254" frequency 1193182 Hz quality 0
Event timer "i8254" frequency 1193182 Hz quality 100
Timecounter "ACPI-fast" frequency 3579545 Hz quality 900
acpi_timer0: <24-bit timer at 3.579545MHz> port 0x1008-0x100b on acpi0
acpi_ec0:  port 0x62,0x66 on acpi0
acpi_lid0:  on acpi0
acpi_button0:  on acpi0
pcib0:  port 0xcf8-0xcff on acpi0
pcib0: could not evaluate _ADR - AE_NOT_FOUND
pcib0: Length mismatch for 3 range: 80 vs 7f
pci0:  on pcib0
vgapci0:  port 0x1800-0x1807 mem 
0xd810-0xd817,0xd000-0xd7ff,0xd838-0xd839 irq 16 at 
device 2.0 on pci0
vgapci0: Boot video device
hdac0:  mem 0xd83a-0xd83a3fff irq 22 at device 
27.0 on pci0
pcib1:  irq 17 at device 28.0 on pci0
pcib1: [GIANT-LOCKED]
pci1:  on pcib1
re0:  port 0x2000-0x20ff mem 
0xd841-0xd8410fff,0xd840-0xd840 irq 16 at device 0.0 on pci1
re0: Using 1 MSI-X message
re0: Chip rev. 0x2480
re0: MAC rev. 0x0040
miibus0:  on re0
rlphy0:  PHY 1 on miibus0
rlphy0:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto, auto-flow
re0: Using defaults for TSO: 65518/35/2048
re0: Ethernet address: 00:24:e8:c6:d7:2c
pcib2:  irq 16 at device 28.1 on pci0
pcib2: [GIANT-LOCKED]
pci2:  on pcib2
ath0:  mem 0xd800-0xd800 irq 17 at device 0.0 on pci2
ath0: could not map interrupt
device_attach: ath0 attach returned 6
uhci0:  port 0x1820-0x183f irq 23 at device 29.0 
on pci0
uhci0: LegSup = 0x
usbus0 on uhci0
usbus0: 12Mbps Full Speed USB v1.0
uhci1:  port 0x1840-0x185f irq 19 at device 29.1 
on pci0
uhci1: LegSup = 0x
usbus1 on uhci1
usbus1: 12Mbps Full Speed USB v1.0
uhci2:  port 0x1860-0x187f irq 18 at device 29.2 
on pci0
uhci2: LegSup = 0x
usbus2 on uhci2
usbus2: 12Mbps Full Speed USB v1.0
ehci0:  mem 0xd83a4000-0xd83a43ff irq 21 at 
device 29.7 on pci0
usbus3: EHCI version 1.0
usbus3 on ehci0
usbus3: 480Mbps High Speed USB v2.0
isab0:  at device 31.0 on pci0
isa0:  on isab0
atapci0:  port 
0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0x1810-0x181f at device 31.1 on pci0
ata0:  at channel 0 on atapci0
acpi_

[Bug 225728] iwm driver for 7265 says ieee80211_new_state_locked: pending SCAN -> AUTH transition lost

2018-05-02 Thread bugzilla-noreply
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 minutes:

-->8--
wlan0: ieee80211_new_state_locked: pending INIT -> AUTH transition lost
wlan0: link state changed to UP
wlan0: link state changed to DOWN
wlan0: ieee80211_new_state_locked: pending INIT -> AUTH transition lost
wlan0: link state changed to UP
wlan0: link state changed to DOWN
wlan0: ieee80211_new_state_locked: pending INIT -> AUTH transition lost
--8<--

If you can assist with "dumping device error log" I could provide that
information as well. It somehow really depends on the access point the notebook
is connected to.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-wireless@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-wireless
To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"