Bug#883365: Kernel panic when rebooting a machine with a Intel XL710

Package: src:linux Version: 4.9.30-2+deb9u5 Severity: important Dear Maintainer, * What led up to the situation? Rebooting a machine with a Intel XL710, 100% reproducible. I connected a serial console to capture the panic. -- Package-specific info: ** Kernel log: # modinfo i40e

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

Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sat, 02 Dec 2017 15:53:59 + Source: linux Binary: linux-source-4.9 linux-support-4.9.0-4 linux-doc-4.9 linux-manual-4.9 linux-kbuild-4.9 linux-cpupower libcpupower1 libcpupower-dev linux-perf-4.9 libusbip-dev

Bug#881830: marked as done (linux: cherry-pick "security/keys: add CONFIG_KEYS_COMPAT to Kconfig" to stretch kernel)

Your message dated Sun, 03 Dec 2017 01:47:08 + with message-id and subject line Bug#881830: fixed in linux 4.9.65-1 has caused the Debian Bug report #881830, regarding linux: cherry-pick "security/keys: add CONFIG_KEYS_COMPAT to Kconfig" to stretch kernel

Bug#877911: marked as done (Please set CONFIG_BRCMFMAC_SDIO=y for WiFi on the Raspberry Pi 3)

Your message dated Sun, 03 Dec 2017 01:47:08 + with message-id and subject line Bug#877911: fixed in linux 4.9.65-1 has caused the Debian Bug report #877911, regarding Please set CONFIG_BRCMFMAC_SDIO=y for WiFi on the Raspberry Pi 3 to be marked as done.

Bug#867358: marked as done (mips/mipsel: mips-linux-gnu-gccgo-7: waitid: bad address)

Your message dated Sun, 03 Dec 2017 01:47:08 + with message-id and subject line Bug#867358: fixed in linux 4.9.65-1 has caused the Debian Bug report #867358, regarding mips/mipsel: mips-linux-gnu-gccgo-7: waitid: bad address to be marked as done. This

Bug#866185: marked as done (cargo ppc64el segfaults in recent (>June 20) kernels, causing FTBFS for rustc)

Your message dated Sun, 03 Dec 2017 01:47:08 + with message-id and subject line Bug#865416: fixed in linux 4.9.65-1 has caused the Debian Bug report #865416, regarding cargo ppc64el segfaults in recent (>June 20) kernels, causing FTBFS for rustc to be

Bug#865549: marked as done (cargo ppc64el segfaults in recent (>June 20) kernels, causing FTBFS for rustc)

Your message dated Sun, 03 Dec 2017 01:47:08 + with message-id and subject line Bug#865416: fixed in linux 4.9.65-1 has caused the Debian Bug report #865416, regarding cargo ppc64el segfaults in recent (>June 20) kernels, causing FTBFS for rustc to be

Bug#865416: marked as done (cargo ppc64el segfaults in recent (>June 20) kernels, causing FTBFS for rustc)

Your message dated Sun, 03 Dec 2017 01:47:08 + with message-id and subject line Bug#865416: fixed in linux 4.9.65-1 has caused the Debian Bug report #865416, regarding cargo ppc64el segfaults in recent (>June 20) kernels, causing FTBFS for rustc to be

Bug#876458: marked as done (LibreOffice Writer does not launch)

Your message dated Sun, 03 Dec 2017 01:47:08 + with message-id and subject line Bug#865303: fixed in linux 4.9.65-1 has caused the Debian Bug report #865303, regarding LibreOffice Writer does not launch to be marked as done. This means that you claim that

Bug#870070: marked as done (Debian 9.1 stretch: LibreOffice Writer crashes at startup)

Your message dated Sun, 03 Dec 2017 01:47:08 + with message-id and subject line Bug#865303: fixed in linux 4.9.65-1 has caused the Debian Bug report #865303, regarding Debian 9.1 stretch: LibreOffice Writer crashes at startup to be marked as done. This

Bug#869613: marked as done (libreoffice write crashes (Debian 9))

Your message dated Sun, 03 Dec 2017 01:47:08 + with message-id and subject line Bug#865303: fixed in linux 4.9.65-1 has caused the Debian Bug report #865303, regarding libreoffice write crashes (Debian 9) to be marked as done. This means that you claim

Bug#883363: linux-compiler-gcc-7-x86: incorrect GCC version number in package description

Package: linux-compiler-gcc-7-x86 Version: 4.14.2-1 Severity: minor The linux-compiler-gcc-7-x86 package depends on GCC 7 but declares in the description that it depends on GCC 6: Package: linux-compiler-gcc-7-x86 Depends: gcc-7 Description: Compiler for Linux on x86 (meta-package) This package

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

Mapping stretch to stable. Mapping stable to proposed-updates. Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sat, 02 Dec 2017 15:53:59 + Source: linux Binary: linux-source-4.9 linux-support-4.9.0-4 linux-doc-4.9 linux-manual-4.9 linux-kbuild-4.9 linux-cpupower

Processing of linux_4.9.65-1_source.changes

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

Processed: closing 875881

Processing commands for cont...@bugs.debian.org: > close 875881 4.9.30-2+deb9u4 Bug #875881 {Done: Ben Hutchings } [src:linux] linux: CVE-2017-1000251 The source 'linux' and version '4.9.30-2+deb9u4' do not appear to match any binary packages Marked as fixed in versions

Processing of linux_3.16.51-1_multi.changes

linux_3.16.51-1_multi.changes uploaded successfully to localhost along with the files: linux_3.16.51-1.dsc linux_3.16.51.orig.tar.xz linux_3.16.51-1.debian.tar.xz linux-support-3.16.0-4_3.16.51-1_all.deb linux-doc-3.16_3.16.51-1_all.deb linux-manual-3.16_3.16.51-1_all.deb

Re: Disable intel management engine on the latest affected Intel platform

On Fri, 2017-12-01 at 09:26 -0800, piruthiviraj natarajan wrote: > I see that system 76 disables intel management engine for a potential > security breach. > Does Debian has any plans similar to this? > > http://blog.system76.com/post/168050597573/system76-me-firmware-updates-plan That's not

Bug#878165: firmware-iwlwifi: Some firmware versions cause 8260 Bluetooth malfunction

Package: firmware-iwlwifi Version: 20170823-1 Followup-For: Bug #878165 Hi, I can confirm this bug, it's root cause seems to be interference between 2.4GHz wifi and bluetooth. In my case, I have 2 wifi networks in range, one in 5GHz range and the other in 2.4GHz range. My main network is the

Processed: closing 829529

Processing commands for cont...@bugs.debian.org: > close 829529 4.9.25-1 Bug #829529 [src:linux] linux-image-4.6.0-1-amd64: Please enable intel hid module Marked as fixed in versions linux/4.9.25-1. Bug #829529 [src:linux] linux-image-4.6.0-1-amd64: Please enable intel hid module Marked Bug as

Bug#878866: Debian bug #878866 usbip - does mass storage work for you ?

Hi, I have noticed that when I used the suggested port number 4 , I'm getting an oops on mass storage devices. Does mass storage devices work on your setup with usbip (https:// bugs.debian.org/cgi-bin/bugreport.cgi?bug=883345) ?