[Kernel-packages] [Bug 1546159] Re: ISST-LTE: high cpus number need a high crashkernel value in kdump

[Kevin W. Rudd]

*** This bug is a duplicate of bug 1560552 ***
https://bugs.launchpad.net/bugs/1560552

** This bug has been marked a duplicate of bug 1560552
   ISST-LTE: pVM:high cpus number need a high crashkernel value in kdump

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1546159

Title:
  ISST-LTE: high cpus number need a high crashkernel value in kdump

Status in linux package in Ubuntu:
  Triaged
Status in linux source package in Xenial:
  Triaged

Bug description:
  ---Problem Description---
  The kdump kernel will be booted with "maxcpus=1", so no matter how many cpus 
this system has, only one cpu will be brought up during kdump I think. But on 
LPAR thymelp2, if we allocate 40 cpus on it, then kdump works just fine with 
512M  as crashkernel value. But if we allocate 200 cpus on it, kdump fails by 
trggering OOM. It has been proved that in latter situation we need 1.5G RAM 
reserved for kdump to let it works.
   
  ---Steps to Reproduce---
   1. configure kdump with crashkernel=512M on thymelp2
  2. allcoate 40 cpus on thymelp2 and trigger kdump
  3. allocate 200 cpus on thymelp2 then do kdump again
   
  ---
  Mahesh has posted a patch upstream to provide support for nr_cpus in kdump 
kernel.
  That should take care of this problem..

  https://lists.ozlabs.org/pipermail/linuxppc-dev/2016-February/138619.html
  ---

  Heads up Canonical: We'll want this patch included as soon
  possible/practical.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1546159/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1654073] Re: Ubuntu 17.04: machine crashes with Oops in dccp_v4_ctl_send_reset while running stress-ng.

[Kevin W. Rudd]

21966978] 
dccp_transmit_skb+0x320/0x550 [dccp]
  [  237.053739] [c0377969bb90] [d0002196732c] dccp_connect+0xf4/0x1f0 
[dccp]
  [  237.053890] [c0377969bc10] [d0002e7b0320] 
dccp_v4_connect+0x308/0x400 [dccp_ipv4]
  [  237.054213] [c0377969bc90] [c0a51678] 
__inet_stream_connect+0x158/0x400
  [  237.065276] [c0377969bd20] [c0a51978] 
inet_stream_connect+0x58/0x90
  [  237.074757] [c0377969bd60] [c097eeac] SyS_connect+0x10c/0x130
  [  237.092889] [c0377969be30] [c000bd84] system_call+0x38/0xe0
  [  237.107020] Instruction dump:
  [  237.107085] 7ca82a14 f9210020 f9210028 ebdc0b98 f9210030 f9210038 f9210040 
f9210048 
  [  237.117663] 419e01c4 e86a00ae 2fa3 419e01b8 <893e02f4> e95e0060 
7c9f2378 897e0149 
  [  237.133181] ---[ end trace ef25e246c86e0bcc ]---
  [  237.133270] 
  [  237.146244] Sending IPI to other CPUs
  [  237.147330] IPI complete

  
  == Comment: #8 - Kevin W. Rudd - 2017-01-03 15:16:06 ==
  The panic happened because the control socks had been cleared:

dccp = {
  v4_ctl_sk = 0x0,
  v6_ctl_sk = 0x0
},

  dccp_v4_ctl_send_reset() ended up calling dccp_v4_route_skb() with a
  NULL ctl_sk.  Close race of some sort?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1654073/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1628230] Re: kernel BUG at /build/linux-bOHhaA/linux-4.8.0/drivers/scsi/lpfc/lpfc_sli.c

[Kevin W. Rudd]

** Package changed: ubuntu => linux (Ubuntu)

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1628230

Title:
  kernel BUG at /build/linux-
  bOHhaA/linux-4.8.0/drivers/scsi/lpfc/lpfc_sli.c

Status in linux package in Ubuntu:
  New

Bug description:
  FYI Canonical.

  Mirroring for visibility and early awareness.

  == Comment: #0 - PAVAMAN SUBRAMANIYAM - 2016-09-26 07:51:06 ==
  ---Problem Description---
  kernel BUG at 
/build/linux-bOHhaA/linux-4.8.0/drivers/scsi/lpfc/lpfc_sli.c:1326!
   
  ---uname output---
  Linux powerkvm3-lp1 4.8.0-16-generic #17-Ubuntu SMP Thu Sep 22 22:45:44 UTC 
2016 ppc64le ppc64le ppc64le GNU/Linux
   
  Machine Type = P8 
   
  ---Steps to Reproduce---
  Install a P8 Hardware with Ubuntu 16.10 OS.
  Then after upgrading to the 4.8.0-16 using apt-get distupgrade and installing 
all the packages, we try to reboot the OS to boot to then newly upgraded kernel.

  Then while booting to the HOST OS, we start getting the kernel Oops messages 
thrown in the IPMI SOL console.
   
  Stack trace output:
   [   66.779781] Call Trace:
  [   66.779807] [c01ff3b1f6a0] [c01ff3b1f6e0] 0xc01ff3b1f6e0 
(unreliable)
  [   66.779901] [c01ff3b1f6e0] [d0001b3f6490] 
__lpfc_sli_issue_iocb_s4+0x178/0x210 [lpfc]
  [   66.779995] [c01ff3b1f7b0] [d0001b402728] 
lpfc_sli_issue_abort_iotag+0x280/0x310 [lpfc]
  [   66.780100] [c01ff3b1f840] [d0001b44f74c] 
lpfc_els_abort+0x1c4/0x4c0 [lpfc]
  [   66.780194] [c01ff3b1f920] [d0001b42b950] lpfc_nlp_put+0x3c8/0x8a0 
[lpfc]
  [   66.780289] [c01ff3b1f9e0] [d0001b42e5b8] 
lpfc_nlp_not_used+0x80/0xb0 [lpfc]
  [   66.780384] [c01ff3b1fa10] [d0001b4163c4] 
lpfc_mbx_cmpl_dflt_rpi+0x14c/0x180 [lpfc]
  [   66.780484] [c01ff3b1fab0] [d0001b3fc28c] 
lpfc_sli_handle_mb_event+0x764/0x8d0 [lpfc]
  [   66.780651] [c01ff3b1fbf0] [d0001b431d48] 
lpfc_do_work+0x1100/0x1990 [lpfc]
  [   66.780815] [c01ff3b1fd80] [c00f8f90] kthread+0x110/0x130
  [   66.780952] [c01ff3b1fe30] [c0009968] 
ret_from_kernel_thread+0x5c/0x74
  [   66.78] Instruction dump:
  [   66.781183] f8010010 f821ffc1 7cbf2b78 7c7d1b78 7c9e2378 4808 e8410018 
2fbf
  [   66.781443] 419e0060 e93f00e8 7d290074 7929d182 <0b09> e89e0038 
38be0030 7fe3fb78
  [   66.781698] ---[ end trace eac3b6cbaaf48963 ]---
   
  Oops output:
   [   35.811926]  rport-3:0-4: blocked FC remote port time out: removing rport
  [   37.859913]  rport-3:0-5: blocked FC remote port time out: removing rport
  [   37.859927]  rport-4:0-5: blocked FC remote port time out: removing rport
  [   66.761353] lpfc 0004:01:00.0: 0:(0):2753 PLOGI failure DID:051900 
Status:x3/x31420002
  [   66.761491] lpfc 0004:01:00.0: 0:(0):2753 PLOGI failure DID:051F00 
Status:x3/x31420002
  [   66.763136] lpfc 0004:01:00.0: 0:(0):2753 PLOGI failure DID:051700 
Status:x3/xa0240008
  [   66.777647] kernel BUG at 
/build/linux-bOHhaA/linux-4.8.0/drivers/scsi/lpfc/lpfc_sli.c:1326!
  [   66.56] Oops: Exception in kernel mode, sig: 5 [#1]
  [   66.777806] SMP NR_CPUS=2048 NUMA PowerNV
  [   66.777857] Modules linked in: sr_mod cdrom sd_mod xhci_pci xhci_hcd 
crc32c_vpmsum lpfc usbcore be2net usb_common scsi_transport_fc tg3 ipr ptp 
pps_core
  [   66.778115] CPU: 0 PID: 951 Comm: lpfc_worker_0 Not tainted 
4.8.0-16-generic #17-Ubuntu
  [   66.778190] task: c01fec419880 task.stack: c01ff3b1c000
  [   66.778253] NIP: d0001b3f2420 LR: d0001b3f6490 CTR: 
d0001b3f6318
  [   66.778327] REGS: c01ff3b1f420 TRAP: 0700   Not tainted  
(4.8.0-16-generic)
  [   66.778401] MSR: 90010282b033 
  CR: 24000288  XER: 
  [   66.778665] CFAR: d0001b3f2404 SOFTE: 0
  GPR00: d0001b3f6490 c01ff3b1f6a0 d0001b4a6c28 c01ff1822000
  GPR04: c01fedb0f2a0 c01fec663600 0026 0040
  GPR08:  0001 d80081260040 0025
  GPR12: d0001b3f6318 c18c  
  GPR16:    
  GPR20:    c01ff18231d0
  GPR24: c01fedb0f000 c01ff3b1f8b0  c01fedb0f2a8
  GPR28:  c01ff1822000 c01fedb0f2a0 c01fec663600
  [   66.779626] NIP [d0001b3f2420] lpfc_sli_ringtxcmpl_put+0x48/0x110 
[lpfc]
  [   66.779706] LR [d0001b3f6490] __lpfc_sli_issue_iocb_s4+0x178/0x210 
[lpfc]
   

  With the previous kernel on the machine we can see all the hardware
  available.

  root@powerkvm3-lp1:~# uname -a
  Linux powerkvm3-lp1 4.8.0-15-generic #16-Ubuntu SMP Wed Sep 21 20:45:56 UTC

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1628230/+subscriptions

-- 
Mailing list: 

[Kernel-packages] [Bug 1607387] Re: lm-sensors is throwing "ERROR: Can't get value of subfeature temp1_input: I/O error" for be2net driver

[Kevin W. Rudd]

** Summary changed:

- [LTCTest][Opal][FW860] Ubuntu: lm-sensors is throwing "ERROR: Can't get value 
of subfeature temp1_input: I/O error" for be2net driver
+ lm-sensors is throwing "ERROR: Can't get value of subfeature temp1_input: I/O 
error" for be2net driver

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1607387

Title:
  lm-sensors is throwing "ERROR: Can't get value of subfeature
  temp1_input: I/O error" for be2net driver

Status in linux package in Ubuntu:
  New

Bug description:
  == Comment: #17 - Guilherme Guaglianoni Piccoli - 2016-07-27 18:49:08 ==
  Temperature and fan information from hardware are normally available to 
userspace through hwmon sysfs abstraction. In case of be2net driver, all PCI 
devices "managed" by this driver have hwmon entries, which are filled in a 
delayed workqueue on driver, every 64 seconds.

  The issue we're seeing is that the hardware temperature queries to
  devices' fw are performed only in devices which interface is up - so,
  we end up having messages like below when using the "sensors" tool
  (from lm-sensors), for example:

  be2net-pci-50100
  Adapter: PCI adapter
  ERROR: Can't get value of subfeature temp1_input: I/O error
  temp1:N/A

  
  The following upstream commit addresses this issue:

  d3480615cf ("be2net: perform temperature query in adapter regardless of its 
interface state") 
  
[https://git.kernel.org/cgit/linux/kernel/git/powerpc/linux.git/commit/?id=d3480615cf00c6f615cdb61a9d03386574b93342]

  We would like Canonical to merge this commit in the Xenial kernel.

  Thanks in advance,

  
  Guilherme

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1607387/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1602717] Re: modprobe does not honor blacklist options in kernel cmdline unless -b is used (at least on the installer)

[Kevin W. Rudd]

Sorry.  The original problem description and mirrored package may be a
bit misleading.  I believe that real issue is that the installer is
*not* using "-b", so any blacklist options passed via the kernel cmdline
are not being honored.  Tagging the package as "debian-installer" to
focus on the install-time issue of needing to be able to blacklist
modules during the install.  Passing blacklist options are reported to
work in 16.04 Pre-GA, so it appears that something changed (either in
the installer, or in modprobe handling).  But, the bottom line problem
we need to have solved is getting the installer to honor any
blacklisting passed on the cmdline.

** Package changed: linux (Ubuntu) => debian-installer (Ubuntu)

** Changed in: debian-installer (Ubuntu)
   Status: Invalid => New

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1602717

Title:
  modprobe does not honor blacklist options in kernel cmdline unless -b
  is used (at least on the installer)

Status in debian-installer package in Ubuntu:
  New

Bug description:
  == Comment: #0 - Mauricio Faria De Oliveira - 2016-07-11 18:47:59 ==
  ---Problem Description---
  modprobe does not honor blacklist options in kernel cmdline unless -b is used 
(at least on the installer)

  The modprobe.blacklist option is required as a work-around until a solution 
to a device-driver bug is found (IBM LTC bug 138273).
   
  I've gone through the code of the kmod src pkg, but didn't spot anything 
obvious.
  Passing along to the Ubuntu team.

  Contact Information = Mauricio Faria de Oliveira  / 
Lekshmi C. Pillai  

  ---Steps to Reproduce---
   Boot the installer w/ this boot/kernel cmdline option (the alias w/ dashes 
is not required, but is here just in case):
  modprobe.blacklist=scsi_dh_alua,scsi-dh-alua

  On the dialog for username/password, select Go Back, then Exit to
  shell:

  The blacklist is detected/present in the config:

  ~ # modprobe -c | grep alua
  blacklist scsi_dh_alua
  blacklist scsi-dh-alua

  But the module is insmod-ed anyway:

  ~ # modprobe -v -n scsi-dh-alua
  insmod 
/lib/modules/4.4.0-21-generic/kernel/drivers/scsi/device_handler/scsi_dh_alua.ko
 

  Unless -b is used:

  ~ # modprobe -v -n -b scsi-dh-alua
  ~ #

  Installer kernel:
  [0.00] Linux version 4.4.0-21-generic (buildd@bos01-ppc64el-017) (gcc 
version 5.3.1 20160413 (Ubuntu/IBM 5.3.1-14ubuntu2) ) #37-Ubuntu SMP Mon Apr 18 
18:30:22 UTC 2016 (Ubuntu 4.4.0-21.37-generic 4.4.6)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/1602717/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1572712] Re: console hung during Ubuntu 16.04 netboot install 4.4.0-12-generic [soft lockup]

[Kevin W. Rudd]

** Package changed: ubuntu => linux (Ubuntu)

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1572712

Title:
  console hung during Ubuntu 16.04 netboot install 4.4.0-12-generic
  [soft lockup]

Status in linux package in Ubuntu:
  New

Bug description:
  Canonical,

  FYI and reference only at this time.

  Details:
  ---Problem Description---
  IPMI Console gets hung for 15 to 30 mins, can not traverse when trying to 
install 
  latest copy of Ubuntu 16.04 on Habanero from 
http://ports.ubuntu.com/ubuntu-ports/dists/xenial/main/installer-ppc64el/current/images/netboot/ubuntu-installer/ppc64el/vmlinux
  which is 4.4.0-12-generic 
   [   36.803240] NMI watchdog: BUG: soft lockup - CPU#2 stuck for 23s! 
[swapper/2:0]
   
  ---uname output---
  4.4.0-12-generic 
   
  ---Additional Hardware Info---
  TN71-BP012  

   
  Machine Type = TN71-BP012  
   
  ---System Hang---
   we have to wait for 15 to 30 mins to regain the console access.

   
  ---Steps to Reproduce---
  use IPMI console for  petitboot on habanero, configure IP to a network 
device, make sure you have internet outbound BSO authenticated. 
  on petit shell run following commands 
  cd /tmp;
  wget 
http://ports.ubuntu.com/ubuntu-ports/dists/xenial/main/installer-ppc64el/current/images/netboot/ubuntu-installer/ppc64el/vmlinux
 ;
  wget 
http://ports.ubuntu.com/ubuntu-ports/dists/xenial/main/installer-ppc64el/current/images/netboot/ubuntu-installer/ppc64el/initrd.gz
 ;
  kexec -l /tmp/vmlinux  -i /tmp/initrd.gz  ;
  kexec -e ;

   
  Stack trace output:
   [   36.803240] NMI watchdog: BUG: soft lockup - CPU#2 stuck for 23s! 
[swapper/2:0]
  [   36.803425] Modules linked in: hid_generic(E) ast(E) i2c_algo_bit(E) 
drm_kms_helper(E) syscopyarea(E) sysfillrect(E) sysimgblt(E) fb_sys_fops(E) ttm
  ) usb_storage(E)
  [   36.803436] CPU: 2 PID: 0 Comm: swapper/2 Tainted: GE   
4.4.0-12-generic #28-Ubuntu
  [   36.803438] task: c03c8fe8e7b0 ti: c03c9753 task.ti: 
c03c9753
  [   36.803440] NIP: c0010a24 LR: c0010a24 CTR: 
c060c2f0
  [   36.803442] REGS: c03c97533510 TRAP: 0901   Tainted: GE
(4.4.0-12-generic)
  [   36.803443] MSR: 90019033   CR: 28002824  
XER: 
  [   36.803448] CFAR: c060c330 SOFTE: 1 
  [   36.803448] GPR00: c00db8b4 c03c97533790 c15a3b00 
0900 
  [   36.803448] GPR04: c03c8fef6e00 0001  
03ff 
  [   36.803448] GPR08:  c03ffb064605 0001 
0004 
  [   36.803448] GPR12: c060c2f0 cfb41300 
  [   36.803460] NIP [c0010a24] arch_local_irq_restore+0x74/0x90
  [   36.803462] LR [c0010a24] arch_local_irq_restore+0x74/0x90
  [   36.803463] Call Trace:
  [   36.803465] [c03c97533790] [c014b184] mod_timer+0x154/0x300 
(unreliable)
  [   36.803468] [c03c975337b0] [c00db8b4] queue_work_on+0x74/0xf0
  [   36.803471] [c03c975337f0] [c060c334] 
cursor_timer_handler+0x44/0x80
  [   36.803474] [c03c97533820] [c0149ebc] call_timer_fn+0x5c/0x1c0
  [   36.803476] [c03c975338b0] [c014a37c] 
run_timer_softirq+0x31c/0x3f0
  [   36.803480] [c03c97533980] [c00beaf8] __do_softirq+0x188/0x3e0
  [   36.803483] [c03c97533a70] [c00befc8] irq_exit+0xc8/0x100
  [   36.803487] [c03c97533a90] [c001f954] timer_interrupt+0xa4/0xe0
  [   36.803490] [c03c97533ac0] [c0002714] 
decrementer_common+0x114/0x180
  [   36.803494] --- interrupt: 901 at arch_local_irq_restore+0x74/0x90
  [   36.803494] LR = arch_local_irq_restore+0x74/0x90
  [   36.803497] [c03c97533db0] [c03ffc49d678] 0xc03ffc49d678 
(unreliable)
  [   36.803502] [c03c97533dd0] [c0900708] 
cpuidle_enter_state+0x1a8/0x410
  [   36.803504] [c03c97533e30] [c0119898] call_cpuidle+0x78/0xd0
  [   36.803506] [c03c97533e70] [c0119c6c] 
cpu_startup_entry+0x37c/0x490
  [   36.803509] [c03c97533f30] [c004565c] 
start_secondary+0x33c/0x360
  [   36.803511] [c03c97533f90] [c0008b6c] 
start_secondary_prolog+0x10/0x14
  [   36.803512] Instruction dump:
  [   36.803514] 994d02ca 2fa3 409e0024 e92d0020 61298000 7d210164 38210020 
e8010010 
  [   36.803517] 7c0803a6 4e800020 6042 4bff17ad <6000> 4be4 
6042 e92d0020 
  [   57.811232] INFO: rcu_sched self-detected stall on CPU
  [   57.811236]  2-...: (1 GPs behind) idle=913/2/0 softirq=1849/1979 fqs=5229 
  [   57.811238]   (t=5250 jiffies g=-114 c=-115 q=1)
  [   57.811242] Task dump for CPU 2:
  [   57.811243] swapper/2   R  running task0 0  1 
0x0804
  [   57.811246] Call Trace:
  [   57.811248] [c03c97532fe0] [c00fb8c0] 
sched_show_task+0xe0/0x180 (unreliable)
  [   

[Kernel-packages] [Bug 1572624] Re: Backport patch to abort syscalls in active transactions

[Kevin W. Rudd]

** Package changed: ubuntu => linux (Ubuntu)

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1572624

Title:
  Backport patch to abort syscalls in active transactions

Status in linux package in Ubuntu:
  New

Bug description:
  == Comment: #0 - Tulio Magno Quites Machado Filho - 2016-02-23 12:47:09 ==
  ---Problem Description---
  This is happening on Ubuntu 14.04.3.
  User is creating stack structure using C++ transactional memory extension:

  int Pop(int)
  {
  int ret = 0;
  __transaction_atomic
  {
  if(!stack_.empty())
  {
  ret = stack_.top();
  stack_.pop();
  } else
  ret = -1;
  }
  return ret;
  }

  While evaluating if(!stack_.empty()), this code calls a libitm function (GCC 
code), which calls malloc (glibc code) which ends up calling futex (a syscall).
  A syscall inside a transaction is forbidden by the kernel, but there is 
nothing the user can do to avoid this syscall.

  This will hang the user application inside the malloc(), which would
  be waiting for the futex to return.

  Ubuntu 14.04 provides glibc 2.19, which is too old to know about HTM.
  And this is probably happening with other libraries as well.

  Backporting commit b4b56f9e would solve this issue.

  ---uname output---
  Linux 3.13.0-66-generic #108-Ubuntu SMP Wed Oct 7 16:06:09 UTC 2015 ppc64le 
ppc64le ppc64le GNU/Linux
   
  ---Steps to Reproduce---
   Start a transaction, make a syscall.
   
  == Comment: #1 - Wei Guo - 2016-02-24 02:33:03 ==
  I already verfied that kernel with patch b4b56f9e (on Ubuntu14.04) will work.

  == Comment: #2 - Wei Guo - 2016-02-26 04:20:37 ==
  Backport patch for commit b4b56f9e is attached. The patch is based on tag 
Ubuntu-lts-3.19.0-25.26_14.04.1.

  Tested based on Ubuntu 14.04.4 LTS ( 3.19.0-25-generic).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1572624/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1568952] Re: ISST-LTE:pVM:thymelp2:ubuntu 16.04: change "maxcpus=1" to "nr_cpus=1" in kdump-tools

[Kevin W. Rudd]

** Package changed: ubuntu => makedumpfile (Ubuntu)

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to makedumpfile in Ubuntu.
https://bugs.launchpad.net/bugs/1568952

Title:
  ISST-LTE:pVM:thymelp2:ubuntu 16.04: change "maxcpus=1" to "nr_cpus=1"
  in kdump-tools

Status in makedumpfile package in Ubuntu:
  New

