From: Kumar Gala <galak@kernel.crashing.org>
To: Dale Farnsworth <dale@farnsworth.org>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: 85xx software reset problems from paulus.git
Date: Tue, 27 Nov 2007 10:26:59 -0600 [thread overview]
Message-ID: <751B3227-484E-45BE-B233-D4A8CAC2F3FD@kernel.crashing.org> (raw)
In-Reply-To: <20071127145424.8925.qmail@farnsworth.org>
On Nov 27, 2007, at 8:54 AM, Dale Farnsworth wrote:
> I wrote:
>> Kumar Gala wrote:
>>>>> Yes. The symptoms in 2.6.24RC2 are that during a kernel panic or
>>>>> when
>>>>> calling 'reboot' in the shell, it just hangs. Using the same dts
>>>>> and
>>>>> resets in 2.6.23.1 reboots fine. I don't have a cds reference, but
>>>>> someone who does should be able to confirm whether the issue
>>>>> exists
>>>>> or
>>>>> not by just attempting to reboot via bash.
>>>
>>> Can someone do a git-bisect and find the patch that breaks things?
>>
>> I'll see if I can reproduce it on my 8548cds. If so, I'll then git-
>> bisect.
>
> I tried this with the current powerpc.git tree on my mpc8548cds, and
> the reboot command works for me. The system rebooted just fine.
I'm wondering if there is an issue rebooting if we are in an oops.
- k
next prev parent reply other threads:[~2007-11-27 17:45 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-16 15:00 85xx software reset problems from paulus.git robert lazarski
2007-11-16 15:27 ` Clemens Koller
2007-11-16 20:44 ` robert lazarski
2007-11-16 21:28 ` robert lazarski
2007-11-16 21:46 ` Kumar Gala
2007-11-16 22:01 ` robert lazarski
2007-11-17 19:52 ` Kumar Gala
2007-11-26 17:41 ` robert lazarski
2007-11-26 20:20 ` Clemens Koller
2007-11-27 7:38 ` Kumar Gala
2007-11-27 13:50 ` Dale Farnsworth
2007-11-27 14:54 ` Dale Farnsworth
2007-11-27 16:26 ` Kumar Gala [this message]
2007-11-27 23:09 ` Dale Farnsworth
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=751B3227-484E-45BE-B233-D4A8CAC2F3FD@kernel.crashing.org \
--to=galak@kernel.crashing.org \
--cc=dale@farnsworth.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).