Processing of linux-signed-amd64_5.3~rc5+1~exp2_source.changes

linux-signed-amd64_5.3~rc5+1~exp2_source.changes uploaded successfully to localhost along with the files: linux-signed-amd64_5.3~rc5+1~exp2.dsc linux-signed-amd64_5.3~rc5+1~exp2.tar.xz Greetings, Your Debian queue daemon (running on host usper.debian.org)

linux_4.19.67-2_source.changes ACCEPTED into proposed-updates->stable-new

Mapping buster to stable. Mapping stable to proposed-updates. Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Wed, 28 Aug 2019 06:20:22 +0200 Source: linux Architecture: source Version: 4.19.67-2 Distribution: buster Urgency: medium Maintainer: Debian Kernel Team

Processing of linux_4.19.67-2_source.changes

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

Re: a bug in genksysms/CONFIG_MODVERSIONS w/ __attribute__((foo))?

Ben Hutchings's on August 28, 2019 1:34 am: > On Tue, 2019-08-27 at 22:42 +1000, Nicholas Piggin wrote: >> Masahiro Yamada's on August 27, 2019 8:49 pm: >> > Hi. >> > >> > On Tue, Aug 27, 2019 at 6:59 PM Nicholas Piggin wrote: >> > > Nick Desaulniers's on August 27, 2019 8:57 am: >> > > > On

Bug#700513: (no subject)

I am Ms.Smadar Barber-Tsadik, I am the Chief Executive Officer with FIRST INTERNATIONAL BANK OF ISRAEL LTD (FIBI). I am getting in touch with you regarding an extremely important and urgent matter. If you would oblige me the opportunity, I shall provide you with details upon your response, please

Re: libbpf distro packaging

On 8/25/19, 11:42 PM, "Jiri Olsa" wrote: > On Fri, Aug 23, 2019 at 04:00:01PM +, Alexei Starovoitov wrote: > > > > Technically we can bump it at any time. > > The goal was to bump it only when new kernel is released > > to capture a collection of new APIs in a given 0.0.X release. > > So

Re: a bug in genksysms/CONFIG_MODVERSIONS w/ __attribute__((foo))?

On Tue, 2019-08-27 at 19:09 +0200, Greg KH wrote: > On Tue, Aug 27, 2019 at 04:34:15PM +0100, Ben Hutchings wrote: > > On Tue, 2019-08-27 at 22:42 +1000, Nicholas Piggin wrote: > > > Masahiro Yamada's on August 27, 2019 8:49 pm: [...] > > > > modversions is ugly, so it would be great if we could

Bug#711135: CLOUD COMPUTING 2020 || Invitation for committee membership || April 26 - 30, 2020 - Nice, France

Invitation: We are in the process of re-inviting the program committee members and inviting new members for CLOUD COMPUTING 2020, The Eleventh International Conference on Cloud Computing, GRIDs, and Virtualization We would greatly appreciate you accept our invitation to join the CLOUD

Re: a bug in genksysms/CONFIG_MODVERSIONS w/ __attribute__((foo))?

On Tue, Aug 27, 2019 at 04:34:15PM +0100, Ben Hutchings wrote: > On Tue, 2019-08-27 at 22:42 +1000, Nicholas Piggin wrote: > > Masahiro Yamada's on August 27, 2019 8:49 pm: > > > Hi. > > > > > > On Tue, Aug 27, 2019 at 6:59 PM Nicholas Piggin wrote: > > > > Nick Desaulniers's on August 27, 2019

Re: a bug in genksysms/CONFIG_MODVERSIONS w/ __attribute__((foo))?

On Tue, 2019-08-27 at 22:42 +1000, Nicholas Piggin wrote: > Masahiro Yamada's on August 27, 2019 8:49 pm: > > Hi. > > > > On Tue, Aug 27, 2019 at 6:59 PM Nicholas Piggin wrote: > > > Nick Desaulniers's on August 27, 2019 8:57 am: > > > > On Mon, Aug 26, 2019 at 2:22 PM Nick Desaulniers > > > >

Re: a bug in genksysms/CONFIG_MODVERSIONS w/ __attribute__((foo))?

Hi. On Tue, Aug 27, 2019 at 6:59 PM Nicholas Piggin wrote: > > Nick Desaulniers's on August 27, 2019 8:57 am: > > On Mon, Aug 26, 2019 at 2:22 PM Nick Desaulniers > > wrote: > >> > >> I'm looking into a linkage failure for one of our device kernels, and > >> it seems that genksyms isn't

Re: a bug in genksysms/CONFIG_MODVERSIONS w/ __attribute__((foo))?

