Encrypted installs break many functionalities - suspend, virtual console, switch user

Bug #993864 reported by Louis Bouchard
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
plymouth (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

This seems to be a follow-up to LP: 942846.

When using the alternate CD to install 12.04 with LVM + Full disk encryption, the resulting O/S has many problems :
 - Unable to switch to virtual consoles : Alt-F1 with hang the graphical output, requiring hardware reset
 - Cannot suspend (S3) : suspend will trigger but will result in a hung system and blank screen
 - Switching user hangs on a blank screen

As outlined in LP: 942846, just after grub, the screen systematically displays :
  error: no video mode activated

The screen will then switch to text mode, then ask for the LUKS password (picture attached)

Comment #6 in LP: 942846 indicates specificities with plymouth when used in conjunction with LUKS.

It is important to know that the same laptop (HP Elitebook 8440p) installed with the standard CD (ubiquity) without LUKS encryption on a separate disk DOES NOT show those problems. Both environments are still available.

First apport-collect: nvidia driver, cryptsetup installed (so plymouth in initramfs), no fb module gets loaded; previous boot failed (no vt.handoff=7 set)
---
ApportVersion: 2.0.1-0ubuntu7
Architecture: amd64
DefaultPlymouth: /lib/plymouth/themes/ubuntu-logo/ubuntu-logo.plymouth
DistroRelease: Ubuntu 12.04
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425)
MachineType: Hewlett-Packard HP EliteBook 8440p
NonfreeKernelModules: nvidia
Package: plymouth 0.8.2-2ubuntu30
PackageArchitecture: amd64
PccardctlStatus:
 Socket 0:
   3.3V
  16-bit
  PC Card
   Subdevice 0 (function 0) bound to driver "pata_pcmcia"
ProcCmdLine: BOOT_IMAGE=/vmlinuz-3.2.0-23-generic root=/dev/mapper/hostname-root ro quiet splash
ProcFB:

ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.2.0-23-generic root=/dev/mapper/hostname-root ro quiet splash
ProcVersionSignature: Ubuntu 3.2.0-23.36-generic 3.2.14
Tags: precise
TextPlymouth: /lib/plymouth/themes/ubuntu-text/ubuntu-text.plymouth
Uname: Linux 3.2.0-23-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip kvm libvirtd lpadmin plugdev sambashare sudo
dmi.bios.date: 11/25/2010
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: 68CCU Ver. F.11
dmi.board.name: 172B
dmi.board.vendor: Hewlett-Packard
dmi.board.version: KBC Version 30.31
dmi.chassis.asset.tag: CZC109660H
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.modalias: dmi:bvnHewlett-Packard:bvr68CCUVer.F.11:bd11/25/2010:svnHewlett-Packard:pnHPEliteBook8440p:pvr:rvnHewlett-Packard:rn172B:rvrKBCVersion30.31:cvnHewlett-Packard:ct10:cvr:
dmi.product.name: HP EliteBook 8440p
dmi.sys.vendor: Hewlett-Packard

Second apport-collect: nvidia driver, cryptsetup not installed, fb module gets loaded; vt.handoff=7 set
---
ApportVersion: 2.0.1-0ubuntu5
Architecture: amd64
DefaultPlymouth: /lib/plymouth/themes/ubuntu-logo/ubuntu-logo.plymouth
DistroRelease: Ubuntu 12.04
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425)
MachineType: Hewlett-Packard HP EliteBook 8440p
NonfreeKernelModules: nvidia
Package: plymouth 0.8.2-2ubuntu30
PackageArchitecture: amd64
PccardctlStatus:
 Socket 0:
   3.3V
  16-bit
  PC Card
   Subdevice 0 (function 0) bound to driver "pata_pcmcia"
ProcCmdLine: BOOT_IMAGE=/vmlinuz-3.2.0-23-generic root=UUID=0aeacb3c-d932-45c9-b43f-8bc85082a760 ro quiet splash vt.handoff=7
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 LANG=fr_FR.UTF-8
 SHELL=/bin/bash
