Hi,
I already upgraded my system completely. Kernel version 5.4.86 was
installed after this error and thus included in the report.
How can I provide kernel log now?
Best regards,
Markus
On 31/12/2020 15.34, Salvatore Bonaccorso wrote:
Control: tags -1 + moreinfo
Hi Markus,
Thanks for y
Control: tags -1 + moreinfo
Hi Markus,
Thanks for your report.
On Thu, Dec 31, 2020 at 12:45:47PM +0200, Markus Bäcklund wrote:
> Package: src:linux-image-4.19.0-13-amd64
> Version: 4.19.160-2
> Severity: critical
> Justification: breaks the whole system
>
>
>
> -- Package-specific info:
> **
Control: reassign -1 src:linux 4.19.160-2
On Jo, 31 dec 20, 12:45:47, Markus Bäcklund wrote:
> Package: src:linux-image-4.19.0-13-amd64
> Version: 4.19.160-2
> Severity: critical
> Justification: breaks the whole system
>
>
>
> -- Package-specific info:
> ** Kernel log: boot messages should be
Hello,
It probably was src:linux because it was in the original bug report I
submitted a couple of minutes earlier. I included everything reportbug
wanted me to include in the report.
I don't know if I can run the reportbug anymore, since I am now
upgrading from 10 to 11.
Kind regards,
M
On Jo, 31 dec 20, 12:45:47, Markus Bäcklund wrote:
> Package: src:linux-image-4.19.0-13-amd64
> Version: 4.19.160-2
> Severity: critical
> Justification: breaks the whole system
Hello,
What package did you specify to reportbug? I'm asking because
'src:linux-image-4.19.0-13-amd64' doesn't exist
Package: src:linux-image-4.19.0-13-amd64
Version: 4.19.160-2
Severity: critical
Justification: breaks the whole system
-- Package-specific info:
** Kernel log: boot messages should be attached
-- System Information:
Debian Release: 10.7
APT prefers stable-updates
APT policy: (500, 'stable-
6 matches
Mail list logo
