similar to: [Bug 30213] New: ION2 (NV50) locks up with infinite loop

Hi all - Here''s my current error handling patchset, against 3.1-rc8. Almost all of this patchset is preparing for actual error handling. Before we start in on that work, I''m trying to reduce the surface we need to worry about. It turns out that there is a ton of code that returns an error code but never actually reports an error. The patchset has grown to 65 patches. 46 of them

This fixes the following warning: drivers/virtio/virtio_ring.c:1032:5: warning: ?queue? may be used uninitialized in this function The conditions that govern when queue is set aren't apparent to gcc. Setting queue = NULL clears the warning. Signed-off-by: Jeff Mahoney <jeffm at suse.com> --- drivers/virtio/virtio_ring.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) ---

This fixes the following warning: drivers/virtio/virtio_ring.c:1032:5: warning: ?queue? may be used uninitialized in this function The conditions that govern when queue is set aren't apparent to gcc. Setting queue = NULL clears the warning. Signed-off-by: Jeff Mahoney <jeffm at suse.com> --- drivers/virtio/virtio_ring.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) ---

Hello List, i have a Samba Problem that is related to Sambas ldap behaviour. Problem: The standalone server ( no DC !!) tries to write an attribute to an write only ldap Slave is sent via WAN to the master write ldap. The problem results from the fact that samba never goes back to the "local" slave ldap to the "local" slave ldap so each samba request goes over an

V1 -> V2: Move kmalloc() before mutex_lock(), suggested by Arjan. file_remove_suid() should be called with i_mutex held, file_update_time() too. So move them after mutex_lock(). Plus, check the return value of kmalloc(). Signed-off-by: WANG Cong <amwang@redhat.com> Cc: Arjan <arjan@infradead.org> Cc: Chris Mason <chris.mason@oracle.com> Cc: Yan Zheng

http://bugs.freedesktop.org/show_bug.cgi?id=26980 Summary: GT230M/nouveau: X server hangs spontaneously Product: xorg Version: 7.5 Platform: x86-64 (AMD64) OS/Version: Linux (All) Status: NEW Severity: normal Priority: medium Component: Driver/nouveau AssignedTo: nouveau at lists.freedesktop.org

On 4/5/16 4:04 AM, Michael S. Tsirkin wrote: > On Mon, Apr 04, 2016 at 02:14:19PM -0400, Jeff Mahoney wrote: >> This fixes the following warning: >> drivers/virtio/virtio_ring.c:1032:5: warning: ?queue? may be used >> uninitialized in this function >> >> The conditions that govern when queue is set aren't apparent to gcc. >> >> Setting queue = NULL

On 4/5/16 4:04 AM, Michael S. Tsirkin wrote: > On Mon, Apr 04, 2016 at 02:14:19PM -0400, Jeff Mahoney wrote: >> This fixes the following warning: >> drivers/virtio/virtio_ring.c:1032:5: warning: ?queue? may be used >> uninitialized in this function >> >> The conditions that govern when queue is set aren't apparent to gcc. >> >> Setting queue = NULL

https://bugs.freedesktop.org/show_bug.cgi?id=30375 Summary: (NV34) X server using 100% cpu with latest nouveau.git and xf86-video-nouveau.git Product: xorg Version: git Platform: x86 (IA32) OS/Version: Linux (All) Status: NEW Severity: major Priority: medium Component: Driver/nouveau

V2 -> V3: set ''err'' to -ENOMEM when kmalloc() fails. Thanks to Tao. V1 -> V2: Move kmalloc() before mutex_lock(), suggested by Arjan. file_remove_suid() should be called with i_mutex held, file_update_time() too. So move them after mutex_lock(). Plus, check the return value of kmalloc(). Signed-off-by: WANG Cong <amwang@redhat.com> Cc: Arjan

I having been trouble by this for a few days now and was wondering if anyone else has had any luck with this? I am currently running Samba 2.2.6pre2 on FreeBSD 4.7-RELEASE I have successfully set up samba to be the PDC I am unsuccessfully trying to change the passwords on the W2k box and I am recieving the error that the user name/password are incorrect make sure the caps lock is not on. When I

Hi all - The following 9 patches add more error handling to the btrfs code: - Add btrfs_panic - Catch locking failures in {set,clear}_extent_bit - Push up set_extent_bit errors to callers - Push up lock_extent errors to callers - Push up clear_extent_bit errors to callers - Push up unlock_extent errors to callers - Make pin_down_extent return void - Push up btrfs_pin_extent errors to

https://bugs.freedesktop.org/show_bug.cgi?id=30424 Summary: Resume from suspend to ram fails on G71 [Quadro FX 1500M] (rev a1) Product: xorg Version: unspecified Platform: x86-64 (AMD64) OS/Version: Linux (All) Status: NEW Severity: major Priority: medium Component: Driver/nouveau

https://bugs.freedesktop.org/show_bug.cgi?id=28320 Summary: Xserver hangs in an infinite loop Product: xorg Version: git Platform: x86-64 (AMD64) OS/Version: Linux (All) Status: NEW Severity: major Priority: high Component: Driver/nouveau AssignedTo: nouveau at lists.freedesktop.org

http://bugs.freedesktop.org/show_bug.cgi?id=24002 Summary: PFIFO_CACHE_ERROR PGRAPH_ERROR Product: xorg Version: unspecified Platform: x86-64 (AMD64) OS/Version: Linux (All) Status: NEW Severity: normal Priority: medium Component: Driver/nouveau AssignedTo: nouveau at lists.freedesktop.org

Ladies and Gentlemen, the following piece of code causes an annoying error: > aa <- structure(list(BG = c(24, 16, 61, 30, 37, 33, 13, 4, -34, + 10, 33, 41, 6, 32, 39, 37, 36, -17, 60, 35, 22, 21, 29, 52, + 41, 62, -26, 30, -33, 27, 34, 28, 36, 29, -12, 38, 34, 32, + 40, 36, 39, 31, 19, 55, 28, 40, 38, 39, -31, 64, -22, 41, + 37, -33, 18, 31, 1, -33, 28, 36, -22), Kont =

hello, i am very new to centos and experienced some trouble yesterday when installing centos 5 onto our workgroup server. Our Server is equipped with an external RAID-array using an LSI Logic / Symbios Logic 53c1030 PCI-X Fusion-MPT Dual Ultra320 SCSI (rev 07) SCSI controller. Unfortunately the Server won't boot with the array connected, but gives the error message: target1:0:2: Domain

an error in my rails code caused the framework to send an infinite number of SQL calls to the database. I killed the webrick server, restarted postgres, deleted the /tmp file in my rails application, deleted the bad code, restarted firefox, restarted the webrick server. All to no avail. As soon as I try loading my application, the infinite recursion starts again. I can no longer work. This

Hi. I spent about 10 hours on saturday trying to understand why my blog/Typo was taking more than 500M and then crashing my server. There is a recursive function in redcloth.rb which is not written properly (a variant is in the parameters, but is not even checked. Variant is existing to be checked, not just print a debug...). Here is the patch to prevent this. Please apply them and release

FastCgiIpcDir /www/fastcgi FastCgiConfig -idle-timeout 30 I have that right in the root level of my httpd.conf (1.3) i made an inifinite loop in rails, and its not killed at all. Any ideas? ------------------------------------------------------------------------ Hunter Peress hunterp-hceJc2YFNylFcjXmduoLkw@public.gmane.org Web Programmer The Santa Fe New Mexican, Inc. www.freenewmexican.com