[SOLVED] systemd reboot and poweroff as user
I decided to try systemd and all my services are working but I cannot reboot or poweroff as user.
$ systemctl poweroff
Failed to issue method call: Access denied
Failed to issue method call: Access denied
I also get that duplicate message for systemctl reboot.
According to the systemd wiki article, I should be able to reboot and poweroff as user and even if not, I should be given the opportunity to provide the root password, but I was not. Both commands work as expected if I su to root. Any suggestions? Thanks.
Last edited by kekules_dream (2012-08-13 10:14:50)
@Smasher816 - the op is right that he/she should be able to reboot, shutdown without superuser access with systemd. I just began using systemd and mine seems to work fine. You aren't logged in as root or another user in another terminal or tty are you? I know that you should STILL be given the option to enter the root password and shutdown, but that is the best I can think of at the moment
Similar Messages
-
[solved] systemd-journal and shadow.pacnew updates
After a recent install and update I have come across the same issue described here where the user was recommended to ignore and erase some .pacnew files. My update generated the following:
/etc/dhcpcd.conf.pacnew
/etc/group.pacnew
/etc/passwd.pacnew
/etc/shadow.pacnew
/etc/gshadow.pacnew
The first, dhcpcd, seemed sensible enough and I incorporated the changes. The latter four all share the following characteristics:
1. Removed mentions of systemd-journal-remote and systemd-journal-upload. I'm not sure why so I left those records in place.
2. Changed a few permissions here or there, which i incorporated into /etc/group and /etc/password.
3. Changed the default shell for a few users; these changes I incorporated.
I was unable to open /etc/shadow or /etc/gshadow in write mode so I've left these files. Perhaps that's fine because the thread mentioned above says so. However, there's no explanation of why or where this information was obtained (or ordained!)
Is it fine to leave these two files? Why have syssystemd-journal-remote and systemd-journal-upload been omitted?
Last edited by Deau (2014-08-29 06:54:18)The steps you took look quite sane to me.
These groups are not in the defaults provided by filesystem (e.g. I don't have them). see the edit
Apparently systemd creates system groups and users on it's own, see 'man systemd-sysusers'. Do you know / can figure out why these groups are created in the first place ? not important in this case, see the edit as well
FYI e.g.: https://bugs.archlinux.org/task/41717
The filesystem package provides those files as defaults (group, passwd, shadow, gshadow amongst otheres). However there are some packages that actually add additional groups they need (like ntp e.g.). The filesystem package cannot know about these. Therefor it's likely to have more groups in your local installation than in the .pacnew files you get.
The same applies for manually created users and groups of course.
If needed see the man pages for explanations of the respective files (e.g. 'man group').
Edit: Ok, I see that after an update I have them as well, so these are apparently new systemd groups and users. I think the rest I said above is still valid, so leaving those in place was the right thing to do.
Last edited by rebootl (2014-08-28 20:46:43) -
[solved] systemd: Start process as specific user
Hi,
I plan to use bittorrent-sync, and want to run it for each user separately. So I would like to modify the service to run the process as the user instead of root. Like bittorrent-sync@user1… and so on.
Is this possible?
Thanks
Last edited by silentsnake (2013-04-27 15:13:25)Thanks to you too, WonderWoofy.
[Unit]
Description=BitTorrent Sync service
After=network.target
[Service]
ExecStart=/usr/bin/btsync --nodaemon --config /home/%i/.sync/btsync.conf
Restart=on-abort
User=%i
Group=users
[Install]
WantedBy=multi-user.target
This allows me to run one instance per user with its own configuration. Since it's a server with no users actively working on, I think this is the way to go. But will investigate the systemd user session for my desktop clients. -
[SOLVED] systemd, autofs and lxdm
OK, after recently migrating rc.conf to the more 'systemd' structure, but still using init I figured I'd give systemd another shot, and herein lies my problem.
According to the wiki there should already be units available for various DMs, though i only have xdm available. I've copied and modified the copied version for lxdm (well, not strictly correctly, I've modified it to start xfce the same way that my "old" style does, with ck-launch) but I just get dumped to a root desktop (which I can't log out of). What I want is the lxdm login. I'm pretty sure there's a bunch of stuff I've forgotten since I set this up, so how do I get systemd to launch lxdm to a login screen.
Second. I'm getting autofs errors at boot, and automounting isn't available.
Google has helped me not one jot (either lousy googling or lousy forum thread titles, not sure which) and I need to fix this too.
Not looking for a verbatim answer. Rather looking for links where I can get the why's and wherefore's. The Arch systemd wiki doesn't cover this (it assumed units present which are not).
I've installed the arch units already. Any pointers would be appreciated.
Last edited by Roken (2012-07-28 22:25:06)lxdm package from Community contains usr/lib/systemd/system/lxdm.service
please check with
pacman -Ql lxdm
But if you can't
systemctl enable lxdm.service
you can try manually symlink it
ln -s '/usr/lib/systemd/system/lxdm.service' '/etc/systemd/system/display-manager.service'
btw. in AUR pkgbuilds there are no lxdm.service at the moment, so you neet to copy it from community source files (best way)
Last edited by nbvcxz (2012-07-26 11:28:11) -
[SOLVED]systemd and make a camera visible GUI-wise in your filemanager
After reading a lot about systemd in the wiki and in this forum I understand there are different opionons about systemd. Anyway, I have a adapted all the changes to rc.conf leaving out only a few daemons to start there. So why not give systemd a try? If you dont want to read the full posting I finally got it to work, basically by reading carefully and checking the suggested tests in the systemd wiki. (loginctl)
As suggested by the wiki, I tried the systemd yesterday. Enabled via systemctl some services to "replace" my rc.conf daemons. I got what I thought everything to work, including autologin directly to my Xfce4 desktop. Everything except the digital camera.
When starting Arch traditionally via initscripts I immediately can see the camera in the filemanager (Nautilus) when the camera is attached via USB.
Some minutes later, after adding "init=/usr/lib/systemd/systemd" to the APPEND line in Syslinux and rebooting, my machine reboots
fine.But when connecting the camera again it is not visible graphically.
The camera is there because when using gphoto2 (the commandline) as root I can transfer pictures etc.
Even if I am no happy CLI user I can handle it when necessary. Handling pictures a graphical view of them is much easier...
As the wiki about systemd says one can try it out. I have not removed anything from the system and when starting Arch again, the initscript way, I can see the camera again in my filemanager, gthumb works again and pictures can be transferred to my machine.
In the wiki again, this time about digital cameras
Permission issues
Camera devices should be granted permission using ACLs. For this to work, users need to have consolekit or systemd running and the user session must be registered with them accordingly.
Check this using /usr/bin/ck-list-sessions to verify a value of "TRUE" should be returned for both the "active" and "is-local" fields:
$ ck-list-sessions | grep TRUE
active = TRUE
is-local = TRUE
ACL=Atlantic Container Line is what first comes into my mind. I have had some connections to transport business...I admit I had to google it to find the correct interpretation of this mumbo-jumbo.
The wiki also gives a "hint", if this is not working try to use the obsolete camera group and edit some udev rules.
Should not be necessary when it has worked before systemd and earlier experiences
But what is this about "Permission issues"? Here is my listings relative the wiki hints. All seems OK.. or why the heck are there two sessions??
[leif@krasaki ~]$ ck-list-sessions | grep TRUE
is-local = TRUE
active = TRUE
is-local = TRUE
[leif@krasaki ~]$ ck-list-sessions
Session1:
unix-user = '1000'
realname = '(null)'
seat = 'Seat1'
session-type = ''
active = FALSE
x11-display = ''
x11-display-device = ''
display-device = '/dev/tty1'
remote-host-name = ''
is-local = TRUE
on-since = '2012-10-24T07:12:56.499847Z'
login-session-id = '1'
idle-since-hint = '2012-10-24T07:13:26.994037Z'
Session2:
unix-user = '1000'
realname = '(null)'
seat = 'Seat1'
session-type = ''
active = TRUE
x11-display = ':0'
x11-display-device = '/dev/tty7'
display-device = '/dev/tty1'
remote-host-name = ''
is-local = TRUE
on-since = '2012-10-24T07:13:02.361157Z'
login-session-id = '1'
[leif@krasaki ~]$
As one can see, the ACTIVE values are here as the wiki says. But no camera. Those values are the same, wheter which way the machine is started. But 2 sessions??
Further reading in the systemd wiki article and consolekit vs systemd.logind gives a clue.
From the wiki:
In order to check the status of your user session, you can use loginctl. To see if your user session is properly set up, check if the following command contains Active=yes. All polkit actions like suspending the system or mounting external drives with Udisks should then work automatically.
So when started via systemd and running logintctl, it gives this surprising result. Does not matter wheter as normal user, nor as root....
[leif@krasaki ~]$ loginctl
SESSION UID USER SEAT
1 1000 leif seat0
1 sessions listed.
[leif@krasaki ~]$ loginctl show-session 1
Id=1
Timestamp=Wed, 24 Oct 2012 10:57:03 +0200
TimestampMonotonic=20040019
DefaultControlGroup=name=systemd:/user/leif/1
VTNr=1
TTY=tty1
Remote=no
Service=login
Leader=315
Audit=1
Type=tty
Class=user
Active=no
State=online
KillProcesses=no
IdleHint=yes
IdleSinceHint=1351069009642296
IdleSinceHintMonotonic=6664433
Name=leif
[leif@krasaki ~]$
Surprising? Should it not have been Active=Yes? So something is wrong in my settings although it had worked "before" starting using systemd..
OK, so far. Lost? Not yet. Double check again everything and I found the culprit, my ~/.bash_profile which had worked before seemed a bit different to what is suggested in the wiki. The old one, actually started 2 sessions, as also could be seen here above checking ck-list-sessions. That was the problem
Using a fresh edited ~/.bash_profile as suggested here, the camera is visible graphically
Finally, just for fun, start again the old initscipt way. Enabling daemon and so on. Still 2 sessions going on....Here it was the "/.xinitrc, which also had some old fashions and I removed the ck-launch-session from the exec line. So even here, now only 1 session..
Anyway, now the camera is visible, both starting with initscripts, naturally also some daemons active in rc.conf and by starting with systemd.
I rest my case and it seems systemd works with everything on my machine which is just a normal desktop used by an old man.
Thanks for reading...Solved now! Boot times are as fast as posssible on my HDD I think. Only thing after uninstalling initscripst and initscripts-systemd was that locale was not set inspite of a correct /etc/locale.conf. I had to make /etc/profile.d/locale.sh with this content;
if [ -s /etc/locale.conf ]; then
. /etc/locale.conf
fi
export LANG LANGUAGE LC_CTYPE LC_NUMERIC LC_TIME LC_COLLATE
export LC_MONETARY LC_MESSAGES LC_PAPER LC_NAME LC_ADDRESS
export LC_TELEPHONE LC_MEASUREMENT LC_IDENTIFICATION -
[SOLVED]Disable Shutdown and Reboot from XFCE
Hi all
I would like to disable the shutdown and reboot buttons from XFCE (4.10) or to do disable shutdown/reboot systemwide.
I searched for specific xfce instructions and all i could find was using xfconf-query[1] and afaik it can only disable hibernate and suspend buttons
[1]http://forum.xfce.org/viewtopic.php?id=4781
Last edited by boriscougar (2012-09-11 21:51:22)@nadman10
it had no change to remove my users from the power group
@2ManyDogs
Creating that file (/etc/xdg/xfce4/kiosk/kioskrc) and setting which users could shutdown solved the problem
Thanks for your time -
[SOLVED] Rebooted and now no Internet
I rebooted and the LAN cable is in and lit up but no network connectivity on my arch box.
Worked fine until i rebooted.
What do I check?
Last edited by CaptainKirk (2009-12-10 10:45:34)This Windows box says:
Microsoft Windows [Version 6.0.6001]
Copyright (c) 2006 Microsoft Corporation. All rights reserved.
C:\Users\kirk>ipconfig
Windows IP Configuration
Ethernet adapter Local Area Connection:
Connection-specific DNS Suffix . : home
Link-local IPv6 Address . . . . . : fe80::f1f4:3a2a:4a84:f5f1%10
IPv4 Address. . . . . . . . . . . : 10.0.0.1
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 10.0.0.138
Tunnel adapter Local Area Connection* 6:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . : home
Tunnel adapter Local Area Connection* 7:
Connection-specific DNS Suffix . :
IPv6 Address. . . . . . . . . . . : 2001:0:4137:9e50:416:2715:f5ff:fffe
Link-local IPv6 Address . . . . . : fe80::416:2715:f5ff:fffe%12
Default Gateway . . . . . . . . . : ::
and arch box says:
[kirk@localhost ~]$ /sbin/ifconfig eth0
eth0 Link encap:Ethernet HWaddr 00:1E:8C:DE:ED:85
inet6 addr: fe80::21e:8cff:fede:ed85/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:134 errors:0 dropped:0 overruns:0 frame:0
TX packets:39 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:13549 (13.2 Kb) TX bytes:5670 (5.5 Kb)
Interrupt:27 Base address:0xe000
[kirk@localhost ~]$ /sbin/route
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
default * 255.255.255.0 U 202 0 0 eth0
[kirk@localhost ~]$ cat /etc/resolv.conf
# Generated by dhcpcd from eth0
# /etc/resolv.conf.head can replace this line
domain home
nameserver 10.0.0.138
# /etc/resolv.conf.tail can replace this line -
iOS Cangjie input method can not be used. Original with Space Bar word selection function is invalid, as soon as possible to solve, it will affect the most users in Taiwan and Hong Kong.
No PR1.2 Firmware update, No update for Nokia Messaging, No updates for Ovi Maps .... Why is the N900 the forgotten stepchild ?
"PR1.2 is still being tested - http://twitter.com/luovanto/statuses/13087245356"
Hong Kong Launch http://www.youtube.com/watch?v=pY8zCBzvQLo -
[SOLVED] systemd-udevd using 100% CPU and monitors go to sleep on boot
Hi,
Turned my PC on this morning to find an issue with the monitors going to sleep immediately after booting. The boot process is usually slim autologin to a cinnamon session. I can see as far as entering my LUKS passphrase, followed by a few additional lines, followed by blank monitors and monitors entering power saving mode.
Booting with nomodeset on the kernel command line allows me to boot to a terminal and I can login etc, but obviously X doesn't start. I'm using xf86-video-ati drivers.
When booting with KMS enabled I also have a runaway systemd-udevd process which is thrashing my processor and I'm unable to kill it (I've tried kill -9 and still it persists).
The PC was working fine when I shut it down last night. No updates have been performed since, and no configuration changes have been made. I did notice that the power management dialog in the settings failed to open though.
Any suggestions would be welcome please, as I've now lost half a day trying to get this resolved.
TIA
X.
Edit: I've also tried downgrading xserver to 1.15, xf86-video-ati and the associated dependencies with no change.
Edit2: I've also disabled slim and rebooted and the same thing happens - so I don't believe it's an issue with X but with KMS.
Edit3: Booting with acpi=off on the kernel command line also fails with the same result.
Last edited by xanthi (2014-07-30 13:55:58)Turned out to be an issue with libdrm. Apparently I had run some updates yesterday before shutting down, but they didn't appear in pacman.log; instead I found them by looking in the pacman package cache and found:
-rw-r--r-- 1 root root 110072 Jul 29 22:59 lib32-libdrm-2.4.56-1-x86_64.pkg.tar.xz
-rw-r--r-- 1 root root 160996 Jul 29 22:55 libdrm-2.4.56-1-x86_64.pkg.tar.xz
Downgraded [lib32-]libdrm packages to 2.4.54-1, rebooted, and success. -
User accounts missing after post install reboot and cannot login
The 10.5 install process completed and my mac mini rebooted and came up with the login screen. None of my user accounts show - my admin user and my regular user account (also has admin privs) are not available and all I can chose is 'Other' - I have enter both my user accounts and passwords but they are not accepted.
I then restarted from the Leopard disk, cancelled the install program and used the password utility to reset these passwords and all the accounts show up in the selections (including a guest one I have set up).
I'm stuck here - can get no further. Only option seems to be restarting the install from scratch unless anyone else has a good suggestion?Ok now restarted the install process (by selecting back from the login screen and then selecting restart from the login screen that showed the 'Other' user account only. I held down the c on the keyboard until the restart took the Leopard disc which was in the drive.
Then I went thru the install steps (language, license agree etc) and when it asked for what disk to install on I selected the mac mini HDD ad then clicked the options button to select the Archiv and Install option (rather than the Update only option I had been doing).
The install process purred through ok and I am up and running.
Now on to my MacBook Pro .....Thanks for the help and suggestions all -
[SOLVED] Would like to allow a user to remotely reboot my box [SOLVED]
Hello,
Here's my problem, I've got two boxes gypsy and crow and gypsy has a habit of having the display lockup, I don't think the system is completely locked up so I'm pretty sure I can ssh and reboot it (since I set up ssh on gypsy, the box hasn't actually locked up, though, so I don't know for sure)
Becuase I'm paranoid, I don't want to allow ssh into gypsy to do anything BESIDES reboot, so I'm interested in what's the best way to implement this. I could stick the reboot command into .bash_profile for my dedicated reboot user, but if you're fast enough w/ ^c you (where you are, presumably, automated cracking software) could, concievably, kill the process before it's done running, and end up logged in.
This is going to be continued in a browser that isn't links.
Edit: Continued:
So I tried writing a shell script
#!/bin/bash
sudo reboot
and using that script as the login shell for the dedicated reboot user ("rebooter"), but I would get a permission denied error when I tried to login as the user then. (My sudoers file allows the user "rebooter" to run reboot w/o a passwd). So it seems like in princple you could make this work, I'm just doing somthing wrong.
But this raises another question, could I still manage to login to bash by interupting this script? I don't think so, becuase in this instance bash is not running interactively, please tell me if I"m wrong.
Is there maybe a better way to set this up? Maybe there's something I can do with the config to sshd to force login by the "rebooter" to force a reboot?
I guess there might also be some way for me to set things up with chroot so that if you managed to login as "rebooter" you couldn't do anything meaningful besides reboot anyway, but I haven't looked into this yet. If this is the best answer, go ahead and tell me to rtfm, but first I'd like to know if there's a simpler solution.
Last edited by pseudonomous (2008-09-27 00:57:23)carlocci wrote:
you could change the user shell to something like this
carlocci:x:1000:100:sig. carlocci,,,:/home/carlocci:/usr/bin/sudo shutdown now -r
or
carlocci:x:1000:100:sig. carlocci,,,:/home/carlocci:/bin/bash -c sudo shutdown now -r
I tried this, and it didn't work, I think it gave me "permission denied" errors, so I wonder if I got the syntax wrong. what I was doing was using "usermod -s " to try and change the shell and I was confused as to how to properly put the white space in you need to run the command "sudo reboot".
Thanks, everybody for your suggestions, I will look more into an ssh key based-authentication. I don't really want to run webmin becuase I don't need to any remote administration besides rebooting, so webmin seems like overkill. I will report back after trying to set this up.
When I say "display locks up" I mean that, for some reason, either after boot or after I end a window manager session, my screen turns black and it looks like X is trying to restart but failing (there's a change in the shading on my monitor I associate with that) hitting control alt backspace doesn't help and trying to switch to one of the consoles doesn't work either. But I don't think the system is dead becuase I can toggle numlock and scrolllock on and off. (Which doesn't work when X completely freezes) I can't replicate this behavior on demand, it seems to occur more or less randomly. -
[SOLVED] Systemd and laptop-mode-tools frequency scaling
Hi all.
After a long time with no arch updates (november 2011) for various reasons, I decided to reinstall Arch from point 0 on my Clevo laptop.
I was pleased to see nothing went bad, all is now set like I want. I installed systemd yesterday. All very straightforward for me, I only have a problem with CPU frequency scaling plus some minor glitches.
Before systemd, everything went fine. Ondemand governor, set up like I wanted.
Now when on AC the system uses ondemand, but when on battery it uses the conservative governor. What's more, it does not go over 1.6GHz (2.54GHz max).
Here are some infos about it:
[adriano@M735T ~] cpupower frequency-info
analyzing CPU 0:
driver: acpi-cpufreq
CPUs which run at the same hardware frequency: 0 1
CPUs which need to have their frequency coordinated by software: 0
maximum transition latency: 10.0 us.
hardware limits: 800 MHz - 2.53 GHz
available frequency steps: 2.53 GHz, 2.53 GHz, 1.60 GHz, 800 MHz
available cpufreq governors: ondemand, performance
current policy: frequency should be within 800 MHz and 1.60 GHz.
The governor "ondemand" may decide which speed to use
within this range.
current CPU frequency is 1.60 GHz.
boost state support:
Supported: yes
Active: yes
[yes this is all come out of the cpupower command, no mention of CPU 1. Is this normal?]
Of course LMT is set up correctly
CONTROL_CPU_FREQUENCY="1"
BATT_CPU_MAXFREQ=fastest
BATT_CPU_MINFREQ=slowest
BATT_CPU_GOVERNOR=ondemand
BATT_CPU_IGNORE_NICE_LOAD=1
LM_AC_CPU_MAXFREQ=fastest
LM_AC_CPU_MINFREQ=slowest
LM_AC_CPU_GOVERNOR=ondemand
LM_AC_CPU_IGNORE_NICE_LOAD=1
NOLM_AC_CPU_MAXFREQ=fastest
NOLM_AC_CPU_MINFREQ=slowest
NOLM_AC_CPU_GOVERNOR=ondemand
NOLM_AC_CPU_IGNORE_NICE_LOAD=0
[adriano@M735T ~] sudo systemctl status laptop-mode-tools.service
laptop-mode-tools.service - Laptop Power Saving Tools
Loaded: loaded (/usr/lib/systemd/system/laptop-mode-tools.service; enabled)
Active: active (exited) since Sun, 02 Sep 2012 17:03:45 +0200; 4h 34min ago
Main PID: 367 (code=exited, status=0/SUCCESS)
CGroup: name=systemd:/system/laptop-mode-tools.service
Sep 02 17:03:43 M735T laptop_mode[367]: /usr/sbin/laptop_mode: line 198: /dev/fd/1: No such device or address
Sep 02 17:03:44 M735T laptop_mode[367]: /usr/sbin/laptop_mode: line 198: /dev/fd/1: No such device or address
Sep 02 17:03:44 M735T laptop_mode[367]: /usr/sbin/laptop_mode: line 198: /dev/fd/1: No such device or address
I wonder why LMT status is "exited"
OK bin that, I just now see something is wrong. I said it used conservative, but I'm on battery and it now says ondemand (still 1.6GHz max). However it seems it does so casually.
ACPI:
[adriano@M735T ~] acpi
Battery 0: Discharging, 53%, rate information unavailable
This may be (?) or may not be linked with nother problem I have: when unplugging the AC the KDE battery monitor does not update. It says AC is plugged and it will not activate power saving features (screen dimming, suspend...)
Note that this battery monitor problem occurred even before systemd, so it should not be linked to the above problem. However I'm not 100% sure the above problems did not occur before installing systemd since I only had the system up and running for a comple of days. I seem to recall I checked and it worked fine.
Any idea why all this happens?
Last edited by OdinEidolon (2012-11-20 08:56:31)Ok rebooted and this is the output of the pm-powersave log file:
(AC IN, no battery)
(pastebin)
http://pastebin.com/Kf2Lx7UQ
If I grep cpupower:
Running hook /usr/lib/pm-utils/power.d/cpupower false:
Setting cpupower frequency governor to ondemand...Setting cpu: 0
/usr/lib/pm-utils/power.d/cpupower false: success.
Running hook /usr/lib/pm-utils/power.d/cpupower true:
Setting cpupower frequency governor to conservative...Setting cpu: 0
/usr/lib/pm-utils/power.d/cpupower true: success.
Running hook /usr/lib/pm-utils/power.d/cpupower false:
Setting cpupower frequency governor to ondemand...Setting cpu: 0
/usr/lib/pm-utils/power.d/cpupower false: success.
Running hook /usr/lib/pm-utils/power.d/cpupower true:
Setting cpupower frequency governor to conservative...Setting cpu: 0
/usr/lib/pm-utils/power.d/cpupower true: success.
Running hook /usr/lib/pm-utils/power.d/cpupower true:
Setting cpupower frequency governor to conservative...Setting cpu: 0
/usr/lib/pm-utils/power.d/cpupower true: success.
Running hook /usr/lib/pm-utils/power.d/cpupower true:
Setting cpupower frequency governor to conservative...Setting cpu: 0
/usr/lib/pm-utils/power.d/cpupower true: success.
Running hook /usr/lib/pm-utils/power.d/cpupower true:
Setting cpupower frequency governor to conservative...Setting cpu: 0
/usr/lib/pm-utils/power.d/cpupower true: success.
Running hook /usr/lib/pm-utils/power.d/cpupower true:
Setting cpupower frequency governor to conservative...Setting cpu: 0
/usr/lib/pm-utils/power.d/cpupower true: success.
Running hook /usr/lib/pm-utils/power.d/cpupower false:
Setting cpupower frequency governor to ondemand...Setting cpu: 0
/usr/lib/pm-utils/power.d/cpupower false: success.
Running hook /usr/lib/pm-utils/power.d/cpupower true:
Setting cpupower frequency governor to conservative...Setting cpu: 0
/usr/lib/pm-utils/power.d/cpupower true: success.
Running hook /usr/lib/pm-utils/power.d/cpupower false:
Setting cpupower frequency governor to ondemand...Setting cpu: 0
/usr/lib/pm-utils/power.d/cpupower false: success.
Running hook /usr/lib/pm-utils/power.d/cpupower false:
Setting cpupower frequency governor to ondemand...Setting cpu: 0
/usr/lib/pm-utils/power.d/cpupower false: success.
Running hook /usr/lib/pm-utils/power.d/cpupower true:
Setting cpupower frequency governor to conservative...Setting cpu: 0
/usr/lib/pm-utils/power.d/cpupower true: success.
Running hook /usr/lib/pm-utils/power.d/cpupower true:
Setting cpupower frequency governor to conservative...Setting cpu: 0
/usr/lib/pm-utils/power.d/cpupower true: success.
Running hook /usr/lib/pm-utils/power.d/cpupower false:
Setting cpupower frequency governor to ondemand...Setting cpu: 0
/usr/lib/pm-utils/power.d/cpupower false: success.
Running hook /usr/lib/pm-utils/power.d/cpupower true:
Setting cpupower frequency governor to conservative...Setting cpu: 0
/usr/lib/pm-utils/power.d/cpupower true: success.
Running hook /usr/lib/pm-utils/power.d/cpupower false:
Setting cpupower frequency governor to ondemand...Setting cpu: 0
/usr/lib/pm-utils/power.d/cpupower false: success.
Running hook /usr/lib/pm-utils/power.d/cpupower true:
Setting cpupower frequency governor to conservative...Setting cpu: 0
/usr/lib/pm-utils/power.d/cpupower true: success.
Running hook /usr/lib/pm-utils/power.d/cpupower false:
Setting cpupower frequency governor to ondemand...Setting cpu: 0
/usr/lib/pm-utils/power.d/cpupower false: success.
Running hook /usr/lib/pm-utils/power.d/cpupower false:
Setting cpupower frequency governor to ondemand...Setting cpu: 0
/usr/lib/pm-utils/power.d/cpupower false: success.
Running hook /usr/lib/pm-utils/power.d/cpupower true:
Setting cpupower frequency governor to conservative...Setting cpu: 0
/usr/lib/pm-utils/power.d/cpupower true: success.
Running hook /usr/lib/pm-utils/power.d/cpupower false:
Setting cpupower frequency governor to ondemand...Setting cpu: 0
/usr/lib/pm-utils/power.d/cpupower false: success.
Running hook /usr/lib/pm-utils/power.d/cpupower true:
Setting cpupower frequency governor to conservative...Setting cpu: 0
/usr/lib/pm-utils/power.d/cpupower true: success.
Running hook /usr/lib/pm-utils/power.d/cpupower false:
Setting cpupower frequency governor to ondemand...Setting cpu: 0
/usr/lib/pm-utils/power.d/cpupower false: success.
Running hook /usr/lib/pm-utils/power.d/cpupower false:
Setting cpupower frequency governor to ondemand...Setting cpu: 0
/usr/lib/pm-utils/power.d/cpupower false: success.
Running hook /usr/lib/pm-utils/power.d/cpupower true:
Setting cpupower frequency governor to conservative...Setting cpu: 0
/usr/lib/pm-utils/power.d/cpupower true: success.
Running hook /usr/lib/pm-utils/power.d/cpupower false:
Setting cpupower frequency governor to ondemand...Setting cpu: 0
/usr/lib/pm-utils/power.d/cpupower false: success.
Running hook /usr/lib/pm-utils/power.d/cpupower true:
Setting cpupower frequency governor to conservative...Setting cpu: 0
/usr/lib/pm-utils/power.d/cpupower true: success.
Running hook /usr/lib/pm-utils/power.d/cpupower false:
Setting cpupower frequency governor to ondemand...Setting cpu: 0
/usr/lib/pm-utils/power.d/cpupower false: success.
Running hook /usr/lib/pm-utils/power.d/cpupower true:
Setting cpupower frequency governor to conservative...Setting cpu: 0
/usr/lib/pm-utils/power.d/cpupower true: success.
Running hook /usr/lib/pm-utils/power.d/cpupower true:
Setting cpupower frequency governor to conservative...Setting cpu: 0
/usr/lib/pm-utils/power.d/cpupower true: success.
Running hook /usr/lib/pm-utils/power.d/cpupower true:
Setting cpupower frequency governor to conservative...Setting cpu: 0
/usr/lib/pm-utils/power.d/cpupower true: success.
Running hook /usr/lib/pm-utils/power.d/cpupower true:
Setting cpupower frequency governor to conservative...Setting cpu: 0
/usr/lib/pm-utils/power.d/cpupower true: success.
Running hook /usr/lib/pm-utils/power.d/cpupower true:
Setting cpupower frequency governor to conservative...Setting cpu: 0
/usr/lib/pm-utils/power.d/cpupower true: success.
Running hook /usr/lib/pm-utils/power.d/cpupower true:
Setting cpupower frequency governor to conservative...Setting cpu: 0
/usr/lib/pm-utils/power.d/cpupower true: success.
Running hook /usr/lib/pm-utils/power.d/cpupower true:
Setting cpupower frequency governor to conservative...Setting cpu: 0
/usr/lib/pm-utils/power.d/cpupower true: success.
Running hook /usr/lib/pm-utils/power.d/cpupower true:
Setting cpupower frequency governor to conservative...Setting cpu: 0
/usr/lib/pm-utils/power.d/cpupower true: success.
Running hook /usr/lib/pm-utils/power.d/cpupower false:
Setting cpupower frequency governor to ondemand...Setting cpu: 0
/usr/lib/pm-utils/power.d/cpupower false: success.
Running hook /usr/lib/pm-utils/power.d/cpupower true:
Setting cpupower frequency governor to conservative...Setting cpu: 0
/usr/lib/pm-utils/power.d/cpupower true: success.
Running hook /usr/lib/pm-utils/power.d/cpupower false:
Setting cpupower frequency governor to ondemand...Setting cpu: 0
/usr/lib/pm-utils/power.d/cpupower false: success.
Running hook /usr/lib/pm-utils/power.d/cpupower true:
Setting cpupower frequency governor to conservative...Setting cpu: 0
/usr/lib/pm-utils/power.d/cpupower true: success.
Running hook /usr/lib/pm-utils/power.d/cpupower true:
Setting cpupower frequency governor to conservative...Setting cpu: 0
/usr/lib/pm-utils/power.d/cpupower true: success.
Running hook /usr/lib/pm-utils/power.d/cpupower false:
Setting cpupower frequency governor to ondemand...Setting cpu: 0
/usr/lib/pm-utils/power.d/cpupower false: success.
Running hook /usr/lib/pm-utils/power.d/cpupower true:
Setting cpupower frequency governor to conservative...Setting cpu: 0
/usr/lib/pm-utils/power.d/cpupower true: success.
Running hook /usr/lib/pm-utils/power.d/cpupower false:
Setting cpupower frequency governor to ondemand...Setting cpu: 0
/usr/lib/pm-utils/power.d/cpupower false: success.
Running hook /usr/lib/pm-utils/power.d/cpupower true:
Setting cpupower frequency governor to conservative...Setting cpu: 0
/usr/lib/pm-utils/power.d/cpupower true: success.
Running hook /usr/lib/pm-utils/power.d/cpupower false:
Setting cpupower frequency governor to ondemand...Setting cpu: 0
/usr/lib/pm-utils/power.d/cpupower false: success.
Running hook /usr/lib/pm-utils/power.d/cpupower true:
Setting cpupower frequency governor to conservative...Setting cpu: 0
/usr/lib/pm-utils/power.d/cpupower true: success.
Running hook /usr/lib/pm-utils/power.d/cpupower false:
Setting cpupower frequency governor to ondemand...Setting cpu: 0
/usr/lib/pm-utils/power.d/cpupower false: success.
Running hook /usr/lib/pm-utils/power.d/cpupower false:
Setting cpupower frequency governor to ondemand...Setting cpu: 0
/usr/lib/pm-utils/power.d/cpupower false: success.
Running hook /usr/lib/pm-utils/power.d/cpupower false:
Setting cpupower frequency governor to ondemand...Setting cpu: 0
/usr/lib/pm-utils/power.d/cpupower false: success.
Running hook /usr/lib/pm-utils/power.d/cpupower true:
Setting cpupower frequency governor to conservative...Setting cpu: 0
/usr/lib/pm-utils/power.d/cpupower true: success.
Running hook /usr/lib/pm-utils/power.d/cpupower false:
Setting cpupower frequency governor to ondemand...Setting cpu: 0
/usr/lib/pm-utils/power.d/cpupower false: success.
Running hook /usr/lib/pm-utils/power.d/cpupower true:
Setting cpupower frequency governor to conservative...Setting cpu: 0
/usr/lib/pm-utils/power.d/cpupower true: success.
Running hook /usr/lib/pm-utils/power.d/cpupower false:
Setting cpupower frequency governor to ondemand...Setting cpu: 0
/usr/lib/pm-utils/power.d/cpupower false: success.
Running hook /usr/lib/pm-utils/power.d/cpupower false:
Setting cpupower frequency governor to ondemand...Setting cpu: 0
/usr/lib/pm-utils/power.d/cpupower false: success.
Running hook /usr/lib/pm-utils/power.d/cpupower false:
Setting cpupower frequency governor to ondemand...Setting cpu: 0
/usr/lib/pm-utils/power.d/cpupower false: success.
Running hook /usr/lib/pm-utils/power.d/cpupower true:
Setting cpupower frequency governor to conservative...Setting cpu: 0
/usr/lib/pm-utils/power.d/cpupower true: success.
Running hook /usr/lib/pm-utils/power.d/cpupower false:
Setting cpupower frequency governor to ondemand...Setting cpu: 0
/usr/lib/pm-utils/power.d/cpupower false: success.
Running hook /usr/lib/pm-utils/power.d/cpupower true:
Setting cpupower frequency governor to conservative...Setting cpu: 0
/usr/lib/pm-utils/power.d/cpupower true: success.
Running hook /usr/lib/pm-utils/power.d/cpupower false:
Setting cpupower frequency governor to ondemand...Setting cpu: 0
/usr/lib/pm-utils/power.d/cpupower false: success.
Running hook /usr/lib/pm-utils/power.d/cpupower true:
Setting cpupower frequency governor to conservative...Setting cpu: 0
/usr/lib/pm-utils/power.d/cpupower true: success.
Running hook /usr/lib/pm-utils/power.d/cpupower true:
Setting cpupower frequency governor to conservative...Setting cpu: 0
/usr/lib/pm-utils/power.d/cpupower true: success.
Running hook /usr/lib/pm-utils/power.d/cpupower false:
Setting cpupower frequency governor to ondemand...Setting cpu: 0
/usr/lib/pm-utils/power.d/cpupower false: success.
Running hook /usr/lib/pm-utils/power.d/cpupower false:
Setting cpupower frequency governor to ondemand...Setting cpu: 0
/usr/lib/pm-utils/power.d/cpupower false: success.
Running hook /usr/lib/pm-utils/power.d/cpupower false:
Setting cpupower frequency governor to ondemand...Setting cpu: 0
/usr/lib/pm-utils/power.d/cpupower false: success.
Running hook /usr/lib/pm-utils/power.d/cpupower true:
Setting cpupower frequency governor to conservative...Setting cpu: 0
/usr/lib/pm-utils/power.d/cpupower true: success.
Running hook /usr/lib/pm-utils/power.d/cpupower false:
Setting cpupower frequency governor to ondemand...Setting cpu: 0
/usr/lib/pm-utils/power.d/cpupower false: success.
Running hook /usr/lib/pm-utils/power.d/cpupower true:
Setting cpupower frequency governor to conservative...Setting cpu: 0
/usr/lib/pm-utils/power.d/cpupower true: success.
Running hook /usr/lib/pm-utils/power.d/cpupower false:
Setting cpupower frequency governor to ondemand...Setting cpu: 0
/usr/lib/pm-utils/power.d/cpupower false: success.
Running hook /usr/lib/pm-utils/power.d/cpupower false:
Setting cpupower frequency governor to ondemand...Setting cpu: 0
/usr/lib/pm-utils/power.d/cpupower false: success.
Running hook /usr/lib/pm-utils/power.d/cpupower false:
Setting cpupower frequency governor to ondemand...Setting cpu: 0
/usr/lib/pm-utils/power.d/cpupower false: success.
Running hook /usr/lib/pm-utils/power.d/cpupower true:
Setting cpupower frequency governor to conservative...Setting cpu: 0
/usr/lib/pm-utils/power.d/cpupower true: success.
Running hook /usr/lib/pm-utils/power.d/cpupower true:
Setting cpupower frequency governor to conservative...Setting cpu: 0
/usr/lib/pm-utils/power.d/cpupower true: success.
Running hook /usr/lib/pm-utils/power.d/cpupower false:
Setting cpupower frequency governor to ondemand...Setting cpu: 0
/usr/lib/pm-utils/power.d/cpupower false: success.
Running hook /usr/lib/pm-utils/power.d/cpupower true:
Setting cpupower frequency governor to conservative...Setting cpu: 0
/usr/lib/pm-utils/power.d/cpupower true: success.
Running hook /usr/lib/pm-utils/power.d/cpupower true:
Setting cpupower frequency governor to conservative...Setting cpu: 0
/usr/lib/pm-utils/power.d/cpupower true: success.
Running hook /usr/lib/pm-utils/power.d/cpupower true:
Setting cpupower frequency governor to conservative...Setting cpu: 0
/usr/lib/pm-utils/power.d/cpupower true: success.
Running hook /usr/lib/pm-utils/power.d/cpupower false:
Setting cpupower frequency governor to ondemand...Setting cpu: 0
/usr/lib/pm-utils/power.d/cpupower false: success.
Running hook /usr/lib/pm-utils/power.d/cpupower true:
Setting cpupower frequency governor to conservative...Setting cpu: 0
/usr/lib/pm-utils/power.d/cpupower true: success.
Running hook /usr/lib/pm-utils/power.d/cpupower true:
Setting cpupower frequency governor to conservative...Setting cpu: 0
/usr/lib/pm-utils/power.d/cpupower true: success.
Running hook /usr/lib/pm-utils/power.d/cpupower true:
Setting cpupower frequency governor to conservative...Setting cpu: 0
/usr/lib/pm-utils/power.d/cpupower true: success.
Running hook /usr/lib/pm-utils/power.d/cpupower false:
Setting cpupower frequency governor to ondemand...Setting cpu: 0
/usr/lib/pm-utils/power.d/cpupower false: success.
Running hook /usr/lib/pm-utils/power.d/cpupower true:
Setting cpupower frequency governor to conservative...Setting cpu: 0
/usr/lib/pm-utils/power.d/cpupower true: success.
Running hook /usr/lib/pm-utils/power.d/cpupower false:
Setting cpupower frequency governor to ondemand...Setting cpu: 0
/usr/lib/pm-utils/power.d/cpupower false: success.
Running hook /usr/lib/pm-utils/power.d/cpupower false:
Setting cpupower frequency governor to ondemand...Setting cpu: 0
/usr/lib/pm-utils/power.d/cpupower false: success.
right now:
1) cpupower reports ondemand and 2.54GHz (right)
2) acpi -bi reports nothing as it should (battery is disconnected)
3) acpi -a reports AC in as it should
4) all KDE stuff works OK
Now I plug the battery in:
1) cpupower reports ondemand and 2.54GHz (right)
2) acpi -bi reports nothing, which is wrong
3) acpi -a reports AC in as it should
4) KDE battery monitor reports no battery in, as signaled by acpi
5) if performing acpi_listen ,it reports nothing interesting
Now I unplug AC:
Absolutely nothing changes (not even in the log file) but:
1) cpupower reports ondemand and 1.6GHz (wrong)
2) acpi -bi reports nothing, which is wrong
3) acpi -a reports no AC as it should
4) KDE battery monitor reports no battery in, as signaled by acpi, but it also reports AC is inserted -
[Solved]Unbootable fresh intall - reboot and select proper boot device
Hello, this is not my first Arch Linux installation, but it is my first time posting to the forums. I just completed my second attempt at installing Arch on a brand-new Toshiba Satellite C55. After the installation completes and I reboot, instead of Grub I get a blank screen with this message:
Reboot and select proper Boot device
or Insert Boot Media in selected Boot device and press a key
I thought maybe I made a mistake, so I started over and completed a second installation, only to get the same message. I am not sure how to proceed. I tried booting from a xubuntu live usb I had lying around, and it doesn't recognize that either, although it does recognize my Arch live usb.
Any ideas?
Last edited by zevski (2015-04-29 03:05:31)UPDATE: I erased the entire disk with
sgdisk -Z
and reinstalled again, this time creating only a boot partition and a root partition for the rest . Installed gummiboot instead of GRUB. This time it worked, so I know that at least I did not brick my machine.
I don't know if erasing the disk did the trick (since this machine had previously had Windows 8 on it, and may have had something "leftover"), or if I had made a mistake during the partition or when mounting the partitions (I noticed an error in my fstab the third time around, so I started over ,again, and the fourth time it worked).
Just thought I would post this in case any other newbies run into the same issue. -
[Solved] systemd-journald periodically uses 50% CPU
Hello!
I run KDE 4.11 on Arch fully upgraded. Since shortly my system seems to choke periodically at the systemd-journald process. It takes 50% of the CPU power available and everything else is starting to studder and freeze. using jounalctl only shows normal log entries and not (like suggested somewhere else) a huge amount of error entries within seconds.
I have tried to remedy this:
- I disabled cups as mentioned somewhere else
- I deleted all configuration files concerning alsa and pulseaudio (cause I found errors with journalctl) and reinstalled both
- I set /var/log/journal to "copy on write" because it is on a btrfs partition (another suggestion in a thread)
- I tried to somehow to disable systemd-journald (seems this is not possible)
Nothing seems to solve the problem - still my the systemd-journald process peaks to 50% CPU every few minutes and stays at this ressource eating level for a few minutes. Then it drops down to normal again using only minimal ressources for a few minutes ...
I am lost here. My system is really quite unusable though it is a fresh install from only two weeks ago. I only noticed this behaviour three days ago - afterwards I upgraded to kernel 3.10.9 but this hasn't changed anything either.
Any ideas anyone?
thx for reading,
piedro
Last edited by piedro (2015-02-08 18:24:45)Hi jrusell!
Well I think I could solve it ... here is what I did:
- I deleted /var/log/journal
- rebooted and looked at the fresh log via journalctl: now it generated fresh entries again and there it was: (like in similar problems) the log has been flushed with hundreds fo fail messages! ... something like a "user burst limit exceeded" for rtkit and I found a problem with nepomukindexer (should have guessed it's KDE again - after the update to 4.11)
- so I stopped all nepomuk stuff and deleted ~/.kde4/share/apps/nepomuk, then let nepomuk trun again recreating the whole indexing database in the process (to be honest it's still in the process but ressources aren't used excessively)
Since then there hasn't been any problem with the journald process yet ... :-)
thx everybody for reading,
p.
Last edited by piedro (2013-08-26 14:11:32) -
[Solved] Shutdown/Reboot takes a long time
I do an upgrade every 5 days or so but it's been a while since I last rebooted--probably around 15-24 days. Since I haven't shutdown/rebooted for a while, I decided to do one today. I noticed that shutdown/reboot takes a long time, around 2-3 minutes whereas before, it would be instant and the behavior seems weird. Upon pressing shutdown or reboot:
1. Monitors become completely black and searches for a signal (by switching HDMI, DVI, etc). PC still on
2. After 1 minute, if reboot, I can hear the GPU fans spin like crazy. Shutdown doesn't do this, just quiet.
3. After waiting another minute, some output shows up really fast and the PC is rebooted or shutdown
This didn't happen before so I think it's probable that one of the updates did this. Unfortunately, I'm not sure how to tell which one.
I followed the section "Diagnosing Shutdown Problems" here on how to debug shutdown problems. I've got the systemd shutdown log but I can't tell where the problem is:
[ 0.000000] Initializing cgroup subsys cpuset
[ 0.000000] Initializing cgroup subsys cpu
[ 0.000000] Initializing cgroup subsys cpuacct
[ 0.000000] Linux version 3.19.3-3-ARCH (builduser@tobias) (gcc version 4.9.2 20150304 (prerelease) (GCC) ) #1 SMP PREEMPT Wed Apr 8 14:10:00 CEST 2015
[ 0.000000] Command line: BOOT_IMAGE=/boot/vmlinuz-linux root=UUID=0a8d7720-6c75-4f1e-b2e4-04d8196aa0fb rw quiet
[ 0.000000] e820: BIOS-provided physical RAM map:
[ 0.000000] BIOS-e820: [mem 0x0000000000000000-0x000000000009d7ff] usable
[ 0.000000] BIOS-e820: [mem 0x000000000009d800-0x000000000009ffff] reserved
[ 0.000000] BIOS-e820: [mem 0x00000000000e0000-0x00000000000fffff] reserved
[ 0.000000] BIOS-e820: [mem 0x0000000000100000-0x00000000bea34fff] usable
[ 0.000000] BIOS-e820: [mem 0x00000000bea35000-0x00000000bea7dfff] ACPI NVS
[ 0.000000] BIOS-e820: [mem 0x00000000bea7e000-0x00000000bea85fff] ACPI data
[ 0.000000] BIOS-e820: [mem 0x00000000bea86000-0x00000000bf5f9fff] reserved
[ 0.000000] BIOS-e820: [mem 0x00000000bf5fa000-0x00000000bf5fbfff] usable
[ 0.000000] BIOS-e820: [mem 0x00000000bf5fc000-0x00000000bf60bfff] reserved
[ 0.000000] BIOS-e820: [mem 0x00000000bf60c000-0x00000000bf615fff] ACPI NVS
[ 0.000000] BIOS-e820: [mem 0x00000000bf616000-0x00000000bf63afff] reserved
[ 0.000000] BIOS-e820: [mem 0x00000000bf63b000-0x00000000bf67dfff] ACPI NVS
[ 0.000000] BIOS-e820: [mem 0x00000000bf67e000-0x00000000bf7fffff] usable
[ 0.000000] BIOS-e820: [mem 0x00000000fed1c000-0x00000000fed3ffff] reserved
[ 0.000000] BIOS-e820: [mem 0x00000000ff000000-0x00000000ffffffff] reserved
[ 0.000000] BIOS-e820: [mem 0x0000000100000000-0x000000023f7fffff] usable
[ 0.000000] NX (Execute Disable) protection: active
[ 0.000000] SMBIOS 2.7 present.
[ 0.000000] DMI: MSI MS-7673/P67A-G43 (MS-7673), BIOS V1.11 04/14/2011
[ 0.000000] e820: update [mem 0x00000000-0x00000fff] usable ==> reserved
[ 0.000000] e820: remove [mem 0x000a0000-0x000fffff] usable
[ 0.000000] AGP: No AGP bridge found
[ 0.000000] e820: last_pfn = 0x23f800 max_arch_pfn = 0x400000000
[ 0.000000] MTRR default type: uncachable
[ 0.000000] MTRR fixed ranges enabled:
[ 0.000000] 00000-9FFFF write-back
[ 0.000000] A0000-BFFFF uncachable
[ 0.000000] C0000-CFFFF write-protect
[ 0.000000] D0000-E7FFF uncachable
[ 0.000000] E8000-FFFFF write-protect
[ 0.000000] MTRR variable ranges enabled:
[ 0.000000] 0 base 000000000 mask E00000000 write-back
[ 0.000000] 1 base 200000000 mask FC0000000 write-back
[ 0.000000] 2 base 0C0000000 mask FC0000000 uncachable
[ 0.000000] 3 base 23F800000 mask FFF800000 uncachable
[ 0.000000] 4 disabled
[ 0.000000] 5 disabled
[ 0.000000] 6 disabled
[ 0.000000] 7 disabled
[ 0.000000] 8 disabled
[ 0.000000] 9 disabled
[ 0.000000] PAT configuration [0-7]: WB WC UC- UC WB WC UC- UC
[ 0.000000] e820: update [mem 0xc0000000-0xffffffff] usable ==> reserved
[ 0.000000] e820: last_pfn = 0xbf800 max_arch_pfn = 0x400000000
[ 0.000000] found SMP MP-table at [mem 0x000fce60-0x000fce6f] mapped at [ffff8800000fce60]
[ 0.000000] Scanning 1 areas for low memory corruption
[ 0.000000] Base memory trampoline at [ffff880000097000] 97000 size 24576
[ 0.000000] init_memory_mapping: [mem 0x00000000-0x000fffff]
[ 0.000000] [mem 0x00000000-0x000fffff] page 4k
[ 0.000000] BRK [0x01b32000, 0x01b32fff] PGTABLE
[ 0.000000] BRK [0x01b33000, 0x01b33fff] PGTABLE
[ 0.000000] BRK [0x01b34000, 0x01b34fff] PGTABLE
[ 0.000000] init_memory_mapping: [mem 0x23f600000-0x23f7fffff]
[ 0.000000] [mem 0x23f600000-0x23f7fffff] page 2M
[ 0.000000] BRK [0x01b35000, 0x01b35fff] PGTABLE
[ 0.000000] init_memory_mapping: [mem 0x220000000-0x23f5fffff]
[ 0.000000] [mem 0x220000000-0x23f5fffff] page 2M
[ 0.000000] init_memory_mapping: [mem 0x200000000-0x21fffffff]
[ 0.000000] [mem 0x200000000-0x21fffffff] page 2M
[ 0.000000] init_memory_mapping: [mem 0x00100000-0xbea34fff]
[ 0.000000] [mem 0x00100000-0x001fffff] page 4k
[ 0.000000] [mem 0x00200000-0xbe9fffff] page 2M
[ 0.000000] [mem 0xbea00000-0xbea34fff] page 4k
[ 0.000000] init_memory_mapping: [mem 0xbf5fa000-0xbf5fbfff]
[ 0.000000] [mem 0xbf5fa000-0xbf5fbfff] page 4k
[ 0.000000] BRK [0x01b36000, 0x01b36fff] PGTABLE
[ 0.000000] init_memory_mapping: [mem 0xbf67e000-0xbf7fffff]
[ 0.000000] [mem 0xbf67e000-0xbf7fffff] page 4k
[ 0.000000] BRK [0x01b37000, 0x01b37fff] PGTABLE
[ 0.000000] init_memory_mapping: [mem 0x100000000-0x1ffffffff]
[ 0.000000] [mem 0x100000000-0x1ffffffff] page 2M
[ 0.000000] RAMDISK: [mem 0x3795c000-0x37ca5fff]
[ 0.000000] ACPI: Early table checksum verification disabled
[ 0.000000] ACPI: RSDP 0x00000000000F0450 000024 (v02 ALASKA)
[ 0.000000] ACPI: XSDT 0x00000000BEA7E068 000054 (v01 ALASKA A M I 01072009 AMI 00010013)
[ 0.000000] ACPI: FACP 0x00000000BEA85148 0000F4 (v04 ALASKA A M I 01072009 AMI 00010013)
[ 0.000000] ACPI: DSDT 0x00000000BEA7E150 006FF4 (v02 ALASKA A M I 00000015 INTL 20051117)
[ 0.000000] ACPI: FACS 0x00000000BF60DF80 000040
[ 0.000000] ACPI: APIC 0x00000000BEA85240 000072 (v03 ALASKA A M I 01072009 AMI 00010013)
[ 0.000000] ACPI: SSDT 0x00000000BEA852B8 000102 (v01 AMICPU PROC 00000001 MSFT 03000001)
[ 0.000000] ACPI: MCFG 0x00000000BEA853C0 00003C (v01 ALASKA A M I 01072009 MSFT 00000097)
[ 0.000000] ACPI: HPET 0x00000000BEA85400 000038 (v01 ALASKA A M I 01072009 AMI. 00000004)
[ 0.000000] ACPI: ASF! 0x00000000BEA85438 0000A0 (v32 INTEL HCG 00000001 TFSM 000F4240)
[ 0.000000] ACPI: Local APIC address 0xfee00000
[ 0.000000] No NUMA configuration found
[ 0.000000] Faking a node at [mem 0x0000000000000000-0x000000023f7fffff]
[ 0.000000] NODE_DATA(0) allocated [mem 0x23f7f5000-0x23f7f8fff]
[ 0.000000] [ffffea0000000000-ffffea0008ffffff] PMD -> [ffff880236e00000-ffff88023edfffff] on node 0
[ 0.000000] Zone ranges:
[ 0.000000] DMA [mem 0x00001000-0x00ffffff]
[ 0.000000] DMA32 [mem 0x01000000-0xffffffff]
[ 0.000000] Normal [mem 0x100000000-0x23f7fffff]
[ 0.000000] Movable zone start for each node
[ 0.000000] Early memory node ranges
[ 0.000000] node 0: [mem 0x00001000-0x0009cfff]
[ 0.000000] node 0: [mem 0x00100000-0xbea34fff]
[ 0.000000] node 0: [mem 0xbf5fa000-0xbf5fbfff]
[ 0.000000] node 0: [mem 0xbf67e000-0xbf7fffff]
[ 0.000000] node 0: [mem 0x100000000-0x23f7fffff]
[ 0.000000] Initmem setup node 0 [mem 0x00001000-0x23f7fffff]
[ 0.000000] On node 0 totalpages: 2089813
[ 0.000000] DMA zone: 64 pages used for memmap
[ 0.000000] DMA zone: 21 pages reserved
[ 0.000000] DMA zone: 3996 pages, LIFO batch:0
[ 0.000000] DMA32 zone: 12143 pages used for memmap
[ 0.000000] DMA32 zone: 777145 pages, LIFO batch:31
[ 0.000000] Normal zone: 20448 pages used for memmap
[ 0.000000] Normal zone: 1308672 pages, LIFO batch:31
[ 0.000000] ACPI: PM-Timer IO Port: 0x408
[ 0.000000] ACPI: Local APIC address 0xfee00000
[ 0.000000] ACPI: LAPIC (acpi_id[0x01] lapic_id[0x00] enabled)
[ 0.000000] ACPI: LAPIC (acpi_id[0x02] lapic_id[0x02] enabled)
[ 0.000000] ACPI: LAPIC (acpi_id[0x03] lapic_id[0x04] enabled)
[ 0.000000] ACPI: LAPIC (acpi_id[0x04] lapic_id[0x06] enabled)
[ 0.000000] ACPI: LAPIC_NMI (acpi_id[0xff] high edge lint[0x1])
[ 0.000000] ACPI: IOAPIC (id[0x00] address[0xfec00000] gsi_base[0])
[ 0.000000] IOAPIC[0]: apic_id 0, version 32, address 0xfec00000, GSI 0-23
[ 0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
[ 0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
[ 0.000000] ACPI: IRQ0 used by override.
[ 0.000000] ACPI: IRQ9 used by override.
[ 0.000000] Using ACPI (MADT) for SMP configuration information
[ 0.000000] ACPI: HPET id: 0x8086a701 base: 0xfed00000
[ 0.000000] smpboot: Allowing 4 CPUs, 0 hotplug CPUs
[ 0.000000] PM: Registered nosave memory: [mem 0x00000000-0x00000fff]
[ 0.000000] PM: Registered nosave memory: [mem 0x0009d000-0x0009dfff]
[ 0.000000] PM: Registered nosave memory: [mem 0x0009e000-0x0009ffff]
[ 0.000000] PM: Registered nosave memory: [mem 0x000a0000-0x000dffff]
[ 0.000000] PM: Registered nosave memory: [mem 0x000e0000-0x000fffff]
[ 0.000000] PM: Registered nosave memory: [mem 0xbea35000-0xbea7dfff]
[ 0.000000] PM: Registered nosave memory: [mem 0xbea7e000-0xbea85fff]
[ 0.000000] PM: Registered nosave memory: [mem 0xbea86000-0xbf5f9fff]
[ 0.000000] PM: Registered nosave memory: [mem 0xbf5fc000-0xbf60bfff]
[ 0.000000] PM: Registered nosave memory: [mem 0xbf60c000-0xbf615fff]
[ 0.000000] PM: Registered nosave memory: [mem 0xbf616000-0xbf63afff]
[ 0.000000] PM: Registered nosave memory: [mem 0xbf63b000-0xbf67dfff]
[ 0.000000] PM: Registered nosave memory: [mem 0xbf800000-0xfed1bfff]
[ 0.000000] PM: Registered nosave memory: [mem 0xfed1c000-0xfed3ffff]
[ 0.000000] PM: Registered nosave memory: [mem 0xfed40000-0xfeffffff]
[ 0.000000] PM: Registered nosave memory: [mem 0xff000000-0xffffffff]
[ 0.000000] e820: [mem 0xbf800000-0xfed1bfff] available for PCI devices
[ 0.000000] Booting paravirtualized kernel on bare hardware
[ 0.000000] setup_percpu: NR_CPUS:128 nr_cpumask_bits:128 nr_cpu_ids:4 nr_node_ids:1
[ 0.000000] PERCPU: Embedded 31 pages/cpu @ffff88023f400000 s86336 r8192 d32448 u524288
[ 0.000000] pcpu-alloc: s86336 r8192 d32448 u524288 alloc=1*2097152
[ 0.000000] pcpu-alloc: [0] 0 1 2 3
[ 0.000000] Built 1 zonelists in Node order, mobility grouping on. Total pages: 2057137
[ 0.000000] Policy zone: Normal
[ 0.000000] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-linux root=UUID=0a8d7720-6c75-4f1e-b2e4-04d8196aa0fb rw quiet
[ 0.000000] PID hash table entries: 4096 (order: 3, 32768 bytes)
[ 0.000000] xsave: enabled xstate_bv 0x7, cntxt size 0x340 using standard form
[ 0.000000] AGP: Checking aperture...
[ 0.000000] AGP: No AGP bridge found
[ 0.000000] Calgary: detecting Calgary via BIOS EBDA area
[ 0.000000] Calgary: Unable to locate Rio Grande table in EBDA - bailing!
[ 0.000000] Memory: 8146392K/8359252K available (5534K kernel code, 917K rwdata, 1744K rodata, 1164K init, 1156K bss, 212860K reserved, 0K cma-reserved)
[ 0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=4, Nodes=1
[ 0.000000] Preemptible hierarchical RCU implementation.
[ 0.000000] RCU dyntick-idle grace-period acceleration is enabled.
[ 0.000000] RCU restricting CPUs from NR_CPUS=128 to nr_cpu_ids=4.
[ 0.000000] RCU: Adjusting geometry for rcu_fanout_leaf=16, nr_cpu_ids=4
[ 0.000000] NR_IRQS:8448 nr_irqs:456 16
[ 0.000000] Console: colour dummy device 80x25
[ 0.000000] console [tty0] enabled
[ 0.000000] hpet clockevent registered
[ 0.000000] tsc: Fast TSC calibration using PIT
[ 0.000000] tsc: Detected 3299.649 MHz processor
[ 0.000020] Calibrating delay loop (skipped), value calculated using timer frequency.. 6601.26 BogoMIPS (lpj=10998830)
[ 0.000022] pid_max: default: 32768 minimum: 301
[ 0.000025] ACPI: Core revision 20141107
[ 0.002006] ACPI: All ACPI Tables successfully acquired
[ 0.229873] Security Framework initialized
[ 0.229877] Yama: becoming mindful.
[ 0.230159] Dentry cache hash table entries: 1048576 (order: 11, 8388608 bytes)
[ 0.231159] Inode-cache hash table entries: 524288 (order: 10, 4194304 bytes)
[ 0.231602] Mount-cache hash table entries: 16384 (order: 5, 131072 bytes)
[ 0.231607] Mountpoint-cache hash table entries: 16384 (order: 5, 131072 bytes)
[ 0.231738] Initializing cgroup subsys memory
[ 0.231741] Initializing cgroup subsys devices
[ 0.231743] Initializing cgroup subsys freezer
[ 0.231744] Initializing cgroup subsys net_cls
[ 0.231745] Initializing cgroup subsys blkio
[ 0.231759] CPU: Physical Processor ID: 0
[ 0.231759] CPU: Processor Core ID: 0
[ 0.231762] ENERGY_PERF_BIAS: Set to 'normal', was 'performance'
ENERGY_PERF_BIAS: View and update with x86_energy_perf_policy(8)
[ 0.231764] mce: CPU supports 9 MCE banks
[ 0.231772] CPU0: Thermal monitoring enabled (TM1)
[ 0.231778] Last level iTLB entries: 4KB 512, 2MB 8, 4MB 8
Last level dTLB entries: 4KB 512, 2MB 32, 4MB 32, 1GB 0
[ 0.231839] Freeing SMP alternatives memory: 20K (ffffffff81a0a000 - ffffffff81a0f000)
[ 0.232422] ftrace: allocating 21171 entries in 83 pages
[ 0.238717] ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1
[ 0.271684] smpboot: CPU0: Intel(R) Core(TM) i5-2500K CPU @ 3.30GHz (fam: 06, model: 2a, stepping: 07)
[ 0.271688] TSC deadline timer enabled
[ 0.271700] Performance Events: PEBS fmt1+, 16-deep LBR, SandyBridge events, full-width counters, Intel PMU driver.
[ 0.271711] perf_event_intel: PEBS disabled due to CPU errata, please upgrade microcode
[ 0.271712] ... version: 3
[ 0.271712] ... bit width: 48
[ 0.271713] ... generic registers: 8
[ 0.271714] ... value mask: 0000ffffffffffff
[ 0.271714] ... max period: 0000ffffffffffff
[ 0.271715] ... fixed-purpose events: 3
[ 0.271715] ... event mask: 00000007000000ff
[ 0.291699] x86: Booting SMP configuration:
[ 0.291700] .... node #0, CPUs: #1
[ 0.304842] NMI watchdog: enabled on all CPUs, permanently consumes one hw-PMU counter.
[ 0.305029] #2 #3
[ 0.334799] x86: Booted up 1 node, 4 CPUs
[ 0.334802] smpboot: Total of 4 processors activated (26407.07 BogoMIPS)
[ 0.336656] devtmpfs: initialized
[ 0.338107] PM: Registering ACPI NVS region [mem 0xbea35000-0xbea7dfff] (299008 bytes)
[ 0.338111] PM: Registering ACPI NVS region [mem 0xbf60c000-0xbf615fff] (40960 bytes)
[ 0.338111] PM: Registering ACPI NVS region [mem 0xbf63b000-0xbf67dfff] (274432 bytes)
[ 0.338196] pinctrl core: initialized pinctrl subsystem
[ 0.338227] RTC time: 18:49:17, date: 04/22/15
[ 0.338286] NET: Registered protocol family 16
[ 0.349856] cpuidle: using governor ladder
[ 0.363177] cpuidle: using governor menu
[ 0.363192] ACPI: bus type PCI registered
[ 0.363193] acpiphp: ACPI Hot Plug PCI Controller Driver version: 0.5
[ 0.363233] PCI: MMCONFIG for domain 0000 [bus 00-ff] at [mem 0xe0000000-0xefffffff] (base 0xe0000000)
[ 0.363234] PCI: not using MMCONFIG
[ 0.363235] PCI: Using configuration type 1 for base access
[ 0.376685] ACPI: Added _OSI(Module Device)
[ 0.376686] ACPI: Added _OSI(Processor Device)
[ 0.376687] ACPI: Added _OSI(3.0 _SCP Extensions)
[ 0.376688] ACPI: Added _OSI(Processor Aggregator Device)
[ 0.377668] ACPI: Executed 1 blocks of module-level executable AML code
[ 0.378832] ACPI: Dynamic OEM Table Load:
[ 0.378835] ACPI: SSDT 0xFFFF880235BFDE40 000084 (v01 AMI CST 00000001 MSFT 03000001)
[ 0.379146] ACPI: Interpreter enabled
[ 0.379150] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S2_] (20141107/hwxface-580)
[ 0.379156] ACPI: (supports S0 S1 S3 S4 S5)
[ 0.379157] ACPI: Using IOAPIC for interrupt routing
[ 0.379168] PCI: MMCONFIG for domain 0000 [bus 00-ff] at [mem 0xe0000000-0xefffffff] (base 0xe0000000)
[ 0.379198] PCI: MMCONFIG at [mem 0xe0000000-0xefffffff] reserved in ACPI motherboard resources
[ 0.379380] PCI: Using host bridge windows from ACPI; if necessary, use "pci=nocrs" and report a bug
[ 0.379496] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 0.381659] ACPI: PCI Root Bridge [PCI0] (domain 0000 [bus 00-ff])
[ 0.381662] acpi PNP0A08:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
[ 0.381725] acpi PNP0A08:00: _OSC: platform does not support [PCIeCapability]
[ 0.381755] acpi PNP0A08:00: _OSC: not requesting control; platform does not support [PCIeCapability]
[ 0.381757] acpi PNP0A08:00: _OSC: OS requested [PCIeHotplug PME AER PCIeCapability]
[ 0.381758] acpi PNP0A08:00: _OSC: platform willing to grant [PCIeHotplug PME AER]
[ 0.381759] acpi PNP0A08:00: _OSC failed (AE_SUPPORT); disabling ASPM
[ 0.381932] PCI host bridge to bus 0000:00
[ 0.381934] pci_bus 0000:00: root bus resource [bus 00-ff]
[ 0.381935] pci_bus 0000:00: root bus resource [io 0x0000-0x03af]
[ 0.381936] pci_bus 0000:00: root bus resource [io 0x03e0-0x0cf7]
[ 0.381936] pci_bus 0000:00: root bus resource [io 0x03b0-0x03df]
[ 0.381937] pci_bus 0000:00: root bus resource [io 0x0d00-0xffff]
[ 0.381938] pci_bus 0000:00: root bus resource [mem 0x000a0000-0x000bffff]
[ 0.381939] pci_bus 0000:00: root bus resource [mem 0x000c0000-0x000dffff]
[ 0.381940] pci_bus 0000:00: root bus resource [mem 0xc0000000-0xffffffff]
[ 0.381945] pci 0000:00:00.0: [8086:0100] type 00 class 0x060000
[ 0.381993] pci 0000:00:01.0: [8086:0101] type 01 class 0x060400
[ 0.382014] pci 0000:00:01.0: PME# supported from D0 D3hot D3cold
[ 0.382032] pci 0000:00:01.0: System wakeup disabled by ACPI
[ 0.382079] pci 0000:00:16.0: [8086:1c3a] type 00 class 0x078000
[ 0.382098] pci 0000:00:16.0: reg 0x10: [mem 0xfe708000-0xfe70800f 64bit]
[ 0.382164] pci 0000:00:16.0: PME# supported from D0 D3hot D3cold
[ 0.382218] pci 0000:00:1a.0: [8086:1c2d] type 00 class 0x0c0320
[ 0.382235] pci 0000:00:1a.0: reg 0x10: [mem 0xfe707000-0xfe7073ff]
[ 0.382315] pci 0000:00:1a.0: PME# supported from D0 D3hot D3cold
[ 0.382339] pci 0000:00:1a.0: System wakeup disabled by ACPI
[ 0.382365] pci 0000:00:1b.0: [8086:1c20] type 00 class 0x040300
[ 0.382378] pci 0000:00:1b.0: reg 0x10: [mem 0xfe700000-0xfe703fff 64bit]
[ 0.382443] pci 0000:00:1b.0: PME# supported from D0 D3hot D3cold
[ 0.382493] pci 0000:00:1c.0: [8086:1c10] type 01 class 0x060400
[ 0.382628] pci 0000:00:1c.0: PME# supported from D0 D3hot D3cold
[ 0.382664] pci 0000:00:1c.0: System wakeup disabled by ACPI
[ 0.382689] pci 0000:00:1c.4: [8086:244e] type 01 class 0x060401
[ 0.382761] pci 0000:00:1c.4: PME# supported from D0 D3hot D3cold
[ 0.382787] pci 0000:00:1c.4: System wakeup disabled by ACPI
[ 0.382810] pci 0000:00:1c.5: [8086:1c1a] type 01 class 0x060400
[ 0.382882] pci 0000:00:1c.5: PME# supported from D0 D3hot D3cold
[ 0.382908] pci 0000:00:1c.5: System wakeup disabled by ACPI
[ 0.382932] pci 0000:00:1c.6: [8086:1c1c] type 01 class 0x060400
[ 0.383004] pci 0000:00:1c.6: PME# supported from D0 D3hot D3cold
[ 0.383029] pci 0000:00:1c.6: System wakeup disabled by ACPI
[ 0.383056] pci 0000:00:1d.0: [8086:1c26] type 00 class 0x0c0320
[ 0.383074] pci 0000:00:1d.0: reg 0x10: [mem 0xfe706000-0xfe7063ff]
[ 0.383154] pci 0000:00:1d.0: PME# supported from D0 D3hot D3cold
[ 0.383181] pci 0000:00:1d.0: System wakeup disabled by ACPI
[ 0.383206] pci 0000:00:1f.0: [8086:1c46] type 00 class 0x060100
[ 0.383340] pci 0000:00:1f.2: [8086:1c02] type 00 class 0x010601
[ 0.383355] pci 0000:00:1f.2: reg 0x10: [io 0xf070-0xf077]
[ 0.383361] pci 0000:00:1f.2: reg 0x14: [io 0xf060-0xf063]
[ 0.383366] pci 0000:00:1f.2: reg 0x18: [io 0xf050-0xf057]
[ 0.383372] pci 0000:00:1f.2: reg 0x1c: [io 0xf040-0xf043]
[ 0.383378] pci 0000:00:1f.2: reg 0x20: [io 0xf020-0xf03f]
[ 0.383384] pci 0000:00:1f.2: reg 0x24: [mem 0xfe705000-0xfe7057ff]
[ 0.383422] pci 0000:00:1f.2: PME# supported from D3hot
[ 0.383461] pci 0000:00:1f.3: [8086:1c22] type 00 class 0x0c0500
[ 0.383473] pci 0000:00:1f.3: reg 0x10: [mem 0xfe704000-0xfe7040ff 64bit]
[ 0.383490] pci 0000:00:1f.3: reg 0x20: [io 0xf000-0xf01f]
[ 0.383561] pci 0000:01:00.0: [1002:6719] type 00 class 0x030000
[ 0.383571] pci 0000:01:00.0: reg 0x10: [mem 0xc0000000-0xcfffffff 64bit pref]
[ 0.383579] pci 0000:01:00.0: reg 0x18: [mem 0xfe620000-0xfe63ffff 64bit]
[ 0.383584] pci 0000:01:00.0: reg 0x20: [io 0xe000-0xe0ff]
[ 0.383593] pci 0000:01:00.0: reg 0x30: [mem 0xfe600000-0xfe61ffff pref]
[ 0.383621] pci 0000:01:00.0: supports D1 D2
[ 0.383650] pci 0000:01:00.1: [1002:aa80] type 00 class 0x040300
[ 0.383660] pci 0000:01:00.1: reg 0x10: [mem 0xfe640000-0xfe643fff 64bit]
[ 0.383708] pci 0000:01:00.1: supports D1 D2
[ 0.389829] pci 0000:00:01.0: PCI bridge to [bus 01]
[ 0.389830] pci 0000:00:01.0: bridge window [io 0xe000-0xefff]
[ 0.389832] pci 0000:00:01.0: bridge window [mem 0xfe600000-0xfe6fffff]
[ 0.389833] pci 0000:00:01.0: bridge window [mem 0xc0000000-0xcfffffff 64bit pref]
[ 0.389906] pci 0000:00:1c.0: PCI bridge to [bus 02]
[ 0.389985] pci 0000:03:00.0: [1b21:1080] type 01 class 0x060400
[ 0.390139] pci 0000:03:00.0: supports D1 D2
[ 0.390140] pci 0000:03:00.0: PME# supported from D0 D1 D2 D3hot D3cold
[ 0.396493] pci 0000:00:1c.4: PCI bridge to [bus 03-04] (subtractive decode)
[ 0.396501] pci 0000:00:1c.4: bridge window [io 0x0000-0x03af] (subtractive decode)
[ 0.396502] pci 0000:00:1c.4: bridge window [io 0x03e0-0x0cf7] (subtractive decode)
[ 0.396503] pci 0000:00:1c.4: bridge window [io 0x03b0-0x03df] (subtractive decode)
[ 0.396504] pci 0000:00:1c.4: bridge window [io 0x0d00-0xffff] (subtractive decode)
[ 0.396505] pci 0000:00:1c.4: bridge window [mem 0x000a0000-0x000bffff] (subtractive decode)
[ 0.396506] pci 0000:00:1c.4: bridge window [mem 0x000c0000-0x000dffff] (subtractive decode)
[ 0.396507] pci 0000:00:1c.4: bridge window [mem 0xc0000000-0xffffffff] (subtractive decode)
[ 0.396651] pci 0000:03:00.0: PCI bridge to [bus 04]
[ 0.396745] pci 0000:05:00.0: [1033:0194] type 00 class 0x0c0330
[ 0.396772] pci 0000:05:00.0: reg 0x10: [mem 0xfe500000-0xfe501fff 64bit]
[ 0.396910] pci 0000:05:00.0: PME# supported from D0 D3hot D3cold
[ 0.403155] pci 0000:00:1c.5: PCI bridge to [bus 05]
[ 0.403160] pci 0000:00:1c.5: bridge window [mem 0xfe500000-0xfe5fffff]
[ 0.403227] pci 0000:06:00.0: [10ec:8168] type 00 class 0x020000
[ 0.403248] pci 0000:06:00.0: reg 0x10: [io 0xd000-0xd0ff]
[ 0.403279] pci 0000:06:00.0: reg 0x18: [mem 0xd0004000-0xd0004fff 64bit pref]
[ 0.403298] pci 0000:06:00.0: reg 0x20: [mem 0xd0000000-0xd0003fff 64bit pref]
[ 0.403403] pci 0000:06:00.0: supports D1 D2
[ 0.403404] pci 0000:06:00.0: PME# supported from D0 D1 D2 D3hot D3cold
[ 0.409816] pci 0000:00:1c.6: PCI bridge to [bus 06]
[ 0.409819] pci 0000:00:1c.6: bridge window [io 0xd000-0xdfff]
[ 0.409826] pci 0000:00:1c.6: bridge window [mem 0xd0000000-0xd00fffff 64bit pref]
[ 0.410049] ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 6 7 10 *11 12 14 15)
[ 0.410074] ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 6 7 *10 11 12 14 15)
[ 0.410098] ACPI: PCI Interrupt Link [LNKC] (IRQs *3 4 5 6 10 11 12 14 15)
[ 0.410122] ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 5 6 10 *11 12 14 15)
[ 0.410146] ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 5 6 7 10 11 12 14 15) *0
[ 0.410170] ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 5 6 7 10 11 12 14 15) *0
[ 0.410194] ACPI: PCI Interrupt Link [LNKG] (IRQs 3 4 *5 6 7 10 11 12 14 15)
[ 0.410218] ACPI: PCI Interrupt Link [LNKH] (IRQs 3 4 5 6 *7 10 11 12 14 15)
[ 0.410250] ACPI: Enabled 3 GPEs in block 00 to 3F
[ 0.410300] vgaarb: setting as boot device: PCI:0000:01:00.0
[ 0.410301] vgaarb: device added: PCI:0000:01:00.0,decodes=io+mem,owns=io+mem,locks=none
[ 0.410302] vgaarb: loaded
[ 0.410303] vgaarb: bridge control possible 0000:01:00.0
[ 0.410339] PCI: Using ACPI for IRQ routing
[ 0.415815] PCI: pci_cache_line_size set to 64 bytes
[ 0.415855] e820: reserve RAM buffer [mem 0x0009d800-0x0009ffff]
[ 0.415856] e820: reserve RAM buffer [mem 0xbea35000-0xbfffffff]
[ 0.415857] e820: reserve RAM buffer [mem 0xbf5fc000-0xbfffffff]
[ 0.415857] e820: reserve RAM buffer [mem 0xbf800000-0xbfffffff]
[ 0.415858] e820: reserve RAM buffer [mem 0x23f800000-0x23fffffff]
[ 0.415918] NetLabel: Initializing
[ 0.415919] NetLabel: domain hash size = 128
[ 0.415919] NetLabel: protocols = UNLABELED CIPSOv4
[ 0.415927] NetLabel: unlabeled traffic allowed by default
[ 0.415940] hpet0: at MMIO 0xfed00000, IRQs 2, 8, 0, 0, 0, 0, 0, 0
[ 0.415942] hpet0: 8 comparators, 64-bit 14.318180 MHz counter
[ 0.417956] Switched to clocksource hpet
[ 0.420722] pnp: PnP ACPI init
[ 0.420798] system 00:00: [mem 0xfed10000-0xfed19fff] has been reserved
[ 0.420799] system 00:00: [mem 0xe0000000-0xefffffff] has been reserved
[ 0.420800] system 00:00: [mem 0xfed90000-0xfed93fff] has been reserved
[ 0.420801] system 00:00: [mem 0xfed20000-0xfed3ffff] has been reserved
[ 0.420802] system 00:00: [mem 0xfee00000-0xfee0ffff] has been reserved
[ 0.420804] system 00:00: Plug and Play ACPI device, IDs PNP0c01 (active)
[ 0.420902] system 00:01: [io 0x0a00-0x0a0f] has been reserved
[ 0.420903] system 00:01: Plug and Play ACPI device, IDs PNP0c02 (active)
[ 0.420993] pnp 00:02: [dma 0 disabled]
[ 0.421016] pnp 00:02: Plug and Play ACPI device, IDs PNP0501 (active)
[ 0.421032] pnp 00:03: Plug and Play ACPI device, IDs PNP0b00 (active)
[ 0.421058] system 00:04: [io 0x04d0-0x04d1] has been reserved
[ 0.421059] system 00:04: Plug and Play ACPI device, IDs PNP0c02 (active)
[ 0.421149] system 00:05: [io 0x0400-0x0453] could not be reserved
[ 0.421150] system 00:05: [io 0x0458-0x047f] has been reserved
[ 0.421151] system 00:05: [io 0x1180-0x119f] has been reserved
[ 0.421152] system 00:05: [io 0x0500-0x057f] has been reserved
[ 0.421153] system 00:05: [mem 0xfed1c000-0xfed1ffff] has been reserved
[ 0.421154] system 00:05: [mem 0xfec00000-0xfecfffff] could not be reserved
[ 0.421155] system 00:05: [mem 0xfed08000-0xfed08fff] has been reserved
[ 0.421157] system 00:05: [mem 0xff000000-0xffffffff] has been reserved
[ 0.421158] system 00:05: Plug and Play ACPI device, IDs PNP0c01 (active)
[ 0.421187] system 00:06: [io 0x0454-0x0457] has been reserved
[ 0.421188] system 00:06: Plug and Play ACPI device, IDs INT3f0d PNP0c02 (active)
[ 0.421295] pnp: PnP ACPI: found 7 devices
[ 0.427004] pci 0000:00:01.0: PCI bridge to [bus 01]
[ 0.427006] pci 0000:00:01.0: bridge window [io 0xe000-0xefff]
[ 0.427007] pci 0000:00:01.0: bridge window [mem 0xfe600000-0xfe6fffff]
[ 0.427009] pci 0000:00:01.0: bridge window [mem 0xc0000000-0xcfffffff 64bit pref]
[ 0.427011] pci 0000:00:1c.0: PCI bridge to [bus 02]
[ 0.427026] pci 0000:03:00.0: PCI bridge to [bus 04]
[ 0.427044] pci 0000:00:1c.4: PCI bridge to [bus 03-04]
[ 0.427053] pci 0000:00:1c.5: PCI bridge to [bus 05]
[ 0.427056] pci 0000:00:1c.5: bridge window [mem 0xfe500000-0xfe5fffff]
[ 0.427063] pci 0000:00:1c.6: PCI bridge to [bus 06]
[ 0.427064] pci 0000:00:1c.6: bridge window [io 0xd000-0xdfff]
[ 0.427070] pci 0000:00:1c.6: bridge window [mem 0xd0000000-0xd00fffff 64bit pref]
[ 0.427075] pci_bus 0000:00: resource 4 [io 0x0000-0x03af]
[ 0.427076] pci_bus 0000:00: resource 5 [io 0x03e0-0x0cf7]
[ 0.427077] pci_bus 0000:00: resource 6 [io 0x03b0-0x03df]
[ 0.427077] pci_bus 0000:00: resource 7 [io 0x0d00-0xffff]
[ 0.427078] pci_bus 0000:00: resource 8 [mem 0x000a0000-0x000bffff]
[ 0.427079] pci_bus 0000:00: resource 9 [mem 0x000c0000-0x000dffff]
[ 0.427080] pci_bus 0000:00: resource 10 [mem 0xc0000000-0xffffffff]
[ 0.427081] pci_bus 0000:01: resource 0 [io 0xe000-0xefff]
[ 0.427082] pci_bus 0000:01: resource 1 [mem 0xfe600000-0xfe6fffff]
[ 0.427083] pci_bus 0000:01: resource 2 [mem 0xc0000000-0xcfffffff 64bit pref]
[ 0.427084] pci_bus 0000:03: resource 4 [io 0x0000-0x03af]
[ 0.427085] pci_bus 0000:03: resource 5 [io 0x03e0-0x0cf7]
[ 0.427086] pci_bus 0000:03: resource 6 [io 0x03b0-0x03df]
[ 0.427087] pci_bus 0000:03: resource 7 [io 0x0d00-0xffff]
[ 0.427087] pci_bus 0000:03: resource 8 [mem 0x000a0000-0x000bffff]
[ 0.427088] pci_bus 0000:03: resource 9 [mem 0x000c0000-0x000dffff]
[ 0.427089] pci_bus 0000:03: resource 10 [mem 0xc0000000-0xffffffff]
[ 0.427090] pci_bus 0000:05: resource 1 [mem 0xfe500000-0xfe5fffff]
[ 0.427091] pci_bus 0000:06: resource 0 [io 0xd000-0xdfff]
[ 0.427092] pci_bus 0000:06: resource 2 [mem 0xd0000000-0xd00fffff 64bit pref]
[ 0.427107] NET: Registered protocol family 2
[ 0.427218] TCP established hash table entries: 65536 (order: 7, 524288 bytes)
[ 0.427305] TCP bind hash table entries: 65536 (order: 8, 1048576 bytes)
[ 0.427411] TCP: Hash tables configured (established 65536 bind 65536)
[ 0.427422] TCP: reno registered
[ 0.427428] UDP hash table entries: 4096 (order: 5, 131072 bytes)
[ 0.427446] UDP-Lite hash table entries: 4096 (order: 5, 131072 bytes)
[ 0.427479] NET: Registered protocol family 1
[ 0.427627] pci 0000:01:00.0: Video device with shadowed ROM
[ 0.427703] PCI: CLS 64 bytes, default 64
[ 0.427731] Unpacking initramfs...
[ 0.458276] Freeing initrd memory: 3368K (ffff88003795c000 - ffff880037ca6000)
[ 0.458282] PCI-DMA: Using software bounce buffering for IO (SWIOTLB)
[ 0.458284] software IO TLB [mem 0xbaa35000-0xbea35000] (64MB) mapped at [ffff8800baa35000-ffff8800bea34fff]
[ 0.458388] RAPL PMU detected, hw unit 2^-16 Joules, API unit is 2^-32 Joules, 3 fixed counters 163840 ms ovfl timer
[ 0.458447] microcode: CPU0 sig=0x206a7, pf=0x2, revision=0x12
[ 0.458451] microcode: CPU1 sig=0x206a7, pf=0x2, revision=0x12
[ 0.458455] microcode: CPU2 sig=0x206a7, pf=0x2, revision=0x12
[ 0.458459] microcode: CPU3 sig=0x206a7, pf=0x2, revision=0x12
[ 0.458489] microcode: Microcode Update Driver: v2.00 <[email protected]>, Peter Oruba
[ 0.458503] Scanning for low memory corruption every 60 seconds
[ 0.458643] futex hash table entries: 1024 (order: 4, 65536 bytes)
[ 0.458653] Initialise system trusted keyring
[ 0.458879] HugeTLB registered 2 MB page size, pre-allocated 0 pages
[ 0.459596] zpool: loaded
[ 0.459598] zbud: loaded
[ 0.459684] VFS: Disk quotas dquot_6.5.2
[ 0.459702] VFS: Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
[ 0.459788] Key type big_key registered
[ 0.459886] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 252)
[ 0.459910] io scheduler noop registered
[ 0.459911] io scheduler deadline registered
[ 0.459926] io scheduler cfq registered (default)
[ 0.460230] pci_hotplug: PCI Hot Plug PCI Core version: 0.5
[ 0.460238] pciehp: PCI Express Hot Plug Controller Driver version: 0.4
[ 0.460245] vesafb: mode is 1400x1050x32, linelength=5632, pages=0
[ 0.460245] vesafb: scrolling: redraw
[ 0.460246] vesafb: Truecolor: size=0:8:8:8, shift=0:16:8:0
[ 0.460257] vesafb: framebuffer at 0xc0000000, mapped to 0xffffc90010e80000, using 5824k, total 5824k
[ 0.507010] Console: switching to colour frame buffer device 175x65
[ 0.553487] fb0: VESA VGA frame buffer device
[ 0.553501] intel_idle: MWAIT substates: 0x1120
[ 0.553502] intel_idle: v0.4 model 0x2A
[ 0.553502] intel_idle: lapic_timer_reliable_states 0xffffffff
[ 0.553594] GHES: HEST is not enabled!
[ 0.553630] Serial: 8250/16550 driver, 4 ports, IRQ sharing disabled
[ 0.574150] 00:02: ttyS0 at I/O 0x3f8 (irq = 4, base_baud = 115200) is a 16550A
[ 0.574369] Linux agpgart interface v0.103
[ 0.574402] rtc_cmos 00:03: RTC can wake from S4
[ 0.574506] rtc_cmos 00:03: rtc core: registered rtc_cmos as rtc0
[ 0.574530] rtc_cmos 00:03: alarms up to one month, y3k, 114 bytes nvram, hpet irqs
[ 0.574537] Intel P-state driver initializing.
[ 0.574635] ledtrig-cpu: registered to indicate activity on CPUs
[ 0.575069] TCP: cubic registered
[ 0.575206] NET: Registered protocol family 10
[ 0.575527] NET: Registered protocol family 17
[ 0.576245] Loading compiled-in X.509 certificates
[ 0.576267] registered taskstats version 1
[ 0.577040] Magic number: 11:338:848
[ 0.577156] rtc_cmos 00:03: setting system clock to 2015-04-22 18:49:17 UTC (1429728557)
[ 0.577255] PM: Hibernation image not present or could not be loaded.
[ 0.577672] Freeing unused kernel memory: 1164K (ffffffff818e7000 - ffffffff81a0a000)
[ 0.577674] Write protecting the kernel read-only data: 8192k
[ 0.578177] Freeing unused kernel memory: 600K (ffff88000156a000 - ffff880001600000)
[ 0.578369] Freeing unused kernel memory: 304K (ffff8800017b4000 - ffff880001800000)
[ 0.586926] random: systemd-tmpfile urandom read with 1 bits of entropy available
[ 0.594161] i8042: PNP: No PS/2 controller found. Probing ports directly.
[ 0.594538] serio: i8042 KBD port at 0x60,0x64 irq 1
[ 0.594602] serio: i8042 AUX port at 0x60,0x64 irq 12
[ 0.596674] ACPI: bus type USB registered
[ 0.596690] usbcore: registered new interface driver usbfs
[ 0.596697] usbcore: registered new interface driver hub
[ 0.596714] usbcore: registered new device driver usb
[ 0.596929] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[ 0.597010] ehci-pci: EHCI PCI platform driver
[ 0.597090] ehci-pci 0000:00:1a.0: EHCI Host Controller
[ 0.597095] ehci-pci 0000:00:1a.0: new USB bus registered, assigned bus number 1
[ 0.597107] ehci-pci 0000:00:1a.0: debug port 2
[ 0.598329] SCSI subsystem initialized
[ 0.600997] ehci-pci 0000:00:1a.0: cache line size of 64 is not supported
[ 0.601009] ehci-pci 0000:00:1a.0: irq 16, io mem 0xfe707000
[ 0.601141] libata version 3.00 loaded.
[ 0.607823] ehci-pci 0000:00:1a.0: USB 2.0 started, EHCI 1.00
[ 0.607929] hub 1-0:1.0: USB hub found
[ 0.607934] hub 1-0:1.0: 2 ports detected
[ 0.608004] xhci_hcd 0000:05:00.0: xHCI Host Controller
[ 0.608009] xhci_hcd 0000:05:00.0: new USB bus registered, assigned bus number 2
[ 0.608319] hub 2-0:1.0: USB hub found
[ 0.608327] hub 2-0:1.0: 2 ports detected
[ 0.608382] xhci_hcd 0000:05:00.0: xHCI Host Controller
[ 0.608384] xhci_hcd 0000:05:00.0: new USB bus registered, assigned bus number 3
[ 0.608386] ehci-pci 0000:00:1d.0: EHCI Host Controller
[ 0.608389] ehci-pci 0000:00:1d.0: new USB bus registered, assigned bus number 4
[ 0.608405] ehci-pci 0000:00:1d.0: debug port 2
[ 0.611688] hub 3-0:1.0: USB hub found
[ 0.611696] hub 3-0:1.0: 2 ports detected
[ 0.612303] ehci-pci 0000:00:1d.0: cache line size of 64 is not supported
[ 0.612313] ehci-pci 0000:00:1d.0: irq 23, io mem 0xfe706000
[ 0.621118] ehci-pci 0000:00:1d.0: USB 2.0 started, EHCI 1.00
[ 0.621236] hub 4-0:1.0: USB hub found
[ 0.621248] hub 4-0:1.0: 2 ports detected
[ 0.621321] ahci 0000:00:1f.2: version 3.0
[ 0.634481] ahci 0000:00:1f.2: AHCI 0001.0300 32 slots 6 ports 6 Gbps 0x3f impl SATA mode
[ 0.634487] ahci 0000:00:1f.2: flags: 64bit ncq sntf pm led clo pio slum part ems apst
[ 0.668448] scsi host0: ahci
[ 0.668750] scsi host1: ahci
[ 0.669100] scsi host2: ahci
[ 0.669412] scsi host3: ahci
[ 0.669697] scsi host4: ahci
[ 0.669967] scsi host5: ahci
[ 0.670051] ata1: SATA max UDMA/133 abar m2048@0xfe705000 port 0xfe705100 irq 30
[ 0.670054] ata2: SATA max UDMA/133 abar m2048@0xfe705000 port 0xfe705180 irq 30
[ 0.670057] ata3: SATA max UDMA/133 abar m2048@0xfe705000 port 0xfe705200 irq 30
[ 0.670059] ata4: SATA max UDMA/133 abar m2048@0xfe705000 port 0xfe705280 irq 30
[ 0.670061] ata5: SATA max UDMA/133 abar m2048@0xfe705000 port 0xfe705300 irq 30
[ 0.670064] ata6: SATA max UDMA/133 abar m2048@0xfe705000 port 0xfe705380 irq 30
[ 0.914200] usb 1-1: new high-speed USB device number 2 using ehci-pci
[ 0.927545] usb 4-1: new high-speed USB device number 2 using ehci-pci
[ 0.987472] ata5: SATA link down (SStatus 0 SControl 300)
[ 0.987497] ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[ 0.987521] ata4: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[ 0.987543] ata2: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[ 0.987563] ata6: SATA link down (SStatus 0 SControl 300)
[ 0.987584] ata3: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
[ 0.987877] ata2.00: supports DRM functions and may not be fully accessible
[ 0.988115] ata3.00: ATAPI: TSSTcorp CDDVDW SH-S243D, SB00, max UDMA/100
[ 0.988210] ata1.00: failed to get NCQ Send/Recv Log Emask 0x1
[ 0.988214] ata1.00: ATA-9: Samsung SSD 840 Series, DXT07B0Q, max UDMA/133
[ 0.988217] ata1.00: 234441648 sectors, multi 16: LBA48 NCQ (depth 31/32), AA
[ 0.988682] ata1.00: failed to get NCQ Send/Recv Log Emask 0x1
[ 0.988746] ata1.00: configured for UDMA/133
[ 0.988881] ata3.00: configured for UDMA/100
[ 0.989027] scsi 0:0:0:0: Direct-Access ATA Samsung SSD 840 7B0Q PQ: 0 ANSI: 5
[ 0.989649] ata4.00: ATA-8: WDC WD1002FAEX-00Z3A0, 05.01D05, max UDMA/133
[ 0.989653] ata4.00: 1953525168 sectors, multi 16: LBA48 NCQ (depth 31/32), AA
[ 0.990752] ata2.00: disabling queued TRIM support
[ 0.990755] ata2.00: ATA-9: Crucial_CT240M500SSD1, MU05, max UDMA/133
[ 0.990757] ata2.00: 468862128 sectors, multi 16: LBA48 NCQ (depth 31/32), AA
[ 0.992466] ata4.00: configured for UDMA/133
[ 0.994299] ata2.00: supports DRM functions and may not be fully accessible
[ 0.997177] ata2.00: disabling queued TRIM support
[ 1.000401] ata2.00: configured for UDMA/133
[ 1.000669] scsi 1:0:0:0: Direct-Access ATA Crucial_CT240M50 MU05 PQ: 0 ANSI: 5
[ 1.001813] scsi 2:0:0:0: CD-ROM TSSTcorp CDDVDW SH-S243D SB00 PQ: 0 ANSI: 5
[ 1.011521] scsi 3:0:0:0: Direct-Access ATA WDC WD1002FAEX-0 1D05 PQ: 0 ANSI: 5
[ 1.015296] ata1.00: Enabling discard_zeroes_data
[ 1.015310] sd 0:0:0:0: [sda] 234441648 512-byte logical blocks: (120 GB/111 GiB)
[ 1.015364] sd 0:0:0:0: [sda] Write Protect is off
[ 1.015367] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
[ 1.015385] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[ 1.015513] sd 1:0:0:0: [sdb] 468862128 512-byte logical blocks: (240 GB/223 GiB)
[ 1.015517] sd 1:0:0:0: [sdb] 4096-byte physical blocks
[ 1.015524] ata1.00: Enabling discard_zeroes_data
[ 1.015532] sd 3:0:0:0: [sdc] 1953525168 512-byte logical blocks: (1.00 TB/931 GiB)
[ 1.015618] sd 3:0:0:0: [sdc] Write Protect is off
[ 1.015621] sd 3:0:0:0: [sdc] Mode Sense: 00 3a 00 00
[ 1.015636] sd 1:0:0:0: [sdb] Write Protect is off
[ 1.015641] sd 1:0:0:0: [sdb] Mode Sense: 00 3a 00 00
[ 1.015657] sd 3:0:0:0: [sdc] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[ 1.015717] sd 1:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[ 1.015779] sda: sda1 sda2
[ 1.016099] ata1.00: Enabling discard_zeroes_data
[ 1.016176] sd 0:0:0:0: [sda] Attached SCSI disk
[ 1.016225] sdb: sdb1
[ 1.016696] sd 1:0:0:0: [sdb] Attached SCSI disk
[ 1.022237] sdc: sdc1 sdc2
[ 1.022726] sd 3:0:0:0: [sdc] Attached SCSI disk
[ 1.025940] sr 2:0:0:0: [sr0] scsi3-mmc drive: 48x/48x writer dvd-ram cd/rw xa/form2 cdda tray
[ 1.025945] cdrom: Uniform CD-ROM driver Revision: 3.20
[ 1.026137] sr 2:0:0:0: Attached scsi CD-ROM sr0
[ 1.038098] hub 1-1:1.0: USB hub found
[ 1.038285] hub 1-1:1.0: 6 ports detected
[ 1.051455] hub 4-1:1.0: USB hub found
[ 1.051648] hub 4-1:1.0: 8 ports detected
[ 1.298000] EXT4-fs (sdb1): mounted filesystem with ordered data mode. Opts: (null)
[ 1.303924] usb 1-1.4: new high-speed USB device number 3 using ehci-pci
[ 1.317239] usb 4-1.2: new full-speed USB device number 3 using ehci-pci
[ 1.443336] systemd[1]: systemd 219 running in system mode. (+PAM -AUDIT -SELINUX -IMA -APPARMOR +SMACK -SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ +LZ4 +SECCOMP +BLKID -ELFUTILS +KMOD +IDN)
[ 1.443537] systemd[1]: Detected architecture 'x86-64'.
[ 1.443740] systemd[1]: Set hostname to <arch>.
[ 1.460317] tsc: Refined TSC clocksource calibration: 3300.020 MHz
[ 1.473794] usb 1-1.5: new high-speed USB device number 4 using ehci-pci
[ 1.497743] systemd[1]: Unit type .busname is not supported on this system.
[ 1.537625] systemd[1]: Set up automount Arbitrary Executable File Formats File System Automount Point.
[ 1.537643] systemd[1]: Starting Arbitrary Executable File Formats File System Automount Point.
[ 1.537662] systemd[1]: Reached target Remote File Systems.
[ 1.537672] systemd[1]: Starting Remote File Systems.
[ 1.537692] systemd[1]: Reached target Encrypted Volumes.
[ 1.537701] systemd[1]: Starting Encrypted Volumes.
[ 1.537748] systemd[1]: Started Forward Password Requests to Wall Directory Watch.
[ 1.537759] systemd[1]: Starting Forward Password Requests to Wall Directory Watch.
[ 1.537800] systemd[1]: Started Dispatch Password Requests to Console Directory Watch.
[ 1.537810] systemd[1]: Starting Dispatch Password Requests to Console Directory Watch.
[ 1.538002] systemd[1]: Created slice Root Slice.
[ 1.538014] systemd[1]: Starting Root Slice.
[ 1.538060] systemd[1]: Listening on /dev/initctl Compatibility Named Pipe.
[ 1.538070] systemd[1]: Starting /dev/initctl Compatibility Named Pipe.
[ 1.538120] systemd[1]: Listening on Journal Socket.
[ 1.538134] systemd[1]: Starting Journal Socket.
[ 1.538265] systemd[1]: Created slice User and Session Slice.
[ 1.538276] systemd[1]: Starting User and Session Slice.
[ 1.545589] systemd[1]: Listening on Journal Audit Socket.
[ 1.545747] systemd[1]: Created slice System Slice.
[ 1.545765] systemd[1]: Starting System Slice.
[ 1.546248] systemd[1]: Mounting Huge Pages File System...
[ 1.546789] systemd[1]: Mounting Debug File System...
[ 1.546970] systemd[1]: Created slice system-dhcpcd.slice.
[ 1.546987] systemd[1]: Starting system-dhcpcd.slice.
[ 1.547561] systemd[1]: Starting Create list of required static device nodes for the current kernel...
[ 1.548678] systemd[1]: Starting Setup Virtual Console...
[ 1.549285] systemd[1]: Started Set Up Additional Binary Formats.
[ 1.550613] systemd[1]: Starting Load Kernel Modules...
[ 1.550645] systemd[1]: Started File System Check on Root Device.
[ 1.551159] systemd[1]: Starting Remount Root and Kernel File Systems...
[ 1.551679] systemd[1]: Mounting POSIX Message Queue File System...
[ 1.551836] systemd[1]: Created slice system-getty.slice.
[ 1.551850] systemd[1]: Starting system-getty.slice.
[ 1.551870] systemd[1]: Reached target Slices.
[ 1.551883] systemd[1]: Starting Slices.
[ 1.551931] systemd[1]: Listening on udev Kernel Socket.
[ 1.551941] systemd[1]: Starting udev Kernel Socket.
[ 1.551986] systemd[1]: Listening on Journal Socket (/dev/log).
[ 1.551997] systemd[1]: Starting Journal Socket (/dev/log).
[ 1.552492] systemd[1]: Starting Journal Service...
[ 1.552545] systemd[1]: Listening on Device-mapper event daemon FIFOs.
[ 1.552561] systemd[1]: Starting Device-mapper event daemon FIFOs.
[ 1.552600] systemd[1]: Listening on udev Control Socket.
[ 1.552611] systemd[1]: Starting udev Control Socket.
[ 1.552659] systemd[1]: Listening on LVM2 metadata daemon socket.
[ 1.552669] systemd[1]: Starting LVM2 metadata daemon socket.
[ 1.552689] systemd[1]: Reached target Login Prompts.
[ 1.552701] systemd[1]: Starting Login Prompts.
[ 1.553185] systemd[1]: Starting udev Coldplug all Devices...
[ 1.553231] systemd[1]: Listening on Delayed Shutdown Socket.
[ 1.553249] systemd[1]: Starting Delayed Shutdown Socket.
[ 1.554439] EXT4-fs (sdb1): re-mounted. Opts: data=ordered
[ 1.555736] systemd[1]: Mounting Temporary Directory...
[ 1.556329] systemd[1]: Mounted POSIX Message Queue File System.
[ 1.556363] systemd[1]: Mounted Huge Pages File System.
[ 1.556388] systemd[1]: Mounted Debug File System.
[ 1.556779] systemd[1]: Started Create list of required static device nodes for the current kernel.
[ 1.557030] systemd[1]: Started Setup Virtual Console.
[ 1.557256] systemd[1]: Started Remount Root and Kernel File Systems.
[ 1.557431] systemd[1]: Mounted Temporary Directory.
[ 1.558591] hub 1-1.5:1.0: USB hub found
[ 1.558901] hub 1-1.5:1.0: 4 ports detected
[ 1.560366] vboxdrv: Found 4 processor cores.
[ 1.561065] vboxdrv: fAsync=0 offMin=0x2ca offMax=0x6c0c
[ 1.561137] vboxdrv: TSC mode is 'synchronous', kernel timer mode is 'normal'.
[ 1.561139] vboxdrv: Successfully loaded version 4.3.26_OSE (interface 0x001a000a).
[ 1.561712] systemd[1]: Started Load Kernel Modules.
[ 1.568012] systemd-journald[149]: Failed to set file attributes: Inappropriate ioctl for device
[ 1.569830] systemd[1]: Started udev Coldplug all Devices.
[ 1.575918] systemd[1]: Mounted FUSE Control File System.
[ 1.576374] systemd[1]: Mounting Configuration File System...
[ 1.576805] systemd[1]: Starting Apply Kernel Variables...
[ 1.576856] systemd[1]: Started Rebuild Dynamic Linker Cache.
[ 1.582712] systemd[1]: Started Rebuild Hardware Database.
[ 1.582739] systemd[1]: Started First Boot Wizard.
[ 1.582757] systemd[1]: Started Create System Users.
[ 1.583212] systemd[1]: Starting Load/Save Random Seed...
[ 1.583784] systemd[1]: Starting Create Static Device Nodes in /dev...
[ 1.584599] systemd[1]: Mounted Configuration File System.
[ 1.587256] systemd[1]: Started Load/Save Random Seed.
[ 1.589801] systemd[1]: Started Apply Kernel Variables.
[ 1.607967] systemd[1]: Started Create Static Device Nodes in /dev.
[ 1.608452] systemd[1]: Starting udev Kernel Device Manager...
[ 1.608476] systemd[1]: Reached target Local File Systems (Pre).
[ 1.608492] systemd[1]: Starting Local File Systems (Pre).
[ 1.626961] usb 1-1.6: new low-speed USB device number 5 using ehci-pci
[ 1.637443] systemd[1]: Started udev Kernel Device Manager.
[ 1.649393] systemd[1]: Started Journal Service.
[ 1.653641] systemd-journald[149]: Received request to flush runtime journal from PID 1
[ 1.813303] input: Power Button as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input2
[ 1.813310] ACPI: Power Button [PWRB]
[ 1.813368] input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input3
[ 1.813371] ACPI: Power Button [PWRF]
[ 1.817850] wmi: Mapper loaded
[ 1.855141] shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
[ 1.872038] r8169 Gigabit Ethernet driver 2.3LK-NAPI loaded
[ 1.872046] r8169 0000:06:00.0: can't disable ASPM; OS doesn't have ASPM control
[ 1.877249] r8169 0000:06:00.0 eth0: RTL8168evl/8111evl at 0xffffc90000c7a000, 8c:89:a5:16:c4:7d, XID 0c900800 IRQ 32
[ 1.877252] r8169 0000:06:00.0 eth0: jumbo features [frames: 9200 bytes, tx checksumming: ko]
[ 1.880259] i801_smbus 0000:00:1f.3: SMBus using PCI interrupt
[ 1.907839] [drm] Initialized drm 1.1.0 20060810
[ 1.910066] input: PC Speaker as /devices/platform/pcspkr/input/input5
[ 1.911296] hidraw: raw HID events driver (C) Jiri Kosina
[ 1.912890] snd_hda_intel 0000:01:00.1: Handle VGA-switcheroo audio client
[ 1.913064] fuse init (API version 7.23)
[ 1.914070] usblp 1-1.4:1.0: usblp0: USB Bidirectional printer dev 3 if 0 alt 0 proto 2 vid 0x04F9 pid 0x024A
[ 1.914093] usbcore: registered new interface driver usblp
[ 1.916048] AVX version of gcm_enc/dec engaged.
[ 1.916050] AES CTR mode by8 optimization enabled
[ 1.924639] input: HDA ATI HDMI HDMI/DP,pcm=3 as /devices/pci0000:00/0000:00:01.0/0000:01:00.1/sound/card1/input6
[ 1.925198] usbcore: registered new interface driver usbhid
[ 1.925200] usbhid: USB HID core driver
[ 1.926129] sound hdaudioC0D1: autoconfig: line_outs=4 (0x14/0x15/0x16/0x17/0x0) type:line
[ 1.926132] sound hdaudioC0D1: speaker_outs=0 (0x0/0x0/0x0/0x0/0x0)
[ 1.926133] sound hdaudioC0D1: hp_outs=1 (0x1b/0x0/0x0/0x0/0x0)
[ 1.926134] sound hdaudioC0D1: mono: mono_out=0x0
[ 1.926136] sound hdaudioC0D1: dig-out=0x11/0x1e
[ 1.926137] sound hdaudioC0D1: inputs:
[ 1.926139] sound hdaudioC0D1: Front Mic=0x19
[ 1.926140] sound hdaudioC0D1: Rear Mic=0x18
[ 1.926142] sound hdaudioC0D1: Line=0x1a
[ 1.934672] iTCO_vendor_support: vendor-support=0
[ 1.934826] [drm] radeon kernel modesetting enabled.
[ 1.935110] iTCO_wdt: Intel TCO WatchDog Timer Driver v1.11
[ 1.935141] iTCO_wdt: Found a Cougar Point TCO device (Version=2, TCOBASE=0x0460)
[ 1.935229] iTCO_wdt: initialized. heartbeat=30 sec (nowayout=0)
[ 1.939587] r8169 0000:06:00.0 enp6s0: renamed from eth0
[ 1.939661] gpio_ich: GPIO from 436 to 511 on gpio_ich
[ 1.941371] logitech-djreceiver 0003:046D:C52B.0003: hiddev0,hidraw0: USB HID v1.11 Device [Logitech USB Receiver] on usb-0000:00:1d.0-1.2/input2
[ 1.941824] AMD IOMMUv2 driver by Joerg Roedel <[email protected]>
[ 1.941825] AMD IOMMUv2 functionality not available on this system
[ 1.943447] CRAT table not found
[ 1.943449] Finished initializing topology ret=0
[ 1.943479] kfd kfd: Initialized module
[ 1.943669] checking generic (c0000000 5b0000) vs hw (c0000000 10000000)
[ 1.943670] fb: switching to radeondrmfb from VESA VGA
[ 1.943685] Console: switching to colour dummy device 80x25
[ 1.943797] random: nonblocking pool is initialized
[ 1.943880] [drm] initializing kernel modesetting (CAYMAN 0x1002:0x6719 0x1787:0x2307).
[ 1.943890] [drm] register mmio base: 0xFE620000
[ 1.943891] [drm] register mmio size: 131072
[ 1.943923] ATOM BIOS: CAYMAN
[ 1.943974] radeon 0000:01:00.0: VRAM: 2048M 0x0000000000000000 - 0x000000007FFFFFFF (2048M used)
[ 1.943975] radeon 0000:01:00.0: GTT: 1024M 0x0000000080000000 - 0x00000000BFFFFFFF
[ 1.943977] [drm] Detected VRAM RAM=2048M, BAR=256M
[ 1.943977] [drm] RAM width 256bits DDR
[ 1.944037] [TTM] Zone kernel: Available graphics memory: 4075924 kiB
[ 1.944038] [TTM] Zone dma32: Available graphics memory: 2097152 kiB
[ 1.944039] [TTM] Initializing pool allocator
[ 1.944043] [TTM] Initializing DMA pool allocator
[ 1.944058] [drm] radeon: 2048M of VRAM memory ready
[ 1.944059] [drm] radeon: 1024M of GTT memory ready.
[ 1.944068] [drm] Loading CAYMAN Microcode
[ 1.946470] input: HDA Intel PCH Front Mic as /devices/pci0000:00/0000:00:1b.0/sound/card0/input7
[ 1.946562] input: HDA Intel PCH Rear Mic as /devices/pci0000:00/0000:00:1b.0/sound/card0/input8
[ 1.946609] input: HDA Intel PCH Line as /devices/pci0000:00/0000:00:1b.0/sound/card0/input9
[ 1.946674] input: HDA Intel PCH Line Out Front as /devices/pci0000:00/0000:00:1b.0/sound/card0/input10
[ 1.946720] input: HDA Intel PCH Line Out Surround as /devices/pci0000:00/0000:00:1b.0/sound/card0/input11
[ 1.946769] EXT4-fs (sdc2): mounted filesystem with ordered data mode. Opts: (null)
[ 1.946769] input: HDA Intel PCH Line Out CLFE as /devices/pci0000:00/0000:00:1b.0/sound/card0/input12
[ 1.946809] input: HDA Intel PCH Line Out Side as /devices/pci0000:00/0000:00:1b.0/sound/card0/input13
[ 1.946849] input: HDA Intel PCH Front Headphone as /devices/pci0000:00/0000:00:1b.0/sound/card0/input14
[ 1.951281] [drm] Internal thermal controller with fan control
[ 1.955166] [drm] radeon: dpm initialized
[ 1.955974] [drm] GART: num cpu pages 262144, num gpu pages 262144
[ 1.956619] input: Lite-On Technology Corp. Goldtouch USB Keyboard as /devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.6/1-1.6:1.0/0003:04CA:005B.0004/input/input15
[ 1.957600] [drm] enabling PCIE gen 2 link speeds, disable with radeon.pcie_gen2=0
[ 1.957733] intel_rapl: Found RAPL domain package
[ 1.957736] intel_rapl: Found RAPL domain core
[ 1.978933] [drm] PCIE GART of 1024M enabled (table at 0x0000000000274000).
[ 1.979020] radeon 0000:01:00.0: WB enabled
[ 1.979022] radeon 0000:01:00.0: fence driver on ring 0 use gpu addr 0x0000000080000c00 and cpu addr 0xffff880234d8bc00
[ 1.979798] radeon 0000:01:00.0: fence driver on ring 5 use gpu addr 0x0000000000072118 and cpu addr 0xffffc90010f32118
[ 1.979800] radeon 0000:01:00.0: fence driver on ring 1 use gpu addr 0x0000000080000c04 and cpu addr 0xffff880234d8bc04
[ 1.979801] radeon 0000:01:00.0: fence driver on ring 2 use gpu addr 0x0000000080000c08 and cpu addr 0xffff880234d8bc08
[ 1.979802] radeon 0000:01:00.0: fence driver on ring 3 use gpu addr 0x0000000080000c0c and cpu addr 0xffff880234d8bc0c
[ 1.979804] radeon 0000:01:00.0: fence driver on ring 4 use gpu addr 0x0000000080000c10 and cpu addr 0xffff880234d8bc10
[ 1.979805] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
[ 1.979806] [drm] Driver supports precise vblank timestamp query.
[ 1.979807] radeon 0000:01:00.0: radeon: MSI limited to 32-bit
[ 1.979844] radeon 0000:01:00.0: radeon: using MSI.
[ 1.980067] [drm] radeon: irq initialized.
[ 1.998991] [drm] ring test on 0 succeeded in 2 usecs
[ 1.998999] [drm] ring test on 3 succeeded in 4 usecs
[ 1.999006] [drm] ring test on 4 succeeded in 4 usecs
[ 2.010399] hid-generic 0003:04CA:005B.0004: input,hidraw1: USB HID v1.10 Keyboard [Lite-On Technology Corp. Goldtouch USB Keyboard] on usb-0000:00:1a.0-1.6/input0
[ 2.012308] input: Lite-On Technology Corp. Goldtouch USB Keyboard as /devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.6/1-1.6:1.1/0003:04CA:005B.0005/input/input16
[ 2.069928] input: Logitech M570 as /devices/pci0000:00/0000:00:1d.0/usb4/4-1/4-1.2/4-1.2:1.2/0003:046D:C52B.0003/0003:046D:1028.0006/input/input17
[ 2.080530] Adding 4194300k swap on /mnt/LinuxStorage/swap. Priority:-1 extents:4 across:4464636k FS
[ 2.116506] hid-generic 0003:04CA:005B.0005: input,hiddev0,hidraw2: USB HID v1.10 Device [Lite-On Technology Corp. Goldtouch USB Keyboard] on usb-0000:00:1a.0-1.6/input1
[ 2.116542] logitech-hidpp-device 0003:046D:1028.0006: input,hidraw3: USB HID v1.11 Mouse [Logitech M570] on usb-0000:00:1d.0-1.2:1
[ 2.118008] mousedev: PS/2 mouse device common for all mice
[ 2.175912] [drm] ring test on 5 succeeded in 2 usecs
[ 2.175917] [drm] UVD initialized successfully.
[ 2.176481] [drm] ib test on ring 0 succeeded in 0 usecs
[ 2.176922] [drm] ib test on ring 3 succeeded in 0 usecs
[ 2.177365] [drm] ib test on ring 4 succeeded in 0 usecs
[ 2.328709] [drm] ib test on ring 5 succeeded
[ 2.329264] [drm] Radeon Display Connectors
[ 2.329265] [drm] Connector 0:
[ 2.329266] [drm] DP-1
[ 2.329267] [drm] HPD5
[ 2.329268] [drm] DDC: 0x6430 0x6430 0x6434 0x6434 0x6438 0x6438 0x643c 0x643c
[ 2.329268] [drm] Encoders:
[ 2.329269] [drm] DFP1: INTERNAL_UNIPHY2
[ 2.329269] [drm] Connector 1:
[ 2.329270] [drm] DP-2
[ 2.329270] [drm] HPD4
[ 2.329271] [drm] DDC: 0x6440 0x6440 0x6444 0x6444 0x6448 0x6448 0x644c 0x644c
[ 2.329271] [drm] Encoders:
[ 2.329272] [drm] DFP2: INTERNAL_UNIPHY2
[ 2.329272] [drm] Connector 2:
[ 2.329273] [drm] HDMI-A-1
[ 2.329273] [drm] HPD6
[ 2.329274] [drm] DDC: 0x6460 0x6460 0x6464 0x6464 0x6468 0x6468 0x646c 0x646c
[ 2.329274] [drm] Encoders:
[ 2.329275] [drm] DFP3: INTERNAL_UNIPHY1
[ 2.329275] [drm] Connector 3:
[ 2.329276] [drm] DVI-D-1
[ 2.329276] [drm] HPD1
[ 2.329277] [drm] DDC: 0x6450 0x6450 0x6454 0x6454 0x6458 0x6458 0x645c 0x645c
[ 2.329277] [drm] Encoders:
[ 2.329278] [drm] DFP4: INTERNAL_UNIPHY1
[ 2.329278] [drm] Connector 4:
[ 2.329279] [drm] DVI-I-1
[ 2.329279] [drm] HPD3
[ 2.329280] [drm] DDC: 0x6470 0x6470 0x6474 0x6474 0x6478 0x6478 0x647c 0x647c
[ 2.329280] [drm] Encoders:
[ 2.329281] [drm] DFP5: INTERNAL_UNIPHY
[ 2.329282] [drm] CRT1: INTERNAL_KLDSCP_DAC1
[ 2.408814] [drm] fb mappable at 0xC0475000
[ 2.408816] [drm] vram apper at 0xC0000000
[ 2.408816] [drm] size 8294400
[ 2.408817] [drm] fb depth is 24
[ 2.408818] [drm] pitch is 7680
[ 2.408899] fbcon: radeondrmfb (fb0) is primary device
[ 2.435470] Console: switching to colour frame buffer device 240x67
[ 2.438497] radeon 0000:01:00.0: fb0: radeondrmfb frame buffer device
[ 2.438498] radeon 0000:01:00.0: registered panic notifier
[ 2.449565] [drm] Initialized radeon 2.40.0 20080528 for 0000:01:00.0 on minor 0
[ 2.459456] Switched to clocksource tsc
[ 2.490495] cfg80211: Calling CRDA to update world regulatory domain
[ 2.687833] r8169 0000:06:00.0 enp6s0: link down
[ 2.687846] r8169 0000:06:00.0 enp6s0: link down
[ 2.687870] IPv6: ADDRCONF(NETDEV_UP): enp6s0: link is not ready
[ 20.764979] r8169 0000:06:00.0 enp6s0: link up
[ 20.764992] IPv6: ADDRCONF(NETDEV_CHANGE): enp6s0: link becomes ready
[ 256.173829] device-mapper: uevent: version 1.0.3
[ 256.173991] device-mapper: ioctl: 4.29.0-ioctl (2014-10-28) initialised: [email protected]
[ 256.713510] SGI XFS with ACLs, security attributes, realtime, no debug enabled
[ 256.718933] JFS: nTxBlock = 8192, nTxLock = 65536
[ 256.730155] ntfs: driver 2.1.31 [Flags: R/W MODULE].
[ 256.800019] raid6: sse2x1 7801 MB/s
[ 256.856622] raid6: sse2x2 11630 MB/s
[ 256.913233] raid6: sse2x4 15648 MB/s
[ 256.913234] raid6: using algorithm sse2x4 (15648 MB/s)
[ 256.913235] raid6: using ssse3x2 recovery algorithm
[ 256.913829] xor: automatically using best checksumming function:
[ 256.946535] avx : 32756.400 MB/sec
[ 256.954986] Btrfs loaded
[ 603.210136] watchdog watchdog0: watchdog did not stop!
[ 603.211033] systemd-shutdown[1]: Sending SIGTERM to remaining processes...
[ 603.244960] systemd-journald[149]: Received SIGTERM from PID 1 (systemd-shutdow).
[ 603.321496] systemd-shutdown[1]: Sending SIGKILL to remaining processes...
[ 603.325328] systemd-shutdown[1]: Hardware watchdog 'iTCO_wdt', version 0
[ 603.325462] systemd-shutdown[1]: Unmounting file systems.
[ 603.393079] EXT4-fs (sdb1): re-mounted. Opts: (null)
[ 603.402416] EXT4-fs (sdb1): re-mounted. Opts: (null)
[ 603.402433] systemd-shutdown[1]: All filesystems unmounted.
[ 603.402438] systemd-shutdown[1]: Deactivating swaps.
[ 603.402507] systemd-shutdown[1]: All swaps deactivated.
[ 603.402511] systemd-shutdown[1]: Detaching loop devices.
[ 603.403097] systemd-shutdown[1]: All loop devices detached.
[ 603.403101] systemd-shutdown[1]: Detaching DM devices.
[ 603.403156] systemd-shutdown[1]: All DM devices detached.
[ 603.412388] EXT4-fs (sdb1): re-mounted. Opts: data=ordered
Would appreciate some input regarding this. Thanks!
EDIT: This is on gnome 3.16. Not sure if that matters.
Last edited by devrepublic (2015-05-13 03:24:19)ksu wrote:Thanks alot for the input guys. Since I want to start from scratch anyways I'll definitively dig deeper into the subject. BTRFS snapshot feature and RAID1 by simply mirroring two partitions sound awesome, and the subvolume feature seems to be exactly what I need for my USB setup, giving me alot of flexibility. But if there are really that many reports of random data loss then I'll also do some research into that direction to see what this is all about. I admit I'm a linux noob, but it's a lot of fun to learn all this stuff.
Be sure to read this: https://btrfs.wiki.kernel.org/index.php/Gotchas
From my own experience, I can say that:
1. I've never had an issue nor data loss with BTRFS RAID1 root partition on a single disk (other than the first issue on the above list).
2. I had recurring problems with BTRFS RAID1 non-root partition on a single disk not being able to mount (had to reboot random number of times to get it to mount). However, I suspect this was caused not just by BTRFS but the combination of BTRFS+LVM+dmcrypt which is a rather complex and unusual setup. I had somewhat similar issue with ZFS.
3. I had BTRFS checkdisk report strange, non-critical, unfixable errors on my non-raid BTRFS root partition, but it never corrupted or lost any data. I simply copied the data to another partition, recreated the root partition and all was fine again.
4. The last time I lost data on a single partition because of BTRFS was 17 months ago. The last time BTRFS snapshot saved me from losing data was yesterday.
5. I migrated from BTRFS to ZFS for my backup server and will possibly do so for my work machines. ZFS is more elegant, mature and I have seen no complaints of losing data because of it. However, ZFS is complicated and somewhat restrictive to setup for a data partition, and many times more difficult to setup as root partition. I would not consider it for a non-permanent USB installation.
6. What we committed here is a massive thread hijacking.
Last edited by Lockheed (2015-04-24 05:27:51)
Maybe you are looking for
-
Why selecting text and hitting F1 doesn't go to specific help page anymore?
Hi. Up until a while ago I was able to, while working on some code, select a particular actionscript component such as a Class, function or property and hit the F1 key which would immediately bring up Adobe Help in my internet browser already show
-
I have a new Epson wireless printer connected and the iPad recognizes it but it still won't print. What is AirPrint & how do I connect to it?
-
100% swap, how to reduce its usage?
Hi All, Hoping you could offer some suggestions. RAM --> 256 GB oracle 11.2.0.2 on RHEL 5.7 has 2 databases on this database server, with each allocated 50GB.(MEMORY_MAX_TARGET=MEMORY_TARGET=50G) free -h lnx133:/app/oracle/product/agent11.2:>free -g
-
SQL execution taking long time
All, I have a read only VO and i have configured the VO to print the SQL getting executed along with bind parameters. The SQL is taking a lot of time to execute when running in web. When i run the generated SQL in toad it takes close to 30.6 seconds,
-
Programmitically call a task flow commit
I'd like to execute a task flow commit from a method inside an application module impl class. How can I get a handle on a task flow and invoke the commit in my code? Any insight appreciated.