[Kernel-packages] [Bug 1995886] Re: vmxnet3: update to latest ToT

2022-11-14 Thread vmware-gos-Yuhua
Test kernel from 
https://kernel.ubuntu.com/~rtg/vmxnet3-update-to-6.0-lp1995886/ in 
ubuntu-22.10-desktop-amd64.iso and ubuntu-20.04-desktop-amd64.iso: 
 No issue is found when sanity check vmxnet3 with following testcases:
  1) vmxnet3 version is 1.7.0.0-k with command "modinfo vmxnet3"
  2) hot-add / hot-remove NIC with vmxnet3
  3) add / remove NIC with vmxnet3 when VM is poweroff
  4) VM can recognize the vmxnet3 NIC when it’s added and the VM is pingable.

Env:
create VM and install guestOS with the image in ESXi and then update the kernel 
from https://kernel.ubuntu.com/~rtg/vmxnet3-update-to-6.0-lp1995886/

1) Image: ubuntu-22.10-desktop-amd64.iso 
   kernel: 5.19.0-23-generic #24
   vmxnet3: /lib/modules/5.19.0-23-generic/kernel/drivers/net/vmxnet3/vmxnet3.ko
   vmxnet3 version: 1.7.0.0-k
 

2) Image: ubuntu-20.04-desktop-amd64.iso
   kernel: 5.15.0-53-generi #59
   vmxnet3: /lib/modules/5.15.0-53-generic/kernel/drivers/net/vmxnet3/vmxnet3.ko
   vmxnet3 version: 1.7.0.0-k
 

Best regards
Yuhua Zou

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

Title:
  vmxnet3: update to latest ToT

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Jammy:
  New
Status in linux source package in Kinetic:
  New

Bug description:
  This request is to port vmxnet3 patches to Ubuntu kernel. Below are
  the commits in order:

  vmxnet3: prepare for version 7 changes
  https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-
  
next.git/commit/drivers/net/vmxnet3?id=55f0395fcace9e675af2cbb96015ce1ae8856806

  vmxnet3: add support for capability registers
  https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-
  
next.git/commit/drivers/net/vmxnet3?id=6f91f4ba046e5de6a6e579620b32b8ecf56873f7

  vmxnet3: add support for large passthrough BAR register
  https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-
  
next.git/commit/drivers/net/vmxnet3?id=543fb67405410cc548a72d7a9a4087688d2f56ac

  vmxnet3: add support for out of order rx completion
  https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-
  
next.git/commit/drivers/net/vmxnet3?id=2c5a5748105a6bb901579d365c6f93e79f282b69

  vmxnet3: add command to set ring buffer sizes
  https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-
  
next.git/commit/drivers/net/vmxnet3?id=c7112ebd27ea0dbe4eecd5c96cad93757e34e73d

  vmxnet3: limit number of TXDs used for TSO packet
  https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-
  
next.git/commit/drivers/net/vmxnet3?id=d2857b99a74b082368ee80f359372faa1d051043

  vmxnet3: use ext1 field to indicate encapsulated packet
  https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-
  
next.git/commit/drivers/net/vmxnet3?id=60cafa0395c2bed44d13277ed328317ed16a58c0

  vmxnet3: update to version 7
  https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-
  
next.git/commit/drivers/net/vmxnet3?id=acc38e041bd304621d4f59cea4849747d13bba9c

  vmxnet3: disable overlay offloads if UPT device does not support
  https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-
  
next.git/commit/drivers/net/vmxnet3?id=a56b158a5078b8120d3d72fc9fd44efed5123b12

  vmxnet3: do not reschedule napi for rx processing
  
https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-next.git/commit/drivers/net/vmxnet3?id=5b91884bf50b21d34bd3daa5c8f8b7e92e0a2c46

  This is a request to bring latest Ubuntu LTS releases' vmxnet3 driver
  up to date with ToT Linux kernel.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1995886/+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 1995886] Re: vmxnet3: update to latest ToT

2022-11-10 Thread vmware-gos-Yuhua
> Can you confirm that these kernels already have patches mentioned in
update 5?

Reply #5 and #8:
I can find all patches mentioned in update #5 when check the source code of 
vmxnet3 driver in the following images:

1) Image: ubuntu-22.10-desktop-amd64.iso
   kernel: 5.19.0-23-generic #24
   vmxnet3: 
/lib/modules/5.19.0-23-generic/kernel/drivers/net/vmxnet3/vmxnet3.ko  
   vmxnet3 version: 1.6.0.0-k
   source code: 
/usr/src/linux-source-5.19.0/linux-source-5.19.0/drivers/net/vmxnet3/
 
2) Image: ubuntu-20.04-desktop-amd64.iso
   kernel: 5.15.0-30-generi #31
   vmxnet3: /lib/modules/5.15.0-30-generic/kernel/drivers/net/vmxnet3/vmxnet3.ko
   vmxnet3 version: 1.6.0.0-k
   source code: 
