From: "Gerhard TAEUBL" <Gerhard.TAEUBL@frequentis.com>
To: <linuxppc-embedded@lists.linuxppc.org>
Subject: Patch fec.c
Date: Wed, 15 Oct 2003 08:58:43 +0200 [thread overview]
Message-ID: <sf8d0c4a.082@mail.frequentis.com> (raw)
Hi!
I found following message:
http://lists.linuxppc.org/linuxppc-embedded/200305/msg00255.html
There Jean-Denis states:
2 - Or, the worst, in function mdio_read called through the ioctl,
which would hang the calling process.
We have an MPC860T custom board and uses DENX kernel 2.4.4.
In our project we use also a second ethernet pcmcia card, and we have to bound both ethernet cards as backup medium. We updsate the bounding.c file and compile it as module. It works, but if we enable the mii check on the bounding module the kernel crash. Our hardware has an hardware watchdog, so it resets within one second.
Does anyone have any idea how to patch the code to prevent this 'failure'?
best regards
Gerhard
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
reply other threads:[~2003-10-15 6:58 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=sf8d0c4a.082@mail.frequentis.com \
--to=gerhard.taeubl@frequentis.com \
--cc=linuxppc-embedded@lists.linuxppc.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;
as well as URLs for NNTP newsgroup(s).