I just got a chance to test the 4.16.0-0.rc2 kernel using the 20180220
Xfce Rawhide Spin. It fails to boot due to a kernel paging request.
Here are the snippets:
U-Boot 2018.03-rc2 (Feb 16 2018 - 14:14:52 +0000) for ODROID-XU3/XU4/HC1
CPU: Exynos5422 @ 800 MHz
Model: Odroid XU3 based on EXYNOS5422
Board: Odroid XU3 based on EXYNOS5422
DRAM: 2 GiB
MMC: EXYNOS DWMMC: 0, EXYNOS DWMMC: 1
Loading Environment from MMC... *** Warning - bad CRC, using default
Net: No ethernet found.
Hit any key to stop autoboot: 0
mmc_init: -5, time 6
switch to partitions #0, OK
mmc0 is current device
Scanning mmc 0:2...
Retrieving file: /extlinux/extlinux.conf
591 bytes read in 14 ms (41 KiB/s)
Ignoring unknown command: ui
Ignoring malformed menu command: autoboot
Ignoring malformed menu command: hidden
Ignoring unknown command: totaltimeout
Fedora-Xfce-armhfp-Rawhide-20180220.n.0 Boot Options.
Enter choice: 1: Fedora-Xfce-armhfp-Rawhide-20180220.n.0
Retrieving file: /initramfs-4.16.0-0.rc2.git0.1.fc28.armv7hl.img
54271696 bytes read in 4082 ms (12.7 MiB/s)
Retrieving file: /vmlinuz-4.16.0-0.rc2.git0.1.fc28.armv7hl
6660608 bytes read in 519 ms (12.2 MiB/s)
append: ro root=UUID=7d9c6236-7437-49c9-9e30-cf5ba8d147d5 cma=192MB
56970 bytes read in 508 ms (109.4 KiB/s)
Kernel image @ 0x42000000 [ 0x000000 - 0x65a200 ]
## Flattened Device Tree blob at 43000000
Booting using the fdt blob at 0x43000000
Loading Ramdisk to 4cc3e000, end 4ffffed0 ... OK
Loading Device Tree to 4cc2d000, end 4cc3de89 ... OK
Starting kernel ...
[ 0.000000] Booting Linux on physical CPU 0x100
[ 0.000000] Linux version 4.16.0-0.rc2.git0.1.fc28.armv7hl
(mockbuild(a)buildvm-armv7-07.arm.fedoraproject.org) (gcc version
8.0.1 20180218 8
[ 0.000000] CPU: ARMv7 Processor [410fc073] revision 3 (ARMv7),
[ 6.366866] 12c30000.serial: ttySAC3 at MMIO 0x12c30000 (irq =
61, base_baud = 0) is a S3C6400/10
[ 6.377630] msm_serial: driver initialized
[ 6.380655] STMicroelectronics ASC driver initialized
[ 6.390013] libphy: Fixed MDIO Bus: probed
[ 6.393299] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI)
[ 6.399194] ehci-pci: EHCI PCI platform driver
[ 6.403631] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
[ 6.409762] ohci-pci: OHCI PCI platform driver
[ 6.414203] uhci_hcd: USB Universal Host Controller Interface driver
[ 6.420729] usbcore: registered new interface driver
[ 6.427020] usbserial: USB Serial support registered for generic
[ 6.433186] mousedev: PS/2 mouse device common for all mice
[ 6.445564] device-mapper: uevent: version 1.0.3
[ 6.449213] device-mapper: ioctl: 4.37.0-ioctl (2017-09-20)
[ 6.461297] ledtrig-cpu: registered to indicate activity on CPUs
[ 6.466198] hidraw: raw HID events driver (C) Jiri Kosina
[ 6.471445] usbcore: registered new interface driver usbhid
[ 6.476783] usbhid: USB HID core driver
[ 6.483709] drop_monitor: Initializing network drop monitor service
[ 6.489025] Initializing XFRM netlink socket
[ 6.493716] NET: Registered protocol family 10
[ 8.028149] Unable to handle kernel paging request at virtual
On 02/22/2018 12:01 PM, Peter Robinson wrote:
On Thu, Feb 22, 2018 at 7:52 PM, Stewart Samuels
> On 02/22/2018 11:39 AM, Peter Robinson wrote:
>> On Thu, Feb 22, 2018 at 7:24 PM, Stewart Samuels <searider74(a)gmail.com>
>>> Hi Peter,
>>> I just got a chance to update my Odroid Xu4 with the latest updates for
>>> All was working fine with the exceptions for the Exynos 5 USB-3 issues
>>> to this upgrade. After the upgrade and a reboot, my system no longer
>>> into graphics mode. It seems to be failing somewhere along the line with
>>> udev, but I am not certain of this. The system will eventually boot into
>>> non-graphics mode, which can be seen when connecting the serial port and
>>> watching the boot messages.
>>> As I mentioned in previous posts, the Rawhide Spins all seem to have this
>>> issue too. In fact, they have had the problem for a long time now. On
>>> positive side, both this release of F27 updates and the Rawhide spins do
>>> seem to have the USB-3 issues fixed.
>> Can you try the 4.16rc2 kernel  and see if that has the same
>> issues. The 4.16 kernel might help as there was a bunch of stuff that
>> changed in the exynos drm driver.
> Looking at the builds in this URL I see "rawhide" listed as one of the
> "Tasks". Doe this mean the current rawhide build are already including
> kernel-4.16.0-0.rc2 kernel?
Yes, and the just branched F-28 will as well. So you can do an upgrade
to F-28 and get it there too
>>> Attached, is a MS Word formatted file of my boot log. Hope this helps.
>> Please don't do that, word processing docs are really not the way to
>> handle this in open source just fpaste it or something. If it's booted
>> just do "dmesg | fpaste" and provide the URL.
>>> On 02/12/2018 09:56 AM, Peter Robinson wrote:
>>>> Hi All,
>>>> Just a heads up that the 4.15 kernel is headed to stable releases.
>>>> I did a bunch of testing over the weekend and fixed up a bunch of
>>>> issues, added some minor enhancements across a number of platforms.
>>>> There is a kernel-4.15.2-301.fc27 build  which had all those fixes
>>>> for people to test, I expect a 4.15.3 kernel going to updates-testing
>>>> later today or tomorrow.
>>>> A few notes for the fixes I added:
>>>> * fixed cpufreq/thermal on i.MX6 (thanks kwizart for upstream fix)
>>>> * Crypto/rng engine on some AllWinner devices now loads/works
>>>> (A10/A143/A20 at least, I suspect more will come with later kernels)
>>>> * Exynos 5 USB-3 issue should now be fixed once and for all (I hope)
>>>> * A bunch of improvements for monitor detection on the Raspberry Pi
>>>> * Ethernet driver more stable on AllWInner A64/H5 platforms (like
>>>> * Numerous other upstream fixes improvements that headed upstream
>>>> * 4.15.3 (not in the build above) will include aarch64 fixes for
>>>> So please test and feel free to reply to this thread with any new
>>>> issues you see with the 4.15 series, or any positive results.
>>>>  https://koji.fedoraproject.org/koji/taskinfo?taskID=24966088
>>>> arm mailing list -- arm(a)lists.fedoraproject.org
>>>> To unsubscribe send an email to arm-leave(a)lists.fedoraproject.org