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 att

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: W

Bug#935862: linux-image-5.2.0-2-amd64: linux kernel 5.2: System halts at or after startup

Package: src:linux Version: 5.2.9-2 Severity: normal Dear Maintainer, * What led up to the situation? Upgrading kernel from v4.19 to v5.2 * What exactly did you do (or not do) that was effective (or ineffective)? apt dist-upgrade * What was the outcome of this action?

Bug with modulo rt2800pci

Package: linux Version: 4.19.37-5 Severity: medium Model hardware: Ralink RT3090 802.11n WiFi Adapter As of version 4.19.67 the problem with this module has been resolved, the module is not a non-free and prevents WiFi from working. The only solution is to add this module to a blacklist and use a

Bug#935853: nouveau.ko: kernel selects nouveau for GE108 GeForce1030 which does not support it

Package: src:linux Version: 4.19.37-5+deb10u2 Severity: important File: nouveau.ko Dear Maintainer, I swapped out a failed graphics card for a NVidia GeForce 1030 GE108; the kernel autodetected the nouveau driver and tried to use it, which it cannot actually do, thus no video at bootup. If I did

Bug#934781: firmware-iwlwifi: iwl4965: Microcode SW error detected

Hi, On Fri, Aug 02, 2019 at 08:50:01PM +0200, Thorsten Glaser wrote: > Package: firmware-iwlwifi > Version: 20190717-1 > Severity: normal > > My WLAN just crashed, no load (an ssh session and some chat). I'm experiencing a similar problem with 8265 and kernel 5.2.7 -- I got the microcode sw erro

linux-latest_105+deb10u1_source.changes ACCEPTED into proposed-updates->stable-new, proposed-updates

Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Mon, 26 Aug 2019 02:16:02 +0100 Source: linux-latest Architecture: source Version: 105+deb10u1 Distribution: buster Urgency: medium Maintainer: Debian Kernel Team Changed-By: Ben Hutchings Changes: linux-latest (105

Bug#935852: linux-image-5.2.0-2-amd64: Heavy static noise on headphone jack snd_hda_intel

Package: src:linux Version: 5.2.9-2 Severity: normal I am experiencing heavy static noise through the headphone jack, while the issue is completely absent when booting with linux-image-4.19.0-5-amd64. When the media stops the static noise persists for a few seconds, I guess until the driver goes i

linux_4.9.189-1_multi.changes ACCEPTED into oldstable-proposed-updates->oldstable-new, oldstable-proposed-updates

Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Thu, 22 Aug 2019 21:50:36 +0100 Binary: linux-doc-4.9 linux-headers-4.9.0-11-common linux-headers-4.9.0-11-common-rt linux-manual-4.9 linux-source-4.9 linux-support-4.9.0-11 Source: linux Architecture: all source Ver

Bug#904385: marked as done (arm64: sigaltstack fails with MINSIGSTKSZ for 32-bit processes)

Your message dated Mon, 26 Aug 2019 17:47:31 + with message-id and subject line Bug#904385: fixed in linux 4.9.189-1 has caused the Debian Bug report #904385, regarding arm64: sigaltstack fails with MINSIGSTKSZ for 32-bit processes to be marked as done. This means that you claim that the prob

Bug#935134: marked as done (wireguard-dkms: kernel module fails to build with latest Stretch linux kernel sources)

Your message dated Mon, 26 Aug 2019 17:47:31 + with message-id and subject line Bug#935134: fixed in linux 4.9.189-1 has caused the Debian Bug report #935134, regarding wireguard-dkms: kernel module fails to build with latest Stretch linux kernel sources to be marked as done. This means that

linux_5.2.9-2~bpo10+1_multi.changes is NEW

binary:acpi-modules-5.2.0-0.bpo.2-686-di is NEW. binary:acpi-modules-5.2.0-0.bpo.2-686-pae-di is NEW. binary:acpi-modules-5.2.0-0.bpo.2-amd64-di is NEW. binary:affs-modules-5.2.0-0.bpo.2-4kc-malta-di is NEW. binary:affs-modules-5.2.0-0.bpo.2-5kc-malta-di is NEW. binary:affs-modules-5.2.0-0.bpo.2-lo

Processed: Re: Bug#935796: linux-image-5.2.0-2-amd64: Kernel 5.2 4.9 hang on reboot or shutdown last Step

Processing control commands: > tag -1 moreinfo Bug #935796 [src:linux] linux-image-5.2.0-2-amd64: Kernel 5.2 4.9 hang on reboot or shutdown last Step Added tag(s) moreinfo. -- 935796: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=935796 Debian Bug Tracking System Contact ow...@bugs.debian.o

Bug#935796: linux-image-5.2.0-2-amd64: Kernel 5.2 4.9 hang on reboot or shutdown last Step

Control: tag -1 moreinfo On Mon, 2019-08-26 at 10:42 +0200, Linuxonlinehelp wrote: > Package: src:linux > Version: 5.2.9-2 > Severity: normal > > Dear Maintainer, > > *** Reporter, please consider answering these questions, where appropriate *** > >* What led up to the situation? >* Wha

Processing of linux_5.2.9-2~bpo10+1_multi.changes

linux_5.2.9-2~bpo10+1_multi.changes uploaded successfully to localhost along with the files: linux_5.2.9-2~bpo10+1.dsc linux_5.2.9-2~bpo10+1.debian.tar.xz linux_5.2.9-2~bpo10+1_source.buildinfo linux-doc-5.2_5.2.9-2~bpo10+1_all.deb linux-headers-5.2.0-0.bpo.2-common-rt_5.2.9-2~bpo10+1_all

Bug#935796: linux-image-5.2.0-2-amd64: Kernel 5.2 4.9 hang on reboot or shutdown last Step

Package: src:linux Version: 5.2.9-2 Severity: normal Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? * What exactly did you do (or not do) that was effective (or ineffective)? * What was the outcome of

Bug#932086: Missing drivers indroduced after Linux 5

A lot of device drivers introduced after Linux 5 is not built in 5.2.9-2, including > # CONFIG_MISC_ALCOR_PCI is not set > # CONFIG_USB_NET_AQC111 is not set I wish much newly introduced drivers could be built along with the new upstream kernel release, or is there any policy preventing these n

Bug#935564: Typo

Hi, This bug was already fixed in the v5.3 and last week I sent a request for it to be applied to v5.2 stable. It should be applied in v5.2.11. We have a bugzilla entry where we tracked this bug: https://bugzilla.kernel.org/show_bug.cgi?id=203315 -- Cheers, Luca.