Discussion:
kernel 4.17rc cycle problem with x86_64 builds
(too old to reply)
youling 257
2018-05-22 08:32:27 UTC
Permalink
what problem

圚 2018幎5月22日星期二 UTC+8䞋午1:02:17Mauro Rossi写道
Hi,
while testing x86_64 oreo-x86 build with recent kernels
I encountered a problem, with all 4.17 release candidates;
x86 32bit build is ok, but x86_64 kernel freezes in the early stage of
boot.
Has someone seen this issue and do you know how to solve?
Mauro
--
You received this message because you are subscribed to the Google Groups "Android-x86" group.
To unsubscribe from this group and stop receiving emails from it, send an email to android-x86+***@googlegroups.com.
To post to this group, send email to android-***@googlegroups.com.
Visit this group at https://groups.google.com/group/android-x86.
For more options, visit https://groups.google.com/d/optout.
Mauro Rossi
2018-05-22 17:57:13 UTC
Permalink
Post by youling 257
what problem
On Lenovo T460 I cannot pass the initial txt boot screen and laptop stays
frozen

Could you send me your kernel sources repo link and x86_64 defconfig files,
I will use kdiff to check how they differ from mine.
Thanks youling 257

Mauro
Post by youling 257
圚 2018幎5月22日星期二 UTC+8䞋午1:02:17Mauro Rossi写道
Hi,
while testing x86_64 oreo-x86 build with recent kernels
I encountered a problem, with all 4.17 release candidates;
x86 32bit build is ok, but x86_64 kernel freezes in the early stage of
boot.
Has someone seen this issue and do you know how to solve?
Mauro
--
You received this message because you are subscribed to the Google Groups "Android-x86" group.
To unsubscribe from this group and stop receiving emails from it, send an email to android-x86+***@googlegroups.com.
To post to this group, send email to android-***@googlegroups.com.
Visit this group at https://groups.google.com/group/android-x86.
For more options, visit https://groups.google.com/d/optout.
Guneet Atwal
2018-05-24 13:54:25 UTC
Permalink
i am still getting stuck on boot when trying 4.17rc6 kernel , everything
else is stock oreo-x86. Can you tell me if i need to make any change in the
device tree or something else ?
https://github.com/youling257/android-4.9/commits/experimental/android-mainline-4.17-tracking
圚 2018幎5月23日星期䞉 UTC+8䞊午1:57:13Mauro Rossi写道
Post by Mauro Rossi
Post by youling 257
what problem
On Lenovo T460 I cannot pass the initial txt boot screen and laptop stays
frozen
Could you send me your kernel sources repo link and x86_64 defconfig
files, I will use kdiff to check how they differ from mine.
Thanks youling 257
Mauro
Post by youling 257
圚 2018幎5月22日星期二 UTC+8䞋午1:02:17Mauro Rossi写道
Hi,
while testing x86_64 oreo-x86 build with recent kernels
I encountered a problem, with all 4.17 release candidates;
x86 32bit build is ok, but x86_64 kernel freezes in the early stage of
boot.
Has someone seen this issue and do you know how to solve?
Mauro
--
You received this message because you are subscribed to the Google Groups "Android-x86" group.
To unsubscribe from this group and stop receiving emails from it, send an email to android-x86+***@googlegroups.com.
To post to this group, send email to android-***@googlegroups.com.
Visit this group at https://groups.google.com/group/android-x86.
For more options, visit https://groups.google.com/d/optout.
youling 257
2018-05-24 14:35:05 UTC
Permalink
4.17 kernelmany timesthe left corner only has a "line"can't load kernel
and initrd.imgtry to reboot and load again.
you can try to use refind or clover. i don't want to say how to use refind.
my English is bad.

圚 2018幎5月24日星期四 UTC+8䞋午9:54:25Guneet Atwal写道
Post by Guneet Atwal
i am still getting stuck on boot when trying 4.17rc6 kernel , everything
else is stock oreo-x86. Can you tell me if i need to make any change in the
device tree or something else ?
https://github.com/youling257/android-4.9/commits/experimental/android-mainline-4.17-tracking
圚 2018幎5月23日星期䞉 UTC+8䞊午1:57:13Mauro Rossi写道
Post by Mauro Rossi
Post by youling 257
what problem
On Lenovo T460 I cannot pass the initial txt boot screen and laptop
stays frozen
Could you send me your kernel sources repo link and x86_64 defconfig
files, I will use kdiff to check how they differ from mine.
Thanks youling 257
Mauro
Post by youling 257
圚 2018幎5月22日星期二 UTC+8䞋午1:02:17Mauro Rossi写道
Hi,
while testing x86_64 oreo-x86 build with recent kernels
I encountered a problem, with all 4.17 release candidates;
x86 32bit build is ok, but x86_64 kernel freezes in the early stage of
boot.
Has someone seen this issue and do you know how to solve?
Mauro
--
You received this message because you are subscribed to the Google Groups "Android-x86" group.
To unsubscribe from this group and stop receiving emails from it, send an email to android-x86+***@googlegroups.com.
To post to this group, send email to android-***@googlegroups.com.
Visit this group at https://groups.google.com/group/android-x86.
For more options, visit https://groups.google.com/d/optout.
youling 257
2018-05-24 14:39:36 UTC
Permalink
see "GRUB _" on the top left of the screen (the underscore seems like a
blinking cursor), and hitting keys does nothing.

yes4.17 kernel have this problem
--
You received this message because you are subscribed to the Google Groups "Android-x86" group.
To unsubscribe from this group and stop receiving emails from it, send an email to android-x86+***@googlegroups.com.
To post to this group, send email to android-***@googlegroups.com.
Visit this group at https://groups.google.com/group/android-x86.
For more options, visit https://groups.google.com/d/optout.
Guneet Atwal
2018-05-25 07:48:58 UTC
Permalink
also how did you compile mesa 18.1.0 ? when i try that i get error that
LLVMAddEarlyCSEMemSSAPass is undefined or when i use LLVM 60 i
get unrecognized module type "llvm_tblgen"
Post by youling 257
see "GRUB _" on the top left of the screen (the underscore seems like a
blinking cursor), and hitting keys does nothing.
yes4.17 kernel have this problem
--
You received this message because you are subscribed to the Google Groups "Android-x86" group.
To unsubscribe from this group and stop receiving emails from it, send an email to android-x86+***@googlegroups.com.
To post to this group, send email to android-***@googlegroups.com.
Visit this group at https://groups.google.com/group/android-x86.
For more options, visit https://groups.google.com/d/optout.
Guneet Atwal
2018-05-25 07:51:20 UTC
Permalink
looks to me like a clang error , maybe i need updated version ?
Post by Guneet Atwal
also how did you compile mesa 18.1.0 ? when i try that i get error that
LLVMAddEarlyCSEMemSSAPass is undefined or when i use LLVM 60 i
get unrecognized module type "llvm_tblgen"
Post by youling 257
see "GRUB _" on the top left of the screen (the underscore seems like a
blinking cursor), and hitting keys does nothing.
yes4.17 kernel have this problem
--
You received this message because you are subscribed to the Google Groups "Android-x86" group.
To unsubscribe from this group and stop receiving emails from it, send an email to android-x86+***@googlegroups.com.
To post to this group, send email to android-***@googlegroups.com.
Visit this group at https://groups.google.com/group/android-x86.
For more options, visit https://groups.google.com/d/optout.
Mauro Rossi
2018-05-25 23:20:37 UTC
Permalink
Post by Guneet Atwal
also how did you compile mesa 18.1.0 ? when i try that i get error that
LLVMAddEarlyCSEMemSSAPass is undefined or when i use LLVM 60 i
get unrecognized module type "llvm_tblgen"
You need llvm 5.0 or 6.0 "side-build", here follows llvm60 commands for
oreo-x86 and nougat-x86:

cd ~/oreo-x86/external
git clone https://github.com/maurossi/llvm llvm60
cd ~/oreo-x86/external/llvm60
git fetch origin oreo-x86_llvm60
git checkout FETCH_HEAD
git remote add llvm-mirror https://github.com/llvm-mirror/llvm
git fetch llvm-mirror release_60
git rebase llvm-mirror/release_60

cd ~/oreo-x86/external/mesa
git reset --hard
git remote add maurossi https://github.com/maurossi/mesa
git fetch maurossi 18.1.0_oreo-x86
git checkout FETCH_HEAD
git apply 0001-DO-NOT-MERGE-android-build-mesa-with-llvm60.patch

[or alternatively for mesa 18.2.0devel]

cd ~/oreo-x86/external/mesa
git reset --hard
git remote add maurossi https://github.com/maurossi/mesa
git fetch maurossi 18.2.0devel_w21
git checkout FETCH_HEAD
git apply 0001-DO-NOT-MERGE-android-build-mesa-with-llvm60.patch

NOTE: if you are building nougat-x86, you will need to checkout x86
oreo-x86 branch of external/libdrm project,
which is modified to install libdrm in /vendor/lib - This step is not
necessary if you are building oreo-x86

cd ~/nougat-x86/external/libdrm/
git fetch x86 oreo-x86
git checkout FETCH_HEAD

cd ~/nougat-x86/external
git clone https://github.com/maurossi/llvm llvm60
cd ~/nougat-x86_kernel/external/llvm60
git fetch origin nougat-x86_llvm60
git checkout FETCH_HEAD
git remote add llvm-mirror https://github.com/llvm-mirror/llvm
git fetch llvm-mirror release_60
git rebase llvm-mirror/release_60

cd ~/nougat-x86/external/mesa
git reset --hard
git remote add maurossi https://github.com/maurossi/mesa
git fetch maurossi 18.1.0_oreo-x86
git checkout FETCH_HEAD
git apply 0001-DO-NOT-MERGE-android-build-mesa-with-llvm60.patch

[or alternatively for mesa 18.2.0devel]

