Hi, looks like this bug is back with the latest microcode update.
My ASUS PC only boot with dis_ucode_ldr kernel parameter.
4.4.0-194-generic #226-Ubuntu
processor : 0
vendor_id : GenuineIntel
cpu family : 6
model : 78
model name : Intel(R) Core(TM) i7-6500U CPU @
I just tried, and it indeed works around the bug.
The bug also disappear when booting with nohz=off
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/620455
Title:
System time drifts when idle
--
ubu
It is fixed upstream, ie I can boot a mainline 3.4.2 kernel without
nohz=off command line, and the clock does not drift.
** Tags removed: needs-upstream-testing
** Tags added: kernel-fixed-upstream
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
Public bug reported:
Binary package hint: gnome-panel
I filed this bug using the PID of the clock-applet and ubuntu bug, but I think
the clock-applet only shows a symptom, Here is
a description :
Expected Behaviour :
Clock-applet displays the correct time,
Observed Behaviour :
Displayed time i
** Attachment added: "Dependencies.txt"
https://bugs.launchpad.net/bugs/619677/+attachment/1497249/+files/Dependencies.txt
** Attachment added: "GConfNonDefault.txt"
https://bugs.launchpad.net/bugs/619677/+attachment/1497250/+files/GConfNonDefault.txt
** Attachment added: "ProcMaps.txt"
Todays lunch break : I launched the program at 12:21, here is the output
when I came back around 13:20
mercredi 18 août 2010, 12:21:59 (UTC+0200)
mer. 18 août 2010 12:22:00 CEST -0.625930 secondes
mercredi 18 août 2010, 12:27:00 (UTC+0200)
mer. 18 août 2010 13:02:00 CEST -0.034145 secondes
mer
** Description changed:
Binary package hint: gnome-panel
I filed this bug using the PID of the clock-applet and ubuntu bug, but I
think the clock-applet only shows a symptom, Here is
a description :
Expected Behaviour :
Clock-applet displays the correct time,
Observed Behavio
Public bug reported:
It seems the system time stops when my notebook goes idle.
By idle, I don't mean suspend or screen lock. But this is best described by the
following script :
#!/bin/bash
# set hwclock to system clock to start
# the log file with the same time
hwclock -w
#start with a fresh l
** Attachment added: "clocktest log"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/620455/+attachment/1500074/+files/clocktest.log
--
System time drifts when idle
https://bugs.launchpad.net/bugs/620455
You received this bug notification because you are a member of Ubuntu
Bugs, which i
** Attachment added: "AlsaDevices.txt"
https://bugs.launchpad.net/bugs/620455/+attachment/1500052/+files/AlsaDevices.txt
** Attachment added: "AplayDevices.txt"
https://bugs.launchpad.net/bugs/620455/+attachment/1500053/+files/AplayDevices.txt
** Attachment added: "ArecordDevices.txt"
Since the 80 column wrap made my two column output look wrong, here is
an edited log
** Attachment added: "Edited clocktest.log"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/620455/+attachment/1500075/+files/clocktest.log
** Description changed:
It seems the system time stops when
Bug reproduced with 2.6.32-02063219-generic
--
System time drifts when idle
https://bugs.launchpad.net/bugs/620455
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.
*** This bug is a duplicate of bug 620455 ***
https://bugs.launchpad.net/bugs/620455
** This bug has been marked a duplicate of bug 620455
System time drifts when idle
--
Clock drifts during inactivity
https://bugs.launchpad.net/bugs/619677
You received this bug notification because you a
Bug reproduced with 2.6.36-rc1
** Tags removed: needs-upstream-testing
--
System time drifts when idle
https://bugs.launchpad.net/bugs/620455
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists
System broken after update !
sudo update-initramfs -u -k 2.6.32-24-generic restored a working boot.
Why don't you save the previous kernel + initramfs when updating image ?
I am glad I had another working kernel + initramfs.
How are you supposed to even find this page if you are not an
experience
I have three different machines running Xubuntu 18.04 i386. All are
affected.
After upgrade to kernel 4.15.0-48 the boot process will stop to an almost black
screen with a few multi-coloured lines.
Problem still persists with kernel 4.15.0-50.
Everything works fine with kernel 4.15.0-47.
--
Yo
16 matches
Mail list logo
