All of lore.kernel.org
 help / color / mirror / Atom feed
* Re: 4.9 Kernel panic on ACS and intermittent ability to host AP
@ 2017-03-07 12:15 Chris Price
  0 siblings, 0 replies; 8+ messages in thread
From: Chris Price @ 2017-03-07 12:15 UTC (permalink / raw)
  To: ath10k

> Could you share the logs with both driver and hostapd (-vvv), please?

# dmesg | grep ath
[    3.263913] ath10k_pci 0000:02:00.0: pci irq msi oper_irq_mode 2
irq_mode 0 reset_mode 0
[    3.545202] ath10k_pci 0000:02:00.0: Direct firmware load for
ath10k/pre-cal-pci-0000:02:00.0.bin failed with error -2
[    3.545211] ath10k_pci 0000:02:00.0: Direct firmware load for
ath10k/cal-pci-0000:02:00.0.bin failed with error -2
[    3.547297] ath10k_pci 0000:02:00.0: qca6174 hw3.2 target
0x05030000 chip_id 0x00340aff sub 1a3b:2260
[    3.547299] ath10k_pci 0000:02:00.0: kconfig debug 0 debugfs 1
tracing 1 dfs 0 testmode 0
[    3.547850] ath10k_pci 0000:02:00.0: firmware ver
WLAN.RM.4.4-00022-QCARMSWPZ-2 api 5 features wowlan,ignore-otp crc32
4d458559
[    3.612058] ath10k_pci 0000:02:00.0: board id is not exist in otp, ignore it
[    3.613345] ath10k_pci 0000:02:00.0: board_file api 2 bmi_id N/A
crc32 6fc88fe7
[    5.773868] ath10k_pci 0000:02:00.0: Unknown eventid: 90118
[    5.774460] ath10k_pci 0000:02:00.0: htt-ver 3.32 wmi-op 4 htt-op 3
cal otp max-sta 32 raw 0 hwcrypto 1
[    5.862557] ath: EEPROM regdomain: 0x6a
[    5.862558] ath: EEPROM indicates we should expect a direct regpair map
[    5.862560] ath: Country alpha2 being used: 00
[    5.862560] ath: Regpair used: 0x6a

# hostapd -dd /etc/hostapd/hostapd1.conf
random: Trying to read entropy from /dev/random
Configuration file: /etc/hostapd/hostapd1.conf
rfkill: initial event: idx=0 type=2 op=0 soft=0 hard=0
rfkill: initial event: idx=1 type=1 op=0 soft=0 hard=0
nl80211: TDLS supported
nl80211: TDLS external setup
nl80211: Supported cipher 00-0f-ac:1
nl80211: Supported cipher 00-0f-ac:5
nl80211: Supported cipher 00-0f-ac:2
nl80211: Supported cipher 00-0f-ac:4
nl80211: Supported cipher 00-0f-ac:6
nl80211: Supports Probe Response offload in AP mode
nl80211: Using driver-based off-channel TX
nl80211: Use separate P2P group interface (driver advertised support)
nl80211: Enable multi-channel concurrent (driver advertised support)
nl80211: interface ap1 in phy phy0
nl80211: Set mode ifindex 8 iftype 3 (AP)
nl80211: Setup AP(ap1) - device_ap_sme=0 use_monitor=0
nl80211: Subscribe to mgmt frames with AP handle 0x558e70e60dd0
nl80211: Register frame type=0xb0 (WLAN_FC_STYPE_AUTH)
nl_handle=0x558e70e60dd0 match=
nl80211: Register frame type=0x0 (WLAN_FC_STYPE_ASSOC_REQ)
nl_handle=0x558e70e60dd0 match=
nl80211: Register frame type=0x20 (WLAN_FC_STYPE_REASSOC_REQ)
nl_handle=0x558e70e60dd0 match=
nl80211: Register frame type=0xa0 (WLAN_FC_STYPE_DISASSOC)
nl_handle=0x558e70e60dd0 match=
nl80211: Register frame type=0xc0 (WLAN_FC_STYPE_DEAUTH)
nl_handle=0x558e70e60dd0 match=
nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION)
nl_handle=0x558e70e60dd0 match=
nl80211: Register frame type=0x40 (WLAN_FC_STYPE_PROBE_REQ)
nl_handle=0x558e70e60dd0 match=
nl80211: Add own interface ifindex 8
nl80211: if_indices[16]: 8
nl80211: Do not indicate P2P_DEVICE support (p2p_device=1 driver param
not specified)
phy: phy0
BSS count 1, BSSID mask 00:00:00:00:00:00 (0 bits)
ap1: interface state UNINITIALIZED->COUNTRY_UPDATE
Previous country code 00, new country code CA
Continue interface setup after channel list update
ctrl_iface not configured!
random: Got 15/20 bytes from /dev/random
RTM_NEWLINK: ifi_index=8 ifname=ap1 operstate=0 linkmode=0
ifi_family=0 ifi_flags=0x1043 ([UP][RUNNING])
RTM_NEWLINK: ifi_index=8 ifname=ap1 operstate=2 linkmode=0
ifi_family=0 ifi_flags=0x1003 ([UP])
nl80211: Event message available
nl80211: Drv Event 36 (NL80211_CMD_REG_CHANGE) received for ap1
nl80211: Regulatory domain change
 * initiator=1
 * type=0
 * alpha2=CA
