Bug#790561: After upgrading udev from 215-18 to 220-7 or 221-1, the system is unbootable afterwards

[Klaus Ethgen]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Hi,

uff, I found some time to finally going on with that issue. Sorry for
the delay.

Am Fr den 10. Jul 2015 um 15:59 schrieb Martin Pitt:
> Thanks. So we now need to bisect the change. My gut feeling is that
> it's due to changes in /lib/udev/rules.d/, not in udevd itself.

I did the test now with version 227-2 and after severa reboots I can
rule out that the bug lies in the rules. Even after replacing all rules
I get the large boot delay. (~100 seconds)

But I might have found another problem that definitively lies in the
rules. But this is another issue I guess so focusing on this first.

Just for the records: When I use (all) original rules from 227-2, I
cannot shutdown (reboot) the system a clean way. The system stuck with
"Stopping remaining crypto devices" (something like that, I do not have
the original message). With all rules replaced with the rules from
215-18, that shutdown works well.

As I started first with going backwards one by one with the scripts,
after two reboots I decided to take the other way, keeping udev 227-2
installed but replacing all rules with the version from 215-18 and then
wanted to go forward step by step as other way around it would take ages
to go ahead. But after seeing that the bug also occcure with all rules
replaced, I stopped, so no idea where this new bug is located.

Regards
   Klaus
- -- 
Klaus Ethgen  http://www.ethgen.ch/
pub  4096R/4E20AF1C 2011-05-16   Klaus Ethgen 
Fingerprint: 85D4 CA42 952C 949B 1753  62B3 79D0 B06F 4E20 AF1C
-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQGcBAEBCgAGBQJWPi11AAoJEKZ8CrGAGfasBSsL/A3xzvwj2sxsE72Im+1KVk/E
9OPPhxJqs5VrJmbWIzjA7bRISHAAV6w0wmzvgDelaoCVqtKcB+ugc3UTEDctcc8A
mRLJnalDM2f7U/oo2x17qemescgDM3MUtzkTIqEk74bftE4ttAN1XPV1bJa0KJ2g
zfLq0jV/tf8g3o9wKFan4RQsoUFHBtBxaexWJ8CDe6rUGvIQjjEnrc5cfUQitKr3
lsPkyt8QmGfhHbhwO8HVKZAW17TyR1JyhrmAbbVckwDt7+B4eiQLors7b9XbUE98
fzRXy9QyAlrD/ABMuEeUamFvdS3iiW98AVxJCR0uxRrYzfK5IyjgVNafv7eIuHYe
cDrsSNcOLh2QRIb2hPo53jAC5bQrfPsAnQk/jfrs0NseOXsUCeSDsdLzW3+4YXDk
gVV8qcLKN3cjFD8bEafo+8KuczFMa82dDV7j6keJxmmvAdSDc+VaY8Nzjkzx3SlD
iDOliTxmIv4HLdF698WUYv7Zd0LiDrambmYZ+61kLg==
=kFti
-END PGP SIGNATURE-

Bug#790561: After upgrading udev from 215-18 to 220-7 or 221-1, the system is unbootable afterwards

[Klaus Ethgen]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Hi,

I found a bit time today to try to get into this problem again.

After upgrading to the most recent udev, I tried to redirect stdout and
stderr in init script to /run and booting the machine with debug output.

Unfortunatelly, the files was empty after boot. As I first did it wrong
and had the old init script from udev 215-18 (what does not work with
new udev) I seen that the redirect works but not with version 225-1.

However, I seen that the problem still exists and I seen some strange
messages about event3 or js0 timing out (I have no joystick connected to
my system and never had).

As it might be a case of the input system, could it be that new udev
cannot handle lenovo thinkvantage keyboard with build in trackpoint over
the same USB connection?

The next days, when I have time again, I'll try to replace rules one by
one. But therefor I need much time considering the long boot process.

Regards
   Klaus
- -- 
Klaus Ethgen  http://www.ethgen.ch/
pub  4096R/4E20AF1C 2011-05-16   Klaus Ethgen 
Fingerprint: 85D4 CA42 952C 949B 1753  62B3 79D0 B06F 4E20 AF1C
-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQGcBAEBCgAGBQJV6rWzAAoJEKZ8CrGAGfassO8L/An2Ol0JMo2lUaYrw3lIFCzj
VxtvFoz1/9Z0zzIW27BiOfYvLeF8vgDe2GgZJWLs2gEYl1XeAAemG4bzKyxZPofo
089nUvUND62tdgpZaNzYRaB2Tsfr1V+2A9tLPGA1KrgYetI8i+v+wdU+N3t82fs3
FIqB6SuX1qYqCj/fLDQUXKSTDmdFnM1LNrcg2UwDaL241MpPyKE8PwRvPuvICz6j
OdsKont5M99/Nujh+BGrFgbfTVDLqCsXWVyLhTYzfLkiqWoHMrcMnFESu8LPnORQ
pPpDnZy2p28ff5HZcSLa2WgTHV/HioTwIBuOQmK/LgIW4YvZRuqrhRDVp/sYFNtn
vJiIyrFsBAQiEU1/b5d20tim5u1yZ7tpX1ZIv8jRvg4qh7F757YXunNuSzCjVl+X
pBzHMHkDEfuP9e/DzuL1cQEzQqQ8FBA1yy0tW3QwRCi3YqdGix87MIkr9J4Jgqug
grEy20Zg23nt0nqSKiueel7MXp6ovcQHrKOe7+XfPg==
=lkZ1
-END PGP SIGNATURE-

Bug#790561: After upgrading udev from 215-18 to 220-7 or 221-1, the system is unbootable afterwards

[Michael Biebl]

Control: severity -1 important

(downgrading severity as per your explanations)

Am 10.07.2015 um 16:41 schrieb Klaus Ethgen:
 Hello,
 
 Am Mo den  6. Jul 2015 um 20:26 schrieb Martin Pitt:
 Klaus Ethgen [2015-07-05  1:34 +0100]:
 Well, it clearly shows that it probes some unexisting USB stuff.
 
 It's a shot into the dark, but this makes me wonder if this is another
 fallout of enabling USB auto-suspend? Can you please try and move away
 /lib/udev/rules.d/42-usb-hid-pm.rules (rename it to *.rules.disabled
 or so), reboot, and see if that improves things?
 
 With version 222-1 there is no /lib/udev/rules.d/42-usb-hid-pm.rules
 anymore. However, I gave it a try but the bug is not gone.
 
 After SCSI detection it takes ~100 seconds to finish USB HID detection.
 That is ten times more than with udev 215-18. So the system is not
 unbootable anymore but painful slow booting.

If the system if fully booted (with v222), is the problem reproducible
if you run
$ udevadm trigger
$ udevadm settle

Does the settle call block as well for such a long time?
Have you seen my earlier reply regarding a verbose udev debug log?
Would be great if you can gather this information.

Michael

-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?



signature.asc
Description: OpenPGP digital signature

Bug#790561: After upgrading udev from 215-18 to 220-7 or 221-1, the system is unbootable afterwards

[Michael Biebl]

Am 10.07.2015 um 16:59 schrieb Martin Pitt:
 It's also not completely clear to me whether the hang already
 happens in initramfs or in the real system. In the former case, you
 need to call update-initramfs -u after each step (doing that can't
 hurt either way).

Klaus is using a custom kernel, no initramfs and a split-usr.



-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?



signature.asc
Description: OpenPGP digital signature

Bug#790561: After upgrading udev from 215-18 to 220-7 or 221-1, the system is unbootable afterwards

[Klaus Ethgen]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Hi,

Am Fr den 10. Jul 2015 um 15:59 schrieb Martin Pitt:
 (Assuming that you saved the tarballs in /tmp). Then see whether your
 system boots normally again? If so, the regression is in the rules, if
 not, it's in udevd itself.
 
 If it's in the rules, could you put back the rules from
 /lib/udev/rules.d.orig/ one by one and see when things start going
 haywire?

As I wrote before, I can do this after the weekend. Unfortunately I need
the system up and running and to be honest, I am not sure, if I find
time next week to do it. (I will be not @home for the two weeks
afterwards. So in worst case, it will take 3 weeks until I can do the
tests fully.)

 It's also not completely clear to me whether the hang already
 happens in initramfs or in the real system. In the former case, you
 need to call update-initramfs -u after each step (doing that can't
 hurt either way).

As the system has no initramfs, it is the real system.

Regards
   Klaus
- -- 
Klaus Ethgen  http://www.ethgen.ch/
pub  4096R/4E20AF1C 2011-05-16   Klaus Ethgen kl...@ethgen.de
Fingerprint: 85D4 CA42 952C 949B 1753  62B3 79D0 B06F 4E20 AF1C
-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQGcBAEBCgAGBQJVn99WAAoJEKZ8CrGAGfas0cAL/jNAugEBfKdxD/QeVwgn+Pej
hWjLLjIDbIJTCsHdbGOXgmMOHMV8drAbhRByzPzWt1pxqX+mPIC8W3IPeefIXnSg
dQ9bTmhJdYjuDkBpruee1gxZlPmLaheu3zHjcjBVgovuec/p9ZnfwjGx88ZYfQNz
drumpBKTzBnR5GFlTk/w8aMYo9FJGkijT+qgCc07NKbL3ysBt1ar8QTIRDiArGD0
meZ9A6TSGOmMcn5JliJj6a6IaaQ4+DZCh9CW2QvcFgq9n9yLviClzljEBuYLpKio
hW80/my9wOV5nOtH9pTLG49H7CDwkI/hRoVNPv28ZUiFW/fEqaeFFAR+F1nYIvLM
1M/kXw7n6e7+CPskSrpKFThdbIfMJgjT0PgMLRLWYWilUwwYTTY952SeukzjMASL
CWaY5HRqrb53H+EACzrnkiQTnDFX1O8WAxkwt/wMPMWZNBi6Ecx79/D8a1xxJEYN
C8yX3HVeP6wwnb90lCKxNAzSxftEfp72Z6T9/at9WQ==
=Sb73
-END PGP SIGNATURE-


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#790561: After upgrading udev from 215-18 to 220-7 or 221-1, the system is unbootable afterwards

[Michael Biebl]

Am 10.07.2015 um 17:00 schrieb Klaus Ethgen:
 Am Fr den 10. Jul 2015 um 15:55 schrieb Michael Biebl:
 After SCSI detection it takes ~100 seconds to finish USB HID detection.
 That is ten times more than with udev 215-18. So the system is not
 unbootable anymore but painful slow booting.
 
 If the system if fully booted (with v222), is the problem reproducible
 if you run
 $ udevadm trigger
 $ udevadm settle
 
 I'll give that a try after the weekend. Sorry, the system is somewhat
 needed so I cannot reboot it every time.
 
 Have you seen my earlier reply regarding a verbose udev debug log?
 Would be great if you can gather this information.
 
 Well, I seen sometink hoe to enable debugging in grub commandline.
 Unfortunately there is no way to write that log stuff to a file. The
 only way I could think of would be to take a video from the booting
 process. However, I do not have a video camera so have to ask friends
 who has such one.

Have you seen my reply, regarding setting SYTEMD_LOG_TARGET=console in
/etc/init.d/udev and redirecting the output when starting the udevd
daemon to a file in /run?

That should work
-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?



signature.asc
Description: OpenPGP digital signature

Bug#790561: After upgrading udev from 215-18 to 220-7 or 221-1, the system is unbootable afterwards

[Klaus Ethgen]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Am Fr den 10. Jul 2015 um 16:05 schrieb Michael Biebl:
  Well, I seen sometink hoe to enable debugging in grub commandline.
  Unfortunately there is no way to write that log stuff to a file. The
  only way I could think of would be to take a video from the booting
  process. However, I do not have a video camera so have to ask friends
  who has such one.
 
 Have you seen my reply, regarding setting SYTEMD_LOG_TARGET=console in
 /etc/init.d/udev and redirecting the output when starting the udevd
 daemon to a file in /run?

No, this I missed. I'll see what I can do.

Regards
   Klaus
- -- 
Klaus Ethgen  http://www.ethgen.ch/
pub  4096R/4E20AF1C 2011-05-16   Klaus Ethgen kl...@ethgen.de
Fingerprint: 85D4 CA42 952C 949B 1753  62B3 79D0 B06F 4E20 AF1C
-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQGcBAEBCgAGBQJVn+CiAAoJEKZ8CrGAGfasExgL/Rk8N8gMexEKLJyB//tf8O1d
P14SI/r8lyh3wEscD1MGGLQ9C0W6+HC6LuzNWi7bf3RFYWEBW30y0aJZpD2dryQL
MKbfa6f2ln6mj7YIfx+gqQSTu8AzeU1Mo+1DrgYAgSmKLEu6oQ5P6gg8H+UWkkvG
D9VtyHOAgFd2VZ2+eYGwhw9OIR6HbS9WNuXlhJwtSWtHE6OxXa2S3u5DKvdrpULy
hYoNITBoVB/gcmIKJ8iPWRuymGdq9dYmM7Q3R8DtujjJllWUeNdB2y+iKQInRT7c
fay2Vpit0jSBTKgj9+4QdIUTiU8/uY3HnHaJvMdc3kn7jwM5SvNFLzqKWR1JXT9Z
Q5cxT/ALogItOvrzwhvMcixlm8H0idF0fbW/9q/ST1NG9+I8kfcflIISLoAAtWdr
848g79a1PN52IjU/BsuE0V3s3T3T2aAFCqE71B0KOjkCmbUAHYAlSeeSKn1Dt86T
Dem4Ta11OFx6nw/pg+pWINDwpXt/MTBuBzm5dwQq/g==
=5sYi
-END PGP SIGNATURE-


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#790561: After upgrading udev from 215-18 to 220-7 or 221-1, the system is unbootable afterwards

[Klaus Ethgen]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Hello,

Am Mo den  6. Jul 2015 um 20:26 schrieb Martin Pitt:
 Klaus Ethgen [2015-07-05  1:34 +0100]:
  Well, it clearly shows that it probes some unexisting USB stuff.
 
 It's a shot into the dark, but this makes me wonder if this is another
 fallout of enabling USB auto-suspend? Can you please try and move away
 /lib/udev/rules.d/42-usb-hid-pm.rules (rename it to *.rules.disabled
 or so), reboot, and see if that improves things?

With version 222-1 there is no /lib/udev/rules.d/42-usb-hid-pm.rules
anymore. However, I gave it a try but the bug is not gone.

After SCSI detection it takes ~100 seconds to finish USB HID detection.
That is ten times more than with udev 215-18. So the system is not
unbootable anymore but painful slow booting.

I went back to 215-18 again and the system boots as usually.

Gruß
   Klaus
- -- 
Klaus Ethgen  http://www.ethgen.ch/
pub  4096R/4E20AF1C 2011-05-16   Klaus Ethgen kl...@ethgen.de
Fingerprint: 85D4 CA42 952C 949B 1753  62B3 79D0 B06F 4E20 AF1C
-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQGcBAEBCgAGBQJVn9mYAAoJEKZ8CrGAGfas3mIL/jXZCXxdYJaodpCDTIcltvt3
s0CKxocUJ856SJcsDPVL0UO+4jHkyPJw+IQt5b13tuwTD35K0O03Xyk5BgjNMYVh
sUhXhPSVjVd0YIwhHuKYLpDY7ldN7Vyi1lrBJtKz90mO+yfemtUFuZKv0IItfR3k
S7TnzEzhItjY4Md1be7enkvWe38e6YXxyWDDiMTwGifpW3lmJSrGk6EU/JsKlG3g
8rWmp41mb/eWKe4PntfLIHgWb8E71P9EdmM2DOYhU2e+Ci6nHWPVsUm3d4qS3t0W
M/EMtlpD8TG3EmtNva3rPLiWrxpABaZVKd99zEnxezSxHIQXCAUqDwYo/jzp6lem
j/vkXPJuoxniU8GbF9dW1MeuaAsx2troxTa2IbAzkI8G/kb++nvB2waceyM9SfOZ
fIGRH2snMCx0ZHOc7n0D8QSk68rC8vTMi7u+Kc2l3pi5UdDzqVjQSA9mwtOMdu8f
kaU+4z9j4RLUz9SmEPm6Q8wsjP3qRR06J9a/rblS5Q==
=J0QZ
-END PGP SIGNATURE-


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#790561: After upgrading udev from 215-18 to 220-7 or 221-1, the system is unbootable afterwards

