You are not logged in.
Pages: 1
I'm running a win+arch dualboot system, though I haven't been using windows much so I started playing games through steam on arch. Normally it works fine but today I got a kernel panic. What should I do? Here is the log
Offline
https://chatgpt.com/share/694ef32c-e4a0 … 8c87486a43
sorry i couldnt resist
people usually dont trust chatgpt but its really good at those things
Offline
Before you throw the nvme at gpt
I'm running a win+arch dualboot system
3rd link below. Mandatory.
Disable it (it's NOT the BIOS setting!) and reboot windows and linux twice for voodo reasons.
Also https://wiki.archlinux.org/title/Solid_ … leshooting and check your journal whether there other IO/device related errors.
Also it matters *a lot* whether you constantly face the problem w/ the same inode.
Offline
3rd link below. Mandatory.
Thanks
And for the IO error, apparently there were none? idk I threw the log into chatgpt and did scans and there was no error.
Well I hope it doesn't become a recurring thing at least.
Offline
Your problems stat here
[37201.831845] Buffer I/O error on device nvme0n1p6, logical block 1175625What to no surprise give etx4 a hard time
[37204.612861] EXT4-fs error (device nvme0n1p6): ext4_find_extent:939: inode #5157453: comm ThreadPool Thre: pblk 46566141 bad header/extent: invalid magic - magic 0, entries 0, max 0(0), depth 0(0)
[37204.612930] EXT4-fs error (device nvme0n1p6): ext4_find_extent:939: inode #5157453: comm ThreadPool Thre: pblk 46566141 bad header/extent: invalid magic - magic 0, entries 0, max 0(0), depth 0(0)
[37204.612958] EXT4-fs error (device nvme0n1p6): ext4_find_extent:939: inode #5157453: comm ThreadPool Thre: pblk 46566141 bad header/extent: invalid magic - magic 0, entries 0, max 0(0), depth 0(0)
[37204.612979] EXT4-fs error (device nvme0n1p6): ext4_find_extent:939: inode #5157453: comm ThreadPool Thre: pblk 46566141 bad header/extent: invalid magic - magic 0, entries 0, max 0(0), depth 0(0)
[37204.612999] EXT4-fs error (device nvme0n1p6): ext4_find_extent:939: inode #5157453: comm ThreadPool Thre: pblk 46566141 bad header/extent: invalid magic - magic 0, entries 0, max 0(0), depth 0(0)
[37204.613018] EXT4-fs error (device nvme0n1p6): ext4_find_extent:939: inode #5157453: comm ThreadPool Thre: pblk 46566141 bad header/extent: invalid magic - magic 0, entries 0, max 0(0), depth 0(0)
[37204.613070] EXT4-fs error (device nvme0n1p6): ext4_find_extent:939: inode #5157453: comm ThreadPool Thre: pblk 46566141 bad header/extent: invalid magic - magic 0, entries 0, max 0(0), depth 0(0)
[37204.613091] EXT4-fs error (device nvme0n1p6): ext4_find_extent:939: inode #5157453: comm ThreadPool Thre: pblk 46566141 bad header/extent: invalid magic - magic 0, entries 0, max 0(0), depth 0(0)
[37204.613110] EXT4-fs error (device nvme0n1p6): ext4_find_extent:939: inode #5157453: comm ThreadPool Thre: pblk 46566141 bad header/extent: invalid magic - magic 0, entries 0, max 0(0), depth 0(0)
[37204.613128] EXT4-fs error (device nvme0n1p6): ext4_find_extent:939: inode #5157453: comm ThreadPool Thre: pblk 46566141 bad header/extent: invalid magic - magic 0, entries 0, max 0(0), depth 0(0)ultimately causing the panic.
The question is what triggers the "Buffer I/O error on device nvme0n1p6, logical block 1175625"
If you get more of those, they better are not all on logical block 1175625 - also still check your smart data.
The dual boot is a possible explanation for the problems but by no means the definitive one.
Offline
Smartctl says the ssd is fine, except I noticed that the number of unsafe shutdowns was unusually high? I don't remember leaving my laptop to die off that many times. Could that have any implication?
Offline
Could that have any implication?
This happens when the disk loses power for whatever reason. Could be the APST situation linked in the nvme troubleshooting section.
Offline
Pages: 1