public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jose Luis Domingo Lopez <linux-kernel@24x7linux.com>
To: Linux-Kernel <linux-kernel@vger.kernel.org>
Subject: Linux 2.6.10-rc3-bk15 hanged under high load (i386)
Date: Wed, 5 Jan 2005 19:39:48 +0100	[thread overview]
Message-ID: <20050105183947.GA5601@localhost> (raw)

[-- Attachment #1: Type: text/plain, Size: 2344 bytes --]

Hi all:

I have been experiencing kernel crashes for the last couple of weeks, and
now it has happened again, but this time I have some info, hope it helps.

* Problem: box freezes (no panic or other kind of messages in the logs),
  under high load (loadavg up to 10, several "spamassassin" processes 
  doing their job).

* Description: the box just hangs, nothing gets printed in the logs (at the
  time of the crash), SysRq+T, SysRq+M don't dump anything to disk (can't
  verify if they get to the local console, because X was running when the
  box hangs). However, some time (in the order of seconds, maybe a minute
  or so) before the box freezes, I get the following in the logs:

  Jan  5 19:09:52 dardhal kernel: swap_dup: Bad swap file entry 10000000
  Jan  5 19:09:52 dardhal kernel: swap_free: Bad swap file entry 10000000
  Jan  5 19:09:52 dardhal kernel: swap_free: Bad swap file entry 10000000
  Jan  5 19:10:08 dardhal kernel: VM: killing process spamassassin
  Jan  5 19:10:08 dardhal kernel: swap_free: Bad swap offset entry 00730000
  
  (I noticed my incoming email was not being tagged as spam by
  "spamassasin" any more, at least some of it ("spamassassin" configured
  to have several copies running in parallel).

* When I noticed the box didn't respond, I tried several SysRq (T, M), and
  then tried an emergency reboot via SysRq+S, SysRq+U, SysRq+B. It worked
  as expected (root file system seemed to be synced to disk, unmounted,
  and the box rebooted), at least upon reboot the root filesystem was
  clean, as it should be.


I have searched for old kernel logs, to check if some other hang in the
past happened just after a message similar to the ones above. And in fact,
this is the case, but I am not sure if the following was the last time the
box crashed until today. What I know for sure is the following message
(and the crashed it happened just after it) was also with kernel version
2.6.10-rc3-bk15, as happened today.
  
  Dec 29 20:41:38 dardhal kernel: swap_free: Bad swap offset entry 003f0000


Could it be just a defective sector under my swap partition?. Any help
greatly appreciated, please ask for more information if needed.

Greetings,

-- 
Jose Luis Domingo Lopez
Linux Registered User #189436     Debian Linux Sid (Linux 2.6.10-rc3-bk15)


[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

             reply	other threads:[~2005-01-05 18:40 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-05 18:39 Jose Luis Domingo Lopez [this message]
2005-01-05 19:04 ` Linux 2.6.10-rc3-bk15 hanged under high load (i386) Jurriaan on adsl-gate
2005-01-05 20:57   ` Jose Luis Domingo Lopez

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=20050105183947.GA5601@localhost \
    --to=linux-kernel@24x7linux.com \
    --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