Unable to use device as an iSCSI target

My intended purpose is to have iSCSI targets for a virtualbox setup at home where block devices are for the systems and existing data on a large RAID partition is exported as well. I'm able to successfully export the block files by using dd and added them as a backing-store into the targets.conf file:
include /etc/tgt/temp/*.conf
default-driver iscsi
<target iqn.2012-09.net.domain:vm.fsrv>
backing-store /srv/vm/disks/iscsi-disk-fsrv
</target>
<target iqn.2012-09.net.domain:vm.wsrv>
backing-store /srv/vm/disks/iscsi-disk-wsrv
</target>
<target iqn.2012-09.net.domain:lan.storage>
backing-store /dev/md0
</target>
but the last one with /dev/md0 only creates the controller and not the disk.
The RAID device is mounted, I don't whether or not that matters, unfortunately I can't try it being unmounted yet because it is in use. I've tried all permutations of backing-store and direct-store with md0 as well as another device (sda) with and without the partition number, all had the same result.
If anyone has been successful exporting a device (specifically a multi disk) I'd be real interested in knowing how. Also, if anyone knows how, or if it's even possible, to use a directory as the backing/direct store I'd like to know that as well, my attempts there have been unsuccessful as well.
I will preempt anyone asking why I'm not using some other technology, eg. NFS, CIFS, ZFS, etc., by saying that this is largely academic. I want to compare the performance that a virtualized file server has that receives it's content being served by both NFS and iSCSI, and the NFS part is easy.
Thanks.

Mass storage only looks at the memory expansion.
Did you have a micro SD card in it?
What OS on the PC are you running?
Click here to Backup the data on your BlackBerry Device! It's important, and FREE!
Click "Accept as Solution" if your problem is solved. To give thanks, click thumbs up
Click to search the Knowledge Base at BTSC and click to Read The Fabulous Manuals
BESAdmin's, please make a signature with your BES environment info.
SIM Free BlackBerry Unlocking FAQ
Follow me on Twitter @knottyrope
Want to thank me? Buy my KnottyRope App here
BES 12 and BES 5.0.4 with Exchange 2010 and SQL 2012 Hyper V

Similar Messages

Unable To Use Device Switch Wizard

Hello,
I just bought a new Tour and want to migrate my data from my Palm Centro to the Blackberry. I have tried using a PC with Vista x64, Vista x32 and XP Pro. For whatever reason, the program doesn't see Palm Desktop or the Centro. Anyone have any ideas?
MIke

Hi and Welcome to the Forums!
I seem to recall others reporting something similar...see this KB:
KB05459 How to use the Switch Device Wizard to switch from another smartphone to a BlackBerry smartphone
Unfortunately, the Centro is not listed. But, all may not be lost...see these KB's:
KB10722 BlackBerry Desktop Manager does not detect the Palm software when using the Switch Device Wizard
KB04437 How to use the organizer data migration wizard
KB04346 Field mapping list for the PIM Data Migration Wizard
And, if all else fails, you can attempt to use your Palm software to export to ASCII or CSV, and then import that via the RIM software:
KB04312 Create and synchronize with an ASCII export file
Good luck and let us know how it goes!
Cheers!
Occam's Razor nearly always applies when troubleshooting technology issues!
If anyone has been helpful to you, please show your appreciation by clicking the button inside of their post. Please click here and read, along with the threads to which it links, for helpful information to guide you as you proceed. I always recommend that you treat your BlackBerry like any other computing device, including using a regular backup schedule...click here for an article with instructions.
Join our BBM Channels
BSCF General Channel
PIN: C0001B7B4 Display/Scan Bar Code
Knowledge Base Updates
PIN: C0005A9AA Display/Scan Bar Code

Ix4-300D as iSCSI target cause alert disk is full

I am using ix4-300D with RAID5 as iSCSI target.
Once I create largest volume using all capacity, ix4-300D sends warning disk is full. Because we monitor this iSCSI target using E-mail alert, I want to eliminate this warning message. There is no configuration point on Web management GUI.
I guess other people using this unit as iSCSI target have same concern. If you know something, please help me about this. Thanks in advance.
Alert message:
The amount of free space on your Lenovo ix4-300d is below 10% of your total capacity.

Thank you for your reply.
I gave up to use 11% of diskspace as iSCSI target of VMware ESXi because catching alert message is more important for production environment. I hoped interface to disable some type of alerts.
I am not sure about using remained 11% space for NFS NAS or something. It is because iSCSI Target volume will contain VM Guest OS volumes which require very stable operation.

ISCSI Target Issues

I am running MS Server 2012 and am only using this as a iscsi target server. I run VMware vspher 5.5 as the initiator. So every night around 12:30 am, my server restarts many of the services, one of them being the iscsi target service. No
errors are produced, just informational logs about the services stopping and starting again. However, when they stop my vphere client and vm's on the iscsi target lose connection. I just want them to run all the time, these are production systems.
When I come in the next day I just do a refresh on the iscsi target gui and everything reconnects. Then I have to go to the vsphere client and answer the guest question about why they lost contact with the targets and the vm's all restart without
a problem. Does anyone know about this problem and how to resolve it?

No, but I think 2012 has built in virus checker, I'll check that. Nope, but this is the info log published.
At 12:31 I got "The Microsoft iSCSI Software Target service entered the stopped state." Then when I came in this morning and hit refresh at 6:01 I got "The Microsoft iSCSI Software Target
service entered the running state.". Both were the event id below. Sometimes it puts it back in the running state automatically, but sometimes I have to manually do it, either way, when it goes into stopped state my vsphere client makes me
answer the "guest" question to bring it back live in the vmware client side. Checked antivirus, no problems there. Again, these are not errors, they a re calling these basic service operations as shown below. How can shutting down
productions systems be a normal operation, must be some way around that or who would want to use this. The nice thing is how easy it is to set up a target, but this is a problem. People use are systems around the clock sooo...any other thoughts?
Event ID 7036 — Basic Service Operations
73 out of 202 rated this helpful - Rate this topic
Updated: December 11, 2007
Applies To: Windows Server 2008
green
Service Control Manager transmits control requests to running services and driver services. It also maintains status information about those services, and reports configuration changes and state changes.
Event Details
Product: Windows Operating System
ID: 7036
Source: Service Control Manager
Version: 6.0
Symbolic Name: EVENT_SERVICE_STATUS_SUCCESS
Message: The %1 service entered the %2 state.
Resolve
This is a normal condition. No further action is required.
Related Management Information
Basic Service Operations
Core Operating System
So how c

Unable to expand/extend partition after growing SAN-based iSCSI target

Hello, all. I have odd situation regarding how to expand iSCSI-based partitions.
Here is my setup:
I use the GlobalSAN iSCSI initiator on 10.6.x server (Snow Leopard).
The iSCSI LUN is formatted with the GPT partition table.
The filesystem is Journaled HFS+
My iSCSI SAN has the ability to non-destructively grow a LUN (iSCSI target).
With this in mind, I wanted to experiment with growing a LUN/target on the SAN and then expanding the Apple partition within it using disk utility. I have been unable to do so.
Here is my procedure:
1) Eject the disk (iSCSI targets show up as external hard drives)
2) Disconnect the iSCSI target using the control panel applet (provided by GlobalSAN)
3) Grow the LUN/target on the SAN.
4) Reconnect the iSCSI initiator
5) Expand/extend the partition using Disk Utility to consume the (newly created) free space.
It works until the last step. When I reconnect to the iSCSI target after expanding it on the SAN, it shows up Disk Utility as being larger than it was (so far, so expected). When I go to expand the partition, however, it errors out saying that there is not enough space.
Investigating further, I went the command line and performed a
"diskutil resizeVolume <identifier> limits"
to determine what the limit was to the partition. The limits did NOT reflect the newly-created space.
My suspicion is that the original partition map, since it was created as 100% of the volume, does not allow room for growth despite the fact that the disk suddenly (and, to the system, unexpectedly) became larger.
Is this assumption correct? Is there any way around this? I would like to be able to expand my LUNs/targets (since the SAN can grow with the business), but this has no value if I cannot also extend the partition table to use the new space.
If anyone has any insight, I would greatly appreciate it. Thank you!

I have exactly the same problem that you describe above. My iSCSI LUN was near capacity and therefore i extended the iSCSI LUN from 100G to 150G. No problem so far.
Disk Utility shows the iSCSI device as 150G but i cannot extend the volume to the new size. It gives me the same error (in Dutch).
Please someone help us out !

First off, i think it's sad that i have to use my non apple device to post this question... Why has my iPad become absolutely useless after updating to iOS 8.1? I am unable to use my mini because it crashes, slow performance, major battery drain.

First off, i think it's sad that i have to use my non apple device to post this question... Why has my iPad become absolutely useless after updating to iOS 8.1? I am unable to use my mini because it crashes, slow performance, major battery drain.

Restore iPad to Factory Default; do not restore from backup. It may be the cause of the problem.
Settings>General>Reset>Erase all content and settings

Since yesterday I have been unable to use FaceTime across all my Apple devices: Iphone 5s, MAC Notebook, and Ipad Mini. It does not connect nor make the ringing sound. Why is this and how can it be fixed?

since yesterday I have been unable to use FaceTime across all my Apple devices: Iphone 5s, MAC Notebook, and Ipad Mini. It does not connect nor make the ringing sound. Why is this and how can it be fixed?

I am haveing same problem canot find itunes.msi

How to create iSCSI target using the entire drive?

This sounds silly, but after setting up the DL4100 in RAID 5, I could not assign the entire 11.89TB to an iSCSI target... Only integer numbers seem to be the valid input. And the only choice of TB or GB offered no help because I could not enter: 11890 GB either?! What am I missing?

Thanks to all who have responded....
Here's my take: 4TB x4 in RAID 5 = 11.89TB but via iSCSI creation will result in 0.89TB unallocable to iSCSI due to the GUI disabling non-interger values (ie: no decimal points). That is 890GB of storage that is supposedly used for firmware upgrades, logs, etc?!
Snooping around I noticed that the validation is only performed via javascript and a quick re-POST to the unit of the params can trigger modification/creation of a non-integer iSCSI volume sizes. Please note that you can only grow volume sizes and not shrink them! Below is a walk-thru of how to do this:
Disclaimer: *WARNING: USE AT YOUR OWN RISK*
1) Create the iSCSI volume as per normal but at the integer value less than what you intend (eg: if you wanted 1.5TB, create 1TB) then wait for the iSCSI volume to be created.
2) Use a web browser with debugging turned on and capturing traffic. For my example I am using Firefox and hit F12 to fire up the debug tool. Pick "Network" and you will see Firefox start picking up all traffic to the DL4100.
3) Go into the iSCSI volume and choose "Details" to modify it. Put the current size as the modified size and click "Apply". Look in the list of messages to locate a POST message "iscsi_mgr.cgi" that has a Request body with a "size" parameter and select that to be resent.
4) In this copy of the same message, look in Request Body and the list of parameters being passed back to the unit. You should find one of the parameters called "size". This value is sent to the unit in GB... Change the value to a GB value that you desire (eg: 1TB would appear as "1000", so you can change it to "1500" for 1.5TB) and then re-POST this POST message back to the unit.
5) Wait for the update to transact and verify that your iSCSI volume has indeed been resized to a "non-Integer" TB value.
That's it! I hope this helps others who have been trapped by this limitation. Please be mindfull not to allocate all your dive space since as Bill_S has mentioned, some space is required by the system for its own housekeeping operations.
Good Luck!

Unable to connect to iSCSI target from PC

We have just installed Storage Server 2012 R2 on a disk array box with 4TB of storage. We installed and configured the iSCSI server software and created a LUN. In Server Manager > File ans Storage Services > iSCSI I see the VM-Store.fhdx file in the
iSCSI VIRTUAL DISKS pane. Below, in the iSCSI TARGETS pane i see the listing for the target.
Both show "Connected" in the Target Status column. From outside the server (on the LAN) I launched the iSCSI Initiator applet in the control panel/administrator tools. I clicked on the "Discovery" tab in the iSCSI Initiator Properties
dialog box and typed in the IP address of the Windows 2012 server. On the Targets tab it's all blank. If I manually enter the IP address in the Quick Connect box at the top and click the Quick Connect button I get a dialog that shows "No targets available
for using Quick Connect" in the status box at the bottom.
CHAP is NOT being used yet so it's not a CHAP issue. What else can I try to make this work? It's holding up a project we desperately need to get online.

Hi,
Do you mean that you get the error "No Targets available for Login using Quick Connect"? I did a test on my pc, and have the same error with you. A workaround for the issue is to enter the server name in the Quick Connect box to connect the iSCSI target.
There is a similar thread, please go through it to help troubleshoot this issue:
How to troubleshoot "No Targets available for Login using Quick Connect."
http://social.technet.microsoft.com/Forums/windowsserver/en-US/9d32b6dd-2957-4305-9818-708d80df5ca1/how-to-troubleshoot-no-targets-available-for-login-using-quick-connect?forum=winserverfiles
Regards,
Mandy
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

Get state of an iSCSI target using iscsicsli command

Hello !!
I want to display the state of an iSCSI target (connected, inactive, ...) using iscsicli command.
iscsicli ListTargets displays only the name of the different targets without the state. How can i do this please ?
Thanks !!

Hi,
iscsicli /? help show all available parameters. Currently I cannot help test but 2 possible parameters are:
iscsicli targetinfo
iscsicli listpersistenttargets
If neither could help then you may try powershell commands instead as Tim mentioned. However it is only supported in Windows Powershell 4.0.
If you have any feedback on our support, please send to [email protected]

Migrate iscsi Targets

Hello,
we have a 2 node sles10.3+oes2sp3 cluster.
both are iscsi-initiators against one target.
Now we need to migrate the data to another iscsi-target.
Is it possible to add the new target2 as a device to the existing pool, migrate the data from target1 to target2 and remove target1?
If yes what is the command for this?
thx,
hugo

In article <[email protected]>, Susehoush wrote:
> Now we need to migrate the data to another iscsi-target.
>
Will you be removing the first target? If so you will also need to
mirror the SBD before you go very far. I last did that step under
NetWare, but the process looks much the same now. Raw docs:
http://www.novell.com/documentation/...age=/documenta
tion//oes2/clus_admin_lx/data/bl9gj0q.html
then for the pools/volumes them selves, you can either do NSS drive
mirroring of them and/or use the Novell Migration Utility as
appropriate for your situation (i.e. are there pool/volume size changes
you need to do).
The new target will not be added as part of an existing pool, but as
its own for either step.
Andy Konecny
KonecnyConsulting.ca in Toronto
Andy's Profile: http://forums.novell.com/member.php?userid=75037

OEL 4.5 iSCSI Target notes wanted

I'm about to build an iSCSI target based around an OEL 4.5/Dual Opteron/8GB/2.5TB Sata machine. Distro is flexible, but I would prefer to stick with OEL 4.5 or OEL 5.0.
I'd appreciate pointers and links to good documentation, howtos, notes, etc. that you have encountered. This is a learning opportunity for me.

Hans,
we can start with installation HowTo :-)
1. Install kernel-devel package
2. Download "iSCSI Enterprise Target" from http://sourceforge.net/project/showfiles.php?group_id=108475
3. tar xvzf iscsitarget-0.4.15.tar.gz
4. cd iscsitarget-0.4.15
5. make
6. # make install
7. Modify /etc/ietd.conf and set mandatory parameters:
- Target (iSCSI qualified name aka IQN - in format iqn.yyyy-mm.reversed domainname:identifier)
- LUN (storage)
Assume that your domain is acme.com and my shared device /dev/sda, no authentication. So config will be as following:
Target iqn.2008-01.com.acme:storage.disk1
Lun 0 Path=/dev/sda8. # chkconfig iscsi-target on
9. # /etc/init.d/iscsi-target start
10. "man ietadm" "man ietd" "man 5 ietd.conf" and cup of coffee :-)
A Quick Guide to iSCSI on Linux - http://www.cuddletech.com/articles/iscsi/index.html
Setting Up an iSCSI Enviroment - http://www.howtoforge.com/iscsi_on_linux
Message was edited by:
Ivan Kartik
Of course you may consider to use this: http://www.openfiler.com

Multiple Hyper-V 2012 R2 servers to access a since ISCSI target

A couple years ago the community helped me configure a CentOS file server to connect to my VMWare and HyperV Servers for the purpose of backup. At the time I created 2 LVM devices, one to connect to Esxi via NFS, and one to connect to HV via ISCSI. This has worked GREAT!I have converted almost all my production environment to HV. I had to of course rebuild the arrays and make the larger one ISCSI rather than NFS. I just noticed that file the file structure of the connected HV drives is not the same. I have (3) HV Servers connected to the same ISCSI target which resides on the CentOS file server. When you view the connected drives, the same target has different files on it from different HV Hosts. Prior to rebuilding the arrays, the ISCSI target worked as intended. I suspect that I missed a step during the rebuild. The drives were...
This topic first appeared in the Spiceworks Community

Hello,
I have installed VMM 2012 R2, this is also not allowing me to add and manage Server 2012 R2 hosts. However it is perfectly able to manage Server 2008 host.
It gives following error when tried to add Server 2012 R2 hosts:
Error (2916)
VMM is unable to complete the request. The connection to the agent windows2012.test.com was lost.
WinRM: URL: [http://windows2012.test.com:5985], Verb: [INVOKE], Method: [Associate], Resource: [http://schemas.microsoft.com/wbem/wsman/1/wmi/root/scvmm/AgentManagement]
Unknown error (0x80338012)
Recommended Action
Ensure that the WS-Management service and the agent are installed and running and that a firewall is not blocking HTTPS traffic.
This problem can also be caused by WMI service crash. Ensure that KB 982293 (http://support.microsoft.com/kb/982293) is installed on the machine if it is running Windows Server 2008 R2.
If the error persists, reboot windows2012.test.com and then try the operation again.
Any suggestions please?

Remote Replication of iSCSI target

I have an iSCSI target on a NSS 326 that my backup server drops our backups onto. I would like to replicate that iSCSI drive to another NSS 326. Is there a way I can accomplish this?

Adam,
No the NAS allocates this space for the connecting operating system to format and use how it chooses. So the connecting operating system has full control over this space and NAS only knows of the allocated space. You have to treat this space as if its a logical drive in that computer and not the NAS.It's best to set up a directory just for your server you can use CIF or NFS to this directory for backup and then use Rsync to replicate to another NSS device.
hope this helps,
Jason
Cisco Support Engineer
.:|:.:|:.

[SOLVED] Gnome 3.8: Unable to use Nokia N9 as a Bluetooth modem

Hi,
I'm unable to use my Nokia Any ideas on how to fix this?
Here are some log files:
Bluetooth startup from everything.log:
/> bluetoothd[382]: Bluetooth daemon 4.101
bluetoothd[382]: Starting SDP server
bluetoothd[382]: DIS cannot start: GATT is disabled
bluetoothd[382]: Failed to init deviceinfo plugin
bluetoothd[382]: Failed to init gatt_example plugin
bluetoothd[382]: Bluetooth Management interface initialized
bluetoothd[382]: bluetoothd[382]: Bluetooth Management interface initialized
bluetoothd[382]: bluetoothd[382]: Unknown command complete for opcode 1J
bluetoothd[382]: Unknown command complete for opcode 19
bluetoothd[382]: bluetoothd[382]: Adapter /org/bluez/382/hci0 has been enabled
bluetoothd[382]: Adapter /org/bluez/382/hci0 has been enabled
entries from everything.log:
/etc/gdm/Xsession[612]: Ikkunointiohjelman varoitus:Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x2800003 (Uuden Blue)
/etc/gdm/Xsession[612]: Ikkunointiohjelman varoitus:meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
bluetoothd[382]: bluetoothd[382]: Discovery session 0x7f5d47491d10 with :1.58 activated
bluetoothd[382]: Discovery session 0x7f5d47491d10 with :1.58 activated
bluetoothd[382]: bluetoothd[382]: Stopping discovery
bluetoothd[382]: Stopping discovery
kernel: [ 1179.820342] usb 2-1: reset high-speed USB device number 2 using ehci-pci
dbus-daemon[396]: dbus[396]: [system] Rejected send message, 3 matched rules; type="method_return", sender=":1.58" (uid=1000 pid=1082 comm="bluetooth-wizard ") interface="(unset)" member="(unset)" error name="(unset)" requested_reply="0" destination=":1.4" (uid=0 pid=382 comm="/usr/lib/bluetooth/bluetoothd -n ")
bluetoothd[382]: bluetoothd[382]: input-headset driver probe failed for device 40:98:4E:65:A1:00
bluetoothd[382]: input-headset driver probe failed for device 40:98:4E:65:A1:00
pulseaudio[678]: [pulseaudio] bluetooth-util.c: org.bluez.AudioSource.GetProperties() failed: org.freedesktop.DBus.Error.UnknownMethod: Method "GetProperties" with signature "" on interface "org.bluez.AudioSource" doesn't exist
pulseaudio[678]: [pulseaudio] bluetooth-util.c: org.bluez.HandsfreeGateway.GetProperties() failed: org.freedesktop.DBus.Error.UnknownMethod: Method "GetProperties" with signature "" on interface "org.bluez.HandsfreeGateway" doesn't exist
pulseaudio[678]: [pulseaudio] bluetooth-util.c: org.bluez.HandsfreeGateway.GetProperties() failed: org.freedesktop.DBus.Error.UnknownMethod: Method "GetProperties" with signature "" on interface "org.bluez.HandsfreeGateway" doesn't exist
/etc/gdm/Xsession[612]: ** Message: has_config_widget 40:98:4E:65:A1:00 SyncMLClient
/etc/gdm/Xsession[612]: ** Message: has_config_widget 40:98:4E:65:A1:00 DialupNetworking
/etc/gdm/Xsession[612]: ** Message: has_config_widget 40:98:4E:65:A1:00 OBEXObjectPush
/etc/gdm/Xsession[612]: ** Message: has_config_widget 40:98:4E:65:A1:00 OBEXFileTransfer
/etc/gdm/Xsession[612]: ** Message: has_config_widget 40:98:4E:65:A1:00 AudioSource
/etc/gdm/Xsession[612]: ** Message: has_config_widget 40:98:4E:65:A1:00 A/V_RemoteControlTarget
/etc/gdm/Xsession[612]: ** Message: has_config_widget 40:98:4E:65:A1:00 A/V_RemoteControl
/etc/gdm/Xsession[612]: ** Message: has_config_widget 40:98:4E:65:A1:00 Headset_-_AG
/etc/gdm/Xsession[612]: ** Message: has_config_widget 40:98:4E:65:A1:00 HandsfreeAudioGateway
/etc/gdm/Xsession[612]: ** Message: has_config_widget 40:98:4E:65:A1:00 Phonebook_Access_-_PSE
/etc/gdm/Xsession[612]: ** Message: has_config_widget 40:98:4E:65:A1:00 SyncMLClient
/etc/gdm/Xsession[612]: ** Message: has_config_widget 40:98:4E:65:A1:00 DialupNetworking
/etc/gdm/Xsession[612]: ** Message: has_config_widget 40:98:4E:65:A1:00 OBEXObjectPush
/etc/gdm/Xsession[612]: ** Message: has_config_widget 40:98:4E:65:A1:00 OBEXFileTransfer
/etc/gdm/Xsession[612]: ** Message: has_config_widget 40:98:4E:65:A1:00 AudioSource
/etc/gdm/Xsession[612]: ** Message: has_config_widget 40:98:4E:65:A1:00 A/V_RemoteControlTarget
/etc/gdm/Xsession[612]: ** Message: has_config_widget 40:98:4E:65:A1:00 A/V_RemoteControl
/etc/gdm/Xsession[612]: ** Message: has_config_widget 40:98:4E:65:A1:00 Headset_-_AG
/etc/gdm/Xsession[612]: ** Message: has_config_widget 40:98:4E:65:A1:00 HandsfreeAudioGateway
/etc/gdm/Xsession[612]: ** Message: has_config_widget 40:98:4E:65:A1:00 Phonebook_Access_-_PSE
/etc/gdm/Xsession[612]: ** Message: Default Bluetooth adapter is powered
/etc/gdm/Xsession[612]: ** Message: dun_start: starting DUN device discovery...
/etc/gdm/Xsession[612]: ** Message: Tutkitaan puhelimen asetuksia…
/etc/gdm/Xsession[612]: ** Message: dun_start: calling Connect...
/etc/gdm/Xsession[612]: ** Message: dun_start: waiting for Connect success...
/etc/gdm/Xsession[612]: ** Message: dun_connect_cb: processing Connect reply
/etc/gdm/Xsession[612]: ** Message: dun_connect_cb: new rfcomm interface '/dev/rfcomm0'
/etc/gdm/Xsession[612]: ** Message: dun_connect_cb: finished
upowerd[506]: (upowerd:506): UPower-Linux-WARNING **: unhandled action 'move' on /sys/devices/pci0000:00/0000:00:13.1/usb6/6-3/6-3:1.0/bluetooth/hci0/hci0:21/rfcomm0
kernel: [ 1212.925984] Bluetooth: TIOCGSERIAL is not supported
kernel: [ 1214.790844] Bluetooth: TIOCGSERIAL is not supported
kernel: [ 1214.791357] Bluetooth: TIOCGSERIAL is not supported
ModemManager[457]: <info> Creating modem with plugin 'Nokia' and '1' ports
kernel: [ 1215.816882] Bluetooth: TIOCGSERIAL is not supported
ModemManager[457]: <info> Modem for device at '/sys/devices/pci0000:00/0000:00:13.1/usb6/6-3' successfully created
kernel: [ 1215.820679] Bluetooth: TIOCGSERIAL is not supported
ModemManager[457]: <info> Modem: state changed (unknown -> disabled)
kernel: [ 1216.873341] Bluetooth: TIOCGSERIAL is not supported
/etc/gdm/Xsession[612]: ** Message: modem_object_added: (/org/freedesktop/ModemManager1/Modem/0) modem found
/etc/gdm/Xsession[612]: ** Message: start_wizard: (/org/freedesktop/ModemManager1/Modem/0) starting the mobile wizard
NetworkManager[387]: <info> ignoring modem 'rfcomm0' (no associated Bluetooth device)
/etc/gdm/Xsession[612]: ** Message: wizard_done_cb: mobile wizard done
/etc/gdm/Xsession[612]: ** Message: wizard_done_cb: adding new setting
/etc/gdm/Xsession[612]: ** Message: wizard_done_cb: waiting for add connection result...
NetworkManager[387]: <info> BT device Nokia N9 (40:98:4E:65:A1:00) added (DUN)
NetworkManager[387]: <info> (40:98:4E:65:A1:00): new Bluetooth device (driver: 'bluez' ifindex: 0)
NetworkManager[387]: <info> (40:98:4E:65:A1:00): exported as /org/freedesktop/NetworkManager/Devices/1
NetworkManager[387]: <info> (40:98:4E:65:A1:00): device state change: unmanaged -> unavailable (reason 'managed') [10 20 2]
NetworkManager[387]: <info> (40:98:4E:65:A1:00): deactivating device (reason 'managed') [2]
NetworkManager[387]: <info> (40:98:4E:65:A1:00): device state change: unavailable -> disconnected (reason 'none') [20 30 0]
/etc/gdm/Xsession[612]: ** Message: Puhelimesi on nyt valmis käyttöön.
upowerd[506]: (upowerd:506): UPower-Linux-WARNING **: unhandled action 'move' on /sys/devices/virtual/tty/rfcomm0
dbus-daemon[396]: dbus[396]: [system] Rejected send message, 2 matched rules; type="method_return", sender=":1.4" (uid=0 pid=382 comm="/usr/lib/bluetooth/bluetoothd -n ") interface="(unset)" member="(unset)" error name="(unset)" requested_reply="0" destination=":1.59" (uid=1000 pid=1082 comm="bluetooth-wizard ")
NetworkManager[387]: <info> (eth0): device state change: activated -> disconnected (reason 'user-requested') [100 30 39]
NetworkManager[387]: <info> (eth0): deactivating device (reason 'user-requested') [39]
avahi-daemon[392]: Withdrawing address record for 192.168.0.222 on eth0.
avahi-daemon[392]: Leaving mDNS multicast group on interface eth0.IPv4 with address 192.168.0.222.
avahi-daemon[392]: Interface eth0.IPv4 no longer relevant for mDNS.
dbus-daemon[396]: dbus[396]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service'
dbus[396]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service'
systemd[1]: Starting Network Manager Script Dispatcher Service...
dbus-daemon[396]: dbus[396]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
dbus[396]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
systemd[1]: Started Network Manager Script Dispatcher Service.
NetworkManager[387]: <info> Activation (40:98:4E:65:A1:00) starting connection 'Dna connection'
NetworkManager[387]: <info> (40:98:4E:65:A1:00): device state change: disconnected -> prepare (reason 'none') [30 40 0]
NetworkManager[387]: <info> Activation (40:98:4E:65:A1:00) Stage 1 of 5 (Device Prepare) scheduled...
NetworkManager[387]: <info> Activation (40:98:4E:65:A1:00) Stage 1 of 5 (Device Prepare) started...
NetworkManager[387]: <info> Activation (40:98:4E:65:A1:00) Stage 2 of 5 (Device Configure) scheduled...
NetworkManager[387]: <info> Activation (40:98:4E:65:A1:00) Stage 1 of 5 (Device Prepare) complete.
NetworkManager[387]: <info> Activation (40:98:4E:65:A1:00) Stage 2 of 5 (Device Configure) starting...
NetworkManager[387]: <info> (40:98:4E:65:A1:00): device state change: prepare -> config (reason 'none') [40 50 0]
NetworkManager[387]: <info> Activation (40:98:4E:65:A1:00) Stage 2 of 5 (Device Configure) complete.
NetworkManager[387]: <info> Activation (40:98:4E:65:A1:00 40:98:4E:65:A1:00/bluetooth) Stage 2 of 5 (Device Configure) successful. Will connect via DUN.
NetworkManager[387]: <info> Activation (40:98:4E:65:A1:00/bluetooth) Stage 2 of 5 (Device Configure) waiting for modem to appear.
upowerd[506]: (upowerd:506): UPower-Linux-WARNING **: unhandled action 'move' on /sys/devices/pci0000:00/0000:00:13.1/usb6/6-3/6-3:1.0/bluetooth/hci0/hci0:21/rfcomm0
NetworkManager[387]: <info> (40:98:4E:65:A1:00): device state change: config -> failed (reason 'modem-not-found') [50 120 43]
NetworkManager[387]: <warn> Activation (40:98:4E:65:A1:00) failed for connection 'Dna connection'
NetworkManager[387]: <info> (40:98:4E:65:A1:00): device state change: failed -> disconnected (reason 'none') [120 30 0]
NetworkManager[387]: <info> (40:98:4E:65:A1:00): deactivating device (reason 'none') [0]
upowerd[506]: (upowerd:506): UPower-Linux-WARNING **: unhandled action 'move' on /sys/devices/virtual/tty/rfcomm0
dbus-daemon[396]: dbus[396]: [system] Rejected send message, 7 matched rules; type="method_return", sender=":1.4" (uid=0 pid=382 comm="/usr/lib/bluetooth/bluetoothd -n ") interface="(unset)" member="(unset)" error name="(unset)" requested_reply="0" destination=":1.8" (uid=0 pid=387 comm="/usr/bin/NetworkManager --no-daemon ")
/> systemd[1]: Mounting Arbitrary Executable File Formats File System...
systemd-sysctl[132]: Duplicate assignment of kernel/sysrq in file '/usr/lib/sysctl.d/50-default.conf', ignoring.
systemd[1]: Started Apply Kernel Variables.
systemd[1]: Started udev Coldplug all Devices.
systemd-modules-load[138]: Inserted module 'fuse'
systemd[1]: Started Create static device nodes in /dev.
systemd[1]: Starting udev Kernel Device Manager...
systemd[1]: Started udev Kernel Device Manager.
systemd[1]: Mounted Arbitrary Executable File Formats File System.
systemd[1]: Mounted Debug File System.
0.000000] Initializing cgroup subsys cpuset
0.000000] Initializing cgroup subsys cpu
0.000000] Linux version 3.9.5-1-ARCH (tobias@T-POWA-LX) (gcc version 4.8.1 (GCC) ) #1 SMP PREEMPT Sat Jun 8 09:22:45 CEST 2013
0.000000] Command line: BOOT_IMAGE=/vmlinuz-linux root=UUID=90b0c2df-9b19-4c19-91ce-5479b086da4d ro quiet
0.000000] e820: BIOS-provided physical RAM map:
0.000000] BIOS-e820: [mem 0x0000000000000000-0x000000000009f7ff] usable
0.000000] BIOS-e820: [mem 0x000000000009f800-0x000000000009ffff] reserved
0.000000] BIOS-e820: [mem 0x00000000000f0000-0x00000000000fffff] reserved
0.000000] BIOS-e820: [mem 0x0000000000100000-0x00000000cfdeffff] usable
0.000000] BIOS-e820: [mem 0x00000000cfdf0000-0x00000000cfdf2fff] ACPI NVS
syslog-ng[390]: syslog-ng starting up; version='3.4.1'
systemd[1]: Mounted Huge Pages File System.
0.000000] BIOS-e820: [mem 0x00000000cfdf3000-0x00000000cfdfffff] ACPI data
0.000000] BIOS-e820: [mem 0x00000000cfe00000-0x00000000cfefffff] reserved
0.000000] BIOS-e820: [mem 0x00000000e0000000-0x00000000efffffff] reserved
0.000000] BIOS-e820: [mem 0x00000000fec00000-0x00000000ffffffff] reserved
0.000000] BIOS-e820: [mem 0x0000000100000000-0x000000032fffffff] usable
0.000000] NX (Execute Disable) protection: active
0.000000] SMBIOS 2.4 present.
0.000000] DMI: Gigabyte Technology Co., Ltd. GA-MA790XT-UD4P/GA-MA790XT-UD4P, BIOS F8g 07/12/2010
0.000000] e820: update [mem 0x00000000-0x00000fff] usable ==> reserved
0.000000] e820: remove [mem 0x000a0000-0x000fffff] usable
0.000000] No AGP bridge found
0.000000] e820: last_pfn = 0x330000 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-C7FFF write-protect
0.000000] C8000-FFFFF uncachable
0.000000] MTRR variable ranges enabled:
0.000000] 0 base 000000000000 mask FFFF80000000 write-back
0.000000] 1 base 000080000000 mask FFFFC0000000 write-back
0.000000] 2 base 0000C0000000 mask FFFFF0000000 write-back
0.000000] 3 base 0000CFE00000 mask FFFFFFE00000 uncachable
0.000000] 4 base 000100000000 mask FFFF00000000 write-back
0.000000] 5 base 000200000000 mask FFFF00000000 write-back
0.000000] 6 base 000300000000 mask FFFFE0000000 write-back
0.000000] 7 base 000320000000 mask FFFFF0000000 write-back
0.000000] TOM2: 0000000330000000 aka 13056M
0.000000] x86 PAT enabled: cpu 0, old 0x7040600070406, new 0x7010600070106
0.000000] e820: update [mem 0xcfe00000-0xffffffff] usable ==> reserved
0.000000] e820: last_pfn = 0xcfdf0 max_arch_pfn = 0x400000000
0.000000] found SMP MP-table at [mem 0x000f5440-0x000f544f] mapped at [ffff8800000f5440]
0.000000] Scanning 1 areas for low memory corruption
0.000000] Base memory trampoline at [ffff880000099000] 99000 size 24576
0.000000] Using GB pages for direct mapping
0.000000] init_memory_mapping: [mem 0x00000000-0x000fffff]
0.000000] [mem 0x00000000-0x000fffff] page 4k
0.000000] BRK [0x01b30000, 0x01b30fff] PGTABLE
0.000000] BRK [0x01b31000, 0x01b31fff] PGTABLE
0.000000] BRK [0x01b32000, 0x01b32fff] PGTABLE
0.000000] init_memory_mapping: [mem 0x32fe00000-0x32fffffff]
0.000000] [mem 0x32fe00000-0x32fffffff] page 2M
0.000000] BRK [0x01b33000, 0x01b33fff] PGTABLE
0.000000] init_memory_mapping: [mem 0x32c000000-0x32fdfffff]
0.000000] [mem 0x32c000000-0x32fdfffff] page 2M
0.000000] init_memory_mapping: [mem 0x300000000-0x32bffffff]
0.000000] [mem 0x300000000-0x32bffffff] page 2M
0.000000] init_memory_mapping: [mem 0x00100000-0xcfdeffff]
0.000000] [mem 0x00100000-0x001fffff] page 4k
0.000000] [mem 0x00200000-0x3fffffff] page 2M
0.000000] [mem 0x40000000-0xbfffffff] page 1G
0.000000] [mem 0xc0000000-0xcfbfffff] page 2M
0.000000] [mem 0xcfc00000-0xcfdeffff] page 4k
0.000000] init_memory_mapping: [mem 0x100000000-0x2ffffffff]
0.000000] [mem 0x100000000-0x2ffffffff] page 1G
0.000000] RAMDISK: [mem 0x378a4000-0x37c49fff]
0.000000] ACPI: RSDP 00000000000f6e70 00014 (v00 GBT )
0.000000] ACPI: RSDT 00000000cfdf3000 00038 (v01 GBT GBTUACPI 42302E31 GBTU 01010101)
0.000000] ACPI: FACP 00000000cfdf3040 00074 (v01 GBT GBTUACPI 42302E31 GBTU 01010101)
0.000000] ACPI: DSDT 00000000cfdf30c0 0725F (v01 GBT GBTUACPI 00001000 MSFT 03000000)
0.000000] ACPI: FACS 00000000cfdf0000 00040
0.000000] ACPI: SSDT 00000000cfdfa400 008F5 (v01 PTLTD POWERNOW 00000001 LTP 00000001)
0.000000] ACPI: HPET 00000000cfdfad00 00038 (v01 GBT GBTUACPI 42302E31 GBTU 00000098)
0.000000] ACPI: MCFG 00000000cfdfad40 0003C (v01 GBT GBTUACPI 42302E31 GBTU 01010101)
0.000000] ACPI: APIC 00000000cfdfa340 000BC (v01 GBT GBTUACPI 42302E31 GBTU 01010101)
0.000000] ACPI: Local APIC address 0xfee00000
0.000000] Scanning NUMA topology in Northbridge 24
0.000000] No NUMA configuration found
0.000000] Faking a node at [mem 0x0000000000000000-0x000000032fffffff]
0.000000] Initmem setup node 0 [mem 0x00000000-0x32fffffff]
0.000000] NODE_DATA [mem 0x32fff9000-0x32fffdfff]
0.000000] [ffffea0000000000-ffffea000cbfffff] PMD -> [ffff880323600000-ffff88032f5fffff] on node 0
0.000000] Zone ranges:
0.000000] DMA [mem 0x00001000-0x00ffffff]
0.000000] DMA32 [mem 0x01000000-0xffffffff]
0.000000] Normal [mem 0x100000000-0x32fffffff]
0.000000] Movable zone start for each node
0.000000] Early memory node ranges
0.000000] node 0: [mem 0x00001000-0x0009efff]
0.000000] node 0: [mem 0x00100000-0xcfdeffff]
0.000000] node 0: [mem 0x100000000-0x32fffffff]
0.000000] On node 0 totalpages: 3145102
0.000000] DMA zone: 64 pages used for memmap
0.000000] DMA zone: 21 pages reserved
0.000000] DMA zone: 3998 pages, LIFO batch:0
0.000000] DMA32 zone: 13240 pages used for memmap
0.000000] DMA32 zone: 847344 pages, LIFO batch:31
0.000000] Normal zone: 35840 pages used for memmap
0.000000] Normal zone: 2293760 pages, LIFO batch:31
0.000000] ACPI: PM-Timer IO Port: 0x4008
0.000000] ACPI: Local APIC address 0xfee00000
0.000000] ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled)
0.000000] ACPI: LAPIC (acpi_id[0x01] lapic_id[0x01] enabled)
0.000000] ACPI: LAPIC (acpi_id[0x02] lapic_id[0x02] enabled)
0.000000] ACPI: LAPIC (acpi_id[0x03] lapic_id[0x03] disabled)
0.000000] ACPI: LAPIC (acpi_id[0x04] lapic_id[0x04] disabled)
0.000000] ACPI: LAPIC (acpi_id[0x05] lapic_id[0x05] disabled)
0.000000] ACPI: LAPIC (acpi_id[0x06] lapic_id[0x06] disabled)
0.000000] ACPI: LAPIC (acpi_id[0x07] lapic_id[0x07] disabled)
0.000000] ACPI: LAPIC_NMI (acpi_id[0x00] dfl dfl lint[0x1])
0.000000] ACPI: LAPIC_NMI (acpi_id[0x01] dfl dfl lint[0x1])
0.000000] ACPI: LAPIC_NMI (acpi_id[0x02] dfl dfl lint[0x1])
0.000000] ACPI: LAPIC_NMI (acpi_id[0x03] dfl dfl lint[0x1])
0.000000] ACPI: LAPIC_NMI (acpi_id[0x04] dfl dfl lint[0x1])
0.000000] ACPI: LAPIC_NMI (acpi_id[0x05] dfl dfl lint[0x1])
0.000000] ACPI: LAPIC_NMI (acpi_id[0x06] dfl dfl lint[0x1])
0.000000] ACPI: LAPIC_NMI (acpi_id[0x07] dfl dfl lint[0x1])
0.000000] ACPI: IOAPIC (id[0x02] address[0xfec00000] gsi_base[0])
0.000000] IOAPIC[0]: apic_id 2, version 33, 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 low level)
0.000000] ACPI: IRQ0 used by override.
0.000000] ACPI: IRQ2 used by override.
0.000000] ACPI: IRQ9 used by override.
0.000000] Using ACPI (MADT) for SMP configuration information
0.000000] ACPI: HPET id: 0x10b9a201 base: 0xfed00000
0.000000] smpboot: Allowing 8 CPUs, 5 hotplug CPUs
0.000000] nr_irqs_gsi: 40
0.000000] PM: Registered nosave memory: 000000000009f000 - 00000000000a0000
0.000000] PM: Registered nosave memory: 00000000000a0000 - 00000000000f0000
0.000000] PM: Registered nosave memory: 00000000000f0000 - 0000000000100000
0.000000] PM: Registered nosave memory: 00000000cfdf0000 - 00000000cfdf3000
0.000000] PM: Registered nosave memory: 00000000cfdf3000 - 00000000cfe00000
0.000000] PM: Registered nosave memory: 00000000cfe00000 - 00000000cff00000
0.000000] PM: Registered nosave memory: 00000000cff00000 - 00000000e0000000
0.000000] PM: Registered nosave memory: 00000000e0000000 - 00000000f0000000
0.000000] PM: Registered nosave memory: 00000000f0000000 - 00000000fec00000
0.000000] PM: Registered nosave memory: 00000000fec00000 - 0000000100000000
0.000000] e820: [mem 0xcff00000-0xdfffffff] available for PCI devices
0.000000] Booting paravirtualized kernel on bare hardware
0.000000] setup_percpu: NR_CPUS:64 nr_cpumask_bits:64 nr_cpu_ids:8 nr_node_ids:1
0.000000] PERCPU: Embedded 28 pages/cpu @ffff88032fc00000 s85824 r8192 d20672 u262144
0.000000] pcpu-alloc: s85824 r8192 d20672 u262144 alloc=1*2097152
0.000000] pcpu-alloc: [0] 0 1 2 3 4 5 6 7
0.000000] Built 1 zonelists in Zone order, mobility grouping on. Total pages: 3095937
0.000000] Policy zone: Normal
0.000000] Kernel command line: BOOT_IMAGE=/vmlinuz-linux root=UUID=90b0c2df-9b19-4c19-91ce-5479b086da4d ro quiet
0.000000] PID hash table entries: 4096 (order: 3, 32768 bytes)
0.000000] __ex_table already sorted, skipping sort
0.000000] Checking aperture...
0.000000] No AGP bridge found
0.000000] Node 0: aperture @ c4000000 size 32 MB
0.000000] Aperture pointing to e820 RAM. Ignoring.
0.000000] Your BIOS doesn't leave a aperture memory hole
0.000000] Please enable the IOMMU option in the BIOS setup
0.000000] This costs you 64 MB of RAM
0.000000] Mapping aperture over 65536 KB of RAM @ c4000000
0.000000] PM: Registered nosave memory: 00000000c4000000 - 00000000c8000000
0.000000] Memory: 12235744k/13369344k available (4984k kernel code, 788936k absent, 344664k reserved, 3966k data, 1092k init)
0.000000] SLUB: Genslabs=15, HWalign=64, Order=0-3, MinObjects=0, CPUs=8, Nodes=1
0.000000] Preemptible hierarchical RCU implementation.
0.000000] RCU dyntick-idle grace-period acceleration is enabled.
0.000000] Dump stacks of tasks blocking RCU-preempt GP.
0.000000] RCU restricting CPUs from NR_CPUS=64 to nr_cpu_ids=8.
0.000000] NR_IRQS:4352 nr_irqs:744 16
0.000000] spurious 8259A interrupt: IRQ7.
0.000000] Console: colour dummy device 80x25
0.000000] console [tty0] enabled
0.000000] allocated 50331648 bytes of page_cgroup
0.000000] please try 'cgroup_disable=memory' option if you don't want memory cgroups
0.000000] hpet clockevent registered
0.003333] tsc: Fast TSC calibration using PIT
0.006666] tsc: Detected 2812.672 MHz processor
0.000003] Calibrating delay loop (skipped), value calculated using timer frequency.. 5627.73 BogoMIPS (lpj=9375573)
0.000006] pid_max: default: 32768 minimum: 301
0.000035] Security Framework initialized
0.000041] AppArmor: AppArmor disabled by boot time parameter
0.000892] Dentry cache hash table entries: 2097152 (order: 12, 16777216 bytes)
0.005505] Inode-cache hash table entries: 1048576 (order: 11, 8388608 bytes)
0.007582] Mount-cache hash table entries: 256
0.007774] Initializing cgroup subsys cpuacct
0.007776] Initializing cgroup subsys memory
0.007786] Initializing cgroup subsys devices
0.007787] Initializing cgroup subsys freezer
0.007789] Initializing cgroup subsys net_cls
0.007790] Initializing cgroup subsys blkio
0.007813] tseg: 00cff00000
0.007816] CPU: Physical Processor ID: 0
0.007817] CPU: Processor Core ID: 0
0.007818] mce: CPU supports 6 MCE banks
0.007823] LVT offset 0 assigned for vector 0xf9
0.007828] Last level iTLB entries: 4KB 512, 2MB 16, 4MB 8
0.007828] Last level dTLB entries: 4KB 512, 2MB 128, 4MB 64
0.007828] tlb_flushall_shift: 4
0.007908] Freeing SMP alternatives: 20k freed
0.008523] ACPI: Core revision 20130117
0.010353] ACPI: All ACPI Tables successfully acquired
0.042664] ftrace: allocating 19546 entries in 77 pages
0.399338] ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1
0.432338] smpboot: CPU0: AMD Phenom(tm) II X3 720 Processor (fam: 10, model: 04, stepping: 02)
0.535738] Performance Events: AMD PMU driver.
0.535742] ... version: 0
0.535743] ... bit width: 48
0.535744] ... generic registers: 4
0.535745] ... value mask: 0000ffffffffffff
0.535746] ... max period: 00007fffffffffff
0.535746] ... fixed-purpose events: 0
0.535747] ... event mask: 000000000000000f
0.565797] NMI watchdog: enabled on all CPUs, permanently consumes one hw-PMU counter.
0.572465] smpboot: Booting Node 0, Processors #1 #2
0.602275] Brought up 3 CPUs
0.602279] smpboot: Total of 3 processors activated (16882.19 BogoMIPS)
0.605948] devtmpfs: initialized
0.608503] PM: Registering ACPI NVS region [mem 0xcfdf0000-0xcfdf2fff] (12288 bytes)
0.609303] RTC time: 21:44:15, date: 06/16/13
0.609349] NET: Registered protocol family 16
0.609448] node 0 link 0: io port [b000, ffff]
0.609451] TOM: 00000000d0000000 aka 3328M
0.609453] Fam 10h mmconf [mem 0xe0000000-0xe00fffff]
0.609455] node 0 link 0: mmio [a0000, bffff]
0.609457] node 0 link 0: mmio [d0000000, dfffffff]
0.609459] node 0 link 0: mmio [f0000000, fe02ffff]
0.609460] node 0 link 0: mmio [e0000000, e04fffff] ==> [e0100000, e04fffff]
0.609462] TOM2: 0000000330000000 aka 13056M
0.609464] bus: [bus 00-04] on node 0 link 0
0.609466] bus: 00 [io 0x0000-0xffff]
0.609467] bus: 00 [mem 0x000a0000-0x000bffff]
0.609468] bus: 00 [mem 0xd0000000-0xdfffffff]
0.609469] bus: 00 [mem 0xe0500000-0xffffffff]
0.609470] bus: 00 [mem 0xe0100000-0xe04fffff]
0.609471] bus: 00 [mem 0x330000000-0xfcffffffff]
0.609498] ACPI: bus type PCI registered
0.609552] PCI: MMCONFIG for domain 0000 [bus 00-ff] at [mem 0xe0000000-0xefffffff] (base 0xe0000000)
0.609554] PCI: MMCONFIG at [mem 0xe0000000-0xefffffff] reserved in E820
0.617921] PCI: Using configuration type 1 for base access
0.618123] mtrr: your CPUs had inconsistent variable MTRR settings
0.618124] mtrr: probably your BIOS does not setup all CPUs.
0.618125] mtrr: corrected configuration.
0.618516] bio: create slab <bio-0> at 0
0.618576] ACPI: Added _OSI(Module Device)
0.618577] ACPI: Added _OSI(Processor Device)
0.618578] ACPI: Added _OSI(3.0 _SCP Extensions)
0.618580] ACPI: Added _OSI(Processor Aggregator Device)
0.619096] ACPI: EC: Look up EC in DSDT
0.623380] ACPI: Interpreter enabled
0.623389] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S1_] (20130117/hwxface-568)
0.623394] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S2_] (20130117/hwxface-568)
0.623403] ACPI: (supports S0 S3 S4 S5)
0.623405] ACPI: Using IOAPIC for interrupt routing
0.623473] PCI: Using host bridge windows from ACPI; if necessary, use "pci=nocrs" and report a bug
0.637118] ACPI: PCI Root Bridge [PCI0] (domain 0000 [bus 00-ff])
0.637201] PCI host bridge to bus 0000:00
0.637204] pci_bus 0000:00: root bus resource [bus 00-ff]
0.637207] pci_bus 0000:00: root bus resource [io 0x0000-0x0cf7]
0.637209] pci_bus 0000:00: root bus resource [io 0x0d00-0xffff]
0.637210] pci_bus 0000:00: root bus resource [mem 0x000a0000-0x000bffff]
0.637212] pci_bus 0000:00: root bus resource [mem 0x000c0000-0x000dffff]
0.637214] pci_bus 0000:00: root bus resource [mem 0xd0000000-0xfebfffff]
0.637223] pci 0000:00:00.0: [1002:5958] type 00 class 0x060000
0.637234] pci 0000:00:00.0: reg 1c: [mem 0xe0000000-0xffffffff 64bit]
0.637312] pci 0000:00:02.0: [1002:5978] type 01 class 0x060400
0.637342] pci 0000:00:02.0: PME# supported from D0 D3hot D3cold
0.637366] pci 0000:00:02.0: System wakeup disabled by ACPI
0.637399] pci 0000:00:04.0: [1002:597a] type 01 class 0x060400
0.637428] pci 0000:00:04.0: PME# supported from D0 D3hot D3cold
0.637453] pci 0000:00:04.0: System wakeup disabled by ACPI
0.637485] pci 0000:00:0a.0: [1002:597f] type 01 class 0x060400
0.637514] pci 0000:00:0a.0: PME# supported from D0 D3hot D3cold
0.637542] pci 0000:00:0a.0: System wakeup disabled by ACPI
0.637581] pci 0000:00:11.0: [1002:4390] type 00 class 0x01018f
0.637600] pci 0000:00:11.0: reg 10: [io 0xff00-0xff07]
0.637609] pci 0000:00:11.0: reg 14: [io 0xfe00-0xfe03]
0.637618] pci 0000:00:11.0: reg 18: [io 0xfd00-0xfd07]
0.637627] pci 0000:00:11.0: reg 1c: [io 0xfc00-0xfc03]
0.637636] pci 0000:00:11.0: reg 20: [io 0xfb00-0xfb0f]
0.637645] pci 0000:00:11.0: reg 24: [mem 0xfe02f000-0xfe02f3ff]
0.637664] pci 0000:00:11.0: set SATA to AHCI mode
0.637736] pci 0000:00:12.0: [1002:4397] type 00 class 0x0c0310
0.637749] pci 0000:00:12.0: reg 10: [mem 0xfe02e000-0xfe02efff]
0.637811] pci 0000:00:12.0: System wakeup disabled by ACPI
0.637840] pci 0000:00:12.1: [1002:4398] type 00 class 0x0c0310
0.637853] pci 0000:00:12.1: reg 10: [mem 0xfe02d000-0xfe02dfff]
0.637916] pci 0000:00:12.1: System wakeup disabled by ACPI
0.637948] pci 0000:00:12.2: [1002:4396] type 00 class 0x0c0320
0.637966] pci 0000:00:12.2: reg 10: [mem 0xfe02c000-0xfe02c0ff]
0.638046] pci 0000:00:12.2: supports D1 D2
0.638047] pci 0000:00:12.2: PME# supported from D0 D1 D2 D3hot
0.638065] pci 0000:00:12.2: System wakeup disabled by ACPI
0.638099] pci 0000:00:13.0: [1002:4397] type 00 class 0x0c0310
0.638112] pci 0000:00:13.0: reg 10: [mem 0xfe02b000-0xfe02bfff]
0.638178] pci 0000:00:13.0: System wakeup disabled by ACPI
0.638205] pci 0000:00:13.1: [1002:4398] type 00 class 0x0c0310
0.638217] pci 0000:00:13.1: reg 10: [mem 0xfe02a000-0xfe02afff]
0.638282] pci 0000:00:13.1: System wakeup disabled by ACPI
0.638316] pci 0000:00:13.2: [1002:4396] type 00 class 0x0c0320
0.638334] pci 0000:00:13.2: reg 10: [mem 0xfe029000-0xfe0290ff]
0.638414] pci 0000:00:13.2: supports D1 D2
0.638415] pci 0000:00:13.2: PME# supported from D0 D1 D2 D3hot
0.638436] pci 0000:00:13.2: System wakeup disabled by ACPI
0.638472] pci 0000:00:14.0: [1002:4385] type 00 class 0x0c0500
0.638587] pci 0000:00:14.1: [1002:439c] type 00 class 0x01018a
0.638602] pci 0000:00:14.1: reg 10: [io 0x0000-0x0007]
0.638611] pci 0000:00:14.1: reg 14: [io 0x0000-0x0003]
0.638620] pci 0000:00:14.1: reg 18: [io 0x0000-0x0007]
0.638629] pci 0000:00:14.1: reg 1c: [io 0x0000-0x0003]
0.638638] pci 0000:00:14.1: reg 20: [io 0xfa00-0xfa0f]
0.638722] pci 0000:00:14.2: [1002:4383] type 00 class 0x040300
0.638743] pci 0000:00:14.2: reg 10: [mem 0xfe024000-0xfe027fff 64bit]
0.638806] pci 0000:00:14.2: PME# supported from D0 D3hot D3cold
0.638830] pci 0000:00:14.2: System wakeup disabled by ACPI
0.638857] pci 0000:00:14.3: [1002:439d] type 00 class 0x060100
0.638963] pci 0000:00:14.4: [1002:4384] type 01 class 0x060401
0.639012] pci 0000:00:14.4: System wakeup disabled by ACPI
0.639040] pci 0000:00:14.5: [1002:4399] type 00 class 0x0c0310
0.639053] pci 0000:00:14.5: reg 10: [mem 0xfe028000-0xfe028fff]
0.639119] pci 0000:00:14.5: System wakeup disabled by ACPI
0.639151] pci 0000:00:18.0: [1022:1200] type 00 class 0x060000
0.639203] pci 0000:00:18.1: [1022:1201] type 00 class 0x060000
0.639254] pci 0000:00:18.2: [1022:1202] type 00 class 0x060000
0.639305] pci 0000:00:18.3: [1022:1203] type 00 class 0x060000
0.639358] pci 0000:00:18.4: [1022:1204] type 00 class 0x060000
0.639454] pci 0000:01:00.0: [1002:94b3] type 00 class 0x030000
0.639466] pci 0000:01:00.0: reg 10: [mem 0xd0000000-0xdfffffff 64bit pref]
0.639475] pci 0000:01:00.0: reg 18: [mem 0xfdee0000-0xfdeeffff 64bit]
0.639482] pci 0000:01:00.0: reg 20: [io 0xee00-0xeeff]
0.639493] pci 0000:01:00.0: reg 30: [mem 0x00000000-0x0001ffff pref]
0.639520] pci 0000:01:00.0: supports D1 D2
0.639554] pci 0000:01:00.1: [1002:aa38] type 00 class 0x040300
0.639566] pci 0000:01:00.1: reg 10: [mem 0xfdefc000-0xfdefffff 64bit]
0.639616] pci 0000:01:00.1: supports D1 D2
0.648955] pci 0000:00:02.0: PCI bridge to [bus 01]
0.648960] pci 0000:00:02.0: bridge window [io 0xe000-0xefff]
0.648963] pci 0000:00:02.0: bridge window [mem 0xfde00000-0xfdefffff]
0.648966] pci 0000:00:02.0: bridge window [mem 0xd0000000-0xdfffffff 64bit pref]
0.649016] pci 0000:02:00.0: [197b:2363] type 00 class 0x010185
0.649081] pci 0000:02:00.0: reg 24: [mem 0xfddfe000-0xfddfffff]
0.649130] pci 0000:02:00.0: PME# supported from D3hot
0.649179] pci 0000:02:00.1: [197b:2363] type 00 class 0x010185
0.649197] pci 0000:02:00.1: reg 10: [io 0xdf00-0xdf07]
0.649207] pci 0000:02:00.1: reg 14: [io 0xde00-0xde03]
0.649217] pci 0000:02:00.1: reg 18: [io 0xdd00-0xdd07]
0.649227] pci 0000:02:00.1: reg 1c: [io 0xdc00-0xdc03]
0.649237] pci 0000:02:00.1: reg 20: [io 0xdb00-0xdb0f]
0.649319] pci 0000:02:00.0: disabling ASPM on pre-1.1 PCIe device. You can enable it with 'pcie_aspm=force'
0.649326] pci 0000:00:04.0: PCI bridge to [bus 02]
0.649329] pci 0000:00:04.0: bridge window [io 0xd000-0xdfff]
0.649331] pci 0000:00:04.0: bridge window [mem 0xfdd00000-0xfddfffff]
0.649334] pci 0000:00:04.0: bridge window [mem 0xfdc00000-0xfdcfffff 64bit pref]
0.649377] pci 0000:03:00.0: [10ec:8168] type 00 class 0x020000
0.649389] pci 0000:03:00.0: reg 10: [io 0xce00-0xceff]
0.649408] pci 0000:03:00.0: reg 18: [mem 0xfdfff000-0xfdffffff 64bit pref]
0.649421] pci 0000:03:00.0: reg 20: [mem 0xfdfe0000-0xfdfeffff 64bit pref]
0.649430] pci 0000:03:00.0: reg 30: [mem 0x00000000-0x0000ffff pref]
0.649474] pci 0000:03:00.0: supports D1 D2
0.649475] pci 0000:03:00.0: PME# supported from D0 D1 D2 D3hot D3cold
0.658954] pci 0000:00:0a.0: PCI bridge to [bus 03]
0.658959] pci 0000:00:0a.0: bridge window [io 0xc000-0xcfff]
0.658961] pci 0000:00:0a.0: bridge window [mem 0xfd900000-0xfd9fffff]
0.658964] pci 0000:00:0a.0: bridge window [mem 0xfdf00000-0xfdffffff 64bit pref]
0.659008] pci 0000:04:06.0: [1131:7146] type 00 class 0x048000
0.659025] pci 0000:04:06.0: reg 10: [mem 0xfdbff000-0xfdbff1ff]
0.659127] pci 0000:04:07.0: [9710:9805] type 00 class 0x078000
0.659143] pci 0000:04:07.0: reg 10: [io 0xbf00-0xbf07]
0.659155] pci 0000:04:07.0: reg 14: [io 0xbe00-0xbe07]
0.659167] pci 0000:04:07.0: reg 18: [io 0xbd00-0xbd07]
0.659179] pci 0000:04:07.0: reg 1c: [io 0xbc00-0xbc07]
0.659190] pci 0000:04:07.0: reg 20: [io 0xbb00-0xbb07]
0.659202] pci 0000:04:07.0: reg 24: [io 0xba00-0xba0f]
0.659264] pci 0000:04:0e.0: [104c:8024] type 00 class 0x0c0010
0.659286] pci 0000:04:0e.0: reg 10: [mem 0xfdbfe000-0xfdbfe7ff]
0.659298] pci 0000:04:0e.0: reg 14: [mem 0xfdbf8000-0xfdbfbfff]
0.659387] pci 0000:04:0e.0: supports D1 D2
0.659389] pci 0000:04:0e.0: PME# supported from D0 D1 D2 D3hot
0.659445] pci 0000:00:14.4: PCI bridge to [bus 04] (subtractive decode)
0.659449] pci 0000:00:14.4: bridge window [io 0xb000-0xbfff]
0.659453] pci 0000:00:14.4: bridge window [mem 0xfdb00000-0xfdbfffff]
0.659457] pci 0000:00:14.4: bridge window [mem 0xfda00000-0xfdafffff pref]
0.659458] pci 0000:00:14.4: bridge window [io 0x0000-0x0cf7] (subtractive decode)
0.659460] pci 0000:00:14.4: bridge window [io 0x0d00-0xffff] (subtractive decode)
0.659462] pci 0000:00:14.4: bridge window [mem 0x000a0000-0x000bffff] (subtractive decode)
0.659463] pci 0000:00:14.4: bridge window [mem 0x000c0000-0x000dffff] (subtractive decode)
0.659465] pci 0000:00:14.4: bridge window [mem 0xd0000000-0xfebfffff] (subtractive decode)
0.659479] acpi PNP0A03:00: ACPI _OSC support notification failed, disabling PCIe ASPM
0.659481] acpi PNP0A03:00: Unable to request _OSC control (_OSC support mask: 0x08)
0.659908] ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 6 7 10 11) *0, disabled.
0.659945] ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 6 7 10 11) *0, disabled.
0.659979] ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 5 6 7 10 11) *0, disabled.
0.660012] ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 5 6 7 10 11) *0, disabled.
0.660045] ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 5 6 7 10 11) *0, disabled.
0.660078] ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 5 6 7 10 11) *0, disabled.
0.660111] ACPI: PCI Interrupt Link [LNK0] (IRQs 3 4 5 6 7 10 11) *0, disabled.
0.660144] ACPI: PCI Interrupt Link [LNK1] (IRQs 3 4 5 6 7 10 11) *0, disabled.
0.660468] acpi root: \_SB_.PCI0 notify handler is installed
0.660494] Found 1 acpi root devices
0.660564] ACPI: No dock devices found.
0.660640] vgaarb: device added: PCI:0000:01:00.0,decodes=io+mem,owns=io+mem,locks=none
0.660643] vgaarb: loaded
0.660644] vgaarb: bridge control possible 0000:01:00.0
0.660676] PCI: Using ACPI for IRQ routing
0.668997] PCI: pci_cache_line_size set to 64 bytes
0.669004] pci 0000:00:00.0: no compatible bridge window for [mem 0xe0000000-0xffffffff 64bit]
0.669070] e820: reserve RAM buffer [mem 0x0009f800-0x0009ffff]
0.669071] e820: reserve RAM buffer [mem 0xcfdf0000-0xcfffffff]
0.669150] NetLabel: Initializing
0.669151] NetLabel: domain hash size = 128
0.669152] NetLabel: protocols = UNLABELED CIPSOv4
0.669161] NetLabel: unlabeled traffic allowed by default
0.669177] hpet0: at MMIO 0xfed00000, IRQs 2, 8, 0, 0
0.669180] hpet0: 4 comparators, 32-bit 14.318180 MHz counter
0.671205] Switching to clocksource hpet
0.674983] pnp: PnP ACPI init
0.674994] ACPI: bus type PNP registered
0.675058] system 00:00: [io 0x04d0-0x04d1] has been reserved
0.675060] system 00:00: [io 0x0220-0x0225] has been reserved
0.675062] system 00:00: [io 0x0290-0x0294] has been reserved
0.675065] system 00:00: Plug and Play ACPI device, IDs PNP0c02 (active)
0.675512] pnp 00:01: disabling [mem 0x00000000-0x00000fff window] because it overlaps 0000:00:00.0 BAR 3 [mem 0x00000000-0x1fffffff 64bit]
0.675535] pnp 00:01: disabling [mem 0x00000000-0x00000fff window disabled] because it overlaps 0000:01:00.0 BAR 6 [mem 0x00000000-0x0001ffff pref]
0.675543] pnp 00:01: disabling [mem 0x00000000-0x00000fff window disabled] because it overlaps 0000:03:00.0 BAR 6 [mem 0x00000000-0x0000ffff pref]
0.675575] system 00:01: [io 0x4100-0x411f] has been reserved
0.675578] system 00:01: [io 0x0228-0x022f] has been reserved
0.675580] system 00:01: [io 0x040b] has been reserved
0.675581] system 00:01: [io 0x04d6] has been reserved
0.675583] system 00:01: [io 0x0c00-0x0c01] has been reserved
0.675585] system 00:01: [io 0x0c14] has been reserved
0.675586] system 00:01: [io 0x0c50-0x0c52] has been reserved
0.675588] system 00:01: [io 0x0c6c-0x0c6d] has been reserved
0.675589] system 00:01: [io 0x0c6f] has been reserved
0.675591] system 00:01: [io 0x0cd0-0x0cd1] has been reserved
0.675593] system 00:01: [io 0x0cd2-0x0cd3] has been reserved
0.675594] system 00:01: [io 0x0cd4-0x0cdf] has been reserved
0.675596] system 00:01: [io 0x4000-0x40fe] has been reserved
0.675597] system 00:01: [io 0x4210-0x4217] has been reserved
0.675599] system 00:01: [io 0x0b00-0x0b0f] has been reserved
0.675601] system 00:01: [io 0x0b10-0x0b1f] has been reserved
0.675602] system 00:01: [io 0x0b20-0x0b3f] has been reserved
0.675604] system 00:01: [mem 0xfee00400-0xfee00fff window] has been reserved
0.675608] system 00:01: Plug and Play ACPI device, IDs PNP0c02 (active)
0.675676] pnp 00:02: [dma 4]
0.675693] pnp 00:02: Plug and Play ACPI device, IDs PNP0200 (active)
0.675740] pnp 00:03: Plug and Play ACPI device, IDs PNP0103 (active)
0.675772] pnp 00:04: Plug and Play ACPI device, IDs PNP0b00 (active)
0.675791] pnp 00:05: Plug and Play ACPI device, IDs PNP0800 (active)
0.675815] pnp 00:06: Plug and Play ACPI device, IDs PNP0c04 (active)
0.676004] system 00:07: [mem 0xe0000000-0xefffffff] has been reserved
0.676006] system 00:07: Plug and Play ACPI device, IDs PNP0c02 (active)
0.676106] pnp 00:08: disabling [mem 0x000cfe00-0x000cffff] because it overlaps 0000:00:00.0 BAR 3 [mem 0x00000000-0x1fffffff 64bit]
0.676108] pnp 00:08: disabling [mem 0x000f0000-0x000f7fff] because it overlaps 0000:00:00.0 BAR 3 [mem 0x00000000-0x1fffffff 64bit]
0.676110] pnp 00:08: disabling [mem 0x000f8000-0x000fbfff] because it overlaps 0000:00:00.0 BAR 3 [mem 0x00000000-0x1fffffff 64bit]
0.676112] pnp 00:08: disabling [mem 0x000fc000-0x000fffff] because it overlaps 0000:00:00.0 BAR 3 [mem 0x00000000-0x1fffffff 64bit]
0.676114] pnp 00:08: disabling [mem 0x00000000-0x0009ffff] because it overlaps 0000:00:00.0 BAR 3 [mem 0x00000000-0x1fffffff 64bit]
0.676117] pnp 00:08: disabling [mem 0x00100000-0xcfdeffff] because it overlaps 0000:00:00.0 BAR 3 [mem 0x00000000-0x1fffffff 64bit]
0.676153] system 00:08: [mem 0xcfdf0000-0xcfdfffff] could not be reserved
0.676155] system 00:08: [mem 0xffff0000-0xffffffff] has been reserved
0.676157] system 00:08: [mem 0xcfe00000-0xcfefffff] has been reserved
0.676159] system 00:08: [mem 0xcff00000-0xcfffffff] could not be reserved
0.676161] system 00:08: [mem 0xfec00000-0xfec00fff] could not be reserved
0.676162] system 00:08: [mem 0xfee00000-0xfee00fff] could not be reserved
0.676164] system 00:08: [mem 0xfff80000-0xfffeffff] has been reserved
0.676166] system 00:08: Plug and Play ACPI device, IDs PNP0c01 (active)
0.676180] pnp: PnP ACPI: found 9 devices
0.676182] ACPI: bus type PNP unregistered
0.682550] pci 0000:01:00.0: BAR 6: assigned [mem 0xfde00000-0xfde1ffff pref]
0.682553] pci 0000:00:02.0: PCI bridge to [bus 01]
0.682556] pci 0000:00:02.0: bridge window [io 0xe000-0xefff]
0.682558] pci 0000:00:02.0: bridge window [mem 0xfde00000-0xfdefffff]
0.682561] pci 0000:00:02.0: bridge window [mem 0xd0000000-0xdfffffff 64bit pref]
0.682564] pci 0000:00:04.0: PCI bridge to [bus 02]
0.682566] pci 0000:00:04.0: bridge window [io 0xd000-0xdfff]
0.682568] pci 0000:00:04.0: bridge window [mem 0xfdd00000-0xfddfffff]
0.682570] pci 0000:00:04.0: bridge window [mem 0xfdc00000-0xfdcfffff 64bit pref]
0.682574] pci 0000:03:00.0: BAR 6: assigned [mem 0xfdf00000-0xfdf0ffff pref]
0.682575] pci 0000:00:0a.0: PCI bridge to [bus 03]
0.682577] pci 0000:00:0a.0: bridge window [io 0xc000-0xcfff]
0.682579] pci 0000:00:0a.0: bridge window [mem 0xfd900000-0xfd9fffff]
0.682582] pci 0000:00:0a.0: bridge window [mem 0xfdf00000-0xfdffffff 64bit pref]
0.682585] pci 0000:00:14.4: PCI bridge to [bus 04]
0.682587] pci 0000:00:14.4: bridge window [io 0xb000-0xbfff]
0.682592] pci 0000:00:14.4: bridge window [mem 0xfdb00000-0xfdbfffff]
0.682595] pci 0000:00:14.4: bridge window [mem 0xfda00000-0xfdafffff pref]
0.682771] pci_bus 0000:00: resource 4 [io 0x0000-0x0cf7]
0.682772] pci_bus 0000:00: resource 5 [io 0x0d00-0xffff]
0.682774] pci_bus 0000:00: resource 6 [mem 0x000a0000-0x000bffff]
0.682775] pci_bus 0000:00: resource 7 [mem 0x000c0000-0x000dffff]
0.682777] pci_bus 0000:00: resource 8 [mem 0xd0000000-0xfebfffff]
0.682779] pci_bus 0000:01: resource 0 [io 0xe000-0xefff]
0.682780] pci_bus 0000:01: resource 1 [mem 0xfde00000-0xfdefffff]
0.682782] pci_bus 0000:01: resource 2 [mem 0xd0000000-0xdfffffff 64bit pref]
0.682784] pci_bus 0000:02: resource 0 [io 0xd000-0xdfff]
0.682785] pci_bus 0000:02: resource 1 [mem 0xfdd00000-0xfddfffff]
0.682787] pci_bus 0000:02: resource 2 [mem 0xfdc00000-0xfdcfffff 64bit pref]
0.682788] pci_bus 0000:03: resource 0 [io 0xc000-0xcfff]
0.682790] pci_bus 0000:03: resource 1 [mem 0xfd900000-0xfd9fffff]
0.682791] pci_bus 0000:03: resource 2 [mem 0xfdf00000-0xfdffffff 64bit pref]
0.682793] pci_bus 0000:04: resource 0 [io 0xb000-0xbfff]
0.682795] pci_bus 0000:04: resource 1 [mem 0xfdb00000-0xfdbfffff]
0.682796] pci_bus 0000:04: resource 2 [mem 0xfda00000-0xfdafffff pref]
0.682798] pci_bus 0000:04: resource 4 [io 0x0000-0x0cf7]
0.682799] pci_bus 0000:04: resource 5 [io 0x0d00-0xffff]

I managed to get my wired connection back and updated my system. After that (and a reboot), NetworkManager started to mysteriously work.
Here are the relevant parts from journald's log:
kesä 17 17:47:40 sunnydale dbus-daemon[396]: dbus[396]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service'
kesä 17 17:47:40 sunnydale dbus[396]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service'
kesä 17 17:47:40 sunnydale systemd[1]: Starting Network Manager Script Dispatcher Service...
kesä 17 17:47:40 sunnydale dbus-daemon[396]: dbus[396]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
kesä 17 17:47:40 sunnydale dbus[396]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
kesä 17 17:47:40 sunnydale systemd[1]: Started Network Manager Script Dispatcher Service.
kesä 17 17:47:49 sunnydale NetworkManager[387]: <info> Activation (40:98:4E:65:A1:00) starting connection 'dna internet connection'
kesä 17 17:47:49 sunnydale NetworkManager[387]: <info> (40:98:4E:65:A1:00): device state change: disconnected -> prepare (reason 'none') [30 40 0]
kesä 17 17:47:49 sunnydale NetworkManager[387]: <debug> [1371480469.388835] [nm-manager.c:596] manager_device_state_changed(): stopping connectivity checks
kesä 17 17:47:49 sunnydale NetworkManager[387]: <info> Activation (40:98:4E:65:A1:00) Stage 1 of 5 (Device Prepare) scheduled...
kesä 17 17:47:49 sunnydale NetworkManager[387]: <info> Activation (40:98:4E:65:A1:00) Stage 1 of 5 (Device Prepare) started...
kesä 17 17:47:49 sunnydale NetworkManager[387]: <info> Activation (40:98:4E:65:A1:00) Stage 2 of 5 (Device Configure) scheduled...
kesä 17 17:47:49 sunnydale NetworkManager[387]: <info> Activation (40:98:4E:65:A1:00) Stage 1 of 5 (Device Prepare) complete.
kesä 17 17:47:49 sunnydale NetworkManager[387]: <info> Activation (40:98:4E:65:A1:00) Stage 2 of 5 (Device Configure) starting...
kesä 17 17:47:49 sunnydale NetworkManager[387]: <info> (40:98:4E:65:A1:00): device state change: prepare -> config (reason 'none') [40 50 0]
kesä 17 17:47:49 sunnydale NetworkManager[387]: <debug> [1371480469.390823] [nm-manager.c:596] manager_device_state_changed(): stopping connectivity checks
kesä 17 17:47:49 sunnydale NetworkManager[387]: <debug> [1371480469.398034] [nm-device-bt.c:947] act_stage2_config(): (40:98:4E:65:A1:00): requesting connection to the device
kesä 17 17:47:49 sunnydale NetworkManager[387]: <info> Activation (40:98:4E:65:A1:00) Stage 2 of 5 (Device Configure) complete.
kesä 17 17:47:52 sunnydale NetworkManager[387]: <debug> [1371480472.813677] [nm-device-bt.c:836] bluez_property_changed(): (40:98:4E:65:A1:00): bluez property 'Connected' changed to 'true'
kesä 17 17:47:52 sunnydale NetworkManager[387]: <debug> [1371480472.813775] [nm-device-bt.c:846] bluez_property_changed(): (40:98:4E:65:A1:00): connected to the device
kesä 17 17:47:53 sunnydale NetworkManager[387]: <debug> [1371480473.67585] [nm-device-bt.c:808] bluez_connect_cb(): (40:98:4E:65:A1:00): connect request successful
kesä 17 17:47:53 sunnydale NetworkManager[387]: <info> Activation (40:98:4E:65:A1:00 40:98:4E:65:A1:00/bluetooth) Stage 2 of 5 (Device Configure) successful. Will connect via DUN.
kesä 17 17:47:53 sunnydale NetworkManager[387]: <info> Activation (40:98:4E:65:A1:00/bluetooth) Stage 2 of 5 (Device Configure) waiting for modem to appear.
kesä 17 17:47:53 sunnydale upowerd[518]: (upowerd:518): UPower-Linux-WARNING **: unhandled action 'move' on /sys/devices/pci0000:00/0000:00:13.1/usb4/4-3/4-3:1.0/bluetooth/hci0/hci0:21/rfcomm0
kesä 17 17:47:53 sunnydale kernel: Bluetooth: TIOCGSERIAL is not supported
kesä 17 17:47:54 sunnydale kernel: Bluetooth: TIOCGSERIAL is not supported
kesä 17 17:47:54 sunnydale kernel: Bluetooth: TIOCGSERIAL is not supported
kesä 17 17:47:56 sunnydale ModemManager[390]: <info> Creating modem with plugin 'Nokia' and '1' ports
kesä 17 17:47:56 sunnydale ModemManager[390]: <info> Modem for device at '/sys/devices/pci0000:00/0000:00:13.1/usb4/4-3' successfully created
kesä 17 17:47:56 sunnydale kernel: Bluetooth: TIOCGSERIAL is not supported
kesä 17 17:47:56 sunnydale kernel: Bluetooth: TIOCGSERIAL is not supported
kesä 17 17:47:57 sunnydale ModemManager[390]: <info> Modem: state changed (unknown -> disabled)
kesä 17 17:47:57 sunnydale kernel: Bluetooth: TIOCGSERIAL is not supported
kesä 17 17:47:57 sunnydale NetworkManager[387]: <info> Activation (40:98:4E:65:A1:00/bluetooth) Stage 2 of 5 (Device Configure) modem found.
kesä 17 17:47:57 sunnydale ModemManager[390]: <info> Simple connect started...
kesä 17 17:47:57 sunnydale ModemManager[390]: <info> Simple connect state (3/8): Enable
kesä 17 17:47:57 sunnydale ModemManager[390]: <info> Modem /org/freedesktop/ModemManager1/Modem/0: state changed (disabled -> enabling)
kesä 17 17:47:57 sunnydale NetworkManager[387]: <info> (rfcomm0) modem state changed, 'disabled' --> 'enabling' (reason: user-requested)
kesä 17 17:47:57 sunnydale kernel: Bluetooth: TIOCGSERIAL is not supported
kesä 17 17:47:57 sunnydale ModemManager[390]: <info> Modem /org/freedesktop/ModemManager1/Modem/0: 3GPP Registration state changed (unknown -> registering)
kesä 17 17:47:57 sunnydale ModemManager[390]: <info> Modem /org/freedesktop/ModemManager1/Modem/0: state changed (enabling -> enabled)
kesä 17 17:47:57 sunnydale ModemManager[390]: <info> Simple connect state (4/8): Wait to get fully enabled
kesä 17 17:47:57 sunnydale ModemManager[390]: <info> Simple connect state (5/8): Register
kesä 17 17:47:57 sunnydale ModemManager[390]: <info> Simple connect state (6/8): Bearer
kesä 17 17:47:57 sunnydale NetworkManager[387]: <info> (rfcomm0) modem state changed, 'enabling' --> 'enabled' (reason: user-requested)
kesä 17 17:47:57 sunnydale ModemManager[390]: <info> Simple connect state (7/8): Connect
kesä 17 17:47:57 sunnydale ModemManager[390]: <info> Modem /org/freedesktop/ModemManager1/Modem/0: state changed (enabled -> connecting)
kesä 17 17:47:57 sunnydale NetworkManager[387]: <info> (rfcomm0) modem state changed, 'enabled' --> 'connecting' (reason: user-requested)
kesä 17 17:47:57 sunnydale ModemManager[390]: <warn> Couldn't load Operator Name: 'Unknown error'
kesä 17 17:47:57 sunnydale ModemManager[390]: <info> Modem /org/freedesktop/ModemManager1/Modem/0: 3GPP Registration state changed (registering -> home)
kesä 17 17:47:57 sunnydale ModemManager[390]: <info> Modem /org/freedesktop/ModemManager1/Modem/0: 3GPP location updated (MCC: '0', MNC: '0', Location area code: 'A1', Cell ID: '10C654')
kesä 17 17:47:57 sunnydale ModemManager[390]: <info> Modem /org/freedesktop/ModemManager1/Modem/0: state changed (connecting -> connected)
kesä 17 17:47:57 sunnydale ModemManager[390]: <info> Simple connect state (8/8): All done
kesä 17 17:47:57 sunnydale NetworkManager[387]: <info> (rfcomm0) modem state changed, 'connecting' --> 'connected' (reason: user-requested)
kesä 17 17:47:57 sunnydale NetworkManager[387]: <warn> (rfcomm0): failed to look up interface index
kesä 17 17:47:57 sunnydale NetworkManager[387]: <debug> [1371480477.987235] [nm-device.c:3066] nm_device_activate_schedule_stage3_ip_config_start(): Activation (40:98:4E:65:A1:00) setting firewall zone 'default'
kesä 17 17:47:57 sunnydale NetworkManager[387]: <debug> [1371480477.987260] [nm-firewall-manager.c:107] nm_firewall_manager_add_or_change_zone(): (rfcomm0) firewall zone add/change skipped (not running)
kesä 17 17:47:57 sunnydale NetworkManager[387]: <info> Activation (40:98:4E:65:A1:00) Stage 3 of 5 (IP Configure Start) scheduled.
kesä 17 17:47:57 sunnydale NetworkManager[387]: <info> Activation (40:98:4E:65:A1:00) Stage 3 of 5 (IP Configure Start) started...
kesä 17 17:47:57 sunnydale NetworkManager[387]: <info> (40:98:4E:65:A1:00): device state change: config -> ip-config (reason 'none') [50 70 0]
kesä 17 17:47:57 sunnydale NetworkManager[387]: <debug> [1371480477.987628] [nm-manager.c:596] manager_device_state_changed(): stopping connectivity checks
kesä 17 17:47:57 sunnydale NetworkManager[387]: <info> using modem-specified IP timeout: 20 seconds
kesä 17 17:47:57 sunnydale NetworkManager[387]: <info> starting PPP connection
kesä 17 17:47:57 sunnydale NetworkManager[387]: <debug> [1371480477.988323] [nm-ppp-manager.c:1068] nm_ppp_manager_start(): command line: /usr/sbin/pppd nodetach lock nodefaultroute ipv6 , debug rfcomm0 noipdefault noauth usepeerdns lcp-echo-failure 0 lcp-echo-interval 0 ipparam /org/freedesktop/NetworkManager/PPP/0 plugin /usr/lib/pppd/2.4.5/nm-pppd-plugin.so
kesä 17 17:47:58 sunnydale NetworkManager[387]: <info> pppd started with pid 914
kesä 17 17:47:58 sunnydale NetworkManager[387]: <info> Activation (40:98:4E:65:A1:00) Stage 4 of 5 (IPv6 Configure Timeout) scheduled...
kesä 17 17:47:58 sunnydale NetworkManager[387]: <info> Activation (40:98:4E:65:A1:00) Stage 3 of 5 (IP Configure Start) complete.
kesä 17 17:47:58 sunnydale NetworkManager[387]: <info> Activation (40:98:4E:65:A1:00) Stage 4 of 5 (IPv6 Configure Timeout) started...
kesä 17 17:47:58 sunnydale NetworkManager[387]: <info> Activation (40:98:4E:65:A1:00) Stage 4 of 5 (IPv6 Configure Timeout) complete.
kesä 17 17:47:58 sunnydale pppd[914]: Plugin /usr/lib/pppd/2.4.5/nm-pppd-plugin.so loaded.
kesä 17 17:47:58 sunnydale NetworkManager[387]: Plugin /usr/lib/pppd/2.4.5/nm-pppd-plugin.so loaded.
kesä 17 17:47:58 sunnydale kernel: PPP generic driver version 2.4.2
kesä 17 17:47:58 sunnydale pppd[914]: pppd 2.4.5 started by root, uid 0
kesä 17 17:47:58 sunnydale pppd[914]: using channel 1
kesä 17 17:47:58 sunnydale pppd[914]: Using interface ppp0
kesä 17 17:47:58 sunnydale pppd[914]: Connect: ppp0 <--> /dev/rfcomm0
kesä 17 17:47:58 sunnydale pppd[914]: sent [LCP ConfReq id=0x1 <asyncmap 0x0> <magic 0x2ae21925> <pcomp> <accomp>]
kesä 17 17:47:58 sunnydale NetworkManager[387]: <debug> [1371480478.113258] [nm-netlink-monitor.c:164] link_msg_handler(): netlink link message: iface idx 3 flags 0x1090
kesä 17 17:47:58 sunnydale NetworkManager[387]: using channel 1
kesä 17 17:47:58 sunnydale NetworkManager[387]: Using interface ppp0
kesä 17 17:47:58 sunnydale NetworkManager[387]: Connect: ppp0 <--> /dev/rfcomm0
kesä 17 17:47:58 sunnydale NetworkManager[387]: sent [LCP ConfReq id=0x1 <asyncmap 0x0> <magic 0x2ae21925> <pcomp> <accomp>]
kesä 17 17:47:58 sunnydale systemd-sysctl[922]: Duplicate assignment of kernel/sysrq in file '/usr/lib/sysctl.d/50-default.conf', ignoring.
kesä 17 17:47:58 sunnydale NetworkManager[387]: <debug> [1371480478.116359] [nm-udev-manager.c:568] handle_uevent(): UDEV event: action 'add' subsys 'net' device 'ppp0'
kesä 17 17:47:58 sunnydale NetworkManager[387]: <warn> /sys/devices/virtual/net/ppp0: couldn't determine device driver; ignoring...
kesä 17 17:47:58 sunnydale pppd[914]: rcvd [LCP ConfRej id=0x1 <magic 0x2ae21925> <pcomp> <accomp>]
kesä 17 17:47:58 sunnydale pppd[914]: sent [LCP ConfReq id=0x2 <asyncmap 0x0>]
kesä 17 17:47:58 sunnydale NetworkManager[387]: rcvd [LCP ConfRej id=0x1 <magic 0x2ae21925> <pcomp> <accomp>]
kesä 17 17:47:58 sunnydale NetworkManager[387]: sent [LCP ConfReq id=0x2 <asyncmap 0x0>]
kesä 17 17:47:58 sunnydale pppd[914]: rcvd [LCP ConfAck id=0x2 <asyncmap 0x0>]
kesä 17 17:47:58 sunnydale NetworkManager[387]: rcvd [LCP ConfAck id=0x2 <asyncmap 0x0>]
kesä 17 17:47:58 sunnydale pppd[914]: rcvd [LCP ConfReq id=0x0 <auth pap> <mru 1500> <asyncmap 0xa0000>]
kesä 17 17:47:58 sunnydale pppd[914]: sent [LCP ConfAck id=0x0 <auth pap> <mru 1500> <asyncmap 0xa0000>]
kesä 17 17:47:58 sunnydale NetworkManager[387]: rcvd [LCP ConfReq id=0x0 <auth pap> <mru 1500> <asyncmap 0xa0000>]
kesä 17 17:47:58 sunnydale NetworkManager[387]: sent [LCP ConfAck id=0x0 <auth pap> <mru 1500> <asyncmap 0xa0000>]
kesä 17 17:47:58 sunnydale pppd[914]: sent [PAP AuthReq id=0x1 user="" password=<hidden>]
kesä 17 17:47:58 sunnydale NetworkManager[387]: sent [PAP AuthReq id=0x1 user="" password=<hidden>]
kesä 17 17:48:01 sunnydale pppd[914]: sent [PAP AuthReq id=0x2 user="" password=<hidden>]
kesä 17 17:48:01 sunnydale NetworkManager[387]: sent [PAP AuthReq id=0x2 user="" password=<hidden>]
kesä 17 17:48:01 sunnydale pppd[914]: rcvd [PAP AuthAck id=0x2 ""]
kesä 17 17:48:01 sunnydale pppd[914]: PAP authentication succeeded
kesä 17 17:48:01 sunnydale NetworkManager[387]: rcvd [PAP AuthAck id=0x2 ""]
kesä 17 17:48:01 sunnydale NetworkManager[387]: PAP authentication succeeded
kesä 17 17:48:01 sunnydale kernel: PPP BSD Compression module registered
kesä 17 17:48:01 sunnydale pppd[914]: sent [CCP ConfReq id=0x1 <deflate 15> <deflate(old#) 15> <bsd v1 15>]
kesä 17 17:48:01 sunnydale pppd[914]: sent [IPCP ConfReq id=0x1 <compress VJ 0f 01> <addr 0.0.0.0> <ms-dns1 0.0.0.0> <ms-dns2 0.0.0.0>]
kesä 17 17:48:01 sunnydale pppd[914]: sent [IPV6CP ConfReq id=0x1 <addr fe80::e85e:dbed:209d:cf47>]
kesä 17 17:48:01 sunnydale pppd[914]: rcvd [IPCP ConfReq id=0x0 <addr 10.6.6.6>]
kesä 17 17:48:01 sunnydale pppd[914]: sent [IPCP ConfAck id=0x0 <addr 10.6.6.6>]
kesä 17 17:48:01 sunnydale NetworkManager[387]: sent [CCP ConfReq id=0x1 <deflate 15> <deflate(old#) 15> <bsd v1 15>]
kesä 17 17:48:01 sunnydale NetworkManager[387]: sent [IPCP ConfReq id=0x1 <compress VJ 0f 01> <addr 0.0.0.0> <ms-dns1 0.0.0.0> <ms-dns2 0.0.0.0>]
kesä 17 17:48:01 sunnydale NetworkManager[387]: sent [IPV6CP ConfReq id=0x1 <addr fe80::e85e:dbed:209d:cf47>]
kesä 17 17:48:01 sunnydale NetworkManager[387]: rcvd [IPCP ConfReq id=0x0 <addr 10.6.6.6>]
kesä 17 17:48:01 sunnydale NetworkManager[387]: sent [IPCP ConfAck id=0x0 <addr 10.6.6.6>]
kesä 17 17:48:01 sunnydale kernel: PPP Deflate Compression module registered
kesä 17 17:48:01 sunnydale pppd[914]: rcvd [LCP ProtRej id=0x0 80 fd 01 01 00 0f 1a 04 78 00 18 04 78 00 15 03 2f]
kesä 17 17:48:01 sunnydale pppd[914]: Protocol-Reject for 'Compression Control Protocol' (0x80fd) received
kesä 17 17:48:01 sunnydale NetworkManager[387]: rcvd [LCP ProtRej id=0x0 80 fd 01 01 00 0f 1a 04 78 00 18 04 78 00 15 03 2f]
kesä 17 17:48:01 sunnydale NetworkManager[387]: Protocol-Reject for 'Compression Control Protocol' (0x80fd) received
kesä 17 17:48:01 sunnydale pppd[914]: rcvd [IPV6CP ConfReq id=0x0 <addr fe80::0000:0000:0000:0000>]
kesä 17 17:48:01 sunnydale pppd[914]: sent [IPV6CP ConfNak id=0x0 <addr fe80::f042:f734:907e:22b9>]
kesä 17 17:48:01 sunnydale NetworkManager[387]: rcvd [IPV6CP ConfReq id=0x0 <addr fe80::0000:0000:0000:0000>]
kesä 17 17:48:01 sunnydale NetworkManager[387]: sent [IPV6CP ConfNak id=0x0 <addr fe80::f042:f734:907e:22b9>]
kesä 17 17:48:01 sunnydale pppd[914]: rcvd [IPV6CP ConfReq id=0x1 <addr fe80::f042:f734:907e:22b9>]
kesä 17 17:48:01 sunnydale pppd[914]: sent [IPV6CP ConfAck id=0x1 <addr fe80::f042:f734:907e:22b9>]
kesä 17 17:48:01 sunnydale NetworkManager[387]: rcvd [IPV6CP ConfReq id=0x1 <addr fe80::f042:f734:907e:22b9>]
kesä 17 17:48:01 sunnydale NetworkManager[387]: sent [IPV6CP ConfAck id=0x1 <addr fe80::f042:f734:907e:22b9>]
kesä 17 17:48:01 sunnydale pppd[914]: rcvd [IPV6CP ConfReq id=0x1 <addr fe80::f042:f734:907e:22b9>]
kesä 17 17:48:01 sunnydale pppd[914]: sent [IPV6CP ConfAck id=0x1 <addr fe80::f042:f734:907e:22b9>]
kesä 17 17:48:01 sunnydale NetworkManager[387]: rcvd [IPV6CP ConfReq id=0x1 <addr fe80::f042:f734:907e:22b9>]
kesä 17 17:48:01 sunnydale NetworkManager[387]: sent [IPV6CP ConfAck id=0x1 <addr fe80::f042:f734:907e:22b9>]
kesä 17 17:48:01 sunnydale pppd[914]: rcvd [IPV6CP ConfReq id=0x1 <addr fe80::f042:f734:907e:22b9>]
kesä 17 17:48:01 sunnydale pppd[914]: sent [IPV6CP ConfAck id=0x1 <addr fe80::f042:f734:907e:22b9>]
kesä 17 17:48:01 sunnydale NetworkManager[387]: rcvd [IPV6CP ConfReq id=0x1 <addr fe80::f042:f734:907e:22b9>]
kesä 17 17:48:01 sunnydale NetworkManager[387]: sent [IPV6CP ConfAck id=0x1 <addr fe80::f042:f734:907e:22b9>]
kesä 17 17:48:02 sunnydale pppd[914]: rcvd [IPV6CP ConfReq id=0x1 <addr fe80::f042:f734:907e:22b9>]
kesä 17 17:48:02 sunnydale pppd[914]: sent [IPV6CP ConfAck id=0x1 <addr fe80::f042:f734:907e:22b9>]
kesä 17 17:48:02 sunnydale NetworkManager[387]: rcvd [IPV6CP ConfReq id=0x1 <addr fe80::f042:f734:907e:22b9>]
kesä 17 17:48:02 sunnydale NetworkManager[387]: sent [IPV6CP ConfAck id=0x1 <addr fe80::f042:f734:907e:22b9>]
kesä 17 17:48:03 sunnydale pppd[914]: rcvd [IPCP ConfRej id=0x1 <compress VJ 0f 01>]
kesä 17 17:48:03 sunnydale pppd[914]: sent [IPCP ConfReq id=0x2 <addr 0.0.0.0> <ms-dns1 0.0.0.0> <ms-dns2 0.0.0.0>]
kesä 17 17:48:03 sunnydale NetworkManager[387]: rcvd [IPCP ConfRej id=0x1 <compress VJ 0f 01>]
kesä 17 17:48:03 sunnydale NetworkManager[387]: sent [IPCP ConfReq id=0x2 <addr 0.0.0.0> <ms-dns1 0.0.0.0> <ms-dns2 0.0.0.0>]
kesä 17 17:48:03 sunnydale pppd[914]: rcvd [IPCP ConfNak id=0x2 <addr 10.241.96.30> <ms-dns1 62.241.198.245> <ms-dns2 62.241.198.246>]
kesä 17 17:48:03 sunnydale pppd[914]: sent [IPCP ConfReq id=0x3 <addr 10.241.96.30> <ms-dns1 62.241.198.245> <ms-dns2 62.241.198.246>]
kesä 17 17:48:03 sunnydale NetworkManager[387]: rcvd [IPCP ConfNak id=0x2 <addr 10.241.96.30> <ms-dns1 62.241.198.245> <ms-dns2 62.241.198.246>]
kesä 17 17:48:03 sunnydale NetworkManager[387]: sent [IPCP ConfReq id=0x3 <addr 10.241.96.30> <ms-dns1 62.241.198.245> <ms-dns2 62.241.198.246>]
kesä 17 17:48:03 sunnydale pppd[914]: rcvd [IPCP ConfReq id=0x0 <addr 10.6.6.6>]
kesä 17 17:48:03 sunnydale pppd[914]: sent [IPCP ConfAck id=0x0 <addr 10.6.6.6>]
kesä 17 17:48:03 sunnydale NetworkManager[387]: rcvd [IPCP ConfReq id=0x0 <addr 10.6.6.6>]
kesä 17 17:48:03 sunnydale NetworkManager[387]: sent [IPCP ConfAck id=0x0 <addr 10.6.6.6>]
kesä 17 17:48:03 sunnydale pppd[914]: rcvd [IPCP ConfAck id=0x3 <addr 10.241.96.30> <ms-dns1 62.241.198.245> <ms-dns2 62.241.198.246>]
kesä 17 17:48:03 sunnydale pppd[914]: Cannot determine ethernet address for proxy ARP
kesä 17 17:48:03 sunnydale pppd[914]: local IP address 10.241.96.30
kesä 17 17:48:03 sunnydale pppd[914]: remote IP address 10.6.6.6
kesä 17 17:48:03 sunnydale pppd[914]: primary DNS address 62.241.198.245
kesä 17 17:48:03 sunnydale pppd[914]: secondary DNS address 62.241.198.246
kesä 17 17:48:03 sunnydale pppd[914]: Script /etc/ppp/ip-up started (pid 928)
kesä 17 17:48:03 sunnydale NetworkManager[387]: <debug> [1371480483.851617] [nm-netlink-monitor.c:164] link_msg_handler(): netlink link message: iface idx 3 flags 0x110D1
kesä 17 17:48:03 sunnydale NetworkManager[387]: <info> PPP manager(IP Config Get) reply received.
kesä 17 17:48:03 sunnydale NetworkManager[387]: <info> Activation (40:98:4E:65:A1:00) Stage 5 of 5 (IPv4 Configure Commit) scheduled...
kesä 17 17:48:03 sunnydale NetworkManager[387]: <info> Activation (40:98:4E:65:A1:00) Stage 5 of 5 (IPv4 Commit) started...
kesä 17 17:48:03 sunnydale NetworkManager[387]: <debug> [1371480483.852986] [nm-system.c:194] sync_addresses(): (ppp0): syncing addresses (family 2)
kesä 17 17:48:03 sunnydale NetworkManager[387]: <debug> [1371480483.853021] [nm-system.c:247] sync_addresses(): (ppp0): removing address '10.241.96.30/32'
kesä 17 17:48:03 sunnydale NetworkManager[387]: rcvd [IPCP ConfAck id=0x3 <addr 10.241.96.30> <ms-dns1 62.241.198.245> <ms-dns2 62.241.198.246>]
kesä 17 17:48:03 sunnydale NetworkManager[387]: Cannot determine ethernet address for proxy ARP
kesä 17 17:48:03 sunnydale NetworkManager[387]: local IP address 10.241.96.30
kesä 17 17:48:03 sunnydale NetworkManager[387]: remote IP address 10.6.6.6
kesä 17 17:48:03 sunnydale NetworkManager[387]: primary DNS address 62.241.198.245
kesä 17 17:48:03 sunnydale NetworkManager[387]: secondary DNS address 62.241.198.246
kesä 17 17:48:03 sunnydale NetworkManager[387]: Script /etc/ppp/ip-up started (pid 928)
kesä 17 17:48:03 sunnydale NetworkManager[387]: <debug> [1371480483.853775] [nm-system.c:280] sync_addresses(): (ppp0): adding address '10.241.96.30/0'
kesä 17 17:48:03 sunnydale pppd[914]: Script /etc/ppp/ip-up finished (pid 928), status = 0x2
kesä 17 17:48:03 sunnydale NetworkManager[387]: Script /etc/ppp/ip-up finished (pid 928), status = 0x2
kesä 17 17:48:04 sunnydale pppd[914]: sent [IPV6CP ConfReq id=0x1 <addr fe80::e85e:dbed:209d:cf47>]
kesä 17 17:48:04 sunnydale NetworkManager[387]: sent [IPV6CP ConfReq id=0x1 <addr fe80::e85e:dbed:209d:cf47>]
kesä 17 17:48:04 sunnydale NetworkManager[387]: <debug> [1371480484.855173] [nm-netlink-utils.c:356] dump_route(): route idx 3 family INET (2) addr 10.6.6.6/32
kesä 17 17:48:04 sunnydale NetworkManager[387]: <debug> [1371480484.855250] [nm-netlink-utils.c:356] dump_route(): route idx 3 family INET (2) addr 10.241.96.30/32
kesä 17 17:48:04 sunnydale NetworkManager[387]: <debug> [1371480484.855608] [nm-dns-manager.c:995] nm_dns_manager_begin_updates(): (device_ip4_config_changed): queueing DNS updates (1)
kesä 17 17:48:04 sunnydale NetworkManager[387]: <debug> [1371480484.855649] [nm-dns-manager.c:1013] nm_dns_manager_end_updates(): (nm_dns_manager_end_updates): DNS configuration did not change
kesä 17 17:48:04 sunnydale NetworkManager[387]: <debug> [1371480484.855666] [nm-dns-manager.c:1017] nm_dns_manager_end_updates(): (device_ip4_config_changed): no DNS changes to commit (0)
kesä 17 17:48:04 sunnydale NetworkManager[387]: <info> (40:98:4E:65:A1:00): device state change: ip-config -> secondaries (reason 'none') [70 90 0]
kesä 17 17:48:04 sunnydale NetworkManager[387]: <debug> [1371480484.855795] [nm-manager.c:596] manager_device_state_changed(): stopping connectivity checks
kesä 17 17:48:04 sunnydale NetworkManager[387]: <debug> [1371480484.858147] [nm-device.c:5244] nm_device_queue_state(): (40:98:4E:65:A1:00): queued state change to activated (id 252)
kesä 17 17:48:04 sunnydale NetworkManager[387]: <debug> [1371480484.858200] [nm-device.c:5174] nm_device_state_changed(): (40:98:4E:65:A1:00): device entered SECONDARIES state
kesä 17 17:48:04 sunnydale NetworkManager[387]: <info> Activation (40:98:4E:65:A1:00) Stage 5 of 5 (IPv4 Commit) complete.
kesä 17 17:48:04 sunnydale NetworkManager[387]: <debug> [1371480484.870449] [nm-device.c:5202] queued_set_state(): (40:98:4E:65:A1:00): running queued state change to activated (id 252)
kesä 17 17:48:04 sunnydale NetworkManager[387]: <info> (40:98:4E:65:A1:00): device state change: secondaries -> activated (reason 'none') [90 100 0]
kesä 17 17:48:04 sunnydale NetworkManager[387]: <debug> [1371480484.872130] [nm-manager.c:591] manager_device_state_changed(): (40:98:4E:65:A1:00): triggered connectivity check due to state change
kesä 17 17:48:04 sunnydale NetworkManager[387]: <debug> [1371480484.873625] [nm-dns-manager.c:995] nm_dns_manager_begin_updates(): (device_state_changed): queueing DNS updates (1)
kesä 17 17:48:04 sunnydale NetworkManager[387]: <debug> [1371480484.873683] [nm-dns-manager.c:995] nm_dns_manager_begin_updates(): (update_routing_and_dns): queueing DNS updates (2)
kesä 17 17:48:04 sunnydale NetworkManager[387]: <info> Policy set 'dna internet connection' (ppp0) as default for IPv4 routing and DNS.
kesä 17 17:48:04 sunnydale NetworkManager[387]: <debug> [1371480484.874320] [nm-dns-manager.c:1013] nm_dns_manager_end_updates(): (nm_dns_manager_end_updates): DNS configuration changed
kesä 17 17:48:04 sunnydale NetworkManager[387]: <debug> [1371480484.874341] [nm-dns-manager.c:1017] nm_dns_manager_end_updates(): (update_routing_and_dns): no DNS changes to commit (1)
kesä 17 17:48:04 sunnydale NetworkManager[387]: <debug> [1371480484.874368] [nm-dns-manager.c:1013] nm_dns_manager_end_updates(): (nm_dns_manager_end_updates): DNS configuration changed
kesä 17 17:48:04 sunnydale NetworkManager[387]: <debug> [1371480484.874383] [nm-dns-manager.c:1022] nm_dns_manager_end_updates(): (device_state_changed): committing DNS changes (0)
kesä 17 17:48:04 sunnydale NetworkManager[387]: <debug> [1371480484.874399] [nm-dns-manager.c:591] update_dns(): updating resolv.conf
kesä 17 17:48:04 sunnydale NetworkManager[387]: <info> Activation (40:98:4E:65:A1:00) successful, device activated.
kesä 17 17:48:04 sunnydale dbus-daemon[396]: dbus[396]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service'
kesä 17 17:48:04 sunnydale dbus[396]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service'
kesä 17 17:48:04 sunnydale systemd[1]: Starting Network Manager Script Dispatcher Service...
kesä 17 17:48:04 sunnydale dbus-daemon[396]: dbus[396]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
kesä 17 17:48:04 sunnydale dbus[396]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
kesä 17 17:48:04 sunnydale systemd[1]: Started Network Manager Script Dispatcher Service.
kesä 17 17:48:07 sunnydale pppd[914]: sent [IPV6CP ConfReq id=0x1 <addr fe80::e85e:dbed:209d:cf47>]
kesä 17 17:48:07 sunnydale NetworkManager[387]: sent [IPV6CP ConfReq id=0x1 <addr fe80::e85e:dbed:209d:cf47>]
kesä 17 17:48:10 sunnydale pppd[914]: sent [IPV6CP ConfReq id=0x1 <addr fe80::e85e:dbed:209d:cf47>]
kesä 17 17:48:10 sunnydale NetworkManager[387]: sent [IPV6CP ConfReq id=0x1 <addr fe80::e85e:dbed:209d:cf47>]
kesä 17 17:48:13 sunnydale pppd[914]: sent [IPV6CP ConfReq id=0x1 <addr fe80::e85e:dbed:209d:cf47>]
kesä 17 17:48:13 sunnydale NetworkManager[387]: sent [IPV6CP ConfReq id=0x1 <addr fe80::e85e:dbed:209d:cf47>]
kesä 17 17:48:16 sunnydale pppd[914]: sent [IPV6CP ConfReq id=0x1 <addr fe80::e85e:dbed:209d:cf47>]
kesä 17 17:48:16 sunnydale NetworkManager[387]: sent [IPV6CP ConfReq id=0x1 <addr fe80::e85e:dbed:209d:cf47>]
kesä 17 17:48:19 sunnydale pppd[914]: sent [IPV6CP ConfReq id=0x1 <addr fe80::e85e:dbed:209d:cf47>]
kesä 17 17:48:19 sunnydale NetworkManager[387]: sent [IPV6CP ConfReq id=0x1 <addr fe80::e85e:dbed:209d:cf47>]
kesä 17 17:48:21 sunnydale /etc/gdm/Xsession[622]: (process:953): GLib-CRITICAL **: g_slice_set_config: assertion `sys_page_size == 0' failed
kesä 17 17:48:22 sunnydale pppd[914]: sent [IPV6CP ConfReq id=0x1 <addr fe80::e85e:dbed:209d:cf47>]
kesä 17 17:48:22 sunnydale NetworkManager[387]: sent [IPV6CP ConfReq id=0x1 <addr fe80::e85e:dbed:209d:cf47>]
kesä 17 17:48:25 sunnydale /etc/gdm/Xsession[622]: Ikkunointiohjelman varoitus:CurrentTime used to choose focus window; focus window may not be correct.
kesä 17 17:48:25 sunnydale /etc/gdm/Xsession[622]: Ikkunointiohjelman varoitus:Got a request to focus 0x2200006 (jussi@sunn) with a timestamp of 0. This shouldn't happen!
kesä 17 17:48:25 sunnydale /etc/gdm/Xsession[622]: Ikkunointiohjelman varoitus:CurrentTime used to choose focus window; focus window may not be correct.
kesä 17 17:48:25 sunnydale /etc/gdm/Xsession[622]: Ikkunointiohjelman varoitus:Got a request to focus the no_focus_window with a timestamp of 0. This shouldn't happen!
kesä 17 17:48:25 sunnydale pppd[914]: sent [IPV6CP ConfReq id=0x1 <addr fe80::e85e:dbed:209d:cf47>]
kesä 17 17:48:25 sunnydale NetworkManager[387]: sent [IPV6CP ConfReq id=0x1 <addr fe80::e85e:dbed:209d:cf47>]
kesä 17 17:48:28 sunnydale pppd[914]: sent [IPV6CP ConfReq id=0x1 <addr fe80::e85e:dbed:209d:cf47>]
kesä 17 17:48:28 sunnydale NetworkManager[387]: sent [IPV6CP ConfReq id=0x1 <addr fe80::e85e:dbed:209d:cf47>]
kesä 17 17:48:31 sunnydale pppd[914]: IPV6CP: timeout sending Config-Requests
kesä 17 17:48:31 sunnydale NetworkManager[387]: IPV6CP: timeout sending Config-Requests
kesä 17 17:49:41 sunnydale dbus-daemon[396]: dbus[396]: [system] Activating via systemd: service name='org.freedesktop.hostname1' unit='dbus-org.freedesktop.hostname1.service'
kesä 17 17:49:41 sunnydale dbus[396]: [system] Activating via systemd: service name='org.freedesktop.hostname1' unit='dbus-org.freedesktop.hostname1.service'
kesä 17 17:49:41 sunnydale systemd[1]: Starting Hostname Service...
kesä 17 17:49:41 sunnydale dbus-daemon[396]: dbus[396]: [system] Successfully activated service 'org.freedesktop.hostname1'
kesä 17 17:49:41 sunnydale dbus[396]: [system] Successfully activated service 'org.freedesktop.hostname1'
kesä 17 17:49:41 sunnydale systemd[1]: Started Hostname Service.
kesä 17 17:49:43 sunnydale /etc/gdm/Xsession[622]: Ikkunointiohjelman varoitus:Log level 8: meta_window_raise: assertion `!window->override_redirect' failed
kesä 17 17:49:44 sunnydale /etc/gdm/Xsession[622]: Ikkunointiohjelman varoitus:Log level 8: meta_window_lower: assertion `!window->override_redirect' failed
And here is log about the updates I made:
[2013-06-17 17:01] [PACMAN] Running 'pacman -Syu'
[2013-06-17 17:01] [PACMAN] synchronizing package lists
[2013-06-17 17:01] [PACMAN] starting full system upgrade
[2013-06-17 17:04] [PACMAN] Running 'pacman -S --asdeps polkit'
[2013-06-17 17:04] [PACMAN] upgraded polkit (0.110-2 -> 0.111-1)
[2013-06-17 17:24] [PACMAN] Running 'pacman -U --asdeps lib32-polkit-0.111-1-x86_64.pkg.tar.xz'
[2013-06-17 17:24] [PACMAN] upgraded lib32-polkit (0.110-2 -> 0.111-1)
[2013-06-17 17:27] [PACMAN] Running 'pacman -S --asdeps libxkbcommon'
[2013-06-17 17:27] [PACMAN] upgraded libxkbcommon (0.3.0-1 -> 0.3.1-1)
[2013-06-17 17:28] [PACMAN] Running 'pacman -U --asdeps lib32-libxkbcommon-0.3.1-1-x86_64.pkg.tar.xz'
[2013-06-17 17:28] [PACMAN] upgraded lib32-libxkbcommon (0.3.0-1 -> 0.3.1-1)
[2013-06-17 17:28] [PACMAN] Running 'pacman -Syu'
[2013-06-17 17:28] [PACMAN] synchronizing package lists
[2013-06-17 17:28] [PACMAN] starting full system upgrade
[2013-06-17 17:33] [PACMAN] removed lib32-dbus-core (1.6.10-1)
[2013-06-17 17:33] [PACMAN] upgraded attr (2.4.46-2 -> 2.4.47-1)
[2013-06-17 17:33] [PACMAN] upgraded acl (2.2.51-3 -> 2.2.52-1)
[2013-06-17 17:33] [PACMAN] upgraded attica (0.4.1-2 -> 0.4.2-1)
[2013-06-17 17:33] [PACMAN] upgraded cups-pk-helper (0.2.4-1 -> 0.2.5-1)
[2013-06-17 17:33] [PACMAN] upgraded dbus (1.6.10-1 -> 1.6.12-1)
[2013-06-17 17:33] [PACMAN] upgraded dosfstools (3.0.17-1 -> 3.0.20-1)
[2013-06-17 17:33] [PACMAN] upgraded gtk-update-icon-cache (2.24.18-1 -> 2.24.19-1)
[2013-06-17 17:33] [PACMAN] upgraded gtk2 (2.24.18-1 -> 2.24.19-1)
[2013-06-17 17:33] [PACMAN] upgraded flashplugin (11.2.202.285-1 -> 11.2.202.291-1)
[2013-06-17 17:33] [PACMAN] upgraded libgdm (3.8.1.1-2 -> 3.8.3-1)
[2013-06-17 17:33] [ALPM] warning: directory permissions differ on /var/log/gdm/
filesystem: 711 package: 1770
[2013-06-17 17:33] [PACMAN] upgraded gdm (3.8.1.1-2 -> 3.8.3-1)
[2013-06-17 17:33] [PACMAN] upgraded geoip-database (20130514-1 -> 20130607-1)
[2013-06-17 17:33] [PACMAN] upgraded git (1.8.3-1 -> 1.8.3.1-1)
[2013-06-17 17:33] [PACMAN] upgraded glib2 (2.36.2-1 -> 2.36.3-2)
[2013-06-17 17:33] [PACMAN] upgraded xkeyboard-config (2.9-1 -> 2.9-2)
[2013-06-17 17:33] [PACMAN] upgraded iso-codes (3.41-1 -> 3.43-1)
[2013-06-17 17:33] [PACMAN] upgraded gnome-desktop (1:3.8.3-1 -> 1:3.8.3-2)
[2013-06-17 17:33] [PACMAN] upgraded gnome-user-docs (3.8.1-1 -> 3.8.2-1)
[2013-06-17 17:33] [PACMAN] upgraded graphite (1:1.2.2-1 -> 1:1.2.3-1)
[2013-06-17 17:33] [PACMAN] upgraded gvfs (1.16.2-2 -> 1.16.3-1)
[2013-06-17 17:33] [PACMAN] upgraded gvfs-afc (1.16.2-2 -> 1.16.3-1)
[2013-06-17 17:33] [PACMAN] upgraded gvfs-goa (1.16.2-2 -> 1.16.3-1)
[2013-06-17 17:33] [ALPM-SCRIPTLET] Users no longer need to be in the 'camera' group to use camera devices
[2013-06-17 17:33] [PACMAN] upgraded libgphoto2 (2.5.1-1 -> 2.5.2-1)
[2013-06-17 17:33] [PACMAN] upgraded gvfs-gphoto2 (1.16.2-2 -> 1.16.3-1)
[2013-06-17 17:33] [PACMAN] upgraded gvfs-mtp (1.16.2-2 -> 1.16.3-1)
[2013-06-17 17:33] [PACMAN] upgraded gvfs-obexftp (1.16.2-2 -> 1.16.3-1)
[2013-06-17 17:33] [PACMAN] upgraded gvfs-smb (1.16.2-2 -> 1.16.3-1)
[2013-06-17 17:33] [PACMAN] upgraded hwids (20130512-1 -> 20130607-1)
[2013-06-17 17:33] [PACMAN] upgraded jre7-openjdk-headless (7.u21_2.3.9-4 -> 7.u40_2.4.0-1)
[2013-06-17 17:33] [PACMAN] upgraded jre7-openjdk (7.u21_2.3.9-4 -> 7.u40_2.4.0-1)
[2013-06-17 17:33] [PACMAN] upgraded jdk7-openjdk (7.u21_2.3.9-4 -> 7.u40_2.4.0-1)
[2013-06-17 17:33] [PACMAN] upgraded json-c (0.10-2 -> 0.11-1)
[2013-06-17 17:33] [PACMAN] upgraded krb5 (1.11.2-4 -> 1.11.3-1)
[2013-06-17 17:33] [PACMAN] upgraded lib32-attr (2.4.46-2 -> 2.4.47-1)
[2013-06-17 17:33] [PACMAN] upgraded lib32-acl (2.2.51-2 -> 2.2.52-1)
[2013-06-17 17:33] [PACMAN] installed lib32-dbus (1.6.12-1)
[2013-06-17 17:33] [PACMAN] upgraded lib32-gtk2 (2.24.18-1 -> 2.24.19-1)
[2013-06-17 17:33] [PACMAN] upgraded lib32-json-c (0.10-2 -> 0.11-1)
[2013-06-17 17:33] [PACMAN] upgraded lib32-krb5 (1.11.2-1 -> 1.11.3-1)
[2013-06-17 17:33] [PACMAN] upgraded libpulse (4.0-1 -> 4.0-2)
[2013-06-17 17:33] [PACMAN] upgraded lib32-libpulse (4.0-1 -> 4.0-2)
[2013-06-17 17:33] [PACMAN] upgraded libxrender (0.9.7-1 -> 0.9.8-1)
[2013-06-17 17:33] [PACMAN] upgraded lib32-libxrender (0.9.7-1 -> 0.9.8-1)
[2013-06-17 17:33] [PACMAN] upgraded libbsd (0.4.2-1 -> 0.5.2-1)
[2013-06-17 17:33] [PACMAN] upgraded libmbim (1.0.0-1 -> 1.2.0-1)
[2013-06-17 17:33] [PACMAN] upgraded libnautilus-extension (3.8.1-1 -> 3.8.2-1)
[2013-06-17 17:33] [PACMAN] upgraded libpipeline (1.2.3-1 -> 1.2.4-1)
[2013-06-17 17:33] [PACMAN] upgraded libquvi-scripts (0.4.14-1 -> 0.4.15-1)
[2013-06-17 17:33] [PACMAN] upgraded libusb-compat (0.1.4-2 -> 0.1.5-1)
[2013-06-17 17:33] [PACMAN] upgraded libxvmc (1.0.7-1 -> 1.0.8-1)
[2013-06-17 17:33] [PACMAN] upgraded link-grammar (4.7.11-1 -> 4.7.12-1)
[2013-06-17 17:33] [PACMAN] upgraded linux-firmware (20130528-1 -> 20130610-1)
[2013-06-17 17:33] [ALPM-SCRIPTLET] >>> Updating module dependencies. Please wait ...
[2013-06-17 17:33] [ALPM-SCRIPTLET] >>> Generating initial ramdisk, using mkinitcpio. Please wait...
[2013-06-17 17:33] [ALPM-SCRIPTLET] ==> Building image from preset: /etc/mkinitcpio.d/linux.preset: 'default'
[2013-06-17 17:33] [ALPM-SCRIPTLET] -> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux.img
[2013-06-17 17:33] [ALPM-SCRIPTLET] ==> Starting build: 3.9.6-1-ARCH
[2013-06-17 17:33] [ALPM-SCRIPTLET] -> Running build hook: [base]
[2013-06-17 17:33] [ALPM-SCRIPTLET] -> Running build hook: [udev]
[2013-06-17 17:33] [ALPM-SCRIPTLET] -> Running build hook: [autodetect]
[2013-06-17 17:33] [ALPM-SCRIPTLET] -> Running build hook: [modconf]
[2013-06-17 17:33] [ALPM-SCRIPTLET] -> Running build hook: [block]
[2013-06-17 17:33] [ALPM-SCRIPTLET] -> Running build hook: [filesystems]
[2013-06-17 17:33] [ALPM-SCRIPTLET] -> Running build hook: [keyboard]
[2013-06-17 17:33] [ALPM-SCRIPTLET] -> Running build hook: [fsck]
[2013-06-17 17:33] [ALPM-SCRIPTLET] ==> Generating module dependencies
[2013-06-17 17:33] [ALPM-SCRIPTLET] ==> Creating gzip initcpio image: /boot/initramfs-linux.img
[2013-06-17 17:33] [ALPM-SCRIPTLET] ==> Image generation successful
[2013-06-17 17:33] [ALPM-SCRIPTLET] ==> Building image from preset: /etc/mkinitcpio.d/linux.preset: 'fallback'
[2013-06-17 17:33] [ALPM-SCRIPTLET] -> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux-fallback.img -S autodetect
[2013-06-17 17:33] [ALPM-SCRIPTLET] ==> Starting build: 3.9.6-1-ARCH
[2013-06-17 17:33] [ALPM-SCRIPTLET] -> Running build hook: [base]
[2013-06-17 17:33] [ALPM-SCRIPTLET] -> Running build hook: [udev]
[2013-06-17 17:33] [ALPM-SCRIPTLET] -> Running build hook: [modconf]
[2013-06-17 17:33] [ALPM-SCRIPTLET] -> Running build hook: [block]
[2013-06-17 17:33] [ALPM-SCRIPTLET] ==> WARNING: Possibly missing firmware for module: bfa
[2013-06-17 17:33] [ALPM-SCRIPTLET] ==> WARNING: Possibly missing firmware for module: aic94xx
[2013-06-17 17:33] [ALPM-SCRIPTLET] -> Running build hook: [filesystems]
[2013-06-17 17:33] [ALPM-SCRIPTLET] -> Running build hook: [keyboard]
[2013-06-17 17:33] [ALPM-SCRIPTLET] -> Running build hook: [fsck]
[2013-06-17 17:33] [ALPM-SCRIPTLET] ==> Generating module dependencies
[2013-06-17 17:33] [ALPM-SCRIPTLET] ==> Creating gzip initcpio image: /boot/initramfs-linux-fallback.img
[2013-06-17 17:33] [ALPM-SCRIPTLET] ==> Image generation successful
[2013-06-17 17:33] [PACMAN] upgraded linux (3.9.5-1 -> 3.9.6-1)
[2013-06-17 17:33] [PACMAN] upgraded linux-headers (3.9.5-1 -> 3.9.6-1)
[2013-06-17 17:33] [PACMAN] upgraded lirc-utils (1:0.9.0-46 -> 1:0.9.0-47)
[2013-06-17 17:33] [PACMAN] upgraded mime-types (8-1 -> 9-1)
[2013-06-17 17:33] [ALPM] warning: extracting /usr/share/applications/nautilus.desktop as /usr/share/applications/nautilus.desktop.pacnew
[2013-06-17 17:33] [ALPM] warning: extracting /usr/share/applications/nautilus-autorun-software.desktop as /usr/share/applications/nautilus-autorun-software.desktop.pacnew
[2013-06-17 17:34] [PACMAN] upgraded nautilus (3.8.1-1 -> 3.8.2-1)
[2013-06-17 17:34] [PACMAN] upgraded p7zip (9.20.1-6 -> 9.20.1-7)
[2013-06-17 17:34] [ALPM] warning: /etc/ppp/ip-down.d/00-dns.sh installed as /etc/ppp/ip-down.d/00-dns.sh.pacnew
[2013-06-17 17:34] [ALPM] warning: /etc/ppp/ip-up.d/00-dns.sh installed as /etc/ppp/ip-up.d/00-dns.sh.pacnew
[2013-06-17 17:34] [PACMAN] upgraded ppp (2.4.5-6 -> 2.4.5-7)
[2013-06-17 17:34] [ALPM-SCRIPTLET] >>> If you have per-user copies of configuration files (such as client.conf,
[2013-06-17 17:34] [ALPM-SCRIPTLET] daemon.conf or default.pa) in ~/.pulse/, make sure you keep them in sync
[2013-06-17 17:34] [ALPM-SCRIPTLET] with changes to the packaged files in /etc/pulse/. Otherwise, PulseAudio
[2013-06-17 17:34] [ALPM-SCRIPTLET] may refuse to start due to configuration errors.
[2013-06-17 17:34] [PACMAN] upgraded pulseaudio (4.0-1 -> 4.0-2)
[2013-06-17 17:34] [PACMAN] upgraded python-dbus-common (1.1.1-2 -> 1.2.0-1)
[2013-06-17 17:34] [PACMAN] upgraded python-dbus (1.1.1-2 -> 1.2.0-1)
[2013-06-17 17:34] [PACMAN] upgraded python2-dbus (1.1.1-2 -> 1.2.0-1)
[2013-06-17 17:34] [PACMAN] upgraded sdparm (1.07-1 -> 1.08-1)
[2013-06-17 17:34] [PACMAN] upgraded sg3_utils (1.35-1 -> 1.36-1)
[2013-06-17 17:34] [PACMAN] upgraded shared-desktop-ontologies (0.10.0-1 -> 0.11.0-1)
[2013-06-17 17:34] [PACMAN] upgraded subversion (1.7.9-6 -> 1.7.10-1)
[2013-06-17 17:34] [PACMAN] upgraded sudo (1.8.6.p8-2 -> 1.8.7-1)
[2013-06-17 17:34] [PACMAN] upgraded syslog-ng (3.4.1-3 -> 3.4.2-1)
[2013-06-17 17:34] [PACMAN] upgraded usbutils (006-1 -> 007-1)
[2013-06-17 17:34] [PACMAN] upgraded webkitgtk (2.0.2-3 -> 2.0.3-1)
[2013-06-17 17:34] [PACMAN] upgraded wine (1.6rc1-1 -> 1.6rc2-1)
I'm marking this thread solved for now. If the problem arises again, I'll reopen it.

Unable to use device as an iSCSI target

Similar Messages

Maybe you are looking for