XPS 15 9570 Owners Thread

Discussion in 'Dell XPS and Studio XPS' started by el3ctronics, May 16, 2018.

  1. kuichido

    kuichido Newbie

    Reputations:
    0
    Messages:
    5
    Likes Received:
    1
    Trophy Points:
    6
    No one tried the new bios 1.15.0?
     
  2. _sem_

    _sem_ Notebook Deity

    Reputations:
    100
    Messages:
    776
    Likes Received:
    271
    Trophy Points:
    76
    SDeP58 likes this.
  3. SDeP58

    SDeP58 Notebook Evangelist

    Reputations:
    69
    Messages:
    422
    Likes Received:
    114
    Trophy Points:
    56
  4. pedro estrela

    pedro estrela Notebook Enthusiast

    Reputations:
    10
    Messages:
    11
    Likes Received:
    15
    Trophy Points:
    6
    maffle likes this.
  5. maffle

    maffle Notebook Evangelist

    Reputations:
    153
    Messages:
    515
    Likes Received:
    454
    Trophy Points:
    76
    @pedro estrela dpc latency checker doesnt work under Windows 10, use https://www.resplendence.com/latencymon but it would be no surprise if youre right, I would totally avoid Dell laptops. The outsourced bios company making these have no idea what theyre doing. The reported issue with the c state after boot is still not fixed and I am 100% sure they dont care and wont fix it. Make a ticket at Dell about this dont post in forums. Or post at their dellcares twitter via DM. change for the 1.16.0 bios of the 9560 was the DPC """fix""" backport "Reduces Deferred Procedure Call (DPC) latency for real-time task performance enhancement, such as audio playback.", so I guess your issue starts with 1.16.0
     
    Last edited: Feb 6, 2020
  6. pedro estrela

    pedro estrela Notebook Enthusiast

    Reputations:
    10
    Messages:
    11
    Likes Received:
    15
    Trophy Points:
    6
    Thanks for your comments
    This issue was confirmed with latencymon as well. I’m aware of the constant 1ms from dpc latency checker; but we are discussing thousands of ms that are trivially visible by the user (even the mouse stops). Correlated with 200 ring -2 SMI interrupts on all cores that lock the OS.

    I did raise a ticket with dell, will tweet to dellcares as well
    Bios 1.16.0 had (regular) dpc dhanges; i not tested the previous one because i jumped directly to the one i actually had for a year (checked dell update log to find out)
     
    pressing likes this.
  7. lefti696

    lefti696 Notebook Enthusiast

    Reputations:
    7
    Messages:
    46
    Likes Received:
    12
    Trophy Points:
    16
    @maffle what is the bios verion you are using with your xps 9570? Or the best one you can recommend? Im still on 1.2.2 and I'm considering upgrade to newer version which fixes a bit DPC latency issues.
     
  8. maffle

    maffle Notebook Evangelist

    Reputations:
    153
    Messages:
    515
    Likes Received:
    454
    Trophy Points:
    76
    I am out of forced reasons on latest 1.15.0. It is kinda a pro and contra list, which I really find annoying and it shouldnt be like that. The pro part is a bit larger for going for latest bios. Yet it has some annoying contra parts, like the always spinning on fans when the dGPU was triggered, or the package c state bug. Pro is of course the better DPC latency and also the "fixed" throttle issue of the dGPU, and I wouldnt advice using older bios anymore too because of the battery swelling issue... I havent noticed a 2 second freeze using the laptop for hours. But sometimes it happens, the mouse cursor freezes for a tiny bit when there is some large work processing. I have noticed this in the past a few times.
     
    lefti696 likes this.
  9. maffle

    maffle Notebook Evangelist

    Reputations:
    153
    Messages:
    515
    Likes Received:
    454
    Trophy Points:
    76
    I think I found a fix for the CPU package c state issue, which was present since bios 1.14.0, at least for me.

    I actually remembered, that I had a similar issue before in the past with my XPS 15, that VM support was not working anymore after a bios update (had reported it here in the past too). Windows 10 said that vt-x wasnt enabled in some apps (I wasnt even aware about it just found out by random after an app reported it). I then downloaded the Intel CPU ident tool, and it also said VT-x/vt-d was off! I tried a lot to find out what was causing it (even VT support was set to enabled in bios), and in the end I found out.

    I did a "load bios defaults" in bios, set everything back to my settings, and then rebooted... and vt-x was working again!

    I just tried the same an hour ago... and CPU package c states are working again on AC and reboot! I tried rebooting several times and c states are working every time!! O M G!!!

    Fun fact: I had tried before last week going into bios and toggle c-states on/off/on with no result. I did the same before in the past with vt support... only "load bios defaults" helped. Seems there is some nasty bios bug, that some options shown in the menu are ignored or connected to the wrong internal flag value.

    I love Dell.

    @pilililo2
     
    Last edited: Feb 14, 2020
    splus, abujafar and pressing like this.
  10. pedro estrela

    pedro estrela Notebook Enthusiast

    Reputations:
    10
    Messages:
    11
    Likes Received:
    15
    Trophy Points:
    6
    UPDATE: the SMIs latency problem returned even on BIOS 0.12.1. It happens every 30minutes,

    It is perfectly correlated with DellSupportAssistRemedationService that does a full PCI inventory every 30m. Disabling this service avoids the problem (again!).


    ----
    windows_count_smi log:

    2020-02-22 13:19:28,504033800+00:00 1582377568.504033800 SMI 192
    2020-02-22 13:49:29,709938000+00:00 1582379369.709938000 SMI 192
    2020-02-22 14:19:31,464194900+00:00 1582381171.464194900 SMI 192
    2020-02-22 14:49:32,292745300+00:00 1582382972.292745300 SMI 192​

    DellSupportAssistRemedationService.log

    20-02-22 13:19:26,938 [4] [ERROR] Failed to detect audio playing. #StackInfo#
    20-02-22 13:49:28,208 [4] [ERROR] Failed to detect audio playing. #StackInfo#
    20-02-22 14:19:29,470 [4] [ERROR] Failed to detect audio playing. #StackInfo#
    20-02-22 14:49:30,732 [4] [ERROR] Failed to detect audio playing. #StackInfo#
    (the whole logs are much longer, it ran overnight)
     
Loading...

Share This Page