All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stephan von Krawczynski <skraw@ithnet.com>
To: linux-kernel <linux-kernel@vger.kernel.org>
Subject: BUG REPORT: 2.4.20 System freeze at 00:00:00 Jan 1 2003
Date: Wed, 1 Jan 2003 01:04:50 +0100	[thread overview]
Message-ID: <20030101010450.17895f47.skraw@ithnet.com> (raw)

Hello all,

I am really unsure what to think about the system freeze I just experienced on a very low loaded system:

Jan  1 00:00:00 core-2 kernel: Unable to handle kernel NULL pointer dereference at virtual address 00000008
Jan  1 00:00:00 core-2 kernel:  printing eip:
Jan  1 00:00:00 core-2 kernel: c0136a7b
Jan  1 00:00:00 core-2 kernel: *pde = 00000000
Jan  1 00:00:00 core-2 kernel: Oops: 0000
Jan  1 00:00:00 core-2 kernel: CPU:    0
Jan  1 00:00:00 core-2 kernel: EIP:    0010:[fput+27/304]    Not tainted
Jan  1 00:00:00 core-2 kernel: EIP:    0010:[<c0136a7b>]    Not tainted
Jan  1 00:00:00 core-2 kernel: EFLAGS: 00010292
Jan  1 00:00:00 core-2 kernel: eax: f675fee0   ebx: f675fee0   ecx: f62333c0   edx: f600bf4c
Jan  1 00:00:00 core-2 kernel: esi: 00000000   edi: fffffe00   ebp: 00000000   esp: f600bf7c
Jan  1 00:00:00 core-2 kernel: ds: 0018   es: 0018   ss: 0018
Jan  1 00:00:00 core-2 kernel: Process run-crons (pid: 859, stackpage=f600b000)
Jan  1 00:00:00 core-2 kernel: Stack: f6233428 00000000 00000000 f675fee0 fffffe00 00000080 c0135be1 f675eee0
Jan  1 00:00:00 core-2 kernel:        bffff9e0 00000080 f675ef00 00000000 00000000 f600a000 00000080 bffff9e0
Jan  1 00:00:00 core-2 kernel:        bffff9b8 c010741f 00000003 bffff9e0 00000080 00000080 bffff9e0 bffff9b8
Jan  1 00:00:00 core-2 kernel: Call Trace:    [sys_read+241/320] [system_call+51/56]
Jan  1 00:00:00 core-2 kernel: Call Trace:    [<c0135be1>] [<c010741f>]
Jan  1 00:00:00 core-2 kernel:
Jan  1 00:00:00 core-2 kernel: Code: 8b 7d 08 ff 48 14 0f 94 c0 84 c0 75 18 8b 5c 24 08 8b 74 24

After this the system was just frozen, I did not see any additional info. Just plain dead.
This is kernel 2.4.20. FS is reiser. Distro used is SuSE 8.1. It is a do-nothing system (no load, no plan).
Stood there for about 2 months, now crashed on new year wrap...

-- 
Regards,
Stephan


             reply	other threads:[~2002-12-31 23:56 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-01  0:04 Stephan von Krawczynski [this message]
2003-01-01  0:13 ` BUG REPORT: 2.4.20 System freeze at 00:00:00 Jan 1 2003 James Stevenson

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=20030101010450.17895f47.skraw@ithnet.com \
    --to=skraw@ithnet.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.