similar to: 5.9-rc7 oops in nvkm_udevice_info() w/ GA100

Make ga100_mc_device static as it isn't exported, to fix the following sparse warning: drivers/gpu/drm/nouveau/nvkm/subdev/mc/ga100.c:51:1: warning: symbol 'ga100_mc_device' was not declared. Should it be static? Signed-off-by: Ben Dooks <ben-linux at fluff.org> --- drivers/gpu/drm/nouveau/nvkm/subdev/mc/ga100.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git

Reviewed-by: Karol Herbst <kherbst at redhat.com> On Thu, Dec 29, 2022 at 4:52?PM Ben Dooks <ben-linux at fluff.org> wrote: > > Make ga100_mc_device static as it isn't exported, to > fix the following sparse warning: > > drivers/gpu/drm/nouveau/nvkm/subdev/mc/ga100.c:51:1: warning: symbol 'ga100_mc_device' was not declared. Should it be static? > >

Hi guys! I'm getting the following warn on 4.15-rc1, on GTX 560 Ti: [ 9.430433] nouveau 0000:01:00.0: NVIDIA GF114 (0ce000a1) ... [ 9.585172] nouveau 0000:01:00.0: bios: version 70.24.2e.00.02 ... [ 9.772204] nouveau 0000:01:00.0: fb: 1024 MiB GDDR5 [ 9.777342] ------------[ cut here ]------------ [ 9.782106] refcount_t: increment on 0; use-after-free. [ 9.787522] WARNING:

https://bugs.freedesktop.org/show_bug.cgi?id=68456 Priority: medium Bug ID: 68456 Assignee: nouveau at lists.freedesktop.org Summary: kernel NULL pointer dereference on 'modprobe nouveau' QA Contact: xorg-team at lists.x.org Severity: normal Classification: Unclassified OS: All Reporter: hpdeifel at

In nouveau_conn_reset(), if connector->state is true, __drm_atomic_helper_connector_destroy_state() will be called, but the memory pointed by asyc isn't freed. Memory leak happens in the following function __drm_atomic_helper_connector_reset(), where newly allocated asyc->state will be assigned to connector->state. So using nouveau_conn_atomic_destroy_state() instead of

Hi, any pointer on how to debug this: [ 19.741005] nouveau 0000:01:00.0: enabling device (0541 -> 0543) [ 19.741095] nouveau 0000:01:00.0: Using 32-bit DMA via iommu [ 19.741165] nouveau 0000:01:00.0: NVIDIA GP108 (138000a1) [ 19.752562] tg3 0004:01:00.0 enP4p1s0f0: renamed from eth0 [ 19.832879] [drm] Initialized ast 0.1.0 20120228 for 0005:02:00.0 on minor 0 [ 19.856391] nouveau

From: Yongxin Liu <yongxin.liu at windriver.com> [ Upstream commit 09b90e2fe35faeace2488234e2a7728f2ea8ba26 ] In nouveau_conn_reset(), if connector->state is true, __drm_atomic_helper_connector_destroy_state() will be called, but the memory pointed by asyc isn't freed. Memory leak happens in the following function __drm_atomic_helper_connector_reset(), where newly allocated

From: Yongxin Liu <yongxin.liu at windriver.com> [ Upstream commit 09b90e2fe35faeace2488234e2a7728f2ea8ba26 ] In nouveau_conn_reset(), if connector->state is true, __drm_atomic_helper_connector_destroy_state() will be called, but the memory pointed by asyc isn't freed. Memory leak happens in the following function __drm_atomic_helper_connector_reset(), where newly allocated

From: Yongxin Liu <yongxin.liu at windriver.com> [ Upstream commit 09b90e2fe35faeace2488234e2a7728f2ea8ba26 ] In nouveau_conn_reset(), if connector->state is true, __drm_atomic_helper_connector_destroy_state() will be called, but the memory pointed by asyc isn't freed. Memory leak happens in the following function __drm_atomic_helper_connector_reset(), where newly allocated

I hit this while testing HMM with nouveau on linux-5.5-rc5. I'm not a lockdep expert but my understanding of this is that an invalidation callback could potentially call kzalloc(GFP_KERNEL) which could cause another invalidation and recursively deadlock. Looking at the drivers/gpu/drm/nouveau/nvkm/ layer, I do see a number of places where GFP_KERNEL is used for allocations and I don't see

smatch reports drivers/gpu/drm/nouveau/nvkm/subdev/mc/ga100.c:51:1: warning: symbol 'ga100_mc_device' was not declared. Should it be static? ga100_mc_device is only used in ga100.c, so it should be static Signed-off-by: Tom Rix <trix at redhat.com> --- drivers/gpu/drm/nouveau/nvkm/subdev/mc/ga100.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git

I am running solaris 5.8 and do not intend to upgrade the OS. Where can I find samba v3 for the solaris 5.8 platform? I have tried the archives but there are no OS designators. kgradowski@paulstra.com

Hey, folks, I just saw Johnny mention 5.9 yesterday, and this morning, my manager tells me he got about 100 emails from somewhere about 5.9 and a CR repo. So, my questions to the team is: is there a CR repo, and is there some urgency to enabling it, or shall we just wait for the release? The *only* thing I can think of having real issues with is the newest PIV cards.... mark

Hello. I tried to install RSPython on Solaris 5.9. After compiling R with --enable-R-shlib, I try to install RSPython using "R INSTALL --clean RSPython". This led to an error complaining about missing "libutil", wich seems not to exist on Solaris. Therefore I just removed the "-lutil" entry in "configure" and tried to install again. The installation worked

After the upgrade to CentOS 5.9, all my CentOS 5 installations report only "Unmatched Entries" in the "yum" section of their daily logwatch mails. It seems the filter script /usr/share/logwatch/scripts/services/yum got broken: --------8<--------8<--------8<--------8<--------8<--------8<--------8< [root at dns01 ~]# /usr/sbin/logwatch --print --service yum

https://bugzilla.mindrot.org/show_bug.cgi?id=1845 Bug 1845 depends on bug 1878, which changed state. Bug 1878 Summary: error message in key_perm_ok should be firmer https://bugzilla.mindrot.org/show_bug.cgi?id=1878 What |Removed |Added ---------------------------------------------------------------------------- Status|CLOSED

https://bugzilla.mindrot.org/show_bug.cgi?id=1845 Bug 1845 depends on bug 1878, which changed state. Bug 1878 Summary: error message in key_perm_ok should be firmer https://bugzilla.mindrot.org/show_bug.cgi?id=1878 What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED

I installed AIM 5.9 via Wine in Ubuntu 8.04, however I'm not hearing any sound. I configured Wine to use the ALSA driver and I tested another application under Wine and the sound worked fine. Does anyone know how I might go about getting the sounds in AIM to work?

The CentOS-5.9 Packages for the i386 and x86_64 Architectures are now available via the Continuous Release (CR) Repository. The CR Announcements for CentOS-5.9 can be viewed here: http://lists.centos.org/pipermail/centos-cr-announce/2013-January/thread.html More information about the CR Repository and how to install it is available here:

From: Ralph Campbell <rcampbell at nvidia.com> [ Upstream commit cfa736f5a6f31ca8a05459b5720aac030247ad1b ] The user level OpenCL code shouldn't have to align start and end addresses to a page boundary. That is better handled in the nouveau driver. The npages field is also redundant since it can be computed from the start and end addresses. Signed-off-by: Ralph Campbell <rcampbell