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

Hi, On 11/24/18 2:19 AM, Cesare Leonardi wrote: > > 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 attac

Bug#914526: linux-image-4.18.0-0.bpo.1-amd64: Invalidating filesystems can corrupt dentry table leading to busy loop in kernel.

Package: src:linux Version: 4.18.6-1~bpo9+1 Severity: important Tags: upstream patch Please see https://git.kernel.org/pub/scm/linux/kernel/git/ebiederm/user-namespace.git/commit/?h=for-linus - invalidating filesystems can cause dentry table corruption leading to busy loop in kernel. Easily tri

Processed: your mail

Processing commands for cont...@bugs.debian.org: > block 910607 by 914526 Bug #910607 [src:zfs-linux] zfs-linux: 'zfs receive' can apparently corrupt system mount table. 910607 was not blocked by any bugs. 910607 was not blocking any bugs. Added blocking bug(s) of 910607: 914526 > End of message,

Bug#914526: marked as done (linux-image-4.18.0-0.bpo.1-amd64: Invalidating filesystems can corrupt dentry table leading to busy loop in kernel.)

Your message dated Sat, 24 Nov 2018 18:23:11 + with message-id and subject line Re: Bug#914526: linux-image-4.18.0-0.bpo.1-amd64: Invalidating filesystems can corrupt dentry table leading to busy loop in kernel. has caused the Debian Bug report #914526, regarding linux-image-4.18.0-0.bpo.1-am

Re: linux: enable CONFIG_CRYPTO_MORUS* and CONFIG_CRYPTO_AEGIS*

Hey. Just wondered if a maintainer could possibly tell me whether this could happen anytime soon? It's no big problem for me if not, I'd just want to avoid compiling the whole kernel on my system (which is not the fastest one ^^) if you'd enable it anyway on the next version or so. Cheers, Chri

Bug#914556: linux: FTBFS on arm64: changed ABI

Source: linux Version: 4.9.135-1 Severity: serious Justification: FTBFS Control: affects -1 release.debian.org For tracking the issue: 4.9.135-1 FTBFS on arm64 due to changed ABI: https://buildd.debian.org/status/fetch.php?pkg=linux&arch=arm64&ver=4.9.135-1&stamp=1543036173&raw=0 Relevant part:

Processed: linux: FTBFS on arm64: changed ABI

Processing control commands: > affects -1 release.debian.org Bug #914556 [src:linux] linux: FTBFS on arm64: changed ABI Added indication that 914556 affects release.debian.org -- 914556: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=914556 Debian Bug Tracking System Contact ow...@bugs.debian

Bug#823485: kernel: brcmsmac bcma0:1: START: tid 1 is not agg'able

I'm seeing the same thing on a MacBookAir5,2 device with this hardware: 02:00.0 Network controller [0280]: Broadcom Limited BCM43224 802.11a/b/g/n [14e4:4353] (rev 01) Subsystem: Apple Inc. AirPort Extreme [106b:00e9] Flags: bus master, fast devsel, latency 0, IRQ 17 Memory