Bug#914422: linux: Enable network drivers for Huawei D06 server board

2018-11-23 Thread Marcin Juszkiewicz
Package: src:linux Version: 4.18.6-1~bpo9+1 Severity: important Attached patch enables network drivers for Huawei D06 server board. With those changes we are able to run debian installer over the network. I can not add kernel boot messages due to lack of access to machine. -- System Informa

Dolgozói juttatások

2018-11-23 Thread László Péter
Kedves Hölgyem/Uram! 2019 januárjától szinte minden béren kívüli juttatás jövedelemként fog adózni (kivételt képez ez alól a SZÉP kártya). A változások ellenére a vállalatok több mint 55%-a meg kívánja tartani a dolgozói juttatások nettó összegét, magára vállalva ezzel a megemelkedett adóterhek

Bug#914428: src:linux: Enable building of libbpf

2018-11-23 Thread Hilko Bengen
Package: src:linux Severity: normal Control: patch Dear maintainers, it would be nice to have libbpf ship with buster. Some use cases involve optimizations for high performance packet captures in recent Suricata versions and several interesting tracing tools (e.g. bpftrace, ply) that make use of

Processed: Re: Bug#914428: src:linux: Enable building of libbpf

2018-11-23 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tag 914428 patch Bug #914428 [src:linux] src:linux: Enable building of libbpf Added tag(s) patch. > thanks Stopping processing here. Please contact me if you need assistance. -- 914428: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=914428 De

Processed: Re: Bug#914429: nftables: Delete and Flush lead to device or resource busy with segmentation fault

2018-11-23 Thread Debian Bug Tracking System
Processing control commands: > severity -1 normal Bug #914429 [nftables] nftables: Delete and Flush lead to device or resource busy with segmentation fault Ignoring request to change severity of Bug 914429 to the same value. > reassign -1 linux Bug #914429 [nftables] nftables: Delete and Flush le

Bug#914429: marked as done (nftables: Delete and Flush lead to device or resource busy with segmentation fault)

2018-11-23 Thread Debian Bug Tracking System
Your message dated Fri, 23 Nov 2018 11:59:29 +0100 with message-id and subject line Re: Bug#914429: nftables: Delete and Flush lead to device or resource busy with segmentation fault has caused the Debian Bug report #914429, regarding nftables: Delete and Flush lead to device or resource busy wit

Bug#914431: linux-headers-4.18.0-3-common: missing file referred in Makefile

2018-11-23 Thread Raphael Plasson
Package: linux-headers-4.18.0-3-common Version: 4.18.20-1 Severity: normal Dear Maintainer, a module couldn't be compiled by dkms with this specific kernel (for information, it was the wireguard module). The compilation failed indicating that it couldn't find the file "scripts/subarch.include", a

Bug#914429: nftables: Delete and Flush lead to device or resource busy with segmentation fault

2018-11-23 Thread Arturo Borrero Gonzalez
On 11/23/18 1:08 PM, Eike Lohmann wrote: > > Hi Arturo, > > thanks for your quick reply. > > Like described in my example, there is no reference to C_TestChain. > I reproduced your steps, and I had multiple issues because your steps try to delete stuff with external references. If you don't g

Bug#914429: nftables: Delete and Flush lead to device or resource busy with segmentation fault

2018-11-23 Thread Eike Lohmann
Hi Arturo, thanks for your quick reply. Like described in my example, there is no reference to C_TestChain. # nft delete chain filter C_TestChain Error: Could not process rule: Device or resource busy delete chain filter C_TestChain what is left and can we d

Bug#914431: Similar bug previously reported for linux-headers-4.19.0-rc6-amd64

2018-11-23 Thread Plasson Raphaël
I just realized that a similar bug was reported in linux-headers-4.19.0-rc6-amd64, in bug #910348 Raphael

Bug#914429: nftables: Delete and Flush lead to device or resource busy with segmentation fault

