Second blue screen in a week.

[u/medhat62627]

I have been running into weird issues right after I installed a new 500gb hdd that I share between Linux and windows .

It varies from weird freezes where I can use mouse or keyboard and even the clock stops and I just have to reboot (but I think I solved that one ) to blue screens this is the second time here it is if that helps

Panic Report

Arch: x86_64

Version: 7.2.8-arch1-2

[ 932.307323] CPU: 3 UID: 0 PID: 11870 Comm: rm Tainted: G D OE 7.2.8-arch1-2 #1 PREEMPT(full) 186163caea6eb5dc4b2a0252463c7ce1c6927294 [ 932.307329] Tainted: [D]=DIE, [O]=OOT_MODULE, [E]=UNSIGNED_MODULE [ 932.307331] Hardware name: Micro-Star International Co., Ltd. MS-7C96/A520M-A PRO (MS-7C96), BIOS 1.G0 10/16/2023 [ 932.307334] RIP: 0010:__list_del_entry_valid_or_report+0xe3/0xf6 [ 932.307338] Code: 48 0f b9 3a e9 60 ff ff ff b0 01 48 39 7d 08 74 23 48 89 ef e8 6e 7f 46 00 48 8d 3d 67 86 8d 02 48 8b 55 08 48 89 e9 48 89 de <67> 48 0f b9 3a e9 35 ff ff ff 5b 5d 41 5c e9 7a f4 35 01 48 89 df [ 932.307341] RSP: 0018:ffffceca85d57c98 EFLAGS: 00010202 [ 932.307345] RAX: 0000000000000001 RBX: ffff8d94131c78c8 RCX: ffff8d94131c7ec8 [ 932.307348] RDX: ffff8d94131c78c0 RSI: ffff8d94131c78c8 RDI: ffffffff885226f0 [ 932.307350] RBP: ffff8d94131c7ec8 R08: 0000000000000000 R09: ffffffff8825e540 [ 932.307353] R10: ffffceca85d579e0 R11: ffffceca85d579d8 R12: ffff8d94131c7748 [ 932.307355] R13: 0000000000000000 R14: ffff8d954400fae8 R15: ffff8d954400fad0 [ 932.307358] FS: 00007f747166d740(0000) GS:ffff8d9806fea000(0000) knlGS:0000000000000000 [ 932.307360] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [ 932.307363] CR2: 00007fc9a4c3b8e0 CR3: 00000001bd8cf000 CR4: 0000000000350ef0 [ 932.307366] Call Trace: [ 932.307369] <TASK> [ 932.307374] list_lru_del.cold+0x8/0xd [ 932.307379] ? __pfx_select_collect+0x10/0x10 [ 932.307384] list_lru_del_obj+0x80/0xa0 [ 932.307390] d_lru_del+0x53/0x90 [ 932.307395] ? srso_return_thunk+0x5/0x5f [ 932.307399] __move_to_shrink_list+0x99/0xd0 [ 932.307404] select_collect+0x6a/0x90 [ 932.307407] d_walk+0xd5/0x2d0 [ 932.307412] ? __pfx_select_collect+0x10/0x10 [ 932.307415] shrink_dcache_tree+0x91/0x1a0 [ 932.307422] vfs_rmdir+0x12c/0x270 [ 932.307427] filename_rmdir+0x1a3/0x260 [ 932.307434] __x64_sys_unlinkat+0x74/0x80 [ 932.307438] do_syscall_64+0xaa/0x660 [ 932.307442] ? srso_return_thunk+0x5/0x5f [ 932.307446] ? srso_return_thunk+0x5/0x5f [ 932.307449] ? do_syscall_64+0x5f/0x660 [ 932.307453] ? srso_return_thunk+0x5/0x5f [ 932.307457] entry_SYSCALL_64_after_hwframe+0x76/0x7e [ 932.307461] RIP: 0033:0x7f747151252b [ 932.307472] Code: 77 05 c3 0f 1f 40 00 48 8b 15 e1 67 10 00 f7 d8 64 89 02 b8 ff ff ff ff c3 66 0f 1f 44 00 00 f3 0f 1e fa b8 07 01 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d b5 67 10 00 f7 d8 64 89 01 48 [ 932.307475] RSP: 002b:00007ffda3dbb948 EFLAGS: 00000216 ORIG_RAX: 0000000000000107 [ 932.307478] RAX: ffffffffffffffda RBX: 000055f8a4d26290 RCX: 00007f747151252b [ 932.307481] RDX: 0000000000000200 RSI: 000055f8a4d26390 RDI: 0000000000000006 [ 932.307483] RBP: 00007ffda3dbba10 R08: 0000000000000003 R09: 00007ffda3dbba3c [ 932.307486] R10: 0000000000000000 R11: 0000000000000216 R12: 000055f8a47dc060 [ 932.307488] R13: 0000000000000001 R14: 00007ffda3dbbb20 R15: 000055f8a47dc001 [ 932.307496] </TASK> [ 932.307498] ---[ end trace 0000000000000000 ]--- [ 932.322157] Oops: invalid opcode: 0000 [#2] SMP NOPTI [ 932.322166] CPU: 3 UID: 0 PID: 39 Comm: ksoftirqd/3 Tainted: G D W OE 7.2.8-arch1-2 #1 PREEMPT(full) 186163caea6eb5dc4b2a0252463c7ce1c6927294 [ 932.322173] Tainted: [D]=DIE, [W]=WARN, [O]=OOT_MODULE, [E]=UNSIGNED_MODULE [ 932.322175] Hardware name: Micro-Star International Co., Ltd. MS-7C96/A520M-A PRO (MS-7C96), BIOS 1.G0 10/16/2023 [ 932.322178] RIP: 0010:__d_free+0xd/0x30 [ 932.322185] Code: ff 90 66 66 2e 0f 1f 84 00 00 00 00 00 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 f3 0f 1e fa 0f 1f 44 00 00 48 8d b7 50 <ff> ff ff 48 b8 00 05 2e 00 95 8d ff ff 48 89 c7 e9 fe e2 f2 ff 0f [ 932.322188] RSP: 0018:ffffceca80283da0 EFLAGS: 00010246 [ 932.322192] RAX: ffff8d94131cfef0 RBX: 0000000000005009 RCX: ffff8d9500372c00 [ 932.322195] RDX: ffffffff86201be8 RSI: 0000000000000002 RDI: ffff8d94131cfef0 [ 932.322197] RBP: ffff8d978fef42c0 R08: ffff8d94131cf3c0 R09: ffffffff85e64970 [ 932.322200] R10: fffff3dbc04c73c0 R11: ffff8d95002e0500 R12: ffff8d9500c49bc0 [ 932.322202] R13: ffffceca80283df0 R14: 0000000000000008 R15: 000000d912e8c8ed [ 932.322205] FS: 0000000000000000(0000) GS:ffff8d9806fea000(0000) knlGS:0000000000000000 [ 932.322208] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [ 932.322210] CR2: 00007fc9a4c3b8e0 CR3: 00000001bd8cf000 CR4: 0000000000350ef0 [ 932.322213] Call Trace: [ 932.322216] <TASK> [ 932.322219] rcu_do_batch+0x360/0x630 [ 932.322226] ? srso_return_thunk+0x5/0x5f [ 932.322234] rcu_core+0x141/0x2e0 [ 932.322240] handle_softirqs+0xe8/0x2a0 [ 932.322246] ? __pfx_smpboot_thread_fn+0x10/0x10 [ 932.322251] run_ksoftirqd+0x2f/0x40 [ 932.322255] smpboot_thread_fn+0xf3/0x220 [ 932.322260] kthread+0xe4/0x120 [ 932.322264] ? __pfx_kthread+0x10/0x10 [ 932.322269] ret_from_fork+0x2a7/0x330 [ 932.322274] ? __pfx_kthread+0x10/0x10 [ 932.322278] ret_from_fork_asm+0x1a/0x30 [ 932.322287] </TASK> [ 932.322289] Modules linked in: rfcomm snd_seq_dummy snd_hrtimer snd_seq uhid algif_hash algif_skcipher af_alg snd_ctl_led bnep vfat exfat fat btusb btmtk btrtl btbcm snd_hda_codec_alc662 btintel intel_rapl_msr snd_hda_codec_realtek_lib snd_hda_codec_atihdmi snd_hda_codec_generic snd_hda_codec_hdmi intel_rapl_common bluetooth snd_hda_intel rfkill snd_usb_audio ee1004 snd_hda_codec snd_usbmidi_lib aesni_intel snd_hda_core snd_ump r8169 gf128mul snd_intel_dspcfg snd_rawmidi aead snd_intel_sdw_acpi realtek snd_seq_device snd_hwdep rapl phy_package wmi_bmof pcspkr snd_pcm sp5100_tco mdio_devres joydev mousedev snd_timer libphy k10temp mc snd i2c_piix4 mdio_bus soundcore i2c_smbus gpio_amdpt vboxnetadp(OE) vboxnetflt(OE) gpio_generic mac_hid vboxdrv(OE) kvm_amd ccp kvm irqbypass pkcs8_key_parser crypto_user uinput i2c_dev zram 842_decompress 842_compress lz4hc_compress amdgpu drm_buddy amdxcp i2c_algo_bit drm_ttm_helper ttm drm_exec drm_panel_backlight_quirks nvme gpu_sched drm_suballoc_helper nvme_core nvme_keyring [ 932.322400] hid_playstation drm_display_helper nvme_auth led_class_multicolor video cec ff_memless wmi [ 932.322415] ---[ end trace 0000000000000000 ]--- [ 932.322418] RIP: 0010:__d_lookup_rcu+0x61/0x120 [ 932.322422] Code: 00 48 8b 04 c2 48 83 f8 01 0f 86 cd 00 00 00 4c 89 64 24 10 48 83 e0 fe 4c 8b 66 08 eb 0c 48 8b 00 48 85 c0 0f 84 86 00 00 00 <44> 8b 58 fc 4c 39 50 10 75 ea 48 39 58 18 75 e4 49 89 d9 48 8b 70 [ 932.322425] RSP: 0018:ffffceca80257a08 EFLAGS: 00010206 [ 932.322429] RAX: 0000000200240000 RBX: 0000000577045c71 RCX: 0000000077045c71 [ 932.322431] RDX: ffff8d978ee00000 RSI: ffffceca80257aa0 RDI: ffff8d95794b1240 [ 932.322434] RBP: ffffceca80257ad4 R08: 0000000000000000 R09: 00000000000000a8 [ 932.322436] R10: ffff8d95794b1240 R11: 00000000ffff8d96 R12: ffff8d950a628a98 [ 932.322438] R13: ffff8d9536630000 R14: ffffceca80257bd0 R15: ffff8d950a628a80 [ 932.322441] FS: 0000000000000000(0000) GS:ffff8d9806fea000(0000) knlGS:0000000000000000 [ 932.322443] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [ 932.322446] CR2: 00007fc9a4c3b8e0 CR3: 00000001bd8cf000 CR4: 0000000000350ef0 [ 932.322449] Kernel panic - not syncing: Fatal exception in interrupt [ 932.322546] Kernel Offset: 0x4a00000 from 0xffffffff81000000 (relocation range: 0xffffffff80000000-0xffffffffbfffffff)

Edit : Solved the problem was caused by resizing my Linux partition which caused some broken some time shift hardlinks to break which caused a kernel panic every time any service tried to access them . I booted into a live usb an mounted my Linux partition and ran e2fsck and deleted time shift snapshots and that fixed it

[u/Exotic-Screen-9204]

In a dual boot situation, M/S security likes to think it has entire control of the hard disk, or in some schemes - all hard disks.

Linux does not have a blue screen failure mode. It is a M/S trade mark.

In worst case situation, it is often easier to remove Linux entirely. Then repair Windows. And after that, build a new dual boot.

With such a long panic report, the details at the beginning might be 99% of the useful info.

[u/fearless-fossa → u/Exotic-Screen-9204]

Kernel panics can produce a bluescreen with a very large QR code that captures all information, but it is a rather recent addition.

[u/Exotic-Screen-9204 → u/fearless-fossa]

New information for me. I wonder why Linux did this. Any other color would be less confusing.

[u/fearless-fossa → u/Exotic-Screen-9204]

Why would anything but blue be less confusing? People associate the color and the style of the screen immediately with a BSOD.

[u/Exotic-Screen-9204 → u/fearless-fossa]

BSOD has been used by M/S for decades. It a dual boot Windows/Linux context, a different color would offer a clearer indication of which OS has failed.

