date:20161118

tests ran:   4, failed: 0;
  
http://kernel.ubuntu.com/testing/4.4.0-49.70-lowlatency/onza__4.4.0-49.70__2016-11-19_04-15-00/results-index.html

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

Title:
  linux: 4.4.0-49.70 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
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:
  In Progress
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 4.4.0-49.70 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
  derivative-trackers-created: 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/1640921/+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 1622376] Re: Mounting SDXC Cards unreliable

2016-11-18 Thread Launchpad Bug Tracker

[Expired for linux (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  Mounting SDXC Cards unreliable

Status in linux package in Ubuntu:
  Expired

Bug description:
  Ubuntu 16.04 Lenovo Y700 laptop

  Using Sandisk SDXC Cards (camera/pictures) works for one card (mounts)
  but not for the other (does not mount). Cars and built-in reader works
  without any problems in this other (obviously) popular OS.

  Conclusion: both cards are OK, the reader is OK.

  The mounting card:

  [94183.755973] mmc0: new ultra high speed DDR50 SDXC card at address 
  [94183.756646] mmcblk0: mmc0: SL64G 59.5 GiB
  [94183.770742] mmcblk0: p1
  udisksd[3993]: Mounted /dev/mmcblk0p1 at /media/xxx/6337-6134 on behalf of 
uid 1000
  .
  .
  .
  udisksd[3993]: Cleaning up mount point /media/xxx/6337-6134 (device 179:1 is 
not mounted)
  udisksd[3993]: Unmounted /dev/mmcblk0p1 on behalf of uid 1000
  [94251.132197] mmc0: card  removed

  The failing card (does not fail when running under an alternative OS):

  [94804.132020] sdhci: Timeout waiting for Buffer Read Ready interrupt during 
tuning procedure, falling back to fixed sampling clock
  [94804.132100] mmc0: tuning execution failed
  [94804.132111] mmc0: error -5 whilst initialising SD card

  Curious...

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-36-generic 4.4.0-36.55
  ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16
  Uname: Linux 4.4.0-36-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  hk 3842 F pulseaudio
  CurrentDesktop: Unity
  Date: Sun Sep 11 20:12:15 2016
  HibernationDevice: RESUME=UUID=87c83c29-86d9-4674-a81c-4012e557565f
  InstallationDate: Installed on 2016-06-21 (82 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  Lsusb:
   Bus 002 Device 002: ID 8086:0a66 Intel Corp. 
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 002: ID 046d:c526 Logitech, Inc. Nano Receiver
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 80NV
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-36-generic.efi.signed 
root=UUID=560e20f5-d2aa-48c1-ab12-55c2a34639f8 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-36-generic N/A
   linux-backports-modules-4.4.0-36-generic  N/A
   linux-firmware1.157.3
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/29/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: CDCN35WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: Allsparks 5A
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ideapad Y700-15ISK
  dmi.modalias: 
dmi:bvnLENOVO:bvrCDCN35WW:bd03/29/2016:svnLENOVO:pn80NV:pvrLenovoideapadY700-15ISK:rvnLENOVO:rnAllsparks5A:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoideapadY700-15ISK:
  dmi.product.name: 80NV
  dmi.product.version: Lenovo ideapad Y700-15ISK
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1622376/+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 1624339] Re: Elantech v4 trackpad no longer working after resuming for hibernate

2016-11-18 Thread Jean-Yves Avenard

Yes, it still occurs with 4.9-rc5

I have made a discovery however that will help:
The problem only occurs if the nvidia GPU is disabled in the BIOS and only the 
intel one is active.
If the nvidia adapter is enabled in BIOS, then restoring from hibernate works.

I'm not sure why this bug was marked as incomplete, I provided all
requested information.


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

Title:
  Elantech v4 trackpad no longer working after resuming for hibernate

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  This is a Gigabyte AERO 14 laptop (http://www.gigabyte.com.au/products
  /product-page.aspx?pid=5902#kf)

  When laptop goes into hibernate mode, the trackpad will no longer work. 
Rebooting will not make the trackpad work again.
  The only work around I've found so far is to reboot into windows and then 
reboot into ubuntu.

  It is similar to bug 1490130; however here it's with hibernating and can't be 
recovered with rebooting (additionally, the kernel patch provided there doesn't 
work)
  Suspend works just fine.

  
  *** before hibernate

  I: Bus=0011 Vendor=0001 Product=0001 Version=ab83
  N: Name="AT Translated Set 2 keyboard"
  P: Phys=isa0060/serio0/input0
  S: Sysfs=/devices/platform/i8042/serio0/input/input0
  U: Uniq=
  H: Handlers=sysrq kbd leds event0 
  B: PROP=0
  B: EV=120013
  B: KEY=40200 3803078f800d001 fedfffef fffe
  B: MSC=10
  B: LED=7

  I: Bus=0019 Vendor= Product=0005 Version=
  N: Name="Lid Switch"
  P: Phys=PNP0C0D/button/input0
  S: 
Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/device:18/PNP0C09:01/PNP0C0D:00/input/input2
  U: Uniq=
  H: Handlers=event1 
  B: PROP=0
  B: EV=21
  B: SW=1

  I: Bus=0019 Vendor= Product=0003 Version=
  N: Name="Sleep Button"
  P: Phys=PNP0C0E/button/input0
  S: 
Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/device:18/PNP0C09:01/PNP0C0E:00/input/input3
  U: Uniq=
  H: Handlers=kbd event2 
  B: PROP=0
  B: EV=3
  B: KEY=4000 0 0

  I: Bus=0019 Vendor= Product=0003 Version=
  N: Name="Sleep Button"
  P: Phys=PNP0C0E/button/input0
  S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0E:01/input/input4
  U: Uniq=
  H: Handlers=kbd event3 
  B: PROP=0
  B: EV=3
  B: KEY=4000 0 0

  I: Bus=0019 Vendor= Product=0001 Version=
  N: Name="Power Button"
  P: Phys=PNP0C0C/button/input0
  S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input5
  U: Uniq=
  H: Handlers=kbd event4 
  B: PROP=0
  B: EV=3
  B: KEY=10 0

  I: Bus=0019 Vendor= Product=0001 Version=
  N: Name="Power Button"
  P: Phys=LNXPWRBN/button/input0
  S: Sysfs=/devices/LNXSYSTM:00/LNXPWRBN:00/input/input6
  U: Uniq=
  H: Handlers=kbd event5 
  B: PROP=0
  B: EV=3
  B: KEY=10 0

  I: Bus=0019 Vendor= Product=0006 Version=
  N: Name="Video Bus"
  P: Phys=LNXVIDEO/video/input0
  S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/LNXVIDEO:00/input/input8
  U: Uniq=
  H: Handlers=kbd event6 
  B: PROP=0
  B: EV=3
  B: KEY=3e000b 0 0 0

  I: Bus=0011 Vendor=0002 Product=000e Version=
  N: Name="ETPS/2 Elantech Touchpad"
  P: Phys=isa0060/serio1/input0
  S: Sysfs=/devices/platform/i8042/serio1/input/input7
  U: Uniq=
  H: Handlers=mouse1 event8 
  B: PROP=5
  B: EV=b
  B: KEY=e420 1 0 0 0 0
  B: ABS=66180001103

  I: Bus=0003 Vendor=1044 Product=7a06 Version=0110
  N: Name="E-Signal Keyboard"
  P: Phys=usb-:00:14.0-5/input0
  S: 
Sysfs=/devices/pci:00/:00:14.0/usb1/1-5/1-5:1.0/0003:1044:7A06.0002/input/input10
  U: Uniq=
  H: Handlers=sysrq kbd leds event9 
  B: PROP=0
  B: EV=120013
  B: KEY=10007 ff9f207ac14057ff febeffdfffef fffe
  B: MSC=10
  B: LED=7

  I: Bus=0003 Vendor=1044 Product=7a06 Version=0110
  N: Name="E-Signal Keyboard"
  P: Phys=usb-:00:14.0-5/input1
  S: 
Sysfs=/devices/pci:00/:00:14.0/usb1/1-5/1-5:1.1/0003:1044:7A06.0003/input/input11
  U: Uniq=
  H: Handlers=kbd mouse2 event10 js0 
  B: PROP=0
  B: EV=10001f
  B: KEY=3f0003007f 0 0 48317aff32d bf56 1f0001 130f938b17c000 
677bfad9415fed 9ed6804400 1002
  B: REL=1c0
  B: ABS=10003
  B: MSC=10

  I: Bus= Vendor= Product= Version=
  N: Name="HDA Intel PCH Headphone"
  P: Phys=ALSA
  S: Sysfs=/devices/pci:00/:00:1f.3/sound/card0/input12
  U: Uniq=
  H: Handlers=event11 
  B: PROP=0
  B: EV=21
  B: SW=4

  I: Bus= Vendor= Product= Version=
  N: Name="HDA Intel PCH HDMI/DP,pcm=3"
  P: Phys=ALSA
  S: Sysfs=/devices/pci:00/:00:1f.3/sound/card0/input13
  U: Uniq=
  H: Handlers=event12 
  B: PROP=0
  B: EV=21
  B: SW=140

  I: Bus= Vendor= Product= Version=
  N: Name="HDA Intel PCH HDMI/DP,pcm=7"
  P: Phys=ALSA
  S:

[Kernel-packages] [Bug 1640921] onza (i386) - tests ran: 4, failed: 0

tests ran:   4, failed: 0;
  
http://kernel.ubuntu.com/testing/4.4.0-49.70-generic/onza__4.4.0-49.70__2016-11-19_02-38-00/results-index.html

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

Title:
  linux: 4.4.0-49.70 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
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:
  In Progress
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 4.4.0-49.70 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
  derivative-trackers-created: 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/1640921/+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 1642821] Re: Touchpad 3 button click no longer works after resume.

2016-11-18 Thread Darin

The Yoga Pro 2 touch pad was very sketchy (nearly useless) on the old
xorg driver.

With the exception of 2 issues, the touch pad works perfectly with libinput as 
long I install xserver-xorg-input-libinput driver. Last remaining issues:
- Middle mouse click lost after resume
- Touchpad always detects my palm (both movement and tap click)

With libinput still under heavy development, I have been waiting/hoping
these issues would eventually disappear.  But now that its maturing, I
filed this BR.

After testing kernel 4.9.0-040900rc5, middle click is still working
after 8 resumes.  So, I would tentatively say, the new kernel seems to
have fixed the middle click issue (more testing required to be certain).

Now to file a palm detection bug against libinput

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

Title:
  Touchpad 3 button click no longer works after resume.

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  After suspending the laptop, middle click) on Yoga 2 pro touch pad
  stops working.  Sometimes middle click emulation survives 3 or more
  suspends, but usually not more than 5.

  Only method to restore middle click is to reboot.

  All other touch pad functionality works fine.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: linux-image-4.8.0-27-generic 4.8.0-27.29
  ProcVersionSignature: Ubuntu 4.8.0-27.29-generic 4.8.1
  Uname: Linux 4.8.0-27-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  darin  1299 F pulseaudio
   /dev/snd/controlC0:  darin  1299 F pulseaudio
  CurrentDesktop: KDE
  Date: Thu Nov 17 22:43:20 2016
  HibernationDevice: RESUME=UUID=e7e99dfd-706a-4f9d-ab08-85b062127431
  InstallationDate: Installed on 2016-11-15 (3 days ago)
  InstallationMedia: Kubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.1)
  MachineType: LENOVO 20266
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-27-generic.efi.signed 
root=UUID=ebd9d973-be2f-4f3b-9686-c4141a1a7b67 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-27-generic N/A
   linux-backports-modules-4.8.0-27-generic  N/A
   linux-firmware1.161
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/17/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 76CN27WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Yoga2
  dmi.board.vendor: LENOVO
  dmi.board.version: 31900058STD
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo Yoga 2 Pro
  dmi.modalias: 
dmi:bvnLENOVO:bvr76CN27WW:bd09/17/2013:svnLENOVO:pn20266:pvrLenovoYoga2Pro:rvnLENOVO:rnYoga2:rvr31900058STD:cvnLENOVO:ct10:cvrLenovoYoga2Pro:
  dmi.product.name: 20266
  dmi.product.version: Lenovo Yoga 2 Pro
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1642821/+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 1640921] onza (amd64) - tests ran: 31, failed: 0

tests ran:  31, failed: 0;
  
http://kernel.ubuntu.com/testing/4.4.0-49.70-lowlatency/onza__4.4.0-49.70__2016-11-19_01-12-00/results-index.html

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

Title:
  linux: 4.4.0-49.70 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
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:
  In Progress
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 4.4.0-49.70 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
  derivative-trackers-created: 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/1640921/+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 1633839] Re: No symbol table. Press any key to continue

2016-11-18 Thread Yu Lou

I have a dual system of Ubuntu and Windows 7 and encountered the same
problem after in place upgrade from 16.04 to 16.10. I tried boot-repair
before but it didn't work. Just a moment ago I tried this command and it
worked:

sudo grub-install /dev/sda

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

Title:
  No symbol table. Press any key to continue

Status in grub2 package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 16.10. shows "error: no symbol table. Press any key to
  continue..." after Kernel boot and before login screen. After pressing
  a key or waiting a few seconds, the boot process continues and login
  screen appears.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: linux-image-4.8.0-22-generic 4.8.0-22.24
  ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0
  Uname: Linux 4.8.0-22-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:     7722 F pulseaudio
  CurrentDesktop: Unity
  Date: Sun Oct 16 13:25:22 2016
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=9d3bac9d-90f6-4fb6-ba39-e08ea2c3aa19
  InstallationDate: Installed on 2013-10-28 (1083 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  MachineType: LENOVO 23255B2
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-22-generic 
root=UUID=3b21f524-fe80-4ab0-8b84-c03e44abcd8b ro elevator=deadline
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-22-generic N/A
   linux-backports-modules-4.8.0-22-generic  N/A
   linux-firmware1.161
  SourcePackage: linux
  UpgradeStatus: Upgraded to yakkety on 2016-10-16 (0 days ago)
  dmi.bios.date: 03/03/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G2ETA6WW (2.66 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 23255B2
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: CS023589
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrG2ETA6WW(2.66):bd03/03/2016:svnLENOVO:pn23255B2:pvrThinkPadX230:rvnLENOVO:rn23255B2:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 23255B2
  dmi.product.version: ThinkPad X230
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1633839/+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 1640621] onibi (i386) - tests ran: 19, failed: 1

tests ran:  19, failed: 1;
  
http://kernel.ubuntu.com/testing/3.19.0-75.83~14.04.1-generic/onibi__3.19.0-75.83~14.04.1__2016-11-19_00-42-00/results-index.html

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

Title:
  linux-lts-vivid: 3.19.0-75.83~14.04.1 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
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 verification-testing series:
  Fix Released
Status in linux-lts-vivid package in Ubuntu:
  Invalid
Status in linux-lts-vivid source package in Trusty:
  Confirmed

Bug description:
  This bug is for tracking the 3.19.0-75.83~14.04.1 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
  derivative-trackers-created: true
  kernel-stable-master-bug: 1640613
  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/1640621/+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 1616107] Comment bridged from LTC Bugzilla

--- Comment From wil...@us.ibm.com 2016-11-18 20:02 EDT---
I traced the probolem to __vlan_vid_add(), this code snipit:

/* Try switchdev op first. In case it is not supported, fallback to
* 8021q add.
*/
err = switchdev_port_obj_add(dev, );
if (err == -EOPNOTSUPP)
return vlan_vid_add(dev, br->vlan_proto, vid);
return err;

switchdev_port_obj_add() returns EOPNOTSUP so it it calls vlan_vid_add()  that 
function is in 8021q module,  on my system that was not loaded.  If I set the 
interface to be added to the bridge UP then load 8021q before creating the 
bridge the problem will not happen.  Using the following steps to create the
bridge will prevent the problem..

rmmod bridge
rmmod 8021q
ifconfig enP2p1s0f3 up
modprobe 8021q
brctl addbr boom
brctl stp boom off
brctl addif boom enP2p1s0f3
brctl delif boom enP2p1s0f3

I made a few attempts to alter the interfaces script to create a
workaround.  Not much luck.  however we can prevent a panic by not
shutting down the interface at system shutdown time.  Using the no-auto-
down directive in /etc/network/interfaces worked for me.  My Bridge
definition is:

no-auto-down boom
iface boom inet static
address 192.168.10.1
netmask 255.255.0.0
bridge_ports enP2p1s0f3
bridge_stp off

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

Title:
  Kernel oops + system freeze on network-bridge shutdown

Status in bridge-utils package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in bridge-utils source package in Xenial:
  Confirmed
Status in linux source package in Xenial:
  Confirmed
Status in bridge-utils source package in Yakkety:
  Confirmed

Bug description:
  A Kernel oops leaves Ubuntu 16.04 unusable when a network bridge is
  brought down on a HPE 530SFP+ 10GBit NIC that uses bnx2x as a driver.
  This error does not appear in Ubuntu 14.04 however.

  The error is reproducible whenever issuing the commands "shutdown",
  "service networking stop" or "brctl delbr br0". Manually creating the
  bridge and subsequently bringing it down results in the same error.

  /var/log/kern.log:
  [...]
  Aug 23 15:09:46 base1 kernel: [  617.996677] device ens1f0 left promiscuous 
mode
  Aug 23 15:09:46 base1 kernel: [  617.996699] br0: port 1(ens1f0) entered 
disabled state
  Aug 23 15:09:46 base1 kernel: [  617.996730] BUG: unable to handle kernel 
NULL pointer dereference at 00d2
  Aug 23 15:09:46 base1 kernel: [  618.008306] IP: [] 
__vlan_flush+0x18/0x60 [bridge]
  Aug 23 15:09:46 base1 kernel: [  618.020549] PGD 10374c0067 PUD 1033927067 
PMD 0
  Aug 23 15:09:46 base1 kernel: [  618.032773] Oops: 0002 [#1] SMP
  Aug 23 15:09:46 base1 kernel: [  618.044434] Modules linked in: nls_iso8859_1 
ipmi_ssif intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel 
kvm irqbypass sb_edac edac_core joydev bridge stp llc input_leds hpilo lpc_ich 
ioatdma ipmi_si ipmi_msghandler shpchp mac_hid acpi_power_meter ib_iser rdma_cm 
iw_cm ib_cm ib_sa ib_mad ib_core ib_addr iscsi_tcp libiscsi_tcp libiscsi 
scsi_transport_iscsi autofs4 btrfs raid10 raid456 async_raid6_recov 
async_memcpy async_pq async_xor async_tx xor raid6_pq raid0 multipath linear 
raid1 hid_generic crct10dif_pclmul crc32_pclmul aesni_intel aes_x86_64 lrw 
gf128mul glue_helper ablk_helper cryptd igb usbhid hid bnx2x dca ahci 
i2c_algo_bit vxlan libahci ip6_udp_tunnel udp_tunnel ptp pps_core mdio 
libcrc32c wmi fjes
  Aug 23 15:09:46 base1 kernel: [  618.058563] CPU: 3 PID: 4049 Comm: brctl Not 
tainted 4.4.0-34-generic #53-Ubuntu
  Aug 23 15:09:46 base1 kernel: [  618.058564] Hardware name: HP ProLiant DL120 
Gen9/ProLiant DL120 Gen9, BIOS P86 05/05/2016
  Aug 23 15:09:46 base1 kernel: [  618.058574] task: 881030676040 ti: 
8810341e4000 task.ti: 8810341e4000
  Aug 23 15:09:46 base1 kernel: [  618.058576] RIP: 0010:[]  
[] __vlan_flush+0x18/0x60 [bridge]
  Aug 23 15:09:46 base1 kernel: [  618.058754] RSP: 0018:8810341e7d68  
EFLAGS: 00010206
  Aug 23 15:09:46 base1 kernel: [  618.058769] RAX:  RBX: 
 RCX: 
  Aug 23 15:09:46 base1 kernel: [  618.058774] RDX: 881038470848 RSI: 
 RDI: 
  Aug 23 15:09:46 base1 kernel: [  618.058775] RBP: 8810341e7d78 R08: 
 R09: 8170d949
  Aug 23 15:09:46 base1 kernel: [  618.058776] R10: ead61340 R11: 
8810329d2c00 R12: 00c0
  Aug 23 15:09:46 base1 kernel: [  618.058777] R13: 881030044000 R14: 
881038470840 R15: 
  Aug 23 15:09:46 base1 kernel: [  618.058782] FS:  7f9aebc94700() 
GS:88107fcc() knlGS:
  Aug 23 15:09:46 base1 kernel: [  618.058789] CS:  0010 DS:  ES:  CR0: 
80050033
  Aug 23 15:09:46 base1 kernel: [  618.058790] CR2: 00d2 CR3: 
00102fe83000 CR4: 001406e0
  Aug 23

[Kernel-packages] [Bug 1640921] onza (amd64) - tests ran: 31, failed: 0

tests ran:  31, failed: 0;
  
http://kernel.ubuntu.com/testing/4.4.0-49.70-generic/onza__4.4.0-49.70__2016-11-18_23-42-00/results-index.html

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

Title:
  linux: 4.4.0-49.70 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
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:
  In Progress
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 4.4.0-49.70 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
  derivative-trackers-created: 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/1640921/+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 1640621] onibi (amd64) - tests ran: 19, failed: 1

tests ran:  19, failed: 1;
  
http://kernel.ubuntu.com/testing/3.19.0-75.83~14.04.1-generic/onibi__3.19.0-75.83~14.04.1__2016-11-18_23-28-00/results-index.html

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

Title:
  linux-lts-vivid: 3.19.0-75.83~14.04.1 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
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 verification-testing series:
  Fix Released
Status in linux-lts-vivid package in Ubuntu:
  Invalid
Status in linux-lts-vivid source package in Trusty:
  Confirmed

Bug description:
  This bug is for tracking the 3.19.0-75.83~14.04.1 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
  derivative-trackers-created: true
  kernel-stable-master-bug: 1640613
  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/1640621/+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 1630063] Re: specific USB devices disconnect and don't reconnect

2016-11-18 Thread Scott Cowles Jacobs

"And it looks like those updates are in Ubuntu-4.8.0-28:"
I think not.


I do not find mention of this bug in the changelog for 4.8.0-28-generic (I 
searched for IO_WATCHDOG_DELAY, and USB and ohci - nothing for the latest 
version)
and an attempted print failed exactly the same way, with a dead-in-the-water 
USB mouse, and with most of the USB devices no longer listed for lsusb.

My usb reset script (not mine - I found it online somewhere, and
modified it a bit to fit my situation) brought things back again and the
syslog entries look just like before... :

Nov 18 18:12:26 scott-ASUS-M2N68-AM-PLUS kernel: [ 7049.029702] ohci-pci 
:00:02.0: HcDoneHead not written back; disabled
Nov 18 18:12:26 scott-ASUS-M2N68-AM-PLUS kernel: [ 7049.029709] ohci-pci 
:00:02.0: HC died; cleaning up
Nov 18 18:12:26 scott-ASUS-M2N68-AM-PLUS kernel: [ 7049.029770] usb 2-1: USB 
disconnect, device number 2
Nov 18 18:12:26 scott-ASUS-M2N68-AM-PLUS kernel: [ 7049.029772] usb 2-1.1: USB 
disconnect, device number 5
Nov 18 18:12:26 scott-ASUS-M2N68-AM-PLUS kernel: [ 7049.072512] usb 2-1.2: USB 
disconnect, device number 6
Nov 18 18:12:26 scott-ASUS-M2N68-AM-PLUS acpid: input device has been 
disconnected, fd 10
Nov 18 18:12:26 scott-ASUS-M2N68-AM-PLUS kernel: [ 7049.174018] usb 2-1.3: USB 
disconnect, device number 7
Nov 18 18:12:26 scott-ASUS-M2N68-AM-PLUS kernel: [ 7049.216254] usb 2-1.4: USB 
disconnect, device number 8
Nov 18 18:12:26 scott-ASUS-M2N68-AM-PLUS kernel: [ 7049.217445] usb 2-2: USB 
disconnect, device number 3
Nov 18 18:12:26 scott-ASUS-M2N68-AM-PLUS kernel: [ 7049.259107] usb 2-3: USB 
disconnect, device number 4
Nov 18 18:17:01 scott-ASUS-M2N68-AM-PLUS CRON[21826]: (root) CMD (   cd / && 
run-parts --report /etc/cron.hourly)
Nov 18 18:17:34 scott-ASUS-M2N68-AM-PLUS kernel: [ 7357.692303] ehci-pci 
:00:02.1: remove, state 1
Nov 18 18:17:34 scott-ASUS-M2N68-AM-PLUS kernel: [ 7357.692312] usb usb1: USB 
disconnect, device number 1
Nov 18 18:17:34 scott-ASUS-M2N68-AM-PLUS kernel: [ 7357.692313] usb 1-4: USB 
disconnect, device number 5
Nov 18 18:17:34 scott-ASUS-M2N68-AM-PLUS kernel: [ 7357.731566] usb 1-6: USB 
disconnect, device number 6

---
scott@scott-ASUS-M2N68-AM-PLUS:~$ uname -a
Linux scott-ASUS-M2N68-AM-PLUS 4.8.0-28-generic #30-Ubuntu SMP Fri Nov 11 
14:03:52 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux

scott@scott-ASUS-M2N68-AM-PLUS:~$ apt-cache policy linux-image*
linux-image-extra-4.8.0-28-generic:
  Installed: 4.8.0-28.30
linux-image-generic:
  Installed: 4.8.0.28.37
linux-image-4.8.0-28-generic:
  Installed: 4.8.0-28.30

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

Title:
  specific USB devices disconnect and don't reconnect

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

Bug description:
  2 USB ports randomly disconnect and don't reconnect (it's always the
  same two), and in dmesg all I get is

  "
  [ 1276.916458] ohci-pci :00:12.0: HcDoneHead not written back; disabled
  [ 1276.916467] ohci-pci :00:12.0: HC died; cleaning up
  [ 1276.916553] usb 3-1: USB disconnect, device number 2
  [ 1277.017302] usb 3-2: USB disconnect, device number 3
  "
  This only started happening when Yakkety went to the 4.8 branch, with 4.7 
branch this doesn't occur, hence the bug report since it's unlikely that a 
hardware failure will only stick to one OS and one branch of the kernel for 
that OS. (these USB ports don't randomly die on Windows or BSD, I've tested 
that in the past couple of days)

  
  kernel version: 4.8.0.17.27
  Ubuntu version
  Description:  Ubuntu Yakkety Yak (development branch)
  Release:  16.10
  --- 
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  c_smith2213 F pulseaudio
   /dev/snd/controlC0:  c_smith2213 F pulseaudio
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 16.10
  HibernationDevice: RESUME=UUID=1a29baaa-55ea-4817-ba45-8c618f65ec4b
  InstallationDate: Installed on 2016-10-03 (0 days ago)
  InstallationMedia: Ubuntu-MATE 16.10 "Yakkety Yak" - Alpha amd64 (20161002)
  MachineType: Gigabyte Technology Co., Ltd. GA-78LMT-S2
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.8.0-17-generic 
root=/dev/mapper/Linux-root ro nomodeset quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.8.0-17.19-generic 4.8.0-rc7
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-17-generic N/A
   linux-backports-modules-4.8.0-17-generic  N/A
   linux-firmware1.161
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  Tags:  yakkety
  Uname: Linux

[Kernel-packages] [Bug 1643087] Re: Yakkety failures on Xeon Phi (Dell Poweredge C6320p)

Got the following when I tried to run apport-collect:
ubuntu@brief-badger:~$ apport-collect 1643087
The authorization page:

(https://launchpad.net/+authorize-token?oauth_token=0h42c3flxcPFlcTk6RqB_permission=DESKTOP_INTEGRATION)
should be opening in your browser. Use your browser to authorize
this program to access Launchpad on your behalf.
Waiting to hear from Launchpad about your decision...
ERROR: connecting to Launchpad failed: local variable 'browser_obj' referenced
before assignment
You can reset the credentials by removing the file
"/home/ubuntu/.cache/apport/launchpad.credentials"
ubuntu@brief-badger:~$

This is a server (maas node) so no browser was available. Opened the url in
my laptop and authorized, nothing exciting happened.
Marking confirmed.

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

Title:
Yakkety failures on Xeon Phi (Dell Poweredge C6320p)

Status in linux package in Ubuntu:
Confirmed

Bug description:
Dell Poweredge C6320p machine with Intel Xeon Phi processor, running
certification tests.
I see 2 segfaults in the logs, there are more errors in the cert tests which
I will post later.

Linux brief-badger 4.8.0-27-generic #29-Ubuntu SMP Thu Oct 20 21:03:13
UTC 2016 x86_64 x86_64 x86_64 GNU/Linux

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1643087/+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 1643087] Re: Yakkety failures on Xeon Phi (Dell Poweredge C6320p)

** Attachment added: "lspci-vnvn.log"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1643087/+attachment/4779652/+files/lspci-vnvn.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/1643087

Title:
  Yakkety failures on Xeon Phi (Dell Poweredge C6320p)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Dell Poweredge C6320p machine with Intel Xeon Phi processor, running 
certification tests.
  I see 2 segfaults in the logs, there are more errors in the cert tests which 
I will post later.  

  Linux brief-badger 4.8.0-27-generic #29-Ubuntu SMP Thu Oct 20 21:03:13
  UTC 2016 x86_64 x86_64 x86_64 GNU/Linux

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

This bug is missing log files that will aid in diagnosing the problem.
>From a terminal window please run:

apport-collect 1643087

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

Title:
  Yakkety failures on Xeon Phi (Dell Poweredge C6320p)

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Dell Poweredge C6320p machine with Intel Xeon Phi processor, running 
certification tests.
  I see 2 segfaults in the logs, there are more errors in the cert tests which 
I will post later.  

  Linux brief-badger 4.8.0-27-generic #29-Ubuntu SMP Thu Oct 20 21:03:13
  UTC 2016 x86_64 x86_64 x86_64 GNU/Linux

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1643087/+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 1643087] Re: Yakkety failures on Xeon Phi (Dell Poweredge C6320p)

Tar file with all the logs:
C6320p_info:
total 892
drwxrwxr-x   2 mwenning mwenning   4096 Nov 18 17:09 ./
drwxr-xr-x 102 mwenning mwenning  12288 Nov 18 17:24 ../
-rw-r--r--   1 mwenning mwenning   5321 Nov 18 17:09 alternatives.log
-rw-r-   1 mwenning mwenning490 Nov 18 17:09 apport.log
-rw-r-   1 mwenning mwenning   3187 Nov 18 17:09 auth.log
-rw-r--r--   1 mwenning mwenning 157698 Nov 18 17:09 cloud-init.log
-rw-r--r--   1 mwenning mwenning   4622 Nov 18 17:09 cloud-init-output.log
-rw-rw-r--   1 mwenning mwenning 266308 Nov 18 17:09 cpuinfo.txt
-rw-rw-r--   1 mwenning mwenning  82262 Nov 18 17:09 dmesg.txt
-rw-r--r--   1 mwenning mwenning 217921 Nov 18 17:09 dpkg.log
-rw-r--r--   1 mwenning mwenning510 Nov 18 17:09 fontconfig.log
-rw-r-   1 mwenning mwenning 124475 Nov 18 17:09 kern.log
-rw-rw-r--   1 mwenning mwenning111 Nov 18 17:09 uname.txt


** Attachment added: "C6320p_info.tar.gz"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1643087/+attachment/4779651/+files/C6320p_info.tar.gz

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

Title:
  Yakkety failures on Xeon Phi (Dell Poweredge C6320p)

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Dell Poweredge C6320p machine with Intel Xeon Phi processor, running 
certification tests.
  I see 2 segfaults in the logs, there are more errors in the cert tests which 
I will post later.  

  Linux brief-badger 4.8.0-27-generic #29-Ubuntu SMP Thu Oct 20 21:03:13
  UTC 2016 x86_64 x86_64 x86_64 GNU/Linux

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1643087/+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 1640613] onza (i386) - tests ran: 3, failed: 0

tests ran:   3, failed: 0;
  
http://kernel.ubuntu.com/testing/3.19.0-75.83-generic/onza__3.19.0-75.83__2016-11-18_22-21-00/results-index.html

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

Title:
  linux: 3.19.0-75.83 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
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:
  In Progress
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:
  Fix Released
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Vivid:
  Confirmed

Bug description:
  This bug is for tracking the 3.19.0-75.83 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
  derivative-trackers-created: 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/1640613/+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 1643087] [NEW] Yakkety failures on Xeon Phi (Dell Poweredge C6320p)

Public bug reported:

Dell Poweredge C6320p machine with Intel Xeon Phi processor, running 
certification tests.
I see 2 segfaults in the logs, there are more errors in the cert tests which I 
will post later.  

Linux brief-badger 4.8.0-27-generic #29-Ubuntu SMP Thu Oct 20 21:03:13
UTC 2016 x86_64 x86_64 x86_64 GNU/Linux

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

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

Title:
  Yakkety failures on Xeon Phi (Dell Poweredge C6320p)

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Dell Poweredge C6320p machine with Intel Xeon Phi processor, running 
certification tests.
  I see 2 segfaults in the logs, there are more errors in the cert tests which 
I will post later.  

  Linux brief-badger 4.8.0-27-generic #29-Ubuntu SMP Thu Oct 20 21:03:13
  UTC 2016 x86_64 x86_64 x86_64 GNU/Linux

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1643087/+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 1640621] onibi (i386) - tests ran: 5, failed: 0

tests ran:   5, failed: 0;
  
http://kernel.ubuntu.com/testing/3.19.0-75.83~14.04.1-generic/onibi__3.19.0-75.83~14.04.1__2016-11-18_23-04-00/results-index.html

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

Title:
  linux-lts-vivid: 3.19.0-75.83~14.04.1 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
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 verification-testing series:
  Fix Released
Status in linux-lts-vivid package in Ubuntu:
  Invalid
Status in linux-lts-vivid source package in Trusty:
  Confirmed

Bug description:
  This bug is for tracking the 3.19.0-75.83~14.04.1 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
  derivative-trackers-created: true
  kernel-stable-master-bug: 1640613
  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/1640621/+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 1642739] Re: Kernel panic on shutdown

2016-11-18 Thread Gustav Näslund

I have now tested both v4.9-rc5 and the bisect kernel (lp1642739) and
both triggered the panic on shutdown.

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

Title:
  Kernel panic on shutdown

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

Bug description:
  Since I have updated to Ubuntu 16.10 (from 16.04) I have this problem
  where the shutdown takes a long time (~30s) and ends with a (at least
  I think it is) kernel panic with blinking harddrive- and battery
  status LEDs. Nothing is visible on the screen.

  This didnt happen on Ubuntu 16.04 so I tried installing a 4.4 kernel
  and the problem disappeared.

  I have then tested with various kernels from http://kernel.ubuntu.com
  /~kernel-ppa/mainline/ and I have found that the last good kernel is
  4.7.10 and the first bad kernel is 4.8-rc1.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: linux-image-4.8.0-27-generic 4.8.0-27.29
  ProcVersionSignature: Ubuntu 4.8.0-27.29-generic 4.8.1
  Uname: Linux 4.8.0-27-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gustav 1998 F pulseaudio
   /dev/snd/controlC1:  gustav 1998 F pulseaudio
  CurrentDesktop: MATE
  Date: Thu Nov 17 22:01:52 2016
  HibernationDevice: RESUME=UUID=d7a5213f-0285-4708-9e97-2486aec53935
  InstallationDate: Installed on 2016-09-15 (63 days ago)
  InstallationMedia: Ubuntu-MATE 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  Lsusb:
   Bus 001 Device 004: ID 1bcf:28ae Sunplus Innovation Technology Inc. Laptop 
Integrated Webcam HD
   Bus 001 Device 003: ID 8087:0a2a Intel Corp.
   Bus 001 Device 002: ID 8087:8001 Intel Corp.
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Latitude E7450
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-27-generic 
root=UUID=15f681e4-0a4a-4613-8810-ba7535bfa0a0 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-27-generic N/A
   linux-backports-modules-4.8.0-27-generic  N/A
   linux-firmware1.161
  SourcePackage: linux
  UpgradeStatus: Upgraded to yakkety on 2016-10-26 (22 days ago)
  dmi.bios.date: 05/17/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A13
  dmi.board.name: 06HN6G
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA13:bd05/17/2016:svnDellInc.:pnLatitudeE7450:pvr:rvnDellInc.:rn06HN6G:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E7450
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1642739/+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 1640621] onibi (amd64) - tests ran: 5, failed: 0

tests ran:   5, failed: 0;
  
http://kernel.ubuntu.com/testing/3.19.0-75.83~14.04.1-generic/onibi__3.19.0-75.83~14.04.1__2016-11-18_22-39-00/results-index.html

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

Title:
  linux-lts-vivid: 3.19.0-75.83~14.04.1 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
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 verification-testing series:
  Fix Released
Status in linux-lts-vivid package in Ubuntu:
  Invalid
Status in linux-lts-vivid source package in Trusty:
  Confirmed

Bug description:
  This bug is for tracking the 3.19.0-75.83~14.04.1 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
  derivative-trackers-created: true
  kernel-stable-master-bug: 1640613
  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/1640621/+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 1640621] onibi (i386) - tests ran: 3, failed: 0

tests ran:   3, failed: 0;
  
http://kernel.ubuntu.com/testing/3.19.0-75.83~14.04.1-generic/onibi__3.19.0-75.83~14.04.1__2016-11-18_21-26-00/results-index.html

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

Title:
  linux-lts-vivid: 3.19.0-75.83~14.04.1 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
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 verification-testing series:
  Fix Released
Status in linux-lts-vivid package in Ubuntu:
  Invalid
Status in linux-lts-vivid source package in Trusty:
  Confirmed

Bug description:
  This bug is for tracking the 3.19.0-75.83~14.04.1 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
  derivative-trackers-created: true
  kernel-stable-master-bug: 1640613
  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/1640621/+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 1640613] onza (amd64) - tests ran: 30, failed: 0

tests ran:  30, failed: 0;
  
http://kernel.ubuntu.com/testing/3.19.0-75.83-generic/onza__3.19.0-75.83__2016-11-18_20-54-00/results-index.html

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

Title:
  linux: 3.19.0-75.83 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
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:
  In Progress
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:
  Fix Released
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Vivid:
  Confirmed

Bug description:
  This bug is for tracking the 3.19.0-75.83 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
  derivative-trackers-created: 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/1640613/+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 1640621] onibi (amd64) - tests ran: 30, failed: 0

tests ran:  30, failed: 0;
  
http://kernel.ubuntu.com/testing/3.19.0-75.83~14.04.1-generic/onibi__3.19.0-75.83~14.04.1__2016-11-18_20-11-00/results-index.html

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

Title:
  linux-lts-vivid: 3.19.0-75.83~14.04.1 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
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 verification-testing series:
  Fix Released
Status in linux-lts-vivid package in Ubuntu:
  Invalid
Status in linux-lts-vivid source package in Trusty:
  Confirmed

Bug description:
  This bug is for tracking the 3.19.0-75.83~14.04.1 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
  derivative-trackers-created: true
  kernel-stable-master-bug: 1640613
  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/1640621/+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 1642739] Re: Kernel panic on shutdown

I'll started a bisect between v4.7 and v4.8-rc1.  It can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1642739/

Can you test this kernel after testing the v4.9-rc5 mainline 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/1642739

Title:
  Kernel panic on shutdown

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

Bug description:
  Since I have updated to Ubuntu 16.10 (from 16.04) I have this problem
  where the shutdown takes a long time (~30s) and ends with a (at least
  I think it is) kernel panic with blinking harddrive- and battery
  status LEDs. Nothing is visible on the screen.

  This didnt happen on Ubuntu 16.04 so I tried installing a 4.4 kernel
  and the problem disappeared.

  I have then tested with various kernels from http://kernel.ubuntu.com
  /~kernel-ppa/mainline/ and I have found that the last good kernel is
  4.7.10 and the first bad kernel is 4.8-rc1.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: linux-image-4.8.0-27-generic 4.8.0-27.29
  ProcVersionSignature: Ubuntu 4.8.0-27.29-generic 4.8.1
  Uname: Linux 4.8.0-27-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gustav 1998 F pulseaudio
   /dev/snd/controlC1:  gustav 1998 F pulseaudio
  CurrentDesktop: MATE
  Date: Thu Nov 17 22:01:52 2016
  HibernationDevice: RESUME=UUID=d7a5213f-0285-4708-9e97-2486aec53935
  InstallationDate: Installed on 2016-09-15 (63 days ago)
  InstallationMedia: Ubuntu-MATE 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  Lsusb:
   Bus 001 Device 004: ID 1bcf:28ae Sunplus Innovation Technology Inc. Laptop 
Integrated Webcam HD
   Bus 001 Device 003: ID 8087:0a2a Intel Corp.
   Bus 001 Device 002: ID 8087:8001 Intel Corp.
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Latitude E7450
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-27-generic 
root=UUID=15f681e4-0a4a-4613-8810-ba7535bfa0a0 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-27-generic N/A
   linux-backports-modules-4.8.0-27-generic  N/A
   linux-firmware1.161
  SourcePackage: linux
  UpgradeStatus: Upgraded to yakkety on 2016-10-26 (22 days ago)
  dmi.bios.date: 05/17/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A13
  dmi.board.name: 06HN6G
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA13:bd05/17/2016:svnDellInc.:pnLatitudeE7450:pvr:rvnDellInc.:rn06HN6G:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E7450
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1642739/+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 1640621] onza (amd64) - tests ran: 30, failed: 0

tests ran:  30, failed: 0;
  
http://kernel.ubuntu.com/testing/3.19.0-75.83~14.04.1-generic/onza__3.19.0-75.83~14.04.1__2016-11-18_19-39-00/results-index.html

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

Title:
  linux-lts-vivid: 3.19.0-75.83~14.04.1 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
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 verification-testing series:
  Fix Released
Status in linux-lts-vivid package in Ubuntu:
  Invalid
Status in linux-lts-vivid source package in Trusty:
  Confirmed

Bug description:
  This bug is for tracking the 3.19.0-75.83~14.04.1 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
  derivative-trackers-created: true
  kernel-stable-master-bug: 1640613
  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/1640621/+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 1400319] Re: [Hyper-V] Kernel panic not functional on 32bit Ubuntu 14.10, 15.04, and 15.10

2016-11-18 Thread Chris Valean

Hi Joe,

We did look at http://kernel.ubuntu.com/~jsalisbury/lp1400319/ however that 
folder has the 32bit kernel and binaries.
As this bug is in regards to the 32bit architecture, we would need the i386 
kernel actually.
Thank you!

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

Title:
  [Hyper-V] Kernel panic not functional on 32bit Ubuntu 14.10, 15.04,
  and 15.10

Status in kexec-tools package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  In Progress

Bug description:
  While testing the final build of 14.10 32bit we found that kernel
  panic cannot be activated for an installation on a Hyper-V VM.

  Repro rate: 100%
  Repro details:
  Hyper-V: Server 2012 R2
  VM: Ubuntu 14.10 32bit

  Kdump is enabled in the config file at /etc/default/kdump-tools

  Different crashkernel values used in grub.cfg – 128M-:64M | 256M-:128m
  | 384M-:256M

  VM settings: 2 cores, various RAM sizes attempted: 1, 2 or 4 GB – this
  in combination with the values for crashkernel.

  Trying to start the kdump service:
  root@ubuntu1410i386:~# /etc/init.d/kdump-tools start
  Starting kdump-tools: Could not find a free area of memory of 0x9f000 bytes...
  locate_hole failed
  * failed to load kdump kernel
  ---

  root@ubuntu1410i386:~# cat /sys/kernel/kexec_crash_loaded
  0

  
  If the conversion from hex to dec is right, the mentioned memory mapping of 
0x9f000 bytes is equal to 651264 (bytes), so under 1MB. This is not then 
related to the RAM allocation nor the crashkernel value used.
  --- 
  AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 
2: ls: cannot access /dev/snd/: No such file or directory
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: i386
  ArecordDevices: Error: [Errno 2] No such file or directory
  CRDA: Error: [Errno 2] No such file or directory
  DistroRelease: Ubuntu 14.10
  HibernationDevice: RESUME=UUID=5a5d0aa4-b8ee-4bf7-b1b9-761b7d1550b6
  InstallationDate: Installed on 2014-10-31 (37 days ago)
  InstallationMedia: Ubuntu-Server 14.10 "Utopic Unicorn" - Release i386 
(20141022.2)
  IwConfig:
   lono wireless extensions.
   
   eth0  no wireless extensions.
  Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize 
libusb: -99
  MachineType: Microsoft Corporation Virtual Machine
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 hyperv_fb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-24-generic 
root=UUID=83fb481a-8898-4adc-bf31-4e160f5f0ce8 ro crashkernel=128M-:64M
  ProcVersionSignature: Ubuntu 3.16.0-24.32-generic 3.16.4
  RelatedPackageVersions:
   linux-restricted-modules-3.16.0-24-generic N/A
   linux-backports-modules-3.16.0-24-generic  N/A
   linux-firmware 1.138
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  utopic
  Uname: Linux 3.16.0-24-generic i686
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  WifiSyslog:
   Dec  8 08:16:46 ubuntu1410i386 dhclient: DHCPREQUEST of 10.226.59.102 on 
eth0 to 10.184.232.100 port 67 (xid=0x4b67ffa3)
   Dec  8 08:16:46 ubuntu1410i386 dhclient: DHCPACK of 10.226.59.102 from 
10.184.232.100
   Dec  8 08:16:47 ubuntu1410i386 dhclient: bound to 10.226.59.102 -- renewal 
in 13914 seconds.
   Dec  8 10:10:47 ubuntu1410i386 kernel: [1840786.031060] init: tty1 main 
process ended, respawning
  _MarkForUpload: True
  dmi.bios.date: 05/23/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 090006
  dmi.board.name: Virtual Machine
  dmi.board.vendor: Microsoft Corporation
  dmi.board.version: 7.0
  dmi.chassis.asset.tag: 7176-0455-3377-8479-3268-6677-66
  dmi.chassis.type: 3
  dmi.chassis.vendor: Microsoft Corporation
  dmi.chassis.version: 7.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr090006:bd05/23/2012:svnMicrosoftCorporation:pnVirtualMachine:pvr7.0:rvnMicrosoftCorporation:rnVirtualMachine:rvr7.0:cvnMicrosoftCorporation:ct3:cvr7.0:
  dmi.product.name: Virtual Machine
  dmi.product.version: 7.0
  dmi.sys.vendor: Microsoft Corporation

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/kexec-tools/+bug/1400319/+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 1642739] Re: Kernel panic on shutdown

I'll start a bisect between v4.7 and v4.8-rc1 and post a link to it.

Could you also see if this bug is still happening with the mainline
kernel?  It can be downloaded from:

http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.9-rc5/

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

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

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

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

Title:
  Kernel panic on shutdown

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

Bug description:
  Since I have updated to Ubuntu 16.10 (from 16.04) I have this problem
  where the shutdown takes a long time (~30s) and ends with a (at least
  I think it is) kernel panic with blinking harddrive- and battery
  status LEDs. Nothing is visible on the screen.

  This didnt happen on Ubuntu 16.04 so I tried installing a 4.4 kernel
  and the problem disappeared.

  I have then tested with various kernels from http://kernel.ubuntu.com
  /~kernel-ppa/mainline/ and I have found that the last good kernel is
  4.7.10 and the first bad kernel is 4.8-rc1.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: linux-image-4.8.0-27-generic 4.8.0-27.29
  ProcVersionSignature: Ubuntu 4.8.0-27.29-generic 4.8.1
  Uname: Linux 4.8.0-27-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gustav 1998 F pulseaudio
   /dev/snd/controlC1:  gustav 1998 F pulseaudio
  CurrentDesktop: MATE
  Date: Thu Nov 17 22:01:52 2016
  HibernationDevice: RESUME=UUID=d7a5213f-0285-4708-9e97-2486aec53935
  InstallationDate: Installed on 2016-09-15 (63 days ago)
  InstallationMedia: Ubuntu-MATE 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  Lsusb:
   Bus 001 Device 004: ID 1bcf:28ae Sunplus Innovation Technology Inc. Laptop 
Integrated Webcam HD
   Bus 001 Device 003: ID 8087:0a2a Intel Corp.
   Bus 001 Device 002: ID 8087:8001 Intel Corp.
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Latitude E7450
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-27-generic 
root=UUID=15f681e4-0a4a-4613-8810-ba7535bfa0a0 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-27-generic N/A
   linux-backports-modules-4.8.0-27-generic  N/A
   linux-firmware1.161
  SourcePackage: linux
  UpgradeStatus: Upgraded to yakkety on 2016-10-26 (22 days ago)
  dmi.bios.date: 05/17/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A13
  dmi.board.name: 06HN6G
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA13:bd05/17/2016:svnDellInc.:pnLatitudeE7450:pvr:rvnDellInc.:rn06HN6G:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E7450
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1642739/+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 1642739] Re: Kernel panic on shutdown

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

** Tags added: performing-bisect

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

Title:
  Kernel panic on shutdown

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

Bug description:
  Since I have updated to Ubuntu 16.10 (from 16.04) I have this problem
  where the shutdown takes a long time (~30s) and ends with a (at least
  I think it is) kernel panic with blinking harddrive- and battery
  status LEDs. Nothing is visible on the screen.

  This didnt happen on Ubuntu 16.04 so I tried installing a 4.4 kernel
  and the problem disappeared.

  I have then tested with various kernels from http://kernel.ubuntu.com
  /~kernel-ppa/mainline/ and I have found that the last good kernel is
  4.7.10 and the first bad kernel is 4.8-rc1.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: linux-image-4.8.0-27-generic 4.8.0-27.29
  ProcVersionSignature: Ubuntu 4.8.0-27.29-generic 4.8.1
  Uname: Linux 4.8.0-27-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gustav 1998 F pulseaudio
   /dev/snd/controlC1:  gustav 1998 F pulseaudio
  CurrentDesktop: MATE
  Date: Thu Nov 17 22:01:52 2016
  HibernationDevice: RESUME=UUID=d7a5213f-0285-4708-9e97-2486aec53935
  InstallationDate: Installed on 2016-09-15 (63 days ago)
  InstallationMedia: Ubuntu-MATE 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  Lsusb:
   Bus 001 Device 004: ID 1bcf:28ae Sunplus Innovation Technology Inc. Laptop 
Integrated Webcam HD
   Bus 001 Device 003: ID 8087:0a2a Intel Corp.
   Bus 001 Device 002: ID 8087:8001 Intel Corp.
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Latitude E7450
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-27-generic 
root=UUID=15f681e4-0a4a-4613-8810-ba7535bfa0a0 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-27-generic N/A
   linux-backports-modules-4.8.0-27-generic  N/A
   linux-firmware1.161
  SourcePackage: linux
  UpgradeStatus: Upgraded to yakkety on 2016-10-26 (22 days ago)
  dmi.bios.date: 05/17/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A13
  dmi.board.name: 06HN6G
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA13:bd05/17/2016:svnDellInc.:pnLatitudeE7450:pvr:rvnDellInc.:rn06HN6G:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E7450
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1642739/+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 1642821] Re: Touchpad 3 button click no longer works after resume.

Did this issue start happening after an update/upgrade?  Was there a
prior kernel version where you were not having this particular problem?

Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.9 kernel[0].

If this bug is fixed in the mainline kernel, please add the following
tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag:
'kernel-bug-exists-upstream'.

Once testing of the upstream kernel is complete, please mark this bug as
"Confirmed".


Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.9-rc5


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

** Changed in: linux (Ubuntu)
   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/1642821

Title:
  Touchpad 3 button click no longer works after resume.

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  After suspending the laptop, middle click) on Yoga 2 pro touch pad
  stops working.  Sometimes middle click emulation survives 3 or more
  suspends, but usually not more than 5.

  Only method to restore middle click is to reboot.

  All other touch pad functionality works fine.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: linux-image-4.8.0-27-generic 4.8.0-27.29
  ProcVersionSignature: Ubuntu 4.8.0-27.29-generic 4.8.1
  Uname: Linux 4.8.0-27-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  darin  1299 F pulseaudio
   /dev/snd/controlC0:  darin  1299 F pulseaudio
  CurrentDesktop: KDE
  Date: Thu Nov 17 22:43:20 2016
  HibernationDevice: RESUME=UUID=e7e99dfd-706a-4f9d-ab08-85b062127431
  InstallationDate: Installed on 2016-11-15 (3 days ago)
  InstallationMedia: Kubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.1)
  MachineType: LENOVO 20266
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-27-generic.efi.signed 
root=UUID=ebd9d973-be2f-4f3b-9686-c4141a1a7b67 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-27-generic N/A
   linux-backports-modules-4.8.0-27-generic  N/A
   linux-firmware1.161
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/17/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 76CN27WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Yoga2
  dmi.board.vendor: LENOVO
  dmi.board.version: 31900058STD
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo Yoga 2 Pro
  dmi.modalias: 
dmi:bvnLENOVO:bvr76CN27WW:bd09/17/2013:svnLENOVO:pn20266:pvrLenovoYoga2Pro:rvnLENOVO:rnYoga2:rvr31900058STD:cvnLENOVO:ct10:cvrLenovoYoga2Pro:
  dmi.product.name: 20266
  dmi.product.version: Lenovo Yoga 2 Pro
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1642821/+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 1640921] onibi (i386) - tests ran: 19, failed: 0

tests ran:  19, failed: 0;
  
http://kernel.ubuntu.com/testing/4.4.0-49.70-lowlatency/onibi__4.4.0-49.70__2016-11-18_18-54-00/results-index.html

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

Title:
  linux: 4.4.0-49.70 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
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:
  In Progress
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 4.4.0-49.70 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
  derivative-trackers-created: 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/1640921/+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 1400319] Re: [Hyper-V] Kernel panic not functional on 32bit Ubuntu 14.10, 15.04, and 15.10

Sorry, the test kernel was up one directory.  The kernel is now available in:
http://kernel.ubuntu.com/~jsalisbury/lp1400319/yakkety/

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

Title:
  [Hyper-V] Kernel panic not functional on 32bit Ubuntu 14.10, 15.04,
  and 15.10

Status in kexec-tools package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  In Progress

Bug description:
  While testing the final build of 14.10 32bit we found that kernel
  panic cannot be activated for an installation on a Hyper-V VM.

  Repro rate: 100%
  Repro details:
  Hyper-V: Server 2012 R2
  VM: Ubuntu 14.10 32bit

  Kdump is enabled in the config file at /etc/default/kdump-tools

  Different crashkernel values used in grub.cfg – 128M-:64M | 256M-:128m
  | 384M-:256M

  VM settings: 2 cores, various RAM sizes attempted: 1, 2 or 4 GB – this
  in combination with the values for crashkernel.

  Trying to start the kdump service:
  root@ubuntu1410i386:~# /etc/init.d/kdump-tools start
  Starting kdump-tools: Could not find a free area of memory of 0x9f000 bytes...
  locate_hole failed
  * failed to load kdump kernel
  ---

  root@ubuntu1410i386:~# cat /sys/kernel/kexec_crash_loaded
  0

  
  If the conversion from hex to dec is right, the mentioned memory mapping of 
0x9f000 bytes is equal to 651264 (bytes), so under 1MB. This is not then 
related to the RAM allocation nor the crashkernel value used.
  --- 
  AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 
2: ls: cannot access /dev/snd/: No such file or directory
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: i386
  ArecordDevices: Error: [Errno 2] No such file or directory
  CRDA: Error: [Errno 2] No such file or directory
  DistroRelease: Ubuntu 14.10
  HibernationDevice: RESUME=UUID=5a5d0aa4-b8ee-4bf7-b1b9-761b7d1550b6
  InstallationDate: Installed on 2014-10-31 (37 days ago)
  InstallationMedia: Ubuntu-Server 14.10 "Utopic Unicorn" - Release i386 
(20141022.2)
  IwConfig:
   lono wireless extensions.
   
   eth0  no wireless extensions.
  Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize 
libusb: -99
  MachineType: Microsoft Corporation Virtual Machine
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 hyperv_fb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-24-generic 
root=UUID=83fb481a-8898-4adc-bf31-4e160f5f0ce8 ro crashkernel=128M-:64M
  ProcVersionSignature: Ubuntu 3.16.0-24.32-generic 3.16.4
  RelatedPackageVersions:
   linux-restricted-modules-3.16.0-24-generic N/A
   linux-backports-modules-3.16.0-24-generic  N/A
   linux-firmware 1.138
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  utopic
  Uname: Linux 3.16.0-24-generic i686
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  WifiSyslog:
   Dec  8 08:16:46 ubuntu1410i386 dhclient: DHCPREQUEST of 10.226.59.102 on 
eth0 to 10.184.232.100 port 67 (xid=0x4b67ffa3)
   Dec  8 08:16:46 ubuntu1410i386 dhclient: DHCPACK of 10.226.59.102 from 
10.184.232.100
   Dec  8 08:16:47 ubuntu1410i386 dhclient: bound to 10.226.59.102 -- renewal 
in 13914 seconds.
   Dec  8 10:10:47 ubuntu1410i386 kernel: [1840786.031060] init: tty1 main 
process ended, respawning
  _MarkForUpload: True
  dmi.bios.date: 05/23/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 090006
  dmi.board.name: Virtual Machine
  dmi.board.vendor: Microsoft Corporation
  dmi.board.version: 7.0
  dmi.chassis.asset.tag: 7176-0455-3377-8479-3268-6677-66
  dmi.chassis.type: 3
  dmi.chassis.vendor: Microsoft Corporation
  dmi.chassis.version: 7.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr090006:bd05/23/2012:svnMicrosoftCorporation:pnVirtualMachine:pvr7.0:rvnMicrosoftCorporation:rnVirtualMachine:rvr7.0:cvnMicrosoftCorporation:ct3:cvr7.0:
  dmi.product.name: Virtual Machine
  dmi.product.version: 7.0
  dmi.sys.vendor: Microsoft Corporation

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/kexec-tools/+bug/1400319/+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 1590590] Re: Touchpad not recognized on Dell Latitude E7470 Ultrabook

2016-11-18 Thread bagl0312

@chmelab @pmonas indeed I was wondering if this kind of fix are expected to be 
backported to relevant older kernels.
In this case it should be backported at least to the 4.4.x series.

I have experience of other bug fixes backported to previous kernel
versions, so this should be the case also for this fix. I just would
like to be sure that the right developers are informed that this is a
very annoying issue which deserves a fix as soon as possible for the LTS
distributions

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

Title:
  Touchpad not recognized on Dell Latitude E7470 Ultrabook

Status in linux package in Ubuntu:
  Triaged
Status in xserver-xorg-input-synaptics package in Ubuntu:
  Confirmed

Bug description:
  Expected: Touchpad settings available in Mouse & Touchpad Settings
  dialog

  Actual result: Touchpad settings missing entirely

  
  Details:
  The touchpad on my Dell Ultrabook (Latitude E7470) functions mostly. 

  The settings for the touchpad are not available at all in the Mouse
  and Touchpad settings (see http://i.imgur.com/YRGiOrj.png).

  Two-finger scrolling works as expected except it's using "Natural
  Scrolling" by default and there is no way to change it.

  xinput list does not display a touchpad at all:

  ⎡ Virtual core pointerid=2[master pointer  (3)]
  ⎜   ↳ Virtual core XTEST pointer  id=4[slave  pointer 
 (2)]
  ⎜   ↳ ELAN Touchscreenid=11   [slave  pointer 
 (2)]
  ⎜   ↳ ImPS/2 Generic Wheel Mouse  id=13   [slave  pointer 
 (2)]
  ⎣ Virtual core keyboard   id=3[master keyboard (2)]
  ↳ Virtual core XTEST keyboard id=5[slave  
keyboard (3)]
  ↳ Power Buttonid=6[slave  
keyboard (3)]
  ↳ Video Bus   id=7[slave  
keyboard (3)]
  ↳ Power Buttonid=8[slave  
keyboard (3)]
  ↳ Sleep Buttonid=9[slave  
keyboard (3)]
  ↳ Integrated_Webcam_FHD   id=10   [slave  
keyboard (3)]
  ↳ AT Translated Set 2 keyboardid=12   [slave  
keyboard (3)]
  ↳ Dell WMI hotkeysid=14   [slave  
keyboard (3)]
  ↳ DELL Wireless hotkeys   id=15   [slave  
keyboard (3)]

  
  /proc/bus/input/devices lists the device as a "Generic Wheel Mouse"

  Output of `lsb_release -rd`:
  Description:  Ubuntu 16.04 LTS
  Release:  16.04

  xserver-xorg-input-synaptics version information:
  xserver-xorg-input-synaptics:
Installed: 1.8.2-1ubuntu3
Candidate: 1.8.2-1ubuntu3
Version table:
   *** 1.8.2-1ubuntu3 500
  500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  100 /var/lib/dpkg/status

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1590590/+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 1635721] Re: Add a driver for Amazon Elastic Network Adapters (ENA)

2016-11-18 Thread Kamal Mostafa

Zesty already carries this (landed in mainline ~v4.9-rc1)

** No longer affects: linux (Ubuntu 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/1635721

Title:
  Add a driver for Amazon Elastic Network Adapters (ENA)

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Trusty:
  Fix Committed
Status in linux source package in Xenial:
  Fix Released
Status in linux source package in Yakkety:
  Confirmed

Bug description:
  Back-porting this driver to Ubuntu LTS generic kernels would be
  beneficial.

  commit 1738cd3ed342294360d6a74d4e5884bff854 linux-next
  "net: ena: Add a driver for Amazon Elastic Network Adapters (ENA)"

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1635721/+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 1642299] Re: Fix Kernel Crashing under IBM Virtual Scsi Driver

https://lists.ubuntu.com/archives/kernel-team/2016-November/081044.html

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

Title:
  Fix Kernel Crashing under IBM Virtual Scsi Driver

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

Bug description:
  Kernel crashes running large amounts of deployment using Ibmvscsis driver. 
   
  Contact Information = Bryant Ly/b...@us.ibm.com 
   
  Stack trace output:
   
  [ 1780.861532] Faulting instruction address: 0xc0583de0
  [ 1780.861542] Oops: Kernel access of bad area, sig: 11 [#1]
  [ 1780.861549] SMP NR_CPUS=2048 NUMA pSeries
  [ 1780.861557] Modules linked in: ip6table_filter ip6_tables xt_tcpudp 
iptable_mangle ebt_arp ebt_among ebtable_filter ebtables iptable_nat 
nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack iptable_filter 
ip_tables x_tables bridge stp llc target_core_user uio target_core_pscsi 
target_core_file dccp_diag target_core_iblock iscsi_target_mod dccp tcp_diag 
udp_diag inet_diag unix_diag af_packet_diag netlink_diag binfmt_misc 
pseries_rng ibmvmc(OE) rtc_generic ib_iser rdma_cm iw_cm ib_cm ib_sa ib_mad 
ib_core ib_addr iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi autofs4 
mlx4_en vxlan ip6_udp_tunnel udp_tunnel ses enclosure ibmvscsis target_core_mod 
configfs ibmveth mlx4_core megaraid_sas ahci libahci
  [ 1780.861707] CPU: 22 PID: 35128 Comm: tcmu-runner Tainted: GW  OE   
4.4.13-customv7 #22
  [ 1780.861718] task: c001e6f50080 ti: c001e6fd task.ti: 
c001e6fd
  [ 1780.861727] NIP: c0583de0 LR: d65c1b04 CTR: 
c0583da0
  [ 1780.861736] REGS: c001e6fd3950 TRAP: 0300   Tainted: GW  OE
(4.4.13-customv7)
  [ 1780.861745] MSR: 80009033   CR: 48004484  
XER: 2000
  [ 1780.861770] CFAR: c0008468 DAR: 12a0 DSISR: 4000 
SOFTE: 0
  GPR00: d65c1974 c001e6fd3bd0 d65cba00 1298
  GPR04: 12b8 c001fe664468 0018 646920726f662064
  GPR08: 0007 0001 1298 d65c2870
  GPR12: c0583da0 c7add100  
  GPR16: 3fffae67  0002 0001
  GPR20: c001e99032e8  c001e9903300 f000
  GPR24: c001e9903340  d660 d6600080
  GPR28: c001e9902000 0080 f0019800 c001fe664458
  [ 1780.861901] NIP [c0583de0] __bitmap_xor+0x40/0x60
  [ 1780.861910] LR [d65c1b04] tcmu_handle_completions+0x394/0x510 
[target_core_user]
  [ 1780.861919] Call Trace:
  [ 1780.861926] [c001e6fd3bd0] [d65c1974] 
tcmu_handle_completions+0x204/0x510 [target_core_user] (unreliable)
  [ 1780.861942] [c001e6fd3cd0] [d65c1cac] 
tcmu_irqcontrol+0x2c/0x50 [target_core_user]
  [ 1780.861956] [c001e6fd3d00] [d6561798] uio_write+0x98/0x140 
[uio]
  [ 1780.861966] [c001e6fd3d50] [c02dda0c] __vfs_write+0x6c/0xe0
  [ 1780.861977] [c001e6fd3d90] [c02de740] vfs_write+0xc0/0x230
  [ 1780.861988] [c001e6fd3de0] [c02df77c] SyS_write+0x6c/0x110
  [ 1780.861999] [c001e6fd3e30] [c0009204] system_call+0x38/0xb4
  [ 1780.862007] Instruction dump:
  [ 1780.862013] 78c60020 3944fff8 38c6 38a5fff8 78c61f48 3863fff8 7c843214 
4814
  [ 1780.862033] 6000 6000 6000 6042  e9050009 
7faa2040 7d294278
  [ 1780.862056] ---[ end trace 212caf961ccdad3d ]---

  
  A series of patches will fix this issue. 
ibmvscsis: Rearrange functions for future patches
ibmvscsis: Synchronize cmds at tpg_enable_store time
ibmvscsis: Synchronize cmds at remove time
ibmvscsis: Clean up properly if target_submit_cmd/tmr fails
ibmvscsis: Return correct partition name/# to client
ibmvscsis: Issues from Dan Carpenter/Smatch
  http://www.spinics.net/lists/linux-scsi/msg100569.html

  The patch has been accepted and applied to 4.10/scsi-queue.

  scsi: ibmvscsis: Rearrange functions for future patches
  
https://kernel.googlesource.com/pub/scm/linux/kernel/git/mkp/scsi/+/fbbcc033a20a6af94eeb8fa995668ed5051be111

  scsi: ibmvscsis: Synchronize cmds at tpg_enable_store time
  
https://kernel.googlesource.com/pub/scm/linux/kernel/git/mkp/scsi/+/f877a5398764ce18487c1a70f297743ae91a0e25

  scsi: ibmvscsis: Synchronize cmds at remove time
  
https://kernel.googlesource.com/pub/scm/linux/kernel/git/mkp/scsi/+/5dda944d439e295cadceb1e2d7f5b73f9dc2b296

  scsi: ibmvscsis: Clean up properly if target_submit_cmd/tmr fails

[Kernel-packages] [Bug 1641083] onza (i386) - tests ran: 1, failed: 0

tests ran:   1, failed: 0;
  
http://kernel.ubuntu.com/testing/4.8.0-28.30-generic/onza__4.8.0-28.30__2016-11-18_19-16-00/results-index.html

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

Title:
  linux: 4.8.0-28.30 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
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:
  In Progress
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 Yakkety:
  Confirmed

Bug description:
  This bug is for tracking the 4.8.0-28.30 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
  derivative-trackers-created: 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/1641083/+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 1634449] Re: Black flicker when leaving monitor

2016-11-18 Thread Andrew

For anyone else just looking for a workaround, I've had success with
this arrangement. I don't really know what I'm doing, so imitate at your
own risk.

Hardware:
Dell XPS 13 9350 Developer Edition
Cable Matters 201016
Dell P2415Q
Distribution:
Ubuntu 16.10
Linux 4.9 from zesty:
$ cat /etc/apt/sources.list.d/zesty.list
deb http://us.archive.ubuntu.com/ubuntu/ zesty   main restricted 
universe multiverse
deb http://us.archive.ubuntu.com/ubuntu/ zesty-updates   main restricted 
universe multiverse
deb http://us.archive.ubuntu.com/ubuntu/ zesty-backports main restricted 
universe multiverse
deb http://us.archive.ubuntu.com/ubuntu/ zesty-proposed  main restricted 
universe multiverse
deb http://security.ubuntu.com/ubuntuzesty-security  main restricted 
universe multiverse
$ cat /etc/apt/preferences.d/zesty
Package: *
Pin: release n=zesty
Pin-Priority: 400
$ sudo apt install -t zesty linux-image-generic
Docker options:
--storage-driver=overlay2

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

Title:
  Black flicker when leaving monitor

Status in linux package in Ubuntu:
  Triaged

Bug description:
  Sometimes, when moving cursor from one monitor to the other, the
  external monitor turns black and gets back on again.

  The hardware is Dell Latitude E5470 with Docking Station and monitor
  connected via DisplayPort (checked both ports and happens on both of
  them).

  Everything worked correctly on Ubuntu 16.04, but it happens on Ubuntu
  16.10. Kernel 4.8.0-25-generic.

  The bug isn't related to cursor only, if focus changes by alt+tab it
  sometimes happens as well.

  
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1553503 This is the same 
bug as this one, but closed.
  --- 
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   vessel 5602 F...m pulseaudio
   /dev/snd/controlC0:  vessel 5602 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.10
  HibernationDevice: RESUME=UUID=56fab9c8-7226-47b9-91cb-a2c865f81bc0
  InstallationDate: Installed on 2016-08-31 (47 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: Dell Inc. Latitude E5470
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.8.0-25-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.8.0-25.27-generic 4.8.1
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-25-generic N/A
   linux-backports-modules-4.8.0-25-generic  N/A
   linux-firmware1.161
  Tags:  yakkety
  Uname: Linux 4.8.0-25-generic x86_64
  UpgradeStatus: Upgraded to yakkety on 2016-10-14 (3 days ago)
  UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 06/15/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.7.3
  dmi.board.name: 0P88J9
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.7.3:bd06/15/2016:svnDellInc.:pnLatitudeE5470:pvr:rvnDellInc.:rn0P88J9:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E5470
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1634449/+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 1641083] onza (amd64) - tests ran: 1, failed: 0

tests ran:   1, failed: 0;
  
http://kernel.ubuntu.com/testing/4.8.0-28.30-generic/onza__4.8.0-28.30__2016-11-18_18-50-00/results-index.html

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

Title:
  linux: 4.8.0-28.30 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
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:
  In Progress
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 Yakkety:
  Confirmed

Bug description:
  This bug is for tracking the 4.8.0-28.30 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
  derivative-trackers-created: 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/1641083/+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 1626436] Re: [4.8 regression] boot has become very slow

Yes, that result is unexpected.   So it sounds like v4.9-rc5 without the
patches is still bad, but adding the two patches fixes the bug.

I built another -proposed Yakkety test kernel with those two patches. It can be 
downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1626436/yakkety-proposed-patched

It may be that 4.9-rc5 has additional commits that are also needed.  If
this Yakkety test kernel is still bad, I'll review what additional
commits are in -rc5.

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

Title:
  [4.8 regression] boot has become very slow

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

Bug description:
  With yakkety's recent update from linux 4.4 to 4.8 booting has become
  a lot slower. It's not one service in particular, but without "quiet"
  and "splash" you can now easily read every single line instead of that
  whole wall of text zipping by. It now takes over 20s instead of ~10
  seconds to boot.

  This is even more dramatic when factoring out the recent boot hang of
  NetworkManager (bug 1622893) and disabling lightdm:

    sudo systemctl mask NetworkManager NetworkManager-wait-online
  lightdm

  then booting with 4.4 takes 1.5s and with 4.8 19.5s (!).

  Some excerps from systemd-analyze blame:

  4.4:
     474ms postfix@-.service
     395ms lxd-containers.service
     305ms networking.service

  4.8:
    4.578s postfix@-.service
    7.300s lxd-containers.service
    6.285s networking.service

  I attach the full outputs of critical-chain and analyze for 4.4 and
  4.8 for reference.

  This is much less noticeable in the running system. There is no
  immediate feeling of sluggishness (although my system is by and large
  idle).

  I compared the time of sbuilding colord under similar circumstances
  (-j4, building on tmpfs, thus no hard disk delays; running with fully
  pre-loaded apt-cacher-ng thus no random network delays), and with 4.4
  it takes 6.5 minutes and with 4.8 it takes 7.5. So that got a bit
  slower, but much less dramatically than during boot, so this is either
  happening when a lot of processes run in parallel, or is perhaps
  related to setting up cgroups.

  One thing I noticed that during sbuild in 4.8 "top" shows ridiculous
  loads (~ 250) under 4.8, while it's around 4 or 5 under 4.4. But that
  doesn't reflect in actual sluggishness, so this might be just an
  unrelated bug.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: linux-image-4.8.0-11-generic 4.8.0-11.12
  ProcVersionSignature: Ubuntu 4.8.0-11.12-generic 4.8.0-rc6
  Uname: Linux 4.8.0-11-generic x86_64
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0c:   martin 3049 F...m pulseaudio
   /dev/snd/pcmC0D0p:   martin 3049 F...m pulseaudio
   /dev/snd/controlC0:  martin 3049 F pulseaudio
  Date: Thu Sep 22 09:42:56 2016
  EcryptfsInUse: Yes
  MachineType: LENOVO 2324CTO
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.8.0-11-generic.efi.signed 
root=UUID=f86539b0-3a1b-4372-83b0-acdd029ade68 ro rootflags=subvol=@ 
systemd.debug-shell
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-11-generic N/A
   linux-backports-modules-4.8.0-11-generic  N/A
   linux-firmware1.161
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/09/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G2ET95WW (2.55 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 2324CTO
  dmi.board.vendor: LENOVO
  dmi.board.version: 0B98401 Pro
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrG2ET95WW(2.55):bd07/09/2013:svnLENOVO:pn2324CTO:pvrThinkPadX230:rvnLENOVO:rn2324CTO:rvr0B98401Pro:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 2324CTO
  dmi.product.version: ThinkPad X230
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1626436/+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 1640921] onza (i386) - tests ran: 1, failed: 0

tests ran:   1, failed: 0;
  
http://kernel.ubuntu.com/testing/4.4.0-49.70-lowlatency/onza__4.4.0-49.70__2016-11-18_18-25-00/results-index.html

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

Title:
  linux: 4.4.0-49.70 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
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:
  In Progress
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 4.4.0-49.70 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
  derivative-trackers-created: 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/1640921/+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 1629603] Re: Wifi stops working sporadically

2016-11-18 Thread mxyzptlk

Don't know if this will help, but I heard that Ubuntu Mate does
something different with their network stack, so I switched (Ubuntu Mate
16.10). I had this same wifi drop with both Unity and Gnome 3, but have
had pretty much no issues on Ubuntu Mate -- one crash in a week, and I'm
not even sure that was the same as this problem and not something else.

So it may help to know that what isn't working in Unity/Gnome 3 does
work in Mate.

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

Title:
  Wifi stops working sporadically

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Since 16.04 I have been having trouble with WIFI stopping working
  daily and requiring a reboot to fix.

  This happens at worst multiple times a day and I dont know what could
  trigger it, the connection just stops working with no apparent reason
  and I cant get it back without a reboot.

  I did not have this problem with 15.10.

  My access point is ASUS RT-N12E_B1. I did not experience this issue
  when I was using a different access point for a few days so I'm not
  sure whether the cause is something specific to this wifi environment.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: linux-image-4.8.0-17-generic 4.8.0-17.19
  ProcVersionSignature: Ubuntu 4.8.0-17.19-generic 4.8.0-rc7
  Uname: Linux 4.8.0-17-generic i686
  NonfreeKernelModules: nvidia_uvm nvidia
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  lelux  2188 F pulseaudio
  CurrentDesktop: MATE
  Date: Sat Oct  1 22:56:40 2016
  HibernationDevice: RESUME=UUID=f9484e9d-673f-4b04-9e39-52035ccf958b
  InstallationDate: Installed on 2016-09-28 (3 days ago)
  InstallationMedia: Ubuntu-MATE 16.10 "Yakkety Yak" - Alpha i386 (20160921)
  MachineType: LENOVO 7665WM6
  PccardctlIdent:
   Socket 0:
 no product info available
  PccardctlStatus:
   Socket 0:
 no card
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.8.0-17-generic 
root=/dev/mapper/ubuntu--mate--vg-root ro quiet splash
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-17-generic N/A
   linux-backports-modules-4.8.0-17-generic  N/A
   linux-firmware1.161
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/18/2011
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 7LETC9WW (2.29 )
  dmi.board.name: 7665WM6
  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:bvr7LETC9WW(2.29):bd03/18/2011:svnLENOVO:pn7665WM6:pvrThinkPadT61:rvnLENOVO:rn7665WM6:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 7665WM6
  dmi.product.version: ThinkPad T61
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1629603/+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 1640921] onibi (amd64) - tests ran: 19, failed: 0

tests ran:  19, failed: 0;
  
http://kernel.ubuntu.com/testing/4.4.0-49.70-lowlatency/onibi__4.4.0-49.70__2016-11-18_17-23-00/results-index.html

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

Title:
  linux: 4.4.0-49.70 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
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:
  In Progress
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 4.4.0-49.70 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
  derivative-trackers-created: 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/1640921/+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 1609601] Re: i2c_hid: probe of i2c-ELAN0732:00 failed with error-61

2016-11-18 Thread Colin Johnstone

I never did get that working, even building direct from upstream. I
ended up putting Windows 10 back onto the computer just to make sure it
wasn’t a hardware error (and also because the BIOS can only be flashed
from within Windows. Thanks, HP.) Touchscreen works in Win10, so it’s
definitely software.

From: Abhay
Sent: Friday, November 18, 2016 12:45 PM
To: johnstone.co...@gmail.com
Subject: [Bug 1609601] Re: i2c_hid: probe of i2c-ELAN0732:00 failed with 
error-61

Hi Colin,
 were you able to get the touchscreen working ? 
I am also having the exact same laptop model.
with the latest available kernel 4.8.7 i don't see the gpio interrupt errors, 
but also i don't see anything touchscreen added to xinput as well. 
  Since I didnt find any resolution in your upstream bug as well, can you 
please let me know how you were able to fix it ?
  I am an ex-AMD vlsi engineer, so if needed I can try to connect with AMD 
software engineers as well.

-- 
You received this bug notification because you are subscribed to the bug
report.
https://bugs.launchpad.net/bugs/1609601

Title:
  i2c_hid: probe of i2c-ELAN0732:00 failed with error -61

Status in linux package in Ubuntu:
  Triaged

Bug description:
  I'm using an HP Envy x360 M6-ar004dx with an AMD 7th-gen FX APU, and
  the touchscreen will not work. Dmesg shows i2c_hid reporting multiple
  "failed to reset device" error messages before finally failing to add
  it as an HID device with error -61. As far as I can tell, it's being
  detected as an ELAN touchscreen. I've seen reports that this error can
  be fixed in newer kernels, as the touchscreen uses GPIO interrupts
  which are fixed in versions 4.6 and later. Most of the information I
  can find indicates that 4.7 includes improved AMD support, but the
  mainline kernel build appears to be missing the AMD GPIO drivers,
  since I get a "failed to get GPIO interrupt" error. I've compiled my
  own 4.7 kernel from the mainline GIT, including the patches used in
  kernel-ppa/mainline and setting the right config flags for AMD GPIO,
  but that just gets me the same errors I'm seeing in 4.4.0-31-generic.
  For additional info, I'm attaching my dmesg output in its entirety.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-31-generic 4.4.0-31.50 [modified: 
boot/vmlinuz-4.4.0-31-generic]
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  Uname: Linux 4.4.0-31-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  colin  3591 F pulseaudio
   /dev/snd/controlC0:  colin  3591 F pulseaudio
  CurrentDesktop: GNOME
  Date: Wed Aug  3 21:51:47 2016
  HibernationDevice: RESUME=UUID=1875834b-d1ff-4b97-a9b8-44afb056c592
  InstallationDate: Installed on 2016-08-03 (0 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160720)
  MachineType: HP HP ENVY x360 m6 Convertible
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-31-generic.efi.signed 
root=/dev/mapper/ubuntu--gnome--vg-root ro quiet splash
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-31-generic N/A
   linux-backports-modules-4.4.0-31-generic  N/A
   linux-firmware1.157.2
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/29/2016
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.10
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 81AA
  dmi.board.vendor: HP
  dmi.board.version: 59.42
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.10:bd06/29/2016:svnHP:pnHPENVYx360m6Convertible:pvrType1ProductConfigId:rvnHP:rn81AA:rvr59.42:cvnHP:ct10:cvrChassisVersion:
  dmi.product.name: HP ENVY x360 m6 Convertible
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP

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

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

Title:
  i2c_hid: probe of i2c-ELAN0732:00 failed with error -61

Status in linux package in Ubuntu:
  Triaged

Bug description:
  I'm using an HP Envy x360 M6-ar004dx with an AMD 7th-gen FX APU, and
  the touchscreen will not work. Dmesg shows i2c_hid reporting multiple
  "failed to reset device" error messages before finally failing to add
  it as an HID device with error -61. As far as I can tell, it's being
  detected as an ELAN touchscreen. I've seen reports that this error can
  be fixed in newer kernels, as the touchscreen uses GPIO interrupts
  which are fixed in versions

[Kernel-packages] [Bug 1609601] Re: i2c_hid: probe of i2c-ELAN0732:00 failed with error -61

2016-11-18 Thread Abhay

Hi Colin,
 were you able to get the touchscreen working ? 
I am also having the exact same laptop model.
with the latest available kernel 4.8.7 i don't see the gpio interrupt errors, 
but also i don't see anything touchscreen added to xinput as well. 
  Since I didnt find any resolution in your upstream bug as well, can you 
please let me know how you were able to fix it ?
  I am an ex-AMD vlsi engineer, so if needed I can try to connect with AMD 
software engineers as well.

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

Title:
  i2c_hid: probe of i2c-ELAN0732:00 failed with error -61

Status in linux package in Ubuntu:
  Triaged

Bug description:
  I'm using an HP Envy x360 M6-ar004dx with an AMD 7th-gen FX APU, and
  the touchscreen will not work. Dmesg shows i2c_hid reporting multiple
  "failed to reset device" error messages before finally failing to add
  it as an HID device with error -61. As far as I can tell, it's being
  detected as an ELAN touchscreen. I've seen reports that this error can
  be fixed in newer kernels, as the touchscreen uses GPIO interrupts
  which are fixed in versions 4.6 and later. Most of the information I
  can find indicates that 4.7 includes improved AMD support, but the
  mainline kernel build appears to be missing the AMD GPIO drivers,
  since I get a "failed to get GPIO interrupt" error. I've compiled my
  own 4.7 kernel from the mainline GIT, including the patches used in
  kernel-ppa/mainline and setting the right config flags for AMD GPIO,
  but that just gets me the same errors I'm seeing in 4.4.0-31-generic.
  For additional info, I'm attaching my dmesg output in its entirety.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-31-generic 4.4.0-31.50 [modified: 
boot/vmlinuz-4.4.0-31-generic]
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  Uname: Linux 4.4.0-31-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  colin  3591 F pulseaudio
   /dev/snd/controlC0:  colin  3591 F pulseaudio
  CurrentDesktop: GNOME
  Date: Wed Aug  3 21:51:47 2016
  HibernationDevice: RESUME=UUID=1875834b-d1ff-4b97-a9b8-44afb056c592
  InstallationDate: Installed on 2016-08-03 (0 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160720)
  MachineType: HP HP ENVY x360 m6 Convertible
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-31-generic.efi.signed 
root=/dev/mapper/ubuntu--gnome--vg-root ro quiet splash
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-31-generic N/A
   linux-backports-modules-4.4.0-31-generic  N/A
   linux-firmware1.157.2
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/29/2016
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.10
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 81AA
  dmi.board.vendor: HP
  dmi.board.version: 59.42
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.10:bd06/29/2016:svnHP:pnHPENVYx360m6Convertible:pvrType1ProductConfigId:rvnHP:rn81AA:rvr59.42:cvnHP:ct10:cvrChassisVersion:
  dmi.product.name: HP ENVY x360 m6 Convertible
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1609601/+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 1641127] Re: Network interface is not coming up

2016-11-18 Thread Raghuram Banda

I have upgraded the kernel to 4.9.0-040900rc5-generic and the issue
mentioned in this defect is resolved. However, as part of our testing
whenever the  command -

ethtool -L enp5s0f0 other 0 rx 18 combined 0 tx 18

is executed on NIC is going down. If I am trying to up the interface I am 
getting below error.
 
ifconfig enp5s0f0 up
SIOCSIFFLAGS: Operation not permitted
 
In-order to make the interface up, we need to remove and load the bnxt_en 
driver again.
 
Please find the card details.
 
ethtool -i enp5s0f0
driver: bnxt_en
version: 1.5.0
firmware-version: 20.6.39/1.5.4 pkg 20.06.00.25
expansion-rom-version:
bus-info: :05:00.0
supports-statistics: yes
supports-test: no
supports-eeprom-access: yes
supports-register-dump: no
supports-priv-flags: no

Please let me know if I need to closed this defect and open a new defect
to track this issue and what all logs you need for this?

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

Title:
  Network interface is not coming up

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Fresh installation of Ubuntu 16.04 and even after executing ifconfig
   up, the network interface is not coming up. Below are the
  kernel and driver details:

  lsb_release -rd
  Description:Ubuntu 16.04
  Release:16.04

  cat /proc/version_signature
  Ubuntu 4.4.0-47.68-generic 4.4.24

  sudo lspci -vnvn > lspci-vnvn.log
  Attached the .log file

  Basically bnxt_en driver needs to be updated with latest HWRM spec.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1641127/+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 1641322] Re: frequently lost connection to nvme

2016-11-18 Thread Thomas M Steenholdt

I've not found a positive match, but this MIGHT be related to the
following upstream bug.

https://bugzilla.kernel.org/show_bug.cgi?id=112121


** Bug watch added: Linux Kernel Bug Tracker #112121
   http://bugzilla.kernel.org/show_bug.cgi?id=112121

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

Title:
  frequently lost connection to nvme

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Since before the release of Yakkety Yak, I've been having problems
  with a new laptop with a Samsung nvme device: 05:00.0 Non-Volatile
  memory controller: Samsung Electronics Co Ltd Device a804 (prog-if 02
  [NVM Express])

  For whatever reason, I sometimes (often) loose connection to the
  device, causing the entire system to stop working until a powercycle
  has been completed. I can go a full day without having the problem -
  Just as I can have an entire night of the system just refusing to be
  stable for long enough to be usable.

  I've tried with official kernels and mainline kernels of 4.8 and 4.9
  versions of the kernel, but all show the exact same problem at one
  point or another.

  I'm aware that this COULD be a hardware-related issue, but have no
  real way to be certain at this point. The system is a brand new Lenovo
  ThinkPad T460s.

  Dmesg always shows the following few lines, in association with the
  error:

  kern  :warn  : [Nov12 03:34] nvme :05:00.0: Failed status: 0x, 
reset controller.
  kern  :warn  : [  +0,017726] pci_raw_set_power_state: 40 callbacks suppressed
  kern  :info  : [  +0,04] nvme :05:00.0: Refused to change power 
state, currently in D3
  kern  :warn  : [  +0,91] nvme nvme0: Removing after probe failure status: 
-19
  kern  :info  : [  +0,13] nvme0n1: detected capacity change from 
1024209543168 to 0

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: linux-image-4.8.0-27-generic 4.8.0-27.29
  ProcVersionSignature: Ubuntu 4.8.0-27.29-generic 4.8.1
  Uname: Linux 4.8.0-27-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  thms   1592 F pulseaudio
  CurrentDesktop: GNOME
  Date: Sat Nov 12 11:59:50 2016
  HibernationDevice: RESUME=UUID=aeb50d49-fb7a-4e4c-928c-582e6a77ad7e
  InstallationDate: Installed on 2016-10-15 (28 days ago)
  InstallationMedia: Ubuntu-GNOME 16.10 "Yakkety Yak" - Release amd64 
(20161012.1)
  MachineType: LENOVO 20FAS43T00
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-27-generic.efi.signed 
root=UUID=881c937d-6215-43a5-b57a-257adaee046b ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-27-generic N/A
   linux-backports-modules-4.8.0-27-generic  N/A
   linux-firmware1.161
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/08/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1CET47W (1.15 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20FAS43T00
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN1CET47W(1.15):bd08/08/2016:svnLENOVO:pn20FAS43T00:pvrThinkPadT460s:rvnLENOVO:rn20FAS43T00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.name: 20FAS43T00
  dmi.product.version: ThinkPad T460s
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1641322/+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 1590590] Re: Touchpad not recognized on Dell Latitude E7470 Ultrabook

2016-11-18 Thread Adam

@chmelab It's not currently fixed in 4.4.x; the question is whether it's
going to be fixed in the 4.4.x kernel at any point in the future, and if
so, when. (from my point of view I'd rather not move away from LTS
unless absolutely necessary)

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

Title:
  Touchpad not recognized on Dell Latitude E7470 Ultrabook

Status in linux package in Ubuntu:
  Triaged
Status in xserver-xorg-input-synaptics package in Ubuntu:
  Confirmed

Bug description:
  Expected: Touchpad settings available in Mouse & Touchpad Settings
  dialog

  Actual result: Touchpad settings missing entirely

  
  Details:
  The touchpad on my Dell Ultrabook (Latitude E7470) functions mostly. 

  The settings for the touchpad are not available at all in the Mouse
  and Touchpad settings (see http://i.imgur.com/YRGiOrj.png).

  Two-finger scrolling works as expected except it's using "Natural
  Scrolling" by default and there is no way to change it.

  xinput list does not display a touchpad at all:

  ⎡ Virtual core pointerid=2[master pointer  (3)]
  ⎜   ↳ Virtual core XTEST pointer  id=4[slave  pointer 
 (2)]
  ⎜   ↳ ELAN Touchscreenid=11   [slave  pointer 
 (2)]
  ⎜   ↳ ImPS/2 Generic Wheel Mouse  id=13   [slave  pointer 
 (2)]
  ⎣ Virtual core keyboard   id=3[master keyboard (2)]
  ↳ Virtual core XTEST keyboard id=5[slave  
keyboard (3)]
  ↳ Power Buttonid=6[slave  
keyboard (3)]
  ↳ Video Bus   id=7[slave  
keyboard (3)]
  ↳ Power Buttonid=8[slave  
keyboard (3)]
  ↳ Sleep Buttonid=9[slave  
keyboard (3)]
  ↳ Integrated_Webcam_FHD   id=10   [slave  
keyboard (3)]
  ↳ AT Translated Set 2 keyboardid=12   [slave  
keyboard (3)]
  ↳ Dell WMI hotkeysid=14   [slave  
keyboard (3)]
  ↳ DELL Wireless hotkeys   id=15   [slave  
keyboard (3)]

  
  /proc/bus/input/devices lists the device as a "Generic Wheel Mouse"

  Output of `lsb_release -rd`:
  Description:  Ubuntu 16.04 LTS
  Release:  16.04

  xserver-xorg-input-synaptics version information:
  xserver-xorg-input-synaptics:
Installed: 1.8.2-1ubuntu3
Candidate: 1.8.2-1ubuntu3
Version table:
   *** 1.8.2-1ubuntu3 500
  500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  100 /var/lib/dpkg/status

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1590590/+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 1614887] Re: Lage samba file transfers block btrfs to hung task

2016-11-18 Thread S. W.

still valid in yakkety and 4.8.0-27


[  726.382817] INFO: task kworker/u4:7:1659 blocked for more than 120 seconds.
[  726.382819]   Not tainted 4.8.0-27-generic #29-Ubuntu
[  726.382820] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this 
message.
[  726.382820] kworker/u4:7D 98c792b57c48 0  1659  2 0x
[  726.382836] Workqueue: btrfs-endio-write btrfs_endio_write_helper [btrfs]
[  726.382838]  98c792b57c48  98c7b8231a00 
98c7b3cf5b00
[  726.382839]  10080008 98c792b58000 98c7ae1649f0 
98c7ae164800
[  726.382841]  98c7ae1649f0 0001 98c792b57c60 
8b89a855
[  726.382843] Call Trace:
[  726.382845]  [] schedule+0x35/0x80
[  726.382858]  [] wait_current_trans.isra.21+0xd3/0x120 
[btrfs]
[  726.382859]  [] ? wake_atomic_t_function+0x60/0x60
[  726.382872]  [] start_transaction+0x272/0x4a0 [btrfs]
[  726.382885]  [] btrfs_join_transaction+0x17/0x20 [btrfs]
[  726.382899]  [] btrfs_finish_ordered_io+0x499/0x6c0 [btrfs]
[  726.382912]  [] finish_ordered_fn+0x15/0x20 [btrfs]
[  726.382926]  [] btrfs_scrubparity_helper+0xc8/0x2d0 [btrfs]
[  726.382941]  [] btrfs_endio_write_helper+0xe/0x10 [btrfs]
[  726.382942]  [] process_one_work+0x1fc/0x4b0
[  726.382944]  [] worker_thread+0x4b/0x500
[  726.382945]  [] ? process_one_work+0x4b0/0x4b0
[  726.382946]  [] ? process_one_work+0x4b0/0x4b0
[  726.382948]  [] kthread+0xd8/0xf0
[  726.382949]  [] ret_from_fork+0x1f/0x40
[  726.382951]  [] ? kthread_create_on_node+0x1e0/0x1e0

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

Title:
  Lage samba file transfers block btrfs to hung task

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  this bug occurs when user transfer big files ~1gb to the samba server
  on xenial/wily

  on wily this problem was NOT showing with samba 4.2 (i guess) until
  samba was also upgraded to 4.3.

  the samba runs on a KVM VM

  samba version: 4.3.9+dfsg-0ubuntu0.16.04.

  
  [   30.171211] zram: Added device: zram0
  [   30.356301] zram0: detected capacity change from 0 to 1518252032
  [   30.668855] Adding 1482664k swap on /dev/zram0.  Priority:5 extents:1 
across:1482664k SSFS
  [   35.608271] [drm:qxl_enc_commit [qxl]] *ERROR* head number too large or 
missing monitors config: c9e3, 0
  [   45.008364] Non-volatile memory driver v1.3
  [65636.820111] INFO: task btrfs-cleaner:631 blocked for more than 120 seconds.
  [65636.820128]   Not tainted 4.4.0-36-generic #55-Ubuntu
  [65636.820129] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [65636.820131] btrfs-cleaner   D 88005ae93ce8 0   631  2 
0x
  [65636.820137]  88005ae93ce8 8800bbb86400 8801b0dc3e80 
8801b0dc2580
  [65636.820139]  88005ae94000 8801851971f0 880185197000 
8801851971f0
  [65636.820141]  0001 88005ae93d00 81829ec5 
8801b7fc4000
  [65636.820143] Call Trace:
  [65636.820182]  [] schedule+0x35/0x80
  [65636.820360]  [] wait_current_trans.isra.21+0xd3/0x120 
[btrfs]
  [65636.820395]  [] ? wake_atomic_t_function+0x60/0x60
  [65636.820409]  [] start_transaction+0x2c5/0x4b0 [btrfs]
  [65636.820434]  [] btrfs_start_transaction+0x18/0x20 [btrfs]
  [65636.820452]  [] btrfs_drop_snapshot+0x7f/0x830 [btrfs]
  [65636.820454]  [] ? __schedule+0x3b6/0xa30
  [65636.820467]  [] 
btrfs_clean_one_deleted_snapshot+0xb2/0x100 [btrfs]
  [65636.820480]  [] cleaner_kthread+0xcf/0x220 [btrfs]
  [65636.820493]  [] ? check_leaf+0x360/0x360 [btrfs]
  [65636.820497]  [] kthread+0xd8/0xf0
  [65636.820499]  [] ? kthread_create_on_node+0x1e0/0x1e0
  [65636.820505]  [] ret_from_fork+0x3f/0x70
  [65636.820507]  [] ? kthread_create_on_node+0x1e0/0x1e0
  [65636.820550] INFO: task kworker/u4:1:7760 blocked for more than 120 seconds.
  [65636.820551]   Not tainted 4.4.0-36-generic #55-Ubuntu
  [65636.820558] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [65636.820559] kworker/u4:1D 880008433c48 0  7760  2 
0x
  [65636.820579] Workqueue: btrfs-endio-write btrfs_endio_write_helper [btrfs]
  [65636.820581]  880008433c48 0040 8800b9d98c80 
8801b51a9900
  [65636.820582]  880008434000 8801851941f0 880185194000 
8801851941f0
  [65636.820584]  0001 880008433c60 81829ec5 
8801b7fc4000
  [65636.820586] Call Trace:
  [65636.820588]  [] schedule+0x35/0x80
  [65636.820602]  [] wait_current_trans.isra.21+0xd3/0x120 
[btrfs]
  [65636.820604]  [] ? wake_atomic_t_function+0x60/0x60
  [65636.820620]  [] start_transaction+0x275/0x4b0 [btrfs]
  [65636.820650]  [] btrfs_join_transaction+0x17/0x20 [btrfs]
  [65636.820667]  [] btrfs_finish_ordered_io+0x435/0x650 
[btrfs]
  [65636.820692]  [] finish_ordered_fn+0x15/0x20 [btrfs]
  [65636.820718]

[Kernel-packages] [Bug 1640613] onza (i386) - tests ran: 1, failed: 0

tests ran:   1, failed: 0;
  
http://kernel.ubuntu.com/testing/3.19.0-75.83-generic/onza__3.19.0-75.83__2016-11-18_16-47-00/results-index.html

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

Title:
  linux: 3.19.0-75.83 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
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:
  In Progress
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:
  Fix Released
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Vivid:
  Confirmed

Bug description:
  This bug is for tracking the 3.19.0-75.83 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
  derivative-trackers-created: 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/1640613/+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 1640921] onibi (i386) - tests ran: 20, failed: 0

tests ran:  20, failed: 0;
  
http://kernel.ubuntu.com/testing/4.4.0-49.70-lowlatency/onibi__4.4.0-49.70__2016-11-18_15-19-00/results-index.html

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

Title:
  linux: 4.4.0-49.70 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
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:
  In Progress
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 4.4.0-49.70 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
  derivative-trackers-created: 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/1640921/+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 1594023] Re: Poweroff or reboot hangs. Laptop won't shutdown. 16.04

2016-11-18 Thread VinDSL

My biggest fear is that during one of these 'freezing' episodes my
Samsung 850 SSD will remount the root partition as read-only.  I've had
several HDDs go read-only, over the years, and it's a PITA to recover
from it, especially in RAID configs.

Somebody will to need to handle this situation upstream. Two likely
scenarios would be either a Linux kernel patch, and/or a firmware
upgrade from Samsung.  In the meantime, we're all sitting on ticking
time bombs.

I suppose it goes without saying, but make sure you're fully backed-up
!!!

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

Title:
  Poweroff or reboot hangs. Laptop won't shutdown. 16.04

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  This is about a fresh Ubuntu 16.04 install on a new laptop (asus
  x540sa). After pressing the shutdown button in the start menu; the
  shutdown procedure starts and in the final splash screen the system
  just hangs. Tried a second time by pressing Esc once the splash screen
  showed up and I saw that it reaches the line "Reached target shutdown"
  and just stops there, no matter how long I leave it there the machine
  won't turn off.

  I also tried a Kubuntu 16.04 fresh install on the same machine and it
  hanged too at the final splash screen where the pulsating logo
  stopped. Then I tried with Esc only to see the exact same line in the
  end.

  The issue seems to affect lately quite many users as shown by the
  google results of the past month / week or so.

  I have also tried shutting down from the console with shutdown -and
  all the parameters after that suggested online- and sudo poweroff but
  unfortunately they didn't do the trick. The exact same situation
  occurred.

  Unmounting the swap as suggested online doesn't work.

  Also rebooting the system is not working either due to the same issue.

  So right now the only way for me to poweroff the machine is to press
  the power button on the keyboard continuously.

  Reproducible: Always

  Steps to Reproduce:
  1.Install OS
  2.Do something, anything or nothing
  3.Try to shutdown or reboot

  Actual Results:
  The computer is not shutting down: "Reached target shutdown" and hangs there.

  Expected Results:
  Powering off the machine.

  For what it's worth, closing the lid won't suspend the system, but
  using the menu buttons for suspension will do it.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1594023/+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 1640613] onza (amd64) - tests ran: 1, failed: 0

tests ran:   1, failed: 0;
  
http://kernel.ubuntu.com/testing/3.19.0-75.83-generic/onza__3.19.0-75.83__2016-11-18_16-24-00/results-index.html

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

Title:
  linux: 3.19.0-75.83 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
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:
  In Progress
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:
  Fix Released
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Vivid:
  Confirmed

Bug description:
  This bug is for tracking the 3.19.0-75.83 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
  derivative-trackers-created: 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/1640613/+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 1632466] htxerr

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

Default Comment by Bridge

** Attachment added: "htxerr"
   https://bugs.launchpad.net/bugs/1632466/+attachment/4779372/+files/htxerr

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

Title:
  STC860:Tuleta-L:KVM:iap03:HTX logs miscompares on multiple adapters on
  ubuntu 16.04 guest.

Status in linux package in Ubuntu:
  New

Bug description:
  == Comment: #0 - Application Cdeadmin  -
  2016-07-26 11:20:20 ==

  
  == Comment: #1 - Application Cdeadmin  - 2016-07-26 
11:20:22 ==
   State: Open by: panico on 25 July 2016 18:02:09 

  Contact Information:
  
  Defect Originator:  Michael Panico
  Defect Originator   pan...@us.ibm.com

  Backup: Deepti Umarani
  Backup ST ID: Deepti S Umarani/India/IBM

  System Info:
  
  Machine Type:8284-22A
  Card Type:...FSP2_P8LE
  Current Boot Side:...T
  Next Boot Side:..T
  PT_Swap:.1
  Current Side Driver:.fips860/b0713a_1630.860 

  Ubuntu KVM Host:
  root@iaos1:/tmp# uname -a
  Linux iaos1 4.4.0-30-generic #49-Ubuntu SMP Fri Jul 1 10:00:36 UTC 2016 
ppc64le ppc64le ppc64le GNU/Linux
  root@iaos1:/tmp# lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu Yakkety Yak (development branch)
  Release:  16.10
  Codename: yakkety

  Ubuntu Guest:
  [htx@iap03]  [1m/usr/lpp/htx/bin# [0m uname -a
  Linux iap03 4.4.0-31-generic #50-Ubuntu SMP Wed Jul 13 00:05:18 UTC 2016 
ppc64le ppc64le ppc64le GNU/Linux
  [htx@iap03]  [1m/usr/lpp/htx/bin# [0m lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 16.04.1 LTS
  Release:  16.04
  Codename: xenial

  HTX level on ubuntu 16.04 guest:
  [htx@iap03]  [1m/usr/lpp/htx/bin# [0m dpkg -l | grep htxubuntu
  ii  htxubuntu  402 ppc64el

  Problem Description:
  
  Running networks (via bridging) on three different guests (other linux, 
ubuntu 16.10 and ubuntu 16.04) the ubuntu 16.04 guest logged a miscompare on 
the austin adapter and the shinerT adapter.  The shinerT ran for 24 hours and 
the austin for 72 hours before logging miscompares.

  From /tmp/htxerr:
  [htx@iap03]  [1m/usr/lpp/htx/bin# [0m cat /tmp/htxerr

  /dev/enp0s6   Jul 23 14:29:00 2016 err=00e3 sev=4 hxecom
  R(102.1.2.20.50854) connected to W(102.1.1.20.39073)
  Miscompare with packet 0, data size = 51062. miscompare_count=0 pakLen = 
51082 
  Miscompare at displacement (decimal) = 23876 
  wbuf = 
  rbuf = 

  For stanza 0, TCP connection, bufmin=3, bufmax=65000, bufinc=10531
  Consecutive prior good reads= 70739865,  good bytes read= 2868570843930

  /dev/enp0s6   Jul 23 14:29:00 2016 err=00d8 sev=4 hxecom
  Shutting down testing due to error flag - 1
  R(102.1.2.20.50854) connected to W(102.1.1.20.39073)
  For stanza 0, TCP connection, bufmin=3, bufmax=65000, bufinc=10531
  Consecutive prior good reads=0,  good bytes read= 0

  /dev/enp0s7   Jul 23 14:29:00 2016 err=00fb0068 sev=1 hxecom
  W(102.1.1.20.39073) connected to R(102.1.2.20.50854)
  Wrote 878 characters, expected 963
  Write failed - Connection reset by peer.
  For stanza 1, TCP connection,  bufmin=3, bufmax=2869, bufinc=94
  Consecutive prior good writes= 25459432,  good bytes written=   
35283290616

  htx_messages  Jul 23 14:29:01 2016 err= sev=1 hxssup
  hxecom HE program for enp0s6 terminated by exit(0) call.

  htx_messages  Jul 23 16:29:07 2016 err= sev=4 hang_monitor  
  hxecom for enp0s7 is HUNG!
  Max run time (set in mdt) = 7200 seconds.
  Current elasped time = 7206 seconds.

  htx_messages  Jul 23 18:29:07 2016 err= sev=4 hang_monitor  
  hxecom for enp0s7 is HUNG!
  Max run time (set in mdt) = 7200 seconds.
  Current elasped time = 14406 seconds.

  htx_messages  Jul 23 20:29:07 2016 err= sev=4 hang_monitor  
  hxecom for enp0s7 is HUNG!
  Max run time (set in mdt) = 7200 seconds.
  Current elasped time = 21606 seconds.

  htx_messages  Jul 23 22:29:08 2016 err= sev=4 hang_monitor  
  hxecom for enp0s7 is HUNG!
  Max run time (set in mdt) = 7200 seconds.
  Current elasped time = 28807 seconds.

  htx_messages  Jul 24 00:29:08 2016 err= sev=4 hang_monitor  
  hxecom for enp0s7 is HUNG!
  Max run time (set in mdt) = 7200 seconds.
  Current elasped time = 36007 seconds.

  /dev/enp0s4   Jul 25 04:56:13 2016 err=00e3 sev=4 hxecom
  R(103.1.2.20.36665) connected to W(103.1.1.20.40459)
  Miscompare with packet 0, data

[Kernel-packages] [Bug 1632466] pKVM3.1.1 config file.

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

Default Comment by Bridge

** Attachment added: "pKVM3.1.1 config file."
   
https://bugs.launchpad.net/bugs/1632466/+attachment/4779380/+files/.config.pkvm

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

Title:
  STC860:Tuleta-L:KVM:iap03:HTX logs miscompares on multiple adapters on
  ubuntu 16.04 guest.

Status in linux package in Ubuntu:
  New

Bug description:
  == Comment: #0 - Application Cdeadmin  -
  2016-07-26 11:20:20 ==

  
  == Comment: #1 - Application Cdeadmin  - 2016-07-26 
11:20:22 ==
   State: Open by: panico on 25 July 2016 18:02:09 

  Contact Information:
  
  Defect Originator:  Michael Panico
  Defect Originator   pan...@us.ibm.com

  Backup: Deepti Umarani
  Backup ST ID: Deepti S Umarani/India/IBM

  System Info:
  
  Machine Type:8284-22A
  Card Type:...FSP2_P8LE
  Current Boot Side:...T
  Next Boot Side:..T
  PT_Swap:.1
  Current Side Driver:.fips860/b0713a_1630.860 

  Ubuntu KVM Host:
  root@iaos1:/tmp# uname -a
  Linux iaos1 4.4.0-30-generic #49-Ubuntu SMP Fri Jul 1 10:00:36 UTC 2016 
ppc64le ppc64le ppc64le GNU/Linux
  root@iaos1:/tmp# lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu Yakkety Yak (development branch)
  Release:  16.10
  Codename: yakkety

  Ubuntu Guest:
  [htx@iap03]  [1m/usr/lpp/htx/bin# [0m uname -a
  Linux iap03 4.4.0-31-generic #50-Ubuntu SMP Wed Jul 13 00:05:18 UTC 2016 
ppc64le ppc64le ppc64le GNU/Linux
  [htx@iap03]  [1m/usr/lpp/htx/bin# [0m lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 16.04.1 LTS
  Release:  16.04
  Codename: xenial

  HTX level on ubuntu 16.04 guest:
  [htx@iap03]  [1m/usr/lpp/htx/bin# [0m dpkg -l | grep htxubuntu
  ii  htxubuntu  402 ppc64el

  Problem Description:
  
  Running networks (via bridging) on three different guests (other linux, 
ubuntu 16.10 and ubuntu 16.04) the ubuntu 16.04 guest logged a miscompare on 
the austin adapter and the shinerT adapter.  The shinerT ran for 24 hours and 
the austin for 72 hours before logging miscompares.

  From /tmp/htxerr:
  [htx@iap03]  [1m/usr/lpp/htx/bin# [0m cat /tmp/htxerr

  /dev/enp0s6   Jul 23 14:29:00 2016 err=00e3 sev=4 hxecom
  R(102.1.2.20.50854) connected to W(102.1.1.20.39073)
  Miscompare with packet 0, data size = 51062. miscompare_count=0 pakLen = 
51082 
  Miscompare at displacement (decimal) = 23876 
  wbuf = 
  rbuf = 

  For stanza 0, TCP connection, bufmin=3, bufmax=65000, bufinc=10531
  Consecutive prior good reads= 70739865,  good bytes read= 2868570843930

  /dev/enp0s6   Jul 23 14:29:00 2016 err=00d8 sev=4 hxecom
  Shutting down testing due to error flag - 1
  R(102.1.2.20.50854) connected to W(102.1.1.20.39073)
  For stanza 0, TCP connection, bufmin=3, bufmax=65000, bufinc=10531
  Consecutive prior good reads=0,  good bytes read= 0

  /dev/enp0s7   Jul 23 14:29:00 2016 err=00fb0068 sev=1 hxecom
  W(102.1.1.20.39073) connected to R(102.1.2.20.50854)
  Wrote 878 characters, expected 963
  Write failed - Connection reset by peer.
  For stanza 1, TCP connection,  bufmin=3, bufmax=2869, bufinc=94
  Consecutive prior good writes= 25459432,  good bytes written=   
35283290616

  htx_messages  Jul 23 14:29:01 2016 err= sev=1 hxssup
  hxecom HE program for enp0s6 terminated by exit(0) call.

  htx_messages  Jul 23 16:29:07 2016 err= sev=4 hang_monitor  
  hxecom for enp0s7 is HUNG!
  Max run time (set in mdt) = 7200 seconds.
  Current elasped time = 7206 seconds.

  htx_messages  Jul 23 18:29:07 2016 err= sev=4 hang_monitor  
  hxecom for enp0s7 is HUNG!
  Max run time (set in mdt) = 7200 seconds.
  Current elasped time = 14406 seconds.

  htx_messages  Jul 23 20:29:07 2016 err= sev=4 hang_monitor  
  hxecom for enp0s7 is HUNG!
  Max run time (set in mdt) = 7200 seconds.
  Current elasped time = 21606 seconds.

  htx_messages  Jul 23 22:29:08 2016 err= sev=4 hang_monitor  
  hxecom for enp0s7 is HUNG!
  Max run time (set in mdt) = 7200 seconds.
  Current elasped time = 28807 seconds.

  htx_messages  Jul 24 00:29:08 2016 err= sev=4 hang_monitor  
  hxecom for enp0s7 is HUNG!
  Max run time (set in mdt) = 7200 seconds.
  Current elasped time = 36007 seconds.

  /dev/enp0s4   Jul 25 04:56:13 2016 err=00e3 sev=4 hxecom
  R(103.1.2.20.36665) connected to W(103.1.1.20.40459)
  Miscompare

[Kernel-packages] [Bug 1632466] DebugPatternFormat

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

Default Comment by Bridge

** Attachment added: "DebugPatternFormat"
   
https://bugs.launchpad.net/bugs/1632466/+attachment/4779378/+files/DebugPatternFormat.jpg

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

Title:
  STC860:Tuleta-L:KVM:iap03:HTX logs miscompares on multiple adapters on
  ubuntu 16.04 guest.

Status in linux package in Ubuntu:
  New

Bug description:
  == Comment: #0 - Application Cdeadmin  -
  2016-07-26 11:20:20 ==

  
  == Comment: #1 - Application Cdeadmin  - 2016-07-26 
11:20:22 ==
   State: Open by: panico on 25 July 2016 18:02:09 

  Contact Information:
  
  Defect Originator:  Michael Panico
  Defect Originator   pan...@us.ibm.com

  Backup: Deepti Umarani
  Backup ST ID: Deepti S Umarani/India/IBM

  System Info:
  
  Machine Type:8284-22A
  Card Type:...FSP2_P8LE
  Current Boot Side:...T
  Next Boot Side:..T
  PT_Swap:.1
  Current Side Driver:.fips860/b0713a_1630.860 

  Ubuntu KVM Host:
  root@iaos1:/tmp# uname -a
  Linux iaos1 4.4.0-30-generic #49-Ubuntu SMP Fri Jul 1 10:00:36 UTC 2016 
ppc64le ppc64le ppc64le GNU/Linux
  root@iaos1:/tmp# lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu Yakkety Yak (development branch)
  Release:  16.10
  Codename: yakkety

  Ubuntu Guest:
  [htx@iap03]  [1m/usr/lpp/htx/bin# [0m uname -a
  Linux iap03 4.4.0-31-generic #50-Ubuntu SMP Wed Jul 13 00:05:18 UTC 2016 
ppc64le ppc64le ppc64le GNU/Linux
  [htx@iap03]  [1m/usr/lpp/htx/bin# [0m lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 16.04.1 LTS
  Release:  16.04
  Codename: xenial

  HTX level on ubuntu 16.04 guest:
  [htx@iap03]  [1m/usr/lpp/htx/bin# [0m dpkg -l | grep htxubuntu
  ii  htxubuntu  402 ppc64el

  Problem Description:
  
  Running networks (via bridging) on three different guests (other linux, 
ubuntu 16.10 and ubuntu 16.04) the ubuntu 16.04 guest logged a miscompare on 
the austin adapter and the shinerT adapter.  The shinerT ran for 24 hours and 
the austin for 72 hours before logging miscompares.

  From /tmp/htxerr:
  [htx@iap03]  [1m/usr/lpp/htx/bin# [0m cat /tmp/htxerr

  /dev/enp0s6   Jul 23 14:29:00 2016 err=00e3 sev=4 hxecom
  R(102.1.2.20.50854) connected to W(102.1.1.20.39073)
  Miscompare with packet 0, data size = 51062. miscompare_count=0 pakLen = 
51082 
  Miscompare at displacement (decimal) = 23876 
  wbuf = 
  rbuf = 

  For stanza 0, TCP connection, bufmin=3, bufmax=65000, bufinc=10531
  Consecutive prior good reads= 70739865,  good bytes read= 2868570843930

  /dev/enp0s6   Jul 23 14:29:00 2016 err=00d8 sev=4 hxecom
  Shutting down testing due to error flag - 1
  R(102.1.2.20.50854) connected to W(102.1.1.20.39073)
  For stanza 0, TCP connection, bufmin=3, bufmax=65000, bufinc=10531
  Consecutive prior good reads=0,  good bytes read= 0

  /dev/enp0s7   Jul 23 14:29:00 2016 err=00fb0068 sev=1 hxecom
  W(102.1.1.20.39073) connected to R(102.1.2.20.50854)
  Wrote 878 characters, expected 963
  Write failed - Connection reset by peer.
  For stanza 1, TCP connection,  bufmin=3, bufmax=2869, bufinc=94
  Consecutive prior good writes= 25459432,  good bytes written=   
35283290616

  htx_messages  Jul 23 14:29:01 2016 err= sev=1 hxssup
  hxecom HE program for enp0s6 terminated by exit(0) call.

  htx_messages  Jul 23 16:29:07 2016 err= sev=4 hang_monitor  
  hxecom for enp0s7 is HUNG!
  Max run time (set in mdt) = 7200 seconds.
  Current elasped time = 7206 seconds.

  htx_messages  Jul 23 18:29:07 2016 err= sev=4 hang_monitor  
  hxecom for enp0s7 is HUNG!
  Max run time (set in mdt) = 7200 seconds.
  Current elasped time = 14406 seconds.

  htx_messages  Jul 23 20:29:07 2016 err= sev=4 hang_monitor  
  hxecom for enp0s7 is HUNG!
  Max run time (set in mdt) = 7200 seconds.
  Current elasped time = 21606 seconds.

  htx_messages  Jul 23 22:29:08 2016 err= sev=4 hang_monitor  
  hxecom for enp0s7 is HUNG!
  Max run time (set in mdt) = 7200 seconds.
  Current elasped time = 28807 seconds.

  htx_messages  Jul 24 00:29:08 2016 err= sev=4 hang_monitor  
  hxecom for enp0s7 is HUNG!
  Max run time (set in mdt) = 7200 seconds.
  Current elasped time = 36007 seconds.

  /dev/enp0s4   Jul 25 04:56:13 2016 err=00e3 sev=4 hxecom
  R(103.1.2.20.36665) connected to W(103.1.1.20.40459)

[Kernel-packages] [Bug 1632466] header_tailer_format

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

Default Comment by Bridge

** Attachment added: "header_tailer_format"
   
https://bugs.launchpad.net/bugs/1632466/+attachment/4779377/+files/header_trailer_format.jpg

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

Title:
  STC860:Tuleta-L:KVM:iap03:HTX logs miscompares on multiple adapters on
  ubuntu 16.04 guest.

Status in linux package in Ubuntu:
  New

Bug description:
  == Comment: #0 - Application Cdeadmin  -
  2016-07-26 11:20:20 ==

  
  == Comment: #1 - Application Cdeadmin  - 2016-07-26 
11:20:22 ==
   State: Open by: panico on 25 July 2016 18:02:09 

  Contact Information:
  
  Defect Originator:  Michael Panico
  Defect Originator   pan...@us.ibm.com

  Backup: Deepti Umarani
  Backup ST ID: Deepti S Umarani/India/IBM

  System Info:
  
  Machine Type:8284-22A
  Card Type:...FSP2_P8LE
  Current Boot Side:...T
  Next Boot Side:..T
  PT_Swap:.1
  Current Side Driver:.fips860/b0713a_1630.860 

  Ubuntu KVM Host:
  root@iaos1:/tmp# uname -a
  Linux iaos1 4.4.0-30-generic #49-Ubuntu SMP Fri Jul 1 10:00:36 UTC 2016 
ppc64le ppc64le ppc64le GNU/Linux
  root@iaos1:/tmp# lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu Yakkety Yak (development branch)
  Release:  16.10
  Codename: yakkety

  Ubuntu Guest:
  [htx@iap03]  [1m/usr/lpp/htx/bin# [0m uname -a
  Linux iap03 4.4.0-31-generic #50-Ubuntu SMP Wed Jul 13 00:05:18 UTC 2016 
ppc64le ppc64le ppc64le GNU/Linux
  [htx@iap03]  [1m/usr/lpp/htx/bin# [0m lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 16.04.1 LTS
  Release:  16.04
  Codename: xenial

  HTX level on ubuntu 16.04 guest:
  [htx@iap03]  [1m/usr/lpp/htx/bin# [0m dpkg -l | grep htxubuntu
  ii  htxubuntu  402 ppc64el

  Problem Description:
  
  Running networks (via bridging) on three different guests (other linux, 
ubuntu 16.10 and ubuntu 16.04) the ubuntu 16.04 guest logged a miscompare on 
the austin adapter and the shinerT adapter.  The shinerT ran for 24 hours and 
the austin for 72 hours before logging miscompares.

  From /tmp/htxerr:
  [htx@iap03]  [1m/usr/lpp/htx/bin# [0m cat /tmp/htxerr

  /dev/enp0s6   Jul 23 14:29:00 2016 err=00e3 sev=4 hxecom
  R(102.1.2.20.50854) connected to W(102.1.1.20.39073)
  Miscompare with packet 0, data size = 51062. miscompare_count=0 pakLen = 
51082 
  Miscompare at displacement (decimal) = 23876 
  wbuf = 
  rbuf = 

  For stanza 0, TCP connection, bufmin=3, bufmax=65000, bufinc=10531
  Consecutive prior good reads= 70739865,  good bytes read= 2868570843930

  /dev/enp0s6   Jul 23 14:29:00 2016 err=00d8 sev=4 hxecom
  Shutting down testing due to error flag - 1
  R(102.1.2.20.50854) connected to W(102.1.1.20.39073)
  For stanza 0, TCP connection, bufmin=3, bufmax=65000, bufinc=10531
  Consecutive prior good reads=0,  good bytes read= 0

  /dev/enp0s7   Jul 23 14:29:00 2016 err=00fb0068 sev=1 hxecom
  W(102.1.1.20.39073) connected to R(102.1.2.20.50854)
  Wrote 878 characters, expected 963
  Write failed - Connection reset by peer.
  For stanza 1, TCP connection,  bufmin=3, bufmax=2869, bufinc=94
  Consecutive prior good writes= 25459432,  good bytes written=   
35283290616

  htx_messages  Jul 23 14:29:01 2016 err= sev=1 hxssup
  hxecom HE program for enp0s6 terminated by exit(0) call.

  htx_messages  Jul 23 16:29:07 2016 err= sev=4 hang_monitor  
  hxecom for enp0s7 is HUNG!
  Max run time (set in mdt) = 7200 seconds.
  Current elasped time = 7206 seconds.

  htx_messages  Jul 23 18:29:07 2016 err= sev=4 hang_monitor  
  hxecom for enp0s7 is HUNG!
  Max run time (set in mdt) = 7200 seconds.
  Current elasped time = 14406 seconds.

  htx_messages  Jul 23 20:29:07 2016 err= sev=4 hang_monitor  
  hxecom for enp0s7 is HUNG!
  Max run time (set in mdt) = 7200 seconds.
  Current elasped time = 21606 seconds.

  htx_messages  Jul 23 22:29:08 2016 err= sev=4 hang_monitor  
  hxecom for enp0s7 is HUNG!
  Max run time (set in mdt) = 7200 seconds.
  Current elasped time = 28807 seconds.

  htx_messages  Jul 24 00:29:08 2016 err= sev=4 hang_monitor  
  hxecom for enp0s7 is HUNG!
  Max run time (set in mdt) = 7200 seconds.
  Current elasped time = 36007 seconds.

  /dev/enp0s4   Jul 25 04:56:13 2016 err=00e3 sev=4 hxecom
  R(103.1.2.20.36665) connected to W(103.1.1.20.40459)

[Kernel-packages] [Bug 1632466] PacketFormat

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

Default Comment by Bridge

** Attachment added: "PacketFormat"
   
https://bugs.launchpad.net/bugs/1632466/+attachment/4779376/+files/PacketFormat.jpg

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

Title:
  STC860:Tuleta-L:KVM:iap03:HTX logs miscompares on multiple adapters on
  ubuntu 16.04 guest.

Status in linux package in Ubuntu:
  New

Bug description:
  == Comment: #0 - Application Cdeadmin  -
  2016-07-26 11:20:20 ==

  
  == Comment: #1 - Application Cdeadmin  - 2016-07-26 
11:20:22 ==
   State: Open by: panico on 25 July 2016 18:02:09 

  Contact Information:
  
  Defect Originator:  Michael Panico
  Defect Originator   pan...@us.ibm.com

  Backup: Deepti Umarani
  Backup ST ID: Deepti S Umarani/India/IBM

  System Info:
  
  Machine Type:8284-22A
  Card Type:...FSP2_P8LE
  Current Boot Side:...T
  Next Boot Side:..T
  PT_Swap:.1
  Current Side Driver:.fips860/b0713a_1630.860 

  Ubuntu KVM Host:
  root@iaos1:/tmp# uname -a
  Linux iaos1 4.4.0-30-generic #49-Ubuntu SMP Fri Jul 1 10:00:36 UTC 2016 
ppc64le ppc64le ppc64le GNU/Linux
  root@iaos1:/tmp# lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu Yakkety Yak (development branch)
  Release:  16.10
  Codename: yakkety

  Ubuntu Guest:
  [htx@iap03]  [1m/usr/lpp/htx/bin# [0m uname -a
  Linux iap03 4.4.0-31-generic #50-Ubuntu SMP Wed Jul 13 00:05:18 UTC 2016 
ppc64le ppc64le ppc64le GNU/Linux
  [htx@iap03]  [1m/usr/lpp/htx/bin# [0m lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 16.04.1 LTS
  Release:  16.04
  Codename: xenial

  HTX level on ubuntu 16.04 guest:
  [htx@iap03]  [1m/usr/lpp/htx/bin# [0m dpkg -l | grep htxubuntu
  ii  htxubuntu  402 ppc64el

  Problem Description:
  
  Running networks (via bridging) on three different guests (other linux, 
ubuntu 16.10 and ubuntu 16.04) the ubuntu 16.04 guest logged a miscompare on 
the austin adapter and the shinerT adapter.  The shinerT ran for 24 hours and 
the austin for 72 hours before logging miscompares.

  From /tmp/htxerr:
  [htx@iap03]  [1m/usr/lpp/htx/bin# [0m cat /tmp/htxerr

  /dev/enp0s6   Jul 23 14:29:00 2016 err=00e3 sev=4 hxecom
  R(102.1.2.20.50854) connected to W(102.1.1.20.39073)
  Miscompare with packet 0, data size = 51062. miscompare_count=0 pakLen = 
51082 
  Miscompare at displacement (decimal) = 23876 
  wbuf = 
  rbuf = 

  For stanza 0, TCP connection, bufmin=3, bufmax=65000, bufinc=10531
  Consecutive prior good reads= 70739865,  good bytes read= 2868570843930

  /dev/enp0s6   Jul 23 14:29:00 2016 err=00d8 sev=4 hxecom
  Shutting down testing due to error flag - 1
  R(102.1.2.20.50854) connected to W(102.1.1.20.39073)
  For stanza 0, TCP connection, bufmin=3, bufmax=65000, bufinc=10531
  Consecutive prior good reads=0,  good bytes read= 0

  /dev/enp0s7   Jul 23 14:29:00 2016 err=00fb0068 sev=1 hxecom
  W(102.1.1.20.39073) connected to R(102.1.2.20.50854)
  Wrote 878 characters, expected 963
  Write failed - Connection reset by peer.
  For stanza 1, TCP connection,  bufmin=3, bufmax=2869, bufinc=94
  Consecutive prior good writes= 25459432,  good bytes written=   
35283290616

  htx_messages  Jul 23 14:29:01 2016 err= sev=1 hxssup
  hxecom HE program for enp0s6 terminated by exit(0) call.

  htx_messages  Jul 23 16:29:07 2016 err= sev=4 hang_monitor  
  hxecom for enp0s7 is HUNG!
  Max run time (set in mdt) = 7200 seconds.
  Current elasped time = 7206 seconds.

  htx_messages  Jul 23 18:29:07 2016 err= sev=4 hang_monitor  
  hxecom for enp0s7 is HUNG!
  Max run time (set in mdt) = 7200 seconds.
  Current elasped time = 14406 seconds.

  htx_messages  Jul 23 20:29:07 2016 err= sev=4 hang_monitor  
  hxecom for enp0s7 is HUNG!
  Max run time (set in mdt) = 7200 seconds.
  Current elasped time = 21606 seconds.

  htx_messages  Jul 23 22:29:08 2016 err= sev=4 hang_monitor  
  hxecom for enp0s7 is HUNG!
  Max run time (set in mdt) = 7200 seconds.
  Current elasped time = 28807 seconds.

  htx_messages  Jul 24 00:29:08 2016 err= sev=4 hang_monitor  
  hxecom for enp0s7 is HUNG!
  Max run time (set in mdt) = 7200 seconds.
  Current elasped time = 36007 seconds.

  /dev/enp0s4   Jul 25 04:56:13 2016 err=00e3 sev=4 hxecom
  R(103.1.2.20.36665) connected to W(103.1.1.20.40459)
  Miscompare with

[Kernel-packages] [Bug 1632466] Ubuntu 16.04 level 4.4.0-31-generic config file

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

Default Comment by Bridge

** Attachment added: "Ubuntu 16.04 level 4.4.0-31-generic config file"
   
https://bugs.launchpad.net/bugs/1632466/+attachment/4779381/+files/config-4.4.0-31-generic

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

Title:
  STC860:Tuleta-L:KVM:iap03:HTX logs miscompares on multiple adapters on
  ubuntu 16.04 guest.

Status in linux package in Ubuntu:
  New

Bug description:
  == Comment: #0 - Application Cdeadmin  -
  2016-07-26 11:20:20 ==

  
  == Comment: #1 - Application Cdeadmin  - 2016-07-26 
11:20:22 ==
   State: Open by: panico on 25 July 2016 18:02:09 

  Contact Information:
  
  Defect Originator:  Michael Panico
  Defect Originator   pan...@us.ibm.com

  Backup: Deepti Umarani
  Backup ST ID: Deepti S Umarani/India/IBM

  System Info:
  
  Machine Type:8284-22A
  Card Type:...FSP2_P8LE
  Current Boot Side:...T
  Next Boot Side:..T
  PT_Swap:.1
  Current Side Driver:.fips860/b0713a_1630.860 

  Ubuntu KVM Host:
  root@iaos1:/tmp# uname -a
  Linux iaos1 4.4.0-30-generic #49-Ubuntu SMP Fri Jul 1 10:00:36 UTC 2016 
ppc64le ppc64le ppc64le GNU/Linux
  root@iaos1:/tmp# lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu Yakkety Yak (development branch)
  Release:  16.10
  Codename: yakkety

  Ubuntu Guest:
  [htx@iap03]  [1m/usr/lpp/htx/bin# [0m uname -a
  Linux iap03 4.4.0-31-generic #50-Ubuntu SMP Wed Jul 13 00:05:18 UTC 2016 
ppc64le ppc64le ppc64le GNU/Linux
  [htx@iap03]  [1m/usr/lpp/htx/bin# [0m lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 16.04.1 LTS
  Release:  16.04
  Codename: xenial

  HTX level on ubuntu 16.04 guest:
  [htx@iap03]  [1m/usr/lpp/htx/bin# [0m dpkg -l | grep htxubuntu
  ii  htxubuntu  402 ppc64el

  Problem Description:
  
  Running networks (via bridging) on three different guests (other linux, 
ubuntu 16.10 and ubuntu 16.04) the ubuntu 16.04 guest logged a miscompare on 
the austin adapter and the shinerT adapter.  The shinerT ran for 24 hours and 
the austin for 72 hours before logging miscompares.

  From /tmp/htxerr:
  [htx@iap03]  [1m/usr/lpp/htx/bin# [0m cat /tmp/htxerr

  /dev/enp0s6   Jul 23 14:29:00 2016 err=00e3 sev=4 hxecom
  R(102.1.2.20.50854) connected to W(102.1.1.20.39073)
  Miscompare with packet 0, data size = 51062. miscompare_count=0 pakLen = 
51082 
  Miscompare at displacement (decimal) = 23876 
  wbuf = 
  rbuf = 

  For stanza 0, TCP connection, bufmin=3, bufmax=65000, bufinc=10531
  Consecutive prior good reads= 70739865,  good bytes read= 2868570843930

  /dev/enp0s6   Jul 23 14:29:00 2016 err=00d8 sev=4 hxecom
  Shutting down testing due to error flag - 1
  R(102.1.2.20.50854) connected to W(102.1.1.20.39073)
  For stanza 0, TCP connection, bufmin=3, bufmax=65000, bufinc=10531
  Consecutive prior good reads=0,  good bytes read= 0

  /dev/enp0s7   Jul 23 14:29:00 2016 err=00fb0068 sev=1 hxecom
  W(102.1.1.20.39073) connected to R(102.1.2.20.50854)
  Wrote 878 characters, expected 963
  Write failed - Connection reset by peer.
  For stanza 1, TCP connection,  bufmin=3, bufmax=2869, bufinc=94
  Consecutive prior good writes= 25459432,  good bytes written=   
35283290616

  htx_messages  Jul 23 14:29:01 2016 err= sev=1 hxssup
  hxecom HE program for enp0s6 terminated by exit(0) call.

  htx_messages  Jul 23 16:29:07 2016 err= sev=4 hang_monitor  
  hxecom for enp0s7 is HUNG!
  Max run time (set in mdt) = 7200 seconds.
  Current elasped time = 7206 seconds.

  htx_messages  Jul 23 18:29:07 2016 err= sev=4 hang_monitor  
  hxecom for enp0s7 is HUNG!
  Max run time (set in mdt) = 7200 seconds.
  Current elasped time = 14406 seconds.

  htx_messages  Jul 23 20:29:07 2016 err= sev=4 hang_monitor  
  hxecom for enp0s7 is HUNG!
  Max run time (set in mdt) = 7200 seconds.
  Current elasped time = 21606 seconds.

  htx_messages  Jul 23 22:29:08 2016 err= sev=4 hang_monitor  
  hxecom for enp0s7 is HUNG!
  Max run time (set in mdt) = 7200 seconds.
  Current elasped time = 28807 seconds.

  htx_messages  Jul 24 00:29:08 2016 err= sev=4 hang_monitor  
  hxecom for enp0s7 is HUNG!
  Max run time (set in mdt) = 7200 seconds.
  Current elasped time = 36007 seconds.

  /dev/enp0s4   Jul 25 04:56:13 2016 err=00e3 sev=4 hxecom
  R(103.1.2.20.36665) connected

[Kernel-packages] [Bug 1632466] Possible memory barrier issue fix

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

Default Comment by Bridge

** Attachment added: "Possible memory barrier issue fix"
   
https://bugs.launchpad.net/bugs/1632466/+attachment/4779379/+files/%5Bv2%5D%5BPATCH%5D_Fix_a_race_between_try_to_wake_up%28%29_and_a_woken_up_task.eml

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

Title:
  STC860:Tuleta-L:KVM:iap03:HTX logs miscompares on multiple adapters on
  ubuntu 16.04 guest.

Status in linux package in Ubuntu:
  New

Bug description:
  == Comment: #0 - Application Cdeadmin  -
  2016-07-26 11:20:20 ==

  
  == Comment: #1 - Application Cdeadmin  - 2016-07-26 
11:20:22 ==
   State: Open by: panico on 25 July 2016 18:02:09 

  Contact Information:
  
  Defect Originator:  Michael Panico
  Defect Originator   pan...@us.ibm.com

  Backup: Deepti Umarani
  Backup ST ID: Deepti S Umarani/India/IBM

  System Info:
  
  Machine Type:8284-22A
  Card Type:...FSP2_P8LE
  Current Boot Side:...T
  Next Boot Side:..T
  PT_Swap:.1
  Current Side Driver:.fips860/b0713a_1630.860 

  Ubuntu KVM Host:
  root@iaos1:/tmp# uname -a
  Linux iaos1 4.4.0-30-generic #49-Ubuntu SMP Fri Jul 1 10:00:36 UTC 2016 
ppc64le ppc64le ppc64le GNU/Linux
  root@iaos1:/tmp# lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu Yakkety Yak (development branch)
  Release:  16.10
  Codename: yakkety

  Ubuntu Guest:
  [htx@iap03]  [1m/usr/lpp/htx/bin# [0m uname -a
  Linux iap03 4.4.0-31-generic #50-Ubuntu SMP Wed Jul 13 00:05:18 UTC 2016 
ppc64le ppc64le ppc64le GNU/Linux
  [htx@iap03]  [1m/usr/lpp/htx/bin# [0m lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 16.04.1 LTS
  Release:  16.04
  Codename: xenial

  HTX level on ubuntu 16.04 guest:
  [htx@iap03]  [1m/usr/lpp/htx/bin# [0m dpkg -l | grep htxubuntu
  ii  htxubuntu  402 ppc64el

  Problem Description:
  
  Running networks (via bridging) on three different guests (other linux, 
ubuntu 16.10 and ubuntu 16.04) the ubuntu 16.04 guest logged a miscompare on 
the austin adapter and the shinerT adapter.  The shinerT ran for 24 hours and 
the austin for 72 hours before logging miscompares.

  From /tmp/htxerr:
  [htx@iap03]  [1m/usr/lpp/htx/bin# [0m cat /tmp/htxerr

  /dev/enp0s6   Jul 23 14:29:00 2016 err=00e3 sev=4 hxecom
  R(102.1.2.20.50854) connected to W(102.1.1.20.39073)
  Miscompare with packet 0, data size = 51062. miscompare_count=0 pakLen = 
51082 
  Miscompare at displacement (decimal) = 23876 
  wbuf = 
  rbuf = 

  For stanza 0, TCP connection, bufmin=3, bufmax=65000, bufinc=10531
  Consecutive prior good reads= 70739865,  good bytes read= 2868570843930

  /dev/enp0s6   Jul 23 14:29:00 2016 err=00d8 sev=4 hxecom
  Shutting down testing due to error flag - 1
  R(102.1.2.20.50854) connected to W(102.1.1.20.39073)
  For stanza 0, TCP connection, bufmin=3, bufmax=65000, bufinc=10531
  Consecutive prior good reads=0,  good bytes read= 0

  /dev/enp0s7   Jul 23 14:29:00 2016 err=00fb0068 sev=1 hxecom
  W(102.1.1.20.39073) connected to R(102.1.2.20.50854)
  Wrote 878 characters, expected 963
  Write failed - Connection reset by peer.
  For stanza 1, TCP connection,  bufmin=3, bufmax=2869, bufinc=94
  Consecutive prior good writes= 25459432,  good bytes written=   
35283290616

  htx_messages  Jul 23 14:29:01 2016 err= sev=1 hxssup
  hxecom HE program for enp0s6 terminated by exit(0) call.

  htx_messages  Jul 23 16:29:07 2016 err= sev=4 hang_monitor  
  hxecom for enp0s7 is HUNG!
  Max run time (set in mdt) = 7200 seconds.
  Current elasped time = 7206 seconds.

  htx_messages  Jul 23 18:29:07 2016 err= sev=4 hang_monitor  
  hxecom for enp0s7 is HUNG!
  Max run time (set in mdt) = 7200 seconds.
  Current elasped time = 14406 seconds.

  htx_messages  Jul 23 20:29:07 2016 err= sev=4 hang_monitor  
  hxecom for enp0s7 is HUNG!
  Max run time (set in mdt) = 7200 seconds.
  Current elasped time = 21606 seconds.

  htx_messages  Jul 23 22:29:08 2016 err= sev=4 hang_monitor  
  hxecom for enp0s7 is HUNG!
  Max run time (set in mdt) = 7200 seconds.
  Current elasped time = 28807 seconds.

  htx_messages  Jul 24 00:29:08 2016 err= sev=4 hang_monitor  
  hxecom for enp0s7 is HUNG!
  Max run time (set in mdt) = 7200 seconds.
  Current elasped time = 36007 seconds.

  /dev/enp0s4   Jul 25 04:56:13 2016 err=00e3 sev=4

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

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

--- Comment From cdead...@us.ibm.com 2016-11-18 10:58 EDT---

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

Title:
  STC860:Tuleta-L:KVM:iap03:HTX logs miscompares on multiple adapters on
  ubuntu 16.04 guest.

Status in linux package in Ubuntu:
  New

Bug description:
  == Comment: #0 - Application Cdeadmin  -
  2016-07-26 11:20:20 ==

  
  == Comment: #1 - Application Cdeadmin  - 2016-07-26 
11:20:22 ==
   State: Open by: panico on 25 July 2016 18:02:09 

  Contact Information:
  
  Defect Originator:  Michael Panico
  Defect Originator   pan...@us.ibm.com

  Backup: Deepti Umarani
  Backup ST ID: Deepti S Umarani/India/IBM

  System Info:
  
  Machine Type:8284-22A
  Card Type:...FSP2_P8LE
  Current Boot Side:...T
  Next Boot Side:..T
  PT_Swap:.1
  Current Side Driver:.fips860/b0713a_1630.860 

  Ubuntu KVM Host:
  root@iaos1:/tmp# uname -a
  Linux iaos1 4.4.0-30-generic #49-Ubuntu SMP Fri Jul 1 10:00:36 UTC 2016 
ppc64le ppc64le ppc64le GNU/Linux
  root@iaos1:/tmp# lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu Yakkety Yak (development branch)
  Release:  16.10
  Codename: yakkety

  Ubuntu Guest:
  [htx@iap03]  [1m/usr/lpp/htx/bin# [0m uname -a
  Linux iap03 4.4.0-31-generic #50-Ubuntu SMP Wed Jul 13 00:05:18 UTC 2016 
ppc64le ppc64le ppc64le GNU/Linux
  [htx@iap03]  [1m/usr/lpp/htx/bin# [0m lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 16.04.1 LTS
  Release:  16.04
  Codename: xenial

  HTX level on ubuntu 16.04 guest:
  [htx@iap03]  [1m/usr/lpp/htx/bin# [0m dpkg -l | grep htxubuntu
  ii  htxubuntu  402 ppc64el

  Problem Description:
  
  Running networks (via bridging) on three different guests (other linux, 
ubuntu 16.10 and ubuntu 16.04) the ubuntu 16.04 guest logged a miscompare on 
the austin adapter and the shinerT adapter.  The shinerT ran for 24 hours and 
the austin for 72 hours before logging miscompares.

  From /tmp/htxerr:
  [htx@iap03]  [1m/usr/lpp/htx/bin# [0m cat /tmp/htxerr

  /dev/enp0s6   Jul 23 14:29:00 2016 err=00e3 sev=4 hxecom
  R(102.1.2.20.50854) connected to W(102.1.1.20.39073)
  Miscompare with packet 0, data size = 51062. miscompare_count=0 pakLen = 
51082 
  Miscompare at displacement (decimal) = 23876 
  wbuf = 
  rbuf = 

  For stanza 0, TCP connection, bufmin=3, bufmax=65000, bufinc=10531
  Consecutive prior good reads= 70739865,  good bytes read= 2868570843930

  /dev/enp0s6   Jul 23 14:29:00 2016 err=00d8 sev=4 hxecom
  Shutting down testing due to error flag - 1
  R(102.1.2.20.50854) connected to W(102.1.1.20.39073)
  For stanza 0, TCP connection, bufmin=3, bufmax=65000, bufinc=10531
  Consecutive prior good reads=0,  good bytes read= 0

  /dev/enp0s7   Jul 23 14:29:00 2016 err=00fb0068 sev=1 hxecom
  W(102.1.1.20.39073) connected to R(102.1.2.20.50854)
  Wrote 878 characters, expected 963
  Write failed - Connection reset by peer.
  For stanza 1, TCP connection,  bufmin=3, bufmax=2869, bufinc=94
  Consecutive prior good writes= 25459432,  good bytes written=   
35283290616

  htx_messages  Jul 23 14:29:01 2016 err= sev=1 hxssup
  hxecom HE program for enp0s6 terminated by exit(0) call.

  htx_messages  Jul 23 16:29:07 2016 err= sev=4 hang_monitor  
  hxecom for enp0s7 is HUNG!
  Max run time (set in mdt) = 7200 seconds.
  Current elasped time = 7206 seconds.

  htx_messages  Jul 23 18:29:07 2016 err= sev=4 hang_monitor  
  hxecom for enp0s7 is HUNG!
  Max run time (set in mdt) = 7200 seconds.
  Current elasped time = 14406 seconds.

  htx_messages  Jul 23 20:29:07 2016 err= sev=4 hang_monitor  
  hxecom for enp0s7 is HUNG!
  Max run time (set in mdt) = 7200 seconds.
  Current elasped time = 21606 seconds.

  htx_messages  Jul 23 22:29:08 2016 err= sev=4 hang_monitor  
  hxecom for enp0s7 is HUNG!
  Max run time (set in mdt) = 7200 seconds.
  Current elasped time = 28807 seconds.

  htx_messages  Jul 24 00:29:08 2016 err= sev=4 hang_monitor  
  hxecom for enp0s7 is HUNG!
  Max run time (set in mdt) = 7200 seconds.
  Current elasped time = 36007 seconds.

  /dev/enp0s4   Jul 25 04:56:13 2016 err=00e3 sev=4 hxecom
  R(103.1.2.20.36665) connected to W(103.1.1.20.40459)
  Miscompare with packet 0, data size = 3. miscompare_count=0 pakLen = 
30020 
  Miscompare at

[Kernel-packages] [Bug 1632466] htxmsg

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

Default Comment by Bridge

** Attachment added: "htxmsg"
   https://bugs.launchpad.net/bugs/1632466/+attachment/4779373/+files/htxmsg

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

Title:
  STC860:Tuleta-L:KVM:iap03:HTX logs miscompares on multiple adapters on
  ubuntu 16.04 guest.

Status in linux package in Ubuntu:
  New

Bug description:
  == Comment: #0 - Application Cdeadmin  -
  2016-07-26 11:20:20 ==

  
  == Comment: #1 - Application Cdeadmin  - 2016-07-26 
11:20:22 ==
   State: Open by: panico on 25 July 2016 18:02:09 

  Contact Information:
  
  Defect Originator:  Michael Panico
  Defect Originator   pan...@us.ibm.com

  Backup: Deepti Umarani
  Backup ST ID: Deepti S Umarani/India/IBM

  System Info:
  
  Machine Type:8284-22A
  Card Type:...FSP2_P8LE
  Current Boot Side:...T
  Next Boot Side:..T
  PT_Swap:.1
  Current Side Driver:.fips860/b0713a_1630.860 

  Ubuntu KVM Host:
  root@iaos1:/tmp# uname -a
  Linux iaos1 4.4.0-30-generic #49-Ubuntu SMP Fri Jul 1 10:00:36 UTC 2016 
ppc64le ppc64le ppc64le GNU/Linux
  root@iaos1:/tmp# lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu Yakkety Yak (development branch)
  Release:  16.10
  Codename: yakkety

  Ubuntu Guest:
  [htx@iap03]  [1m/usr/lpp/htx/bin# [0m uname -a
  Linux iap03 4.4.0-31-generic #50-Ubuntu SMP Wed Jul 13 00:05:18 UTC 2016 
ppc64le ppc64le ppc64le GNU/Linux
  [htx@iap03]  [1m/usr/lpp/htx/bin# [0m lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 16.04.1 LTS
  Release:  16.04
  Codename: xenial

  HTX level on ubuntu 16.04 guest:
  [htx@iap03]  [1m/usr/lpp/htx/bin# [0m dpkg -l | grep htxubuntu
  ii  htxubuntu  402 ppc64el

  Problem Description:
  
  Running networks (via bridging) on three different guests (other linux, 
ubuntu 16.10 and ubuntu 16.04) the ubuntu 16.04 guest logged a miscompare on 
the austin adapter and the shinerT adapter.  The shinerT ran for 24 hours and 
the austin for 72 hours before logging miscompares.

  From /tmp/htxerr:
  [htx@iap03]  [1m/usr/lpp/htx/bin# [0m cat /tmp/htxerr

  /dev/enp0s6   Jul 23 14:29:00 2016 err=00e3 sev=4 hxecom
  R(102.1.2.20.50854) connected to W(102.1.1.20.39073)
  Miscompare with packet 0, data size = 51062. miscompare_count=0 pakLen = 
51082 
  Miscompare at displacement (decimal) = 23876 
  wbuf = 
  rbuf = 

  For stanza 0, TCP connection, bufmin=3, bufmax=65000, bufinc=10531
  Consecutive prior good reads= 70739865,  good bytes read= 2868570843930

  /dev/enp0s6   Jul 23 14:29:00 2016 err=00d8 sev=4 hxecom
  Shutting down testing due to error flag - 1
  R(102.1.2.20.50854) connected to W(102.1.1.20.39073)
  For stanza 0, TCP connection, bufmin=3, bufmax=65000, bufinc=10531
  Consecutive prior good reads=0,  good bytes read= 0

  /dev/enp0s7   Jul 23 14:29:00 2016 err=00fb0068 sev=1 hxecom
  W(102.1.1.20.39073) connected to R(102.1.2.20.50854)
  Wrote 878 characters, expected 963
  Write failed - Connection reset by peer.
  For stanza 1, TCP connection,  bufmin=3, bufmax=2869, bufinc=94
  Consecutive prior good writes= 25459432,  good bytes written=   
35283290616

  htx_messages  Jul 23 14:29:01 2016 err= sev=1 hxssup
  hxecom HE program for enp0s6 terminated by exit(0) call.

  htx_messages  Jul 23 16:29:07 2016 err= sev=4 hang_monitor  
  hxecom for enp0s7 is HUNG!
  Max run time (set in mdt) = 7200 seconds.
  Current elasped time = 7206 seconds.

  htx_messages  Jul 23 18:29:07 2016 err= sev=4 hang_monitor  
  hxecom for enp0s7 is HUNG!
  Max run time (set in mdt) = 7200 seconds.
  Current elasped time = 14406 seconds.

  htx_messages  Jul 23 20:29:07 2016 err= sev=4 hang_monitor  
  hxecom for enp0s7 is HUNG!
  Max run time (set in mdt) = 7200 seconds.
  Current elasped time = 21606 seconds.

  htx_messages  Jul 23 22:29:08 2016 err= sev=4 hang_monitor  
  hxecom for enp0s7 is HUNG!
  Max run time (set in mdt) = 7200 seconds.
  Current elasped time = 28807 seconds.

  htx_messages  Jul 24 00:29:08 2016 err= sev=4 hang_monitor  
  hxecom for enp0s7 is HUNG!
  Max run time (set in mdt) = 7200 seconds.
  Current elasped time = 36007 seconds.

  /dev/enp0s4   Jul 25 04:56:13 2016 err=00e3 sev=4 hxecom
  R(103.1.2.20.36665) connected to W(103.1.1.20.40459)
  Miscompare with packet 0, data

[Kernel-packages] [Bug 1632466] htxenp0s5.rbuf_1.out

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

Default Comment by Bridge

** Attachment added: "htxenp0s5.rbuf_1.out"
   
https://bugs.launchpad.net/bugs/1632466/+attachment/4779375/+files/htxenp0s5.rbuf_1.out

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

Title:
  STC860:Tuleta-L:KVM:iap03:HTX logs miscompares on multiple adapters on
  ubuntu 16.04 guest.

Status in linux package in Ubuntu:
  New

Bug description:
  == Comment: #0 - Application Cdeadmin  -
  2016-07-26 11:20:20 ==

  
  == Comment: #1 - Application Cdeadmin  - 2016-07-26 
11:20:22 ==
   State: Open by: panico on 25 July 2016 18:02:09 

  Contact Information:
  
  Defect Originator:  Michael Panico
  Defect Originator   pan...@us.ibm.com

  Backup: Deepti Umarani
  Backup ST ID: Deepti S Umarani/India/IBM

  System Info:
  
  Machine Type:8284-22A
  Card Type:...FSP2_P8LE
  Current Boot Side:...T
  Next Boot Side:..T
  PT_Swap:.1
  Current Side Driver:.fips860/b0713a_1630.860 

  Ubuntu KVM Host:
  root@iaos1:/tmp# uname -a
  Linux iaos1 4.4.0-30-generic #49-Ubuntu SMP Fri Jul 1 10:00:36 UTC 2016 
ppc64le ppc64le ppc64le GNU/Linux
  root@iaos1:/tmp# lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu Yakkety Yak (development branch)
  Release:  16.10
  Codename: yakkety

  Ubuntu Guest:
  [htx@iap03]  [1m/usr/lpp/htx/bin# [0m uname -a
  Linux iap03 4.4.0-31-generic #50-Ubuntu SMP Wed Jul 13 00:05:18 UTC 2016 
ppc64le ppc64le ppc64le GNU/Linux
  [htx@iap03]  [1m/usr/lpp/htx/bin# [0m lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 16.04.1 LTS
  Release:  16.04
  Codename: xenial

  HTX level on ubuntu 16.04 guest:
  [htx@iap03]  [1m/usr/lpp/htx/bin# [0m dpkg -l | grep htxubuntu
  ii  htxubuntu  402 ppc64el

  Problem Description:
  
  Running networks (via bridging) on three different guests (other linux, 
ubuntu 16.10 and ubuntu 16.04) the ubuntu 16.04 guest logged a miscompare on 
the austin adapter and the shinerT adapter.  The shinerT ran for 24 hours and 
the austin for 72 hours before logging miscompares.

  From /tmp/htxerr:
  [htx@iap03]  [1m/usr/lpp/htx/bin# [0m cat /tmp/htxerr

  /dev/enp0s6   Jul 23 14:29:00 2016 err=00e3 sev=4 hxecom
  R(102.1.2.20.50854) connected to W(102.1.1.20.39073)
  Miscompare with packet 0, data size = 51062. miscompare_count=0 pakLen = 
51082 
  Miscompare at displacement (decimal) = 23876 
  wbuf = 
  rbuf = 

  For stanza 0, TCP connection, bufmin=3, bufmax=65000, bufinc=10531
  Consecutive prior good reads= 70739865,  good bytes read= 2868570843930

  /dev/enp0s6   Jul 23 14:29:00 2016 err=00d8 sev=4 hxecom
  Shutting down testing due to error flag - 1
  R(102.1.2.20.50854) connected to W(102.1.1.20.39073)
  For stanza 0, TCP connection, bufmin=3, bufmax=65000, bufinc=10531
  Consecutive prior good reads=0,  good bytes read= 0

  /dev/enp0s7   Jul 23 14:29:00 2016 err=00fb0068 sev=1 hxecom
  W(102.1.1.20.39073) connected to R(102.1.2.20.50854)
  Wrote 878 characters, expected 963
  Write failed - Connection reset by peer.
  For stanza 1, TCP connection,  bufmin=3, bufmax=2869, bufinc=94
  Consecutive prior good writes= 25459432,  good bytes written=   
35283290616

  htx_messages  Jul 23 14:29:01 2016 err= sev=1 hxssup
  hxecom HE program for enp0s6 terminated by exit(0) call.

  htx_messages  Jul 23 16:29:07 2016 err= sev=4 hang_monitor  
  hxecom for enp0s7 is HUNG!
  Max run time (set in mdt) = 7200 seconds.
  Current elasped time = 7206 seconds.

  htx_messages  Jul 23 18:29:07 2016 err= sev=4 hang_monitor  
  hxecom for enp0s7 is HUNG!
  Max run time (set in mdt) = 7200 seconds.
  Current elasped time = 14406 seconds.

  htx_messages  Jul 23 20:29:07 2016 err= sev=4 hang_monitor  
  hxecom for enp0s7 is HUNG!
  Max run time (set in mdt) = 7200 seconds.
  Current elasped time = 21606 seconds.

  htx_messages  Jul 23 22:29:08 2016 err= sev=4 hang_monitor  
  hxecom for enp0s7 is HUNG!
  Max run time (set in mdt) = 7200 seconds.
  Current elasped time = 28807 seconds.

  htx_messages  Jul 24 00:29:08 2016 err= sev=4 hang_monitor  
  hxecom for enp0s7 is HUNG!
  Max run time (set in mdt) = 7200 seconds.
  Current elasped time = 36007 seconds.

  /dev/enp0s4   Jul 25 04:56:13 2016 err=00e3 sev=4 hxecom
  R(103.1.2.20.36665) connected to W(103.1.1.20.40459)

[Kernel-packages] [Bug 1636890] Re: invalid file times with overlayroot and encrypted home

2016-11-18 Thread Seth Forshee

One correction to comment #16 - I'm now finding cases where files not
copied up still have the correct timestamps in ecryptfs, and all the
timestamps match those in the lower inode. So I'm not sure why the
overlayfs inodes seem to have the correct timestamps sometimes.

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

Title:
  invalid file times with overlayroot and encrypted home

Status in cloud-initramfs-tools:
  New
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I did a basic install of 16.04.1 server amd64 (accepting most of the
  defaults) but selected to have the home area of the initial user
  encrypted. Then log on as that user and create some files. Next enable
  overlayroot by adding a /etc/overlayroot.local.conf with
  'overlayroot=tmpfs' and reboot.

  After rebooting and logging in as the user, the previously created files are 
there but the timestamps are wrong. 'stat' gives the times as:
  Access: 1970-01-01 01:00:00.0 +01:00
  Modify: 1970-01-01 01:00:00.0 +01:00
  Change: 1970-01-01 01:00:00.0 +01:00
  --- 
  AlsaDevices:
   total 0
   crw-rw+ 1 root audio 116,  1 Nov 14 15:46 seq
   crw-rw+ 1 root audio 116, 33 Nov 14 15:46 timer
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 16.04
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=05dc7e53-33c6-4784-9d1e-230db315c1f8
  InstallationDate: Installed on 2016-11-14 (0 days ago)
  InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  IwConfig: Error: [Errno 2] No such file or directory
  MachineType: Supermicro Super Server
  Package: linux (not installed)
  PciMultimedia:
   
  ProcFB: 0 astdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-47-generic 
root=UUID=a933e18e-10d8-417d-8154-a0a16a691ae4 ro
  ProcVersionSignature: Ubuntu 4.4.0-47.68-generic 4.4.24
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-47-generic N/A
   linux-backports-modules-4.4.0-47-generic  N/A
   linux-firmware1.157.4
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  xenial
  Uname: Linux 4.4.0-47-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/17/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2.0
  dmi.board.asset.tag: Default string
  dmi.board.name: X10DRD-i
  dmi.board.vendor: Supermicro
  dmi.board.version: 1.00
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 17
  dmi.chassis.vendor: Supermicro
  dmi.chassis.version: 0123456789
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2.0:bd12/17/2015:svnSupermicro:pnSuperServer:pvr0123456789:rvnSupermicro:rnX10DRD-i:rvr1.00:cvnSupermicro:ct17:cvr0123456789:
  dmi.product.name: Super Server
  dmi.product.version: 0123456789
  dmi.sys.vendor: Supermicro

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-initramfs-tools/+bug/1636890/+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 1636330] Re: guest experiencing Transmit Timeouts on CX4

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

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

Title:
  guest experiencing Transmit Timeouts on CX4

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

Bug description:
  This patch fixes a race condition that was reintroduced in the 4.8
  kernel, as part of the P9 changes, after having been originally fixed
  in 3.19. The effect of the race condition is that a secondary thread
  can start trying to execute code from the guest while the thread is
  still in hypervisor mode, so it can cause many different symptoms, one
  of which seems to be the timebase corruption that leads to the lockup
  in ktime_get_ts64. It could cause other problems such as CPU cores
  locking up hard or memory corruption.

  This patch is only needed on the host. It should be applied to any 4.8
  kernel being used as a host, including the Ubuntu 16.10 kernel.

  Hi Paul
  I built a kernel with your patch and put at the host and in the guest. I can 
still see some ktime_get_ts64 at the host. The guest dmesg is clean.

  This patch fixes another race condition I found in the fastsleep code.
  Please apply this patch as well and test.

  Sure will do and provide feedback.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1636330/+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 1640621] onza (i386) - tests ran: 1, failed: 0

tests ran:   1, failed: 0;
  
http://kernel.ubuntu.com/testing/3.19.0-75.83~14.04.1-generic/onza__3.19.0-75.83~14.04.1__2016-11-18_16-01-00/results-index.html

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

Title:
  linux-lts-vivid: 3.19.0-75.83~14.04.1 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
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 verification-testing series:
  Fix Released
Status in linux-lts-vivid package in Ubuntu:
  Invalid
Status in linux-lts-vivid source package in Trusty:
  Confirmed

Bug description:
  This bug is for tracking the 3.19.0-75.83~14.04.1 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
  derivative-trackers-created: true
  kernel-stable-master-bug: 1640613
  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/1640621/+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 1640621] onza (amd64) - tests ran: 1, failed: 0

tests ran:   1, failed: 0;
  
http://kernel.ubuntu.com/testing/3.19.0-75.83~14.04.1-generic/onza__3.19.0-75.83~14.04.1__2016-11-18_15-36-00/results-index.html

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

Title:
  linux-lts-vivid: 3.19.0-75.83~14.04.1 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
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 verification-testing series:
  Fix Released
Status in linux-lts-vivid package in Ubuntu:
  Invalid
Status in linux-lts-vivid source package in Trusty:
  Confirmed

Bug description:
  This bug is for tracking the 3.19.0-75.83~14.04.1 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
  derivative-trackers-created: true
  kernel-stable-master-bug: 1640613
  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/1640621/+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 1636890] Re: invalid file times with overlayroot and encrypted home

2016-11-18 Thread Seth Forshee

I think I see what's going on. Ecryptfs copies up attributes from the
lower filesystem's inode directly. However the practice of overlayfs is
to only copy up i_uid, i_gid, and i_mode from the lower inode into the
overlayfs inode, and to fetch other attributes from the lower inode on
getattr.

The pattern I'm seeing is that inodes that overlayfs has "copied up"
from the lowerdir to the upperdir show up okay. I suspect then that it's
the vfs updating the timestamps in the overlayfs inodes whenever the
event happens that triggered the copy-up.

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

Title:
  invalid file times with overlayroot and encrypted home

Status in cloud-initramfs-tools:
  New
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I did a basic install of 16.04.1 server amd64 (accepting most of the
  defaults) but selected to have the home area of the initial user
  encrypted. Then log on as that user and create some files. Next enable
  overlayroot by adding a /etc/overlayroot.local.conf with
  'overlayroot=tmpfs' and reboot.

  After rebooting and logging in as the user, the previously created files are 
there but the timestamps are wrong. 'stat' gives the times as:
  Access: 1970-01-01 01:00:00.0 +01:00
  Modify: 1970-01-01 01:00:00.0 +01:00
  Change: 1970-01-01 01:00:00.0 +01:00
  --- 
  AlsaDevices:
   total 0
   crw-rw+ 1 root audio 116,  1 Nov 14 15:46 seq
   crw-rw+ 1 root audio 116, 33 Nov 14 15:46 timer
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 16.04
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=05dc7e53-33c6-4784-9d1e-230db315c1f8
  InstallationDate: Installed on 2016-11-14 (0 days ago)
  InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  IwConfig: Error: [Errno 2] No such file or directory
  MachineType: Supermicro Super Server
  Package: linux (not installed)
  PciMultimedia:
   
  ProcFB: 0 astdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-47-generic 
root=UUID=a933e18e-10d8-417d-8154-a0a16a691ae4 ro
  ProcVersionSignature: Ubuntu 4.4.0-47.68-generic 4.4.24
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-47-generic N/A
   linux-backports-modules-4.4.0-47-generic  N/A
   linux-firmware1.157.4
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  xenial
  Uname: Linux 4.4.0-47-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/17/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2.0
  dmi.board.asset.tag: Default string
  dmi.board.name: X10DRD-i
  dmi.board.vendor: Supermicro
  dmi.board.version: 1.00
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 17
  dmi.chassis.vendor: Supermicro
  dmi.chassis.version: 0123456789
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2.0:bd12/17/2015:svnSupermicro:pnSuperServer:pvr0123456789:rvnSupermicro:rnX10DRD-i:rvr1.00:cvnSupermicro:ct17:cvr0123456789:
  dmi.product.name: Super Server
  dmi.product.version: 0123456789
  dmi.sys.vendor: Supermicro

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

2016-11-18 Thread Tyler Hicks

Xenial's apparmor was fixed with package version 2.10.95-0ubuntu2.5

** Changed in: apparmor (Ubuntu Xenial)
   Importance: Undecided => Critical

** Changed in: apparmor (Ubuntu Xenial)
   Status: Confirmed => Fix Released

** Changed in: apparmor (Ubuntu Xenial)
 Assignee: (unassigned) => Tyler Hicks (tyhicks)

-- 
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 Committed
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 1642299] Re: Fix Kernel Crashing under IBM Virtual Scsi Driver

** Changed in: linux (Ubuntu Zesty)
   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/1642299

Title:
  Fix Kernel Crashing under IBM Virtual Scsi Driver

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

Bug description:
  Kernel crashes running large amounts of deployment using Ibmvscsis driver. 
   
  Contact Information = Bryant Ly/b...@us.ibm.com 
   
  Stack trace output:
   
  [ 1780.861532] Faulting instruction address: 0xc0583de0
  [ 1780.861542] Oops: Kernel access of bad area, sig: 11 [#1]
  [ 1780.861549] SMP NR_CPUS=2048 NUMA pSeries
  [ 1780.861557] Modules linked in: ip6table_filter ip6_tables xt_tcpudp 
iptable_mangle ebt_arp ebt_among ebtable_filter ebtables iptable_nat 
nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack iptable_filter 
ip_tables x_tables bridge stp llc target_core_user uio target_core_pscsi 
target_core_file dccp_diag target_core_iblock iscsi_target_mod dccp tcp_diag 
udp_diag inet_diag unix_diag af_packet_diag netlink_diag binfmt_misc 
pseries_rng ibmvmc(OE) rtc_generic ib_iser rdma_cm iw_cm ib_cm ib_sa ib_mad 
ib_core ib_addr iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi autofs4 
mlx4_en vxlan ip6_udp_tunnel udp_tunnel ses enclosure ibmvscsis target_core_mod 
configfs ibmveth mlx4_core megaraid_sas ahci libahci
  [ 1780.861707] CPU: 22 PID: 35128 Comm: tcmu-runner Tainted: GW  OE   
4.4.13-customv7 #22
  [ 1780.861718] task: c001e6f50080 ti: c001e6fd task.ti: 
c001e6fd
  [ 1780.861727] NIP: c0583de0 LR: d65c1b04 CTR: 
c0583da0
  [ 1780.861736] REGS: c001e6fd3950 TRAP: 0300   Tainted: GW  OE
(4.4.13-customv7)
  [ 1780.861745] MSR: 80009033   CR: 48004484  
XER: 2000
  [ 1780.861770] CFAR: c0008468 DAR: 12a0 DSISR: 4000 
SOFTE: 0
  GPR00: d65c1974 c001e6fd3bd0 d65cba00 1298
  GPR04: 12b8 c001fe664468 0018 646920726f662064
  GPR08: 0007 0001 1298 d65c2870
  GPR12: c0583da0 c7add100  
  GPR16: 3fffae67  0002 0001
  GPR20: c001e99032e8  c001e9903300 f000
  GPR24: c001e9903340  d660 d6600080
  GPR28: c001e9902000 0080 f0019800 c001fe664458
  [ 1780.861901] NIP [c0583de0] __bitmap_xor+0x40/0x60
  [ 1780.861910] LR [d65c1b04] tcmu_handle_completions+0x394/0x510 
[target_core_user]
  [ 1780.861919] Call Trace:
  [ 1780.861926] [c001e6fd3bd0] [d65c1974] 
tcmu_handle_completions+0x204/0x510 [target_core_user] (unreliable)
  [ 1780.861942] [c001e6fd3cd0] [d65c1cac] 
tcmu_irqcontrol+0x2c/0x50 [target_core_user]
  [ 1780.861956] [c001e6fd3d00] [d6561798] uio_write+0x98/0x140 
[uio]
  [ 1780.861966] [c001e6fd3d50] [c02dda0c] __vfs_write+0x6c/0xe0
  [ 1780.861977] [c001e6fd3d90] [c02de740] vfs_write+0xc0/0x230
  [ 1780.861988] [c001e6fd3de0] [c02df77c] SyS_write+0x6c/0x110
  [ 1780.861999] [c001e6fd3e30] [c0009204] system_call+0x38/0xb4
  [ 1780.862007] Instruction dump:
  [ 1780.862013] 78c60020 3944fff8 38c6 38a5fff8 78c61f48 3863fff8 7c843214 
4814
  [ 1780.862033] 6000 6000 6000 6042  e9050009 
7faa2040 7d294278
  [ 1780.862056] ---[ end trace 212caf961ccdad3d ]---

  
  A series of patches will fix this issue. 
ibmvscsis: Rearrange functions for future patches
ibmvscsis: Synchronize cmds at tpg_enable_store time
ibmvscsis: Synchronize cmds at remove time
ibmvscsis: Clean up properly if target_submit_cmd/tmr fails
ibmvscsis: Return correct partition name/# to client
ibmvscsis: Issues from Dan Carpenter/Smatch
  http://www.spinics.net/lists/linux-scsi/msg100569.html

  The patch has been accepted and applied to 4.10/scsi-queue.

  scsi: ibmvscsis: Rearrange functions for future patches
  
https://kernel.googlesource.com/pub/scm/linux/kernel/git/mkp/scsi/+/fbbcc033a20a6af94eeb8fa995668ed5051be111

  scsi: ibmvscsis: Synchronize cmds at tpg_enable_store time
  
https://kernel.googlesource.com/pub/scm/linux/kernel/git/mkp/scsi/+/f877a5398764ce18487c1a70f297743ae91a0e25

  scsi: ibmvscsis: Synchronize cmds at remove time
  
https://kernel.googlesource.com/pub/scm/linux/kernel/git/mkp/scsi/+/5dda944d439e295cadceb1e2d7f5b73f9dc2b296

  scsi: ibmvscsis: Clean up properly if target_submit_cmd/tmr fails

[Kernel-packages] [Bug 1642299] Re: Fix Kernel Crashing under IBM Virtual Scsi Driver

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

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

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

** Changed in: linux (Ubuntu Xenial)
 Assignee: (unassigned) => Tim Gardner (timg-tpi)

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

** Changed in: linux (Ubuntu Yakkety)
 Assignee: (unassigned) => Tim Gardner (timg-tpi)

** Also affects: linux (Ubuntu Zesty)
   Importance: High
 Assignee: Canonical Kernel Team (canonical-kernel-team)
   Status: Triaged

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

** Changed in: linux (Ubuntu Zesty)
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Tim Gardner 
(timg-tpi)

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

Title:
  Fix Kernel Crashing under IBM Virtual Scsi Driver

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

Bug description:
  Kernel crashes running large amounts of deployment using Ibmvscsis driver. 
   
  Contact Information = Bryant Ly/b...@us.ibm.com 
   
  Stack trace output:
   
  [ 1780.861532] Faulting instruction address: 0xc0583de0
  [ 1780.861542] Oops: Kernel access of bad area, sig: 11 [#1]
  [ 1780.861549] SMP NR_CPUS=2048 NUMA pSeries
  [ 1780.861557] Modules linked in: ip6table_filter ip6_tables xt_tcpudp 
iptable_mangle ebt_arp ebt_among ebtable_filter ebtables iptable_nat 
nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack iptable_filter 
ip_tables x_tables bridge stp llc target_core_user uio target_core_pscsi 
target_core_file dccp_diag target_core_iblock iscsi_target_mod dccp tcp_diag 
udp_diag inet_diag unix_diag af_packet_diag netlink_diag binfmt_misc 
pseries_rng ibmvmc(OE) rtc_generic ib_iser rdma_cm iw_cm ib_cm ib_sa ib_mad 
ib_core ib_addr iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi autofs4 
mlx4_en vxlan ip6_udp_tunnel udp_tunnel ses enclosure ibmvscsis target_core_mod 
configfs ibmveth mlx4_core megaraid_sas ahci libahci
  [ 1780.861707] CPU: 22 PID: 35128 Comm: tcmu-runner Tainted: GW  OE   
4.4.13-customv7 #22
  [ 1780.861718] task: c001e6f50080 ti: c001e6fd task.ti: 
c001e6fd
  [ 1780.861727] NIP: c0583de0 LR: d65c1b04 CTR: 
c0583da0
  [ 1780.861736] REGS: c001e6fd3950 TRAP: 0300   Tainted: GW  OE
(4.4.13-customv7)
  [ 1780.861745] MSR: 80009033   CR: 48004484  
XER: 2000
  [ 1780.861770] CFAR: c0008468 DAR: 12a0 DSISR: 4000 
SOFTE: 0
  GPR00: d65c1974 c001e6fd3bd0 d65cba00 1298
  GPR04: 12b8 c001fe664468 0018 646920726f662064
  GPR08: 0007 0001 1298 d65c2870
  GPR12: c0583da0 c7add100  
  GPR16: 3fffae67  0002 0001
  GPR20: c001e99032e8  c001e9903300 f000
  GPR24: c001e9903340  d660 d6600080
  GPR28: c001e9902000 0080 f0019800 c001fe664458
  [ 1780.861901] NIP [c0583de0] __bitmap_xor+0x40/0x60
  [ 1780.861910] LR [d65c1b04] tcmu_handle_completions+0x394/0x510 
[target_core_user]
  [ 1780.861919] Call Trace:
  [ 1780.861926] [c001e6fd3bd0] [d65c1974] 
tcmu_handle_completions+0x204/0x510 [target_core_user] (unreliable)
  [ 1780.861942] [c001e6fd3cd0] [d65c1cac] 
tcmu_irqcontrol+0x2c/0x50 [target_core_user]
  [ 1780.861956] [c001e6fd3d00] [d6561798] uio_write+0x98/0x140 
[uio]
  [ 1780.861966] [c001e6fd3d50] [c02dda0c] __vfs_write+0x6c/0xe0
  [ 1780.861977] [c001e6fd3d90] [c02de740] vfs_write+0xc0/0x230
  [ 1780.861988] [c001e6fd3de0] [c02df77c] SyS_write+0x6c/0x110
  [ 1780.861999] [c001e6fd3e30] [c0009204] system_call+0x38/0xb4
  [ 1780.862007] Instruction dump:
  [ 1780.862013] 78c60020 3944fff8 38c6 38a5fff8 78c61f48 3863fff8 7c843214 
4814
  [ 1780.862033] 6000 6000 6000 6042  e9050009 
7faa2040 7d294278
  [ 1780.862056] ---[ end trace 212caf961ccdad3d ]---

  
  A series of patches will fix this issue. 
ibmvscsis: Rearrange functions for future patches
ibmvscsis: Synchronize cmds at tpg_enable_store time
ibmvscsis: Synchronize cmds at remove time
ibmvscsis: Clean up properly if target_submit_cmd/tmr fails
ibmvscsis: Return correct partition name/# to client
ibmvscsis: Issues from Dan Carpenter/Smatch

[Kernel-packages] [Bug 1640921] onibi (amd64) - tests ran: 33, failed: 0

tests ran:  33, failed: 0;
  
http://kernel.ubuntu.com/testing/4.4.0-49.70-lowlatency/onibi__4.4.0-49.70__2016-11-18_13-13-00/results-index.html

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

Title:
  linux: 4.4.0-49.70 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
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:
  In Progress
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 4.4.0-49.70 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
  derivative-trackers-created: 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/1640921/+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 1642972] [NEW] Yakkety update to v4.8.9 stable release

Public bug reported:

SRU Justification

Impact:
   The upstream process for stable tree updates is quite similar
   in scope to the Ubuntu SRU process, e.g., each patch has to
   demonstrably fix a bug, and each patch is vetted by upstream
   by originating either directly from a mainline/stable Linux tree or
   a minimally backported form of that patch. The v4.8.9 upstream stable
   patch set is now available. It should be included in the Ubuntu
   kernel as well.

   git://git.kernel.org/

TEST CASE: TBD

   The following patches from the v4.8.9 stable release shall be
applied:

ALSA: info: Return error for invalid read/write
ALSA: info: Limit the proc text input size
ASoC: cs4270: fix DAPM stream name mismatch
dib0700: fix nec repeat handling
mm, frontswap: make sure allocated frontswap map is assigned
shmem: fix pageflags after swapping DMA32 object
swapfile: fix memory corruption via malformed swapfile
mm: hwpoison: fix thp split handling in memory_failure()
mm/hugetlb: fix huge page reservation leak in private mapping error paths
coredump: fix unfreezable coredumping task
s390/hypfs: Use get_free_page() instead of kmalloc to ensure page alignment
ARC: timer: rtc: implement read loop in "C" vs. inline asm
PCI: Don't attempt to claim shadow copies of ROM
arc: Implement arch-specific dma_map_ops.mmap
pinctrl: cherryview: Serialize register access in suspend/resume
pinctrl: cherryview: Prevent possible interrupt storm on resume
cpupower: Correct return type of cpu_power_is_cpu_online() in cpufreq-set
mmc: sdhci: Fix CMD line reset interfering with ongoing data transfer
mmc: sdhci: Fix unexpected data interrupt handling
mmc: mmc: Use 500ms as the default generic CMD6 timeout
staging: iio: ad5933: avoid uninitialized variable in error case
staging: sm750fb: Fix bugs introduced by early commits
staging: comedi: ni_tio: fix buggy ni_tio_clock_period_ps() return value
drivers: staging: nvec: remove bogus reset command for PS/2 interface
Revert "staging: nvec: ps2: change serio type to passthrough"
staging: nvec: remove managed resource from PS2 driver
usb: dwc3: Fix error handling for core init
USB: cdc-acm: fix TIOCMIWAIT
usb: gadget: u_ether: remove interrupt throttling
drbd: Fix kernel_sendmsg() usage - potential NULL deref
toshiba-wmi: Fix loading the driver on non Toshiba laptops
clk: qoriq: Don't allow CPU clocks higher than starting value
cdc-acm: fix uninitialized variable
iio: hid-sensors: Increase the precision of scale to fix wrong reading 
interpretation.
iio: orientation: hid-sensor-rotation: Add PM function (fix non working driver)
iio: st_sensors: fix scale configuration for h3lis331dl
scsi: qla2xxx: Fix scsi scan hang triggered if adapter fails during init
scsi: mpt3sas: Fix for block device of raid exists even after deleting raid disk
scsi: scsi_dh_alua: fix missing kref_put() in alua_rtpg_work()
scsi: scsi_dh_alua: Fix a reference counting bug
KVM: arm/arm64: vgic: Prevent access to invalid SPIs
drm/radeon: disable runtime pm in certain cases
drm/i915: Respect alternate_ddc_pin for all DDI ports
drm/i915/dp: BDW cdclk fix for DP audio
drm/i915/dp: Extend BDW DP audio workaround to GEN9 platforms
drm/amdgpu: disable runtime pm in certain cases
drm/amdgpu: fix crash in acp_hw_fini
tty/serial: at91: fix hardware handshake on Atmel platforms
drm/amdgpu: fix sched fence slab teardown
drm/amd: fix scheduler fence teardown order v2
xprtrdma: use complete() instead complete_all()
xprtrdma: Fix DMAR failure in frwr_op_map() after reconnect
iommu/io-pgtable-arm: Check for v7s-incapable systems
iommu/amd: Free domain id when free a domain of struct dma_ops_domain
iommu/vt-d: Fix dead-locks in disable_dmar_iommu() path
agp/intel: Flush chipset writes after updating a single PTE
watchdog: core: Fix devres_alloc() allocation size
Input: synaptics-rmi4 - fix error handling in SPI transport driver
Input: synaptics-rmi4 - fix error handling in I2C transport driver
perf top: Fix refreshing hierarchy entries on TUI
mei: bus: fix received data size check in NFC fixup
svcrdma: Skip put_page() when send_reply() fails
svcrdma: Tail iovec leaves an orphaned DMA mapping
nvme: Delete created IO queues on reset
Revert "clocksource/drivers/timer_sun5i: Replace code by clocksource_mmio_init"
x86/build: Fix build with older GCC versions
clk: samsung: clk-exynos-audss: Fix module autoload
rtc: pcf2123: Add missing error code assignment before test
s390/dumpstack: restore reliable indicator for call traces
lib/genalloc.c: start search from start of chunk
hwrng: core - Don't use a stack buffer in add_early_randomness()
i40e: fix call of ndo_dflt_bridge_getlink()
mmc: sdhci-msm: Fix error return code in sdhci_msm_probe()
ACPI / APEI: Fix incorrect return value of ghes_proc()
ACPI/PCI/IRQ: assign ISA IRQ directly during early boot stages
ACPI/PCI: pci_link: penalize SCI correctly
ACPI/PCI: pci_link: Include PIRQ_PENALTY_PCI_USING for ISA IRQs
batman-adv: Modify neigh_list only

[Kernel-packages] [Bug 1642968] [NEW] Xenial update to v4.4.33 stable release

Public bug reported:

SRU Justification

Impact:
   The upstream process for stable tree updates is quite similar
   in scope to the Ubuntu SRU process, e.g., each patch has to
   demonstrably fix a bug, and each patch is vetted by upstream
   by originating either directly from a mainline/stable Linux tree or
   a minimally backported form of that patch. The v4.4.33 upstream stable
   patch set is now available. It should be included in the Ubuntu
   kernel as well.

   git://git.kernel.org/

TEST CASE: TBD

   The following patches from the v4.4.33 stable release shall be
applied:

ALSA: info: Return error for invalid read/write
ALSA: info: Limit the proc text input size
ASoC: cs4270: fix DAPM stream name mismatch
dib0700: fix nec repeat handling
swapfile: fix memory corruption via malformed swapfile
coredump: fix unfreezable coredumping task
s390/hypfs: Use get_free_page() instead of kmalloc to ensure page alignment
ARC: timer: rtc: implement read loop in "C" vs. inline asm
pinctrl: cherryview: Serialize register access in suspend/resume
pinctrl: cherryview: Prevent possible interrupt storm on resume
staging: iio: ad5933: avoid uninitialized variable in error case
drivers: staging: nvec: remove bogus reset command for PS/2 interface
Revert "staging: nvec: ps2: change serio type to passthrough"
staging: nvec: remove managed resource from PS2 driver
USB: cdc-acm: fix TIOCMIWAIT
usb: gadget: u_ether: remove interrupt throttling
drbd: Fix kernel_sendmsg() usage - potential NULL deref
toshiba-wmi: Fix loading the driver on non Toshiba laptops
clk: qoriq: Don't allow CPU clocks higher than starting value
iio: hid-sensors: Increase the precision of scale to fix wrong reading 
interpretation.
iio: orientation: hid-sensor-rotation: Add PM function (fix non working driver)
scsi: qla2xxx: Fix scsi scan hang triggered if adapter fails during init
scsi: mpt3sas: Fix for block device of raid exists even after deleting raid disk
KVM: MIPS: Precalculate MMIO load resume PC
drm/i915: Respect alternate_ddc_pin for all DDI ports
dmaengine: at_xdmac: fix spurious flag status for mem2mem transfers
tty/serial: at91: fix hardware handshake on Atmel platforms
iommu/amd: Free domain id when free a domain of struct dma_ops_domain
iommu/vt-d: Fix dead-locks in disable_dmar_iommu() path
mei: bus: fix received data size check in NFC fixup
lib/genalloc.c: start search from start of chunk
hwrng: core - Don't use a stack buffer in add_early_randomness()
i40e: fix call of ndo_dflt_bridge_getlink()
ACPI / APEI: Fix incorrect return value of ghes_proc()
ASoC: sun4i-codec: return error code instead of NULL when create_card fails
mmc: mxs: Initialize the spinlock prior to using it
btrfs: qgroup: Prevent qgroup->reserved from going subzero
netfilter: fix namespace handling in nf_log_proc_dostring
Linux 4.4.33

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

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


** Tags: kernel-stable-tracking-bug

** Tags added: kernel-stable-tracking-bug

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

** Description changed:

+ SRU Justification
  
- SRU Justification
+ Impact:
+    The upstream process for stable tree updates is quite similar
+    in scope to the Ubuntu SRU process, e.g., each patch has to
+    demonstrably fix a bug, and each patch is vetted by upstream
+    by originating either directly from a mainline/stable Linux tree or
+    a minimally backported form of that patch. The v4.4.33 upstream stable
+    patch set is now available. It should be included in the Ubuntu
+    kernel as well.
  
- Impact:
-The upstream process for stable tree updates is quite similar
-in scope to the Ubuntu SRU process, e.g., each patch has to
-demonstrably fix a bug, and each patch is vetted by upstream
-by originating either directly from a mainline/stable Linux tree or
-a minimally backported form of that patch. The v4.4.33 upstream stable
-patch set is now available. It should be included in the Ubuntu
-kernel as well.
+    git://git.kernel.org/
  
-git://git.kernel.org/
+ TEST CASE: TBD
  
- TEST CASE: TBD
+    The following patches from the v4.4.33 stable release shall be
+ applied:
  
-The following patches from the v4.4.33 stable release shall be
- applied:
+ ALSA: info: Return error for invalid read/write
+ ALSA: info: Limit the proc text input size
+ ASoC: cs4270: fix DAPM stream name mismatch
+ dib0700: fix nec repeat handling
+ swapfile: fix memory corruption via malformed swapfile
+ coredump: fix unfreezable coredumping task
+ s390/hypfs: Use get_free_page() instead of kmalloc to ensure page alignment
+ ARC: timer: rtc: implement read loop in "C" vs. inline asm
+ pinctrl: cherryview: Serialize register access in suspend/resume
+

[Kernel-packages] [Bug 1447909] Re: external mic not detected on machines with alc256 codec

2016-11-18 Thread MIFAS

Not working. It's only working when I add the following line in
/etc/modprobe.d/alsa-base.conf file

options snd-hda-intel model=laptop-dmic

And Also I need to manually change to Internal Microphone through Sound
Switcher Indicator - version 1.2.2

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

Title:
  external mic not detected on machines with alc256 codec

Status in HWE Next:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released

Bug description:
  This bug is used for tracking, please do not triage.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1447909/+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 1641083] modoc (ppc64el) - tests ran: 18, failed: 0

tests ran:  18, failed: 0;
  
http://kernel.ubuntu.com/testing/4.8.0-28.30-generic/modoc__4.8.0-28.30__2016-11-18_13-06-00/results-index.html

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

Title:
  linux: 4.8.0-28.30 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
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:
  In Progress
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 Yakkety:
  Confirmed

Bug description:
  This bug is for tracking the 4.8.0-28.30 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
  derivative-trackers-created: 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/1641083/+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 1594023] Re: Poweroff or reboot hangs. Laptop won't shutdown. 16.04

2016-11-18 Thread Blackbug

I have HP envy ultrabook. However, I do have samsung 850 SSD..so i guess
it all comes to SSD then

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

Title:
  Poweroff or reboot hangs. Laptop won't shutdown. 16.04

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  This is about a fresh Ubuntu 16.04 install on a new laptop (asus
  x540sa). After pressing the shutdown button in the start menu; the
  shutdown procedure starts and in the final splash screen the system
  just hangs. Tried a second time by pressing Esc once the splash screen
  showed up and I saw that it reaches the line "Reached target shutdown"
  and just stops there, no matter how long I leave it there the machine
  won't turn off.

  I also tried a Kubuntu 16.04 fresh install on the same machine and it
  hanged too at the final splash screen where the pulsating logo
  stopped. Then I tried with Esc only to see the exact same line in the
  end.

  The issue seems to affect lately quite many users as shown by the
  google results of the past month / week or so.

  I have also tried shutting down from the console with shutdown -and
  all the parameters after that suggested online- and sudo poweroff but
  unfortunately they didn't do the trick. The exact same situation
  occurred.

  Unmounting the swap as suggested online doesn't work.

  Also rebooting the system is not working either due to the same issue.

  So right now the only way for me to poweroff the machine is to press
  the power button on the keyboard continuously.

  Reproducible: Always

  Steps to Reproduce:
  1.Install OS
  2.Do something, anything or nothing
  3.Try to shutdown or reboot

  Actual Results:
  The computer is not shutting down: "Reached target shutdown" and hangs there.

  Expected Results:
  Powering off the machine.

  For what it's worth, closing the lid won't suspend the system, but
  using the menu buttons for suspension will do it.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1594023/+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 1385113] Re: hid-generic 0005:099A:0500.0001: unknown main item tag 0x0

2016-11-18 Thread Jani Tykkä

Could this fix be
related?https://github.com/torvalds/linux/commit/6add49fff9233a5c43011eb42b521257cbaa9bda

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

Title:
  hid-generic 0005:099A:0500.0001: unknown main item tag 0x0

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

Bug description:
  Message with Mouse Bluetooth

  [   32.960478] hid-generic 0005:099A:0500.0001: unknown main item tag
  0x0

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: linux-image-3.16.0-23-generic 3.16.0-23.31
  ProcVersionSignature: Ubuntu 3.16.0-23.31-generic 3.16.4
  Uname: Linux 3.16.0-23-generic x86_64
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  caravena   3344 F pulseaudio
  CurrentDesktop: GNOME
  Date: Fri Oct 24 05:22:54 2014
  HibernationDevice: RESUME=UUID=360bd2d2-4f44-4311-86d6-4781ac81ee87
  InstallationDate: Installed on 2014-09-25 (29 days ago)
  InstallationMedia: Ubuntu-GNOME 14.10 "Utopic Unicorn" - Alpha amd64 
(20140923)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 530U3C/530U4C
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-3.16.0-23-generic 
root=UUID=0fb75fae-baa3-428b-ace4-498e69ff7fb6 ro rootflags=subvol=@ quiet 
splash nomdmonddf nomdmonisw nomdmonddf nomdmonisw vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.16.0-23-generic N/A
   linux-backports-modules-3.16.0-23-generic  N/A
   linux-firmware 1.138
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/15/2013
  dmi.bios.vendor: Phoenix Technologies Ltd.
  dmi.bios.version: P14AAJ
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: SAMSUNG_NP1234567890
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: FAB1
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLtd.:bvrP14AAJ:bd04/15/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn530U3C/530U4C:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnSAMSUNG_NP1234567890:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1:
  dmi.product.name: 530U3C/530U4C
  dmi.product.version: 0.1
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1385113/+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 1640613] ms10-35-mcdivittB0-kernel (arm64) - tests ran: 3, failed: 2

tests ran:   3, failed: 2;
  
http://kernel.ubuntu.com/testing/3.19.0-75.83-generic/ms10-35-mcdivittB0-kernel__3.19.0-75.83__2016-11-18_12-41-00/results-index.html

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

Title:
  linux: 3.19.0-75.83 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
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:
  In Progress
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:
  Fix Released
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Vivid:
  Confirmed

Bug description:
  This bug is for tracking the 3.19.0-75.83 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
  derivative-trackers-created: 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/1640613/+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 1590590] Re: Touchpad not recognized on Dell Latitude E7470 Ultrabook

2016-11-18 Thread Petr Chmelar

No @bagl0312, this is not fixed in
Linux p37470 4.4.0-47-generic #68-Ubuntu SMP Wed Oct 26 19:39:52 UTC 2016 
x86_64 x86_64 x86_64 GNU/Linux

I spoke to some Dell representatives and they told me that anyone with
Premium Support can report the this issue and they are supposed to fix
it, because the Premium Support includes both hardware and software
issues.

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

Title:
  Touchpad not recognized on Dell Latitude E7470 Ultrabook

Status in linux package in Ubuntu:
  Triaged
Status in xserver-xorg-input-synaptics package in Ubuntu:
  Confirmed

Bug description:
  Expected: Touchpad settings available in Mouse & Touchpad Settings
  dialog

  Actual result: Touchpad settings missing entirely

  
  Details:
  The touchpad on my Dell Ultrabook (Latitude E7470) functions mostly. 

  The settings for the touchpad are not available at all in the Mouse
  and Touchpad settings (see http://i.imgur.com/YRGiOrj.png).

  Two-finger scrolling works as expected except it's using "Natural
  Scrolling" by default and there is no way to change it.

  xinput list does not display a touchpad at all:

  ⎡ Virtual core pointerid=2[master pointer  (3)]
  ⎜   ↳ Virtual core XTEST pointer  id=4[slave  pointer 
 (2)]
  ⎜   ↳ ELAN Touchscreenid=11   [slave  pointer 
 (2)]
  ⎜   ↳ ImPS/2 Generic Wheel Mouse  id=13   [slave  pointer 
 (2)]
  ⎣ Virtual core keyboard   id=3[master keyboard (2)]
  ↳ Virtual core XTEST keyboard id=5[slave  
keyboard (3)]
  ↳ Power Buttonid=6[slave  
keyboard (3)]
  ↳ Video Bus   id=7[slave  
keyboard (3)]
  ↳ Power Buttonid=8[slave  
keyboard (3)]
  ↳ Sleep Buttonid=9[slave  
keyboard (3)]
  ↳ Integrated_Webcam_FHD   id=10   [slave  
keyboard (3)]
  ↳ AT Translated Set 2 keyboardid=12   [slave  
keyboard (3)]
  ↳ Dell WMI hotkeysid=14   [slave  
keyboard (3)]
  ↳ DELL Wireless hotkeys   id=15   [slave  
keyboard (3)]

  
  /proc/bus/input/devices lists the device as a "Generic Wheel Mouse"

  Output of `lsb_release -rd`:
  Description:  Ubuntu 16.04 LTS
  Release:  16.04

  xserver-xorg-input-synaptics version information:
  xserver-xorg-input-synaptics:
Installed: 1.8.2-1ubuntu3
Candidate: 1.8.2-1ubuntu3
Version table:
   *** 1.8.2-1ubuntu3 500
  500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  100 /var/lib/dpkg/status

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1590590/+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 1618678] Re: Disk Device Driver Reported Error: DID_ERROR ... DRIVER SENSE

2016-11-18 Thread Chris Samuel

Just to update that this is still happening in 4.8.0-27-generic (AMD64).

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

Title:
  Disk Device Driver Reported Error: DID_ERROR ... DRIVER SENSE

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  The Ubuntu 16.04.1 LTS upgrade from kernel 4.4.0-21 to 4.4.0-34
  introduced the following periodic error message sequence reported in
  dmesg/syslog:

  ...
  sd 4:0:0:0: [sdc] tag#0 FAILED Result: hostbyte=DID_ERROR 
driverbyte=DRIVER_SENSE
  sd 4:0:0:0: [sdc] tag#0 Sense Key : Hardware Error [current] [descriptor] 
  sd 4:0:0:0: [sdc] tag#0 Add. Sense: No additional sense information
  sd 4:0:0:0: [sdc] tag#0 CDB: ATA command pass through(16) 85 06 2c 00 da 00 
00 00 00 00 4f 00 c2 00 b0 00 
  sd 4:0:0:0: [sdc] tag#0 FAILED Result: hostbyte=DID_ERROR 
driverbyte=DRIVER_SENSE
  sd 4:0:0:0: [sdc] tag#0 Sense Key : Hardware Error [current] [descriptor] 
  sd 4:0:0:0: [sdc] tag#0 Add. Sense: No additional sense information
  sd 4:0:0:0: [sdc] tag#0 CDB: ATA command pass through(16) 85 06 20 00 00 00 
00 00 00 00 00 00 00 00 e5 00 
  sd 4:0:0:0: [sdc] tag#0 FAILED Result: hostbyte=DID_ERROR 
driverbyte=DRIVER_SENSE
  sd 4:0:0:0: [sdc] tag#0 Sense Key : Hardware Error [current] [descriptor] 
  sd 4:0:0:0: [sdc] tag#0 Add. Sense: No additional sense information
  sd 4:0:0:0: [sdc] tag#0 CDB: ATA command pass through(12)/Blank a1 06 20 da 
00 00 4f c2 00 b0 00 00 
  ...

  These repeat at precisely five and ten minute intervals but appear to
  result in no data corruption, nor performance degradation on the
  external USB drive.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-36-generic 4.4.0-36.55
  ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16
  Uname: Linux 4.4.0-36-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC1D0c:   rap3412 F...m pulseaudio
   /dev/snd/pcmC1D0p:   rap3412 F...m pulseaudio
   /dev/snd/controlC1:  rap3412 F pulseaudio
   /dev/snd/controlC0:  rap3412 F pulseaudio
  CurrentDesktop: Unity
  Date: Tue Aug 30 19:48:43 2016
  HibernationDevice: RESUME=UUID=bb098361-baff-41e3-bf95-dad938b5d42c
  InstallationDate: Installed on 2016-08-10 (21 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  IwConfig:
   lono wireless extensions.
   
   enp0s9no wireless extensions.
  MachineType: ECS K8M890M-M
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-36-generic 
root=UUID=d38a2b9b-2da3-48e2-b5f8-a464f49a5dc5 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-36-generic N/A
   linux-backports-modules-4.4.0-36-generic  N/A
   linux-firmware1.157.3
  RfKill:
   0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/29/2006
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 080013
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: K8M890M-M
  dmi.board.vendor: ECS
  dmi.board.version: 1.X
  dmi.chassis.asset.tag: 0123ABC
  dmi.chassis.type: 3
  dmi.chassis.vendor: ECS
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr080013:bd12/29/2006:svnECS:pnK8M890M-M:pvr1.X:rvnECS:rnK8M890M-M:rvr1.X:cvnECS:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: K8M890M-M
  dmi.product.version: 1.X
  dmi.sys.vendor: ECS

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1618678/+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 1639202] Re: Cannot enlist/commission machines in MAAS 2.1 with usb network adapter

2016-11-18 Thread Richard Lovell

Hi Dave,

The following output appears. I don't see an error relating to "no net-
BOOTIF.conf" now...just what's below...

ipconfig: BOOTIF: SIOCGIFINDEX: no such device
ipconfig: no devices to configure
/scripts/local-top/scsi: line 515: can't open '/run/net-BOOTIF.conf'
lvmetad is not active yet, using direct activation during sysinit


ip a # gives:
1: lo  mtu 65536 qdisc noop qlen 1
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: enx847beb55c195:  mtu 1500 qdisc noop qlen 1000
link/ether 84:7b:eb:55:c1:95 brd ff:ff:ff:ff:ff:ff


cat /proc/cmdline gives the mac of the usb-c network adapter (different mac to 
the previous command - above):

BOOT_IMAGE=ubuntu/amd64/generic/xenial/daily/boot-kernel nomodeset
isci_target_name=iqn.2004-05.com.ubuntu:maas:ephermeral-ubuntu-amd64
-generic-xenial-daily iscsi_target_ip=
iscsi_target_port=3260 iscsi_initiator=maas-enlist ip=maas-
enlist:BOOTIF ro root=/dev/disk/by-path/ip-:3260
-iscsi-iqn.2004-05.com.ubuntu:maas:ephemeral-ubuntu-amd64-generic-
xenial-daily-lun-1 overlayroot=tmpfs cloud-config-url=http://:5420/MAAS/metadata/latest/enlist-preseed/?op=get_enlist_preseed
log_host= log_port=514
initrd=ubuntu/amd64/generic/xenial/daily/boot-initrd BOOTIF=01-9c-
eb-e8-3c-52-cc


lsmod gives:

/bin/sh: lsmod: not found


ipconfig:

ipconfig: no devices to configure


Other info:
Gave up waiting for root device. Common problems:
- Boot args (cat /proc/cmdline)
  - Check rootdelay = ( did the system wait long enough)
  - Check root= (did the system wait for the right device?)
- Missing modules (cat /proc/modules; ls /dev)
ALERT ..dropping to shell.

regards
Richard

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

Title:
  Cannot enlist/commission machines in MAAS 2.1 with usb network adapter

Status in MAAS:
  Invalid
Status in maas-images:
  New
Status in initramfs-tools package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Invalid

Bug description:
  After upgrade from MAAS 2.0 to MAAS 2.1:

  Cannot enlist/commission client machines via network boot (or pre-
  staging machine) when using usb-c network adapter D59GG (e.g.
  Precision 5510). This was working ok with MAAS 2.0.

  Using the Xenial 16.04 base image for enlist/commission (no minimum
  kernel set).

  Enlist/Commission/Deploy works fine with other laptop and desktop
  models which have a built in NIC.

  From an already deployed Precision 5510 system (16.04.1) I can see the
  following module is loaded when the usb-c adapter is connected (and
  working):

  $ lsmod
  usbnet45056 1 cdc_ether

  
  Errors received on client during enlisting with MAAS:

  no /run/net-bootif.conf
  lvmetad is not activated
  ...invalid path for logical volume.
  gave up waiting for root device
  common problems: boot args (cat /proc/cmdline)
  check rootdelay = (did system wait long enough)
  check root = (did the system wait for the right device?)
  missing modules (cat /proc/modules)
  ALERT!  
/dev/disk/by-path/ip-:3260-iscsi-iqn,2004.05.com.ubuntu:maas:ephemeral-ubuntu-amd64-generic-xenial-daily-lun-1
 does not exist. Dropping to shell!
  usbcore: registered new interface driver usbhid
  usbhid: USB HID core driver

  - cat /proc/cmdline shows mac address that of usb-c network adapter.
  - cat /proc/modules includes “usbnet 45056 cdc_ether, Live 0xc009c000”
  - cat /proc/modules | grep usb … includes “ usbnet 45056 and usbhid 49152”

  
  I've tried enlisting with older boot image and different kernel versions 
(14.04 and 16.04 with ga-16.04, hwe-16.04 set) but get the same problem.

  It seems like the usb-c network adapter isn't loading properly or
  maybe just not quickly enough?

  Please let me know if you require any more info. I can provide info
  from /var/log/maas/* and dpkg -l '*maas*'|cat if need be.

To manage notifications about this bug go to:
https://bugs.launchpad.net/maas/+bug/1639202/+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 1640921] onibi (i386) - tests ran: 4, failed: 0

tests ran:   4, failed: 0;
  
http://kernel.ubuntu.com/testing/4.4.0-49.70-lowlatency/onibi__4.4.0-49.70__2016-11-18_11-23-00/results-index.html

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

Title:
  linux: 4.4.0-49.70 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
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:
  In Progress
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 4.4.0-49.70 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
  derivative-trackers-created: 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/1640921/+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 1594023] Re: Poweroff or reboot hangs. Laptop won't shutdown. 16.04

2016-11-18 Thread Daniele Viganò

So, it seems we are all on Dell with a Samsung SSD 850 drive. Next week
I'll have a chance to try a different SSD from Kingston. I'll see if the
bug is still reproducible.

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

Title:
  Poweroff or reboot hangs. Laptop won't shutdown. 16.04

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  This is about a fresh Ubuntu 16.04 install on a new laptop (asus
  x540sa). After pressing the shutdown button in the start menu; the
  shutdown procedure starts and in the final splash screen the system
  just hangs. Tried a second time by pressing Esc once the splash screen
  showed up and I saw that it reaches the line "Reached target shutdown"
  and just stops there, no matter how long I leave it there the machine
  won't turn off.

  I also tried a Kubuntu 16.04 fresh install on the same machine and it
  hanged too at the final splash screen where the pulsating logo
  stopped. Then I tried with Esc only to see the exact same line in the
  end.

  The issue seems to affect lately quite many users as shown by the
  google results of the past month / week or so.

  I have also tried shutting down from the console with shutdown -and
  all the parameters after that suggested online- and sudo poweroff but
  unfortunately they didn't do the trick. The exact same situation
  occurred.

  Unmounting the swap as suggested online doesn't work.

  Also rebooting the system is not working either due to the same issue.

  So right now the only way for me to poweroff the machine is to press
  the power button on the keyboard continuously.

  Reproducible: Always

  Steps to Reproduce:
  1.Install OS
  2.Do something, anything or nothing
  3.Try to shutdown or reboot

  Actual Results:
  The computer is not shutting down: "Reached target shutdown" and hangs there.

  Expected Results:
  Powering off the machine.

  For what it's worth, closing the lid won't suspend the system, but
  using the menu buttons for suspension will do it.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1594023/+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 1641083] modoc (ppc64el) - tests ran: 10, failed: 0

tests ran:  10, failed: 0;
  
http://kernel.ubuntu.com/testing/4.8.0-28.30-generic/modoc__4.8.0-28.30__2016-11-18_11-46-00/results-index.html

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

Title:
  linux: 4.8.0-28.30 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
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:
  In Progress
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 Yakkety:
  Confirmed

Bug description:
  This bug is for tracking the 4.8.0-28.30 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
  derivative-trackers-created: 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/1641083/+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 1640621] ms10-35-mcdivittB0-kernel (arm64) - tests ran: 3, failed: 2

tests ran:   3, failed: 2;
  
http://kernel.ubuntu.com/testing/3.19.0-75.83~14.04.1-generic/ms10-35-mcdivittB0-kernel__3.19.0-75.83~14.04.1__2016-11-18_11-54-00/results-index.html

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

Title:
  linux-lts-vivid: 3.19.0-75.83~14.04.1 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
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 verification-testing series:
  Fix Released
Status in linux-lts-vivid package in Ubuntu:
  Invalid
Status in linux-lts-vivid source package in Trusty:
  Confirmed

Bug description:
  This bug is for tracking the 3.19.0-75.83~14.04.1 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
  derivative-trackers-created: true
  kernel-stable-master-bug: 1640613
  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/1640621/+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 1640621] ms10-35-mcdivittB0-kernel (arm64) - tests ran: 1, failed: 0

tests ran:   1, failed: 0;
  
http://kernel.ubuntu.com/testing/3.19.0-75.83~14.04.1-generic/ms10-35-mcdivittB0-kernel__3.19.0-75.83~14.04.1__2016-11-18_11-32-00/results-index.html

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

Title:
  linux-lts-vivid: 3.19.0-75.83~14.04.1 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
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 verification-testing series:
  Fix Released
Status in linux-lts-vivid package in Ubuntu:
  Invalid
Status in linux-lts-vivid source package in Trusty:
  Confirmed

Bug description:
  This bug is for tracking the 3.19.0-75.83~14.04.1 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
  derivative-trackers-created: true
  kernel-stable-master-bug: 1640613
  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/1640621/+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 1639202] Re: Cannot enlist/commission machines in MAAS 2.1 with usb network adapter

2016-11-18 Thread Dave Chiluk

@Richard Lovell
Can you please provide me the console log messages that exist above the "no 
/run/net-bootif.conf"?

Additionally can I get the output of following commands from the laptop after 
the message "Dropping to shell!"
- ip a # I'm not sure if this available, but ifconfig or similar would be 
helpful.  Basically I need the name of the nic as discovered.  I have a feeling 
that the initramfs is not correctly checking for this name when it attempts to 
bring up the interfaces.
- lsmod 
- cat /proc/cmdline

More commands may be necessary after I have this output and am able to
investigate the initramfs.

Thanks

** Changed in: maas
   Status: Incomplete => Invalid

** Also affects: initramfs-tools (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: initramfs-tools (Ubuntu)
 Assignee: (unassigned) => Dave Chiluk (chiluk)

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

Title:
  Cannot enlist/commission machines in MAAS 2.1 with usb network adapter

Status in MAAS:
  Invalid
Status in maas-images:
  New
Status in initramfs-tools package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Invalid

Bug description:
  After upgrade from MAAS 2.0 to MAAS 2.1:

  Cannot enlist/commission client machines via network boot (or pre-
  staging machine) when using usb-c network adapter D59GG (e.g.
  Precision 5510). This was working ok with MAAS 2.0.

  Using the Xenial 16.04 base image for enlist/commission (no minimum
  kernel set).

  Enlist/Commission/Deploy works fine with other laptop and desktop
  models which have a built in NIC.

  From an already deployed Precision 5510 system (16.04.1) I can see the
  following module is loaded when the usb-c adapter is connected (and
  working):

  $ lsmod
  usbnet45056 1 cdc_ether

  
  Errors received on client during enlisting with MAAS:

  no /run/net-bootif.conf
  lvmetad is not activated
  ...invalid path for logical volume.
  gave up waiting for root device
  common problems: boot args (cat /proc/cmdline)
  check rootdelay = (did system wait long enough)
  check root = (did the system wait for the right device?)
  missing modules (cat /proc/modules)
  ALERT!  
/dev/disk/by-path/ip-:3260-iscsi-iqn,2004.05.com.ubuntu:maas:ephemeral-ubuntu-amd64-generic-xenial-daily-lun-1
 does not exist. Dropping to shell!
  usbcore: registered new interface driver usbhid
  usbhid: USB HID core driver

  - cat /proc/cmdline shows mac address that of usb-c network adapter.
  - cat /proc/modules includes “usbnet 45056 cdc_ether, Live 0xc009c000”
  - cat /proc/modules | grep usb … includes “ usbnet 45056 and usbhid 49152”

  
  I've tried enlisting with older boot image and different kernel versions 
(14.04 and 16.04 with ga-16.04, hwe-16.04 set) but get the same problem.

  It seems like the usb-c network adapter isn't loading properly or
  maybe just not quickly enough?

  Please let me know if you require any more info. I can provide info
  from /var/log/maas/* and dpkg -l '*maas*'|cat if need be.

To manage notifications about this bug go to:
https://bugs.launchpad.net/maas/+bug/1639202/+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 1639202] Re: Cannot enlist/commission machines in MAAS 2.1 with usb network adapter

2016-11-18 Thread Dave Chiluk

I just checked the maas daily images, and both the 4.4.0-45 xenial and
4.8.0-27 yakkety initrd contain the cdc_ether kernel drivers.  I also
checked the 20160310 maas image that contains the 4.4.0-11-generic
kernel, and it contains the drivers as well.

So I now suspect that the initramfs is not correctly configuring the
network adapter.

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

Title:
  Cannot enlist/commission machines in MAAS 2.1 with usb network adapter

Status in MAAS:
  Invalid
Status in maas-images:
  New
Status in initramfs-tools package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Invalid

Bug description:
  After upgrade from MAAS 2.0 to MAAS 2.1:

  Cannot enlist/commission client machines via network boot (or pre-
  staging machine) when using usb-c network adapter D59GG (e.g.
  Precision 5510). This was working ok with MAAS 2.0.

  Using the Xenial 16.04 base image for enlist/commission (no minimum
  kernel set).

  Enlist/Commission/Deploy works fine with other laptop and desktop
  models which have a built in NIC.

  From an already deployed Precision 5510 system (16.04.1) I can see the
  following module is loaded when the usb-c adapter is connected (and
  working):

  $ lsmod
  usbnet45056 1 cdc_ether

  
  Errors received on client during enlisting with MAAS:

  no /run/net-bootif.conf
  lvmetad is not activated
  ...invalid path for logical volume.
  gave up waiting for root device
  common problems: boot args (cat /proc/cmdline)
  check rootdelay = (did system wait long enough)
  check root = (did the system wait for the right device?)
  missing modules (cat /proc/modules)
  ALERT!  
/dev/disk/by-path/ip-:3260-iscsi-iqn,2004.05.com.ubuntu:maas:ephemeral-ubuntu-amd64-generic-xenial-daily-lun-1
 does not exist. Dropping to shell!
  usbcore: registered new interface driver usbhid
  usbhid: USB HID core driver

  - cat /proc/cmdline shows mac address that of usb-c network adapter.
  - cat /proc/modules includes “usbnet 45056 cdc_ether, Live 0xc009c000”
  - cat /proc/modules | grep usb … includes “ usbnet 45056 and usbhid 49152”

  
  I've tried enlisting with older boot image and different kernel versions 
(14.04 and 16.04 with ga-16.04, hwe-16.04 set) but get the same problem.

  It seems like the usb-c network adapter isn't loading properly or
  maybe just not quickly enough?

  Please let me know if you require any more info. I can provide info
  from /var/log/maas/* and dpkg -l '*maas*'|cat if need be.

To manage notifications about this bug go to:
https://bugs.launchpad.net/maas/+bug/1639202/+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 1640921] onibi (amd64) - tests ran: 31, failed: 0

tests ran:  31, failed: 0;
  
http://kernel.ubuntu.com/testing/4.4.0-49.70-lowlatency/onibi__4.4.0-49.70__2016-11-18_09-33-00/results-index.html

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

Title:
  linux: 4.4.0-49.70 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
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:
  In Progress
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 4.4.0-49.70 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
  derivative-trackers-created: 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/1640921/+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 1639016] Re: e100e NETDEV WATCHDOG: transmit queue 0 timed out

2016-11-18 Thread Konrad

I can't boot the mainline kernel. 4.9-rc4 and rc5 stops at initramfs and drops 
to busybox.
>From dmesg I can see that a lot of modules (libahci, wmi, usb_storage, hid, 
>psmouse) errror on this:
"hid: disagrees about version of symbol mcount
hid: unknown symbol mcount (err -22)"

I can't save dmesg on pendrive, because usb_storage is not loading too.
Can't mount anything else where I could write to file.

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

Title:
  e100e NETDEV WATCHDOG: transmit queue 0 timed out

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After some time the Ethernet adapter resets itself and a reboot is required 
to use it.
  It started to happen with 4.8.0 kernel.

  [22677.216049] [ cut here ]
  [22677.216067] WARNING: CPU: 1 PID: 0 at 
/build/linux-yFroJZ/linux-4.8.0/net/sched/sch_generic.c:316 
dev_watchdog+0x1ee/0x1f0
  [22677.216074] NETDEV WATCHDOG: enp2s0 (e1000e): transmit queue 0 timed out
  [22677.216076] Modules linked in: ipt_MASQUERADE nf_nat_masquerade_ipv4 
xfrm_user xfrm_algo iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 
xt_addrtype iptable_filter xt_conntrack nf_nat nf_conntrack br_netfilter bridge 
stp llc aufs bnep ccm snd_hrtimer zram nvidia(POE) btusb btrtl btbcm btintel 
bluetooth coretemp kvm irqbypass arc4 iwl3945 snd_hda_codec_conexant 
snd_hda_codec_generic iwlegacy input_leds snd_hda_intel joydev mac80211 
snd_hda_codec serio_raw snd_hda_core snd_hwdep snd_pcm pcmcia snd_seq_midi 
cfg80211 lpc_ich snd_seq_midi_event drm tifm_7xx1 snd_rawmidi yenta_socket 
snd_seq pcmcia_rsrc tifm_core snd_seq_device pcmcia_core snd_timer toshiba_acpi 
snd soundcore industrialio sparse_keymap toshiba_bluetooth shpchp wmi mac_hid 
binfmt_misc parport_pc ppdev lp parport ip_tables x_tables
  [22677.216181]  autofs4 btrfs xor raid6_pq uas usb_storage hid_generic usbhid 
hid psmouse firewire_ohci firewire_core sdhci_pci e1000e pata_acpi sdhci 
crc_itu_t ptp pps_core fjes video
  [22677.216215] CPU: 1 PID: 0 Comm: swapper/1 Tainted: P   OE   
4.8.0-26-generic #28-Ubuntu
  [22677.216218] Hardware name: TOSHIBA Satellite P100/Satellite P100, BIOS 
V4.80   11/12/20092
  [22677.216221]  d5b54967 866cf8be 00200286 f63a9e9c d53da625 f63a9ee0 
d5af19b8 f63a9ecc
  [22677.216232]  d5071b9a d5af197c f63a9f00  d5af19b8 013c 
d57268fe 013c
  [22677.216242]   f5658000 fb74 f63a9eec d5071c06 0009 
 f63a9ee0
  [22677.216252] Call Trace:
  [22677.216261]  [] dump_stack+0x58/0x73
  [22677.216267]  [] __warn+0xea/0x110
  [22677.216272]  [] ? dev_watchdog+0x1ee/0x1f0
  [22677.216276]  [] warn_slowpath_fmt+0x46/0x60
  [22677.216281]  [] dev_watchdog+0x1ee/0x1f0
  [22677.216287]  [] ? qdisc_rcu_free+0x40/0x40
  [22677.216293]  [] call_timer_fn+0x30/0x110
  [22677.216297]  [] ? qdisc_rcu_free+0x40/0x40
  [22677.216301]  [] ? qdisc_rcu_free+0x40/0x40
  [22677.216306]  [] run_timer_softirq+0x1dd/0x490
  [22677.216310]  [] ? rcu_report_qs_rnp+0x92/0x160
  [22677.216317]  [] __do_softirq+0xd7/0x245
  [22677.216331]  [] ? nmi+0x53/0x6d
  [22677.216333]  [] ? __irqentry_text_end+0x3/0x3
  [22677.216335]  [] ? __irqentry_text_end+0x3/0x3
  [22677.216337]  [] do_softirq_own_stack+0x28/0x30
  [22677.216338][] irq_exit+0xa5/0xb0
  [22677.216343]  [] smp_apic_timer_interrupt+0x38/0x50
  [22677.216344]  [] apic_timer_interrupt+0x34/0x3c
  [22677.216348]  [] ? cpuidle_enter_state+0x136/0x330
  [22677.216350]  [] cpuidle_enter+0x14/0x20
  [22677.216353]  [] call_cpuidle+0x2c/0x50
  [22677.216355]  [] cpu_startup_entry+0x281/0x320
  [22677.216358]  [] start_secondary+0x144/0x1a0
  [22677.216359] ---[ end trace 63b8fe6a0c6fd16b ]---
  [22677.216382] e1000e :02:00.0 enp2s0: Reset adapter unexpectedly
  [22686.433572] e1000e: enp2s0 NIC Link is Down
  [22687.952535] IPv6: ADDRCONF(NETDEV_UP): enp2s0: link is not ready
  [22688.304061] e1000e :02:00.0 enp2s0: MSI interrupt test failed, using 
legacy interrupt.
  [22688.304635] IPv6: ADDRCONF(NETDEV_UP): enp2s0: link is not ready
  --- 
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  konrad 3522 F pulseaudio
  CurrentDesktop: GNOME-Flashback:Unity
  DistroRelease: Ubuntu 16.10
  EcryptfsInUse: Yes
  MachineType: TOSHIBA Satellite P100
  NonfreeKernelModules: nvidia
  Package: linux (not installed)
  PccardctlIdent:
   Socket 0:
 no product info available
  PccardctlStatus:
   Socket 0:
 no card
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-26-generic 
root=UUID=4c307497-59d5-4242-b842-3afe0801f5b6 ro quiet splash
  ProcVersionSignature: Ubuntu 4.8.0-26.28-generic 4.8.0
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-26-generic N/A
   linux-backports-modules-4.8.0-26-generic  N/A
   linux-firmware

[Kernel-packages] [Bug 172937] Re: SQUASHFS error while booting from live cd

2016-11-18 Thread ethan.hsieh

I have also encountered this issue with a SanDisk USB 3.0 drive.
And, this workaround works for me.
http://forums.sandisk.com/t5/ratings/ratingdetailpage/message-uid/342584/rating-system/message_ratings

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

Title:
  SQUASHFS error while booting from live cd

Status in linux package in Ubuntu:
  Won't Fix
Status in linux package in Fedora:
  Won't Fix
Status in linux package in Mandriva:
  Invalid

Bug description:
  Some users have reported being unable to boot from the Ubuntu LiveCD,
  due to SquasFS errors like this:

  [  135.292409] SQUASHFS error: sb_bread failed reading block 0x9d7f3
  [  135.292411] SQUASHFS error: Unable to read fragment cache block [275faa28]
  [  135.292413] SQUASHFS error: Unable to read page, block 275faa28, size 23a7

  These errors can be due to a variety of reasons:

  * bad media (solution: try burning the iso image to a new disc)
  * a bad dvd drive (solution: if possible, try using a different cd/dvd 
drive)
  * bad memory modules (solution: use memtest86+ to check your memory)
  * a corrupted iso image (solution: run an md5 checksum, and if they don't 
match, download the iso image again)
  * an optical drive connected via SATA instead of PATA and running in 
Enhanced mode (solution: change the IDE configuration to "compatible" in the 
BIOS)

  This is all described in more detail here:
  https://help.ubuntu.com/community/SquashfsErrors

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/172937/+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 1640921] onibi (i386) - tests ran: 19, failed: 0

tests ran:  19, failed: 0;
  
http://kernel.ubuntu.com/testing/4.4.0-49.70-generic/onibi__4.4.0-49.70__2016-11-18_08-01-00/results-index.html

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

Title:
  linux: 4.4.0-49.70 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
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:
  In Progress
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 4.4.0-49.70 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
  derivative-trackers-created: 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/1640921/+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 1640621] onza (i386) - tests ran: 19, failed: 1

tests ran:  19, failed: 1;
  
http://kernel.ubuntu.com/testing/3.19.0-75.83~14.04.1-generic/onza__3.19.0-75.83~14.04.1__2016-11-18_07-27-00/results-index.html

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

Title:
  linux-lts-vivid: 3.19.0-75.83~14.04.1 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
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 verification-testing series:
  Fix Released
Status in linux-lts-vivid package in Ubuntu:
  Invalid
Status in linux-lts-vivid source package in Trusty:
  Confirmed

Bug description:
  This bug is for tracking the 3.19.0-75.83~14.04.1 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
  derivative-trackers-created: true
  kernel-stable-master-bug: 1640613
  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/1640621/+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 1634607] Re: kernel generates ACPI Exception: AE_NOT_FOUND, Evaluating _DOD incorrectly

2016-11-18 Thread Alex Hung

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

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

Title:
  kernel generates ACPI Exception: AE_NOT_FOUND, Evaluating _DOD
  incorrectly

Status in HWE Next:
  Fix Committed
Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Xenial:
  Fix Committed

Bug description:
  Many system supports hybrid graphics and its discrete VGA does not
  have any connectors and therefore has no _DOD method.  However, kernel
  assumes the control method, _DOD, is required.  As a result, an
  exception is thrown incorrectly.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1634607/+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 1641083] s2lp4 (s390x.LPAR) - tests ran: 18, failed: 0