From: Gary Thomas <gary@mlbassoc.com>
To: "Mark S. Mathews" <mark@linux-wlan.com>
Cc: "Stefan Stürke" <sst@pandatel.com>,
"linuxppc embedded" <linuxppc-embedded@lists.linuxppc.org>
Subject: Re: [SPAM] Re: m8xx hang in reboot
Date: Thu, 26 Aug 2004 06:57:41 -0600 [thread overview]
Message-ID: <1093525060.2961.2826.camel@hermes> (raw)
In-Reply-To: <Pine.LNX.4.61.0408260822060.19804@chef.linux-wlan.com>
On Thu, 2004-08-26 at 06:28, Mark S. Mathews wrote:
> This is interesting, thanks Stefan.
>
> 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.
> 2) the wlan device that's attached to the pcmcia interface was
> previously in use.
>
> 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.
Do either of those use 'printk()'? I've seen this failure if the
caches currently hold everything in the printk path - it's actually
the call to printk that causes the bad bus cycles. Try flushing or
even disabling the caches just before the printk in the reset routine.
Note: I would think that if the problem were the FLASH being in the
wrong mode (suggested by Mark), then the whole thing would freeze,
rather than sitting in the while() loop...
>
> Thanks Stefan,
> -M
>
>
> On Thu, 26 Aug 2004, Stefan Stürke wrote:
>
> >
> > Mark S. Mathews wrote:
> >>
> >> Hey Folks,
> >>
> >> I've got an mpc850 based setup running 2.4.27 that, under certain
> >> circumstances, hangs in the the m8xx_restart() function (instead of
> >> rebooting) when I issue the usermode reboot cmd.
> >>
> >> I've traced all through the path and confirmed that yes, it is hanging in
> >> this function. ;-)
> >
> > Maybe you can have a look at your boot flash when you enter the
> > m8xx_restart() function. I had a similar problem and found that
> > my boot flash was in read status state in that moment, so it was
> > impossible to fetch the correct programm code after reset.
> >
> > HTH,
> > Stefan
> >
> > --
> > PANDATEL AG
> > Bayernstrasse 33
> > 30855 Langenhagen
> > Germany
> >
> > Tel.: +49 (0)511 978199-15
> > Fax.: +49 (0)511 978199-77
> > mailto:sst-news2003@pandatel.com
> > www.pandatel.com
> >
> >
> >
> >
>
> --
>
> 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
--
Gary Thomas <gary@mlbassoc.com>
MLB Associates
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2004-08-26 12:57 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 [this message]
2004-08-26 14:23 ` Dan Malek
2004-08-26 15:34 ` Mark S. Mathews
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=1093525060.2961.2826.camel@hermes \
--to=gary@mlbassoc.com \
--cc=linuxppc-embedded@lists.linuxppc.org \
--cc=mark@linux-wlan.com \
--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).