PCI: 0000:03:00.0, VID: 86:95, Class: 02:80 (Network controller)
Config:
0000: 86 80 95 08 06 00 10 00 c4 00 80 02 10 00 00 00 ................
0010: 04 00 c0 f7 00 00 00 00 00 00 00 00 00 00 00 00 ................
0020: 00 00 00 00 00 00 00 00 00 00 00 00 86 80 22 02 ..............".
0030: 00 00 00 00 c8 00 00 00 00 00 00 00 0b 01 00 00 ................
PCI: 0000:03:00.0, VID: 86:95, Class: 02:80 (Network controller)
Config:
0000: 86 80 95 08 06 04 10 00 c4 00 80 02 10 00 00 00 ................
0010: 04 00 c0 f7 00 00 00 00 00 00 00 00 00 00 00 00 ................
0020: 00 00 00 00 00 00 00 00 00 00 00 00 86 80 22 02 ..............".
0030: 00 00 00 00 c8 00 00 00 00 00 00 00 0b 01 00 00 ................
Carefully comparing them found BYTE 5 is changed from 0x00 to 0x04, i.e. BIT3
changed. According to PCI spec, it is Command Register and it is "Interupt
disable". This can indicate the device interupt was disabled when fwts reads
its pci registers. It seems that when the fwts compares the registers the wifi
device is under working/reconnecting, it might be affected by the environment,
eg. two APs in the same room, AP signal not stable...
Checking the machine on my desk over 160 times, it works fine and cannot be
reproduced.
It doesn't affect the real function. This can also be safely ignored.
** Attachment added: "results.log"
https://bugs.launchpad.net/ubuntu/+source/linux-lts-saucy/+bug/1287545/+attachment/4028114/+files/results.log
** Changed in: linux-lts-saucy (Ubuntu)
Status: New => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1287545
Title:
Device configuration differ between S3
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-lts-saucy/+bug/1287545/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