cd ~/nougat-x86/external/mesa
git reset --hard
git remote add maurossi https://github.com/maurossi/mesa
git fetch maurossi 18.2.0devel_w21
git checkout FETCH_HEAD
git apply 0001-DO-NOT-MERGE-android-build-mesa-with-llvm60.patch
Post by Guneet Atwal
Post by youling 257
see "GRUB _" on the top left of the screen (the underscore seems like a
blinking cursor), and hitting keys does nothing.
yes4.17 kernel have this problem
--
You received this message because you are subscribed to the Google Groups "Android-x86" group.
To unsubscribe from this group and stop receiving emails from it, send an email to android-x86+***@googlegroups.com.
To post to this group, send email to android-***@googlegroups.com.
Visit this group at https://groups.google.com/group/android-x86.
For more options, visit https://groups.google.com/d/optout.
Guneet Atwal
2018-05-26 10:32:00 UTC
Permalink
can you tell me why my kernel 4.17rc6 32bit build with mesa 18.0.4 is
working fine on my old core i3 laptop and not on my cherry trail z8350
laptop ? it boots fine and then i only see terminal. No bootanimation
nothing.
Post by Mauro Rossi
Post by Guneet Atwal
also how did you compile mesa 18.1.0 ? when i try that i get error that
LLVMAddEarlyCSEMemSSAPass is undefined or when i use LLVM 60 i
get unrecognized module type "llvm_tblgen"
You need llvm 5.0 or 6.0 "side-build", here follows llvm60 commands for
cd ~/oreo-x86/external
git clone https://github.com/maurossi/llvm llvm60
cd ~/oreo-x86/external/llvm60
git fetch origin oreo-x86_llvm60
git checkout FETCH_HEAD
git remote add llvm-mirror https://github.com/llvm-mirror/llvm
git fetch llvm-mirror release_60
git rebase llvm-mirror/release_60
cd ~/oreo-x86/external/mesa
git reset --hard
git remote add maurossi https://github.com/maurossi/mesa
git fetch maurossi 18.1.0_oreo-x86
git checkout FETCH_HEAD
git apply 0001-DO-NOT-MERGE-android-build-mesa-with-llvm60.patch
[or alternatively for mesa 18.2.0devel]
cd ~/oreo-x86/external/mesa
git reset --hard
git remote add maurossi https://github.com/maurossi/mesa
git fetch maurossi 18.2.0devel_w21
git checkout FETCH_HEAD
git apply 0001-DO-NOT-MERGE-android-build-mesa-with-llvm60.patch
NOTE: if you are building nougat-x86, you will need to checkout x86
oreo-x86 branch of external/libdrm project,
which is modified to install libdrm in /vendor/lib - This step is not
necessary if you are building oreo-x86
cd ~/nougat-x86/external/libdrm/
git fetch x86 oreo-x86
git checkout FETCH_HEAD
cd ~/nougat-x86/external
git clone https://github.com/maurossi/llvm llvm60
cd ~/nougat-x86_kernel/external/llvm60
git fetch origin nougat-x86_llvm60
git checkout FETCH_HEAD
git remote add llvm-mirror https://github.com/llvm-mirror/llvm
git fetch llvm-mirror release_60
git rebase llvm-mirror/release_60
cd ~/nougat-x86/external/mesa
git reset --hard
git remote add maurossi https://github.com/maurossi/mesa
git fetch maurossi 18.1.0_oreo-x86
git checkout FETCH_HEAD
git apply 0001-DO-NOT-MERGE-android-build-mesa-with-llvm60.patch
[or alternatively for mesa 18.2.0devel]
cd ~/nougat-x86/external/mesa
git reset --hard
git remote add maurossi https://github.com/maurossi/mesa
git fetch maurossi 18.2.0devel_w21
git checkout FETCH_HEAD
git apply 0001-DO-NOT-MERGE-android-build-mesa-with-llvm60.patch
Post by Guneet Atwal
Post by youling 257
see "GRUB _" on the top left of the screen (the underscore seems like a
blinking cursor), and hitting keys does nothing.
yes4.17 kernel have this problem
--
You received this message because you are subscribed to the Google Groups "Android-x86" group.
To unsubscribe from this group and stop receiving emails from it, send an email to android-x86+***@googlegroups.com.
To post to this group, send email to android-***@googlegroups.com.
Visit this group at https://groups.google.com/group/android-x86.
For more options, visit https://groups.google.com/d/optout.
Mauro Rossi
2018-05-27 06:48:55 UTC
Permalink
I forgot that also for external/drm_gralloc is nececessary in case you
build nougat-x86,
but I suppose, since you booted on Core i3, that you are using oreo-x86
latest repo update.
Post by Guneet Atwal
can you tell me why my kernel 4.17rc6 32bit build with mesa 18.0.4 is
working fine on my old core i3 laptop and not on my cherry trail z8350
laptop ? it boots fine and then i only see terminal. No bootanimation
nothing.
It was reported in the past past that that cherry trail is problematic
dmesg, logcat are needed to analyze what prevents SurfaceFlinger showing
the GUI
Could you please provide yours?
Thanks
Post by Guneet Atwal
Post by Mauro Rossi
Post by Guneet Atwal
also how did you compile mesa 18.1.0 ? when i try that i get error that
LLVMAddEarlyCSEMemSSAPass is undefined or when i use LLVM 60 i
get unrecognized module type "llvm_tblgen"
You need llvm 5.0 or 6.0 "side-build", here follows llvm60 commands for
cd ~/oreo-x86/external
git clone https://github.com/maurossi/llvm llvm60
cd ~/oreo-x86/external/llvm60
git fetch origin oreo-x86_llvm60
git checkout FETCH_HEAD
git remote add llvm-mirror https://github.com/llvm-mirror/llvm
git fetch llvm-mirror release_60
git rebase llvm-mirror/release_60
cd ~/oreo-x86/external/mesa
git reset --hard
git remote add maurossi https://github.com/maurossi/mesa
git fetch maurossi 18.1.0_oreo-x86
git checkout FETCH_HEAD
git apply 0001-DO-NOT-MERGE-android-build-mesa-with-llvm60.patch
[or alternatively for mesa 18.2.0devel]
cd ~/oreo-x86/external/mesa
git reset --hard
git remote add maurossi https://github.com/maurossi/mesa
git fetch maurossi 18.2.0devel_w21
git checkout FETCH_HEAD
git apply 0001-DO-NOT-MERGE-android-build-mesa-with-llvm60.patch
NOTE: if you are building nougat-x86, you will need to checkout x86
oreo-x86 branch of external/libdrm project,
which is modified to install libdrm in /vendor/lib - This step is not
necessary if you are building oreo-x86
cd ~/nougat-x86/external/libdrm/
git fetch x86 oreo-x86
git checkout FETCH_HEAD
cd ~/nougat-x86/external
git clone https://github.com/maurossi/llvm llvm60
cd ~/nougat-x86_kernel/external/llvm60
git fetch origin nougat-x86_llvm60
git checkout FETCH_HEAD
git remote add llvm-mirror https://github.com/llvm-mirror/llvm
git fetch llvm-mirror release_60
git rebase llvm-mirror/release_60
cd ~/nougat-x86/external/mesa
git reset --hard
git remote add maurossi https://github.com/maurossi/mesa
git fetch maurossi 18.1.0_oreo-x86
git checkout FETCH_HEAD
git apply 0001-DO-NOT-MERGE-android-build-mesa-with-llvm60.patch
[or alternatively for mesa 18.2.0devel]
cd ~/nougat-x86/external/mesa
git reset --hard
git remote add maurossi https://github.com/maurossi/mesa
git fetch maurossi 18.2.0devel_w21
git checkout FETCH_HEAD
git apply 0001-DO-NOT-MERGE-android-build-mesa-with-llvm60.patch
Post by Guneet Atwal
Post by youling 257
see "GRUB _" on the top left of the screen (the underscore seems like
a blinking cursor), and hitting keys does nothing.
yes4.17 kernel have this problem
--
You received this message because you are subscribed to the Google Groups "Android-x86" group.
To unsubscribe from this group and stop receiving emails from it, send an email to android-x86+***@googlegroups.com.
To post to this group, send email to android-***@googlegroups.com.
Visit this group at https://groups.google.com/group/android-x86.
For more options, visit https://groups.google.com/d/optout.
Guneet Atwal
2018-06-14 10:17:40 UTC
Permalink
when i try to build using llvm60 and mesa 18.1.0 then i get this error
error: undefined reference to
'llvm::initializeX86FlagsCopyLoweringPassPass(llvm::PassRegistry&
external/llvm60/lib/Target/X86/X86TargetMachine.cpp:420: error: undefined
reference to 'llvm::createX86FlagsCopyLoweringPass()'

Any idea what i might be missing here
Post by Mauro Rossi
Post by Guneet Atwal
also how did you compile mesa 18.1.0 ? when i try that i get error that
LLVMAddEarlyCSEMemSSAPass is undefined or when i use LLVM 60 i
get unrecognized module type "llvm_tblgen"
You need llvm 5.0 or 6.0 "side-build", here follows llvm60 commands for
cd ~/oreo-x86/external
git clone https://github.com/maurossi/llvm llvm60
cd ~/oreo-x86/external/llvm60
git fetch origin oreo-x86_llvm60
git checkout FETCH_HEAD
git remote add llvm-mirror https://github.com/llvm-mirror/llvm
git fetch llvm-mirror release_60
git rebase llvm-mirror/release_60
cd ~/oreo-x86/external/mesa
git reset --hard
git remote add maurossi https://github.com/maurossi/mesa
git fetch maurossi 18.1.0_oreo-x86
git checkout FETCH_HEAD
git apply 0001-DO-NOT-MERGE-android-build-mesa-with-llvm60.patch
[or alternatively for mesa 18.2.0devel]
cd ~/oreo-x86/external/mesa
git reset --hard
git remote add maurossi https://github.com/maurossi/mesa
git fetch maurossi 18.2.0devel_w21
git checkout FETCH_HEAD
git apply 0001-DO-NOT-MERGE-android-build-mesa-with-llvm60.patch
NOTE: if you are building nougat-x86, you will need to checkout x86
oreo-x86 branch of external/libdrm project,
which is modified to install libdrm in /vendor/lib - This step is not
necessary if you are building oreo-x86
cd ~/nougat-x86/external/libdrm/
git fetch x86 oreo-x86
git checkout FETCH_HEAD
cd ~/nougat-x86/external
git clone https://github.com/maurossi/llvm llvm60
cd ~/nougat-x86_kernel/external/llvm60
git fetch origin nougat-x86_llvm60
git checkout FETCH_HEAD
git remote add llvm-mirror https://github.com/llvm-mirror/llvm
git fetch llvm-mirror release_60
git rebase llvm-mirror/release_60
cd ~/nougat-x86/external/mesa
git reset --hard
git remote add maurossi https://github.com/maurossi/mesa
git fetch maurossi 18.1.0_oreo-x86
git checkout FETCH_HEAD
git apply 0001-DO-NOT-MERGE-android-build-mesa-with-llvm60.patch
[or alternatively for mesa 18.2.0devel]
cd ~/nougat-x86/external/mesa
git reset --hard
git remote add maurossi https://github.com/maurossi/mesa
git fetch maurossi 18.2.0devel_w21
git checkout FETCH_HEAD
git apply 0001-DO-NOT-MERGE-android-build-mesa-with-llvm60.patch
Post by Guneet Atwal
Post by youling 257
see "GRUB _" on the top left of the screen (the underscore seems like a
blinking cursor), and hitting keys does nothing.
yes4.17 kernel have this problem
--
You received this message because you are subscribed to the Google Groups "Android-x86" group.
To unsubscribe from this group and stop receiving emails from it, send an email to android-x86+***@googlegroups.com.
To post to this group, send email to android-***@googlegroups.com.
Visit this group at https://groups.google.com/group/android-x86.
For more options, visit https://groups.google.com/d/optout.
Mauro Rossi
2018-06-14 21:03:18 UTC
Permalink
Post by Guneet Atwal
when i try to build using llvm60 and mesa 18.1.0 then i get this error
error: undefined reference to
'llvm::initializeX86FlagsCopyLoweringPassPass(llvm::PassRegistry&
external/llvm60/lib/Target/X86/X86TargetMachine.cpp:420: error: undefined
reference to 'llvm::createX86FlagsCopyLoweringPass()'
I did not see this error when building mesa 18.1.0,
please try to checkout oreo-x86_llvm60 without doing the rebase to
llvm-mirror/release_60, which may have changed/evolved

