Possible kernel bug

[exploder]

I noticed when I ran mylivecd I had errors saying "file stamp in the future". This seemed odd and I checked the time settings in the BIOS, the time was 4 hrs ahead. I re-set the time and watched all of the text when the system booted up, the kernel found a superblock error and re-set the time. I rebooted and the system clock was again 4 hrs ahead. This was with the 2.6.38-4 bfs kernel. I found the exact same thing on my other machine using the 2.6.38-4 bfs pae kernel.

I installed the 2.6.37-4 pae kernel and ran mylivecd on the second machine, the timestamp errors were gone but the system clock was still being put 4 hrs ahead. Granted I have cheap hardware but 2 machines having the same issue makes me wonder if their might be a problem with the kernel. The operating systems clock stays set, I used the proper tool in the "Configure Your Computer" tools.

It is totally possible I made a mistake in my configuration but I figured there was no harm in asking and if there is a problem with the kernel or tool that sets the time you would want to be aware of it. Both computers run fine and the remastered iso's I made both worked despite the errors I saw in the konsole.

[AS]

Hello exploder,

me too noticed this behavior, but as far as I can understand this is not related to kernel, but to the default timezone, which is set up to Texas. 
I need to investigate further about this issue ... if I remember correctly, if you fix the timezone and date/time before to perform the install the problem doesn't occurs.

AS

[exploder]

me too noticed this behavior, but as far as I can understand this is not related to kernel, but to the default timezone, which is set up to Texas.  Wink
I need to investigate further about this issue ... if I remember correctly, if you fix the timezone and date/time before to perform the install the problem doesn't occurs.

What you are saying makes sense. I wonder if there is a way to fix this in the installed system? I got to thinking, this did not effect mylivecd in the e17 mini beta 2, so is it possible the KDE tool for setting the time interferes with the proper system tool? I would hate to have to do a re-install on both computers to fix this.

Edit: I will wait and see if someone knows a solution for this. I have both these machines set up so nice I would hate to start all over again...

[AS]

me too noticed this behavior, but as far as I can understand this is not related to kernel, but to the default timezone, which is set up to Texas.  Wink
I need to investigate further about this issue ... if I remember correctly, if you fix the timezone and date/time before to perform the install the problem doesn't occurs.

What you are saying makes sense. I wonder if there is a way to fix this in the installed system? I got to thinking, this did not effect mylivecd in the e17 mini beta 2, so is it possible the KDE tool for setting the time interferes with the proper system tool? I would hate to have to do a re-install on both computers to fix this.

As said before, don't know much, I noticed this while installing / remastering some ISO in virtual box, at that time I didn't care about time/timezone because it was a test system ... but don't think you need to reinstall.

I noticed when I ran mylivecd I had errors saying "file stamp in the future"

Then, identify the files (best using --verbose option of mylivecd), then check date time using ls -l, eventually change the date time using touch <filename>
anyway ... untested ... so far. 

AS

[exploder]

As said before, don't know much, I noticed this while installing / remastering some ISO in virtual box, at that time I didn't care about time/timezone because it was a test system ... but don't think you need to reinstall.

I have never encountered this either and I agree that there probably is a solution for it. I also remastered in Virtualbox before installing on both computers.

[exploder]

I do not think reinstalling is the answer. I reinstalled from the remastered CD, it had the timezone set to FT Wayne and the problem is still present.

Edit: It is odd that with the 2.6.38 kernels I get the timestamp errors with mylivecd but with the 2.6.37 kernels I do not get the timestamp errors with mylivecd. Both kernels still change the BIOS settings though. This has really got me stumped.... Reinstalling with the timezone properly set did not fix the problem, neither did setting KDE's utility and the PCLinuxOS tool to the same timezone. Is there a way to set the kernel to not adjust the time in the BIOS?

Edit: I kept messing with the machine with the 2.6.38 bfs kernel and the errors in mylivecd magically went away, the BIOS still thinks I am in Texas but it is not hurting anything. I still do not understand this but since everything is working I am not going to worry about the BIOS settings.