Activity log for bug #418154

Date Who What changed Old value New value Message
2009-08-24 14:29:42 Stefan Bader bug added bug
2009-08-24 14:32:31 Stefan Bader bug task added linux (Ubuntu Hardy)
2009-08-24 14:32:47 Stefan Bader linux (Ubuntu Hardy): importance Undecided High
2009-08-24 14:32:47 Stefan Bader linux (Ubuntu Hardy): status New Triaged
2009-08-24 14:32:47 Stefan Bader linux (Ubuntu Hardy): assignee Stefan Bader (stefan-bader-canonical)
2009-08-24 14:33:08 Stefan Bader linux (Ubuntu): importance Undecided High
2009-08-24 14:33:08 Stefan Bader linux (Ubuntu): status New Fix Released
2009-08-24 14:35:09 Stefan Bader description > While testing Ubuntu 8.04.3 under VMware. We have seen situations when we hit this panic in the guest, during bootup. > " Kernel panic - not syncing: IO-APIC + timer doesn't work! Try using the 'noapic' kernel parameter" > > I had fixed this problem for mainline some time back but I guess I forgot to ask you guys to pick this patch. > The direct port of the mainline commit (3da757daf86e498872855f0b5e101f763ba79499) gave a couple of trivial > merge conflicts for hardy. The backport (lpj_tsc.patch) of the patch which applies to hardy-git is attached. > > Many user's might hit this when they start running 8.04.3 guests, so it would be great if you could apply the fix at your earliest. Please note that, with VMware hypervisor specific changes which went in the 8.04.3 > kernel (tsc improvements) the likelihood of anybody hitting this on AMD systems is slightly increased. > Other Newer Ubuntu releases already have the fix from mainline. From Alok Kataria: While testing Ubuntu 8.04.3 under VMware. We have seen situations when we hit this panic in the guest, during bootup. "Kernel panic - not syncing: IO-APIC + timer doesn't work! Try using the 'noapic' kernel parameter" I had fixed this problem for mainline some time back but I guess I forgot to ask you guys to pick this patch. The direct port of the mainline commit (3da757daf86e498872855f0b5e101f763ba79499) gave a couple of trivial merge conflicts for hardy. The backport (lpj_tsc.patch) of the patch which applies to hardy-git is attached. Many user's might hit this when they start running 8.04.3 guests, so it would be great if you could apply the fix at your earliest. Please note that, with VMware hypervisor specific changes which went in the 8.04.3 kernel (tsc improvements) the likelihood of anybody hitting this on AMD systems is slightly increased. Other Newer Ubuntu releases already have the fix from mainline.
2009-08-26 15:06:51 Stefan Bader description From Alok Kataria: While testing Ubuntu 8.04.3 under VMware. We have seen situations when we hit this panic in the guest, during bootup. "Kernel panic - not syncing: IO-APIC + timer doesn't work! Try using the 'noapic' kernel parameter" I had fixed this problem for mainline some time back but I guess I forgot to ask you guys to pick this patch. The direct port of the mainline commit (3da757daf86e498872855f0b5e101f763ba79499) gave a couple of trivial merge conflicts for hardy. The backport (lpj_tsc.patch) of the patch which applies to hardy-git is attached. Many user's might hit this when they start running 8.04.3 guests, so it would be great if you could apply the fix at your earliest. Please note that, with VMware hypervisor specific changes which went in the 8.04.3 kernel (tsc improvements) the likelihood of anybody hitting this on AMD systems is slightly increased. Other Newer Ubuntu releases already have the fix from mainline. SRU justification: Impact: Panic in vmware guest running Hardy (see below) Fix: Backport from upstream to make sure of the correct loops per jiffie value. Testcase: Booting guest on a busy host --- From Alok Kataria: While testing Ubuntu 8.04.3 under VMware. We have seen situations when we hit this panic in the guest, during bootup. "Kernel panic - not syncing: IO-APIC + timer doesn't work! Try using the 'noapic' kernel parameter" I had fixed this problem for mainline some time back but I guess I forgot to ask you guys to pick this patch. The direct port of the mainline commit (3da757daf86e498872855f0b5e101f763ba79499) gave a couple of trivial merge conflicts for hardy. The backport (lpj_tsc.patch) of the patch which applies to hardy-git is attached. Many user's might hit this when they start running 8.04.3 guests, so it would be great if you could apply the fix at your earliest. Please note that, with VMware hypervisor specific changes which went in the 8.04.3 kernel (tsc improvements) the likelihood of anybody hitting this on AMD systems is slightly increased. Other Newer Ubuntu releases already have the fix from mainline.
2009-08-27 08:50:55 Stefan Bader linux (Ubuntu Hardy): status Triaged Fix Committed
2009-09-18 16:01:26 Martin Pitt tags verification-needed
2009-09-30 06:44:50 Martin Pitt tags verification-needed verification-done
2009-10-05 14:34:58 Launchpad Janitor linux (Ubuntu Hardy): status Fix Committed Fix Released