February 2015 - kernel - Fedora Mailing-Lists

Re: Android Emulator not working with 3.18.3-201.fc21 and onwards

by Sudhir Khanger

On Thu, Feb 12, 2015 at 10:23 PM, Josh Boyer <jwboyer(a)fedoraproject.org> wrote: > 3.19 is perfectly OK to recommend for the purpose of seeing if this is > resolved in newer kernels. If that works then we have a range to look at. > If it doesn't, then 3.18.0 would be the next to try to see if the problem > came in with that release or if it was introduced in the stable series. 3.19 is also a no go. Emulator with API 21 gets stuck at boot with black screen with same connection refused networking error I posted before. -- Regards, Sudhir Khanger, sudhirkhanger.com, github.com/donniezazen, 5577 8CDB A059 085D 1D60 807F 8C00 45D9 F5EF C394.

9 years, 2 months

1
0
0 / 0

Re: Android Emulator not working with 3.18.3-201.fc21 and onwards

by Sudhir Khanger

On Thu, Feb 12, 2015 at 4:48 PM, drago01 <drago01(a)gmail.com> wrote: > On Wed, Feb 11, 2015 at 11:50 AM, Sudhir Khanger <ml(a)sudhirkhanger.com> wrote: >> Dang sent it to the wrong mailing list. Drago01 please advise. >> >> ---------- Forwarded message ---------- >> From: Sudhir Khanger <ml(a)sudhirkhanger.com> >> Date: Sat, Feb 7, 2015 at 6:08 PM >> Subject: Re: Android Emulator not working with 3.18.3-201.fc21 and onwards >> To: security(a)lists.fedoraproject.org >> >> >> On Saturday, February 07, 2015 10:15:17 AM you wrote: >>> I have just tested it ... it works just fine here with the 3.18 kernel. >> >> Are you using Android Studio or Eclipse with ADT? What hardware profile, api >> level and GPU enabled/disabled profiles are you using for your avds? > > I just used the "Android SDK Manager" Android SDK Manager is used to install source, images, etc. You use AVD Manager to create emulators or AVDs. > >> I deleted all avds on my system and created new ones with default profiles. >> >> Nexus 4 avds work from API 10 to 19 but API 21 doesn't work. >> Nexus 5 & 6 hardware profiles don't work with any APIs. >> I have tried both arm and x86 ones and enabled/disabled GPU, and also tried >> starting with snapshots. >> >> All profiles worked in 3.17 kernel series and some work and some don't in >> 3.18. None of the API 21 are working. > > 4.2.2 / API 17 is what I have installed a while ago ... I tested it > and it seems to run just fine. > I created a Nexus 6 5.0.1 / API 21 and this does indeed not work (black screen), Good. The problem is 100% reproducible for at least 3 concerned folks. -- Regards, Sudhir Khanger, sudhirkhanger.com, github.com/donniezazen, 5577 8CDB A059 085D 1D60 807F 8C00 45D9 F5EF C394.

9 years, 2 months

4
4
0 / 0

Re: Android Emulator not working with 3.18.3-201.fc21 and onwards

by Sudhir Khanger

On Thu, Feb 12, 2015 at 7:42 PM, Justin M. Forbes <jforbes(a)redhat.com> wrote: > Is the problem reproducible on 3.19? I will leave 3.19.0 in > rawhide-nodebug for a couple of days to allow testing. > > http://fedoraproject.org/wiki/RawhideKernelNodebug Will the rawhide kernel work on Fedora 21 for testing purposes? If not I will try to find a machine to run Rawhide The following error seems to be causing the problem. emulator: Error while connecting to socket '127.0.0.1:1970': 111 -> Connection refused emulator: ASC 127.0.0.1:1970: Retrying connection. Connector FD = 27 emulator: Error while connecting to socket '127.0.0.1:1970': 111 -> Connection refused emulator: ASC 127.0.0.1:1970: Retrying connection. Connector FD = 27 emulator: Error while connecting to socket '127.0.0.1:1970': 111 -> Connection refused emulator: ASC 127.0.0.1:1970: Retrying connection. Connector FD = 27 emulator: Error while connecting to socket '127.0.0.1:1970': 111 -> Connection refused emulator: ASC 127.0.0.1:1970: Retrying connection. Connector FD = 27 emulator: Error while connecting to socket '127.0.0.1:1970': 111 -> Connection refused emulator: ASC 127.0.0.1:1970: Retrying connection. Connector FD = 27 -- Regards, Sudhir Khanger, sudhirkhanger.com, github.com/donniezazen, 5577 8CDB A059 085D 1D60 807F 8C00 45D9 F5EF C394. PS:- Pardon me. I am not sure why emails from me are creating new threads and reply-to is not set to fedora-kernel mailing list. I am using Gmail.

9 years, 2 months

3
2
0 / 0

Fwd: Android Emulator not working with 3.18.3-201.fc21 and onwards

by Sudhir Khanger

Dang sent it to the wrong mailing list. Drago01 please advise. ---------- Forwarded message ---------- From: Sudhir Khanger <ml(a)sudhirkhanger.com> Date: Sat, Feb 7, 2015 at 6:08 PM Subject: Re: Android Emulator not working with 3.18.3-201.fc21 and onwards To: security(a)lists.fedoraproject.org On Saturday, February 07, 2015 10:15:17 AM you wrote: > I have just tested it ... it works just fine here with the 3.18 kernel. Are you using Android Studio or Eclipse with ADT? What hardware profile, api level and GPU enabled/disabled profiles are you using for your avds? I deleted all avds on my system and created new ones with default profiles. Nexus 4 avds work from API 10 to 19 but API 21 doesn't work. Nexus 5 & 6 hardware profiles don't work with any APIs. I have tried both arm and x86 ones and enabled/disabled GPU, and also tried starting with snapshots. All profiles worked in 3.17 kernel series and some work and some don't in 3.18. None of the API 21 are working. -- Regards, Sudhir Khanger, sudhirkhanger.com, github.com/donniezazen, 5577 8CDB A059 085D 1D60 807F 8C00 45D9 F5EF C394.

9 years, 2 months

2
1
0 / 0

Re: Android Emulator not working with 3.18.3-201.fc21 and onwards

by Sudhir Khanger

On Sat, Feb 7, 2015 at 2:45 PM, drago01 <drago01(a)gmail.com> wrote: > On Sat, Feb 7, 2015 at 7:47 AM, Sudhir Khanger <ml(a)sudhirkhanger.com> wrote: >> On Sun, Feb 1, 2015 at 2:39 AM, Sudhir Khanger <ml(a)sudhirkhanger.com> wrote: >>> Hello, >>> >>> Android Emulator has stopped working with kernel-3.18.3-201.fc21 and also >>> kernel-3.18.4-201.fc21 from updates-testing. It is working fine on >>> kernel-3.17.4-301.fc21.x86_64. Please see the logs. >>> >>> Not working - http://fpaste.org/179320/ >>> >>> Working - http://fpaste.org/179321/ >> >> My Android development environment is still broken with >> kernel-3.18.5-201.fc21.x86_64. Android Emulator is not working with >> anymore with any 3.18 kernel. Any ideas would be much appreciated. >> >> Emulator verbose outpur - http://ur1.ca/jnyjo >> >> dmesg - http://ur1.ca/jnyk1 >> > > I have just tested it ... it works just fine here with the 3.18 kernel. Also fails with 3.18.6-200.fc21.x86_64 from updates-testing. Another person reported same problem. https://bugzilla.redhat.com/show_bug.cgi?id=1187982 -- Regards, Sudhir Khanger, sudhirkhanger.com, github.com/donniezazen, 5577 8CDB A059 085D 1D60 807F 8C00 45D9 F5EF C394.

9 years, 2 months

1
0
0 / 0

Android Emulator not working with 3.18.3-201.fc21 and onwards

by Sudhir Khanger

Hello, Android Emulator has stopped working with kernel-3.18.3-201.fc21 and also kernel-3.18.4-201.fc21 from updates-testing. It is working fine on kernel-3.17.4-301.fc21.x86_64. Please see the logs. Not working - http://fpaste.org/179320/ Working - http://fpaste.org/179321/ -- Regards, Sudhir Khanger, sudhirkhanger.com, github.com/donniezazen, 5577 8CDB A059 085D 1D60 807F 8C00 45D9 F5EF C394.

9 years, 2 months

2
2
0 / 0

Trouble cross compiling for powerpc

by Paul Bolle

I'm having trouble cross compiling on an up-to-date x64_64 F20 machine. make CROSS_COMPILE=powerpc64-linux-gnu- ARCH=powerpc drivers/dma/ppc4xx/adma.o CHK include/config/kernel.release CHK include/generated/uapi/linux/version.h CHK include/generated/utsrelease.h CALL scripts/checksyscalls.sh CC drivers/dma/ppc4xx/adma.o {standard input}: Assembler messages: {standard input}:4475: Error: junk at end of line: `1' {standard input}:4616: Error: junk at end of line: `1' {standard input}:4626: Error: junk at end of line: `1' {standard input}:4649: Error: junk at end of line: `1' make[1]: *** [drivers/dma/ppc4xx/adma.o] Error 1 make: *** [drivers/dma/ppc4xx/adma.o] Error 2 make CROSS_COMPILE=powerpc64-linux-gnu- ARCH=powerpc CFLAGS_adma.o="-S" drivers/dma/ppc4xx/adma.o CHK include/config/kernel.release CHK include/generated/uapi/linux/version.h CHK include/generated/utsrelease.h CALL scripts/checksyscalls.sh CC drivers/dma/ppc4xx/adma.o sed -n -e "4475p; 4616p; 4626p; 4649p" drivers/dma/ppc4xx/adma.o mfcr 10,1 mfcr 10,1 mfcr 10,1 mfcr 10,1 Anyone else seeing this? Is powerpc64-linux-gnu-gcc choking on the assembler it generates itself, or am I doing something wrong? Paul Bolle

9 years, 2 months

3
6
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

kernel February 2015