From: Ben Skeggs <bskeggs@redhat.com>
To: Takashi Iwai <tiwai@suse.de>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Luigi Baldoni <aloisio@gmx.com>,
linux-stable@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [4.4.70 REGRESSION] Nouveau hangs up at boot
Date: Tue, 13 Jun 2017 08:40:26 +1000 [thread overview]
Message-ID: <e88a05d9-bf79-b1a8-4b8b-2a8fc89e0da0@redhat.com> (raw)
In-Reply-To: <s5hefus3o46.wl-tiwai@suse.de>
[-- Attachment #1.1: Type: text/plain, Size: 1725 bytes --]
On 06/10/2017 06:25 AM, Takashi Iwai wrote:
> Hi,
>
> we've received a bug report about 4.4.70 kernel showing the hang up at
> boot. And, this turned out to be a regression in nouveau driver:
> https://bugzilla.suse.com/show_bug.cgi?id=1043467
>
> I provided a test kernel reverting the last five commits about
> nouveau below, and it was confirmed to work. But still not figured
> out which one actually breaks.
>
> e4add1cf6b4154804350c3385c6d447cff3570de
> drm/nouveau/tmr: handle races with hw when updating the next alarm time
> commit 1b0f84380b10ee97f7d2dd191294de9017e94d1d upstream.
>
> 9d78e40f5f41ad1db1849f8d15acbda99d0871b4
> drm/nouveau/tmr: avoid processing completed alarms when adding a new one
> commit 330bdf62fe6a6c5b99a647f7bf7157107c9348b3 upstream.
>
> 5e07724c28f4e06fe42dd5b58bb6f9dd56510567
> drm/nouveau/tmr: fix corruption of the pending list when rescheduling an alarm
> commit 9fc64667ee48c9a25e7dca1a6bcb6906fec5bcc5 upstream.
>
> 27f82df2f02688c51d2c1d9f624cc0c5b8a62661
> drm/nouveau/tmr: ack interrupt before processing alarms
> commit 3733bd8b407211739e72d051e5f30ad82a52c4bc upstream.
>
> 3819271d8a5f4c6e0c8f71c339e44e2efbe40710
> drm/nouveau/therm: remove ineffective workarounds for alarm bugs
> commit e4311ee51d1e2676001b2d8fcefd92bdd79aad85 upstream.
>
>
> Ben, is this a known problem? Or is there any fixup?
> The kernel back trace found in the bugzilla report shows the issue in
> nvkm_timer_alarm_trigger(), at least.
>
A fix (b4e382ca7586a63b6c1e5221ce0863ff867c2df6) has been submitted already.
Sorry for the trouble!
Ben.
>
> thanks,
>
> Takashi
>
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2017-06-12 22:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-09 20:25 Takashi Iwai
2017-06-12 22:40 ` Ben Skeggs [this message]
2017-06-13 6:08 ` Takashi Iwai
2017-06-13 13:32 ` Takashi Iwai
2017-06-13 14:42 ` Luigi Baldoni
2017-06-15 6:39 ` Greg Kroah-Hartman
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=e88a05d9-bf79-b1a8-4b8b-2a8fc89e0da0@redhat.com \
--to=bskeggs@redhat.com \
--cc=aloisio@gmx.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-stable@vger.kernel.org \
--cc=tiwai@suse.de \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®