lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Mon, 3 Nov 2008 13:04:59 -0800 From: Tony Lindgren <tony@...mide.com> To: Ming Lei <tom.leiming@...il.com> Cc: beagleboard@...glegroups.com, linux-kernel@...r.kernel.org Subject: Re: [beagleboard] Diff between Linux-2.6.27-omap1-dirty and Linux-2.6.27-omap1 ? * Ming Lei <tom.leiming@...il.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 > > Thanks! > ------------------------------------------------------------ > Texas Instruments X-Loader 1.41 > Starting OS Bootloader... > > > U-Boot 1.3.3 (Jul 10 2008 - 16:33:09) > > OMAP3530-GP rev 2, CPU-OPP2 L3-165MHz > OMAP3 Beagle Board + LPDDR/NAND > DRAM: 128 MB > NAND: 256 MiB > In: serial > Out: serial > Err: serial > Audio Tone on Speakers ... complete > Hit any key to stop autoboot: 0 > OMAP3 beagleboard.org # > OMAP3 beagleboard.org # > OMAP3 beagleboard.org # printenv > bootargs=console=ttyS2,115200n8 ramdisk_size=8192 root=/dev/ram0 rw > rootfstype=ext2 initrd=0x81600000f > bootcmd=mmcinit;fatload mmc 0 0x80300000 uImage;fatload mmc 0 > 0x81600000 rd-ext2.bin;bootm 0x80300000 > stdin=serial > stdout=serial > stderr=serial > > Environment size: 257/131068 bytes > OMAP3 beagleboard.org # mmcinit;fatload mmc 0 0x80300000 ui3;bootm 0x80300000 > reading ui3 > > 1723104 bytes read > ## Booting kernel from Legacy Image at 80300000 ... > Image Name: Linux-2.6.28-rc2-omap1-05147-g82 > Image Type: ARM Linux Kernel Image (uncompressed) > Data Size: 1723040 Bytes = 1.6 MB > Load Address: 80008000 > Entry Point: 80008000 > Verifying Checksum ... OK > Loading Kernel Image ... OK > OK > > Starting kernel ... > > Uncompressing Linux................................................................................... > > > > > 2008/10/31 Shivdas Gujare <shivdas.tech@...il.com>: > > > > 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 > > > > --~--~---------~--~----~------------~-------~--~----~ > > You received this message because you are subscribed to the Google Groups "Beagle Board" group. > > To post to this group, send email to discussion@...gleboard.org. > > To unsubscribe from this group, send email to beagleboard-unsubscribe@...gleboard.org > > For more options, visit this group at http://groups.google.com/group/beagleboard?hl=en > > -~----------~----~----~----~------~----~------~--~--- > > > > > > > > -- > Lei Ming > -- > To unsubscribe from this list: send the line "unsubscribe linux-kernel" in > the body of a message to majordomo@...r.kernel.org > More majordomo info at http://vger.kernel.org/majordomo-info.html > Please read the FAQ at http://www.tux.org/lkml/ -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists