You are not logged in.

#1 2014-11-24 17:08:57

penright14
Member
Registered: 2014-11-20
Posts: 35

[SLOVED] .rule required for udev to start an enabled network@.service?

Solved
Bottom line there was a type-0 :-( For the install section on the Unit's Wantedby entry, I had 'multi.user.target.wants' instead of 'multi-user.taget.wants'  Googling systemd boot progress or course took me to the systemd wiki. https://wiki.archlinux.org/index.php/Systemd_FAQ One of the early discussion was on getty. Reading down it talked about adding a "tty2" if you wanted to auto start a second getty without the alt+f2. Looking at the Unit definition and the getty.target.wants directory, I started connecting the dots. I notice there was a multi.user.target.wants and multi-user.target.wants under the /etc/systemd/system directory. My unit was installed in the 'multi.user.target.wants' and inside the 'multi-user.target.wants' was dhcpd@_ens32.service and then the light bulb went off. So I changed the install section "WantedBy" to multi-user.target.wants, enable and now there is a network@ens32.service in the directory. Also disabled the dhcpd@_ens32.service and that was removed. Rebooted and the IP connection came up automatically. Still have a lot to understand systemd, but the targets vs. run levels make a little more sense now.

Begin of original post -------------------------
Hopefully, someday my questions may deserve not to be in the newbie section, but until then......

Question on udev and networks. In the wiki on networks https://wiki.archlinux.org/index.php/Ne … figuration, in the section on specifying static ip, it talks about setting a rule. I thought the rule was just to have a constant device name. Since I only have one, I did not make a rule. Do you have to have one for udev start the service? I have a network@.service and the unit works if I run the service manually 'systemctl start network@ens32.service. Just not at boot up.

Last edited by penright14 (2014-11-25 12:49:36)

Offline

#2 2014-11-24 17:28:20

jasonwryan
Anarchist
From: .nz
Registered: 2009-05-09
Posts: 30,424
Website

Re: [SLOVED] .rule required for udev to start an enabled network@.service?

Did you enable it?


Arch + dwm   •   Mercurial repos  •   Surfraw

Registered Linux User #482438

Offline

#3 2014-11-24 18:48:08

penright14
Member
Registered: 2014-11-20
Posts: 35

Re: [SLOVED] .rule required for udev to start an enabled network@.service?

jasonwryan wrote:

Did you enable it?

Yes, 'systemctl enable network@.service. But when I systemctl status netwrok@.service I see 'Failed to get properties: Unit name network@.service is not valid. But it is because systemctl@ens32.service seems to work. There something simple I missing, just not seeing it yet.

Last edited by penright14 (2014-11-24 18:48:24)

Offline

#4 2014-11-24 19:48:21

jasonwryan
Anarchist
From: .nz
Registered: 2009-05-09
Posts: 30,424
Website

Re: [SLOVED] .rule required for udev to start an enabled network@.service?

Please post the output of `ip a` and your service file.


Arch + dwm   •   Mercurial repos  •   Surfraw

Registered Linux User #482438

Offline

#5 2014-11-24 20:09:20

penright14
Member
Registered: 2014-11-20
Posts: 35

Re: [SLOVED] .rule required for udev to start an enabled network@.service?

jasonwryan wrote:

Please post the output of `ip a`

1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default 
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host 
       valid_lft forever preferred_lft forever
2: ens32: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
    link/ether 00:50:56:97:0d:a3 brd ff:ff:ff:ff:ff:ff
    inet 192.168.60.120/24 brd 192.168.60.255 scope global ens32
       valid_lft forever preferred_lft forever
    inet6 fe80::250:56ff:fe97:da3/64 scope link 
       valid_lft forever preferred_lft forever
jasonwryan wrote:

Please post the output of your service file.

I am assuming cat network@.service?

[Unit]
Description=Network connectivity (%i)
Wants=network.target
Before=network.target
BindsTo=sys-subsystem-net-devices-%i.device
After=sys-subsystem-net-devices-%i.device

[Service]
Type=oneshot
RemainAfterExit=yes
EnvironmentFile=/etc/conf.d/net-conf-%i
ExecStart=/usr/local/bin/net-up.sh %i
ExecStop=/usr/local/bin/net-down.sh %i

[Install]
WantedBy=multi.user.target

Last edited by penright14 (2014-11-25 11:25:30)

Offline

#6 2014-11-24 20:25:37

jasonwryan
Anarchist
From: .nz
Registered: 2009-05-09
Posts: 30,424
Website

Re: [SLOVED] .rule required for udev to start an enabled network@.service?

Please use code tags when pasting to the boards: https://wiki.archlinux.org/index.php/Fo … s_and_Code


So, the status is determined by `systemctl status network@ens32`... and similarly for enable.


Arch + dwm   •   Mercurial repos  •   Surfraw

Registered Linux User #482438

Offline

#7 2014-11-24 21:59:49

penright14
Member
Registered: 2014-11-20
Posts: 35

Re: [SLOVED] .rule required for udev to start an enabled network@.service?

jasonwryan wrote:

So, the status is determined by `systemctl status network@ens32`... and similarly for enable.

I think I found my misunderstanding. Let me throw this out.
First after reading network@.service, the device would show up between @ and .service, and it does. if I run systemctl start network@ens32.service, it starts. Now, if I systemctl enable network@ens32.service, reboot the service does not start automatically. But I thought that udev would run unit network@.service for any class/net devices it found, hence 'systemctl enable network@.service'.

Let me also say, I am trying to understand this, because the purpose of this Arch is to create an environment, for me to create a rootfs for pxe boot so you will see why I am wanting a rule.The assumption for the pxe booted device is there will only be one network card. And there is a good chance it will be dhcp, but I still want to understand how to get a static IP working on different nic.
Now, if I understand right .... I need a rule that will rename whatever the nic is to say 'net0'. then I would 'systemctl enable network@net0.service' ?


If I did enable "net0" and the rule was working, would the service start? The reason for the question is because, I have enabled ens32 and it does not seem to start. A 'systemctl status network@ens32.service' give me Loaded: loaded (/etc/systemd/system/network@service; enabled) but the Active line says Active: inactive (dead). If I run systemctl start network@ens32.service, then I get Active: active (exited) the date, process number, script name, PID, and exit code status of 0. This makes me wonder why udev is not starting ens32 even though I have it enabled. Will it work if I get the rule switch to net0 and enable net0?

Let me add one other detail in case it matters, this is a VM running on ESX host.

Offline

#8 2014-11-24 22:20:47

jasonwryan
Anarchist
From: .nz
Registered: 2009-05-09
Posts: 30,424
Website

Re: [SLOVED] .rule required for udev to start an enabled network@.service?

Your overall approach seems correct. As to why the enabled service is not starting (or is exiting), you'd need to dig into the journal more to track that down.


Arch + dwm   •   Mercurial repos  •   Surfraw

Registered Linux User #482438

Offline

#9 2014-11-24 22:35:07

TheSaint
Member
From: my computer
Registered: 2007-08-19
Posts: 1,523

Re: [SLOVED] .rule required for udev to start an enabled network@.service?

I suspect that in several case the cause is dhcpcd starts too early.
In case of fixed IP, it'd works and in such circumstance it'll confirm my theory.
Connections manager provide a second chance to connect dynamic IP.


do it good first, it will be faster than do it twice the saint wink

Offline

#10 2014-11-24 23:03:51

penright14
Member
Registered: 2014-11-20
Posts: 35

Re: [SLOVED] .rule required for udev to start an enabled network@.service?

jasonwryan wrote:

Your overall approach seems correct. As to why the enabled service is not starting (or is exiting), you'd need to dig into the journal more to track that down.

Below is the log, but there is an interesting snippet

Nov 24 16:35:28 PingBuild kernel: e1000: Intel(R) PRO/1000 Network Driver - version 7.3.21-k8-NAPI
Nov 24 16:35:28 PingBuild kernel: e1000: Copyright (c) 1999-2006 Intel Corporation.
Nov 24 16:35:28 PingBuild kernel: input: PC Speaker as /devices/platform/pcspkr/input/input4
Nov 24 16:35:28 PingBuild kernel: ppdev: user-space parallel port driver
Nov 24 16:35:28 PingBuild kernel: e1000 0000:02:00.0 eth0: (PCI:66MHz:32-bit) 00:50:56:97:0d:a3
Nov 24 16:35:28 PingBuild kernel: e1000 0000:02:00.0 eth0: Intel(R) PRO/1000 Network Connection
Nov 24 16:35:28 PingBuild kernel: e1000 0000:02:00.0 ens32: renamed from eth0

I was looking in my /etc/udev/rules.d directory is empty. So there must be (one of the do not change rule) in the /usr/lib/udev/rules.d directory that is renaming eth0 to ens32. Can I count on nic being called ens32 or do I still need to override it?

-- Subject: System start-up is now complete
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- All system services necessary queued for starting at boot have been
-- successfully started. Note that this does not mean that the machine is
-- now idle as services might still be busy with completing start-up.
-- 
-- Kernel start-up required KERNEL_USEC microseconds.
-- 
-- Initial RAM disk start-up required INITRD_USEC microseconds.
-- 
-- Userspace start-up required 44790 microseconds.
Nov 24 16:35:41 PingBuild login[171]: ROOT LOGIN ON tty1
Nov 24 16:36:55 PingBuild systemd[1]: Job sys-subsystem-net-devices-_ens32.device/start timed out.
Nov 24 16:36:55 PingBuild systemd[1]: Timed out waiting for device sys-subsystem-net-devices-_ens32.device.
-- Subject: Unit sys-subsystem-net-devices-_ens32.device has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- Unit sys-subsystem-net-devices-_ens32.device has failed.
-- 
-- The result is timeout.
Nov 24 16:36:55 PingBuild systemd[1]: Dependency failed for dhcpcd on _ens32.
-- Subject: Unit dhcpcd@_ens32.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- Unit dhcpcd@_ens32.service has failed.
-- 
-- The result is dependency.

Looking at the above snippet, it looks like something about DHCP failed, I am sure I have 'systemctl disable dhcpcd'. Also the ens32 device issues are after I logged on tty1 and started the ens32 service. I must be missing something again. :-(



The entire log. journalctl -xe>/tmp.txt

-- Logs begin at Wed 2014-11-19 16:23:50 CST, end at Mon 2014-11-24 16:47:57 CST. --
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:16.2: PME# supported from D0 D3hot D3cold
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:16.2: System wakeup disabled by ACPI
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:16.3: [15ad:07a0] type 01 class 0x060400
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:16.3: PME# supported from D0 D3hot D3cold
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:16.3: System wakeup disabled by ACPI
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:16.4: [15ad:07a0] type 01 class 0x060400
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:16.4: PME# supported from D0 D3hot D3cold
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:16.4: System wakeup disabled by ACPI
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:16.5: [15ad:07a0] type 01 class 0x060400
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:16.5: PME# supported from D0 D3hot D3cold
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:16.5: System wakeup disabled by ACPI
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:16.6: [15ad:07a0] type 01 class 0x060400
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:16.6: PME# supported from D0 D3hot D3cold
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:16.6: System wakeup disabled by ACPI
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:16.7: [15ad:07a0] type 01 class 0x060400
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:16.7: PME# supported from D0 D3hot D3cold
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:16.7: System wakeup disabled by ACPI
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:17.0: [15ad:07a0] type 01 class 0x060400
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:17.0: PME# supported from D0 D3hot D3cold
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:17.0: System wakeup disabled by ACPI
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:17.1: [15ad:07a0] type 01 class 0x060400
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:17.1: PME# supported from D0 D3hot D3cold
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:17.1: System wakeup disabled by ACPI
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:17.2: [15ad:07a0] type 01 class 0x060400
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:17.2: PME# supported from D0 D3hot D3cold
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:17.2: System wakeup disabled by ACPI
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:17.3: [15ad:07a0] type 01 class 0x060400
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:17.3: PME# supported from D0 D3hot D3cold
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:17.3: System wakeup disabled by ACPI
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:17.4: [15ad:07a0] type 01 class 0x060400
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:17.4: PME# supported from D0 D3hot D3cold
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:17.4: System wakeup disabled by ACPI
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:17.5: [15ad:07a0] type 01 class 0x060400
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:17.5: PME# supported from D0 D3hot D3cold
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:17.5: System wakeup disabled by ACPI
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:17.6: [15ad:07a0] type 01 class 0x060400
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:17.6: PME# supported from D0 D3hot D3cold
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:17.6: System wakeup disabled by ACPI
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:17.7: [15ad:07a0] type 01 class 0x060400
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:17.7: PME# supported from D0 D3hot D3cold
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:17.7: System wakeup disabled by ACPI
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:18.0: [15ad:07a0] type 01 class 0x060400
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:18.0: PME# supported from D0 D3hot D3cold
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:18.0: System wakeup disabled by ACPI
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:18.1: [15ad:07a0] type 01 class 0x060400
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:18.1: PME# supported from D0 D3hot D3cold
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:18.1: System wakeup disabled by ACPI
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:18.2: [15ad:07a0] type 01 class 0x060400
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:18.2: PME# supported from D0 D3hot D3cold
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:18.2: System wakeup disabled by ACPI
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:18.3: [15ad:07a0] type 01 class 0x060400
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:18.3: PME# supported from D0 D3hot D3cold
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:18.3: System wakeup disabled by ACPI
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:18.4: [15ad:07a0] type 01 class 0x060400
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:18.4: PME# supported from D0 D3hot D3cold
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:18.4: System wakeup disabled by ACPI
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:18.5: [15ad:07a0] type 01 class 0x060400
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:18.5: PME# supported from D0 D3hot D3cold
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:18.5: System wakeup disabled by ACPI
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:18.6: [15ad:07a0] type 01 class 0x060400
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:18.6: PME# supported from D0 D3hot D3cold
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:18.6: System wakeup disabled by ACPI
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:18.7: [15ad:07a0] type 01 class 0x060400
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:18.7: PME# supported from D0 D3hot D3cold
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:18.7: System wakeup disabled by ACPI
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:01.0: PCI bridge to [bus 01]
Nov 24 16:35:28 PingBuild kernel: acpiphp: Slot [32] registered
Nov 24 16:35:28 PingBuild kernel: acpiphp: Slot [33] registered
Nov 24 16:35:28 PingBuild kernel: acpiphp: Slot [34] registered
Nov 24 16:35:28 PingBuild kernel: acpiphp: Slot [35] registered
Nov 24 16:35:28 PingBuild kernel: acpiphp: Slot [36] registered
Nov 24 16:35:28 PingBuild kernel: acpiphp: Slot [37] registered
Nov 24 16:35:28 PingBuild kernel: acpiphp: Slot [38] registered
Nov 24 16:35:28 PingBuild kernel: acpiphp: Slot [39] registered
Nov 24 16:35:28 PingBuild kernel: acpiphp: Slot [40] registered
Nov 24 16:35:28 PingBuild kernel: acpiphp: Slot [41] registered
Nov 24 16:35:28 PingBuild kernel: acpiphp: Slot [42] registered
Nov 24 16:35:28 PingBuild kernel: acpiphp: Slot [43] registered
Nov 24 16:35:28 PingBuild kernel: acpiphp: Slot [44] registered
Nov 24 16:35:28 PingBuild kernel: acpiphp: Slot [45] registered
Nov 24 16:35:28 PingBuild kernel: acpiphp: Slot [46] registered
Nov 24 16:35:28 PingBuild kernel: acpiphp: Slot [47] registered
Nov 24 16:35:28 PingBuild kernel: acpiphp: Slot [48] registered
Nov 24 16:35:28 PingBuild kernel: acpiphp: Slot [49] registered
Nov 24 16:35:28 PingBuild kernel: acpiphp: Slot [50] registered
Nov 24 16:35:28 PingBuild kernel: acpiphp: Slot [51] registered
Nov 24 16:35:28 PingBuild kernel: acpiphp: Slot [52] registered
Nov 24 16:35:28 PingBuild kernel: acpiphp: Slot [53] registered
Nov 24 16:35:28 PingBuild kernel: acpiphp: Slot [54] registered
Nov 24 16:35:28 PingBuild kernel: acpiphp: Slot [55] registered
Nov 24 16:35:28 PingBuild kernel: acpiphp: Slot [56] registered
Nov 24 16:35:28 PingBuild kernel: acpiphp: Slot [57] registered
Nov 24 16:35:28 PingBuild kernel: acpiphp: Slot [58] registered
Nov 24 16:35:28 PingBuild kernel: acpiphp: Slot [59] registered
Nov 24 16:35:28 PingBuild kernel: acpiphp: Slot [60] registered
Nov 24 16:35:28 PingBuild kernel: acpiphp: Slot [61] registered
Nov 24 16:35:28 PingBuild kernel: acpiphp: Slot [62] registered
Nov 24 16:35:28 PingBuild kernel: acpiphp: Slot [63] registered
Nov 24 16:35:28 PingBuild kernel: pci 0000:02:00.0: [8086:100f] type 00 class 0x020000
Nov 24 16:35:28 PingBuild kernel: pci 0000:02:00.0: reg 0x10: [mem 0xd1020000-0xd103ffff 64bit]
Nov 24 16:35:28 PingBuild kernel: pci 0000:02:00.0: reg 0x18: [mem 0xd1000000-0xd100ffff 64bit]
Nov 24 16:35:28 PingBuild kernel: pci 0000:02:00.0: reg 0x20: [io  0x2000-0x203f]
Nov 24 16:35:28 PingBuild kernel: pci 0000:02:00.0: reg 0x30: [mem 0x00000000-0x0000ffff pref]
Nov 24 16:35:28 PingBuild kernel: pci 0000:02:00.0: PME# supported from D0 D3hot D3cold
Nov 24 16:35:28 PingBuild kernel: pci 0000:02:00.0: System wakeup disabled by ACPI
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:11.0: PCI bridge to [bus 02] (subtractive decode)
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:11.0:   bridge window [io  0x2000-0x3fff]
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:11.0:   bridge window [mem 0xd1000000-0xd23fffff]
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:11.0:   bridge window [mem 0xdc400000-0xdc9fffff 64bit pref]
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:11.0:   bridge window [mem 0x000a0000-0x000bffff] (subtractive decode)
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:11.0:   bridge window [mem 0x000cc000-0x000cffff] (subtractive decode)
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:11.0:   bridge window [mem 0x000d0000-0x000d3fff] (subtractive decode)
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:11.0:   bridge window [mem 0x000d4000-0x000d7fff] (subtractive decode)
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:11.0:   bridge window [mem 0x000d8000-0x000dbfff] (subtractive decode)
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:11.0:   bridge window [mem 0xc0000000-0xfebfffff] (subtractive decode)
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:11.0:   bridge window [io  0x0000-0x0cf7] (subtractive decode)
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:11.0:   bridge window [io  0x0d00-0xfeff] (subtractive decode)
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:15.0: PCI bridge to [bus 03]
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:15.0:   bridge window [io  0x4000-0x4fff]
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:15.0:   bridge window [mem 0xd2400000-0xd24fffff]
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:15.0:   bridge window [mem 0xd4400000-0xd44fffff 64bit pref]
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:15.1: PCI bridge to [bus 04]
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:15.1:   bridge window [io  0x8000-0x8fff]
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:15.1:   bridge window [mem 0xd2800000-0xd28fffff]
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:15.1:   bridge window [mem 0xd4800000-0xd48fffff 64bit pref]
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:15.2: PCI bridge to [bus 05]
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:15.2:   bridge window [io  0xc000-0xcfff]
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:15.2:   bridge window [mem 0xd2c00000-0xd2cfffff]
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:15.2:   bridge window [mem 0xdcb00000-0xdcbfffff 64bit pref]
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:15.3: PCI bridge to [bus 06]
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:15.3:   bridge window [mem 0xd3000000-0xd30fffff]
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:15.3:   bridge window [mem 0xdcd00000-0xdcdfffff 64bit pref]
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:15.4: PCI bridge to [bus 07]
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:15.4:   bridge window [mem 0xd3400000-0xd34fffff]
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:15.4:   bridge window [mem 0xdcf00000-0xdcffffff 64bit pref]
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:15.5: PCI bridge to [bus 08]
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:15.5:   bridge window [mem 0xd3800000-0xd38fffff]
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:15.5:   bridge window [mem 0xdd100000-0xdd1fffff 64bit pref]
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:15.6: PCI bridge to [bus 09]
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:15.6:   bridge window [mem 0xd3c00000-0xd3cfffff]
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:15.6:   bridge window [mem 0xdd300000-0xdd3fffff 64bit pref]
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:15.7: PCI bridge to [bus 0a]
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:15.7:   bridge window [mem 0xd4000000-0xd40fffff]
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:15.7:   bridge window [mem 0xdd500000-0xdd5fffff 64bit pref]
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:16.0: PCI bridge to [bus 0b]
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:16.0:   bridge window [io  0x5000-0x5fff]
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:16.0:   bridge window [mem 0xd2500000-0xd25fffff]
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:16.0:   bridge window [mem 0xd4500000-0xd45fffff 64bit pref]
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:16.1: PCI bridge to [bus 0c]
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:16.1:   bridge window [io  0x9000-0x9fff]
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:16.1:   bridge window [mem 0xd2900000-0xd29fffff]
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:16.1:   bridge window [mem 0xd4900000-0xd49fffff 64bit pref]
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:16.2: PCI bridge to [bus 0d]
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:16.2:   bridge window [io  0xd000-0xdfff]
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:16.2:   bridge window [mem 0xd2d00000-0xd2dfffff]
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:16.2:   bridge window [mem 0xd4b00000-0xd4bfffff 64bit pref]
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:16.3: PCI bridge to [bus 0e]
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:16.3:   bridge window [mem 0xd3100000-0xd31fffff]
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:16.3:   bridge window [mem 0xd4d00000-0xd4dfffff 64bit pref]
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:16.4: PCI bridge to [bus 0f]
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:16.4:   bridge window [mem 0xd3500000-0xd35fffff]
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:16.4:   bridge window [mem 0xd4f00000-0xd4ffffff 64bit pref]
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:16.5: PCI bridge to [bus 10]
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:16.5:   bridge window [mem 0xd3900000-0xd39fffff]
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:16.5:   bridge window [mem 0xd5100000-0xd51fffff 64bit pref]
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:16.6: PCI bridge to [bus 11]
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:16.6:   bridge window [mem 0xd3d00000-0xd3dfffff]
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:16.6:   bridge window [mem 0xd5300000-0xd53fffff 64bit pref]
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:16.7: PCI bridge to [bus 12]
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:16.7:   bridge window [mem 0xd4100000-0xd41fffff]
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:16.7:   bridge window [mem 0xd5500000-0xd55fffff 64bit pref]
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:17.0: PCI bridge to [bus 13]
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:17.0:   bridge window [io  0x6000-0x6fff]
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:17.0:   bridge window [mem 0xd2600000-0xd26fffff]
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:17.0:   bridge window [mem 0xd4600000-0xd46fffff 64bit pref]
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:17.1: PCI bridge to [bus 14]
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:17.1:   bridge window [io  0xa000-0xafff]
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:17.1:   bridge window [mem 0xd2a00000-0xd2afffff]
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:17.1:   bridge window [mem 0xdca00000-0xdcafffff 64bit pref]
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:17.2: PCI bridge to [bus 15]
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:17.2:   bridge window [io  0xe000-0xefff]
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:17.2:   bridge window [mem 0xd2e00000-0xd2efffff]
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:17.2:   bridge window [mem 0xdcc00000-0xdccfffff 64bit pref]
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:17.3: PCI bridge to [bus 16]
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:17.3:   bridge window [mem 0xd3200000-0xd32fffff]
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:17.3:   bridge window [mem 0xdce00000-0xdcefffff 64bit pref]
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:17.4: PCI bridge to [bus 17]
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:17.4:   bridge window [mem 0xd3600000-0xd36fffff]
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:17.4:   bridge window [mem 0xdd000000-0xdd0fffff 64bit pref]
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:17.5: PCI bridge to [bus 18]
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:17.5:   bridge window [mem 0xd3a00000-0xd3afffff]
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:17.5:   bridge window [mem 0xdd200000-0xdd2fffff 64bit pref]
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:17.6: PCI bridge to [bus 19]
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:17.6:   bridge window [mem 0xd3e00000-0xd3efffff]
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:17.6:   bridge window [mem 0xdd400000-0xdd4fffff 64bit pref]
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:17.7: PCI bridge to [bus 1a]
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:17.7:   bridge window [mem 0xd4200000-0xd42fffff]
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:17.7:   bridge window [mem 0xdd600000-0xdd6fffff 64bit pref]
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:18.0: PCI bridge to [bus 1b]
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:18.0:   bridge window [io  0x7000-0x7fff]
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:18.0:   bridge window [mem 0xd2700000-0xd27fffff]
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:18.0:   bridge window [mem 0xd4700000-0xd47fffff 64bit pref]
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:18.1: PCI bridge to [bus 1c]
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:18.1:   bridge window [io  0xb000-0xbfff]
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:18.1:   bridge window [mem 0xd2b00000-0xd2bfffff]
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:18.1:   bridge window [mem 0xd4a00000-0xd4afffff 64bit pref]
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:18.2: PCI bridge to [bus 1d]
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:18.2:   bridge window [io  0xf000-0xffff]
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:18.2:   bridge window [mem 0xd2f00000-0xd2ffffff]
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:18.2:   bridge window [mem 0xd4c00000-0xd4cfffff 64bit pref]
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:18.3: PCI bridge to [bus 1e]
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:18.3:   bridge window [mem 0xd3300000-0xd33fffff]
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:18.3:   bridge window [mem 0xd4e00000-0xd4efffff 64bit pref]
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:18.4: PCI bridge to [bus 1f]
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:18.4:   bridge window [mem 0xd3700000-0xd37fffff]
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:18.4:   bridge window [mem 0xd5000000-0xd50fffff 64bit pref]
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:18.5: PCI bridge to [bus 20]
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:18.5:   bridge window [mem 0xd3b00000-0xd3bfffff]
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:18.5:   bridge window [mem 0xd5200000-0xd52fffff 64bit pref]
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:18.6: PCI bridge to [bus 21]
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:18.6:   bridge window [mem 0xd3f00000-0xd3ffffff]
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:18.6:   bridge window [mem 0xd5400000-0xd54fffff 64bit pref]
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:18.7: PCI bridge to [bus 22]
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:18.7:   bridge window [mem 0xd4300000-0xd43fffff]
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:18.7:   bridge window [mem 0xd5600000-0xd56fffff 64bit pref]
Nov 24 16:35:28 PingBuild kernel: ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 6 7 *9 10 11 14 15)
Nov 24 16:35:28 PingBuild kernel: ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 6 7 9 10 *11 14 15)
Nov 24 16:35:28 PingBuild kernel: ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 5 6 7 9 *10 11 14 15)
Nov 24 16:35:28 PingBuild kernel: ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 5 6 7 9 10 11 14 15) *0, disabled.
Nov 24 16:35:28 PingBuild kernel: ACPI: Enabled 2 GPEs in block 00 to 0F
Nov 24 16:35:28 PingBuild kernel: vgaarb: setting as boot device: PCI:0000:00:0f.0
Nov 24 16:35:28 PingBuild kernel: vgaarb: device added: PCI:0000:00:0f.0,decodes=io+mem,owns=io+mem,locks=none
Nov 24 16:35:28 PingBuild kernel: vgaarb: loaded
Nov 24 16:35:28 PingBuild kernel: vgaarb: bridge control possible 0000:00:0f.0
Nov 24 16:35:28 PingBuild kernel: PCI: Using ACPI for IRQ routing
Nov 24 16:35:28 PingBuild kernel: PCI: pci_cache_line_size set to 64 bytes
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:18.2: can't claim BAR 13 [io  0xf000-0xffff]: no compatible bridge window
Nov 24 16:35:28 PingBuild kernel: e820: reserve RAM buffer [mem 0x0009f800-0x0009ffff]
Nov 24 16:35:28 PingBuild kernel: e820: reserve RAM buffer [mem 0xbfef0000-0xbfffffff]
Nov 24 16:35:28 PingBuild kernel: NetLabel: Initializing
Nov 24 16:35:28 PingBuild kernel: NetLabel:  domain hash size = 128
Nov 24 16:35:28 PingBuild kernel: NetLabel:  protocols = UNLABELED CIPSOv4
Nov 24 16:35:28 PingBuild kernel: NetLabel:  unlabeled traffic allowed by default
Nov 24 16:35:28 PingBuild kernel: HPET: 16 timers in total, 0 timers will be used for per-cpu timer
Nov 24 16:35:28 PingBuild kernel: hpet0: at MMIO 0xfed00000, IRQs 2, 8, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0
Nov 24 16:35:28 PingBuild kernel: hpet0: 16 comparators, 64-bit 14.318180 MHz counter
Nov 24 16:35:28 PingBuild kernel: Switched to clocksource hpet
Nov 24 16:35:28 PingBuild kernel: pnp: PnP ACPI init
Nov 24 16:35:28 PingBuild kernel: system 00:00: [io  0x1000-0x103f] could not be reserved
Nov 24 16:35:28 PingBuild kernel: system 00:00: [io  0x1040-0x104f] has been reserved
Nov 24 16:35:28 PingBuild kernel: system 00:00: [io  0x0cf0-0x0cf1] has been reserved
Nov 24 16:35:28 PingBuild kernel: system 00:00: Plug and Play ACPI device, IDs PNP0c02 (active)
Nov 24 16:35:28 PingBuild kernel: pnp 00:01: Plug and Play ACPI device, IDs PNP0b00 (active)
Nov 24 16:35:28 PingBuild kernel: pnp 00:02: Plug and Play ACPI device, IDs PNP0303 (active)
Nov 24 16:35:28 PingBuild kernel: pnp 00:03: Plug and Play ACPI device, IDs PNP0f13 (active)
Nov 24 16:35:28 PingBuild kernel: system 00:04: [mem 0xfed00000-0xfed003ff] has been reserved
Nov 24 16:35:28 PingBuild kernel: system 00:04: Plug and Play ACPI device, IDs PNP0103 PNP0c01 (active)
Nov 24 16:35:28 PingBuild kernel: pnp 00:05: Plug and Play ACPI device, IDs PNP0400 (active)
Nov 24 16:35:28 PingBuild kernel: pnp 00:06: Plug and Play ACPI device, IDs PNP0501 (active)
Nov 24 16:35:28 PingBuild kernel: pnp 00:07: Plug and Play ACPI device, IDs PNP0501 (active)
Nov 24 16:35:28 PingBuild kernel: pnp 00:08: [dma 2]
Nov 24 16:35:28 PingBuild kernel: pnp 00:08: Plug and Play ACPI device, IDs PNP0700 (active)
Nov 24 16:35:28 PingBuild kernel: system 00:09: [io  0x1060-0x107f] has been reserved
Nov 24 16:35:28 PingBuild kernel: system 00:09: [mem 0xe0000000-0xefffffff] has been reserved
Nov 24 16:35:28 PingBuild kernel: system 00:09: [mem 0xd0200000-0xd03fffff] has been reserved
Nov 24 16:35:28 PingBuild kernel: system 00:09: Plug and Play ACPI device, IDs PNP0c02 (active)
Nov 24 16:35:28 PingBuild kernel: pnp: PnP ACPI: found 10 devices
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:15.3: bridge window [io  0x1000-0x0fff] to [bus 06] add_size 1000
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:15.4: bridge window [io  0x1000-0x0fff] to [bus 07] add_size 1000
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:15.5: bridge window [io  0x1000-0x0fff] to [bus 08] add_size 1000
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:15.6: bridge window [io  0x1000-0x0fff] to [bus 09] add_size 1000
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:15.7: bridge window [io  0x1000-0x0fff] to [bus 0a] add_size 1000
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:16.3: bridge window [io  0x1000-0x0fff] to [bus 0e] add_size 1000
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:16.4: bridge window [io  0x1000-0x0fff] to [bus 0f] add_size 1000
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:16.5: bridge window [io  0x1000-0x0fff] to [bus 10] add_size 1000
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:16.6: bridge window [io  0x1000-0x0fff] to [bus 11] add_size 1000
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:16.7: bridge window [io  0x1000-0x0fff] to [bus 12] add_size 1000
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:17.3: bridge window [io  0x1000-0x0fff] to [bus 16] add_size 1000
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:17.4: bridge window [io  0x1000-0x0fff] to [bus 17] add_size 1000
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:17.5: bridge window [io  0x1000-0x0fff] to [bus 18] add_size 1000
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:17.6: bridge window [io  0x1000-0x0fff] to [bus 19] add_size 1000
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:17.7: bridge window [io  0x1000-0x0fff] to [bus 1a] add_size 1000
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:18.2: bridge window [io  0x1000-0x0fff] to [bus 1d] add_size 1000
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:18.3: bridge window [io  0x1000-0x0fff] to [bus 1e] add_size 1000
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:18.4: bridge window [io  0x1000-0x0fff] to [bus 1f] add_size 1000
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:18.5: bridge window [io  0x1000-0x0fff] to [bus 20] add_size 1000
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:18.6: bridge window [io  0x1000-0x0fff] to [bus 21] add_size 1000
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:18.7: bridge window [io  0x1000-0x0fff] to [bus 22] add_size 1000
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:15.3: res[13]=[io  0x1000-0x0fff] get_res_add_size add_size 1000
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:15.4: res[13]=[io  0x1000-0x0fff] get_res_add_size add_size 1000
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:15.5: res[13]=[io  0x1000-0x0fff] get_res_add_size add_size 1000
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:15.6: res[13]=[io  0x1000-0x0fff] get_res_add_size add_size 1000
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:15.7: res[13]=[io  0x1000-0x0fff] get_res_add_size add_size 1000
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:16.3: res[13]=[io  0x1000-0x0fff] get_res_add_size add_size 1000
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:16.4: res[13]=[io  0x1000-0x0fff] get_res_add_size add_size 1000
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:16.5: res[13]=[io  0x1000-0x0fff] get_res_add_size add_size 1000
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:16.6: res[13]=[io  0x1000-0x0fff] get_res_add_size add_size 1000
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:16.7: res[13]=[io  0x1000-0x0fff] get_res_add_size add_size 1000
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:17.3: res[13]=[io  0x1000-0x0fff] get_res_add_size add_size 1000
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:17.4: res[13]=[io  0x1000-0x0fff] get_res_add_size add_size 1000
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:17.5: res[13]=[io  0x1000-0x0fff] get_res_add_size add_size 1000
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:17.6: res[13]=[io  0x1000-0x0fff] get_res_add_size add_size 1000
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:17.7: res[13]=[io  0x1000-0x0fff] get_res_add_size add_size 1000
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:18.2: res[13]=[io  0x1000-0x0fff] get_res_add_size add_size 1000
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:18.3: res[13]=[io  0x1000-0x0fff] get_res_add_size add_size 1000
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:18.4: res[13]=[io  0x1000-0x0fff] get_res_add_size add_size 1000
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:18.5: res[13]=[io  0x1000-0x0fff] get_res_add_size add_size 1000
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:18.6: res[13]=[io  0x1000-0x0fff] get_res_add_size add_size 1000
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:18.7: res[13]=[io  0x1000-0x0fff] get_res_add_size add_size 1000
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:0f.0: BAR 6: assigned [mem 0xc0000000-0xc0007fff pref]
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:10.0: BAR 6: assigned [mem 0xc0008000-0xc000bfff pref]
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:15.3: BAR 13: no space for [io  size 0x1000]
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:15.3: BAR 13: failed to assign [io  size 0x1000]
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:15.4: BAR 13: no space for [io  size 0x1000]
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:15.4: BAR 13: failed to assign [io  size 0x1000]
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:15.5: BAR 13: no space for [io  size 0x1000]
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:15.5: BAR 13: failed to assign [io  size 0x1000]
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:15.6: BAR 13: no space for [io  size 0x1000]
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:15.6: BAR 13: failed to assign [io  size 0x1000]
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:15.7: BAR 13: no space for [io  size 0x1000]
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:15.7: BAR 13: failed to assign [io  size 0x1000]
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:16.3: BAR 13: no space for [io  size 0x1000]
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:16.3: BAR 13: failed to assign [io  size 0x1000]
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:16.4: BAR 13: no space for [io  size 0x1000]
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:16.4: BAR 13: failed to assign [io  size 0x1000]
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:16.5: BAR 13: no space for [io  size 0x1000]
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:16.5: BAR 13: failed to assign [io  size 0x1000]
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:16.6: BAR 13: no space for [io  size 0x1000]
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:16.6: BAR 13: failed to assign [io  size 0x1000]
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:16.7: BAR 13: no space for [io  size 0x1000]
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:16.7: BAR 13: failed to assign [io  size 0x1000]
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:17.3: BAR 13: no space for [io  size 0x1000]
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:17.3: BAR 13: failed to assign [io  size 0x1000]
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:17.4: BAR 13: no space for [io  size 0x1000]
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:17.4: BAR 13: failed to assign [io  size 0x1000]
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:17.5: BAR 13: no space for [io  size 0x1000]
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:17.5: BAR 13: failed to assign [io  size 0x1000]
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:17.6: BAR 13: no space for [io  size 0x1000]
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:17.6: BAR 13: failed to assign [io  size 0x1000]
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:17.7: BAR 13: no space for [io  size 0x1000]
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:17.7: BAR 13: failed to assign [io  size 0x1000]
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:18.2: BAR 13: no space for [io  size 0x1000]
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:18.2: BAR 13: failed to assign [io  size 0x1000]
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:18.3: BAR 13: no space for [io  size 0x1000]
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:18.3: BAR 13: failed to assign [io  size 0x1000]
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:18.4: BAR 13: no space for [io  size 0x1000]
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:18.4: BAR 13: failed to assign [io  size 0x1000]
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:18.5: BAR 13: no space for [io  size 0x1000]
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:18.5: BAR 13: failed to assign [io  size 0x1000]
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:18.6: BAR 13: no space for [io  size 0x1000]
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:18.6: BAR 13: failed to assign [io  size 0x1000]
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:18.7: BAR 13: no space for [io  size 0x1000]
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:18.7: BAR 13: failed to assign [io  size 0x1000]
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:18.7: BAR 13: no space for [io  size 0x1000]
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:18.7: BAR 13: failed to assign [io  size 0x1000]
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:18.6: BAR 13: no space for [io  size 0x1000]
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:18.6: BAR 13: failed to assign [io  size 0x1000]
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:18.5: BAR 13: no space for [io  size 0x1000]
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:18.5: BAR 13: failed to assign [io  size 0x1000]
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:18.4: BAR 13: no space for [io  size 0x1000]
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:18.4: BAR 13: failed to assign [io  size 0x1000]
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:18.3: BAR 13: no space for [io  size 0x1000]
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:18.3: BAR 13: failed to assign [io  size 0x1000]
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:18.2: BAR 13: no space for [io  size 0x1000]
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:18.2: BAR 13: failed to assign [io  size 0x1000]
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:17.7: BAR 13: no space for [io  size 0x1000]
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:17.7: BAR 13: failed to assign [io  size 0x1000]
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:17.6: BAR 13: no space for [io  size 0x1000]
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:17.6: BAR 13: failed to assign [io  size 0x1000]
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:17.5: BAR 13: no space for [io  size 0x1000]
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:17.5: BAR 13: failed to assign [io  size 0x1000]
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:17.4: BAR 13: no space for [io  size 0x1000]
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:17.4: BAR 13: failed to assign [io  size 0x1000]
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:17.3: BAR 13: no space for [io  size 0x1000]
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:17.3: BAR 13: failed to assign [io  size 0x1000]
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:16.7: BAR 13: no space for [io  size 0x1000]
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:16.7: BAR 13: failed to assign [io  size 0x1000]
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:16.6: BAR 13: no space for [io  size 0x1000]
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:16.6: BAR 13: failed to assign [io  size 0x1000]
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:16.5: BAR 13: no space for [io  size 0x1000]
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:16.5: BAR 13: failed to assign [io  size 0x1000]
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:16.4: BAR 13: no space for [io  size 0x1000]
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:16.4: BAR 13: failed to assign [io  size 0x1000]
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:16.3: BAR 13: no space for [io  size 0x1000]
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:16.3: BAR 13: failed to assign [io  size 0x1000]
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:15.7: BAR 13: no space for [io  size 0x1000]
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:15.7: BAR 13: failed to assign [io  size 0x1000]
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:15.6: BAR 13: no space for [io  size 0x1000]
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:15.6: BAR 13: failed to assign [io  size 0x1000]
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:15.5: BAR 13: no space for [io  size 0x1000]
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:15.5: BAR 13: failed to assign [io  size 0x1000]
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:15.4: BAR 13: no space for [io  size 0x1000]
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:15.4: BAR 13: failed to assign [io  size 0x1000]
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:15.3: BAR 13: no space for [io  size 0x1000]
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:15.3: BAR 13: failed to assign [io  size 0x1000]
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:01.0: PCI bridge to [bus 01]
Nov 24 16:35:28 PingBuild kernel: pci 0000:02:00.0: BAR 6: assigned [mem 0xd1010000-0xd101ffff pref]
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:11.0: PCI bridge to [bus 02]
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:11.0:   bridge window [io  0x2000-0x3fff]
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:11.0:   bridge window [mem 0xd1000000-0xd23fffff]
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:11.0:   bridge window [mem 0xdc400000-0xdc9fffff 64bit pref]
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:15.0: PCI bridge to [bus 03]
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:15.0:   bridge window [io  0x4000-0x4fff]
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:15.0:   bridge window [mem 0xd2400000-0xd24fffff]
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:15.0:   bridge window [mem 0xd4400000-0xd44fffff 64bit pref]
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:15.1: PCI bridge to [bus 04]
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:15.1:   bridge window [io  0x8000-0x8fff]
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:15.1:   bridge window [mem 0xd2800000-0xd28fffff]
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:15.1:   bridge window [mem 0xd4800000-0xd48fffff 64bit pref]
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:15.2: PCI bridge to [bus 05]
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:15.2:   bridge window [io  0xc000-0xcfff]
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:15.2:   bridge window [mem 0xd2c00000-0xd2cfffff]
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:15.2:   bridge window [mem 0xdcb00000-0xdcbfffff 64bit pref]
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:15.3: PCI bridge to [bus 06]
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:15.3:   bridge window [mem 0xd3000000-0xd30fffff]
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:15.3:   bridge window [mem 0xdcd00000-0xdcdfffff 64bit pref]
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:15.4: PCI bridge to [bus 07]
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:15.4:   bridge window [mem 0xd3400000-0xd34fffff]
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:15.4:   bridge window [mem 0xdcf00000-0xdcffffff 64bit pref]
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:15.5: PCI bridge to [bus 08]
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:15.5:   bridge window [mem 0xd3800000-0xd38fffff]
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:15.5:   bridge window [mem 0xdd100000-0xdd1fffff 64bit pref]
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:15.6: PCI bridge to [bus 09]
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:15.6:   bridge window [mem 0xd3c00000-0xd3cfffff]
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:15.6:   bridge window [mem 0xdd300000-0xdd3fffff 64bit pref]
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:15.7: PCI bridge to [bus 0a]
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:15.7:   bridge window [mem 0xd4000000-0xd40fffff]
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:15.7:   bridge window [mem 0xdd500000-0xdd5fffff 64bit pref]
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:16.0: PCI bridge to [bus 0b]
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:16.0:   bridge window [io  0x5000-0x5fff]
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:16.0:   bridge window [mem 0xd2500000-0xd25fffff]
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:16.0:   bridge window [mem 0xd4500000-0xd45fffff 64bit pref]
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:16.1: PCI bridge to [bus 0c]
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:16.1:   bridge window [io  0x9000-0x9fff]
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:16.1:   bridge window [mem 0xd2900000-0xd29fffff]
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:16.1:   bridge window [mem 0xd4900000-0xd49fffff 64bit pref]
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:16.2: PCI bridge to [bus 0d]
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:16.2:   bridge window [io  0xd000-0xdfff]
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:16.2:   bridge window [mem 0xd2d00000-0xd2dfffff]
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:16.2:   bridge window [mem 0xd4b00000-0xd4bfffff 64bit pref]
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:16.3: PCI bridge to [bus 0e]
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:16.3:   bridge window [mem 0xd3100000-0xd31fffff]
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:16.3:   bridge window [mem 0xd4d00000-0xd4dfffff 64bit pref]
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:16.4: PCI bridge to [bus 0f]
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:16.4:   bridge window [mem 0xd3500000-0xd35fffff]
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:16.4:   bridge window [mem 0xd4f00000-0xd4ffffff 64bit pref]
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:16.5: PCI bridge to [bus 10]
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:16.5:   bridge window [mem 0xd3900000-0xd39fffff]
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:16.5:   bridge window [mem 0xd5100000-0xd51fffff 64bit pref]
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:16.6: PCI bridge to [bus 11]
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:16.6:   bridge window [mem 0xd3d00000-0xd3dfffff]
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:16.6:   bridge window [mem 0xd5300000-0xd53fffff 64bit pref]
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:16.7: PCI bridge to [bus 12]
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:16.7:   bridge window [mem 0xd4100000-0xd41fffff]
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:16.7:   bridge window [mem 0xd5500000-0xd55fffff 64bit pref]
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:17.0: PCI bridge to [bus 13]
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:17.0:   bridge window [io  0x6000-0x6fff]
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:17.0:   bridge window [mem 0xd2600000-0xd26fffff]
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:17.0:   bridge window [mem 0xd4600000-0xd46fffff 64bit pref]
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:17.1: PCI bridge to [bus 14]
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:17.1:   bridge window [io  0xa000-0xafff]
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:17.1:   bridge window [mem 0xd2a00000-0xd2afffff]
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:17.1:   bridge window [mem 0xdca00000-0xdcafffff 64bit pref]
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:17.2: PCI bridge to [bus 15]
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:17.2:   bridge window [io  0xe000-0xefff]
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:17.2:   bridge window [mem 0xd2e00000-0xd2efffff]
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:17.2:   bridge window [mem 0xdcc00000-0xdccfffff 64bit pref]
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:17.3: PCI bridge to [bus 16]
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:17.3:   bridge window [mem 0xd3200000-0xd32fffff]
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:17.3:   bridge window [mem 0xdce00000-0xdcefffff 64bit pref]
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:17.4: PCI bridge to [bus 17]
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:17.4:   bridge window [mem 0xd3600000-0xd36fffff]
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:17.4:   bridge window [mem 0xdd000000-0xdd0fffff 64bit pref]
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:17.5: PCI bridge to [bus 18]
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:17.5:   bridge window [mem 0xd3a00000-0xd3afffff]
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:17.5:   bridge window [mem 0xdd200000-0xdd2fffff 64bit pref]
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:17.6: PCI bridge to [bus 19]
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:17.6:   bridge window [mem 0xd3e00000-0xd3efffff]
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:17.6:   bridge window [mem 0xdd400000-0xdd4fffff 64bit pref]
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:17.7: PCI bridge to [bus 1a]
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:17.7:   bridge window [mem 0xd4200000-0xd42fffff]
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:17.7:   bridge window [mem 0xdd600000-0xdd6fffff 64bit pref]
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:18.0: PCI bridge to [bus 1b]
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:18.0:   bridge window [io  0x7000-0x7fff]
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:18.0:   bridge window [mem 0xd2700000-0xd27fffff]
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:18.0:   bridge window [mem 0xd4700000-0xd47fffff 64bit pref]
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:18.1: PCI bridge to [bus 1c]
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:18.1:   bridge window [io  0xb000-0xbfff]
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:18.1:   bridge window [mem 0xd2b00000-0xd2bfffff]
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:18.1:   bridge window [mem 0xd4a00000-0xd4afffff 64bit pref]
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:18.2: PCI bridge to [bus 1d]
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:18.2:   bridge window [mem 0xd2f00000-0xd2ffffff]
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:18.2:   bridge window [mem 0xd4c00000-0xd4cfffff 64bit pref]
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:18.3: PCI bridge to [bus 1e]
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:18.3:   bridge window [mem 0xd3300000-0xd33fffff]
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:18.3:   bridge window [mem 0xd4e00000-0xd4efffff 64bit pref]
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:18.4: PCI bridge to [bus 1f]
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:18.4:   bridge window [mem 0xd3700000-0xd37fffff]
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:18.4:   bridge window [mem 0xd5000000-0xd50fffff 64bit pref]
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:18.5: PCI bridge to [bus 20]
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:18.5:   bridge window [mem 0xd3b00000-0xd3bfffff]
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:18.5:   bridge window [mem 0xd5200000-0xd52fffff 64bit pref]
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:18.6: PCI bridge to [bus 21]
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:18.6:   bridge window [mem 0xd3f00000-0xd3ffffff]
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:18.6:   bridge window [mem 0xd5400000-0xd54fffff 64bit pref]
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:18.7: PCI bridge to [bus 22]
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:18.7:   bridge window [mem 0xd4300000-0xd43fffff]
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:18.7:   bridge window [mem 0xd5600000-0xd56fffff 64bit pref]
Nov 24 16:35:28 PingBuild kernel: pci_bus 0000:00: resource 4 [mem 0x000a0000-0x000bffff]
Nov 24 16:35:28 PingBuild kernel: pci_bus 0000:00: resource 5 [mem 0x000cc000-0x000cffff]
Nov 24 16:35:28 PingBuild kernel: pci_bus 0000:00: resource 6 [mem 0x000d0000-0x000d3fff]
Nov 24 16:35:28 PingBuild kernel: pci_bus 0000:00: resource 7 [mem 0x000d4000-0x000d7fff]
Nov 24 16:35:28 PingBuild kernel: pci_bus 0000:00: resource 8 [mem 0x000d8000-0x000dbfff]
Nov 24 16:35:28 PingBuild kernel: pci_bus 0000:00: resource 9 [mem 0xc0000000-0xfebfffff]
Nov 24 16:35:28 PingBuild kernel: pci_bus 0000:00: resource 10 [io  0x0000-0x0cf7]
Nov 24 16:35:28 PingBuild kernel: pci_bus 0000:00: resource 11 [io  0x0d00-0xfeff]
Nov 24 16:35:28 PingBuild kernel: pci_bus 0000:02: resource 0 [io  0x2000-0x3fff]
Nov 24 16:35:28 PingBuild kernel: pci_bus 0000:02: resource 1 [mem 0xd1000000-0xd23fffff]
Nov 24 16:35:28 PingBuild kernel: pci_bus 0000:02: resource 2 [mem 0xdc400000-0xdc9fffff 64bit pref]
Nov 24 16:35:28 PingBuild kernel: pci_bus 0000:02: resource 4 [mem 0x000a0000-0x000bffff]
Nov 24 16:35:28 PingBuild kernel: pci_bus 0000:02: resource 5 [mem 0x000cc000-0x000cffff]
Nov 24 16:35:28 PingBuild kernel: pci_bus 0000:02: resource 6 [mem 0x000d0000-0x000d3fff]
Nov 24 16:35:28 PingBuild kernel: pci_bus 0000:02: resource 7 [mem 0x000d4000-0x000d7fff]
Nov 24 16:35:28 PingBuild kernel: pci_bus 0000:02: resource 8 [mem 0x000d8000-0x000dbfff]
Nov 24 16:35:28 PingBuild kernel: pci_bus 0000:02: resource 9 [mem 0xc0000000-0xfebfffff]
Nov 24 16:35:28 PingBuild kernel: pci_bus 0000:02: resource 10 [io  0x0000-0x0cf7]
Nov 24 16:35:28 PingBuild kernel: pci_bus 0000:02: resource 11 [io  0x0d00-0xfeff]
Nov 24 16:35:28 PingBuild kernel: pci_bus 0000:03: resource 0 [io  0x4000-0x4fff]
Nov 24 16:35:28 PingBuild kernel: pci_bus 0000:03: resource 1 [mem 0xd2400000-0xd24fffff]
Nov 24 16:35:28 PingBuild kernel: pci_bus 0000:03: resource 2 [mem 0xd4400000-0xd44fffff 64bit pref]
Nov 24 16:35:28 PingBuild kernel: pci_bus 0000:04: resource 0 [io  0x8000-0x8fff]
Nov 24 16:35:28 PingBuild kernel: pci_bus 0000:04: resource 1 [mem 0xd2800000-0xd28fffff]
Nov 24 16:35:28 PingBuild kernel: pci_bus 0000:04: resource 2 [mem 0xd4800000-0xd48fffff 64bit pref]
Nov 24 16:35:28 PingBuild kernel: pci_bus 0000:05: resource 0 [io  0xc000-0xcfff]
Nov 24 16:35:28 PingBuild kernel: pci_bus 0000:05: resource 1 [mem 0xd2c00000-0xd2cfffff]
Nov 24 16:35:28 PingBuild kernel: pci_bus 0000:05: resource 2 [mem 0xdcb00000-0xdcbfffff 64bit pref]
Nov 24 16:35:28 PingBuild kernel: pci_bus 0000:06: resource 1 [mem 0xd3000000-0xd30fffff]
Nov 24 16:35:28 PingBuild kernel: pci_bus 0000:06: resource 2 [mem 0xdcd00000-0xdcdfffff 64bit pref]
Nov 24 16:35:28 PingBuild kernel: pci_bus 0000:07: resource 1 [mem 0xd3400000-0xd34fffff]
Nov 24 16:35:28 PingBuild kernel: pci_bus 0000:07: resource 2 [mem 0xdcf00000-0xdcffffff 64bit pref]
Nov 24 16:35:28 PingBuild kernel: pci_bus 0000:08: resource 1 [mem 0xd3800000-0xd38fffff]
Nov 24 16:35:28 PingBuild kernel: pci_bus 0000:08: resource 2 [mem 0xdd100000-0xdd1fffff 64bit pref]
Nov 24 16:35:28 PingBuild kernel: pci_bus 0000:09: resource 1 [mem 0xd3c00000-0xd3cfffff]
Nov 24 16:35:28 PingBuild kernel: pci_bus 0000:09: resource 2 [mem 0xdd300000-0xdd3fffff 64bit pref]
Nov 24 16:35:28 PingBuild kernel: pci_bus 0000:0a: resource 1 [mem 0xd4000000-0xd40fffff]
Nov 24 16:35:28 PingBuild kernel: pci_bus 0000:0a: resource 2 [mem 0xdd500000-0xdd5fffff 64bit pref]
Nov 24 16:35:28 PingBuild kernel: pci_bus 0000:0b: resource 0 [io  0x5000-0x5fff]
Nov 24 16:35:28 PingBuild kernel: pci_bus 0000:0b: resource 1 [mem 0xd2500000-0xd25fffff]
Nov 24 16:35:28 PingBuild kernel: pci_bus 0000:0b: resource 2 [mem 0xd4500000-0xd45fffff 64bit pref]
Nov 24 16:35:28 PingBuild kernel: pci_bus 0000:0c: resource 0 [io  0x9000-0x9fff]
Nov 24 16:35:28 PingBuild kernel: pci_bus 0000:0c: resource 1 [mem 0xd2900000-0xd29fffff]
Nov 24 16:35:28 PingBuild kernel: pci_bus 0000:0c: resource 2 [mem 0xd4900000-0xd49fffff 64bit pref]
Nov 24 16:35:28 PingBuild kernel: pci_bus 0000:0d: resource 0 [io  0xd000-0xdfff]
Nov 24 16:35:28 PingBuild kernel: pci_bus 0000:0d: resource 1 [mem 0xd2d00000-0xd2dfffff]
Nov 24 16:35:28 PingBuild kernel: pci_bus 0000:0d: resource 2 [mem 0xd4b00000-0xd4bfffff 64bit pref]
Nov 24 16:35:28 PingBuild kernel: pci_bus 0000:0e: resource 1 [mem 0xd3100000-0xd31fffff]
Nov 24 16:35:28 PingBuild kernel: pci_bus 0000:0e: resource 2 [mem 0xd4d00000-0xd4dfffff 64bit pref]
Nov 24 16:35:28 PingBuild kernel: pci_bus 0000:0f: resource 1 [mem 0xd3500000-0xd35fffff]
Nov 24 16:35:28 PingBuild kernel: pci_bus 0000:0f: resource 2 [mem 0xd4f00000-0xd4ffffff 64bit pref]
Nov 24 16:35:28 PingBuild kernel: pci_bus 0000:10: resource 1 [mem 0xd3900000-0xd39fffff]
Nov 24 16:35:28 PingBuild kernel: pci_bus 0000:10: resource 2 [mem 0xd5100000-0xd51fffff 64bit pref]
Nov 24 16:35:28 PingBuild kernel: pci_bus 0000:11: resource 1 [mem 0xd3d00000-0xd3dfffff]
Nov 24 16:35:28 PingBuild kernel: pci_bus 0000:11: resource 2 [mem 0xd5300000-0xd53fffff 64bit pref]
Nov 24 16:35:28 PingBuild kernel: pci_bus 0000:12: resource 1 [mem 0xd4100000-0xd41fffff]
Nov 24 16:35:28 PingBuild kernel: pci_bus 0000:12: resource 2 [mem 0xd5500000-0xd55fffff 64bit pref]
Nov 24 16:35:28 PingBuild kernel: pci_bus 0000:13: resource 0 [io  0x6000-0x6fff]
Nov 24 16:35:28 PingBuild kernel: pci_bus 0000:13: resource 1 [mem 0xd2600000-0xd26fffff]
Nov 24 16:35:28 PingBuild kernel: pci_bus 0000:13: resource 2 [mem 0xd4600000-0xd46fffff 64bit pref]
Nov 24 16:35:28 PingBuild kernel: pci_bus 0000:14: resource 0 [io  0xa000-0xafff]
Nov 24 16:35:28 PingBuild kernel: pci_bus 0000:14: resource 1 [mem 0xd2a00000-0xd2afffff]
Nov 24 16:35:28 PingBuild kernel: pci_bus 0000:14: resource 2 [mem 0xdca00000-0xdcafffff 64bit pref]
Nov 24 16:35:28 PingBuild kernel: pci_bus 0000:15: resource 0 [io  0xe000-0xefff]
Nov 24 16:35:28 PingBuild kernel: pci_bus 0000:15: resource 1 [mem 0xd2e00000-0xd2efffff]
Nov 24 16:35:28 PingBuild kernel: pci_bus 0000:15: resource 2 [mem 0xdcc00000-0xdccfffff 64bit pref]
Nov 24 16:35:28 PingBuild kernel: pci_bus 0000:16: resource 1 [mem 0xd3200000-0xd32fffff]
Nov 24 16:35:28 PingBuild kernel: pci_bus 0000:16: resource 2 [mem 0xdce00000-0xdcefffff 64bit pref]
Nov 24 16:35:28 PingBuild kernel: pci_bus 0000:17: resource 1 [mem 0xd3600000-0xd36fffff]
Nov 24 16:35:28 PingBuild kernel: pci_bus 0000:17: resource 2 [mem 0xdd000000-0xdd0fffff 64bit pref]
Nov 24 16:35:28 PingBuild kernel: pci_bus 0000:18: resource 1 [mem 0xd3a00000-0xd3afffff]
Nov 24 16:35:28 PingBuild kernel: pci_bus 0000:18: resource 2 [mem 0xdd200000-0xdd2fffff 64bit pref]
Nov 24 16:35:28 PingBuild kernel: pci_bus 0000:19: resource 1 [mem 0xd3e00000-0xd3efffff]
Nov 24 16:35:28 PingBuild kernel: pci_bus 0000:19: resource 2 [mem 0xdd400000-0xdd4fffff 64bit pref]
Nov 24 16:35:28 PingBuild kernel: pci_bus 0000:1a: resource 1 [mem 0xd4200000-0xd42fffff]
Nov 24 16:35:28 PingBuild kernel: pci_bus 0000:1a: resource 2 [mem 0xdd600000-0xdd6fffff 64bit pref]
Nov 24 16:35:28 PingBuild kernel: pci_bus 0000:1b: resource 0 [io  0x7000-0x7fff]
Nov 24 16:35:28 PingBuild kernel: pci_bus 0000:1b: resource 1 [mem 0xd2700000-0xd27fffff]
Nov 24 16:35:28 PingBuild kernel: pci_bus 0000:1b: resource 2 [mem 0xd4700000-0xd47fffff 64bit pref]
Nov 24 16:35:28 PingBuild kernel: pci_bus 0000:1c: resource 0 [io  0xb000-0xbfff]
Nov 24 16:35:28 PingBuild kernel: pci_bus 0000:1c: resource 1 [mem 0xd2b00000-0xd2bfffff]
Nov 24 16:35:28 PingBuild kernel: pci_bus 0000:1c: resource 2 [mem 0xd4a00000-0xd4afffff 64bit pref]
Nov 24 16:35:28 PingBuild kernel: pci_bus 0000:1d: resource 1 [mem 0xd2f00000-0xd2ffffff]
Nov 24 16:35:28 PingBuild kernel: pci_bus 0000:1d: resource 2 [mem 0xd4c00000-0xd4cfffff 64bit pref]
Nov 24 16:35:28 PingBuild kernel: pci_bus 0000:1e: resource 1 [mem 0xd3300000-0xd33fffff]
Nov 24 16:35:28 PingBuild kernel: pci_bus 0000:1e: resource 2 [mem 0xd4e00000-0xd4efffff 64bit pref]
Nov 24 16:35:28 PingBuild kernel: pci_bus 0000:1f: resource 1 [mem 0xd3700000-0xd37fffff]
Nov 24 16:35:28 PingBuild kernel: pci_bus 0000:1f: resource 2 [mem 0xd5000000-0xd50fffff 64bit pref]
Nov 24 16:35:28 PingBuild kernel: pci_bus 0000:20: resource 1 [mem 0xd3b00000-0xd3bfffff]
Nov 24 16:35:28 PingBuild kernel: pci_bus 0000:20: resource 2 [mem 0xd5200000-0xd52fffff 64bit pref]
Nov 24 16:35:28 PingBuild kernel: pci_bus 0000:21: resource 1 [mem 0xd3f00000-0xd3ffffff]
Nov 24 16:35:28 PingBuild kernel: pci_bus 0000:21: resource 2 [mem 0xd5400000-0xd54fffff 64bit pref]
Nov 24 16:35:28 PingBuild kernel: pci_bus 0000:22: resource 1 [mem 0xd4300000-0xd43fffff]
Nov 24 16:35:28 PingBuild kernel: pci_bus 0000:22: resource 2 [mem 0xd5600000-0xd56fffff 64bit pref]
Nov 24 16:35:28 PingBuild kernel: NET: Registered protocol family 2
Nov 24 16:35:28 PingBuild kernel: TCP established hash table entries: 32768 (order: 6, 262144 bytes)
Nov 24 16:35:28 PingBuild kernel: TCP bind hash table entries: 32768 (order: 7, 524288 bytes)
Nov 24 16:35:28 PingBuild kernel: TCP: Hash tables configured (established 32768 bind 32768)
Nov 24 16:35:28 PingBuild kernel: TCP: reno registered
Nov 24 16:35:28 PingBuild kernel: UDP hash table entries: 2048 (order: 4, 65536 bytes)
Nov 24 16:35:28 PingBuild kernel: UDP-Lite hash table entries: 2048 (order: 4, 65536 bytes)
Nov 24 16:35:28 PingBuild kernel: NET: Registered protocol family 1
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:00.0: Limiting direct PCI/PCI transfers
Nov 24 16:35:28 PingBuild kernel: pci 0000:00:0f.0: Video device with shadowed ROM
Nov 24 16:35:28 PingBuild kernel: PCI: CLS mismatch (32 != 64), using 64 bytes
Nov 24 16:35:28 PingBuild kernel: Unpacking initramfs...
Nov 24 16:35:28 PingBuild kernel: Freeing initrd memory: 3148K (ffff8800379ca000 - ffff880037cdd000)
Nov 24 16:35:28 PingBuild kernel: PCI-DMA: Using software bounce buffering for IO (SWIOTLB)
Nov 24 16:35:28 PingBuild kernel: software IO TLB [mem 0xbbef0000-0xbfef0000] (64MB) mapped at [ffff8800bbef0000-ffff8800bfeeffff]
Nov 24 16:35:28 PingBuild kernel: Simple Boot Flag at 0x36 set to 0x80
Nov 24 16:35:28 PingBuild kernel: Switched to clocksource tsc
Nov 24 16:35:28 PingBuild kernel: microcode: CPU0 sig=0x106a4, pf=0x1, revision=0x9
Nov 24 16:35:28 PingBuild kernel: microcode: Microcode Update Driver: v2.00 <tigran@aivazian.fsnet.co.uk>, Peter Oruba
Nov 24 16:35:28 PingBuild kernel: Scanning for low memory corruption every 60 seconds
Nov 24 16:35:28 PingBuild kernel: futex hash table entries: 256 (order: 2, 16384 bytes)
Nov 24 16:35:28 PingBuild kernel: Initialise system trusted keyring
Nov 24 16:35:28 PingBuild kernel: HugeTLB registered 2 MB page size, pre-allocated 0 pages
Nov 24 16:35:28 PingBuild kernel: zpool: loaded
Nov 24 16:35:28 PingBuild kernel: zbud: loaded
Nov 24 16:35:28 PingBuild kernel: VFS: Disk quotas dquot_6.5.2
Nov 24 16:35:28 PingBuild kernel: Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
Nov 24 16:35:28 PingBuild kernel: msgmni has been set to 7910
Nov 24 16:35:28 PingBuild kernel: Key type big_key registered
Nov 24 16:35:28 PingBuild kernel: Block layer SCSI generic (bsg) driver version 0.4 loaded (major 252)
Nov 24 16:35:28 PingBuild kernel: io scheduler noop registered
Nov 24 16:35:28 PingBuild kernel: io scheduler deadline registered
Nov 24 16:35:28 PingBuild kernel: io scheduler cfq registered (default)
Nov 24 16:35:28 PingBuild kernel: pcieport 0000:00:15.0: irq 24 for MSI/MSI-X
Nov 24 16:35:28 PingBuild kernel: pcieport 0000:00:15.1: irq 25 for MSI/MSI-X
Nov 24 16:35:28 PingBuild kernel: pcieport 0000:00:15.2: irq 26 for MSI/MSI-X
Nov 24 16:35:28 PingBuild kernel: pcieport 0000:00:15.3: irq 27 for MSI/MSI-X
Nov 24 16:35:28 PingBuild kernel: pcieport 0000:00:15.4: irq 28 for MSI/MSI-X
Nov 24 16:35:28 PingBuild kernel: pcieport 0000:00:15.5: irq 29 for MSI/MSI-X
Nov 24 16:35:28 PingBuild kernel: pcieport 0000:00:15.6: irq 30 for MSI/MSI-X
Nov 24 16:35:28 PingBuild kernel: pcieport 0000:00:15.7: irq 31 for MSI/MSI-X
Nov 24 16:35:28 PingBuild kernel: pcieport 0000:00:16.0: irq 32 for MSI/MSI-X
Nov 24 16:35:28 PingBuild kernel: pcieport 0000:00:16.1: irq 33 for MSI/MSI-X
Nov 24 16:35:28 PingBuild kernel: pcieport 0000:00:16.2: irq 34 for MSI/MSI-X
Nov 24 16:35:28 PingBuild kernel: pcieport 0000:00:16.3: irq 35 for MSI/MSI-X
Nov 24 16:35:28 PingBuild kernel: pcieport 0000:00:16.4: irq 36 for MSI/MSI-X
Nov 24 16:35:28 PingBuild kernel: pcieport 0000:00:16.5: irq 37 for MSI/MSI-X
Nov 24 16:35:28 PingBuild kernel: pcieport 0000:00:16.6: irq 38 for MSI/MSI-X
Nov 24 16:35:28 PingBuild kernel: pcieport 0000:00:16.7: irq 39 for MSI/MSI-X
Nov 24 16:35:28 PingBuild kernel: pcieport 0000:00:17.0: irq 40 for MSI/MSI-X
Nov 24 16:35:28 PingBuild kernel: pcieport 0000:00:17.1: irq 41 for MSI/MSI-X
Nov 24 16:35:28 PingBuild kernel: pcieport 0000:00:17.2: irq 42 for MSI/MSI-X
Nov 24 16:35:28 PingBuild kernel: pcieport 0000:00:17.3: irq 43 for MSI/MSI-X
Nov 24 16:35:28 PingBuild kernel: pcieport 0000:00:17.4: irq 44 for MSI/MSI-X
Nov 24 16:35:28 PingBuild kernel: pcieport 0000:00:17.5: irq 45 for MSI/MSI-X
Nov 24 16:35:28 PingBuild kernel: pcieport 0000:00:17.6: irq 46 for MSI/MSI-X
Nov 24 16:35:28 PingBuild kernel: pcieport 0000:00:17.7: irq 47 for MSI/MSI-X
Nov 24 16:35:28 PingBuild kernel: pcieport 0000:00:18.0: irq 48 for MSI/MSI-X
Nov 24 16:35:28 PingBuild kernel: pcieport 0000:00:18.1: irq 49 for MSI/MSI-X
Nov 24 16:35:28 PingBuild kernel: pcieport 0000:00:18.2: irq 50 for MSI/MSI-X
Nov 24 16:35:28 PingBuild kernel: pcieport 0000:00:18.3: irq 51 for MSI/MSI-X
Nov 24 16:35:28 PingBuild kernel: pcieport 0000:00:18.4: irq 52 for MSI/MSI-X
Nov 24 16:35:28 PingBuild kernel: pcieport 0000:00:18.5: irq 53 for MSI/MSI-X
Nov 24 16:35:28 PingBuild kernel: pcieport 0000:00:18.6: irq 54 for MSI/MSI-X
Nov 24 16:35:28 PingBuild kernel: pcieport 0000:00:18.7: irq 55 for MSI/MSI-X
Nov 24 16:35:28 PingBuild kernel: pcieport 0000:00:15.0: Signaling PME through PCIe PME interrupt
Nov 24 16:35:28 PingBuild kernel: pcie_pme 0000:00:15.0:pcie01: service driver pcie_pme loaded
Nov 24 16:35:28 PingBuild kernel: pcieport 0000:00:15.1: Signaling PME through PCIe PME interrupt
Nov 24 16:35:28 PingBuild kernel: pcie_pme 0000:00:15.1:pcie01: service driver pcie_pme loaded
Nov 24 16:35:28 PingBuild kernel: pcieport 0000:00:15.2: Signaling PME through PCIe PME interrupt
Nov 24 16:35:28 PingBuild kernel: pcie_pme 0000:00:15.2:pcie01: service driver pcie_pme loaded
Nov 24 16:35:28 PingBuild kernel: pcieport 0000:00:15.3: Signaling PME through PCIe PME interrupt
Nov 24 16:35:28 PingBuild kernel: pcie_pme 0000:00:15.3:pcie01: service driver pcie_pme loaded
Nov 24 16:35:28 PingBuild kernel: pcieport 0000:00:15.4: Signaling PME through PCIe PME interrupt
Nov 24 16:35:28 PingBuild kernel: pcie_pme 0000:00:15.4:pcie01: service driver pcie_pme loaded
Nov 24 16:35:28 PingBuild kernel: pcieport 0000:00:15.5: Signaling PME through PCIe PME interrupt
Nov 24 16:35:28 PingBuild kernel: pcie_pme 0000:00:15.5:pcie01: service driver pcie_pme loaded
Nov 24 16:35:28 PingBuild kernel: pcieport 0000:00:15.6: Signaling PME through PCIe PME interrupt
Nov 24 16:35:28 PingBuild kernel: pcie_pme 0000:00:15.6:pcie01: service driver pcie_pme loaded
Nov 24 16:35:28 PingBuild kernel: pcieport 0000:00:15.7: Signaling PME through PCIe PME interrupt
Nov 24 16:35:28 PingBuild kernel: pcie_pme 0000:00:15.7:pcie01: service driver pcie_pme loaded
Nov 24 16:35:28 PingBuild kernel: pcieport 0000:00:16.0: Signaling PME through PCIe PME interrupt
Nov 24 16:35:28 PingBuild kernel: pcie_pme 0000:00:16.0:pcie01: service driver pcie_pme loaded
Nov 24 16:35:28 PingBuild kernel: pcieport 0000:00:16.1: Signaling PME through PCIe PME interrupt
Nov 24 16:35:28 PingBuild kernel: pcie_pme 0000:00:16.1:pcie01: service driver pcie_pme loaded
Nov 24 16:35:28 PingBuild kernel: pcieport 0000:00:16.2: Signaling PME through PCIe PME interrupt
Nov 24 16:35:28 PingBuild kernel: pcie_pme 0000:00:16.2:pcie01: service driver pcie_pme loaded
Nov 24 16:35:28 PingBuild kernel: pcieport 0000:00:16.3: Signaling PME through PCIe PME interrupt
Nov 24 16:35:28 PingBuild kernel: pcie_pme 0000:00:16.3:pcie01: service driver pcie_pme loaded
Nov 24 16:35:28 PingBuild kernel: pcieport 0000:00:16.4: Signaling PME through PCIe PME interrupt
Nov 24 16:35:28 PingBuild kernel: pcie_pme 0000:00:16.4:pcie01: service driver pcie_pme loaded
Nov 24 16:35:28 PingBuild kernel: pcieport 0000:00:16.5: Signaling PME through PCIe PME interrupt
Nov 24 16:35:28 PingBuild kernel: pcie_pme 0000:00:16.5:pcie01: service driver pcie_pme loaded
Nov 24 16:35:28 PingBuild kernel: pcieport 0000:00:16.6: Signaling PME through PCIe PME interrupt
Nov 24 16:35:28 PingBuild kernel: pcie_pme 0000:00:16.6:pcie01: service driver pcie_pme loaded
Nov 24 16:35:28 PingBuild kernel: pcieport 0000:00:16.7: Signaling PME through PCIe PME interrupt
Nov 24 16:35:28 PingBuild kernel: pcie_pme 0000:00:16.7:pcie01: service driver pcie_pme loaded
Nov 24 16:35:28 PingBuild kernel: pcieport 0000:00:17.0: Signaling PME through PCIe PME interrupt
Nov 24 16:35:28 PingBuild kernel: pcie_pme 0000:00:17.0:pcie01: service driver pcie_pme loaded
Nov 24 16:35:28 PingBuild kernel: pcieport 0000:00:17.1: Signaling PME through PCIe PME interrupt
Nov 24 16:35:28 PingBuild kernel: pcie_pme 0000:00:17.1:pcie01: service driver pcie_pme loaded
Nov 24 16:35:28 PingBuild kernel: pcieport 0000:00:17.2: Signaling PME through PCIe PME interrupt
Nov 24 16:35:28 PingBuild kernel: pcie_pme 0000:00:17.2:pcie01: service driver pcie_pme loaded
Nov 24 16:35:28 PingBuild kernel: pcieport 0000:00:17.3: Signaling PME through PCIe PME interrupt
Nov 24 16:35:28 PingBuild kernel: pcie_pme 0000:00:17.3:pcie01: service driver pcie_pme loaded
Nov 24 16:35:28 PingBuild kernel: pcieport 0000:00:17.4: Signaling PME through PCIe PME interrupt
Nov 24 16:35:28 PingBuild kernel: pcie_pme 0000:00:17.4:pcie01: service driver pcie_pme loaded
Nov 24 16:35:28 PingBuild kernel: pcieport 0000:00:17.5: Signaling PME through PCIe PME interrupt
Nov 24 16:35:28 PingBuild kernel: pcie_pme 0000:00:17.5:pcie01: service driver pcie_pme loaded
Nov 24 16:35:28 PingBuild kernel: pcieport 0000:00:17.6: Signaling PME through PCIe PME interrupt
Nov 24 16:35:28 PingBuild kernel: pcie_pme 0000:00:17.6:pcie01: service driver pcie_pme loaded
Nov 24 16:35:28 PingBuild kernel: pcieport 0000:00:17.7: Signaling PME through PCIe PME interrupt
Nov 24 16:35:28 PingBuild kernel: pcie_pme 0000:00:17.7:pcie01: service driver pcie_pme loaded
Nov 24 16:35:28 PingBuild kernel: pcieport 0000:00:18.0: Signaling PME through PCIe PME interrupt
Nov 24 16:35:28 PingBuild kernel: pcie_pme 0000:00:18.0:pcie01: service driver pcie_pme loaded
Nov 24 16:35:28 PingBuild kernel: pcieport 0000:00:18.1: Signaling PME through PCIe PME interrupt
Nov 24 16:35:28 PingBuild kernel: pcie_pme 0000:00:18.1:pcie01: service driver pcie_pme loaded
Nov 24 16:35:28 PingBuild kernel: pcieport 0000:00:18.2: Signaling PME through PCIe PME interrupt
Nov 24 16:35:28 PingBuild kernel: pcie_pme 0000:00:18.2:pcie01: service driver pcie_pme loaded
Nov 24 16:35:28 PingBuild kernel: pcieport 0000:00:18.3: Signaling PME through PCIe PME interrupt
Nov 24 16:35:28 PingBuild kernel: pcie_pme 0000:00:18.3:pcie01: service driver pcie_pme loaded
Nov 24 16:35:28 PingBuild kernel: pcieport 0000:00:18.4: Signaling PME through PCIe PME interrupt
Nov 24 16:35:28 PingBuild kernel: pcie_pme 0000:00:18.4:pcie01: service driver pcie_pme loaded
Nov 24 16:35:28 PingBuild kernel: pcieport 0000:00:18.5: Signaling PME through PCIe PME interrupt
Nov 24 16:35:28 PingBuild kernel: pcie_pme 0000:00:18.5:pcie01: service driver pcie_pme loaded
Nov 24 16:35:28 PingBuild kernel: pcieport 0000:00:18.6: Signaling PME through PCIe PME interrupt
Nov 24 16:35:28 PingBuild kernel: pcie_pme 0000:00:18.6:pcie01: service driver pcie_pme loaded
Nov 24 16:35:28 PingBuild kernel: pcieport 0000:00:18.7: Signaling PME through PCIe PME interrupt
Nov 24 16:35:28 PingBuild kernel: pcie_pme 0000:00:18.7:pcie01: service driver pcie_pme loaded
Nov 24 16:35:28 PingBuild kernel: pci_hotplug: PCI Hot Plug PCI Core version: 0.5
Nov 24 16:35:28 PingBuild kernel: pciehp 0000:00:15.0:pcie04: Slot #160 AttnBtn+ AttnInd- PwrInd- PwrCtrl+ MRL- Interlock- NoCompl+ LLActRep+
Nov 24 16:35:28 PingBuild kernel: pciehp 0000:00:15.0:pcie04: service driver pciehp loaded
Nov 24 16:35:28 PingBuild kernel: pciehp 0000:00:15.1:pcie04: Slot #161 AttnBtn+ AttnInd- PwrInd- PwrCtrl+ MRL- Interlock- NoCompl+ LLActRep+
Nov 24 16:35:28 PingBuild kernel: pciehp 0000:00:15.1:pcie04: service driver pciehp loaded
Nov 24 16:35:28 PingBuild kernel: pciehp 0000:00:15.2:pcie04: Slot #162 AttnBtn+ AttnInd- PwrInd- PwrCtrl+ MRL- Interlock- NoCompl+ LLActRep+
Nov 24 16:35:28 PingBuild kernel: pciehp 0000:00:15.2:pcie04: service driver pciehp loaded
Nov 24 16:35:28 PingBuild kernel: pciehp 0000:00:15.3:pcie04: Slot #163 AttnBtn+ AttnInd- PwrInd- PwrCtrl+ MRL- Interlock- NoCompl+ LLActRep+
Nov 24 16:35:28 PingBuild kernel: pciehp 0000:00:15.3:pcie04: service driver pciehp loaded
Nov 24 16:35:28 PingBuild kernel: pciehp 0000:00:15.4:pcie04: Slot #164 AttnBtn+ AttnInd- PwrInd- PwrCtrl+ MRL- Interlock- NoCompl+ LLActRep+
Nov 24 16:35:28 PingBuild kernel: pciehp 0000:00:15.4:pcie04: service driver pciehp loaded
Nov 24 16:35:28 PingBuild kernel: pciehp 0000:00:15.5:pcie04: Slot #165 AttnBtn+ AttnInd- PwrInd- PwrCtrl+ MRL- Interlock- NoCompl+ LLActRep+
Nov 24 16:35:28 PingBuild kernel: pciehp 0000:00:15.5:pcie04: service driver pciehp loaded
Nov 24 16:35:28 PingBuild kernel: pciehp 0000:00:15.6:pcie04: Slot #166 AttnBtn+ AttnInd- PwrInd- PwrCtrl+ MRL- Interlock- NoCompl+ LLActRep+
Nov 24 16:35:28 PingBuild kernel: pciehp 0000:00:15.6:pcie04: service driver pciehp loaded
Nov 24 16:35:28 PingBuild kernel: pciehp 0000:00:15.7:pcie04: Slot #167 AttnBtn+ AttnInd- PwrInd- PwrCtrl+ MRL- Interlock- NoCompl+ LLActRep+
Nov 24 16:35:28 PingBuild kernel: pciehp 0000:00:15.7:pcie04: service driver pciehp loaded
Nov 24 16:35:28 PingBuild kernel: pciehp 0000:00:16.0:pcie04: Slot #192 AttnBtn+ AttnInd- PwrInd- PwrCtrl+ MRL- Interlock- NoCompl+ LLActRep+
Nov 24 16:35:28 PingBuild kernel: pciehp 0000:00:16.0:pcie04: service driver pciehp loaded
Nov 24 16:35:28 PingBuild kernel: pciehp 0000:00:16.1:pcie04: Slot #193 AttnBtn+ AttnInd- PwrInd- PwrCtrl+ MRL- Interlock- NoCompl+ LLActRep+
Nov 24 16:35:28 PingBuild kernel: pciehp 0000:00:16.1:pcie04: service driver pciehp loaded
Nov 24 16:35:28 PingBuild kernel: pciehp 0000:00:16.2:pcie04: Slot #194 AttnBtn+ AttnInd- PwrInd- PwrCtrl+ MRL- Interlock- NoCompl+ LLActRep+
Nov 24 16:35:28 PingBuild kernel: pciehp 0000:00:16.2:pcie04: service driver pciehp loaded
Nov 24 16:35:28 PingBuild kernel: pciehp 0000:00:16.3:pcie04: Slot #195 AttnBtn+ AttnInd- PwrInd- PwrCtrl+ MRL- Interlock- NoCompl+ LLActRep+
Nov 24 16:35:28 PingBuild kernel: pciehp 0000:00:16.3:pcie04: service driver pciehp loaded
Nov 24 16:35:28 PingBuild kernel: pciehp 0000:00:16.4:pcie04: Slot #196 AttnBtn+ AttnInd- PwrInd- PwrCtrl+ MRL- Interlock- NoCompl+ LLActRep+
Nov 24 16:35:28 PingBuild kernel: pciehp 0000:00:16.4:pcie04: service driver pciehp loaded
Nov 24 16:35:28 PingBuild kernel: pciehp 0000:00:16.5:pcie04: Slot #197 AttnBtn+ AttnInd- PwrInd- PwrCtrl+ MRL- Interlock- NoCompl+ LLActRep+
Nov 24 16:35:28 PingBuild kernel: pciehp 0000:00:16.5:pcie04: service driver pciehp loaded
Nov 24 16:35:28 PingBuild kernel: pciehp 0000:00:16.6:pcie04: Slot #198 AttnBtn+ AttnInd- PwrInd- PwrCtrl+ MRL- Interlock- NoCompl+ LLActRep+
Nov 24 16:35:28 PingBuild kernel: pciehp 0000:00:16.6:pcie04: service driver pciehp loaded
Nov 24 16:35:28 PingBuild kernel: pciehp 0000:00:16.7:pcie04: Slot #199 AttnBtn+ AttnInd- PwrInd- PwrCtrl+ MRL- Interlock- NoCompl+ LLActRep+
Nov 24 16:35:28 PingBuild kernel: pciehp 0000:00:16.7:pcie04: service driver pciehp loaded
Nov 24 16:35:28 PingBuild kernel: pciehp 0000:00:17.0:pcie04: Slot #224 AttnBtn+ AttnInd- PwrInd- PwrCtrl+ MRL- Interlock- NoCompl+ LLActRep+
Nov 24 16:35:28 PingBuild kernel: pciehp 0000:00:17.0:pcie04: service driver pciehp loaded
Nov 24 16:35:28 PingBuild kernel: pciehp 0000:00:17.1:pcie04: Slot #225 AttnBtn+ AttnInd- PwrInd- PwrCtrl+ MRL- Interlock- NoCompl+ LLActRep+
Nov 24 16:35:28 PingBuild kernel: pciehp 0000:00:17.1:pcie04: service driver pciehp loaded
Nov 24 16:35:28 PingBuild kernel: pciehp 0000:00:17.2:pcie04: Slot #226 AttnBtn+ AttnInd- PwrInd- PwrCtrl+ MRL- Interlock- NoCompl+ LLActRep+
Nov 24 16:35:28 PingBuild kernel: pciehp 0000:00:17.2:pcie04: service driver pciehp loaded
Nov 24 16:35:28 PingBuild kernel: pciehp 0000:00:17.3:pcie04: Slot #227 AttnBtn+ AttnInd- PwrInd- PwrCtrl+ MRL- Interlock- NoCompl+ LLActRep+
Nov 24 16:35:28 PingBuild kernel: pciehp 0000:00:17.3:pcie04: service driver pciehp loaded
Nov 24 16:35:28 PingBuild kernel: pciehp 0000:00:17.4:pcie04: Slot #228 AttnBtn+ AttnInd- PwrInd- PwrCtrl+ MRL- Interlock- NoCompl+ LLActRep+
Nov 24 16:35:28 PingBuild kernel: pciehp 0000:00:17.4:pcie04: service driver pciehp loaded
Nov 24 16:35:28 PingBuild kernel: pciehp 0000:00:17.5:pcie04: Slot #229 AttnBtn+ AttnInd- PwrInd- PwrCtrl+ MRL- Interlock- NoCompl+ LLActRep+
Nov 24 16:35:28 PingBuild kernel: pciehp 0000:00:17.5:pcie04: service driver pciehp loaded
Nov 24 16:35:28 PingBuild kernel: pciehp 0000:00:17.6:pcie04: Slot #230 AttnBtn+ AttnInd- PwrInd- PwrCtrl+ MRL- Interlock- NoCompl+ LLActRep+
Nov 24 16:35:28 PingBuild kernel: pciehp 0000:00:17.6:pcie04: service driver pciehp loaded
Nov 24 16:35:28 PingBuild kernel: pciehp 0000:00:17.7:pcie04: Slot #231 AttnBtn+ AttnInd- PwrInd- PwrCtrl+ MRL- Interlock- NoCompl+ LLActRep+
Nov 24 16:35:28 PingBuild kernel: pciehp 0000:00:17.7:pcie04: service driver pciehp loaded
Nov 24 16:35:28 PingBuild kernel: pciehp 0000:00:18.0:pcie04: Slot #256 AttnBtn+ AttnInd- PwrInd- PwrCtrl+ MRL- Interlock- NoCompl+ LLActRep+
Nov 24 16:35:28 PingBuild kernel: pciehp 0000:00:18.0:pcie04: service driver pciehp loaded
Nov 24 16:35:28 PingBuild kernel: pciehp 0000:00:18.1:pcie04: Slot #257 AttnBtn+ AttnInd- PwrInd- PwrCtrl+ MRL- Interlock- NoCompl+ LLActRep+
Nov 24 16:35:28 PingBuild kernel: pciehp 0000:00:18.1:pcie04: service driver pciehp loaded
Nov 24 16:35:28 PingBuild kernel: pciehp 0000:00:18.2:pcie04: Slot #258 AttnBtn+ AttnInd- PwrInd- PwrCtrl+ MRL- Interlock- NoCompl+ LLActRep+
Nov 24 16:35:28 PingBuild kernel: pciehp 0000:00:18.2:pcie04: service driver pciehp loaded
Nov 24 16:35:28 PingBuild kernel: pciehp 0000:00:18.3:pcie04: Slot #259 AttnBtn+ AttnInd- PwrInd- PwrCtrl+ MRL- Interlock- NoCompl+ LLActRep+
Nov 24 16:35:28 PingBuild kernel: pciehp 0000:00:18.3:pcie04: service driver pciehp loaded
Nov 24 16:35:28 PingBuild kernel: pciehp 0000:00:18.4:pcie04: Slot #260 AttnBtn+ AttnInd- PwrInd- PwrCtrl+ MRL- Interlock- NoCompl+ LLActRep+
Nov 24 16:35:28 PingBuild kernel: pciehp 0000:00:18.4:pcie04: service driver pciehp loaded
Nov 24 16:35:28 PingBuild kernel: pciehp 0000:00:18.5:pcie04: Slot #261 AttnBtn+ AttnInd- PwrInd- PwrCtrl+ MRL- Interlock- NoCompl+ LLActRep+
Nov 24 16:35:28 PingBuild kernel: pciehp 0000:00:18.5:pcie04: service driver pciehp loaded
Nov 24 16:35:28 PingBuild kernel: pciehp 0000:00:18.6:pcie04: Slot #262 AttnBtn+ AttnInd- PwrInd- PwrCtrl+ MRL- Interlock- NoCompl+ LLActRep+
Nov 24 16:35:28 PingBuild kernel: pciehp 0000:00:18.6:pcie04: service driver pciehp loaded
Nov 24 16:35:28 PingBuild kernel: pciehp 0000:00:18.7:pcie04: Slot #263 AttnBtn+ AttnInd- PwrInd- PwrCtrl+ MRL- Interlock- NoCompl+ LLActRep+
Nov 24 16:35:28 PingBuild kernel: pciehp 0000:00:18.7:pcie04: service driver pciehp loaded
Nov 24 16:35:28 PingBuild kernel: pciehp: PCI Express Hot Plug Controller Driver version: 0.4
Nov 24 16:35:28 PingBuild kernel: vesafb: mode is 640x480x32, linelength=2560, pages=0
Nov 24 16:35:28 PingBuild kernel: vesafb: scrolling: redraw
Nov 24 16:35:28 PingBuild kernel: vesafb: Truecolor: size=8:8:8:8, shift=24:16:8:0
Nov 24 16:35:28 PingBuild kernel: vesafb: framebuffer at 0xd8000000, mapped to 0xffffc90010780000, using 1216k, total 1216k
Nov 24 16:35:28 PingBuild kernel: Console: switching to colour frame buffer device 80x30
Nov 24 16:35:28 PingBuild kernel: fb0: VESA VGA frame buffer device
Nov 24 16:35:28 PingBuild kernel: intel_idle: does not run on family 6 model 26
Nov 24 16:35:28 PingBuild kernel: GHES: HEST is not enabled!
Nov 24 16:35:28 PingBuild kernel: Serial: 8250/16550 driver, 4 ports, IRQ sharing disabled
Nov 24 16:35:28 PingBuild kernel: 00:06: ttyS0 at I/O 0x3f8 (irq = 4, base_baud = 115200) is a 16550A
Nov 24 16:35:28 PingBuild kernel: 00:07: ttyS1 at I/O 0x2f8 (irq = 3, base_baud = 115200) is a 16550A
Nov 24 16:35:28 PingBuild kernel: Linux agpgart interface v0.103
Nov 24 16:35:28 PingBuild kernel: rtc_cmos 00:01: rtc core: registered rtc_cmos as rtc0
Nov 24 16:35:28 PingBuild kernel: rtc_cmos 00:01: alarms up to one month, y3k, 114 bytes nvram, hpet irqs
Nov 24 16:35:28 PingBuild kernel: ledtrig-cpu: registered to indicate activity on CPUs
Nov 24 16:35:28 PingBuild kernel: TCP: cubic registered
Nov 24 16:35:28 PingBuild kernel: NET: Registered protocol family 10
Nov 24 16:35:28 PingBuild kernel: NET: Registered protocol family 17
Nov 24 16:35:28 PingBuild kernel: Loading compiled-in X.509 certificates
Nov 24 16:35:28 PingBuild kernel: registered taskstats version 1
Nov 24 16:35:28 PingBuild kernel:   Magic number: 6:200:604
Nov 24 16:35:28 PingBuild kernel: rtc_cmos 00:01: setting system clock to 2014-11-24 22:35:23 UTC (1416868523)
Nov 24 16:35:28 PingBuild kernel: PM: Hibernation image not present or could not be loaded.
Nov 24 16:35:28 PingBuild kernel: Freeing unused kernel memory: 1140K (ffffffff818e2000 - ffffffff819ff000)
Nov 24 16:35:28 PingBuild kernel: Write protecting the kernel read-only data: 8192k
Nov 24 16:35:28 PingBuild kernel: Freeing unused kernel memory: 748K (ffff880001545000 - ffff880001600000)
Nov 24 16:35:28 PingBuild kernel: Freeing unused kernel memory: 336K (ffff8800017ac000 - ffff880001800000)
Nov 24 16:35:28 PingBuild kernel: random: systemd-tmpfile urandom read with 2 bits of entropy available
Nov 24 16:35:28 PingBuild kernel: i8042: PNP: PS/2 Controller [PNP0303:KBC,PNP0f13:MOUS] at 0x60,0x64 irq 1,12
Nov 24 16:35:28 PingBuild kernel: serio: i8042 KBD port at 0x60,0x64 irq 1
Nov 24 16:35:28 PingBuild kernel: serio: i8042 AUX port at 0x60,0x64 irq 12
Nov 24 16:35:28 PingBuild kernel: Floppy drive(s): fd0 is 1.44M
Nov 24 16:35:28 PingBuild kernel: FDC 0 is a post-1991 82077
Nov 24 16:35:28 PingBuild kernel: input: AT Translated Set 2 keyboard as /devices/platform/i8042/serio0/input/input0
Nov 24 16:35:28 PingBuild kernel: Fusion MPT base driver 3.04.20
Nov 24 16:35:28 PingBuild kernel: Copyright (c) 1999-2008 LSI Corporation
Nov 24 16:35:28 PingBuild kernel: SCSI subsystem initialized
Nov 24 16:35:28 PingBuild kernel: Fusion MPT SPI Host driver 3.04.20
Nov 24 16:35:28 PingBuild kernel: mptbase: ioc0: Initiating bringup
Nov 24 16:35:28 PingBuild kernel: libata version 3.00 loaded.
Nov 24 16:35:28 PingBuild kernel: ioc0: LSI53C1030 B0: Capabilities={Initiator}
Nov 24 16:35:28 PingBuild kernel: scsi host0: ioc0: LSI53C1030 B0, FwRev=01032920h, Ports=1, MaxQ=128, IRQ=17
Nov 24 16:35:28 PingBuild kernel: scsi 0:0:0:0: Direct-Access     VMware   Virtual disk     1.0  PQ: 0 ANSI: 2
Nov 24 16:35:28 PingBuild kernel: scsi target0:0:0: Beginning Domain Validation
Nov 24 16:35:28 PingBuild kernel: scsi target0:0:0: Domain Validation skipping write tests
Nov 24 16:35:28 PingBuild kernel: scsi target0:0:0: Ending Domain Validation
Nov 24 16:35:28 PingBuild kernel: scsi target0:0:0: FAST-40 WIDE SCSI 80.0 MB/s ST (25 ns, offset 127)
Nov 24 16:35:28 PingBuild kernel: ata_piix 0000:00:07.1: version 2.13
Nov 24 16:35:28 PingBuild kernel: scsi host1: ata_piix
Nov 24 16:35:28 PingBuild kernel: scsi host2: ata_piix
Nov 24 16:35:28 PingBuild kernel: ata1: PATA max UDMA/33 cmd 0x1f0 ctl 0x3f6 bmdma 0x10c0 irq 14
Nov 24 16:35:28 PingBuild kernel: ata2: PATA max UDMA/33 cmd 0x170 ctl 0x376 bmdma 0x10c8 irq 15
Nov 24 16:35:28 PingBuild kernel: sd 0:0:0:0: [sda] 209715200 512-byte logical blocks: (107 GB/100 GiB)
Nov 24 16:35:28 PingBuild kernel: sd 0:0:0:0: [sda] Write Protect is off
Nov 24 16:35:28 PingBuild kernel: sd 0:0:0:0: [sda] Mode Sense: 61 00 00 00
Nov 24 16:35:28 PingBuild kernel: sd 0:0:0:0: [sda] Cache data unavailable
Nov 24 16:35:28 PingBuild kernel: sd 0:0:0:0: [sda] Assuming drive cache: write through
Nov 24 16:35:28 PingBuild kernel:  sda: sda1 sda2 sda3 sda4
Nov 24 16:35:28 PingBuild kernel: sd 0:0:0:0: [sda] Attached SCSI disk
Nov 24 16:35:28 PingBuild kernel: ata2.00: ATAPI: VMware Virtual IDE CDROM Drive, 00000001, max UDMA/33
Nov 24 16:35:28 PingBuild kernel: ata2.00: configured for UDMA/33
Nov 24 16:35:28 PingBuild kernel: scsi 2:0:0:0: CD-ROM            NECVMWar VMware IDE CDR10 1.00 PQ: 0 ANSI: 5
Nov 24 16:35:28 PingBuild kernel: sr 2:0:0:0: [sr0] scsi3-mmc drive: 1x/1x writer dvd-ram cd/rw xa/form2 cdda tray
Nov 24 16:35:28 PingBuild kernel: cdrom: Uniform CD-ROM driver Revision: 3.20
Nov 24 16:35:28 PingBuild kernel: sr 2:0:0:0: Attached scsi CD-ROM sr0
Nov 24 16:35:28 PingBuild kernel: EXT4-fs (sda2): mounted filesystem with ordered data mode. Opts: (null)
Nov 24 16:35:28 PingBuild kernel: random: nonblocking pool is initialized
Nov 24 16:35:28 PingBuild systemd[1]: Cannot add dependency job for unit display-manager.service, ignoring: Unit display-manager.service failed to load: No such file or directory.
Nov 24 16:35:28 PingBuild kernel: EXT4-fs (sda2): re-mounted. Opts: data=ordered
Nov 24 16:35:28 PingBuild kernel: input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input2
Nov 24 16:35:28 PingBuild kernel: ACPI: Power Button [PWRF]
Nov 24 16:35:28 PingBuild kernel: ACPI: AC Adapter [ACAD] (on-line)
Nov 24 16:35:28 PingBuild kernel: parport_pc 00:05: reported by Plug and Play ACPI
Nov 24 16:35:28 PingBuild kernel: parport0: PC-style at 0x378, irq 7 [PCSPP,TRISTATE]
Nov 24 16:35:28 PingBuild kernel: NET: Registered protocol family 23
Nov 24 16:35:28 PingBuild kernel: nsc-ircc, Found chip at base=0x02e
Nov 24 16:35:28 PingBuild kernel: nsc-ircc, Wrong chip version 00
Nov 24 16:35:28 PingBuild kernel: agpgart-intel 0000:00:00.0: Intel 440BX Chipset
Nov 24 16:35:28 PingBuild kernel: agpgart-intel 0000:00:00.0: AGP aperture is 256M @ 0x0
Nov 24 16:35:28 PingBuild kernel: vmw_vmci 0000:00:07.7: Found VMCI PCI device at 0x11080, irq 16
Nov 24 16:35:28 PingBuild kernel: vmw_vmci 0000:00:07.7: Using capabilities 0xc
Nov 24 16:35:28 PingBuild kernel: vmw_vmci 0000:00:07.7: irq 56 for MSI/MSI-X
Nov 24 16:35:28 PingBuild kernel: vmw_vmci 0000:00:07.7: irq 57 for MSI/MSI-X
Nov 24 16:35:28 PingBuild kernel: Guest personality initialized and is active
Nov 24 16:35:28 PingBuild kernel: VMCI host device registered (name=vmci, major=10, minor=59)
Nov 24 16:35:28 PingBuild kernel: Initialized host personality
Nov 24 16:35:28 PingBuild kernel: shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
Nov 24 16:35:28 PingBuild kernel: piix4_smbus 0000:00:07.3: SMBus Host Controller not enabled!
Nov 24 16:35:28 PingBuild kernel: [drm] Initialized drm 1.1.0 20060810
Nov 24 16:35:28 PingBuild kernel: [drm] DMA map mode: Using physical TTM page addresses.
Nov 24 16:35:28 PingBuild kernel: [drm] Capabilities:
Nov 24 16:35:28 PingBuild kernel: [drm]   Rect copy.
Nov 24 16:35:28 PingBuild kernel: [drm]   Cursor.
Nov 24 16:35:28 PingBuild kernel: [drm]   Cursor bypass.
Nov 24 16:35:28 PingBuild kernel: [drm]   Cursor bypass 2.
Nov 24 16:35:28 PingBuild kernel: [drm]   8bit emulation.
Nov 24 16:35:28 PingBuild kernel: [drm]   Alpha cursor.
Nov 24 16:35:28 PingBuild kernel: [drm]   3D.
Nov 24 16:35:28 PingBuild kernel: [drm]   Extended Fifo.
Nov 24 16:35:28 PingBuild kernel: [drm]   Multimon.
Nov 24 16:35:28 PingBuild kernel: [drm]   Pitchlock.
Nov 24 16:35:28 PingBuild kernel: [drm]   Irq mask.
Nov 24 16:35:28 PingBuild kernel: [drm]   Display Topology.
Nov 24 16:35:28 PingBuild kernel: [drm]   GMR.
Nov 24 16:35:28 PingBuild kernel: [drm]   Traces.
Nov 24 16:35:28 PingBuild kernel: [drm]   GMR2.
Nov 24 16:35:28 PingBuild kernel: [drm]   Screen Object 2.
Nov 24 16:35:28 PingBuild kernel: [drm] Max GMR ids is 64
Nov 24 16:35:28 PingBuild kernel: [drm] Max number of GMR pages is 65536
Nov 24 16:35:28 PingBuild kernel: [drm] Max dedicated hypervisor surface memory is 163840 kiB
Nov 24 16:35:28 PingBuild kernel: [drm] Maximum display memory size is 32768 kiB
Nov 24 16:35:28 PingBuild kernel: [drm] VRAM at 0xd8000000 size is 32768 kiB
Nov 24 16:35:28 PingBuild kernel: [drm] MMIO at 0xd0800000 size is 516 kiB
Nov 24 16:35:28 PingBuild kernel: [drm] global init.
Nov 24 16:35:28 PingBuild kernel: [TTM] Zone  kernel: Available graphics memory: 2026280 kiB
Nov 24 16:35:28 PingBuild kernel: [TTM] Initializing pool allocator
Nov 24 16:35:28 PingBuild kernel: [TTM] Initializing DMA pool allocator
Nov 24 16:35:28 PingBuild kernel: vmwgfx 0000:00:0f.0: BAR 1: can't reserve [mem 0xd8000000-0xdbffffff pref]
Nov 24 16:35:28 PingBuild kernel: [drm] It appears like vesafb is loaded. Ignore above error if any.
Nov 24 16:35:28 PingBuild kernel: [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
Nov 24 16:35:28 PingBuild kernel: [drm] No driver support for vblank timestamp query.
Nov 24 16:35:28 PingBuild kernel: [drm] Screen objects system initialized
Nov 24 16:35:28 PingBuild kernel: [drm] width 640
Nov 24 16:35:28 PingBuild kernel: [drm] height 480
Nov 24 16:35:28 PingBuild kernel: [drm] bpp 32
Nov 24 16:35:28 PingBuild kernel: [drm] Fifo max 0x00081000 min 0x00001000 cap 0x0000077f
Nov 24 16:35:28 PingBuild kernel: checking generic (d8000000 130000) vs hw (d8000000 2000000)
Nov 24 16:35:28 PingBuild kernel: fb: switching to svgadrmfb from VESA VGA
Nov 24 16:35:28 PingBuild kernel: Console: switching to colour dummy device 80x25
Nov 24 16:35:28 PingBuild kernel: fbcon: svgadrmfb (fb0) is primary device
Nov 24 16:35:28 PingBuild kernel: Console: switching to colour frame buffer device 100x37
Nov 24 16:35:28 PingBuild kernel: [drm] Initialized vmwgfx 2.6.1 20140704 for 0000:00:0f.0 on minor 0
Nov 24 16:35:28 PingBuild kernel: e1000: Intel(R) PRO/1000 Network Driver - version 7.3.21-k8-NAPI
Nov 24 16:35:28 PingBuild kernel: e1000: Copyright (c) 1999-2006 Intel Corporation.
Nov 24 16:35:28 PingBuild kernel: input: PC Speaker as /devices/platform/pcspkr/input/input4
Nov 24 16:35:28 PingBuild kernel: ppdev: user-space parallel port driver
Nov 24 16:35:28 PingBuild kernel: e1000 0000:02:00.0 eth0: (PCI:66MHz:32-bit) 00:50:56:97:0d:a3
Nov 24 16:35:28 PingBuild kernel: e1000 0000:02:00.0 eth0: Intel(R) PRO/1000 Network Connection
Nov 24 16:35:28 PingBuild kernel: e1000 0000:02:00.0 ens32: renamed from eth0
Nov 24 16:35:28 PingBuild kernel: input: ImPS/2 Generic Wheel Mouse as /devices/platform/i8042/serio1/input/input3
Nov 24 16:35:28 PingBuild kernel: mousedev: PS/2 mouse device common for all mice
Nov 24 16:35:28 PingBuild kernel: EXT4-fs (sda4): mounted filesystem with ordered data mode. Opts: data=ordered
Nov 24 16:35:28 PingBuild systemd-journal[109]: Journal started
-- Subject: The Journal has been started
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- The system journal process has been starting up, opened the journal
-- files for writing and is now ready to process requests.
Nov 24 16:35:26 PingBuild systemd-udevd[127]: starting version 217
Nov 24 16:35:28 PingBuild systemd-fsck[144]: /dev/sda4: clean, 16106/4915200 files, 372421/19660800 blocks
Nov 24 16:35:29 PingBuild start[161]: Starting Webmin server in /opt/webmin
Nov 24 16:35:30 PingBuild webmin[161]: Webmin starting
Nov 24 16:35:30 PingBuild systemd-logind[163]: New seat seat0.
-- Subject: A new seat seat0 is now available
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- Documentation: http://www.freedesktop.org/wiki/Software/systemd/multiseat
-- 
-- A new seat seat0 has been configured and is now available.
Nov 24 16:35:30 PingBuild systemd-logind[163]: Watching system buttons on /dev/input/event1 (Power Button)
Nov 24 16:35:31 PingBuild start[161]: Pre-loaded WebminCore
Nov 24 16:35:40 PingBuild login[171]: pam_unix(login:session): session opened for user root by LOGIN(uid=0)
Nov 24 16:35:40 PingBuild systemd-logind[163]: New session c1 of user root.
-- Subject: A new session c1 has been created for user root
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- Documentation: http://www.freedesktop.org/wiki/Software/systemd/multiseat
-- 
-- A new session with the ID c1 has been created for the user root.
-- 
-- The leading process of the session is 171.
Nov 24 16:35:40 PingBuild systemd[195]: pam_unix(systemd-user:session): session opened for user root by (uid=0)
Nov 24 16:35:41 PingBuild systemd[195]: Starting Paths.
-- Subject: Unit UNIT has begun with start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- Unit UNIT has begun starting up.
Nov 24 16:35:41 PingBuild systemd[195]: Reached target Paths.
-- Subject: Unit UNIT has finished start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- Unit UNIT has finished starting up.
-- 
-- The start-up result is done.
Nov 24 16:35:41 PingBuild systemd[195]: Starting Timers.
-- Subject: Unit UNIT has begun with start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- Unit UNIT has begun starting up.
Nov 24 16:35:41 PingBuild systemd[195]: Reached target Timers.
-- Subject: Unit UNIT has finished start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- Unit UNIT has finished starting up.
-- 
-- The start-up result is done.
Nov 24 16:35:41 PingBuild systemd[195]: Starting Sockets.
-- Subject: Unit UNIT has begun with start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- Unit UNIT has begun starting up.
Nov 24 16:35:41 PingBuild systemd[195]: Reached target Sockets.
-- Subject: Unit UNIT has finished start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- Unit UNIT has finished starting up.
-- 
-- The start-up result is done.
Nov 24 16:35:41 PingBuild systemd[195]: Starting Basic System.
-- Subject: Unit UNIT has begun with start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- Unit UNIT has begun starting up.
Nov 24 16:35:41 PingBuild systemd[195]: Reached target Basic System.
-- Subject: Unit UNIT has finished start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- Unit UNIT has finished starting up.
-- 
-- The start-up result is done.
Nov 24 16:35:41 PingBuild systemd[195]: Starting Default.
-- Subject: Unit UNIT has begun with start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- Unit UNIT has begun starting up.
Nov 24 16:35:41 PingBuild systemd[195]: Reached target Default.
-- Subject: Unit UNIT has finished start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- Unit UNIT has finished starting up.
-- 
-- The start-up result is done.
Nov 24 16:35:41 PingBuild systemd[195]: Startup finished in 44ms.
-- Subject: System start-up is now complete
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- All system services necessary queued for starting at boot have been
-- successfully started. Note that this does not mean that the machine is
-- now idle as services might still be busy with completing start-up.
-- 
-- Kernel start-up required KERNEL_USEC microseconds.
-- 
-- Initial RAM disk start-up required INITRD_USEC microseconds.
-- 
-- Userspace start-up required 44790 microseconds.
Nov 24 16:35:41 PingBuild login[171]: ROOT LOGIN ON tty1
Nov 24 16:36:55 PingBuild systemd[1]: Job sys-subsystem-net-devices-_ens32.device/start timed out.
Nov 24 16:36:55 PingBuild systemd[1]: Timed out waiting for device sys-subsystem-net-devices-_ens32.device.
-- Subject: Unit sys-subsystem-net-devices-_ens32.device has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- Unit sys-subsystem-net-devices-_ens32.device has failed.
-- 
-- The result is timeout.
Nov 24 16:36:55 PingBuild systemd[1]: Dependency failed for dhcpcd on _ens32.
-- Subject: Unit dhcpcd@_ens32.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- Unit dhcpcd@_ens32.service has failed.
-- 
-- The result is dependency.
Nov 24 16:36:56 PingBuild nmbd[212]: [2014/11/24 16:36:56.643375,  0] ../lib/util/become_daemon.c:147(daemon_status)
Nov 24 16:36:56 PingBuild nmbd[212]: STATUS=daemon 'nmbd' : No local IPv4 non-loopback interfaces available, waiting for interface ...NOTE: NetBIOS name resolution is not supported for Internet Protocol Version 6 (IPv6).
Nov 24 16:36:57 PingBuild smbd[214]: [2014/11/24 16:36:57.071990,  0] ../lib/util/become_daemon.c:136(daemon_ready)
Nov 24 16:36:57 PingBuild dbus[164]: [system] Activating via systemd: service name='org.freedesktop.Avahi' unit='dbus-org.freedesktop.Avahi.service'
Nov 24 16:36:57 PingBuild smbd[215]: STATUS=daemon 'smbd' finished starting up and ready to serve connectionsUnable to open printcap file /etc/printcap for read!
Nov 24 16:36:57 PingBuild avahi-daemon[216]: Found user 'avahi' (UID 84) and group 'avahi' (GID 84).
Nov 24 16:36:57 PingBuild avahi-daemon[216]: Successfully dropped root privileges.
Nov 24 16:36:57 PingBuild avahi-daemon[216]: avahi-daemon 0.6.31 starting up.
Nov 24 16:36:57 PingBuild avahi-daemon[216]: WARNING: No NSS support for mDNS detected, consider installing nss-mdns!
Nov 24 16:36:57 PingBuild dbus[164]: [system] Successfully activated service 'org.freedesktop.Avahi'
Nov 24 16:36:57 PingBuild avahi-daemon[216]: Successfully called chroot().
Nov 24 16:36:57 PingBuild avahi-daemon[216]: Successfully dropped remaining capabilities.
Nov 24 16:36:57 PingBuild avahi-daemon[216]: Loading service file /services/sftp-ssh.service.
Nov 24 16:36:57 PingBuild avahi-daemon[216]: Loading service file /services/ssh.service.
Nov 24 16:36:57 PingBuild avahi-daemon[216]: Network interface enumeration completed.
Nov 24 16:36:57 PingBuild avahi-daemon[216]: Registering HINFO record with values 'X86_64'/'LINUX'.
Nov 24 16:36:57 PingBuild avahi-daemon[216]: Server startup complete. Host name is PingBuild.local. Local service cookie is 678374054.
Nov 24 16:36:57 PingBuild avahi-daemon[216]: Service "PingBuild" (/services/ssh.service) successfully established.
Nov 24 16:36:57 PingBuild avahi-daemon[216]: Service "PingBuild" (/services/sftp-ssh.service) successfully established.
Nov 24 16:38:02 PingBuild net-up.sh[221]: Start of /usr/local/bin/net-up.sh
Nov 24 16:38:02 PingBuild kernel: e1000: ens32 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: None
Nov 24 16:38:02 PingBuild avahi-daemon[216]: Joining mDNS multicast group on interface ens32.IPv4 with address 192.168.60.120.
Nov 24 16:38:02 PingBuild avahi-daemon[216]: New relevant interface ens32.IPv4 for mDNS.
Nov 24 16:38:02 PingBuild avahi-daemon[216]: Registering new address record for 192.168.60.120 on ens32.IPv4.
Nov 24 16:38:03 PingBuild avahi-daemon[216]: Registering new address record for fe80::250:56ff:fe97:da3 on ens32.*.
Nov 24 16:38:06 PingBuild nmbd[212]: [2014/11/24 16:38:06.677020,  0] ../lib/util/become_daemon.c:136(daemon_ready)
Nov 24 16:38:28 PingBuild nmbd[212]: STATUS=daemon 'nmbd' finished starting up and ready to serve connections*****
Nov 24 16:38:28 PingBuild nmbd[212]: 
Nov 24 16:38:28 PingBuild nmbd[212]: Samba name server PINGBUILD is now a local master browser for workgroup MYGROUP on subnet 192.168.60.120
Nov 24 16:38:28 PingBuild nmbd[212]: 
Nov 24 16:38:28 PingBuild nmbd[212]: *****
Nov 24 16:47:57 PingBuild smbd[215]: [2014/11/24 16:47:57.694439,  0] ../source3/printing/print_standard.c:69(std_pcap_cache_reload)
Nov 24 16:47:57 PingBuild smbd[215]: Unable to open printcap file /etc/printcap for read!

Offline

#11 2014-11-24 23:14:07

TheSaint
Member
From: my computer
Registered: 2007-08-19
Posts: 1,523

Re: [SLOVED] .rule required for udev to start an enabled network@.service?

At the end of journal it seems that the network is up and linked. Why you're unsatisfied ?
Your script usr/local/bin/net-up.sh, works. Or is that what you don't want ?


do it good first, it will be faster than do it twice the saint wink

Offline

#12 2014-11-24 23:24:51

penright14
Member
Registered: 2014-11-20
Posts: 35

Re: [SLOVED] .rule required for udev to start an enabled network@.service?

TheSaint wrote:

Why you're unsatisfied ?

I thought it would start on its own, the reason it is running is because I started it by hand. Should the service start by udev?

Offline

#13 2014-11-24 23:27:55

jasonwryan
Anarchist
From: .nz
Registered: 2009-05-09
Posts: 30,424
Website

Re: [SLOVED] .rule required for udev to start an enabled network@.service?

No, systemd is responsible for the service.

You can use a udev rule to rename the interface...


Arch + dwm   •   Mercurial repos  •   Surfraw

Registered Linux User #482438

Offline

#14 2014-11-24 23:54:44

TheSaint
Member
From: my computer
Registered: 2007-08-19
Posts: 1,523

Re: [SLOVED] .rule required for udev to start an enabled network@.service?

I never seen udev starting a service. It's rather the other way round that systemd starts udevd.
The point allows to wait for udev to define a device name and then systemd is able to start the service. If you want to play around this, then is a chance. Otherwise you should do more research how to write a service. Like here
Even you can try to add

RestartSec=1min
Restart=on-failure

to your service. See this as reference.
One more note, better you write your service in /etc/systemd/system/ which has precedence over /usr/lib/systemd/system/ and it isn't overwrite by the updates.

Last edited by TheSaint (2014-11-25 00:00:37)


do it good first, it will be faster than do it twice the saint wink

Offline

#15 2014-11-25 12:04:24

penright14
Member
Registered: 2014-11-20
Posts: 35

Re: [SLOVED] .rule required for udev to start an enabled network@.service?

Ok, lot to digest, let me see if I can get my arms around this....

TheSaint wrote:

I suspect that in several case the cause is dhcpcd starts too early.
In case of fixed IP, it'd works and in such circumstance it'll confirm my theory.
Connections manager provide a second chance to connect dynamic IP.

Not sure if I follow. Are you saying to test something, try dhcpcd?

jasonwryan wrote:

No, systemd is responsible for the service.
You can use a udev rule to rename the interface...

TheSaint wrote:

I never seen udev starting a service. It's rather the other way round that systemd starts udevd.
The point allows to wait for udev to define a device name and then systemd is able to start the service. If you want to play around this, then is a chance. Otherwise you should do more research how to write a service. Like here
Even you can try to add

RestartSec=1min
Restart=on-failure

to your service. See this as reference.
One more note, better you write your service in /etc/systemd/system/ which has precedence over /usr/lib/systemd/system/ and it isn't overwrite by the updates.

I hear you guys and I think I understand. I may have asked my original question wrong out of ignorance. The bottom line is setting static IP. I used the network wiki https://wiki.archlinux.org/index.php/Ne … figuration and just tried to follow the directions. Typo and lessons learned that can be seen in my other threads, I finally got the unit, shell scripts, and .conf files right, that if I systemctl start network@ens32.service I could get an IP connection going. Now I am down to two issues. One is the startx on a different thread and two is I expect the IP to be up after a reboot. For now the only way I can get an IP connection is manually running the service after logging on. So when the "automatic" starting of the service did not work, then I was trying to understand the difference between my system and the wiki. I started with a udev rule to rename ens32 to net0, but then I thought that is all the purpose of the rule was, so I deleted it. Since the "automatic" is not working, I was wondering if the udev rule was what trips the systemd into starting a service, hence the title of my post. Maybe a bad choice of words and if either of you think it would make the questions clearer, I can edit it.

I guess the bottom line question is can a static IP connection be brought up from boot without any user intervention?

I believe if I get the "automatic" start working then I will understand systemd better. I was by far not an expert on System-V start up, but I did have a few years of hacking around on it, I have only a few days of systemd and udev. That tells you how old my boot experience is. Actually my original experience was with SCO Unix. I was certified back in the middle 90's. Lot of things have changed.  I have been able to use my special purpose rootfs for years by just upgrading the kernel with new drivers. But the kernel is starting to complain with the older libs. Now I need to create a new rootfs and move the special purpose scripts over to it. I am testing Arch over LFS, my thinking is it will be easier in the long run to update. I am building my "make pxe" environment and at the same time learning what is needed to integrate my scripts. Thanks for all the patience.

Offline

#16 2014-11-25 16:28:00

TheSaint
Member
From: my computer
Registered: 2007-08-19
Posts: 1,523

Re: [SLOVED] .rule required for udev to start an enabled network@.service?

Well, If you want to try using a fixed ip, what would it be the result ?
Just for the sake of an empiric learning.


do it good first, it will be faster than do it twice the saint wink

Offline

#17 2014-11-25 20:40:43

penright14
Member
Registered: 2014-11-20
Posts: 35

Re: [SLOVED] .rule required for udev to start an enabled network@.service?

TheSaint wrote:

Well, If you want to try using a fixed ip, what would it be the result ?
Just for the sake of an empiric learning.

I am all for documenting my stupidity if it saves someone else. :-)
My solve was static (fix) IP. If I would have followed the wiki right it would have worked.