Bug description:
  == Comment: #0 - Ping Tian Han - 2016-04-07 23:04:30 ==
  ---Problem Description---
  Because canonical  has fixed bug 137281 ( LP: #1560552 ) in 4.4.0-17-generic, 
the kernel now supports "nr_cpus=1". So we should update the "maxcpus=1" to 
"nr_cpus=1" in /etc/default/kdump-tools I think.
   
  ---uname output---
  Linux thymelp2 4.4.0-17-generic #33-Ubuntu SMP Tue Mar 29 17:15:31 UTC 2016 
ppc64le ppc64le ppc64le GNU/Linux
   
  Userspace tool: kdump-tools  version 1:1.5.9-5 

  == Comment: #2 - Hari Krishna Bathini - 2016-04-11 04:36:14 ==
  (In reply to comment #1)
  > Hari.
  > 
  > Would you please validate that nr_cpus is consistent across architectures
  > and should become the new default?
  > 
  > Thanks.

  Hi Kevin,

  I know nr_cpus=1 is supported on x86 based on this patch
  
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=14cb6dcf0a023f5977461c94d8d5a163c937979b

  About other architectures, I am not really sure.

  But looking at the kdump-tools source package, it seems like other 
architectures
  are using maxcpus=1 to boot kdump kernel unless there is architecture specific
  overrides that are missing in the source. Canonical might be able to answer 
better.

  If other aren't using or willing to use nr_cpus=1, we may need a patch
  of this kind:

  diff --git a/kdump-config b/kdump-config
  index 0ff0e6f..aba300e 100755
  --- a/kdump-config
  +++ b/kdump-config
  @@ -48,7 +48,11 @@ KDUMP_COREDIR=${KDUMP_COREDIR:=/var/crash}
   KDUMP_DUMP_DMESG=${KDUMP_DUMP_DMESG:=1}
   KDUMP_DIR="/var/lib/kdump"
   MAKEDUMP_ARGS=${MAKEDUMP_ARGS:="-c -d 31"}
  -KDUMP_CMDLINE_APPEND=${KDUMP_CMDLINE_APPEND:="irqpoll maxcpus=1 nousb 
systemd.unit=kdump-tools.service"}
  +if [ "$ARCH" = "ppc64le" ]; then
  +   KDUMP_CMDLINE_APPEND=${KDUMP_CMDLINE_APPEND:="irqpoll nr_cpus=1 nousb 
systemd.unit=kdump-tools.service"}
  +else
  +   KDUMP_CMDLINE_APPEND=${KDUMP_CMDLINE_APPEND:="irqpoll maxcpus=1 nousb 
systemd.unit=kdump-tools.service"}
  +fi
   KDUMP_KERNEL_HOOK="/etc/kernel/postinst.d/kdump-tools"
   [ -d $KDUMP_COREDIR ] || mkdir -p $KDUMP_COREDIR ;

  == Comment: #4 - Kevin W. Rudd - 2016-04-11 11:08:16 ==
  Mirroring to Canonical for their review and feedback.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1568952/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1566400] Re: Ubuntu 16.04 testing with PMC 12GB Series 8 adapter with MaxView RAID Migration deletes the RAID array.

[Kevin W. Rudd]

** Package changed: ubuntu => linux (Ubuntu)

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1566400

Title:
  Ubuntu 16.04 testing with PMC 12GB Series 8 adapter with MaxView RAID
  Migration deletes the RAID array.

Status in linux package in Ubuntu:
  New

Bug description:
   State: Open by: nauahmed on 17 March 2016 16:09:48 

  Hi,

  While using MaxView Storage Manager on Ubuntu 16.04 
  from 
https://w3-connections.ibm.com/communities/service/html/communitystart?communityUuid=7bb2d98d-64aa-437d-863e-db67dc1f50db
  
https://w3-connections.ibm.com/wikis/home?lang=en-us#!/wiki/W6ee916ce65bf_4973_a6c3_a0f025d8acc6/page/PMC%20Adapter%20Series%207%20and%20Series%208%20Code%20Deliveries

  PostGA_2.zip
  https://w3-connections.ibm.com/files/form/anonymous/api/library/c5f8d539
  -710e-4e26-9d2f-5073644c8c67/document/f9b22e38-4b5e-46ab-94ca-
  f5cb80b9e13d/media/PostGA_2.zip

  with Expand/Migrate Logical Drive option in web GUI menu.
  whole array is lost. 

  Steps:
  1> INITIALIZE ALL disks # arcconf task start 1 device all INITIALIZE noprompt

  Controllers found: 1
  Initializing Channel 0, Device 9.
  Initializing Channel 0, Device 12.
  Initializing Channel 0, Device 13.
  Initializing Channel 0, Device 14.
  4 device(s) initialized.

  Command completed successfully.

  2> Login to Web gui of MSM.. 
  clink on controller --> create logical device ---> custom mode -->RAID 1  
Mirroring; 2 drives required; redundant ---> select minimum two drives ---> 
next ---> finish. 

  3> Click on new logical raid1 device, click expand/migrate logical
  device

  RAID1
  Select a RAID level and click 'Next' to continue
Select raid Level
RAID Members
Set Attributes
Summary
RAID 1  Mirroring,2 drives required, redundant
RAID 5  Striping with parity,3 or more drives required, redundant
Simple Volume   A single drive segment,not redundant 

  Select RAID5, add additional drive, next, Finish,

  Existing RAID 1 logical device is lost.. there is no migration <-- ALL
  data lost...

  root@p7pran04:~# uname -a
  Linux p7pran04 4.4.0-12-generic #28-Ubuntu SMP Wed Mar 9 00:40:38 UTC 2016 
ppc64le ppc64le ppc64le GNU/Linux
  root@p7pran04:~# arcconf getversion
  Controllers found: 1
  Controller #1
  ==
  Firmware   : 7.8-0 (32968)
  Staged Firmware: 7.8-0 (32968)
  BIOS   : 7.8-0 (32968)
  Driver : 1.2-1 (41010)
  Boot Flash : 7.8-1 (32968)
  CPLD (Load version/ Flash version) : 5/ 10
  SEEPROM (Load version/ Flash version)  : 1/ 1
  root@p7pran04:~# modinfo aacraid
  filename:   
/lib/modules/4.4.0-12-generic/kernel/drivers/scsi/aacraid/aacraid.ko
  version:1.2-1[41010]-ms
  license:GPL
  description:Dell PERC2, 2/Si, 3/Si, 3/Di, Adaptec Advanced Raid Products, 
HP NetRAID-4M, IBM ServeRAID & ICP SCSI driver
  author: Red Hat Inc and Adaptec
  srcversion: FE59F41215F9D0437EA29CE
  alias:  pci:v9005d028Fsv*sd*bc*sc*i*
  alias:  pci:v9005d028Dsv*sd*bc*sc*i*
  alias:  pci:v9005d028Csv*sd*bc*sc*i*
  alias:  pci:v9005d028Bsv*sd*bc*sc*i*
  alias:  pci:v9005d0288sv*sd*bc*sc*i*
  alias:  pci:v9005d0286sv*sd*bc*sc*i*
  alias:  pci:v9005d0285sv*sd*bc*sc*i*
  alias:  pci:v9005d0285sv17AAsd*bc*sc*i*
  alias:  pci:v9005d0285sv1028sd*bc*sc*i*
  alias:  pci:v1011d0046sv103Csd10C2bc*sc*i*
  alias:  pci:v1011d0046sv9005sd1364bc*sc*i*
  alias:  pci:v1011d0046sv9005sd0364bc*sc*i*
  alias:  pci:v1011d0046sv9005sd0365bc*sc*i*
  alias:  pci:v9005d0285sv1028sd0287bc*sc*i*
  alias:  pci:v9005d0286sv9005sd02A2bc*sc*i*
  alias:  pci:v9005d0285sv9005sd029Abc*sc*i*
  alias:  pci:v9005d0285sv9005sd0299bc*sc*i*
  alias:  pci:v9005d0285sv9005sd0298bc*sc*i*
  alias:  pci:v9005d0286sv1014sd9540bc*sc*i*
  alias:  pci:v9005d0286sv1014sd9580bc*sc*i*
  alias:  pci:v9005d0285sv1014sd0312bc*sc*i*
  alias:  pci:v9005d0285sv1014sd02F2bc*sc*i*
  alias:  pci:v9005d0285sv9005sd0297bc*sc*i*
  alias:  pci:v9005d0285sv9005sd0296bc*sc*i*
  alias:  pci:v9005d0285sv103Csd3227bc*sc*i*
  alias:  pci:v9005d0285sv9005sd0294bc*sc*i*
  alias:  pci:v9005d0285sv9005sd0293bc*sc*i*
  alias:  

[Kernel-packages] [Bug 1564487] Re: ISST-LTE:pVM:thymelp2:ubuntu 16.04: cannot analyse vmcore with crash (s390x, ppc64)

[Kevin W. Rudd]

** Package changed: ubuntu => crash (Ubuntu)

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to crash in Ubuntu.
https://bugs.launchpad.net/bugs/1564487

Title:
  ISST-LTE:pVM:thymelp2:ubuntu 16.04: cannot analyse vmcore with crash
  (s390x, ppc64)

Status in crash package in Ubuntu:
  New

Bug description:
  == Comment: #0 - Ping Tian Han - 2016-03-31 02:19:27 ==
  ---Problem Description---
  With the kexec-tools comes from 
https://bugzilla.linux.ibm.com/show_bug.cgi?id=136588#c58 , we have dumpped a 
vmcore for bug 139815 after quiting from xmon. But when trying to analyse with 
crash:

  % sudo crash /usr/lib/debug/boot/vmlinux-4.4.0-15-generic
  /var/crash/201603310043/dump.201603310043

  crash 7.1.4
  Copyright (C) 2002-2015  Red Hat, Inc.
  Copyright (C) 2004, 2005, 2006, 2010  IBM Corporation
  Copyright (C) 1999-2006  Hewlett-Packard Co
  Copyright (C) 2005, 2006, 2011, 2012  Fujitsu Limited
  Copyright (C) 2006, 2007  VA Linux Systems Japan K.K.
  Copyright (C) 2005, 2011  NEC Corporation
  Copyright (C) 1999, 2002, 2007  Silicon Graphics, Inc.
  Copyright (C) 1999, 2000, 2001, 2002  Mission Critical Linux, Inc.
  This program is free software, covered by the GNU General Public License,
  and you are welcome to change it and/or distribute copies of it under
  certain conditions.  Enter "help copying" to see the conditions.
  This program has absolutely no warranty.  Enter "help warranty" for details.

  GNU gdb (GDB) 7.6
  Copyright (C) 2013 Free Software Foundation, Inc.
  License GPLv3+: GNU GPL version 3 or later 
  This is free software: you are free to change and redistribute it.
  There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
  and "show warranty" for details.
  This GDB was configured as "powerpc64le-unknown-linux-gnu"...

  please wait... (gathering module symbol data)
  crash: invalid structure member offset: module_num_symtab
 FILE: kernel.c  LINE: 3450  FUNCTION: module_init()

  [/usr/bin/crash] error trace: 1008af0c => 10124250 => 10179bd0 =>
  10083378

10083378: (undetermined)
10179bd0: OFFSET_verify+80
10124250: module_init+1104
1008af0c: main_loop+764

  %

  == Comment: #4 - Hari Krishna Bathini - 2016-03-31 08:20:39 ==
  (In reply to comment #2)
  > Hi, 
  > 
  > Crash failing with 4.4+ kernels is a known issue which is fixed by the
  > upstream patch 
  > 
  > commit 6f1f78e33474d00d5f261d7ed9d835c558b34d61
  > Author: Dave Anderson 
  > Date:   Wed Jan 20 09:56:36 2016 -0500
  > 
  > Fix for the changes made to the kernel module structure introduced by
  > this kernel commit for Linux 4.5 and later kernels:
  > 
  >   commit 7523e4dc5057e157212b4741abd6256e03404cf1
  >   module: use a structure to encapsulate layout.
  > 
  > Without the patch, the crash session fails during initialization
  > with the error message: "crash: invalid structure member offset:
  > module_init_text_size".
  > (seb...@linux.vnet.ibm.com)
  > 

  We also need the below upstream patch along with the patch mentioned
  above to fix this issue

  commit 098cdab16dfa6a85e9dad2cad604dee14ee15f66
  Author: Dave Anderson 
  Date:   Fri Feb 12 14:32:53 2016 -0500

  Fix for the changes made to the kernel module structure introduced by
  this kernel commit for Linux 4.5 and later kernels:
  
commit 8244062ef1e54502ef55f54cced659913f244c3e
modules: fix longstanding /proc/kallsyms vs module insertion race.
  
  Without the patch, the crash session fails during initialization
  with the error message: "crash: invalid structure member offset:
  module_num_symtab".
  (ander...@redhat.com)

  Thanks
  Hari

  == Comment: #9 - Hendrik Brueckner - 2016-03-31 11:47:13 ==
  Problem also exists on s390x:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/crash/+bug/1564487/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1560514] Re: Predictable naming mechanism is leading to issues in DLPAR operations of NICs

[Kevin W. Rudd]

** Package changed: ubuntu => linux (Ubuntu)

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1560514

Title:
  Predictable naming mechanism is leading to issues in DLPAR operations
  of NICs

Status in linux package in Ubuntu:
  New

Bug description:
  Recent kernels are using predictable naming for network interfaces, so
  the network stack is more tied to PCI naming. This can be a problem in
  hotplug scenarios, because PCI addresses will change if devices are
  removed and then re-added. This situation seems unusual, but it can
  happen if a user wants to replace a NIC without rebooting the machine,
  for example.

  The patch attached here should deal with this situation, since it makes 
PHB/domain number fixed based on device-tree properties.
   
  The problem can be reproduced by removing and re-adding a PCI network 
adapter, so its address will change and, per predictable naming scheme, so is 
the interface name.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1560514/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1558624] Re: s390/pci: backport upstream commits since v4.4

[Kevin W. Rudd]

** Package changed: ubuntu => linux (Ubuntu)

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1558624

Title:
  s390/pci: backport upstream commits since v4.4

Status in linux package in Ubuntu:
  New

Bug description:
  == Comment: #0 - Hendrik Brueckner - 2016-03-17 09:22:19 ==
  Could you backport the following PCI related upstream commits since v4.4

  69eea95c48857c9dfcac120d6acea43027627b28 s390/pci_dma: fix DMA table 
corruption with > 4 TB main memory
  bdb97e91e0140230bda9a83f6dbaa29b0c2e0522 [s390] page_to_phys() always returns 
a multiple of PAGE_SIZE
  9e00caaea14b90a788c17a2e0c32108a3d7008ec s390/pci: provide ZPCI_ADDR macro
  bf19c94d5caa100f22c20d756c57e3550c01cdb8 s390/pci: improve ZPCI_* macros
  c506fff3d3a8a632e8eb2270680548ec415f0357 s390/pci: resize iomap
  c0cabaddeeeab13db8ef4e275ab5c7c0e8746324 s390/pci: fix bar check
  8ead7efb6379354d0d31efb39342f4399c87cb67 s390/pci: set error state for 
unusable functions
  f5e44f82c1848d8e55fb0061308f14c0884e5483 s390/pci: remove iomap sanity checks
  9a99649f2a89fdfc9dde5d5401675561567bf99a s390/pci: remove pdev pointer from 
arch data
  988b86e69ded17f0f1209fd3ef1c4c7f1567dcc1 s390/pci: add ioctl interface for CLP

  
  Note that there is already a separate LaunchPad open to backport
  80c544ded25ac14d7cc3e555abb8ed2c2da99b84 s390/pci: enforce fmb page boundary 
rule

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1558624/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1558625] Re: s390/pci: enforce fmb page boundary rule

[Kevin W. Rudd]

** Package changed: ubuntu => linux (Ubuntu)

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1558625

Title:
  s390/pci: enforce fmb page boundary rule

Status in linux package in Ubuntu:
  New

Bug description:
  == Comment: #0 - Helmut Grauer - 2016-03-17 02:18:56 ==
  Hi,

  PCI ROCE test running int a kernel panic please pickup this
  upstreamfix for  Ubuntu driver when available

  upstream via:

  commit 80c544ded25ac14d7cc3e555abb8ed2c2da99b84
  Author: Sebastian Ott 
  Date:   Mon Mar 14 15:47:23 2016 +0100

  s390/pci: enforce fmb page boundary rule
  
  The function measurement block must not cross a page boundary. Ensure
  that by raising the alignment requirement to the smallest power of 2
  larger than the size of the fmb.
  
  Fixes: d0b088531 ("s390/pci: performance statistics and debug 
infrastructure")
  Cc: sta...@vger.kernel.org # v3.8+
  Signed-off-by: Sebastian Ott 
  Signed-off-by: Martin Schwidefsky 

  
  Thanks
  Helmut

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1558625/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1557751] Re: makedumpfile generates kernel version error

[Kevin W. Rudd]

** Package changed: ubuntu => makedumpfile (Ubuntu)

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to makedumpfile in Ubuntu.
https://bugs.launchpad.net/bugs/1557751

Title:
  makedumpfile generates kernel version error

Status in makedumpfile package in Ubuntu:
  New

Bug description:
  == Comment: #7 - Vaishnavi Bhat  - 2016-03-15 06:16:53 ==
  The following warning is generated by makedumpfile 
  * running makedumpfile --dump-dmesg /proc/vmcore 
/mnt/201602030129/dmesg.201602030129
  The kernel version is not supported.
  The created dumpfile may be incomplete.

  The makedumpfile version on your machine is 
  # makedumpfile -v
  makedumpfile: version 1.5.5 (released on 18 Dec 2013)

  I did a #sudo apt-get source makedumpfile and checked for the sources. 
  In the makedumpfile.h ,  the LATEST_VERSION is set to
  #define OLDEST_VERSION  KERNEL_VERSION(2, 6, 15)/* linux-2.6.15 */
  #define LATEST_VERSION  KERNEL_VERSION(4, 1, 0)/* linux-4.1.0 */
  where as kernel version on the machine is 
  # uname -r
  4.2.0-27-generic

  Hence we see this mismatch and message as "The kernel version is not
  supported."

  We need canonical to change the value of LATEST_VERSION  so that we do
  not see this message.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1557751/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1555344] Re: s390/cpumf: Fix lpp detection

[Kevin W. Rudd]

** Package changed: ubuntu => linux (Ubuntu)

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1555344

Title:
  s390/cpumf: Fix lpp detection

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  == Comment: #0 - Hendrik Brueckner - 2016-03-09 10:54:54 ==
  Please backport 

  
http://git.kernel.org/cgit/linux/kernel/git/s390/linux.git/commit/?h=fixes=7a76aa95f6f6682db5629449d763251d1c9f8c4e

  The patch is currently in the s390 tree queued for the next merge
  window.  I will attach a patch for convenience.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1555344/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1552788] Re: network lost after large number of reboots

