search for: borowski

https://bugs.freedesktop.org/show_bug.cgi?id=79518 Priority: medium Bug ID: 79518 Assignee: nouveau at lists.freedesktop.org Summary: nouveau causes lockup and reboot on GT215 QA Contact: xorg-team at lists.x.org Severity: normal Classification: Unclassified OS: Linux (All) Reporter: kilobyte at angband.pl

...h: int lines = 32; u32 mask = (1 << lines) - 1; // 00000000 on x86 u32 mask = (1 << lines) - 1; // ffffffff on arm (32) u32 mask = (1 << lines) - 1; // 00000000 on arm64 u32 mask = (1ULL << lines) - 1; // ffffffff everywhere Signed-off-by: Adam Borowski <kilobyte at angband.pl> --- To be honest, I can't tell the difference other than UBSAN stopping its complaints, but the current code is obviously wrong. drivers/gpu/drm/nouveau/nvkm/subdev/gpio/base.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/gpu/drm/n...

On Wed, Apr 04, 2018 at 03:48:39PM +0300, Māris Nartišs wrote: > 2018-04-03 23:00 GMT+03:00, Adam Borowski <kilobyte at angband.pl>: > > In commit da5e45e619b3f101420c38b3006a9ae4f3ad19b0 > > > > yet it is still reproducible for me on 4.16-rc7 and 4.16.0, which already > > have your fix. I don't know about earlier versions -- my newer card went > > into flames ju...

On Wed, Apr 4, 2018 at 6:58 PM, Adam Borowski <kilobyte at angband.pl> wrote: > On Wed, Apr 04, 2018 at 03:48:39PM +0300, Māris Nartišs wrote: >> 2018-04-03 23:00 GMT+03:00, Adam Borowski <kilobyte at angband.pl>: >> > In commit da5e45e619b3f101420c38b3006a9ae4f3ad19b0 >> > >> > yet it is still r...

Hi! On v4.18-rc1, the mouse cursor is missing on my right monitor. Card is G98 [GeForce 8400 GS Rev. 2]. I have two monitors: one small landscape 1280x1024 on DVI-I-1 left, and one big 1600x1200 (1200x1600 portrait) on HDMI-1 right. Curiously, the cursor is missing not only with proper xrandr setup after logging in but even in mirrored mode at the lightdm greeter[1]. How is this even possible

Hi, Adam. 2018-04-03 23:00 GMT+03:00, Adam Borowski <kilobyte at angband.pl>: > Hi! > In commit da5e45e619b3f101420c38b3006a9ae4f3ad19b0 > > yet it is still reproducible for me on 4.16-rc7 and 4.16.0, which already > have your fix. I don't know about earlier versions -- my newer card went > into flames just a few days ag...

I would like to query an existing plot to learn the actual x and y limits of the plottable area. Is this possible? I can discover the extreme tick mark locations but not the actual plot area limits. Setting the limits with ylim will not help in this case because I am overplotting an existing plot with a separate function, and I don't want my end-user to have to pass parameters around.

On Mon, Jun 18, 2018 at 7:46 AM, Adam Borowski <kilobyte at angband.pl> wrote: > Hi! > On v4.18-rc1, the mouse cursor is missing on my right monitor. > Card is G98 [GeForce 8400 GS Rev. 2]. > > I have two monitors: one small landscape 1280x1024 on DVI-I-1 left, and one > big 1600x1200 (1200x1600 portrait) on HDMI-1 right...

Hi! In commit da5e45e619b3f101420c38b3006a9ae4f3ad19b0: > drm/nouveau/mmu: ALIGN_DOWN correct variable > > Commit 7110c89bb8852ff8b0f88ce05b332b3fe22bd11e ("mmu: swap out round > for ALIGN") replaced two calls to round/rounddown with ALIGN/ALIGN_DOWN, > but erroneously applied ALIGN_DOWN to a different variable (addr) and left > intended variable (tail) not

For a while we've been having issues with seemingly random interrupts coming from nvidia cards when resuming them. Originally the fix for this was thought to be just re-arming the MSI interrupt registers right after re-allocating our IRQs, however it seems a lot of what we do is both wrong and not even nessecary. This was made apparent by what appeared to be a regression in the mainline

...hem back into the packaging. I (smoke)tested the resulting packages in my test environment at work. To be able to properly test I put them in a repository at [1]. Note that I'm not a Debian Maintainer (yet). I do have packages in Debian with my work on btrfs, the uploads are sponsored by Adam Borowski. [2] I guess that it'd be good to finally take the step to apply for Debian Maintainer status when starting to work on low level security sensitive packages like this. Luckily, we have a Debian keysigning party in the next days in The Netherlands, so I have a quick opportinity to get things in...

...0437 ! Bug #670437 [pygopherd] pygopherd: unowned files after purge (policy 6.8, 10.8): /var/gopher/gophermap Changed Bug submitter to 'Andreas Beckmann <anbe at debian.org>' from 'Andreas Beckmann <debian at abeckmann.de>' > submitter 692947 ! Bug #692947 {Done: Adam Borowski <kilobyte at angband.pl>} [crawl] crawl: copyright file missing after upgrade (policy 12.5) Changed Bug submitter to 'Andreas Beckmann <anbe at debian.org>' from 'Andreas Beckmann <debian at abeckmann.de>' > submitter 659180 ! Bug #659180 {Done: Holger Levsen &l...

On Thu, Jan 25, 2018 at 06:29:53PM -0500, Lyude Paul wrote: > This was made apparent by what appeared to be a regression in the > mainline kernel that started introducing suspend/resume issues for > nouveau: > > a0c9259dc4e1 (irq/matrix: Spread interrupts on allocation) I'm just a dumb user here, but I confirm: CPU: AMD Phenom II X6 1055T, GPU: GTX 560 Ti 100% fail to

On Thu, Apr 04, 2019 at 02:12:30AM -0400, Pankaj Gupta wrote: > > All this ad hoc IS_DAX conditional logic is getting pretty nasty. > > > > xfs_file_mmap( > > .... > > { > > struct inode *inode = file_inode(filp); > > > > if (vma->vm_flags & VM_SYNC) { > > if (!IS_DAX(inode)) > > return -EOPNOTSUPP; > > if

On Thu, Apr 04, 2019 at 02:12:30AM -0400, Pankaj Gupta wrote: > > All this ad hoc IS_DAX conditional logic is getting pretty nasty. > > > > xfs_file_mmap( > > .... > > { > > struct inode *inode = file_inode(filp); > > > > if (vma->vm_flags & VM_SYNC) { > > if (!IS_DAX(inode)) > > return -EOPNOTSUPP; > > if

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: