Processing control commands:
> notfound -1 2.25.1-4
Bug #751238 [util-linux,linux] util-linux/linux: ignores RTC when the RTC
driver is a module
There is no source info for the package 'util-linux' at version '2.25.1-4' with
architecture ''
There is no source info for the package 'linux' at vers
Control: notfound -1 2.25.1-4
Control: clone -1 -2
Control: retitle -2 hwclock-set misconfigures kernel for NTP when RTC holds
local time
Control: notfound -1 2.20.1-5
Control: close -1 2.25-2
Control: found -2 2.25-2
Control: found -2 2.25.1-3
Control: severity -2 serious
(Splitting this bug as
Am 09.10.2014 um 00:54 schrieb Ben Hutchings:
> If
> not, then there is a double adjustment during boot.
That got me thinking. I do have ntp enabled.
After disabling the ntp service, my hwclock is no longer incorrectly set
and I no longer get the fsck errors.
Does ntp and hwclock --hctosys not p
Am 09.10.2014 um 00:54 schrieb Ben Hutchings:
> On Thu, 2014-10-09 at 00:14 +0200, Michael Biebl wrote:
>> Am 08.10.2014 um 23:20 schrieb Ben Hutchings:
>>> With those exact same versions, I still see the system clock set
>>> correctly!
>>
>> What's your timezone? Mine is Europe/Berlin.
>
> Europe
On Thu, 2014-10-09 at 00:14 +0200, Michael Biebl wrote:
> Am 08.10.2014 um 23:20 schrieb Ben Hutchings:
> > With those exact same versions, I still see the system clock set
> > correctly!
>
> What's your timezone? Mine is Europe/Berlin.
Europe/London, which is currently at +0100.
> On each reboo
Am 08.10.2014 um 18:14 schrieb Michael Biebl:
> Am 08.10.2014 um 23:20 schrieb Ben Hutchings:
>> With those exact same versions, I still see the system clock set
>> correctly!
>
> What's your timezone? Mine is Europe/Berlin.
> On each reboot, my hwclock will be off by another -2 hours.
> So if it'
Am 08.10.2014 um 23:20 schrieb Ben Hutchings:
> With those exact same versions, I still see the system clock set
> correctly!
What's your timezone? Mine is Europe/Berlin.
On each reboot, my hwclock will be off by another -2 hours.
So if it's 12:00 local time, after reboot, my hwclock will be set t
On Tue, 2014-10-07 at 21:11 +0200, Michael Biebl wrote:
> Hi Ben
>
> Am 07.10.2014 um 21:00 schrieb Ben Hutchings:
> > On Tue, 2014-10-07 at 20:21 +0200, Michael Biebl wrote:
> >> Fwiw, it was me, how experiences this issue.
> >> After the switch from systz to hctosys in /lib/udev/hwclock-set, my
Hi Ben
Am 07.10.2014 um 21:00 schrieb Ben Hutchings:
> On Tue, 2014-10-07 at 20:21 +0200, Michael Biebl wrote:
>> Fwiw, it was me, how experiences this issue.
>> After the switch from systz to hctosys in /lib/udev/hwclock-set, my
>> hardware clock is no longer properly set under systemd.
>
> It w
On Tue, 2014-10-07 at 19:14 +0200, Andreas Henriksson wrote:
> Control: reopen -1
> Control: found -1 2.25.1-4
Where is -4?
> Hello!
>
> I'm reopening this bug report regarding using --hctosys in the util-linux
> hwclock-set script. The change was proposed for the benefit of arm
> systems where
On Tue, 2014-10-07 at 20:21 +0200, Michael Biebl wrote:
> Am 07.10.2014 um 19:14 schrieb Andreas Henriksson:
> > Control: reopen -1
> > Control: found -1 2.25.1-4
> >
> > Hello!
> >
> > I'm reopening this bug report regarding using --hctosys in the util-linux
> > hwclock-set script. The change wa
On Tue, Oct 07, 2014 at 08:40:26PM +0200, Michael Biebl wrote:
> Am 07.10.2014 um 20:37 schrieb Aurelien Jarno:
> > On Tue, Oct 07, 2014 at 08:21:51PM +0200, Michael Biebl wrote:
> >> Fwiw, it was me, how experiences this issue.
> >> After the switch from systz to hctosys in /lib/udev/hwclock-set,
Am 07.10.2014 um 20:37 schrieb Aurelien Jarno:
> On Tue, Oct 07, 2014 at 08:21:51PM +0200, Michael Biebl wrote:
>> Fwiw, it was me, how experiences this issue.
>> After the switch from systz to hctosys in /lib/udev/hwclock-set, my
>> hardware clock is no longer properly set under systemd.
>>
>> Afa
Am 07.10.2014 um 20:40 schrieb Michael Biebl:
> Am 07.10.2014 um 20:37 schrieb Aurelien Jarno:
>> I don't really see how it can happen, this file is not supposed to be
>> run under systemd, due to the following code at the beginning:
>>
>> | if [ -e /run/systemd/system ] ; then
>> |exit 0
>> |
On Tue, Oct 07, 2014 at 08:21:51PM +0200, Michael Biebl wrote:
> Am 07.10.2014 um 19:14 schrieb Andreas Henriksson:
> > Control: reopen -1
> > Control: found -1 2.25.1-4
> >
> > Hello!
> >
> > I'm reopening this bug report regarding using --hctosys in the util-linux
> > hwclock-set script. The ch
Am 07.10.2014 um 19:14 schrieb Andreas Henriksson:
> Control: reopen -1
> Control: found -1 2.25.1-4
>
> Hello!
>
> I'm reopening this bug report regarding using --hctosys in the util-linux
> hwclock-set script. The change was proposed for the benefit of arm
> systems where RTC drivers are built
Control: reopen -1
Control: found -1 2.25.1-4
Hello!
I'm reopening this bug report regarding using --hctosys in the util-linux
hwclock-set script. The change was proposed for the benefit of arm
systems where RTC drivers are built as modules and when they get loaded
the previous scheme didn't work
17 matches
Mail list logo
