Cannot boot full disk encrypted system, impossible to type password

Bug #1501205 reported by DavidEG
56
This bug affects 11 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Confirmed
High
Unassigned
Vivid
Incomplete
High
Unassigned

Bug Description

After last kernel upgrade (3.19.0-30-generic) I'm no longer able to start the system.

1. Press power button.
2. System shows

Ignoring BGRT invalid status 0 (expected 1)
ACPI PCC Probe failed
Starting version 219

(AFAIK this text is the same when everything works)

3. System ask for full disk encryption password.

4. Cannot type password (see attached video).

* Selecting previous kernel (3.19.0-28-generic) in grub allows me to boot normally.
* In a different machine I can use last kernel with full disk encryption without problems.

ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: linux-image-3.19.0-30-generic 3.19.0-30.33
ProcVersionSignature: Ubuntu 3.19.0-28.30-generic 3.19.8-ckt5
Uname: Linux 3.19.0-28-generic x86_64
ApportVersion: 2.17.2-0ubuntu1.5
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: david 2055 F.... pulseaudio
 /dev/snd/controlC1: david 2055 F.... pulseaudio
CurrentDesktop: Unity
Date: Wed Sep 30 09:23:44 2015
HibernationDevice: RESUME=UUID=d225720a-fc40-49a3-9182-17d278d40460
InstallationDate: Installed on 2015-06-29 (92 days ago)
InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
MachineType: TOSHIBA SATELLITE S50-B
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-28-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash
RelatedPackageVersions:
 linux-restricted-modules-3.19.0-28-generic N/A
 linux-backports-modules-3.19.0-28-generic N/A
 linux-firmware 1.143.3
SourcePackage: linux
UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/02/2014
dmi.bios.vendor: INSYDE Corp.
dmi.bios.version: 2.00
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: Type2 - Board Product Name1
dmi.board.vendor: Type2 - Board Vendor Name1
dmi.board.version: Type2 - Board Version
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: OEM Chassis ManuFacturer
dmi.chassis.version: OEM Chassis Version
dmi.modalias: dmi:bvnINSYDECorp.:bvr2.00:bd12/02/2014:svnTOSHIBA:pnSATELLITES50-B:pvrPSPQEE-00F00JEN:rvnType2-BoardVendorName1:rnType2-BoardProductName1:rvrType2-BoardVersion:cvnOEMChassisManuFacturer:ct10:cvrOEMChassisVersion:
dmi.product.name: SATELLITE S50-B
dmi.product.version: PSPQEE-00F00JEN
dmi.sys.vendor: TOSHIBA

Revision history for this message
DavidEG (davideg) 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
Changed in linux (Ubuntu):
importance: Undecided → Critical
Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

Would it be possible for you to test the latest upstream stable kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v3.19 stable kernel[0].

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.19.8-ckt7-vivid/

Changed in linux (Ubuntu):
importance: Critical → High
tags: added: kernel-da-key needs-bisect regression-update
Changed in linux (Ubuntu Vivid):
importance: Undecided → High
status: New → Incomplete
Changed in linux (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
DavidEG (davideg) wrote :

Mainline kernel worked for me.

tags: added: kernel-fixed-upstream
Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

The latest Vivid kernel in the -proposed repository also has the upstream 3.19.8-ckt7 updates.

 Would it be possible for you to test this latest kernel and post back if it resolves this bug?
See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed.

Thank you in advance!

Revision history for this message
DavidEG (davideg) wrote :

I cannot see that kernel, I've added:

deb http://gb.archive.ubuntu.com/ubuntu/ vivid-proposed restricted main multiverse universe

to the sources.list.

Then:

$ sudo apt-get update
$ apt-cache search linux | grep "3.19.8"

And that returns nothing.

Revision history for this message
DisasteR (benj.saiz) wrote :

Also affected after upgrading to 3.19.0-30.

Booting on old kernel 3.19.0-28 resolv the issue.

Revision history for this message
Fredrik Jonson (fredrik-jonson) wrote :

I see the same broken behaviour as in the reporter's video for kernel
linux-image-3.19.0-30-generic, version 3.19.0-30.33.

I have a Dell XPS13, 2015 devel ed, and I run Ubuntu 15.04 with a amd64
kernel.

The system works as expected with linux-image-3.19.0-28-generic, version
3.19.0-28.30.

I've also tested the following kernels, both of which works fine.

1. linux-image-3.19.8-031908ckt7-generic

http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.19.8-ckt7-vivid/linux-image-3.19.8-031908ckt7-generic_3.19.8-031908ckt7.201509251130_amd64.deb

2. linux-image-3.19.8-992-generic

http://kernel.ubuntu.com/~kernel-ppa/mainline/linux-3.19.y.z-review/2015-09-26-vivid/linux-image-3.19.8-992-generic_3.19.8-992.201509260216_amd64.deb

I'd be happy to test other kernel images too. If possible provide a direct
url.

BTW, I'm unable to determine exactly which kernel Joseph refers to in
comment 5 when he mentions that "[the] latest Vivid kernel in the -proposed
repository [includes the fixes of the ctk-7 kernel.]".

Thanks!

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