[Also posted to Planet Debian.]
The Debian kernel team regularly backports driver updates to the Linux
kernel in stable releases to add support for new hardware, and I've
prepared several updates intended for point release 6.0.2. Since the
kernel team does not have a large collection of hardware on which to
test driver changes, we would appreciate test reports from users. It is
important to test not just that new devices are supported properly, but
that there are no regressions in support for older devices.
Changes
-------
I have updated these drivers to the versions found in Linux 2.6.38,
modulo driver API changes:
* bna: New driver for Brocade Ethernet adapters. (#627699)
* e1000e: Add support for i82567V-4, i82579. Bug fixes for i82577,
i82578, i82583. (#627700)
* hpsa: New driver for HP Smart Array controllers. It also
supports some devices that are currently handled by cciss, but I
have disabled that for 'squeeze'. (#627701)
* igb, igbvf: Add support for i82576-ET2, 82580, DH89xxCC, i350.
(#627702)
* pm8001: New driver for PMC-Sierra SAS/SATA HBAs. (#627703)
* r8169: Add full support for RTL8168DP. Bug fixes for RTL8102E.
(#627704)
* tg3, broadcom: Add support for BCM5717, BCM5719, BCM57765, and
BCM50610M and BCM5241 PHYs. Bug fixes for BCM5755. (#627705)
I have also cherry-picked some small changes:
* bnx2i: Add support for BCM5771E
* wl1251: Add support for PG11 chips
* bnx2x: Add support for BCM84823
* ar9170usb: Add several additional USB device IDs
There are more drivers that I think should be added or updated (see
#624794) but they will probably have to wait for release 6.0.3.
Packages
--------
The source package and binary packages for i386 and amd64 are available
on people.debian.org. They can be verified by the checksums in the
signed changes file.
The current packages are version 2.6.32-35~test1, but there may be
further test versions before an official stable update.
How to test
-----------
For network drivers, I suggest the following regression tests:
1. If the driver tries to load firmware (only required for some
chips), does this work once the firmware file(s) are installed?
2. Can you receive and transmit VLAN-tagged frames after creating a
VLAN interface?
3. Does the interface work after suspend and resume?
4. Does the interface work after removing the cable for 10 seconds
and reinserting it?
5. Does multicast configuration work? (IPv6 autoconfiguration or
mDNS will cover this.)
6. Can the interface send and receive TCP/IP across a LAN at the
same speed, before and after these changes? (Use e.g. netperf to
test this, but don't forget to remove the netperf package after
use.)
7. Are any warnings or errors logged by the kernel during the
preceding tests?
For storage drivers, unfortunately I don't have a good idea of what
tests would be suitable. In any case, please don't test on disks storing
valuable data!
Please send test reports to the bug reports linked above, stating the
driver name, the PCI ID for the device you tested (from lspci -n) and
any other device identification that the kernel log (for example, r8169
logs the 'XID' of the device).
Ben.
--
Ben Hutchings
Once a job is fouled up, anything done to improve it makes it worse.
Attachment:
signature.asc
Description: This is a digitally signed message part