I don't know how I managed to mess up such an easy process, but the bug report is about linux-image-4.3.0-1-686-pae and not the headers. Is there anyway I can rectify this?
On Sun, Jan 3, 2016 at 2:29 PM, Barkın Çelebican <bcelebi...@gmail.com> wrote: > Package: linux-headers-4.3.0-1-all > Severity: important > > Dear Maintainer, > > I have removed the problem kernel package and reverted to the older 4.2.0 > package as there were no errors prior to the upgrade. While searching for a > solution before I came across this bug report: > https://bugzilla.kernel.org/show_bug.cgi?id=109661 > > * What led up to the situation? > upgrade to linux-image-4.3.0-1-686-pae and booting into new kernel > * What exactly did you do (or not do) that was effective (or > ineffective)? > booting into new kernel > * What was the outcome of this action? > errors writing to disk in dmesg and stdout/console > * What outcome did you expect instead? > no errors > > > -- System Information: > Debian Release: stretch/sid > APT prefers testing > APT policy: (500, 'testing') > Architecture: i386 (i686) > > Kernel: Linux 4.2.0-1-686-pae (SMP w/4 CPU cores) > Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) > Shell: /bin/sh linked to /bin/dash > Init: systemd (via /run/systemd/system) >
