public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: David Ford <david@blue-labs.org>
To: linux-kernel@vger.kernel.org
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
	Ross Biro <bir7@leland.stanford.edu>
Subject: [PATCH] Re: 2.4.5+ hangs on boot
Date: Sat, 14 Jul 2001 20:56:19 -0400	[thread overview]
Message-ID: <3B50EA33.1010900@blue-labs.org> (raw)
In-Reply-To: <3B50AE0D.80002@blue-labs.org> <3B50C391.3050804@blue-labs.org>

[-- Attachment #1: Type: text/plain, Size: 1518 bytes --]

Ok, since net_dev_init() is called from genhd.c:53, I figured it'd work 
just fine if I removed it from net/core/dev.c in register_netdev(). 
 Since I'm not as well steeped in this code, those who know better are 
invited to correct me.

--- linux-2.4.6.orig/net/core/dev.c     Sat Jul 14 17:48:57 2001
+++ linux-2.4.6/net/core/dev.c  Wed Jun 20 21:00:55 2001
@@ -2405,6 +2401,9 @@
 #ifdef CONFIG_NET_FASTROUTE
        dev->fastpath_lock=RW_LOCK_UNLOCKED;
 #endif
-
-       if (dev_boot_phase)
-               net_dev_init();
 
 #ifdef CONFIG_NET_DIVERT
        ret = alloc_divert_blk(dev);

David

David Ford wrote:

> Ok, the problem is this.  I have TEQL packet scheduling in my config, 
> the kernel runs through this sequence on boot:
>
> net_dev_init()
>    pktsched_init()
>        teql_init()    [starts a lock with rtnl_lock()]
>            register_netdevice()
>                net_dev_init()
>                    pktsched_init()
>                        teql_init() [hangs here...]
>
> Here is the problem.  We enter teql_init() again with a rtnl_lock() 
> already being held.  Do any of the authors of these functions want to 
> jump in here?
>
> David
>
> David Ford wrote:
>
>> [...]
>> I2O LAN OSM (C) 1999 University of Helsinki.
>> early initialization of device teql0 is deferred
>> loop: loaded (max 8 devices)
>> Linux Tulip driver version 0.9.15-pre3 (June 1, 2001)
>> PCI: Found IRQ 5 for device 00:10.0
>>
>> Any comments or suggestions?  2.4.5-ac19 is the last kernel I have 
>> that works.
>


[-- Attachment #2: dev.c-diff --]
[-- Type: text/plain, Size: 317 bytes --]

--- linux-2.4.6.orig/net/core/dev.c	Sat Jul 14 17:48:57 2001
+++ linux-2.4.6/net/core/dev.c	Wed Jun 20 21:00:55 2001
@@ -2405,6 +2401,9 @@
 #ifdef CONFIG_NET_FASTROUTE
 	dev->fastpath_lock=RW_LOCK_UNLOCKED;
 #endif
-
-	if (dev_boot_phase)
-		net_dev_init();
 
 #ifdef CONFIG_NET_DIVERT
 	ret = alloc_divert_blk(dev);

      reply	other threads:[~2001-07-15  0:56 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-07-14 20:39 2.4.5+ hangs on boot David Ford
2001-07-14 22:11 ` [found-not fixed] " David Ford
2001-07-15  0:56   ` David Ford [this message]

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=3B50EA33.1010900@blue-labs.org \
    --to=david@blue-labs.org \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=bir7@leland.stanford.edu \
    --cc=linux-kernel@vger.kernel.org \
    /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