*Monotonic* uptime in Linux hibernation increased by 1, into a 5 days now.

I think it was maybe due to FireDragon browser. No graphic card upgrade!!! Still older nvidia.

I don't know if crash (second time!!) has been from swap, or if it was from NVIDIA bugs. SysRq magic key combinations are slightly overmarketed! Reset combination was needed.

Maybe a quick fix of some hibernation problems? With new FireDragon Browser, monotonic uptime of 4 days, 21:06:50.592779 (Linux)

Current hibernation cycle uptime

4 days, 21:06:50.592779

Fish version of monotonic uptime script:

type uptime
uptime is a function with definition
# Defined in /root/.config/fish/functions/BASH.fish @ line 48
function uptime
   python3 -c 'import time,datetime;print(datetime.timedelta(seconds=time.clock_gettime(time.CLOCK_MONOTONIC)))'
end

!Important. „Fish s-hell”: You MUST include a newly created file containing your function/abbrev into standard fish settings files (as  shown in the snippet above)– in order not to erase functions when updating sth with your system package manager!!!!

And it does work under Xorg normally!!!

Memory leak of 882-877 =5MB after hibernation?? Browser was in text-mode only. AND: they USA are so STUPID, **that** possibility under NOUVEAU the same error aroses!!!

They're so IMPOSSIBLY stupid, certainly... they do bad and good simultaneously, shits of hybrids... [ARURT-US!!!]

 •Test circumstances - [EDIT] I omitted copying certain param into „shadow” module subsystem... &... THE PROPER ONE.

„Clear” initcpio: no nvidia, no nouveau & /etc/modprobe.d/nvidia.conf filled-in.
And  NVreg_PreserveVideoMemoryAllocations=1 as copy from boot cmdline:

 

/etc/modprobe.d/nvidia.conf        :

...

 6 options nvidia  NVreg_PreserveVideoMemoryAllocations=1
 7 options nvidia_drm  NVreg_PreserveVideoMemoryAllocations=1
 8 options nvidia_modeset   NVreg_PreserveVideoMemoryAllocations=1
 9 options nvidia_uvm  NVreg_PreserveVideoMemoryAllocations=1
10 

.... 

# Defined in /root/.config/fish/functions/BASH.fish @ line 50
function hibertest
   s2disk -P "shutdown method"="reboot"
end

Standard GLX info program [EDIT — that is, before the 1-param duplication from cmdline...]:

 root@Knoppix /# glxinfo |grep -i "mem"

Gives
    GLX_NV_multisample_coverage, GLX_NV_robustness_video_memory_purge,
    GLX_NV_robustness_video_memory_purge, GLX_NV_swap_group,
    GLX_NV_multisample_coverage, GLX_NV_robustness_video_memory_purge,
Memory info (GL_NVX_gpu_memory_info):
    Dedicated video memory: 1024 MB
    Total available memory: 1024 MB
    Currently available dedicated video memory: 886 MB
    GL_NVX_gpu_memory_info, GL_NV_ES1_1_compatibility,
    GL_NV_gpu_program5, GL_NV_gpu_program5_mem_extended,
    GL_NV_robustness_video_memory_purge, GL_NV_shader_atomic_counters,
    GL_NV_transform_feedback2, GL_NV_uniform_buffer_unified_memory,
    GL_NV_vertex_attrib_integer_64bit, GL_NV_vertex_buffer_unified_memory,
    GL_NVX_gpu_memory_info, GL_NV_ES1_1_compatibility,
    GL_NV_gpu_program5, GL_NV_gpu_program5_mem_extended,
    GL_NV_robustness_video_memory_purge, GL_NV_shader_atomic_counters,
    GL_NV_transform_feedback2, GL_NV_uniform_buffer_unified_memory,
    GL_NV_vertex_attrib_integer_64bit, GL_NV_vertex_buffer_unified_memory,
root@Knoppix /# glxinfo |grep -i "mem"
    GLX_NV_multisample_coverage, GLX_NV_robustness_video_memory_purge,
    GLX_NV_robustness_video_memory_purge, GLX_NV_swap_group,
    GLX_NV_multisample_coverage, GLX_NV_robustness_video_memory_purge,
