Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.user > #177069 > unrolled thread

Boot fails after stretch upgrade to linux 4.9.0

Back to article view | Back to linux.debian.user

Contents

  Boot fails after stretch upgrade to linux 4.9.0 Francesco Montanari <francesco.montanari@openmailbox.org> - 2017-01-28 13:40 +0100
    Re: Boot fails after stretch upgrade to linux 4.9.0 Francesco Montanari <francesco.montanari@openmailbox.org> - 2017-02-04 17:30 +0100
      Re: Boot fails after stretch upgrade to linux 4.9.0 francesco.montanari@openmailbox.org - 2017-02-13 10:50 +0100

#177069 — Boot fails after stretch upgrade to linux 4.9.0

Hi,

With a recent Stretch update, linux 4.9.0-1-amd64 was installed. I got:
  A TPM error (6) occurred attempting to read a pcr value

Disabling the security chip from BIOS solved the error. Still, 4.9.0
does not boot. It manages to start some service (e.g., network
manager), but then it gets stuck before displaying the login screen.

I managed to boot in recovery mode. I collect here some grep of errors
and warnings:

- From dmesg:
  [ 0.773426] acpi PNP0A08:00: _OSC failed (AE_SUPPORT); disabling ASPM

- From journalctl -xb:
  Jan 28 10:05:08 debian-francesco kernel: acpi PNP0A08:00: _OSC failed (AE_SUPPORT); disabling ASPM
  -- The process /bin/plymouth could not be executed and failed.
  Jan 28 10:05:17 debian-francesco bluetoothd[512]: Sap driver initialization failed.
  Jan 28 10:05:08 debian-francesco kernel: EXT4-fs (sda3): re-mounted. Opts: errors=remount-ro
  -- The error number returned by this process is 2.

- From syslog:
  https://is.gd/fMGaPr

When rebooting from recovery mode (i.e., executing 'systemctl
reboot'), it also gets stuck.

Finally, If I pass the following command in recovery mode
  # lspci -nn | grep VGA
it gets stuck (ctrl-c/d/z have no effect) right after displaying this
message:
    [   19.948099] nouveau 0000:01:00.0: DRM: suspending console...
    [   19.951782] nouveau 0000:01:00.0: DRM: suspending display...
    [   19.955032] nouveau 0000:01:00.0: DRM: evicting buffers...
    [   19.958215] nouveau 0000:01:00.0: DRM: waiting for kernel channels to go idle...
    [   19.961380] nouveau 0000:01:00.0: DRM: suspending client object trees...
    [   19.964738] nouveau 0000:01:00.0: DRM: suspending kernel object tree...

I successfully booted with the old 4.8.0 kernel (normal mode). In that
case:
  $ lspci -nn | grep VGA
  00:02.0 VGA compatible controller [0300]: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0126] (rev 09)
  01:00.0 VGA compatible controller [0300]: NVIDIA Corporation GF119M [Quadro NVS 4200M] [10de:1057] (rev a1)


Not sure if it is related to some configuration I may have modified in
the past, to graphics drivers or, e.g., to old BIOS? Maybe something
else?

I have a Thinkpad T420.

Thanks,
Francesco

[toc] | [next] | [standalone]

#177397

Hi,

I may have not copied the correct error message when the system
freezes after passing lspci in recovery mode (unless
the message changed). I report below the corrected message.

To sum up:
- using linux 4.8.0. I notice no problem.
- When I first booted linux 4.9.0, I got a TPM error message that I never
  had before. Disabling the security chip from BIOS solved it.
- The system does not boot as it gets stucked after loading some
  service (e.g., network manager).
- It boots in recovery mode, but freezes when passing the lspci
  command. It also freezes if I pass "systemctl reboot"
