Why?! All those hours I put into my startup up until that point are now gone! These sort of game-ending events remind me of a time when games had no 'save' functionality and should have no place on the management/simulation genre today. You have to get all of your feature ratings above 7, which I did. For example, there is a quest (non-optional "objective") that is forced on you. What if instead you made them rarer and more random to appear genuine and you make the economics and management aspects of the game harder to balance the game's difficulty? Overall I would say it is fun, however, that is until you run into the game breaking bugs. These aspects seem unfairly punitive and not random at all like they would be in real life. For example, negative events seem to appear right when the game knows you are doing good financially. There are also certain aspects of the game that need to be balanced and polished. It has many great features that other similar games do not. Its a cute game and you can tell it is a labor of love. It has many great tl dr: Decent game but needs polish and has game-breaking bugs.
# Linux/x86_64 6.0.0-rc3 Kernel ConfigurationĬONFIG_CC_VERSION_TEXT="gcc-11 (Debian 11.3.0-8) 11.3.Tl dr: Decent game but needs polish and has game-breaking bugs. # Automatically generated file DO NOT EDIT. # please remove ~/.lkp and /lkp dir to run from a clean state. # if come across any failure that blocks the test, Make HOSTCC=gcc-11 CC=gcc-11 ARCH=x86_64 INSTALL_MOD_PATH= modules_installįind lib/ | cpio -o -H newc -quiet | gzip > modules.cgzīin/lkp qemu -k -m modules.cgz job-script # job-script is attached in this email Make HOSTCC=gcc-11 CC=gcc-11 ARCH=x86_64 olddefconfig prepare modules_prepare bzImage modules ? _raw_callee_save_native_queued_spin_unlock (?:?) CPU: 0 PID: 0 Comm: swapper Not tainted 6.0.1-gdb8d280d38ef #5 PANIC: early exception 0x0e IP 10:ffffffff8149c282 error 0 cr2 0x1e08 If you fix the issue, kindly add following tag | BUG:kernel_hang_in_boot_stage | 0 | 18 | On test machine: qemu-system-x86_64 -enable-kvm -cpu SandyBridge -smp 2 -m 16GĬaused below changes (please refer to attached dmesg/kmsg for entire log/backtrace):
#Startup panic steam Patch
Patch link: subject: mm: use stack_depot for recording kmemleak's backtrace report FYIįYI, we noticed the following commit (built with gcc-11):Ĭommit: db8d280d38efb061ad1a57ce060cbb917a4cf503 (" mm: use stack_depot for recording kmemleak's backtrace") " 0e949320db: now it seems have new issue. Seems this is the fix based on our report
Db8d280d38: PANIC:early_exception - kernel test robot All of help / color / mirror / Atom feed From: kernel test robot
0 kommentar(er)
