On Wed, 2018-07-25 at 16:52 +, fakefur wrote:
> the screenshot shows the errors
> it basically would not boot
Oh right, I can see it on the BTS but it didn't appear on the mailing
list.
Does adding the kernel parameter "ahci.mobile_lpm_policy=1" avoid this?
Can you also run these commands
Processing control commands:
> notfound -1 4.16.16-2
Bug #904600 [src:linux] linux-image-4.16.0-2-amd64: kernel 4.17.0-1 caused many
problems on cold boot
No longer marked as found in versions linux/4.16.16-2.
> found -1 4.17.8-1
Bug #904600 [src:linux] linux-image-4.16.0-2-amd64: kernel
the screenshot shows the errors
it basically would not boot
On July 25, 2018 4:51:21 PM UTC, Ben Hutchings wrote:
>Control: notfound -1 4.16.16-2
>Control: found -1 4.17.8-1
>Control: tag -1 moreinfo
>
>On Wed, 2018-07-25 at 16:46 +0200, lauren wrote:
>> Package: src:linux
>> Version: 4.16.16-2
Control: notfound -1 4.16.16-2
Control: found -1 4.17.8-1
Control: tag -1 moreinfo
On Wed, 2018-07-25 at 16:46 +0200, lauren wrote:
> Package: src:linux
> Version: 4.16.16-2
> Severity: important
>
> Dear Maintainer,
>
> *** Reporter, please consider answering these questions, where
>
Package: src:linux
Version: 4.16.16-2
Severity: important
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
* What led up to the situation?
apt update caused the new kernel to be installed
* What exactly did you do (or not do) that was
5 matches
Mail list logo
