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

2016-02-11 Thread bugproxy
--- Comment From shriy...@in.ibm.com 2016-02-12 01:54 EDT--- The fix works fine and it is verified on : 4.4.0-4-generic Ubuntu 16.04. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu.

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

2016-01-29 Thread bugproxy
--- Comment From shriy...@in.ibm.com 2016-01-29 04:46 EDT--- Also verified the same on Ubuntu 14.04.04 uname : 4.2.0-27-generic Call trace is not seen. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu.

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

2016-01-28 Thread bugproxy
--- Comment From shriy...@in.ibm.com 2016-01-29 02:24 EDT--- Verified the fix for Ubuntu Xenial 16.04. uname output : 4.3.0-7-generic dmesg : After adding FC Adapter root@alp2:~# dmesg -c [55673.527853] PCI host bridge /pci@8002020 ranges: [55673.527859] MEM

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

2016-01-11 Thread bugproxy
--- Comment From cha...@us.ibm.com 2016-01-11 10:34 EDT--- Status update: The root cause was found, and a patch is provided. The problem happens when DLPAR of PCI device is done in LPAR with no PCI devices present at boot time. When DDW is being enabled (in function query_ddw()

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

2015-12-07 Thread bugproxy
--- Comment From gpicc...@br.ibm.com 2015-12-07 21:56 EDT--- Quick update/information: I wasn't able to perform DLPAR in the way described on bug. Normally I use command-line tool called "drmgr", and even with this tool, I couldn't perform DLPAR in the usual way. I was able to add the