On Sun, Dec 08, 2013 at 07:03:02PM +0000, Roger Leigh wrote:
> On Thu, Dec 05, 2013 at 03:18:58PM -0500, Jeffrey Sheinberg wrote:
> > I regularly boot into "-b" (emergency) at least once a week, in order to
> > perform backups of my root partition while it is in a read-only state.
> >
> > I have never experienced any problems with using "-b" (emergency) mode
> > before encountering this problem.
> >
> > This problem has so far only happened when booting this linux kernel,
> >
> > linux-image-3.11-0.bpo.2-amd64
>
> This is an odd problem, and it's going to be tricky to track down
> without being able to easily reproduce it. If you notice the
> keyboard lights flickering, this looks like it's possibly an
> input layer issue. If only this kernel exhibits the problem then
> sysvinit is unlikely to be involved directly. I would suggest
> looking at a newer kernel e.g. 3.12 and the options the kernel
> was compiled with.
I only use Debian packaged kernels from wheezy-backports, jessie, or
sid, so 3.12 is not an option for me.
> If you try either 3.11.8-1 (testing) or 3.11.10-1 (unstable), do
> these also show the problem?
Yes, these two kernels exhibit exactly the same behavior as the
linux-image-3.11-0.bpo.2-amd64 mentioned above.
> I would suggest if it's dependent upon the kernel you are running,
> that this should be reassigned to the "linux" kernel source
> package.
I agree. That would be,
ii linux-source-3.11 3.11.8-1~bpo70+1 all Linux kernel source for
version 3.11 with Debian patches
Could you please reassign this bug report for me?
Thanks,
--
Jeffrey Sheinberg
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
