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.
Processing control commands:
severity -1 important
Bug #790561 [udev] After upgrading udev from 215-18 to 220-7 or 221-1, the
system is unbootable afterwards
Severity set to 'important' from 'critical'
--
790561: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=790561
Debian Bug Tracking
-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
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
-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
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
-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
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
Processing control commands:
tags -1 moreinfo
Bug #790561 [udev] After upgrading udev from 215-18 to 220-7 or 221-1, the
system is unbootable afterwards
Added tag(s) moreinfo.
--
790561: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=790561
Debian Bug Tracking System
Contact
-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
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
-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
-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
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
-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.
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
-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.
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
-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
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
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
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
-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
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
-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
25 matches
Mail list logo
