This bug was fixed in the package fwts - 0.23.25
---------------
fwts (0.23.25) oneiric; urgency=low
* acpi: checksum: output correct checksum value (LP: #869018)
* framework: -T option should be -t, (LP: #868226)
fwts (0.23.24) oneiric; urgency=low
* acpi: method: relax _BIF, _BIX tests.
* acpi: method: Check _BST charging + discharging more thoroughly (LP:
#862153)
* acpi: acpitables: fix spurious advice infomation (LP: #862170)
* pci: maxreadreq: add more helpful advice (LP: #859651)
-- Colin King <colin.k...@canonical.com> Thu, 6 Oct 2011 15:11:00 +0100
** Changed in: fwts (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/859651
Title:
fwts: maxreadreq should explain why a low setting is bad
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fwts/+bug/859651/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
