From: "Glenn C. Hofmann" <hofmanng@swbell.net>
To: Jeff Garzik <jgarzik@mandrakesoft.com>,
"David S. Miller" <davem@redhat.com>
Cc: Russell King <rmk@arm.linux.org.uk>,
Ben LaHaise <bcrl@redhat.com>, Andrew Morton <andrewm@uow.edu.au>,
linux-kernel@vger.kernel.org, netdev@oss.sgi.com
Subject: Re: 3C905b partial lockup in 2.4.5-pre5 and up to 2.4.6-pre1
Date: Sun, 10 Jun 2001 22:17:46 -0500 [thread overview]
Message-ID: <3B23F20A.22574.10AD93@localhost> (raw)
In-Reply-To: <15140.5762.589629.252904@pizda.ninka.net>
In-Reply-To: <3B23A4BB.7B4567A3@mandrakesoft.com>
I have, as was suggested, built as a module, and get unresolved symbol do_softirq, so
this appears to be another problem in this driver with 2.4.6-pre2. If I can help in any
way, please let me know, although I am by no means a programmer, just a tester.
Thanks.
Glenn C. Hofmann
On 10 Jun 2001, at 17:53 David S. Miller wrote:
>
> Jeff Garzik writes:
> > > [note I've not found anything in 2.4.5 where netif_carrier_ok prevents
> > > the net layers queueing packets for an interface, and forwarding them
> > > on for transmission].
> >
> > we want netif_carrier_{on,off} to emit netlink messages. I don't know
> > how DaveM would feel about such getting implemented in 2.4.x though,
> > even if well tested.
>
> If someone sent me patches which did this (and minded the
> restrictions, if any, this adds to the execution contexts in
> which the carrier on/off stuff can be invoked) I would consider
> the patch seriously for 2.4.x
>
> Later,
> David S. Miller
> davem@redhat.com
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2001-06-11 3:18 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-09 17:45 3C905b partial lockup in 2.4.5-pre5 and up to 2.4.6-pre1 Glenn C. Hofmann
2001-06-10 1:35 ` Andrew Morton
2001-06-10 4:56 ` Glenn C. Hofmann
2001-06-10 5:08 ` Glenn C. Hofmann
2001-06-10 5:54 ` Ben LaHaise
2001-06-10 8:38 ` Russell King
2001-06-10 9:39 ` arjan
2001-06-10 16:06 ` Ben LaHaise
2001-06-10 16:34 ` Russell King
2001-06-10 16:47 ` Jeff Garzik
2001-06-10 22:23 ` Ben LaHaise
2001-06-11 0:53 ` David S. Miller
2001-06-11 13:03 ` Andrew Morton
2001-06-11 13:27 ` David S. Miller
2001-06-11 13:49 ` Jeff Garzik
2001-06-11 14:21 ` Andrew Morton
2001-06-11 16:05 ` Jeff Garzik
2001-06-11 3:17 ` Glenn C. Hofmann [this message]
2001-06-11 3:25 ` Jeff Garzik
2001-06-12 3:17 ` Glenn C. Hofmann
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=3B23F20A.22574.10AD93@localhost \
--to=hofmanng@swbell.net \
--cc=andrewm@uow.edu.au \
--cc=bcrl@redhat.com \
--cc=davem@redhat.com \
--cc=ghofmann@pair.com \
--cc=jgarzik@mandrakesoft.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@oss.sgi.com \
--cc=rmk@arm.linux.org.uk \
/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