From: Paul Mundt <lethal@linux-sh.org>
To: linux-sh@vger.kernel.org
Subject: Re: 2.6.30-rc4-git: timer-related oops
Date: Thu, 07 May 2009 09:19:06 +0000 [thread overview]
Message-ID: <20090507091906.GA26125@linux-sh.org> (raw)
In-Reply-To: <20090504091430.GA30660@linux-sh.org>
On Tue, May 05, 2009 at 07:44:48AM +0200, Manuel Lauss wrote:
> On Mon, May 04, 2009 at 11:41:38PM +0900, Paul Mundt wrote:
> > On Mon, May 04, 2009 at 04:14:46PM +0200, Manuel Lauss wrote:
> > > On Mon, May 04, 2009 at 11:15:23AM +0200, Manuel Lauss wrote:
> > > > Hello!
> > > >
> > > > Current -git (and a few revisions before that) oops when kernel tries to
> > > > mount nfsroot. Anyone else seeing this? (system is SH7760; I disabled
> > > > almost all of my platform code to rule out a screwup on my part. The code
> > > > works on 2.6.29).
> > >
> > > Gaah, found it: CONFIG_4KSTACKS=y is the culprit. Removing it gives me a
> > > nicely working system again.
> > >
> > > Sorry for the noise!
> > >
> > That is interesting, I run with 4k stacks all the time without incident
> > on most configurations, with ample space to spare. Have you tried turning
> > on stack usage reporting to see where it is all going?
>
> There are no warnings regarding stack overflows, and all in-kernel stack
> users have plenty (>P%) stack space left.
>
> The _real_ culprit is actually CONFIG_IRQSTACKS=y; 4k stacks on its own is
> fine, but with irqstacks enabled the kernel blows up with random oopses as
> soon as it goes on to start the init process.
>
It looks like there is still some stack corruption going on here, I will
have to debug it some more. I've added a depends on BROKEN for now so
this doesn't get accidentally selected.
prev parent reply other threads:[~2009-05-07 9:19 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-04 9:14 2.6.30-rc4-git: timer-related oops Paul Mundt
2009-05-04 9:15 ` Manuel Lauss
2009-05-04 10:07 ` Manuel Lauss
2009-05-04 12:46 ` Luca Santini
2009-05-04 13:54 ` Manuel Lauss
2009-05-04 14:14 ` Manuel Lauss
2009-05-04 14:41 ` Paul Mundt
2009-05-04 15:43 ` Manuel Lauss
2009-05-05 5:44 ` Manuel Lauss
2009-05-07 9:19 ` Paul Mundt [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=20090507091906.GA26125@linux-sh.org \
--to=lethal@linux-sh.org \
--cc=linux-sh@vger.kernel.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