|
Bugzilla – Full Text Bug Listing |
| Summary: | yast2-kdump: Wrong default memory | ||
|---|---|---|---|
| Product: | [openSUSE] openSUSE 10.3 | Reporter: | Bernhard Walle <bwalle> |
| Component: | YaST2 | Assignee: | Jozef Uhliarik <juhliarik> |
| Status: | RESOLVED FIXED | QA Contact: | Jiri Srain <jsrain> |
| Severity: | Normal | ||
| Priority: | P5 - None | ||
| Version: | Beta 1 | ||
| Target Milestone: | --- | ||
| Hardware: | Other | ||
| OS: | Other | ||
| Whiteboard: | |||
| Found By: | Development | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
Bug is fixed in yast2-kdump version 2.15.5 |
On my machine, yast2-kdump suggests to use 128 MiB memory for the crashkernel. That's too much. According to FATE 301682, the algorithm should be: if (number_of_cpus > 16 || memory_size > 16GB) size = 256MB; else if (number_of_cpus > 4 || memory_size > 4GB) size = 128MB; else size = 64MB; That x86_64 machine has exactly 4 GiB of memory and 4 cores, so it should have 64 MiB. I'd even suggest to use 512 MiB of memory always on IA64 since my experience shows that 256 MiB is too less (and IA64 machines tend to be big). So use: if ia64 size = 512MB; else if (number_of_cpus > 16 || memory_size > 16GB) size = 256MB; else if (number_of_cpus > 4 || memory_size > 4GB) size = 128MB; else size = 64MB; That should work. Reading the source code of yast2-kdump, it looks like the module always takes 128 MiB (however, I'm no YaST expert, so maybe I just read the code wrong), so it's no rounding issue but a lack of that "feature".