=== infinity_ is now known as infinity
=== chihchun_afk is now known as chihchun
[07:21] <alfonsojon> Hi.
[07:22] <alfonsojon> Does the kernel in 14.04 better support Exynos chips?
=== doko_ is now known as doko
[12:37] <hvn2> hi, is there any known issue with the combination of ARMv7l and kernel 3.10.18 ? e.g. top doesnt show output, but ps does; apt-get starts but doesnt finish
[14:07] <c10ud> Hi, I have an interesting issue with a BeagleboneBlack (kernel 3.13) and ubuntu raring. It looks like the system sometimes locks up, and TI suggests it could be something related to gtk2 and PNG (probably libpng)
[14:07] <c10ud> so my question is: has any of you already heard about such issue in the past and/or other boards, etc.=
[14:08] <c10ud> cool thing is there's no kernel panic output even in serial (and TI says even jtag locks up (!))
[14:25] <rbasak> c10ud: I don't see how a full system lockup, including even jtag, could possibly be caused by a userspace library.
[14:25] <rbasak> c10ud: surely it's a kernel problem?
[14:26] <rbasak> (or a hardware problem?)
[14:26]  * rbasak doesn't see how a kernel could lock up jtag either
[14:27] <c10ud> rbasak, neither do I, but that's what TI says (altrough the message is unclear, see https://groups.google.com/forum/#!category-topic/beagleboard/beaglebone-black/5vaehZewk2U )
[14:29] <c10ud> probably some zlib-crypto related, I guess..(?) but surely jtag hanging..
[14:30] <rbasak> c10ud: I think you're confused. I don't interpret that thread in the same way you do.
[14:31] <rbasak> A kernel panic is clearly a kernel or hardware issue. It may be triggered by something in userspace, but that is a symptom, not a root cause.
[14:31] <rbasak> (unless userspace is taking direct control of hardware in some way, which doesn't seem to be the case here)
[14:31] <c10ud> rbasak, I don't interpret it, I just ask if you ever heard of some similar issue:)
[14:32] <rbasak> c10ud: I read your original message as implicating Ubuntu in some way.
[14:34] <c10ud> rbasak, well I'm using ubuntu, I ask if anyone ever heard of such an issue (maybe libpng does nasty stuff with the cpu, I don't know..)
[14:34] <c10ud> apparently that's not the case
=== chihchun is now known as chihchun_afk
=== chihchun_afk is now known as chihchun
[19:24] <kmcguire> Hello, Anyone familar with VSMA v6?
[19:25] <kmcguire> VMSA
[19:41] <applepi> Hi all..  I am having crazy issues getting SSL working properly on my ubuntu armhf 12.04 build...  I've followed everything online I can find about getting it installed and setup and I still cannot wget an https or run get-pip.py or anything that requires an SSL.
[19:41] <applepi> Is there any sort of definitive 'this is required to make SSL work in ubuntu' somewhere that I'm missing?
[19:44] <applepi> (curl fails as well.)
[20:02] <infinity> applepi: There's nothing special about SSL on ARM.  What works on amd64 should work on armhf.
[20:02] <infinity> applepi: Maybe you should describe the problem you're seeing?
[20:05] <applepi> infinity: when I attempt to wget https://www.google.com (or any other https), I get 'ERROR: cannot verify www.google.com's certificate'
[20:05] <applepi> infinity: curl gives me 'error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed'
[20:05] <infinity> applepi: You might need ca-certificates installed.
[20:06] <applepi> infinity: ca-certificates is already the newest version
[20:06] <applepi> they're installed to /etc/ssl/certs it looks like
[20:07] <infinity> Well, that's definitely a case of "it works for me", so you might need to investigate a bit.
[20:08] <applepi> infinity:  I have..  so much..  :|  is there some sort of configuration I might need to touch?  I've looked at /etc/ssl/openssl.cnf and it looks okay as far as I can tell (granted I'm very much an ssl lightweight..)
[20:11] <infinity> applepi: Well, like I said, it should just work.  I'd help dig deeper, but I'm in the middle of a bunch of things right now. :/