Diff between Linux-2.6.27-omap1-dirty and Linux-2.6.27-omap1 ?

Hi All,

I am working on testing Linux-2.6.27 omap kernel on beagle board.

I cloned kernel from
git://git.kernel.org/pub/scm/linux/kernel/git/tmlind/linux-omap-2.6.git

and checked out to tag v2.6.27-omap1, I loaded kernel on beagle board,
and was able to boot properly like....

OMAP3 beagleboard.org # bootm 0x80300000
## Booting kernel from Legacy Image at 80300000 ...
   Image Name: Linux-2.6.27-omap1
   Image Type: ARM Linux Kernel Image (uncompressed)
   Data Size: 1614320 Bytes = 1.5 MB
   Load Address: 80008000
   Entry Point: 80008000
   Verifying Checksum ... OK
   Loading Kernel Image ... OK
OK

Now, I done some operations, like checkout to master, checkout to
v2.6.26-omap1 and v2.6.25-omap1, loaded corresponding uImages to
beagle board
and was able to boot board every time.

After this, I again checkout to v2.6.27-omap1, compiled and loaded
uImage to beagleboard
But this time I am not able to boot the board.
and Got the message like

OMAP3 beagleboard.org # bootm 0x80300000
## Booting kernel from Legacy Image at 80300000 ...
   Image Name: Linux-2.6.27-omap1-dirty
   Image Type: ARM Linux Kernel Image (uncompressed)
   Data Size: 1669176 Bytes = 1.6 MB
   Load Address: 80008000
   Entry Point: 80008000
   Verifying Checksum ... OK
   Loading Kernel Image ... OK
OK

Starting kernel ...

Uncompressing Linux...........................................................................................................
done, booting the kernel.

and it, stucks at here..

Here, the only difference I observed is "Image Name:
Linux-2.6.27-omap1" and "Image Name: Linux-2.6.27-omap1-dirty",
where uImage with second Image name is not booting.

I think, I have done something wrong here, while compilation and checkout.

I just want to know in what cases "-dirty" is appended to linux kernel
Image Names or anything I done wrong?

Thanks for your Helps.

Regards,
Shivdas

Shivdas Gujare wrote:

Hi All,

I am working on testing Linux-2.6.27 omap kernel on beagle board.

I cloned kernel from
git://git.kernel.org/pub/scm/linux/kernel/git/tmlind/linux-omap-2.6.git

and checked out to tag v2.6.27-omap1, I loaded kernel on beagle board,
and was able to boot properly like....

OMAP3 beagleboard.org # bootm 0x80300000
## Booting kernel from Legacy Image at 80300000 ...
   Image Name: Linux-2.6.27-omap1
   Image Type: ARM Linux Kernel Image (uncompressed)
   Data Size: 1614320 Bytes = 1.5 MB
   Load Address: 80008000
   Entry Point: 80008000
   Verifying Checksum ... OK
   Loading Kernel Image ... OK
OK

Now, I done some operations, like checkout to master, checkout to
v2.6.26-omap1 and v2.6.25-omap1, loaded corresponding uImages to
beagle board
and was able to boot board every time.

After this, I again checkout to v2.6.27-omap1, compiled and loaded
uImage to beagleboard
But this time I am not able to boot the board.
and Got the message like

OMAP3 beagleboard.org # bootm 0x80300000
## Booting kernel from Legacy Image at 80300000 ...
   Image Name: Linux-2.6.27-omap1-dirty
   Image Type: ARM Linux Kernel Image (uncompressed)
   Data Size: 1669176 Bytes = 1.6 MB
   Load Address: 80008000
   Entry Point: 80008000
   Verifying Checksum ... OK
   Loading Kernel Image ... OK
OK

Starting kernel ...

Uncompressing Linux...........................................................................................................
done, booting the kernel.

and it, stucks at here..

Here, the only difference I observed is "Image Name:
Linux-2.6.27-omap1" and "Image Name: Linux-2.6.27-omap1-dirty",
where uImage with second Image name is not booting.

I think, I have done something wrong here, while compilation and checkout.

I just want to know in what cases "-dirty" is appended to linux kernel
Image Names or anything I done wrong?

-dirty is appended to the version string when there are differences between the working tree and the git HEAD. In other words, it sounds like you accidentally modified some file.

You can see which files have been modified with "git status". It will also show extra files under "untracked"; you may see a few arch-specific object files, but all the .o, .ko, etc. files will be hidden by virtue of gitignore.

If the files were modified before the last "git checkout", it would have tried to preserve the modifications. It would also warn you by listing the files, with an "M" next to their name.

Hope that helps. You described your problem very well, btw.

Regards
Alan

I also have this problem, even git-tree is not dirty.
Why?

Thanks!

* Ming Lei <tom.leiming@gmail.com> [081031 21:26]:

I also have this problem, even git-tree is not dirty.
Why?

Looks like you've hit the ptebits problem.. See the arm-linux-kernel
mailing list archive or linux-omap list today for an experimental
patch to fix it.

Tony