* Re: Configuring WiFi6 in hostapd
[not found] ` <CAD_iCC8StVW7Yh9f8fm2Da7LcN6LQzR=ssp+1E8-=YYCM-5tOQ@mail.gmail.com>
@ 2020-09-11 15:07 ` Krishna Chaitanya
2020-09-11 17:10 ` Johannes Berg
0 siblings, 1 reply; 9+ messages in thread
From: Krishna Chaitanya @ 2020-09-11 15:07 UTC (permalink / raw)
To: Sugandh Huthanahally Mohan, linux-wireless, Emmanuel Grumbach
Cc: Cedric Izoard, Hostap
On Fri, Sep 11, 2020 at 8:25 PM Sugandh Huthanahally Mohan
<sugandhgowda@gmail.com> wrote:
>
> On Fri, Sep 11, 2020 at 7:33 PM Sugandh Huthanahally Mohan
> <sugandhgowda@gmail.com> wrote:
> >
> > On Wed, Sep 9, 2020 at 2:18 AM Sugandh Huthanahally Mohan
> > <sugandhgowda at gmail.com> wrote:
> > >
> > > On Wed, Sep 9, 2020 at 12:27 AM Sugandh Huthanahally Mohan
> > > <sugandhgowda at gmail.com> wrote:
> > > > >
> > > > > I have captured connection between a WiFi6 AP and a WiFi6 STA in wireshark.
> > > > >I have attached a wireshark pcap file.
> > > > > I could see HE capabilities exchange in Association request and response.
> > > > Yes, this looks fine to me except for VHT IEs in the probe and
> > > > association response in 2.4GHz.
> > > > Maybe this is what is confusing, can you please disable ieee80211ac=0
> > > > in the hostapd.conf and try?
> > > I disabled iee80211ac and I am not seeing VHT capabilities in Association
> > > frames but the data rate remains the same.I am attaching wireshark capture.
> > okay, thanks.
> > > > The iw phy output is below. I couldn't see HE connection in this output.
> > > >
> > > > $iw dev wlp3s0 link
> > > > Connected to 8c:c6:81:69:86:65 (on wlp3s0)
> > > > SSID: WiFi_AX200
> > > > freq: 2437
> > > > RX: 27838 bytes (199 packets)
> > > > TX: 13319 bytes (97 packets)
> > > > signal: -34 dBm
> > > > rx bitrate: 26.0 MBit/s MCS 3
> > > > tx bitrate: 2.0 MBit/s
> > > >
> > > > bss flags: short-slot-time
> > > > dtim period: 2
> > > > beacon int: 100
> > > >
> > > > > The link doesn't show any specific details related to HE other than
> > > > > the MCS which can vary, try running
> > > > > an iperf to see HE MCSes in a clean channel.
> > >
> > > Could you please explain what this means.
> > > I want to know what clean channel means and where actually I can see HE MCSes.
> >
> > > Sure. The link command doesn't printout any in capability information explicitly
> > > except for the MCS details. And figuring out the mode of connection (11n/11ax)
> > > from the MCS is tricky as the MCS varies across depending on the rate
> > > control algorithm
> > > (for iwlwifi: hardware). So, I was suggesting to use iperf (the more
> > > data you pass, more
> > > chance of the rate control algo to go to higher MCSes) and also by
> > > "clean channels" I was
> > > referring to quieter channels where there are no other BSSes or no
> > > other traffic.
> > Okay. I tried running iperf for long period of time between AP and STA
> > (injected incremental traffic ,like running more parallel connections between
> > iperf server and iperf client ) and I did not see any changes in MCSes.
> > It remained the same throughout the time I ran the iperf test.
> > Okay, this was to rule out any rate control issues but as it turned out to be
> > a functional issue, we can ignore this for now.
> Okay
>
> >
> > > >But, before we go into debugging data path, I still don't understand
> > > >why wpa_supplicant
> > > >isn't saying it is a HE association?
> >
> > > > Ah, After staring at the code and using blame, a crucial fix missed
> > > > out hostap-2.9 windows,
> > > > the fix was to properly validate the HE capabilities, I was looking at
> > > > the latest cod and
> > > > everything looked fine, hence took time.
> >
> > > > hostap_2_9-> 7th August
> > > >0497e4148197fb8fdf92b5c901ce06df1bfa548c ->13th August
> > > >
> > > > Please use the latest HEAD of hostap.git, you need to compile it
> > > > manually and try the
> > > > test and let me know how it goes. (make sure all proper configs are enabled)
> > > >
> > > > Previously I was using hostapd version 2.9 and with this version I could
> > > >connect STA's to AP with the hostapd.conf which I had shared earlier.
> > >
> > > Now I pulled the latest HEAD and compiled it with proper flags enabled.
> > > When I run hostapd now , the WiFi6 STA's(AX200) are not able to establish
> > > solid connection to AP. In other words, I could see they are connecting but
> > > hostapd is deleting the station. Below are the log pertaining to that
> > >
> > > nl80211: NL80211_CMD_SET_STATION result: -5 (Input/output error)
> > > wlp3s0: STA 8c:c6:81:69:ac:80 IEEE 802.11: Could not set STA to kernel driver
> > > nl80211: sta_remove -> DEL_STATION wlp3s0 8c:c6:81:69:ac:80 --> 0 (Success)
>
> > First of all, the original problem is resolved, I can see he_capabs
> > now, but unfortunately
> > , the problem moved to the kernel :). There are many reasons why the
> > mac80211/iwlwifi
> > might return EIO, Could you please also share the dmesg as well when
> >this happens?
>
> Then, the hostapd version 2.9 may not be establishing a HE connection
> but the latest HEAD I used is trying to establish one.
Yes, that was the hypothesis and it is now confirmed.
>
> dmesg is below:
>
> $dmesg
<snip...>
> [ 217.159617] RIP: 0033:0x7f8e708f55b7
> [ 217.159619] Code: 64 89 02 48 c7 c0 ff ff ff ff eb bb 0f 1f 80 00
> 00 00 00 f3 0f 1e fa 64 8b 04 25 18 00 00 00 85 c0 75 10 b8 2e 00 00
> 00 0f 05 <48> 3d 00 f0 ff ff 77 51 c3 48 83 ec 28 89 54 24 1c 48 89 74
> 24 10
> [ 217.159619] RSP: 002b:00007ffffed54048 EFLAGS: 00000246 ORIG_RAX:
> 000000000000002e
> [ 217.159621] RAX: ffffffffffffffda RBX: 0000557df150a5e0 RCX: 00007f8e708f55b7
> [ 217.159621] RDX: 0000000000000000 RSI: 00007ffffed54080 RDI: 0000000000000005
> [ 217.159622] RBP: 0000557df1514bd0 R08: 0000000000000004 R09: 0000000000000000
> [ 217.159622] R10: 00007ffffed54164 R11: 0000000000000246 R12: 0000557df1508aa0
> [ 217.159623] R13: 00007ffffed54080 R14: 0000000000000000 R15: 0000000000000000
> [ 217.824610] iwlwifi 0000:03:00.0: Applying debug destination EXTERNAL_DRAM
> [ 217.993230] iwlwifi 0000:03:00.0: FW already configured (0) - re-configuring
> [ 228.315161] iwlwifi 0000:03:00.0: Microcode SW error detected.
> Restarting 0x0.
> [ 228.315276] iwlwifi 0000:03:00.0: Start IWL Error Log Dump:
> [ 228.315281] iwlwifi 0000:03:00.0: Status: 0x00000040, count: 6
> [ 228.315285] iwlwifi 0000:03:00.0: Loaded firmware version: 48.4fa0041f.0
> [ 228.315290] iwlwifi 0000:03:00.0: 0x00002078 | ADVANCED_SYSASSERT
> [ 228.315294] iwlwifi 0000:03:00.0: 0x00A0A200 | trm_hw_status0
> [ 228.315297] iwlwifi 0000:03:00.0: 0x00000000 | trm_hw_status1
> [ 228.315300] iwlwifi 0000:03:00.0: 0x004F8E3C | branchlink2
> [ 228.315303] iwlwifi 0000:03:00.0: 0x004E4FF4 | interruptlink1
> [ 228.315307] iwlwifi 0000:03:00.0: 0x004E4FF4 | interruptlink2
> [ 228.315310] iwlwifi 0000:03:00.0: 0x07000101 | data1
> [ 228.315313] iwlwifi 0000:03:00.0: 0x48308403 | data2
> [ 228.315316] iwlwifi 0000:03:00.0: 0x00000005 | data3
> [ 228.315319] iwlwifi 0000:03:00.0: 0x00000000 | beacon time
> [ 228.315322] iwlwifi 0000:03:00.0: 0x009FA807 | tsf low
> [ 228.315326] iwlwifi 0000:03:00.0: 0x00000000 | tsf hi
> [ 228.315329] iwlwifi 0000:03:00.0: 0x00000000 | time gp1
> [ 228.315332] iwlwifi 0000:03:00.0: 0x00A01170 | time gp2
> [ 228.315335] iwlwifi 0000:03:00.0: 0x00000001 | uCode revision type
> [ 228.315338] iwlwifi 0000:03:00.0: 0x00000030 | uCode version major
> [ 228.315342] iwlwifi 0000:03:00.0: 0x4FA0041F | uCode version minor
> [ 228.315345] iwlwifi 0000:03:00.0: 0x00000340 | hw version
> [ 228.315348] iwlwifi 0000:03:00.0: 0x00489000 | board version
> [ 228.315351] iwlwifi 0000:03:00.0: 0x802CFC09 | hcmd
> [ 228.315354] iwlwifi 0000:03:00.0: 0x24020000 | isr0
> [ 228.315357] iwlwifi 0000:03:00.0: 0x61000000 | isr1
> [ 228.315360] iwlwifi 0000:03:00.0: 0x18F00002 | isr2
> [ 228.315363] iwlwifi 0000:03:00.0: 0x00C1FFCC | isr3
> [ 228.315366] iwlwifi 0000:03:00.0: 0x00000000 | isr4
> [ 228.315369] iwlwifi 0000:03:00.0: 0x0405001C | last cmd Id
> [ 228.315372] iwlwifi 0000:03:00.0: 0x00016D22 | wait_event
> [ 228.315375] iwlwifi 0000:03:00.0: 0x00000000 | l2p_control
> [ 228.315379] iwlwifi 0000:03:00.0: 0x00018034 | l2p_duration
> [ 228.315382] iwlwifi 0000:03:00.0: 0x0000003F | l2p_mhvalid
> [ 228.315385] iwlwifi 0000:03:00.0: 0x00CB0000 | l2p_addr_match
> [ 228.315388] iwlwifi 0000:03:00.0: 0x00000009 | lmpm_pmg_sel
> [ 228.315391] iwlwifi 0000:03:00.0: 0x00000000 | timestamp
> [ 228.315394] iwlwifi 0000:03:00.0: 0x00004894 | flow_handler
> [ 228.315452] iwlwifi 0000:03:00.0: Start IWL Error Log Dump:
> [ 228.315455] iwlwifi 0000:03:00.0: Status: 0x00000040, count: 7
> [ 228.315459] iwlwifi 0000:03:00.0: 0x20000070 | NMI_INTERRUPT_LMAC_FATAL
> [ 228.315462] iwlwifi 0000:03:00.0: 0x00000000 | umac branchlink1
> [ 228.315465] iwlwifi 0000:03:00.0: 0xC008CC3C | umac branchlink2
> [ 228.315468] iwlwifi 0000:03:00.0: 0x8048D0E6 | umac interruptlink1
> [ 228.315472] iwlwifi 0000:03:00.0: 0x8048D0E6 | umac interruptlink2
> [ 228.315475] iwlwifi 0000:03:00.0: 0x00000400 | umac data1
> [ 228.315478] iwlwifi 0000:03:00.0: 0x8048D0E6 | umac data2
> [ 228.315481] iwlwifi 0000:03:00.0: 0x00000000 | umac data3
> [ 228.315484] iwlwifi 0000:03:00.0: 0x00000030 | umac major
> [ 228.315487] iwlwifi 0000:03:00.0: 0x4FA0041F | umac minor
> [ 228.315490] iwlwifi 0000:03:00.0: 0x00A01180 | frame pointer
> [ 228.315493] iwlwifi 0000:03:00.0: 0xC0886284 | stack pointer
> [ 228.315496] iwlwifi 0000:03:00.0: 0x003B050F | last host cmd
> [ 228.315499] iwlwifi 0000:03:00.0: 0x00000000 | isr status reg
> [ 228.315530] iwlwifi 0000:03:00.0: Fseq Registers:
> [ 228.315543] iwlwifi 0000:03:00.0: 0xE0000101 | FSEQ_ERROR_CODE
> [ 228.315555] iwlwifi 0000:03:00.0: 0x00290011 | FSEQ_TOP_INIT_VERSION
> [ 228.315568] iwlwifi 0000:03:00.0: 0x80050008 | FSEQ_CNVIO_INIT_VERSION
> [ 228.315581] iwlwifi 0000:03:00.0: 0x0000A503 | FSEQ_OTP_VERSION
> [ 228.315594] iwlwifi 0000:03:00.0: 0x80000003 | FSEQ_TOP_CONTENT_VERSION
> [ 228.315606] iwlwifi 0000:03:00.0: 0x4552414E | FSEQ_ALIVE_TOKEN
> [ 228.315619] iwlwifi 0000:03:00.0: 0x00100530 | FSEQ_CNVI_ID
> [ 228.315632] iwlwifi 0000:03:00.0: 0x00000532 | FSEQ_CNVR_ID
> [ 228.315644] iwlwifi 0000:03:00.0: 0x00100530 | CNVI_AUX_MISC_CHIP
> [ 228.315659] iwlwifi 0000:03:00.0: 0x00000532 | CNVR_AUX_MISC_CHIP
> [ 228.315674] iwlwifi 0000:03:00.0: 0x05B0905B |
> CNVR_SCU_SD_REGS_SD_REG_DIG_DCDC_VTRIM
> [ 228.315689] iwlwifi 0000:03:00.0: 0x0000025B |
> CNVR_SCU_SD_REGS_SD_REG_ACTIVE_VDIG_MIRROR
> [ 228.315833] iwlwifi 0000:03:00.0: Collecting data: trigger 2 fired.
> [ 228.315842] ieee80211 phy0: Hardware restart was requested
> [ 228.315867] iwlwifi 0000:03:00.0: FW error in SYNC CMD ADD_STA
> [ 228.315877] CPU: 2 PID: 3471 Comm: hostapd Tainted: P OE
> 5.4.0-42-generic #46-Ubuntu
> [ 228.315879] Hardware name: LENOVO 20FXS1FA00/20FXS1FA00, BIOS
> R07ET91W (2.31 ) 12/11/2019
> [ 228.315880] Call Trace:
> [ 228.315893] dump_stack+0x6d/0x9a
> [ 228.315918] iwl_trans_pcie_gen2_send_hcmd+0x3de/0x3f0 [iwlwifi]
> [ 228.315924] ? wait_woken+0x80/0x80
> [ 228.315944] iwl_trans_send_cmd+0x55/0xc0 [iwlwifi]
> [ 228.315965] iwl_mvm_send_cmd_status+0x38/0xd0 [iwlmvm]
> [ 228.315983] iwl_mvm_send_cmd_pdu_status+0x53/0x70 [iwlmvm]
> [ 228.316002] iwl_mvm_sta_send_to_fw+0x1ca/0x310 [iwlmvm]
> [ 228.316017] iwl_mvm_mac_sta_state+0x3e1/0x6e0 [iwlmvm]
> [ 228.316023] ? __switch_to_asm+0x40/0x70
> [ 228.316060] drv_sta_state+0x96/0x3f0 [mac80211]
> [ 228.316094] sta_info_move_state+0x276/0x370 [mac80211]
> [ 228.316134] sta_apply_auth_flags.isra.0+0x73/0x140 [mac80211]
> [ 228.316170] sta_apply_parameters+0x34c/0x690 [mac80211]
> [ 228.316204] ieee80211_change_station+0x130/0x340 [mac80211]
> [ 228.316244] ? nl80211_parse_sta_wme.isra.0+0x50/0xc0 [cfg80211]
> [ 228.316278] nl80211_set_station+0x365/0x440 [cfg80211]
> [ 228.316286] genl_family_rcv_msg+0x1b9/0x470
> [ 228.316291] genl_rcv_msg+0x4c/0xa0
> [ 228.316301] ? _cond_resched+0x19/0x30
> [ 228.316304] ? genl_family_rcv_msg+0x470/0x470
> [ 228.316307] netlink_rcv_skb+0x50/0x120
> [ 228.316311] genl_rcv+0x29/0x40
> [ 228.316314] netlink_unicast+0x187/0x220
> [ 228.316317] netlink_sendmsg+0x222/0x3e0
> [ 228.316323] sock_sendmsg+0x65/0x70
> [ 228.316326] ____sys_sendmsg+0x212/0x280
> [ 228.316331] ___sys_sendmsg+0x88/0xd0
> [ 228.316336] ? __wake_up_common_lock+0x8a/0xc0
> [ 228.316340] ? __wake_up+0x13/0x20
> [ 228.316346] ? tty_write_unlock+0x31/0x40
> [ 228.316352] ? __cgroup_bpf_run_filter_setsockopt+0xae/0x2c0
> [ 228.316354] ? _cond_resched+0x19/0x30
> [ 228.316359] ? aa_sk_perm+0x43/0x170
> [ 228.316364] __sys_sendmsg+0x5c/0xa0
> [ 228.316369] __x64_sys_sendmsg+0x1f/0x30
> [ 228.316375] do_syscall_64+0x57/0x190
> [ 228.316379] entry_SYSCALL_64_after_hwframe+0x44/0xa9
> [ 228.316383] RIP: 0033:0x7f8e708f55b7
> [ 228.316388] Code: 64 89 02 48 c7 c0 ff ff ff ff eb bb 0f 1f 80 00
> 00 00 00 f3 0f 1e fa 64 8b 04 25 18 00 00 00 85 c0 75 10 b8 2e 00 00
> 00 0f 05 <48> 3d 00 f0 ff ff 77 51 c3 48 83 ec 28 89 54 24 1c 48 89 74
> 24 10
> [ 228.316390] RSP: 002b:00007ffffed54048 EFLAGS: 00000246 ORIG_RAX:
> 000000000000002e
> [ 228.316394] RAX: ffffffffffffffda RBX: 0000557df150a5e0 RCX: 00007f8e708f55b7
> [ 228.316396] RDX: 0000000000000000 RSI: 00007ffffed54080 RDI: 0000000000000005
> [ 228.316398] RBP: 0000557df1514bd0 R08: 0000000000000004 R09: 0000000000000000
> [ 228.316399] R10: 00007ffffed54164 R11: 0000000000000246 R12: 0000557df1508aa0
> [ 228.316401] R13: 00007ffffed54080 R14: 0000000000000000 R15: 0000000000000000
> [ 228.966456] iwlwifi 0000:03:00.0: Failed to trigger RX queues sync (-5)
> [ 228.992214] iwlwifi 0000:03:00.0: Applying debug destination EXTERNAL_DRAM
> [ 229.161947] iwlwifi 0000:03:00.0: FW already configured (0) - re-configuring
Urgh...a LMAC firmware crash in the sta_add. I will leave this to the
Intel guys.
+ Linux Wireless
I am still not sure if this a genuine issue or just an
incompatibility, I would suggest you to
switch to iwlwifi-next.git with corresponding latest iwlwifi firmware.
>
>
>
> >
> > Also I could see multiple Association requests and responses. On the
> > other hand I am
> > able to connect WiFi4(802.11n) STA's to AP. I am attaching the hostapd logs
> > with debugs enabled and also wireshark captures.
> This is in line with the logs, as Set-STA is failing association
> request will not go through.
>
> >
> > > > On Wed, Sep 2, 2020 at 3:39 PM Krishna Chaitanya
> > > > <chaitanya.mgit at gmail.com> wrote:
> > > > >
> > > > > On Wed, Sep 2, 2020 at 6:38 PM Sugandh Huthanahally Mohan
> > > > > <sugandhgowda at gmail.com> wrote:
> > > > > >
> > > > > > On Wed, Sep 2, 2020 at 3:16 PM Sugandh Huthanahally Mohan
> > > > > > <sugandhgowda at gmail.com> wrote:
> > > > > > >
> > > > > > > On Tue, Sep 1, 2020 at 10:09 PM Krishna Chaitanya
> > > > > > > <chaitanya.mgit at gmail.com> wrote:
> > > > > > > >
> > > > > > > >
> > > > > > > > Well, not necessarily, but hostap side it looks fine, so,
> > > > > > > > we need to see why the STA isn't responding well, probably a
> > > > > > > > different draft implementation. At the very least we should start
> > > > > > > > with a sniffer capture of the association b/w the stations to check
> > > > > > > > the IEs.
> > > > > > >
> > > > > > > I am using wpa_supplicant in STA to connect to AP.
> > > > > > > I am attaching hostapd logs and wpa_supplicant logs.
> > > > > > > I am observing that the STA is connecting and disconnecting when
> > > > > > > I try to connect STA to AP.
> > > > > > I guess this is a new STA with wpa_supplicant, right? Is it also AX200 based
> > > > > > chipset? In the STA mode, the kernel adds the HE IEs (either mac80211
> > > > > > or the driver),
> > > > > > so, but interestingly in your previous dmesg, I don't see any mac80211 logs.
> > > > > >
> > > > > > So, need dmesg logs that capture the connection (look for mac80211 logs).
> > > > > > >
> > > > > > > On Tue, Sep 1, 2020 at 10:09 PM Krishna Chaitanya
> > > > > > > <chaitanya.mgit at gmail.com> wrote:
> > > > > > > >
> > > > > > > > On Wed, Sep 2, 2020 at 1:23 AM Sugandh Huthanahally Mohan
> > > > > > > > <sugandhgowda at gmail.com> wrote:
> > > > > > > > >
> > > > > > > > > Hi Krishna,
> > > > > > > > >
> > > > > > > > > Currently I am not running wpa_supplicant.
> > > > > > > > > Is it necessary for hostapd?
> > > > > > > >
> > > > > > > > Well, not necessarily, but hostap side it looks fine, so,
> > > > > > > > we need to see why the STA isn't responding well, probably a
> > > > > > > > different draft implementation. At the very least we should start
> > > > > > > > with a sniffer capture of the association b/w the stations to check
> > > > > > > > the IEs.
> > > > > >
> > > > > > Yes this is a new STA connecting AP with wpa_supplicant.
> > > > > > It is also an AX200.
> > > > > > I don’t see mac80211 logs on the STA dmesg.
> > > > > > I am attaching dmesg of the station.
> > > > >
> > > > > These are from mac80211:
> > > > > [ 152.255545] wlp3s0: authenticate with 8c:c6:81:69:86:65
> > > > > [ 152.258347] wlp3s0: send auth to 8c:c6:81:69:86:65 (try 1/3)
> > > > > [ 152.283971] wlp3s0: authenticated
> > > > > [ 152.286624] wlp3s0: associate with 8c:c6:81:69:86:65 (try 1/3)
> > > > > [ 152.293456] wlp3s0: RX AssocResp from 8c:c6:81:69:86:65
> > > > > (capab=0x411 status=0 aid=1)
> > > > > [ 152.299672] wlp3s0: associated
> > > > > [ 152.364843] IPv6: ADDRCONF(NETDEV_CHANGE): wlp3s0: link becomes ready
> > > > >
> > > > > I was hoping to see some prints disabling HE, but looks fine. So,
> > > > > still, nothing from the logs
> > > > > to say why HE is disabled in the STA (why it isn't sending HE IEs in
> > > > > assoc resp).
> > > > >
> > > > > Only Sniffer should tell us without resorting to Whitebox debug.
> > > > > >
> > > > > > On Wed, Sep 2, 2020 at 1:26 PM Krishna Chaitanya
> > > > > > <chaitanya.mgit at gmail.com> wrote:
> > > > > > >
> > > > > > > On Wed, Sep 2, 2020 at 3:16 PM Sugandh Huthanahally Mohan
> > > > > > > <sugandhgowda at gmail.com> wrote:
> > > > > > > >
> > > > > > > > On Tue, Sep 1, 2020 at 10:09 PM Krishna Chaitanya
> > > > > > > > <chaitanya.mgit at gmail.com> wrote:
> > > > > > > > >
> > > > > > > > >
> > > > > > > > > Well, not necessarily, but hostap side it looks fine, so,
> > > > > > > > > we need to see why the STA isn't responding well, probably a
> > > > > > > > > different draft implementation. At the very least we should start
> > > > > > > > > with a sniffer capture of the association b/w the stations to check
> > > > > > > > > the IEs.
> > > > > > > >
> > > > > > > > I am using wpa_supplicant in STA to connect to AP.
> > > > > > > > I am attaching hostapd logs and wpa_supplicant logs.
> > > > > > > > I am observing that the STA is connecting and disconnecting when
> > > > > > > > I try to connect STA to AP.
> > > > > > > I guess this is a new STA with wpa_supplicant, right? Is it also AX200 based
> > > > > > > chipset? In the STA mode, the kernel adds the HE IEs (either mac80211
> > > > > > > or the driver),
> > > > > > > so, but interestingly in your previous dmesg, I don't see any mac80211 logs.
> > > > > > >
> > > > > > > So, need dmesg logs that capture the connection (look for mac80211 logs).
> > > > > > > >
> > > > > > > > On Tue, Sep 1, 2020 at 10:09 PM Krishna Chaitanya
> > > > > > > > <chaitanya.mgit at gmail.com> wrote:
> > > > > > > > >
> > > > > > > > > On Wed, Sep 2, 2020 at 1:23 AM Sugandh Huthanahally Mohan
> > > > > > > > > <sugandhgowda at gmail.com> wrote:
> > > > > > > > > >
> > > > > > > > > > Hi Krishna,
> > > > > > > > > >
> > > > > > > > > > Currently I am not running wpa_supplicant.
> > > > > > > > > > Is it necessary for hostapd?
> > > > > > > > >
> > > > > > > > > Well, not necessarily, but hostap side it looks fine, so,
> > > > > > > > > we need to see why the STA isn't responding well, probably a
> > > > > > > > > different draft implementation. At the very least we should start
> > > > > > > > > with a sniffer capture of the association b/w the stations to check
> > > > > > > > > the IEs.
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > --
> > > > > > > Thanks,
> > > > > > > Regards,
> > > > > > > Chaitanya T K.
> > > > >
> > > > >
> > > > >
> > > > > --
> > > > > Thanks,
> > > > > Regards,
> > > > > Chaitanya T K.
> > >
> > >
> > > On Tue, Sep 8, 2020 at 9:55 PM Krishna Chaitanya
> > > <chaitanya.mgit at gmail.com> wrote:
> > > >
> > > > On Wed, Sep 9, 2020 at 12:27 AM Sugandh Huthanahally Mohan
> > > > <sugandhgowda at gmail.com> wrote:
> > > > >
> > > > > I have captured connection between a WiFi6 AP and a WiFi6 STA in wireshark.
> > > > > I have attached a wireshark pcap file.
> > > > > I could see HE capabilities exchange in Association request and response.
> > > > Yes, this looks fine to me except for VHT IEs in the probe and
> > > > association response in 2.4GHz.
> > > > Maybe this is what is confusing, can you please disable ieee80211ac=0
> > > > in the hostapd.conf and try?
> > > >
> > > > > The iw phy output is below. I couldn't see HE connection in this output.
> > > > >
> > > > > $iw dev wlp3s0 link
> > > > > Connected to 8c:c6:81:69:86:65 (on wlp3s0)
> > > > > SSID: WiFi_AX200
> > > > > freq: 2437
> > > > > RX: 27838 bytes (199 packets)
> > > > > TX: 13319 bytes (97 packets)
> > > > > signal: -34 dBm
> > > > > rx bitrate: 26.0 MBit/s MCS 3
> > > > > tx bitrate: 2.0 MBit/s
> > > > >
> > > > > bss flags: short-slot-time
> > > > > dtim period: 2
> > > > > beacon int: 100
> > > > >
> > > > The link doesn't show any specific details related to HE other than
> > > > the MCS which can vary, try running
> > > > an iperf to see HE MCSes in a clean channel.
> > > > >
> > > > > On Wed, Sep 2, 2020 at 3:39 PM Krishna Chaitanya
> > > > > <chaitanya.mgit at gmail.com> wrote:
> > > > > >
> > > > > > On Wed, Sep 2, 2020 at 6:38 PM Sugandh Huthanahally Mohan
> > > > > > <sugandhgowda at gmail.com> wrote:
> > > > > > >
> > > > > > > On Wed, Sep 2, 2020 at 3:16 PM Sugandh Huthanahally Mohan
> > > > > > > <sugandhgowda at gmail.com> wrote:
> > > > > > > >
> > > > > > > > On Tue, Sep 1, 2020 at 10:09 PM Krishna Chaitanya
> > > > > > > > <chaitanya.mgit at gmail.com> wrote:
> > > > > > > > >
> > > > > > > > >
> > > > > > > > > Well, not necessarily, but hostap side it looks fine, so,
> > > > > > > > > we need to see why the STA isn't responding well, probably a
> > > > > > > > > different draft implementation. At the very least we should start
> > > > > > > > > with a sniffer capture of the association b/w the stations to check
> > > > > > > > > the IEs.
> > > > > > > >
> > > > > > > > I am using wpa_supplicant in STA to connect to AP.
> > > > > > > > I am attaching hostapd logs and wpa_supplicant logs.
> > > > > > > > I am observing that the STA is connecting and disconnecting when
> > > > > > > > I try to connect STA to AP.
> > > > > > > I guess this is a new STA with wpa_supplicant, right? Is it also AX200 based
> > > > > > > chipset? In the STA mode, the kernel adds the HE IEs (either mac80211
> > > > > > > or the driver),
> > > > > > > so, but interestingly in your previous dmesg, I don't see any mac80211 logs.
> > > > > > >
> > > > > > > So, need dmesg logs that capture the connection (look for mac80211 logs).
> > > > > > > >
> > > > > > > > On Tue, Sep 1, 2020 at 10:09 PM Krishna Chaitanya
> > > > > > > > <chaitanya.mgit at gmail.com> wrote:
> > > > > > > > >
> > > > > > > > > On Wed, Sep 2, 2020 at 1:23 AM Sugandh Huthanahally Mohan
> > > > > > > > > <sugandhgowda at gmail.com> wrote:
> > > > > > > > > >
> > > > > > > > > > Hi Krishna,
> > > > > > > > > >
> > > > > > > > > > Currently I am not running wpa_supplicant.
> > > > > > > > > > Is it necessary for hostapd?
> > > > > > > > >
> > > > > > > > > Well, not necessarily, but hostap side it looks fine, so,
> > > > > > > > > we need to see why the STA isn't responding well, probably a
> > > > > > > > > different draft implementation. At the very least we should start
> > > > > > > > > with a sniffer capture of the association b/w the stations to check
> > > > > > > > > the IEs.
> > > > > > >
> > > > > > > Yes this is a new STA connecting AP with wpa_supplicant.
> > > > > > > It is also an AX200.
> > > > > > > I don’t see mac80211 logs on the STA dmesg.
> > > > > > > I am attaching dmesg of the station.
> > > > > >
> > > > > > These are from mac80211:
> > > > > > [ 152.255545] wlp3s0: authenticate with 8c:c6:81:69:86:65
> > > > > > [ 152.258347] wlp3s0: send auth to 8c:c6:81:69:86:65 (try 1/3)
> > > > > > [ 152.283971] wlp3s0: authenticated
> > > > > > [ 152.286624] wlp3s0: associate with 8c:c6:81:69:86:65 (try 1/3)
> > > > > > [ 152.293456] wlp3s0: RX AssocResp from 8c:c6:81:69:86:65
> > > > > > (capab=0x411 status=0 aid=1)
> > > > > > [ 152.299672] wlp3s0: associated
> > > > > > [ 152.364843] IPv6: ADDRCONF(NETDEV_CHANGE): wlp3s0: link becomes ready
> > > > > >
> > > > > > I was hoping to see some prints disabling HE, but looks fine. So,
> > > > > > still, nothing from the logs
> > > > > > to say why HE is disabled in the STA (why it isn't sending HE IEs in
> > > > > > assoc resp).
> > > > > >
> > > > > > Only Sniffer should tell us without resorting to Whitebox debug.
> > > > > > >
> > > > > > > On Wed, Sep 2, 2020 at 1:26 PM Krishna Chaitanya
> > > > > > > <chaitanya.mgit at gmail.com> wrote:
> > > > > > > >
> > > > > > > > On Wed, Sep 2, 2020 at 3:16 PM Sugandh Huthanahally Mohan
> > > > > > > > <sugandhgowda at gmail.com> wrote:
> > > > > > > > >
> > > > > > > > > On Tue, Sep 1, 2020 at 10:09 PM Krishna Chaitanya
> > > > > > > > > <chaitanya.mgit at gmail.com> wrote:
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > > Well, not necessarily, but hostap side it looks fine, so,
> > > > > > > > > > we need to see why the STA isn't responding well, probably a
> > > > > > > > > > different draft implementation. At the very least we should start
> > > > > > > > > > with a sniffer capture of the association b/w the stations to check
> > > > > > > > > > the IEs.
> > > > > > > > >
> > > > > > > > > I am using wpa_supplicant in STA to connect to AP.
> > > > > > > > > I am attaching hostapd logs and wpa_supplicant logs.
> > > > > > > > > I am observing that the STA is connecting and disconnecting when
> > > > > > > > > I try to connect STA to AP.
> > > > > > > > I guess this is a new STA with wpa_supplicant, right? Is it also AX200 based
> > > > > > > > chipset? In the STA mode, the kernel adds the HE IEs (either mac80211
> > > > > > > > or the driver),
> > > > > > > > so, but interestingly in your previous dmesg, I don't see any mac80211 logs.
> > > > > > > >
> > > > > > > > So, need dmesg logs that capture the connection (look for mac80211 logs).
> > > > > > > > >
> > > > > > > > > On Tue, Sep 1, 2020 at 10:09 PM Krishna Chaitanya
> > > > > > > > > <chaitanya.mgit at gmail.com> wrote:
> > > > > > > > > >
> > > > > > > > > > On Wed, Sep 2, 2020 at 1:23 AM Sugandh Huthanahally Mohan
> > > > > > > > > > <sugandhgowda at gmail.com> wrote:
> > > > > > > > > > >
> > > > > > > > > > > Hi Krishna,
> > > > > > > > > > >
> > > > > > > > > > > Currently I am not running wpa_supplicant.
> > > > > > > > > > > Is it necessary for hostapd?
> > > > > > > > > >
> > > > > > > > > > Well, not necessarily, but hostap side it looks fine, so,
> > > > > > > > > > we need to see why the STA isn't responding well, probably a
> > > > > > > > > > different draft implementation. At the very least we should start
> > > > > > > > > > with a sniffer capture of the association b/w the stations to check
> > > > > > > > > > the IEs.
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > > --
> > > > > > > > Thanks,
> > > > > > > > Regards,
> > > > > > > > Chaitanya T K.
> > > > > >
> > > > > >
> > > > > >
> > > > > > --
> > > > > > Thanks,
> > > > > > Regards,
> > > > > > Chaitanya T K.
> >
> >
> > On Wed, Sep 9, 2020 at 12:53 AM Krishna Chaitanya
> > <chaitanya.mgit@gmail.com> wrote:
> > >
> > > On Wed, Sep 9, 2020 at 2:18 AM Sugandh Huthanahally Mohan
> > > <sugandhgowda@gmail.com> wrote:
> > > >
> > > > On Wed, Sep 9, 2020 at 12:27 AM Sugandh Huthanahally Mohan
> > > > <sugandhgowda at gmail.com> wrote:
> > > > > >
> > > > > > I have captured connection between a WiFi6 AP and a WiFi6 STA in wireshark.
> > > > > >I have attached a wireshark pcap file.
> > > > > > I could see HE capabilities exchange in Association request and response.
> > > > > Yes, this looks fine to me except for VHT IEs in the probe and
> > > > > association response in 2.4GHz.
> > > > > Maybe this is what is confusing, can you please disable ieee80211ac=0
> > > > > in the hostapd.conf and try?
> > > > I disabled iee80211ac and I am not seeing VHT capabilities in Association
> > > > frames but the data rate remains the same.I am attaching wireshark capture.
> > > okay, thanks.
> > > > > The iw phy output is below. I couldn't see HE connection in this output.
> > > > >
> > > > > $iw dev wlp3s0 link
> > > > > Connected to 8c:c6:81:69:86:65 (on wlp3s0)
> > > > > SSID: WiFi_AX200
> > > > > freq: 2437
> > > > > RX: 27838 bytes (199 packets)
> > > > > TX: 13319 bytes (97 packets)
> > > > > signal: -34 dBm
> > > > > rx bitrate: 26.0 MBit/s MCS 3
> > > > > tx bitrate: 2.0 MBit/s
> > > > >
> > > > > bss flags: short-slot-time
> > > > > dtim period: 2
> > > > > beacon int: 100
> > > > >
> > > > > > The link doesn't show any specific details related to HE other than
> > > > > > the MCS which can vary, try running
> > > > > > an iperf to see HE MCSes in a clean channel.
> > > >
> > > > Could you please explain what this means.
> > > > I want to know what clean channel means and where actually I can see HE MCSes.
> > >
> > > Sure. The link command doesn't printout any in capability information explicitly
> > > except for the MCS details. And figuring out the mode of connection (11n/11ax)
> > > from the MCS is tricky as the MCS varies across depending on the rate
> > > control algorithm
> > > (for iwlwifi: hardware). So, I was suggesting to use iperf (the more
> > > data you pass, more
> > > chance of the rate control algo to go to higher MCSes) and also by
> > > "clean channels" I was
> > > referring to quieter channels where there are no other BSSes or no
> > > other traffic.
> > >
> > > But, before we go into debugging data path, I still don't understand
> > > why wpa_supplicant
> > > isn't saying it is a HE association?
> > >
> > > Ah, After staring at the code and using blame, a crucial fix missed
> > > out hostap-2.9 windows,
> > > the fix was to properly validate the HE capabilities, I was looking at
> > > the latest cod and
> > > everything looked fine, hence took time.
> > >
> > > hostap_2_9-> 7th August
> > > 0497e4148197fb8fdf92b5c901ce06df1bfa548c ->13th August
> > >
> > > Please use the latest HEAD of hostap.git, you need to compile it
> > > manually and try the
> > > test and let me know how it goes. (make sure all proper configs are enabled)
> > >
> > > > > On Wed, Sep 2, 2020 at 3:39 PM Krishna Chaitanya
> > > > > <chaitanya.mgit at gmail.com> wrote:
> > > > > >
> > > > > > On Wed, Sep 2, 2020 at 6:38 PM Sugandh Huthanahally Mohan
> > > > > > <sugandhgowda at gmail.com> wrote:
> > > > > > >
> > > > > > > On Wed, Sep 2, 2020 at 3:16 PM Sugandh Huthanahally Mohan
> > > > > > > <sugandhgowda at gmail.com> wrote:
> > > > > > > >
> > > > > > > > On Tue, Sep 1, 2020 at 10:09 PM Krishna Chaitanya
> > > > > > > > <chaitanya.mgit at gmail.com> wrote:
> > > > > > > > >
> > > > > > > > >
> > > > > > > > > Well, not necessarily, but hostap side it looks fine, so,
> > > > > > > > > we need to see why the STA isn't responding well, probably a
> > > > > > > > > different draft implementation. At the very least we should start
> > > > > > > > > with a sniffer capture of the association b/w the stations to check
> > > > > > > > > the IEs.
> > > > > > > >
> > > > > > > > I am using wpa_supplicant in STA to connect to AP.
> > > > > > > > I am attaching hostapd logs and wpa_supplicant logs.
> > > > > > > > I am observing that the STA is connecting and disconnecting when
> > > > > > > > I try to connect STA to AP.
> > > > > > > I guess this is a new STA with wpa_supplicant, right? Is it also AX200 based
> > > > > > > chipset? In the STA mode, the kernel adds the HE IEs (either mac80211
> > > > > > > or the driver),
> > > > > > > so, but interestingly in your previous dmesg, I don't see any mac80211 logs.
> > > > > > >
> > > > > > > So, need dmesg logs that capture the connection (look for mac80211 logs).
> > > > > > > >
> > > > > > > > On Tue, Sep 1, 2020 at 10:09 PM Krishna Chaitanya
> > > > > > > > <chaitanya.mgit at gmail.com> wrote:
> > > > > > > > >
> > > > > > > > > On Wed, Sep 2, 2020 at 1:23 AM Sugandh Huthanahally Mohan
> > > > > > > > > <sugandhgowda at gmail.com> wrote:
> > > > > > > > > >
> > > > > > > > > > Hi Krishna,
> > > > > > > > > >
> > > > > > > > > > Currently I am not running wpa_supplicant.
> > > > > > > > > > Is it necessary for hostapd?
> > > > > > > > >
> > > > > > > > > Well, not necessarily, but hostap side it looks fine, so,
> > > > > > > > > we need to see why the STA isn't responding well, probably a
> > > > > > > > > different draft implementation. At the very least we should start
> > > > > > > > > with a sniffer capture of the association b/w the stations to check
> > > > > > > > > the IEs.
> > > > > > >
> > > > > > > Yes this is a new STA connecting AP with wpa_supplicant.
> > > > > > > It is also an AX200.
> > > > > > > I don’t see mac80211 logs on the STA dmesg.
> > > > > > > I am attaching dmesg of the station.
> > > > > >
> > > > > > These are from mac80211:
> > > > > > [ 152.255545] wlp3s0: authenticate with 8c:c6:81:69:86:65
> > > > > > [ 152.258347] wlp3s0: send auth to 8c:c6:81:69:86:65 (try 1/3)
> > > > > > [ 152.283971] wlp3s0: authenticated
> > > > > > [ 152.286624] wlp3s0: associate with 8c:c6:81:69:86:65 (try 1/3)
> > > > > > [ 152.293456] wlp3s0: RX AssocResp from 8c:c6:81:69:86:65
> > > > > > (capab=0x411 status=0 aid=1)
> > > > > > [ 152.299672] wlp3s0: associated
> > > > > > [ 152.364843] IPv6: ADDRCONF(NETDEV_CHANGE): wlp3s0: link becomes ready
> > > > > >
> > > > > > I was hoping to see some prints disabling HE, but looks fine. So,
> > > > > > still, nothing from the logs
> > > > > > to say why HE is disabled in the STA (why it isn't sending HE IEs in
> > > > > > assoc resp).
> > > > > >
> > > > > > Only Sniffer should tell us without resorting to Whitebox debug.
> > > > > > >
> > > > > > > On Wed, Sep 2, 2020 at 1:26 PM Krishna Chaitanya
> > > > > > > <chaitanya.mgit at gmail.com> wrote:
> > > > > > > >
> > > > > > > > On Wed, Sep 2, 2020 at 3:16 PM Sugandh Huthanahally Mohan
> > > > > > > > <sugandhgowda at gmail.com> wrote:
> > > > > > > > >
> > > > > > > > > On Tue, Sep 1, 2020 at 10:09 PM Krishna Chaitanya
> > > > > > > > > <chaitanya.mgit at gmail.com> wrote:
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > > Well, not necessarily, but hostap side it looks fine, so,
> > > > > > > > > > we need to see why the STA isn't responding well, probably a
> > > > > > > > > > different draft implementation. At the very least we should start
> > > > > > > > > > with a sniffer capture of the association b/w the stations to check
> > > > > > > > > > the IEs.
> > > > > > > > >
> > > > > > > > > I am using wpa_supplicant in STA to connect to AP.
> > > > > > > > > I am attaching hostapd logs and wpa_supplicant logs.
> > > > > > > > > I am observing that the STA is connecting and disconnecting when
> > > > > > > > > I try to connect STA to AP.
> > > > > > > > I guess this is a new STA with wpa_supplicant, right? Is it also AX200 based
> > > > > > > > chipset? In the STA mode, the kernel adds the HE IEs (either mac80211
> > > > > > > > or the driver),
> > > > > > > > so, but interestingly in your previous dmesg, I don't see any mac80211 logs.
> > > > > > > >
> > > > > > > > So, need dmesg logs that capture the connection (look for mac80211 logs).
> > > > > > > > >
> > > > > > > > > On Tue, Sep 1, 2020 at 10:09 PM Krishna Chaitanya
> > > > > > > > > <chaitanya.mgit at gmail.com> wrote:
> > > > > > > > > >
> > > > > > > > > > On Wed, Sep 2, 2020 at 1:23 AM Sugandh Huthanahally Mohan
> > > > > > > > > > <sugandhgowda at gmail.com> wrote:
> > > > > > > > > > >
> > > > > > > > > > > Hi Krishna,
> > > > > > > > > > >
> > > > > > > > > > > Currently I am not running wpa_supplicant.
> > > > > > > > > > > Is it necessary for hostapd?
> > > > > > > > > >
> > > > > > > > > > Well, not necessarily, but hostap side it looks fine, so,
> > > > > > > > > > we need to see why the STA isn't responding well, probably a
> > > > > > > > > > different draft implementation. At the very least we should start
> > > > > > > > > > with a sniffer capture of the association b/w the stations to check
> > > > > > > > > > the IEs.
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > > --
> > > > > > > > Thanks,
> > > > > > > > Regards,
> > > > > > > > Chaitanya T K.
> > > > > >
> > > > > >
> > > > > >
> > > > > > --
> > > > > > Thanks,
> > > > > > Regards,
> > > > > > Chaitanya T K.
> > > >
> > > >
> > > > On Tue, Sep 8, 2020 at 9:55 PM Krishna Chaitanya
> > > > <chaitanya.mgit@gmail.com> wrote:
> > > > >
> > > > > On Wed, Sep 9, 2020 at 12:27 AM Sugandh Huthanahally Mohan
> > > > > <sugandhgowda@gmail.com> wrote:
> > > > > >
> > > > > > I have captured connection between a WiFi6 AP and a WiFi6 STA in wireshark.
> > > > > > I have attached a wireshark pcap file.
> > > > > > I could see HE capabilities exchange in Association request and response.
> > > > > Yes, this looks fine to me except for VHT IEs in the probe and
> > > > > association response in 2.4GHz.
> > > > > Maybe this is what is confusing, can you please disable ieee80211ac=0
> > > > > in the hostapd.conf and try?
> > > > >
> > > > > > The iw phy output is below. I couldn't see HE connection in this output.
> > > > > >
> > > > > > $iw dev wlp3s0 link
> > > > > > Connected to 8c:c6:81:69:86:65 (on wlp3s0)
> > > > > > SSID: WiFi_AX200
> > > > > > freq: 2437
> > > > > > RX: 27838 bytes (199 packets)
> > > > > > TX: 13319 bytes (97 packets)
> > > > > > signal: -34 dBm
> > > > > > rx bitrate: 26.0 MBit/s MCS 3
> > > > > > tx bitrate: 2.0 MBit/s
> > > > > >
> > > > > > bss flags: short-slot-time
> > > > > > dtim period: 2
> > > > > > beacon int: 100
> > > > > >
> > > > > The link doesn't show any specific details related to HE other than
> > > > > the MCS which can vary, try running
> > > > > an iperf to see HE MCSes in a clean channel.
> > > > > >
> > > > > > On Wed, Sep 2, 2020 at 3:39 PM Krishna Chaitanya
> > > > > > <chaitanya.mgit@gmail.com> wrote:
> > > > > > >
> > > > > > > On Wed, Sep 2, 2020 at 6:38 PM Sugandh Huthanahally Mohan
> > > > > > > <sugandhgowda@gmail.com> wrote:
> > > > > > > >
> > > > > > > > On Wed, Sep 2, 2020 at 3:16 PM Sugandh Huthanahally Mohan
> > > > > > > > <sugandhgowda at gmail.com> wrote:
> > > > > > > > >
> > > > > > > > > On Tue, Sep 1, 2020 at 10:09 PM Krishna Chaitanya
> > > > > > > > > <chaitanya.mgit at gmail.com> wrote:
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > > Well, not necessarily, but hostap side it looks fine, so,
> > > > > > > > > > we need to see why the STA isn't responding well, probably a
> > > > > > > > > > different draft implementation. At the very least we should start
> > > > > > > > > > with a sniffer capture of the association b/w the stations to check
> > > > > > > > > > the IEs.
> > > > > > > > >
> > > > > > > > > I am using wpa_supplicant in STA to connect to AP.
> > > > > > > > > I am attaching hostapd logs and wpa_supplicant logs.
> > > > > > > > > I am observing that the STA is connecting and disconnecting when
> > > > > > > > > I try to connect STA to AP.
> > > > > > > > I guess this is a new STA with wpa_supplicant, right? Is it also AX200 based
> > > > > > > > chipset? In the STA mode, the kernel adds the HE IEs (either mac80211
> > > > > > > > or the driver),
> > > > > > > > so, but interestingly in your previous dmesg, I don't see any mac80211 logs.
> > > > > > > >
> > > > > > > > So, need dmesg logs that capture the connection (look for mac80211 logs).
> > > > > > > > >
> > > > > > > > > On Tue, Sep 1, 2020 at 10:09 PM Krishna Chaitanya
> > > > > > > > > <chaitanya.mgit at gmail.com> wrote:
> > > > > > > > > >
> > > > > > > > > > On Wed, Sep 2, 2020 at 1:23 AM Sugandh Huthanahally Mohan
> > > > > > > > > > <sugandhgowda at gmail.com> wrote:
> > > > > > > > > > >
> > > > > > > > > > > Hi Krishna,
> > > > > > > > > > >
> > > > > > > > > > > Currently I am not running wpa_supplicant.
> > > > > > > > > > > Is it necessary for hostapd?
> > > > > > > > > >
> > > > > > > > > > Well, not necessarily, but hostap side it looks fine, so,
> > > > > > > > > > we need to see why the STA isn't responding well, probably a
> > > > > > > > > > different draft implementation. At the very least we should start
> > > > > > > > > > with a sniffer capture of the association b/w the stations to check
> > > > > > > > > > the IEs.
> > > > > > > >
> > > > > > > > Yes this is a new STA connecting AP with wpa_supplicant.
> > > > > > > > It is also an AX200.
> > > > > > > > I don’t see mac80211 logs on the STA dmesg.
> > > > > > > > I am attaching dmesg of the station.
> > > > > > >
> > > > > > > These are from mac80211:
> > > > > > > [ 152.255545] wlp3s0: authenticate with 8c:c6:81:69:86:65
> > > > > > > [ 152.258347] wlp3s0: send auth to 8c:c6:81:69:86:65 (try 1/3)
> > > > > > > [ 152.283971] wlp3s0: authenticated
> > > > > > > [ 152.286624] wlp3s0: associate with 8c:c6:81:69:86:65 (try 1/3)
> > > > > > > [ 152.293456] wlp3s0: RX AssocResp from 8c:c6:81:69:86:65
> > > > > > > (capab=0x411 status=0 aid=1)
> > > > > > > [ 152.299672] wlp3s0: associated
> > > > > > > [ 152.364843] IPv6: ADDRCONF(NETDEV_CHANGE): wlp3s0: link becomes ready
> > > > > > >
> > > > > > > I was hoping to see some prints disabling HE, but looks fine. So,
> > > > > > > still, nothing from the logs
> > > > > > > to say why HE is disabled in the STA (why it isn't sending HE IEs in
> > > > > > > assoc resp).
> > > > > > >
> > > > > > > Only Sniffer should tell us without resorting to Whitebox debug.
> > > > > > > >
> > > > > > > > On Wed, Sep 2, 2020 at 1:26 PM Krishna Chaitanya
> > > > > > > > <chaitanya.mgit@gmail.com> wrote:
> > > > > > > > >
> > > > > > > > > On Wed, Sep 2, 2020 at 3:16 PM Sugandh Huthanahally Mohan
> > > > > > > > > <sugandhgowda@gmail.com> wrote:
> > > > > > > > > >
> > > > > > > > > > On Tue, Sep 1, 2020 at 10:09 PM Krishna Chaitanya
> > > > > > > > > > <chaitanya.mgit at gmail.com> wrote:
> > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > > Well, not necessarily, but hostap side it looks fine, so,
> > > > > > > > > > > we need to see why the STA isn't responding well, probably a
> > > > > > > > > > > different draft implementation. At the very least we should start
> > > > > > > > > > > with a sniffer capture of the association b/w the stations to check
> > > > > > > > > > > the IEs.
> > > > > > > > > >
> > > > > > > > > > I am using wpa_supplicant in STA to connect to AP.
> > > > > > > > > > I am attaching hostapd logs and wpa_supplicant logs.
> > > > > > > > > > I am observing that the STA is connecting and disconnecting when
> > > > > > > > > > I try to connect STA to AP.
> > > > > > > > > I guess this is a new STA with wpa_supplicant, right? Is it also AX200 based
> > > > > > > > > chipset? In the STA mode, the kernel adds the HE IEs (either mac80211
> > > > > > > > > or the driver),
> > > > > > > > > so, but interestingly in your previous dmesg, I don't see any mac80211 logs.
> > > > > > > > >
> > > > > > > > > So, need dmesg logs that capture the connection (look for mac80211 logs).
> > > > > > > > > >
> > > > > > > > > > On Tue, Sep 1, 2020 at 10:09 PM Krishna Chaitanya
> > > > > > > > > > <chaitanya.mgit@gmail.com> wrote:
> > > > > > > > > > >
> > > > > > > > > > > On Wed, Sep 2, 2020 at 1:23 AM Sugandh Huthanahally Mohan
> > > > > > > > > > > <sugandhgowda@gmail.com> wrote:
> > > > > > > > > > > >
> > > > > > > > > > > > Hi Krishna,
> > > > > > > > > > > >
> > > > > > > > > > > > Currently I am not running wpa_supplicant.
> > > > > > > > > > > > Is it necessary for hostapd?
> > > > > > > > > > >
> > > > > > > > > > > Well, not necessarily, but hostap side it looks fine, so,
> > > > > > > > > > > we need to see why the STA isn't responding well, probably a
> > > > > > > > > > > different draft implementation. At the very least we should start
> > > > > > > > > > > with a sniffer capture of the association b/w the stations to check
> > > > > > > > > > > the IEs.
> > > > > > > > >
> > > > > > > > >
> > > > > > > > >
> > > > > > > > > --
> > > > > > > > > Thanks,
> > > > > > > > > Regards,
> > > > > > > > > Chaitanya T K.
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > --
> > > > > > > Thanks,
> > > > > > > Regards,
> > > > > > > Chaitanya T K.
>
> On Fri, Sep 11, 2020 at 4:36 PM Krishna Chaitanya
> <chaitanya.mgit@gmail.com> wrote:
> >
> > On Fri, Sep 11, 2020 at 7:33 PM Sugandh Huthanahally Mohan
> > <sugandhgowda@gmail.com> wrote:
> > >
> > > On Wed, Sep 9, 2020 at 2:18 AM Sugandh Huthanahally Mohan
> > > <sugandhgowda at gmail.com> wrote:
> > > >
> > > > On Wed, Sep 9, 2020 at 12:27 AM Sugandh Huthanahally Mohan
> > > > <sugandhgowda at gmail.com> wrote:
> > > > > >
> > > > > > I have captured connection between a WiFi6 AP and a WiFi6 STA in wireshark.
> > > > > >I have attached a wireshark pcap file.
> > > > > > I could see HE capabilities exchange in Association request and response.
> > > > > Yes, this looks fine to me except for VHT IEs in the probe and
> > > > > association response in 2.4GHz.
> > > > > Maybe this is what is confusing, can you please disable ieee80211ac=0
> > > > > in the hostapd.conf and try?
> > > > I disabled iee80211ac and I am not seeing VHT capabilities in Association
> > > > frames but the data rate remains the same.I am attaching wireshark capture.
> > > okay, thanks.
> > > > > The iw phy output is below. I couldn't see HE connection in this output.
> > > > >
> > > > > $iw dev wlp3s0 link
> > > > > Connected to 8c:c6:81:69:86:65 (on wlp3s0)
> > > > > SSID: WiFi_AX200
> > > > > freq: 2437
> > > > > RX: 27838 bytes (199 packets)
> > > > > TX: 13319 bytes (97 packets)
> > > > > signal: -34 dBm
> > > > > rx bitrate: 26.0 MBit/s MCS 3
> > > > > tx bitrate: 2.0 MBit/s
> > > > >
> > > > > bss flags: short-slot-time
> > > > > dtim period: 2
> > > > > beacon int: 100
> > > > >
> > > > > > The link doesn't show any specific details related to HE other than
> > > > > > the MCS which can vary, try running
> > > > > > an iperf to see HE MCSes in a clean channel.
> > > >
> > > > Could you please explain what this means.
> > > > I want to know what clean channel means and where actually I can see HE MCSes.
> > >
> > > > Sure. The link command doesn't printout any in capability information explicitly
> > > > except for the MCS details. And figuring out the mode of connection (11n/11ax)
> > > > from the MCS is tricky as the MCS varies across depending on the rate
> > > > control algorithm
> > > > (for iwlwifi: hardware). So, I was suggesting to use iperf (the more
> > > > data you pass, more
> > > > chance of the rate control algo to go to higher MCSes) and also by
> > > > "clean channels" I was
> > > > referring to quieter channels where there are no other BSSes or no
> > > > other traffic.
> > > Okay. I tried running iperf for long period of time between AP and STA
> > > (injected incremental traffic ,like running more parallel connections between
> > > iperf server and iperf client ) and I did not see any changes in MCSes.
> > > It remained the same throughout the time I ran the iperf test.
> > Okay, this was to rule out any rate control issues but as it turned out to be
> > a functional issue, we can ignore this for now.
> > >
> > > > But, before we go into debugging data path, I still don't understand
> > > > why wpa_supplicant
> > > > isn't saying it is a HE association?
> > >
> > > > Ah, After staring at the code and using blame, a crucial fix missed
> > > > out hostap-2.9 windows,
> > > > the fix was to properly validate the HE capabilities, I was looking at
> > > > the latest cod and
> > > > everything looked fine, hence took time.
> > >
> > > > hostap_2_9-> 7th August
> > > > 0497e4148197fb8fdf92b5c901ce06df1bfa548c ->13th August
> > >
> > > > Please use the latest HEAD of hostap.git, you need to compile it
> > > > manually and try the
> > > > test and let me know how it goes. (make sure all proper configs are enabled)
> > >
> > > Previously I was using hostapd version 2.9 and with this version I could
> > > connect STA's to AP with the hostapd.conf which I had shared earlier.
> > >
> > > Now I pulled the latest HEAD and compiled it with proper flags enabled.
> > > When I run hostapd now , the WiFi6 STA's(AX200) are not able to establish
> > > solid connection to AP. In other words, I could see they are connecting but
> > > hostapd is deleting the station. Below are the log pertaining to that
> > >
> > > nl80211: NL80211_CMD_SET_STATION result: -5 (Input/output error)
> > > wlp3s0: STA 8c:c6:81:69:ac:80 IEEE 802.11: Could not set STA to kernel driver
> > > nl80211: sta_remove -> DEL_STATION wlp3s0 8c:c6:81:69:ac:80 --> 0 (Success)
> > First of all, the original problem is resolved, I can see he_capabs
> > now, but unfortunately
> > , the problem moved to the kernel :). There are many reasons why the
> > mac80211/iwlwifi
> > might return EIO, Could you please also share the dmesg as well when
> > this happens?
> > >
> > >
> > > Also I could see multiple Association requests and responses. On the
> > > other hand I am
> > > able to connect WiFi4(802.11n) STA's to AP. I am attaching the hostapd logs
> > > with debugs enabled and also wireshark captures.
> > This is in line with the logs, as Set-STA is failing association
> > request will not go through.
> > >
> > > > > On Wed, Sep 2, 2020 at 3:39 PM Krishna Chaitanya
> > > > > <chaitanya.mgit at gmail.com> wrote:
> > > > > >
> > > > > > On Wed, Sep 2, 2020 at 6:38 PM Sugandh Huthanahally Mohan
> > > > > > <sugandhgowda at gmail.com> wrote:
> > > > > > >
> > > > > > > On Wed, Sep 2, 2020 at 3:16 PM Sugandh Huthanahally Mohan
> > > > > > > <sugandhgowda at gmail.com> wrote:
> > > > > > > >
> > > > > > > > On Tue, Sep 1, 2020 at 10:09 PM Krishna Chaitanya
> > > > > > > > <chaitanya.mgit at gmail.com> wrote:
> > > > > > > > >
> > > > > > > > >
> > > > > > > > > Well, not necessarily, but hostap side it looks fine, so,
> > > > > > > > > we need to see why the STA isn't responding well, probably a
> > > > > > > > > different draft implementation. At the very least we should start
> > > > > > > > > with a sniffer capture of the association b/w the stations to check
> > > > > > > > > the IEs.
> > > > > > > >
> > > > > > > > I am using wpa_supplicant in STA to connect to AP.
> > > > > > > > I am attaching hostapd logs and wpa_supplicant logs.
> > > > > > > > I am observing that the STA is connecting and disconnecting when
> > > > > > > > I try to connect STA to AP.
> > > > > > > I guess this is a new STA with wpa_supplicant, right? Is it also AX200 based
> > > > > > > chipset? In the STA mode, the kernel adds the HE IEs (either mac80211
> > > > > > > or the driver),
> > > > > > > so, but interestingly in your previous dmesg, I don't see any mac80211 logs.
> > > > > > >
> > > > > > > So, need dmesg logs that capture the connection (look for mac80211 logs).
> > > > > > > >
> > > > > > > > On Tue, Sep 1, 2020 at 10:09 PM Krishna Chaitanya
> > > > > > > > <chaitanya.mgit at gmail.com> wrote:
> > > > > > > > >
> > > > > > > > > On Wed, Sep 2, 2020 at 1:23 AM Sugandh Huthanahally Mohan
> > > > > > > > > <sugandhgowda at gmail.com> wrote:
> > > > > > > > > >
> > > > > > > > > > Hi Krishna,
> > > > > > > > > >
> > > > > > > > > > Currently I am not running wpa_supplicant.
> > > > > > > > > > Is it necessary for hostapd?
> > > > > > > > >
> > > > > > > > > Well, not necessarily, but hostap side it looks fine, so,
> > > > > > > > > we need to see why the STA isn't responding well, probably a
> > > > > > > > > different draft implementation. At the very least we should start
> > > > > > > > > with a sniffer capture of the association b/w the stations to check
> > > > > > > > > the IEs.
> > > > > > >
> > > > > > > Yes this is a new STA connecting AP with wpa_supplicant.
> > > > > > > It is also an AX200.
> > > > > > > I don’t see mac80211 logs on the STA dmesg.
> > > > > > > I am attaching dmesg of the station.
> > > > > >
> > > > > > These are from mac80211:
> > > > > > [ 152.255545] wlp3s0: authenticate with 8c:c6:81:69:86:65
> > > > > > [ 152.258347] wlp3s0: send auth to 8c:c6:81:69:86:65 (try 1/3)
> > > > > > [ 152.283971] wlp3s0: authenticated
> > > > > > [ 152.286624] wlp3s0: associate with 8c:c6:81:69:86:65 (try 1/3)
> > > > > > [ 152.293456] wlp3s0: RX AssocResp from 8c:c6:81:69:86:65
> > > > > > (capab=0x411 status=0 aid=1)
> > > > > > [ 152.299672] wlp3s0: associated
> > > > > > [ 152.364843] IPv6: ADDRCONF(NETDEV_CHANGE): wlp3s0: link becomes ready
> > > > > >
> > > > > > I was hoping to see some prints disabling HE, but looks fine. So,
> > > > > > still, nothing from the logs
> > > > > > to say why HE is disabled in the STA (why it isn't sending HE IEs in
> > > > > > assoc resp).
> > > > > >
> > > > > > Only Sniffer should tell us without resorting to Whitebox debug.
> > > > > > >
> > > > > > > On Wed, Sep 2, 2020 at 1:26 PM Krishna Chaitanya
> > > > > > > <chaitanya.mgit at gmail.com> wrote:
> > > > > > > >
> > > > > > > > On Wed, Sep 2, 2020 at 3:16 PM Sugandh Huthanahally Mohan
> > > > > > > > <sugandhgowda at gmail.com> wrote:
> > > > > > > > >
> > > > > > > > > On Tue, Sep 1, 2020 at 10:09 PM Krishna Chaitanya
> > > > > > > > > <chaitanya.mgit at gmail.com> wrote:
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > > Well, not necessarily, but hostap side it looks fine, so,
> > > > > > > > > > we need to see why the STA isn't responding well, probably a
> > > > > > > > > > different draft implementation. At the very least we should start
> > > > > > > > > > with a sniffer capture of the association b/w the stations to check
> > > > > > > > > > the IEs.
> > > > > > > > >
> > > > > > > > > I am using wpa_supplicant in STA to connect to AP.
> > > > > > > > > I am attaching hostapd logs and wpa_supplicant logs.
> > > > > > > > > I am observing that the STA is connecting and disconnecting when
> > > > > > > > > I try to connect STA to AP.
> > > > > > > > I guess this is a new STA with wpa_supplicant, right? Is it also AX200 based
> > > > > > > > chipset? In the STA mode, the kernel adds the HE IEs (either mac80211
> > > > > > > > or the driver),
> > > > > > > > so, but interestingly in your previous dmesg, I don't see any mac80211 logs.
> > > > > > > >
> > > > > > > > So, need dmesg logs that capture the connection (look for mac80211 logs).
> > > > > > > > >
> > > > > > > > > On Tue, Sep 1, 2020 at 10:09 PM Krishna Chaitanya
> > > > > > > > > <chaitanya.mgit at gmail.com> wrote:
> > > > > > > > > >
> > > > > > > > > > On Wed, Sep 2, 2020 at 1:23 AM Sugandh Huthanahally Mohan
> > > > > > > > > > <sugandhgowda at gmail.com> wrote:
> > > > > > > > > > >
> > > > > > > > > > > Hi Krishna,
> > > > > > > > > > >
> > > > > > > > > > > Currently I am not running wpa_supplicant.
> > > > > > > > > > > Is it necessary for hostapd?
> > > > > > > > > >
> > > > > > > > > > Well, not necessarily, but hostap side it looks fine, so,
> > > > > > > > > > we need to see why the STA isn't responding well, probably a
> > > > > > > > > > different draft implementation. At the very least we should start
> > > > > > > > > > with a sniffer capture of the association b/w the stations to check
> > > > > > > > > > the IEs.
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > > --
> > > > > > > > Thanks,
> > > > > > > > Regards,
> > > > > > > > Chaitanya T K.
> > > > > >
> > > > > >
> > > > > >
> > > > > > --
> > > > > > Thanks,
> > > > > > Regards,
> > > > > > Chaitanya T K.
> > > >
> > > >
> > > > On Tue, Sep 8, 2020 at 9:55 PM Krishna Chaitanya
> > > > <chaitanya.mgit at gmail.com> wrote:
> > > > >
> > > > > On Wed, Sep 9, 2020 at 12:27 AM Sugandh Huthanahally Mohan
> > > > > <sugandhgowda at gmail.com> wrote:
> > > > > >
> > > > > > I have captured connection between a WiFi6 AP and a WiFi6 STA in wireshark.
> > > > > > I have attached a wireshark pcap file.
> > > > > > I could see HE capabilities exchange in Association request and response.
> > > > > Yes, this looks fine to me except for VHT IEs in the probe and
> > > > > association response in 2.4GHz.
> > > > > Maybe this is what is confusing, can you please disable ieee80211ac=0
> > > > > in the hostapd.conf and try?
> > > > >
> > > > > > The iw phy output is below. I couldn't see HE connection in this output.
> > > > > >
> > > > > > $iw dev wlp3s0 link
> > > > > > Connected to 8c:c6:81:69:86:65 (on wlp3s0)
> > > > > > SSID: WiFi_AX200
> > > > > > freq: 2437
> > > > > > RX: 27838 bytes (199 packets)
> > > > > > TX: 13319 bytes (97 packets)
> > > > > > signal: -34 dBm
> > > > > > rx bitrate: 26.0 MBit/s MCS 3
> > > > > > tx bitrate: 2.0 MBit/s
> > > > > >
> > > > > > bss flags: short-slot-time
> > > > > > dtim period: 2
> > > > > > beacon int: 100
> > > > > >
> > > > > The link doesn't show any specific details related to HE other than
> > > > > the MCS which can vary, try running
> > > > > an iperf to see HE MCSes in a clean channel.
> > > > > >
> > > > > > On Wed, Sep 2, 2020 at 3:39 PM Krishna Chaitanya
> > > > > > <chaitanya.mgit at gmail.com> wrote:
> > > > > > >
> > > > > > > On Wed, Sep 2, 2020 at 6:38 PM Sugandh Huthanahally Mohan
> > > > > > > <sugandhgowda at gmail.com> wrote:
> > > > > > > >
> > > > > > > > On Wed, Sep 2, 2020 at 3:16 PM Sugandh Huthanahally Mohan
> > > > > > > > <sugandhgowda at gmail.com> wrote:
> > > > > > > > >
> > > > > > > > > On Tue, Sep 1, 2020 at 10:09 PM Krishna Chaitanya
> > > > > > > > > <chaitanya.mgit at gmail.com> wrote:
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > > Well, not necessarily, but hostap side it looks fine, so,
> > > > > > > > > > we need to see why the STA isn't responding well, probably a
> > > > > > > > > > different draft implementation. At the very least we should start
> > > > > > > > > > with a sniffer capture of the association b/w the stations to check
> > > > > > > > > > the IEs.
> > > > > > > > >
> > > > > > > > > I am using wpa_supplicant in STA to connect to AP.
> > > > > > > > > I am attaching hostapd logs and wpa_supplicant logs.
> > > > > > > > > I am observing that the STA is connecting and disconnecting when
> > > > > > > > > I try to connect STA to AP.
> > > > > > > > I guess this is a new STA with wpa_supplicant, right? Is it also AX200 based
> > > > > > > > chipset? In the STA mode, the kernel adds the HE IEs (either mac80211
> > > > > > > > or the driver),
> > > > > > > > so, but interestingly in your previous dmesg, I don't see any mac80211 logs.
> > > > > > > >
> > > > > > > > So, need dmesg logs that capture the connection (look for mac80211 logs).
> > > > > > > > >
> > > > > > > > > On Tue, Sep 1, 2020 at 10:09 PM Krishna Chaitanya
> > > > > > > > > <chaitanya.mgit at gmail.com> wrote:
> > > > > > > > > >
> > > > > > > > > > On Wed, Sep 2, 2020 at 1:23 AM Sugandh Huthanahally Mohan
> > > > > > > > > > <sugandhgowda at gmail.com> wrote:
> > > > > > > > > > >
> > > > > > > > > > > Hi Krishna,
> > > > > > > > > > >
> > > > > > > > > > > Currently I am not running wpa_supplicant.
> > > > > > > > > > > Is it necessary for hostapd?
> > > > > > > > > >
> > > > > > > > > > Well, not necessarily, but hostap side it looks fine, so,
> > > > > > > > > > we need to see why the STA isn't responding well, probably a
> > > > > > > > > > different draft implementation. At the very least we should start
> > > > > > > > > > with a sniffer capture of the association b/w the stations to check
> > > > > > > > > > the IEs.
> > > > > > > >
> > > > > > > > Yes this is a new STA connecting AP with wpa_supplicant.
> > > > > > > > It is also an AX200.
> > > > > > > > I don’t see mac80211 logs on the STA dmesg.
> > > > > > > > I am attaching dmesg of the station.
> > > > > > >
> > > > > > > These are from mac80211:
> > > > > > > [ 152.255545] wlp3s0: authenticate with 8c:c6:81:69:86:65
> > > > > > > [ 152.258347] wlp3s0: send auth to 8c:c6:81:69:86:65 (try 1/3)
> > > > > > > [ 152.283971] wlp3s0: authenticated
> > > > > > > [ 152.286624] wlp3s0: associate with 8c:c6:81:69:86:65 (try 1/3)
> > > > > > > [ 152.293456] wlp3s0: RX AssocResp from 8c:c6:81:69:86:65
> > > > > > > (capab=0x411 status=0 aid=1)
> > > > > > > [ 152.299672] wlp3s0: associated
> > > > > > > [ 152.364843] IPv6: ADDRCONF(NETDEV_CHANGE): wlp3s0: link becomes ready
> > > > > > >
> > > > > > > I was hoping to see some prints disabling HE, but looks fine. So,
> > > > > > > still, nothing from the logs
> > > > > > > to say why HE is disabled in the STA (why it isn't sending HE IEs in
> > > > > > > assoc resp).
> > > > > > >
> > > > > > > Only Sniffer should tell us without resorting to Whitebox debug.
> > > > > > > >
> > > > > > > > On Wed, Sep 2, 2020 at 1:26 PM Krishna Chaitanya
> > > > > > > > <chaitanya.mgit at gmail.com> wrote:
> > > > > > > > >
> > > > > > > > > On Wed, Sep 2, 2020 at 3:16 PM Sugandh Huthanahally Mohan
> > > > > > > > > <sugandhgowda at gmail.com> wrote:
> > > > > > > > > >
> > > > > > > > > > On Tue, Sep 1, 2020 at 10:09 PM Krishna Chaitanya
> > > > > > > > > > <chaitanya.mgit at gmail.com> wrote:
> > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > > Well, not necessarily, but hostap side it looks fine, so,
> > > > > > > > > > > we need to see why the STA isn't responding well, probably a
> > > > > > > > > > > different draft implementation. At the very least we should start
> > > > > > > > > > > with a sniffer capture of the association b/w the stations to check
> > > > > > > > > > > the IEs.
> > > > > > > > > >
> > > > > > > > > > I am using wpa_supplicant in STA to connect to AP.
> > > > > > > > > > I am attaching hostapd logs and wpa_supplicant logs.
> > > > > > > > > > I am observing that the STA is connecting and disconnecting when
> > > > > > > > > > I try to connect STA to AP.
> > > > > > > > > I guess this is a new STA with wpa_supplicant, right? Is it also AX200 based
> > > > > > > > > chipset? In the STA mode, the kernel adds the HE IEs (either mac80211
> > > > > > > > > or the driver),
> > > > > > > > > so, but interestingly in your previous dmesg, I don't see any mac80211 logs.
> > > > > > > > >
> > > > > > > > > So, need dmesg logs that capture the connection (look for mac80211 logs).
> > > > > > > > > >
> > > > > > > > > > On Tue, Sep 1, 2020 at 10:09 PM Krishna Chaitanya
> > > > > > > > > > <chaitanya.mgit at gmail.com> wrote:
> > > > > > > > > > >
> > > > > > > > > > > On Wed, Sep 2, 2020 at 1:23 AM Sugandh Huthanahally Mohan
> > > > > > > > > > > <sugandhgowda at gmail.com> wrote:
> > > > > > > > > > > >
> > > > > > > > > > > > Hi Krishna,
> > > > > > > > > > > >
> > > > > > > > > > > > Currently I am not running wpa_supplicant.
> > > > > > > > > > > > Is it necessary for hostapd?
> > > > > > > > > > >
> > > > > > > > > > > Well, not necessarily, but hostap side it looks fine, so,
> > > > > > > > > > > we need to see why the STA isn't responding well, probably a
> > > > > > > > > > > different draft implementation. At the very least we should start
> > > > > > > > > > > with a sniffer capture of the association b/w the stations to check
> > > > > > > > > > > the IEs.
> > > > > > > > >
> > > > > > > > >
> > > > > > > > >
> > > > > > > > > --
> > > > > > > > > Thanks,
> > > > > > > > > Regards,
> > > > > > > > > Chaitanya T K.
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > --
> > > > > > > Thanks,
> > > > > > > Regards,
> > > > > > > Chaitanya T K.
> > >
> > >
> > > On Wed, Sep 9, 2020 at 12:53 AM Krishna Chaitanya
> > > <chaitanya.mgit@gmail.com> wrote:
> > > >
> > > > On Wed, Sep 9, 2020 at 2:18 AM Sugandh Huthanahally Mohan
> > > > <sugandhgowda@gmail.com> wrote:
> > > > >
> > > > > On Wed, Sep 9, 2020 at 12:27 AM Sugandh Huthanahally Mohan
> > > > > <sugandhgowda at gmail.com> wrote:
> > > > > > >
> > > > > > > I have captured connection between a WiFi6 AP and a WiFi6 STA in wireshark.
> > > > > > >I have attached a wireshark pcap file.
> > > > > > > I could see HE capabilities exchange in Association request and response.
> > > > > > Yes, this looks fine to me except for VHT IEs in the probe and
> > > > > > association response in 2.4GHz.
> > > > > > Maybe this is what is confusing, can you please disable ieee80211ac=0
> > > > > > in the hostapd.conf and try?
> > > > > I disabled iee80211ac and I am not seeing VHT capabilities in Association
> > > > > frames but the data rate remains the same.I am attaching wireshark capture.
> > > > okay, thanks.
> > > > > > The iw phy output is below. I couldn't see HE connection in this output.
> > > > > >
> > > > > > $iw dev wlp3s0 link
> > > > > > Connected to 8c:c6:81:69:86:65 (on wlp3s0)
> > > > > > SSID: WiFi_AX200
> > > > > > freq: 2437
> > > > > > RX: 27838 bytes (199 packets)
> > > > > > TX: 13319 bytes (97 packets)
> > > > > > signal: -34 dBm
> > > > > > rx bitrate: 26.0 MBit/s MCS 3
> > > > > > tx bitrate: 2.0 MBit/s
> > > > > >
> > > > > > bss flags: short-slot-time
> > > > > > dtim period: 2
> > > > > > beacon int: 100
> > > > > >
> > > > > > > The link doesn't show any specific details related to HE other than
> > > > > > > the MCS which can vary, try running
> > > > > > > an iperf to see HE MCSes in a clean channel.
> > > > >
> > > > > Could you please explain what this means.
> > > > > I want to know what clean channel means and where actually I can see HE MCSes.
> > > >
> > > > Sure. The link command doesn't printout any in capability information explicitly
> > > > except for the MCS details. And figuring out the mode of connection (11n/11ax)
> > > > from the MCS is tricky as the MCS varies across depending on the rate
> > > > control algorithm
> > > > (for iwlwifi: hardware). So, I was suggesting to use iperf (the more
> > > > data you pass, more
> > > > chance of the rate control algo to go to higher MCSes) and also by
> > > > "clean channels" I was
> > > > referring to quieter channels where there are no other BSSes or no
> > > > other traffic.
> > > >
> > > > But, before we go into debugging data path, I still don't understand
> > > > why wpa_supplicant
> > > > isn't saying it is a HE association?
> > > >
> > > > Ah, After staring at the code and using blame, a crucial fix missed
> > > > out hostap-2.9 windows,
> > > > the fix was to properly validate the HE capabilities, I was looking at
> > > > the latest cod and
> > > > everything looked fine, hence took time.
> > > >
> > > > hostap_2_9-> 7th August
> > > > 0497e4148197fb8fdf92b5c901ce06df1bfa548c ->13th August
> > > >
> > > > Please use the latest HEAD of hostap.git, you need to compile it
> > > > manually and try the
> > > > test and let me know how it goes. (make sure all proper configs are enabled)
> > > >
> > > > > > On Wed, Sep 2, 2020 at 3:39 PM Krishna Chaitanya
> > > > > > <chaitanya.mgit at gmail.com> wrote:
> > > > > > >
> > > > > > > On Wed, Sep 2, 2020 at 6:38 PM Sugandh Huthanahally Mohan
> > > > > > > <sugandhgowda at gmail.com> wrote:
> > > > > > > >
> > > > > > > > On Wed, Sep 2, 2020 at 3:16 PM Sugandh Huthanahally Mohan
> > > > > > > > <sugandhgowda at gmail.com> wrote:
> > > > > > > > >
> > > > > > > > > On Tue, Sep 1, 2020 at 10:09 PM Krishna Chaitanya
> > > > > > > > > <chaitanya.mgit at gmail.com> wrote:
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > > Well, not necessarily, but hostap side it looks fine, so,
> > > > > > > > > > we need to see why the STA isn't responding well, probably a
> > > > > > > > > > different draft implementation. At the very least we should start
> > > > > > > > > > with a sniffer capture of the association b/w the stations to check
> > > > > > > > > > the IEs.
> > > > > > > > >
> > > > > > > > > I am using wpa_supplicant in STA to connect to AP.
> > > > > > > > > I am attaching hostapd logs and wpa_supplicant logs.
> > > > > > > > > I am observing that the STA is connecting and disconnecting when
> > > > > > > > > I try to connect STA to AP.
> > > > > > > > I guess this is a new STA with wpa_supplicant, right? Is it also AX200 based
> > > > > > > > chipset? In the STA mode, the kernel adds the HE IEs (either mac80211
> > > > > > > > or the driver),
> > > > > > > > so, but interestingly in your previous dmesg, I don't see any mac80211 logs.
> > > > > > > >
> > > > > > > > So, need dmesg logs that capture the connection (look for mac80211 logs).
> > > > > > > > >
> > > > > > > > > On Tue, Sep 1, 2020 at 10:09 PM Krishna Chaitanya
> > > > > > > > > <chaitanya.mgit at gmail.com> wrote:
> > > > > > > > > >
> > > > > > > > > > On Wed, Sep 2, 2020 at 1:23 AM Sugandh Huthanahally Mohan
> > > > > > > > > > <sugandhgowda at gmail.com> wrote:
> > > > > > > > > > >
> > > > > > > > > > > Hi Krishna,
> > > > > > > > > > >
> > > > > > > > > > > Currently I am not running wpa_supplicant.
> > > > > > > > > > > Is it necessary for hostapd?
> > > > > > > > > >
> > > > > > > > > > Well, not necessarily, but hostap side it looks fine, so,
> > > > > > > > > > we need to see why the STA isn't responding well, probably a
> > > > > > > > > > different draft implementation. At the very least we should start
> > > > > > > > > > with a sniffer capture of the association b/w the stations to check
> > > > > > > > > > the IEs.
> > > > > > > >
> > > > > > > > Yes this is a new STA connecting AP with wpa_supplicant.
> > > > > > > > It is also an AX200.
> > > > > > > > I don’t see mac80211 logs on the STA dmesg.
> > > > > > > > I am attaching dmesg of the station.
> > > > > > >
> > > > > > > These are from mac80211:
> > > > > > > [ 152.255545] wlp3s0: authenticate with 8c:c6:81:69:86:65
> > > > > > > [ 152.258347] wlp3s0: send auth to 8c:c6:81:69:86:65 (try 1/3)
> > > > > > > [ 152.283971] wlp3s0: authenticated
> > > > > > > [ 152.286624] wlp3s0: associate with 8c:c6:81:69:86:65 (try 1/3)
> > > > > > > [ 152.293456] wlp3s0: RX AssocResp from 8c:c6:81:69:86:65
> > > > > > > (capab=0x411 status=0 aid=1)
> > > > > > > [ 152.299672] wlp3s0: associated
> > > > > > > [ 152.364843] IPv6: ADDRCONF(NETDEV_CHANGE): wlp3s0: link becomes ready
> > > > > > >
> > > > > > > I was hoping to see some prints disabling HE, but looks fine. So,
> > > > > > > still, nothing from the logs
> > > > > > > to say why HE is disabled in the STA (why it isn't sending HE IEs in
> > > > > > > assoc resp).
> > > > > > >
> > > > > > > Only Sniffer should tell us without resorting to Whitebox debug.
> > > > > > > >
> > > > > > > > On Wed, Sep 2, 2020 at 1:26 PM Krishna Chaitanya
> > > > > > > > <chaitanya.mgit at gmail.com> wrote:
> > > > > > > > >
> > > > > > > > > On Wed, Sep 2, 2020 at 3:16 PM Sugandh Huthanahally Mohan
> > > > > > > > > <sugandhgowda at gmail.com> wrote:
> > > > > > > > > >
> > > > > > > > > > On Tue, Sep 1, 2020 at 10:09 PM Krishna Chaitanya
> > > > > > > > > > <chaitanya.mgit at gmail.com> wrote:
> > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > > Well, not necessarily, but hostap side it looks fine, so,
> > > > > > > > > > > we need to see why the STA isn't responding well, probably a
> > > > > > > > > > > different draft implementation. At the very least we should start
> > > > > > > > > > > with a sniffer capture of the association b/w the stations to check
> > > > > > > > > > > the IEs.
> > > > > > > > > >
> > > > > > > > > > I am using wpa_supplicant in STA to connect to AP.
> > > > > > > > > > I am attaching hostapd logs and wpa_supplicant logs.
> > > > > > > > > > I am observing that the STA is connecting and disconnecting when
> > > > > > > > > > I try to connect STA to AP.
> > > > > > > > > I guess this is a new STA with wpa_supplicant, right? Is it also AX200 based
> > > > > > > > > chipset? In the STA mode, the kernel adds the HE IEs (either mac80211
> > > > > > > > > or the driver),
> > > > > > > > > so, but interestingly in your previous dmesg, I don't see any mac80211 logs.
> > > > > > > > >
> > > > > > > > > So, need dmesg logs that capture the connection (look for mac80211 logs).
> > > > > > > > > >
> > > > > > > > > > On Tue, Sep 1, 2020 at 10:09 PM Krishna Chaitanya
> > > > > > > > > > <chaitanya.mgit at gmail.com> wrote:
> > > > > > > > > > >
> > > > > > > > > > > On Wed, Sep 2, 2020 at 1:23 AM Sugandh Huthanahally Mohan
> > > > > > > > > > > <sugandhgowda at gmail.com> wrote:
> > > > > > > > > > > >
> > > > > > > > > > > > Hi Krishna,
> > > > > > > > > > > >
> > > > > > > > > > > > Currently I am not running wpa_supplicant.
> > > > > > > > > > > > Is it necessary for hostapd?
> > > > > > > > > > >
> > > > > > > > > > > Well, not necessarily, but hostap side it looks fine, so,
> > > > > > > > > > > we need to see why the STA isn't responding well, probably a
> > > > > > > > > > > different draft implementation. At the very least we should start
> > > > > > > > > > > with a sniffer capture of the association b/w the stations to check
> > > > > > > > > > > the IEs.
> > > > > > > > >
> > > > > > > > >
> > > > > > > > >
> > > > > > > > > --
> > > > > > > > > Thanks,
> > > > > > > > > Regards,
> > > > > > > > > Chaitanya T K.
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > --
> > > > > > > Thanks,
> > > > > > > Regards,
> > > > > > > Chaitanya T K.
> > > > >
> > > > >
> > > > > On Tue, Sep 8, 2020 at 9:55 PM Krishna Chaitanya
> > > > > <chaitanya.mgit@gmail.com> wrote:
> > > > > >
> > > > > > On Wed, Sep 9, 2020 at 12:27 AM Sugandh Huthanahally Mohan
> > > > > > <sugandhgowda@gmail.com> wrote:
> > > > > > >
> > > > > > > I have captured connection between a WiFi6 AP and a WiFi6 STA in wireshark.
> > > > > > > I have attached a wireshark pcap file.
> > > > > > > I could see HE capabilities exchange in Association request and response.
> > > > > > Yes, this looks fine to me except for VHT IEs in the probe and
> > > > > > association response in 2.4GHz.
> > > > > > Maybe this is what is confusing, can you please disable ieee80211ac=0
> > > > > > in the hostapd.conf and try?
> > > > > >
> > > > > > > The iw phy output is below. I couldn't see HE connection in this output.
> > > > > > >
> > > > > > > $iw dev wlp3s0 link
> > > > > > > Connected to 8c:c6:81:69:86:65 (on wlp3s0)
> > > > > > > SSID: WiFi_AX200
> > > > > > > freq: 2437
> > > > > > > RX: 27838 bytes (199 packets)
> > > > > > > TX: 13319 bytes (97 packets)
> > > > > > > signal: -34 dBm
> > > > > > > rx bitrate: 26.0 MBit/s MCS 3
> > > > > > > tx bitrate: 2.0 MBit/s
> > > > > > >
> > > > > > > bss flags: short-slot-time
> > > > > > > dtim period: 2
> > > > > > > beacon int: 100
> > > > > > >
> > > > > > The link doesn't show any specific details related to HE other than
> > > > > > the MCS which can vary, try running
> > > > > > an iperf to see HE MCSes in a clean channel.
> > > > > > >
> > > > > > > On Wed, Sep 2, 2020 at 3:39 PM Krishna Chaitanya
> > > > > > > <chaitanya.mgit@gmail.com> wrote:
> > > > > > > >
> > > > > > > > On Wed, Sep 2, 2020 at 6:38 PM Sugandh Huthanahally Mohan
> > > > > > > > <sugandhgowda@gmail.com> wrote:
> > > > > > > > >
> > > > > > > > > On Wed, Sep 2, 2020 at 3:16 PM Sugandh Huthanahally Mohan
> > > > > > > > > <sugandhgowda at gmail.com> wrote:
> > > > > > > > > >
> > > > > > > > > > On Tue, Sep 1, 2020 at 10:09 PM Krishna Chaitanya
> > > > > > > > > > <chaitanya.mgit at gmail.com> wrote:
> > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > > Well, not necessarily, but hostap side it looks fine, so,
> > > > > > > > > > > we need to see why the STA isn't responding well, probably a
> > > > > > > > > > > different draft implementation. At the very least we should start
> > > > > > > > > > > with a sniffer capture of the association b/w the stations to check
> > > > > > > > > > > the IEs.
> > > > > > > > > >
> > > > > > > > > > I am using wpa_supplicant in STA to connect to AP.
> > > > > > > > > > I am attaching hostapd logs and wpa_supplicant logs.
> > > > > > > > > > I am observing that the STA is connecting and disconnecting when
> > > > > > > > > > I try to connect STA to AP.
> > > > > > > > > I guess this is a new STA with wpa_supplicant, right? Is it also AX200 based
> > > > > > > > > chipset? In the STA mode, the kernel adds the HE IEs (either mac80211
> > > > > > > > > or the driver),
> > > > > > > > > so, but interestingly in your previous dmesg, I don't see any mac80211 logs.
> > > > > > > > >
> > > > > > > > > So, need dmesg logs that capture the connection (look for mac80211 logs).
> > > > > > > > > >
> > > > > > > > > > On Tue, Sep 1, 2020 at 10:09 PM Krishna Chaitanya
> > > > > > > > > > <chaitanya.mgit at gmail.com> wrote:
> > > > > > > > > > >
> > > > > > > > > > > On Wed, Sep 2, 2020 at 1:23 AM Sugandh Huthanahally Mohan
> > > > > > > > > > > <sugandhgowda at gmail.com> wrote:
> > > > > > > > > > > >
> > > > > > > > > > > > Hi Krishna,
> > > > > > > > > > > >
> > > > > > > > > > > > Currently I am not running wpa_supplicant.
> > > > > > > > > > > > Is it necessary for hostapd?
> > > > > > > > > > >
> > > > > > > > > > > Well, not necessarily, but hostap side it looks fine, so,
> > > > > > > > > > > we need to see why the STA isn't responding well, probably a
> > > > > > > > > > > different draft implementation. At the very least we should start
> > > > > > > > > > > with a sniffer capture of the association b/w the stations to check
> > > > > > > > > > > the IEs.
> > > > > > > > >
> > > > > > > > > Yes this is a new STA connecting AP with wpa_supplicant.
> > > > > > > > > It is also an AX200.
> > > > > > > > > I don’t see mac80211 logs on the STA dmesg.
> > > > > > > > > I am attaching dmesg of the station.
> > > > > > > >
> > > > > > > > These are from mac80211:
> > > > > > > > [ 152.255545] wlp3s0: authenticate with 8c:c6:81:69:86:65
> > > > > > > > [ 152.258347] wlp3s0: send auth to 8c:c6:81:69:86:65 (try 1/3)
> > > > > > > > [ 152.283971] wlp3s0: authenticated
> > > > > > > > [ 152.286624] wlp3s0: associate with 8c:c6:81:69:86:65 (try 1/3)
> > > > > > > > [ 152.293456] wlp3s0: RX AssocResp from 8c:c6:81:69:86:65
> > > > > > > > (capab=0x411 status=0 aid=1)
> > > > > > > > [ 152.299672] wlp3s0: associated
> > > > > > > > [ 152.364843] IPv6: ADDRCONF(NETDEV_CHANGE): wlp3s0: link becomes ready
> > > > > > > >
> > > > > > > > I was hoping to see some prints disabling HE, but looks fine. So,
> > > > > > > > still, nothing from the logs
> > > > > > > > to say why HE is disabled in the STA (why it isn't sending HE IEs in
> > > > > > > > assoc resp).
> > > > > > > >
> > > > > > > > Only Sniffer should tell us without resorting to Whitebox debug.
> > > > > > > > >
> > > > > > > > > On Wed, Sep 2, 2020 at 1:26 PM Krishna Chaitanya
> > > > > > > > > <chaitanya.mgit@gmail.com> wrote:
> > > > > > > > > >
> > > > > > > > > > On Wed, Sep 2, 2020 at 3:16 PM Sugandh Huthanahally Mohan
> > > > > > > > > > <sugandhgowda@gmail.com> wrote:
> > > > > > > > > > >
> > > > > > > > > > > On Tue, Sep 1, 2020 at 10:09 PM Krishna Chaitanya
> > > > > > > > > > > <chaitanya.mgit at gmail.com> wrote:
> > > > > > > > > > > >
> > > > > > > > > > > >
> > > > > > > > > > > > Well, not necessarily, but hostap side it looks fine, so,
> > > > > > > > > > > > we need to see why the STA isn't responding well, probably a
> > > > > > > > > > > > different draft implementation. At the very least we should start
> > > > > > > > > > > > with a sniffer capture of the association b/w the stations to check
> > > > > > > > > > > > the IEs.
> > > > > > > > > > >
> > > > > > > > > > > I am using wpa_supplicant in STA to connect to AP.
> > > > > > > > > > > I am attaching hostapd logs and wpa_supplicant logs.
> > > > > > > > > > > I am observing that the STA is connecting and disconnecting when
> > > > > > > > > > > I try to connect STA to AP.
> > > > > > > > > > I guess this is a new STA with wpa_supplicant, right? Is it also AX200 based
> > > > > > > > > > chipset? In the STA mode, the kernel adds the HE IEs (either mac80211
> > > > > > > > > > or the driver),
> > > > > > > > > > so, but interestingly in your previous dmesg, I don't see any mac80211 logs.
> > > > > > > > > >
> > > > > > > > > > So, need dmesg logs that capture the connection (look for mac80211 logs).
> > > > > > > > > > >
> > > > > > > > > > > On Tue, Sep 1, 2020 at 10:09 PM Krishna Chaitanya
> > > > > > > > > > > <chaitanya.mgit@gmail.com> wrote:
> > > > > > > > > > > >
> > > > > > > > > > > > On Wed, Sep 2, 2020 at 1:23 AM Sugandh Huthanahally Mohan
> > > > > > > > > > > > <sugandhgowda@gmail.com> wrote:
> > > > > > > > > > > > >
> > > > > > > > > > > > > Hi Krishna,
> > > > > > > > > > > > >
> > > > > > > > > > > > > Currently I am not running wpa_supplicant.
> > > > > > > > > > > > > Is it necessary for hostapd?
> > > > > > > > > > > >
> > > > > > > > > > > > Well, not necessarily, but hostap side it looks fine, so,
> > > > > > > > > > > > we need to see why the STA isn't responding well, probably a
> > > > > > > > > > > > different draft implementation. At the very least we should start
> > > > > > > > > > > > with a sniffer capture of the association b/w the stations to check
> > > > > > > > > > > > the IEs.
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > > --
> > > > > > > > > > Thanks,
> > > > > > > > > > Regards,
> > > > > > > > > > Chaitanya T K.
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > > --
> > > > > > > > Thanks,
> > > > > > > > Regards,
> > > > > > > > Chaitanya T K.
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: Configuring WiFi6 in hostapd
2020-09-11 15:07 ` Configuring WiFi6 in hostapd Krishna Chaitanya
@ 2020-09-11 17:10 ` Johannes Berg
2020-09-11 19:26 ` Krishna Chaitanya
0 siblings, 1 reply; 9+ messages in thread
From: Johannes Berg @ 2020-09-11 17:10 UTC (permalink / raw)
To: Krishna Chaitanya, Sugandh Huthanahally Mohan, linux-wireless,
Emmanuel Grumbach, luciano.coelho
Cc: Cedric Izoard, Hostap
On Fri, 2020-09-11 at 20:37 +0530, Krishna Chaitanya wrote:
> > [ 228.315290] iwlwifi 0000:03:00.0: 0x00002078 | ADVANCED_SYSASSERT
> > [ 228.315294] iwlwifi 0000:03:00.0: 0x00A0A200 | trm_hw_status0
> > [ 228.315297] iwlwifi 0000:03:00.0: 0x00000000 | trm_hw_status1
> > [ 228.315300] iwlwifi 0000:03:00.0: 0x004F8E3C | branchlink2
> > [ 228.315303] iwlwifi 0000:03:00.0: 0x004E4FF4 | interruptlink1
> > [ 228.315307] iwlwifi 0000:03:00.0: 0x004E4FF4 | interruptlink2
> > [ 228.315310] iwlwifi 0000:03:00.0: 0x07000101 | data1
> > [ 228.315313] iwlwifi 0000:03:00.0: 0x48308403 | data2
> > [ 228.315316] iwlwifi 0000:03:00.0: 0x00000005 | data3
This means that we got an invalid TX rate, notably an HE rate was
requested/configured on a MAC configuration that didn't have HE.
I think I saw some patches in this area (configuring the MAC to be HE)
fly by internally recently, but not sure... Luca probably knows.
johannes
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: Configuring WiFi6 in hostapd
2020-09-11 17:10 ` Johannes Berg
@ 2020-09-11 19:26 ` Krishna Chaitanya
2020-09-16 21:31 ` Krishna Chaitanya
0 siblings, 1 reply; 9+ messages in thread
From: Krishna Chaitanya @ 2020-09-11 19:26 UTC (permalink / raw)
To: Johannes Berg
Cc: Sugandh Huthanahally Mohan, linux-wireless, Emmanuel Grumbach,
luciano.coelho, Cedric Izoard, Hostap
On Fri, Sep 11, 2020 at 10:41 PM Johannes Berg
<johannes@sipsolutions.net> wrote:
>
> On Fri, 2020-09-11 at 20:37 +0530, Krishna Chaitanya wrote:
>
> > > [ 228.315290] iwlwifi 0000:03:00.0: 0x00002078 | ADVANCED_SYSASSERT
> > > [ 228.315294] iwlwifi 0000:03:00.0: 0x00A0A200 | trm_hw_status0
> > > [ 228.315297] iwlwifi 0000:03:00.0: 0x00000000 | trm_hw_status1
> > > [ 228.315300] iwlwifi 0000:03:00.0: 0x004F8E3C | branchlink2
> > > [ 228.315303] iwlwifi 0000:03:00.0: 0x004E4FF4 | interruptlink1
> > > [ 228.315307] iwlwifi 0000:03:00.0: 0x004E4FF4 | interruptlink2
> > > [ 228.315310] iwlwifi 0000:03:00.0: 0x07000101 | data1
> > > [ 228.315313] iwlwifi 0000:03:00.0: 0x48308403 | data2
> > > [ 228.315316] iwlwifi 0000:03:00.0: 0x00000005 | data3
>
> This means that we got an invalid TX rate, notably an HE rate was
> requested/configured on a MAC configuration that didn't have HE.
>
> I think I saw some patches in this area (configuring the MAC to be HE)
> fly by internally recently, but not sure... Luca probably knows.
Ah okay. This was reported on 5.4 kernel, do you think is it worth
trying on latest iwlwifi-next tree? Or as you are referring to the internal tree
the issue is present in the latest as well?
> johannes
>
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: Configuring WiFi6 in hostapd
2020-09-11 19:26 ` Krishna Chaitanya
@ 2020-09-16 21:31 ` Krishna Chaitanya
2020-09-23 8:16 ` Coelho, Luciano
0 siblings, 1 reply; 9+ messages in thread
From: Krishna Chaitanya @ 2020-09-16 21:31 UTC (permalink / raw)
To: Johannes Berg
Cc: Sugandh Huthanahally Mohan, linux-wireless, Emmanuel Grumbach,
Luciano Coelho, Cedric Izoard, Hostap
On Sat, Sep 12, 2020 at 12:56 AM Krishna Chaitanya
<chaitanya.mgit@gmail.com> wrote:
>
> On Fri, Sep 11, 2020 at 10:41 PM Johannes Berg
> <johannes@sipsolutions.net> wrote:
> >
> > On Fri, 2020-09-11 at 20:37 +0530, Krishna Chaitanya wrote:
> >
> > > > [ 228.315290] iwlwifi 0000:03:00.0: 0x00002078 | ADVANCED_SYSASSERT
> > > > [ 228.315294] iwlwifi 0000:03:00.0: 0x00A0A200 | trm_hw_status0
> > > > [ 228.315297] iwlwifi 0000:03:00.0: 0x00000000 | trm_hw_status1
> > > > [ 228.315300] iwlwifi 0000:03:00.0: 0x004F8E3C | branchlink2
> > > > [ 228.315303] iwlwifi 0000:03:00.0: 0x004E4FF4 | interruptlink1
> > > > [ 228.315307] iwlwifi 0000:03:00.0: 0x004E4FF4 | interruptlink2
> > > > [ 228.315310] iwlwifi 0000:03:00.0: 0x07000101 | data1
> > > > [ 228.315313] iwlwifi 0000:03:00.0: 0x48308403 | data2
> > > > [ 228.315316] iwlwifi 0000:03:00.0: 0x00000005 | data3
> >
> > This means that we got an invalid TX rate, notably an HE rate was
> > requested/configured on a MAC configuration that didn't have HE.
> >
> > I think I saw some patches in this area (configuring the MAC to be HE)
> > fly by internally recently, but not sure... Luca probably knows.
> Ah okay. This was reported on 5.4 kernel, do you think is it worth
> trying on latest iwlwifi-next tree? Or as you are referring to the internal tree
> the issue is present in the latest as well?
Hi Luca,
Can you please take a look? Any help is appreciated.
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: Configuring WiFi6 in hostapd
2020-09-16 21:31 ` Krishna Chaitanya
@ 2020-09-23 8:16 ` Coelho, Luciano
2020-09-23 8:36 ` Coelho, Luciano
0 siblings, 1 reply; 9+ messages in thread
From: Coelho, Luciano @ 2020-09-23 8:16 UTC (permalink / raw)
To: johannes, chaitanya.mgit
Cc: linux-wireless, sugandhgowda, Grumbach, Emmanuel, Cedric.Izoard, Hostap
On Thu, 2020-09-17 at 03:01 +0530, Krishna Chaitanya wrote:
> On Sat, Sep 12, 2020 at 12:56 AM Krishna Chaitanya
> <chaitanya.mgit@gmail.com> wrote:
> > On Fri, Sep 11, 2020 at 10:41 PM Johannes Berg
> > <johannes@sipsolutions.net> wrote:
> > > On Fri, 2020-09-11 at 20:37 +0530, Krishna Chaitanya wrote:
> > >
> > > > > [ 228.315290] iwlwifi 0000:03:00.0: 0x00002078 | ADVANCED_SYSASSERT
> > > > > [ 228.315294] iwlwifi 0000:03:00.0: 0x00A0A200 | trm_hw_status0
> > > > > [ 228.315297] iwlwifi 0000:03:00.0: 0x00000000 | trm_hw_status1
> > > > > [ 228.315300] iwlwifi 0000:03:00.0: 0x004F8E3C | branchlink2
> > > > > [ 228.315303] iwlwifi 0000:03:00.0: 0x004E4FF4 | interruptlink1
> > > > > [ 228.315307] iwlwifi 0000:03:00.0: 0x004E4FF4 | interruptlink2
> > > > > [ 228.315310] iwlwifi 0000:03:00.0: 0x07000101 | data1
> > > > > [ 228.315313] iwlwifi 0000:03:00.0: 0x48308403 | data2
> > > > > [ 228.315316] iwlwifi 0000:03:00.0: 0x00000005 | data3
> > >
> > > This means that we got an invalid TX rate, notably an HE rate was
> > > requested/configured on a MAC configuration that didn't have HE.
> > >
> > > I think I saw some patches in this area (configuring the MAC to be HE)
> > > fly by internally recently, but not sure... Luca probably knows.
> > Ah okay. This was reported on 5.4 kernel, do you think is it worth
> > trying on latest iwlwifi-next tree? Or as you are referring to the internal tree
> > the issue is present in the latest as well?
> Hi Luca,
>
> Can you please take a look? Any help is appreciated.
Hi,
There have been some new patches in this area, but after a quick look I
didn't find anything specific that jumps out. I'll take a closer look
and let you know if I find anything.
--
Cheers,
Luca.
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: Configuring WiFi6 in hostapd
2020-09-23 8:16 ` Coelho, Luciano
@ 2020-09-23 8:36 ` Coelho, Luciano
2020-09-23 17:40 ` Ben Greear
[not found] ` <CAD_iCC8qJ_Xaa5yjkdzapGCtJsAt2VbYzTfgpUDCeT7RpyrBjw@mail.gmail.com>
0 siblings, 2 replies; 9+ messages in thread
From: Coelho, Luciano @ 2020-09-23 8:36 UTC (permalink / raw)
To: johannes, chaitanya.mgit
Cc: linux-wireless, sugandhgowda, Grumbach, Emmanuel, Cedric.Izoard, Hostap
On Wed, 2020-09-23 at 11:16 +0300, Luciano Coelho wrote:
> On Thu, 2020-09-17 at 03:01 +0530, Krishna Chaitanya wrote:
> > On Sat, Sep 12, 2020 at 12:56 AM Krishna Chaitanya
> > <chaitanya.mgit@gmail.com> wrote:
> > > On Fri, Sep 11, 2020 at 10:41 PM Johannes Berg
> > > <johannes@sipsolutions.net> wrote:
> > > > On Fri, 2020-09-11 at 20:37 +0530, Krishna Chaitanya wrote:
> > > >
> > > > > > [ 228.315290] iwlwifi 0000:03:00.0: 0x00002078 | ADVANCED_SYSASSERT
> > > > > > [ 228.315294] iwlwifi 0000:03:00.0: 0x00A0A200 | trm_hw_status0
> > > > > > [ 228.315297] iwlwifi 0000:03:00.0: 0x00000000 | trm_hw_status1
> > > > > > [ 228.315300] iwlwifi 0000:03:00.0: 0x004F8E3C | branchlink2
> > > > > > [ 228.315303] iwlwifi 0000:03:00.0: 0x004E4FF4 | interruptlink1
> > > > > > [ 228.315307] iwlwifi 0000:03:00.0: 0x004E4FF4 | interruptlink2
> > > > > > [ 228.315310] iwlwifi 0000:03:00.0: 0x07000101 | data1
> > > > > > [ 228.315313] iwlwifi 0000:03:00.0: 0x48308403 | data2
> > > > > > [ 228.315316] iwlwifi 0000:03:00.0: 0x00000005 | data3
> > > >
> > > > This means that we got an invalid TX rate, notably an HE rate was
> > > > requested/configured on a MAC configuration that didn't have HE.
> > > >
> > > > I think I saw some patches in this area (configuring the MAC to be HE)
> > > > fly by internally recently, but not sure... Luca probably knows.
> > > Ah okay. This was reported on 5.4 kernel, do you think is it worth
> > > trying on latest iwlwifi-next tree? Or as you are referring to the internal tree
> > > the issue is present in the latest as well?
> > Hi Luca,
> >
> > Can you please take a look? Any help is appreciated.
>
> Hi,
>
> There have been some new patches in this area, but after a quick look I
> didn't find anything specific that jumps out. I'll take a closer look
> and let you know if I find anything.
In the meantime, you could try our public backport-iwlwifi tree, where
most of the internal tree is published:
https://git.kernel.org/pub/scm/linux/kernel/git/iwlwifi/backport-iwlwifi.git/
This is an out-of-tree driver, based on the linux-backports project.
You could try the core56 branch, for instance, or even master and
check if the problem is still there. If not, we can try to look for
the patch that fixes it and push it to stable.
--
Cheers,
Luca.
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: Configuring WiFi6 in hostapd
2020-09-23 8:36 ` Coelho, Luciano
@ 2020-09-23 17:40 ` Ben Greear
[not found] ` <CAD_iCC_iVN8HgCM=g+8MrLJVAoApNXtkRgEUgPZCs8_+DiJTyA@mail.gmail.com>
[not found] ` <CAD_iCC8qJ_Xaa5yjkdzapGCtJsAt2VbYzTfgpUDCeT7RpyrBjw@mail.gmail.com>
1 sibling, 1 reply; 9+ messages in thread
From: Ben Greear @ 2020-09-23 17:40 UTC (permalink / raw)
To: Coelho, Luciano, johannes, chaitanya.mgit
Cc: linux-wireless, sugandhgowda, Grumbach, Emmanuel, Cedric.Izoard, Hostap
On 9/23/20 1:36 AM, Coelho, Luciano wrote:
> On Wed, 2020-09-23 at 11:16 +0300, Luciano Coelho wrote:
>> On Thu, 2020-09-17 at 03:01 +0530, Krishna Chaitanya wrote:
>>> On Sat, Sep 12, 2020 at 12:56 AM Krishna Chaitanya
>>> <chaitanya.mgit@gmail.com> wrote:
>>>> On Fri, Sep 11, 2020 at 10:41 PM Johannes Berg
>>>> <johannes@sipsolutions.net> wrote:
>>>>> On Fri, 2020-09-11 at 20:37 +0530, Krishna Chaitanya wrote:
>>>>>
>>>>>>> [ 228.315290] iwlwifi 0000:03:00.0: 0x00002078 | ADVANCED_SYSASSERT
>>>>>>> [ 228.315294] iwlwifi 0000:03:00.0: 0x00A0A200 | trm_hw_status0
>>>>>>> [ 228.315297] iwlwifi 0000:03:00.0: 0x00000000 | trm_hw_status1
>>>>>>> [ 228.315300] iwlwifi 0000:03:00.0: 0x004F8E3C | branchlink2
>>>>>>> [ 228.315303] iwlwifi 0000:03:00.0: 0x004E4FF4 | interruptlink1
>>>>>>> [ 228.315307] iwlwifi 0000:03:00.0: 0x004E4FF4 | interruptlink2
>>>>>>> [ 228.315310] iwlwifi 0000:03:00.0: 0x07000101 | data1
>>>>>>> [ 228.315313] iwlwifi 0000:03:00.0: 0x48308403 | data2
>>>>>>> [ 228.315316] iwlwifi 0000:03:00.0: 0x00000005 | data3
>>>>>
>>>>> This means that we got an invalid TX rate, notably an HE rate was
>>>>> requested/configured on a MAC configuration that didn't have HE.
>>>>>
>>>>> I think I saw some patches in this area (configuring the MAC to be HE)
>>>>> fly by internally recently, but not sure... Luca probably knows.
>>>> Ah okay. This was reported on 5.4 kernel, do you think is it worth
>>>> trying on latest iwlwifi-next tree? Or as you are referring to the internal tree
>>>> the issue is present in the latest as well?
>>> Hi Luca,
>>>
>>> Can you please take a look? Any help is appreciated.
>>
>> Hi,
>>
>> There have been some new patches in this area, but after a quick look I
>> didn't find anything specific that jumps out. I'll take a closer look
>> and let you know if I find anything.
>
> In the meantime, you could try our public backport-iwlwifi tree, where
> most of the internal tree is published:
>
> https://git.kernel.org/pub/scm/linux/kernel/git/iwlwifi/backport-iwlwifi.git/
>
> This is an out-of-tree driver, based on the linux-backports project.
> You could try the core56 branch, for instance, or even master and
> check if the problem is still there. If not, we can try to look for
> the patch that fixes it and push it to stable.
I'm curious if anyone is interested in helping to maintain a non-backports version of this,
something like how I did the ath10k-ct driver. I'd like to use this driver, but
don't want to use the rest of the backports funk.
Thanks,
Ben
>
> --
> Cheers,
> Luca.
>
--
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc http://www.candelatech.com
^ permalink raw reply [flat|nested] 9+ messages in thread
* Fwd: Configuring WiFi6 in hostapd
[not found] ` <CAD_iCC_iVN8HgCM=g+8MrLJVAoApNXtkRgEUgPZCs8_+DiJTyA@mail.gmail.com>
@ 2020-09-30 15:41 ` Sugandh Huthanahally Mohan
0 siblings, 0 replies; 9+ messages in thread
From: Sugandh Huthanahally Mohan @ 2020-09-30 15:41 UTC (permalink / raw)
To: Coelho, Luciano, johannes, chaitanya.mgit, linux-wireless,
Grumbach, Emmanuel, Cedric.Izoard, Hostap, Ben Greear
[-- Attachment #1: Type: text/plain, Size: 3321 bytes --]
On Wed, 2020-09-23 at 11:16 +0300, Luciano Coelho wrote:
> On Thu, 2020-09-17 at 03:01 +0530, Krishna Chaitanya wrote:
> > > On Sat, Sep 12, 2020 at 12:56 AM Krishna Chaitanya
> > > <chaitanya.mgit at gmail.com> wrote:
> > > >On Fri, Sep 11, 2020 at 10:41 PM Johannes Berg
> > > > <johannes at sipsolutions.net> wrote:
> > > > >On Fri, 2020-09-11 at 20:37 +0530, Krishna Chaitanya wrote:
> > > > >
> > > > > > > [ 228.315290] iwlwifi 0000:03:00.0: 0x00002078 | ADVANCED_SYSASSERT
> > > > > > > [ 228.315294] iwlwifi 0000:03:00.0: 0x00A0A200 | trm_hw_status0
> > > > > > > [ 228.315297] iwlwifi 0000:03:00.0: 0x00000000 | trm_hw_status1
> > > > > > > [ 228.315300] iwlwifi 0000:03:00.0: 0x004F8E3C | branchlink2
> > > > > > > [ 228.315303] iwlwifi 0000:03:00.0: 0x004E4FF4 | interruptlink1
> > > > > > > [ 228.315307] iwlwifi 0000:03:00.0: 0x004E4FF4 | interruptlink2
> > > > > > > [ 228.315310] iwlwifi 0000:03:00.0: 0x07000101 | data1
> > > > > > > [ 228.315313] iwlwifi 0000:03:00.0: 0x48308403 | data2
> > > > > > > [ 228.315316] iwlwifi 0000:03:00.0: 0x00000005 | data3
> > > > >
> > > > > This means that we got an invalid TX rate, notably an HE rate was
> > > > > requested/configured on a MAC configuration that didn't have HE.
> > > > >
> > > > > I think I saw some patches in this area (configuring the MAC to be HE)
> > > > > fly by internally recently, but not sure... Luca probably knows.
> > > > Ah okay. This was reported on 5.4 kernel, do you think is it worth
> > > > trying on latest iwlwifi-next tree? Or as you are referring to the internal tree
> > > > the issue is present in the latest as well?
> > > Hi Luca,
> > >
> > > Can you please take a look? Any help is appreciated.
> >
> > Hi,
> >
> > There have been some new patches in this area, but after a quick look I
> > didn't find anything specific that jumps out. I'll take a closer look
> > and let you know if I find anything.
> In the meantime, you could try our public backport-iwlwifi tree, where
> most of the internal tree is published:
>
> https://git.kernel.org/pub/scm/linux/kernel/git/iwlwifi/backport-iwlwifi.git/
>
> This is an out-of-tree driver, based on the linux-backports project.
> You could try the core56 branch, for instance, or even master and
> check if the problem is still there. If not, we can try to look for
> the patch that fixes it and push it to stable.
> --
> Cheers,
> Luca.
Hello Luca,
I used public backport iwlwifi tree with core56 branch as you suggested.
I am still observing the crash which I reported earlier.
Also I upgraded my linux kernel to 5.8 and tried , but still observing
the same crash.
I am attaching the dmesg.
Also when I run hostapd_cli (see below for output )on my AP, I could
see HE flag.
>all_sta
8c:c6:81:69:86:65
flags=[AUTH][SHORT_PREAMBLE][WMM][HT][HE]
aid=1
capability=0x431
listen_interval=10
supported_rates=02 04 0b 16 0c 12 18 24 30 48 60 6c
timeout_next=NULLFUNC POLL
dot11RSNAStatsSTAAddress=8c:c6:81:69:86:65
dot11RSNAStatsVersion=1
dot11RSNAStatsSelectedPairwiseCipher=00-0f-ac-4
dot11RSNAStatsTKIPLocalMICFailures=0
dot11RSNAStatsTKIPRemoteMICFailures=0
wpa=2
AKMSuiteSelector=00-0f-ac-2
hostapdWPAPTKState=0
hostapdWPAPTKGroupState=0
supp_op_classes=51515354737475767778797a7b7c7d7e7f
ht_caps_info=0x19e7
ext_capab=04004000010000400020
Regards,
Sugandh
[-- Attachment #2: dmesg --]
[-- Type: application/octet-stream, Size: 126362 bytes --]
$ dmesg
dmesg: read kernel buffer failed: Operation not permitted
wifitsn@for1700:~$ sudo dmesg
[sudo] password for wifitsn:
[ 0.000000] microcode: microcode updated early to revision 0xdc, date = 2020-04-27
[ 0.000000] Linux version 5.8.0-050800-generic (kernel@kathleen) (gcc (Ubuntu 10.2.0-3ubuntu1) 10.2.0, GNU ld (GNU Binutils for Ubuntu) 2.35) #202008022230 SMP Sun Aug 2 22:33:21 UTC 2020
[ 0.000000] Command line: BOOT_IMAGE=/vmlinuz-5.8.0-050800-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
[ 0.000000] KERNEL supported cpus:
[ 0.000000] Intel GenuineIntel
[ 0.000000] AMD AuthenticAMD
[ 0.000000] Hygon HygonGenuine
[ 0.000000] Centaur CentaurHauls
[ 0.000000] zhaoxin Shanghai
[ 0.000000] x86/fpu: Supporting XSAVE feature 0x001: 'x87 floating point registers'
[ 0.000000] x86/fpu: Supporting XSAVE feature 0x002: 'SSE registers'
[ 0.000000] x86/fpu: Supporting XSAVE feature 0x004: 'AVX registers'
[ 0.000000] x86/fpu: Supporting XSAVE feature 0x008: 'MPX bounds registers'
[ 0.000000] x86/fpu: Supporting XSAVE feature 0x010: 'MPX CSR'
[ 0.000000] x86/fpu: xstate_offset[2]: 576, xstate_sizes[2]: 256
[ 0.000000] x86/fpu: xstate_offset[3]: 832, xstate_sizes[3]: 64
[ 0.000000] x86/fpu: xstate_offset[4]: 896, xstate_sizes[4]: 64
[ 0.000000] x86/fpu: Enabled xstate features 0x1f, context size is 960 bytes, using 'compacted' format.
[ 0.000000] BIOS-provided physical RAM map:
[ 0.000000] BIOS-e820: [mem 0x0000000000000000-0x0000000000057fff] usable
[ 0.000000] BIOS-e820: [mem 0x0000000000058000-0x0000000000058fff] reserved
[ 0.000000] BIOS-e820: [mem 0x0000000000059000-0x000000000009cfff] usable
[ 0.000000] BIOS-e820: [mem 0x000000000009d000-0x00000000000fffff] reserved
[ 0.000000] BIOS-e820: [mem 0x0000000000100000-0x00000000abdc0fff] usable
[ 0.000000] BIOS-e820: [mem 0x00000000abdc1000-0x00000000abdc1fff] ACPI NVS
[ 0.000000] BIOS-e820: [mem 0x00000000abdc2000-0x00000000abe0bfff] reserved
[ 0.000000] BIOS-e820: [mem 0x00000000abe0c000-0x00000000b561dfff] usable
[ 0.000000] BIOS-e820: [mem 0x00000000b561e000-0x00000000b7eadfff] reserved
[ 0.000000] BIOS-e820: [mem 0x00000000b7eae000-0x00000000b7fadfff] ACPI NVS
[ 0.000000] BIOS-e820: [mem 0x00000000b7fae000-0x00000000b7ffdfff] ACPI data
[ 0.000000] BIOS-e820: [mem 0x00000000b7ffe000-0x00000000b7ffefff] usable
[ 0.000000] BIOS-e820: [mem 0x00000000b7fff000-0x00000000b80fffff] reserved
[ 0.000000] BIOS-e820: [mem 0x00000000b8600000-0x00000000bc7fffff] reserved
[ 0.000000] BIOS-e820: [mem 0x00000000f80fa000-0x00000000f80fafff] reserved
[ 0.000000] BIOS-e820: [mem 0x00000000f80fd000-0x00000000f80fdfff] reserved
[ 0.000000] BIOS-e820: [mem 0x00000000fe000000-0x00000000fe010fff] reserved
[ 0.000000] BIOS-e820: [mem 0x0000000100000000-0x00000004417fffff] usable
[ 0.000000] NX (Execute Disable) protection: active
[ 0.000000] efi: EFI v2.40 by Lenovo
[ 0.000000] efi: SMBIOS=0xb6f6a000 ACPI=0xb7ffd000 ACPI 2.0=0xb7ffd014 ESRT=0xb6ddf000 RNG=0xb6dfba98 TPMEventLog=0xabf0b018
[ 0.000000] efi: seeding entropy pool
[ 0.000000] random: fast init done
[ 0.000000] [Firmware Bug]: TPM Final Events table missing or invalid
[ 0.000000] SMBIOS 2.8 present.
[ 0.000000] DMI: LENOVO 20FWCTO1WW/20FWCTO1WW, BIOS R07ET91W (2.31 ) 12/11/2019
[ 0.000000] tsc: Detected 2600.000 MHz processor
[ 0.000949] tsc: Detected 2599.992 MHz TSC
[ 0.000949] e820: update [mem 0x00000000-0x00000fff] usable ==> reserved
[ 0.000953] e820: remove [mem 0x000a0000-0x000fffff] usable
[ 0.000966] last_pfn = 0x441800 max_arch_pfn = 0x400000000
[ 0.000974] MTRR default type: write-back
[ 0.000976] MTRR fixed ranges enabled:
[ 0.000978] 00000-9FFFF write-back
[ 0.000980] A0000-BFFFF uncachable
[ 0.000982] C0000-FFFFF write-protect
[ 0.000983] MTRR variable ranges enabled:
[ 0.000986] 0 base 00C0000000 mask 7FC0000000 uncachable
[ 0.000988] 1 base 00BC000000 mask 7FFC000000 uncachable
[ 0.000990] 2 base 00BA000000 mask 7FFE000000 uncachable
[ 0.000991] 3 disabled
[ 0.000992] 4 disabled
[ 0.000993] 5 disabled
[ 0.000994] 6 disabled
[ 0.000995] 7 disabled
[ 0.000996] 8 disabled
[ 0.000997] 9 disabled
[ 0.001567] x86/PAT: Configuration [0-7]: WB WC UC- UC WB WP UC- WT
[ 0.001810] last_pfn = 0xb7fff max_arch_pfn = 0x400000000
[ 0.026857] esrt: Reserving ESRT space from 0x00000000b6ddf000 to 0x00000000b6ddf088.
[ 0.026872] check: Scanning 1 areas for low memory corruption
[ 0.026879] Using GB pages for direct mapping
[ 0.027528] Secure boot disabled
[ 0.027530] RAMDISK: [mem 0x3acaa000-0x3fffdfff]
[ 0.027553] ACPI: Early table checksum verification disabled
[ 0.027558] ACPI: RSDP 0x00000000B7FFD014 000024 (v02 LENOVO)
[ 0.027564] ACPI: XSDT 0x00000000B7FD1188 00010C (v01 LENOVO TP-R07 00000000 PTEC 00000002)
[ 0.027574] ACPI: FACP 0x00000000B7FF1000 0000F4 (v05 LENOVO TP-R07 00002310 PTEC 00000002)
[ 0.027583] ACPI: DSDT 0x00000000B7FDC000 010D9A (v02 LENOVO TP-R07 00002310 INTL 20141107)
[ 0.027589] ACPI: FACS 0x00000000B7F67000 000040
[ 0.027593] ACPI: TCPA 0x00000000B7FFB000 000032 (v02 LENOVO TP-R07 00000002 PTEC 00000002)
[ 0.027598] ACPI: SSDT 0x00000000B7FFA000 0004B7 (v02 LENOVO Tpm2Tabl 00001000 INTL 20141107)
[ 0.027603] ACPI: SSDT 0x00000000B7FF9000 00004B (v02 LENOVO MeSsdt 00003000 INTL 20141107)
[ 0.027609] ACPI: TPM2 0x00000000B7FF8000 000034 (v03 LENOVO TP-R07 00002310 PTEC 00000002)
[ 0.027614] ACPI: UEFI 0x00000000B7F7E000 000042 (v01 LENOVO TP-R07 00002310 PTEC 00000002)
[ 0.027619] ACPI: SSDT 0x00000000B7FF3000 004D97 (v02 LENOVO SaSsdt 00003000 INTL 20141107)
[ 0.027624] ACPI: SSDT 0x00000000B7FF2000 0005C5 (v02 LENOVO PerfTune 00001000 INTL 20141107)
[ 0.027629] ACPI: ECDT 0x00000000B7FF0000 000052 (v01 LENOVO TP-R07 00002310 PTEC 00000002)
[ 0.027634] ACPI: HPET 0x00000000B7FEF000 000038 (v01 LENOVO TP-R07 00002310 PTEC 00000002)
[ 0.027639] ACPI: APIC 0x00000000B7FEE000 0000BC (v03 LENOVO TP-R07 00002310 PTEC 00000002)
[ 0.027644] ACPI: MCFG 0x00000000B7FED000 00003C (v01 LENOVO TP-R07 00002310 PTEC 00000002)
[ 0.027649] ACPI: SSDT 0x00000000B7FDA000 0018D2 (v01 LENOVO SataAhci 00001000 INTL 20141107)
[ 0.027654] ACPI: DBGP 0x00000000B7FD9000 000034 (v01 LENOVO TP-R07 00002310 PTEC 00000002)
[ 0.027659] ACPI: DBG2 0x00000000B7FD8000 000054 (v00 LENOVO TP-R07 00002310 PTEC 00000002)
[ 0.027663] ACPI: BOOT 0x00000000B7FD7000 000028 (v01 LENOVO TP-R07 00002310 PTEC 00000002)
[ 0.027668] ACPI: BATB 0x00000000B7FD6000 00004A (v02 LENOVO TP-R07 00002310 PTEC 00000002)
[ 0.027673] ACPI: SLIC 0x00000000B7FD5000 000176 (v01 LENOVO TP-R07 00002310 PTEC 00000002)
[ 0.027678] ACPI: SSDT 0x00000000B7FD4000 000649 (v02 LENOVO Cpu0Ist 00003000 INTL 20141107)
[ 0.027683] ACPI: SSDT 0x00000000B7FD3000 000E73 (v02 LENOVO CpuSsdt 00003000 INTL 20141107)
[ 0.027688] ACPI: SSDT 0x00000000B7FD2000 0003D9 (v02 LENOVO CtdpB 00001000 INTL 20141107)
[ 0.027693] ACPI: MSDM 0x00000000B7FFC000 000055 (v03 LENOVO TP-R07 00002310 PTEC 00000002)
[ 0.027698] ACPI: SSDT 0x00000000B7FCF000 001005 (v01 LENOVO NvOptTbl 00001000 INTL 20141107)
[ 0.027703] ACPI: SSDT 0x00000000B7FCE000 000732 (v02 LENOVO SgPch 00001000 INTL 20141107)
[ 0.027708] ACPI: DMAR 0x00000000B7FCD000 0000A8 (v01 LENOVO TP-R07 00002310 PTEC 00000002)
[ 0.027713] ACPI: ASF! 0x00000000B7FCC000 0000A5 (v32 LENOVO TP-R07 00002310 PTEC 00000002)
[ 0.027718] ACPI: FPDT 0x00000000B7FCB000 000044 (v01 LENOVO TP-R07 00002310 PTEC 00000002)
[ 0.027723] ACPI: BGRT 0x00000000B7FCA000 000038 (v01 LENOVO TP-R07 00002310 PTEC 00000002)
[ 0.027728] ACPI: UEFI 0x00000000B7F44000 00013E (v01 LENOVO TP-R07 00002310 PTEC 00000002)
[ 0.027742] ACPI: Local APIC address 0xfee00000
[ 0.027866] No NUMA configuration found
[ 0.027868] Faking a node at [mem 0x0000000000000000-0x00000004417fffff]
[ 0.027888] NODE_DATA(0) allocated [mem 0x4417d5000-0x4417fffff]
[ 0.028561] cma: Reserved 32 MiB at 0x000000043f400000
[ 0.028613] Zone ranges:
[ 0.028614] DMA [mem 0x0000000000001000-0x0000000000ffffff]
[ 0.028617] DMA32 [mem 0x0000000001000000-0x00000000ffffffff]
[ 0.028618] Normal [mem 0x0000000100000000-0x00000004417fffff]
[ 0.028620] Device empty
[ 0.028621] Movable zone start for each node
[ 0.028628] Early memory node ranges
[ 0.028629] node 0: [mem 0x0000000000001000-0x0000000000057fff]
[ 0.028631] node 0: [mem 0x0000000000059000-0x000000000009cfff]
[ 0.028632] node 0: [mem 0x0000000000100000-0x00000000abdc0fff]
[ 0.028634] node 0: [mem 0x00000000abe0c000-0x00000000b561dfff]
[ 0.028635] node 0: [mem 0x00000000b7ffe000-0x00000000b7ffefff]
[ 0.028636] node 0: [mem 0x0000000100000000-0x00000004417fffff]
[ 0.029206] Zeroed struct page in unavailable ranges: 37521 pages
[ 0.029208] Initmem setup node 0 [mem 0x0000000000001000-0x00000004417fffff]
[ 0.029211] On node 0 totalpages: 4156783
[ 0.029213] DMA zone: 64 pages used for memmap
[ 0.029214] DMA zone: 21 pages reserved
[ 0.029216] DMA zone: 3995 pages, LIFO batch:0
[ 0.029257] DMA32 zone: 11544 pages used for memmap
[ 0.029259] DMA32 zone: 738772 pages, LIFO batch:63
[ 0.036596] Normal zone: 53344 pages used for memmap
[ 0.036598] Normal zone: 3414016 pages, LIFO batch:63
[ 0.068668] Reserving Intel graphics memory at [mem 0xba800000-0xbc7fffff]
[ 0.068953] ACPI: PM-Timer IO Port: 0x1808
[ 0.068956] ACPI: Local APIC address 0xfee00000
[ 0.068967] ACPI: LAPIC_NMI (acpi_id[0x01] high edge lint[0x1])
[ 0.068968] ACPI: LAPIC_NMI (acpi_id[0x02] high edge lint[0x1])
[ 0.068969] ACPI: LAPIC_NMI (acpi_id[0x03] high edge lint[0x1])
[ 0.068970] ACPI: LAPIC_NMI (acpi_id[0x04] high edge lint[0x1])
[ 0.068971] ACPI: LAPIC_NMI (acpi_id[0x05] high edge lint[0x1])
[ 0.068972] ACPI: LAPIC_NMI (acpi_id[0x06] high edge lint[0x1])
[ 0.068973] ACPI: LAPIC_NMI (acpi_id[0x07] high edge lint[0x1])
[ 0.068974] ACPI: LAPIC_NMI (acpi_id[0x08] high edge lint[0x1])
[ 0.069013] IOAPIC[0]: apic_id 2, version 32, address 0xfec00000, GSI 0-119
[ 0.069017] ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
[ 0.069019] ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
[ 0.069021] ACPI: IRQ0 used by override.
[ 0.069023] ACPI: IRQ9 used by override.
[ 0.069026] Using ACPI (MADT) for SMP configuration information
[ 0.069029] ACPI: HPET id: 0x8086a201 base: 0xfed00000
[ 0.069039] e820: update [mem 0xaec5d000-0xaecedfff] usable ==> reserved
[ 0.069052] TSC deadline timer available
[ 0.069054] smpboot: Allowing 8 CPUs, 0 hotplug CPUs
[ 0.069082] PM: hibernation: Registered nosave memory: [mem 0x00000000-0x00000fff]
[ 0.069084] PM: hibernation: Registered nosave memory: [mem 0x00058000-0x00058fff]
[ 0.069087] PM: hibernation: Registered nosave memory: [mem 0x0009d000-0x000fffff]
[ 0.069089] PM: hibernation: Registered nosave memory: [mem 0xabdc1000-0xabdc1fff]
[ 0.069090] PM: hibernation: Registered nosave memory: [mem 0xabdc2000-0xabe0bfff]
[ 0.069093] PM: hibernation: Registered nosave memory: [mem 0xaec5d000-0xaecedfff]
[ 0.069095] PM: hibernation: Registered nosave memory: [mem 0xb561e000-0xb7eadfff]
[ 0.069096] PM: hibernation: Registered nosave memory: [mem 0xb7eae000-0xb7fadfff]
[ 0.069097] PM: hibernation: Registered nosave memory: [mem 0xb7fae000-0xb7ffdfff]
[ 0.069100] PM: hibernation: Registered nosave memory: [mem 0xb7fff000-0xb80fffff]
[ 0.069101] PM: hibernation: Registered nosave memory: [mem 0xb8100000-0xb85fffff]
[ 0.069102] PM: hibernation: Registered nosave memory: [mem 0xb8600000-0xbc7fffff]
[ 0.069103] PM: hibernation: Registered nosave memory: [mem 0xbc800000-0xf80f9fff]
[ 0.069104] PM: hibernation: Registered nosave memory: [mem 0xf80fa000-0xf80fafff]
[ 0.069105] PM: hibernation: Registered nosave memory: [mem 0xf80fb000-0xf80fcfff]
[ 0.069105] PM: hibernation: Registered nosave memory: [mem 0xf80fd000-0xf80fdfff]
[ 0.069106] PM: hibernation: Registered nosave memory: [mem 0xf80fe000-0xfdffffff]
[ 0.069107] PM: hibernation: Registered nosave memory: [mem 0xfe000000-0xfe010fff]
[ 0.069108] PM: hibernation: Registered nosave memory: [mem 0xfe011000-0xffffffff]
[ 0.069111] [mem 0xbc800000-0xf80f9fff] available for PCI devices
[ 0.069112] Booting paravirtualized kernel on bare hardware
[ 0.069116] clocksource: refined-jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 7645519600211568 ns
[ 0.069127] setup_percpu: NR_CPUS:8192 nr_cpumask_bits:8 nr_cpu_ids:8 nr_node_ids:1
[ 0.069444] percpu: Embedded 56 pages/cpu s192512 r8192 d28672 u262144
[ 0.069456] pcpu-alloc: s192512 r8192 d28672 u262144 alloc=1*2097152
[ 0.069457] pcpu-alloc: [0] 0 1 2 3 4 5 6 7
[ 0.069499] Built 1 zonelists, mobility grouping on. Total pages: 4091810
[ 0.069501] Policy zone: Normal
[ 0.069502] Kernel command line: BOOT_IMAGE=/vmlinuz-5.8.0-050800-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
[ 0.071093] Dentry cache hash table entries: 2097152 (order: 12, 16777216 bytes, linear)
[ 0.071803] Inode-cache hash table entries: 1048576 (order: 11, 8388608 bytes, linear)
[ 0.071941] mem auto-init: stack:off, heap alloc:on, heap free:off
[ 0.136227] Memory: 16039328K/16627132K available (14339K kernel code, 2557K rwdata, 8744K rodata, 2640K init, 4896K bss, 555036K reserved, 32768K cma-reserved)
[ 0.136238] random: get_random_u64 called from kmem_cache_open+0x2b/0x240 with crng_init=1
[ 0.136519] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=8, Nodes=1
[ 0.136546] Kernel/User page tables isolation: enabled
[ 0.136582] ftrace: allocating 48531 entries in 190 pages
[ 0.172659] ftrace: allocated 190 pages with 6 groups
[ 0.172850] rcu: Hierarchical RCU implementation.
[ 0.172852] rcu: RCU restricting CPUs from NR_CPUS=8192 to nr_cpu_ids=8.
[ 0.172853] Trampoline variant of Tasks RCU enabled.
[ 0.172854] Rude variant of Tasks RCU enabled.
[ 0.172855] Tracing variant of Tasks RCU enabled.
[ 0.172857] rcu: RCU calculated value of scheduler-enlistment delay is 25 jiffies.
[ 0.172858] rcu: Adjusting geometry for rcu_fanout_leaf=16, nr_cpu_ids=8
[ 0.179461] NR_IRQS: 524544, nr_irqs: 2048, preallocated irqs: 16
[ 0.180291] random: crng done (trusting CPU's manufacturer)
[ 0.180338] Console: colour dummy device 80x25
[ 0.180345] printk: console [tty0] enabled
[ 0.180379] ACPI: Core revision 20200528
[ 0.180830] clocksource: hpet: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 79635855245 ns
[ 0.180929] APIC: Switch to symmetric I/O mode setup
[ 0.180932] DMAR: Host address width 39
[ 0.180934] DMAR: DRHD base: 0x000000fed90000 flags: 0x0
[ 0.180943] DMAR: dmar0: reg_base_addr fed90000 ver 1:0 cap 1c0000c40660462 ecap 7e3ff0505e
[ 0.180944] DMAR: DRHD base: 0x000000fed91000 flags: 0x1
[ 0.180950] DMAR: dmar1: reg_base_addr fed91000 ver 1:0 cap d2008c40660462 ecap f050da
[ 0.180952] DMAR: RMRR base: 0x000000b742f000 end: 0x000000b744efff
[ 0.180954] DMAR: RMRR base: 0x000000ba000000 end: 0x000000bc7fffff
[ 0.180957] DMAR-IR: IOAPIC id 2 under DRHD base 0xfed91000 IOMMU 1
[ 0.180959] DMAR-IR: HPET id 0 under DRHD base 0xfed91000
[ 0.180960] DMAR-IR: x2apic is disabled because BIOS sets x2apic opt out bit.
[ 0.180961] DMAR-IR: Use 'intremap=no_x2apic_optout' to override the BIOS setting.
[ 0.182664] DMAR-IR: Enabled IRQ remapping in xapic mode
[ 0.182665] x2apic: IRQ remapping doesn't support X2APIC mode
[ 0.186812] ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1
[ 0.204812] clocksource: tsc-early: mask: 0xffffffffffffffff max_cycles: 0x257a34a6eea, max_idle_ns: 440795264358 ns
[ 0.204818] Calibrating delay loop (skipped), value calculated using timer frequency.. 5199.98 BogoMIPS (lpj=10399968)
[ 0.204821] pid_max: default: 32768 minimum: 301
[ 0.210353] LSM: Security Framework initializing
[ 0.210372] Yama: becoming mindful.
[ 0.210410] AppArmor: AppArmor initialized
[ 0.210502] Mount-cache hash table entries: 32768 (order: 6, 262144 bytes, linear)
[ 0.210540] Mountpoint-cache hash table entries: 32768 (order: 6, 262144 bytes, linear)
[ 0.211073] mce: CPU0: Thermal monitoring enabled (TM1)
[ 0.211114] process: using mwait in idle threads
[ 0.211118] Last level iTLB entries: 4KB 64, 2MB 8, 4MB 8
[ 0.211119] Last level dTLB entries: 4KB 64, 2MB 0, 4MB 0, 1GB 4
[ 0.211124] Spectre V1 : Mitigation: usercopy/swapgs barriers and __user pointer sanitization
[ 0.211126] Spectre V2 : Mitigation: Full generic retpoline
[ 0.211127] Spectre V2 : Spectre v2 / SpectreRSB mitigation: Filling RSB on context switch
[ 0.211128] Spectre V2 : Enabling Restricted Speculation for firmware calls
[ 0.211131] Spectre V2 : mitigation: Enabling conditional Indirect Branch Prediction Barrier
[ 0.211131] Spectre V2 : User space: Mitigation: STIBP via seccomp and prctl
[ 0.211134] Speculative Store Bypass: Mitigation: Speculative Store Bypass disabled via prctl and seccomp
[ 0.211138] TAA: Mitigation: Clear CPU buffers
[ 0.211144] SRBDS: Mitigation: Microcode
[ 0.211145] MDS: Mitigation: Clear CPU buffers
[ 0.211671] Freeing SMP alternatives memory: 40K
[ 0.216722] smpboot: CPU0: Intel(R) Core(TM) i7-6700HQ CPU @ 2.60GHz (family: 0x6, model: 0x5e, stepping: 0x3)
[ 0.216814] Performance Events: PEBS fmt3+, Skylake events, 32-deep LBR, full-width counters, Intel PMU driver.
[ 0.216814] ... version: 4
[ 0.216814] ... bit width: 48
[ 0.216814] ... generic registers: 4
[ 0.216814] ... value mask: 0000ffffffffffff
[ 0.216814] ... max period: 00007fffffffffff
[ 0.216814] ... fixed-purpose events: 3
[ 0.216814] ... event mask: 000000070000000f
[ 0.216814] rcu: Hierarchical SRCU implementation.
[ 0.216814] NMI watchdog: Enabled. Permanently consumes one hw-PMU counter.
[ 0.216814] smp: Bringing up secondary CPUs ...
[ 0.216814] x86: Booting SMP configuration:
[ 0.216814] .... node #0, CPUs: #1 #2 #3 #4
[ 0.230092] MDS CPU bug present and SMT on, data leak possible. See https://www.kernel.org/doc/html/latest/admin-guide/hw-vuln/mds.html for more details.
[ 0.230092] TAA CPU bug present and SMT on, data leak possible. See https://www.kernel.org/doc/html/latest/admin-guide/hw-vuln/tsx_async_abort.html for more details.
[ 0.230092] #5 #6 #7
[ 0.233878] smp: Brought up 1 node, 8 CPUs
[ 0.233878] smpboot: Max logical packages: 1
[ 0.233878] smpboot: Total of 8 processors activated (41599.87 BogoMIPS)
[ 0.237669] devtmpfs: initialized
[ 0.237669] x86/mm: Memory block size: 128MB
[ 0.239536] PM: Registering ACPI NVS region [mem 0xabdc1000-0xabdc1fff] (4096 bytes)
[ 0.239536] PM: Registering ACPI NVS region [mem 0xb7eae000-0xb7fadfff] (1048576 bytes)
[ 0.240939] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 7645041785100000 ns
[ 0.240939] futex hash table entries: 2048 (order: 5, 131072 bytes, linear)
[ 0.241324] pinctrl core: initialized pinctrl subsystem
[ 0.241565] PM: RTC time: 14:12:37, date: 2020-09-30
[ 0.241568] thermal_sys: Registered thermal governor 'fair_share'
[ 0.241569] thermal_sys: Registered thermal governor 'bang_bang'
[ 0.241571] thermal_sys: Registered thermal governor 'step_wise'
[ 0.241572] thermal_sys: Registered thermal governor 'user_space'
[ 0.241573] thermal_sys: Registered thermal governor 'power_allocator'
[ 0.241852] NET: Registered protocol family 16
[ 0.242362] DMA: preallocated 2048 KiB GFP_KERNEL pool for atomic allocations
[ 0.242654] DMA: preallocated 2048 KiB GFP_KERNEL|GFP_DMA pool for atomic allocations
[ 0.242957] DMA: preallocated 2048 KiB GFP_KERNEL|GFP_DMA32 pool for atomic allocations
[ 0.242976] audit: initializing netlink subsys (disabled)
[ 0.243009] audit: type=2000 audit(1601475157.060:1): state=initialized audit_enabled=0 res=1
[ 0.243009] EISA bus registered
[ 0.243009] cpuidle: using governor ladder
[ 0.243009] cpuidle: using governor menu
[ 0.243009] Simple Boot Flag at 0x47 set to 0x1
[ 0.243009] ACPI: bus type PCI registered
[ 0.243009] acpiphp: ACPI Hot Plug PCI Controller Driver version: 0.5
[ 0.244860] PCI: MMCONFIG for domain 0000 [bus 00-3f] at [mem 0xf8000000-0xfbffffff] (base 0xf8000000)
[ 0.244891] PCI: not using MMCONFIG
[ 0.244893] PCI: Using configuration type 1 for base access
[ 0.245837] ENERGY_PERF_BIAS: Set to 'normal', was 'performance'
[ 0.250036] HugeTLB registered 1.00 GiB page size, pre-allocated 0 pages
[ 0.250036] HugeTLB registered 2.00 MiB page size, pre-allocated 0 pages
[ 0.253064] ACPI: Added _OSI(Module Device)
[ 0.253066] ACPI: Added _OSI(Processor Device)
[ 0.253068] ACPI: Added _OSI(3.0 _SCP Extensions)
[ 0.253070] ACPI: Added _OSI(Processor Aggregator Device)
[ 0.253072] ACPI: Added _OSI(Linux-Dell-Video)
[ 0.253074] ACPI: Added _OSI(Linux-Lenovo-NV-HDMI-Audio)
[ 0.253077] ACPI: Added _OSI(Linux-HPI-Hybrid-Graphics)
[ 0.338076] ACPI: 11 ACPI AML tables successfully acquired and loaded
[ 0.340355] ACPI: EC: EC started
[ 0.340356] ACPI: EC: interrupt blocked
[ 0.343468] ACPI: EC: EC_CMD/EC_SC=0x66, EC_DATA=0x62
[ 0.343469] ACPI: EC: Boot ECDT EC used to handle transactions
[ 0.344574] ACPI: [Firmware Bug]: BIOS _OSI(Linux) query ignored
[ 0.353826] ACPI: Dynamic OEM Table Load:
[ 0.353861] ACPI: SSDT 0xFFFF9D69ED3E7000 000649 (v02 PmRef Cpu0Ist 00003000 INTL 20141107)
[ 0.353877] ACPI BIOS Error (bug): Failure creating named object [\_PR.CPU0._PPC], AE_ALREADY_EXISTS (20200528/dswload2-326)
[ 0.353893] fbcon: Taking over console
[ 0.353901] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20200528/psobject-220)
[ 0.353907] ACPI: Skipping parse of AML opcode: Method (0x0014)
[ 0.353911] ACPI BIOS Error (bug): Failure creating named object [\_PR.CPU0._PCT], AE_ALREADY_EXISTS (20200528/dswload2-326)
[ 0.353918] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20200528/psobject-220)
[ 0.353923] ACPI: Skipping parse of AML opcode: Method (0x0014)
[ 0.353926] ACPI BIOS Error (bug): Failure creating named object [\_PR.CPU0._PSS], AE_ALREADY_EXISTS (20200528/dswload2-326)
[ 0.353932] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20200528/psobject-220)
[ 0.353936] ACPI: Skipping parse of AML opcode: Method (0x0014)
[ 0.353939] ACPI BIOS Error (bug): Failure creating named object [\_PR.CPU0.LPSS], AE_ALREADY_EXISTS (20200528/dswload2-326)
[ 0.353945] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20200528/psobject-220)
[ 0.354126] ACPI BIOS Error (bug): Failure creating named object [\_PR.CPU0.TPSS], AE_ALREADY_EXISTS (20200528/dswload2-326)
[ 0.354158] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20200528/psobject-220)
[ 0.354375] ACPI BIOS Error (bug): Failure creating named object [\_PR.CPU0.PSDF], AE_ALREADY_EXISTS (20200528/dswload2-326)
[ 0.354413] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20200528/psobject-220)
[ 0.354419] ACPI BIOS Error (bug): Failure creating named object [\_PR.CPU0._PSD], AE_ALREADY_EXISTS (20200528/dswload2-326)
[ 0.354426] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20200528/psobject-220)
[ 0.354431] ACPI: Skipping parse of AML opcode: Method (0x0014)
[ 0.354434] ACPI BIOS Error (bug): Failure creating named object [\_PR.CPU0.HPSD], AE_ALREADY_EXISTS (20200528/dswload2-326)
[ 0.354440] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20200528/psobject-220)
[ 0.354459] ACPI BIOS Error (bug): Failure creating named object [\_PR.CPU0.SPSD], AE_ALREADY_EXISTS (20200528/dswload2-326)
[ 0.354468] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20200528/psobject-220)
[ 0.356652] ACPI: \_PR_.CPU0: _OSC native thermal LVT Acked
[ 0.358510] ACPI: Dynamic OEM Table Load:
[ 0.358526] ACPI: SSDT 0xFFFF9D69ECA96400 0003CF (v02 PmRef Cpu0Cst 00003001 INTL 20141107)
[ 0.361219] ACPI: Dynamic OEM Table Load:
[ 0.361232] ACPI: SSDT 0xFFFF9D69ED3C33C0 00008E (v02 PmRef Cpu0Hwp 00003000 INTL 20141107)
[ 0.363591] ACPI: Dynamic OEM Table Load:
[ 0.363602] ACPI: SSDT 0xFFFF9D69ECA49E00 000130 (v02 PmRef HwpLvt 00003000 INTL 20141107)
[ 0.366934] ACPI: Dynamic OEM Table Load:
[ 0.366950] ACPI: SSDT 0xFFFF9D69ED3E3000 0005AA (v02 PmRef ApIst 00003000 INTL 20141107)
[ 0.370189] ACPI: Dynamic OEM Table Load:
[ 0.370200] ACPI: SSDT 0xFFFF9D69ECA48A00 000119 (v02 PmRef ApHwp 00003000 INTL 20141107)
[ 0.372658] ACPI: Dynamic OEM Table Load:
[ 0.372669] ACPI: SSDT 0xFFFF9D69ECA48200 000119 (v02 PmRef ApCst 00003000 INTL 20141107)
[ 0.382344] ACPI: Interpreter enabled
[ 0.382447] ACPI: (supports S0 S3 S4 S5)
[ 0.382449] ACPI: Using IOAPIC for interrupt routing
[ 0.382508] PCI: MMCONFIG for domain 0000 [bus 00-3f] at [mem 0xf8000000-0xfbffffff] (base 0xf8000000)
[ 0.383344] PCI: MMCONFIG at [mem 0xf8000000-0xfbffffff] reserved in ACPI motherboard resources
[ 0.383359] PCI: Using host bridge windows from ACPI; if necessary, use "pci=nocrs" and report a bug
[ 0.383983] ACPI: Enabled 5 GPEs in block 00 to 7F
[ 0.390262] ACPI: Power Resource [PUBS] (on)
[ 0.390889] ACPI: Power Resource [PG00] (on)
[ 0.391186] ACPI: Power Resource [PG01] (on)
[ 0.391474] ACPI: Power Resource [PG02] (on)
[ 0.404946] ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 6 7 9 10 *11)
[ 0.405183] ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 6 7 9 *10 11)
[ 0.405415] ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 5 6 7 9 10 *11)
[ 0.405644] ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 5 6 7 9 10 *11)
[ 0.405873] ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 5 6 7 9 10 *11)
[ 0.406103] ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 5 6 7 9 10 *11)
[ 0.406317] ACPI: PCI Interrupt Link [LNKG] (IRQs 3 4 5 6 7 9 10 11) *0, disabled.
[ 0.406556] ACPI: PCI Interrupt Link [LNKH] (IRQs 3 4 5 6 7 9 10 *11)
[ 0.406762] ACPI: PCI Root Bridge [PCI0] (domain 0000 [bus 00-80])
[ 0.406771] acpi PNP0A08:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI HPX-Type3]
[ 0.407031] acpi PNP0A08:00: _OSC: platform does not support [SHPCHotplug PCIeCapability LTR]
[ 0.407146] acpi PNP0A08:00: _OSC: not requesting control; platform does not support [PCIeCapability]
[ 0.407149] acpi PNP0A08:00: _OSC: OS requested [PCIeHotplug SHPCHotplug PME AER PCIeCapability LTR]
[ 0.407152] acpi PNP0A08:00: _OSC: platform willing to grant [PCIeHotplug PME AER]
[ 0.407153] acpi PNP0A08:00: _OSC failed (AE_SUPPORT); disabling ASPM
[ 0.407210] acpi PNP0A08:00: [Firmware Info]: MMCONFIG for domain 0000 [bus 00-3f] only partially covers this bridge
[ 0.408869] PCI host bridge to bus 0000:00
[ 0.408872] pci_bus 0000:00: root bus resource [io 0x0000-0x0cf7 window]
[ 0.408874] pci_bus 0000:00: root bus resource [io 0x0d00-0xffff window]
[ 0.408876] pci_bus 0000:00: root bus resource [mem 0x000a0000-0x000bffff window]
[ 0.408878] pci_bus 0000:00: root bus resource [mem 0x000c0000-0x000c3fff window]
[ 0.408880] pci_bus 0000:00: root bus resource [mem 0x000c4000-0x000c7fff window]
[ 0.408881] pci_bus 0000:00: root bus resource [mem 0x000c8000-0x000cbfff window]
[ 0.408883] pci_bus 0000:00: root bus resource [mem 0x000cc000-0x000cffff window]
[ 0.408885] pci_bus 0000:00: root bus resource [mem 0x000d0000-0x000d3fff window]
[ 0.408886] pci_bus 0000:00: root bus resource [mem 0x000d4000-0x000d7fff window]
[ 0.408888] pci_bus 0000:00: root bus resource [mem 0x000d8000-0x000dbfff window]
[ 0.408890] pci_bus 0000:00: root bus resource [mem 0x000dc000-0x000dffff window]
[ 0.408891] pci_bus 0000:00: root bus resource [mem 0x000e0000-0x000e3fff window]
[ 0.408893] pci_bus 0000:00: root bus resource [mem 0x000e4000-0x000e7fff window]
[ 0.408895] pci_bus 0000:00: root bus resource [mem 0x000e8000-0x000ebfff window]
[ 0.408896] pci_bus 0000:00: root bus resource [mem 0x000ec000-0x000effff window]
[ 0.408898] pci_bus 0000:00: root bus resource [mem 0xbc800000-0xfebfffff window]
[ 0.408900] pci_bus 0000:00: root bus resource [bus 00-80]
[ 0.408917] pci 0000:00:00.0: [8086:1910] type 00 class 0x060000
[ 0.409678] pci 0000:00:01.0: [8086:1901] type 01 class 0x060400
[ 0.409760] pci 0000:00:01.0: PME# supported from D0 D3hot D3cold
[ 0.410606] pci 0000:00:01.2: [8086:1909] type 01 class 0x060400
[ 0.410685] pci 0000:00:01.2: PME# supported from D0 D3hot D3cold
[ 0.411544] pci 0000:00:02.0: [8086:191b] type 00 class 0x030000
[ 0.411562] pci 0000:00:02.0: reg 0x10: [mem 0xf2000000-0xf2ffffff 64bit]
[ 0.411573] pci 0000:00:02.0: reg 0x18: [mem 0xc0000000-0xdfffffff 64bit pref]
[ 0.411580] pci 0000:00:02.0: reg 0x20: [io 0xe000-0xe03f]
[ 0.411609] pci 0000:00:02.0: BAR 2: assigned to efifb
[ 0.412454] pci 0000:00:14.0: [8086:a12f] type 00 class 0x0c0330
[ 0.412483] pci 0000:00:14.0: reg 0x10: [mem 0xf4220000-0xf422ffff 64bit]
[ 0.412582] pci 0000:00:14.0: PME# supported from D3hot D3cold
[ 0.413338] pci 0000:00:14.2: [8086:a131] type 00 class 0x118000
[ 0.413366] pci 0000:00:14.2: reg 0x10: [mem 0xf424a000-0xf424afff 64bit]
[ 0.414179] pci 0000:00:16.0: [8086:a13a] type 00 class 0x078000
[ 0.414211] pci 0000:00:16.0: reg 0x10: [mem 0xf424b000-0xf424bfff 64bit]
[ 0.414307] pci 0000:00:16.0: PME# supported from D3hot
[ 0.415135] pci 0000:00:17.0: [8086:a103] type 00 class 0x010601
[ 0.415159] pci 0000:00:17.0: reg 0x10: [mem 0xf4248000-0xf4249fff]
[ 0.415168] pci 0000:00:17.0: reg 0x14: [mem 0xf424e000-0xf424e0ff]
[ 0.415178] pci 0000:00:17.0: reg 0x18: [io 0xe080-0xe087]
[ 0.415187] pci 0000:00:17.0: reg 0x1c: [io 0xe088-0xe08b]
[ 0.415196] pci 0000:00:17.0: reg 0x20: [io 0xe060-0xe07f]
[ 0.415205] pci 0000:00:17.0: reg 0x24: [mem 0xf424c000-0xf424c7ff]
[ 0.415271] pci 0000:00:17.0: PME# supported from D3hot
[ 0.416095] pci 0000:00:1c.0: [8086:a110] type 01 class 0x060400
[ 0.416225] pci 0000:00:1c.0: PME# supported from D0 D3hot D3cold
[ 0.417104] pci 0000:00:1c.4: [8086:a114] type 01 class 0x060400
[ 0.417230] pci 0000:00:1c.4: PME# supported from D0 D3hot D3cold
[ 0.418103] pci 0000:00:1f.0: [8086:a14d] type 00 class 0x060100
[ 0.419032] pci 0000:00:1f.2: [8086:a121] type 00 class 0x058000
[ 0.419050] pci 0000:00:1f.2: reg 0x10: [mem 0xf4244000-0xf4247fff]
[ 0.419909] pci 0000:00:1f.3: [8086:a170] type 00 class 0x040300
[ 0.419943] pci 0000:00:1f.3: reg 0x10: [mem 0xf4240000-0xf4243fff 64bit]
[ 0.419982] pci 0000:00:1f.3: reg 0x20: [mem 0xf4230000-0xf423ffff 64bit]
[ 0.420052] pci 0000:00:1f.3: PME# supported from D3hot D3cold
[ 0.420873] pci 0000:00:1f.4: [8086:a123] type 00 class 0x0c0500
[ 0.420928] pci 0000:00:1f.4: reg 0x10: [mem 0xf424d000-0xf424d0ff 64bit]
[ 0.420978] pci 0000:00:1f.4: reg 0x20: [io 0xefa0-0xefbf]
[ 0.421853] pci 0000:00:1f.6: [8086:15b7] type 00 class 0x020000
[ 0.421887] pci 0000:00:1f.6: reg 0x10: [mem 0xf4200000-0xf421ffff]
[ 0.422033] pci 0000:00:1f.6: PME# supported from D0 D3hot D3cold
[ 0.422896] pci 0000:00:01.0: PCI bridge to [bus 01]
[ 0.422989] pci 0000:02:00.0: [10de:134d] type 00 class 0x030200
[ 0.423025] pci 0000:02:00.0: reg 0x10: [mem 0xf3000000-0xf3ffffff]
[ 0.423043] pci 0000:02:00.0: reg 0x14: [mem 0xe0000000-0xefffffff 64bit pref]
[ 0.423060] pci 0000:02:00.0: reg 0x1c: [mem 0xf0000000-0xf1ffffff 64bit pref]
[ 0.423071] pci 0000:02:00.0: reg 0x24: [io 0xd000-0xd07f]
[ 0.423082] pci 0000:02:00.0: reg 0x30: [mem 0xfff80000-0xffffffff pref]
[ 0.423114] pci 0000:02:00.0: Enabling HDA controller
[ 0.423453] pci 0000:00:01.2: PCI bridge to [bus 02]
[ 0.423457] pci 0000:00:01.2: bridge window [io 0xd000-0xdfff]
[ 0.423461] pci 0000:00:01.2: bridge window [mem 0xf3000000-0xf3ffffff]
[ 0.423465] pci 0000:00:01.2: bridge window [mem 0xe0000000-0xf1ffffff 64bit pref]
[ 0.423784] pci 0000:03:00.0: [8086:2723] type 00 class 0x028000
[ 0.423912] pci 0000:03:00.0: reg 0x10: [mem 0xf4100000-0xf4103fff 64bit]
[ 0.424279] pci 0000:03:00.0: PME# supported from D0 D3hot D3cold
[ 0.425152] pci 0000:00:1c.0: PCI bridge to [bus 03]
[ 0.425162] pci 0000:00:1c.0: bridge window [mem 0xf4100000-0xf41fffff]
[ 0.425383] pci 0000:04:00.0: [10ec:522a] type 00 class 0xff0000
[ 0.425421] pci 0000:04:00.0: reg 0x10: [mem 0xf4000000-0xf4000fff]
[ 0.425644] pci 0000:04:00.0: supports D1 D2
[ 0.425646] pci 0000:04:00.0: PME# supported from D1 D2 D3hot D3cold
[ 0.426282] pci 0000:00:1c.4: PCI bridge to [bus 04]
[ 0.426288] pci 0000:00:1c.4: bridge window [mem 0xf4000000-0xf40fffff]
[ 0.428814] ACPI: EC: interrupt unblocked
[ 0.428818] ACPI: EC: event unblocked
[ 0.428833] ACPI: EC: EC_CMD/EC_SC=0x66, EC_DATA=0x62
[ 0.428834] ACPI: EC: GPE=0x16
[ 0.428837] ACPI: \_SB_.PCI0.LPC_.EC__: Boot ECDT EC initialization complete
[ 0.428839] ACPI: \_SB_.PCI0.LPC_.EC__: EC: Used to handle transactions and events
[ 0.428985] iommu: Default domain type: Translated
[ 0.428985] pci 0000:00:02.0: vgaarb: VGA device added: decodes=io+mem,owns=mem,locks=none
[ 0.428985] pci 0000:00:02.0: vgaarb: bridge control possible
[ 0.428985] pci 0000:00:02.0: vgaarb: setting as boot device
[ 0.428985] vgaarb: loaded
[ 0.429104] SCSI subsystem initialized
[ 0.429130] libata version 3.00 loaded.
[ 0.429130] ACPI: bus type USB registered
[ 0.429130] usbcore: registered new interface driver usbfs
[ 0.429130] usbcore: registered new interface driver hub
[ 0.429130] usbcore: registered new device driver usb
[ 0.429130] pps_core: LinuxPPS API ver. 1 registered
[ 0.429130] pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <giometti@linux.it>
[ 0.429130] PTP clock support registered
[ 0.429130] EDAC MC: Ver: 3.0.0
[ 0.429204] Registered efivars operations
[ 0.429204] NetLabel: Initializing
[ 0.429204] NetLabel: domain hash size = 128
[ 0.429204] NetLabel: protocols = UNLABELED CIPSOv4 CALIPSO
[ 0.429204] NetLabel: unlabeled traffic allowed by default
[ 0.429204] PCI: Using ACPI for IRQ routing
[ 0.436982] PCI: pci_cache_line_size set to 64 bytes
[ 0.437412] e820: reserve RAM buffer [mem 0x00058000-0x0005ffff]
[ 0.437414] e820: reserve RAM buffer [mem 0x0009d000-0x0009ffff]
[ 0.437415] e820: reserve RAM buffer [mem 0xabdc1000-0xabffffff]
[ 0.437417] e820: reserve RAM buffer [mem 0xaec5d000-0xafffffff]
[ 0.437418] e820: reserve RAM buffer [mem 0xb561e000-0xb7ffffff]
[ 0.437420] e820: reserve RAM buffer [mem 0xb7fff000-0xb7ffffff]
[ 0.437421] e820: reserve RAM buffer [mem 0x441800000-0x443ffffff]
[ 0.437979] hpet0: at MMIO 0xfed00000, IRQs 2, 8, 0, 0, 0, 0, 0, 0
[ 0.437985] hpet0: 8 comparators, 64-bit 24.000000 MHz counter
[ 0.440044] clocksource: Switched to clocksource tsc-early
[ 0.460311] VFS: Disk quotas dquot_6.6.0
[ 0.460333] VFS: Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
[ 0.460509] AppArmor: AppArmor Filesystem Enabled
[ 0.460549] pnp: PnP ACPI init
[ 0.461472] system 00:00: [mem 0x00000000-0x0009ffff] could not be reserved
[ 0.461475] system 00:00: [mem 0x000f0000-0x000fffff] could not be reserved
[ 0.461477] system 00:00: [mem 0x00100000-0xbc7fffff] could not be reserved
[ 0.461479] system 00:00: [mem 0xfec00000-0xfed3ffff] could not be reserved
[ 0.461482] system 00:00: [mem 0xfed4c000-0xffffffff] could not be reserved
[ 0.461489] system 00:00: Plug and Play ACPI device, IDs PNP0c01 (active)
[ 0.461617] system 00:01: [io 0x1800-0x189f] has been reserved
[ 0.461619] system 00:01: [io 0x0800-0x087f] has been reserved
[ 0.461621] system 00:01: [io 0x0880-0x08ff] has been reserved
[ 0.461623] system 00:01: [io 0x0900-0x097f] has been reserved
[ 0.461625] system 00:01: [io 0x0980-0x09ff] has been reserved
[ 0.461627] system 00:01: [io 0x0a00-0x0a7f] has been reserved
[ 0.461631] system 00:01: [io 0x0a80-0x0aff] has been reserved
[ 0.461633] system 00:01: [io 0x0b00-0x0b7f] has been reserved
[ 0.461635] system 00:01: [io 0x0b80-0x0bff] has been reserved
[ 0.461637] system 00:01: [io 0x15e0-0x15ef] has been reserved
[ 0.461639] system 00:01: [io 0x1600-0x167f] has been reserved
[ 0.461641] system 00:01: [io 0x1640-0x165f] has been reserved
[ 0.461644] system 00:01: [mem 0xf8000000-0xfbffffff] could not be reserved
[ 0.461647] system 00:01: [mem 0xfed10000-0xfed13fff] has been reserved
[ 0.461649] system 00:01: [mem 0xfed18000-0xfed18fff] has been reserved
[ 0.461651] system 00:01: [mem 0xfed19000-0xfed19fff] has been reserved
[ 0.461653] system 00:01: [mem 0xfeb00000-0xfebfffff] has been reserved
[ 0.461658] system 00:01: Plug and Play ACPI device, IDs PNP0c02 (active)
[ 0.461800] pnp 00:02: Plug and Play ACPI device, IDs PNP0b00 (active)
[ 0.461830] pnp 00:03: Plug and Play ACPI device, IDs LEN0071 PNP0303 (active)
[ 0.461868] pnp 00:04: Plug and Play ACPI device, IDs LEN2018 PNP0f13 (active)
[ 0.462893] system 00:05: [mem 0xfd000000-0xfdabffff] has been reserved
[ 0.462895] system 00:05: [mem 0xfdad0000-0xfdadffff] has been reserved
[ 0.462897] system 00:05: [mem 0xfdb00000-0xfdffffff] has been reserved
[ 0.462900] system 00:05: [mem 0xfe000000-0xfe01ffff] could not be reserved
[ 0.462902] system 00:05: [mem 0xfe036000-0xfe03bfff] has been reserved
[ 0.462904] system 00:05: [mem 0xfe03d000-0xfe3fffff] has been reserved
[ 0.462906] system 00:05: [mem 0xfe410000-0xfe7fffff] has been reserved
[ 0.462912] system 00:05: Plug and Play ACPI device, IDs PNP0c02 (active)
[ 0.463616] system 00:06: [io 0xff00-0xfffe] has been reserved
[ 0.463621] system 00:06: Plug and Play ACPI device, IDs PNP0c02 (active)
[ 0.463815] pnp: PnP ACPI: found 7 devices
[ 0.470510] clocksource: acpi_pm: mask: 0xffffff max_cycles: 0xffffff, max_idle_ns: 2085701024 ns
[ 0.470610] NET: Registered protocol family 2
[ 0.470894] tcp_listen_portaddr_hash hash table entries: 8192 (order: 5, 131072 bytes, linear)
[ 0.471032] TCP established hash table entries: 131072 (order: 8, 1048576 bytes, linear)
[ 0.471358] TCP bind hash table entries: 65536 (order: 8, 1048576 bytes, linear)
[ 0.471491] TCP: Hash tables configured (established 131072 bind 65536)
[ 0.471680] UDP hash table entries: 8192 (order: 6, 262144 bytes, linear)
[ 0.471760] UDP-Lite hash table entries: 8192 (order: 6, 262144 bytes, linear)
[ 0.471892] NET: Registered protocol family 1
[ 0.471899] NET: Registered protocol family 44
[ 0.471907] pci 0000:02:00.0: can't claim BAR 6 [mem 0xfff80000-0xffffffff pref]: no compatible bridge window
[ 0.471920] pci 0000:00:01.0: PCI bridge to [bus 01]
[ 0.471934] pci 0000:02:00.0: BAR 6: no space for [mem size 0x00080000 pref]
[ 0.471936] pci 0000:02:00.0: BAR 6: failed to assign [mem size 0x00080000 pref]
[ 0.471938] pci 0000:00:01.2: PCI bridge to [bus 02]
[ 0.471941] pci 0000:00:01.2: bridge window [io 0xd000-0xdfff]
[ 0.471945] pci 0000:00:01.2: bridge window [mem 0xf3000000-0xf3ffffff]
[ 0.471949] pci 0000:00:01.2: bridge window [mem 0xe0000000-0xf1ffffff 64bit pref]
[ 0.471954] pci 0000:00:1c.0: PCI bridge to [bus 03]
[ 0.471971] pci 0000:00:1c.0: bridge window [mem 0xf4100000-0xf41fffff]
[ 0.471979] pci 0000:00:1c.4: PCI bridge to [bus 04]
[ 0.471984] pci 0000:00:1c.4: bridge window [mem 0xf4000000-0xf40fffff]
[ 0.471994] pci_bus 0000:00: resource 4 [io 0x0000-0x0cf7 window]
[ 0.471996] pci_bus 0000:00: resource 5 [io 0x0d00-0xffff window]
[ 0.471998] pci_bus 0000:00: resource 6 [mem 0x000a0000-0x000bffff window]
[ 0.472000] pci_bus 0000:00: resource 7 [mem 0x000c0000-0x000c3fff window]
[ 0.472001] pci_bus 0000:00: resource 8 [mem 0x000c4000-0x000c7fff window]
[ 0.472003] pci_bus 0000:00: resource 9 [mem 0x000c8000-0x000cbfff window]
[ 0.472005] pci_bus 0000:00: resource 10 [mem 0x000cc000-0x000cffff window]
[ 0.472007] pci_bus 0000:00: resource 11 [mem 0x000d0000-0x000d3fff window]
[ 0.472008] pci_bus 0000:00: resource 12 [mem 0x000d4000-0x000d7fff window]
[ 0.472010] pci_bus 0000:00: resource 13 [mem 0x000d8000-0x000dbfff window]
[ 0.472012] pci_bus 0000:00: resource 14 [mem 0x000dc000-0x000dffff window]
[ 0.472014] pci_bus 0000:00: resource 15 [mem 0x000e0000-0x000e3fff window]
[ 0.472015] pci_bus 0000:00: resource 16 [mem 0x000e4000-0x000e7fff window]
[ 0.472017] pci_bus 0000:00: resource 17 [mem 0x000e8000-0x000ebfff window]
[ 0.472019] pci_bus 0000:00: resource 18 [mem 0x000ec000-0x000effff window]
[ 0.472021] pci_bus 0000:00: resource 19 [mem 0xbc800000-0xfebfffff window]
[ 0.472023] pci_bus 0000:02: resource 0 [io 0xd000-0xdfff]
[ 0.472024] pci_bus 0000:02: resource 1 [mem 0xf3000000-0xf3ffffff]
[ 0.472026] pci_bus 0000:02: resource 2 [mem 0xe0000000-0xf1ffffff 64bit pref]
[ 0.472028] pci_bus 0000:03: resource 1 [mem 0xf4100000-0xf41fffff]
[ 0.472030] pci_bus 0000:04: resource 1 [mem 0xf4000000-0xf40fffff]
[ 0.472224] pci 0000:00:02.0: Video device with shadowed ROM at [mem 0x000c0000-0x000dffff]
[ 0.472965] PCI: CLS 0 bytes, default 64
[ 0.473026] Trying to unpack rootfs image as initramfs...
[ 0.849234] Initramfs unpacking failed: Decoding failed
[ 0.864723] Freeing initrd memory: 85328K
[ 0.880876] PCI-DMA: Using software bounce buffering for IO (SWIOTLB)
[ 0.880879] software IO TLB: mapped [mem 0xb0d56000-0xb4d56000] (64MB)
[ 0.881009] resource sanity check: requesting [mem 0xfed10000-0xfed15fff], which spans more than pnp 00:01 [mem 0xfed10000-0xfed13fff]
[ 0.881015] caller snb_uncore_imc_init_box+0x6c/0xb0 mapping multiple BARs
[ 0.881384] check: Scanning for low memory corruption every 60 seconds
[ 0.882176] Initialise system trusted keyrings
[ 0.882200] Key type blacklist registered
[ 0.882248] workingset: timestamp_bits=36 max_order=22 bucket_order=0
[ 0.884754] zbud: loaded
[ 0.885224] squashfs: version 4.0 (2009/01/31) Phillip Lougher
[ 0.885479] fuse: init (API version 7.31)
[ 0.885719] integrity: Platform Keyring initialized
[ 0.904092] Key type asymmetric registered
[ 0.904093] Asymmetric key parser 'x509' registered
[ 0.904104] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 244)
[ 0.904166] io scheduler mq-deadline registered
[ 0.905566] shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
[ 0.905657] efifb: probing for efifb
[ 0.905679] efifb: showing boot graphics
[ 0.907443] efifb: framebuffer at 0xc0000000, using 8100k, total 8100k
[ 0.907445] efifb: mode is 1920x1080x32, linelength=7680, pages=1
[ 0.907446] efifb: scrolling: redraw
[ 0.907448] efifb: Truecolor: size=8:8:8:8, shift=24:16:8:0
[ 0.907596] Console: switching to colour frame buffer device 240x67
[ 0.917542] fb0: EFI VGA frame buffer device
[ 0.917555] intel_idle: MWAIT substates: 0x11142120
[ 0.917557] intel_idle: v0.5.1 model 0x5E
[ 0.918358] intel_idle: Local APIC timer is reliable in all C-states
[ 0.918909] ACPI: AC Adapter [AC] (off-line)
[ 0.919001] input: Lid Switch as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0D:00/input/input0
[ 0.919052] ACPI: Lid Switch [LID]
[ 0.919097] input: Sleep Button as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0E:00/input/input1
[ 0.919133] ACPI: Sleep Button [SLPB]
[ 0.919220] input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input2
[ 0.919255] ACPI: Power Button [PWRF]
[ 0.919353] ACPI BIOS Error (bug): Could not resolve symbol [\_PR.CPU0._CPC.CPC1], AE_NOT_FOUND (20200528/psargs-330)
[ 0.919456] No Local Variables are initialized for Method [_CPC]
[ 0.919458] No Arguments are initialized for method [_CPC]
[ 0.919462] ACPI Error: Aborting method \_PR.CPU0._CPC due to previous error (AE_NOT_FOUND) (20200528/psparse-529)
[ 0.919693] ACPI BIOS Error (bug): Could not resolve symbol [\_PR.CPU0._CPC.CPC1], AE_NOT_FOUND (20200528/psargs-330)
[ 0.919789] No Local Variables are initialized for Method [_CPC]
[ 0.919791] No Arguments are initialized for method [_CPC]
[ 0.919794] ACPI Error: Aborting method \_PR.CPU0._CPC due to previous error (AE_NOT_FOUND) (20200528/psparse-529)
[ 0.919885] ACPI Error: Aborting method \_PR.CPU1._CPC due to previous error (AE_NOT_FOUND) (20200528/psparse-529)
[ 0.920144] ACPI BIOS Error (bug): Could not resolve symbol [\_PR.CPU0._CPC.CPC1], AE_NOT_FOUND (20200528/psargs-330)
[ 0.920239] No Local Variables are initialized for Method [_CPC]
[ 0.920240] No Arguments are initialized for method [_CPC]
[ 0.920243] ACPI Error: Aborting method \_PR.CPU0._CPC due to previous error (AE_NOT_FOUND) (20200528/psparse-529)
[ 0.920333] ACPI Error: Aborting method \_PR.CPU2._CPC due to previous error (AE_NOT_FOUND) (20200528/psparse-529)
[ 0.920585] ACPI BIOS Error (bug): Could not resolve symbol [\_PR.CPU0._CPC.CPC1], AE_NOT_FOUND (20200528/psargs-330)
[ 0.920680] No Local Variables are initialized for Method [_CPC]
[ 0.920681] No Arguments are initialized for method [_CPC]
[ 0.920683] ACPI Error: Aborting method \_PR.CPU0._CPC due to previous error (AE_NOT_FOUND) (20200528/psparse-529)
[ 0.920774] ACPI Error: Aborting method \_PR.CPU3._CPC due to previous error (AE_NOT_FOUND) (20200528/psparse-529)
[ 0.921058] ACPI BIOS Error (bug): Could not resolve symbol [\_PR.CPU0._CPC.CPC1], AE_NOT_FOUND (20200528/psargs-330)
[ 0.921154] No Local Variables are initialized for Method [_CPC]
[ 0.921155] No Arguments are initialized for method [_CPC]
[ 0.921158] ACPI Error: Aborting method \_PR.CPU0._CPC due to previous error (AE_NOT_FOUND) (20200528/psparse-529)
[ 0.921248] ACPI Error: Aborting method \_PR.CPU4._CPC due to previous error (AE_NOT_FOUND) (20200528/psparse-529)
[ 0.921606] ACPI BIOS Error (bug): Could not resolve symbol [\_PR.CPU0._CPC.CPC1], AE_NOT_FOUND (20200528/psargs-330)
[ 0.921702] No Local Variables are initialized for Method [_CPC]
[ 0.921703] No Arguments are initialized for method [_CPC]
[ 0.921706] ACPI Error: Aborting method \_PR.CPU0._CPC due to previous error (AE_NOT_FOUND) (20200528/psparse-529)
[ 0.921797] ACPI Error: Aborting method \_PR.CPU5._CPC due to previous error (AE_NOT_FOUND) (20200528/psparse-529)
[ 0.922190] ACPI BIOS Error (bug): Could not resolve symbol [\_PR.CPU0._CPC.CPC1], AE_NOT_FOUND (20200528/psargs-330)
[ 0.922285] No Local Variables are initialized for Method [_CPC]
[ 0.922286] No Arguments are initialized for method [_CPC]
[ 0.922288] ACPI Error: Aborting method \_PR.CPU0._CPC due to previous error (AE_NOT_FOUND) (20200528/psparse-529)
[ 0.922381] ACPI Error: Aborting method \_PR.CPU6._CPC due to previous error (AE_NOT_FOUND) (20200528/psparse-529)
[ 0.922765] ACPI BIOS Error (bug): Could not resolve symbol [\_PR.CPU0._CPC.CPC1], AE_NOT_FOUND (20200528/psargs-330)
[ 0.922867] No Local Variables are initialized for Method [_CPC]
[ 0.922869] No Arguments are initialized for method [_CPC]
[ 0.922873] ACPI Error: Aborting method \_PR.CPU0._CPC due to previous error (AE_NOT_FOUND) (20200528/psparse-529)
[ 0.922966] ACPI Error: Aborting method \_PR.CPU7._CPC due to previous error (AE_NOT_FOUND) (20200528/psparse-529)
[ 0.927888] thermal LNXTHERM:00: registered as thermal_zone0
[ 0.927891] ACPI: Thermal Zone [THM0] (41 C)
[ 0.928285] Serial: 8250/16550 driver, 32 ports, IRQ sharing enabled
[ 0.948356] battery: ACPI: Battery Slot [BAT0] (battery present)
[ 0.949659] serial8250: ttyS0 at I/O 0x3f8 (irq = 4, base_baud = 115200) is a 16550A
[ 0.952993] Linux agpgart interface v0.103
[ 1.039750] loop: module loaded
[ 1.040493] libphy: Fixed MDIO Bus: probed
[ 1.040495] tun: Universal TUN/TAP device driver, 1.6
[ 1.040587] PPP generic driver version 2.4.2
[ 1.040712] VFIO - User Level meta-driver version: 0.3
[ 1.040861] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[ 1.040876] ehci-pci: EHCI PCI platform driver
[ 1.040895] ehci-platform: EHCI generic platform driver
[ 1.040917] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
[ 1.040920] ohci-pci: OHCI PCI platform driver
[ 1.040935] ohci-platform: OHCI generic platform driver
[ 1.040949] uhci_hcd: USB Universal Host Controller Interface driver
[ 1.041037] i8042: PNP: PS/2 Controller [PNP0303:KBD,PNP0f13:MOU] at 0x60,0x64 irq 1,12
[ 1.043144] serio: i8042 KBD port at 0x60,0x64 irq 1
[ 1.043152] serio: i8042 AUX port at 0x60,0x64 irq 12
[ 1.043331] mousedev: PS/2 mouse device common for all mice
[ 1.043585] rtc_cmos 00:02: RTC can wake from S4
[ 1.044260] rtc_cmos 00:02: registered as rtc0
[ 1.044421] rtc_cmos 00:02: setting system clock to 2020-09-30T14:12:37 UTC (1601475157)
[ 1.044450] rtc_cmos 00:02: alarms up to one month, y3k, 114 bytes nvram, hpet irqs
[ 1.044490] i2c /dev entries driver
[ 1.044580] device-mapper: uevent: version 1.0.3
[ 1.044730] device-mapper: ioctl: 4.42.0-ioctl (2020-02-27) initialised: dm-devel@redhat.com
[ 1.044768] platform eisa.0: Probing EISA bus 0
[ 1.044771] platform eisa.0: EISA: Cannot allocate resource for mainboard
[ 1.044774] platform eisa.0: Cannot allocate resource for EISA slot 1
[ 1.044776] platform eisa.0: Cannot allocate resource for EISA slot 2
[ 1.044778] platform eisa.0: Cannot allocate resource for EISA slot 3
[ 1.044780] platform eisa.0: Cannot allocate resource for EISA slot 4
[ 1.044782] platform eisa.0: Cannot allocate resource for EISA slot 5
[ 1.044784] platform eisa.0: Cannot allocate resource for EISA slot 6
[ 1.044786] platform eisa.0: Cannot allocate resource for EISA slot 7
[ 1.044788] platform eisa.0: Cannot allocate resource for EISA slot 8
[ 1.044790] platform eisa.0: EISA: Detected 0 cards
[ 1.044795] intel_pstate: Intel P-state driver initializing
[ 1.045526] input: AT Translated Set 2 keyboard as /devices/platform/i8042/serio0/input/input3
[ 1.046077] intel_pstate: HWP enabled
[ 1.046611] ledtrig-cpu: registered to indicate activity on CPUs
[ 1.046628] EFI Variables Facility v0.08 2004-May-17
[ 1.091200] intel_pmc_core intel_pmc_core.0: initialized
[ 1.091233] drop_monitor: Initializing network drop monitor service
[ 1.091375] NET: Registered protocol family 10
[ 1.096244] Segment Routing with IPv6
[ 1.096277] NET: Registered protocol family 17
[ 1.096303] Key type dns_resolver registered
[ 1.096679] microcode: sig=0x506e3, pf=0x20, revision=0xdc
[ 1.096735] microcode: Microcode Update Driver: v2.2.
[ 1.096737] IPI shorthand broadcast: enabled
[ 1.096743] sched_clock: Marking stable (1095903135, 829158)->(1134941402, -38209109)
[ 1.096795] registered taskstats version 1
[ 1.096802] Loading compiled-in X.509 certificates
[ 1.097369] Loaded X.509 cert 'Build time autogenerated kernel key: 328af5441b6367468283d56e87c4ff404dcf99f9'
[ 1.097391] zswap: loaded using pool lzo/zbud
[ 1.097529] Key type ._fscrypt registered
[ 1.097529] Key type .fscrypt registered
[ 1.097530] Key type fscrypt-provisioning registered
[ 1.097584] Key type trusted registered
[ 1.099720] Key type encrypted registered
[ 1.099722] AppArmor: AppArmor sha1 policy hashing enabled
[ 1.100480] integrity: Loading X.509 certificate: UEFI:db
[ 1.100502] integrity: Loaded X.509 cert 'Lenovo Ltd.: ThinkPad Product CA 2012: 838b1f54c1550463f45f98700640f11069265949'
[ 1.100503] integrity: Loading X.509 certificate: UEFI:db
[ 1.100530] integrity: Loaded X.509 cert 'Lenovo UEFI CA 2014: 4b91a68732eaefdd2c8ffffc6b027ec3449e9c8f'
[ 1.100530] integrity: Loading X.509 certificate: UEFI:db
[ 1.100541] integrity: Loaded X.509 cert 'Lenovo UEFI CA 2014: 4b91a68732eaefdd2c8ffffc6b027ec3449e9c8f'
[ 1.100541] integrity: Loading X.509 certificate: UEFI:db
[ 1.100560] integrity: Loaded X.509 cert 'Microsoft Corporation UEFI CA 2011: 13adbf4309bd82709c8cd54f316ed522988a1bd4'
[ 1.100560] integrity: Loading X.509 certificate: UEFI:db
[ 1.100576] integrity: Loaded X.509 cert 'Microsoft Windows Production PCA 2011: a92902398e16c49778cd90f99e4f9ae17c55af53'
[ 1.101821] ima: Allocated hash algorithm: sha1
[ 1.257526] ima: No architecture policies found
[ 1.257538] evm: Initialising EVM extended attributes:
[ 1.257538] evm: security.selinux
[ 1.257539] evm: security.SMACK64
[ 1.257539] evm: security.SMACK64EXEC
[ 1.257540] evm: security.SMACK64TRANSMUTE
[ 1.257540] evm: security.SMACK64MMAP
[ 1.257540] evm: security.apparmor
[ 1.257541] evm: security.ima
[ 1.257541] evm: security.capability
[ 1.257542] evm: HMAC attrs: 0x1
[ 1.258250] PM: Magic number: 4:925:233
[ 1.258289] memory memory111: hash matches
[ 1.258631] RAS: Correctable Errors collector initialized.
[ 1.259623] Freeing unused decrypted memory: 2040K
[ 1.260059] Freeing unused kernel image (initmem) memory: 2640K
[ 1.260143] Write protecting the kernel read-only data: 26624k
[ 1.260575] Freeing unused kernel image (text/rodata gap) memory: 2044K
[ 1.260798] Freeing unused kernel image (rodata/data gap) memory: 1496K
[ 1.304012] x86/mm: Checked W+X mappings: passed, no W+X pages found.
[ 1.304013] x86/mm: Checking user space page tables
[ 1.346401] x86/mm: Checked W+X mappings: passed, no W+X pages found.
[ 1.346404] Run /init as init process
[ 1.346405] with arguments:
[ 1.346405] /init
[ 1.346406] splash
[ 1.346406] with environment:
[ 1.346407] HOME=/
[ 1.346407] TERM=linux
[ 1.346407] BOOT_IMAGE=/vmlinuz-5.8.0-050800-generic
[ 1.422278] ahci 0000:00:17.0: version 3.0
[ 1.422663] rtsx_pci 0000:04:00.0: enabling device (0000 -> 0002)
[ 1.425498] i801_smbus 0000:00:1f.4: enabling device (0000 -> 0003)
[ 1.425986] xhci_hcd 0000:00:14.0: xHCI Host Controller
[ 1.425993] xhci_hcd 0000:00:14.0: new USB bus registered, assigned bus number 1
[ 1.426088] e1000e: Intel(R) PRO/1000 Network Driver - 3.2.6-k
[ 1.426088] e1000e: Copyright(c) 1999 - 2015 Intel Corporation.
[ 1.427135] xhci_hcd 0000:00:14.0: hcc params 0x200077c1 hci version 0x100 quirks 0x0000000001109810
[ 1.427150] xhci_hcd 0000:00:14.0: cache line size of 64 is not supported
[ 1.427375] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 5.08
[ 1.427377] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[ 1.427379] usb usb1: Product: xHCI Host Controller
[ 1.427380] usb usb1: Manufacturer: Linux 5.8.0-050800-generic xhci-hcd
[ 1.427382] usb usb1: SerialNumber: 0000:00:14.0
[ 1.427929] acpi PNP0C14:01: duplicate WMI GUID 05901221-D566-11D1-B2F0-00A0C9062910 (first instance was on PNP0C14:00)
[ 1.428155] hub 1-0:1.0: USB hub found
[ 1.428172] hub 1-0:1.0: 16 ports detected
[ 1.431159] acpi PNP0C14:02: duplicate WMI GUID 05901221-D566-11D1-B2F0-00A0C9062910 (first instance was on PNP0C14:00)
[ 1.431187] i801_smbus 0000:00:1f.4: SPD Write Disable is set
[ 1.431222] i801_smbus 0000:00:1f.4: SMBus using PCI interrupt
[ 1.431555] e1000e 0000:00:1f.6: Interrupt Throttling Rate (ints/sec) set to dynamic conservative mode
[ 1.434007] cryptd: max_cpu_qlen set to 1000
[ 1.434951] i2c i2c-0: 2/2 memory slots populated (from DMI)
[ 1.438721] AVX2 version of gcm_enc/dec engaged.
[ 1.438722] AES CTR mode by8 optimization enabled
[ 1.439768] xhci_hcd 0000:00:14.0: xHCI Host Controller
[ 1.439771] xhci_hcd 0000:00:14.0: new USB bus registered, assigned bus number 2
[ 1.439774] xhci_hcd 0000:00:14.0: Host supports USB 3.0 SuperSpeed
[ 1.439807] usb usb2: New USB device found, idVendor=1d6b, idProduct=0003, bcdDevice= 5.08
[ 1.439808] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[ 1.439809] usb usb2: Product: xHCI Host Controller
[ 1.439810] usb usb2: Manufacturer: Linux 5.8.0-050800-generic xhci-hcd
[ 1.439811] usb usb2: SerialNumber: 0000:00:14.0
[ 1.439898] ahci 0000:00:17.0: AHCI 0001.0301 32 slots 4 ports 6 Gbps 0x1 impl SATA mode
[ 1.439900] ahci 0000:00:17.0: flags: 64bit ncq sntf pm led clo only pio slum part ems deso sadm sds apst
[ 1.439901] hub 2-0:1.0: USB hub found
[ 1.439914] hub 2-0:1.0: 8 ports detected
[ 1.440043] i2c i2c-0: Successfully instantiated SPD at 0x50
[ 1.440895] usb: port power management may be unreliable
[ 1.449229] scsi host0: ahci
[ 1.449601] scsi host1: ahci
[ 1.449923] scsi host2: ahci
[ 1.450261] scsi host3: ahci
[ 1.450302] ata1: SATA max UDMA/133 abar m2048@0xf424c000 port 0xf424c100 irq 128
[ 1.450305] ata2: DUMMY
[ 1.450306] ata3: DUMMY
[ 1.450306] ata4: DUMMY
[ 1.502260] i915 0000:00:02.0: enabling device (0006 -> 0007)
[ 1.502878] checking generic (c0000000 7e9000) vs hw (f2000000 1000000)
[ 1.502879] checking generic (c0000000 7e9000) vs hw (c0000000 20000000)
[ 1.502880] fb0: switching to inteldrmfb from EFI VGA
[ 1.502932] Console: switching to colour dummy device 80x25
[ 1.502956] i915 0000:00:02.0: vgaarb: deactivate vga console
[ 1.503824] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
[ 1.504168] i915 0000:00:02.0: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=io+mem:owns=mem
[ 1.504598] i915 0000:00:02.0: [drm] Finished loading DMC firmware i915/skl_dmc_ver1_27.bin (v1.27)
[ 1.519223] i915 0000:00:02.0: [drm] Panel advertises DPCD backlight support, but VBT disagrees. If your backlight controls don't work try booting with i915.enable_dpcd_backlight=1. If your machine needs this, please file a _new_ bug report on drm/i915, see https://gitlab.freedesktop.org/drm/intel/-/wikis/How-to-file-i915-bugs for details.
[ 1.522983] [drm] Initialized i915 1.6.0 20200515 for 0000:00:02.0 on minor 0
[ 1.523739] ACPI: Video Device [PEGP] (multi-head: no rom: yes post: no)
[ 1.523878] input: Video Bus as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/device:05/LNXVIDEO:00/input/input6
[ 1.526487] ACPI: Video Device [GFX0] (multi-head: yes rom: no post: no)
[ 1.526642] input: Video Bus as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/LNXVIDEO:01/input/input7
[ 1.539300] fbcon: i915drmfb (fb0) is primary device
[ 1.553613] Console: switching to colour frame buffer device 240x67
[ 1.574042] i915 0000:00:02.0: fb0: i915drmfb frame buffer device
[ 1.619819] e1000e 0000:00:1f.6 0000:00:1f.6 (uninitialized): registered PHC clock
[ 1.684529] e1000e 0000:00:1f.6 eth0: (PCI Express:2.5GT/s:Width x1) c8:5b:76:72:53:1b
[ 1.684530] e1000e 0000:00:1f.6 eth0: Intel(R) PRO/1000 Network Connection
[ 1.684587] e1000e 0000:00:1f.6 eth0: MAC: 12, PHY: 12, PBA No: 1000FF-0FF
[ 1.685431] e1000e 0000:00:1f.6 enp0s31f6: renamed from eth0
[ 1.766150] ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[ 1.770260] ata1.00: ACPI cmd ef/02:00:00:00:00:a0 (SET FEATURES) succeeded
[ 1.770262] ata1.00: ACPI cmd f5/00:00:00:00:00:a0 (SECURITY FREEZE LOCK) filtered out
[ 1.771025] ata1.00: supports DRM functions and may not be fully accessible
[ 1.771941] ata1.00: NCQ Send/Recv Log not supported
[ 1.771942] ata1.00: ATA-9: Samsung SSD 840 EVO 250GB, EXT0BB6Q, max UDMA/133
[ 1.771943] ata1.00: 488397168 sectors, multi 1: LBA48 NCQ (depth 32), AA
[ 1.775380] ata1.00: ACPI cmd ef/02:00:00:00:00:a0 (SET FEATURES) succeeded
[ 1.775382] ata1.00: ACPI cmd f5/00:00:00:00:00:a0 (SECURITY FREEZE LOCK) filtered out
[ 1.776103] ata1.00: supports DRM functions and may not be fully accessible
[ 1.777040] usb 1-6: new full-speed USB device number 2 using xhci_hcd
[ 1.777050] ata1.00: NCQ Send/Recv Log not supported
[ 1.777753] ata1.00: configured for UDMA/133
[ 1.788747] scsi 0:0:0:0: Direct-Access ATA Samsung SSD 840 BB6Q PQ: 0 ANSI: 5
[ 1.788988] sd 0:0:0:0: Attached scsi generic sg0 type 0
[ 1.789013] sd 0:0:0:0: [sda] 488397168 512-byte logical blocks: (250 GB/233 GiB)
[ 1.789034] sd 0:0:0:0: [sda] Write Protect is off
[ 1.789036] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
[ 1.789042] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[ 1.806998] sda: sda1 sda2 sda3
[ 1.807693] sd 0:0:0:0: [sda] supports TCG Opal
[ 1.807694] sd 0:0:0:0: [sda] Attached SCSI disk
[ 1.908839] tsc: Refined TSC clocksource calibration: 2591.979 MHz
[ 1.908843] clocksource: tsc: mask: 0xffffffffffffffff max_cycles: 0x255ca30827e, max_idle_ns: 440795317935 ns
[ 1.910010] clocksource: Switched to clocksource tsc
[ 1.930329] usb 1-6: New USB device found, idVendor=138a, idProduct=0090, bcdDevice= 1.64
[ 1.930330] usb 1-6: New USB device strings: Mfr=0, Product=0, SerialNumber=1
[ 1.930331] usb 1-6: SerialNumber: 417580b91453
[ 2.056910] usb 1-7: new full-speed USB device number 3 using xhci_hcd
[ 2.209086] usb 1-7: New USB device found, idVendor=8087, idProduct=0029, bcdDevice= 0.01
[ 2.209087] usb 1-7: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[ 2.245043] psmouse serio1: synaptics: queried max coordinates: x [..5676], y [..4758]
[ 2.282201] psmouse serio1: synaptics: queried min coordinates: x [1266..], y [1096..]
[ 2.282221] psmouse serio1: synaptics: Your touchpad (PNP: LEN2018 PNP0f13) says it can support a different bus. If i2c-hid and hid-rmi are not used, you might want to try setting psmouse.synaptics_intertouch to 1 and report this to linux-input@vger.kernel.org.
[ 2.337417] usb 1-8: new high-speed USB device number 4 using xhci_hcd
[ 2.354352] psmouse serio1: synaptics: Touchpad model: 1, fw: 8.2, id: 0x1e2b1, caps: 0xf006a3/0x943300/0x12e800/0x10000, board id: 3053, fw id: 2010421
[ 2.354358] psmouse serio1: synaptics: serio: Synaptics pass-through port at isa0060/serio1/input0
[ 2.400477] input: SynPS/2 Synaptics TouchPad as /devices/platform/i8042/serio1/input/input5
[ 2.525910] usb 1-8: New USB device found, idVendor=04f2, idProduct=b541, bcdDevice= 0.09
[ 2.525911] usb 1-8: New USB device strings: Mfr=3, Product=1, SerialNumber=2
[ 2.525912] usb 1-8: Product: Integrated Camera
[ 2.525912] usb 1-8: Manufacturer: Chicony Electronics Co.,Ltd.
[ 2.525913] usb 1-8: SerialNumber: 0001
[ 3.094651] psmouse serio2: trackpoint: IBM TrackPoint firmware: 0x0e, buttons: 3/3
[ 3.334842] input: TPPS/2 IBM TrackPoint as /devices/platform/i8042/serio1/serio2/input/input8
[ 8.664212] EXT4-fs (dm-1): mounted filesystem with ordered data mode. Opts: (null)
[ 8.827607] systemd[1]: Inserted module 'autofs4'
[ 8.931265] systemd[1]: systemd 245.4-4ubuntu3.1 running in system mode. (+PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ +LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD +IDN2 -IDN +PCRE2 default-hierarchy=hybrid)
[ 8.949245] systemd[1]: Detected architecture x86-64.
[ 8.966683] systemd[1]: Set hostname to <for1700>.
[ 9.067139] systemd[1]: /lib/systemd/system/dbus.socket:5: ListenStream= references a path below legacy directory /var/run/, updating /var/run/dbus/system_bus_socket → /run/dbus/system_bus_socket; please update the unit file accordingly.
[ 9.127388] systemd[1]: Created slice system-modprobe.slice.
[ 9.127545] systemd[1]: Created slice Cryptsetup Units Slice.
[ 9.127679] systemd[1]: Created slice system-systemd\x2dfsck.slice.
[ 9.127890] systemd[1]: Created slice User and Session Slice.
[ 9.127937] systemd[1]: Started Forward Password Requests to Wall Directory Watch.
[ 9.128060] systemd[1]: Set up automount Arbitrary Executable File Formats File System Automount Point.
[ 9.128101] systemd[1]: Reached target User and Group Name Lookups.
[ 9.128110] systemd[1]: Reached target Remote File Systems.
[ 9.128118] systemd[1]: Reached target Slices.
[ 9.128185] systemd[1]: Listening on Device-mapper event daemon FIFOs.
[ 9.128247] systemd[1]: Listening on LVM2 poll daemon socket.
[ 9.128304] systemd[1]: Listening on Syslog Socket.
[ 9.128367] systemd[1]: Listening on fsck to fsckd communication Socket.
[ 9.128401] systemd[1]: Listening on initctl Compatibility Named Pipe.
[ 9.128543] systemd[1]: Listening on Journal Audit Socket.
[ 9.128607] systemd[1]: Listening on Journal Socket (/dev/log).
[ 9.128676] systemd[1]: Listening on Journal Socket.
[ 9.128742] systemd[1]: Listening on udev Control Socket.
[ 9.128794] systemd[1]: Listening on udev Kernel Socket.
[ 9.129469] systemd[1]: Mounting Huge Pages File System...
[ 9.130154] systemd[1]: Mounting POSIX Message Queue File System...
[ 9.131063] systemd[1]: Mounting Kernel Debug File System...
[ 9.131904] systemd[1]: Mounting Kernel Trace File System...
[ 9.133616] systemd[1]: Starting Journal Service...
[ 9.134523] systemd[1]: Starting Availability of block devices...
[ 9.135344] systemd[1]: Starting Set the console keyboard layout...
[ 9.136310] systemd[1]: Starting Create list of static device nodes for the current kernel...
[ 9.137019] systemd[1]: Starting Monitoring of LVM2 mirrors, snapshots etc. using dmeventd or progress polling...
[ 9.137074] systemd[1]: Condition check resulted in Load Kernel Module drm being skipped.
[ 9.145372] systemd[1]: Condition check resulted in Set Up Additional Binary Formats being skipped.
[ 9.145411] systemd[1]: Condition check resulted in File System Check on Root Device being skipped.
[ 9.148054] systemd[1]: Starting Load Kernel Modules...
[ 9.148794] systemd[1]: Starting Remount Root and Kernel File Systems...
[ 9.149851] systemd[1]: Starting udev Coldplug all Devices...
[ 9.150807] systemd[1]: Starting Uncomplicated firewall...
[ 9.152443] systemd[1]: Mounted Huge Pages File System.
[ 9.152619] systemd[1]: Mounted POSIX Message Queue File System.
[ 9.152780] systemd[1]: Mounted Kernel Debug File System.
[ 9.152939] systemd[1]: Mounted Kernel Trace File System.
[ 9.153404] systemd[1]: Finished Availability of block devices.
[ 9.155240] systemd[1]: Finished Create list of static device nodes for the current kernel.
[ 9.156006] systemd[1]: Finished Uncomplicated firewall.
[ 9.168088] EXT4-fs (dm-1): re-mounted. Opts: errors=remount-ro
[ 9.169788] systemd[1]: Finished Remount Root and Kernel File Systems.
[ 9.170331] systemd[1]: Condition check resulted in Rebuild Hardware Database being skipped.
[ 9.170368] systemd[1]: Condition check resulted in Platform Persistent Storage Archival being skipped.
[ 9.171440] systemd[1]: Starting Load/Save Random Seed...
[ 9.172406] lp: driver loaded but no devices found
[ 9.172583] systemd[1]: Starting Create System Users...
[ 9.176651] ppdev: user-space parallel port driver
[ 9.183203] systemd[1]: Finished Load Kernel Modules.
[ 9.184800] systemd[1]: Mounting FUSE Control File System...
[ 9.186018] systemd[1]: Mounting Kernel Configuration File System...
[ 9.187199] systemd[1]: Starting Apply Kernel Variables...
[ 9.189536] systemd[1]: Finished Load/Save Random Seed.
[ 9.189810] systemd[1]: Mounted FUSE Control File System.
[ 9.190018] systemd[1]: Mounted Kernel Configuration File System.
[ 9.192246] systemd[1]: Finished Create System Users.
[ 9.194285] systemd[1]: Starting Create Static Device Nodes in /dev...
[ 9.202439] systemd[1]: Finished Apply Kernel Variables.
[ 9.205422] systemd[1]: Finished Create Static Device Nodes in /dev.
[ 9.206335] systemd[1]: Starting udev Kernel Device Manager...
[ 9.230177] systemd[1]: Finished Monitoring of LVM2 mirrors, snapshots etc. using dmeventd or progress polling.
[ 9.246413] systemd[1]: Finished udev Coldplug all Devices.
[ 9.270551] systemd[1]: Finished Set the console keyboard layout.
[ 9.270754] systemd[1]: Reached target Local File Systems (Pre).
[ 9.272303] systemd[1]: Mounting Mount unit for core18, revision 1705...
[ 9.273250] systemd[1]: Mounting Mount unit for core18, revision 1885...
[ 9.274339] systemd[1]: Mounting Mount unit for gnome-3-34-1804, revision 24...
[ 9.275744] systemd[1]: Mounting Mount unit for gnome-3-34-1804, revision 36...
[ 9.277034] systemd[1]: Mounting Mount unit for gtk-common-themes, revision 1506...
[ 9.277946] systemd[1]: Mounting Mount unit for snap-store, revision 433...
[ 9.278890] systemd[1]: Mounting Mount unit for snap-store, revision 467...
[ 9.280116] systemd[1]: Mounting Mount unit for snapd, revision 8790...
[ 9.281496] systemd[1]: Mounting Mount unit for snapd, revision 9279...
[ 9.295061] systemd[1]: Started udev Kernel Device Manager.
[ 9.296304] systemd[1]: Starting Show Plymouth Boot Screen...
[ 9.315955] systemd[1]: plymouth-start.service: Succeeded.
[ 9.316440] systemd[1]: Started Show Plymouth Boot Screen.
[ 9.316599] systemd[1]: Condition check resulted in Dispatch Password Requests to Console Directory Watch being skipped.
[ 9.316723] systemd[1]: Started Forward Password Requests to Plymouth Directory Watch.
[ 9.377340] systemd[1]: Mounted Mount unit for core18, revision 1885.
[ 9.412509] systemd[1]: Mounted Mount unit for core18, revision 1705.
[ 9.433550] systemd[1]: Mounted Mount unit for snap-store, revision 467.
[ 9.433751] systemd[1]: Mounted Mount unit for snapd, revision 8790.
[ 9.453350] systemd[1]: Mounted Mount unit for gnome-3-34-1804, revision 24.
[ 9.454152] systemd[1]: Mounted Mount unit for gtk-common-themes, revision 1506.
[ 9.465526] systemd[1]: Created slice system-systemd\x2dbacklight.slice.
[ 9.466463] systemd[1]: Starting Load/Save Screen Backlight Brightness of backlight:intel_backlight...
[ 9.468967] mei_me 0000:00:16.0: enabling device (0000 -> 0002)
[ 9.474261] systemd[1]: Finished Load/Save Screen Backlight Brightness of backlight:intel_backlight.
[ 9.496099] compat: loading out-of-tree module taints kernel.
[ 9.496125] compat: module verification failed: signature and/or required key missing - tainting kernel
[ 9.496252] Loading modules backported from iwlwifi
[ 9.496253] iwlwifi-stack-public:release/core56:8758:f9a85a73
[ 9.533209] systemd[1]: Mounted Mount unit for snapd, revision 9279.
[ 9.550596] Bluetooth: Core ver 2.22
[ 9.550611] NET: Registered protocol family 31
[ 9.550612] Bluetooth: HCI device and connection manager initialized
[ 9.550619] Bluetooth: HCI socket layer initialized
[ 9.550621] Bluetooth: L2CAP socket layer initialized
[ 9.550624] Bluetooth: SCO socket layer initialized
[ 9.556106] cfg80211: Loading compiled-in X.509 certificates for regulatory database
[ 9.556726] pstore: Using crash dump compression: deflate
[ 9.556745] pstore: Registered efi as persistent store backend
[ 9.557213] cfg80211: Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7'
[ 9.559098] mc: Linux media interface: v0.10
[ 9.559249] ee1004 0-0050: 512 byte EE1004-compliant SPD EEPROM, read-only
[ 9.561050] Non-volatile memory driver v1.3
[ 9.565733] RAPL PMU: API unit is 2^-32 Joules, 5 fixed counters, 655360 ms ovfl timer
[ 9.565734] RAPL PMU: hw unit of domain pp0-core 2^-14 Joules
[ 9.565734] RAPL PMU: hw unit of domain package 2^-14 Joules
[ 9.565735] RAPL PMU: hw unit of domain dram 2^-14 Joules
[ 9.565736] RAPL PMU: hw unit of domain pp1-gpu 2^-14 Joules
[ 9.565736] RAPL PMU: hw unit of domain psys 2^-14 Joules
[ 9.573372] systemd[1]: Mounted Mount unit for gnome-3-34-1804, revision 36.
[ 9.575501] usbcore: registered new interface driver btusb
[ 9.578317] Intel(R) Wireless WiFi driver for Linux
[ 9.578609] iwlwifi 0000:03:00.0: enabling device (0000 -> 0002)
[ 9.583960] systemd[1]: Started Journal Service.
[ 9.584608] Bluetooth: hci0: Firmware revision 0.0 build 128 week 11 2020
[ 9.592741] videodev: Linux video capture interface: v2.00
[ 9.593587] thinkpad_acpi: ThinkPad ACPI Extras v0.26
[ 9.593588] thinkpad_acpi: http://ibm-acpi.sf.net/
[ 9.593588] thinkpad_acpi: ThinkPad BIOS R07ET91W (2.31 ), EC R07HT15W
[ 9.593589] thinkpad_acpi: Lenovo ThinkPad T460p, model 20FWCTO1WW
[ 9.594955] snd_hda_intel 0000:00:1f.3: bound 0000:00:02.0 (ops i915_audio_component_bind_ops [i915])
[ 9.597775] systemd-journald[571]: Received client request to flush runtime journal.
[ 9.606951] thinkpad_acpi: radio switch found; radios are enabled
[ 9.606971] thinkpad_acpi: This ThinkPad has standard ACPI backlight brightness control, supported by the ACPI video driver
[ 9.606971] thinkpad_acpi: Disabling thinkpad-acpi brightness events by default...
[ 9.612039] iwlwifi 0000:03:00.0: Direct firmware load for iwlwifi-cc-a0-59.ucode failed with error -2
[ 9.612068] iwlwifi 0000:03:00.0: Direct firmware load for iwlwifi-cc-a0-58.ucode failed with error -2
[ 9.612091] iwlwifi 0000:03:00.0: Direct firmware load for iwlwifi-cc-a0-57.ucode failed with error -2
[ 9.612106] iwlwifi 0000:03:00.0: Direct firmware load for iwlwifi-cc-a0-56.ucode failed with error -2
[ 9.612124] iwlwifi 0000:03:00.0: Direct firmware load for iwlwifi-cc-a0-55.ucode failed with error -2
[ 9.612143] iwlwifi 0000:03:00.0: Direct firmware load for iwlwifi-cc-a0-54.ucode failed with error -2
[ 9.612164] iwlwifi 0000:03:00.0: Direct firmware load for iwlwifi-cc-a0-53.ucode failed with error -2
[ 9.612183] iwlwifi 0000:03:00.0: Direct firmware load for iwlwifi-cc-a0-52.ucode failed with error -2
[ 9.612205] iwlwifi 0000:03:00.0: Direct firmware load for iwlwifi-cc-a0-51.ucode failed with error -2
[ 9.612225] iwlwifi 0000:03:00.0: Direct firmware load for iwlwifi-cc-a0-50.ucode failed with error -2
[ 9.612244] iwlwifi 0000:03:00.0: Direct firmware load for iwlwifi-cc-a0-49.ucode failed with error -2
[ 9.614259] thinkpad_acpi: rfkill switch tpacpi_bluetooth_sw: radio is unblocked
[ 9.619035] iwlwifi 0000:03:00.0: TLV_FW_FSEQ_VERSION: FSEQ Version: 43.2.23.17
[ 9.619038] iwlwifi 0000:03:00.0: Found debug destination: EXTERNAL_DRAM
[ 9.619040] iwlwifi 0000:03:00.0: Found debug configuration: 0
[ 9.619313] iwlwifi 0000:03:00.0: loaded firmware version 48.4fa0041f.0 cc-a0-48.ucode op_mode iwlmvm
[ 9.624717] thinkpad_acpi: Standard ACPI backlight interface available, not loading native one
[ 9.632075] thinkpad_acpi: battery 1 registered (start 0, stop 100)
[ 9.632079] battery: new extension: ThinkPad Battery Extension
[ 9.632145] input: ThinkPad Extra Buttons as /devices/platform/thinkpad_acpi/input/input9
[ 9.650481] snd_hda_codec_realtek hdaudioC0D0: autoconfig for ALC293: line_outs=1 (0x14/0x0/0x0/0x0/0x0) type:speaker
[ 9.650483] snd_hda_codec_realtek hdaudioC0D0: speaker_outs=0 (0x0/0x0/0x0/0x0/0x0)
[ 9.650484] snd_hda_codec_realtek hdaudioC0D0: hp_outs=2 (0x16/0x15/0x0/0x0/0x0)
[ 9.650485] snd_hda_codec_realtek hdaudioC0D0: mono: mono_out=0x0
[ 9.650486] snd_hda_codec_realtek hdaudioC0D0: inputs:
[ 9.650488] snd_hda_codec_realtek hdaudioC0D0: Dock Mic=0x19
[ 9.650489] snd_hda_codec_realtek hdaudioC0D0: Mic=0x1a
[ 9.650490] snd_hda_codec_realtek hdaudioC0D0: Internal Mic=0x12
[ 9.705134] iwlwifi 0000:03:00.0: Detected Intel(R) Wi-Fi 6 AX200 160MHz, REV=0x340
[ 9.709314] uvcvideo: Found UVC 1.00 device Integrated Camera (04f2:b541)
[ 9.718991] uvcvideo: Failed to initialize entity for entity 6
[ 9.718992] uvcvideo: Failed to register entities (-22).
[ 9.719039] input: Integrated Camera: Integrated C as /devices/pci0000:00/0000:00:14.0/usb1/1-8/1-8:1.0/input/input14
[ 9.719086] usbcore: registered new interface driver uvcvideo
[ 9.719087] USB Video Class driver (1.1.1)
[ 9.723989] input: HDA Intel PCH Dock Mic as /devices/pci0000:00/0000:00:1f.3/sound/card0/input10
[ 9.724045] input: HDA Intel PCH Mic as /devices/pci0000:00/0000:00:1f.3/sound/card0/input11
[ 9.724099] input: HDA Intel PCH Dock Headphone as /devices/pci0000:00/0000:00:1f.3/sound/card0/input12
[ 9.724148] input: HDA Intel PCH Headphone as /devices/pci0000:00/0000:00:1f.3/sound/card0/input13
[ 9.724197] input: HDA Intel PCH HDMI/DP,pcm=3 as /devices/pci0000:00/0000:00:1f.3/sound/card0/input15
[ 9.725017] input: HDA Intel PCH HDMI/DP,pcm=7 as /devices/pci0000:00/0000:00:1f.3/sound/card0/input16
[ 9.725084] input: HDA Intel PCH HDMI/DP,pcm=8 as /devices/pci0000:00/0000:00:1f.3/sound/card0/input17
[ 9.725129] input: HDA Intel PCH HDMI/DP,pcm=9 as /devices/pci0000:00/0000:00:1f.3/sound/card0/input18
[ 9.725203] input: HDA Intel PCH HDMI/DP,pcm=10 as /devices/pci0000:00/0000:00:1f.3/sound/card0/input19
[ 9.740557] iwlwifi 0000:03:00.0: Applying debug destination EXTERNAL_DRAM
[ 9.740785] iwlwifi 0000:03:00.0: Allocated 0x00400000 bytes for firmware monitor.
[ 9.756119] intel_rapl_common: Found RAPL domain package
[ 9.756120] intel_rapl_common: Found RAPL domain core
[ 9.756121] intel_rapl_common: Found RAPL domain uncore
[ 9.756122] intel_rapl_common: Found RAPL domain dram
[ 9.804837] psmouse serio2: Failed to deactivate mouse on synaptics-pt/serio0: -5
[ 9.907898] iwlwifi 0000:03:00.0: base HW address: 8c:c6:81:69:86:56
[ 9.923466] thermal thermal_zone3: failed to read out thermal zone (-61)
[ 9.927931] iwlwifi 0000:03:00.0 wlp3s0: renamed from wlan0
[ 11.440854] Adding 999420k swap on /dev/mapper/vgubuntu-swap_1. Priority:-2 extents:1 across:999420k SSFS
[ 11.497298] EXT4-fs (sda2): mounted filesystem with ordered data mode. Opts: (null)
[ 11.530318] audit: type=1400 audit(1601475167.981:2): apparmor="STATUS" operation="profile_load" profile="unconfined" name="libreoffice-xpdfimport" pid=885 comm="apparmor_parser"
[ 11.530694] audit: type=1400 audit(1601475167.981:3): apparmor="STATUS" operation="profile_load" profile="unconfined" name="ippusbxd" pid=883 comm="apparmor_parser"
[ 11.530812] audit: type=1400 audit(1601475167.981:4): apparmor="STATUS" operation="profile_load" profile="unconfined" name="lsb_release" pid=881 comm="apparmor_parser"
[ 11.531690] audit: type=1400 audit(1601475167.981:5): apparmor="STATUS" operation="profile_load" profile="unconfined" name="libreoffice-oopslash" pid=882 comm="apparmor_parser"
[ 11.534854] audit: type=1400 audit(1601475167.985:6): apparmor="STATUS" operation="profile_load" profile="unconfined" name="nvidia_modprobe" pid=892 comm="apparmor_parser"
[ 11.534857] audit: type=1400 audit(1601475167.985:7): apparmor="STATUS" operation="profile_load" profile="unconfined" name="nvidia_modprobe//kmod" pid=892 comm="apparmor_parser"
[ 11.535085] audit: type=1400 audit(1601475167.985:8): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/snapd/snap-confine" pid=889 comm="apparmor_parser"
[ 11.535088] audit: type=1400 audit(1601475167.985:9): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/snapd/snap-confine//mount-namespace-capture-helper" pid=889 comm="apparmor_parser"
[ 11.536143] audit: type=1400 audit(1601475167.985:10): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/bin/man" pid=894 comm="apparmor_parser"
[ 11.536146] audit: type=1400 audit(1601475167.985:11): apparmor="STATUS" operation="profile_load" profile="unconfined" name="man_filter" pid=894 comm="apparmor_parser"
[ 12.098369] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[ 12.098371] Bluetooth: BNEP filters: protocol multicast
[ 12.098375] Bluetooth: BNEP socket layer initialized
[ 12.111955] NET: Registered protocol family 38
[ 12.715313] iwlwifi 0000:03:00.0: Applying debug destination EXTERNAL_DRAM
[ 12.881456] iwlwifi 0000:03:00.0: FW already configured (0) - re-configuring
[ 14.709184] rfkill: input handler disabled
[ 15.922088] wlp3s0: authenticate with c8:08:73:6d:c9:ac
[ 15.931137] wlp3s0: send auth to c8:08:73:6d:c9:ac (try 1/3)
[ 15.956124] wlp3s0: authenticated
[ 15.956852] wlp3s0: associate with c8:08:73:6d:c9:ac (try 1/3)
[ 15.958828] wlp3s0: RX AssocResp from c8:08:73:6d:c9:ac (capab=0x1001 status=0 aid=3)
[ 15.962787] wlp3s0: associated
[ 15.964872] IPv6: ADDRCONF(NETDEV_CHANGE): wlp3s0: link becomes ready
[ 15.974486] wlp3s0: Limiting TX power to 30 (30 - 0) dBm as advertised by c8:08:73:6d:c9:ac
[ 20.821017] rfkill: input handler enabled
[ 21.298363] Bluetooth: RFCOMM TTY layer initialized
[ 21.298370] Bluetooth: RFCOMM socket layer initialized
[ 21.298376] Bluetooth: RFCOMM ver 1.11
[ 23.113916] rfkill: input handler disabled
[ 39.015042] wlp3s0: deauthenticating from c8:08:73:6d:c9:ac by local choice (Reason: 3=DEAUTH_LEAVING)
[ 244.023288] IPv6: ADDRCONF(NETDEV_CHANGE): wlp3s0: link becomes ready
[ 264.891994] iwlwifi 0000:03:00.0: Microcode SW error detected. Restarting 0x0.
[ 264.892121] iwlwifi 0000:03:00.0: Start IWL Error Log Dump:
[ 264.892127] iwlwifi 0000:03:00.0: Status: 0x00000040, count: 6
[ 264.892131] iwlwifi 0000:03:00.0: Loaded firmware version: 48.4fa0041f.0 cc-a0-48.ucode
[ 264.892136] iwlwifi 0000:03:00.0: 0x00002078 | ADVANCED_SYSASSERT
[ 264.892140] iwlwifi 0000:03:00.0: 0x00A0A200 | trm_hw_status0
[ 264.892144] iwlwifi 0000:03:00.0: 0x00000000 | trm_hw_status1
[ 264.892148] iwlwifi 0000:03:00.0: 0x004F8E3C | branchlink2
[ 264.892151] iwlwifi 0000:03:00.0: 0x004E4FF4 | interruptlink1
[ 264.892154] iwlwifi 0000:03:00.0: 0x004E4FF4 | interruptlink2
[ 264.892158] iwlwifi 0000:03:00.0: 0x07000101 | data1
[ 264.892162] iwlwifi 0000:03:00.0: 0x48308403 | data2
[ 264.892165] iwlwifi 0000:03:00.0: 0x00000005 | data3
[ 264.892168] iwlwifi 0000:03:00.0: 0x5FC051BE | beacon time
[ 264.892172] iwlwifi 0000:03:00.0: 0x0F076C4E | tsf low
[ 264.892175] iwlwifi 0000:03:00.0: 0x00000000 | tsf hi
[ 264.892179] iwlwifi 0000:03:00.0: 0x00000000 | time gp1
[ 264.892182] iwlwifi 0000:03:00.0: 0x0F07D7C1 | time gp2
[ 264.892186] iwlwifi 0000:03:00.0: 0x00000001 | uCode revision type
[ 264.892189] iwlwifi 0000:03:00.0: 0x00000030 | uCode version major
[ 264.892193] iwlwifi 0000:03:00.0: 0x4FA0041F | uCode version minor
[ 264.892196] iwlwifi 0000:03:00.0: 0x00000340 | hw version
[ 264.892200] iwlwifi 0000:03:00.0: 0x00489000 | board version
[ 264.892203] iwlwifi 0000:03:00.0: 0x801EFC09 | hcmd
[ 264.892206] iwlwifi 0000:03:00.0: 0x24020000 | isr0
[ 264.892210] iwlwifi 0000:03:00.0: 0x61000000 | isr1
[ 264.892213] iwlwifi 0000:03:00.0: 0x18F00002 | isr2
[ 264.892216] iwlwifi 0000:03:00.0: 0x00C1FFCC | isr3
[ 264.892220] iwlwifi 0000:03:00.0: 0x00000000 | isr4
[ 264.892223] iwlwifi 0000:03:00.0: 0x040D001C | last cmd Id
[ 264.892227] iwlwifi 0000:03:00.0: 0x00016D22 | wait_event
[ 264.892230] iwlwifi 0000:03:00.0: 0x00000000 | l2p_control
[ 264.892234] iwlwifi 0000:03:00.0: 0x00018034 | l2p_duration
[ 264.892237] iwlwifi 0000:03:00.0: 0x0000003F | l2p_mhvalid
[ 264.892241] iwlwifi 0000:03:00.0: 0x00CB0000 | l2p_addr_match
[ 264.892244] iwlwifi 0000:03:00.0: 0x00000009 | lmpm_pmg_sel
[ 264.892248] iwlwifi 0000:03:00.0: 0x00000000 | timestamp
[ 264.892251] iwlwifi 0000:03:00.0: 0x00006038 | flow_handler
[ 264.892309] iwlwifi 0000:03:00.0: Start IWL Error Log Dump:
[ 264.892313] iwlwifi 0000:03:00.0: Status: 0x00000040, count: 7
[ 264.892317] iwlwifi 0000:03:00.0: 0x20000070 | NMI_INTERRUPT_LMAC_FATAL
[ 264.892321] iwlwifi 0000:03:00.0: 0x00000000 | umac branchlink1
[ 264.892324] iwlwifi 0000:03:00.0: 0xC008CC3C | umac branchlink2
[ 264.892327] iwlwifi 0000:03:00.0: 0x8048D0E6 | umac interruptlink1
[ 264.892331] iwlwifi 0000:03:00.0: 0x8048D0E6 | umac interruptlink2
[ 264.892334] iwlwifi 0000:03:00.0: 0x00000400 | umac data1
[ 264.892338] iwlwifi 0000:03:00.0: 0x8048D0E6 | umac data2
[ 264.892341] iwlwifi 0000:03:00.0: 0x00000000 | umac data3
[ 264.892344] iwlwifi 0000:03:00.0: 0x00000030 | umac major
[ 264.892348] iwlwifi 0000:03:00.0: 0x4FA0041F | umac minor
[ 264.892351] iwlwifi 0000:03:00.0: 0x0F07D7D1 | frame pointer
[ 264.892355] iwlwifi 0000:03:00.0: 0xC0886284 | stack pointer
[ 264.892358] iwlwifi 0000:03:00.0: 0x00C8050F | last host cmd
[ 264.892361] iwlwifi 0000:03:00.0: 0x00000000 | isr status reg
[ 264.892392] iwlwifi 0000:03:00.0: Fseq Registers:
[ 264.892405] iwlwifi 0000:03:00.0: 0xE0000101 | FSEQ_ERROR_CODE
[ 264.892419] iwlwifi 0000:03:00.0: 0x00290011 | FSEQ_TOP_INIT_VERSION
[ 264.892432] iwlwifi 0000:03:00.0: 0x80050008 | FSEQ_CNVIO_INIT_VERSION
[ 264.892445] iwlwifi 0000:03:00.0: 0x0000A503 | FSEQ_OTP_VERSION
[ 264.892458] iwlwifi 0000:03:00.0: 0x80000003 | FSEQ_TOP_CONTENT_VERSION
[ 264.892471] iwlwifi 0000:03:00.0: 0x4552414E | FSEQ_ALIVE_TOKEN
[ 264.892484] iwlwifi 0000:03:00.0: 0x00100530 | FSEQ_CNVI_ID
[ 264.892497] iwlwifi 0000:03:00.0: 0x00000532 | FSEQ_CNVR_ID
[ 264.892510] iwlwifi 0000:03:00.0: 0x00100530 | CNVI_AUX_MISC_CHIP
[ 264.892525] iwlwifi 0000:03:00.0: 0x00000532 | CNVR_AUX_MISC_CHIP
[ 264.892541] iwlwifi 0000:03:00.0: 0x05B0905B | CNVR_SCU_SD_REGS_SD_REG_DIG_DCDC_VTRIM
[ 264.892556] iwlwifi 0000:03:00.0: 0x0000025B | CNVR_SCU_SD_REGS_SD_REG_ACTIVE_VDIG_MIRROR
[ 264.892706] iwlwifi 0000:03:00.0: Collecting data: trigger 2 fired.
[ 264.892717] ieee80211 phy0: Hardware restart was requested
[ 264.892797] iwlwifi 0000:03:00.0: FW error in SYNC CMD ADD_STA
[ 264.892807] CPU: 3 PID: 4905 Comm: hostapd Tainted: G OE 5.8.0-050800-generic #202008022230
[ 264.892809] Hardware name: LENOVO 20FWCTO1WW/20FWCTO1WW, BIOS R07ET91W (2.31 ) 12/11/2019
[ 264.892811] Call Trace:
[ 264.892825] dump_stack+0x70/0x8d
[ 264.892861] iwl_trans_pcie_gen2_send_hcmd+0x421/0x430 [iwlwifi]
[ 264.892872] ? wait_woken+0x80/0x80
[ 264.892899] iwl_trans_send_cmd+0x55/0xc0 [iwlwifi]
[ 264.892929] iwl_mvm_send_cmd_status+0x38/0xd0 [iwlmvm]
[ 264.892953] iwl_mvm_send_cmd_pdu_status+0x53/0x70 [iwlmvm]
[ 264.892985] iwl_mvm_sta_send_to_fw+0x1e1/0x330 [iwlmvm]
[ 264.893004] iwl_mvm_mac_sta_state+0x3e1/0x720 [iwlmvm]
[ 264.893050] drv_sta_state+0x91/0x3f0 [mac80211]
[ 264.893087] sta_info_move_state+0x276/0x370 [mac80211]
[ 264.893132] sta_apply_auth_flags.isra.0+0x73/0x140 [mac80211]
[ 264.893173] sta_apply_parameters+0x336/0x490 [mac80211]
[ 264.893208] ieee80211_change_station+0x137/0x2a0 [mac80211]
[ 264.893262] ? nl80211_parse_sta_wme+0x57/0xc0 [cfg80211]
[ 264.893306] nl80211_set_station+0x381/0x450 [cfg80211]
[ 264.893320] genl_family_rcv_msg+0x17b/0x290
[ 264.893330] genl_rcv_msg+0x4c/0xa0
[ 264.893339] ? genl_family_rcv_msg+0x290/0x290
[ 264.893346] netlink_rcv_skb+0x4e/0x110
[ 264.893354] genl_rcv+0x29/0x40
[ 264.893361] netlink_unicast+0x218/0x330
[ 264.893369] netlink_sendmsg+0x233/0x460
[ 264.893379] sock_sendmsg+0x65/0x70
[ 264.893389] ____sys_sendmsg+0x257/0x2a0
[ 264.893399] ? sendmsg_copy_msghdr+0x7e/0xa0
[ 264.893408] ___sys_sendmsg+0x82/0xc0
[ 264.893418] ? ___sys_recvmsg+0xa3/0x130
[ 264.893428] ? update_process_times+0x7a/0xa0
[ 264.893435] ? enqueue_hrtimer+0x40/0x90
[ 264.893445] ? recalibrate_cpu_khz+0x10/0x10
[ 264.893452] ? ktime_get_ts64+0x4c/0xf0
[ 264.893464] ? __cgroup_bpf_run_filter_setsockopt+0xb0/0x2d0
[ 264.893474] __sys_sendmsg+0x62/0xb0
[ 264.893483] __x64_sys_sendmsg+0x1f/0x30
[ 264.893495] do_syscall_64+0x52/0xc0
[ 264.893505] entry_SYSCALL_64_after_hwframe+0x44/0xa9
[ 264.893514] RIP: 0033:0x7f113d47e5b7
[ 264.893522] Code: 64 89 02 48 c7 c0 ff ff ff ff eb bb 0f 1f 80 00 00 00 00 f3 0f 1e fa 64 8b 04 25 18 00 00 00 85 c0 75 10 b8 2e 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 51 c3 48 83 ec 28 89 54 24 1c 48 89 74 24 10
[ 264.893528] RSP: 002b:00007fff67b087e8 EFLAGS: 00000246 ORIG_RAX: 000000000000002e
[ 264.893537] RAX: ffffffffffffffda RBX: 0000555aa4b7b1d0 RCX: 00007f113d47e5b7
[ 264.893539] RDX: 0000000000000000 RSI: 00007fff67b08820 RDI: 0000000000000005
[ 264.893541] RBP: 0000555aa4b849e0 R08: 0000000000000004 R09: 00007f113d547250
[ 264.893543] R10: 00007fff67b08904 R11: 0000000000000246 R12: 0000555aa4b79690
[ 264.893545] R13: 00007fff67b08820 R14: 0000000000000000 R15: 0000000000000000
[ 265.487552] iwlwifi 0000:03:00.0: Applying debug destination EXTERNAL_DRAM
[ 265.658825] iwlwifi 0000:03:00.0: FW already configured (0) - re-configuring
[ 273.606994] iwlwifi 0000:03:00.0: Microcode SW error detected. Restarting 0x0.
[ 273.607115] iwlwifi 0000:03:00.0: Start IWL Error Log Dump:
[ 273.607121] iwlwifi 0000:03:00.0: Status: 0x00000040, count: 6
[ 273.607125] iwlwifi 0000:03:00.0: Loaded firmware version: 48.4fa0041f.0 cc-a0-48.ucode
[ 273.607130] iwlwifi 0000:03:00.0: 0x00002078 | ADVANCED_SYSASSERT
[ 273.607134] iwlwifi 0000:03:00.0: 0x00A0A200 | trm_hw_status0
[ 273.607138] iwlwifi 0000:03:00.0: 0x00000000 | trm_hw_status1
[ 273.607142] iwlwifi 0000:03:00.0: 0x004F8E3C | branchlink2
[ 273.607145] iwlwifi 0000:03:00.0: 0x004E4FF4 | interruptlink1
[ 273.607148] iwlwifi 0000:03:00.0: 0x004E4FF4 | interruptlink2
[ 273.607152] iwlwifi 0000:03:00.0: 0x07000101 | data1
[ 273.607155] iwlwifi 0000:03:00.0: 0x48308403 | data2
[ 273.607159] iwlwifi 0000:03:00.0: 0x00000005 | data3
[ 273.607162] iwlwifi 0000:03:00.0: 0x00000000 | beacon time
[ 273.607166] iwlwifi 0000:03:00.0: 0x007B77D2 | tsf low
[ 273.607169] iwlwifi 0000:03:00.0: 0x00000000 | tsf hi
[ 273.607172] iwlwifi 0000:03:00.0: 0x00000000 | time gp1
[ 273.607176] iwlwifi 0000:03:00.0: 0x007BE2A7 | time gp2
[ 273.607179] iwlwifi 0000:03:00.0: 0x00000001 | uCode revision type
[ 273.607183] iwlwifi 0000:03:00.0: 0x00000030 | uCode version major
[ 273.607187] iwlwifi 0000:03:00.0: 0x4FA0041F | uCode version minor
[ 273.607190] iwlwifi 0000:03:00.0: 0x00000340 | hw version
[ 273.607193] iwlwifi 0000:03:00.0: 0x00489000 | board version
[ 273.607197] iwlwifi 0000:03:00.0: 0x809FFC09 | hcmd
[ 273.607200] iwlwifi 0000:03:00.0: 0x24020000 | isr0
[ 273.607204] iwlwifi 0000:03:00.0: 0x61000000 | isr1
[ 273.607207] iwlwifi 0000:03:00.0: 0x18F00002 | isr2
[ 273.607210] iwlwifi 0000:03:00.0: 0x00C1FFCC | isr3
[ 273.607214] iwlwifi 0000:03:00.0: 0x00000000 | isr4
[ 273.607217] iwlwifi 0000:03:00.0: 0x0405001C | last cmd Id
[ 273.607221] iwlwifi 0000:03:00.0: 0x00016D22 | wait_event
[ 273.607224] iwlwifi 0000:03:00.0: 0x00000000 | l2p_control
[ 273.607228] iwlwifi 0000:03:00.0: 0x00018034 | l2p_duration
[ 273.607231] iwlwifi 0000:03:00.0: 0x0000003F | l2p_mhvalid
[ 273.607234] iwlwifi 0000:03:00.0: 0x00CB0000 | l2p_addr_match
[ 273.607238] iwlwifi 0000:03:00.0: 0x00000009 | lmpm_pmg_sel
[ 273.607241] iwlwifi 0000:03:00.0: 0x00000000 | timestamp
[ 273.607245] iwlwifi 0000:03:00.0: 0x00004090 | flow_handler
[ 273.607303] iwlwifi 0000:03:00.0: Start IWL Error Log Dump:
[ 273.607307] iwlwifi 0000:03:00.0: Status: 0x00000040, count: 7
[ 273.607311] iwlwifi 0000:03:00.0: 0x20000070 | NMI_INTERRUPT_LMAC_FATAL
[ 273.607314] iwlwifi 0000:03:00.0: 0x00000000 | umac branchlink1
[ 273.607318] iwlwifi 0000:03:00.0: 0xC008CC3C | umac branchlink2
[ 273.607321] iwlwifi 0000:03:00.0: 0x8048D0E6 | umac interruptlink1
[ 273.607325] iwlwifi 0000:03:00.0: 0x8048D0E6 | umac interruptlink2
[ 273.607328] iwlwifi 0000:03:00.0: 0x00000400 | umac data1
[ 273.607331] iwlwifi 0000:03:00.0: 0x8048D0E6 | umac data2
[ 273.607335] iwlwifi 0000:03:00.0: 0x00000000 | umac data3
[ 273.607338] iwlwifi 0000:03:00.0: 0x00000030 | umac major
[ 273.607341] iwlwifi 0000:03:00.0: 0x4FA0041F | umac minor
[ 273.607345] iwlwifi 0000:03:00.0: 0x007BE2B8 | frame pointer
[ 273.607348] iwlwifi 0000:03:00.0: 0xC0886284 | stack pointer
[ 273.607352] iwlwifi 0000:03:00.0: 0x003C050F | last host cmd
[ 273.607355] iwlwifi 0000:03:00.0: 0x00000000 | isr status reg
[ 273.607386] iwlwifi 0000:03:00.0: Fseq Registers:
[ 273.607399] iwlwifi 0000:03:00.0: 0xE0000101 | FSEQ_ERROR_CODE
[ 273.607412] iwlwifi 0000:03:00.0: 0x00290011 | FSEQ_TOP_INIT_VERSION
[ 273.607425] iwlwifi 0000:03:00.0: 0x80050008 | FSEQ_CNVIO_INIT_VERSION
[ 273.607438] iwlwifi 0000:03:00.0: 0x0000A503 | FSEQ_OTP_VERSION
[ 273.607451] iwlwifi 0000:03:00.0: 0x80000003 | FSEQ_TOP_CONTENT_VERSION
[ 273.607464] iwlwifi 0000:03:00.0: 0x4552414E | FSEQ_ALIVE_TOKEN
[ 273.607477] iwlwifi 0000:03:00.0: 0x00100530 | FSEQ_CNVI_ID
[ 273.607491] iwlwifi 0000:03:00.0: 0x00000532 | FSEQ_CNVR_ID
[ 273.607504] iwlwifi 0000:03:00.0: 0x00100530 | CNVI_AUX_MISC_CHIP
[ 273.607519] iwlwifi 0000:03:00.0: 0x00000532 | CNVR_AUX_MISC_CHIP
[ 273.607534] iwlwifi 0000:03:00.0: 0x05B0905B | CNVR_SCU_SD_REGS_SD_REG_DIG_DCDC_VTRIM
[ 273.607549] iwlwifi 0000:03:00.0: 0x0000025B | CNVR_SCU_SD_REGS_SD_REG_ACTIVE_VDIG_MIRROR
[ 273.607700] iwlwifi 0000:03:00.0: Collecting data: trigger 2 fired.
[ 273.607710] ieee80211 phy0: Hardware restart was requested
[ 273.607783] iwlwifi 0000:03:00.0: FW error in SYNC CMD ADD_STA
[ 273.607794] CPU: 3 PID: 4905 Comm: hostapd Tainted: G OE 5.8.0-050800-generic #202008022230
[ 273.607796] Hardware name: LENOVO 20FWCTO1WW/20FWCTO1WW, BIOS R07ET91W (2.31 ) 12/11/2019
[ 273.607797] Call Trace:
[ 273.607811] dump_stack+0x70/0x8d
[ 273.607846] iwl_trans_pcie_gen2_send_hcmd+0x421/0x430 [iwlwifi]
[ 273.607854] ? wait_woken+0x80/0x80
[ 273.607875] iwl_trans_send_cmd+0x55/0xc0 [iwlwifi]
[ 273.607899] iwl_mvm_send_cmd_status+0x38/0xd0 [iwlmvm]
[ 273.607919] iwl_mvm_send_cmd_pdu_status+0x53/0x70 [iwlmvm]
[ 273.607941] iwl_mvm_sta_send_to_fw+0x1e1/0x330 [iwlmvm]
[ 273.607958] iwl_mvm_mac_sta_state+0x3e1/0x720 [iwlmvm]
[ 273.607999] drv_sta_state+0x91/0x3f0 [mac80211]
[ 273.608031] sta_info_move_state+0x276/0x370 [mac80211]
[ 273.608072] sta_apply_auth_flags.isra.0+0x73/0x140 [mac80211]
[ 273.608109] sta_apply_parameters+0x336/0x490 [mac80211]
[ 273.608142] ieee80211_change_station+0x137/0x2a0 [mac80211]
[ 273.608191] ? nl80211_parse_sta_wme+0x57/0xc0 [cfg80211]
[ 273.608230] nl80211_set_station+0x381/0x450 [cfg80211]
[ 273.608240] genl_family_rcv_msg+0x17b/0x290
[ 273.608246] genl_rcv_msg+0x4c/0xa0
[ 273.608249] ? genl_family_rcv_msg+0x290/0x290
[ 273.608253] netlink_rcv_skb+0x4e/0x110
[ 273.608258] genl_rcv+0x29/0x40
[ 273.608261] netlink_unicast+0x218/0x330
[ 273.608265] netlink_sendmsg+0x233/0x460
[ 273.608273] sock_sendmsg+0x65/0x70
[ 273.608278] ____sys_sendmsg+0x257/0x2a0
[ 273.608284] ? sendmsg_copy_msghdr+0x7e/0xa0
[ 273.608290] ___sys_sendmsg+0x82/0xc0
[ 273.608296] ? ___sys_recvmsg+0xa3/0x130
[ 273.608302] ? __sys_sendto+0x113/0x190
[ 273.608309] ? recalibrate_cpu_khz+0x10/0x10
[ 273.608314] ? ktime_get_ts64+0x4c/0xf0
[ 273.608321] ? __cgroup_bpf_run_filter_setsockopt+0xb0/0x2d0
[ 273.608327] __sys_sendmsg+0x62/0xb0
[ 273.608334] __x64_sys_sendmsg+0x1f/0x30
[ 273.608340] do_syscall_64+0x52/0xc0
[ 273.608347] entry_SYSCALL_64_after_hwframe+0x44/0xa9
[ 273.608351] RIP: 0033:0x7f113d47e5b7
[ 273.608357] Code: 64 89 02 48 c7 c0 ff ff ff ff eb bb 0f 1f 80 00 00 00 00 f3 0f 1e fa 64 8b 04 25 18 00 00 00 85 c0 75 10 b8 2e 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 51 c3 48 83 ec 28 89 54 24 1c 48 89 74 24 10
[ 273.608360] RSP: 002b:00007fff67b087e8 EFLAGS: 00000246 ORIG_RAX: 000000000000002e
[ 273.608364] RAX: ffffffffffffffda RBX: 0000555aa4b7b1d0 RCX: 00007f113d47e5b7
[ 273.608366] RDX: 0000000000000000 RSI: 00007fff67b08820 RDI: 0000000000000005
[ 273.608368] RBP: 0000555aa4b81440 R08: 0000000000000004 R09: 00007f113d547210
[ 273.608370] R10: 00007fff67b08904 R11: 0000000000000246 R12: 0000555aa4b79690
[ 273.608372] R13: 00007fff67b08820 R14: 0000000000000000 R15: 0000000000000000
[ 274.214596] iwlwifi 0000:03:00.0: Applying debug destination EXTERNAL_DRAM
[ 274.386784] iwlwifi 0000:03:00.0: FW already configured (0) - re-configuring
[ 301.540720] iwlwifi 0000:03:00.0: Microcode SW error detected. Restarting 0x0.
[ 301.540899] iwlwifi 0000:03:00.0: Start IWL Error Log Dump:
[ 301.540909] iwlwifi 0000:03:00.0: Status: 0x00000040, count: 6
[ 301.540915] iwlwifi 0000:03:00.0: Loaded firmware version: 48.4fa0041f.0 cc-a0-48.ucode
[ 301.540931] iwlwifi 0000:03:00.0: 0x00002078 | ADVANCED_SYSASSERT
[ 301.540938] iwlwifi 0000:03:00.0: 0x000022F0 | trm_hw_status0
[ 301.540948] iwlwifi 0000:03:00.0: 0x00000000 | trm_hw_status1
[ 301.540954] iwlwifi 0000:03:00.0: 0x004F8E3C | branchlink2
[ 301.540960] iwlwifi 0000:03:00.0: 0x004E4FF4 | interruptlink1
[ 301.540965] iwlwifi 0000:03:00.0: 0x004E4FF4 | interruptlink2
[ 301.540971] iwlwifi 0000:03:00.0: 0x07000101 | data1
[ 301.540976] iwlwifi 0000:03:00.0: 0x48308403 | data2
[ 301.540982] iwlwifi 0000:03:00.0: 0x00000005 | data3
[ 301.540987] iwlwifi 0000:03:00.0: 0x00000000 | beacon time
[ 301.540997] iwlwifi 0000:03:00.0: 0x01A0891F | tsf low
[ 301.541007] iwlwifi 0000:03:00.0: 0x00000000 | tsf hi
[ 301.541017] iwlwifi 0000:03:00.0: 0x00000000 | time gp1
[ 301.541023] iwlwifi 0000:03:00.0: 0x01A0F3D4 | time gp2
[ 301.541029] iwlwifi 0000:03:00.0: 0x00000001 | uCode revision type
[ 301.541035] iwlwifi 0000:03:00.0: 0x00000030 | uCode version major
[ 301.541040] iwlwifi 0000:03:00.0: 0x4FA0041F | uCode version minor
[ 301.541048] iwlwifi 0000:03:00.0: 0x00000340 | hw version
[ 301.541059] iwlwifi 0000:03:00.0: 0x00489000 | board version
[ 301.541068] iwlwifi 0000:03:00.0: 0x806DFC09 | hcmd
[ 301.541073] iwlwifi 0000:03:00.0: 0x00020000 | isr0
[ 301.541078] iwlwifi 0000:03:00.0: 0x60000000 | isr1
[ 301.541082] iwlwifi 0000:03:00.0: 0x18F00002 | isr2
[ 301.541092] iwlwifi 0000:03:00.0: 0x00C1FFCD | isr3
[ 301.541104] iwlwifi 0000:03:00.0: 0x00000000 | isr4
[ 301.541109] iwlwifi 0000:03:00.0: 0x0407001C | last cmd Id
[ 301.541115] iwlwifi 0000:03:00.0: 0x000067F4 | wait_event
[ 301.541122] iwlwifi 0000:03:00.0: 0x00000000 | l2p_control
[ 301.541126] iwlwifi 0000:03:00.0: 0x00000020 | l2p_duration
[ 301.541131] iwlwifi 0000:03:00.0: 0x0000003F | l2p_mhvalid
[ 301.541136] iwlwifi 0000:03:00.0: 0x00CB0000 | l2p_addr_match
[ 301.541140] iwlwifi 0000:03:00.0: 0x00000009 | lmpm_pmg_sel
[ 301.541145] iwlwifi 0000:03:00.0: 0x00000000 | timestamp
[ 301.541149] iwlwifi 0000:03:00.0: 0x000058A0 | flow_handler
[ 301.541221] iwlwifi 0000:03:00.0: Start IWL Error Log Dump:
[ 301.541227] iwlwifi 0000:03:00.0: Status: 0x00000040, count: 7
[ 301.541238] iwlwifi 0000:03:00.0: 0x20000070 | NMI_INTERRUPT_LMAC_FATAL
[ 301.541243] iwlwifi 0000:03:00.0: 0x00000000 | umac branchlink1
[ 301.541250] iwlwifi 0000:03:00.0: 0xC008CC3C | umac branchlink2
[ 301.541258] iwlwifi 0000:03:00.0: 0x8048D0E6 | umac interruptlink1
[ 301.541263] iwlwifi 0000:03:00.0: 0x8048D0E6 | umac interruptlink2
[ 301.541272] iwlwifi 0000:03:00.0: 0x00000400 | umac data1
[ 301.541277] iwlwifi 0000:03:00.0: 0x8048D0E6 | umac data2
[ 301.541286] iwlwifi 0000:03:00.0: 0x00000000 | umac data3
[ 301.541291] iwlwifi 0000:03:00.0: 0x00000030 | umac major
[ 301.541299] iwlwifi 0000:03:00.0: 0x4FA0041F | umac minor
[ 301.541307] iwlwifi 0000:03:00.0: 0x01A0F3E4 | frame pointer
[ 301.541313] iwlwifi 0000:03:00.0: 0xC0886284 | stack pointer
[ 301.541317] iwlwifi 0000:03:00.0: 0x003C050F | last host cmd
[ 301.541327] iwlwifi 0000:03:00.0: 0x00000000 | isr status reg
[ 301.541367] iwlwifi 0000:03:00.0: Fseq Registers:
[ 301.541383] iwlwifi 0000:03:00.0: 0xE0000101 | FSEQ_ERROR_CODE
[ 301.541399] iwlwifi 0000:03:00.0: 0x00290011 | FSEQ_TOP_INIT_VERSION
[ 301.541415] iwlwifi 0000:03:00.0: 0x80050008 | FSEQ_CNVIO_INIT_VERSION
[ 301.541430] iwlwifi 0000:03:00.0: 0x0000A503 | FSEQ_OTP_VERSION
[ 301.541447] iwlwifi 0000:03:00.0: 0x80000003 | FSEQ_TOP_CONTENT_VERSION
[ 301.541463] iwlwifi 0000:03:00.0: 0x4552414E | FSEQ_ALIVE_TOKEN
[ 301.541479] iwlwifi 0000:03:00.0: 0x00100530 | FSEQ_CNVI_ID
[ 301.541495] iwlwifi 0000:03:00.0: 0x00000532 | FSEQ_CNVR_ID
[ 301.541511] iwlwifi 0000:03:00.0: 0x00100530 | CNVI_AUX_MISC_CHIP
[ 301.541530] iwlwifi 0000:03:00.0: 0x00000532 | CNVR_AUX_MISC_CHIP
[ 301.541549] iwlwifi 0000:03:00.0: 0x05B0905B | CNVR_SCU_SD_REGS_SD_REG_DIG_DCDC_VTRIM
[ 301.541569] iwlwifi 0000:03:00.0: 0x0000025B | CNVR_SCU_SD_REGS_SD_REG_ACTIVE_VDIG_MIRROR
[ 301.541739] iwlwifi 0000:03:00.0: Collecting data: trigger 2 fired.
[ 301.541755] ieee80211 phy0: Hardware restart was requested
[ 301.541790] iwlwifi 0000:03:00.0: FW error in SYNC CMD ADD_STA
[ 301.541801] CPU: 3 PID: 4905 Comm: hostapd Tainted: G OE 5.8.0-050800-generic #202008022230
[ 301.541803] Hardware name: LENOVO 20FWCTO1WW/20FWCTO1WW, BIOS R07ET91W (2.31 ) 12/11/2019
[ 301.541804] Call Trace:
[ 301.541818] dump_stack+0x70/0x8d
[ 301.541852] iwl_trans_pcie_gen2_send_hcmd+0x421/0x430 [iwlwifi]
[ 301.541860] ? wait_woken+0x80/0x80
[ 301.541880] iwl_trans_send_cmd+0x55/0xc0 [iwlwifi]
[ 301.541903] iwl_mvm_send_cmd_status+0x38/0xd0 [iwlmvm]
[ 301.541922] iwl_mvm_send_cmd_pdu_status+0x53/0x70 [iwlmvm]
[ 301.541943] iwl_mvm_sta_send_to_fw+0x1e1/0x330 [iwlmvm]
[ 301.541958] iwl_mvm_mac_sta_state+0x3e1/0x720 [iwlmvm]
[ 301.541996] drv_sta_state+0x91/0x3f0 [mac80211]
[ 301.542026] sta_info_move_state+0x276/0x370 [mac80211]
[ 301.542064] sta_apply_auth_flags.isra.0+0x73/0x140 [mac80211]
[ 301.542099] sta_apply_parameters+0x336/0x490 [mac80211]
[ 301.542130] ieee80211_change_station+0x137/0x2a0 [mac80211]
[ 301.542176] ? nl80211_parse_sta_wme+0x57/0xc0 [cfg80211]
[ 301.542212] nl80211_set_station+0x381/0x450 [cfg80211]
[ 301.542224] genl_family_rcv_msg+0x17b/0x290
[ 301.542230] genl_rcv_msg+0x4c/0xa0
[ 301.542233] ? genl_family_rcv_msg+0x290/0x290
[ 301.542237] netlink_rcv_skb+0x4e/0x110
[ 301.542241] genl_rcv+0x29/0x40
[ 301.542245] netlink_unicast+0x218/0x330
[ 301.542249] netlink_sendmsg+0x233/0x460
[ 301.542257] sock_sendmsg+0x65/0x70
[ 301.542262] ____sys_sendmsg+0x257/0x2a0
[ 301.542267] ? sendmsg_copy_msghdr+0x7e/0xa0
[ 301.542274] ___sys_sendmsg+0x82/0xc0
[ 301.542279] ? ___sys_recvmsg+0xa3/0x130
[ 301.542286] ? __sys_sendto+0x113/0x190
[ 301.542292] ? recalibrate_cpu_khz+0x10/0x10
[ 301.542296] ? ktime_get_ts64+0x4c/0xf0
[ 301.542304] ? __cgroup_bpf_run_filter_setsockopt+0xb0/0x2d0
[ 301.542310] __sys_sendmsg+0x62/0xb0
[ 301.542316] __x64_sys_sendmsg+0x1f/0x30
[ 301.542322] do_syscall_64+0x52/0xc0
[ 301.542329] entry_SYSCALL_64_after_hwframe+0x44/0xa9
[ 301.542333] RIP: 0033:0x7f113d47e5b7
[ 301.542338] Code: 64 89 02 48 c7 c0 ff ff ff ff eb bb 0f 1f 80 00 00 00 00 f3 0f 1e fa 64 8b 04 25 18 00 00 00 85 c0 75 10 b8 2e 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 51 c3 48 83 ec 28 89 54 24 1c 48 89 74 24 10
[ 301.542341] RSP: 002b:00007fff67b087e8 EFLAGS: 00000246 ORIG_RAX: 000000000000002e
[ 301.542346] RAX: ffffffffffffffda RBX: 0000555aa4b7b1d0 RCX: 00007f113d47e5b7
[ 301.542348] RDX: 0000000000000000 RSI: 00007fff67b08820 RDI: 0000000000000005
[ 301.542350] RBP: 0000555aa4b849e0 R08: 0000000000000004 R09: 00007f113d547200
[ 301.542352] R10: 00007fff67b08904 R11: 0000000000000246 R12: 0000555aa4b79690
[ 301.542354] R13: 00007fff67b08820 R14: 0000000000000000 R15: 0000000000000000
[ 302.114359] iwlwifi 0000:03:00.0: Failed to trigger RX queues sync (-5)
[ 302.142259] iwlwifi 0000:03:00.0: Applying debug destination EXTERNAL_DRAM
[ 302.314495] iwlwifi 0000:03:00.0: FW already configured (0) - re-configuring
[ 304.802335] iwlwifi 0000:03:00.0: Microcode SW error detected. Restarting 0x0.
[ 304.802458] iwlwifi 0000:03:00.0: Start IWL Error Log Dump:
[ 304.802463] iwlwifi 0000:03:00.0: Status: 0x00000040, count: 6
[ 304.802467] iwlwifi 0000:03:00.0: Loaded firmware version: 48.4fa0041f.0 cc-a0-48.ucode
[ 304.802472] iwlwifi 0000:03:00.0: 0x00002078 | ADVANCED_SYSASSERT
[ 304.802476] iwlwifi 0000:03:00.0: 0x00A0A200 | trm_hw_status0
[ 304.802479] iwlwifi 0000:03:00.0: 0x00000000 | trm_hw_status1
[ 304.802483] iwlwifi 0000:03:00.0: 0x004F8E3C | branchlink2
[ 304.802486] iwlwifi 0000:03:00.0: 0x004E4FF4 | interruptlink1
[ 304.802490] iwlwifi 0000:03:00.0: 0x004E4FF4 | interruptlink2
[ 304.802493] iwlwifi 0000:03:00.0: 0x07000101 | data1
[ 304.802497] iwlwifi 0000:03:00.0: 0x48308403 | data2
[ 304.802500] iwlwifi 0000:03:00.0: 0x00000005 | data3
[ 304.802503] iwlwifi 0000:03:00.0: 0x00000000 | beacon time
[ 304.802507] iwlwifi 0000:03:00.0: 0x00282AF5 | tsf low
[ 304.802510] iwlwifi 0000:03:00.0: 0x00000000 | tsf hi
[ 304.802514] iwlwifi 0000:03:00.0: 0x00000000 | time gp1
[ 304.802517] iwlwifi 0000:03:00.0: 0x002894ED | time gp2
[ 304.802520] iwlwifi 0000:03:00.0: 0x00000001 | uCode revision type
[ 304.802524] iwlwifi 0000:03:00.0: 0x00000030 | uCode version major
[ 304.802528] iwlwifi 0000:03:00.0: 0x4FA0041F | uCode version minor
[ 304.802531] iwlwifi 0000:03:00.0: 0x00000340 | hw version
[ 304.802535] iwlwifi 0000:03:00.0: 0x00489000 | board version
[ 304.802538] iwlwifi 0000:03:00.0: 0x8024FC09 | hcmd
[ 304.802542] iwlwifi 0000:03:00.0: 0x24020000 | isr0
[ 304.802545] iwlwifi 0000:03:00.0: 0x61000000 | isr1
[ 304.802548] iwlwifi 0000:03:00.0: 0x18F00002 | isr2
[ 304.802551] iwlwifi 0000:03:00.0: 0x00C1FFDC | isr3
[ 304.802555] iwlwifi 0000:03:00.0: 0x00000000 | isr4
[ 304.802558] iwlwifi 0000:03:00.0: 0x0404001C | last cmd Id
[ 304.802562] iwlwifi 0000:03:00.0: 0x00016D22 | wait_event
[ 304.802565] iwlwifi 0000:03:00.0: 0x00000000 | l2p_control
[ 304.802568] iwlwifi 0000:03:00.0: 0x00018034 | l2p_duration
[ 304.802572] iwlwifi 0000:03:00.0: 0x0000003F | l2p_mhvalid
[ 304.802575] iwlwifi 0000:03:00.0: 0x00CB0000 | l2p_addr_match
[ 304.802579] iwlwifi 0000:03:00.0: 0x00000009 | lmpm_pmg_sel
[ 304.802582] iwlwifi 0000:03:00.0: 0x00000000 | timestamp
[ 304.802585] iwlwifi 0000:03:00.0: 0x00004084 | flow_handler
[ 304.802650] iwlwifi 0000:03:00.0: Start IWL Error Log Dump:
[ 304.802656] iwlwifi 0000:03:00.0: Status: 0x00000040, count: 7
[ 304.802662] iwlwifi 0000:03:00.0: 0x20000070 | NMI_INTERRUPT_LMAC_FATAL
[ 304.802667] iwlwifi 0000:03:00.0: 0x00000000 | umac branchlink1
[ 304.802672] iwlwifi 0000:03:00.0: 0xC008CC3C | umac branchlink2
[ 304.802677] iwlwifi 0000:03:00.0: 0x8048D0E6 | umac interruptlink1
[ 304.802682] iwlwifi 0000:03:00.0: 0x8048D0E6 | umac interruptlink2
[ 304.802687] iwlwifi 0000:03:00.0: 0x00000400 | umac data1
[ 304.802692] iwlwifi 0000:03:00.0: 0x8048D0E6 | umac data2
[ 304.802698] iwlwifi 0000:03:00.0: 0x00000000 | umac data3
[ 304.802703] iwlwifi 0000:03:00.0: 0x00000030 | umac major
[ 304.802707] iwlwifi 0000:03:00.0: 0x4FA0041F | umac minor
[ 304.802712] iwlwifi 0000:03:00.0: 0x00289501 | frame pointer
[ 304.802717] iwlwifi 0000:03:00.0: 0xC0886284 | stack pointer
[ 304.802723] iwlwifi 0000:03:00.0: 0x0035050F | last host cmd
[ 304.802730] iwlwifi 0000:03:00.0: 0x00000000 | isr status reg
[ 304.802768] iwlwifi 0000:03:00.0: Fseq Registers:
[ 304.802787] iwlwifi 0000:03:00.0: 0xE0000101 | FSEQ_ERROR_CODE
[ 304.802809] iwlwifi 0000:03:00.0: 0x00290011 | FSEQ_TOP_INIT_VERSION
[ 304.802834] iwlwifi 0000:03:00.0: 0x80050008 | FSEQ_CNVIO_INIT_VERSION
[ 304.802856] iwlwifi 0000:03:00.0: 0x0000A503 | FSEQ_OTP_VERSION
[ 304.802872] iwlwifi 0000:03:00.0: 0x80000003 | FSEQ_TOP_CONTENT_VERSION
[ 304.802889] iwlwifi 0000:03:00.0: 0x4552414E | FSEQ_ALIVE_TOKEN
[ 304.802906] iwlwifi 0000:03:00.0: 0x00100530 | FSEQ_CNVI_ID
[ 304.802925] iwlwifi 0000:03:00.0: 0x00000532 | FSEQ_CNVR_ID
[ 304.802942] iwlwifi 0000:03:00.0: 0x00100530 | CNVI_AUX_MISC_CHIP
[ 304.802960] iwlwifi 0000:03:00.0: 0x00000532 | CNVR_AUX_MISC_CHIP
[ 304.802980] iwlwifi 0000:03:00.0: 0x05B0905B | CNVR_SCU_SD_REGS_SD_REG_DIG_DCDC_VTRIM
[ 304.803004] iwlwifi 0000:03:00.0: 0x0000025B | CNVR_SCU_SD_REGS_SD_REG_ACTIVE_VDIG_MIRROR
[ 304.803173] iwlwifi 0000:03:00.0: Collecting data: trigger 2 fired.
[ 304.803186] ieee80211 phy0: Hardware restart was requested
[ 304.803255] iwlwifi 0000:03:00.0: FW error in SYNC CMD ADD_STA
[ 304.803265] CPU: 3 PID: 4905 Comm: hostapd Tainted: G OE 5.8.0-050800-generic #202008022230
[ 304.803267] Hardware name: LENOVO 20FWCTO1WW/20FWCTO1WW, BIOS R07ET91W (2.31 ) 12/11/2019
[ 304.803269] Call Trace:
[ 304.803283] dump_stack+0x70/0x8d
[ 304.803318] iwl_trans_pcie_gen2_send_hcmd+0x421/0x430 [iwlwifi]
[ 304.803326] ? wait_woken+0x80/0x80
[ 304.803347] iwl_trans_send_cmd+0x55/0xc0 [iwlwifi]
[ 304.803371] iwl_mvm_send_cmd_status+0x38/0xd0 [iwlmvm]
[ 304.803390] iwl_mvm_send_cmd_pdu_status+0x53/0x70 [iwlmvm]
[ 304.803412] iwl_mvm_sta_send_to_fw+0x1e1/0x330 [iwlmvm]
[ 304.803428] iwl_mvm_mac_sta_state+0x3e1/0x720 [iwlmvm]
[ 304.803469] drv_sta_state+0x91/0x3f0 [mac80211]
[ 304.803501] sta_info_move_state+0x276/0x370 [mac80211]
[ 304.803542] sta_apply_auth_flags.isra.0+0x73/0x140 [mac80211]
[ 304.803579] sta_apply_parameters+0x336/0x490 [mac80211]
[ 304.803611] ieee80211_change_station+0x137/0x2a0 [mac80211]
[ 304.803659] ? nl80211_parse_sta_wme+0x57/0xc0 [cfg80211]
[ 304.803698] nl80211_set_station+0x381/0x450 [cfg80211]
[ 304.803708] genl_family_rcv_msg+0x17b/0x290
[ 304.803714] genl_rcv_msg+0x4c/0xa0
[ 304.803717] ? genl_family_rcv_msg+0x290/0x290
[ 304.803721] netlink_rcv_skb+0x4e/0x110
[ 304.803726] genl_rcv+0x29/0x40
[ 304.803729] netlink_unicast+0x218/0x330
[ 304.803733] netlink_sendmsg+0x233/0x460
[ 304.803741] sock_sendmsg+0x65/0x70
[ 304.803746] ____sys_sendmsg+0x257/0x2a0
[ 304.803752] ? sendmsg_copy_msghdr+0x7e/0xa0
[ 304.803758] ___sys_sendmsg+0x82/0xc0
[ 304.803764] ? ___sys_recvmsg+0xa3/0x130
[ 304.803770] ? __sys_sendto+0x113/0x190
[ 304.803776] ? recalibrate_cpu_khz+0x10/0x10
[ 304.803782] ? ktime_get_ts64+0x4c/0xf0
[ 304.803789] ? __cgroup_bpf_run_filter_setsockopt+0xb0/0x2d0
[ 304.803795] __sys_sendmsg+0x62/0xb0
[ 304.803802] __x64_sys_sendmsg+0x1f/0x30
[ 304.803808] do_syscall_64+0x52/0xc0
[ 304.803815] entry_SYSCALL_64_after_hwframe+0x44/0xa9
[ 304.803819] RIP: 0033:0x7f113d47e5b7
[ 304.803825] Code: 64 89 02 48 c7 c0 ff ff ff ff eb bb 0f 1f 80 00 00 00 00 f3 0f 1e fa 64 8b 04 25 18 00 00 00 85 c0 75 10 b8 2e 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 51 c3 48 83 ec 28 89 54 24 1c 48 89 74 24 10
[ 304.803828] RSP: 002b:00007fff67b087e8 EFLAGS: 00000246 ORIG_RAX: 000000000000002e
[ 304.803832] RAX: ffffffffffffffda RBX: 0000555aa4b7b1d0 RCX: 00007f113d47e5b7
[ 304.803834] RDX: 0000000000000000 RSI: 00007fff67b08820 RDI: 0000000000000005
[ 304.803836] RBP: 0000555aa4b82340 R08: 0000000000000004 R09: 00007f113d547200
[ 304.803838] R10: 00007fff67b08904 R11: 0000000000000246 R12: 0000555aa4b79690
[ 304.803840] R13: 00007fff67b08820 R14: 0000000000000000 R15: 0000000000000000
[ 304.804060] iwlwifi 0000:03:00.0: Failed to trigger RX queues sync (-5)
[ 305.409905] iwlwifi 0000:03:00.0: Applying debug destination EXTERNAL_DRAM
[ 305.581559] iwlwifi 0000:03:00.0: FW already configured (0) - re-configuring
[ 312.059962] iwlwifi 0000:03:00.0: Microcode SW error detected. Restarting 0x0.
[ 312.060084] iwlwifi 0000:03:00.0: Start IWL Error Log Dump:
[ 312.060089] iwlwifi 0000:03:00.0: Status: 0x00000040, count: 6
[ 312.060093] iwlwifi 0000:03:00.0: Loaded firmware version: 48.4fa0041f.0 cc-a0-48.ucode
[ 312.060099] iwlwifi 0000:03:00.0: 0x00002078 | ADVANCED_SYSASSERT
[ 312.060103] iwlwifi 0000:03:00.0: 0x00A0A200 | trm_hw_status0
[ 312.060106] iwlwifi 0000:03:00.0: 0x00000000 | trm_hw_status1
[ 312.060110] iwlwifi 0000:03:00.0: 0x004F8E3C | branchlink2
[ 312.060113] iwlwifi 0000:03:00.0: 0x004E4FF4 | interruptlink1
[ 312.060116] iwlwifi 0000:03:00.0: 0x004E4FF4 | interruptlink2
[ 312.060120] iwlwifi 0000:03:00.0: 0x07000101 | data1
[ 312.060124] iwlwifi 0000:03:00.0: 0x48308403 | data2
[ 312.060127] iwlwifi 0000:03:00.0: 0x00000005 | data3
[ 312.060130] iwlwifi 0000:03:00.0: 0x00000000 | beacon time
[ 312.060134] iwlwifi 0000:03:00.0: 0x00650DDC | tsf low
[ 312.060137] iwlwifi 0000:03:00.0: 0x00000000 | tsf hi
[ 312.060140] iwlwifi 0000:03:00.0: 0x00000000 | time gp1
[ 312.060144] iwlwifi 0000:03:00.0: 0x00657714 | time gp2
[ 312.060147] iwlwifi 0000:03:00.0: 0x00000001 | uCode revision type
[ 312.060151] iwlwifi 0000:03:00.0: 0x00000030 | uCode version major
[ 312.060154] iwlwifi 0000:03:00.0: 0x4FA0041F | uCode version minor
[ 312.060158] iwlwifi 0000:03:00.0: 0x00000340 | hw version
[ 312.060161] iwlwifi 0000:03:00.0: 0x00489000 | board version
[ 312.060165] iwlwifi 0000:03:00.0: 0x8014FC09 | hcmd
[ 312.060168] iwlwifi 0000:03:00.0: 0x24020000 | isr0
[ 312.060172] iwlwifi 0000:03:00.0: 0x61000000 | isr1
[ 312.060175] iwlwifi 0000:03:00.0: 0x18F00002 | isr2
[ 312.060178] iwlwifi 0000:03:00.0: 0x00C1FFCC | isr3
[ 312.060181] iwlwifi 0000:03:00.0: 0x00000000 | isr4
[ 312.060185] iwlwifi 0000:03:00.0: 0x0405001C | last cmd Id
[ 312.060188] iwlwifi 0000:03:00.0: 0x00016D22 | wait_event
[ 312.060192] iwlwifi 0000:03:00.0: 0x00000000 | l2p_control
[ 312.060195] iwlwifi 0000:03:00.0: 0x00018034 | l2p_duration
[ 312.060199] iwlwifi 0000:03:00.0: 0x0000003F | l2p_mhvalid
[ 312.060202] iwlwifi 0000:03:00.0: 0x00CB0000 | l2p_addr_match
[ 312.060206] iwlwifi 0000:03:00.0: 0x00000009 | lmpm_pmg_sel
[ 312.060209] iwlwifi 0000:03:00.0: 0x00000000 | timestamp
[ 312.060212] iwlwifi 0000:03:00.0: 0x00004080 | flow_handler
[ 312.060280] iwlwifi 0000:03:00.0: Start IWL Error Log Dump:
[ 312.060284] iwlwifi 0000:03:00.0: Status: 0x00000040, count: 7
[ 312.060288] iwlwifi 0000:03:00.0: 0x20000070 | NMI_INTERRUPT_LMAC_FATAL
[ 312.060292] iwlwifi 0000:03:00.0: 0x00000000 | umac branchlink1
[ 312.060295] iwlwifi 0000:03:00.0: 0xC008CC3C | umac branchlink2
[ 312.060299] iwlwifi 0000:03:00.0: 0x8048D0E6 | umac interruptlink1
[ 312.060302] iwlwifi 0000:03:00.0: 0x8048D0E6 | umac interruptlink2
[ 312.060305] iwlwifi 0000:03:00.0: 0x00000400 | umac data1
[ 312.060309] iwlwifi 0000:03:00.0: 0x8048D0E6 | umac data2
[ 312.060312] iwlwifi 0000:03:00.0: 0x00000000 | umac data3
[ 312.060315] iwlwifi 0000:03:00.0: 0x00000030 | umac major
[ 312.060319] iwlwifi 0000:03:00.0: 0x4FA0041F | umac minor
[ 312.060322] iwlwifi 0000:03:00.0: 0x00657724 | frame pointer
[ 312.060325] iwlwifi 0000:03:00.0: 0xC0886284 | stack pointer
[ 312.060329] iwlwifi 0000:03:00.0: 0x0035050F | last host cmd
[ 312.060332] iwlwifi 0000:03:00.0: 0x00000000 | isr status reg
[ 312.060369] iwlwifi 0000:03:00.0: Fseq Registers:
[ 312.060385] iwlwifi 0000:03:00.0: 0xE0000101 | FSEQ_ERROR_CODE
[ 312.060401] iwlwifi 0000:03:00.0: 0x00290011 | FSEQ_TOP_INIT_VERSION
[ 312.060417] iwlwifi 0000:03:00.0: 0x80050008 | FSEQ_CNVIO_INIT_VERSION
[ 312.060433] iwlwifi 0000:03:00.0: 0x0000A503 | FSEQ_OTP_VERSION
[ 312.060449] iwlwifi 0000:03:00.0: 0x80000003 | FSEQ_TOP_CONTENT_VERSION
[ 312.060465] iwlwifi 0000:03:00.0: 0x4552414E | FSEQ_ALIVE_TOKEN
[ 312.060481] iwlwifi 0000:03:00.0: 0x00100530 | FSEQ_CNVI_ID
[ 312.060498] iwlwifi 0000:03:00.0: 0x00000532 | FSEQ_CNVR_ID
[ 312.060513] iwlwifi 0000:03:00.0: 0x00100530 | CNVI_AUX_MISC_CHIP
[ 312.060528] iwlwifi 0000:03:00.0: 0x00000532 | CNVR_AUX_MISC_CHIP
[ 312.060544] iwlwifi 0000:03:00.0: 0x05B0905B | CNVR_SCU_SD_REGS_SD_REG_DIG_DCDC_VTRIM
[ 312.060560] iwlwifi 0000:03:00.0: 0x0000025B | CNVR_SCU_SD_REGS_SD_REG_ACTIVE_VDIG_MIRROR
[ 312.060723] iwlwifi 0000:03:00.0: Collecting data: trigger 2 fired.
[ 312.060734] ieee80211 phy0: Hardware restart was requested
[ 312.060768] iwlwifi 0000:03:00.0: FW error in SYNC CMD ADD_STA
[ 312.060779] CPU: 3 PID: 4905 Comm: hostapd Tainted: G OE 5.8.0-050800-generic #202008022230
[ 312.060781] Hardware name: LENOVO 20FWCTO1WW/20FWCTO1WW, BIOS R07ET91W (2.31 ) 12/11/2019
[ 312.060783] Call Trace:
[ 312.060796] dump_stack+0x70/0x8d
[ 312.060836] iwl_trans_pcie_gen2_send_hcmd+0x421/0x430 [iwlwifi]
[ 312.060845] ? wait_woken+0x80/0x80
[ 312.060866] iwl_trans_send_cmd+0x55/0xc0 [iwlwifi]
[ 312.060890] iwl_mvm_send_cmd_status+0x38/0xd0 [iwlmvm]
[ 312.060911] iwl_mvm_send_cmd_pdu_status+0x53/0x70 [iwlmvm]
[ 312.060941] iwl_mvm_sta_send_to_fw+0x1e1/0x330 [iwlmvm]
[ 312.060963] iwl_mvm_mac_sta_state+0x3e1/0x720 [iwlmvm]
[ 312.061004] drv_sta_state+0x91/0x3f0 [mac80211]
[ 312.061037] sta_info_move_state+0x276/0x370 [mac80211]
[ 312.061079] sta_apply_auth_flags.isra.0+0x73/0x140 [mac80211]
[ 312.061118] sta_apply_parameters+0x336/0x490 [mac80211]
[ 312.061152] ieee80211_change_station+0x137/0x2a0 [mac80211]
[ 312.061203] ? nl80211_parse_sta_wme+0x57/0xc0 [cfg80211]
[ 312.061244] nl80211_set_station+0x381/0x450 [cfg80211]
[ 312.061259] genl_family_rcv_msg+0x17b/0x290
[ 312.061268] genl_rcv_msg+0x4c/0xa0
[ 312.061277] ? genl_family_rcv_msg+0x290/0x290
[ 312.061285] netlink_rcv_skb+0x4e/0x110
[ 312.061293] genl_rcv+0x29/0x40
[ 312.061301] netlink_unicast+0x218/0x330
[ 312.061309] netlink_sendmsg+0x233/0x460
[ 312.061321] sock_sendmsg+0x65/0x70
[ 312.061330] ____sys_sendmsg+0x257/0x2a0
[ 312.061341] ? sendmsg_copy_msghdr+0x7e/0xa0
[ 312.061351] ___sys_sendmsg+0x82/0xc0
[ 312.061361] ? ___sys_recvmsg+0xa3/0x130
[ 312.061371] ? __sys_sendto+0x113/0x190
[ 312.061380] ? recalibrate_cpu_khz+0x10/0x10
[ 312.061388] ? ktime_get_ts64+0x4c/0xf0
[ 312.061400] ? __cgroup_bpf_run_filter_setsockopt+0xb0/0x2d0
[ 312.061410] __sys_sendmsg+0x62/0xb0
[ 312.061421] __x64_sys_sendmsg+0x1f/0x30
[ 312.061431] do_syscall_64+0x52/0xc0
[ 312.061442] entry_SYSCALL_64_after_hwframe+0x44/0xa9
[ 312.061451] RIP: 0033:0x7f113d47e5b7
[ 312.061461] Code: 64 89 02 48 c7 c0 ff ff ff ff eb bb 0f 1f 80 00 00 00 00 f3 0f 1e fa 64 8b 04 25 18 00 00 00 85 c0 75 10 b8 2e 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 51 c3 48 83 ec 28 89 54 24 1c 48 89 74 24 10
[ 312.061468] RSP: 002b:00007fff67b087e8 EFLAGS: 00000246 ORIG_RAX: 000000000000002e
[ 312.061478] RAX: ffffffffffffffda RBX: 0000555aa4b7b1d0 RCX: 00007f113d47e5b7
[ 312.061483] RDX: 0000000000000000 RSI: 00007fff67b08820 RDI: 0000000000000005
[ 312.061489] RBP: 0000555aa4b81440 R08: 0000000000000004 R09: 00007f113d547200
[ 312.061494] R10: 00007fff67b08904 R11: 0000000000000246 R12: 0000555aa4b79690
[ 312.061500] R13: 00007fff67b08820 R14: 0000000000000000 R15: 0000000000000000
[ 312.636904] iwlwifi 0000:03:00.0: Failed to trigger RX queues sync (-5)
[ 312.663222] iwlwifi 0000:03:00.0: Applying debug destination EXTERNAL_DRAM
[ 312.830868] iwlwifi 0000:03:00.0: FW already configured (0) - re-configuring
[ 324.448802] iwlwifi 0000:03:00.0: Microcode SW error detected. Restarting 0x0.
[ 324.448966] iwlwifi 0000:03:00.0: Start IWL Error Log Dump:
[ 324.448976] iwlwifi 0000:03:00.0: Status: 0x00000040, count: 6
[ 324.448981] iwlwifi 0000:03:00.0: Loaded firmware version: 48.4fa0041f.0 cc-a0-48.ucode
[ 324.448989] iwlwifi 0000:03:00.0: 0x00002078 | ADVANCED_SYSASSERT
[ 324.448999] iwlwifi 0000:03:00.0: 0x00A0A200 | trm_hw_status0
[ 324.449003] iwlwifi 0000:03:00.0: 0x00000000 | trm_hw_status1
[ 324.449007] iwlwifi 0000:03:00.0: 0x004F8E3C | branchlink2
[ 324.449010] iwlwifi 0000:03:00.0: 0x004E4FF4 | interruptlink1
[ 324.449016] iwlwifi 0000:03:00.0: 0x004E4FF4 | interruptlink2
[ 324.449029] iwlwifi 0000:03:00.0: 0x07000101 | data1
[ 324.449036] iwlwifi 0000:03:00.0: 0x48308403 | data2
[ 324.449040] iwlwifi 0000:03:00.0: 0x00000005 | data3
[ 324.449043] iwlwifi 0000:03:00.0: 0x00000000 | beacon time
[ 324.449047] iwlwifi 0000:03:00.0: 0x00B369BB | tsf low
[ 324.449050] iwlwifi 0000:03:00.0: 0x00000000 | tsf hi
[ 324.449054] iwlwifi 0000:03:00.0: 0x00000000 | time gp1
[ 324.449057] iwlwifi 0000:03:00.0: 0x00B3D361 | time gp2
[ 324.449061] iwlwifi 0000:03:00.0: 0x00000001 | uCode revision type
[ 324.449065] iwlwifi 0000:03:00.0: 0x00000030 | uCode version major
[ 324.449071] iwlwifi 0000:03:00.0: 0x4FA0041F | uCode version minor
[ 324.449083] iwlwifi 0000:03:00.0: 0x00000340 | hw version
[ 324.449094] iwlwifi 0000:03:00.0: 0x00489000 | board version
[ 324.449107] iwlwifi 0000:03:00.0: 0x8089FC09 | hcmd
[ 324.449114] iwlwifi 0000:03:00.0: 0x24020000 | isr0
[ 324.449118] iwlwifi 0000:03:00.0: 0x61000000 | isr1
[ 324.449122] iwlwifi 0000:03:00.0: 0x18F00002 | isr2
[ 324.449125] iwlwifi 0000:03:00.0: 0x00C1FFCC | isr3
[ 324.449129] iwlwifi 0000:03:00.0: 0x00000000 | isr4
[ 324.449133] iwlwifi 0000:03:00.0: 0x0409001C | last cmd Id
[ 324.449137] iwlwifi 0000:03:00.0: 0x00016D22 | wait_event
[ 324.449140] iwlwifi 0000:03:00.0: 0x00000000 | l2p_control
[ 324.449144] iwlwifi 0000:03:00.0: 0x00018034 | l2p_duration
[ 324.449149] iwlwifi 0000:03:00.0: 0x0000003F | l2p_mhvalid
[ 324.449155] iwlwifi 0000:03:00.0: 0x00CB0000 | l2p_addr_match
[ 324.449162] iwlwifi 0000:03:00.0: 0x00000009 | lmpm_pmg_sel
[ 324.449168] iwlwifi 0000:03:00.0: 0x00000000 | timestamp
[ 324.449173] iwlwifi 0000:03:00.0: 0x00004890 | flow_handler
[ 324.449252] iwlwifi 0000:03:00.0: Start IWL Error Log Dump:
[ 324.449258] iwlwifi 0000:03:00.0: Status: 0x00000040, count: 7
[ 324.449269] iwlwifi 0000:03:00.0: 0x20000070 | NMI_INTERRUPT_LMAC_FATAL
[ 324.449278] iwlwifi 0000:03:00.0: 0x00000000 | umac branchlink1
[ 324.449288] iwlwifi 0000:03:00.0: 0xC008CC3C | umac branchlink2
[ 324.449297] iwlwifi 0000:03:00.0: 0x8048D0E6 | umac interruptlink1
[ 324.449307] iwlwifi 0000:03:00.0: 0x8048D0E6 | umac interruptlink2
[ 324.449317] iwlwifi 0000:03:00.0: 0x00000400 | umac data1
[ 324.449325] iwlwifi 0000:03:00.0: 0x8048D0E6 | umac data2
[ 324.449330] iwlwifi 0000:03:00.0: 0x00000000 | umac data3
[ 324.449336] iwlwifi 0000:03:00.0: 0x00000030 | umac major
[ 324.449341] iwlwifi 0000:03:00.0: 0x4FA0041F | umac minor
[ 324.449348] iwlwifi 0000:03:00.0: 0x00B3D371 | frame pointer
[ 324.449354] iwlwifi 0000:03:00.0: 0xC0886284 | stack pointer
[ 324.449360] iwlwifi 0000:03:00.0: 0x0035050F | last host cmd
[ 324.449366] iwlwifi 0000:03:00.0: 0x00000000 | isr status reg
[ 324.449405] iwlwifi 0000:03:00.0: Fseq Registers:
[ 324.449430] iwlwifi 0000:03:00.0: 0xE0000101 | FSEQ_ERROR_CODE
[ 324.449454] iwlwifi 0000:03:00.0: 0x00290011 | FSEQ_TOP_INIT_VERSION
[ 324.449487] iwlwifi 0000:03:00.0: 0x80050008 | FSEQ_CNVIO_INIT_VERSION
[ 324.449519] iwlwifi 0000:03:00.0: 0x0000A503 | FSEQ_OTP_VERSION
[ 324.449551] iwlwifi 0000:03:00.0: 0x80000003 | FSEQ_TOP_CONTENT_VERSION
[ 324.449582] iwlwifi 0000:03:00.0: 0x4552414E | FSEQ_ALIVE_TOKEN
[ 324.449614] iwlwifi 0000:03:00.0: 0x00100530 | FSEQ_CNVI_ID
[ 324.449637] iwlwifi 0000:03:00.0: 0x00000532 | FSEQ_CNVR_ID
[ 324.449654] iwlwifi 0000:03:00.0: 0x00100530 | CNVI_AUX_MISC_CHIP
[ 324.449691] iwlwifi 0000:03:00.0: 0x00000532 | CNVR_AUX_MISC_CHIP
[ 324.449722] iwlwifi 0000:03:00.0: 0x05B0905B | CNVR_SCU_SD_REGS_SD_REG_DIG_DCDC_VTRIM
[ 324.449755] iwlwifi 0000:03:00.0: 0x0000025B | CNVR_SCU_SD_REGS_SD_REG_ACTIVE_VDIG_MIRROR
[ 324.449922] iwlwifi 0000:03:00.0: Collecting data: trigger 2 fired.
[ 324.449933] ieee80211 phy0: Hardware restart was requested
[ 324.450022] iwlwifi 0000:03:00.0: FW error in SYNC CMD ADD_STA
[ 324.450032] CPU: 3 PID: 4905 Comm: hostapd Tainted: G OE 5.8.0-050800-generic #202008022230
[ 324.450034] Hardware name: LENOVO 20FWCTO1WW/20FWCTO1WW, BIOS R07ET91W (2.31 ) 12/11/2019
[ 324.450036] Call Trace:
[ 324.450050] dump_stack+0x70/0x8d
[ 324.450084] iwl_trans_pcie_gen2_send_hcmd+0x421/0x430 [iwlwifi]
[ 324.450092] ? wait_woken+0x80/0x80
[ 324.450113] iwl_trans_send_cmd+0x55/0xc0 [iwlwifi]
[ 324.450137] iwl_mvm_send_cmd_status+0x38/0xd0 [iwlmvm]
[ 324.450157] iwl_mvm_send_cmd_pdu_status+0x53/0x70 [iwlmvm]
[ 324.450180] iwl_mvm_sta_send_to_fw+0x1e1/0x330 [iwlmvm]
[ 324.450196] iwl_mvm_mac_sta_state+0x3e1/0x720 [iwlmvm]
[ 324.450239] drv_sta_state+0x91/0x3f0 [mac80211]
[ 324.450271] sta_info_move_state+0x276/0x370 [mac80211]
[ 324.450312] sta_apply_auth_flags.isra.0+0x73/0x140 [mac80211]
[ 324.450350] sta_apply_parameters+0x336/0x490 [mac80211]
[ 324.450382] ieee80211_change_station+0x137/0x2a0 [mac80211]
[ 324.450430] ? nl80211_parse_sta_wme+0x57/0xc0 [cfg80211]
[ 324.450470] nl80211_set_station+0x381/0x450 [cfg80211]
[ 324.450483] genl_family_rcv_msg+0x17b/0x290
[ 324.450489] genl_rcv_msg+0x4c/0xa0
[ 324.450493] ? genl_family_rcv_msg+0x290/0x290
[ 324.450497] netlink_rcv_skb+0x4e/0x110
[ 324.450501] genl_rcv+0x29/0x40
[ 324.450505] netlink_unicast+0x218/0x330
[ 324.450509] netlink_sendmsg+0x233/0x460
[ 324.450516] sock_sendmsg+0x65/0x70
[ 324.450521] ____sys_sendmsg+0x257/0x2a0
[ 324.450527] ? sendmsg_copy_msghdr+0x7e/0xa0
[ 324.450534] ___sys_sendmsg+0x82/0xc0
[ 324.450540] ? ___sys_recvmsg+0xa3/0x130
[ 324.450546] ? __sys_sendto+0x113/0x190
[ 324.450552] ? recalibrate_cpu_khz+0x10/0x10
[ 324.450557] ? ktime_get_ts64+0x4c/0xf0
[ 324.450565] ? __cgroup_bpf_run_filter_setsockopt+0xb0/0x2d0
[ 324.450571] __sys_sendmsg+0x62/0xb0
[ 324.450578] __x64_sys_sendmsg+0x1f/0x30
[ 324.450583] do_syscall_64+0x52/0xc0
[ 324.450590] entry_SYSCALL_64_after_hwframe+0x44/0xa9
[ 324.450595] RIP: 0033:0x7f113d47e5b7
[ 324.450600] Code: 64 89 02 48 c7 c0 ff ff ff ff eb bb 0f 1f 80 00 00 00 00 f3 0f 1e fa 64 8b 04 25 18 00 00 00 85 c0 75 10 b8 2e 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 51 c3 48 83 ec 28 89 54 24 1c 48 89 74 24 10
[ 324.450603] RSP: 002b:00007fff67b087e8 EFLAGS: 00000246 ORIG_RAX: 000000000000002e
[ 324.450608] RAX: ffffffffffffffda RBX: 0000555aa4b7b1d0 RCX: 00007f113d47e5b7
[ 324.450610] RDX: 0000000000000000 RSI: 00007fff67b08820 RDI: 0000000000000005
[ 324.450612] RBP: 0000555aa4b849e0 R08: 0000000000000004 R09: 00007f113d5471e0
[ 324.450614] R10: 00007fff67b08904 R11: 0000000000000246 R12: 0000555aa4b79690
[ 324.450615] R13: 00007fff67b08820 R14: 0000000000000000 R15: 0000000000000000
[ 325.060058] iwlwifi 0000:03:00.0: Applying debug destination EXTERNAL_DRAM
[ 325.229883] iwlwifi 0000:03:00.0: FW already configured (0) - re-configuring
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: Configuring WiFi6 in hostapd
[not found] ` <CAD_iCC8qJ_Xaa5yjkdzapGCtJsAt2VbYzTfgpUDCeT7RpyrBjw@mail.gmail.com>
@ 2020-10-15 5:21 ` Coelho, Luciano
0 siblings, 0 replies; 9+ messages in thread
From: Coelho, Luciano @ 2020-10-15 5:21 UTC (permalink / raw)
To: sugandhgowda, Damary, Guy
Cc: linux-wireless, johannes, Grumbach, Emmanuel, Cedric.Izoard,
chaitanya.mgit, Hostap
On Wed, 2020-09-30 at 21:59 +0200, Sugandh Huthanahally Mohan wrote:
> On Wed, 2020-09-23 at 11:16 +0300, Luciano Coelho wrote:
> > On Thu, 2020-09-17 at 03:01 +0530, Krishna Chaitanya wrote:
> > > > On Sat, Sep 12, 2020 at 12:56 AM Krishna Chaitanya
> > > > <chaitanya.mgit at gmail.com> wrote:
> > > > >On Fri, Sep 11, 2020 at 10:41 PM Johannes Berg
> > > > > <johannes at sipsolutions.net> wrote:
> > > > > >On Fri, 2020-09-11 at 20:37 +0530, Krishna Chaitanya wrote:
> > > > > >
> > > > > > > > [ 228.315290] iwlwifi 0000:03:00.0: 0x00002078 | ADVANCED_SYSASSERT
> > > > > > > > [ 228.315294] iwlwifi 0000:03:00.0: 0x00A0A200 | trm_hw_status0
> > > > > > > > [ 228.315297] iwlwifi 0000:03:00.0: 0x00000000 | trm_hw_status1
> > > > > > > > [ 228.315300] iwlwifi 0000:03:00.0: 0x004F8E3C | branchlink2
> > > > > > > > [ 228.315303] iwlwifi 0000:03:00.0: 0x004E4FF4 | interruptlink1
> > > > > > > > [ 228.315307] iwlwifi 0000:03:00.0: 0x004E4FF4 | interruptlink2
> > > > > > > > [ 228.315310] iwlwifi 0000:03:00.0: 0x07000101 | data1
> > > > > > > > [ 228.315313] iwlwifi 0000:03:00.0: 0x48308403 | data2
> > > > > > > > [ 228.315316] iwlwifi 0000:03:00.0: 0x00000005 | data3
> > > > > >
> > > > > > This means that we got an invalid TX rate, notably an HE rate was
> > > > > > requested/configured on a MAC configuration that didn't have HE.
> > > > > >
> > > > > > I think I saw some patches in this area (configuring the MAC to be HE)
> > > > > > fly by internally recently, but not sure... Luca probably knows.
> > > > > Ah okay. This was reported on 5.4 kernel, do you think is it worth
> > > > > trying on latest iwlwifi-next tree? Or as you are referring to the internal tree
> > > > > the issue is present in the latest as well?
> > > > Hi Luca,
> > > >
> > > > Can you please take a look? Any help is appreciated.
> > >
> > > Hi,
> > >
> > > There have been some new patches in this area, but after a quick look I
> > > didn't find anything specific that jumps out. I'll take a closer look
> > > and let you know if I find anything.
>
> > In the meantime, you could try our public backport-iwlwifi tree, where
> > most of the internal tree is published:
> >
> > https://git.kernel.org/pub/scm/linux/kernel/git/iwlwifi/backport-iwlwifi.git/
> >
> > This is an out-of-tree driver, based on the linux-backports project.
> > You could try the core56 branch, for instance, or even master and
> > check if the problem is still there. If not, we can try to look for
> > the patch that fixes it and push it to stable.
>
> > --
> > Cheers,
> > Luca.
>
> Hello Luca,
>
> I used public backport iwlwifi tree with core56 branch as you suggested.
> I am still observing the crash which I reported earlier.
>
> Also I upgraded my linux kernel to 5.8 and tried , but still observing
> the same crash.
> I am attaching the dmesg.
>
> Also when I run hostapd_cli (see below for output )on my AP, I could
> see HE flag.
>
> >all_sta
>
> 8c:c6:81:69:86:65
> flags=[AUTH][SHORT_PREAMBLE][WMM][HT][HE]
> aid=1
> capability=0x431
> listen_interval=10
> supported_rates=02 04 0b 16 0c 12 18 24 30 48 60 6c
> timeout_next=NULLFUNC POLL
> dot11RSNAStatsSTAAddress=8c:c6:81:69:86:65
> dot11RSNAStatsVersion=1
> dot11RSNAStatsSelectedPairwiseCipher=00-0f-ac-4
> dot11RSNAStatsTKIPLocalMICFailures=0
> dot11RSNAStatsTKIPRemoteMICFailures=0
> wpa=2
> AKMSuiteSelector=00-0f-ac-2
> hostapdWPAPTKState=0
> hostapdWPAPTKGroupState=0
> supp_op_classes=51515354737475767778797a7b7c7d7e7f
> ht_caps_info=0x19e7
> ext_capab=04004000010000400020
>
Hi Sugandh,
I'm CCing Guy here. He can help you get some dedicated support on this
issue.
--
Cheers,
Luca.
^ permalink raw reply [flat|nested] 9+ messages in thread
end of thread, other threads:[~2020-10-15 5:22 UTC | newest]
Thread overview: 9+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
[not found] <CAD_iCC8EyWV8bLdJ+VsRdMHOa6ccOOOOUMM6nMwDk16LtMppcg@mail.gmail.com>
[not found] ` <PR2PR08MB464983615CFB2AF2B3BCD644D12E0@PR2PR08MB4649.eurprd08.prod.outlook.com>
[not found] ` <CAD_iCC-=rvC6mC8pOKNKqrrWQv2wt9BXVMQB2DR1QKcGp_KbiQ@mail.gmail.com>
[not found] ` <CABPxzYJ=vJB4pnCC__G6Luhdp_m51Z_nKq80HFxEfN6cdsKQbw@mail.gmail.com>
[not found] ` <CAD_iCC-koZwPCew4+n4nk8Ou_jWC2BxxcSDy_rf9KnO4Q=MO=g@mail.gmail.com>
[not found] ` <CABPxzY+tfkjKETjdKJE7AjY6ELFfsLw4utVWOfXwxuV4C+RK8w@mail.gmail.com>
[not found] ` <CAD_iCC-=9XU-DbfUorUtSRzCOEW=gr83T8ZSMvJn_xFgoMWvew@mail.gmail.com>
[not found] ` <CABPxzYJmL7x1Hfx9Yf+4XT6xngWNmYC9ZGGvDYqLo7y2bNtCow@mail.gmail.com>
[not found] ` <CAD_iCC9Vu55FG5vHSWF=H8v-ZZKQoyin8B-1zBtaJ+2MeJqCjg@mail.gmail.com>
[not found] ` <CABPxzYKVK3OK6nKMrLrBfdy-Yz1v_bbyhHHLCkxnFzWtFBSGaA@mail.gmail.com>
[not found] ` <CAD_iCC8XDNXfDmghhXyK8auFg5WinqaACpbpbiZ4g0toaDoeiw@mail.gmail.com>
[not found] ` <CABPxzYK-HN-Q3wREn+6qAkiHAnkuyqz-g6m9XpUtaMd8ckHQPg@mail.gmail.com>
[not found] ` <CAD_iCC-LMnDeL-e-i2GPYe9fRruWxkKvHEsNGDERv2j8eN1YFw@mail.gmail.com>
[not found] ` <CABPxzYJVwjPGrHitstWkgiL+kEB9AeTMy_e5nu7FNXVv4ZNk-A@mail.gmail.com>
[not found] ` <CAD_iCC_1TV_wQK+xOWk48eaJhWo82CZgTL-g4jg7tOdVxvqEZw@mail.gmail.com>
[not found] ` <CABPxzY+2OO6nptyE+oH+COLe3pVgKhji=H1trP7m_bcpVqEe7Q@mail.gmail.com>
[not found] ` <CAD_iCC-x9J4UB5aVR85WNi4OwaXQiU28+4B1AD176zDu8DBhwQ@mail.gmail.com>
[not found] ` <CABPxzY+oy=p4QLHfyVMprigHOpTJEJGsJ-Bsti5b9Ly=eDy+cQ@mail.gmail.com>
[not found] ` <CAD_iCC-mCo58fs1v+bqyB=NRXkQDTa20R=NGe+SwTP2s7NPfOA@mail.gmail.com>
[not found] ` <CABPxzYKckJ94+96YsTY4Y7D7_z-Pk=b+T1tvu5BzaoVjVi0apw@mail.gmail.com>
[not found] ` <CAD_iCC8StVW7Yh9f8fm2Da7LcN6LQzR=ssp+1E8-=YYCM-5tOQ@mail.gmail.com>
2020-09-11 15:07 ` Configuring WiFi6 in hostapd Krishna Chaitanya
2020-09-11 17:10 ` Johannes Berg
2020-09-11 19:26 ` Krishna Chaitanya
2020-09-16 21:31 ` Krishna Chaitanya
2020-09-23 8:16 ` Coelho, Luciano
2020-09-23 8:36 ` Coelho, Luciano
2020-09-23 17:40 ` Ben Greear
[not found] ` <CAD_iCC_iVN8HgCM=g+8MrLJVAoApNXtkRgEUgPZCs8_+DiJTyA@mail.gmail.com>
2020-09-30 15:41 ` Fwd: " Sugandh Huthanahally Mohan
[not found] ` <CAD_iCC8qJ_Xaa5yjkdzapGCtJsAt2VbYzTfgpUDCeT7RpyrBjw@mail.gmail.com>
2020-10-15 5:21 ` Coelho, Luciano
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).