cd ~/oreo-x86/external
git clone https://github.com/maurossi/llvm llvm60
cd ~/oreo-x86/external/llvm60
git fetch origin oreo-x86_llvm60
git checkout FETCH_HEAD
git remote add llvm-mirror https://github.com/llvm-mirror/llvm
#git fetch llvm-mirror release_60
#git rebase llvm-mirror/release_60

As an alternative, you could use the updated oreo-x86_llvm70 branch, but in
that case you need to change external/mesa/Android.mk accordingly with
attached patch

cd ~/oreo-x86/external
git clone https://github.com/maurossi/llvm llvm70
cd ~/oreo-x86/external/llvm70
git fetch origin oreo-x86_llvm70
git checkout FETCH_HEAD
Post by Guneet Atwal
Any idea what i might be missing here
Post by Mauro Rossi
Post by Guneet Atwal
also how did you compile mesa 18.1.0 ? when i try that i get error that
LLVMAddEarlyCSEMemSSAPass is undefined or when i use LLVM 60 i
get unrecognized module type "llvm_tblgen"
You need llvm 5.0 or 6.0 "side-build", here follows llvm60 commands for
cd ~/oreo-x86/external
git clone https://github.com/maurossi/llvm llvm60
cd ~/oreo-x86/external/llvm60
git fetch origin oreo-x86_llvm60
git checkout FETCH_HEAD
git remote add llvm-mirror https://github.com/llvm-mirror/llvm
git fetch llvm-mirror release_60
git rebase llvm-mirror/release_60
cd ~/oreo-x86/external/mesa
git reset --hard
git remote add maurossi https://github.com/maurossi/mesa
git fetch maurossi 18.1.0_oreo-x86
git checkout FETCH_HEAD
git apply 0001-DO-NOT-MERGE-android-build-mesa-with-llvm60.patch
[or alternatively for mesa 18.2.0devel]
cd ~/oreo-x86/external/mesa
git reset --hard
git remote add maurossi https://github.com/maurossi/mesa
git fetch maurossi 18.2.0devel_w21
git checkout FETCH_HEAD
git apply 0001-DO-NOT-MERGE-android-build-mesa-with-llvm60.patch
NOTE: if you are building nougat-x86, you will need to checkout x86
oreo-x86 branch of external/libdrm project,
which is modified to install libdrm in /vendor/lib - This step is not
necessary if you are building oreo-x86
cd ~/nougat-x86/external/libdrm/
git fetch x86 oreo-x86
git checkout FETCH_HEAD
cd ~/nougat-x86/external
git clone https://github.com/maurossi/llvm llvm60
cd ~/nougat-x86_kernel/external/llvm60
git fetch origin nougat-x86_llvm60
git checkout FETCH_HEAD
git remote add llvm-mirror https://github.com/llvm-mirror/llvm
git fetch llvm-mirror release_60
git rebase llvm-mirror/release_60
cd ~/nougat-x86/external/mesa
git reset --hard
git remote add maurossi https://github.com/maurossi/mesa
git fetch maurossi 18.1.0_oreo-x86
git checkout FETCH_HEAD
git apply 0001-DO-NOT-MERGE-android-build-mesa-with-llvm60.patch
[or alternatively for mesa 18.2.0devel]
cd ~/nougat-x86/external/mesa
git reset --hard
git remote add maurossi https://github.com/maurossi/mesa
git fetch maurossi 18.2.0devel_w21
git checkout FETCH_HEAD
git apply 0001-DO-NOT-MERGE-android-build-mesa-with-llvm60.patch
Post by Guneet Atwal
Post by youling 257
see "GRUB _" on the top left of the screen (the underscore seems like
a blinking cursor), and hitting keys does nothing.
yes4.17 kernel have this problem
--
You received this message because you are subscribed to the Google Groups "Android-x86" group.
To unsubscribe from this group and stop receiving emails from it, send an email to android-x86+***@googlegroups.com.
To post to this group, send email to android-***@googlegroups.com.
Visit this group at https://groups.google.com/group/android-x86.
For more options, visit https://groups.google.com/d/optout.
zjaro
2018-06-22 09:27:34 UTC
Permalink
Thanks man , rebasing llvm-mirror was causing the issue. Can you tell me
how to add gapps in the ROM ? cause when i use open gapps it gives me
crashes. Same happens even in nougat x86 . But there are no crashes in
official release builds. Thanks in advance.
Post by Mauro Rossi
Post by Guneet Atwal
when i try to build using llvm60 and mesa 18.1.0 then i get this error
error: undefined reference to
'llvm::initializeX86FlagsCopyLoweringPassPass(llvm::PassRegistry&
external/llvm60/lib/Target/X86/X86TargetMachine.cpp:420: error: undefined
reference to 'llvm::createX86FlagsCopyLoweringPass()'
I did not see this error when building mesa 18.1.0,
please try to checkout oreo-x86_llvm60 without doing the rebase to
llvm-mirror/release_60, which may have changed/evolved
cd ~/oreo-x86/external
git clone https://github.com/maurossi/llvm llvm60
cd ~/oreo-x86/external/llvm60
git fetch origin oreo-x86_llvm60
git checkout FETCH_HEAD
git remote add llvm-mirror https://github.com/llvm-mirror/llvm
#git fetch llvm-mirror release_60
#git rebase llvm-mirror/release_60
As an alternative, you could use the updated oreo-x86_llvm70 branch, but
in that case you need to change external/mesa/Android.mk accordingly with
attached patch
cd ~/oreo-x86/external
git clone https://github.com/maurossi/llvm llvm70
cd ~/oreo-x86/external/llvm70
git fetch origin oreo-x86_llvm70
git checkout FETCH_HEAD
Post by Guneet Atwal
Any idea what i might be missing here
Post by Mauro Rossi
Post by Guneet Atwal
also how did you compile mesa 18.1.0 ? when i try that i get error that
LLVMAddEarlyCSEMemSSAPass is undefined or when i use LLVM 60 i
get unrecognized module type "llvm_tblgen"
You need llvm 5.0 or 6.0 "side-build", here follows llvm60 commands for
cd ~/oreo-x86/external
git clone https://github.com/maurossi/llvm llvm60
cd ~/oreo-x86/external/llvm60
git fetch origin oreo-x86_llvm60
git checkout FETCH_HEAD
git remote add llvm-mirror https://github.com/llvm-mirror/llvm
git fetch llvm-mirror release_60
git rebase llvm-mirror/release_60
cd ~/oreo-x86/external/mesa
git reset --hard
git remote add maurossi https://github.com/maurossi/mesa
git fetch maurossi 18.1.0_oreo-x86
git checkout FETCH_HEAD
git apply 0001-DO-NOT-MERGE-android-build-mesa-with-llvm60.patch
[or alternatively for mesa 18.2.0devel]
cd ~/oreo-x86/external/mesa
git reset --hard
git remote add maurossi https://github.com/maurossi/mesa
git fetch maurossi 18.2.0devel_w21
git checkout FETCH_HEAD
git apply 0001-DO-NOT-MERGE-android-build-mesa-with-llvm60.patch
NOTE: if you are building nougat-x86, you will need to checkout x86
oreo-x86 branch of external/libdrm project,
which is modified to install libdrm in /vendor/lib - This step is not
necessary if you are building oreo-x86
cd ~/nougat-x86/external/libdrm/
git fetch x86 oreo-x86
git checkout FETCH_HEAD
cd ~/nougat-x86/external
git clone https://github.com/maurossi/llvm llvm60
cd ~/nougat-x86_kernel/external/llvm60
git fetch origin nougat-x86_llvm60
git checkout FETCH_HEAD
git remote add llvm-mirror https://github.com/llvm-mirror/llvm
git fetch llvm-mirror release_60
git rebase llvm-mirror/release_60
cd ~/nougat-x86/external/mesa
git reset --hard
git remote add maurossi https://github.com/maurossi/mesa
git fetch maurossi 18.1.0_oreo-x86
git checkout FETCH_HEAD
git apply 0001-DO-NOT-MERGE-android-build-mesa-with-llvm60.patch
[or alternatively for mesa 18.2.0devel]
cd ~/nougat-x86/external/mesa
git reset --hard
git remote add maurossi https://github.com/maurossi/mesa
git fetch maurossi 18.2.0devel_w21
git checkout FETCH_HEAD
git apply 0001-DO-NOT-MERGE-android-build-mesa-with-llvm60.patch
Post by Guneet Atwal
Post by youling 257
see "GRUB _" on the top left of the screen (the underscore seems like
a blinking cursor), and hitting keys does nothing.
yes4.17 kernel have this problem
--
You received this message because you are subscribed to the Google Groups "Android-x86" group.
To unsubscribe from this group and stop receiving emails from it, send an email to android-x86+***@googlegroups.com.
To post to this group, send email to android-***@googlegroups.com.
Visit this group at https://groups.google.com/group/android-x86.
For more options, visit https://groups.google.com/d/optout.
yuki haya
2018-07-01 16:57:25 UTC
Permalink
Hello.

I also have similar problems.
Hang after initrd.
I tried it in various environments.
The only thing that started was when Nested Paging was disabled in
VirtualBox.
In other words, is there a problem with managing memory space?

