similar to: [Bug 105626] New: BUG: unable to handle kernel NULL pointer dereference at 0000000000000040

https://bugs.freedesktop.org/show_bug.cgi?id=105174 Bug ID: 105174 Summary: [regression] BUG unable to handle kernel NULL pointer dereference in kernel 4.15.3 Product: xorg Version: unspecified Hardware: x86-64 (AMD64) OS: All Status: NEW Severity: normal Priority: medium

https://bugs.freedesktop.org/show_bug.cgi?id=105687 Bug ID: 105687 Summary: BUG: unable to handle kernel NULL pointer dereference at 0000000000000ca0 Product: xorg Version: unspecified Hardware: Other OS: All Status: NEW Severity: normal Priority: medium Component:

https://bugs.freedesktop.org/show_bug.cgi?id=86115 Bug ID: 86115 Summary: Suspend to RAM fails when using Nouveau Product: xorg Version: unspecified Hardware: Other OS: All Status: NEW Severity: normal Priority: medium Component: Driver/nouveau Assignee: nouveau at

On 14/09/2018 10:28, Ben Skeggs wrote: > On Wed, 12 Sep 2018 at 20:59, Takashi Iwai <tiwai at suse.de> wrote: >> >> When a fan is controlled via linear fallback without cstate, we >> shouldn't stop polling. Otherwise it won't be adjusted again and >> keeps running at an initial crazy pace. > Martin, > > Any thoughts on this? > > Ben. Wow,

When a fan is controlled via linear fallback without cstate, we shouldn't stop polling. Otherwise it won't be adjusted again and keeps running at an initial crazy pace. Fixes: 800efb4c2857 ("drm/nouveau/drm/therm/fan: add a fallback if no fan control is specified in the vbios") Bugzilla: https://bugzilla.suse.com/show_bug.cgi?id=1103356 Bugzilla:

https://bugs.freedesktop.org/show_bug.cgi?id=107447 Bug ID: 107447 Summary: regression in thermal management of Quadro FX 1500 Product: Mesa Version: unspecified Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: normal Priority: medium Component: Drivers/DRI/nouveau

From: Sui Jingfeng <suijingfeng at loongson.cn> Should be no functional change Cc: Jaroslav Kysela <perex at perex.cz> Cc: Takashi Iwai <tiwai at suse.com> Cc: Fred Oh <fred.oh at linux.intel.com> Cc: Pierre-Louis Bossart <pierre-louis.bossart at linux.intel.com> Cc: Kai Vehmanen <kai.vehmanen at linux.intel.com> Cc: Bjorn Helgaas <bhelgaas at

> -----Original Message----- > From: Takashi Iwai <tiwai at suse.de> > Sent: Thursday, August 15, 2019 9:57 AM > To: Alex Deucher > Cc: Karol Herbst; Limonciello, Mario; nouveau; Rafael J . Wysocki; LKML; dri-devel; > Linux ACPI Mailing List; Alex Hung; Ben Skeggs; David Airlie > Subject: Re: [Nouveau] [PATCH 1/7] Revert "ACPI / OSI: Add OEM _OSI string to >

Since the commit 742db30c4ee6 ("drm/nouveau: Add HD-audio component notifier support"), the nouveau driver notifies and pokes the HD-audio HPD and ELD via audio component, but this seems broken. The culprit is the naive assumption that crtc->index corresponds to the HDA pin. Actually this rather corresponds to the MST dev_id (alias "pipe" in the audio component framework)

