Description of problem: dkms-anbox need updating for kernel 6.6 Also probably good for waydroid Bug 32467 - On mga9, we cannot start waydroid due to various errors Also see Bug 29611
Blocks: (none) => 32786
Blocks: (none) => 32467
Priority: Normal => High
CC: (none) => eatdirt, ngompa13
Created attachment 14322 [details] Changes from current spec in mageia 9 @Chris Denice, I test the recent commit and works for kernel 6.6 server and linus and at less with current kernel 6.5 desktop With kernel 6.6 desktop in my hardware I get kernel panic if I add the psi=1 option
(In reply to Morgan Leijström from comment #0) > Description of problem: > dkms-anbox need updating for kernel 6.6 > > Also probably good for waydroid > Bug 32467 - On mga9, we cannot start waydroid due to various errors > > Also see Bug 29611 Bug 29611 was solved with the updates of Bug 32496
Whiteboard: (none) => MGA9TOOVersion: 9 => Cauldron
(In reply to katnatek from comment #1) > Created attachment 14322 [details] > Changes from current spec in mageia 9 > > @Chris Denice, I test the recent commit and works for kernel 6.6 server and > linus and at less with current kernel 6.5 desktop > > With kernel 6.6 desktop in my hardware I get kernel panic if I add the psi=1 > option Not need to add psi=1, in the first reboot after install dkms-anbox the modules are build and if reboot again I get the panic
I'll have a look if upstream provides new patches! But if not, it is a lost fight. May be we should drop the whole anbox packages and waydroid. If we're longer to push dkms-anbox updates than we update kernels that break them, there is no point of working on that :-/ Maybe we should also think about our kernel update policy...
(In reply to Chris Denice from comment #4) > I'll have a look if upstream provides new patches! > > But if not, it is a lost fight. May be we should drop the whole anbox > packages and waydroid. If we're longer to push dkms-anbox updates than we > update kernels that break them, there is no point of working on that :-/ > > Maybe we should also think about our kernel update policy... We follow lts versions 6.5 is EOL is not sure keep it I hope you find some fix, but if not we most recommend use just kernel server or linus flavors
Which kernels need dkms-anbox and which are not ? It seems to me that's already built-in for some time... $ zgrep ANDR /boot/config-6.6.14-desktop-2.mga10 CONFIG_X86_ANDROID_TABLETS=m CONFIG_ANDROID_BINDER_IPC=y CONFIG_ANDROID_BINDERFS=y CONFIG_ANDROID_BINDER_DEVICES="binder,hwbinder,vndbinder" # CONFIG_ANDROID_BINDER_IPC_SELFTEST is not set
CC: (none) => geex+mageia
(In reply to Guillaume Bedot from comment #6) > Which kernels need dkms-anbox and which are not ? > It seems to me that's already built-in for some time... > > $ zgrep ANDR /boot/config-6.6.14-desktop-2.mga10 > CONFIG_X86_ANDROID_TABLETS=m > CONFIG_ANDROID_BINDER_IPC=y > CONFIG_ANDROID_BINDERFS=y > CONFIG_ANDROID_BINDER_DEVICES="binder,hwbinder,vndbinder" > # CONFIG_ANDROID_BINDER_IPC_SELFTEST is not set I got kernel panics with kernel 6.6 after install dkms-anbox and reboot twice, build the recent commit mitigate the situation, but works just with server and linus flavors, if you want to make the test in your system be sure to have a kernel 6.5 as alternative
All right, dkms-anbox-0.0.3-1.3.mga9.src.rpm will soon be available on updates_testing!
Package in 9/Core/Updates_testing: ======================= dkms-anbox-0.0.3-1.3.mga9.noarch.rpm From SRPM: dkms-anbox-0.0.3-1.3.mga9.src.rpm
Assignee: bgmilne => qa-bugs
(In reply to Chris Denice from comment #8) > All right, > > dkms-anbox-0.0.3-1.3.mga9.src.rpm > > will soon be available on updates_testing! Maybe due dracut and microcode testing packages but now just kernel server don't panic :( This need other test if is just my system then we can add a Errata just in case other users have similar hardware Need to test with kernel 6.6 desktop and linus https://bugs.mageia.org/show_bug.cgi?id=32786#c75, and have server as fallback option Install current version of dkms-anbox Reboot Select Advanced options Select one of the 6.6 kernels Wait until dm screen or desktop load if you have autologin Reboot If the panic is produced Press Alt + Print Screen + R E I S U B Select Advanced options Select other kernel Update to testing version and repeat the test If the panic is produced after Press Alt + Print Screen + R E I S U B Select Advanced options Select other kernel Uninstall dkms-anbox Please confirm if you get a kernel panic or not I will test on my i586 hardware
Tested on real hardware mageia 9 i586 Tested -kernel-desktop-6.6.14-2.mga9 -kernel-desktop586-6.6.14-2.mga9 -kernel-server-6.6.14-2.mga9 -kernel-linus-6.6.14-1.mga9 Current and testing versions of dkms-anbox, not issues , so my current x86_64 system have some issues with the combination of kernels 6.6 != server and dkms-anbox
advisory was uploaded by tarazed
CC: (none) => marja11Keywords: (none) => advisory
Whiteboard: MGA9TOO => (none)Version: Cauldron => 9
CC: (none) => andrewsfarmBlocks: 32786 => (none)
Sending this back until the Waydroid issues can be resolved. As it is, it just isn't ready for QA yet.
Assignee: qa-bugs => eatdirt
https://wiki.mageia.org/en/Mageia_9_Errata#Various_software
Whiteboard: (none) => IN_ERRATA9
Is dkms-anbox really needed? From https://ml.mageia.org/l/arc/qa-discuss/2024-02/msg00053.html : > Why aren't we just turning on binderfs in the kernel? We don't need > dkms-anbox if we have the features turned on in the kernel itself. CONFIG_ANDROID_BINDERFS=y is enabled in kernel-desktop (not in kernel-server, of course), so according to that it should work already without dkms-anbox.
As far as I see 1) binderfs is not anbox, so you're not going to replace anbox by binderfs. 2) anbox was supposed to support binderfs: https://github.com/anbox/anbox/pull/1309 3) Good spot that kernel server are not built with binderfs! That may explain the kernel panic observed with all but kernel-servers, possibly that support is actually broken. 4) If there is a way to make waydroid working directly with binderfs, that would allow us to drop dkms-anbox, but I did not find any. Finally, I cannot tutor QA testers at their home to make waydroid working, and parts of waydroid are out-of-mageia and cannot be fixed within mageia. But I'll have another full test to see if this is still working for me.
Waydroid already does in Fedora, that's why Waydroid is packaged there.
Ah good, I'll have a look to their packaging then!!
Removing the advisory keyword, as it will likely be needed to change or drop the uploaded one.
Keywords: advisory => (none)
Two reports of similar issues https://forums.mageia.org/en/viewtopic.php?f=7&t=15248#p89251 https://www.mageialinux-online.org/forum/topic-31321-kernel-6-6-14.php
I am on it. All that mess comes from kernel-6.6 because it actually has binderfs built in, indeed, but not our kernels <=6.5 So, waydroid should be easier to run on >= 6.6, but people having kernel <=6.5 will still need dkms-anbox. I giving a last push to everything , remove the Requires:dkms-anbox in waydroid, but we should let that package in mageia 9 for people running kernels <=6.5.
First, let's close this bug as dkms-anbox is not needed anymore for waydroid.
Resolution: (none) => WONTFIXStatus: NEW => RESOLVED
See Also: (none) => https://bugs.mageia.org/show_bug.cgi?id=32467
CC: (none) => saveurlinux