Thank you.

= Yuki =
--
You received this message because you are subscribed to the Google Groups "Android-x86" group.
To unsubscribe from this group and stop receiving emails from it, send an email to android-x86+***@googlegroups.com.
To post to this group, send email to android-***@googlegroups.com.
Visit this group at https://groups.google.com/group/android-x86.
For more options, visit https://groups.google.com/d/optout.
Mauro Rossi
2018-05-27 22:10:32 UTC
Permalink
Post by youling 257
see "GRUB _" on the top left of the screen (the underscore seems like a
blinking cursor), and hitting keys does nothing.
yes4.17 kernel have this problem
Now x86_64 kernel 4.17rc7 freezes a little bit later with following trace
(pictures only)
Mauro
--
You received this message because you are subscribed to the Google Groups "Android-x86" group.
To unsubscribe from this group and stop receiving emails from it, send an email to android-x86+***@googlegroups.com.
To post to this group, send email to android-***@googlegroups.com.
Visit this group at https://groups.google.com/group/android-x86.
For more options, visit https://groups.google.com/d/optout.
youling 257
2018-05-28 06:06:31 UTC
Permalink
I don't have this problemi have never see this problem.

圚 2018幎5月28日星期䞀 UTC+8䞊午6:10:32Mauro Rossi写道
Post by Mauro Rossi
Post by youling 257
see "GRUB _" on the top left of the screen (the underscore seems like a
blinking cursor), and hitting keys does nothing.
yes4.17 kernel have this problem
Now x86_64 kernel 4.17rc7 freezes a little bit later with following trace
(pictures only)
Mauro
--
You received this message because you are subscribed to the Google Groups "Android-x86" group.
To unsubscribe from this group and stop receiving emails from it, send an email to android-x86+***@googlegroups.com.
To post to this group, send email to android-***@googlegroups.com.
Visit this group at https://groups.google.com/group/android-x86.
For more options, visit https://groups.google.com/d/optout.
spin877
2018-05-29 15:30:15 UTC
Permalink
gcmaes_crypt_by_sg Ú stata inserita il 18 febbraio prova a chiedere a chi ha proposto la patch.
--
You received this message because you are subscribed to the Google Groups "Android-x86" group.
To unsubscribe from this group and stop receiving emails from it, send an email to android-x86+***@googlegroups.com.
To post to this group, send email to android-***@googlegroups.com.
Visit this group at https://groups.google.com/group/android-x86.
For more options, visit https://groups.google.com/d/optout.
youling 257
2018-07-02 08:49:21 UTC
Permalink
https://github.com/torvalds/linux/commit/52e1cf2d19c2e62e6a81b8de3f7320d033917dd5

it fixed my Bay trail problembay trail 32bit uefirunning 64bit kernel.
--
You received this message because you are subscribed to the Google Groups "Android-x86" group.
To unsubscribe from this group and stop receiving emails from it, send an email to android-x86+***@googlegroups.com.
To post to this group, send email to android-***@googlegroups.com.
Visit this group at https://groups.google.com/group/android-x86.
For more options, visit https://groups.google.com/d/optout.
yuki haya
2018-07-07 12:32:22 UTC
Permalink
Hello.

Does the behavior of kernel 4.16 or later Native Bridge behave differently?

There is a problem that the application does not start up.

logcat has an error on libEGL.so.

Thank you.
--
You received this message because you are subscribed to the Google Groups "Android-x86" group.
To unsubscribe from this group and stop receiving emails from it, send an email to android-x86+***@googlegroups.com.
To post to this group, send email to android-***@googlegroups.com.
Visit this group at https://groups.google.com/group/android-x86.
For more options, visit https://groups.google.com/d/optout.
youling 257
2018-07-07 16:32:17 UTC
Permalink
you can test 7.1 rc2 and r1 use 7_y/z houdini running 王者荣耀

4.9、4.10、4.11、4.12、4.13、4.14、4.15、4.16、4.17、4.18all need Revert
"x86/signal/64: Re-add support for SS in the 64-bit signal context"I say
this patchandroid-x86: fix 64bit android7.1 games crashFrom: lixin
<***@phoenixos.com>Date: Sat, 8 Apr 2017 20:06:45 +0800

openthos kernel 4.9、4.14、4.15、4.16、4.17、4.18 has a Revert "x86/signal/64:
Re-add support for SS in the 64-bit signal context" patch by cwhuangfix
5_y/z houdini with high kernel versionthis patch added to Androidx86 7.1
r2 kernel 4.9.

圚 2018幎7月7日星期六 UTC+8䞋午8:32:23yuki haya写道
Post by yuki haya
Hello.
Does the behavior of kernel 4.16 or later Native Bridge behave differently?
There is a problem that the application does not start up.
logcat has an error on libEGL.so.
Thank you.
--
You received this message because you are subscribed to the Google Groups "Android-x86" group.
To unsubscribe from this group and stop receiving emails from it, send an email to android-x86+***@googlegroups.com.
To post to this group, send email to android-***@googlegroups.com.
Visit this group at https://groups.google.com/group/android-x86.
For more options, visit https://groups.google.com/d/optout.
youling 257
2018-07-07 16:41:02 UTC
Permalink
https://github.com/PhoenixOS/kernel/commits/phoenix-4.9/arch/x86/kernel/signal.c
https://github.com/youling257/android-4.9/commits/experimental/android-mainline-4.15-tracking/arch/x86/kernel/signal.c
https://github.com/youling257/android-4.9/commits/experimental/android-mainline-4.16-tracking/arch/x86/kernel/signal.c
https://github.com/youling257/android-4.9/commits/experimental/android-mainline-4.17-tracking/arch/x86/kernel/signal.c
https://github.com/youling257/openthos-kernel/commits/openthos-4.9.31/arch/x86/kernel/signal.c
https://github.com/youling257/openthos-kernel/commits/openthos-4.18/arch/x86/kernel/signal.c
https://github.com/youling257/openthos-kernel/commits/openthos-4.17/arch/x86/kernel/signal.c
https://github.com/youling257/openthos-kernel/commits/openthos-4.16/arch/x86/kernel/signal.c
--
You received this message because you are subscribed to the Google Groups "Android-x86" group.
To unsubscribe from this group and stop receiving emails from it, send an email to android-x86+***@googlegroups.com.
To post to this group, send email to android-***@googlegroups.com.
Visit this group at https://groups.google.com/group/android-x86.
For more options, visit https://groups.google.com/d/optout.
Mauro Rossi
2018-07-09 07:33:26 UTC
Permalink
Hi,
thanks a lot

Do you see some kind of freeze happening with 4.18rc expecially with Intel
manufactured chipsets?

My builds with kernel 4.17 and 4.18rc are still not reaching the console
they freeze when autoloading some kernel module
Mauro
Post by youling 257
you can test 7.1 rc2 and r1 use 7_y/z houdini running 王者荣耀
4.9、4.10、4.11、4.12、4.13、4.14、4.15、4.16、4.17、4.18all need Revert
"x86/signal/64: Re-add support for SS in the 64-bit signal context"I say
this patchandroid-x86: fix 64bit android7.1 games crashFrom: lixin <
Re-add support for SS in the 64-bit signal context" patch by cwhuangfix
5_y/z houdini with high kernel versionthis patch added to Androidx86 7.1
r2 kernel 4.9.
圚 2018幎7月7日星期六 UTC+8䞋午8:32:23yuki haya写道
Post by yuki haya
Hello.
Does the behavior of kernel 4.16 or later Native Bridge behave differently?
There is a problem that the application does not start up.
logcat has an error on libEGL.so.
Thank you.
--
You received this message because you are subscribed to the Google Groups "Android-x86" group.
To unsubscribe from this group and stop receiving emails from it, send an email to android-x86+***@googlegroups.com.
To post to this group, send email to android-***@googlegroups.com.
Visit this group at https://groups.google.com/group/android-x86.
For more options, visit https://groups.google.com/d/optout.
t***@gmail.com
2018-07-10 00:53:57 UTC
Permalink
I am also attempting to a build with kernel 4.17 and 4.18 and am failing to
boot completely. Always, the last message I see printed to the console is:

random: crng init done

It takes between 30 seconds and 5 minutes for this message to appear. That
time can be cut down if I randomly press keys on a keyboard, thereby
increasing entropy. I've attempted to boot two different machines, a
SandyBridge desktop and a Broadwell tablet, and received the same result.

I see that experimental-android-4.17 has been tagged at
https://android.googlesource.com/kernel/common/+/experimental-android-4.17,
so my next step will be to roll patches from the maurossi branch into
experimental-android-4.17 and try again.
Post by Mauro Rossi
Hi,
thanks a lot
Do you see some kind of freeze happening with 4.18rc expecially with Intel
manufactured chipsets?
My builds with kernel 4.17 and 4.18rc are still not reaching the console
they freeze when autoloading some kernel module
Mauro
Post by youling 257
you can test 7.1 rc2 and r1 use 7_y/z houdini running 王者荣耀
4.9、4.10、4.11、4.12、4.13、4.14、4.15、4.16、4.17、4.18all need Revert
"x86/signal/64: Re-add support for SS in the 64-bit signal context"I say
this patchandroid-x86: fix 64bit android7.1 games crashFrom: lixin <
Re-add support for SS in the 64-bit signal context" patch by cwhuangfix
5_y/z houdini with high kernel versionthis patch added to Androidx86 7.1
r2 kernel 4.9.
圚 2018幎7月7日星期六 UTC+8䞋午8:32:23yuki haya写道
Post by yuki haya
Hello.
Does the behavior of kernel 4.16 or later Native Bridge behave differently?
There is a problem that the application does not start up.
logcat has an error on libEGL.so.
Thank you.
--
You received this message because you are subscribed to the Google Groups "Android-x86" group.
To unsubscribe from this group and stop receiving emails from it, send an email to android-x86+***@googlegroups.com.
To post to this group, send email to android-***@googlegroups.com.
Visit this group at https://groups.google.com/group/android-x86.
For more options, visit https://groups.google.com/d/optout.
Mauro Rossi
2018-07-11 17:09:41 UTC
Permalink
Hi,
Post by t***@gmail.com
I am also attempting to a build with kernel 4.17 and 4.18 and am failing
to boot completely. Always, the last message I see printed to the console
random: crng init done
It takes between 30 seconds and 5 minutes for this message to appear. That
time can be cut down if I randomly press keys on a keyboard, thereby
increasing entropy. I've attempted to boot two different machines, a
SandyBridge desktop and a Broadwell tablet, and received the same result.
Thanks for the info, the problem is described
here: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=897572#82

