Processed: unarchiving 502816, reopening 502816, found 502816 in 3.1.5-1 ...

Processing commands for cont...@bugs.debian.org: unarchive 502816 Bug #502816 {Done: Moritz Muehlenhoff j...@inutil.org} [linux-2.6] cannot suspend Unarchived Bug 502816 reopen 502816 Bug #502816 {Done: Moritz Muehlenhoff j...@inutil.org} [linux-2.6] cannot suspend found 502816 3.1.5-1 Bug

Bug#502816: Processed: unarchiving 502816, reopening 502816, found 502816 in 3.1.5-1 ...

Alexander GQ Gerasiov wrote: unarchive 502816 reopen 502816 found 502816 3.1.5-1 found 502816 3.2~rc4-1~experimental.1 Do you use a Thinkpad T61, too? Thanks for writing, Jonathan -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble?

Processed: found 502816 in 3.1.6-1

Processing commands for cont...@bugs.debian.org: found 502816 3.1.6-1 Bug #502816 [linux-2.6] cannot suspend There is no source info for the package 'linux-2.6' at version '3.1.6-1' with architecture '' Unable to make a source version for version '3.1.6-1' Bug Marked as found in versions

Bug#652857: Missing support for Intel C600 Series SAS/SATA controllers

On Sun, 2011-12-25 at 10:05 -0800, Vahidin Memić wrote: I was wondering when will I see the new kernel version available for the installer so it can recognize my SATA problem I have been having with the Intel C600. I thought on Friday someone mentioned to me that the new kernel 3.1.6-1 will be

Bug#586494: marked as done (linux-image-2.6.26-2-686: Dell PowerEdge 4200's don't work with 2.6.26)

Your message dated Mon, 26 Dec 2011 13:57:41 + with message-id e1rfb3d-000329...@franck.debian.org and subject line Bug#586494: fixed in linux-2.6 2.6.32-40 has caused the Debian Bug report #586494, regarding linux-image-2.6.26-2-686: Dell PowerEdge 4200's don't work with 2.6.26 to be marked

Bug#637234: marked as done (linux-image-3.0.0-1-686-pae: I/O errors using ext4 under xen (also affects ext3 as of linux-image-3.1.0-1-amd64 et al))

Your message dated Mon, 26 Dec 2011 13:57:41 + with message-id e1rfb3d-00032k...@franck.debian.org and subject line Bug#637234: fixed in linux-2.6 2.6.32-40 has caused the Debian Bug report #637234, regarding linux-image-3.0.0-1-686-pae: I/O errors using ext4 under xen (also affects ext3 as

Bug#633526: marked as done (NFS client uid/gid cache broken on VServer kernels)

Your message dated Mon, 26 Dec 2011 13:57:41 + with message-id e1rfb3d-00032f...@franck.debian.org and subject line Bug#633526: fixed in linux-2.6 2.6.32-40 has caused the Debian Bug report #633526, regarding NFS client uid/gid cache broken on VServer kernels to be marked as done. This means

Bug#638172: marked as done (BUG: soft lockup - CPU#0 stuck for 61s! [qemu-dm:3205])

Your message dated Mon, 26 Dec 2011 13:57:41 + with message-id e1rfb3d-00032u...@franck.debian.org and subject line Bug#638172: fixed in linux-2.6 2.6.32-40 has caused the Debian Bug report #638172, regarding BUG: soft lockup - CPU#0 stuck for 61s! [qemu-dm:3205] to be marked as done. This

Bug#646917: marked as done (base: Debian gets unresponsive on higher IO load - BUG: soft lockup - CPU#0 stuck for 61s)

Your message dated Mon, 26 Dec 2011 13:57:41 + with message-id e1rfb3d-00032u...@franck.debian.org and subject line Bug#638172: fixed in linux-2.6 2.6.32-40 has caused the Debian Bug report #638172, regarding base: Debian gets unresponsive on higher IO load - BUG: soft lockup - CPU#0 stuck

Bug#647624: marked as done (Changes from longterm 2.6.32.47)

Your message dated Mon, 26 Dec 2011 13:57:41 + with message-id e1rfb3d-00032j...@franck.debian.org and subject line Bug#647624: fixed in linux-2.6 2.6.32-40 has caused the Debian Bug report #647624, regarding Changes from longterm 2.6.32.47 to be marked as done. This means that you claim that

Bug#650160: marked as done (Changes from longterm release 2.6.32.49)

Your message dated Mon, 26 Dec 2011 13:57:41 + with message-id e1rfb3d-00032o...@franck.debian.org and subject line Bug#650160: fixed in linux-2.6 2.6.32-40 has caused the Debian Bug report #650160, regarding Changes from longterm release 2.6.32.49 to be marked as done. This means that you

Bug#651255: marked as done (ipv6: Fails to report all IPv6 addresses assigned to interface)

Your message dated Mon, 26 Dec 2011 13:57:41 + with message-id e1rfb3d-00032y...@franck.debian.org and subject line Bug#651255: fixed in linux-2.6 2.6.32-40 has caused the Debian Bug report #651255, regarding ipv6: Fails to report all IPv6 addresses assigned to interface to be marked as done.

Bug#651367: marked as done (Changes from longterm release 2.6.32.50)

Your message dated Mon, 26 Dec 2011 13:57:41 + with message-id e1rfb3d-000333...@franck.debian.org and subject line Bug#651367: fixed in linux-2.6 2.6.32-40 has caused the Debian Bug report #651367, regarding Changes from longterm release 2.6.32.50 to be marked as done. This means that you

