Results 1 to 3 of 3

Thread: Complete freeze

  1. #1
    Join Date
    May 2015
    Location
    Italy
    Posts
    412

    Default Complete freeze

    I am experiencing total, complete freezes in my desktop pc with fully updated openSUSE Tumbleweed.
    It happens since a few days, sometimes after seconds from boot, other times after a few minutes. I have tried booting with the previous kernel (5.8.4) and in recovery mode, but the problem persists.
    I have nothing in dmesg or in other logs, but I got "lucky" yesterday: I was working in virtual terminal 1 when it froze showing this message:
    Code:
     BUG: kernel NULL pointer dereference, address: 0000000000000001
    Is it a real bug or an hardware problem? My desktop system is getting quite old...
    Here (and in my signature) you can find a few infos about it:
    Code:
     ~ > inxi
    CPU: 8-Core AMD FX-8350 (-MCP-) speed/min/max: 1404/1400/4000 MHz Kernel: 5.8.7-1-default x86_64 Up: N/A
    Mem: 2558.9/15982.1 MiB (16.0%) Storage: 642.77 GiB (58.0% used) Procs: 378 Shell: bash 5.0.18 inxi: 3.1.00
    
     ~ > inxi -G
    Graphics:  Device-1: Advanced Micro Devices [AMD/ATI] Caicos [Radeon HD 6450/7450/8450 / R5 230 OEM] driver: radeon v: kernel
    Display: x11 server: X.Org 1.20.9 driver: radeon resolution: 1920x1080~60Hz
    OpenGL: renderer: AMD CAICOS (DRM 2.50.0 / 5.8.7-1-default LLVM 10.0.1) v: 3.3 Mesa 20.1.7
    And here is the results of a few greps into my dmesg... don't know if they are relevant or not:
    Code:
     ~ > dmesg|grep -i fail
    [   21.383555] CIFS: VFS: cifs_mount failed w/return code = -2
     ~ > dmesg|grep -i error
    [    2.379049] RAS: Correctable Errors collector initialized.
    [   21.382628] CIFS: VFS: Error connecting to socket. Aborting operation.
     ~ > dmesg|grep -i warn
    [    0.029096] ACPI BIOS Warning (bug): Optional FADT field Pm2ControlBlock has valid Length but zero Address: 0x0000000000000000/0x1 (20200528/tbfadt-615)
    [    0.029099] ACPI BIOS Warning (bug): 32/64X length mismatch in FADT/Gpe0Block: 64/32 (20200528/tbfadt-564)
    [    4.271192] random: 7 urandom warning(s) missed due to ratelimiting
    [    7.874162] ACPI Warning: SystemIO range 0x0000000000000B00-0x0000000000000B08 conflicts with OpRegion 0x0000000000000B00-0x0000000000000B0F (\SOR1) (20200528/utaddress-204)
    [    7.875447] ACPI Warning: SystemIO range 0x0000000000000B00-0x0000000000000B08 conflicts with OpRegion 0x0000000000000B00-0x0000000000000B2F (\_SB.PCI0.SBRG.ASOC.SMRG) (20200528/utaddress-204)
    [    7.875453] ACPI Warning: SystemIO range 0x0000000000000B00-0x0000000000000B08 conflicts with OpRegion 0x0000000000000B00-0x0000000000000B2F (\SMRG) (20200528/utaddress-204)
    Any suggestions?

    Thank you in advance
    Cris
    Desktop: OpenSUSE Tumbleweed (x86_64) - AMD FX-8350 Eight-Core Processor, 16Gb RAM, 120GB Samsung Evo 840 SSD
    Laptop: OpenSUSE Tumbleweed (x86_64) - Thinkpad T440 - Intel i5-4210U, 12Gb RAM, 250GB Samsung EVO 750 SSD

  2. #2
    Join Date
    Oct 2014
    Location
    Switzerland
    Posts
    746

    Default Re: Complete freeze

    Quote Originally Posted by Cris70 View Post
    I am experiencing total, complete freezes in my desktop pc with fully updated openSUSE Tumbleweed.
    It happens since a few days, sometimes after seconds from boot, other times after a few minutes. I have tried booting with the previous kernel (5.8.4) and in recovery mode, but the problem persists.
    I have nothing in dmesg or in other logs, but I got "lucky" yesterday: I was working in virtual terminal 1 when it froze showing this message:
    Code:
     BUG: kernel NULL pointer dereference, address: 0000000000000001
    Is it a real bug or an hardware problem? My desktop system is getting quite old...
    Here (and in my signature) you can find a few infos about it:
    Code:
     ~ > inxi
    CPU: 8-Core AMD FX-8350 (-MCP-) speed/min/max: 1404/1400/4000 MHz Kernel: 5.8.7-1-default x86_64 Up: N/A
    Mem: 2558.9/15982.1 MiB (16.0%) Storage: 642.77 GiB (58.0% used) Procs: 378 Shell: bash 5.0.18 inxi: 3.1.00
    
     ~ > inxi -G
    Graphics:  Device-1: Advanced Micro Devices [AMD/ATI] Caicos [Radeon HD 6450/7450/8450 / R5 230 OEM] driver: radeon v: kernel
    Display: x11 server: X.Org 1.20.9 driver: radeon resolution: 1920x1080~60Hz
    OpenGL: renderer: AMD CAICOS (DRM 2.50.0 / 5.8.7-1-default LLVM 10.0.1) v: 3.3 Mesa 20.1.7
    And here is the results of a few greps into my dmesg... don't know if they are relevant or not:
    Code:
     ~ > dmesg|grep -i fail
    [   21.383555] CIFS: VFS: cifs_mount failed w/return code = -2
     ~ > dmesg|grep -i error
    [    2.379049] RAS: Correctable Errors collector initialized.
    [   21.382628] CIFS: VFS: Error connecting to socket. Aborting operation.
     ~ > dmesg|grep -i warn
    [    0.029096] ACPI BIOS Warning (bug): Optional FADT field Pm2ControlBlock has valid Length but zero Address: 0x0000000000000000/0x1 (20200528/tbfadt-615)
    [    0.029099] ACPI BIOS Warning (bug): 32/64X length mismatch in FADT/Gpe0Block: 64/32 (20200528/tbfadt-564)
    [    4.271192] random: 7 urandom warning(s) missed due to ratelimiting
    [    7.874162] ACPI Warning: SystemIO range 0x0000000000000B00-0x0000000000000B08 conflicts with OpRegion 0x0000000000000B00-0x0000000000000B0F (\SOR1) (20200528/utaddress-204)
    [    7.875447] ACPI Warning: SystemIO range 0x0000000000000B00-0x0000000000000B08 conflicts with OpRegion 0x0000000000000B00-0x0000000000000B2F (\_SB.PCI0.SBRG.ASOC.SMRG) (20200528/utaddress-204)
    [    7.875453] ACPI Warning: SystemIO range 0x0000000000000B00-0x0000000000000B08 conflicts with OpRegion 0x0000000000000B00-0x0000000000000B2F (\SMRG) (20200528/utaddress-204)
    Any suggestions?

    Thank you in advance
    Cris
    I've had a similar freeze on a desktop with a funky Nvidia driver. I can see that you have an AMD driver, I don't know if this is related but can you boot with nomodeset?

  3. #3
    Join Date
    May 2015
    Location
    Italy
    Posts
    412

    Default Re: Complete freeze

    Quote Originally Posted by SJLPHI View Post
    I've had a similar freeze on a desktop with a funky Nvidia driver. I can see that you have an AMD driver, I don't know if this is related but can you boot with nomodeset?
    Hi SJLPHI, thank you for your reply!
    After a few more tests, it seems that there is a very high chance that the problem is a faulty RAM module.

    Cris
    Desktop: OpenSUSE Tumbleweed (x86_64) - AMD FX-8350 Eight-Core Processor, 16Gb RAM, 120GB Samsung Evo 840 SSD
    Laptop: OpenSUSE Tumbleweed (x86_64) - Thinkpad T440 - Intel i5-4210U, 12Gb RAM, 250GB Samsung EVO 750 SSD

Tags for this Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •