Symmetric Multiprocessing (SMP) development
 help / color / mirror / Atom feed
From: Tom Harding <tom_harding@worldpac.com>
To: linux-smp@vger.kernel.org
Subject: panic in kjournald
Date: Sat, 03 Aug 2002 07:38:41 -0700	[thread overview]
Message-ID: <3D4BEAF1.9060605@worldpac.com> (raw)

As requested, I'm contacting you with an SMP problem.  The system (an 
IBM xSeries 350) has been running fine under load for several weeks but 
this morning there was a kernel panic in kjournald.  Unfortunately I 
don't have any output from it.  Could this be related to the worry 
below, or is it more likely a kjournald bug?


Linux version 2.4.18-3smp (bhcompile@daffy.perf.redhat.com) (gcc version 
2.96 20
000731 (Red Hat Linux 7.3 2.96-110)) #1 SMP Thu Apr 18 07:27:31 EDT 2002
BIOS-provided physical RAM map:
 BIOS-e820: 0000000000000000 - 000000000009d000 (usable)
 BIOS-e820: 000000000009d000 - 00000000000a0000 (reserved)
 BIOS-e820: 00000000000e0000 - 0000000000100000 (reserved)
 BIOS-e820: 0000000000100000 - 000000007fff9380 (usable)
 BIOS-e820: 000000007fff9380 - 0000000080000000 (ACPI data)
 BIOS-e820: 00000000fec00000 - 00000000fec01000 (reserved)
 BIOS-e820: 00000000fee00000 - 00000000fee01000 (reserved)
 BIOS-e820: 00000000fff80000 - 0000000100000000 (reserved)
1151MB HIGHMEM available.
found SMP MP-table at 0009e1d0
hm, page 0009e000 reserved twice.
hm, page 0009f000 reserved twice.
hm, page 0009e000 reserved twice.
hm, page 0009f000 reserved twice.
WARNING: MP table in the EBDA can be UNSAFE, contact 
linux-smp@vger.kernel.org i
f you experience SMP problems!



             reply	other threads:[~2002-08-03 14:38 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-08-03 14:38 Tom Harding [this message]
2002-08-03 15:50 ` panic in kjournald Earle Nietzel
2002-08-03 17:01 ` Alan Cox

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=3D4BEAF1.9060605@worldpac.com \
    --to=tom_harding@worldpac.com \
    --cc=linux-smp@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