I will try with simple and unsafe approach of 43838a23a05f ("random: fix
crng_ready() test")
Post by t***@gmail.com
I see that experimental-android-4.17 has been tagged at
https://android.googlesource.com/kernel/common/+/experimental-android-4.17,
so my next step will be to roll patches from the maurossi branch into
experimental-android-4.17 and try again.
Post by Mauro Rossi
Hi,
thanks a lot
Do you see some kind of freeze happening with 4.18rc expecially with
Intel manufactured chipsets?
My builds with kernel 4.17 and 4.18rc are still not reaching the console
they freeze when autoloading some kernel module
Mauro
Post by youling 257
you can test 7.1 rc2 and r1 use 7_y/z houdini running 王者荣耀
4.9、4.10、4.11、4.12、4.13、4.14、4.15、4.16、4.17、4.18all need Revert
"x86/signal/64: Re-add support for SS in the 64-bit signal context"I say
this patchandroid-x86: fix 64bit android7.1 games crashFrom: lixin <
openthos kernel 4.9、4.14、4.15、4.16、4.17、4.18 has a Revert
"x86/signal/64: Re-add support for SS in the 64-bit signal context" patch
by cwhuangfix 5_y/z houdini with high kernel versionthis patch added to
Androidx86 7.1 r2 kernel 4.9.
圚 2018幎7月7日星期六 UTC+8䞋午8:32:23yuki haya写道
Post by yuki haya
Hello.
Does the behavior of kernel 4.16 or later Native Bridge behave differently?
There is a problem that the application does not start up.
logcat has an error on libEGL.so.
Thank you.
Hi youling257,

at the moment I do not see improvements with Revert "x86/signal/64: Re-add
support for SS in the 64-bit signal context", but maybe my testing scope
was too restricted (VulkanCapsViewer)

Have you seen improvements?

In which specific arm only application?

Mauro
--
You received this message because you are subscribed to the Google Groups "Android-x86" group.
To unsubscribe from this group and stop receiving emails from it, send an email to android-x86+***@googlegroups.com.
To post to this group, send email to android-***@googlegroups.com.
Visit this group at https://groups.google.com/group/android-x86.
For more options, visit https://groups.google.com/d/optout.
Mauro Rossi
2018-07-11 17:11:34 UTC
Permalink
minor editing correction

43838a23a05f ("random: fix crng_ready() test") needs to be Reverted

Mauro
Post by Mauro Rossi
Hi,
Post by t***@gmail.com
I am also attempting to a build with kernel 4.17 and 4.18 and am failing
to boot completely. Always, the last message I see printed to the console
random: crng init done
It takes between 30 seconds and 5 minutes for this message to appear.
That time can be cut down if I randomly press keys on a keyboard, thereby
increasing entropy. I've attempted to boot two different machines, a
SandyBridge desktop and a Broadwell tablet, and received the same result.
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=897572#82
I will try with simple and unsafe approach of *Reverting* 43838a23a05f
("random: fix crng_ready() test")
Post by t***@gmail.com
I see that experimental-android-4.17 has been tagged at
https://android.googlesource.com/kernel/common/+/experimental-android-4.17,
so my next step will be to roll patches from the maurossi branch into
experimental-android-4.17 and try again.
Post by Mauro Rossi
Hi,
thanks a lot
Do you see some kind of freeze happening with 4.18rc expecially with
Intel manufactured chipsets?
My builds with kernel 4.17 and 4.18rc are still not reaching the console
they freeze when autoloading some kernel module
Mauro
Post by youling 257
you can test 7.1 rc2 and r1 use 7_y/z houdini running 王者荣耀
4.9、4.10、4.11、4.12、4.13、4.14、4.15、4.16、4.17、4.18all need Revert
"x86/signal/64: Re-add support for SS in the 64-bit signal context"I say
this patchandroid-x86: fix 64bit android7.1 games crashFrom: lixin <
openthos kernel 4.9、4.14、4.15、4.16、4.17、4.18 has a Revert
"x86/signal/64: Re-add support for SS in the 64-bit signal context" patch
by cwhuangfix 5_y/z houdini with high kernel versionthis patch added to
Androidx86 7.1 r2 kernel 4.9.
圚 2018幎7月7日星期六 UTC+8䞋午8:32:23yuki haya写道
Post by yuki haya
Hello.
Does the behavior of kernel 4.16 or later Native Bridge behave differently?
There is a problem that the application does not start up.
logcat has an error on libEGL.so.
Thank you.
Hi youling257,
Re-add support for SS in the 64-bit signal context", but maybe my testing
scope was too restricted (VulkanCapsViewer)
Have you seen improvements?
In which specific arm only application?
Mauro
--
You received this message because you are subscribed to the Google Groups "Android-x86" group.
To unsubscribe from this group and stop receiving emails from it, send an email to android-x86+***@googlegroups.com.
To post to this group, send email to android-***@googlegroups.com.
Visit this group at https://groups.google.com/group/android-x86.
For more options, visit https://groups.google.com/d/optout.
youling 257
2018-07-11 17:26:21 UTC
Permalink
nougat 7_y/z houdini
王者荣耀http://dlied5.myapp.com/myapp/1104466820/sgame/2017_com.tencent.tmgp.sgame_h170_1.35.1.10_d756be.apk

圚 2018幎7月12日星期四 UTC+8䞊午1:11:34Mauro Rossi写道
Post by Mauro Rossi
minor editing correction
43838a23a05f ("random: fix crng_ready() test") needs to be Reverted
Mauro
Post by Mauro Rossi
Hi,
Post by t***@gmail.com
I am also attempting to a build with kernel 4.17 and 4.18 and am failing
to boot completely. Always, the last message I see printed to the console
random: crng init done
It takes between 30 seconds and 5 minutes for this message to appear.
That time can be cut down if I randomly press keys on a keyboard, thereby
increasing entropy. I've attempted to boot two different machines, a
SandyBridge desktop and a Broadwell tablet, and received the same result.
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=897572#82
I will try with simple and unsafe approach of *Reverting* 43838a23a05f
("random: fix crng_ready() test")
Post by t***@gmail.com
I see that experimental-android-4.17 has been tagged at
https://android.googlesource.com/kernel/common/+/experimental-android-4.17,
so my next step will be to roll patches from the maurossi branch into
experimental-android-4.17 and try again.
Post by Mauro Rossi
Hi,
thanks a lot
Do you see some kind of freeze happening with 4.18rc expecially with
Intel manufactured chipsets?
My builds with kernel 4.17 and 4.18rc are still not reaching the
console they freeze when autoloading some kernel module
Mauro
Post by youling 257
you can test 7.1 rc2 and r1 use 7_y/z houdini running 王者荣耀
4.9、4.10、4.11、4.12、4.13、4.14、4.15、4.16、4.17、4.18all need Revert
"x86/signal/64: Re-add support for SS in the 64-bit signal context"I say
this patchandroid-x86: fix 64bit android7.1 games crashFrom: lixin <
openthos kernel 4.9、4.14、4.15、4.16、4.17、4.18 has a Revert
"x86/signal/64: Re-add support for SS in the 64-bit signal context" patch
by cwhuangfix 5_y/z houdini with high kernel versionthis patch added to
Androidx86 7.1 r2 kernel 4.9.
圚 2018幎7月7日星期六 UTC+8䞋午8:32:23yuki haya写道
Post by yuki haya
Hello.
Does the behavior of kernel 4.16 or later Native Bridge behave differently?
There is a problem that the application does not start up.
logcat has an error on libEGL.so.
Thank you.
Hi youling257,
Re-add support for SS in the 64-bit signal context", but maybe my testing
scope was too restricted (VulkanCapsViewer)
Have you seen improvements?
In which specific arm only application?
Mauro
--
You received this message because you are subscribed to the Google Groups "Android-x86" group.
To unsubscribe from this group and stop receiving emails from it, send an email to android-x86+***@googlegroups.com.
To post to this group, send email to android-***@googlegroups.com.
Visit this group at https://groups.google.com/group/android-x86.
For more options, visit https://groups.google.com/d/optout.
Mauro Rossi
2018-07-22 20:58:30 UTC
Permalink
Hi,
Post by t***@gmail.com
I am also attempting to a build with kernel 4.17 and 4.18 and am failing
to boot completely. Always, the last message I see printed to the console
random: crng init done
It takes between 30 seconds and 5 minutes for this message to appear. That
time can be cut down if I randomly press keys on a keyboard, thereby
increasing entropy. I've attempted to boot two different machines, a
SandyBridge desktop and a Broadwell tablet, and received the same result.
In order to avoid the wait (or freeze) happening because of random,
enabling CONFIG_HW_RANDOM as builtin helps
In some other project kernel the CONFIG_HW_RANDOM* are all enabled and in
principle they should do no harm.

Now, the only remaining problem is that for me it works only for x86 32bit
kernel,
but at least I can boot with one of the two targets.

Mauro

CONFIG_HW_RANDOM=y
CONFIG_HW_RANDOM_TIMERIOMEM=y
CONFIG_HW_RANDOM_INTEL=y
CONFIG_HW_RANDOM_AMD=y
CONFIG_HW_RANDOM_VIA=y
CONFIG_HW_RANDOM_VIRTIO=y
Post by t***@gmail.com
I see that experimental-android-4.17 has been tagged at
https://android.googlesource.com/kernel/common/+/experimental-android-4.17,
so my next step will be to roll patches from the maurossi branch into
experimental-android-4.17 and try again.
Post by Mauro Rossi
Hi,
thanks a lot
Do you see some kind of freeze happening with 4.18rc expecially with
Intel manufactured chipsets?
My builds with kernel 4.17 and 4.18rc are still not reaching the console
they freeze when autoloading some kernel module
Mauro
Post by youling 257
you can test 7.1 rc2 and r1 use 7_y/z houdini running 王者荣耀
4.9、4.10、4.11、4.12、4.13、4.14、4.15、4.16、4.17、4.18all need Revert
"x86/signal/64: Re-add support for SS in the 64-bit signal context"I say
this patchandroid-x86: fix 64bit android7.1 games crashFrom: lixin <
openthos kernel 4.9、4.14、4.15、4.16、4.17、4.18 has a Revert
"x86/signal/64: Re-add support for SS in the 64-bit signal context" patch
by cwhuangfix 5_y/z houdini with high kernel versionthis patch added to
Androidx86 7.1 r2 kernel 4.9.
圚 2018幎7月7日星期六 UTC+8䞋午8:32:23yuki haya写道
Post by yuki haya
Hello.
Does the behavior of kernel 4.16 or later Native Bridge behave differently?
There is a problem that the application does not start up.
logcat has an error on libEGL.so.
Thank you.
--
You received this message because you are subscribed to the Google Groups "Android-x86" group.
To unsubscribe from this group and stop receiving emails from it, send an email to android-x86+***@googlegroups.com.
To post to this group, send email to android-***@googlegroups.com.
Visit this group at https://groups.google.com/group/android-x86.
For more options, visit https://groups.google.com/d/optout.
Mauro Rossi
2018-07-24 20:29:24 UTC
Permalink
Hi, kind request for help.

Does some one know, after having enabled the CONFIG_HW_RANDOM* stuff,
what is still causing the problem with booting 64 bit kernels from 4.17 to
4.18rc6?

It would be nice to solve this problem once and forever,
to be able to boot and solve the other problems too. :-)