/usr/src/linux-source-5.15.0/linux-source-5.15.0/drivers/net/vmxnet3/


Best regards
Yuhua Zou

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

Title:
  vmxnet3: update to latest ToT

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Jammy:
  New
Status in linux source package in Kinetic:
  New

Bug description:
  This request is to port vmxnet3 patches to Ubuntu kernel. Below are
  the commits in order:

  vmxnet3: prepare for version 7 changes
  https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-
  
next.git/commit/drivers/net/vmxnet3?id=55f0395fcace9e675af2cbb96015ce1ae8856806

  vmxnet3: add support for capability registers
  https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-
  
next.git/commit/drivers/net/vmxnet3?id=6f91f4ba046e5de6a6e579620b32b8ecf56873f7

  vmxnet3: add support for large passthrough BAR register
  https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-
  
next.git/commit/drivers/net/vmxnet3?id=543fb67405410cc548a72d7a9a4087688d2f56ac

  vmxnet3: add support for out of order rx completion
  https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-
  
next.git/commit/drivers/net/vmxnet3?id=2c5a5748105a6bb901579d365c6f93e79f282b69

  vmxnet3: add command to set ring buffer sizes
  https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-
  
next.git/commit/drivers/net/vmxnet3?id=c7112ebd27ea0dbe4eecd5c96cad93757e34e73d

  vmxnet3: limit number of TXDs used for TSO packet
  https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-
  
next.git/commit/drivers/net/vmxnet3?id=d2857b99a74b082368ee80f359372faa1d051043

  vmxnet3: use ext1 field to indicate encapsulated packet
  https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-
  
next.git/commit/drivers/net/vmxnet3?id=60cafa0395c2bed44d13277ed328317ed16a58c0

  vmxnet3: update to version 7
  https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-
  
next.git/commit/drivers/net/vmxnet3?id=acc38e041bd304621d4f59cea4849747d13bba9c

  vmxnet3: disable overlay offloads if UPT device does not support
  https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-
  
next.git/commit/drivers/net/vmxnet3?id=a56b158a5078b8120d3d72fc9fd44efed5123b12

  vmxnet3: do not reschedule napi for rx processing
  
https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-next.git/commit/drivers/net/vmxnet3?id=5b91884bf50b21d34bd3daa5c8f8b7e92e0a2c46

  This is a request to bring latest Ubuntu LTS releases' vmxnet3 driver
  up to date with ToT Linux kernel.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1995886/+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 1882834] Re: vmxnet3: update to latest ToT

2020-11-26 Thread vmware-gos-Yuhua
Any updates ?

Thanks 
Yuhua Zou

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

Title:
  vmxnet3: update to latest ToT

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  This request is to port vmxnet3 patches to Ubuntu kernel. Below are
  the commits in order:

  vmxnet3: prepare for version 4 changes 
  
https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-next.git/commit/?id=123db31d01219a4f794f3769e7bca6649d65ecb1

  vmxnet3: add support to get/set rx flow hash 
  
https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-next.git/commit/?id=d3a8a9e5c3b334d443e97daa59bb95c0b69f4794

  vmxnet3: add geneve and vxlan tunnel offload support 
  
https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-next.git/commit/?id=dacce2be33124df3c71f979ac47e3d6354a41125

  vmxnet3: update to version 4
  
https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-next.git/commit/?id=a31135e36eccd0d16e500d3041f23c3ece62096f

  vmxnet3: use correct hdr reference when packet is encapsulated
  
https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-next.git/commit/?id=36432797641ff0013be9252eecf7ad1ba73171a2

  vmxnet3: allow rx flow hash ops only when rss is enabled 
  
https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-next.git/commit/?id=11e877b2a8cfd282a1b81f9d4c594b900889a5d8

  This is a request to bring Ubuntu vmxnet3 driver up to date with ToT
  Linux kernel. Could you apply these patches to ongoing releases?

  
  Also, could you help verify if the below commits are present in vmxnet3 of 
ubuntu kernel? If not, then please apply these patches before above ones.

  vmxnet3: set the DMA mask before the first DMA map operation
  
https://git.kernel.org/pub/scm/linux/kernel/git/davem/net.git/commit/?id=61aeecea40afb2b89933e27cd4adb10fc2e75cfd

  vmxnet3: use DMA memory barriers where required
  
https://git.kernel.org/pub/scm/linux/kernel/git/davem/net.git/commit/?id=f3002c1374fb2367c9d8dbb28852791ef90d2bac

  vmxnet3: turn off lro when rxcsum is disabled
  
https://git.kernel.org/pub/scm/linux/kernel/git/davem/net-next.git/commit/drivers/net/vmxnet3?id=3dd7400b419409b1551f7f01764b1f3160feda90

  Thanks

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1882834/+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 1882834] Re: vmxnet3: update to latest ToT

2020-07-31 Thread vmware-gos-Yuhua
So do we still have the following commits needed to  patches to Ubuntu
kernel ?

