**** BEGIN LOGGING AT Mon Nov 17 03:00:00 2014
Nov 17 09:37:12 <ant_work> bluelightning: I start to suspect some recent toolchain/gcc change broke armv4
Nov 17 09:37:20 <ant_work> after release
Nov 17 09:37:32 <ant_work> I'll counter-check with an old kernel
Nov 17 09:41:16 <bluelightning> ant_work: hmm, ok
Nov 17 09:41:44 <bluelightning> FYI, I merged Linus's patch over the weekend, that appeared to be all that was outstanding for meta-handheld
Nov 17 09:42:44 <ant_work> right
Nov 17 09:42:45 <ant_work> hi
Nov 17 09:43:23 <ant_work> there are patches for meta-initramfs
Nov 17 09:43:54 <ant_work> well, about toolchain you know...I was developing with lumag so I didn't pull for a while
Nov 17 09:44:03 <lumag> hello ant_work bluelightning
Nov 17 09:44:21 <ant_work> I compiled 3.18-rc4 (have the logs) so tc was ok
Nov 17 09:44:33 <ant_work> after pull collie doesn't boot anymore
Nov 17 09:44:50 <ant_work> it wouldn't be the first time armv4 is broken...
Nov 17 09:45:24 <ant_work> the fact that linusw sent a patch means he successfully compiled (I guess)
Nov 17 09:47:27 <ant_work> lumag: can an update to byacc break the kernel?
Nov 17 09:47:45 <lumag> ant_work, hopefully no.
Nov 17 09:48:22 <ant_work> ah ha..we have a gcc update as well..
Nov 17 09:48:54 <ant_work> some changes to gcc configure
Nov 17 09:49:17 <ant_work> and a backport of two patches
Nov 17 09:49:50 <ant_work> damn,,why did I pull :p
Nov 17 09:51:36 <lumag> is that in oe-core or in meta-oe?
Nov 17 09:53:20 <ant_work> oe-core
Nov 17 09:54:15 <lumag> I see no obvious problems there.
Nov 17 09:54:51 <ant_work> see, I had a pull after
Nov 17 09:54:52 * lumag is not a toolchain expert though.
Nov 17 09:54:53 <ant_work> http://cgit.openembedded.org/openembedded-core/commit/?id=04b725511a505c582a3abdf63d096967f0320779
Nov 17 09:55:10 <ant_work> this was the 'big change' immediately after relase
Nov 17 09:55:21 <ant_work> err.. immediately BEFORE ;)
Nov 17 09:55:37 <ant_work> then I pulled couple of days after release
Nov 17 09:56:04 <ant_work> that toolchain was ok because I did compile kexecboot and kernels for collie
Nov 17 09:56:25 <ant_work> the actual toolchain is ok for pxa/poodle anyway
Nov 17 09:56:40 <ant_work> must be some bx lr
Nov 17 09:57:54 <ant_work> I've asked linusw right now
Nov 17 10:00:21 <lumag> You can always a git revert a patch
Nov 17 10:01:06 <ant_work> heh, I could start to bisect but ... I'd prefer to spend the littl etime for kernel & co and not toolchain ;)
Nov 17 10:01:25 <lumag> I'll do a fresh build with just updated oe.
Nov 17 10:01:34 <lumag> Let's check if I will be able to reproduce the problem.
Nov 17 10:02:14 * lumag uses an old code sourcery lite to do builds.
Nov 17 10:02:25 <lumag> * to build kernels
Nov 17 10:02:40 <ant_work> good so we can compare
Nov 17 10:02:51 <lumag> It will build 3.17
Nov 17 10:02:53 <lumag> though
Nov 17 10:05:37 <ant_work> Nov 14 00:26:33 <ant__> looks better  http://pastebin.com/tbu1KF1x
Nov 17 10:07:01 <ant_work> this was built with the 'old' tc
Nov 17 10:09:45 <ant_work> probablywas pulled on 1st november
Nov 17 10:10:30 <ant_work> lumag: the good side of it is that while collie was not booting I could test poodle;)
Nov 17 10:12:00 <ant_work> bluelightning: thx
Nov 17 10:12:42 <ant_work> the gcc patch I posted above broke klibc build just before dizzy release...
Nov 17 10:30:24 <lumag> still building
Nov 17 10:51:54 <ant_work> lumag: try for fun the kernel I uploaded on github/locomo
Nov 17 11:03:42 <lumag> ant_work, tried, doesn't output a thing
Nov 17 11:08:48 <lumag> <lumag> Ugh.
Nov 17 11:08:48 <lumag> <lumag> Uncompressing Linux... done, booting the kernel.
Nov 17 11:08:48 <lumag> <lumag> strongarm_ppc_write: Bad offset 0x0000000000000030
Nov 17 11:08:48 <lumag> <lumag> VFS: Unable to mount root fs on unknown-block(0,0)
Nov 17 11:08:48 <lumag> <lumag> User configuration error - no valid root filesystem found
Nov 17 11:08:49 <lumag> <lumag> Kernel panic - not syncing: Invalid configuration from end user prevents continuing
Nov 17 11:08:51 <lumag> <lumag> ---[ end Kernel panic - not syncing: Invalid configuration from end user prevents continuing
Nov 17 11:08:53 <lumag> <lumag> But at least it boots.
Nov 17 11:08:55 <lumag> <lumag> That is 3.17 from oe
Nov 17 11:08:57 <lumag> <lumag> Linux version 3.17.0-yocto-standard (lumag@fangorn) (gcc version 4.9.1 (GCC) ) #1 PREEMPT Mon Nov 17 14:02:22 MSK 2014
Nov 17 11:09:00 <lumag> <lumag> CPU: StrongARM-1110 [6901b119] revision 9 (ARMv4), cr=0000717f
Nov 17 11:17:07 <ant_work> yes, 3.17 oe was booting
Nov 17 13:25:11 <ant_work> lumag: hm..linusw was at head/master and h3600 meta-handheld kernel did boot
Nov 17 21:10:20 <ant__> hi lumag_, Jay7
Nov 17 21:13:56 <lumag_> hello
Nov 17 21:18:03 <ant__> while I'm rebuilding -yocto 3.17, how can we respin the sa1100 fb and pcmcia no-cufreq patches?
Nov 17 21:24:54 <ant__> heh, he said back then http://marc.info/?l=linux-arm-kernel&m=139697302004377&w=2
Nov 17 21:25:23 <ant__> " We should have clk_prepare_enable() " doh
Nov 17 21:26:09 <ant__> now he doesn't seem to agree...
Nov 17 21:26:17 <ant__> hi bluelightning
Nov 17 21:26:29 <bluelightning> hi lumag_, ant__
Nov 17 21:28:04 <lumag_> ant__, I will check if I comply to his comments and respin.
Nov 17 21:29:48 <lumag_> hi bluelightning
Nov 17 21:30:50 <lumag_> ant__, I'm getting tired of being ignored wrt. sa1100. Even simple collie patches are ignored.
Nov 17 21:31:19 <lumag_> he responds about pxa, but ignores sa1100
Nov 17 21:32:01 <ant__> yes, maybe he's busy but strangely these got ignores
Nov 17 21:32:07 <ant__> *ignored
Nov 17 21:33:10 <ant__> I have that collie...maybe could send to Robert
Nov 17 21:34:09 <ant__> he'd need a serial, though
Nov 17 21:49:33 <lumag_> ant__, let him finish with pxa first. After several years we have good pxa maintainers.
Nov 17 21:49:47 <ant__> :p
Nov 17 21:52:40 <lumag_> I hope to receive few more pxa boards for testing.
Nov 17 21:52:57 <lumag_> And maybe I'll buy a simpad and/or Jornada
Nov 17 21:55:33 <ant__> hm... 3,17 doesn't boot as well...
Nov 17 21:55:56 <ant__> I'll go back with oe-core
Nov 17 21:56:11 <lumag_> That is really strange.
Nov 17 21:56:32 <lumag_> I've built 3.17 today with oe-core (+meta-oe +  ..) and it booted in qemu.
Nov 17 21:56:40 <ant__> collie suddendly defective ? ;)
Nov 17 21:56:50 <lumag_> A possible reason.
Nov 17 21:57:10 <lumag_> Send me your 3.17 image
Nov 17 21:59:32 <ant__> done
Nov 17 22:08:01 <ant__> lumag_, the collie does kexec a linux-kexecboot zImage
Nov 17 22:08:23 <ant__> it's like the recent kernels are miscompiled
Nov 17 22:08:30 <ant__> here on my host
Nov 17 22:08:35 <lumag_> send me your kernel.
Nov 17 22:08:45 <ant__> sent 3.17
Nov 17 22:09:23 <ant__> do you need the image as well? I can upload it
Nov 17 22:13:24 <lumag_> Your 3.17 boots fine in emulator.
Nov 17 22:13:42 <ant__> I'm flashing now Ospack over there...
Nov 17 22:14:02 <ant__> unfortunately kexecboot site is down so I cannot reflash 2.6.31
Nov 17 22:15:31 <lumag_> If everything fails, try booting with this kernel: http://tosa.lumag.spb.ru/uploads/zImage-collie-test
Nov 17 22:15:36 <lumag_> it is huge, but self-contained.
Nov 17 22:16:00 <lumag_> It should drop to a shell prompt on serial console
Nov 17 22:16:05 <lumag_> after a while.
Nov 17 22:48:04 <ant__> lumag_, I'm in Diag Menu
Nov 17 22:48:14 <ant__> when I inser SandDisk 1GB SD
Nov 17 22:48:25 <ant__> SD CD: H ->L
Nov 17 22:48:35 <ant__> SD WP: H ->L
Nov 17 22:48:42 <ant__> ^ write protect?
Nov 17 22:49:45 <lumag_> yes
Nov 17 22:51:01 <ant__> when I eject SanDisk it goes High immediately
Nov 17 22:51:22 <ant__> if I eject Lexar it takes a little more to come high again
Nov 17 22:51:26 <lumag_> It's a gpio. reading a 'lock' on the side of the card
Nov 17 22:51:32 <lumag_> Nothing magic.
Nov 17 22:51:54 <ant__> I've read SanDisk has proprietary/undocumented lockings
Nov 17 22:52:06 <ant__> myths?
Nov 17 22:52:56 <ant__> ouch..battery reads 60-70
Nov 17 22:53:00 <ant__> dead...?
Nov 17 23:06:46 <lumag_> don't know to both questions.
Nov 17 23:08:47 <ant__> seems it outputs 0.4v
Nov 17 23:11:34 <ant__> replaced..new one does 4.1v :)
Nov 17 23:25:40 <ant__> ok, with the new battery collie is like new...tested with sharp rom
Nov 17 23:44:30 <ant__> lumag_, it boots 3.17 now
Nov 17 23:44:45 <lumag_> :)
Nov 17 23:44:51 <ant__> battery fault...
Nov 17 23:45:05 <lumag_> Maybe the issue was in a battery - kernel drains significant amount of power when booting.
Nov 17 23:45:28 * lumag_ has to extend kexec to be able to boot 2.4 kernels.
Nov 18 00:10:38 <ant__> good, 3.18-rc4 boots again  http://pastebin.com/Hyc04pS6
Nov 18 00:11:06 <ant__> this has all locomo patches + corrections
Nov 18 00:13:05 <ant__> argh..it doesn't resume
Nov 18 00:14:18 <ant__> gn
**** ENDING LOGGING AT Tue Nov 18 02:59:59 2014