ProcFB: 0 VESA VGA
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.2.0-23-generic root=UUID=0aeacb3c-d932-45c9-b43f-8bc85082a760 ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 3.2.0-23.36-generic 3.2.14
Tags: precise
TextPlymouth: /lib/plymouth/themes/ubuntu-text/ubuntu-text.plymouth
Uname: Linux 3.2.0-23-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

dmi.bios.date: 11/25/2010
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: 68CCU Ver. F.11
dmi.board.name: 172B
dmi.board.vendor: Hewlett-Packard
dmi.board.version: KBC Version 30.31
dmi.chassis.asset.tag: CZC109660H
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.modalias: dmi:bvnHewlett-Packard:bvr68CCUVer.F.11:bd11/25/2010:svnHewlett-Packard:pnHPEliteBook8440p:pvr:rvnHewlett-Packard:rn172B:rvrKBCVersion30.31:cvnHewlett-Packard:ct10:cvr:
dmi.product.name: HP EliteBook 8440p
dmi.sys.vendor: Hewlett-Packard

Third apport-collect: recovery mode, so vt.handoff=7 not set; cryptsetup installed; nvidia driver not seen; , cryptsetup not installed, fb module gets loaded; vt.handoff=7 set
---
ApportVersion: 2.0.1-0ubuntu7
Architecture: amd64
DefaultPlymouth: /lib/plymouth/themes/ubuntu-logo/ubuntu-logo.plymouth
DistroRelease: Ubuntu 12.04
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425)
MachineType: Hewlett-Packard HP EliteBook 8440p
Package: plymouth 0.8.2-2ubuntu30
PackageArchitecture: amd64
PccardctlStatus:
 Socket 0:
   3.3V
  16-bit
  PC Card
   Subdevice 0 (function 0) bound to driver "pata_pcmcia"
ProcCmdLine: BOOT_IMAGE=/vmlinuz-3.2.0-23-generic root=/dev/mapper/hostname-root ro recovery nomodeset
ProcEnviron:
 LANGUAGE=fr:en
 TERM=linux
 PATH=(custom, no user)
 LANG=fr_FR.UTF-8
 SHELL=/bin/bash
ProcFB:
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.2.0-23-generic root=/dev/mapper/hostname-root ro recovery nomodeset
ProcVersionSignature: Ubuntu 3.2.0-23.36-generic 3.2.14
Tags: precise
TextPlymouth: /lib/plymouth/themes/ubuntu-text/ubuntu-text.plymouth
Uname: Linux 3.2.0-23-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)

dmi.bios.date: 11/25/2010
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: 68CCU Ver. F.11
dmi.board.name: 172B
dmi.board.vendor: Hewlett-Packard
dmi.board.version: KBC Version 30.31
dmi.chassis.asset.tag: CZC109660H
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.modalias: dmi:bvnHewlett-Packard:bvr68CCUVer.F.11:bd11/25/2010:svnHewlett-Packard:pnHPEliteBook8440p:pvr:rvnHewlett-Packard:rn172B:rvrKBCVersion30.31:cvnHewlett-Packard:ct10:cvr:
dmi.product.name: HP EliteBook 8440p
dmi.sys.vendor: Hewlett-Packard

Revision history for this message
Louis Bouchard (louis) wrote :

screenshot of LUKS password prompt

tags: added: apport-collected precise
description: updated
Revision history for this message
Louis Bouchard (louis) wrote : BootDmesg.txt

apport information

Revision history for this message
Louis Bouchard (louis) wrote : BootLog.gz

apport information

Revision history for this message
Louis Bouchard (louis) wrote : CurrentDmesg.txt

apport information

Revision history for this message
Louis Bouchard (louis) wrote : Dependencies.txt

apport information