Memory info (GL_NVX_gpu_memory_info):
    Dedicated video memory: 1024 MB
    Total available memory: 1024 MB
    Currently available dedicated video memory: 882 MB
    GL_NVX_gpu_memory_info, GL_NV_ES1_1_compatibility,
    GL_NV_gpu_program5, GL_NV_gpu_program5_mem_extended,
    GL_NV_robustness_video_memory_purge, GL_NV_shader_atomic_counters,
    GL_NV_transform_feedback2, GL_NV_uniform_buffer_unified_memory,
    GL_NV_vertex_attrib_integer_64bit, GL_NV_vertex_buffer_unified_memory,
    GL_NVX_gpu_memory_info, GL_NV_ES1_1_compatibility,
    GL_NV_gpu_program5, GL_NV_gpu_program5_mem_extended,
    GL_NV_robustness_video_memory_purge, GL_NV_shader_atomic_counters,
    GL_NV_transform_feedback2, GL_NV_uniform_buffer_unified_memory,
    GL_NV_vertex_attrib_integer_64bit, GL_NV_vertex_buffer_unified_memory,
root@Knoppix /# glxinfo |grep -i "mem"
    GLX_NV_multisample_coverage, GLX_NV_robustness_video_memory_purge,
    GLX_NV_robustness_video_memory_purge, GLX_NV_swap_group,
    GLX_NV_multisample_coverage, GLX_NV_robustness_video_memory_purge,
Memory info (GL_NVX_gpu_memory_info):
    Dedicated video memory: 1024 MB
    Total available memory: 1024 MB
    Currently available dedicated video memory: 882 MB
    GL_NVX_gpu_memory_info, GL_NV_ES1_1_compatibility,
    GL_NV_gpu_program5, GL_NV_gpu_program5_mem_extended,
    GL_NV_robustness_video_memory_purge, GL_NV_shader_atomic_counters,
    GL_NV_transform_feedback2, GL_NV_uniform_buffer_unified_memory,
    GL_NV_vertex_attrib_integer_64bit, GL_NV_vertex_buffer_unified_memory,
    GL_NVX_gpu_memory_info, GL_NV_ES1_1_compatibility,
    GL_NV_gpu_program5, GL_NV_gpu_program5_mem_extended,
    GL_NV_robustness_video_memory_purge, GL_NV_shader_atomic_counters,
    GL_NV_transform_feedback2, GL_NV_uniform_buffer_unified_memory,
    GL_NV_vertex_attrib_integer_64bit, GL_NV_vertex_buffer_unified_memory,
root@Knoppix /# glxinfo |grep -i "mem"
    GLX_NV_multisample_coverage, GLX_NV_robustness_video_memory_purge,
    GLX_NV_robustness_video_memory_purge, GLX_NV_swap_group,
    GLX_NV_multisample_coverage, GLX_NV_robustness_video_memory_purge,
Memory info (GL_NVX_gpu_memory_info):
    Dedicated video memory: 1024 MB
    Total available memory: 1024 MB
    Currently available dedicated video memory: 882 MB
    GL_NVX_gpu_memory_info, GL_NV_ES1_1_compatibility,
    GL_NV_gpu_program5, GL_NV_gpu_program5_mem_extended,
    GL_NV_robustness_video_memory_purge, GL_NV_shader_atomic_counters,
    GL_NV_transform_feedback2, GL_NV_uniform_buffer_unified_memory,
    GL_NV_vertex_attrib_integer_64bit, GL_NV_vertex_buffer_unified_memory,
    GL_NVX_gpu_memory_info, GL_NV_ES1_1_compatibility,
    GL_NV_gpu_program5, GL_NV_gpu_program5_mem_extended,
    GL_NV_robustness_video_memory_purge, GL_NV_shader_atomic_counters,
    GL_NV_transform_feedback2, GL_NV_uniform_buffer_unified_memory,
    GL_NV_vertex_attrib_integer_64bit, GL_NV_vertex_buffer_unified_memory,
root@Knoppix /# glxinfo |grep -i "mem"
    GLX_NV_multisample_coverage, GLX_NV_robustness_video_memory_purge,
    GLX_NV_robustness_video_memory_purge, GLX_NV_swap_group,
    GLX_NV_multisample_coverage, GLX_NV_robustness_video_memory_purge,
Memory info (GL_NVX_gpu_memory_info):
    Dedicated video memory: 1024 MB
    Total available memory: 1024 MB
    Currently available dedicated video memory: 882 MB
    GL_NVX_gpu_memory_info, GL_NV_ES1_1_compatibility,
    GL_NV_gpu_program5, GL_NV_gpu_program5_mem_extended,
    GL_NV_robustness_video_memory_purge, GL_NV_shader_atomic_counters,
    GL_NV_transform_feedback2, GL_NV_uniform_buffer_unified_memory,
    GL_NV_vertex_attrib_integer_64bit, GL_NV_vertex_buffer_unified_memory,
    GL_NVX_gpu_memory_info, GL_NV_ES1_1_compatibility,
    GL_NV_gpu_program5, GL_NV_gpu_program5_mem_extended,
    GL_NV_robustness_video_memory_purge, GL_NV_shader_atomic_counters,
    GL_NV_transform_feedback2, GL_NV_uniform_buffer_unified_memory,
    GL_NV_vertex_attrib_integer_64bit, GL_NV_vertex_buffer_unified_memory,
root@Knoppix /# glxinfo |grep -i "mem"
    GLX_NV_multisample_coverage, GLX_NV_robustness_video_memory_purge,
    GLX_NV_robustness_video_memory_purge, GLX_NV_swap_group,
    GLX_NV_multisample_coverage, GLX_NV_robustness_video_memory_purge,
Memory info (GL_NVX_gpu_memory_info):
    Dedicated video memory: 1024 MB
    Total available memory: 1024 MB
    Currently available dedicated video memory: 882 MB
    GL_NVX_gpu_memory_info, GL_NV_ES1_1_compatibility,
    GL_NV_gpu_program5, GL_NV_gpu_program5_mem_extended,
    GL_NV_robustness_video_memory_purge, GL_NV_shader_atomic_counters,
    GL_NV_transform_feedback2, GL_NV_uniform_buffer_unified_memory,
    GL_NV_vertex_attrib_integer_64bit, GL_NV_vertex_buffer_unified_memory,
    GL_NVX_gpu_memory_info, GL_NV_ES1_1_compatibility,
    GL_NV_gpu_program5, GL_NV_gpu_program5_mem_extended,
    GL_NV_robustness_video_memory_purge, GL_NV_shader_atomic_counters,
    GL_NV_transform_feedback2, GL_NV_uniform_buffer_unified_memory,
    GL_NV_vertex_attrib_integer_64bit, GL_NV_vertex_buffer_unified_memory,
root@Knoppix /# glxinfo |grep -i "mem"
    GLX_NV_multisample_coverage, GLX_NV_robustness_video_memory_purge,
    GLX_NV_robustness_video_memory_purge, GLX_NV_swap_group,
    GLX_NV_multisample_coverage, GLX_NV_robustness_video_memory_purge,
Memory info (GL_NVX_gpu_memory_info):
    Dedicated video memory: 1024 MB
    Total available memory: 1024 MB
    Currently available dedicated video memory: 882 MB
    GL_NVX_gpu_memory_info, GL_NV_ES1_1_compatibility,
    GL_NV_gpu_program5, GL_NV_gpu_program5_mem_extended,
    GL_NV_robustness_video_memory_purge, GL_NV_shader_atomic_counters,
    GL_NV_transform_feedback2, GL_NV_uniform_buffer_unified_memory,
    GL_NV_vertex_attrib_integer_64bit, GL_NV_vertex_buffer_unified_memory,
    GL_NVX_gpu_memory_info, GL_NV_ES1_1_compatibility,
    GL_NV_gpu_program5, GL_NV_gpu_program5_mem_extended,
    GL_NV_robustness_video_memory_purge, GL_NV_shader_atomic_counters,
    GL_NV_transform_feedback2, GL_NV_uniform_buffer_unified_memory,
    GL_NV_vertex_attrib_integer_64bit, GL_NV_vertex_buffer_unified_memory,
root@Knoppix /# hibertest
root@Knoppix /# glxinfo |grep -i "mem"
    GLX_NV_multisample_coverage, GLX_NV_robustness_video_memory_purge,
    GLX_NV_robustness_video_memory_purge, GLX_NV_swap_group,
    GLX_NV_multisample_coverage, GLX_NV_robustness_video_memory_purge,
Memory info (GL_NVX_gpu_memory_info):
    Dedicated video memory: 1024 MB
    Total available memory: 1024 MB
    Currently available dedicated video memory: 877 MB
    GL_NVX_gpu_memory_info, GL_NV_ES1_1_compatibility,
    GL_NV_gpu_program5, GL_NV_gpu_program5_mem_extended,
    GL_NV_robustness_video_memory_purge, GL_NV_shader_atomic_counters,
    GL_NV_transform_feedback2, GL_NV_uniform_buffer_unified_memory,
    GL_NV_vertex_attrib_integer_64bit, GL_NV_vertex_buffer_unified_memory,
    GL_NVX_gpu_memory_info, GL_NV_ES1_1_compatibility,
    GL_NV_gpu_program5, GL_NV_gpu_program5_mem_extended,
    GL_NV_robustness_video_memory_purge, GL_NV_shader_atomic_counters,
    GL_NV_transform_feedback2, GL_NV_uniform_buffer_unified_memory,
    GL_NV_vertex_attrib_integer_64bit, GL_NV_vertex_buffer_unified_memory,
root@Knoppix /# glxinfo |grep -i "mem"
    GLX_NV_multisample_coverage, GLX_NV_robustness_video_memory_purge,
    GLX_NV_robustness_video_memory_purge, GLX_NV_swap_group,
    GLX_NV_multisample_coverage, GLX_NV_robustness_video_memory_purge,
Memory info (GL_NVX_gpu_memory_info):
    Dedicated video memory: 1024 MB
    Total available memory: 1024 MB
    Currently available dedicated video memory: 877 MB
    GL_NVX_gpu_memory_info, GL_NV_ES1_1_compatibility,
    GL_NV_gpu_program5, GL_NV_gpu_program5_mem_extended,
    GL_NV_robustness_video_memory_purge, GL_NV_shader_atomic_counters,
    GL_NV_transform_feedback2, GL_NV_uniform_buffer_unified_memory,
    GL_NV_vertex_attrib_integer_64bit, GL_NV_vertex_buffer_unified_memory,
    GL_NVX_gpu_memory_info, GL_NV_ES1_1_compatibility,
    GL_NV_gpu_program5, GL_NV_gpu_program5_mem_extended,
    GL_NV_robustness_video_memory_purge, GL_NV_shader_atomic_counters,
    GL_NV_transform_feedback2, GL_NV_uniform_buffer_unified_memory,
    GL_NV_vertex_attrib_integer_64bit, GL_NV_vertex_buffer_unified_memory,
root@Knoppix /# glxinfo |grep -i "mem"
    GLX_NV_multisample_coverage, GLX_NV_robustness_video_memory_purge,
    GLX_NV_robustness_video_memory_purge, GLX_NV_swap_group,
    GLX_NV_multisample_coverage, GLX_NV_robustness_video_memory_purge,
Memory info (GL_NVX_gpu_memory_info):
    Dedicated video memory: 1024 MB
    Total available memory: 1024 MB
    Currently available dedicated video memory: 877 MB
    GL_NVX_gpu_memory_info, GL_NV_ES1_1_compatibility,
    GL_NV_gpu_program5, GL_NV_gpu_program5_mem_extended,
    GL_NV_robustness_video_memory_purge, GL_NV_shader_atomic_counters,
    GL_NV_transform_feedback2, GL_NV_uniform_buffer_unified_memory,
    GL_NV_vertex_attrib_integer_64bit, GL_NV_vertex_buffer_unified_memory,
    GL_NVX_gpu_memory_info, GL_NV_ES1_1_compatibility,
    GL_NV_gpu_program5, GL_NV_gpu_program5_mem_extended,
    GL_NV_robustness_video_memory_purge, GL_NV_shader_atomic_counters,
    GL_NV_transform_feedback2, GL_NV_uniform_buffer_unified_memory,
    GL_NV_vertex_attrib_integer_64bit, GL_NV_vertex_buffer_unified_memory,
root@Knoppix /# glxinfo |grep -i "mem"
    GLX_NV_multisample_coverage, GLX_NV_robustness_video_memory_purge,
    GLX_NV_robustness_video_memory_purge, GLX_NV_swap_group,
    GLX_NV_multisample_coverage, GLX_NV_robustness_video_memory_purge,
