[arch-general] my Arch box randomly becomes irresponsible
Dear Arch users, I have latest Arch installed on my desktop at work. In recent two weeks, the system randomly "suspends" at night (I call it "randomly" because it didn't happen every night. And it seems to happen after a random period idle time) when I am off. I can't wake it up in the next morning thru mouse or keyboard. I tried to disable suspension and hibernation by editing /usr/share/polkit-1/actions/org.freedesktop.upower.policy to change from <allow_active>yes</allow_active> to <allow_active>no</allow_active> But it doesn't work. While I call it "suspend", I am not sure it suspend to RAM or hibernate to disk, because I find the CPU fan and power fan still spin normally. RAM light is also on. So it might be a video driver / setting related issue. For your information, I am using nvidia-302.17-2-x86_64 and have dual monitor set up with nvidia-utils-302.17-1-x86_64 This really bothers me a lot. Any help is appreciated. Thanks! -- Best, Zech
2012/7/15 Not To Miss <not.to.miss@gmail.com>
Dear Arch users,
I have latest Arch installed on my desktop at work. In recent two weeks, the system randomly "suspends" at night (I call it "randomly" because it didn't happen every night. And it seems to happen after a random period idle time) when I am off. I can't wake it up in the next morning thru mouse or keyboard.
I tried to disable suspension and hibernation by editing /usr/share/polkit-1/actions/org.freedesktop.upower.policy to change from <allow_active>yes</allow_active> to <allow_active>no</allow_active>
But it doesn't work.
While I call it "suspend", I am not sure it suspend to RAM or hibernate to disk, because I find the CPU fan and power fan still spin normally. RAM light is also on. So it might be a video driver / setting related issue. For your information, I am using nvidia-302.17-2-x86_64 and have dual monitor set up with nvidia-utils-302.17-1-x86_64
This really bothers me a lot. Any help is appreciated. Thanks!
-- Best, Zech
Any hint on /var/log/messages or /var/log/errors?
I didn't remeber I had seen anything relevant in log files. Here is the most recent record in /var/log/messages files (I pressed reset button to reboot at Jul 15 20:37) with "-- MARK -- \" message lines skipped: Jul 14 20:36:15 phelps kernel: [111935.191008] PGD 10b42e067 PUD 0 Jul 14 20:36:15 phelps kernel: [111935.191011] Oops: 0000 [#1] PREEMPT SMP Jul 14 20:36:15 phelps kernel: [111935.191015] CPU 0 Jul 14 20:36:15 phelps kernel: [111935.191016] Modules linked in: fuse pci_stub vboxpci(O) vboxnetflt(O) vboxnetadp(O) vboxdrv(O) snd_hda_codec_realtek nvidia(PO) r8169 snd_hd a_intel snd_hda_codec snd_hwdep snd_pcm snd_page_alloc snd_timer snd soundcore microcode psmouse i2c_i801 serio_raw intel_agp processor pcspkr iTCO_wdt coretemp mii evdev inte l_gtt iTCO_vendor_support button i2c_core ext4 crc16 jbd2 mbcache raid0 raid456 async_raid6_recov async_memcpy async_pq async_xor xor async_tx raid6_pq raid1 md_mod sr_mod cdr om sd_mod usbhid pata_jmicron hid pata_acpi ahci libahci uhci_hcd ata_piix ata_generic ehci_hcd libata scsi_mod usbcore usb_common floppy Jul 14 20:36:15 phelps kernel: [111935.191057] Jul 14 20:36:15 phelps kernel: [111935.191059] Pid: 1373, comm: gnome-shell Tainted: P O 3.4.4-2-ARCH #1 Gigabyte Technology Co., Ltd. P35-DS3R/P35-DS3R Jul 14 20:36:15 phelps kernel: [111935.191063] RIP: 0010:[<ffffffffa06deb9e>] [<ffffffffa06deb9e>] _nv003990rm+0x4160/0xa790 [nvidia] Jul 14 20:36:15 phelps kernel: [111935.191186] RSP: 0018:ffff88010b6efa88 EFLAGS: 00010246 Jul 14 20:36:15 phelps kernel: [111935.191188] RAX: 00000000ffffffbb RBX: ffff88011742e008 RCX: 0000000000088004 Jul 14 20:36:15 phelps kernel: [111935.191190] RDX: ffff88011742e378 RSI: ffff88011742e008 RDI: 000000201875d808 Jul 14 20:36:15 phelps kernel: [111935.191192] RBP: ffff880118a8dfe0 R08: 0000000000000000 R09: ffff880118a8dfec Jul 14 20:36:15 phelps kernel: [111935.191194] R10: 0000000000000000 R11: 0000000000000001 R12: 0000000000088004 Jul 14 20:36:15 phelps kernel: [111935.191196] R13: 0000000000000000 R14: ffff88011742e378 R15: 0000000000000000 Jul 14 20:36:15 phelps kernel: [111935.191199] FS: 00007f8f3df8e940(0000) GS:ffff88011fc00000(0000) knlGS:0000000000000000 Jul 14 20:36:15 phelps kernel: [111935.191201] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 Jul 14 20:36:15 phelps kernel: [111935.191203] CR2: 000000201875dac0 CR3: 000000010b42b000 CR4: 00000000000007f0 Jul 14 20:36:15 phelps kernel: [111935.191205] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 Jul 14 20:36:15 phelps kernel: [111935.191208] DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400 Jul 14 20:36:15 phelps kernel: [111935.191210] Process gnome-shell (pid: 1373, threadinfo ffff88010b6ee000, task ffff8801103d7710) Jul 14 20:36:15 phelps kernel: [111935.191212] Stack: Jul 14 20:36:15 phelps kernel: [111935.191213] ffff88011742e008 ffff88011742e008 0000000000000000 0000000000088004 Jul 14 20:36:15 phelps kernel: [111935.191218] ffffc90005144008 ffffffffa06deaac ffff88011875f800 ffff88011742e008 Jul 14 20:36:15 phelps kernel: [111935.191222] 0000000000000000 ffff880118a8b000 ffffc90005144008 ffffffffa09067a1 Jul 14 20:36:15 phelps kernel: [111935.191226] Call Trace: Jul 14 20:36:15 phelps kernel: [111935.191347] [<ffffffffa06deaac>] ? _nv003990rm+0x406e/0xa790 [nvidia] Jul 14 20:36:15 phelps kernel: [111935.191400] [<ffffffffa09067a1>] ? rm_check_pci_config_space+0x499/0xa44 [nvidia] Jul 14 20:36:15 phelps kernel: [111935.191450] [<ffffffffa0921930>] ? nv_verify_pci_config+0x60/0x80 [nvidia] Jul 14 20:36:15 phelps kernel: [111935.191502] [<ffffffffa08fbaab>] ? _nv014590rm+0x22/0x27 [nvidia] Jul 14 20:36:15 phelps kernel: [111935.191553] [<ffffffffa09080f7>] ? _nv014633rm+0x31/0x538 [nvidia] Jul 14 20:36:15 phelps kernel: [111935.191675] [<ffffffffa06be7e3>] ? _nv009673rm+0xf7/0x134 [nvidia] Jul 14 20:36:15 phelps kernel: [111935.191795] [<ffffffffa06df156>] ? _nv003990rm+0x4718/0xa790 [nvidia] Jul 14 20:36:15 phelps kernel: [111935.191846] [<ffffffffa0906bdf>] ? rm_check_pci_config_space+0x8d7/0xa44 [nvidia] Jul 14 20:36:15 phelps kernel: [111935.191915] [<ffffffffa0360736>] ? _nv014429rm+0x9/0x21 [nvidia] Jul 14 20:36:15 phelps kernel: [111935.191964] [<ffffffffa0921930>] ? nv_verify_pci_config+0x60/0x80 [nvidia] Jul 14 20:36:15 phelps kernel: [111935.192015] [<ffffffffa08fbaab>] ? _nv014590rm+0x22/0x27 [nvidia] Jul 14 20:36:15 phelps kernel: [111935.192078] [<ffffffffa031eefa>] ? _nv000529rm+0x62/0x98 [nvidia] Jul 14 20:36:15 phelps kernel: [111935.192146] [<ffffffffa03639a2>] ? _nv016127rm+0x2c/0x67 [nvidia] Jul 14 20:36:15 phelps kernel: [111935.192214] [<ffffffffa0362eaa>] ? _nv016521rm+0x14aa/0x14fb [nvidia] Jul 14 20:36:15 phelps kernel: [111935.192282] [<ffffffffa0363458>] ? _nv016148rm+0x55d/0x58b [nvidia] Jul 14 20:36:15 phelps kernel: [111935.192349] [<ffffffffa0363495>] ? _nv001046rm+0xf/0x14 [nvidia] Jul 14 20:36:15 phelps kernel: [111935.192416] [<ffffffffa0348b2e>] ? _nv000945rm+0x31/0x59 [nvidia] Jul 14 20:36:15 phelps kernel: [111935.192470] [<ffffffffa08f6a2e>] ? _nv001095rm+0xa3e/0xa9f [nvidia] Jul 14 20:36:15 phelps kernel: [111935.192521] [<ffffffffa09035d0>] ? rm_ioctl+0x76/0xf3 [nvidia] Jul 14 20:36:15 phelps kernel: [111935.192570] [<ffffffffa0921e0e>] ? nv_kern_ioctl+0x15e/0x480 [nvidia] Jul 14 20:36:15 phelps kernel: [111935.192619] [<ffffffffa0922181>] ? nv_kern_unlocked_ioctl+0x21/0x30 [nvidia] Jul 14 20:36:15 phelps kernel: [111935.192624] [<ffffffff81180787>] ? do_vfs_ioctl+0x97/0x530 Jul 14 20:36:15 phelps kernel: [111935.192627] [<ffffffff81170097>] ? fget_light+0x97/0x100 Jul 14 20:36:15 phelps kernel: [111935.192630] [<ffffffff81180cb9>] ? sys_ioctl+0x99/0xa0 Jul 14 20:36:15 phelps kernel: [111935.192634] [<ffffffff8146a8e9>] ? system_call_fastpath+0x16/0x1b ul 14 20:36:15 phelps kernel: [111935.192636] Code: 20 00 00 00 44 89 f9 44 89 e2 44 89 ee 48 89 df e8 42 7d 00 00 f6 45 0c 02 75 16 45 89 f8 44 89 e1 4c 89 f2 48 89 de 48 8b 7d 00 <ff> 97 b8 02 00 00 48 83 c5 10 5b 41 5c 41 5d 41 5e 41 5f c3 41 Jul 14 20:36:15 phelps kernel: [111935.192788] RSP <ffff88010b6efa88> Jul 14 20:36:15 phelps kernel: [111935.192789] CR2: 000000201875dac0 Jul 14 20:36:15 phelps kernel: [111935.192821] ---[ end trace e8b17fa2032ffeeb ]--- ... Jul 15 13:31:45 phelps dhcpcd[873]: eth0: renewing lease of 172.18.200.52 Jul 15 13:31:45 phelps dhcpcd[873]: eth0: acknowledged 172.18.200.52 from 172.17.254.30 Jul 15 13:31:45 phelps dhcpcd[873]: eth0: leased 172.18.200.52 for 86400 seconds ... Jul 15 20:37:17 phelps kernel: [ 0.000000] Initializing cgroup subsys cpuset Jul 15 20:37:17 phelps kernel: [ 0.000000] Initializing cgroup subsys cpu Jul 15 20:37:17 phelps kernel: [ 0.000000] Linux version 3.4.4-2-ARCH (tobias@T-POWA-LX) (gcc version 4.7.1 (GCC) ) #1 SMP PREEMPT Sun Jun 24 18:59:47 CEST 2012 Jul 15 20:37:17 phelps kernel: [ 0.000000] Command line: root=/dev/md2 ro initrd=../initramfs-linux.img BOOT_IMAGE=../vmlinuz-linux Jul 15 20:37:17 phelps kernel: [ 0.000000] BIOS-provided physical RAM map: Jul 15 20:37:17 phelps kernel: [ 0.000000] BIOS-e820: 0000000000000000 - 000000000009f800 (usable) Jul 15 20:37:17 phelps kernel: [ 0.000000] BIOS-e820: 000000000009f800 - 00000000000a0000 (reserved) Jul 15 20:37:17 phelps kernel: [ 0.000000] BIOS-e820: 00000000000f0000 - 0000000000100000 (reserved) ... These are the record from /var/log/errors: Jul 13 13:42:23 phelps kernel: [ 703.602239] end_request: I/O error, dev fd0, sector 0 Jul 13 13:42:23 phelps kernel: [ 703.602246] Buffer I/O error on device fd0, logical block 0 Jul 13 13:42:35 phelps kernel: [ 715.772126] end_request: I/O error, dev fd0, sector 0 Jul 13 13:42:35 phelps kernel: [ 715.772133] Buffer I/O error on device fd0, logical block 0 Jul 13 13:42:47 phelps kernel: [ 727.935544] end_request: I/O error, dev fd0, sector 0 Jul 13 13:42:47 phelps kernel: [ 727.935551] Buffer I/O error on device fd0, logical block 0 Jul 13 13:43:00 phelps kernel: [ 740.098959] end_request: I/O error, dev fd0, sector 0 Jul 13 13:43:00 phelps kernel: [ 740.098965] Buffer I/O error on device fd0, logical block 0 Jul 13 13:43:12 phelps kernel: [ 752.262394] end_request: I/O error, dev fd0, sector 0 Jul 13 13:43:12 phelps kernel: [ 752.262401] Buffer I/O error on device fd0, logical block 0 Jul 13 13:43:24 phelps kernel: [ 764.428886] end_request: I/O error, dev fd0, sector 0 Jul 13 13:43:24 phelps kernel: [ 764.428891] Buffer I/O error on device fd0, logical block 0 Jul 13 13:43:36 phelps kernel: [ 776.598318] end_request: I/O error, dev fd0, sector 0 Jul 13 13:43:48 phelps kernel: [ 788.758826] end_request: I/O error, dev fd0, sector 0 Jul 13 13:44:00 phelps kernel: [ 800.922217] end_request: I/O error, dev fd0, sector 2 Jul 13 13:44:00 phelps kernel: [ 800.922241] EXT4-fs (fd0): unable to read superblock Jul 13 13:44:13 phelps kernel: [ 813.089021] end_request: I/O error, dev fd0, sector 0 Jul 13 13:44:25 phelps kernel: [ 825.255519] end_request: I/O error, dev fd0, sector 2 Jul 13 13:44:25 phelps kernel: [ 825.255541] EXT4-fs (fd0): unable to read superblock Jul 13 13:44:37 phelps kernel: [ 837.435621] end_request: I/O error, dev fd0, sector 0 Jul 13 13:44:49 phelps kernel: [ 849.602125] end_request: I/O error, dev fd0, sector 2 Jul 13 13:44:49 phelps kernel: [ 849.602143] EXT4-fs (fd0): unable to read superblock Jul 13 13:45:01 phelps kernel: [ 861.778900] end_request: I/O error, dev fd0, sector 0 Thanks a lot for your help. On Sun, Jul 15, 2012 at 11:15 PM, Victor Silva <vfbsilva@gmail.com> wrote:
2012/7/15 Not To Miss <not.to.miss@gmail.com>
Dear Arch users,
I have latest Arch installed on my desktop at work. In recent two weeks, the system randomly "suspends" at night (I call it "randomly" because it didn't happen every night. And it seems to happen after a random period idle time) when I am off. I can't wake it up in the next morning thru mouse or keyboard.
I tried to disable suspension and hibernation by editing /usr/share/polkit-1/actions/org.freedesktop.upower.policy to change from <allow_active>yes</allow_active> to <allow_active>no</allow_active>
But it doesn't work.
While I call it "suspend", I am not sure it suspend to RAM or hibernate to disk, because I find the CPU fan and power fan still spin normally. RAM light is also on. So it might be a video driver / setting related issue. For your information, I am using nvidia-302.17-2-x86_64 and have dual monitor set up with nvidia-utils-302.17-1-x86_64
This really bothers me a lot. Any help is appreciated. Thanks!
-- Best, Zech
Any hint on /var/log/messages or /var/log/errors?
-- Best, Zech
2012/7/16 Not To Miss <not.to.miss@gmail.com>
I didn't remeber I had seen anything relevant in log files. Here is the most recent record in /var/log/messages files (I pressed reset button to reboot at Jul 15 20:37) with "-- MARK -- \" message lines skipped: Jul 14 20:36:15 phelps kernel: [111935.191008] PGD 10b42e067 PUD 0 Jul 14 20:36:15 phelps kernel: [111935.191011] Oops: 0000 [#1] PREEMPT SMP Jul 14 20:36:15 phelps kernel: [111935.191015] CPU 0 Jul 14 20:36:15 phelps kernel: [111935.191016] Modules linked in: fuse pci_stub vboxpci(O) vboxnetflt(O) vboxnetadp(O) vboxdrv(O) snd_hda_codec_realtek nvidia(PO) r8169 snd_hd a_intel snd_hda_codec snd_hwdep snd_pcm snd_page_alloc snd_timer snd soundcore microcode psmouse i2c_i801 serio_raw intel_agp processor pcspkr iTCO_wdt coretemp mii evdev inte l_gtt iTCO_vendor_support button i2c_core ext4 crc16 jbd2 mbcache raid0 raid456 async_raid6_recov async_memcpy async_pq async_xor xor async_tx raid6_pq raid1 md_mod sr_mod cdr om sd_mod usbhid pata_jmicron hid pata_acpi ahci libahci uhci_hcd ata_piix ata_generic ehci_hcd libata scsi_mod usbcore usb_common floppy Jul 14 20:36:15 phelps kernel: [111935.191057] Jul 14 20:36:15 phelps kernel: [111935.191059] Pid: 1373, comm: gnome-shell Tainted: P O 3.4.4-2-ARCH #1 Gigabyte Technology Co., Ltd. P35-DS3R/P35-DS3R Jul 14 20:36:15 phelps kernel: [111935.191063] RIP: 0010:[<ffffffffa06deb9e>] [<ffffffffa06deb9e>] _nv003990rm+0x4160/0xa790 [nvidia] Jul 14 20:36:15 phelps kernel: [111935.191186] RSP: 0018:ffff88010b6efa88 EFLAGS: 00010246 Jul 14 20:36:15 phelps kernel: [111935.191188] RAX: 00000000ffffffbb RBX: ffff88011742e008 RCX: 0000000000088004 Jul 14 20:36:15 phelps kernel: [111935.191190] RDX: ffff88011742e378 RSI: ffff88011742e008 RDI: 000000201875d808 Jul 14 20:36:15 phelps kernel: [111935.191192] RBP: ffff880118a8dfe0 R08: 0000000000000000 R09: ffff880118a8dfec Jul 14 20:36:15 phelps kernel: [111935.191194] R10: 0000000000000000 R11: 0000000000000001 R12: 0000000000088004 Jul 14 20:36:15 phelps kernel: [111935.191196] R13: 0000000000000000 R14: ffff88011742e378 R15: 0000000000000000 Jul 14 20:36:15 phelps kernel: [111935.191199] FS: 00007f8f3df8e940(0000) GS:ffff88011fc00000(0000) knlGS:0000000000000000 Jul 14 20:36:15 phelps kernel: [111935.191201] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 Jul 14 20:36:15 phelps kernel: [111935.191203] CR2: 000000201875dac0 CR3: 000000010b42b000 CR4: 00000000000007f0 Jul 14 20:36:15 phelps kernel: [111935.191205] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 Jul 14 20:36:15 phelps kernel: [111935.191208] DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400 Jul 14 20:36:15 phelps kernel: [111935.191210] Process gnome-shell (pid: 1373, threadinfo ffff88010b6ee000, task ffff8801103d7710) Jul 14 20:36:15 phelps kernel: [111935.191212] Stack: Jul 14 20:36:15 phelps kernel: [111935.191213] ffff88011742e008 ffff88011742e008 0000000000000000 0000000000088004 Jul 14 20:36:15 phelps kernel: [111935.191218] ffffc90005144008 ffffffffa06deaac ffff88011875f800 ffff88011742e008 Jul 14 20:36:15 phelps kernel: [111935.191222] 0000000000000000 ffff880118a8b000 ffffc90005144008 ffffffffa09067a1 Jul 14 20:36:15 phelps kernel: [111935.191226] Call Trace: Jul 14 20:36:15 phelps kernel: [111935.191347] [<ffffffffa06deaac>] ? _nv003990rm+0x406e/0xa790 [nvidia] Jul 14 20:36:15 phelps kernel: [111935.191400] [<ffffffffa09067a1>] ? rm_check_pci_config_space+0x499/0xa44 [nvidia] Jul 14 20:36:15 phelps kernel: [111935.191450] [<ffffffffa0921930>] ? nv_verify_pci_config+0x60/0x80 [nvidia] Jul 14 20:36:15 phelps kernel: [111935.191502] [<ffffffffa08fbaab>] ? _nv014590rm+0x22/0x27 [nvidia] Jul 14 20:36:15 phelps kernel: [111935.191553] [<ffffffffa09080f7>] ? _nv014633rm+0x31/0x538 [nvidia] Jul 14 20:36:15 phelps kernel: [111935.191675] [<ffffffffa06be7e3>] ? _nv009673rm+0xf7/0x134 [nvidia] Jul 14 20:36:15 phelps kernel: [111935.191795] [<ffffffffa06df156>] ? _nv003990rm+0x4718/0xa790 [nvidia] Jul 14 20:36:15 phelps kernel: [111935.191846] [<ffffffffa0906bdf>] ? rm_check_pci_config_space+0x8d7/0xa44 [nvidia] Jul 14 20:36:15 phelps kernel: [111935.191915] [<ffffffffa0360736>] ? _nv014429rm+0x9/0x21 [nvidia] Jul 14 20:36:15 phelps kernel: [111935.191964] [<ffffffffa0921930>] ? nv_verify_pci_config+0x60/0x80 [nvidia] Jul 14 20:36:15 phelps kernel: [111935.192015] [<ffffffffa08fbaab>] ? _nv014590rm+0x22/0x27 [nvidia] Jul 14 20:36:15 phelps kernel: [111935.192078] [<ffffffffa031eefa>] ? _nv000529rm+0x62/0x98 [nvidia] Jul 14 20:36:15 phelps kernel: [111935.192146] [<ffffffffa03639a2>] ? _nv016127rm+0x2c/0x67 [nvidia] Jul 14 20:36:15 phelps kernel: [111935.192214] [<ffffffffa0362eaa>] ? _nv016521rm+0x14aa/0x14fb [nvidia] Jul 14 20:36:15 phelps kernel: [111935.192282] [<ffffffffa0363458>] ? _nv016148rm+0x55d/0x58b [nvidia] Jul 14 20:36:15 phelps kernel: [111935.192349] [<ffffffffa0363495>] ? _nv001046rm+0xf/0x14 [nvidia] Jul 14 20:36:15 phelps kernel: [111935.192416] [<ffffffffa0348b2e>] ? _nv000945rm+0x31/0x59 [nvidia] Jul 14 20:36:15 phelps kernel: [111935.192470] [<ffffffffa08f6a2e>] ? _nv001095rm+0xa3e/0xa9f [nvidia] Jul 14 20:36:15 phelps kernel: [111935.192521] [<ffffffffa09035d0>] ? rm_ioctl+0x76/0xf3 [nvidia] Jul 14 20:36:15 phelps kernel: [111935.192570] [<ffffffffa0921e0e>] ? nv_kern_ioctl+0x15e/0x480 [nvidia] Jul 14 20:36:15 phelps kernel: [111935.192619] [<ffffffffa0922181>] ? nv_kern_unlocked_ioctl+0x21/0x30 [nvidia] Jul 14 20:36:15 phelps kernel: [111935.192624] [<ffffffff81180787>] ? do_vfs_ioctl+0x97/0x530 Jul 14 20:36:15 phelps kernel: [111935.192627] [<ffffffff81170097>] ? fget_light+0x97/0x100 Jul 14 20:36:15 phelps kernel: [111935.192630] [<ffffffff81180cb9>] ? sys_ioctl+0x99/0xa0 Jul 14 20:36:15 phelps kernel: [111935.192634] [<ffffffff8146a8e9>] ? system_call_fastpath+0x16/0x1b ul 14 20:36:15 phelps kernel: [111935.192636] Code: 20 00 00 00 44 89 f9 44 89 e2 44 89 ee 48 89 df e8 42 7d 00 00 f6 45 0c 02 75 16 45 89 f8 44 89 e1 4c 89 f2 48 89 de 48 8b 7d 00 <ff> 97 b8 02 00 00 48 83 c5 10 5b 41 5c 41 5d 41 5e 41 5f c3 41 Jul 14 20:36:15 phelps kernel: [111935.192788] RSP <ffff88010b6efa88> Jul 14 20:36:15 phelps kernel: [111935.192789] CR2: 000000201875dac0 Jul 14 20:36:15 phelps kernel: [111935.192821] ---[ end trace e8b17fa2032ffeeb ]--- ... Jul 15 13:31:45 phelps dhcpcd[873]: eth0: renewing lease of 172.18.200.52 Jul 15 13:31:45 phelps dhcpcd[873]: eth0: acknowledged 172.18.200.52 from 172.17.254.30 Jul 15 13:31:45 phelps dhcpcd[873]: eth0: leased 172.18.200.52 for 86400 seconds ... Jul 15 20:37:17 phelps kernel: [ 0.000000] Initializing cgroup subsys cpuset Jul 15 20:37:17 phelps kernel: [ 0.000000] Initializing cgroup subsys cpu Jul 15 20:37:17 phelps kernel: [ 0.000000] Linux version 3.4.4-2-ARCH (tobias@T-POWA-LX) (gcc version 4.7.1 (GCC) ) #1 SMP PREEMPT Sun Jun 24 18:59:47 CEST 2012 Jul 15 20:37:17 phelps kernel: [ 0.000000] Command line: root=/dev/md2 ro initrd=../initramfs-linux.img BOOT_IMAGE=../vmlinuz-linux Jul 15 20:37:17 phelps kernel: [ 0.000000] BIOS-provided physical RAM map: Jul 15 20:37:17 phelps kernel: [ 0.000000] BIOS-e820: 0000000000000000 - 000000000009f800 (usable) Jul 15 20:37:17 phelps kernel: [ 0.000000] BIOS-e820: 000000000009f800 - 00000000000a0000 (reserved) Jul 15 20:37:17 phelps kernel: [ 0.000000] BIOS-e820: 00000000000f0000 - 0000000000100000 (reserved) ...
These are the record from /var/log/errors: Jul 13 13:42:23 phelps kernel: [ 703.602239] end_request: I/O error, dev fd0, sector 0 Jul 13 13:42:23 phelps kernel: [ 703.602246] Buffer I/O error on device fd0, logical block 0 Jul 13 13:42:35 phelps kernel: [ 715.772126] end_request: I/O error, dev fd0, sector 0 Jul 13 13:42:35 phelps kernel: [ 715.772133] Buffer I/O error on device fd0, logical block 0 Jul 13 13:42:47 phelps kernel: [ 727.935544] end_request: I/O error, dev fd0, sector 0 Jul 13 13:42:47 phelps kernel: [ 727.935551] Buffer I/O error on device fd0, logical block 0 Jul 13 13:43:00 phelps kernel: [ 740.098959] end_request: I/O error, dev fd0, sector 0 Jul 13 13:43:00 phelps kernel: [ 740.098965] Buffer I/O error on device fd0, logical block 0 Jul 13 13:43:12 phelps kernel: [ 752.262394] end_request: I/O error, dev fd0, sector 0 Jul 13 13:43:12 phelps kernel: [ 752.262401] Buffer I/O error on device fd0, logical block 0 Jul 13 13:43:24 phelps kernel: [ 764.428886] end_request: I/O error, dev fd0, sector 0 Jul 13 13:43:24 phelps kernel: [ 764.428891] Buffer I/O error on device fd0, logical block 0 Jul 13 13:43:36 phelps kernel: [ 776.598318] end_request: I/O error, dev fd0, sector 0 Jul 13 13:43:48 phelps kernel: [ 788.758826] end_request: I/O error, dev fd0, sector 0 Jul 13 13:44:00 phelps kernel: [ 800.922217] end_request: I/O error, dev fd0, sector 2 Jul 13 13:44:00 phelps kernel: [ 800.922241] EXT4-fs (fd0): unable to read superblock Jul 13 13:44:13 phelps kernel: [ 813.089021] end_request: I/O error, dev fd0, sector 0 Jul 13 13:44:25 phelps kernel: [ 825.255519] end_request: I/O error, dev fd0, sector 2 Jul 13 13:44:25 phelps kernel: [ 825.255541] EXT4-fs (fd0): unable to read superblock Jul 13 13:44:37 phelps kernel: [ 837.435621] end_request: I/O error, dev fd0, sector 0 Jul 13 13:44:49 phelps kernel: [ 849.602125] end_request: I/O error, dev fd0, sector 2 Jul 13 13:44:49 phelps kernel: [ 849.602143] EXT4-fs (fd0): unable to read superblock Jul 13 13:45:01 phelps kernel: [ 861.778900] end_request: I/O error, dev fd0, sector 0
Thanks a lot for your help.
On Sun, Jul 15, 2012 at 11:15 PM, Victor Silva <vfbsilva@gmail.com> wrote:
2012/7/15 Not To Miss <not.to.miss@gmail.com>
Dear Arch users,
I have latest Arch installed on my desktop at work. In recent two weeks, the system randomly "suspends" at night (I call it "randomly" because it didn't happen every night. And it seems to happen after a random period idle time) when I am off. I can't wake it up in the next morning thru mouse or keyboard.
I tried to disable suspension and hibernation by editing /usr/share/polkit-1/actions/org.freedesktop.upower.policy to change from <allow_active>yes</allow_active> to <allow_active>no</allow_active>
But it doesn't work.
While I call it "suspend", I am not sure it suspend to RAM or hibernate to disk, because I find the CPU fan and power fan still spin normally. RAM light is also on. So it might be a video driver / setting related issue. For your information, I am using nvidia-302.17-2-x86_64 and have dual monitor set up with nvidia-utils-302.17-1-x86_64
This really bothers me a lot. Any help is appreciated. Thanks!
-- Best, Zech
Any hint on /var/log/messages or /var/log/errors?
-- Best, Zech
Don't think it is related but... http://superuser.com/questions/141770/ubuntu-login-takes-15-seconds-i-o-erro...
Thanks. I don't think it is related either. But perhaps I should fix that floppy error anyway Another thing I want to mention is that the screen jitters occasionally and when I lock the screen, only one monitor turns black while the other is still displaying with keyboard disabled but mouse still working. On Sun, Jul 15, 2012 at 11:49 PM, Victor Silva <vfbsilva@gmail.com> wrote:
2012/7/16 Not To Miss <not.to.miss@gmail.com>
I didn't remeber I had seen anything relevant in log files. Here is the most recent record in /var/log/messages files (I pressed reset button to reboot at Jul 15 20:37) with "-- MARK -- \" message lines skipped: Jul 14 20:36:15 phelps kernel: [111935.191008] PGD 10b42e067 PUD 0 Jul 14 20:36:15 phelps kernel: [111935.191011] Oops: 0000 [#1] PREEMPT SMP Jul 14 20:36:15 phelps kernel: [111935.191015] CPU 0 Jul 14 20:36:15 phelps kernel: [111935.191016] Modules linked in: fuse pci_stub vboxpci(O) vboxnetflt(O) vboxnetadp(O) vboxdrv(O) snd_hda_codec_realtek nvidia(PO) r8169 snd_hd a_intel snd_hda_codec snd_hwdep snd_pcm snd_page_alloc snd_timer snd soundcore microcode psmouse i2c_i801 serio_raw intel_agp processor pcspkr iTCO_wdt coretemp mii evdev inte l_gtt iTCO_vendor_support button i2c_core ext4 crc16 jbd2 mbcache raid0 raid456 async_raid6_recov async_memcpy async_pq async_xor xor async_tx raid6_pq raid1 md_mod sr_mod cdr om sd_mod usbhid pata_jmicron hid pata_acpi ahci libahci uhci_hcd ata_piix ata_generic ehci_hcd libata scsi_mod usbcore usb_common floppy Jul 14 20:36:15 phelps kernel: [111935.191057] Jul 14 20:36:15 phelps kernel: [111935.191059] Pid: 1373, comm: gnome-shell Tainted: P O 3.4.4-2-ARCH #1 Gigabyte Technology Co., Ltd. P35-DS3R/P35-DS3R Jul 14 20:36:15 phelps kernel: [111935.191063] RIP: 0010:[<ffffffffa06deb9e>] [<ffffffffa06deb9e>] _nv003990rm+0x4160/0xa790 [nvidia] Jul 14 20:36:15 phelps kernel: [111935.191186] RSP: 0018:ffff88010b6efa88 EFLAGS: 00010246 Jul 14 20:36:15 phelps kernel: [111935.191188] RAX: 00000000ffffffbb RBX: ffff88011742e008 RCX: 0000000000088004 Jul 14 20:36:15 phelps kernel: [111935.191190] RDX: ffff88011742e378 RSI: ffff88011742e008 RDI: 000000201875d808 Jul 14 20:36:15 phelps kernel: [111935.191192] RBP: ffff880118a8dfe0 R08: 0000000000000000 R09: ffff880118a8dfec Jul 14 20:36:15 phelps kernel: [111935.191194] R10: 0000000000000000 R11: 0000000000000001 R12: 0000000000088004 Jul 14 20:36:15 phelps kernel: [111935.191196] R13: 0000000000000000 R14: ffff88011742e378 R15: 0000000000000000 Jul 14 20:36:15 phelps kernel: [111935.191199] FS: 00007f8f3df8e940(0000) GS:ffff88011fc00000(0000) knlGS:0000000000000000 Jul 14 20:36:15 phelps kernel: [111935.191201] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 Jul 14 20:36:15 phelps kernel: [111935.191203] CR2: 000000201875dac0 CR3: 000000010b42b000 CR4: 00000000000007f0 Jul 14 20:36:15 phelps kernel: [111935.191205] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 Jul 14 20:36:15 phelps kernel: [111935.191208] DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400 Jul 14 20:36:15 phelps kernel: [111935.191210] Process gnome-shell (pid: 1373, threadinfo ffff88010b6ee000, task ffff8801103d7710) Jul 14 20:36:15 phelps kernel: [111935.191212] Stack: Jul 14 20:36:15 phelps kernel: [111935.191213] ffff88011742e008 ffff88011742e008 0000000000000000 0000000000088004 Jul 14 20:36:15 phelps kernel: [111935.191218] ffffc90005144008 ffffffffa06deaac ffff88011875f800 ffff88011742e008 Jul 14 20:36:15 phelps kernel: [111935.191222] 0000000000000000 ffff880118a8b000 ffffc90005144008 ffffffffa09067a1 Jul 14 20:36:15 phelps kernel: [111935.191226] Call Trace: Jul 14 20:36:15 phelps kernel: [111935.191347] [<ffffffffa06deaac>] ? _nv003990rm+0x406e/0xa790 [nvidia] Jul 14 20:36:15 phelps kernel: [111935.191400] [<ffffffffa09067a1>] ? rm_check_pci_config_space+0x499/0xa44 [nvidia] Jul 14 20:36:15 phelps kernel: [111935.191450] [<ffffffffa0921930>] ? nv_verify_pci_config+0x60/0x80 [nvidia] Jul 14 20:36:15 phelps kernel: [111935.191502] [<ffffffffa08fbaab>] ? _nv014590rm+0x22/0x27 [nvidia] Jul 14 20:36:15 phelps kernel: [111935.191553] [<ffffffffa09080f7>] ? _nv014633rm+0x31/0x538 [nvidia] Jul 14 20:36:15 phelps kernel: [111935.191675] [<ffffffffa06be7e3>] ? _nv009673rm+0xf7/0x134 [nvidia] Jul 14 20:36:15 phelps kernel: [111935.191795] [<ffffffffa06df156>] ? _nv003990rm+0x4718/0xa790 [nvidia] Jul 14 20:36:15 phelps kernel: [111935.191846] [<ffffffffa0906bdf>] ? rm_check_pci_config_space+0x8d7/0xa44 [nvidia] Jul 14 20:36:15 phelps kernel: [111935.191915] [<ffffffffa0360736>] ? _nv014429rm+0x9/0x21 [nvidia] Jul 14 20:36:15 phelps kernel: [111935.191964] [<ffffffffa0921930>] ? nv_verify_pci_config+0x60/0x80 [nvidia] Jul 14 20:36:15 phelps kernel: [111935.192015] [<ffffffffa08fbaab>] ? _nv014590rm+0x22/0x27 [nvidia] Jul 14 20:36:15 phelps kernel: [111935.192078] [<ffffffffa031eefa>] ? _nv000529rm+0x62/0x98 [nvidia] Jul 14 20:36:15 phelps kernel: [111935.192146] [<ffffffffa03639a2>] ? _nv016127rm+0x2c/0x67 [nvidia] Jul 14 20:36:15 phelps kernel: [111935.192214] [<ffffffffa0362eaa>] ? _nv016521rm+0x14aa/0x14fb [nvidia] Jul 14 20:36:15 phelps kernel: [111935.192282] [<ffffffffa0363458>] ? _nv016148rm+0x55d/0x58b [nvidia] Jul 14 20:36:15 phelps kernel: [111935.192349] [<ffffffffa0363495>] ? _nv001046rm+0xf/0x14 [nvidia] Jul 14 20:36:15 phelps kernel: [111935.192416] [<ffffffffa0348b2e>] ? _nv000945rm+0x31/0x59 [nvidia] Jul 14 20:36:15 phelps kernel: [111935.192470] [<ffffffffa08f6a2e>] ? _nv001095rm+0xa3e/0xa9f [nvidia] Jul 14 20:36:15 phelps kernel: [111935.192521] [<ffffffffa09035d0>] ? rm_ioctl+0x76/0xf3 [nvidia] Jul 14 20:36:15 phelps kernel: [111935.192570] [<ffffffffa0921e0e>] ? nv_kern_ioctl+0x15e/0x480 [nvidia] Jul 14 20:36:15 phelps kernel: [111935.192619] [<ffffffffa0922181>] ? nv_kern_unlocked_ioctl+0x21/0x30 [nvidia] Jul 14 20:36:15 phelps kernel: [111935.192624] [<ffffffff81180787>] ? do_vfs_ioctl+0x97/0x530 Jul 14 20:36:15 phelps kernel: [111935.192627] [<ffffffff81170097>] ? fget_light+0x97/0x100 Jul 14 20:36:15 phelps kernel: [111935.192630] [<ffffffff81180cb9>] ? sys_ioctl+0x99/0xa0 Jul 14 20:36:15 phelps kernel: [111935.192634] [<ffffffff8146a8e9>] ? system_call_fastpath+0x16/0x1b ul 14 20:36:15 phelps kernel: [111935.192636] Code: 20 00 00 00 44 89 f9 44 89 e2 44 89 ee 48 89 df e8 42 7d 00 00 f6 45 0c 02 75 16 45 89 f8 44 89 e1 4c 89 f2 48 89 de 48 8b 7d 00 <ff> 97 b8 02 00 00 48 83 c5 10 5b 41 5c 41 5d 41 5e 41 5f c3 41 Jul 14 20:36:15 phelps kernel: [111935.192788] RSP <ffff88010b6efa88> Jul 14 20:36:15 phelps kernel: [111935.192789] CR2: 000000201875dac0 Jul 14 20:36:15 phelps kernel: [111935.192821] ---[ end trace e8b17fa2032ffeeb ]--- ... Jul 15 13:31:45 phelps dhcpcd[873]: eth0: renewing lease of 172.18.200.52 Jul 15 13:31:45 phelps dhcpcd[873]: eth0: acknowledged 172.18.200.52 from 172.17.254.30 Jul 15 13:31:45 phelps dhcpcd[873]: eth0: leased 172.18.200.52 for 86400 seconds ... Jul 15 20:37:17 phelps kernel: [ 0.000000] Initializing cgroup subsys cpuset Jul 15 20:37:17 phelps kernel: [ 0.000000] Initializing cgroup subsys cpu Jul 15 20:37:17 phelps kernel: [ 0.000000] Linux version 3.4.4-2-ARCH (tobias@T-POWA-LX) (gcc version 4.7.1 (GCC) ) #1 SMP PREEMPT Sun Jun 24 18:59:47 CEST 2012 Jul 15 20:37:17 phelps kernel: [ 0.000000] Command line: root=/dev/md2 ro initrd=../initramfs-linux.img BOOT_IMAGE=../vmlinuz-linux Jul 15 20:37:17 phelps kernel: [ 0.000000] BIOS-provided physical RAM map: Jul 15 20:37:17 phelps kernel: [ 0.000000] BIOS-e820: 0000000000000000 - 000000000009f800 (usable) Jul 15 20:37:17 phelps kernel: [ 0.000000] BIOS-e820: 000000000009f800 - 00000000000a0000 (reserved) Jul 15 20:37:17 phelps kernel: [ 0.000000] BIOS-e820: 00000000000f0000 - 0000000000100000 (reserved) ...
These are the record from /var/log/errors: Jul 13 13:42:23 phelps kernel: [ 703.602239] end_request: I/O error, dev fd0, sector 0 Jul 13 13:42:23 phelps kernel: [ 703.602246] Buffer I/O error on device fd0, logical block 0 Jul 13 13:42:35 phelps kernel: [ 715.772126] end_request: I/O error, dev fd0, sector 0 Jul 13 13:42:35 phelps kernel: [ 715.772133] Buffer I/O error on device fd0, logical block 0 Jul 13 13:42:47 phelps kernel: [ 727.935544] end_request: I/O error, dev fd0, sector 0 Jul 13 13:42:47 phelps kernel: [ 727.935551] Buffer I/O error on device fd0, logical block 0 Jul 13 13:43:00 phelps kernel: [ 740.098959] end_request: I/O error, dev fd0, sector 0 Jul 13 13:43:00 phelps kernel: [ 740.098965] Buffer I/O error on device fd0, logical block 0 Jul 13 13:43:12 phelps kernel: [ 752.262394] end_request: I/O error, dev fd0, sector 0 Jul 13 13:43:12 phelps kernel: [ 752.262401] Buffer I/O error on device fd0, logical block 0 Jul 13 13:43:24 phelps kernel: [ 764.428886] end_request: I/O error, dev fd0, sector 0 Jul 13 13:43:24 phelps kernel: [ 764.428891] Buffer I/O error on device fd0, logical block 0 Jul 13 13:43:36 phelps kernel: [ 776.598318] end_request: I/O error, dev fd0, sector 0 Jul 13 13:43:48 phelps kernel: [ 788.758826] end_request: I/O error, dev fd0, sector 0 Jul 13 13:44:00 phelps kernel: [ 800.922217] end_request: I/O error, dev fd0, sector 2 Jul 13 13:44:00 phelps kernel: [ 800.922241] EXT4-fs (fd0): unable to read superblock Jul 13 13:44:13 phelps kernel: [ 813.089021] end_request: I/O error, dev fd0, sector 0 Jul 13 13:44:25 phelps kernel: [ 825.255519] end_request: I/O error, dev fd0, sector 2 Jul 13 13:44:25 phelps kernel: [ 825.255541] EXT4-fs (fd0): unable to read superblock Jul 13 13:44:37 phelps kernel: [ 837.435621] end_request: I/O error, dev fd0, sector 0 Jul 13 13:44:49 phelps kernel: [ 849.602125] end_request: I/O error, dev fd0, sector 2 Jul 13 13:44:49 phelps kernel: [ 849.602143] EXT4-fs (fd0): unable to read superblock Jul 13 13:45:01 phelps kernel: [ 861.778900] end_request: I/O error, dev fd0, sector 0
Thanks a lot for your help.
On Sun, Jul 15, 2012 at 11:15 PM, Victor Silva <vfbsilva@gmail.com> wrote:
2012/7/15 Not To Miss <not.to.miss@gmail.com>
Dear Arch users,
I have latest Arch installed on my desktop at work. In recent two weeks, the system randomly "suspends" at night (I call it "randomly" because it didn't happen every night. And it seems to happen after a random period idle time) when I am off. I can't wake it up in the next morning thru mouse or keyboard.
I tried to disable suspension and hibernation by editing /usr/share/polkit-1/actions/org.freedesktop.upower.policy to change from <allow_active>yes</allow_active> to <allow_active>no</allow_active>
But it doesn't work.
While I call it "suspend", I am not sure it suspend to RAM or hibernate to disk, because I find the CPU fan and power fan still spin normally. RAM light is also on. So it might be a video driver / setting related issue. For your information, I am using nvidia-302.17-2-x86_64 and have dual monitor set up with nvidia-utils-302.17-1-x86_64
This really bothers me a lot. Any help is appreciated. Thanks!
-- Best, Zech
Any hint on /var/log/messages or /var/log/errors?
-- Best, Zech
Don't think it is related but...
http://superuser.com/questions/141770/ubuntu-login-takes-15-seconds-i-o-erro...
-- Best, Zech
You certainly seem to have an OOPS related to the nvidia driver:
Call Trace: [<ffffffffa06deaac>] ? _nv003990rm+0x406e/0xa790 [nvidia]
And it looks like it is originated in the gnome-shell process. You can try switching to the fallback graphics mode (no gnome-shell) and see if it works normally. Regards. -- Rodrigo
How do I do that? When I choose fallback mode as Arch is booting up, I still enter gnome-shell. And sometimes it frozen upon startup when I enter this mode. On Mon, Jul 16, 2012 at 3:52 AM, Rodrigo Rivas <rodrigorivascosta@gmail.com>wrote:
You certainly seem to have an OOPS related to the nvidia driver:
Call Trace: [<ffffffffa06deaac>] ? _nv003990rm+0x406e/0xa790 [nvidia]
And it looks like it is originated in the gnome-shell process. You can try switching to the fallback graphics mode (no gnome-shell) and see if it works normally.
Regards. -- Rodrigo
-- Best, Zech
On Mon, Jul 16, 2012 at 3:45 PM, Not To Miss <not.to.miss@gmail.com> wrote:
How do I do that? When I choose fallback mode as Arch is booting up, I still enter gnome-shell. And sometimes it frozen upon startup when I enter this mode.
The official way is opening "gnome-control-center", and "Details" (in System section), select "Graphics" and then set "Forced Fallback Mode" to "ON". That should do it. But if it fails, as a workaround, you can simply remove the executable bit from (or rename) the file "/usr/bin/gnome-shell". -- Rodrigo
-----Mensaje original----- De: arch-general-bounces@archlinux.org [mailto:arch-general- bounces@archlinux.org] En nombre de Not To Miss Enviado el: lunes, 16 de julio de 2012 6:00 Para: General Discussion about Arch Linux Asunto: Re: [arch-general] my Arch box randomly becomes irresponsible
Thanks. I don't think it is related either. But perhaps I should fix that floppy error anyway
Another thing I want to mention is that the screen jitters occasionally and when I lock the screen, only one monitor turns black while the other is still displaying with keyboard disabled but mouse still working.
On Sun, Jul 15, 2012 at 11:49 PM, Victor Silva <vfbsilva@gmail.com> wrote:
2012/7/16 Not To Miss <not.to.miss@gmail.com>
I didn't remeber I had seen anything relevant in log files. Here is the most recent record in /var/log/messages files (I pressed reset button to reboot at Jul 15 20:37) with "-- MARK -- \" message lines skipped: Jul 14 20:36:15 phelps kernel: [111935.191008] PGD 10b42e067 PUD 0 Jul 14 20:36:15 phelps kernel: [111935.191011] Oops: 0000 [#1] PREEMPT Jul 13 13:45:01 phelps kernel: [ 861.778900] end_request: I/O error, dev fd0, sector 0
Thanks a lot for your help.
On Sun, Jul 15, 2012 at 11:15 PM, Victor Silva <vfbsilva@gmail.com> wrote:
2012/7/15 Not To Miss <not.to.miss@gmail.com>
Dear Arch users,
I have latest Arch installed on my desktop at work. In recent two weeks, the system randomly "suspends" at night (I call it "randomly" because it didn't happen every night. And it seems to happen after a random period idle time) when I am off. I can't wake it up in the next morning thru mouse or keyboard.
I tried to disable suspension and hibernation by editing /usr/share/polkit-1/actions/org.freedesktop.upower.policy to change from <allow_active>yes</allow_active> to <allow_active>no</allow_active>
But it doesn't work.
While I call it "suspend", I am not sure it suspend to RAM or hibernate to disk, because I find the CPU fan and power fan still spin normally. RAM light is also on. So it might be a video driver / setting related issue. For your information, I am using nvidia-302.17-2-x86_64 and have dual monitor set up with nvidia-utils-302.17-1-x86_64
This really bothers me a lot. Any help is appreciated. Thanks!
-- Best, Zech
Any hint on /var/log/messages or /var/log/errors?
-- Best, Zech
Don't think it is related but...
http://superuser.com/questions/141770/ubuntu-login-takes-15-seconds-i-o- error-dev-fd0-sector-0
I'm having exactly the same behavior, but I have Intel graphics. Are you using gnome? I don't know where or when this problem comes from. I have set the screensaver to shut down the screen after an hour of inactivity, and so reduce the times that it happens. If I left the computer for more than one hour, I have to press ctrl-alt-f1, and enter killall -HUP gnome-shell This restarts gnome-shell, but all the applications are still working. HTH Guillermo Leira
On Sun, Jul 15, 2012 at 10:46 PM, Not To Miss <not.to.miss@gmail.com> wrote:
I didn't remeber I had seen anything relevant in log files. Here is the most recent record in /var/log/messages files (I pressed reset button to reboot at Jul 15 20:37) with "-- MARK -- \" message lines skipped: Jul 14 20:36:15 phelps kernel: [111935.191008] PGD 10b42e067 PUD 0 Jul 14 20:36:15 phelps kernel: [111935.191011] Oops: 0000 [#1] PREEMPT SMP Jul 14 20:36:15 phelps kernel: [111935.191015] CPU 0 Jul 14 20:36:15 phelps kernel: [111935.191016] Modules linked in: fuse pci_stub vboxpci(O) vboxnetflt(O) vboxnetadp(O) vboxdrv(O) snd_hda_codec_realtek nvidia(PO) r8169 snd_hd a_intel snd_hda_codec snd_hwdep snd_pcm snd_page_alloc snd_timer snd soundcore microcode psmouse i2c_i801 serio_raw intel_agp processor pcspkr iTCO_wdt coretemp mii evdev inte l_gtt iTCO_vendor_support button i2c_core ext4 crc16 jbd2 mbcache raid0 raid456 async_raid6_recov async_memcpy async_pq async_xor xor async_tx raid6_pq raid1 md_mod sr_mod cdr om sd_mod usbhid pata_jmicron hid pata_acpi ahci libahci uhci_hcd ata_piix ata_generic ehci_hcd libata scsi_mod usbcore usb_common floppy Jul 14 20:36:15 phelps kernel: [111935.191057] Jul 14 20:36:15 phelps kernel: [111935.191059] Pid: 1373, comm: gnome-shell Tainted: P O 3.4.4-2-ARCH #1 Gigabyte Technology Co., Ltd. P35-DS3R/P35-DS3R Jul 14 20:36:15 phelps kernel: [111935.191063] RIP: 0010:[<ffffffffa06deb9e>] [<ffffffffa06deb9e>] _nv003990rm+0x4160/0xa790 [nvidia] Jul 14 20:36:15 phelps kernel: [111935.191186] RSP: 0018:ffff88010b6efa88 EFLAGS: 00010246 Jul 14 20:36:15 phelps kernel: [111935.191188] RAX: 00000000ffffffbb RBX: ffff88011742e008 RCX: 0000000000088004 Jul 14 20:36:15 phelps kernel: [111935.191190] RDX: ffff88011742e378 RSI: ffff88011742e008 RDI: 000000201875d808 Jul 14 20:36:15 phelps kernel: [111935.191192] RBP: ffff880118a8dfe0 R08: 0000000000000000 R09: ffff880118a8dfec Jul 14 20:36:15 phelps kernel: [111935.191194] R10: 0000000000000000 R11: 0000000000000001 R12: 0000000000088004 Jul 14 20:36:15 phelps kernel: [111935.191196] R13: 0000000000000000 R14: ffff88011742e378 R15: 0000000000000000 Jul 14 20:36:15 phelps kernel: [111935.191199] FS: 00007f8f3df8e940(0000) GS:ffff88011fc00000(0000) knlGS:0000000000000000 Jul 14 20:36:15 phelps kernel: [111935.191201] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 Jul 14 20:36:15 phelps kernel: [111935.191203] CR2: 000000201875dac0 CR3: 000000010b42b000 CR4: 00000000000007f0 Jul 14 20:36:15 phelps kernel: [111935.191205] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 Jul 14 20:36:15 phelps kernel: [111935.191208] DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400 Jul 14 20:36:15 phelps kernel: [111935.191210] Process gnome-shell (pid: 1373, threadinfo ffff88010b6ee000, task ffff8801103d7710) Jul 14 20:36:15 phelps kernel: [111935.191212] Stack: Jul 14 20:36:15 phelps kernel: [111935.191213] ffff88011742e008 ffff88011742e008 0000000000000000 0000000000088004 Jul 14 20:36:15 phelps kernel: [111935.191218] ffffc90005144008 ffffffffa06deaac ffff88011875f800 ffff88011742e008 Jul 14 20:36:15 phelps kernel: [111935.191222] 0000000000000000 ffff880118a8b000 ffffc90005144008 ffffffffa09067a1 Jul 14 20:36:15 phelps kernel: [111935.191226] Call Trace: Jul 14 20:36:15 phelps kernel: [111935.191347] [<ffffffffa06deaac>] ? _nv003990rm+0x406e/0xa790 [nvidia] Jul 14 20:36:15 phelps kernel: [111935.191400] [<ffffffffa09067a1>] ? rm_check_pci_config_space+0x499/0xa44 [nvidia] Jul 14 20:36:15 phelps kernel: [111935.191450] [<ffffffffa0921930>] ? nv_verify_pci_config+0x60/0x80 [nvidia] Jul 14 20:36:15 phelps kernel: [111935.191502] [<ffffffffa08fbaab>] ? _nv014590rm+0x22/0x27 [nvidia] Jul 14 20:36:15 phelps kernel: [111935.191553] [<ffffffffa09080f7>] ? _nv014633rm+0x31/0x538 [nvidia] Jul 14 20:36:15 phelps kernel: [111935.191675] [<ffffffffa06be7e3>] ? _nv009673rm+0xf7/0x134 [nvidia] Jul 14 20:36:15 phelps kernel: [111935.191795] [<ffffffffa06df156>] ? _nv003990rm+0x4718/0xa790 [nvidia] Jul 14 20:36:15 phelps kernel: [111935.191846] [<ffffffffa0906bdf>] ? rm_check_pci_config_space+0x8d7/0xa44 [nvidia] Jul 14 20:36:15 phelps kernel: [111935.191915] [<ffffffffa0360736>] ? _nv014429rm+0x9/0x21 [nvidia] Jul 14 20:36:15 phelps kernel: [111935.191964] [<ffffffffa0921930>] ? nv_verify_pci_config+0x60/0x80 [nvidia] Jul 14 20:36:15 phelps kernel: [111935.192015] [<ffffffffa08fbaab>] ? _nv014590rm+0x22/0x27 [nvidia] Jul 14 20:36:15 phelps kernel: [111935.192078] [<ffffffffa031eefa>] ? _nv000529rm+0x62/0x98 [nvidia] Jul 14 20:36:15 phelps kernel: [111935.192146] [<ffffffffa03639a2>] ? _nv016127rm+0x2c/0x67 [nvidia] Jul 14 20:36:15 phelps kernel: [111935.192214] [<ffffffffa0362eaa>] ? _nv016521rm+0x14aa/0x14fb [nvidia] Jul 14 20:36:15 phelps kernel: [111935.192282] [<ffffffffa0363458>] ? _nv016148rm+0x55d/0x58b [nvidia] Jul 14 20:36:15 phelps kernel: [111935.192349] [<ffffffffa0363495>] ? _nv001046rm+0xf/0x14 [nvidia] Jul 14 20:36:15 phelps kernel: [111935.192416] [<ffffffffa0348b2e>] ? _nv000945rm+0x31/0x59 [nvidia] Jul 14 20:36:15 phelps kernel: [111935.192470] [<ffffffffa08f6a2e>] ? _nv001095rm+0xa3e/0xa9f [nvidia] Jul 14 20:36:15 phelps kernel: [111935.192521] [<ffffffffa09035d0>] ? rm_ioctl+0x76/0xf3 [nvidia] Jul 14 20:36:15 phelps kernel: [111935.192570] [<ffffffffa0921e0e>] ? nv_kern_ioctl+0x15e/0x480 [nvidia] Jul 14 20:36:15 phelps kernel: [111935.192619] [<ffffffffa0922181>] ? nv_kern_unlocked_ioctl+0x21/0x30 [nvidia] Jul 14 20:36:15 phelps kernel: [111935.192624] [<ffffffff81180787>] ? do_vfs_ioctl+0x97/0x530 Jul 14 20:36:15 phelps kernel: [111935.192627] [<ffffffff81170097>] ? fget_light+0x97/0x100 Jul 14 20:36:15 phelps kernel: [111935.192630] [<ffffffff81180cb9>] ? sys_ioctl+0x99/0xa0 Jul 14 20:36:15 phelps kernel: [111935.192634] [<ffffffff8146a8e9>] ? system_call_fastpath+0x16/0x1b ul 14 20:36:15 phelps kernel: [111935.192636] Code: 20 00 00 00 44 89 f9 44 89 e2 44 89 ee 48 89 df e8 42 7d 00 00 f6 45 0c 02 75 16 45 89 f8 44 89 e1 4c 89 f2 48 89 de 48 8b 7d 00 <ff> 97 b8 02 00 00 48 83 c5 10 5b 41 5c 41 5d 41 5e 41 5f c3 41 Jul 14 20:36:15 phelps kernel: [111935.192788] RSP <ffff88010b6efa88> Jul 14 20:36:15 phelps kernel: [111935.192789] CR2: 000000201875dac0 Jul 14 20:36:15 phelps kernel: [111935.192821] ---[ end trace e8b17fa2032ffeeb ]--- ... Jul 15 13:31:45 phelps dhcpcd[873]: eth0: renewing lease of 172.18.200.52 Jul 15 13:31:45 phelps dhcpcd[873]: eth0: acknowledged 172.18.200.52 from 172.17.254.30 Jul 15 13:31:45 phelps dhcpcd[873]: eth0: leased 172.18.200.52 for 86400 seconds ... Jul 15 20:37:17 phelps kernel: [ 0.000000] Initializing cgroup subsys cpuset Jul 15 20:37:17 phelps kernel: [ 0.000000] Initializing cgroup subsys cpu Jul 15 20:37:17 phelps kernel: [ 0.000000] Linux version 3.4.4-2-ARCH (tobias@T-POWA-LX) (gcc version 4.7.1 (GCC) ) #1 SMP PREEMPT Sun Jun 24 18:59:47 CEST 2012 Jul 15 20:37:17 phelps kernel: [ 0.000000] Command line: root=/dev/md2 ro initrd=../initramfs-linux.img BOOT_IMAGE=../vmlinuz-linux Jul 15 20:37:17 phelps kernel: [ 0.000000] BIOS-provided physical RAM map: Jul 15 20:37:17 phelps kernel: [ 0.000000] BIOS-e820: 0000000000000000 - 000000000009f800 (usable) Jul 15 20:37:17 phelps kernel: [ 0.000000] BIOS-e820: 000000000009f800 - 00000000000a0000 (reserved) Jul 15 20:37:17 phelps kernel: [ 0.000000] BIOS-e820: 00000000000f0000 - 0000000000100000 (reserved) ...
These are the record from /var/log/errors: Jul 13 13:42:23 phelps kernel: [ 703.602239] end_request: I/O error, dev fd0, sector 0 Jul 13 13:42:23 phelps kernel: [ 703.602246] Buffer I/O error on device fd0, logical block 0 Jul 13 13:42:35 phelps kernel: [ 715.772126] end_request: I/O error, dev fd0, sector 0 Jul 13 13:42:35 phelps kernel: [ 715.772133] Buffer I/O error on device fd0, logical block 0 Jul 13 13:42:47 phelps kernel: [ 727.935544] end_request: I/O error, dev fd0, sector 0 Jul 13 13:42:47 phelps kernel: [ 727.935551] Buffer I/O error on device fd0, logical block 0 Jul 13 13:43:00 phelps kernel: [ 740.098959] end_request: I/O error, dev fd0, sector 0 Jul 13 13:43:00 phelps kernel: [ 740.098965] Buffer I/O error on device fd0, logical block 0 Jul 13 13:43:12 phelps kernel: [ 752.262394] end_request: I/O error, dev fd0, sector 0 Jul 13 13:43:12 phelps kernel: [ 752.262401] Buffer I/O error on device fd0, logical block 0 Jul 13 13:43:24 phelps kernel: [ 764.428886] end_request: I/O error, dev fd0, sector 0 Jul 13 13:43:24 phelps kernel: [ 764.428891] Buffer I/O error on device fd0, logical block 0 Jul 13 13:43:36 phelps kernel: [ 776.598318] end_request: I/O error, dev fd0, sector 0 Jul 13 13:43:48 phelps kernel: [ 788.758826] end_request: I/O error, dev fd0, sector 0 Jul 13 13:44:00 phelps kernel: [ 800.922217] end_request: I/O error, dev fd0, sector 2 Jul 13 13:44:00 phelps kernel: [ 800.922241] EXT4-fs (fd0): unable to read superblock Jul 13 13:44:13 phelps kernel: [ 813.089021] end_request: I/O error, dev fd0, sector 0 Jul 13 13:44:25 phelps kernel: [ 825.255519] end_request: I/O error, dev fd0, sector 2 Jul 13 13:44:25 phelps kernel: [ 825.255541] EXT4-fs (fd0): unable to read superblock Jul 13 13:44:37 phelps kernel: [ 837.435621] end_request: I/O error, dev fd0, sector 0 Jul 13 13:44:49 phelps kernel: [ 849.602125] end_request: I/O error, dev fd0, sector 2 Jul 13 13:44:49 phelps kernel: [ 849.602143] EXT4-fs (fd0): unable to read superblock Jul 13 13:45:01 phelps kernel: [ 861.778900] end_request: I/O error, dev fd0, sector 0
Thanks a lot for your help.
On Sun, Jul 15, 2012 at 11:15 PM, Victor Silva <vfbsilva@gmail.com> wrote:
2012/7/15 Not To Miss <not.to.miss@gmail.com>
Dear Arch users,
I have latest Arch installed on my desktop at work. In recent two weeks, the system randomly "suspends" at night (I call it "randomly" because it didn't happen every night. And it seems to happen after a random period idle time) when I am off. I can't wake it up in the next morning thru mouse or keyboard.
I tried to disable suspension and hibernation by editing /usr/share/polkit-1/actions/org.freedesktop.upower.policy to change from <allow_active>yes</allow_active> to <allow_active>no</allow_active>
But it doesn't work.
While I call it "suspend", I am not sure it suspend to RAM or hibernate to disk, because I find the CPU fan and power fan still spin normally. RAM light is also on. So it might be a video driver / setting related issue. For your information, I am using nvidia-302.17-2-x86_64 and have dual monitor set up with nvidia-utils-302.17-1-x86_64
This really bothers me a lot. Any help is appreciated. Thanks!
-- Best, Zech
Any hint on /var/log/messages or /var/log/errors?
-- Best, Zech
Zech: Not sure this will help or make you feel better. I noticed you are running a Gigabyte board, so am I. I started having trouble with suspend after some of the changes in udev. some other changes to accommodate systemd, and the progression of the 3.4 version of the kernel. I don't believe those changes are directly responsible for the problems but Gigabytes bios's are notoriously buggy. They are written for Windows and compiled with Microsoft's compiler not the Intel compiler. I've been hacking (well my version of stumbling) on this for about two weeks. Mine appears to be a problem with timing errors. Look through /var/log/everything.log and see if you can find any errors or warnings, or anything related to TSC. I would up changing my boot line to clocksource=HPET which helped in my case. Myra PS: Anyone know how to write a DSDT table? -- Life's fun when your sick and psychotic!
Hi Myra, Thanks. Those are related log lines in /var/log/everything: Jul 13 09:57:20 phelps kernel: [ 0.000000] Fast TSC calibration using PIT Jul 13 09:57:20 phelps kernel: [ 1.293370] Refined TSC clocksource calibration: 2399.999 MHz. Jul 13 09:57:20 phelps kernel: [ 1.293377] Switching to clocksource tsc Jul 13 09:57:24 phelps kernel: [ 54.168396] vboxdrv: TSC mode is 'synchronous', kernel timer mode is 'normal'. Do you see anything abnormal? How to add "clocksource=HPET" to boot line if that is the problem? On Mon, Jul 16, 2012 at 6:16 PM, Myra Nelson <myra.nelson@hughes.net> wrote:
On Sun, Jul 15, 2012 at 10:46 PM, Not To Miss <not.to.miss@gmail.com> wrote:
I didn't remeber I had seen anything relevant in log files. Here is the most recent record in /var/log/messages files (I pressed reset button to reboot at Jul 15 20:37) with "-- MARK -- \" message lines skipped: Jul 14 20:36:15 phelps kernel: [111935.191008] PGD 10b42e067 PUD 0 Jul 14 20:36:15 phelps kernel: [111935.191011] Oops: 0000 [#1] PREEMPT SMP Jul 14 20:36:15 phelps kernel: [111935.191015] CPU 0 Jul 14 20:36:15 phelps kernel: [111935.191016] Modules linked in: fuse pci_stub vboxpci(O) vboxnetflt(O) vboxnetadp(O) vboxdrv(O) snd_hda_codec_realtek nvidia(PO) r8169 snd_hd a_intel snd_hda_codec snd_hwdep snd_pcm snd_page_alloc snd_timer snd soundcore microcode psmouse i2c_i801 serio_raw intel_agp processor pcspkr iTCO_wdt coretemp mii evdev inte l_gtt iTCO_vendor_support button i2c_core ext4 crc16 jbd2 mbcache raid0 raid456 async_raid6_recov async_memcpy async_pq async_xor xor async_tx raid6_pq raid1 md_mod sr_mod cdr om sd_mod usbhid pata_jmicron hid pata_acpi ahci libahci uhci_hcd ata_piix ata_generic ehci_hcd libata scsi_mod usbcore usb_common floppy Jul 14 20:36:15 phelps kernel: [111935.191057] Jul 14 20:36:15 phelps kernel: [111935.191059] Pid: 1373, comm: gnome-shell Tainted: P O 3.4.4-2-ARCH #1 Gigabyte Technology Co., Ltd. P35-DS3R/P35-DS3R Jul 14 20:36:15 phelps kernel: [111935.191063] RIP: 0010:[<ffffffffa06deb9e>] [<ffffffffa06deb9e>] _nv003990rm+0x4160/0xa790 [nvidia] Jul 14 20:36:15 phelps kernel: [111935.191186] RSP: 0018:ffff88010b6efa88 EFLAGS: 00010246 Jul 14 20:36:15 phelps kernel: [111935.191188] RAX: 00000000ffffffbb RBX: ffff88011742e008 RCX: 0000000000088004 Jul 14 20:36:15 phelps kernel: [111935.191190] RDX: ffff88011742e378 RSI: ffff88011742e008 RDI: 000000201875d808 Jul 14 20:36:15 phelps kernel: [111935.191192] RBP: ffff880118a8dfe0 R08: 0000000000000000 R09: ffff880118a8dfec Jul 14 20:36:15 phelps kernel: [111935.191194] R10: 0000000000000000 R11: 0000000000000001 R12: 0000000000088004 Jul 14 20:36:15 phelps kernel: [111935.191196] R13: 0000000000000000 R14: ffff88011742e378 R15: 0000000000000000 Jul 14 20:36:15 phelps kernel: [111935.191199] FS: 00007f8f3df8e940(0000) GS:ffff88011fc00000(0000) knlGS:0000000000000000 Jul 14 20:36:15 phelps kernel: [111935.191201] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 Jul 14 20:36:15 phelps kernel: [111935.191203] CR2: 000000201875dac0 CR3: 000000010b42b000 CR4: 00000000000007f0 Jul 14 20:36:15 phelps kernel: [111935.191205] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 Jul 14 20:36:15 phelps kernel: [111935.191208] DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400 Jul 14 20:36:15 phelps kernel: [111935.191210] Process gnome-shell (pid: 1373, threadinfo ffff88010b6ee000, task ffff8801103d7710) Jul 14 20:36:15 phelps kernel: [111935.191212] Stack: Jul 14 20:36:15 phelps kernel: [111935.191213] ffff88011742e008 ffff88011742e008 0000000000000000 0000000000088004 Jul 14 20:36:15 phelps kernel: [111935.191218] ffffc90005144008 ffffffffa06deaac ffff88011875f800 ffff88011742e008 Jul 14 20:36:15 phelps kernel: [111935.191222] 0000000000000000 ffff880118a8b000 ffffc90005144008 ffffffffa09067a1 Jul 14 20:36:15 phelps kernel: [111935.191226] Call Trace: Jul 14 20:36:15 phelps kernel: [111935.191347] [<ffffffffa06deaac>] ? _nv003990rm+0x406e/0xa790 [nvidia] Jul 14 20:36:15 phelps kernel: [111935.191400] [<ffffffffa09067a1>] ? rm_check_pci_config_space+0x499/0xa44 [nvidia] Jul 14 20:36:15 phelps kernel: [111935.191450] [<ffffffffa0921930>] ? nv_verify_pci_config+0x60/0x80 [nvidia] Jul 14 20:36:15 phelps kernel: [111935.191502] [<ffffffffa08fbaab>] ? _nv014590rm+0x22/0x27 [nvidia] Jul 14 20:36:15 phelps kernel: [111935.191553] [<ffffffffa09080f7>] ? _nv014633rm+0x31/0x538 [nvidia] Jul 14 20:36:15 phelps kernel: [111935.191675] [<ffffffffa06be7e3>] ? _nv009673rm+0xf7/0x134 [nvidia] Jul 14 20:36:15 phelps kernel: [111935.191795] [<ffffffffa06df156>] ? _nv003990rm+0x4718/0xa790 [nvidia] Jul 14 20:36:15 phelps kernel: [111935.191846] [<ffffffffa0906bdf>] ? rm_check_pci_config_space+0x8d7/0xa44 [nvidia] Jul 14 20:36:15 phelps kernel: [111935.191915] [<ffffffffa0360736>] ? _nv014429rm+0x9/0x21 [nvidia] Jul 14 20:36:15 phelps kernel: [111935.191964] [<ffffffffa0921930>] ? nv_verify_pci_config+0x60/0x80 [nvidia] Jul 14 20:36:15 phelps kernel: [111935.192015] [<ffffffffa08fbaab>] ? _nv014590rm+0x22/0x27 [nvidia] Jul 14 20:36:15 phelps kernel: [111935.192078] [<ffffffffa031eefa>] ? _nv000529rm+0x62/0x98 [nvidia] Jul 14 20:36:15 phelps kernel: [111935.192146] [<ffffffffa03639a2>] ? _nv016127rm+0x2c/0x67 [nvidia] Jul 14 20:36:15 phelps kernel: [111935.192214] [<ffffffffa0362eaa>] ? _nv016521rm+0x14aa/0x14fb [nvidia] Jul 14 20:36:15 phelps kernel: [111935.192282] [<ffffffffa0363458>] ? _nv016148rm+0x55d/0x58b [nvidia] Jul 14 20:36:15 phelps kernel: [111935.192349] [<ffffffffa0363495>] ? _nv001046rm+0xf/0x14 [nvidia] Jul 14 20:36:15 phelps kernel: [111935.192416] [<ffffffffa0348b2e>] ? _nv000945rm+0x31/0x59 [nvidia] Jul 14 20:36:15 phelps kernel: [111935.192470] [<ffffffffa08f6a2e>] ? _nv001095rm+0xa3e/0xa9f [nvidia] Jul 14 20:36:15 phelps kernel: [111935.192521] [<ffffffffa09035d0>] ? rm_ioctl+0x76/0xf3 [nvidia] Jul 14 20:36:15 phelps kernel: [111935.192570] [<ffffffffa0921e0e>] ? nv_kern_ioctl+0x15e/0x480 [nvidia] Jul 14 20:36:15 phelps kernel: [111935.192619] [<ffffffffa0922181>] ? nv_kern_unlocked_ioctl+0x21/0x30 [nvidia] Jul 14 20:36:15 phelps kernel: [111935.192624] [<ffffffff81180787>] ? do_vfs_ioctl+0x97/0x530 Jul 14 20:36:15 phelps kernel: [111935.192627] [<ffffffff81170097>] ? fget_light+0x97/0x100 Jul 14 20:36:15 phelps kernel: [111935.192630] [<ffffffff81180cb9>] ? sys_ioctl+0x99/0xa0 Jul 14 20:36:15 phelps kernel: [111935.192634] [<ffffffff8146a8e9>] ? system_call_fastpath+0x16/0x1b ul 14 20:36:15 phelps kernel: [111935.192636] Code: 20 00 00 00 44 89 f9 44 89 e2 44 89 ee 48 89 df e8 42 7d 00 00 f6 45 0c 02 75 16 45 89 f8 44 89 e1 4c 89 f2 48 89 de 48 8b 7d 00 <ff> 97 b8 02 00 00 48 83 c5 10 5b 41 5c 41 5d 41 5e 41 5f c3 41 Jul 14 20:36:15 phelps kernel: [111935.192788] RSP <ffff88010b6efa88> Jul 14 20:36:15 phelps kernel: [111935.192789] CR2: 000000201875dac0 Jul 14 20:36:15 phelps kernel: [111935.192821] ---[ end trace e8b17fa2032ffeeb ]--- ... Jul 15 13:31:45 phelps dhcpcd[873]: eth0: renewing lease of 172.18.200.52 Jul 15 13:31:45 phelps dhcpcd[873]: eth0: acknowledged 172.18.200.52 from 172.17.254.30 Jul 15 13:31:45 phelps dhcpcd[873]: eth0: leased 172.18.200.52 for 86400 seconds ... Jul 15 20:37:17 phelps kernel: [ 0.000000] Initializing cgroup subsys cpuset Jul 15 20:37:17 phelps kernel: [ 0.000000] Initializing cgroup subsys cpu Jul 15 20:37:17 phelps kernel: [ 0.000000] Linux version 3.4.4-2-ARCH (tobias@T-POWA-LX) (gcc version 4.7.1 (GCC) ) #1 SMP PREEMPT Sun Jun 24 18:59:47 CEST 2012 Jul 15 20:37:17 phelps kernel: [ 0.000000] Command line: root=/dev/md2 ro initrd=../initramfs-linux.img BOOT_IMAGE=../vmlinuz-linux Jul 15 20:37:17 phelps kernel: [ 0.000000] BIOS-provided physical RAM map: Jul 15 20:37:17 phelps kernel: [ 0.000000] BIOS-e820: 0000000000000000 - 000000000009f800 (usable) Jul 15 20:37:17 phelps kernel: [ 0.000000] BIOS-e820: 000000000009f800 - 00000000000a0000 (reserved) Jul 15 20:37:17 phelps kernel: [ 0.000000] BIOS-e820: 00000000000f0000 - 0000000000100000 (reserved) ...
These are the record from /var/log/errors: Jul 13 13:42:23 phelps kernel: [ 703.602239] end_request: I/O error, dev fd0, sector 0 Jul 13 13:42:23 phelps kernel: [ 703.602246] Buffer I/O error on device fd0, logical block 0 Jul 13 13:42:35 phelps kernel: [ 715.772126] end_request: I/O error, dev fd0, sector 0 Jul 13 13:42:35 phelps kernel: [ 715.772133] Buffer I/O error on device fd0, logical block 0 Jul 13 13:42:47 phelps kernel: [ 727.935544] end_request: I/O error, dev fd0, sector 0 Jul 13 13:42:47 phelps kernel: [ 727.935551] Buffer I/O error on device fd0, logical block 0 Jul 13 13:43:00 phelps kernel: [ 740.098959] end_request: I/O error, dev fd0, sector 0 Jul 13 13:43:00 phelps kernel: [ 740.098965] Buffer I/O error on device fd0, logical block 0 Jul 13 13:43:12 phelps kernel: [ 752.262394] end_request: I/O error, dev fd0, sector 0 Jul 13 13:43:12 phelps kernel: [ 752.262401] Buffer I/O error on device fd0, logical block 0 Jul 13 13:43:24 phelps kernel: [ 764.428886] end_request: I/O error, dev fd0, sector 0 Jul 13 13:43:24 phelps kernel: [ 764.428891] Buffer I/O error on device fd0, logical block 0 Jul 13 13:43:36 phelps kernel: [ 776.598318] end_request: I/O error, dev fd0, sector 0 Jul 13 13:43:48 phelps kernel: [ 788.758826] end_request: I/O error, dev fd0, sector 0 Jul 13 13:44:00 phelps kernel: [ 800.922217] end_request: I/O error, dev fd0, sector 2 Jul 13 13:44:00 phelps kernel: [ 800.922241] EXT4-fs (fd0): unable to read superblock Jul 13 13:44:13 phelps kernel: [ 813.089021] end_request: I/O error, dev fd0, sector 0 Jul 13 13:44:25 phelps kernel: [ 825.255519] end_request: I/O error, dev fd0, sector 2 Jul 13 13:44:25 phelps kernel: [ 825.255541] EXT4-fs (fd0): unable to read superblock Jul 13 13:44:37 phelps kernel: [ 837.435621] end_request: I/O error, dev fd0, sector 0 Jul 13 13:44:49 phelps kernel: [ 849.602125] end_request: I/O error, dev fd0, sector 2 Jul 13 13:44:49 phelps kernel: [ 849.602143] EXT4-fs (fd0): unable to read superblock Jul 13 13:45:01 phelps kernel: [ 861.778900] end_request: I/O error, dev fd0, sector 0
Thanks a lot for your help.
On Sun, Jul 15, 2012 at 11:15 PM, Victor Silva <vfbsilva@gmail.com> wrote:
2012/7/15 Not To Miss <not.to.miss@gmail.com>
Dear Arch users,
I have latest Arch installed on my desktop at work. In recent two weeks, the system randomly "suspends" at night (I call it "randomly" because it didn't happen every night. And it seems to happen after a random period idle time) when I am off. I can't wake it up in the next morning thru mouse or keyboard.
I tried to disable suspension and hibernation by editing /usr/share/polkit-1/actions/org.freedesktop.upower.policy to change from <allow_active>yes</allow_active> to <allow_active>no</allow_active>
But it doesn't work.
While I call it "suspend", I am not sure it suspend to RAM or hibernate to disk, because I find the CPU fan and power fan still spin normally. RAM light is also on. So it might be a video driver / setting related issue. For your information, I am using nvidia-302.17-2-x86_64 and have dual monitor set up with nvidia-utils-302.17-1-x86_64
This really bothers me a lot. Any help is appreciated. Thanks!
-- Best, Zech
Any hint on /var/log/messages or /var/log/errors?
-- Best, Zech
Zech:
Not sure this will help or make you feel better. I noticed you are running a Gigabyte board, so am I. I started having trouble with suspend after some of the changes in udev. some other changes to accommodate systemd, and the progression of the 3.4 version of the kernel. I don't believe those changes are directly responsible for the problems but Gigabytes bios's are notoriously buggy. They are written for Windows and compiled with Microsoft's compiler not the Intel compiler. I've been hacking (well my version of stumbling) on this for about two weeks. Mine appears to be a problem with timing errors. Look through /var/log/everything.log and see if you can find any errors or warnings, or anything related to TSC. I would up changing my boot line to clocksource=HPET which helped in my case.
Myra
PS: Anyone know how to write a DSDT table?
-- Life's fun when your sick and psychotic!
-- Best, Zech
On Mon, Jul 16, 2012 at 5:30 PM, Not To Miss <not.to.miss@gmail.com> wrote:
Hi Myra,
Thanks. Those are related log lines in /var/log/everything: Jul 13 09:57:20 phelps kernel: [ 0.000000] Fast TSC calibration using PIT Jul 13 09:57:20 phelps kernel: [ 1.293370] Refined TSC clocksource calibration: 2399.999 MHz. Jul 13 09:57:20 phelps kernel: [ 1.293377] Switching to clocksource tsc Jul 13 09:57:24 phelps kernel: [ 54.168396] vboxdrv: TSC mode is 'synchronous', kernel timer mode is 'normal'.
Do you see anything abnormal?
How to add "clocksource=HPET" to boot line if that is the problem?
-- Best, Zech
Zech: Everything seems fine. Did you notice any other errors or warnings in /var/log/everything? This is for syslinux.cfg. I'm not sure how it would work in grub/grub2. append initrd=/initramfs-linux.img root=/dev/disk/by-uuid/067395a0-8575-4323-9cf6-3cf501b66547 rootflags=,relatime,user_xattr,barrier=1,data=ordered rootfstype=ext4 graphics=345 ipv6.disable_ipv6=1 clocksource=hpet Sorry I couldn't help. Myra Myra -- Life's fun when your sick and psychotic!
Am 16.07.2012 05:46, schrieb Not To Miss:
Jul 14 20:36:15 phelps kernel: [111935.191008] PGD 10b42e067 PUD 0 Jul 14 20:36:15 phelps kernel: [111935.191011] Oops: 0000 [#1] PREEMPT SMP Jul 14 20:36:15 phelps kernel: [111935.191015] CPU 0 Jul 14 20:36:15 phelps kernel: [111935.191016] Modules linked in: fuse pci_stub vboxpci(O) vboxnetflt(O) vboxnetadp(O) vboxdrv(O) snd_hda_codec_realtek nvidia(PO) r8169 snd_hd a_intel snd_hda_codec snd_hwdep snd_pcm snd_page_alloc snd_timer snd soundcore microcode psmouse i2c_i801 serio_raw intel_agp processor pcspkr iTCO_wdt coretemp mii evdev inte l_gtt iTCO_vendor_support button i2c_core ext4 crc16 jbd2 mbcache raid0 raid456 async_raid6_recov async_memcpy async_pq async_xor xor async_tx raid6_pq raid1 md_mod sr_mod cdr om sd_mod usbhid pata_jmicron hid pata_acpi ahci libahci uhci_hcd ata_piix ata_generic ehci_hcd libata scsi_mod usbcore usb_common floppy Jul 14 20:36:15 phelps kernel: [111935.191057] Jul 14 20:36:15 phelps kernel: [111935.191059] Pid: 1373, comm: gnome-shell Tainted: P O 3.4.4-2-ARCH #1 Gigabyte Technology Co., Ltd. P35-DS3R/P35-DS3R Jul 14 20:36:15 phelps kernel: [111935.191063] RIP: 0010:[<ffffffffa06deb9e>] [<ffffffffa06deb9e>] _nv003990rm+0x4160/0xa790 [nvidia]
This originates in the nvidia driver, so it is likely there is a bug there. Try if the problem still occurs with nouveau. There have been occasions where virtualbox causes weird errors in the kernel, so you could also try disabling the virtualbox modules - it is still more likely that nvidia is the problem.
Am Sun, 15 Jul 2012 22:06:01 -0400 schrieb Not To Miss <not.to.miss@gmail.com>:
Dear Arch users,
I have latest Arch installed on my desktop at work. In recent two weeks, the system randomly "suspends" at night (I call it "randomly" because it didn't happen every night. And it seems to happen after a random period idle time) when I am off. I can't wake it up in the next morning thru mouse or keyboard.
I tried to disable suspension and hibernation by editing /usr/share/polkit-1/actions/org.freedesktop.upower.policy to change from <allow_active>yes</allow_active> to <allow_active>no</allow_active>
But it doesn't work.
While I call it "suspend", I am not sure it suspend to RAM or hibernate to disk, because I find the CPU fan and power fan still spin normally. RAM light is also on. So it might be a video driver / setting related issue. For your information, I am using nvidia-302.17-2-x86_64 and have dual monitor set up with nvidia-utils-302.17-1-x86_64
This really bothers me a lot. Any help is appreciated. Thanks!
Another question, probably not related to this. What about SMP? Do you have a multi core CPU? And do you also have instabilities, probably including kernel panics, if you run tasks which use both cores under heavy load like compiling the kernel from ABS or converting videos e.g. ripping a DVD with HandBrake or something like that, particularly when X is running at the same time? Heiko
Yes, I am using quad core CPU. I don't have instabilities under heavy load. The only thing I saw is that the left one of my two screens jitter when I start wine. On Mon, Jul 16, 2012 at 6:06 AM, Heiko Baums <lists@baums-on-web.de> wrote:
Am Sun, 15 Jul 2012 22:06:01 -0400 schrieb Not To Miss <not.to.miss@gmail.com>:
Dear Arch users,
I have latest Arch installed on my desktop at work. In recent two weeks, the system randomly "suspends" at night (I call it "randomly" because it didn't happen every night. And it seems to happen after a random period idle time) when I am off. I can't wake it up in the next morning thru mouse or keyboard.
I tried to disable suspension and hibernation by editing /usr/share/polkit-1/actions/org.freedesktop.upower.policy to change from <allow_active>yes</allow_active> to <allow_active>no</allow_active>
But it doesn't work.
While I call it "suspend", I am not sure it suspend to RAM or hibernate to disk, because I find the CPU fan and power fan still spin normally. RAM light is also on. So it might be a video driver / setting related issue. For your information, I am using nvidia-302.17-2-x86_64 and have dual monitor set up with nvidia-utils-302.17-1-x86_64
This really bothers me a lot. Any help is appreciated. Thanks!
Another question, probably not related to this. What about SMP? Do you have a multi core CPU? And do you also have instabilities, probably including kernel panics, if you run tasks which use both cores under heavy load like compiling the kernel from ABS or converting videos e.g. ripping a DVD with HandBrake or something like that, particularly when X is running at the same time?
Heiko
-- Best, Zhenjiang
I tried to disable suspension and hibernation by editing /usr/share/polkit-1/actions/org.freedesktop.upower.policy to change from <allow_active>yes</allow_active> to <allow_active>no</allow_active>
But it doesn't work.
The polkit docs (you have to look at the source code) and configuration system are terrible and difficult to monitor to the point that I am switching all the code I need to the simple straight forward, transparent and more secure sudo. Atleast you get config files on arch though, you don't on Fedora (polkits home). Have you checked if suspend is still enabled with pkaction. -- ________________________________________________________ Why not do something good every day and install BOINC. ________________________________________________________
I didn't know the command pkaction. It's quite handy. Here are the output of the pkaction: $ pkaction | grep "\(hibernate\)\|\(suspend\)" -i org.freedesktop.upower.hibernate org.freedesktop.upower.suspend $ pkaction --action-id org.freedesktop.upower.suspend --verbose org.freedesktop.upower.suspend: description: Suspend the system message: Authentication is required to suspend the system vendor: The UPower Project vendor_url: http://upower.freedesktop.org/ icon: system-suspend implicit any: no implicit inactive: no implicit active: yes $ pkaction --action-id org.freedesktop.upower.hibernate --verbose org.freedesktop.upower.hibernate: description: Hibernate the system message: Authentication is required to hibernate the system vendor: The UPower Project vendor_url: http://upower.freedesktop.org/ icon: system-suspend implicit any: no implicit inactive: no implicit active: yes I think my current settings is overwritten by an most recent system update to "yes" now. But the problem exists no matter what setting that is. On Mon, Jul 16, 2012 at 6:43 AM, Kevin Chadwick <ma1l1ists@yahoo.co.uk>wrote:
I tried to disable suspension and hibernation by editing /usr/share/polkit-1/actions/org.freedesktop.upower.policy to change from <allow_active>yes</allow_active> to <allow_active>no</allow_active>
But it doesn't work.
The polkit docs (you have to look at the source code) and configuration system are terrible and difficult to monitor to the point that I am switching all the code I need to the simple straight forward, transparent and more secure sudo. Atleast you get config files on arch though, you don't on Fedora (polkits home).
Have you checked if suspend is still enabled with pkaction.
-- ________________________________________________________
Why not do something good every day and install BOINC. ________________________________________________________
-- Best, Zhenjiang
I think my current settings is overwritten by an most recent system update to "yes" now. But the problem exists no matter what setting that is.
If my memory serves try editing inside the directories in /etc/polkit-1, rather than /usr/share. I think there are some incorrect (/usr/share is usually reference) or distro specific guides on the net?. -- ________________________________________________________ Why not do something good every day and install BOINC. ________________________________________________________
I learned it from https://linuxexpresso.wordpress.com/2010/05/09/disable-suspend-and-hibernate... . It is different for Arch? There isn't anything related under /etc/polkit-1 directory: $ sudo ls -R .: localauthority localauthority.conf.d nullbackend.conf.d ./localauthority: 10-vendor.d 20-org.d 30-site.d 50-local.d 90-mandatory.d ./localauthority/10-vendor.d: ./localauthority/20-org.d: ./localauthority/30-site.d: ./localauthority/50-local.d: ./localauthority/90-mandatory.d: ./localauthority.conf.d: 50-localauthority.conf ./nullbackend.conf.d: 50-nullbackend.conf On Mon, Jul 16, 2012 at 11:14 AM, Kevin Chadwick <ma1l1ists@yahoo.co.uk>wrote:
I think my current settings is overwritten by an most recent system
update
to "yes" now. But the problem exists no matter what setting that is.
If my memory serves try editing inside the directories in /etc/polkit-1, rather than /usr/share.
I think there are some incorrect (/usr/share is usually reference) or distro specific guides on the net?.
-- ________________________________________________________
Why not do something good every day and install BOINC. ________________________________________________________
-- Best, Zhenjiang
I learned it from https://linuxexpresso.wordpress.com/2010/05/09/disable-suspend-and-hibernate... .
It is different for Arch?
There isn't anything related under /etc/polkit-1 directory: $ sudo ls -R .: localauthority localauthority.conf.d nullbackend.conf.d
./localauthority: 10-vendor.d 20-org.d 30-site.d 50-local.d 90-mandatory.d
./localauthority/10-vendor.d:
./localauthority/20-org.d:
./localauthority/30-site.d:
./localauthority/50-local.d:
Copy the file you set suspend inactive in to the 50-local.d folder with a .pkla extension. Now I've gained root and checked. I used org.freedesktop.consolekit.pkla before I disabled polkit all together. Now I remember I did that ages ago in my install scripts before forgetting I had copied those in. Far from intuitive. Tom pointed me to the man page pklocalauthority more recently that explains the folders. That might save you picking through the bones when you want the meat. Unfortunately you can't get to the steak without reading the source. With sudo and RBAC all you deal with is self explanatory steak and without the stringy IPC too. -- ________________________________________________________ Why not do something good every day and install BOINC. ________________________________________________________
@Not To Miss If you are using GRUB Legacy (the one that you can choose when installing a fresh Arch) all you have to do to add a parameter to the kernel is to edit /boot/grub/menu.cfg and add it to the kernel line. For example, this is a typical section of Arch's GRUB Legacy fresh menu.cfg: # (0) Arch Linux title Arch Linux root (hd0,1) kernel /boot/vmlinuz-linux root=/dev/sda2 ro initrd /boot/initramfs-linux.img lock then you add clocksource=HPET to the kernel line this way: kernel /boot/vmlinuz-linux root=/dev/sda2 ro clocksource=HPET (ro is just another kernel parameter that means "read-only") If you're using GRUB2 it's a whole different story. Since GRUB2 is a completely different boot-loader, redesigned from scratch to meet current cumputing requeriments, you first need to a edit /etc/default/grub file and add clocksource=HPET to the kernel line and the generate a new /boot/grub/grub.cfg file as explained in the wiki: https://wiki.archlinux.org/index.php/GRUB2 Regarding your video issue, I remember time back I too had a similar problem with a gigabyte-based computer (as pointed by Myra) running GNOME 2.32; what I can't remember if I used xset or vbetool to force turn on display and temporarily workaround the issue - actually may be both depending if I did turn on the monitor from an X console or from a tty. Anyway, both tools are in our repos so you can install them and try luck. @ PGD: "[...] and brings to mind pictures of your computer spending all your money, running an anonymous proxy without asking you, or maybe sending prank e-mails to your friends. Maybe you're dealing with a teenage computer? :p" Lol x'D, I almost died with "brings to mind pictures of your computer spending all your money" These are the kind of grammatical errors that happens to me too despite I try to speak a descent english ^_^ (and the type of corrections I thanks!) -- -msx
@Not To Miss If you are using GRUB Legacy (the one that you can choose when installing a fresh Arch) all you have to do to add a parameter to the kernel is to edit /boot/grub/menu.cfg and add it to the kernel line. For example, this is a typical section of Arch's GRUB Legacy fresh
I've updated Arch and all the observations I had before are amost gone (the jittering screen and one monitor can't be locked). But the problem of sporadic freezing is still happening. It's so annoying. I tried the boot flag "clocksource=HPET" suggested by Myra as following but it doesn't work: 53 LABEL arch 54 MENU LABEL Arch Linux 55 LINUX ../vmlinuz-linux 56 APPEND root=/dev/md2 ro modprobe.blacklist=floppy clocksource=HPET 57 INITRD ../initramfs-linux.img Here is the record in /var/log/everything.log just before it happened (these call stacks are logged sometimes, not every time it hangs): Aug 9 16:25:38 phelps kernel: [72554.912096] BUG: unable to handle kernel paging request at 0000002015f822c0 Aug 9 16:25:38 phelps kernel: [72554.912102] IP: [<ffffffffa06d9c48>] _nv004044rm+0x447f/0xae8b [nvidia] Aug 9 16:25:38 phelps kernel: [72554.912264] PGD 10fb0b067 PUD 0 Aug 9 16:25:38 phelps kernel: [72554.912267] Oops: 0000 [#1] PREEMPT SMP Aug 9 16:25:38 phelps kernel: [72554.912271] CPU 3 Aug 9 16:25:38 phelps kernel: [72554.912272] Modules linked in: fuse pci_stub vboxpci(O) vboxnetflt(O) vboxnetadp(O) vboxdrv(O) snd_hda_codec_realtek nvidia(PO) snd_hda_intel snd_hda_codec snd_hwdep snd_pcm snd_page_alloc snd_timer pcspkr serio_raw r8169 microcode evdev processor button i2c_i801 intel_agp coretemp i2c_core psmouse intel_gtt snd soun dcore iTCO_wdt iTCO_vendor_support mii ext4 crc16 jbd2 mbcache raid0 raid456 async_raid6_recov async_memcpy async_pq async_xor xor async_tx raid6_pq raid1 md_mod sr_mod usbhid hid cdrom sd_mod pata_jmicron pata_acpi ata_generic ata_piix uhci_hcd ahci libahci ehci_hcd libata scsi_mod usbcore usb_common Aug 9 16:25:38 phelps kernel: [72554.912314] Aug 9 16:25:38 phelps kernel: [72554.912316] Pid: 1637, comm: gnome-shell Tainted: P O 3.4.7-1-ARCH #1 Gigabyte Technology Co., Ltd. P35-DS3R/P35-DS3R Aug 9 16:25:38 phelps kernel: [72554.912320] RIP: 0010:[<ffffffffa06d9c48>] [<ffffffffa06d9c48>] _nv004044rm+0x447f/0xae8b [nvidia] Aug 9 16:25:38 phelps kernel: [72554.912445] RSP: 0018:ffff88010b779a68 EFLAGS: 00010246 Aug 9 16:25:38 phelps kernel: [72554.912447] RAX: 00000000ffffffbb RBX: ffff88010faa0008 RCX: 0000000000088004 Aug 9 16:25:38 phelps kernel: [72554.912449] RDX: ffff88010faa0380 RSI: ffff88010faa0008 RDI: 0000002015f82008 Aug 9 16:25:38 phelps kernel: [72554.912451] RBP: ffff880110e45fe0 R08: 0000000000000000 R09: ffff880110e45fec Aug 9 16:25:38 phelps kernel: [72554.912454] R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000088004 Aug 9 16:25:38 phelps kernel: [72554.912456] R13: 0000000000000000 R14: ffff88010faa0380 R15: 0000000000000000 Aug 9 16:25:38 phelps kernel: [72554.912458] FS: 00007ffc16a8d940(0000) GS:ffff88011fd80000(0000) knlGS:0000000000000000 Aug 9 16:25:38 phelps kernel: [72554.912461] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 Aug 9 16:25:38 phelps kernel: [72554.912463] CR2: 0000002015f822c0 CR3: 000000010fb08000 CR4: 00000000000027e0 Aug 9 16:25:38 phelps kernel: [72554.912465] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 Aug 9 16:25:38 phelps kernel: [72554.912467] DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400 Aug 9 16:25:38 phelps kernel: [72554.912469] Process gnome-shell (pid: 1637, threadinfo ffff88010b778000, task ffff8801188c3f80) Aug 9 16:25:38 phelps kernel: [72554.912471] Stack: Aug 9 16:25:38 phelps kernel: [72554.912472] ffff88010faa0008 ffff88010faa0008 0000000000000000 0000000000088004 Aug 9 16:25:38 phelps kernel: [72554.912477] ffffc90005084008 ffffffffa06d9b3c ffff880115f86000 ffff88010faa0008 Aug 9 16:25:38 phelps kernel: [72554.912481] 0000000000000000 ffff880110e43000 ffffc90005084008 ffffffffa0917c20 Aug 9 16:25:38 phelps kernel: [72554.912485] Call Trace: Aug 9 16:25:38 phelps kernel: [72554.912609] [<ffffffffa06d9b3c>] ? _nv004044rm+0x4373/0xae8b [nvidia] Aug 9 16:25:38 phelps kernel: [72554.912663] [<ffffffffa0917c20>] ? rm_check_pci_config_space+0x4f0/0xab9 [nvidia] Aug 9 16:25:38 phelps kernel: [72554.912714] [<ffffffffa0932c20>] ? nv_verify_pci_config+0x60/0x80 [nvidia] Aug 9 16:25:38 phelps kernel: [72554.912749] [<ffffffffa090d198>] ? _nv014810rm+0x22/0x27 [nvidia] Aug 9 16:25:38 phelps kernel: [72554.912749] [<ffffffffa0919472>] ? _nv014853rm+0x31/0x389 [nvidia] Aug 9 16:25:38 phelps kernel: [72554.912749] [<ffffffffa06b7ef3>] ? _nv009812rm+0xf7/0x13a [nvidia] Aug 9 16:25:38 phelps kernel: [72554.912749] [<ffffffffa06da24a>] ? _nv004044rm+0x4a81/0xae8b [nvidia] Aug 9 16:25:38 phelps kernel: [72554.912749] [<ffffffffa091806f>] ? rm_check_pci_config_space+0x93f/0xab9 [nvidia] Aug 9 16:25:38 phelps kernel: [72554.912749] [<ffffffff8115962e>] ? __kmalloc+0x2e/0x180 Aug 9 16:25:38 phelps kernel: [72554.912749] [<ffffffffa0932c20>] ? nv_verify_pci_config+0x60/0x80 [nvidia] Aug 9 16:25:38 phelps kernel: [72554.912749] [<ffffffffa090d198>] ? _nv014810rm+0x22/0x27 [nvidia] Aug 9 16:25:38 phelps kernel: [72554.912749] [<ffffffffa02fd1be>] ? _nv000535rm+0x62/0x98 [nvidia] Aug 9 16:25:38 phelps kernel: [72554.912749] [<ffffffffa034400a>] ? _nv016391rm+0x39/0x74 [nvidia] Aug 9 16:25:38 phelps kernel: [72554.912749] [<ffffffffa0343427>] ? _nv016929rm+0x1517/0x1568 [nvidia] Aug 9 16:25:38 phelps kernel: [72554.912749] [<ffffffffa03439f0>] ? _nv016412rm+0x578/0x5a6 [nvidia] Aug 9 16:25:38 phelps kernel: [72554.912749] [<ffffffffa0343a2d>] ? _nv001056rm+0xf/0x14 [nvidia] Aug 9 16:25:38 phelps kernel: [72554.912749] [<ffffffffa032887e>] ? _nv000955rm+0x31/0x59 [nvidia] Aug 9 16:25:38 phelps kernel: [72554.912749] [<ffffffffa09092ee>] ? _nv001106rm+0xa4e/0xaaf [nvidia] Aug 9 16:25:38 phelps kernel: [72554.912749] [<ffffffffa09147b6>] ? rm_ioctl+0x76/0x100 [nvidia] Aug 9 16:25:38 phelps kernel: [72554.912749] [<ffffffffa09330fe>] ? nv_kern_ioctl+0x15e/0x480 [nvidia] Aug 9 16:25:38 phelps kernel: [72554.912749] [<ffffffffa0933471>] ? nv_kern_unlocked_ioctl+0x21/0x30 [nvidia] Aug 9 16:25:38 phelps kernel: [72554.912749] [<ffffffff81180ab7>] ? do_vfs_ioctl+0x97/0x530 Aug 9 16:25:38 phelps kernel: [72554.912749] [<ffffffff81138b63>] ? do_munmap+0x1e3/0x3d0 Aug 9 16:25:38 phelps kernel: [72554.912749] [<ffffffff811703c7>] ? fget_light+0x97/0x100 Aug 9 16:25:38 phelps kernel: [72554.912749] [<ffffffff81180fe9>] ? sys_ioctl+0x99/0xa0 Aug 9 16:25:38 phelps kernel: [72554.912749] [<ffffffff810718a1>] ? posix_ktime_get_ts+0x11/0x20 Aug 9 16:25:38 phelps kernel: [72554.912749] [<ffffffff8146aaa9>] ? system_call_fastpath+0x16/0x1b Aug 9 16:25:38 phelps kernel: [72554.912749] Code: 20 00 00 00 44 89 f9 44 89 e2 44 89 ee 48 89 df e8 12 82 00 00 f6 45 0c 02 75 16 45 89 f8 44 89 e1 4c 89 f2 48 89 de 48 8b 7d 00 <ff> 97 b8 02 00 00 48 83 c5 10 5b 41 5c 41 5d 41 5e 41 5f c3 41 Aug 9 16:25:38 phelps kernel: [72554.912749] RIP [<ffffffffa06d9c48>] _nv004044rm+0x447f/0xae8b [nvidia] Aug 9 16:25:38 phelps kernel: [72554.912749] RSP <ffff88010b779a68> Aug 9 16:25:38 phelps kernel: [72554.912749] CR2: 0000002015f822c0 Aug 9 16:25:38 phelps kernel: [72554.914215] ---[ end trace e123ee6ee100cb2c ]--- I would REALLY appreciate it if someone knows what it's going on and how to fix it... On Tue, Jul 17, 2012 at 3:25 AM, Martin Cigorraga <msx@archlinux.us> wrote: menu.cfg:
# (0) Arch Linux title Arch Linux root (hd0,1) kernel /boot/vmlinuz-linux root=/dev/sda2 ro initrd /boot/initramfs-linux.img lock
then you add clocksource=HPET to the kernel line this way: kernel /boot/vmlinuz-linux root=/dev/sda2 ro clocksource=HPET (ro is just another kernel parameter that means "read-only")
If you're using GRUB2 it's a whole different story. Since GRUB2 is a completely different boot-loader, redesigned from scratch to meet current cumputing requeriments, you first need to a edit /etc/default/grub file and add clocksource=HPET to the kernel line and the generate a new /boot/grub/grub.cfg file as explained in the wiki: https://wiki.archlinux.org/index.php/GRUB2
Regarding your video issue, I remember time back I too had a similar problem with a gigabyte-based computer (as pointed by Myra) running GNOME 2.32; what I can't remember if I used xset or vbetool to force turn on display and temporarily workaround the issue - actually may be both depending if I did turn on the monitor from an X console or from a tty. Anyway, both tools are in our repos so you can install them and try luck.
@ PGD: "[...] and brings to mind pictures of your computer spending all your money, running an anonymous proxy without asking you, or maybe sending prank e-mails to your friends. Maybe you're dealing with a teenage computer? :p"
Lol x'D, I almost died with "brings to mind pictures of your computer spending all your money"
These are the kind of grammatical errors that happens to me too despite I try to speak a descent english ^_^ (and the type of corrections I thanks!)
-- -msx
-- Best, Zech
Not sure if it's any help, but it looks like your using virtualbox. I am also using it to run XP and ever since I started using the multiple monitor option in the XP virtual machine, it hasn't been as stable. I also use the Seamless mode, which causes some random graphics glitches. My system became un-responsive earlier today however, I was still able to CTRL+F1 to a virtual console and from their I had to init 3 and then init 5 to get my desktop back. I think this is a virtualbox issue. Squall -- Yesterday is history. Tomorrow is a mystery. Today is a gift. That's why its called the present. Headmaster Squall :: The Wired/Section-9 Close the world txen eht nepo $3R14L 3XP3R1M3NT$ #L41N http://twitter.com/headmastersqual
On Sunday 15 Jul 2012 22:06:01 Not To Miss wrote:
Dear Arch users,
I have latest Arch installed on my desktop at work. In recent two weeks, the system randomly "suspends" at night (I call it "randomly" because it didn't happen every night. And it seems to happen after a random period idle time) when I am off. I can't wake it up in the next morning thru mouse or keyboard.
I tried to disable suspension and hibernation by editing /usr/share/polkit-1/actions/org.freedesktop.upower.policy to change from <allow_active>yes</allow_active> to <allow_active>no</allow_active>
But it doesn't work.
While I call it "suspend", I am not sure it suspend to RAM or hibernate to disk, because I find the CPU fan and power fan still spin normally. RAM light is also on. So it might be a video driver / setting related issue. For your information, I am using nvidia-302.17-2-x86_64 and have dual monitor set up with nvidia-utils-302.17-1-x86_64
This really bothers me a lot. Any help is appreciated. Thanks!
Completely off-topic, but am I the only one that chuckled at this title? A very minor mistake, but "irresponsible" means "not responsible", and brings to mind pictures of your computer spending all your money, running an anonymous proxy without asking you, or maybe sending prank e-mails to your friends. Maybe you're dealing with a teenage computer? :p You meant to say "unresponsive", but we all understood what you meant to say. Paul
hah, excuse my poor English On Mon, Jul 16, 2012 at 7:03 AM, Paul Gideon Dann <pdgiddie@gmail.com>wrote:
On Sunday 15 Jul 2012 22:06:01 Not To Miss wrote:
Dear Arch users,
I have latest Arch installed on my desktop at work. In recent two weeks, the system randomly "suspends" at night (I call it "randomly" because it didn't happen every night. And it seems to happen after a random period idle time) when I am off. I can't wake it up in the next morning thru mouse or keyboard.
I tried to disable suspension and hibernation by editing /usr/share/polkit-1/actions/org.freedesktop.upower.policy to change from <allow_active>yes</allow_active> to <allow_active>no</allow_active>
But it doesn't work.
While I call it "suspend", I am not sure it suspend to RAM or hibernate to disk, because I find the CPU fan and power fan still spin normally. RAM light is also on. So it might be a video driver / setting related issue. For your information, I am using nvidia-302.17-2-x86_64 and have dual monitor set up with nvidia-utils-302.17-1-x86_64
This really bothers me a lot. Any help is appreciated. Thanks!
Completely off-topic, but am I the only one that chuckled at this title? A very minor mistake, but "irresponsible" means "not responsible", and brings to mind pictures of your computer spending all your money, running an anonymous proxy without asking you, or maybe sending prank e-mails to your friends. Maybe you're dealing with a teenage computer? :p
You meant to say "unresponsive", but we all understood what you meant to say.
Paul
-- Best, Zech
On Mon, Jul 16, 2012 at 12:03:35PM +0100, Paul Gideon Dann wrote:
Completely off-topic, but am I the only one that chuckled at this title? A very minor mistake, but "irresponsible" means "not responsible", and brings to mind pictures of your computer spending all your money, running an anonymous proxy without asking you, or maybe sending prank e-mails to your friends.
Or like this one: <http://questionablecontent.net/view.php?comic=2230> Ciao, -- FA A world of exhaustive, reliable metadata would be an utopia. It's also a pipe-dream, founded on self-delusion, nerd hubris and hysterically inflated market opportunities. (Cory Doctorow)
participants (12)
-
Fons Adriaensen
-
Guillermo Leira
-
Heiko Baums
-
Kevin Chadwick
-
Martin Cigorraga
-
Myra Nelson
-
Not To Miss
-
Paul Gideon Dann
-
Rodrigo Rivas
-
Squall Lionheart
-
Thomas Bächler
-
Victor Silva