[Martin Pitt]

Hey Klaus,

Klaus Ethgen [2015-07-10 15:41 +0100]:
 With version 222-1 there is no /lib/udev/rules.d/42-usb-hid-pm.rules
 anymore. However, I gave it a try but the bug is not gone.
 
 After SCSI detection it takes ~100 seconds to finish USB HID detection.
 That is ten times more than with udev 215-18. So the system is not
 unbootable anymore but painful slow booting.

Thanks. So we now need to bisect the change. My gut feeling is that
it's due to changes in /lib/udev/rules.d/, not in udevd itself.

I attached all udev rules provided by the udev 215 package (note that
lots of other packages ship stuff in /lib/udev/rules.d/) for
convenience.  As a starter, could you install udev 222, and do

  cp -a /lib/udev/rules.d{,.orig}
  dpkg -L udev|grep lib/udev/rules.d/.*rules|xargs rm
  tar -C /lib/udev/rules.d/ -xf /tmp/rules-215.tar.gz
  update-initramfs -u

(Assuming that you saved the tarballs in /tmp). Then see whether your
system boots normally again? If so, the regression is in the rules, if
not, it's in udevd itself.

If it's in the rules, could you put back the rules from
/lib/udev/rules.d.orig/ one by one and see when things start going
haywire?

It's also not completely clear to me whether the hang already
happens in initramfs or in the real system. In the former case, you
need to call update-initramfs -u after each step (doing that can't
hurt either way).

Thanks!

Martin

-- 
Martin Pitt| http://www.piware.de
Ubuntu Developer (www.ubuntu.com)  | Debian Developer  (www.debian.org)


rules-215.tar.gz
Description: application/gzip


signature.asc
Description: Digital signature

Bug#790561: After upgrading udev from 215-18 to 220-7 or 221-1, the system is unbootable afterwards

[Klaus Ethgen]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Am Fr den 10. Jul 2015 um 15:55 schrieb Michael Biebl:
  After SCSI detection it takes ~100 seconds to finish USB HID detection.
  That is ten times more than with udev 215-18. So the system is not
  unbootable anymore but painful slow booting.
 
 If the system if fully booted (with v222), is the problem reproducible
 if you run
 $ udevadm trigger
 $ udevadm settle

I'll give that a try after the weekend. Sorry, the system is somewhat
needed so I cannot reboot it every time.

 Have you seen my earlier reply regarding a verbose udev debug log?
 Would be great if you can gather this information.

Well, I seen sometink hoe to enable debugging in grub commandline.
Unfortunately there is no way to write that log stuff to a file. The
only way I could think of would be to take a video from the booting
process. However, I do not have a video camera so have to ask friends
who has such one.

Regards
   Klaus
- -- 
Klaus Ethgen  http://www.ethgen.ch/
pub  4096R/4E20AF1C 2011-05-16   Klaus Ethgen kl...@ethgen.de
Fingerprint: 85D4 CA42 952C 949B 1753  62B3 79D0 B06F 4E20 AF1C
-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQGcBAEBCgAGBQJVn94VAAoJEKZ8CrGAGfasoBsL/iFyCw3EoIalTfAppMdO6cNw
NbOyzJGElx35wHJms7jkYVYwkLypQuwS3sib+6OixwZ/O1dJ6wTVK7YEEKFij2CT
MPZX17nbYoQCSz234D8bQuCzwZoYxTpbqMzoI2WO98e4Q7Rf0nlwc49lFrjfkojV
ph5N+KMNpCXxsnF6DCsm3sWhjuc0T75CXC7HAQOnX654uhoWJFDy4GVmkA5e1OsK
Rrl1RMZC/q5C3AlEsn7+BQ+tHc6Stxi6m5xyZK8vcL5q7jimCUtqqjL43OKE4OFc
TVuaRw4wzYHfrzRNHQgeuiJ6tcTuQ8ZR1yumudCplj6IqtO/Q5GLJCNqJxz6AidI
m6FJFvvx0Yz+k9lyD5OLKUXnGwrS2lyUQrlV+57l8BzN6PSr2oMZggD2UzPHwCIq
NwDhVqorRwjqgj9yq77O4gad6uga5HIUmvsnZU3d3mKRntP4D60OHAlc1HRAzt/Q
/AbpPUw+DJGOYDnyxYjKzn1JQpYGVxPXihQtk1ypmg==
=RxNF
-END PGP SIGNATURE-


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#790561: After upgrading udev from 215-18 to 220-7 or 221-1, the system is unbootable afterwards

[Martin Pitt]

Hello Klaus,

Klaus Ethgen [2015-07-05  1:34 +0100]:
 Well, it clearly shows that it probes some unexisting USB stuff.

It's a shot into the dark, but this makes me wonder if this is another
fallout of enabling USB auto-suspend? Can you please try and move away
/lib/udev/rules.d/42-usb-hid-pm.rules (rename it to *.rules.disabled
or so), reboot, and see if that improves things?

Thanks,

Martin
-- 
Martin Pitt| http://www.piware.de
Ubuntu Developer (www.ubuntu.com)  | Debian Developer  (www.debian.org)


signature.asc
Description: Digital signature

Bug#790561: After upgrading udev from 215-18 to 220-7 or 221-1, the system is unbootable afterwards

[Klaus Ethgen]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Am Fr den  3. Jul 2015 um 20:58 schrieb Michael Biebl:
  However, I'll attach you the dmesg from that boot try and a clean dmesg
  from a good udev. In the last one I mark the position where new udev
  breaks. (Note that the order of the messages is completely different
  between the two dmesg outputs.)
  
  Please note also that I get different counts of the following messages with
  every boot:
 usb 2-3.2: device descriptor read/64, error -110
 usb 8-3.2: device descriptor read/64, error -110
 usb 8-3.2: device descriptor read/64, error -110
 usb 8-3.2: device descriptor read/64, error -110
 
 I don't see anything relevant in those logs.

Well, it clearly shows that it probes some unexisting USB stuff.

 I'm a bit confused though: how can you get a dmesg output from a bad
 boot, when the system did not boot?

I already wrote that, from time to time the boot get through after
really long time. That is the only way to fix it. (Ok, I could boot from
a grml boot stick. But the first time it happened, I did not have such a
stick pre-prepared. I did not expect an upgrade of udev breaking the
whole system, that I never had that complete.)

Regards
   Klaus
- -- 
Klaus Ethgen  http://www.ethgen.ch/
pub  4096R/4E20AF1C 2011-05-16   Klaus Ethgen kl...@ethgen.de
Fingerprint: 85D4 CA42 952C 949B 1753  62B3 79D0 B06F 4E20 AF1C
-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQGcBAEBCgAGBQJVmHtyAAoJEKZ8CrGAGfasv9IMAJruWwlEy21NnLzvFCq5L+uA
Ln4oL9FFzb3/szEo8gAsiUw3+LodldajsbCanF2HdJSYiXlqvZDDaTS+k4c/TXja
jf0y41vE7IGjQhFQhC2R8bGjI3gLzIJHBGRuYchVZVvrDlaUOk8lB1UxNLPECbBl
2Y+GRXoQgYfFAF/K4YiyRKlrIME7K2YjF7ocfuDjuEoe7JEA1dKVjIrqsk/gZQbH
bu+zyjt6xljAfHwNpz6SADNSPsS4Mp+kqpWoqH4lp/xnH45U8iPKFanQeNIE54l7
wTMzGQtC828PGIQA0Yyu9K4brsZeK9DXRJ25Qi+LIfPkr8AcRlFPW6c9REIROflI
fb3lzq5zVdNCh4P0MOhZ1Sff6BHNV6ONX6TKzihw9d0XKkpafWto5qkvDkIqpKwu
n48QiBXpRkxrGrx+8wude4OhHd+qWS9DzxIuak3ljmshPVxyJAxckdTKdestS1fx
BtynZx+DqfKJoacutmOp+tEc6X4qdv1bPsQJUvC6lQ==
=sq3i
-END PGP SIGNATURE-


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#790561: After upgrading udev from 215-18 to 220-7 or 221-1, the system is unbootable afterwards

[Michael Biebl]

Am 30.06.2015 um 22:53 schrieb Klaus Ethgen:
 Am Di den 30. Jun 2015 um 20:22 schrieb Michael Biebl:
 Booting with udev.log-priority=debug udev.children-max=1 on the kernel
 command line should give you a more verbose log. Please attach that.
 
 I did that. And it seems that the bug does not happen with that
 settings.
 
 It just take over 10 minutes for all that messages to scroll over the
 screen. Unfortunately, the messages gets not written anywhere so there
 is no way to attach them to a mail.

With systemd, those early boot messages would end up in the journal.

I don't use sysvinit anymore, so I don't know if there is a way to get
early boot message but you could probably hack the /etc/init.d/udev sysv
init script and add
export SYSTEMD_LOG_TARGET=console before the systemd-udevd daemon is
started and redirect stderr of the daemon to a file in /run (which
should be a tmpfs and writable early during boot).

 Maybe I can film the boot screen
 with all that messages and send you the movie about it. That is the only
 idea that I have to provide you with that informations.

I don't think that would be particularly helpful.

 However, I'll attach you the dmesg from that boot try and a clean dmesg
 from a good udev. In the last one I mark the position where new udev
 breaks. (Note that the order of the messages is completely different
 between the two dmesg outputs.)
 
 Please note also that I get different counts of the following messages with
 every boot:
usb 2-3.2: device descriptor read/64, error -110
usb 8-3.2: device descriptor read/64, error -110
usb 8-3.2: device descriptor read/64, error -110
usb 8-3.2: device descriptor read/64, error -110

I don't see anything relevant in those logs.
I'm a bit confused though: how can you get a dmesg output from a bad
boot, when the system did not boot?

-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?



signature.asc
Description: OpenPGP digital signature

Bug#790561: After upgrading udev from 215-18 to 220-7 or 221-1, the system is unbootable afterwards

[Klaus Ethgen]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Package: udev
Version: 220-7
Severity: critical

After upgrading my system from 215-18 to 220-7 or 221-1, (only udev
changes), my system is not bootable anymore.

Here is all the informations I have:
I first upgraded to 221-1 and then did the reboot. After that, the
system freezes after the SCSI initialisation.

After several tries the system finally booted (after ~5 minutes) with
many errors and showing many timeout of nonexisting devices with an
sequence counter aroung 3000(!) that shows that udev tries to loop over
all available and unavailable USB devices and freezes there with one or
another nonexisting device combination. It craped out, for example,
trying to find a joystick device on a keyboard (the system has no
joystick at all).

Downgrading to 220-7 makes the problem even worse. Then it seems to loop
over all USB devices twice what has twice the change to freeze.

Downgrading to 215-18 solves the problem (After an one hour restart
nightmare).

- -- Package-specific info:

- -- System Information:
Debian Release: stretch/sid
  APT prefers unstable
  APT policy: (800, 'unstable'), (500, 'testing'), (110, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.0.4 (SMP w/8 CPU cores)
Locale: LANG=de_DE, LC_CTYPE=de_DE (charmap=ISO-8859-1) (ignored: LC_ALL set to 
de_DE)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Versions of packages udev depends on:
ii  adduser3.113+nmu3
ii  debconf [debconf-2.0]  1.5.56
ii  libacl12.2.52-2
ii  libblkid1  2.26.2-6
ii  libc6  2.19-18
ii  libkmod2   20-1
ii  libselinux12.3-2+b1
ii  libudev1   215-18
ii  lsb-base   4.1+Debian13+nmu1
ii  procps 2:3.3.10-2
ii  util-linux 2.26.2-6

udev recommends no packages.

udev suggests no packages.

- -- debconf information:
  udev/reboot_needed:
  udev/title/upgrade:
  udev/new_kernel_needed: false
  udev/sysfs_deprecated_incompatibility:

- -- 
Klaus Ethgen  http://www.ethgen.ch/
pub  4096R/4E20AF1C 2011-05-16   Klaus Ethgen kl...@ethgen.de
Fingerprint: 85D4 CA42 952C 949B 1753  62B3 79D0 B06F 4E20 AF1C
-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iQGcBAEBCgAGBQJVklC6AAoJEKZ8CrGAGfas8FAMALiSGXM397rlmDJPbAKREAli
7leRiS1Rq9qQYhuQqrqtaCYyAE4QHJDkz/U/iSsjzJmfkCYGdLtTdcLXvblY6Fx7
P0Gne7Ti/w9+A/WezBWCcn6SY4585zk+hGd+7fj75FUGNiCyteAFJRDTWNH+RrbH
DS+XZ7sJ7XoAGs7MdVCo1QqTQRed2CzkNEnNje9eMRsnBVcrE/J/RO3sYFwEnOnG
C9rGYzA6PCbmILJmkPDjwgR4dLChHeKKtWp/zOJ8we4wgz8wyeFUPms54N7PqJek
xUtO917bQX+34Lt1u2skrA+4sYzg4WNwG/eW+QFOyW4I+PCSUeVnh1mnUw77Dyq9
R0BWIGg8mpnipoer6IUPg7qSuyYPGgb9VQvmmkeeQU06GKj4ljbRNQCiCzMPKgZh
muj5m9zKu+HZRQId06IzbuIZvLWNPsIkl11moq2KkvOJiPNaCKYhJf2wrABWpx2e
/vnXewoJLBbSMilZz7BnNQgfoh6tIWp+9RBUyOv9+g==
=7Peg
-END PGP SIGNATURE-


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#790561: After upgrading udev from 215-18 to 220-7 or 221-1, the system is unbootable afterwards

[Michael Biebl]

Control: tags -1 moreinfo

Am 30.06.2015 um 10:18 schrieb Klaus Ethgen:
 Package: udev
 Version: 220-7
 Severity: critical
 
 After upgrading my system from 215-18 to 220-7 or 221-1, (only udev
 changes), my system is not bootable anymore.
 
 Here is all the informations I have:
 I first upgraded to 221-1 and then did the reboot. After that, the
 system freezes after the SCSI initialisation.
 
 After several tries the system finally booted (after ~5 minutes) with
 many errors and showing many timeout of nonexisting devices with an
 sequence counter aroung 3000(!) that shows that udev tries to loop over
 all available and unavailable USB devices and freezes there with one or
 another nonexisting device combination. It craped out, for example,
 trying to find a joystick device on a keyboard (the system has no
 joystick at all).
 
 Downgrading to 220-7 makes the problem even worse. Then it seems to loop
 over all USB devices twice what has twice the change to freeze.

Is this reproducible with systemd as PID 1 as well?
Is this reproducible with a Debian provided kernel?
Have you made sure that your kernel has all options enabled as specified
in /usr/share/doc/systemd/README.gz?




-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?

-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?



signature.asc
Description: OpenPGP digital signature

Bug#790561: After upgrading udev from 215-18 to 220-7 or 221-1, the system is unbootable afterwards

[Klaus Ethgen]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Am Di den 30. Jun 2015 um 17:38 schrieb Michael Biebl:
 Am 30.06.2015 um 17:52 schrieb Klaus Ethgen:
  # CONFIG_FHANDLE is not set
 
 E.g. that one is missing.
 If you compile your own kernel, you should make sure all requirements
 listed at [1] are met. I didn't check all other options, but your
 problem is most likely related to that.
 
 Regards,
 Michael
 
 [1] https://anonscm.debian.org/cgit/pkg-systemd/systemd.git/tree/README#n38

Well, that are the dependencies for systemd. But I do not use systemd. I
cannot find any dependencies (even new dependencies) for udev.

Regards
   Klaus
- -- 
Klaus Ethgen  http://www.ethgen.ch/
pub  4096R/4E20AF1C 2011-05-16   Klaus Ethgen kl...@ethgen.de
Fingerprint: 85D4 CA42 952C 949B 1753  62B3 79D0 B06F 4E20 AF1C
-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQGcBAEBCgAGBQJVktImAAoJEKZ8CrGAGfasQIwMAJMP4V1VcEAbD6CZrRod/Jsz
QD6zZBc5uv1hEkAVo670mIhZzI5A9iwTEQ1zhEuItiLx22pNO5NTb25g+xAePhKY
9mx1GFOwQbmaV9znd4ymrqNSVtACMp2lFgSaYsoL+vD7Oxh0KtDHZQYJ5Y4LmtOA
UXASd7lljhk9GrImNzvyM1LfMUJ0BE7OaSwLg+cBsEEg6GYT83WWFZ6Bo9tPCkRg
/HQle4ZSeccwTLuCdBluU0DVaI/ItRFIzgDB85lDvCdsKwwC+muUO0zdTEQyuza7
Eo2jktXis8aRd0slbaPz2+iLhwZpTXDOWIRiCynJWBsAEcBvj0zBzvhiOhkiXqD/
aueXuCdZBjbVwqubmUa5qYhJeouZc5lmdVuke+X5D/X6+o0GUova96C01YxvLOF8
a5duuzDvG3lL7WgPVt0NnNJCr+ZIG98+19FQeQezjyuRoELEk6SOjwnGznEfwySV
lOrqsvCEYSu//wkli7ATF/ve4bGBusVQq0YjwPaz4w==
=AJ3v
-END PGP SIGNATURE-


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#790561: After upgrading udev from 215-18 to 220-7 or 221-1, the system is unbootable afterwards

[Michael Biebl]

Am 30.06.2015 um 19:50 schrieb Axel Beckert:
 Hi,
 
 Michael Biebl wrote:
 Am 30.06.2015 um 17:52 schrieb Klaus Ethgen:
 # CONFIG_FHANDLE is not set

 E.g. that one is missing.
 If you compile your own kernel, you should make sure all requirements
 listed at [1] are met. I didn't check all other options, but your
 problem is most likely related to that.
 
 In the past the udev package IIRC checked for such issues in preinst
 and refused to upgrade if it found newly required configurations not
 being present.
 
 Any reason why this hasn't been done in this case?

I'd be willing to merge a tested patch for that.

Thanks,
Michael


-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?



signature.asc
Description: OpenPGP digital signature

Bug#790561: After upgrading udev from 215-18 to 220-7 or 221-1, the system is unbootable afterwards

[Klaus Ethgen]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Am Di den 30. Jun 2015 um 17:38 schrieb Michael Biebl:
 Am 30.06.2015 um 17:52 schrieb Klaus Ethgen:
  # CONFIG_FHANDLE is not set
 
 E.g. that one is missing.

I cannot see how this can introduce this particular bug. However, I'll
give it a try.

 If you compile your own kernel, you should make sure all requirements
 listed at [1] are met. I didn't check all other options, but your
 problem is most likely related to that.

All other kernel requirements on this page are meet.

Regards
   Klaus
- -- 
Klaus Ethgen  http://www.ethgen.ch/
pub  4096R/4E20AF1C 2011-05-16   Klaus Ethgen kl...@ethgen.de
Fingerprint: 85D4 CA42 952C 949B 1753  62B3 79D0 B06F 4E20 AF1C
-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQGcBAEBCgAGBQJVktTSAAoJEKZ8CrGAGfas/KsMAK0aAG6RJ5wzHxzZvYA1brVk
e1WpCgRGeKtY01ivpIbUTqLS4wzLKI4mM7vSAwwzenOUvOi4zBDN8RpH+UOmBly6
Ktn9zy5J/QfSGyR2wzY/Ue0H1320S9xwGLCg4JP68Hs1UaFCaSV0zcaA5NUHeT5c
L34jHBXo+rP9YAmHlkLyhMbOESveAQvN3fCTs9Q1q6csuUk9lXiWM2O4P/6MPaCH
IFT3YHfkL4871BTVe2vsieAIxBsAnE7SBRVtGIZALOeu33ogP/EftqVq5EQom8Q9
bZIEl59gDOC1Ee16nbqScPKq0qEwl/gqjHfl/oOZBwb3yZPMykU03wjSpSWMkiRO
7QSmFHHc/mvpC4MOE3cd+ET6WVhdsD3Fjyf/c7iVuOUhI7zzmOcscEJ56QBvgJB3
6HDB4Pgnlgoj8MfOqywte+FRm9tvKgspBo73wEaBBNVlL67ZrF5rjx2cSN8Cjx3k
jnvWl2zdcSBIpxtAhoQK4TAM8g/1VbTfJoKbrKfl6Q==
=Gobn
-END PGP SIGNATURE-


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#790561: After upgrading udev from 215-18 to 220-7 or 221-1, the system is unbootable afterwards

[Klaus Ethgen]

Hi,

Am Di den 30. Jun 2015 um 16:16 schrieb Michael Biebl:
 Am 30.06.2015 um 10:18 schrieb Klaus Ethgen:
  Package: udev
  Version: 220-7
  Severity: critical
  
  After upgrading my system from 215-18 to 220-7 or 221-1, (only udev
  changes), my system is not bootable anymore.
  
  Here is all the informations I have:
  I first upgraded to 221-1 and then did the reboot. After that, the
  system freezes after the SCSI initialisation.
  
  After several tries the system finally booted (after ~5 minutes) with
  many errors and showing many timeout of nonexisting devices with an
  sequence counter aroung 3000(!) that shows that udev tries to loop over
  all available and unavailable USB devices and freezes there with one or
  another nonexisting device combination. It craped out, for example,
  trying to find a joystick device on a keyboard (the system has no
  joystick at all).
  
  Downgrading to 220-7 makes the problem even worse. Then it seems to loop
  over all USB devices twice what has twice the change to freeze.
 
 Is this reproducible with systemd as PID 1 as well?

I have no systemd on any of my systems. So I cannot test this.

 Is this reproducible with a Debian provided kernel?

Well, as a debian provided kernel is not booting on that system, that is
not possible to get tested.

As you might see, this is a system without initrd and with a separate
/usr. Both thinks that are not supported by systemd. That setup worked
well for ages now.

Also the fact that this bug is especially introduced by only udev change
and that all udev before shows that it is introduced in the changed
versions of udev.

 Have you made sure that your kernel has all options enabled as specified
 in /usr/share/doc/systemd/README.gz?

There is no /usr/share/doc/systemd/README.gz on my system. However, I'll
send you the kernel config so you can check yourself.

Regards
   Klaus
-- 
Klaus Ethgen  http://www.ethgen.ch/
pub  4096R/4E20AF1C 2011-05-16   Klaus Ethgen kl...@ethgen.de
Fingerprint: 85D4 CA42 952C 949B 1753  62B3 79D0 B06F 4E20 AF1C
#
# Automatically generated file; DO NOT EDIT.
# Linux/x86_64 4.0.4 Kernel Configuration
#
CONFIG_64BIT=y
CONFIG_X86_64=y
CONFIG_X86=y
CONFIG_INSTRUCTION_DECODER=y
CONFIG_PERF_EVENTS_INTEL_UNCORE=y
CONFIG_OUTPUT_FORMAT=elf64-x86-64
CONFIG_ARCH_DEFCONFIG=arch/x86/configs/x86_64_defconfig
CONFIG_LOCKDEP_SUPPORT=y
CONFIG_STACKTRACE_SUPPORT=y
CONFIG_HAVE_LATENCYTOP_SUPPORT=y
CONFIG_MMU=y
CONFIG_NEED_DMA_MAP_STATE=y
CONFIG_NEED_SG_DMA_LENGTH=y
CONFIG_GENERIC_ISA_DMA=y
CONFIG_GENERIC_BUG=y
CONFIG_GENERIC_BUG_RELATIVE_POINTERS=y
CONFIG_GENERIC_HWEIGHT=y
CONFIG_ARCH_MAY_HAVE_PC_FDC=y
CONFIG_RWSEM_XCHGADD_ALGORITHM=y
CONFIG_GENERIC_CALIBRATE_DELAY=y
CONFIG_ARCH_HAS_CPU_RELAX=y
CONFIG_ARCH_HAS_CACHE_LINE_SIZE=y
CONFIG_HAVE_SETUP_PER_CPU_AREA=y
CONFIG_NEED_PER_CPU_EMBED_FIRST_CHUNK=y
CONFIG_NEED_PER_CPU_PAGE_FIRST_CHUNK=y
CONFIG_ARCH_HIBERNATION_POSSIBLE=y
CONFIG_ARCH_SUSPEND_POSSIBLE=y
CONFIG_ARCH_WANT_HUGE_PMD_SHARE=y
CONFIG_ARCH_WANT_GENERAL_HUGETLB=y
CONFIG_ZONE_DMA32=y
CONFIG_AUDIT_ARCH=y
CONFIG_ARCH_SUPPORTS_OPTIMIZED_INLINING=y
CONFIG_ARCH_SUPPORTS_DEBUG_PAGEALLOC=y
CONFIG_HAVE_INTEL_TXT=y
CONFIG_X86_64_SMP=y
CONFIG_X86_HT=y
CONFIG_ARCH_HWEIGHT_CFLAGS=-fcall-saved-rdi -fcall-saved-rsi -fcall-saved-rdx 
-fcall-saved-rcx -fcall-saved-r8 -fcall-saved-r9 -fcall-saved-r10 
-fcall-saved-r11
CONFIG_ARCH_SUPPORTS_UPROBES=y
CONFIG_FIX_EARLYCON_MEM=y
CONFIG_DEFCONFIG_LIST=/lib/modules/$UNAME_RELEASE/.config
CONFIG_IRQ_WORK=y
CONFIG_BUILDTIME_EXTABLE_SORT=y

#
# General setup
#
CONFIG_INIT_ENV_ARG_LIMIT=32
CONFIG_CROSS_COMPILE=
# CONFIG_COMPILE_TEST is not set
CONFIG_LOCALVERSION=
CONFIG_LOCALVERSION_AUTO=y
CONFIG_HAVE_KERNEL_GZIP=y
CONFIG_HAVE_KERNEL_BZIP2=y
CONFIG_HAVE_KERNEL_LZMA=y
CONFIG_HAVE_KERNEL_XZ=y
CONFIG_HAVE_KERNEL_LZO=y
CONFIG_HAVE_KERNEL_LZ4=y
# CONFIG_KERNEL_GZIP is not set
# CONFIG_KERNEL_BZIP2 is not set
# CONFIG_KERNEL_LZMA is not set
CONFIG_KERNEL_XZ=y
# CONFIG_KERNEL_LZO is not set
# CONFIG_KERNEL_LZ4 is not set
CONFIG_DEFAULT_HOSTNAME=(none)
CONFIG_SWAP=y
CONFIG_SYSVIPC=y
CONFIG_SYSVIPC_SYSCTL=y
CONFIG_POSIX_MQUEUE=y
CONFIG_POSIX_MQUEUE_SYSCTL=y
CONFIG_CROSS_MEMORY_ATTACH=y
# CONFIG_FHANDLE is not set
# CONFIG_USELIB is not set
CONFIG_AUDIT=y
CONFIG_HAVE_ARCH_AUDITSYSCALL=y
CONFIG_AUDITSYSCALL=y
CONFIG_AUDIT_WATCH=y
CONFIG_AUDIT_TREE=y

#
# IRQ subsystem
#
CONFIG_GENERIC_IRQ_PROBE=y
CONFIG_GENERIC_IRQ_SHOW=y
CONFIG_GENERIC_IRQ_LEGACY_ALLOC_HWIRQ=y
CONFIG_GENERIC_PENDING_IRQ=y
CONFIG_IRQ_DOMAIN=y
CONFIG_GENERIC_MSI_IRQ=y
# CONFIG_IRQ_DOMAIN_DEBUG is not set
CONFIG_IRQ_FORCED_THREADING=y
CONFIG_SPARSE_IRQ=y
CONFIG_CLOCKSOURCE_WATCHDOG=y
CONFIG_ARCH_CLOCKSOURCE_DATA=y
CONFIG_CLOCKSOURCE_VALIDATE_LAST_CYCLE=y
CONFIG_GENERIC_TIME_VSYSCALL=y
CONFIG_GENERIC_CLOCKEVENTS=y
CONFIG_GENERIC_CLOCKEVENTS_BUILD=y
CONFIG_GENERIC_CLOCKEVENTS_BROADCAST=y
CONFIG_GENERIC_CLOCKEVENTS_MIN_ADJUST=y
CONFIG_GENERIC_CMOS_UPDATE=y

#
# Timers subsystem
#
CONFIG_TICK_ONESHOT=y

Bug#790561: After upgrading udev from 215-18 to 220-7 or 221-1, the system is unbootable afterwards

[Klaus Ethgen]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Am Di den 30. Jun 2015 um 19:14 schrieb Ansgar Burchardt:
 Axel Beckert a...@debian.org writes:
  In the past the udev package IIRC checked for such issues in preinst
  and refused to upgrade if it found newly required configurations not
  being present.
 
  Any reason why this hasn't been done in this case?
 
 udev.preinst looks like it tries to do so (check_kernel_features), but
 it depends on several factors:
 
  - /proc/kallsyms needs to be present for the symbols check. This might
not be enabled on custom kernels.

It is enabled in my case. I have a populated /proc/kallsyms.

  - udev must be active

It is. (Is it even possible to run debian without active udev?)

 There is even a check for CONFIG_FHANDLE:
 
 - open_by_handle_at(2)  (CONFIG_FHANDLE)
 
 But I wouldn't trust it too much; after all this check is probably not
 the most tested part of the package...

That might be as it seems to not working.

Regards
   Klaus
- -- 
Klaus Ethgen  http://www.ethgen.ch/
pub  4096R/4E20AF1C 2011-05-16   Klaus Ethgen kl...@ethgen.de
Fingerprint: 85D4 CA42 952C 949B 1753  62B3 79D0 B06F 4E20 AF1C
-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQGcBAEBCgAGBQJVkt5XAAoJEKZ8CrGAGfasOowL/ip0XOTpnPKNTTm5UZiCnhK7
mI0lXTuTm7v8ChDnVEbOrIbWVTDJEEoni0vWOVW64UakHprBQLubTq4fKxdEyrZ5
QbjmGjaqrRKgEz1iAXQXfzWt0dlxURkn9jB5tve5zNRygUO5941QrI3f3KUJE4dB
xmrTd34wA9YcLsg5qjA8S0EjCXCFmwcJpb50TQwaJbYf2kSpxAsjNJ3/gZcNhvaL
9lh+ZX7Mawc1L2qJL9iDkVtYcAwrKV3eBgMD4rk1FDchYASo5JWCwQpuFy9r62xp
AFHfVOA079lPEtfw9boVqJtZqknVUh2jdL41Q1Rz09tzqjHKzbVUhPhluTKRNwxk
2OqSSHqFmepan+9iWRnp6780SpQP6HaDrKV6j4zstWp/bNzTlujjKPHO7P21VOzQ
3mzU1Xs9dphPJBDy5XhEDadrcx7uxc2YS7OHAEWLrwEEjs/cRa5CD5cAg9v3LGO/
wAts0PgF6guDCJaDFEJMGQCetphUDsX4UVqauzdcow==
=DWwd
-END PGP SIGNATURE-


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#790561: After upgrading udev from 215-18 to 220-7 or 221-1, the system is unbootable afterwards

[Klaus Ethgen]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Am Di den 30. Jun 2015 um 17:38 schrieb Michael Biebl:
 Am 30.06.2015 um 17:52 schrieb Klaus Ethgen:
  # CONFIG_FHANDLE is not set
 
 E.g. that one is missing.
 If you compile your own kernel, you should make sure all requirements
 listed at [1] are met. I didn't check all other options, but your
 problem is most likely related to that.

As expected from reading the description and the source of that option,
it doesn't help.

New kernel with all pre requirements in kernel enabled and still
unbootable.

Regards
   Klaus
- -- 
Klaus Ethgen  http://www.ethgen.ch/
pub  4096R/4E20AF1C 2011-05-16   Klaus Ethgen kl...@ethgen.de
Fingerprint: 85D4 CA42 952C 949B 1753  62B3 79D0 B06F 4E20 AF1C
-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQGcBAEBCgAGBQJVkuPdAAoJEKZ8CrGAGfasRXgL/RSCW6CpQf4laq8RrUwNJdZX
BvEtFWrpHV8zLYVge65Cf43yQu5qwDBcSEUv1VX0hoZxijbD+M4I/fvP5dBoD8ar
9ZoRB+thbAZCGWyydau9OL/F5Y4Hd4MBkQ0dqYFSOmeFqdW94WV5INL4iYcMokQ7
gq0aKNvcx82j0aqcRhkT054iF2a1FUDkLgopQLatOYNI1dt4AFULhBC5ywLy2/mh
iFjitA89opUelXfALXmHuGqe1NQopdlUOYWceawlljuNfaZE+Dfv7TZx910E4+0M
J1LWVCjk/PL7crSZjLAii1lcE4iFyYcjZ8oblm87MZDzWXZKneZox/z9d7BoaG3/
9sCzylefPfkrgvKzxjSMoLi3DVwo0OtHJhRUL0TBv6F/klnUb30ITVh7VPxdNIZL
EXTnvUpJGr7zKqJ21r+Prw1Ix8bGBDvR8LQ5Os4h+o+0u7KnqiJjVZDi2ant3FfI
tx6Y0pGebTQlUm2q5CvQ1vsesbBc6Ar/wArj/HgBIA==
=Lcl4
-END PGP SIGNATURE-


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#790561: After upgrading udev from 215-18 to 220-7 or 221-1, the system is unbootable afterwards

[Klaus Ethgen]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Without greetings as the other party also did no greetings.

Am Di den 30. Jun 2015 um 17:38 schrieb Michael Biebl:
 Am 30.06.2015 um 17:52 schrieb Klaus Ethgen:
  # CONFIG_FHANDLE is not set

Ah, now I see. There is a reference to udef. Unfortunatelly no reason
why this is needed now and was not before.


Regards
   Klaus
- -- 
Klaus Ethgen  http://www.ethgen.ch/
pub  4096R/4E20AF1C 2011-05-16   Klaus Ethgen kl...@ethgen.de
Fingerprint: 85D4 CA42 952C 949B 1753  62B3 79D0 B06F 4E20 AF1C
-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQGcBAEBCgAGBQJVktMlAAoJEKZ8CrGAGfas5KgMAK6q/y13K2nuPkkwPpROxfz+
hgGkmMKkcYLOSeJEX/IdojH6tp1bl2tDvrKKXEVXE+UlY4Yh/j1JqjCCckyAnUCQ
Feij8GVObrhDWetSP2JfSHyObkrCTqHc6ruBccg4C1C97JXXM1LzGI3Cyi7UzrWY
gA9fqEsNIC5NHDep2BU7Tct9CiQvVRB+2LKGLkrB72825mxwI1rFDGwHoc4P8efB
JU1nfJTkTswN0+krBuImY4e4lW3R2TeCYYi19ssib3PTVycoiSo7uQEWLH0GwMV3
Z/qa3ugQxwCY/P9WSoE9yTazdT+9PZsHZNIsxJPjp2sXpAPR3Y8ChfQExr3ATgDQ
fbSDPZrqx+Dlo9DWOVDujKaepRrZB3ryh7TSv8ZhWELb6v97URhuw3MdUcfCWa2a
Njc1Cvbo4kM/2BInnA+6e9wgulJYLVqwMnK4Y8Li98QrT0XpNARLo408mPrd0v7U
brc/LdxKURsvy6dFaofvOMOKoy29PmP6N3sAONQz3A==
=FWVb
-END PGP SIGNATURE-


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#790561: After upgrading udev from 215-18 to 220-7 or 221-1, the system is unbootable afterwards

[Axel Beckert]

Hi,

Michael Biebl wrote:
 Am 30.06.2015 um 17:52 schrieb Klaus Ethgen:
  # CONFIG_FHANDLE is not set
 
 E.g. that one is missing.
 If you compile your own kernel, you should make sure all requirements
 listed at [1] are met. I didn't check all other options, but your
 problem is most likely related to that.

In the past the udev package IIRC checked for such issues in preinst
and refused to upgrade if it found newly required configurations not
being present.

Any reason why this hasn't been done in this case?

Regards, Axel
-- 
 ,''`.  |  Axel Beckert a...@debian.org, http://people.debian.org/~abe/
: :' :  |  Debian Developer, ftp.ch.debian.org Admin
`. `'   |  4096R: 2517 B724 C5F6 CA99 5329  6E61 2FF9 CD59 6126 16B5
  `-|  1024D: F067 EA27 26B9 C3FC 1486  202E C09E 1D89 9593 0EDE


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#790561: After upgrading udev from 215-18 to 220-7 or 221-1, the system is unbootable afterwards

[Ansgar Burchardt]

Axel Beckert a...@debian.org writes:
 Michael Biebl wrote:
 Am 30.06.2015 um 17:52 schrieb Klaus Ethgen:
  # CONFIG_FHANDLE is not set
 
 E.g. that one is missing.
 If you compile your own kernel, you should make sure all requirements
 listed at [1] are met. I didn't check all other options, but your
 problem is most likely related to that.

 In the past the udev package IIRC checked for such issues in preinst
 and refused to upgrade if it found newly required configurations not
 being present.

 Any reason why this hasn't been done in this case?

udev.preinst looks like it tries to do so (check_kernel_features), but
it depends on several factors:

 - /proc/kallsyms needs to be present for the symbols check. This might
   not be enabled on custom kernels.
 - udev must be active

There is even a check for CONFIG_FHANDLE:

- open_by_handle_at(2)  (CONFIG_FHANDLE)

But I wouldn't trust it too much; after all this check is probably not
the most tested part of the package...

Ansgar


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#790561: After upgrading udev from 215-18 to 220-7 or 221-1, the system is unbootable afterwards

[Michael Biebl]

Am 30.06.2015 um 20:45 schrieb Klaus Ethgen:
 Am Di den 30. Jun 2015 um 17:38 schrieb Michael Biebl:
 Am 30.06.2015 um 17:52 schrieb Klaus Ethgen:
 # CONFIG_FHANDLE is not set
 
 E.g. that one is missing.
 If you compile your own kernel, you should make sure all requirements
 listed at [1] are met. I didn't check all other options, but your
 problem is most likely related to that.
 
 As expected from reading the description and the source of that option,
 it doesn't help.
 
 New kernel with all pre requirements in kernel enabled and still
 unbootable.

CONFIG_UEVENT_HELPER=y
CONFIG_UEVENT_HELPER_PATH=/sbin/hotplug

Have you fixed that as well?
-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?



signature.asc
Description: OpenPGP digital signature

Bug#790561: After upgrading udev from 215-18 to 220-7 or 221-1, the system is unbootable afterwards

[Michael Biebl]

Am 30.06.2015 um 21:44 schrieb Klaus Ethgen:
 Am Di den 30. Jun 2015 um 20:20 schrieb Michael Biebl:
 New kernel with all pre requirements in kernel enabled and still
 unbootable.
 
 CONFIG_UEVENT_HELPER=y
 
 I cannot find any note about that.

See the README I linked to:

Legacy hotplug slows down the system and confuses udev:
  CONFIG_UEVENT_HELPER_PATH=

The Debian kernel uses
# CONFIG_UEVENT_HELPER is not set

-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?



signature.asc
Description: OpenPGP digital signature

Bug#790561: After upgrading udev from 215-18 to 220-7 or 221-1, the system is unbootable afterwards

[Klaus Ethgen]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Am Di den 30. Jun 2015 um 20:20 schrieb Michael Biebl:
  New kernel with all pre requirements in kernel enabled and still
  unbootable.
 
 CONFIG_UEVENT_HELPER=y

I cannot find any note about that.

 CONFIG_UEVENT_HELPER_PATH=/sbin/hotplug

Yes, I have. But this was always a noop as I have no /sbin/hotplug on my
system.

Regards
   Klaus
- -- 
Klaus Ethgen  http://www.ethgen.ch/
pub  4096R/4E20AF1C 2011-05-16   Klaus Ethgen kl...@ethgen.de
Fingerprint: 85D4 CA42 952C 949B 1753  62B3 79D0 B06F 4E20 AF1C
-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQGcBAEBCgAGBQJVkvGdAAoJEKZ8CrGAGfasaqMMAKBUhAAWGaWPdF/KlAH2PV4e
tytK3oMBHUiY6B0PdLhzfmPmv0hQsLckjbEZ9ipLTIVhABQRTeFbvQNRYIQRjTXS
hESzQVL/OhUtNxDewKNEjUG+/a5Dp49u46HZP0KUE/Q/W8Qz8jILCCS1cCYLTZdh
ouRuHam/Kt7HWIKOhn4rOO/M1pHyvWzP3thh0p+yi3iE+4ZlagEIvo8Ttrw2M838
1ciGtyziQ5v+IyCykGO+nn/lsjCUKwpVbr8NRA+9zZ5nPEMJI1zXhy8QKfodZvHM
CoYhJKyOX7XIUxGJx+qEhP7/GL6PaxtcpR00DViTf67ij4iQ02DM0ij/wEQ+WkFd
6kgtbbKsJbpsMi12svEx0gwiWwHRqMWzn1fKakI+bWStD6EsC5CeyQ+3NuwWtQt6
2+G6z6wyeik5Ltjunmf0uviMvOu5FeBhrcw4yyrHS7vn6evgI5vNCLH57SEuLNWF
u5vnwpXyrp3rIWcVO4D35qq6pZN3YLb+lTW4ec99Aw==
=JuzM
-END PGP SIGNATURE-


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#790561: After upgrading udev from 215-18 to 220-7 or 221-1, the system is unbootable afterwards

[Michael Biebl]

Am 30.06.2015 um 21:20 schrieb Michael Biebl:
 Am 30.06.2015 um 20:45 schrieb Klaus Ethgen:
 Am Di den 30. Jun 2015 um 17:38 schrieb Michael Biebl:
 Am 30.06.2015 um 17:52 schrieb Klaus Ethgen:
 # CONFIG_FHANDLE is not set

 E.g. that one is missing.
 If you compile your own kernel, you should make sure all requirements
 listed at [1] are met. I didn't check all other options, but your
 problem is most likely related to that.

 As expected from reading the description and the source of that option,
 it doesn't help.

 New kernel with all pre requirements in kernel enabled and still
 unbootable.
 
 CONFIG_UEVENT_HELPER=y
 CONFIG_UEVENT_HELPER_PATH=/sbin/hotplug
 
 Have you fixed that as well?

Do you have custom udev rules in /etc/udev/rules.d?
Booting with udev.log-priority=debug udev.children-max=1 on the kernel
command line should give you a more verbose log. Please attach that.


-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?



signature.asc
Description: OpenPGP digital signature

Bug#790561: After upgrading udev from 215-18 to 220-7 or 221-1, the system is unbootable afterwards

[Klaus Ethgen]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Am Di den 30. Jun 2015 um 20:22 schrieb Michael Biebl:
 Do you have custom udev rules in /etc/udev/rules.d?

Not that I know. There are 3 files:
   40-lomoco.rules  70-persistent-cd.rules  70-persistent-net.rules

Gruß
   Klaus
- -- 
Klaus Ethgen  http://www.ethgen.ch/
pub  4096R/4E20AF1C 2011-05-16   Klaus Ethgen kl...@ethgen.de
Fingerprint: 85D4 CA42 952C 949B 1753  62B3 79D0 B06F 4E20 AF1C
-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQGcBAEBCgAGBQJVkvJOAAoJEKZ8CrGAGfaspmgMAIMp7rHbPrfC+yI2mR1WhYdq
H1+Fchqz33QwyflerNPpRLzI85Jv4eu7BVa9CSK+P/uxnd9KCfEtONE4dVxB99Sf
TXElICRpRnXfNu2G/s94Tx3riYWDSa6W91FxbTtHUold6CZ02nMDpJLwZMQT8UBk
aoMODw+w0xvGy/P4KlRmHLB5u1pbkWMH6Dk0pLGJ7XkBRbgNki3PJ/KJ0a3JfYnO
pTnaFElXB8+S9TSod5cBIExBLj3kMCDue+OwzhSH6NOj9HF5KzQiyLoxBpvRbglm
qA77Z/SILirjdEdOF1mkNi0IdwKxGaVSFVhtHwJ1ksMjLMZe2aUNIBJkO2EonVgy
8Siuf5mx0WJt//F/oAlWM40PQQurDqDpB7wSdsTcu04db59o8CKZeanqmMIXF/CP
xLCDctMBzeWEXpPxpLRKk4Qh2qaKvZwsWLnP2xuitxt+eRSLuUKeBc8+XLOxaXk4
VeVb7sV2GkUmw0HgC6CNg0imHuxVj+VYi91l4obdMw==
=Ao3i
-END PGP SIGNATURE-


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#790561: After upgrading udev from 215-18 to 220-7 or 221-1, the system is unbootable afterwards

[Klaus Ethgen]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Am Di den 30. Jun 2015 um 20:20 schrieb Michael Biebl:
 CONFIG_UEVENT_HELPER=y
 CONFIG_UEVENT_HELPER_PATH=/sbin/hotplug

Am Di den 30. Jun 2015 um 21:21 schrieb Michael Biebl:
  CONFIG_UEVENT_HELPER=y
  
  I cannot find any note about that.
 
 See the README I linked to:
 
 Legacy hotplug slows down the system and confuses udev:
   CONFIG_UEVENT_HELPER_PATH=

So please tell me where there is any note about CONFIG_UEVENT_HELPER.
There is a note about CONFIG_UEVENT_HELPER_PATH and I already answered
that this is set to an empty value in the new kernel like descripted in
your link. And I also told you that this is a noop as my system had not
have any /sbin/hotplug.

 The Debian kernel uses
 # CONFIG_UEVENT_HELPER is not set

But this is not what is descripted in the link you gave me.

Gruß
   Klaus
- -- 
Klaus Ethgen  http://www.ethgen.ch/
pub  4096R/4E20AF1C 2011-05-16   Klaus Ethgen kl...@ethgen.de
Fingerprint: 85D4 CA42 952C 949B 1753  62B3 79D0 B06F 4E20 AF1C
-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQGbBAEBCgAGBQJVkv8ZAAoJEKZ8CrGAGfaskegL+J8t4a0zl1+goQ4XcQBdOeOm
aWqJ6fjxs8EktI0JBYlvlG9gnJRQ6Rd33iSrtJF9kqCQZ8EZBXopd1aRiFo4alxl
5HdIlrwxKWzglVAKybjuY2k2tBUNCq3ytdcZ8NW0vjNngvkofSU5B22idKeLRyZz
B4qCE4sm4XvbGgTjqWqCiHeLEFiVfMzV61qNa0QSC0gFewtNT5luK+nD2pplAcbk
1GbbWA8/eUCZ8dbUGirgtLPmZ6w6KVCVy+vb2RDtxw5PgTQ7uzhW8sWAA9pi0i8X
fJDzFmMM/njBrJt5bbzp7MZRmVGfeDv9EGmi91t1g5x3svb+bw7b1G7S8iDU80x/
L4CSKzQr8M1X5FrvV2PlupudbT832Y1zJu1lpVpRoNcUDwL42N8jdHY2XkCbLLpZ
JZi78bzHgrPS9u3lf7odPD8UV0vC8azxug6r4rdCItbZwfY32+WEn0aPAFeYZ67g
Q8CMb3y3uGkB175PuQ1lUExHrHiLCKxnAvC/J6ya
=jeN7
-END PGP SIGNATURE-


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#790561: After upgrading udev from 215-18 to 220-7 or 221-1, the system is unbootable afterwards

[Klaus Ethgen]

Am Di den 30. Jun 2015 um 20:22 schrieb Michael Biebl:
 Booting with udev.log-priority=debug udev.children-max=1 on the kernel
 command line should give you a more verbose log. Please attach that.

I did that. And it seems that the bug does not happen with that
settings.

It just take over 10 minutes for all that messages to scroll over the
screen. Unfortunately, the messages gets not written anywhere so there
is no way to attach them to a mail. Maybe I can film the boot screen
with all that messages and send you the movie about it. That is the only
idea that I have to provide you with that informations.

However, I'll attach you the dmesg from that boot try and a clean dmesg
from a good udev. In the last one I mark the position where new udev
breaks. (Note that the order of the messages is completely different
between the two dmesg outputs.)

Please note also that I get different counts of the following messages with
every boot:
   usb 2-3.2: device descriptor read/64, error -110
   usb 8-3.2: device descriptor read/64, error -110
   usb 8-3.2: device descriptor read/64, error -110
   usb 8-3.2: device descriptor read/64, error -110
(Just a random selection)

Regards
   Klaus
-- 
Klaus Ethgen  http://www.ethgen.ch/
pub  4096R/4E20AF1C 2011-05-16   Klaus Ethgen kl...@ethgen.de
Fingerprint: 85D4 CA42 952C 949B 1753  62B3 79D0 B06F 4E20 AF1C


dmesg.bad.xz
Description: application/xz


dmesg.good.xz
Description: application/xz


signature.asc
Description: Digital signature