vmxnet3: prepare for version 4 changes
https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-next.git/commit/?id=123db31d01219a4f794f3769e7bca6649d65ecb1

vmxnet3: add support to get/set rx flow hash
https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-next.git/commit/?id=d3a8a9e5c3b334d443e97daa59bb95c0b69f4794

vmxnet3: add geneve and vxlan tunnel offload support
https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-next.git/commit/?id=dacce2be33124df3c71f979ac47e3d6354a41125

vmxnet3: update to version 4
https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-next.git/commit/?id=a31135e36eccd0d16e500d3041f23c3ece62096f

vmxnet3: use correct hdr reference when packet is encapsulated
https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-next.git/commit/?id=36432797641ff0013be9252eecf7ad1ba73171a2

vmxnet3: allow rx flow hash ops only when rss is enabled
https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-next.git/commit/?id=11e877b2a8cfd282a1b81f9d4c594b900889a5d8


Thanks
Yuhua Zou

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

Title:
  vmxnet3: update to latest ToT

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  This request is to port vmxnet3 patches to Ubuntu kernel. Below are
  the commits in order:

  vmxnet3: prepare for version 4 changes 
  
https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-next.git/commit/?id=123db31d01219a4f794f3769e7bca6649d65ecb1

  vmxnet3: add support to get/set rx flow hash 
  
https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-next.git/commit/?id=d3a8a9e5c3b334d443e97daa59bb95c0b69f4794

  vmxnet3: add geneve and vxlan tunnel offload support 
  
https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-next.git/commit/?id=dacce2be33124df3c71f979ac47e3d6354a41125

  vmxnet3: update to version 4
  
https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-next.git/commit/?id=a31135e36eccd0d16e500d3041f23c3ece62096f

  vmxnet3: use correct hdr reference when packet is encapsulated
  
https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-next.git/commit/?id=36432797641ff0013be9252eecf7ad1ba73171a2

  vmxnet3: allow rx flow hash ops only when rss is enabled 
  
https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-next.git/commit/?id=11e877b2a8cfd282a1b81f9d4c594b900889a5d8

  This is a request to bring Ubuntu vmxnet3 driver up to date with ToT
  Linux kernel. Could you apply these patches to ongoing releases?

  
  Also, could you help verify if the below commits are present in vmxnet3 of 
ubuntu kernel? If not, then please apply these patches before above ones.

  vmxnet3: set the DMA mask before the first DMA map operation
  
https://git.kernel.org/pub/scm/linux/kernel/git/davem/net.git/commit/?id=61aeecea40afb2b89933e27cd4adb10fc2e75cfd

  vmxnet3: use DMA memory barriers where required
  
https://git.kernel.org/pub/scm/linux/kernel/git/davem/net.git/commit/?id=f3002c1374fb2367c9d8dbb28852791ef90d2bac

  vmxnet3: turn off lro when rxcsum is disabled
  
https://git.kernel.org/pub/scm/linux/kernel/git/davem/net-next.git/commit/drivers/net/vmxnet3?id=3dd7400b419409b1551f7f01764b1f3160feda90

  Thanks

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1882834/+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 1856434] Re: blk_update_request: I/O error, dev sdb, sector 976772992 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 0

2020-07-06 Thread vmware-gos-Yuhua
>  vmware-gos-Yuhua (yhzou) wrote on 2020-06-01:#22

   It's because VMs on vmfs5 datastore doesn't support trim/unmap command. 
it won't hit this issue with vmfs6

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

Title:
  blk_update_request: I/O error, dev sdb, sector 976772992 op 0x0:(READ)
  flags 0x80700 phys_seg 1 prio class 0

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  1) Ubuntu 19.10
  2) unknown
  3) no error
  4) error in log app.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  htpc   9157 F pulseaudio
   /dev/snd/controlC1:  htpc   9157 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 19.10
  InstallationDate: Installed on 2019-10-28 (48 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  IwConfig:
   lxcbr0no wireless extensions.
   
   lono wireless extensions.
   
   enp3s0no wireless extensions.
  MachineType: Gigabyte Technology Co., Ltd. GA-MA780G-UD3H
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-23-generic 
root=UUID=0fa008d8-2279-4e78-9043-161b7f514243 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-23-generic N/A
   linux-backports-modules-5.3.0-23-generic  N/A
   linux-firmware1.183.2
  RfKill:
   
  Tags:  wayland-session eoan
  Uname: Linux 5.3.0-23-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 07/13/2010
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F6b
  dmi.board.name: GA-MA780G-UD3H
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF6b:bd07/13/2010:svnGigabyteTechnologyCo.,Ltd.:pnGA-MA780G-UD3H:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-MA780G-UD3H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: GA-MA780G-UD3H
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1856434/+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 1882893] Re: vmxnet3: update to latest vmxnet3 driver (upgrade vmxnet3 driver to version 4)

