IRC log for #elinux on 20090129

00:48.55*** join/#elinux Madsy (n=madsy@fu/coder/madsy)
01:08.21*** join/#elinux thraxisp (n=thraxisp@24.139.16.154)
02:28.34flybackis already starting to massively hurt from falling on the ice
02:30.47*** join/#elinux ccjoe (n=joeg@75-169-37-165.slkc.qwest.net)
02:32.09flybackdefintely canucked his body up
02:39.21*** join/#elinux ccjoe (n=joeg@75-169-37-165.slkc.qwest.net)
02:53.01flybackis going to try dethawing the ice in his driveway tomarrow WITH MOTHERCANUCKING GASOLINE AND A MATCH
02:55.20flybackis already in 2x more pain than usualy thanks to falling trying to snow out the ice and snow so he could get his car up the driveway.....THE BITCH ICE MUST DIE
02:58.08*** join/#elinux linac (n=lin@123.249.178.207)
03:05.28flybackremebers the piles of dead lithium battieres and ponders
03:22.58flybackbbl going to be sick now
04:34.29*** join/#elinux Dr_Who (n=tgall@gentoo/developer/dr-who)
04:40.18flybackhttp://www.cpubuyerscrap.com/AMDPentium.htm
04:45.11*** join/#elinux rocket (n=rocket@68-112-142-119.dhcp.stcd.mn.charter.com)
05:18.51*** join/#elinux harpal (n=Harpal@59.162.116.80)
07:17.47*** join/#elinux fgomez (i=c191fc0b@gateway/web/ajax/mibbit.com/x-8d139969cc7b6f74)
07:24.12*** join/#elinux hw_ (n=hw@p578b3905.dip0.t-ipconnect.de)
07:24.51*** join/#elinux lyakh (n=lyakh@p57BD29D1.dip0.t-ipconnect.de)
07:30.53*** join/#elinux pleemans (n=toi@116.54-246-81.adsl-static.isp.belgacom.be)
08:12.08*** join/#elinux boris_OmegA (n=boris@194.51.141.172)
08:29.32*** join/#elinux rraasch (n=ryan@80.72.151.98)
08:30.37*** join/#elinux ZeZu (n=null@c-98-227-56-17.hsd1.in.comcast.net)
10:59.39*** join/#elinux menomc (n=amery@shell.opensde.net)
11:01.16*** join/#elinux gustavoz (n=gustavoz@imhotep.toptech.com.ar)
11:09.08*** join/#elinux fgomez (i=c191fc0b@gateway/web/ajax/mibbit.com/x-b5ad7e1877fb889f)
12:18.54*** join/#elinux mitesh (n=mitesh@203.200.95.130)
12:20.28miteshHi, is anyone able to cross compile mysql server with uclibc?
14:20.16*** join/#elinux prpplague^2 (n=dave@mail.americanmicrosystems.com)
14:22.32*** join/#elinux GPSFan (n=kenm@64.92.145.112)
15:20.18miteshAny buildroot developers here?
15:33.14prpplaguemitesh: most of the developers are on #uclinux , but if you just want some end user support you can ask here
15:33.29prpplaguemitesh: sorry, #uclibc not #uclinux
15:34.30miteshprpplague, thanks
15:34.37*** part/#elinux mitesh (n=mitesh@203.200.95.130)
16:55.20*** join/#elinux booxter (n=booxter@night02.sml.by)
17:00.52*** join/#elinux markl__ (n=mark@c-67-186-245-229.hsd1.ut.comcast.net)
17:22.16*** join/#elinux pb__ (n=pb@88-111-107-22.dynamic.dsl.as9105.com)
18:05.39*** join/#elinux TimRiker (n=timr@70-1-81-157.pools.spcsdns.net)
18:05.39*** mode/#elinux [+o TimRiker] by ChanServ
18:09.23*** join/#elinux zx80user (n=adrian@80-44-176-198.dynamic.dsl.as9105.com)
18:54.30*** join/#elinux mdos1 (n=mdos1@pool-173-70-93-208.nwrknj.fios.verizon.net)
18:58.17mdos1Hi All. I'm seeing corruption on a flash device, resulting in jffs2 inode checksum failures. I'm running 2.6.21.7.
19:00.58mdos1Is the best way to diagnose this to instrument mtd writes in the driver, and dump_stack() to try to see if someone outside jffs2 is trying to write to the device?
19:01.18HcEupgrade to 2.6.28 as well, loads of changes to mtd
19:01.40mdos1That might not be an option in this case.
19:02.07HcEhow is the flash device connected?
19:02.14HcEserial? parallel? NAND?
19:02.28mdos1nand, I believe
19:02.55HcEcould it be as easy that you need to adjust the timing parameters of your external bus?
19:03.55mdos1I'd need to ask the HW team for this board
19:04.20HcEbut I guess you only have the NAND flash mounted?
19:04.33mdos1Yeah
19:04.35HcEto bad you can not fast forward to 2.6.28, so you can use ubifs istead
19:04.57mdos1There are some rare cases where I see mount failures
19:05.15HcEhow do you program the device?
19:05.29HcEmtd-utils? flash_erase + nandwrite?
19:05.49mdos1initially uboot gets put on with an emulator on a partition
19:05.58mdos1then it's flash_erase
19:07.16HcEyou use nandwrite to program the jffs2 image?
19:08.46HcEhowever you program it, it takes care to not program the bad blocks?
19:08.55HcEand not erase them?
19:09.04mdos1I thought that was a function of jffs2 itself
19:09.18HcEthe kernel should detect one or more bad blocks during boot
19:09.32mdos1when it's building the inode table,correct ?
19:09.40HcEsort of, jffs2 will detect new bad blocks, but if you program data into an already bad block you are screwed
19:09.50mdos1Yeah, so I've seen.
19:10.12mdos1I do notice jffs2 printk errors on the console during boot
19:10.37*** join/#elinux pleemans (n=toi@d54C2AAB7.access.telenet.be)
19:10.38mdos1complaining about bad MAGIC 0x1985 values encountered, and CRC errors
19:10.58HcEhmm, how do you program the jffs2 image? I did not see an answer to that
19:11.16mdos1where can I verify that? The MTD driver?
19:11.16HcEI've done the mistake in the past by using cp and dd to do that, they fail if they hit a bad block
19:11.35HcEhow do you put the generated jffs2 image into your NAND flash the first time?
19:12.47mdos1it's a dpkg based install
19:13.30mdos1The image goes onto the board OK and boots, but it gets corrupted at runtime on certain boards in the field
19:13.40HcEah, okay
19:14.10HcEif you can give some slack on the timing when writing/reading from the flash I would do that
19:14.17mdos1we've been mounting partitions read only and it still gets corrupted
19:14.32HcEhmmm, then I would suspect hardware
19:14.46mdos1so i figure this is not coming from proper vfs channels
19:14.49HcEhow is it connected to the processor?
19:15.03HcEwhat architecture are you running?
19:15.09mdos1ppc
19:15.21HcEhmmm, I do not know too much about ppc
19:16.01HcEMy guess is that if you have the flash on an external bus interface and the chip select is not hardware controlled, then you can get into "fun" situations
19:16.03mdos1I figured if I could instrument the mtd driver, and prove that no writes are being done, we have a HW issue
19:16.40HcEor hook a digital analyzer on the chip eneable + write enable lines
19:17.09flybackhttp://www.liveleak.com/view?i=097_1233174793 <--- YOU GO TO HELL AND YOU DIE MORONS
19:17.29*** join/#elinux pcgeil (n=steffen@p549E4F44.dip.t-dialin.net)
19:17.29mdos1The symptoms are seemingly random, could voltage variation cause this type of thing?
19:17.39rocketgrrr .. why do you have to segfault cryptsetup ...
19:27.14*** join/#elinux archae0pteryx (n=snewman@207.47.42.130.static.nextweb.net)
19:52.10*** join/#elinux Dr_Who (n=tgall@gentoo/developer/dr-who)
19:58.05*** join/#elinux zx80user (n=adrian@80-44-176-198.dynamic.dsl.as9105.com)
23:24.33*** join/#elinux gigi65 (n=user@host110-75-dynamic.42-79-r.retail.telecomitalia.it)
23:24.55*** part/#elinux gigi65 (n=user@host110-75-dynamic.42-79-r.retail.telecomitalia.it)

Generated by irclog2html.pl Modified by Tim Riker to work with infobot.