[lkml]   [2001]   [Dec]   [28]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
    SubjectRE: 2.4.17 still croaks under heavy load
    No RAID1 on disks.

    Here's /proc/meminfo within 1 minute of the box dying last night:

    total: used: free: shared: buffers: cached:
    Mem: 1054371840 1044684800 9687040 0 7802880 834752512
    Swap: 535797760 7626752 528171008
    MemTotal: 1029660 kB
    MemFree: 9460 kB
    MemShared: 0 kB
    Buffers: 7620 kB
    Cached: 811872 kB
    SwapCached: 3316 kB
    Active: 231880 kB
    Inactive: 747344 kB
    HighTotal: 131072 kB
    HighFree: 1028 kB <--------- See comment below
    LowTotal: 898588 kB
    LowFree: 8432 kB
    SwapTotal: 523240 kB
    SwapFree: 515792 kB

    The HighFree value was at 2044 for the prior hour. It went to 1028
    within 1 minute of the box freezing. Out of HighMem???

    Here's vmstat within 30 seconds of freezing:

    procs memory swap io system
    r b w swpd free buff cache si so bi bo in cs us
    sy id
    1 0 0 7448 9536 7616 812092 0 0 932 2 235 577 50
    1 49

    Seems VM related.


    -----Original Message-----
    From: Matti Aarnio []
    Sent: Friday, December 28, 2001 2:02 AM
    To: Phil Oester
    Subject: Re: 2.4.17 still croaks under heavy load

    On Thu, Dec 27, 2001 at 11:06:50PM -0800, Phil Oester wrote:
    > Have a webserver running Zope (specifically the ZEO db) which dies
    > few days with no messages in syslog. Locks up so tight a powercycle
    > required to recover. System has 1gb RAM, 2xSMP, kernel configured
    > 4gb highmem.

    Do you have RAID1 on the disks ?
    Apparently "noapic" option helps, e.g. breaking the SYMMETRIC part of
    You may also try "nmi_watchdog=1", if you have serial console attached
    to the box for kernel message logging (and command).

    > Since the kernel doesn't provide any info in syslog when it dies, I
    > ran a vmstat 30 to a file and waited for the next untimely demise.
    > Here's what happened when it died last time. Note the sudden surge in
    > disk activity (bi)

    Yes, looks familiar. My hangups have been during high disc activity
    My box is located into a place into which I have difficult access,
    I can't use it to collect the debug data, and do magics (press reset)
    to recover.

    > I'd be more than willing to collect any other data required here, just
    > let me know what would be of assistance. Note though that I only have
    > remote access to this box, so getting magic sysrq info could be
    > difficult/impossible (tho I do have console access if that helps).
    > Thanks,
    > Phil Oester

    /Matti Aarnio

    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to
    More majordomo info at
    Please read the FAQ at

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