I don’t really understand the cause and effect here but I finally got rid of “GPU HANG” issue with #i915, i.e.
Jul 02 21:20:50 suppilovahvero kernel: i915 0000:03:00.0: [drm] GPU HANG: ecode 12:1:84dfd7f7, in ChaosGate.exe >
Jul 02 21:20:50 suppilovahvero kernel: i915 0000:03:00.0: [drm] ChaosGate.exe[40919] context reset due to GPU ha>
I did the following:
/etc/modprobe.d/i915.conf
and run sudo dracut --force
(in Fedora).The contents of /etc/modprobe.d/i915.conf
are the following:
options i915 enable_guc=3
options i915 enable_fbc=1
I put these there because I found multiple forum posts etc. where this was the suggested solution but obviously I have zero idea what they’re doing 🤷 I’ve played Chaos Gate as a test without hangs, and it used to hang within just few minutes.
It is still a bit weird that #Fedora 40 with its default settings gives such crap results on Intel Arc A770.
I like to start a bug fix by:
$ git commit -a -s --allow-empty -m "Fixes: 1085b8276bb4 (\"tpm: Add the rest of the session HMAC API\")"
[auth-null d5d3411b52f7] Fixes: 1085b8276bb4 ("tpm: Add the rest of the session HMAC API")
$ git show
commit d5d3411b52f741cb16cfb7180d24f454e97b4570 (HEAD -> auth-null)
Author: Jarkko Sakkinen <jarkko@kernel.org>
Date: Wed Jul 3 18:47:46 2024 +0300
Fixes: 1085b8276bb4 ("tpm: Add the rest of the session HMAC API")
Signed-off-by: Jarkko Sakkinen <jarkko@kernel.org>
So that I get the fixes-line backed up fast :-) Then I just amend the meat.
For generating the fixes line I have:
git-fixes() {
git --no-pager log --format='Fixes: %h ("%s")' --abbrev=12 -1 $1;
}
Sometimes while I'm digging around the bowels of PLs, I find websites straight out of the 90s for seemingly active projects:
My initial ~/.vimrc
for #vim after 3-4 years of using #neovim:
filetype plugin indent on
syntax enable
let g:mapleader = ","
set autoindent
set autoread
set formatoptions+=j
set guifont=MesloLGM\ Nerd\ Font\ Mono\ 12
set hidden
set history=500
set hlsearch
set listchars=tab:→\ ,trail:•,extends:›,precedes:‹,nbsp:␣,eol:↲
set nobackup
set nonumber
set noswapfile
set nowrap
set path+=**
set scrolloff=1
set showbreak=↪\
set showmatch
set sidescroll=1
set smarttab
set tags=./tags;/
set termguicolors
nnoremap <silent> <C-l> :nohl<C-R>=has('diff')?'<Bar>diffupdate':''<CR><CR><C-L>
nnoremap <silent> <leader>lcd :lcd %:p:h<CR>:pwd<CR>
nnoremap <silent> <leader>n :set number!<CR>
if !empty(globpath(&rtp, 'autoload/plug.vim'))
call plug#begin()
Plug 'ap/vim-buftabline', { 'as': 'buftabline' }
Plug 'dracula/vim', { 'as': 'dracula' }
Plug 'editorconfig/editorconfig-vim', { 'as': 'editorconfig' }
Plug 'kaarmu/typst.vim', { 'as': 'typst' }
Plug 'tpope/vim-commentary', { 'as': 'commentary' }
Plug 'vim-scripts/git_patch_tags.vim', { 'as': 'git_patch_tags' }
call plug#end()
endif
silent! colorscheme dracula
It’s quite short but does pretty much what I would ever want from a text editor:
$ wc -l .vimrc
42 .vimrc
The OpenAI ChatGPT app on macOS is not sandboxed and stores all the conversations in **plain-text** in a non-protected location:
~/Library/Application\ Support/com.openai.chat/conversations-{uuid}/
So basically any other running app / process / malware can read all your ChatGPT conversations without any permission prompt:
Generally speaking, C is pretty straightforward. It takes about 20 days to learn 80% of it, and then no more than 20 years to cover the remaining 20%