Apologies for taking so long to return to this thread, it took way longer than expected to get to the machine and get it up and running again. I also just updated the build to the latest 4.9.60.
Here is a download link to both binaries and src.rpm (download the kernel tarball from kernel.org manually to build from src.rpm): http://ftp.redsleeve.org/pub/misc/kernel/aarch64/RPMS/ http://ftp.redsleeve.org/pub/misc/kernel/aarch64/SRPMS/
To recap - I am also running with Tianocore EFI chain-loaded from u-boot, and mainling 4.9.x boots just fine on it.
No need for disabling ACPI on the kernel command line, no need to run EFI firmware as a 1st stage boot loader, it just works. Do feel free to try it - if that works for you but the distro supplied 4.5.x kernel doesn't, it seems reasonably conclusive that it is the CentOS kernel that is broken for this board.
I'd also be interested in learning whether you have any luck getting PCIe cards to work with it without problems - I haven't tried it since upgrading to 4.9.x, but certainly on 4.4.x mainline the machine used to reliably lock up as soon as the driver for the PCIe card loads.
Gordan
On Fri, Sep 22, 2017 at 12:06 PM, Jeremiah Rothschild jeremiah@franz.com wrote:
On Fri, Sep 22, 2017 at 11:59:00AM +0100, Gordan Bobic wrote:
On Fri, Sep 22, 2017 at 11:54 AM, Jeremiah Rothschild <
jeremiah@franz.com>
wrote:
On Fri, Sep 22, 2017 at 11:39:19AM +0100, Gordan Bobic wrote:
If you are interested, I'm more than happy to share my src.rpm for
4.9.x,
but won't be able to get to it before tomorrow morning as the
machine was
recently mothballed.
Thanks. I actually need to test with as new of a version as I can
because I
have been experiencing an occasional "page allocation failure" kernel panic. No idea if/when that was fixed but I figure the newest version is my
best
hope.
I've been on my own 4.9.x more or less since I got the machine, it was in 24/7 use, and I never experienced that issue. So it may be worth a cross-check with the kernel that I'm running to see whether the fault follows your machine or whether it is kernel dependent.
You're right. It would be a good extra data point. Feel free to mail me directly once you're sorted and I'll gladly check out your 4.9 build. Thanks again!
Arm-dev mailing list Arm-dev@centos.org https://lists.centos.org/mailman/listinfo/arm-dev
Arm-dev mailing list Arm-dev@centos.org https://lists.centos.org/mailman/listinfo/arm-dev
On Sat, Nov 04, 2017 at 05:37:54PM +0000, Gordan Bobic wrote:
Apologies for taking so long to return to this thread, it took way longer than expected to get to the machine and get it up and running again.
Thanks for the update & apologies as well on my delayed follow-up.
Last time I wrote the mailing list about my kernel problems, I was told (by jperrin@centos.org) that my system was not in a supported state because I was daisy-chaining Tianocore EFI via U-Boot. I was directed to flash the Tianocore firmware and remove U-Boot from the equation. Although I was skeptical of this answer, I finally was able to do this.
Unfortunately, however, this does not change behavior. I still cannot successfully boot into any kernels beyond 4.5 unless I use 'acpi=off'.
I am, interestingly enough, able to run the 4.9.60 kernel that you supplied.
So:
(1) My experience leads me to believe that it is still a possibility that a kernel related bug exists.
(2) I am confused as to why your kernel worked. I built kernel-alt-4.11.0-22.el7a from source and it fails like the others. Were there any special steps you took in building the rpm's you supplied me?
(3) Is it true that you are able to boot into the (> 4.5) distro-supplied kernels? Or have you only tried/succeeded with your custom builds?
Thanks again!
j
I also just updated the build to the latest 4.9.60.
Here is a download link to both binaries and src.rpm (download the kernel tarball from kernel.org manually to build from src.rpm): http://ftp.redsleeve.org/pub/misc/kernel/aarch64/RPMS/ http://ftp.redsleeve.org/pub/misc/kernel/aarch64/SRPMS/
To recap - I am also running with Tianocore EFI chain-loaded from u-boot, and mainling 4.9.x boots just fine on it.
No need for disabling ACPI on the kernel command line, no need to run EFI firmware as a 1st stage boot loader, it just works. Do feel free to try it - if that works for you but the distro supplied 4.5.x kernel doesn't, it seems reasonably conclusive that it is the CentOS kernel that is broken for this board.
I'd also be interested in learning whether you have any luck getting PCIe cards to work with it without problems - I haven't tried it since upgrading to 4.9.x, but certainly on 4.4.x mainline the machine used to reliably lock up as soon as the driver for the PCIe card loads.
Gordan
On Fri, Sep 22, 2017 at 12:06 PM, Jeremiah Rothschild jeremiah@franz.com wrote:
On Fri, Sep 22, 2017 at 11:59:00AM +0100, Gordan Bobic wrote:
On Fri, Sep 22, 2017 at 11:54 AM, Jeremiah Rothschild <
jeremiah@franz.com>
wrote:
On Fri, Sep 22, 2017 at 11:39:19AM +0100, Gordan Bobic wrote:
If you are interested, I'm more than happy to share my src.rpm for
4.9.x,
but won't be able to get to it before tomorrow morning as the
machine was
recently mothballed.
Thanks. I actually need to test with as new of a version as I can
because I
have been experiencing an occasional "page allocation failure" kernel panic. No idea if/when that was fixed but I figure the newest version is my
best
hope.
I've been on my own 4.9.x more or less since I got the machine, it was in 24/7 use, and I never experienced that issue. So it may be worth a cross-check with the kernel that I'm running to see whether the fault follows your machine or whether it is kernel dependent.
You're right. It would be a good extra data point. Feel free to mail me directly once you're sorted and I'll gladly check out your 4.9 build. Thanks again!
Arm-dev mailing list Arm-dev@centos.org https://lists.centos.org/mailman/listinfo/arm-dev
Arm-dev mailing list Arm-dev@centos.org https://lists.centos.org/mailman/listinfo/arm-dev
Arm-dev mailing list Arm-dev@centos.org https://lists.centos.org/mailman/listinfo/arm-dev
Jeremy,
Is this on which board? Unless you provide a log file, it is difficult to tell, but latest CentOS 7.4 (kernel 4.11) boots fine on X-Gene platforms.
I am not sure how you built kernel, but this is what you can check. To boot X-Gene using acpi, you need to enable CONFIG_ARM64_ACPI_PARKING_PROTOCOL=y. CentOS (RPM) default configuration should already have this enabled.
-Phong
+-----Original Message----- +From: Arm-dev [mailto:arm-dev-bounces@centos.org] On Behalf Of Jeremiah +Rothschild +Sent: Friday, January 26, 2018 4:35 PM +To: Conversations around CentOS on ARM hardware +Subject: Re: [Arm-dev] Kernel problems on APM X-Gene + +On Sat, Nov 04, 2017 at 05:37:54PM +0000, Gordan Bobic wrote: +> Apologies for taking so long to return to this thread, it took way +> longer than expected to get to the machine and get it up and running +again. + +Thanks for the update & apologies as well on my delayed follow-up. + +Last time I wrote the mailing list about my kernel problems, I was told +(by jperrin@centos.org) that my system was not in a supported state +because I was daisy-chaining Tianocore EFI via U-Boot. I was directed to +flash the Tianocore firmware and remove U-Boot from the equation. +Although I was skeptical of this answer, I finally was able to do this. + +Unfortunately, however, this does not change behavior. I still cannot +successfully boot into any kernels beyond 4.5 unless I use 'acpi=off'. + +I am, interestingly enough, able to run the 4.9.60 kernel that you +supplied. + +So: + +(1) My experience leads me to believe that it is still a possibility +that a kernel related bug exists. + +(2) I am confused as to why your kernel worked. I built kernel-alt- +4.11.0-22.el7a from source and it fails like the others. Were there any +special steps you took in building the rpm's you supplied me? + +(3) Is it true that you are able to boot into the (> 4.5) distro- +supplied kernels? Or have you only tried/succeeded with your custom +builds? + +Thanks again! + +j + +> I also just updated the build to the latest 4.9.60. +> +> Here is a download link to both binaries and src.rpm (download the +> kernel tarball from kernel.org manually to build from src.rpm): +> http://ftp.redsleeve.org/pub/misc/kernel/aarch64/RPMS/ +> http://ftp.redsleeve.org/pub/misc/kernel/aarch64/SRPMS/ +> +> To recap - I am also running with Tianocore EFI chain-loaded from +> u-boot, and mainling 4.9.x boots just fine on it. +> +> No need for disabling ACPI on the kernel command line, no need to run +> EFI firmware as a 1st stage boot loader, it just works. +> Do feel free to try it - if that works for you but the distro supplied +> 4.5.x kernel doesn't, it seems reasonably conclusive that it is the +> CentOS kernel that is broken for this board. +> +> I'd also be interested in learning whether you have any luck getting +> PCIe cards to work with it without problems - I haven't tried it since +> upgrading to 4.9.x, but certainly on 4.4.x mainline the machine used +> to reliably lock up as soon as the driver for the PCIe card loads. +> +> Gordan +> +> +> On Fri, Sep 22, 2017 at 12:06 PM, Jeremiah Rothschild +> jeremiah@franz.com +> wrote: +> +> > On Fri, Sep 22, 2017 at 11:59:00AM +0100, Gordan Bobic wrote: +> > > On Fri, Sep 22, 2017 at 11:54 AM, Jeremiah Rothschild < +> > jeremiah@franz.com> +> > > wrote: +> > > +> > > > On Fri, Sep 22, 2017 at 11:39:19AM +0100, Gordan Bobic wrote: +> > > > > If you are interested, I'm more than happy to share my src.rpm +> > > > > for +> > 4.9.x, +> > > > > but won't be able to get to it before tomorrow morning as the +> > machine was +> > > > > recently mothballed. +> > > > +> > > > Thanks. I actually need to test with as new of a version as I +> > > > can +> > because I +> > > > have been experiencing an occasional "page allocation failure" +> > > > kernel panic. +> > > > No idea if/when that was fixed but I figure the newest version +> > > > is my +> > best +> > > > hope. +> > > > +> > > +> > > I've been on my own 4.9.x more or less since I got the machine, it +> > > was in +> > > 24/7 use, and I never experienced that issue. So it may be worth a +> > > cross-check with the kernel that I'm running to see whether the +> > > fault follows your machine or whether it is kernel dependent. +> > +> > You're right. It would be a good extra data point. Feel free to mail +> > me directly once you're sorted and I'll gladly check out your 4.9 +build. +> > Thanks +> > again! +> > +> > +> > +> > > _______________________________________________ +> > > Arm-dev mailing list +> > > Arm-dev@centos.org +> > > https://lists.centos.org/mailman/listinfo/arm-dev +> > +> > _______________________________________________ +> > Arm-dev mailing list +> > Arm-dev@centos.org +> > https://lists.centos.org/mailman/listinfo/arm-dev +> > + +> _______________________________________________ +> Arm-dev mailing list +> Arm-dev@centos.org +> https://lists.centos.org/mailman/listinfo/arm-dev + +_______________________________________________ +Arm-dev mailing list +Arm-dev@centos.org +https://lists.centos.org/mailman/listinfo/arm-dev
On Fri, Jan 26, 2018 at 04:48:24PM +0700, Phong Vo wrote:
Jeremy,
Hi Phong. Thanks for the reply! Also, thank you for the tools & instructions to flash the Tianocore. That process worked great. :)
Is this on which board?
Gigabyte MP30-AR0 (uart0).
Unless you provide a log file, it is difficult to tell,
Understood. I have attached boot.log to this message. After this point, it freezes/hangs.
but latest CentOS 7.4 (kernel 4.11) boots fine on X-Gene platforms.
I am not sure how you built kernel, but this is what you can check. To boot X-Gene using acpi, you need to enable CONFIG_ARM64_ACPI_PARKING_PROTOCOL=y. CentOS (RPM) default configuration should already have this enabled.
Interesting. It is enabled in the failing kernel:
[root@hammer ~]# grep CONFIG_ARM64_ACPI_PARKING_PROTOCOL /boot/config-4.11.0-45.el7.aarch64 CONFIG_ARM64_ACPI_PARKING_PROTOCOL=y
but it is not enabled in the working kernel that Gordan built for me:
[root@hammer ~]# grep CONFIG_ARM64_ACPI_PARKING_PROTOCOL /boot/config-4.9.60-1.el7.centos.aarch64 [root@hammer ]#
-Phong
+-----Original Message----- +From: Arm-dev [mailto:arm-dev-bounces@centos.org] On Behalf Of Jeremiah +Rothschild +Sent: Friday, January 26, 2018 4:35 PM +To: Conversations around CentOS on ARM hardware +Subject: Re: [Arm-dev] Kernel problems on APM X-Gene
+On Sat, Nov 04, 2017 at 05:37:54PM +0000, Gordan Bobic wrote: +> Apologies for taking so long to return to this thread, it took way +> longer than expected to get to the machine and get it up and running +again.
+Thanks for the update & apologies as well on my delayed follow-up.
+Last time I wrote the mailing list about my kernel problems, I was told +(by jperrin@centos.org) that my system was not in a supported state +because I was daisy-chaining Tianocore EFI via U-Boot. I was directed to +flash the Tianocore firmware and remove U-Boot from the equation. +Although I was skeptical of this answer, I finally was able to do this.
+Unfortunately, however, this does not change behavior. I still cannot +successfully boot into any kernels beyond 4.5 unless I use 'acpi=off'.
+I am, interestingly enough, able to run the 4.9.60 kernel that you +supplied.
+So:
+(1) My experience leads me to believe that it is still a possibility +that a kernel related bug exists.
+(2) I am confused as to why your kernel worked. I built kernel-alt- +4.11.0-22.el7a from source and it fails like the others. Were there any +special steps you took in building the rpm's you supplied me?
+(3) Is it true that you are able to boot into the (> 4.5) distro- +supplied kernels? Or have you only tried/succeeded with your custom +builds?
+Thanks again!
+j
+> I also just updated the build to the latest 4.9.60. +> +> Here is a download link to both binaries and src.rpm (download the +> kernel tarball from kernel.org manually to build from src.rpm): +> http://ftp.redsleeve.org/pub/misc/kernel/aarch64/RPMS/ +> http://ftp.redsleeve.org/pub/misc/kernel/aarch64/SRPMS/ +> +> To recap - I am also running with Tianocore EFI chain-loaded from +> u-boot, and mainling 4.9.x boots just fine on it. +> +> No need for disabling ACPI on the kernel command line, no need to run +> EFI firmware as a 1st stage boot loader, it just works. +> Do feel free to try it - if that works for you but the distro supplied +> 4.5.x kernel doesn't, it seems reasonably conclusive that it is the +> CentOS kernel that is broken for this board. +> +> I'd also be interested in learning whether you have any luck getting +> PCIe cards to work with it without problems - I haven't tried it since +> upgrading to 4.9.x, but certainly on 4.4.x mainline the machine used +> to reliably lock up as soon as the driver for the PCIe card loads. +> +> Gordan +> +> +> On Fri, Sep 22, 2017 at 12:06 PM, Jeremiah Rothschild +> jeremiah@franz.com +> wrote: +> +> > On Fri, Sep 22, 2017 at 11:59:00AM +0100, Gordan Bobic wrote: +> > > On Fri, Sep 22, 2017 at 11:54 AM, Jeremiah Rothschild < +> > jeremiah@franz.com> +> > > wrote: +> > > +> > > > On Fri, Sep 22, 2017 at 11:39:19AM +0100, Gordan Bobic wrote: +> > > > > If you are interested, I'm more than happy to share my src.rpm +> > > > > for +> > 4.9.x, +> > > > > but won't be able to get to it before tomorrow morning as the +> > machine was +> > > > > recently mothballed. +> > > > +> > > > Thanks. I actually need to test with as new of a version as I +> > > > can +> > because I +> > > > have been experiencing an occasional "page allocation failure" +> > > > kernel panic. +> > > > No idea if/when that was fixed but I figure the newest version +> > > > is my +> > best +> > > > hope. +> > > > +> > > +> > > I've been on my own 4.9.x more or less since I got the machine, it +> > > was in +> > > 24/7 use, and I never experienced that issue. So it may be worth a +> > > cross-check with the kernel that I'm running to see whether the +> > > fault follows your machine or whether it is kernel dependent. +> > +> > You're right. It would be a good extra data point. Feel free to mail +> > me directly once you're sorted and I'll gladly check out your 4.9 +build. +> > Thanks +> > again! +> > +> > +> > +> > > _______________________________________________ +> > > Arm-dev mailing list +> > > Arm-dev@centos.org +> > > https://lists.centos.org/mailman/listinfo/arm-dev +> > +> > _______________________________________________ +> > Arm-dev mailing list +> > Arm-dev@centos.org +> > https://lists.centos.org/mailman/listinfo/arm-dev +> >
+> _______________________________________________ +> Arm-dev mailing list +> Arm-dev@centos.org +> https://lists.centos.org/mailman/listinfo/arm-dev
+_______________________________________________ +Arm-dev mailing list +Arm-dev@centos.org +https://lists.centos.org/mailman/listinfo/arm-dev _______________________________________________ Arm-dev mailing list Arm-dev@centos.org https://lists.centos.org/mailman/listinfo/arm-dev
On Fri, Jan 26, 2018 at 02:03:54AM -0800, Jeremiah Rothschild wrote:
Interesting. It is enabled in the failing kernel:
[root@hammer ~]# grep CONFIG_ARM64_ACPI_PARKING_PROTOCOL /boot/config-4.11.0-45.el7.aarch64 CONFIG_ARM64_ACPI_PARKING_PROTOCOL=y
but it is not enabled in the working kernel that Gordan built for me:
[root@hammer ~]# grep CONFIG_ARM64_ACPI_PARKING_PROTOCOL /boot/config-4.9.60-1.el7.centos.aarch64 [root@hammer ]#
Also, it is enabled in the old 4.5 kernels that do work:
[root@hammer ~]# grep CONFIG_ARM64_ACPI_PARKING_PROTOCOL /boot/config-4.5.* /boot/config-4.5.0-23.el7.aarch64:CONFIG_ARM64_ACPI_PARKING_PROTOCOL=y /boot/config-4.5.0-25.el7.aarch64:CONFIG_ARM64_ACPI_PARKING_PROTOCOL=y
-Phong
+-----Original Message----- +From: Arm-dev [mailto:arm-dev-bounces@centos.org] On Behalf Of Jeremiah +Rothschild +Sent: Friday, January 26, 2018 4:35 PM +To: Conversations around CentOS on ARM hardware +Subject: Re: [Arm-dev] Kernel problems on APM X-Gene
+On Sat, Nov 04, 2017 at 05:37:54PM +0000, Gordan Bobic wrote: +> Apologies for taking so long to return to this thread, it took way +> longer than expected to get to the machine and get it up and running +again.
+Thanks for the update & apologies as well on my delayed follow-up.
+Last time I wrote the mailing list about my kernel problems, I was told +(by jperrin@centos.org) that my system was not in a supported state +because I was daisy-chaining Tianocore EFI via U-Boot. I was directed to +flash the Tianocore firmware and remove U-Boot from the equation. +Although I was skeptical of this answer, I finally was able to do this.
+Unfortunately, however, this does not change behavior. I still cannot +successfully boot into any kernels beyond 4.5 unless I use 'acpi=off'.
+I am, interestingly enough, able to run the 4.9.60 kernel that you +supplied.
+So:
+(1) My experience leads me to believe that it is still a possibility +that a kernel related bug exists.
+(2) I am confused as to why your kernel worked. I built kernel-alt- +4.11.0-22.el7a from source and it fails like the others. Were there any +special steps you took in building the rpm's you supplied me?
+(3) Is it true that you are able to boot into the (> 4.5) distro- +supplied kernels? Or have you only tried/succeeded with your custom +builds?
+Thanks again!
+j
+> I also just updated the build to the latest 4.9.60. +> +> Here is a download link to both binaries and src.rpm (download the +> kernel tarball from kernel.org manually to build from src.rpm): +> http://ftp.redsleeve.org/pub/misc/kernel/aarch64/RPMS/ +> http://ftp.redsleeve.org/pub/misc/kernel/aarch64/SRPMS/ +> +> To recap - I am also running with Tianocore EFI chain-loaded from +> u-boot, and mainling 4.9.x boots just fine on it. +> +> No need for disabling ACPI on the kernel command line, no need to run +> EFI firmware as a 1st stage boot loader, it just works. +> Do feel free to try it - if that works for you but the distro supplied +> 4.5.x kernel doesn't, it seems reasonably conclusive that it is the +> CentOS kernel that is broken for this board. +> +> I'd also be interested in learning whether you have any luck getting +> PCIe cards to work with it without problems - I haven't tried it since +> upgrading to 4.9.x, but certainly on 4.4.x mainline the machine used +> to reliably lock up as soon as the driver for the PCIe card loads. +> +> Gordan +> +> +> On Fri, Sep 22, 2017 at 12:06 PM, Jeremiah Rothschild +> jeremiah@franz.com +> wrote: +> +> > On Fri, Sep 22, 2017 at 11:59:00AM +0100, Gordan Bobic wrote: +> > > On Fri, Sep 22, 2017 at 11:54 AM, Jeremiah Rothschild < +> > jeremiah@franz.com> +> > > wrote: +> > > +> > > > On Fri, Sep 22, 2017 at 11:39:19AM +0100, Gordan Bobic wrote: +> > > > > If you are interested, I'm more than happy to share my src.rpm +> > > > > for +> > 4.9.x, +> > > > > but won't be able to get to it before tomorrow morning as the +> > machine was +> > > > > recently mothballed. +> > > > +> > > > Thanks. I actually need to test with as new of a version as I +> > > > can +> > because I +> > > > have been experiencing an occasional "page allocation failure" +> > > > kernel panic. +> > > > No idea if/when that was fixed but I figure the newest version +> > > > is my +> > best +> > > > hope. +> > > > +> > > +> > > I've been on my own 4.9.x more or less since I got the machine, it +> > > was in +> > > 24/7 use, and I never experienced that issue. So it may be worth a +> > > cross-check with the kernel that I'm running to see whether the +> > > fault follows your machine or whether it is kernel dependent. +> > +> > You're right. It would be a good extra data point. Feel free to mail +> > me directly once you're sorted and I'll gladly check out your 4.9 +build. +> > Thanks +> > again! +> > +> > +> > +> > > _______________________________________________ +> > > Arm-dev mailing list +> > > Arm-dev@centos.org +> > > https://lists.centos.org/mailman/listinfo/arm-dev +> > +> > _______________________________________________ +> > Arm-dev mailing list +> > Arm-dev@centos.org +> > https://lists.centos.org/mailman/listinfo/arm-dev +> >
+> _______________________________________________ +> Arm-dev mailing list +> Arm-dev@centos.org +> https://lists.centos.org/mailman/listinfo/arm-dev
+_______________________________________________ +Arm-dev mailing list +Arm-dev@centos.org +https://lists.centos.org/mailman/listinfo/arm-dev _______________________________________________ Arm-dev mailing list Arm-dev@centos.org https://lists.centos.org/mailman/listinfo/arm-dev
EFI stub: Booting Linux Kernel... EFI stub: Using DTB from configuration table EFI stub: Exiting boot services and installing virtual address map... L3c Cache: 8MB [ 0.000000] Booting Linux on physical CPU 0x0 [ 0.000000] Linux version 4.11.0-45.el7.aarch64 (mockbuild@aarch64_02.bsys.centos.org) (gcc version 4.8.5 20150623 (Red Hat 4.8.5-16) (GCC) ) #1 SMP Tue Dec 19 03:48:41 UTC 2017 [ 0.000000] Boot CPU: AArch64 Processor [500f0001] [ 0.000000] earlycon: uart8250 at MMIO32 0x000000001c020000 (options '') [ 0.000000] bootconsole [uart8250] enabled [ 0.000000] efi: Getting EFI parameters from FDT: [ 0.000000] efi: EFI v2.40 by X-Gene Mp30ar0 Board EFI Nov 2 2016 09:37:39 [ 0.000000] efi: ACPI=0xffff0000 ACPI 2.0=0xffff0014 SMBIOS 3.0=0x807afcb000 ESRT=0x807f6bfd18 [ 0.000000] esrt: Reserving ESRT space from 0x000000807f6bfd18 to 0x000000807f6bfd78. [ 0.000000] cma: Reserved 512 MiB at 0x00000000c0000000 [ 0.000000] ACPI: Early table checksum verification disabled [ 0.000000] ACPI: RSDP 0x00000000FFFF0014 000024 (v02 APM ) [ 0.000000] ACPI: XSDT 0x00000000FFFE00E8 00006C (v01 APM XGENE 00000003 01000013) [ 0.000000] ACPI: FACP 0x00000000FFFB0000 00010C (v05 APM XGENE 00000003 INTL 20140724) [ 0.000000] ACPI: DSDT 0x00000000FFFC0000 005668 (v05 APM APM88xxx 00000001 INTL 20140724) [ 0.000000] ACPI: DBG2 0x00000000FFFD0000 0000AA (v00 APMC0D XGENEDBG 00000000 INTL 20140724) [ 0.000000] ACPI: GTDT 0x00000000FFF90000 0000E0 (v02 APM XGENE 00000001 INTL 20140724) [ 0.000000] ACPI: MCFG 0x00000000FFF80000 00007C (v01 APM XGENE 00000002 INTL 20140724) [ 0.000000] ACPI: SPCR 0x00000000FFF70000 000050 (v02 APMC0D XGENESPC 00000000 INTL 20140724) [ 0.000000] ACPI: SSDT 0x00000000FFF60000 00002D (v02 APM XGENE 00000001 INTL 20140724) [ 0.000000] ACPI: APIC 0x00000000FFF50000 0002A4 (v03 APM XGENE 00000003 01000013) [ 0.000000] ACPI: SSDT 0x00000000FFF40000 000078 (v02 REDHAT MACADDRS 00000001 01000013) [ 0.000000] ACPI: SSDT 0x00000000FFF30000 000032 (v02 REDHAT UARTCLKS 00000001 01000013) [ 0.000000] ACPI: SPCR: console: uart,mmio32,0x1c020000 [ 0.000000] ACPI: NUMA: Failed to initialise from firmware [ 0.000000] NUMA: Faking a node at [mem 0x0000000000000000-0x000000807fffffff] [ 0.000000] NUMA: Adding memblock [0x80000000 - 0x801fffff] on node 0 [ 0.000000] NUMA: Adding memblock [0x80200000 - 0xfff2ffff] on node 0 [ 0.000000] NUMA: Adding memblock [0xfff30000 - 0xffffffff] on node 0 [ 0.000000] NUMA: Adding memblock [0x100000000 - 0x1ffffffff] on node 0 [ 0.000000] NUMA: Adding memblock [0x8000000000 - 0x807accffff] on node 0 [ 0.000000] NUMA: Adding memblock [0x807acd0000 - 0x807afcffff] on node 0 [ 0.000000] NUMA: Adding memblock [0x807afd0000 - 0x807ff8ffff] on node 0 [ 0.000000] NUMA: Adding memblock [0x807ff90000 - 0x807ff9ffff] on node 0 [ 0.000000] NUMA: Adding memblock [0x807ffa0000 - 0x807ffaffff] on node 0 [ 0.000000] NUMA: Adding memblock [0x807ffb0000 - 0x807ffdffff] on node 0 [ 0.000000] NUMA: Adding memblock [0x807ffe0000 - 0x807fffffff] on node 0 [ 0.000000] NUMA: Initmem setup node 0 [mem 0x80000000-0x807fffffff] [ 0.000000] NUMA: NODE_DATA [mem 0x807fffe200-0x807fffffff] [ 0.000000] Zone ranges: [ 0.000000] DMA [mem 0x0000000080000000-0x00000000ffffffff] [ 0.000000] Normal [mem 0x0000000100000000-0x000000807fffffff] [ 0.000000] Movable zone start for each node [ 0.000000] Early memory node ranges [ 0.000000] node 0: [mem 0x0000000080000000-0x00000000801fffff] [ 0.000000] node 0: [mem 0x0000000080200000-0x00000000fff2ffff] [ 0.000000] node 0: [mem 0x00000000fff30000-0x00000000ffffffff] [ 0.000000] node 0: [mem 0x0000000100000000-0x00000001ffffffff] [ 0.000000] node 0: [mem 0x0000008000000000-0x000000807accffff] [ 0.000000] node 0: [mem 0x000000807acd0000-0x000000807afcffff] [ 0.000000] node 0: [mem 0x000000807afd0000-0x000000807ff8ffff] [ 0.000000] node 0: [mem 0x000000807ff90000-0x000000807ff9ffff] [ 0.000000] node 0: [mem 0x000000807ffa0000-0x000000807ffaffff] [ 0.000000] node 0: [mem 0x000000807ffb0000-0x000000807ffdffff] [ 0.000000] node 0: [mem 0x000000807ffe0000-0x000000807fffffff] [ 0.000000] Initmem setup node 0 [mem 0x0000000080000000-0x000000807fffffff] [ 0.000000] psci: is not imple mobility grouping on. Total pages: 130944 [ 0.000000] Policy zone: Normal [ 0.000000] Kernel command line: BOOT_IMAGE=/vmlinuz-4.11.0-45.el7.aarch64 root=/dev/mapper/rootvg-root ro rd.md.uuid=2b289d2b:f1ce3a2e:b768d6cb:a6b2252b rd.lvm.lv=rootvg/root rd.md.uuid=f755ea06:9f0a248f:bacc7922:3458f893 rd.lvm.lv=rootvg/swap rhgb console=ttyS0,115200 earlycon=uart8250,mmio32,0x1c020000 LANG=en_US.UTF-8 [ 0.000000] PID hash table entries: 4096 (order: -1, 32768 bytes) [ 0.000000] software IO TLB [mem 0xfbf20000-0xfff20000] (64MB) mapped at [ffff80007bf20000-ffff80007ff1ffff] [ 0.000000] Memory: 7743936K/8388608K available (7548K kernel code, 1372K rwdata, 3200K rodata, 1280K init, 7589K bss, 120384K reserved, 524288K cma-reserved) [ 0.000000] Virtual kernel memory layout: [ 0.000000] modules : 0xffff000000000000 - 0xffff000008000000 ( 128 MB) [ 0.000000] vmalloc : 0xffff000008000000 - 0xffff7bdfffff0000 (126847 GB) [ 0.000000] .text : 0xffff000008080000 - 0xffff0000087e0000 ( 7552 KB) [ 0.000000] .rodata : 0xffff0000087e0000 - 0xffff000008b10000 ( 3264 KB) [ 0.000000] .init : 0xffff000008b10000 - 0xffff000008c50000 ( 1280 KB) [ 0.000000] .data : 0xffff000008c50000 - 0xffff000008da7200 ( 1373 KB) [ 0.000000] .bss : 0xffff000008da7200 - 0xffff000009510954 ( 7590 KB) [ 0.000000] fixed : 0xffff7fdffe7d0000 - 0xffff7fdffec00000 ( 4288 KB) [ 0.000000] PCI I/O : 0xffff7fdffee00000 - 0xffff7fdfffe00000 ( 16 MB) [ 0.000000] vmemmap : 0xffff7fe000000000 - 0xffff800000000000 ( 128 GB maximum) [ 0.000000] 0xffff7fe000000000 - 0xffff7fe020000000 ( 512 MB actual) [ 0.000000] memory : 0xffff800000000000 - 0xffff808000000000 (524288 MB) [ 0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=8, Nodes=1 [ 0.000000] Hierarchical RCU implementation. [ 0.000000] Build-time adjustment of leaf fanout to 64. [ 0.000000] RCU restricting CPUs from NR_CPUS=4096 to nr_cpu_ids=8. [ 0.000000] RCU: Adjusting geometry for rcu_fanout_leaf=64, nr_cpu_ids=8 [ 0.000000] NR_IRQS:64 nr_irqs:64 0 [ 0.000000] GIC: Using split EOI/Deactivate mode [ 0.000000] GICv3: No distributor detected at @ffff000008050000, giving up [ 0.000000] arch_timer: Failed to initialize memory-mapped timer. [ 0.000000] arch_timer: cp15 timer(s) running at 50.00MHz (phys). [ 0.000000] clocksource: arch_sys_counter: mask: 0xffffffffffffff max_cycles: 0xb8812736b, max_idle_ns: 440795202655 ns [ 0.000002] sched_clock: 56 bits at 50MHz, resolution 20ns, wraps every 4398046511100ns [ 0.008346] Console: colour dummy device 80x25 [ 0.012941] Calibrating delay loop (skipped), value calculated using timer frequency.. 100.00 BogoMIPS (lpj=500000) [ 0.023745] pid_max: default: 32768 minimum: 301 [ 0.028509] ACPI: Core revision 20170119 [ 0.036542] ACPI: 4 ACPI AML tables successfully acquired and loaded [ 0.043140] Security Framework initialized [ 0.047350] SELinux: Initializing. [ 0.051062] Dentry cache hash table entries: 1048576 (order: 7, 8388608 bytes) [ 0.059829] Inode-cache hash table entries: 524288 (order: 6, 4194304 bytes) [ 0.067694] Mount-cache hash table entries: 16384 (order: 1, 131072 bytes) [ 0.074780] Mountpoint-cache hash table entries: 16384 (order: 1, 131072 bytes) [ 0.082692] ftrace: allocating 27115 entries in 7 pages [ 0.134464] ASID allocator initialised with 65536 entries [ 0.140648] Remapping and enabling EFI services. [ 0.145385] EFI remap 0x0000000010510000 => 0000000020000000 [ 0.151378] EFI remap 0x0000000010548000 => 0000000020018000 [ 0.157357] EFI remap 0x0000000017000000 => 0000000020020000 [ 0.163358] EFI remap 0x000000001c025000 => 0000000020035000 [ 0.169423] EFI remap 0x000000807acd0000 => 0000000020040000 [ 0.175414] EFI remap 0x000000807ace0000 => 0000000020050000 [ 0.181435] EFI remap 0x000000807acf0000 => 0000000020060000 [ 0.187383] EFI remap 0x000000807ad20000 => 0000000020090000 [ 0.193361] EFI remap 0x000000807ad80000 => 00000000200f0000 [ 0.199311] EFI remap 0x000000807ad90000 => 0000000020100000 [ 0.205348] EFI remap 0x000000807af90000 => 0000000020300000 [ 0.211366] EFI remap 0x000000807afa0000 => 0000000020310000 [ 0.217404] EFI remap 0x000000807ff90000 => 0000000020330000 [ 0.223447] EFI remap 0x000000807ffb0000 => 0000000020340000 [ 0.229612] smp: Bringing up secondary CPUs ... [ 0.234456] Detected PIPT I-cache on CPU1 [ 0.234483] CPU1: Booted secondary processor [500f0001] [ 0.234703] Detected PIPT I-cache on CPU2 [ 0.234723] CPU2: Booted secondary processor [500f0001] [ 0.234937] Detected PIPT I-cache on CPU3 [ 0.234950] CPU3: Booted secondary processor [500f0001] [ 0.235144] Detected PIPT I-cache on CPU4 [ 0.235165] CPU4: Booted secondary processor [500f0001] [ 0.235367] Detected PIPT I-cache on CPU5 [ 0.235381] CPU5: Booted secondary processor [500f0001] [ 0.235571] Detected PIPT I-cache on CPU6 [ 0.235591] CPU6: Booted secondary processor [500f0001] [ 0.235795] Detected PIPT I-cache on CPU7 [ 0.235808] CPU7: Booted secondary processor [500f0001] [ 0.235851] smp: Brought up 1 node, 8 CPUs [ 0.308534] SMP: Total of 8 processors activated. [ 0.313517] CPU features: detected feature: 32-bit EL0 Support [ 0.319681] CPU: All CPU(s) started at EL2 [ 0.324899] devtmpfs: initialized [ 0.328709] SMBIOS 3.0.0 present. [ 0.332210] DMI: AppliedMicro X-Gene Mp30ar0 Board/X-Gene Mp30ar0 Board, BIOS 1.1.0 Nov 2 2016 [ 0.341516] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 19112604462750000 ns [ 0.351945] futex hash table entries: 2048 (order: 2, 262144 bytes) [ 0.359069] pinctrl core: initialized pinctrl subsystem [ 0.364843] NET: Registered protocol family 16 [ 0.369902] cpuidle: using governor menu [ 0.374065] PCCT header not found. [ 0.377719] vdso: 2 pages (1 code @ ffff000008800000, 1 data @ ffff000008c70000) [ 0.385558] hw-breakpoint: found 4 breakpoint and 4 watchpoint registers. [ 0.395350] DMA: preallocated 256 KiB pool for atomic allocations [ 0.401846] ACPI: bus type PCI registered [ 0.406092] acpiphp: ACPI Hot Plug PCI Controller Driver version: 0.5 [ 0.412950] Serial: AMBA PL011 UART driver [ 0.419304] HugeTLB registered 2 MB page size, pre-allocated 0 pages [ 0.426048] HugeTLB registered 512 MB page size, pre-allocated 0 pages [ 0.433545] ACPI: Added _OSI(Module Device) [ 0.437995] ACPI: Added _OSI(Processor Device) [ 0.442688] ACPI: Added _OSI(3.0 _SCP Extensions) [ 0.447659] ACPI: Added _OSI(Processor Aggregator Device) [ 0.461591] ACPI: Interpreter enabled [ 0.465479] ACPI: Using GIC for interrupt routing [ 0.470479] ACPI: MCFG table detected, 5 entries [ 0.477755] ACPI: Power Resource [SCVR] (off) [ 0.490175] ACPI: PCI Root Bridge [PCI0] (domain 0000 [bus 00-ff]) [ 0.496752] acpi PNP0A08:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI] [ 0.505646] acpi PNP0A08:00: _OSC: OS now controls [PCIeHotplug PME AER PCIeCapability] [ 0.514152] acpi PNP0A08:00: MCFG quirk: ECAM at [mem 0xe0d0000000-0xe0dfffffff] for [bus 00-ff] with xgene_v1_pcie_ecam_ops [ 0.527193] acpi PNP0A08:00: [Firmware Bug]: ECAM area [mem 0xe0d0000000-0xe0dfffffff] not reserved in ACPI namespace [ 0.538509] acpi PNP0A08:00: ECAM at [mem 0xe0d0000000-0xe0dfffffff] for [bus 00-ff] [ 0.546726] Remapped I/O 0x000000e010000000 to [io 0x0000-0xffff window] [ 0.554045] PCI host bridge to bus 0000:00 [ 0.558388] pci_bus 0000:00: root bus resource [io 0x0000-0xffff window] [ 0.565595] pci_bus 0000:00: root bus resource [mem 0xe140000000-0xe17fffffff window] (bus address [0x40000000-0x7fffffff]) [ 0.577400] pci_bus 0000:00: root bus resource [mem 0xf000000000-0xffffffffff window] [ 0.585699] pci_bus 0000:00: root bus resource [bus 00-ff] [ 0.591751] pci 0000:00:00.0: PCI bridge to [bus 01] [ 0.597077] ACPI: PCI Root Bridge [PCI2] (domain 0002 [bus 00-ff]) [ 0.603636] acpi PNP0A08:01: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI] [ 0.612470] acpi PNP0A08:01: _OSC: platform does not support [PCIeHotplug] [ 0.619910] acpi PNP0A08:01: _OSC: OS now controls [PME AER PCIeCapability] [ 0.627298] acpi PNP0A08:01: MCFG quirk: ECAM at [mem 0x90d0000000-0x90dfffffff] for [bus 00-ff] with xgene_v1_pcie_ecam_ops [ 0.640162] acpi PNP0A08:01: [Firmware Bug]: ECAM area [mem 0x90d0000000-0x90dfffffff] not reserved in ACPI namespace [ 0.651467] acpi PNP0A08:01: ECAM at [mem 0x90d0000000-0x90dfffffff] for [bus 00-ff] [ 0.659699] Remapped I/O 0x0000009010000000 to [io 0x10000-0x1ffff window] [ 0.667187] PCI host bridge to bus 0002:00 [ 0.671521] pci_bus 0002:00: root bus resource [io 0x10000-0x1ffff window] (bus address [0x10000000-0x1000ffff]) [ 0.682410] pci_bus 0002:00: root bus resource [mem 0x9140000000-0x917fffffff window] (bus address [0x40000000-0x7fffffff]) [ 0.694210] pci_bus 0002:00: root bus resource [mem 0x9400000000-0x97ffffffff window] [ 0.702491] pci_bus 0002:00: root bus resource [bus 00-ff] [ 0.708773] pci 0002:01:00.0: disabling ASPM on pre-1.1 PCIe device. You can enable it with 'pcie_aspm=force' [ 0.719895] pci 0002:00:00.0: BAR 14: assigned [mem 0x9140000000-0x91417fffff] [ 0.727537] pci 0002:00:00.0: BAR 13: assigned [io 0x10000-0x10fff] [ 0.734279] pci 0002:01:00.0: BAR 14: assigned [mem 0x9140000000-0x91417fffff] [ 0.741937] pci 0002:01:00.0: BAR 13: assigned [io 0x10000-0x10fff] [ 0.748667] pci 0002:02:00.0: BAR 0: assigned [mem 0x9140000000-0x9140ffffff] [ 0.756236] pci 0002:02:00.0: BAR 1: assigned [mem 0x9141000000-0x914101ffff] [ 0.763811] pci 0002:02:00.0: BAR 2: assigned [io 0x10000-0x1007f] [ 0.770446] pci 0002:01:00.0: PCI bridge to [bus 02] [ 0.775699] pci 0002:01:00.0: bridge window [io 0x10000-0x10fff] [ 0.782335] pci 0002:01:00.0: bridge window [mem 0x9140000000-0x91417fffff] [ 0.789914] pci 0002:00:00.0: PCI bridge to [bus 01-02] [ 0.795447] pci 0002:00:00.0: bridge window [io 0x10000-0x10fff] [ 0.802083] pci 0002:00:00.0: bridge window [mem 0x9140000000-0x91417fffff] [ 0.809707] ACPI: PCI Root Bridge [PCI3] (domain 0003 [bus 00-ff]) [ 0.816279] acpi PNP0A08:02: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI] [ 0.825164] acpi PNP0A08:02: _OSC: OS now controls [PCIeHotplug PME AER PCIeCapability] [ 0.833672] acpi PNP0A08:02: MCFG quirk: ECAM at [mem 0xa0d0000000-0xa0dfffffff] for [bus 00-ff] with xgene_v1_pcie_ecam_ops [ 0.846518] acpi PNP0A08:02: [Firmware Bug]: ECAM area [mem 0xa0d0000000-0xa0dfffffff] not reserved in ACPI namespace [ 0.857822] acpi PNP0A08:02: ECAM at [mem 0xa0d0000000-0xa0dfffffff] for [bus 00-ff] [ 0.866063] Remapped I/O 0x000000a010000000 to [io 0x20000-0x2ffff window] [ 0.873565] PCI host bridge to bus 0003:00 [ 0.877899] pci_bus 0003:00: root bus resource [io 0x20000-0x2ffff window] (bus address [0x0000-0xffff]) [ 0.888044] pci_bus 0003:00: root bus resource [mem 0xa140000000-0xa17fffffff window] (bus address [0x40000000-0x7fffffff]) [ 0.899845] pci_bus 0003:00: root bus resource [mem 0xb000000000-0xbfffffffff window] [ 0.908151] pci_bus 0003:00: root bus resource [bus 00-ff] [ 0.914172] pci 0003:00:00.0: PCI bridge to [bus 01] [ 0.919692] xgene-msi APMC0D0E:00: APM X-Gene PCIe MSI driver loaded [ 0.926832] pci 0002:02:00.0: vgaarb: VGA device added: decodes=io+mem,owns=none,locks=none [ 0.935693] pci 0002:02:00.0: vgaarb: bridge control possible [ 0.941779] vgaarb: loaded [ 0.944736] SCSI subsystem initialized [ 0.948806] ACPI: bus type USB registered [ 0.953083] usbcore: registered new interface driver usbfs [ 0.958914] usbcore: registered new interface driver hub [ 0.964588] usbcore: registered new device driver usb [ 0.970044] Registered efivars operations [ 0.974676] NetLabel: Initializing [ 0.978274] NetLabel: domain hash size = 128 [ 0.982881] NetLabel: protocols = UNLABELED CIPSOv4 CALIPSO [ 0.988899] NetLabel: unlabeled traffic allowed by default [ 0.994947] clocksource: Switched to clocksource arch_sys_counter [ 1.020688] VFS: Disk quotas dquot_6.6.0 [ 1.024885] VFS: Dquot-cache hash table entries: 8192 (order 0, 65536 bytes) [ 1.032617] pnp: PnP ACPI init [ 1.036471] pnp: PnP ACPI: found 0 devices [ 1.043277] NET: Registered protocol family 2 [ 1.048136] TCP established hash table entries: 65536 (order: 3, 524288 bytes) [ 1.055981] TCP bind hash table entries: 65536 (order: 4, 1048576 bytes) [ 1.063453] TCP: Hash tables configured (established 65536 bind 65536) [ 1.070440] UDP hash table entries: 4096 (order: 1, 131072 bytes) [ 1.076974] UDP-Lite hash table entries: 4096 (order: 1, 131072 bytes) [ 1.084038] NET: Registered protocol family 1 [ 1.088793] Unpacking initramfs... [ 1.394774] Freeing initrd memory: 14208K [ 1.399373] hw perfevents: enabled with armv8_pmuv3_0 PMU driver, 5 counters available [ 1.407797] kvm [1]: 8-bit VMID [ 1.411109] kvm [1]: IDMAP page: 809cf000 [ 1.415355] kvm [1]: HYP VA range: 800000000000:ffffffffffff [ 1.421438] kvm [1]: Hyp mode initialized successfully [ 1.426896] kvm [1]: GICV region size/alignment is unsafe, using trapping (reduced performance) [ 1.436141] kvm [1]: vgic-v2@780cf000 [ 1.440089] kvm [1]: vgic interrupt IRQ1 [ 1.444251] kvm [1]: virtual timer IRQ3 [ 1.464992] audit: initializing netlink subsys (disabled) [ 1.470796] audit: type=2000 audit(1.210:1): state=initialized audit_enabled=0 res=1 [ 1.470955] Initialise system trusted keyrings [ 1.471013] workingset: timestamp_bits=44 max_order=17 bucket_order=0 [ 1.473109] zbud: loaded [ 1.553032] NET: Registered protocol family 38 [ 1.557778] Key type asymmetric registered [ 1.562119] Asymmetric key parser 'x509' registered [ 1.567314] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 251) [ 1.575231] io scheduler noop registered [ 1.579390] io scheduler deadline registered (default) [ 1.584870] io scheduler cfq registered [ 1.588942] io scheduler mq-deadline registered [ 1.593881] atomic64_test: passed [ 1.597701] xgene-gpio APMC0D14:00: X-Gene GPIO driver registered. [ 1.604834] pcieport 0000:00:00.0: AER enabled with IRQ 30 [ 1.610673] pcieport 0002:00:00.0: AER enabled with IRQ 31 [ 1.616545] pcieport 0003:00:00.0: AER enabled with IRQ 32 [ 1.622387] pcieport 0000:00:00.0: Signaling PME with IRQ 30 [ 1.628399] pcieport 0002:00:00.0: Signaling PME with IRQ 31 [ 1.634413] pcieport 0003:00:00.0: Signaling PME with IRQ 32 [ 1.640553] efifb: probing for efifb [ 1.644335] efifb: framebuffer at 0x40000000, using 1216k, total 1200k [ 1.651255] efifb: mode is 640x480x32, linelength=2560, pages=1 [ 1.657514] efifb: scrolling: redraw [ 1.661302] efifb: Truecolor: size=8:8:8:8, shift=24:0:8:16 [ 1.668723] Console: switching to colour frame buffer device 80x30 [ 1.676642] fb0: EFI VGA frame buffer device [ 1.681302] acpi ACPI0007:00: CPPC data invalid or not present [ 1.687504] acpi ACPI0007:01: CPPC data invalid or not present [ 1.693696] acpi ACPI0007:02: CPPC data invalid or not present [ 1.699865] acpi ACPI0007:03: CPPC data invalid or not present [ 1.706051] acpi ACPI0007:04: CPPC data invalid or not present [ 1.712232] acpi ACPI0007:05: CPPC data invalid or not present [ 1.718417] acpi ACPI0007:06: CPPC data invalid or not present [ 1.724598] acpi ACPI0007:07: CPPC data invalid or not present [ 1.730934] GHES: HEST is not enabled! [ 1.734915] ACPI GTDT: [Firmware Bug]: failed to get the Watchdog base address. [ 1.742794] Serial: 8250/16550 driver, 4 ports, IRQ sharing enabled [ 1.775138] console [ttyS0] disabled [ 1.799055] APMC0D08:00: ttyS0 at MMIO 0x1c020000 (irq = 33, base_baud = 3125000) is a U6_16550A [ 0.000000] Booting Linux on physical CPU 0x0 [ 0.000000] Linux version 4.11.0-45.el7.aarch64 (mockbuild@aarch64_02.bsys.centos.org) (gcc version 4.8.5 20150623 (Red Hat 4.8.5-16) (GCC) ) #1 SMP Tue Dec 19 03:48:41 UTC 2017 [ 0.000000] Boot CPU: AArch64 Processor [500f0001] [ 0.000000] earlycon: uart8250 at MMIO32 0x000000001c020000 (options '') [ 0.000000] bootconsole [uart8250] enabled [ 0.000000] efi: Getting EFI parameters from FDT: [ 0.000000] efi: EFI v2.40 by X-Gene Mp30ar0 Board EFI Nov 2 2016 09:37:39 [ 0.000000] efi: ACPI=0xffff0000 ACPI 2.0=0xffff0014 SMBIOS 3.0=0x807afcb000 ESRT=0x807f6bfd18 [ 0.000000] esrt: Reserving ESRT space from 0x000000807f6bfd18 to 0x000000807f6bfd78. [ 0.000000] cma: Reserved 512 MiB at 0x00000000c0000000 [ 0.000000] ACPI: Early table checksum verification disabled [ 0.000000] ACPI: RSDP 0x00000000FFFF0014 000024 (v02 APM ) [ 0.000000] ACPI: XSDT 0x00000000FFFE00E8 00006C (v01 APM XGENE 00000003 01000013) [ 0.000000] ACPI: FACP 0x00000000FFFB0000 00010C (v05 APM XGENE 00000003 INTL 20140724) [ 0.000000] ACPI: DSDT 0x00000000FFFC0000 005668 (v05 APM APM88xxx 00000001 INTL 20140724) [ 0.000000] ACPI: DBG2 0x00000000FFFD0000 0000AA (v00 APMC0D XGENEDBG 00000000 INTL 20140724) [ 0.000000] ACPI: GTDT 0x00000000FFF90000 0000E0 (v02 APM XGENE 00000001 INTL 20140724) [ 0.000000] ACPI: MCFG 0x00000000FFF80000 00007C (v01 APM XGENE 00000002 INTL 20140724) [ 0.000000] ACPI: SPCR 0x00000000FFF70000 000050 (v02 APMC0D XGENESPC 00000000 INTL 20140724) [ 0.000000] ACPI: SSDT 0x00000000FFF60000 00002D (v02 APM XGENE 00000001 INTL 20140724) [ 0.000000] ACPI: APIC 0x00000000FFF50000 0002A4 (v03 APM XGENE 00000003 01000013) [ 0.000000] ACPI: SSDT 0x00000000FFF40000 000078 (v02 REDHAT MACADDRS 00000001 01000013) [ 0.000000] ACPI: SSDT 0x00000000FFF30000 000032 (v02 REDHAT UARTCLKS 00000001 01000013) [ 0.000000] ACPI: SPCR: console: uart,mmio32,0x1c020000 [ 0.000000] ACPI: NUMA: Failed to initialise from firmware [ 0.000000] NUMA: Faking a node at [mem 0x0000000000000000-0x000000807fffffff] [ 0.000000] NUMA: Adding memblock [0x80000000 - 0x801fffff] on node 0 [ 0.000000] NUMA: Adding memblock [0x80200000 - 0xfff2ffff] on node 0 [ 0.000000] NUMA: Adding memblock [0xfff30000 - 0xffffffff] on node 0 [ 0.000000] NUMA: Adding memblock [0x100000000 - 0x1ffffffff] on node 0 [ 0.000000] NUMA: Adding memblock [0x8000000000 - 0x807accffff] on node 0 [ 0.000000] NUMA: Adding memblock [0x807acd0000 - 0x807afcffff] on node 0 [ 0.000000] NUMA: Adding memblock [0x807afd0000 - 0x807ff8ffff] on node 0 [ 0.000000] NUMA: Adding memblock [0x807ff90000 - 0x807ff9ffff] on node 0 [ 0.000000] NUMA: Adding memblock [0x807ffa0000 - 0x807ffaffff] on node 0 [ 0.000000] NUMA: Adding memblock [0x807ffb0000 - 0x807ffdffff] on node 0 [ 0.000000] NUMA: Adding memblock [0x807ffe0000 - 0x807fffffff] on node 0 [ 0.000000] NUMA: Initmem setup node 0 [mem 0x80000000-0x807fffffff] [ 0.000000] NUMA: NODE_DATA [mem 0x807fffe200-0x807fffffff] [ 0.000000] Zone ranges: [ 0.000000] DMA [mem 0x0000000080000000-0x00000000ffffffff] [ 0.000000] Normal [mem 0x0000000100000000-0x000000807fffffff] [ 0.000000] Movable zone start for each node [ 0.000000] Early memory node ranges [ 0.000000] node 0: [mem 0x0000000080000000-0x00000000801fffff] [ 0.000000] node 0: [mem 0x0000000080200000-0x00000000fff2ffff] [ 0.000000] node 0: [mem 0x00000000fff30000-0x00000000ffffffff] [ 0.000000] node 0: [mem 0x0000000100000000-0x00000001ffffffff] [ 0.000000] node 0: [mem 0x0000008000000000-0x000000807accffff] [ 0.000000] node 0: [mem 0x000000807acd0000-0x000000807afcffff] [ 0.000000] node 0: [mem 0x000000807afd0000-0x000000807ff8ffff] [ 0.000000] node 0: [mem 0x000000807ff90000-0x000000807ff9ffff] [ 0.000000] node 0: [mem 0x000000807ffa0000-0x000000807ffaffff] [ 0.000000] node 0: [mem 0x000000807ffb0000-0x000000807ffdffff] [ 0.000000] node 0: [mem 0x000000807ffe0000-0x000000807fffffff] [ 0.000000] Initmem setup node 0 [mem 0x0000000080000000-0x000000807fffffff] [ 0.000000] psci: is not implemented in ACPI. [ 0.000000] percpu: Embedded 3 pages/cpu @ffff807fffda0000 s133016 r8192 d55400 u196608 [ 0.000000] Detected PIPT I-cache on CPU0 [ 0.000000] Built 1 zonelists in Node order, mobility grouping on. Total pages: 130944 [ 0.000000] Policy zone: Normal [ 0.000000] Kernel command line: BOOT_IMAGE=/vmlinuz-4.11.0-45.el7.aarch64 root=/dev/mapper/rootvg-root ro rd.md.uuid=2b289d2b:f1ce3a2e:b768d6cb:a6b2252b rd.lvm.lv=rootvg/root rd.md.uuid=f755ea06:9f0a248f:bacc7922:3458f893 rd.lvm.lv=rootvg/swap rhgb console=ttyS0,115200 earlycon=uart8250,mmio32,0x1c020000 LANG=en_US.UTF-8 [ 0.000000] PID hash table entries: 4096 (order: -1, 32768 bytes) [ 0.000000] software IO TLB [mem 0xfbf20000-0xfff20000] (64MB) mapped at [ffff80007bf20000-ffff80007ff1ffff] [ 0.000000] Memory: 7743936K/8388608K available (7548K kernel code, 1372K rwdata, 3200K rodata, 1280K init, 7589K bss, 120384K reserved, 524288K cma-reserved) [ 0.000000] Virtual kernel memory layout: [ 0.000000] modules : 0xffff000000000000 - 0xffff000008000000 ( 128 MB) [ 0.000000] vmalloc : 0xffff000008000000 - 0xffff7bdfffff0000 (126847 GB) [ 0.000000] .text : 0xffff000008080000 - 0xffff0000087e0000 ( 7552 KB) [ 0.000000] .rodata : 0xffff0000087e0000 - 0xffff000008b10000 ( 3264 KB) [ 0.000000] .init : 0xffff000008b10000 - 0xffff000008c50000 ( 1280 KB) [ 0.000000] .data : 0xffff000008c50000 - 0xffff000008da7200 ( 1373 KB) [ 0.000000] .bss : 0xffff000008da7200 - 0xffff000009510954 ( 7590 KB) [ 0.000000] fixed : 0xffff7fdffe7d0000 - 0xffff7fdffec00000 ( 4288 KB) [ 0.000000] PCI I/O : 0xffff7fdffee00000 - 0xffff7fdfffe00000 ( 16 MB) [ 0.000000] vmemmap : 0xffff7fe000000000 - 0xffff800000000000 ( 128 GB maximum) [ 0.000000] 0xffff7fe000000000 - 0xffff7fe020000000 ( 512 MB actual) [ 0.000000] memory : 0xffff800000000000 - 0xffff808000000000 (524288 MB) [ 0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=8, Nodes=1 [ 0.000000] Hierarchical RCU implementation. [ 0.000000] Build-time adjustment of leaf fanout to 64. [ 0.000000] RCU restricting CPUs from NR_CPUS=4096 to nr_cpu_ids=8. [ 0.000000] RCU: Adjusting geometry for rcu_fanout_leaf=64, nr_cpu_ids=8 [ 0.000000] NR_IRQS:64 nr_irqs:64 0 [ 0.000000] GIC: Using split EOI/Deactivate mode [ 0.000000] GICv3: No distributor detected at @ffff000008050000, giving up [ 0.000000] arch_timer: Failed to initialize memory-mapped timer. [ 0.000000] arch_timer: cp15 timer(s) running at 50.00MHz (phys). [ 0.000000] clocksource: arch_sys_counter: mask: 0xffffffffffffff max_cycles: 0xb8812736b, max_idle_ns: 440795202655 ns [ 0.000002] sched_clock: 56 bits at 50MHz, resolution 20ns, wraps every 4398046511100ns [ 0.008346] Console: colour dummy device 80x25 [ 0.012941] Calibrating delay loop (skipped), value calculated using timer frequency.. 100.00 BogoMIPS (lpj=500000) [ 0.023745] pid_max: default: 32768 minimum: 301 [ 0.028509] ACPI: Core revision 20170119 [ 0.036542] ACPI: 4 ACPI AML tables successfully acquired and loaded [ 0.043140] Security Framework initialized [ 0.047350] SELinux: Initializing. [ 0.051062] Dentry cache hash table entries: 1048576 (order: 7, 8388608 bytes) [ 0.059829] Inode-cache hash table entries: 524288 (order: 6, 4194304 bytes) [ 0.067694] Mount-cache hash table entries: 16384 (order: 1, 131072 bytes) [ 0.074780] Mountpoint-cache hash table entries: 16384 (order: 1, 131072 bytes) [ 0.082692] ftrace: allocating 27115 entries in 7 pages [ 0.134464] ASID allocator initialised with 65536 entries [ 0.140648] Remapping and enabling EFI services. [ 0.145385] EFI remap 0x0000000010510000 => 0000000020000000 [ 0.151378] EFI remap 0x0000000010548000 => 0000000020018000 [ 0.157357] EFI remap 0x0000000017000000 => 0000000020020000 [ 0.163358] EFI remap 0x000000001c025000 => 0000000020035000 [ 0.169423] EFI remap 0x000000807acd0000 => 0000000020040000 [ 0.175414] EFI remap 0x000000807ace0000 => 0000000020050000 [ 0.181435] EFI remap 0x000000807acf0000 => 0000000020060000 [ 0.187383] EFI remap 0x000000807ad20000 => 0000000020090000 [ 0.193361] EFI remap 0x000000807ad80000 => 00000000200f0000 [ 0.199311] EFI remap 0x000000807ad90000 => 0000000020100000 [ 0.205348] EFI remap 0x000000807af90000 => 0000000020300000 [ 0.211366] EFI remap 0x000000807afa0000 => 0000000020310000 [ 0.217404] EFI remap 0x000000807ff90000 => 0000000020330000 [ 0.223447] EFI remap 0x000000807ffb0000 => 0000000020340000 [ 0.229612] smp: Bringing up secondary CPUs ... [ 0.234456] Detected PIPT I-cache on CPU1 [ 0.234483] CPU1: Booted secondary processor [500f0001] [ 0.234703] Detected PIPT I-cache on CPU2 [ 0.234723] CPU2: Booted secondary processor [500f0001] [ 0.234937] Detected PIPT I-cache on CPU3 [ 0.234950] CPU3: Booted secondary processor [500f0001] [ 0.235144] Detected PIPT I-cache on CPU4 [ 0.235165] CPU4: Booted secondary processor [500f0001] [ 0.235367] Detected PIPT I-cache on CPU5 [ 0.235381] CPU5: Booted secondary processor [500f0001] [ 0.235571] Detected PIPT I-cache on CPU6 [ 0.235591] CPU6: Booted secondary processor [500f0001] [ 0.235795] Detected PIPT I-cache on CPU7 [ 0.235808] CPU7: Booted secondary processor [500f0001] [ 0.235851] smp: Brought up 1 node, 8 CPUs [ 0.308534] SMP: Total of 8 processors activated. [ 0.313517] CPU features: detected feature: 32-bit EL0 Support [ 0.319681] CPU: All CPU(s) started at EL2 [ 0.324899] devtmpfs: initialized [ 0.328709] SMBIOS 3.0.0 present. [ 0.332210] DMI: AppliedMicro X-Gene Mp30ar0 Board/X-Gene Mp30ar0 Board, BIOS 1.1.0 Nov 2 2016 [ 0.341516] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 19112604462750000 ns [ 0.351945] futex hash table entries: 2048 (order: 2, 262144 bytes) [ 0.359069] pinctrl core: initialized pinctrl subsystem [ 0.364843] NET: Registered protocol family 16 [ 0.369902] cpuidle: using governor menu [ 0.374065] PCCT header not found. [ 0.377719] vdso: 2 pages (1 code @ ffff000008800000, 1 data @ ffff000008c70000) [ 0.385558] hw-breakpoint: found 4 breakpoint and 4 watchpoint registers. [ 0.395350] DMA: preallocated 256 KiB pool for atomic allocations [ 0.401846] ACPI: bus type PCI registered [ 0.406092] acpiphp: ACPI Hot Plug PCI Controller Driver version: 0.5 [ 0.412950] Serial: AMBA PL011 UART driver [ 0.419304] HugeTLB registered 2 MB page size, pre-allocated 0 pages [ 0.426048] HugeTLB registePI: Added _OSI(Processor Aggregator Device) [ 0.461591] ACPI: Interpreter enabled [ 0.465479] ACPI: Using GIC for interrupt routing [ 0.470479] ACPI: MCFG table detected, 5 entries [ 0.477755] ACPI: Power Resource [SCVR] (off) [ 0.490175] ACPI: PCI Root Bridge [PCI0] (domain 0000 [bus 00-ff]) [ 0.496752] acpi PNP0A08:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI] [ 0.505646] acpi PNP0A08:00: _OSC: OS now controls [PCIeHotplug PME AER PCIeCapability] [ 0.514152] acpi PNP0A08:00: MCFG quirk: ECAM at [mem 0xe0d0000000-0xe0dfffffff] for [bus 00-ff] with xgene_v1_pcie_ecam_ops [ 0.527193] acpi PNP0A08:00: [Firmware Bug]: ECAM area [mem 0xe0d0000000-0xe0dfffffff] not reserved in ACPI namespace [ 0.538509] acpi PNP0A08:00: ECAM at [mem 0xe0d0000000-0xe0dfffffff] for [bus 00-ff] [ 0.546726] Remapped I/O 0x000000e010000000 to [io 0x0000-0xffff window] [ 0.554045] PCI host bridge to bus 0000:00 [ 0.558388] pci_bus 0000:00: root bus resource [io 0x0000-0xffff window] [ 0.565595] pci_bus 0000:00: root bus resource [mem 0xe140000000-0xe17fffffff window] (bus address [0x40000000-0x7fffffff]) [ 0.577400] pci_bus 0000:00: root bus resource [mem 0xf000000000-0xffffffffff window] [ 0.585699] pci_bus 0000:00: root bus resource [bus 00-ff] [ 0.591751] pci 0000:00:00.0: PCI bridge to [bus 01] [ 0.597077] ACPI: PCI Root Bridge [PCI2] (domain 0002 [bus 00-ff]) [ 0.603636] acpi PNP0A08:01: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI] [ 0.612470] acpi PNP0A08:01: _OSC: platform does not support [PCIeHotplug] [ 0.619910] acpi PNP0A08:01: _OSC: OS now controls [PME AER PCIeCapability] [ 0.627298] acpi PNP0A08:01: MCFG quirk: ECAM at [mem 0x90d0000000-0x90dfffffff] for [bus 00-ff] with xgene_v1_pcie_ecam_ops [ 0.640162] acpi PNP0A08:01: [Firmware Bug]: ECAM area [mem 0x90d0000000-0x90dfffffff] not reserved in ACPI namespace [ 0.651467] acpi PNP0A08:01: ECAM at [mem 0x90d0000000-0x90dfffffff] for [bus 00-ff] [ 0.659699] Remapped I/O 0x0000009010000000 to [io 0x10000-0x1ffff window] [ 0.667187] PCI host bridge to bus 0002:00 [ 0.671521] pci_bus 0002:00: root bus resource [io 0x10000-0x1ffff window] (bus address [0x10000000-0x1000ffff]) [ 0.682410] pci_bus 0002:00: root bus resource [mem 0x9140000000-0x917fffffff window] (bus address [0x40000000-0x7fffffff]) [ 0.694210] pci_bus 0002:00: root bus resource [mem 0x9400000000-0x97ffffffff window] [ 0.702491] pci_bus 0002:00: root bus resource [bus 00-ff] [ 0.708773] pci 0002:01:00.0: disabling ASPM on pre-1.1 PCIe device. You can enable it with 'pcie_aspm=force' [ 0.719895] pci 0002:00:00.0: BAR 14: assigned [mem 0x9140000000-0x91417fffff] [ 0.727537] pci 0002:00:00.0: BAR 13: assigned [io 0x10000-0x10fff] [ 0.734279] pci 0002:01:00.0: BAR 14: assigned [mem 0x9140000000-0x91417fffff] [ 0.741937] pci 0002:01:00.0: BAR 13: assigned [io 0x10000-0x10fff] [ 0.748667] pci 0002:02:00.0: BAR 0: assigned [mem 0x9140000000-0x9140ffffff] [ 0.756236] pci 0002:02:00.0: BAR 1: assigned [mem 0x9141000000-0x914101ffff] [ 0.763811] pci 0002:02:00.0: BAR 2: assigned [io 0x10000-0x1007f] [ 0.770446] pci 0002:01:00.0: PCI bridge to [bus 02] [ 0.775699] pci 0002:01:00.0: bridge window [io 0x10000-0x10fff] [ 0.782335] pci 0002:01:00.0: bridge window [mem 0x9140000000-0x91417fffff] [ 0.789914] pci 0002:00:00.0: PCI bridge to [bus 01-02] [ 0.795447] pci 0002:00:00.0: bridge window [io 0x10000-0x10fff] [ 0.802083] pci 0002:00:00.0: bridge window [mem 0x9140000000-0x91417fffff] [ 0.809707] ACPI: PCI Root Bridge [PCI3] (domain 0003 [bus 00-ff]) [ 0.816279] acpi PNP0A08:02: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI] [ 0.825164] acpi PNP0A08:02: _OSC: OS now controls [PCIeHotplug PME AER PCIeCapability] [ 0.833672] acpi PNP0A08:02: MCFG quirk: ECAM at [mem 0xa0d0000000-0xa0dfffffff] for [bus 00-ff] with xgene_v1_pcie_ecam_ops [ 0.846518] acpi PNP0A08:02: [Firmware Bug]: ECAM area [mem 0xa0d0000000-0xa0dfffffff] not reserved in ACPI namespace [ 0.857822] acpi PNP0A08:02: ECAM at [mem 0xa0d0000000-0xa0dfffffff] for [bus 00-ff] [ 0.866063] Remapped I/O 0x000000a010000000 to [io 0x20000-0x2ffff window] [ 0.873565] PCI host bridge to bus 0003:00 [ 0.877899] pci_bus 0003:00: root bus resource [io 0x20000-0x2ffff window] (bus address [0x0000-0xffff]) [ 0.888044] pci_bus 0003:00: root bus resource [mem 0xa140000000-0xa17fffffff window] (bus address [0x40000000-0x7fffffff]) [ 0.899845] pci_bus 0003:00: root bus resource [mem 0xb000000000-0xbfffffffff window] [ 0.908151] pci_bus 0003:00: root bus resource [bus 00-ff] [ 0.914172] pci 0003:00:00.0: PCI bridge to [bus 01] [ 0.919692] xgene-msi APMC0D0E:00: APM X-Gene PCIe MSI driver loaded [ 0.926832] pci 0002:02:00.0: vgaarb: VGA device added: decodes=io+mem,owns=none,locks=none [ 0.935693] pci 0002:02:00.0: vgaarb: bridge control possible [ 0.941779] vgaarb: loaded [ 0.944736] SCSI subsystem initialized [ 0.948806] ACPI: bus type USB registered [ 0.953083] usbcore: registered new interface driver usbfs [ 0.958914] usbcore: registered new interface driver hub [ 0.964588] usbcore: registered new device driver usb [ 0.970044] Registered efivars operations [ 0.974676] NetLabel: Initializing [ 0.978274] NetLabel: domain hash size = 128 [ 0.982881] NetLabel: protocols = UNLABELED CIPSOv4 CALIPSO [ 0.988899] NetLabel: unlabeled traffic allowed by default [ 0.994947] clocksource: Switched to clocksource arch_sys_counter [ 1.020688] VFS: Disk quotas dquot_6.6.0 [ 1.024885] VFS: Dquot-cache hash table entries: 8192 (order 0, 65536 bytes) [ 1.032617] pnp: PnP ACPI init [ 1.036471] pnp: PnP ACPI: found 0 devices [ 1.043277] NET: Registered protocol family 2 [ 1.048136] TCP established hash table entries: 65536 (order: 3, 524288 bytes) [ 1.055981] TCP bind hash table entries: 65536 (order: 4, 1048576 bytes) [ 1.063453] TCP: Hash tables configured (established 65536 bind 65536) [ 1.070440] UDP hash table entries: 4096 (order: 1, 131072 bytes) [ 1.076974] UDP-Lite hash table entries: 4096 (order: 1, 131072 bytes) [ 1.084038] NET: Registered protocol family 1 [ 1.088793] Unpacking initramfs... [ 1.394774] Freeing initrd memory: 14208K [ 1.399373] hw perfevents: enabled with armv8_pmuv3_0 PMU driver, 5 counters available [ 1.407797] kvm [1]: 8-bit VMID [ 1.411109] kvm [1]: IDMAP page: 809cf000 [ 1.415355] kvm [1]: HYP VA range: 800000000000:ffffffffffff [ 1.421438] kvm [1]: Hyp mode initialized successfully [ 1.426896] kvm [1]: GICV region size/alignment is unsafe, using trapping (reduced performance) [ 1.436141] kvm [1]: vgic-v2@780cf000 [ 1.440089] kvm [1]: vgic interrupt IRQ1 [ 1.444251] kvm [1]: virtual timer IRQ3 [ 1.464992] audit: initializing netlink subsys (disabled) [ 1.470796] audit: type=2000 audit(1.210:1): state=initialized audit_enabled=0 res=1 [ 1.470955] Initialise system trusted keyrings [ 1.471013] workingset: timestamp_bits=44 max_order=17 bucket_order=0 [ 1.473109] zbud: loaded [ 1.553032] NET: Registered protocol family 38 [ 1.557778] Key type asymmetric registered [ 1.562119] Asymmetric key parser 'x509' registered [ 1.567314] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 251) [ 1.575231] io scheduler noop registered [ 1.579390] io scheduler deadline registered (default) [ 1.584870] io scheduler cfq registered [ 1.588942] io scheduler mq-deadline registered [ 1.593881] atomic64_test: passed [ 1.597701] xgene-gpio APMC0D14:00: X-Gene GPIO driver registered. [ 1.604834] pcieport 0000:00:00.0: AER enabled with IRQ 30 [ 1.610673] pcieport 0002:00:00.0: AER enabled with IRQ 31 [ 1.616545] pcieport 0003:00:00.0: AER enabled with IRQ 32 [ 1.622387] pcieport 0000:00:00.0: Signaling PME with IRQ 30 [ 1.628399] pcieport 0002:00:00.0: Signaling PME with IRQ 31 [ 1.634413] pcieport 0003:00:00.0: Signaling PME with IRQ 32 [ 1.640553] efifb: probing for efifb [ 1.644335] efifb: framebuffer at 0x40000000, using 1216k, total 1200k [ 1.651255] efifb: mode is 640x480x32, linelength=2560, pages=1 [ 1.657514] efifb: scrolling: redraw [ 1.661302] efifb: Truecolor: size=8:8:8:8, shift=24:0:8:16 [ 1.668723] Console: switching to colour frame buffer device 80x30 [ 1.676642] fb0: EFI VGA frame buffer device [ 1.681302] acpi ACPI0007:00: CPPC data invalid or not present [ 1.687504] acpi ACPI0007:01: CPPC data invalid or not present [ 1.693696] acpi ACPI0007:02: CPPC data invalid or not present [ 1.699865] acpi ACPI0007:03: CPPC data invalid or not present [ 1.706051] acpi ACPI0007:04: CPPC data invalid or not present [ 1.712232] acpi ACPI0007:05: CPPC data invalid or not present [ 1.718417] acpi ACPI0007:06: CPPC data invalid or not present [ 1.724598] acpi ACPI0007:07: CPPC data invalid or not present [ 1.730934] GHES: HEST is not enabled! [ 1.734915] ACPI GTDT: [Firmware Bug]: failed to get the Watchdog base address. [ 1.742794] Serial: 8250/16550 driver, 4 ports, IRQ sharing enabled [ 1.775138] console [ttyS0] disabled [ 1.799055] APMC0D08:00: ttyS0 at MMIO 0x1c020000 (irq = 33, base_baud = 3125000) is a U6_16550A [ 3.620494] console [ttyS0] enabled [ 3.620494] console [ttyS0] enabled [ 3.648008] APMC0D08:01: ttyS1 at MMIO 0x1c021000 (irq = 34, base_baud = 3125000) is a U6_16550A [ 3.648008] APMC0D08:01: ttyS1 at MMIO 0x1c021000 (irq = 34, base_baud = 3125000) is a U6_16550A [ 3.686451] APMC0D08:02: ttyS2 at MMIO 0x1c022000 (irq = 35, base_baud = 3125000) is a U6_16550A [ 3.686451] APMC0D08:02: ttyS2 at MMIO 0x1c022000 (irq = 35, base_baud = 3125000) is a U6_16550A [ 3.724876] APMC0D08:03: ttyS3 at MMIO 0x1c023000 (irq = 36, base_baud = 3125000) is a U6_16550A [ 3.724876] APMC0D08:03: ttyS3 at MMIO 0x1c023000 (irq = 36, base_baud = 3125000) is a U6_16550A [ 3.743860] rdac: device handler registered [ 3.743860] rdac: device handler registered [ 3.752523] hp_sw: device handler registered [ 3.752523] hp_sw: device handler registered [ 3.761295] emc: device handler registered [ 3.761295] emc: device handler registered [ 3.769786] alua: device handler registered [ 3.769786] alua: device handler registered [ 3.778554] libphy: Fixed MDIO Bus: probed [ 3.778554] libphy: Fixed MDIO Bus: probed [ 3.787093] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver [ 3.787093] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver [ 3.800497] ehci-pci: EHCI PCI platform driver [ 3.800497] ehci-pci: EHCI PCI platform driver [ 3.809613] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver [ 3.809613] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver [ 3.822301] ohci-pci: OHCI PCI platform driver [ 3.822301] ohci-pci: OHCI PCI platform driver [ 3.831437] uhci_hcd: USB Universal Host Controller Interface driver [ 3.831437] uhci_hcd: USB Universal Host Controller Interface driver [ 3.844583] xhci-hcd APMC0D03:00: xHCI Host Controller [ 3.844583] xhci-hcd APMC0D03:00: xHCI Host Controller [ 3.855201] xhci-hcd APMC0D03:00: new USB bus registered, assigned bus number 1 [ 3.855201] xhci-hcd APMC0D03:00: new USB bus registered, assigned bus number 1 [ 3.870420] xhci-hcd APMC0D03:00: hcc params 0x0220f06d hci version 0x100 quirks 0x00010010 [ 3.870420] xhci-hcd APMC0D03:00: hcc params 0x0220f06d hci version 0x100 quirks 0x00010010 [ 3.887600] xhci-hcd APMC0D03:00: irq 8, io mem 0x19000000 [ 3.887600] xhci-hcd APMC0D03:00: irq 8, io mem 0x19000000 [ 3.898927] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002 [ 3.898927] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002 [ 3.912856] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [ 3.912856] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [ 3.927698] usb usb1: Product: xHCI Host Controller [ 3.927698] usb usb1: Product: xHCI Host Controller [ 3.937711] usb usb1: Manufacturer: Linux 4.11.0-45.el7.aarch64 xhci-hcd [ 3.937711] usb usb1: Manufacturer: Linux 4.11.0-45.el7.aarch64 xhci-hcd [ 3.951482] usb usb1: SerialNumber: APMC0D03:00 [ 3.951482] usb usb1: SerialNumber: APMC0D03:00 [ 3.960963] hub 1-0:1.0: USB hub found [ 3.960963] hub 1-0:1.0: USB hub found [ 3.968677] hub 1-0:1.0: 1 port detected [ 3.968677] hub 1-0:1.0: 1 port detected [ 3.976827] xhci-hcd APMC0D03:00: xHCI Host Controller [ 3.976827] xhci-hcd APMC0D03:00: xHCI Host Controller [ 3.987450] xhci-hcd APMC0D03:00: new USB bus registered, assigned bus number 2 [ 3.987450] xhci-hcd APMC0D03:00: new USB bus registered, assigned bus number 2 [ 4.002491] usb usb2: We don't know the algorithms for LPM for this host, disabling LPM. [ 4.002491] usb usb2: We don't know the algorithms for LPM for this host, disabling LPM. [ 4.019161] usb usb2: New USB device found, idVendor=1d6b, idProduct=0003 [ 4.019161] usb usb2: New USB device found, idVendor=1d6b, idProduct=0003 [ 4.033107] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [ 4.033107] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [ 4.047941] usb usb2: Product: xHCI Host Controller [ 4.047941] usb usb2: Product: xHCI Host Controller [ 4.057955] usb usb2: Manufacturer: Linux 4.11.0-45.el7.aarch64 xhci-hcd [ 4.057955] usb usb2: Manufacturer: Linux 4.11.0-45.el7.aarch64 xhci-hcd [ 4.071726] usb usb2: SerialNumber: APMC0D03:00 [ 4.071726] usb usb2: SerialNumber: APMC0D03:00 [ 4.081174] hub 2-0:1.0: USB hub found [ 4.081174] hub 2-0:1.0: USB hub found [ 4.088904] hub 2-0:1.0: 1 port detected [ 4.088904] hub 2-0:1.0: 1 port detected [ 4.097088] xhci-hcd APMC0D03:01: xHCI Host Controller [ 4.097088] xhci-hcd APMC0D03:01: xHCI Host Controller [ 4.107690] xhci-hcd APMC0D03:01: new USB bus registered, assigned bus number 3 [ 4.107690] xhci-hcd APMC0D03:01: new USB bus registered, assigned bus number 3 [ 4.122850] xhci-hcd APMC0D03:01: hcc params 0x0220f06d hci version 0x100 quirks 0x00010010 [ 4.122850] xhci-hcd APMC0D03:01: hcc params 0x0220f06d hci version 0x100 quirks 0x00010010 [ 4.140039] xhci-hcd APMC0D03:01: irq 9, io mem 0x19800000 [ 4.140039] xhci-hcd APMC0D03:01: irq 9, io mem 0x19800000 [ 4.151359] usb usb3: New USB device found, idVendor=1d6b, idProduct=0002 [ 4.151359] usb usb3: New USB device found, idVendor=1d6b, idProduct=0002 [ 4.165298] usb usb3: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [ 4.165298] usb usb3: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [ 4.180131] usb usb3: Product: xHCI Host Controller [ 4.180131] usb usb3: Product: xHCI Host Controller [ 4.190153] usb usb3: Manufacturer: Linux 4.11.0-45.el7.aarch64 xhci-hcd [ 4.190153] usb usb3: Manufacturer: Linux 4.11.0-45.el7.aarch64 xhci-hcd [ 4.203919] usb usb3: SerialNumber: APMC0D03:01 [ 4.203919] usb usb3: SerialNumber: APMC0D03:01 [ 4.213494] hub 3-0:1.0: USB hub found [ 4.213494] hub 3-0:1.0: USB hub found [ 4.221206] hub 3-0:1.0: 1 port detected [ 4.221206] hub 3-0:1.0: 1 port detected [ 4.229351] xhci-hcd APMC0D03:01: xHCI Host Controller [ 4.229351] xhci-hcd APMC0D03:01: xHCI Host Controller [ 4.239951] xhci-hcd APMC0D03:01: new USB bus registered, assigned bus number 4 [ 4.239951] xhci-hcd APMC0D03:01: new USB bus registered, assigned bus number 4 [ 4.254999] usb usb4: We don't know the algorithms for LPM for this host, disabling LPM. [ 4.254999] usb usb4: We don't know the algorithms for LPM for this host, disabling LPM. [ 4.271663] usb usb4: New USB device found, idVendor=1d6b, idProduct=0003 [ 4.271663] usb usb4: New USB device found, idVendor=1d6b, idProduct=0003 [ 4.285613] usb usb4: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [ 4.285613] usb usb4: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [ 4.300457] usb usb4: Product: xHCI Host Controller [ 4.300457] usb usb4: Product: xHCI Host Controller [ 4.310464] usb usb4: Manufacturer: Linux 4.11.0-45.el7.aarch64 xhci-hcd [ 4.310464] usb usb4: Manufacturer: Linux 4.11.0-45.el7.aarch64 xhci-hcd [ 4.324236] usb usb4: SerialNumber: APMC0D03:01 [ 4.324236] usb usb4: SerialNumber: APMC0D03:01 [ 4.333712] hub 4-0:1.0: USB hub found [ 4.333712] hub 4-0:1.0: USB hub found [ 4.341444] hub 4-0:1.0: 1 port detected [ 4.341444] hub 4-0:1.0: 1 port detected [ 4.349643] usbcore: registered new interface driver usbserial [ 4.349643] usbcore: registered new interface driver usbserial [ 4.361644] usbcore: registered new interface driver usbserial_generic [ 4.361644] usbcore: registered new interface driver usbserial_generic [ 4.375055] usbserial: USB Serial support registered for generic [ 4.375055] usbserial: USB Serial support registered for generic [ 4.387444] mousedev: PS/2 mouse device common for all mice [ 4.387444] mousedev: PS/2 mouse device common for all mice [ 4.394961] usb 1-1: new high-speed USB device number 2 using xhci-hcd [ 4.394961] usb 1-1: new high-speed USB device number 2 using xhci-hcd [ 4.412427] rtc-efi rtc-efi: rtc core: registered rtc-efi as rtc0 [ 4.412427] rtc-efi rtc-efi: rtc core: registered rtc-efi as rtc0 [ 4.425250] EFI Variables Facility v0.08 2004-May-17 [ 4.425250] EFI Variables Facility v0.08 2004-May-17 [ 4.435637] hidraw: raw HID events driver (C) Jiri Kosina [ 4.435637] hidraw: raw HID events driver (C) Jiri Kosina [ 4.446809] usbcore: registered new interface driver usbhid [ 4.446809] usbcore: registered new interface driver usbhid [ 4.458264] usbhid: USB HID core driver [ 4.458264] usbhid: USB HID core driver [ 4.466275] drop_monitor: Initializing network drop monitor service [ 4.466275] drop_monitor: Initializing network drop monitor service [ 4.479235] Initializing XFRM netlink socket [ 4.479235] Initializing XFRM netlink socket [ 4.488159] NET: Registered protocol family 10 [ 4.488159] NET: Registered protocol family 10 [ 4.497643] Segment Routing with IPv6 [ 4.497643] Segment Routing with IPv6 [ 4.505184] NET: Registered protocol family 17 [ 4.505184] NET: Registered protocol family 17 [ 4.514570] registered taskstats version 1 [ 4.514570] registered taskstats version 1 [ 4.522977] Loading compiled-in X.509 certificates [ 4.522977] Loading compiled-in X.509 certificates [ 4.536243] alg: No test for pkcs1pad(rsa,sha1) (pkcs1pad(rsa-generic,sha1)) [ 4.536243] alg: No test for pkcs1pad(rsa,sha1) (pkcs1pad(rsa-generic,sha1)) [ 4.551638] Loaded X.509 cert 'CentOS Linux kernel signing key: 2dcaddc228df4f391be1f0c0517b9cb7a2e7ef34' [ 4.551638] Loaded X.509 cert 'CentOS Linux kernel signing key: 2dcaddc228df4f391be1f0c0517b9cb7a2e7ef34' [ 4.571344] zswap: loaded using pool lzo/zbud [ 4.571344] zswap: loaded using pool lzo/zbud [ 4.580771] usb 1-1: New USB device found, idVendor=0624, idProduct=0248 [ 4.580771] usb 1-1: New USB device found, idVendor=0624, idProduct=0248 [ 4.594532] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 4.594532] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 4.605236] Key type big_key registered [ 4.605236] Key type big_key registered [ 4.609085] rtc-efi rtc-efi: setting system clock to 2018-01-26 09:54:40 UTC (1516960480) [ 4.609085] rtc-efi rtc-efi: setting system clock to 2018-01-26 09:54:40 UTC (1516960480) [ 4.633727] usb 1-1: Product: Gadget USB HUB [ 4.633727] usb 1-1: Product: Gadget USB HUB [ 4.633730] usb 1-1: Manufacturer: no manufacturer [ 4.633730] usb 1-1: Manufacturer: no manufacturer [ 4.633732] usb 1-1: SerialNumber: 0123456789 [ 4.633732] usb 1-1: SerialNumber: 0123456789 [ 4.633743] usb 3-1: new high-speed USB device number 2 using xhci-hcd [ 4.633743] usb 3-1: new high-speed USB device number 2 using xhci-hcd [ 4.652422] hub 1-1:1.0: USB hub found [ 4.652422] hub 1-1:1.0: USB hub found [ 4.661306] hub 1-1:1.0: 5 ports detected [ 4.661306] hub 1-1:1.0: 5 ports detected
Arm-dev mailing list Arm-dev@centos.org https://lists.centos.org/mailman/listinfo/arm-dev
Jeremy,
Edit the grub command line and remove both or one of console= or earlycon= below
console=ttyS0,115200 earlycon=uart8250,mmio32,0x1c020000
to see if proceeds any further.
-Phong
-----Original Message----- From: Arm-dev [mailto:arm-dev-bounces@centos.org] On Behalf Of Jeremiah Rothschild Sent: Friday, January 26, 2018 5:04 PM To: Conversations around CentOS on ARM hardware Subject: Re: [Arm-dev] Kernel problems on APM X-Gene
On Fri, Jan 26, 2018 at 04:48:24PM +0700, Phong Vo wrote:
Jeremy,
Hi Phong. Thanks for the reply! Also, thank you for the tools & instructions to flash the Tianocore. That process worked great. :)
Is this on which board?
Gigabyte MP30-AR0 (uart0).
Unless you provide a log file, it is difficult to tell,
Understood. I have attached boot.log to this message. After this point, it freezes/hangs.
but latest CentOS 7.4 (kernel 4.11) boots fine on X-Gene platforms.
I am not sure how you built kernel, but this is what you can check. To boot X-Gene using acpi, you need to enable CONFIG_ARM64_ACPI_PARKING_PROTOCOL=y. CentOS (RPM) default configuration should already have this enabled.
Interesting. It is enabled in the failing kernel:
[root@hammer ~]# grep CONFIG_ARM64_ACPI_PARKING_PROTOCOL /boot/config-4.11.0-45.el7.aarch64 CONFIG_ARM64_ACPI_PARKING_PROTOCOL=y
but it is not enabled in the working kernel that Gordan built for me:
[root@hammer ~]# grep CONFIG_ARM64_ACPI_PARKING_PROTOCOL /boot/config-4.9.60-1.el7.centos.aarch64 [root@hammer ]#
-Phong
+-----Original Message----- +From: Arm-dev [mailto:arm-dev-bounces@centos.org] On Behalf Of +Jeremiah Rothschild +Sent: Friday, January 26, 2018 4:35 PM +To: Conversations around CentOS on ARM hardware +Subject: Re: [Arm-dev] Kernel problems on APM X-Gene
+On Sat, Nov 04, 2017 at 05:37:54PM +0000, Gordan Bobic wrote: +> Apologies for taking so long to return to this thread, it took way +> longer than expected to get to the machine and get it up and +> running +again.
+Thanks for the update & apologies as well on my delayed follow-up.
+Last time I wrote the mailing list about my kernel problems, I was +told (by jperrin@centos.org) that my system was not in a supported +state because I was daisy-chaining Tianocore EFI via U-Boot. I was +directed to flash the Tianocore firmware and remove U-Boot from the
equation.
+Although I was skeptical of this answer, I finally was able to do this.
+Unfortunately, however, this does not change behavior. I still cannot +successfully boot into any kernels beyond 4.5 unless I use 'acpi=off'.
+I am, interestingly enough, able to run the 4.9.60 kernel that you +supplied.
+So:
+(1) My experience leads me to believe that it is still a possibility +that a kernel related bug exists.
+(2) I am confused as to why your kernel worked. I built kernel-alt- +4.11.0-22.el7a from source and it fails like the others. Were there +any special steps you took in building the rpm's you supplied me?
+(3) Is it true that you are able to boot into the (> 4.5) distro- +supplied kernels? Or have you only tried/succeeded with your custom +builds?
+Thanks again!
+j
+> I also just updated the build to the latest 4.9.60. +> +> Here is a download link to both binaries and src.rpm (download the +> kernel tarball from kernel.org manually to build from src.rpm): +> http://ftp.redsleeve.org/pub/misc/kernel/aarch64/RPMS/ +> http://ftp.redsleeve.org/pub/misc/kernel/aarch64/SRPMS/ +> +> To recap - I am also running with Tianocore EFI chain-loaded from +> u-boot, and mainling 4.9.x boots just fine on it. +> +> No need for disabling ACPI on the kernel command line, no need to +> run EFI firmware as a 1st stage boot loader, it just works. +> Do feel free to try it - if that works for you but the distro +> supplied 4.5.x kernel doesn't, it seems reasonably conclusive that +> it is the CentOS kernel that is broken for this board. +> +> I'd also be interested in learning whether you have any luck +> getting PCIe cards to work with it without problems - I haven't +> tried it since upgrading to 4.9.x, but certainly on 4.4.x mainline +> the machine used to reliably lock up as soon as the driver for the
PCIe card loads.
+> +> Gordan +> +> +> On Fri, Sep 22, 2017 at 12:06 PM, Jeremiah Rothschild +> jeremiah@franz.com +> wrote: +> +> > On Fri, Sep 22, 2017 at 11:59:00AM +0100, Gordan Bobic wrote: +> > > On Fri, Sep 22, 2017 at 11:54 AM, Jeremiah Rothschild < +> > jeremiah@franz.com> +> > > wrote: +> > > +> > > > On Fri, Sep 22, 2017 at 11:39:19AM +0100, Gordan Bobic wrote: +> > > > > If you are interested, I'm more than happy to share my +> > > > > src.rpm for +> > 4.9.x, +> > > > > but won't be able to get to it before tomorrow morning as +> > > > > the +> > machine was +> > > > > recently mothballed. +> > > > +> > > > Thanks. I actually need to test with as new of a version as I +> > > > can +> > because I +> > > > have been experiencing an occasional "page allocation failure" +> > > > kernel panic. +> > > > No idea if/when that was fixed but I figure the newest +> > > > version is my +> > best +> > > > hope. +> > > > +> > > +> > > I've been on my own 4.9.x more or less since I got the machine, +> > > it was in +> > > 24/7 use, and I never experienced that issue. So it may be +> > > worth a cross-check with the kernel that I'm running to see +> > > whether the fault follows your machine or whether it is kernel
dependent.
+> > +> > You're right. It would be a good extra data point. Feel free to +> > mail me directly once you're sorted and I'll gladly check out +> > your 4.9 +build. +> > Thanks +> > again! +> > +> > +> > +> > > _______________________________________________ +> > > Arm-dev mailing list +> > > Arm-dev@centos.org +> > > https://lists.centos.org/mailman/listinfo/arm-dev +> > +> > _______________________________________________ +> > Arm-dev mailing list +> > Arm-dev@centos.org +> > https://lists.centos.org/mailman/listinfo/arm-dev +> >
+> _______________________________________________ +> Arm-dev mailing list +> Arm-dev@centos.org +> https://lists.centos.org/mailman/listinfo/arm-dev
+_______________________________________________ +Arm-dev mailing list +Arm-dev@centos.org +https://lists.centos.org/mailman/listinfo/arm-dev _______________________________________________ Arm-dev mailing list Arm-dev@centos.org https://lists.centos.org/mailman/listinfo/arm-dev
On Fri, Jan 26, 2018 at 10:07:03PM +0700, Phong Vo wrote:
Jeremy,
Edit the grub command line and remove both or one of console= or earlycon= below
console=ttyS0,115200 earlycon=uart8250,mmio32,0x1c020000
to see if proceeds any further.
Wow, removing "console=" worked! Can you please explain?
-Phong
-----Original Message----- From: Arm-dev [mailto:arm-dev-bounces@centos.org] On Behalf Of Jeremiah Rothschild Sent: Friday, January 26, 2018 5:04 PM To: Conversations around CentOS on ARM hardware Subject: Re: [Arm-dev] Kernel problems on APM X-Gene
On Fri, Jan 26, 2018 at 04:48:24PM +0700, Phong Vo wrote:
Jeremy,
Hi Phong. Thanks for the reply! Also, thank you for the tools & instructions to flash the Tianocore. That process worked great. :)
Is this on which board?
Gigabyte MP30-AR0 (uart0).
Unless you provide a log file, it is difficult to tell,
Understood. I have attached boot.log to this message. After this point, it freezes/hangs.
but latest CentOS 7.4 (kernel 4.11) boots fine on X-Gene platforms.
I am not sure how you built kernel, but this is what you can check. To boot X-Gene using acpi, you need to enable CONFIG_ARM64_ACPI_PARKING_PROTOCOL=y. CentOS (RPM) default configuration should already have this enabled.
Interesting. It is enabled in the failing kernel:
[root@hammer ~]# grep CONFIG_ARM64_ACPI_PARKING_PROTOCOL /boot/config-4.11.0-45.el7.aarch64 CONFIG_ARM64_ACPI_PARKING_PROTOCOL=y
but it is not enabled in the working kernel that Gordan built for me:
[root@hammer ~]# grep CONFIG_ARM64_ACPI_PARKING_PROTOCOL /boot/config-4.9.60-1.el7.centos.aarch64 [root@hammer ]#
-Phong
+-----Original Message----- +From: Arm-dev [mailto:arm-dev-bounces@centos.org] On Behalf Of +Jeremiah Rothschild +Sent: Friday, January 26, 2018 4:35 PM +To: Conversations around CentOS on ARM hardware +Subject: Re: [Arm-dev] Kernel problems on APM X-Gene
+On Sat, Nov 04, 2017 at 05:37:54PM +0000, Gordan Bobic wrote: +> Apologies for taking so long to return to this thread, it took way +> longer than expected to get to the machine and get it up and +> running +again.
+Thanks for the update & apologies as well on my delayed follow-up.
+Last time I wrote the mailing list about my kernel problems, I was +told (by jperrin@centos.org) that my system was not in a supported +state because I was daisy-chaining Tianocore EFI via U-Boot. I was +directed to flash the Tianocore firmware and remove U-Boot from the
equation.
+Although I was skeptical of this answer, I finally was able to do this.
+Unfortunately, however, this does not change behavior. I still cannot +successfully boot into any kernels beyond 4.5 unless I use 'acpi=off'.
+I am, interestingly enough, able to run the 4.9.60 kernel that you +supplied.
+So:
+(1) My experience leads me to believe that it is still a possibility +that a kernel related bug exists.
+(2) I am confused as to why your kernel worked. I built kernel-alt- +4.11.0-22.el7a from source and it fails like the others. Were there +any special steps you took in building the rpm's you supplied me?
+(3) Is it true that you are able to boot into the (> 4.5) distro- +supplied kernels? Or have you only tried/succeeded with your custom +builds?
+Thanks again!
+j
+> I also just updated the build to the latest 4.9.60. +> +> Here is a download link to both binaries and src.rpm (download the +> kernel tarball from kernel.org manually to build from src.rpm): +> http://ftp.redsleeve.org/pub/misc/kernel/aarch64/RPMS/ +> http://ftp.redsleeve.org/pub/misc/kernel/aarch64/SRPMS/ +> +> To recap - I am also running with Tianocore EFI chain-loaded from +> u-boot, and mainling 4.9.x boots just fine on it. +> +> No need for disabling ACPI on the kernel command line, no need to +> run EFI firmware as a 1st stage boot loader, it just works. +> Do feel free to try it - if that works for you but the distro +> supplied 4.5.x kernel doesn't, it seems reasonably conclusive that +> it is the CentOS kernel that is broken for this board. +> +> I'd also be interested in learning whether you have any luck +> getting PCIe cards to work with it without problems - I haven't +> tried it since upgrading to 4.9.x, but certainly on 4.4.x mainline +> the machine used to reliably lock up as soon as the driver for the
PCIe card loads.
+> +> Gordan +> +> +> On Fri, Sep 22, 2017 at 12:06 PM, Jeremiah Rothschild +> jeremiah@franz.com +> wrote: +> +> > On Fri, Sep 22, 2017 at 11:59:00AM +0100, Gordan Bobic wrote: +> > > On Fri, Sep 22, 2017 at 11:54 AM, Jeremiah Rothschild < +> > jeremiah@franz.com> +> > > wrote: +> > > +> > > > On Fri, Sep 22, 2017 at 11:39:19AM +0100, Gordan Bobic wrote: +> > > > > If you are interested, I'm more than happy to share my +> > > > > src.rpm for +> > 4.9.x, +> > > > > but won't be able to get to it before tomorrow morning as +> > > > > the +> > machine was +> > > > > recently mothballed. +> > > > +> > > > Thanks. I actually need to test with as new of a version as I +> > > > can +> > because I +> > > > have been experiencing an occasional "page allocation failure" +> > > > kernel panic. +> > > > No idea if/when that was fixed but I figure the newest +> > > > version is my +> > best +> > > > hope. +> > > > +> > > +> > > I've been on my own 4.9.x more or less since I got the machine, +> > > it was in +> > > 24/7 use, and I never experienced that issue. So it may be +> > > worth a cross-check with the kernel that I'm running to see +> > > whether the fault follows your machine or whether it is kernel
dependent.
+> > +> > You're right. It would be a good extra data point. Feel free to +> > mail me directly once you're sorted and I'll gladly check out +> > your 4.9 +build. +> > Thanks +> > again! +> > +> > +> > +> > > _______________________________________________ +> > > Arm-dev mailing list +> > > Arm-dev@centos.org +> > > https://lists.centos.org/mailman/listinfo/arm-dev +> > +> > _______________________________________________ +> > Arm-dev mailing list +> > Arm-dev@centos.org +> > https://lists.centos.org/mailman/listinfo/arm-dev +> >
+> _______________________________________________ +> Arm-dev mailing list +> Arm-dev@centos.org +> https://lists.centos.org/mailman/listinfo/arm-dev
+_______________________________________________ +Arm-dev mailing list +Arm-dev@centos.org +https://lists.centos.org/mailman/listinfo/arm-dev _______________________________________________ Arm-dev mailing list Arm-dev@centos.org https://lists.centos.org/mailman/listinfo/arm-dev
Arm-dev mailing list Arm-dev@centos.org https://lists.centos.org/mailman/listinfo/arm-dev
-----Original Message----- From: Arm-dev [mailto:arm-dev-bounces@centos.org] On Behalf Of Jeremiah Rothschild Sent: Saturday, January 27, 2018 3:18 AM To: Conversations around CentOS on ARM hardware Subject: Re: [Arm-dev] Kernel problems on APM X-Gene
On Fri, Jan 26, 2018 at 10:07:03PM +0700, Phong Vo wrote:
Jeremy,
Edit the grub command line and remove both or one of console= or earlycon= below
console=ttyS0,115200 earlycon=uart8250,mmio32,0x1c020000
to see if proceeds any further.
Wow, removing "console=" worked! Can you please explain?
The UARTSerialBus macro in Tianocore is used to define the characteristics of a slave device attached to the UART bus. It should be put in Resource template of a different Device node rather than the UART controller node. With a rather recent commit
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/ ?id=e361d1f85855ded967bd4803e8293445a6ce301a
the visible of UARTSerialBus forces ACPI subsystem to think that the UART controller node is a slave device node thus fails to open the console device.
-Phong
-----Original Message----- From: Arm-dev [mailto:arm-dev-bounces@centos.org] On Behalf Of Jeremiah Rothschild Sent: Friday, January 26, 2018 5:04 PM To: Conversations around CentOS on ARM hardware Subject: Re: [Arm-dev] Kernel problems on APM X-Gene
On Fri, Jan 26, 2018 at 04:48:24PM +0700, Phong Vo wrote:
Jeremy,
Hi Phong. Thanks for the reply! Also, thank you for the tools & instructions to flash the Tianocore. That process worked great. :)
Is this on which board?
Gigabyte MP30-AR0 (uart0).
Unless you provide a log file, it is difficult to tell,
Understood. I have attached boot.log to this message. After this point, it freezes/hangs.
but latest CentOS 7.4 (kernel 4.11) boots fine on X-Gene platforms.
I am not sure how you built kernel, but this is what you can check. To boot X-Gene using acpi, you need to enable CONFIG_ARM64_ACPI_PARKING_PROTOCOL=y. CentOS (RPM) default configuration should already have this enabled.
Interesting. It is enabled in the failing kernel:
[root@hammer ~]# grep CONFIG_ARM64_ACPI_PARKING_PROTOCOL /boot/config-4.11.0-45.el7.aarch64 CONFIG_ARM64_ACPI_PARKING_PROTOCOL=y
but it is not enabled in the working kernel that Gordan built for me:
[root@hammer ~]# grep CONFIG_ARM64_ACPI_PARKING_PROTOCOL /boot/config-4.9.60-1.el7.centos.aarch64 [root@hammer ]#
-Phong
+-----Original Message----- +From: Arm-dev [mailto:arm-dev-bounces@centos.org] On Behalf Of +Jeremiah Rothschild +Sent: Friday, January 26, 2018 4:35 PM +To: Conversations around CentOS on ARM hardware +Subject: Re: [Arm-dev] Kernel problems on APM X-Gene
+On Sat, Nov 04, 2017 at 05:37:54PM +0000, Gordan Bobic wrote: +> Apologies for taking so long to return to this thread, it took +> way longer than expected to get to the machine and get it up and +> running +again.
+Thanks for the update & apologies as well on my delayed follow-up.
+Last time I wrote the mailing list about my kernel problems, I was +told (by jperrin@centos.org) that my system was not in a supported +state because I was daisy-chaining Tianocore EFI via U-Boot. I was +directed to flash the Tianocore firmware and remove U-Boot from
the
equation.
+Although I was skeptical of this answer, I finally was able to do
this.
+Unfortunately, however, this does not change behavior. I still +cannot successfully boot into any kernels beyond 4.5 unless I use
'acpi=off'.
+I am, interestingly enough, able to run the 4.9.60 kernel that you +supplied.
+So:
+(1) My experience leads me to believe that it is still a +possibility that a kernel related bug exists.
+(2) I am confused as to why your kernel worked. I built kernel-
alt-
+4.11.0-22.el7a from source and it fails like the others. Were
there
+any special steps you took in building the rpm's you supplied me?
+(3) Is it true that you are able to boot into the (> 4.5) distro- +supplied kernels? Or have you only tried/succeeded with your
custom
+builds?
+Thanks again!
+j
+> I also just updated the build to the latest 4.9.60. +> +> Here is a download link to both binaries and src.rpm (download +> the kernel tarball from kernel.org manually to build from
src.rpm):
+> http://ftp.redsleeve.org/pub/misc/kernel/aarch64/RPMS/ +> http://ftp.redsleeve.org/pub/misc/kernel/aarch64/SRPMS/ +> +> To recap - I am also running with Tianocore EFI chain-loaded
from
+> u-boot, and mainling 4.9.x boots just fine on it. +> +> No need for disabling ACPI on the kernel command line, no need
to
+> run EFI firmware as a 1st stage boot loader, it just works. +> Do feel free to try it - if that works for you but the distro +> supplied 4.5.x kernel doesn't, it seems reasonably conclusive +> that it is the CentOS kernel that is broken for this board. +> +> I'd also be interested in learning whether you have any luck +> getting PCIe cards to work with it without problems - I haven't +> tried it since upgrading to 4.9.x, but certainly on 4.4.x +> mainline the machine used to reliably lock up as soon as the +> driver for the
PCIe card loads.
+> +> Gordan +> +> +> On Fri, Sep 22, 2017 at 12:06 PM, Jeremiah Rothschild +> jeremiah@franz.com +> wrote: +> +> > On Fri, Sep 22, 2017 at 11:59:00AM +0100, Gordan Bobic wrote: +> > > On Fri, Sep 22, 2017 at 11:54 AM, Jeremiah Rothschild < +> > jeremiah@franz.com> +> > > wrote: +> > > +> > > > On Fri, Sep 22, 2017 at 11:39:19AM +0100, Gordan Bobic
wrote:
+> > > > > If you are interested, I'm more than happy to share my +> > > > > src.rpm for +> > 4.9.x, +> > > > > but won't be able to get to it before tomorrow morning
as
+> > > > > the +> > machine was +> > > > > recently mothballed. +> > > > +> > > > Thanks. I actually need to test with as new of a version
as
+> > > > I can +> > because I +> > > > have been experiencing an occasional "page allocation
failure"
+> > > > kernel panic. +> > > > No idea if/when that was fixed but I figure the newest +> > > > version is my +> > best +> > > > hope. +> > > > +> > > +> > > I've been on my own 4.9.x more or less since I got the +> > > machine, it was in +> > > 24/7 use, and I never experienced that issue. So it may be +> > > worth a cross-check with the kernel that I'm running to see +> > > whether the fault follows your machine or whether it is +> > > kernel
dependent.
+> > +> > You're right. It would be a good extra data point. Feel free
to
+> > mail me directly once you're sorted and I'll gladly check out +> > your 4.9 +build. +> > Thanks +> > again! +> > +> > +> > +> > > _______________________________________________ +> > > Arm-dev mailing list +> > > Arm-dev@centos.org +> > > https://lists.centos.org/mailman/listinfo/arm-dev +> > +> > _______________________________________________ +> > Arm-dev mailing list +> > Arm-dev@centos.org +> > https://lists.centos.org/mailman/listinfo/arm-dev +> >
+> _______________________________________________ +> Arm-dev mailing list +> Arm-dev@centos.org +> https://lists.centos.org/mailman/listinfo/arm-dev
+_______________________________________________ +Arm-dev mailing list +Arm-dev@centos.org +https://lists.centos.org/mailman/listinfo/arm-dev _______________________________________________ Arm-dev mailing list Arm-dev@centos.org https://lists.centos.org/mailman/listinfo/arm-dev
Arm-dev mailing list Arm-dev@centos.org https://lists.centos.org/mailman/listinfo/arm-dev
Arm-dev mailing list Arm-dev@centos.org https://lists.centos.org/mailman/listinfo/arm-dev
-
Gordan Bobic -
Jeremiah Rothschild -
Phong Vo