Hi, the patch below fixes a possible bug accessing an uninitialized variable. The patch is to 1.1.2. Takashi --- src/metaflac/options.c-dist 2005-05-25 16:23:34.000000000 +0200 +++ src/metaflac/options.c 2005-05-25 16:23:42.000000000 +0200 @@ -555,13 +555,14 @@ FLAC__bool parse_option(int option_index FLAC__ASSERT(0 != violation); fprintf(stderr, "ERROR (--%s): malformed

Hi, the patch below fixes the wrong use of g_strconcat. It must be a typo of g_strdup_printf. Also fixed the printf format, too. Takashi --- src/plugin_xmms/http.c-dist 2005-05-25 16:14:03.000000000 +0200 +++ src/plugin_xmms/http.c 2005-05-25 16:17:30.000000000 +0200 @@ -484,7 +484,7 @@ static int http_connect (gchar *url_, gb flac_cfg.stream.use_udp_channel ? udpspace :

With lightweight desktoping, the atomic modesetting seems far from robust. BUG: unable to handle kernel NULL pointer dereference at 0000000000000021 IP: dma_fence_wait_timeout+0x36/0xf0 ... Oops: 0000 [#1] SMP Modules linked in: ... nouveau ... CPU: 0 PID: 6895 Comm: Xorg Not tainted 4.10.5-1001.fc24.x86_64 #1 ... Call Trace: drm_atomic_helper_wait_for_fences+0x48/0x120 [drm_kms_helper]

On Mon, 14 Aug 2023 16:51:08 +0200, Karol Herbst wrote: > > I've sent a patch out to address this memory corruption > https://patchwork.freedesktop.org/patch/552642/ > > It might or might not fix regressions from the original I2C fix, so > please test and report if there are remaining issues. Thanks! I'll build a test kernel and ask the reporter for testing with it.

On Wednesday, February 21, 2018 10:57:14 AM CET Rafael J. Wysocki wrote: > On Tue, Feb 20, 2018 at 10:29 PM, Bjorn Helgaas <helgaas at kernel.org> wrote: > > On Sun, Feb 18, 2018 at 09:38:32AM +0100, Lukas Wunner wrote: > >> PCI devices not bound to a driver are supposed to stay in D0 during > >> runtime suspend. > > > > Doesn't "runtime

On Thu, Aug 15, 2019 at 10:25 AM Karol Herbst <kherbst at redhat.com> wrote: > > On Thu, Aug 15, 2019 at 4:20 PM <Mario.Limonciello at dell.com> wrote: > > > > > > There are definitely going to be regressions on machines in the field with the > > > > in tree drivers by reverting this. I think we should have an answer for all of > > > those

Modernize vga_switcheroo by using a "device link" to enforce a runtime PM dependency from an HDA controller to the GPU it's integrated into. Remove thereby obsoleted code and fix a bunch of bugs. Device links were introduced in v4.10. Users might see a small power saving if the discrete GPU is in use and its HDA controller is not, because the HDA controller is now allowed to runtime

Video and input drivers Subgroups and projects on gitlab does not list modesetting DDX, presumably because it's not packaged separately from the server. Where's the right place to report a modesetting DDX bug that manifests only on an NVidia GPU? Directly against the server https://gitlab.freedesktop.org/xorg/xserver? Here are some particulars: How can I tell whether this should be

Modernize vga_switcheroo by using a device link to enforce a runtime PM dependency from an HDA controller to the GPU it's integrated into, v2. Changes since v1: - Replace patch [1/7] to use pci_save_state() / pci_restore_state() for consistency between runtime PM code path of bound and unbound devices. (Rafael, Bjorn) - Patch [5/7]: Drop an unnecessary initialization. (Bjorn) Rephrase

https://bugs.freedesktop.org/show_bug.cgi?id=86491 Bug ID: 86491 Summary: Nouveau crash when shutting down Product: xorg Version: unspecified Hardware: Other OS: All Status: NEW Severity: normal Priority: medium Component: Driver/nouveau Assignee: nouveau at

I installed the elrepo kmod-nvidia and also the nvidia-detect and modules (see below). I had X working with the 3.10 from Centos - but video was freezing. SO I thought I would try the elrepo kernel. I installed that and X does not come up? How do I re-make the nvidia module for 4.14.5 kernel? I want to make sure the kmod kernel did it. I 'm thinking it did not. lspci | grep VGA says