ap1: Event CHANNEL_LIST_CHANGED (30) received
Channel list updated - continue setup
nl80211: Regulatory information - country=CA (DFS-FCC)
nl80211: 2402-2472 @ 40 MHz 30 mBm
nl80211: 5170-5250 @ 80 MHz 17 mBm
nl80211: 5250-5330 @ 80 MHz 24 mBm (DFS)
nl80211: 5490-5600 @ 80 MHz 24 mBm (DFS)
nl80211: 5650-5730 @ 80 MHz 24 mBm (DFS)
nl80211: 5735-5835 @ 80 MHz 30 mBm
nl80211: Added 802.11b mode based on 802.11g information
Allowed channel: mode=1 chan=1 freq=2412 MHz max_tx_power=30 dBm
Allowed channel: mode=1 chan=2 freq=2417 MHz max_tx_power=30 dBm
Allowed channel: mode=1 chan=3 freq=2422 MHz max_tx_power=30 dBm
Allowed channel: mode=1 chan=4 freq=2427 MHz max_tx_power=30 dBm
Allowed channel: mode=1 chan=5 freq=2432 MHz max_tx_power=30 dBm
Allowed channel: mode=1 chan=6 freq=2437 MHz max_tx_power=30 dBm
Allowed channel: mode=1 chan=7 freq=2442 MHz max_tx_power=30 dBm
Allowed channel: mode=1 chan=8 freq=2447 MHz max_tx_power=30 dBm
Allowed channel: mode=1 chan=9 freq=2452 MHz max_tx_power=30 dBm
Allowed channel: mode=1 chan=10 freq=2457 MHz max_tx_power=30 dBm
Allowed channel: mode=1 chan=11 freq=2462 MHz max_tx_power=30 dBm
Allowed channel: mode=0 chan=1 freq=2412 MHz max_tx_power=30 dBm
Allowed channel: mode=0 chan=2 freq=2417 MHz max_tx_power=30 dBm
Allowed channel: mode=0 chan=3 freq=2422 MHz max_tx_power=30 dBm
Allowed channel: mode=0 chan=4 freq=2427 MHz max_tx_power=30 dBm
Allowed channel: mode=0 chan=5 freq=2432 MHz max_tx_power=30 dBm
Allowed channel: mode=0 chan=6 freq=2437 MHz max_tx_power=30 dBm
Allowed channel: mode=0 chan=7 freq=2442 MHz max_tx_power=30 dBm
Allowed channel: mode=0 chan=8 freq=2447 MHz max_tx_power=30 dBm
Allowed channel: mode=0 chan=9 freq=2452 MHz max_tx_power=30 dBm
Allowed channel: mode=0 chan=10 freq=2457 MHz max_tx_power=30 dBm
Allowed channel: mode=0 chan=11 freq=2462 MHz max_tx_power=30 dBm
ACS: Automatic channel selection started, this may take a bit
ACS: Scanning 1 / 5
ap1: nl80211: scan request
Scan requested (ret=0) - scan timeout 10 seconds
ap1: interface state COUNTRY_UPDATE->ACS
ap1: ACS-STARTED
Interface initialization will be completed in a callback (ACS)
nl80211: Event message available
nl80211: Drv Event 33 (NL80211_CMD_TRIGGER_SCAN) received for ap1
ap1: nl80211: Scan trigger
ap1: Event SCAN_STARTED (49) received
Unknown event 49
nl80211: Event message available
nl80211: Drv Event 42 (NL80211_CMD_REG_BEACON_HINT) received for ap1
nl80211: Regulatory beacon hint
ap1: Event CHANNEL_LIST_CHANGED (30) received
nl80211: Event message available
nl80211: Drv Event 42 (NL80211_CMD_REG_BEACON_HINT) received for ap1
nl80211: Regulatory beacon hint
ap1: Event CHANNEL_LIST_CHANGED (30) received
nl80211: Event message available
nl80211: Drv Event 42 (NL80211_CMD_REG_BEACON_HINT) received for ap1
nl80211: Regulatory beacon hint
ap1: Event CHANNEL_LIST_CHANGED (30) received
nl80211: Event message available
nl80211: Drv Event 42 (NL80211_CMD_REG_BEACON_HINT) received for ap1
nl80211: Regulatory beacon hint
ap1: Event CHANNEL_LIST_CHANGED (30) received
nl80211: Event message available
nl80211: Drv Event 42 (NL80211_CMD_REG_BEACON_HINT) received for ap1
nl80211: Regulatory beacon hint
ap1: Event CHANNEL_LIST_CHANGED (30) received
nl80211: Event message available
nl80211: Drv Event 42 (NL80211_CMD_REG_BEACON_HINT) received for ap1
nl80211: Regulatory beacon hint
ap1: Event CHANNEL_LIST_CHANGED (30) received
RTM_NEWLINK: ifi_index=8 ifname=ap1 wext ifi_family=0 ifi_flags=0x1003 ([UP])
nl80211: Event message available
nl80211: Drv Event 34 (NL80211_CMD_NEW_SCAN_RESULTS) received for ap1
ap1: nl80211: New scan results available
nl80211: Scan included frequencies: 2412 2417 2422 2427 2432 2437 2442
2447 2452 2457 2462 5180 5200 5220 5240 5260 5280 5300 5320 5500 5520
5540 5560 5580 5660 5680 5700 5720 5745 5765 5785 5805 5825
ap1: Event SCAN_RESULTS (3) received
ACS: Using survey based algorithm (acs_num_scans=5)
nl80211: Fetch survey data
nl80211: Freq survey dump event (freq=2412 MHz noise=-101
channel_time=150 busy_time=62 tx_time=0 rx_time=0 filled=0007)
nl80211: Freq survey dump event (freq=2417 MHz noise=-101
channel_time=149 busy_time=30 tx_time=0 rx_time=0 filled=0007)
nl80211: Freq survey dump event (freq=2422 MHz noise=-102
channel_time=149 busy_time=118 tx_time=0 rx_time=0 filled=0007)
nl80211: Freq survey dump event (freq=2427 MHz noise=-102
channel_time=149 busy_time=21 tx_time=0 rx_time=0 filled=0007)
nl80211: Freq survey dump event (freq=2432 MHz noise=-104
channel_time=149 busy_time=42 tx_time=0 rx_time=0 filled=0007)
nl80211: Freq survey dump event (freq=2437 MHz noise=-104
channel_time=149 busy_time=28 tx_time=0 rx_time=0 filled=0007)
nl80211: Freq survey dump event (freq=2442 MHz noise=-105
channel_time=149 busy_time=52 tx_time=0 rx_time=0 filled=0007)
nl80211: Freq survey dump event (freq=2447 MHz noise=-106
channel_time=149 busy_time=63 tx_time=0 rx_time=0 filled=0007)
nl80211: Freq survey dump event (freq=2452 MHz noise=-105
channel_time=149 busy_time=54 tx_time=0 rx_time=0 filled=0007)
nl80211: Freq survey dump event (freq=2457 MHz noise=-105
channel_time=149 busy_time=46 tx_time=0 rx_time=0 filled=0007)
nl80211: Freq survey dump event (freq=2462 MHz noise=-106
channel_time=149 busy_time=122 tx_time=0 rx_time=0 filled=0007)
nl80211: Freq survey dump event (freq=5180 MHz noise=-100
channel_time=146 busy_time=11 tx_time=0 rx_time=0 filled=0007)
nl80211: Freq survey dump event (freq=5200 MHz noise=-43
channel_time=149 busy_time=63 tx_time=0 rx_time=0 filled=0007)
nl80211: Freq survey dump event (freq=5220 MHz noise=-100
channel_time=149 busy_time=0 tx_time=0 rx_time=0 filled=0007)
nl80211: Freq survey dump event (freq=5240 MHz noise=-100
channel_time=149 busy_time=4 tx_time=0 rx_time=0 filled=0007)
nl80211: Freq survey dump event (freq=5260 MHz noise=-100
channel_time=149 busy_time=0 tx_time=0 rx_time=0 filled=0007)
nl80211: Freq survey dump event (freq=5280 MHz noise=-99
channel_time=149 busy_time=0 tx_time=0 rx_time=0 filled=0007)
nl80211: Freq survey dump event (freq=5300 MHz noise=-99
channel_time=149 busy_time=0 tx_time=0 rx_time=0 filled=0007)
nl80211: Freq survey dump event (freq=5320 MHz noise=-98
channel_time=149 busy_time=0 tx_time=0 rx_time=0 filled=0007)
nl80211: Freq survey dump event (freq=5500 MHz noise=-43
channel_time=149 busy_time=61 tx_time=0 rx_time=0 filled=0007)
nl80211: Freq survey dump event (freq=5520 MHz noise=-97
channel_time=149 busy_time=0 tx_time=0 rx_time=0 filled=0007)
nl80211: Freq survey dump event (freq=5540 MHz noise=-96
channel_time=149 busy_time=0 tx_time=0 rx_time=0 filled=0007)
nl80211: Freq survey dump event (freq=5560 MHz noise=-96
channel_time=149 busy_time=0 tx_time=0 rx_time=0 filled=0007)
nl80211: Freq survey dump event (freq=5580 MHz noise=-97
channel_time=149 busy_time=0 tx_time=0 rx_time=0 filled=0007)
nl80211: Freq survey dump event (freq=5660 MHz noise=-97
channel_time=149 busy_time=0 tx_time=0 rx_time=0 filled=0007)
nl80211: Freq survey dump event (freq=5680 MHz noise=-97
channel_time=149 busy_time=0 tx_time=0 rx_time=0 filled=0007)
nl80211: Freq survey dump event (freq=5700 MHz noise=-97
channel_time=149 busy_time=0 tx_time=0 rx_time=0 filled=0007)
nl80211: Freq survey dump event (freq=5720 MHz noise=-97
channel_time=149 busy_time=0 tx_time=0 rx_time=0 filled=0007)
nl80211: Freq survey dump event (freq=5745 MHz noise=-96
channel_time=149 busy_time=10 tx_time=0 rx_time=0 filled=0007)
nl80211: Freq survey dump event (freq=5765 MHz noise=-43
channel_time=149 busy_time=106 tx_time=0 rx_time=0 filled=0007)
nl80211: Freq survey dump event (freq=5785 MHz noise=-96
channel_time=149 busy_time=21 tx_time=0 rx_time=0 filled=0007)
nl80211: Freq survey dump event (freq=5805 MHz noise=-96
channel_time=149 busy_time=1 tx_time=0 rx_time=0 filled=0007)
nl80211: Freq survey dump event (freq=5825 MHz noise=-96
channel_time=149 busy_time=0 tx_time=0 rx_time=0 filled=0007)
ap1: Event SURVEY (48) received
ACS: Scanning 2 / 5
ap1: nl80211: scan request
Scan requested (ret=0) - scan timeout 30 seconds
nl80211: Event message available
nl80211: Drv Event 33 (NL80211_CMD_TRIGGER_SCAN) received for ap1
ap1: nl80211: Scan trigger
ap1: Event SCAN_STARTED (49) received
Unknown event 49
RTM_NEWLINK: ifi_index=8 ifname=ap1 wext ifi_family=0 ifi_flags=0x1003 ([UP])
nl80211: Event message available
nl80211: Drv Event 34 (NL80211_CMD_NEW_SCAN_RESULTS) received for ap1
ap1: nl80211: New scan results available
nl80211: Scan included frequencies: 2412 2417 2422 2427 2432 2437 2442
2447 2452 2457 2462 5180 5200 5220 5240 5260 5280 5300 5320 5500 5520
5540 5560 5580 5660 5680 5700 5720 5745 5765 5785 5805 5825
ap1: Event SCAN_RESULTS (3) received
ACS: Using survey based algorithm (acs_num_scans=5)
nl80211: Fetch survey data
nl80211: Freq survey dump event (freq=2412 MHz noise=-54
channel_time=149 busy_time=129 tx_time=0 rx_time=0 filled=0007)
nl80211: Freq survey dump event (freq=2417 MHz noise=-101
channel_time=149 busy_time=91 tx_time=0 rx_time=0 filled=0007)
nl80211: Freq survey dump event (freq=2422 MHz noise=-101
channel_time=149 busy_time=79 tx_time=0 rx_time=0 filled=0007)
nl80211: Freq survey dump event (freq=2427 MHz noise=-102
channel_time=149 busy_time=78 tx_time=0 rx_time=0 filled=0007)
nl80211: Freq survey dump event (freq=2432 MHz noise=-103
channel_time=149 busy_time=98 tx_time=0 rx_time=0 filled=0007)
nl80211: Freq survey dump event (freq=2437 MHz noise=-104
channel_time=149 busy_time=42 tx_time=0 rx_time=0 filled=0007)
nl80211: Freq survey dump event (freq=2442 MHz noise=-104
channel_time=149 busy_time=56 tx_time=0 rx_time=0 filled=0007)
nl80211: Freq survey dump event (freq=2447 MHz noise=-105
channel_time=149 busy_time=86 tx_time=0 rx_time=0 filled=0007)
nl80211: Freq survey dump event (freq=2452 MHz noise=-105
channel_time=149 busy_time=123 tx_time=0 rx_time=0 filled=0007)
nl80211: Freq survey dump event (freq=2457 MHz noise=-106
channel_time=149 busy_time=69 tx_time=0 rx_time=0 filled=0007)
nl80211: Freq survey dump event (freq=2462 MHz noise=-106
channel_time=149 busy_time=39 tx_time=0 rx_time=0 filled=0007)
nl80211: Freq survey dump event (freq=5180 MHz noise=-100
channel_time=149 busy_time=15 tx_time=0 rx_time=0 filled=0007)
nl80211: Freq survey dump event (freq=5200 MHz noise=-43
channel_time=149 busy_time=66 tx_time=0 rx_time=0 filled=0007)
nl80211: Freq survey dump event (freq=5220 MHz noise=-100
channel_time=149 busy_time=0 tx_time=0 rx_time=0 filled=0007)
nl80211: Freq survey dump event (freq=5240 MHz noise=-99
channel_time=149 busy_time=3 tx_time=0 rx_time=0 filled=0007)
nl80211: Freq survey dump event (freq=5260 MHz noise=-100
channel_time=149 busy_time=0 tx_time=0 rx_time=0 filled=0007)
nl80211: Freq survey dump event (freq=5280 MHz noise=-99
channel_time=149 busy_time=0 tx_time=0 rx_time=0 filled=0007)
nl80211: Freq survey dump event (freq=5300 MHz noise=-99
channel_time=149 busy_time=0 tx_time=0 rx_time=0 filled=0007)
nl80211: Freq survey dump event (freq=5320 MHz noise=-99
channel_time=149 busy_time=0 tx_time=0 rx_time=0 filled=0007)
nl80211: Freq survey dump event (freq=5500 MHz noise=-43
channel_time=149 busy_time=62 tx_time=0 rx_time=0 filled=0007)
nl80211: Freq survey dump event (freq=5520 MHz noise=-97
channel_time=149 busy_time=0 tx_time=0 rx_time=0 filled=0007)
nl80211: Freq survey dump event (freq=5540 MHz noise=-96
channel_time=149 busy_time=0 tx_time=0 rx_time=0 filled=0007)
nl80211: Freq survey dump event (freq=5560 MHz noise=-96
channel_time=149 busy_time=0 tx_time=0 rx_time=0 filled=0007)
nl80211: Freq survey dump event (freq=5580 MHz noise=-97
channel_time=149 busy_time=0 tx_time=0 rx_time=0 filled=0007)
nl80211: Freq survey dump event (freq=5660 MHz noise=-97
channel_time=149 busy_time=0 tx_time=0 rx_time=0 filled=0007)
nl80211: Freq survey dump event (freq=5680 MHz noise=-97
channel_time=149 busy_time=0 tx_time=0 rx_time=0 filled=0007)
nl80211: Freq survey dump event (freq=5700 MHz noise=-97
channel_time=149 busy_time=0 tx_time=0 rx_time=0 filled=0007)
nl80211: Freq survey dump event (freq=5720 MHz noise=-97
channel_time=149 busy_time=0 tx_time=0 rx_time=0 filled=0007)
nl80211: Freq survey dump event (freq=5745 MHz noise=-96
channel_time=149 busy_time=5 tx_time=0 rx_time=0 filled=0007)
nl80211: Freq survey dump event (freq=5765 MHz noise=-43
channel_time=149 busy_time=106 tx_time=0 rx_time=0 filled=0007)
nl80211: Freq survey dump event (freq=5785 MHz noise=-96
channel_time=149 busy_time=2 tx_time=0 rx_time=0 filled=0007)
nl80211: Freq survey dump event (freq=5805 MHz noise=-97
channel_time=149 busy_time=1 tx_time=0 rx_time=0 filled=0007)
nl80211: Freq survey dump event (freq=5825 MHz noise=-96
channel_time=149 busy_time=0 tx_time=0 rx_time=0 filled=0007)
ap1: Event SURVEY (48) received
ACS: Scanning 3 / 5
ap1: nl80211: scan request
Scan requested (ret=0) - scan timeout 30 seconds
nl80211: Event message available
nl80211: Drv Event 33 (NL80211_CMD_TRIGGER_SCAN) received for ap1
ap1: nl80211: Scan trigger
ap1: Event SCAN_STARTED (49) received
Unknown event 49
RTM_NEWLINK: ifi_index=8 ifname=ap1 wext ifi_family=0 ifi_flags=0x1003 ([UP])
nl80211: Event message available
nl80211: Drv Event 34 (NL80211_CMD_NEW_SCAN_RESULTS) received for ap1
ap1: nl80211: New scan results available
nl80211: Scan included frequencies: 2412 2417 2422 2427 2432 2437 2442
2447 2452 2457 2462 5180 5200 5220 5240 5260 5280 5300 5320 5500 5520
5540 5560 5580 5660 5680 5700 5720 5745 5765 5785 5805 5825
ap1: Event SCAN_RESULTS (3) received
ACS: Using survey based algorithm (acs_num_scans=5)
nl80211: Fetch survey data
nl80211: Freq survey dump event (freq=2412 MHz noise=-101
channel_time=149 busy_time=14 tx_time=0 rx_time=0 filled=0007)
nl80211: Freq survey dump event (freq=2417 MHz noise=-101
channel_time=149 busy_time=17 tx_time=0 rx_time=0 filled=0007)
nl80211: Freq survey dump event (freq=2422 MHz noise=-102
channel_time=149 busy_time=62 tx_time=0 rx_time=0 filled=0007)
nl80211: Freq survey dump event (freq=2427 MHz noise=-102
channel_time=149 busy_time=74 tx_time=0 rx_time=0 filled=0007)
nl80211: Freq survey dump event (freq=2432 MHz noise=-103
channel_time=149 busy_time=36 tx_time=0 rx_time=0 filled=0007)
nl80211: Freq survey dump event (freq=2437 MHz noise=-104
channel_time=149 busy_time=25 tx_time=0 rx_time=0 filled=0007)
nl80211: Freq survey dump event (freq=2442 MHz noise=-105
channel_time=149 busy_time=31 tx_time=0 rx_time=0 filled=0007)
nl80211: Freq survey dump event (freq=2447 MHz noise=-105
channel_time=149 busy_time=62 tx_time=0 rx_time=0 filled=0007)
nl80211: Freq survey dump event (freq=2452 MHz noise=-105
channel_time=149 busy_time=59 tx_time=0 rx_time=0 filled=0007)
nl80211: Freq survey dump event (freq=2457 MHz noise=-106
channel_time=149 busy_time=62 tx_time=0 rx_time=0 filled=0007)
nl80211: Freq survey dump event (freq=2462 MHz noise=-106
channel_time=149 busy_time=106 tx_time=0 rx_time=0 filled=0007)
nl80211: Freq survey dump event (freq=5180 MHz noise=-100
channel_time=149 busy_time=20 tx_time=0 rx_time=0 filled=0007)
nl80211: Freq survey dump event (freq=5200 MHz noise=-43
channel_time=149 busy_time=66 tx_time=0 rx_time=0 filled=0007)
nl80211: Freq survey dump event (freq=5220 MHz noise=-99
channel_time=149 busy_time=0 tx_time=0 rx_time=0 filled=0007)
nl80211: Freq survey dump event (freq=5240 MHz noise=-99
channel_time=149 busy_time=3 tx_time=0 rx_time=0 filled=0007)
nl80211: Freq survey dump event (freq=5260 MHz noise=-99
channel_time=149 busy_time=0 tx_time=0 rx_time=0 filled=0007)
nl80211: Freq survey dump event (freq=5280 MHz noise=-99
channel_time=149 busy_time=0 tx_time=0 rx_time=0 filled=0007)
nl80211: Freq survey dump event (freq=5300 MHz noise=-99
channel_time=149 busy_time=0 tx_time=0 rx_time=0 filled=0007)
nl80211: Freq survey dump event (freq=5320 MHz noise=-98
channel_time=149 busy_time=0 tx_time=0 rx_time=0 filled=0007)
nl80211: Freq survey dump event (freq=5500 MHz noise=-43
channel_time=149 busy_time=61 tx_time=0 rx_time=0 filled=0007)
nl80211: Freq survey dump event (freq=5520 MHz noise=-97
channel_time=149 busy_time=0 tx_time=0 rx_time=0 filled=0007)
nl80211: Freq survey dump event (freq=5540 MHz noise=-96
channel_time=149 busy_time=0 tx_time=0 rx_time=0 filled=0007)
nl80211: Freq survey dump event (freq=5560 MHz noise=-96
channel_time=149 busy_time=0 tx_time=0 rx_time=0 filled=0007)
nl80211: Freq survey dump event (freq=5580 MHz noise=-96
channel_time=149 busy_time=0 tx_time=0 rx_time=0 filled=0007)
nl80211: Freq survey dump event (freq=5660 MHz noise=-97
channel_time=149 busy_time=0 tx_time=0 rx_time=0 filled=0007)
nl80211: Freq survey dump event (freq=5680 MHz noise=-97
channel_time=149 busy_time=0 tx_time=0 rx_time=0 filled=0007)
nl80211: Freq survey dump event (freq=5700 MHz noise=-97
channel_time=149 busy_time=0 tx_time=0 rx_time=0 filled=0007)
nl80211: Freq survey dump event (freq=5720 MHz noise=-96
channel_time=149 busy_time=0 tx_time=0 rx_time=0 filled=0007)
nl80211: Freq survey dump event (freq=5745 MHz noise=-96
channel_time=149 busy_time=13 tx_time=0 rx_time=0 filled=0007)
nl80211: Freq survey dump event (freq=5765 MHz noise=-43
channel_time=149 busy_time=107 tx_time=0 rx_time=0 filled=0007)
nl80211: Freq survey dump event (freq=5785 MHz noise=-96
channel_time=149 busy_time=1 tx_time=0 rx_time=0 filled=0007)
nl80211: Freq survey dump event (freq=5805 MHz noise=-97
channel_time=149 busy_time=1 tx_time=0 rx_time=0 filled=0007)
nl80211: Freq survey dump event (freq=5825 MHz noise=-96
channel_time=149 busy_time=0 tx_time=0 rx_time=0 filled=0007)
ap1: Event SURVEY (48) received
ACS: Scanning 4 / 5
ap1: nl80211: scan request
Scan requested (ret=0) - scan timeout 30 seconds
nl80211: Event message available
nl80211: Drv Event 33 (NL80211_CMD_TRIGGER_SCAN) received for ap1
ap1: nl80211: Scan trigger
ap1: Event SCAN_STARTED (49) received
Unknown event 49
RTM_NEWLINK: ifi_index=8 ifname=ap1 wext ifi_family=0 ifi_flags=0x1003 ([UP])
nl80211: Event message available
nl80211: Drv Event 34 (NL80211_CMD_NEW_SCAN_RESULTS) received for ap1
ap1: nl80211: New scan results available
nl80211: Scan included frequencies: 2412 2417 2422 2427 2432 2437 2442
2447 2452 2457 2462 5180 5200 5220 5240 5260 5280 5300 5320 5500 5520
5540 5560 5580 5660 5680 5700 5720 5745 5765 5785 5805 5825
ap1: Event SCAN_RESULTS (3) received
ACS: Using survey based algorithm (acs_num_scans=5)
nl80211: Fetch survey data
nl80211: Freq survey dump event (freq=2412 MHz noise=-101
channel_time=149 busy_time=108 tx_time=0 rx_time=0 filled=0007)
nl80211: Freq survey dump event (freq=2417 MHz noise=-101
channel_time=149 busy_time=64 tx_time=0 rx_time=0 filled=0007)
nl80211: Freq survey dump event (freq=2422 MHz noise=-102
channel_time=149 busy_time=88 tx_time=0 rx_time=0 filled=0007)
nl80211: Freq survey dump event (freq=2427 MHz noise=-102
channel_time=149 busy_time=76 tx_time=0 rx_time=0 filled=0007)
nl80211: Freq survey dump event (freq=2432 MHz noise=-104
channel_time=149 busy_time=64 tx_time=0 rx_time=0 filled=0007)
nl80211: Freq survey dump event (freq=2437 MHz noise=-105
channel_time=149 busy_time=37 tx_time=0 rx_time=0 filled=0007)
nl80211: Freq survey dump event (freq=2442 MHz noise=-105
channel_time=149 busy_time=80 tx_time=0 rx_time=0 filled=0007)
nl80211: Freq survey dump event (freq=2447 MHz noise=-105
channel_time=149 busy_time=100 tx_time=0 rx_time=0 filled=0007)
nl80211: Freq survey dump event (freq=2452 MHz noise=-105
channel_time=149 busy_time=123 tx_time=0 rx_time=0 filled=0007)
nl80211: Freq survey dump event (freq=2457 MHz noise=-106
channel_time=149 busy_time=89 tx_time=0 rx_time=0 filled=0007)
nl80211: Freq survey dump event (freq=2462 MHz noise=-106
channel_time=149 busy_time=34 tx_time=0 rx_time=0 filled=0007)
nl80211: Freq survey dump event (freq=5180 MHz noise=-100
channel_time=149 busy_time=6 tx_time=0 rx_time=0 filled=0007)
nl80211: Freq survey dump event (freq=5200 MHz noise=-43
channel_time=149 busy_time=68 tx_time=0 rx_time=0 filled=0007)
nl80211: Freq survey dump event (freq=5220 MHz noise=-100
channel_time=149 busy_time=0 tx_time=0 rx_time=0 filled=0007)
nl80211: Freq survey dump event (freq=5240 MHz noise=-100
channel_time=149 busy_time=3 tx_time=0 rx_time=0 filled=0007)
nl80211: Freq survey dump event (freq=5260 MHz noise=-100
channel_time=149 busy_time=0 tx_time=0 rx_time=0 filled=0007)
nl80211: Freq survey dump event (freq=5280 MHz noise=-99
channel_time=149 busy_time=0 tx_time=0 rx_time=0 filled=0007)
nl80211: Freq survey dump event (freq=5300 MHz noise=-99
channel_time=149 busy_time=0 tx_time=0 rx_time=0 filled=0007)
nl80211: Freq survey dump event (freq=5320 MHz noise=-98
channel_time=149 busy_time=0 tx_time=0 rx_time=0 filled=0007)
nl80211: Freq survey dump event (freq=5500 MHz noise=-43
channel_time=149 busy_time=60 tx_time=0 rx_time=0 filled=0007)
nl80211: Freq survey dump event (freq=5520 MHz noise=-96
channel_time=149 busy_time=0 tx_time=0 rx_time=0 filled=0007)
nl80211: Freq survey dump event (freq=5540 MHz noise=-96
channel_time=149 busy_time=0 tx_time=0 rx_time=0 filled=0007)
nl80211: Freq survey dump event (freq=5560 MHz noise=-96
channel_time=149 busy_time=0 tx_time=0 rx_time=0 filled=0007)
nl80211: Freq survey dump event (freq=5580 MHz noise=-96
channel_time=149 busy_time=0 tx_time=0 rx_time=0 filled=0007)
nl80211: Freq survey dump event (freq=5660 MHz noise=-97
channel_time=149 busy_time=0 tx_time=0 rx_time=0 filled=0007)
nl80211: Freq survey dump event (freq=5680 MHz noise=-97
channel_time=149 busy_time=0 tx_time=0 rx_time=0 filled=0007)
nl80211: Freq survey dump event (freq=5700 MHz noise=-96
channel_time=149 busy_time=0 tx_time=0 rx_time=0 filled=0007)
nl80211: Freq survey dump event (freq=5720 MHz noise=-97
channel_time=149 busy_time=0 tx_time=0 rx_time=0 filled=0007)
nl80211: Freq survey dump event (freq=5745 MHz noise=-96
channel_time=149 busy_time=6 tx_time=0 rx_time=0 filled=0007)
nl80211: Freq survey dump event (freq=5765 MHz noise=-43
channel_time=149 busy_time=106 tx_time=0 rx_time=0 filled=0007)
nl80211: Freq survey dump event (freq=5785 MHz noise=-96
channel_time=149 busy_time=1 tx_time=0 rx_time=0 filled=0007)
nl80211: Freq survey dump event (freq=5805 MHz noise=-96
channel_time=149 busy_time=1 tx_time=0 rx_time=0 filled=0007)
nl80211: Freq survey dump event (freq=5825 MHz noise=-96
channel_time=149 busy_time=0 tx_time=0 rx_time=0 filled=0007)
ap1: Event SURVEY (48) received
ACS: Scanning 5 / 5
ap1: nl80211: scan request
Scan requested (ret=0) - scan timeout 30 seconds
nl80211: Event message available
nl80211: Drv Event 33 (NL80211_CMD_TRIGGER_SCAN) received for ap1
ap1: nl80211: Scan trigger
ap1: Event SCAN_STARTED (49) received
Unknown event 49
random: Got 5/5 bytes from /dev/random
RTM_NEWLINK: ifi_index=8 ifname=ap1 wext ifi_family=0 ifi_flags=0x1003 ([UP])
nl80211: Event message available
nl80211: Drv Event 34 (NL80211_CMD_NEW_SCAN_RESULTS) received for ap1
ap1: nl80211: New scan results available
nl80211: Scan included frequencies: 2412 2417 2422 2427 2432 2437 2442
2447 2452 2457 2462 5180 5200 5220 5240 5260 5280 5300 5320 5500 5520
5540 5560 5580 5660 5680 5700 5720 5745 5765 5785 5805 5825
ap1: Event SCAN_RESULTS (3) received
ACS: Using survey based algorithm (acs_num_scans=5)
nl80211: Fetch survey data
nl80211: Freq survey dump event (freq=2412 MHz noise=-101
channel_time=149 busy_time=21 tx_time=0 rx_time=0 filled=0007)
nl80211: Freq survey dump event (freq=2417 MHz noise=-102
channel_time=149 busy_time=21 tx_time=0 rx_time=0 filled=0007)
nl80211: Freq survey dump event (freq=2422 MHz noise=-102
channel_time=149 busy_time=69 tx_time=0 rx_time=0 filled=0007)
nl80211: Freq survey dump event (freq=2427 MHz noise=-102
channel_time=149 busy_time=53 tx_time=0 rx_time=0 filled=0007)
nl80211: Freq survey dump event (freq=2432 MHz noise=-104
channel_time=149 busy_time=61 tx_time=0 rx_time=0 filled=0007)
nl80211: Freq survey dump event (freq=2437 MHz noise=-104
channel_time=149 busy_time=37 tx_time=0 rx_time=0 filled=0007)
nl80211: Freq survey dump event (freq=2442 MHz noise=-105
channel_time=149 busy_time=32 tx_time=0 rx_time=0 filled=0007)
nl80211: Freq survey dump event (freq=2447 MHz noise=-105
channel_time=149 busy_time=69 tx_time=0 rx_time=0 filled=0007)
nl80211: Freq survey dump event (freq=2452 MHz noise=-105
channel_time=149 busy_time=75 tx_time=0 rx_time=0 filled=0007)
nl80211: Freq survey dump event (freq=2457 MHz noise=-107
channel_time=149 busy_time=83 tx_time=0 rx_time=0 filled=0007)
nl80211: Freq survey dump event (freq=2462 MHz noise=-106
channel_time=149 busy_time=46 tx_time=0 rx_time=0 filled=0007)
nl80211: Freq survey dump event (freq=5180 MHz noise=-100
channel_time=149 busy_time=56 tx_time=0 rx_time=0 filled=0007)
nl80211: Freq survey dump event (freq=5200 MHz noise=-43
channel_time=149 busy_time=68 tx_time=0 rx_time=0 filled=0007)
nl80211: Freq survey dump event (freq=5220 MHz noise=-99
channel_time=149 busy_time=1 tx_time=0 rx_time=0 filled=0007)
nl80211: Freq survey dump event (freq=5240 MHz noise=-100
channel_time=149 busy_time=4 tx_time=0 rx_time=0 filled=0007)
nl80211: Freq survey dump event (freq=5260 MHz noise=-100
channel_time=149 busy_time=0 tx_time=0 rx_time=0 filled=0007)
nl80211: Freq survey dump event (freq=5280 MHz noise=-99
channel_time=149 busy_time=0 tx_time=0 rx_time=0 filled=0007)
nl80211: Freq survey dump event (freq=5300 MHz noise=-99
channel_time=149 busy_time=0 tx_time=0 rx_time=0 filled=0007)
nl80211: Freq survey dump event (freq=5320 MHz noise=-98
channel_time=149 busy_time=0 tx_time=0 rx_time=0 filled=0007)
nl80211: Freq survey dump event (freq=5500 MHz noise=-43
channel_time=149 busy_time=60 tx_time=0 rx_time=0 filled=0007)
nl80211: Freq survey dump event (freq=5520 MHz noise=-97
channel_time=149 busy_time=0 tx_time=0 rx_time=0 filled=0007)
nl80211: Freq survey dump event (freq=5540 MHz noise=-96
channel_time=149 busy_time=0 tx_time=0 rx_time=0 filled=0007)
nl80211: Freq survey dump event (freq=5560 MHz noise=-96
channel_time=149 busy_time=0 tx_time=0 rx_time=0 filled=0007)
nl80211: Freq survey dump event (freq=5580 MHz noise=-96
channel_time=149 busy_time=0 tx_time=0 rx_time=0 filled=0007)
nl80211: Freq survey dump event (freq=5660 MHz noise=-97
channel_time=149 busy_time=0 tx_time=0 rx_time=0 filled=0007)
nl80211: Freq survey dump event (freq=5680 MHz noise=-97
channel_time=149 busy_time=0 tx_time=0 rx_time=0 filled=0007)
nl80211: Freq survey dump event (freq=5700 MHz noise=-97
channel_time=149 busy_time=0 tx_time=0 rx_time=0 filled=0007)
nl80211: Freq survey dump event (freq=5720 MHz noise=-97
channel_time=149 busy_time=0 tx_time=0 rx_time=0 filled=0007)
nl80211: Freq survey dump event (freq=5745 MHz noise=-97
channel_time=149 busy_time=11 tx_time=0 rx_time=0 filled=0007)
nl80211: Freq survey dump event (freq=5765 MHz noise=-43
channel_time=149 busy_time=107 tx_time=0 rx_time=0 filled=0007)
nl80211: Freq survey dump event (freq=5785 MHz noise=-96
channel_time=149 busy_time=0 tx_time=0 rx_time=0 filled=0007)
nl80211: Freq survey dump event (freq=5805 MHz noise=-97
channel_time=149 busy_time=1 tx_time=0 rx_time=0 filled=0007)
nl80211: Freq survey dump event (freq=5825 MHz noise=-96
channel_time=149 busy_time=0 tx_time=0 rx_time=0 filled=0007)
ap1: Event SURVEY (48) received
ACS: Trying survey-based ACS
ACS: Unable to collect survey data
ACS: All study options have failed
Interface initialization failed
ap1: interface state ACS->DISABLED
ap1: AP-DISABLED
ACS: Possibly channel configuration is invalid, please report this
along with your config file.
ACS: Failed to start
ap1: AP-DISABLED
ap1: Deauthenticate all stations
nl80211: send_mlme - da= ff:ff:ff:ff:ff:ff noack=0 freq=0 no_cck=0
offchanok=0 wait_time=0 fc=0xc0 (WLAN_FC_STYPE_DEAUTH) nlmode=3
nl80211: send_mlme -> send_frame
nl80211: send_frame - Use bss->freq=0
nl80211: send_frame -> send_frame_cmd
nl80211: CMD_FRAME freq=0 wait=0 no_cck=0 no_ack=0 offchanok=0
CMD_FRAME - hexdump(len=26): c0 00 00 00 ff ff ff ff ff ff f0 03 8c 4a
64 fd f0 03 8c 4a 64 fd 00 00 03 00
nl80211: Frame command failed: ret=-22 (Invalid argument) (freq=0 wait=0)
hostapd_free_hapd_data: Interface ap1 wasn't started
hostapd_deinit_driver: driver=0x558e6f5cf9c0 drv_priv=0x558e70e625e0
-> hapd_deinit
nl80211: Remove monitor interface: refcount=0
nl80211: Remove beacon (ifindex=8)
netlink: Operstate: ifindex=8 linkmode=0 (kernel-control), operstate=6
(IF_OPER_UP)
nl80211: Set mode ifindex 8 iftype 2 (STATION)
nl80211: Teardown AP(ap1) - device_ap_sme=0 use_monitor=0
nl80211: Unsubscribe mgmt frames handle 0x8888dd06f86e8559 (AP teardown)
hostapd_deinit_driver:bss[0]->drv_priv=0x558e70e625e0
hostapd_cleanup_iface_partial(0x558e70e603c0)
Interface ap1 disabled
ap1: interface state DISABLED->DISABLED
hostapd_interface_deinit_free(0x558e70e603c0)
hostapd_interface_deinit_free: num_bss=1 conf->num_bss=1
hostapd_interface_deinit(0x558e70e603c0)
hostapd_bss_deinit: deinit bss ap1
hostapd_cleanup(hapd=0x558e70e616e0 (ap1))
hostapd_free_hapd_data: Interface ap1 wasn't started
hostapd_interface_deinit_free: driver=0x558e6f5cf9c0 drv_priv=(nil) ->
hapd_deinit
hostapd_interface_free(0x558e70e603c0)
hostapd_interface_free: free hapd 0x558e70e616e0
hostapd_cleanup_iface(0x558e70e603c0)
hostapd_cleanup_iface_partial(0x558e70e603c0)
hostapd_cleanup_iface: free iface=0x558e70e603c0

