From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Greg KH <greg@kroah.com>
Cc: Andrew Morton <akpm@osdl.org>,
linux-kernel@vger.kernel.org, tulip-users@lists.sourceforge.net,
netdev@vger.kernel.org, Jeff Garzik <jeff@garzik.org>,
Valerie Henson <val_henson@linux.intel.com>
Subject: Re: 2.6.19-rc6-mm2: uli526x only works after reload
Date: Sat, 2 Dec 2006 01:07:39 +0100 [thread overview]
Message-ID: <200612020107.40214.rjw@sisk.pl> (raw)
In-Reply-To: <20061201012049.GA20352@kroah.com>
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" <rjw@sisk.pl> 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
next prev parent reply other threads:[~2006-12-02 0:12 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20061128020246.47e481eb.akpm@osdl.org>
[not found] ` <200611292054.35313.rjw@sisk.pl>
[not found] ` <200611292108.00578.rjw@sisk.pl>
2006-11-29 21:30 ` 2.6.19-rc6-mm2: uli526x only works after reload Andrew Morton
2006-11-29 21:31 ` Rafael J. Wysocki
2006-11-29 23:08 ` Rafael J. Wysocki
2006-11-29 23:26 ` Andrew Morton
2006-11-30 1:04 ` Rafael J. Wysocki
2006-11-30 2:18 ` Andrew Morton
2006-12-01 1:20 ` Greg KH
2006-12-02 0:07 ` Rafael J. Wysocki [this message]
2006-11-30 20:21 ` Rafael J. Wysocki
2006-11-30 21:12 ` Andrew Morton
2006-11-30 21:32 ` Rafael J. Wysocki
2006-12-01 1:08 ` Rafael J. Wysocki
2006-12-01 1:27 ` Greg KH
2006-12-04 23:13 ` Greg KH
2006-12-03 7:49 ` [-mm patch] drivers/net/netxen/: possible cleanups Adrian Bunk
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200612020107.40214.rjw@sisk.pl \
--to=rjw@sisk.pl \
--cc=akpm@osdl.org \
--cc=greg@kroah.com \
--cc=jeff@garzik.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=tulip-users@lists.sourceforge.net \
--cc=val_henson@linux.intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).