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@xxxxxxxxxxxx> wrote: > @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 -- Best, Zech
