From: Darcy Watkins <dwatkins@tranzeo.com>
To: Benjamin Krill <ben@codiert.org>
Cc: linuxppc-embedded <linuxppc-embedded@ozlabs.org>
Subject: Re: Possible init bug in ibm_newemac/core.c
Date: Fri, 15 Aug 2008 13:00:40 -0700 [thread overview]
Message-ID: <1218830440.3465.201.camel@localhost> (raw)
In-Reply-To: <20080815174821.GK10829@codiert.org>
Hi Ben,
Thanks for the pointer the the thread. What they did was exactly what I
did (and then later reverted). I guess my "lame hack attempt" wasn't so
lame after all.
It works fine on my "mule" board with more memory and two Ethernet
ports, but fails on the production board having less memory and only one
Ethernet port.
This probably means that I need to look into something else.
In our setup, the DTS always says two Ethernet ports. It may be that
the failure of the probe in the case of the non-existent Ethernet port
causes the kernel panic when the order of execution of those two
functions are reversed.
Thanks again. This gives me a few more leads to chase down.
Darcy
On Fri, 2008-08-15 at 10:48 -0700, Benjamin Krill wrote:
> Hi Darcy,
>
> >The bug normally goes unnoticed until you turn on spinlock and/or
> >rtmutex debuggging in the kernel config - then the debugging magic
> >checks will catch it during boot.
>
> Have a look at thread:
> http://ozlabs.org/pipermail/linuxppc-dev/2008-August/061631.html
>
> cheers
> ben
>
--
Regards,
Darcy
--------------
Darcy L. Watkins - Senior Software Developer
Tranzeo Wireless Technologies, Inc.
19273 Fraser Way, Pitt Meadows, BC, Canada V3Y 2V4
T:604-460-6002 ext:410
http://www.tranzeo.com
next prev parent reply other threads:[~2008-08-15 20:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-15 17:03 Possible init bug in ibm_newemac/core.c Darcy Watkins
2008-08-15 17:48 ` Benjamin Krill
2008-08-15 20:00 ` Darcy Watkins [this message]
2008-08-15 20:38 ` Darcy Watkins
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=1218830440.3465.201.camel@localhost \
--to=dwatkins@tranzeo.com \
--cc=ben@codiert.org \
--cc=linuxppc-embedded@ozlabs.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).