From: Andrew Morton <akpm@digeo.com>
To: Justin A <ja6447@albany.edu>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.5.47-ac4 panic on boot.
Date: Fri, 15 Nov 2002 00:28:15 -0800 [thread overview]
Message-ID: <3DD4B01F.B3C1DCDC@digeo.com> (raw)
In-Reply-To: 200211150254.25306.ja6447@albany.edu
Justin A wrote:
>
> I did that...
> Disabling PM made it boot:
>
> < CONFIG_PM=y
> < CONFIG_APM=m
> < # CONFIG_APM_IGNORE_USER_SUSPEND is not set
> < CONFIG_APM_DO_ENABLE=y
> < CONFIG_APM_CPU_IDLE=y
> < CONFIG_APM_DISPLAY_BLANK=y
> < # CONFIG_APM_RTC_IS_GMT is not set
> < # CONFIG_APM_ALLOW_INTS is not set
> < # CONFIG_APM_REAL_MODE_POWER_OFF is not set
> ---
> > # CONFIG_PM is not set
>
> I think I still had swsusp on before I disabled PM...I will have to test more
> tomorrow to make sure thats it...
> Perhaps its the CONFIG_APM_CPU_IDLE that did it?
Could be...
> I had tried linux init=/bin/sh, which got to the shell, then 2 seconds later
> paniced, so I have a feeling its the idle thingy:)
slab runs a timer every couple of seconds to drain caches which could
otherwise be wasted-for-ever memory. So it looks like we don't get
to find out about abuse until much later. Damn.
Oh, it'd be interesting to enable memory debugging under the kernel-hacking
menu - that may trap the bug when it's happening.
next prev parent reply other threads:[~2002-11-15 8:21 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-15 5:59 2.5.47-ac4 panic on boot Justin A
2002-11-15 6:33 ` Andrew Morton
2002-11-15 7:54 ` Justin A
2002-11-15 8:28 ` Andrew Morton [this message]
2002-11-15 22:12 ` Justin A
2002-11-15 22:16 ` Andrew Morton
2002-11-15 22:59 ` Justin A
2002-11-15 22:02 ` Samuli Suonpaa
2002-11-15 22:36 ` Justin A
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=3DD4B01F.B3C1DCDC@digeo.com \
--to=akpm@digeo.com \
--cc=ja6447@albany.edu \
--cc=linux-kernel@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