From: Ralf Baechle <ralf@linux-mips.org>
To: Steve Scott <steve.scott@pioneer-pdt.com>
Cc: linux-mips@linux-mips.org
Subject: Re: bug in kernel_entry?
Date: Fri, 10 Oct 2003 15:23:12 +0200 [thread overview]
Message-ID: <20031010132312.GB27103@linux-mips.org> (raw)
In-Reply-To: <021e01c38eb2$4e95f840$2256fea9@janelle>
On Thu, Oct 09, 2003 at 03:11:36PM -0700, Steve Scott wrote:
> kernel_entry initializes the kernel stack pointer 'kernelsp'. But then
> immediately after this clears the bss, which has the side effect of setting
> kernelsp to 0. In our system, on initial entry to cpu_idle(), kernelsp is 0.
Funny this wasn't noticed for so long. Fix is in CVS, thanks for reporting.
Ralf
next prev parent reply other threads:[~2003-10-10 13:23 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-08 22:00 mips 32 bit HIGHMEM support exister99
2003-10-08 22:00 ` exister99
2003-10-09 14:03 ` Ralf Baechle
2003-10-09 22:11 ` bug in kernel_entry? Steve Scott
2003-10-09 22:11 ` Steve Scott
2003-10-10 13:23 ` Ralf Baechle [this message]
2003-10-10 14:59 ` mips 32 bit HIGHMEM support Ralf Baechle
2003-10-13 23:15 ` 64 bit kernel in the name of HIGHMEM exister99
2003-10-13 23:15 ` exister99
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=20031010132312.GB27103@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=linux-mips@linux-mips.org \
--cc=steve.scott@pioneer-pdt.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