Revision history for this message
Louis Bouchard (louis) wrote : EtcDefaultGrub.txt

apport information

Revision history for this message
Louis Bouchard (louis) wrote : Lspci.txt

apport information

Revision history for this message
Louis Bouchard (louis) wrote : Lsusb.txt

apport information

Revision history for this message
Louis Bouchard (louis) wrote : PccardctlIdent.txt

apport information

Revision history for this message
Louis Bouchard (louis) wrote : ProcCpuinfo.txt

apport information

Revision history for this message
Louis Bouchard (louis) wrote : ProcEnviron.txt

apport information

Revision history for this message
Louis Bouchard (louis) wrote : ProcInterrupts.txt

apport information

Revision history for this message
Louis Bouchard (louis) wrote : ProcModules.txt

apport information

Revision history for this message
Louis Bouchard (louis) wrote : UdevDb.txt

apport information

Revision history for this message
Louis Bouchard (louis) wrote : UdevLog.txt

apport information

Revision history for this message
Steve Langasek (vorlon) wrote :

Hi Louis,

If you boot without the 'splash' boot option, how does this behavior change?

Revision history for this message
Steve Langasek (vorlon) wrote :

Since you say this also affects suspend and user switching, this is probably not a plymouth issue at all; but will wait for the answer to the above before reassigning.

Changed in plymouth (Ubuntu):
status: New → Incomplete
Revision history for this message
Louis Bouchard (louis) wrote :

Hi Steve,

just tested without the 'splash' (and quiet) boot params. I get the same behavior : ALT-F1 gets me to a blank screen, unable to ALT-F7 back into Unity. Hardware poweroff (10 seconds on the power on button) is the only way out of this.

FYI, I also noticed that the normal shutdown procedure never completes and does not power off the laptop. Again, this is not the case on the other disk, installed without full disk encryption.

Revision history for this message
Louis Bouchard (louis) wrote :

Hi Steve,

Here are the results of some more tests. You may find them interesting.

When booting in failsafe mode (i.e. without graphical activation), everything works fine. I'm able to use VC and the poweroff works correctly.

So I proceeded to remove the nvidia drivers. When Using OSS modules, I get the VC back, poweroff works fine, switching user also works and the laptop suspends correctly.

So I have rebooted on my second disk (standard install from Ubiquity without full disk encryption). I can confirm that everything works fine, even with the nvidia module :

# jockey-text -l
xorg:nvidia_current - NVIDIA accelerated graphics driver (Proprietary, Enabled, In use)
xorg:nvidia_current_updates - NVIDIA accelerated graphics driver (post-release updates) (Proprietary, Disabled, Not in use)

The following apport-collect was done on the second install in case you need it for comparaison.

Let me know how I can help.

description: updated
Revision history for this message
Louis Bouchard (louis) wrote : BootDmesg.txt

apport information

Revision history for this message
Louis Bouchard (louis) wrote : BootLog.gz

apport information

Revision history for this message
Louis Bouchard (louis) wrote : CurrentDmesg.txt

apport information

Revision history for this message
Louis Bouchard (louis) wrote : Dependencies.txt

apport information

Revision history for this message
Louis Bouchard (louis) wrote : EtcDefaultGrub.txt

apport information

Revision history for this message
Louis Bouchard (louis) wrote : Lspci.txt

apport information

Revision history for this message
Louis Bouchard (louis) wrote : Lsusb.txt

apport information

Revision history for this message
Louis Bouchard (louis) wrote : PccardctlIdent.txt

apport information

Revision history for this message
Louis Bouchard (louis) wrote : ProcCpuinfo.txt

apport information

Revision history for this message
Louis Bouchard (louis) wrote : ProcInterrupts.txt

apport information

Revision history for this message
Louis Bouchard (louis) wrote : ProcModules.txt

apport information

Revision history for this message
Louis Bouchard (louis) wrote : UdevDb.txt

apport information

