Processed: fixed 649294 in 3.1.1-1

2011-12-01 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: fixed 649294 3.1.1-1 Bug #649294 [linux-2.6] linux-2.6: Duplicate battery after suspend/resume There is no source info for the package 'linux-2.6' at version '3.1.1-1' with architecture '' Unable to make a source version for version '3.1.1-1' Bug

Bug#613321: linux-image-amd64: Please enable 'memtest' option for all linux kernels

2011-12-01 Thread Jonathan Nieder
Dmitry Smirnov wrote: It is probably obvious to everyone that MEMTEST is harmless. Then why not enable it without painful discussions? Having a feature enabled in the Debian kernel (at release time) is a promise to continue supporting it for the period in which that release is supported. It

Bug#613321: linux-image-amd64: Please enable 'memtest' option for all linux kernels

2011-12-01 Thread Uwe Kleine-König
On Thu, Dec 01, 2011 at 06:09:03AM -0600, Jonathan Nieder wrote: Dmitry Smirnov wrote: It is probably obvious to everyone that MEMTEST is harmless. Then why not enable it without painful discussions? Having a feature enabled in the Debian kernel (at release time) is a promise to

Bug#633526: vserver kernel breaks ssh public_key authentication on NFS

2011-12-01 Thread Mirco Bauer
tags 633526 + patch retitle 633526 NFS client uid/gid cache broken on VServer kernels thanks Herbert Poetzl wrote: we now understand the problem, and it was fixed for 3.0.4 with the following patch: http://vserver.13thfloor.at/ExperimentalT/delta-nfs-fix02.diff I can confirm that this

Processed: Re: vserver kernel breaks ssh public_key authentication on NFS

2011-12-01 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: tags 633526 + patch Bug #633526 [linux-2.6] vserver kernel breaks ssh public_key authentication on NFS Added tag(s) patch. retitle 633526 NFS client uid/gid cache broken on VServer kernels Bug #633526 [linux-2.6] vserver kernel breaks ssh

Bug#650652: linux-image-2.6.32-5-amd64: Kernel IPsec code rejects 288-bit keys for AES-CTR as being too long

2011-12-01 Thread Calvin Owens
Package: linux-2.6 Version: 2.6.32-38 Severity: important Tags: patch The kernel incorrectly rejects 288-bit keys for AES-CTR (256 + 32 for nonce) as being too long. This is a rather major deficiency, as it prevents using AES-256-CTR at all for IPsec. This has been fixed as of the

Re: Moving default module/package lists out of kernel-wedge

2011-12-01 Thread Joey Hess
Ben Hutchings wrote: It's fairly obvious that the default module lists for Linux should be moved to the linux-2.6 source package. We can do that right now and use relative paths to include them in the per-architecture/flavour lists. However the #include foo-modules syntax would then be

Bug#649294: marked as done (linux-2.6: Duplicate battery after suspend/resume)

2011-12-01 Thread Debian Bug Tracking System
Your message dated Thu, 1 Dec 2011 19:22:58 +0100 with message-id 20111201182258.gn3...@radis.cristau.org and subject line Re: Bug#649294: linux-2.6: Duplicate battery after suspend/resume has caused the Debian Bug report #649294, regarding linux-2.6: Duplicate battery after suspend/resume to be

Bug#650652: Patch

2011-12-01 Thread Calvin Owens
commit 4203223a1aed862b4445fdcd260d6139603a51d9 Author: Tushar Gohad tgo...@mvista.com Date: Thu Jul 28 10:36:20 2011 + xfrm: Fix key lengths for rfc3686(ctr(aes)) Fix the min and max bit lengths for AES-CTR (RFC3686) keys. The number of bits in key spec is the key length

Bug#594676: [giggzounets...@googlemail.com: Re: Files Download Pb with the atl1c module and my ReadyNAS]

2011-12-01 Thread Jonathan Nieder
Forwarding with permission. ---BeginMessage--- Le jeudi 24 novembre 2011 à 00:42 -0600, Jonathan Nieder a écrit : Hi Guillaume, Ben Hutchings wrote: On Sat, 2010-08-28 at 11:23 +0200, giggz wrote: I have an eeepc 1201n with debian stable lenny+backports. So I'm using the kernel

Bug#613321: linux-image-amd64: Please enable 'memtest' option for all linux kernels

2011-12-01 Thread Jonathan Nieder
Uwe Kleine-König wrote: With the latter you have a test case to determine if your RAM is bad (or not). With the memtest kernel option memory is tested before it's given out to kmalloc. So it is able in some cases to just not give out bad parts of RAM allowing to use RAM that is a bit broken.

Bug#613321: linux-image-amd64: Please enable 'memtest' option for all linux kernels

2011-12-01 Thread Dmitry Smirnov
On Thursday 01 December 2011 23:09:03 Jonathan Nieder wrote: (Kernel image size is also a consideration, though probably not a major worry in this particular example.) Indeed. In this case we're talking about 130 lines of source code (3 KB), see arch/x86/mm/memtest.c If just few requests

Bug#613321: linux-image-amd64: Please enable 'memtest' option for all linux kernels

2011-12-01 Thread Dmitry Smirnov
On Friday 02 December 2011 07:59:02 Jonathan Nieder wrote: Having said that I don't know if it's sensible to add to Debian as I didn't test runtime and binary size overhead. Binary size overhead is really negligible. No opinion on that from me. It does seem a shame that many kinds of

[bts-link] source package linux-2.6

2011-12-01 Thread bts-link-upstream
# # bts-link upstream status pull for source package linux-2.6 # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html # user bts-link-upstr...@lists.alioth.debian.org # remote status report for #600846 (http://bugs.debian.org/600846) # Bug title: linux-image-2.6.32-5-amd64:

Processed: Re: linux-image-3.1.0-1-686-pae: Invalid opcode running df on seed Btrfs filesystem

2011-12-01 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: found 649847 linux-2.6/3.1.1-1 Bug #649847 [linux-2.6] linux-image-3.1.0-1-686-pae: Invalid opcode running df on seed Btrfs filesystem Bug Marked as found in versions linux-2.6/3.1.1-1. # Regression introduced by 6d07bcec969a (btrfs: fix wrong