From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: Jani Nikula <jani.nikula@linux.intel.com>
Cc: intel-gfx@lists.freedesktop.org, "Mario Hüttel" <mario.huettel@gmx.net>
Subject: Re: [Intel-gfx] BUG in i915/i915_pci.c, commit fe0f1e3
Date: Thu, 29 Apr 2021 18:48:39 +0300 [thread overview]
Message-ID: <YIrVV4QnzDPgszvZ@intel.com> (raw)
In-Reply-To: <87o8dx33um.fsf@intel.com>
On Thu, Apr 29, 2021 at 11:13:53AM +0300, Jani Nikula wrote:
> On Wed, 28 Apr 2021, Mario Hüttel <mario.huettel@gmx.net> wrote:
> > Hi,
> >
> > yes. The bug is still present with a recent kernel.
> > I got the tip from Imre Deak to try out
> >
> > 7962893ecb853 ("drm/i915: Disable runtime power management during
> > shutdown")
> >
> > This fixes the issue for me. Do I still have to file a bug report or
> > will this patch eventually find its way upstream?
>
> That's in Linus' upstream now, but not in any release yet.
>
> Imre, Ville, should we ask for a Cc: stable?
I would say yes, unless Imre has a good reason against it.
commit fe0f1e3bfdfe ("drm/i915: Shut down displays gracefully on
reboot") seems to be in 5.11, so that's as far back it needs to
go.
>
> BR,
> Jani.
>
>
> >
> > Thanks
> > Mario
> >
> > On Mon, 2021-04-26 at 17:47 +0300, Jani Nikula wrote:
> >> On Sat, 13 Mar 2021, Mario Hüttel <mario.huettel@gmx.net> wrote:
> >> > Hello,
> >> >
> >> > I want to report a bug. I have a PC with Intel i7-6700K processor
> >> > (with
> >> > integrated graphics) and an AsRock Fatal1ty Z170 Gaming K6
> >> > mainboard. I
> >> > use the CPU's integrated graphics.
> >> > My system is Archlinux with Kernel v5.11.6.
> >> >
> >> > Using this setup, my PC works normally. However, when I shut it
> >> > down,
> >> > the power is not cut. Fans and LEDs keep spinning. I couldn't
> >> > detect
> >> > any other problem when shutting down. Drives etc. stop as expected
> >> > and
> >> > the video is blank. Even after waiting several hours, the system
> >> > doesn't power down.
> >> > I haven't yet found any other people on the internet that have the
> >> > same
> >> > bug.
> >> >
> >> > I used git bisect to find the commit that causes this behavior on
> >> > my
> >> > machine. The result is: fe0f1e3bfdfeb53e18f1206aea4f40b9bd1f291c is
> >> > the
> >> > first bad commit.
> >> >
> >> > I hope this is the correct mailing list for this issue.
> >> >
> >> > Let me know if you need more information or someone to test it.
> >>
> >> This seems to have fallen between the cracks, apologies. Is this
> >> still
> >> an issue with newer kernels? If yes, please file a bug at [1].
> >>
> >> BR,
> >> Jani.
> >>
> >>
> >> [1]
> >> https://gitlab.freedesktop.org/drm/intel/wikis/How-to-file-i915-bugs
> >>
> >
> >
>
> --
> Jani Nikula, Intel Open Source Graphics Center
--
Ville Syrjälä
Intel
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2021-04-29 15:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-13 21:26 [Intel-gfx] BUG in i915/i915_pci.c, commit fe0f1e3 Mario Hüttel
2021-04-26 14:47 ` Jani Nikula
2021-04-28 18:44 ` Mario Hüttel
2021-04-29 8:13 ` Jani Nikula
2021-04-29 15:48 ` Ville Syrjälä [this message]
2021-04-29 16:05 ` Imre Deak
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=YIrVV4QnzDPgszvZ@intel.com \
--to=ville.syrjala@linux.intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jani.nikula@linux.intel.com \
--cc=mario.huettel@gmx.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.