Mauro
Post by Mauro Rossi
Hi,
Post by t***@gmail.com
I am also attempting to a build with kernel 4.17 and 4.18 and am failing
to boot completely. Always, the last message I see printed to the console
random: crng init done
It takes between 30 seconds and 5 minutes for this message to appear.
That time can be cut down if I randomly press keys on a keyboard, thereby
increasing entropy. I've attempted to boot two different machines, a
SandyBridge desktop and a Broadwell tablet, and received the same result.
In order to avoid the wait (or freeze) happening because of random,
enabling CONFIG_HW_RANDOM as builtin helps
In some other project kernel the CONFIG_HW_RANDOM* are all enabled and in
principle they should do no harm.
Now, the only remaining problem is that for me it works only for x86 32bit
kernel,
but at least I can boot with one of the two targets.
Mauro
CONFIG_HW_RANDOM=y
CONFIG_HW_RANDOM_TIMERIOMEM=y
CONFIG_HW_RANDOM_INTEL=y
CONFIG_HW_RANDOM_AMD=y
CONFIG_HW_RANDOM_VIA=y
CONFIG_HW_RANDOM_VIRTIO=y
Post by t***@gmail.com
I see that experimental-android-4.17 has been tagged at
https://android.googlesource.com/kernel/common/+/experimental-android-4.17,
so my next step will be to roll patches from the maurossi branch into
experimental-android-4.17 and try again.
Post by Mauro Rossi
Hi,
thanks a lot
Do you see some kind of freeze happening with 4.18rc expecially with
Intel manufactured chipsets?
My builds with kernel 4.17 and 4.18rc are still not reaching the console
they freeze when autoloading some kernel module
Mauro
Post by youling 257
you can test 7.1 rc2 and r1 use 7_y/z houdini running 王者荣耀
4.9、4.10、4.11、4.12、4.13、4.14、4.15、4.16、4.17、4.18all need Revert
"x86/signal/64: Re-add support for SS in the 64-bit signal context"I say
this patchandroid-x86: fix 64bit android7.1 games crashFrom: lixin <
openthos kernel 4.9、4.14、4.15、4.16、4.17、4.18 has a Revert
"x86/signal/64: Re-add support for SS in the 64-bit signal context" patch
by cwhuangfix 5_y/z houdini with high kernel versionthis patch added to
Androidx86 7.1 r2 kernel 4.9.
圚 2018幎7月7日星期六 UTC+8䞋午8:32:23yuki haya写道
Post by yuki haya
Hello.
Does the behavior of kernel 4.16 or later Native Bridge behave differently?
There is a problem that the application does not start up.
logcat has an error on libEGL.so.
Thank you.
--
You received this message because you are subscribed to the Google Groups "Android-x86" group.
To unsubscribe from this group and stop receiving emails from it, send an email to android-x86+***@googlegroups.com.
To post to this group, send email to android-***@googlegroups.com.
Visit this group at https://groups.google.com/group/android-x86.
For more options, visit https://groups.google.com/d/optout.
spin877
2018-07-28 01:43:49 UTC
Permalink
oreo-x86_64 kernel
https://github.com/youling257/openthos-kernel/commits/openthos-4.18
<https://www.google.com/url?q=https%3A%2F%2Fgithub.com%2Fyouling257%2Fopenthos-kernel%2Fcommits%2Fopenthos-4.18%2Farch%2Fx86%2Fkernel%2Fsignal.c&sa=D&sntz=1&usg=AFQjCNH96CgUivV4lQyaoyY0JuuIqOUA-A> rc-3
BayTrail efi32


I have to add these patches to start on my tablet.



diff --git a/arch/x86/configs/android-x86_64_defconfig
b/arch/x86/configs/android-x86_64_defconfig
index d60742c..fc6cfc5 100644
--- a/arch/x86/configs/android-x86_64_defconfig
+++ b/arch/x86/configs/android-x86_64_defconfig
+# CONFIG_CRYPTO_AES_NI_INTEL is not set
diff --git a/drivers/gpu/drm/ttm/ttm_bo_vm.c
b/drivers/gpu/drm/ttm/ttm_bo_vm.c
index c7ece76..0df1388 100644
--- a/drivers/gpu/drm/ttm/ttm_bo_vm.c
+++ b/drivers/gpu/drm/ttm/ttm_bo_vm.c
@@ -301,7 +301,7 @@ static void ttm_bo_vm_open(struct vm_area_struct *vma)
struct ttm_buffer_object *bo =
(struct ttm_buffer_object *)vma->vm_private_data;

- WARN_ON(bo->bdev->dev_mapping != vma->vm_file->f_mapping);
+// WARN_ON(bo->bdev->dev_mapping != vma->vm_file->f_mapping);

(void)ttm_bo_reference(bo);
}
diff --git a/drivers/i2c/busses/i2c-designware-baytrail.c
b/drivers/i2c/busses/i2c-designware-baytrail.c
index dbda8c9..2d3c4f2 100644
--- a/drivers/i2c/busses/i2c-designware-baytrail.c
+++ b/drivers/i2c/busses/i2c-designware-baytrail.c
@@ -128,7 +128,7 @@ static int baytrail_i2c_acquire(struct dw_i2c_dev *dev)
else
dev_err(dev->dev, "PUNIT SEM: %d\n", sem);

- WARN_ON(1);
+// WARN_ON(1);

return -ETIMEDOUT;
}
diff --git a/fs/buffer.c b/fs/buffer.c
index cabc045..3fb0528 100644
--- a/fs/buffer.c
+++ b/fs/buffer.c
@@ -1133,7 +1133,7 @@ void __brelse(struct buffer_head * buf)
put_bh(buf);
return;
}
- WARN(1, KERN_ERR "VFS: brelse: Trying to free free buffer\n");
+// WARN(1, KERN_ERR "VFS: brelse: Trying to free free buffer\n");
}
EXPORT_SYMBOL(__brelse);


with quemu, also, with these patches, it does not work
--
You received this message because you are subscribed to the Google Groups "Android-x86" group.
To unsubscribe from this group and stop receiving emails from it, send an email to android-x86+***@googlegroups.com.
To post to this group, send email to android-***@googlegroups.com.
Visit this group at https://groups.google.com/group/android-x86.
For more options, visit https://groups.google.com/d/optout.
youling 257
2018-07-12 16:04:25 UTC
Permalink
my problem is this[tip:efi/urgent] efi/x86: Fix mixed mode reboot loop by
removing ...efi/x86: remove pointless call to PciIo->AttributesLKML: Ard
Biesheuvel: Re: [GIT PULL 0/1] EFI mixed mode fix for v4.18

https://patchwork.kernel.org/patch/10519375/
https://lkml.org/lkml/2018/7/11/190 http://patches.linaro.org/patches/307/

mixed EFI mode Bay Trail tablet
would not boot at all any more, but enter a reboot loop without
any logs printed by the kernel.

圚 2018幎7月2日星期䞀 UTC+8䞋午4:49:21youling 257写道
Post by youling 257
https://github.com/torvalds/linux/commit/52e1cf2d19c2e62e6a81b8de3f7320d033917dd5
it fixed my Bay trail problembay trail 32bit uefirunning 64bit kernel.
--
You received this message because you are subscribed to the Google Groups "Android-x86" group.
To unsubscribe from this group and stop receiving emails from it, send an email to android-x86+***@googlegroups.com.
To post to this group, send email to android-***@googlegroups.com.
Visit this group at https://groups.google.com/group/android-x86.
For more options, visit https://groups.google.com/d/optout.
spin877
2018-07-12 17:37:46 UTC
Permalink
I tried a compile android-x86 7.1.2 with kernel openthos-4.18 I had to
disable the CONFIG_CRYPTO_AES_NI_INTEL module on my Baytrail efi32 tablet
the kernel was blocked immediately
--
You received this message because you are subscribed to the Google Groups "Android-x86" group.
To unsubscribe from this group and stop receiving emails from it, send an email to android-x86+***@googlegroups.com.
To post to this group, send email to android-***@googlegroups.com.
Visit this group at https://groups.google.com/group/android-x86.
For more options, visit https://groups.google.com/d/optout.
spin877
2018-07-12 17:50:30 UTC
Permalink
I tried a compile android-x86 7.1.2 with kernel openthos-4.18

He gave me an error:
RIP: 0010:aesni_gcm_init+0x89/0x30f


I had to disable the CONFIG_CRYPTO_AES_NI_INTEL module
on my Baytrail efi32 tablet the kernel was blocked immediately
--
You received this message because you are subscribed to the Google Groups "Android-x86" group.
To unsubscribe from this group and stop receiving emails from it, send an email to android-x86+***@googlegroups.com.
To post to this group, send email to android-***@googlegroups.com.
Visit this group at https://groups.google.com/group/android-x86.
For more options, visit https://groups.google.com/d/optout.
youling 257
2018-07-28 02:03:41 UTC
Permalink
it's wrongno any help at all.

圚 2018幎7月13日星期五 UTC+8䞊午12:04:26youling 257写道
Post by youling 257
my problem is this[tip:efi/urgent] efi/x86: Fix mixed mode reboot loop by
removing ...efi/x86: remove pointless call to PciIo->AttributesLKML: Ard
Biesheuvel: Re: [GIT PULL 0/1] EFI mixed mode fix for v4.18
https://patchwork.kernel.org/patch/10519375/
https://lkml.org/lkml/2018/7/11/190 http://patches.linaro.org/patches/307/
mixed EFI mode Bay Trail tablet
would not boot at all any more, but enter a reboot loop without
any logs printed by the kernel.
圚 2018幎7月2日星期䞀 UTC+8䞋午4:49:21youling 257写道
Post by youling 257
https://github.com/torvalds/linux/commit/52e1cf2d19c2e62e6a81b8de3f7320d033917dd5
it fixed my Bay trail problembay trail 32bit uefirunning 64bit kernel.
--
You received this message because you are subscribed to the Google Groups "Android-x86" group.
To unsubscribe from this group and stop receiving emails from it, send an email to android-x86+***@googlegroups.com.
To post to this group, send email to android-***@googlegroups.com.
Visit this group at https://groups.google.com/group/android-x86.
For more options, visit https://groups.google.com/d/optout.
youling 257
2018-07-28 02:04:47 UTC
Permalink
it's wrongno any help at alll for me.

