Conversation

Notices

1. Embed this notice
   pistolero :thispersondoesnotexist: (p@freespeechextremist.com)'s status on Thursday, 25-Jan-2024 01:05:14 JST pistolero :thispersondoesnotexist:
   :hacker_f::hacker_s::hacker_e:
   
   It's up again. Didn't reboot the box to try out the new kernel (with the hotplug to disable the bad stick in software) over the weekend because dog, will do it this weekend, or just drive down there, shut it down, and pop the bad stick.
   • , 受不了包 and ✙ dcc :pedomustdie: :phear_slackware: like this.
   • Embed this notice
     pistolero :thispersondoesnotexist: (p@freespeechextremist.com)'s status on Thursday, 25-Jan-2024 04:15:39 JST pistolero :thispersondoesnotexist:

     in reply to
     Then it bounces twice. Working right now, will probably boot the machine to try the new kernel anyway if it's gonna be this much of a pain in the ass.
   • Embed this notice
     pistolero :thispersondoesnotexist: (p@freespeechextremist.com)'s status on Thursday, 25-Jan-2024 08:53:11 JST pistolero :thispersondoesnotexist:

     in reply to
     Okay, are we alive?
     
     If we stay alive, it is because the shit I guessed was correct. Got I/O errors attempting to use memory hotplug. The memory failure subsystem (/usr/src/linux-*/Documentation/ABI/testing/sysfs-memory-page-offline) worked, but I'm not entirely certain I got the addresses right; often, mcelog and dmesg and /sys have different opinions on what an address is. But no MCEs, no problems, everything seems fine, and the VM hasn't had an aneurysm yet, so I guess it's cool.
     
     I look forward to forgetting what I typed that fixed it by the next time something retarded happens and the machine reboots.
   • Embed this notice
     pistolero :thispersondoesnotexist: (p@freespeechextremist.com)'s status on Friday, 26-Jan-2024 03:34:21 JST pistolero :thispersondoesnotexist:

     in reply to
     Gonna just pop the stick in bank 18 ("B7") over the weekend. Gonna be a weird week for FSE. :bofh:
     ✙ dcc :pedomustdie: :phear_slackware: likes this.
   • Embed this notice
     pistolero :thispersondoesnotexist: (p@freespeechextremist.com)'s status on Friday, 26-Jan-2024 09:04:08 JST pistolero :thispersondoesnotexist:

     in reply to
     Basically when it crashed, it said "Memory failure: 0xfca3a4: already hardware poisoned". I don't know what would make the kernel hand that memory to a process if it's already poisoned.
     
     Anyway, reasonable idea would be to just pop the bad stick instead of trying to hack around it in software.
     ✙ dcc :pedomustdie: :phear_slackware: likes this.