[Bug 1882890] Re: intel-ucode/06-4e-03 from release 20200609 hangs system in early boot
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 @ 2.50GHz stepping: 3 microcode : 0x74 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1882890 Title: intel-ucode/06-4e-03 from release 20200609 hangs system in early boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/intel-microcode/+bug/1882890/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1827884] Re: Boot problems after upgrade to kernel 4.15.0-48 (18.04.2LTS/i386)
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. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1827884 Title: Boot problems after upgrade to kernel 4.15.0-48 (18.04.2LTS/i386) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1827884/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 620455] Re: System time drifts when idle
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 to Ubuntu. https://bugs.launchpad.net/bugs/620455 Title: System time drifts when idle To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/620455/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 620455] Re: System time drifts when idle
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 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 358654] Re: udevadm trigger is not permitted while udev is unconfigured
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 experienced user ? A broken system after an update is a very bad bug IMO. Please find attached the dpkg.log file. ** Attachment added: dpkg.log https://bugs.launchpad.net/ubuntu/+source/devmapper/+bug/358654/+attachment/1536875/+files/dpkg.log -- udevadm trigger is not permitted while udev is unconfigured https://bugs.launchpad.net/bugs/358654 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.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 620455] Re: System time drifts when idle
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.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 619677] Re: Clock drifts during inactivity
** 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 Behaviour : Displayed time is drifting How to reproduce : If I get away from my computer for some times, the time displayed by the clock applet drifts. But the date command also show the wrong time. Moreover, sleep interval also get wrong. To debug this, I tested the following script : #!/bin/bash while [[ true ]] do - date clocktest.log - hwclock clocktest.log - sleep 300 + date clocktest.log + hwclock clocktest.log + sleep 300 done Must be run as root because of hwclock. Il launched it : ./clocktest.sh and got away from my computer Here is the output log : 1 mardi 17 août 2010, 12:42:12 (UTC+0200) 2 mar. 17 août 2010 12:42:13 CEST -0.346882 secondes 3 mardi 17 août 2010, 12:47:13 (UTC+0200) 4 mar. 17 août 2010 12:57:13 CEST -0.080965 secondes 5 mardi 17 août 2010, 12:52:13 (UTC+0200) 6 mar. 17 août 2010 13:02:14 CEST -1.002776 secondes 7 mardi 17 août 2010, 12:57:18 (UTC+0200) 8 mar. 17 août 2010 13:07:18 CEST -0.063633 secondes 9 mardi 17 août 2010, 13:02:18 (UTC+0200) 10 mar. 17 août 2010 13:12:19 CEST -0.361501 secondes 11 mardi 17 août 2010, 13:07:19 (UTC+0200) 12 mar. 17 août 2010 13:17:20 CEST -0.987434 secondes Line 1 and 2 show the first time through the loop. Line 3 and 4 show the bug : while date (and sleep) thinks 5 minutes have elapsed, hwclock shows that 15 minutes have elapsed. Line 5 to 12 shows normal behaviour, except now date is late by 10 minutes. Behaviour is normal because I was back at my desk using the computer. - Having clock applet displaying the wrong time is one thing, but having - the whole system time wrong (since sleep gets confused too) is a major - bug. + Additional info : + * Hardware is an Amilo xi2550 + * If I keep the computer busy, for example building a kernel, and I go away, clock works a expected, + and so does the screen locking mechanism. + * Everything was working fine with 8.04 + ProblemType: Bug DistroRelease: Ubuntu 10.04 Package: gnome-panel 1:2.30.2-0ubuntu0.2 ProcVersionSignature: Ubuntu 2.6.32-24.39-generic 2.6.32.15+drm33.5 Uname: Linux 2.6.32-24-generic i686 Architecture: i386 Date: Wed Aug 18 09:43:59 2010 ExecutablePath: /usr/lib/gnome-panel/clock-applet ProcEnviron: - LANG=fr_FR.utf8 - PATH=(custom, user) - SHELL=/bin/bash + LANG=fr_FR.utf8 + PATH=(custom, user) + SHELL=/bin/bash SourcePackage: gnome-panel XsessionErrors: - (polkit-gnome-authentication-agent-1:1990): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed - (gnome-terminal:2235): Gtk-CRITICAL **: gtk_accel_map_unlock_path: assertion `entry != NULL entry-lock_count 0' failed - (unknown:2763): Gdk-WARNING **: XID collision, trouble ahead - (unknown:2763): Gdk-WARNING **: XID collision, trouble ahead + (polkit-gnome-authentication-agent-1:1990): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed + (gnome-terminal:2235): Gtk-CRITICAL **: gtk_accel_map_unlock_path: assertion `entry != NULL entry-lock_count 0' failed + (unknown:2763): Gdk-WARNING **: XID collision, trouble ahead + (unknown:2763): Gdk-WARNING **: XID collision, trouble ahead -- Clock drifts during inactivity https://bugs.launchpad.net/bugs/619677 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.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 620455] [NEW] System time drifts when idle
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 logfile touch clocktest.log echo START clocktest.log while [[ true ]] do systime=$(date) hwtime=$(hwclock -r) echo $systime | $hwtime clocktest.log sleep 20 done Expected output : On each line, the system time should be roughly the same. Time delta between each line should be around 20 seconds Observed output : Sorry for the 80 character column wrap. See the edited clocktest.log for a cleaner ouput. Look at the following logfile : START jeudi 19 août 2010, 15:09:43 (UTC+0200) | jeu. 19 août 2010 15:09:44 CEST -0.500555 secondes jeudi 19 août 2010, 15:10:04 (UTC+0200) | jeu. 19 août 2010 15:10:05 CEST -1.001562 secondes jeudi 19 août 2010, 15:10:25 (UTC+0200) | jeu. 19 août 2010 15:10:26 CEST -0.985944 secondes jeudi 19 août 2010, 15:10:46 (UTC+0200) | jeu. 19 août 2010 15:15:46 CEST -0.032792 secondes -- 5 minute lag ! jeudi 19 août 2010, 15:11:06 (UTC+0200) | jeu. 19 août 2010 15:16:07 CEST -0.985926 secondes jeudi 19 août 2010, 15:11:27 (UTC+0200) | jeu. 19 août 2010 15:16:28 CEST -1.001539 secondes jeudi 19 août 2010, 15:11:48 (UTC+0200) | jeu. 19 août 2010 15:16:49 CEST -0.985969 secondes jeudi 19 août 2010, 15:12:09 (UTC+0200) | jeu. 19 août 2010 15:17:10 CEST -0.985977 secondes jeudi 19 août 2010, 15:12:30 (UTC+0200) | jeu. 19 août 2010 15:17:31 CEST -1.001544 secondes jeudi 19 août 2010, 15:12:51 (UTC+0200) | jeu. 19 août 2010 15:17:52 CEST -0.985920 secondes jeudi 19 août 2010, 15:13:12 (UTC+0200) | jeu. 19 août 2010 15:18:13 CEST -0.985939 secondes jeudi 19 août 2010, 15:13:33 (UTC+0200) | jeu. 19 août 2010 15:18:34 CEST -1.001581 secondes jeudi 19 août 2010, 15:13:54 (UTC+0200) | jeu. 19 août 2010 15:18:55 CEST -0.985917 secondes jeudi 19 août 2010, 15:14:15 (UTC+0200) | jeu. 19 août 2010 15:29:15 CEST -0.079685 secondes -- add another 10 minute jeudi 19 août 2010, 15:14:35 (UTC+0200) | jeu. 19 août 2010 15:29:36 CEST -1.001568 secondes jeudi 19 août 2010, 15:14:56 (UTC+0200) | jeu. 19 août 2010 15:29:57 CEST -0.985952 secondes As you can see, after 20 minutes without touching the computer, the system time is late by 15 minutes. It did not happen with an ubuntu 8.04 kernel ie 2.6.24-28, so I said it was a regression when asked by ubuntu-bug It has indirect security consequences, because for example after these 20 minutes, I was still able to sudo without being asked for a password. Screen locking does not happen The script must be run with sudo because of hwclock This is an Amilo Xi 2550 notebook. ProblemType: Bug DistroRelease: Ubuntu 10.04 Package: linux-image-2.6.32-24-generic 2.6.32-24.39 [modified: lib/modules/2.6.32-24-generic/kernel/drivers/usb/serial/cp210x.ko] Regression: Yes Reproducible: Yes ProcVersionSignature: Ubuntu 2.6.32-24.39-generic 2.6.32.15+drm33.5 Uname: Linux 2.6.32-24-generic i686 AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.21. Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: cynove 1823 F pulseaudio CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: Card0.Amixer.info: Card hw:0 'Intel'/'HDA Intel at 0xf080 irq 22' Mixer name : 'Realtek ALC883' Components : 'HDA:10573055,10573055,00100700 HDA:10ec0883,17341238,0012' Controls : 29 Simple ctrls : 18 Card1.Amixer.info: Card hw:1 'HDMI'/'HDA ATI HDMI at 0xcfeec000 irq 17' Mixer name : 'ATI R6xx HDMI' Components : 'HDA:1002aa01,00aa0100,0010' Controls : 5 Simple ctrls : 2 Date: Thu Aug 19 15:23:03 2010 HibernationDevice: RESUME=UUID=d8f0ebc9-37f3-4cdb-aca7-44a4bc42c13e MachineType: FUJITSU SIEMENS AMILO Xi 2550 ProcCmdLine: root=UUID=d6f01bdd-8503-4992-bc4e-a511f74318fb ro quiet splash ProcEnviron: PATH=(custom, user) LANG=fr_FR.utf8 SHELL=/bin/bash RelatedPackageVersions: linux-firmware 1.34.1 SourcePackage: linux dmi.bios.date: 03/05/2008 dmi.bios.vendor: Phoenix dmi.bios.version: 1.11C dmi.board.name: F44 dmi.board.vendor: FUJITSU SIEMENS dmi.board.version: 00030D0055014B3C dmi.chassis.type: 10 dmi.chassis.vendor: FUJITSU SIEMENS dmi.modalias: dmi:bvnPhoenix:bvr1.11C:bd03/05/2008:svnFUJITSUSIEMENS:pnAMILOXi2550:pvr:rvnFUJITSUSIEMENS:rnF44:rvr00030D0055014B3C:cvnFUJITSUSIEMENS:ct10:cvr: dmi.product.name: AMILO Xi 2550 dmi.sys.vendor: FUJITSU SIEMENS ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 lucid needs-upstream-testing regression-release -- 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
[Bug 620455] Re: System time drifts when idle
** 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 is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 620455] Re: System time drifts when idle
** 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 https://bugs.launchpad.net/bugs/620455/+attachment/1500054/+files/ArecordDevices.txt ** Attachment added: BootDmesg.txt https://bugs.launchpad.net/bugs/620455/+attachment/1500055/+files/BootDmesg.txt ** Attachment added: Card0.Amixer.values.txt https://bugs.launchpad.net/bugs/620455/+attachment/1500056/+files/Card0.Amixer.values.txt ** Attachment added: Card0.Codecs.codec.0.txt https://bugs.launchpad.net/bugs/620455/+attachment/1500057/+files/Card0.Codecs.codec.0.txt ** Attachment added: Card0.Codecs.codec.1.txt https://bugs.launchpad.net/bugs/620455/+attachment/1500058/+files/Card0.Codecs.codec.1.txt ** Attachment added: Card1.Amixer.values.txt https://bugs.launchpad.net/bugs/620455/+attachment/1500059/+files/Card1.Amixer.values.txt ** Attachment added: Card1.Codecs.codec.0.txt https://bugs.launchpad.net/bugs/620455/+attachment/1500060/+files/Card1.Codecs.codec.0.txt ** Attachment added: CurrentDmesg.txt https://bugs.launchpad.net/bugs/620455/+attachment/1500061/+files/CurrentDmesg.txt ** Attachment added: Dependencies.txt https://bugs.launchpad.net/bugs/620455/+attachment/1500062/+files/Dependencies.txt ** Attachment added: IwConfig.txt https://bugs.launchpad.net/bugs/620455/+attachment/1500063/+files/IwConfig.txt ** Attachment added: Lspci.txt https://bugs.launchpad.net/bugs/620455/+attachment/1500064/+files/Lspci.txt ** Attachment added: Lsusb.txt https://bugs.launchpad.net/bugs/620455/+attachment/1500065/+files/Lsusb.txt ** Attachment added: PciMultimedia.txt https://bugs.launchpad.net/bugs/620455/+attachment/1500066/+files/PciMultimedia.txt ** Attachment added: ProcCpuinfo.txt https://bugs.launchpad.net/bugs/620455/+attachment/1500067/+files/ProcCpuinfo.txt ** Attachment added: ProcInterrupts.txt https://bugs.launchpad.net/bugs/620455/+attachment/1500068/+files/ProcInterrupts.txt ** Attachment added: ProcModules.txt https://bugs.launchpad.net/bugs/620455/+attachment/1500069/+files/ProcModules.txt ** Attachment added: RfKill.txt https://bugs.launchpad.net/bugs/620455/+attachment/1500070/+files/RfKill.txt ** Attachment added: UdevDb.txt https://bugs.launchpad.net/bugs/620455/+attachment/1500071/+files/UdevDb.txt ** Attachment added: UdevLog.txt https://bugs.launchpad.net/bugs/620455/+attachment/1500072/+files/UdevLog.txt ** Attachment added: WifiSyslog.txt https://bugs.launchpad.net/bugs/620455/+attachment/1500073/+files/WifiSyslog.txt -- 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.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 620455] Re: System time drifts when idle
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 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 + # the log file with the same time hwclock -w #start with a fresh logfile touch clocktest.log echo START clocktest.log while [[ true ]] do - systime=$(date) - hwtime=$(hwclock -r) - echo $systime | $hwtime clocktest.log - sleep 20 + systime=$(date) + hwtime=$(hwclock -r) + echo $systime | $hwtime clocktest.log + sleep 20 done Expected output : - On each line, the system time should be roughly the same. Time delta between each line should be + On each line, the system time should be roughly the same. Time delta between each line should be around 20 seconds Observed output : + Sorry for the 80 character column wrap. See the edited clocktest.log + for a cleaner ouput. Look at the following logfile : START jeudi 19 août 2010, 15:09:43 (UTC+0200) | jeu. 19 août 2010 15:09:44 CEST -0.500555 secondes jeudi 19 août 2010, 15:10:04 (UTC+0200) | jeu. 19 août 2010 15:10:05 CEST -1.001562 secondes jeudi 19 août 2010, 15:10:25 (UTC+0200) | jeu. 19 août 2010 15:10:26 CEST -0.985944 secondes jeudi 19 août 2010, 15:10:46 (UTC+0200) | jeu. 19 août 2010 15:15:46 CEST -0.032792 secondes -- 5 minute lag ! jeudi 19 août 2010, 15:11:06 (UTC+0200) | jeu. 19 août 2010 15:16:07 CEST -0.985926 secondes jeudi 19 août 2010, 15:11:27 (UTC+0200) | jeu. 19 août 2010 15:16:28 CEST -1.001539 secondes jeudi 19 août 2010, 15:11:48 (UTC+0200) | jeu. 19 août 2010 15:16:49 CEST -0.985969 secondes jeudi 19 août 2010, 15:12:09 (UTC+0200) | jeu. 19 août 2010 15:17:10 CEST -0.985977 secondes jeudi 19 août 2010, 15:12:30 (UTC+0200) | jeu. 19 août 2010 15:17:31 CEST -1.001544 secondes jeudi 19 août 2010, 15:12:51 (UTC+0200) | jeu. 19 août 2010 15:17:52 CEST -0.985920 secondes jeudi 19 août 2010, 15:13:12 (UTC+0200) | jeu. 19 août 2010 15:18:13 CEST -0.985939 secondes jeudi 19 août 2010, 15:13:33 (UTC+0200) | jeu. 19 août 2010 15:18:34 CEST -1.001581 secondes jeudi 19 août 2010, 15:13:54 (UTC+0200) | jeu. 19 août 2010 15:18:55 CEST -0.985917 secondes jeudi 19 août 2010, 15:14:15 (UTC+0200) | jeu. 19 août 2010 15:29:15 CEST -0.079685 secondes -- add another 10 minute jeudi 19 août 2010, 15:14:35 (UTC+0200) | jeu. 19 août 2010 15:29:36 CEST -1.001568 secondes jeudi 19 août 2010, 15:14:56 (UTC+0200) | jeu. 19 août 2010 15:29:57 CEST -0.985952 secondes As you can see, after 20 minutes without touching the computer, the system time is late by 15 minutes. It did not happen with an ubuntu 8.04 kernel ie 2.6.24-28, so I said it was a regression when asked by ubuntu-bug It has indirect security consequences, because for example after these 20 minutes, I was still able to sudo without being asked - for a password. Screen locking does not happen + for a password. Screen locking does not happen The script must be run with sudo because of hwclock This is an Amilo Xi 2550 notebook. ProblemType: Bug DistroRelease: Ubuntu 10.04 Package: linux-image-2.6.32-24-generic 2.6.32-24.39 [modified: lib/modules/2.6.32-24-generic/kernel/drivers/usb/serial/cp210x.ko] Regression: Yes Reproducible: Yes ProcVersionSignature: Ubuntu 2.6.32-24.39-generic 2.6.32.15+drm33.5 Uname: Linux 2.6.32-24-generic i686 AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.21. Architecture: i386 AudioDevicesInUse: - USERPID ACCESS COMMAND - /dev/snd/controlC0: cynove 1823 F pulseaudio + USERPID ACCESS COMMAND + /dev/snd/controlC0: cynove 1823 F pulseaudio CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: Card0.Amixer.info: - Card hw:0 'Intel'/'HDA Intel at 0xf080 irq 22' -Mixer name : 'Realtek ALC883' -Components : 'HDA:10573055,10573055,00100700 HDA:10ec0883,17341238,0012' -Controls : 29 -Simple ctrls : 18 + Card hw:0 'Intel'/'HDA Intel at 0xf080 irq 22' + Mixer name : 'Realtek ALC883' + Components : 'HDA:10573055,10573055,00100700 HDA:10ec0883,17341238,0012' + Controls : 29 + Simple ctrls : 18 Card1.Amixer.info: - Card hw:1 'HDMI'/'HDA ATI HDMI at 0xcfeec000 irq 17' -Mixer name : 'ATI R6xx HDMI' -Components : 'HDA:1002aa01,00aa0100,0010' -Controls : 5 -Simple ctrls : 2 + Card hw:1 'HDMI'/'HDA ATI HDMI at 0xcfeec000 irq 17' + Mixer name : 'ATI R6xx HDMI' + Components : 'HDA:1002aa01,00aa0100,0010' + Controls : 5 + Simple ctrls : 2
[Bug 620455] Re: System time drifts when idle
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.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 619677] Re: Clock drifts during inactivity
*** 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 are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 619677] [NEW] Clock drifts during inactivity
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 is drifting How to reproduce : If I get away from my computer for some times, the time displayed by the clock applet drifts. But the date command also show the wrong time. Moreover, sleep interval also get wrong. To debug this, I tested the following script : #!/bin/bash while [[ true ]] do date clocktest.log hwclock clocktest.log sleep 300 done Must be run as root because of hwclock. Il launched it : ./clocktest.sh and got away from my computer Here is the output log : 1 mardi 17 août 2010, 12:42:12 (UTC+0200) 2 mar. 17 août 2010 12:42:13 CEST -0.346882 secondes 3 mardi 17 août 2010, 12:47:13 (UTC+0200) 4 mar. 17 août 2010 12:57:13 CEST -0.080965 secondes 5 mardi 17 août 2010, 12:52:13 (UTC+0200) 6 mar. 17 août 2010 13:02:14 CEST -1.002776 secondes 7 mardi 17 août 2010, 12:57:18 (UTC+0200) 8 mar. 17 août 2010 13:07:18 CEST -0.063633 secondes 9 mardi 17 août 2010, 13:02:18 (UTC+0200) 10 mar. 17 août 2010 13:12:19 CEST -0.361501 secondes 11 mardi 17 août 2010, 13:07:19 (UTC+0200) 12 mar. 17 août 2010 13:17:20 CEST -0.987434 secondes Line 1 and 2 show the first time through the loop. Line 3 and 4 show the bug : while date (and sleep) thinks 5 minutes have elapsed, hwclock shows that 15 minutes have elapsed. Line 5 to 12 shows normal behaviour, except now date is late by 10 minutes. Behaviour is normal because I was back at my desk using the computer. Having clock applet displaying the wrong time is one thing, but having the whole system time wrong (since sleep gets confused too) is a major bug. ProblemType: Bug DistroRelease: Ubuntu 10.04 Package: gnome-panel 1:2.30.2-0ubuntu0.2 ProcVersionSignature: Ubuntu 2.6.32-24.39-generic 2.6.32.15+drm33.5 Uname: Linux 2.6.32-24-generic i686 Architecture: i386 Date: Wed Aug 18 09:43:59 2010 ExecutablePath: /usr/lib/gnome-panel/clock-applet ProcEnviron: LANG=fr_FR.utf8 PATH=(custom, user) SHELL=/bin/bash SourcePackage: gnome-panel XsessionErrors: (polkit-gnome-authentication-agent-1:1990): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed (gnome-terminal:2235): Gtk-CRITICAL **: gtk_accel_map_unlock_path: assertion `entry != NULL entry-lock_count 0' failed (unknown:2763): Gdk-WARNING **: XID collision, trouble ahead (unknown:2763): Gdk-WARNING **: XID collision, trouble ahead ** Affects: gnome-panel (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 lucid -- Clock drifts during inactivity https://bugs.launchpad.net/bugs/619677 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.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 619677] Re: Clock drifts during inactivity
** 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 https://bugs.launchpad.net/bugs/619677/+attachment/1497251/+files/ProcMaps.txt ** Attachment added: ProcStatus.txt https://bugs.launchpad.net/bugs/619677/+attachment/1497252/+files/ProcStatus.txt -- Clock drifts during inactivity https://bugs.launchpad.net/bugs/619677 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.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 619677] Re: Clock drifts during inactivity
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 mercredi 18 août 2010, 12:32:00 (UTC+0200) mer. 18 août 2010 13:17:00 CEST -0.079076 secondes 10 minutes elapsed for the system clock, while almost one hour really elapsed. This as security consequences, because when I came back, my screen was not locked. I don't know what the default screen lock timing is, but I guess it is less than 1 hour. -- Clock drifts during inactivity https://bugs.launchpad.net/bugs/619677 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.ubuntu.com/mailman/listinfo/ubuntu-bugs
