Bug 205545
Summary: | Linux >=5.3.11 < 5.4.0 --> i915: Resetting rcs0 for hang on rcs0 | ||
---|---|---|---|
Product: | Drivers | Reporter: | Ale (alpiturchi) |
Component: | Video(Other) | Assignee: | drivers_video-other |
Status: | RESOLVED MOVED | ||
Severity: | high | CC: | alpiturchi, hi-angel, kernel, marek.bartosiewicz, waltercool |
Priority: | P1 | ||
Hardware: | Intel | ||
OS: | Linux | ||
Kernel Version: | >=5.3.11 <5.4.0 | Subsystem: | |
Regression: | No | Bisected commit-id: |
Description
Ale
2019-11-16 09:13:34 UTC
I used git bisect from vanilla sources following this: https://wiki.gentoo.org/wiki/Kernel_git-bisect Finally I got the incriminated commit: 77fc9100fc5768ca01ca2dd2cc5a515a4723a58a is the first bad commit commit 77fc9100fc5768ca01ca2dd2cc5a515a4723a58a Author: Jon Bloomfield <jon.bloomfield@intel.com> Date: Thu Sep 27 10:23:17 2018 -0700 drm/i915/cmdparser: Use explicit goto for error paths commit 0546a29cd884fb8184731c79ab008927ca8859d0 upstream. In the next patch we will be adding a second valid termination condition which will require a small amount of refactoring to share logic with the BB_END case. Refactor all error conditions to jump to a dedicated exit path, with 'break' reserved only for a successful parse. Cc: Tony Luck <tony.luck@intel.com> Cc: Dave Airlie <airlied@redhat.com> Cc: Takashi Iwai <tiwai@suse.de> Cc: Tyler Hicks <tyhicks@canonical.com> Signed-off-by: Jon Bloomfield <jon.bloomfield@intel.com> Reviewed-by: Chris Wilson <chris.p.wilson@intel.com> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org> drivers/gpu/drm/i915/i915_cmd_parser.c | 25 +++++++++++++------------ 1 file changed, 13 insertions(+), 12 deletions(-) Prior to this the hangs does not happen. After this it hangs just opening a libreoffice document a 2-3 times This is the bisect log heavensdoor linux # git bisect log git bisect start # bad: [dada86c5aaa8f2305bf8a8bf9014b60603f9f013] Linux 5.3.11 git bisect bad dada86c5aaa8f2305bf8a8bf9014b60603f9f013 # good: [b260a0862e3a9fccdac23ec3b783911b098c1c74] Linux 5.3.10 git bisect good b260a0862e3a9fccdac23ec3b783911b098c1c74 # good: [9fd8ecf10b9cf44efc6d70791df3e1857598fb76] net: stmmac: Fix the problem of tso_xmit git bisect good 9fd8ecf10b9cf44efc6d70791df3e1857598fb76 # good: [cf0ccb042e9ea3e6a156b753292b4d3e80bfeef9] hv_netvsc: Fix error handling in netvsc_attach() git bisect good cf0ccb042e9ea3e6a156b753292b4d3e80bfeef9 # good: [7819546459c63b98fe14d43137ef8e4eebeb78f4] drm/i915: Remove Master tables from cmdparser git bisect good 7819546459c63b98fe14d43137ef8e4eebeb78f4 # bad: [981d3a01c29b03b512604f21196af3ec7a14987f] x86/speculation/taa: Add mitigation for TSX Async Abort git bisect bad 981d3a01c29b03b512604f21196af3ec7a14987f # bad: [bdb4e778f43a07e0d51354c4b9a8a17306ec4b85] drm/i915/cmdparser: Ignore Length operands during command matching git bisect bad bdb4e778f43a07e0d51354c4b9a8a17306ec4b85 # good: [41e79b82c420f88c709f53dd2f3e61e0c01d511b] drm/i915: Allow parsing of unsized batches git bisect good 41e79b82c420f88c709f53dd2f3e61e0c01d511b # bad: [77fc9100fc5768ca01ca2dd2cc5a515a4723a58a] drm/i915/cmdparser: Use explicit goto for error paths git bisect bad 77fc9100fc5768ca01ca2dd2cc5a515a4723a58a # good: [4b75b05cb098b15658a91fae3be29a58a1cfa2a1] drm/i915: Add gen9 BCS cmdparsing git bisect good 4b75b05cb098b15658a91fae3be29a58a1cfa2a1 # first bad commit: [77fc9100fc5768ca01ca2dd2cc5a515a4723a58a] drm/i915/cmdparser: Use explicit goto for error paths Problem still present in 5.3.12 Problem still present in 5.3.13 but solved somehow in 5.4.0 5.4.0 is still bad for my Skylake laptop. Keeps its Intel GPU 100% powered on and no cstates: | GPU | | | | Powered On100,0% | | RC6 0,0% | | RC6p 0,0% | | RC6pp 0,0% | I discovered that 5.4.0 now hangs the notebook completely. No logs, just freeze and a hard reset. It's a bit too much for me to debug this, so I'll stick with 5.3.10 for a while... Please, is any kernel developer watching this? (In reply to Ale from comment #5) > Please, is any kernel developer watching this? No. Please file all i915 bugs at [1]. [1] https://bugs.freedesktop.org/enter_bug.cgi?product=DRI&component=DRM/Intel (In reply to Jani Nikula from comment #6) > (In reply to Ale from comment #5) > > Please, is any kernel developer watching this? > > No. Please file all i915 bugs at [1]. > > [1] > https://bugs.freedesktop.org/enter_bug.cgi?product=DRI&component=DRM/Intel Ahem, just moved to https://gitlab.freedesktop.org/drm/intel/issues/new I think it is this one https://gitlab.freedesktop.org/drm/intel/issues/673 |