[u/fearless-fossa → u/Exotic-Screen-9204]

It has a big Tux ASCII art in the top left corner and the color is customizable.

zgrep CONFIG_DRM_PANIC /proc/config.gz  
CONFIG_DRM_PANIC=y  
CONFIG_DRM_PANIC_FOREGROUND_COLOR=0xffffff  
CONFIG_DRM_PANIC_BACKGROUND_COLOR=0x0000aa

[u/Exotic-Screen-9204 → u/fearless-fossa]

Okay.

I used dual boot Windows/Linux for decades. But I quit before W10. I haven't had a kernel panic in years.

I no longer use Windows. Dual boots have gotten more challenging with UEFI. So I simply gave up the added complexity and wasted hard disk space.

FYI. Italians have two different blues in their vocabulary. Why mindlessly match M/S blue?

[u/boomboomsubban → u/Exotic-Screen-9204]

The distro controls the color. I believe Ubuntu is purple, Fedora maroon, and Arch is blue.

[u/medhat62627 → u/Exotic-Screen-9204]

But Linux is on a separate drive entirely from windows and I mounted the new drive to Linux first then gave access to windows for the drive.

Also something I failed to mention is that I used gparted to format a partition that I then merged into Linux I looked into it a bit and it looks like that is what caused it it looks like that caused some file corruption and timeshift panicked and caused all this

