[Kernel-packages] [Bug 1517142] Comment bridged from LTC Bugzilla

2016-02-08 Thread bugproxy
--- Comment From gpicc...@br.ibm.com 2016-02-08 12:08 EDT--- Thanks for adding the patch, will close the bug now. Cheers, Guilherme -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu.

[Kernel-packages] [Bug 1517142] Comment bridged from LTC Bugzilla

2016-01-28 Thread bugproxy
--- Comment From psubb...@us.ibm.com 2016-01-28 09:08 EDT--- I have tested the proposed kernel and I was able to test it without any issues... The crash was not recreated. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in

[Kernel-packages] [Bug 1517142] Comment bridged from LTC Bugzilla

2016-01-25 Thread bugproxy
--- Comment From gpicc...@br.ibm.com 2016-01-22 09:29 EDT--- Thanks very much. Do you know exactly which versions of kernels 3.19 (Vivid) and 4.2 (Wily) will contain the patch reverted, so we can test them? Cheers, Guilherme -- You received this bug notification because you are a

[Kernel-packages] [Bug 1517142] Comment bridged from LTC Bugzilla

2016-01-21 Thread bugproxy
--- Comment From gpicc...@br.ibm.com 2016-01-21 10:10 EDT--- The commit's author is not too "friendly" to the idea of reverting it. He keeps asking for more evidence that it crashes the system. We can easily reproduce it on our side, and by reverting the commit in Ubuntu source, we can

[Kernel-packages] [Bug 1517142] Comment bridged from LTC Bugzilla

2016-01-14 Thread bugproxy
--- Comment From gpicc...@br.ibm.com 2016-01-14 14:34 EDT--- (In reply to comment #14) > What kernel versions are affected ? Commit > 659743b02c411075b26601725947b21df0bb29c8. has been mainline since v3.15 Every kernel containing this commit should be affected, unfortunately. -- You

[Kernel-packages] [Bug 1517142] Comment bridged from LTC Bugzilla

2016-01-13 Thread bugproxy
--- Comment From gpicc...@br.ibm.com 2016-01-13 06:36 EDT--- (In reply to comment #12) > IBM, any updates on the recommended fix for this issue? Hello, thanks for bumping this. The fix right now is to revert the commit mentioned above: 659743b02c41 ("[SCSI] libiscsi: Reduce locking