From: "Joakim Tjernlund" <joakim.tjernlund@transmode.se>
To: "'Scott Wood'" <scottwood@freescale.com>,
"'Kumar Gala'" <galak@kernel.crashing.org>
Cc: 'linuxppc-dev' <linuxppc-dev@ozlabs.org>
Subject: RE: mpc83xx_restart() buggy
Date: Sat, 30 Dec 2006 11:49:14 +0100 [thread overview]
Message-ID: <012101c72c00$256bc370$1e67a8c0@Jocke> (raw)
In-Reply-To: <45959EFC.4040404@freescale.com>
> -----Original Message-----
> From:
> linuxppc-dev-bounces+joakim.tjernlund=transmode.se@ozlabs.org
> [mailto:linuxppc-dev-bounces+joakim.tjernlund=transmode.se@ozl
> abs.org] On Behalf Of Scott Wood
> Sent: den 30 december 2006 00:04
> To: Kumar Gala
> Cc: Tjernlund; 'linuxppc-dev'
> Subject: Re: mpc83xx_restart() buggy
>
> Kumar Gala wrote:
> > On Dec 27, 2006, at 6:45 PM, Tjernlund wrote:
> >>mpc83xx_restart() uses ioremap(), which doesn't like
> >>beeing called while in IRQ context.
> >>
> >>Calling mpc83xx_restart() in IRQ context yields OOPS
> >>which calls mpc83xx_restart() again and the loop never
> >>termintes.
> >
> > This is interesting, I know I've seen restart work properly w/o an
> > oops. How are you causing the restart?
>
> sysrq-b triggers it, as probably does crashing from an
> interrupt handler
> with panic_timeout nonzero. You'll need CONFIG_DEBUG_SPINLOCK_SLEEP
> turned on, of course.
For me it was http://ozlabs.org/pipermail/linuxppc-dev/2006-December/029414.html
ucc_geth_timeout() is buggy and so is ucc_geth_start_xmit(), needs to
return NETDEV_TX_BUSY or NETDEV_TX_OK.
Jocke
next prev parent reply other threads:[~2006-12-30 10:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-28 0:45 mpc83xx_restart() buggy Tjernlund
2006-12-29 22:45 ` Kumar Gala
2006-12-29 23:04 ` Scott Wood
2006-12-30 10:49 ` Joakim Tjernlund [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-01-09 8:13 Joakim Tjernlund
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='012101c72c00$256bc370$1e67a8c0@Jocke' \
--to=joakim.tjernlund@transmode.se \
--cc=galak@kernel.crashing.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=scottwood@freescale.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).