Bug#652857: marked as done (Missing support for Intel C600 Series SAS/SATA controllers)

Your message dated Mon, 26 Dec 2011 13:57:41 + with message-id e1rfb3d-000338...@franck.debian.org and subject line Bug#652857: fixed in linux-2.6 2.6.32-40 has caused the Debian Bug report #652857, regarding Missing support for Intel C600 Series SAS/SATA controllers to be marked as done.

linux-2.6_2.6.32-40_amd64.changes ACCEPTED into proposed-updates

Notes: Mapping stable to proposed-updates. Accepted: firmware-linux-free_2.6.32-40_all.deb to main/l/linux-2.6/firmware-linux-free_2.6.32-40_all.deb linux-2.6_2.6.32-40.diff.gz to main/l/linux-2.6/linux-2.6_2.6.32-40.diff.gz linux-2.6_2.6.32-40.dsc to

Bug#602095: [nouveau] black screen after reboot

Hi, I'm not sure what I'm supposed to do with this message... Results of preceding discussions: Please remove the nvidia driver, unblacklist nouveau, and attach the resulting dmesg. I can't do that. If I unblacklist nouveau and remove the nvidia driver, I just get a black screen right

Bug#652596: marked as done (Changes from longterm release 2.6.32.51)

Your message dated Mon, 26 Dec 2011 17:28:21 +0100 with message-id 1324916901.14957.3.camel@deadeye and subject line Re: Changes from longterm release 2.6.32.51 has caused the Debian Bug report #652596, regarding Changes from longterm release 2.6.32.51 to be marked as done. This means that you

Bug#641749: ath3k_load_firmware: Can't change to loading configuration err

Hi there Yes, no ideas here, either.  Please contact linux-blueto...@vger.kernel.org, cc-ing linux-ker...@vger.kernel.org and either me or this bug log so we can track it. I've spotted something odd that may give us some light as to why it's not working and I wanted to discuss it here before

Processed: severity of 653292 is important

Processing commands for cont...@bugs.debian.org: severity 653292 important Bug #653292 [linux-2.6] nfs exclusive lock does not work anymore after openvz kernel version : 2.6.32-35squeeze1 Severity set to 'important' from 'critical' thanks Stopping processing here. Please contact me if you

Bug#653314: e1000e: Wake-on-lan from hibernate broken since 2.6.32-36

Package: linux-2.6 Version: 2.6.32-39 Severity: normal Tags: squeeze Between 2.6.32-35 and 2.6.32-36, the ability to wake-on-lan from suspend-to-disk got lost for my mainboard. Waking from poweroff and from suspend-to-ram still works. This is probably related to bug #627700. The bug is present up

Bug#627372: Console turns black during boot.

The bug has been reported as https://bugs.freedesktop.org/show_bug.cgi?id=44156 Alan On Thu, Dec 22, 2011 at 9:36 PM, Jonathan Nieder jrnie...@gmail.com wrote: Alan Zimmerman wrote: I reinstalled the video-intel package. When the console turns black, the machine is still usable. Booting

Processed: Re: Console turns black during boot.

Processing commands for cont...@bugs.debian.org: forwarded 627372 https://bugs.freedesktop.org/show_bug.cgi?id=44156 Bug #627372 [linux-2.6] linux-image-2.6.38-2-686: Console turns black during boot Set Bug forwarded-to-address to 'https://bugs.freedesktop.org/show_bug.cgi?id=44156'. End of

Bug#653192: marked as done (linux 3.2~rc4-1~experimental.1: Intel X-25M SSD destroyed)

Your message dated Mon, 26 Dec 2011 21:22:11 + with message-id 4ef8e583.1000...@pyro.eu.org and subject line Bug#653192: Re: Intel X-25M SSD destroyed has caused the Debian Bug report #653192, regarding linux 3.2~rc4-1~experimental.1: Intel X-25M SSD destroyed to be marked as done. This

Bug#627019: several kernel hangs before geting to login

  Monday, December 26, 2011 5:24 PMWill Set wrote: Sunday, December 25, 2011 4:24 AM Jonathan Nieder wrote: Will Set wrote: Jonathan Nieder wrote but the boot fails in some way unless you add processor.nocst=1 to the kernel command line.  [...] I had to test using  3.1.0-1-686-pae (

Bug#653331: linux-image-3.1.0-1-686-pae: CPU#0 stuck for 23s, system does not boot

Package: linux-2.6 Version: 3.1.1-1 Severity: critical Justification: breaks the whole system Dear Maintainer, First of all, thanks for looking into this.. I've installed debian-stable with 2.6.32 kernel. After that, I made the upgrade to wheezy. From that moment on, the system no longer boots:

Bug#653331: linux-image-3.1.0-1-686-pae: CPU#0 stuck for 23s, system does not boot

On Tue, 2011-12-27 at 03:16 +0100, P. van Gaans wrote: Package: linux-2.6 Version: 3.1.1-1 Please try the current version in testing, 3.1.5-1. Severity: critical Justification: breaks the whole system Dear Maintainer, First of all, thanks for looking into this.. I've installed

Processed: severity of 653331 is important, tagging 653331

Processing commands for cont...@bugs.debian.org: severity 653331 important Bug #653331 [linux-2.6] linux-image-3.1.0-1-686-pae: CPU#0 stuck for 23s, system does not boot Severity set to 'important' from 'critical' tags 653331 + moreinfo Bug #653331 [linux-2.6] linux-image-3.1.0-1-686-pae: