<div dir="ltr"><div class="gmail_default" style="font-family:monospace,monospace"><div class="gmail_default" style="font-family:monospace,monospace">Michael,<br><br></div><div class="gmail_default" style="font-family:monospace,monospace">I grabbed<br><br><a href="https://people.debian.org/%7Ebiebl/udev/test0/libudev1_215-17+deb8u2%7Etest0_amd64.deb" target="_blank">https://people.debian.org/~biebl/udev/test0/libudev1_215-17+deb8u2~test0_amd64.deb</a><br><a href="https://people.debian.org/%7Ebiebl/udev/test0/udev_215-17+deb8u2%7Etest0_amd64.deb" target="_blank">https://people.debian.org/~biebl/udev/test0/udev_215-17+deb8u2~test0_amd64.deb</a><br><br><a href="https://people.debian.org/%7Ebiebl/udev/test1/libudev1_215-17+deb8u2%7Etest1_amd64.deb" target="_blank">https://people.debian.org/~biebl/udev/test1/libudev1_215-17+deb8u2~test1_amd64.deb</a><br><a href="https://people.debian.org/%7Ebiebl/udev/test1/udev_215-17+deb8u2%7Etest1_amd64.deb" target="_blank">https://people.debian.org/~biebl/udev/test1/udev_215-17+deb8u2~test1_amd64.deb</a><br><br></div><div class="gmail_default" style="font-family:monospace,monospace">I presume you want me to test these testN pairs independently -- as there are TWO candidate fixes we're testing?<br><br></div><div class="gmail_default" style="font-family:monospace,monospace">I'll start with the 'test1' pair first then.<br><br>........<br><br></div><div class="gmail_default" style="font-family:monospace,monospace">Sorry
this took so long. we'd been debugging and broke out the SAS 6i/R
setup to do two standalone disks with MD RAID in an attempt to see if
the controller would respond sooner if it wasn't HW RAID-1, so i had to
put the system back together. Due to lots of issues, this took a lot
longer.<br><br></div><div class="gmail_default" style="font-family:monospace,monospace">I
discovered, that our FAI server, which i thought was not using
systemd-udevd, is in fact using that. But, it is a hit/miss whether the
system hits the bug or not, leading to an occasional window where the
system can get installed (booting the installed OS is always a no-go,
however, so something in the FAI environment is giving us a slight
edge). Also, i had to fight with residual turds from the MD RAID
install borking my FAI install -- blowing away all the partitions,
'wipefs', etc weren't working, anyway.... that's all over<br><br></div><div class="gmail_default" style="font-family:monospace,monospace">So in the fai install at the final block before reboot to installed-OS, i did:<br><br>------------------------------------------------------------------------- <br>root@hammett:/tmp/fai# chroot /target<br># cd /root<br># ls<br>hammett-jessie-fai.dpkg README.FAI sfdisk.out tmp udev-fixes<br># cd udev-fixes <br># ls<br>getit test0 test1<br># cd test1<br># ls<br>libudev1_215-17+deb8u2~test1_amd64.deb udev_215-17+deb8u2~test1_amd64.deb X Y<br># dpkg -i libudev1_215-17+deb8u2~test1_amd64.deb udev_215-17+deb8u2~test1_amd64.deb<br>(Reading database ... 251068 files and directories currently installed.)<br>Preparing to unpack libudev1_215-17+deb8u2~test1_amd64.deb ...<br>Unpacking libudev1:amd64 (215-17+deb8u2~test1) over (215-17+deb8u1) ...<br>Preparing to unpack udev_215-17+deb8u2~test1_amd64.deb ...<br>Unpacking udev (215-17+deb8u2~test1) over (215-17+deb8u1) ...<br>Setting up libudev1:amd64 (215-17+deb8u2~test1) ...<br>Setting up udev (215-17+deb8u2~test1) ...<br>A chroot environment has been detected, udev not started.<br>A chroot environment has been detected, udev not started.<br>update-initramfs: deferring update (trigger activated)<br>Processing triggers for systemd (215-17+deb8u1) ...<br>Processing triggers for man-db (2.7.0.2-5) ...<br>Processing triggers for libc-bin (2.19-18) ...<br>Processing triggers for initramfs-tools (0.120) ...<br>update-initramfs: Generating /boot/initrd.img-3.16.0-4-amd64<br>------------------------------------------------------------------------- <br><br></div><div class="gmail_default" style="font-family:monospace,monospace">The system DOES boot successfully, after a long pause (as expected)...<br></div><div class="gmail_default" style="font-family:monospace,monospace">but
it DOES boot. I am going to reboot a few more times with this setup
(test1) to make sure it's consistent, and then try installing the
'test0' pair of .debs <br>and get back to you, but i wanted to confirm that at least on initial glance, the 'test1' .debs solve my problem.<br><br></div><div class="gmail_default" style="font-family:monospace,monospace">--stephen<br></div><div class="gmail_default" style="font-family:monospace,monospace"><br></div><div class="gmail_default" style="font-family:monospace,monospace"><br></div><div class="gmail_extra"><br><div class="gmail_quote">On Fri, Aug 28, 2015 at 2:26 PM, Michael Biebl <span dir="ltr"><<a href="mailto:biebl@debian.org" target="_blank">biebl@debian.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><span>Am 28.08.2015 um 21:41 schrieb Stephen Dowdy:<br>
> I've not built debian source package stuff before, and wasn't quickly able<br>
> to determine how to even do it on the systemd-215 download,<br>
> so prebuilt packages for amd64 would help greatly.<br>
><br>
> I'm also not entirely sure if this is happening in the initrd level or in<br>
> the /lib/systemd/systemd-udevd, so can i simply extract the<br>
> 'systemd-udevd' from your package and drop onto the target disk directory,<br>
> or should i 'dpkg -i' on it from the chroot of my FAI install before<br>
> reboot, or do i need to run a mkinitramfs or<br>
> some other higher-level debian initrd rebuild binary? Just let me know<br>
> what i need to do to if it involves something more complex than either a<br>
> pgk->disk extraction or 'dpkg -i'<br>
<br>
</span>I've uploaded test packages to <a href="https://people.debian.org/%7Ebiebl/udev/" rel="noreferrer" target="_blank">https://people.debian.org/~biebl/udev/</a><br>
The one in the test0 folder have the patch for udev-event.c, the on in<br>
test1 have the patch for udevd.c<br>
<br>
Download the udev and libudev1 deb and install them via dpkg -i.<br>
<br>
Please let me know, if the test0 or test1 package works.<br>
<br>
Simply installing the packages via dpkg will be enough for having the<br>
initrd regenerated.<br>
<div><div><br>
<br>
Michael<br>
<br>
<br>
<br>
--<br>
Why is it that all of the instruments seeking intelligent life in the<br>
universe are pointed away from Earth?<br>
<br>
</div></div></blockquote></div><br><br clear="all"><br>-- <br><div>Stephen Dowdy - Systems Administrator - NCAR/RAL<br>303.497.2869 - <a href="mailto:sdowdy@ucar.edu" target="_blank">sdowdy@ucar.edu</a> - <a href="http://www.ral.ucar.edu/%7Esdowdy/" target="_blank">http://www.ral.ucar.edu/~sdowdy/</a><br><br><br></div>
</div></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Fri, Aug 28, 2015 at 2:26 PM, Michael Biebl <span dir="ltr"><<a href="mailto:biebl@debian.org" target="_blank">biebl@debian.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">Am 28.08.2015 um 21:41 schrieb Stephen Dowdy:<br>
> I've not built debian source package stuff before, and wasn't quickly able<br>
> to determine how to even do it on the systemd-215 download,<br>
> so prebuilt packages for amd64 would help greatly.<br>
><br>
> I'm also not entirely sure if this is happening in the initrd level or in<br>
> the /lib/systemd/systemd-udevd, so can i simply extract the<br>
> 'systemd-udevd' from your package and drop onto the target disk directory,<br>
> or should i 'dpkg -i' on it from the chroot of my FAI install before<br>
> reboot, or do i need to run a mkinitramfs or<br>
> some other higher-level debian initrd rebuild binary? Just let me know<br>
> what i need to do to if it involves something more complex than either a<br>
> pgk->disk extraction or 'dpkg -i'<br>
<br>
</span>I've uploaded test packages to <a href="https://people.debian.org/~biebl/udev/" rel="noreferrer" target="_blank">https://people.debian.org/~biebl/udev/</a><br>
The one in the test0 folder have the patch for udev-event.c, the on in<br>
test1 have the patch for udevd.c<br>
<br>
Download the udev and libudev1 deb and install them via dpkg -i.<br>
<br>
Please let me know, if the test0 or test1 package works.<br>
<br>
Simply installing the packages via dpkg will be enough for having the<br>
initrd regenerated.<br>
<div class="HOEnZb"><div class="h5"><br>
<br>
Michael<br>
<br>
<br>
<br>
--<br>
Why is it that all of the instruments seeking intelligent life in the<br>
universe are pointed away from Earth?<br>
<br>
</div></div></blockquote></div><br><br clear="all"><br>-- <br><div class="gmail_signature">Stephen Dowdy - Systems Administrator - NCAR/RAL<br>303.497.2869 - <a href="mailto:sdowdy@ucar.edu" target="_blank">sdowdy@ucar.edu</a> - <a href="http://www.ral.ucar.edu/~sdowdy/" target="_blank">http://www.ral.ucar.edu/~sdowdy/</a><br><br><br></div>
</div>