[Kernel-packages] [Bug 1720228] Re: User reports excessive ALUA retry messages

[Dragan S.]

** Changed in: linux (Ubuntu Xenial)
   Importance: Undecided => High

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

Title:
  User reports excessive ALUA retry messages

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Xenial:
  New

Bug description:
   SRU Justification:

  Impact:
  User reports excessive ALUA messages on Ubuntu Trusty, kernel 
Ubuntu-lts-4.4.0-91.114_14.04.1
  Messages appear after a LUN disappears and there are hundreds of them 
flooding the log...

  [263095.795873] sd 3:0:0:129: alua: rtpg retry
  [263095.795874] sd 3:0:0:129: [alua] Sense Key : Illegal Request [current]
  [263095.795876] sd 3:0:0:129: [alua] Add. Sense: Logical unit not supported

  This causes an intense requeing of the ALUA work queue for 60 seconds
  and it floods the kernel log

  
  Fix:
  UBUNTU: scsi: fixe excessive ALUA (LP: #1720228)
  
  BugLink: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1720228

  The err value was initialized to 0 to prevent random assignemtn
  the fix is a cherry-pick from linus tree 
a4bd85203190990ad808abbd4a5dc848a950002c

  
  Testcase:
  User reports issue when a network iscsi disk gets disconnected.

  
  Original Bug Text:

  User reports excessive ALUA messages on Ubuntu Trusty, kernel Ubuntu-
  lts-4.4.0-91.114_14.04.1

  Messages appear after a LUN disappears and there are hundreds of them
  flooding the log...

  [263095.795873] sd 3:0:0:129: alua: rtpg retry
  [263095.795874] sd 3:0:0:129: [alua] Sense Key : Illegal Request [current]
  [263095.795876] sd 3:0:0:129: [alua] Add. Sense: Logical unit not supported
  [263095.795961] sd 3:0:0:129: alua: rtpg retry
  [263095.795962] sd 3:0:0:129: [alua] Sense Key : Illegal Request [current]
  [263095.795964] sd 3:0:0:129: [alua] Add. Sense: Logical unit not supported
  [263095.796049] sd 3:0:0:129: alua: rtpg retry
  [263095.796052] sd 3:0:0:129: [alua] Sense Key : Illegal Request [current]
  [263095.796054] sd 3:0:0:129: [alua] Add. Sense: Logical unit not supported
  [263095.796140] sd 3:0:0:129: alua: rtpg retry
  [263095.796142] sd 3:0:0:129: [alua] Sense Key : Illegal Request [current]
  [263095.796143] sd 3:0:0:129: [alua] Add. Sense: Logical unit not supported
  [263095.796224] sd 3:0:0:129: alua: rtpg retry
  [263095.796226] sd 3:0:0:129: [alua] Sense Key : Illegal Request [current]
  [263095.796227] sd 3:0:0:129: [alua] Add. Sense: Logical unit not supported
  [263095.796473] sd 3:0:0:129: alua: rtpg retry
  [263095.796475] sd 3:0:0:129: [alua] Sense Key : Illegal Request [current]
  [263095.796476] sd 3:0:0:129: [alua] Add. Sense: Logical unit not supported
  [263095.796604] sd 3:0:0:129: alua: rtpg retry
  [263095.796606] sd 3:0:0:129: [alua] Sense Key : Illegal Request [current]
  [263095.796607] sd 3:0:0:129: [alua] Add. Sense: Logical unit not supported
  [263095.796691] sd 3:0:0:129: alua: rtpg retry
  [263095.796693] sd 3:0:0:129: [alua] Sense Key : Illegal Request [current]
  [263095.796694] sd 3:0:0:129: [alua] Add. Sense: Logical unit not supported
  [263095.796778] sd 3:0:0:129: alua: rtpg retry
  [263095.796780] sd 3:0:0:129: [alua] Sense Key : Illegal Request [current]
  [263095.796781] sd 3:0:0:129: [alua] Add. Sense: Logical unit not supported
  [263095.796868] sd 3:0:0:129: alua: rtpg retry
  [263095.796869] sd 3:0:0:129: [alua] Sense Key : Illegal Request [current]
  [263095.796871] sd 3:0:0:129: [alua] Add. Sense: Logical unit not supported
  [263095.796951] sd 3:0:0:129: alua: rtpg retry
  [263095.796953] sd 3:0:0:129: [alua] Sense Key : Illegal Request [current]
  [263095.796954] sd 3:0:0:129: [alua] Add. Sense: Logical unit not supported
  [263095.797034] sd 3:0:0:129: alua: rtpg retry
  [263095.797035] sd 3:0:0:129: [alua] Sense Key : Illegal Request [current]
  [263095.797037] sd 3:0:0:129: [alua] Add. Sense: Logical unit not supported
  [263095.797117] sd 3:0:0:129: alua: rtpg retry
  [263095.797119] sd 3:0:0:129: [alua] Sense Key : Illegal Request [current]
  [263095.797120] sd 3:0:0:129: [alua] Add. Sense: Logical unit not supported
  [263095.797202] sd 3:0:0:129: alua: rtpg retry
  [263095.797203] sd 3:0:0:129: [alua] Sense Key : Illegal Request [current]
  [263095.797205] sd 3:0:0:129: [alua] Add. Sense: Logical unit not supported
  [263095.797288] sd 3:0:0:129: alua: rtpg retry
  [263095.797289] sd 3:0:0:129: [alua] Sense Key : Illegal Request [current]
  [263095.797290] sd 3:0:0:129: [alua] Add. Sense: Logical unit not supported
  [263095.797387] sd 3:0:0:129: alua: rtpg retry
  [263095.797388] sd 3:0:0:129: [alua] Sense Key : Illegal Request [current]
  [263095.797390] sd 3:0:0:129: [alua] Add. Sense: Logical unit not supported
  [263095.797470] sd 3:0:0:129: alua: rtpg retry
  [263095.797471] sd 3:0:0:129: [alua] Sense Key : Illegal Request [current]
  [263095.797472] sd 3:0:0:129: [alua] Add. Sense: Logical un

[Kernel-packages] [Bug 1720228] Re: User reports excessive ALUA retry messages

[Dragan S.]

Hi Stefan-

fix verified so I changed the tag to verification-done-xenia

** Tags removed: verification-needed-xenial
** Tags added: verification-done-xenia

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

Title:
  User reports excessive ALUA retry messages

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Xenial:
  Fix Committed

Bug description:
   SRU Justification:

  Impact:
  User reports excessive ALUA messages on Ubuntu Trusty, kernel 
Ubuntu-lts-4.4.0-91.114_14.04.1
  Messages appear after a LUN disappears and there are hundreds of them 
flooding the log...

  [263095.795873] sd 3:0:0:129: alua: rtpg retry
  [263095.795874] sd 3:0:0:129: [alua] Sense Key : Illegal Request [current]
  [263095.795876] sd 3:0:0:129: [alua] Add. Sense: Logical unit not supported

  This causes an intense requeing of the ALUA work queue for 60 seconds
  and it floods the kernel log

  
  Fix:
  UBUNTU: scsi: fixe excessive ALUA (LP: #1720228)
  
  BugLink: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1720228

  The err value was initialized to 0 to prevent random assignemtn
  the fix is a cherry-pick from linus tree 
a4bd85203190990ad808abbd4a5dc848a950002c

  
  Testcase:
  User reports issue when a network iscsi disk gets disconnected.

  
  Original Bug Text:

  User reports excessive ALUA messages on Ubuntu Trusty, kernel Ubuntu-
  lts-4.4.0-91.114_14.04.1

  Messages appear after a LUN disappears and there are hundreds of them
  flooding the log...

  [263095.795873] sd 3:0:0:129: alua: rtpg retry
  [263095.795874] sd 3:0:0:129: [alua] Sense Key : Illegal Request [current]
  [263095.795876] sd 3:0:0:129: [alua] Add. Sense: Logical unit not supported
  [263095.795961] sd 3:0:0:129: alua: rtpg retry
  [263095.795962] sd 3:0:0:129: [alua] Sense Key : Illegal Request [current]
  [263095.795964] sd 3:0:0:129: [alua] Add. Sense: Logical unit not supported
  [263095.796049] sd 3:0:0:129: alua: rtpg retry
  [263095.796052] sd 3:0:0:129: [alua] Sense Key : Illegal Request [current]
  [263095.796054] sd 3:0:0:129: [alua] Add. Sense: Logical unit not supported
  [263095.796140] sd 3:0:0:129: alua: rtpg retry
  [263095.796142] sd 3:0:0:129: [alua] Sense Key : Illegal Request [current]
  [263095.796143] sd 3:0:0:129: [alua] Add. Sense: Logical unit not supported
  [263095.796224] sd 3:0:0:129: alua: rtpg retry
  [263095.796226] sd 3:0:0:129: [alua] Sense Key : Illegal Request [current]
  [263095.796227] sd 3:0:0:129: [alua] Add. Sense: Logical unit not supported
  [263095.796473] sd 3:0:0:129: alua: rtpg retry
  [263095.796475] sd 3:0:0:129: [alua] Sense Key : Illegal Request [current]
  [263095.796476] sd 3:0:0:129: [alua] Add. Sense: Logical unit not supported
  [263095.796604] sd 3:0:0:129: alua: rtpg retry
  [263095.796606] sd 3:0:0:129: [alua] Sense Key : Illegal Request [current]
  [263095.796607] sd 3:0:0:129: [alua] Add. Sense: Logical unit not supported
  [263095.796691] sd 3:0:0:129: alua: rtpg retry
  [263095.796693] sd 3:0:0:129: [alua] Sense Key : Illegal Request [current]
  [263095.796694] sd 3:0:0:129: [alua] Add. Sense: Logical unit not supported
  [263095.796778] sd 3:0:0:129: alua: rtpg retry
  [263095.796780] sd 3:0:0:129: [alua] Sense Key : Illegal Request [current]
  [263095.796781] sd 3:0:0:129: [alua] Add. Sense: Logical unit not supported
  [263095.796868] sd 3:0:0:129: alua: rtpg retry
  [263095.796869] sd 3:0:0:129: [alua] Sense Key : Illegal Request [current]
  [263095.796871] sd 3:0:0:129: [alua] Add. Sense: Logical unit not supported
  [263095.796951] sd 3:0:0:129: alua: rtpg retry
  [263095.796953] sd 3:0:0:129: [alua] Sense Key : Illegal Request [current]
  [263095.796954] sd 3:0:0:129: [alua] Add. Sense: Logical unit not supported
  [263095.797034] sd 3:0:0:129: alua: rtpg retry
  [263095.797035] sd 3:0:0:129: [alua] Sense Key : Illegal Request [current]
  [263095.797037] sd 3:0:0:129: [alua] Add. Sense: Logical unit not supported
  [263095.797117] sd 3:0:0:129: alua: rtpg retry
  [263095.797119] sd 3:0:0:129: [alua] Sense Key : Illegal Request [current]
  [263095.797120] sd 3:0:0:129: [alua] Add. Sense: Logical unit not supported
  [263095.797202] sd 3:0:0:129: alua: rtpg retry
  [263095.797203] sd 3:0:0:129: [alua] Sense Key : Illegal Request [current]
  [263095.797205] sd 3:0:0:129: [alua] Add. Sense: Logical unit not supported
  [263095.797288] sd 3:0:0:129: alua: rtpg retry
  [263095.797289] sd 3:0:0:129: [alua] Sense Key : Illegal Request [current]
  [263095.797290] sd 3:0:0:129: [alua] Add. Sense: Logical unit not supported
  [263095.797387] sd 3:0:0:129: alua: rtpg retry
  [263095.797388] sd 3:0:0:129: [alua] Sense Key : Illegal Request [current]
  [263095.797390] sd 3:0:0:129: [alua] Add. Sense: Logical unit not supported
  [263095.797470] sd 3:0:0:129: alua: rtpg retry
  [263095.797471] sd 3:0:0:129: [alua] Se

[Kernel-packages] [Bug 1720228] Re: User reports excessive ALUA retry messages

[Dragan S.]

Khaled, any ides when this fix will be released?

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

Title:
  User reports excessive ALUA retry messages

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Xenial:
  Fix Committed

Bug description:
   SRU Justification:

  Impact:
  User reports excessive ALUA messages on Ubuntu Trusty, kernel 
Ubuntu-lts-4.4.0-91.114_14.04.1
  Messages appear after a LUN disappears and there are hundreds of them 
flooding the log...

  [263095.795873] sd 3:0:0:129: alua: rtpg retry
  [263095.795874] sd 3:0:0:129: [alua] Sense Key : Illegal Request [current]
  [263095.795876] sd 3:0:0:129: [alua] Add. Sense: Logical unit not supported

  This causes an intense requeing of the ALUA work queue for 60 seconds
  and it floods the kernel log

  
  Fix:
  UBUNTU: scsi: fixe excessive ALUA (LP: #1720228)
  
  BugLink: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1720228

  The err value was initialized to 0 to prevent random assignemtn
  the fix is a cherry-pick from linus tree 
a4bd85203190990ad808abbd4a5dc848a950002c

  
  Testcase:
  User reports issue when a network iscsi disk gets disconnected.

  
  Original Bug Text:

  User reports excessive ALUA messages on Ubuntu Trusty, kernel Ubuntu-
  lts-4.4.0-91.114_14.04.1

  Messages appear after a LUN disappears and there are hundreds of them
  flooding the log...

  [263095.795873] sd 3:0:0:129: alua: rtpg retry
  [263095.795874] sd 3:0:0:129: [alua] Sense Key : Illegal Request [current]
  [263095.795876] sd 3:0:0:129: [alua] Add. Sense: Logical unit not supported
  [263095.795961] sd 3:0:0:129: alua: rtpg retry
  [263095.795962] sd 3:0:0:129: [alua] Sense Key : Illegal Request [current]
  [263095.795964] sd 3:0:0:129: [alua] Add. Sense: Logical unit not supported
  [263095.796049] sd 3:0:0:129: alua: rtpg retry
  [263095.796052] sd 3:0:0:129: [alua] Sense Key : Illegal Request [current]
  [263095.796054] sd 3:0:0:129: [alua] Add. Sense: Logical unit not supported
  [263095.796140] sd 3:0:0:129: alua: rtpg retry
  [263095.796142] sd 3:0:0:129: [alua] Sense Key : Illegal Request [current]
  [263095.796143] sd 3:0:0:129: [alua] Add. Sense: Logical unit not supported
  [263095.796224] sd 3:0:0:129: alua: rtpg retry
  [263095.796226] sd 3:0:0:129: [alua] Sense Key : Illegal Request [current]
  [263095.796227] sd 3:0:0:129: [alua] Add. Sense: Logical unit not supported
  [263095.796473] sd 3:0:0:129: alua: rtpg retry
  [263095.796475] sd 3:0:0:129: [alua] Sense Key : Illegal Request [current]
  [263095.796476] sd 3:0:0:129: [alua] Add. Sense: Logical unit not supported
  [263095.796604] sd 3:0:0:129: alua: rtpg retry
  [263095.796606] sd 3:0:0:129: [alua] Sense Key : Illegal Request [current]
  [263095.796607] sd 3:0:0:129: [alua] Add. Sense: Logical unit not supported
  [263095.796691] sd 3:0:0:129: alua: rtpg retry
  [263095.796693] sd 3:0:0:129: [alua] Sense Key : Illegal Request [current]
  [263095.796694] sd 3:0:0:129: [alua] Add. Sense: Logical unit not supported
  [263095.796778] sd 3:0:0:129: alua: rtpg retry
  [263095.796780] sd 3:0:0:129: [alua] Sense Key : Illegal Request [current]
  [263095.796781] sd 3:0:0:129: [alua] Add. Sense: Logical unit not supported
  [263095.796868] sd 3:0:0:129: alua: rtpg retry
  [263095.796869] sd 3:0:0:129: [alua] Sense Key : Illegal Request [current]
  [263095.796871] sd 3:0:0:129: [alua] Add. Sense: Logical unit not supported
  [263095.796951] sd 3:0:0:129: alua: rtpg retry
  [263095.796953] sd 3:0:0:129: [alua] Sense Key : Illegal Request [current]
  [263095.796954] sd 3:0:0:129: [alua] Add. Sense: Logical unit not supported
  [263095.797034] sd 3:0:0:129: alua: rtpg retry
  [263095.797035] sd 3:0:0:129: [alua] Sense Key : Illegal Request [current]
  [263095.797037] sd 3:0:0:129: [alua] Add. Sense: Logical unit not supported
  [263095.797117] sd 3:0:0:129: alua: rtpg retry
  [263095.797119] sd 3:0:0:129: [alua] Sense Key : Illegal Request [current]
  [263095.797120] sd 3:0:0:129: [alua] Add. Sense: Logical unit not supported
  [263095.797202] sd 3:0:0:129: alua: rtpg retry
  [263095.797203] sd 3:0:0:129: [alua] Sense Key : Illegal Request [current]
  [263095.797205] sd 3:0:0:129: [alua] Add. Sense: Logical unit not supported
  [263095.797288] sd 3:0:0:129: alua: rtpg retry
  [263095.797289] sd 3:0:0:129: [alua] Sense Key : Illegal Request [current]
  [263095.797290] sd 3:0:0:129: [alua] Add. Sense: Logical unit not supported
  [263095.797387] sd 3:0:0:129: alua: rtpg retry
  [263095.797388] sd 3:0:0:129: [alua] Sense Key : Illegal Request [current]
  [263095.797390] sd 3:0:0:129: [alua] Add. Sense: Logical unit not supported
  [263095.797470] sd 3:0:0:129: alua: rtpg retry
  [263095.797471] sd 3:0:0:129: [alua] Sense Key : Illegal Request [current]
  [263095.797472] sd 3:0:0:129: [alua] Add. Sense: Logical unit not supp

[Kernel-packages] [Bug 1756197] [NEW] Kernel panic BUG_ON in 4.4.0-92-generic fs/ext4/inode.c:1894!

[Dragan S.]

ucm(OE) 
ib_ucm(OE) rdma_cm(OE) iw_cm(OE) configfs ib_ipoib(OE) ib_cm(OE) ib_uverbs(OE) 
ib_umad(OE) mlx5_ib(OE) mlx4_ib(OE) ib_core(OE) mlx4_en(OE) mlx4_core(OE) 
ipmi_ssif mxm_wmi intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp 
kvm_intel kvm irqbypass crct10dif_pclmul crc32_pclmul ghash_clmulni_intel 
aesni_intel aes_x86_64 lrw gf128mul glue_helper ablk_helper cryptd joydev 
input_leds sb_edac edac_core nvidia_uvm(POE) lpc_ich mei_me mei shpchp
[2503476.691252]  8250_fintek ipmi_si acpi_power_meter wmi mac_hid ipmi_devintf 
ipmi_msghandler knem(OE) sunrpc autofs4 nvidia_drm(POE) nvidia_modeset(POE) ses 
enclosure ast ixgbe i2c_algo_bit dca ttm nvidia(POE) drm_kms_helper syscopyarea 
hid_generic vxlan sysfillrect sysimgblt ip6_udp_tunnel mlx5_core(OE) usbhid 
udp_tunnel mlx_compat(OE) megaraid_sas fb_sys_fops hid ahci ptp libahci drm 
pps_core mdio fjes
[2503476.692726] CPU: 23 PID: 27629 Comm: kworker/u162:3 Tainted: P  D
OE   4.4.0-92-generic #115-Ubuntu
[2503476.693996] Hardware name: NVIDIA DGX-1 with V100/DGX-1 with V100, BIOS 
S2W_3A04 08/29/2017
[2503476.695119] task: 884b48124600 ti: 887a04a58000 task.ti: 
887a04a58000
[2503476.696215] RIP: 0010:[]  [] 
kthread_data+0x10/0x20
[2503476.697313] RSP: 0018:887a04a5b528  EFLAGS: 00010002
[2503476.698404] RAX:  RBX: 0017 RCX: 
82109e80
[2503476.699529] RDX: 0017 RSI: 0017 RDI: 
884b48124600
[2503476.700569] RBP: 887a04a5b528 R08:  R09: 

[2503476.701511] R10: 884b48124660 R11: 6c00 R12: 

[2503476.702419] R13: 00016dc0 R14: 884b48124600 R15: 
887f7ecd6dc0
[2503476.703346] FS:  () GS:887f7ecc() 
knlGS:
[2503476.704206] CS:  0010 DS:  ES:  CR0: 80050033
[2503476.705054] CR2: 0028 CR3: 02e0a000 CR4: 
003406e0
[2503476.705898] DR0:  DR1:  DR2: 

[2503476.706732] DR3:  DR6: fffe0ff0 DR7: 
0400
[2503476.707606] Stack:
[2503476.708423]  887a04a5b540 8109b9c1 887f7ecd6dc0 
887a04a5b590
[2503476.709253]  8183dab0 887f60547eb0 887a0017 
884b48124600
[2503476.710079]  887a04a5c000 884b48124cd0 887a04a5b140 

[2503476.710922] Call Trace:
[2503476.711769]  [] wq_worker_sleeping+0x11/0x90
[2503476.712594]  [] __schedule+0x650/0xa30
[2503476.713414]  [] schedule+0x35/0x80
[2503476.714228]  [] do_exit+0x775/0xb00
[2503476.715061]  [] oops_end+0xa1/0xd0
[2503476.715883]  [] die+0x4b/0x70
[2503476.716681]  [] do_trap+0xb1/0x140
[2503476.717481]  [] do_error_trap+0x89/0x110
[2503476.718280]  [] ? ext4_writepage+0x2ec/0x540
[2503476.719099]  [] ? do_get_write_access+0x38d/0x490
[2503476.719909]  [] ? __wake_up+0x44/0x50
[2503476.720690]  [] do_invalid_op+0x20/0x30
[2503476.721468]  [] invalid_op+0x1e/0x30
[2503476.722241]  [] ? ext4_writepage+0x2ec/0x540
[2503476.723044]  [] ? page_mkclean+0x73/0xa0
[2503476.723847]  [] ? page_referenced_one+0x1a0/0x1a0
[2503476.724621]  [] __writepage+0x12/0x30
[2503476.725396]  [] write_cache_pages+0x1ee/0x510
[2503476.726172]  [] ? ext4_writepage+0x540/0x540
[2503476.726967]  [] ext4_writepages+0x195/0xd30
[2503476.727770]  [] ? generic_writepages+0x5b/0x80
[2503476.728545]  [] do_writepages+0x1e/0x30
[2503476.729318]  [] __writeback_single_inode+0x45/0x340
[2503476.730093]  [] writeback_sb_inodes+0x262/0x600
[2503476.730870]  [] __writeback_inodes_wb+0x8c/0xc0
[2503476.731696]  [] wb_writeback+0x253/0x310
[2503476.732472]  [] wb_workfn+0x24d/0x400
[2503476.733248]  [] process_one_work+0x165/0x480
[2503476.734026]  [] worker_thread+0x4b/0x4c0
[2503476.734801]  [] ? process_one_work+0x480/0x480
[2503476.735691]  [] kthread+0xe5/0x100
[2503476.736464]  [] ? kthread_create_on_node+0x1e0/0x1e0
[2503476.737240]  [] ret_from_fork+0x3f/0x70
[2503476.737991]  [] ? kthread_create_on_node+0x1e0/0x1e0
[2503476.738724] Code: ff ff ff be 49 02 00 00 48 c7 c7 98 b9 cb 81 e8 e7 00 fe 
ff e9 a6 fe ff ff 66 90 0f 1f 44 00 00 48 8b 87 18 05 00 00 55 48 89 e5 <48> 8b 
40 d8 5d c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 
[2503476.739609] RIP  [] kthread_data+0x10/0x20
[2503476.740384]  RSP 
[2503476.741149] CR2: ffd8
[2503476.741909] ---[ end trace 03d35738081084c7 ]---

** Affects: linux (Ubuntu)
 Importance: Undecided
     Assignee: Dragan S. (dragan-s)
 Status: New

** Changed in: linux (Ubuntu)
 Assignee: (unassigned) => Dragan S. (dragan-s)

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

Title:
  Kernel panic BUG_ON in 4.4.0-92-generic fs/ext4/inode.c:1894!

Status in linux package in Ubuntu:
  New

Bug description:
  User reports a kernel panic under load:

  [2503476.606215

[Kernel-packages] [Bug 1750038] [NEW] user space process hung in 'D' state waiting for disk io to complete

[Dragan S.]

Public bug reported:

Using Ubuntu Xenial user reports processes hang in D state waiting for
disk io.

Ocassionally one of the applications gets into "D" state on NFS
reads/sync and close system calls. based on the kernel backtraces seems
to be stuck in kmalloc allocation during cleanup of dirty NFS pages.

All the subsequent operations on the NFS mounts are stuck and reboot is
required to rectify the situation.

[Test scenario]

1) Applications running in Docker environment 
2) Application have cgroup limits --cpu-shares --memory -shm-limit 
3) python and C++ based applications (torch and caffe) 
4) Applications read big lmdb files and write results to NFS shares 
5) use NFS v3 , hard and fscache is enabled 
6) now swap space is configured 

This prevents all other I/O activity on that mount to hang.

we are running into this issue more frequently and identified few
applications causing this problem.

As updated in the description, the problem seems to be happening when
exercising the stack

try_to_free_mem_cgroup_pages+0xba/0x1a0

we see this with docker containers with cgroup option --memory
.

whenever there is a deadlock, we see that the process that is hung has
reached the maximum cgroup limit, multiple times and typically cleans up
dirty data and caches to bring the usage under the limit.

This reclaim path happens many times and finally we hit probably a race
get into deadlock

** Affects: linux (Ubuntu)
 Importance: Undecided
 Assignee: Dragan S. (dragan-s)
 Status: Incomplete

** Changed in: linux (Ubuntu)
Milestone: None => xenial-updates

** Changed in: linux (Ubuntu)
 Assignee: (unassigned) => Dragan S. (dragan-s)

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

Title:
  user space process hung in 'D' state waiting for disk io to complete

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Using Ubuntu Xenial user reports processes hang in D state waiting for
  disk io.

  Ocassionally one of the applications gets into "D" state on NFS
  reads/sync and close system calls. based on the kernel backtraces
  seems to be stuck in kmalloc allocation during cleanup of dirty NFS
  pages.

  All the subsequent operations on the NFS mounts are stuck and reboot
  is required to rectify the situation.

  [Test scenario]

  1) Applications running in Docker environment 
  2) Application have cgroup limits --cpu-shares --memory -shm-limit 
  3) python and C++ based applications (torch and caffe) 
  4) Applications read big lmdb files and write results to NFS shares 
  5) use NFS v3 , hard and fscache is enabled 
  6) now swap space is configured 

  This prevents all other I/O activity on that mount to hang.

  we are running into this issue more frequently and identified few
  applications causing this problem.

  As updated in the description, the problem seems to be happening when
  exercising the stack

  try_to_free_mem_cgroup_pages+0xba/0x1a0

  we see this with docker containers with cgroup option --memory
  .

  whenever there is a deadlock, we see that the process that is hung has
  reached the maximum cgroup limit, multiple times and typically cleans
  up dirty data and caches to bring the usage under the limit.

  This reclaim path happens many times and finally we hit probably a
  race get into deadlock

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1750038/+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 1477466] Re: Low performance when using vlan over VxLan

