Bug#612298: repeated columns on VGA/Radeon head

2011-02-07 Thread martin f krafft
Package: linux-2.6 Version: 2.6.37-1~experimental.1 Severity: normal This problem occurs when booting 2.6.37, but not with 2.6.36. I have three Radeon cards (HD 4350 / RV710), all using the free driver in a Zaphod configuration. I have three different screens connected, two DVI and one VGA. The

Bug#612300: linux-image-2.6.32-5-686: USB devices can't wakeup the system

2011-02-07 Thread Adam Sloboda
Package: linux-2.6 Version: 2.6.32-30 Severity: important Tags: upstream After upgrade to squeeze I can't wake up the PC anymore with USB dongle (remote control) and probably the same thing applies to UPS backup. It's nVidia ION based motherboard. /proc/acpi/wakeup is properly configured: USB0

Re: Bug#612300: linux-image-2.6.32-5-686: USB devices can't wakeup the system

2011-02-07 Thread marco giardina
On Mon, 07 Feb 2011 15:24:06 +0100 Adam Sloboda j...@disorder.sk wrote: bisogna attivarla sui tre pc Package: linux-2.6 Version: 2.6.32-30 Severity: important Tags: upstream After upgrade to squeeze I can't wake up the PC anymore with USB dongle (remote control) and probably the same

Bug#612300: linux-image-2.6.32-5-686: USB devices can't wakeup the system

2011-02-07 Thread maximilian attems
On Mon, Feb 07, 2011 at 03:24:06PM +0100, Adam Sloboda wrote: Package: linux-2.6 Version: 2.6.32-30 Severity: important Tags: upstream After upgrade to squeeze I can't wake up the PC anymore with USB dongle (remote control) and probably the same thing applies to UPS backup. It's nVidia

Bug#612300: linux-image-2.6.32-5-686: USB devices can't wakeup the system

2011-02-07 Thread Adam Sloboda
At Mon, 7 Feb 2011 14:58:14 +, maximilian attems wrote: On Mon, Feb 07, 2011 at 03:24:06PM +0100, Adam Sloboda wrote: Package: linux-2.6 Version: 2.6.32-30 Severity: important Tags: upstream After upgrade to squeeze I can't wake up the PC anymore with USB dongle (remote

Bug#612300: linux-image-2.6.32-5-686: USB devices can't wakeup the system

2011-02-07 Thread maximilian attems
On Mon, Feb 07, 2011 at 04:14:18PM +0100, Adam Sloboda wrote: At Mon, 7 Feb 2011 14:58:14 +, maximilian attems wrote: On Mon, Feb 07, 2011 at 03:24:06PM +0100, Adam Sloboda wrote: Package: linux-2.6 Version: 2.6.32-30 Severity: important Tags: upstream After

Bug#612300: linux-image-2.6.32-5-686: USB devices can't wakeup the system

2011-02-07 Thread Adam Sloboda
At Mon, 7 Feb 2011 16:06:14 +, maximilian attems wrote: There is no other version in the apt repository, I have nothing to test. I was very lucky to find this package on my laptop. There were *many* changes since, use http://snapshot.debian.org/ Sure, I am not disputing that. But

Bug#612300: linux-image-2.6.32-5-686: USB devices can't wakeup the system

2011-02-07 Thread maximilian attems
On Mon, Feb 07, 2011 at 05:24:43PM +0100, Adam Sloboda wrote: At Mon, 7 Feb 2011 16:06:14 +, maximilian attems wrote: There is no other version in the apt repository, I have nothing to test. I was very lucky to find this package on my laptop. There were *many* changes since,

Bug#612300: linux-image-2.6.32-5-686: USB devices can't wakeup the system

2011-02-07 Thread Adam Sloboda
At Mon, 7 Feb 2011 16:27:51 +, maximilian attems wrote: On Mon, Feb 07, 2011 at 05:24:43PM +0100, Adam Sloboda wrote: At Mon, 7 Feb 2011 16:06:14 +, maximilian attems wrote: There is no other version in the apt repository, I have nothing to test. I was very lucky to

Bug#612300: linux-image-2.6.32-5-686: USB devices can't wakeup the system

2011-02-07 Thread maximilian attems
On Mon, Feb 07, 2011 at 05:48:25PM +0100, Adam Sloboda wrote: The regression was introduced in 2.6.32-29 Right changelog has it: * USB: Retain device power/wakeup setting across reconfiguration; don't enable remote wakeup by default (Closes: #605246) -- To UNSUBSCRIBE, email to

Bug#612300: marked as done (linux-image-2.6.32-5-686: USB devices can't wakeup the system)

2011-02-07 Thread Debian Bug Tracking System
Your message dated Mon, 7 Feb 2011 18:44:22 + with message-id 20110207184422.gb21...@decadent.org.uk and subject line Re: Bug#612300: linux-image-2.6.32-5-686: USB devices can't wakeup the system has caused the Debian Bug report #612300, regarding linux-image-2.6.32-5-686: USB devices can't

Bug#612300: linux-image-2.6.32-5-686: USB devices can't wakeup the system

2011-02-07 Thread Adam Sloboda
At Mon, 7 Feb 2011 17:27:49 +, maximilian attems wrote: On Mon, Feb 07, 2011 at 05:48:25PM +0100, Adam Sloboda wrote: The regression was introduced in 2.6.32-29 Right changelog has it: * USB: Retain device power/wakeup setting across reconfiguration; don't enable remote

