[Kernel-packages] [Bug 1811660] Re: [SRU] Unable to modify/create-namespace over NVDIMM-N

2019-02-19 Thread Sujith Pandel
This is a kernel issue and we have seen this with upstream kernels and verified 
the fixes on upstream kernels.
I expect bionic kernel 4.15 and above kernels to display this defect.

Although I have not tried applying only the kernel fix on bionic, the test 
kernel shared above shows that original defect is resolved, however another one 
has popped up. 
This indicates that a few more patches are required to get the complete 
namespace modification functionality working.

-- 
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/1811660

Title:
  [SRU] Unable to modify/create-namespace over NVDIMM-N

Status in The Dell-poweredge project:
  New
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  [Impact]
  Users are unable to modify or create namespaces over NVDIMM-N

  [Test Case]

  Steps to Reproduce:
  1. Setup a Dell EMC 14G server R740xd server with NVDIMM-N, update BIOS & 
NVDIMM firmware to latest available to customers.
  2. Install and boot to Ubuntu 18.04
  3. Notice that no pmems are enumerated.
  4. Try #ndctl create-namespace -> Failure with device or resource busy.

  Actual results:
  No pmems are enumerated, cannot create namespaces.
  If pmems are already present, then cannot modify the namespaces.

  Expected results:
  namespace creation should be possible

  
  [Regression Potential] 

  The Regression Risk is low, Intel not impacted but Dell is.

  
  [Other Info]
  Additional Info:
  * Seen with upstream linux-4.20.2 also.

  * Upstream bug report -
  https://github.com/pmem/ndctl/issues/78

  * Upstream kernel patch:
  https://lists.01.org/pipermail/linux-nvdimm/2019-January/019435.html

  Request you to incorporate it in bionic and xenial kernels.

To manage notifications about this bug go to:
https://bugs.launchpad.net/dell-poweredge/+bug/1811660/+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 1811660] Re: [SRU] Unable to modify/create-namespace over NVDIMM-N

2019-02-11 Thread Sujith Pandel
Another issue pops-up, looks like there are a few nvdimm patches that
require backporting:

# ndctl create-namespace -e "namespace0.0" -m fsdax -f -vvv
libndctl: sizeof_namespace_index: nmem0: label area (1024) too small to host 
(256 byte) labels
libndctl: sizeof_namespace_index: nmem0: label area (1024) too small to host 
(256 byte) labels
libndctl: sizeof_namespace_index: nmem0: label area (1024) too small to host 
(256 byte) labels
libndctl: sizeof_namespace_index: nmem0: label area (1024) too small to host 
(256 byte) labels
libndctl: sizeof_namespace_index: nmem0: label area (1024) too small to host 
(256 byte) labels
libndctl: sizeof_namespace_index: nmem0: label area (1024) too small to host 
(256 byte) labels
libndctl: sizeof_namespace_index: nmem0: label area (1024) too small to host 
(256 byte) labels
libndctl: sizeof_namespace_index: nmem0: label area (1024) too small to host 
(256 byte) labels
libndctl: sizeof_namespace_index: nmem0: label area (1024) too small to host 
(256 byte) labels
libndctl: sizeof_namespace_index: nmem0: label area (1024) too small to host 
(256 byte) labels
libndctl: sizeof_namespace_index: nmem0: label area (1024) too small to host 
(256 byte) labels
libndctl: sizeof_namespace_index: nmem0: label area (1024) too small to host 
(256 byte) labels
libndctl: sizeof_namespace_index: nmem0: label area (1024) too small to host 
(256 byte) labels
libndctl: sizeof_namespace_index: nmem0: label area (1024) too small to host 
(256 byte) labels
libndctl: sizeof_namespace_index: nmem0: label area (1024) too small to host 
(256 byte) labels
libndctl: sizeof_namespace_index: nmem0: label area (1024) too small to host 
(256 byte) labels
libndctl: sizeof_namespace_index: nmem0: label area (1024) too small to host 
(256 byte) labels
libndctl: sizeof_namespace_index: nmem0: label area (1024) too small to host 
(256 byte) labels
libndctl: sizeof_namespace_index: nmem0: label area (1024) too small to host 
(256 byte) labels
libndctl: sizeof_namespace_index: nmem0: label area (1024) too small to host 
(256 byte) labels
libndctl: ndctl_dimm_enable: nmem0: failed to enable
libndctl: sizeof_namespace_index: nmem0: label area (1024) too small to host 
(128 byte) labels
libndctl: sizeof_namespace_index: nmem0: label area (1024) too small to host 
(128 byte) labels
libndctl: sizeof_namespace_index: nmem0: label area (1024) too small to host 
(128 byte) labels
libndctl: sizeof_namespace_index: nmem0: label area (1024) too small to host 
(128 byte) labels
libndctl: sizeof_namespace_index: nmem0: label area (1024) too small to host 
(128 byte) labels
libndctl: sizeof_namespace_index: nmem0: label area (1024) too small to host 
(128 byte) labels
libndctl: sizeof_namespace_index: nmem0: label area (1024) too small to host 
(128 byte) labels
libndctl: sizeof_namespace_index: nmem0: label area (1024) too small to host 
(128 byte) labels
libndctl: sizeof_namespace_index: nmem0: label area (1024) too small to host 
(128 byte) labels
libndctl: sizeof_namespace_index: nmem0: label area (1024) too small to host 
(128 byte) labels
libndctl: sizeof_namespace_index: nmem0: label area (1024) too small to host 
(128 byte) labels
libndctl: sizeof_namespace_index: nmem0: label area (1024) too small to host 
(128 byte) labels
libndctl: sizeof_namespace_index: nmem0: label area (1024) too small to host 
(128 byte) labels
libndctl: sizeof_namespace_index: nmem0: label area (1024) too small to host 
(128 byte) labels
libndctl: sizeof_namespace_index: nmem0: label area (1024) too small to host 
(128 byte) labels
libndctl: sizeof_namespace_index: nmem0: label area (1024) too small to host 
(128 byte) labels
libndctl: sizeof_namespace_index: nmem0: label area (1024) too small to host 
(128 byte) labels
libndctl: sizeof_namespace_index: nmem0: label area (1024) too small to host 
(128 byte) labels
libndctl: sizeof_namespace_index: nmem0: label area (1024) too small to host 
(128 byte) labels
libndctl: sizeof_namespace_index: nmem0: label area (1024) too small to host 
(128 byte) labels
libndctl: ndctl_dimm_enable: nmem0: failed to enable
enable_labels:945: region0: failed to initialize labels
namespace_reconfig:977: region0: no idle namespace seed
failed to reconfigure namespace: No such device

root@ubuntu:~# ndctl -v
61.2+

-- 
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/1811660

Title:
  [SRU] Unable to modify/create-namespace over NVDIMM-N

Status in The Dell-poweredge project:
  New
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  [Impact]
  Users are unable to modify or create namespaces over NVDIMM-N

  [Test Case]

  Steps to Reproduce:
  1. Setup a Dell EMC 14G server R740xd server with NVDIMM-N, update BIOS & 
NVDIMM firmware to latest available to customers.
  2. Install and boot to Ubuntu 18.04
  3. Notice that no pmems are enumerated.
  4. Try #ndctl create-namespace -> Failure with 

[Kernel-packages] [Bug 1795453] Re: [SRU] IO's are issued with incorrect Scatter Gather Buffer

2019-02-07 Thread Sujith Pandel
Can we also get the above fixes in Xenial HWE kernels?
I suppose Xenial HWE kernel is a fork of bionic LTS kernels..

-- 
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/1795453

Title:
  [SRU] IO's are issued with incorrect Scatter Gather Buffer

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Bionic:
  Fix Committed
Status in linux source package in Cosmic:
  Fix Committed

Bug description:
  [Impact]
  We have observed that OS is sending the IO's (SCSI Read/Write) with incorrect 
Scatter Gather Buffer address .

  i.e

   OS is sending the IO with 64 bit Scatter Gather Buffer address , such
  that if we add the length with buffer address then it causes the roll
  over .

  Here is the data we captured in our driver (Printed the SGE details
  which was sent by OS)

  sgl_ptr->Address = f000
  [14547.313240]
  sgl_ptr->Length = 1000
  [14547.313241]
  sge_count = 18
  [14547.313242]
  cmd->index = 9d9

  Note : This issue is observed only when virtualization is enabled

  Product : Broadcom (LSI) Megaraid H840 controller

  
  [Test Case]
  Steps found in comment #60
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1795453/comments/60

  
  [Regression Potential]

  The patches in Comment #59 have been accepted upstream.

  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1795453/comments/59


  [Other Info]

  Product : Broadcom (LSI) Megaraid H840 controller
  ---
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw+ 1 root audio 116,  1 Oct 12 16:35 seq
   crw-rw+ 1 root audio 116, 33 Oct 12 16:35 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 18.04
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  MachineType: Dell Inc. PowerEdge R7415
  Package: linux (not installed)
  PciMultimedia:

  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 mgadrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-8-generic 
root=UUID=43e89410-c7ff-11e8-9229-d094661013d8 ro
  ProcVersionSignature: Ubuntu 4.18.0-8.9~18.04.1-generic 4.18.7
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-8-generic N/A
   linux-backports-modules-4.18.0-8-generic  N/A
   linux-firmware1.173.1
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  Tags:  bionic uec-images
  Uname: Linux 4.18.0-8-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lxd plugdev sudo
  _MarkForUpload: True
  dmi.bios.date: 09/07/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.6.2
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 23
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.6.2:bd09/07/2018:svnDellInc.:pnPowerEdgeR7415:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct23:cvr:
  dmi.product.family: PowerEdge
  dmi.product.name: PowerEdge R7415
  dmi.product.sku: SKU=NotProvided;ModelName=PowerEdge R7415
  dmi.sys.vendor: Dell Inc.
  ---
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw+ 1 root audio 116,  1 Oct 12 16:35 seq
   crw-rw+ 1 root audio 116, 33 Oct 12 16:35 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 18.04
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  MachineType: Dell Inc. PowerEdge R7415
  Package: linux (not installed)
  PciMultimedia:

  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 mgadrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-8-generic 
root=UUID=43e89410-c7ff-11e8-9229-d094661013d8 ro
  ProcVersionSignature: Ubuntu 4.18.0-8.9~18.04.1-generic 4.18.7
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-8-generic N/A
   linux-backports-modules-4.18.0-8-generic  N/A
   linux-firmware1.173.1
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  Tags:  bionic uec-images
  Uname: Linux 4.18.0-8-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lxd plugdev sudo
  _MarkForUpload: True
  dmi.bios.date: 09/07/2018
  

[Kernel-packages] [Bug 1811660] Re: Unable to modify/create-namespace over NVDIMM-N

2019-01-27 Thread Sujith Pandel
Same as https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1811785

-- 
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/1811660

Title:
  Unable to modify/create-namespace over NVDIMM-N

Status in The Dell-poweredge project:
  New
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Steps to Reproduce:
  1. Setup a Dell EMC 14G server R740xd server with NVDIMM-N, update BIOS & 
NVDIMM firmware to latest available to customers.
  2. Install and boot to Ubuntu 18.04
  3. Notice that no pmems are enumerated.
  4. Try #ndctl create-namespace -> Failure with device or resource busy.

  Actual results:
  No pmems are enumerated, cannot create namespaces.
  If pmems are already present, then cannot modify the namespaces.

  Expected results:
  namespace creation should be possible

  Additional Info:
  * Seen with upstream linux-4.20.2 also.

  * Upstream bug report -
  https://github.com/pmem/ndctl/issues/78

  * Upstream kernel patch: 
  https://lists.01.org/pipermail/linux-nvdimm/2019-January/019435.html

  Request you to incorporate it in bionic and xenial kernels.

To manage notifications about this bug go to:
https://bugs.launchpad.net/dell-poweredge/+bug/1811660/+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 1811660] Re: Unable to modify/create-namespace over NVDIMM-N

2019-01-23 Thread Sujith Pandel
** Also affects: dell-poweredge
   Importance: Undecided
   Status: 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/1811660

Title:
  Unable to modify/create-namespace over NVDIMM-N

Status in The Dell-poweredge project:
  New
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Steps to Reproduce:
  1. Setup a Dell EMC 14G server R740xd server with NVDIMM-N, update BIOS & 
NVDIMM firmware to latest available to customers.
  2. Install and boot to Ubuntu 18.04
  3. Notice that no pmems are enumerated.
  4. Try #ndctl create-namespace -> Failure with device or resource busy.

  Actual results:
  No pmems are enumerated, cannot create namespaces.
  If pmems are already present, then cannot modify the namespaces.

  Expected results:
  namespace creation should be possible

  Additional Info:
  * Seen with upstream linux-4.20.2 also.

  * Upstream bug report -
  https://github.com/pmem/ndctl/issues/78

  * Upstream kernel patch: 
  https://lists.01.org/pipermail/linux-nvdimm/2019-January/019435.html

  Request you to incorporate it in bionic and xenial kernels.

To manage notifications about this bug go to:
https://bugs.launchpad.net/dell-poweredge/+bug/1811660/+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 1811660] Re: Unable to modify/create-namespace over NVDIMM-N

2019-01-23 Thread Sujith Pandel
Fix:
acpi/nfit: Block function zero DSMs
https://git.kernel.org/pub/scm/linux/kernel/git/nvdimm/nvdimm.git/commit/?h=libnvdimm-fixes=11189c1089da413aa4b5fd6be4c4d47c78968819

acpi/nfit: Fix command-supported detection
https://git.kernel.org/pub/scm/linux/kernel/git/nvdimm/nvdimm.git/commit/?h=libnvdimm-fixes=5e9e38d0db1d29efed1dd4cf9a70115d33521be7

-- 
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/1811660

Title:
  Unable to modify/create-namespace over NVDIMM-N

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Steps to Reproduce:
  1. Setup a Dell EMC 14G server R740xd server with NVDIMM-N, update BIOS & 
NVDIMM firmware to latest available to customers.
  2. Install and boot to Ubuntu 18.04
  3. Notice that no pmems are enumerated.
  4. Try #ndctl create-namespace -> Failure with device or resource busy.

  Actual results:
  No pmems are enumerated, cannot create namespaces.
  If pmems are already present, then cannot modify the namespaces.

  Expected results:
  namespace creation should be possible

  Additional Info:
  * Seen with upstream linux-4.20.2 also.

  * Upstream bug report -
  https://github.com/pmem/ndctl/issues/78

  * Upstream kernel patch: 
  https://lists.01.org/pipermail/linux-nvdimm/2019-January/019435.html

  Request you to incorporate it in bionic and xenial kernels.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1811660/+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 1811660] Re: Unable to modify/create-namespace over NVDIMM-N

2019-01-23 Thread Sujith Pandel
It can be seen across all 14G Dell EMC servers carrying NVDIMM-N.

Current setup I have is a T640 with 1.6.13 BIOS and NVDIMM fw
version-9324

-- 
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/1811660

Title:
  Unable to modify/create-namespace over NVDIMM-N

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Steps to Reproduce:
  1. Setup a Dell EMC 14G server R740xd server with NVDIMM-N, update BIOS & 
NVDIMM firmware to latest available to customers.
  2. Install and boot to Ubuntu 18.04
  3. Notice that no pmems are enumerated.
  4. Try #ndctl create-namespace -> Failure with device or resource busy.

  Actual results:
  No pmems are enumerated, cannot create namespaces.
  If pmems are already present, then cannot modify the namespaces.

  Expected results:
  namespace creation should be possible

  Additional Info:
  * Seen with upstream linux-4.20.2 also.

  * Upstream bug report -
  https://github.com/pmem/ndctl/issues/78

  * Upstream kernel patch: 
  https://lists.01.org/pipermail/linux-nvdimm/2019-January/019435.html

  Request you to incorporate it in bionic and xenial kernels.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1811660/+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 1811660] Re: Unable to modify/create-namespace over NVDIMM-N

2019-01-23 Thread Sujith Pandel
Issue seen across all kernels of Ubuntu 18.04

-- 
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/1811660

Title:
  Unable to modify/create-namespace over NVDIMM-N

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Steps to Reproduce:
  1. Setup a Dell EMC 14G server R740xd server with NVDIMM-N, update BIOS & 
NVDIMM firmware to latest available to customers.
  2. Install and boot to Ubuntu 18.04
  3. Notice that no pmems are enumerated.
  4. Try #ndctl create-namespace -> Failure with device or resource busy.

  Actual results:
  No pmems are enumerated, cannot create namespaces.
  If pmems are already present, then cannot modify the namespaces.

  Expected results:
  namespace creation should be possible

  Additional Info:
  * Seen with upstream linux-4.20.2 also.

  * Upstream bug report -
  https://github.com/pmem/ndctl/issues/78

  * Upstream kernel patch: 
  https://lists.01.org/pipermail/linux-nvdimm/2019-January/019435.html

  Request you to incorporate it in bionic and xenial kernels.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1811660/+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 1811660] [NEW] Unable to modify/create-namespace over NVDIMM-N

2019-01-14 Thread Sujith Pandel
Private bug reported:

Steps to Reproduce:
1. Setup a Dell EMC 14G server R740xd server with NVDIMM-N, update BIOS & 
NVDIMM firmware to latest available to customers.
2. Install and boot to Ubuntu 18.04
3. Notice that no pmems are enumerated.
4. Try #ndctl create-namespace -> Failure with device or resource busy.

Actual results:
No pmems are enumerated, cannot create namespaces.
If pmems are already present, then cannot modify the namespaces.

Expected results:
namespace creation should be possible

Additional Info:
* Seen with upstream linux-4.20.2 also.

* Upstream bug report -
https://github.com/pmem/ndctl/issues/78

* Upstream kernel patch: 
https://lists.01.org/pipermail/linux-nvdimm/2019-January/019435.html

Request you to incorporate it in bionic and xenial kernels.

** Affects: linux (Ubuntu)
 Importance: Undecided
 Status: New

** Information type changed from Public to Private

-- 
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/1811660

Title:
  Unable to modify/create-namespace over NVDIMM-N

Status in linux package in Ubuntu:
  New

Bug description:
  Steps to Reproduce:
  1. Setup a Dell EMC 14G server R740xd server with NVDIMM-N, update BIOS & 
NVDIMM firmware to latest available to customers.
  2. Install and boot to Ubuntu 18.04
  3. Notice that no pmems are enumerated.
  4. Try #ndctl create-namespace -> Failure with device or resource busy.

  Actual results:
  No pmems are enumerated, cannot create namespaces.
  If pmems are already present, then cannot modify the namespaces.

  Expected results:
  namespace creation should be possible

  Additional Info:
  * Seen with upstream linux-4.20.2 also.

  * Upstream bug report -
  https://github.com/pmem/ndctl/issues/78

  * Upstream kernel patch: 
  https://lists.01.org/pipermail/linux-nvdimm/2019-January/019435.html

  Request you to incorporate it in bionic and xenial kernels.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1811660/+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 1795453] Re: IO's are issued with incorrect Scatter Gather Buffer

2018-12-19 Thread Sujith Pandel
Broadcom submitted the fix upstream:
https://marc.info/?l=linux-scsi=154514161019901=2
https://marc.info/?l=linux-scsi=154514161319908=2
https://marc.info/?l=linux-scsi=154514161619911=2

and the commit IDs of these patches from upstream:

894169db1246 scsi: megaraid_sas: Use 63-bit DMA addressing
7b9e2d348c2a scsi: megaraid_sas: driver version update

Please include them in the Ubuntu 18.04 LTS kernels.

-- 
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/1795453

Title:
  IO's are issued with incorrect Scatter Gather Buffer

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  
  We have observed that OS is sending the IO's (SCSI Read/Write) with incorrect 
Scatter Gather Buffer address .

  i.e

   OS is sending the IO with 64 bit Scatter Gather Buffer address , such
  that if we add the length with buffer address then it causes the roll
  over .

  
  Here is the data we captured in our driver (Printed the SGE details which was 
sent by OS)

  sgl_ptr->Address = f000 
  [14547.313240] 
  sgl_ptr->Length = 1000 
  [14547.313241] 
  sge_count = 18 
  [14547.313242] 
  cmd->index = 9d9

  
  Note : This issue is observed only when virtualization is enabled 

  Product : Broadcom (LSI) Megaraid H840 controller
  --- 
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw+ 1 root audio 116,  1 Oct 12 16:35 seq
   crw-rw+ 1 root audio 116, 33 Oct 12 16:35 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 18.04
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  MachineType: Dell Inc. PowerEdge R7415
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 mgadrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-8-generic 
root=UUID=43e89410-c7ff-11e8-9229-d094661013d8 ro
  ProcVersionSignature: Ubuntu 4.18.0-8.9~18.04.1-generic 4.18.7
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-8-generic N/A
   linux-backports-modules-4.18.0-8-generic  N/A
   linux-firmware1.173.1
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  Tags:  bionic uec-images
  Uname: Linux 4.18.0-8-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lxd plugdev sudo
  _MarkForUpload: True
  dmi.bios.date: 09/07/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.6.2
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 23
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.6.2:bd09/07/2018:svnDellInc.:pnPowerEdgeR7415:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct23:cvr:
  dmi.product.family: PowerEdge
  dmi.product.name: PowerEdge R7415
  dmi.product.sku: SKU=NotProvided;ModelName=PowerEdge R7415
  dmi.sys.vendor: Dell Inc.
  --- 
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw+ 1 root audio 116,  1 Oct 12 16:35 seq
   crw-rw+ 1 root audio 116, 33 Oct 12 16:35 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 18.04
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  MachineType: Dell Inc. PowerEdge R7415
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 mgadrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-8-generic 
root=UUID=43e89410-c7ff-11e8-9229-d094661013d8 ro
  ProcVersionSignature: Ubuntu 4.18.0-8.9~18.04.1-generic 4.18.7
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-8-generic N/A
   linux-backports-modules-4.18.0-8-generic  N/A
   linux-firmware1.173.1
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  Tags:  bionic uec-images
  Uname: Linux 4.18.0-8-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lxd plugdev sudo
  _MarkForUpload: True
  dmi.bios.date: 09/07/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.6.2
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 23
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 

[Kernel-packages] [Bug 1795453] Re: IO's are issued with incorrect Scatter Gather Buffer

2018-11-01 Thread Sujith Pandel
The 63bit dma_mask was just a test to understand the adress-wraparound by the 
fw. Nothing specific.
PERC didn't go offline. Always ended up with OOM btw.

-- 
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/1795453

Title:
  IO's are issued with incorrect Scatter Gather Buffer

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  
  We have observed that OS is sending the IO's (SCSI Read/Write) with incorrect 
Scatter Gather Buffer address .

  i.e

   OS is sending the IO with 64 bit Scatter Gather Buffer address , such
  that if we add the length with buffer address then it causes the roll
  over .

  
  Here is the data we captured in our driver (Printed the SGE details which was 
sent by OS)

  sgl_ptr->Address = f000 
  [14547.313240] 
  sgl_ptr->Length = 1000 
  [14547.313241] 
  sge_count = 18 
  [14547.313242] 
  cmd->index = 9d9

  
  Note : This issue is observed only when virtualization is enabled 

  Product : Broadcom (LSI) Megaraid H840 controller
  --- 
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw+ 1 root audio 116,  1 Oct 12 16:35 seq
   crw-rw+ 1 root audio 116, 33 Oct 12 16:35 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 18.04
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  MachineType: Dell Inc. PowerEdge R7415
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 mgadrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-8-generic 
root=UUID=43e89410-c7ff-11e8-9229-d094661013d8 ro
  ProcVersionSignature: Ubuntu 4.18.0-8.9~18.04.1-generic 4.18.7
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-8-generic N/A
   linux-backports-modules-4.18.0-8-generic  N/A
   linux-firmware1.173.1
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  Tags:  bionic uec-images
  Uname: Linux 4.18.0-8-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lxd plugdev sudo
  _MarkForUpload: True
  dmi.bios.date: 09/07/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.6.2
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 23
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.6.2:bd09/07/2018:svnDellInc.:pnPowerEdgeR7415:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct23:cvr:
  dmi.product.family: PowerEdge
  dmi.product.name: PowerEdge R7415
  dmi.product.sku: SKU=NotProvided;ModelName=PowerEdge R7415
  dmi.sys.vendor: Dell Inc.
  --- 
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw+ 1 root audio 116,  1 Oct 12 16:35 seq
   crw-rw+ 1 root audio 116, 33 Oct 12 16:35 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 18.04
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  MachineType: Dell Inc. PowerEdge R7415
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 mgadrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-8-generic 
root=UUID=43e89410-c7ff-11e8-9229-d094661013d8 ro
  ProcVersionSignature: Ubuntu 4.18.0-8.9~18.04.1-generic 4.18.7
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-8-generic N/A
   linux-backports-modules-4.18.0-8-generic  N/A
   linux-firmware1.173.1
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  Tags:  bionic uec-images
  Uname: Linux 4.18.0-8-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lxd plugdev sudo
  _MarkForUpload: True
  dmi.bios.date: 09/07/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.6.2
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 23
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.6.2:bd09/07/2018:svnDellInc.:pnPowerEdgeR7415:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct23:cvr:
  dmi.product.family: PowerEdge
  dmi.product.name: PowerEdge R7415
  dmi.product.sku: SKU=NotProvided;ModelName=PowerEdge R7415
  dmi.sys.vendor: Dell Inc.
  --- 
  ProblemType: 

[Kernel-packages] [Bug 1795453] Re: IO's are issued with incorrect Scatter Gather Buffer

2018-10-29 Thread Sujith Pandel
@sasikumarpc -
We observed this scenario where the PERC goes offline:
sgl_ptr->Address = f000
sgl_ptr->Length = 1000

We do not see a roll-over here..

Kernel is indicating to read 0x1000 bytes starting from address
0xf000 i.e till 0x which very well aligns
with 64 bit dma_mask being assigned by megaraid_sas driver.

Looks like kernel is working as expected based on the dma_mask set by 
megaraid_sas driver.
Once the 32bit address gets exhausted, the kernel tries to get buffer based on 
64bit dma_mask top-down.

We are suspecting that the PERC firmware might not be able to handle this 
corner case. 
PERC did not go offline by changing the dma_mask to 63, and these initial 
results looks to be supporting this stance on fw.
Can you please check this and revert?

-- 
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/1795453

Title:
  IO's are issued with incorrect Scatter Gather Buffer

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  
  We have observed that OS is sending the IO's (SCSI Read/Write) with incorrect 
Scatter Gather Buffer address .

  i.e

   OS is sending the IO with 64 bit Scatter Gather Buffer address , such
  that if we add the length with buffer address then it causes the roll
  over .

  
  Here is the data we captured in our driver (Printed the SGE details which was 
sent by OS)

  sgl_ptr->Address = f000 
  [14547.313240] 
  sgl_ptr->Length = 1000 
  [14547.313241] 
  sge_count = 18 
  [14547.313242] 
  cmd->index = 9d9

  
  Note : This issue is observed only when virtualization is enabled 

  Product : Broadcom (LSI) Megaraid H840 controller
  --- 
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw+ 1 root audio 116,  1 Oct 12 16:35 seq
   crw-rw+ 1 root audio 116, 33 Oct 12 16:35 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 18.04
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  MachineType: Dell Inc. PowerEdge R7415
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 mgadrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-8-generic 
root=UUID=43e89410-c7ff-11e8-9229-d094661013d8 ro
  ProcVersionSignature: Ubuntu 4.18.0-8.9~18.04.1-generic 4.18.7
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-8-generic N/A
   linux-backports-modules-4.18.0-8-generic  N/A
   linux-firmware1.173.1
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  Tags:  bionic uec-images
  Uname: Linux 4.18.0-8-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lxd plugdev sudo
  _MarkForUpload: True
  dmi.bios.date: 09/07/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.6.2
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 23
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.6.2:bd09/07/2018:svnDellInc.:pnPowerEdgeR7415:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct23:cvr:
  dmi.product.family: PowerEdge
  dmi.product.name: PowerEdge R7415
  dmi.product.sku: SKU=NotProvided;ModelName=PowerEdge R7415
  dmi.sys.vendor: Dell Inc.
  --- 
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw+ 1 root audio 116,  1 Oct 12 16:35 seq
   crw-rw+ 1 root audio 116, 33 Oct 12 16:35 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 18.04
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  MachineType: Dell Inc. PowerEdge R7415
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 mgadrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-8-generic 
root=UUID=43e89410-c7ff-11e8-9229-d094661013d8 ro
  ProcVersionSignature: Ubuntu 4.18.0-8.9~18.04.1-generic 4.18.7
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-8-generic N/A
   linux-backports-modules-4.18.0-8-generic  N/A
   linux-firmware1.173.1
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  Tags:  bionic 

[Kernel-packages] [Bug 1795453] Re: IO's are issued with incorrect Scatter Gather Buffer

2018-10-22 Thread Sujith Pandel
With the 4.18.0-8-generic kernel, I see AMD IOMMU IO_PAGE_FAULTs for invalid 
addresses
AMD-Vi: Event logged [IO_PAGE_FAULT device=e1:00.0 domain=0x 
address=0xfffd14c0 flags=0x0030]

PERC controller is still present btw, but the vdbench stress crashed due
to this page faults.

** Attachment added: "4.18 - amd- iommu - page_faults"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1795453/+attachment/5204196/+files/4.18-stress_fails-page_faults.txt

-- 
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/1795453

Title:
  IO's are issued with incorrect Scatter Gather Buffer

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  
  We have observed that OS is sending the IO's (SCSI Read/Write) with incorrect 
Scatter Gather Buffer address .

  i.e

   OS is sending the IO with 64 bit Scatter Gather Buffer address , such
  that if we add the length with buffer address then it causes the roll
  over .

  
  Here is the data we captured in our driver (Printed the SGE details which was 
sent by OS)

  sgl_ptr->Address = f000 
  [14547.313240] 
  sgl_ptr->Length = 1000 
  [14547.313241] 
  sge_count = 18 
  [14547.313242] 
  cmd->index = 9d9

  
  Note : This issue is observed only when virtualization is enabled 

  Product : Broadcom (LSI) Megaraid H840 controller
  --- 
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw+ 1 root audio 116,  1 Oct 12 16:35 seq
   crw-rw+ 1 root audio 116, 33 Oct 12 16:35 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 18.04
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  MachineType: Dell Inc. PowerEdge R7415
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 mgadrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-8-generic 
root=UUID=43e89410-c7ff-11e8-9229-d094661013d8 ro
  ProcVersionSignature: Ubuntu 4.18.0-8.9~18.04.1-generic 4.18.7
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-8-generic N/A
   linux-backports-modules-4.18.0-8-generic  N/A
   linux-firmware1.173.1
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  Tags:  bionic uec-images
  Uname: Linux 4.18.0-8-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lxd plugdev sudo
  _MarkForUpload: True
  dmi.bios.date: 09/07/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.6.2
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 23
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.6.2:bd09/07/2018:svnDellInc.:pnPowerEdgeR7415:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct23:cvr:
  dmi.product.family: PowerEdge
  dmi.product.name: PowerEdge R7415
  dmi.product.sku: SKU=NotProvided;ModelName=PowerEdge R7415
  dmi.sys.vendor: Dell Inc.
  --- 
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw+ 1 root audio 116,  1 Oct 12 16:35 seq
   crw-rw+ 1 root audio 116, 33 Oct 12 16:35 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 18.04
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  MachineType: Dell Inc. PowerEdge R7415
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 mgadrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-8-generic 
root=UUID=43e89410-c7ff-11e8-9229-d094661013d8 ro
  ProcVersionSignature: Ubuntu 4.18.0-8.9~18.04.1-generic 4.18.7
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-8-generic N/A
   linux-backports-modules-4.18.0-8-generic  N/A
   linux-firmware1.173.1
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  Tags:  bionic uec-images
  Uname: Linux 4.18.0-8-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lxd plugdev sudo
  _MarkForUpload: True
  dmi.bios.date: 09/07/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.6.2
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 23
  dmi.chassis.vendor: 

