Re: Bug#579017: autodetection fails when booting with 64-bit kernel on 32-bit userland

2010-05-04 Thread Stanislav Maslovski
On Mon, May 03, 2010 at 08:16:50PM +0200, Julien Cristau wrote: > reassign 579017 linux-2.6 2.6.32-9 > kthxbye > > On Sat, Apr 24, 2010 at 15:27:11 +0400, Stanislav Maslovski wrote: > > > Package: xserver-xorg-input-synaptics > > Version: 1.2.2-2 > > Severity: normal > > > > Without giving the e

Bug#580068: Bug#580050: linux-image-2.6.32-3-amd64: kcryptd crashes under heavy I/O

2010-05-04 Thread Juha
On Mon, May 3, 2010 at 4:18 PM, Ben Hutchings wrote: > This might or might not be related.  I have split it off as bug #580068. > > Please use 'reportbug -N 580068' to add information about the network > configuration for your computer. After some more testing I noticed that the same problem occu

linux-latest-2.6_26_i386.changes ACCEPTED

2010-05-04 Thread Archive Administrator
Accepted: linux-headers-2.6-486_2.6.32+26_i386.deb to main/l/linux-latest-2.6/linux-headers-2.6-486_2.6.32+26_i386.deb linux-headers-2.6-686-bigmem_2.6.32+26_i386.deb to main/l/linux-latest-2.6/linux-headers-2.6-686-bigmem_2.6.32+26_i386.deb linux-headers-2.6-686_2.6.32+26_i386.deb to main

linux-latest-2.6_27_i386.changes ACCEPTED

2010-05-04 Thread Archive Administrator
Accepted: linux-doc-2.6_27_all.deb to main/l/linux-latest-2.6/linux-doc-2.6_27_all.deb linux-headers-2.6-486_2.6.32+27_i386.deb to main/l/linux-latest-2.6/linux-headers-2.6-486_2.6.32+27_i386.deb linux-headers-2.6-686-bigmem_2.6.32+27_i386.deb to main/l/linux-latest-2.6/linux-headers-2.6-6

Bug#347284: marked as done (linux-doc-2.6.14: get the latest linux-doc)

2010-05-04 Thread Debian Bug Tracking System
Your message dated Tue, 04 May 2010 11:19:18 + with message-id and subject line Bug#347284: fixed in linux-latest-2.6 26 has caused the Debian Bug report #347284, regarding linux-doc-2.6.14: get the latest linux-doc to be marked as done. This means that you claim that the problem has been dea

Bug#480060: marked as done (linux-doc-2.6.24: inconsistency between image/headers virtual package and doc virtual package)

2010-05-04 Thread Debian Bug Tracking System
Your message dated Tue, 04 May 2010 11:19:18 + with message-id and subject line Bug#347284: fixed in linux-latest-2.6 26 has caused the Debian Bug report #347284, regarding linux-doc-2.6.24: inconsistency between image/headers virtual package and doc virtual package to be marked as done. Thi

firmware-nonfree_0.24_i386.changes ACCEPTED

2010-05-04 Thread Archive Administrator
Accepted: firmware-bnx2_0.24_all.deb to non-free/f/firmware-nonfree/firmware-bnx2_0.24_all.deb firmware-bnx2x_0.24_all.deb to non-free/f/firmware-nonfree/firmware-bnx2x_0.24_all.deb firmware-intelwimax_0.24_all.deb to non-free/f/firmware-nonfree/firmware-intelwimax_0.24_all.deb firmware-ip

Bug#574145: marked as done (confusing use of debconf for license agreement)

2010-05-04 Thread Debian Bug Tracking System
Your message dated Tue, 04 May 2010 11:32:28 + with message-id and subject line Bug#574145: fixed in firmware-nonfree 0.24 has caused the Debian Bug report #574145, regarding confusing use of debconf for license agreement to be marked as done. This means that you claim that the problem has be

Bug#576104: marked as done (extra copyright file should include rlc.bin files)

2010-05-04 Thread Debian Bug Tracking System
Your message dated Tue, 04 May 2010 11:32:28 + with message-id and subject line Bug#576104: fixed in firmware-nonfree 0.24 has caused the Debian Bug report #576104, regarding extra copyright file should include rlc.bin files to be marked as done. This means that you claim that the problem has

Bug#579694: marked as done (firmware-nonfree: Please include rtl8192su/ r8192s_usb firmware into the (unreleased) firmware-realtek binary package.)

2010-05-04 Thread Debian Bug Tracking System
Your message dated Tue, 04 May 2010 11:32:28 + with message-id and subject line Bug#579694: fixed in firmware-nonfree 0.24 has caused the Debian Bug report #579694, regarding firmware-nonfree: Please include rtl8192su/ r8192s_usb firmware into the (unreleased) firmware-realtek binary package.

