From: "Mark S. Mathews" <mark@linux-wlan.com>
To: Dan Malek <dan@embeddededge.com>
Cc: linuxppc-embedded@lists.linuxppc.org, "Stefan Stürke" <sst@pandatel.com>
Subject: Re: [SPAM] Re: m8xx hang in reboot
Date: Thu, 26 Aug 2004 11:34:56 -0400 (EDT) [thread overview]
Message-ID: <Pine.LNX.4.61.0408261110400.20706@chef.linux-wlan.com> (raw)
In-Reply-To: <8F645223-F76B-11D8-89B4-003065F9B7DC@embeddededge.com>
Dan, Stefan, all...
Yup, doing a read via the mtd device after the write to the mtd device
appears to take care of the problem. Hmmm, is this an mtd bug? or
perhaps a board specific thing.
Oh well, don't have time to debug the mtd stuff right now so I'll just do
the read-after-write workaround and move on.
My thanks to all for the suggestions and for making me think,
-Mark
BTW Dan: The wlan device does get shutdown (and driver is unloaded) before
the reboot call. The wierd thing is that I set up the system in
a mode where the wlan device is never brought up at all, did the
flash unlock/erase/write (no read), and issued the reboot...
it worked just fine. The reboot failure seems to require that
the wlan device be operational. Seems to imply that this problem
is somehow tied to one or more of: pcmcia hw, wlan device hw,
pcmcia sw, or wlan sw. 'Tis a quandry. Perhaps we'll never
know, I've got other fish to fry now...
On Thu, 26 Aug 2004, Dan Malek wrote:
>
> On Aug 26, 2004, at 8:28 AM, Mark S. Mathews wrote:
>
>> One item of info that I had left out of the original post (because I
>> hadn't verified 100% that this was truly part of the issue):
>> The "certain circumstances" prior to the reboot failure are:
>> 1) we've just completed an unlock/erase/write on one of our flash
>> partitions.
>
> Oh Geeze.....yeah, that could be a problem :-)
>
>> 2) the wlan device that's attached to the pcmcia interface was
>> previously in use.
>
> Can you test these independently to see which is causing the
> trouble? I'm also guessing it's number 1.
>
>> If the wlan device was not in use or if we don't do the flash
>> unlock/erase/write, then the reboot works just fine. Strange
>> combination
>> of factors.
>
> Both of these make sense. After you are done writing the flash,
> do something to read it, so it returns to that state. You may
> need to shut down the wlan before rebooting if that is causing
> the trouble.
>
>
> -- Dan
>
>
>
>
--
Mark S. Mathews
AbsoluteValue Systems Web: http://www.linux-wlan.com
721-D North Drive e-mail: mark@linux-wlan.com
Melbourne, FL 32934 Phone: 321.259.0737
USA Fax: 321.259.0286
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
prev parent reply other threads:[~2004-08-26 15:34 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-25 20:22 m8xx hang in reboot Mark S. Mathews
2004-08-26 3:29 ` Dan Malek
2004-08-26 12:42 ` Mark S. Mathews
2004-08-26 6:40 ` Stefan Stürke
2004-08-26 12:28 ` [SPAM] " Mark S. Mathews
2004-08-26 12:57 ` Gary Thomas
2004-08-26 14:23 ` Dan Malek
2004-08-26 15:34 ` Mark S. Mathews [this message]
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=Pine.LNX.4.61.0408261110400.20706@chef.linux-wlan.com \
--to=mark@linux-wlan.com \
--cc=dan@embeddededge.com \
--cc=linuxppc-embedded@lists.linuxppc.org \
--cc=sst@pandatel.com \
/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).