http://bugzilla.kernel.org/show_bug.cgi?id=10374 ------- Comment #6 from anonymous@xxxxxxxxxxxxxxxxxxxx 2008-04-01 13:20 ------- Reply-To: James.Bottomley@xxxxxxxxxxxxxxxxxxxxx On Tue, 2008-04-01 at 21:05 +0200, Jos van der Ende wrote: > 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. :-) That's odd ... it's behaving like a resource conflict. However, the ports and interrupt trace didn't betray anything. What does lspci -vv say for each of the devices? Also, if you remove the sym2 module in the problem case, does the sungem come back to life? I'm afraid I can't see anything relevant looking over the sym2 changes, so you might need to bisect this to identify the culprit. James -- 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