_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k

^ permalink raw reply	[flat|nested] 8+ messages in thread

* Re: 4.9 Kernel panic on ACS and intermittent ability to host AP
  2017-03-06 14:37 Chris Price
@ 2017-03-06 18:44 ` Hsu, Ryan
  0 siblings, 0 replies; 8+ messages in thread
From: Hsu, Ryan @ 2017-03-06 18:44 UTC (permalink / raw)
  To: ath10k

On 03/06/2017 06:37 AM, Chris Price wrote:

> This has been working for me so far (patch + new firmware).

Glad to hear that!!
Seems to be like the old firmware has some issue to support ACS, and no one really tested that before as well... :(

> The only unusual behaviour I've seen is that the 5 GHz AP seems to fail to
> start on the first try after boot, 

Could you share the logs with both driver and hostapd (-vvv), please?


Ryan

_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k

^ permalink raw reply	[flat|nested] 8+ messages in thread

* Re: 4.9 Kernel panic on ACS and intermittent ability to host AP
@ 2017-03-06 14:37 Chris Price
  2017-03-06 18:44 ` Hsu, Ryan
  0 siblings, 1 reply; 8+ messages in thread
From: Chris Price @ 2017-03-06 14:37 UTC (permalink / raw)
  To: ath10k

> You might want to apply this one - https://patchwork.kernel.org/patch/9486941/

