On Friday, 1 December 2006 02:20, Greg KH wrote:
> On Wed, Nov 29, 2006 at 06:18:09PM -0800, Andrew Morton wrote:
> > 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).
>
> No, I disabled it for 2.6.19, -mm turns it back on :)
But it's not set in my .config.
Greetings,
Rafael
--
You never change things by fighting the existing reality.
R. Buckminster Fuller
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]