DocScrutinizer05 changed the topic of #qi-hardware to: Copyleft hardware - http://qi-hardware.com | hardware hackers join here to discuss Ben NanoNote, atben / atusb 802.15.4 wireless, and other community driven hw projects | public logging at http://en.qi-hardware.com/irclogs and http://irclog.whitequark.org/qi-hardware
cmbrgo has quit [Changing host]
cmbrgo has joined #qi-hardware
<kristianpaul> freertos? :o
pcercuei has quit [Quit: dodo]
dos1 has quit [Ping timeout: 240 seconds]
wej has quit [Ping timeout: 264 seconds]
<DocScrutinizer05> o.O
<DocScrutinizer05> rogue site?
xiangfu has quit [Ping timeout: 272 seconds]
wolfspraul has joined #qi-hardware
wolfspraul has quit [Read error: Connection reset by peer]
xiangfu has joined #qi-hardware
xiangfu has quit [Ping timeout: 245 seconds]
xiangfu has joined #qi-hardware
xiangfu has quit [Ping timeout: 245 seconds]
xiangfu has joined #qi-hardware
viric has quit [Ping timeout: 240 seconds]
viric has joined #qi-hardware
xiangfu has quit [Remote host closed the connection]
kilae has joined #qi-hardware
wej has joined #qi-hardware
xiangfu has joined #qi-hardware
dos1 has joined #qi-hardware
pcercuei has joined #qi-hardware
rz2k has joined #qi-hardware
Jurting_pc2 has joined #qi-hardware
mth has joined #qi-hardware
paul_boddie has joined #qi-hardware
cmbrgo has quit [Ping timeout: 246 seconds]
xiangfu has quit [Remote host closed the connection]
<apelete> ahah, just built jz-3.11 vanilla (without my musb hacks), and the pagealloc memory corruption appears in it too: http://paste.debian.net/57073/
<larsc> now that is unexpected
<apelete> tried to debug the thing this whole afternoon, and after reading backtraces in gdb I suspected that the problem was not in musb and I was right
<apelete> I don't know where it's coming from exactly though, cause gdb won't let me break on the exact function that produce the memory corruption error :-(
<larsc> you should build your kernel with KALLSYMS
<larsc> then we'll see where it is triggered
<apelete> yeah, forgot to build jz-3.11 with KALLSYMS, but I think I recorded a boot session with more information a few days ago
<apelete> larsc: there you have it, recorded on october 10 -> http://paste.debian.net/57081/
<larsc> hm, maybe your memory is bad
<larsc> so it should all be 0xaa
<larsc> but you got some 0xae
<larsc> in there
<apelete> larsc: what do you mean by "memory is bad" ?
<apelete> you mean my nanonote may be faulty ?
<apelete> the memory corruption only shows up if DEBUG_PAGEALLOC is enabled by the way
<larsc> yes
<larsc> it will only be detected if DEBUG_PAGEALLOC is enabled
<larsc> cause there is a function checking if it is 0xaa
<apelete> larsc: hmm, since I'm booting from sdcard, maybe it's the card that's faulty, what do you think ?
<larsc> no
<apelete> ah no, it must be the nanonote memory
<apelete> pagealloc is done on memory, didn't think before asking :)
<larsc> yep, there is one function that sets the memory to all 0xaa
<larsc> when the memory is freed
<larsc> once it is allocated again it checks whether it is still all 0xaa
<apelete> yes, I think it's check_poison_mem() from debug-pagealloc.c you're talking about
<apelete> still, that's bad. I hope the device won't be damaged though
<apelete> I need it to continue hacking on musb :-(
<larsc> it could also be a user after free somewhere
<apelete> will ignore that problem for now, and focus on getting the glue layer init function right
<apelete> larsc: this is what I'm trying to do currently:
<apelete> /* The musb_platform_init() call:
<apelete> * - sets the musb->isr
<apelete> * - adjusts musb->mregs
<larsc> ok
<apelete> larsc: any advice on how to proceed here ?
<larsc> So mregs should probably come out of the mmio platform_resource
<larsc> same for the interrupt number (platform_get_irq())
<larsc> not sure about what the isr is supposed to do exactly
<larsc> or if there is some kind of musb default isr
<apelete> <larsc> So mregs should probably come out of the mmio platform_resource
<apelete> I don't get it, could you be more specific please ?
<larsc> I think you are supposed to call musb_init_controller
<larsc> hm, no actually
<larsc> I think you don't need to do anything for mregs
<larsc> as it should already be correct
<apelete> so that leaves musb->isr to take care of
<larsc> As far as I can see none of the existing drivers implement the init callback
<larsc> ah, no they do
<larsc> so some init functions add a offset to mregs
<larsc> but I don't think we need to do this
<larsc> about what the isr is supposed to do exactly
<larsc> 20:02 < larsc> or if there is some kind of musb default isr
<larsc> ups
<larsc> ux500_musb_interrupt seems to be a good example
<apelete> will try that
<apelete> larsc: ok, will try to get the interrupt settings right, then we'll see. thanks for the advices
paul_boddie has left #qi-hardware ["Konversation terminated!"]
<wpwrak> DocScrutinizer05: btw, some more EE design verification: http://lists.en.qi-hardware.com/pipermail/discussion/2013-October/010329.html
kilae has quit [Quit: ChatZilla 0.9.90.1 [Firefox 24.0/20130910160258]]
rz2k has quit []
pcercuei has quit [Read error: Connection reset by peer]
pcercuei has joined #qi-hardware
zear has quit [Ping timeout: 260 seconds]
zear has joined #qi-hardware
<apelete> larsc mth: just added interruot regs initialisation in musb init function -> http://seketeli.fr/git/~apelete/qi-kernel.git/commit/?h=jz4740-musb&id=6de03fc47ef850a34b4bcdf1d63f7b9fb015b94a
<apelete> but something's amiss -> http://paste.debian.net/57163/:
<apelete> [ 1.320000] musb-hdrc musb-hdrc.0.auto: can't request region for resource [mem 0x13040000-0x1304ffff]
<apelete> [ 1.330000] musb-hdrc: probe of musb-hdrc.0.auto failed with error -16
<apelete> enabled a few printk to get a clearer picture -> http://paste.debian.net/57164/:
<apelete> [ 1.560000] bus: 'platform': really_probe: probing driver musb-hdrc with device musb-hdrc.0.auto
<apelete> [ 1.570000] musb-hdrc musb-hdrc.0.auto: can't request region for resource [mem 0x13040000-0x1304ffff]
<apelete> [ 1.580000] musb-hdrc: probe of musb-hdrc.0.auto failed with error -16
<apelete> seems like there is still something wrong with platform data...
<apelete> anyway, need some sleep right now, maybe we can discuss it in a few hours
<pcercuei> this memory area has probably already been requested elsewhere
Yogi_Bear has joined #qi-hardware
<Yogi_Bear> invitation http://www.tatuuu.com.br ONLY QI-HARDWARE
Yogi_Bear has quit [Client Quit]
<DocScrutinizer05> wpwrak: sorry, just wake up
<DocScrutinizer05> woke
<DocScrutinizer05> ugh a wall of text
pcercuei_ has joined #qi-hardware
pcercuei has quit [Read error: Connection reset by peer]
Jurting_pc2 has quit [Read error: Connection reset by peer]
<DocScrutinizer05> wpwrak: sorry, takes a while to what that NCIS in TV and then wait til the coffeee kicks in
<DocScrutinizer05> to watch*
pcercuei_ has quit [Ping timeout: 240 seconds]