On Thu, 30 Nov 2006 02:04:15 +0100 "Rafael J. Wysocki" <[EMAIL PROTECTED]> wrote:
> > > > > > git-netdev-all.patch > > > git-netdev-all-fixup.patch > > > libphy-dont-do-that.patch > > > > Are you able to eliminate libphy-dont-do-that.patch? > > > > > Is a broken-out version of git-netdev-all.patch available from somewhere? > > > > Nope, and my few fumbling attempts to generate the sort of patch series > > which you want didn't work out too well. One has to downgrade to > > git-bisect :( > > > > What does "doesn't work" mean, btw? > > Well, it turns out not to be 100% reproducible. I can only reproduce it after > a soft reboot (eg. shutdown -r now). > > Then, while configuring network interfaces the system says the interface name > is ethxx0, but it should be eth1 (eth0 is an RTL-8139, which is not used). > Now > if I run ifconfig, it says: > > eth0: error fetching interface information: Device not found > > and that's all (normally, ifconfig would show the information for lo and eth1, > without eth0). Moreover, 'ifconfig eth1' says: > > eth1: error fetching interface information: Device not found > > Next, I run 'rmmod uli526x' and 'modprobe uli526x' and then 'ifconfig' is > still saying the above (about eth0), but 'ifconfig eth1' seems to work as > it should. However, the interface often fails to transfer anything after > that. Lovely. Sounds like some startup race, perhaps against userspace. Is CONFIG_PCI_MULTITHREAD_PROBE set? (err, we meant to disable that for 2.6.19 but forgot). - To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
