Processed: your mail

2018-03-22 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > package initramfs-tools Limiting to bugs with field 'package' containing at least one of 'initramfs-tools' Limit currently set to 'package':'initramfs-tools' > tags 883664 + patch Bug #883664 [initramfs-tools] DEVICE= in initramfs.conf is ignore

Processed: severity of 893829 is important

2018-03-22 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > severity 893829 important Bug #893829 [src:linux] linux-image-4.9.0-6-amd64: hv_netvsc stuk in loop if setting both channels and mtu Severity set to 'important' from 'critical' > thanks Stopping processing here. Please contact me if you need ass

Re: armel/marvell kernel size

2018-03-22 Thread Ben Hutchings
On Thu, 2018-03-22 at 00:12 -0300, Rogério Brito wrote: [...] > If nobody is working on getting a new kernel working on armel, I would > like to (at least, unsuccessfully) try to get it to compile. > > At worst, I believe, I can gain some knowledge and compare what I get from > this armel kernel w

Bug#893829: linux-image-4.9.0-6-amd64: hv_netvsc stuk in loop if setting both channels and mtu

2018-03-22 Thread Yorick de Wid
Package: src:linux Version: 4.9.82-1+deb9u3 Severity: critical Justification: breaks the whole system Dear Maintainer, If both the MTU and channels are set using ethtool the Microsoft Hyper-V network drivers crashes. The network driver gets stuck in a loop and causes one or more kernel threads

Re: armel/marvell kernel size

2018-03-22 Thread Rogério Brito
Dear Roger and other people! On Thu, Mar 22, 2018 at 8:40 AM, Roger Shimizu wrote: > Good to hear from you again! Thank you very much. Glad to hear from you again, keeping the armel flame lit! First of all, it seems weird that my previous message didn't get to the lists. I find this very strang

Processed: tagging 887304

2018-03-22 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tags 887304 + moreinfo Bug #887304 [src:linux] linux-image-4.14.0-0.bpo.2-amd64: Error crypto/algapi.c:348 and a long system boot. Added tag(s) moreinfo. > thanks Stopping processing here. Please contact me if you need assistance. -- 887304: ht

reassign 893805 to src:linux, closing 893805

2018-03-22 Thread Salvatore Bonaccorso
reassign 893805 src:linux 4.14.13-1 close 893805 4.15.4-1 thanks

Bug#887304: linux-image-4.14.0-0.bpo.2-amd64: Error crypto/algapi.c:348 and a long system boot.

2018-03-22 Thread Salvatore Bonaccorso
Hi, On Wed, Mar 21, 2018 at 10:56:57AM -0400, LeJacq, Jean Pierre wrote: > I've tested the following two kernels from sid on a stretch system and they > both DO NOT exhibit this bug: > > linux-image-4.15.0-1-amd64 > linux-image-4.15.0-2-amd64 > > Instead of the kernel null pointer e

Processed: reassign 893805 to src:linux, closing 893805

2018-03-22 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > reassign 893805 src:linux 4.14.13-1 Bug #893805 [linux-image-amd64] linux-image-amd64: enable CONFIG_IPV6_SEG6_LWTUNNEL Bug reassigned from package 'linux-image-amd64' to 'src:linux'. No longer marked as found in versions linux-latest/89~bpo9+1.

Bug#893805: linux-image-amd64: enable CONFIG_IPV6_SEG6_LWTUNNEL

2018-03-22 Thread Magnus Frühling
Package: linux-image-amd64 Version: 4.14+89~bpo9+1 Severity: wishlist Dear Maintainer, Please enable CONFIG_IPV6_SEG6_LWTUNNEL & CONFIG_IPV6_SEG6_HMAC in linux kernel builds so that SRv6 is possible. http://www.segment-routing.org/index.php/Implementation/Installation -- System Information: Debi

Re: armel/marvell kernel size

2018-03-22 Thread Roger Shimizu
Dear Rogério, Good to hear from you again! On Thu, Mar 22, 2018 at 12:12 PM, Rogério Brito wrote: > Hi, all (and sorry for jumping in a bit late). > > On 2018-02-17 10:48, Salvatore Bonaccorso wrote: >> On Tue, Jan 23, 2018 at 06:30:23PM +, Ben Hutchings wrote: >>> There's an upstream change

Re: armel/marvell kernel size

2018-03-22 Thread Roger Shimizu
[ CC tbm ] On Sat, Feb 17, 2018 at 9:57 PM, Bastian Blank wrote: > On Sat, Feb 17, 2018 at 01:48:51PM +0100, Salvatore Bonaccorso wrote: >> Did you had a chance to look at Ben's suggestions or ideas? >> We would like to ideally upload a 4.15.x based version to unstable >> (currently imported 4.15