boot error after increasing memory - ioremap error

Hi,
after increasing the memory of my PC boot ends with message:
2.450072] ioremap error for 0xfe02f000-0xfe030000, requested by 0x2, got 0x0
→ 10 min later few more messages:
Starting Dracut Emergency Shell …
→ [FAILED]

This happens as soon as the memory is higher than 10 GB. Looks like different combinations up to 10GB (using all 4 memory banks) work well. As well using 2 of the 4 modules together in the first 2 banks (8GB). Hence all 4 moduls seem to be ok.
In all cases (up to 16 GB) the memory is accepted by the PC properly.
After reducing mem boot is ok again.
Suse Memory check (from installation DVD) reports no error.
Similiar a try with installation DVD (42.1 or SLES 11.4) end up in nirvana as soon there is to much memory.

This is a Gigabyte GA-MA69GM-S2H motherbord with AMD Athlon™ 64 X2,

  1. North Bridge Chipset: AMD 690G
  2. South Bridge Chipset: ATI SB600
  3. Super I/O chip: ITE IT8716

The BIOS seems to be up to date, no major changes according to GIGABYTE.
Changes in BIOS settings seem to have no effect on the issue.

Anybody who can advice?
Thanks and kind regards,
Axel

Recommend posting your problem boot entries to a pastebin (eg pastebin.com or paste.opensuse.org).

You can extract only your problem boot log entries by

  1. First attempt to boot with your full memory which should eventually fail as you describe.
  2. Then, do whatever modifications you need to do to boot successfully.
  3. Assuming the current session is immediately after an attempted fail, you can now run the following which should extract only the failed boot entries and write them to a file “bootlog.txt” wherever your console prompt is located.
journalctl -n 1> bootlog.txt

Of course, you can skip doing another failed boot if you know exactly how many boot attempts ago was a failure and specify that number following “-n”

TSU

-> http://paste.opensuse.org/56387561

-> journalctl does not bring up informations about the fail boot. Looks like the file system is not mounted yet.

Thanks and kind regards,
Axel

You’re supposed to post the contents of bootlog.txt (following my instructions) so that everyone can inspect your bootlog.

Re-posting only your analysis and not the raw data doesn’t move your issue forward…

:slight_smile:

TSU

ok, sorry for confusion.

here the full output after from a failed boot (after the grub screen):
2.459519] ioremap error for 0xfe02f000-0xfe030000, requested by 0x2, got 0x0

→ 10 min later:
Starting Dracut Emergency Shell
Warning: /dev/disc/by-uuid/e7… does not exist
Warning: Boot has failed. To debug this issue add “rd.shell rd.debug” to the kernel command line.
[FAILED] Failed to start Dracut Emergency Shell.
See “systemctl status dracut-emergency.service” for details.
OK ] Started dracut initqueue hook.
Starting dracut pre-mount hook…
OK ] Reached target Remote File Systems (Pre).
OK ] Reached target Remote File Systems.
OK ] Started dracut pre-mount hook.
blinking curser _

**after regular boot:
**journalctl (full list) does not report the desired timestamp of the failboot at all.
journalctl --list-boots does not report the desired timestamp of the failboot at all.

journalctl -b -1 would report the last regular boot.

I guess this not what you need?

Kind regards,
Axel