Re: [arch-general] my Arch box randomly becomes irresponsible
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 002015f822c0 Aug 9 16:25:38 phelps kernel: [72554.912102] IP: [a06d9c48] _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: [#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:[a06d9c48] [a06d9c48] _nv004044rm+0x447f/0xae8b [nvidia] Aug 9 16:25:38 phelps kernel: [72554.912445] RSP: 0018:88010b779a68 EFLAGS: 00010246 Aug 9 16:25:38 phelps kernel: [72554.912447] RAX: ffbb RBX: 88010faa0008 RCX: 00088004 Aug 9 16:25:38 phelps kernel: [72554.912449] RDX: 88010faa0380 RSI: 88010faa0008 RDI: 002015f82008 Aug 9 16:25:38 phelps kernel: [72554.912451] RBP: 880110e45fe0 R08: R09: 880110e45fec Aug 9 16:25:38 phelps kernel: [72554.912454] R10: R11: 0246 R12: 00088004 Aug 9 16:25:38 phelps kernel: [72554.912456] R13: R14: 88010faa0380 R15: Aug 9 16:25:38 phelps kernel: [72554.912458] FS: 7ffc16a8d940() GS:88011fd8() knlGS: Aug 9 16:25:38 phelps kernel: [72554.912461] CS: 0010 DS: ES: CR0: 80050033 Aug 9 16:25:38 phelps kernel: [72554.912463] CR2: 002015f822c0 CR3: 00010fb08000 CR4: 27e0 Aug 9 16:25:38 phelps kernel: [72554.912465] DR0: DR1: DR2: Aug 9 16:25:38 phelps kernel: [72554.912467] DR3: DR6: 0ff0 DR7: 0400 Aug 9 16:25:38 phelps kernel: [72554.912469] Process gnome-shell (pid: 1637, threadinfo 88010b778000, task 8801188c3f80) Aug 9 16:25:38 phelps kernel: [72554.912471] Stack: Aug 9 16:25:38 phelps kernel: [72554.912472] 88010faa0008 88010faa0008 00088004 Aug 9 16:25:38 phelps kernel: [72554.912477] c90005084008 a06d9b3c 880115f86000 88010faa0008 Aug 9 16:25:38 phelps kernel: [72554.912481] 880110e43000 c90005084008 a0917c20 Aug 9 16:25:38 phelps kernel: [72554.912485] Call Trace: Aug 9 16:25:38 phelps kernel: [72554.912609] [a06d9b3c] ? _nv004044rm+0x4373/0xae8b [nvidia] Aug 9 16:25:38 phelps kernel: [72554.912663] [a0917c20] ? rm_check_pci_config_space+0x4f0/0xab9 [nvidia] Aug 9 16:25:38 phelps kernel: [72554.912714] [a0932c20] ? nv_verify_pci_config+0x60/0x80 [nvidia] Aug 9 16:25:38 phelps kernel: [72554.912749] [a090d198] ? _nv014810rm+0x22/0x27 [nvidia] Aug 9 16:25:38 phelps kernel: [72554.912749] [a0919472] ? _nv014853rm+0x31/0x389 [nvidia] Aug 9 16:25:38 phelps kernel: [72554.912749] [a06b7ef3] ? _nv009812rm+0xf7/0x13a [nvidia] Aug 9 16:25:38 phelps kernel: [72554.912749] [a06da24a] ? _nv004044rm+0x4a81/0xae8b [nvidia] Aug 9 16:25:38 phelps kernel: [72554.912749] [a091806f] ? rm_check_pci_config_space+0x93f/0xab9 [nvidia] Aug 9 16:25:38 phelps kernel: [72554.912749] [8115962e] ? __kmalloc+0x2e/0x180 Aug 9 16:25:38 phelps kernel: [72554.912749] [a0932c20] ? nv_verify_pci_config+0x60/0x80 [nvidia] Aug 9 16:25:38 phelps kernel: [72554.912749] [a090d198] ? _nv014810rm+0x22/0x27 [nvidia] Aug 9 16:25:38 phelps kernel: [72554.912749]
Re: [arch-general] my Arch box randomly becomes irresponsible
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
Re: [arch-general] my Arch box randomly becomes irresponsible
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: [#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:[a06deb9e] [a06deb9e] _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. signature.asc Description: OpenPGP digital signature
Re: [arch-general] my Arch box randomly becomes irresponsible
@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
Re: [arch-general] my Arch box randomly becomes irresponsible
You certainly seem to have an OOPS related to the nvidia driver: Call Trace: [a06deaac] ? _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
Re: [arch-general] my Arch box randomly becomes irresponsible
-Mensaje original- De: arch-general-boun...@archlinux.org [mailto:arch-general- boun...@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 vfbsi...@gmail.com wrote: 2012/7/16 Not To Miss not.to.m...@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: [#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 vfbsi...@gmail.com wrote: 2012/7/15 Not To Miss not.to.m...@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_activeyes/allow_active to allow_activeno/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
Re: [arch-general] my Arch box randomly becomes irresponsible
I tried to disable suspension and hibernation by editing /usr/share/polkit-1/actions/org.freedesktop.upower.policy to change from allow_activeyes/allow_active to allow_activeno/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.
Re: [arch-general] my Arch box randomly becomes irresponsible
Am Sun, 15 Jul 2012 22:06:01 -0400 schrieb Not To Miss not.to.m...@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_activeyes/allow_active to allow_activeno/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
Re: [arch-general] my Arch box randomly becomes irresponsible
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_activeyes/allow_active to allow_activeno/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
Re: [arch-general] my Arch box randomly becomes irresponsible
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 ma1l1i...@yahoo.co.ukwrote: I tried to disable suspension and hibernation by editing /usr/share/polkit-1/actions/org.freedesktop.upower.policy to change from allow_activeyes/allow_active to allow_activeno/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
Re: [arch-general] my Arch box randomly becomes irresponsible
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 rodrigorivasco...@gmail.comwrote: You certainly seem to have an OOPS related to the nvidia driver: Call Trace: [a06deaac] ? _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
Re: [arch-general] my Arch box randomly becomes irresponsible
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.
Re: [arch-general] my Arch box randomly becomes irresponsible
On Mon, Jul 16, 2012 at 3:45 PM, Not To Miss not.to.m...@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
Re: [arch-general] my Arch box randomly becomes irresponsible
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 li...@baums-on-web.de wrote: Am Sun, 15 Jul 2012 22:06:01 -0400 schrieb Not To Miss not.to.m...@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_activeyes/allow_active to allow_activeno/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
Re: [arch-general] my Arch box randomly becomes irresponsible
hah, excuse my poor English On Mon, Jul 16, 2012 at 7:03 AM, Paul Gideon Dann pdgid...@gmail.comwrote: 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_activeyes/allow_active to allow_activeno/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
Re: [arch-general] my Arch box randomly becomes irresponsible
I learned it from https://linuxexpresso.wordpress.com/2010/05/09/disable-suspend-and-hibernate-ubuntu/ . It is different for Arch? There isn't anything related under /etc/polkit-1 directory: $ sudo ls -R .: localauthoritylocalauthority.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 ma1l1i...@yahoo.co.ukwrote: 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
Re: [arch-general] my Arch box randomly becomes irresponsible
On Sun, Jul 15, 2012 at 10:46 PM, Not To Miss not.to.m...@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: [#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:[a06deb9e] [a06deb9e] _nv003990rm+0x4160/0xa790 [nvidia] Jul 14 20:36:15 phelps kernel: [111935.191186] RSP: 0018:88010b6efa88 EFLAGS: 00010246 Jul 14 20:36:15 phelps kernel: [111935.191188] RAX: ffbb RBX: 88011742e008 RCX: 00088004 Jul 14 20:36:15 phelps kernel: [111935.191190] RDX: 88011742e378 RSI: 88011742e008 RDI: 00201875d808 Jul 14 20:36:15 phelps kernel: [111935.191192] RBP: 880118a8dfe0 R08: R09: 880118a8dfec Jul 14 20:36:15 phelps kernel: [111935.191194] R10: R11: 0001 R12: 00088004 Jul 14 20:36:15 phelps kernel: [111935.191196] R13: R14: 88011742e378 R15: Jul 14 20:36:15 phelps kernel: [111935.191199] FS: 7f8f3df8e940() GS:88011fc0() knlGS: Jul 14 20:36:15 phelps kernel: [111935.191201] CS: 0010 DS: ES: CR0: 80050033 Jul 14 20:36:15 phelps kernel: [111935.191203] CR2: 00201875dac0 CR3: 00010b42b000 CR4: 07f0 Jul 14 20:36:15 phelps kernel: [111935.191205] DR0: DR1: DR2: Jul 14 20:36:15 phelps kernel: [111935.191208] DR3: DR6: 0ff0 DR7: 0400 Jul 14 20:36:15 phelps kernel: [111935.191210] Process gnome-shell (pid: 1373, threadinfo 88010b6ee000, task 8801103d7710) Jul 14 20:36:15 phelps kernel: [111935.191212] Stack: Jul 14 20:36:15 phelps kernel: [111935.191213] 88011742e008 88011742e008 00088004 Jul 14 20:36:15 phelps kernel: [111935.191218] c90005144008 a06deaac 88011875f800 88011742e008 Jul 14 20:36:15 phelps kernel: [111935.191222] 880118a8b000 c90005144008 a09067a1 Jul 14 20:36:15 phelps kernel: [111935.191226] Call Trace: Jul 14 20:36:15 phelps kernel: [111935.191347] [a06deaac] ? _nv003990rm+0x406e/0xa790 [nvidia] Jul 14 20:36:15 phelps kernel: [111935.191400] [a09067a1] ? rm_check_pci_config_space+0x499/0xa44 [nvidia] Jul 14 20:36:15 phelps kernel: [111935.191450] [a0921930] ? nv_verify_pci_config+0x60/0x80 [nvidia] Jul 14 20:36:15 phelps kernel: [111935.191502] [a08fbaab] ? _nv014590rm+0x22/0x27 [nvidia] Jul 14 20:36:15 phelps kernel: [111935.191553] [a09080f7] ? _nv014633rm+0x31/0x538 [nvidia] Jul 14 20:36:15 phelps kernel: [111935.191675] [a06be7e3] ? _nv009673rm+0xf7/0x134 [nvidia] Jul 14 20:36:15 phelps kernel: [111935.191795] [a06df156] ? _nv003990rm+0x4718/0xa790 [nvidia] Jul 14 20:36:15 phelps kernel: [111935.191846] [a0906bdf] ? rm_check_pci_config_space+0x8d7/0xa44 [nvidia] Jul 14 20:36:15 phelps kernel: [111935.191915] [a0360736] ? _nv014429rm+0x9/0x21 [nvidia] Jul 14 20:36:15 phelps kernel: [111935.191964] [a0921930] ? nv_verify_pci_config+0x60/0x80 [nvidia] Jul 14 20:36:15 phelps kernel: [111935.192015] [a08fbaab] ? _nv014590rm+0x22/0x27 [nvidia] Jul 14 20:36:15 phelps kernel: [111935.192078] [a031eefa] ? _nv000529rm+0x62/0x98 [nvidia] Jul 14 20:36:15 phelps kernel: [111935.192146] [a03639a2] ? _nv016127rm+0x2c/0x67 [nvidia] Jul 14 20:36:15 phelps kernel: [111935.192214] [a0362eaa] ? _nv016521rm+0x14aa/0x14fb [nvidia] Jul 14 20:36:15 phelps kernel: [111935.192282] [a0363458] ? _nv016148rm+0x55d/0x58b [nvidia] Jul 14 20:36:15 phelps kernel: [111935.192349]
Re: [arch-general] my Arch box randomly becomes irresponsible
Hi Myra, Thanks. Those are related log lines in /var/log/everything: Jul 13 09:57:20 phelps kernel: [0.00] 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.nel...@hughes.net wrote: On Sun, Jul 15, 2012 at 10:46 PM, Not To Miss not.to.m...@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: [#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:[a06deb9e] [a06deb9e] _nv003990rm+0x4160/0xa790 [nvidia] Jul 14 20:36:15 phelps kernel: [111935.191186] RSP: 0018:88010b6efa88 EFLAGS: 00010246 Jul 14 20:36:15 phelps kernel: [111935.191188] RAX: ffbb RBX: 88011742e008 RCX: 00088004 Jul 14 20:36:15 phelps kernel: [111935.191190] RDX: 88011742e378 RSI: 88011742e008 RDI: 00201875d808 Jul 14 20:36:15 phelps kernel: [111935.191192] RBP: 880118a8dfe0 R08: R09: 880118a8dfec Jul 14 20:36:15 phelps kernel: [111935.191194] R10: R11: 0001 R12: 00088004 Jul 14 20:36:15 phelps kernel: [111935.191196] R13: R14: 88011742e378 R15: Jul 14 20:36:15 phelps kernel: [111935.191199] FS: 7f8f3df8e940() GS:88011fc0() knlGS: Jul 14 20:36:15 phelps kernel: [111935.191201] CS: 0010 DS: ES: CR0: 80050033 Jul 14 20:36:15 phelps kernel: [111935.191203] CR2: 00201875dac0 CR3: 00010b42b000 CR4: 07f0 Jul 14 20:36:15 phelps kernel: [111935.191205] DR0: DR1: DR2: Jul 14 20:36:15 phelps kernel: [111935.191208] DR3: DR6: 0ff0 DR7: 0400 Jul 14 20:36:15 phelps kernel: [111935.191210] Process gnome-shell (pid: 1373, threadinfo 88010b6ee000, task 8801103d7710) Jul 14 20:36:15 phelps kernel: [111935.191212] Stack: Jul 14 20:36:15 phelps kernel: [111935.191213] 88011742e008 88011742e008 00088004 Jul 14 20:36:15 phelps kernel: [111935.191218] c90005144008 a06deaac 88011875f800 88011742e008 Jul 14 20:36:15 phelps kernel: [111935.191222] 880118a8b000 c90005144008 a09067a1 Jul 14 20:36:15 phelps kernel: [111935.191226] Call Trace: Jul 14 20:36:15 phelps kernel: [111935.191347] [a06deaac] ? _nv003990rm+0x406e/0xa790 [nvidia] Jul 14 20:36:15 phelps kernel: [111935.191400] [a09067a1] ? rm_check_pci_config_space+0x499/0xa44 [nvidia] Jul 14 20:36:15 phelps kernel: [111935.191450] [a0921930] ? nv_verify_pci_config+0x60/0x80 [nvidia] Jul 14 20:36:15 phelps kernel: [111935.191502] [a08fbaab] ? _nv014590rm+0x22/0x27 [nvidia] Jul 14 20:36:15 phelps kernel: [111935.191553] [a09080f7] ? _nv014633rm+0x31/0x538 [nvidia] Jul 14 20:36:15 phelps kernel: [111935.191675] [a06be7e3] ? _nv009673rm+0xf7/0x134 [nvidia] Jul 14 20:36:15 phelps kernel: [111935.191795] [a06df156] ? _nv003990rm+0x4718/0xa790 [nvidia] Jul 14 20:36:15 phelps kernel: [111935.191846] [a0906bdf] ? rm_check_pci_config_space+0x8d7/0xa44 [nvidia] Jul 14 20:36:15 phelps kernel: [111935.191915] [a0360736] ? _nv014429rm+0x9/0x21
[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_activeyes/allow_active to allow_activeno/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
Re: [arch-general] my Arch box randomly becomes irresponsible
2012/7/15 Not To Miss not.to.m...@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_activeyes/allow_active to allow_activeno/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?
Re: [arch-general] my Arch box randomly becomes irresponsible
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: [#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:[a06deb9e] [a06deb9e] _nv003990rm+0x4160/0xa790 [nvidia] Jul 14 20:36:15 phelps kernel: [111935.191186] RSP: 0018:88010b6efa88 EFLAGS: 00010246 Jul 14 20:36:15 phelps kernel: [111935.191188] RAX: ffbb RBX: 88011742e008 RCX: 00088004 Jul 14 20:36:15 phelps kernel: [111935.191190] RDX: 88011742e378 RSI: 88011742e008 RDI: 00201875d808 Jul 14 20:36:15 phelps kernel: [111935.191192] RBP: 880118a8dfe0 R08: R09: 880118a8dfec Jul 14 20:36:15 phelps kernel: [111935.191194] R10: R11: 0001 R12: 00088004 Jul 14 20:36:15 phelps kernel: [111935.191196] R13: R14: 88011742e378 R15: Jul 14 20:36:15 phelps kernel: [111935.191199] FS: 7f8f3df8e940() GS:88011fc0() knlGS: Jul 14 20:36:15 phelps kernel: [111935.191201] CS: 0010 DS: ES: CR0: 80050033 Jul 14 20:36:15 phelps kernel: [111935.191203] CR2: 00201875dac0 CR3: 00010b42b000 CR4: 07f0 Jul 14 20:36:15 phelps kernel: [111935.191205] DR0: DR1: DR2: Jul 14 20:36:15 phelps kernel: [111935.191208] DR3: DR6: 0ff0 DR7: 0400 Jul 14 20:36:15 phelps kernel: [111935.191210] Process gnome-shell (pid: 1373, threadinfo 88010b6ee000, task 8801103d7710) Jul 14 20:36:15 phelps kernel: [111935.191212] Stack: Jul 14 20:36:15 phelps kernel: [111935.191213] 88011742e008 88011742e008 00088004 Jul 14 20:36:15 phelps kernel: [111935.191218] c90005144008 a06deaac 88011875f800 88011742e008 Jul 14 20:36:15 phelps kernel: [111935.191222] 880118a8b000 c90005144008 a09067a1 Jul 14 20:36:15 phelps kernel: [111935.191226] Call Trace: Jul 14 20:36:15 phelps kernel: [111935.191347] [a06deaac] ? _nv003990rm+0x406e/0xa790 [nvidia] Jul 14 20:36:15 phelps kernel: [111935.191400] [a09067a1] ? rm_check_pci_config_space+0x499/0xa44 [nvidia] Jul 14 20:36:15 phelps kernel: [111935.191450] [a0921930] ? nv_verify_pci_config+0x60/0x80 [nvidia] Jul 14 20:36:15 phelps kernel: [111935.191502] [a08fbaab] ? _nv014590rm+0x22/0x27 [nvidia] Jul 14 20:36:15 phelps kernel: [111935.191553] [a09080f7] ? _nv014633rm+0x31/0x538 [nvidia] Jul 14 20:36:15 phelps kernel: [111935.191675] [a06be7e3] ? _nv009673rm+0xf7/0x134 [nvidia] Jul 14 20:36:15 phelps kernel: [111935.191795] [a06df156] ? _nv003990rm+0x4718/0xa790 [nvidia] Jul 14 20:36:15 phelps kernel: [111935.191846] [a0906bdf] ? rm_check_pci_config_space+0x8d7/0xa44 [nvidia] Jul 14 20:36:15 phelps kernel: [111935.191915] [a0360736] ? _nv014429rm+0x9/0x21 [nvidia] Jul 14 20:36:15 phelps kernel: [111935.191964] [a0921930] ? nv_verify_pci_config+0x60/0x80 [nvidia] Jul 14 20:36:15 phelps kernel: [111935.192015] [a08fbaab] ? _nv014590rm+0x22/0x27 [nvidia] Jul 14 20:36:15 phelps kernel: [111935.192078] [a031eefa] ? _nv000529rm+0x62/0x98 [nvidia] Jul 14 20:36:15 phelps kernel: [111935.192146] [a03639a2] ? _nv016127rm+0x2c/0x67 [nvidia] Jul 14 20:36:15 phelps kernel: [111935.192214] [a0362eaa] ? _nv016521rm+0x14aa/0x14fb [nvidia] Jul 14 20:36:15 phelps kernel: [111935.192282] [a0363458] ? _nv016148rm+0x55d/0x58b [nvidia] Jul 14 20:36:15 phelps kernel: [111935.192349] [a0363495] ? _nv001046rm+0xf/0x14 [nvidia] Jul 14 20:36:15 phelps kernel: [111935.192416] [a0348b2e] ? _nv000945rm+0x31/0x59 [nvidia] Jul 14
Re: [arch-general] my Arch box randomly becomes irresponsible
2012/7/16 Not To Miss not.to.m...@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: [#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:[a06deb9e] [a06deb9e] _nv003990rm+0x4160/0xa790 [nvidia] Jul 14 20:36:15 phelps kernel: [111935.191186] RSP: 0018:88010b6efa88 EFLAGS: 00010246 Jul 14 20:36:15 phelps kernel: [111935.191188] RAX: ffbb RBX: 88011742e008 RCX: 00088004 Jul 14 20:36:15 phelps kernel: [111935.191190] RDX: 88011742e378 RSI: 88011742e008 RDI: 00201875d808 Jul 14 20:36:15 phelps kernel: [111935.191192] RBP: 880118a8dfe0 R08: R09: 880118a8dfec Jul 14 20:36:15 phelps kernel: [111935.191194] R10: R11: 0001 R12: 00088004 Jul 14 20:36:15 phelps kernel: [111935.191196] R13: R14: 88011742e378 R15: Jul 14 20:36:15 phelps kernel: [111935.191199] FS: 7f8f3df8e940() GS:88011fc0() knlGS: Jul 14 20:36:15 phelps kernel: [111935.191201] CS: 0010 DS: ES: CR0: 80050033 Jul 14 20:36:15 phelps kernel: [111935.191203] CR2: 00201875dac0 CR3: 00010b42b000 CR4: 07f0 Jul 14 20:36:15 phelps kernel: [111935.191205] DR0: DR1: DR2: Jul 14 20:36:15 phelps kernel: [111935.191208] DR3: DR6: 0ff0 DR7: 0400 Jul 14 20:36:15 phelps kernel: [111935.191210] Process gnome-shell (pid: 1373, threadinfo 88010b6ee000, task 8801103d7710) Jul 14 20:36:15 phelps kernel: [111935.191212] Stack: Jul 14 20:36:15 phelps kernel: [111935.191213] 88011742e008 88011742e008 00088004 Jul 14 20:36:15 phelps kernel: [111935.191218] c90005144008 a06deaac 88011875f800 88011742e008 Jul 14 20:36:15 phelps kernel: [111935.191222] 880118a8b000 c90005144008 a09067a1 Jul 14 20:36:15 phelps kernel: [111935.191226] Call Trace: Jul 14 20:36:15 phelps kernel: [111935.191347] [a06deaac] ? _nv003990rm+0x406e/0xa790 [nvidia] Jul 14 20:36:15 phelps kernel: [111935.191400] [a09067a1] ? rm_check_pci_config_space+0x499/0xa44 [nvidia] Jul 14 20:36:15 phelps kernel: [111935.191450] [a0921930] ? nv_verify_pci_config+0x60/0x80 [nvidia] Jul 14 20:36:15 phelps kernel: [111935.191502] [a08fbaab] ? _nv014590rm+0x22/0x27 [nvidia] Jul 14 20:36:15 phelps kernel: [111935.191553] [a09080f7] ? _nv014633rm+0x31/0x538 [nvidia] Jul 14 20:36:15 phelps kernel: [111935.191675] [a06be7e3] ? _nv009673rm+0xf7/0x134 [nvidia] Jul 14 20:36:15 phelps kernel: [111935.191795] [a06df156] ? _nv003990rm+0x4718/0xa790 [nvidia] Jul 14 20:36:15 phelps kernel: [111935.191846] [a0906bdf] ? rm_check_pci_config_space+0x8d7/0xa44 [nvidia] Jul 14 20:36:15 phelps kernel: [111935.191915] [a0360736] ? _nv014429rm+0x9/0x21 [nvidia] Jul 14 20:36:15 phelps kernel: [111935.191964] [a0921930] ? nv_verify_pci_config+0x60/0x80 [nvidia] Jul 14 20:36:15 phelps kernel: [111935.192015] [a08fbaab] ? _nv014590rm+0x22/0x27 [nvidia] Jul 14 20:36:15 phelps kernel: [111935.192078] [a031eefa] ? _nv000529rm+0x62/0x98 [nvidia] Jul 14 20:36:15 phelps kernel: [111935.192146] [a03639a2] ? _nv016127rm+0x2c/0x67 [nvidia] Jul 14 20:36:15 phelps kernel: [111935.192214] [a0362eaa] ? _nv016521rm+0x14aa/0x14fb [nvidia] Jul 14 20:36:15 phelps kernel: [111935.192282] [a0363458] ? _nv016148rm+0x55d/0x58b [nvidia] Jul 14 20:36:15 phelps kernel: [111935.192349] [a0363495] ?
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 vfbsi...@gmail.com wrote: 2012/7/16 Not To Miss not.to.m...@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: [#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:[a06deb9e] [a06deb9e] _nv003990rm+0x4160/0xa790 [nvidia] Jul 14 20:36:15 phelps kernel: [111935.191186] RSP: 0018:88010b6efa88 EFLAGS: 00010246 Jul 14 20:36:15 phelps kernel: [111935.191188] RAX: ffbb RBX: 88011742e008 RCX: 00088004 Jul 14 20:36:15 phelps kernel: [111935.191190] RDX: 88011742e378 RSI: 88011742e008 RDI: 00201875d808 Jul 14 20:36:15 phelps kernel: [111935.191192] RBP: 880118a8dfe0 R08: R09: 880118a8dfec Jul 14 20:36:15 phelps kernel: [111935.191194] R10: R11: 0001 R12: 00088004 Jul 14 20:36:15 phelps kernel: [111935.191196] R13: R14: 88011742e378 R15: Jul 14 20:36:15 phelps kernel: [111935.191199] FS: 7f8f3df8e940() GS:88011fc0() knlGS: Jul 14 20:36:15 phelps kernel: [111935.191201] CS: 0010 DS: ES: CR0: 80050033 Jul 14 20:36:15 phelps kernel: [111935.191203] CR2: 00201875dac0 CR3: 00010b42b000 CR4: 07f0 Jul 14 20:36:15 phelps kernel: [111935.191205] DR0: DR1: DR2: Jul 14 20:36:15 phelps kernel: [111935.191208] DR3: DR6: 0ff0 DR7: 0400 Jul 14 20:36:15 phelps kernel: [111935.191210] Process gnome-shell (pid: 1373, threadinfo 88010b6ee000, task 8801103d7710) Jul 14 20:36:15 phelps kernel: [111935.191212] Stack: Jul 14 20:36:15 phelps kernel: [111935.191213] 88011742e008 88011742e008 00088004 Jul 14 20:36:15 phelps kernel: [111935.191218] c90005144008 a06deaac 88011875f800 88011742e008 Jul 14 20:36:15 phelps kernel: [111935.191222] 880118a8b000 c90005144008 a09067a1 Jul 14 20:36:15 phelps kernel: [111935.191226] Call Trace: Jul 14 20:36:15 phelps kernel: [111935.191347] [a06deaac] ? _nv003990rm+0x406e/0xa790 [nvidia] Jul 14 20:36:15 phelps kernel: [111935.191400] [a09067a1] ? rm_check_pci_config_space+0x499/0xa44 [nvidia] Jul 14 20:36:15 phelps kernel: [111935.191450] [a0921930] ? nv_verify_pci_config+0x60/0x80 [nvidia] Jul 14 20:36:15 phelps kernel: [111935.191502] [a08fbaab] ? _nv014590rm+0x22/0x27 [nvidia] Jul 14 20:36:15 phelps kernel: [111935.191553] [a09080f7] ? _nv014633rm+0x31/0x538 [nvidia] Jul 14 20:36:15 phelps kernel: [111935.191675] [a06be7e3] ? _nv009673rm+0xf7/0x134 [nvidia] Jul 14 20:36:15 phelps kernel: [111935.191795] [a06df156] ? _nv003990rm+0x4718/0xa790 [nvidia] Jul 14 20:36:15 phelps kernel: [111935.191846] [a0906bdf] ? rm_check_pci_config_space+0x8d7/0xa44 [nvidia] Jul 14 20:36:15 phelps kernel: [111935.191915] [a0360736] ? _nv014429rm+0x9/0x21 [nvidia] Jul 14 20:36:15 phelps kernel: [111935.191964] [a0921930] ? nv_verify_pci_config+0x60/0x80 [nvidia] Jul 14 20:36:15 phelps kernel: [111935.192015] [a08fbaab] ? _nv014590rm+0x22/0x27 [nvidia] Jul 14 20:36:15 phelps