2018-11-23 Thread Eike Lohmann
Hi Arturo, we broke it down with less steps, hopefully not confusing. Please try this: table ip filter {     chain FORWARD {         type filter hook forward priority 0; policy accept;         jump vpn_master     }     map J_TestMap {         type ipv4_addr : verdict         flags interval   

Bug#911121: Please compile with CONFIG_SND_BCM2835=m

2018-11-23 Thread Ben Hutchings
On Thu, 2018-11-22 at 23:49 +0100, Santiago Garcia Mantinan wrote: > Hi! > > > I don't have an rpi3 to test, but I wonder if it is really > > necessary to > > enable CONFIG_SND_BCM2835 to get sound. > > After our talk on irc I thought you had commited this change, but a > new version of the kerne

Processed: limit source to linux, reassign 910348 to src:linux, reassign 914431 to src:linux ..., closing 910348

2018-11-23 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > limit source linux Limiting to bugs with field 'source' containing at least one of 'linux' Limit currently set to 'source':'linux' > reassign 910348 src:linux 4.19~rc6-1~exp1 Bug #910348 {Done: Ben Hutchings } [linux-kbuild-4.19] linux-headers-4

Bug#913880: ITP: overlay-userns -- Overlay mounting in user namespaces (DKMS)

2018-11-23 Thread Nicolas Schier
> > > Why don't you talk to the kernel team about adding a module > > > parameter > > > enable this, rather than packaging a fragile hack? > > > > thanks for the pointer. Do you think about something like the > > attached patch? Would you recommend a post in debian-kernel@l.d.o > > about it o

Processing of linux_4.18.20-2_source.changes

2018-11-23 Thread Debian FTP Masters
linux_4.18.20-2_source.changes uploaded successfully to localhost along with the files: linux_4.18.20-2.dsc linux_4.18.20-2.debian.tar.xz linux_4.18.20-2_source.buildinfo Greetings, Your Debian queue daemon (running on host usper.debian.org)

Bug#914431: marked as done (linux-headers-4.18.0-3-common: missing file referred in Makefile)

2018-11-23 Thread Debian Bug Tracking System
Your message dated Fri, 23 Nov 2018 19:50:49 + with message-id and subject line Bug#910348: fixed in linux 4.18.20-2 has caused the Debian Bug report #910348, regarding linux-headers-4.18.0-3-common: missing file referred in Makefile to be marked as done. This means that you claim that the pr

Bug#910348: marked as done (linux-headers-4.19.0-rc6-amd64: File scripts/subarch.include is missing)

2018-11-23 Thread Debian Bug Tracking System
Your message dated Fri, 23 Nov 2018 19:50:49 + with message-id and subject line Bug#910348: fixed in linux 4.18.20-2 has caused the Debian Bug report #910348, regarding linux-headers-4.19.0-rc6-amd64: File scripts/subarch.include is missing to be marked as done. This means that you claim tha

linux_4.18.20-2_source.changes ACCEPTED into unstable

2018-11-23 Thread Debian FTP Masters
Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Fri, 23 Nov 2018 19:15:55 + Source: linux Binary: linux-source-4.18 linux-support-4.18.0-3 linux-doc-4.18 linux-cpupower libcpupower1 libcpupower-dev usbip hyperv-daemons lockdep liblockdep4.18 liblockdep-dev lin

Bug#914491: linux-image-4.18.0-3-amd64: Please revert the STIBP patch from 4.18.20

2018-11-23 Thread Jon
Package: linux-image-4.18.0-3-amd64 Version: 4.18.20-1 Severity: normal Dear Maintainer, The recently uploaded 4.18.20 kernel package has the STIBP patch in it that has been reverted from the 4.9.140, 4.14.83, and 4.19.4 kernels upstream. There will never been an official revert for 4.18 because

Bug#914495: linux-image-4.18.0-3-amd64: does not boot here

2018-11-23 Thread TS
Package: src:linux Version: 4.18.20-1 Severity: critical Justification: breaks the whole system Dear Maintainers, linux-image-4.18.0-3-amd64 does not boot on this computer. After grub shortly cursor is blinking upper left (when usually the initrd is deflating and systemd starts). After that nothi

linux_4.9.135-1_source.changes ACCEPTED into proposed-updates->stable-new, proposed-updates

2018-11-23 Thread Debian FTP Masters
Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sun, 11 Nov 2018 15:03:44 +0100 Source: linux Binary: linux-source-4.9 linux-support-4.9.0-8 linux-doc-4.9 linux-manual-4.9 linux-kbuild-4.9 linux-cpupower libcpupower1 libcpupower-dev linux-perf-4.9 libusbip-dev usb

Bug#913119: linux-image-4.18.0-2-amd64: Hangs on lvm raid1

2018-11-23 Thread Cesare Leonardi
Bug still present with the new 4.18.0-3-amd64 (4.18.20-1). This morning I've tryed to boot this new kernel version, removing the workaround given by the following kernel parameters: scsi_mod.use_blk_mq=0 dm_mod.use_blk_mq=0 The system showed disk hangs in less than 5 hours, and, as in previous

Bug#913119: linux-image-4.18.0-2-amd64: Hangs on lvm raid1

2018-11-23 Thread Hans van Kranenburg
Hi, On 11/24/18 12:42 AM, Cesare Leonardi wrote: > Bug still present with the new 4.18.0-3-amd64 (4.18.20-1). > > This morning I've tryed to boot this new kernel version, removing the > workaround given by the following kernel parameters: > scsi_mod.use_blk_mq=0 dm_mod.use_blk_mq=0 > > The syste

Bug#913119: linux-image-4.18.0-2-amd64: Hangs on lvm raid1

2018-11-23 Thread Cesare Leonardi
Hi Hans! On Sat, 24 Nov 2018 01:08:56 +0100 Hans van Kranenburg wrote: You didn't share any part of your logging. Can you share a part of dmesg logging that shows Oops in it? Here it is, attached to this message. Previously I didn't attached it because to me it looks substantially the same

Bug#914505: linux: reference to netfilter chain not removed on rule replacement, subsequently system hangs

2018-11-23 Thread Christoph Anton Mitterer
Source: linux Version: 4.18.20-1 Severity: important Tags: upstream Hi. Possibly the following may be also partially iptables (i.e. the userland tool) fault. I'm using fail2ban with some custom usage mode, which is that the hook-rule for fail2ban's change isn't just appended somehwere, but an

Bug#914511: Please enable the "virtio-rng" driver in "cloud" kernels

2018-11-23 Thread Martijn van de Streek
Package: linux-image-cloud-amd64 Version: 4.18+99 The "HW_RANDOM_VIRTIO" configuration setting is not currently enabled in the "cloud" flavour of kernel images. KVM virtual machines set up by virt-manager (and possibly virt-install, I'm not sure) come with a virtual random device like that by def