2020-06-29 Thread vmware-gos-Yuhua
It's not a issue but a task. So no logs are needed.

** 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/1882893

Title:
  vmxnet3: update to latest vmxnet3 driver (upgrade vmxnet3 driver to
  version 4)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Recently, a couple of patches were upstreamed to Linux to upgrade
  vmxnet3 driver to version 4. Below are the commits:

  vmxnet3: prepare for version 4 changes
  
https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-next.git/commit/?id=123db31d01219a4f794f3769e7bca6649d65ecb1

  vmxnet3: add support to get/set rx flow hash
  
https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-next.git/commit/?id=d3a8a9e5c3b334d443e97daa59bb95c0b69f4794

  vmxnet3: add geneve and vxlan tunnel offload support
  
https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-next.git/commit/?id=dacce2be33124df3c71f979ac47e3d6354a41125

  vmxnet3: update to version 4
  
https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-next.git/commit/?id=a31135e36eccd0d16e500d3041f23c3ece62096f

  vmxnet3: use correct hdr reference when packet is encapsulated
  
https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-next.git/commit/?id=36432797641ff0013be9252eecf7ad1ba73171a2

  vmxnet3: allow rx flow hash ops only when rss is enabled
  
https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-next.git/commit/?id=11e877b2a8cfd282a1b81f9d4c594b900889a5d8

  This is a request to bring Ubuntu vmxnet3 driver up to date with Linux
  kernel.

  Thanks,
  Yuhua Zou

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1882893/+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 1856434] Re: blk_update_request: I/O error, dev sdb, sector 976772992 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 0

2020-06-01 Thread vmware-gos-Yuhua
vmware deve's comment for the issue "blk_update_request: I/O error, dev
sda, sector 3270728 op 0x9 VM ubuntu-20.04-live-server in ESXi 7.0GA" :

I noticed that when it's happening, abnormal kernel log:
[0.00]  ? lockdown_lsm_init+0x21/0x25
[0.00] Kernel is locked down from EFI Secure Boot mode; see man 
kernel_lockdown.7
.
[   66.261508] Lockdown: fwupd: /dev/mem,kmem,port is restricted; see man 
kernel_lockdown.7
[  233.169823] ata3: SATA link down (SStatus 0 SControl 300)
[  238.577700] ata3: SATA link down (SStatus 0 SControl 300)
[  243.953448] ata3: SATA link down (SStatus 0 SControl 300)
[  243.953455] ata3.00: disabled
[  243.953481] sr 2:0:0:0: rejecting I/O to offline device
[  243.958034] ata3.00: detaching (SCSI 2:0:0:0)
[  304.517077] sd 3:0:0:0: [sda] tag#55 FAILED Result: hostbyte=DID_OK 
driverbyte=DRIVER_SENSE
[  304.517081] sd 3:0:0:0: [sda] tag#55 Sense Key : Vendor Specific(9) [current]
[  304.517086] sd 3:0:0:0: [sda] tag#55 <>ASC=0x80 <>ASCQ=0x85
[  304.517090] sd 3:0:0:0: [sda] tag#55 CDB: Write same(16) 93 08 00 00 00 00 
00 31 e7 e8 00 00 00 18 00 00
[  304.517100] blk_update_request: I/O error, dev sda, sector 3270632 op 
0x9:(WRITE_ZEROES) flags 0x800 phys_seg 0 prio class 0
[  314.319273] sd 3:0:0:0: [sda] tag#11 FAILED Result: hostbyte=DID_OK 
driverbyte=DRIVER_SENSE
[  314.319275] sd 3:0:0:0: [sda] tag#11 Sense Key : Vendor Specific(9) [current]
[  314.319278] sd 3:0:0:0: [sda] tag#11 <>ASC=0x80 <>ASCQ=0x85
[  314.319295] sd 3:0:0:0: [sda] tag#11 CDB: Write same(16) 93 08 00 00 00 00 
00 31 e8 10 00 00 00 18 00 00
[  314.319299] blk_update_request: I/O error, dev sda, sector 3270672 op 
0x9:(WRITE_ZEROES) flags 0x800 phys_seg 0 prio class 0


And no error log in hostside.

Noticed you enabled secure boot in uefi and ubuntu are configured with
lockdown


vmware@ubuntu:~$ cat /boot/config-5.4.0-26-generic  | grep LOCK_DOWN
CONFIG_LOCK_DOWN_IN_SECURE_BOOT=y
CONFIG_LOCK_DOWN_KERNEL_FORCE_NONE=y


So the error should caused by uefi lockdown feature.

Please refer to  https://mjg59.dreamwidth.org/50577.html for more
details.

To workaroud this, 
echo 1 > /proc/sys/kernel/sysrq
echo x > /proc/sysrq-trigger


or you can use sudo mokutil --disable-validation to disable it.

I tried "echo to /proc" way, the error msg disappered. You might try the
second way. Anyway, it's an upstream bug.

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

