Dazzozo changed the topic of #huawei-g300 to: #huawei-g300 | G300 & Y300 innovation station | home of the G300's CyanogenMod port and mnupea | http://irclog.whitequark.org/huawei-g300 | https://dazzozo.com/L.png
fonz93 has quit [Remote host closed the connection]
ValicekB has quit [Ping timeout: 276 seconds]
ValicekB has joined #huawei-g300
subz3r0 has quit [Ping timeout: 256 seconds]
subz3r0 has joined #huawei-g300
subz3r0 has joined #huawei-g300
subz3r0 has quit [Ping timeout: 256 seconds]
subz3r0 has joined #huawei-g300
subz3r0 has joined #huawei-g300
subz3r0 has quit [Ping timeout: 256 seconds]
subz3r0 has joined #huawei-g300
subz3r0 has quit [Ping timeout: 256 seconds]
subz3r0 has joined #huawei-g300
subz3r0 has quit [Ping timeout: 256 seconds]
subz3r0 has joined #huawei-g300
subz3r0 has joined #huawei-g300
subz3r0 has quit [Ping timeout: 256 seconds]
subz3r0 has joined #huawei-g300
subz3r0 has quit [Ping timeout: 256 seconds]
subz3r0 has joined #huawei-g300
gregor160300 has joined #huawei-g300
moeter15 has joined #huawei-g300
moeter14 has quit [Ping timeout: 250 seconds]
fonz93 has joined #huawei-g300
<fonz93> Dazzozo: we have selinux set to permissive right? why dmesg still shows some avc denial errors?
<fonz93> there are many
<fonz93> this is an example
<fonz93> avc: denied { read write } for path="/dev/kgsl-3d0" dev="tmpfs" ino=3592 scontext=u:r:system_server:s0 tcontext=u:object_r:device:s0 tclass=chr_file permissive=1
<Dazzozo> i suggest you read up on what permissive does :P
<fonz93> oh
<fonz93> so i shouldn't care about this error?
<Dazzozo> its not an error, its debug
<Dazzozo> if it was enforcing, it would be an error
<fonz93> ok
<Dazzozo> its designed so you can fix up your sepolicy before you switch to enforcing
<fonz93> oh so it's from there that all take sepolicies
<fonz93> xD
<Dazzozo> if you switch to enforcing, you will crash the system
<fonz93> i won't ahahahahaha
<Dazzozo> because of those warnings
<Dazzozo> it'll start blocking things that are system critical
<Dazzozo> without a proper sepolicy
<Dazzozo> and if you boot with enforcing it won't get very far
<fonz93> i am pretty satisfied in the current state of cm12.1 anyway
<luca020400> fonz93 : the call bug got fixed ?
<fonz93> yes
<luca020400> So everything was due a "fix" :p
luca020400 has quit [Quit: AndroIRC - Android IRC Client ( http://www.androirc.com )]
luca020400 has joined #huawei-g300
<fonz93> i have found the real reason of why the wifi issue happens
<fonz93> maybe also the fix
<Dazzozo> hm?
<luca020400> ????????????????????????
<fonz93> i have found a bug report
<fonz93> they suggested to increase min_free_kbytes as a workaround until they update the kernel
<fonz93> i did it
<Dazzozo> its a fucking page allocation failure? we had one of those with the g300 module
<fonz93> and the bug "disappeared"
<fonz93> so i may need to follow their real fix
<luca020400> lol
<fonz93> instead of increasing min free kbytes
<fonz93> also
<fonz93> there are common dmesg errors
<luca020400> so kernel fault
<luca020400> xd
<luca020400> huawei
<luca020400> xd
<fonz93> witksdioirqd/mmc2: page allocation failure: order:0, mode:0x20
<fonz93> and slub allocation failure
<Dazzozo> ancient
<fonz93> thanks
<fonz93> what was happening on u8815 when getting the allocation failure?
<Dazzozo> 9 times out of 10 it would hang the entire system for about a minute and then some watchdog would kick in and reboot it
<Dazzozo> and 1/10 of the time it would give us some crash output in dmesg
<Dazzozo> and then crash the system immediately
gregor160300 has quit [Ping timeout: 256 seconds]
<fonz93> ok that's similar to the current situation
<fonz93> i'll try that now
<fonz93> thanks
<Dazzozo> not the kernel
<fonz93> oh yes thanks
<fonz93> that issue can cause also swap errors right?
<Dazzozo> probably?
<Dazzozo> i mean, i guess
<Dazzozo> this isn't really a "fix"
<Dazzozo> but it was more reliable than fucking with min_free_kbytes
<luca020400> *workaround everywhere*
<Dazzozo> as in: it stopped the crashing, which was good enough at the time
<luca020400> xd
<Dazzozo> pretty much
<fonz93> ok
<fonz93> this is the other error that appears in dmesg: SLUB: Unable to allocate memory on node -1
Ghost|afk is now known as Shadowghoster
<fonz93> ok
<fonz93> the bug is evolvev now
<fonz93> *evolved
<luca020400> so xd
<Shadowghoster> hi
<fonz93> if you try to download a file
<fonz93> the download stops and in dmesg appears the same allocation error
<fonz93> but the wi-fi doesn't stop to work
<luca020400> loool
<fonz93> so the wi-fi issue is fixed but the allocation error not
<luca020400> so try to chnge sysctl
<fonz93> it's a bad solution because of our low RAM
<luca020400> yes just try :p
<Dazzozo> to be fair
<fonz93> i already did
<Dazzozo> android is a bad solution for that device
<fonz93> and the bug is fixed but the system became really laggy
<fonz93> yes Dazzozo you're right :P
<fonz93> xD
<fonz93> what ksdioirqd/mmc2 is?
<Dazzozo> fonz93: if i was to guess
<Dazzozo> kernel sdio interrupt request daemon?
<Dazzozo> :P
<Dazzozo> wifi crap is often on an mmc bus
<fonz93> just tried to debug again
<fonz93> and the wifi issue happened
<fonz93> spamming this like hell ksdioirqd/mmc2: page allocation failure: order:0, mode:0x20
<fonz93> within all of the swap device errors lol
<fonz93> it also gives me this
<fonz93> <4>[ 572.528063] [<c0015494>] (unwind_backtrace+0x0/0x138) from [<c06da638>] (dump_stack+0x18/0x1c)
<fonz93> <4>[ 572.528084] [<c06da638>] (dump_stack+0x18/0x1c) from [<c01403ec>] (warn_alloc_failed+0xec/0x124)
<fonz93> <4>[ 572.528108] [<c01403ec>] (warn_alloc_failed+0xec/0x124) from [<c0140ac0>] (__alloc_pages_nodemask+0x608/0x7f4)
<fonz93> <4>[ 572.528131] [<c0140ac0>] (__alloc_pages_nodemask+0x608/0x7f4) from [<c017f03c>] (new_slab+0x298/0x2a8)
<fonz93> <4>[ 572.528154] [<c017f03c>] (new_slab+0x298/0x2a8) from [<c06dd9dc>] (__slab_alloc.isra.49.constprop.56+0x3cc/0x59c)
<fonz93> <4>[ 572.528179] [<c06dd9dc>] (__slab_alloc.isra.49.constprop.56+0x3cc/0x59c) from [<c0181b6c>] (__kmalloc_track_caller+0xfc/0x1c0)
<fonz93> <4>[ 572.528204] [<c0181b6c>] (__kmalloc_track_caller+0xfc/0x1c0) from [<c057790c>] (__alloc_skb+0x5c/0x104)
<fonz93> <4>[ 572.528228] [<c057790c>] (__alloc_skb+0x5c/0x104) from [<c0577b04>] (dev_alloc_skb+0x20/0x44)
<fonz93> <4>[ 572.528288] [<c0577b04>] (dev_alloc_skb+0x20/0x44) from [<bf0469f8>] (ath6kl_buf_alloc+0x14/0x38 [ar6000])
<fonz93> <4>[ 572.528364] [<bf0469f8>] (ath6kl_buf_alloc+0x14/0x38 [ar6000]) from [<bf04dabc>] (ath6kl_rx_refill+0x60/0x114 [ar6000])
<fonz93> <4>[ 572.528434] [<bf04dabc>] (ath6kl_rx_refill+0x60/0x114 [ar6000]) from [<bf03dc80>] (ath6kl_htc_rxmsg_pending_handler+0xd74/0xf20 [ar6000])
<fonz93> <4>[ 572.528501] [<bf03dc80>] (ath6kl_htc_rxmsg_pending_handler+0xd74/0xf20 [ar6000]) from [<bf03a7c4>] (ath6kl_hif_intr_bh_handler+0x2f8/0x690 [ar6000])
<fonz93> <4>[ 572.528571] [<bf03a7c4>] (ath6kl_hif_intr_bh_handler+0x2f8/0x690 [ar6000]) from [<bf0560f0>] (ath6kl_sdio_irq_handler+0x48/0xac [ar6000])
<fonz93> <4>[ 572.528619] [<bf0560f0>] (ath6kl_sdio_irq_handler+0x48/0xac [ar6000]) from [<c051995c>] (sdio_irq_thread+0x208/0x39c)
<fonz93> <4>[ 572.528644] [<c051995c>] (sdio_irq_thread+0x208/0x39c) from [<c00c9d5c>] (kthread+0x98/0x9c)
<fonz93> <4>[ 572.528668] [<c00c9d5c>] (kthread+0x98/0x9c) from [<c0010284>] (kernel_thread_exit+0x0/0x8)
<fonz93> it should be a backtrace?
<Dazzozo> ye, it is one
<Dazzozo> looks like ath6kl is allocating something itself?
<Dazzozo> and its choking on that
<Dazzozo> though, i don't know why this is going fatal
<Dazzozo> surely if the kernel can't allocate the memory it should kindly tell the requesting code to fuck off
<Dazzozo> and not die deep in alloc code
<Dazzozo> ? idk
<fonz93> weird things happen on this device
<Dazzozo> really, you shouldnt have to hack every allocation, because this issue will extend to other subsystems too
<Dazzozo> and you would be there all year
<Dazzozo> there's either some obvious misconfiguration or the kernel is very broken
<fonz93> what if i add some code that cleares the atkh6l buffer before it gets full?
<fonz93> what about this? just finding slub allocator commits in the kernel...
<Dazzozo> well, it could be anything, if you've changed the allocator you're using
<Dazzozo> try reverting it back to the original code
<Dazzozo> if the issue was there from CAF then that's going to be fun
<fonz93> oh god
<Dazzozo> im preeeetty sure the move to 3.4 fixed the issue with the G300
<Dazzozo> and I didn't need to hack it anymore
<fonz93> well the kernel is a chil360-kernel fork
<Dazzozo> so it might be something you guys introduced
<fonz93> changes on slub were introduced by that commit i linked and some others to update the kernel on 3.4.y versions
<luca020400> so add chil360 patches to huawei kernel :p
<fonz93> 450+ commits :(
<luca020400> not that difficult
<luca020400> xd
<fonz93> i think that he tried to do that already anyway
<luca020400> I will do that
<fonz93> how?
<luca020400> squash
<Dazzozo> just restore slub to how it was in my 3.4 kernel
<Dazzozo> i don't think i modified it
<fonz93> ok i'll try it right now
<luca020400> om
<luca020400> g
<luca020400> 90 kb/s
<luca020400> download
<luca020400> xd
<Dazzozo> yeah i didnt
<luca020400> he did
<luca020400> great
<luca020400> 80000 lines of patch
<luca020400> xd
<fonz93> D:
<fonz93> did you include KSGSL/ION/framebuffer patches only?
<fonz93> *KGSL
<luca020400> seems like
<luca020400> xd
<luca020400> diff from a162fdd8e68b1e2aaafbc5f03df24aa4a8041961..7f517c19434902f6071d0a37f54ebe55c76f52ca
<Dazzozo> da fak is this
<luca020400> gitignore is weird
<luca020400> d
<luca020400> d
<luca020400> wait
<luca020400> xd
<luca020400> inverted patch xd
<fonz93> just reverte slub to caf
<fonz93> didn't solve the issue
<fonz93> so what that diff contain?
<luca020400> is broken xd
<fonz93> no swap errors while using mobile data
<fonz93> so i suppose the slub allocator goes crazy using wifi only
<fonz93> no wait i didn't enalbe zRAM lol
<fonz93> yes it happens only with wifi enabled
<fonz93> oh god no it doesn't
<luca020400> mobile data too ?
<fonz93> also without any data
<fonz93> switching between apps causes the swap error
<luca020400> oh
<luca020400> fonz93 : can you shut up users asking wifi fix ? thanks :p
gregor160300 has joined #huawei-g300
<rymate1234> luca020400, you can't shut up used
<rymate1234> users
<rymate1234> you can ignore them until wifi is fixed
<rymate1234> :P
<Dazzozo> rymate1234: oh shit
<Dazzozo> wait
<rymate1234> hi
<Dazzozo> theyre trying to make my hobby illegal
<Dazzozo> literally
<Dazzozo> 3ds stuff in here
<Dazzozo> in the exhibits
<rymate1234> Dazzozo, why is it that america hates fun
<gregor160300> Dazzozo do you know why there is only one member left in androidarmv6 since you were also a member
<Dazzozo> fuck knows whats going on with them, i havent been affiliated with them for years
<Dazzozo> i figured the project was pretty dead?
<Dazzozo> what's your interest with them?
<Dazzozo> there were a lot more people at some point
<Dazzozo> either they were all kicked or they all left
<gregor160300> http://postimg.org/image/nrmd8px8h/ I need armv6 support so I can work on android for rpi
<Dazzozo> and if they were all kicked i probably should've been kicked too
<Dazzozo> yeah, 3 people with private membership
<Dazzozo> you have to optionally publicise membership on github
<gregor160300> But last week I saw more members not private
<rymate1234> gregor160300, get with the times
<rymate1234> all about the armv7 rpi2
<gregor160300> I am still about armv6 one
<gregor160300> B+
<rymate1234> i have the armv7 one
<rymate1234> highly superior
<Dazzozo> honestly, i don't really know, you can basically consider me nothing to do with them
<Dazzozo> there was a brief period back in the 4.1 days
<Dazzozo> and thats when the project really sort of "existed"
<gregor160300> I know you are with 3ds
<Dazzozo> well, that's before i started 3ds stuff
<Dazzozo> like, they still have their gerrit...
<Dazzozo> so i guess there's still some interest in it
<gregor160300> I know but is there anything like it on github or so with cm 11 and cm 12 and androidarmv6 support
<Dazzozo> you'll struggle...
<Dazzozo> armv6 really should've died wrt android like 2+ years ago
<luca020400> lol
<gregor160300> Yes but I still need armv6 for rpi, I want android on it
<Dazzozo> i mean in here these guys are struggling getting armv7 devices to run android properly
<Dazzozo> well if you want it be prepared to put the work in ;)
<Dazzozo> you're probably not going to find somewhere that hands you that in a platter
<gregor160300> I am prepared I found some good starts
<rymate1234> gregor160300, easiest way is to not port the latest android on rpi
<rymate1234> ice cream sandwich might be a good thing to start with
<gregor160300> I am working on cm 11
<rymate1234> gl;hf
<gregor160300> I compiled razdroid but it didnt work and installation is too hard
<Dazzozo> honestly there might be small chance of getting gingerbread to go
<Dazzozo> if that doesnt already exist
<gregor160300> It exists it is razdroid
<rymate1234> CyanogenMOD 7.2 (based on Android 2.3): Boots, very slow, barely usable. (unstable)
<gregor160300> But I couldnt install it properly
<Dazzozo> yeah... then no
<gregor160300> I mostly use trevd on github and mozilla-b2g
<Dazzozo> at some point someone needs to realise its not capable
<Dazzozo> it also has no vendor support for android
<rymate1234> gregor160300, your main issue is there's no hardware accelerated drivers for the Pi that work with android
<Dazzozo> ^
<gregor160300> It is capable but it requires a lot of work
<Dazzozo> no, it isnt
<Dazzozo> for reasons outside of the device itself
<rymate1234> gregor160300, do you know how to write a graphics driver?
<rymate1234> Framebuffer issues: possibly due to the lack of double buffering and/or page flipping in the bcm2708 framebuffer driver
<rymate1234> Proper libEGL library not present: libraries *are* available, but those are linked against glibc instead of android's bionic libc (issue filed here)
<rymate1234> UI Crashes
<gregor160300> There was someone with hw accelerated ics, so I mailed and asked for the sources
<Dazzozo> alternatively, you could buy a phone
<gregor160300> I first need to build cm 11 properly and the I will see further
<gregor160300> I have a phone moto g 2014
<rymate1234> use that for android
<rymate1234> android isn't really meant for a device like the raspberry pu
<rymate1234> pi
<gregor160300> I don´t know what to use my pi for then
<gregor160300> A webserver is too slow
<rymate1234> well I have two
<rymate1234> the armv7 rpi works exceptionally well as a web server
<gregor160300> I could sell my B+ and buy B 2
<rymate1234> the armv6 one I have is a pretty good print server
<rymate1234> gregor160300, could use your armv6 one as a media centre
<rymate1234> xbmc works quite well
<gregor160300> I dont need a media centre
<rymate1234> gregor160300, why did you buy it in the first place if you don't know what to do with it
<Dazzozo> i got one for free from my uni B)
<Dazzozo> >for free
<Dazzozo> £9000 a year
<rymate1234> sounds like ur getting value for money Dazzozo
<Dazzozo> frankly i expect to be dead before i'll be concerned with paying that back so
TheFallingOne has joined #huawei-g300
<luca020400> hey
TheFallingOne has quit [Quit: http://www.kiwiirc.com/ - A hand crafted IRC client]
TheFallingOne has joined #huawei-g300
TheFallingOne has quit [Client Quit]
<luca020400> ùxd
<luca020400> *xd
<fonz93> lol
<fonz93> is he drunk?
<luca020400> nah
<luca020400> he's the community manager
<luca020400> ;)
gregor160300 has quit [Quit: Leaving]
gregor160300 has joined #huawei-g300
gregor160300 has quit [Quit: Leaving]
sunnyden has joined #huawei-g300
sunnyden has quit [Remote host closed the connection]
gregor160300-m has joined #huawei-g300
<pyongyang> You could turn the RasPi into a Wifi sniffer.
<gregor160300-m> Why would I
gregor160300-m has quit [Remote host closed the connection]
fonz93 has quit [Quit: Leaving]
fonz93 has joined #huawei-g300
TheFallingOne has joined #huawei-g300
TheFallingOne has quit [Client Quit]
Weritos has joined #huawei-g300
<Weritos> Hi all
<luca020400> hey
<Weritos> What else can be used in addition to these figures?
<Weritos> I have 768 RAM
Weritos has quit [Quit: http://www.kiwiirc.com/ - A hand crafted IRC client]
fonz93 has quit [Quit: Leaving]
fonz93 has joined #huawei-g300
fonz93 has quit [Quit: Leaving]
gregor160300 has joined #huawei-g300
gregor160300 has quit [Client Quit]
gregor160300 has joined #huawei-g300
gregor160300 has quit [Client Quit]
luca020400 has quit [Quit: Leaving]
luca020400 has joined #huawei-g300
Shadowghoster is now known as Ghost|afk
Ghost|afk is now known as Shadowghoster
luca020400-m has joined #huawei-g300
luca020400 has quit [Read error: Connection reset by peer]
Shadowghoster is now known as Ghost|afk
luca020400-m has quit [Remote host closed the connection]