Masahiro Yamada's on August 27, 2019 8:49 pm: > Hi. > > On Tue, Aug 27, 2019 at 6:59 PM Nicholas Piggin wrote: >> >> Nick Desaulniers's on August 27, 2019 8:57 am: >> > On Mon, Aug 26, 2019 at 2:22 PM Nick Desaulniers >> > wrote: >> >> >> >> I'm looking into a linkage failure for one of our

linux-latest_106~bpo10+1_multi.changes is NEW

binary:linux-doc is NEW. binary:linux-headers-4kc-malta is NEW. binary:linux-headers-5kc-malta is NEW. binary:linux-headers-686 is NEW. binary:linux-headers-686-pae is NEW. binary:linux-headers-amd64 is NEW. binary:linux-headers-arm64 is NEW. binary:linux-headers-armmp is NEW.

Processing of linux-latest_106~bpo10+1_multi.changes

linux-latest_106~bpo10+1_multi.changes uploaded successfully to localhost along with the files: linux-latest_106~bpo10+1.dsc linux-latest_106~bpo10+1.tar.xz linux-latest_106~bpo10+1_source.buildinfo linux-doc_5.2+106~bpo10+1_all.deb linux-latest_106~bpo10+1_all.buildinfo

Bug#935894: marked as done (linux: buster-backports version)

Your message dated Tue, 27 Aug 2019 15:31:49 +0100 with message-id <6d2e69e3aac49cfb30c7405bdd3d858201b595e4.ca...@decadent.org.uk> and subject line Re: Bug#935894: linux: buster-backports version has caused the Debian Bug report #935894, regarding linux: buster-backports version to be marked as

linux-latest_106~bpo10+1_source.changes REJECTED

Source-only uploads to NEW are not allowed. binary:linux-doc is NEW. binary:linux-headers-4kc-malta is NEW. binary:linux-headers-5kc-malta is NEW. binary:linux-headers-686 is NEW. binary:linux-headers-686-pae is NEW. binary:linux-headers-amd64 is NEW. binary:linux-headers-arm64 is NEW.

Processing of linux-latest_106~bpo10+1_source.changes

linux-latest_106~bpo10+1_source.changes uploaded successfully to localhost along with the files: linux-latest_106~bpo10+1.dsc linux-latest_106~bpo10+1.tar.xz linux-latest_106~bpo10+1_source.buildinfo Greetings, Your Debian queue daemon (running on host usper.debian.org)

Bug#935894: linux: buster-backports version

Source: linux Severity: wishlist Dear Maintainers, would it be possible to get the bullseye kernel into buster-backports? I would very much appreciate that. Regards, Bastian

linux_5.2.9-2~bpo10+1_multi.changes ACCEPTED into buster-backports, buster-backports

Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sun, 25 Aug 2019 18:28:10 +0100 Binary: linux-doc-5.2 linux-headers-5.2.0-0.bpo.2-common linux-headers-5.2.0-0.bpo.2-common-rt linux-source-5.2 linux-support-5.2.0-0.bpo.2 Source: linux Architecture: all source

Bug#928605: No irq handler for vector

Hi, I'm also getting such messages since the buster upgrade: Message from syslogd@lant at Aug 26 20:05:12 ... kernel:[686221.093605] do_IRQ: 1.52 No irq handler for vector Message from syslogd@lant at Aug 27 01:03:12 ... kernel:[704101.075251] do_IRQ: 1.43 No irq handler for vector --

Bug#935245: Problem found

I found the problem. 5.2.7-1 had # CONFIG_INTEL_IOMMU_DEFAULT_ON is not set 5.2.9-1 had CONFIG_INTEL_IOMMU_DEFAULT_ON=y 5.2.9-2 has # CONFIG_INTEL_IOMMU_DEFAULT_ON is not set CONFIG_INTEL_IOMMU_DEFAULT_ON_INTGPU_OFF=y Only 5.2.7-1 boots on my system. I can successfully boot

Bug#935245: Successful boot of mainline 5.3.0-rc6

I built mainline 5.3.0-rc6 in the following way: $ make distclean $ make localmodconfig $ scripts/config --disable DEBUG_INFO $ make -j5 bindeb-pkg LOCALVERSION=-mainline while running linux-image-5.0.0-trunk-amd64_5.0.2-1~exp1. I was able to successfully boot this kernel. Since my previous

fsck on ext4: "WARN Wrong bounce buffer write length: 1024 != 0"

FYI: "fsck -y" on an external USB drive (USB-C, ext4) gave me a ton of messages : [ 191.261939] xhci_hcd :05:00.0: WARN Wrong bounce buffer write length: 1024 != 0 [ 191.263743] xhci_hcd :05:00.0: WARN Wrong bounce buffer write length: 1024 != 0 [ 191.263788] xhci_hcd :05:00.0: