Processed: tagging 809740

2016-02-01 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tags 809740 + pending Bug #809740 [src:initramfs-tools] initramfs-tools: Completely ignores rootdelay Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 809740:

Re: Booting uncompressed kernel images

2016-02-01 Thread Tiago Ilieve
Hi Jose, I'm dropping off the cc of "debian-cloud at l.d.o", because this is really a kernel matter, so I see no reason for cross-posting. I can post the outcome in there when we reach a solution. On 1 February 2016 at 08:37, Jose R R wrote: > Does the kernel boot after

Booting uncompressed kernel images

2016-02-01 Thread Tiago Ilieve
Hi, I have a scenario[1] where the default Linux kernel compressed with XZ (from Jessie and up) cannot be booted. The first thing that I've tried was to uncompress it using "extract-linux"[2] and it didn't worked by the time, so I decided to rebuild the entire "linux-image-*" package changing

Re: Booting uncompressed kernel images

2016-02-01 Thread Ian Campbell
On Mon, 2016-02-01 at 06:03 -0200, Tiago Ilieve wrote: > Hi, > > I have a scenario[1] where the default Linux kernel compressed with XZ > (from Jessie and up) cannot be booted. The first thing that I've tried > was to uncompress it using "extract-linux"[2] and it didn't worked by > the time, so I

Re: Booting uncompressed kernel images

2016-02-01 Thread Ian Campbell
On Mon, 2016-02-01 at 10:06 +, Ian Campbell wrote: > On Mon, 2016-02-01 at 06:03 -0200, Tiago Ilieve wrote: > > Hi, > > > > I have a scenario[1] where the default Linux kernel compressed with XZ > > (from Jessie and up) cannot be booted. The first thing that I've tried > > was to uncompress

Re: Booting uncompressed kernel images

2016-02-01 Thread Jose R R
On Mon, Feb 1, 2016 at 12:03 AM, Tiago Ilieve wrote: > Hi, > > I have a scenario[1] where the default Linux kernel compressed with XZ > (from Jessie and up) cannot be booted. The first thing that I've tried > was to uncompress it using "extract-linux"[2] and it didn't

Bug#808043: closed by Ben Hutchings <b...@decadent.org.uk> (Re: linux-image-4.3.0-1-powerpc64: Fail to load md_mod with unknow symbol error)

2016-02-01 Thread Christian Marillat
reopen 808043 thanks On 28 janv. 2016 01:36, ow...@bugs.debian.org (Debian Bug Tracking System) wrote: [...] > On Tue, 15 Dec 2015 15:26:39 +0100 Christian Marillat > wrote: >> Package: src:linux >> Version: 4.3.1-1 >> Severity: serious >>  >> Dear Maintainer, >>  >>

Processed: Re: Bug#808043 closed by Ben Hutchings <b...@decadent.org.uk> (Re: linux-image-4.3.0-1-powerpc64: Fail to load md_mod with unknow symbol error)

2016-02-01 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > reopen 808043 Bug #808043 {Done: Ben Hutchings } [src:linux] [powerpc] Modules fail to load following toolchain upgrade Bug reopened Ignoring request to alter fixed versions of bug #808043 to the same values previously set

Re: broken mount behaviour on jessie

2016-02-01 Thread Raphael Hertzog
Hi, On Mon, 01 Feb 2016, Brian May wrote: > I see two patches here - one patch applies easy enough to schroot - > 1.6-schroot-mount-make-bind-mounts-private.patch > > I am not sure what the > master-libexec-mount-make-bind-mounts-private.patch is for, it seems to > patch files not in schroot but

Bug#784688: Thousands of "xen:balloon: Cannot add additional memory (-17) messages" despite dom0 ballooning disabled

2016-02-01 Thread Ian Campbell
On Fri, 2016-01-29 at 15:59 +, Andy Smith wrote: > Hi Ian, > > On Fri, Jan 29, 2016 at 02:57:23PM +, Ian Campbell wrote: > > I spent a bit of time investigating this, but sadly I'm not able to > > reproduce the basis failure. > > FWIW it was me who reported this with the packages in

