LinuxPPC-Dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Rune Torgersen" <runet@innovsys.com>
To: "Stefan Nickl" <Stefan.Nickl@kontron.com>
Cc: Tom Rini <trini@kernel.crashing.org>,
	linuxppc-embedded <linuxppc-embedded@ozlabs.org>
Subject: RE: [PATCH] RE: FCC Ethernet startup crash
Date: Mon, 11 Apr 2005 08:51:53 -0500	[thread overview]
Message-ID: <DCEAAC0833DD314AB0B58112AD99B93B859354@ismail.innsys.innovsys.com> (raw)

=20

> -----Original Message-----
> From: Stefan Nickl [mailto:Stefan.Nickl@kontron.com]=20
> Sent: Monday, April 11, 2005 04:20
> On Fri, 2005-04-08 at 09:39 -0500, Rune Torgersen wrote:
> > I'm not sure what is going on, but that patch causes me to=20
> get "eth0: tx
> > queue full!." messages as soon as I try to use the ethernet
> > (Same thing happened if I just tried to remove the fcc_restart from
> > init_fcc_startup)
> But regarding my current indisposition with hardware, I'd suggest to
> choose the smaller of the two evils, that is calling fcc_restart()
> before starting the queue, leaving but a tiny race condition=20
> on rx side.

Still get the tx full messages.
They do go away if I call fcc_restart twice in a row... (again)=09
I'll look a little more on what it is doing

             reply	other threads:[~2005-04-11 13:51 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-11 13:51 Rune Torgersen [this message]
  -- strict thread matches above, loose matches on Subject: below --
2005-04-11 14:40 [PATCH] RE: FCC Ethernet startup crash Rune Torgersen
2005-04-08 14:39 Rune Torgersen
2005-04-11  9:19 ` [PATCH] " Stefan Nickl

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=DCEAAC0833DD314AB0B58112AD99B93B859354@ismail.innsys.innovsys.com \
    --to=runet@innovsys.com \
    --cc=Stefan.Nickl@kontron.com \
    --cc=linuxppc-embedded@ozlabs.org \
    --cc=trini@kernel.crashing.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