panic in kjournald

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 ([email protected]) (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 [email protected] i f you experience SMP problems!

"WARNING: MP table in the EBDA can be UNSAFE, contact [email protected] if you experience SMP problems!"

This message merely hints that it is possible that the EBDA or XBDA (Extended Bios Data Area) can be written to which just so happens to be where the MP table is located during boot. Once your system is booted then the EBDA is no longer available and the MP table has been read by the OS.

So if you boot fine then all is good!!!

Earle

The message below is a warning thats really out of date and only affects systems using very old boot loaders - which you wont be on Red Hat 7.3 (or 7.2 for that matter)

If you don't have the 7.3 errata kernel please upgrade to that