Title:
  blk_update_request: I/O error, dev sdb, sector 976772992 op 0x0:(READ)
  flags 0x80700 phys_seg 1 prio class 0

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  1) Ubuntu 19.10
  2) unknown
  3) no error
  4) error in log app.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  htpc   9157 F pulseaudio
   /dev/snd/controlC1:  htpc   9157 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 19.10
  InstallationDate: Installed on 2019-10-28 (48 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  IwConfig:
   lxcbr0no wireless extensions.
   
   lono wireless extensions.
   
   enp3s0no wireless extensions.
  MachineType: Gigabyte Technology Co., Ltd. GA-MA780G-UD3H
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-23-generic 
root=UUID=0fa008d8-2279-4e78-9043-161b7f514243 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-23-generic N/A
   linux-backports-modules-5.3.0-23-generic  N/A
   linux-firmware1.183.2
  RfKill:
   
  Tags:  wayland-session eoan
  Uname: Linux 5.3.0-23-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 07/13/2010
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F6b
  dmi.board.name: GA-MA780G-UD3H
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF6b:bd07/13/2010:svnGigabyteTechnologyCo.,Ltd.:pnGA-MA780G-UD3H:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-MA780G-UD3H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: GA-MA780G-UD3H
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to 

[Kernel-packages] [Bug 1856434] Re: blk_update_request: I/O error, dev sdb, sector 976772992 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 0

2020-05-26 Thread vmware-gos-Yuhua
Similar issue is found in VM ubuntu-20.04-live-server in ESXi 7.0GA
   blk_update_request: I/O error, dev sda, sector 3270728 op 0x9:(WRITE_ZEROES) 
flags 0x800 phys_seg 0 prio class 0


Attach the dmesg info. 
sda means the system disk.

Steps:
1) install guestOS with ubuntu-20.04-live-server-amd64.iso in ESXi 7.0GA
2) Follow the wizard to finish installation
3) I take no any operations on the VM. Sometimes the console output message:
   blk_update_request: I/O error, dev sda, sector 3270728 op 0x9:(WRITE_ZEROES) 
flags 0x800 phys_seg 0 prio class 0
   
   output from  command "dmesg"
   [  313.011817] blk_update_request: I/O error, dev sda, sector 3270672 op 
0x9:(WRITE_ZEROES) flags 0x800 phys_seg 0 prio class 0
   [  357.810551] sd 3:0:0:0: [sda] tag#19 FAILED Result: hostbyte=DID_OK 
driverbyte=DRIVER_SENSE
   [  357.810557] sd 3:0:0:0: [sda] tag#19 Sense Key : Vendor Specific(9) 
[current] 
   [  357.810560] sd 3:0:0:0: [sda] tag#19 <>ASC=0x80 
<>ASCQ=0x85 
   [  357.810562] sd 3:0:0:0: [sda] tag#19 CDB: Write same(16) 93 08 00 00 00 
00 00 31 e8 48 00 


Same error message when sda is NVMe disk, PVSCSI, SAS disk.  So this issue 
should be not related to virtual disk type.



** Attachment added: "dmesg.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1856434/+attachment/5377178/+files/dmesg.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/1856434

Title:
  blk_update_request: I/O error, dev sdb, sector 976772992 op 0x0:(READ)
  flags 0x80700 phys_seg 1 prio class 0

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  1) Ubuntu 19.10
  2) unknown
  3) no error
  4) error in log app.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  htpc   9157 F pulseaudio
   /dev/snd/controlC1:  htpc   9157 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 19.10
  InstallationDate: Installed on 2019-10-28 (48 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  IwConfig:
   lxcbr0no wireless extensions.
   
   lono wireless extensions.
   
   enp3s0no wireless extensions.
  MachineType: Gigabyte Technology Co., Ltd. GA-MA780G-UD3H
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-23-generic 
root=UUID=0fa008d8-2279-4e78-9043-161b7f514243 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-23-generic N/A
   linux-backports-modules-5.3.0-23-generic  N/A
   linux-firmware1.183.2
  RfKill:
   
  Tags:  wayland-session eoan
  Uname: Linux 5.3.0-23-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 07/13/2010
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F6b
  dmi.board.name: GA-MA780G-UD3H
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF6b:bd07/13/2010:svnGigabyteTechnologyCo.,Ltd.:pnGA-MA780G-UD3H:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-MA780G-UD3H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: GA-MA780G-UD3H
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1856434/+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 1755384] Re: hot-add memory can't be recognized for ubuntu-16.04.4-desktop-64 in ESXi

2018-08-22 Thread vmware-gos-Yuhua
This issue doesn't exist when check ubuntu18.04.1-desktop64.
Ubuntu-18.04.1-desktop has kernel 4.15.0-32-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/1755384

Title:
  hot-add memory can't be recognized for ubuntu-16.04.4-desktop-64 in
  ESXi

Status in linux:
  Confirmed
Status in linux package in Ubuntu:
  Triaged

