Trying to resume monthly(ish) d-i releases

2016-05-05 Thread Cyril Brulebois
Hi folks, I've been away from Debian and d-i duties for a while, but I'd like to get back to trying to release d-i every month or so. I've noticed ongoing discussions on #debian-kernel regarding the next target (security issues, etc.), and I'm not entirely sure when I'll find time to catch up

Bug#823552: endless "supply vcc not found, using dummy regulator"

2016-05-05 Thread Ben Hutchings
On Thu, 2016-05-05 at 23:29 +0200, Steinar H. Gunderson wrote: > Package: linux-image-4.5.0-2-armmp-lpae > Version: 4.5.2-1 > Severity: normal > > Hi, > > I'm installing an ODROID XU4 (Exynos 5422-based). After upgrading it to sid > and > installing 4.5.0-2-armmp-lpae (and generating the

Processed: reassign 823552 to src:linux

2016-05-05 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > reassign 823552 src:linux 4.5.2-1 Bug #823552 [linux-image-4.5.0-2-armmp-lpae] endless "supply vcc not found, using dummy regulator" Bug reassigned from package 'linux-image-4.5.0-2-armmp-lpae' to 'src:linux'. No longer marked as found in

Bug#823551: marked as done (linux-image-4.5.0-2-amd64: [graphdriver] prior storage driver "aufs" failed: driver not supported)

2016-05-05 Thread Debian Bug Tracking System
Your message dated Thu, 05 May 2016 22:57:26 +0100 with message-id <1462485446.19332.4.ca...@decadent.org.uk> and subject line Re: Bug#823551: linux-image-4.5.0-2-amd64: [graphdriver] prior storage driver "aufs" failed: driver not supported has caused the Debian Bug report #823551, regarding

Processed: severity of 823543 is important

2016-05-05 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > severity 823543 important Bug #823543 [src:linux] Kernel-image-4.5 amd64 does not boot; kernel 4.3 only boots in recovery. Severity set to 'important' from 'critical' > thanks Stopping processing here. Please contact me if you need assistance.

Processed: tagging 822396

2016-05-05 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > # Also affects testing; not a regression > tags 822396 - sid Bug #822396 [src:linux,src:glibc] and conflict needs to be resolved Bug #822378 [src:linux,src:glibc] and conflict needs to be resolved Bug #822393 [src:linux,src:glibc] and

Bug#823526: linux: FTBFS on powerpcspe due to the use of unsupported instructions

2016-05-05 Thread John Paul Adrian Glaubitz
On 05/05/2016 10:45 PM, Lennart Sorensen wrote: >> I just verified that the patch provided fixes the problem as expected. > > I have submitted it upstream. Great, that was quick. Please let me know in the bug tracker when it has been merged upstream, then Ben will be able to merge it in the

Bug#823551: linux-image-4.5.0-2-amd64: [graphdriver] prior storage driver "aufs" failed: driver not supported

2016-05-05 Thread joblack
Package: src:linux Version: 4.5.2-1 Severity: normal Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** Docker doesn't start because of missing aufs module root@koeck:/home/joblack# docker -d Warning: '-d' is deprecated, it will be removed soon. See

Bug#823552: endless "supply vcc not found, using dummy regulator"

2016-05-05 Thread Steinar H. Gunderson
Package: linux-image-4.5.0-2-armmp-lpae Version: 4.5.2-1 Severity: normal Hi, I'm installing an ODROID XU4 (Exynos 5422-based). After upgrading it to sid and installing 4.5.0-2-armmp-lpae (and generating the uInitrd myself, and updating boot.ini -- I'm not entirely sure if this can be done more

Processed: tagging 823522, notfound 823542 in 8:6.8.9.9-7+b2, found 823542 in 8:6.8.9.9-7 ...

2016-05-05 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tags 823522 + sid Bug #823522 [src:ngrok] ngrok: FTBFS: can't load package: package ngrok/cache: cannot find package "ngrok/cache" Added tag(s) sid. > notfound 823542 8:6.8.9.9-7+b2 Bug #823542 [imagemagick-common] imagemagick-common: please

Bug#823526: linux: FTBFS on powerpcspe due to the use of unsupported instructions

2016-05-05 Thread Lennart Sorensen
On Thu, May 05, 2016 at 10:26:18PM +0200, John Paul Adrian Glaubitz wrote: > Control: tags -1 + patch > > On 05/05/2016 09:32 PM, John Paul Adrian Glaubitz wrote: > >> If it works, I can submit it to the kernel. I don't have a powerpcspe > >> environment to try building it, but I did notice that

Bug#823526: linux: FTBFS on powerpcspe due to the use of unsupported instructions

2016-05-05 Thread John Paul Adrian Glaubitz
Control: tags -1 + patch On 05/05/2016 09:32 PM, John Paul Adrian Glaubitz wrote: >> If it works, I can submit it to the kernel. I don't have a powerpcspe >> environment to try building it, but I did notice that sstep.o contained >> those two instructions when building a ppc32 kernel, and that's

Processed: Re: Bug#823526: linux: FTBFS on powerpcspe due to the use of unsupported instructions

2016-05-05 Thread Debian Bug Tracking System
Processing control commands: > tags -1 + patch Bug #823526 [src:linux] linux: FTBFS on powerpcspe due to the use of unsupported instructions Added tag(s) patch. -- 823526: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=823526 Debian Bug Tracking System Contact ow...@bugs.debian.org with

Bug#823543: Kernel-image-4.5 amd64 does not boot; kernel 4.3 only boots in recovery.

