Project

General

Profile

Bug #15152

Tails fails to start with an HP pavillion (broadwell chipset)

Added by goupille about 2 years ago. Updated almost 2 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
Category:
-
Target version:
Start date:
01/08/2018
Due date:
% Done:

100%

Feature Branch:
Type of work:
Research
Blueprint:
Starter:
Affected tool:

Description

A user reported that Tails 3.3 doesn't start on this computer :

https://support.hp.com/ca-en/document/c04785675

In the boot menu, when the user clicks on the "Start Tails" button, the error message "Error parsing PCC subspaces from PCCT" is displayed for a few seconds and the computer reboots.

The Toubleshooting mode, or adding xorg-driver=intel as a boot parameter doesn't work around this issue.

the problem is the same with https://nightly.tails.boum.org/build_Tails_ISO_feature-14976-linux-4.14-force-all-tests/lastSuccessful/archive/build-artifacts/

The user was able to start previous versions of Tails and the current Debian-live (9.3).


Related issues

Blocks Tails - Feature #13245: Core work 2018Q1: Foundations Team Resolved 06/29/2017

Associated revisions

Revision 449ca234 (diff)
Added by intrigeri about 2 years ago

Document know issue (Closes: #15152)

History

#1 Updated by mercedes508 about 2 years ago

  • Status changed from New to Confirmed

#2 Updated by intrigeri about 2 years ago

  • Assignee changed from intrigeri to goupille
  • QA Check set to Info Needed

Potential fixes:

  1. Ensure the system boots in UEFI mode and not in Legacy BIOS mode.
  2. Add the intel_pstate=disable boot option.
  3. Ensure the BIOS is up-to-date.
  4. If on a Windows computer, disable fastboot ("hiberboot"): https://www.tenforums.com/tutorials/4189-turn-off-fast-startup-windows-10-a.html, https://www.trishtech.com/2013/07/how-to-disable-hiberboot-in-windows-8/

Now, I doubt that "Error parsing PCC subspaces from PCCT" is the actual problem.

#3 Updated by goupille about 2 years ago

  • Subject changed from Gnome fails to start with an HP pavillion (broadwell chipset) to Tails fails to start with an HP pavillion (broadwell chipset)
  • Assignee changed from goupille to intrigeri
  • QA Check deleted (Info Needed)

Actually, the user confused 'Tails greeter' and 'Boot Loader Menu'. The computer reboots just after the boot menu, whatever mode the user choose (tails or troubleshooting).

regarding the workaround suggested previously:

the computer seems to have graphics issues when booting tails in UEFI (light grey boot menu instead of the regular black), there is no BIOS update provided by the vendor at the moment, fastboot has been disabled, the suggested boot parameter added, and yet, Tails still doesn't start and the computer keeps rebooting after the boot loader menu.

#4 Updated by intrigeri about 2 years ago

  • Description updated (diff)

goupille wrote:

Actually, the user confused 'Tails greeter' and 'Boot Loader Menu'. The computer reboots just after the boot menu, whatever mode the user choose (tails or troubleshooting).

I had guessed, but thanks anyway. Adjusted the description accordingly.

the computer seems to have graphics issues when booting tails in UEFI (light grey boot menu instead of the regular black),

As discussed on XMPP that's the expected behavior in UEFI mode.

there is no BIOS update provided by the vendor at the moment, fastboot has been disabled, the suggested boot parameter added, and yet, Tails still doesn't start and the computer keeps rebooting after the boot loader menu.

:/

So that's probably a regression in the kernel (we've upgraded to 4.13 in Tails 3.3). It would be interested to know which "previous versions of Tails" did work, but frankly I don't think we can do better than 1. document the problem (I'll do it right away); 2. ask the OP to test with newer kernels (e.g. 4.14.13 should be available later today); 3. wait for someone to fix this regression upstream.

Now, as usual with low level bugs, if the OP is technical enough to report this upstream and compile kernels, they could do that.

#5 Updated by intrigeri about 2 years ago

#6 Updated by intrigeri about 2 years ago

  • Status changed from Confirmed to Resolved
  • % Done changed from 0 to 100

#7 Updated by anonym about 2 years ago

  • Status changed from Resolved to Confirmed
  • QA Check set to Info Needed

This ticket was not supposed to be resolved, right?

#8 Updated by intrigeri about 2 years ago

  • Status changed from Confirmed to In Progress
  • Assignee changed from intrigeri to anonym

anonym wrote:

This ticket was not supposed to be resolved, right?

Yes, I closed it intentionally. What else do you think we should do?

#9 Updated by intrigeri almost 2 years ago

  • Target version set to Tails_3.6

Ping?

#10 Updated by bertagaz almost 2 years ago

  • Target version changed from Tails_3.6 to Tails_3.7

#11 Updated by anonym almost 2 years ago

  • Status changed from In Progress to Resolved
  • QA Check deleted (Info Needed)

Also available in: Atom PDF