There are a couple of good web resources that I found for the sytemd
http://www.hoverbear.org/2014/09/29/ini … d-targets/
https://wiki.archlinux.org/index.php/Systemd
https://wiki.archlinux.org/index.php/Systemd_FAQ

This is my newbie observation and if wrong someone can correct me.
snippte from init-runlevels-and targets

poweroff:       Halt the system.
rescue:         Single user mode.
multi-user:     Multi-user, non-graphical. User-defined/Site-specific runlevels.
graphical:      Multi-user, graphical. Usually multi-user + graphical login.
reboot:          Reboot
emergency:   Emergency Shell

So as in my example I type-o the multi-user and instead of a "-" (dash) I had a "." (period) 'multi.user' Well you look though both systemd/system (/etc and /usr/lib) there are no multi.user.target, there is a multi-user.target in the /usr/lib/system/sytemd. One other note that I found mentions somewhere, all your custom '.service' and '.target' need to go into the /etc tree. installer may overwrite the /usr/lib tree.
Then when you run the 'systemctl enable x.service' it creates a link.
So using network@.service as an example. the install sections has a 'WantedBy=multi-user.target.wants'
You when you run "systemctl enable network@ens32.service" it creates a link in the multi-user.target.wants directory back to the network@.service.
If you ls -l you would see something like lrwxrwxrwx 1 root root 36 Nov 25 06:25 network@ens32.service -> /etc/systemd/system/network@.service
Next a 'systemctl disable network@ens32.service' removes the link.