2016-05-05 Thread Jonathan Polak
Package: src:linux Version: 4.5.1-1 AND 4.3.5-1 Severity: critical Justification: breaks the whole system System type: Lenovo X230 Distro: Debian Testing I was using kernel 4.3.5-1 because neither kernel 4.4 nor 4.5 booted normally. (See bug 819597). Between May 2 and May 4 I Upon updating the

Bug#798102: ams: Lots of kworker activity after wake from hibernate on Powerbook

2016-05-05 Thread Michael Hanselmann
Hello Dan and Mathieu On 18.04.2016 18:17, Michael Hanselmann wrote: > Fortunately I still have two devices with the two variants of the > sensor. I'm not able to look into this in more detail before early May, > but then I will try to spin up the hardware and reproduce the issue. I spent an

Bug#823526: linux: FTBFS on powerpcspe due to the use of unsupported instructions

2016-05-05 Thread Lennart Sorensen
On Thu, May 05, 2016 at 06:59:33PM +0200, John Paul Adrian Glaubitz wrote: > Source: linux > Version: 4.5.2-1 > Severity: normal > User: debian-powe...@lists.debian.org > Usertags: powerpcspe > > Hi! > > linux currently fails to build from source on powerpcspe since the compiler > is using FPU

Bug#823526: linux: FTBFS on powerpcspe due to the use of unsupported instructions

2016-05-05 Thread John Paul Adrian Glaubitz
On 05/05/2016 09:01 PM, Lennart Sorensen wrote: > I think this would fix it: > (...) Good idea, I'll give that a try! > It seems that gas on powerpc is willing to accept ldarx and stdcx even > when compiling in 32 bit mode (even though the instructions are not > allowed in 32 bit mode), while

Bug#823526: linux: FTBFS on powerpcspe due to the use of unsupported instructions

2016-05-05 Thread Lennart Sorensen
On Thu, May 05, 2016 at 06:59:33PM +0200, John Paul Adrian Glaubitz wrote: > Source: linux > Version: 4.5.2-1 > Severity: normal > User: debian-powe...@lists.debian.org > Usertags: powerpcspe > > Hi! > > linux currently fails to build from source on powerpcspe since the compiler > is using FPU

Bug#823526: linux: FTBFS on powerpcspe due to the use of unsupported instructions

2016-05-05 Thread Christian Zigotzky
Sent from my iPhone > On 05 May 2016, at 18:59, John Paul Adrian Glaubitz > wrote: > > Source: linux > Version: 4.5.2-1 > Severity: normal > User: debian-powe...@lists.debian.org > Usertags: powerpcspe > > Hi! > > linux currently fails to build from source on

Bug#823526: linux: FTBFS on powerpcspe due to the use of unsupported instructions

2016-05-05 Thread John Paul Adrian Glaubitz
Source: linux Version: 4.5.2-1 Severity: normal User: debian-powe...@lists.debian.org Usertags: powerpcspe Hi! linux currently fails to build from source on powerpcspe since the compiler is using FPU instructions which are not available on the e500v2 CPUs [1,2]: {standard input}: Assembler

Bug#794266: More tests

2016-05-05 Thread Manuel Roeder
Hello! I changed the bootargs in uboot to: [0.00] Kernel command line: console=ttyS0,115200 root=/dev/ram0 initrd=0xa0,0x90 ramdisk=32768 trace_event=i2c ... triggered the rtc-bug before this boot: [1.247677] rtc rtc0: invalid alarm value: 1900-1-7 1193037:1:16 [

Bug#768006: nfs-common: systemd fails to start nfs-common daemons before attmpting NFS mounts (NFSv3)

2016-05-05 Thread Donovan Baarda
Package: nfs-common Version: 1:1.2.8-9 Followup-For: Bug #768006 Dear Maintainer, I also encountered this problem, and had a nasty time trying to fix it. In my case I just want to nfs mount /home with this /etc/fstab entry; ngurra:/Minkirri/home nfs defaults,bg 0 0 On reboot

Processed: reassign 823493 to src:linux

2016-05-05 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > reassign 823493 src:linux 4.5.1-1 Bug #823493 [linux-image-4.5.0-1-armmp-lpae] BananaPi: libphy: PHY stmmac-0: not found Bug reassigned from package 'linux-image-4.5.0-1-armmp-lpae' to 'src:linux'. No longer marked as found in versions

Bug#823493: BananaPi: libphy: PHY stmmac-0:ffffffff not found

2016-05-05 Thread Heinrich Schuchardt
Package: linux-image-4.5.0-1-armmp-lpae Version: 4.5.1-1 Severity: Normal Dear maintainer, after upgrading my BananaPi to Debian stretch I cannot connect to ethernet anymore. I get the following messages: [ 649.676499] libphy: PHY stmmac-0: not found [ 649.681594] eth0: Could not

Re: linux 4.6 FTBFS on hppa

2016-05-05 Thread Ben Hutchings
On Thu, 2016-05-05 at 06:13 +0200, Helge Deller wrote: > Hi Ben, > > On 05.05.2016 03:29, Ben Hutchings wrote: [...] > Yes, but I tend to think that you are probably right to simply turnĀ  > CONFIG_MLONGCALLS back on again. > I do have kernel patches queued for kernel 4.7 which enable FTRACE

Bug#823485: kernel: brcmsmac bcma0:1: START: tid 1 is not agg'able

2016-05-05 Thread Mikhail Morfikov
Package: src:linux Version: 4.5.2-1 Severity: normal File: brcmsmac -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 I have the following WiFi hardware in my laptop: 03:00.0 Network controller [0280]: Broadcom Corporation BCM4313 802.11bgn Wireless Network Adapter [14e4:4727] (rev 01)