From: Mike Westall <westall@cs.clemson.edu>
To: chas williams - CONTRACTOR <chas@cmf.nrl.navy.mil>
Cc: Lukasz Trabinski <lukasz@oceanic.wsisiz.edu.pl>,
linux-atm-general@lists.sourceforge.net,
linux-kernel@vger.kernel.org,
Bartlomiej Solarz <solarz@wsisiz.edu.pl>
Subject: Re: [Linux-ATM-General] Kernel 2.6.10 and 2.4.29 Oops fore200e (fwd)
Date: Mon, 24 Jan 2005 17:27:23 -0500 [thread overview]
Message-ID: <41F5764B.8050308@cs.clemson.edu> (raw)
In-Reply-To: <200501241837.j0OIbAE7011717@ginger.cmf.nrl.navy.mil>
You could also just revert to kernel 2.4.25 or
earlier. Someone who was apparently oblivious
to the fact that device driver send routines
were "routinely" called in irq context and/or
that it was a <very bad thing> to call schedule()
under such circumstances slipped that one in
sometime between 2.4.25 which is OK and 2.4.28
where it is broken.
In 2.4.25 and earlier it was a simple busy wait loop
in which "goto retry_here;" immediately followed
the "if" statement. This was safe, albeit MP unfriendly
because of the spin_lock()/unlock() on each iteration.
I'd say just delete the if and drop the damn
packet.
At any rate someone who has access to the golden code
should fix this one way or another ASAP because its
definitely seriously broken the way it is now.
Mike
chas williams - CONTRACTOR wrote:
> In message <Pine.LNX.4.61L.0501210835270.6993@lt.wsisiz.edu.pl>,Lukasz Trabinsk
> i writes:
>
>>Sorry, but I don;t understand, what line, i am not kernel guru. :/
>
>
> look for the following code:
>
> /* retry once again? */
> if(--retry > 0) {
> schedule();
> goto retry_here;
> }
>
>
> change schedule() to udelay(50) and see if things are 'better'.
>
>
>>Is was happened on 2.4.29, too. It is a interrupt problem?
>
>
> its calling a routine that might sleep while in the transmit routine.
> this is not allow.
>
>
> -------------------------------------------------------
> This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
> Tool for open source databases. Create drag-&-drop reports. Save time
> by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
> Download a FREE copy at http://www.intelliview.com/go/osdn_nl
> _______________________________________________
> Linux-atm-general mailing list
> Linux-atm-general@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/linux-atm-general
>
>
next prev parent reply other threads:[~2005-01-24 22:32 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200501181659.j0IGx7km019753@ginger.cmf.nrl.navy.mil>
2005-01-21 7:46 ` [Linux-ATM-General] Kernel 2.6.10 and 2.4.29 Oops fore200e (fwd) Lukasz Trabinski
2005-01-24 18:37 ` chas williams - CONTRACTOR
2005-01-24 22:27 ` Mike Westall [this message]
2005-01-24 22:38 ` chas williams - CONTRACTOR
2005-01-24 23:18 ` Lukasz Trabinski
2005-01-30 19:24 ` Lukasz Trabinski
2005-01-30 22:55 ` chas williams - CONTRACTOR
2005-01-31 8:48 ` Lukasz Trabinski
2005-03-05 12:34 ` Lukasz Trabinski
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=41F5764B.8050308@cs.clemson.edu \
--to=westall@cs.clemson.edu \
--cc=chas@cmf.nrl.navy.mil \
--cc=linux-atm-general@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=lukasz@oceanic.wsisiz.edu.pl \
--cc=solarz@wsisiz.edu.pl \
/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