Bug 92870 - GF117M nvkm_pmu_pgob fault - v4.3 regression
Summary: GF117M nvkm_pmu_pgob fault - v4.3 regression
Alias: None
Product: xorg
Classification: Unclassified
Component: Driver/nouveau (show other bugs)
Version: unspecified
Hardware: x86-64 (AMD64) Linux (All)
: medium normal
Assignee: Nouveau Project
QA Contact: Xorg Project Team
Depends on:
Reported: 2015-11-09 09:56 UTC by Wu Xiaotian
Modified: 2019-12-04 09:06 UTC (History)
1 user (show)

See Also:
i915 platform:
i915 features:

error message. (193.24 KB, image/jpeg)
2015-11-09 09:56 UTC, Wu Xiaotian
no flags Details

Description Wu Xiaotian 2015-11-09 09:56:48 UTC
Created attachment 119500 [details]
error message.

Dell notebook vostro 2421, lspci output:
    Intel Corporation 3rd Gen Core processor Graphics Controller
    NVIDIA Corporation GF117M [GeForce 610M/710M/810M/820M / GT 620M/625M/630M/720M]

When use kernel 4.2.x, all is ok.

If use kernel 4.3.x, kernel panic. Please see attachment for more message.
Comment 1 Ilia Mirkin 2015-11-09 10:11:11 UTC
Interesting. The v4.3 kernel has:

nvkm_pmu_pgob(struct nvkm_pmu *pmu, bool enable)
        if (pmu->func->pgob)
                pmu->func->pgob(pmu, enable);

But Ben's latest upstream has:

nvkm_pmu_pgob(struct nvkm_pmu *pmu, bool enable)
        if (pmu && pmu->func->pgob)
                pmu->func->pgob(pmu, enable);

And indeed it looks like the GF117 is missing a PMU definition. I have no idea why that'd be the case, but it was that way before the rewrite as well. The simplest thing is to fix up that function as above, but I think we may also want to enable the PMU on GF117.
Comment 2 Martin Peres 2019-12-04 09:06:10 UTC
-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/xorg/driver/xf86-video-nouveau/issues/232.

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.