Re: For discussion: security support strategy for the wheezy kernel

2011-02-07 Thread Moritz Mühlenhoff
Michael Gilbert michael.s.gilb...@gmail.com schrieb: Hi, So, my proposal in a nutshell is to only upload upstream 2.6.32 point releases to wheezy/sid for the next 12-18 months. At that time, reevaluate and determine what the next longterm cadence kernel will be, and then once that is

Re: For discussion: security support strategy for the wheezy kernel

2011-02-07 Thread Ben Hutchings
On Mon, Feb 07, 2011 at 07:12:48PM +0100, Moritz Mühlenhoff wrote: Michael Gilbert michael.s.gilb...@gmail.com schrieb: Hi, So, my proposal in a nutshell is to only upload upstream 2.6.32 point releases to wheezy/sid for the next 12-18 months. At that time, reevaluate and determine

Bug#612340: linux-image-2.6.32-5-686: kernel 2.6.32-5 hang with call trace about inotify_inode_queue

2011-02-07 Thread Stephane Purnelle
Package: linux-2.6 Version: 2.6.32-30 Severity: important Tags: upstream After upgrade from debian 5, I am unable to boot with kernel 2.6.32-5. I can boot with the older kernel 2.6.22. It's maybe due to newer PATA drivers. I don't have all data for resolve because the problem is displayed

Re: [Secure-testing-team] For discussion: security support strategy for the wheezy kernel

2011-02-07 Thread Michael Gilbert
On Mon, 7 Feb 2011 19:12:48 +0100, Moritz Mühlenhoff wrote: Michael Gilbert michael.s.gilb...@gmail.com schrieb: Hi, So, my proposal in a nutshell is to only upload upstream 2.6.32 point releases to wheezy/sid for the next 12-18 months. At that time, reevaluate and determine what the

Re: [Secure-testing-team] For discussion: security support strategy for the wheezy kernel

2011-02-07 Thread Julien Cristau
On Mon, Feb 7, 2011 at 16:28:31 -0500, Michael Gilbert wrote: On Mon, 7 Feb 2011 19:12:48 +0100, Moritz Mühlenhoff wrote: Michael Gilbert michael.s.gilb...@gmail.com schrieb: Hi, So, my proposal in a nutshell is to only upload upstream 2.6.32 point releases to wheezy/sid for the

Re: [Secure-testing-team] For discussion: security support strategy for the wheezy kernel

2011-02-07 Thread Michael Gilbert
2011/2/7 Ben Hutchings wrote: On Mon, Feb 07, 2011 at 07:12:48PM +0100, Moritz Mühlenhoff wrote: Michael Gilbert michael.s.gilb...@gmail.com schrieb: Hi, So, my proposal in a nutshell is to only upload upstream 2.6.32 point releases to wheezy/sid for the next 12-18 months.  At that time,

Re: [Secure-testing-team] For discussion: security support strategy for the wheezy kernel

2011-02-07 Thread Michael Gilbert
On Mon, Feb 7, 2011 at 5:08 PM, Michael Gilbert wrote: What about introducing a new linux-2.6-stable kernel package as a compromise?  That way users that want stability and security support in testing continue to have that as an option.  Also, I will assume responsibility as the maintainer, so

Re: [Secure-testing-team] For discussion: security support strategy for the wheezy kernel

2011-02-07 Thread Michael Gilbert
On Mon, Feb 7, 2011 at 5:09 PM, Julien Cristau wrote: What does that buy us?  It means instead of dealing with bugs on an ongoing basis, you get them all at the same time and get to bisect along many kernel versions at once instead of just one.  It means problems don't get reported (and fixed)

Bug#612340: linux-image-2.6.32-5-686: kernel 2.6.32-5 hang with call trace about inotify_inode_queue

2011-02-07 Thread Ben Hutchings
On Mon, 2011-02-07 at 21:35 +0100, Stephane Purnelle wrote: Package: linux-2.6 Version: 2.6.32-30 Severity: important Tags: upstream Really, you tested an upstream version too? After upgrade from debian 5, I am unable to boot with kernel 2.6.32-5. I can boot with the older kernel 2.6.22.

Re: For discussion: security support strategy for the wheezy kernel

2011-02-07 Thread Michael Gilbert
On Mon, 7 Feb 2011 22:54:53 -0500 Michael Gilbert wrote: Even playing the numbers game with a bit more thoughtful analysis with the LWN data, lenny looks a lot better. It can be seen that lenny (2.6.26) was vulnerable to 69% (36 out of 52) of the vulnerabilities listed there, and squeeze

Bug#585085: Issue detected in Squeeze

2011-02-07 Thread Lawrence S K Ong
This issue is present in the newly released Squeeze. Using kernel: 2.6.32-5-amd64 nfs-common: 1.2.2-4 nfs-kernel-server: 1.2.2-4 Workaround is by downgrading to lenny's version of nfs-comon and nfs-kernel-server: nfs-common: 1.1.2-6lenny2 nfs-kernel-server: 1.1.2-6lenny2

Bug#607879: System hangs up with mmap.c:873!

2011-02-07 Thread Ronny Standtke
Fortunately, after some trial and error, I successfully built a linux-headers-2.6.32-5-common_2.6.32-30a~test package with the following two commands: export UPSTREAMVERSION=2.6.32-5 fakeroot make -f debian/rules.real binary-arch-featureset Is this the right