Bug description:
  hot-add memory can't be recognized for ubuntu-16.04.4-desktop-64 in
  ESXi.

  
  Reproduce:
  -
  1. create VM with default setting in ESXi 6.5 / on-developing ESXi build 
7940658

  2. install geustOS zyh-ubuntu16.04.4-dsktop-64 image.

  3. reboot it after finish installation

  4. edit VM setting and enable hot-add CPU and memory

  5. open a terminal and type command "ls /sys/devices/system/memory", 
 find memory0 -- memory7 listed.

  6. edit VM setting and set default 1024M memory to 2048M

  7. type command "ls /sys/devices/system/memory", it still lists 
memory0-memory7.  
 No more memoryX is added.

 The hot-add memory can't be recognized.

  Expect:
  For step 7, it should list memory8--memory15 when type "ls 
/sys/devices/system/memory".

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel/+bug/1755384/+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 1755393] Re: hot-add CPU cause VM with ubuntu-16.04.4-desktop-64bit and ubuntu-18.04-desktop hang

2018-08-21 Thread vmware-gos-Yuhua
This issue doesn't exist when check ubuntu18.04.1-desktop64.   
Ubuntu-18.04.1-desktop has kernel 4.15.0-32-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/1755393

Title:
  hot-add CPU cause VM with ubuntu-16.04.4-desktop-64bit and
  ubuntu-18.04-desktop hang

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

Bug description:
  hot-add CPU cause VM with ubuntu-16.04.4-desktop-64bit hang in ESXi

  Reproduce:
  -
  1. create VM with EFI firewall in ESXi

  2. install geustOS with ubuntu16.04.4-dsktop-64bit image.

  3. reboot it after finish installation

  4. edit VM setting and enable hot-add CPU and memory

  5. edit VM setting and set default 1 vCPU to 2

  6. open a terminal and run script to enable vcpu1: "sudo
  ~/rescanCpu.sh"

  7. check the cpu number with command "cat /proc/cpuinfo" in terminal.
  but there is not output message for this command.  click anywhere on
  VM desktop, there is no response. It seems like VM hang.

  
  From vmware developer's analysis:
  

  Looks to me like Ubuntu's problem.  It noticed at 566 seconds after
  boot that CPU1 was hot-added.  Then perhaps you run code to online
  CPU, and doing so ended up with warning at blk-mq.c:

  Mar  6 17:41:33 vmware-virtual-machine kernel: [  566.583896] CPU1 has been 
hot-added
  Mar  6 17:42:17 vmware-virtual-machine CommAmqpListener[2376]: Initializing 
CommAmqpListener
  Mar  6 17:42:17 vmware-virtual-machine kernel: [  610.431990] SMP 
alternatives: switching to SMP code
  Mar  6 17:42:17 vmware-virtual-machine kernel: [  610.487612] x86: Booting 
SMP configuration:
  Mar  6 17:42:17 vmware-virtual-machine kernel: [  610.487616] smpboot: 
Booting Node 0 Processor 1 APIC 0x2
  Mar  6 17:42:17 vmware-virtual-machine kernel: [  610.489517] Disabled fast 
string operations
  Mar  6 17:42:17 vmware-virtual-machine kernel: [  610.492082] smpboot: CPU 1 
Converting physical 2 to logical package 1
  Mar  6 17:42:17 vmware-virtual-machine kernel: [  610.493162] Will online and 
init hotplugged CPU: 1
  Mar  6 17:42:17 vmware-virtual-machine kernel: [  610.524713] [ 
cut here ]
  Mar  6 17:42:17 vmware-virtual-machine kernel: [  610.524726] WARNING: CPU: 1 
PID: 2402 at /build/linux-hwe-4GXcua/linux-hwe-4.13.0/block/blk-mq.c:1106 
__blk_mq_run_hw_queue+0x7b/0xa0
  Mar  6 17:42:17 vmware-virtual-machine kernel: [  610.524727] Modules linked 
in: vmw_vsock_vmci_transport vsock nls_iso8859_1 vmw_balloon sb_edac 
crct10dif_pclmul crc32_pclmul ghash_clmulni_intel pcbc aesni_intel aes_x86_64 
crypto_simd glue_helpe
  r cryptd intel_rapl_perf joydev input_leds serio_raw shpchp vmw_vmci 
i2c_piix4 nfit tpm_crb mac_hid parport_pc ppdev lp parport autofs4 vmw_pvscsi 
vmwgfx ttm drm_kms_helper psmouse syscopyarea sysfillrect sysimgblt fb_sys_fops 
mptspi mptscsih drm
   mptbase nvme nvme_core vmxnet3 scsi_transport_spi ahci libahci pata_acpi 
floppy
  Mar  6 17:42:17 vmware-virtual-machine kernel: [  610.525006] CPU: 1 PID: 
2402 Comm: kworker/1:0H Not tainted 4.13.0-36-generic #40~16.04.1-Ubuntu
  Mar  6 17:42:17 vmware-virtual-machine kernel: [  610.525008] Hardware name: 
