debian's initrd should support ntfs

2020-08-18 Thread 陈添来
Thank you. I am chen,a Chinese. "findiso=/a.iso" is I writed,just to test live-boot how to do when a.iso is not existing, sorry. You are not a part of debian,but are you part of live-boot packages?live-boot's function 'is_supported_fs' should add one statement,'if test "$fstype" = "ntfs" -a -e

Bug#964494: Info received (Bug#964494: File system corruption with ext3 + kernel-4.19.0-9-amd64)

2020-08-18 Thread Sarah Newman
We haven't had any further reports of file system corruption. I would guess that converting to EXT4 is sufficient to avoid the issue.

Bug#964263: marked as done (linux-image-5.7.0-1-amd64: Switching from a graphical VT to a non-graphical one freezes display)

2020-08-18 Thread Debian Bug Tracking System
Your message dated Wed, 19 Aug 2020 00:40:22 -0400 with message-id <87mu2r9rk9@posteo.net> and subject line Re: Bug#964263: linux-image-5.7.0-1-amd64: Switching from a graphical VT to a non-graphical one freezes display has caused the Debian Bug report #964263, regarding

Bug#968625: Kernel null pointer deref in the TCP stack

2020-08-18 Thread Raleigh
Package: src:linux Version: 4.19.132-1 Severity: normal My server's kernel randomly panics (maybe once a day?). I didn't experience this issue on the 4.19.0-9 kernel. The network card I'm using is HP NC364T (based on the 82571EB chip, e1000e module). There's also an integrated Intel I217-LM on

Bug#964181: linux-image-4.19.0-9-amd64: Unable to get battery status

2020-08-18 Thread Tino Schmidt
Thank you Bernhard, your comment was quite useful. As mentioned in https://bugs.debian.org/873038 and https://bugs.debian.org/927163 a few changes were necessary to fix this issue: diff --git a/config-4.19.0-10-amd64 b/config-4.19.0-10-amd64 index

Bug#968623: src:linux: buster fails to boot successfully on AWS arm64 bare-metal instances

2020-08-18 Thread Noah Meyerhans
Control: tags -1 + patch MR available at https://salsa.debian.org/kernel-team/linux/-/merge_requests/263

Processed: src:linux: buster fails to boot successfully on AWS arm64 bare-metal instances

2020-08-18 Thread Debian Bug Tracking System
Processing control commands: > tags -1 + patch Bug #968623 [src:linux] src:linux: buster fails to boot successfully on AWS arm64 bare-metal instances Added tag(s) patch. -- 968623: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=968623 Debian Bug Tracking System Contact ow...@bugs.debian.org

Processed: block 968616 with 968623

2020-08-18 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > block 968616 with 968623 Bug #968616 [cloud.debian.org] cloud.debian.org: buster AMIs fail to boot on AWS arm64 bare-metal instances 968616 was not blocked by any bugs. 968616 was not blocking any bugs. Added blocking bug(s) of 968616: 968623 >

Bug#968623: src:linux: buster fails to boot successfully on AWS arm64 bare-metal instances

2020-08-18 Thread Noah Meyerhans
Package: src:linux Version: 4.19.132-1 Severity: important Tags: buster Buster fails to fully initialize the hardware on AWS arm64 bare-metal instances (e.g. m6g.metal). The issue is fixed with the patch series from

Bug#968509: linux-image-4.19.0-10-amd64: System hangs within a few minutes of booting

2020-08-18 Thread Kári Hreinsson
I am experiencing a similar issue though the system usually lives a few hours. Upgrading from 4.19.0-9 to 4.19.0-10 lead to the system randomly becoming completely unresponsive, with this happening between several minutes until several hours from boot time. Choosing 4.19.0-9 at boot time