It turned out that hibernation aka s2disk is BETTER (generally quicker due to [Z]RAM usage) **while** using FireDragon web browser [Linux]

Replacing a browser changes whole system usage experience.

So far the following exclusive-or: dismission or quick hibernation start.

Main cause maybe FireDragon compiled with R language? As drivers??

Linux usermode programming is somewhat similar to the driver programming.

 QMutex helped one time with controlling GUI from C++ under Qt library. I Don't know precisely, why.

But smartphonized//controlled s**t can comprehend??

How **SHIT** you are, USA!!!

(...)

   LD [M]  drivers/scsi/csiostor/csiostor.o

  CC [M]  drivers/scsi/smartpqi/smartpqi_init.o

PLEASE submit a bug report to https://github.com/llvm/llvm-project/issues/ and include the crash backtrace, preprocessed source, and associated run script.

Stack dump:

0. Program arguments: clang -Wp,-MMD,drivers/scsi/smartpqi/.smartpqi_init.o.d -nostdinc -I./arch/x86/include -I./arch/x86/include/generated -I./include -I./arch/x86/include/uapi -I./arch/x86/include/generated/uapi -I./include/uapi -I./include/generated/uapi -include ./include/linux/compiler-version.h -include ./include/linux/kconfig.h -include ./include/linux/compiler_types.h -D__KERNEL__ --target=x86_64-linux-gnu -fintegrated-as -Werror=unknown-warning-option -Werror=ignored-optimization-argument -Werror=option-ignored -Werror=unused-command-line-argument -fmacro-prefix-map=./= -std=gnu11 -fshort-wchar -funsigned-char -fno-common -fno-PIE -fno-strict-aliasing -mno-sse -mno-mmx -mno-sse2 -mno-3dnow -mno-avx -fcf-protection=branch -fno-jump-tables -m64 -falign-loops=1 -mno-80387 -mno-fp-ret-in-387 -mstack-alignment=8 -mskip-rax-setup -mtune=generic -mno-red-zone -mcmodel=kernel -Wno-sign-compare -fno-asynchronous-unwind-tables -mretpoline-external-thunk -mindirect-branch-cs-prefix -mfunction-return=thunk-extern -mharden-sls=all -fpatchable-function-entry=16,16 -fno-delete-null-pointer-checks -O2 -fstack-protector-strong -ftrivial-auto-var-init=zero -fno-stack-clash-protection -pg -mfentry -DCC_USING_NOP_MCOUNT -DCC_USING_FENTRY -falign-functions=16 -fstrict-flex-arrays=3 -fno-strict-overflow -fno-stack-check -Wall -Wundef -Werror=implicit-function-declaration -Werror=implicit-int -Werror=return-type -Werror=strict-prototypes -Wno-format-security -Wno-trigraphs -Wno-frame-address -Wno-address-of-packed-member -Wmissing-declarations -Wmissing-prototypes -Wframe-larger-than=2048 -Wno-gnu -Wvla -Wno-pointer-sign -Wcast-function-type -Wimplicit-fallthrough -Werror=date-time -Werror=incompatible-pointer-types -Wenum-conversion -Wextra -Wunused -Wno-unused-but-set-variable -Wno-unused-const-variable -Wno-format-overflow -Wno-format-overflow-non-kprintf -Wno-format-truncation-non-kprintf -Wno-override-init -Wno-pointer-to-enum-cast -Wno-tautological-constant-out-of-range-compare -Wno-unaligned-access -Wno-enum-compare-conditional -Wno-enum-enum-conversion -Wno-missing-field-initializers -Wno-type-limits -Wno-shift-negative-value -Wno-sign-compare -Wno-unused-parameter -g -gdwarf-5 -DMODULE -DKBUILD_BASENAME=\"smartpqi_init\" -DKBUILD_MODNAME=\"smartpqi\" -D__KBUILD_MODNAME=kmod_smartpqi -c -o drivers/scsi/smartpqi/smartpqi_init.o drivers/scsi/smartpqi/smartpqi_init.c

1. <eof> parser at end of file

