Re: Resume bug on 2.6.39 kernel identified! (was QTMoko v55 GTA02 flash issue)

2014-01-29 Thread Peter Viskup
Radek Polak: On Monday, January 20, 2014 05:04:53 PM Jake Drexel wrote: the mmc0 device is actually where the ar6000 (wifi) is conneted. I had the same problem with the 2.6.39 kernel on shr. The issue looks hw and sw related. My wifi-board was not connected very well but with older kernel

Re: Resume bug on 2.6.39 kernel identified! (was QTMoko v55 GTA02 flash issue)

2014-01-27 Thread Giacomo 'giotti' Mariani
Hi Radek, all, Hi, it seems that thanks to your mail we have discovered resume problems on 2.6.39 kernels! I tried rmmod ar6000 and i cant reproduce my resume issues anymore! I had running my dial script over night. Freerunner now shows 333 succesful resumes, while it used to fail

Re: Resume bug on 2.6.39 kernel identified! (was QTMoko v55 GTA02 flash issue)

2014-01-27 Thread Radek Polak
On Monday, January 27, 2014 02:29:10 PM Giacomo 'giotti' Mariani wrote: Hi Radek, all, Hi, it seems that thanks to your mail we have discovered resume problems on 2.6.39 kernels! I tried rmmod ar6000 and i cant reproduce my resume issues anymore! I had running my dial

Re: Resume bug on 2.6.39 kernel identified! (was QTMoko v55 GTA02 flash issue)

2014-01-21 Thread Nick
On Tue, Jan 21, 2014 at 08:15:27AM +0100, Radek Polak wrote: I tried rmmod ar6000 and i cant reproduce my resume issues anymore! I had running my dial script over night. Freerunner now shows 333 succesful resumes, while it used to fail after 30 resumes before. So please if you are using

Re: Resume bug on 2.6.39 kernel identified! (was QTMoko v55 GTA02 flash issue)

2014-01-21 Thread robin
hi radek, thank for digging in so deep to find the bug. If I remove the ar6000 does that also mean that I will not be able to use wifi (that would be my guess)? and as an off topic question: if I remove btusb and bluetooth (as I am not using bluetooth at all) would this somehow interfere with

Re: Resume bug on 2.6.39 kernel identified! (was QTMoko v55 GTA02 flash issue)

2014-01-21 Thread Radek Polak
On Tuesday, January 21, 2014 10:53:08 AM robin wrote: hi radek, thank for digging in so deep to find the bug. If I remove the ar6000 does that also mean that I will not be able to use wifi (that would be my guess)? Yes Maybe it would be possible to use before-suspend.sh and

Re: Resume bug on 2.6.39 kernel identified! (was QTMoko v55 GTA02 flash issue)

2014-01-21 Thread Radek Polak
On Tuesday, January 21, 2014 10:21:09 AM Jake Drexel wrote: On 1/21/14, Jake Drexel jackram...@googlemail.com wrote: Good to hear that. The strange thing is that the issue also is hw dependend. After I took apart my phone, reseated the wifi-board, put it back together, and replaced the two

Re: QTMoko v55 GTA02 flash issue

2014-01-20 Thread Peter Viskup
Radek Polak: On Sunday, January 19, 2014 08:21:20 PM Peter Viskup wrote: Btw can you try if USB networking works in this state? Yes - USB network is available and screen is blank with non-blinking cursor in left top corner. ___ Openmoko community

Resume bug on 2.6.39 kernel identified! (was QTMoko v55 GTA02 flash issue)

2014-01-20 Thread Radek Polak
On Monday, January 20, 2014 05:04:53 PM Jake Drexel wrote: the mmc0 device is actually where the ar6000 (wifi) is conneted. I had the same problem with the 2.6.39 kernel on shr. The issue looks hw and sw related. My wifi-board was not connected very well but with older kernel it still worked,

QTMoko v55 GTA02 flash issue

2014-01-19 Thread Peter Viskup
After upgrade of QTMoko to latest v55 my GTA02 don't wake-up to fully functional state after some random time (more suspends/resumes and uptime of some days). Looks like the flash didn't become available/writable. Seeing these messages: [64691.81] s3c-sdi s3c2440-sdi: running at 400kHz

Re: QTMoko v55 GTA02 flash issue

2014-01-19 Thread Radek Polak
On Sunday, January 19, 2014 08:21:20 PM Peter Viskup wrote: After upgrade of QTMoko to latest v55 my GTA02 don't wake-up to fully functional state after some random time (more suspends/resumes and uptime of some days). Looks like the flash didn't become available/writable. Seeing these