That is when I saw the link back to dhcpd and i disable it. I should have seen the same thing using the systemctl tool, but I am the kind of guy who cant remember details, if I know how it works, then I can get there.
I assume you want to use the systemctl to maintain the links, that way if something changes it will handle it.

Offline

#18 2014-11-26 09:24:17

TheSaint
Member
From: my computer
Registered: 2007-08-19
Posts: 1,523

Re: [SLOVED] .rule required for udev to start an enabled network@.service?

"penright14 wrote:

If I would have followed the wiki right it would have worked

So, is there a chance to use a dynamic IP too?

"penright14 wrote:

the kind of guy who cant remember details, if I know how it works, then I can get there

You're not alone big_smile


do it good first, it will be faster than do it twice the saint wink

Offline

#19 2014-11-26 13:36:06

penright14
Member
Registered: 2014-11-20
Posts: 35

Re: [SLOVED] .rule required for udev to start an enabled network@.service?

TheSaint wrote:

So, is there a chance to use a dynamic IP too?

Not quite sure I follow the quesiton. You can not have two configurations active at the same time. It has to be either dhcp or static. I am assuming you are asking did the dhcp still work?

Take the dhcpcd comments with a grain of salt, remember I have only been messing with Arch for a few days and this is based on my reading and experience.
In my case the nic is ens32.
Looking at dhcpcd first, there are two units (service). dhcpcd.service and dhcpcd@.service. The difference is the first will discover all nic and try to assign IP. The latter will just do the nic passed.
In my case it seemed that was the latter, the only thing that confused me was the link (enabled) was dhcpcd@_ens32.service. So that it what I had to use to disable. But you will see when I discribe my testing I did not use the underscore and it all worked as I expected. Not sure where or what the underscore came from or means.
For static after doing the wiki https://wiki.archlinux.org/index.php/Ne … figuration. The both dhcpcd services came "out of the box".

Hope this is what you were asking :-)

Since I had the static enabled.... this is the order of my test .....
After each step I rebooted, ran a 'ip a' to see what the nic interface ip was
1.
systemctl disable network@ens32.service
systemctl enable dhcpcd.service
Had a IP in our dhcp range
2.
systemctl disable dhcpcd.service
systemctl enable dhcpcd@ens32.service
Had a IP in our dhcp range
3.
systemctl disable dhcpcd@ens32.service
systemctl enable network@ens32.service
Had my static IP.

Offline

Board footer

Powered by FluxBB