- Logs show error messages related to acpi, drivers, remount error of
  EXT4 partition (fsck did not find problems), and segfault related to
  gnome-session-f (https://is.gd/fMGaPr).

Do you have any hint to identify and understand better the origin of
the issue (please let me know if you need more info)?




Here is the message before the system gets stucked:
# lspci -nn | grep VGA
[   111.290008] thinkpad_acpi: EC reports that Thermal Table has changed
[   111.290185] nouveau 0000:01:00.0: DRM: resuming kernel object
tree..
[   111.477119] nouveau 0000:01:00.0: DRM: resuming client object trees...
[   111.478199] nouveau 0000:01:00.0: DRM: resuming display...
[   111.479289] nouveau 0000:01:00.0: DRM: resuming console...




Thanks,
Francesco


On Sat, Jan 28, 2017 at 02:35:24PM +0200, Francesco Montanari wrote:
> Hi,
>
> With a recent Stretch update, linux 4.9.0-1-amd64 was installed. I got:
>   A TPM error (6) occurred attempting to read a pcr value
>
> Disabling the security chip from BIOS solved the error. Still, 4.9.0
> does not boot. It manages to start some service (e.g., network
> manager), but then it gets stuck before displaying the login screen.
>
> I managed to boot in recovery mode. I collect here some grep of errors
> and warnings:
>
> - From dmesg:
>   [ 0.773426] acpi PNP0A08:00: _OSC failed (AE_SUPPORT); disabling ASPM
>
> - From journalctl -xb:
>   Jan 28 10:05:08 debian-francesco kernel: acpi PNP0A08:00: _OSC failed (AE_SUPPORT); disabling ASPM
>   -- The process /bin/plymouth could not be executed and failed.
>   Jan 28 10:05:17 debian-francesco bluetoothd[512]: Sap driver initialization failed.
>   Jan 28 10:05:08 debian-francesco kernel: EXT4-fs (sda3): re-mounted. Opts: errors=remount-ro
>   -- The error number returned by this process is 2.
>
> - From syslog:
>   https://is.gd/fMGaPr
>
> When rebooting from recovery mode (i.e., executing 'systemctl
> reboot'), it also gets stuck.
>
> Finally, If I pass the following command in recovery mode
>   # lspci -nn | grep VGA
> it gets stuck (ctrl-c/d/z have no effect) right after displaying this
> message:
>     [   19.948099] nouveau 0000:01:00.0: DRM: suspending console...
>     [   19.951782] nouveau 0000:01:00.0: DRM: suspending display...
>     [   19.955032] nouveau 0000:01:00.0: DRM: evicting buffers...
>     [   19.958215] nouveau 0000:01:00.0: DRM: waiting for kernel channels to go idle...
>     [   19.961380] nouveau 0000:01:00.0: DRM: suspending client object trees...
>     [   19.964738] nouveau 0000:01:00.0: DRM: suspending kernel object tree...
>
> I successfully booted with the old 4.8.0 kernel (normal mode). In that
> case:
>   $ lspci -nn | grep VGA
>   00:02.0 VGA compatible controller [0300]: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0126] (rev 09)
>   01:00.0 VGA compatible controller [0300]: NVIDIA Corporation GF119M [Quadro NVS 4200M] [10de:1057] (rev a1)
>
>
> Not sure if it is related to some configuration I may have modified in
> the past, to graphics drivers or, e.g., to old BIOS? Maybe something
> else?
>
> I have a Thinkpad T420.
>
> Thanks,
> Francesco
>

[toc] | [prev] | [next] | [standalone]

#177766

On 2017-02-04 19:26, Francesco Montanari wrote:
> To sum up:
> - using linux 4.8.0. I notice no problem.
> - When I first booted linux 4.9.0, I got a TPM error message that I 
> never
>   had before. Disabling the security chip from BIOS solved it.
> - The system does not boot as it gets stucked after loading some
>   service (e.g., network manager).
> - It boots in recovery mode, but freezes when passing the lspci
>   command. It also freezes if I pass "systemctl reboot"
> - Logs show error messages related to acpi, drivers, remount error of
>   EXT4 partition (fsck did not find problems), and segfault related to
>   gnome-session-f (https://is.gd/fMGaPr).
> 

Comparing various logs of 4.8.0 vs 4.9.0 I didn't spot significant 
differences. As a test, I also tried to install the proprietary nvidia 
drivers and CPU microcode update packages, but things didn't change.

Thanks to an off-list exchange I managed to boot 4.9.0 in normal mode by 
deactivating the discrete graphic card (Nvidia Optimus) from BIOS. The 
integrated card is good enough for me anyway.

Best,
Francesco

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.user

csiph-web