http://bugzilla.kernel.org/show_bug.cgi?id=10374 ------- Comment #5 from seraph@xxxxxxxxx 2008-04-01 12:05 ------- Hello all, I did a bit more testing, and I think this may be related to the order in which modules are loaded. If I let udev load sungem, and load sym53c8xx manually, everything works. If I let udev load sym53c8xx, and load sungem manually, I get the non-functional network. If I let udev load both modules, I also get the non-functional network. While udev loads sungem first and sym53c8xx later, I don't suppose it waits for one module to 'settle' before loading the next. :-) So to sum it up, the bug is triggered if sym53c8xx is loaded before sungem is. -- Configure bugmail: http://bugzilla.kernel.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee. -- To unsubscribe from this list: send the line "unsubscribe linux-scsi" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