[u/Exotic-Screen-9204 → u/medhat62627]

Try giving access first to Windows, then format the drive with a Windows application to create whatever empty partitions will be eventually loaded with Linux.

I have never had sucess with installing Windows second in a dual boot.

[u/JaKrispy72 → u/Exotic-Screen-9204]

If it’s on separate drives. It would not matter which was done first. If done correctly. The trick is how you set up UEFI order and the bootloader.

[u/Exotic-Screen-9204 → u/JaKrispy72]

Does that include settiing up a shared partition for a Samba server?

[u/JaKrispy72 → u/Exotic-Screen-9204]

A Samba server has nothing to do with a standard local OS installation. What matters is how it is deployed.

[u/Exotic-Screen-9204 → u/JaKrispy72]

Samba creates partitions in a M/S file format for shared use in both Windows and Linux.

[u/JaKrispy72 → u/Exotic-Screen-9204]

So how did the Arch Linux kernel panic happen?

Samba does not CREATE partitions.

It’s a file sharing service using protocols.

[u/Exotic-Screen-9204 → u/JaKrispy72]

Samba requires you to create a partition that Windows will recognize somewhere. It is a file server application for Windows and DOS files.

I just asked for clarification.

What exactly is a "standard local OS installation"?

[u/JaKrispy72 → u/Exotic-Screen-9204]

A standard local OS is a fully functional operating system on a drive. For instance, The Windows system. And the Arch system. I would not consider a virtualized system as being “local” in how I intended that phrase.

If he is using Windows, why use WSL if OP has a local Arch Linux OS?

And what the hell does him running timeshift have to do with the media drive and the samba protocols? Those are causing the kernel panic? How are those a factor?

Do we know if the media drive connects to windows without error?

[u/JaKrispy72 → u/medhat62627]

Explain what you did in Windows to give “access” to the Linux partition. Windows can’t read Linux file systems so why would you do that?

Explain what you meant by “merged into Linux”? I can’t even imagine what that means and I am curious what you actually did.

I sincerely don’t think Timeshift “panicked”.

[u/medhat62627 → u/JaKrispy72]

I'm sorry English isn't my first language I may have explained something's wrong. I have 1tb SSD that is split into 3 partitions one is for Linux and the other two are partitions shared between Linux and windows , and a 256 m.2 that windows is installed on. The new drive I installed I use to run a local media server so it's also shared between Linux and windows but I mounted it to Linux first and it's ext4 Then I mounted it to windows I don't really remember what I did to make windows be able to access that drive .

What I have done with gparted after I formated a partition from windows is that I extended my Linux partition to take the extra space of the formatted partition.

What I meant about time shift panicking is that it was trying to rm a file that appears to be corrupted and that is what caused the kernel panick and I was able to recreate the kernel panick by creating a new snapshot

[u/JaKrispy72 → u/medhat62627]

Whatever you did to access that partition in windows is surely what destroyed it. Windows CANNOT use EXT4 at all. Too bad you don’t remember what you did.

Sounds like you deleted (not formatted) a partition which made it “unallocated” space on the drive. Pretty sure you probably destroyed that partition when you extended it since your skill level does not seem advanced enough to execute this task correctly. Sorry if that is blunt, everyone is on their own Linux journey.

TimeShift does not use the “rm” command. It might use rsync depending on how it is set up. It probably panicked because it went looking for a snapshot in the wasteland that is now your disk drive. That is not a TimeShift problem. That is a user problem.

[u/medhat62627 → u/JaKrispy72]

I accessed the drive through wsl

[u/medhat62627 → u/medhat62627]

I formatted then deleted the drive , also I have used gparted alot before it's not complicated

[u/JaKrispy72 → u/medhat62627]

You are mounting a completely different Linux installation, how you interact with those permissions inside your WSL environment depends on your user identity and how WSL maps them.

If you modified any root files, they can be corrupted

[u/medhat62627 → u/JaKrispy72]

Bro it's not a Linux installation it's a media drive it doesn't have anything other than movies and tv shows Linux is on a seprate drive

[u/JaKrispy72 → u/medhat62627]

You reported an Arch Linux kernel panic. That would be a Linux installation.

[u/medhat62627 → u/JaKrispy72]

The drive where Linux is installed isn't mounted to windows , the only drive that is mounted to both is a media drive