Random "Kernel panic - not syncing" with cirros 0.3.5 image

Bug #1737039 reported by Matt Riedemann
22
This bug affects 3 people
Affects Status Importance Assigned to Milestone
OpenStack-Gate
Confirmed
Undecided
Unassigned

Bug Description

http://logs.openstack.org/22/518022/8/check/legacy-tempest-dsvm-neutron-full/81721fe/job-output.txt.gz#_2017-11-30_21_57_15_838147

2017-11-30 21:57:15.837682 | primary | [ 1.052065] ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1
2017-11-30 21:57:15.837744 | primary | [ 1.064065] ..MP-BIOS bug: 8254 timer not connected to IO-APIC
2017-11-30 21:57:15.837788 | primary | [ 1.064065] ...trying to set up timer (IRQ0) through the 8259A ...
2017-11-30 21:57:15.837829 | primary | [ 1.064065] ..... (found apic 0 pin 2) ...
2017-11-30 21:57:15.837858 | primary | [ 1.072066] ....... failed.
2017-11-30 21:57:15.837895 | primary | [ 1.072066] ...trying to set up timer as Virtual Wire IRQ...
2017-11-30 21:57:15.837926 | primary | [ 1.080066] ..... failed.
2017-11-30 21:57:15.838036 | primary | [ 1.080066] ...trying to set up timer as ExtINT IRQ...
2017-11-30 21:57:15.838072 | primary | [ 1.092067] ..... failed :(.
2017-11-30 21:57:15.838147 | primary | [ 1.092067] Kernel panic - not syncing: IO-APIC + timer doesn't work! Boot with apic=debug and send a report. Then try booting with the 'noapic' option.
2017-11-30 21:57:15.838181 | primary | [ 1.092067]
2017-11-30 21:57:15.838236 | primary | [ 1.092067] Pid: 1, comm: swapper/0 Not tainted 3.2.0-80-virtual #116-Ubuntu
2017-11-30 21:57:15.838277 | primary | [ 1.092067] Call Trace:
2017-11-30 21:57:15.838311 | primary | [ 1.092067] [<ffffffff8164639e>] panic+0x91/0x1a4
2017-11-30 21:57:15.838361 | primary | [ 1.092067] [<ffffffff81d0b1ae>] setup_IO_APIC+0x651/0x693
2017-11-30 21:57:15.838405 | primary | [ 1.092067] [<ffffffff81d07651>] native_smp_prepare_cpus+0x1c4/0x207
2017-11-30 21:57:15.838439 | primary | [ 1.092067] [<ffffffff81cf9ca4>] kernel_init+0x8c/0x169
2017-11-30 21:57:15.838497 | primary | [ 1.092067] [<ffffffff81669234>] kernel_thread_helper+0x4/0x10
2017-11-30 21:57:15.838560 | primary | [ 1.092067] [<ffffffff81cf9c18>] ? start_kernel+0x3c7/0x3c7
2017-11-30 21:57:15.838620 | primary | [ 1.092067] [<ffffffff81669230>] ? gs_change+0x13/0x13

Looks like we've been using cirros 0.3.5 for awhile now:

https://github.com/openstack-dev/devstack/commit/9f2dcd333103553626db1924a019e151e3e7252e

http://logstash.openstack.org/#dashboard/file/logstash.json?query=message%3A%5C%22Kernel%20panic%20-%20not%20syncing%5C%22%20AND%20message%3A%5C%22timer%20doesn't%20work%5C%22%20AND%20tags%3A%5C%22console%5C%22&from=7d

10 hits in 7 days, check and gate, all failures.

Matt Riedemann (mriedem)
Changed in openstack-gate:
status: New → Confirmed
Revision history for this message
Dr. Jens Harbott (j-harbott) wrote :

Seems this goes back to https://bugs.launchpad.net/cirros/+bug/1312199 , I'll ping smoser.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.