* Reporting a bug for QCA6174 802.11ac
@ 2017-03-20 15:31 Guilherme Íscaro
2017-03-21 18:35 ` Ryan Hsu
0 siblings, 1 reply; 12+ messages in thread
From: Guilherme Íscaro @ 2017-03-20 15:31 UTC (permalink / raw)
To: ath10k
[-- Attachment #1: Type: text/plain, Size: 696 bytes --]
Hello everyone, I would like to report a bug for QCA6174.
I use WiFi everyday, but from time to time I lose my connection. This
might be related to a firmware problem, because after I lose my
connection the firmware keeps flooding dmesg about problems.
I have this problem since I bought my laptop (which was last year)
and I do regular updates in my system.
P.S: dmest output attached.
My system:
Dist: Arch Linux.
Kernel: 4.10.3-1
Linux-firmware version: 20170309.695f2d6-1 (commit 695f2d6d82173f4e...
from linux-firmware)
Board: 02:00.0 Network controller: Qualcomm Atheros QCA6174 802.11ac
Wireless Network Adapter (rev 32)
Please, let me know if I should provide more info.
Thanks.
[-- Attachment #2: dmesg-qca-problem --]
[-- Type: application/octet-stream, Size: 18554 bytes --]
[ 2535.699889] ath10k_pci 0000:02:00.0: failed to wake target for read32 at 0x0003a028: -110
[ 2535.779081] ath10k_pci 0000:02:00.0: failed to wake target for write32 of 0x00001ee1 at 0x0003543c: -110
[ 2536.591254] ath10k_pci 0000:02:00.0: failed to wake target for read32 at 0x0003a028: -110
[ 2542.608446] ath10k_pci 0000:02:00.0: failed to wake target for write32 of 0x00001ee3 at 0x0003543c: -110
[ 2545.502193] ath10k_pci 0000:02:00.0: failed to wake target for write32 of 0x00001ee5 at 0x0003543c: -110
[ 2545.536956] ath10k_pci 0000:02:00.0: failed to wake target for write32 of 0x00001ee7 at 0x0003543c: -110
[ 2545.571692] ath10k_pci 0000:02:00.0: failed to wake target for write32 of 0x00001ee9 at 0x0003543c: -110
[ 2547.706056] ath10k_pci 0000:02:00.0: failed to wake target for write32 of 0x00001eeb at 0x0003543c: -110
[ 2547.740694] ath10k_pci 0000:02:00.0: failed to wake target for write32 of 0x00001eed at 0x0003543c: -110
[ 2547.775294] ath10k_pci 0000:02:00.0: failed to wake target for write32 of 0x00001eef at 0x0003543c: -110
[ 2547.809913] ath10k_pci 0000:02:00.0: failed to wake target for write32 of 0x00001ef1 at 0x0003543c: -110
[ 2550.318331] ath10k_pci 0000:02:00.0: failed to wake target for write32 of 0x00001ef3 at 0x0003543c: -110
[ 2550.506743] ath10k_pci 0000:02:00.0: failed to wake target for write32 of 0x00001ef5 at 0x0003543c: -110
[ 2550.540546] ath10k_pci 0000:02:00.0: failed to wake target for write32 of 0x00001ef7 at 0x0003543c: -110
[ 2552.740261] ath10k_pci 0000:02:00.0: failed to wake target for write32 of 0x00001ef9 at 0x0003543c: -110
[ 2552.775083] ath10k_pci 0000:02:00.0: failed to wake target for write32 of 0x00001efb at 0x0003543c: -110
[ 2552.817356] ath10k_pci 0000:02:00.0: failed to wake target for write32 of 0x00001efd at 0x0003543c: -110
[ 2555.579492] ath10k_pci 0000:02:00.0: failed to wake target for write32 of 0x00001eff at 0x0003543c: -110
[ 2555.613582] ath10k_pci 0000:02:00.0: failed to wake target for write32 of 0x00001f01 at 0x0003543c: -110
[ 2557.815099] ath10k_pci 0000:02:00.0: failed to wake target for write32 of 0x00001f03 at 0x0003543c: -110
[ 2557.850039] ath10k_pci 0000:02:00.0: failed to wake target for write32 of 0x00001f05 at 0x0003543c: -110
[ 2557.883883] ath10k_pci 0000:02:00.0: failed to wake target for write32 of 0x00001f07 at 0x0003543c: -110
[ 2559.086298] ath10k_pci 0000:02:00.0: failed to wake target for write32 of 0x00001f09 at 0x0003543c: -110
[ 2559.300345] ath10k_pci 0000:02:00.0: failed to wake target for write32 of 0x00001f0b at 0x0003543c: -110
[ 2560.335488] ath10k_pci 0000:02:00.0: failed to wake target for write32 of 0x00001f0d at 0x0003543c: -110
[ 2560.652182] ath10k_pci 0000:02:00.0: failed to wake target for write32 of 0x00001f0f at 0x0003543c: -110
[ 2560.686410] ath10k_pci 0000:02:00.0: failed to wake target for write32 of 0x00001f11 at 0x0003543c: -110
[ 2561.369618] ath10k_pci 0000:02:00.0: failed to wake target for write32 of 0x00001f13 at 0x0003543c: -110
[ 2562.889874] ath10k_pci 0000:02:00.0: failed to wake target for write32 of 0x00001f15 at 0x0003543c: -110
[ 2562.924638] ath10k_pci 0000:02:00.0: failed to wake target for write32 of 0x00001f17 at 0x0003543c: -110
[ 2562.959448] ath10k_pci 0000:02:00.0: failed to wake target for write32 of 0x00001f19 at 0x0003543c: -110
[ 2565.723854] ath10k_pci 0000:02:00.0: failed to wake target for write32 of 0x00001f1b at 0x0003543c: -110
[ 2565.757578] ath10k_pci 0000:02:00.0: failed to wake target for write32 of 0x00001f1d at 0x0003543c: -110
[ 2566.501475] ath10k_pci 0000:02:00.0: failed to wake target for write32 of 0x00001f1f at 0x0003543c: -110
[ 2566.536238] ath10k_pci 0000:02:00.0: failed to wake target for write32 of 0x00001f21 at 0x0003543c: -110
[ 2566.571060] ath10k_pci 0000:02:00.0: failed to wake target for write32 of 0x00001f23 at 0x0003543c: -110
[ 2567.409383] ath10k_pci 0000:02:00.0: failed to wake target for write32 of 0x00001f25 at 0x0003543c: -110
[ 2567.926898] ath10k_pci 0000:02:00.0: failed to wake target for write32 of 0x00001f27 at 0x0003543c: -110
[ 2567.998321] ath10k_pci 0000:02:00.0: failed to wake target for write32 of 0x00001f29 at 0x0003543c: -110
[ 2568.033206] ath10k_pci 0000:02:00.0: failed to wake target for write32 of 0x00001f2b at 0x0003543c: -110
[ 2568.409114] ath10k_pci 0000:02:00.0: failed to wake target for write32 of 0x00001f2d at 0x0003543c: -110
[ 2569.408197] ath10k_pci 0000:02:00.0: failed to wake target for write32 of 0x00001f2f at 0x0003543c: -110
[ 2570.796905] ath10k_pci 0000:02:00.0: failed to wake target for write32 of 0x00001f31 at 0x0003543c: -110
[ 2570.830701] ath10k_pci 0000:02:00.0: failed to wake target for write32 of 0x00001f33 at 0x0003543c: -110
[ 2571.621701] ath10k_pci 0000:02:00.0: failed to wake target for write32 of 0x00001f35 at 0x0003543c: -110
[ 2571.699545] ath10k_pci 0000:02:00.0: failed to wake target for write32 of 0x00001f37 at 0x0003543c: -110
[ 2571.734322] ath10k_pci 0000:02:00.0: failed to wake target for write32 of 0x00001f39 at 0x0003543c: -110
[ 2572.966035] ath10k_warn: 2 callbacks suppressed
[ 2572.966038] ath10k_pci 0000:02:00.0: failed to wake target for write32 of 0x00001f3f at 0x0003543c: -110
[ 2573.070306] ath10k_pci 0000:02:00.0: failed to wake target for write32 of 0x00001f41 at 0x0003543c: -110
[ 2573.105078] ath10k_pci 0000:02:00.0: failed to wake target for write32 of 0x00001f43 at 0x0003543c: -110
[ 2575.867210] ath10k_pci 0000:02:00.0: failed to wake target for write32 of 0x00001f45 at 0x0003543c: -110
[ 2575.900868] ath10k_pci 0000:02:00.0: failed to wake target for write32 of 0x00001f47 at 0x0003543c: -110
[ 2576.741450] ath10k_pci 0000:02:00.0: failed to wake target for write32 of 0x00001f49 at 0x0003543c: -110
[ 2576.808801] ath10k_pci 0000:02:00.0: failed to wake target for write32 of 0x00001f4b at 0x0003543c: -110
[ 2576.843652] ath10k_pci 0000:02:00.0: failed to wake target for write32 of 0x00001f4d at 0x0003543c: -110
[ 2577.426424] ath10k_pci 0000:02:00.0: failed to wake target for write32 of 0x00001f4f at 0x0003543c: -110
[ 2577.474388] ath10k_pci 0000:02:00.0: failed to wake target for write32 of 0x00001f51 at 0x0003543c: -110
[ 2578.006007] ath10k_warn: 3 callbacks suppressed
[ 2578.006011] ath10k_pci 0000:02:00.0: failed to wake target for write32 of 0x00001f59 at 0x0003543c: -110
[ 2578.144805] ath10k_pci 0000:02:00.0: failed to wake target for write32 of 0x00001f5b at 0x0003543c: -110
[ 2578.179568] ath10k_pci 0000:02:00.0: failed to wake target for write32 of 0x00001f5d at 0x0003543c: -110
[ 2578.448142] ath10k_pci 0000:02:00.0: failed to wake target for write32 of 0x00001f5f at 0x0003543c: -110
[ 2578.768324] ath10k_pci 0000:02:00.0: failed to wake target for write32 of 0x00001f61 at 0x0003543c: -110
[ 2580.157214] ath10k_pci 0000:02:00.0: failed to wake target for write32 of 0x00001f63 at 0x0003543c: -110
[ 2581.168016] ath10k_pci 0000:02:00.0: failed to wake target for write32 of 0x00001f65 at 0x0003543c: -110
[ 2582.181391] ath10k_pci 0000:02:00.0: failed to wake target for write32 of 0x00001f67 at 0x0003543c: -110
[ 2583.215282] ath10k_pci 0000:02:00.0: failed to wake target for write32 of 0x00001f69 at 0x0003543c: -110
[ 2584.234770] ath10k_pci 0000:02:00.0: failed to wake target for write32 of 0x00001f6b at 0x0003543c: -110
[ 2585.248017] ath10k_pci 0000:02:00.0: failed to wake target for write32 of 0x00001f6d at 0x0003543c: -110
[ 2586.884157] ath10k_pci 0000:02:00.0: failed to wake target for write32 of 0x00001f6f at 0x0003543c: -110
[ 2587.887995] ath10k_pci 0000:02:00.0: failed to wake target for write32 of 0x00001f71 at 0x0003543c: -110
[ 2588.901419] ath10k_pci 0000:02:00.0: failed to wake target for write32 of 0x00001f73 at 0x0003543c: -110
[ 2589.086213] ath10k_pci 0000:02:00.0: failed to wake target for write32 of 0x00001f75 at 0x0003543c: -110
[ 2591.371774] ath10k_pci 0000:02:00.0: failed to wake target for write32 of 0x00001f77 at 0x0003543c: -110
[ 2591.406564] ath10k_pci 0000:02:00.0: failed to wake target for write32 of 0x00001f79 at 0x0003543c: -110
[ 2591.923808] ath10k_pci 0000:02:00.0: failed to wake target for write32 of 0x00001f7b at 0x0003543c: -110
[ 2592.926842] ath10k_pci 0000:02:00.0: failed to wake target for write32 of 0x00001f7d at 0x0003543c: -110
[ 2593.941397] ath10k_pci 0000:02:00.0: failed to wake target for write32 of 0x00001f7f at 0x0003543c: -110
[ 2596.962535] ath10k_pci 0000:02:00.0: failed to wake target for write32 of 0x00001f81 at 0x0003543c: -110
[ 2597.966980] ath10k_pci 0000:02:00.0: failed to wake target for write32 of 0x00001f83 at 0x0003543c: -110
[ 2598.980285] ath10k_pci 0000:02:00.0: failed to wake target for write32 of 0x00001f85 at 0x0003543c: -110
[ 2599.994441] ath10k_pci 0000:02:00.0: failed to wake target for write32 of 0x00001f87 at 0x0003543c: -110
[ 2601.006946] ath10k_pci 0000:02:00.0: failed to wake target for write32 of 0x00001f89 at 0x0003543c: -110
[ 2602.020812] ath10k_pci 0000:02:00.0: failed to wake target for write32 of 0x00001f8b at 0x0003543c: -110
[ 2603.063045] ath10k_pci 0000:02:00.0: failed to wake target for write32 of 0x00001f8d at 0x0003543c: -110
[ 2604.074685] ath10k_pci 0000:02:00.0: failed to wake target for write32 of 0x00001f8f at 0x0003543c: -110
[ 2605.087912] ath10k_pci 0000:02:00.0: failed to wake target for write32 of 0x00001f91 at 0x0003543c: -110
[ 2606.101254] ath10k_pci 0000:02:00.0: failed to wake target for write32 of 0x00001f93 at 0x0003543c: -110
[ 2607.114648] ath10k_pci 0000:02:00.0: failed to wake target for write32 of 0x00001f95 at 0x0003543c: -110
[ 2608.128135] ath10k_pci 0000:02:00.0: failed to wake target for write32 of 0x00001f97 at 0x0003543c: -110
[ 2609.141409] ath10k_pci 0000:02:00.0: failed to wake target for write32 of 0x00001f99 at 0x0003543c: -110
[ 2610.154661] ath10k_pci 0000:02:00.0: failed to wake target for write32 of 0x00001f9b at 0x0003543c: -110
[ 2611.167958] ath10k_pci 0000:02:00.0: failed to wake target for write32 of 0x00001f9d at 0x0003543c: -110
[ 2612.181346] ath10k_pci 0000:02:00.0: failed to wake target for write32 of 0x00001f9f at 0x0003543c: -110
[ 2613.194592] ath10k_pci 0000:02:00.0: failed to wake target for write32 of 0x00001fa1 at 0x0003543c: -110
[ 2614.207933] ath10k_pci 0000:02:00.0: failed to wake target for write32 of 0x00001fa3 at 0x0003543c: -110
[ 2615.221229] ath10k_pci 0000:02:00.0: failed to wake target for write32 of 0x00001fa5 at 0x0003543c: -110
[ 2616.234608] ath10k_pci 0000:02:00.0: failed to wake target for write32 of 0x00001fa7 at 0x0003543c: -110
[ 2617.247955] ath10k_pci 0000:02:00.0: failed to wake target for write32 of 0x00001fa9 at 0x0003543c: -110
[ 2619.048127] ath10k_pci 0000:02:00.0: failed to wake target for write32 of 0x00001fab at 0x0003543c: -110
[ 2619.086111] ath10k_pci 0000:02:00.0: failed to wake target for write32 of 0x00001fad at 0x0003543c: -110
[ 2620.074846] ath10k_pci 0000:02:00.0: failed to wake target for write32 of 0x00001faf at 0x0003543c: -110
[ 2621.088039] ath10k_pci 0000:02:00.0: failed to wake target for write32 of 0x00001fb1 at 0x0003543c: -110
[ 2622.582490] ath10k_pci 0000:02:00.0: failed to wake target for write32 of 0x00001fb3 at 0x0003543c: -110
[ 2623.594591] ath10k_pci 0000:02:00.0: failed to wake target for write32 of 0x00001fb5 at 0x0003543c: -110
[ 2624.607903] ath10k_pci 0000:02:00.0: failed to wake target for write32 of 0x00001fb7 at 0x0003543c: -110
[ 2625.662827] ath10k_pci 0000:02:00.0: failed to wake target for write32 of 0x00001fb9 at 0x0003543c: -110
[ 2626.687850] ath10k_pci 0000:02:00.0: failed to wake target for write32 of 0x00001fbb at 0x0003543c: -110
[ 2627.701653] ath10k_pci 0000:02:00.0: failed to wake target for write32 of 0x00001fbd at 0x0003543c: -110
[ 2628.714651] ath10k_pci 0000:02:00.0: failed to wake target for write32 of 0x00001fbf at 0x0003543c: -110
[ 2629.727885] ath10k_pci 0000:02:00.0: failed to wake target for write32 of 0x00001fc1 at 0x0003543c: -110
[ 2630.741182] ath10k_pci 0000:02:00.0: failed to wake target for write32 of 0x00001fc3 at 0x0003543c: -110
[ 2632.028680] ath10k_pci 0000:02:00.0: failed to wake target for write32 of 0x00001fc5 at 0x0003543c: -110
[ 2633.034585] ath10k_pci 0000:02:00.0: failed to wake target for write32 of 0x00001fc7 at 0x0003543c: -110
[ 2633.068282] ath10k_pci 0000:02:00.0: failed to wake target for write32 of 0x0000001f at 0x0003503c: -110
[ 2634.047921] ath10k_pci 0000:02:00.0: failed to wake target for write32 of 0x00001fc9 at 0x0003543c: -110
[ 2634.126916] ath10k_pci 0000:02:00.0: failed to wake target for write32 of 0x00000000 at 0x0003503c: -110
[ 2636.256585] ath10k_pci 0000:02:00.0: failed to wake target for write32 of 0x00001fcb at 0x0003543c: -110
[ 2637.274093] ath10k_pci 0000:02:00.0: failed to wake target for write32 of 0x00001fcd at 0x0003543c: -110
[ 2637.293109] ath10k_pci 0000:02:00.0: failed to receive scan abortion completion: timed out
[ 2637.293114] ath10k_pci 0000:02:00.0: failed to stop scan: -110
[ 2637.293115] ath10k_pci 0000:02:00.0: failed to start hw scan: -110
[ 2638.286816] ath10k_pci 0000:02:00.0: failed to wake target for write32 of 0x00001fcf at 0x0003543c: -110
[ 2639.341341] ath10k_pci 0000:02:00.0: failed to wake target for write32 of 0x00001fd1 at 0x0003543c: -110
[ 2640.367934] ath10k_pci 0000:02:00.0: failed to wake target for write32 of 0x00001fd3 at 0x0003543c: -110
[ 2641.381306] ath10k_pci 0000:02:00.0: failed to wake target for write32 of 0x00001fd5 at 0x0003543c: -110
[ 2642.634603] ath10k_pci 0000:02:00.0: failed to wake target for write32 of 0x00001fd7 at 0x0003543c: -110
[ 2643.647859] ath10k_pci 0000:02:00.0: failed to wake target for write32 of 0x00001fd9 at 0x0003543c: -110
[ 2644.661204] ath10k_pci 0000:02:00.0: failed to wake target for write32 of 0x00001fdb at 0x0003543c: -110
[ 2646.268559] ath10k_pci 0000:02:00.0: failed to wake target for write32 of 0x00001fdd at 0x0003543c: -110
[ 2647.274586] ath10k_pci 0000:02:00.0: failed to wake target for write32 of 0x00001fdf at 0x0003543c: -110
[ 2648.287856] ath10k_pci 0000:02:00.0: failed to wake target for write32 of 0x00001fe1 at 0x0003543c: -110
[ 2649.086539] ath10k_pci 0000:02:00.0: failed to wake target for write32 of 0x00001fe3 at 0x0003543c: -110
[ 2649.383561] ath10k_pci 0000:02:00.0: failed to wake target for write32 of 0x00001fe5 at 0x0003543c: -110
[ 2650.394744] ath10k_pci 0000:02:00.0: failed to wake target for write32 of 0x00001fe7 at 0x0003543c: -110
[ 2651.408063] ath10k_pci 0000:02:00.0: failed to wake target for write32 of 0x00001fe9 at 0x0003543c: -110
[ 2652.679578] ath10k_pci 0000:02:00.0: failed to wake target for write32 of 0x00001feb at 0x0003543c: -110
[ 2653.701230] ath10k_pci 0000:02:00.0: failed to wake target for write32 of 0x00001fed at 0x0003543c: -110
[ 2654.714566] ath10k_pci 0000:02:00.0: failed to wake target for write32 of 0x00001fef at 0x0003543c: -110
[ 2656.310806] ath10k_pci 0000:02:00.0: failed to wake target for write32 of 0x00001ff1 at 0x0003543c: -110
[ 2657.328033] ath10k_pci 0000:02:00.0: failed to wake target for write32 of 0x00001ff3 at 0x0003543c: -110
[ 2658.341357] ath10k_pci 0000:02:00.0: failed to wake target for write32 of 0x00001ff5 at 0x0003543c: -110
[ 2659.423643] ath10k_pci 0000:02:00.0: failed to wake target for write32 of 0x00001ff7 at 0x0003543c: -110
[ 2660.446850] ath10k_pci 0000:02:00.0: failed to wake target for write32 of 0x00001ff9 at 0x0003543c: -110
[ 2661.460114] ath10k_pci 0000:02:00.0: failed to wake target for write32 of 0x00001ffb at 0x0003543c: -110
[ 2663.142727] ath10k_pci 0000:02:00.0: failed to wake target for write32 of 0x00001ffd at 0x0003543c: -110
[ 2664.154518] ath10k_pci 0000:02:00.0: failed to wake target for write32 of 0x00001fff at 0x0003543c: -110
[ 2665.167875] ath10k_pci 0000:02:00.0: failed to wake target for write32 of 0x00000001 at 0x0003543c: -110
[ 2666.318298] ath10k_pci 0000:02:00.0: failed to wake target for write32 of 0x00000003 at 0x0003543c: -110
[ 2667.326791] ath10k_pci 0000:02:00.0: failed to wake target for write32 of 0x00000005 at 0x0003543c: -110
[ 2668.340397] ath10k_pci 0000:02:00.0: failed to wake target for write32 of 0x00000007 at 0x0003543c: -110
[ 2669.464587] ath10k_pci 0000:02:00.0: failed to wake target for write32 of 0x00000009 at 0x0003543c: -110
[ 2670.473527] ath10k_pci 0000:02:00.0: failed to wake target for write32 of 0x0000000b at 0x0003543c: -110
[ 2671.486820] ath10k_pci 0000:02:00.0: failed to wake target for write32 of 0x0000000d at 0x0003543c: -110
[ 2672.686281] ath10k_pci 0000:02:00.0: failed to wake target for write32 of 0x0000000f at 0x0003543c: -110
[ 2673.704595] ath10k_pci 0000:02:00.0: failed to wake target for write32 of 0x00000011 at 0x0003543c: -110
[ 2674.714564] ath10k_pci 0000:02:00.0: failed to wake target for write32 of 0x00000013 at 0x0003543c: -110
[ 2676.361346] ath10k_pci 0000:02:00.0: failed to wake target for write32 of 0x00000015 at 0x0003543c: -110
[ 2677.379220] ath10k_pci 0000:02:00.0: failed to wake target for write32 of 0x00000017 at 0x0003543c: -110
[ 2678.392490] ath10k_pci 0000:02:00.0: failed to wake target for write32 of 0x00000019 at 0x0003543c: -110
[ 2679.086180] ath10k_pci 0000:02:00.0: failed to wake target for write32 of 0x0000001b at 0x0003543c: -110
[ 2679.506163] ath10k_pci 0000:02:00.0: failed to wake target for write32 of 0x0000001d at 0x0003543c: -110
[ 2680.526767] ath10k_pci 0000:02:00.0: failed to wake target for write32 of 0x0000001f at 0x0003543c: -110
[ 2681.540271] ath10k_pci 0000:02:00.0: failed to wake target for write32 of 0x00000021 at 0x0003543c: -110
[ 2682.691391] ath10k_pci 0000:02:00.0: failed to wake target for write32 of 0x00000023 at 0x0003543c: -110
[ 2683.700307] ath10k_pci 0000:02:00.0: failed to wake target for write32 of 0x00000025 at 0x0003543c: -110
[ 2684.713730] ath10k_pci 0000:02:00.0: failed to wake target for write32 of 0x00000027 at 0x0003543c: -110
[ 2686.368226] ath10k_pci 0000:02:00.0: failed to wake target for write32 of 0x00000029 at 0x0003543c: -110
[ 2687.380425] ath10k_pci 0000:02:00.0: failed to wake target for write32 of 0x0000002b at 0x0003543c: -110
[ 2688.393800] ath10k_pci 0000:02:00.0: failed to wake target for write32 of 0x0000002d at 0x0003543c: -110
[ 2689.546036] ath10k_pci 0000:02:00.0: failed to wake target for write32 of 0x0000002f at 0x0003543c: -110
[ 2690.553655] ath10k_pci 0000:02:00.0: failed to wake target for write32 of 0x00000031 at 0x0003543c: -110
[ 2691.567000] ath10k_pci 0000:02:00.0: failed to wake target for write32 of 0x00000033 at 0x0003543c: -110
[-- Attachment #3: Type: text/plain, Size: 146 bytes --]
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
^ permalink raw reply [flat|nested] 12+ messages in thread
* RE: Reporting a bug for QCA6174 802.11ac
2017-03-20 15:31 Reporting a bug for QCA6174 802.11ac Guilherme Íscaro
@ 2017-03-21 18:35 ` Ryan Hsu
2017-03-21 18:58 ` Guilherme Íscaro
0 siblings, 1 reply; 12+ messages in thread
From: Ryan Hsu @ 2017-03-21 18:35 UTC (permalink / raw)
To: Guilherme Íscaro, ath10k
Iscaro,
Not sure how exactly the issue and scenario of your usage.
e.g how far the AP from you and is there any specific scenario you're seeing the failure open?
Also would you mind try to pick up the latest firmware to see if that help?
https://github.com/kvalo/ath10k-firmware/tree/master/QCA6174/hw3.0/4.4
With the latest firmware, you might also need to get the latest driver backport package.
http://buildbot.w1.fi/backports-wireless-testing/
Ryan
> -----Original Message-----
> From: ath10k [mailto:ath10k-bounces@lists.infradead.org] On Behalf Of
> Guilherme Íscaro
> Sent: Monday, March 20, 2017 08:32 AM
> To: ath10k@lists.infradead.org
> Subject: Reporting a bug for QCA6174 802.11ac
>
> Hello everyone, I would like to report a bug for QCA6174.
>
> I use WiFi everyday, but from time to time I lose my connection. This might be
> related to a firmware problem, because after I lose my connection the firmware
> keeps flooding dmesg about problems.
>
> I have this problem since I bought my laptop (which was last year) and I do
> regular updates in my system.
>
> P.S: dmest output attached.
>
> My system:
>
> Dist: Arch Linux.
> Kernel: 4.10.3-1
> Linux-firmware version: 20170309.695f2d6-1 (commit 695f2d6d82173f4e...
> from linux-firmware)
> Board: 02:00.0 Network controller: Qualcomm Atheros QCA6174 802.11ac
> Wireless Network Adapter (rev 32)
>
>
> Please, let me know if I should provide more info.
>
> Thanks.
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: Reporting a bug for QCA6174 802.11ac
2017-03-21 18:35 ` Ryan Hsu
@ 2017-03-21 18:58 ` Guilherme Íscaro
2017-03-22 13:56 ` Guilherme Íscaro
0 siblings, 1 reply; 12+ messages in thread
From: Guilherme Íscaro @ 2017-03-21 18:58 UTC (permalink / raw)
To: Ryan Hsu; +Cc: ath10k
Hello Ryan, Thanks for your response.
My AP is in the same room that I use my notebook, it's right in front
of me. There's no specific scenario for this failure to happen.
Sometimes it does not happens for days, but sometimes it happens 3/4
times in the same day.
It looks like that there is not specific scenario, sometimes it
happens while I'm using firefox, sometimes it happens when my laptop
is "doing nothing". (Was it helpful?)
I'm using WiFi 802.11n, 2.4ghz with AES.
I'll try this new firmware/driver.
Thanks.
2017-03-21 15:35 GMT-03:00 Ryan Hsu <ryanhsu@qca.qualcomm.com>:
> Iscaro,
>
> Not sure how exactly the issue and scenario of your usage.
>
> e.g how far the AP from you and is there any specific scenario you're seeing the failure open?
>
> Also would you mind try to pick up the latest firmware to see if that help?
> https://github.com/kvalo/ath10k-firmware/tree/master/QCA6174/hw3.0/4.4
>
> With the latest firmware, you might also need to get the latest driver backport package.
> http://buildbot.w1.fi/backports-wireless-testing/
>
> Ryan
>
>> -----Original Message-----
>> From: ath10k [mailto:ath10k-bounces@lists.infradead.org] On Behalf Of
>> Guilherme Íscaro
>> Sent: Monday, March 20, 2017 08:32 AM
>> To: ath10k@lists.infradead.org
>> Subject: Reporting a bug for QCA6174 802.11ac
>>
>> Hello everyone, I would like to report a bug for QCA6174.
>>
>> I use WiFi everyday, but from time to time I lose my connection. This might be
>> related to a firmware problem, because after I lose my connection the firmware
>> keeps flooding dmesg about problems.
>>
>> I have this problem since I bought my laptop (which was last year) and I do
>> regular updates in my system.
>>
>> P.S: dmest output attached.
>>
>> My system:
>>
>> Dist: Arch Linux.
>> Kernel: 4.10.3-1
>> Linux-firmware version: 20170309.695f2d6-1 (commit 695f2d6d82173f4e...
>> from linux-firmware)
>> Board: 02:00.0 Network controller: Qualcomm Atheros QCA6174 802.11ac
>> Wireless Network Adapter (rev 32)
>>
>>
>> Please, let me know if I should provide more info.
>>
>> Thanks.
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: Reporting a bug for QCA6174 802.11ac
2017-03-21 18:58 ` Guilherme Íscaro
@ 2017-03-22 13:56 ` Guilherme Íscaro
2017-03-22 22:17 ` Guilherme Íscaro
0 siblings, 1 reply; 12+ messages in thread
From: Guilherme Íscaro @ 2017-03-22 13:56 UTC (permalink / raw)
To: Ryan Hsu; +Cc: ath10k
I've installed the new firmware/driver. I'll send a new email in some
days to tell you guys if the new driver/firmware resolved the problem.
Thanks for the help.
2017-03-21 15:58 GMT-03:00 Guilherme Íscaro <cabelitostos@gmail.com>:
> Hello Ryan, Thanks for your response.
>
> My AP is in the same room that I use my notebook, it's right in front
> of me. There's no specific scenario for this failure to happen.
> Sometimes it does not happens for days, but sometimes it happens 3/4
> times in the same day.
> It looks like that there is not specific scenario, sometimes it
> happens while I'm using firefox, sometimes it happens when my laptop
> is "doing nothing". (Was it helpful?)
>
> I'm using WiFi 802.11n, 2.4ghz with AES.
>
> I'll try this new firmware/driver.
>
> Thanks.
>
>
>
> 2017-03-21 15:35 GMT-03:00 Ryan Hsu <ryanhsu@qca.qualcomm.com>:
>> Iscaro,
>>
>> Not sure how exactly the issue and scenario of your usage.
>>
>> e.g how far the AP from you and is there any specific scenario you're seeing the failure open?
>>
>> Also would you mind try to pick up the latest firmware to see if that help?
>> https://github.com/kvalo/ath10k-firmware/tree/master/QCA6174/hw3.0/4.4
>>
>> With the latest firmware, you might also need to get the latest driver backport package.
>> http://buildbot.w1.fi/backports-wireless-testing/
>>
>> Ryan
>>
>>> -----Original Message-----
>>> From: ath10k [mailto:ath10k-bounces@lists.infradead.org] On Behalf Of
>>> Guilherme Íscaro
>>> Sent: Monday, March 20, 2017 08:32 AM
>>> To: ath10k@lists.infradead.org
>>> Subject: Reporting a bug for QCA6174 802.11ac
>>>
>>> Hello everyone, I would like to report a bug for QCA6174.
>>>
>>> I use WiFi everyday, but from time to time I lose my connection. This might be
>>> related to a firmware problem, because after I lose my connection the firmware
>>> keeps flooding dmesg about problems.
>>>
>>> I have this problem since I bought my laptop (which was last year) and I do
>>> regular updates in my system.
>>>
>>> P.S: dmest output attached.
>>>
>>> My system:
>>>
>>> Dist: Arch Linux.
>>> Kernel: 4.10.3-1
>>> Linux-firmware version: 20170309.695f2d6-1 (commit 695f2d6d82173f4e...
>>> from linux-firmware)
>>> Board: 02:00.0 Network controller: Qualcomm Atheros QCA6174 802.11ac
>>> Wireless Network Adapter (rev 32)
>>>
>>>
>>> Please, let me know if I should provide more info.
>>>
>>> Thanks.
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: Reporting a bug for QCA6174 802.11ac
2017-03-22 13:56 ` Guilherme Íscaro
@ 2017-03-22 22:17 ` Guilherme Íscaro
2017-03-23 22:46 ` Ryan Hsu
0 siblings, 1 reply; 12+ messages in thread
From: Guilherme Íscaro @ 2017-03-22 22:17 UTC (permalink / raw)
To: Ryan Hsu; +Cc: ath10k
Hi, unfortunately the problem happened with the new drivers and firmware. :[
I really don't know what to do anymore.....
thanks.
2017-03-22 10:56 GMT-03:00 Guilherme Íscaro <cabelitostos@gmail.com>:
> I've installed the new firmware/driver. I'll send a new email in some
> days to tell you guys if the new driver/firmware resolved the problem.
>
> Thanks for the help.
>
> 2017-03-21 15:58 GMT-03:00 Guilherme Íscaro <cabelitostos@gmail.com>:
>> Hello Ryan, Thanks for your response.
>>
>> My AP is in the same room that I use my notebook, it's right in front
>> of me. There's no specific scenario for this failure to happen.
>> Sometimes it does not happens for days, but sometimes it happens 3/4
>> times in the same day.
>> It looks like that there is not specific scenario, sometimes it
>> happens while I'm using firefox, sometimes it happens when my laptop
>> is "doing nothing". (Was it helpful?)
>>
>> I'm using WiFi 802.11n, 2.4ghz with AES.
>>
>> I'll try this new firmware/driver.
>>
>> Thanks.
>>
>>
>>
>> 2017-03-21 15:35 GMT-03:00 Ryan Hsu <ryanhsu@qca.qualcomm.com>:
>>> Iscaro,
>>>
>>> Not sure how exactly the issue and scenario of your usage.
>>>
>>> e.g how far the AP from you and is there any specific scenario you're seeing the failure open?
>>>
>>> Also would you mind try to pick up the latest firmware to see if that help?
>>> https://github.com/kvalo/ath10k-firmware/tree/master/QCA6174/hw3.0/4.4
>>>
>>> With the latest firmware, you might also need to get the latest driver backport package.
>>> http://buildbot.w1.fi/backports-wireless-testing/
>>>
>>> Ryan
>>>
>>>> -----Original Message-----
>>>> From: ath10k [mailto:ath10k-bounces@lists.infradead.org] On Behalf Of
>>>> Guilherme Íscaro
>>>> Sent: Monday, March 20, 2017 08:32 AM
>>>> To: ath10k@lists.infradead.org
>>>> Subject: Reporting a bug for QCA6174 802.11ac
>>>>
>>>> Hello everyone, I would like to report a bug for QCA6174.
>>>>
>>>> I use WiFi everyday, but from time to time I lose my connection. This might be
>>>> related to a firmware problem, because after I lose my connection the firmware
>>>> keeps flooding dmesg about problems.
>>>>
>>>> I have this problem since I bought my laptop (which was last year) and I do
>>>> regular updates in my system.
>>>>
>>>> P.S: dmest output attached.
>>>>
>>>> My system:
>>>>
>>>> Dist: Arch Linux.
>>>> Kernel: 4.10.3-1
>>>> Linux-firmware version: 20170309.695f2d6-1 (commit 695f2d6d82173f4e...
>>>> from linux-firmware)
>>>> Board: 02:00.0 Network controller: Qualcomm Atheros QCA6174 802.11ac
>>>> Wireless Network Adapter (rev 32)
>>>>
>>>>
>>>> Please, let me know if I should provide more info.
>>>>
>>>> Thanks.
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: Reporting a bug for QCA6174 802.11ac
2017-03-22 22:17 ` Guilherme Íscaro
@ 2017-03-23 22:46 ` Ryan Hsu
2017-03-23 23:11 ` Guilherme Íscaro
0 siblings, 1 reply; 12+ messages in thread
From: Ryan Hsu @ 2017-03-23 22:46 UTC (permalink / raw)
To: Guilherme Íscaro; +Cc: ath10k
Let's start from the basic, could you provide the ftrace logs and also the AP model you're using? try without security or different phy mode to see if it would behave differently?
The last thing is, your previous logs only stuffed with the register access failure logs, can you share a full dmesg logs as well?
Ryan
________________________________________
From: Guilherme Íscaro <cabelitostos@gmail.com>
Sent: Wednesday, March 22, 2017 3:17 PM
To: Ryan Hsu
Cc: ath10k@lists.infradead.org
Subject: Re: Reporting a bug for QCA6174 802.11ac
Hi, unfortunately the problem happened with the new drivers and firmware. :[
I really don't know what to do anymore.....
thanks.
2017-03-22 10:56 GMT-03:00 Guilherme Íscaro <cabelitostos@gmail.com>:
> I've installed the new firmware/driver. I'll send a new email in some
> days to tell you guys if the new driver/firmware resolved the problem.
>
> Thanks for the help.
>
> 2017-03-21 15:58 GMT-03:00 Guilherme Íscaro <cabelitostos@gmail.com>:
>> Hello Ryan, Thanks for your response.
>>
>> My AP is in the same room that I use my notebook, it's right in front
>> of me. There's no specific scenario for this failure to happen.
>> Sometimes it does not happens for days, but sometimes it happens 3/4
>> times in the same day.
>> It looks like that there is not specific scenario, sometimes it
>> happens while I'm using firefox, sometimes it happens when my laptop
>> is "doing nothing". (Was it helpful?)
>>
>> I'm using WiFi 802.11n, 2.4ghz with AES.
>>
>> I'll try this new firmware/driver.
>>
>> Thanks.
>>
>>
>>
>> 2017-03-21 15:35 GMT-03:00 Ryan Hsu <ryanhsu@qca.qualcomm.com>:
>>> Iscaro,
>>>
>>> Not sure how exactly the issue and scenario of your usage.
>>>
>>> e.g how far the AP from you and is there any specific scenario you're seeing the failure open?
>>>
>>> Also would you mind try to pick up the latest firmware to see if that help?
>>> https://github.com/kvalo/ath10k-firmware/tree/master/QCA6174/hw3.0/4.4
>>>
>>> With the latest firmware, you might also need to get the latest driver backport package.
>>> http://buildbot.w1.fi/backports-wireless-testing/
>>>
>>> Ryan
>>>
>>>> -----Original Message-----
>>>> From: ath10k [mailto:ath10k-bounces@lists.infradead.org] On Behalf Of
>>>> Guilherme Íscaro
>>>> Sent: Monday, March 20, 2017 08:32 AM
>>>> To: ath10k@lists.infradead.org
>>>> Subject: Reporting a bug for QCA6174 802.11ac
>>>>
>>>> Hello everyone, I would like to report a bug for QCA6174.
>>>>
>>>> I use WiFi everyday, but from time to time I lose my connection. This might be
>>>> related to a firmware problem, because after I lose my connection the firmware
>>>> keeps flooding dmesg about problems.
>>>>
>>>> I have this problem since I bought my laptop (which was last year) and I do
>>>> regular updates in my system.
>>>>
>>>> P.S: dmest output attached.
>>>>
>>>> My system:
>>>>
>>>> Dist: Arch Linux.
>>>> Kernel: 4.10.3-1
>>>> Linux-firmware version: 20170309.695f2d6-1 (commit 695f2d6d82173f4e...
>>>> from linux-firmware)
>>>> Board: 02:00.0 Network controller: Qualcomm Atheros QCA6174 802.11ac
>>>> Wireless Network Adapter (rev 32)
>>>>
>>>>
>>>> Please, let me know if I should provide more info.
>>>>
>>>> Thanks.
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: Reporting a bug for QCA6174 802.11ac
2017-03-23 22:46 ` Ryan Hsu
@ 2017-03-23 23:11 ` Guilherme Íscaro
2017-03-28 17:45 ` Guilherme Íscaro
0 siblings, 1 reply; 12+ messages in thread
From: Guilherme Íscaro @ 2017-03-23 23:11 UTC (permalink / raw)
To: Ryan Hsu; +Cc: ath10k
[-- Attachment #1: Type: text/plain, Size: 3980 bytes --]
Hello Ryan, thanks for your contact.
My AP is a D-link DMG 6661. I'll try another wifi settings and check
if it happens and if it happens I'll provide de ftrace logs.
Btw, just after I read your email the bug happened. Here's the full
dmesg. After the "failed to wake target" problem happens it keeps
flooding dmesg forever. There are no other error indications.
I guess that the dmesg output will not help us, maybe ftrace will be
more helpful. Anyway, here's the dmesg...
Thanks for your help
2017-03-23 19:46 GMT-03:00 Ryan Hsu <ryanhsu@qca.qualcomm.com>:
> Let's start from the basic, could you provide the ftrace logs and also the AP model you're using? try without security or different phy mode to see if it would behave differently?
>
> The last thing is, your previous logs only stuffed with the register access failure logs, can you share a full dmesg logs as well?
>
> Ryan
> ________________________________________
> From: Guilherme Íscaro <cabelitostos@gmail.com>
> Sent: Wednesday, March 22, 2017 3:17 PM
> To: Ryan Hsu
> Cc: ath10k@lists.infradead.org
> Subject: Re: Reporting a bug for QCA6174 802.11ac
>
> Hi, unfortunately the problem happened with the new drivers and firmware. :[
> I really don't know what to do anymore.....
>
> thanks.
>
> 2017-03-22 10:56 GMT-03:00 Guilherme Íscaro <cabelitostos@gmail.com>:
>> I've installed the new firmware/driver. I'll send a new email in some
>> days to tell you guys if the new driver/firmware resolved the problem.
>>
>> Thanks for the help.
>>
>> 2017-03-21 15:58 GMT-03:00 Guilherme Íscaro <cabelitostos@gmail.com>:
>>> Hello Ryan, Thanks for your response.
>>>
>>> My AP is in the same room that I use my notebook, it's right in front
>>> of me. There's no specific scenario for this failure to happen.
>>> Sometimes it does not happens for days, but sometimes it happens 3/4
>>> times in the same day.
>>> It looks like that there is not specific scenario, sometimes it
>>> happens while I'm using firefox, sometimes it happens when my laptop
>>> is "doing nothing". (Was it helpful?)
>>>
>>> I'm using WiFi 802.11n, 2.4ghz with AES.
>>>
>>> I'll try this new firmware/driver.
>>>
>>> Thanks.
>>>
>>>
>>>
>>> 2017-03-21 15:35 GMT-03:00 Ryan Hsu <ryanhsu@qca.qualcomm.com>:
>>>> Iscaro,
>>>>
>>>> Not sure how exactly the issue and scenario of your usage.
>>>>
>>>> e.g how far the AP from you and is there any specific scenario you're seeing the failure open?
>>>>
>>>> Also would you mind try to pick up the latest firmware to see if that help?
>>>> https://github.com/kvalo/ath10k-firmware/tree/master/QCA6174/hw3.0/4.4
>>>>
>>>> With the latest firmware, you might also need to get the latest driver backport package.
>>>> http://buildbot.w1.fi/backports-wireless-testing/
>>>>
>>>> Ryan
>>>>
>>>>> -----Original Message-----
>>>>> From: ath10k [mailto:ath10k-bounces@lists.infradead.org] On Behalf Of
>>>>> Guilherme Íscaro
>>>>> Sent: Monday, March 20, 2017 08:32 AM
>>>>> To: ath10k@lists.infradead.org
>>>>> Subject: Reporting a bug for QCA6174 802.11ac
>>>>>
>>>>> Hello everyone, I would like to report a bug for QCA6174.
>>>>>
>>>>> I use WiFi everyday, but from time to time I lose my connection. This might be
>>>>> related to a firmware problem, because after I lose my connection the firmware
>>>>> keeps flooding dmesg about problems.
>>>>>
>>>>> I have this problem since I bought my laptop (which was last year) and I do
>>>>> regular updates in my system.
>>>>>
>>>>> P.S: dmest output attached.
>>>>>
>>>>> My system:
>>>>>
>>>>> Dist: Arch Linux.
>>>>> Kernel: 4.10.3-1
>>>>> Linux-firmware version: 20170309.695f2d6-1 (commit 695f2d6d82173f4e...
>>>>> from linux-firmware)
>>>>> Board: 02:00.0 Network controller: Qualcomm Atheros QCA6174 802.11ac
>>>>> Wireless Network Adapter (rev 32)
>>>>>
>>>>>
>>>>> Please, let me know if I should provide more info.
>>>>>
>>>>> Thanks.
[-- Attachment #2: full-dmesg.txt --]
[-- Type: text/plain, Size: 63131 bytes --]
[ 0.000000] Linux version 4.10.4-1-ARCH (builduser@tobias) (gcc version 6.3.1 20170306 (GCC) ) #1 SMP PREEMPT Sat Mar 18 19:39:18 CET 2017
[ 0.000000] Command line: BOOT_IMAGE=/boot/vmlinuz-linux root=UUID=6d22f373-b455-4a50-a80f-fac7aad2f8e3 rw quiet
[ 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] e820: BIOS-provided physical RAM map:
[ 0.000000] BIOS-e820: [mem 0x0000000000000000-0x000000000009c7ff] usable
[ 0.000000] BIOS-e820: [mem 0x000000000009c800-0x000000000009ffff] reserved
[ 0.000000] BIOS-e820: [mem 0x00000000000e0000-0x00000000000fffff] reserved
[ 0.000000] BIOS-e820: [mem 0x0000000000100000-0x000000006a3c2fff] usable
[ 0.000000] BIOS-e820: [mem 0x000000006a3c3000-0x000000006a3c3fff] ACPI NVS
[ 0.000000] BIOS-e820: [mem 0x000000006a3c4000-0x0000000077627fff] reserved
[ 0.000000] BIOS-e820: [mem 0x0000000077628000-0x0000000077f98fff] ACPI NVS
[ 0.000000] BIOS-e820: [mem 0x0000000077f99000-0x0000000077ffefff] ACPI data
[ 0.000000] BIOS-e820: [mem 0x0000000078000000-0x00000000780fffff] reserved
[ 0.000000] BIOS-e820: [mem 0x00000000e0000000-0x00000000efffffff] reserved
[ 0.000000] BIOS-e820: [mem 0x00000000fe000000-0x00000000fe010fff] reserved
[ 0.000000] BIOS-e820: [mem 0x00000000fec00000-0x00000000fec00fff] reserved
[ 0.000000] BIOS-e820: [mem 0x00000000fee00000-0x00000000fee00fff] reserved
[ 0.000000] BIOS-e820: [mem 0x00000000ff000000-0x00000000ffffffff] reserved
[ 0.000000] BIOS-e820: [mem 0x0000000100000000-0x0000000482ffffff] usable
[ 0.000000] NX (Execute Disable) protection: active
[ 0.000000] SMBIOS 2.8 present.
[ 0.000000] DMI: Dell Inc. Inspiron 5457/0WT51R, BIOS 1.1.9 04/25/2016
[ 0.000000] e820: update [mem 0x00000000-0x00000fff] usable ==> reserved
[ 0.000000] e820: remove [mem 0x000a0000-0x000fffff] usable
[ 0.000000] e820: last_pfn = 0x483000 max_arch_pfn = 0x400000000
[ 0.000000] MTRR default type: write-back
[ 0.000000] MTRR fixed ranges enabled:
[ 0.000000] 00000-9FFFF write-back
[ 0.000000] A0000-BFFFF uncachable
[ 0.000000] C0000-FFFFF write-protect
[ 0.000000] MTRR variable ranges enabled:
[ 0.000000] 0 base 0080000000 mask 7F80000000 uncachable
[ 0.000000] 1 base 007C000000 mask 7FFC000000 uncachable
[ 0.000000] 2 base 007A000000 mask 7FFE000000 uncachable
[ 0.000000] 3 base 0079800000 mask 7FFF800000 uncachable
[ 0.000000] 4 disabled
[ 0.000000] 5 disabled
[ 0.000000] 6 disabled
[ 0.000000] 7 disabled
[ 0.000000] 8 disabled
[ 0.000000] 9 disabled
[ 0.000000] x86/PAT: Configuration [0-7]: WB WC UC- UC WB WC UC- WT
[ 0.000000] e820: last_pfn = 0x6a3c3 max_arch_pfn = 0x400000000
[ 0.000000] found SMP MP-table at [mem 0x000fce00-0x000fce0f] mapped at [ffff8800000fce00]
[ 0.000000] Scanning 1 areas for low memory corruption
[ 0.000000] Base memory trampoline at [ffff880000096000] 96000 size 24576
[ 0.000000] Using GB pages for direct mapping
[ 0.000000] BRK [0x01d5f000, 0x01d5ffff] PGTABLE
[ 0.000000] BRK [0x01d60000, 0x01d60fff] PGTABLE
[ 0.000000] BRK [0x01d61000, 0x01d61fff] PGTABLE
[ 0.000000] BRK [0x01d62000, 0x01d62fff] PGTABLE
[ 0.000000] RAMDISK: [mem 0x374a8000-0x37a4bfff]
[ 0.000000] ACPI: Early table checksum verification disabled
[ 0.000000] ACPI: RSDP 0x00000000000EF380 000024 (v02 DELL )
[ 0.000000] ACPI: XSDT 0x0000000077FD40A8 0000D4 (v01 DELL CBX3 01072009 AMI 00010013)
[ 0.000000] ACPI: FACP 0x0000000077FF1BA0 00010C (v05 DELL CBX3 01072009 AMI 00010013)
[ 0.000000] ACPI: DSDT 0x0000000077FD4210 01D98C (v02 DELL CBX3 01072009 INTL 20120913)
[ 0.000000] ACPI: FACS 0x0000000077F97F80 000040
[ 0.000000] ACPI: APIC 0x0000000077FF1CB0 000084 (v03 DELL CBX3 01072009 AMI 00010013)
[ 0.000000] ACPI: FPDT 0x0000000077FF1D38 000044 (v01 DELL CBX3 01072009 AMI 00010013)
[ 0.000000] ACPI: FIDT 0x0000000077FF1D80 00009C (v01 DELL CBX3 01072009 AMI 00010013)
[ 0.000000] ACPI: MCFG 0x0000000077FF1E20 00003C (v01 DELL CBX3 01072009 MSFT 00000097)
[ 0.000000] ACPI: HPET 0x0000000077FF1E60 000038 (v01 DELL CBX3 01072009 AMI. 0005000B)
[ 0.000000] ACPI: SSDT 0x0000000077FF1E98 000315 (v01 SataRe SataTabl 00001000 INTL 20120913)
[ 0.000000] ACPI: LPIT 0x0000000077FF21B0 000094 (v01 INTEL SKL-ULT 00000000 MSFT 0000005F)
[ 0.000000] ACPI: SSDT 0x0000000077FF2248 000248 (v02 INTEL sensrhub 00000000 INTL 20120913)
[ 0.000000] ACPI: SSDT 0x0000000077FF2490 002BAE (v02 INTEL PtidDevc 00001000 INTL 20120913)
[ 0.000000] ACPI: SSDT 0x0000000077FF5040 000C45 (v02 INTEL Ther_Rvp 00001000 INTL 20120913)
[ 0.000000] ACPI: DBGP 0x0000000077FF5C88 000034 (v01 INTEL 00000000 MSFT 0000005F)
[ 0.000000] ACPI: DBG2 0x0000000077FF5CC0 000054 (v00 INTEL 00000000 MSFT 0000005F)
[ 0.000000] ACPI: SSDT 0x0000000077FF5D18 000740 (v02 INTEL xh_rvp07 00000000 INTL 20120913)
[ 0.000000] ACPI: BOOT 0x0000000077FF6458 000028 (v01 DELL CBX3 01072009 AMI 00010013)
[ 0.000000] ACPI: SSDT 0x0000000077FF6480 003617 (v02 SaSsdt SaSsdt 00003000 INTL 20120913)
[ 0.000000] ACPI: UEFI 0x0000000077FF9A98 000042 (v01 00000000 00000000)
[ 0.000000] ACPI: SSDT 0x0000000077FF9AE0 000E58 (v02 CpuRef CpuSsdt 00003000 INTL 20120913)
[ 0.000000] ACPI: SSDT 0x0000000077FFA938 0006AA (v02 SgRef SgPch 00001000 INTL 20120913)
[ 0.000000] ACPI: DMAR 0x0000000077FFAFE8 0000F0 (v01 INTEL SKL 00000001 INTL 00000001)
[ 0.000000] ACPI: SSDT 0x0000000077FFB0D8 0018B8 (v01 OptRef OptTabl 00001000 INTL 20120913)
[ 0.000000] ACPI: ASF! 0x0000000077FFC990 0000A5 (v32 INTEL HCG 00000001 TFSM 000F4240)
[ 0.000000] ACPI: Local APIC address 0xfee00000
[ 0.000000] No NUMA configuration found
[ 0.000000] Faking a node at [mem 0x0000000000000000-0x0000000482ffffff]
[ 0.000000] NODE_DATA(0) allocated [mem 0x482ff9000-0x482ffdfff]
[ 0.000000] Zone ranges:
[ 0.000000] DMA [mem 0x0000000000001000-0x0000000000ffffff]
[ 0.000000] DMA32 [mem 0x0000000001000000-0x00000000ffffffff]
[ 0.000000] Normal [mem 0x0000000100000000-0x0000000482ffffff]
[ 0.000000] Device empty
[ 0.000000] Movable zone start for each node
[ 0.000000] Early memory node ranges
[ 0.000000] node 0: [mem 0x0000000000001000-0x000000000009bfff]
[ 0.000000] node 0: [mem 0x0000000000100000-0x000000006a3c2fff]
[ 0.000000] node 0: [mem 0x0000000100000000-0x0000000482ffffff]
[ 0.000000] Initmem setup node 0 [mem 0x0000000000001000-0x0000000482ffffff]
[ 0.000000] On node 0 totalpages: 4117342
[ 0.000000] DMA zone: 64 pages used for memmap
[ 0.000000] DMA zone: 21 pages reserved
[ 0.000000] DMA zone: 3995 pages, LIFO batch:0
[ 0.000000] DMA32 zone: 6736 pages used for memmap
[ 0.000000] DMA32 zone: 431043 pages, LIFO batch:31
[ 0.000000] Normal zone: 57536 pages used for memmap
[ 0.000000] Normal zone: 3682304 pages, LIFO batch:31
[ 0.000000] Reserving Intel graphics memory at 0x000000007a000000-0x000000007bffffff
[ 0.000000] ACPI: PM-Timer IO Port: 0x1808
[ 0.000000] ACPI: Local APIC address 0xfee00000
[ 0.000000] ACPI: LAPIC_NMI (acpi_id[0x01] high edge lint[0x1])
[ 0.000000] ACPI: LAPIC_NMI (acpi_id[0x02] high edge lint[0x1])
[ 0.000000] ACPI: LAPIC_NMI (acpi_id[0x03] high edge lint[0x1])
[ 0.000000] ACPI: LAPIC_NMI (acpi_id[0x04] high edge lint[0x1])
[ 0.000000] IOAPIC[0]: apic_id 2, version 32, address 0xfec00000, GSI 0-119
[ 0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
[ 0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
[ 0.000000] ACPI: IRQ0 used by override.
[ 0.000000] ACPI: IRQ9 used by override.
[ 0.000000] Using ACPI (MADT) for SMP configuration information
[ 0.000000] ACPI: HPET id: 0x8086a701 base: 0xfed00000
[ 0.000000] smpboot: Allowing 4 CPUs, 0 hotplug CPUs
[ 0.000000] PM: Registered nosave memory: [mem 0x00000000-0x00000fff]
[ 0.000000] PM: Registered nosave memory: [mem 0x0009c000-0x0009cfff]
[ 0.000000] PM: Registered nosave memory: [mem 0x0009d000-0x0009ffff]
[ 0.000000] PM: Registered nosave memory: [mem 0x000a0000-0x000dffff]
[ 0.000000] PM: Registered nosave memory: [mem 0x000e0000-0x000fffff]
[ 0.000000] PM: Registered nosave memory: [mem 0x6a3c3000-0x6a3c3fff]
[ 0.000000] PM: Registered nosave memory: [mem 0x6a3c4000-0x77627fff]
[ 0.000000] PM: Registered nosave memory: [mem 0x77628000-0x77f98fff]
[ 0.000000] PM: Registered nosave memory: [mem 0x77f99000-0x77ffefff]
[ 0.000000] PM: Registered nosave memory: [mem 0x77fff000-0x77ffffff]
[ 0.000000] PM: Registered nosave memory: [mem 0x78000000-0x780fffff]
[ 0.000000] PM: Registered nosave memory: [mem 0x78100000-0x79ffffff]
[ 0.000000] PM: Registered nosave memory: [mem 0x7a000000-0x7bffffff]
[ 0.000000] PM: Registered nosave memory: [mem 0x7c000000-0xdfffffff]
[ 0.000000] PM: Registered nosave memory: [mem 0xe0000000-0xefffffff]
[ 0.000000] PM: Registered nosave memory: [mem 0xf0000000-0xfdffffff]
[ 0.000000] PM: Registered nosave memory: [mem 0xfe000000-0xfe010fff]
[ 0.000000] PM: Registered nosave memory: [mem 0xfe011000-0xfebfffff]
[ 0.000000] PM: Registered nosave memory: [mem 0xfec00000-0xfec00fff]
[ 0.000000] PM: Registered nosave memory: [mem 0xfec01000-0xfedfffff]
[ 0.000000] PM: Registered nosave memory: [mem 0xfee00000-0xfee00fff]
[ 0.000000] PM: Registered nosave memory: [mem 0xfee01000-0xfeffffff]
[ 0.000000] PM: Registered nosave memory: [mem 0xff000000-0xffffffff]
[ 0.000000] e820: [mem 0x7c000000-0xdfffffff] available for PCI devices
[ 0.000000] Booting paravirtualized kernel on bare hardware
[ 0.000000] clocksource: refined-jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 6370452778343963 ns
[ 0.000000] setup_percpu: NR_CPUS:128 nr_cpumask_bits:128 nr_cpu_ids:4 nr_node_ids:1
[ 0.000000] percpu: Embedded 35 pages/cpu @ffff880482c00000 s103640 r8192 d31528 u524288
[ 0.000000] pcpu-alloc: s103640 r8192 d31528 u524288 alloc=1*2097152
[ 0.000000] pcpu-alloc: [0] 0 1 2 3
[ 0.000000] Built 1 zonelists in Node order, mobility grouping on. Total pages: 4052985
[ 0.000000] Policy zone: Normal
[ 0.000000] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-linux root=UUID=6d22f373-b455-4a50-a80f-fac7aad2f8e3 rw quiet
[ 0.000000] PID hash table entries: 4096 (order: 3, 32768 bytes)
[ 0.000000] Calgary: detecting Calgary via BIOS EBDA area
[ 0.000000] Calgary: Unable to locate Rio Grande table in EBDA - bailing!
[ 0.000000] Memory: 16123092K/16469368K available (6350K kernel code, 1091K rwdata, 1980K rodata, 1292K init, 1032K bss, 346276K reserved, 0K cma-reserved)
[ 0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=4, Nodes=1
[ 0.000000] Preemptible hierarchical RCU implementation.
[ 0.000000] Build-time adjustment of leaf fanout to 64.
[ 0.000000] RCU restricting CPUs from NR_CPUS=128 to nr_cpu_ids=4.
[ 0.000000] RCU: Adjusting geometry for rcu_fanout_leaf=64, nr_cpu_ids=4
[ 0.000000] NR_IRQS:8448 nr_irqs:1024 16
[ 0.000000] spurious 8259A interrupt: IRQ7.
[ 0.000000] Console: colour dummy device 80x25
[ 0.000000] console [tty0] enabled
[ 0.000000] clocksource: hpet: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 79635855245 ns
[ 0.000000] hpet clockevent registered
[ 0.000000] tsc: Detected 2600.000 MHz processor
[ 0.000022] Calibrating delay loop (skipped), value calculated using timer frequency.. 5186.00 BogoMIPS (lpj=8640000)
[ 0.000024] pid_max: default: 32768 minimum: 301
[ 0.000030] ACPI: Core revision 20160930
[ 0.027417] ACPI: 10 ACPI AML tables successfully acquired and loaded
[ 0.027435] Security Framework initialized
[ 0.027436] Yama: becoming mindful.
[ 0.028015] Dentry cache hash table entries: 2097152 (order: 12, 16777216 bytes)
[ 0.030309] Inode-cache hash table entries: 1048576 (order: 11, 8388608 bytes)
[ 0.031292] Mount-cache hash table entries: 32768 (order: 6, 262144 bytes)
[ 0.031302] Mountpoint-cache hash table entries: 32768 (order: 6, 262144 bytes)
[ 0.031495] CPU: Physical Processor ID: 0
[ 0.031495] CPU: Processor Core ID: 0
[ 0.031498] ENERGY_PERF_BIAS: Set to 'normal', was 'performance'
[ 0.031498] ENERGY_PERF_BIAS: View and update with x86_energy_perf_policy(8)
[ 0.031502] mce: CPU supports 8 MCE banks
[ 0.031509] CPU0: Thermal monitoring enabled (TM1)
[ 0.031520] process: using mwait in idle threads
[ 0.031522] Last level iTLB entries: 4KB 64, 2MB 8, 4MB 8
[ 0.031522] Last level dTLB entries: 4KB 64, 2MB 0, 4MB 0, 1GB 4
[ 0.031604] Freeing SMP alternatives memory: 24K
[ 0.032432] ftrace: allocating 25113 entries in 99 pages
[ 0.041499] smpboot: Max logical packages: 2
[ 0.041505] DMAR: Host address width 39
[ 0.041506] DMAR: DRHD base: 0x000000fed90000 flags: 0x0
[ 0.041509] DMAR: dmar0: reg_base_addr fed90000 ver 1:0 cap 1c0000c40660462 ecap 7e3ff0505e
[ 0.041510] DMAR: DRHD base: 0x000000fed91000 flags: 0x1
[ 0.041513] DMAR: dmar1: reg_base_addr fed91000 ver 1:0 cap d2008c40660462 ecap f050da
[ 0.041513] DMAR: RMRR base: 0x0000007758a000 end: 0x000000775a9fff
[ 0.041514] DMAR: RMRR base: 0x00000079800000 end: 0x0000007bffffff
[ 0.041515] DMAR: ANDD device: 1 name: \_SB.PCI0.I2C0
[ 0.041515] DMAR: ANDD device: 2 name: \_SB.PCI0.I2C1
[ 0.041516] DMAR-IR: IOAPIC id 2 under DRHD base 0xfed91000 IOMMU 1
[ 0.041517] DMAR-IR: HPET id 0 under DRHD base 0xfed91000
[ 0.041517] DMAR-IR: x2apic is disabled because BIOS sets x2apic opt out bit.
[ 0.041518] DMAR-IR: Use 'intremap=no_x2apic_optout' to override the BIOS setting.
[ 0.043994] DMAR-IR: Enabled IRQ remapping in xapic mode
[ 0.043994] x2apic: IRQ remapping doesn't support X2APIC mode
[ 0.047974] ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1
[ 0.080984] TSC deadline timer enabled
[ 0.080989] smpboot: CPU0: Intel(R) Core(TM) i7-6500U CPU @ 2.50GHz (family: 0x6, model: 0x4e, stepping: 0x3)
[ 0.091027] Performance Events: PEBS fmt3+, Skylake events, 32-deep LBR, full-width counters, Intel PMU driver.
[ 0.091081] ... version: 4
[ 0.091082] ... bit width: 48
[ 0.091082] ... generic registers: 4
[ 0.091082] ... value mask: 0000ffffffffffff
[ 0.091083] ... max period: 00007fffffffffff
[ 0.091083] ... fixed-purpose events: 3
[ 0.091083] ... event mask: 000000070000000f
[ 0.114503] NMI watchdog: enabled on all CPUs, permanently consumes one hw-PMU counter.
[ 0.121101] smp: Bringing up secondary CPUs ...
[ 0.147866] x86: Booting SMP configuration:
[ 0.147867] .... node #0, CPUs: #1 #2 #3
[ 0.451389] smp: Brought up 1 node, 4 CPUs
[ 0.451391] smpboot: Total of 4 processors activated (20747.59 BogoMIPS)
[ 0.455162] devtmpfs: initialized
[ 0.455202] x86/mm: Memory block size: 128MB
[ 0.457347] PM: Registering ACPI NVS region [mem 0x6a3c3000-0x6a3c3fff] (4096 bytes)
[ 0.457348] PM: Registering ACPI NVS region [mem 0x77628000-0x77f98fff] (9900032 bytes)
[ 0.457484] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 6370867519511994 ns
[ 0.457490] futex hash table entries: 1024 (order: 4, 65536 bytes)
[ 0.457524] pinctrl core: initialized pinctrl subsystem
[ 0.457637] RTC time: 12:10:11, date: 03/23/17
[ 0.458492] NET: Registered protocol family 16
[ 0.471504] cpuidle: using governor ladder
[ 0.488197] cpuidle: using governor menu
[ 0.488198] PCCT header not found.
[ 0.488222] Simple Boot Flag at 0x47 set to 0x80
[ 0.488243] ACPI FADT declares the system doesn't support PCIe ASPM, so disable it
[ 0.488244] ACPI: bus type PCI registered
[ 0.488245] acpiphp: ACPI Hot Plug PCI Controller Driver version: 0.5
[ 0.488293] PCI: MMCONFIG for domain 0000 [bus 00-ff] at [mem 0xe0000000-0xefffffff] (base 0xe0000000)
[ 0.488294] PCI: MMCONFIG at [mem 0xe0000000-0xefffffff] reserved in E820
[ 0.488304] PCI: Using configuration type 1 for base access
[ 0.488309] dmi type 0xB1 record - unknown flag
[ 0.501637] HugeTLB registered 1 GB page size, pre-allocated 0 pages
[ 0.501638] HugeTLB registered 2 MB page size, pre-allocated 0 pages
[ 0.501800] ACPI: Added _OSI(Module Device)
[ 0.501801] ACPI: Added _OSI(Processor Device)
[ 0.501801] ACPI: Added _OSI(3.0 _SCP Extensions)
[ 0.501802] ACPI: Added _OSI(Processor Aggregator Device)
[ 0.502865] ACPI: Executed 21 blocks of module-level executable AML code
[ 0.512100] ACPI: [Firmware Bug]: BIOS _OSI(Linux) query ignored
[ 0.521017] ACPI: Dynamic OEM Table Load:
[ 0.521023] ACPI: SSDT 0xFFFF88047019A000 000660 (v02 PmRef Cpu0Ist 00003000 INTL 20120913)
[ 0.521259] ACPI: \_PR_.CPU0: _OSC native thermal LVT Acked
[ 0.522411] ACPI: Dynamic OEM Table Load:
[ 0.522416] ACPI: SSDT 0xFFFF880470192400 00037F (v02 PmRef Cpu0Cst 00003001 INTL 20120913)
[ 0.523199] ACPI: Dynamic OEM Table Load:
[ 0.523203] ACPI: SSDT 0xFFFF88047019E800 0005AA (v02 PmRef ApIst 00003000 INTL 20120913)
[ 0.523666] ACPI: Dynamic OEM Table Load:
[ 0.523669] ACPI: SSDT 0xFFFF880470106E00 000119 (v02 PmRef ApCst 00003000 INTL 20120913)
[ 0.525567] ACPI : EC: EC started
[ 0.579711] ACPI: \_SB_.PCI0.LPCB.ECDV: Used as first EC
[ 0.579713] ACPI: \_SB_.PCI0.LPCB.ECDV: GPE=0x45, EC_CMD/EC_SC=0x934, EC_DATA=0x930
[ 0.579714] ACPI: \_SB_.PCI0.LPCB.ECDV: Used as boot DSDT EC to handle transactions
[ 0.579714] ACPI: Interpreter enabled
[ 0.579754] ACPI: (supports S0 S3 S4 S5)
[ 0.579754] ACPI: Using IOAPIC for interrupt routing
[ 0.579787] PCI: Using host bridge windows from ACPI; if necessary, use "pci=nocrs" and report a bug
[ 0.592219] ACPI: Power Resource [PG00] (on)
[ 0.592535] ACPI: Power Resource [PG01] (on)
[ 0.592833] ACPI: Power Resource [PG02] (on)
[ 0.594105] ACPI: Power Resource [WRST] (off)
[ 0.594413] ACPI: Power Resource [WRST] (off)
[ 0.594719] ACPI: Power Resource [WRST] (off)
[ 0.595031] ACPI: Power Resource [WRST] (off)
[ 0.595342] ACPI: Power Resource [WRST] (off)
[ 0.595387] ACPI: Power Resource [PC09] (on)
[ 0.596396] ACPI: Power Resource [WRST] (off)
[ 0.596700] ACPI: Power Resource [WRST] (off)
[ 0.597002] ACPI: Power Resource [WRST] (off)
[ 0.597440] ACPI: Power Resource [WRST] (off)
[ 0.597754] ACPI: Power Resource [WRST] (off)
[ 0.598056] ACPI: Power Resource [WRST] (off)
[ 0.598357] ACPI: Power Resource [WRST] (off)
[ 0.598673] ACPI: Power Resource [WRST] (off)
[ 0.598979] ACPI: Power Resource [WRST] (off)
[ 0.599283] ACPI: Power Resource [WRST] (off)
[ 0.599587] ACPI: Power Resource [WRST] (off)
[ 0.599892] ACPI: Power Resource [WRST] (off)
[ 0.600193] ACPI: Power Resource [WRST] (off)
[ 0.600496] ACPI: Power Resource [WRST] (off)
[ 0.637043] ACPI: Power Resource [FN00] (off)
[ 0.637106] ACPI: Power Resource [FN01] (off)
[ 0.637167] ACPI: Power Resource [FN02] (off)
[ 0.637226] ACPI: Power Resource [FN03] (off)
[ 0.637285] ACPI: Power Resource [FN04] (off)
[ 0.638377] ACPI: PCI Root Bridge [PCI0] (domain 0000 [bus 00-fe])
[ 0.638381] acpi PNP0A08:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
[ 0.638410] acpi PNP0A08:00: _OSC failed (AE_ERROR); disabling ASPM
[ 0.639017] PCI host bridge to bus 0000:00
[ 0.639019] pci_bus 0000:00: root bus resource [io 0x0000-0x0cf7 window]
[ 0.639019] pci_bus 0000:00: root bus resource [io 0x0d00-0xffff window]
[ 0.639020] pci_bus 0000:00: root bus resource [mem 0x000a0000-0x000bffff window]
[ 0.639021] pci_bus 0000:00: root bus resource [mem 0x7c000000-0xdfffffff window]
[ 0.639022] pci_bus 0000:00: root bus resource [mem 0xfd000000-0xfe7fffff window]
[ 0.639023] pci_bus 0000:00: root bus resource [bus 00-fe]
[ 0.639029] pci 0000:00:00.0: [8086:1904] type 00 class 0x060000
[ 0.639137] pci 0000:00:02.0: [8086:1916] type 00 class 0x030000
[ 0.639145] pci 0000:00:02.0: reg 0x10: [mem 0xd4000000-0xd4ffffff 64bit]
[ 0.639150] pci 0000:00:02.0: reg 0x18: [mem 0xb0000000-0xbfffffff 64bit pref]
[ 0.639154] pci 0000:00:02.0: reg 0x20: [io 0xf000-0xf03f]
[ 0.639327] pci 0000:00:14.0: [8086:9d2f] type 00 class 0x0c0330
[ 0.639346] pci 0000:00:14.0: reg 0x10: [mem 0xd5310000-0xd531ffff 64bit]
[ 0.639415] pci 0000:00:14.0: PME# supported from D3hot D3cold
[ 0.639513] pci 0000:00:14.0: System wakeup disabled by ACPI
[ 0.639546] pci 0000:00:14.2: [8086:9d31] type 00 class 0x118000
[ 0.639564] pci 0000:00:14.2: reg 0x10: [mem 0xd5330000-0xd5330fff 64bit]
[ 0.639805] pci 0000:00:15.0: [8086:9d60] type 00 class 0x118000
[ 0.640013] pci 0000:00:15.0: reg 0x10: [mem 0xd532f000-0xd532ffff 64bit]
[ 0.640963] pci 0000:00:15.1: [8086:9d61] type 00 class 0x118000
[ 0.641171] pci 0000:00:15.1: reg 0x10: [mem 0xd532e000-0xd532efff 64bit]
[ 0.642067] pci 0000:00:16.0: [8086:9d3a] type 00 class 0x078000
[ 0.642100] pci 0000:00:16.0: reg 0x10: [mem 0xd532d000-0xd532dfff 64bit]
[ 0.642219] pci 0000:00:16.0: PME# supported from D3hot
[ 0.642352] pci 0000:00:17.0: [8086:9d03] type 00 class 0x010601
[ 0.642367] pci 0000:00:17.0: reg 0x10: [mem 0xd5328000-0xd5329fff]
[ 0.642375] pci 0000:00:17.0: reg 0x14: [mem 0xd532c000-0xd532c0ff]
[ 0.642382] pci 0000:00:17.0: reg 0x18: [io 0xf090-0xf097]
[ 0.642390] pci 0000:00:17.0: reg 0x1c: [io 0xf080-0xf083]
[ 0.642397] pci 0000:00:17.0: reg 0x20: [io 0xf060-0xf07f]
[ 0.642405] pci 0000:00:17.0: reg 0x24: [mem 0xd532b000-0xd532b7ff]
[ 0.642448] pci 0000:00:17.0: PME# supported from D3hot
[ 0.642576] pci 0000:00:1c.0: [8086:9d10] type 01 class 0x060400
[ 0.642641] pci 0000:00:1c.0: PME# supported from D0 D3hot D3cold
[ 0.642753] pci 0000:00:1c.0: System wakeup disabled by ACPI
[ 0.642793] pci 0000:00:1c.4: [8086:9d14] type 01 class 0x060400
[ 0.642855] pci 0000:00:1c.4: PME# supported from D0 D3hot D3cold
[ 0.642963] pci 0000:00:1c.4: System wakeup disabled by ACPI
[ 0.642993] pci 0000:00:1c.5: [8086:9d15] type 01 class 0x060400
[ 0.643055] pci 0000:00:1c.5: PME# supported from D0 D3hot D3cold
[ 0.643162] pci 0000:00:1c.5: System wakeup disabled by ACPI
[ 0.643204] pci 0000:00:1f.0: [8086:9d48] type 00 class 0x060100
[ 0.643414] pci 0000:00:1f.2: [8086:9d21] type 00 class 0x058000
[ 0.643425] pci 0000:00:1f.2: reg 0x10: [mem 0xd5324000-0xd5327fff]
[ 0.643589] pci 0000:00:1f.3: [8086:9d70] type 00 class 0x040300
[ 0.643613] pci 0000:00:1f.3: reg 0x10: [mem 0xd5320000-0xd5323fff 64bit]
[ 0.643647] pci 0000:00:1f.3: reg 0x20: [mem 0xd5300000-0xd530ffff 64bit]
[ 0.643699] pci 0000:00:1f.3: PME# supported from D3hot D3cold
[ 0.643848] pci 0000:00:1f.3: System wakeup disabled by ACPI
[ 0.643883] pci 0000:00:1f.4: [8086:9d23] type 00 class 0x0c0500
[ 0.643929] pci 0000:00:1f.4: reg 0x10: [mem 0xd532a000-0xd532a0ff 64bit]
[ 0.643998] pci 0000:00:1f.4: reg 0x20: [io 0xf040-0xf05f]
[ 0.644233] pci 0000:01:00.0: [10de:1346] type 00 class 0x030200
[ 0.644247] pci 0000:01:00.0: reg 0x10: [mem 0xd2000000-0xd2ffffff]
[ 0.644259] pci 0000:01:00.0: reg 0x14: [mem 0xc0000000-0xcfffffff 64bit pref]
[ 0.644271] pci 0000:01:00.0: reg 0x1c: [mem 0xd0000000-0xd1ffffff 64bit pref]
[ 0.644279] pci 0000:01:00.0: reg 0x24: [io 0xe000-0xe07f]
[ 0.644287] pci 0000:01:00.0: reg 0x30: [mem 0xd3000000-0xd307ffff pref]
[ 0.652010] pci 0000:00:1c.0: PCI bridge to [bus 01]
[ 0.652013] pci 0000:00:1c.0: bridge window [io 0xe000-0xefff]
[ 0.652015] pci 0000:00:1c.0: bridge window [mem 0xc0000000-0xd30fffff]
[ 0.652237] pci 0000:02:00.0: [168c:003e] type 00 class 0x028000
[ 0.652281] pci 0000:02:00.0: reg 0x10: [mem 0xd5000000-0xd51fffff 64bit]
[ 0.652613] pci 0000:02:00.0: PME# supported from D0 D3hot D3cold
[ 0.652742] pci 0000:02:00.0: System wakeup disabled by ACPI
[ 0.662163] pci 0000:00:1c.4: PCI bridge to [bus 02]
[ 0.662167] pci 0000:00:1c.4: bridge window [mem 0xd5000000-0xd51fffff]
[ 0.662257] pci 0000:03:00.0: [10ec:8136] type 00 class 0x020000
[ 0.662280] pci 0000:03:00.0: reg 0x10: [io 0xd000-0xd0ff]
[ 0.662311] pci 0000:03:00.0: reg 0x18: [mem 0xd5204000-0xd5204fff 64bit]
[ 0.662333] pci 0000:03:00.0: reg 0x20: [mem 0xd5200000-0xd5203fff 64bit pref]
[ 0.662434] pci 0000:03:00.0: supports D1 D2
[ 0.662435] pci 0000:03:00.0: PME# supported from D0 D1 D2 D3hot D3cold
[ 0.662531] pci 0000:03:00.0: System wakeup disabled by ACPI
[ 0.672048] pci 0000:00:1c.5: PCI bridge to [bus 03]
[ 0.672051] pci 0000:00:1c.5: bridge window [io 0xd000-0xdfff]
[ 0.672053] pci 0000:00:1c.5: bridge window [mem 0xd5200000-0xd52fffff]
[ 0.675223] ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 6 10 *11 12 14 15)
[ 0.675266] ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 6 *10 11 12 14 15)
[ 0.675307] ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 5 6 10 *11 12 14 15)
[ 0.675350] ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 5 6 10 *11 12 14 15)
[ 0.675395] ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 5 6 10 *11 12 14 15)
[ 0.675435] ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 5 6 10 *11 12 14 15)
[ 0.675475] ACPI: PCI Interrupt Link [LNKG] (IRQs 3 4 5 6 10 *11 12 14 15)
[ 0.675516] ACPI: PCI Interrupt Link [LNKH] (IRQs 3 4 5 6 10 *11 12 14 15)
[ 0.689781] ACPI: Enabled 6 GPEs in block 00 to 7F
[ 0.689895] ACPI : EC: event unblocked
[ 0.689918] ACPI: \_SB_.PCI0.LPCB.ECDV: GPE=0x45, EC_CMD/EC_SC=0x934, EC_DATA=0x930
[ 0.689919] ACPI: \_SB_.PCI0.LPCB.ECDV: Used as boot DSDT EC to handle transactions and events
[ 0.690161] pci 0000:00:02.0: vgaarb: setting as boot VGA device
[ 0.690162] pci 0000:00:02.0: vgaarb: VGA device added: decodes=io+mem,owns=io+mem,locks=none
[ 0.690165] pci 0000:00:02.0: vgaarb: bridge control possible
[ 0.690166] vgaarb: loaded
[ 0.690396] PCI: Using ACPI for IRQ routing
[ 0.719833] PCI: pci_cache_line_size set to 64 bytes
[ 0.720197] e820: reserve RAM buffer [mem 0x0009c800-0x0009ffff]
[ 0.720198] e820: reserve RAM buffer [mem 0x6a3c3000-0x6bffffff]
[ 0.720198] e820: reserve RAM buffer [mem 0x483000000-0x483ffffff]
[ 0.720261] NetLabel: Initializing
[ 0.720261] NetLabel: domain hash size = 128
[ 0.720261] NetLabel: protocols = UNLABELED CIPSOv4 CALIPSO
[ 0.720271] NetLabel: unlabeled traffic allowed by default
[ 0.720339] hpet0: at MMIO 0xfed00000, IRQs 2, 8, 0, 0, 0, 0, 0, 0
[ 0.720343] hpet0: 8 comparators, 64-bit 24.000000 MHz counter
[ 0.722381] clocksource: Switched to clocksource hpet
[ 0.726704] VFS: Disk quotas dquot_6.6.0
[ 0.726715] VFS: Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
[ 0.726781] pnp: PnP ACPI init
[ 0.726960] system 00:00: [io 0x0680-0x069f] has been reserved
[ 0.726961] system 00:00: [io 0xffff] has been reserved
[ 0.726962] system 00:00: [io 0xffff] has been reserved
[ 0.726963] system 00:00: [io 0xffff] has been reserved
[ 0.726963] system 00:00: [io 0x1800-0x18fe] has been reserved
[ 0.726964] system 00:00: [io 0x164e-0x164f] has been reserved
[ 0.726966] system 00:00: Plug and Play ACPI device, IDs PNP0c02 (active)
[ 0.727042] pnp 00:01: Plug and Play ACPI device, IDs PNP0b00 (active)
[ 0.727068] system 00:02: [io 0x1854-0x1857] has been reserved
[ 0.727069] system 00:02: Plug and Play ACPI device, IDs INT3f0d PNP0c02 (active)
[ 0.727091] pnp 00:03: Plug and Play ACPI device, IDs PNP0303 (active)
[ 0.727106] pnp 00:04: Plug and Play ACPI device, IDs DLLb70a PNP0f13 (active)
[ 0.727271] system 00:05: [mem 0xfed10000-0xfed17fff] has been reserved
[ 0.727272] system 00:05: [mem 0xfed18000-0xfed18fff] has been reserved
[ 0.727273] system 00:05: [mem 0xfed19000-0xfed19fff] has been reserved
[ 0.727274] system 00:05: [mem 0xe0000000-0xefffffff] has been reserved
[ 0.727275] system 00:05: [mem 0xfed20000-0xfed3ffff] has been reserved
[ 0.727275] system 00:05: [mem 0xfed90000-0xfed93fff] could not be reserved
[ 0.727276] system 00:05: [mem 0xfed45000-0xfed8ffff] has been reserved
[ 0.727277] system 00:05: [mem 0xff000000-0xffffffff] has been reserved
[ 0.727278] system 00:05: [mem 0xfee00000-0xfeefffff] could not be reserved
[ 0.727279] system 00:05: [mem 0xdffe0000-0xdfffffff] has been reserved
[ 0.727280] system 00:05: Plug and Play ACPI device, IDs PNP0c02 (active)
[ 0.727311] system 00:06: [mem 0xfd000000-0xfdabffff] has been reserved
[ 0.727312] system 00:06: [mem 0xfdad0000-0xfdadffff] has been reserved
[ 0.727313] system 00:06: [mem 0xfdb00000-0xfdffffff] has been reserved
[ 0.727314] system 00:06: [mem 0xfe000000-0xfe01ffff] could not be reserved
[ 0.727314] system 00:06: [mem 0xfe036000-0xfe03bfff] has been reserved
[ 0.727315] system 00:06: [mem 0xfe03d000-0xfe3fffff] has been reserved
[ 0.727316] system 00:06: [mem 0xfe410000-0xfe7fffff] has been reserved
[ 0.727317] system 00:06: Plug and Play ACPI device, IDs PNP0c02 (active)
[ 0.728127] system 00:07: [mem 0xfe029000-0xfe029fff] has been reserved
[ 0.728128] system 00:07: [mem 0xfe028000-0xfe028fff] has been reserved
[ 0.728129] system 00:07: Plug and Play ACPI device, IDs PNP0c02 (active)
[ 0.729575] pnp: PnP ACPI: found 8 devices
[ 0.736635] clocksource: acpi_pm: mask: 0xffffff max_cycles: 0xffffff, max_idle_ns: 2085701024 ns
[ 0.736655] pci 0000:00:1c.0: PCI bridge to [bus 01]
[ 0.736657] pci 0000:00:1c.0: bridge window [io 0xe000-0xefff]
[ 0.736660] pci 0000:00:1c.0: bridge window [mem 0xc0000000-0xd30fffff]
[ 0.736665] pci 0000:00:1c.4: PCI bridge to [bus 02]
[ 0.736668] pci 0000:00:1c.4: bridge window [mem 0xd5000000-0xd51fffff]
[ 0.736673] pci 0000:00:1c.5: PCI bridge to [bus 03]
[ 0.736674] pci 0000:00:1c.5: bridge window [io 0xd000-0xdfff]
[ 0.736677] pci 0000:00:1c.5: bridge window [mem 0xd5200000-0xd52fffff]
[ 0.736682] pci_bus 0000:00: resource 4 [io 0x0000-0x0cf7 window]
[ 0.736683] pci_bus 0000:00: resource 5 [io 0x0d00-0xffff window]
[ 0.736684] pci_bus 0000:00: resource 6 [mem 0x000a0000-0x000bffff window]
[ 0.736685] pci_bus 0000:00: resource 7 [mem 0x7c000000-0xdfffffff window]
[ 0.736685] pci_bus 0000:00: resource 8 [mem 0xfd000000-0xfe7fffff window]
[ 0.736686] pci_bus 0000:01: resource 0 [io 0xe000-0xefff]
[ 0.736687] pci_bus 0000:01: resource 1 [mem 0xc0000000-0xd30fffff]
[ 0.736688] pci_bus 0000:02: resource 1 [mem 0xd5000000-0xd51fffff]
[ 0.736688] pci_bus 0000:03: resource 0 [io 0xd000-0xdfff]
[ 0.736689] pci_bus 0000:03: resource 1 [mem 0xd5200000-0xd52fffff]
[ 0.736779] NET: Registered protocol family 2
[ 0.736899] TCP established hash table entries: 131072 (order: 8, 1048576 bytes)
[ 0.737044] TCP bind hash table entries: 65536 (order: 8, 1048576 bytes)
[ 0.737133] TCP: Hash tables configured (established 131072 bind 65536)
[ 0.737151] UDP hash table entries: 8192 (order: 6, 262144 bytes)
[ 0.737181] UDP-Lite hash table entries: 8192 (order: 6, 262144 bytes)
[ 0.737223] NET: Registered protocol family 1
[ 0.737233] pci 0000:00:02.0: Video device with shadowed ROM at [mem 0x000c0000-0x000dffff]
[ 0.738008] PCI: CLS 0 bytes, default 64
[ 0.738038] Unpacking initramfs...
[ 0.807737] Freeing initrd memory: 5776K
[ 0.807759] DMAR: ACPI device "device:65" under DMAR at fed91000 as 00:15.0
[ 0.807761] DMAR: ACPI device "device:66" under DMAR at fed91000 as 00:15.1
[ 0.807770] PCI-DMA: Using software bounce buffering for IO (SWIOTLB)
[ 0.807771] software IO TLB [mem 0x663c3000-0x6a3c3000] (64MB) mapped at [ffff8800663c3000-ffff88006a3c2fff]
[ 0.807908] clocksource: tsc: mask: 0xffffffffffffffff max_cycles: 0x255cb6cc5db, max_idle_ns: 440795203504 ns
[ 0.808040] Scanning for low memory corruption every 60 seconds
[ 0.808480] Initialise system trusted keyrings
[ 0.808603] workingset: timestamp_bits=40 max_order=22 bucket_order=0
[ 0.809638] zbud: loaded
[ 0.810726] Key type asymmetric registered
[ 0.810753] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 249)
[ 0.810830] io scheduler noop registered
[ 0.810830] io scheduler deadline registered
[ 0.810848] io scheduler cfq registered (default)
[ 0.811374] vesafb: mode is 1366x768x32, linelength=5504, pages=0
[ 0.811374] vesafb: scrolling: redraw
[ 0.811375] vesafb: Truecolor: size=8:8:8:8, shift=24:16:8:0
[ 0.811381] vesafb: framebuffer at 0xb0000000, mapped to 0xffffc90002000000, using 4160k, total 4160k
[ 0.883856] Console: switching to colour frame buffer device 170x48
[ 0.955960] fb0: VESA VGA frame buffer device
[ 0.955969] intel_idle: MWAIT substates: 0x11142120
[ 0.955970] intel_idle: v0.4.1 model 0x4E
[ 0.956186] intel_idle: lapic_timer_reliable_states 0xffffffff
[ 0.956276] GHES: HEST is not enabled!
[ 0.956336] Serial: 8250/16550 driver, 4 ports, IRQ sharing enabled
[ 0.956756] Linux agpgart interface v0.103
[ 0.957031] rtc_cmos 00:01: RTC can wake from S4
[ 0.957413] rtc_cmos 00:01: rtc core: registered rtc_cmos as rtc0
[ 0.957493] rtc_cmos 00:01: alarms up to one month, y3k, 242 bytes nvram, hpet irqs
[ 0.957498] intel_pstate: Intel P-state driver initializing
[ 0.957717] intel_pstate: HWP enabled
[ 0.957869] ledtrig-cpu: registered to indicate activity on CPUs
[ 0.958065] NET: Registered protocol family 10
[ 0.960940] Segment Routing with IPv6
[ 0.960951] NET: Registered protocol family 17
[ 0.961191] microcode: sig=0x406e3, pf=0x80, revision=0x8a
[ 0.961229] microcode: Microcode Update Driver: v2.2.
[ 0.961343] registered taskstats version 1
[ 0.961348] Loading compiled-in X.509 certificates
[ 0.961357] zswap: loaded using pool lzo/zbud
[ 0.962434] Magic number: 9:597:178
[ 0.962469] acpi device:0e: hash matches
[ 0.962483] platform: hash matches
[ 0.962607] rtc_cmos 00:01: setting system clock to 2017-03-23 12:10:12 UTC (1490271012)
[ 0.962635] PM: Hibernation image not present or could not be loaded.
[ 0.963304] Freeing unused kernel memory: 1292K
[ 0.963304] Write protecting the kernel read-only data: 10240k
[ 0.963633] Freeing unused kernel memory: 1828K
[ 0.963744] Freeing unused kernel memory: 68K
[ 0.968845] random: systemd-tmpfile: uninitialized urandom read (16 bytes read)
[ 0.970242] random: systemd-udevd: uninitialized urandom read (16 bytes read)
[ 0.970269] random: systemd-udevd: uninitialized urandom read (16 bytes read)
[ 0.970793] random: udevadm: uninitialized urandom read (16 bytes read)
[ 0.970803] random: udevadm: uninitialized urandom read (16 bytes read)
[ 0.972270] random: systemd-udevd: uninitialized urandom read (16 bytes read)
[ 0.972281] random: systemd-udevd: uninitialized urandom read (16 bytes read)
[ 0.972285] random: systemd-udevd: uninitialized urandom read (16 bytes read)
[ 0.972482] random: systemd-udevd: uninitialized urandom read (16 bytes read)
[ 0.972490] random: systemd-udevd: uninitialized urandom read (16 bytes read)
[ 0.994007] i8042: PNP: PS/2 Controller [PNP0303:PS2K,PNP0f13:PS2M] at 0x60,0x64 irq 1,12
[ 0.994342] i8042: Warning: Keylock active
[ 0.995909] serio: i8042 KBD port at 0x60,0x64 irq 1
[ 0.995934] serio: i8042 AUX port at 0x60,0x64 irq 12
[ 1.007984] ACPI: bus type USB registered
[ 1.008004] usbcore: registered new interface driver usbfs
[ 1.008011] usbcore: registered new interface driver hub
[ 1.008029] usbcore: registered new device driver usb
[ 1.008390] SCSI subsystem initialized
[ 1.009135] xhci_hcd 0000:00:14.0: xHCI Host Controller
[ 1.009140] xhci_hcd 0000:00:14.0: new USB bus registered, assigned bus number 1
[ 1.009462] libata version 3.00 loaded.
[ 1.010269] xhci_hcd 0000:00:14.0: hcc params 0x200077c1 hci version 0x100 quirks 0x00109810
[ 1.010274] xhci_hcd 0000:00:14.0: cache line size of 64 is not supported
[ 1.010483] hub 1-0:1.0: USB hub found
[ 1.010512] hub 1-0:1.0: 12 ports detected
[ 1.017806] xhci_hcd 0000:00:14.0: xHCI Host Controller
[ 1.017809] xhci_hcd 0000:00:14.0: new USB bus registered, assigned bus number 2
[ 1.017937] hub 2-0:1.0: USB hub found
[ 1.017955] hub 2-0:1.0: 6 ports detected
[ 1.021549] ahci 0000:00:17.0: version 3.0
[ 1.021713] ahci 0000:00:17.0: SSS flag set, parallel bus scan disabled
[ 1.021747] ahci 0000:00:17.0: AHCI 0001.0301 32 slots 1 ports 6 Gbps 0x1 impl SATA mode
[ 1.021748] ahci 0000:00:17.0: flags: 64bit ncq stag pm led clo only pio slum part deso sadm sds apst
[ 1.021927] scsi host0: ahci
[ 1.021980] ata1: SATA max UDMA/133 abar m2048@0xd532b000 port 0xd532b100 irq 275
[ 1.032907] input: AT Translated Set 2 keyboard as /devices/platform/i8042/serio0/input/input0
[ 1.337509] ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[ 1.392527] usb 1-2: new full-speed USB device number 2 using xhci_hcd
[ 1.418100] ata1.00: ATA-8: TOSHIBA MQ02ABD100H, HEF01D, max UDMA/100
[ 1.418104] ata1.00: 1953525168 sectors, multi 16: LBA48 NCQ (depth 31/32), AA
[ 1.421629] ata1.00: configured for UDMA/100
[ 1.422314] scsi 0:0:0:0: Direct-Access ATA TOSHIBA MQ02ABD1 1D PQ: 0 ANSI: 5
[ 1.462317] sd 0:0:0:0: [sda] 1953525168 512-byte logical blocks: (1.00 TB/932 GiB)
[ 1.462323] sd 0:0:0:0: [sda] 4096-byte physical blocks
[ 1.462371] sd 0:0:0:0: [sda] Write Protect is off
[ 1.462378] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
[ 1.462512] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[ 1.463538] sda: sda1 sda2
[ 1.464460] sd 0:0:0:0: [sda] Attached SCSI disk
[ 1.588157] hidraw: raw HID events driver (C) Jiri Kosina
[ 1.602256] usbcore: registered new interface driver usbhid
[ 1.602260] usbhid: USB HID core driver
[ 1.603744] input: Microsoft Microsoft® Nano Transceiver v2.0 as /devices/pci0000:00/0000:00:14.0/usb1/1-2/1-2:1.0/0003:045E:0745.0001/input/input2
[ 1.659361] hid-generic 0003:045E:0745.0001: input,hidraw0: USB HID v1.11 Keyboard [Microsoft Microsoft® Nano Transceiver v2.0] on usb-0000:00:14.0-2/input0
[ 1.660084] input: Microsoft Microsoft® Nano Transceiver v2.0 as /devices/pci0000:00/0000:00:14.0/usb1/1-2/1-2:1.1/0003:045E:0745.0002/input/input3
[ 1.716031] hid-generic 0003:045E:0745.0002: input,hidraw1: USB HID v1.11 Mouse [Microsoft Microsoft® Nano Transceiver v2.0] on usb-0000:00:14.0-2/input1
[ 1.726555] input: Microsoft Microsoft® Nano Transceiver v2.0 as /devices/pci0000:00/0000:00:14.0/usb1/1-2/1-2:1.2/0003:045E:0745.0003/input/input4
[ 1.755863] usb 1-5: new high-speed USB device number 3 using xhci_hcd
[ 1.782821] hid-generic 0003:045E:0745.0003: input,hiddev0,hidraw2: USB HID v1.11 Device [Microsoft Microsoft® Nano Transceiver v2.0] on usb-0000:00:14.0-2/input2
[ 1.815899] clocksource: Switched to clocksource tsc
[ 1.903233] EXT4-fs (sda2): mounted filesystem with ordered data mode. Opts: (null)
[ 1.908985] random: fast init done
[ 2.118792] systemd[1]: RTC configured in localtime, applying delta of -180 minutes to system time.
[ 2.159008] ip_tables: (C) 2000-2006 Netfilter Core Team
[ 2.187759] systemd[1]: systemd 232 running in system mode. (+PAM -AUDIT -SELINUX -IMA -APPARMOR +SMACK -SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ +LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD +IDN)
[ 2.188038] systemd[1]: Detected architecture x86-64.
[ 2.188367] systemd[1]: Set hostname to <iscaro-arch>.
[ 2.242409] usb 1-6: new high-speed USB device number 4 using xhci_hcd
[ 2.305047] systemd[1]: Listening on udev Control Socket.
[ 2.305132] systemd[1]: Reached target Remote File Systems.
[ 2.305185] systemd[1]: Listening on Device-mapper event daemon FIFOs.
[ 2.306338] systemd[1]: Listening on Process Core Dump Socket.
[ 2.306988] systemd[1]: Created slice System Slice.
[ 2.307230] systemd[1]: Created slice system-getty.slice.
[ 2.307323] systemd[1]: Listening on Journal Socket.
[ 2.359038] systemd-journald[156]: File /var/log/journal/0f5d952157514b2bb9e88d47f5e9b2c9/system.journal corrupted or uncleanly shut down, renaming and replacing.
[ 2.535859] EXT4-fs (sda2): re-mounted. Opts: data=ordered
[ 2.602633] usb 1-8: new full-speed USB device number 5 using xhci_hcd
[ 2.615800] systemd-journald[156]: Received request to flush runtime journal from PID 1
[ 3.099474] random: crng init done
[ 3.291953] FUJITSU Extended Socket Network Device Driver - version 1.2 - Copyright (c) 2015 FUJITSU LIMITED
[ 3.296045] usbcore: registered new interface driver rtsx_usb
[ 3.298049] input: DELL Wireless hotkeys as /devices/virtual/input/input5
[ 3.313300] ACPI: AC Adapter [AC] (on-line)
[ 3.321336] wmi: Mapper loaded
[ 3.330564] input: Lid Switch as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0D:00/input/input6
[ 3.331156] ACPI: Lid Switch [LID0]
[ 3.331208] input: Power Button as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input7
[ 3.331211] ACPI: Power Button [PBTN]
[ 3.331250] input: Sleep Button as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0E:00/input/input8
[ 3.331251] ACPI: Sleep Button [SBTN]
[ 3.331293] input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input9
[ 3.331295] ACPI: Power Button [PWRF]
[ 3.360612] Bluetooth: Core ver 2.22
[ 3.360624] NET: Registered protocol family 31
[ 3.360625] Bluetooth: HCI device and connection manager initialized
[ 3.360627] Bluetooth: HCI socket layer initialized
[ 3.360629] Bluetooth: L2CAP socket layer initialized
[ 3.360633] Bluetooth: SCO socket layer initialized
[ 3.450121] usbcore: registered new interface driver btusb
[ 3.453592] (NULL device *): hwmon_device_register() is deprecated. Please convert the driver to use hwmon_device_register_with_info().
[ 3.455839] thermal LNXTHERM:00: registered as thermal_zone0
[ 3.455840] ACPI: Thermal Zone [THM] (25 C)
[ 3.464067] ACPI: Battery Slot [BAT0] (battery present)
[ 3.464199] thermal LNXTHERM:01: registered as thermal_zone1
[ 3.464199] ACPI: Thermal Zone [TZ00] (28 C)
[ 3.464462] thermal LNXTHERM:02: registered as thermal_zone2
[ 3.464462] ACPI: Thermal Zone [TZ01] (30 C)
[ 3.481568] Bluetooth: HCI UART driver ver 2.3
[ 3.481570] Bluetooth: HCI UART protocol H4 registered
[ 3.481571] Bluetooth: HCI UART protocol BCSP registered
[ 3.481571] Bluetooth: HCI UART protocol LL registered
[ 3.481572] Bluetooth: HCI UART protocol ATH3K registered
[ 3.481573] Bluetooth: HCI UART protocol Three-wire (H5) registered
[ 3.481599] Bluetooth: HCI UART protocol Intel registered
[ 3.481611] Bluetooth: HCI UART protocol Broadcom registered
[ 3.481612] Bluetooth: HCI UART protocol QCA registered
[ 3.481613] Bluetooth: HCI UART protocol AG6XX registered
[ 3.481613] Bluetooth: HCI UART protocol Marvell registered
[ 3.552483] input: PC Speaker as /devices/platform/pcspkr/input/input11
[ 3.615813] intel-lpss 0000:00:15.0: enabling device (0000 -> 0002)
[ 3.618554] idma64 idma64.0: Found Intel integrated DMA 64-bit
[ 3.622112] RAPL PMU: API unit is 2^-32 Joules, 5 fixed counters, 655360 ms ovfl timer
[ 3.622114] RAPL PMU: hw unit of domain pp0-core 2^-14 Joules
[ 3.622114] RAPL PMU: hw unit of domain package 2^-14 Joules
[ 3.622115] RAPL PMU: hw unit of domain dram 2^-14 Joules
[ 3.622116] RAPL PMU: hw unit of domain pp1-gpu 2^-14 Joules
[ 3.622116] RAPL PMU: hw unit of domain psys 2^-14 Joules
[ 3.629084] mousedev: PS/2 mouse device common for all mice
[ 3.635741] intel-lpss 0000:00:15.1: enabling device (0000 -> 0002)
[ 3.636036] idma64 idma64.1: Found Intel integrated DMA 64-bit
[ 3.636250] shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
[ 3.636395] i801_smbus 0000:00:1f.4: SPD Write Disable is set
[ 3.636415] i801_smbus 0000:00:1f.4: SMBus using PCI interrupt
[ 3.636755] AVX2 version of gcm_enc/dec engaged.
[ 3.636756] AES CTR mode by8 optimization enabled
[ 3.644951] compat: loading out-of-tree module taints kernel.
[ 3.645104] Loading modules backported from Linux version wt-2017-02-19-0-g77f6337
[ 3.645104] Backport generated by backports.git backports-20160324-96-gd9a853f
[ 3.668244] ath10k_pci 0000:02:00.0: pci irq msi oper_irq_mode 2 irq_mode 0 reset_mode 0
[ 3.731259] media: Linux media interface: v0.10
[ 3.735941] Linux video capture interface: v2.00
[ 4.260552] (NULL device *): hwmon_device_register() is deprecated. Please convert the driver to use hwmon_device_register_with_info().
[ 4.260680] mei_me 0000:00:16.0: enabling device (0000 -> 0002)
[ 4.272511] dcdbas dcdbas: Dell Systems Management Base Driver (version 5.6.0-3.2)
[ 4.278716] uvcvideo: Found UVC 1.00 device Integrated_Webcam_HD (1bcf:28b0)
[ 4.286856] uvcvideo 1-5:1.0: Entity type for entity Extension 4 was not initialized!
[ 4.286858] uvcvideo 1-5:1.0: Entity type for entity Extension 3 was not initialized!
[ 4.286860] uvcvideo 1-5:1.0: Entity type for entity Processing 2 was not initialized!
[ 4.286861] uvcvideo 1-5:1.0: Entity type for entity Camera 1 was not initialized!
[ 4.286925] input: Integrated_Webcam_HD as /devices/pci0000:00/0000:00:14.0/usb1/1-5/1-5:1.0/input/input12
[ 4.286978] usbcore: registered new interface driver uvcvideo
[ 4.286978] USB Video Class driver (1.1.1)
[ 4.310760] r8169 Gigabit Ethernet driver 2.3LK-NAPI loaded
[ 4.310765] r8169 0000:03:00.0: can't disable ASPM; OS doesn't have ASPM control
[ 4.311213] r8169 0000:03:00.0 eth0: RTL8106e at 0xffffc90001a21000, f4:8e:38:e4:69:36, XID 04900000 IRQ 278
[ 4.438922] ath10k_pci 0000:02:00.0: qca6174 hw3.2 target 0x05030000 chip_id 0x00340aff sub 1028:0310
[ 4.438928] ath10k_pci 0000:02:00.0: kconfig debug 1 debugfs 1 tracing 0 dfs 0 testmode 0
[ 4.440361] ath10k_pci 0000:02:00.0: firmware ver WLAN.RM.4.4-00022-QCARMSWPZ-2 api 5 features wowlan,ignore-otp crc32 4d458559
[ 4.500305] psmouse serio1: synaptics: queried max coordinates: x [..5664], y [..4648]
[ 4.521236] dell_wmi: Detected Dell WMI interface version 1
[ 4.521288] input: Dell WMI hotkeys as /devices/virtual/input/input13
[ 4.529106] psmouse serio1: synaptics: queried min coordinates: x [1278..], y [1206..]
[ 4.535360] intel_rapl: Found RAPL domain package
[ 4.535365] intel_rapl: Found RAPL domain core
[ 4.535366] intel_rapl: Found RAPL domain uncore
[ 4.535366] intel_rapl: Found RAPL domain dram
[ 4.540226] iTCO_vendor_support: vendor-support=0
[ 4.541299] iTCO_wdt: Intel TCO WatchDog Timer Driver v1.11
[ 4.541419] iTCO_wdt: Found a Intel PCH TCO device (Version=4, TCOBASE=0x0400)
[ 4.541515] iTCO_wdt: initialized. heartbeat=30 sec (nowayout=0)
[ 4.552479] r8169 0000:03:00.0 enp3s0: renamed from eth0
[ 4.576989] [drm] Initialized
[ 4.581572] IPv6: ADDRCONF(NETDEV_UP): enp3s0: link is not ready
[ 4.601692] ath10k_pci 0000:02:00.0: board_file api 2 bmi_id N/A crc32 19644295
[ 4.716503] MXM: GUID detected in BIOS
[ 4.716695] ACPI Warning: \_SB.PCI0.GFX0._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20160930/nsarguments-95)
[ 4.716886] checking generic (b0000000 410000) vs hw (c0000000 10000000)
[ 4.716887] checking generic (b0000000 410000) vs hw (d0000000 2000000)
[ 4.716945] nouveau 0000:01:00.0: NVIDIA GM108 (118060a2)
[ 4.736341] nouveau 0000:01:00.0: Invalid PCI ROM header signature: expecting 0xaa55, got 0xfb00
[ 4.737471] nouveau 0000:01:00.0: bios: unable to locate usable image
[ 4.738339] nouveau 0000:01:00.0: bios ctor failed, -22
[ 4.739113] [drm] Memory usable by graphics device = 4096M
[ 4.739114] checking generic (b0000000 410000) vs hw (b0000000 10000000)
[ 4.739115] fb: switching to inteldrmfb from VESA VGA
[ 4.739392] nouveau: probe of 0000:01:00.0 failed with error -22
[ 4.739478] Console: switching to colour dummy device 80x25
[ 4.739946] [drm] Replacing VGA console driver
[ 4.760272] r8169 0000:03:00.0 enp3s0: link down
[ 4.760346] IPv6: ADDRCONF(NETDEV_UP): enp3s0: link is not ready
[ 4.762393] psmouse serio1: synaptics: Advanced gesture mode init failed.
[ 4.762398] psmouse serio1: synaptics: Unable to initialize device.
[ 4.891772] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
[ 4.891773] [drm] Driver supports precise vblank timestamp query.
[ 4.899719] i915 0000:00:02.0: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=io+mem:owns=io+mem
[ 4.904602] [drm] Finished loading i915/skl_dmc_ver1_26.bin (v1.26)
[ 4.912692] [drm] GuC firmware load skipped
[ 4.943522] ACPI: Video Device [GFX0] (multi-head: yes rom: no post: no)
[ 4.944246] input: Video Bus as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/LNXVIDEO:00/input/input14
[ 4.944408] ACPI: Video Device [PEGP] (multi-head: no rom: yes post: no)
[ 4.944446] input: Video Bus as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/device:1b/LNXVIDEO:01/input/input15
[ 4.945117] snd_hda_intel 0000:00:1f.3: bound 0000:00:02.0 (ops i915_audio_component_bind_ops [i915])
[ 4.945122] [drm] Initialized i915 1.6.0 20161121 for 0000:00:02.0 on minor 0
[ 4.954773] fbcon: inteldrmfb (fb0) is primary device
[ 4.976799] input: DLLA70A:00 06CB:7621 Touchpad as /devices/pci0000:00/0000:00:15.0/i2c_designware.0/i2c-1/i2c-DLLA70A:00/0018:06CB:7621.0004/input/input17
[ 4.976896] hid-multitouch 0018:06CB:7621.0004: input,hidraw3: I2C HID v1.00 Mouse [DLLA70A:00 06CB:7621] on i2c-DLLA70A:00
[ 6.085551] Console: switching to colour frame buffer device 170x48
[ 6.120705] i915 0000:00:02.0: fb0: inteldrmfb frame buffer device
[ 6.202957] snd_hda_codec_realtek hdaudioC0D0: autoconfig for ALC3234: line_outs=1 (0x14/0x0/0x0/0x0/0x0) type:speaker
[ 6.202959] snd_hda_codec_realtek hdaudioC0D0: speaker_outs=0 (0x0/0x0/0x0/0x0/0x0)
[ 6.202960] snd_hda_codec_realtek hdaudioC0D0: hp_outs=1 (0x21/0x0/0x0/0x0/0x0)
[ 6.202961] snd_hda_codec_realtek hdaudioC0D0: mono: mono_out=0x0
[ 6.202962] snd_hda_codec_realtek hdaudioC0D0: inputs:
[ 6.202964] snd_hda_codec_realtek hdaudioC0D0: Headset Mic=0x19
[ 6.202965] snd_hda_codec_realtek hdaudioC0D0: Headphone Mic=0x1a
[ 6.202966] snd_hda_codec_realtek hdaudioC0D0: Internal Mic=0x12
[ 6.322664] [drm] RC6 on
[ 6.813017] ath10k_pci 0000:02:00.0: Unknown eventid: 90118
[ 6.813627] ath10k_pci 0000:02:00.0: htt-ver 3.32 wmi-op 4 htt-op 3 cal otp max-sta 32 raw 0 hwcrypto 1
[ 6.890351] ath: EEPROM regdomain: 0x6c
[ 6.890352] ath: EEPROM indicates we should expect a direct regpair map
[ 6.890352] ath: Country alpha2 being used: 00
[ 6.890353] ath: Regpair used: 0x6c
[ 6.894443] ath10k_pci 0000:02:00.0 wlp2s0: renamed from wlan0
[ 6.909070] IPv6: ADDRCONF(NETDEV_UP): wlp2s0: link is not ready
[ 7.235712] input: HDA Digital PCBeep as /devices/pci0000:00/0000:00:1f.3/sound/card0/input22
[ 7.237109] input: HDA Intel PCH Headphone Mic as /devices/pci0000:00/0000:00:1f.3/sound/card0/input23
[ 7.237159] input: HDA Intel PCH HDMI/DP,pcm=3 as /devices/pci0000:00/0000:00:1f.3/sound/card0/input24
[ 7.237206] input: HDA Intel PCH HDMI/DP,pcm=7 as /devices/pci0000:00/0000:00:1f.3/sound/card0/input25
[ 7.237252] input: HDA Intel PCH HDMI/DP,pcm=8 as /devices/pci0000:00/0000:00:1f.3/sound/card0/input26
[ 9.142205] ath10k_pci 0000:02:00.0: Unknown eventid: 90118
[ 9.185269] IPv6: ADDRCONF(NETDEV_UP): wlp2s0: link is not ready
[ 10.429148] input: PS/2 Synaptics TouchPad as /devices/platform/i8042/serio1/input/input10
[ 10.632402] psmouse serio1: Failed to enable mouse on isa0060/serio1
[ 11.487623] ath10k_pci 0000:02:00.0: Unknown eventid: 90118
[ 11.542121] IPv6: ADDRCONF(NETDEV_UP): wlp2s0: link is not ready
[ 11.612555] IPv6: ADDRCONF(NETDEV_UP): wlp2s0: link is not ready
[ 16.470553] IPv6: ADDRCONF(NETDEV_UP): wlp2s0: link is not ready
[ 21.350812] wlp2s0: authenticate with 00:26:86:01:fd:9c
[ 21.408478] wlp2s0: send auth to 00:26:86:01:fd:9c (try 1/3)
[ 21.409457] wlp2s0: authenticated
[ 21.412504] wlp2s0: associate with 00:26:86:01:fd:9c (try 1/3)
[ 21.421142] wlp2s0: RX AssocResp from 00:26:86:01:fd:9c (capab=0x511 status=0 aid=15)
[ 21.423555] wlp2s0: associated
[ 21.423588] IPv6: ADDRCONF(NETDEV_CHANGE): wlp2s0: link becomes ready
[ 29.394577] fuse init (API version 7.26)
[ 4204.623496] usb 1-1: new full-speed USB device number 7 using xhci_hcd
[ 4306.709579] ttyPos:303 2014.10.13_01
[ 4306.709653] ttyPos probe:303 2014.10.13_01,index:0
[ 4306.709839] PosUsb 1-1:1.0: USB POS device now attached to PosUsb--1
[ 4306.709894] usbcore: registered new interface driver PosUsb
[15287.052471] perf: interrupt took too long (2544 > 2500), lowering kernel.perf_event_max_sample_rate to 78600
[17858.169179] ath10k_pci 0000:02:00.0: failed to wake target for write32 of 0x00000895 at 0x0003543c: -110
[17858.214418] ath10k_pci 0000:02:00.0: failed to wake target for read32 at 0x0003a028: -110
[17860.149655] ath10k_pci 0000:02:00.0: failed to wake target for write32 of 0x00000897 at 0x0003543c: -110
[17860.640457] ath10k_pci 0000:02:00.0: failed to wake target for read32 at 0x0003a028: -110
[17860.860532] ath10k_pci 0000:02:00.0: failed to wake target for write32 of 0x00000899 at 0x0003543c: -110
[17861.544337] ath10k_pci 0000:02:00.0: failed to wake target for write32 of 0x0000089b at 0x0003543c: -110
[17861.967021] ath10k_pci 0000:02:00.0: failed to wake target for write32 of 0x0000089d at 0x0003543c: -110
[17863.549225] ath10k_pci 0000:02:00.0: failed to wake target for write32 of 0x0000089f at 0x0003543c: -110
[17863.601510] ath10k_pci 0000:02:00.0: failed to wake target for write32 of 0x000008a1 at 0x0003543c: -110
[17864.455197] ath10k_pci 0000:02:00.0: failed to wake target for write32 of 0x000008a3 at 0x0003543c: -110
[17864.490298] ath10k_pci 0000:02:00.0: failed to wake target for write32 of 0x000008a5 at 0x0003543c: -110
[17864.740990] ath10k_pci 0000:02:00.0: failed to wake target for write32 of 0x000008a7 at 0x0003543c: -110
[17866.114862] ath10k_pci 0000:02:00.0: failed to wake target for write32 of 0x000008a9 at 0x0003543c: -110
[17868.830430] ath10k_pci 0000:02:00.0: failed to wake target for write32 of 0x000008ab at 0x0003543c: -110
[17868.865338] ath10k_pci 0000:02:00.0: failed to wake target for write32 of 0x000008ad at 0x0003543c: -110
[17868.900144] ath10k_pci 0000:02:00.0: failed to wake target for write32 of 0x000008af at 0x0003543c: -110
[17868.935282] ath10k_pci 0000:02:00.0: failed to wake target for write32 of 0x000008b1 at 0x0003543c: -110
[17868.970191] ath10k_pci 0000:02:00.0: failed to wake target for write32 of 0x000008b3 at 0x0003543c: -110
[17869.004982] ath10k_pci 0000:02:00.0: failed to wake target for write32 of 0x000008b5 at 0x0003543c: -110
[17869.051699] ath10k_pci 0000:02:00.0: failed to wake target for write32 of 0x000008b7 at 0x0003543c: -110
[17869.085288] ath10k_pci 0000:02:00.0: failed to wake target for write32 of 0x000008b9 at 0x0003543c: -110
[17869.118922] ath10k_pci 0000:02:00.0: failed to wake target for write32 of 0x000008bb at 0x0003543c: -110
[17869.152613] ath10k_pci 0000:02:00.0: failed to wake target for write32 of 0x000008bd at 0x0003543c: -110
[17873.835296] ath10k_warn: 13 callbacks suppressed
[17873.835299] ath10k_pci 0000:02:00.0: failed to wake target for write32 of 0x000008d5 at 0x0003543c: -110
[17873.870117] ath10k_pci 0000:02:00.0: failed to wake target for write32 of 0x000008d7 at 0x0003543c: -110
[17873.904925] ath10k_pci 0000:02:00.0: failed to wake target for write32 of 0x000008d9 at 0x0003543c: -110
[17873.940975] ath10k_pci 0000:02:00.0: failed to wake target for write32 of 0x000008db at 0x0003543c: -110
[17873.975853] ath10k_pci 0000:02:00.0: failed to wake target for write32 of 0x000008dd at 0x0003543c: -110
[17874.058864] ath10k_pci 0000:02:00.0: failed to wake target for write32 of 0x000008df at 0x0003543c: -110
[17874.093760] ath10k_pci 0000:02:00.0: failed to wake target for write32 of 0x000008e1 at 0x0003543c: -110
[17874.128555] ath10k_pci 0000:02:00.0: failed to wake target for write32 of 0x000008e3 at 0x0003543c: -110
[17874.193940] ath10k_pci 0000:02:00.0: failed to wake target for write32 of 0x000008e5 at 0x0003543c: -110
[17874.228784] ath10k_pci 0000:02:00.0: failed to wake target for write32 of 0x000008e7 at 0x0003543c: -110
[17878.877699] ath10k_warn: 7 callbacks suppressed
[17878.877703] ath10k_pci 0000:02:00.0: failed to wake target for write32 of 0x000008f1 at 0x0003543c: -110
[17878.944655] ath10k_pci 0000:02:00.0: failed to wake target for write32 of 0x000008f3 at 0x0003543c: -110
[17878.979559] ath10k_pci 0000:02:00.0: failed to wake target for write32 of 0x000008f5 at 0x0003543c: -110
[17879.015235] ath10k_pci 0000:02:00.0: failed to wake target for write32 of 0x000008f7 at 0x0003543c: -110
[17879.050059] ath10k_pci 0000:02:00.0: failed to wake target for write32 of 0x000008f9 at 0x0003543c: -110
[17879.084846] ath10k_pci 0000:02:00.0: failed to wake target for write32 of 0x000008fb at 0x0003543c: -110
[17879.168481] ath10k_pci 0000:02:00.0: failed to wake target for write32 of 0x000008fd at 0x0003543c: -110
[17879.203454] ath10k_pci 0000:02:00.0: failed to wake target for write32 of 0x000008ff at 0x0003543c: -110
[17879.268733] ath10k_pci 0000:02:00.0: failed to wake target for write32 of 0x00000901 at 0x0003543c: -110
[17879.303717] ath10k_pci 0000:02:00.0: failed to wake target for write32 of 0x00000903 at 0x0003543c: -110
[17883.916524] ath10k_warn: 8 callbacks suppressed
[17883.916528] ath10k_pci 0000:02:00.0: failed to wake target for write32 of 0x00000915 at 0x0003543c: -110
[17884.017088] ath10k_pci 0000:02:00.0: failed to wake target for write32 of 0x00000917 at 0x0003543c: -110
[17884.050875] ath10k_pci 0000:02:00.0: failed to wake target for write32 of 0x00000919 at 0x0003543c: -110
[17884.084501] ath10k_pci 0000:02:00.0: failed to wake target for write32 of 0x0000091b at 0x0003543c: -110
[17884.124726] ath10k_pci 0000:02:00.0: failed to wake target for write32 of 0x0000091d at 0x0003543c: -110
[17884.159698] ath10k_pci 0000:02:00.0: failed to wake target for write32 of 0x0000091f at 0x0003543c: -110
[17884.238615] ath10k_pci 0000:02:00.0: failed to wake target for write32 of 0x00000921 at 0x0003543c: -110
[17884.273481] ath10k_pci 0000:02:00.0: failed to wake target for write32 of 0x00000923 at 0x0003543c: -110
[17884.343809] ath10k_pci 0000:02:00.0: failed to wake target for write32 of 0x00000925 at 0x0003543c: -110
[17884.378602] ath10k_pci 0000:02:00.0: failed to wake target for write32 of 0x00000927 at 0x0003543c: -110
[17888.952034] ath10k_warn: 5 callbacks suppressed
[17888.952099] ath10k_pci 0000:02:00.0: failed to wake target for write32 of 0x00000933 at 0x0003543c: -110
[17889.084029] ath10k_pci 0000:02:00.0: failed to wake target for write32 of 0x00000935 at 0x0003543c: -110
[17889.123152] ath10k_pci 0000:02:00.0: failed to wake target for write32 of 0x00000937 at 0x0003543c: -110
[17889.156883] ath10k_pci 0000:02:00.0: failed to wake target for write32 of 0x00000939 at 0x0003543c: -110
[17889.197186] ath10k_pci 0000:02:00.0: failed to wake target for write32 of 0x0000093b at 0x0003543c: -110
[17889.232003] ath10k_pci 0000:02:00.0: failed to wake target for write32 of 0x0000093d at 0x0003543c: -110
[17889.311613] ath10k_pci 0000:02:00.0: failed to wake target for write32 of 0x0000093f at 0x0003543c: -110
[17889.346588] ath10k_pci 0000:02:00.0: failed to wake target for write32 of 0x00000941 at 0x0003543c: -110
[17889.417874] ath10k_pci 0000:02:00.0: failed to wake target for write32 of 0x00000943 at 0x0003543c: -110
[17889.452699] ath10k_pci 0000:02:00.0: failed to wake target for write32 of 0x00000945 at 0x0003543c: -110
[17893.990663] ath10k_warn: 5 callbacks suppressed
[17893.990666] ath10k_pci 0000:02:00.0: failed to wake target for write32 of 0x00000951 at 0x0003543c: -110
[17894.123982] ath10k_pci 0000:02:00.0: failed to wake target for write32 of 0x00000953 at 0x0003543c: -110
[17894.195611] ath10k_pci 0000:02:00.0: failed to wake target for write32 of 0x00000955 at 0x0003543c: -110
[17894.229405] ath10k_pci 0000:02:00.0: failed to wake target for write32 of 0x00000957 at 0x0003543c: -110
[17894.271877] ath10k_pci 0000:02:00.0: failed to wake target for write32 of 0x00000959 at 0x0003543c: -110
[17894.306743] ath10k_pci 0000:02:00.0: failed to wake target for write32 of 0x0000095b at 0x0003543c: -110
[17894.386451] ath10k_pci 0000:02:00.0: failed to wake target for write32 of 0x0000095d at 0x0003543c: -110
[17894.421254] ath10k_pci 0000:02:00.0: failed to wake target for write32 of 0x0000095f at 0x0003543c: -110
[17894.487439] ath10k_pci 0000:02:00.0: failed to wake target for write32 of 0x00000961 at 0x0003543c: -110
[17894.522362] ath10k_pci 0000:02:00.0: failed to wake target for write32 of 0x00000963 at 0x0003543c: -110
[17899.029250] ath10k_warn: 5 callbacks suppressed
[17899.029254] ath10k_pci 0000:02:00.0: failed to wake target for write32 of 0x0000096f at 0x0003543c: -110
[17899.163966] ath10k_pci 0000:02:00.0: failed to wake target for write32 of 0x00000971 at 0x0003543c: -110
[17899.268313] ath10k_pci 0000:02:00.0: failed to wake target for write32 of 0x00000973 at 0x0003543c: -110
[17899.302849] ath10k_pci 0000:02:00.0: failed to wake target for write32 of 0x00000975 at 0x0003543c: -110
[17899.343027] ath10k_pci 0000:02:00.0: failed to wake target for write32 of 0x00000977 at 0x0003543c: -110
[17899.376636] ath10k_pci 0000:02:00.0: failed to wake target for write32 of 0x00000979 at 0x0003543c: -110
[17899.460714] ath10k_pci 0000:02:00.0: failed to wake target for write32 of 0x0000097b at 0x0003543c: -110
[17899.495420] ath10k_pci 0000:02:00.0: failed to wake target for write32 of 0x0000097d at 0x0003543c: -110
[17899.560987] ath10k_pci 0000:02:00.0: failed to wake target for write32 of 0x0000097f at 0x0003543c: -110
[17899.595222] ath10k_pci 0000:02:00.0: failed to wake target for write32 of 0x00000981 at 0x0003543c: -110
[-- Attachment #3: Type: text/plain, Size: 146 bytes --]
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: Reporting a bug for QCA6174 802.11ac
2017-03-23 23:11 ` Guilherme Íscaro
@ 2017-03-28 17:45 ` Guilherme Íscaro
2017-03-31 11:12 ` Kalle Valo
0 siblings, 1 reply; 12+ messages in thread
From: Guilherme Íscaro @ 2017-03-28 17:45 UTC (permalink / raw)
To: Ryan Hsu; +Cc: ath10k
[-- Attachment #1: Type: text/plain, Size: 4713 bytes --]
Hello everyone,
I would like to inform that I "fixed" the problem. After my last
email, I cloned the linux repo and started to hack around the driver
source code. By looking at the dmesg output that I provided to you
guys, I noticed that for some reason the board was not being properly
awake ( ath10k_pci_wake_wait() returns ETIMEOUT). I so sick with this
problem that I hardcoded "ar_pci->pci_ps" to false, thus the board
can't sleep now.
Please, send some thoughts.
I attached the patch so you guys can take a look.
Thanks.
2017-03-23 20:11 GMT-03:00 Guilherme Íscaro <cabelitostos@gmail.com>:
> Hello Ryan, thanks for your contact.
>
> My AP is a D-link DMG 6661. I'll try another wifi settings and check
> if it happens and if it happens I'll provide de ftrace logs.
>
> Btw, just after I read your email the bug happened. Here's the full
> dmesg. After the "failed to wake target" problem happens it keeps
> flooding dmesg forever. There are no other error indications.
>
> I guess that the dmesg output will not help us, maybe ftrace will be
> more helpful. Anyway, here's the dmesg...
>
> Thanks for your help
>
> 2017-03-23 19:46 GMT-03:00 Ryan Hsu <ryanhsu@qca.qualcomm.com>:
>> Let's start from the basic, could you provide the ftrace logs and also the AP model you're using? try without security or different phy mode to see if it would behave differently?
>>
>> The last thing is, your previous logs only stuffed with the register access failure logs, can you share a full dmesg logs as well?
>>
>> Ryan
>> ________________________________________
>> From: Guilherme Íscaro <cabelitostos@gmail.com>
>> Sent: Wednesday, March 22, 2017 3:17 PM
>> To: Ryan Hsu
>> Cc: ath10k@lists.infradead.org
>> Subject: Re: Reporting a bug for QCA6174 802.11ac
>>
>> Hi, unfortunately the problem happened with the new drivers and firmware. :[
>> I really don't know what to do anymore.....
>>
>> thanks.
>>
>> 2017-03-22 10:56 GMT-03:00 Guilherme Íscaro <cabelitostos@gmail.com>:
>>> I've installed the new firmware/driver. I'll send a new email in some
>>> days to tell you guys if the new driver/firmware resolved the problem.
>>>
>>> Thanks for the help.
>>>
>>> 2017-03-21 15:58 GMT-03:00 Guilherme Íscaro <cabelitostos@gmail.com>:
>>>> Hello Ryan, Thanks for your response.
>>>>
>>>> My AP is in the same room that I use my notebook, it's right in front
>>>> of me. There's no specific scenario for this failure to happen.
>>>> Sometimes it does not happens for days, but sometimes it happens 3/4
>>>> times in the same day.
>>>> It looks like that there is not specific scenario, sometimes it
>>>> happens while I'm using firefox, sometimes it happens when my laptop
>>>> is "doing nothing". (Was it helpful?)
>>>>
>>>> I'm using WiFi 802.11n, 2.4ghz with AES.
>>>>
>>>> I'll try this new firmware/driver.
>>>>
>>>> Thanks.
>>>>
>>>>
>>>>
>>>> 2017-03-21 15:35 GMT-03:00 Ryan Hsu <ryanhsu@qca.qualcomm.com>:
>>>>> Iscaro,
>>>>>
>>>>> Not sure how exactly the issue and scenario of your usage.
>>>>>
>>>>> e.g how far the AP from you and is there any specific scenario you're seeing the failure open?
>>>>>
>>>>> Also would you mind try to pick up the latest firmware to see if that help?
>>>>> https://github.com/kvalo/ath10k-firmware/tree/master/QCA6174/hw3.0/4.4
>>>>>
>>>>> With the latest firmware, you might also need to get the latest driver backport package.
>>>>> http://buildbot.w1.fi/backports-wireless-testing/
>>>>>
>>>>> Ryan
>>>>>
>>>>>> -----Original Message-----
>>>>>> From: ath10k [mailto:ath10k-bounces@lists.infradead.org] On Behalf Of
>>>>>> Guilherme Íscaro
>>>>>> Sent: Monday, March 20, 2017 08:32 AM
>>>>>> To: ath10k@lists.infradead.org
>>>>>> Subject: Reporting a bug for QCA6174 802.11ac
>>>>>>
>>>>>> Hello everyone, I would like to report a bug for QCA6174.
>>>>>>
>>>>>> I use WiFi everyday, but from time to time I lose my connection. This might be
>>>>>> related to a firmware problem, because after I lose my connection the firmware
>>>>>> keeps flooding dmesg about problems.
>>>>>>
>>>>>> I have this problem since I bought my laptop (which was last year) and I do
>>>>>> regular updates in my system.
>>>>>>
>>>>>> P.S: dmest output attached.
>>>>>>
>>>>>> My system:
>>>>>>
>>>>>> Dist: Arch Linux.
>>>>>> Kernel: 4.10.3-1
>>>>>> Linux-firmware version: 20170309.695f2d6-1 (commit 695f2d6d82173f4e...
>>>>>> from linux-firmware)
>>>>>> Board: 02:00.0 Network controller: Qualcomm Atheros QCA6174 802.11ac
>>>>>> Wireless Network Adapter (rev 32)
>>>>>>
>>>>>>
>>>>>> Please, let me know if I should provide more info.
>>>>>>
>>>>>> Thanks.
[-- Attachment #2: 0001-FIX-BUG.patch --]
[-- Type: text/x-patch, Size: 816 bytes --]
From c3bc3e52998d8b6189da00391570359e17d1d359 Mon Sep 17 00:00:00 2001
From: Guilherme Iscaro <iscaro@profusion.mobi>
Date: Tue, 21 Mar 2017 10:05:40 -0300
Subject: [PATCH] FIX BUG.
---
drivers/net/wireless/ath/ath10k/pci.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/net/wireless/ath/ath10k/pci.c b/drivers/net/wireless/ath/ath10k/pci.c
index b541a1c74488..0da470b0aee4 100644
--- a/drivers/net/wireless/ath/ath10k/pci.c
+++ b/drivers/net/wireless/ath/ath10k/pci.c
@@ -3187,7 +3187,7 @@ static int ath10k_pci_probe(struct pci_dev *pdev,
case QCA6164_2_1_DEVICE_ID:
case QCA6174_2_1_DEVICE_ID:
hw_rev = ATH10K_HW_QCA6174;
- pci_ps = true;
+ pci_ps = false;
pci_soft_reset = ath10k_pci_warm_reset;
pci_hard_reset = ath10k_pci_qca6174_chip_reset;
break;
--
2.12.1
[-- Attachment #3: Type: text/plain, Size: 146 bytes --]
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
^ permalink raw reply related [flat|nested] 12+ messages in thread
* Re: Reporting a bug for QCA6174 802.11ac
2017-03-28 17:45 ` Guilherme Íscaro
@ 2017-03-31 11:12 ` Kalle Valo
2017-03-31 15:11 ` Adrian Chadd
0 siblings, 1 reply; 12+ messages in thread
From: Kalle Valo @ 2017-03-31 11:12 UTC (permalink / raw)
To: Guilherme Íscaro; +Cc: Ryan Hsu, ath10k
Guilherme Íscaro <cabelitostos@gmail.com> writes:
> I would like to inform that I "fixed" the problem. After my last
> email, I cloned the linux repo and started to hack around the driver
> source code. By looking at the dmesg output that I provided to you
> guys, I noticed that for some reason the board was not being properly
> awake ( ath10k_pci_wake_wait() returns ETIMEOUT). I so sick with this
> problem that I hardcoded "ar_pci->pci_ps" to false, thus the board
> can't sleep now.
Sounds like a problem with your PCI bus or the platform/laptop so try
different PCI settings both on BIOS and kernel. I have seen lots of talk
about ASPM, especially with some iwlwifi devices, so you should also
investigate about that.
Please let us know if you find anything, it's always valuable
information. Have fun googling :)
--
Kalle Valo
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: Reporting a bug for QCA6174 802.11ac
2017-03-31 11:12 ` Kalle Valo
@ 2017-03-31 15:11 ` Adrian Chadd
2017-04-05 19:48 ` Guilherme Íscaro
0 siblings, 1 reply; 12+ messages in thread
From: Adrian Chadd @ 2017-03-31 15:11 UTC (permalink / raw)
To: Kalle Valo; +Cc: Guilherme Íscaro, Ryan Hsu, ath10k
hiya,
hm, what's the reference driver do for pci powersave versus aspm? Does
it change any pci config space register settings for allowable sleep
states?
-adrian
On 31 March 2017 at 04:12, Kalle Valo <kvalo@qca.qualcomm.com> wrote:
> Guilherme Íscaro <cabelitostos@gmail.com> writes:
>
>> I would like to inform that I "fixed" the problem. After my last
>> email, I cloned the linux repo and started to hack around the driver
>> source code. By looking at the dmesg output that I provided to you
>> guys, I noticed that for some reason the board was not being properly
>> awake ( ath10k_pci_wake_wait() returns ETIMEOUT). I so sick with this
>> problem that I hardcoded "ar_pci->pci_ps" to false, thus the board
>> can't sleep now.
>
> Sounds like a problem with your PCI bus or the platform/laptop so try
> different PCI settings both on BIOS and kernel. I have seen lots of talk
> about ASPM, especially with some iwlwifi devices, so you should also
> investigate about that.
>
> Please let us know if you find anything, it's always valuable
> information. Have fun googling :)
>
> --
> Kalle Valo
> _______________________________________________
> ath10k mailing list
> ath10k@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/ath10k
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: Reporting a bug for QCA6174 802.11ac
2017-03-31 15:11 ` Adrian Chadd
@ 2017-04-05 19:48 ` Guilherme Íscaro
2017-04-06 3:52 ` Kalle Valo
0 siblings, 1 reply; 12+ messages in thread
From: Guilherme Íscaro @ 2017-04-05 19:48 UTC (permalink / raw)
To: Adrian Chadd; +Cc: Kalle Valo, Ryan Hsu, ath10k
Hi, I have a question
Are you sure this is an ASPM problem? I've disable pcie_aspm during
boot (Kernel boot option - pcie_aspm=off) and the problem still
persists.
2017-03-31 12:11 GMT-03:00 Adrian Chadd <adrian@freebsd.org>:
> hiya,
>
> hm, what's the reference driver do for pci powersave versus aspm? Does
> it change any pci config space register settings for allowable sleep
> states?
>
>
>
> -adrian
>
>
> On 31 March 2017 at 04:12, Kalle Valo <kvalo@qca.qualcomm.com> wrote:
>> Guilherme Íscaro <cabelitostos@gmail.com> writes:
>>
>>> I would like to inform that I "fixed" the problem. After my last
>>> email, I cloned the linux repo and started to hack around the driver
>>> source code. By looking at the dmesg output that I provided to you
>>> guys, I noticed that for some reason the board was not being properly
>>> awake ( ath10k_pci_wake_wait() returns ETIMEOUT). I so sick with this
>>> problem that I hardcoded "ar_pci->pci_ps" to false, thus the board
>>> can't sleep now.
>>
>> Sounds like a problem with your PCI bus or the platform/laptop so try
>> different PCI settings both on BIOS and kernel. I have seen lots of talk
>> about ASPM, especially with some iwlwifi devices, so you should also
>> investigate about that.
>>
>> Please let us know if you find anything, it's always valuable
>> information. Have fun googling :)
>>
>> --
>> Kalle Valo
>> _______________________________________________
>> ath10k mailing list
>> ath10k@lists.infradead.org
>> http://lists.infradead.org/mailman/listinfo/ath10k
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: Reporting a bug for QCA6174 802.11ac
2017-04-05 19:48 ` Guilherme Íscaro
@ 2017-04-06 3:52 ` Kalle Valo
0 siblings, 0 replies; 12+ messages in thread
From: Kalle Valo @ 2017-04-06 3:52 UTC (permalink / raw)
To: Guilherme Íscaro; +Cc: Adrian Chadd, Ryan Hsu, ath10k
(please don't top post)
Guilherme Íscaro <cabelitostos@gmail.com> writes:
> Hi, I have a question
To whom?
> Are you sure this is an ASPM problem? I've disable pcie_aspm during
> boot (Kernel boot option - pcie_aspm=off) and the problem still
> persists.
ASPM was just one area to investigate. The real problem could be
anywhere.
--
Kalle Valo
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
^ permalink raw reply [flat|nested] 12+ messages in thread
end of thread, other threads:[~2017-04-06 3:53 UTC | newest]
Thread overview: 12+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2017-03-20 15:31 Reporting a bug for QCA6174 802.11ac Guilherme Íscaro
2017-03-21 18:35 ` Ryan Hsu
2017-03-21 18:58 ` Guilherme Íscaro
2017-03-22 13:56 ` Guilherme Íscaro
2017-03-22 22:17 ` Guilherme Íscaro
2017-03-23 22:46 ` Ryan Hsu
2017-03-23 23:11 ` Guilherme Íscaro
2017-03-28 17:45 ` Guilherme Íscaro
2017-03-31 11:12 ` Kalle Valo
2017-03-31 15:11 ` Adrian Chadd
2017-04-05 19:48 ` Guilherme Íscaro
2017-04-06 3:52 ` Kalle Valo
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.