[arch-general] error setting up webdav
Hi, I followed the wiki https://wiki.archlinux.org/index.php/WebDAV#Server_.28Apache.29 exactly to setup webdav. After I restart the httpd.service, and cadaver test gave me error: $ cadaver http://localhost/dav Could not access /dav/ (not WebDAV-enabled?): 405 Method Not Allowed Connection to `localhost' closed. dav:!> ^CTerminated by signal 2. Here is the log from /var/log/httpd/127.0.0.1-access_log: ::1 - - [25/Feb/2013:23:32:07 -0700] "OPTIONS /dav/ HTTP/1.1" 200 - ::1 - - [25/Feb/2013:23:32:07 -0700] "PROPFIND /dav/ HTTP/1.1" 405 979 nothing special is reported in error_log. Anyone has anyone ideas what's wrong? I'd really appreciate any help. Thanks! Zech
Re: [arch-general] my Arch box randomly becomes irresponsible
x1568 [nvidia] Aug 9 16:25:38 phelps kernel: [72554.912749] [] ? _nv016412rm+0x578/0x5a6 [nvidia] Aug 9 16:25:38 phelps kernel: [72554.912749] [] ? _nv001056rm+0xf/0x14 [nvidia] Aug 9 16:25:38 phelps kernel: [72554.912749] [] ? _nv000955rm+0x31/0x59 [nvidia] Aug 9 16:25:38 phelps kernel: [72554.912749] [] ? _nv001106rm+0xa4e/0xaaf [nvidia] Aug 9 16:25:38 phelps kernel: [72554.912749] [] ? rm_ioctl+0x76/0x100 [nvidia] Aug 9 16:25:38 phelps kernel: [72554.912749] [] ? nv_kern_ioctl+0x15e/0x480 [nvidia] Aug 9 16:25:38 phelps kernel: [72554.912749] [] ? nv_kern_unlocked_ioctl+0x21/0x30 [nvidia] Aug 9 16:25:38 phelps kernel: [72554.912749] [] ? do_vfs_ioctl+0x97/0x530 Aug 9 16:25:38 phelps kernel: [72554.912749] [] ? do_munmap+0x1e3/0x3d0 Aug 9 16:25:38 phelps kernel: [72554.912749] [] ? fget_light+0x97/0x100 Aug 9 16:25:38 phelps kernel: [72554.912749] [] ? sys_ioctl+0x99/0xa0 Aug 9 16:25:38 phelps kernel: [72554.912749] [] ? posix_ktime_get_ts+0x11/0x20 Aug 9 16:25:38 phelps kernel: [72554.912749] [] ? 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 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 [] _nv004044rm+0x447f/0xae8b [nvidia] Aug 9 16:25:38 phelps kernel: [72554.912749] RSP Aug 9 16:25:38 phelps kernel: [72554.912749] CR2: 002015f822c0 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 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
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 wrote: > On Sun, Jul 15, 2012 at 10:46 PM, Not To Miss > 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:[] [] _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] [] ? > > _nv003990rm+0x406e/0xa790 [nvidia] > > Jul 14 20:36:15 phelps kernel: [111935.191400] [] ? > > rm_check_pci_config_space+0x499/0xa44 [nvidia] > > Jul 14 20:36:15 phelps kernel: [111935.191450] [] ? > > nv_verify_pci_config+0x60/0x80 [nvidia] > > Jul 14 20:36:15 phelps kernel: [111935.191502] [] ? > > _nv014590rm+0x22/0x27 [nvidia] > > Jul 14 20:36:15 phelps kernel: [111935.191553] [] ? > > _nv0
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 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
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 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 > > yes > > to > > no > > > > 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
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 wrote: > Am Sun, 15 Jul 2012 22:06:01 -0400 > schrieb Not To Miss : > > > 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 > > yes > > to > > no > > > > 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
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 wrote: > You certainly seem to have an OOPS related to the nvidia driver: > > >Call Trace: > >[] ? _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 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 wrote: > > I tried to disable suspension and hibernation by editing > > /usr/share/polkit-1/actions/org.freedesktop.upower.policy to change > > from > > yes > > to > > no > > > > 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
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 wrote: > 2012/7/16 Not To Miss > > > 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:[] [] _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] [] ? > > _nv003990rm+0x406e/0xa790 [nvidia] > > Jul 14 20:36:15 phelps kernel: [111935.191400] [] ? > > rm_check_pci_config_space+0x499/0xa44 [nvidia] > > Jul 14 20:36:15 phelps kernel: [111935.191450] [] ? > > nv_verify_pci_config+0x60/0x80 [nvidia] > > Jul 14 20:36:15 phelps kernel: [111935.191502] [] ? > > _nv014590rm+0x22/0x27 [nvidia] > > Jul 14 20:36:15 phelps kernel: [111935.191553] [] ? > > _nv014633rm+0x31/0x538 [nvidia] > > Jul 14 20:36:15 phelps kernel: [111935.191675] [] ? > > _nv009673rm+0xf7/0x134 [nvidia] > > Jul 14 20:36:15 phelps kernel: [111935.191795] [] ? > > _nv003990rm+0x4718/0xa790 [nvidia] > > Jul 14 20:36:15 phelps kernel: [
Re: [arch-general] my Arch box randomly becomes irresponsible
[111935.192619] [] ? nv_kern_unlocked_ioctl+0x21/0x30 [nvidia] Jul 14 20:36:15 phelps kernel: [111935.192624] [] ? do_vfs_ioctl+0x97/0x530 Jul 14 20:36:15 phelps kernel: [111935.192627] [] ? fget_light+0x97/0x100 Jul 14 20:36:15 phelps kernel: [111935.192630] [] ? sys_ioctl+0x99/0xa0 Jul 14 20:36:15 phelps kernel: [111935.192634] [] ? 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 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 Jul 14 20:36:15 phelps kernel: [111935.192789] CR2: 00201875dac0 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.00] Initializing cgroup subsys cpuset Jul 15 20:37:17 phelps kernel: [0.00] Initializing cgroup subsys cpu Jul 15 20:37:17 phelps kernel: [0.00] 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.00] Command line: root=/dev/md2 ro initrd=../initramfs-linux.img BOOT_IMAGE=../vmlinuz-linux Jul 15 20:37:17 phelps kernel: [0.00] BIOS-provided physical RAM map: Jul 15 20:37:17 phelps kernel: [0.00] BIOS-e820: - 0009f800 (usable) Jul 15 20:37:17 phelps kernel: [0.00] BIOS-e820: 0009f800 - 000a (reserved) Jul 15 20:37:17 phelps kernel: [0.00] BIOS-e820: 000f - 0010 (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 wrote: > 2012/7/15 Not To Miss > > > 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 > > yes > > to > > no > > > > 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 no
[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 yes to no 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
