Sorry this took so long, but I can confirm that the bug does not
reproduce on kernel 4.10.17-041017-generic that you linked to, or on
4.13.0-37-generic from 17.10. Interestingly, kernel 4.10.17 is 3-4x
slower at writing to the NVM device than 4.13.0-37, with the former I
get 260-290 MB/s, with the latter I get about 1 GB/s.

In any case, the bug is fixed in 4.10.17.

You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.

  Writing to GPT partition on NVM device triggers "Kernel BUG"

Status in linux package in Ubuntu:

Bug description:
  When I try writing a large amount of data to a GPT partition on my NVM
  SSD using dd, after a second or so I get "kernel BUG" messages in
  dmesg, and the writing comes to a halt. The machine remains responsive
  and I can write to other disks, but if I run "sync", it hangs forever.

  The bug is 100 % repeatable. To replicate, run:

    dd if=/dev/zero of=/dev/nvme0n1p1

  This happens only when I write more than 0.5-1.5 GiB to a GPT
  partition on the NVM device. The bug does not happen in the following

  - writing just 500 MB on a GPT partition
  - writing to the raw device (/dev/nvme0n1)
  - writing to a DOS partition (i.e. when the NVM device is using a DOS style 
partition table)

  The device in question is a 1 TB Samsung 960 EVO M.2 SSD.
  Ubuntu release: 17.04

  I have dmesg logs available of four instances of this happening, with very 
similar stack traces. I will be happy to experiment and provide any additional 
information you may need.
  ApportVersion: 2.20.4-0ubuntu4.1
  Architecture: amd64
   /dev/snd/controlC1:  jl         1792 F.... pulseaudio
   /dev/snd/controlC0:  jl         1792 F.... pulseaudio
  CurrentDesktop: Unity:Unity7
  DistroRelease: Ubuntu 17.04
   lo        no wireless extensions.
   enp0s31f6  no wireless extensions.
  MachineType: System manufacturer System Product Name
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  Package: linux (not installed)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-24-generic 
root=UUID=1fb7b4e5-d026-4b10-a87b-c7726fe0b1a3 ro
  ProcVersionSignature: Ubuntu 4.10.0-24.28-generic 4.10.15
   linux-restricted-modules-4.10.0-24-generic N/A
   linux-backports-modules-4.10.0-24-generic  N/A
   linux-firmware                             1.164.1
  Tags:  zesty
  Uname: Linux 4.10.0-24-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True 09/19/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2202
  dmi.board.asset.tag: Default string Z170-A
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
dmi:bvnAmericanMegatrendsInc.:bvr2202:bd09/19/2016:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ170-A:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

To manage notifications about this bug go to:

Mailing list:
Post to     :
Unsubscribe :
More help   :

Reply via email to