** Changed in: debian-installer (Ubuntu Zesty)
Status: In Progress => Won't Fix
** Changed in: debian-installer (Ubuntu Trusty)
Status: In Progress => Won't Fix
** Changed in: debian-installer-utils (Ubuntu Trusty)
Status: In Progress => Won't Fix
--
You received this bug n
xenial debian-installer has been rebuilt and archive.ubuntu.com updated
2018-01-02 and includes this fix:
http://archive.ubuntu.com/ubuntu/dists/xenial-updates/main/installer-amd64/20101020ubuntu451.18/
** Changed in: debian-installer (Ubuntu Xenial)
Status: New => Fix Released
--
You re
This bug was fixed in the package debian-installer-utils -
1.113ubuntu1.16.04.1
---
debian-installer-utils (1.113ubuntu1.16.04.1) xenial; urgency=medium
* Make sure udevd internal state is up-to-date before calling trigger &
settle. This insures that newly anna-installed udev ru
> But, specifically about this bug and trusty, are there actual users who are
> encountering this
> bug on trusty?
No, the user who reported this does not encounter it with trusty, but
that of course doesn't mean it does not exist there.
I am not able to reproduce it on my nvme systems with any
This bug was fixed in the package debian-installer-utils -
1.113ubuntu1.17.04.1
---
debian-installer-utils (1.113ubuntu1.17.04.1) zesty; urgency=medium
* Make sure udevd internal state is up-to-date before calling trigger &
settle. This insures that newly anna-installed udev rul
Dan, I'm not talking about hypothetical users who hypothetically are
encountering any bugs. Of course, we fix all the things.
But, specifically about this bug and trusty, are there actual users who
are encountering this bug on trusty?
Specifically, since the hardware in question was released afte
reporter noted xenial fixed initrd also works.
** Tags removed: verification-needed-xenial
** Tags added: verification-done-xenial
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscr
in zesty lxd container built initrd without -proposed di-utils and
initrd with -proposed di-utils:
ubuntu@build-zesty:~/debian-installer-20101020ubuntu504/build$ make
USE_UDEBS_FROM_EXTRA="zesty-security zesty-updates" build_netboot
...
ubuntu@build-zesty:~/debian-installer-20101020ubuntu504/buil
Hello Dan, or anyone else affected,
Accepted debian-installer-utils into zesty-proposed. The package will
build now and be available at https://launchpad.net/ubuntu/+source
/debian-installer-utils/1.113ubuntu1.17.04.1 in a few hours, and then in
the -proposed repository.
Please help us by testing
To clarify - if we don't SRU this, what do we tell Ubuntu users
(including Canonical customers) who are encountering this problem on
trusty, xenial, or zesty? Sorry, we aren't fixing this, you can't use
your automated preseed install. Or, sorry, you'll have to upgrade to
artful, or wait for the n
> What is the rationale behind requesting a fix for trusty? How do you expect
> it to get onto
> an .iso? A customized iso?
Customers use the initrd provided in our archive, not just isos, e.g.:
http://archive.ubuntu.com/ubuntu/dists/trusty-updates/main/installer-
amd64/current/images/netboot/ub
Whilst we can upload fixes for zesty and trusty; neither of those will
have a point release anymore to include a fix for this.
What is the rationale behind requesting a fix for trusty? How do you
expect it to get onto an .iso? A customized iso?
** Changed in: debian-installer-utils (Ubuntu Zesty)
** Changed in: systemd (Ubuntu Artful)
Status: New => Won't Fix
** Description changed:
[Impact]
udev's rules use a built-in 'kmod' instead of the system
modprobe/insmod, and this built-in kmod only validates/refreshes its
kmod 'context' every 3 seconds (or longer) during event
** Also affects: debian-installer (Ubuntu Artful)
Importance: Undecided
Status: New
** Also affects: debian-installer-utils (Ubuntu Artful)
Importance: Undecided
Status: New
** Also affects: systemd (Ubuntu Artful)
Importance: Undecided
Status: New
** Also affects:
** Tags added: sts-sponsor-ddstreet
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1714505
Title:
systemd kmod builtin uses out of date kmod context
To manage notifications about this bug go to:
htt
** Changed in: debian-installer (Ubuntu)
Milestone: None => ubuntu-17.10
** Changed in: debian-installer (Ubuntu)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/
** No longer affects: debian-installer (Ubuntu Artful)
** No longer affects: debian-installer (Ubuntu Zesty)
** No longer affects: debian-installer (Ubuntu Xenial)
** No longer affects: debian-installer (Ubuntu Trusty)
** Also affects: debian-installer (Ubuntu Trusty)
Importance: Undecided
This bug was fixed in the package debian-installer-utils - 1.113ubuntu2
---
debian-installer-utils (1.113ubuntu2) artful; urgency=medium
* Make sure udevd internal state is up-to-date before calling trigger &
settle. This insures that newly anna-installed udev rules and kernel
** Changed in: debian-installer-utils (Ubuntu)
Status: Confirmed => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1714505
Title:
systemd kmod builtin uses out of date kmod context
To man
** Changed in: debian-installer-utils (Ubuntu)
Status: New => Confirmed
** Changed in: debian-installer-utils (Ubuntu)
Milestone: None => ubuntu-17.09
** Changed in: debian-installer-utils (Ubuntu)
Assignee: (unassigned) => Dimitri John Ledkov (xnox)
** Changed in: debian-install
@xnox, the person that reported this to me and who can reproduce it,
tested with a initrd including your update-dev patch and it does fix the
problem. Can you go ahead and merge it and SRU please?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
Also, this upstream udev bug has caused trouble before, e.g.:
https://bugs.launchpad.net/ubuntu/+source/hw-detect/+bug/1549456
that does a udev reload too, but only when specific devices are found.
Hopefully this change to update-dev will cover more cases where this
upstream udev bug will cause fa
> Here is a sample patch against debian-installer-utils to try.
yes i think it at least needs to go here, to handle this very specific
case. It may be better to put it into the if $TRIGGER section, as I
don't think it is needed for only the settle case, but either way should
work.
This was repor
> Changed in systemd:
> status: New → Fix Released
for clarification, this is not Fix Released upstream, it has been
rejected as Won't Fix upstream, systemd/udev believes it isn't their
problem.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscri
** Tags added: patch
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1714505
Title:
systemd kmod builtin uses out of date kmod context
To manage notifications about this bug go to:
https://bugs.launc
Here is a sample patch against debian-installer-utils to try.
Do you need a d-i build for testing? If yes, for which release(s)?
** Patch added: "lp1714505.patch"
https://bugs.launchpad.net/ubuntu/+source/debian-installer-utils/+bug/1714505/+attachment/4951445/+files/lp1714505.patch
--
You
I think we should fix .udeb installation and the d-i to call `udevadm
control --reload` after .udeb installation and before (re-)triggering
udev.
** Also affects: debian-installer (Ubuntu)
Importance: Undecided
Status: New
** Changed in: systemd (Ubuntu Artful)
Status: In Progres
** Changed in: systemd
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1714505
Title:
systemd kmod builtin uses out of date kmod context
To manage notifications abo
opened upstream merge request 6814:
https://github.com/systemd/systemd/pull/6814
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1714505
Title:
systemd kmod builtin uses out of date kmod context
To m
** Changed in: systemd (Ubuntu Zesty)
Assignee: (unassigned) => Dan Streetman (ddstreet)
** Changed in: systemd (Ubuntu Xenial)
Assignee: (unassigned) => Dan Streetman (ddstreet)
** Changed in: systemd (Ubuntu Trusty)
Assignee: (unassigned) => Dan Streetman (ddstreet)
** Changed i
** Also affects: systemd (Ubuntu Artful)
Importance: Medium
Assignee: Dan Streetman (ddstreet)
Status: In Progress
** Also affects: systemd (Ubuntu Trusty)
Importance: Undecided
Status: New
** Also affects: systemd (Ubuntu Xenial)
Importance: Undecided
Status: N
** Changed in: systemd
Status: Unknown => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1714505
Title:
systemd kmod builtin uses out of date kmod context
To manage notifications about th
yep, having up to 3 seconds worth of stale system data is too much time.
Also, I think the builtins can just validate themselves - for example
the kmod builtin can trivially call kmod_validate_resource(ctx) every
time it's asked to load a module, and I think the other builtins that
implement .valid
I guess this is related to the fact that udevd main loop re-reads
configs at most every 3 seconds. I find that 3 seconds is a really long
time these days.
I wonder if the 3s timeout around manager_reload(manager) should be
removed in udevd.
--
You received this bug notification because you are a
** Also affects: systemd via
https://github.com/systemd/systemd/issues/6723
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1714505
Title:
systemd kmod
slight update to test script, add a check to make sure the nvme module
was unloaded - if any nvme partitions are mounted it would cause a false
positive result.
#!/bin/bash
MOD_DIR=/lib/modules/$( uname -r )/kernel/drivers/nvme/host
modprobe -rq nvme
mv $MOD_DIR/nvme.ko .
depmod -a
sleep 3
udevadm
grr, please note line wrap in above comment; script should be:
#!/bin/bash
MOD_DIR=/lib/modules/$( uname -r )/kernel/drivers/nvme/host
modprobe -rq nvme
mv $MOD_DIR/nvme.ko .
depmod -a
sleep 3
udevadm trigger
sleep 1
mv nvme.ko $MOD_DIR/
depmod -a
grep -q nvme /proc/partitions \
&& echo FAIL nvm
note that the test script in the description must be run as root on a
system that does have a nvme drive that isn't in use (because the nvme
module can't be removed if any nvme drive is in use).
** Bug watch added: github.com/systemd/systemd/issues #6723
https://github.com/systemd/systemd/issu
https://github.com/systemd/systemd/issues/6723
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1714505
Title:
systemd kmod builtin uses out of date kmod context
To manage notifications about this bug
39 matches
Mail list logo
