lkml.org 
[lkml]   [2002]   [Nov]   [15]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    /
    Date
    From
    SubjectRe: 2.5.47-ac4 panic on boot.
    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.
    -
    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to majordomo@vger.kernel.org
    More majordomo info at http://vger.kernel.org/majordomo-info.html
    Please read the FAQ at http://www.tux.org/lkml/

    \
     
     \ /
      Last update: 2005-03-22 13:31    [W:0.024 / U:118.980 seconds]
    ©2003-2016 Jasper Spaans. hosted at Digital OceanAdvertise on this site