From apgmoorthi@hotmail.com Mon Aug 25 06:01:18 2008 Received: from blu0-omc1-s1.blu0.hotmail.com ([65.55.116.12]) by stoneboat.aleph1.co.uk with esmtp (Exim 4.63) (envelope-from ) id 1KXUCL-0001hL-Cm for yaffs@lists.aleph1.co.uk; Mon, 25 Aug 2008 06:01:18 +0100 Received: from BLU149-W38 ([65.55.116.9]) by blu0-omc1-s1.blu0.hotmail.com with Microsoft SMTPSVC(6.0.3790.3959); Sun, 24 Aug 2008 22:00:55 -0700 Message-ID: Content-Type: multipart/alternative; boundary="_1c5670a3-1102-42ab-81ba-fad32f71ca5b_" X-Originating-IP: [203.78.214.150] From: Gangheya moorthy To: Date: Mon, 25 Aug 2008 10:30:55 +0530 Importance: Normal In-Reply-To: References: MIME-Version: 1.0 X-OriginalArrivalTime: 25 Aug 2008 05:00:55.0420 (UTC) FILETIME=[8E3BF3C0:01C9066F] X-SA-Exim-Connect-IP: 65.55.116.12 X-SA-Exim-Mail-From: apgmoorthi@hotmail.com X-Spam-Checker-Version: SpamAssassin 3.2.3 (2007-08-08) on stoneboat.aleph1.co.uk X-Spam-Level: X-Spam-Status: No, score=-2.6 required=5.0 tests=AWL,BAYES_00,HTML_MESSAGE, SPF_PASS autolearn=ham version=3.2.3 X-SA-Exim-Version: 4.2.1 (built Tue, 09 Jan 2007 17:23:22 +0000) X-SA-Exim-Scanned: Yes (on stoneboat.aleph1.co.uk) Subject: [Yaffs] YAFFS2 issue with fsstress X-BeenThere: yaffs@lists.aleph1.co.uk X-Mailman-Version: 2.1.9 Precedence: list List-Id: Discussion of YAFFS NAND flash filesystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 25 Aug 2008 05:01:18 -0000 --_1c5670a3-1102-42ab-81ba-fad32f71ca5b_ Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Hi=2C =20 When YAFFS2 is stress tested with fsstress =2C after nearly an hour all= the fsstress process goes to D-state. =20 Set up is 2.6.22 Kernel version on OMAP Board with OneNAND (2G ) as MTD =20 and with cat /proc/yaffs =20 Free space is 2MB (Intial Ram size -64MB) and the Gross lock count is -1. =20 When we did some permutation and combination in the operations listed in fs= stress =2C=20 found that when 'symlink' operation is taken out from the execution list of= fsstress. Everthing goes fine with the same setup. =20 On going through symlink implmenetation have seen that the alias string mem= allocation done in the clone string function =2C is freed only in unlink o= r unmount. =20 Is this understanding correct ? If it is right then why to have the copy always on RAM ( yes till unlink or= unmount) ?=20 But still why the fsstress process going to d-State 'coz of symlink =2C is = there is someother issue in symlink ? =20 Please do guide me and throw some light on this . =20 Let me know more on any clarification required. =20 Thanks in advance. =20 With Regards =20 Moorthy =20 =20 =20 > From: yaffs-request@lists.aleph1.co.uk> Subject: yaffs Digest=2C Vol 39= =2C Issue 14> To: yaffs@lists.aleph1.co.uk> Date: Sat=2C 23 Aug 2008 12:00:= 04 +0100> > Send yaffs mailing list submissions to> yaffs@lists.aleph1.co.u= k> > To subscribe or unsubscribe via the World Wide Web=2C visit> http://li= sts.aleph1.co.uk/cgi-bin/mailman/listinfo/yaffs> or=2C via email=2C send a = message with subject or body 'help' to> yaffs-request@lists.aleph1.co.uk> >= You can reach the person managing the list at> yaffs-owner@lists.aleph1.co= .uk> > When replying=2C please edit your Subject line so it is more specifi= c> than "Re: Contents of yaffs digest..."> > > Today's Topics:> > 1. YAFFS2= and HIGHMEM (Ajit.Prem@Emerson.com)> 2. Re: porting yaffs2 to linux user m= ode (Charles Manning)> > > ------------------------------------------------= ----------------------> > Message: 1> Date: Fri=2C 22 Aug 2008 14:32:12 -05= 00> From: > Subject: [Yaffs] YAFFS2 and HIGHMEM> To:= > Message-ID:> <403DA57433416541B977A593BBEAE400= 2CBA42@etsmsg-slexm02.etsmsg.org>> Content-Type: text/plain=3B charset=3D"u= s-ascii"> > Hello=2C> > Does YAFFS2 work on boards which use HIGHMEM? I hav= e a PowerPC board> that comes in 1G and 2G variants. YAFFS works just fine = on the 1G board> and works just fine on the 2G board if I boot with mem=3D1= G (HIGHMEM> starts above 1G on this board). Everything but YAFFS work just = fine on> the 2G board when the full 2G is used=2C so there isn't a HIGHMEM = issue on> the board. > > YAFFS works well enough on these boards to allow u= sing a root file> system on NAND. However=2C when I try a simple write to a= YAFFS partition> on a 2G board configured to use the full 2G=2C I get the = following crash.> I don't seem to be the only one with this issue. My board= is based on a> dual-core 8641D PowerPC. Mathias Fuchs reported exactly the= same problem> on a 1G 44O board. The posting can be found with a google se= arch for the> item "HIGHMEM on 440EPx board with 1GB of RAM". On Matthias' = board> HIGHMEM started at 768M. When Matthias reconfigured his kernel so th= at> he could use the full 1G as low memory=2C his YAFFS problems went away.= > > > # mount -t yaffs2 /dev/mtdblock4 /mnt> # cd /mnt> # cp -a /etc .> > -= -----------[ cut here ]------------> Kernel BUG at 8013cd0c [verbose debug = info unavailable]> Oops: Exception in kernel mode=2C sig: 5 [#1] > PREEMPT = SMP NR_CPUS=3D2 > Modules linked in:> NIP: 8013CD0C LR: 8013CD0C CTR: 8003E= 24C> REGS: 8fb53a00 TRAP: 0700 Not tainted (2.6.20)> MSR: 00029032 CR: 24422428 XER: 00000000 > TASK =3D 842652d0[626] 'cp' THREAD= : 8fb52000 CPU: 0> GPR00: 8013CD0C 8FB53AB0 842652D0 00000012 6419EFF8 F026= 6C8C 3F664DCF> 00000000> GPR08: 00000610 00000000 10000000 8FB52000 3852626= 8 10024A08 80400000> 00001000> GPR16: BD37E368 8FB53C38 8FB53C3C 00000000 0= 0000000 00000000 8FB53BC0> 00000000> GPR24: 00000000 00000001 00000000 8427= 2980 00000000 004C2000 8FB53BC0> BD318000 > NIP [8013CD0C] nandmtd2_WriteCh= unkWithTagsToNAND+0xe8/0xf0> LR [8013CD0C] nandmtd2_WriteChunkWithTagsToNAN= D+0xe8/0xf0> Call Trace:> [8FB53AB0] [8013CD0C] nandmtd2_WriteChunkWithTags= ToNAND+0xe8/0xf0> (unreliable) > [8FB53B10] [8013ACDC] yaffs_WriteChunkWith= TagsToNAND+0x90/0x140> [8FB53B30] [80133C64] yaffs_WriteNewChunkWithTagsToN= AND+0x3d4/0x538> [8FB53B70] [80135BE0] yaffs_WriteChunkDataToObject+0x94/0x= e8> [8FB53C30] [80136304] yaffs_WriteDataToFile+0x214/0x2e0 > [8FB53C90] [8= 012FE04] yaffs_commit_write+0x120/0x2bc > [8FB53CD0] [800513D8] generic_fil= e_buffered_write+0x3cc/0xa2c> [8FB53D90] [80052E48] __generic_file_aio_writ= e_nolock+0x314/0x5bc> [8FB53E00] [80053158] generic_file_aio_write+0x68/0x1= 0c > [8FB53E30] [80078F88] do_sync_write+0xc0/0x134 > [8FB53EF0] [80079628]= vfs_write+0xf4/0x1bc > [8FB53F10] [8007A210] sys_write+0x4c/0x90 > [8FB53F= 40] [80011458] ret_from_syscall+0x0/0x38> --- Exception: c01 at 0xff69874> = LR =3D 0x10008670> Instruction dump:> 80010064 38210060 7c0803a6 4e800020 3= c608038 386378bc 4bee9125 0fe00000> 48000000 3c608038 38637908 4bee9111 <0f= e00000> 48000000 7c0802a6> 9421ff90 > > > > Some other info:> > -- part of = boot log> > Creating 4 MTD partitions on "mvme7100-flash":> 0x00000000-0x01= 000000 : "Linux Kernel + INITRD"> 0x01000000-0x07e00000 : "Linux JFFS2 File= system"> 0x07e00000-0x07f00000 : "Bootloader Block B"> 0x07f00000-0x0800000= 0 : "Bootloader Block A"> NAND device: Manufacturer ID: 0xec=2C Chip ID: 0x= d5 (Samsung NAND 4GiB> 3=2C3V 8-bit) > Scanning device for bad blocks > Usi= ng static partition definition > Creating 2 MTD partitions on "mvme7100-nan= d":> 0x00000000-0x40000000 : "Linux"> 0x40000000-0x80000000 : "Linux"> > > = # cat /proc/mtd> dev: size erasesize name> mtd0: 01000000 00040000 "Linux K= ernel + INITRD"> mtd1: 06e00000 00040000 "Linux JFFS2 Filesystem"> mtd2: 00= 100000 00040000 "Bootloader Block B"> mtd3: 00100000 00040000 "Bootloader B= lock A"> mtd4: 40000000 00040000 "Linux"> mtd5: 40000000 00040000 "Linux"> = > Partitions mtd0->mtd3 are in NOR flash. Partitions mtd4 and mtd5 are in> = NAND flash.> > The flash part is Samsung K9KAG08U0M SLC flash. We use 4G an= d 8G> variants. > I have also had exactly the same problem using Samsung K9= LBG08U0M MLC> flash > in 8G and 16G variants (no surprise). These flash par= ts have a 4K page> size > and 128 byte spare area.> > I have these problems= using a Linux 2.6.20 kernel with a YAFFS snapshot> from > 8/15/2008=2C and= also from another snapshot from sometime ago - yaffs> versions below.> > c= at /proc/yaffs> YAFFS built:Aug 19 2008 10:45:21> $Id: yaffs_fs.c=2Cv 1.63 = 2007/09/19 20:35:40 imcd Exp $> $Id: yaffs_guts.c=2Cv 1.52 2007/10/16 00:45= :05 charles Exp $> > Any ideas on how I can fix this problem would be appre= ciated.> > Thanks=2C> > ap> > > > ------------------------------> > Message= : 2> Date: Sat=2C 23 Aug 2008 10:02:48 +1200> From: Charles Manning > Subject: Re: [Yaffs] porting yaffs2 to linux user mode>= To: yaffs@lists.aleph1.co.uk> Message-ID: <200808231002.48933.manningc2@ac= trix.gen.nz>> Content-Type: text/plain=3B charset=3D"utf-8"> > On Friday 22= August 2008 17:00:46 Manju wrote:> > hi=2C> > I am porting yaffs2 to linux= user mode so i need some documentation on> > DIRECT module.. where can i g= et the documentation of this module by which i> > can understand the code b= etter...> > thanks> >> > cheers> > manju> > Try this:> > http://users.actri= x.co.nz/manningc/yaffs_direct2doc.pdf> > -- Charles> > > > ----------------= --------------> > _______________________________________________> yaffs ma= iling list> yaffs@lists.aleph1.co.uk> http://lists.aleph1.co.uk/cgi-bin/mai= lman/listinfo/yaffs> > > End of yaffs Digest=2C Vol 39=2C Issue 14> *******= ****************************** _________________________________________________________________ Chose your Life Partner? Join MSN Matrimony FREE http://www.shaadi.com/msn/matrimony.php = --_1c5670a3-1102-42ab-81ba-fad32f71ca5b_ Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Hi=2C
 =3B
 =3B =3B =3BWhen YAFFS2 is stress tested with fsstress =2C = =3B after nearly an hour all the fsstress process goes to D-state.
 =3B
