[arch-general] my Arch box randomly becomes irresponsible

Sun Jul 15 23:46:46 EDT 2012

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 at 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 at gmail.com> wrote:

> 2012/7/15 Not To Miss <not.to.miss at 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