Processing commands for cont...@bugs.debian.org:
unarchive 655944
Bug #655944 {Done: Moritz Mühlenhoff j...@inutil.org} [linux-2.6]
linux-image-3.1.0-1-amd64: Kernel threads use significant amount of CPU
Unarchived Bug 655944
reopen 655944
Bug #655944 {Done: Moritz Mühlenhoff j...@inutil.org}
I saw a similar issue.
Wheezy KVM host (Doesn't do anything else) with squeeze VMs (Latest
packages on host - Kernel was stock Debian one). All filesystems are
ext3 (no ext4). This was the stacktrace from kern.log (anonymised to
remove hostname):
[406699.787067] general protection fault:
using 3.x instead of 3.x.0 (when minor-minor version is 0) is done by
kernel.org, so I suppose it makes sense for Debian to follow this scheme.
it may be a good idea to run a test that logs all components calling uname,
so they can be checked for version scheme bugs.
On Sun, Sep 8, 2013 at 5:46
On Mon, 2013-09-09 at 14:12 +0200, Yoram Bar Haim wrote:
using 3.x instead of 3.x.0 (when minor-minor version is 0) is done by
kernel.org, so I suppose it makes sense for Debian to follow this
scheme.
Actually, the '.0' is still included if you build a kernel without any
stable updates and
this work-around will make program think they run on top of 2.6.x kernel,
which might be a bug if the program does have special behavior for 3.x.y
On Mon, Sep 9, 2013 at 3:49 PM, Ben Hutchings b...@decadent.org.uk wrote:
On Mon, 2013-09-09 at 14:12 +0200, Yoram Bar Haim wrote:
using 3.x
Package: src:linux
Version: 3.2.46-1+deb7u1
Severity: important
Dear Maintainer,
we are trying to setup Debin Linux in a UEFI Secure Boot environment
using our own keying material.
To be able to write to the UEFI Secure Boot nvram from Linux we need
support for the efivarfs. Unfortunately
On 09/09/13 14:07, Yoram Bar Haim wrote:
this work-around will make program think they run on top of 2.6.x
kernel, which might be a bug if the program does have special behavior
for 3.x.y
With all due respect, it's a bug in a program if it crashes with a 3.x
uname string. If it then also
Package: src:linux
Version: 3.10.7-1
Severity: normal
Hi,
my system will only reboot, e.g. from the gnome-shell menu, if I have
forcefully unloaded the ehci_pci and ehci_hcd modules via rmmod before. Else,
it simply changes to a VT and prints a line like The system is going to reboot
NOW but
Of course, this is a bug in the user-space compnent (libamu in this case),
and sure, a code that crashes because it does not like the release string
is a bad code, no argument about that.
the idea of running a test to locate problematic component was not ment to
be a responsibility of
9 matches
Mail list logo