Memory info (GL_NVX_gpu_memory_info):
    Dedicated video memory: 1024 MB
    Total available memory: 1024 MB
    Currently available dedicated video memory: 877 MB
    GL_NVX_gpu_memory_info, GL_NV_ES1_1_compatibility,
    GL_NV_gpu_program5, GL_NV_gpu_program5_mem_extended,
    GL_NV_robustness_video_memory_purge, GL_NV_shader_atomic_counters,
    GL_NV_transform_feedback2, GL_NV_uniform_buffer_unified_memory,
    GL_NV_vertex_attrib_integer_64bit, GL_NV_vertex_buffer_unified_memory,
    GL_NVX_gpu_memory_info, GL_NV_ES1_1_compatibility,
    GL_NV_gpu_program5, GL_NV_gpu_program5_mem_extended,
    GL_NV_robustness_video_memory_purge, GL_NV_shader_atomic_counters,
    GL_NV_transform_feedback2, GL_NV_uniform_buffer_unified_memory,
    GL_NV_vertex_attrib_integer_64bit, GL_NV_vertex_buffer_unified_memory,
root@Knoppix /# glxinfo |grep -i "mem"
    GLX_NV_multisample_coverage, GLX_NV_robustness_video_memory_purge,
    GLX_NV_robustness_video_memory_purge, GLX_NV_swap_group,
    GLX_NV_multisample_coverage, GLX_NV_robustness_video_memory_purge,
Memory info (GL_NVX_gpu_memory_info):
    Dedicated video memory: 1024 MB
    Total available memory: 1024 MB
    Currently available dedicated video memory: 877 MB
    GL_NVX_gpu_memory_info, GL_NV_ES1_1_compatibility,
    GL_NV_gpu_program5, GL_NV_gpu_program5_mem_extended,
    GL_NV_robustness_video_memory_purge, GL_NV_shader_atomic_counters,
    GL_NV_transform_feedback2, GL_NV_uniform_buffer_unified_memory,
    GL_NV_vertex_attrib_integer_64bit, GL_NV_vertex_buffer_unified_memory,
    GL_NVX_gpu_memory_info, GL_NV_ES1_1_compatibility,
    GL_NV_gpu_program5, GL_NV_gpu_program5_mem_extended,
    GL_NV_robustness_video_memory_purge, GL_NV_shader_atomic_counters,
    GL_NV_transform_feedback2, GL_NV_uniform_buffer_unified_memory,
    GL_NV_vertex_attrib_integer_64bit, GL_NV_vertex_buffer_unified_memory,
root@Knoppix /#

After combining boot „cmdline” with NVreg_PreserveVideoMemoryAllocations=1 , 2× HIBERNATION OK

Preface:
» Even Brave full-crash DID NOT indicated graphic card crash!!!

I restarted Brave successfully (a contrario previous times, when FULL [not-soft] reboot was needed).

In summary, two resumed hibernations, along one brave crash & Brave restart!

Final /proc/cmdline addition list of parameters:

• nvidia_drm.modeset=1

• nvidia_drm.fbdev=1 

•NVreg_PreserveVideoMemoryAllocations=1

This is a complete misunderstanding that you can't join such info into quick handbook, USA!!! Only this „joy”, „gaming”!!!!

You don't need to study forums!!!! How simple is this.... – a some rule, that proper guide-book is far more important than forums, with all selective quietness (!!!), & other NLP sh*ts.

Not website but „Compiled HTML Help” 'd be OK... YOU CAN'T... even make manpages .... that 'd be simply-usable...

I think also your U. S. „L/R problems” are also from your f***ng, sinful-THUS-stupid, antimorality... . The one nation, that is in „big bit” comparable to Russia...

I hear NLP when listening to U. S. music (there are some honorable exceptions).

ZRAM&HIBERNATION w/swappiness value of 50 good for Brave and several other BIG apps (SIMULTANEOUSLY!)

Startup often quick, sometimes swap op going on along relatively short timespan.

THUS:

It makes NO sense to hear „specialists” saying 80, 100 or... „even” above 'd be.... . Its false, I performed several hibernations, monotonic uptime so far 4+ days.

Closing of SMALLER applications before hibernation.

With ≈3 GB of RAM, I must control some smaller unnecessary applications – before (complaining) s2disk. But after shutdown of something, the rest process is OK.

Thrash-protect Python script has been turned off during test.