> As mentioned, please try the new firmware again.

This has been working for me so far (patch + new firmware). The only
unusual behaviour I've seen is that the 5 GHz AP seems to fail to
start on the first try after boot, but then works thereafter.
Obviously this can be worked around. I have yet to see a panic.

_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k

^ permalink raw reply	[flat|nested] 8+ messages in thread

* Re: 4.9 Kernel panic on ACS and intermittent ability to host AP
  2017-03-01 14:02 Chris Price
@ 2017-03-04  0:13 ` Hsu, Ryan
  0 siblings, 0 replies; 8+ messages in thread
From: Hsu, Ryan @ 2017-03-04  0:13 UTC (permalink / raw)
  To: ath10k



On 03/01/2017 06:02 AM, Chris Price wrote:
>> Can you give it a try with the latest firmware - https://github.com/kvalo/ath10k-firmware.git
> I should mention that I have the 'skip_otp' directive set to 'y'. I
> tried the following both with and without this setting to no avail.
>
> The card seems to present only intermittently. When it does not
> present, I see the following in the kernel's ring buffer.
>
> # dmesg | grep ath
> [    3.460109] ath10k_pci 0000:02:00.0: pci irq msi oper_irq_mode 2
> irq_mode 0 reset_mode 0
> [    3.745235] ath10k_pci 0000:02:00.0: firmware: failed to load
> ath10k/pre-cal-pci-0000:02:00.0.bin (-2)
> [    3.745240] ath10k_pci 0000:02:00.0: Direct firmware load for
> ath10k/pre-cal-pci-0000:02:00.0.bin failed with error -2
> [    3.745249] ath10k_pci 0000:02:00.0: firmware: failed to load
> ath10k/cal-pci-0000:02:00.0.bin (-2)
> [    3.745252] ath10k_pci 0000:02:00.0: Direct firmware load for
> ath10k/cal-pci-0000:02:00.0.bin failed with error -2
> [    3.747717] ath10k_pci 0000:02:00.0: firmware: direct-loading
> firmware ath10k/QCA6174/hw3.0/firmware-5.bin
> [    3.747723] ath10k_pci 0000:02:00.0: qca6174 hw3.2 target
> 0x05030000 chip_id 0x00340aff sub 1a3b:2260
> [    3.747724] ath10k_pci 0000:02:00.0: kconfig debug 0 debugfs 0
> tracing 0 dfs 0 testmode 0
> [    3.748278] ath10k_pci 0000:02:00.0: firmware ver
> WLAN.RM.4.4-00022-QCARMSWPZ-2 api 5 features wowlan,ignore-otp crc32
> 4d458559
> [    3.814875] ath10k_pci 0000:02:00.0: firmware: direct-loading
> firmware ath10k/QCA6174/hw3.0/board-2.bin
> [    3.814880] ath10k_pci 0000:02:00.0: failed to fetch board data for
> bus=pci,bmi-chip-id=0,bmi-board-id=0 from
> ath10k/QCA6174/hw3.0/board-2.bin

In the latest firmware, there is a feature supported with latest hw but not currently present in the card you've.
So the invalid board id is read from the hw and misplaced to create the file string, then the default (incorrect) board file is loaded to your case.

You might want to apply this one - https://patchwork.kernel.org/patch/9486941/

>
> It now seems to be having some trouble setting the interface up.
>
> # hostapd /etc/hostapd/hostapd1.conf
> Configuration file: /etc/hostapd/hostapd1.conf
> Could not set interface ap1 flags (UP): Connection timed out
> nl80211: Could not set interface 'ap1' UP
> nl80211: deinit ifname=ap1 disabled_11b_rates=0
> nl80211 driver initialization failed.
> ap1: interface state UNINITIALIZED->DISABLED
> ap1: AP-DISABLED
> hostapd_free_hapd_data: Interface ap1 wasn't started
>
> # ip link set dev ap1 up
> RTNETLINK answers: Connection timed out
>
> No kernel panics, however. If I delete the new firmware, the card then
> presents on each boot. I'm using the firmware from the repo at hash
> 8d15818.
>

As mentioned, please try the new firmware again.

>
> I wasn't clear about this part - there is only one card, and I wish to
> use it in one of a few ways. Namely, I want to host 2 access points,
> or host to one access point and connect to another. `iw list` gives me
> the following.
>
> valid interface combinations:
> * #{ managed } <= 2, #{ AP, mesh point, P2P-client, P2P-GO } <= 2, #{
> P2P-device } <= 1,
>   total <= 4, #channels <= 1
> * #{ managed } <= 2, #{ P2P-client } <= 2, #{ AP, mesh point, P2P-GO }
> <= 1, #{ P2P-device } <= 1,
>   total <= 4, #channels <= 2
> * #{ managed } <= 1, #{ IBSS } <= 1,
>   total <= 2, #channels <= 1
>
> Maybe I misunderstand the output, but I would expect to be able to
> host two access points simultaneously. However I am unable to do that
> by either running a single hostapd instance, specifying both config
> files, or by running two separate instances.

I never run multiple BSSID on the QCA6174 card, not sure will the hardware/firmware support it.
but from the interface combination shows, it doesn't support that though.


Ryan
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k

^ permalink raw reply	[flat|nested] 8+ messages in thread

* Re: 4.9 Kernel panic on ACS and intermittent ability to host AP
@ 2017-03-03 14:20 Chris Price
  0 siblings, 0 replies; 8+ messages in thread
From: Chris Price @ 2017-03-03 14:20 UTC (permalink / raw)
  To: ath10k

> For the rest of the response, I'm back to using the old firmware. In
> addition, I tried not setting the skip_otp option and I seem to be
> able to get it working, so this is probably some bad advice I found
> somewhere on the web.

This seems to have been a fluke as I'm back to getting kernel panics
on a vanilla 4.9 kernel with the firmware from kernel.org. The panic
looks the same as before. Reception is still good.

I'm not sure it's relevant, but I'm connecting the card via a M.2 to
mini PCIe adapter. I've tried multiple adapters and with multiple
cards, and the adapters themselves seem to be working okay.

> * #{ managed } <= 2, #{ P2P-client } <= 2, #{ AP, mesh point, P2P-GO }
> <= 1, #{ P2P-device } <= 1,
>   total <= 4, #channels <= 2
>
> Maybe I misunderstand the output, but I would expect to be able to
> host two access points simultaneously.

I do misunderstand the output: *#{ AP, mesh point, P2P-GO } <= 1*. Derp.

_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k

^ permalink raw reply	[flat|nested] 8+ messages in thread

* Re: 4.9 Kernel panic on ACS and intermittent ability to host AP
@ 2017-03-01 14:02 Chris Price
  2017-03-04  0:13 ` Hsu, Ryan
  0 siblings, 1 reply; 8+ messages in thread
