[Checkpoint P-20-00] Failed to boot after upgrade to 12.04.1

Bug #1055506 reported by J Bauer
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Linux
Won't Fix
Medium
linux (Ubuntu)
Triaged
Medium
Unassigned

Bug Description

After upgrading (with do-release-upgrade) the OS to Ubuntu 12.04.1 LTS, the system failed to boot. It failed to find any disks. Boot process ended with the "(initramfs)" prompt. Output attached. Tried the following option with the new kernel (3.2.0-31-generic):
noapic -- failed
nolapic -- failed
acpi=ht -- failed

WORKAROUND: Add to boot options:
acpi=off

Falling back to old kernel (2.6.32-43-server) the system booted fine.

ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: linux-image-3.2.0-31-generic 3.2.0-31.50
ProcVersionSignature: Ubuntu 3.2.0-31.50-generic 3.2.28
Uname: Linux 3.2.0-31-generic x86_64
AcpiTables:

AlsaDevices:
 total 0
 crw-rw---T 1 root audio 116, 1 Sep 24 09:08 seq
 crw-rw---T 1 root audio 116, 33 Sep 24 09:08 timer
AplayDevices: Error: [Errno 2] No such file or directory
ApportVersion: 2.0.1-0ubuntu13
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found.
Date: Mon Sep 24 09:31:18 2012
HibernationDevice: RESUME=UUID=eaff9f20-4df4-40db-a79b-fe4b1a9d48ec
InstallationMedia: Ubuntu-Server 10.04 LTS "Lucid Lynx" - Release amd64 (20100427)
Lsusb:
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: CheckPoint P-20-00
PciMultimedia:

ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 LANG=C
 SHELL=/bin/bash
ProcFB:

ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-31-generic root=UUID=3cb24138-2b7c-4dae-9de8-10ffda57c140 ro console=ttyS0,115200n8 acpi=off
RelatedPackageVersions:
 linux-restricted-modules-3.2.0-31-generic N/A
 linux-backports-modules-3.2.0-31-generic N/A
 linux-firmware 1.79.1
RfKill: Error: [Errno 2] No such file or directory
SourcePackage: linux
UpgradeStatus: Upgraded to precise on 2012-09-21 (2 days ago)
dmi.bios.date: 03/26/2008
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 080014
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: Bridgeport
dmi.board.vendor: Intel
dmi.board.version: To be filled by O.E.M.
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: Intel
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr080014:bd03/26/2008:svnCheckPoint:pnP-20-00:pvrToBeFilledByO.E.M.:rvnIntel:rnBridgeport:rvrTobefilledbyO.E.M.:cvnIntel:ct3:cvrToBeFilledByO.E.M.:
dmi.product.name: P-20-00
dmi.product.version: To Be Filled By O.E.M.
dmi.sys.vendor: CheckPoint

Revision history for this message
J Bauer (jbauer-b) wrote :
Revision history for this message
J Bauer (jbauer-b) wrote :
Brad Figg (brad-figg)
Changed in linux (Ubuntu):
status: New → Confirmed
tags: added: lucid
Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v3.6 kernel[0] (Not a kernel in the daily directory) and install both the linux-image and linux-image-extra .deb packages.

Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag. Please only remove that one tag and leave the other tags. This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs-upstream-testing' text.

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

If you are unable to test the mainline kernel, for example it will not boot, please add the tag: 'kernel-unable-to-test-upstream'.
Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".

Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.6-rc7-quantal/

Changed in linux (Ubuntu):
importance: Undecided → High
status: Confirmed → Incomplete
tags: added: needs-upstream-testing
tags: added: kernel-da-key
Revision history for this message
J Bauer (jbauer-b) wrote :

I tried the 3.6.0-030600rc7-generic kernel from http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.6-rc7-quantal/
It failed in the same manner as the 3.2.0 kernel. It also booted ok with acpi=off.

tags: added: kernel-bug-exists-upstream
removed: needs-upstream-testing
Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

This issue appears to be an upstream bug, since you tested the latest upstream kernel. Would it be possible for you to open an upstream bug report[0]? That will allow the upstream Developers to examine the issue, and may provide a quicker resolution to the bug.

If you are comfortable with opening a bug upstream, It would be great if you can report back the upstream bug number in this bug report. That will allow us to link this bug to the upstream report.

[0] https://wiki.ubuntu.com/Bugs/Upstream/kernel

Changed in linux (Ubuntu):
status: Incomplete → Triaged
Revision history for this message
J Bauer (jbauer-b) wrote :
Changed in linux:
importance: Unknown → Medium
status: Unknown → Incomplete
Changed in linux:
status: Incomplete → Won't Fix
penalvch (penalvch)
description: updated
tags: added: kernel-bug-exists-upstream-v3.6-rc7 regression-release
removed: kernel-bug-exists-upstream
Changed in linux (Ubuntu):
status: Triaged → Incomplete
Revision history for this message
J Bauer (jbauer-b) wrote : Re: [Bug 1055506] Re: Failed to boot after upgrade to 12.04.1

I confirmed that the system was running 12.04.3, disabled the workaround
(pci=nocrs), and rebooted. The problem still exists.

Distributor ID: Ubuntu
Description: Ubuntu 12.04.3 LTS
Release: 12.04
Codename: precise

Linux range 3.6.0-030600rc7-generic #201209232235 SMP Mon Sep 24
02:36:02 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux

Christopher M. Penalver wrote, On 11/11/13 12:57:
> J Bauer, this bug was reported a while ago and there hasn't been any
> activity in it recently. We were wondering if this is still an issue? If
> so, could you please advise if after updating to 12.04.3 during your
> maintenance window, this is still reproducible?
>

penalvch (penalvch)
tags: added: raring
tags: removed: raring
Revision history for this message
penalvch (penalvch) wrote : Re: Failed to boot after upgrade to 12.04.1

J Bauer, did you get a chance to test the upstream patch? If so, did it address your issue?

Revision history for this message
J Bauer (jbauer-b) wrote :

Yes, tested patch https://bugzilla.kernel.org/attachment.cgi?id=82781&action=diff last year. It worked, although there were a bunch of error messages. See https://bugzilla.kernel.org/show_bug.cgi?id=47981#c26.

The patch was applied to upstream and then reverted

Revision history for this message
penalvch (penalvch) wrote :

J Bauer, could you please test the latest mainline kernel via http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.12-trusty/ and advise to the results?

Changed in linux (Ubuntu):
importance: High → Medium
Revision history for this message
J Bauer (jbauer-b) wrote :

Tried linux-image-3.12.0-031200-generic_3.12.0-031200.201311071835_amd64.deb. It did not work. Same issue.

penalvch (penalvch)
tags: added: kernel-bug-exists-upstream-v3.12
removed: kernel-bug-exists-upstream-v3.6-rc7
Revision history for this message
penalvch (penalvch) wrote :

J Bauer, it wouldn't hurt to have a commit bisect done from 2.6.32-43-server to 3.2.0.31-generic in order to identify the offending commit following https://wiki.ubuntu.com/Kernel/KernelBisection . Despite this, it looks like the upstream consensus is this issue is BIOS driven, and they would prefer a fix there versus a quirk. Any information on the BIOS front?

Changed in linux (Ubuntu):
status: Incomplete → Triaged
summary: - Failed to boot after upgrade to 12.04.1
+ [Checkpoint P-20-00] Failed to boot after upgrade to 12.04.1
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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