Your message dated Thu, 22 Dec 2016 08:21:29 +0100 with message-id <[email protected]> and subject line Re: #845260: incorrect bug tracker has caused the Debian Bug report #845260, regarding kernel-common: hard lockup with Call Trace after upgrading from 4.2 to 4.8 kernel to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [email protected] immediately.) -- 845260: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=845260 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Package: kernel-common Version: kernel Severity: critical Justification: breaks the whole system Dear Maintainer, * What led up to the situation? upgraded Sparky Linux 4, kernel 4.2 to 4.8 via safe upgrade method * What exactly did you do (or not do) that was effective (or ineffective)? was able to only boot to single recovery mode. Managed to boot once with 4.2 kernel to report this * What was the outcome of this action? boots to 4.8 result in hard lockup after Call Trace * What outcome did you expect instead? normal boot, then xserver -- System Information: Distributor ID: Sparky Description: SparkyLinux Release: 4 Codename: Tyche Architecture: i686 Kernel: Linux 4.2.0-1-586 Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system)
--- End Message ---
--- Begin Message ---The Debian BTS only tracks bugs in Debian; this bug appears to be about some other distribution. (Also, the assigned package is probably incorrect.) -- christian hofstaedtler <[email protected]>
--- End Message ---