Set up is =3B2.6.22 Kernel version =3Bon OMAP Board with =3BOne= NAND (2G ) as MTD
 =3B
 =3Band with cat /proc/yaffs
 =3B
 =3B =3B =3B =3B =3B =3B =3B Free space is 2MB = (Intial Ram size -64MB) =3Band
 =3B =3B =3B =3B =3B =3B =3B =3Bthe Gross l= ock count is -1.
 =3B
When we did some permutation and combination in the operations listed in fs= stress =2C
found that when 'symlink' operation is taken out from the execution list of= fsstress.
Everthing goes fine with the same setup.
 =3B
On =3Bgoing through symlink implmenetation =3Bhave seen that the al= ias string mem allocation done in the clone string function =2C is freed on= ly in unlink or unmount.
 =3B
Is this understanding correct ?
If it is right then why to have the copy always on RAM ( yes till unlink or= unmount) =3B?
But still why the fsstress process going to d-State 'coz of symlink =2C is = there is someother issue in symlink ?
 =3B
Please do guide me and =3B throw some light on this .
 =3B
Let me know more on any clarification required.
 =3B
Thanks in advance.
 =3B
With Regards
 =3B
 =3BMoorthy
 =3B
 =3B
 =3B


>=3B From: yaffs-request@lists.aleph1.co.uk
>=3B Subject: ya= ffs Digest=2C Vol 39=2C Issue 14
>=3B To: yaffs@lists.aleph1.co.uk
= >=3B Date: Sat=2C 23 Aug 2008 12:00:04 +0100
>=3B
>=3B Send ya= ffs mailing list submissions to
>=3B yaffs@lists.aleph1.co.uk
>= =3B
>=3B To subscribe or unsubscribe via the World Wide Web=2C visit<= BR>>=3B http://lists.aleph1.co.uk/cgi-bin/mailman/listinfo/yaffs
>= =3B or=2C via email=2C send a message with subject or body 'help' to
>= =3B yaffs-request@lists.aleph1.co.uk
>=3B
>=3B You can reach the= person managing the list at
>=3B yaffs-owner@lists.aleph1.co.uk
&g= t=3B
>=3B When replying=2C please edit your Subject line so it is mor= e specific
>=3B than "Re: Contents of yaffs digest..."
>=3B
&= gt=3B
>=3B Today's Topics:
>=3B
>=3B 1. YAFFS2 and HIGHMEM= (Ajit.Prem@Emerson.com)
>=3B 2. Re: porting yaffs2 to linux user mode= (Charles Manning)
>=3B
>=3B
>=3B ------------------------= ----------------------------------------------
>=3B
>=3B Message= : 1
>=3B Date: Fri=2C 22 Aug 2008 14:32:12 -0500
>=3B From: <= =3BAjit.Prem@Emerson.com>=3B
>=3B Subject: [Yaffs] YAFFS2 and HIGHME= M
>=3B To: <=3Byaffs@lists.aleph1.co.uk>=3B
>=3B Message-ID:<= BR>>=3B <=3B403DA57433416541B977A593BBEAE4002CBA42@etsmsg-slexm02.etsms= g.org>=3B
>=3B Content-Type: text/plain=3B charset=3D"us-ascii"
&= gt=3B
>=3B Hello=2C
>=3B
>=3B Does YAFFS2 work on boards w= hich use HIGHMEM? I have a PowerPC board
>=3B that comes in 1G and 2G = variants. YAFFS works just fine on the 1G board
>=3B and works just fi= ne on the 2G board if I boot with mem=3D1G (HIGHMEM
>=3B starts above = 1G on this board). Everything but YAFFS work just fine on
>=3B the 2G = board when the full 2G is used=2C so there isn't a HIGHMEM issue on
>= =3B the board.
>=3B
>=3B YAFFS works well enough on these board= s to allow using a root file
>=3B system on NAND. However=2C when I tr= y a simple write to a YAFFS partition
>=3B on a 2G board configured to= use the full 2G=2C I get the following crash.
>=3B I don't seem to be= the only one with this issue. My board is based on a
>=3B dual-core 8= 641D PowerPC. Mathias Fuchs reported exactly the same problem
>=3B on = a 1G 44O board. The posting can be found with a google search for the
&g= t=3B item "HIGHMEM on 440EPx board with 1GB of RAM". On Matthias' board
= >=3B HIGHMEM started at 768M. When Matthias reconfigured his kernel so th= at
>=3B he could use the full 1G as low memory=2C his YAFFS problems w= ent away.
>=3B
>=3B
>=3B # mount -t yaffs2 /dev/mtdblock4 = /mnt
>=3B # cd /mnt
>=3B # cp -a /etc .
>=3B
>=3B ----= --------[ cut here ]------------
>=3B Kernel BUG at 8013cd0c [verbose = debug info unavailable]
>=3B Oops: Exception in kernel mode=2C sig: 5 = [#1]
>=3B PREEMPT SMP NR_CPUS=3D2
>=3B Modules linked in:
&g= t=3B NIP: 8013CD0C LR: 8013CD0C CTR: 8003E24C
>=3B REGS: 8fb53a00 TRAP= : 0700 Not tainted (2.6.20)
>=3B MSR: 00029032 <=3BEE=2CME=2CIR=2CDR= >=3B CR: 24422428 XER: 00000000
>=3B TASK =3D 842652d0[626] 'cp' TH= READ: 8fb52000 CPU: 0
>=3B GPR00: 8013CD0C 8FB53AB0 842652D0 00000012 = 6419EFF8 F0266C8C 3F664DCF
>=3B 00000000
>=3B GPR08: 00000610 000= 00000 10000000 8FB52000 38526268 10024A08 80400000
>=3B 00001000
&g= t=3B GPR16: BD37E368 8FB53C38 8FB53C3C 00000000 00000000 00000000 8FB53BC0<= BR>>=3B 00000000
>=3B GPR24: 00000000 00000001 00000000 84272980 000= 00000 004C2000 8FB53BC0
>=3B BD318000
>=3B NIP [8013CD0C] nandmt= d2_WriteChunkWithTagsToNAND+0xe8/0xf0
>=3B LR [8013CD0C] nandmtd2_Writ= eChunkWithTagsToNAND+0xe8/0xf0
>=3B Call Trace:
>=3B [8FB53AB0] [= 8013CD0C] nandmtd2_WriteChunkWithTagsToNAND+0xe8/0xf0
>=3B (unreliable= )
>=3B [8FB53B10] [8013ACDC] yaffs_WriteChunkWithTagsToNAND+0x90/0x14= 0
>=3B [8FB53B30] [80133C64] yaffs_WriteNewChunkWithTagsToNAND+0x3d4/0= x538
>=3B [8FB53B70] [80135BE0] yaffs_WriteChunkDataToObject+0x94/0xe8=
>=3B [8FB53C30] [80136304] yaffs_WriteDataToFile+0x214/0x2e0
>= =3B [8FB53C90] [8012FE04] yaffs_commit_write+0x120/0x2bc
>=3B [8FB53C= D0] [800513D8] generic_file_buffered_write+0x3cc/0xa2c
>=3B [8FB53D90]= [80052E48] __generic_file_aio_write_nolock+0x314/0x5bc
>=3B [8FB53E00= ] [80053158] generic_file_aio_write+0x68/0x10c
>=3B [8FB53E30] [80078= F88] do_sync_write+0xc0/0x134
>=3B [8FB53EF0] [80079628] vfs_write+0x= f4/0x1bc
>=3B [8FB53F10] [8007A210] sys_write+0x4c/0x90
>=3B [8= FB53F40] [80011458] ret_from_syscall+0x0/0x38
>=3B --- Exception: c01 = at 0xff69874
>=3B LR =3D 0x10008670
>=3B Instruction dump:
>= =3B 80010064 38210060 7c0803a6 4e800020 3c608038 386378bc 4bee9125 0fe00000=
>=3B 48000000 3c608038 38637908 4bee9111 <=3B0fe00000>=3B 4800000= 0 7c0802a6
>=3B 9421ff90
>=3B
>=3B
>=3B
>=3B S= ome other info:
>=3B
>=3B -- part of boot log
>=3B
>= =3B Creating 4 MTD partitions on "mvme7100-flash":
>=3B 0x00000000-0x0= 1000000 : "Linux Kernel + INITRD"
>=3B 0x01000000-0x07e00000 : "Linux = JFFS2 Filesystem"
>=3B 0x07e00000-0x07f00000 : "Bootloader Block B">=3B 0x07f00000-0x08000000 : "Bootloader Block A"
>=3B NAND device:= Manufacturer ID: 0xec=2C Chip ID: 0xd5 (Samsung NAND 4GiB
>=3B 3=2C3V= 8-bit)
>=3B Scanning device for bad blocks
>=3B Using static p= artition definition
>=3B Creating 2 MTD partitions on "mvme7100-nand"= :
>=3B 0x00000000-0x40000000 : "Linux"
>=3B 0x40000000-0x80000000= : "Linux"
>=3B
>=3B
>=3B # cat /proc/mtd
>=3B dev: s= ize erasesize name
>=3B mtd0: 01000000 00040000 "Linux Kernel + INITRD= "
>=3B mtd1: 06e00000 00040000 "Linux JFFS2 Filesystem"
>=3B mtd2= : 00100000 00040000 "Bootloader Block B"
>=3B mtd3: 00100000 00040000 = "Bootloader Block A"
>=3B mtd4: 40000000 00040000 "Linux"
>=3B mt= d5: 40000000 00040000 "Linux"
>=3B
>=3B Partitions mtd0->=3Bmt= d3 are in NOR flash. Partitions mtd4 and mtd5 are in
>=3B NAND flash.<= BR>>=3B
>=3B The flash part is Samsung K9KAG08U0M SLC flash. We use= 4G and 8G
>=3B variants.
>=3B I have also had exactly the same = problem using Samsung K9LBG08U0M MLC
>=3B flash
>=3B in 8G and 1= 6G variants (no surprise). These flash parts have a 4K page
>=3B size =
>=3B and 128 byte spare area.
>=3B
>=3B I have these probl= ems using a Linux 2.6.20 kernel with a YAFFS snapshot
>=3B from
&g= t=3B 8/15/2008=2C and also from another snapshot from sometime ago - yaffs<= BR>>=3B versions below.
>=3B
>=3B cat /proc/yaffs
>=3B YA= FFS built:Aug 19 2008 10:45:21
>=3B $Id: yaffs_fs.c=2Cv 1.63 2007/09/1= 9 20:35:40 imcd Exp $
>=3B $Id: yaffs_guts.c=2Cv 1.52 2007/10/16 00:45= :05 charles Exp $
>=3B
>=3B Any ideas on how I can fix this prob= lem would be appreciated.
>=3B
>=3B Thanks=2C
>=3B
>= =3B ap
>=3B
>=3B
>=3B
>=3B -------------------------= -----
>=3B
>=3B Message: 2
>=3B Date: Sat=2C 23 Aug 2008 10= :02:48 +1200
>=3B From: Charles Manning <=3Bmanningc2@actrix.gen.nz&= gt=3B
>=3B Subject: Re: [Yaffs] porting yaffs2 to linux user mode
&= gt=3B To: yaffs@lists.aleph1.co.uk
>=3B Message-ID: <=3B200808231002= .48933.manningc2@actrix.gen.nz>=3B
>=3B Content-Type: text/plain=3B = charset=3D"utf-8"
>=3B
>=3B On Friday 22 August 2008 17:00:46 Ma= nju wrote:
>=3B >=3B hi=2C
>=3B >=3B I am porting yaffs2 to l= inux user mode so i need some documentation on
>=3B >=3B DIRECT modu= le.. where can i get the documentation of this module by which i
>=3B = >=3B can understand the code better...
>=3B >=3B thanks
>=3B = >=3B
>=3B >=3B cheers
>=3B >=3B manju
>=3B
>=3B = Try this:
>=3B
>=3B http://users.actrix.co.nz/manningc/yaffs_dir= ect2doc.pdf
>=3B
>=3B -- Charles
>=3B
>=3B
>=3B=
>=3B ------------------------------
>=3B
>=3B ___________= ____________________________________
>=3B yaffs mailing list
>=3B= yaffs@lists.aleph1.co.uk
>=3B http://lists.aleph1.co.uk/cgi-bin/mailm= an/listinfo/yaffs
>=3B
>=3B
>=3B End of yaffs Digest=2C Vo= l 39=2C Issue 14
>=3B *************************************

Get up-to-date on the latest movies=2C hottest stars to hit the sc= reens. And don't miss the juicy gossip. Only on MSN Entertainment Check it out! = --_1c5670a3-1102-42ab-81ba-fad32f71ca5b_--