圚 2018幎7月2日星期䞀 UTC+8䞋午4:49:21youling 257写道
Post by youling 257
https://github.com/torvalds/linux/commit/52e1cf2d19c2e62e6a81b8de3f7320d033917dd5
it fixed my Bay trail problembay trail 32bit uefirunning 64bit kernel.
--
You received this message because you are subscribed to the Google Groups "Android-x86" group.
To unsubscribe from this group and stop receiving emails from it, send an email to android-x86+***@googlegroups.com.
To post to this group, send email to android-***@googlegroups.com.
Visit this group at https://groups.google.com/group/android-x86.
For more options, visit https://groups.google.com/d/optout.
youling 257
2018-07-16 18:39:51 UTC
Permalink
Hope to find the problem right direction.

/* Copy trampoline code in place */
memcpy(trampoline_32bit + TRAMPOLINE_32BIT_CODE_OFFSET / sizeof(unsigned
long),
&trampoline_32bit_src, TRAMPOLINE_32BIT_CODE_SIZE);

https://lkml.org/lkml/2018/7/3/574
https://lkml.org/lkml/2018/7/3/1028
https://patchwork.kernel.org/patch/10507261/
--
You received this message because you are subscribed to the Google Groups "Android-x86" group.
To unsubscribe from this group and stop receiving emails from it, send an email to android-x86+***@googlegroups.com.
To post to this group, send email to android-***@googlegroups.com.
Visit this group at https://groups.google.com/group/android-x86.
For more options, visit https://groups.google.com/d/optout.
youling 257
2018-07-28 02:13:12 UTC
Permalink
I use gcc 8 build Linux kerneli needn't Android source and Android
toolchaini use time make targz-pkg -i command . Linux version
4.18.0-rc6-android-x86_64+ (***@localhost) (gcc version 8.1.0 (Ubuntu
8.1.0-12ubuntu1)) #2 SMP PREEMPT Fri Jul 27 22:24:34 CST 2018

a lot of bisect to find problem reasonhttps://www.spinics.net/lists/linux-efi/msg14445.html
Temporary solutionRevert "x86/boot/compressed/64: Set up trampoline
memory"https://github.com/youling257/android-4.9/commits/experimental/android-mainline-4.18-tracking

https://lkml.org/lkml/2018/7/27/648
https://lkml.org/lkml/diff/2018/7/27/648/1
this patch final solved my problem.

圚 2018幎7月17日星期二 UTC+8䞊午2:39:51youling 257写道
Post by youling 257
Hope to find the problem right direction.
/* Copy trampoline code in place */
memcpy(trampoline_32bit + TRAMPOLINE_32BIT_CODE_OFFSET / sizeof(unsigned
long),
&trampoline_32bit_src, TRAMPOLINE_32BIT_CODE_SIZE);
https://lkml.org/lkml/2018/7/3/574
https://lkml.org/lkml/2018/7/3/1028
https://patchwork.kernel.org/patch/10507261/
--
You received this message because you are subscribed to the Google Groups "Android-x86" group.
To unsubscribe from this group and stop receiving emails from it, send an email to android-x86+***@googlegroups.com.
To post to this group, send email to android-***@googlegroups.com.
Visit this group at https://groups.google.com/group/android-x86.
For more options, visit https://groups.google.com/d/optout.
Mauro Rossi
2018-07-28 17:05:19 UTC
Permalink
Hi youling257,
Post by youling 257
I use gcc 8 build Linux kerneli needn't Android source and Android
toolchaini use time make targz-pkg -i command . Linux version
8.1.0-12ubuntu1)) #2 SMP PREEMPT Fri Jul 27 22:24:34 CST 2018
a lot of bisect to find problem reason
https://www.spinics.net/lists/linux-efi/msg14445.html Temporary
solutionRevert "x86/boot/compressed/64: Set up trampoline memory"
https://github.com/youling257/android-4.9/commits/experimental/android-mainline-4.18-tracking
<https://www.google.com/url?q=https%3A%2F%2Fgithub.com%2Fyouling257%2Fandroid-4.9%2Fcommits%2Fexperimental%2Fandroid-mainline-4.18-tracking&sa=D&sntz=1&usg=AFQjCNGF1IZYZvCHIP4lLTRVQXWLFnsNGw>
https://lkml.org/lkml/2018/7/27/648
https://lkml.org/lkml/diff/2018/7/27/648/1
this patch final solved my problem.
Do you meant that that patch solves you problem with u32k64 android-x86
builds

or that also solves default x86_64 iso kernel freeze/panic?

Thanks
Mauro
Post by youling 257
圚 2018幎7月17日星期二 UTC+8䞊午2:39:51youling 257写道
Post by youling 257
Hope to find the problem right direction.
/* Copy trampoline code in place */
memcpy(trampoline_32bit + TRAMPOLINE_32BIT_CODE_OFFSET / sizeof(unsigned
long),
&trampoline_32bit_src, TRAMPOLINE_32BIT_CODE_SIZE);
https://lkml.org/lkml/2018/7/3/574
https://lkml.org/lkml/2018/7/3/1028
https://patchwork.kernel.org/patch/10507261/
--
You received this message because you are subscribed to the Google Groups "Android-x86" group.
To unsubscribe from this group and stop receiving emails from it, send an email to android-x86+***@googlegroups.com.
To post to this group, send email to android-***@googlegroups.com.
Visit this group at https://groups.google.com/group/android-x86.
For more options, visit https://groups.google.com/d/optout.
youling 257
2018-07-28 19:11:07 UTC
Permalink
as i knowmy problem won't happen on gcc 4.6you no this problem.
https://lkml.org/lkml/2018/4/16/1097 ***@ANDROIDDEV) (gcc version 4.6
20120106***@android-x86) (gcc version 4.6 20120106

from beginwe are talk different problemmy problem made me very
angryunbearableuntil i have to do git bisect.
why you not do git bisect to find the bad one commit ?

圚 2018幎7月29日星期日 UTC+8䞊午1:05:19Mauro Rossi写道
Post by Mauro Rossi
Hi youling257,
Post by youling 257
I use gcc 8 build Linux kerneli needn't Android source and Android
toolchaini use time make targz-pkg -i command . Linux version
8.1.0-12ubuntu1)) #2 SMP PREEMPT Fri Jul 27 22:24:34 CST 2018
a lot of bisect to find problem reason
https://www.spinics.net/lists/linux-efi/msg14445.html Temporary
solutionRevert "x86/boot/compressed/64: Set up trampoline memory"
https://github.com/youling257/android-4.9/commits/experimental/android-mainline-4.18-tracking
<https://www.google.com/url?q=https%3A%2F%2Fgithub.com%2Fyouling257%2Fandroid-4.9%2Fcommits%2Fexperimental%2Fandroid-mainline-4.18-tracking&sa=D&sntz=1&usg=AFQjCNGF1IZYZvCHIP4lLTRVQXWLFnsNGw>
https://lkml.org/lkml/2018/7/27/648
https://lkml.org/lkml/diff/2018/7/27/648/1
this patch final solved my problem.
Do you meant that that patch solves you problem with u32k64 android-x86
builds
or that also solves default x86_64 iso kernel freeze/panic?
Thanks
Mauro
Post by youling 257
圚 2018幎7月17日星期二 UTC+8䞊午2:39:51youling 257写道
Post by youling 257
Hope to find the problem right direction.
/* Copy trampoline code in place */
memcpy(trampoline_32bit + TRAMPOLINE_32BIT_CODE_OFFSET /
sizeof(unsigned long),
&trampoline_32bit_src, TRAMPOLINE_32BIT_CODE_SIZE);
https://lkml.org/lkml/2018/7/3/574
https://lkml.org/lkml/2018/7/3/1028
https://patchwork.kernel.org/patch/10507261/
--
You received this message because you are subscribed to the Google Groups "Android-x86" group.
To unsubscribe from this group and stop receiving emails from it, send an email to android-x86+***@googlegroups.com.
To post to this group, send email to android-***@googlegroups.com.
Visit this group at https://groups.google.com/group/android-x86.
For more options, visit https://groups.google.com/d/optout.
Mauro Rossi
2018-07-28 20:01:00 UTC
Permalink
Hi,
Post by youling 257
as i knowmy problem won't happen on gcc 4.6you no this problem.
from beginwe are talk different problemmy problem made me very
angryunbearableuntil i have to do git bisect.
why you not do git bisect to find the bad one commit ?
圚 2018幎7月29日星期日 UTC+8䞊午1:05:19Mauro Rossi写道
Post by Mauro Rossi
Hi youling257,
Post by youling 257
I use gcc 8 build Linux kerneli needn't Android source and Android
toolchaini use time make targz-pkg -i command . Linux version
8.1.0-12ubuntu1)) #2 SMP PREEMPT Fri Jul 27 22:24:34 CST 2018
a lot of bisect to find problem reason
https://www.spinics.net/lists/linux-efi/msg14445.html Temporary
solutionRevert "x86/boot/compressed/64: Set up trampoline memory"
https://github.com/youling257/android-4.9/commits/experimental/android-mainline-4.18-tracking
<https://www.google.com/url?q=https%3A%2F%2Fgithub.com%2Fyouling257%2Fandroid-4.9%2Fcommits%2Fexperimental%2Fandroid-mainline-4.18-tracking&sa=D&sntz=1&usg=AFQjCNGF1IZYZvCHIP4lLTRVQXWLFnsNGw>
https://lkml.org/lkml/2018/7/27/648
https://lkml.org/lkml/diff/2018/7/27/648/1
this patch final solved my problem.
Do you meant that that patch solves you problem with u32k64 android-x86
builds
or that also solves default x86_64 iso kernel freeze/panic?
Thanks
Mauro
Post by youling 257
圚 2018幎7月17日星期二 UTC+8䞊午2:39:51youling 257写道
Post by youling 257
Hope to find the problem right direction.
/* Copy trampoline code in place */
memcpy(trampoline_32bit + TRAMPOLINE_32BIT_CODE_OFFSET /
sizeof(unsigned long),
&trampoline_32bit_src, TRAMPOLINE_32BIT_CODE_SIZE);
https://lkml.org/lkml/2018/7/3/574
https://lkml.org/lkml/2018/7/3/1028
https://patchwork.kernel.org/patch/10507261/
Because with my manual setup it could take ages, I don't know how to
automate,
are there documented ways?