Bug#809928: linux-image-4.3.0-1-m68k: does not boot any more (on ARAnyM)

2016-02-01 Thread John Paul Adrian Glaubitz
On 01/24/2016 11:48 AM, John Paul Adrian Glaubitz wrote: > Can you try kernel 4.4 from experimental? That should be available > as of now as I have enabled building experimental packages for > m68k now. Linux 4.4 works fine here on Aranym: root@pacman:~> uname -a Linux pacman 4.4.0-trunk-m68k #1

Re: broken mount behaviour on jessie

2016-02-01 Thread Peter Palfrader
On Mon, 01 Feb 2016, Brian May wrote: > Michael Biebl writes: > > > Have you tried the patch in > > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=786566 > > I see two patches here - one patch applies easy enough to schroot - >

Re: broken mount behaviour on jessie

2016-02-01 Thread Brian May
Michael Biebl writes: > Have you tried the patch in > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=786566 I see two patches here - one patch applies easy enough to schroot - 1.6-schroot-mount-make-bind-mounts-private.patch I am not sure what the

Bug#803159: linux: Enable DT support for armel/orion5x arch

2016-02-01 Thread Ben Hutchings
Control: fixed -1 4.3-1~exp2 On Tue, 2016-02-02 at 00:39 +0900, Roger Shimizu wrote: > Control: reopen -1 It was not necessary to reopen this bug, as the BTS can keep track of whether it is actually fixed in each suite. Ben. -- Ben Hutchings Larkinson's Law: All laws are basically false.

Bug#805122: marked as done (linux: kernel panic instead of boot on m68k (ARAnyM))

2016-02-01 Thread Debian Bug Tracking System
Your message dated Mon, 01 Feb 2016 17:28:32 + with message-id <1454347712.13367.40.ca...@decadent.org.uk> and subject line Re: Bug#809928: linux-image-4.3.0-1-m68k: does not boot any more (on ARAnyM) has caused the Debian Bug report #809928, regarding linux: kernel panic instead of boot on

Re: Kernel version for stretch

2016-02-01 Thread Niels Thykier
Hi Ben, Pulling in d-i on this, since they might be affected by this. If you know of a maintainer that would be similarly affected, let me know, so we can ask them as well. Ben Hutchings: > [...] > > For stretch, I would very much like to choose a kernel version for > stretch that gets

Bug#803159: linux: Enable DT support for armel/orion5x arch

2016-02-01 Thread Roger Shimizu
Control: reopen -1 On Fri, Jan 8, 2016 at 1:24 AM, Roger Shimizu wrote: > Dear Kernel Maintainers, > > I'm wondering whether it's possible to add armel/orion5x support to > "jessie proposed update kernel" series. > If so, here's the changes need to be made: > -

Processed: Re: Bug#803159: linux: Enable DT support for armel/orion5x arch

2016-02-01 Thread Debian Bug Tracking System
Processing control commands: > reopen -1 Bug #803159 {Done: Ben Hutchings } [linux] linux: Enable DT support for armel/orion5x arch 'reopen' may be inappropriate when a bug has been closed with a version; all fixed versions will be cleared, and you may need to re-add them.

Processed: Re: Bug#803159: linux: Enable DT support for armel/orion5x arch

2016-02-01 Thread Debian Bug Tracking System
Processing control commands: > fixed -1 4.3-1~exp2 Bug #803159 [linux] linux: Enable DT support for armel/orion5x arch There is no source info for the package 'linux' at version '4.3-1~exp2' with architecture '' Unable to make a source version for version '4.3-1~exp2' Marked as fixed in versions

Bug#809928: marked as done (linux-image-4.3.0-1-m68k: does not boot any more (on ARAnyM))

2016-02-01 Thread Debian Bug Tracking System
Your message dated Mon, 01 Feb 2016 17:28:32 + with message-id <1454347712.13367.40.ca...@decadent.org.uk> and subject line Re: Bug#809928: linux-image-4.3.0-1-m68k: does not boot any more (on ARAnyM) has caused the Debian Bug report #809928, regarding linux-image-4.3.0-1-m68k: does not boot