Bug#573950: marked as done (Please include RTL8192E firmware)

2010-05-04 Thread Debian Bug Tracking System
Your message dated Tue, 04 May 2010 11:32:28 + with message-id and subject line Bug#573950: fixed in firmware-nonfree 0.24 has caused the Debian Bug report #573950, regarding Please include RTL8192E firmware to be marked as done. This means that you claim that the problem has been dealt with.

Bug#563313: that's not fair!

2010-05-04 Thread Γιώργος Πάλλας
I regularly follow testing's upgrades. So I was with 2.6.30, the sensors were working fine. I got 2.6.32-3 sensors broken. And I must wait until 2.6.32-12 (!) to get it working again? Why doesn't a patch slip into 2.6.32-3 ?? Am I missing something? With real respect to your job, Giorgos Palla

Bug#580214: linux-image-2.6.32-5: cannot mount (or fsck) a usb disk at boot time

2010-05-04 Thread Alan Braslau
Package: linux-source-2.6.32 Version: 2.6.32-12 Severity: normal Tags: sid A second hard disk is installed on my computer as an external usb device. Since the last kernel update (either using an official debian kernel-image or a locally compiled kernel from debian sources), mounting of this disk

Processed: tagging 580214

2010-05-04 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tags 580214 - sid Bug #580214 [linux-source-2.6.32] linux-image-2.6.32-5: cannot mount (or fsck) a usb disk at boot time Removed tag(s) sid. > thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system

Bug#563313: that's not fair!

2010-05-04 Thread Ben Hutchings
On Tue, May 04, 2010 at 02:23:20PM +0300, Γιώργος Πάλλας wrote: > I regularly follow testing's upgrades. So I was with 2.6.30, the sensors > were working fine. I got 2.6.32-3 sensors broken. And I must wait until > 2.6.32-12 (!) to get it working again? Why doesn't a patch slip into > 2.6.32-

uploading 2.6.33

2010-05-04 Thread maximilian attems
will upload 2.6.33 to experimental tomorrow after 12 UT. phylib has a current trouble to compile, any other outstanding issues? plan is that to be the last 2.6.33 and then move on to 2.6.34 to provide testers with really the latest linux-2.6. thanks -- To UNSUBSCRIBE, email to debian-kernel

Re: Bug#365349: linux-image-*-dbg for squeeze?

2010-05-04 Thread Lucas Nussbaum
On 26/04/10 at 21:01 +0200, Joerg Jaspert wrote: > >> > I wonder what we (as Debian) could do about it. Would it make sense to > >> > sponsor a very fast machine that the kernel team could use to build the > >> > kernels and upload from, replacing kernel-archive.buildserver.net ? > >> The easiest f

Re: uploading 2.6.33

2010-05-04 Thread Ben Hutchings
On Tue, 2010-05-04 at 17:35 +0200, maximilian attems wrote: > will upload 2.6.33 to experimental tomorrow after 12 UT. > > > phylib has a current trouble to compile, Now fixed. > any other outstanding issues? I suspect there are some other patches that should be copied from sid. > plan is tha

Bug#580068: Bug#580050: linux-image-2.6.32-3-amd64: kcryptd crashes under heavy I/O

2010-05-04 Thread Ben Hutchings
On Tue, 2010-05-04 at 13:46 +0300, Juha wrote: > On Mon, May 3, 2010 at 4:18 PM, Ben Hutchings wrote: > > This might or might not be related. I have split it off as bug #580068. > > > > Please use 'reportbug -N 580068' to add information about the network > > configuration for your computer. > >

Bug#470474: cpufrequtils: Laptop limited to 1.2GHz vs 2.2GHz when no battery, running on AC only.

2010-05-04 Thread Ben Hutchings
On Mon, 2010-05-03 at 12:19 -0400, Greg Folkert wrote: > On Mon, 2010-05-03 at 15:41 +0100, Ben Hutchings wrote: > [...] > > > > Please report this upstream at under > > product 'Power Management, component 'cpufreq'. Let us know the bug > > number so that we can tra

Bug#367026: Nope, stll doesn't work

2010-05-04 Thread Daniel Dickinson
On Sat, 1 May 2010 23:08:54 +0200 Moritz Muehlenhoff wrote: > On Wed, Feb 25, 2009 at 08:43:10PM -0500, Daniel Dickinson wrote: > > In response to your query; I don't have the Logitech mouse anymore > > but I just tested and Microsoft mice don't work so it probably is > > still not working for an