[Kernel-packages] [Bug 1795453] Re: IO's are issued with incorrect Scatter Gather Buffer

2018-10-22 Thread Sujith Pandel
I see the disks going offline during stress in mainline
4.19.0-041900rc7-generic as well.

Although the symptoms look different in 4.15 and 4.18 kernels, I feel
the bug is not fixed; address being accessed is still out-of-range in
this 16GB server.

-- 
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/1795453

Title:
  IO's are issued with incorrect Scatter Gather Buffer

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  
  We have observed that OS is sending the IO's (SCSI Read/Write) with incorrect 
Scatter Gather Buffer address .

  i.e

   OS is sending the IO with 64 bit Scatter Gather Buffer address , such
  that if we add the length with buffer address then it causes the roll
  over .

  
  Here is the data we captured in our driver (Printed the SGE details which was 
sent by OS)

  sgl_ptr->Address = f000 
  [14547.313240] 
  sgl_ptr->Length = 1000 
  [14547.313241] 
  sge_count = 18 
  [14547.313242] 
  cmd->index = 9d9

  
  Note : This issue is observed only when virtualization is enabled 

  Product : Broadcom (LSI) Megaraid H840 controller
  --- 
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw+ 1 root audio 116,  1 Oct 12 16:35 seq
   crw-rw+ 1 root audio 116, 33 Oct 12 16:35 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 18.04
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  MachineType: Dell Inc. PowerEdge R7415
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 mgadrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-8-generic 
root=UUID=43e89410-c7ff-11e8-9229-d094661013d8 ro
  ProcVersionSignature: Ubuntu 4.18.0-8.9~18.04.1-generic 4.18.7
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-8-generic N/A
   linux-backports-modules-4.18.0-8-generic  N/A
   linux-firmware1.173.1
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  Tags:  bionic uec-images
  Uname: Linux 4.18.0-8-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lxd plugdev sudo
  _MarkForUpload: True
  dmi.bios.date: 09/07/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.6.2
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 23
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.6.2:bd09/07/2018:svnDellInc.:pnPowerEdgeR7415:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct23:cvr:
  dmi.product.family: PowerEdge
  dmi.product.name: PowerEdge R7415
  dmi.product.sku: SKU=NotProvided;ModelName=PowerEdge R7415
  dmi.sys.vendor: Dell Inc.
  --- 
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw+ 1 root audio 116,  1 Oct 12 16:35 seq
   crw-rw+ 1 root audio 116, 33 Oct 12 16:35 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 18.04
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  MachineType: Dell Inc. PowerEdge R7415
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 mgadrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-8-generic 
root=UUID=43e89410-c7ff-11e8-9229-d094661013d8 ro
  ProcVersionSignature: Ubuntu 4.18.0-8.9~18.04.1-generic 4.18.7
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-8-generic N/A
   linux-backports-modules-4.18.0-8-generic  N/A
   linux-firmware1.173.1
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  Tags:  bionic uec-images
  Uname: Linux 4.18.0-8-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lxd plugdev sudo
  _MarkForUpload: True
  dmi.bios.date: 09/07/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.6.2
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 23
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.6.2:bd09/07/2018:svnDellInc.:pnPowerEdgeR7415:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct23:cvr:
  dmi.product.family: PowerEdge
  dmi.product.name: PowerEdge R7415
  

[Kernel-packages] [Bug 1795453] Re: IO's are issued with incorrect Scatter Gather Buffer

2018-10-22 Thread Sujith Pandel
With latest 4.15 LTS kernels, I see the vdbench process crash and the
PERC controller and the related disks go offline..

** Attachment added: "4.15 - vdbench - disks go offline"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1795453/+attachment/5204195/+files/4.15-stress_fails.txt

-- 
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/1795453

Title:
  IO's are issued with incorrect Scatter Gather Buffer

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  
  We have observed that OS is sending the IO's (SCSI Read/Write) with incorrect 
Scatter Gather Buffer address .

  i.e

   OS is sending the IO with 64 bit Scatter Gather Buffer address , such
  that if we add the length with buffer address then it causes the roll
  over .

  
  Here is the data we captured in our driver (Printed the SGE details which was 
sent by OS)

  sgl_ptr->Address = f000 
  [14547.313240] 
  sgl_ptr->Length = 1000 
  [14547.313241] 
  sge_count = 18 
  [14547.313242] 
  cmd->index = 9d9

  
  Note : This issue is observed only when virtualization is enabled 

  Product : Broadcom (LSI) Megaraid H840 controller
  --- 
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw+ 1 root audio 116,  1 Oct 12 16:35 seq
   crw-rw+ 1 root audio 116, 33 Oct 12 16:35 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 18.04
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  MachineType: Dell Inc. PowerEdge R7415
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 mgadrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-8-generic 
root=UUID=43e89410-c7ff-11e8-9229-d094661013d8 ro
  ProcVersionSignature: Ubuntu 4.18.0-8.9~18.04.1-generic 4.18.7
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-8-generic N/A
   linux-backports-modules-4.18.0-8-generic  N/A
   linux-firmware1.173.1
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  Tags:  bionic uec-images
  Uname: Linux 4.18.0-8-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lxd plugdev sudo
  _MarkForUpload: True
  dmi.bios.date: 09/07/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.6.2
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 23
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.6.2:bd09/07/2018:svnDellInc.:pnPowerEdgeR7415:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct23:cvr:
  dmi.product.family: PowerEdge
  dmi.product.name: PowerEdge R7415
  dmi.product.sku: SKU=NotProvided;ModelName=PowerEdge R7415
  dmi.sys.vendor: Dell Inc.
  --- 
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw+ 1 root audio 116,  1 Oct 12 16:35 seq
   crw-rw+ 1 root audio 116, 33 Oct 12 16:35 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 18.04
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  MachineType: Dell Inc. PowerEdge R7415
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 mgadrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-8-generic 
root=UUID=43e89410-c7ff-11e8-9229-d094661013d8 ro
  ProcVersionSignature: Ubuntu 4.18.0-8.9~18.04.1-generic 4.18.7
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-8-generic N/A
   linux-backports-modules-4.18.0-8-generic  N/A
   linux-firmware1.173.1
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  Tags:  bionic uec-images
  Uname: Linux 4.18.0-8-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lxd plugdev sudo
  _MarkForUpload: True
  dmi.bios.date: 09/07/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.6.2
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 23
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.6.2:bd09/07/2018:svnDellInc.:pnPowerEdgeR7415:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct23:cvr:
  dmi.product.family: PowerEdge
  

[Kernel-packages] [Bug 1798056] [NEW] [Feature] Set kernel config - IPMI_PANIC_EVENT

2018-10-16 Thread Sujith Pandel
Private bug reported:

We have a requirement to trigger Panic event from Linux IPMI native
driver to BMC in case of kernel panic. To achieve this, linux IPMI
driver should be built with kernel config IPMI_PANIC_EVENT to be set.

However, it is not set with shipping Ubuntu version. 
Can we get this IPMI_PANIC_EVENT set with the future releases of Ubuntu 18.04?

I will update the business justification later.

** Affects: dell-poweredge
 Importance: Undecided
 Status: New

** Affects: linux (Ubuntu)
 Importance: Undecided
 Status: New

** Also affects: dell-poweredge
   Importance: Undecided
   Status: New

** Information type changed from Public to Private

-- 
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/1798056

Title:
  [Feature] Set kernel config - IPMI_PANIC_EVENT

Status in The Dell-poweredge project:
  New
Status in linux package in Ubuntu:
  New

Bug description:
  We have a requirement to trigger Panic event from Linux IPMI native
  driver to BMC in case of kernel panic. To achieve this, linux IPMI
  driver should be built with kernel config IPMI_PANIC_EVENT to be set.

  However, it is not set with shipping Ubuntu version. 
  Can we get this IPMI_PANIC_EVENT set with the future releases of Ubuntu 18.04?

  I will update the business justification later.

To manage notifications about this bug go to:
https://bugs.launchpad.net/dell-poweredge/+bug/1798056/+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 1795453] Re: IO's are issued with incorrect Scatter Gather Buffer

2018-10-15 Thread Sujith Pandel
@sasikumarpc - Ok. So when you say below v4.18 kernel fixes it, does it
mean with increased memory or is it with the same setup where the issue
was originally seen?

Issue resolved Kernel Version
-
4.18.0-8-generic

-- 
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/1795453

Title:
  IO's are issued with incorrect Scatter Gather Buffer

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  
  We have observed that OS is sending the IO's (SCSI Read/Write) with incorrect 
Scatter Gather Buffer address .

  i.e

   OS is sending the IO with 64 bit Scatter Gather Buffer address , such
  that if we add the length with buffer address then it causes the roll
  over .

  
  Here is the data we captured in our driver (Printed the SGE details which was 
sent by OS)

  sgl_ptr->Address = f000 
  [14547.313240] 
  sgl_ptr->Length = 1000 
  [14547.313241] 
  sge_count = 18 
  [14547.313242] 
  cmd->index = 9d9

  
  Note : This issue is observed only when virtualization is enabled 

  Product : Broadcom (LSI) Megaraid H840 controller
  --- 
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw+ 1 root audio 116,  1 Oct 12 16:35 seq
   crw-rw+ 1 root audio 116, 33 Oct 12 16:35 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 18.04
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  MachineType: Dell Inc. PowerEdge R7415
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 mgadrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-8-generic 
root=UUID=43e89410-c7ff-11e8-9229-d094661013d8 ro
  ProcVersionSignature: Ubuntu 4.18.0-8.9~18.04.1-generic 4.18.7
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-8-generic N/A
   linux-backports-modules-4.18.0-8-generic  N/A
   linux-firmware1.173.1
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  Tags:  bionic uec-images
  Uname: Linux 4.18.0-8-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lxd plugdev sudo
  _MarkForUpload: True
  dmi.bios.date: 09/07/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.6.2
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 23
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.6.2:bd09/07/2018:svnDellInc.:pnPowerEdgeR7415:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct23:cvr:
  dmi.product.family: PowerEdge
  dmi.product.name: PowerEdge R7415
  dmi.product.sku: SKU=NotProvided;ModelName=PowerEdge R7415
  dmi.sys.vendor: Dell Inc.
  --- 
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw+ 1 root audio 116,  1 Oct 12 16:35 seq
   crw-rw+ 1 root audio 116, 33 Oct 12 16:35 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 18.04
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  MachineType: Dell Inc. PowerEdge R7415
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 mgadrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-8-generic 
root=UUID=43e89410-c7ff-11e8-9229-d094661013d8 ro
  ProcVersionSignature: Ubuntu 4.18.0-8.9~18.04.1-generic 4.18.7
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-8-generic N/A
   linux-backports-modules-4.18.0-8-generic  N/A
   linux-firmware1.173.1
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  Tags:  bionic uec-images
  Uname: Linux 4.18.0-8-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lxd plugdev sudo
  _MarkForUpload: True
  dmi.bios.date: 09/07/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.6.2
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 23
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.6.2:bd09/07/2018:svnDellInc.:pnPowerEdgeR7415:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct23:cvr:
  dmi.product.family: PowerEdge
  dmi.product.name: PowerEdge R7415
  dmi.product.sku: 

[Kernel-packages] [Bug 1795453] Re: IO's are issued with incorrect Scatter Gather Buffer

2018-10-15 Thread Sujith Pandel
> Also another version (other than default version of Ubuntu 18.04.01)
of 4.15 kernel fixes the issue

Can you share this kernel version as well?

-- 
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/1795453

Title:
  IO's are issued with incorrect Scatter Gather Buffer

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  
  We have observed that OS is sending the IO's (SCSI Read/Write) with incorrect 
Scatter Gather Buffer address .

  i.e

   OS is sending the IO with 64 bit Scatter Gather Buffer address , such
  that if we add the length with buffer address then it causes the roll
  over .

  
  Here is the data we captured in our driver (Printed the SGE details which was 
sent by OS)

  sgl_ptr->Address = f000 
  [14547.313240] 
  sgl_ptr->Length = 1000 
  [14547.313241] 
  sge_count = 18 
  [14547.313242] 
  cmd->index = 9d9

  
  Note : This issue is observed only when virtualization is enabled 

  Product : Broadcom (LSI) Megaraid H840 controller
  --- 
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw+ 1 root audio 116,  1 Oct 12 16:35 seq
   crw-rw+ 1 root audio 116, 33 Oct 12 16:35 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 18.04
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  MachineType: Dell Inc. PowerEdge R7415
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 mgadrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-8-generic 
root=UUID=43e89410-c7ff-11e8-9229-d094661013d8 ro
  ProcVersionSignature: Ubuntu 4.18.0-8.9~18.04.1-generic 4.18.7
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-8-generic N/A
   linux-backports-modules-4.18.0-8-generic  N/A
   linux-firmware1.173.1
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  Tags:  bionic uec-images
  Uname: Linux 4.18.0-8-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lxd plugdev sudo
  _MarkForUpload: True
  dmi.bios.date: 09/07/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.6.2
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 23
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.6.2:bd09/07/2018:svnDellInc.:pnPowerEdgeR7415:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct23:cvr:
  dmi.product.family: PowerEdge
  dmi.product.name: PowerEdge R7415
  dmi.product.sku: SKU=NotProvided;ModelName=PowerEdge R7415
  dmi.sys.vendor: Dell Inc.
  --- 
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw+ 1 root audio 116,  1 Oct 12 16:35 seq
   crw-rw+ 1 root audio 116, 33 Oct 12 16:35 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 18.04
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  MachineType: Dell Inc. PowerEdge R7415
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 mgadrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-8-generic 
root=UUID=43e89410-c7ff-11e8-9229-d094661013d8 ro
  ProcVersionSignature: Ubuntu 4.18.0-8.9~18.04.1-generic 4.18.7
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-8-generic N/A
   linux-backports-modules-4.18.0-8-generic  N/A
   linux-firmware1.173.1
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  Tags:  bionic uec-images
  Uname: Linux 4.18.0-8-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lxd plugdev sudo
  _MarkForUpload: True
  dmi.bios.date: 09/07/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.6.2
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 23
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.6.2:bd09/07/2018:svnDellInc.:pnPowerEdgeR7415:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct23:cvr:
  dmi.product.family: PowerEdge
  dmi.product.name: PowerEdge R7415
  dmi.product.sku: SKU=NotProvided;ModelName=PowerEdge R7415
  dmi.sys.vendor: Dell Inc.
  --- 
  ProblemType: Bug
  

[Kernel-packages] [Bug 1795453] Re: IO's are issued with incorrect Scatter Gather Buffer

2018-10-15 Thread Sujith Pandel
sasikumarpc -
Can you share the specific kernel versions that you are using, where the issue 
is fixed?
Can you also share the logs of pass & failure cases?

-- 
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/1795453

Title:
  IO's are issued with incorrect Scatter Gather Buffer

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  
  We have observed that OS is sending the IO's (SCSI Read/Write) with incorrect 
Scatter Gather Buffer address .

  i.e

   OS is sending the IO with 64 bit Scatter Gather Buffer address , such
  that if we add the length with buffer address then it causes the roll
  over .

  
  Here is the data we captured in our driver (Printed the SGE details which was 
sent by OS)

  sgl_ptr->Address = f000 
  [14547.313240] 
  sgl_ptr->Length = 1000 
  [14547.313241] 
  sge_count = 18 
  [14547.313242] 
  cmd->index = 9d9

  
  Note : This issue is observed only when virtualization is enabled 

  Product : Broadcom (LSI) Megaraid H840 controller

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1795453/+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 1797587] [NEW] Intel NVMe drives timeout when nvme format is attempted

2018-10-12 Thread Sujith Pandel
Private bug reported:

Every time you run an nvme format on a Intel NVMe drive (whether
specifying the secure/crypto erase options or not), the format
apparently works (drive is wiped clean) but the drive's admin queue
(queue 0) times out, making the nvme device driver flag an error and
reset the controller.

Here's an example:
 
nvme-cli-1.5 # ./nvme format -l 0 /dev/nvme1
NVME Admin command error:ABORT_REQ(7)
nvme-cli-1.5 # dmesg|tail -1
[79725.404910] nvme nvme1: I/O 151 QID 0 timeout, reset controller

Patch required:
https://github.com/torvalds/linux/commit/62843c2e4226057c83f520c74fe9c81a1891c331

Request you to include the patch for LTS kernel 4.15 of Ubuntu 18.04

** Affects: dell-poweredge
 Importance: Undecided
 Status: New

** Affects: linux (Ubuntu)
 Importance: Undecided
 Status: New

** Information type changed from Public to Private

** Also affects: dell-poweredge
   Importance: Undecided
   Status: 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/1797587

Title:
  Intel NVMe drives timeout when nvme format is attempted

Status in The Dell-poweredge project:
  New
Status in linux package in Ubuntu:
  New

Bug description:
  Every time you run an nvme format on a Intel NVMe drive (whether
  specifying the secure/crypto erase options or not), the format
  apparently works (drive is wiped clean) but the drive's admin queue
  (queue 0) times out, making the nvme device driver flag an error and
  reset the controller.

  Here's an example:
   
  nvme-cli-1.5 # ./nvme format -l 0 /dev/nvme1
  NVME Admin command error:ABORT_REQ(7)
  nvme-cli-1.5 # dmesg|tail -1
  [79725.404910] nvme nvme1: I/O 151 QID 0 timeout, reset controller

  Patch required:
  
https://github.com/torvalds/linux/commit/62843c2e4226057c83f520c74fe9c81a1891c331

  Request you to include the patch for LTS kernel 4.15 of Ubuntu 18.04

To manage notifications about this bug go to:
https://bugs.launchpad.net/dell-poweredge/+bug/1797587/+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 1794110] Re: MPS (Max Payload Size) is not correctly programmed upon Hot Insertion NVMe PCIe SSD

2018-10-09 Thread Sujith Pandel
@jsalisbury -
Unfortunately we do not have that info in hand. I'll check if we can try 
getting it.

I see the patches in HWE 4.18 kernel of 18.04.2.
Thanks for including them in it.

-- 
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/1794110

Title:
  MPS (Max Payload Size) is not correctly programmed upon Hot Insertion
  NVMe PCIe SSD

Status in The Dell-poweredge project:
  New
Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Bionic:
  In Progress
Status in linux source package in Cosmic:
  In Progress

Bug description:
  Max Payload Size for the NVMe device is not getting programmed correctly. 
  The OS is trying to set the device MPS to match Root Port which is greater 
than Capability of Device, instead of looking for lowest common denominator. 

  This is fixed in upstream kernel version 4.19. Below are the commits that fix 
the issue. 
  Please help include them in Ubuntu releases.

  PCI: Skip MPS logic for Virtual Functions (VFs)
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/drivers/pci/probe.c?h=v4.19-rc2=3dbe97efe8bf450b183d6dee2305cbc032e6b8a4

  PCI: Match Root Port's MPS to endpoint's MPSS as necessary
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/drivers/pci/probe.c?h=v4.19-rc2=9f0e89359775ee21fe1ea732e34edb52aef5addf

To manage notifications about this bug go to:
https://bugs.launchpad.net/dell-poweredge/+bug/1794110/+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 1777674] Re: Ubuntu 18.04 hangs at "kvm: exiting hardware virtualization" on AMD servers with DVD

2018-10-09 Thread Sujith Pandel
reboot is triggered using #systemctl reboot.
systemd timeout of 30min does not help, system stays hung. Needs a manual 
power-reset.

-- 
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/1777674

Title:
  Ubuntu 18.04 hangs at "kvm: exiting hardware virtualization" on AMD
  servers with DVD

Status in dellserver:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in systemd package in Ubuntu:
  Incomplete
Status in linux source package in Bionic:
  Incomplete

Bug description:
  Ubuntu 18.04 hangs at "kvm: exiting hardware virtualization" on AMD
  servers when under graceful reboot stress for 12hrs.

  * This hand is observed only when Onboard SATA DVD Drive is connected.

  * Not seen with Ubuntu 16.04.4 (HWE kernel v4.13)

  * Seen with Ubuntu 18.04 (4.15.0-23-generic, 4.15.0-20-generic)

  Steps:
  Setup a DellEMC AMD server with Onboard DVD Drive, install Ubuntu 18.04 and 
start reboot stress
  After a few reboots, observe that the machine hangs at "kvm: exiting hardware 
virtualization" and does not proceed with reboot cycles.

  Only physical reset helps in continuing the reboot test.

To manage notifications about this bug go to:
https://bugs.launchpad.net/dellserver/+bug/1777674/+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 1796130] Re: Patches for Additional NVME Support

2018-10-09 Thread Sujith Pandel
Description:
These missing patches are basically to improve Ubuntu kernel support for NVMe 
Surprise Removel/hot-plug of NVMe disks.
The patch list shared and formed above is from comparing the 4.18 HWE kernel 
that is already present in the -proposed apt repo.
We would like to have these included into the HWE kernel 4.18 of 18.04.2

-- 
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/1796130

Title:
  Patches for  Additional NVME Support

Status in The Dell-poweredge project:
  New
Status in linux package in Ubuntu:
  Triaged
Status in linux source package in Bionic:
  Triaged
Status in linux source package in Cosmic:
  Triaged

Bug description:
  Dell is requesting these patches for inclusion into 18.04.2 for
  additional NVME support

  PCI: Check for PCIe Link downtraining
  
https://github.com/torvalds/linux/commit/2d1ce5ec2117d16047334a1aa4b62e0cfb5a0605

  
  PCI/AER: Add sysfs attributes to provide AER stats and breakdown
  https://github.com/torvalds/linux/commit/81aa5206f9a7

  
  PCI/AER: Honor "pcie_ports=native" even if HEST sets FIRMWARE_FIRST
  https://github.com/torvalds/linux/commit/7af02fcd84c1

  
  PCI/AER: Don't clear AER bits if error handling is Firmware-First
  https://github.com/torvalds/linux/commit/45687f96c112

  
  PCI: pciehp: Differentiate between surprise and safe removal
  
https://git.kernel.org/pub/scm/linux/kernel/git/helgaas/pci.git/commit/?h=pci/hotplug=e76ac5875f5d5848558edc79a0869bf20765fec3

To manage notifications about this bug go to:
https://bugs.launchpad.net/dell-poweredge/+bug/1796130/+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 1794110] Re: MPS (Max Payload Size) is not correctly programmed upon Hot Insertion NVMe PCIe SSD

2018-10-09 Thread Sujith Pandel
The cosmic test-kernel based on v4.18 is a Pass.
Please include them in planned HWE kernels of 18.04.2 that is based on v4.18.

The bionic test-kernel based on v4.15 is a Fail.
This requires a few more patches to be included.

-- 
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/1794110

Title:
  MPS (Max Payload Size) is not correctly programmed upon Hot Insertion
  NVMe PCIe SSD

Status in The Dell-poweredge project:
  New
Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Bionic:
  In Progress
Status in linux source package in Cosmic:
  In Progress

Bug description:
  Max Payload Size for the NVMe device is not getting programmed correctly. 
  The OS is trying to set the device MPS to match Root Port which is greater 
than Capability of Device, instead of looking for lowest common denominator. 

  This is fixed in upstream kernel version 4.19. Below are the commits that fix 
the issue. 
  Please help include them in Ubuntu releases.

  PCI: Skip MPS logic for Virtual Functions (VFs)
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/drivers/pci/probe.c?h=v4.19-rc2=3dbe97efe8bf450b183d6dee2305cbc032e6b8a4

  PCI: Match Root Port's MPS to endpoint's MPSS as necessary
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/drivers/pci/probe.c?h=v4.19-rc2=9f0e89359775ee21fe1ea732e34edb52aef5addf

To manage notifications about this bug go to:
https://bugs.launchpad.net/dell-poweredge/+bug/1794110/+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 1796631] [NEW] dcdbas: Add support for WSMT ACPI table

2018-10-08 Thread Sujith Pandel
Private bug reported:

Business case (Partner benefit):
Dell: dcdbas driver is used to raise SMIs. Dell System BIOS will implement 
support for WSMT table soon. This change in dcdbas driver will implement 
support for WSMT table.

Patch details:
If the WSMT ACPI table is present and indicates that a fixed communication 
buffer should be used, use the firmware-specified buffer instead of allocating 
a buffer in memory for communications between the dcdbas driver and firmare. 

https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-
next.git/commit/drivers/firmware?id=12c956c4f32e08799de452abe1e1ec6021b1e41f

For details on WSMT, please refer to the 'Links to ACPI-related
Documents' section below - http://www.uefi.org/acpi
https://msdn.microsoft.com/windows/hardware/drivers/bringup/acpi-system-
description-tables#wsmt

Requesting this patch to be included into Ubuntu 18.04.2 HWE kernels.

** Affects: dell-poweredge
 Importance: Undecided
 Status: New

** Affects: linux (Ubuntu)
 Importance: Undecided
 Status: New

** Information type changed from Public to Private

** Also affects: dell-poweredge
   Importance: Undecided
   Status: 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/1796631

Title:
  dcdbas: Add support for WSMT ACPI table

Status in The Dell-poweredge project:
  New
Status in linux package in Ubuntu:
  New

Bug description:
  Business case (Partner benefit):
  Dell: dcdbas driver is used to raise SMIs. Dell System BIOS will implement 
support for WSMT table soon. This change in dcdbas driver will implement 
support for WSMT table.

  Patch details:
  If the WSMT ACPI table is present and indicates that a fixed communication 
buffer should be used, use the firmware-specified buffer instead of allocating 
a buffer in memory for communications between the dcdbas driver and firmare. 

  https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-
  next.git/commit/drivers/firmware?id=12c956c4f32e08799de452abe1e1ec6021b1e41f

  For details on WSMT, please refer to the 'Links to ACPI-related
  Documents' section below - http://www.uefi.org/acpi
  https://msdn.microsoft.com/windows/hardware/drivers/bringup/acpi-
  system-description-tables#wsmt

  Requesting this patch to be included into Ubuntu 18.04.2 HWE kernels.

To manage notifications about this bug go to:
https://bugs.launchpad.net/dell-poweredge/+bug/1796631/+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 1794110] Re: MPS (Max Payload Size) is not correctly programmed upon Hot Insertion NVMe PCIe SSD

2018-10-02 Thread Sujith Pandel
Thank you for sharing a test-kernel.
We will test it and revert back here with test-results.

Thanks,
Sujith

-- 
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/1794110

Title:
  MPS (Max Payload Size) is not correctly programmed upon Hot Insertion
  NVMe PCIe SSD

Status in The Dell-poweredge project:
  New
Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Bionic:
  In Progress
Status in linux source package in Cosmic:
  In Progress

Bug description:
  Max Payload Size for the NVMe device is not getting programmed correctly. 
  The OS is trying to set the device MPS to match Root Port which is greater 
than Capability of Device, instead of looking for lowest common denominator. 

  This is fixed in upstream kernel version 4.19. Below are the commits that fix 
the issue. 
  Please help include them in Ubuntu releases.

  PCI: Skip MPS logic for Virtual Functions (VFs)
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/drivers/pci/probe.c?h=v4.19-rc2=3dbe97efe8bf450b183d6dee2305cbc032e6b8a4

  PCI: Match Root Port's MPS to endpoint's MPSS as necessary
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/drivers/pci/probe.c?h=v4.19-rc2=9f0e89359775ee21fe1ea732e34edb52aef5addf

To manage notifications about this bug go to:
https://bugs.launchpad.net/dell-poweredge/+bug/1794110/+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 1794110] [NEW] MPS (Max Payload Size) is not correctly programmed upon Hot Insertion NVMe PCIe SSD

2018-09-24 Thread Sujith Pandel
Public bug reported:

Max Payload Size for the NVMe device is not getting programmed correctly. 
The OS is trying to set the device MPS to match Root Port which is greater than 
Capability of Device, instead of looking for lowest common denominator. 

This is fixed in upstream kernel version 4.19. Below are the commits that fix 
the issue. 
Please help include them in Ubuntu releases.

PCI: Skip MPS logic for Virtual Functions (VFs)
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/drivers/pci/probe.c?h=v4.19-rc2=3dbe97efe8bf450b183d6dee2305cbc032e6b8a4

PCI: Match Root Port's MPS to endpoint's MPSS as necessary
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/drivers/pci/probe.c?h=v4.19-rc2=9f0e89359775ee21fe1ea732e34edb52aef5addf

** Affects: dell-poweredge
 Importance: Undecided
 Status: New

** Affects: linux (Ubuntu)
 Importance: Undecided
 Status: Incomplete

** Also affects: dell-poweredge
   Importance: Undecided
   Status: 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/1794110

Title:
  MPS (Max Payload Size) is not correctly programmed upon Hot Insertion
  NVMe PCIe SSD

Status in The Dell-poweredge project:
  New
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Max Payload Size for the NVMe device is not getting programmed correctly. 
  The OS is trying to set the device MPS to match Root Port which is greater 
than Capability of Device, instead of looking for lowest common denominator. 

  This is fixed in upstream kernel version 4.19. Below are the commits that fix 
the issue. 
  Please help include them in Ubuntu releases.

  PCI: Skip MPS logic for Virtual Functions (VFs)
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/drivers/pci/probe.c?h=v4.19-rc2=3dbe97efe8bf450b183d6dee2305cbc032e6b8a4

  PCI: Match Root Port's MPS to endpoint's MPSS as necessary
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/drivers/pci/probe.c?h=v4.19-rc2=9f0e89359775ee21fe1ea732e34edb52aef5addf

To manage notifications about this bug go to:
https://bugs.launchpad.net/dell-poweredge/+bug/1794110/+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 1772434] Re: Broadcom: IT (HBA) Driver Enablement in 18.04 (Patches)

2018-08-19 Thread Sujith Pandel
Can you guys share the release plans for kernel-4.15.0-33.36?
We have a installation/boot failure with HBA330 and the patches in this list 
are fixing it.

-- 
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/1772434

Title:
  Broadcom:  IT (HBA) Driver Enablement in 18.04 (Patches)

Status in dellserver:
  In Progress
Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Bionic:
  In Progress

Bug description:
  The purpose of this bug is to track the patches needed to enable the
  IT (HBA) driver into 18.04.

  Below are upstream commit ids of IT driver which went in over the in-
  box driver of Ubuntu18.04 OS’s base kernel,


  864449eea7c600596e305ffdc4a6a846414b222c scsi: mpt3sas: Do not mark
  fw_event workqueue as WQ_MEM_RECLAIM

  6f9e09fd6488de7661ee20efb5d8ab4e05a59735 scsi: mpt3sas: clarify mmio
  pointer types

  40114bde9773ccaf9ad77233ac2cc9039f0f2941 scsi: mpt3sas: Do not use
  32-bit atomic request descriptor for Ventura controllers.

  b4472d7180894c96b6133ef5ff3df50836591eaa scsi: mpt3sas: Introduce
  function to clone mpi reply.

  e5747439366c1079257083f231f5dd9a84bf0fd7 scsi: mpt3sas: Introduce
  function to clone mpi request.

  182ac784b41faee02e8b44cd7149575258ad6858 scsi: mpt3sas: Introduce Base
  function for cloning.

  22ae5a3c2599381cf7aaa5aca25c515a3166adcc scsi: mpt3sas: Introduce API
  to get BAR0 mapped buffer address

  0448f0195124e33f11d15b7d1e1cab959989eee7 scsi: mpt3sas: Configure
  reply post queue depth, DMA and sgl tablesize.

  c520691b38cde1d94f53e5782feba892f5645043 scsi: mpt3sas: Add PCI device
  ID for Andromeda.

  4a8842de8db4953fdda7866626b78b12fb8adb97 scsi: mpt3sas: fix an out of
  bound write

  61dfb8a5fb7e93e692856026fa4c778a27f28984 scsi: mpt3sas: make function
  _get_st_from_smid static

  dbec4c9040edc15442c3ebdb65408aa9d3b82c24 scsi: mpt3sas: lockless
  command submission

  272e253c7bcabfeef5f4d0aaed94a413e13e520f scsi: mpt3sas: simplify
  _wait_for_commands_to_complete()

  6da999fe5a9285c2a78f3cf1e768abcd48d7607e scsi: mpt3sas: simplify
  mpt3sas_scsi_issue_tm()

  74fcfa5371b7a681e864d3a9d3b9ecfd5737d8ea scsi: mpt3sas: simplify task
  management functions

  b0cd285eb57cd3cb18d882565c22d39bccffe7f0 scsi: mpt3sas: always use
  first reserved smid for ioctl passthrough

  9961c9bbf2b43acaaf030a0fbabc9954d937ad8c scsi: mpt3sas: check command
  status before attempting abort

  12e7c6782bc58128392b768fc2a87b230414a2a5 scsi: mpt3sas: Introduce
  mpt3sas_get_st_from_smid()

  02a386df3678275b01eec71fee39735c379e4a2a scsi: mpt3sas: open-code
  _scsih_scsi_lookup_get()

  6a2d4618aef3d4ffb83514e5e58a091d61e54a03 scsi: mpt3sas: separate out
  _base_recovery_check()

  05303dfb738066ad597d7feb422ff9fa2d3d8ef3 scsi: mpt3sas: use
  list_splice_init()

  ba4494d47bd02e5757b449a2ccfa3ff87bc8 scsi: mpt3sas: set default
  value for cb_idx

  f49d4aed1315a7b766d855f1367142e682b0cc87 scsi: mpt3sas: Proper
  handling of set/clear of "ATA command pending" flag.

  45b7aef7fb7d5f5bfa3a2a6727f1accf7660f6fd scsi: mpt3sas: Remove unused
  variable requeue_event

To manage notifications about this bug go to:
https://bugs.launchpad.net/dellserver/+bug/1772434/+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 1777674] Re: Ubuntu 18.04 hangs at "kvm: exiting hardware virtualization" on AMD servers with DVD

2018-07-16 Thread Sujith Pandel
Any update on this?

-- 
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/1777674

Title:
  Ubuntu 18.04 hangs at "kvm: exiting hardware virtualization" on AMD
  servers with DVD

Status in dellserver:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in systemd package in Ubuntu:
  New
Status in linux source package in Bionic:
  Incomplete
Status in systemd source package in Bionic:
  New

Bug description:
  Ubuntu 18.04 hangs at "kvm: exiting hardware virtualization" on AMD
  servers when under graceful reboot stress for 12hrs.

  * This hand is observed only when Onboard SATA DVD Drive is connected.

  * Not seen with Ubuntu 16.04.4 (HWE kernel v4.13)

  * Seen with Ubuntu 18.04 (4.15.0-23-generic, 4.15.0-20-generic)

  Steps:
  Setup a DellEMC AMD server with Onboard DVD Drive, install Ubuntu 18.04 and 
start reboot stress
  After a few reboots, observe that the machine hangs at "kvm: exiting hardware 
virtualization" and does not proceed with reboot cycles.

  Only physical reset helps in continuing the reboot test.

To manage notifications about this bug go to:
https://bugs.launchpad.net/dellserver/+bug/1777674/+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 1779605] Re: [Ubuntu 18.04] Error parsing PCC subspaces from PPCT" is splashed to screen

2018-07-09 Thread Sujith Pandel
** Attachment added: "dmesg - test-kernel"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1779605/+attachment/5161476/+files/dmesg-test-kernel.txt

-- 
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/1779605

Title:
  [Ubuntu 18.04] Error parsing PCC subspaces from PPCT" is splashed to
  screen

Status in dellserver:
  New
Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Bionic:
  In Progress

Bug description:
  When installing and booting to Ubuntu 18.04 Server, we see this error
  being shown on screen (Attached Screenshot)

  Setup details- Take a DellEMC 14G server and start installation of
  Ubuntu 18.04 Server. Observe this message in #dmesg.

  Cosmetic error message, no functionality loss.

  Upstream patch details:
  https://www.spinics.net/lists/linux-acpi/msg81863.html
  Please include these in future builds of Ubuntu 18.04.

  Uploading the #dmesg logs.

To manage notifications about this bug go to:
https://bugs.launchpad.net/dellserver/+bug/1779605/+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 1779605] Re: [Ubuntu 18.04] Error parsing PCC subspaces from PPCT" is splashed to screen

2018-07-09 Thread Sujith Pandel
Verified the test-kernel shared in the above link on the same setup
where the issue was seen with bionic kernels.

Uploading dmesg.

Issue seems to be fixed and change observed now is:

[0.229581] Detected 1 PCC Subspaces
[0.229581] Registering PCC driver as Mailbox controller

-- 
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/1779605

Title:
  [Ubuntu 18.04] Error parsing PCC subspaces from PPCT" is splashed to
  screen

Status in dellserver:
  New
Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Bionic:
  In Progress

Bug description:
  When installing and booting to Ubuntu 18.04 Server, we see this error
  being shown on screen (Attached Screenshot)

  Setup details- Take a DellEMC 14G server and start installation of
  Ubuntu 18.04 Server. Observe this message in #dmesg.

  Cosmetic error message, no functionality loss.

  Upstream patch details:
  https://www.spinics.net/lists/linux-acpi/msg81863.html
  Please include these in future builds of Ubuntu 18.04.

  Uploading the #dmesg logs.

To manage notifications about this bug go to:
https://bugs.launchpad.net/dellserver/+bug/1779605/+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 1779605] Re: [Ubuntu 18.04] Error parsing PCC subspaces from PPCT" is splashed to screen

2018-07-05 Thread Sujith Pandel
The v4 was proposed and applied:
https://patchwork.kernel.org/patch/10404957/

I feel only the 3/3 (3rd patch in whole series) is enough to deal with this bug.
If you could give me a test kernel, I shall verify it and confirm it here.

-- 
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/1779605

Title:
  [Ubuntu 18.04] Error parsing PCC subspaces from PPCT" is splashed to
  screen

Status in dellserver:
  New
Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Bionic:
  In Progress

Bug description:
  When installing and booting to Ubuntu 18.04 Server, we see this error
  being shown on screen (Attached Screenshot)

  Setup details- Take a DellEMC 14G server and start installation of
  Ubuntu 18.04 Server. Observe this message in #dmesg.

  Cosmetic error message, no functionality loss.

  Upstream patch details:
  https://www.spinics.net/lists/linux-acpi/msg81863.html
  Please include these in future builds of Ubuntu 18.04.

  Uploading the #dmesg logs.

To manage notifications about this bug go to:
https://bugs.launchpad.net/dellserver/+bug/1779605/+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 1748689] Re: Mounting SMB shares with vers=3.0 in fstab gives "ioctl error in smb2_get_dfs_refer rc=-2"

2018-07-02 Thread Sujith Pandel
** Also affects: dellserver
   Importance: Undecided
   Status: 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/1748689

Title:
  Mounting SMB shares with vers=3.0 in fstab gives "ioctl error in
  smb2_get_dfs_refer rc=-2"

Status in dellserver:
  New
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Xubuntu 17.10 artful
  Kernel: x86_64 Linux 4.13.0-32.35-generic
  cifs-utils 2:6.7-1
  smbclient  2:4.6.7+dfsg-1ubuntu3.1

  Mounting an SMB share with
  
sec=ntlmssp,vers=3.0,credentials=/home/.smbcredentials,dir_mode=0777,file_mode=0777

  in /etc/fstab gives the error: "CIFS VFS: ioctl error in
  smb2_get_dfs_refer rc=-2" in dmesg.

  Shares mounted this way are readable, but writing data to them (or using 
programs such as EasyTAG to write to them) ultimately fails. This bug did not 
occur in kernel 4.10. Mounting the share(s) with vers=1.0 does not give the 
error, but this is a haphazard fix as SMB v3.0 carries many security features 
with it not avaliable in SMB 1.0.
  --- 
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 17.10
  HibernationDevice: RESUME=/dev/mapper/DeusVitam--vg-swap_1
  JournalErrors:
   Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] 
failed with exit code 1: Hint: You are currently not seeing messages from other 
users and the system.
 Users in the 'systemd-journal' group can see all messages. Pass -q to
 turn off this notice.
   No journal files were opened due to insufficient permissions.
  MachineType: ASUS All Series
  Package: linux (not installed)
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic 
root=/dev/mapper/hostname--vg-root ro splash quiet amdgpu.cik_support=1 
vt.handoff=7
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-32-generic N/A
   linux-backports-modules-4.13.0-32-generic  N/A
   linux-firmware 1.169.3
  RfKill:
   
  Tags:  artful
  Uname: Linux 4.13.0-32-generic x86_64
  UpgradeStatus: Upgraded to artful on 2018-02-05 (7 days ago)
  UserGroups: libvirt libvirtd sudo wireshark
  WifiSyslog:
   
  _MarkForUpload: True
  dmi.bios.date: 03/16/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0701
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z97-E/USB 3.1
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0701:bd03/16/2016:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ97-E/USB3.1:rvrRevX.0x:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: ASUS MB
  dmi.product.name: All Series
  dmi.product.version: System Version
  dmi.sys.vendor: ASUS

To manage notifications about this bug go to:
https://bugs.launchpad.net/dellserver/+bug/1748689/+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 1779605] Re: [Ubuntu 18.04] Error parsing PCC subspaces from PPCT" is splashed to screen

2018-07-02 Thread Sujith Pandel
Moving back to 'Confirmed' as mentioned in c#3, since dmesg logs are already 
attached. 
If more logs are required, please let me know.

** Changed in: linux (Ubuntu)
   Status: Incomplete => Confirmed

-- 
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/1779605

Title:
  [Ubuntu 18.04] Error parsing PCC subspaces from PPCT" is splashed to
  screen

Status in dellserver:
  New
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  When installing and booting to Ubuntu 18.04 Server, we see this error
  being shown on screen (Attached Screenshot)

  Setup details- Take a DellEMC 14G server and start installation of
  Ubuntu 18.04 Server. Observe this message in #dmesg.

  Cosmetic error message, no functionality loss.

  Upstream patch details:
  https://www.spinics.net/lists/linux-acpi/msg81863.html
  Please include these in future builds of Ubuntu 18.04.

  Uploading the #dmesg logs.

To manage notifications about this bug go to:
https://bugs.launchpad.net/dellserver/+bug/1779605/+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 1779605] Re: [Ubuntu 18.04] Error parsing PCC subspaces from PPCT" is splashed to screen

2018-07-01 Thread Sujith Pandel
** Attachment added: "Screenshot"
   
https://bugs.launchpad.net/dellserver/+bug/1779605/+attachment/5158528/+files/PCCT_error.jpg

-- 
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/1779605

Title:
  [Ubuntu 18.04] Error parsing PCC subspaces from PPCT" is splashed to
  screen

Status in dellserver:
  New
Status in linux package in Ubuntu:
  New

Bug description:
  When installing and booting to Ubuntu 18.04 Server, we see this error
  being shown on screen (Attached Screenshot)

  Setup details- Take a DellEMC 14G server and start installation of
  Ubuntu 18.04 Server. Observe this message in #dmesg.

  Cosmetic error message, no functionality loss.

  Upstream patch details:
  https://www.spinics.net/lists/linux-acpi/msg81863.html
  Please include these in future builds of Ubuntu 18.04.

  Uploading the #dmesg logs.

To manage notifications about this bug go to:
https://bugs.launchpad.net/dellserver/+bug/1779605/+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 1779605] [NEW] [Ubuntu 18.04] Error parsing PCC subspaces from PPCT" is splashed to screen

2018-07-01 Thread Sujith Pandel
Public bug reported:

When installing and booting to Ubuntu 18.04 Server, we see this error
being shown on screen (Attached Screenshot)

Setup details- Take a DellEMC 14G server and start installation of
Ubuntu 18.04 Server. Observe this message in #dmesg.

Cosmetic error message, no functionality loss.

Upstream patch details:
https://www.spinics.net/lists/linux-acpi/msg81863.html
Please include these in future builds of Ubuntu 18.04.

Uploading the #dmesg logs.

** Affects: dellserver
 Importance: Undecided
 Status: New

** Affects: linux (Ubuntu)
 Importance: Undecided
 Status: New

** Attachment added: "dmesg"
   https://bugs.launchpad.net/bugs/1779605/+attachment/5158527/+files/dmesg.txt

** Also affects: dellserver
   Importance: Undecided
   Status: 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/1779605

Title:
  [Ubuntu 18.04] Error parsing PCC subspaces from PPCT" is splashed to
  screen

Status in dellserver:
  New
Status in linux package in Ubuntu:
  New

Bug description:
  When installing and booting to Ubuntu 18.04 Server, we see this error
  being shown on screen (Attached Screenshot)

  Setup details- Take a DellEMC 14G server and start installation of
  Ubuntu 18.04 Server. Observe this message in #dmesg.

  Cosmetic error message, no functionality loss.

  Upstream patch details:
  https://www.spinics.net/lists/linux-acpi/msg81863.html
  Please include these in future builds of Ubuntu 18.04.

  Uploading the #dmesg logs.

To manage notifications about this bug go to:
https://bugs.launchpad.net/dellserver/+bug/1779605/+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 1748689] Re: Mounting SMB shares with vers=3.0 in fstab gives "ioctl error in smb2_get_dfs_refer rc=-2"

2018-06-27 Thread Sujith Pandel
I see this on 4.13.0-45-generic of Ubuntu 16.04 HWE kernels.

-- 
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/1748689

Title:
  Mounting SMB shares with vers=3.0 in fstab gives "ioctl error in
  smb2_get_dfs_refer rc=-2"

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Xubuntu 17.10 artful
  Kernel: x86_64 Linux 4.13.0-32.35-generic
  cifs-utils 2:6.7-1
  smbclient  2:4.6.7+dfsg-1ubuntu3.1

  Mounting an SMB share with
  
sec=ntlmssp,vers=3.0,credentials=/home/.smbcredentials,dir_mode=0777,file_mode=0777

  in /etc/fstab gives the error: "CIFS VFS: ioctl error in
  smb2_get_dfs_refer rc=-2" in dmesg.

  Shares mounted this way are readable, but writing data to them (or using 
programs such as EasyTAG to write to them) ultimately fails. This bug did not 
occur in kernel 4.10. Mounting the share(s) with vers=1.0 does not give the 
error, but this is a haphazard fix as SMB v3.0 carries many security features 
with it not avaliable in SMB 1.0.
  --- 
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 17.10
  HibernationDevice: RESUME=/dev/mapper/DeusVitam--vg-swap_1
  JournalErrors:
   Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] 
failed with exit code 1: Hint: You are currently not seeing messages from other 
users and the system.
 Users in the 'systemd-journal' group can see all messages. Pass -q to
 turn off this notice.
   No journal files were opened due to insufficient permissions.
  MachineType: ASUS All Series
  Package: linux (not installed)
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic 
root=/dev/mapper/hostname--vg-root ro splash quiet amdgpu.cik_support=1 
vt.handoff=7
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-32-generic N/A
   linux-backports-modules-4.13.0-32-generic  N/A
   linux-firmware 1.169.3
  RfKill:
   
  Tags:  artful
  Uname: Linux 4.13.0-32-generic x86_64
  UpgradeStatus: Upgraded to artful on 2018-02-05 (7 days ago)
  UserGroups: libvirt libvirtd sudo wireshark
  WifiSyslog:
   
  _MarkForUpload: True
  dmi.bios.date: 03/16/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0701
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z97-E/USB 3.1
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0701:bd03/16/2016:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ97-E/USB3.1:rvrRevX.0x:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: ASUS MB
  dmi.product.name: All Series
  dmi.product.version: System Version
  dmi.sys.vendor: ASUS

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1748689/+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 1778717] Re: Ubuntu 18.04 guest hangs during diskio stress

2018-06-26 Thread Sujith Pandel
Moving back to Confirmed state - since all the available logs are
already uploaded.

** Changed in: linux (Ubuntu)
   Status: Incomplete => Confirmed

-- 
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/1778717

Title:
  Ubuntu 18.04 guest hangs during diskio stress

Status in dellserver:
  New
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Setup - A Dell EMC 14th Gen AMD server, with ESXi 6.7 as host and
  Ubuntu 18.04 (latest updates) guest.

  Guest has 3 data disks apart from the boot disk. All these disks are exposed 
through "ParaVirtual SCSI controller" from the host ESXi 6.7.
  Run diskio stress on all the 3 data disks for overnight.
  Guest goes unresponsive (even ping fails) in between.
  Only way to recover is to reset the guest.

  Logs do not indicate much on this error.
  Rarely we get a crash on the Guest-screen. Attaching 2 screenshots of 
different hits.

  We have tried mainline kernel v4.18-rc-2 and have hit the issue there
  as well.

  Changing the SCSI controller to "LSI Logic SAS adapter" helps and we
  have not seen any crash/hang here.

To manage notifications about this bug go to:
https://bugs.launchpad.net/dellserver/+bug/1778717/+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 1778717] Re: Ubuntu 18.04 guest hangs during diskio stress

2018-06-26 Thread Sujith Pandel
* Also hit with 16.04.4 HWE kernel 4.13.0-45-generic.

* Not seen with LTS kernel 4.4 of Ubuntu 16.04

** Also affects: dellserver
   Importance: Undecided
   Status: 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/1778717

Title:
  Ubuntu 18.04 guest hangs during diskio stress

Status in dellserver:
  New
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Setup - A Dell EMC 14th Gen AMD server, with ESXi 6.7 as host and
  Ubuntu 18.04 (latest updates) guest.

  Guest has 3 data disks apart from the boot disk. All these disks are exposed 
through "ParaVirtual SCSI controller" from the host ESXi 6.7.
  Run diskio stress on all the 3 data disks for overnight.
  Guest goes unresponsive (even ping fails) in between.
  Only way to recover is to reset the guest.

  Logs do not indicate much on this error.
  Rarely we get a crash on the Guest-screen. Attaching 2 screenshots of 
different hits.

  We have tried mainline kernel v4.18-rc-2 and have hit the issue there
  as well.

  Changing the SCSI controller to "LSI Logic SAS adapter" helps and we
  have not seen any crash/hang here.

To manage notifications about this bug go to:
https://bugs.launchpad.net/dellserver/+bug/1778717/+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 1778717] Re: Ubuntu 18.04 guest hangs during diskio stress

2018-06-26 Thread Sujith Pandel
** Attachment added: "screenshot-2"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1778717/+attachment/5156771/+files/image-2018-06-22-14-48-57-801.png

-- 
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/1778717

Title:
  Ubuntu 18.04 guest hangs during diskio stress

Status in dellserver:
  New
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Setup - A Dell EMC 14th Gen AMD server, with ESXi 6.7 as host and
  Ubuntu 18.04 (latest updates) guest.

  Guest has 3 data disks apart from the boot disk. All these disks are exposed 
through "ParaVirtual SCSI controller" from the host ESXi 6.7.
  Run diskio stress on all the 3 data disks for overnight.
  Guest goes unresponsive (even ping fails) in between.
  Only way to recover is to reset the guest.

  Logs do not indicate much on this error.
  Rarely we get a crash on the Guest-screen. Attaching 2 screenshots of 
different hits.

  We have tried mainline kernel v4.18-rc-2 and have hit the issue there
  as well.

  Changing the SCSI controller to "LSI Logic SAS adapter" helps and we
  have not seen any crash/hang here.

To manage notifications about this bug go to:
https://bugs.launchpad.net/dellserver/+bug/1778717/+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 1778717] Re: Ubuntu 18.04 guest hangs during diskio stress

2018-06-26 Thread Sujith Pandel
** Attachment added: "screenshot-1"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1778717/+attachment/5156770/+files/image-2018-06-25-10-13-05-871.png

-- 
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/1778717

Title:
  Ubuntu 18.04 guest hangs during diskio stress

Status in dellserver:
  New
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Setup - A Dell EMC 14th Gen AMD server, with ESXi 6.7 as host and
  Ubuntu 18.04 (latest updates) guest.

  Guest has 3 data disks apart from the boot disk. All these disks are exposed 
through "ParaVirtual SCSI controller" from the host ESXi 6.7.
  Run diskio stress on all the 3 data disks for overnight.
  Guest goes unresponsive (even ping fails) in between.
  Only way to recover is to reset the guest.

  Logs do not indicate much on this error.
  Rarely we get a crash on the Guest-screen. Attaching 2 screenshots of 
different hits.

  We have tried mainline kernel v4.18-rc-2 and have hit the issue there
  as well.

  Changing the SCSI controller to "LSI Logic SAS adapter" helps and we
  have not seen any crash/hang here.

To manage notifications about this bug go to:
https://bugs.launchpad.net/dellserver/+bug/1778717/+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 1778717] [NEW] Ubuntu 18.04 guest hangs during diskio stress

2018-06-26 Thread Sujith Pandel
Public bug reported:

Setup - A Dell EMC 14th Gen AMD server, with ESXi 6.7 as host and Ubuntu
18.04 (latest updates) guest.

Guest has 3 data disks apart from the boot disk. All these disks are exposed 
through "ParaVirtual SCSI controller" from the host ESXi 6.7.
Run diskio stress on all the 3 data disks for overnight.
Guest goes unresponsive (even ping fails) in between.
Only way to recover is to reset the guest.

Logs do not indicate much on this error.
Rarely we get a crash on the Guest-screen. Attaching 2 screenshots of different 
hits.

We have tried mainline kernel v4.18-rc-2 and have hit the issue there as
well.

Changing the SCSI controller to "LSI Logic SAS adapter" helps and we
have not seen any crash/hang here.

** Affects: dellserver
 Importance: Undecided
 Status: New

** Affects: linux (Ubuntu)
 Importance: Undecided
 Status: Confirmed


** Tags: bionic

** Attachment added: "log files inside /var/log/"
   
https://bugs.launchpad.net/bugs/1778717/+attachment/5156769/+files/var-log-ubuntu1804-vm.zip

-- 
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/1778717

Title:
  Ubuntu 18.04 guest hangs during diskio stress

Status in dellserver:
  New
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Setup - A Dell EMC 14th Gen AMD server, with ESXi 6.7 as host and
  Ubuntu 18.04 (latest updates) guest.

  Guest has 3 data disks apart from the boot disk. All these disks are exposed 
through "ParaVirtual SCSI controller" from the host ESXi 6.7.
  Run diskio stress on all the 3 data disks for overnight.
  Guest goes unresponsive (even ping fails) in between.
  Only way to recover is to reset the guest.

  Logs do not indicate much on this error.
  Rarely we get a crash on the Guest-screen. Attaching 2 screenshots of 
different hits.

  We have tried mainline kernel v4.18-rc-2 and have hit the issue there
  as well.

  Changing the SCSI controller to "LSI Logic SAS adapter" helps and we
  have not seen any crash/hang here.

To manage notifications about this bug go to:
https://bugs.launchpad.net/dellserver/+bug/1778717/+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 1777674] Re: Ubuntu 18.04 hangs at "kvm: exiting hardware virtualization" on AMD servers

2018-06-20 Thread Sujith Pandel
I think I narrowed it down to these:
v4.14 - No issue observed
v4.15-rc-1 - Issue observed

Wherever the issue is observed, if I blacklist or rmmod ahci driver
before reboot, no issue is observed (because the SATA ODD is gone now).

-- 
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/1777674

Title:
  Ubuntu 18.04 hangs at "kvm: exiting hardware virtualization" on AMD
  servers

Status in dellserver:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in systemd package in Ubuntu:
  New
Status in linux source package in Bionic:
  Incomplete
Status in systemd source package in Bionic:
  New

Bug description:
  Ubuntu 18.04 hangs at "kvm: exiting hardware virtualization" on AMD
  servers when under graceful reboot stress for 12hrs.

  * This hand is observed only when Onboard SATA DVD Drive is connected.

  * Not seen with Ubuntu 16.04.4 (HWE kernel v4.13)

  * Seen with Ubuntu 18.04 (4.15.0-23-generic, 4.15.0-20-generic)

  Steps:
  Setup a DellEMC AMD server with Onboard DVD Drive, install Ubuntu 18.04 and 
start reboot stress
  After a few reboots, observe that the machine hangs at "kvm: exiting hardware 
virtualization" and does not proceed with reboot cycles.

  Only physical reset helps in continuing the reboot test.

To manage notifications about this bug go to:
https://bugs.launchpad.net/dellserver/+bug/1777674/+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 1777674] Re: Ubuntu 18.04 hangs at "kvm: exiting hardware virtualization" on AMD servers

2018-06-20 Thread Sujith Pandel
I am observing that in the absence of any network (interfaces not
configured for dhcp/static) I can see the graceful reboot halting almost
every reboot.

* Issue is observed with Ubuntu 18.04 kernel 4.15.0-23-generic
* Also observed with 4.18-rc1 hosted at 
http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.18-rc1

Attaching the log which contains failure for both these cases.

Do you think systemd could be the suspect?

** Attachment added: "4.18 fail and 4.15.0-23 fail"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1777674/+attachment/5154491/+files/nf_odd.log

-- 
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/1777674

Title:
  Ubuntu 18.04 hangs at "kvm: exiting hardware virtualization" on AMD
  servers

Status in dellserver:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in systemd package in Ubuntu:
  New
Status in linux source package in Bionic:
  Incomplete
Status in systemd source package in Bionic:
  New

Bug description:
  Ubuntu 18.04 hangs at "kvm: exiting hardware virtualization" on AMD
  servers when under graceful reboot stress for 12hrs.

  * This hand is observed only when Onboard SATA DVD Drive is connected.

  * Not seen with Ubuntu 16.04.4 (HWE kernel v4.13)

  * Seen with Ubuntu 18.04 (4.15.0-23-generic, 4.15.0-20-generic)

  Steps:
  Setup a DellEMC AMD server with Onboard DVD Drive, install Ubuntu 18.04 and 
start reboot stress
  After a few reboots, observe that the machine hangs at "kvm: exiting hardware 
virtualization" and does not proceed with reboot cycles.

  Only physical reset helps in continuing the reboot test.

To manage notifications about this bug go to:
https://bugs.launchpad.net/dellserver/+bug/1777674/+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 1777674] Re: Ubuntu 18.04 hangs at "kvm: exiting hardware virtualization" on AMD servers

2018-06-19 Thread Sujith Pandel
Update:
I was under the assumption that kvm/kvm_amd module was the suspect.
But I was wrong.
Reason - I tried performing '#modprobe -r kvm_amd kvm' before issuing 
'#systemctl reboot' in the reboot script and the system still halted with 
Ubuntu 18.04 kernel.

@jsalisbury -
I will keep it today and update you by tomorrow.

-- 
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/1777674

Title:
  Ubuntu 18.04 hangs at "kvm: exiting hardware virtualization" on AMD
  servers

Status in dellserver:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in systemd package in Ubuntu:
  New
Status in linux source package in Bionic:
  Incomplete
Status in systemd source package in Bionic:
  New

Bug description:
  Ubuntu 18.04 hangs at "kvm: exiting hardware virtualization" on AMD
  servers when under graceful reboot stress for 12hrs.

  * This hand is observed only when Onboard SATA DVD Drive is connected.

  * Not seen with Ubuntu 16.04.4 (HWE kernel v4.13)

  * Seen with Ubuntu 18.04 (4.15.0-23-generic, 4.15.0-20-generic)

  Steps:
  Setup a DellEMC AMD server with Onboard DVD Drive, install Ubuntu 18.04 and 
start reboot stress
  After a few reboots, observe that the machine hangs at "kvm: exiting hardware 
virtualization" and does not proceed with reboot cycles.

  Only physical reset helps in continuing the reboot test.

To manage notifications about this bug go to:
https://bugs.launchpad.net/dellserver/+bug/1777674/+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 1777674] Re: Ubuntu 18.04 hangs at "kvm: exiting hardware virtualization" on AMD servers

2018-06-19 Thread Sujith Pandel
Moving the bug-report back to Confirmed since these logs like "kvm exiting 
hardware virt" and the logs post this are not stored on the physical disks 
(reason - disks are already unmounted).
Such logs are available only in the console logs which are already uploaded in 
this report.

** Changed in: linux (Ubuntu)
   Status: Incomplete => Confirmed

** Changed in: linux (Ubuntu)
   Status: Confirmed => New

** Changed in: linux (Ubuntu)
   Status: New => Confirmed

-- 
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/1777674

Title:
  Ubuntu 18.04 hangs at "kvm: exiting hardware virtualization" on AMD
  servers

Status in dellserver:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  New

Bug description:
  Ubuntu 18.04 hangs at "kvm: exiting hardware virtualization" on AMD
  servers when under graceful reboot stress for 12hrs.

  * This hand is observed only when Onboard SATA DVD Drive is connected.

  * Not seen with Ubuntu 16.04.4 (HWE kernel v4.13)

  * Seen with Ubuntu 18.04 (4.15.0-23-generic, 4.15.0-20-generic)

  Steps:
  Setup a DellEMC AMD server with Onboard DVD Drive, install Ubuntu 18.04 and 
start reboot stress
  After a few reboots, observe that the machine hangs at "kvm: exiting hardware 
virtualization" and does not proceed with reboot cycles.

  Only physical reset helps in continuing the reboot test.

To manage notifications about this bug go to:
https://bugs.launchpad.net/dellserver/+bug/1777674/+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 1777674] Re: Ubuntu 18.04 hangs at "kvm: exiting hardware virtualization" on AMD servers

2018-06-19 Thread Sujith Pandel
Logs where the hang is not seen:

[   75.448494] kvm: exiting hardware virtualization
[   76.187482] reboot: Restarting system
[   76.191663] reboot: machine restart
[   76.197621] ACPI MEMORY or I/O RESET_REG.


The last 3 lines are not seen when the hang is observed.

** Attachment added: "console-logs-no-failure-case"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1777674/+attachment/5154317/+files/console-logs-no-failure.txt

** Also affects: dellserver
   Importance: Undecided
   Status: 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/1777674

Title:
  Ubuntu 18.04 hangs at "kvm: exiting hardware virtualization" on AMD
  servers

Status in dellserver:
  New
Status in linux package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  New

Bug description:
  Ubuntu 18.04 hangs at "kvm: exiting hardware virtualization" on AMD
  servers when under graceful reboot stress for 12hrs.

  * This hand is observed only when Onboard SATA DVD Drive is connected.

  * Not seen with Ubuntu 16.04.4 (HWE kernel v4.13)

  * Seen with Ubuntu 18.04 (4.15.0-23-generic, 4.15.0-20-generic)

  Steps:
  Setup a DellEMC AMD server with Onboard DVD Drive, install Ubuntu 18.04 and 
start reboot stress
  After a few reboots, observe that the machine hangs at "kvm: exiting hardware 
virtualization" and does not proceed with reboot cycles.

  Only physical reset helps in continuing the reboot test.

To manage notifications about this bug go to:
https://bugs.launchpad.net/dellserver/+bug/1777674/+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 1777674] [NEW] Ubuntu 18.04 hangs at "kvm: exiting hardware virtualization" on AMD servers

2018-06-19 Thread Sujith Pandel
Public bug reported:

Ubuntu 18.04 hangs at "kvm: exiting hardware virtualization" on AMD
servers when under graceful reboot stress for 12hrs.

* This hand is observed only when Onboard SATA DVD Drive is connected.

* Not seen with Ubuntu 16.04.4 (HWE kernel v4.13)