[Kevin W. Rudd]

** Package changed: ubuntu => linux (Ubuntu)

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1552788

Title:
  network lost after large number of reboots

Status in linux package in Ubuntu:
  New

Bug description:
  ---Problem Description---
  network lost after large number of reboots (>500)
   
  Contact Information = pschm...@de.ibm.com 
   
  ---uname output---
  Linux s8330025 4.4.0-2-generic #16-Ubuntu SMP Thu Jan 28 15:44:18 UTC 2016 
s390x s390x s390x GNU/Linux
   
  Machine Type = s390 z/VM Guest 
   
  ---Steps to Reproduce---
   reboot z/VM guest several times >500. After a large number of reboots the 
network interfaces doesn't come up any more. The z/VM guest boots fine, unless 
the missing network. Impossible to bring up network again manually.

  ==

  Further debug shows that it is the "ip link set enccw0.0.f5f0 up" that
  is failing with "RTNETLINK answers: Operation not permitted".  Looking
  for further debug assistance in determining why the CAP_NET_ADMIN
  check for the root user running ip might be failing.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1552788/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1546145] Re: Surelock-GA2:kernel panic @ cxl_configure_adapter+0x418/0x8b0

[Kevin W. Rudd]

Test worked fine in below level.

Kernel Level:
---
Linux p8tul13-lp1 4.2.0-32-generic #37-Ubuntu SMP Fri Feb 26 02:20:27 UTC 2016 
ppc64le ppc64le ppc64le GNU/Linux
ii  linux-generic 4.2.0.32.35   
   ppc64el  Complete Generic Linux kernel and headers
ii  linux-headers-4.2.0-324.2.0-32.37   
   all  Header files related to Linux kernel version 4.2.0
ii  linux-headers-4.2.0-32-generic4.2.0-32.37   
   ppc64el  Linux kernel headers for version 4.2.0 on PowerPC 64el SMP
ii  linux-headers-generic 4.2.0.32.35   
   ppc64el  Generic Linux kernel headers
ii  linux-image-4.2.0-32-generic  4.2.0-32.37   
   ppc64el  Linux kernel image for version 4.2.0 on PowerPC 64el SMP
ii  linux-image-extra-4.2.0-32-generic4.2.0-32.37   
   ppc64el  Linux kernel extra modules for version 4.2.0 on PowerPC 64el SMP
ii  linux-image-generic   4.2.0.32.35   
   ppc64el  Generic Linux kernel image

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1546145

Title:
  Surelock-GA2:kernel panic @ cxl_configure_adapter+0x418/0x8b0

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Wily:
  Fix Committed
Status in linux source package in Xenial:
  Fix Released

Bug description:
  == Comment: #18 - Andrew Donnellan - 2016-02-15 20:17:01 ==
  Canonical kernel team - please apply 1bc74f1ccd457832dc515fc1febe6655985fdcd2 
from the powerpc-fixes tree.

  
https://git.kernel.org/cgit/linux/kernel/git/powerpc/linux.git/commit/?h=fixes=1bc74f1ccd457832dc515fc1febe6655985fdcd2

  powerpc/powernv: Fix stale PE primary bus
  When PCI bus is unplugged during full hotplug for EEH recovery,
  the platform PE instance (struct pnv_ioda_pe) isn't released and
  it dereferences the stale PCI bus that has been released. It leads
  to kernel crash when referring to the stale PCI bus.

  This fixes the issue by correcting the PE's primary bus when it's
  oneline at plugging time, in pnv_pci_dma_bus_setup() which is to
  be called by pcibios_fixup_bus().

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1546145/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1547207] Re: skb -> ip_summed == CHECKSUM_NONE creates corrupt packets

[Kevin W. Rudd]

** Tags added: verification-done-precise

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1547207

Title:
  skb -> ip_summed == CHECKSUM_NONE creates corrupt packets

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Precise:
  Fix Committed
Status in linux source package in Trusty:
  Fix Released
Status in linux source package in Vivid:
  Fix Released
Status in linux source package in Wily:
  Fix Released
Status in linux source package in Xenial:
  Fix Released

Bug description:
  Canonical,  Please apply.

  Release: all
  Arch: all

  Original discussion here: http://www.gossamer-
  threads.com/lists/linux/kernel/2329960

  Signed off patch here:
  
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=ce8c839b74e3017996fad4e1b7ba2e2625ede82f

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1547207/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1550468] Re: kernel: correct restore of high gprs on signal return

[Kevin W. Rudd]

** Package changed: ubuntu => linux (Ubuntu)

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1550468

Title:
  kernel: correct restore of high gprs on signal return

Status in linux package in Ubuntu:
  New

Bug description:
  == Comment: #0 - Hendrik Brueckner - 2016-02-26 11:02:00 ==
  Please backport Linux kernel upstream commit ID:

  commit 342300cc9cd3428bc6bfe5809bfcc1b9a0f06702
  Author: Martin Schwidefsky 
  Date:   Fri Feb 19 14:44:14 2016 +0100

  s390/compat: correct restore of high gprs on signal return
  
  git commit 8070361799ae1e3f4ef347bd10f0a508ac10acfb
  "s390: add support for vector extension"
  broke 31-bit compat processes in regard to signal handling.
  
  The restore_sigregs_ext32() function is used to restore the additional
  elements from the user space signal frame. Among the additional elements
  are the upper registers halves for 64-bit register support for 31-bit
  processes. The copy_from_user that is used to retrieve the high-gprs
  array from the user stack uses an incorrect length, 8 bytes instead of
  64 bytes. This causes incorrect upper register halves to get loaded.
  
  Cc: sta...@vger.kernel.org # 3.8+
  Signed-off-by: Martin Schwidefsky 

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1550468/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1548413] Re: bug from upstream commit changes behavior of PCI DMA on PowerNV/bare-metal platforms and can result in EEH when adapter tries to read back buffer after DMA write

[Kevin W. Rudd]

** Package changed: ubuntu => linux (Ubuntu)

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1548413

Title:
  bug from upstream commit changes behavior of PCI DMA on PowerNV/bare-
  metal platforms and can result in EEH when adapter tries to read back
  buffer after DMA write

Status in linux package in Ubuntu:
  New

Bug description:
  == Comment: #0 - Douglas Miller - 2016-01-12 14:28:48 ==
  ---Problem Description---
  bug from upstream commit 10b35b2b7485c342334a48cf199063eed8b8748e changes 
behavior of PCI DMA on PowerNV/bare-metal platforms and can result in EEH when 
adapter tries to read back buffer after DMA write.
   
  ---uname output---
  Affects Wily and Xenial kernel streams. Based on code inspection, not 
observation in running kernel
   
  Machine Type = 8348 "Habanero LC" 
   
  ---Steps to Reproduce---
  Setup RAID volume on PMC-Sierra adapter (driver aacraid) and start a 
test/exerciser doing disk reads on the volume. Pull a disk from the volume and 
an EEH should result.
   
  == Comment: #1 - Douglas Miller - 2016-01-12 14:29:51 ==
  Fix is being reviewed and should get pushed upstream soon. Suggest pulling 
that fix as soon as it is available. Patch is being reviewed on linuxppc-dev 
mailing list, titled "powerpc/ioda: Set "read" permission when "write" is set".

  == Comment: #4 - Douglas Miller  - 2016-02-22 08:08:43 ==

  The fix has been accepted and is now in "master" on linux.git.

  commit 6ecad912a0073c768db1491c27ca55ad2d0ee68f

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1548413/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1547207] Re: skb -> ip_summed == CHECKSUM_NONE creates corrupt packets

[Kevin W. Rudd]

** Package changed: ubuntu => linux (Ubuntu)

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1547207

Title:
  skb -> ip_summed == CHECKSUM_NONE creates corrupt packets

Status in linux package in Ubuntu:
  New

Bug description:
  Canonical,  Please apply.

  Release: all
  Arch: all

  Original discussion here: http://www.gossamer-
  threads.com/lists/linux/kernel/2329960

  Signed off patch here:
  
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=ce8c839b74e3017996fad4e1b7ba2e2625ede82f

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1547207/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1546343] Re: ISST-LTE: kernel BUG at /build/linux-lts-wily-W0lTWH/linux-lts-wily-4.2.0/fs/btrfs/extent-tree.c:6016!

[Kevin W. Rudd]

** Package changed: ubuntu => linux (Ubuntu)

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1546343

Title:
  ISST-LTE: kernel BUG at /build/linux-lts-wily-W0lTWH/linux-lts-
  wily-4.2.0/fs/btrfs/extent-tree.c:6016!

Status in linux package in Ubuntu:
  New

Bug description:
  Mirroring for awareness:

  Last replicated on the 4.2.0-27-generic #32~14.04.1 kernel

  We are encountering btrfs panics like the following while doing stress
  testing:

  68:mon> e
  cpu 0x68: Vector: 700 (Program Check) at [c00029a971d0]
  pc: d691f7b4: unpin_extent_range+0xe4/0x320 [btrfs]
  lr: d691f7a4: unpin_extent_range+0xd4/0x320 [btrfs]
  sp: c00029a97450
 msr: 800100029033
current = 0xc000fbdae590
paca= 0xc7b1dc00   softe: 0irq_happened: 0x01
  pid   = 28091, comm = aio-stress
  kernel BUG at 
/build/linux-lts-wily-YKsqw8/linux-lts-wily-4.2.0/fs/btrfs/extent-tree.c:6022!

  68:mon> t
  [c00029a974e0] d6936a68 btrfs_destroy_pinned_extent+0xe8/0x120 
[btrfs]
  [c00029a97530] d693b8e0 btrfs_cleanup_one_transaction+0x3a0/0x7c0 
[btrfs]
  [c00029a97610] d69405a0 cleanup_transaction+0x150/0x3b0 [btrfs]
  [c00029a976f0] d694184c btrfs_commit_transaction+0x40c/0xd40 
[btrfs]
  [c00029a977f0] d692910c flush_space+0x10c/0x5f0 [btrfs]
  [c00029a978b0] d6929b78 reserve_metadata_bytes+0x258/0x640 [btrfs]
  [c00029a97990] d692a7b0 
btrfs_delalloc_reserve_metadata+0x190/0x560 [btrfs]
  [c00029a97a10] d69591d0 __btrfs_buffered_write+0x1a0/0x5c0 [btrfs]
  [c00029a97af0] d695c9a8 btrfs_file_write_iter+0x208/0x540 [btrfs]
  [c00029a97b90] c0327dc0 aio_run_iocb+0x330/0x3c0
  [c00029a97ce0] c0329664 do_io_submit+0x314/0x670
  [c00029a97e30] c0009204 system_call+0x38/0xb4
  --- Exception: c01 (System Call) at 3fffa79e0768
  SP (3fffa27ce550) is in userspace

  
  68:mon> r
  R00 = d691f7a4   R16 = 0d0f
  R01 = c00029a97450   R17 = c00203badee8
  R02 = d6a134d0   R18 = 0060
  R03 =    R19 = 
  R04 = 0041f20d   R20 = 
  R05 = 0001   R21 = 0001
  R06 = c001e6d9a409   R22 = c00204c00138
  R07 = c001e6d9a400   R23 = c15342d8
  R08 = 1500   R24 = 0041f20e
  R09 = 0001   R25 = 0041f20d
  R10 = 004200a8   R26 = c00204c0
  R11 = d69def18   R27 = 
  R12 = c0a717c0   R28 = c0022fc8e698
  R13 = c7b1dc00   R29 = 
  R14 = 10004820   R30 = 0041f20d
  R15 = c00203badec4   R31 = 
  pc  = d691f7b4 unpin_extent_range+0xe4/0x320 [btrfs]
  cfar= d69174b4 block_group_cache_tree_search+0x104/0x180 [btrfs]
  lr  = d691f7a4 unpin_extent_range+0xd4/0x320 [btrfs]
  msr = 800100029033   cr  = 28022842
  ctr = c0a717c0   xer = 2001   trap =  700

  Partial Output for dump log:
  [269404.043284] [ cut here ]
  [269404.043288] WARNING: at 
/build/linux-lts-wily-YKsqw8/linux-lts-wily-4.2.0/fs/btrfs/extent-tree.c:3581
  [269404.043325] CPU: 104 PID: 28091 Comm: aio-stress Not tainted 
4.2.0-27-generic #32~14.04.1-Ubuntu
  [269404.043329] task: c000fbdae590 ti: c00029a94000 task.ti: 
c00029a94000
  [269404.043331] NIP: d6928fec LR: d6928fe8 CTR: 
c053f720
  [269404.043334] REGS: c00029a97310 TRAP: 0700   Not tainted 
(4.2.0-27-generic)
  [269404.043336] MSR: 800100029033   CR: 28044822  
XER: 2000
  [269404.043346] CFAR: c0a79ec4 SOFTE: 1
  [269404.043407] NIP [d6928fec] 
btrfs_write_dirty_block_groups+0x30c/0x320 [btrfs]
  [269404.043425] LR [d6928fe8] 
btrfs_write_dirty_block_groups+0x308/0x320 [btrfs]
  [269404.043428] Call Trace:
  [269404.043441] [c00029a97590] [d6928fe8] 
btrfs_write_dirty_block_groups+0x308/0x320 [btrfs] (unreliable)
  [269404.043453] [c00029a97660] [d69db42c] 
commit_cowonly_roots+0x23c/0x324 [btrfs]
  [269404.043468] [c00029a976f0] [d6941c0c] 
btrfs_commit_transaction+0x7cc/0xd40 [btrfs]
  [269404.043483] [c00029a977f0] [d692910c] flush_space+0x10c/0x5f0 
[btrfs]
  [269404.043497] [c00029a978b0] [d6929b78] 
reserve_metadata_bytes+0x258/0x640 [btrfs]
  [269404.043511] [c00029a97990] [d692a7b0] 
btrfs_delalloc_reserve_metadata+0x190/0x560 [btrfs]
  [269404.043527] [c00029a97a10] [d69591d0] 
__btrfs_buffered_write+0x1a0/0x5c0 [btrfs]
  [269404.043541] [c00029a97af0] [d695c9a8] 
btrfs_file_write_iter+0x208/0x540 [btrfs]
  [269404.043548] [c00029a97b90] 

[Kernel-packages] [Bug 1546159] Re: ISST-LTE: high cpus number need a high crashkernel value in kdump

[Kevin W. Rudd]

** Package changed: ubuntu => linux (Ubuntu)

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1546159

Title:
  ISST-LTE: high cpus number need a high crashkernel value in kdump

Status in linux package in Ubuntu:
  New

Bug description:
  ---Problem Description---
  The kdump kernel will be booted with "maxcpus=1", so no matter how many cpus 
this system has, only one cpu will be brought up during kdump I think. But on 
LPAR thymelp2, if we allocate 40 cpus on it, then kdump works just fine with 
512M  as crashkernel value. But if we allocate 200 cpus on it, kdump fails by 
trggering OOM. It has been proved that in latter situation we need 1.5G RAM 
reserved for kdump to let it works.
   
  ---Steps to Reproduce---
   1. configure kdump with crashkernel=512M on thymelp2
  2. allcoate 40 cpus on thymelp2 and trigger kdump
  3. allocate 200 cpus on thymelp2 then do kdump again
   
  ---
  Mahesh has posted a patch upstream to provide support for nr_cpus in kdump 
