Github messages for voidlinux
 help / color / mirror / Atom feed
From: thomasxg <thomasxg@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: screen frozen linux6.6 and 6.7
Date: Sat, 23 Mar 2024 18:20:09 +0100	[thread overview]
Message-ID: <20240323172009.200692157C@inbox.vuxu.org> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-48473@inbox.vuxu.org>

[-- Attachment #1: Type: text/plain, Size: 5346 bytes --]

New comment by thomasxg on void-packages repository

https://github.com/void-linux/void-packages/issues/48473#issuecomment-2016552514

Comment:
I have the same issue when installing/running Void, so I'm stuck on the 6.5.13 kernel for now (NVIDIA GTX 1060 3G).

I did manage to login to the "frozen" machine via ssh and take a look at the log. I'll post the trace below from booting the 6.8.1 kernel, I get the same error from the 6.6.22 kernel:

```
[    2.231417] ------------[ cut here ]------------
[    2.231418] kernel BUG at include/linux/scatterlist.h:187!
[    2.231422] fbcon: Taking over console
[    2.231429] invalid opcode: 0000 [#1] PREEMPT SMP PTI
[    2.231432] CPU: 3 PID: 333 Comm: systemd-udevd Not tainted 6.8.1_1 #1
[    2.231436] Hardware name: System manufacturer System Product Name/H170I-PRO, BIOS 3805 05/16/2018
[    2.231440] RIP: 0010:sg_init_one+0x77/0x80
[    2.231446] Code: 00 01 83 e1 03 a8 03 75 23 83 e2 01 75 20 48 09 c8 41 89 6c 24 08 49 89 04 24 41 89 5c 24 0c 5b 5d 41 5c 41 5d c3 cc cc cc cc <0f> 0b 0f 0b 0f 0b 0f 1f 00 90 90 90 90 90 90 90 90 90 90 90 90 90
[    2.231452] RSP: 0018:ffffb221804c78d0 EFLAGS: 00010246
[    2.231456] RAX: 0000000000000000 RBX: 0000000000005000 RCX: 0000000000000027
[    2.231459] RDX: 0000000000000036 RSI: 0000000000000000 RDI: ffffb22200599000
[    2.231462] RBP: 0000000000005000 R08: 0000000000000000 R09: 0000000000000000
[    2.231466] R10: ffff96bf02610058 R11: 0000000000000000 R12: ffff96bf02610058
[    2.231469] R13: ffffb22180599000 R14: ffffb22180265000 R15: ffffb22180265100
[    2.231472] FS:  00007fa35e14e740(0000) GS:ffff96c226d80000(0000) knlGS:0000000000000000
[    2.231476] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[    2.231479] CR2: 00007ffe8930eff8 CR3: 0000000100d5e005 CR4: 00000000003706f0
[    2.231482] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
[    2.231485] DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
[    2.231488] Call Trace:
[    2.231491]  <TASK>
[    2.231493]  ? die+0x36/0x90
[    2.231498]  ? do_trap+0xda/0x100
[    2.231501]  ? sg_init_one+0x77/0x80
[    2.231505]  ? do_error_trap+0x6a/0x90
[    2.231508]  ? sg_init_one+0x77/0x80
[    2.231511]  ? exc_invalid_op+0x50/0x70
[    2.231515]  ? sg_init_one+0x77/0x80
[    2.231518]  ? asm_exc_invalid_op+0x1a/0x20
[    2.231524]  ? sg_init_one+0x77/0x80
[    2.231529]  nvkm_firmware_ctor+0x1fd/0x260 [nouveau]
[    2.231657]  nvkm_falcon_fw_ctor_hs+0x113/0x360 [nouveau]
[    2.231768]  gm200_acr_hsfw_ctor+0xce/0xf0 [nouveau]
[    2.231878]  gp102_acr_load+0x206/0x370 [nouveau]
[    2.231989]  nvkm_acr_new_+0x208/0x2f0 [nouveau]
[    2.232098]  nvkm_device_ctor+0xd74/0x4610 [nouveau]
[    2.232239]  nvkm_device_pci_new+0x101/0x2c0 [nouveau]
[    2.232379]  nouveau_drm_probe+0xd5/0x280 [nouveau]
[    2.232513]  ? _raw_spin_unlock_irqrestore+0x27/0x50
[    2.232518]  local_pci_probe+0x42/0xa0
[    2.232522]  pci_device_probe+0xc1/0x220
[    2.232527]  really_probe+0x19b/0x3e0
[    2.232532]  ? __pfx___driver_attach+0x10/0x10
[    2.232536]  __driver_probe_device+0x78/0x160
[    2.232540]  driver_probe_device+0x1f/0x90
[    2.232545]  __driver_attach+0xd2/0x1c0
[    2.232549]  bus_for_each_dev+0x85/0xd0
[    2.232553]  bus_add_driver+0x116/0x220
[    2.232557]  driver_register+0x59/0x100
[    2.232561]  ? __pfx_nouveau_drm_init+0x10/0x10 [nouveau]
[    2.232662]  do_one_initcall+0x58/0x320
[    2.232668]  do_init_module+0x60/0x240
[    2.232672]  __do_sys_init_module+0x17f/0x1b0
[    2.232677]  do_syscall_64+0x88/0x180
[    2.232681]  ? fpregs_assert_state_consistent+0x26/0x50
[    2.232687]  entry_SYSCALL_64_after_hwframe+0x6e/0x76
[    2.232691] RIP: 0033:0x7fa35e365c9a
[    2.232695] Code: 48 8b 0d 91 21 0d 00 f7 d8 64 89 01 48 83 c8 ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 49 89 ca b8 af 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d 5e 21 0d 00 f7 d8 64 89 01 48
[    2.232701] RSP: 002b:00007ffe89323e68 EFLAGS: 00000246 ORIG_RAX: 00000000000000af
[    2.232706] RAX: ffffffffffffffda RBX: 00007fa35ce00010 RCX: 00007fa35e365c9a
[    2.232709] RDX: 00007fa35e45aafd RSI: 0000000000730769 RDI: 00007fa35ce00010
[    2.232712] RBP: 0000555f37eb4570 R08: 0000000000007b80 R09: 0000000000000000
[    2.232715] R10: 00007fa35e438b20 R11: 0000000000000246 R12: 00007fa35e45aafd
[    2.232718] R13: 0000000000020000 R14: 0000555f37eaab00 R15: 0000000000000001
[    2.232723]  </TASK>
[    2.232725] Modules linked in: sd_mod nouveau(+) drm_gpuvm drm_exec gpu_sched i2c_algo_bit drm_display_helper cec ahci crct10dif_pclmul libahci rc_core crc32_pclmul polyval_clmulni xhci_pci polyval_generic libata drm_kms_helper gf128mul ghash_clmulni_intel xhci_pci_renesas sha512_ssse3 drm_ttm_helper sha256_ssse3 ttm sha1_ssse3 mxm_wmi aesni_intel agpgart xhci_hcd crypto_simd drm scsi_mod cryptd usbcore usb_common scsi_common video wmi button dm_mirror dm_region_hash dm_log dm_mod btrfs blake2b_generic xor raid6_pq libcrc32c crc32c_generic crc32c_intel
[    2.232773] ---[ end trace 0000000000000000 ]---
```

Perhaps someone else can confirm the same error on their machine, it seems to be something related to firmware loading?

[6.8.1.log](https://github.com/void-linux/void-packages/files/14733053/6.8.1.log)


  parent reply	other threads:[~2024-03-23 17:20 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-01  3:57 [ISSUE] " levdopa
2024-02-01 15:47 ` abenson
2024-02-01 20:19 ` levdopa
2024-02-01 20:27 ` classabbyamp
2024-02-01 22:09 ` levdopa
2024-02-06  1:57 ` nau5ea
2024-02-06 17:24 ` mblouka
2024-02-06 17:25 ` mblouka
2024-02-06 17:26 ` mblouka
2024-02-09 18:10 ` Sapein
2024-03-09 12:17 ` Brixy
2024-03-23 17:20 ` thomasxg [this message]
2024-03-23 19:24 ` mblouka
2024-03-23 19:24 ` mblouka
2024-04-16 20:14 ` nezos

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20240323172009.200692157C@inbox.vuxu.org \
    --to=thomasxg@users.noreply.github.com \
    --cc=ml@inbox.vuxu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).