[Kernel-packages] [Bug 1713765] Re: Consider "s390/mm: avoid empty zero pages for KVM guests to avoid postcopy hangs" for Artful

[bugproxy]

** Tags added: architecture-s39064 bugnameltc-158134 severity-high
targetmilestone-inin1604

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

Title:
  Consider "s390/mm: avoid empty zero pages for KVM guests to avoid
  postcopy hangs" for Artful

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hi,
  there is this patch in discussion [1].

  If I read correctly between the lines that is supposed to go to -stable trees 
as well as to linxu-s390x next (4.14) submissions.
  But the change is rather big and we have to consider taking that early or as 
SRU or not at all.

  I wanted to ask the kernel Team to keep an eye on that discussion and take 
the patch into consideration - IMHO it might change KVM behavior on s390 quite 
a bit.
  So I'm not sure how SRUable it is while on Artful we migth add it rather soon 
before release.

  To some extend we should wait for the discussion on the upstreaming,
  but then I wanted to make you aware asap.

  [1]: https://lists.gnu.org/archive/html/qemu-
  devel/2017-08/msg05286.html

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1713765/+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 1713940] [NEW] kexec-tools 2.0.14 fails to load 4.12+ crash kernels

[Stefan Bader]

Public bug reported:

Starting with 4.12 kernels, kexec-tools cannot load a crash kernel
because ELF core parsing fails with errors like:

  Unknown type (Reserved) while parsing /sys/firmware/memmap/5/type.
  Please report this as bug. Using RANGE_RESERVED now.
  ...
  ELF core (kcore) parse failed
  Cannot load /var/lib/kdump/vmlinuz

The issue is fixed upstream in kexec-tools 2.0.15 (Debian is still at
2.0.14)

The complete changes list between 2.0.14 and 2.0.15 shows mostly bug
fixes and in fact all additional patches in debian/patches which are
Ubuntu delta, have moved into upstream 2.0.15. So we could drop all
those while moving to the new version.

* ppc64: Reduce number of ELF LOAD segments
* kexec: Increase the upper limit for RAM segments
* alpha: add missing __NR_kexec_load definition
* kexec: implemented XEN KEXEC STATUS to determine if an image is loaded
* kexec: Remove redundant space from help message
* purgatory: Add purgatory.map and purgatory.ro.sym to clean recipe
* kexec: Add option to get crash kernel region size
* crashdump/arm: Add get_crash_kernel_load_range() function
* crashdump/arm64: Add get_crash_kernel_load_range() function
* crashdump/cris: Add get_crash_kernel_load_range() function
* crashdump/ia64: Add get_crash_kernel_load_range() function
* crashdump/m68k: Add get_crash_kernel_load_range() function
* crashdump/mips: Add get_crash_kernel_load_range() function
* crashdump/ppc: Add get_crash_kernel_load_range() function
* crashdump/ppc64: Add get_crash_kernel_load_range() function
* crashdump/s390: Add get_crash_kernel_load_range() function
* crashdump/sh: Add get_crash_kernel_load_range() function
* gitignore: add two generated files in purgatory
* Only print debug message when failed to serach for kernel symbol from
  /proc/kallsyms
* build_mem_phdrs(): check if p_paddr is invalid
* uImage: fix realloc() pointer confusion
* uImage: Fix uImage_load() for little-endian machines
* uImage: Add new IH_ARCH_xxx definitions
* uImage: use 'char *' instead of 'unsigned char *' for uImage_load()
* uImage: use 'char *' instead of 'unsigned char *' for uImage_probe()
* arm64: add uImage support
* vmcore-dmesg: Define _GNU_SOURCE
* Don't use %L width specifier with integer values
* x86/x86_64: Fix format warning with die()
* ppc: Fix format warning with die()
* crashdump: Remove stray get_crashkernel_region() declaration
* x86: Support large number of memory ranges
* Fix broken Xen support in configure.ac
* kexec: extend the semantics of kexec_iomem_for_each_line
* kexec: generalize and rename get_kernel_stext_sym()
* arm64: identify PHYS_OFFSET correctly
* arm64: change return values on error to negative
* arm64: kdump: identify memory regions
* arm64: kdump: add elf core header segment
* arm64: kdump: set up kernel image segment
* arm64: kdump: set up other segments
* arm64: kdump: add DT properties to crash dump kernel's dtb
* arm64: kdump: Add support for binary image files
* Handle additional e820 memmap type strings

** Affects: kexec-tools (Ubuntu)
 Importance: High
 Assignee: Stefan Bader (smb)
 Status: Triaged


** Tags: artful

** Patch added: "Delta between current 2.0.14-1ubuntu5 and 2.0.15-0ubuntu1"
   
https://bugs.launchpad.net/bugs/1713940/+attachment/4941222/+files/newversion.debdiff

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

Title:
  kexec-tools 2.0.14 fails to load 4.12+ crash kernels

Status in kexec-tools package in Ubuntu:
  Triaged

Bug description:
  Starting with 4.12 kernels, kexec-tools cannot load a crash kernel
  because ELF core parsing fails with errors like:

Unknown type (Reserved) while parsing /sys/firmware/memmap/5/type.
Please report this as bug. Using RANGE_RESERVED now.
...
ELF core (kcore) parse failed
Cannot load /var/lib/kdump/vmlinuz

  The issue is fixed upstream in kexec-tools 2.0.15 (Debian is still at
  2.0.14)

  The complete changes list between 2.0.14 and 2.0.15 shows mostly bug
  fixes and in fact all additional patches in debian/patches which are
  Ubuntu delta, have moved into upstream 2.0.15. So we could drop all
  those while moving to the new version.

  * ppc64: Reduce number of ELF LOAD segments
  * kexec: Increase the upper limit for RAM segments
  * alpha: add missing __NR_kexec_load definition
  * kexec: implemented XEN KEXEC STATUS to determine if an image is loaded
  * kexec: Remove redundant space from help message
  * purgatory: Add purgatory.map and purgatory.ro.sym to clean recipe
  * kexec: Add option to get crash kernel region size
  * crashdump/arm: Add get_crash_kernel_load_range() function
  * crashdump/arm64: Add get_crash_kernel_load_range() function
  * crashdump/cris: Add get_crash_kernel_load_range() function
  * crashdump/ia64: Add get_crash_kernel_load_range() function
  * crashdump/m68k: Add get_crash_kernel_load_range() function
  * crashdump/m

[Kernel-packages] [Bug 1708399] dbginfo

[bugproxy]

Default Comment by Bridge

** Attachment added: "dbginfo"
   
https://bugs.launchpad.net/bugs/1708399/+attachment/4941238/+files/DBGINFO-2017-08-02-10-02-26-zml025-016A77.tgz

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

Title:
  kernel panic -not syncing: Fatal exception: panic_on_oops

Status in Ubuntu on IBM z Systems:
  New
Status in linux package in Ubuntu:
  New

Bug description:
  == Comment: #0 - QI YE  - 2017-08-02 04:11:25 ==
  ---Problem Description---
  Ubuntu got kernel panic

  ---uname output---
  #110-Ubuntu SMP Tue Jul 18 12:56:43 UTC 2017 s390x s390x s390x GNU/Linux
   
  ---Debugger Data---
  PID: 10991  TASK: 19872a0e8 CPU: 2   COMMAND: "hyperkube"
   LOWCORE INFO:
-psw  : 0x0004c0018000 0x00115fa6
-function : pcpu_delegate at 115fa6
-prefix   : 0x7fe42000
-cpu timer: 0x7ffab2827828aa50
-clock cmp: 0xd2eb8b31445e4200
-general registers:
   0x0004e001 0x001283b6
   0xc001 0x8380fcb8
   0x00115f9e 0x0056f6e2
   0x0004 0x00cf9070
   0x0001f3bfc000 0x00112fd8
   0x0001c72bb400 0x0002
   0x7fffc000 0x007c9ef0
   0x00115f9e 0x8380fc18
-access registers:
   0x03ff 0x7910 00 00
   00 00 00 00
   00 00 00 00
   00 00 00 00
-control registers:
   0x14066a12 0x7e6d81c7
   0x00011140 00
   0x2aef 0x0400
   0x5000 0x7e6d81c7
   00 00
   00 00
   00 0x00cfc007
   0xdb00 0x00011280
-floating point registers:
   0x409c7e258000 0x401de4e0
   00 0x3fd24407ab0e073a
   0x3ff0 0x3fee
   0x3fef218f8a7a41a0 0x3fee
   0x0080 00
   0x03ff7f80 0x02aa4940e9e0
   0xd401 0x03ffe81fe110
   00 0x03fff2cfe638

   #0 [8380fc78] smp_find_processor_id at 1160f8
   #1 [8380fc90] machine_kexec at 1135d4
   #2 [8380fcb8] crash_kexec at 1fbb8a
   #3 [8380fd88] panic at 27d0e0
   #4 [8380fe28] die at 1142cc
   #5 [8380fe90] do_low_address at 12215e
   #6 [8380fea8] pgm_check_handler at 7c2ab4
   PSW:  070520018000 02aa267e0e42 (user space)
   GPRS:   02aa2c4fd690 0001
 02aa2c4fd690 03ff7fffee38  0002
 00029c0f 00c42001ea00 0001 0001
 00c42001c5c8 00c42082c1a0 02aa2666325e 03ff7fffed90 
   
  Contact Information = Chee Ye / y...@cn.ibm.com 
   
  Stack trace output:
   no
   
  Oops output:
   [43200.761465] docker0: port 10(vethb9132e9) entered forwarding state
  [50008.560926] hrtimer: interrupt took 1698076 ns
  [123483.768984] systemd[1]: apt-daily.timer: Adding 7h 34min 22.582204s 
random time.
  [123483.930058] systemd[1]: apt-daily.timer: Adding 2h 18min 14.857162s 
random time.
  [123484.064879] systemd[1]: apt-daily.timer: Adding 10h 46min 2.301756s 
random time.
  [123484.824760] systemd[1]: apt-daily.timer: Adding 6h 16min 22.178655s 
random time.
  [153113.703126] conntrack: generic helper won't handle protocol 47. Please 
consider loading the specific helper module.
  [477085.704538] Low-address protection: 0004 ilc:2 [#1] SMP
  [477085.704551] Modules linked in: xt_physdev veth xt_recent xt_comment 
xt_mark xt_nat ipt_MASQUERADE nf_nat_masquerade_ipv4 xfrm_user xfrm_algo 
iptable_nat nf_nat_ipv4 xt_addrtype nf_nat br_netfilter bridge stp llc aufs 
ipt_REJECT nf_reject_ipv4 xt_tcpudp nf_conntrack_ipv4 nf_defrag_ipv4 
xt_conntrack nf_conntrack iptable_filter ip_tables x_tables ghash_s390 prng 
aes_s390 des_s390 des_generic sha512_s390 qeth_l2 sha256_s390 qeth sha1_s390 
qdio sha_common ccwgroup vmur dasd_eckd_mod dasd_mod
  [477085.705522] CPU: 2 PID: 10991 Comm: hyperkube Not tainted 
4.4.0-87-generic #110-Ubuntu
  [477085.705525] task: 00019872a0e8 ti: 8380c000 task.ti: 
8380c000
  [477085.705529] User PSW : 070520018000 02aa267e0e42
  [477085.705532]R:0 T:1 IO:1 EX:1 Key:0 M:1 W:0 P:1 AS:0 CC:2 PM:0 
EA:3
  User GPRS:   02aa2c4fd690 
0001
  [477085.705539]02aa2c4fd690 03ff7fffee38  
0002
  [477085.705553]00029c0f 00c42001ea00 0001 
0001
  [477085.705554]00c42001c5c8 00

[Kernel-packages] [Bug 1713940] Re: kexec-tools 2.0.14 fails to load 4.12+ crash kernels

[Ubuntu Foundations Team Bug Bot]

** Tags added: patch

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

Title:
  kexec-tools 2.0.14 fails to load 4.12+ crash kernels

Status in kexec-tools package in Ubuntu:
  Triaged

Bug description:
  Starting with 4.12 kernels, kexec-tools cannot load a crash kernel
  because ELF core parsing fails with errors like:

Unknown type (Reserved) while parsing /sys/firmware/memmap/5/type.
Please report this as bug. Using RANGE_RESERVED now.
...
ELF core (kcore) parse failed
Cannot load /var/lib/kdump/vmlinuz

  The issue is fixed upstream in kexec-tools 2.0.15 (Debian is still at
  2.0.14)

  The complete changes list between 2.0.14 and 2.0.15 shows mostly bug
  fixes and in fact all additional patches in debian/patches which are
  Ubuntu delta, have moved into upstream 2.0.15. So we could drop all
  those while moving to the new version.

  * ppc64: Reduce number of ELF LOAD segments
  * kexec: Increase the upper limit for RAM segments
  * alpha: add missing __NR_kexec_load definition
  * kexec: implemented XEN KEXEC STATUS to determine if an image is loaded
  * kexec: Remove redundant space from help message
  * purgatory: Add purgatory.map and purgatory.ro.sym to clean recipe
  * kexec: Add option to get crash kernel region size
  * crashdump/arm: Add get_crash_kernel_load_range() function
  * crashdump/arm64: Add get_crash_kernel_load_range() function
  * crashdump/cris: Add get_crash_kernel_load_range() function
  * crashdump/ia64: Add get_crash_kernel_load_range() function
  * crashdump/m68k: Add get_crash_kernel_load_range() function
  * crashdump/mips: Add get_crash_kernel_load_range() function
  * crashdump/ppc: Add get_crash_kernel_load_range() function
  * crashdump/ppc64: Add get_crash_kernel_load_range() function
  * crashdump/s390: Add get_crash_kernel_load_range() function
  * crashdump/sh: Add get_crash_kernel_load_range() function
  * gitignore: add two generated files in purgatory
  * Only print debug message when failed to serach for kernel symbol from
/proc/kallsyms
  * build_mem_phdrs(): check if p_paddr is invalid
  * uImage: fix realloc() pointer confusion
  * uImage: Fix uImage_load() for little-endian machines
  * uImage: Add new IH_ARCH_xxx definitions
  * uImage: use 'char *' instead of 'unsigned char *' for uImage_load()
  * uImage: use 'char *' instead of 'unsigned char *' for uImage_probe()
  * arm64: add uImage support
  * vmcore-dmesg: Define _GNU_SOURCE
  * Don't use %L width specifier with integer values
  * x86/x86_64: Fix format warning with die()
  * ppc: Fix format warning with die()
  * crashdump: Remove stray get_crashkernel_region() declaration
  * x86: Support large number of memory ranges
  * Fix broken Xen support in configure.ac
  * kexec: extend the semantics of kexec_iomem_for_each_line
  * kexec: generalize and rename get_kernel_stext_sym()
  * arm64: identify PHYS_OFFSET correctly
  * arm64: change return values on error to negative
  * arm64: kdump: identify memory regions
  * arm64: kdump: add elf core header segment
  * arm64: kdump: set up kernel image segment
  * arm64: kdump: set up other segments
  * arm64: kdump: add DT properties to crash dump kernel's dtb
  * arm64: kdump: Add support for binary image files
  * Handle additional e820 memmap type strings

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/kexec-tools/+bug/1713940/+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 1713765] Comment bridged from LTC Bugzilla

[bugproxy]

--- Comment From cborn...@de.ibm.com 2017-08-30 04:09 EDT---
FWIW, this fix is only necessary if you have guest that use storage keys - e.g. 
an 16.04 guest should not trigger this problem.

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

Title:
  Consider "s390/mm: avoid empty zero pages for KVM guests to avoid
  postcopy hangs" for Artful

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hi,
  there is this patch in discussion [1].

  If I read correctly between the lines that is supposed to go to -stable trees 
as well as to linxu-s390x next (4.14) submissions.
  But the change is rather big and we have to consider taking that early or as 
SRU or not at all.

  I wanted to ask the kernel Team to keep an eye on that discussion and take 
the patch into consideration - IMHO it might change KVM behavior on s390 quite 
a bit.
  So I'm not sure how SRUable it is while on Artful we migth add it rather soon 
before release.

  To some extend we should wait for the discussion on the upstreaming,
  but then I wanted to make you aware asap.

  [1]: https://lists.gnu.org/archive/html/qemu-
  devel/2017-08/msg05286.html

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1713765/+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 1653843] Re: Bluetooth 04ca:3018 not working correctly

[Matteo Lucca]

Hello Pilot6,

after using

wget 
https://launchpad.net/~hanipouspilot/+archive/ubuntu/bluetooth/+files/btusb-lp1653843-dkms_0.2_all.deb
sudo dpkg -i btusb-lp1653843-dkms_0.2_all.deb 

I get the output

ERROR (dkms apport): unable to determine source package for btusb-lp1653843-dkms
Error! Bad return status for module build on kernel: 4.10.0-32-generic (x86_64)
Consult /var/lib/dkms/btusb-lp1653843/0.2/build/make.log for more information.

do you know how to solve the problem?

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

Title:
  Bluetooth 04ca:3018 not working correctly

Status in linux package in Ubuntu:
  In Progress

Bug description:
  The bluetooth device is unable to discover any devices and when
  visible it cannot be discovered by any device.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-57-generic 4.4.0-57.78
  ProcVersionSignature: Ubuntu 4.4.0-57.78-generic 4.4.35
  Uname: Linux 4.4.0-57-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   david  3259 F...m pulseaudio
   /dev/snd/controlC0:  david  3259 F pulseaudio
  CurrentDesktop: Unity
  Date: Wed Jan  4 03:07:28 2017
  HibernationDevice: RESUME=UUID=53d59b56-5824-4ede-8752-62ef2e227c18
  InstallationDate: Installed on 2016-12-22 (12 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: ASUSTeK COMPUTER INC. X556UAK
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-57-generic.efi.signed 
root=UUID=5eed2705-b031-466b-8c03-d40f6ccfc133 ro quiet splash
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-57-generic N/A
   linux-backports-modules-4.4.0-57-generic  N/A
   linux-firmware1.157.6
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/05/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X556UAK.302
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X556UAK
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrX556UAK.302:bd09/05/2016:svnASUSTeKCOMPUTERINC.:pnX556UAK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX556UAK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: X556UAK
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1653843/+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 1708399] Re: kernel panic -not syncing: Fatal exception: panic_on_oops

[Stefan Bader]

While preparing to provide a test kernel I noticed that the backport for
patch #1 introduces a test for MACHINE_HAS_TLB_LC which is not present
even in linux-next. Martin, is this really correct?

+   /* Reset TLB flush mask */
+   if (MACHINE_HAS_TLB_LC)
+   cpumask_copy(mm_cpumask(mm), &mm->context.cpu_attach_mask);

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

Title:
  kernel panic -not syncing: Fatal exception: panic_on_oops

Status in Ubuntu on IBM z Systems:
  New
Status in linux package in Ubuntu:
  New

Bug description:
  == Comment: #0 - QI YE  - 2017-08-02 04:11:25 ==
  ---Problem Description---
  Ubuntu got kernel panic

  ---uname output---
  #110-Ubuntu SMP Tue Jul 18 12:56:43 UTC 2017 s390x s390x s390x GNU/Linux
   
  ---Debugger Data---
  PID: 10991  TASK: 19872a0e8 CPU: 2   COMMAND: "hyperkube"
   LOWCORE INFO:
-psw  : 0x0004c0018000 0x00115fa6
-function : pcpu_delegate at 115fa6
-prefix   : 0x7fe42000
-cpu timer: 0x7ffab2827828aa50
-clock cmp: 0xd2eb8b31445e4200
-general registers:
   0x0004e001 0x001283b6
   0xc001 0x8380fcb8
   0x00115f9e 0x0056f6e2
   0x0004 0x00cf9070
   0x0001f3bfc000 0x00112fd8
   0x0001c72bb400 0x0002
   0x7fffc000 0x007c9ef0
   0x00115f9e 0x8380fc18
-access registers:
   0x03ff 0x7910 00 00
   00 00 00 00
   00 00 00 00
   00 00 00 00
-control registers:
   0x14066a12 0x7e6d81c7
   0x00011140 00
   0x2aef 0x0400
   0x5000 0x7e6d81c7
   00 00
   00 00
   00 0x00cfc007
   0xdb00 0x00011280
-floating point registers:
   0x409c7e258000 0x401de4e0
   00 0x3fd24407ab0e073a
   0x3ff0 0x3fee
   0x3fef218f8a7a41a0 0x3fee
   0x0080 00
   0x03ff7f80 0x02aa4940e9e0
   0xd401 0x03ffe81fe110
   00 0x03fff2cfe638

   #0 [8380fc78] smp_find_processor_id at 1160f8
   #1 [8380fc90] machine_kexec at 1135d4
   #2 [8380fcb8] crash_kexec at 1fbb8a
   #3 [8380fd88] panic at 27d0e0
   #4 [8380fe28] die at 1142cc
   #5 [8380fe90] do_low_address at 12215e
   #6 [8380fea8] pgm_check_handler at 7c2ab4
   PSW:  070520018000 02aa267e0e42 (user space)
   GPRS:   02aa2c4fd690 0001
 02aa2c4fd690 03ff7fffee38  0002
 00029c0f 00c42001ea00 0001 0001
 00c42001c5c8 00c42082c1a0 02aa2666325e 03ff7fffed90 
   
  Contact Information = Chee Ye / y...@cn.ibm.com 
   
  Stack trace output:
   no
   
  Oops output:
   [43200.761465] docker0: port 10(vethb9132e9) entered forwarding state
  [50008.560926] hrtimer: interrupt took 1698076 ns
  [123483.768984] systemd[1]: apt-daily.timer: Adding 7h 34min 22.582204s 
random time.
  [123483.930058] systemd[1]: apt-daily.timer: Adding 2h 18min 14.857162s 
random time.
  [123484.064879] systemd[1]: apt-daily.timer: Adding 10h 46min 2.301756s 
random time.
  [123484.824760] systemd[1]: apt-daily.timer: Adding 6h 16min 22.178655s 
random time.
  [153113.703126] conntrack: generic helper won't handle protocol 47. Please 
