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 min
Michael Biebl writes:
> If 215-8 was working successfully, finding the faulty commit would
> indeed be very helpful. If you know how to use git bisect, you could use
> that to determine the commit. This will be a lengthy process though and
> probably not something you want to do on a live system.
-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
> Unfortunately snapshots.debian.org [1] doesn't seem to have any sparc64
> binaries which would have simplified that process somewhat, as you could
> have quickly installed older versions. And we don't have any sparc64
> porter boxes :-/
But it is normal sparc debian, just sparc64 kernel. Got the
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:
Legac
Hi,
Am 30.06.2015 um 21:48 schrieb Meelis Roos:
>> Did older udev versions work?
>
> Yes.
>
> By dpkg.log, 215-18 was the previous version before 220-7 that broke.
> Unfortunatley, 215 does not seem to be available from Debian mirrors any
> more. 215-18 seems to be available from snapshot.debi
> > Upgraded to 221-1 with init=/bin/bash and chroot, still the same:
> >
> > Loading, please wait...
> > e or neveruudevadm: unrecognized option '--action=add'
>
> Is that "e or neveru" a corruption of some sort?
Yes, it seems so. With different kernel with no initramfs, there were
more corrup
> > I had trouble with udev 220-7 hanging on sparc boot with corrupted
> > messages on serial console. Because it was hard to report in
> > understandable way, I booted init=/bin/bash and tried to upgrade all
> > packages to try the lastest before reporting. However, now systemd setup
> > crashes a
-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
-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"
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 kerne
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
Processing commands for cont...@bugs.debian.org:
> reopen 790561
Bug #790561 {Done: Michael Biebl } [udev] After upgrading
udev from 215-18 to 220-7 or 221-1, the system is unbootable afterwards
Bug reopened
Ignoring request to alter fixed versions of bug #790561 to the same values
previously se
-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 [
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Am Di den 30. Jun 2015 um 19:14 schrieb Ansgar Burchardt:
> Axel Beckert 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.
> >
Axel Beckert 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 you
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 ch
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 likel
-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
-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. Unfortuna
-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 [
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.
> >
>
Processing control commands:
> found -1 220-7
Bug #790560 [udev] udev fails to start on sparc boot, breaking boot
Ignoring request to alter found versions of bug #790560 to the same values
previously set
> severity -1 important
Bug #790560 [udev] udev fails to start on sparc boot, breaking boot
S
Control: severity -1 important
(I'm downgrading to non-RC, since sparc is not a release architecture)
Am 30.06.2015 um 09:57 schrieb Meelis Roos:
> Package: systemd
> Version: 221-1
> Severity: critical
> Justification: breaks the whole system
>
> I had trouble with udev 220-7 hanging on sparc b
Control: found -1 220-7
Control: severity -1 important
(downgrading, not a release architecture)
Am 30.06.2015 um 10:04 schrieb Meelis Roos:
> Package: udev
> Version: 221-1
> Severity: critical
> Justification: breaks the whole system
>
> udev 220-7 broke sparc boot with strange messages about
Processing control commands:
> severity -1 important
Bug #790556 [systemd] systemctl crashes, systemd setup fails
Severity set to 'important' from 'critical'
--
790556: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=790556
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Your message dated Tue, 30 Jun 2015 18:38:18 +0200
with message-id <5592c5fa.5060...@debian.org>
and subject line Re: Bug#790561: After upgrading udev from 215-18 to 220-7 or
221-1, the system is unbootable afterwards
has caused the Debian Bug report #790561,
regarding After upgrading udev from 21
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 ow...@bugs.debi
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 u
Package: usb-modeswitch
Version: 2.2.2+repack0-1
Severity: important
Hi,
according to [1], there is an incompatibility between usb-modeswitch
< 2.2.3 and systemd v221. Now that systemd v221 has landed in unstable,
it would be great if you can update usb-modeswitch accordingly.
Depending on the
Another crash. This time while doing an apt upgrade. I seems not related
to adding new jobs or the hashmap iteration. I have no idea where this
signal is coming from. There is nothing but the usual watchdog messages
in the log before the SEGV.
Jun 30 12:02:08 Storage-Blue systemd[1]: systemd-journa
Processing commands for cont...@bugs.debian.org:
> found 790561 220-7
Bug #790561 [udev] After upgrading udev from 215-18 to 220-7 or 221-1, the
system is unbootable afterwards
Ignoring request to alter found versions of bug #790561 to the same values
previously set
> thanks
Stopping processing
Processing commands for cont...@bugs.debian.org:
> notfound 790561 215-18
Bug #790561 [udev] After upgrading udev from 215-18 to 220-7 or 221-1, the
system is unbootable afterwards
Ignoring request to alter found versions of bug #790561 to the same values
previously set
> thanks
Stopping process
Processing commands for cont...@bugs.debian.org:
> found 790561 221-1
Bug #790561 [udev] After upgrading udev from 215-18 to 220-7 or 221-1, the
system is unbootable afterwards
Marked as found in versions systemd/221-1.
> thanks
Stopping processing here.
Please contact me if you need assistance.
-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.
Processing commands for cont...@bugs.debian.org:
> found 790560 220-7
Bug #790560 [udev] udev fails to start on sparc boot, breaking boot
Marked as found in versions systemd/220-7.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
790560: http://bugs.debian.org/cgi-
Package: udev
Version: 221-1
Severity: critical
Justification: breaks the whole system
udev 220-7 broke sparc boot with strange messages about different
options of udevadm not supported (--cleanup-db un recognized,
--action=add not recognized, --timeout=10 not recognized).
Upgraded to 221-1 with
Package: systemd
Version: 221-1
Severity: critical
Justification: breaks the whole system
I had trouble with udev 220-7 hanging on sparc boot with corrupted
messages on serial console. Because it was hard to report in
understandable way, I booted init=/bin/bash and tried to upgrade all
packages to
38 matches
Mail list logo
