[Bug 651370] Re: ec2 kernel crash invalid opcode 0000 [#1]

Mikael Gueck 651370 at bugs.launchpad.net
Wed Oct 27 20:37:02 UTC 2010


Brandon's and Scott's workaround works for me partly, but the kernel on
an instance started in such a way seems to detect only 32 GB of memory
even for a m2.4xlarge instance which should have 68.4 GB available,
according to the EC2 instances page. Is this a side-effect of the
workaround, or a completely separate bug?

Maveric results:
ubuntu at ip-10-230-9-87:~$ uname -a
Linux ip-10-230-9-87 2.6.35-22-virtual #35-Ubuntu SMP Sat Oct 16 23:19:29 UTC 2010 x86_64 GNU/Linux
ubuntu at ip-10-230-9-87:~$ ec2metadata --instance-type
m2.4xlarge
ubuntu at ip-10-230-9-87:~$ free
             total       used       free     shared    buffers     cached
Mem:      32810684     667628   32143056          0       6444      32152
-/+ buffers/cache:     629032   32181652
Swap:            0          0          0

Expected results (from a SUSE 11 guest):
ip-10-230-45-187:~ # uname -a
Linux ip-10-230-45-187 2.6.32.19-0.3-ec2 #1 SMP 2010-09-17 20:28:21 +0200 x86_64 x86_64 x86_64 GNU/Linux
ip-10-230-45-187:~ # curl http://169.254.169.254/latest/meta-data/instance-type
m2.4xlarge
ip-10-230-45-187:~ # free
             total       used       free     shared    buffers     cached
Mem:      71705116    2361584   69343532          0      10972     126424
-/+ buffers/cache:    2224188   69480928
Swap:            0          0          0

-- 
ec2 kernel crash invalid opcode 0000 [#1]
https://bugs.launchpad.net/bugs/651370
You received this bug notification because you are a member of Kernel
Bugs, which is subscribed to linux in ubuntu.




More information about the kernel-bugs mailing list