kernel.
  That should take care of this problem..

  https://lists.ozlabs.org/pipermail/linuxppc-dev/2016-February/138619.html
  ---

  Heads up Canonical: We'll want this patch included as soon
  possible/practical.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1546159/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1546145] Re: Surelock-GA2:kernel panic @ cxl_configure_adapter+0x418/0x8b0

[Kevin W. Rudd]

** Package changed: ubuntu => linux (Ubuntu)

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1546145

Title:
  Surelock-GA2:kernel panic @ cxl_configure_adapter+0x418/0x8b0

Status in linux package in Ubuntu:
  New

Bug description:
  == Comment: #18 - Andrew Donnellan - 2016-02-15 20:17:01 ==
  Canonical kernel team - please apply 1bc74f1ccd457832dc515fc1febe6655985fdcd2 
from the powerpc-fixes tree.

  
https://git.kernel.org/cgit/linux/kernel/git/powerpc/linux.git/commit/?h=fixes=1bc74f1ccd457832dc515fc1febe6655985fdcd2

  powerpc/powernv: Fix stale PE primary bus
  When PCI bus is unplugged during full hotplug for EEH recovery,
  the platform PE instance (struct pnv_ioda_pe) isn't released and
  it dereferences the stale PCI bus that has been released. It leads
  to kernel crash when referring to the stale PCI bus.

  This fixes the issue by correcting the PE's primary bus when it's
  oneline at plugging time, in pnv_pci_dma_bus_setup() which is to
  be called by pcibios_fixup_bus().

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1546145/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1545037] Re: Surelock-GA2:kernel panic/ exception @ pcibios_set_pcie_reset_state+0x118/0x280 + cxl_reset+0x5c/0xc0

[Kevin W. Rudd]

** Package changed: ubuntu => linux (Ubuntu)

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1545037

Title:
  Surelock-GA2:kernel panic/ exception @
  pcibios_set_pcie_reset_state+0x118/0x280 + cxl_reset+0x5c/0xc0

Status in linux package in Ubuntu:
  New

Bug description:
  Requesting Canonical kernel team apply
  5b8255dd55f61ff1f65774a2084823415ec09a90 from upstream for 16.04

  Recent bug activity recap:

  == Comment: #17 - Guo Wen Shan  - 2016-02-08 22:40:35 ==
  Tentative patch sent to Andrew for verification. I'm putting a note here 
about the root cause: Each PE (struct eeh_pe) instance is tracking the primary 
bus by "pbus". When we have full hotplug as EEH recovery, the PE instance won't 
be refreshed. So the "pbus" is still dereferencing the stale PCI bus. Access to 
that at later pointer will cause kernel crash.

  The fix, as the patch sent to Andrew for verification, introduces
  another EEH PE flag (EEH_PE_PRI_BUS). That flag represents the
  validity of eeh_pe::pbus. Before unplugging in full hotplug case, the
  flag is cleared so that the eeh_pe::pbus can be updated at plugging
  time. I will send the patch to linux-ppc-dev for review after Andrew
  verified it helps.

  == Comment: #18 - Guo Wen Shan - 2016-02-08 23:55:00 ==
  The patch was sent to linux-ppc-dev for review/pickup: 
https://patchwork.ozlabs.org/patch/580626/ which reads "[v2,1/4] powerpc/eeh: 
Fix stale cached primary bus".

  == Comment: #19 - Andrew Donnellan - 2016-02-09 00:19:33 ==
  Patch has been submitted as per Gavin's comment. Please test!

  == Comment: #22 - Andrew Donnellan - 2016-02-11 01:41:06 ==
  Requesting Canonical kernel team apply 
5b8255dd55f61ff1f65774a2084823415ec09a90 from upstream for 16.04

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1545037/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1542444] Re: ib1: sendonly multicast join failed for ff12:601b:ffff:0000:0000:0000:0000:0016, status -22 (Multicast)

[Kevin W. Rudd]

** Package changed: ubuntu => linux (Ubuntu)

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1542444

Title:
  ib1: sendonly multicast join failed for
  ff12:601b::::::0016, status -22 (Multicast)

Status in linux package in Ubuntu:
  New

Bug description:
  ---Problem Description---
  ib1: sendonly multicast join failed for 
ff12:601b::::::0016, status -22 (Multicast) 
   
  ---uname output---
  Linux ltcalpine-lp4 4.2.0-21-generic #25~14.04.1-Ubuntu SMP Thu Dec 3 
13:55:42 UTC 2015 ppc64le ppc64le ppc64le GNU/Linux

  ---Steps to Reproduce---
   1. run multicast tests and in the syslog you would find the below error 
messages

  [  362.785829] ib1: sendonly multicast join failed for 
ff12:601b::::::0016, status -22
  [  364.785811] ib1: sendonly multicast join failed for 
ff12:601b::::::0016, status -22
   
  == Comment: #2 - Carol L. Soto  - 2016-02-05 11:29:07 ==
  If I add this set of patches I do not see the messages:
  From c3acdc06a95ff20d920220ecb931186b0bb22c42 Mon Sep 17 00:00:00 2001
  From: Doug Ledford 
  Date: Thu, 3 Sep 2015 17:05:58 -0400
  Subject: IB/ipoib: Clean up send-only multicast joins

  
  From d1178cbcdcf91900ccf10a177350d7945703c151 Mon Sep 17 00:00:00 2001
  From: Jason Gunthorpe 
  Date: Fri, 21 Aug 2015 17:34:13 -0600
  Subject: IB/ipoib: Suppress warning for send only join failures

  
  From bd99b2e05c4df2a428e5c9dd338289089d0e26df Mon Sep 17 00:00:00 2001
  From: Christoph Lameter 
  Date: Thu, 24 Sep 2015 12:00:05 -0500
  Subject: IB/ipoib: Expire sendonly multicast joins

  
  From c3852ab0e606212de523c1fb1e15adbf9f431619 Mon Sep 17 00:00:00 2001
  From: Doug Ledford 
  Date: Fri, 25 Sep 2015 14:35:01 -0400
  Subject: IB/ipoib: Make sendonly multicast joins create the mcast group

  
  From 2866196f294954ce9fa226825c8c1eaa64c7da8a Mon Sep 17 00:00:00 2001
  From: Doug Ledford 
  Date: Fri, 25 Sep 2015 22:30:24 -0400
  Subject: IB/ipoib: increase the max mcast backlog queue

  
  From 0b5c9279e568d90903acedc2b9b832d8d78e8288 Mon Sep 17 00:00:00 2001
  From: Christoph Lameter 
  Date: Sun, 11 Oct 2015 18:49:42 -0500
  Subject: IB/ipoib: For sendonly join free the multicast group on leave

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1542444/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1541635] Re: Backport upstream cxlflash commits to Ubuntu 15.10 (Wily) SRU stream

[Kevin W. Rudd]

** Package changed: ubuntu => linux (Ubuntu)

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1541635

Title:
  Backport upstream cxlflash commits to Ubuntu 15.10 (Wily) SRU stream

Status in linux package in Ubuntu:
  New

Bug description:
  == Comment: #0 - UMA KRISHNAN  - 2016-02-03
  16:41:26 ==

  The following fixes for cxlflash are upstreamed as of 4.5-rc1, please
  backport them to Wily SRU stream:

  
  b45cdbaf9f7f0486847c52f60747fb108724652a cxlflash: Resolve oops in 
wait_port_offline

  ee91e332a6e6e9b939f60f6e1bd72fb2def5290d cxlflash: Fix to resolve cmd
  leak after host reset

  85599218914dadad3347eaa4337e71f09f39e78f cxlflash: Removed driver date
  print

  21891a452a42afc2313f1e3a69040e46c1d068c1 cxlflash: drop unlikely
  before IS_ERR_OR_NULL

  f2dd80ecca5f06b46134f2bd811f046c503c756c powerpc/powernv: Panic on
  unhandled Machine Check


  As an FYI, these 2 fixes were also upstreamed but are already present
  in the Wily SRU stream (they were accepted by Canonical as
  SAUCE/noup):

  
  d5e26bb1d812ba74f29b6bcbc88c3dbfb3eed824 cxlflash: Fix to avoid virtual LUN 
failover failure

  a9be294ecb3b9dc82b15625631b153f871181d16 cxlflash: Fix to escalate
  LINK_RESET also on port 1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1541635/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1541638] Re: [Ubuntu 16.04] Backport upstream cxlflash commits to Xenial

[Kevin W. Rudd]

** Package changed: ubuntu => linux (Ubuntu)

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1541638

Title:
  [Ubuntu 16.04] Backport upstream cxlflash commits to Xenial

Status in linux package in Ubuntu:
  New

Bug description:
  == Comment: #0 - UMA KRISHNAN - 2016-02-03 16:45:51 ==

  The following fixes for cxlflash are upstreamed as of 4.5-rc1, please
  backport them to Xenial:

  
  b45cdbaf9f7f0486847c52f60747fb108724652a cxlflash: Resolve oops in 
wait_port_offline

  ee91e332a6e6e9b939f60f6e1bd72fb2def5290d cxlflash: Fix to resolve cmd
  leak after host reset

  85599218914dadad3347eaa4337e71f09f39e78f cxlflash: Removed driver date
  print

  21891a452a42afc2313f1e3a69040e46c1d068c1 cxlflash: drop unlikely
  before IS_ERR_OR_NULL


  These 2 fixes were also upstreamed but are already present in Xenial
  (they were accepted by Canonical as SAUCE/noup). They are candidates
  for reversion:

  
  d5e26bb1d812ba74f29b6bcbc88c3dbfb3eed824 cxlflash: Fix to avoid virtual LUN 
