Re: Invalid module format

On Sun, Feb 25, 2018 at 12:04:30AM -0500, valdis.kletni...@vt.edu wrote: > On Sun, 25 Feb 2018 13:34:41 +1100, "Tobin C. Harding" said: > > On Fri, Feb 23, 2018 at 10:06:14PM -0500, valdis.kletni...@vt.edu wrote: > > > OK, I'll bite - how can the kernel go into a reboot loop that doesn't get > >

Re: Year 2038 time set problem

On Sat, 24 Feb 2018 19:29:35 +0530, techi eth said: > I am trying on 32 Bit micro board with ubifs file system with Linux Kernel > 4.1. Is this board something that has a realistic expectation of still being in use in 2038? What's making you worry about 2038 issues? I'm willing to bet that the

Re: Invalid module format

On Sun, 25 Feb 2018 13:34:41 +1100, "Tobin C. Harding" said: > On Fri, Feb 23, 2018 at 10:06:14PM -0500, valdis.kletni...@vt.edu wrote: > > OK, I'll bite - how can the kernel go into a reboot loop that doesn't get > > to the > > grub menu? (Hint: How does your system get from the BIOS splash

Re: Invalid module format

On Fri, Feb 23, 2018 at 10:06:14PM -0500, valdis.kletni...@vt.edu wrote: > On Sat, 24 Feb 2018 10:29:33 +1100, "Tobin C. Harding" said: > > > (For the record I happened to be trying to learn about linux-next myself > > this morning and built a kernel that just goes into a reboot loop > > without

Re: Year 2038 time set problem

On Sat, Feb 24, 2018 at 07:29:35PM +0530, techi eth wrote: > I am trying on 32 Bit micro board with ubifs file system with Linux Kernel > 4.1. And in your testing, did you find any problems? Also note that the 4.1 kernel is very old and obsolete and insecure, and should NOT be used for any

Re: Year 2038 time set problem

I am trying on 32 Bit micro board with ubifs file system with Linux Kernel 4.1. On Fri, Feb 23, 2018 at 6:48 PM, wrote: > On Fri, 23 Feb 2018 15:13:30 +0530, techi eth said: > > > Which Linux kernel version have Year 2038 problem solved for Linux > running > > on 32