Upgrade from 3.16.0-23 to -30 caused cascade.

Bug #1416913 reported by Neil Hearn
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Expired
Low
Unassigned

Bug Description

Upgrade from 3.16.0-23 to -30 caused cascade of errors.
Started with TPM error (7) at boot and would not continue past.
Enabled TPM in BIOS security. TPM Error disappeared but on boot Ubuntu splash was small and located top left. Would not boot past this screen.

Recovery console would not boot failsafeX

Shell allowed the removal of nfs-common (only non-update module installed before reboot).
Ran apt-get clean
apt-get autoremove
apt-get update

WORKAROUND: In /etc/default/grub:
GRUB_CMDLINE_LINUX_DEFAULT="acpi=nomsi quiet splash nolapic"
GRUB_CMDLINE_LINUX="tpm_tis.interrupts=0"

adding the "acpi=nomsi" and "nolapic" along with "tpm_tis.interrupts=0".

ProblemType: Bug
DistroRelease: Ubuntu 14.10
Package: linux-image-3.16.0-30-generic 3.16.0-30.40
ProcVersionSignature: Ubuntu 3.16.0-30.40-generic 3.16.7-ckt3
Uname: Linux 3.16.0-30-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.14.7-0ubuntu8.1
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: katy 2172 F.... pulseaudio
Date: Sun Feb 1 23:07:23 2015
HibernationDevice: RESUME=UUID=572dc790-34eb-4020-8032-633bb996f79a
InstallationDate: Installed on 2015-01-30 (2 days ago)
InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
MachineType: Hewlett-Packard HP Compaq 6715b (GB837ET#ABU)
PccardctlIdent:
 Socket 0:
   no product info available
PccardctlStatus:
 Socket 0:
   no card
ProcFB: 0 radeondrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-30-generic root=UUID=1814090d-3c21-4bab-8fca-84a748e4f43a ro tpm_tis.interrupts=0 acpi=nomsi quiet splash nolapic vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-3.16.0-30-generic N/A
 linux-backports-modules-3.16.0-30-generic N/A
 linux-firmware 1.138.1
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/16/2007
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: 68YTT Ver. F.07
dmi.board.name: 30C2
dmi.board.vendor: Hewlett-Packard
dmi.board.version: KBC Version 71.28
dmi.chassis.asset.tag: CNU8021MSF
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.modalias: dmi:bvnHewlett-Packard:bvr68YTTVer.F.07:bd07/16/2007:svnHewlett-Packard:pnHPCompaq6715b(GB837ET#ABU):pvrF.07:rvnHewlett-Packard:rn30C2:rvrKBCVersion71.28:cvnHewlett-Packard:ct10:cvr:
dmi.product.name: HP Compaq 6715b (GB837ET#ABU)
dmi.product.version: F.07
dmi.sys.vendor: Hewlett-Packard

Revision history for this message
Neil Hearn (nhearn) wrote :
Revision history for this message
Brad Figg (brad-figg) wrote : Status changed to Confirmed

This change was made by a bot.

Changed in linux (Ubuntu):
status: New → Confirmed
Revision history for this message
penalvch (penalvch) wrote :

Neil Hearn, thank you for reporting this and helping make Ubuntu better. Could you please test the latest upstream kernel available from the very top line at the top of the page (the release names are irrelevant for testing, and please do not test the daily folder) following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue.

If the test did not allow you to test to the issue (ex. you couldn't boot into the OS) please make a comment in your report about this, and continue to test the next most recent kernel version until you can test to the issue. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested. If this bug is fixed in the mainline kernel, please add the following tags by clicking on the yellow circle with a black pencil icon, next to the word Tags, located at the bottom of the report description:
kernel-fixed-upstream
kernel-fixed-upstream-3.XY-rcZ

Where XY and Z are numbers corresponding to the kernel version.

If the mainline kernel does not fix this bug, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-3.XY-rcZ

Once testing of the upstream kernel is complete, please mark this bug's Status as Confirmed. Please let us know your results.

Thank you for your understanding.

tags: added: regression-update
description: updated
Changed in linux (Ubuntu):
importance: Undecided → Low
status: Confirmed → Incomplete
Revision history for this message
Neil Hearn (nhearn) wrote : Re: [Bug 1416913] Re: Upgrade from 3.16.0-23 to -30 caused cascade.
Download full text (8.1 KiB)

Hi Christopher,
The device in question is my wife's laptop, so I daren't "test" anything.
I submitted the bug, and would test this upstream, but I have no experience of this error on my personal or development devices. Apologies if I have reported when I should not.

Neil Hearn.

On 1 Feb 2015, at 23:49, "Christopher M. Penalver" <email address hidden> wrote:

> Neil Hearn, thank you for reporting this and helping make Ubuntu better.
> Could you please test the latest upstream kernel available from the very
> top line at the top of the page (the release names are irrelevant for
> testing, and please do not test the daily folder) following
> https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional
> upstream developers to examine the issue.
>
> If the test did not allow you to test to the issue (ex. you couldn't boot into the OS) please make a comment in your report about this, and continue to test the next most recent kernel version until you can test to the issue. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested. If this bug is fixed in the mainline kernel, please add the following tags by clicking on the yellow circle with a black pencil icon, next to the word Tags, located at the bottom of the report description:
> kernel-fixed-upstream
> kernel-fixed-upstream-3.XY-rcZ
>
> Where XY and Z are numbers corresponding to the kernel version.
>
> If the mainline kernel does not fix this bug, please add the following tags:
> kernel-bug-exists-upstream
> kernel-bug-exists-upstream-3.XY-rcZ
>
> Once testing of the upstream kernel is complete, please mark this bug's
> Status as Confirmed. Please let us know your results.
>
> Thank you for your understanding.
>
> ** Tags added: regression-update
>
> ** Description changed:
>
> Upgrade from 3.16.0-23 to -30 caused cascade of errors.
> Started with TPM error (7) at boot and would not continue past.
> - Enabled TPM in Bios security.
> - TPM Error dissappeared but on boot Ubuntu splash was small and located top left.
> - Would not boot past this screen.
> + Enabled TPM in BIOS security. TPM Error disappeared but on boot Ubuntu splash was small and located top left. Would not boot past this screen.
>
> Recovery console would not boot failsafeX
>
> Shell allowed the removal of nfs-common (only non-update module installed before reboot).
> Ran apt-get clean
> apt-get autoremove
> apt-get update
>
> - changed /etc/default/grub as per...
> + WORKAROUND: In /etc/default/grub:
> GRUB_CMDLINE_LINUX_DEFAULT="acpi=nomsi quiet splash nolapic"
> GRUB_CMDLINE_LINUX="tpm_tis.interrupts=0"
>
> adding the "acpi=nomsi" and "nolapic" along with "tpm_tis.interrupts=0".
> -
> - Rebooted and system came up.
> -
> - None of this occurred before the kernel upgrade to 3.16.0-30
>
> ProblemType: Bug
> DistroRelease: Ubuntu 14.10
> Package: linux-image-3.16.0-30-generic 3.16.0-30.40
> ProcVersionSignature: Ubuntu 3.16.0-30.40-generic 3.16.7-ckt3
> Uname: Linux 3.16.0-30-generic x86_64
> NonfreeKernelModules: wl
> ApportVersion: 2.14.7-0ubuntu8.1
> Architecture: amd64
> AudioDevicesInUse:
> - USER PID ACCESS...

Read more...

Revision history for this message
Neil Hearn (nhearn) wrote :

Got permission from my wife to try and "fix" her issues.
Installed 3.19.0-031900rc7-generic kernel.

Laptop does not exhibit previous bug.

However, new issues appeared.
Broadcom4311 not recognised on boot.
Suspend to resume causes halt with a flashing "_" at top left of screen.

Should I close and open new report?

Revision history for this message
penalvch (penalvch) wrote :

Neil Hearn, the next step is to fully reverse commit bisect from kernel 3.16 to 3.19-rc7 in order to identify the last bad commit, followed immediately by the first good one. Once this commit has been identified, then it may be reviewed as a candidate for backporting into your release. Could you please do this following https://wiki.ubuntu.com/Kernel/KernelBisection#How_do_I_reverse_bisect_the_upstream_kernel.3F ?

Please note, finding adjacent kernel versions is not fully commit bisecting.

Thank you for your understanding.

Helpful bug reporting tips:
https://wiki.ubuntu.com/ReportingBugs

tags: added: kernel-fixed-upstream kernel-fixed-upstream-3.19-rc7 needs-reverse-bisect
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]

Changed in linux (Ubuntu):
status: Incomplete → Expired
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.