* Seen with Ubuntu 18.04 (4.15.0-23-generic, 4.15.0-20-generic)

Steps:
Setup a DellEMC AMD server with Onboard DVD Drive, install Ubuntu 18.04 and 
start reboot stress
After a few reboots, observe that the machine hangs at "kvm: exiting hardware 
virtualization" and does not proceed with reboot cycles.

Only physical reset helps in continuing the reboot test.

** Affects: dellserver
 Importance: Undecided
 Status: New

** Affects: linux (Ubuntu)
 Importance: Undecided
 Status: New

** Affects: systemd (Ubuntu)
 Importance: Undecided
 Status: New

** Attachment added: "console-logs"
   
https://bugs.launchpad.net/bugs/1777674/+attachment/5154314/+files/console-logs.txt

** Also affects: linux (Ubuntu)
   Importance: Undecided
   Status: 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/1777674

Title:
  Ubuntu 18.04 hangs at "kvm: exiting hardware virtualization" on AMD
  servers

Status in dellserver:
  New
Status in linux package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  New

Bug description:
  Ubuntu 18.04 hangs at "kvm: exiting hardware virtualization" on AMD
  servers when under graceful reboot stress for 12hrs.

  * This hand is observed only when Onboard SATA DVD Drive is connected.

  * Not seen with Ubuntu 16.04.4 (HWE kernel v4.13)

  * Seen with Ubuntu 18.04 (4.15.0-23-generic, 4.15.0-20-generic)

  Steps:
  Setup a DellEMC AMD server with Onboard DVD Drive, install Ubuntu 18.04 and 
start reboot stress
  After a few reboots, observe that the machine hangs at "kvm: exiting hardware 
virtualization" and does not proceed with reboot cycles.

  Only physical reset helps in continuing the reboot test.

To manage notifications about this bug go to:
https://bugs.launchpad.net/dellserver/+bug/1777674/+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 1749746] Re: DellEMC AMD servers hang when running IO stress on NVMe disks

2018-02-27 Thread Sujith Pandel
** Changed in: linux (Ubuntu)
   Status: Fix Committed => Invalid

-- 
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/1749746

Title:
  DellEMC AMD servers hang when running IO stress on NVMe disks

Status in linux package in Ubuntu:
  Invalid

Bug description:
  Description:
  On Ubuntu 16.04 running 4.13.0-32 kernel, when file IO stress is run on 
multiple NVMe disks (ext4 partitioned), system hangs with multiple kernel 
crashes in the logs.

  Steps:
  1. Setup a DellEMC AMD servers with a few NVMe disks.
  2. Run the file IO stress on these disks for 24 hours.
  3. Observe that the system goes un-reponsive after a few mins/hrs.

  Additional Info:
  * Stress ran fine for 24hrs with 4.12.0-041200-generic.

  * Stress ran fine for 13hrs with 4.10.0-28-generic. Had to stop the
  run manually due to some other reasons.

  * Stress fails with linux-image-4.13.0-25-generic.

  Attaching the logs.
  Will update here once we have more data.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1749746/+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 1749746] Re: DellEMC AMD servers hang when running IO stress on NVMe disks

2018-02-27 Thread Sujith Pandel
I think we are good to close this issue.
BIOS team confirmed firmware change is fixing this.

Please close this issue.

Thank you,
Sujith

-- 
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/1749746

Title:
  DellEMC AMD servers hang when running IO stress on NVMe disks

Status in linux package in Ubuntu:
  Invalid

Bug description:
  Description:
  On Ubuntu 16.04 running 4.13.0-32 kernel, when file IO stress is run on 
multiple NVMe disks (ext4 partitioned), system hangs with multiple kernel 
crashes in the logs.

  Steps:
  1. Setup a DellEMC AMD servers with a few NVMe disks.
  2. Run the file IO stress on these disks for 24 hours.
  3. Observe that the system goes un-reponsive after a few mins/hrs.

  Additional Info:
  * Stress ran fine for 24hrs with 4.12.0-041200-generic.

  * Stress ran fine for 13hrs with 4.10.0-28-generic. Had to stop the
  run manually due to some other reasons.

  * Stress fails with linux-image-4.13.0-25-generic.

  Attaching the logs.
  Will update here once we have more data.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1749746/+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 1749746] Re: DellEMC AMD servers hang when running IO stress on NVMe disks

2018-02-20 Thread Sujith Pandel
I am sorry about the delay in uploading the logs.

Update:
* I wanted to experiment on many things before I conclude this as a kernel 
defect. 

* A few firmware updates (including BIOS) were done.

* After these fw updates, I am unable to hit the same crash/hang issue.
Rather, I only see couple of my stress threads getting killed by oom-
killer and other threads exiting gracefully after 20hrs of I/O stress
run. This seems ok for me. I've tried 5 full runs now.

* # uname -r
4.13.0-32-generic
This is the same kernel where the hang was previously seen during the 20hr 
stress.

Give me a couple of days to get back here and update if this looks to be
a genuine Xenial defect.

Thanks,
Sujith

-- 
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/1749746

Title:
  DellEMC AMD servers hang when running IO stress on NVMe disks

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Description:
  On Ubuntu 16.04 running 4.13.0-32 kernel, when file IO stress is run on 
multiple NVMe disks (ext4 partitioned), system hangs with multiple kernel 
crashes in the logs.

  Steps:
  1. Setup a DellEMC AMD servers with a few NVMe disks.
  2. Run the file IO stress on these disks for 24 hours.
  3. Observe that the system goes un-reponsive after a few mins/hrs.

  Additional Info:
  * Stress ran fine for 24hrs with 4.12.0-041200-generic.

  * Stress ran fine for 13hrs with 4.10.0-28-generic. Had to stop the
  run manually due to some other reasons.

  * Stress fails with linux-image-4.13.0-25-generic.

  Attaching the logs.
  Will update here once we have more data.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1749746/+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 1749746] [NEW] DellEMC AMD servers hang when running IO stress on NVMe disks

2018-02-15 Thread Sujith Pandel
*** This bug is a security vulnerability ***

Private security bug reported:

Description:
On Ubuntu 16.04 running 4.13.0-32 kernel, when file IO stress is run on 
multiple NVMe disks (ext4 partitioned), system hangs with multiple kernel 
crashes in the logs.

Steps:
1. Setup a DellEMC AMD servers with a few NVMe disks.
2. Run the file IO stress on these disks for 24 hours.
3. Observe that the system goes un-reponsive after a few mins/hrs.

Additional Info:
* Stress ran fine for 24hrs with 4.12.0-041200-generic.

* Stress ran fine for 13hrs with 4.10.0-28-generic. Had to stop the run
manually due to some other reasons.

* Stress fails with linux-image-4.13.0-25-generic.

Attaching the logs.
Will update here once we have more data.

** Affects: linux (Ubuntu)
 Importance: Undecided
 Status: New

** Attachment added: "kern.log"
   https://bugs.launchpad.net/bugs/1749746/+attachment/5055864/+files/kern.log

** Information type changed from Public to Private Security

-- 
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/1749746

Title:
  DellEMC AMD servers hang when running IO stress on NVMe disks

Status in linux package in Ubuntu:
  New

Bug description:
  Description:
  On Ubuntu 16.04 running 4.13.0-32 kernel, when file IO stress is run on 
multiple NVMe disks (ext4 partitioned), system hangs with multiple kernel 
crashes in the logs.

  Steps:
  1. Setup a DellEMC AMD servers with a few NVMe disks.
  2. Run the file IO stress on these disks for 24 hours.
  3. Observe that the system goes un-reponsive after a few mins/hrs.

  Additional Info:
  * Stress ran fine for 24hrs with 4.12.0-041200-generic.

  * Stress ran fine for 13hrs with 4.10.0-28-generic. Had to stop the
  run manually due to some other reasons.

  * Stress fails with linux-image-4.13.0-25-generic.

  Attaching the logs.
  Will update here once we have more data.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1749746/+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 1719697] Re: Boot/Installation crash of Ubuntu-16.04.3 HWE kernel on R940

2017-12-04 Thread Sujith Pandel
** Tags removed: kernel-da-key verification-needed-zesty zesty
** Tags added: verification-done-zesty

-- 
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/1719697

Title:
  Boot/Installation crash of Ubuntu-16.04.3 HWE kernel on R940

Status in dellserver:
  In Progress
Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Zesty:
  Fix Committed

