Control: severity -1 important
After further consideration, I'm downgrading this bug to important.
It only happens for split-usr setups and is apparently hard to trigger,
i.e. happens rarely due to race conditions.
--
Why is it that all of the instruments seeking intelligent life in the
univers
Am 05.01.2016 um 00:58 schrieb Michael Biebl:
> Am 03.01.2016 um 16:21 schrieb Martin Pitt:
>> https://github.com/systemd/systemd/commit/9d06297e26
>>
>> Frank, Michael, if possible, it would be nice if you could confirm
>> that this really fixes your case as well?
>
> I tried the patch, but I
Hello Frank,
Frank B. Brokken [2016-01-04 12:06 +0100]:
> However, if there is/are .deb packages available that I can use to test the
> new, hopefully fixed, version I'm of course more than willing to give it a
> try: in that case all dependencies and the installation/removal of files are
> handle
Hello Frank,
Michael Biebl [2015-12-20 2:08 +0100]:
> So the best guess is that the timing in v228 changed a little (some code
> paths became faster). This would confirm Frank's findings that enabling
> verbose output (which slows down boot a bit) made it less likely to hit.
This also came up re
Dear Michael Biebl, you wrote:
> Here is a more complete log excerpt for v228 (full log attached)
>
> > Dez 20 01:27:42 debian systemd[1]: -.mount: Changed dead -> mounted
...
>
> So the best guess is that the timing in v228 changed a little (some code
> paths became faster). This would confirm F
Here is a more complete log excerpt for v228 (full log attached)
> Dez 20 01:27:42 debian systemd[1]: -.mount: Changed dead -> mounted
> Dez 20 01:27:42 debian systemd[1]: usr.mount: Changed dead -> mounted
> Dez 20 01:27:42 debian systemd[1]: usr.mount: Unit is bound to inactive unit
> dev-sda5.
Am 19.12.2015 um 16:27 schrieb Frank B. Brokken:
> Dear Michael Biebl, you wrote:
>
>>> This information is available at https://www.icce.rug.nl/systemd in the
>>> files
>>> initramfs.debug and alb.
>>
>> Hm, unfortunately the journal dump is incomplete again. I have no idea why
>
> Remarkable.
Hi Michael,
I downgraded to the following versions of the following packages:
libpam-systemd_227-2_i386.deb libudev1_227-2_i386.deb
libsystemd-dev_227-2_i386.deb systemd-sysv_227-2_i386.deb
libsystemd0_227-2_i386.deb systemd_227-2_i386.deb
libudev-dev_227-2_i386.deb udev_227-2_i386.d
Hi Michael,
The journalctl -alb output after adding:
> Then add
> [Service]
> ExecStartPre=/bin/sh -c 'echo "before rootfs remount"; findmnt'
> ExecStartPost=/bin/sh -c 'echo "after rootfs remount"; findmnt'
and rebooting (until failure) is at https:/www.icce.rug.nl/systemd/alb-1650
It does con
Dear Michael Biebl, you wrote:
> > This information is available at https://www.icce.rug.nl/systemd in the
> > files
> > initramfs.debug and alb.
>
> Hm, unfortunately the journal dump is incomplete again. I have no idea why
Remarkable. I made it available the way I got it, so that's apparentl
Am 19.12.2015 um 13:06 schrieb Frank B. Brokken:
> Hi Michael,
>
> As announced in my previous e-mail:
>
>> I'll add the debug entry next (cf. your mail from Date: Fri, 18 Dec 2015
>> 03:15:15 +0100) and let you know the results.
>
> This information is available at https://www.icce.rug.nl/syste
Am 19.12.2015 um 12:40 schrieb Frank B. Brokken:
> Dear Michael Biebl, you wrote:
>> If you downgrade systemd/udev, does the problem go away?
>
> As I feared, downgrading is difficult because of the many reverse
> dependencies.
>
> I looked at
>
> ftp://ftp.de.debian.org/debian/pool/main/
Hi Michael,
As announced in my previous e-mail:
> I'll add the debug entry next (cf. your mail from Date: Fri, 18 Dec 2015
> 03:15:15 +0100) and let you know the results.
This information is available at https://www.icce.rug.nl/systemd in the files
initramfs.debug and alb.
Maybe useful to note
Dear Michael Biebl, you wrote:
> Am 18.12.2015 um 15:59 schrieb Frank B. Brokken:
> > Is there a way to determine that? What I do to upgrade the system is run
> > 'aptitude update' and then 'aptitude upgrade'. Is there a log somewhere that
> > tells me what packages and versions were updated at wha
Am 18.12.2015 um 15:59 schrieb Frank B. Brokken:
> Is there a way to determine that? What I do to upgrade the system is run
> 'aptitude update' and then 'aptitude upgrade'. Is there a log somewhere that
> tells me what packages and versions were updated at what moments in time?
/var/log/dpkg.log i
Dear Michael Biebl, you wrote:
> The verbose debug log from the initramfs and systemd can maybe tell us
> more. But looking at https://www.icce.rug.nl/systemd/journalctl, the
> sda5 mount happens at line 773, the first errors start at line 785 and
> the remount is at line 802.
> So it looks like /
Am 18.12.2015 um 13:34 schrieb Frank B. Brokken:
>> I'm a bit confused by those logs. They show that sda5 have been mounted.
>>
>> Dec 17 15:44:29 localhost.localdomain kernel: EXT4-fs (sda5): mounting
>> ext3 file system using the ext4 subsystem
>> Dec 17 15:44:29 localhost.localdomain kernel: EXT
Dear Michael Biebl, you wrote:
> Well, /usr is mounted by the initramfs these days. So it should already
> be available when systemd is started. If that fails, this is a bug which
> needs to be addressed by initramfs-tools (or one of the hook scripts).
> It wasn't clear so far that /usr hasn't bee
Am 17.12.2015 um 22:38 schrieb Michael Biebl:
> Am 17.12.2015 um 16:24 schrieb Frank B. Brokken:
>> This time the debug shell prompt was available at tty9, although booting
>> failed. And in line with my previous findings, systemd-analyze and journalctl
>> weren't available, as they live in /usr/bi
Am 17.12.2015 um 16:24 schrieb Frank B. Brokken:
> This time the debug shell prompt was available at tty9, although booting
> failed. And in line with my previous findings, systemd-analyze and journalctl
> weren't available, as they live in /usr/bin, and /usr hadn't been mounted. But
Well, /usr is
Dear Michael Biebl, you wrote:
> Am 17.12.2015 um 13:46 schrieb Frank B. Brokken:
> > halt. No reboot (e.g. ctrl-alt-del) is possible and there's no rescue
> > shell>
> What exactly do you mean with halt? The systems completely locks up so
> you can't use the keyboard and switch to tty9?
No, th
Am 17.12.2015 um 13:46 schrieb Frank B. Brokken:
> Dear Michael Biebl, you wrote:
>
>> What happens afterwards? Are you dropped into the rescue shell?
>
> Afterwards (i.e., after the initial failure message) the system tries to
> continue booting, but shows lots of failure messages, eventually gr
Dear Michael Biebl, you wrote:
> What happens afterwards? Are you dropped into the rescue shell?
Afterwards (i.e., after the initial failure message) the system tries to
continue booting, but shows lots of failure messages, eventually grinding to a
halt. No reboot (e.g. ctrl-alt-del) is possible
Am 16.12.2015 um 15:43 schrieb Frank B. Brokken:
> Package: systemd
> Version: 228-2
> Severity: critical
> Justification: breaks the whole system
>
> Dear Maintainer,
>
>* What led up to the situation?
>
> Last week, Tuesday Dec. 8 I upgraded this system. One of the packages that
> were upg
24 matches
Mail list logo
