Jeff, thanks for that update. I'm focusing on the via-rhine issue as you know. I'm confused by your report that via-rhine failed after resume on Hardy even though acpi- support was unloading the module. That doesn't seem to make sense since there should be no difference between boot-time loading and manual reloading.
However, there could be a problem with the driver in Hardy where a load- unload-load cycle breaks something without needing a suspend/resume in between. Would it be possible to test that out on Hardy so we can be sure the issue is caused by suspend/resume and not something independent? Overview: The Hardy workaround was usually to add the module-name to the acpi- support configuration: /etc/default/acpi-support MODULES="" MODULES_WHITELIST="" In Hardy the acpi-support scripts: /etc/acpi/suspend.d/60-generate-modules-list.sh /etc/acpi/suspend.d/70-modules-unload.sh handled unloading of modules. To find out which network drivers it would/should unload via 60-, from the Hardy installation issue this command: for device in /sys/class/net/*/device/driver; do basename $(readlink $device); done One would expect the network device module was being unloaded via that mechanism, but if the module name wasn't resolved correctly it wouldn't get unloaded automatically. -- [intrepid] Kernel warning, network and usb mouse fail after resume https://bugs.launchpad.net/bugs/281089 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
