Bug#931499: [Fwd: Re: initramfs hook scripts which use log_* functions die]

2019-07-08 Thread Ben Hutchings
Forwarded Message From: Guenther Brunthaler To: Ben Hutchings Subject: Re: initramfs hook scripts which use log_* functions die Date: Sun, 7 Jul 2019 19:38:00 +0200 Message-Id: <26898f5b-40b3-d225-03c1-3f4955035...@gmx.net> Am 2019-07-07 um 15:50 schrieb Ben Hutchings: >

Bug#931499: initramfs hook scripts which use log_* functions die

2019-07-08 Thread Ben Hutchings
[Please use "reply to all", to record your messages in the bug reporting system.] On Sun, 2019-07-07 at 19:38 +0200, Guenther Brunthaler wrote: > Am 2019-07-07 um 15:50 schrieb Ben Hutchings: > > > These functions are meant to be used by boot scripts, not by hook > > scripts. > > Thank you,

Processed: tagging 931499

2019-07-08 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tags 931499 - moreinfo Bug #931499 [initramfs-tools-core] initramfs hook scripts which use log_* functions die Removed tag(s) moreinfo. > thanks Stopping processing here. Please contact me if you need assistance. -- 931499:

Processed: submitter 931639

2019-07-08 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > submitter 931639 kinky_neko...@nekoboi.moe Bug #931639 [src:linux] linux-image-4.19.0-5-amd64: Does not boot - stuck at "Loading initial ramdisk" Changed Bug submitter to 'kinky_neko...@nekoboi.moe' from 'QWERTY man '. > thanks Stopping

Processed: severity of 931639 is important

2019-07-08 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > severity 931639 important Bug #931639 [src:linux] linux-image-4.19.0-5-amd64: Does not boot - stuck at "Loading initial ramdisk" Severity set to 'important' from 'critical' > thanks Stopping processing here. Please contact me if you need

Bug#731016: ok

2019-07-08 Thread Johnson Andy
Hea päev, palun, kas mul on sinuga sõna?

Processed: bug 931500 is forwarded to https://lore.kernel.org/lkml/5022bdc4-9f3e-9756-cbca-ada37f88e...@cambridgegreys.com/

2019-07-08 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > forwarded 931500 > https://lore.kernel.org/lkml/5022bdc4-9f3e-9756-cbca-ada37f88e...@cambridgegreys.com/ Bug #931500 [src:linux] linux-image-4.19.0-5-amd64: kernel deadlock with autofs Set Bug forwarded-to-address to

Bug#931644: Buster kernel entropy pool too low on VM boot

2019-07-08 Thread Andy Smith
Hi Michael, On Mon, Jul 08, 2019 at 12:59:29PM -0400, Michael J. Redd wrote: > After upgrading to Debian Buster, Xen PV guests' entropy pool is too > low to start cryptographic services in a timely manner. This results in > 30+ second delays in the startup of services such as SSH. The release

Bug#931644: Buster kernel entropy pool too low on VM boot

2019-07-08 Thread Michael J. Redd
Package: linux-image-4.19.0-5-amd64 Version: 4.19.0-5 Issue: == After upgrading to Debian Buster, Xen PV guests' entropy pool is too low to start cryptographic services in a timely manner. This results in 30+ second delays in the startup of services such as SSH. If I connect to the VM's

Bug#931639: linux-image-4.19.0-5-amd64: Does not boot - stuck at "Loading initial ramdisk"

2019-07-08 Thread Kinky Nekoboi
This is proberly linked to this Bug, also coreboot used as firmware on the affected system: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=930029 So its possible that this only apears in the combination linux 4.19 + coreboot. With earlyprintk= VALUE as bootparameter you can get more output

Bug#931639: linux-image-4.19.0-5-amd64: Does not boot - stuck at "Loading initial ramdisk"

2019-07-08 Thread QWERTY man
Package: src:linux Version: 4.19.37-5 Severity: critical Justification: breaks the whole system Dear Maintainer, * What led up to the situation? Upgraded from a very stable and largely vanilla Debian Stretch to Debian Buster. * What exactly did you do (or not do) that was effective

Bug#931500:

2019-07-08 Thread Anton Ivanov
Same picture with different NFS minor versions - 4.0, 4.1 Same picture with and without hyperthreading Same picture with and without different mitigations on/off via kernel command line. 100% reproducible within 4-5 repeats of make -j `cat /proc/cpuinfo | grep processor | wc -l` ; make

Bug#931500: Acknowledgement (linux-image-4.19.0-5-amd64: kernel deadlock with autofs)

2019-07-08 Thread Anton Ivanov
The most interesting part - it is always the same file. ls -laF /var/autofs/local/src/openwrt/build_dir/target-mips_24kc_musl/linux-ar71xx_tiny/linux-4.14.125/arch/mips/include/generated/uapi/asm/ipcbuf.h It becomes invisible from the client, but exists in the server. Usually takes ~4-5

Bug#931500: Acknowledgement (linux-image-4.19.0-5-amd64: kernel deadlock with autofs)

2019-07-08 Thread Anton Ivanov
There are clearly some issues with nfs across an autofs mount (maybe for hard mounts as well), so this may warrant an upgrade. Example test.  Run make -j 12 ; make clean in a loop on an nfs mounted openwrt tree until it fails (usually 2-3 iterations). State on the client ls -laF

Bug#931500: Acknowledgement (linux-image-4.19.0-5-amd64: kernel deadlock with autofs)

2019-07-08 Thread Anton Ivanov
On 08/07/2019 11:59, Anton Ivanov wrote: There are clearly some issues with nfs across an autofs mount (maybe for hard mounts as well), so this may warrant an upgrade. Example test.  Run make -j 12 ; make clean in a loop on an nfs mounted openwrt tree until it fails (usually 2-3

Re: READY! Tomas Ukkonen: Genocide. SOS.

2019-07-08 Thread Tomas Ukkonen
Hi Someone seemed to have modified the previous email I send to you. The sentence should have been "Title seem to have lost full  lenght." Fix the title as soon as possible. Tomas Erno Ukkonen, M. Sc.Sent from ProtonMail, encrypted email. ‐‐‐ Original Message ‐‐‐ On Saturday, 6th

Bug#922234:

2019-07-08 Thread ouafnico
Hi, Got the same bug on 4.9.0-9 running on a DELL T630 server. After removing firmware-misc-nonfree and update initramfs, it's booting fine. 4.9.0-8 was not working too. I had to get back to 4.9.0-4 (didn't have other versions).