[Bug 613273] Re: kernel panic on ec2 in system_call_fastpath

jMCg 613273 at bugs.launchpad.net
Wed Oct 19 14:05:31 UTC 2011


There was a concern that udev is still running at this point, so I added a `ps` right after `udevadm control  --timeout=61 --exit` and the result is this:
    Begin: Running /scripts/local-bottom ... done.
    done.
    Begin: Running /scripts/init-bottom ...   PID USER       VSZ STAT COMMAND
        1 0         4460 S    /bin/sh /init ro
        2 0            0 SW   [kthreadd]
        3 0            0 SW   [ksoftirqd/0]
        4 0            0 SW   [kworker/0:0]
        5 0            0 SW   [kworker/u:0]
        6 0            0 SW   [migration/0]
        7 0            0 SW   [migration/1]
        8 0            0 SW   [kworker/1:0]
        9 0            0 SW   [ksoftirqd/1]
       10 0            0 SW   [kworker/0:1]
       11 0            0 SW<  [cpuset]
       12 0            0 SW<  [khelper]
       13 0            0 SW<  [netns]
       14 0            0 SW   [sync_supers]
       15 0            0 SW   [kworker/u:1]
       16 0            0 SW   [bdi-default]
       17 0            0 SW<  [kintegrityd]
       18 0            0 SW<  [kblockd]
       19 0            0 SW<  [ata_sff]
       20 0            0 SW   [khubd]
       21 0            0 SW<  [md]
       22 0            0 SW   [kworker/1:1]
       24 0            0 SW   [khungtaskd]
       25 0            0 SW   [kswapd0]
       26 0            0 SWN  [ksmd]
       27 0            0 SWN  [khugepaged]
       28 0            0 DW   [fsnotify_mark]
       29 0            0 SW   [ecryptfs-kthrea]
       30 0            0 SW<  [crypto]
       38 0            0 SW<  [kthrotld]
       39 0            0 SW   [scsi_eh_0]
       40 0            0 SW   [scsi_eh_1]
       41 0            0 SW   [kworker/u:2]
       42 0            0 SW   [kworker/u:3]
      298 0            0 SW   [jbd2/vda-8]
      299 0            0 SW<  [ext4-dio-unwrit]
      303 0         4456 S    /bin/sh -e /scripts/init-bottom/udev
      305 0         4460 R    ps
    done.
    run-init: nuking initramfs contents: Directory not empty
    [    6.397128] Kernel panic - not syncing: Attempted to kill init!
    [    6.397849] Pid: 1, comm: run-init Not tainted 3.0.0-12-server #20-Ubuntu
    [    6.398715] Call Trace:
    [    6.399018]  [<ffffffff815e8184>] panic+0x91/0x194
    [    6.399609]  [<ffffffff810626c5>] forget_original_parent+0x245/0x250
    [    6.400424]  [<ffffffff810626e7>] exit_notify+0x17/0x150
    [    6.401102]  [<ffffffff81062feb>] do_exit+0x1fb/0x440
    [    6.401660]  [<ffffffff81063387>] sys_exit+0x17/0x20
    [    6.402255]  [<ffffffff81606c02>] system_call_fastpath+0x16/0x1b

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to udev in Ubuntu.
https://bugs.launchpad.net/bugs/613273

Title:
  kernel panic on ec2 in system_call_fastpath

Status in “initramfs-tools” package in Ubuntu:
  Invalid
Status in “linux” package in Ubuntu:
  Invalid
Status in “udev” package in Ubuntu:
  Fix Released
Status in “initramfs-tools” source package in Maverick:
  Invalid
Status in “linux” source package in Maverick:
  Invalid
Status in “udev” source package in Maverick:
  Triaged
Status in “initramfs-tools” source package in Natty:
  Invalid
Status in “linux” source package in Natty:
  Invalid
Status in “udev” source package in Natty:
  Triaged

Bug description:
  In testing alpha-3 build 20100813.2, I found the following kernel oops:
  [    0.473264] Kernel panic - not syncing: Attempted to kill init!^M
  [    0.473277] Pid: 1, comm: run-init Not tainted 2.6.35-14-virtual #19-Ubuntu^M
  [    0.473284] Call Trace:^M
  [    0.473294]  [<ffffffff815a0109>] panic+0x90/0x111^M
  [    0.473303]  [<ffffffff81006b1b>] ? __raw_callee_save_xen_irq_enable+0x11/0x26^M
  [    0.473312]  [<ffffffff8106276d>] forget_original_parent+0x33d/0x350^M
  [    0.473318]  [<ffffffff81061b94>] ? put_files_struct+0xc4/0xf0^M
  [    0.473325]  [<ffffffff8106279b>] exit_notify+0x1b/0x190^M
  [    0.473330]  [<ffffffff810640a5>] do_exit+0x1c5/0x3f0^M
  [    0.473336]  [<ffffffff81006afd>] ? __raw_callee_save_xen_irq_disable+0x11/0x1e^M
  [    0.473343]  [<ffffffff810643d7>] sys_exit+0x17/0x20^M
  [    0.473349]  [<ffffffff8100a0f2>] system_call_fastpath+0x16/0x1b^M

  This happened only once in my testing so far today (dozens of boots).
  I'm attaching the console log of failed instance.  The instance that reported this bug is same ami/region different instance.

  ProblemType: Bug
  DistroRelease: Ubuntu 10.10
  Package: linux-image-2.6.35-14-virtual 2.6.35-14.19
  Regression: Yes
  Reproducible: No
  ProcVersionSignature: User Name 2.6.35-14.19-virtual 2.6.35
  Uname: Linux 2.6.35-14-virtual x86_64
  AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access /dev/snd/: No such file or directory
  AplayDevices: Error: [Errno 2] No such file or directory
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory
  CurrentDmesg: [   12.900041] eth0: no IPv6 routers present
  Date: Wed Aug  4 01:19:11 2010
  Ec2AMI: ami-09c3bc5b
  Ec2AMIManifest: ubuntu-images-testing-ap-southeast-1/ubuntu-maverick-daily-amd64-server-20100803.2.manifest.xml
  Ec2AvailabilityZone: ap-southeast-1b
  Ec2InstanceType: m1.large
  Ec2Kernel: aki-11d5aa43
  Ec2Ramdisk: unavailable
  Frequency: Once a week.
  Lspci:
   
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  ProcCmdLine: root=LABEL=uec-rootfs ro
  ProcEnviron:
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcModules: acpiphp 18752 0 - Live 0xffffffffa0000000
  SourcePackage: linux

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/613273/+subscriptions




More information about the foundations-bugs mailing list