Bug#917607: udev 240 Makes System Unbootable; rootfs Not Found

2019-01-03 Thread Vincent Lefevre
On 2018-12-29 16:06:38 -0800, Leo L. Schwab wrote: > JPGs attached. The messages appear to be coming from initramfs, > which is trying to locate and mount the rootfs, and failing. Same problem, with the keyboard not working, so that I couldn't do anything here. I reported the bug against th

Bug#917247: udev: Many modules are no longer automatically loaded at boot

2019-01-03 Thread gregor herrmann
On Thu, 03 Jan 2019 00:53:08 +0100, gregor herrmann wrote: > So it looks like the udev upgrade is reponsible for both the modules > and the lvm troubles (although the latter still has to be confirmed > in actual use over time). > > After each boot I saved parts of /var/log away. > Find attached d

Bug#917607: udev 240 Makes System Unbootable; rootfs Not Found

2019-01-03 Thread Leo L. Schwab
On Thu, Jan 03, 2019 at 01:46:19PM +0100, Vincent Lefevre wrote: > Same problem, with the keyboard not working, so that I couldn't do > anything here. I reported the bug against the Linux kernel, because > everything is fine with a 4.18 kernel (which I had fortunately kept, > otherwise I would have

Bug#917247: udev: Many modules are no longer automatically loaded at boot

2019-01-03 Thread Michael Biebl
Hi Gregor Am 03.01.19 um 20:45 schrieb gregor herrmann: > Following the next suggestion in the upstream ticket, I've now added > > udevadm trigger --type=subsystems --action=add > > (on top of the b261494 patch, not sure if this is needed) to the init > script; and lo and behold, all seems t

Bug#917247: udev: Many modules are no longer automatically loaded at boot

2019-01-03 Thread gregor herrmann
On Thu, 03 Jan 2019 20:53:34 +0100, Michael Biebl wrote: > Am 03.01.19 um 20:45 schrieb gregor herrmann: > > Following the next suggestion in the upstream ticket, I've now added > > udevadm trigger --type=subsystems --action=add > Hm, I still think there is some deeper issue which causes all

Bug#917247: udev: Many modules are no longer automatically loaded at boot

2019-01-03 Thread Michael Biebl
Am 03.01.19 um 20:45 schrieb gregor herrmann: > Following the next suggestion in the upstream ticket, I've now added > > udevadm trigger --type=subsystems --action=add > > (on top of the b261494 patch, not sure if this is needed) to the init > script; and lo and behold, all seems to be here

Bug#917607: udev 240 Makes System Unbootable; rootfs Not Found

2019-01-03 Thread Martin
I had the same issues on one of my computers and it behaved exactly as described above: Nor root device found (USB keyboard unusable) update-initramfs destroyed any initrd.img it touched with udev 240-2 a downgrade to 239-8 (the last I could get my hands on quickly) resolved the issue The system

Processed: bug 917247 is not forwarded

2019-01-03 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > notforwarded 917247 Bug #917247 [udev] udev: Many modules are no longer automatically loaded at boot Unset Bug forwarded-to-address > thanks Stopping processing here. Please contact me if you need assistance. -- 917247: https://bugs.debian.org/c

Bug#917247: udev: Many modules are no longer automatically loaded at boot

2019-01-03 Thread Michael Biebl
forcemerge 908796 917247 917185 thanks I'm now convinced this is just another incarnation of https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=908796 Sorry for not thinking about this earlier. The only difference seems to be, that with v240 it has become more likely that this race condition is

Processed: Re: Bug#917247: udev: Many modules are no longer automatically loaded at boot

2019-01-03 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > forcemerge 908796 917247 917185 Bug #908796 [udev] udev (with sysvinit) fails to find devices at boot Bug #917185 [udev] udev 240-1 + sysvinit-core 2.93-1 break input devices + other problems 917185 was not blocked by any bugs. 917185 was not blo

Bug#917247: udev: Many modules are no longer automatically loaded at boot

2019-01-03 Thread gregor herrmann
On Fri, 04 Jan 2019 01:22:49 +0100, Michael Biebl wrote: > I'm now convinced this is just another incarnation of > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=908796 > Sorry for not thinking about this earlier. > > The only difference seems to be, that with v240 it has become more > likely

Bug#917607: udev 240 Makes System Unbootable; rootfs Not Found

2019-01-03 Thread Vincent Lefevre
On 2019-01-03 11:02:42 -0800, Leo L. Schwab wrote: > On Thu, Jan 03, 2019 at 01:46:19PM +0100, Vincent Lefevre wrote: > > Same problem, with the keyboard not working, so that I couldn't do > > anything here. I reported the bug against the Linux kernel, because > > everything is fine with a 4.18 ker

Capital Support | T - 722k

2019-01-03 Thread William - .105
Greetings,We are providing Loan/Investment funds to Companies and Individuals with profitable Business project in any area of specialization at a low interest rate between 3% - 5% annually for a duration of 1 upto 10 years plus a 12 months grace period.Minimum application is 1M USD/EURIf interest

Bug#918190: systemd: timesyncd stopped updating clock file after package update

2019-01-03 Thread Patrick Häcker
Package: systemd Version: 240-2 Severity: normal Dear Maintainer, after updating systemd from 239-15 to 240-2 timesyncd stopped touching /var/lib/private/systemd/timesync/clock any more and its time stamps stay at the time of the package upgrade. Additionally the file is no longer used to update