2. Code generation

 #0 0x00007b958a9c4d90 llvm::sys::PrintStackTrace(llvm::raw_ostream&, int) (/usr/lib/libLLVM.so.18.1+0x7c4d90)

 #1 0x00007b958a9c226d llvm::sys::CleanupOnSignal(unsigned long) (/usr/lib/libLLVM.so.18.1+0x7c226d)

 #2 0x00007b958a8a88e9 (/usr/lib/libLLVM.so.18.1+0x6a88e9)

 #3 0x00007b9589c50ae0 (/usr/lib/libc.so.6+0x3cae0)

 #4 0x00007b958caa12f4 llvm::MCAssembler::registerSymbol(llvm::MCSymbol const&) (/usr/lib/libLLVM.so.18.1+0x28a12f4)

 #5 0x00007b958cae94f1 llvm::MCObjectStreamer::emitValueImpl(llvm::MCExpr const*, unsigned int, llvm::SMLoc) (/usr/lib/libLLVM.so.18.1+0x28e94f1)

 #6 0x00007b958b660640 llvm::AddressPool::emit(llvm::AsmPrinter&, llvm::MCSection*) (/usr/lib/libLLVM.so.18.1+0x1460640)

 #7 0x00007b958b6d7b8b llvm::DwarfDebug::endModule() (/usr/lib/libLLVM.so.18.1+0x14d7b8b)

 #8 0x00007b958b66fb1b llvm::AsmPrinter::doFinalization(llvm::Module&) (/usr/lib/libLLVM.so.18.1+0x146fb1b)

 #9 0x00007b958ab78e0d llvm::FPPassManager::doFinalization(llvm::Module&) (/usr/lib/libLLVM.so.18.1+0x978e0d)

#10 0x00007b958ab85149 llvm::legacy::PassManagerImpl::run(llvm::Module&) (/usr/lib/libLLVM.so.18.1+0x985149)

#11 0x00007b959392f21f clang::EmitBackendOutput(clang::DiagnosticsEngine&, clang::HeaderSearchOptions const&, clang::CodeGenOptions const&, clang::TargetOptions const&, clang::LangOptions const&, llvm::StringRef, llvm::Module*, clang::BackendAction, llvm::IntrusiveRefCntPtr<llvm::vfs::FileSystem>, std::unique_ptr<llvm::raw_pwrite_stream, std::default_delete<llvm::raw_pwrite_stream>>, clang::BackendConsumer*) (/usr/lib/libclang-cpp.so.18.1+0x152f21f)

#12 0x00007b9593cadd95 clang::BackendConsumer::HandleTranslationUnit(clang::ASTContext&) (/usr/lib/libclang-cpp.so.18.1+0x18add95)

#13 0x00007b9592989f23 clang::ParseAST(clang::Sema&, bool, bool) (/usr/lib/libclang-cpp.so.18.1+0x589f23)

#14 0x00007b959441a7c1 clang::FrontendAction::Execute() (/usr/lib/libclang-cpp.so.18.1+0x201a7c1)

#15 0x00007b95943bbad7 clang::CompilerInstance::ExecuteAction(clang::FrontendAction&) (/usr/lib/libclang-cpp.so.18.1+0x1fbbad7)

#16 0x00007b959446e11d clang::ExecuteCompilerInvocation(clang::CompilerInstance*) (/usr/lib/libclang-cpp.so.18.1+0x206e11d)

#17 0x00005bddd4459284 cc1_main(llvm::ArrayRef<char const*>, char const*, void*) (/usr/bin/clang-18+0x13284)

#18 0x00005bddd445d5ba (/usr/bin/clang-18+0x175ba)

#19 0x00007b95940f7175 (/usr/lib/libclang-cpp.so.18.1+0x1cf7175)

#20 0x00007b958a8a8d3a llvm::CrashRecoveryContext::RunSafely(llvm::function_ref<void ()>) (/usr/lib/libLLVM.so.18.1+0x6a8d3a)

#21 0x00007b95940f9aa6 (/usr/lib/libclang-cpp.so.18.1+0x1cf9aa6)

#22 0x00007b95940b5529 clang::driver::Compilation::ExecuteCommand(clang::driver::Command const&, clang::driver::Command const*&, bool) const (/usr/lib/libclang-cpp.so.18.1+0x1cb5529)

#23 0x00007b95940b591c clang::driver::Compilation::ExecuteJobs(clang::driver::JobList const&, llvm::SmallVectorImpl<std::pair<int, clang::driver::Command const*>>&, bool) const (/usr/lib/libclang-cpp.so.18.1+0x1cb591c)

#24 0x00007b95940d38c4 clang::driver::Driver::ExecuteCompilation(clang::driver::Compilation&, llvm::SmallVectorImpl<std::pair<int, clang::driver::Command const*>>&) (/usr/lib/libclang-cpp.so.18.1+0x1cd38c4)

#25 0x00005bddd445febd clang_main(int, char**, llvm::ToolContext const&) (/usr/bin/clang-18+0x19ebd)

