Bug#793377: linux-image-4.0.0-2-amd64: USB keyboard losing keystrokes

Package: linux-image-4.0.0-2-amd64 Version: 4.0.8-1 Severity: important Dear Maintainer, I recently upgraded from Jessie to Stretch, which bought along a kernel upgrade from 3.16 to 4.0. After the upgrade - and a reboot - my USB keyboard (TypeMatrix 2030) started losing keystrokes: typing at norm

Re: Bug#705168: Wheezy fails to boot after 2013-04-05 update

Control: reassign -1 src:linux 3.2.39-2 Barry Fishman writes: > Package: linux-image > Version: 3.2.0-4-amd64 I'm reassigning this to src:linux, with version set to wheezy's src:linux version. > When booting the system, I see about 8 lines of boot messages and then > the display turns off. Th

Re: Processed: Re: Bug#657162: linux-image-2.6.26-amd64: task ... blocked for more than 120 seconds.

Ben Hutchings writes: > On Tue, 2012-01-24 at 16:09 +, Debian Bug Tracking System wrote: >> Processing commands for cont...@bugs.debian.org: >> >> > reassign 657162 linux-image-2.6.32-5-amd64 >> Bug #657162 [linux-image-2.6.26-amd64] linux-image-2.6.26-amd64: task ... >> blocked for more th

Bug#636501: WARNING: at kernel/printk.c:293 do_syslog+0x74/0x38f()

Jonathan Nieder writes: > Gergely Nagy wrote: >> Jonathan Nieder writes: > >>> It looks like intended behavior. I guess the syslogd should be using >>> CAP_SYSLOG these days. >> >> That is correct, even though I personally find the warning stup

Bug#636501: WARNING: at kernel/printk.c:293 do_syslog+0x74/0x38f()

Jonathan Nieder writes: > maximilian attems wrote: >> On Wed, Aug 03, 2011 at 04:10:04PM +0200, Ralf Hildebrandt wrote: > >>> After/deuring the installation of syslog-ng I found the attached trace >>> in dmesg! >> >> oho, is that reproducible on 3.0 that you find in unstable? > > It looks like in