From: Chris Price @ 2017-03-01 14:02 UTC (permalink / raw)
  To: ath10k

> Is this  a regression you saw and working with other kernel version but failed with 4.9?

I've only tried this card on a custom 4.1 kernel and `iw list` does
not report it as supporting more than one channel - for our purposes,
we require 2 channels, hence the upgrade.

> Can you give it a try with the latest firmware - https://github.com/kvalo/ath10k-firmware.git

I should mention that I have the 'skip_otp' directive set to 'y'. I
tried the following both with and without this setting to no avail.

The card seems to present only intermittently. When it does not
present, I see the following in the kernel's ring buffer.

# dmesg | grep ath
[    3.460109] ath10k_pci 0000:02:00.0: pci irq msi oper_irq_mode 2
irq_mode 0 reset_mode 0
[    3.745235] ath10k_pci 0000:02:00.0: firmware: failed to load
ath10k/pre-cal-pci-0000:02:00.0.bin (-2)
[    3.745240] ath10k_pci 0000:02:00.0: Direct firmware load for
ath10k/pre-cal-pci-0000:02:00.0.bin failed with error -2
[    3.745249] ath10k_pci 0000:02:00.0: firmware: failed to load
ath10k/cal-pci-0000:02:00.0.bin (-2)
[    3.745252] ath10k_pci 0000:02:00.0: Direct firmware load for
ath10k/cal-pci-0000:02:00.0.bin failed with error -2
[    3.747717] ath10k_pci 0000:02:00.0: firmware: direct-loading
firmware ath10k/QCA6174/hw3.0/firmware-5.bin
[    3.747723] ath10k_pci 0000:02:00.0: qca6174 hw3.2 target
0x05030000 chip_id 0x00340aff sub 1a3b:2260
[    3.747724] ath10k_pci 0000:02:00.0: kconfig debug 0 debugfs 0
tracing 0 dfs 0 testmode 0
[    3.748278] ath10k_pci 0000:02:00.0: firmware ver
WLAN.RM.4.4-00022-QCARMSWPZ-2 api 5 features wowlan,ignore-otp crc32
4d458559
[    3.814875] ath10k_pci 0000:02:00.0: firmware: direct-loading
firmware ath10k/QCA6174/hw3.0/board-2.bin
[    3.814880] ath10k_pci 0000:02:00.0: failed to fetch board data for
bus=pci,bmi-chip-id=0,bmi-board-id=0 from
ath10k/QCA6174/hw3.0/board-2.bin
[    3.814996] ath10k_pci 0000:02:00.0: firmware: direct-loading
firmware ath10k/QCA6174/hw3.0/board.bin
[    3.815007] ath10k_pci 0000:02:00.0: board_file api 1 bmi_id 0:0
crc32 ed5f849a
[    5.927102] ath10k_pci 0000:02:00.0: Unknown eventid: 90118
[    8.934247] ath10k_pci 0000:02:00.0: htt version request timed out
[    8.934250] ath10k_pci 0000:02:00.0: failed to setup htt: -110
[    9.013168] ath10k_pci 0000:02:00.0: could not init core (-110)
[    9.013240] ath10k_pci 0000:02:00.0: could not probe fw (-110)