failover failure

  a9be294ecb3b9dc82b15625631b153f871181d16 cxlflash: Fix to escalate
  LINK_RESET also on port 1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1541638/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1529666] Re: Random NX requests failed under heavy load testing

[Kevin W. Rudd]

** Package changed: ubuntu => linux-meta (Ubuntu)

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-meta in Ubuntu.
https://bugs.launchpad.net/bugs/1529666

Title:
  Random NX requests failed under heavy load testing

Status in linux package in Ubuntu:
  New

Bug description:
  == Comment: #0 - Haren Myneni  - 2015-12-23 19:27:08
  ==

  ---Problem Description---
  Under heavy load, some NX requests failed with "Invalid ICSWX return code". 
NX hardware sets return first bit to XER[S0] which is not handled in the driver.
   
  Contact Information = hb...@us.ibm.com 
   
  ---uname output---
  Ubuntu 15.10 kernel
   
  Machine Type = P8 system 
   
  ---Steps to Reproduce---
   Happens randomly under NX heavy load testing. 

  == Comment: #1 - Haren Myneni  - 2015-12-23 19:28:07 ==
  Fix is accepted in maintainers tree 

  
https://git.kernel.org/cgit/linux/kernel/git/herbert/cryptodev-2.6.git/commit/?id=6333ed8f26cf77311088d2e2b7cf16d8480bcbb2

  Customers can see failures with NX compression with this bug.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1529666/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1528688] Re: scsi-firmware udeb does not include ql2500_fw.bin

[Kevin W. Rudd]

** Package changed: ubuntu => linux-firmware (Ubuntu)

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
https://bugs.launchpad.net/bugs/1528688

Title:
  scsi-firmware udeb does not include ql2500_fw.bin

Status in linux-firmware package in Ubuntu:
  New

Bug description:
  == Comment: #0 - Mauricio Faria De Oliveira  - 
2015-12-22 15:54:12 ==
  ---Problem Description---
  scsi-firmware udeb does not include ql2500_fw.bin
  linux-firmware deb does include it.

  linux-firmware_1.154_all.deb

-rw-r--r-- root/root 76802 2014-11-24 15:42 
./lib/firmware/ql2100_fw.bin
-rw-r--r-- root/root 84566 2014-11-24 15:42 
./lib/firmware/ql2200_fw.bin
-rw-r--r-- root/root125252 2014-12-01 15:16 
./lib/firmware/ql2300_fw.bin
-rw-r--r-- root/root136038 2014-12-01 15:16 
./lib/firmware/ql2322_fw.bin
-rw-r--r-- root/root260656 2015-11-20 16:15 
./lib/firmware/ql2400_fw.bin
-rw-r--r-- root/root266912 2015-11-20 16:15 
./lib/firmware/ql2500_fw.bin

  scsi-firmware_1.154_all.udeb

-rw-r--r-- root/root 76802 2015-11-24 18:55 
./lib/firmware/ql2100_fw.bin
-rw-r--r-- root/root 84566 2015-11-24 18:55 
./lib/firmware/ql2200_fw.bin
-rw-r--r-- root/root125252 2015-11-24 18:55 
./lib/firmware/ql2300_fw.bin
-rw-r--r-- root/root136038 2015-11-24 18:55 
./lib/firmware/ql2322_fw.bin
-rw-r--r-- root/root260656 2015-11-24 18:55 
./lib/firmware/ql2400_fw.bin

  listings from:


https://launchpadlibrarian.net/228951553/buildlog_ubuntu-xenial-amd64.linux-firmware_1.154_BUILDING.txt.gz
   
  ---Additional Hardware Info---
  Qlogic QLE2500-based adapters.

  == Comment: #1 - Mauricio Faria De Oliveira  - 
2015-12-22 15:56:45 ==
  Hi Canonical,

  Please include the ql2500_fw.bin file in scsi-firmware.udeb 
(debian/scsi-firmware.lst)
   for 16.04 and 14.04.x.

  Thanks

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1528688/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1509120] Re: Process accounting deadlock with idmapd callout when writing to NFSv4 mount

[Kevin W. Rudd]

** Package changed: ubuntu => linux (Ubuntu)

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1509120

Title:
  Process accounting deadlock with idmapd callout when writing to NFSv4
  mount

Status in linux package in Ubuntu:
  New

Bug description:
  ---Problem Description---
  System hang when process accounting to a NFSv4 mount.

  ---uname output---
  Linux ppc001 3.19.0-30-generic #34~14.04.1-Ubuntu SMP Fri Oct 2 22:21:52
  UTC 2015 ppc64le ppc64le ppc64le GNU/Linux

  ---Problem Details---

  We have a customer that is experiencing intermittent system hangs on
  their system.  After a bit of debug, it was discovered that the
  trigger was turning on process accounting and writing to a file hosted
  via an NFSv4 mount.  During the testing, several vmcores were
  captured, and the fingerprint indicates a mutex deadlock situation
  with process accounting.   In the most recent vmcore, it appears that
  the scenario is something like the following:

  1. PID: 4898 COMMAND: "ls" triggers a write to the process accounting file.
  2. The resulting NFS write needs idmapd information and calls out to idmapd
  3. The idmapd usermodehelper process triggers another process accounting 
update that blocks on the mutex being held by PID 4898.

  PID: 4898   TASK: c01fd26d7580  CPU: 7   COMMAND: "ls"
   #0 [c01fd274a950] __switch_to at c0015934
   #1 [c01fd274ab20] __switch_to at c0015934
   #2 [c01fd274ab80] __schedule at c0a11de8
   #3 [c01fd274ada0] schedule_timeout at c0a16284
   #4 [c01fd274ae90] wait_for_common at c0a1360c
   #5 [c01fd274af10] call_usermodehelper_exec at c00ccd38
   #6 [c01fd274af70] call_sbin_request_key at c0429258
   #7 [c01fd274b100] request_key_and_link at c042983c
   #8 [c01fd274b200] request_key at c0429978
   #9 [c01fd274b240] nfs_idmap_get_key at d0002ca8b0bc [nfsv4]
  #10 [c01fd274b2b0] nfs_map_name_to_uid at d0002ca8bbd0 [nfsv4]
  #11 [c01fd274b320] decode_getfattr_attrs at d0002ca7f59c [nfsv4]
  #12 [c01fd274b420] decode_getfattr_generic.constprop.96 at 
d0002ca7fd78 
  [nfsv4]
  #13 [c01fd274b4d0] nfs4_xdr_dec_getattr at d0002ca80738 [nfsv4]
  #14 [c01fd274b530] rpcauth_unwrap_resp at d0001fe67180 [sunrpc]
  #15 [c01fd274b600] call_decode at d0001fe527c8 [sunrpc]
  #16 [c01fd274b6b0] __rpc_execute at d0001fe64260 [sunrpc]
  #17 [c01fd274b790] rpc_run_task at d0001fe54a78 [sunrpc]
  #18 [c01fd274b7c0] nfs4_call_sync_sequence at d0002ca60960 [nfsv4]
  #19 [c01fd274b860] _nfs4_proc_getattr at d0002ca6217c [nfsv4]
  #20 [c01fd274b930] nfs4_proc_getattr at d0002ca6f494 [nfsv4]
  #21 [c01fd274b9a0] __nfs_revalidate_inode at d000202cf614 [nfs]
  #22 [c01fd274ba30] nfs_revalidate_file_size at d000202c9618 [nfs]
  #23 [c01fd274ba70] nfs_file_write at d000202cabdc [nfs]
  #24 [c01fd274bb00] new_sync_write at c02b3d9c
  #25 [c01fd274bbd0] __kernel_write at c02b3fec
  #26 [c01fd274bc20] do_acct_process at c0166b78
  #27 [c01fd274bcc0] acct_process at c016748c
  #28 [c01fd274bcf0] do_exit at c00b3660
  #29 [c01fd274bdc0] do_group_exit at c00b3b14
  #30 [c01fd274be00] sys_exit_group at c00b3bdc
  #31 [c01fd274be30] system_call at c0009258

  PID: 4900   TASK: c03c9946c180  CPU: 16  COMMAND: "kworker/u320:2"
   #0 [c03c994fb790] __switch_to at c0015934
   #1 [c03c994fb960] __switch_to at c0015934
   #2 [c03c994fb9c0] __schedule at c0a11de8
   #3 [c03c994fbbe0] schedule_preempt_disabled at c0a12980
   #4 [c03c994fbc00] __mutex_lock_slowpath at c0a14aec
   #5 [c03c994fbc80] mutex_lock at c0a14c4c
   #6 [c03c994fbcb0] acct_get at c01663ec
   #7 [c03c994fbcf0] acct_process at c0167480
   #8 [c03c994fbd20] do_exit at c00b3660
   #9 [c03c994fbdf0] call_usermodehelper at c00ccaf4
  #10 [c03c994fbe30] ret_from_kernel_thread at c000956c

  Historical bug data:

  from customer:

   am uploading a crash dump file from a lock up event that I just had.
  I was reminded on a status update call this morning that I never tried
  running process accounting since opening the ticket and updating the
  kernel. So, I tried that this morning. The first time I turned it on
  with the default output location and didn?t have any problems. Then I
  tried turning it on with the output going to our shared disk space,
  which is where I was originally sending it. I ran a couple commands
  that returned just fine, then when I ran a CUDA test program it didn?t
  return and I verified that I was no longer able to login to the node.
  I let it sit for awhile