On Sat, Feb 24, 2018 at 4:40 AM, Stewart Samuels <searider74@xxxxxxxxx> wrote: > 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: > > [ 8.028149] Unable to handle kernel paging request at virtual address fffffffc Wow kernel, thanks, it's very useful :-/ Was there any further output after this? The kernel would normally spit out a full traceback right after this line. There's some fixes for the exynos landed for rc3 so might be worth trying that one when it lands next week. P > > Stewart > > > > > > On 02/22/2018 12:01 PM, Peter Robinson wrote: > > On Thu, Feb 22, 2018 at 7:52 PM, Stewart Samuels <searider74@xxxxxxxxx> > wrote: > > On 02/22/2018 11:39 AM, Peter Robinson wrote: > > On Thu, Feb 22, 2018 at 7:24 PM, Stewart Samuels <searider74@xxxxxxxxx> > wrote: > > Hi Peter, > > I just got a chance to update my Odroid Xu4 with the latest updates for > F27. > All was working fine with the exceptions for the Exynos 5 USB-3 issues > prior > to this upgrade. After the upgrade and a reboot, my system no longer > boots > 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 > the > 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 [1] 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. > > https://koji.fedoraproject.org/koji/buildinfo?buildID=1046448 > > 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 the > 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. > > Regards, > Stewart > > > 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 [1] 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 > Pine64) > * Numerous other upstream fixes improvements that headed upstream > * 4.15.3 (not in the build above) will include aarch64 fixes for > Spectre/Meltdown. > > 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. > > [1] https://koji.fedoraproject.org/koji/taskinfo?taskID=24966088 > _______________________________________________ > arm mailing list -- arm@xxxxxxxxxxxxxxxxxxxxxxx > To unsubscribe send an email to arm-leave@xxxxxxxxxxxxxxxxxxxxxxx > > > > _______________________________________________ > arm mailing list -- arm@xxxxxxxxxxxxxxxxxxxxxxx > To unsubscribe send an email to arm-leave@xxxxxxxxxxxxxxxxxxxxxxx > _______________________________________________ arm mailing list -- arm@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to arm-leave@xxxxxxxxxxxxxxxxxxxxxxx