Bug description:

  == SRU Justification ==
  Kernel crashes when installation of Ubuntu-16.04.3 with HWE (ISO).
  Same observation while booting to 4.10.0-28 HWE kerenl of Ubuntu-16.04.3
  and 4.10.0-33 HWE as well.

  Seen only with 4.10 HWE kernels of Ubuntu-16.04.3.  4.4 kernels of
  Ubuntu-16.04.3 works fine. Daily builds of Ubuntu Server 17.10 works fine.

  Reducing the core count to <26 cores helps here. Boot & installation of
  HWE-kernel works fine.

  This bug was introduced by commit:
  dc6db24d2476 ("x86/acpi: Set persistent cpuid <-> nodeid mapping when 
booting")

  It is resolved by reverting commit dc6db24d2476, which was done in mainline 
by 
  commit c962cff17df as of v4.11-rc3.

  There are three additiona commits introduced by the same patch author when
  commit c962cff17df was submitted.  However, it was confirmed that only the 
single
  revert is needed to fix this particular bug.  Upstream thread:
   https://lkml.org/lkml/2017/2/20/66

  == Fix ==
  commit c962cff17dfa11f4a8227ac16de2b28aea3312e4
  Author: Dou Liyang 
  Date:   Fri Mar 3 16:02:23 2017 +0800

  Revert "x86/acpi: Set persistent cpuid <-> nodeid mapping when
  booting"

  == Regression Potential ==
  This is reverting a commit that introduced a bug.  This commit has also
  been reverted upstream.

  == Test Case ==
  A test kernel was built with this patch and tested by the original bug 
reporter.
  The bug reporter states the test kernel resolved the bug.




  Setup:
  Dell PowerEdge R940 having 2 socket populated with 28 cores.

  Impact:
  This is a boot and installation failure for R940 users having 2 socket x 28 
cores.
  Requesting an SRU for the fix.

  Steps:
  1. Setup a Dell PowerEdge R940 with 28 cores CPUs on 2 sockets.
  2. Start installation of Ubuntu-16.04.3 with HWE kernel.
  3. Observe the screen remains blank. Console logs indicate kernel crash.

  Additional Info:
  * Seen only with 4.10 HWE kernels of Ubuntu-16.04.3.
    4.4 kernels of Ubuntu-16.04.3 works fine. Daily builds of Ubuntu Server 
17.10 works fine.

  * Reducing the core count to <26 cores helps here. Boot & installation
  of HWE-kernel works fine.

  * Attaching the console log and acpidump from the setup.

  * Patch causing this failure: 
https://github.com/torvalds/linux/commit/dc6db24d2476cd09c0ecf2b8d80313539f737a89
  x86/acpi: Set persistent cpuid <-> nodeid mapping when booting

  * Fix patch series: https://lkml.org/lkml/2017/2/20/66

  Revert "x86/acpi: Set persistent cpuid <-> nodeid mapping when booting"
  
https://github.com/torvalds/linux/commit/c962cff17dfa11f4a8227ac16de2b28aea3312e4#diff-6bd7ef719bca1a2a56b9ebf4bd0bd88d

  Revert"x86/acpi: Enable MADT APIs to return disabled apicids"
  
https://github.com/torvalds/linux/commit/09c3f2bd5c7e5f18687663acb6adc6b167484ca5

  acpi/processor: Implement DEVICE operator for processor enumeration
  
https://github.com/torvalds/linux/commit/8c8cb30f49b86333d8e036e1945cf1a78c03577e

  acpi/processor: Check for duplicate processor ids at hotplug time
  
https://github.com/torvalds/linux/commit/a77d6cd968497792e072b74dff45b891ba778ddb

To manage notifications about this bug go to:
https://bugs.launchpad.net/dellserver/+bug/1719697/+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 1719697] Re: Boot/Installation crash of Ubuntu-16.04.3 HWE kernel on R940

2017-11-29 Thread Sujith Pandel
>If the problem is solved, change the tag 'verification-needed-zesty' to
'verification-done-zesty'.

Can someone help me here?
Is this action on me? Problem is solved with the above kernel.

-- 
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/1719697

Title:
  Boot/Installation crash of Ubuntu-16.04.3 HWE kernel on R940

Status in dellserver:
  In Progress
Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Zesty:
  Fix Committed

Bug description:

  == SRU Justification ==
  Kernel crashes when installation of Ubuntu-16.04.3 with HWE (ISO).
  Same observation while booting to 4.10.0-28 HWE kerenl of Ubuntu-16.04.3
  and 4.10.0-33 HWE as well.

  Seen only with 4.10 HWE kernels of Ubuntu-16.04.3.  4.4 kernels of
  Ubuntu-16.04.3 works fine. Daily builds of Ubuntu Server 17.10 works fine.

  Reducing the core count to <26 cores helps here. Boot & installation of
  HWE-kernel works fine.

  This bug was introduced by commit:
  dc6db24d2476 ("x86/acpi: Set persistent cpuid <-> nodeid mapping when 
booting")

  It is resolved by reverting commit dc6db24d2476, which was done in mainline 
by 
  commit c962cff17df as of v4.11-rc3.

  There are three additiona commits introduced by the same patch author when
  commit c962cff17df was submitted.  However, it was confirmed that only the 
single
  revert is needed to fix this particular bug.  Upstream thread:
   https://lkml.org/lkml/2017/2/20/66

  == Fix ==
  commit c962cff17dfa11f4a8227ac16de2b28aea3312e4
  Author: Dou Liyang 
  Date:   Fri Mar 3 16:02:23 2017 +0800

  Revert "x86/acpi: Set persistent cpuid <-> nodeid mapping when
  booting"

  == Regression Potential ==
  This is reverting a commit that introduced a bug.  This commit has also
  been reverted upstream.

  == Test Case ==
  A test kernel was built with this patch and tested by the original bug 
reporter.
  The bug reporter states the test kernel resolved the bug.




  Setup:
  Dell PowerEdge R940 having 2 socket populated with 28 cores.

  Impact:
  This is a boot and installation failure for R940 users having 2 socket x 28 
cores.
  Requesting an SRU for the fix.

  Steps:
  1. Setup a Dell PowerEdge R940 with 28 cores CPUs on 2 sockets.
  2. Start installation of Ubuntu-16.04.3 with HWE kernel.
  3. Observe the screen remains blank. Console logs indicate kernel crash.

  Additional Info:
  * Seen only with 4.10 HWE kernels of Ubuntu-16.04.3.
    4.4 kernels of Ubuntu-16.04.3 works fine. Daily builds of Ubuntu Server 
17.10 works fine.

  * Reducing the core count to <26 cores helps here. Boot & installation
  of HWE-kernel works fine.

  * Attaching the console log and acpidump from the setup.

  * Patch causing this failure: 
https://github.com/torvalds/linux/commit/dc6db24d2476cd09c0ecf2b8d80313539f737a89
  x86/acpi: Set persistent cpuid <-> nodeid mapping when booting

  * Fix patch series: https://lkml.org/lkml/2017/2/20/66

  Revert "x86/acpi: Set persistent cpuid <-> nodeid mapping when booting"
  
https://github.com/torvalds/linux/commit/c962cff17dfa11f4a8227ac16de2b28aea3312e4#diff-6bd7ef719bca1a2a56b9ebf4bd0bd88d

  Revert"x86/acpi: Enable MADT APIs to return disabled apicids"
  
https://github.com/torvalds/linux/commit/09c3f2bd5c7e5f18687663acb6adc6b167484ca5

  acpi/processor: Implement DEVICE operator for processor enumeration
  
https://github.com/torvalds/linux/commit/8c8cb30f49b86333d8e036e1945cf1a78c03577e

  acpi/processor: Check for duplicate processor ids at hotplug time
  
https://github.com/torvalds/linux/commit/a77d6cd968497792e072b74dff45b891ba778ddb

To manage notifications about this bug go to:
https://bugs.launchpad.net/dellserver/+bug/1719697/+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 1719697] Re: Boot/Installation crash of Ubuntu-16.04.3 HWE kernel on R940

2017-11-29 Thread Sujith Pandel
After adding xenial-proposed to /etc/apt/sources.list,

#apt-get install linux-generic-hwe-16.04/xenial-proposed

Confirmed Booting pass with:

# uname -a
Linux dhcp-165-167 4.10.0-41-generic #45~16.04.1-Ubuntu SMP Fri Nov 24 15:06:20 
UTC 2017 x86_64 x86_64 x86_64 GNU/Linux

Thanks for including the fix.
http://kernel.ubuntu.com/git/ubuntu/ubuntu-xenial.git/commit/?h=hwe=dcde44490772d2059ecc5035a3b6c994176c6212

-- 
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/1719697

Title:
  Boot/Installation crash of Ubuntu-16.04.3 HWE kernel on R940

Status in dellserver:
  In Progress
Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Zesty:
  Fix Committed

Bug description:

  == SRU Justification ==
  Kernel crashes when installation of Ubuntu-16.04.3 with HWE (ISO).
  Same observation while booting to 4.10.0-28 HWE kerenl of Ubuntu-16.04.3
  and 4.10.0-33 HWE as well.

  Seen only with 4.10 HWE kernels of Ubuntu-16.04.3.  4.4 kernels of
  Ubuntu-16.04.3 works fine. Daily builds of Ubuntu Server 17.10 works fine.

  Reducing the core count to <26 cores helps here. Boot & installation of
  HWE-kernel works fine.

  This bug was introduced by commit:
  dc6db24d2476 ("x86/acpi: Set persistent cpuid <-> nodeid mapping when 
booting")

  It is resolved by reverting commit dc6db24d2476, which was done in mainline 
by 
  commit c962cff17df as of v4.11-rc3.

  There are three additiona commits introduced by the same patch author when
  commit c962cff17df was submitted.  However, it was confirmed that only the 
single
  revert is needed to fix this particular bug.  Upstream thread:
   https://lkml.org/lkml/2017/2/20/66

  == Fix ==
  commit c962cff17dfa11f4a8227ac16de2b28aea3312e4
  Author: Dou Liyang 
  Date:   Fri Mar 3 16:02:23 2017 +0800

  Revert "x86/acpi: Set persistent cpuid <-> nodeid mapping when
  booting"

  == Regression Potential ==
  This is reverting a commit that introduced a bug.  This commit has also
  been reverted upstream.

  == Test Case ==
  A test kernel was built with this patch and tested by the original bug 
reporter.
  The bug reporter states the test kernel resolved the bug.




  Setup:
  Dell PowerEdge R940 having 2 socket populated with 28 cores.

  Impact:
  This is a boot and installation failure for R940 users having 2 socket x 28 
cores.
  Requesting an SRU for the fix.

  Steps:
  1. Setup a Dell PowerEdge R940 with 28 cores CPUs on 2 sockets.
  2. Start installation of Ubuntu-16.04.3 with HWE kernel.
  3. Observe the screen remains blank. Console logs indicate kernel crash.

  Additional Info:
  * Seen only with 4.10 HWE kernels of Ubuntu-16.04.3.
    4.4 kernels of Ubuntu-16.04.3 works fine. Daily builds of Ubuntu Server 
17.10 works fine.

  * Reducing the core count to <26 cores helps here. Boot & installation
  of HWE-kernel works fine.

  * Attaching the console log and acpidump from the setup.

  * Patch causing this failure: 
https://github.com/torvalds/linux/commit/dc6db24d2476cd09c0ecf2b8d80313539f737a89
  x86/acpi: Set persistent cpuid <-> nodeid mapping when booting

  * Fix patch series: https://lkml.org/lkml/2017/2/20/66

  Revert "x86/acpi: Set persistent cpuid <-> nodeid mapping when booting"
  
https://github.com/torvalds/linux/commit/c962cff17dfa11f4a8227ac16de2b28aea3312e4#diff-6bd7ef719bca1a2a56b9ebf4bd0bd88d

  Revert"x86/acpi: Enable MADT APIs to return disabled apicids"
  
https://github.com/torvalds/linux/commit/09c3f2bd5c7e5f18687663acb6adc6b167484ca5

  acpi/processor: Implement DEVICE operator for processor enumeration
  
https://github.com/torvalds/linux/commit/8c8cb30f49b86333d8e036e1945cf1a78c03577e

  acpi/processor: Check for duplicate processor ids at hotplug time
  
https://github.com/torvalds/linux/commit/a77d6cd968497792e072b74dff45b891ba778ddb

To manage notifications about this bug go to:
https://bugs.launchpad.net/dellserver/+bug/1719697/+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 1719697] Re: Boot/Installation crash of Ubuntu-16.04.3 HWE kernel on R940

2017-11-28 Thread Sujith Pandel
Thank you.
We will revert back with the findings on xenial-proposed kernel.

-- 
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/1719697

Title:
  Boot/Installation crash of Ubuntu-16.04.3 HWE kernel on R940

Status in dellserver:
  In Progress
Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Zesty:
  Fix Committed

Bug description:

  == SRU Justification ==
  Kernel crashes when installation of Ubuntu-16.04.3 with HWE (ISO).
  Same observation while booting to 4.10.0-28 HWE kerenl of Ubuntu-16.04.3
  and 4.10.0-33 HWE as well.

  Seen only with 4.10 HWE kernels of Ubuntu-16.04.3.  4.4 kernels of
  Ubuntu-16.04.3 works fine. Daily builds of Ubuntu Server 17.10 works fine.

  Reducing the core count to <26 cores helps here. Boot & installation of
  HWE-kernel works fine.

  This bug was introduced by commit:
  dc6db24d2476 ("x86/acpi: Set persistent cpuid <-> nodeid mapping when 
booting")

  It is resolved by reverting commit dc6db24d2476, which was done in mainline 
by 
  commit c962cff17df as of v4.11-rc3.

  There are three additiona commits introduced by the same patch author when
  commit c962cff17df was submitted.  However, it was confirmed that only the 
single
  revert is needed to fix this particular bug.  Upstream thread:
   https://lkml.org/lkml/2017/2/20/66

  == Fix ==
  commit c962cff17dfa11f4a8227ac16de2b28aea3312e4
  Author: Dou Liyang 
  Date:   Fri Mar 3 16:02:23 2017 +0800

  Revert "x86/acpi: Set persistent cpuid <-> nodeid mapping when
  booting"

  == Regression Potential ==
  This is reverting a commit that introduced a bug.  This commit has also
  been reverted upstream.

  == Test Case ==
  A test kernel was built with this patch and tested by the original bug 
reporter.
  The bug reporter states the test kernel resolved the bug.




  Setup:
  Dell PowerEdge R940 having 2 socket populated with 28 cores.

  Impact:
  This is a boot and installation failure for R940 users having 2 socket x 28 
cores.
  Requesting an SRU for the fix.

  Steps:
  1. Setup a Dell PowerEdge R940 with 28 cores CPUs on 2 sockets.
  2. Start installation of Ubuntu-16.04.3 with HWE kernel.
  3. Observe the screen remains blank. Console logs indicate kernel crash.

  Additional Info:
  * Seen only with 4.10 HWE kernels of Ubuntu-16.04.3.
    4.4 kernels of Ubuntu-16.04.3 works fine. Daily builds of Ubuntu Server 
17.10 works fine.

  * Reducing the core count to <26 cores helps here. Boot & installation
  of HWE-kernel works fine.

  * Attaching the console log and acpidump from the setup.

  * Patch causing this failure: 
https://github.com/torvalds/linux/commit/dc6db24d2476cd09c0ecf2b8d80313539f737a89
  x86/acpi: Set persistent cpuid <-> nodeid mapping when booting

  * Fix patch series: https://lkml.org/lkml/2017/2/20/66

  Revert "x86/acpi: Set persistent cpuid <-> nodeid mapping when booting"
  
https://github.com/torvalds/linux/commit/c962cff17dfa11f4a8227ac16de2b28aea3312e4#diff-6bd7ef719bca1a2a56b9ebf4bd0bd88d

  Revert"x86/acpi: Enable MADT APIs to return disabled apicids"
  
https://github.com/torvalds/linux/commit/09c3f2bd5c7e5f18687663acb6adc6b167484ca5

  acpi/processor: Implement DEVICE operator for processor enumeration
  
https://github.com/torvalds/linux/commit/8c8cb30f49b86333d8e036e1945cf1a78c03577e

  acpi/processor: Check for duplicate processor ids at hotplug time
  
https://github.com/torvalds/linux/commit/a77d6cd968497792e072b74dff45b891ba778ddb

To manage notifications about this bug go to:
https://bugs.launchpad.net/dellserver/+bug/1719697/+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 1719697] Re: Boot/Installation crash of Ubuntu-16.04.3 HWE kernel on R940

2017-11-05 Thread Sujith Pandel
Hi Joseph,
Thanks for taking this up.
Can you let us know if this is confirmed for upcoming SRU?

>From the schedule, I see we are already past the freeze date:
 * Next cycle: 27-Oct through 18-Nov
   27-Oct   Last day for kernel commits for this cycle.
  30-Oct - 04-Nov   Kernel prep week.
  05-Nov - 17-Nov   Bug verification & Regression testing.
   20-Nov   Release to -updates.

Thanks,
Sujith

-- 
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/1719697

Title:
  Boot/Installation crash of Ubuntu-16.04.3 HWE kernel on R940

Status in dellserver:
  In Progress
Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Zesty:
  In Progress

Bug description:

  == SRU Justification ==
  Kernel crashes when installation of Ubuntu-16.04.3 with HWE (ISO).
  Same observation while booting to 4.10.0-28 HWE kerenl of Ubuntu-16.04.3
  and 4.10.0-33 HWE as well.

  Seen only with 4.10 HWE kernels of Ubuntu-16.04.3.  4.4 kernels of
  Ubuntu-16.04.3 works fine. Daily builds of Ubuntu Server 17.10 works fine.

  Reducing the core count to <26 cores helps here. Boot & installation of
  HWE-kernel works fine.

  This bug was introduced by commit:
  dc6db24d2476 ("x86/acpi: Set persistent cpuid <-> nodeid mapping when 
booting")

  It is resolved by reverting commit dc6db24d2476, which was done in mainline 
by 
  commit c962cff17df as of v4.11-rc3.

  There are three additiona commits introduced by the same patch author when
  commit c962cff17df was submitted.  However, it was confirmed that only the 
single
  revert is needed to fix this particular bug.  Upstream thread:
   https://lkml.org/lkml/2017/2/20/66

  == Fix ==
  commit c962cff17dfa11f4a8227ac16de2b28aea3312e4
  Author: Dou Liyang 
  Date:   Fri Mar 3 16:02:23 2017 +0800

  Revert "x86/acpi: Set persistent cpuid <-> nodeid mapping when
  booting"

  == Regression Potential ==
  This is reverting a commit that introduced a bug.  This commit has also
  been reverted upstream.

  == Test Case ==
  A test kernel was built with this patch and tested by the original bug 
reporter.
  The bug reporter states the test kernel resolved the bug.




  Setup:
  Dell PowerEdge R940 having 2 socket populated with 28 cores.

  Impact:
  This is a boot and installation failure for R940 users having 2 socket x 28 
cores.
  Requesting an SRU for the fix.

  Steps:
  1. Setup a Dell PowerEdge R940 with 28 cores CPUs on 2 sockets.
  2. Start installation of Ubuntu-16.04.3 with HWE kernel.
  3. Observe the screen remains blank. Console logs indicate kernel crash.

  Additional Info:
  * Seen only with 4.10 HWE kernels of Ubuntu-16.04.3.
    4.4 kernels of Ubuntu-16.04.3 works fine. Daily builds of Ubuntu Server 
17.10 works fine.

  * Reducing the core count to <26 cores helps here. Boot & installation
  of HWE-kernel works fine.

  * Attaching the console log and acpidump from the setup.

  * Patch causing this failure: 
https://github.com/torvalds/linux/commit/dc6db24d2476cd09c0ecf2b8d80313539f737a89
  x86/acpi: Set persistent cpuid <-> nodeid mapping when booting

  * Fix patch series: https://lkml.org/lkml/2017/2/20/66

  Revert "x86/acpi: Set persistent cpuid <-> nodeid mapping when booting"
  
https://github.com/torvalds/linux/commit/c962cff17dfa11f4a8227ac16de2b28aea3312e4#diff-6bd7ef719bca1a2a56b9ebf4bd0bd88d

  Revert"x86/acpi: Enable MADT APIs to return disabled apicids"
  
https://github.com/torvalds/linux/commit/09c3f2bd5c7e5f18687663acb6adc6b167484ca5

  acpi/processor: Implement DEVICE operator for processor enumeration
  
https://github.com/torvalds/linux/commit/8c8cb30f49b86333d8e036e1945cf1a78c03577e

  acpi/processor: Check for duplicate processor ids at hotplug time
  
https://github.com/torvalds/linux/commit/a77d6cd968497792e072b74dff45b891ba778ddb

To manage notifications about this bug go to:
https://bugs.launchpad.net/dellserver/+bug/1719697/+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 1491654] Re: Intel P3700 PCIe SSD string shows ''Unknown'' during Ubuntu 14.04 installation

2017-08-16 Thread Sujith Pandel
I can see this behavior of reporting NVME disks as 'Unknown' by the installer 
in Ubuntu-16.04.3 (Server) with HWE kernel 4.10 during installation.
I do see that the sysfs has 'model' attribute, so I think its the installer who 
is not reading it, now.

-- 
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/1491654

Title:
  Intel P3700 PCIe SSD string shows ''Unknown'' during Ubuntu 14.04
  installation

Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Trusty:
  Incomplete
Status in linux source package in Xenial:
  Incomplete
Status in linux source package in Yakkety:
  Won't Fix
Status in linux source package in Zesty:
  Incomplete

Bug description:
  Current Behavior
  ==
  1. Intel P3700 PCIe SSD string shows "Unknow" during Ubuntu 14.04 install.

  Reference Verification
  ==
  1. Which version of previous BIOS/BMC/HW passed/failed? 1st Test
  2. Which similar project/product passed/failed? NA

  Steps to reproduce the problem
  ==
  1. Install Intel P3700 PCIe SSD*2 and SAS 12G HDD*8 with LSI 3108 into SUT.
  2. Power on system and install Ubuntu 14.04.
  3. Intel P3700 PCIe SSD string shows "Unknown" during OS install.

  Expected Behavior
  ==
  1. Intel P3700 PCIe SSD string should not show "Unknown" during Ubuntu 14.04 
install.

  Pcie SSD config:HDD/SSD:Intel,SSDPE2MD016T4,PCI-e,1.6TB,Gen3

  Copied from private bug:
  https://bugs.launchpad.net/quantatw/+bug/1454965

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1491654/+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 1555350] Re: "Error parsing PCC subspaces from PCCT" during initializing the system

2017-07-18 Thread Sujith Pandel
CONFIG_MAILBOX and CONFIG_PCC are enabled.

I also checked the acpidump. The PCCT defines only a "Generic Communications 
Subspace" or Type-0 and not the other two types.
(Ref: 
http://elixir.free-electrons.com/linux/latest/source/include/acpi/actbl3.h#L481)
 

Whereas the acpi_pcc_probe takes count of only these 2 missing/not-
defined PCC subspace types.. I do not know much about this to comment on
why this approach..

(Ref: http://elixir.free-
electrons.com/linux/latest/source/drivers/mailbox/pcc.c#L448)

Would like to have someone explain why kernel does not consider type-0
in this 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/1555350

Title:
  "Error parsing PCC subspaces from PCCT" during initializing the system

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After an update such an error shows when I turn my xubuntu on.

  I was wrinting on this also in https://bugs.launchpad.net/bugs/1528684

  Thanks

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1555350/+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