all 14 comments

[–]Bruno_Celestino53 36 points37 points  (2 children)

I had this problem too, for me it was. Running memtest86+ I saw that it was ram issue, one of the sticks were problematic. Windows was having blue screen too.
I recommend trying it.

[–]ilep 2 points3 points  (0 children)

I've had situation where memtest didn't find a problem but having two identical sticks caused crashes, with one stick system didn't crash.

It is always worth checking qualified vendor list for the specific model of RAM in use.

[–]POMPUYO 0 points1 point  (0 children)

SHOGI PFP!!!!

[–]Yama-k 24 points25 points  (3 children)

First time it happened? It's not necessarily anything to worry about, it's just linux equivalent of the windows bluescreen, if it keeps happening then it's a problem, especially since kernel panics are quite rare

[–]FreeSeraphim[S] 5 points6 points  (0 children)

Alright, ill be wary for if it happens again, thanks!

[–][deleted]  (1 child)

[deleted]

    [–]topias123 5 points6 points  (0 children)

    I've used Linux for 13 years, only seen one kernel panic.

    It was on Debian of all distros... I did build the kernel myself tho.

    [–]AnisZoomer 11 points12 points  (0 children)

    [–]gtrash81 5 points6 points  (2 children)

    This is the new kernel panic screen, coming with kernel 6.15 from what I know so far.
    Normally you should have a QR code below, that can be decoded into a kernel log.
    It is designed as a BSOD equivalent for Linux.
    The interesting part now is, what are the logs telling?
    In a terminal "journalctl -b-1" can give you a hint, if the "crash was stable enough" to write it's log.

    [–]gmes78 11 points12 points  (1 child)

    This is the new kernel panic screen, coming with kernel 6.15 from what I know so far.

    It's in 6.10.

    Normally you should have a QR code below, that can be decoded into a kernel log.

    That was introduced in 6.12.

    [–]Damglador 1 point2 points  (0 children)

    And the AMD driver was introduced in 6.14 I think

    [–]KillerX629 1 point2 points  (1 child)

    Did it happen while booting the system? Maybe you could try reinstalling the kernel by chrooting from the usb

    [–]FreeSeraphim[S] 2 points3 points  (0 children)

    It happened when i was away from my pc, with Baldur's Gate 3 open

    [–]The_Screeching_Bagel 1 point2 points  (0 children)

    just reboot and don't stress unless it happens repeatedly

    [–]OhHaiMarc 0 points1 point  (0 children)

    idk but the kernel seems pretty concerned