Bug#591061: Fixed upstream.

As pointed out by David Mansfield, the fix has found its way upstream: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdiff;h=1df6a2ebd75067aefbdf07482bf8e3d0584e04ee -- Eduardo. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "

Bug#591061: Patch OK.

I tried it, seems to work as well as the previous one! Regards, -- Eduardo. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#591061: Info received (Leak still present.)

The latest patch solves it! (as confirmed on RH's bugzilla). Cyril, out of curiosity: is this bug report going to remain open while the patch finds its way upstream and/or to Debian's patchset? I would like to know more about the procedure if you have any pointers and don't mind. Thanks to everyo

Bug#591061: Leak still present.

Hi Cyril, thanks for the heads up. Unfortunately I still seem to be able to leak memory in the exact same way. I'm reporting this back at RH's bugzilla. I'm attaching ttm/drm related entries in vmallocinfo just in case. -- Eduardo. vmallocinfo.20100928 Description: Binary data

Bug#591061: vmallocinfo

I'm also attaching the output of 'cat /proc/vmallocinfo' pre-trigger (at least as far as I can tell), after some scrolling and after a little extra scrolling. Seems to be grow. -- Eduardo. nox:/home/perseguidor# cat /proc/vmallocinfo |egrep '(ttm|drm)' 0xc90011093000-0xc900110a4000 69632

Bug#591061: errata

I mean "egrep '(ttm|drm)' /proc/vmallocinfo" of course. I'm attaching the full vmallocinfo now. -- Eduardo. 0xc900-0xc90020008192 hpet_enable+0x2b/0x279 phys=fed0 ioremap 0xc9003000-0xc9404000 4198400 alloc_large_system_hash+0x165/0x21b pages=1024 vma

Bug#591061: Still in 2.6.36-rc4.

And it's still in 2.6.36-rc4. I added a kfree(parser->track) in r600_cs_parser_fini in r600_cs.c as per David's suggestion without any noticeable effect. Does anyone know how could we go about debugging this? Regards, -- Eduardo. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.deb

Bug#591061: Info received (Bug#591061: libdrm-radeon1: Huge memory leak with Radeon HD 4200 while using KMS.)

Just chiming in to let you know that I've just compiled and installed 2.6.36-rc3 from upstream and the leak is definitely still here. I also added/disabled/toggled several driver settings (AccelMethod, ColorTiling, etc.) in my xorg.conf file without noticeable effects on either the visual artifact

Bug#579859: Second this.

I would also like to see Clementine in Debian. I guess it's not a trivial app to package, but if you need help I'm willing to lend a hand. -- Eduardo. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.

Bug#591061: Info received (Bug#591061: libdrm-radeon1: Huge memory leak with Radeon HD 4200 while using KMS.)

OK, not sure this is quite relevant for this bug report, but at least on a related note using unstable's libdrm-radeon1 2.4.18-6 after a while I get this is logged to dmesg and the system becomes unreachable remotely (ssh can't complete the login process, but I can execute individual commands): [2

Bug#591061: libdrm-radeon1: Huge memory leak with Radeon HD 4200 while using KMS.

Cyril Brulebois wrote: > reassign 591061 src:xserver-xorg-video-ati 1:6.13.1-2 > thanks > > Eduardo I. (06/08/2010): >> Hi Cyril, thanks for your answer. > > No problem, > >> Do you want me to try any other combination of packages? > > not yet, reassigning to

Bug#591061: libdrm-radeon1: Huge memory leak with Radeon HD 4200 while using KMS.

Hi Cyril, thanks for your answer. Just confirmed the memory leak is present using 2.4.18-6 with kernel 2.6.35. ii libdrm-radeon1 2.4.18-6 Userspace interface to radeon-specific kernel DRM services -- runtime Will try again with 2.6.32 in a co

Bug#591061: Acknowledgement (libdrm-radeon1: Huge memory leak with Radeon HD 4200 while using KMS.)

Attached is another 'free' output with absolutely nothing running (algo see 'ps auxww' output sorted by RSS). Any ideas? Thanks in advance! -- Eduardo. On Sat, Jul 31, 2010 at 12:12 PM, Debian Bug Tracking System wrote: > Thank you for filing a new Bug report with Debian. > > This is an auto

Bug#559055: Still pending.

Hi! As of March 27th 2.2 hasn't hit unstable. Judging from popcon it would seem it's a reasonably popular package (1899 installs out of 36801 installs of linux-sound-base work out to approx. 5% of the relevant installs? If I'm reading this well). Are you in need of mantainers? Thanks in advance!

Bug#535920: Solved on 2.1-1 (sid)

I concur. Just a heads up: appears to be fixed on sid (2.1-1) now. -- Eduardo. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#508009: Ongoing packaging effort?

I second this, is there an ongoing packaging effort? If there is and they happen to need help, I would like to lend a hand. -- Eduardo. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]