This no longer reproduces for me with udev 240-4, my sysvsinit systems
are back to the same behavior as 239-9 leading me to believe #917247
is more #917607 than it is #908796.
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
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
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
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
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
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
On Wed, 02 Jan 2019 22:29:17 +0100, Michael Biebl wrote:
> could you provide the complete debug log. What you quoted look like
> excerpts.
> Seems the kernel rate limiting unhelpfully kicked in as well (Jan 1
> 23:57:06 jadzia kernel: [ 392.915694] systemd-udevd: 2084 output lines
> suppressed d
Control: forwarded -1 https://github.com/systemd/systemd/issues/11314
Am 02.01.19 um 23:12 schrieb gregor herrmann:
> Thanks; I guess you mean https://github.com/systemd/systemd/issues/11314
> (which then refers to the pull request)
Urgh, c&p fail. Thanks for the correction.
--
Why is it that
On Wed, 02 Jan 2019 22:42:46 +0100, Michael Biebl wrote:
> Control: forwarded -1 https://github.com/systemd/systemd/pull/11244
>
> I've forwarded this issue upstream.
Thanks; I guess you mean https://github.com/systemd/systemd/issues/11314
(which then refers to the pull request)
> Gregor, Frédé
Control: forwarded -1 https://github.com/systemd/systemd/pull/11244
I've forwarded this issue upstream.
Gregor, Frédéric, maybe it's best if you directly follow-up there, in
case you have a github account.
Regards,
Michael
--
Why is it that all of the instruments seeking intelligent life in the
Hi Gregor,
could you provide the complete debug log. What you quoted look like
excerpts.
Seems the kernel rate limiting unhelpfully kicked in as well (Jan 1
23:57:06 jadzia kernel: [ 392.915694] systemd-udevd: 2084 output lines
suppressed due to ratelimiting), so best disable that [1]
Regards,
On Tue, 01 Jan 2019 16:52:31 +0100, Michael Biebl wrote:
> Am 01.01.19 um 01:40 schrieb gregor herrmann:
> > [0] The initialization problems, with loads of:
> > WARNING: Device /dev/xxx not initialized in udev database even after
> > waiting 1000 microseconds.
>
> Is that the only error mess
Am 01.01.19 um 01:40 schrieb gregor herrmann:
> [0] The initialization problems, with loads of:
> WARNING: Device /dev/xxx not initialized in udev database even after waiting
> 1000 microseconds.
Is that the only error message from udev?
Have you tried running udev with udev debug logging en
On Tue, 01 Jan 2019 01:40:09 +0100, gregor herrmann wrote:
> (And with 240-2 and 2.03.02-1 there are still interaction problems
*cough*
… with udev 240-2 and lvm2 2.03.02-1 …
--
.''`. https://info.comodo.priv.at -- Debian Developer https://www.debian.org
: :' : OpenPGP fingerprint D1E1 316
On Fri, 28 Dec 2018 20:39:46 +0100, Michael Biebl wrote:
> Am 28.12.18 um 20:19 schrieb Jamie Heilman:
> >> Please test if this problem is still reproducible with 240-2
> > still very much a problem with 240-2
> Are you using sysvinit as well?
I got the same today with 240-2 and sysvinit.
(And w
Michael Biebl wrote:
> Am 28.12.18 um 20:19 schrieb Jamie Heilman:
> >> Please test if this problem is still reproducible with 240-2
> >
> > still very much a problem with 240-2
>
> Are you using sysvinit as well?
I am, where I use systemd the problem doesn't seem to reproduce.
Am 28.12.18 um 20:19 schrieb Jamie Heilman:
>> Please test if this problem is still reproducible with 240-2
>
> still very much a problem with 240-2
Are you using sysvinit as well?
--
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?
On Mon, 24 Dec 2018 12:18:09 -0500 =?utf-8?b?RnLDqWTDqXJpYyBCcmnDqHJl?=
wrote:
> Package: udev
> Version: 240-1
> Severity: important
>
> After upgrading to 240-1 and rebooting, many modules (about ⅓ of them)
> were no longer automatically loaded at boot, causing many problems as
> you can imagin
19 matches
Mail list logo
