Michael Biebl - 26.06.18, 13:30:
> Am 26.06.2018 um 13:02 schrieb Michael Biebl:
> > The only thing we could do is add a versioned
> > Breaks: libffi6 >> 3.3~ to systemd, but I feel a bit uncomfortable
> > doing that.
>
> After further consideration, such a Breaks will not really be helpful,
> as
Am 26.06.2018 um 12:45 schrieb Martin Steigerwald:
> Michael Biebl - 26.06.18, 12:28:
>> Am 25.06.2018 um 18:33 schrieb Michael Biebl:
>>> Am 25.06.2018 um 17:45 schrieb Martin Steigerwald:
So for that booting with Debian kernel would not be necessary I
think, but in order to check for t
Michael Biebl - 26.06.18, 12:28:
> Am 25.06.2018 um 18:33 schrieb Michael Biebl:
> > Am 25.06.2018 um 17:45 schrieb Martin Steigerwald:
> >> So for that booting with Debian kernel would not be necessary I
> >> think, but in order to check for the upower issues after restoring
> >> the original serv
Michael Biebl - 25.06.18, 17:20:
> Am 25.06.2018 um 15:11 schrieb Michael Biebl:
> > Am 25.06.2018 um 09:18 schrieb Martin Steigerwald:
> >> Package: systemd
> >> Version: 239-1
> >> Severity: normal
> >>
> >> Dear Michael, dear Maintainers,
> >>
> >> Since using kernel 4.17-rc7 I think (now usin
Am 25.06.2018 um 18:33 schrieb Michael Biebl:
> Am 25.06.2018 um 17:45 schrieb Martin Steigerwald:
>> So for that booting with Debian kernel would not be necessary I think,
>> but in order to check for the upower issues after restoring the original
>> service file.
>
> The upower related start
Am 25.06.2018 um 17:45 schrieb Martin Steigerwald:
> Michael Biebl - 25.06.18, 17:20:
>> Am 25.06.2018 um 15:11 schrieb Michael Biebl:
>>> Am 25.06.2018 um 09:18 schrieb Martin Steigerwald:
Package: systemd
Version: 239-1
Severity: normal
> […]
Since using kernel 4.17-rc7 I thin
Am 25.06.2018 um 15:11 schrieb Michael Biebl:
> Am 25.06.2018 um 09:18 schrieb Martin Steigerwald:
>> Package: systemd
>> Version: 239-1
>> Severity: normal
>>
>> Dear Michael, dear Maintainers,
>>
>> Since using kernel 4.17-rc7 I think (now using self compiled 4.17 vanilla
>> kernel), I see a stra
Am 25.06.2018 um 09:18 schrieb Martin Steigerwald:
> Package: systemd
> Version: 239-1
> Severity: normal
>
> Dear Michael, dear Maintainers,
>
> Since using kernel 4.17-rc7 I think (now using self compiled 4.17 vanilla
> kernel), I see a strange new behavior on this ThinkPad T520. I did not yet
Dear Michael.
Thank you for your replies.
Michael Biebl - 25.06.18, 10:26:
> Am 25.06.2018 um 10:14 schrieb Martin Steigerwald:
> > severity 902336 important
> > thanks
> >
> > Martin Steigerwald - 25.06.18, 09:18:
> >> Package: systemd
> >> Version: 239-1
> >> Severity: normal
> >
> > […]
> >
Am 25.06.2018 um 10:14 schrieb Martin Steigerwald:
> severity 902336 important
> thanks
>
> Martin Steigerwald - 25.06.18, 09:18:
>> Package: systemd
>> Version: 239-1
>> Severity: normal
> […]
>> % systemctl --state=failed
>> UNIT LOAD ACTIVE SUBDESCRIPTION
>> ● chrony.service l
severity 902336 important
thanks
Martin Steigerwald - 25.06.18, 09:18:
> Package: systemd
> Version: 239-1
> Severity: normal
[…]
> % systemctl --state=failed
> UNIT LOAD ACTIVE SUBDESCRIPTION
> ● chrony.service loaded failed failed chrony, an NTP client/server
> ● upower.service
Am 25.06.2018 um 09:18 schrieb Martin Steigerwald:
> Kernel: Linux 4.17.0-tp520-btrfstrim+ (SMP w/4 CPU cores; PREEMPT)
I would try a Debian provided kernel as a first step.
What happens if you restart chrony when the system is up an running?
Does chrony log something itself?
The journal log from
Package: systemd
Version: 239-1
Severity: normal
Dear Michael, dear Maintainers,
Since using kernel 4.17-rc7 I think (now using self compiled 4.17 vanilla
kernel), I see a strange new behavior on this ThinkPad T520. I did not yet
test whether it is related to the kernel or something else I upgrad
13 matches
Mail list logo