#26 0x00005bddd4450fb5 main (/usr/bin/clang-18+0xafb5)

#27 0x00007b9589c39c88 (/usr/lib/libc.so.6+0x25c88)

#28 0x00007b9589c39d4c __libc_start_main (/usr/lib/libc.so.6+0x25d4c)

#29 0x00005bddd4451015 _start (/usr/bin/clang-18+0xb015)

clang: error: clang frontend command failed with exit code 139 (use -v to see invocation)

clang version 18.1.8

Target: x86_64-unknown-linux-gnu

Thread model: posix

InstalledDir: /usr/bin

clang: note: diagnostic msg: 

********************

PLEASE ATTACH THE FOLLOWING FILES TO THE BUG REPORT:

Preprocessed source(s) and associated run script(s) are located at:

clang: note: diagnostic msg: /tmp/smartpqi_init-60f254.c

clang: note: diagnostic msg: /tmp/smartpqi_init-60f254.sh

clang: note: diagnostic msg: 

********************

make[5]: *** [scripts/Makefile.build:244: drivers/scsi/smartpqi/smartpqi_init.o] Error 1

make[4]: *** [scripts/Makefile.build:485: drivers/scsi/smartpqi] Error 2

make[3]: *** [scripts/Makefile.build:485: drivers/scsi] Error 2

make[2]: *** [scripts/Makefile.build:485: drivers] Error 2

make[1]: *** [/HIBERPATCH/original/linux611/src/linux-6.11-rc3/Makefile:1925: .] Error 2

NVIDIA/Xorg screen (RE)DRAW BUG as a next case from multievidence of (un)corporate RATS: both business and open source „mans”!!

When using Linux ope*RAT*ing system, remember about it overwhelming downsides!

But the worst is HIBERNATION. And shut up stupids forum maniacs!

People don't write about topic THAT GOING INTO s2disk AND (!!!) RETURNING, THE HDD DRIVE SPINS DOWN [the HDD LIFETIME] in summary THREE TIMES, NOT THE ONE AMOUNT NEEDED — a. before saving image b. when power downs (and, again, NOT ACPI!!!!!) c. while resuming!!!! WHAT YOU NOT UNDERSTAND??

— How this is even possible, crappy people!! Errors, bugs at fundamental kernel-mode levels!!!

They have hope that new approach into NVIDIA drivers will make the Xorg/Wayland experience normalized?

When errors last from nouveau times/usage??!! Discovered at KNOPPIX distribution. The screen not whole crashing, but modern Blender repaints often in black. I remember also the mouse problem to this day. *Your* stupidity, you cannot even maintain Linice debugger – I saw 32-bit version (DWORD—compilation problem) now, 2024.

•Even more! Can't check one Rebecca Black OS Wayland operating (- checked by pgrep to surety! -), because screen completely damages (source of naming convention...!!) at startup!

If *you* would stop bad NLP, then you'd have more mind abilities.

Linux is not such revolution. It lacks in graphics, and power management. Simple sleep operation (to RAM) sometimes crashes whole system. Some fear can arise when VT-switch, still. Some people like standard Linux VT, and you crap do regress Blender (both in BI and memory consumption/loading times by main program file size), VTs (some a'la VT remake layers when you cannot even in.... QUICK simple words explain usage of fbsplash), IF YOU CANNOT MAKE SOMETHING REPAIRED THEN YOU CREATE REGRESSION MAYBE DELIBERATELY!?? Does KWin/Wayfire support ALL compiz options (as ccsm) or NOT?!!

*You* must stand in truth!! Fake mans == apes!

You programmers/testers/bug reporters & forums „staff” are •lazy, •news-oriented, •stupid/ADHD•unlogical – WHY s2disk informs me about page poisoning, when I am sure that my RAM are OK!!! && And why you cannot make comprehenvive manpage about differentating basic concepts: KMS, framebuffer, ...x...dga, DRM!!!

Basic programming layer is making key concepts simple & logical – not jumping with manpage, info, wiki, forum.

Linux OS lacks documentation ability – its structure is very confusing (in comparison with M$' MSDN Library / aka MSDN Collection). Kernel code comments are non-encyclopedical, non-scientific (w/o making big difference in sys-freeze, disk-freeze, suspend and hibernation). Yea, particular KDE program makes help pages user experience a bit better. But it is NOT what we need. But again, very strange that variety of naming conventions and DE amount harden the ability to quickness – productiveness. As Babel thing, once again.