From: Les Mikesell <lesmikesell(a)gmail.com>
> Agreed. But note that the standards are set long before that...
??? By "standard" what do you mean. ???
Linux's history has been notorious for variance from ANSI, NIST, POSIX
and GNU standards. Yes, far less than Microsoft and even some UNIX
vendors, but there are still major issues today with this.
When developers try to change things for standards compliance, they
get reamed by all the people who want backward compatibility instead.
That's why companies like Red Hat and SuSE try to not do it for several
versions until it comes to a head (typically future adoption required).
> If you are doing anything complicated, I'm not sure you have any
> other choice. But then you run into ugliness where you want to
> run perl programs that need perl=>5.8.3 to get character set handling
> right, and you can't, or you have to do a local install trying not
> to break the system version.
Internationalization is a reality and we English speaking Americans,
as well as Westerners in general, can't go around complaining when a
program really _does_ need to get off its American/Western-only duff.
That means getting away from ASCII as well as ISO8859.
In reality, there is a massive set of issues in the UNIX space where there
are no less than 15 common different interpretations of byte order,
endianess and organization just for 4-byte ISO character sets.
Pretty much all standards-based platforms are moving to UTF-8 because
it solves the multi-byte organizational issues. ASCII is still 7-bit (1 byte),
while any 4-byte ISO character set can be accomodated in 2-6 bytes total.
And as 1-6 streamed bytes, the common endianness is network order
(big endian), no multi-byte endianness/order issues.
Ironically, being an American company, this is where Red Hat has done
a phenominal job of any "western" distro company, IMHO, of pushing
_hard_ for UTF-8. Red Hat made this major shift with CL3.0 (Red Hat
Linux 8.0), which then went into EL3, which was based on CL3.1 (Red
Hat Linux 9). Typical bitching and moaning was present, condemnations
of both Perl maintainers of 5.8 and Red Hat Linux 8.0, etc...
More on the GUI front, I think Java and .NET/Mono have the right idea,
ISO10464 Unicode everything.
> Or you need mysql 4.x for transactions.
Again, there is a licensing issue with MySQL 4 that MySQL AB introduced
that most people, short of Red Hat, are ignoring. MySQL AB is GPL,
_not_ LGPL or BSD, so you have to be very careful what you link to it.
I see that Fedora Core 4 Test does adopt MySQL 4 though. I need to
read up on what Red Hat did, or is possibly excluding to make MySQL AB
happy (unless they changed their stance on some static linking) to find
out more.
> I guess my real complaint is that the bugfixes and improvements to
> the old releases that you are forced by the situation to run are
> minimal as soon as it becomes obvious that the future belongs to
> a different version - that may be a long time in stabilizing to
> a usable point.
So what's your solution?
I'm still waiting for someone to show me one better than the:
2-2-2 -> 6-6-6 model
In fact, the full model is really:
2-2-2 -> 6-6-6 -> 18-18-18 model
Whereby Red Hat and SuSE maintain up to 3 simultaneous versions of
their 18 month distros. [ Actually, SuSE is dropping the first "enterprise"
release, SLES 7 just shy of 5 years. ]
So if you are talking about stability/maturity, then run RHEL2.1 or now.
Heck, Fedora Legacy is _still_ supporting CL2.3 (RHL7.3) too! ;->
> It will be interesting to see how this works out for Ubuntu. I think it
> would be possible to be more aggressive with the application versions
> but hold back more than RH on the kernel changes.
And that's the real question. What is the "best balance"?
> Of course they'll have it easy for the first few since they don't have to
> be backwards compatible to a huge installed base.
Exactomundo! ;->
In reality, Red Hat has probably the longest "backward compatible" run
of any vendor. Why? Because they adopt things early -- like GLibC 2,
GCC 3, NPTL, etc...
Heck, pretty much everything released for CL/EL2 (GLibC 2.2,
GCC 2.96/3.0 -- RHL7.x/RHEL2.1) still runs on my latest Fedora Core 4
Test systems.
> How was the CIPE author supposed to know that what would be
> released as FC2 would have a changed kernel interface?
My God, I actually can't believe you could even make such a statement.
At this point, it's _futile_ to even really debate you anymore, you keep
talking from a total standing of "assumption" and "unfamilarity."
Something a maintainer of a package would not be, unless he honestly
didn't care.
Fedora Core 2 (2004May) was released 6 months _after_ Linux 2.6 (2003Dec).
Fedora Core 1 -- fka Red Hat Linux 10 -- had just been released (2003Nov)
before kernel 2.6.
Within 2 months, Rawhide/Development had Fedora Core 2's intended kernel
-- 2.6. There was absolutely _no_question_ what it was going to be.
I know, I was checking out the packages on Fedora Development -- saw
2.6.1/2.6.2. I believe 2.6.3 was the first one used in Fedora Core 2 Test 1 in
2004Mar.
Red Hat's Rawhide, now Fedora Development (although many Red Hat
employees still call it "Rawhide" ;-), has been around since the Red Hat
Linux 5.x timeframe. It's the packages that are being built for the next
revision -- be it same version or a major version change. Rawhide/Dev
is the "package testing," so you can see what packages they are looking
at. Beta/Test is the "regression testing" of the entire release as a whole
(packages against packages testing in all).
Again, the 2-2-2 model. There is at least 4 months before release when
you can find out pretty much _anything_ that's going to be in the distro
for a good certainty.
Pretty much every major distro -- Red Hat, SuSE, etc... adopted Linux 2.6
within 6 months. SuSE even released SuSE Linux 9.0 before 2.6 was
released, but with a lot of the backports (like Red Hat) in prepartion for
2.6 in SL9.1.
> He did respond with 1.6 as quickly as could be expected after a released
> distribution didn't work with it and a user reported problems on the mailing
> list.
How can you blame this on distributions? Honestly, I don't see it at all!
There were months and months of pre-release 2.6 releases in 2003.
I saw the comments that many things weren't working (including CIPE).
There were 6 months between Linux 2.6's release and FC2. Heck, I believe
SL9.1 came out with it before that.
> About the kernel, or all of the drivers' authors that assumed that
> kernel interfaces shouldn't change?
Many drivers were actually _deprecated_ in kernel 2.6, and not built by
default because people didn't come forward and take ownership. I know,
the lack of the "advansys.c" SCSI driver got me good. ;->
But who did I blame? Myself for not volunteering! At some point,
when there's lack of interest, it typically means there are not enough
people interested to hold up everything.
> And if you want the things that work to not change???
Then you do _not_ adopt the latest distro that just came out -- especially
not an "early adopter" release. It was well known that Fedora Core 2
was changing a lot of things, just like SuSE Linux 9.0/9.1.
[ SIDE NOTE: Again, I have stated that I am _disappointed_ that Red Hat
does not use revisioning to designation something like Fedora Core 2
as a ".0" revision. But it was well known it was going to be kernel 2.6
4 months before its release. ]
> Where do you find the real info?
It takes me 5 minutes to figure out what Red Hat's up to. Red Hat is
pretty explicit on what their plans are, and the packages are out there
for all to see during Development, even _before_ the Test hits (Development
is about 4 months before release).
Heck, when their Test 1 hits (a good 2+ months before release), they go
over _all_ the major changes in the "Release Notes." SuSE and even
Mandrake are similar too.
> Specific example: I'm trying to make a software RAID1 partition with
> one internal IDE and a matching external drive in a firewire case work.
> FC1 worked flawlessly once the raid was established but would not
> autodetect the drive, either when hotplugged or at bootup. Everything
> later that I've tried is worse. Some get the autodetect right on a
> hotplug but crash after some amount of runtime.
> Is any distro likely to autodetect at bootup in time to cleanly connect
> the RAID and then keep working?
When you disconnect a drive from the RAID array, there is no way
for the software to assume whether or not the drive is any good anymore
when it reconnects unless you _manually_ tell it (or configure it to always
assume it is good).
This is not a Red Hat issue either.
And LVM2 is still going through some maturity with RAID-1 and snapshots.
> Maybe it matters that the filesystem is reiserfs - I see some bug
> reports about that, but rarely have problems when the internal IDE
> is running as a broken mirror.
Filesystem shouldn't matter, it's a Disk Label (aka Partition Table)
consideration.
> Like letting it be a surprise to the CIPE author that it didn't work
> at release time. I don't remember seeing a hint about this on the
> CIPE mail list when someone must have known well ahead that it was
> coming.
More assumptions. CIPE has been breaking in 2.6 since the very early
2.5.2+ developments. I'm sure the author was waiting until late in 2.5 (say
near 2.5.70+) as it came closer to 2.6. I saw reports on all sorts of
network code breakage the second it hit in 2003Dec -- 6 months before.
In looking through Fedora Development, I note lots of references to all sorts
of issues with the 2.6-test releases as of summer of 2004 (over 9 months
before FC2 release, months before kernel 2.6's official release). There were
efforts to get cipe to work -- both in FC2 and then in Fedora Extras for FC2,
but they were eventually dropped because of lack of interested by the
CIPE developers themselveas in getting "up-to-speed" on 2.5/2.6.
The first hints of recommendations to go IPSec instead were that fall.
By March of 2004, I see the last comments to not even bother with CIPE
for Fedora Core 2 (as well as SuSE Linux 9.1) were made from several.
> Buggy. I don't mean RH bugs, I mean bugs from the upstream packages
> that got their first huge real world exposure because RH bundled them
> on a CD that you could drop into just about any PC and have a working
> system. I mean things like the bind, sendmail, and ssh versions that
> went out with RH 4.0 and were installed on more machines than ever
> before - all with remote exploits that weren't known yet.
Yes, Linux is not free from vunerabilities. This is not new.
Either you pay for a subscription (and optional SLA) to an "enterprise"
distro that maintains 5+ years of support, or you rely on community
projects (like Fedora Legacy) that attempt to do the same. Fedora
Legacy is still supporting CL2.3 (Red Hat Linux 7.3), even though they
dropped CL3.0 (Red Hat Linux 8.0) a long time ago because CL3.1/3.2
(Red Hat Linux 9 / Fedora Core 1) exist.
> The real world is a complicated place. If you want to substitute
> a different program for an old but non-standard one you need to
> make sure it handles all the same things.
But what if those either conflict with standards or are broken?
> Until just recently, star didn't even come close to getting incrementals
> right and still. unlike gnutar, requires the runs to be on filesystem
> boundaries for incrementals to work. And, it probably doesn't handle
> the options that amanda needs. Theory, meet practice.
You assume "GNU Tar" is the "standard." ;->
It's not, never has been, and is years late to the POSIX-2001/SUSv3
party.
As far as not crossing filesystem boundaries, that is easily accomodated.
> By 'first', I meant before RH 4.x, which in my opinion really drove
> the popularity of Linux simply because it had a decent installer
> that came up working on most hardware at the time. Freebsd was
> around at the time but in a form that was much more difficult
> for a new user to get working.
> That depends on when you started. Before SP6, NT was also unreliable.
Hell of a lot better than "Chicago," but yes, I agree.
> Remember that in the timeframe of RH4, you could kill an NT box
> by sending it an oversized ping packet - and have a fair chance of
> corrupting the filesystem beyond repair from the ungraceful shutdown.
Oh, you could hang Linux in various ways too, just not as many.
> It wasn't so much the cloning as it was setting the IP address
> with their GUI tool (and I did that because when I just made
> the change to the /etc/sysconfig/network-scripts/ifcfg-xxx file
> the way that worked in earlier RH versions it sometimes mysteriously
> didn't work). Then I shipped the disks in their hot-swap carriers to
> the remote sites to be installed.
Again, I will repeat that "configuration management" is part of avoiding
"professional negligence." You should have tested those carriers before
shipping them out by putting them in another box.
> That procedure can't be uncommon.
No, it's not uncommon, I didn't say that. I'm just saying that vendors
can't test for a lot of different issues.
Don't get me started on the design of NTFS and the Registry SAM-SID
issues. The current "hack" is to either put everything in a domain, or
use Dynamic Discs to store stuff outside of a NTFS filesystem because
you can _never_ safely access a NTFS filesystem _except_ for the NT
installation that created it (not even with another install of the same
NT version).
> And the same thing would happen if you swapped a NIC card -
> hmmm, I wonder about PCMCIA cards now.
Yes, maybe that has something to do with it, eh? ;->
For example, maybe when you want to switch between an unclassified
and classified network, you use a different card (and hard drive), which
will connect to a different subnet. ;->
I'm sure some changes have been for "Common Criteria" compliance.
I've seen similiar on SuSE as well. They might have been made mid-update.
> I'm not sure exactly when it happened because it was an update that
> did not include a new kernel so the machines weren't rebooted
> immediately. I think the ones where I noticed it first were somewhere
> in the Centos 3.4 range with some subsequent updates (maybe a month
> or so ago).
I'll check it out then.
> I think this was just an update without a version number change. As it
> turned out, I saw the screen of one that was rebooted at a nearby site
> and knew more or less what happened but before I got around to fixing
> them all a machine crashed at a distant site and I had to talk someone
> who didn't know vi through finding the file and removing the hardware
> address entry.
No offense, but when I ship out components to remote sites, I do my
due dilligence and test for every condition I can think of. But maybe
I'm anal because I ship things out to places like White Sands, Edwards,
etc... and techs can't be expected debugging such concepts, so
I always test with at least a partially replicated environment (which
would be at least 1 change of physical system ;-).
> If I hadn't already known about it by then or if a lot of the remote
> servers had been rebooted and came up with no network
> access it might have ruined my whole day.
I think you're assigning blame in the wrong direction. You might think
that's rude and arrogant, but in reality, if you keep blaming vendors for
those type of mistakes, you're going to have a lot more of them coming
your way until you change that attitude. No offense. ;->
--
Bryan J. Smith mailto:b.j.smith@ieee.org
Folks
I'm playing with a Raspberry Pi 2 and Centos. Here are some issues
I've bumped into. I'm not sure this is the right medium for
commenting; please correct me if needed.
I wrote a copy of the distributed image (1151) to my MicroSD card,
then turned on the Rpi2.
Issue 1:
Even though my DHCP server was configured to give the node a name,
it showed up as "rpi2" as the host name.
Issue 2:
Network works, but if I issue the command
systemctl reset network
the command fails and I haven't found a way to get the network
back. I saved the output of "journalctl -ce", rebooted, and
installed "ftp" so I could copy the data to a real machine. The text
is as below.
I issued the "systemctl reset network" command towards the bottom,
where you see the time jump from 00:01:01 to 00:02:28
--------------------------------------------------------------
-- Logs begin at Thu 1970-01-01 00:00:04 UTC, end at Thu 1970-01-01
00:02:28 UTC. --
Jan 01 00:00:04 rpi2 systemd-journal[81]: Runtime journal is using
5.7M (max allowed 46.3M, trying to leave 69.4M free of 457.1M
available ? current limit 46.3M).
Jan 01 00:00:04 rpi2 systemd-journal[81]: Runtime journal is using
5.7M (max allowed 46.3M, trying to leave 69.4M free of 457.1M
available ? current limit 46.3M).
Jan 01 00:00:04 rpi2 kernel: Booting Linux on physical CPU 0xf00
Jan 01 00:00:04 rpi2 kernel: Initializing cgroup subsys cpuset
Jan 01 00:00:04 rpi2 kernel: Initializing cgroup subsys cpu
Jan 01 00:00:04 rpi2 kernel: Initializing cgroup subsys cpuacct
Jan 01 00:00:04 rpi2 kernel: Linux version 4.1.11-v7+
(dc4@dc4-XPS13-9333) (gcc version 4.8.3 20140303 (prerelease)
(crosstool-NG linaro-1.13.1+bzr2650 - Linaro GCC 2014.03) ) #822 SMP
PREEMPT Fri Oct 23 16:22:18 BST 2015
Jan 01 00:00:04 rpi2 kernel: CPU: ARMv7 Processor [410fc075] revision
5 (ARMv7), cr=10c5387d
Jan 01 00:00:04 rpi2 kernel: CPU: PIPT / VIPT nonaliasing data cache,
VIPT aliasing instruction cache
Jan 01 00:00:04 rpi2 kernel: Machine: BCM2709
Jan 01 00:00:04 rpi2 kernel: cma: Reserved 8 MiB at 0x3a800000
Jan 01 00:00:04 rpi2 kernel: Memory policy: Data cache writealloc
Jan 01 00:00:04 rpi2 kernel: On node 0 totalpages: 241664
Jan 01 00:00:04 rpi2 kernel: free_area_init_node: node 0, pgdat
80859000, node_mem_map b9fa6000
Jan 01 00:00:04 rpi2 kernel: Normal zone: 2124 pages used for memmap
Jan 01 00:00:04 rpi2 kernel: Normal zone: 0 pages reserved
Jan 01 00:00:04 rpi2 kernel: Normal zone: 241664 pages, LIFO batch:31
Jan 01 00:00:04 rpi2 kernel: [bcm2709_smp_init_cpus] enter (9420->f3003010)
Jan 01 00:00:04 rpi2 kernel: [bcm2709_smp_init_cpus] ncores=4
Jan 01 00:00:04 rpi2 kernel: PERCPU: Embedded 13 pages/cpu @b9f6d000
s20608 r8192 d24448 u53248
Jan 01 00:00:04 rpi2 kernel: pcpu-alloc: s20608 r8192 d24448 u53248
alloc=13*4096
Jan 01 00:00:04 rpi2 kernel: pcpu-alloc: [0] 0 [0] 1 [0] 2 [0] 3
Jan 01 00:00:04 rpi2 kernel: Built 1 zonelists in Zone order,
mobility grouping on. Total pages: 239540
Jan 01 00:00:04 rpi2 kernel: Kernel command line: dma.dmachans=0x7f35
bcm2708_fb.fbwidth=1872 bcm2708_fb.fbheight=1168
bcm2709.boardrev=0xa21041 bcm2709.serial=0x72e14965
smsc95xx.macaddr=B8:27:EB:E1:49:65 bcm2708_fb.fbswap=1
bcm2709.disk_led_gpio=47 bcm2709.disk_led_active_low=0
sdhci-bcm2708.emmc_clock_freq=250000000 vc_mem.mem_base=0x3dc00000
vc_mem.mem_size=0x3f000000 dwc_otg.lpm_enable=0
console=ttyAMA0,115200 console=tty1 root=/dev/mmcblk0p3
rootfstype=ext4 elevator=deadline rootwait
Jan 01 00:00:04 rpi2 kernel: PID hash table entries: 4096 (order: 2,
16384 bytes)
Jan 01 00:00:04 rpi2 kernel: Dentry cache hash table entries: 131072
(order: 7, 524288 bytes)
Jan 01 00:00:04 rpi2 kernel: Inode-cache hash table entries: 65536
(order: 6, 262144 bytes)
Jan 01 00:00:04 rpi2 kernel: Memory: 939572K/966656K available (5955K
kernel code, 534K rwdata, 1644K rodata, 416K init, 757K bss, 18892K
reserved, 8192K cma-reserved)
Jan 01 00:00:04 rpi2 kernel: Virtual kernel memory layout:
vector : 0xffff0000 - 0xffff1000 ( 4 kB)
fixmap : 0xffc00000 - 0xfff00000 (3072 kB)
vmalloc : 0xbb800000 - 0xff000000 (1080 MB)
lowmem : 0x80000000 - 0xbb000000 ( 944 MB)
modules : 0x7f000000 - 0x80000000 ( 16 MB)
.text : 0x80008000 - 0x80773e88 (7600 kB)
.init : 0x80774000 - 0x807dc000 ( 416 kB)
.data : 0x807dc000 - 0x80861b6c ( 535 kB)
.bss : 0x80864000 - 0x8092179c ( 758 kB)
Jan 01 00:00:04 rpi2 kernel: SLUB: HWalign=64, Order=0-3,
MinObjects=0, CPUs=4, Nodes=1
Jan 01 00:00:04 rpi2 kernel: Preemptible hierarchical RCU implementation.
Jan 01 00:00:04 rpi2 kernel: Additional per-CPU info printed
with stalls.
Jan 01 00:00:04 rpi2 kernel: NR_IRQS:608
Jan 01 00:00:04 rpi2 kernel: Architected cp15 timer(s) running at
19.20MHz (phys).
Jan 01 00:00:04 rpi2 kernel: clocksource arch_sys_counter: mask:
0xffffffffffffff max_cycles: 0x46d987e47, max_idle_ns: 440795202767 ns
Jan 01 00:00:04 rpi2 kernel: sched_clock: 56 bits at 19MHz,
resolution 52ns, wraps every 4398046511078ns
Jan 01 00:00:04 rpi2 kernel: Switching to timer-based delay loop,
resolution 52ns
Jan 01 00:00:04 rpi2 kernel: Console: colour dummy device 80x30
Jan 01 00:00:04 rpi2 kernel: console [tty1] enabled
Jan 01 00:00:04 rpi2 kernel: Calibrating delay loop (skipped), value
calculated using timer frequency.. 38.40 BogoMIPS (lpj=192000)
Jan 01 00:00:04 rpi2 kernel: pid_max: default: 32768 minimum: 301
Jan 01 00:00:04 rpi2 kernel: Mount-cache hash table entries: 2048
(order: 1, 8192 bytes)
Jan 01 00:00:04 rpi2 kernel: Mountpoint-cache hash table entries:
2048 (order: 1, 8192 bytes)
Jan 01 00:00:04 rpi2 kernel: Initializing cgroup subsys blkio
Jan 01 00:00:04 rpi2 kernel: Initializing cgroup subsys memory
Jan 01 00:00:04 rpi2 kernel: Initializing cgroup subsys devices
Jan 01 00:00:04 rpi2 kernel: Initializing cgroup subsys freezer
Jan 01 00:00:04 rpi2 kernel: Initializing cgroup subsys net_cls
Jan 01 00:00:04 rpi2 kernel: CPU: Testing write buffer coherency: ok
Jan 01 00:00:04 rpi2 kernel: ftrace: allocating 20224 entries in 60 pages
Jan 01 00:00:04 rpi2 kernel: missing device node for CPU 0
Jan 01 00:00:04 rpi2 kernel: missing device node for CPU 1
Jan 01 00:00:04 rpi2 kernel: missing device node for CPU 2
Jan 01 00:00:04 rpi2 kernel: missing device node for CPU 3
Jan 01 00:00:04 rpi2 kernel: CPU0: thread -1, cpu 0, socket 15, mpidr 80000f00
Jan 01 00:00:04 rpi2 kernel: [bcm2709_smp_prepare_cpus] enter
Jan 01 00:00:04 rpi2 kernel: Setting up static identity map for 0x8240 - 0x8274
Jan 01 00:00:04 rpi2 kernel: [bcm2709_boot_secondary] cpu:1 started (0) 16
Jan 01 00:00:04 rpi2 kernel: [bcm2709_secondary_init] enter cpu:1
Jan 01 00:00:04 rpi2 kernel: CPU1: thread -1, cpu 1, socket 15, mpidr 80000f01
Jan 01 00:00:04 rpi2 kernel: [bcm2709_boot_secondary] cpu:2 started (0) 18
Jan 01 00:00:04 rpi2 kernel: [bcm2709_secondary_init] enter cpu:2
Jan 01 00:00:04 rpi2 kernel: CPU2: thread -1, cpu 2, socket 15, mpidr 80000f02
Jan 01 00:00:04 rpi2 kernel: [bcm2709_boot_secondary] cpu:3 started (0) 18
Jan 01 00:00:04 rpi2 kernel: [bcm2709_secondary_init] enter cpu:3
Jan 01 00:00:04 rpi2 kernel: CPU3: thread -1, cpu 3, socket 15, mpidr 80000f03
Jan 01 00:00:04 rpi2 kernel: Brought up 4 CPUs
Jan 01 00:00:04 rpi2 kernel: SMP: Total of 4 processors activated
(153.60 BogoMIPS).
Jan 01 00:00:04 rpi2 kernel: CPU: All CPU(s) started in HYP mode.
Jan 01 00:00:04 rpi2 kernel: CPU: Virtualization extensions available.
Jan 01 00:00:04 rpi2 kernel: devtmpfs: initialized
Jan 01 00:00:04 rpi2 kernel: VFP support v0.3: implementor 41
architecture 2 part 30 variant 7 rev 5
Jan 01 00:00:04 rpi2 kernel: clocksource jiffies: mask: 0xffffffff
max_cycles: 0xffffffff, max_idle_ns: 19112604462750000 ns
Jan 01 00:00:04 rpi2 kernel: pinctrl core: initialized pinctrl subsystem
Jan 01 00:00:04 rpi2 kernel: NET: Registered protocol family 16
Jan 01 00:00:04 rpi2 kernel: DMA: preallocated 4096 KiB pool for
atomic coherent allocations
Jan 01 00:00:04 rpi2 kernel: bcm2709.uart_clock = 3000000
Jan 01 00:00:04 rpi2 kernel: of_platform_populate failed: -22
Jan 01 00:00:04 rpi2 kernel: hw-breakpoint: found 5 (+1 reserved)
breakpoint and 4 watchpoint registers.
Jan 01 00:00:04 rpi2 kernel: hw-breakpoint: maximum watchpoint size is 8 bytes.
Jan 01 00:00:04 rpi2 kernel: Serial: AMBA PL011 UART driver
Jan 01 00:00:04 rpi2 kernel: dev:f1: ttyAMA0 at MMIO 0x3f201000 (irq
= 83, base_baud = 0) is a PL011 rev3
Jan 01 00:00:04 rpi2 kernel: console [ttyAMA0] enabled
Jan 01 00:00:04 rpi2 kernel: bcm2835-mbox bcm2835-mbox: mailbox enabled
Jan 01 00:00:04 rpi2 kernel: bcm2708-dmaengine bcm2708-dmaengine: DMA
legacy API manager at f3007000, dmachans=0x7f35
Jan 01 00:00:04 rpi2 kernel: bcm2708-dmaengine bcm2708-dmaengine:
failed to get irq for DMA channel 13
Jan 01 00:00:04 rpi2 kernel: bcm2708-dmaengine bcm2708-dmaengine:
Initialized 8 DMA channels (+ 1 legacy)
Jan 01 00:00:04 rpi2 kernel: bcm2708-dmaengine bcm2708-dmaengine:
Load BCM2835 DMA engine driver
Jan 01 00:00:04 rpi2 kernel: bcm2708-dmaengine bcm2708-dmaengine: dma_debug:0
Jan 01 00:00:04 rpi2 kernel: SCSI subsystem initialized
Jan 01 00:00:04 rpi2 kernel: usbcore: registered new interface driver usbfs
Jan 01 00:00:04 rpi2 kernel: usbcore: registered new interface driver hub
Jan 01 00:00:04 rpi2 kernel: usbcore: registered new device driver usb
Jan 01 00:00:04 rpi2 kernel: raspberrypi-firmware
raspberrypi-firmware.0: Attached to firmware from 2015-10-23 16:24
Jan 01 00:00:04 rpi2 kernel: Switched to clocksource arch_sys_counter
Jan 01 00:00:04 rpi2 kernel: FS-Cache: Loaded
Jan 01 00:00:04 rpi2 kernel: CacheFiles: Loaded
Jan 01 00:00:04 rpi2 kernel: NET: Registered protocol family 2
Jan 01 00:00:04 rpi2 kernel: TCP established hash table entries: 8192
(order: 3, 32768 bytes)
Jan 01 00:00:04 rpi2 kernel: TCP bind hash table entries: 8192
(order: 4, 65536 bytes)
Jan 01 00:00:04 rpi2 kernel: TCP: Hash tables configured (established
8192 bind 8192)
Jan 01 00:00:04 rpi2 kernel: UDP hash table entries: 512 (order: 2,
16384 bytes)
Jan 01 00:00:04 rpi2 kernel: UDP-Lite hash table entries: 512 (order:
2, 16384 bytes)
Jan 01 00:00:04 rpi2 kernel: NET: Registered protocol family 1
Jan 01 00:00:04 rpi2 kernel: RPC: Registered named UNIX socket
transport module.
Jan 01 00:00:04 rpi2 kernel: RPC: Registered udp transport module.
Jan 01 00:00:04 rpi2 kernel: RPC: Registered tcp transport module.
Jan 01 00:00:04 rpi2 kernel: RPC: Registered tcp NFSv4.1 backchannel
transport module.
Jan 01 00:00:04 rpi2 kernel: bcm2708_gpio: bcm2708_gpio_probe 80800a68
Jan 01 00:00:04 rpi2 kernel: futex hash table entries: 1024 (order:
4, 65536 bytes)
Jan 01 00:00:04 rpi2 kernel: VFS: Disk quotas dquot_6.6.0
Jan 01 00:00:04 rpi2 kernel: VFS: Dquot-cache hash table entries:
1024 (order 0, 4096 bytes)
Jan 01 00:00:04 rpi2 kernel: FS-Cache: Netfs 'nfs' registered for caching
Jan 01 00:00:04 rpi2 kernel: NFS: Registering the id_resolver key type
Jan 01 00:00:04 rpi2 kernel: Key type id_resolver registered
Jan 01 00:00:04 rpi2 kernel: Key type id_legacy registered
Jan 01 00:00:04 rpi2 kernel: Block layer SCSI generic (bsg) driver
version 0.4 loaded (major 252)
Jan 01 00:00:04 rpi2 kernel: io scheduler noop registered
Jan 01 00:00:04 rpi2 kernel: io scheduler deadline registered (default)
Jan 01 00:00:04 rpi2 kernel: io scheduler cfq registered
Jan 01 00:00:04 rpi2 kernel: BCM2708FB: allocated DMA memory fac00000
Jan 01 00:00:04 rpi2 kernel: BCM2708FB: allocated DMA channel 0 @ f3007000
Jan 01 00:00:04 rpi2 kernel: Console: switching to colour frame
buffer device 234x73
Jan 01 00:00:04 rpi2 kernel: Serial: 8250/16550 driver, 0 ports, IRQ
sharing disabled
Jan 01 00:00:04 rpi2 kernel: vc-cma: Videocore CMA driver
Jan 01 00:00:04 rpi2 kernel: vc-cma: vc_cma_base = 0x00000000
Jan 01 00:00:04 rpi2 kernel: vc-cma: vc_cma_size = 0x00000000 (0 MiB)
Jan 01 00:00:04 rpi2 kernel: vc-cma: vc_cma_initial = 0x00000000 (0 MiB)
Jan 01 00:00:04 rpi2 kernel: vc-mem: phys_addr:0x00000000
mem_base=0x3dc00000 mem_size:0x3f000000(1008 MiB)
Jan 01 00:00:04 rpi2 kernel: brd: module loaded
Jan 01 00:00:04 rpi2 kernel: loop: module loaded
Jan 01 00:00:04 rpi2 kernel: vchiq: vchiq_init_state: slot_zero =
0xbac80000, is_master = 0
Jan 01 00:00:04 rpi2 kernel: Loading iSCSI transport class v2.0-870.
Jan 01 00:00:04 rpi2 kernel: usbcore: registered new interface driver smsc95xx
Jan 01 00:00:04 rpi2 kernel: dwc_otg: version 3.00a 10-AUG-2012 (platform bus)
Jan 01 00:00:04 rpi2 kernel: Core Release: 2.80a
Jan 01 00:00:04 rpi2 kernel: Setting default values for core params
Jan 01 00:00:04 rpi2 kernel: Finished setting default values for core params
Jan 01 00:00:04 rpi2 kernel: Using Buffer DMA mode
Jan 01 00:00:04 rpi2 kernel: Periodic Transfer Interrupt Enhancement - disabled
Jan 01 00:00:04 rpi2 kernel: Multiprocessor Interrupt Enhancement - disabled
Jan 01 00:00:04 rpi2 kernel: OTG VER PARAM: 0, OTG VER FLAG: 0
Jan 01 00:00:04 rpi2 kernel: Dedicated Tx FIFOs mode
Jan 01 00:00:04 rpi2 kernel: WARN::dwc_otg_hcd_init:1047: FIQ DMA
bounce buffers: virt = 0xbac14000 dma = 0xfac14000 len=9024
Jan 01 00:00:04 rpi2 kernel: FIQ FSM acceleration enabled for :
Non-periodic Split Transactions
Periodic Split Transactions
High-Speed Isochronous Endpoints
Jan 01 00:00:04 rpi2 kernel: dwc_otg: Microframe scheduler enabled
Jan 01 00:00:04 rpi2 kernel: WARN::hcd_init_fiq:412: FIQ on core 1 at
0x80400a40
Jan 01 00:00:04 rpi2 kernel: WARN::hcd_init_fiq:413: FIQ ASM at
0x80400d9c length 36
Jan 01 00:00:04 rpi2 kernel: WARN::hcd_init_fiq:438: MPHI regs_base
at 0xbb89a000
Jan 01 00:00:04 rpi2 kernel: dwc_otg bcm2708_usb: DWC OTG Controller
Jan 01 00:00:04 rpi2 kernel: dwc_otg bcm2708_usb: new USB bus
registered, assigned bus number 1
Jan 01 00:00:04 rpi2 kernel: dwc_otg bcm2708_usb: irq 32, io mem 0x00000000
Jan 01 00:00:04 rpi2 kernel: Init: Port Power? op_state=1
Jan 01 00:00:04 rpi2 kernel: Init: Power Port (0)
Jan 01 00:00:04 rpi2 kernel: usb usb1: New USB device found,
idVendor=1d6b, idProduct=0002
Jan 01 00:00:04 rpi2 kernel: usb usb1: New USB device strings: Mfr=3,
Product=2, SerialNumber=1
Jan 01 00:00:04 rpi2 kernel: usb usb1: Product: DWC OTG Controller
Jan 01 00:00:04 rpi2 kernel: usb usb1: Manufacturer: Linux 4.1.11-v7+
dwc_otg_hcd
Jan 01 00:00:04 rpi2 kernel: usb usb1: SerialNumber: bcm2708_usb
Jan 01 00:00:04 rpi2 kernel: hub 1-0:1.0: USB hub found
Jan 01 00:00:04 rpi2 kernel: hub 1-0:1.0: 1 port detected
Jan 01 00:00:04 rpi2 kernel: dwc_otg: FIQ enabled
Jan 01 00:00:04 rpi2 kernel: dwc_otg: NAK holdoff enabled
Jan 01 00:00:04 rpi2 kernel: dwc_otg: FIQ split-transaction FSM enabled
Jan 01 00:00:04 rpi2 kernel: Module dwc_common_port init
Jan 01 00:00:04 rpi2 kernel: usbcore: registered new interface driver
usb-storage
Jan 01 00:00:04 rpi2 kernel: mousedev: PS/2 mouse device common for all mice
Jan 01 00:00:04 rpi2 kernel: bcm2835-cpufreq: min=600000 max=700000
Jan 01 00:00:04 rpi2 kernel: sdhci: Secure Digital Host Controller
Interface driver
Jan 01 00:00:04 rpi2 kernel: sdhci: Copyright(c) Pierre Ossman
Jan 01 00:00:04 rpi2 kernel: mmc-bcm2835 mmc-bcm2835.0: mmc_debug:0
mmc_debug2:0
Jan 01 00:00:04 rpi2 kernel: mmc-bcm2835 mmc-bcm2835.0: DMA channels allocated
Jan 01 00:00:04 rpi2 kernel: sdhci-pltfm: SDHCI platform and OF driver helper
Jan 01 00:00:04 rpi2 kernel: ledtrig-cpu: registered to indicate
activity on CPUs
Jan 01 00:00:04 rpi2 kernel: hidraw: raw HID events driver (C) Jiri Kosina
Jan 01 00:00:04 rpi2 kernel: usbcore: registered new interface driver usbhid
Jan 01 00:00:04 rpi2 kernel: usbhid: USB HID core driver
Jan 01 00:00:04 rpi2 kernel: Initializing XFRM netlink socket
Jan 01 00:00:04 rpi2 kernel: NET: Registered protocol family 17
Jan 01 00:00:04 rpi2 kernel: Indeed it is in host mode hprt0 = 00021501
Jan 01 00:00:04 rpi2 kernel: Key type dns_resolver registered
Jan 01 00:00:04 rpi2 kernel: Registering SWP/SWPB emulation handler
Jan 01 00:00:04 rpi2 kernel: registered taskstats version 1
Jan 01 00:00:04 rpi2 kernel: vc-sm: Videocore shared memory driver
Jan 01 00:00:04 rpi2 kernel: [vc_sm_connected_init]: start
Jan 01 00:00:04 rpi2 kernel: [vc_sm_connected_init]: end - returning 0
Jan 01 00:00:04 rpi2 kernel: Waiting for root device /dev/mmcblk0p3...
Jan 01 00:00:04 rpi2 kernel: mmc0: host does not support reading
read-only switch, assuming write-enable
Jan 01 00:00:04 rpi2 kernel: mmc0: new high speed SDHC card at address 0001
Jan 01 00:00:04 rpi2 kernel: mmcblk0: mmc0:0001 00000 29.8 GiB
Jan 01 00:00:04 rpi2 kernel: mmcblk0: p1 p2 p3
Jan 01 00:00:04 rpi2 kernel: usb 1-1: new high-speed USB device
number 2 using dwc_otg
Jan 01 00:00:04 rpi2 kernel: Indeed it is in host mode hprt0 = 00001101
Jan 01 00:00:04 rpi2 kernel: EXT4-fs (mmcblk0p3): mounted filesystem
with ordered data mode. Opts: (null)
Jan 01 00:00:04 rpi2 kernel: VFS: Mounted root (ext4 filesystem) on
device 179:3.
Jan 01 00:00:04 rpi2 kernel: devtmpfs: mounted
Jan 01 00:00:04 rpi2 kernel: Freeing unused kernel memory: 416K
(80774000 - 807dc000)
Jan 01 00:00:04 rpi2 kernel: usb 1-1: New USB device found,
idVendor=0424, idProduct=9514
Jan 01 00:00:04 rpi2 kernel: usb 1-1: New USB device strings: Mfr=0,
Product=0, SerialNumber=0
Jan 01 00:00:04 rpi2 kernel: hub 1-1:1.0: USB hub found
Jan 01 00:00:04 rpi2 kernel: hub 1-1:1.0: 5 ports detected
Jan 01 00:00:04 rpi2 kernel: usb 1-1.1: new high-speed USB device
number 3 using dwc_otg
Jan 01 00:00:04 rpi2 kernel: NET: Registered protocol family 10
Jan 01 00:00:04 rpi2 systemd[1]: Inserted module 'ipv6'
Jan 01 00:00:04 rpi2 kernel: usb 1-1.1: New USB device found,
idVendor=0424, idProduct=ec00
Jan 01 00:00:04 rpi2 kernel: usb 1-1.1: New USB device strings:
Mfr=0, Product=0, SerialNumber=0
Jan 01 00:00:04 rpi2 kernel: ip_tables: (C) 2000-2006 Netfilter Core Team
Jan 01 00:00:04 rpi2 systemd[1]: Inserted module 'ip_tables'
Jan 01 00:00:04 rpi2 kernel: smsc95xx v1.0.4
Jan 01 00:00:04 rpi2 kernel: random: systemd urandom read with 64
bits of entropy available
Jan 01 00:00:04 rpi2 systemd[1]: systemd 219 running in system mode.
(+PAM +AUDIT +SELINUX +IMA -APPARMOR +SMACK +SYSVINIT +UTMP
+LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ -LZ4 -SECCOMP +BLKID
+ELFUTILS +KMOD +IDN)
Jan 01 00:00:04 rpi2 systemd[1]: Detected architecture arm.
Jan 01 00:00:04 rpi2 systemd[1]: Set hostname to <rpi2>.
Jan 01 00:00:04 rpi2 kernel: smsc95xx 1-1.1:1.0 eth0: register
'smsc95xx' at usb-bcm2708_usb-1.1, smsc95xx USB 2.0 Ethernet, b8:27:eb:e1:49:65
Jan 01 00:00:04 rpi2 kernel: uart-pl011 dev:f1: no DMA platform data
Jan 01 00:00:04 rpi2 kernel: usb 1-1.3: new low-speed USB device
number 4 using dwc_otg
Jan 01 00:00:04 rpi2 kernel: usb 1-1.3: New USB device found,
idVendor=045e, idProduct=0040
Jan 01 00:00:04 rpi2 kernel: usb 1-1.3: New USB device strings:
Mfr=1, Product=3, SerialNumber=0
Jan 01 00:00:04 rpi2 kernel: usb 1-1.3: Product: Microsoft 3-Button
Mouse with IntelliEye(TM)
Jan 01 00:00:04 rpi2 kernel: usb 1-1.3: Manufacturer: Microsoft
Jan 01 00:00:04 rpi2 kernel: input: Microsoft Microsoft 3-Button
Mouse with IntelliEye(TM) as
/devices/platform/bcm2708_usb/usb1/1-1/1-1.3/1-1.3:1.0/0003:045E:0040.0001/input/input0
Jan 01 00:00:04 rpi2 kernel: hid-generic 0003:045E:0040.0001:
input,hidraw0: USB HID v1.10 Mouse [Microsoft Microsoft 3-Button
Mouse with IntelliEye(TM)] on usb-bcm2708_usb-1.3/input0
Jan 01 00:00:04 rpi2 systemd[1]: Configuration file
/usr/lib/systemd/system/auditd.service is marked world-inaccessible.
This has no effect as configuration data is accessible via APIs
without restrictions. Proceeding anyway.
Jan 01 00:00:04 rpi2 kernel: usb 1-1.5: new low-speed USB device
number 5 using dwc_otg
Jan 01 00:00:04 rpi2 systemd[1]: Configuration file
/usr/lib/systemd/system/ebtables.service is marked executable. Please
remove executable permission bits. Proceeding anyway.
Jan 01 00:00:04 rpi2 systemd[1]: Cannot add dependency job for unit
display-manager.service, ignoring: Unit display-manager.service
failed to load: No such file or directory.
Jan 01 00:00:04 rpi2 systemd[1]: Reached target Encrypted Volumes.
Jan 01 00:00:04 rpi2 systemd[1]: Starting Encrypted Volumes.
Jan 01 00:00:04 rpi2 systemd[1]: Started Forward Password Requests to
Wall Directory Watch.
Jan 01 00:00:04 rpi2 systemd[1]: Starting Forward Password Requests
to Wall Directory Watch.
Jan 01 00:00:04 rpi2 kernel: usb 1-1.5: New USB device found,
idVendor=413c, idProduct=2105
Jan 01 00:00:04 rpi2 kernel: usb 1-1.5: New USB device strings:
Mfr=1, Product=2, SerialNumber=0
Jan 01 00:00:04 rpi2 kernel: usb 1-1.5: Product: Dell USB Keyboard
Jan 01 00:00:04 rpi2 kernel: usb 1-1.5: Manufacturer: Dell
Jan 01 00:00:04 rpi2 kernel: input: Dell Dell USB Keyboard as
/devices/platform/bcm2708_usb/usb1/1-1/1-1.5/1-1.5:1.0/0003:413C:2105.0002/input/input1
Jan 01 00:00:04 rpi2 systemd[1]: Set up automount Arbitrary
Executable File Formats File System Automount Point.
Jan 01 00:00:04 rpi2 systemd[1]: Starting Arbitrary Executable File
Formats File System Automount Point.
Jan 01 00:00:04 rpi2 kernel: hid-generic 0003:413C:2105.0002:
input,hidraw1: USB HID v1.10 Keyboard [Dell Dell USB Keyboard] on
usb-bcm2708_usb-1.5/input0
Jan 01 00:00:04 rpi2 systemd[1]: Reached target Remote File Systems.
Jan 01 00:00:04 rpi2 systemd[1]: Starting Remote File Systems.
Jan 01 00:00:04 rpi2 systemd[1]: Created slice Root Slice.
Jan 01 00:00:04 rpi2 systemd[1]: Starting Root Slice.
Jan 01 00:00:04 rpi2 systemd[1]: Listening on udev Control Socket.
Jan 01 00:00:04 rpi2 systemd[1]: Starting udev Control Socket.
Jan 01 00:00:04 rpi2 systemd[1]: Listening on Delayed Shutdown Socket.
Jan 01 00:00:04 rpi2 systemd[1]: Starting Delayed Shutdown Socket.
Jan 01 00:00:04 rpi2 systemd[1]: Created slice System Slice.
Jan 01 00:00:04 rpi2 systemd[1]: Starting System Slice.
Jan 01 00:00:04 rpi2 systemd[1]: Starting Collect Read-Ahead Data...
Jan 01 00:00:04 rpi2 systemd[1]: Started Replay Read-Ahead Data.
Jan 01 00:00:04 rpi2 systemd[1]: Created slice system-getty.slice.
Jan 01 00:00:04 rpi2 systemd[1]: Starting system-getty.slice.
Jan 01 00:00:04 rpi2 systemd[1]: Created slice system-serial\x2dgetty.slice.
Jan 01 00:00:04 rpi2 systemd[1]: Starting system-serial\x2dgetty.slice.
Jan 01 00:00:04 rpi2 systemd[1]: Created slice User and Session Slice.
Jan 01 00:00:04 rpi2 systemd[1]: Starting User and Session Slice.
Jan 01 00:00:04 rpi2 systemd[1]: Reached target Slices.
Jan 01 00:00:04 rpi2 systemd[1]: Starting Slices.
Jan 01 00:00:04 rpi2 systemd[1]: Listening on /dev/initctl
Compatibility Named Pipe.
Jan 01 00:00:04 rpi2 systemd[1]: Starting /dev/initctl Compatibility
Named Pipe.
Jan 01 00:00:04 rpi2 systemd[1]: Listening on udev Kernel Socket.
Jan 01 00:00:04 rpi2 systemd[1]: Starting udev Kernel Socket.
Jan 01 00:00:04 rpi2 systemd[1]: Listening on Journal Socket.
Jan 01 00:00:04 rpi2 systemd[1]: Starting Journal Socket.
Jan 01 00:00:04 rpi2 systemd[1]: Mounting Debug File System...
Jan 01 00:00:04 rpi2 systemd[1]: Starting Create list of required
static device nodes for the current kernel...
Jan 01 00:00:04 rpi2 systemd[1]: Mounted Huge Pages File System.
Jan 01 00:00:04 rpi2 systemd[1]: Mounting POSIX Message Queue File System...
Jan 01 00:00:04 rpi2 systemd[1]: Starting Journal Service...
Jan 01 00:00:04 rpi2 systemd[1]: Mounted POSIX Message Queue File System.
Jan 01 00:00:04 rpi2 systemd[1]: Mounted Debug File System.
Jan 01 00:00:04 rpi2 systemd[1]: Started Collect Read-Ahead Data.
Jan 01 00:00:04 rpi2 systemd[1]: Started Create list of required
static device nodes for the current kernel.
Jan 01 00:00:04 rpi2 systemd-journal[81]: 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 started up, opened the journal
-- files for writing and is now ready to process requests.
Jan 01 00:00:04 rpi2 systemd[1]: Started Journal Service.
Jan 01 00:00:04 rpi2 systemd[1]: Starting Setup Virtual Console...
-- Subject: Unit systemd-vconsole-setup.service has begun start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit systemd-vconsole-setup.service has begun starting up.
Jan 01 00:00:04 rpi2 systemd[1]: Starting Remount Root and Kernel
File Systems...
-- Subject: Unit systemd-remount-fs.service has begun start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit systemd-remount-fs.service has begun starting up.
Jan 01 00:00:04 rpi2 systemd[1]: Started Load legacy module configuration.
-- Subject: Unit rhel-loadmodules.service has finished start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit rhel-loadmodules.service has finished starting up.
--
-- The start-up result is done.
Jan 01 00:00:04 rpi2 systemd[1]: Started Set Up Additional Binary Formats.
-- Subject: Unit systemd-binfmt.service has finished start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit systemd-binfmt.service has finished starting up.
--
-- The start-up result is done.
Jan 01 00:00:04 rpi2 systemd[1]: Starting Create Static Device Nodes in /dev...
-- Subject: Unit systemd-tmpfiles-setup-dev.service has begun start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit systemd-tmpfiles-setup-dev.service has begun starting up.
Jan 01 00:00:04 rpi2 systemd[1]: Started Load Kernel Modules.
-- Subject: Unit systemd-modules-load.service has finished start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit systemd-modules-load.service has finished starting up.
--
-- The start-up result is done.
Jan 01 00:00:04 rpi2 systemd[1]: Starting Apply Kernel Variables...
-- Subject: Unit systemd-sysctl.service has begun start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit systemd-sysctl.service has begun starting up.
Jan 01 00:00:04 rpi2 systemd[1]: Mounting Configuration File System...
-- Subject: Unit sys-kernel-config.mount has begun start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit sys-kernel-config.mount has begun starting up.
Jan 01 00:00:04 rpi2 systemd[1]: Mounted FUSE Control File System.
-- Subject: Unit sys-fs-fuse-connections.mount has finished start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit sys-fs-fuse-connections.mount has finished starting up.
--
-- The start-up result is done.
Jan 01 00:00:04 rpi2 systemd[1]: Started Setup Virtual Console.
-- Subject: Unit systemd-vconsole-setup.service has finished start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit systemd-vconsole-setup.service has finished starting up.
--
-- The start-up result is done.
Jan 01 00:00:04 rpi2 systemd[1]: Started Apply Kernel Variables.
-- Subject: Unit systemd-sysctl.service has finished start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit systemd-sysctl.service has finished starting up.
--
-- The start-up result is done.
Jan 01 00:00:04 rpi2 systemd[1]: Mounted Configuration File System.
-- Subject: Unit sys-kernel-config.mount has finished start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit sys-kernel-config.mount has finished starting up.
--
-- The start-up result is done.
Jan 01 00:00:04 rpi2 systemd[1]: Started Create Static Device Nodes in /dev.
-- Subject: Unit systemd-tmpfiles-setup-dev.service has finished start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit systemd-tmpfiles-setup-dev.service has finished starting up.
--
-- The start-up result is done.
Jan 01 00:00:04 rpi2 systemd[1]: Starting udev Kernel Device Manager...
-- Subject: Unit systemd-udevd.service has begun start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit systemd-udevd.service has begun starting up.
Jan 01 00:00:04 rpi2 systemd-udevd[96]: starting version 219
Jan 01 00:00:04 rpi2 kernel: EXT4-fs (mmcblk0p3): re-mounted. Opts: (null)
Jan 01 00:00:04 rpi2 systemd[1]: Started Remount Root and Kernel File Systems.
-- Subject: Unit systemd-remount-fs.service has finished start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit systemd-remount-fs.service has finished starting up.
--
-- The start-up result is done.
Jan 01 00:00:04 rpi2 systemd[1]: Reached target Local File Systems (Pre).
-- Subject: Unit local-fs-pre.target has finished start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit local-fs-pre.target has finished starting up.
--
-- The start-up result is done.
Jan 01 00:00:04 rpi2 systemd[1]: Starting Local File Systems (Pre).
-- Subject: Unit local-fs-pre.target has begun start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit local-fs-pre.target has begun starting up.
Jan 01 00:00:04 rpi2 systemd[1]: Starting Rebuild Dynamic Linker Cache...
-- Subject: Unit ldconfig.service has begun start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit ldconfig.service has begun starting up.
Jan 01 00:00:04 rpi2 systemd[1]: Starting Load/Save Random Seed...
-- Subject: Unit systemd-random-seed.service has begun start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit systemd-random-seed.service has begun starting up.
Jan 01 00:00:04 rpi2 systemd[1]: Starting Flush Journal to Persistent
Storage...
-- Subject: Unit systemd-journal-flush.service has begun start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit systemd-journal-flush.service has begun starting up.
Jan 01 00:00:04 rpi2 systemd[1]: Starting Configure read-only root support...
-- Subject: Unit rhel-readonly.service has begun start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit rhel-readonly.service has begun starting up.
Jan 01 00:00:04 rpi2 systemd[1]: Started First Boot Wizard.
-- Subject: Unit systemd-firstboot.service has finished start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit systemd-firstboot.service has finished starting up.
--
-- The start-up result is done.
Jan 01 00:00:04 rpi2 systemd[1]: Starting Rebuild Hardware Database...
-- Subject: Unit systemd-hwdb-update.service has begun start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit systemd-hwdb-update.service has begun starting up.
Jan 01 00:00:04 rpi2 systemd[1]: Started udev Kernel Device Manager.
-- Subject: Unit systemd-udevd.service has finished start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit systemd-udevd.service has finished starting up.
--
-- The start-up result is done.
Jan 01 00:00:04 rpi2 systemd[1]: Started Load/Save Random Seed.
-- Subject: Unit systemd-random-seed.service has finished start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit systemd-random-seed.service has finished starting up.
--
-- The start-up result is done.
Jan 01 00:00:04 rpi2 systemd-journal[81]: Runtime journal is using
5.7M (max allowed 46.3M, trying to leave 69.4M free of 457.1M
available ? current limit 46.3M).
Jan 01 00:00:04 rpi2 systemd[1]: Started Flush Journal to Persistent Storage.
-- Subject: Unit systemd-journal-flush.service has finished start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit systemd-journal-flush.service has finished starting up.
--
-- The start-up result is done.
Jan 01 00:00:04 rpi2 systemd[1]: Started Configure read-only root support.
-- Subject: Unit rhel-readonly.service has finished start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit rhel-readonly.service has finished starting up.
--
-- The start-up result is done.
Jan 01 00:00:05 rpi2 kernel: random: nonblocking pool is initialized
Jan 01 00:00:05 rpi2 systemd[1]: Started Rebuild Dynamic Linker Cache.
-- Subject: Unit ldconfig.service has finished start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit ldconfig.service has finished starting up.
--
-- The start-up result is done.
Jan 01 00:00:07 rpi2 systemd[1]: Started Rebuild Hardware Database.
-- Subject: Unit systemd-hwdb-update.service has finished start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit systemd-hwdb-update.service has finished starting up.
--
-- The start-up result is done.
Jan 01 00:00:07 rpi2 systemd[1]: Starting udev Coldplug all Devices...
-- Subject: Unit systemd-udev-trigger.service has begun start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit systemd-udev-trigger.service has begun starting up.
Jan 01 00:00:07 rpi2 systemd[1]: Started udev Coldplug all Devices.
-- Subject: Unit systemd-udev-trigger.service has finished start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit systemd-udev-trigger.service has finished starting up.
--
-- The start-up result is done.
Jan 01 00:00:07 rpi2 systemd[1]: Found device /dev/ttyAMA0.
-- Subject: Unit dev-ttyAMA0.device has finished start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit dev-ttyAMA0.device has finished starting up.
--
-- The start-up result is done.
Jan 01 00:00:07 rpi2 systemd[1]: Starting Show Plymouth Boot Screen...
-- Subject: Unit plymouth-start.service has begun start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit plymouth-start.service has begun starting up.
Jan 01 00:00:07 rpi2 kernel: bcm2708_spi bcm2708_spi.0: master is
unqueued, this is deprecated
Jan 01 00:00:07 rpi2 kernel: bcm2708_spi bcm2708_spi.0: SPI
Controller at 0x3f204000 (irq 80)
Jan 01 00:00:07 rpi2 kernel: bcm2708_i2c_init_pinmode(1,2)
Jan 01 00:00:07 rpi2 kernel: bcm2708_i2c_init_pinmode(1,3)
Jan 01 00:00:07 rpi2 kernel: bcm2708_i2c bcm2708_i2c.1: BSC1
Controller at 0x3f804000 (irq 79) (baudrate 100000)
Jan 01 00:00:07 rpi2 systemd[1]: Received SIGRTMIN+20 from PID 138 (plymouthd).
Jan 01 00:00:07 rpi2 systemd[1]: Started Show Plymouth Boot Screen.
-- Subject: Unit plymouth-start.service has finished start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit plymouth-start.service has finished starting up.
--
-- The start-up result is done.
Jan 01 00:00:07 rpi2 systemd[1]: Started Forward Password Requests to
Plymouth Directory Watch.
-- Subject: Unit systemd-ask-password-plymouth.path has finished start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit systemd-ask-password-plymouth.path has finished starting up.
--
-- The start-up result is done.
Jan 01 00:00:07 rpi2 systemd[1]: Starting Forward Password Requests
to Plymouth Directory Watch.
-- Subject: Unit systemd-ask-password-plymouth.path has begun start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit systemd-ask-password-plymouth.path has begun starting up.
Jan 01 00:00:07 rpi2 systemd[1]: Started Dispatch Password Requests
to Console Directory Watch.
-- Subject: Unit systemd-ask-password-console.path has finished start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit systemd-ask-password-console.path has finished starting up.
--
-- The start-up result is done.
Jan 01 00:00:07 rpi2 systemd[1]: Found device /dev/disk/by-label/1BBF2D52.
-- Subject: Unit dev-disk-by\x2dlabel-1BBF2D52.device has finished start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit dev-disk-by\x2dlabel-1BBF2D52.device has finished starting up.
--
-- The start-up result is done.
Jan 01 00:00:08 rpi2 systemd[1]: Found device
/dev/disk/by-uuid/f28d9939-d00d-4e9e-aceb-1ac7b3e607ce.
-- Subject: Unit
dev-disk-by\x2duuid-f28d9939\x2dd00d\x2d4e9e\x2daceb\x2d1ac7b3e607ce.device
has finished start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit
dev-disk-by\x2duuid-f28d9939\x2dd00d\x2d4e9e\x2daceb\x2d1ac7b3e607ce.device
has finished starting up.
--
-- The start-up result is done.
Jan 01 00:00:08 rpi2 systemd[1]: Activating swap
/dev/disk/by-uuid/f28d9939-d00d-4e9e-aceb-1ac7b3e607ce...
-- Subject: Unit
dev-disk-by\x2duuid-f28d9939\x2dd00d\x2d4e9e\x2daceb\x2d1ac7b3e607ce.swap
has begun start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit
dev-disk-by\x2duuid-f28d9939\x2dd00d\x2d4e9e\x2daceb\x2d1ac7b3e607ce.swap
has begun starting up.
Jan 01 00:00:08 rpi2 systemd[1]: Mounting /boot...
-- Subject: Unit boot.mount has begun start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit boot.mount has begun starting up.
Jan 01 00:00:08 rpi2 kernel: Adding 524284k swap on
/dev/mmcblk0p2. Priority:-1 extents:1 across:524284k SSFS
Jan 01 00:00:08 rpi2 systemd[1]: Activated swap
/dev/disk/by-uuid/f28d9939-d00d-4e9e-aceb-1ac7b3e607ce.
-- Subject: Unit
dev-disk-by\x2duuid-f28d9939\x2dd00d\x2d4e9e\x2daceb\x2d1ac7b3e607ce.swap
has finished start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit
dev-disk-by\x2duuid-f28d9939\x2dd00d\x2d4e9e\x2daceb\x2d1ac7b3e607ce.swap
has finished starting up.
--
-- The start-up result is done.
Jan 01 00:00:08 rpi2 systemd[1]: Mounted /boot.
-- Subject: Unit boot.mount has finished start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit boot.mount has finished starting up.
--
-- The start-up result is done.
Jan 01 00:00:08 rpi2 kernel: wm8804 1-003b: Failed to read device ID: -5
Jan 01 00:00:08 rpi2 kernel: wm8804: probe of 1-003b failed with error -5
Jan 01 00:00:08 rpi2 systemd[1]: Reached target Local File Systems.
-- Subject: Unit local-fs.target has finished start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit local-fs.target has finished starting up.
--
-- The start-up result is done.
Jan 01 00:00:08 rpi2 systemd[1]: Starting Local File Systems.
-- Subject: Unit local-fs.target has begun start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit local-fs.target has begun starting up.
Jan 01 00:00:08 rpi2 systemd[1]: Started Reconfigure the system on
administrator request.
-- Subject: Unit rhel-configure.service has finished start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit rhel-configure.service has finished starting up.
--
-- The start-up result is done.
Jan 01 00:00:08 rpi2 systemd[1]: Starting Tell Plymouth To Write Out
Runtime Data...
-- Subject: Unit plymouth-read-write.service has begun start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit plymouth-read-write.service has begun starting up.
Jan 01 00:00:08 rpi2 systemd[1]: Started Import network configuration
from initramfs.
-- Subject: Unit rhel-import-state.service has finished start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit rhel-import-state.service has finished starting up.
--
-- The start-up result is done.
Jan 01 00:00:08 rpi2 systemd[1]: Started Commit a transient machine-id on disk.
-- Subject: Unit systemd-machine-id-commit.service has finished start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit systemd-machine-id-commit.service has finished starting up.
--
-- The start-up result is done.
Jan 01 00:00:08 rpi2 systemd[1]: Starting Create Volatile Files and
Directories...
-- Subject: Unit systemd-tmpfiles-setup.service has begun start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit systemd-tmpfiles-setup.service has begun starting up.
Jan 01 00:00:08 rpi2 kernel: pcm512x 1-004d: Failed to reset device: -5
Jan 01 00:00:08 rpi2 kernel: pcm512x: probe of 1-004d failed with error -5
Jan 01 00:00:08 rpi2 kernel: pcm512x 1-004c: Failed to reset device: -5
Jan 01 00:00:08 rpi2 kernel: pcm512x: probe of 1-004c failed with error -5
Jan 01 00:00:08 rpi2 systemd[1]: Starting Mark the need to relabel
after reboot...
-- Subject: Unit rhel-autorelabel-mark.service has begun start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit rhel-autorelabel-mark.service has begun starting up.
Jan 01 00:00:08 rpi2 systemd[1]: Started Relabel all filesystems, if necessary.
-- Subject: Unit rhel-autorelabel.service has finished start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit rhel-autorelabel.service has finished starting up.
--
-- The start-up result is done.
Jan 01 00:00:08 rpi2 systemd[1]: Starting Rebuild Journal Catalog...
-- Subject: Unit systemd-journal-catalog-update.service has begun start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit systemd-journal-catalog-update.service has begun starting up.
Jan 01 00:00:08 rpi2 systemd[1]: Reached target Swap.
-- Subject: Unit swap.target has finished start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit swap.target has finished starting up.
--
-- The start-up result is done.
Jan 01 00:00:08 rpi2 systemd[1]: Starting Swap.
-- Subject: Unit swap.target has begun start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit swap.target has begun starting up.
Jan 01 00:00:08 rpi2 systemd[1]: Started Create Volatile Files and Directories.
-- Subject: Unit systemd-tmpfiles-setup.service has finished start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit systemd-tmpfiles-setup.service has finished starting up.
--
-- The start-up result is done.
Jan 01 00:00:08 rpi2 systemd[1]: Started Mark the need to relabel after reboot.
-- Subject: Unit rhel-autorelabel-mark.service has finished start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit rhel-autorelabel-mark.service has finished starting up.
--
-- The start-up result is done.
Jan 01 00:00:08 rpi2 systemd[1]: Started Tell Plymouth To Write Out
Runtime Data.
-- Subject: Unit plymouth-read-write.service has finished start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit plymouth-read-write.service has finished starting up.
--
-- The start-up result is done.
Jan 01 00:00:08 rpi2 systemd[1]: Started Rebuild Journal Catalog.
-- Subject: Unit systemd-journal-catalog-update.service has finished start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit systemd-journal-catalog-update.service has finished starting up.
--
-- The start-up result is done.
Jan 01 00:00:08 rpi2 systemd[1]: Starting Update is Completed...
-- Subject: Unit systemd-update-done.service has begun start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit systemd-update-done.service has begun starting up.
Jan 01 00:00:08 rpi2 systemd[1]: Starting Security Auditing Service...
-- Subject: Unit auditd.service has begun start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit auditd.service has begun starting up.
Jan 01 00:00:08 rpi2 systemd[1]: Started Update is Completed.
-- Subject: Unit systemd-update-done.service has finished start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit systemd-update-done.service has finished starting up.
--
-- The start-up result is done.
Jan 01 00:00:08 rpi2 auditd[164]: Error - audit support not in kernel
Jan 01 00:00:08 rpi2 auditd[164]: Cannot open netlink audit socket
Jan 01 00:00:08 rpi2 auditd[164]: The audit daemon is exiting.
Jan 01 00:00:08 rpi2 systemd[1]: auditd.service: main process exited,
code=exited, status=1/FAILURE
Jan 01 00:00:08 rpi2 augenrules[165]: Error - audit support not in kernel
Jan 01 00:00:08 rpi2 augenrules[165]: Error - audit support not in kernel
Jan 01 00:00:08 rpi2 augenrules[165]: Cannot open netlink audit socket
Jan 01 00:00:08 rpi2 systemd[1]: Failed to start Security Auditing Service.
-- Subject: Unit auditd.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit auditd.service has failed.
--
-- The result is failed.
Jan 01 00:00:08 rpi2 systemd[1]: Unit auditd.service entered failed state.
Jan 01 00:00:08 rpi2 systemd[1]: auditd.service failed.
Jan 01 00:00:08 rpi2 systemd[1]: Starting Update UTMP about System
Boot/Shutdown...
-- Subject: Unit systemd-update-utmp.service has begun start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit systemd-update-utmp.service has begun starting up.
Jan 01 00:00:08 rpi2 systemd[1]: Started Update UTMP about System
Boot/Shutdown.
-- Subject: Unit systemd-update-utmp.service has finished start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit systemd-update-utmp.service has finished starting up.
--
-- The start-up result is done.
Jan 01 00:00:08 rpi2 systemd[1]: Reached target System Initialization.
-- Subject: Unit sysinit.target has finished start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit sysinit.target has finished starting up.
--
-- The start-up result is done.
Jan 01 00:00:08 rpi2 systemd[1]: Starting System Initialization.
-- Subject: Unit sysinit.target has begun start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit sysinit.target has begun starting up.
Jan 01 00:00:08 rpi2 systemd[1]: Started Flexible branding.
-- Subject: Unit brandbot.path has finished start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit brandbot.path has finished starting up.
--
-- The start-up result is done.
Jan 01 00:00:08 rpi2 systemd[1]: Starting Flexible branding.
-- Subject: Unit brandbot.path has begun start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit brandbot.path has begun starting up.
Jan 01 00:00:08 rpi2 systemd[1]: Reached target Paths.
-- Subject: Unit paths.target has finished start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit paths.target has finished starting up.
--
-- The start-up result is done.
Jan 01 00:00:08 rpi2 systemd[1]: Starting Paths.
-- Subject: Unit paths.target has begun start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit paths.target has begun starting up.
Jan 01 00:00:08 rpi2 systemd[1]: Started Daily Cleanup of Temporary
Directories.
-- Subject: Unit systemd-tmpfiles-clean.timer has finished start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit systemd-tmpfiles-clean.timer has finished starting up.
--
-- The start-up result is done.
Jan 01 00:00:08 rpi2 systemd[1]: Starting Daily Cleanup of Temporary
Directories.
-- Subject: Unit systemd-tmpfiles-clean.timer has begun start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit systemd-tmpfiles-clean.timer has begun starting up.
Jan 01 00:00:08 rpi2 systemd[1]: Reached target Timers.
-- Subject: Unit timers.target has finished start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit timers.target has finished starting up.
--
-- The start-up result is done.
Jan 01 00:00:08 rpi2 systemd[1]: Starting Timers.
-- Subject: Unit timers.target has begun start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit timers.target has begun starting up.
Jan 01 00:00:08 rpi2 systemd[1]: Listening on D-Bus System Message Bus Socket.
-- Subject: Unit dbus.socket has finished start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit dbus.socket has finished starting up.
--
-- The start-up result is done.
Jan 01 00:00:08 rpi2 systemd[1]: Starting D-Bus System Message Bus Socket.
-- Subject: Unit dbus.socket has begun start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit dbus.socket has begun starting up.
Jan 01 00:00:08 rpi2 systemd[1]: Reached target Sockets.
-- Subject: Unit sockets.target has finished start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit sockets.target has finished starting up.
--
-- The start-up result is done.
Jan 01 00:00:08 rpi2 systemd[1]: Starting Sockets.
-- Subject: Unit sockets.target has begun start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit sockets.target has begun starting up.
Jan 01 00:00:08 rpi2 systemd[1]: Reached target Basic System.
-- Subject: Unit basic.target has finished start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit basic.target has finished starting up.
--
-- The start-up result is done.
Jan 01 00:00:08 rpi2 systemd[1]: Starting Basic System.
-- Subject: Unit basic.target has begun start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit basic.target has begun starting up.
Jan 01 00:00:08 rpi2 systemd[1]: Started irqbalance daemon.
-- Subject: Unit irqbalance.service has finished start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit irqbalance.service has finished starting up.
--
-- The start-up result is done.
Jan 01 00:00:08 rpi2 systemd[1]: Starting irqbalance daemon...
-- Subject: Unit irqbalance.service has begun start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit irqbalance.service has begun starting up.
Jan 01 00:00:08 rpi2 systemd[1]: Starting firewalld - dynamic
firewall daemon...
-- Subject: Unit firewalld.service has begun start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit firewalld.service has begun starting up.
Jan 01 00:00:08 rpi2 systemd[1]: Started D-Bus System Message Bus.
-- Subject: Unit dbus.service has finished start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit dbus.service has finished starting up.
--
-- The start-up result is done.
Jan 01 00:00:09 rpi2 systemd[1]: Starting D-Bus System Message Bus...
-- Subject: Unit dbus.service has begun start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit dbus.service has begun starting up.
Jan 01 00:00:09 rpi2 systemd[1]: Starting Permit User Sessions...
-- Subject: Unit systemd-user-sessions.service has begun start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit systemd-user-sessions.service has begun starting up.
Jan 01 00:00:09 rpi2 systemd[1]: Starting System Logging Service...
-- Subject: Unit rsyslog.service has begun start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit rsyslog.service has begun starting up.
Jan 01 00:00:09 rpi2 systemd[1]: Starting OpenSSH Server Key Generation...
-- Subject: Unit sshd-keygen.service has begun start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit sshd-keygen.service has begun starting up.
Jan 01 00:00:09 rpi2 systemd[1]: Starting Root Filesystem Auto-Resizer...
-- Subject: Unit rootfs-resize.service has begun start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit rootfs-resize.service has begun starting up.
Jan 01 00:00:09 rpi2 systemd[1]: Starting Login Service...
-- Subject: Unit systemd-logind.service has begun start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit systemd-logind.service has begun starting up.
Jan 01 00:00:09 rpi2 systemd[1]: Starting Dump dmesg to /var/log/dmesg...
-- Subject: Unit rhel-dmesg.service has begun start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit rhel-dmesg.service has begun starting up.
Jan 01 00:00:09 rpi2 systemd[1]: Started Permit User Sessions.
-- Subject: Unit systemd-user-sessions.service has finished start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit systemd-user-sessions.service has finished starting up.
--
-- The start-up result is done.
Jan 01 00:00:09 rpi2 systemd[1]: Starting Terminate Plymouth Boot Screen...
-- Subject: Unit plymouth-quit.service has begun start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit plymouth-quit.service has begun starting up.
Jan 01 00:00:09 rpi2 systemd[1]: Starting Wait for Plymouth Boot
Screen to Quit...
-- Subject: Unit plymouth-quit-wait.service has begun start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit plymouth-quit-wait.service has begun starting up.
Jan 01 00:00:09 rpi2 systemd[1]: Started Command Scheduler.
-- Subject: Unit crond.service has finished start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit crond.service has finished starting up.
--
-- The start-up result is done.
Jan 01 00:00:09 rpi2 systemd[1]: Starting Command Scheduler...
-- Subject: Unit crond.service has begun start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit crond.service has begun starting up.
Jan 01 00:00:09 rpi2 systemd[1]: Received SIGRTMIN+21 from PID 138 (plymouthd).
Jan 01 00:00:09 rpi2 systemd[1]: Started Dump dmesg to /var/log/dmesg.
-- Subject: Unit rhel-dmesg.service has finished start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit rhel-dmesg.service has finished starting up.
--
-- The start-up result is done.
Jan 01 00:00:09 rpi2 crond[208]: (CRON) INFO (RANDOM_DELAY will be
scaled with factor 67% if used.)
Jan 01 00:00:09 rpi2 systemd[1]: Started Terminate Plymouth Boot Screen.
-- Subject: Unit plymouth-quit.service has finished start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit plymouth-quit.service has finished starting up.
--
-- The start-up result is done.
Jan 01 00:00:09 rpi2 systemd[1]: Started Wait for Plymouth Boot Screen to Quit.
-- Subject: Unit plymouth-quit-wait.service has finished start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit plymouth-quit-wait.service has finished starting up.
--
-- The start-up result is done.
Jan 01 00:00:09 rpi2 crond[208]: (CRON) INFO (running with inotify support)
Jan 01 00:00:09 rpi2 systemd[1]: Started Serial Getty on ttyAMA0.
-- Subject: Unit serial-getty(a)ttyAMA0.service has finished start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit serial-getty(a)ttyAMA0.service has finished starting up.
--
-- The start-up result is done.
Jan 01 00:00:09 rpi2 systemd[1]: Starting Serial Getty on ttyAMA0...
-- Subject: Unit serial-getty(a)ttyAMA0.service has begun start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit serial-getty(a)ttyAMA0.service has begun starting up.
Jan 01 00:00:09 rpi2 systemd[1]: Started Getty on tty1.
-- Subject: Unit getty(a)tty1.service has finished start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit getty(a)tty1.service has finished starting up.
--
-- The start-up result is done.
Jan 01 00:00:09 rpi2 systemd[1]: Starting Getty on tty1...
-- Subject: Unit getty(a)tty1.service has begun start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit getty(a)tty1.service has begun starting up.
Jan 01 00:00:09 rpi2 systemd[1]: Reached target Login Prompts.
-- Subject: Unit getty.target has finished start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit getty.target has finished starting up.
--
-- The start-up result is done.
Jan 01 00:00:09 rpi2 systemd[1]: Starting Login Prompts.
-- Subject: Unit getty.target has begun start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit getty.target has begun starting up.
Jan 01 00:00:09 rpi2 systemd[1]: Started Login Service.
-- Subject: Unit systemd-logind.service has finished start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit systemd-logind.service has finished starting up.
--
-- The start-up result is done.
Jan 01 00:00:09 rpi2 systemd-logind[201]: 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.
Jan 01 00:00:09 rpi2 systemd[1]: Started System Logging Service.
-- Subject: Unit rsyslog.service has finished start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit rsyslog.service has finished starting up.
--
-- The start-up result is done.
Jan 01 00:00:10 rpi2 systemd[1]: Started Root Filesystem Auto-Resizer.
-- Subject: Unit rootfs-resize.service has finished start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit rootfs-resize.service has finished starting up.
--
-- The start-up result is done.
Jan 01 00:00:11 rpi2 kernel: nf_conntrack version 0.5.0 (14815
buckets, 59260 max)
Jan 01 00:00:11 rpi2 kernel: ip6_tables: (C) 2000-2006 Netfilter Core Team
Jan 01 00:00:11 rpi2 kernel: Ebtables v2.0 registered
Jan 01 00:00:11 rpi2 kernel: bridge: automatic filtering via
arp/ip/ip6tables has been deprecated. Update your scripts to load
br_netfilter if you need this.
Jan 01 00:00:12 rpi2 systemd[1]: Started firewalld - dynamic firewall daemon.
-- Subject: Unit firewalld.service has finished start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit firewalld.service has finished starting up.
--
-- The start-up result is done.
Jan 01 00:00:12 rpi2 systemd[1]: Starting Network Manager...
-- Subject: Unit NetworkManager.service has begun start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit NetworkManager.service has begun starting up.
Jan 01 00:00:12 rpi2 NetworkManager[269]: <info> NetworkManager
(version 1.0.6-27.el7) is starting...
Jan 01 00:00:12 rpi2 NetworkManager[269]: <info> Read config:
/etc/NetworkManager/NetworkManager.conf and conf.d: 10-ibft-plugin.conf
Jan 01 00:00:12 rpi2 systemd[1]: Started Network Manager.
-- Subject: Unit NetworkManager.service has finished start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit NetworkManager.service has finished starting up.
--
-- The start-up result is done.
Jan 01 00:00:12 rpi2 systemd[1]: Starting Network Manager Wait Online...
-- Subject: Unit NetworkManager-wait-online.service has begun start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit NetworkManager-wait-online.service has begun starting up.
Jan 01 00:00:13 rpi2 NetworkManager[269]: <info> Loaded settings
plugin ifcfg-rh: (c) 2007 - 2015 Red Hat, Inc. To report bugs please
use the NetworkManager mailing list.
(/usr/lib/NetworkManager/libnm-settings-plugin-ifcfg-rh.so)
Jan 01 00:00:13 rpi2 NetworkManager[269]: <info> Loaded settings
plugin iBFT: (c) 2014 Red Hat, Inc. To report bugs please use the
NetworkManager mailing list.
(/usr/lib/NetworkManager/libnm-settings-plugin-ibft.so)
Jan 01 00:00:13 rpi2 NetworkManager[269]: <info> Loaded settings
plugin keyfile: (c) 2007 - 2015 Red Hat, Inc. To report bugs please
use the NetworkManager mailing list.
Jan 01 00:00:13 rpi2 NetworkManager[269]: <info> ifcfg-rh: new
connection /etc/sysconfig/network-scripts/ifcfg-eth0
(0cb1274f-af94-4a51-a5bc-7608a1e37d63,"eth0")
Jan 01 00:00:13 rpi2 NetworkManager[269]: <info> monitoring kernel
firmware directory '/lib/firmware'.
Jan 01 00:00:13 rpi2 NetworkManager[269]: <info> Loaded device
plugin: NMVxlanFactory (internal)
Jan 01 00:00:13 rpi2 NetworkManager[269]: <info> Loaded device
plugin: NMVlanFactory (internal)
Jan 01 00:00:13 rpi2 NetworkManager[269]: <info> Loaded device
plugin: NMVethFactory (internal)
Jan 01 00:00:13 rpi2 NetworkManager[269]: <info> Loaded device
plugin: NMTunFactory (internal)
Jan 01 00:00:13 rpi2 NetworkManager[269]: <info> Loaded device
plugin: NMMacvlanFactory (internal)
Jan 01 00:00:13 rpi2 NetworkManager[269]: <info> Loaded device
plugin: NMInfinibandFactory (internal)
Jan 01 00:00:13 rpi2 NetworkManager[269]: <info> Loaded device
plugin: NMGreFactory (internal)
Jan 01 00:00:13 rpi2 NetworkManager[269]: <info> Loaded device
plugin: NMEthernetFactory (internal)
Jan 01 00:00:13 rpi2 NetworkManager[269]: <info> Loaded device
plugin: NMBridgeFactory (internal)
Jan 01 00:00:13 rpi2 NetworkManager[269]: <info> Loaded device
plugin: NMBondFactory (internal)
Jan 01 00:00:13 rpi2 NetworkManager[269]: <info> Loaded device
plugin: NMTeamFactory (/usr/lib/NetworkManager/libnm-device-plugin-team.so)
Jan 01 00:00:13 rpi2 NetworkManager[269]: <info> Loaded device
plugin: NMWifiFactory (/usr/lib/NetworkManager/libnm-device-plugin-wifi.so)
Jan 01 00:00:13 rpi2 NetworkManager[269]: <info> WiFi enabled by
radio killswitch; enabled by state file
Jan 01 00:00:13 rpi2 NetworkManager[269]: <info> WWAN enabled by
radio killswitch; enabled by state file
Jan 01 00:00:13 rpi2 NetworkManager[269]: <info> WiMAX enabled by
radio killswitch; enabled by state file
Jan 01 00:00:13 rpi2 NetworkManager[269]: <info> Networking is
enabled by state file
Jan 01 00:00:13 rpi2 NetworkManager[269]: <info> (lo): link connected
Jan 01 00:00:13 rpi2 NetworkManager[269]: <info> (lo): new Generic
device (carrier: ON, driver: 'unknown', ifindex: 1)
Jan 01 00:00:13 rpi2 NetworkManager[269]: <info> (eth0): new
Ethernet device (carrier: OFF, driver: 'smsc95xx', ifindex: 2)
Jan 01 00:00:13 rpi2 NetworkManager[269]: <info> (eth0): device
state change: unmanaged -> unavailable (reason 'managed') [10 20 2]
Jan 01 00:00:13 rpi2 kernel: IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
Jan 01 00:00:13 rpi2 kernel: smsc95xx 1-1.1:1.0 eth0: hardware isn't
capable of remote wakeup
Jan 01 00:00:13 rpi2 kernel: IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
Jan 01 00:00:13 rpi2 dbus[193]: [system] Activating via systemd:
service name='org.freedesktop.PolicyKit1' unit='polkit.service'
Jan 01 00:00:13 rpi2 dbus-daemon[193]: dbus[193]: [system] Activating
via systemd: service name='org.freedesktop.PolicyKit1' unit='polkit.service'
Jan 01 00:00:13 rpi2 systemd[1]: Starting Authorization Manager...
-- Subject: Unit polkit.service has begun start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit polkit.service has begun starting up.
Jan 01 00:00:13 rpi2 dbus[193]: [system] Activating via systemd:
service name='fi.w1.wpa_supplicant1' unit='wpa_supplicant.service'
Jan 01 00:00:13 rpi2 systemd[1]: Configuration file
/usr/lib/systemd/system/wpa_supplicant.service is marked executable.
Please remove executable permission bits. Proceeding anyway.
Jan 01 00:00:13 rpi2 dbus-daemon[193]: dbus[193]: [system] Activating
via systemd: service name='fi.w1.wpa_supplicant1' unit='wpa_supplicant.service'
Jan 01 00:00:13 rpi2 systemd[1]: Starting WPA Supplicant daemon...
-- Subject: Unit wpa_supplicant.service has begun start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit wpa_supplicant.service has begun starting up.
Jan 01 00:00:13 rpi2 dbus[193]: [system] Successfully activated
service 'fi.w1.wpa_supplicant1'
Jan 01 00:00:13 rpi2 dbus-daemon[193]: dbus[193]: [system]
Successfully activated service 'fi.w1.wpa_supplicant1'
Jan 01 00:00:13 rpi2 systemd[1]: Started WPA Supplicant daemon.
-- Subject: Unit wpa_supplicant.service has finished start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit wpa_supplicant.service has finished starting up.
--
-- The start-up result is done.
Jan 01 00:00:13 rpi2 NetworkManager[269]: <info> wpa_supplicant running
Jan 01 00:00:13 rpi2 polkitd[319]: Started polkitd version 0.112
Jan 01 00:00:13 rpi2 polkitd[319]: Loading rules from directory
/etc/polkit-1/rules.d
Jan 01 00:00:13 rpi2 polkitd[319]: Loading rules from directory
/usr/share/polkit-1/rules.d
Jan 01 00:00:14 rpi2 polkitd[319]: Finished loading, compiling and
executing 2 rules
Jan 01 00:00:14 rpi2 dbus[193]: [system] Successfully activated
service 'org.freedesktop.PolicyKit1'
Jan 01 00:00:14 rpi2 dbus-daemon[193]: dbus[193]: [system]
Successfully activated service 'org.freedesktop.PolicyKit1'
Jan 01 00:00:14 rpi2 systemd[1]: Started Authorization Manager.
-- Subject: Unit polkit.service has finished start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit polkit.service has finished starting up.
--
-- The start-up result is done.
Jan 01 00:00:14 rpi2 polkitd[319]: Acquired the name
org.freedesktop.PolicyKit1 on the system bus
Jan 01 00:00:14 rpi2 kernel: smsc95xx 1-1.1:1.0 eth0: link up,
100Mbps, full-duplex, lpa 0x4DE1
Jan 01 00:00:14 rpi2 kernel: IPv6: ADDRCONF(NETDEV_CHANGE): eth0:
link becomes ready
Jan 01 00:00:14 rpi2 NetworkManager[269]: <info> (eth0): link connected
Jan 01 00:00:14 rpi2 NetworkManager[269]: <info> (eth0): device
state change: unavailable -> disconnected (reason 'carrier-changed') [20 30 40]
Jan 01 00:00:14 rpi2 NetworkManager[269]: <info> Auto-activating
connection 'eth0'.
Jan 01 00:00:14 rpi2 NetworkManager[269]: <info> (eth0): Activation:
starting connection 'eth0' (0cb1274f-af94-4a51-a5bc-7608a1e37d63)
Jan 01 00:00:14 rpi2 NetworkManager[269]: <info> (eth0): device
state change: disconnected -> prepare (reason 'none') [30 40 0]
Jan 01 00:00:14 rpi2 NetworkManager[269]: <info> NetworkManager
state is now CONNECTING
Jan 01 00:00:14 rpi2 NetworkManager[269]: <info> (eth0): device
state change: prepare -> config (reason 'none') [40 50 0]
Jan 01 00:00:18 rpi2 NetworkManager[269]: <info> (eth0): device
state change: config -> ip-config (reason 'none') [50 70 0]
Jan 01 00:00:18 rpi2 NetworkManager[269]: <info> Activation (eth0)
Beginning DHCPv4 transaction (timeout in 45 seconds)
Jan 01 00:00:19 rpi2 NetworkManager[269]: <info> dhclient started with pid 564
Jan 01 00:00:19 rpi2 dhclient[564]: DHCPDISCOVER on eth0 to
255.255.255.255 port 67 interval 3 (xid=0x58650026)
Jan 01 00:00:19 rpi2 dhclient[564]: DHCPREQUEST on eth0 to
255.255.255.255 port 67 (xid=0x58650026)
Jan 01 00:00:19 rpi2 dhclient[564]: DHCPOFFER from 192.168.155.2
Jan 01 00:00:19 rpi2 dhclient[564]: DHCPACK from 192.168.155.2 (xid=0x58650026)
Jan 01 00:00:19 rpi2 dhclient[564]: suspect value in | option - discarded
Jan 01 00:00:19 rpi2 NetworkManager[269]: <info> address 192.168.155.116
Jan 01 00:00:19 rpi2 dhclient[564]: bound to 192.168.155.116 --
renewal in 898 seconds.
Jan 01 00:00:19 rpi2 NetworkManager[269]: <info> plen 24 (255.255.255.0)
Jan 01 00:00:19 rpi2 NetworkManager[269]: <info> gateway 192.168.155.2
Jan 01 00:00:19 rpi2 NetworkManager[269]: <info> server identifier
192.168.155.2
Jan 01 00:00:19 rpi2 NetworkManager[269]: <info> lease time 1800
Jan 01 00:00:19 rpi2 NetworkManager[269]: <info> nameserver '192.168.155.2'
Jan 01 00:00:19 rpi2 NetworkManager[269]: <info> domain name 'daku.org'
Jan 01 00:00:19 rpi2 NetworkManager[269]: <info> (eth0): DHCPv4
state changed unknown -> bound
Jan 01 00:00:19 rpi2 NetworkManager[269]: <info> (eth0): device
state change: ip-config -> ip-check (reason 'none') [70 80 0]
Jan 01 00:00:19 rpi2 NetworkManager[269]: <info> (eth0): device
state change: ip-check -> secondaries (reason 'none') [80 90 0]
Jan 01 00:00:19 rpi2 NetworkManager[269]: <info> (eth0): device
state change: secondaries -> activated (reason 'none') [90 100 0]
Jan 01 00:00:19 rpi2 NetworkManager[269]: <info> NetworkManager
state is now CONNECTED_LOCAL
Jan 01 00:00:19 rpi2 NetworkManager[269]: <info> NetworkManager
state is now CONNECTED_GLOBAL
Jan 01 00:00:19 rpi2 NetworkManager[269]: <info> Policy set 'eth0'
(eth0) as default for IPv4 routing and DNS.
Jan 01 00:00:19 rpi2 NetworkManager[269]: <info> (eth0): Activation:
successful, device activated.
Jan 01 00:00:19 rpi2 dbus[193]: [system] Activating via systemd:
service name='org.freedesktop.nm_dispatcher'
unit='dbus-org.freedesktop.nm-dispatcher.service'
Jan 01 00:00:19 rpi2 dbus-daemon[193]: dbus[193]: [system] Activating
via systemd: service name='org.freedesktop.nm_dispatcher'
unit='dbus-org.freedesktop.nm-dispatcher.service'
Jan 01 00:00:19 rpi2 systemd[1]: Starting Network Manager Script
Dispatcher Service...
-- Subject: Unit NetworkManager-dispatcher.service has begun start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit NetworkManager-dispatcher.service has begun starting up.
Jan 01 00:00:19 rpi2 sshd-keygen[199]: Generating SSH2 RSA host key: [ OK ]
Jan 01 00:00:19 rpi2 dbus[193]: [system] Successfully activated
service 'org.freedesktop.nm_dispatcher'
Jan 01 00:00:19 rpi2 systemd[1]: Started Network Manager Script
Dispatcher Service.
-- Subject: Unit NetworkManager-dispatcher.service has finished start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit NetworkManager-dispatcher.service has finished starting up.
--
-- The start-up result is done.
Jan 01 00:00:19 rpi2 dbus-daemon[193]: dbus[193]: [system]
Successfully activated service 'org.freedesktop.nm_dispatcher'
Jan 01 00:00:19 rpi2 nm-dispatcher[571]: Dispatching action 'up' for eth0
Jan 01 00:00:19 rpi2 sshd-keygen[199]: Generating SSH2 ECDSA host key: [ OK ]
Jan 01 00:00:19 rpi2 sshd-keygen[199]: Generating SSH2 ED25519 host
key: [ OK ]
Jan 01 00:00:19 rpi2 systemd[1]: Started OpenSSH Server Key Generation.
-- Subject: Unit sshd-keygen.service has finished start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit sshd-keygen.service has finished starting up.
--
-- The start-up result is done.
Jan 01 00:00:20 rpi2 NetworkManager[269]: <info> startup complete
Jan 01 00:00:20 rpi2 systemd[1]: Started Network Manager Wait Online.
-- Subject: Unit NetworkManager-wait-online.service has finished start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit NetworkManager-wait-online.service has finished starting up.
--
-- The start-up result is done.
Jan 01 00:00:20 rpi2 systemd[1]: Starting LSB: Bring up/down networking...
-- Subject: Unit network.service has begun start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit network.service has begun starting up.
Jan 01 00:00:20 rpi2 systemd[1]: network.service: control process
exited, code=exited status=6
Jan 01 00:00:20 rpi2 systemd[1]: Failed to start LSB: Bring up/down networking.
-- Subject: Unit network.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit network.service has failed.
--
-- The result is failed.
Jan 01 00:00:20 rpi2 systemd[1]: Unit network.service entered failed state.
Jan 01 00:00:20 rpi2 systemd[1]: network.service failed.
Jan 01 00:00:20 rpi2 systemd[1]: Reached target Network.
-- Subject: Unit network.target has finished start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit network.target has finished starting up.
--
-- The start-up result is done.
Jan 01 00:00:20 rpi2 systemd[1]: Starting Network.
-- Subject: Unit network.target has begun start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit network.target has begun starting up.
Jan 01 00:00:20 rpi2 systemd[1]: Started OpenSSH server daemon.
-- Subject: Unit sshd.service has finished start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit sshd.service has finished starting up.
--
-- The start-up result is done.
Jan 01 00:00:20 rpi2 systemd[1]: Starting OpenSSH server daemon...
-- Subject: Unit sshd.service has begun start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit sshd.service has begun starting up.
Jan 01 00:00:20 rpi2 systemd[1]: Starting Postfix Mail Transport Agent...
-- Subject: Unit postfix.service has begun start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit postfix.service has begun starting up.
Jan 01 00:00:20 rpi2 systemd[1]: Reached target Network is Online.
-- Subject: Unit network-online.target has finished start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit network-online.target has finished starting up.
--
-- The start-up result is done.
Jan 01 00:00:20 rpi2 systemd[1]: Starting Network is Online.
-- Subject: Unit network-online.target has begun start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit network-online.target has begun starting up.
Jan 01 00:00:20 rpi2 systemd[1]: Starting Crash recovery kernel arming...
-- Subject: Unit kdump.service has begun start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit kdump.service has begun starting up.
Jan 01 00:00:20 rpi2 systemd[1]: Starting Dynamic System Tuning Daemon...
-- Subject: Unit tuned.service has begun start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit tuned.service has begun starting up.
Jan 01 00:00:20 rpi2 sshd[605]: Server listening on 0.0.0.0 port 22.
Jan 01 00:00:20 rpi2 sshd[605]: Server listening on :: port 22.
Jan 01 00:00:22 rpi2 systemd[1]: Started Dynamic System Tuning Daemon.
-- Subject: Unit tuned.service has finished start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit tuned.service has finished starting up.
--
-- The start-up result is done.
Jan 01 00:00:23 rpi2 kdumpctl[607]: Kdump is not supported on this kernel
Jan 01 00:00:23 rpi2 kdumpctl[607]: Starting kdump: [FAILED]
Jan 01 00:00:23 rpi2 systemd[1]: kdump.service: main process exited,
code=exited, status=1/FAILURE
Jan 01 00:00:23 rpi2 systemd[1]: Failed to start Crash recovery kernel arming.
-- Subject: Unit kdump.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit kdump.service has failed.
--
-- The result is failed.
Jan 01 00:00:23 rpi2 systemd[1]: Unit kdump.service entered failed state.
Jan 01 00:00:23 rpi2 systemd[1]: kdump.service failed.
Jan 01 00:00:24 rpi2 postfix/postfix-script[1216]: starting the
Postfix mail system
Jan 01 00:00:24 rpi2 postfix/master[1218]: daemon started -- version
2.10.1, configuration /etc/postfix
Jan 01 00:00:24 rpi2 systemd[1]: Started Postfix Mail Transport Agent.
-- Subject: Unit postfix.service has finished start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit postfix.service has finished starting up.
--
-- The start-up result is done.
Jan 01 00:00:24 rpi2 systemd[1]: Reached target Multi-User System.
-- Subject: Unit multi-user.target has finished start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit multi-user.target has finished starting up.
--
-- The start-up result is done.
Jan 01 00:00:24 rpi2 systemd[1]: Starting Multi-User System.
-- Subject: Unit multi-user.target has begun start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit multi-user.target has begun starting up.
Jan 01 00:00:24 rpi2 systemd[1]: Reached target Graphical Interface.
-- Subject: Unit graphical.target has finished start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit graphical.target has finished starting up.
--
-- The start-up result is done.
Jan 01 00:00:24 rpi2 systemd[1]: Starting Graphical Interface.
-- Subject: Unit graphical.target has begun start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit graphical.target has begun starting up.
Jan 01 00:00:24 rpi2 systemd[1]: Started Stop Read-Ahead Data
Collection 10s After Completed Startup.
-- Subject: Unit systemd-readahead-done.timer has finished start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit systemd-readahead-done.timer has finished starting up.
--
-- The start-up result is done.
Jan 01 00:00:24 rpi2 systemd[1]: Starting Stop Read-Ahead Data
Collection 10s After Completed Startup.
-- Subject: Unit systemd-readahead-done.timer has begun start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit systemd-readahead-done.timer has begun starting up.
Jan 01 00:00:24 rpi2 systemd[1]: Starting Update UTMP about System
Runlevel Changes...
-- Subject: Unit systemd-update-utmp-runlevel.service has begun start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit systemd-update-utmp-runlevel.service has begun starting up.
Jan 01 00:00:25 rpi2 systemd[1]: Started Update UTMP about System
Runlevel Changes.
-- Subject: Unit systemd-update-utmp-runlevel.service has finished start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit systemd-update-utmp-runlevel.service has finished starting up.
--
-- The start-up result is done.
Jan 01 00:00:25 rpi2 systemd[1]: Startup finished in 2.388s (kernel)
+ 22.636s (userspace) = 25.025s.
-- 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 2388988 microseconds.
--
-- Initial RAM disk start-up required INITRD_USEC microseconds.
--
-- Userspace start-up required 22636223 microseconds.
Jan 01 00:00:49 rpi2 login[214]: pam_unix(login:account): account
root has password changed in future
Jan 01 00:00:49 rpi2 systemd[1]: Created slice user-0.slice.
-- Subject: Unit user-0.slice has finished start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit user-0.slice has finished starting up.
--
-- The start-up result is done.
Jan 01 00:00:49 rpi2 systemd[1]: Starting user-0.slice.
-- Subject: Unit user-0.slice has begun start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit user-0.slice has begun starting up.
Jan 01 00:00:49 rpi2 systemd-logind[201]: 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 214.
Jan 01 00:00:49 rpi2 systemd[1]: Started Session c1 of user root.
-- Subject: Unit session-c1.scope has finished start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit session-c1.scope has finished starting up.
--
-- The start-up result is done.
Jan 01 00:00:49 rpi2 systemd[1]: Starting Session c1 of user root.
-- Subject: Unit session-c1.scope has begun start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit session-c1.scope has begun starting up.
Jan 01 00:00:49 rpi2 login[214]: pam_unix(login:session): session
opened for user root by LOGIN(uid=0)
Jan 01 00:00:49 rpi2 login[214]: ROOT LOGIN ON tty1
Jan 01 00:00:55 rpi2 systemd[1]: Starting Stop Read-Ahead Data Collection...
-- Subject: Unit systemd-readahead-done.service has begun start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit systemd-readahead-done.service has begun starting up.
Jan 01 00:00:55 rpi2 systemd[1]: Started Stop Read-Ahead Data Collection.
-- Subject: Unit systemd-readahead-done.service has finished start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit systemd-readahead-done.service has finished starting up.
--
-- The start-up result is done.
Jan 01 00:01:01 rpi2 crond[1255]: pam_unix(crond:account): account
root has password changed in future
Jan 01 00:01:01 rpi2 systemd[1]: Started Session c2 of user root.
-- Subject: Unit session-c2.scope has finished start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit session-c2.scope has finished starting up.
--
-- The start-up result is done.
Jan 01 00:01:01 rpi2 systemd[1]: Starting Session c2 of user root.
-- Subject: Unit session-c2.scope has begun start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit session-c2.scope has begun starting up.
Jan 01 00:01:01 rpi2 CROND[1264]: (root) CMD (run-parts /etc/cron.hourly)
Jan 01 00:01:01 rpi2 run-parts(/etc/cron.hourly)[1267]: starting 0anacron
Jan 01 00:01:01 rpi2 anacron[1273]: Anacron started on 1970-01-01
Jan 01 00:01:01 rpi2 anacron[1273]: Will run job `cron.daily' in 13 min.
Jan 01 00:01:01 rpi2 anacron[1273]: Will run job `cron.weekly' in 33 min.
Jan 01 00:01:01 rpi2 anacron[1273]: Will run job `cron.monthly' in 53 min.
Jan 01 00:01:01 rpi2 anacron[1273]: Jobs will be executed sequentially
Jan 01 00:01:01 rpi2 run-parts(/etc/cron.hourly)[1275]: finished 0anacron
Jan 01 00:01:01 rpi2 run-parts(/etc/cron.hourly)[1277]: starting
0yum-hourly.cron
Jan 01 00:01:01 rpi2 run-parts(/etc/cron.hourly)[1281]: finished
0yum-hourly.cron
Jan 01 00:02:28 rpi2 polkitd[319]: Registered Authentication Agent
for unix-process:1299:14877 (system bus name :1.12
[/usr/bin/pkttyagent --notify-fd 5 --fallback], object path
/org/freedesktop/PolicyKit1/AuthenticationAgent, locale en_US.UTF-8)
Jan 01 00:02:28 rpi2 systemd[1]: Starting LSB: Bring up/down networking...
-- Subject: Unit network.service has begun start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit network.service has begun starting up.
Jan 01 00:02:28 rpi2 systemd[1]: network.service: control process
exited, code=exited status=6
Jan 01 00:02:28 rpi2 systemd[1]: Failed to start LSB: Bring up/down networking.
-- Subject: Unit network.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit network.service has failed.
--
-- The result is failed.
Jan 01 00:02:28 rpi2 systemd[1]: Unit network.service entered failed state.
Jan 01 00:02:28 rpi2 systemd[1]: network.service failed.
Jan 01 00:02:28 rpi2 polkitd[319]: Unregistered Authentication Agent
for unix-process:1299:14877 (system bus name :1.12, object path
/org/freedesktop/PolicyKit1/AuthenticationAgent, locale en_US.UTF-8)
(disconnected from bus)