Revision history for this message
Louis Bouchard (louis) wrote : UdevLog.txt

apport information

Revision history for this message
Louis Bouchard (louis) wrote :

@steve

One thing that I forgot to mention in my previous comment is that, when using the OSS drivers, I get into the problem described by LP: 942846 : I need to hit <Esc> in order to see the prompt for the LUKS password.

With the nvidia driver on the second install, the boot sequence happens normally with the graphical aubergine screen and then the Ubuntu logo with dots.

hth

Revision history for this message
Steve Langasek (vorlon) wrote :

> When booting in failsafe mode (i.e. without graphical activation),
> everything works fine. I'm able to use VC and the poweroff works correctly.

I'm not entirely sure what you mean by either "failsafe mode" or "without graphical activation". Do you mean the "recovery mode" boot option in grub? I would be very interested in getting apport data from a boot this way, for comparison.

description: updated
Revision history for this message
Louis Bouchard (louis) wrote :

@steve

Sorry for the "failsafe mode", which is the RHEL menu selection. Yes I'm talking about the "recovery mode" accessible by grub.

I'll run a test on monday morning and post the apport data here.

In the meantime, I'm running with the OSS driver which seem fine.

Revision history for this message
Louis Bouchard (louis) wrote :

@steve

Here are the result of 'apport-collect plymouth & apport-collect linux

Revision history for this message
Louis Bouchard (louis) wrote :
Steve Langasek (vorlon)
description: updated
Revision history for this message
Steve Langasek (vorlon) wrote :

Louis, when you booted in recovery mode, did you resume the normal boot and boot to a full desktop before running apport-collect? I'm puzzled by the output because it doesn't show any attempt to load either the vesafb or the nvidia modules, and I don't know why recovery mode would have impacted this: we pass 'nomodeset' on the commandline in recovery mode, but I don't know why the nvidia module would care about that, when this option is supposed to be for *KMS* drivers.

Revision history for this message
Steve Langasek (vorlon) wrote :

Also, just to confirm, which nvidia driver package do you have installed? I've checked the kernel module source for nvidia-current, and it doesn't look at the 'nomodeset' boot option at all.

Revision history for this message
Louis Bouchard (louis) wrote :

oups sorry I misunderstood your request : I did the apport-collect at the shell prompt without enabling graphical. I'll rerun the test when I'm back on wednesday.

Regarding the nvidia package, it is the default one coming with Precise, which is 295.40-0ubuntu1_amd64.

Since I know that you must be rather busy with UDS-P, we can postpone work on this up until its done. I'm currently running with the FOSS modules which are fine for now.

Revision history for this message
Louis Bouchard (louis) wrote :

Here is one interesting thing I have just identified : the inaccessible virtual consoles ( <Alt>Fn ) problem only happens with dual-head enabled using the Twinview option of the Nvidia settings.

When only using the laptop screen, virtual consoles are accessible and suspend works correctly as well.

Revision history for this message
Louis Bouchard (louis) wrote :

@steve

These apport runs were done while in recovery mode, after trying to run with X activated. The request to start X fails and the laptop returns to the recovery menu.

Revision history for this message
Louis Bouchard (louis) wrote :
Revision history for this message
Steve Langasek (vorlon) wrote :

So with these latest apport collect logs, I still don't see any mention of nvidia and vesafb, but instead I see nouveaufb being loaded. Is this what you expect here? I'm afraid I'm a bit confused at this point as to which driver we need to be debugging.

Revision history for this message
Steve Langasek (vorlon) wrote :

If you're using nouveaufb + TwinView, you can certainly expect things to be very broken...

Revision history for this message
Louis Bouchard (louis) wrote :

@steve

Some of the recent package updates seem to have taken care of most of the problems. I can now use the VC, suspend/resume etc. Hence I will mark this bug as Invalid. Thanks for your help.

Changed in plymouth (Ubuntu):
status: Incomplete → Invalid
To post a comment you must log in.