> Of course. It looks like we can do that by reverting the change that > caused this regression. Please test whether the attached patch fixes > the problem, following the instructions at: > > https://kernel-handbook.alioth.debian.org/ch-common-tasks.html#s-common-official >
Yes, it fixes the problem, even without my modprobe.blacklist argument. Some notes: test-patches asked me for a flavour; I entered amd64. When installing the linux-image package, I got this error: update-initramfs: Generating /boot/initrd.img-4.5.0-0.bpo.1-amd64 W: Possible missing firmware /lib/firmware/rtl_nic/rtl8107e-2.fw for module r8169 W: Possible missing firmware /lib/firmware/rtl_nic/rtl8107e-1.fw for module r8169 W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168h-2.fw for module r8169 W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168h-1.fw for module r8169 I ignored it, since I probably won't need WiFi during early start-up. When fully booted with this kernel, I tested my WiFi and it still works. lsmod shows now that the sp5100_tco module is loaded. dmesg contains the following line: [ 0.000000] Command line: BOOT_IMAGE=/vmlinuz-4.5.0-0.bpo.1-amd64 root=UUID=cab2c5d5-4664-4105-bcbd-fcb860cc035d ro quiet (so it is version 4.5, without the blacklist argument) dmesg does not show the ACPI error lines that were generated by the faulty 4.5. dmesg | grep sp5100_tco returns the following: [ 31.700531] sp5100_tco: SP5100/SB800 TCO WatchDog Timer Driver v0.05 [ 31.700640] sp5100_tco: PCI Revision ID: 0x13 [ 31.700709] sp5100_tco: failed to find MMIO address, giving up. I hope this is what you expected. To me, it looks like the problem is fixed. CJP