[Dragan S.]

** Changed in: linux (Ubuntu)
 Assignee: (unassigned) => Dragan S. (dragan-s)

** Changed in: linux (Ubuntu Vivid)
 Assignee: (unassigned) => Dragan S. (dragan-s)

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

Title:
  Low performance when using vlan over VxLan

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

Bug description:
  We see a performance issue when running traffic over vlan interface
  that created over VxLAN interface.

  We reach 24 Gbps over the VxLan interface while we reach only 4 Gbps
  over the VLAN interface.  Turned out that GRO isn't supported for VLAN
  over VxLAN.

  The following upstream commits fix this issue.

  commit 66e5133f19e901a044fa5eaeeb6ecff4545839e5
  Author: Toshiaki Makita 
  Date:   Mon Jun 1 21:55:06 2015 +0900

  vlan: Add GRO support for non hardware accelerated vlan

  Currently packets with non-hardware-accelerated vlan cannot be handled
  by GRO. This causes low performance for 802.1ad and stacked vlan, as their
  vlan tags are currently not stripped by hardware.

  This patch adds GRO support for non-hardware-accelerated vlan and
  improves receive performance of them.

  commit 9b174d88c257150562b0101fcc6cb6c3cb74275c
  Author: Jesse Gross 
  Date:   Tue Dec 30 19:10:15 2014 -0800

  net: Add Transparent Ethernet Bridging GRO support.

  Currently the only tunnel protocol that supports GRO with encapsulated
  Ethernet is VXLAN. This pulls out the Ethernet code into a proper layer
  so that it can be used by other tunnel protocols such as GRE and Geneve.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1477466/+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 1477466] Re: Low performance when using vlan over VxLan

[Dragan S.]

Hi Kamal-

what is the status of this issue. Have you had a chance to try the
kernel with back-ported changes?

Thank you

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

Title:
  Low performance when using vlan over VxLan

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

Bug description:
  We see a performance issue when running traffic over vlan interface
  that created over VxLAN interface.

  We reach 24 Gbps over the VxLan interface while we reach only 4 Gbps
  over the VLAN interface.  Turned out that GRO isn't supported for VLAN
  over VxLAN.

  The following upstream commits fix this issue.

  commit 66e5133f19e901a044fa5eaeeb6ecff4545839e5
  Author: Toshiaki Makita 
  Date:   Mon Jun 1 21:55:06 2015 +0900

  vlan: Add GRO support for non hardware accelerated vlan

  Currently packets with non-hardware-accelerated vlan cannot be handled
  by GRO. This causes low performance for 802.1ad and stacked vlan, as their
  vlan tags are currently not stripped by hardware.

  This patch adds GRO support for non-hardware-accelerated vlan and
  improves receive performance of them.

  commit 9b174d88c257150562b0101fcc6cb6c3cb74275c
  Author: Jesse Gross 
  Date:   Tue Dec 30 19:10:15 2014 -0800

  net: Add Transparent Ethernet Bridging GRO support.

  Currently the only tunnel protocol that supports GRO with encapsulated
  Ethernet is VXLAN. This pulls out the Ethernet code into a proper layer
  so that it can be used by other tunnel protocols such as GRE and Geneve.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1477466/+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 1477466] Re: Low performance when using vlan over VxLan

[Dragan S.]

Hi Talat-

The bug was filed against vivid which is no longer maintained. The
original submitter had requested certain patches be back-ported to vivid
because they supposedly fixed an issue.

The requested patches were back-ported and they didn't fix the issue the
submitter purported that they fix.

So I wanted to know two things:
1. Does the reported issue still appear in latest releases such as xenial(16.04)
2. If so does this issue appear in the mainline kernel as well?

This will determine if the reported issue is an Ubuntu specific issue or
if the general mainline linux kernel needs fixing.

If you can re-run the tests on 1 & 2 that would be very helpful, but it
would also help if you could provide the exact configuration and steps
you use so that I can try and reproduce your tests.

Thanks.

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

Title:
  Low performance when using vlan over VxLan

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

Bug description:
  We see a performance issue when running traffic over vlan interface
  that created over VxLAN interface.

  We reach 24 Gbps over the VxLan interface while we reach only 4 Gbps
  over the VLAN interface.  Turned out that GRO isn't supported for VLAN
  over VxLAN.

  The following upstream commits fix this issue.

  commit 66e5133f19e901a044fa5eaeeb6ecff4545839e5
  Author: Toshiaki Makita 
  Date:   Mon Jun 1 21:55:06 2015 +0900

  vlan: Add GRO support for non hardware accelerated vlan

  Currently packets with non-hardware-accelerated vlan cannot be handled
  by GRO. This causes low performance for 802.1ad and stacked vlan, as their
  vlan tags are currently not stripped by hardware.

  This patch adds GRO support for non-hardware-accelerated vlan and
  improves receive performance of them.

  commit 9b174d88c257150562b0101fcc6cb6c3cb74275c
  Author: Jesse Gross 
  Date:   Tue Dec 30 19:10:15 2014 -0800

  net: Add Transparent Ethernet Bridging GRO support.

  Currently the only tunnel protocol that supports GRO with encapsulated
  Ethernet is VXLAN. This pulls out the Ethernet code into a proper layer
  so that it can be used by other tunnel protocols such as GRE and Geneve.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1477466/+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 1477466] Re: Low performance when using vlan over VxLan

[Dragan S.]

Hi Talat-

any update on this issue?

Thanks

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

Title:
  Low performance when using vlan over VxLan

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

Bug description:
  We see a performance issue when running traffic over vlan interface
  that created over VxLAN interface.

  We reach 24 Gbps over the VxLan interface while we reach only 4 Gbps
  over the VLAN interface.  Turned out that GRO isn't supported for VLAN
  over VxLAN.

  The following upstream commits fix this issue.

  commit 66e5133f19e901a044fa5eaeeb6ecff4545839e5
  Author: Toshiaki Makita 
  Date:   Mon Jun 1 21:55:06 2015 +0900

  vlan: Add GRO support for non hardware accelerated vlan

  Currently packets with non-hardware-accelerated vlan cannot be handled
  by GRO. This causes low performance for 802.1ad and stacked vlan, as their
  vlan tags are currently not stripped by hardware.

  This patch adds GRO support for non-hardware-accelerated vlan and
  improves receive performance of them.

  commit 9b174d88c257150562b0101fcc6cb6c3cb74275c
  Author: Jesse Gross 
  Date:   Tue Dec 30 19:10:15 2014 -0800

  net: Add Transparent Ethernet Bridging GRO support.

  Currently the only tunnel protocol that supports GRO with encapsulated
  Ethernet is VXLAN. This pulls out the Ethernet code into a proper layer
  so that it can be used by other tunnel protocols such as GRE and Geneve.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1477466/+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 1651609] Re: Missing hugepages in xenial on 4.4.0-36-generic

[Dragan S.]

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

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

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

Title:
  Missing hugepages in xenial on 4.4.0-36-generic

Status in linux package in Ubuntu:
  New

Bug description:
  When spawning multiple VMs and then shutting then down there are
  hugepages that are unaccounted for, they don't show up in "ipcs -m" or
  on in /dev/hugepages/

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1651609/+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 1625381] Re: Crash on Ubuntu 14.04.5 LTS linux kernel 4.4.0-21-generic #37~14.04.1-Ubuntu

[Dragan S.]

** Changed in: linux (Ubuntu)
 Assignee: Dragan S. (dragan-s) => (unassigned)

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

Title:
  Crash on Ubuntu 14.04.5 LTS linux kernel 4.4.0-21-generic
  #37~14.04.1-Ubuntu

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  On Ubuntu 14.04.5 LTS linux kernel 4.4.0-21-generic #37~14.04.1-Ubuntu
  there is a crash that randomly happens.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1625381/+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 1657281] [NEW] Ubuntu xenial - 4.4.0-59-generic i3 I/O performance issue

[Dragan S.]

Public bug reported:


[Impact]

 * When running block device I/O on an Amazon i3 system there
   is a performance degradation. A patch with git change id
   87c279e613f848c69b29 that is in Ubuntu-lts-4.8.0 kernel
   series increases I/O performance.

 * Fix should be backported to xenial 4.4 series to avoid more
   support issues being filed.

 * This change gets rid of uneccessary work being performed.

[Test Case]

 * Steps to reproduce below
   1) partition ephemeral disks 
  /sbin/parted -s --align optimal /dev/nvme0n1 mklabel gpt mkpart primary 
0% 100% 
  /sbin/parted -s --align optimal /dev/nvme1n1 mklabel gpt mkpart primary 
0% 100% 
  /sbin/parted -s --align optimal /dev/nvme2n1 mklabel gpt mkpart primary 
0% 100% 
  /sbin/parted -s --align optimal /dev/nvme3n1 mklabel gpt mkpart primary 
0% 100% 

   2) create raid array 
  /sbin/mdadm --create /dev/md0 --assume-clean --chunk=2048 --level=10 
--raid-devices=4 /dev/nvme0n1p1 /dev/nvme1n1p1 /dev/nvme2n1p1 /dev/nvme3n1p1 

   3) create pv 
  /sbin/pvcreate --force --metadatasize 4092k /dev/md0 

   4) create volume group 
  /sbin/vgcreate RDSVG /dev/md0 

   5) create lv 
  /sbin/lvcreate -L 2.5T -n RDSRAIDLV RDSVG 

   5) test I/O
  sudo dd if=/dev/zero of=/dev/RDSVG/RDSRAIDLV bs=8k count=100 && sync

[Regression Potential]

 * No known regression potential.

