Processed: Re: Bug#779628: bcache: task bcache_writebac blocked for more than 240 seconds, system load high when module used

2016-02-05 Thread Debian Bug Tracking System
Processing control commands: > tag -1 patch fixed-upstream Bug #779628 [src:linux] bcache: task bcache_writebac blocked for more than 240 seconds, system load high when module used Added tag(s) patch and fixed-upstream. > fixed -1 4.3.3-6 Bug #779628 [src:linux] bcache: task bcache_writebac block

Bug#779628: bcache: task bcache_writebac blocked for more than 240 seconds, system load high when module used

2016-02-05 Thread Ben Hutchings
Control: tag -1 patch fixed-upstream Control: fixed -1 4.3.3-6 On Fri, 2016-02-05 at 21:09 +, Tim Small wrote: > Package: src:linux > Version: 3.16.7-ckt20-1+deb8u3 > Followup-For: Bug #779628 > > I think this patch fixes this issue: > > https://github.com/torvalds/linux/commit/627ccd20b4ad3

Bug#779628: bcache: task bcache_writebac blocked for more than 240 seconds, system load high when module used

2016-02-05 Thread Tim Small
Package: src:linux Version: 3.16.7-ckt20-1+deb8u3 Followup-For: Bug #779628 I think this patch fixes this issue: https://github.com/torvalds/linux/commit/627ccd20b4ad3ba836472468208e2ac4dfadbf03 It's included in this set which got merged in the 4.5 window. See this thread: https://lkml.org/lkm

Processed (with 1 error): reassign 795772 to lvm2, reassign 804629 to lvm2, merging 811033 795772 804629

2016-02-05 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > reassign 795772 lvm2 Bug #795772 [src:linux] [src:linux] linux-image-4.1.0-1 fails to boot on mirrored lvm Bug reassigned from package 'src:linux' to 'lvm2'. No longer marked as found in versions linux/4.1.3-1. Ignoring request to alter fixed ver

Re: Kernel version for stretch

2016-02-05 Thread Niels Thykier
Ben Hutchings: > On Tue, 2016-02-02 at 07:34 +, Niels Thykier wrote: > [...] >> >> Would you prefer that we moved future freezes (i.e. Buster and later), >> so we could always rely on Greg's branch? > > Yes, I would. > Ok, we will take it into consideration for the planning of the next freez

Bug#813327: linux-image-3.16.0-4-amd64: cryptroot + VIA padlock fails with message from testmgr.c

2016-02-05 Thread Ben Hutchings
On Fri, 2016-02-05 at 16:58 +0100, Carsten Wolff wrote: > On Friday 05 February 2016 01:10:37 Ben Hutchings wrote: > > I found what seems to be a bug in the driver, but it was present in > > both 3.2 and 3.16.  Please test whether the attached patch fixes this > > issue > > Hum, the patch only fix

Bug#799226: linux-image-4.1.0-2-amd64: Not able to mount LVM RAID1 file system at boot

2016-02-05 Thread Vladimir K
I also see this happening on Debian Jessie with kernel 3.16.7-ckt20-1+deb8u3 (and older 3.2). Root is on LVM RAID1, boot fails with error: device-mapper: table: 253:11: raid: Fail to run raid array In initramfs prompt I am able to see only technical volumes *_mlog_mimage_*, *_mimage_*, bu

Bug#813327: linux-image-3.16.0-4-amd64: cryptroot + VIA padlock fails with message from testmgr.c

2016-02-05 Thread Carsten Wolff
On Friday 05 February 2016 01:10:37 Ben Hutchings wrote: > I found what seems to be a bug in the driver, but it was present in > both 3.2 and 3.16. Please test whether the attached patch fixes this > issue Hum, the patch only fixes the decision, if and when the key is reset before an operation,

linux-2.6_2.6.32-48squeeze19_multi.changes ACCEPTED into squeeze-lts

2016-02-05 Thread Debian FTP Masters
Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Thu, 04 Feb 2016 19:06:47 + Source: linux-2.6 Binary: linux-tools-2.6.32 linux-source-2.6.32 linux-doc-2.6.32 linux-manual-2.6.32 linux-patch-debian-2.6.32 firmware-linux-free linux-support-2.6.32-5 linux-base lin

Processing of linux-2.6_2.6.32-48squeeze19_multi.changes

2016-02-05 Thread Debian FTP Masters
linux-2.6_2.6.32-48squeeze19_multi.changes uploaded successfully to localhost along with the files: linux-2.6_2.6.32-48squeeze19.dsc linux-2.6_2.6.32-48squeeze19.diff.gz linux-support-2.6.32-5_2.6.32-48squeeze19_all.deb firmware-linux-free_2.6.32-48squeeze19_all.deb linux-base_2.6.32-48sq

Re: Booting uncompressed kernel images

2016-02-05 Thread Ben Hutchings
On Fri, 2016-02-05 at 15:52 +0100, Andreas Ziegler wrote: > Hi, > > please allow me to dive in here, i do have a very similar problem. > > one of my VPS is running on a providers host system, that seems to use > an old Xen version, which can't boot the Jessie-Kernel. > at the moment im using the

Re: Booting uncompressed kernel images

2016-02-05 Thread Andreas Ziegler
Hi, please allow me to dive in here, i do have a very similar problem. one of my VPS is running on a providers host system, that seems to use an old Xen version, which can't boot the Jessie-Kernel. at the moment im using the wheezy-Kernel on jessie, but that's not the best solution... do i have

Bug#813764: linux-source-3.16: "Dazed and confused, but trying to continue" on X10SDV-TLN4F while using perf top

2016-02-05 Thread Ben Hutchings
Control: reassign -1 src:linux 3.16.7-ckt20-1+deb8u3 Control: tag -1 unreproducible moreinfo On Thu, 2016-02-04 at 23:25 -0500, Rich Ercolani wrote: > Package: linux-source-3.16 > Version: 3.16.0-4 > Severity: normal > > Dear Maintainer, > > I was going about my business, using perf top to see w

Processed: Re: Bug#813764: linux-source-3.16: "Dazed and confused, but trying to continue" on X10SDV-TLN4F while using perf top

2016-02-05 Thread Debian Bug Tracking System
Processing control commands: > reassign -1 src:linux 3.16.7-ckt20-1+deb8u3 Bug #813764 [linux-source-3.16] linux-source-3.16: "Dazed and confused, but trying to continue" on X10SDV-TLN4F while using perf top Bug reassigned from package 'linux-source-3.16' to 'src:linux'. No longer marked as found

Re: Booting uncompressed kernel images

2016-02-05 Thread Ian Campbell
On Thu, 2016-02-04 at 15:40 -0200, Tiago Ilieve wrote: > Sorry for the delay in my response. In the past couple days I was > confirming with Oracle if my findings (using virt-what, as you > suggested) where right and, indeed, they are supporting Xen HVM right > now. Great! > > So, there's no nee