When the card does present (it seems to work randomly), I see the following.

# dmesg | grep ath
[    3.104528] ath10k_pci 0000:02:00.0: pci irq msi oper_irq_mode 2
irq_mode 0 reset_mode 0
[    3.384558] ath10k_pci 0000:02:00.0: firmware: failed to load
ath10k/pre-cal-pci-0000:02:00.0.bin (-2)
[    3.384564] ath10k_pci 0000:02:00.0: Direct firmware load for
ath10k/pre-cal-pci-0000:02:00.0.bin failed with error -2
[    3.384572] ath10k_pci 0000:02:00.0: firmware: failed to load
ath10k/cal-pci-0000:02:00.0.bin (-2)
[    3.384575] ath10k_pci 0000:02:00.0: Direct firmware load for
ath10k/cal-pci-0000:02:00.0.bin failed with error -2
[    3.387098] ath10k_pci 0000:02:00.0: firmware: direct-loading
firmware ath10k/QCA6174/hw3.0/firmware-5.bin
[    3.387105] ath10k_pci 0000:02:00.0: qca6174 hw3.2 target
0x05030000 chip_id 0x00340aff sub 1a3b:2260
[    3.387106] ath10k_pci 0000:02:00.0: kconfig debug 0 debugfs 0
tracing 0 dfs 0 testmode 0
[    3.387664] ath10k_pci 0000:02:00.0: firmware ver
WLAN.RM.4.4-00022-QCARMSWPZ-2 api 5 features wowlan,ignore-otp crc32
4d458559
[    3.454317] ath10k_pci 0000:02:00.0: firmware: direct-loading
firmware ath10k/QCA6174/hw3.0/board-2.bin
[    3.454322] ath10k_pci 0000:02:00.0: failed to fetch board data for
bus=pci,bmi-chip-id=0,bmi-board-id=0 from
ath10k/QCA6174/hw3.0/board-2.bin
[    3.454475] ath10k_pci 0000:02:00.0: firmware: direct-loading
firmware ath10k/QCA6174/hw3.0/board.bin
[    3.454486] ath10k_pci 0000:02:00.0: board_file api 1 bmi_id 0:0
crc32 ed5f849a
[    5.562906] ath10k_pci 0000:02:00.0: Unknown eventid: 90118
[    5.563521] ath10k_pci 0000:02:00.0: htt-ver 3.32 wmi-op 4 htt-op 3
cal otp max-sta 32 raw 0 hwcrypto 1
[    6.565534] ath10k_pci 0000:02:00.0: suspend timed out - target
pause event never came
[    6.644490] ath: EEPROM regdomain: 0x6a
[    6.644491] ath: EEPROM indicates we should expect a direct regpair map
[    6.644493] ath: Country alpha2 being used: 00
[    6.644494] ath: Regpair used: 0x6a

It now seems to be having some trouble setting the interface up.

# hostapd /etc/hostapd/hostapd1.conf
Configuration file: /etc/hostapd/hostapd1.conf
Could not set interface ap1 flags (UP): Connection timed out
nl80211: Could not set interface 'ap1' UP
nl80211: deinit ifname=ap1 disabled_11b_rates=0
nl80211 driver initialization failed.
ap1: interface state UNINITIALIZED->DISABLED
ap1: AP-DISABLED
hostapd_free_hapd_data: Interface ap1 wasn't started

# ip link set dev ap1 up
RTNETLINK answers: Connection timed out

No kernel panics, however. If I delete the new firmware, the card then
presents on each boot. I'm using the firmware from the repo at hash
8d15818.

> Can you give it a try if you just do the STA interface and scan?

For the rest of the response, I'm back to using the old firmware. In
addition, I tried not setting the skip_otp option and I seem to be
able to get it working, so this is probably some bad advice I found
somewhere on the web.

# ip link set dev ap1 up
# iw dev ap1 scan | grep signal
signal: -47.00 dBm
signal: -47.00 dBm
signal: -47.00 dBm
signal: -46.00 dBm
signal: -52.00 dBm
signal: -58.00 dBm
signal: -55.00 dBm
signal: -45.00 dBm
signal: -57.00 dBm
signal: -41.00 dBm
signal: -54.00 dBm
signal: -49.00 dBm
signal: -48.00 dBm
signal: -48.00 dBm
signal: -50.00 dBm
signal: -71.00 dBm
signal: -56.00 dBm
signal: -55.00 dBm
signal: -44.00 dBm
signal: -69.00 dBm
signal: -68.00 dBm
signal: -75.00 dBm
signal: -55.00 dBm
signal: -55.00 dBm
signal: -55.00 dBm
signal: -55.00 dBm
signal: -84.00 dBm
signal: -83.00 dBm
signal: -82.00 dBm
signal: -41.00 dBm
signal: -52.00 dBm
signal: -83.00 dBm
signal: -83.00 dBm
signal: -83.00 dBm
signal: -85.00 dBm
signal: -67.00 dBm
signal: -78.00 dBm
signal: -61.00 dBm
signal: -60.00 dBm
signal: -60.00 dBm
signal: -60.00 dBm
signal: -55.00 dBm
signal: -83.00 dBm
signal: -75.00 dBm
signal: -78.00 dBm
signal: -78.00 dBm
signal: -78.00 dBm

And for the first time, the ACS seems to actually work. I noticed that
I have to manually set the interface to 'up' however, though this is
probably a matter for the hostapd devs. I've been able to host the AP
repeatedly without seeing the panic, so this looks promising.

> What is the other channel you failed? what is the output of the "iw reg get" show?
> Can you share the kernel log as well?

Possibly not relevant anymore, but here you go.

# iw reg get
global
country CA: DFS-FCC
(2402 - 2472 @ 40), (N/A, 30), (N/A)
(5170 - 5250 @ 80), (N/A, 17), (N/A), AUTO-BW
(5250 - 5330 @ 80), (N/A, 24), (0 ms), DFS, AUTO-BW
(5490 - 5600 @ 80), (N/A, 24), (0 ms), DFS
(5650 - 5730 @ 80), (N/A, 24), (0 ms), DFS
(5735 - 5835 @ 80), (N/A, 30), (N/A)

The dmesg output is as above.

> Is the other card also run with ath10k? what is the combination you've?
> Are you running multiple hostapd or wpa_supplicant instance?

I wasn't clear about this part - there is only one card, and I wish to
use it in one of a few ways. Namely, I want to host 2 access points,
or host to one access point and connect to another. `iw list` gives me
the following.

valid interface combinations:
* #{ managed } <= 2, #{ AP, mesh point, P2P-client, P2P-GO } <= 2, #{
P2P-device } <= 1,
  total <= 4, #channels <= 1
* #{ managed } <= 2, #{ P2P-client } <= 2, #{ AP, mesh point, P2P-GO }
<= 1, #{ P2P-device } <= 1,
  total <= 4, #channels <= 2
* #{ managed } <= 1, #{ IBSS } <= 1,
  total <= 2, #channels <= 1

Maybe I misunderstand the output, but I would expect to be able to
host two access points simultaneously. However I am unable to do that
by either running a single hostapd instance, specifying both config
files, or by running two separate instances.

# hostapd /etc/hostapd/hostapd0.conf /etc/hostapd/hostapd1.conf
Configuration file: /etc/hostapd/hostapd0.conf
Configuration file: /etc/hostapd/hostapd1.conf
ap0: interface state UNINITIALIZED->COUNTRY_UPDATE
Using interface ap0 with hwaddr f0:03:8c:4a:64:fe and ssid "test2.4"
random: Only 15/20 bytes of strong random data available from /dev/random
random: Not enough entropy pool available for secure operations
WPA: Not enough entropy in random pool for secure operations - update
keys later when the first station connects
ap0: interface state COUNTRY_UPDATE->ENABLED
ap0: AP-ENABLED
ap1: interface state UNINITIALIZED->COUNTRY_UPDATE
ACS: Automatic channel selection started, this may take a bit
ap1: interface state COUNTRY_UPDATE->ACS
ap1: ACS-STARTED
ap1: ACS-COMPLETED freq=5220 channel=44
Using interface ap1 with hwaddr f0:03:8c:4a:64:fd and ssid "test5"
Failed to set beacon parameters
Interface initialization failed
ap1: interface state ACS->DISABLED
ap1: AP-DISABLED
ACS: Possibly channel configuration is invalid, please report this
along with your config file.
ACS: Failed to start
ap1: AP-DISABLED
hostapd_free_hapd_data: Interface ap1 wasn't started
nl80211: deinit ifname=ap1 disabled_11b_rates=0
ap1: interface state DISABLED->DISABLED
ap0: interface state ENABLED->DISABLED
ap0: AP-DISABLED
nl80211: deinit ifname=ap0 disabled_11b_rates=0
ap1: interface state DISABLED->DISABLED
ap1: AP-DISABLED
hostapd_free_hapd_data: Interface ap1 wasn't started

When I run two instances, I also see "Failed to set beacon parameters"
on whichever AP I start last.

On the other hand, I am able to simultaneously host one AP and connect
to another, so it's performing some of the functions I would expect.
As for the panic, that seems to be related to the 'skip_otp' option.

_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k

^ permalink raw reply	[flat|nested] 8+ messages in thread

* Re: 4.9 Kernel panic on ACS and intermittent ability to host AP
  2017-02-27 13:21 Chris Price
