Bug 120995 - 10.0 Live DVD doesn't boot with 224Mb RAM
Summary: 10.0 Live DVD doesn't boot with 224Mb RAM
Status: RESOLVED INVALID
Alias: None
Product: SUSE LINUX 10.0
Classification: openSUSE
Component: Kernel (show other bugs)
Version: Final
Hardware: x86 All
: P5 - None : Minor
Target Milestone: ---
Assignee: Hubert Mantel
QA Contact: E-mail List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-10-07 15:09 UTC by Andreas Hasenack
Modified: 2005-10-11 12:11 UTC (History)
0 users

See Also:
Found By: Other
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---


Attachments
cat /proc/cpuinfo (1.00 KB, text/plain)
2005-10-07 16:51 UTC, Andreas Hasenack
Details
dmesg output (13.61 KB, text/plain)
2005-10-07 16:52 UTC, Andreas Hasenack
Details
free output (230 bytes, text/plain)
2005-10-07 16:52 UTC, Andreas Hasenack
Details
lspci -v output (3.22 KB, text/plain)
2005-10-07 16:52 UTC, Andreas Hasenack
Details
oom-killer.jpg (90.70 KB, image/jpeg)
2005-10-07 18:33 UTC, Andreas Hasenack
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Andreas Hasenack 2005-10-07 15:09:00 UTC
I tried to boot the recent 10.0 Live DVD in a Pentium 4 HT 3GHz with 256Mb of
RAM (32Mb shared, thus the 224Mb figure) but it gives an Out Of Memory error
right after the cloop message.
I never saw before a Live CD/DVD require more than 224Mb of RAM so it may be a bug.
Comment 1 Klaus Kämpf 2005-10-07 15:29:39 UTC
iirc, the kernel can't automaticall detect shared ram, so you must boot with 
"mem=224m". 
 
-> kernel 
Comment 2 Andreas Hasenack 2005-10-07 16:15:28 UTC
I'll try that option and report back.
Comment 3 Andreas Hasenack 2005-10-07 16:37:15 UTC
Tried with "mem=224m" and "mem=220M" and got the same error. I may post some
pictures later. The error is right after the first "cloop" line and starts with
"oom-killer". It's difficult to write it down because it keeps happening (for
the "cp" process, "rm" and others I couldn't write down).

I'll try to deactivate graphical boot now to see how much memory the kernel is
recognizing on this machine (it's at the very top of the screen I think and I
can't see it because it takes some time to switch to verbose mode).
Comment 4 Andreas Hasenack 2005-10-07 16:51:00 UTC
It scrolls off too fast.

Anyway, I'm attaching some info about the machine (lspci, cpuinfo, etc) when
booted into somewhing else.
Comment 5 Andreas Hasenack 2005-10-07 16:51:43 UTC
Created attachment 51824 [details]
cat /proc/cpuinfo
Comment 6 Andreas Hasenack 2005-10-07 16:52:17 UTC
Created attachment 51835 [details]
dmesg output
Comment 7 Andreas Hasenack 2005-10-07 16:52:28 UTC
Created attachment 51836 [details]
free output
Comment 8 Andreas Hasenack 2005-10-07 16:52:41 UTC
Created attachment 51837 [details]
lspci -v output
Comment 9 Andreas Hasenack 2005-10-07 16:59:25 UTC
I also tried with other values lower than 224m (such as 220m), same error.
Comment 10 Andreas Hasenack 2005-10-07 18:33:19 UTC
Created attachment 51937 [details]
oom-killer.jpg
Comment 11 Klaus Kämpf 2005-10-10 06:39:44 UTC
dmesg shows: 
"Linux version 2.6.12-12mdksmp (apatard@n1.mandriva.com) (gcc version 4.0.1 
(4.0.1-5mdk for Mandriva Linux release 2006.0))" 
 
Please use the SUSE kernel compiled with the SUSE compiler for SUSE 
bugreports. 
Comment 12 Andreas Hasenack 2005-10-10 12:15:58 UTC
(In reply to comment #11)
> dmesg shows: 
> "Linux version 2.6.12-12mdksmp (apatard@n1.mandriva.com) (gcc version 4.0.1 
> (4.0.1-5mdk for Mandriva Linux release 2006.0))" 
>  
> Please use the SUSE kernel compiled with the SUSE compiler for SUSE 
> bugreports. 

Did you even look at the fscking screen shot? The fscking suse system won't even
boot!
Comment 13 Hubert Mantel 2005-10-10 12:39:15 UTC
256 MB of RAM is required for the Live CD. So the "fscking suse system" won't
work on your "fscking hardware". Thanks for the nice words and the invalid "bug"
report.
Comment 14 Andreas Hasenack 2005-10-10 12:44:58 UTC
You are welcome. Just don't assume all bug reporters are idiots like was done
comment #11. The first sentence of your comment #13 would have settled this
nicely (I can live with this restriction: see my last sentence in comment #1),
but now I obviously won't care anymore to report bugs.
Comment 15 Hubert Mantel 2005-10-10 13:56:13 UTC
I don't assume all bug reporters are idiots. I did not even write comment #11. I
don't care whether you are filing bug reports or not. But I'm sure I won't work
on reports that use insulting language. Now go somewhere else and don't waste my
time with your whining and your oh-so-cool "fscking" language. I have some
babies at home, don't need that at work too. If you cannot hehave, just shut up!