VMware, Inc. VMware7,1/440BX Desktop Reference Platform, BIOS 
VMW71.00V.7915097.B64.1802282254 02/28/2018
  Mar  6 17:42:17 vmware-virtual-machine kernel: [  610.525013] Workqueue: 
kblockd blk_mq_run_work_fn
  Mar  6 17:42:17 vmware-virtual-machine kernel: [  610.525016] task: 
8ab5326b task.stack: a694441d8000
  Mar  6 17:42:17 vmware-virtual-machine kernel: [  610.525021] RIP: 
0010:__blk_mq_run_hw_queue+0x7b/0xa0
  Mar  6 17:42:17 vmware-virtual-machine kernel: [  610.525023] RSP: 
0018:a694441dbe38 EFLAGS: 00010202
  Mar  6 17:42:17 vmware-virtual-machine kernel: [  610.525026] RAX: 
0001 RBX: 8ab50b4edc00 RCX: 8ab53c662760
  Mar  6 17:42:17 vmware-virtual-machine kernel: [  610.525028] RDX: 
8ab50b9cba60 RSI: 8ab50b4edc40 RDI: 8ab50b4edc00
  Mar  6 17:42:17 vmware-virtual-machine kernel: [  610.525029] RBP: 
a694441dbe50 R08:  R09: 0001
  Mar  6 17:42:17 vmware-virtual-machine kernel: [  610.525031] R10: 
02e2 R11: 029b R12: 8ab5310d69c0
  Mar  6 17:42:17 vmware-virtual-machine kernel: [  610.525032] R13: 
8ab53c662740 R14: 8ab53c668300 R15: 
  Mar  6 17:42:17 vmware-virtual-machine kernel: [  610.525036] FS:  
() GS:8ab53c64() knlGS:
  Mar  6 17:42:17 vmware-virtual-machine kernel: [  610.525038] CS:  0010 DS: 
 ES:  CR0: 80050033
  Mar  6 17:42:17 vmware-virtual-machine kernel: [  610.525039] CR2: 
7ff14dd7ab00 CR3: 1180a002 CR4: 001606e0
  Mar  6 17:42:17 vmware-virtual-machine kernel: [  610.525140] Cal

[Kernel-packages] [Bug 1755393] Re: hot-add CPU cause VM with ubuntu-16.04.4-desktop-64bit and ubuntu-18.04-desktop hang

2018-08-21 Thread vmware-gos-Yuhua
** Summary changed:

- hot-add CPU cause VM with ubuntu-16.04.4-desktop-64bit / ubuntu-18.04-desktop 
hang
+ hot-add CPU cause VM with ubuntu-16.04.4-desktop-64bit and 
ubuntu-18.04-desktop hang

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

Title:
  hot-add CPU cause VM with ubuntu-16.04.4-desktop-64bit and
  ubuntu-18.04-desktop hang

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

Bug description:
  hot-add CPU cause VM with ubuntu-16.04.4-desktop-64bit hang in ESXi

  Reproduce:
  -
  1. create VM with EFI firewall in ESXi

  2. install geustOS with ubuntu16.04.4-dsktop-64bit image.

  3. reboot it after finish installation

  4. edit VM setting and enable hot-add CPU and memory

  5. edit VM setting and set default 1 vCPU to 2

  6. open a terminal and run script to enable vcpu1: "sudo
  ~/rescanCpu.sh"

  7. check the cpu number with command "cat /proc/cpuinfo" in terminal.
  but there is not output message for this command.  click anywhere on
  VM desktop, there is no response. It seems like VM hang.

  
  From vmware developer's analysis:
  

  Looks to me like Ubuntu's problem.  It noticed at 566 seconds after
  boot that CPU1 was hot-added.  Then perhaps you run code to online
  CPU, and doing so ended up with warning at blk-mq.c:

  Mar  6 17:41:33 vmware-virtual-machine kernel: [  566.583896] CPU1 has been 
hot-added
  Mar  6 17:42:17 vmware-virtual-machine CommAmqpListener[2376]: Initializing 
CommAmqpListener
  Mar  6 17:42:17 vmware-virtual-machine kernel: [  610.431990] SMP 
alternatives: switching to SMP code
  Mar  6 17:42:17 vmware-virtual-machine kernel: [  610.487612] x86: Booting 
SMP configuration:
  Mar  6 17:42:17 vmware-virtual-machine kernel: [  610.487616] smpboot: 
Booting Node 0 Processor 1 APIC 0x2
  Mar  6 17:42:17 vmware-virtual-machine kernel: [  610.489517] Disabled fast 
string operations
  Mar  6 17:42:17 vmware-virtual-machine kernel: [  610.492082] smpboot: CPU 1 
Converting physical 2 to logical package 1
  Mar  6 17:42:17 vmware-virtual-machine kernel: [  610.493162] Will online and 