@ 2017-03-01  0:22 ` Hsu, Ryan
  0 siblings, 0 replies; 8+ messages in thread
From: Hsu, Ryan @ 2017-03-01  0:22 UTC (permalink / raw)
  To: ath10k

On 02/27/2017 05:21 AM, Chris Price wrote:
> I'm working with a QCA6174 chipset on a vanilla 4.9 kernel.
>
> I'm using the firmware from
> https://git.kernel.org/cgit/linux/kernel/git/firmware/linux-firmware.git

Is this  a regression you saw and working with other kernel version but failed with 4.9?

Can you give it a try with the latest firmware - https://github.com/kvalo/ath10k-firmware.git

cp ath10k-firmware/QCA6174/hw3.0/4.4/firmware-5.bin_WLAN.RM.4.4-00022-QCARMSWPZ-2 /lib/firmware/ath10k/QCA6174/hw3.0/firmware-5.bin


> The card presents as follows:
> root@debian:~# lspci -v
> 02:00.0 Network controller: Qualcomm Atheros QCA6174 802.11ac Wireless
> Network Adapter (rev 32)
> Subsystem: AzureWave QCA6174 802.11ac Wireless Network Adapter
> Flags: bus master, fast devsel, latency 0, IRQ 324
> Memory at df000000 (64-bit, non-prefetchable) [size=2M]
> Capabilities: [40] Power Management version 3
> Capabilities: [50] MSI: Enable+ Count=1/8 Maskable+ 64bit-
> Capabilities: [70] Express Endpoint, MSI 00
> Capabilities: [100] Advanced Error Reporting
> Capabilities: [148] Virtual Channel
> Capabilities: [168] Device Serial Number 00-00-00-00-00-00-00-00
> Capabilities: [178] Latency Tolerance Reporting
> Capabilities: [180] L1 PM Substates
> Kernel driver in use: ath10k_pci
> Kernel modules: ath10k_pci
>
> I wish to host a 5GHz AP. My hostapd.conf file is as follows.
> root@debian:~# cat /etc/hostapd/hostapd1.conf
> interface=ap1
> driver=nl80211
> hw_mode=a
> channel=0
> ieee80211d=1
> country_code=CA
> ieee80211ac=1
> ssid=test5
> auth_algs=1
> wpa=2
> wpa_key_mgmt=WPA-PSK
> rsn_pairwise=CCMP
> wpa_passphrase=testtest
>
> When I try to start the AP, I either get the following output, or a
> kernel panic.
> root@debian:~# hostapd /etc/hostapd/hostapd1.conf
> Configuration file: /etc/hostapd/hostapd1.conf
> ap1: interface state UNINITIALIZED->COUNTRY_UPDATE
> ACS: Automatic channel selection started, this may take a bit
> ap1: interface state COUNTRY_UPDATE->ACS
> ap1: ACS-STARTED
> ACS: Unable to collect survey data
> ACS: All study options have failed

It seems like the scan result is empty? I tried my device without antenna that I could see the same error.
But with good RX reception, I could see that the ACS is always working on my 4.10 setup.

Can you give it a try if you just do the STA interface and scan?

Configuration file: /etc/acs_hostapd.conf
ACS: Automatic channel selection started, this may take a bit
wlan0: interface state UNINITIALIZED->ACS
wlan0: ACS-STARTED
wlan0: ACS-COMPLETED freq=5220 channel=44
Using interface wlan0 with hwaddr 00:03:7f:91:56:96 and ssid "test-ath10k"
wlan0: interface state ACS->ENABLED
wlan0: AP-ENABLED

hostapd_free_hapd_data: Interface wlan0 wasn't started
nl80211: deinit ifname=wlan0 disabled_11b_rates=0
wlan0: interface state DISABLED->DISABLED
wlan0: interface state DISABLED->DISABLED
wlan0: AP-DISABLED
hostapd_free_hapd_data: Interface wlan0 wasn't started

> Interface initialization failed
> ap1: interface state ACS->DISABLED
> ap1: AP-DISABLED
> ACS: Possibly channel configuration is invalid, please report this
> along with your config file.
> ACS: Failed to start
> ap1: AP-DISABLED
> hostapd_free_hapd_data: Interface ap1 wasn't started
> nl80211: deinit ifname=ap1 disabled_11b_rates=0
> ap1: interface state DISABLED->DISABLED
> ap1: interface state DISABLED->DISABLED
> ap1: AP-DISABLED
> hostapd_free_hapd_data: Interface ap1 wasn't started
>
> Here (http://pasteboard.co/DnVQHOycK.jpg) is a picture of the panic I
> get otherwise.
>
> I am occasionally able to start an access point if I pin the channel
> to 36. Otherwise, I get the following.

What is the other channel you failed? what is the output of the "iw reg get" show?
Can you share the kernel log as well?

> root@debian:~# hostapd /etc/hostapd/hostapd1.conf
> Configuration file: /etc/hostapd/hostapd1.conf
> ap1: interface state UNINITIALIZED->COUNTRY_UPDATE
> ap1: IEEE 802.11 Configured channel (36) not found from the channel
> list of current mode (2) IEEE 802.11a
> ap1: IEEE 802.11 Hardware does not support configured channel
> Could not select hw_mode and channel. (-3)
> ap1: interface state COUNTRY_UPDATE->DISABLED
> ap1: AP-DISABLED
> ap1: interface state DISABLED->DISABLED
> ap1: AP-DISABLED
> hostapd_free_hapd_data: Interface ap1 wasn't started
> nl80211: deinit ifname=ap1 disabled_11b_rates=0
>
> This latter problem, I suspect, is somehow related to interface
> combinations, because I have never seen the card work when I create
> multiple interfaces.

Is the other card also run with ath10k? what is the combination you've?
Are you running multiple hostapd or wpa_supplicant instance?


Ryan

_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k

^ permalink raw reply	[flat|nested] 8+ messages in thread

* 4.9 Kernel panic on ACS and intermittent ability to host AP
@ 2017-02-27 13:21 Chris Price
  2017-03-01  0:22 ` Hsu, Ryan
  0 siblings, 1 reply; 8+ messages in thread
From: Chris Price @ 2017-02-27 13:21 UTC (permalink / raw)
  To: ath10k

I'm working with a QCA6174 chipset on a vanilla 4.9 kernel.

I'm using the firmware from
https://git.kernel.org/cgit/linux/kernel/git/firmware/linux-firmware.git

The card presents as follows:
root@debian:~# lspci -v
02:00.0 Network controller: Qualcomm Atheros QCA6174 802.11ac Wireless
Network Adapter (rev 32)
Subsystem: AzureWave QCA6174 802.11ac Wireless Network Adapter
Flags: bus master, fast devsel, latency 0, IRQ 324
Memory at df000000 (64-bit, non-prefetchable) [size=2M]
Capabilities: [40] Power Management version 3
Capabilities: [50] MSI: Enable+ Count=1/8 Maskable+ 64bit-
Capabilities: [70] Express Endpoint, MSI 00
Capabilities: [100] Advanced Error Reporting
Capabilities: [148] Virtual Channel
Capabilities: [168] Device Serial Number 00-00-00-00-00-00-00-00
Capabilities: [178] Latency Tolerance Reporting
Capabilities: [180] L1 PM Substates
Kernel driver in use: ath10k_pci
Kernel modules: ath10k_pci

I wish to host a 5GHz AP. My hostapd.conf file is as follows.
root@debian:~# cat /etc/hostapd/hostapd1.conf
interface=ap1
driver=nl80211
hw_mode=a
channel=0
ieee80211d=1
country_code=CA
ieee80211ac=1
ssid=test5
auth_algs=1
wpa=2
wpa_key_mgmt=WPA-PSK
rsn_pairwise=CCMP
wpa_passphrase=testtest

When I try to start the AP, I either get the following output, or a
kernel panic.
root@debian:~# hostapd /etc/hostapd/hostapd1.conf
Configuration file: /etc/hostapd/hostapd1.conf
ap1: interface state UNINITIALIZED->COUNTRY_UPDATE
ACS: Automatic channel selection started, this may take a bit
ap1: interface state COUNTRY_UPDATE->ACS
ap1: ACS-STARTED
ACS: Unable to collect survey data
ACS: All study options have failed
Interface initialization failed
ap1: interface state ACS->DISABLED
ap1: AP-DISABLED
ACS: Possibly channel configuration is invalid, please report this
along with your config file.
ACS: Failed to start
ap1: AP-DISABLED
hostapd_free_hapd_data: Interface ap1 wasn't started
nl80211: deinit ifname=ap1 disabled_11b_rates=0
ap1: interface state DISABLED->DISABLED
ap1: interface state DISABLED->DISABLED
ap1: AP-DISABLED
hostapd_free_hapd_data: Interface ap1 wasn't started

Here (http://pasteboard.co/DnVQHOycK.jpg) is a picture of the panic I
get otherwise.

I am occasionally able to start an access point if I pin the channel
to 36. Otherwise, I get the following.
root@debian:~# hostapd /etc/hostapd/hostapd1.conf
Configuration file: /etc/hostapd/hostapd1.conf
ap1: interface state UNINITIALIZED->COUNTRY_UPDATE
ap1: IEEE 802.11 Configured channel (36) not found from the channel
list of current mode (2) IEEE 802.11a
ap1: IEEE 802.11 Hardware does not support configured channel
Could not select hw_mode and channel. (-3)
ap1: interface state COUNTRY_UPDATE->DISABLED
ap1: AP-DISABLED
ap1: interface state DISABLED->DISABLED
ap1: AP-DISABLED
hostapd_free_hapd_data: Interface ap1 wasn't started
nl80211: deinit ifname=ap1 disabled_11b_rates=0

This latter problem, I suspect, is somehow related to interface
combinations, because I have never seen the card work when I create
multiple interfaces.

Any help would be appreciated.

_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k

^ permalink raw reply	[flat|nested] 8+ messages in thread

end of thread, other threads:[~2017-03-07 12:16 UTC | newest]

Thread overview: 8+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2017-03-07 12:15 4.9 Kernel panic on ACS and intermittent ability to host AP Chris Price
  -- strict thread matches above, loose matches on Subject: below --
2017-03-06 14:37 Chris Price
2017-03-06 18:44 ` Hsu, Ryan
2017-03-03 14:20 Chris Price
2017-03-01 14:02 Chris Price
2017-03-04  0:13 ` Hsu, Ryan
2017-02-27 13:21 Chris Price
2017-03-01  0:22 ` Hsu, Ryan

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.