Comment 67 for bug 634487

"US-West-2 availability region" I suggest is a misnomer.
There are availability zones us-west-2a and us-west-2b in the us-west-2 region.

On 9 November 2011 15:33, Ben Howard <email address hidden> wrote:
> On 2011-11-08, Amazon launched the US-West-2 availability region.  (
> http://aws.typepad.com/aws/2011/11/now-open-us-west-portland-region.html
> )
>
> This region appears to NOT be affected by the bug. If you are
> experiencing this bug and are not bound to a particular EC2 region,
> please try the US-West-2 region as a work around.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/634487
>
> Title:
>  t1.micro instance hangs when installing java
>
> Status in Release Notes for Ubuntu:
>  Fix Released
> Status in “linux” package in Ubuntu:
>  Confirmed
> Status in “linux-ec2” package in Ubuntu:
>  Invalid
> Status in “openjdk-6” package in Ubuntu:
>  Invalid
> Status in “sun-java6” package in Ubuntu:
>  Invalid
> Status in “linux” source package in Lucid:
>  Invalid
> Status in “linux-ec2” source package in Lucid:
>  Confirmed
> Status in “openjdk-6” source package in Lucid:
>  Invalid
> Status in “sun-java6” source package in Lucid:
>  Invalid
> Status in “linux” source package in Maverick:
>  Confirmed
> Status in “linux-ec2” source package in Maverick:
>  Invalid
> Status in “openjdk-6” source package in Maverick:
>  Invalid
> Status in “sun-java6” source package in Maverick:
>  Invalid
> Status in “linux” source package in Natty:
>  Confirmed
> Status in “linux-ec2” source package in Natty:
>  Invalid
> Status in “openjdk-6” source package in Natty:
>  Invalid
> Status in “sun-java6” source package in Natty:
>  Invalid
>
> Bug description:
>  Binary package hint: cloud-init
>
>  I booted the 32bit EBS lucid AMI (ami-1234de7b) for a t1.micro
>  instance. I attempted to install Sun Java. The instance hung during
>  the install. Repros every time. Only repros on t1.micro instances. I
>  tried adding swap in case it was an out-of-memory condition, and it
>  still repro'd. No reboots or anything else like that were involved so
>  it's not the same issue as #634102
>
>  Console log snippet (full one attached):
>
>  [  525.195499] ------------[ cut here ]------------
>  [  525.195515] kernel BUG at /build/buildd/linux-ec2-2.6.32/arch/x86/mm/hypervisor.c:461!
>  [  525.195522] invalid opcode: 0000 [#1] SMP
>  [  525.195527] last sysfs file: /sys/kernel/uevent_seqnum
>  [  525.195531] Modules linked in: ipv6
>  [  525.195537]
>  [  525.195541] Pid: 8663, comm: java Not tainted (2.6.32-308-ec2 #15-Ubuntu)
>  [  525.195545] EIP: 0061:[<c0118550>] EFLAGS: 00010282 CPU: 0
>  [  525.195553] EIP is at T.566+0x150/0x180
>  [  525.195557] EAX: ffffffea EBX: c1f17e70 ECX: 00000002 EDX: 00000000
>  [  525.195561] ESI: 0d537000 EDI: 00000004 EBP: c1f17ebc ESP: c1f17e60
>  [  525.195565]  DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0069
>  [  525.195580] Process java (pid: 8663, ti=c1f16000 task=e5373200 task.ti=c1f16000)
>  [  525.195588] Stack:
>  [  525.195591]  c103a020 c1f17ee0 80000000 00000061 0000000e 00000000 c1c81000 0d537061
>  [  525.195603] <0> 80000004 00000000 00000000 00000040 00000001 ffffffea c1f17ee0 00000001
>  [  525.195617] <0> 00000000 00007ff0 00000000 00000000 0d537001 00000004 c14e5000 c1f17efc
>  [  525.195632] Call Trace:
>  [  525.195640]  [<c01188dd>] ? xen_l3_entry_update+0x12d/0x1b0
>  [  525.195647]  [<c01145de>] ? pud_populate+0x9e/0xc0
>  [  525.195654]  [<c01aed59>] ? __pmd_alloc+0x99/0xa0
>  [  525.195659]  [<c01b2eb9>] ? handle_mm_fault+0x509/0x5b0
>  [  525.195665]  [<c01b7b2a>] ? do_munmap+0x22a/0x2b0
>  [  525.195672]  [<c05370f9>] ? do_page_fault+0x119/0x340
>  [  525.195677]  [<c0536fe0>] ? do_page_fault+0x0/0x340
>  [  525.195683]  [<c0535525>] ? error_code+0x3d/0x44
>  [  525.195687] Code: c3 64 a0 cc 40 6f c0 84 c0 75 28 8b 5d a8 b9 01 00 00 00 31 d2 be f0 7f 00 00 e8 dc 8a fe ff 85 c0 79 d6 0f 0b eb fe 8d 74 26 00 <0f> 0b eb fe 0f 0b eb fe 8b 45 a8 31 c9 ba 01 00 00 00 c7 04 24
>  [  525.195754] EIP: [<c0118550>] T.566+0x150/0x180 SS:ESP 0069:c1f17e60
>  [  525.195769] ---[ end trace 9706b235d81a7968 ]---
>
>
>  Script which can 100% repro the problem:
>
>  #!/bin/bash
>
>  export DEBIAN_FRONTEND=noninteractive
>  add-apt-repository "deb http://archive.canonical.com/ lucid partner"
>  apt-get update
>  echo 'sun-java6-bin   shared/accepted-sun-dlj-v1-1    boolean true
>  sun-java6-jdk   shared/accepted-sun-dlj-v1-1    boolean true
>  sun-java6-jre   shared/accepted-sun-dlj-v1-1    boolean true
>  sun-java6-jre   sun-java6-jre/stopthread        boolean true
>  sun-java6-jre   sun-java6-jre/jcepolicy note
>  sun-java6-bin   shared/present-sun-dlj-v1-1     note
>  sun-java6-jdk   shared/present-sun-dlj-v1-1     note
>  sun-java6-jre   shared/present-sun-dlj-v1-1     note
>  '|debconf-set-selections
>  apt-get -y install sun-java6-jdk
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu-release-notes/+bug/634487/+subscriptions
>