| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-ID: <Zuho6e9T08Dzrqyp@gallifrey> Date: Mon, 16 Sep 2024 17:20:41 +0000 From: "Dr. David Alan Gilbert" <linux@...blig.org> To: Bob Gill <gillb5@...us.net> Cc: linux-kernel@...r.kernel.org Subject: Re: 6.11.0 crash on X startup * Bob Gill (gillb5@...us.net) wrote: > OK. Thanks! I'm not seeing anything too obvious, however... > 6.10.0.dmesg.txt: > > [ 0.000000] Linux version 6.10.0 (root@...edom) (gcc (Ubuntu > 11.4.0-1ubuntu1~22.04) 11.4.0, GNU ld (GNU Binutils for Ubuntu) 2.38) #1 SMP > PREEMPT_DYNAMIC Sun Jul 14 18:50:17 MDT 2024 > [ 0.000000] Command line: BOOT_IMAGE=/vmlinuz-6.10.0 > root=UUID=94072726-5fed-439f-a496-8e6aaa88617e ro quiet splash ..... > 6.11.0.dmesg.txt > > [ 0.000000] Linux version 6.11.0 (root@...edom) (gcc (Ubuntu > 11.4.0-1ubuntu1~22.04) 11.4.0, GNU ld (GNU Binutils for Ubuntu) 2.38) #1 SMP > PREEMPT_DYNAMIC Sun Sep 15 13:10:55 MDT 2024 > [ 0.000000] Command line: BOOT_IMAGE=/vmlinuz-6.11.0 > root=UUID=94072726-5fed-439f-a496-8e6aaa88617e ro recovery nomodeset > dis_ucode_ldr > [ 0.000000] KERNEL supported cpus: Would it be possible to get a 6.11.0 dmesg without the 'nomodeset' ? I realise that's trickier, but it's really where things start to get interesting. On the 6.10 dmesg we have the normal fun: > [ 15.759932] [drm] amdgpu kernel modesetting enabled. > [ 15.760169] amdgpu: Virtual CRAT table created for CPU > [ 15.760203] amdgpu: Topology: Add CPU node > [ 15.760502] [drm] initializing kernel modesetting (BEIGE_GOBY > 0x1002:0x743F 0x148C:0x2415 0xC1). > [ 15.760519] [drm] register mmio base: 0xFB700000 > [ 15.760520] [drm] register mmio size: 1048576 > [ 15.764353] [drm] add ip block number 0 <nv_common> > [ 15.764355] [drm] add ip block number 1 <gmc_v10_0> > [ 15.764357] [drm] add ip block number 2 <navi10_ih> > [ 15.764359] [drm] add ip block number 3 <psp> > [ 15.764360] [drm] add ip block number 4 <smu> > [ 15.764361] [drm] add ip block number 5 <dm> > [ 15.764363] [drm] add ip block number 6 <gfx_v10_0> > [ 15.764364] [drm] add ip block number 7 <sdma_v5_2> > [ 15.764366] [drm] add ip block number 8 <vcn_v3_0> > [ 15.764379] resource: resource sanity check: requesting [mem > 0x00000000000c0000-0x00000000000dffff], which spans more than PCI Bus > 0000:00 [mem 0x000d0000-0x000dffff window] > [ 15.764383] caller pci_map_rom+0x83/0x220 mapping multiple BARs > [ 15.764391] amdgpu 0000:04:00.0: No more image in the PCI ROM > [ 15.764412] amdgpu 0000:04:00.0: amdgpu: Fetched VBIOS from ROM BAR > [ 15.764414] amdgpu: ATOM BIOS: 113-001-XT7 > [ 15.777550] [drm] VCN(0) decode is enabled in VM mode > [ 15.781178] amdgpu 0000:04:00.0: vgaarb: deactivate vga console > [ 15.781185] amdgpu 0000:04:00.0: amdgpu: Trusted Memory Zone (TMZ) > feature disabled as experimental (default) > [ 15.781194] amdgpu 0000:04:00.0: amdgpu: PCIE atomic ops is not supported > [ 15.781245] [drm] vm size is 262144 GB, 4 levels, block size is 9-bit, > fragment size is 9-bit > [ 15.781261] amdgpu 0000:04:00.0: amdgpu: VRAM: 4080M 0x0000008000000000 - > 0x00000080FEFFFFFF (4080M used) > [ 15.781264] amdgpu 0000:04:00.0: amdgpu: GART: 512M 0x0000000000000000 - > 0x000000001FFFFFFF > [ 15.781277] [drm] Detected VRAM RAM=4080M, BAR=256M > [ 15.781279] [drm] RAM width 64bits GDDR6 > [ 15.783108] [drm] amdgpu: 4080M of VRAM memory ready > [ 15.783112] [drm] amdgpu: 5979M of GTT memory ready. > [ 15.783133] [drm] GART: num cpu pages 131072, num gpu pages 131072 > [ 15.783255] [drm] PCIE GART of 512M enabled (table at > 0x0000008000800000). > [ 18.564918] random: crng init done > [ 19.594908] amdgpu 0000:04:00.0: amdgpu: STB initialized to 2048 entries > [ 19.595220] [drm] Loading DMUB firmware via PSP: version=0x02020020 > [ 19.595937] [drm] use_doorbell being set to: [true] > [ 19.595955] [drm] Found VCN firmware Version ENC: 1.31 DEC: 3 VEP: 0 > Revision: 2 > [ 19.595965] amdgpu 0000:04:00.0: amdgpu: Will use PSP to load VCN > firmware > [ 19.663643] amdgpu 0000:04:00.0: amdgpu: reserve 0xa00000 from > 0x80fd000000 for PSP TMR > [ 19.765435] amdgpu 0000:04:00.0: amdgpu: RAS: optional ras ta ucode is > not available > [ 19.781512] amdgpu 0000:04:00.0: amdgpu: SECUREDISPLAY: securedisplay ta > ucode is not available > [ 19.781538] amdgpu 0000:04:00.0: amdgpu: smu driver if version = > 0x0000000d, smu fw if version = 0x00000010, smu fw program = 0, version = > 0x00492400 (73.36.0) > [ 19.781544] amdgpu 0000:04:00.0: amdgpu: SMU driver if version not > matched > [ 19.781581] amdgpu 0000:04:00.0: amdgpu: use vbios provided pptable > [ 19.828182] amdgpu 0000:04:00.0: amdgpu: SMU is initialized successfully! > [ 19.828795] [drm] Display Core v3.2.281 initialized on DCN 3.0.3 > [ 19.828798] [drm] DP-HDMI FRL PCON supported > [ 19.829988] [drm] DMUB hardware initialized: version=0x02020020 > [ 19.914675] [drm] kiq ring mec 2 pipe 1 q 0 > [ 19.956011] amdgpu: HMM registered 4080MB device memory > [ 19.963868] kfd kfd: amdgpu: Allocated 3969056 bytes on gart > [ 19.963883] kfd kfd: amdgpu: Total number of KFD nodes to be created: 1 > [ 19.964255] amdgpu: Virtual CRAT table created for GPU > [ 19.964896] amdgpu: Topology: Add dGPU node [0x743f:0x1002] > [ 19.964900] kfd kfd: amdgpu: added device 1002:743f > [ 19.964919] amdgpu 0000:04:00.0: amdgpu: SE 1, SH per SE 2, CU per SH 8, > active_cu_number 16 > [ 19.964924] amdgpu 0000:04:00.0: amdgpu: ring gfx_0.0.0 uses VM inv eng 0 > on hub 0 > [ 19.964926] amdgpu 0000:04:00.0: amdgpu: ring gfx_0.1.0 uses VM inv eng 1 > on hub 0 > [ 19.964927] amdgpu 0000:04:00.0: amdgpu: ring comp_1.0.0 uses VM inv eng > 4 on hub 0 > [ 19.964929] amdgpu 0000:04:00.0: amdgpu: ring comp_1.1.0 uses VM inv eng > 5 on hub 0 > [ 19.964931] amdgpu 0000:04:00.0: amdgpu: ring comp_1.2.0 uses VM inv eng > 6 on hub 0 > [ 19.964933] amdgpu 0000:04:00.0: amdgpu: ring comp_1.3.0 uses VM inv eng > 7 on hub 0 > [ 19.964935] amdgpu 0000:04:00.0: amdgpu: ring comp_1.0.1 uses VM inv eng > 8 on hub 0 > [ 19.964936] amdgpu 0000:04:00.0: amdgpu: ring comp_1.1.1 uses VM inv eng > 9 on hub 0 > [ 19.964938] amdgpu 0000:04:00.0: amdgpu: ring comp_1.2.1 uses VM inv eng > 10 on hub 0 > [ 19.964940] amdgpu 0000:04:00.0: amdgpu: ring comp_1.3.1 uses VM inv eng > 11 on hub 0 > [ 19.964941] amdgpu 0000:04:00.0: amdgpu: ring kiq_0.2.1.0 uses VM inv eng > 12 on hub 0 > [ 19.964943] amdgpu 0000:04:00.0: amdgpu: ring sdma0 uses VM inv eng 13 on > hub 0 > [ 19.964945] amdgpu 0000:04:00.0: amdgpu: ring vcn_dec_0 uses VM inv eng 0 > on hub 8 > [ 19.966250] amdgpu 0000:04:00.0: amdgpu: Using BACO for runtime pm > [ 19.966781] [drm] Initialized amdgpu 3.57.0 20150101 for 0000:04:00.0 on > minor 0 > [ 19.975362] fbcon: amdgpudrmfb (fb0) is primary device > [ 19.975369] fbcon: Deferring console take-over > [ 19.975373] amdgpu 0000:04:00.0: [drm] fb0: amdgpudrmfb frame buffer > device So lets see what that looks like on a 6.11.0 without the nomodeset. Dave -- -----Open up your eyes, open up your mind, open up your code ------- / Dr. David Alan Gilbert | Running GNU/Linux | Happy \ \ dave @ treblig.org | | In Hex / \ _________________________|_____ http://www.treblig.org |_______/
Powered by blists - more mailing lists