[Original Description]

When we were doing testing on i3, we noticed that it is taking
significantly longer to perform operations when using software RAID than
without, we believe this is resolved in an upstream commit:
http://kernel.ubuntu.com/git/ubuntu/ubuntu-
xenial.git/commit/?id=87c279e613f848c69b29d49de8df3f4f56da

So stock 4.4.0-59-generic performs ok:
$ sudo dd if=/dev/zero of=/dev/RDSVG/RDSRAIDLV bs=8k count=100 && sync 
sudo: unable to resolve host ip-10-0-85-167
100+0 records in
100+0 records out
819200 bytes (8.2 GB, 7.6 GiB) copied, 54.3711 s, 151 MB/s

and the patch you originally providing works a little bit better (as expected):
$ uname -a
Linux ip-10-0-85-167 4.4.0-57-generic 
#78hf00v20170110b0h3199a6e718db-Ubuntu SMP Tue Jan 10 02:53: x86_64 x86_64 
x86_64 GNU/Linux
ubuntu@ip-10-0-85-167:~$ sudo dd if=/dev/zero of=/dev/RDSVG/RDSRAIDLV bs=8k 
count=100 && sync 
sudo: unable to resolve host ip-10-0-85-167
100+0 records in
100+0 records out
819200 bytes (8.2 GB, 7.6 GiB) copied, 31.4108 s, 261 MB/s

** Affects: linux (Ubuntu)
 Importance: Undecided
     Assignee: Dragan S. (dragan-s)
 Status: Incomplete


** Tags: sts

** Patch added: "block: fix plug list flushing for nomerge queues"
   
https://bugs.launchpad.net/bugs/1657281/+attachment/4805506/+files/fix_plug_list_flushing_for_nomerge_queues.patch

** Tags added: sts

** Description changed:

+ 
+ [Impact]
+ 
+  * When running block device I/O on an Amazon i3 system there
+is a performance degradation. A patch with git change id
+87c279e613f848c69b29 that is in Ubuntu-lts-4.8.0 kernel
+series increases I/O performance.
+ 
+  * Fix should be backported to xenial 4.4 series to avoid more
+support issues being filed.
+ 
+  * This change gets rid of uneccessary work being performed.
+ 
+ [Test Case]
+ 
+  * Steps to reproduce below
+1) partition ephemeral disks 
+   /sbin/parted -s --align optimal /dev/nvme0n1 mklabel gpt mkpart primary 
0% 100% 
+   /sbin/parted -s --align optimal /dev/nvme1n1 mklabel gpt mkpart primary 
0% 100% 
+   /sbin/parted -s --align optimal /dev/nvme2n1 mklabel gpt mkpart primary 
0% 100% 
+   /sbin/parted -s --align optimal /dev/nvme3n1 mklabel gpt mkpart primary 
0% 100% 
+ 
+2) create raid array 
+   /sbin/mdadm --create /dev/md0 --assume-clean --chunk=2048 --level=10 
--raid-devices=4 /dev/nvme0n1p1 /dev/nvme1n1p1 /dev/nvme2n1p1 /dev/nvme3n1p1 
+ 
+3) create pv 
+   /sbin/pvcreate --force --metadatasize 4092k /dev/md0 
+ 
+4) create volume group 
+   /sbin/vgcreate RDSVG /dev/md0 
+ 
+5) create lv 
+   /sbin/lvcreate -L 2.5T -n RDSRAIDLV RDSVG 
+ 
+5) test I/O
+   sudo dd if=/dev/zero of=/dev/RDSVG/RDSRAIDLV bs=8k count=100 && sync
+ 
+ [Regression Potential]
+ 
+  * No known regression potential.
+ 
+ [Original Description]
+ 
  When we were doing testing on i3, we noticed that it is taking
  significantly longer to perform operations when using software RAID than
  without, we believe this is resolved in an upstream commit:
  http://kernel.ubuntu.com/git/ubuntu/ubuntu-
  xenial.git/commit/?id=87c279e613f848c69b29d49de8df3f4f56da
  
  So stock 4.4.0-59-generic performs ok:
  $ sudo dd if=/dev/zero of=/dev/RDSVG/RDSRAIDLV bs=8k count=100 && sync 
  sudo: unable to resolve host ip-10-0-85-167
  100+0 records in
  100+0 records out
  819200 bytes (8.2 GB, 7.6 GiB) copied, 54.3711 s, 151 MB/s
  
  and the patch you originally providing works a little 

[Kernel-packages] [Bug 1657281] Re: Ubuntu xenial - 4.4.0-59-generic i3 I/O performance issue

[Dragan S.]

Verified:

4.4.0-59-generic
$ sudo dd if=/dev/zero of=/dev/RDSVG/RDSRAIDLV bs=8k count=100 && sync
100+0 records in
100+0 records out
819200 bytes (8.2 GB, 7.6 GiB) copied, 56.7741 s, 144 MB/s

4.4.0-62-generic
$ sudo dd if=/dev/zero of=/dev/RDSVG/RDSRAIDLV bs=8k count=100 && sync
100+0 records in
100+0 records out
819200 bytes (8.2 GB, 7.6 GiB) copied, 31.3783 s, 261 MB/s


** Tags removed: verification-needed-xenial
** Tags added: verification-done-xenial

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

Title:
  Ubuntu xenial - 4.4.0-59-generic i3 I/O performance issue

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Xenial:
  Fix Committed

Bug description:
  
  [Impact]

   * When running block device I/O on an Amazon i3 system there
 is a performance degradation. A patch with git change id
 87c279e613f848c69b29 that is in Ubuntu-lts-4.8.0 kernel
 series increases I/O performance.

   * Fix should be backported to xenial 4.4 series to avoid more
 support issues being filed.

   * This change gets rid of uneccessary work being performed.

  [Test Case]

   * Steps to reproduce below
 1) partition ephemeral disks 
/sbin/parted -s --align optimal /dev/nvme0n1 mklabel gpt mkpart primary 
0% 100% 
/sbin/parted -s --align optimal /dev/nvme1n1 mklabel gpt mkpart primary 
0% 100% 
/sbin/parted -s --align optimal /dev/nvme2n1 mklabel gpt mkpart primary 
0% 100% 
/sbin/parted -s --align optimal /dev/nvme3n1 mklabel gpt mkpart primary 
0% 100% 

 2) create raid array 
/sbin/mdadm --create /dev/md0 --assume-clean --chunk=2048 --level=10 
--raid-devices=4 /dev/nvme0n1p1 /dev/nvme1n1p1 /dev/nvme2n1p1 /dev/nvme3n1p1 

 3) create pv 
/sbin/pvcreate --force --metadatasize 4092k /dev/md0 

 4) create volume group 
/sbin/vgcreate RDSVG /dev/md0 

 5) create lv 
/sbin/lvcreate -L 2.5T -n RDSRAIDLV RDSVG 

 5) test I/O
sudo dd if=/dev/zero of=/dev/RDSVG/RDSRAIDLV bs=8k count=100 && sync

  [Regression Potential]

   * No known regression potential.

  [Original Description]

  When we were doing testing on i3, we noticed that it is taking
  significantly longer to perform operations when using software RAID
  than without, we believe this is resolved in an upstream commit:
  http://kernel.ubuntu.com/git/ubuntu/ubuntu-
  xenial.git/commit/?id=87c279e613f848c69b29d49de8df3f4f56da

  So stock 4.4.0-59-generic performs ok:
  $ sudo dd if=/dev/zero of=/dev/RDSVG/RDSRAIDLV bs=8k count=100 && sync 
  sudo: unable to resolve host ip-10-0-85-167
  100+0 records in
  100+0 records out
  819200 bytes (8.2 GB, 7.6 GiB) copied, 54.3711 s, 151 MB/s

  and the patch you originally providing works a little bit better (as 
expected):
  $ uname -a
  Linux ip-10-0-85-167 4.4.0-57-generic 
#78hf00v20170110b0h3199a6e718db-Ubuntu SMP Tue Jan 10 02:53: x86_64 x86_64 
x86_64 GNU/Linux
  ubuntu@ip-10-0-85-167:~$ sudo dd if=/dev/zero of=/dev/RDSVG/RDSRAIDLV bs=8k 
count=100 && sync 
  sudo: unable to resolve host ip-10-0-85-167
  100+0 records in
  100+0 records out
  819200 bytes (8.2 GB, 7.6 GiB) copied, 31.4108 s, 261 MB/s

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1657281/+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 1625381] [NEW] Crash on Ubuntu 14.04.5 LTS linux kernel 4.4.0-21-generic #37~14.04.1-Ubuntu

[Dragan S.]

Public bug reported:

On Ubuntu 14.04.5 LTS linux kernel 4.4.0-21-generic #37~14.04.1-Ubuntu
there is a crash that randomly happens.

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

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

Title:
  Crash on Ubuntu 14.04.5 LTS linux kernel 4.4.0-21-generic
  #37~14.04.1-Ubuntu

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  On Ubuntu 14.04.5 LTS linux kernel 4.4.0-21-generic #37~14.04.1-Ubuntu
  there is a crash that randomly happens.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1625381/+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 1625381] Re: Crash on Ubuntu 14.04.5 LTS linux kernel 4.4.0-21-generic #37~14.04.1-Ubuntu

[Dragan S.]

Here is the crash log:

Aug 31 15:35:34 6SZXP72 kernel: [4.320565] general protection fault:  
[#1] SMP 
Aug 31 15:35:34 6SZXP72 kernel: [4.320605] Modules linked in: joydev wacom 
arc4 ip6t_REJECT nf_reject_ipv6 nf_log_ipv6 xt_hl ip6t_rt nf_conntrack_ipv6 
nf_defrag_ipv6 ipt_REJECT nf_reject_ipv4 nf_log_ipv4 nf_log_common xt_LOG 
snd_hda_codec_hdmi iwlmvm i2c_designware_platform xt_limit 
snd_hda_codec_realtek i2c_designware_core snd_hda_codec_generic xt_tcpudp 
mac80211 xt_addrtype snd_soc_skl snd_soc_skl_ipc snd_hda_ext_core 
snd_soc_sst_ipc dell_wmi sparse_keymap snd_soc_sst_dsp nf_conntrack_ipv4 
snd_soc_core nf_defrag_ipv4 xt_conntrack snd_compress ip6table_filter 
ip6_tables ac97_bus nf_conntrack_netbios_ns nf_conntrack_broadcast 
snd_pcm_dmaengine nf_nat_ftp nf_nat dw_dmac_core nf_conntrack_ftp snd_hda_intel 
nf_conntrack iwlwifi intel_rapl iptable_filter x86_pkg_temp_thermal ip_tables 
x_tables intel_powerclamp coretemp snd_hda_codec cfg80211 kvm_intel dell_laptop 
dcdbas snd_hda_core snd_hwdep dell_smm_hwmon rtsx_pci_ms memstick cdc_mbim 
cdc_wdm kvm cdc_ncm usbnet snd_pcm mii irqbypas
 s crct10dif_pclmul crc32_pclmul rfcomm idma64 aesni_intel virt_dma aes_x86_64 
lrw gf128mul bnep glue_helper ablk_helper cryptd snd_seq_midi 
snd_seq_midi_event snd_rawmidi snd_seq snd_seq_device snd_timer input_leds snd 
serio_raw soundcore mei_me btusb btrtl mei shpchp intel_lpss_pci wmi i2c_hid 
hid i915_bpo hci_uart btbcm btqca int3403_thermal soc_button_array btintel 
bluetooth intel_ips video pinctrl_sunrisepoint pinctrl_intel int3402_thermal 
drm_kms_helper nls_iso8859_1 drm tpm_crb int3400_thermal acpi_thermal_rel 
intel_lpss_acpi intel_lpss processor_thermal_device int340x_thermal_zone 
intel_soc_dts_iosf i2c_algo_bit fb_sys_fops syscopyarea sysfillrect sysimgblt 
acpi_pad mac_hid parport_pc ppdev acpi_als kfifo_buf industrialio lp parport 
rtsx_pci_sdmmc ahci rtsx_pci libahci fjes
Aug 31 15:35:34 6SZXP72 kernel: [4.321778] CPU: 2 PID: 900 Comm: sh Not 
tainted 4.4.0-21-generic #37~14.04.1-Ubuntu
Aug 31 15:35:34 6SZXP72 kernel: [4.321821] Hardware name: Dell Inc. 
Latitude 5175/0W1PYK, BIOS 01.00.07 02/24/2016
Aug 31 15:35:34 6SZXP72 kernel: [4.321865] task: 88016c61d880 ti: 
880084b0c000 task.ti: 880084b0c000
Aug 31 15:35:34 6SZXP72 kernel: [4.321908] RIP: 0010:[]  
[] kmem_cache_alloc+0x79/0x200
Aug 31 15:35:34 6SZXP72 kernel: [4.321963] RSP: 0018:880084b0fd90  
EFLAGS: 00010282
Aug 31 15:35:34 6SZXP72 kernel: [4.321995] RAX:  RBX: 
024000c0 RCX: 473a
Aug 31 15:35:34 6SZXP72 kernel: [4.322035] RDX: 4739 RSI: 
024000c0 RDI: 88016d401b00
Aug 31 15:35:34 6SZXP72 kernel: [4.322075] RBP: 880084b0fdc0 R08: 
00019f80 R09: 811bd98d
Aug 31 15:35:34 6SZXP72 kernel: [4.322115] R10: 0007efee6131 R11: 
88016ad39040 R12: 024000c0
Aug 31 15:35:34 6SZXP72 kernel: [4.322156] R13: 00020501 R14: 
88016d401b00 R15: 88016d401b00
Aug 31 15:35:34 6SZXP72 kernel: [4.322197] FS:  7efee6113740() 
GS:88017210() knlGS:
Aug 31 15:35:34 6SZXP72 kernel: [4.322242] CS:  0010 DS:  ES:  CR0: 
80050033
Aug 31 15:35:34 6SZXP72 kernel: [4.322275] CR2: 7efee5c87e00 CR3: 
84d49000 CR4: 003406e0
Aug 31 15:35:34 6SZXP72 kernel: [4.322316] DR0:  DR1: 
 DR2: 
Aug 31 15:35:34 6SZXP72 kernel: [4.322356] DR3:  DR6: 
fffe0ff0 DR7: 0400
Aug 31 15:35:34 6SZXP72 kernel: [4.322396] Stack:
Aug 31 15:35:34 6SZXP72 kernel: [4.322410]  811bd98d 
88007fbcf190 88016c3debb8 88016a3529b0
Aug 31 15:35:34 6SZXP72 kernel: [4.322462]  0001 
8800864fa268 880084b0fdf0 811bd98d
Aug 31 15:35:34 6SZXP72 kernel: [4.322514]  88007f9bda40 
88016c3debb8 88007fbcf190 0001
Aug 31 15:35:34 6SZXP72 kernel: [4.322565] Call Trace:
Aug 31 15:35:34 6SZXP72 kernel: [4.322586]  [] ? 
anon_vma_fork+0x8d/0x130
Aug 31 15:35:34 6SZXP72 kernel: [4.322621]  [] 
anon_vma_fork+0x8d/0x130
Aug 31 15:35:34 6SZXP72 kernel: [4.322655]  [] 
copy_process+0xe36/0x1c60
Aug 31 15:35:34 6SZXP72 kernel: [4.322689]  [] 
_do_fork+0x82/0x310
Aug 31 15:35:34 6SZXP72 kernel: [4.322720]  [] 
SyS_clone+0x19/0x20
Aug 31 15:35:34 6SZXP72 kernel: [4.322752]  [] 
entry_SYSCALL_64_fastpath+0x16/0x75
Aug 31 15:35:34 6SZXP72 kernel: [4.322789] Code: 4c 03 05 13 e9 e2 7e 4d 8b 
28 49 8b 40 10 4d 85 ed 0f 84 43 01 00 00 48 85 c0 0f 84 3a 01 00 00 49 63 46 
20 48 8d 4a 01 4d 8b 06 <49> 8b 5c 05 00 4c 89 e8 65 49 0f c7 08 0f 94 c0 84 c0 
74 b8 49 
Aug 31 15:35:34 6SZXP72 kernel: [4.323049] RIP  [] 
kmem_cache_alloc+0x79/0x200
Aug 31 15:35:34 6SZXP72 kernel: [4.323090]  RSP 
Aug 31 15:35:34 6SZXP72 kernel: [4.323130] ---[ end trace fa17d7c26f4

[Kernel-packages] [Bug 1625381] Re: Crash on Ubuntu 14.04.5 LTS linux kernel 4.4.0-21-generic #37~14.04.1-Ubuntu

[Dragan S.]

** Changed in: linux (Ubuntu)
 Assignee: (unassigned) => Dragan S. (dragan-s)

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

Title:
  Crash on Ubuntu 14.04.5 LTS linux kernel 4.4.0-21-generic
  #37~14.04.1-Ubuntu

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  On Ubuntu 14.04.5 LTS linux kernel 4.4.0-21-generic #37~14.04.1-Ubuntu
  there is a crash that randomly happens.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1625381/+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 1477466] Re: Low performance when using vlan over VxLan

[Dragan S.]

Closing as incomplete since we are missing required information

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

** Changed in: linux (Ubuntu Vivid)
   Status: In Progress => Incomplete

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

Title:
  Low performance when using vlan over VxLan

Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Vivid:
  Incomplete

Bug description:
  We see a performance issue when running traffic over vlan interface
  that created over VxLAN interface.

  We reach 24 Gbps over the VxLan interface while we reach only 4 Gbps
  over the VLAN interface.  Turned out that GRO isn't supported for VLAN
  over VxLAN.

  The following upstream commits fix this issue.

  commit 66e5133f19e901a044fa5eaeeb6ecff4545839e5
  Author: Toshiaki Makita 
  Date:   Mon Jun 1 21:55:06 2015 +0900

  vlan: Add GRO support for non hardware accelerated vlan

  Currently packets with non-hardware-accelerated vlan cannot be handled
  by GRO. This causes low performance for 802.1ad and stacked vlan, as their
  vlan tags are currently not stripped by hardware.

  This patch adds GRO support for non-hardware-accelerated vlan and
  improves receive performance of them.

  commit 9b174d88c257150562b0101fcc6cb6c3cb74275c
  Author: Jesse Gross 
  Date:   Tue Dec 30 19:10:15 2014 -0800

  net: Add Transparent Ethernet Bridging GRO support.

  Currently the only tunnel protocol that supports GRO with encapsulated
  Ethernet is VXLAN. This pulls out the Ethernet code into a proper layer
  so that it can be used by other tunnel protocols such as GRE and Geneve.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1477466/+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 1720228] [NEW] User reports excessive ALUA retry messages

[Dragan S.]

Public bug reported:

User reports excessive ALUA messages on Ubuntu Trusty, kernel Ubuntu-
lts-4.4.0-91.114_14.04.1

Messages appear after a LUN disappears and there are hundreds of them
flooding the log...


[263095.795873] sd 3:0:0:129: alua: rtpg retry
[263095.795874] sd 3:0:0:129: [alua] Sense Key : Illegal Request [current] 
[263095.795876] sd 3:0:0:129: [alua] Add. Sense: Logical unit not supported
[263095.795961] sd 3:0:0:129: alua: rtpg retry
[263095.795962] sd 3:0:0:129: [alua] Sense Key : Illegal Request [current] 
[263095.795964] sd 3:0:0:129: [alua] Add. Sense: Logical unit not supported
[263095.796049] sd 3:0:0:129: alua: rtpg retry
[263095.796052] sd 3:0:0:129: [alua] Sense Key : Illegal Request [current] 
[263095.796054] sd 3:0:0:129: [alua] Add. Sense: Logical unit not supported
[263095.796140] sd 3:0:0:129: alua: rtpg retry
[263095.796142] sd 3:0:0:129: [alua] Sense Key : Illegal Request [current] 
[263095.796143] sd 3:0:0:129: [alua] Add. Sense: Logical unit not supported
[263095.796224] sd 3:0:0:129: alua: rtpg retry
[263095.796226] sd 3:0:0:129: [alua] Sense Key : Illegal Request [current] 
[263095.796227] sd 3:0:0:129: [alua] Add. Sense: Logical unit not supported
[263095.796473] sd 3:0:0:129: alua: rtpg retry
[263095.796475] sd 3:0:0:129: [alua] Sense Key : Illegal Request [current] 
[263095.796476] sd 3:0:0:129: [alua] Add. Sense: Logical unit not supported
[263095.796604] sd 3:0:0:129: alua: rtpg retry
[263095.796606] sd 3:0:0:129: [alua] Sense Key : Illegal Request [current] 
[263095.796607] sd 3:0:0:129: [alua] Add. Sense: Logical unit not supported
[263095.796691] sd 3:0:0:129: alua: rtpg retry
[263095.796693] sd 3:0:0:129: [alua] Sense Key : Illegal Request [current] 
[263095.796694] sd 3:0:0:129: [alua] Add. Sense: Logical unit not supported
[263095.796778] sd 3:0:0:129: alua: rtpg retry
[263095.796780] sd 3:0:0:129: [alua] Sense Key : Illegal Request [current] 
[263095.796781] sd 3:0:0:129: [alua] Add. Sense: Logical unit not supported
[263095.796868] sd 3:0:0:129: alua: rtpg retry
[263095.796869] sd 3:0:0:129: [alua] Sense Key : Illegal Request [current] 
[263095.796871] sd 3:0:0:129: [alua] Add. Sense: Logical unit not supported
[263095.796951] sd 3:0:0:129: alua: rtpg retry
[263095.796953] sd 3:0:0:129: [alua] Sense Key : Illegal Request [current] 
[263095.796954] sd 3:0:0:129: [alua] Add. Sense: Logical unit not supported
[263095.797034] sd 3:0:0:129: alua: rtpg retry
[263095.797035] sd 3:0:0:129: [alua] Sense Key : Illegal Request [current] 
[263095.797037] sd 3:0:0:129: [alua] Add. Sense: Logical unit not supported
[263095.797117] sd 3:0:0:129: alua: rtpg retry
[263095.797119] sd 3:0:0:129: [alua] Sense Key : Illegal Request [current] 
[263095.797120] sd 3:0:0:129: [alua] Add. Sense: Logical unit not supported
[263095.797202] sd 3:0:0:129: alua: rtpg retry
[263095.797203] sd 3:0:0:129: [alua] Sense Key : Illegal Request [current] 
[263095.797205] sd 3:0:0:129: [alua] Add. Sense: Logical unit not supported
[263095.797288] sd 3:0:0:129: alua: rtpg retry
[263095.797289] sd 3:0:0:129: [alua] Sense Key : Illegal Request [current] 
[263095.797290] sd 3:0:0:129: [alua] Add. Sense: Logical unit not supported
[263095.797387] sd 3:0:0:129: alua: rtpg retry
[263095.797388] sd 3:0:0:129: [alua] Sense Key : Illegal Request [current] 
[263095.797390] sd 3:0:0:129: [alua] Add. Sense: Logical unit not supported
[263095.797470] sd 3:0:0:129: alua: rtpg retry
[263095.797471] sd 3:0:0:129: [alua] Sense Key : Illegal Request [current] 
[263095.797472] sd 3:0:0:129: [alua] Add. Sense: Logical unit not supported
[263095.797562] sd 3:0:0:129: alua: rtpg retry
[263095.797563] sd 3:0:0:129: [alua] Sense Key : Illegal Request [current] 
[263095.797564] sd 3:0:0:129: [alua] Add. Sense: Logical unit not supported
[263095.797652] sd 3:0:0:129: alua: rtpg retry
[263095.797653] sd 3:0:0:129: [alua] Sense Key : Illegal Request [current] 
[263095.797654] sd 3:0:0:129: [alua] Add. Sense: Logical unit not supported

** Affects: linux (Ubuntu)
 Importance: Undecided
 Assignee: Dragan S. (dragan-s)
 Status: Incomplete


** Tags: kernel-bug sts trusty

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

Title:
  User reports excessive ALUA retry messages

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  User reports excessive ALUA messages on Ubuntu Trusty, kernel Ubuntu-
  lts-4.4.0-91.114_14.04.1

  Messages appear after a LUN disappears and there are hundreds of them
  flooding the log...

  
  [263095.795873] sd 3:0:0:129: alua: rtpg retry
  [263095.795874] sd 3:0:0:129: [alua] Sense Key : Illegal Request [current] 
  [263095.795876] sd 3:0:0:129: [alua] Add. Sense: Logical unit not supported
  [263095.795961] sd 3:0:0:129: alua: rtpg retry
  [263095.795962] sd 3:0:0:129: [alua] Sense Key : Illegal Request [current] 
  [263095.795964] sd 3:0:0:129: [alua

[Kernel-packages] [Bug 1720228] Re: User reports excessive ALUA retry messages

[Dragan S.]

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

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

Title:
  User reports excessive ALUA retry messages

Status in linux package in Ubuntu:
  In Progress

Bug description:
  User reports excessive ALUA messages on Ubuntu Trusty, kernel Ubuntu-
  lts-4.4.0-91.114_14.04.1

  Messages appear after a LUN disappears and there are hundreds of them
  flooding the log...

  
  [263095.795873] sd 3:0:0:129: alua: rtpg retry
  [263095.795874] sd 3:0:0:129: [alua] Sense Key : Illegal Request [current] 
  [263095.795876] sd 3:0:0:129: [alua] Add. Sense: Logical unit not supported
  [263095.795961] sd 3:0:0:129: alua: rtpg retry
  [263095.795962] sd 3:0:0:129: [alua] Sense Key : Illegal Request [current] 
  [263095.795964] sd 3:0:0:129: [alua] Add. Sense: Logical unit not supported
  [263095.796049] sd 3:0:0:129: alua: rtpg retry
  [263095.796052] sd 3:0:0:129: [alua] Sense Key : Illegal Request [current] 
  [263095.796054] sd 3:0:0:129: [alua] Add. Sense: Logical unit not supported
  [263095.796140] sd 3:0:0:129: alua: rtpg retry
  [263095.796142] sd 3:0:0:129: [alua] Sense Key : Illegal Request [current] 
  [263095.796143] sd 3:0:0:129: [alua] Add. Sense: Logical unit not supported
  [263095.796224] sd 3:0:0:129: alua: rtpg retry
  [263095.796226] sd 3:0:0:129: [alua] Sense Key : Illegal Request [current] 
  [263095.796227] sd 3:0:0:129: [alua] Add. Sense: Logical unit not supported
  [263095.796473] sd 3:0:0:129: alua: rtpg retry
  [263095.796475] sd 3:0:0:129: [alua] Sense Key : Illegal Request [current] 
  [263095.796476] sd 3:0:0:129: [alua] Add. Sense: Logical unit not supported
  [263095.796604] sd 3:0:0:129: alua: rtpg retry
  [263095.796606] sd 3:0:0:129: [alua] Sense Key : Illegal Request [current] 
  [263095.796607] sd 3:0:0:129: [alua] Add. Sense: Logical unit not supported
  [263095.796691] sd 3:0:0:129: alua: rtpg retry
  [263095.796693] sd 3:0:0:129: [alua] Sense Key : Illegal Request [current] 
  [263095.796694] sd 3:0:0:129: [alua] Add. Sense: Logical unit not supported
  [263095.796778] sd 3:0:0:129: alua: rtpg retry
  [263095.796780] sd 3:0:0:129: [alua] Sense Key : Illegal Request [current] 
  [263095.796781] sd 3:0:0:129: [alua] Add. Sense: Logical unit not supported
  [263095.796868] sd 3:0:0:129: alua: rtpg retry
  [263095.796869] sd 3:0:0:129: [alua] Sense Key : Illegal Request [current] 
  [263095.796871] sd 3:0:0:129: [alua] Add. Sense: Logical unit not supported
  [263095.796951] sd 3:0:0:129: alua: rtpg retry
  [263095.796953] sd 3:0:0:129: [alua] Sense Key : Illegal Request [current] 
  [263095.796954] sd 3:0:0:129: [alua] Add. Sense: Logical unit not supported
  [263095.797034] sd 3:0:0:129: alua: rtpg retry
  [263095.797035] sd 3:0:0:129: [alua] Sense Key : Illegal Request [current] 
  [263095.797037] sd 3:0:0:129: [alua] Add. Sense: Logical unit not supported
  [263095.797117] sd 3:0:0:129: alua: rtpg retry
  [263095.797119] sd 3:0:0:129: [alua] Sense Key : Illegal Request [current] 
  [263095.797120] sd 3:0:0:129: [alua] Add. Sense: Logical unit not supported
  [263095.797202] sd 3:0:0:129: alua: rtpg retry
  [263095.797203] sd 3:0:0:129: [alua] Sense Key : Illegal Request [current] 
  [263095.797205] sd 3:0:0:129: [alua] Add. Sense: Logical unit not supported
  [263095.797288] sd 3:0:0:129: alua: rtpg retry
  [263095.797289] sd 3:0:0:129: [alua] Sense Key : Illegal Request [current] 
  [263095.797290] sd 3:0:0:129: [alua] Add. Sense: Logical unit not supported
  [263095.797387] sd 3:0:0:129: alua: rtpg retry
  [263095.797388] sd 3:0:0:129: [alua] Sense Key : Illegal Request [current] 
  [263095.797390] sd 3:0:0:129: [alua] Add. Sense: Logical unit not supported
  [263095.797470] sd 3:0:0:129: alua: rtpg retry
  [263095.797471] sd 3:0:0:129: [alua] Sense Key : Illegal Request [current] 
  [263095.797472] sd 3:0:0:129: [alua] Add. Sense: Logical unit not supported
  [263095.797562] sd 3:0:0:129: alua: rtpg retry
  [263095.797563] sd 3:0:0:129: [alua] Sense Key : Illegal Request [current] 
  [263095.797564] sd 3:0:0:129: [alua] Add. Sense: Logical unit not supported
  [263095.797652] sd 3:0:0:129: alua: rtpg retry
  [263095.797653] sd 3:0:0:129: [alua] Sense Key : Illegal Request [current] 
  [263095.797654] sd 3:0:0:129: [alua] Add. Sense: Logical unit not supported

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1720228/+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 1720228] Re: User reports excessive ALUA retry messages

[Dragan S.]

PPA fix for the issue is at:

https://launchpad.net/~dragan-s/+archive/ubuntu/lp1720228

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

Title:
  User reports excessive ALUA retry messages

Status in linux package in Ubuntu:
  In Progress

Bug description:
  User reports excessive ALUA messages on Ubuntu Trusty, kernel Ubuntu-
  lts-4.4.0-91.114_14.04.1

  Messages appear after a LUN disappears and there are hundreds of them
  flooding the log...

  
  [263095.795873] sd 3:0:0:129: alua: rtpg retry
  [263095.795874] sd 3:0:0:129: [alua] Sense Key : Illegal Request [current] 
  [263095.795876] sd 3:0:0:129: [alua] Add. Sense: Logical unit not supported
  [263095.795961] sd 3:0:0:129: alua: rtpg retry
  [263095.795962] sd 3:0:0:129: [alua] Sense Key : Illegal Request [current] 
  [263095.795964] sd 3:0:0:129: [alua] Add. Sense: Logical unit not supported
  [263095.796049] sd 3:0:0:129: alua: rtpg retry
  [263095.796052] sd 3:0:0:129: [alua] Sense Key : Illegal Request [current] 
  [263095.796054] sd 3:0:0:129: [alua] Add. Sense: Logical unit not supported
  [263095.796140] sd 3:0:0:129: alua: rtpg retry
  [263095.796142] sd 3:0:0:129: [alua] Sense Key : Illegal Request [current] 
  [263095.796143] sd 3:0:0:129: [alua] Add. Sense: Logical unit not supported
  [263095.796224] sd 3:0:0:129: alua: rtpg retry
  [263095.796226] sd 3:0:0:129: [alua] Sense Key : Illegal Request [current] 
  [263095.796227] sd 3:0:0:129: [alua] Add. Sense: Logical unit not supported
  [263095.796473] sd 3:0:0:129: alua: rtpg retry
  [263095.796475] sd 3:0:0:129: [alua] Sense Key : Illegal Request [current] 
  [263095.796476] sd 3:0:0:129: [alua] Add. Sense: Logical unit not supported
  [263095.796604] sd 3:0:0:129: alua: rtpg retry
  [263095.796606] sd 3:0:0:129: [alua] Sense Key : Illegal Request [current] 
  [263095.796607] sd 3:0:0:129: [alua] Add. Sense: Logical unit not supported
  [263095.796691] sd 3:0:0:129: alua: rtpg retry
  [263095.796693] sd 3:0:0:129: [alua] Sense Key : Illegal Request [current] 
  [263095.796694] sd 3:0:0:129: [alua] Add. Sense: Logical unit not supported
  [263095.796778] sd 3:0:0:129: alua: rtpg retry
  [263095.796780] sd 3:0:0:129: [alua] Sense Key : Illegal Request [current] 
  [263095.796781] sd 3:0:0:129: [alua] Add. Sense: Logical unit not supported
  [263095.796868] sd 3:0:0:129: alua: rtpg retry
  [263095.796869] sd 3:0:0:129: [alua] Sense Key : Illegal Request [current] 
  [263095.796871] sd 3:0:0:129: [alua] Add. Sense: Logical unit not supported
  [263095.796951] sd 3:0:0:129: alua: rtpg retry
  [263095.796953] sd 3:0:0:129: [alua] Sense Key : Illegal Request [current] 
  [263095.796954] sd 3:0:0:129: [alua] Add. Sense: Logical unit not supported
  [263095.797034] sd 3:0:0:129: alua: rtpg retry
  [263095.797035] sd 3:0:0:129: [alua] Sense Key : Illegal Request [current] 
  [263095.797037] sd 3:0:0:129: [alua] Add. Sense: Logical unit not supported
  [263095.797117] sd 3:0:0:129: alua: rtpg retry
  [263095.797119] sd 3:0:0:129: [alua] Sense Key : Illegal Request [current] 
  [263095.797120] sd 3:0:0:129: [alua] Add. Sense: Logical unit not supported
  [263095.797202] sd 3:0:0:129: alua: rtpg retry
  [263095.797203] sd 3:0:0:129: [alua] Sense Key : Illegal Request [current] 
  [263095.797205] sd 3:0:0:129: [alua] Add. Sense: Logical unit not supported
  [263095.797288] sd 3:0:0:129: alua: rtpg retry
  [263095.797289] sd 3:0:0:129: [alua] Sense Key : Illegal Request [current] 
  [263095.797290] sd 3:0:0:129: [alua] Add. Sense: Logical unit not supported
  [263095.797387] sd 3:0:0:129: alua: rtpg retry
  [263095.797388] sd 3:0:0:129: [alua] Sense Key : Illegal Request [current] 
  [263095.797390] sd 3:0:0:129: [alua] Add. Sense: Logical unit not supported
  [263095.797470] sd 3:0:0:129: alua: rtpg retry
  [263095.797471] sd 3:0:0:129: [alua] Sense Key : Illegal Request [current] 
  [263095.797472] sd 3:0:0:129: [alua] Add. Sense: Logical unit not supported
  [263095.797562] sd 3:0:0:129: alua: rtpg retry
  [263095.797563] sd 3:0:0:129: [alua] Sense Key : Illegal Request [current] 
  [263095.797564] sd 3:0:0:129: [alua] Add. Sense: Logical unit not supported
  [263095.797652] sd 3:0:0:129: alua: rtpg retry
  [263095.797653] sd 3:0:0:129: [alua] Sense Key : Illegal Request [current] 
  [263095.797654] sd 3:0:0:129: [alua] Add. Sense: Logical unit not supported

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1720228/+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 1720228] Re: User reports excessive ALUA retry messages

[Dragan S.]

** Description changed:

- User reports excessive ALUA messages on Ubuntu Trusty, kernel Ubuntu-
- lts-4.4.0-91.114_14.04.1
+  SRU Justification:
+ 
+ Impact:
+ User reports excessive ALUA messages on Ubuntu Trusty, kernel 
Ubuntu-lts-4.4.0-91.114_14.04.1. Messages appear after a LUN disappears and 
there are hundreds of them flooding the log...
+ 
+ [263095.795873] sd 3:0:0:129: alua: rtpg retry
+ [263095.795874] sd 3:0:0:129: [alua] Sense Key : Illegal Request [current]
+ [263095.795876] sd 3:0:0:129: [alua] Add. Sense: Logical unit not supported
+ 
+ This causes an intense requeing of the ALUA work queue for 60 seconds
+ and it floods the kernel log
+ 
+ Fix:
+ The err value was initialized to 0 to prevent random assignment the fix is a 
cherry-pick from linus' tree a4bd85203190990ad808abbd4a5dc848a950002c
+ 
+ Testcase:
+ User reports issue when a network iscsi disk gets disconnected.
+ 
+ 
+ Original Bug Text:
+ 
+ 
+ User reports excessive ALUA messages on Ubuntu Trusty, kernel 
Ubuntu-lts-4.4.0-91.114_14.04.1
  
  Messages appear after a LUN disappears and there are hundreds of them
  flooding the log...
  
- 
  [263095.795873] sd 3:0:0:129: alua: rtpg retry
- [263095.795874] sd 3:0:0:129: [alua] Sense Key : Illegal Request [current] 
+ [263095.795874] sd 3:0:0:129: [alua] Sense Key : Illegal Request [current]
  [263095.795876] sd 3:0:0:129: [alua] Add. Sense: Logical unit not supported
  [263095.795961] sd 3:0:0:129: alua: rtpg retry
- [263095.795962] sd 3:0:0:129: [alua] Sense Key : Illegal Request [current] 
+ [263095.795962] sd 3:0:0:129: [alua] Sense Key : Illegal Request [current]
  [263095.795964] sd 3:0:0:129: [alua] Add. Sense: Logical unit not supported
  [263095.796049] sd 3:0:0:129: alua: rtpg retry
- [263095.796052] sd 3:0:0:129: [alua] Sense Key : Illegal Request [current] 
+ [263095.796052] sd 3:0:0:129: [alua] Sense Key : Illegal Request [current]
  [263095.796054] sd 3:0:0:129: [alua] Add. Sense: Logical unit not supported
  [263095.796140] sd 3:0:0:129: alua: rtpg retry
- [263095.796142] sd 3:0:0:129: [alua] Sense Key : Illegal Request [current] 
+ [263095.796142] sd 3:0:0:129: [alua] Sense Key : Illegal Request [current]
  [263095.796143] sd 3:0:0:129: [alua] Add. Sense: Logical unit not supported
  [263095.796224] sd 3:0:0:129: alua: rtpg retry
- [263095.796226] sd 3:0:0:129: [alua] Sense Key : Illegal Request [current] 
+ [263095.796226] sd 3:0:0:129: [alua] Sense Key : Illegal Request [current]
  [263095.796227] sd 3:0:0:129: [alua] Add. Sense: Logical unit not supported
  [263095.796473] sd 3:0:0:129: alua: rtpg retry
- [263095.796475] sd 3:0:0:129: [alua] Sense Key : Illegal Request [current] 
+ [263095.796475] sd 3:0:0:129: [alua] Sense Key : Illegal Request [current]
  [263095.796476] sd 3:0:0:129: [alua] Add. Sense: Logical unit not supported
  [263095.796604] sd 3:0:0:129: alua: rtpg retry
- [263095.796606] sd 3:0:0:129: [alua] Sense Key : Illegal Request [current] 
+ [263095.796606] sd 3:0:0:129: [alua] Sense Key : Illegal Request [current]
  [263095.796607] sd 3:0:0:129: [alua] Add. Sense: Logical unit not supported
  [263095.796691] sd 3:0:0:129: alua: rtpg retry
- [263095.796693] sd 3:0:0:129: [alua] Sense Key : Illegal Request [current] 
+ [263095.796693] sd 3:0:0:129: [alua] Sense Key : Illegal Request [current]
  [263095.796694] sd 3:0:0:129: [alua] Add. Sense: Logical unit not supported
  [263095.796778] sd 3:0:0:129: alua: rtpg retry
- [263095.796780] sd 3:0:0:129: [alua] Sense Key : Illegal Request [current] 
+ [263095.796780] sd 3:0:0:129: [alua] Sense Key : Illegal Request [current]
  [263095.796781] sd 3:0:0:129: [alua] Add. Sense: Logical unit not supported
  [263095.796868] sd 3:0:0:129: alua: rtpg retry
- [263095.796869] sd 3:0:0:129: [alua] Sense Key : Illegal Request [current] 
+ [263095.796869] sd 3:0:0:129: [alua] Sense Key : Illegal Request [current]
  [263095.796871] sd 3:0:0:129: [alua] Add. Sense: Logical unit not supported
  [263095.796951] sd 3:0:0:129: alua: rtpg retry
- [263095.796953] sd 3:0:0:129: [alua] Sense Key : Illegal Request [current] 
+ [263095.796953] sd 3:0:0:129: [alua] Sense Key : Illegal Request [current]
  [263095.796954] sd 3:0:0:129: [alua] Add. Sense: Logical unit not supported
  [263095.797034] sd 3:0:0:129: alua: rtpg retry
- [263095.797035] sd 3:0:0:129: [alua] Sense Key : Illegal Request [current] 
+ [263095.797035] sd 3:0:0:129: [alua] Sense Key : Illegal Request [current]
  [263095.797037] sd 3:0:0:129: [alua] Add. Sense: Logical unit not supported
  [263095.797117] sd 3:0:0:129: alua: rtpg retry
- [263095.797119] sd 3:0:0:129: [alua] Sense Key : Illegal Request [current] 
+ [263095.797119] sd 3:0:0:129: [alua] Sense Key : Illegal Request [current]
  [263095.797120] sd 3:0:0:129: [alua] Add. Sense: Logical unit not supported
  [263095.797202] sd 3:0:0:129: alua: rtpg retry
- [263095.797203] sd 3:0:0:129: [alua] Sense Key : Illegal Request [current] 
+ [263095.797203] sd 3:0:0:129: [alua] Sense Key : Illegal 

[Kernel-packages] [Bug 1720228] Re: User reports excessive ALUA retry messages

[Dragan S.]

** Description changed:

   SRU Justification:
  
  Impact:
- User reports excessive ALUA messages on Ubuntu Trusty, kernel 
Ubuntu-lts-4.4.0-91.114_14.04.1. Messages appear after a LUN disappears and 
there are hundreds of them flooding the log...
+ User reports excessive ALUA messages on Ubuntu Trusty, kernel 
Ubuntu-lts-4.4.0-91.114_14.04.1
+ Messages appear after a LUN disappears and there are hundreds of them 
flooding the log...
  
  [263095.795873] sd 3:0:0:129: alua: rtpg retry
  [263095.795874] sd 3:0:0:129: [alua] Sense Key : Illegal Request [current]
  [263095.795876] sd 3:0:0:129: [alua] Add. Sense: Logical unit not supported
  
  This causes an intense requeing of the ALUA work queue for 60 seconds
  and it floods the kernel log
  
+ 
  Fix:
- The err value was initialized to 0 to prevent random assignment the fix is a 
cherry-pick from linus' tree a4bd85203190990ad808abbd4a5dc848a950002c
+ UBUNTU: scsi: fixe excessive ALUA (LP: #1720228)
+ 
+ BugLink: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1720228
+ 
+ The err value was initialized to 0 to prevent random assignemtn
+ the fix is a cherry-pick from linus tree 
a4bd85203190990ad808abbd4a5dc848a950002c
+ 
  
  Testcase:
  User reports issue when a network iscsi disk gets disconnected.
  
  
- Original Bug Text:
+ Original Bug Text:
  
- 
- User reports excessive ALUA messages on Ubuntu Trusty, kernel 
Ubuntu-lts-4.4.0-91.114_14.04.1
+ User reports excessive ALUA messages on Ubuntu Trusty, kernel Ubuntu-
+ lts-4.4.0-91.114_14.04.1
  
  Messages appear after a LUN disappears and there are hundreds of them
  flooding the log...
  
  [263095.795873] sd 3:0:0:129: alua: rtpg retry
  [263095.795874] sd 3:0:0:129: [alua] Sense Key : Illegal Request [current]
  [263095.795876] sd 3:0:0:129: [alua] Add. Sense: Logical unit not supported
  [263095.795961] sd 3:0:0:129: alua: rtpg retry
  [263095.795962] sd 3:0:0:129: [alua] Sense Key : Illegal Request [current]
  [263095.795964] sd 3:0:0:129: [alua] Add. Sense: Logical unit not supported
  [263095.796049] sd 3:0:0:129: alua: rtpg retry
  [263095.796052] sd 3:0:0:129: [alua] Sense Key : Illegal Request [current]
  [263095.796054] sd 3:0:0:129: [alua] Add. Sense: Logical unit not supported
  [263095.796140] sd 3:0:0:129: alua: rtpg retry
  [263095.796142] sd 3:0:0:129: [alua] Sense Key : Illegal Request [current]
  [263095.796143] sd 3:0:0:129: [alua] Add. Sense: Logical unit not supported
  [263095.796224] sd 3:0:0:129: alua: rtpg retry
  [263095.796226] sd 3:0:0:129: [alua] Sense Key : Illegal Request [current]
  [263095.796227] sd 3:0:0:129: [alua] Add. Sense: Logical unit not supported
  [263095.796473] sd 3:0:0:129: alua: rtpg retry
  [263095.796475] sd 3:0:0:129: [alua] Sense Key : Illegal Request [current]
  [263095.796476] sd 3:0:0:129: [alua] Add. Sense: Logical unit not supported
  [263095.796604] sd 3:0:0:129: alua: rtpg retry
  [263095.796606] sd 3:0:0:129: [alua] Sense Key : Illegal Request [current]
  [263095.796607] sd 3:0:0:129: [alua] Add. Sense: Logical unit not supported
  [263095.796691] sd 3:0:0:129: alua: rtpg retry
  [263095.796693] sd 3:0:0:129: [alua] Sense Key : Illegal Request [current]
  [263095.796694] sd 3:0:0:129: [alua] Add. Sense: Logical unit not supported
  [263095.796778] sd 3:0:0:129: alua: rtpg retry
  [263095.796780] sd 3:0:0:129: [alua] Sense Key : Illegal Request [current]
  [263095.796781] sd 3:0:0:129: [alua] Add. Sense: Logical unit not supported
  [263095.796868] sd 3:0:0:129: alua: rtpg retry
  [263095.796869] sd 3:0:0:129: [alua] Sense Key : Illegal Request [current]
  [263095.796871] sd 3:0:0:129: [alua] Add. Sense: Logical unit not supported
  [263095.796951] sd 3:0:0:129: alua: rtpg retry
  [263095.796953] sd 3:0:0:129: [alua] Sense Key : Illegal Request [current]
  [263095.796954] sd 3:0:0:129: [alua] Add. Sense: Logical unit not supported
  [263095.797034] sd 3:0:0:129: alua: rtpg retry
  [263095.797035] sd 3:0:0:129: [alua] Sense Key : Illegal Request [current]
  [263095.797037] sd 3:0:0:129: [alua] Add. Sense: Logical unit not supported
  [263095.797117] sd 3:0:0:129: alua: rtpg retry
  [263095.797119] sd 3:0:0:129: [alua] Sense Key : Illegal Request [current]
  [263095.797120] sd 3:0:0:129: [alua] Add. Sense: Logical unit not supported
  [263095.797202] sd 3:0:0:129: alua: rtpg retry
  [263095.797203] sd 3:0:0:129: [alua] Sense Key : Illegal Request [current]
  [263095.797205] sd 3:0:0:129: [alua] Add. Sense: Logical unit not supported
  [263095.797288] sd 3:0:0:129: alua: rtpg retry
  [263095.797289] sd 3:0:0:129: [alua] Sense Key : Illegal Request [current]
  [263095.797290] sd 3:0:0:129: [alua] Add. Sense: Logical unit not supported
  [263095.797387] sd 3:0:0:129: alua: rtpg retry
  [263095.797388] sd 3:0:0:129: [alua] Sense Key : Illegal Request [current]
  [263095.797390] sd 3:0:0:129: [alua] Add. Sense: Logical unit not supported
  [263095.797470] sd 3:0:0:129: alua: rtpg retry
  [263095.797471] sd 3:0:0:129: [alua

[Kernel-packages] [Bug 1587475] Re: Kernel panic on btrfs mount and ls

[Dragan S.]

** Changed in: linux (Ubuntu Xenial)
 Assignee: (unassigned) => Dragan S. (dragan-s)

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

Title:
  Kernel panic on btrfs mount and ls

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

Bug description:
  Kernel panic happens after mount and ls specific btrfs image

  Way to reproduce:
  1. download and unpack btrfs image from tar(sparse file)(tar -Sxf img.tar)
  2. mount btrfs (sudo mount -t btrfs -o rw,noatime,compress=no,commit=5 
71bb49cf-26f1-484a-832c-e966f43adca9.img broken)
  3. list files in mount point (ls -al broken)

  the system down to kernel panic with log above

  (looks like 3.19.x and 4.2.x not affected, only 4.4.x)

  dmesg log:
  May 31 13:02:21 fs-new kernel: [  694.744630] BTRFS error (device loop0): 
parent transid verify failed on 30425088 wanted 120 found 119
  May 31 13:02:21 fs-new kernel: [  694.747077] BTRFS error (device loop0): 
parent transid verify failed on 30425088 wanted 120 found 119
  May 31 13:02:21 fs-new kernel: [  694.747128] [ cut here 
]
  May 31 13:02:21 fs-new kernel: [  694.747135] WARNING: CPU: 0 PID: 13795 at 
/build/linux-lts-xenial-7RlTta/linux-lts-xenial-4.4.0/lib/idr.c:1051 
ida_remove+0xfa/0x130()
  May 31 13:02:21 fs-new kernel: [  694.747136] ida_remove called for id=47 
which is not allocated.
  May 31 13:02:21 fs-new kernel: [  694.747137] Modules linked in: ufs qnx4 
hfsplus hfs minix ntfs msdos jfs xfs libcrc32c nfsv3 vboxsf xt_CHECKSUM 
iptable_mangle ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat 
nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack zram 
lz4_compress xt_tcpudp bridge stp llc iptable_filter ip_tables x_tables autofs4 
ppdev vboxvideo ttm crct10dif_pclmul crc32_pclmul drm_kms_helper drm 
aesni_intel aes_x86_64 lrw input_leds gf128mul nfsd glue_helper ablk_helper 
cryptd auth_rpcgss serio_raw nfs_acl nfs fb_sys_fops syscopyarea lockd 
sysfillrect grace 8250_fintek parport_pc sysimgblt vboxguest i2c_piix4 sunrpc 
video mac_hid fscache lp parport zfs(POE) zunicode(POE) zcommon(POE) 
znvpair(POE) spl(OE) zavl(POE) btrfs xor raid6_pq psmouse e1000 fjes pata_acpi
  May 31 13:02:21 fs-new kernel: [  694.747182] CPU: 0 PID: 13795 Comm: ls 
Tainted: P   OE   4.4.0-22-generic #40~14.04.1-Ubuntu
  May 31 13:02:21 fs-new kernel: [  694.747183] Hardware name: innotek GmbH 
VirtualBox/VirtualBox, BIOS VirtualBox 12/01/2006
  May 31 13:02:21 fs-new kernel: [  694.747185]   
8800024e7a88 813cde6c 8800024e7ad0
  May 31 13:02:21 fs-new kernel: [  694.747187]  81af5298 
8800024e7ac0 8107d856 
  May 31 13:02:21 fs-new kernel: [  694.747189]  81fce200 
88003c827a00 88003616e068 0001
  May 31 13:02:21 fs-new kernel: [  694.747191] Call Trace:
  May 31 13:02:21 fs-new kernel: [  694.747195]  [] 
dump_stack+0x63/0x87
  May 31 13:02:21 fs-new kernel: [  694.747199]  [] 
warn_slowpath_common+0x86/0xc0
  May 31 13:02:21 fs-new kernel: [  694.747201]  [] 
warn_slowpath_fmt+0x4c/0x50
  May 31 13:02:21 fs-new kernel: [  694.747214]  [] ? 
free_percpu+0xba/0x180
  May 31 13:02:21 fs-new kernel: [  694.747217]  [] 
ida_remove+0xfa/0x130
  May 31 13:02:21 fs-new kernel: [  694.747220]  [] 
free_anon_bdev+0x2c/0x50
  May 31 13:02:21 fs-new kernel: [  694.747239]  [] 
free_fs_root+0xbe/0xe0 [btrfs]
  May 31 13:02:21 fs-new kernel: [  694.747251]  [] 
btrfs_get_fs_root+0x216/0x250 [btrfs]
  May 31 13:02:21 fs-new kernel: [  694.747264]  [] ? 
memcmp_extent_buffer+0xbd/0x120 [btrfs]
  May 31 13:02:21 fs-new kernel: [  694.747277]  [] 
btrfs_lookup_dentry+0x28c/0x4c0 [btrfs]
  May 31 13:02:21 fs-new kernel: [  694.747288]  [] 
btrfs_lookup+0x12/0x40 [btrfs]
  May 31 13:02:21 fs-new kernel: [  694.747291]  [] 
lookup_real+0x1d/0x50
  May 31 13:02:21 fs-new kernel: [  694.747293]  [] 
__lookup_hash+0x33/0x40
  May 31 13:02:21 fs-new kernel: [  694.747295]  [] 
walk_component+0x177/0x280
  May 31 13:02:21 fs-new kernel: [  694.747297]  [] ? 
posix_acl_xattr_get+0x49/0xb0
  May 31 13:02:21 fs-new kernel: [  694.747299]  [] 
path_lookupat+0x60/0x110
  May 31 13:02:21 fs-new kernel: [  694.747301]  [] 
filename_lookup+0x9c/0x150
  May 31 13:02:21 fs-new kernel: [  694.747304]  [] ? 
kmem_cache_alloc+0x19f/0x200
  May 31 13:02:21 fs-new kernel: [  694.747306]  [] ? 
getname_flags+0x4f/0x1f0
  May 31 13:02:21 fs-new kernel: [  694.747308]  [] 
user_path_at_empty+0x36/0x40
  May 31 13:02:21 fs-new kernel: [  694.747310]  [] 
vfs_fstatat+0x53/0xa0
  May 31 13:02:21 fs-new kernel: [  694.747312]  [] 
SYSC_newlstat+0x22/0x40
  May 31 13:02:21 fs-new kernel: [  694.747315]  [] ? 
mntput+0x24/0x40
  May 31 13:02:21 fs-new kernel: [  694.747317]  [] ? 
path_put+0x1e/0x30
  May 31 13:02:21 fs-new kernel: [  694.747

[Kernel-packages] [Bug 1587475] Re: Kernel panic on btrfs mount and ls

[Dragan S.]

I can reproduce this problem and I have pinpointed the problem. Working
on creating a patch and a test build.

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

Title:
  Kernel panic on btrfs mount and ls

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

Bug description:
  Kernel panic happens after mount and ls specific btrfs image

  Way to reproduce:
  1. download and unpack btrfs image from tar(sparse file)(tar -Sxf img.tar)
  2. mount btrfs (sudo mount -t btrfs -o rw,noatime,compress=no,commit=5 
71bb49cf-26f1-484a-832c-e966f43adca9.img broken)
  3. list files in mount point (ls -al broken)

  the system down to kernel panic with log above

  (looks like 3.19.x and 4.2.x not affected, only 4.4.x)

  dmesg log:
  May 31 13:02:21 fs-new kernel: [  694.744630] BTRFS error (device loop0): 
parent transid verify failed on 30425088 wanted 120 found 119
  May 31 13:02:21 fs-new kernel: [  694.747077] BTRFS error (device loop0): 
parent transid verify failed on 30425088 wanted 120 found 119
  May 31 13:02:21 fs-new kernel: [  694.747128] [ cut here 
]
  May 31 13:02:21 fs-new kernel: [  694.747135] WARNING: CPU: 0 PID: 13795 at 
/build/linux-lts-xenial-7RlTta/linux-lts-xenial-4.4.0/lib/idr.c:1051 
ida_remove+0xfa/0x130()
  May 31 13:02:21 fs-new kernel: [  694.747136] ida_remove called for id=47 
which is not allocated.
  May 31 13:02:21 fs-new kernel: [  694.747137] Modules linked in: ufs qnx4 
hfsplus hfs minix ntfs msdos jfs xfs libcrc32c nfsv3 vboxsf xt_CHECKSUM 
iptable_mangle ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat 
nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack zram 
lz4_compress xt_tcpudp bridge stp llc iptable_filter ip_tables x_tables autofs4 
ppdev vboxvideo ttm crct10dif_pclmul crc32_pclmul drm_kms_helper drm 
aesni_intel aes_x86_64 lrw input_leds gf128mul nfsd glue_helper ablk_helper 
cryptd auth_rpcgss serio_raw nfs_acl nfs fb_sys_fops syscopyarea lockd 
sysfillrect grace 8250_fintek parport_pc sysimgblt vboxguest i2c_piix4 sunrpc 
video mac_hid fscache lp parport zfs(POE) zunicode(POE) zcommon(POE) 
znvpair(POE) spl(OE) zavl(POE) btrfs xor raid6_pq psmouse e1000 fjes pata_acpi
  May 31 13:02:21 fs-new kernel: [  694.747182] CPU: 0 PID: 13795 Comm: ls 
Tainted: P   OE   4.4.0-22-generic #40~14.04.1-Ubuntu
  May 31 13:02:21 fs-new kernel: [  694.747183] Hardware name: innotek GmbH 
VirtualBox/VirtualBox, BIOS VirtualBox 12/01/2006
  May 31 13:02:21 fs-new kernel: [  694.747185]   
8800024e7a88 813cde6c 8800024e7ad0
  May 31 13:02:21 fs-new kernel: [  694.747187]  81af5298 
8800024e7ac0 8107d856 
  May 31 13:02:21 fs-new kernel: [  694.747189]  81fce200 
88003c827a00 88003616e068 0001
  May 31 13:02:21 fs-new kernel: [  694.747191] Call Trace:
  May 31 13:02:21 fs-new kernel: [  694.747195]  [] 
dump_stack+0x63/0x87
  May 31 13:02:21 fs-new kernel: [  694.747199]  [] 
warn_slowpath_common+0x86/0xc0
  May 31 13:02:21 fs-new kernel: [  694.747201]  [] 
warn_slowpath_fmt+0x4c/0x50
  May 31 13:02:21 fs-new kernel: [  694.747214]  [] ? 
free_percpu+0xba/0x180
  May 31 13:02:21 fs-new kernel: [  694.747217]  [] 
ida_remove+0xfa/0x130
  May 31 13:02:21 fs-new kernel: [  694.747220]  [] 
free_anon_bdev+0x2c/0x50
  May 31 13:02:21 fs-new kernel: [  694.747239]  [] 
free_fs_root+0xbe/0xe0 [btrfs]
  May 31 13:02:21 fs-new kernel: [  694.747251]  [] 
btrfs_get_fs_root+0x216/0x250 [btrfs]
  May 31 13:02:21 fs-new kernel: [  694.747264]  [] ? 
memcmp_extent_buffer+0xbd/0x120 [btrfs]
  May 31 13:02:21 fs-new kernel: [  694.747277]  [] 
btrfs_lookup_dentry+0x28c/0x4c0 [btrfs]
  May 31 13:02:21 fs-new kernel: [  694.747288]  [] 
btrfs_lookup+0x12/0x40 [btrfs]
  May 31 13:02:21 fs-new kernel: [  694.747291]  [] 
lookup_real+0x1d/0x50
  May 31 13:02:21 fs-new kernel: [  694.747293]  [] 
__lookup_hash+0x33/0x40
  May 31 13:02:21 fs-new kernel: [  694.747295]  [] 
walk_component+0x177/0x280
  May 31 13:02:21 fs-new kernel: [  694.747297]  [] ? 
posix_acl_xattr_get+0x49/0xb0
  May 31 13:02:21 fs-new kernel: [  694.747299]  [] 
path_lookupat+0x60/0x110
  May 31 13:02:21 fs-new kernel: [  694.747301]  [] 
filename_lookup+0x9c/0x150
  May 31 13:02:21 fs-new kernel: [  694.747304]  [] ? 
kmem_cache_alloc+0x19f/0x200
  May 31 13:02:21 fs-new kernel: [  694.747306]  [] ? 
getname_flags+0x4f/0x1f0
  May 31 13:02:21 fs-new kernel: [  694.747308]  [] 
user_path_at_empty+0x36/0x40
  May 31 13:02:21 fs-new kernel: [  694.747310]  [] 
vfs_fstatat+0x53/0xa0
  May 31 13:02:21 fs-new kernel: [  694.747312]  [] 
SYSC_newlstat+0x22/0x40
  May 31 13:02:21 fs-new kernel: [  694.747315]  [] ? 
mntput+0x24/0x40
  May 31 13:02:21 fs-new kernel: [  694.747317]  [] ? 
path_put+0x1e/0x30
  May 31 13:02:21 fs-new kernel: [  69