init hotplugged CPU: 1
  Mar  6 17:42:17 vmware-virtual-machine kernel: [  610.524713] [ 
cut here ]
  Mar  6 17:42:17 vmware-virtual-machine kernel: [  610.524726] WARNING: CPU: 1 
PID: 2402 at /build/linux-hwe-4GXcua/linux-hwe-4.13.0/block/blk-mq.c:1106 
__blk_mq_run_hw_queue+0x7b/0xa0
  Mar  6 17:42:17 vmware-virtual-machine kernel: [  610.524727] Modules linked 
in: vmw_vsock_vmci_transport vsock nls_iso8859_1 vmw_balloon sb_edac 
crct10dif_pclmul crc32_pclmul ghash_clmulni_intel pcbc aesni_intel aes_x86_64 
crypto_simd glue_helpe
  r cryptd intel_rapl_perf joydev input_leds serio_raw shpchp vmw_vmci 
i2c_piix4 nfit tpm_crb mac_hid parport_pc ppdev lp parport autofs4 vmw_pvscsi 
vmwgfx ttm drm_kms_helper psmouse syscopyarea sysfillrect sysimgblt fb_sys_fops 
mptspi mptscsih drm
   mptbase nvme nvme_core vmxnet3 scsi_transport_spi ahci libahci pata_acpi 
floppy
  Mar  6 17:42:17 vmware-virtual-machine kernel: [  610.525006] CPU: 1 PID: 
2402 Comm: kworker/1:0H Not tainted 4.13.0-36-generic #40~16.04.1-Ubuntu
  Mar  6 17:42:17 vmware-virtual-machine kernel: [  610.525008] Hardware name: 
VMware, Inc. VMware7,1/440BX Desktop Reference Platform, BIOS 
VMW71.00V.7915097.B64.1802282254 02/28/2018
  Mar  6 17:42:17 vmware-virtual-machine kernel: [  610.525013] Workqueue: 
kblockd blk_mq_run_work_fn
  Mar  6 17:42:17 vmware-virtual-machine kernel: [  610.525016] task: 
8ab5326b task.stack: a694441d8000
  Mar  6 17:42:17 vmware-virtual-machine kernel: [  610.525021] RIP: 
0010:__blk_mq_run_hw_queue+0x7b/0xa0
  Mar  6 17:42:17 vmware-virtual-machine kernel: [  610.525023] RSP: 
0018:a694441dbe38 EFLAGS: 00010202
  Mar  6 17:42:17 vmware-virtual-machine kernel: [  610.525026] RAX: 
0001 RBX: 8ab50b4edc00 RCX: 8ab53c662760
  Mar  6 17:42:17 vmware-virtual-machine kernel: [  610.525028] RDX: 
8ab50b9cba60 RSI: 8ab50b4edc40 RDI: 8ab50b4edc00
  Mar  6 17:42:17 vmware-virtual-machine kernel: [  610.525029] RBP: 
a694441dbe50 R08:  R09: 0001
  Mar  6 17:42:17 vmware-virtual-machine kernel: [  610.525031] R10: 
02e2 R11: 029b R12: 8ab5310d69c0
  Mar  6 17:42:17 vmware-virtual-machine kernel: [  610.525032] R13: 
8ab53c662740 R14: 8ab53c668300 R15: 
  Mar  6 17:42:17 vmware-virtual-machine kernel: [  610.525036] FS:  
() GS:8ab53c64() knlGS:
  Mar  6 17:42:17 vmware-virtual-machine kernel: [  610.525038] CS:  0010 DS: 
 ES:  CR0: 80050033
  Mar  6 17:42:17 vmware-virtual-machine kernel: [  610.525039] CR2: 
7ff14dd7ab00 CR3: 1180a002 CR4: 001606

[Kernel-packages] [Bug 1564217] Re: Hot add of a disk attached to LSI Logic SAS is not getting detected

2017-05-12 Thread vmware-gos-Yuhua
Hi Joseph,
   This issue is fixed in VMware vsphere product. 
   It is not vSphere bug but we modified our code so that it does not trigger 
the problem 

best regards
Yuhua Zou

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

Title:
  Hot add of a disk attached to LSI Logic SAS is not getting detected

Status in Linux:
  Unknown
Status in linux package in Ubuntu:
  Triaged

Bug description:
  when install VM ubuntu 16.04 beta1 image in VMware ESXi,  Hot add of
  a disk attached to LSI Logic SAS is not getting detected

  Steps to reproduce:
  1.Install ubuntu 16.04 beta1 with BUS logic SAS as boot controller in VMware 
ESXi 6.0GA.
  2.Power on the VM
  3.Hot add a hard disk to LSI SAS controller, the ubuntu 16.04 does not detect 
the disk

  the developer from VMware company investigate it and find it's a kernel issue.
  Bug 114611(https://bugzilla.kernel.org/show_bug.cgi?id=114611) is tracking it 
and now have fix for it.

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