88 snmpwalk -m+AMAVIS-MIB -M-mibs -OQ -v2c -c xxxx host. 540 - when all virus scanners failed. 1643 author address and the usual lookup rules apply (README. Ignoring previously applied (or reversed) patch. 2001 2002 2003 2004 2005 2006 2007 2008 2009 2010 2011 2012 2013 2014. 4345 4346 4347 4348 4349 4350 4351 4352 4353 4354 4355. Technical Notes. BZ#7. The be. 2iscsi driver passed a local variable in the request. All data in /proc/interrupts was correct except the device names. This update fixes the incorrect devices names in /proc/interrupts. After the file was closed, fasync. The use of the invalid file pointer could result in a deadlock on the system because the send. With this update, a release callback function has been added for the file operations in the mptctl module. However, on Red Hat Enterprise Linux 5, the waiting time to allow a full reset completion for the megaraid. The driver incorrectly recognized the controller as stalled, and, as a result, the system stalled as well. With this update, more time is given to the controller to properly restart, thus, the controller operates as expected after being reset. Once the firmware is successfully updates, reboot the system and kdump will work as expected. This could have caused the file system to become read- only or panic, and the whole system to become unstable. This update adds an extra read operation to both the cciss and hpsa drivers, with the result that commands in the completion queue are properly processed. With this update, the message context sent to the mptctl module is stored (previously, it was zeroed). When an ioctl command completes, the saved message context is used to recognize the completion of the message, thus resolving the faulty detection. With this update, the rq- > bio pointer is used only when the blk. However, write operations were not affected and were always directed to the correct disk location. With this update, the driver detects if LBA > 0xffffffff & cdb. This update resolves the lock ordering issue, and unlinked inodes are now properly deallocated under all circumstances. The driver's page tables were not set up properly on Big Endian machines, causing extended error handling (EEH) errors on Power. PC machines. With this update, the page tables are properly set up, and a system crash no longer occurs in the aforementioned case. When calling the VDSO gettimeofday() function in Red Hat Enterprise Linux 5, a missing declaration lead to a segmentation fault. With this update, the sysctl. Home; History; Annotate; Line#. 2000 2001 2002 2003 2004 2005 2006 2007 2008 2009 2010 2011 2012 2013 2014 2015 2016. 4344 4345 4346 4347 4348 4349 4350 4351. This is a discussion on Re. 2014-09-03 Christian Beier <[email protected]> * tightvnc-1.3dev5-vncviewer-alpha-cursor.patch. With this update, the GFS2 kernel properly counts all the new resource groups and fixes the statfs file correctly. Previously, when the user created a large file in GFS2, GFS2 could have run out of allocation space because it was confined to the recently- used resource groups. With this update, GFS2 uses the MRU (Most Recently Used) list instead of the list of the recently- used resource groups. The MRU list allows GFS2 to use all available resource groups and if a large span of blocks is in use, GFS2 uses allocation blocks of another resource group. This update adds multiple checks for dinode's i. Specifically, all nodes but one would hang, waiting for a particular glock. All the waiting nodes had the W (Waiting) bit set. The remaining node had the glock in the Exclusive Mode (EX) with no holder records. The race was caused by the Pending Demote bit, which could be set and then immediately reset by another process. With this update, the Pending Demote bit is properly handled, and GFS2 nodes no longer hang. This occurred because the scsi. With this update, the arrays have been added to the list, and they are now detected and operate as expected. APIC (Advanced Programmable Interrupt Controllers) and TSC (Time Stamp Counter) reads normally take longer than 1. With this update, the MAX. With this update, the wall. This could result in not up- to- date values being stored in the cache. The loop in the flush. As a result, the system could become unresponsive. With this update, the cpu mask being waited on is the same cpu mask used in the IPI call function, and the system no longer hangs. The misuse of a per- cpu flag in the bonding driver during these operations at the wrong time could lead to the detection of an invalid state in the bonding driver, triggering kernel panic. With this update, the use of the aforementioned per- cpu flag has been corrected and a kernel panic no longer occurs. This was due to an IPI- related data structure within kdump's kernel not being properly initialized, resulting in a dereference of an invalid pointer. This update addresses this issue, and the kdump kernel no longer fails upon encountering an in- flight IPI. As a result, this signed char overflow also caused the ALUA handler to incorrectly identify the AAS (Asymmetric Access State) of the specified device as well as incorrectly interpret the supported AAS of the target. With this update, the aforementioned issue has been addressed and no longer occurs. This update includes a number of fixes that address this issue. As a result, kernel panic occurred in the evdev. With this update, locking of data structures works as expected, and kernel panic no longer occurs. With this update, a check was added after the lock has been lifted in order to prevent the race and the calling of the kfree() function on an empty list. However, some functions were not grabbing the lock, causing a NULL pointer kernel panic when iscsi. With this update, the underlying source code has been modified to address this issue, and kernel panic no longer occurs. The application program waited for a FILE lock in glibc, but the lock seemed to be corrupted, which was caused by a race condition in the COW (Copy On Write) logic. With this update, the race condition was corrected and FILE lock corruption no longer occurs. This was due to faulty barrier flag setting in WRITE. With this update, this issue has been fixed, and ext. The newly calculated window size was always a multiple of the window scaling factor, however, the remaining window size was not since it depended on rcv. As a result, a window was shrunk when it was scaled down. With this update, aligning the remaining window to the window scaling factor assures a window is no longer shrunk. With this update, the underlying source code has been modified to address this issue, and a traffic flood on the network bridge no longer occurs. This occurred when the kernel merged two I/O operations for adjacent sectors which were located on different disk partitions. Two merge requests were submitted for the adjacent sectors, the first request for the second partition and the second request for the first partition, which was then merged to the first request. The first submission of the merge request incremented the in. However, at the completion of the merge request, the in. This resulted in the erroneous values displayed in the /proc/diskstats file. With this update, the merging of two I/O operations which are located on different disk partitions has been fixed and works as expected. Write operations of size smaller than wsize worked as expected. With this update, write operations of size equal to wsize now work as expected and no longer cause the NFS client to send out unnecessary RPCs. With this update, the lockd. This was due to the fact that the netdev- > trans. With this update, the aforementioned pointer has been properly updated and flapping errors no longer occur. This was due to the fact that at the end of a probe operation, the netif. With this update, the netif. The feature is disabled by default in order to not break any existing configurations. To enable the feature, please set the tunnable parameter below to 1. This was due to the lack of IPv. IPsec tunnel. With this update, IPv. IPSecv. 6 tunnel mode. However, the added check caused a kernel panic due to missing multi- node CPU topology detection on AMD CPU family 0x. To preserve backwards compatibility, the check has not been removed but is triggered only on AMD Family 1. AMD family 0x. 15 systems do not require the aforementioned check because they are not supported as 5. Xen Hypervisor hosts. For Xen Hypervisor 5. The reset vector is comprised of two 1. Instead of zeroing out 3. On some machines this overwritten memory was used during the boot process, resulting in a hang. With this update, the long data type has been changed to the unsigned 3. The Red Hat Enterprise Linux 5. The set values were not persistent. With this update, the capture values are now cached in the usb- audio driver leaving the set capture levels unchanged. If a kernel module causes the tainted status, then running the command cat /proc/modules will display a (T) next to any module that is tainting the kernel. The guest kernels now use all three zones the same way natively running kernels do. In Red Hat Enterprise Linux 5. The implication is that if an OEM configures an SCU controller to advertise different SAS addresses per PHY, but hooks up a wide target or an expander to those PHYs, libsas will only create one port. The expectation, in the “strict” case, is that this would result in a single controller multipath configuration. Multi- controller multipath should behave as a expected. This was due to a calculation bug in the get. This update fixes the calculation, and timekeeping works correctly for such virtual machines. On kernel- xen, Hypervisor trapped the aforementioned accesses and truncated them, causing the lpfc driver to fail to initialize hardware. Note that this issue was only observed when using the lpfc driver with the following parameters: Vendor. With this update, the part of the patch related to kernel- xen that was causing the failures was removed and the lpfc driver now works as expected. This was due to a PCI resource for the SR- IOV Virtual Function (vf) not being released after the hot removing, causing the memory area in the pci. With this update, when a PCIe device is removed from a system, all resources are properly released; kernel panic no longer occurs. This resulted in memory fragmentation which caused the number of network packet fragments in requests to exceed the network hardware limit. The network hardware firmware dropped the network packets exceeding this limit.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. Archives
November 2017
Categories |