Mauro
--
You received this message because you are subscribed to the Google Groups "Android-x86" group.
To unsubscribe from this group and stop receiving emails from it, send an email to android-x86+***@googlegroups.com.
To post to this group, send email to android-***@googlegroups.com.
Visit this group at https://groups.google.com/group/android-x86.
For more options, visit https://groups.google.com/d/optout.
Mauro Rossi
2018-08-03 20:55:05 UTC
Permalink
Hi,
I have found what was causing the problem with 64bit kernel freezing in
both virtuamachines and physical

[ 0.984004] RIP: 0010:aesni_gcm_init+0x89/0x30f
[ 0.984832] Code: 0f 6f ca 66 0f 73 fa 08 66 0f 73 d9 08 66 0f eb da 66
0f 70 d1 24 66 0f 76 15 33 11 03 01 66 0f db 15 1b 11 03 01 66 0f ef da
<66> 0f 7f 5e 60 66 0f 6f eb 66 0f 70 cb 4e 66 0f ef cb 66 0f 7f 8e
[ 0.987813] RSP: 0000:ffff90924132f7d8 EFLAGS: 00010246
[ 0.988818] RAX: ffff90924132fb98 RBX: 0000000000000010 RCX:
ffff8d3ddd93fc50
[ 0.989979] RDX: ffff90924132fb98 RSI: ffff90924132f8c8 RDI:
ffff8d3ddd93fc60
[ 0.991171] RBP: 0000000000000000 R08: ffff8d3dde3e4000 R09:
0000000000000008
[ 0.992349] R10: ffff8d3e5e9ad000 R11: 0000000000000000 R12:
ffff8d3ddd93fc50
[ 0.993424] R13: 0000000000000000 R14: 0000000000000000 R15:
0000000000000008
[ 0.994491] FS: 0000000000000000(0000) GS:ffff8d3de3d80000(0000)
knlGS:0000000000000000
[ 0.996428] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[ 0.997315] CR2: 0000000000000000 CR3: 000000003000a001 CR4:
00000000000606e0
[ 0.998395] note: cryptomgr_test[939] exited with preempt_count 2

then I found this:

https://www.spinics.net/lists/linux-crypto/msg23319.html

then I changed the kernel config like this:

-# CONFIG_CRYPTO_MANAGER_DISABLE_TESTS is not set
+CONFIG_CRYPTO_MANAGER_DISABLE_TESTS=y

and now I can proceed in boot with 64bit kernel

Mauro
Post by Mauro Rossi
Hi,
Post by youling 257
as i knowmy problem won't happen on gcc 4.6you no this problem.
from beginwe are talk different problemmy problem made me very
angryunbearableuntil i have to do git bisect.
why you not do git bisect to find the bad one commit ?
圚 2018幎7月29日星期日 UTC+8䞊午1:05:19Mauro Rossi写道
Post by Mauro Rossi
Hi youling257,
Post by youling 257
I use gcc 8 build Linux kerneli needn't Android source and Android
toolchaini use time make targz-pkg -i command . Linux version
8.1.0-12ubuntu1)) #2 SMP PREEMPT Fri Jul 27 22:24:34 CST 2018
a lot of bisect to find problem reason
https://www.spinics.net/lists/linux-efi/msg14445.html Temporary
solutionRevert "x86/boot/compressed/64: Set up trampoline memory"
https://github.com/youling257/android-4.9/commits/experimental/android-mainline-4.18-tracking
<https://www.google.com/url?q=https%3A%2F%2Fgithub.com%2Fyouling257%2Fandroid-4.9%2Fcommits%2Fexperimental%2Fandroid-mainline-4.18-tracking&sa=D&sntz=1&usg=AFQjCNGF1IZYZvCHIP4lLTRVQXWLFnsNGw>
https://lkml.org/lkml/2018/7/27/648
https://lkml.org/lkml/diff/2018/7/27/648/1
this patch final solved my problem.
Do you meant that that patch solves you problem with u32k64 android-x86
builds
or that also solves default x86_64 iso kernel freeze/panic?
Thanks
Mauro
Post by youling 257
圚 2018幎7月17日星期二 UTC+8䞊午2:39:51youling 257写道
Post by youling 257
Hope to find the problem right direction.
/* Copy trampoline code in place */
memcpy(trampoline_32bit + TRAMPOLINE_32BIT_CODE_OFFSET /
sizeof(unsigned long),
&trampoline_32bit_src, TRAMPOLINE_32BIT_CODE_SIZE);
https://lkml.org/lkml/2018/7/3/574
https://lkml.org/lkml/2018/7/3/1028
https://patchwork.kernel.org/patch/10507261/
Because with my manual setup it could take ages, I don't know how to
automate,
are there documented ways?
Mauro
--
You received this message because you are subscribed to the Google Groups "Android-x86" group.
To unsubscribe from this group and stop receiving emails from it, send an email to android-x86+***@googlegroups.com.
To post to this group, send email to android-***@googlegroups.com.
Visit this group at https://groups.google.com/group/android-x86.
For more options, visit https://groups.google.com/d/optout.
Mauro Rossi
2018-08-04 17:43:19 UTC
Permalink
Post by Mauro Rossi
Hi,
I have found what was causing the problem with 64bit kernel freezing in
both virtuamachines and physical
[ 0.984004] RIP: 0010:aesni_gcm_init+0x89/0x30f
[ 0.984832] Code: 0f 6f ca 66 0f 73 fa 08 66 0f 73 d9 08 66 0f eb da 66
0f 70 d1 24 66 0f 76 15 33 11 03 01 66 0f db 15 1b 11 03 01 66 0f ef da
<66> 0f 7f 5e 60 66 0f 6f eb 66 0f 70 cb 4e 66 0f ef cb 66 0f 7f 8e
[ 0.987813] RSP: 0000:ffff90924132f7d8 EFLAGS: 00010246
ffff8d3ddd93fc50
ffff8d3ddd93fc60
0000000000000008
ffff8d3ddd93fc50
0000000000000008
[ 0.994491] FS: 0000000000000000(0000) GS:ffff8d3de3d80000(0000)
knlGS:0000000000000000
[ 0.996428] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
00000000000606e0
[ 0.998395] note: cryptomgr_test[939] exited with preempt_count 2
https://www.spinics.net/lists/linux-crypto/msg23319.html
-# CONFIG_CRYPTO_MANAGER_DISABLE_TESTS is not set
+CONFIG_CRYPTO_MANAGER_DISABLE_TESTS=y
and now I can proceed in boot with 64bit kernel
Mauro
Post by Mauro Rossi
Hi,
Post by youling 257
as i knowmy problem won't happen on gcc 4.6you no this problem.
from beginwe are talk different problemmy problem made me very
angryunbearableuntil i have to do git bisect.
why you not do git bisect to find the bad one commit ?
Hi Youling,
I've bisected the cryptomgr_test crash and panic with 64bit kernel to this
first bad commit:

1476db2d129d5e4fc59e93a7abd22edcb26b52f5
"crypto: aesni - Move HashKey computation from stack to gcm_context"

and informed the developer about the crash
Mauro
Post by Mauro Rossi
Post by Mauro Rossi
Post by youling 257
圚 2018幎7月29日星期日 UTC+8䞊午1:05:19Mauro Rossi写道
Post by Mauro Rossi
Hi youling257,
Post by youling 257
I use gcc 8 build Linux kerneli needn't Android source and Android
toolchaini use time make targz-pkg -i command . Linux version
8.1.0-12ubuntu1)) #2 SMP PREEMPT Fri Jul 27 22:24:34 CST 2018
a lot of bisect to find problem reason
https://www.spinics.net/lists/linux-efi/msg14445.html Temporary
solutionRevert "x86/boot/compressed/64: Set up trampoline memory"
https://github.com/youling257/android-4.9/commits/experimental/android-mainline-4.18-tracking
<https://www.google.com/url?q=https%3A%2F%2Fgithub.com%2Fyouling257%2Fandroid-4.9%2Fcommits%2Fexperimental%2Fandroid-mainline-4.18-tracking&sa=D&sntz=1&usg=AFQjCNGF1IZYZvCHIP4lLTRVQXWLFnsNGw>
https://lkml.org/lkml/2018/7/27/648
https://lkml.org/lkml/diff/2018/7/27/648/1
this patch final solved my problem.
Do you meant that that patch solves you problem with u32k64 android-x86
builds
or that also solves default x86_64 iso kernel freeze/panic?
Thanks
Mauro
Post by youling 257
圚 2018幎7月17日星期二 UTC+8䞊午2:39:51youling 257写道
Post by youling 257
Hope to find the problem right direction.
/* Copy trampoline code in place */
memcpy(trampoline_32bit + TRAMPOLINE_32BIT_CODE_OFFSET /
sizeof(unsigned long),
&trampoline_32bit_src, TRAMPOLINE_32BIT_CODE_SIZE);
https://lkml.org/lkml/2018/7/3/574
https://lkml.org/lkml/2018/7/3/1028
https://patchwork.kernel.org/patch/10507261/
Because with my manual setup it could take ages, I don't know how to
automate,
are there documented ways?
Mauro
--
You received this message because you are subscribed to the Google Groups "Android-x86" group.
To unsubscribe from this group and stop receiving emails from it, send an email to android-x86+***@googlegroups.com.
To post to this group, send email to android-***@googlegroups.com.
Visit this group at https://groups.google.com/group/android-x86.
For more options, visit https://groups.google.com/d/optout.
youling 257
2018-07-28 02:01:51 UTC
Permalink
git init
git remote add openthos
https://mirrors.tuna.tsinghua.edu.cn/git/openthos-src/kernel/common
git fetch openthos
git checkout openthos-4.18
git checkout openthos-4.17










--
You received this message because you are subscribed to the Google Groups "Android-x86" group.
To unsubscribe from this group and stop receiving emails from it, send an email to android-x86+***@googlegroups.com.
To post to this group, send email to android-***@googlegroups.com.
Visit this group at https://groups.google.com/group/android-x86.
For more options, visit https://groups.google.com/d/optout.
Loading...