It isn't as useful, maybe not a bit!!!

Bad bug of hibernation causes 3 HDD spindowns in a full s2disk cycle -SUDDENLY I found THIS[after I reduced it to 2]

Possible solution for hibernation problem

But why it is not in /proc/... filesystem already??

Documentation abilities of Linuxed USA is still very poor – it frustrates so much. I remember Microsoft MSDN, it was written in good manner, easy to read, find, etc. . But in Linux, some Qt help program does is – but seems to be still in early stage. The sh**it of problem is having to remember next, next – why Windows had XP with good hibernation feature and Linux to this days, on the same BIOS (!!!) spins down HDD three times?

Maybe not BIOS is bad, but OS(es) itself.

Windows XP hiber-OK => Windows 7 regression (with the same BIOS, understand!!!). And now some strange module lines to #define some boolean value?? Hopefully, someone can think libata has 150k of lines — rather NOT.

Compilation furtherly – not believing programming groups – why?

Because („caused [to]”...) they, in my theory at least, have fun of old „technique” of making partial product (0.5-working, in other word aka „halfy”) — in disorder to make fun of repairing, repairing... . The worst feature of America, since „multipersons” don't trusting „original” G-d – they manipulate also Bible, even named it after Babel. If they can't read Hebrew „code”, they MUST have weak programming abilities – it is a general correlation of reality. In exegesis, a good code is helpful also. Letter by letter /literally/ in so-called „prehistoric” (!!!) languages „sin” can mean „China”. Atheists have NO good software philosophy, rather an POV of stupidity. If C++ programmer is „baptist”, then (IMO) he doesn't code in bug-resistant manner. 

You have poor religion, you are poor „informatician”. 

Those groups simply can't. Why they not opening BIOS/UEFI source code – an one example of thesis' evidence. 

...ATA flags?? You made source code (almost?) unreadable by „horkages”, „DMAs” and _do_ 's!!

Why not one „uncloned” procedure, but this nested ...do.... PM's function names and stuff?? Effect of years of laziness, addiction to music (why monopoly of Apple, can't do fusion with portable hardware producers?? You like your shit Babel crap, when stupid immoral can make money almost from nothing (aka fiduciary value in „eco”nomy). Some of this „rule” we see in „real life” of game industry (the most), and fears of incompatibility of Rockbox MP3 player „BIOS”.

Kernel recompilation BAD caveat (next!): .config's NOUVEAU is *NOT* marked (y/m) automatically/remains only commended out!!...

• —Despite make defconfig/localmodconfig/THE ETC.!!
• Similar problem is when installing Debian (EVEN both user/kernel-land packages ) inside chrooted container (or usual system as „well”, USTUPID): it is sado-masonism of USA — „deb configuring” have auto-remove even needed packages — we are not robots to discern it as bug!! Deb „configure” IMO does is equivocative — see Arch Linux pacman philosophy (!!!),
• Hibernation patch is in 1/3 OK – is means, HDD spindown turned from amount of 3 (three), to the smaller 2 (two) value.
• Yea, even if restoration failed to reach its end (drivers re-initialization, maybe from lacking of nouveau module - as above) – some crash – see what USA „colonization”, „mega”, „giga”, „super”, „explore”, „discover”, „fun//ky” (etc.) is not that morality that you should have ***to be really happy**** (NOT the «APE»).

LINUX HIBERNATION PATCH: CAUSED HDD SPIN DOWNS 3-TIMES (!!!) — REDUCED TO 2 now — working part of the bug FIX: I managed to ELIMINATE the one case, about the SNAPSHOT image saving image – HDD SPINDOWN REDUNDANCE!! STUPID PROGRAMMERS

So far general stub with conditional if, (nouveau KMS waits...)

In any standard Linux distribution, when you hibernate system to HDD – the disk is powered down 3 TIMES, NOT due to stupidity of Linux programmers

The bug is when uswsusp but reaches swsusp in kernel.

The bug means i short terms that HDD is powered down (spinned down that you can hear it clearly!!) unnecessary times (as in Windows 7, XP & even W2000 had hibernation functionality normal). They made code reusing in the improper manner.

HDD SPINDOWN REDUNDANCE!! STUPID PROGRAMMERS (& users).