consider loading the specific helper module.
  [477085.704538] Low-address protection: 0004 ilc:2 [#1] SMP
  [477085.704551] Modules linked in: xt_physdev veth xt_recent xt_comment 
xt_mark xt_nat ipt_MASQUERADE nf_nat_masquerade_ipv4 xfrm_user xfrm_algo 
iptable_nat nf_nat_ipv4 xt_addrtype nf_nat br_netfilter bridge stp llc aufs 
ipt_REJECT nf_reject_ipv4 xt_tcpudp nf_conntrack_ipv4 nf_defrag_ipv4 
xt_conntrack nf_conntrack iptable_filter ip_tables x_tables ghash_s390 prng 
aes_s390 des_s390 des_generic sha512_s390 qeth_l2 sha256_s390 qeth sha1_s390 
qdio sha_common ccwgroup vmur dasd_eckd_mod dasd_mod
  [477085.705522] CPU: 2 PID: 10991 Comm: hyperkube Not tainted 
4.4.0-87-generic #110-Ubuntu
  [477085.705525] task: 00019872a0e8 ti: 8380c000 task.ti: 
8380c000
  [477085.705529] User PSW : 070520018000 02aa267e0e42
  [477085.705532]R:0 T:1 IO:1 EX:1 Key:0 M:1 W:0 P:1 AS:0 CC:2 PM:0 
EA:3
  User GPRS:   02aa2c4fd690 
0001
  [477085.705539]02aa2c4fd690 03ff7fffee38  
00

[Kernel-packages] [Bug 1708399] Re: kernel panic -not syncing: Fatal exception: panic_on_oops

[Stefan Bader]

In fact hunk #3 of the original patch was also dropped which removed the
check in a different location. Yet, the last hunk removes the check for
that from the flush functions.

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

Title:
  kernel panic -not syncing: Fatal exception: panic_on_oops

Status in Ubuntu on IBM z Systems:
  New
Status in linux package in Ubuntu:
  New

Bug description:
  == Comment: #0 - QI YE  - 2017-08-02 04:11:25 ==
  ---Problem Description---
  Ubuntu got kernel panic

  ---uname output---
  #110-Ubuntu SMP Tue Jul 18 12:56:43 UTC 2017 s390x s390x s390x GNU/Linux
   
  ---Debugger Data---
  PID: 10991  TASK: 19872a0e8 CPU: 2   COMMAND: "hyperkube"
   LOWCORE INFO:
-psw  : 0x0004c0018000 0x00115fa6
-function : pcpu_delegate at 115fa6
-prefix   : 0x7fe42000
-cpu timer: 0x7ffab2827828aa50
-clock cmp: 0xd2eb8b31445e4200
-general registers:
   0x0004e001 0x001283b6
   0xc001 0x8380fcb8
   0x00115f9e 0x0056f6e2
   0x0004 0x00cf9070
   0x0001f3bfc000 0x00112fd8
   0x0001c72bb400 0x0002
   0x7fffc000 0x007c9ef0
   0x00115f9e 0x8380fc18
-access registers:
   0x03ff 0x7910 00 00
   00 00 00 00
   00 00 00 00
   00 00 00 00
-control registers:
   0x14066a12 0x7e6d81c7
   0x00011140 00
   0x2aef 0x0400
   0x5000 0x7e6d81c7
   00 00
   00 00
   00 0x00cfc007
   0xdb00 0x00011280
-floating point registers:
   0x409c7e258000 0x401de4e0
   00 0x3fd24407ab0e073a
   0x3ff0 0x3fee
   0x3fef218f8a7a41a0 0x3fee
   0x0080 00
   0x03ff7f80 0x02aa4940e9e0
   0xd401 0x03ffe81fe110
   00 0x03fff2cfe638

   #0 [8380fc78] smp_find_processor_id at 1160f8
   #1 [8380fc90] machine_kexec at 1135d4
   #2 [8380fcb8] crash_kexec at 1fbb8a
   #3 [8380fd88] panic at 27d0e0
   #4 [8380fe28] die at 1142cc
   #5 [8380fe90] do_low_address at 12215e
   #6 [8380fea8] pgm_check_handler at 7c2ab4
   PSW:  070520018000 02aa267e0e42 (user space)
   GPRS:   02aa2c4fd690 0001
 02aa2c4fd690 03ff7fffee38  0002
 00029c0f 00c42001ea00 0001 0001
 00c42001c5c8 00c42082c1a0 02aa2666325e 03ff7fffed90 
   
  Contact Information = Chee Ye / y...@cn.ibm.com 
   
  Stack trace output:
   no
   
  Oops output:
   [43200.761465] docker0: port 10(vethb9132e9) entered forwarding state
  [50008.560926] hrtimer: interrupt took 1698076 ns
  [123483.768984] systemd[1]: apt-daily.timer: Adding 7h 34min 22.582204s 
random time.
  [123483.930058] systemd[1]: apt-daily.timer: Adding 2h 18min 14.857162s 
random time.
  [123484.064879] systemd[1]: apt-daily.timer: Adding 10h 46min 2.301756s 
random time.
  [123484.824760] systemd[1]: apt-daily.timer: Adding 6h 16min 22.178655s 
random time.
  [153113.703126] conntrack: generic helper won't handle protocol 47. Please 
consider loading the specific helper module.
  [477085.704538] Low-address protection: 0004 ilc:2 [#1] SMP
  [477085.704551] Modules linked in: xt_physdev veth xt_recent xt_comment 
xt_mark xt_nat ipt_MASQUERADE nf_nat_masquerade_ipv4 xfrm_user xfrm_algo 
iptable_nat nf_nat_ipv4 xt_addrtype nf_nat br_netfilter bridge stp llc aufs 
ipt_REJECT nf_reject_ipv4 xt_tcpudp nf_conntrack_ipv4 nf_defrag_ipv4 
xt_conntrack nf_conntrack iptable_filter ip_tables x_tables ghash_s390 prng 
aes_s390 des_s390 des_generic sha512_s390 qeth_l2 sha256_s390 qeth sha1_s390 
qdio sha_common ccwgroup vmur dasd_eckd_mod dasd_mod
  [477085.705522] CPU: 2 PID: 10991 Comm: hyperkube Not tainted 
4.4.0-87-generic #110-Ubuntu
  [477085.705525] task: 00019872a0e8 ti: 8380c000 task.ti: 
8380c000
  [477085.705529] User PSW : 070520018000 02aa267e0e42
  [477085.705532]R:0 T:1 IO:1 EX:1 Key:0 M:1 W:0 P:1 AS:0 CC:2 PM:0 
EA:3
  User GPRS:   02aa2c4fd690 
0001
  [477085.705539]02aa2c4fd690 03ff7fffee38  
0002
  [477085.705553]00029c0f 00c42001ea00 0001 
0001
  [477085.705554]00c42001c5c8 0

[Kernel-packages] [Bug 1550301] Re: ZFS: Set elevator=noop on disks in the root pool

[Simon Quigley]

Unsubscribing ~ubuntu-sponsors as there's nothing left to do. If that is
incorrect, please feel free to resubscribe.

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

Title:
  ZFS: Set elevator=noop on disks in the root pool

Status in zfs-linux package in Ubuntu:
  In Progress
Status in zfs-linux source package in Xenial:
  Fix Released
Status in zfs-linux source package in Zesty:
  Confirmed

Bug description:
  ZFS-on-Linux has its own I/O scheduler, so it sets the "noop" elevator
  on whole disks used in a pool.
  https://github.com/zfsonlinux/zfs/issues/90

  It does not set the scheduler for a disk if a partition is used in a
  pool out of respect for the possibility that there are non-ZFS
  partitions on the same disk.
  https://github.com/zfsonlinux/zfs/issues/152

  For regular pools, the recommendation is to use whole disks. For a
  root pools, it's just the opposite. The typical case is that
  partitions are used. And, for root pools, it is unlikely that the same
  disks have non-ZFS filesystems.

  The debdiff in comment #5 applies cleanly to the latest package and
  functions correctly. This is an important change for root-on-ZFS
  users. It has no effect on non-root-on-ZFS installs, because the code
  is only in the zfs-initramfs package.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1550301/+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 1708399] Comment bridged from LTC Bugzilla

[bugproxy]

--- Comment From martin.schwidef...@de.ibm.com 2017-08-30 04:53 EDT---
The upstream version of __tlb_flush_mm has this:

static inline void __tlb_flush_mm(struct mm_struct *mm)
{
...
/* Reset TLB flush mask */
cpumask_copy(mm_cpumask(mm), &mm->context.cpu_attach_mask);
...
}

The difference is because of git commit 64f31d5802af11fd
"s390/mm: simplify the TLB flushing code" which removed the
check for MACHINE_HAS_TLB_LC and simply always does the
copy.

Imho the patch is correct.

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

Title:
  kernel panic -not syncing: Fatal exception: panic_on_oops

Status in Ubuntu on IBM z Systems:
  New
Status in linux package in Ubuntu:
  New

Bug description:
  == Comment: #0 - QI YE  - 2017-08-02 04:11:25 ==
  ---Problem Description---
  Ubuntu got kernel panic

  ---uname output---
  #110-Ubuntu SMP Tue Jul 18 12:56:43 UTC 2017 s390x s390x s390x GNU/Linux
   
  ---Debugger Data---
  PID: 10991  TASK: 19872a0e8 CPU: 2   COMMAND: "hyperkube"
   LOWCORE INFO:
-psw  : 0x0004c0018000 0x00115fa6
-function : pcpu_delegate at 115fa6
-prefix   : 0x7fe42000
-cpu timer: 0x7ffab2827828aa50
-clock cmp: 0xd2eb8b31445e4200
-general registers:
   0x0004e001 0x001283b6
   0xc001 0x8380fcb8
   0x00115f9e 0x0056f6e2
   0x0004 0x00cf9070
   0x0001f3bfc000 0x00112fd8
   0x0001c72bb400 0x0002
   0x7fffc000 0x007c9ef0
   0x00115f9e 0x8380fc18
-access registers:
   0x03ff 0x7910 00 00
   00 00 00 00
   00 00 00 00
   00 00 00 00
-control registers:
   0x14066a12 0x7e6d81c7
   0x00011140 00
   0x2aef 0x0400
   0x5000 0x7e6d81c7
   00 00
   00 00
   00 0x00cfc007
   0xdb00 0x00011280
-floating point registers:
   0x409c7e258000 0x401de4e0
   00 0x3fd24407ab0e073a
   0x3ff0 0x3fee
   0x3fef218f8a7a41a0 0x3fee
   0x0080 00
   0x03ff7f80 0x02aa4940e9e0
   0xd401 0x03ffe81fe110
   00 0x03fff2cfe638

   #0 [8380fc78] smp_find_processor_id at 1160f8
   #1 [8380fc90] machine_kexec at 1135d4
   #2 [8380fcb8] crash_kexec at 1fbb8a
   #3 [8380fd88] panic at 27d0e0
   #4 [8380fe28] die at 1142cc
   #5 [8380fe90] do_low_address at 12215e
   #6 [8380fea8] pgm_check_handler at 7c2ab4
   PSW:  070520018000 02aa267e0e42 (user space)
   GPRS:   02aa2c4fd690 0001
 02aa2c4fd690 03ff7fffee38  0002
 00029c0f 00c42001ea00 0001 0001
 00c42001c5c8 00c42082c1a0 02aa2666325e 03ff7fffed90 
   
  Contact Information = Chee Ye / y...@cn.ibm.com 
   
  Stack trace output:
   no
   
  Oops output:
   [43200.761465] docker0: port 10(vethb9132e9) entered forwarding state
  [50008.560926] hrtimer: interrupt took 1698076 ns
  [123483.768984] systemd[1]: apt-daily.timer: Adding 7h 34min 22.582204s 
random time.
  [123483.930058] systemd[1]: apt-daily.timer: Adding 2h 18min 14.857162s 
random time.
  [123484.064879] systemd[1]: apt-daily.timer: Adding 10h 46min 2.301756s 
random time.
  [123484.824760] systemd[1]: apt-daily.timer: Adding 6h 16min 22.178655s 
random time.
  [153113.703126] conntrack: generic helper won't handle protocol 47. Please 
consider loading the specific helper module.
  [477085.704538] Low-address protection: 0004 ilc:2 [#1] SMP
  [477085.704551] Modules linked in: xt_physdev veth xt_recent xt_comment 
xt_mark xt_nat ipt_MASQUERADE nf_nat_masquerade_ipv4 xfrm_user xfrm_algo 
iptable_nat nf_nat_ipv4 xt_addrtype nf_nat br_netfilter bridge stp llc aufs 
ipt_REJECT nf_reject_ipv4 xt_tcpudp nf_conntrack_ipv4 nf_defrag_ipv4 
xt_conntrack nf_conntrack iptable_filter ip_tables x_tables ghash_s390 prng 
aes_s390 des_s390 des_generic sha512_s390 qeth_l2 sha256_s390 qeth sha1_s390 
qdio sha_common ccwgroup vmur dasd_eckd_mod dasd_mod
  [477085.705522] CPU: 2 PID: 10991 Comm: hyperkube Not tainted 
4.4.0-87-generic #110-Ubuntu
  [477085.705525] task: 00019872a0e8 ti: 8380c000 task.ti: 
8380c000
  [477085.705529] User PSW : 070520018000 02aa267e0e42
  [477085.705532]R:0 T:1 IO:1 EX:1 Key:0 M:1 W:0 P:1 AS:0 CC:2 PM:0 
EA:3
  User GPRS: 

[Kernel-packages] [Bug 1713765] Re: Consider "s390/mm: avoid empty zero pages for KVM guests to avoid postcopy hangs" for Artful

[ChristianEhrhardt]

Continued the discussion on IRC:

[10:19]  cpaelzer: just to shortcut. FWIW, this fix is only necessary 
if you have guest that use storage keys - e.g. an 16.04 guest should not 
trigger this problem.
[10:21]  hws: do we have any linux guests that use storgae keys in 
the meantime?
[10:21]  I might have lost track
[10:21]  cpaelzer: question for christian...
[10:21]  and as a HV host it is a bit weird, as you can only make "so 
much" assumption on your guests
[10:22]  who says no one uses a Ubuntu Xenial as host in 2020 (still 
supported then) with a new Guest that suddenly uses stroage keys
[10:22]  ...
[10:22]  anyway this is just the sort of discussion that I wanted on 
that bugzilla
[10:22]  for a more permanent documentation of the case
[10:23]  and since it is mirrored now this will happen
[10:23]  I don't mind loosing a few hours for the mirroring
[10:32]  cpaelzer, hws no current Linux guest uses storage keys
[10:32]  sles 11 and rhel6 do
[10:32]  sles12, rhel7 ubuntu 16.04 do not
[10:32]  well the old one before we removed it
[10:33]  so since there is no intention to add storage keys back in 
Linux or host non Linux (not intention I'd know of) - the TL;DR is "not needed"?
[10:40]  cpaelzer, unless you want to support some old debians as 
guest or so
[10:45]  borntraeger: did anybody check if there really is no perf 
impact?
[10:45]  I know that over time all pages will be used
[10:45]  but I thought the zero page would still be overloaded
[10:45]  or is even the fix
[10:45]  only active on storage key using guests
[10:46]  borntraeger: and so it is not only "not needed" but even 
when applied "not actively changing" the zero page handling as long as you have 
only "new" guests?
[10:48]  cpaelzer, if a guest has a pattern of only reading a 
page, it will be a zero page inside the guest
[10:49]  cpaelzer, the fix is to not use zero pages in the host to 
back guest pages

So leaving it to the kernel Team, but I'd think won't fix is correct for
now.

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

Title:
  Consider "s390/mm: avoid empty zero pages for KVM guests to avoid
  postcopy hangs" for Artful

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hi,
  there is this patch in discussion [1].

  If I read correctly between the lines that is supposed to go to -stable trees 
as well as to linxu-s390x next (4.14) submissions.
  But the change is rather big and we have to consider taking that early or as 
SRU or not at all.

  I wanted to ask the kernel Team to keep an eye on that discussion and take 
the patch into consideration - IMHO it might change KVM behavior on s390 quite 
a bit.
  So I'm not sure how SRUable it is while on Artful we migth add it rather soon 
before release.

  To some extend we should wait for the discussion on the upstreaming,
  but then I wanted to make you aware asap.

  [1]: https://lists.gnu.org/archive/html/qemu-
  devel/2017-08/msg05286.html

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1713765/+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 1708399] Re: kernel panic -not syncing: Fatal exception: panic_on_oops

[Stefan Bader]

Ah ok, thanks. Will add some info to the commit message and prepare that
test kernel.

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

Title:
  kernel panic -not syncing: Fatal exception: panic_on_oops

Status in Ubuntu on IBM z Systems:
  New
Status in linux package in Ubuntu:
  New

Bug description:
  == Comment: #0 - QI YE  - 2017-08-02 04:11:25 ==
  ---Problem Description---
  Ubuntu got kernel panic

  ---uname output---
  #110-Ubuntu SMP Tue Jul 18 12:56:43 UTC 2017 s390x s390x s390x GNU/Linux
   
  ---Debugger Data---
  PID: 10991  TASK: 19872a0e8 CPU: 2   COMMAND: "hyperkube"
   LOWCORE INFO:
-psw  : 0x0004c0018000 0x00115fa6
-function : pcpu_delegate at 115fa6
-prefix   : 0x7fe42000
-cpu timer: 0x7ffab2827828aa50
-clock cmp: 0xd2eb8b31445e4200
-general registers:
   0x0004e001 0x001283b6
   0xc001 0x8380fcb8
   0x00115f9e 0x0056f6e2
   0x0004 0x00cf9070
   0x0001f3bfc000 0x00112fd8
   0x0001c72bb400 0x0002
   0x7fffc000 0x007c9ef0
   0x00115f9e 0x8380fc18
-access registers:
   0x03ff 0x7910 00 00
   00 00 00 00
   00 00 00 00
   00 00 00 00
-control registers:
   0x14066a12 0x7e6d81c7
   0x00011140 00
   0x2aef 0x0400
   0x5000 0x7e6d81c7
   00 00
   00 00
   00 0x00cfc007
   0xdb00 0x00011280
-floating point registers:
   0x409c7e258000 0x401de4e0
   00 0x3fd24407ab0e073a
   0x3ff0 0x3fee
   0x3fef218f8a7a41a0 0x3fee
   0x0080 00
   0x03ff7f80 0x02aa4940e9e0
   0xd401 0x03ffe81fe110
   00 0x03fff2cfe638

   #0 [8380fc78] smp_find_processor_id at 1160f8
   #1 [8380fc90] machine_kexec at 1135d4
   #2 [8380fcb8] crash_kexec at 1fbb8a
   #3 [8380fd88] panic at 27d0e0
   #4 [8380fe28] die at 1142cc
   #5 [8380fe90] do_low_address at 12215e
   #6 [8380fea8] pgm_check_handler at 7c2ab4
   PSW:  070520018000 02aa267e0e42 (user space)
   GPRS:   02aa2c4fd690 0001
 02aa2c4fd690 03ff7fffee38  0002
 00029c0f 00c42001ea00 0001 0001
 00c42001c5c8 00c42082c1a0 02aa2666325e 03ff7fffed90 
   
  Contact Information = Chee Ye / y...@cn.ibm.com 
   
  Stack trace output:
   no
   
  Oops output:
   [43200.761465] docker0: port 10(vethb9132e9) entered forwarding state
  [50008.560926] hrtimer: interrupt took 1698076 ns
  [123483.768984] systemd[1]: apt-daily.timer: Adding 7h 34min 22.582204s 
random time.
  [123483.930058] systemd[1]: apt-daily.timer: Adding 2h 18min 14.857162s 
random time.
  [123484.064879] systemd[1]: apt-daily.timer: Adding 10h 46min 2.301756s 
random time.
  [123484.824760] systemd[1]: apt-daily.timer: Adding 6h 16min 22.178655s 
random time.
  [153113.703126] conntrack: generic helper won't handle protocol 47. Please 
consider loading the specific helper module.
  [477085.704538] Low-address protection: 0004 ilc:2 [#1] SMP
  [477085.704551] Modules linked in: xt_physdev veth xt_recent xt_comment 
xt_mark xt_nat ipt_MASQUERADE nf_nat_masquerade_ipv4 xfrm_user xfrm_algo 
iptable_nat nf_nat_ipv4 xt_addrtype nf_nat br_netfilter bridge stp llc aufs 
ipt_REJECT nf_reject_ipv4 xt_tcpudp nf_conntrack_ipv4 nf_defrag_ipv4 
xt_conntrack nf_conntrack iptable_filter ip_tables x_tables ghash_s390 prng 
aes_s390 des_s390 des_generic sha512_s390 qeth_l2 sha256_s390 qeth sha1_s390 
qdio sha_common ccwgroup vmur dasd_eckd_mod dasd_mod
  [477085.705522] CPU: 2 PID: 10991 Comm: hyperkube Not tainted 
4.4.0-87-generic #110-Ubuntu
  [477085.705525] task: 00019872a0e8 ti: 8380c000 task.ti: 
8380c000
  [477085.705529] User PSW : 070520018000 02aa267e0e42
  [477085.705532]R:0 T:1 IO:1 EX:1 Key:0 M:1 W:0 P:1 AS:0 CC:2 PM:0 
EA:3
  User GPRS:   02aa2c4fd690 
0001
  [477085.705539]02aa2c4fd690 03ff7fffee38  
0002
  [477085.705553]00029c0f 00c42001ea00 0001 
0001
  [477085.705554]00c42001c5c8 00c42082c1a0 02aa2666325e 
03ff7fffed90
  [477085.705578] User Code: 02aa267e0e

[Kernel-packages] [Bug 1670634] Comment bridged from LTC Bugzilla

[bugproxy]

--- Comment From heinz-werner_se...@de.ibm.com 2017-08-30 05:15 EDT---
This function worked with SLES 12 SP2  kernel 4.4.74.

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

Title:
  blk-mq: possible deadlock on CPU hot(un)plug

Status in Ubuntu on IBM z Systems:
  Triaged
Status in linux package in Ubuntu:
  Triaged

Bug description:
  == Comment: #0 - Carsten Jacobi  - 2017-03-07 03:35:31 ==
  I'm evaluating Ubuntu-Xenial on z for development purposes, the test system 
is installed in an LPAR with one FCP-LUN which is accessable by 4 pathes (all 
pathes are configured).
  The system hangs regularly when I make packages with "pdebuild" using the 
pbuilder packaging suit.
  The local Linux development team helped me out with a pre-analysis that I can 
post here (thanks a lot for that):

  With the default settings and under a certain workload,
  blk_mq seems to get into a presumed "deadlock".
  Possibly this happens on CPU hot(un)plug.

  After the I/O stalled, a dump was pulled manually.
  The following information is from the crash dump pre-analysis.

  $ zgetdump -i dump.0
  General dump info:
Dump format: elf
Version: 1
UTS node name..: mclint
UTS kernel release.: 4.4.0-65-generic
UTS kernel version.: #86-Ubuntu SMP Thu Feb 23 17:54:37 UTC 2017
System arch: s390x (64 bit)
CPU count (online).: 2
Dump memory range..: 8192 MB
  Memory map:
 - 0001b831afff (7043 MB)
0001b831b000 - 0001 (1149 MB)

  Things look similarly with HWE kernel ubuntu16.04-4.8.0-34.36~16.04.1.

KERNEL: vmlinux.full
  DUMPFILE: dump.0
  CPUS: 2
  DATE: Fri Mar  3 14:31:07 2017
UPTIME: 02:11:20
  LOAD AVERAGE: 13.00, 12.92, 11.37
 TASKS: 411
  NODENAME: mclint
   RELEASE: 4.4.0-65-generic
   VERSION: #86-Ubuntu SMP Thu Feb 23 17:54:37 UTC 2017
   MACHINE: s390x  (unknown Mhz)
MEMORY: 7.8 GB
 PANIC: ""
   PID: 0
   COMMAND: "swapper/0"
  TASK: bad528  (1 of 2)  [THREAD_INFO: b78000]
   CPU: 0
 STATE: TASK_RUNNING (ACTIVE)
  INFO: no panic task found

  crash> dev -d
  MAJOR GENDISKNAME   REQUEST_QUEUE  TOTAL ASYNC  SYNC   DRV
  ...
  8 1e1d6d800  sda1e1d51210  0 23151 4294944145 
N/A(MQ)
  8 1e4e06800  sdc2081b180 23148 4294944148 
N/A(MQ)
  8 1f07800sdb20c75680 23195 4294944101 
N/A(MQ)
  8 1e4e06000  sdd1e4e31210  0 23099 4294944197 
N/A(MQ)
252 1e1d6c800  dm-0   1e1d51b18  9 1 8 
N/A(MQ)
  ...

  So both dm-mpath and sd have requests pending in their block multiqueue.
  The large numbers of sd look strange and seem to be the unsigned formatting 
of the values shown for async multiplied by -1.

  [0.798256] Linux version 4.4.0-65-generic (buildd@z13-011) (gcc version 
5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.4) ) #86-Ubuntu SMP Thu Feb 23 
17:54:37 UTC 2017 (Ubuntu 4.4.0-65.86-generic 4.4.49)
  [0.798262] setup: Linux is running natively in 64-bit mode
  [0.798290] setup: Max memory size: 8192MB
  [0.798298] setup: Reserving 196MB of memory at 7996MB for crashkernel 
(System RAM: 7996MB)

  [0.836923] Kernel command line: root=/dev/mapper/mclint_vg-root
  rootflags=subvol=@ crashkernel=196M BOOT_IMAGE=0

  [ 5281.179428] INFO: task xfsaild/dm-11:1604 blocked for more than 120 
seconds.
  [ 5281.179437]   Not tainted 4.4.0-65-generic #86-Ubuntu
  [ 5281.179438] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [ 5281.179440] xfsaild/dm-11   D 007bcf52 0  1604  2 
0x
  [ 5281.179444]0001e931c230 001a6964 0001e6f9b958 
0001e6f9b9d8
0001e15795f0 0001e6f9b988 00ce8c00 
0001ea805c70
0001ea805c00 00ba5ed0 0001e931c1d0 
0001e1579b20
0001ea805c00 0001e15795f0 0001ea805c00 

007d3978 007bc9f8 0001e6f9b9d8 
0001e6f9ba40
  [ 5281.179454] Call Trace:
  [ 5281.179461] ([<007bc9f8>] __schedule+0x300/0x810)
  [ 5281.179462]  [<007bcf52>] schedule+0x4a/0xb0
  [ 5281.179465]  [<007c02aa>] schedule_timeout+0x232/0x2a8
  [ 5281.179466]  [<007bde50>] wait_for_common+0x110/0x1c8
  [ 5281.179472]  [<0017b602>] flush_work+0x42/0x58
  [ 5281.179564]  [<03ff805e14ba>] xlog_cil_force_lsn+0x7a/0x238 [xfs]
  [ 5281.179589]  [<03ff805dee82>] _xfs_log_force+0x9a/0x2e8 [xfs]
  [ 5281.179615]  [<03ff805df114>] xfs_log_force+0x44/0x100 [xfs]
  [ 5281.179640]  [<03ff805ec668>] xfsaild+

[Kernel-packages] [Bug 1653843] Re: Bluetooth 04ca:3018 not working correctly

[Pilot6]

Fixed in zesty

http://kernel.ubuntu.com/git/ubuntu/ubuntu-
zesty.git/commit/?id=9a84078d73ffbe009f394fa06d3a5112d0bf5fe5

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

Title:
  Bluetooth 04ca:3018 not working correctly

Status in linux package in Ubuntu:
  Fix Released

Bug description:
  The bluetooth device is unable to discover any devices and when
  visible it cannot be discovered by any device.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-57-generic 4.4.0-57.78
  ProcVersionSignature: Ubuntu 4.4.0-57.78-generic 4.4.35
  Uname: Linux 4.4.0-57-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   david  3259 F...m pulseaudio
   /dev/snd/controlC0:  david  3259 F pulseaudio
  CurrentDesktop: Unity
  Date: Wed Jan  4 03:07:28 2017
  HibernationDevice: RESUME=UUID=53d59b56-5824-4ede-8752-62ef2e227c18
  InstallationDate: Installed on 2016-12-22 (12 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: ASUSTeK COMPUTER INC. X556UAK
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-57-generic.efi.signed 
root=UUID=5eed2705-b031-466b-8c03-d40f6ccfc133 ro quiet splash
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-57-generic N/A
   linux-backports-modules-4.4.0-57-generic  N/A
   linux-firmware1.157.6
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/05/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X556UAK.302
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X556UAK
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrX556UAK.302:bd09/05/2016:svnASUSTeKCOMPUTERINC.:pnX556UAK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX556UAK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: X556UAK
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1653843/+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 1653843] Re: Bluetooth 04ca:3018 not working correctly

[Pilot6]

@Matteo,

This module has been built for the 4.4 kernel. It is not compatible with
the 4.10 one.

And you don't need it, because the patch is already there. It is in
Ubuntu kernel 4.10.0-32

So remove this package.

** Changed in: linux (Ubuntu)
   Status: In Progress => Fix 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/1653843

Title:
  Bluetooth 04ca:3018 not working correctly

Status in linux package in Ubuntu:
  Fix Released

Bug description:
  The bluetooth device is unable to discover any devices and when
  visible it cannot be discovered by any device.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-57-generic 4.4.0-57.78
  ProcVersionSignature: Ubuntu 4.4.0-57.78-generic 4.4.35
  Uname: Linux 4.4.0-57-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   david  3259 F...m pulseaudio
   /dev/snd/controlC0:  david  3259 F pulseaudio
  CurrentDesktop: Unity
  Date: Wed Jan  4 03:07:28 2017
  HibernationDevice: RESUME=UUID=53d59b56-5824-4ede-8752-62ef2e227c18
  InstallationDate: Installed on 2016-12-22 (12 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: ASUSTeK COMPUTER INC. X556UAK
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-57-generic.efi.signed 
root=UUID=5eed2705-b031-466b-8c03-d40f6ccfc133 ro quiet splash
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-57-generic N/A
   linux-backports-modules-4.4.0-57-generic  N/A
   linux-firmware1.157.6
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/05/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X556UAK.302
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X556UAK
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrX556UAK.302:bd09/05/2016:svnASUSTeKCOMPUTERINC.:pnX556UAK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX556UAK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: X556UAK
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1653843/+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 1653843] Re: Bluetooth 04ca:3018 not working correctly

[Pilot6]

Fixed in xenial

http://kernel.ubuntu.com/git/ubuntu/ubuntu-
xenial.git/commit/?id=8405415606fa946702a3401cd64d418f48886ba7

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

Title:
  Bluetooth 04ca:3018 not working correctly

Status in linux package in Ubuntu:
  Fix Released

Bug description:
  The bluetooth device is unable to discover any devices and when
  visible it cannot be discovered by any device.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-57-generic 4.4.0-57.78
  ProcVersionSignature: Ubuntu 4.4.0-57.78-generic 4.4.35
  Uname: Linux 4.4.0-57-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   david  3259 F...m pulseaudio
   /dev/snd/controlC0:  david  3259 F pulseaudio
  CurrentDesktop: Unity
  Date: Wed Jan  4 03:07:28 2017
  HibernationDevice: RESUME=UUID=53d59b56-5824-4ede-8752-62ef2e227c18
  InstallationDate: Installed on 2016-12-22 (12 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: ASUSTeK COMPUTER INC. X556UAK
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-57-generic.efi.signed 
root=UUID=5eed2705-b031-466b-8c03-d40f6ccfc133 ro quiet splash
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-57-generic N/A
   linux-backports-modules-4.4.0-57-generic  N/A
   linux-firmware1.157.6
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/05/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X556UAK.302
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X556UAK
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrX556UAK.302:bd09/05/2016:svnASUSTeKCOMPUTERINC.:pnX556UAK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX556UAK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: X556UAK
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1653843/+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 1705748] Re: Samsung SSD 960 EVO 500GB refused to change power state

[Steve Roberts]

I haven't yet tried with that latest kernel... but this morning, after 5
days of successful suspend/resume:

Aug 30 09:35:19 phs08 kernel: [71904.271956] nvme nvme0: controller is down; 
will reset: CSTS=0x, PCI_STATUS=0x10
Aug 30 09:35:19 phs08 kernel: [71904.320269] print_req_error: I/O error, dev 
nvme0n1, sector 136098096
Aug 30 09:35:19 phs08 kernel: [71904.320280] BTRFS error (device nvme0n1p5): 
bdev /dev/nvme0n1p5 errs: wr 1, rd 0, flush 0, corrupt 0, gen 0
Aug 30 09:35:19 phs08 kernel: [71904.339992] nvme :01:00.0: enabling device 
( -> 0002)
Aug 30 09:35:19 phs08 kernel: [71904.340163] nvme nvme0: Removing after probe 
failure status: -19
Aug 30 09:35:19 phs08 kernel: [71904.371974] nvme0n1: detected capacity change 
from 500107862016 to 0

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

Title:
  Samsung SSD 960 EVO 500GB refused to change power state

Status in linux package in Ubuntu:
  In Progress

Bug description:
  Originally thought my issue was same as this:
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1678184
  but requested to report as separate bug

  System becomes unusable at seemingly random times but especially after
  resume from suspend due to disk 'disappearing' becoming inaccessible,
  with hundreds of I/O errors logged.

  After viewing the above bug report yesterday as a quick temporary fix I added 
kernel param, updated grub, etc with:
  GRUB_CMDLINE_LINUX_DEFAULT="nvme_core.default_ps_max_latency_us=0"

  System appears to have been stable for the last day, but is presumably
  using more power than it should.

  System, drive details below:

  M2 nvme drive: Samsung SSD 960 EVO 500GB

  Ubuntu 4.10.0-26.30~16.04.1-generic 4.10.17

  M/B Asus Prime B350m-A
  Ryzen 1600 cpu

  Jul 20 16:32:59 phs08 kernel: [ 190.893571] INVALID_DEVICE_REQUEST 
device=00:00.0 address=0xfffdf800 flags=0x0a00]
  Jul 20 16:33:05 phs08 kernel: [ 197.010928] nvme :01:00.0: controller is 
down; will reset: CSTS=0x, PCI_STATUS=0x
  Jul 20 16:33:05 phs08 kernel: [ 197.046980] pci_raw_set_power_state: 4 
callbacks suppressed
  Jul 20 16:33:05 phs08 kernel: [ 197.046985] nvme :01:00.0: Refused to 
change power state, currently in D3
  Jul 20 16:33:05 phs08 kernel: [ 197.047163] nvme nvme0: Removing after probe 
failure status: -19
  Jul 20 16:33:05 phs08 kernel: [ 197.047182] nvme0n1: detected capacity change 
from 500107862016 to 0
  Jul 20 16:33:05 phs08 kernel: [ 197.047793] blk_update_request: I/O error, 
dev nvme0n1, sector 0

  
  nvme list

  /dev/nvme0n1 S3EUNX0J305518L Samsung SSD 960 EVO 500GB 1.2 1 125.20 GB
  / 500.11 GB 512 B + 0 B 2B7QCXE7

  sudo nvme id-ctrl /dev/nvme0

  NVME Identify Controller:
  vid : 0x144d
  ssvid : 0x144d
  sn : S3EUNX0J305518L
  mn : Samsung SSD 960 EVO 500GB
  fr : 2B7QCXE7
  rab : 2
  ieee : 002538
  cmic : 0
  mdts : 9
  cntlid : 2
  ver : 10200
  rtd3r : 7a120
  rtd3e : 4c4b40
  oaes : 0
  oacs : 0x7
  acl : 7
  aerl : 3
  frmw : 0x16
  lpa : 0x3
  elpe : 63
  npss : 4
  avscc : 0x1
  apsta : 0x1
  wctemp : 350
  cctemp : 352
  mtfa : 0
  hmpre : 0
  hmmin : 0
  tnvmcap : 500107862016
  unvmcap : 0
  rpmbs : 0
  sqes : 0x66
  cqes : 0x44
  nn : 1
  oncs : 0x1f
  fuses : 0
  fna : 0x5
  vwc : 0x1
  awun : 255
  awupf : 0
  nvscc : 1
  acwu : 0
  sgls : 0
  ps 0 : mp:6.04W operational enlat:0 exlat:0 rrt:0 rrl:0
rwt:0 rwl:0 idle_power:- active_power:-
  ps 1 : mp:5.09W operational enlat:0 exlat:0 rrt:1 rrl:1
rwt:1 rwl:1 idle_power:- active_power:-
  ps 2 : mp:4.08W operational enlat:0 exlat:0 rrt:2 rrl:2
rwt:2 rwl:2 idle_power:- active_power:-
  ps 3 : mp:0.0400W non-operational enlat:210 exlat:1500 rrt:3 rrl:3
rwt:3 rwl:3 idle_power:- active_power:-
  ps 4 : mp:0.0050W non-operational enlat:2200 exlat:6000 rrt:4 rrl:4
rwt:4 rwl:4 idle_power:- active_power:-
  --- 
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  drgrumpy   2192 F pulseaudio
   /dev/snd/pcmC1D0p:   drgrumpy   2192 F...m pulseaudio
   /dev/snd/controlC1:  drgrumpy   2192 F pulseaudio
  DistroRelease: Linux 18.2
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=a6896cdd-6bac-4e7f-9e13-55460859c3ec
  InstallationDate: Installed on 2017-07-06 (15 days ago)
  InstallationMedia: Linux Mint 18.2 "Sonya" - Release amd64 20170628
  IwConfig:
   lono wireless extensions.
   
   enp37s0   no wireless extensions.
  MachineType: System manufacturer System Product Name
  Package: linux (not installed)
  ProcEnviron:
   LANGUAGE=en_GB:en
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-26-generic 
root=UUID=f7ae652b-cbf6-48b8-bc6a-d3963957ab57 ro 
nvme_core.default_ps_max_latency

[Kernel-packages] [Bug 1713940] Re: kexec-tools 2.0.14 fails to load 4.12+ crash kernels

[Andy Whitcroft]

** Changed in: kexec-tools (Ubuntu)
   Status: Triaged => In Progress

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

Title:
  kexec-tools 2.0.14 fails to load 4.12+ crash kernels

Status in kexec-tools package in Ubuntu:
  In Progress

Bug description:
  Starting with 4.12 kernels, kexec-tools cannot load a crash kernel
  because ELF core parsing fails with errors like:

Unknown type (Reserved) while parsing /sys/firmware/memmap/5/type.
Please report this as bug. Using RANGE_RESERVED now.
...
ELF core (kcore) parse failed
Cannot load /var/lib/kdump/vmlinuz

  The issue is fixed upstream in kexec-tools 2.0.15 (Debian is still at
  2.0.14)

  The complete changes list between 2.0.14 and 2.0.15 shows mostly bug
  fixes and in fact all additional patches in debian/patches which are
  Ubuntu delta, have moved into upstream 2.0.15. So we could drop all
  those while moving to the new version.

  * ppc64: Reduce number of ELF LOAD segments
  * kexec: Increase the upper limit for RAM segments
  * alpha: add missing __NR_kexec_load definition
  * kexec: implemented XEN KEXEC STATUS to determine if an image is loaded
  * kexec: Remove redundant space from help message
  * purgatory: Add purgatory.map and purgatory.ro.sym to clean recipe
  * kexec: Add option to get crash kernel region size
  * crashdump/arm: Add get_crash_kernel_load_range() function
  * crashdump/arm64: Add get_crash_kernel_load_range() function
  * crashdump/cris: Add get_crash_kernel_load_range() function
  * crashdump/ia64: Add get_crash_kernel_load_range() function
  * crashdump/m68k: Add get_crash_kernel_load_range() function
  * crashdump/mips: Add get_crash_kernel_load_range() function
  * crashdump/ppc: Add get_crash_kernel_load_range() function
  * crashdump/ppc64: Add get_crash_kernel_load_range() function
  * crashdump/s390: Add get_crash_kernel_load_range() function
  * crashdump/sh: Add get_crash_kernel_load_range() function
  * gitignore: add two generated files in purgatory
  * Only print debug message when failed to serach for kernel symbol from
/proc/kallsyms
  * build_mem_phdrs(): check if p_paddr is invalid
  * uImage: fix realloc() pointer confusion
  * uImage: Fix uImage_load() for little-endian machines
  * uImage: Add new IH_ARCH_xxx definitions
  * uImage: use 'char *' instead of 'unsigned char *' for uImage_load()
  * uImage: use 'char *' instead of 'unsigned char *' for uImage_probe()
  * arm64: add uImage support
  * vmcore-dmesg: Define _GNU_SOURCE
  * Don't use %L width specifier with integer values
  * x86/x86_64: Fix format warning with die()
  * ppc: Fix format warning with die()
  * crashdump: Remove stray get_crashkernel_region() declaration
  * x86: Support large number of memory ranges
  * Fix broken Xen support in configure.ac
  * kexec: extend the semantics of kexec_iomem_for_each_line
  * kexec: generalize and rename get_kernel_stext_sym()
  * arm64: identify PHYS_OFFSET correctly
  * arm64: change return values on error to negative
  * arm64: kdump: identify memory regions
  * arm64: kdump: add elf core header segment
  * arm64: kdump: set up kernel image segment
  * arm64: kdump: set up other segments
  * arm64: kdump: add DT properties to crash dump kernel's dtb
  * arm64: kdump: Add support for binary image files
  * Handle additional e820 memmap type strings

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/kexec-tools/+bug/1713940/+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 1705748] Re: Samsung SSD 960 EVO 500GB refused to change power state

[Kai-Heng Feng]

But no more "nvme :01:00.0: Refused to change power state, currently
in D3"?

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

Title:
  Samsung SSD 960 EVO 500GB refused to change power state

Status in linux package in Ubuntu:
  In Progress

Bug description:
  Originally thought my issue was same as this:
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1678184
  but requested to report as separate bug

  System becomes unusable at seemingly random times but especially after
  resume from suspend due to disk 'disappearing' becoming inaccessible,
  with hundreds of I/O errors logged.

  After viewing the above bug report yesterday as a quick temporary fix I added 
kernel param, updated grub, etc with:
  GRUB_CMDLINE_LINUX_DEFAULT="nvme_core.default_ps_max_latency_us=0"

  System appears to have been stable for the last day, but is presumably
  using more power than it should.

  System, drive details below:

  M2 nvme drive: Samsung SSD 960 EVO 500GB

  Ubuntu 4.10.0-26.30~16.04.1-generic 4.10.17

  M/B Asus Prime B350m-A
  Ryzen 1600 cpu

  Jul 20 16:32:59 phs08 kernel: [ 190.893571] INVALID_DEVICE_REQUEST 
device=00:00.0 address=0xfffdf800 flags=0x0a00]
  Jul 20 16:33:05 phs08 kernel: [ 197.010928] nvme :01:00.0: controller is 
down; will reset: CSTS=0x, PCI_STATUS=0x
  Jul 20 16:33:05 phs08 kernel: [ 197.046980] pci_raw_set_power_state: 4 
callbacks suppressed
  Jul 20 16:33:05 phs08 kernel: [ 197.046985] nvme :01:00.0: Refused to 
change power state, currently in D3
  Jul 20 16:33:05 phs08 kernel: [ 197.047163] nvme nvme0: Removing after probe 
failure status: -19
  Jul 20 16:33:05 phs08 kernel: [ 197.047182] nvme0n1: detected capacity change 
from 500107862016 to 0
  Jul 20 16:33:05 phs08 kernel: [ 197.047793] blk_update_request: I/O error, 
dev nvme0n1, sector 0

  
  nvme list

  /dev/nvme0n1 S3EUNX0J305518L Samsung SSD 960 EVO 500GB 1.2 1 125.20 GB
  / 500.11 GB 512 B + 0 B 2B7QCXE7

  sudo nvme id-ctrl /dev/nvme0

  NVME Identify Controller:
  vid : 0x144d
  ssvid : 0x144d
  sn : S3EUNX0J305518L
  mn : Samsung SSD 960 EVO 500GB
  fr : 2B7QCXE7
  rab : 2
  ieee : 002538
  cmic : 0
  mdts : 9
  cntlid : 2
  ver : 10200
  rtd3r : 7a120
  rtd3e : 4c4b40
  oaes : 0
  oacs : 0x7
  acl : 7
  aerl : 3
  frmw : 0x16
  lpa : 0x3
  elpe : 63
  npss : 4
  avscc : 0x1
  apsta : 0x1
  wctemp : 350
  cctemp : 352
  mtfa : 0
  hmpre : 0
  hmmin : 0
  tnvmcap : 500107862016
  unvmcap : 0
  rpmbs : 0
  sqes : 0x66
  cqes : 0x44
  nn : 1
  oncs : 0x1f
  fuses : 0
  fna : 0x5
  vwc : 0x1
  awun : 255
  awupf : 0
  nvscc : 1
  acwu : 0
  sgls : 0
  ps 0 : mp:6.04W operational enlat:0 exlat:0 rrt:0 rrl:0
rwt:0 rwl:0 idle_power:- active_power:-
  ps 1 : mp:5.09W operational enlat:0 exlat:0 rrt:1 rrl:1
rwt:1 rwl:1 idle_power:- active_power:-
  ps 2 : mp:4.08W operational enlat:0 exlat:0 rrt:2 rrl:2
rwt:2 rwl:2 idle_power:- active_power:-
  ps 3 : mp:0.0400W non-operational enlat:210 exlat:1500 rrt:3 rrl:3
rwt:3 rwl:3 idle_power:- active_power:-
  ps 4 : mp:0.0050W non-operational enlat:2200 exlat:6000 rrt:4 rrl:4
rwt:4 rwl:4 idle_power:- active_power:-
  --- 
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  drgrumpy   2192 F pulseaudio
   /dev/snd/pcmC1D0p:   drgrumpy   2192 F...m pulseaudio
   /dev/snd/controlC1:  drgrumpy   2192 F pulseaudio
  DistroRelease: Linux 18.2
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=a6896cdd-6bac-4e7f-9e13-55460859c3ec
  InstallationDate: Installed on 2017-07-06 (15 days ago)
  InstallationMedia: Linux Mint 18.2 "Sonya" - Release amd64 20170628
  IwConfig:
   lono wireless extensions.
   
   enp37s0   no wireless extensions.
  MachineType: System manufacturer System Product Name
  Package: linux (not installed)
  ProcEnviron:
   LANGUAGE=en_GB:en
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-26-generic 
root=UUID=f7ae652b-cbf6-48b8-bc6a-d3963957ab57 ro 
nvme_core.default_ps_max_latency_us=0
  ProcVersionSignature: Ubuntu 4.10.0-26.30~16.04.1-generic 4.10.17
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-26-generic N/A
   linux-backports-modules-4.10.0-26-generic  N/A
   linux-firmware 1.157.11
  RfKill:
   
  Tags:  sonya
  Uname: Linux 4.10.0-26-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 06/20/2017
  dmi.bios.vendor: American Megatrends Inc.
  

[Kernel-packages] [Bug 1708399] Re: kernel panic -not syncing: Fatal exception: panic_on_oops

[Stefan Bader]

Replaced the packages at http://people.canonical.com/~smb/lp1708399/
with the latest kernel and the three suggested patche on top.

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

Title:
  kernel panic -not syncing: Fatal exception: panic_on_oops

Status in Ubuntu on IBM z Systems:
  New
Status in linux package in Ubuntu:
  New

Bug description:
  == Comment: #0 - QI YE  - 2017-08-02 04:11:25 ==
  ---Problem Description---
  Ubuntu got kernel panic

  ---uname output---
  #110-Ubuntu SMP Tue Jul 18 12:56:43 UTC 2017 s390x s390x s390x GNU/Linux
   
  ---Debugger Data---
  PID: 10991  TASK: 19872a0e8 CPU: 2   COMMAND: "hyperkube"
   LOWCORE INFO:
-psw  : 0x0004c0018000 0x00115fa6
-function : pcpu_delegate at 115fa6
-prefix   : 0x7fe42000
-cpu timer: 0x7ffab2827828aa50
-clock cmp: 0xd2eb8b31445e4200
-general registers:
   0x0004e001 0x001283b6
   0xc001 0x8380fcb8
   0x00115f9e 0x0056f6e2
   0x0004 0x00cf9070
   0x0001f3bfc000 0x00112fd8
   0x0001c72bb400 0x0002
   0x7fffc000 0x007c9ef0
   0x00115f9e 0x8380fc18
-access registers:
   0x03ff 0x7910 00 00
   00 00 00 00
   00 00 00 00
   00 00 00 00
-control registers:
   0x14066a12 0x7e6d81c7
   0x00011140 00
   0x2aef 0x0400
   0x5000 0x7e6d81c7
   00 00
   00 00
   00 0x00cfc007
   0xdb00 0x00011280
-floating point registers:
   0x409c7e258000 0x401de4e0
   00 0x3fd24407ab0e073a
   0x3ff0 0x3fee
   0x3fef218f8a7a41a0 0x3fee
   0x0080 00
   0x03ff7f80 0x02aa4940e9e0
   0xd401 0x03ffe81fe110
   00 0x03fff2cfe638

   #0 [8380fc78] smp_find_processor_id at 1160f8
   #1 [8380fc90] machine_kexec at 1135d4
   #2 [8380fcb8] crash_kexec at 1fbb8a
   #3 [8380fd88] panic at 27d0e0
   #4 [8380fe28] die at 1142cc
   #5 [8380fe90] do_low_address at 12215e
   #6 [8380fea8] pgm_check_handler at 7c2ab4
   PSW:  070520018000 02aa267e0e42 (user space)
   GPRS:   02aa2c4fd690 0001
 02aa2c4fd690 03ff7fffee38  0002
 00029c0f 00c42001ea00 0001 0001
 00c42001c5c8 00c42082c1a0 02aa2666325e 03ff7fffed90 
   
  Contact Information = Chee Ye / y...@cn.ibm.com 
   
  Stack trace output:
   no
   
  Oops output:
   [43200.761465] docker0: port 10(vethb9132e9) entered forwarding state
  [50008.560926] hrtimer: interrupt took 1698076 ns
  [123483.768984] systemd[1]: apt-daily.timer: Adding 7h 34min 22.582204s 
random time.
  [123483.930058] systemd[1]: apt-daily.timer: Adding 2h 18min 14.857162s 
random time.
  [123484.064879] systemd[1]: apt-daily.timer: Adding 10h 46min 2.301756s 
random time.
  [123484.824760] systemd[1]: apt-daily.timer: Adding 6h 16min 22.178655s 
random time.
  [153113.703126] conntrack: generic helper won't handle protocol 47. Please 
consider loading the specific helper module.
  [477085.704538] Low-address protection: 0004 ilc:2 [#1] SMP
  [477085.704551] Modules linked in: xt_physdev veth xt_recent xt_comment 
xt_mark xt_nat ipt_MASQUERADE nf_nat_masquerade_ipv4 xfrm_user xfrm_algo 
iptable_nat nf_nat_ipv4 xt_addrtype nf_nat br_netfilter bridge stp llc aufs 
ipt_REJECT nf_reject_ipv4 xt_tcpudp nf_conntrack_ipv4 nf_defrag_ipv4 
xt_conntrack nf_conntrack iptable_filter ip_tables x_tables ghash_s390 prng 
aes_s390 des_s390 des_generic sha512_s390 qeth_l2 sha256_s390 qeth sha1_s390 
qdio sha_common ccwgroup vmur dasd_eckd_mod dasd_mod
  [477085.705522] CPU: 2 PID: 10991 Comm: hyperkube Not tainted 
4.4.0-87-generic #110-Ubuntu
  [477085.705525] task: 00019872a0e8 ti: 8380c000 task.ti: 
8380c000
  [477085.705529] User PSW : 070520018000 02aa267e0e42
  [477085.705532]R:0 T:1 IO:1 EX:1 Key:0 M:1 W:0 P:1 AS:0 CC:2 PM:0 
EA:3
  User GPRS:   02aa2c4fd690 
0001
  [477085.705539]02aa2c4fd690 03ff7fffee38  
0002
  [477085.705553]00029c0f 00c42001ea00 0001 
0001
  [477085.705554]00c42001c5c8 00c42082c1a0 02aa2666325e 
03ff7fffed9

[Kernel-packages] [Bug 1683982] Re: net/ipv4: original ingress device index set as the loopback interface.

[Eduardo Gonzalez]

Removing kolla as affected project, the fix is merged in packagers and
we consume their packages.

** No longer affects: kolla

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

Title:
  net/ipv4: original ingress device index set as the loopback interface.

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Yakkety:
  Fix Released
Status in linux source package in Zesty:
  Fix Released

Bug description:
  [Environment]

  # lsb_release -a
  No LSB modules are available.
  Distributor ID: Ubuntu
  Description:Ubuntu 16.04.2 LTS
  Release:16.04
  Codename:   xenial

  # uname -a

  Linux juju-niedbalski-xenial-machine-12 4.8.0-46-generic
  #49~16.04.1-Ubuntu SMP Fri Mar 31 14:51:03 UTC 2017 x86_64 x86_64
  x86_64 GNU/Linux

  
  [Description]

  We identified a bug in one of the utilities provided by dnsmasq, the 
'dhcp_release' utility which
  is executed as part of the DHCP lease cleanup mechanism by Neutron once a 
network resource is freed.
  We noticed that some packets were discarded by the DHCP server (dnsmasq) in 
Ubuntu systems
  running a kernel >= 4.7. The reason was the ipi_ifindex field on the pktinfo 
was incorrectly assumed to be 1 (loopback),
  this causes the message to be ignored by the dnsmasq daemon since isn't the 
interface on which dnsmasq is bind to.

  (gdb) p *p.p 
  $4 = { 
  ipi_ifindex = 1, 
  ipi_spec_dst = { 
  s_addr = 34973888 
  }, 
  ipi_addr = { 
  s_addr = 34973888 
  } 
  } 

  (gdb) p ifr 
  $8 = {ifr_ifrn = {ifrn_name = "lo", '\000' }, 

  
  [Fix]

  Upstream commit:
  
https://github.com/torvalds/linux/commit/f0c16ba8933ed217c2688b277410b2a37ba81591

  [Test Case]

  1) Configure a dnsmasq instance to server DHCP

  (Example):

  $ sudo dnsmasq --no-hosts --no-resolv --strict-order --except-interface=lo 
--pid-file=/var/lib/neutron/dhcp/860b0cbb-37c3-4bcb-8345-52b942518dca/pid 
--dhcp-hostsfile=/var/lib/neutron/dhcp/860b0cbb-37c3-4bcb-8345-52b942518dca/host
 -
  
-addn-hosts=/var/lib/neutron/dhcp/860b0cbb-37c3-4bcb-8345-52b942518dca/addn_hosts
 
--dhcp-optsfile=/var/lib/neutron/dhcp/860b0cbb-37c3-4bcb-8345-52b942518dca/opts 
--dhcp-leasefile=/var/lib/neutron/dhcp/860b0cbb-37c3-4bcb-8345-52b942
  518dca/leases --dhcp-match=set:ipxe,175 --bind-interfaces 
--interface=ns-1cb1b7c7-c0 --dhcp-range=set:tag0,192.168.21.0,static,86400s 
--dhcp-option-force=option:mtu,1458 --dhcp-lease-max=256 
--conf-file=/etc/neutron/dnsmasq.conf --
  domain=openstacklocal

  2) Boot a VM or container on the bridge/interface on which dnsmasq is bind to.
  2) Use the dhcp_release utility to release the lease.

  (Example):
  $ sudo dhcp_release ns-1cb1b7c7-c0 192.168.21.8 fa:16:3e:f3:b2:fe

  The expected result: The lease is freed.
  Current results: dnsmasq ignored the DHCP Release message.

  [Fix]

  When we send a packet for our own local address on a non-loopback
  interface (e.g. eth0), due to the change had been introduced from
  commit 0b922b7 ("net: original ingress device index in PKTINFO"), the
  original ingress device index would be set as the loopback interface.

  *
  
https://github.com/torvalds/linux/commit/f0c16ba8933ed217c2688b277410b2a37ba81591

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1683982/+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 1713458] Re: linux-lts-trusty: 3.13.0-130.179~precise1 -proposed tracker

[Kleber Sacilotto de Souza]

** Summary changed:

- linux-lts-trusty:  -proposed tracker
+ linux-lts-trusty: 3.13.0-130.179~precise1 -proposed tracker

** Changed in: kernel-sru-workflow/prepare-package
   Status: Confirmed => In Progress

** Changed in: kernel-sru-workflow/prepare-package
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Kleber 
Sacilotto de Souza (kleber-souza)

** Changed in: kernel-sru-workflow/prepare-package-meta
   Status: New => In Progress

** Changed in: kernel-sru-workflow/prepare-package-meta
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Kleber 
Sacilotto de Souza (kleber-souza)

** Changed in: kernel-sru-workflow/prepare-package-signed
   Status: New => In Progress

** Changed in: kernel-sru-workflow/prepare-package-signed
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Kleber 
Sacilotto de Souza (kleber-souza)

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

Title:
  linux-lts-trusty: 3.13.0-130.179~precise1 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  New
Status in Kernel SRU Workflow prepare-package series:
  In Progress
Status in Kernel SRU Workflow prepare-package-meta series:
  In Progress
Status in Kernel SRU Workflow prepare-package-signed series:
  In Progress
Status in Kernel SRU Workflow promote-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-lts-trusty package in Ubuntu:
  Invalid
Status in linux-lts-trusty source package in Precise:
  Confirmed

Bug description:
  This bug is for tracking the  upload package.
  This bug will contain status and testing results related to that
  upload.

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  kernel-stable-master-bug: 1713456
  phase: Packaging

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1713458/+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 1713940] Re: kexec-tools 2.0.14 fails to load 4.12+ crash kernels

[Andy Whitcroft]

The delta indeed does appear to majority bug fixes, the only new
features look to be arm64 crash support which we were already carrying
in the ubuntu delta so can be ignored.  Sponsored to artful.

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

Title:
  kexec-tools 2.0.14 fails to load 4.12+ crash kernels

Status in kexec-tools package in Ubuntu:
  In Progress

Bug description:
  Starting with 4.12 kernels, kexec-tools cannot load a crash kernel
  because ELF core parsing fails with errors like:

Unknown type (Reserved) while parsing /sys/firmware/memmap/5/type.
Please report this as bug. Using RANGE_RESERVED now.
...
ELF core (kcore) parse failed
Cannot load /var/lib/kdump/vmlinuz

  The issue is fixed upstream in kexec-tools 2.0.15 (Debian is still at
  2.0.14)

  The complete changes list between 2.0.14 and 2.0.15 shows mostly bug
  fixes and in fact all additional patches in debian/patches which are
  Ubuntu delta, have moved into upstream 2.0.15. So we could drop all
  those while moving to the new version.

  * ppc64: Reduce number of ELF LOAD segments
  * kexec: Increase the upper limit for RAM segments
  * alpha: add missing __NR_kexec_load definition
  * kexec: implemented XEN KEXEC STATUS to determine if an image is loaded
  * kexec: Remove redundant space from help message
  * purgatory: Add purgatory.map and purgatory.ro.sym to clean recipe
  * kexec: Add option to get crash kernel region size
  * crashdump/arm: Add get_crash_kernel_load_range() function
  * crashdump/arm64: Add get_crash_kernel_load_range() function
  * crashdump/cris: Add get_crash_kernel_load_range() function
  * crashdump/ia64: Add get_crash_kernel_load_range() function
  * crashdump/m68k: Add get_crash_kernel_load_range() function
  * crashdump/mips: Add get_crash_kernel_load_range() function
  * crashdump/ppc: Add get_crash_kernel_load_range() function
  * crashdump/ppc64: Add get_crash_kernel_load_range() function
  * crashdump/s390: Add get_crash_kernel_load_range() function
  * crashdump/sh: Add get_crash_kernel_load_range() function
  * gitignore: add two generated files in purgatory
  * Only print debug message when failed to serach for kernel symbol from
/proc/kallsyms
  * build_mem_phdrs(): check if p_paddr is invalid
  * uImage: fix realloc() pointer confusion
  * uImage: Fix uImage_load() for little-endian machines
  * uImage: Add new IH_ARCH_xxx definitions
  * uImage: use 'char *' instead of 'unsigned char *' for uImage_load()
  * uImage: use 'char *' instead of 'unsigned char *' for uImage_probe()
  * arm64: add uImage support
  * vmcore-dmesg: Define _GNU_SOURCE
  * Don't use %L width specifier with integer values
  * x86/x86_64: Fix format warning with die()
  * ppc: Fix format warning with die()
  * crashdump: Remove stray get_crashkernel_region() declaration
  * x86: Support large number of memory ranges
  * Fix broken Xen support in configure.ac
  * kexec: extend the semantics of kexec_iomem_for_each_line
  * kexec: generalize and rename get_kernel_stext_sym()
  * arm64: identify PHYS_OFFSET correctly
  * arm64: change return values on error to negative
  * arm64: kdump: identify memory regions
  * arm64: kdump: add elf core header segment
  * arm64: kdump: set up kernel image segment
  * arm64: kdump: set up other segments
  * arm64: kdump: add DT properties to crash dump kernel's dtb
  * arm64: kdump: Add support for binary image files
  * Handle additional e820 memmap type strings

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/kexec-tools/+bug/1713940/+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 1705748] Re: Samsung SSD 960 EVO 500GB refused to change power state

[Steve Roberts]

Yes, correct I just searched the kernel log and no more 
"...Refused to change..."

since I booted with:

Command line: BOOT_IMAGE=/vmlinuz-4.13.0-6-generic root=UUID=f7ae652b-
cbf6-48b8-bc6a-d3963957ab57 ro nvme_core.default_ps_max_latency_us=1500

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

Title:
  Samsung SSD 960 EVO 500GB refused to change power state

Status in linux package in Ubuntu:
  In Progress

Bug description:
  Originally thought my issue was same as this:
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1678184
  but requested to report as separate bug

  System becomes unusable at seemingly random times but especially after
  resume from suspend due to disk 'disappearing' becoming inaccessible,
  with hundreds of I/O errors logged.

  After viewing the above bug report yesterday as a quick temporary fix I added 
kernel param, updated grub, etc with:
  GRUB_CMDLINE_LINUX_DEFAULT="nvme_core.default_ps_max_latency_us=0"

  System appears to have been stable for the last day, but is presumably
  using more power than it should.

  System, drive details below:

  M2 nvme drive: Samsung SSD 960 EVO 500GB

  Ubuntu 4.10.0-26.30~16.04.1-generic 4.10.17

  M/B Asus Prime B350m-A
  Ryzen 1600 cpu

  Jul 20 16:32:59 phs08 kernel: [ 190.893571] INVALID_DEVICE_REQUEST 
device=00:00.0 address=0xfffdf800 flags=0x0a00]
  Jul 20 16:33:05 phs08 kernel: [ 197.010928] nvme :01:00.0: controller is 
down; will reset: CSTS=0x, PCI_STATUS=0x
  Jul 20 16:33:05 phs08 kernel: [ 197.046980] pci_raw_set_power_state: 4 
callbacks suppressed
  Jul 20 16:33:05 phs08 kernel: [ 197.046985] nvme :01:00.0: Refused to 
change power state, currently in D3
  Jul 20 16:33:05 phs08 kernel: [ 197.047163] nvme nvme0: Removing after probe 
failure status: -19
  Jul 20 16:33:05 phs08 kernel: [ 197.047182] nvme0n1: detected capacity change 
from 500107862016 to 0
  Jul 20 16:33:05 phs08 kernel: [ 197.047793] blk_update_request: I/O error, 
dev nvme0n1, sector 0

  
  nvme list

  /dev/nvme0n1 S3EUNX0J305518L Samsung SSD 960 EVO 500GB 1.2 1 125.20 GB
  / 500.11 GB 512 B + 0 B 2B7QCXE7

  sudo nvme id-ctrl /dev/nvme0

  NVME Identify Controller:
  vid : 0x144d
  ssvid : 0x144d
  sn : S3EUNX0J305518L
  mn : Samsung SSD 960 EVO 500GB
  fr : 2B7QCXE7
  rab : 2
  ieee : 002538
  cmic : 0
  mdts : 9
  cntlid : 2
  ver : 10200
  rtd3r : 7a120
  rtd3e : 4c4b40
  oaes : 0
  oacs : 0x7
  acl : 7
  aerl : 3
  frmw : 0x16
  lpa : 0x3
  elpe : 63
  npss : 4
  avscc : 0x1
  apsta : 0x1
  wctemp : 350
  cctemp : 352
  mtfa : 0
  hmpre : 0
  hmmin : 0
  tnvmcap : 500107862016
  unvmcap : 0
  rpmbs : 0
  sqes : 0x66
  cqes : 0x44
  nn : 1
  oncs : 0x1f
  fuses : 0
  fna : 0x5
  vwc : 0x1
  awun : 255
  awupf : 0
  nvscc : 1
  acwu : 0
  sgls : 0
  ps 0 : mp:6.04W operational enlat:0 exlat:0 rrt:0 rrl:0
rwt:0 rwl:0 idle_power:- active_power:-
  ps 1 : mp:5.09W operational enlat:0 exlat:0 rrt:1 rrl:1
rwt:1 rwl:1 idle_power:- active_power:-
  ps 2 : mp:4.08W operational enlat:0 exlat:0 rrt:2 rrl:2
rwt:2 rwl:2 idle_power:- active_power:-
  ps 3 : mp:0.0400W non-operational enlat:210 exlat:1500 rrt:3 rrl:3
rwt:3 rwl:3 idle_power:- active_power:-
  ps 4 : mp:0.0050W non-operational enlat:2200 exlat:6000 rrt:4 rrl:4
rwt:4 rwl:4 idle_power:- active_power:-
  --- 
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  drgrumpy   2192 F pulseaudio
   /dev/snd/pcmC1D0p:   drgrumpy   2192 F...m pulseaudio
   /dev/snd/controlC1:  drgrumpy   2192 F pulseaudio
  DistroRelease: Linux 18.2
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=a6896cdd-6bac-4e7f-9e13-55460859c3ec
  InstallationDate: Installed on 2017-07-06 (15 days ago)
  InstallationMedia: Linux Mint 18.2 "Sonya" - Release amd64 20170628
  IwConfig:
   lono wireless extensions.
   
   enp37s0   no wireless extensions.
  MachineType: System manufacturer System Product Name
  Package: linux (not installed)
  ProcEnviron:
   LANGUAGE=en_GB:en
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-26-generic 
root=UUID=f7ae652b-cbf6-48b8-bc6a-d3963957ab57 ro 
nvme_core.default_ps_max_latency_us=0
  ProcVersionSignature: Ubuntu 4.10.0-26.30~16.04.1-generic 4.10.17
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-26-generic N/A
   linux-backports-modules-4.10.0-26-generic  N/A
   linux-firmware 1.157.11
  RfKill:
   
  Tags:  sonya
  Uname: Linux 4.10.0-26-generic x86_64
  UpgradeSta

[Kernel-packages] [Bug 1704363] Re: Add firmware for Redpine 9113 chipset

[Shrirang Bagul]

@Chris,

The linux-firmware package was upgraded to version 1.157.12 by following
instructions in comment #3 on HW platform which requires the latest
RS9113 firmware.

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

Title:
  Add firmware for Redpine 9113 chipset

Status in linux-firmware package in Ubuntu:
  Invalid
Status in linux-firmware source package in Xenial:
  Fix Committed

Bug description:
  SRU Justification

  Impact: The redpine driver in xenial has been updated, and a
  corresponding firmware update is also required.

  Fix: Add new firmware files.

  Test case: Test with affected hw and with a kernel which has the
  driver update.

  Regression potential: These are new files used by a single driver, so
  no regressions are possible outside of that driver.

  ---

  Latest firmware images provided by Redpine in 1.2 production release
  are updated to ubuntu's linux-firmware.git

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1704363/+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 1713940] Re: kexec-tools 2.0.14 fails to load 4.12+ crash kernels

[Launchpad Bug Tracker]

This bug was fixed in the package kexec-tools - 1:2.0.15-0ubuntu1

---
kexec-tools (1:2.0.15-0ubuntu1) artful; urgency=medium

  * New upstream version (LP: #1713940):
- Modified:
  - distclean_fix.patch
Hunk which modified purgatory makefile went upstream
- Dropped (already upstream):
  - format-security.patch
  - kexec-Increase-the-upper-limit-for-RAM-segments.patch
  - ppc64-Reduce-number-of-ELF-LOAD-segments.patch
  - 0001-kexec-extend-the-semantics-of-kexec_iomem_for_each_l.patch
  - 0002-kexec-generalize-and-rename-get_kernel_stext_sym.patch
  - 0003-arm64-identify-PHYS_OFFSET-correctly.patch
  - 0004-arm64-change-return-values-on-error-to-negative.patch
  - 0005-arm64-kdump-identify-memory-regions.patch
  - 0006-arm64-kdump-add-elf-core-header-segment.patch
  - 0007-arm64-kdump-set-up-kernel-image-segment.patch
  - 0008-arm64-kdump-set-up-other-segments.patch
  - 0009-arm64-kdump-add-DT-properties-to-crash-dump-kernel-s.patch
  - 0010-arm64-kdump-Add-support-for-binary-image-files.patch

 -- Stefan Bader   Wed, 30 Aug 2017 10:02:25
+0200

** Changed in: kexec-tools (Ubuntu)
   Status: In Progress => Fix Released

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

Title:
  kexec-tools 2.0.14 fails to load 4.12+ crash kernels

Status in kexec-tools package in Ubuntu:
  Fix Released

Bug description:
  Starting with 4.12 kernels, kexec-tools cannot load a crash kernel
  because ELF core parsing fails with errors like:

Unknown type (Reserved) while parsing /sys/firmware/memmap/5/type.
Please report this as bug. Using RANGE_RESERVED now.
...
ELF core (kcore) parse failed
Cannot load /var/lib/kdump/vmlinuz

  The issue is fixed upstream in kexec-tools 2.0.15 (Debian is still at
  2.0.14)

  The complete changes list between 2.0.14 and 2.0.15 shows mostly bug
  fixes and in fact all additional patches in debian/patches which are
  Ubuntu delta, have moved into upstream 2.0.15. So we could drop all
  those while moving to the new version.

  * ppc64: Reduce number of ELF LOAD segments
  * kexec: Increase the upper limit for RAM segments
  * alpha: add missing __NR_kexec_load definition
  * kexec: implemented XEN KEXEC STATUS to determine if an image is loaded
  * kexec: Remove redundant space from help message
  * purgatory: Add purgatory.map and purgatory.ro.sym to clean recipe
  * kexec: Add option to get crash kernel region size
  * crashdump/arm: Add get_crash_kernel_load_range() function
  * crashdump/arm64: Add get_crash_kernel_load_range() function
  * crashdump/cris: Add get_crash_kernel_load_range() function
  * crashdump/ia64: Add get_crash_kernel_load_range() function
  * crashdump/m68k: Add get_crash_kernel_load_range() function
  * crashdump/mips: Add get_crash_kernel_load_range() function
  * crashdump/ppc: Add get_crash_kernel_load_range() function
  * crashdump/ppc64: Add get_crash_kernel_load_range() function
  * crashdump/s390: Add get_crash_kernel_load_range() function
  * crashdump/sh: Add get_crash_kernel_load_range() function
  * gitignore: add two generated files in purgatory
  * Only print debug message when failed to serach for kernel symbol from
/proc/kallsyms
  * build_mem_phdrs(): check if p_paddr is invalid
  * uImage: fix realloc() pointer confusion
  * uImage: Fix uImage_load() for little-endian machines
  * uImage: Add new IH_ARCH_xxx definitions
  * uImage: use 'char *' instead of 'unsigned char *' for uImage_load()
  * uImage: use 'char *' instead of 'unsigned char *' for uImage_probe()
  * arm64: add uImage support
  * vmcore-dmesg: Define _GNU_SOURCE
  * Don't use %L width specifier with integer values
  * x86/x86_64: Fix format warning with die()
  * ppc: Fix format warning with die()
  * crashdump: Remove stray get_crashkernel_region() declaration
  * x86: Support large number of memory ranges
  * Fix broken Xen support in configure.ac
  * kexec: extend the semantics of kexec_iomem_for_each_line
  * kexec: generalize and rename get_kernel_stext_sym()
  * arm64: identify PHYS_OFFSET correctly
  * arm64: change return values on error to negative
  * arm64: kdump: identify memory regions
  * arm64: kdump: add elf core header segment
  * arm64: kdump: set up kernel image segment
  * arm64: kdump: set up other segments
  * arm64: kdump: add DT properties to crash dump kernel's dtb
  * arm64: kdump: Add support for binary image files
  * Handle additional e820 memmap type strings

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/kexec-tools/+bug/1713940/+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 1667750] Re: xhci_hcd: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 2 comp_code 13

[Johann Hartwig Hauschild]

Will do, we're verifying that it's not firmware-related.

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

Title:
  xhci_hcd: ERROR Transfer event TRB DMA ptr not part of current TD
  ep_index 2 comp_code 13

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Fix Released
Status in linux source package in Zesty:
  Fix Released
Status in linux source package in Artful:
  Fix Released
Status in linux package in Arch Linux:
  New
Status in linux package in Debian:
  New
Status in linux package in Fedora:
  Unknown

Bug description:
  [SRU Justification]

  [Impact] 
  Dell TB16 docking station has issue to use gigabit ethernet. The ethernet
  will disconnect unless it's changed to 100Mb/s.

  
  [Test Case]
  Download some big files from the web.
  User confirms the patch fixes the issue.

  [Regression Potential] 
  This patch only effects ASMEDIA's ASM1042A.
  The regression potential is low, also limited to the specific device.

  ---

  My system contains a Realtek Semiconductor Corp. RTL8153 Gigabit
  Ethernet Adapter which is on usb3 bus in my docking station (Dell
  TB16) which is attached to my laptop (Dell XPS9550) via Thunderbolt 3.

  I get usb related kernel error messages when I initiate a high speed
  transfer (by issuing wget http://cdimage.ubuntu.com/daily-live/current
  /zesty-desktop-amd64.iso) and the download fails.

  This does not happened when the Ethernet adapter is connected to a
  100Mb/s switch, but only when connected to 1000Mb/s. It also does not
  happened with slow traffic (e.g. web page browsing). This is not a new
  bug with kernel 4.10, but has been going on since at least 4.7 and
  maybe (probably?) since forever. I'm aware of several others with this
  configuration (RTL8153 on usb3 behind thunderbolt 3) that have the
  same issue. This bug is also not specific to Ubuntu; I also get it on
  Arch Linux. I've also tested and seen this bug with several different
  models of thunderbolt 3 docks.

  Here are the relevant kernel log messages:

  Feb 24 16:42:38 ubuntu kernel: xhci_hcd :0e:00.0: ERROR Transfer event 
TRB DMA ptr not part of current TD ep_index 2 comp_code 13
  Feb 24 16:42:38 ubuntu kernel: xhci_hcd :0e:00.0: Looking for event-dma 
0004777d9010 trb-start 000475a14fe0 trb-end 000475a14fe0 seg-start 
000475a14000 seg-end 000475a14ff0
  Feb 24 16:42:38 ubuntu kernel: xhci_hcd :0e:00.0: ERROR Transfer event 
TRB DMA ptr not part of current TD ep_index 2 comp_code 13
  Feb 24 16:42:38 ubuntu kernel: xhci_hcd :0e:00.0: Looking for event-dma 
0004777d9020 trb-start 000475a14fe0 trb-end 000475a14fe0 seg-start 
000475a14000 seg-end 000475a14ff0
  Feb 24 16:42:38 ubuntu kernel: xhci_hcd :0e:00.0: ERROR Transfer event 
TRB DMA ptr not part of current TD ep_index 2 comp_code 13
  Feb 24 16:42:38 ubuntu kernel: xhci_hcd :0e:00.0: Looking for event-dma 
0004777d9030 trb-start 000475a14fe0 trb-end 000475a14fe0 seg-start 
000475a14000 seg-end 000475a14ff0
  Feb 24 16:42:38 ubuntu kernel: xhci_hcd :0e:00.0: ERROR Transfer event 
TRB DMA ptr not part of current TD ep_index 2 comp_code 13
  Feb 24 16:42:38 ubuntu kernel: xhci_hcd :0e:00.0: Looking for event-dma 
0004777d9040 trb-start 000475a14fe0 trb-end 000475a14fe0 seg-start 
000475a14000 seg-end 000475a14ff0
  Feb 24 16:42:38 ubuntu kernel: xhci_hcd :0e:00.0: ERROR Transfer event 
TRB DMA ptr not part of current TD ep_index 2 comp_code 13
  Feb 24 16:42:38 ubuntu kernel: xhci_hcd :0e:00.0: Looking for event-dma 
0004777d9050 trb-start 000475a14fe0 trb-end 000475a14fe0 seg-start 
000475a14000 seg-end 000475a14ff0
  Feb 24 16:42:38 ubuntu kernel: xhci_hcd :0e:00.0: ERROR Transfer event 
TRB DMA ptr not part of current TD ep_index 2 comp_code 13
  Feb 24 16:42:38 ubuntu kernel: xhci_hcd :0e:00.0: Looking for event-dma 
0004777d9060 trb-start 000475a14fe0 trb-end 000475a14fe0 seg-start 
000475a14000 seg-end 000475a14ff0
  Feb 24 16:42:39 ubuntu kernel: xhci_hcd :0e:00.0: ERROR Transfer event 
TRB DMA ptr not part of current TD ep_index 2 comp_code 13
  Feb 24 16:42:39 ubuntu kernel: xhci_hcd :0e:00.0: Looking for event-dma 
0004777d9070 trb-start 000475a14fe0 trb-end 000475a14fe0 seg-start 
000475a14000 seg-end 000475a14ff0
  Feb 24 16:42:39 ubuntu kernel: xhci_hcd :0e:00.0: ERROR Transfer event 
TRB DMA ptr not part of current TD ep_index 2 comp_code 13
  Feb 24 16:42:39 ubuntu kernel: xhci_hcd :0e:00.0: Looking for event-dma 
0004777d9080 trb-start 000475a14fe0 trb-end 000475a14fe0 seg-start 
000475a14000 seg-end 000475a14ff0
  Feb 24 16:43:06 ubuntu kernel: r8152 4-1.2:1.0 enx204747f8f471: Tx timeout
  Feb 24 16:43:06 ubuntu ker

[Kernel-packages] [Bug 264789] I guess There is it finally

[Marietto64]

Content-Transfer-Encoding: base64
Content-Type: text/plain; charset="utf-8"

SGV5LCANCg0KWW91IG1heSAgYWxyZWFkeSBrbm93IEkgYW0gIGxvb2tpbmcgIGZvciBzb21lIHN0
dWZmICBmb3IgIGEgbG9uZyBwZXJpb2QsICBhbmQgIEkgdGhpbmsgSSd2ZSBmb3VuZCBpdCBmaW5h
bGx5LCBzaW1wbHkgIHRha2UgIGEgbG9vayBodHRwOi8vZGF4aWFzb2Z0LmNvbS9zaGlwLnBocD9V
RTh5TmpRM09EbEFZblZuY3k1c1lYVnVZMmh3WVdRdWJtVjANCg0KV2FybSByZWdhcmRzLCBNYXJp
byBQaWNjb2xpDQoNCg==

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

Title:
  USB Hard Drive Not Accessible, vol_id hangs

Status in Linux:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Intrepid:
  Invalid

Bug description:
  I updated to 2.6.27-2 today, and one of my hard drives is no longer
  recognized. It is in a Vantec NexStar GX enclosure, and was working
  fine on .26, and continues to work fine on a Hardy machine. Here is
  the dmesg for it:

  [ 6722.944029] usb 5-5: new high speed USB device using ehci_hcd and address 
27
  [ 6723.077863] usb 5-5: configuration #1 chosen from 1 choice
  [ 6723.079511] hub 5-5:1.0: USB hub found
  [ 6723.080345] hub 5-5:1.0: 4 ports detected
  [ 6732.712034] usb 5-5: reset high speed USB device using ehci_hcd and 
address 27
  [ 6733.124011] usb 5-5.1: new high speed USB device using ehci_hcd and 
address 28
  [ 6733.364598] usb 5-5.1: configuration #1 chosen from 1 choice
  [ 6733.365180] scsi17 : SCSI emulation for USB Mass Storage devices
  [ 6733.365818] usb-storage: device found at 28
  [ 6733.365830] usb-storage: waiting for device to settle before scanning
  [ 6738.364276] usb-storage: device scan complete
  [ 6738.361002] scsi 17:0:0:0: Direct-Access ST340063 2A   
3.04 PQ: 0 ANSI: 0
  [ 6738.361002] sd 17:0:0:0: [sdm] 781422769 512-byte hardware sectors (400088 
MB)
  [ 6738.361002] sd 17:0:0:0: [sdm] Write Protect is off
  [ 6738.361002] sd 17:0:0:0: [sdm] Mode Sense: 03 00 00 00
  [ 6738.361002] sd 17:0:0:0: [sdm] Assuming drive cache: write through
  [ 6738.361002] sd 17:0:0:0: [sdm] 781422769 512-byte hardware sectors (400088 
MB)
  [ 6738.370354] sd 17:0:0:0: [sdm] Write Protect is off
  [ 6738.370362] sd 17:0:0:0: [sdm] Mode Sense: 03 00 00 00
  [ 6738.370365] sd 17:0:0:0: [sdm] Assuming drive cache: write through
  [ 6738.371516]  sdm: sdm1
  [ 6738.418089] sd 17:0:0:0: [sdm] Attached SCSI disk
  [ 6738.418995] sd 17:0:0:0: Attached scsi generic sg8 type 0
  [ 6738.656598] sd 17:0:0:0: [sdm] Sense Key : No Sense [current] 
  [ 6738.656614] sd 17:0:0:0: [sdm] Add. Sense: No additional sense information

  From there, the last 2 lines about Sense Key and Add Sense repeat over
  and over again.

  The 4 port hub that is a part of the enclosure continues to work fine
  though, with a floppy drive, a printer, and another hard drive. I have
  a Vantec NexStar 3 enclosure as well, and it is working just fine.
  Dmesg for the working enclosure:

  [ 4281.996024] usb 5-3: new high speed USB device using ehci_hcd and address 
19
  [ 4282.131863] usb 5-3: configuration #1 chosen from 1 choice
  [ 4282.133222] scsi12 : SCSI emulation for USB Mass Storage devices
  [ 4282.133561] usb-storage: device found at 19
  [ 4282.133566] usb-storage: waiting for device to settle before scanning
  [ 4287.132002] usb-storage: device scan complete
  [ 4287.136004] scsi 12:0:0:0: Direct-Access ST375064 0AS  
 PQ: 0 ANSI: 2
  [ 4287.138368] sd 12:0:0:0: [sdi] 1465149168 512-byte hardware sectors 
(750156 MB)
  [ 4287.144790] sd 12:0:0:0: [sdi] Write Protect is off
  [ 4287.144800] sd 12:0:0:0: [sdi] Mode Sense: 38 00 00 00
  [ 4287.144804] sd 12:0:0:0: [sdi] Assuming drive cache: write through
  [ 4287.152388] sd 12:0:0:0: [sdi] 1465149168 512-byte hardware sectors 
(750156 MB)
  [ 4287.154966] sd 12:0:0:0: [sdi] Write Protect is off
  [ 4287.154975] sd 12:0:0:0: [sdi] Mode Sense: 38 00 00 00
  [ 4287.154979] sd 12:0:0:0: [sdi] Assuming drive cache: write through
  [ 4287.154988]  sdi: sdi1
  [ 4287.176965] sd 12:0:0:0: [sdi] Attached SCSI disk
  [ 4287.177173] sd 12:0:0:0: Attached scsi generic sg7 type 0
  [ 4289.129138] kjournald starting.  Commit interval 5 seconds
  [ 4289.130101] EXT3 FS on sdi1, internal journal
  [ 4289.130110] EXT3-fs: mounted filesystem with ordered data mode.

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/264789/+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 1713997] [NEW] kexec-tools should not ask to handle reboots

[Juerg Haefliger]

Public bug reported:

Reboots via kexec-tools are only supported on SysV init systems. With
systemd the only supported init system by now, kexec-tools should no
longer ask (during installation) if reboots should be handled by kexec-
tools.

There should be no user interaction required when installing the
package.

$ lsb_release -rd
Description:Ubuntu Artful Aardvark (development branch)
Release:17.10

$ apt-cache policy kexec-tools
kexec-tools:
  Installed: 1:2.0.15-0ubuntu1
  Candidate: 1:2.0.15-0ubuntu1
  Version table:
 *** 1:2.0.15-0ubuntu1 500
500 http://archive.ubuntu.com/ubuntu artful/main amd64 Packages
100 /var/lib/dpkg/status

** Affects: kexec-tools (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  kexec-tools should not ask to handle reboots

Status in kexec-tools package in Ubuntu:
  New

Bug description:
  Reboots via kexec-tools are only supported on SysV init systems. With
  systemd the only supported init system by now, kexec-tools should no
  longer ask (during installation) if reboots should be handled by
  kexec-tools.

  There should be no user interaction required when installing the
  package.

  $ lsb_release -rd
  Description:  Ubuntu Artful Aardvark (development branch)
  Release:  17.10

  $ apt-cache policy kexec-tools
  kexec-tools:
Installed: 1:2.0.15-0ubuntu1
Candidate: 1:2.0.15-0ubuntu1
Version table:
   *** 1:2.0.15-0ubuntu1 500
  500 http://archive.ubuntu.com/ubuntu artful/main amd64 Packages
  100 /var/lib/dpkg/status

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/kexec-tools/+bug/1713997/+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 1713535] Re: No /dev/watchdog on NUC6CAYS devices with iTCO_wdt

[Olivier Louvignes]

I've just installed v4.13-rc7 and no more luck .

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

** Tags added: kernel-bug-exists-upstream

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

Title:
  No /dev/watchdog on NUC6CAYS devices with iTCO_wdt

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  It looks like iTCO_wdt won't properly setup a /dev/watchdog device on
  Intel recent Celeron NUCs (NUC6CAYS).

  ```
  # uname -a
  Linux player-ef15 4.11.0-14-generic #20~16.04.1-Ubuntu SMP Wed Aug 9 09:06:22 
UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
  # lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 16.04.3 LTS
  Release:  16.04
  Codename: xenial
  ```

  Modules are properly loaded (but looks like it is not used)

  ```
  # lsmod | grep -e dog -e wdt
  iTCO_wdt   16384  0
  iTCO_vendor_support16384  1 iTCO_wdt
  ```

  No device found in kernel.log:
  ```
  Aug 28 18:49:56 player-ef15 kernel: [   14.192689] iTCO_vendor_support: 
vendor-support=0
  Aug 28 18:49:56 player-ef15 kernel: [   14.198585] iTCO_wdt: Intel TCO 
WatchDog Timer Driver v1.11
  ```

  No device found by the service:

  ```
  # service watchdog status
  ● watchdog.service - watchdog daemon
     Loaded: loaded (/lib/systemd/system/watchdog.service; enabled; vendor 
preset: enabled)
     Active: active (running) since lun. 2017-08-28 18:49:56 CEST; 17s ago
    Process: 2763 ExecStart=/bin/sh -c [ $run_watchdog != 1 ] || exec 
/usr/sbin/watchdog $watchdog_options (code=exited, status=0/SUCCESS)
    Process: 2758 ExecStartPre=/bin/sh -c [ -z "${watchdog_module}" ] || [ 
"${watchdog_module}" = "none" ] || /sbin/modprobe $watchdog_module 
(code=exited, status=0/SUCCESS)
   Main PID: 2768 (watchdog)
  Tasks: 1
     Memory: 732.0K
    CPU: 13ms
     CGroup: /system.slice/watchdog.service
     └─2768 /usr/sbin/watchdog

  août 28 18:49:56 player-ef15 systemd[1]: Started watchdog daemon.
  août 28 18:49:56 player-ef15 watchdog[2768]: starting daemon (5.14):
  août 28 18:49:56 player-ef15 watchdog[2768]: int=1s realtime=yes sync=no 
soft=no mla=0 mem=0
  août 28 18:49:56 player-ef15 watchdog[2768]: ping: no machine to check
  août 28 18:49:56 player-ef15 watchdog[2768]: file: no file to check
  août 28 18:49:56 player-ef15 watchdog[2768]: pidfile: no server process to 
check
  août 28 18:49:56 player-ef15 watchdog[2768]: interface: no interface to check
  août 28 18:49:56 player-ef15 watchdog[2768]: temperature: no sensors to check
  août 28 18:49:56 player-ef15 watchdog[2768]: test=none(0) repair=none(0) 
alive=/dev/watchdog heartbeat=none to=root no_act=no force=no
  août 28 18:49:56 player-ef15 watchdog[2768]: cannot open /dev/watchdog (errno 
= 2 = 'No such file or directory')
  ```
  --- 
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/hwC0D2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D10p', 
'/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', 
'/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', 
'/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] 
failed with exit code 1:
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=912a4deb-6713-4f38-8c3a-8280e9c732cf
  InstallationDate: Installed on 2017-08-28 (1 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0aa7 Intel Corp. 
   Bus 001 Device 003: ID 046d:c05a Logitech, Inc. M90/M100 Optical Mouse
   Bus 001 Device 002: ID 04ca:0027 Lite-On Technology Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.11.0-14-generic 
root=UUID=25140007-3f56-4beb-8070-e96eabdb6319 ro quiet splash net.ifnames=0 
vt.handoff=7
  ProcVersionSignature: Ubuntu 4.11.0-14.20~16.04.1-generic 4.11.12
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.11.0-14-generic N/A
   linux-backports-modules-4.11.0-14-generic  N/A
   linux-firmware 1.157.11
  Tags:  xenial
  Uname: Linux 4.11.0-14-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dialout dip lpadmin mongodb plugdev pulse-access 
sambashare sudo video www-data
  _MarkForUpload: True
  dmi.bios.date: 11/24/2016
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: AYAPLCEL.86A.0029.2016.1124.1625
  dmi.board.name: NUC6CAYB
  dmi.board.vendor: Intel Corporation
  dmi.board.version: J23203-402
  

[Kernel-packages] [Bug 1700657] Re: Touchpad not detected in Lenovo X1 Yoga / Yoga 720-15IKB

[Mattia]

Could we please get any report on the progress? Did someone respond?

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

Title:
  Touchpad not detected in Lenovo X1 Yoga / Yoga 720-15IKB

Status in Linux:
  Unknown
Status in linux package in Ubuntu:
  Fix Committed

Bug description:
  Touchpad is not automatically detected in 14.04, 16.04 or 17.04. I
  tried in live mode and after full installation. I was able to connect
  an external mouse and a bluetooth mouse and both worked. I checked my
  xinput list and no sign:

  ⎡ Virtual core pointerid=2[master pointer
  (3)] ⎜   ↳ Virtual core XTEST pointer  id=4[slave
  pointer  (2)] ⎜   ↳ Wacom HID 50FE Finger touch id=12
  [slave  pointer  (2)] ⎜   ↳ Wacom HID 50FE Pen stylus
  id=13[slave  pointer  (2)] ⎜   ↳ Wacom HID 50FE Pen eraser
  id=16[slave  pointer  (2)] ⎜   ↳ byron's trackpad
  id=17[slave  pointer  (2)] ⎣ Virtual core keyboard
  id=3[master keyboard (2)]↳ Virtual core XTEST keyboard
  id=5[slave  keyboard (3)]↳ Power Button
  id=6[slave  keyboard (3)]↳ Video Bus
  id=7[slave  keyboard (3)]↳ Video Bus
  id=8[slave  keyboard (3)]↳ Power Button
  id=9[slave  keyboard (3)]↳ Apple Inc. Magic Keyboard
  id=10[slave  keyboard (3)]↳ EasyCamera
  id=11[slave  keyboard (3)]↳ Ideapad extra buttons
  id=14[slave  keyboard (3)]↳ AT Translated Set 2 keyboard
  id=15[slave  keyboard (3)]

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: linux-image-4.10.0-24-generic 4.10.0-24.28
  ProcVersionSignature: Ubuntu 4.10.0-24.28-generic 4.10.15
  Uname: Linux 4.10.0-24-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  byron  1794 F pulseaudio
  CurrentDesktop: Unity:Unity7
  Date: Mon Jun 26 16:51:37 2017
  InstallationDate: Installed on 2017-06-26 (0 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  MachineType: LENOVO 80X7
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-24-generic.efi.signed 
root=UUID=39280165-1a70-4b0d-b1fa-3b01e8bc1e25 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-24-generic N/A
   linux-backports-modules-4.10.0-24-generic  N/A
   linux-firmware 1.164
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/12/2017
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 4MCN20WW(V1.06)
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: Lenovo YOGA 720-15IKB
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 31
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo YOGA 720-15IKB
  dmi.modalias: 
dmi:bvnLENOVO:bvr4MCN20WW(V1.06):bd04/12/2017:svnLENOVO:pn80X7:pvrLenovoYOGA720-15IKB:rvnLENOVO:rnLenovoYOGA720-15IKB:rvrSDK0J40709WIN:cvnLENOVO:ct31:cvrLenovoYOGA720-15IKB:
  dmi.product.name: 80X7
  dmi.product.version: Lenovo YOGA 720-15IKB
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1700657/+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 1700657] Re: Touchpad not detected in Lenovo X1 Yoga / Yoga 720-15IKB

[F. H.]

The patch is accepted upstream, but has to be backported to Ubuntu kernels <= 
4.13.
See also https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1710392

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

Title:
  Touchpad not detected in Lenovo X1 Yoga / Yoga 720-15IKB

Status in Linux:
  Unknown
Status in linux package in Ubuntu:
  Fix Committed

Bug description:
  Touchpad is not automatically detected in 14.04, 16.04 or 17.04. I
  tried in live mode and after full installation. I was able to connect
  an external mouse and a bluetooth mouse and both worked. I checked my
  xinput list and no sign:

  ⎡ Virtual core pointerid=2[master pointer
  (3)] ⎜   ↳ Virtual core XTEST pointer  id=4[slave
  pointer  (2)] ⎜   ↳ Wacom HID 50FE Finger touch id=12
  [slave  pointer  (2)] ⎜   ↳ Wacom HID 50FE Pen stylus
  id=13[slave  pointer  (2)] ⎜   ↳ Wacom HID 50FE Pen eraser
  id=16[slave  pointer  (2)] ⎜   ↳ byron's trackpad
  id=17[slave  pointer  (2)] ⎣ Virtual core keyboard
  id=3[master keyboard (2)]↳ Virtual core XTEST keyboard
  id=5[slave  keyboard (3)]↳ Power Button
  id=6[slave  keyboard (3)]↳ Video Bus
  id=7[slave  keyboard (3)]↳ Video Bus
  id=8[slave  keyboard (3)]↳ Power Button
  id=9[slave  keyboard (3)]↳ Apple Inc. Magic Keyboard
  id=10[slave  keyboard (3)]↳ EasyCamera
  id=11[slave  keyboard (3)]↳ Ideapad extra buttons
  id=14[slave  keyboard (3)]↳ AT Translated Set 2 keyboard
  id=15[slave  keyboard (3)]

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: linux-image-4.10.0-24-generic 4.10.0-24.28
  ProcVersionSignature: Ubuntu 4.10.0-24.28-generic 4.10.15
  Uname: Linux 4.10.0-24-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  byron  1794 F pulseaudio
  CurrentDesktop: Unity:Unity7
  Date: Mon Jun 26 16:51:37 2017
  InstallationDate: Installed on 2017-06-26 (0 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  MachineType: LENOVO 80X7
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-24-generic.efi.signed 
root=UUID=39280165-1a70-4b0d-b1fa-3b01e8bc1e25 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-24-generic N/A
   linux-backports-modules-4.10.0-24-generic  N/A
   linux-firmware 1.164
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/12/2017
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 4MCN20WW(V1.06)
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: Lenovo YOGA 720-15IKB
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 31
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo YOGA 720-15IKB
  dmi.modalias: 
dmi:bvnLENOVO:bvr4MCN20WW(V1.06):bd04/12/2017:svnLENOVO:pn80X7:pvrLenovoYOGA720-15IKB:rvnLENOVO:rnLenovoYOGA720-15IKB:rvrSDK0J40709WIN:cvnLENOVO:ct31:cvrLenovoYOGA720-15IKB:
  dmi.product.name: 80X7
  dmi.product.version: Lenovo YOGA 720-15IKB
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1700657/+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 1713884] Re: [CIFS] Fix maximum SMB2 header size

[Joseph Salisbury]

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

** Also affects: linux (Ubuntu Vivid)
   Importance: Undecided
   Status: New

** Also affects: linux (Ubuntu Artful)
   Importance: Medium
   Status: Confirmed

** Also affects: linux (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Also affects: linux (Ubuntu Zesty)
   Importance: Undecided
   Status: New

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

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

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

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

** Changed in: linux (Ubuntu Zesty)
   Importance: Undecided => Medium

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

** Changed in: linux (Ubuntu Vivid)
   Importance: Undecided => Medium

** Tags added: artful kernel-da-key kernel-hyper-v xenial zesty

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

Title:
  [CIFS] Fix maximum SMB2 header size

Status in linux package in Ubuntu:
  Triaged
Status in linux source package in Vivid:
  Triaged
Status in linux source package in Xenial:
  Triaged
Status in linux source package in Zesty:
  Triaged
Status in linux source package in Artful:
  Triaged

Bug description:
  Currently the maximum size of SMB2/3 header is set incorrectly which
  leads to hanging of directory listing operations on encrypted SMB3
  connections. Fix this by setting the maximum size to 170 bytes that
  is calculated as RFC1002 length field size (4) + transform header
  size (52) + SMB2 header size (64) + create response size (56).

  https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-
  next.git/commit/?id=47690ab81f4f29b12bbb0676d3579e61ab4d84de

  This applies across the board 3.16, 4.4, 4.10, artful, and azure.
  Microsoft would be happy to help test.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1713884/+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 1713462] Re: linux: 4.4.0-94.117 -proposed tracker

[Łukasz Zemczak]

** Changed in: kernel-sru-workflow/promote-to-proposed
   Status: Confirmed => In Progress

** Changed in: kernel-sru-workflow/promote-to-proposed
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Łukasz 
Zemczak (sil2100)

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

Title:
  linux: 4.4.0-94.117 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  New
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  In Progress
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  Confirmed

Bug description:
  This bug is for tracking the  upload package.
  This bug will contain status and testing results related to that
  upload.

  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  backports: 1713463
  derivatives: 1713464,1713465,1713467,1713468,1713469
  kernel-stable-phase-changed:Tuesday, 29. August 2017 09:02 UTC
  kernel-stable-phase:Uploaded

  -- swm properties --
  boot-testing-requested: true
  phase: Uploaded

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1713462/+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 1713458] Re: linux-lts-trusty: 3.13.0-130.179~precise1 -proposed tracker

[Brad Figg]

** Changed in: kernel-sru-workflow/prepare-package
   Status: In Progress => Fix Released

** Changed in: kernel-sru-workflow/prepare-package-signed
   Status: In Progress => Fix Released

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  kernel-stable-master-bug: 1713456
  phase: Packaging
+ kernel-stable-phase:Uploaded
+ kernel-stable-phase-changed:Wednesday, 30. August 2017 14:31 UTC

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  kernel-stable-master-bug: 1713456
- phase: Packaging
- kernel-stable-phase:Uploaded
- kernel-stable-phase-changed:Wednesday, 30. August 2017 14:31 UTC
+ phase: Uploaded

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

Title:
  linux-lts-trusty: 3.13.0-130.179~precise1 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  New
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  In Progress
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-lts-trusty package in Ubuntu:
  Invalid
Status in linux-lts-trusty source package in Precise:
  Confirmed

Bug description:
  This bug is for tracking the  upload package.
  This bug will contain status and testing results related to that
  upload.

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  kernel-stable-master-bug: 1713456
  phase: Uploaded

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1713458/+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 1714030] [NEW] package linux-firmware 1.157.11 failed to install/upgrade: el subproceso instalado el script post-installation devolvió el código de salida de error 1

[Matias Mugnaini]

Public bug reported:

Im not technically able to detail the bug.

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: linux-firmware 1.157.11
ProcVersionSignature: Ubuntu 4.8.0-36.36~16.04.1-generic 4.8.11
Uname: Linux 4.8.0-36-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.10
Architecture: amd64
Date: Mon Aug 28 10:16:57 2017
Dependencies:
 
ErrorMessage: el subproceso instalado el script post-installation devolvió el 
código de salida de error 1
InstallationDate: Installed on 2017-03-19 (164 days ago)
InstallationMedia: Xubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215)
PackageArchitecture: all
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.1
 apt  1.2.19
SourcePackage: linux-firmware
Title: package linux-firmware 1.157.11 failed to install/upgrade: el subproceso 
instalado el script post-installation devolvió el código de salida de error 1
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package xenial

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

Title:
  package linux-firmware 1.157.11 failed to install/upgrade: el
  subproceso instalado el script post-installation devolvió el código de
  salida de error 1

Status in linux-firmware package in Ubuntu:
  New

Bug description:
  Im not technically able to detail the bug.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: linux-firmware 1.157.11
  ProcVersionSignature: Ubuntu 4.8.0-36.36~16.04.1-generic 4.8.11
  Uname: Linux 4.8.0-36-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  Date: Mon Aug 28 10:16:57 2017
  Dependencies:
   
  ErrorMessage: el subproceso instalado el script post-installation devolvió el 
código de salida de error 1
  InstallationDate: Installed on 2017-03-19 (164 days ago)
  InstallationMedia: Xubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.19
  SourcePackage: linux-firmware
  Title: package linux-firmware 1.157.11 failed to install/upgrade: el 
subproceso instalado el script post-installation devolvió el código de salida 
de error 1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1714030/+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 1238110] Re: makedumpfile needs porting for AArch64

[dann frazier]

ubuntu@dawes:~$ sudo apt install kdump-tools
Reading package lists... Done
Building dependency tree   
Reading state information... Done
The following additional packages will be installed:
  binutils crash kexec-tools libdw1 makedumpfile
Suggested packages:
  binutils-doc
The following NEW packages will be installed:
  binutils crash kdump-tools kexec-tools libdw1 makedumpfile
0 upgraded, 6 newly installed, 0 to remove and 0 not upgraded.
Need to get 4,901 kB of archives.
After this operation, 22.4 MB of additional disk space will be used.
Do you want to continue? [Y/n] 
Get:1 http://ports.ubuntu.com/ubuntu-ports xenial-proposed/main arm64 binutils 
arm64 2.26.1-1ubuntu1~16.04.5 [2,450 kB]
Get:2 http://ports.ubuntu.com/ubuntu-ports xenial-updates/main arm64 crash 
arm64 7.1.4-1ubuntu4.1 [2,096 kB]
Get:3 http://ports.ubuntu.com/ubuntu-ports xenial/main arm64 libdw1 arm64 
0.165-3ubuntu1 [161 kB]
Get:4 http://ports.ubuntu.com/ubuntu-ports xenial-proposed/main arm64 
makedumpfile arm64 1:1.5.9-5ubuntu0.5 [111 kB]
Get:5 http://ports.ubuntu.com/ubuntu-ports xenial-updates/main arm64 
kexec-tools arm64 1:2.0.10-1ubuntu2.3 [63.3 kB]
Get:6 http://ports.ubuntu.com/ubuntu-ports xenial-proposed/main arm64 
kdump-tools all 1:1.5.9-5ubuntu0.5 [20.9 kB]
Fetched 4,901 kB in 1s (4,899 kB/s) 
Preconfiguring packages ...
Selecting previously unselected package binutils.
(Reading database ... 65324 files and directories currently installed.)
Preparing to unpack .../binutils_2.26.1-1ubuntu1~16.04.5_arm64.deb ...
Unpacking binutils (2.26.1-1ubuntu1~16.04.5) ...
Selecting previously unselected package crash.
Preparing to unpack .../crash_7.1.4-1ubuntu4.1_arm64.deb ...
Unpacking crash (7.1.4-1ubuntu4.1) ...
Selecting previously unselected package libdw1:arm64.
Preparing to unpack .../libdw1_0.165-3ubuntu1_arm64.deb ...
Unpacking libdw1:arm64 (0.165-3ubuntu1) ...
Selecting previously unselected package makedumpfile.
Preparing to unpack .../makedumpfile_1%3a1.5.9-5ubuntu0.5_arm64.deb ...
Unpacking makedumpfile (1:1.5.9-5ubuntu0.5) ...
Selecting previously unselected package kexec-tools.
Preparing to unpack .../kexec-tools_1%3a2.0.10-1ubuntu2.3_arm64.deb ...
Unpacking kexec-tools (1:2.0.10-1ubuntu2.3) ...
Selecting previously unselected package kdump-tools.
Preparing to unpack .../kdump-tools_1%3a1.5.9-5ubuntu0.5_all.deb ...
Unpacking kdump-tools (1:1.5.9-5ubuntu0.5) ...
Processing triggers for libc-bin (2.23-0ubuntu9) ...
Processing triggers for man-db (2.7.5-1) ...
Processing triggers for systemd (229-4ubuntu19) ...
Processing triggers for ureadahead (0.100.0-19) ...
Setting up binutils (2.26.1-1ubuntu1~16.04.5) ...
Setting up crash (7.1.4-1ubuntu4.1) ...
Setting up libdw1:arm64 (0.165-3ubuntu1) ...
Setting up makedumpfile (1:1.5.9-5ubuntu0.5) ...
Setting up kexec-tools (1:2.0.10-1ubuntu2.3) ...
Generating /etc/default/kexec...
Generating grub configuration file ...
Warning: Setting GRUB_TIMEOUT to a non-zero value when GRUB_HIDDEN_TIMEOUT is 
set is no longer supported.
Found linux image: /boot/vmlinuz-4.10.0-33-generic
Found initrd image: /boot/initrd.img-4.10.0-33-generic
Adding boot menu entry for EFI firmware configuration
done
Setting up kdump-tools (1:1.5.9-5ubuntu0.5) ...
Processing triggers for libc-bin (2.23-0ubuntu9) ...
Processing triggers for systemd (229-4ubuntu19) ...
Processing triggers for ureadahead (0.100.0-19) ...
ubuntu@dawes:~$

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

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

Title:
  makedumpfile needs porting for AArch64

Status in Linaro AArch64 cross-distro work:
  New
Status in makedumpfile package in Ubuntu:
  Fix Released
Status in makedumpfile source package in Xenial:
  Fix Committed

Bug description:
  [Impact]
  kdump-tools is not installable on arm64 because it depends on makedumpfile, 
which is not currently built on arm64. Adding arm64 to the Architecture list in 
debian/control is all that is needed for it to build successfully.

  That said, xenial's version was too old to support filtering kdump-
  enabled xenial kernels (>= 4.10.0). So, this doesn't actually produce
  a *useful* makedumpfile, but does allow kdump-tools to be installed,
  which unblocks collection of (unfiltered) crash dump files.

  [Test Case]
  On an arm64 system:
   sudo apt install kdump-tools

  [Regression Risk]
  The only change here is to make a binary package available on arm64 that 
previously was not - regression risk to existing architectures should therefore 
be negligible.

  Note: Enabling a binary package for an architecture where it's known
  not to be useful - at last on it's own - is obviously non-ideal. I
  considered other options, but they all seem to add unnecessary
  regression risk:

  - Demoting the "Depends:" to a "Recommends:". I actually think 

[Kernel-packages] [Bug 1713462] Re: linux: 4.4.0-94.117 -proposed tracker

[Łukasz Zemczak]

** Changed in: kernel-sru-workflow/promote-to-proposed
   Status: In Progress => Fix Committed

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

Title:
  linux: 4.4.0-94.117 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  New
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Committed
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  Confirmed

Bug description:
  This bug is for tracking the  upload package.
  This bug will contain status and testing results related to that
  upload.

  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  backports: 1713463
  derivatives: 1713464,1713465,1713467,1713468,1713469
  kernel-stable-phase-changed:Tuesday, 29. August 2017 09:02 UTC
  kernel-stable-phase:Uploaded

  -- swm properties --
  boot-testing-requested: true
  phase: Uploaded

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1713462/+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 1713458] Re: linux-lts-trusty: 3.13.0-130.179~precise1 -proposed tracker

[Brad Figg]

** Changed in: kernel-sru-workflow/prepare-package-meta
   Status: In Progress => Fix Released

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

Title:
  linux-lts-trusty: 3.13.0-130.179~precise1 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  New
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-lts-trusty package in Ubuntu:
  Invalid
Status in linux-lts-trusty source package in Precise:
  Confirmed

Bug description:
  This bug is for tracking the  upload package.
  This bug will contain status and testing results related to that
  upload.

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  kernel-stable-master-bug: 1713456
  phase: Uploaded

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1713458/+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 1713461] Re: linux-lts-vivid: -proposed tracker

[Kleber Sacilotto de Souza]

** Changed in: kernel-sru-workflow
   Status: In Progress => Invalid

** Changed in: kernel-sru-workflow/automated-testing
   Status: New => Invalid

** Changed in: kernel-sru-workflow/certification-testing
   Status: New => Invalid

** Changed in: kernel-sru-workflow/prepare-package
   Status: New => Invalid

** Changed in: kernel-sru-workflow/prepare-package-meta
   Status: New => Invalid

** Changed in: kernel-sru-workflow/prepare-package-signed
   Status: New => Invalid

** Changed in: kernel-sru-workflow/promote-to-proposed
   Status: New => Invalid

** Changed in: kernel-sru-workflow/promote-to-security
   Status: New => Invalid

** Changed in: kernel-sru-workflow/promote-to-updates
   Status: New => Invalid

** Changed in: kernel-sru-workflow/regression-testing
   Status: New => Invalid

** Changed in: kernel-sru-workflow/security-signoff
   Status: New => Invalid

** Changed in: kernel-sru-workflow/upload-to-ppa
   Status: New => Invalid

** Changed in: kernel-sru-workflow/verification-testing
   Status: New => Invalid

** Changed in: linux-lts-vivid (Ubuntu Trusty)
   Status: Confirmed => Invalid

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

Title:
  linux-lts-vivid:  -proposed tracker

Status in Kernel SRU Workflow:
  Invalid
Status in Kernel SRU Workflow automated-testing series:
  Invalid
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Invalid
Status in Kernel SRU Workflow prepare-package-meta series:
  Invalid
Status in Kernel SRU Workflow prepare-package-signed series:
  Invalid
Status in Kernel SRU Workflow promote-to-proposed series:
  Invalid
Status in Kernel SRU Workflow promote-to-security series:
  Invalid
Status in Kernel SRU Workflow promote-to-updates series:
  Invalid
Status in Kernel SRU Workflow regression-testing series:
  Invalid
Status in Kernel SRU Workflow security-signoff series:
  Invalid
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Invalid
Status in linux-lts-vivid package in Ubuntu:
  Invalid
Status in linux-lts-vivid source package in Trusty:
  Invalid

Bug description:
  This bug is for tracking the  upload package.
  This bug will contain status and testing results related to that
  upload.

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  kernel-stable-master-bug: 1713459

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1713461/+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 1713459] Re: linux: -proposed tracker

[Kleber Sacilotto de Souza]

** Changed in: kernel-sru-workflow
   Status: In Progress => Invalid

** Changed in: kernel-sru-workflow/automated-testing
   Status: New => Invalid

** Changed in: kernel-sru-workflow/certification-testing
   Status: New => Invalid

** Changed in: kernel-sru-workflow/prepare-package
   Status: Confirmed => Invalid

** Changed in: kernel-sru-workflow/prepare-package-meta
   Status: New => Invalid

** Changed in: kernel-sru-workflow/prepare-package-signed
   Status: New => Invalid

** Changed in: kernel-sru-workflow/promote-to-proposed
   Status: New => Invalid

** Changed in: kernel-sru-workflow/promote-to-security
   Status: New => Invalid

** Changed in: kernel-sru-workflow/promote-to-updates
   Status: New => Invalid

** Changed in: kernel-sru-workflow/regression-testing
   Status: New => Invalid

** Changed in: kernel-sru-workflow/security-signoff
   Status: New => Invalid

** Changed in: kernel-sru-workflow/verification-testing
   Status: New => Invalid

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

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

Title:
  linux:  -proposed tracker

Status in Kernel SRU Workflow:
  Invalid
Status in Kernel SRU Workflow automated-testing series:
  Invalid
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Invalid
Status in Kernel SRU Workflow prepare-package-meta series:
  Invalid
Status in Kernel SRU Workflow prepare-package-signed series:
  Invalid
Status in Kernel SRU Workflow promote-to-proposed series:
  Invalid
Status in Kernel SRU Workflow promote-to-security series:
  Invalid
Status in Kernel SRU Workflow promote-to-updates series:
  Invalid
Status in Kernel SRU Workflow regression-testing series:
  Invalid
Status in Kernel SRU Workflow security-signoff series:
  Invalid
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Invalid
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Vivid:
  Invalid

Bug description:
  This bug is for tracking the  upload package.
  This bug will contain status and testing results related to that
  upload.

  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  backports: 1713461
  derivatives:

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1713459/+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 1713455] Re: linux: -proposed tracker

[Kleber Sacilotto de Souza]

** Changed in: kernel-sru-workflow
   Status: In Progress => Invalid

** Changed in: kernel-sru-workflow/automated-testing
   Status: New => Invalid

** Changed in: kernel-sru-workflow/certification-testing
   Status: New => Invalid

** Changed in: kernel-sru-workflow/prepare-package
   Status: Confirmed => Invalid

** Changed in: kernel-sru-workflow/prepare-package-lbm
   Status: New => Invalid

** Changed in: kernel-sru-workflow/prepare-package-meta
   Status: New => Invalid

** Changed in: kernel-sru-workflow/promote-to-proposed
   Status: New => Invalid

** Changed in: kernel-sru-workflow/promote-to-security
   Status: New => Invalid

** Changed in: kernel-sru-workflow/promote-to-updates
   Status: New => Invalid

** Changed in: kernel-sru-workflow/regression-testing
   Status: New => Invalid

** Changed in: kernel-sru-workflow/security-signoff
   Status: New => Invalid

** Changed in: kernel-sru-workflow/verification-testing
   Status: New => Invalid

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

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

Title:
  linux:  -proposed tracker

Status in Kernel SRU Workflow:
  Invalid
Status in Kernel SRU Workflow automated-testing series:
  Invalid
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Invalid
Status in Kernel SRU Workflow prepare-package-lbm series:
  Invalid
Status in Kernel SRU Workflow prepare-package-meta series:
  Invalid
Status in Kernel SRU Workflow promote-to-proposed series:
  Invalid
Status in Kernel SRU Workflow promote-to-security series:
  Invalid
Status in Kernel SRU Workflow promote-to-updates series:
  Invalid
Status in Kernel SRU Workflow regression-testing series:
  Invalid
Status in Kernel SRU Workflow security-signoff series:
  Invalid
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Invalid
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Precise:
  Invalid

Bug description:
  This bug is for tracking the  upload package.
  This bug will contain status and testing results related to that
  upload.

  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  backports: 
  derivatives:

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1713455/+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 1713456] Re: linux: 3.13.0-130.179 -proposed tracker

[Łukasz Zemczak]

** Changed in: kernel-sru-workflow/promote-to-proposed
   Status: Confirmed => Fix Committed

** Changed in: kernel-sru-workflow/promote-to-proposed
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Łukasz 
Zemczak (sil2100)

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

Title:
  linux: 3.13.0-130.179 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  New
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Committed
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Trusty:
  Confirmed

Bug description:
  This bug is for tracking the  upload package.
  This bug will contain status and testing results related to that
  upload.

  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  backports: 1713458
  derivatives:
  kernel-stable-phase-changed:Tuesday, 29. August 2017 16:01 UTC
  kernel-stable-phase:Uploaded

  -- swm properties --
  boot-testing-requested: true
  phase: Uploaded

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1713456/+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 1713467] Re: linux-aws: 4.4.0-1033.42 -proposed tracker

[Łukasz Zemczak]

** Changed in: kernel-sru-workflow/promote-to-proposed
   Status: Confirmed => Fix Committed

** Changed in: kernel-sru-workflow/promote-to-proposed
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Łukasz 
Zemczak (sil2100)

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

Title:
  linux-aws: 4.4.0-1033.42 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  New
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Committed
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-aws package in Ubuntu:
  Invalid
Status in linux-aws source package in Xenial:
  Confirmed

Bug description:
  This bug is for tracking the  upload package.
  This bug will contain status and testing results related to that
  upload.

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1713462
  phase: Uploaded

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1713467/+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 1667750] Re: xhci_hcd: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 2 comp_code 13

[Daniel Aden]

Same issue in kernel 4.4.  Is there a backport for 16.04?

$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 16.04.3 LTS
Release:16.04
Codename:   xenial

$ uname -a
Linux rig01 4.4.0-92-generic #115-Ubuntu SMP Thu Aug 10 09:04:33 UTC 2017 
x86_64 x86_64 x86_64 GNU/Linux

$ dmesg
[81862.720112] xhci_hcd :0d:00.0: ERROR Transfer event TRB DMA ptr not part 
of current TD ep_index 4 comp_code 13
[81862.720120] xhci_hcd :0d:00.0: Looking for event-dma 001fa64e2110 
trb-start 001fa64e20f0 trb-end 001fa64e20f0 seg-start 001fa64e2000 
seg-end 001fa64e2ff0
[81862.720299] xhci_hcd :0d:00.0: ERROR Transfer event TRB DMA ptr not part 
of current TD ep_index 4 comp_code 13
[81862.720302] xhci_hcd :0d:00.0: Looking for event-dma 001fa64e2120 
trb-start 001fa64e20f0 trb-end 001fa64e20f0 seg-start 001fa64e2000 
seg-end 001fa64e2ff0
[81862.720687] xhci_hcd :0d:00.0: ERROR Transfer event TRB DMA ptr not part 
of current TD ep_index 4 comp_code 13
[81862.720694] xhci_hcd :0d:00.0: Looking for event-dma 001fa64e2130 
trb-start 001fa64e20f0 trb-end 001fa64e20f0 seg-start 001fa64e2000 
seg-end 001fa64e2ff0
[81862.720911] xhci_hcd :0d:00.0: ERROR Transfer event TRB DMA ptr not part 
of current TD ep_index 4 comp_code 13
[81862.720914] xhci_hcd :0d:00.0: Looking for event-dma 001fa64e2140 
trb-start 001fa64e20f0 trb-end 001fa64e20f0 seg-start 001fa64e2000 
seg-end 001fa64e2ff0
[81862.722506] xhci_hcd :0d:00.0: ERROR Transfer event TRB DMA ptr not part 
of current TD ep_index 4 comp_code 13
[81862.722513] xhci_hcd :0d:00.0: Looking for event-dma 001fa64e2150 
trb-start 001fa64e20f0 trb-end 001fa64e20f0 seg-start 001fa64e2000 
seg-end 001fa64e2ff0
[81862.722584] xhci_hcd :0d:00.0: ERROR Transfer event TRB DMA ptr not part 
of current TD ep_index 4 comp_code 13
[81862.722588] xhci_hcd :0d:00.0: Looking for event-dma 001fa64e2160 
trb-start 001fa64e20f0 trb-end 001fa64e20f0 seg-start 001fa64e2000 
seg-end 001fa64e2ff0

$ lsusb -s 006:002 -v

Bus 006 Device 002: ID 0b95:1790 ASIX Electronics Corp. AX88179 Gigabit Ethernet
Device Descriptor:
  bLength18
  bDescriptorType 1
  bcdUSB   3.00
  bDeviceClass  255 Vendor Specific Class
  bDeviceSubClass   255 Vendor Specific Subclass
  bDeviceProtocol 0 
  bMaxPacketSize0 9
  idVendor   0x0b95 ASIX Electronics Corp.
  idProduct  0x1790 AX88179 Gigabit Ethernet
  bcdDevice1.00
  iManufacturer   1 ASIX Elec. Corp.
  iProduct2 AX88179
  iSerial 3 249B1E94E5
  bNumConfigurations  1
  Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength   57
bNumInterfaces  1
bConfigurationValue 1
iConfiguration  0 
bmAttributes 0xa0
  (Bus Powered)
  Remote Wakeup
MaxPower  124mA
Interface Descriptor:
  bLength 9
  bDescriptorType 4
  bInterfaceNumber0
  bAlternateSetting   0
  bNumEndpoints   3
  bInterfaceClass   255 Vendor Specific Class
  bInterfaceSubClass255 Vendor Specific Subclass
  bInterfaceProtocol  0 
  iInterface  4 Network_Interface
  Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81  EP 1 IN
bmAttributes3
  Transfer TypeInterrupt
  Synch Type   None
  Usage Type   Data
wMaxPacketSize 0x0008  1x 8 bytes
bInterval  11
bMaxBurst   0
  Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x82  EP 2 IN
bmAttributes2
  Transfer TypeBulk
  Synch Type   None
  Usage Type   Data
wMaxPacketSize 0x0400  1x 1024 bytes
bInterval   0
bMaxBurst   3
  Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x03  EP 3 OUT
bmAttributes2
  Transfer TypeBulk
  Synch Type   None
  Usage Type   Data
wMaxPacketSize 0x0400  1x 1024 bytes
bInterval   0
bMaxBurst  15
Binary Object Store Descriptor:
  bLength 5
  bDescriptorType15
  wTotalLength   22
  bNumDeviceCaps  2
  USB 2.0 Extension Device Capability:
bLength 7
bDescriptorType16
bDevCapabilityType  2
b

[Kernel-packages] [Bug 1667750] Re: xhci_hcd: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 2 comp_code 13

[André Düwel]

@Daniel Aden: The fix was release in Kernel  4.4.0-93.116, please update
;)

You posted that you are using 4.4.0-92-generic #115.

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

Title:
  xhci_hcd: ERROR Transfer event TRB DMA ptr not part of current TD
  ep_index 2 comp_code 13

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Fix Released
Status in linux source package in Zesty:
  Fix Released
Status in linux source package in Artful:
  Fix Released
Status in linux package in Arch Linux:
  New
Status in linux package in Debian:
  New
Status in linux package in Fedora:
  Unknown

Bug description:
  [SRU Justification]

  [Impact] 
  Dell TB16 docking station has issue to use gigabit ethernet. The ethernet
  will disconnect unless it's changed to 100Mb/s.

  
  [Test Case]
  Download some big files from the web.
  User confirms the patch fixes the issue.

  [Regression Potential] 
  This patch only effects ASMEDIA's ASM1042A.
  The regression potential is low, also limited to the specific device.

  ---

  My system contains a Realtek Semiconductor Corp. RTL8153 Gigabit
  Ethernet Adapter which is on usb3 bus in my docking station (Dell
  TB16) which is attached to my laptop (Dell XPS9550) via Thunderbolt 3.

  I get usb related kernel error messages when I initiate a high speed
  transfer (by issuing wget http://cdimage.ubuntu.com/daily-live/current
  /zesty-desktop-amd64.iso) and the download fails.

  This does not happened when the Ethernet adapter is connected to a
  100Mb/s switch, but only when connected to 1000Mb/s. It also does not
  happened with slow traffic (e.g. web page browsing). This is not a new
  bug with kernel 4.10, but has been going on since at least 4.7 and
  maybe (probably?) since forever. I'm aware of several others with this
  configuration (RTL8153 on usb3 behind thunderbolt 3) that have the
  same issue. This bug is also not specific to Ubuntu; I also get it on
  Arch Linux. I've also tested and seen this bug with several different
  models of thunderbolt 3 docks.

  Here are the relevant kernel log messages:

  Feb 24 16:42:38 ubuntu kernel: xhci_hcd :0e:00.0: ERROR Transfer event 
TRB DMA ptr not part of current TD ep_index 2 comp_code 13
  Feb 24 16:42:38 ubuntu kernel: xhci_hcd :0e:00.0: Looking for event-dma 
0004777d9010 trb-start 000475a14fe0 trb-end 000475a14fe0 seg-start 
000475a14000 seg-end 000475a14ff0
  Feb 24 16:42:38 ubuntu kernel: xhci_hcd :0e:00.0: ERROR Transfer event 
TRB DMA ptr not part of current TD ep_index 2 comp_code 13
  Feb 24 16:42:38 ubuntu kernel: xhci_hcd :0e:00.0: Looking for event-dma 
0004777d9020 trb-start 000475a14fe0 trb-end 000475a14fe0 seg-start 
000475a14000 seg-end 000475a14ff0
  Feb 24 16:42:38 ubuntu kernel: xhci_hcd :0e:00.0: ERROR Transfer event 
TRB DMA ptr not part of current TD ep_index 2 comp_code 13
  Feb 24 16:42:38 ubuntu kernel: xhci_hcd :0e:00.0: Looking for event-dma 
0004777d9030 trb-start 000475a14fe0 trb-end 000475a14fe0 seg-start 
000475a14000 seg-end 000475a14ff0
  Feb 24 16:42:38 ubuntu kernel: xhci_hcd :0e:00.0: ERROR Transfer event 
TRB DMA ptr not part of current TD ep_index 2 comp_code 13
  Feb 24 16:42:38 ubuntu kernel: xhci_hcd :0e:00.0: Looking for event-dma 
0004777d9040 trb-start 000475a14fe0 trb-end 000475a14fe0 seg-start 
000475a14000 seg-end 000475a14ff0
  Feb 24 16:42:38 ubuntu kernel: xhci_hcd :0e:00.0: ERROR Transfer event 
TRB DMA ptr not part of current TD ep_index 2 comp_code 13
  Feb 24 16:42:38 ubuntu kernel: xhci_hcd :0e:00.0: Looking for event-dma 
0004777d9050 trb-start 000475a14fe0 trb-end 000475a14fe0 seg-start 
000475a14000 seg-end 000475a14ff0
  Feb 24 16:42:38 ubuntu kernel: xhci_hcd :0e:00.0: ERROR Transfer event 
TRB DMA ptr not part of current TD ep_index 2 comp_code 13
  Feb 24 16:42:38 ubuntu kernel: xhci_hcd :0e:00.0: Looking for event-dma 
0004777d9060 trb-start 000475a14fe0 trb-end 000475a14fe0 seg-start 
000475a14000 seg-end 000475a14ff0
  Feb 24 16:42:39 ubuntu kernel: xhci_hcd :0e:00.0: ERROR Transfer event 
TRB DMA ptr not part of current TD ep_index 2 comp_code 13
  Feb 24 16:42:39 ubuntu kernel: xhci_hcd :0e:00.0: Looking for event-dma 
0004777d9070 trb-start 000475a14fe0 trb-end 000475a14fe0 seg-start 
000475a14000 seg-end 000475a14ff0
  Feb 24 16:42:39 ubuntu kernel: xhci_hcd :0e:00.0: ERROR Transfer event 
TRB DMA ptr not part of current TD ep_index 2 comp_code 13
  Feb 24 16:42:39 ubuntu kernel: xhci_hcd :0e:00.0: Looking for event-dma 
0004777d9080 trb-start 000475a14fe0 trb-end 000475a14fe0 seg-start 
000475a14000 seg-end 000475a14ff0
  Feb 24 16:43:06 ubuntu kernel:

[Kernel-packages] [Bug 1713770] Re: USN-3405-1 kernel cause kernel panic when using mandos

[KayNettle]

Sorry everyone, this is a mandos problem and it's in universe, so I
shouldn't have reported the problem here.  Building a 1.7.16 mandos-
client package fixed my issue.

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

Title:
  USN-3405-1 kernel cause kernel panic when using mandos

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

Bug description:
  When mandos is installed, kernel panics and doesn't get password from
  mandos server.  Since it happens so early in the boot, the panic isn't
  in the logs.  On machine that don't have mandos installed, kernel
  boots fine.  The linux-image-4.4.0-92-generic kernel works fine.

  sorry, I had to say I didn't know which package is was in order to
  submit the bug report, it's linux-image-4.4.0-93-generic.

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

Re: [Kernel-packages] [Bug 1710019] Re: support GICv3 ITS save/restore & migration

[dann frazier]

On Wed, Aug 30, 2017 at 12:35 AM, ChristianEhrhardt
<1710...@bugs.launchpad.net> wrote:
> Hi Dann,
> Sorry to ask, really I'm not neglecting all the work you do here.
> But it is a huge set of changes (17 files changed, 929 insertions(+), 46 
> deletions(-), and not all arm only) and I wonder as Zesty will never have the 
> 4.13 kernel (as HWE is for LTS only).

No offense taken! It's a good question. I also have a tested backport
of the necessary changes to zesty's 4.10 kernel, I'm just awaiting
upstream acceptance of Vijay's patch before doing a final round of
testing and sending a PR to the kernel team.

WRT the patches impacting !arm, the only one I see here is
kvm-all-Pass-an-error-object-to-kvm_device_access.patch, which impacts
the error handling of kvm_device_access(). I'd be happy coordinate
appropriate testing on other architectures to mitigate the risk there.

  -dann

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

Title:
  support GICv3 ITS save/restore & migration

Status in linux package in Ubuntu:
  Triaged
Status in qemu package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Won't Fix
Status in qemu source package in Xenial:
  Triaged
Status in linux source package in Zesty:
  Triaged
Status in qemu source package in Zesty:
  In Progress

Bug description:
  [Impact]
  Virtual machines on GICv3-based ARM systems cannot be saved/restored or 
migrated.
  This feature was added in QEMU 2.10.

  [Test Case]
  ubuntu@grotrian:~$ sudo virsh save 7936-0 7936-0.sav

  Domain 7936-0 saved to 7936-0.sav

  ubuntu@grotrian:~$ sudo virsh restore 7396-0.sav
  error: Failed to restore domain from 7396-0.sav
  error: operation failed: job: unexpectedly failed

  ubuntu@grotrian:~$ sudo tail -3 /var/log/libvirt/qemu/7936-0.log 
  2017-08-10T21:26:38.217427Z qemu-system-aarch64: State blocked by 
non-migratable device 'arm_gicv3_its'
  2017-08-10T21:26:38.217565Z qemu-system-aarch64: load of migration failed: 
Invalid argument
  2017-08-10 21:26:38.217+: shutting down, reason=failed

  [Regression Risk]

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1710019/+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 1713821] Re: arm64 arch_timer fixes

[dann frazier]

** Description changed:

  [Impact]
  This bug captures a few issues with the ARM arch_timer driver:
  
  1) Some arm64 systems have hardware defects in their architected timer
  implementations that require errata, which we workaround in the kernel.
  However, it's possible that this workaround will not be applied if the
  timer was reset w/ the user access bit set.
  
  2) The Juno board fails to initialize a timer at boot:
  
-   arch_timer: Unable to map frame @ 0x
-   arch_timer: Frame missing phys irq.
-   Failed to initialize '/timer@2a81': -22
+   arch_timer: Unable to map frame @ 0x
+   arch_timer: Frame missing phys irq.
+   Failed to initialize '/timer@2a81': -22
  
  3) Possible boot warning from arch_timer_mem_of_init():
-'Trying to vfree() nonexistent vm area'
+    'Trying to vfree() nonexistent vm area'
  
  4) There's a theoretical problem where the first frame of a timer could
  be used even though a better suited timer frame is available.
  
  5) An infinite recursion loop will occur when enabling the function
  tracer in builds with CONFIG_PREEMPT_TRACER=y. Ubuntu does not enable
  CONFIG_PREEMPT_TRACER, so this will only be a problem if that changes.
  
  [Test Case]
+ I've regression tested this on both a system w/ an errata workaround 
(HiSilicon D05) and one that is not (Cavium ThunderX CRB1S). In both cases the 
timer was initialized correctly.
  
  [Regression Risk]
+ The regression risk is restricted to ARM systems, as this driver only applies 
there. Regressions could lead to a timer failing to initialize, or a system 
that requires errata not having the appropriate workaround applied. (Which are 
also the  conditions that the suggested backports are attempting to fix).

** Description changed:

  [Impact]
  This bug captures a few issues with the ARM arch_timer driver:
  
  1) Some arm64 systems have hardware defects in their architected timer
  implementations that require errata, which we workaround in the kernel.
  However, it's possible that this workaround will not be applied if the
  timer was reset w/ the user access bit set.
  
  2) The Juno board fails to initialize a timer at boot:
  
    arch_timer: Unable to map frame @ 0x
    arch_timer: Frame missing phys irq.
    Failed to initialize '/timer@2a81': -22
  
  3) Possible boot warning from arch_timer_mem_of_init():
     'Trying to vfree() nonexistent vm area'
  
  4) There's a theoretical problem where the first frame of a timer could
  be used even though a better suited timer frame is available.
  
  5) An infinite recursion loop will occur when enabling the function
  tracer in builds with CONFIG_PREEMPT_TRACER=y. Ubuntu does not enable
  CONFIG_PREEMPT_TRACER, so this will only be a problem if that changes.
  
  [Test Case]
- I've regression tested this on both a system w/ an errata workaround 
(HiSilicon D05) and one that is not (Cavium ThunderX CRB1S). In both cases the 
timer was initialized correctly.
+ I've regression tested this on both a system w/ an errata workaround 
(HiSilicon D05) and one that is not (Cavium ThunderX CRB1S). In both cases the 
timer was initialized correctly. Verified by looking at the boot messages:
+ 
+ dannf@d05-3:~$ dmesg | grep arch_timer
+ [0.00] arch_timer: Enabling global workaround for HiSilicon erratum 
161010101
+ [0.00] arch_timer: CPU0: Trapping CNTVCT access
+ [0.00] arch_timer: cp15 timer(s) running at 50.00MHz (phys).
+ [0.194241] arch_timer: CPU1: Trapping CNTVCT access
+ [0.197305] arch_timer: CPU2: Trapping CNTVCT access
+ <.>
+ [0.396228] arch_timer: CPU62: Trapping CNTVCT access
+ [0.399752] arch_timer: CPU63: Trapping CNTVCT access
+ 
+ ubuntu@grotrian:~$ dmesg | grep arch_timer
+ [0.00] arch_timer: cp15 timer(s) running at 100.00MHz (phys).
  
  [Regression Risk]
  The regression risk is restricted to ARM systems, as this driver only applies 
there. Regressions could lead to a timer failing to initialize, or a system 
that requires errata not having the appropriate workaround applied. (Which are 
also the  conditions that the suggested backports are attempting to fix).

** Changed in: linux (Ubuntu)
 Assignee: (unassigned) => dann frazier (dannf)

** Changed in: linux (Ubuntu Zesty)
 Assignee: (unassigned) => dann frazier (dannf)

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

** Changed in: linux (Ubuntu Zesty)
   Status: Confirmed => 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/1713821

Title:
  arm64 arch_timer fixes

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

Bug description:
  [Impact]
  This bug captures a few issues with the ARM arch_timer driver:

  1) Some arm64 systems have hardware def

[Kernel-packages] [Bug 1713458] Re: linux-lts-trusty: 3.13.0-130.179~precise1 -proposed tracker

[Brad Figg]

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
+ boot-testing-requested: true
  kernel-stable-master-bug: 1713456
  phase: Uploaded

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

Title:
  linux-lts-trusty: 3.13.0-130.179~precise1 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  New
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-lts-trusty package in Ubuntu:
  Invalid
Status in linux-lts-trusty source package in Precise:
  Confirmed

Bug description:
  This bug is for tracking the  upload package.
  This bug will contain status and testing results related to that
  upload.

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1713456
  phase: Uploaded

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1713458/+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 1713467] Re: linux-aws: 4.4.0-1033.42 -proposed tracker

[Brad Figg]

** Changed in: kernel-sru-workflow/automated-testing
   Status: New => Confirmed

** Changed in: kernel-sru-workflow/certification-testing
   Status: New => Confirmed

** Changed in: kernel-sru-workflow/promote-to-proposed
   Status: Fix Committed => Fix Released

** Changed in: kernel-sru-workflow/regression-testing
   Status: New => Confirmed

** Changed in: kernel-sru-workflow/verification-testing
   Status: New => Confirmed

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1713462
  phase: Uploaded
+ kernel-stable-phase:Promoted to proposed
+ kernel-stable-phase-changed:Wednesday, 30. August 2017 18:03 UTC

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1713462
- phase: Uploaded
- kernel-stable-phase:Promoted to proposed
- kernel-stable-phase-changed:Wednesday, 30. August 2017 18:03 UTC
+ phase: Promoted to proposed
+ proposed-announcement-sent: true
+ proposed-testing-requested: true

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

Title:
  linux-aws: 4.4.0-1033.42 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Confirmed
Status in Kernel SRU Workflow certification-testing series:
  Confirmed
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-aws package in Ubuntu:
  Invalid
Status in linux-aws source package in Xenial:
  Confirmed

Bug description:
  This bug is for tracking the  upload package.
  This bug will contain status and testing results related to that
  upload.

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1713462
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1713467/+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 1702998] Re: Ubuntu 17.04: Guest crashed @writeback_sb_inodes+0x310/0x590

[Joseph Salisbury]

** Also affects: linux (Ubuntu Zesty)
   Importance: Undecided
   Status: New

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

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

** Changed in: linux (Ubuntu Zesty)
 Assignee: (unassigned) => Joseph Salisbury (jsalisbury)

** Changed in: linux (Ubuntu)
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Joseph 
Salisbury (jsalisbury)

** Changed in: linux (Ubuntu)
   Status: Triaged => 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/1702998

Title:
  Ubuntu 17.04: Guest crashed @writeback_sb_inodes+0x310/0x590

Status in The Ubuntu-power-systems project:
  Triaged
Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Zesty:
  In Progress

Bug description:
  == Comment: #0 - Lata Kuntal  - 2017-03-03 00:50:54 ==
  Ubuntu 17.04 guest dropped at xmon after crashing at 
writeback_sb_inodes+0x310/0x590. 
  The guest is having XFS rootfs and NPIV disk. It crashed after 30+ hrs of 
BASE and NFS stress test .

  Crash logs
  ===
  root@guskvm:~# virsh console gusg1 --force
  Connected to domain gusg1
  Escape character is ^]

  0:mon>
  0:mon> t
  [c000a4bc7940] c036f790 writeback_sb_inodes+0x310/0x590
  [c000a4bc7a50] c036faf4 __writeback_inodes_wb+0xe4/0x150
  [c000a4bc7ab0] c036ff1c wb_writeback+0x2cc/0x440
  [c000a4bc7b80] c0370c30 wb_workfn+0x150/0x560
  [c000a4bc7c90] c00ed8c0 process_one_work+0x2b0/0x5a0
  [c000a4bc7d20] c00edc58 worker_thread+0xa8/0x650
  [c000a4bc7dc0] c00f67b4 kthread+0x154/0x1a0
  [c000a4bc7e30] c000b4e8 ret_from_kernel_thread+0x5c/0x74
  0:mon> r
  R00 = c036f790   R16 = c000eca70300
  R01 = c000a4bc78e0   R17 = c000f7035240
  R02 = c143c900   R18 = 
  R03 = c000f7035150   R19 = 
  R04 = 0019   R20 = c000a4bc4000
  R05 = 0100   R21 = ff7f
  R06 =    R22 = c433d758
  R07 =    R23 = c433d738
  R08 = 00034995   R24 = 
  R09 =    R25 = 
  R10 = 8000   R26 = c000f70351d8
  R11 = c000a4bc7a40   R27 = 
  R12 = 2200   R28 = 0001
  R13 = cfb8   R29 = c433d728
  R14 =    R30 = c000f7035150
  R15 = c000f70351d8   R31 = 
  pc  = c036c120 locked_inode_to_wb_and_lock_list+0x50/0x290
  cfar= c00b2a14 kvmppc_save_tm+0x168/0x16c
  lr  = c036f790 writeback_sb_inodes+0x310/0x590
  msr = 80009033   cr  = 24002482
  ctr = c0381e30   xer =    trap =  300
  dar =    dsisr = 4000
  0:mon> e
  cpu 0x0: Vector: 300 (Data Access) at [c000a4bc7660]
  pc: c036c120: locked_inode_to_wb_and_lock_list+0x50/0x290
  lr: c036f790: writeback_sb_inodes+0x310/0x590
  sp: c000a4bc78e0
 msr: 80009033
 dar: 0
   dsisr: 4000
current = 0xc000fbe96000
paca= 0xcfb8   softe: 0irq_happened: 0x01
  pid   = 17305, comm = kworker/u16:0
  Linux version 4.10.0-8-generic (buildd@bos01-ppc64el-001) (gcc version 6.3.0 
20161229 (Ubuntu 6.3.0-2ubuntu1) ) #10-Ubuntu SMP Mon Feb 13 14:00:06 UTC 2017 
(Ubuntu 4.10.0-8.10-generic 4.10.0-rc8)
  0:mon> d
      ||
  0:mon>

  
  Host and guest kernel build
  =
  4.10.0-8-generic

  
  OPAL firmware version
  
T side: FW860.20 (SV860_078)
Boot side : FW860.20 (SV860_078)

  
  == Comment: #4 - VIPIN K. PARASHAR  - 2017-03-03 
02:55:20 ==
  [140071.761707] Adding 153536k swap on /dev/loop0.  Priority:-2 extents:1 
across:153536k FS
  [140072.153143] Adding 153472k swap on /dev/loop0.  Priority:-2 extents:1 
across:153472k FS
  [140072.441833] Unable to handle kernel paging request for data at address 
0x
  [140072.442064] Faulting instruction address: 0xc036c120
  0:mon>

  0:mon> e
  cpu 0x0: Vector: 300 (Data Access) at [c000a4bc7660]
  pc: c036c120: locked_inode_to_wb_and_lock_list+0x50/0x290
  lr: c036f790: writeback_sb_inodes+0x310/0x590
  sp: c000a4bc78e0
 msr: 80009033
 dar: 0
   dsisr: 4000
current = 0xc000fbe96000
paca= 0xcfb8 softe: 0irq_happened: 0x01
  pid   = 17305, comm = kworker/u16:0
  Linux version 4.10.0-8-generic (buildd@bos01-ppc64el-001) (gcc version 6.3.0 
20161229 (Ubuntu 6.3.0-2ubuntu1) ) #10-Ubuntu SMP Mon Feb 13 14:00:06 UTC 2017 
(Ubuntu 4.10.0-8.10-generic 4.10.0-rc8)
  0:m

[Kernel-packages] [Bug 1667750] Re: xhci_hcd: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 2 comp_code 13

[Mario Limonciello]

FYI there are two separate issues.  The first is the poor performance of
the ethernet on the TB16.  That's the original reason this bug was
opened and has been fixed in kernel upgrades.

There is a second issue that a BIOS update causes problems with USB on the TB16 
(such as corrupted packets).  Dell support is aware of it and a new BIOS is on 
it's way out very soon to resolve it.  You can track the status of that with 
Dell here:
http://en.community.dell.com/techcenter/os-applications/f/4613/p/20018487/21017133#21017133

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

Title:
  xhci_hcd: ERROR Transfer event TRB DMA ptr not part of current TD
  ep_index 2 comp_code 13

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Fix Released
Status in linux source package in Zesty:
  Fix Released
Status in linux source package in Artful:
  Fix Released
Status in linux package in Arch Linux:
  New
Status in linux package in Debian:
  New
Status in linux package in Fedora:
  Unknown

Bug description:
  [SRU Justification]

  [Impact] 
  Dell TB16 docking station has issue to use gigabit ethernet. The ethernet
  will disconnect unless it's changed to 100Mb/s.

  
  [Test Case]
  Download some big files from the web.
  User confirms the patch fixes the issue.

  [Regression Potential] 
  This patch only effects ASMEDIA's ASM1042A.
  The regression potential is low, also limited to the specific device.

  ---

  My system contains a Realtek Semiconductor Corp. RTL8153 Gigabit
  Ethernet Adapter which is on usb3 bus in my docking station (Dell
  TB16) which is attached to my laptop (Dell XPS9550) via Thunderbolt 3.

  I get usb related kernel error messages when I initiate a high speed
  transfer (by issuing wget http://cdimage.ubuntu.com/daily-live/current
  /zesty-desktop-amd64.iso) and the download fails.

  This does not happened when the Ethernet adapter is connected to a
  100Mb/s switch, but only when connected to 1000Mb/s. It also does not
  happened with slow traffic (e.g. web page browsing). This is not a new
  bug with kernel 4.10, but has been going on since at least 4.7 and
  maybe (probably?) since forever. I'm aware of several others with this
  configuration (RTL8153 on usb3 behind thunderbolt 3) that have the
  same issue. This bug is also not specific to Ubuntu; I also get it on
  Arch Linux. I've also tested and seen this bug with several different
  models of thunderbolt 3 docks.

  Here are the relevant kernel log messages:

  Feb 24 16:42:38 ubuntu kernel: xhci_hcd :0e:00.0: ERROR Transfer event 
TRB DMA ptr not part of current TD ep_index 2 comp_code 13
  Feb 24 16:42:38 ubuntu kernel: xhci_hcd :0e:00.0: Looking for event-dma 
0004777d9010 trb-start 000475a14fe0 trb-end 000475a14fe0 seg-start 
000475a14000 seg-end 000475a14ff0
  Feb 24 16:42:38 ubuntu kernel: xhci_hcd :0e:00.0: ERROR Transfer event 
TRB DMA ptr not part of current TD ep_index 2 comp_code 13
  Feb 24 16:42:38 ubuntu kernel: xhci_hcd :0e:00.0: Looking for event-dma 
0004777d9020 trb-start 000475a14fe0 trb-end 000475a14fe0 seg-start 
000475a14000 seg-end 000475a14ff0
  Feb 24 16:42:38 ubuntu kernel: xhci_hcd :0e:00.0: ERROR Transfer event 
TRB DMA ptr not part of current TD ep_index 2 comp_code 13
  Feb 24 16:42:38 ubuntu kernel: xhci_hcd :0e:00.0: Looking for event-dma 
0004777d9030 trb-start 000475a14fe0 trb-end 000475a14fe0 seg-start 
000475a14000 seg-end 000475a14ff0
  Feb 24 16:42:38 ubuntu kernel: xhci_hcd :0e:00.0: ERROR Transfer event 
TRB DMA ptr not part of current TD ep_index 2 comp_code 13
  Feb 24 16:42:38 ubuntu kernel: xhci_hcd :0e:00.0: Looking for event-dma 
0004777d9040 trb-start 000475a14fe0 trb-end 000475a14fe0 seg-start 
000475a14000 seg-end 000475a14ff0
  Feb 24 16:42:38 ubuntu kernel: xhci_hcd :0e:00.0: ERROR Transfer event 
TRB DMA ptr not part of current TD ep_index 2 comp_code 13
  Feb 24 16:42:38 ubuntu kernel: xhci_hcd :0e:00.0: Looking for event-dma 
0004777d9050 trb-start 000475a14fe0 trb-end 000475a14fe0 seg-start 
000475a14000 seg-end 000475a14ff0
  Feb 24 16:42:38 ubuntu kernel: xhci_hcd :0e:00.0: ERROR Transfer event 
TRB DMA ptr not part of current TD ep_index 2 comp_code 13
  Feb 24 16:42:38 ubuntu kernel: xhci_hcd :0e:00.0: Looking for event-dma 
0004777d9060 trb-start 000475a14fe0 trb-end 000475a14fe0 seg-start 
000475a14000 seg-end 000475a14ff0
  Feb 24 16:42:39 ubuntu kernel: xhci_hcd :0e:00.0: ERROR Transfer event 
TRB DMA ptr not part of current TD ep_index 2 comp_code 13
  Feb 24 16:42:39 ubuntu kernel: xhci_hcd :0e:00.0: Looking for event-dma 
0004777d9070 trb-start 000475a14fe0 trb-end 000475a14fe0 seg-start 
000475a14

[Kernel-packages] [Bug 1714065] [NEW] ZFS NULL pointer dereference

[Robert C Jennings]

Public bug reported:

I am using a file-backed ZFS pool for LXD containers.  I have a few
running and I got a few ZFS null pointer dereferences that make the
system unusable.

ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: linux-image-4.10.0-33-generic 4.10.0-33.37
ProcVersionSignature: Ubuntu 4.10.0-33.37-generic 4.10.17
Uname: Linux 4.10.0-33-generic x86_64
NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
ApportVersion: 2.20.4-0ubuntu4.5
Architecture: amd64
Date: Wed Aug 30 13:00:37 2017
InstallationDate: Installed on 2017-04-21 (130 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Beta amd64 (20170404)
MachineType: Micro-Star International Co., Ltd MS-7A34
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcFB: 0 amdgpudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-33-generic.efi.signed 
root=UUID=1bf886cb-50ea-4487-a660-07d91bbb51fc ro quiet splash vt.handoff=7
PulseList:
 Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
 No PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
 linux-restricted-modules-4.10.0-33-generic N/A
 linux-backports-modules-4.10.0-33-generic  N/A
 linux-firmware 1.164.1
RfKill:
 
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 06/22/2017
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1.60
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: B350 TOMAHAWK (MS-7A34)
dmi.board.vendor: Micro-Star International Co., Ltd
dmi.board.version: 1.0
dmi.chassis.asset.tag: To be filled by O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: Micro-Star International Co., Ltd
dmi.chassis.version: 1.0
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.60:bd06/22/2017:svnMicro-StarInternationalCo.,Ltd:pnMS-7A34:pvr1.0:rvnMicro-StarInternationalCo.,Ltd:rnB350TOMAHAWK(MS-7A34):rvr1.0:cvnMicro-StarInternationalCo.,Ltd:ct3:cvr1.0:
dmi.product.name: MS-7A34
dmi.product.version: 1.0
dmi.sys.vendor: Micro-Star International Co., Ltd

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


** Tags: amd64 apport-bug zesty

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

Title:
  ZFS NULL pointer dereference

Status in linux package in Ubuntu:
  New

Bug description:
  I am using a file-backed ZFS pool for LXD containers.  I have a few
  running and I got a few ZFS null pointer dereferences that make the
  system unusable.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: linux-image-4.10.0-33-generic 4.10.0-33.37
  ProcVersionSignature: Ubuntu 4.10.0-33.37-generic 4.10.17
  Uname: Linux 4.10.0-33-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  Date: Wed Aug 30 13:00:37 2017
  InstallationDate: Installed on 2017-04-21 (130 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Beta amd64 (20170404)
  MachineType: Micro-Star International Co., Ltd MS-7A34
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-33-generic.efi.signed 
root=UUID=1bf886cb-50ea-4487-a660-07d91bbb51fc ro quiet splash vt.handoff=7
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-33-generic N/A
   linux-backports-modules-4.10.0-33-generic  N/A
   linux-firmware 1.164.1
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/22/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.60
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: B350 TOMAHAWK (MS-7A34)
  dmi.board.vendor: Micro-Star International Co., Ltd
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: To be filled by O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Micro-Star International Co., Ltd
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.60:bd06/22/2017:svnMicro-StarInternationalCo.,Ltd:pnMS-7A34:pvr1.0:rvnMicro-StarInternationalCo.,Ltd:rnB350TOMAHAWK(MS-7A34):rvr1.0:cvnMicro-StarInternationalCo.,Ltd:ct3:cvr1.0:
  dmi.product.name: MS-7A34
  dmi.product.version: 1.0
  dmi.sys.vendor: Micro-Star International Co., Ltd

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

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

[Kernel-packages] [Bug 1714065] Re: ZFS NULL pointer dereference

[Robert C Jennings]

Kernel log attached.  There are a few ZFS kernel BUG traces included NPE
on dbuf_destroy() and zfs_acl_release_nodes().

** Attachment added: "kern.log"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1714065/+attachment/4941492/+files/kern.log

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

Title:
  ZFS NULL pointer dereference

Status in linux package in Ubuntu:
  New

Bug description:
  I am using a file-backed ZFS pool for LXD containers.  I have a few
  running and I got a few ZFS null pointer dereferences that make the
  system unusable.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: linux-image-4.10.0-33-generic 4.10.0-33.37
  ProcVersionSignature: Ubuntu 4.10.0-33.37-generic 4.10.17
  Uname: Linux 4.10.0-33-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  Date: Wed Aug 30 13:00:37 2017
  InstallationDate: Installed on 2017-04-21 (130 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Beta amd64 (20170404)
  MachineType: Micro-Star International Co., Ltd MS-7A34
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-33-generic.efi.signed 
root=UUID=1bf886cb-50ea-4487-a660-07d91bbb51fc ro quiet splash vt.handoff=7
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-33-generic N/A
   linux-backports-modules-4.10.0-33-generic  N/A
   linux-firmware 1.164.1
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/22/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.60
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: B350 TOMAHAWK (MS-7A34)
  dmi.board.vendor: Micro-Star International Co., Ltd
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: To be filled by O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Micro-Star International Co., Ltd
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.60:bd06/22/2017:svnMicro-StarInternationalCo.,Ltd:pnMS-7A34:pvr1.0:rvnMicro-StarInternationalCo.,Ltd:rnB350TOMAHAWK(MS-7A34):rvr1.0:cvnMicro-StarInternationalCo.,Ltd:ct3:cvr1.0:
  dmi.product.name: MS-7A34
  dmi.product.version: 1.0
  dmi.sys.vendor: Micro-Star International Co., Ltd

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1714065/+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 1702998] Re: Ubuntu 17.04: Guest crashed @writeback_sb_inodes+0x310/0x590

[Joseph Salisbury]

I'll build a test kernel and post a link to it shortly.

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

Title:
  Ubuntu 17.04: Guest crashed @writeback_sb_inodes+0x310/0x590

Status in The Ubuntu-power-systems project:
  Triaged
Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Zesty:
  In Progress

Bug description:
  == Comment: #0 - Lata Kuntal  - 2017-03-03 00:50:54 ==
  Ubuntu 17.04 guest dropped at xmon after crashing at 
writeback_sb_inodes+0x310/0x590. 
  The guest is having XFS rootfs and NPIV disk. It crashed after 30+ hrs of 
BASE and NFS stress test .

  Crash logs
  ===
  root@guskvm:~# virsh console gusg1 --force
  Connected to domain gusg1
  Escape character is ^]

  0:mon>
  0:mon> t
  [c000a4bc7940] c036f790 writeback_sb_inodes+0x310/0x590
  [c000a4bc7a50] c036faf4 __writeback_inodes_wb+0xe4/0x150
  [c000a4bc7ab0] c036ff1c wb_writeback+0x2cc/0x440
  [c000a4bc7b80] c0370c30 wb_workfn+0x150/0x560
  [c000a4bc7c90] c00ed8c0 process_one_work+0x2b0/0x5a0
  [c000a4bc7d20] c00edc58 worker_thread+0xa8/0x650
  [c000a4bc7dc0] c00f67b4 kthread+0x154/0x1a0
  [c000a4bc7e30] c000b4e8 ret_from_kernel_thread+0x5c/0x74
  0:mon> r
  R00 = c036f790   R16 = c000eca70300
  R01 = c000a4bc78e0   R17 = c000f7035240
  R02 = c143c900   R18 = 
  R03 = c000f7035150   R19 = 
  R04 = 0019   R20 = c000a4bc4000
  R05 = 0100   R21 = ff7f
  R06 =    R22 = c433d758
  R07 =    R23 = c433d738
  R08 = 00034995   R24 = 
  R09 =    R25 = 
  R10 = 8000   R26 = c000f70351d8
  R11 = c000a4bc7a40   R27 = 
  R12 = 2200   R28 = 0001
  R13 = cfb8   R29 = c433d728
  R14 =    R30 = c000f7035150
  R15 = c000f70351d8   R31 = 
  pc  = c036c120 locked_inode_to_wb_and_lock_list+0x50/0x290
  cfar= c00b2a14 kvmppc_save_tm+0x168/0x16c
  lr  = c036f790 writeback_sb_inodes+0x310/0x590
  msr = 80009033   cr  = 24002482
  ctr = c0381e30   xer =    trap =  300
  dar =    dsisr = 4000
  0:mon> e
  cpu 0x0: Vector: 300 (Data Access) at [c000a4bc7660]
  pc: c036c120: locked_inode_to_wb_and_lock_list+0x50/0x290
  lr: c036f790: writeback_sb_inodes+0x310/0x590
  sp: c000a4bc78e0
 msr: 80009033
 dar: 0
   dsisr: 4000
current = 0xc000fbe96000
paca= 0xcfb8   softe: 0irq_happened: 0x01
  pid   = 17305, comm = kworker/u16:0
  Linux version 4.10.0-8-generic (buildd@bos01-ppc64el-001) (gcc version 6.3.0 
20161229 (Ubuntu 6.3.0-2ubuntu1) ) #10-Ubuntu SMP Mon Feb 13 14:00:06 UTC 2017 
(Ubuntu 4.10.0-8.10-generic 4.10.0-rc8)
  0:mon> d
      ||
  0:mon>

  
  Host and guest kernel build
  =
  4.10.0-8-generic

  
  OPAL firmware version
  
T side: FW860.20 (SV860_078)
Boot side : FW860.20 (SV860_078)

  
  == Comment: #4 - VIPIN K. PARASHAR  - 2017-03-03 
02:55:20 ==
  [140071.761707] Adding 153536k swap on /dev/loop0.  Priority:-2 extents:1 
across:153536k FS
  [140072.153143] Adding 153472k swap on /dev/loop0.  Priority:-2 extents:1 
across:153472k FS
  [140072.441833] Unable to handle kernel paging request for data at address 
0x
  [140072.442064] Faulting instruction address: 0xc036c120
  0:mon>

  0:mon> e
  cpu 0x0: Vector: 300 (Data Access) at [c000a4bc7660]
  pc: c036c120: locked_inode_to_wb_and_lock_list+0x50/0x290
  lr: c036f790: writeback_sb_inodes+0x310/0x590
  sp: c000a4bc78e0
 msr: 80009033
 dar: 0
   dsisr: 4000
current = 0xc000fbe96000
paca= 0xcfb8 softe: 0irq_happened: 0x01
  pid   = 17305, comm = kworker/u16:0
  Linux version 4.10.0-8-generic (buildd@bos01-ppc64el-001) (gcc version 6.3.0 
20161229 (Ubuntu 6.3.0-2ubuntu1) ) #10-Ubuntu SMP Mon Feb 13 14:00:06 UTC 2017 
(Ubuntu 4.10.0-8.10-generic 4.10.0-rc8)
  0:mon> t
  [c000a4bc7940] c036f790 writeback_sb_inodes+0x310/0x590
  [c000a4bc7a50] c036faf4 __writeback_inodes_wb+0xe4/0x150
  [c000a4bc7ab0] c036ff1c wb_writeback+0x2cc/0x440
  [c000a4bc7b80] c0370c30 wb_workfn+0x150/0x560
  [c000a4bc7c90] c00ed8c0 process_one_work+0x2b0/0x5a0
  [c000a4bc7d20] c00edc58 worker_thread+0xa8/0x650
  [c000a4bc7dc0] c00f67b4 kthread+0x154/0x1a0
  

[Kernel-packages] [Bug 1714065] Status changed to Confirmed

[Ubuntu Kernel Bot]

This change was made by a bot.

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

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

Title:
  ZFS NULL pointer dereference

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I am using a file-backed ZFS pool for LXD containers.  I have a few
  running and I got a few ZFS null pointer dereferences that make the
  system unusable.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: linux-image-4.10.0-33-generic 4.10.0-33.37
  ProcVersionSignature: Ubuntu 4.10.0-33.37-generic 4.10.17
  Uname: Linux 4.10.0-33-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  Date: Wed Aug 30 13:00:37 2017
  InstallationDate: Installed on 2017-04-21 (130 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Beta amd64 (20170404)
  MachineType: Micro-Star International Co., Ltd MS-7A34
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-33-generic.efi.signed 
root=UUID=1bf886cb-50ea-4487-a660-07d91bbb51fc ro quiet splash vt.handoff=7
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-33-generic N/A
   linux-backports-modules-4.10.0-33-generic  N/A
   linux-firmware 1.164.1
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/22/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.60
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: B350 TOMAHAWK (MS-7A34)
  dmi.board.vendor: Micro-Star International Co., Ltd
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: To be filled by O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Micro-Star International Co., Ltd
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.60:bd06/22/2017:svnMicro-StarInternationalCo.,Ltd:pnMS-7A34:pvr1.0:rvnMicro-StarInternationalCo.,Ltd:rnB350TOMAHAWK(MS-7A34):rvr1.0:cvnMicro-StarInternationalCo.,Ltd:ct3:cvr1.0:
  dmi.product.name: MS-7A34
  dmi.product.version: 1.0
  dmi.sys.vendor: Micro-Star International Co., Ltd

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1714065/+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 1713467] Re: linux-aws: 4.4.0-1033.42 -proposed tracker

[Brad Figg]

** Changed in: kernel-sru-workflow/security-signoff
   Status: New => Confirmed

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

Title:
  linux-aws: 4.4.0-1033.42 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Confirmed
Status in Kernel SRU Workflow certification-testing series:
  Confirmed
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  Confirmed
Status in Kernel SRU Workflow upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-aws package in Ubuntu:
  Invalid
Status in linux-aws source package in Xenial:
  Confirmed

Bug description:
  This bug is for tracking the  upload package.
  This bug will contain status and testing results related to that
  upload.

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1713462
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1713467/+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 1713456] Re: linux: 3.13.0-130.179 -proposed tracker

[Brad Figg]

** Changed in: kernel-sru-workflow/automated-testing
   Status: New => Confirmed

** Changed in: kernel-sru-workflow/certification-testing
   Status: New => Confirmed

** Changed in: kernel-sru-workflow/promote-to-proposed
   Status: Fix Committed => Fix Released

** Changed in: kernel-sru-workflow/regression-testing
   Status: New => Confirmed

** Changed in: kernel-sru-workflow/security-signoff
   Status: New => Confirmed

** Changed in: kernel-sru-workflow/verification-testing
   Status: New => Confirmed

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  backports: 1713458
  derivatives:
- kernel-stable-phase-changed:Tuesday, 29. August 2017 16:01 UTC
- kernel-stable-phase:Uploaded
- 
  -- swm properties --
  boot-testing-requested: true
  phase: Uploaded
+ kernel-stable-phase-changed:Wednesday, 30. August 2017 19:01 UTC
+ kernel-stable-phase:Promoted to proposed

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  backports: 1713458
  derivatives:
  -- swm properties --
  boot-testing-requested: true
- phase: Uploaded
- kernel-stable-phase-changed:Wednesday, 30. August 2017 19:01 UTC
- kernel-stable-phase:Promoted to proposed
+ phase: Promoted to proposed
+ proposed-announcement-sent: true
+ proposed-testing-requested: true

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

Title:
  linux: 3.13.0-130.179 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Confirmed
Status in Kernel SRU Workflow certification-testing series:
  Confirmed
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  Confirmed
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Trusty:
  Confirmed

Bug description:
  This bug is for tracking the  upload package.
  This bug will contain status and testing results related to that
  upload.

  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  backports: 1713458
  derivatives:
  -- swm properties --
  boot-testing-requested: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1713456/+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 1713462] Re: linux: 4.4.0-94.117 -proposed tracker

[Brad Figg]

** Changed in: kernel-sru-workflow/automated-testing
   Status: New => Confirmed

** Changed in: kernel-sru-workflow/certification-testing
   Status: New => Confirmed

** Changed in: kernel-sru-workflow/promote-to-proposed
   Status: Fix Committed => Fix Released

** Changed in: kernel-sru-workflow/regression-testing
   Status: New => Confirmed

** Changed in: kernel-sru-workflow/security-signoff
   Status: New => Confirmed

** Changed in: kernel-sru-workflow/verification-testing
   Status: New => Confirmed

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  backports: 1713463
  derivatives: 1713464,1713465,1713467,1713468,1713469
- kernel-stable-phase-changed:Tuesday, 29. August 2017 09:02 UTC
- kernel-stable-phase:Uploaded
- 
  -- swm properties --
  boot-testing-requested: true
  phase: Uploaded
+ kernel-stable-phase-changed:Wednesday, 30. August 2017 19:03 UTC
+ kernel-stable-phase:Promoted to proposed

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  backports: 1713463
  derivatives: 1713464,1713465,1713467,1713468,1713469
  -- swm properties --
  boot-testing-requested: true
- phase: Uploaded
- kernel-stable-phase-changed:Wednesday, 30. August 2017 19:03 UTC
- kernel-stable-phase:Promoted to proposed
+ phase: Promoted to proposed
+ proposed-announcement-sent: true
+ proposed-testing-requested: true

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

Title:
  linux: 4.4.0-94.117 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Confirmed
Status in Kernel SRU Workflow certification-testing series:
  Confirmed
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  Confirmed
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  Confirmed

Bug description:
  This bug is for tracking the  upload package.
  This bug will contain status and testing results related to that
  upload.

  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  backports: 1713463
  derivatives: 1713464,1713465,1713467,1713468,1713469
  -- swm properties --
  boot-testing-requested: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1713462/+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 1713458] Re: linux-lts-trusty: 3.13.0-130.179~precise1 -proposed tracker

[Brad Figg]

** Changed in: kernel-sru-workflow/promote-to-proposed
   Status: New => Confirmed

** Tags added: block-proposed-precise

** Tags added: block-proposed

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

Title:
  linux-lts-trusty: 3.13.0-130.179~precise1 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  New
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Confirmed
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-lts-trusty package in Ubuntu:
  Invalid
Status in linux-lts-trusty source package in Precise:
  Confirmed

Bug description:
  This bug is for tracking the  upload package.
  This bug will contain status and testing results related to that
  upload.

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1713456
  phase: Uploaded

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1713458/+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 1701137] Re: enable ARCH_SUNXI (and friends) in arm64 kernel .config

[Seth Forshee]

I've applied the config options as in your config to our 4.13 "unstable"
kernel. There were a few differences. First a couple of new options
which I set as follows:

 CONFIG_DWMAC_SUN8I=m
 CONFIG_SUN8I_A83T_CCU=y

And the CONFIG_SUNXI_CCU_* options have been removed. Let me know if
anything looks wrong.

https://git.launchpad.net/~ubuntu-
kernel/ubuntu/+source/linux/+git/unstable

** Changed in: linux (Ubuntu Artful)
   Status: In Progress => Fix Committed

** Changed in: linux (Ubuntu Artful)
 Assignee: (unassigned) => Seth Forshee (sforshee)

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

Title:
  enable ARCH_SUNXI (and friends) in arm64 kernel .config

Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Artful:
  Fix Committed

Bug description:
  The mainline support for the ARM64 Allwinner SoCs (featured on the Pine64 
boards and the Pinebook notebook, for instance, as well as other development 
boards like the BananaPi-M64) has come a long way by now, since 4.11 we have 
MMC and USB support working.
  Now can we just enable the proper .config bits to make the official Ubuntu 
kernel support those boards? The latest mainline U-Boot can load an EFI grub 
from some UEFI ESP partition, so any standard EFI installer should work.
  Apart from some minor hiccup (a missing MBR bootable flag/MBR at all) this 
works already with the Debian-testing netinst installer.
  The config symbols needed for decent support are (all enabled by the latest 
Debian kernel and the official mainline defconfig):
  ARCH_SUNXI=y
  CONFIG_USB_MUSB_SUNXI=m
  CONFIG_MMC_SUNXI=m
  CONFIG_RTC_DRV_SUN6I=y
  CONFIG_PHY_SUN4I_USB=y

  Those enable MMC and USB (the mandatory clocks, pinctrl and UART are enabled 
by default) and make those boards quite usable already. The on-SoC Ethernet 
driver will probably be merged into 4.13-rc1.
  Optionally:
  CONFIG_I2C_MV64XXX=m
  CONFIG_SPI_SUN6I=m
  give us I2C and SPI support as well.

  So can we add those symbols to the Ubuntu kernel .config to give users
  an out-of-the-box experience?

  Cheers,
  Andre.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1701137/+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 1467190] Re: No audio over DisplayPort MST

[MR Zenwiz]

I have an HP 8740w that has the same problem on Xenial LTS (16.04.3)
with the HWE (4.10) kernel, although I have also tested it on the 4.4
generic kernel with the same results.

The sound configuration shows only analog audio possibilities (5, IIRC),
whereas on my older HP (stolen) and my broken ASUS (when it was working)
both showed 7 or more options, including several digital options, many
of which worked just fine through the HDMI TV at the other end.

I have used four different DP-HDMI adapters, 3 which were non-active and
the newest one, which is an active adapter from SIIG - no digital sound
at all.

What this does is it makes it impossible to get, e.g., movie sound on
the HDMI TV set, which means I am stuck with the notebook speakers -
they're nice, but it's just not the same, or a plug-in set, which should
never be necessary when the hardware supports the right kind of sound.

If I put the Windows hard drive the system cam with back into the
notebook and run from there, the sound is just fine.  That was strictly
for test purposes - I never use Windows if I can avoid it, which is
better than 99% of the time.

I would really appreciate a fix.  I can attach whatever information you
need on request.

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

Title:
  No audio over DisplayPort MST

Status in linux package in Ubuntu:
  Triaged

Bug description:
  I have a Lenovo ThinkPad E540 with an Intel Haswell (4th Gen) HD
  graphics controller connected to a OneLink Pro Dock. The Dock uses
  DisplayPort (DP) 1.2 MST (multi stream transport) to provide both a DP
  and a DVI port. My monitor is connected to the DP.

  When I used kernels <= 3.16 audio worked fine, but the monitor would
  flicker heavily. So I installed linux-lts-vivid (3.19) which fixed the
  graphics problem (now I can see various DP? outputs in xrandr as
  opposed to one before), but there is no DP audio output to chose
  anymore.

  I also tested the latest mainline kernel 4.1-rc8, where this bug still
  exists. To further investigate I got these version's kernel sources,
  applied 4 patches by Dave Airlie from the intel-gfx mailing list [1]
  and tested this build (4.1-rc8+), which fixed the problem! I can play
  sound over DP, the same way I can over HDMI or DP without MST.

  I hope it is possible to backport these changes!

  [1] haswell displayport MST audio support
  http://www.spinics.net/lists/intel-gfx/msg68973.html

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.19.0-22-generic 3.19.0-22.22~14.04.1
  ProcVersionSignature: Ubuntu 3.19.0-22.22~14.04.1-generic 3.19.8-ckt1
  Uname: Linux 3.19.0-22-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.11
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sun Jun 21 01:44:30 2015
  InstallationDate: Installed on 2014-01-06 (530 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  SourcePackage: linux-lts-vivid
  UpgradeStatus: Upgraded to trusty on 2014-06-12 (373 days ago)
  --- 
  ApportVersion: 2.20.1-0ubuntu2.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  stefan 2509 F pulseaudio
   /dev/snd/controlC1:  stefan 2509 F pulseaudio
   /dev/snd/controlC0:  stefan 2509 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=2ecc68b9-65e3-4cee-9b2a-d41ff651e4e8
  InstallationDate: Installed on 2014-01-06 (1077 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  MachineType: LENOVO 20C6S00200
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-57-generic.efi.signed 
root=/dev/mapper/ubuntuvg-root ro nogpumanager quiet splash pcie_aspm=force 
intel_pstate=enable
  ProcVersionSignature: Ubuntu 4.4.0-57.78-generic 4.4.35
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-57-generic N/A
   linux-backports-modules-4.4.0-57-generic  N/A
   linux-firmware1.157.6
  Tags:  xenial
  Uname: Linux 4.4.0-57-generic x86_64
  UpgradeStatus: Upgraded to xenial on 2016-12-15 (3 days ago)
  UserGroups: adm bumblebee cdrom dip lp lpadmin plugdev sambashare staff sudo 
vboxusers wireshark
  _MarkForUpload: True
  dmi.bios.date: 09/23/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: J9ET9EWW (2.24 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20C6S00200
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrJ9ET9EWW(2.24):bd09/23/2016:svnLENOVO:pn20C6S00200:pvrThinkPadEdgeE540:rvnLENOVO:rn20C6S00200:rvrNotAvailable:cvn

[Kernel-packages] [Bug 1467190] Re: No audio over DisplayPort MST

[MR Zenwiz]

Please forgive my typos.  I usually catch those...

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

Title:
  No audio over DisplayPort MST

Status in linux package in Ubuntu:
  Triaged

Bug description:
  I have a Lenovo ThinkPad E540 with an Intel Haswell (4th Gen) HD
  graphics controller connected to a OneLink Pro Dock. The Dock uses
  DisplayPort (DP) 1.2 MST (multi stream transport) to provide both a DP
  and a DVI port. My monitor is connected to the DP.

  When I used kernels <= 3.16 audio worked fine, but the monitor would
  flicker heavily. So I installed linux-lts-vivid (3.19) which fixed the
  graphics problem (now I can see various DP? outputs in xrandr as
  opposed to one before), but there is no DP audio output to chose
  anymore.

  I also tested the latest mainline kernel 4.1-rc8, where this bug still
  exists. To further investigate I got these version's kernel sources,
  applied 4 patches by Dave Airlie from the intel-gfx mailing list [1]
  and tested this build (4.1-rc8+), which fixed the problem! I can play
  sound over DP, the same way I can over HDMI or DP without MST.

  I hope it is possible to backport these changes!

  [1] haswell displayport MST audio support
  http://www.spinics.net/lists/intel-gfx/msg68973.html

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.19.0-22-generic 3.19.0-22.22~14.04.1
  ProcVersionSignature: Ubuntu 3.19.0-22.22~14.04.1-generic 3.19.8-ckt1
  Uname: Linux 3.19.0-22-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.11
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sun Jun 21 01:44:30 2015
  InstallationDate: Installed on 2014-01-06 (530 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  SourcePackage: linux-lts-vivid
  UpgradeStatus: Upgraded to trusty on 2014-06-12 (373 days ago)
  --- 
  ApportVersion: 2.20.1-0ubuntu2.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  stefan 2509 F pulseaudio
   /dev/snd/controlC1:  stefan 2509 F pulseaudio
   /dev/snd/controlC0:  stefan 2509 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=2ecc68b9-65e3-4cee-9b2a-d41ff651e4e8
  InstallationDate: Installed on 2014-01-06 (1077 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  MachineType: LENOVO 20C6S00200
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-57-generic.efi.signed 
root=/dev/mapper/ubuntuvg-root ro nogpumanager quiet splash pcie_aspm=force 
intel_pstate=enable
  ProcVersionSignature: Ubuntu 4.4.0-57.78-generic 4.4.35
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-57-generic N/A
   linux-backports-modules-4.4.0-57-generic  N/A
   linux-firmware1.157.6
  Tags:  xenial
  Uname: Linux 4.4.0-57-generic x86_64
  UpgradeStatus: Upgraded to xenial on 2016-12-15 (3 days ago)
  UserGroups: adm bumblebee cdrom dip lp lpadmin plugdev sambashare staff sudo 
vboxusers wireshark
  _MarkForUpload: True
  dmi.bios.date: 09/23/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: J9ET9EWW (2.24 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20C6S00200
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrJ9ET9EWW(2.24):bd09/23/2016:svnLENOVO:pn20C6S00200:pvrThinkPadEdgeE540:rvnLENOVO:rn20C6S00200:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 20C6S00200
  dmi.product.version: ThinkPad Edge E540
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1467190/+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 332467] 💰this is simply an unforgettable place

[ixzel]

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

Content-Transfer-Encoding: base64
Content-Type: text/plain; charset="utf-8"

RGVhciEgDQoNCkknbSAgc28gaGFwcHkgdG8gdGVsbCB5b3UgIGFib3V0IGFuIGV4dHJlbWVseSBu
aWNlIHBsYWNlICBJJ3ZlIHdlbnQgdG8gIGxhc3QgbmlnaHQsIGl0J3Mgc2ltcGx5ICByZW1hcmth
YmxlISAgSnVzdCB0YWtlIGEgbG9vayBodHRwOi8vd3d3LmZhbWlsbGUtdHJhdmVsLmNvbS9pbnRl
cnByZXQucGhwP1VFOHpNekkwTmpkQVluVm5jeTVzWVhWdVkyaHdZV1F1Ym1WMA0KDQpXaXNoZXMs
IENhbWlsbGUgTW9zZWxleQ0KDQo=

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

Title:
  package linux-image-2.6.27-7-generic 2.6.27-7.14 failed to
  install/upgrade: unable to make backup link of
  `./boot/vmlinuz-2.6.27-7-generic' before installing new version:
  Operation not permitted

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Automated bug report information should be attached. Fresh install
  using wubi. Applied 259 updates after opening OpenOffice.org twice and
  file browsing but no other system usage.

  ProblemType: Package
  Architecture: i386
  DistroRelease: Ubuntu 8.10
  ErrorMessage: unable to make backup link of `./boot/vmlinuz-2.6.27-7-generic' 
before installing new version: Operation not permitted
  LsUsb:
   Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 002 Device 002: ID 046d:c001 Logitech, Inc. N48/M-BB48 [FirstMouse Plus]
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Package: linux-image-2.6.27-7-generic 2.6.27-7.14
  ProcCmdLine: User Name=UUID=1542-16FE loop=/hostname/disks/home/username.disk 
ro ROOTFLAGS=sync quiet splash
  ProcVersionSignature: Ubuntu 2.6.27-7.14-generic
  SourcePackage: linux
  Title: package linux-image-2.6.27-7-generic 2.6.27-7.14 failed to 
install/upgrade: unable to make backup link of 
`./boot/vmlinuz-2.6.27-7-generic' before installing new version: Operation not 
permitted

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/332467/+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 1635597] Re: Ubuntu16.10:talclp1: Kdump failed with multipath disk

[Thadeu Lima de Souza Cascardo]

I understand there is a fix in artful, as per version 1:1.6.1-2. I am
doing some backport to xenial, will need someone at IBM to test it. In
fact, Louis Bouchard had already asked for testing of a package on his
ppa. Can someone test it? It's at ppa:louis/kdump-tools-multipath.

Regards.
Cascardo.

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

Title:
  Ubuntu16.10:talclp1: Kdump failed with multipath disk

Status in The Ubuntu-power-systems project:
  In Progress
Status in linux package in Ubuntu:
  New
Status in makedumpfile package in Ubuntu:
  Fix Released
Status in linux source package in Trusty:
  New
Status in makedumpfile source package in Trusty:
  Confirmed
Status in linux source package in Xenial:
  New
Status in makedumpfile source package in Xenial:
  Confirmed
Status in linux source package in Zesty:
  New
Status in makedumpfile source package in Zesty:
  Confirmed

Bug description:
  Problem  Description
  ==
  On talclp1, I enabled kdump. But kdump failed and it drop to BusyBox.

  root@talclp1:~# echo c> /proc/sysrq-trigger
  [  132.643690] sysrq: SysRq : Trigger a crash
  [  132.643739] Unable to handle kernel paging request for data at address 
0x
  [  132.643745] Faulting instruction address: 0xc05c28f4
  [  132.643749] Oops: Kernel access of bad area, sig: 11 [#1]
  [  132.643753] SMP NR_CPUS=2048 NUMA pSeries
  [  132.643758] Modules linked in: fuse ufs qnx4 hfsplus hfs minix ntfs msdos 
jfs rpadlpar_io rpaphp rpcsec_gss_krb5 nfsv4 dccp_diag cifs nfs dns_resolver 
dccp tcp_diag fscache udp_diag inet_diag unix_diag af_packet_diag netlink_diag 
binfmt_misc xfs libcrc32c pseries_rng rng_core ghash_generic gf128mul 
vmx_crypto sg nfsd auth_rpcgss nfs_acl lockd grace sunrpc ip_tables x_tables 
autofs4 ext4 crc16 jbd2 fscrypto mbcache crc32c_generic btrfs xor raid6_pq 
dm_round_robin sr_mod sd_mod cdrom ses enclosure scsi_transport_sas ibmveth 
crc32c_vpmsum ipr scsi_dh_emc scsi_dh_rdac scsi_dh_alua dm_multipath dm_mod
  [  132.643819] CPU: 49 PID: 10174 Comm: bash Not tainted 4.8.0-15-generic 
#16-Ubuntu
  [  132.643824] task: c00111767080 task.stack: c000d82e
  [  132.643828] NIP: c05c28f4 LR: c05c39d8 CTR: 
c05c28c0
  [  132.643832] REGS: c000d82e3990 TRAP: 0300   Not tainted  
(4.8.0-15-generic)
  [  132.643836] MSR: 80009033   CR: 28242422  
XER: 0001
  [  132.643848] CFAR: c00087d0 DAR:  DSISR: 4200 
SOFTE: 1
  GPR00: c05c39d8 c000d82e3c10 c0f67b00 0063
  GPR04: c0011d04a9b8 c0011d05f7e0 c0047fb0 00015998
  GPR08: 0007 0001  0001
  GPR12: c05c28c0 c7b4b900  2200
  GPR16: 10170dc8 01002b566368 10140f58 100c7570
  GPR20:  1017dd58 10153618 1017b608
  GPR24: 3e87a294 0001 c0ebff60 0004
  GPR28: c0ec0320 0063 c0e72a90 
  [  132.643906] NIP [c05c28f4] sysrq_handle_crash+0x34/0x50
  [  132.643911] LR [c05c39d8] __handle_sysrq+0xe8/0x280
  [  132.643914] Call Trace:
  [  132.643917] [c000d82e3c10] [c0a245e8] 0xc0a245e8 
(unreliable)
  [  132.643923] [c000d82e3c30] [c05c39d8] __handle_sysrq+0xe8/0x280
  [  132.643928] [c000d82e3cd0] [c05c4188] 
write_sysrq_trigger+0x78/0xa0
  [  132.643935] [c000d82e3d00] [c03ad770] proc_reg_write+0xb0/0x110
  [  132.643941] [c000d82e3d50] [c030fc3c] __vfs_write+0x6c/0xe0
  [  132.643946] [c000d82e3d90] [c0311144] vfs_write+0xd4/0x240
  [  132.643950] [c000d82e3de0] [c0312e5c] SyS_write+0x6c/0x110
  [  132.643957] [c000d82e3e30] [c00095e0] system_call+0x38/0x108
  [  132.643961] Instruction dump:
  [  132.643963] 38425240 7c0802a6 f8010010 f821ffe1 6000 6000 3d220019 
3949ba60
  [  132.643972] 3921 912a 7c0004ac 3940 <992a> 38210020 
e8010010 7c0803a6
  [  132.643981] ---[ end trace eed6bbcd2c3bdfdf ]---
  [  132.646105]
  [  132.646176] Sending IPI to other CPUs
  [  132.647490] IPI complete
  I'm in purgatory
   -> smp_release_cpus()
  spinning_secondaries = 104
   <- smp_release_cpus()
  [2.011346] alg: hash: Test 1 failed for crc32c-vpmsum
  [2.729254] sd 0:2:0:0: [sda] Assuming drive cache: write through
  [2.731554] sd 1:2:5:0: [sdn] Assuming drive cache: write through
  [2.739087] sd 1:2:4:0: [sdm] Assuming drive cache: write through
  [2.739089] sd 1:2:6:0: [sdo] Assuming drive cache: write through
  [2.739110] sd 1:2:7:0: [sdp] Assuming drive cache: write through
  [2.739115] sd 1:2:0:0: [sdi] Assuming drive cache: write through
  [2.73912

[Kernel-packages] [Bug 1713462] Re: linux: 4.4.0-94.117 -proposed tracker

[Brad Figg]

** Changed in: kernel-sru-workflow/automated-testing
   Status: Confirmed => 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/1713462

Title:
  linux: 4.4.0-94.117 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Incomplete
Status in Kernel SRU Workflow certification-testing series:
  Confirmed
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  Confirmed
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  Confirmed

Bug description:
  This bug is for tracking the  upload package.
  This bug will contain status and testing results related to that
  upload.

  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  backports: 1713463
  derivatives: 1713464,1713465,1713467,1713468,1713469
  -- swm properties --
  boot-testing-requested: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1713462/+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 1658733] Re: Ubuntu 16.04.2KVM:kdump fails to mount root file system on multipath root device

[Thadeu Lima de Souza Cascardo]

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

In case, louis package does not fix this specific issue, please try
ppa:cascardo/ppa.

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

Title:
  Ubuntu 16.04.2KVM:kdump fails to mount root file system on multipath
  root device

Status in The Ubuntu-power-systems project:
  Confirmed
Status in kexec-tools package in Ubuntu:
  Invalid
Status in makedumpfile package in Ubuntu:
  In Progress
Status in kexec-tools source package in Trusty:
  New
Status in makedumpfile source package in Trusty:
  New
Status in kexec-tools source package in Xenial:
  New
Status in makedumpfile source package in Xenial:
  New
Status in kexec-tools source package in Zesty:
  New
Status in makedumpfile source package in Zesty:
  New

Bug description:
  == Comment: #0 - Richard M. Scheller - 2016-12-14 16:50:26 ==

  ---Problem Description---

  On a KVM guest installed to a multipath root device, the kdump kernel fails 
to mount the root file system.  This error does not occur in a similar guest 
installed to a single path device.
   
  Full console output of the kdump failure is attached.  These messages from 
the output may be relevant:

  Begin: Loading multipath modules ... Success: loaded module dm-multipath.
  done.
  Begin: Loading multipath hardware handlers ... Failure: failed to load module 
sc
  si_dh_alua.
  Failure: failed to load module scsi_dh_rdac.
  Failure: failed to load module scsi_dh_emc.
  done.
  Begin: Starting multipathd ... done.
   
  ---uname output---
  Linux dotg9 4.8.0-32-generic #34~16.04.1-Ubuntu SMP Tue Dec 13 17:01:57 UTC 
2016 ppc64le ppc64le ppc64le GNU/Linux
   
  Machine Type = 8247-22L Ubuntu 16.04.1 KVM guest 
   
   
  ---Steps to Reproduce---
   - Install Ubuntu 16.04.1 to a muiltpath target disk
  - Install kdump-tools package
  - Configure kexec-tools to reserve sufficient RAM for the kdump kernel to 
load (I use 512MB) in /etc/default/grub.d/kexec-tools.cfg
  - Run update-grub
  - Reboot
  - Initiate a system crash using "echo c > /proc/sysrq-trigger"

  == Comment: #12 - Richard M. Scheller - 2016-12-20 20:37:45 ==
  Here is the log level 8 kdump console log requested in comment 10.

  == Comment: #21 - Richard M. Scheller - 2017-01-06 11:04:17 ==
  (In reply to comment #19)
  > Hi, I logged in dotkvm and I couldn't find the guest dotg9. Also, although I
  > found a dotg9.xml in /kte/xml/ it doesn't look like it uses multipath (it
  > uses .img files which I didn't found as disks).
  > 
  > Could you please recreate the guest for further debug? 

  Yes, I recreated the guest with its correct multipath lun
  configuration.  I have also attached the guest XML to this bug.

  > Besides that could you please let us know:
  >  - is the multipath the system's root? I mean / is installed/mounted on the
  > multipath device?

  Yes, the guest has only one disk.  That disk is actually a LUN from a
  fiber channel storage device with two paths on the host side.  I have
  passed through both paths to the guest, so the multipath nature of the
  target disk is known to the guest.

  In other words, the guest sees a multipath device and is using it as a
  multipath device.  The root file system is called /dev/mapper/mpatha-
  part2 on the guest.

  >  - how did you attach the device to the guest?

  Each FC LUN path on the host is mapped to a virtio-scsi controller on
  the guest using LUN passthrough.  (See the guest XML for details on
  this.)

  == Comment: #22 - Mauro Sergio Martins Rodrigues  - 2017-01-11 09:31:38 ==
  I managed to get kdump to mount rootfs and perform its tasks by setting 
KDUMP_CMDLINE_APPEND="nr_cpus=4" parameter in /etc/default/kdump-tools see 
http://pastebin.hursley.ibm.com/8239

  I'm still investigating to figure out what is the reason behind this
  behavior.

  Thanks,

  --
  maurosr

  == Comment: #23 - Mauricio Faria De Oliveira  - 2017-01-11 11:56:40 ==
  Mauro,

  (In reply to comment #22)
  > I managed to get kdump to mount rootfs and perform its tasks by setting
  > KDUMP_CMDLINE_APPEND="nr_cpus=4" parameter in /etc/default/kdump-tools see
  > http://pastebin.hursley.ibm.com/8239
  > 
  > I'm still investigating to figure out what is the reason behind this
  > behavior.
  > 
  > Thanks,
  > 
  > --
  > maurosr

  That would smell like an out of memory condition that is alleviated
  with a smaller number of CPUs allowed for the kernel (so the amount of
  memory associated with per-CPU stuff is less in total).

  Per the bug description, the memory reserved for the crashkernel is
  512MB:

  (In reply to comment #23)
  > - Configure kexec-tools to reserve sufficient RAM for the kdump kernel to
  > load (I use 512MB) in /etc/default/grub.d/kexec-tools.cfg

  That seems low for Power guests/systems. 
  I think it theory is doesn't seem so, but the reality 

[Kernel-packages] [Bug 1655280] Re: ISST-LTE:pVM:roselp4:ubuntu 16.04.2: cp: error reading '/proc/vmcore': Bad address when trying to dump vmcore

[Thadeu Lima de Souza Cascardo]

Hi, Hari.

My understanding is that the kernel should handle that. Otherwise,
whenever the user manually loads a different kdump kernel, a memory
hotplug would cause the default kdump kernel to be loaded, not what the
user has loaded.

Can you comment on that?

Regards.
Cascardo.

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

Title:
  ISST-LTE:pVM:roselp4:ubuntu 16.04.2: cp: error reading '/proc/vmcore':
  Bad address when trying to dump vmcore

Status in The Ubuntu-power-systems project:
  In Progress
Status in linux package in Ubuntu:
  In Progress

Bug description:
  == Comment: #0 - Ping Tian Han  - 2017-01-09 02:51:00 ==
  ---Problem Description---
  Vmcore cannot be saved when triggering bug 150353 on roselp4:

  Copying data   : [  2.0 %] \/usr/sbin/kdump-config: line 
591:  5502 Bus error   makedumpfile $MAKEDUMP_ARGS $vmcore_file 
$KDUMP_CORETEMP
  [  512.833872] kdump-tools[5450]:  * kdump-tools: makedumpfile failed, 
falling back to 'cp'
  [  573.595449] kdump-tools[5450]: cp: error reading '/proc/vmcore': Bad 
address
  [  573.605717] kdump-tools[5450]:  * kdump-tools: failed to save vmcore in 
/var/crash/201701090223
  [  573.765417] kdump-tools[5450]:  * running makedumpfile --dump-dmesg 
/proc/vmcore /var/crash/201701090223/dmesg.201701090223
  [  574.285506] kdump-tools[5450]: The kernel version is not supported.
  [  574.285672] kdump-tools[5450]: The makedumpfile operation may be 
incomplete.
  [  574.285767] kdump-tools[5450]: The dmesg log is saved to 
/var/crash/201701090223/dmesg.201701090223.
  [  574.305422] kdump-tools[5450]: makedumpfile Completed.
  [  574.315363] kdump-tools[5450]:  * kdump-tools: saved dmesg content in 
/var/crash/201701090223
  [  574.615688] kdump-tools[5450]: Mon, 09 Jan 2017 02:24:26 -0600
  [  574.705384] kdump-tools[5450]: Rebooting.
   Stopping ifup for ib0...
  [  OK  ] Stopped ifup for ib0.
  [ 1008.579897] reboot: Restarting system
   
  Contact Information = Ping Tian Han/pt...@cn.ibm.com Carrie 
Mitsuyoshi/carri...@us.ibm.com 
   
  ---uname output---
  Linux roselp4 4.8.0-34-generic #36~16.04.1-Ubuntu SMP Wed Dec 21 18:53:20 UTC 
2016 ppc64le ppc64le ppc64le GNU/Linux
   
  Machine Type = lpar 
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
   1. config kdump on roselp4
  2. try to trigger bug 150353

   
  *Additional Instructions for Ping Tian Han/pt...@cn.ibm.com Carrie 
Mitsuyoshi/carri...@us.ibm.com: 
  -Post a private note with access information to the machine that the bug is 
occuring on.

  == Comment: #3 - Brahadambal Srinivasan  -
  2017-01-10 02:42:25 ==

  root@roselp4:~# cat /proc/cmdline
  BOOT_IMAGE=/boot/vmlinux-4.8.0-34-generic 
root=UUID=0bcf3431-df8b-499c-9a13-33070f242e0c ro splash quiet 
crashkernel=384M-:512M

  root@roselp4:~# dmesg | grep Reser
  [0.00] Reserving 512MB of memory at 128MB for crashkernel (System 
RAM: 21760MB)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1655280/+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 1713467] Re: linux-aws: 4.4.0-1033.42 -proposed tracker

[Steve Beattie]

** Changed in: kernel-sru-workflow/security-signoff
   Status: Confirmed => In Progress

** Changed in: kernel-sru-workflow/security-signoff
 Assignee: Canonical Security Team (canonical-security) => Steve Beattie 
(sbeattie)

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

Title:
  linux-aws: 4.4.0-1033.42 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Confirmed
Status in Kernel SRU Workflow certification-testing series:
  Confirmed
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-aws package in Ubuntu:
  Invalid
Status in linux-aws source package in Xenial:
  Confirmed

Bug description:
  This bug is for tracking the  upload package.
  This bug will contain status and testing results related to that
  upload.

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1713462
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1713467/+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 1713462] Re: linux: 4.4.0-94.117 -proposed tracker

[Steve Beattie]

** Changed in: kernel-sru-workflow/security-signoff
   Status: Confirmed => In Progress

** Changed in: kernel-sru-workflow/security-signoff
 Assignee: Canonical Security Team (canonical-security) => Steve Beattie 
(sbeattie)

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

Title:
  linux: 4.4.0-94.117 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Incomplete
Status in Kernel SRU Workflow certification-testing series:
  Confirmed
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  Confirmed

Bug description:
  This bug is for tracking the  upload package.
  This bug will contain status and testing results related to that
  upload.

  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  backports: 1713463
  derivatives: 1713464,1713465,1713467,1713468,1713469
  -- swm properties --
  boot-testing-requested: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1713462/+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 1713456] Re: linux: 3.13.0-130.179 -proposed tracker

[Steve Beattie]

** Changed in: kernel-sru-workflow/security-signoff
   Status: Confirmed => In Progress

** Changed in: kernel-sru-workflow/security-signoff
 Assignee: Canonical Security Team (canonical-security) => Steve Beattie 
(sbeattie)

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

Title:
  linux: 3.13.0-130.179 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Confirmed
Status in Kernel SRU Workflow certification-testing series:
  Confirmed
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Trusty:
  Confirmed

Bug description:
  This bug is for tracking the  upload package.
  This bug will contain status and testing results related to that
  upload.

  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  backports: 1713458
  derivatives:
  -- swm properties --
  boot-testing-requested: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1713456/+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 1689365] Re: ibmvscsis: Do not send aborted task response

[bugproxy]

** Tags added: bugnameltc-154092 severity-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/1689365

Title:
  ibmvscsis: Do not send aborted task response

Status in The Ubuntu-power-systems project:
  Fix Committed
Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Zesty:
  Fix Released

Bug description:
  [Impact]
  ibmvscsis: Do not send aborted task response

  The driver is sending a response to the actual scsi op that was
  aborted by an abort task TM, while LIO is sending a response to
  the abort task TM.

  ibmvscsis_tgt does not send the response to the client until
  release_cmd time. The reason for this was because if we did it
  at queue_status time, then the client would be free to reuse the
  tag for that command, but we're still using the tag until the
  command is released at release_cmd time, so we chose to delay
  sending the response until then. That then caused this issue, because
  release_cmd is always called, even if queue_status is not.

  SCSI spec says that the initiator that sends the abort task
  TM NEVER gets a response to the aborted op and with the current
  code it will send a response. Thus this fix will remove that response
  if the CMD_T_ABORTED && !CMD_T_TAS.

  Another case with a small timing window is the case where if LIO sends a
  TMR_DOES_NOT_EXIST, and the release_cmd callback is called for the TMR Abort
  cmd before the release_cmd for the (attemped) aborted cmd, then we need to
  ensure that we send the response for the (attempted) abort cmd to the client
  before we send the response for the TMR Abort cmd.

  [Test Case]
  As per comment #11, this requires sending manual abort signals to trigger the 
bug.

  [Fix]
  ibmvscsis: Fix the incorrect req_lim_delta
  ibmvscsis: Clear left-over abort_cmd pointers
  ibmvscsis: Do not send aborted task response
  target: Fix unknown fabric callback queue-full errors

  [Regression Potential]
  Patches are confined to ibmvscsi driver and target driver.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1689365/+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 1714084] [NEW] package zfsutils-linux 0.6.5.6-0ubuntu17 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

[ben-Nabiy Derush]

Public bug reported:

Attempted reinstall of zfsutils-linux

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: zfsutils-linux 0.6.5.6-0ubuntu17
ProcVersionSignature: Ubuntu 4.4.0-92.115-generic 4.4.76
Uname: Linux 4.4.0-92-generic x86_64
NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
ApportVersion: 2.20.1-0ubuntu2.10
Architecture: amd64
Date: Wed Aug 30 15:49:18 2017
ErrorMessage: subprocess installed post-installation script returned error exit 
status 1
InstallationDate: Installed on 2016-07-24 (402 days ago)
InstallationMedia: Ubuntu-MATE 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.2
 apt  1.2.24
SourcePackage: zfs-linux
Title: package zfsutils-linux 0.6.5.6-0ubuntu17 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 1
UpgradeStatus: No upgrade log present (probably fresh install)
modified.conffile..etc.default.zfs: [deleted]

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


** Tags: amd64 apport-package xenial

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

Title:
  package zfsutils-linux 0.6.5.6-0ubuntu17 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 1

Status in zfs-linux package in Ubuntu:
  New

Bug description:
  Attempted reinstall of zfsutils-linux

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: zfsutils-linux 0.6.5.6-0ubuntu17
  ProcVersionSignature: Ubuntu 4.4.0-92.115-generic 4.4.76
  Uname: Linux 4.4.0-92-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  Date: Wed Aug 30 15:49:18 2017
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2016-07-24 (402 days ago)
  InstallationMedia: Ubuntu-MATE 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.24
  SourcePackage: zfs-linux
  Title: package zfsutils-linux 0.6.5.6-0ubuntu17 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.default.zfs: [deleted]

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1714084/+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 1714084] Re: package zfsutils-linux 0.6.5.6-0ubuntu17 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

[Apport retracing service]

** Tags removed: need-duplicate-check

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

Title:
  package zfsutils-linux 0.6.5.6-0ubuntu17 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 1

Status in zfs-linux package in Ubuntu:
  New

Bug description:
  Attempted reinstall of zfsutils-linux

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: zfsutils-linux 0.6.5.6-0ubuntu17
  ProcVersionSignature: Ubuntu 4.4.0-92.115-generic 4.4.76
  Uname: Linux 4.4.0-92-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  Date: Wed Aug 30 15:49:18 2017
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2016-07-24 (402 days ago)
  InstallationMedia: Ubuntu-MATE 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.24
  SourcePackage: zfs-linux
  Title: package zfsutils-linux 0.6.5.6-0ubuntu17 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.default.zfs: [deleted]

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1714084/+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 1710690] Comment bridged from LTC Bugzilla

[bugproxy]

--- Comment From bjki...@us.ibm.com 2017-08-30 16:34 EDT---
This was root caused to be a bug in the aacraid driver, which is used on all 
Boston systems. It is issue that can cause random memory corruption and is 
resolved with this patch:

https://git.kernel.org/pub/scm/linux/kernel/git/mkp/scsi.git/commit/?h=4.13/scsi-fixes&id=1ae948fa4f00f3a2823e7cb19a3049ef27dd6947
("scsi: aacraid: Fix command send race condition")

Can we get a Ubuntu 16.04.3 test kernel built with this change so that
we can load this on our test systems?

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

Title:
  Ubuntu16.04.3: System running network stress crashes with Alignment
  exception

Status in The Ubuntu-power-systems project:
  New
Status in linux package in Ubuntu:
  Incomplete

Bug description:
   State: Open by: nguyenp on 11 August 2017 11:03:32 

  Contact:
  ===
  Paul Nguyen
  nguy...@us.ibm.com

  BMC:
  
  bos1u1

  Firmware Revision : 00.25 
  Firmware Build Time : 20170807BMC MAC address : 0c:c4:7a:f4:4d:60
  PNOR Build Time : 20170729
  CPLD Version : B2.91.00   

  Ubuntu 16.04.3:
  ===
  bos1u1p1

 ver 1.5.4.5 - OS, HTX, Firmware and Machine details

 OS: GNU/Linux
 OS Version: Ubuntu 16.04.3 LTS \n \l
 Kernel Version: 4.11.0-12-generic
HTX Version: htxubuntu-448
  Host Name: bos1u1p1
  Machine Serial No: C819UAF32B2 
 Machine Type/Model: 9006-12C

  root@bos1u1p1:~# dpkg -l |grep mlx
  ii  libmlx4-1  41mlnx1-OFED.4.1.0.1.0.41014   
ppc64el  Userspace driver for Mellanox ConnectX 

  InfiniBand HCAs
  ii  libmlx4-1-dbg  41mlnx1-OFED.4.1.0.1.0.41014   
ppc64el  Debugging symbols for the libmlx4 driver
  ii  libmlx4-dev41mlnx1-OFED.4.1.0.1.0.41014   
ppc64el  Development files for the libmlx4 driver
  ii  libmlx5-1  41mlnx1-OFED.4.1.0.1.3.0.1.41014   
ppc64el  Userspace driver for Mellanox ConnectX 

  InfiniBand HCAs
  ii  libmlx5-1-dbg  41mlnx1-OFED.4.1.0.1.3.0.1.41014   
ppc64el  Debugging symbols for the libmlx5 driver
  ii  libmlx5-dev41mlnx1-OFED.4.1.0.1.3.0.1.41014   
ppc64el  Development files for the libmlx5 driver

  root@bos1u1p1:~# lsscsi
  [0:2:0:0]diskSEAGATE  ST4000NM0034 E005  /dev/sda 
  [0:3:123:0]  enclosu ADAPTEC  Smart Adapter2.99  -
  root@bos1u1p1:~# lspci
  :00:00.0 PCI bridge: IBM Device 04c1
  0001:00:00.0 PCI bridge: IBM Device 04c1
  0002:00:00.0 PCI bridge: IBM Device 04c1
  0002:01:00.0 Ethernet controller: Intel Corporation Ethernet Controller 
X710/X557-AT 10GBASE-T (rev 02)
  0002:01:00.1 Ethernet controller: Intel Corporation Ethernet Controller 
X710/X557-AT 10GBASE-T (rev 02)
  0002:01:00.2 Ethernet controller: Intel Corporation Ethernet Controller 
X710/X557-AT 10GBASE-T (rev 02)
  0002:01:00.3 Ethernet controller: Intel Corporation Ethernet Controller 
X710/X557-AT 10GBASE-T (rev 02)
  0003:00:00.0 PCI bridge: IBM Device 04c1
  0003:01:00.0 Serial Attached SCSI controller: Adaptec Series 8 12G SAS/PCIe 3 
(rev 01)
  0004:00:00.0 PCI bridge: IBM Device 04c1
  0004:01:00.0 PCI bridge: ASPEED Technology, Inc. AST1150 PCI-to-PCI Bridge 
(rev 04)
  0004:02:00.0 VGA compatible controller: ASPEED Technology, Inc. ASPEED 
Graphics Family (rev 41)
  0005:00:00.0 PCI bridge: IBM Device 04c1
  0005:01:00.0 USB controller: Texas Instruments TUSB73x0 SuperSpeed USB 3.0 
xHCI Host Controller (rev 02)
  0030:00:00.0 PCI bridge: IBM Device 04c1
  0030:01:00.0 Infiniband controller: Mellanox Technologies Device 1019
  0030:01:00.1 Infiniband controller: Mellanox Technologies Device 1019
  0031:00:00.0 PCI bridge: IBM Device 04c1
  0031:01:00.0 Ethernet controller: Intel Corporation 82599ES 10-Gigabit 
SFI/SFP+ Network Connection (rev 01)
  0031:01:00.1 Ethernet controller: Intel Corporation 82599ES 10-Gigabit 
SFI/SFP+ Network Connection (rev 01)
  0032:00:00.0 PCI bridge: IBM Device 04c1
  0033:00:00.0 PCI bridge: IBM Device 04c1
  0033:01:00.0 Ethernet controller: Intel Corporation 82575EB Gigabit Network 
Connection (rev 02)
  0033:01:00.1 Ethernet controller: Intel Corporation 82575EB Gigabit Network 
Connection (rev 02)

  root@bos1u1p1:~# ifconfig -a
  enP2p1s0f0 Link encap:Ethernet  HWaddr ac:1f:6b:09:c0:9e  
inet addr:9.3.20.217  Bcast:9.3.21.255  Mask:255.255.254.0
inet6 addr: fe80::ae1f:6bff:fe09:c09e/64 Scope:Link
UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
RX packets:62603 errors:0 dropped:0 overruns:0 frame:0
TX packets:105 errors:0 drop

[Kernel-packages] [Bug 1689365] Re: ibmvscsis: Do not send aborted task response

[bugproxy]

--- Comment From b...@us.ibm.com 2017-08-30 16:30 EDT---
I added the keyword: verification-done-zesty

** Tags added: verification-done-zesty

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

Title:
  ibmvscsis: Do not send aborted task response

Status in The Ubuntu-power-systems project:
  Fix Committed
Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Zesty:
  Fix Released

Bug description:
  [Impact]
  ibmvscsis: Do not send aborted task response

  The driver is sending a response to the actual scsi op that was
  aborted by an abort task TM, while LIO is sending a response to
  the abort task TM.

  ibmvscsis_tgt does not send the response to the client until
  release_cmd time. The reason for this was because if we did it
  at queue_status time, then the client would be free to reuse the
  tag for that command, but we're still using the tag until the
  command is released at release_cmd time, so we chose to delay
  sending the response until then. That then caused this issue, because
  release_cmd is always called, even if queue_status is not.

  SCSI spec says that the initiator that sends the abort task
  TM NEVER gets a response to the aborted op and with the current
  code it will send a response. Thus this fix will remove that response
  if the CMD_T_ABORTED && !CMD_T_TAS.

  Another case with a small timing window is the case where if LIO sends a
  TMR_DOES_NOT_EXIST, and the release_cmd callback is called for the TMR Abort
  cmd before the release_cmd for the (attemped) aborted cmd, then we need to
  ensure that we send the response for the (attempted) abort cmd to the client
  before we send the response for the TMR Abort cmd.

  [Test Case]
  As per comment #11, this requires sending manual abort signals to trigger the 
bug.

  [Fix]
  ibmvscsis: Fix the incorrect req_lim_delta
  ibmvscsis: Clear left-over abort_cmd pointers
  ibmvscsis: Do not send aborted task response
  target: Fix unknown fabric callback queue-full errors

  [Regression Potential]
  Patches are confined to ibmvscsi driver and target driver.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1689365/+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 732677] Re: bcmwl 5.100.82.38+bdcom-0ubuntu2 not work on BCM4311

[Mustafa]

** Also affects: broadcom-sta
   Importance: Undecided
   Status: New

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

Title:
  bcmwl 5.100.82.38+bdcom-0ubuntu2 not work on BCM4311

Status in Broadcom 802.11 Linux STA driver:
  New
Status in bcmwl package in Ubuntu:
  Invalid
Status in Arch Linux:
  Invalid
Status in CentOS:
  Invalid

Bug description:
  After upgrade to Natty Alpha updated driver bcmwl-kernel-source
  5.100.82.38+bdcom-0ubuntu2 doesn`t work with wifi module. Notebook
  Dell inspiron 1501. b43 ot work too.

  I downgraded to bcmwl-kernel-source 5.60.48.36+bdcom-0ubuntu5 and
  still work fine.

  Please update driver.

  Additional:

  05:00.0 Network controller: Broadcom Corporation BCM4311 802.11b/g WLAN (rev 
01)
   Subsystem: Dell Wireless 1390 WLAN Mini-Card
   Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
   Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
   Kernel driver in use: wl
   Kernel modules: wl, ssb

To manage notifications about this bug go to:
https://bugs.launchpad.net/broadcom-sta/+bug/732677/+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 1611078] Re: Support snaps inside of lxd containers

[Jacek Nykis]

I am still unable to run snaps inside lxd containers. I've just tested
on an Ubuntu 16.04.3 LTS host:

$ uname -a
Linux hp 4.10.0-33-generic #37~16.04.1-Ubuntu SMP Fri Aug 11 14:07:24 UTC 2017 
x86_64 x86_64 x86_64 GNU/Linux
$ lxc version
2.0.10
$ lxc launch  ubuntu:16.04 test
Creating test
Starting test 
$ lxc exec test -- apt update

$ lxc exec test -- apt dist-upgrade -y

$ lxc exec test -- apt install squashfuse -y

$ lxc exec test -- snap install hello
error: cannot communicate with server: Post http://localhost/v2/snaps/hello: 
dial unix /run/snapd.socket: connect: connection refused
$ lxc exec test -- systemctl status snapd
● snapd.service - Snappy daemon
   Loaded: loaded (/lib/systemd/system/snapd.service; enabled; vendor preset: 
enabled)
   Active: inactive (dead) (Result: exit-code) since Wed 2017-08-30 22:39:39 
UTC; 35s ago
 Main PID: 2017 (code=exited, status=201/NICE)

Aug 30 22:39:39 test systemd[1]: snapd.service: Unit entered failed state.
Aug 30 22:39:39 test systemd[1]: snapd.service: Failed with result 'exit-code'.
Aug 30 22:39:39 test systemd[1]: snapd.service: Service hold-off time over, 
scheduling restart.
Aug 30 22:39:39 test systemd[1]: Stopped Snappy daemon.
Aug 30 22:39:39 test systemd[1]: snapd.service: Start request repeated too 
quickly.
Aug 30 22:39:39 test systemd[1]: Failed to start Snappy daemon.
$ lxc exec test -- snap version
snap2.26.10
snapd   unavailable
series  -
$

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

Title:
  Support snaps inside of lxd containers

Status in Snappy:
  Fix Released
Status in apparmor package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in lxd package in Ubuntu:
  Fix Released
Status in apparmor source package in Xenial:
  Fix Released
Status in linux source package in Xenial:
  Fix Released
Status in lxd source package in Xenial:
  Fix Released
Status in apparmor source package in Yakkety:
  Fix Released
Status in linux source package in Yakkety:
  Fix Released
Status in lxd source package in Yakkety:
  Fix Released

Bug description:
  I tried following the instructions on snapcraft.io and got a failure.
  See the output below.  I've also attached the relevant output from
  running "journalctl -xe".

  uname: Linux 3.19.0-65-generic x86_64
  release: Ubuntu 16.04
  package: snapd 2.11+0.16.04

  Notably, I'm running this in an LXD container (version: 2.0.0.rc9).

  -

  $ sudo snap install hello-world
  64.75 MB / 64.75 MB 
[==]
 100.00 % 2.85 MB/s 

  error: cannot perform the following tasks:
  - Mount snap "ubuntu-core" (122) ([start snap-ubuntu\x2dcore-122.mount] 
failed with exit status 1: Job for snap-ubuntu\x2dcore-122.mount failed. See 
"systemctl status "snap-ubuntu\\x2dcore-122.mount"" and "journalctl -xe" for 
details.
  )
  $ ls -la /snap
  total 4K
  drwxr-xr-x 3 root root 4096 Aug  8 17:49 ubuntu-core
  $ ls -la /snap/ubuntu-core/
  total 4K
  drwxr-xr-x 2 root root 4096 Aug  8 17:49 122
  $ ls -la /snap/ubuntu-core/122/
  total 0K
  $ systemctl status "snap-ubuntu\\x2dcore-122.mount"
  ● snap-ubuntu\x2dcore-122.mount - Mount unit for ubuntu-core
 Loaded: loaded (/etc/systemd/system/snap-ubuntu\x2dcore-122.mount; 
enabled; vendor preset: enabled)
 Active: failed (Result: exit-code) since Mon 2016-08-08 17:49:36 UTC; 6min 
ago
  Where: /snap/ubuntu-core/122
   What: /var/lib/snapd/snaps/ubuntu-core_122.snap
Process: 31781 ExecMount=/bin/mount 
/var/lib/snapd/snaps/ubuntu-core_122.snap /snap/ubuntu-core/122 -t squashfs 
(code=exited, status=32)

  Aug 08 17:49:35 my-host systemd[1]: Mounting Mount unit for ubuntu-core...
  Aug 08 17:49:35 my-host mount[31781]: mount: /snap/ubuntu-core/122: mount 
failed: Unknown error -1
  Aug 08 17:49:36 my-host systemd[1]: snap-ubuntu\x2dcore-122.mount: Mount 
process exited, code=exited status=32
  Aug 08 17:49:36 my-host systemd[1]: Failed to mount Mount unit for 
ubuntu-core.
  Aug 08 17:49:36 my-host systemd[1]: snap-ubuntu\x2dcore-122.mount: Unit 
entered failed state.

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

[Kernel-packages] [Bug 1611078] Re: Support snaps inside of lxd containers

[Haw Loeung]

Sounds like it might be LP:1709536

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

Title:
  Support snaps inside of lxd containers

Status in Snappy:
  Fix Released
Status in apparmor package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in lxd package in Ubuntu:
  Fix Released
Status in apparmor source package in Xenial:
  Fix Released
Status in linux source package in Xenial:
  Fix Released
Status in lxd source package in Xenial:
  Fix Released
Status in apparmor source package in Yakkety:
  Fix Released
Status in linux source package in Yakkety:
  Fix Released
Status in lxd source package in Yakkety:
  Fix Released

Bug description:
  I tried following the instructions on snapcraft.io and got a failure.
  See the output below.  I've also attached the relevant output from
  running "journalctl -xe".

  uname: Linux 3.19.0-65-generic x86_64
  release: Ubuntu 16.04
  package: snapd 2.11+0.16.04

  Notably, I'm running this in an LXD container (version: 2.0.0.rc9).

  -

  $ sudo snap install hello-world
  64.75 MB / 64.75 MB 
[==]
 100.00 % 2.85 MB/s 

  error: cannot perform the following tasks:
  - Mount snap "ubuntu-core" (122) ([start snap-ubuntu\x2dcore-122.mount] 
failed with exit status 1: Job for snap-ubuntu\x2dcore-122.mount failed. See 
"systemctl status "snap-ubuntu\\x2dcore-122.mount"" and "journalctl -xe" for 
details.
  )
  $ ls -la /snap
  total 4K
  drwxr-xr-x 3 root root 4096 Aug  8 17:49 ubuntu-core
  $ ls -la /snap/ubuntu-core/
  total 4K
  drwxr-xr-x 2 root root 4096 Aug  8 17:49 122
  $ ls -la /snap/ubuntu-core/122/
  total 0K
  $ systemctl status "snap-ubuntu\\x2dcore-122.mount"
  ● snap-ubuntu\x2dcore-122.mount - Mount unit for ubuntu-core
 Loaded: loaded (/etc/systemd/system/snap-ubuntu\x2dcore-122.mount; 
enabled; vendor preset: enabled)
 Active: failed (Result: exit-code) since Mon 2016-08-08 17:49:36 UTC; 6min 
ago
  Where: /snap/ubuntu-core/122
   What: /var/lib/snapd/snaps/ubuntu-core_122.snap
Process: 31781 ExecMount=/bin/mount 
/var/lib/snapd/snaps/ubuntu-core_122.snap /snap/ubuntu-core/122 -t squashfs 
(code=exited, status=32)

  Aug 08 17:49:35 my-host systemd[1]: Mounting Mount unit for ubuntu-core...
  Aug 08 17:49:35 my-host mount[31781]: mount: /snap/ubuntu-core/122: mount 
failed: Unknown error -1
  Aug 08 17:49:36 my-host systemd[1]: snap-ubuntu\x2dcore-122.mount: Mount 
process exited, code=exited status=32
  Aug 08 17:49:36 my-host systemd[1]: Failed to mount Mount unit for 
ubuntu-core.
  Aug 08 17:49:36 my-host systemd[1]: snap-ubuntu\x2dcore-122.mount: Unit 
entered failed state.

To manage notifications about this bug go to:
https://bugs.launchpad.net/snappy/+bug/1611078/+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 1714112] [NEW] EDAC sbridge: Failed to register device with error -22.

[Vinson Lee]

Public bug reported:

These kernel error messages appear with artful kernel 4.12.0-11-generic.

EDAC sbridge: Couldn't find mci handler
EDAC sbridge: Couldn't find mci handler
EDAC sbridge: Failed to register device with error -22.

EDAC_GHES is enable in 4.12.0-11-generic, but according to
https://lkml.org/lkml/2017/7/9/258 it should be disabled.

$ grep CONFIG_EDAC /boot/config-4.12.0-11-generic 
CONFIG_EDAC_ATOMIC_SCRUB=y
CONFIG_EDAC_SUPPORT=y
CONFIG_EDAC=y
# CONFIG_EDAC_LEGACY_SYSFS is not set
# CONFIG_EDAC_DEBUG is not set
CONFIG_EDAC_DECODE_MCE=m
CONFIG_EDAC_GHES=y
CONFIG_EDAC_AMD64=m
# CONFIG_EDAC_AMD64_ERROR_INJECTION is not set
CONFIG_EDAC_E752X=m
CONFIG_EDAC_I82975X=m
CONFIG_EDAC_I3000=m
CONFIG_EDAC_I3200=m
CONFIG_EDAC_IE31200=m
CONFIG_EDAC_X38=m
CONFIG_EDAC_I5400=m
CONFIG_EDAC_I7CORE=m
CONFIG_EDAC_I5000=m
CONFIG_EDAC_I5100=m
CONFIG_EDAC_I7300=m
CONFIG_EDAC_SBRIDGE=m
CONFIG_EDAC_SKX=m
CONFIG_EDAC_PND2=m

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


** Tags: artful

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

Title:
  EDAC sbridge: Failed to register device with error -22.

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  These kernel error messages appear with artful kernel
  4.12.0-11-generic.

  EDAC sbridge: Couldn't find mci handler
  EDAC sbridge: Couldn't find mci handler
  EDAC sbridge: Failed to register device with error -22.

  EDAC_GHES is enable in 4.12.0-11-generic, but according to
  https://lkml.org/lkml/2017/7/9/258 it should be disabled.

  $ grep CONFIG_EDAC /boot/config-4.12.0-11-generic 
  CONFIG_EDAC_ATOMIC_SCRUB=y
  CONFIG_EDAC_SUPPORT=y
  CONFIG_EDAC=y
  # CONFIG_EDAC_LEGACY_SYSFS is not set
  # CONFIG_EDAC_DEBUG is not set
  CONFIG_EDAC_DECODE_MCE=m
  CONFIG_EDAC_GHES=y
  CONFIG_EDAC_AMD64=m
  # CONFIG_EDAC_AMD64_ERROR_INJECTION is not set
  CONFIG_EDAC_E752X=m
  CONFIG_EDAC_I82975X=m
  CONFIG_EDAC_I3000=m
  CONFIG_EDAC_I3200=m
  CONFIG_EDAC_IE31200=m
  CONFIG_EDAC_X38=m
  CONFIG_EDAC_I5400=m
  CONFIG_EDAC_I7CORE=m
  CONFIG_EDAC_I5000=m
  CONFIG_EDAC_I5100=m
  CONFIG_EDAC_I7300=m
  CONFIG_EDAC_SBRIDGE=m
  CONFIG_EDAC_SKX=m
  CONFIG_EDAC_PND2=m

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

[Ubuntu Kernel Bot]

This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:

apport-collect 1714112

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable
to run this command, please add a comment stating that fact and change
the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the
Ubuntu Kernel Team.

** Changed in: linux (Ubuntu)
   Status: New => 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/1714112

Title:
  EDAC sbridge: Failed to register device with error -22.

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  These kernel error messages appear with artful kernel
  4.12.0-11-generic.

  EDAC sbridge: Couldn't find mci handler
  EDAC sbridge: Couldn't find mci handler
  EDAC sbridge: Failed to register device with error -22.

  EDAC_GHES is enable in 4.12.0-11-generic, but according to
  https://lkml.org/lkml/2017/7/9/258 it should be disabled.

  $ grep CONFIG_EDAC /boot/config-4.12.0-11-generic 
  CONFIG_EDAC_ATOMIC_SCRUB=y
  CONFIG_EDAC_SUPPORT=y
  CONFIG_EDAC=y
  # CONFIG_EDAC_LEGACY_SYSFS is not set
  # CONFIG_EDAC_DEBUG is not set
  CONFIG_EDAC_DECODE_MCE=m
  CONFIG_EDAC_GHES=y
  CONFIG_EDAC_AMD64=m
  # CONFIG_EDAC_AMD64_ERROR_INJECTION is not set
  CONFIG_EDAC_E752X=m
  CONFIG_EDAC_I82975X=m
  CONFIG_EDAC_I3000=m
  CONFIG_EDAC_I3200=m
  CONFIG_EDAC_IE31200=m
  CONFIG_EDAC_X38=m
  CONFIG_EDAC_I5400=m
  CONFIG_EDAC_I7CORE=m
  CONFIG_EDAC_I5000=m
  CONFIG_EDAC_I5100=m
  CONFIG_EDAC_I7300=m
  CONFIG_EDAC_SBRIDGE=m
  CONFIG_EDAC_SKX=m
  CONFIG_EDAC_PND2=m

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1714112/+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 1667750] Re: xhci_hcd: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 2 comp_code 13

[Corey Schuhen]

I do not see the same behaviour as Johann:

cschuhen@loriel:/tmp$ for i in 1 2 3 4; do curl -s 
http://de.releases.ubuntu.com/zesty/ubuntu-17.04-server-amd64.img -o $i.iso; 
md5sum $i.iso; done   
4672ce371fb3c1170a9e71bc4b2810b9  1.iso
4672ce371fb3c1170a9e71bc4b2810b9  2.iso
4672ce371fb3c1170a9e71bc4b2810b9  3.iso
4672ce371fb3c1170a9e71bc4b2810b9  4.iso
cschuhen@loriel:/tmp$ uname -a
Linux loriel 4.10.0-33-generic #37-Ubuntu SMP Fri Aug 11 10:55:28 UTC 2017 
x86_64 x86_64 x86_64 GNU/Linux


This is using the port on TB16.

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

Title:
  xhci_hcd: ERROR Transfer event TRB DMA ptr not part of current TD
  ep_index 2 comp_code 13

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Fix Released
Status in linux source package in Zesty:
  Fix Released
Status in linux source package in Artful:
  Fix Released
Status in linux package in Arch Linux:
  New
Status in linux package in Debian:
  New
Status in linux package in Fedora:
  Unknown

Bug description:
  [SRU Justification]

  [Impact] 
  Dell TB16 docking station has issue to use gigabit ethernet. The ethernet
  will disconnect unless it's changed to 100Mb/s.

  
  [Test Case]
  Download some big files from the web.
  User confirms the patch fixes the issue.

  [Regression Potential] 
  This patch only effects ASMEDIA's ASM1042A.
  The regression potential is low, also limited to the specific device.

  ---

  My system contains a Realtek Semiconductor Corp. RTL8153 Gigabit
  Ethernet Adapter which is on usb3 bus in my docking station (Dell
  TB16) which is attached to my laptop (Dell XPS9550) via Thunderbolt 3.

  I get usb related kernel error messages when I initiate a high speed
  transfer (by issuing wget http://cdimage.ubuntu.com/daily-live/current
  /zesty-desktop-amd64.iso) and the download fails.

  This does not happened when the Ethernet adapter is connected to a
  100Mb/s switch, but only when connected to 1000Mb/s. It also does not
  happened with slow traffic (e.g. web page browsing). This is not a new
  bug with kernel 4.10, but has been going on since at least 4.7 and
  maybe (probably?) since forever. I'm aware of several others with this
  configuration (RTL8153 on usb3 behind thunderbolt 3) that have the
  same issue. This bug is also not specific to Ubuntu; I also get it on
  Arch Linux. I've also tested and seen this bug with several different
  models of thunderbolt 3 docks.

  Here are the relevant kernel log messages:

  Feb 24 16:42:38 ubuntu kernel: xhci_hcd :0e:00.0: ERROR Transfer event 
TRB DMA ptr not part of current TD ep_index 2 comp_code 13
  Feb 24 16:42:38 ubuntu kernel: xhci_hcd :0e:00.0: Looking for event-dma 
0004777d9010 trb-start 000475a14fe0 trb-end 000475a14fe0 seg-start 
000475a14000 seg-end 000475a14ff0
  Feb 24 16:42:38 ubuntu kernel: xhci_hcd :0e:00.0: ERROR Transfer event 
TRB DMA ptr not part of current TD ep_index 2 comp_code 13
  Feb 24 16:42:38 ubuntu kernel: xhci_hcd :0e:00.0: Looking for event-dma 
0004777d9020 trb-start 000475a14fe0 trb-end 000475a14fe0 seg-start 
000475a14000 seg-end 000475a14ff0
  Feb 24 16:42:38 ubuntu kernel: xhci_hcd :0e:00.0: ERROR Transfer event 
TRB DMA ptr not part of current TD ep_index 2 comp_code 13
  Feb 24 16:42:38 ubuntu kernel: xhci_hcd :0e:00.0: Looking for event-dma 
0004777d9030 trb-start 000475a14fe0 trb-end 000475a14fe0 seg-start 
000475a14000 seg-end 000475a14ff0
  Feb 24 16:42:38 ubuntu kernel: xhci_hcd :0e:00.0: ERROR Transfer event 
TRB DMA ptr not part of current TD ep_index 2 comp_code 13
  Feb 24 16:42:38 ubuntu kernel: xhci_hcd :0e:00.0: Looking for event-dma 
0004777d9040 trb-start 000475a14fe0 trb-end 000475a14fe0 seg-start 
000475a14000 seg-end 000475a14ff0
  Feb 24 16:42:38 ubuntu kernel: xhci_hcd :0e:00.0: ERROR Transfer event 
TRB DMA ptr not part of current TD ep_index 2 comp_code 13
  Feb 24 16:42:38 ubuntu kernel: xhci_hcd :0e:00.0: Looking for event-dma 
0004777d9050 trb-start 000475a14fe0 trb-end 000475a14fe0 seg-start 
000475a14000 seg-end 000475a14ff0
  Feb 24 16:42:38 ubuntu kernel: xhci_hcd :0e:00.0: ERROR Transfer event 
TRB DMA ptr not part of current TD ep_index 2 comp_code 13
  Feb 24 16:42:38 ubuntu kernel: xhci_hcd :0e:00.0: Looking for event-dma 
0004777d9060 trb-start 000475a14fe0 trb-end 000475a14fe0 seg-start 
000475a14000 seg-end 000475a14ff0
  Feb 24 16:42:39 ubuntu kernel: xhci_hcd :0e:00.0: ERROR Transfer event 
TRB DMA ptr not part of current TD ep_index 2 comp_code 13
  Feb 24 16:42:39 ubuntu kernel: xhci_hcd :0e:00.0: Looking for event-dma 
0004777d9070 trb-start 000475a14fe0 trb-end 00047

[Kernel-packages] [Bug 1714112] Re: EDAC sbridge: Failed to register device with error -22.

[Vinson Lee]

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

Title:
  EDAC sbridge: Failed to register device with error -22.

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  These kernel error messages appear with artful kernel
  4.12.0-11-generic.

  EDAC sbridge: Couldn't find mci handler
  EDAC sbridge: Couldn't find mci handler
  EDAC sbridge: Failed to register device with error -22.

  EDAC_GHES is enable in 4.12.0-11-generic, but according to
  https://lkml.org/lkml/2017/7/9/258 it should be disabled.

  $ grep CONFIG_EDAC /boot/config-4.12.0-11-generic 
  CONFIG_EDAC_ATOMIC_SCRUB=y
  CONFIG_EDAC_SUPPORT=y
  CONFIG_EDAC=y
  # CONFIG_EDAC_LEGACY_SYSFS is not set
  # CONFIG_EDAC_DEBUG is not set
  CONFIG_EDAC_DECODE_MCE=m
  CONFIG_EDAC_GHES=y
  CONFIG_EDAC_AMD64=m
  # CONFIG_EDAC_AMD64_ERROR_INJECTION is not set
  CONFIG_EDAC_E752X=m
  CONFIG_EDAC_I82975X=m
  CONFIG_EDAC_I3000=m
  CONFIG_EDAC_I3200=m
  CONFIG_EDAC_IE31200=m
  CONFIG_EDAC_X38=m
  CONFIG_EDAC_I5400=m
  CONFIG_EDAC_I7CORE=m
  CONFIG_EDAC_I5000=m
  CONFIG_EDAC_I5100=m
  CONFIG_EDAC_I7300=m
  CONFIG_EDAC_SBRIDGE=m
  CONFIG_EDAC_SKX=m
  CONFIG_EDAC_PND2=m

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1714112/+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 1712427] Re: No audio output to Speakers when HDMI cable removed

[Brain]

Unfortunately I have to revise what I said. The bug does still exists in 4.13.
There is however the difference that with the 4.10 kernel it always exists, 
whereas in 4.13 it sometimes happens and sometimes correctly switches to analog 
audio. I haven't found yet any pattern when it happens.

** Tags removed: kernel-fixed-upstream
** Tags added: kernel-bug-exists-upstream

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

Title:
  No audio output to Speakers when HDMI cable removed

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The Sound Settings dialog in Unity allows to switch between various
  audio outputs.

  If HDMI is selected and the cable removed the dialog shows that Speakers are 
selected. But there is no audio. To actually output audio to speakers one needs 
to click some other output ("Simultaneous output ...") and then again on 
Speakers.
  The expected behaviour would be to actually play audio on the speakers 
without the need to switch forth and back.
  --- 
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  brain  2435 F pulseaudio
   /dev/snd/controlC1:  brain  2435 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=5165b586-2b44-4e4b-be49-177090e3b609
  InstallationDate: Installed on 2015-05-26 (819 days ago)
  InstallationMedia: Kubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  MachineType: ASUSTeK COMPUTER INC. N501JW
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-33-generic 
root=UUID=299cfed8-e49e-40d4-a8dd-fd66089e6d8a ro quiet splash 
iwlwifi.power_save=1 iwlwifi.power_level=5 acpi_osi= acpi_backlight=vendor 
acpi_enforce_resources=lax acpi=force nmi_watchdog=0 drm.vblankoffdelay=1 
i915.semaphores=1 i915.enable_rc6=7 i915.lvds_downclock=1 
rcutree.rcu_idle_gp_delay=1 pcie_aspm=force i915.enable_psr=1 i915.enable_fbc=1 
i915.disable_power_well=1 vt.handoff=7
  ProcVersionSignature: Ubuntu 4.10.0-33.37~16.04.1-generic 4.10.17
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-33-generic N/A
   linux-backports-modules-4.10.0-33-generic  N/A
   linux-firmware 1.157.12
  Tags:  xenial
  Uname: Linux 4.10.0-33-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm bumblebee cdrom dialout dip disk lp lpadmin opt plugdev 
sambashare sudo vboxusers wireshark
  _MarkForUpload: True
  dmi.bios.date: 08/03/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: N501JW.210
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: N501JW
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrN501JW.210:bd08/03/2015:svnASUSTeKCOMPUTERINC.:pnN501JW:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnN501JW:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: N501JW
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1712427/+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 1713787] Re: linux 4.4.0-93 triggers call traces

[Simon Déziel]

This really looks like https://patchwork.ozlabs.org/patch/799015/ which
fortunately made it into 4.4.0-94.117. I'll give that -proposed kernel a
test run.

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

Title:
  linux 4.4.0-93 triggers call traces

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  == Regression details ==

  Since the rolled out 4.4.0-93, we are getting many ~identical call
  traces that look like this:

  [ cut here ]
  WARNING: CPU: 0 PID:  at 
/build/linux-YyUNAI/linux-4.4.0/net/core/dev.c:2445 
skb_warn_bad_offload+0xd1/0x120()
  bond0: caps=(0x0fd97ba9, 0x) len=1487 data_len=0 
gso_size=1440 gso_type=6 ip_summed=0
  Modules linked in: binfmt_misc nf_log_ipv6 nf_conntrack_ipv6 nf_defrag_ipv6 
ip6table_filter ip6_tables nf_log_ipv4 nf_log_common xt_LOG xt_tcpudp 
nf_conntrack_ipv4 nf_defrag_ipv4 xt_owner xt_conntrack nf_conntrack 
iptable_filter ip_tables x_tables 8021q garp mrp bonding ipmi_devintf dcdbas 
intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp crct10dif_pclmul 
ipmi_ssif crc32_pclmul bridge ghash_clmulni_intel stp llc aesni_intel 
aes_x86_64 lrw gf128mul glue_helper ablk_helper cryptd vhost_net vhost macvtap 
macvlan sb_edac edac_core kvm_intel kvm ipmi_si 8250_fintek ipmi_msghandler 
lpc_ich irqbypass shpchp mei_me mei acpi_power_meter mac_hid drbd lru_cache 
autofs4 btrfs xor raid6_pq bnx2x mxm_wmi vxlan ip6_udp_tunnel tg3 udp_tunnel 
ahci mdio ptp libcrc32c libahci megaraid_sas pps_core fjes wmi
  CPU: 0 PID:  Comm: qemu-system-x86 Not tainted 4.4.0-93-generic 
#116-Ubuntu
  Hardware name: Dell Inc. PowerEdge R830/0VVT0H, BIOS 1.3.4 11/09/2016
   0286 f5a0655ded96de87 88bd7f2038c0 813f9f83
   88bd7f203908 81d6f780 88bd7f2038f8 810812f2
   88b6e118e000 8a3d17f52000 0006 0081
  Call Trace:
 [] dump_stack+0x63/0x90
   [] warn_slowpath_common+0x82/0xc0
   [] warn_slowpath_fmt+0x5c/0x80
   [] ? ___ratelimit+0xa2/0xe0
   [] skb_warn_bad_offload+0xd1/0x120
   [] __skb_gso_segment+0xfd/0x110
   [] validate_xmit_skb.isra.97.part.98+0x10d/0x2b0
   [] __dev_queue_xmit+0x582/0x590
   [] dev_queue_xmit+0x10/0x20
   [] vlan_dev_hard_start_xmit+0x98/0x120 [8021q]
   [] dev_hard_start_xmit+0x249/0x3d0
   [] __dev_queue_xmit+0x526/0x590
   [] dev_queue_xmit+0x10/0x20
   [] br_dev_queue_push_xmit+0x7a/0x140 [bridge]
   [] br_forward_finish+0x3d/0xb0 [bridge]
   [] ? br_handle_frame_finish+0x3a0/0x620 [bridge]
   [] __br_forward+0xa6/0x130 [bridge]
   [] br_forward+0x87/0x90 [bridge]
   [] br_handle_frame_finish+0x3a0/0x620 [bridge]
   [] ? __netif_receive_skb_core+0x364/0xa60
   [] ? dev_gro_receive+0x1c0/0x3c0
   [] br_handle_frame+0x174/0x2b0 [bridge]
   [] ? tg3_poll_work+0x4cb/0xf10 [tg3]
   [] ? __netif_receive_skb+0x18/0x60
   [] __netif_receive_skb_core+0x364/0xa60
   [] ? napi_gro_flush+0x5a/0x80
   [] __netif_receive_skb+0x18/0x60
   [] process_backlog+0xa8/0x150
   [] net_rx_action+0x21e/0x360
   [] __do_softirq+0x101/0x290
   [] do_softirq_own_stack+0x1c/0x30
 [] do_softirq.part.19+0x38/0x40
   [] do_softirq+0x1d/0x20
   [] netif_rx_ni+0x33/0x80
   [] tun_get_user+0x506/0x880
   [] tun_chr_write_iter+0x57/0x70
   [] do_iter_readv_writev+0x6c/0xa0
   [] do_readv_writev+0x18f/0x230
   [] vfs_writev+0x39/0x50
   [] SyS_writev+0x59/0xf0
   [] entry_SYSCALL_64_fastpath+0x16/0x71
  ---[ end trace 9fe5c984ff319e6a ]---

  For now this doesn't seem to have any user visible impact but we are
  not paying close attention to latencies/packet losses.

  Discovered in version:  linux-image-4.4.0-93-generic 4.4.0-93.116
  Last known good version: linux-image-4.4.0-92-generic 4.4.0-92.115

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-93-generic 4.4.0-93.116
  ProcVersionSignature: Ubuntu 4.4.0-93.116-generic 4.4.79
  Uname: Linux 4.4.0-93-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Aug 28 12:27 seq
   crw-rw 1 root audio 116, 33 Aug 28 12:27 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: [Errno 2] No such file or directory: 'fuser'
  Date: Tue Aug 29 13:46:12 2017
  HibernationDevice: RESUME=/dev/mapper/vghost-swap
  InstallationDate: Installed on 2017-04-01 (149 days ago)
  InstallationMedia: Ubuntu-Server 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.8)
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb:
   Bus 002 Device 002: ID 8087:8002 Intel Corp. 
   Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 001 Device 003: ID 413c:a001 Dell Computer Corp. Hub
   Bus 001 Device 002: ID 8087:800a Intel Corp. 
   

[Kernel-packages] [Bug 1667750] Re: xhci_hcd: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 2 comp_code 13

[André Düwel]

Thank @Mario for this clarification, I recently updated my BIOS, too.
Since then under Linux my mouse and keyboard (connected to the USB ports
of the TB16) stop working from time to time. In Windows Mouse and
Keyboard are just sometimes laggy but don't stop completely. I will try
to downgrade the BIOS today to an earlier version.

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

Title:
  xhci_hcd: ERROR Transfer event TRB DMA ptr not part of current TD
  ep_index 2 comp_code 13

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Fix Released
Status in linux source package in Zesty:
  Fix Released
Status in linux source package in Artful:
  Fix Released
Status in linux package in Arch Linux:
  New
Status in linux package in Debian:
  New
Status in linux package in Fedora:
  Unknown

Bug description:
  [SRU Justification]

  [Impact] 
  Dell TB16 docking station has issue to use gigabit ethernet. The ethernet
  will disconnect unless it's changed to 100Mb/s.

  
  [Test Case]
  Download some big files from the web.
  User confirms the patch fixes the issue.

  [Regression Potential] 
  This patch only effects ASMEDIA's ASM1042A.
  The regression potential is low, also limited to the specific device.

  ---

  My system contains a Realtek Semiconductor Corp. RTL8153 Gigabit
  Ethernet Adapter which is on usb3 bus in my docking station (Dell
  TB16) which is attached to my laptop (Dell XPS9550) via Thunderbolt 3.

  I get usb related kernel error messages when I initiate a high speed
  transfer (by issuing wget http://cdimage.ubuntu.com/daily-live/current
  /zesty-desktop-amd64.iso) and the download fails.

  This does not happened when the Ethernet adapter is connected to a
  100Mb/s switch, but only when connected to 1000Mb/s. It also does not
  happened with slow traffic (e.g. web page browsing). This is not a new
  bug with kernel 4.10, but has been going on since at least 4.7 and
  maybe (probably?) since forever. I'm aware of several others with this
  configuration (RTL8153 on usb3 behind thunderbolt 3) that have the
  same issue. This bug is also not specific to Ubuntu; I also get it on
  Arch Linux. I've also tested and seen this bug with several different
  models of thunderbolt 3 docks.

  Here are the relevant kernel log messages:

  Feb 24 16:42:38 ubuntu kernel: xhci_hcd :0e:00.0: ERROR Transfer event 
TRB DMA ptr not part of current TD ep_index 2 comp_code 13
  Feb 24 16:42:38 ubuntu kernel: xhci_hcd :0e:00.0: Looking for event-dma 
0004777d9010 trb-start 000475a14fe0 trb-end 000475a14fe0 seg-start 
000475a14000 seg-end 000475a14ff0
  Feb 24 16:42:38 ubuntu kernel: xhci_hcd :0e:00.0: ERROR Transfer event 
TRB DMA ptr not part of current TD ep_index 2 comp_code 13
  Feb 24 16:42:38 ubuntu kernel: xhci_hcd :0e:00.0: Looking for event-dma 
0004777d9020 trb-start 000475a14fe0 trb-end 000475a14fe0 seg-start 
000475a14000 seg-end 000475a14ff0
  Feb 24 16:42:38 ubuntu kernel: xhci_hcd :0e:00.0: ERROR Transfer event 
TRB DMA ptr not part of current TD ep_index 2 comp_code 13
  Feb 24 16:42:38 ubuntu kernel: xhci_hcd :0e:00.0: Looking for event-dma 
0004777d9030 trb-start 000475a14fe0 trb-end 000475a14fe0 seg-start 
000475a14000 seg-end 000475a14ff0
  Feb 24 16:42:38 ubuntu kernel: xhci_hcd :0e:00.0: ERROR Transfer event 
TRB DMA ptr not part of current TD ep_index 2 comp_code 13
  Feb 24 16:42:38 ubuntu kernel: xhci_hcd :0e:00.0: Looking for event-dma 
0004777d9040 trb-start 000475a14fe0 trb-end 000475a14fe0 seg-start 
000475a14000 seg-end 000475a14ff0
  Feb 24 16:42:38 ubuntu kernel: xhci_hcd :0e:00.0: ERROR Transfer event 
TRB DMA ptr not part of current TD ep_index 2 comp_code 13
  Feb 24 16:42:38 ubuntu kernel: xhci_hcd :0e:00.0: Looking for event-dma 
0004777d9050 trb-start 000475a14fe0 trb-end 000475a14fe0 seg-start 
000475a14000 seg-end 000475a14ff0
  Feb 24 16:42:38 ubuntu kernel: xhci_hcd :0e:00.0: ERROR Transfer event 
TRB DMA ptr not part of current TD ep_index 2 comp_code 13
  Feb 24 16:42:38 ubuntu kernel: xhci_hcd :0e:00.0: Looking for event-dma 
0004777d9060 trb-start 000475a14fe0 trb-end 000475a14fe0 seg-start 
000475a14000 seg-end 000475a14ff0
  Feb 24 16:42:39 ubuntu kernel: xhci_hcd :0e:00.0: ERROR Transfer event 
TRB DMA ptr not part of current TD ep_index 2 comp_code 13
  Feb 24 16:42:39 ubuntu kernel: xhci_hcd :0e:00.0: Looking for event-dma 
0004777d9070 trb-start 000475a14fe0 trb-end 000475a14fe0 seg-start 
000475a14000 seg-end 000475a14ff0
  Feb 24 16:42:39 ubuntu kernel: xhci_hcd :0e:00.0: ERROR Transfer event 
TRB DMA ptr not part of current TD ep_index 2 comp_code 13
  Feb 24 16:42:39 ubuntu kernel

[Kernel-packages] [Bug 989191] Re: Asus Zenbook UX31E powers off on plugin in/out AC adapter

[mcafeesupport]

very interesting post and I really enjoyed a lot and I found many
interesting posts on your website thanks for sharing if you have any
query related to McAfee support so contact us we are providing best
support service with the best solution https://mcafeesupports.org/mcafee-activation-errors-and-
solutions/"> McAfee  Customer Service

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

Title:
  Asus Zenbook UX31E powers off on plugin in/out AC adapter

Status in Linux:
  Unknown
Status in linux package in Ubuntu:
  In Progress

Bug description:
  When I have logged in to Unity and plug in or out AC adapter to Asus
  Zenbook UX31E, computer powers off. Sometimes this needs couple of
  tries (waiting or not waiting in between) when plugin in or out AC
  adapter.

  This problem doesn't occur when I have switched to console or when in LightDM 
login screen. Problem doesn't happen with MS Windows either.
  And yes, there's enough power in my battery too, I can boot up and use the 
computer without AC adapter.

  syslog prints these lines to stdout in console, when plugin AC adapter first 
out and then in:
    [  869.521396] asus_wmi: Unknown key 57 pressed
    [  874.704525] asus_wmi: Unknown key 58 pressed
    [  876.993295] [drm:drm_mode_getfb] *ERROR* invalid framebuffer id

  What you also need:

  1) lsb_release -rd
    Description:Ubuntu 12.04 LTS
    Release:12.04

  2) I could guess kernel, but it happens _only_ when I have logged in
  to Unity (or Unity 2D)...

  3) I expect that my computer doesn't power off.

  4) Computer powers off.

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