similar to: [Bug 22756] New: nouveau_fence.c kernel BUG and recursive faults

http://bugs.freedesktop.org/show_bug.cgi?id=12825 Summary: TvTime shows only the upper left corner (~ 1280x1024) in Randr1.2 Product: xorg Version: unspecified Platform: x86 (IA32) OS/Version: Linux (All) Status: NEW Severity: normal Priority: medium Component: Driver/nouveau

http://bugs.freedesktop.org/show_bug.cgi?id=24830 Summary: Some characters are not drawn well, missing vertical lines with NVIDIA NV18 Product: xorg Version: unspecified Platform: x86 (IA32) OS/Version: Linux (All) Status: NEW Severity: normal Priority: medium Component: Driver/nouveau

Hi Yutani, ALTREP is part of the official R api, as illustrated by the presence of src/include/R_ext/Altrep.h. Everything declared in the header files in that directory is official API AFAIK (and I believe that is more definitive than the manuals). The documentation of ALTREP has lagged behind its implementation unfortunately, which may partially my fault for not submitting doc patches for it

Hello, I don't believe it is illegal, as ALTREP "implements an abstraction underneath the C API". And is "compatible with all code which uses the API". Please see slide deck by Gabriel Becker, with L Tierney, M Lawrence and T Kalibera. https://bioconductor.org/help/course-materials/2020/BiocDevelForum/16-ALTREP .pdf ALTREP framework implements an abstraction underneath

Thanks, Hernando, Sorry, "API" is a bit confusing term in this context, but what I want to discuss is the "API" that Writing R Extension defines as quoted in my previous email. It's probably different from an ordinary sense when we casually say "R C API". You might wonder why I care about such a difference. This is because calling a "non-API" is

Thanks for your convincing comment, but it seems the R core team has a different opinion... A few hours ago, src/include/R_ext/Altrep.h got this comment: /* Not part of the API, subject to change at any time. */ commit: https://github.com/r-devel/r-svn/commit/2059bffde642f8426d1f39ab5dd995d19a575d4d While I'm glad to see their attempt to make it clear, I'm confused. That

> On Apr 22, 2024, at 7:37 PM, Gabriel Becker <gabembecker at gmail.com> wrote: > > Hi Yutani, > > ALTREP is part of the official R api, as illustrated by the presence of > src/include/R_ext/Altrep.h. Everything declared in the header files in that > directory is official API AFAIK (and I believe that is more definitive than > the manuals). > That is not true

https://bugs.freedesktop.org/show_bug.cgi?id=79946 Priority: medium Bug ID: 79946 Assignee: nouveau at lists.freedesktop.org Summary: Segmentation violation at nouveau_fence.c Severity: minor Classification: Unclassified OS: Linux (All) Reporter: zeccav at gmail.com Hardware: x86-64 (AMD64)

Hi Tommi, Not sure if these apply here but there are a couple of outstanding locking fixes available in http://cgit.freedesktop.org/~darktama/nouveau/ -- specifically these two: http://cgit.freedesktop.org/~darktama/nouveau/commit/?id=2f3a56ad019e378a352e9cb7a559f478826f1a87 http://cgit.freedesktop.org/~darktama/nouveau/commit/?id=4179b15c6e9fcfb253e811e5477debe46c84c395 Not sure if they affect

Hello, this is quite a minor issue but as summary() is in all likelihood one of the most widely used functions in R I decided to email this list. When producing a count of missing values, summary() in English generates an unnecessary and grammatically incorrect apostrophe (NA's rather than NAs) in its table header. For example: > summary(c(1,2,NA,3,4,NA)) Min. 1st Qu. Median Mean

Writing R Extension[1] defines "API" as: Entry points which are documented in this manual and declared in an installed header file. These can be used in distributed packages and will only be changed after deprecation. But, the document (WRE) doesn't have even a single mention of ALTREP, the term "ALTREP" itself or any entry points related to ALTREP. Does this mean,

Hello, I'm seeing this warning and oops when trying to fuzz linus v4.4-rc1-290-g3ad5d7e with trinity. ------------[ cut here ]------------ WARNING: CPU: 1 PID: 4308 at drivers/gpu/drm/nouveau/nouveau_fence.c:198 nouveau_fence_context_new+0x22e/0x270() CPU: 1 PID: 4308 Comm: trinity-c19 Tainted: G B 4.4.0-rc1+ #1 Hardware name: Dell Inc. OptiPlex 990/0D6H9T, BIOS A06 07/25/2011

I have a problem in where i generate m independent draws from a binomial distribution, say draw1 = rbinom( m , size.a, prob.a ) then I need to use each draw to generate a beta distribution. So, like using a beta prior, binomial likelihood, and obtain beta posterior, m many times. I have not found out a way to vectorize draws from a beta distribution, so I have an explicit for loop

Dear group: sorry for my beginners question, but I'm rather new to R and was searching high and low without success: I have a data frame (df) with variables in the rows and observations in the columns like (the actual data frame has 15 columns and 1789 rows): early1 early2 early3 early4 early5 M386T1000 57056 55372 58012 55546 57309 M336T90 11063 10312 10674 10840 11208

I am running samba-3.0.10 on a Solaris 8 box. The server is running as a DOMAIN_MEMBER in an Active Directory Domain. It has 8G of memory and 2 cpus. The smbd processes are started from inetd.conf. Lately, the server's load has been staying very high, from 10 - 14 and the smbd processes fluctuate between 1200 and 1600. This causes performance to suffer and clients start to complain that

Starting a new thread, as I've got a lot more details now... First, I know this may be (or is even likely) something weird happening with Thunderbird, but the bottom line is, I have to find a resolution or a workaround or something, or I will be unable to pull the trigger on the server migration. It is simply unacceptable to lose ANY mails doing this. Goal: migrate mailstore from old

The Asterisk Development Team would like to announce the release of Asterisk 13.20.0. This release is available for immediate download at http://downloads.asterisk.org/pub/telephony/asterisk The release of Asterisk 13.20.0 resolves several issues reported by the community and would have not been possible without your participation. Thank you! The following issues are resolved in this release:

The Asterisk Development Team would like to announce the release of Asterisk 15.3.0. This release is available for immediate download at http://downloads.asterisk.org/pub/telephony/asterisk The release of Asterisk 15.3.0 resolves several issues reported by the community and would have not been possible without your participation. Thank you! The following issues are resolved in this release:

Signed-off-by: Maarten Lankhorst <maarten.lankhorst at canonical.com> --- src/gallium/drivers/nouveau/nouveau_fence.c | 76 ++++++++++++------------- src/gallium/drivers/nouveau/nouveau_fence.h | 22 +++++-- src/gallium/drivers/nouveau/nouveau_screen.c | 9 +++ src/gallium/drivers/nouveau/nouveau_screen.h | 14 ++--- src/gallium/drivers/nouveau/nv30/nv30_context.c | 4

There are certain queries that I can execute that will cause a completely repeatable segmentation fault at the point where the search or search_each leaves my control and goes into the ferret libraries. I tried deleting my indexes and recreating them, and even so the exact same queries seg fault repeatedly after. Usually a one character change will make them succeed. Changing away from a