„I can't believe” — — that you all not observed it — WHAT is your intuition??? And, where!!! You maybe wait for Fedora, Cent OS... wait, wait... waiting and lazy.... . HOW!!! Really you are unmoral SHIT that group of idiots made idiotal continuum (even if they name themselves Linux system programmers). „We” are not automatons – THINK! 

A some clue from grepping?? AND ROXTERM CAN'T COPY HTML FORMAT YOU „VARIOUS CURIOUS”

Error „listing” from Kbuild/make:

/HIBERPATCH/krnl_with_hiber_modifs/linux611/src/linux-6.11-rc3/samples/bpf/xdp_sample.bpf.h: * perf uses -Wstrict-aliasing=3 which makes build fail

Next worst a[s]pect of Linux is you need... the debugger for debugger, AND some de fucto compiler for even a... compiler.

They can't even port Linice to 64-bit 2024 systems. This'd be Linux future direction??!! YOU STUPID TALK ABOUT 128?!!

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.

'nolpm' parameter at Linux kernel command line NOT suppressed REDUNDANT HDD spin down — shortening hard disk lifetime. SHIT OPEN SOURCE NEO-PROPRIETARY LIARS

Understand what written?

You crap think that SSD disks are better?? WHY STUPID!!?
Marketing worms!! FALSE opensource co-workers, compared to Windows!! MONOPOLY of laziness.
They go into opensource to help others- or- to accumulate experience to return into buggy proprietary??? WHAT experience?? In managing of new HYBRID mainboard  „cards”: crap-shit hybrid modules?? BE CURSED!!! 

Both Cycles & Eevee: WORSER volumetrics VS Classic Blender Internal (→2....

Naivety that „future” / „„nonlegacy”” (what irony…) releases of Blender(/Bforartists) would be OK in cloud volumetric rendering must be cancelled... . Bfor have nice icons, but whole rendering are so nervous. Some ADHD of Americans. They think you should wait, wait, wait... . Ver, ver+, version»#.###... . Firstly repair what you have made buggy. Then, you will have proper field to add new functionality. Step after step. All with Spirituality. ...... There is some rationale of distance of „made” and „mad”. Two „bla bla best... fast... good for animations...” (do YOU mean that ugly, unmoral , pokemonny unpeaced anime? Or beautiful, natural, solid ... — they EVEN can't normalize Lux...!) are BAD in order to take Blender 3D graphics seriously. THEY REMOVED IT, the FK, even made black, sometimes I think ugly Blender GUI motive) according to functions of the packet?? Subliminal programming?). LUX IS COMPATIBLE WITH ZRAM & 3GB RAM, **DESPITE*** ITS EVEN INSTABILITY (?mainly PY-GIL?) . WHY YOU DON"T CONSOLIDATE CYCLES/EEVEE WITH LUXCORE? America seems to be ”good, yea” but the truth still remains that it is only empty, waste narcissism. Citizens are bad, then why require more morality from .... politicians? Bad corporations? Citizens are NOT ok. Instead of drawing such pokemons, the pokemon-goY, better solution for US is changing FAITH. Do NOT trust FREEWARE, do NOT trust stefania church baptists. Trust HaShem of Jewish instead. Freedom from money/nonprofit corporations is possible only in the proper Orientality. 3D Renderings are very handy here. Orientals have very interesting lookings (POV) around Earth & Cosmic topics. •My experiences demands assuming that selectivity of software engineers is so big, that they even don't account hibernation feature – that is, by measuring renderers (as even in Lux!!) times. Soft is hole – ful, buggy, semi-featured (halfy) as in closed, as in free soft. •Some persons would silently require that customer would replace graphics cards so often... for what? Even driver replacing (and checking if DKMS if for concrete kernel) is time-consuming. If U need pokemons, tell politics.... . Enjoy, US, small things... . Ha ha... #blender #bforartists #rendering #test #ranking #zram #linux #clouds #volumetric #OpenVDB #Cycles #Internal #Eevee #hibernation #crash #XServer #Xorg #OOM #bug #software #methodology #experiences #opensource #testing #packet #pros #cons #wtf #plugins #generator #noise #deformations #delicate #classic #apel #raytracing #evening #cloudscape #distorted #unaccurate #details #panel #settings #underlight #highlight #whatisbest #old #legacy #s2disk #modelling #3dblender #issue #actualization #pixels #mosaic #sunlight #sunbeams