Uploaded image for project: 'CernVM'
  1. CernVM
  2. CVM-872

cvmfs-server always crashes on reboot.

    XMLWordPrintable

Details

    • Bug
    • Resolution: Not Needed
    • High
    • None
    • None
    • CVMFS
    • None
    • x86_64-slc6-gcc48-opt

    Description

      When ever a 2.1.20 cvmfs-server host is rebooted via a normal

      /sbin/shutdown -r now

      it always crashes as below.

      While clearly harmless may be worth looking at.

      abrt_version:   2.0.8
      cmdline:        ro root=/dev/mapper/VolGroup00-LogVol00 rd_NO_LUKS console=ttyS0,115200 console=tty0 LANG=en_US.UTF-8 rd_NO_MD SYSFONT=latarcyrheb-sun16 rd_LVM_LV=VolGroup00/LogVol01 rd_LVM_LV=VolGroup00/LogVol00  KEYBOARDTYPE=pc KEYTABLE=us rd_NO_DM crashkernel=129M@0M
      hostname:       lxcvmfs52.cern.ch
      kernel:         2.6.32-504.23.4.el6.aufs21.x86_64
      last_occurrence: 1435649368
      not-reportable: The backtrace does not contain enough meaningful function frames to be reported. It is annoying but it does not necessary signalize a problem with your computer. ABRT will not allow you to create a report in a bug tracking system but you can contact kernel maintainers via e-mail.
      time:           Tue 30 Jun 2015 09:20:19 AM CEST
       
      sosreport.tar.xz: Binary file, 1213704 bytes
       
      backtrace:
      :WARNING: at arch/x86/kernel/cpu/perf_event_amd.c:701 amd_pmu_init+0x181/0x1f2() (Not tainted)
      :Hardware name: OpenStack Nova
      :Odd, counter constraints enabled but no core perfctrs detected!
      :Modules linked in:
      :Pid: 1, comm: swapper Not tainted 2.6.32-504.23.4.el6.aufs21.x86_64 #1
      :Call Trace:
      :[<ffffffff81074e47>] ? warn_slowpath_common+0x87/0xc0
      :[<ffffffff81c35021>] ? init_hw_perf_events+0x0/0x4bb
      :[<ffffffff81074f36>] ? warn_slowpath_fmt+0x46/0x50
      :[<ffffffff81c3565d>] ? amd_pmu_init+0x181/0x1f2
      :[<ffffffff81c35060>] ? init_hw_perf_events+0x3f/0x4bb
      :[<ffffffff81c35021>] ? init_hw_perf_events+0x0/0x4bb
      :[<ffffffff8100204c>] ? do_one_initcall+0x3c/0x1d0
      :[<ffffffff81c2a762>] ? kernel_init+0x119/0x2f7
      :[<ffffffff8100969d>] ? __switch_to+0x7d/0x320
      :[<ffffffff8100c28a>] ? child_rip+0xa/0x20
      :[<ffffffff81c2a649>] ? kernel_init+0x0/0x2f7
      :[<ffffffff8100c280>] ? child_rip+0x0/0x20

      Hopefully you can reproduce but here is an crash dump.

      Attachments

        Activity

          People

            rmeusel Rene Meusel (Inactive)
            straylen Steve Traylen
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: