date:20170111

This change was made by a bot.

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

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

Title:
  "Out of memory" errors after upgrade to 4.4.0-59

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I recently replaced some Xenial servers, and started experiencing "Out
  of memory" problems with the default kernel.

  We bake Amazon AMIs based on an official Ubuntu-provided image (ami-
  e6b58e85, in ap-southeast-2, from https://cloud-
  images.ubuntu.com/locator/ec2/).  Previous versions of our AMI
  included "4.4.0-57-generic", but the latest version picked up
  "4.4.0-59-generic" as part of a "dist-upgrade".

  Instances booted using the new AMI have been using more memory, and
  experiencing OOM issues - sometimes during boot, and sometimes a while
  afterwards.  An example from the system log is:

  [  130.113411] cloud-init[1560]: Cloud-init v. 0.7.8 running 'modules:final' 
at Wed, 11 Jan 2017 22:07:53 +. Up 29.28 seconds.
  [  130.124219] cloud-init[1560]: Cloud-init v. 0.7.8 finished at Wed, 11 Jan 
2017 22:09:35 +. Datasource DataSourceEc2.  Up 130.09 seconds
  [29871.137128] Out of memory: Kill process 2920 (ruby) score 107 or sacrifice 
child
  [29871.140816] Killed process 2920 (ruby) total-vm:675048kB, 
anon-rss:51184kB, file-rss:2164kB
  [29871.449209] Out of memory: Kill process 3257 (splunkd) score 97 or 
sacrifice child
  [29871.453282] Killed process 3258 (splunkd) total-vm:66272kB, 
anon-rss:6676kB, file-rss:0kB
  [29871.677910] Out of memory: Kill process 2647 (fluentd) score 51 or 
sacrifice child
  [29871.681872] Killed process 2647 (fluentd) total-vm:117944kB, 
anon-rss:23956kB, file-rss:1356kB

  I have a hunch that this may be related to the fix for
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1647400,
  introduced in linux (4.4.0-58.79).

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-59-generic 4.4.0-59.80
  ProcVersionSignature: User Name 4.4.0-59.80-generic 4.4.35
  Uname: Linux 4.4.0-59-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Jan 12 06:29 seq
   crw-rw 1 root audio 116, 33 Jan 12 06:29 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.1-0ubuntu2.4
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  Date: Thu Jan 12 06:38:45 2017
  Ec2AMI: ami-0f93966c
  Ec2AMIManifest: (unknown)
  Ec2AvailabilityZone: ap-southeast-2a
  Ec2InstanceType: t2.nano
  Ec2Kernel: unavailable
  Ec2Ramdisk: unavailable
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  MachineType: Xen HVM domU
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 cirrusdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-59-generic 
root=UUID=fb0fef08-f3c5-40bf-9776-f7ba00fe72be ro console=tty1 console=ttyS0
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-59-generic N/A
   linux-backports-modules-4.4.0-59-generic  N/A
   linux-firmware1.157.6
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/09/2016
  dmi.bios.vendor: Xen
  dmi.bios.version: 4.2.amazon
  dmi.chassis.type: 1
  dmi.chassis.vendor: Xen
  dmi.modalias: 
dmi:bvnXen:bvr4.2.amazon:bd12/09/2016:svnXen:pnHVMdomU:pvr4.2.amazon:cvnXen:ct1:cvr:
  dmi.product.name: HVM domU
  dmi.product.version: 4.2.amazon
  dmi.sys.vendor: Xen

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1655842/+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 1655842] [NEW] "Out of memory" errors after upgrade to 4.4.0-59

2017-01-11 Thread Mike Williams

Public bug reported:

I recently replaced some Xenial servers, and started experiencing "Out
of memory" problems with the default kernel.

We bake Amazon AMIs based on an official Ubuntu-provided image (ami-
e6b58e85, in ap-southeast-2, from https://cloud-
images.ubuntu.com/locator/ec2/).  Previous versions of our AMI included
"4.4.0-57-generic", but the latest version picked up "4.4.0-59-generic"
as part of a "dist-upgrade".

Instances booted using the new AMI have been using more memory, and
experiencing OOM issues - sometimes during boot, and sometimes a while
afterwards.  An example from the system log is:

[  130.113411] cloud-init[1560]: Cloud-init v. 0.7.8 running 'modules:final' at 
Wed, 11 Jan 2017 22:07:53 +. Up 29.28 seconds.
[  130.124219] cloud-init[1560]: Cloud-init v. 0.7.8 finished at Wed, 11 Jan 
2017 22:09:35 +. Datasource DataSourceEc2.  Up 130.09 seconds
[29871.137128] Out of memory: Kill process 2920 (ruby) score 107 or sacrifice 
child
[29871.140816] Killed process 2920 (ruby) total-vm:675048kB, anon-rss:51184kB, 
file-rss:2164kB
[29871.449209] Out of memory: Kill process 3257 (splunkd) score 97 or sacrifice 
child
[29871.453282] Killed process 3258 (splunkd) total-vm:66272kB, anon-rss:6676kB, 
file-rss:0kB
[29871.677910] Out of memory: Kill process 2647 (fluentd) score 51 or sacrifice 
child
[29871.681872] Killed process 2647 (fluentd) total-vm:117944kB, 
anon-rss:23956kB, file-rss:1356kB

I have a hunch that this may be related to the fix for
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1647400, introduced
in linux (4.4.0-58.79).

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: linux-image-4.4.0-59-generic 4.4.0-59.80
ProcVersionSignature: User Name 4.4.0-59.80-generic 4.4.35
Uname: Linux 4.4.0-59-generic x86_64
AlsaDevices:
 total 0
 crw-rw 1 root audio 116,  1 Jan 12 06:29 seq
 crw-rw 1 root audio 116, 33 Jan 12 06:29 timer
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
ApportVersion: 2.20.1-0ubuntu2.4
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
Date: Thu Jan 12 06:38:45 2017
Ec2AMI: ami-0f93966c
Ec2AMIManifest: (unknown)
Ec2AvailabilityZone: ap-southeast-2a
Ec2InstanceType: t2.nano
Ec2Kernel: unavailable
Ec2Ramdisk: unavailable
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
Lsusb: Error: command ['lsusb'] failed with exit code 1:
MachineType: Xen HVM domU
PciMultimedia:
 
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcFB: 0 cirrusdrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-59-generic 
root=UUID=fb0fef08-f3c5-40bf-9776-f7ba00fe72be ro console=tty1 console=ttyS0
RelatedPackageVersions:
 linux-restricted-modules-4.4.0-59-generic N/A
 linux-backports-modules-4.4.0-59-generic  N/A
 linux-firmware1.157.6
RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/09/2016
dmi.bios.vendor: Xen
dmi.bios.version: 4.2.amazon
dmi.chassis.type: 1
dmi.chassis.vendor: Xen
dmi.modalias: 
dmi:bvnXen:bvr4.2.amazon:bd12/09/2016:svnXen:pnHVMdomU:pvr4.2.amazon:cvnXen:ct1:cvr:
dmi.product.name: HVM domU
dmi.product.version: 4.2.amazon
dmi.sys.vendor: Xen

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


** Tags: amd64 apport-bug ec2-images 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/1655842

Title:
  "Out of memory" errors after upgrade to 4.4.0-59

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I recently replaced some Xenial servers, and started experiencing "Out
  of memory" problems with the default kernel.

  We bake Amazon AMIs based on an official Ubuntu-provided image (ami-
  e6b58e85, in ap-southeast-2, from https://cloud-
  images.ubuntu.com/locator/ec2/).  Previous versions of our AMI
  included "4.4.0-57-generic", but the latest version picked up
  "4.4.0-59-generic" as part of a "dist-upgrade".

  Instances booted using the new AMI have been using more memory, and
  experiencing OOM issues - sometimes during boot, and sometimes a while
  afterwards.  An example from the system log is:

  [  130.113411] cloud-init[1560]: Cloud-init v. 0.7.8 running 'modules:final' 
at Wed, 11 Jan 2017 22:07:53 +. Up 29.28 seconds.
  [  130.124219] cloud-init[1560]: Cloud-init v. 0.7.8 finished at Wed, 11 Jan 
2017 22:09:35 +. Datasource DataSourceEc2.  Up 130.09 seconds
  [29871.137128] Out of memory: Kill process 2920 (ruby) score 107 or sacrifice 
child
  [29871.140816] Killed process 2920 (ruby) total-vm:675048kB, 
anon-rss:51184kB, file-rss:2164kB
  [29871.449209] Out of memory: Kill process 3257

[Kernel-packages] [Bug 1645591] Re: Driver for Exar USB UART

2017-01-11 Thread Anthony Wong

** Changed in: hwe-next
   Status: Fix Committed => Fix Released

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

Title:
  Driver for Exar USB UART

Status in HWE Next:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Fix Released
Status in linux source package in Yakkety:
  Fix Released

Bug description:
  Driver can be found at
  https://www.exar.com/design-tools/software-drivers

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1645591/+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 1530405] Re: NMI watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [kerneloops:814]

2017-01-11 Thread Jimmy Pan

One problem for the method in #44, the fan very easily get spinning all
the time if nouveau is blacklisted. So I have the enable it. I don't
think this is a sensible workaround.

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

Title:
  NMI watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [kerneloops:814]

Status in linux package in Ubuntu:
  Triaged

Bug description:
  I'm using Ubuntu Xenial 16.04 and my computer (ASUS M32BF) will
  randomly freeze up, sometimes before the login screen, sometimes while
  I'm in the middle of using a program. This sometimes happens on the
  Wily 15.10 live cd as well, and on both kernel 4.3.0-2, and kernel
  4.2.0-22.

  Important part of log:

  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112129] NMI watchdog: BUG: soft 
lockup - CPU#0 stuck for 22s! [kerneloops:814]
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112134] Modules linked in: rfcomm 
bnep nls_iso8859_1 kvm_amd kvm eeepc_wmi asus_wmi crct10dif_pclmul 
sparse_keymap crc32_pclmul aesni_intel aes_x86_64 arc4 lrw gf128mul rtl8821ae 
glue_helper snd_hda_codec_realtek ablk_helper snd_hda_codec_generic 
snd_hda_codec_hdmi snd_hda_intel btcoexist snd_hda_codec rtl_pci snd_hda_core 
joydev input_leds snd_hwdep rtlwifi snd_pcm fam15h_power cryptd snd_seq_midi 
serio_raw snd_seq_midi_event snd_rawmidi mac80211 snd_seq snd_seq_device 
snd_timer cfg80211 btusb btrtl btbcm btintel bluetooth snd soundcore 
edac_mce_amd k10temp edac_core i2c_piix4 shpchp mac_hid parport_pc ppdev lp 
parport autofs4 hid_logitech_hidpp uas usb_storage hid_logitech_dj usbhid hid 
amdkfd amd_iommu_v2 radeon i2c_algo_bit ttm drm_kms_helper syscopyarea 
sysfillrect sysimgblt fb_sys_fops r8169 psmouse mii drm ahci libahci wmi fjes 
video
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112183] CPU: 0 PID: 814 Comm: 
kerneloops Not tainted 4.3.0-2-generic #11-Ubuntu
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112184] Hardware name: ASUSTeK 
COMPUTER INC. K30BF_M32BF_A_F_K31BF_6/K30BF_M32BF_A_F_K31BF_6, BIOS 0501 
07/09/2015
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112186] task: 88031146d400 
ti: 88030e838000 task.ti: 88030e838000
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112188] RIP: 
0010:[]  [] __do_softirq+0x76/0x250
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112194] RSP: 
0018:88031fc03f30  EFLAGS: 0202
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112196] RAX: 88030e83c000 
RBX:  RCX: 40400040
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112197] RDX:  
RSI: 613e RDI: 0380
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112198] RBP: 88031fc03f80 
R08: 0029f8fa1411 R09: 88031fc169f0
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112199] R10: 0020 
R11: 0004 R12: 88031fc169c0
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112201] R13: 88030df8e200 
R14:  R15: 0001
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112202] FS:  
7f6c266ac880() GS:88031fc0() knlGS:
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112203] CS:  0010 DS:  ES: 
 CR0: 80050033
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112205] CR2: 7ffef000bff8 
CR3: 00030f368000 CR4: 000406f0
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112206] Stack:
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112207]  404000401fc03f78 
88030e83c000 0121 8803000a
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112209]  00021fc0d640 
 88031fc169c0 88030df8e200
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112211]   
0001 88031fc03f90 81081d23
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112213] Call Trace:
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112215]   
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112219]  [] 
irq_exit+0xa3/0xb0
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.11]  [] 
smp_apic_timer_interrupt+0x42/0x50
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112225]  [] 
apic_timer_interrupt+0x82/0x90
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112226]   
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112230]  [] ? 
finish_task_switch+0x67/0x1c0
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112232]  [] 
__schedule+0x36c/0x980
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112234]  [] 
schedule+0x33/0x80
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112236]  [] 
do_nanosleep+0x6f/0xf0
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112239]  [] 
hrtimer_nanosleep+0xdc/0x1f0
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112241]  [] ? 
__hrtimer_init+0x90/0x90
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112243]  [] ? 
do_nanosleep+0x5a/0xf0
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112245]  [] 
SyS_nanosleep+0x7a/0x90
  Dec 31 19:13:12 COMPUTERNAME

[Kernel-packages] [Bug 1655825] Re: package linux-image-4.4.0-59-generic 4.4.0-59.80 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2

2017-01-11 Thread Eric J. Meyer

See note for fix.  Was a broken package.

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

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

Title:
  package linux-image-4.4.0-59-generic 4.4.0-59.80 failed to
  install/upgrade: subprocess installed post-installation script
  returned error exit status 2

Status in linux package in Ubuntu:
  Invalid

Bug description:
  Ubuntu 4.4.0-57.78-generic 4.4.35

  00:00.0 Host bridge [0600]: Intel Corporation Sky Lake Host Bridge/DRAM 
Registers [8086:1910] (rev 0a)
DeviceName:  WIFI
Subsystem: Intel Corporation Skylake Host Bridge/DRAM Registers 
[8086:2064]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- 

  00:02.0 VGA compatible controller [0300]: Intel Corporation Sky Lake 
Integrated Graphics [8086:193b] (rev 09) (prog-if 00 [VGA controller])
DeviceName:  CPU
Subsystem: Intel Corporation Skylake Integrated Graphics [8086:2064]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR-  [disabled]
Capabilities: [40] Vendor Specific Information: Len=0c 
Capabilities: [70] Express (v2) Root Complex Integrated Endpoint, MSI 00
DevCap: MaxPayload 128 bytes, PhantFunc 0
ExtTag- RBE+
DevCtl: Report errors: Correctable- Non-Fatal- Fatal- 
Unsupported-
RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop-
MaxPayload 128 bytes, MaxReadReq 128 bytes
DevSta: CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr- 
TransPend-
DevCap2: Completion Timeout: Not Supported, TimeoutDis-, LTR-, 
OBFF Not Supported
DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis-, LTR-, 
OBFF Disabled
Capabilities: [ac] MSI: Enable+ Count=1/1 Maskable- 64bit-
Address: fee00018  Data: 
Capabilities: [d0] Power Management version 2
Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA 
PME(D0-,D1-,D2-,D3hot-,D3cold-)
Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME-
Capabilities: [100 v1] #1b
Capabilities: [200 v1] Address Translation Service (ATS)
ATSCap: Invalidate Queue Depth: 00
ATSCtl: Enable-, Smallest Translation Unit: 00
Capabilities: [300 v1] #13
Kernel driver in use: i915_bpo
Kernel modules: i915_bpo

  00:08.0 System peripheral [0880]: Intel Corporation Sky Lake Gaussian Mixture 
Model [8086:1911]
Subsystem: Intel Corporation Skylake Gaussian Mixture Model [8086:2064]
Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- 
SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- Reset- FastB2B-
PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
Capabilities: [40] Express (v2) Root Port (Slot+), MSI 00
DevCap: MaxPayload 256 bytes, PhantFunc 0
ExtTag- RBE+
DevCtl: Report errors: Correctable- Non-Fatal- Fatal- 
Unsupported-
RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop-
MaxPayload 128 bytes, MaxReadReq 128 bytes
DevSta: CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr+ 
TransPend-
LnkCap: Port #1, Speed 8GT/s, Width x1, ASPM L0s L1, Exit 
Latency L0s unlimited, L1 <4us
ClockPM- Surprise- LLActRep+ BwNot+ ASPMOptComp+
LnkCtl: ASPM L0s L1 Enabled; RCB 64 bytes Disabled- CommClk-
ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt-
LnkSta: Speed 2.5GT/s, Width x0, TrErr- Train- SlotClk+ 
DLActive- BWMgmt- ABWMgmt-
SltCap: AttnBtn- PwrCtrl- MRL- AttnInd- PwrInd- HotPlug+ 
Surprise+
Slot #0, PowerLimit 0.000W; Interlock- NoCompl+
SltCtl: Enable: AttnBtn- PwrFlt- MRL- PresDet- CmdCplt- HPIrq- 
LinkChg-
Control: AttnInd Unknown, PwrInd Unknown, Power- 
Interlock-
SltSta: Status: AttnBtn- PowerFlt- MRL- CmdCplt- PresDet- 
Interlock-
Changed: MRL- PresDet- LinkState-
RootCtl: ErrCorrectable- ErrNon-Fatal- ErrFatal- PMEIntEna- 
CRSVisible-
RootCap: CRSVisible-
RootSta: PME ReqID , PMEStatus- PMEPending-
DevCap2: Completion Timeout: Range ABC, TimeoutDis+, LTR+, OBFF 
Via WAKE# ARIFwd+
DevCtl2: Completion Timeout:

[Kernel-packages] [Bug 1655825] Re: package linux-image-4.4.0-59-generic 4.4.0-59.80 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2

2017-01-11 Thread Eric J. Meyer

This turned out to be an issue with a broken package:

linux-image-4.4.0-59-generic

fixed with:

sudo apt remove linux-image-4.4.0-59-generic
sudo dpkg --configure -a
sudo apt install linux-image-4.4.0-59-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/1655825

Title:
  package linux-image-4.4.0-59-generic 4.4.0-59.80 failed to
  install/upgrade: subprocess installed post-installation script
  returned error exit status 2

Status in linux package in Ubuntu:
  Invalid

Bug description:
  Ubuntu 4.4.0-57.78-generic 4.4.35

  00:00.0 Host bridge [0600]: Intel Corporation Sky Lake Host Bridge/DRAM 
Registers [8086:1910] (rev 0a)
DeviceName:  WIFI
Subsystem: Intel Corporation Skylake Host Bridge/DRAM Registers 
[8086:2064]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- 

  00:02.0 VGA compatible controller [0300]: Intel Corporation Sky Lake 
Integrated Graphics [8086:193b] (rev 09) (prog-if 00 [VGA controller])
DeviceName:  CPU
Subsystem: Intel Corporation Skylake Integrated Graphics [8086:2064]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR-  [disabled]
Capabilities: [40] Vendor Specific Information: Len=0c 
Capabilities: [70] Express (v2) Root Complex Integrated Endpoint, MSI 00
DevCap: MaxPayload 128 bytes, PhantFunc 0
ExtTag- RBE+
DevCtl: Report errors: Correctable- Non-Fatal- Fatal- 
Unsupported-
RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop-
MaxPayload 128 bytes, MaxReadReq 128 bytes
DevSta: CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr- 
TransPend-
DevCap2: Completion Timeout: Not Supported, TimeoutDis-, LTR-, 
OBFF Not Supported
DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis-, LTR-, 
OBFF Disabled
Capabilities: [ac] MSI: Enable+ Count=1/1 Maskable- 64bit-
Address: fee00018  Data: 
Capabilities: [d0] Power Management version 2
Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA 
PME(D0-,D1-,D2-,D3hot-,D3cold-)
Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME-
Capabilities: [100 v1] #1b
Capabilities: [200 v1] Address Translation Service (ATS)
ATSCap: Invalidate Queue Depth: 00
ATSCtl: Enable-, Smallest Translation Unit: 00
Capabilities: [300 v1] #13
Kernel driver in use: i915_bpo
Kernel modules: i915_bpo

  00:08.0 System peripheral [0880]: Intel Corporation Sky Lake Gaussian Mixture 
Model [8086:1911]
Subsystem: Intel Corporation Skylake Gaussian Mixture Model [8086:2064]
Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- 
SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- Reset- FastB2B-
PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
Capabilities: [40] Express (v2) Root Port (Slot+), MSI 00
DevCap: MaxPayload 256 bytes, PhantFunc 0
ExtTag- RBE+
DevCtl: Report errors: Correctable- Non-Fatal- Fatal- 
Unsupported-
RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop-
MaxPayload 128 bytes, MaxReadReq 128 bytes
DevSta: CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr+ 
TransPend-
LnkCap: Port #1, Speed 8GT/s, Width x1, ASPM L0s L1, Exit 
Latency L0s unlimited, L1 <4us
ClockPM- Surprise- LLActRep+ BwNot+ ASPMOptComp+
LnkCtl: ASPM L0s L1 Enabled; RCB 64 bytes Disabled- CommClk-
ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt-
LnkSta: Speed 2.5GT/s, Width x0, TrErr- Train- SlotClk+ 
DLActive- BWMgmt- ABWMgmt-
SltCap: AttnBtn- PwrCtrl- MRL- AttnInd- PwrInd- HotPlug+ 
Surprise+
Slot #0, PowerLimit 0.000W; Interlock- NoCompl+
SltCtl: Enable: AttnBtn- PwrFlt- MRL- PresDet- CmdCplt- HPIrq- 
LinkChg-
Control: AttnInd Unknown, PwrInd Unknown, Power- 
Interlock-
SltSta: Status: AttnBtn- PowerFlt- MRL- CmdCplt- PresDet- 
Interlock-
Changed: MRL- PresDet- LinkState-
RootCtl: ErrCorrectable- ErrNon-Fatal- ErrFatal- PMEIntEna- 
CRSVisible-
RootCap: CRSVisible-
RootSta: PME ReqID , PMEStatus- PMEPending-
DevCap2: Completion

[Kernel-packages] [Bug 1655825] Re: package linux-image-4.4.0-59-generic 4.4.0-59.80 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2

2017-01-11 Thread Apport retracing service

** Tags removed: need-duplicate-check

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

Title:
  package linux-image-4.4.0-59-generic 4.4.0-59.80 failed to
  install/upgrade: subprocess installed post-installation script
  returned error exit status 2

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 4.4.0-57.78-generic 4.4.35

  00:00.0 Host bridge [0600]: Intel Corporation Sky Lake Host Bridge/DRAM 
Registers [8086:1910] (rev 0a)
DeviceName:  WIFI
Subsystem: Intel Corporation Skylake Host Bridge/DRAM Registers 
[8086:2064]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- 

  00:02.0 VGA compatible controller [0300]: Intel Corporation Sky Lake 
Integrated Graphics [8086:193b] (rev 09) (prog-if 00 [VGA controller])
DeviceName:  CPU
Subsystem: Intel Corporation Skylake Integrated Graphics [8086:2064]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR-  [disabled]
Capabilities: [40] Vendor Specific Information: Len=0c 
Capabilities: [70] Express (v2) Root Complex Integrated Endpoint, MSI 00
DevCap: MaxPayload 128 bytes, PhantFunc 0
ExtTag- RBE+
DevCtl: Report errors: Correctable- Non-Fatal- Fatal- 
Unsupported-
RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop-
MaxPayload 128 bytes, MaxReadReq 128 bytes
DevSta: CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr- 
TransPend-
DevCap2: Completion Timeout: Not Supported, TimeoutDis-, LTR-, 
OBFF Not Supported
DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis-, LTR-, 
OBFF Disabled
Capabilities: [ac] MSI: Enable+ Count=1/1 Maskable- 64bit-
Address: fee00018  Data: 
Capabilities: [d0] Power Management version 2
Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA 
PME(D0-,D1-,D2-,D3hot-,D3cold-)
Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME-
Capabilities: [100 v1] #1b
Capabilities: [200 v1] Address Translation Service (ATS)
ATSCap: Invalidate Queue Depth: 00
ATSCtl: Enable-, Smallest Translation Unit: 00
Capabilities: [300 v1] #13
Kernel driver in use: i915_bpo
Kernel modules: i915_bpo

  00:08.0 System peripheral [0880]: Intel Corporation Sky Lake Gaussian Mixture 
Model [8086:1911]
Subsystem: Intel Corporation Skylake Gaussian Mixture Model [8086:2064]
Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- 
SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- Reset- FastB2B-
PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
Capabilities: [40] Express (v2) Root Port (Slot+), MSI 00
DevCap: MaxPayload 256 bytes, PhantFunc 0
ExtTag- RBE+
DevCtl: Report errors: Correctable- Non-Fatal- Fatal- 
Unsupported-
RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop-
MaxPayload 128 bytes, MaxReadReq 128 bytes
DevSta: CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr+ 
TransPend-
LnkCap: Port #1, Speed 8GT/s, Width x1, ASPM L0s L1, Exit 
Latency L0s unlimited, L1 <4us
ClockPM- Surprise- LLActRep+ BwNot+ ASPMOptComp+
LnkCtl: ASPM L0s L1 Enabled; RCB 64 bytes Disabled- CommClk-
ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt-
LnkSta: Speed 2.5GT/s, Width x0, TrErr- Train- SlotClk+ 
DLActive- BWMgmt- ABWMgmt-
SltCap: AttnBtn- PwrCtrl- MRL- AttnInd- PwrInd- HotPlug+ 
Surprise+
Slot #0, PowerLimit 0.000W; Interlock- NoCompl+
SltCtl: Enable: AttnBtn- PwrFlt- MRL- PresDet- CmdCplt- HPIrq- 
LinkChg-
Control: AttnInd Unknown, PwrInd Unknown, Power- 
Interlock-
SltSta: Status: AttnBtn- PowerFlt- MRL- CmdCplt- PresDet- 
Interlock-
Changed: MRL- PresDet- LinkState-
RootCtl: ErrCorrectable- ErrNon-Fatal- ErrFatal- PMEIntEna- 
CRSVisible-
RootCap: CRSVisible-
RootSta: PME ReqID , PMEStatus- PMEPending-
DevCap2: Completion Timeout: Range ABC, TimeoutDis+, LTR+, OBFF 
Via WAKE# ARIFwd+
DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis-, LTR-, 
OBFF Disabled ARIFwd-

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

This change was made by a bot.

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

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

Title:
  package linux-image-4.4.0-59-generic 4.4.0-59.80 failed to
  install/upgrade: subprocess installed post-installation script
  returned error exit status 2

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 4.4.0-57.78-generic 4.4.35

  00:00.0 Host bridge [0600]: Intel Corporation Sky Lake Host Bridge/DRAM 
Registers [8086:1910] (rev 0a)
DeviceName:  WIFI
Subsystem: Intel Corporation Skylake Host Bridge/DRAM Registers 
[8086:2064]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- 

  00:02.0 VGA compatible controller [0300]: Intel Corporation Sky Lake 
Integrated Graphics [8086:193b] (rev 09) (prog-if 00 [VGA controller])
DeviceName:  CPU
Subsystem: Intel Corporation Skylake Integrated Graphics [8086:2064]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR-  [disabled]
Capabilities: [40] Vendor Specific Information: Len=0c 
Capabilities: [70] Express (v2) Root Complex Integrated Endpoint, MSI 00
DevCap: MaxPayload 128 bytes, PhantFunc 0
ExtTag- RBE+
DevCtl: Report errors: Correctable- Non-Fatal- Fatal- 
Unsupported-
RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop-
MaxPayload 128 bytes, MaxReadReq 128 bytes
DevSta: CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr- 
TransPend-
DevCap2: Completion Timeout: Not Supported, TimeoutDis-, LTR-, 
OBFF Not Supported
DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis-, LTR-, 
OBFF Disabled
Capabilities: [ac] MSI: Enable+ Count=1/1 Maskable- 64bit-
Address: fee00018  Data: 
Capabilities: [d0] Power Management version 2
Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA 
PME(D0-,D1-,D2-,D3hot-,D3cold-)
Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME-
Capabilities: [100 v1] #1b
Capabilities: [200 v1] Address Translation Service (ATS)
ATSCap: Invalidate Queue Depth: 00
ATSCtl: Enable-, Smallest Translation Unit: 00
Capabilities: [300 v1] #13
Kernel driver in use: i915_bpo
Kernel modules: i915_bpo

  00:08.0 System peripheral [0880]: Intel Corporation Sky Lake Gaussian Mixture 
Model [8086:1911]
Subsystem: Intel Corporation Skylake Gaussian Mixture Model [8086:2064]
Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- 
SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- Reset- FastB2B-
PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
Capabilities: [40] Express (v2) Root Port (Slot+), MSI 00
DevCap: MaxPayload 256 bytes, PhantFunc 0
ExtTag- RBE+
DevCtl: Report errors: Correctable- Non-Fatal- Fatal- 
Unsupported-
RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop-
MaxPayload 128 bytes, MaxReadReq 128 bytes
DevSta: CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr+ 
TransPend-
LnkCap: Port #1, Speed 8GT/s, Width x1, ASPM L0s L1, Exit 
Latency L0s unlimited, L1 <4us
ClockPM- Surprise- LLActRep+ BwNot+ ASPMOptComp+
LnkCtl: ASPM L0s L1 Enabled; RCB 64 bytes Disabled- CommClk-
ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt-
LnkSta: Speed 2.5GT/s, Width x0, TrErr- Train- SlotClk+ 
DLActive- BWMgmt- ABWMgmt-
SltCap: AttnBtn- PwrCtrl- MRL- AttnInd- PwrInd- HotPlug+ 
Surprise+
Slot #0, PowerLimit 0.000W; Interlock- NoCompl+
SltCtl: Enable: AttnBtn- PwrFlt- MRL- PresDet- CmdCplt- HPIrq- 
LinkChg-
Control: AttnInd Unknown, PwrInd Unknown, Power- 
Interlock-
SltSta: Status: AttnBtn- PowerFlt- MRL- CmdCplt- PresDet- 
Interlock-
Changed: MRL- PresDet- LinkState-
RootCtl: ErrCorrectable- ErrNon-Fatal- ErrFatal- PMEIntEna- 
CRSVisible-
RootCap: CRSVisible-
RootSta: PME ReqID , PMEStatus- PMEPending-
DevCap2: Completion Timeout: Range ABC, TimeoutDis+, LTR+, OBFF 
Via WAKE# ARIFwd+
DevCtl2: Completion Timeout: 50us to 50ms,

[Kernel-packages] [Bug 1655825] [NEW] package linux-image-4.4.0-59-generic 4.4.0-59.80 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2

2017-01-11 Thread Eric J. Meyer

Public bug reported:

Ubuntu 4.4.0-57.78-generic 4.4.35

00:00.0 Host bridge [0600]: Intel Corporation Sky Lake Host Bridge/DRAM 
Registers [8086:1910] (rev 0a)
DeviceName:  WIFI
Subsystem: Intel Corporation Skylake Host Bridge/DRAM Registers 
[8086:2064]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- 

00:02.0 VGA compatible controller [0300]: Intel Corporation Sky Lake Integrated 
Graphics [8086:193b] (rev 09) (prog-if 00 [VGA controller])
DeviceName:  CPU
Subsystem: Intel Corporation Skylake Integrated Graphics [8086:2064]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR-  [disabled]
Capabilities: [40] Vendor Specific Information: Len=0c 
Capabilities: [70] Express (v2) Root Complex Integrated Endpoint, MSI 00
DevCap: MaxPayload 128 bytes, PhantFunc 0
ExtTag- RBE+
DevCtl: Report errors: Correctable- Non-Fatal- Fatal- 
Unsupported-
RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop-
MaxPayload 128 bytes, MaxReadReq 128 bytes
DevSta: CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr- 
TransPend-
DevCap2: Completion Timeout: Not Supported, TimeoutDis-, LTR-, 
OBFF Not Supported
DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis-, LTR-, 
OBFF Disabled
Capabilities: [ac] MSI: Enable+ Count=1/1 Maskable- 64bit-
Address: fee00018  Data: 
Capabilities: [d0] Power Management version 2
Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA 
PME(D0-,D1-,D2-,D3hot-,D3cold-)
Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME-
Capabilities: [100 v1] #1b
Capabilities: [200 v1] Address Translation Service (ATS)
ATSCap: Invalidate Queue Depth: 00
ATSCtl: Enable-, Smallest Translation Unit: 00
Capabilities: [300 v1] #13
Kernel driver in use: i915_bpo
Kernel modules: i915_bpo

00:08.0 System peripheral [0880]: Intel Corporation Sky Lake Gaussian Mixture 
Model [8086:1911]
Subsystem: Intel Corporation Skylake Gaussian Mixture Model [8086:2064]
Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- 
SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- Reset- FastB2B-
PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
Capabilities: [40] Express (v2) Root Port (Slot+), MSI 00
DevCap: MaxPayload 256 bytes, PhantFunc 0
ExtTag- RBE+
DevCtl: Report errors: Correctable- Non-Fatal- Fatal- 
Unsupported-
RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop-
MaxPayload 128 bytes, MaxReadReq 128 bytes
DevSta: CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr+ 
TransPend-
LnkCap: Port #1, Speed 8GT/s, Width x1, ASPM L0s L1, Exit 
Latency L0s unlimited, L1 <4us
ClockPM- Surprise- LLActRep+ BwNot+ ASPMOptComp+
LnkCtl: ASPM L0s L1 Enabled; RCB 64 bytes Disabled- CommClk-
ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt-
LnkSta: Speed 2.5GT/s, Width x0, TrErr- Train- SlotClk+ 
DLActive- BWMgmt- ABWMgmt-
SltCap: AttnBtn- PwrCtrl- MRL- AttnInd- PwrInd- HotPlug+ 
Surprise+
Slot #0, PowerLimit 0.000W; Interlock- NoCompl+
SltCtl: Enable: AttnBtn- PwrFlt- MRL- PresDet- CmdCplt- HPIrq- 
LinkChg-
Control: AttnInd Unknown, PwrInd Unknown, Power- 
Interlock-
SltSta: Status: AttnBtn- PowerFlt- MRL- CmdCplt- PresDet- 
Interlock-
Changed: MRL- PresDet- LinkState-
RootCtl: ErrCorrectable- ErrNon-Fatal- ErrFatal- PMEIntEna- 
CRSVisible-
RootCap: CRSVisible-
RootSta: PME ReqID , PMEStatus- PMEPending-
DevCap2: Completion Timeout: Range ABC, TimeoutDis+, LTR+, OBFF 
Via WAKE# ARIFwd+
DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis-, LTR-, 
OBFF Disabled ARIFwd-
LnkCtl2: Target Link Speed: 8GT/s, EnterCompliance- SpeedDis-
 Transmit Margin: Normal Operating Range, 
EnterModifiedCompliance- ComplianceSOS-
 Compliance De-emphasis: -6dB
LnkSta2: Current De-emphasis Level: -3.5dB, 
EqualizationComplete-, EqualizationPhase1-
 EqualizationPhase2-, EqualizationPhase3-,

[Kernel-packages] [Bug 1649048] Re: "Power off" required for resume from hybrid-sleep

2017-01-11 Thread Steven Ward

I would like to start by apologizing to anyone who may have wasted
time/effort on resolving this non-existent bug; I promise that I was not
being intentionally misleading. I was finally able to find the root of
my issue and, as it turns out, the issue was not the new bug I reported
here but instead was a combination of the "resume from suspend" bug and
systemd ignoring my settings in /etc/systemd/logind.conf when an
external display is connected.

I have changed the status of this bug to "Invalid" for the reasons
stated above. Again, I am sorry for any time and/or effort that was
wasted resolving or monitoring an issue that was actually just my
misunderstanding of my own system.

- Steven

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

Title:
  "Power off" required for resume from hybrid-sleep

Status in linux package in Ubuntu:
  Invalid

Bug description:
  Due to issues with "waking from suspend", I have modified a few entries in 
/etc/systemd/logind.conf to use hybrid-sleep instead of suspend, namely 
'HandleSuspendKey=hybrid-sleep', 'HandleLidSwitch=hybrid-sleep' and 
'HandleLidSwitchDocked=hybrid-sleep'. On a few occasions now, I have closed my 
laptop lid while it is plugged it and when I return to it later, it does not 
resume on lifting the lid. The disk spins up and the fan runs as if the laptop 
was resuming but I am unable to do anything other than hold the power button 
down until it shuts down - much as I had to when I was having problems with 
suspend. When I hit the power button again and select the entry for Ubuntu in 
grub, the laptop boots to the login screen normally. When I log in, everything 
is just as it was when I originally closed the laptop's lid - basically 
"resuming" the way I had hoped. I do not believe that this is the intended 
behavior as I have had my computer resume from hybrid-sleep without powering it 
off in 16
 .04 and in 16.10 (I have not, that I know of, experienced this problem while 
on battery power). In case it is relevant, the current values of 'Suspend when 
inactive for' and 'When the lid closes' in Settings > Power are "Don't suspend" 
(for battery and plugged in) and "Suspend" (for battery and plugged in), 
respectively.
  I will attach the output from 'cat /proc/version_signature' and 'lspci -vnvn' 
but I would like to add that 'sudo lspci -vnvn' sent 'pcilib: sysfs_read_vpd: 
read failed: Input/output error' to stderr, which was not redirected to the log 
file.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: linux-image-4.8.0-30-generic 4.8.0-30.32
  ProcVersionSignature: Ubuntu 4.8.0-30.32-generic 4.8.6
  Uname: Linux 4.8.0-30-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  steven 4004 F pulseaudio
   /dev/snd/controlC0:  steven 4004 F pulseaudio
  CurrentDesktop: Unity
  Date: Sat Dec 10 22:06:19 2016
  HibernationDevice: RESUME=UUID=891e7a47-9f8c-4fc9-9fe3-fe5c88ef2147
  InstallationDate: Installed on 2016-11-23 (17 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  MachineType: LENOVO 20347
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-30-generic.efi.signed 
root=UUID=b40d7383-45c3-4885-a1df-0e534eb44fef ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-30-generic N/A
   linux-backports-modules-4.8.0-30-generic  N/A
   linux-firmware1.161
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/24/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 99CN21WW(V1.04)
  dmi.board.asset.tag: Std
  dmi.board.name: Lenovo Y40-70
  dmi.board.vendor: LENOVO
  dmi.board.version: 31900058Std
  dmi.chassis.asset.tag: Std
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo Y40-70
  dmi.modalias: 
dmi:bvnLENOVO:bvr99CN21WW(V1.04):bd03/24/2014:svnLENOVO:pn20347:pvrLenovoY40-70:rvnLENOVO:rnLenovoY40-70:rvr31900058Std:cvnLENOVO:ct10:cvrLenovoY40-70:
  dmi.product.name: 20347
  dmi.product.version: Lenovo Y40-70
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1649048/+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 1636034] Re: Kernel panic - not syncing: VFS: Unable to mount root fs

2017-01-11 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/1636034

Title:
  Kernel panic - not syncing: VFS: Unable to mount root fs

Status in linux package in Ubuntu:
  Expired

Bug description:
  Got kernel panic at boot and could not reach grub using shift. Found
  Bug #1547559, saw this comment by Jason Straight.

  "Stumbled across this today while searching for a fix for a PC running
  16.04 that this is happening on. I don't understand why, but editing
  /etc/default/grub to uncomment the line for graphical terminal fixed
  it. What that has to do with mounting root I don't know, but that was
  certainly the fix."

  "Uncommenting #GRUB_TERMINAL=console fixed it."

  Yes, it does. Not sure if this is related or not so new bug.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-45-generic 4.4.0-45.66
  ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21
  Uname: Linux 4.4.0-45-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  gilsr  2587 F pulseaudio
   /dev/snd/controlC1:  gilsr  2587 F pulseaudio
   /dev/snd/controlC0:  gilsr  2587 F pulseaudio
  CurrentDesktop: Unity
  Date: Sun Oct 23 19:53:47 2016
  HibernationDevice: RESUME=UUID=6b783c22-05f6-4b87-8d0b-5f23d003361b
  InstallationDate: Installed on 2016-10-08 (15 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  IwConfig:
   lono wireless extensions.
   
   eno1  no wireless extensions.
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.4.0-45-generic 
root=UUID=b69ab98a-b1e4-4612-a1b2-1cfb9f742265 ro rootflags=subvol=@ quiet 
splash
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-45-generic N/A
   linux-backports-modules-4.4.0-45-generic  N/A
   linux-firmware1.157.4
  RfKill:
   0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/01/2012
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: BHZ7710H.86A.0094.2012.1101.1115
  dmi.board.name: DZ77BH-55K
  dmi.board.vendor: Intel Corporation
  dmi.board.version: AAG39008-400
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrBHZ7710H.86A.0094.2012.1101.1115:bd11/01/2012:svn:pn:pvr:rvnIntelCorporation:rnDZ77BH-55K:rvrAAG39008-400:cvn:ct3:cvr:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1636034/+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 1639377] Re: Wacom touch screen does not recognize finger touch after upgrading

2017-01-11 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/1639377

Title:
  Wacom touch screen does not recognize finger touch after upgrading

Status in linux package in Ubuntu:
  Expired

Bug description:
  After upgrading from Trusty to Xenial, the touch screen does not
  recognize finger touch as input, pen and eraser are still recognized
  instead.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-45-generic 4.4.0-45.66
  ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21
  Uname: Linux 4.4.0-45-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  sergio 2759 F pulseaudio
  CurrentDesktop: Unity
  Date: Sat Nov  5 00:02:17 2016
  HibernationDevice: RESUME=UUID=4348ce50-e421-4055-b3e3-6725a62be18a
  InstallationDate: Installed on 2014-07-16 (842 days ago)
  InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 
20140417-06:05
  MachineType: LENOVO 3113D24
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-45-generic 
root=UUID=b4e39992-3a7c-490b-bbfd-949733cba18c ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-45-generic N/A
   linux-backports-modules-4.4.0-45-generic  N/A
   linux-firmware1.157.4
  RfKill:
   0: phy0: Wireless LAN
    Soft blocked: no
    Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: Upgraded to xenial on 2016-06-21 (136 days ago)
  dmi.bios.date: 10/11/2012
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 6QET70WW (1.40 )
  dmi.board.name: 3113D24
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: 100010202125
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr6QET70WW(1.40):bd10/11/2012:svnLENOVO:pn3113D24:pvrThinkPadX201Tablet:rvnLENOVO:rn3113D24:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 3113D24
  dmi.product.version: ThinkPad X201 Tablet
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1639377/+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 1655822] [NEW] bcmwl-kernel-source (not installed): bcmwl kernel module failed to build

2017-01-11 Thread subrata samanta

Public bug reported:

I didnot find the solution. please solve these issues

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: bcmwl-kernel-source (not installed)
ProcVersionSignature: Ubuntu 4.4.0-57.78-generic 4.4.35
Uname: Linux 4.4.0-57-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.4
Architecture: amd64
DKMSKernelVersion: 4.4.0-59-generic
Date: Thu Jan 12 09:36:10 2017
InstallationDate: Installed on 2016-10-09 (94 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
PackageVersion: (not installed)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.1
 apt  1.2.15ubuntu0.2
SourcePackage: bcmwl
Title: bcmwl-kernel-source (not installed): bcmwl kernel module failed to build
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package xenial

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

Title:
  bcmwl-kernel-source (not installed): bcmwl kernel module failed to
  build

Status in bcmwl package in Ubuntu:
  New

Bug description:
  I didnot find the solution. please solve these issues

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: bcmwl-kernel-source (not installed)
  ProcVersionSignature: Ubuntu 4.4.0-57.78-generic 4.4.35
  Uname: Linux 4.4.0-57-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.4
  Architecture: amd64
  DKMSKernelVersion: 4.4.0-59-generic
  Date: Thu Jan 12 09:36:10 2017
  InstallationDate: Installed on 2016-10-09 (94 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  PackageVersion: (not installed)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.15ubuntu0.2
  SourcePackage: bcmwl
  Title: bcmwl-kernel-source (not installed): bcmwl kernel module failed to 
build
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1655822/+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 1649048] Re: "Power off" required for resume from hybrid-sleep

2017-01-11 Thread Steven Ward

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

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

Title:
  "Power off" required for resume from hybrid-sleep

Status in linux package in Ubuntu:
  Invalid

Bug description:
  Due to issues with "waking from suspend", I have modified a few entries in 
/etc/systemd/logind.conf to use hybrid-sleep instead of suspend, namely 
'HandleSuspendKey=hybrid-sleep', 'HandleLidSwitch=hybrid-sleep' and 
'HandleLidSwitchDocked=hybrid-sleep'. On a few occasions now, I have closed my 
laptop lid while it is plugged it and when I return to it later, it does not 
resume on lifting the lid. The disk spins up and the fan runs as if the laptop 
was resuming but I am unable to do anything other than hold the power button 
down until it shuts down - much as I had to when I was having problems with 
suspend. When I hit the power button again and select the entry for Ubuntu in 
grub, the laptop boots to the login screen normally. When I log in, everything 
is just as it was when I originally closed the laptop's lid - basically 
"resuming" the way I had hoped. I do not believe that this is the intended 
behavior as I have had my computer resume from hybrid-sleep without powering it 
off in 16
 .04 and in 16.10 (I have not, that I know of, experienced this problem while 
on battery power). In case it is relevant, the current values of 'Suspend when 
inactive for' and 'When the lid closes' in Settings > Power are "Don't suspend" 
(for battery and plugged in) and "Suspend" (for battery and plugged in), 
respectively.
  I will attach the output from 'cat /proc/version_signature' and 'lspci -vnvn' 
but I would like to add that 'sudo lspci -vnvn' sent 'pcilib: sysfs_read_vpd: 
read failed: Input/output error' to stderr, which was not redirected to the log 
file.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: linux-image-4.8.0-30-generic 4.8.0-30.32
  ProcVersionSignature: Ubuntu 4.8.0-30.32-generic 4.8.6
  Uname: Linux 4.8.0-30-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  steven 4004 F pulseaudio
   /dev/snd/controlC0:  steven 4004 F pulseaudio
  CurrentDesktop: Unity
  Date: Sat Dec 10 22:06:19 2016
  HibernationDevice: RESUME=UUID=891e7a47-9f8c-4fc9-9fe3-fe5c88ef2147
  InstallationDate: Installed on 2016-11-23 (17 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  MachineType: LENOVO 20347
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-30-generic.efi.signed 
root=UUID=b40d7383-45c3-4885-a1df-0e534eb44fef ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-30-generic N/A
   linux-backports-modules-4.8.0-30-generic  N/A
   linux-firmware1.161
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/24/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 99CN21WW(V1.04)
  dmi.board.asset.tag: Std
  dmi.board.name: Lenovo Y40-70
  dmi.board.vendor: LENOVO
  dmi.board.version: 31900058Std
  dmi.chassis.asset.tag: Std
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo Y40-70
  dmi.modalias: 
dmi:bvnLENOVO:bvr99CN21WW(V1.04):bd03/24/2014:svnLENOVO:pn20347:pvrLenovoY40-70:rvnLENOVO:rnLenovoY40-70:rvr31900058Std:cvnLENOVO:ct10:cvrLenovoY40-70:
  dmi.product.name: 20347
  dmi.product.version: Lenovo Y40-70
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1649048/+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 1653796] Re: eSATA external drive not recognized by Ubuntu Studio

kernel-bug-exists-upstream

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

** Description changed:

  did a search for similar problems and found an old bug from earlier
  versions of Ubuntu: bug 153768.
  
  old bug report said to try some of these things, which I did..
  
  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-57-lowlatency 4.4.0-57.78
  ProcVersionSignature: Ubuntu 4.4.0-57.78-lowlatency 4.4.35
  Uname: Linux 4.4.0-57-lowlatency x86_64
  ApportVersion: 2.20.1-0ubuntu2.4
  Architecture: amd64
  AudioDevicesInUse:
-  USERPID ACCESS COMMAND
-  /dev/snd/controlC0:  Edward-admin   1721 F pulseaudio
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC0:  Edward-admin   1721 F pulseaudio
  CurrentDesktop: XFCE
  Date: Tue Jan  3 13:37:32 2017
  GvfsMonitorLog: Monitoring events. Press Ctrl+C to quit.
  HibernationDevice: RESUME=UUID=cd636119-7499-4207-a479-13ab3d7c7d28
  HotplugNewDevices:
-  
+ 
  HotplugNewMounts:
-  
+ 
  InstallationDate: Installed on 2016-12-19 (15 days ago)
  InstallationMedia: Ubuntu-Studio 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  JournalErrors:
-  Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] 
failed with exit code 1: Hint: You are currently not seeing messages from other 
users and the system.
-Users in the 'systemd-journal' group can see all messages. Pass -q to
-turn off this notice.
-  No journal files were opened due to insufficient permissions.
+  Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] 
failed with exit code 1: Hint: You are currently not seeing messages from other 
users and the system.
+    Users in the 'systemd-journal' group can see all messages. Pass -q to
+    turn off this notice.
+  No journal files were opened due to insufficient permissions.
  MachineType: Motherboard by ZOTAC ZBOX-CI320NANO series
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-57-lowlatency 
root=UUID=838e029d-694d-496b-b3ef-116bf1ff4afa ro quiet splash 
intel_idle.max_cstate=2 vt.handoff=7
  RelatedPackageVersions:
-  linux-restricted-modules-4.4.0-57-lowlatency N/A
-  linux-backports-modules-4.4.0-57-lowlatency  N/A
-  linux-firmware   1.157.6
+  linux-restricted-modules-4.4.0-57-lowlatency N/A
+  linux-backports-modules-4.4.0-57-lowlatency  N/A
+  linux-firmware   1.157.6
  SourcePackage: linux
  Symptom: storage
  UdevMonitorLog:
-  monitor will print the received events for:
-  UDEV - the event which udev sends out after rule processing
+  monitor will print the received events for:
+  UDEV - the event which udev sends out after rule processing
  UdisksMonitorLog:
-  Monitoring the udisks daemon. Press Ctrl+C to exit.
-  13:37:57.897: The udisks-daemon is running (name-owner :1.52).
+  Monitoring the udisks daemon. Press Ctrl+C to exit.
+  13:37:57.897: The udisks-daemon is running (name-owner :1.52).
  UpgradeStatus: No upgrade log present (probably fresh install)
  WifiSyslog:
-  
+ 
  dmi.bios.date: 07/16/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: B219P027
  dmi.board.asset.tag: N/A
  dmi.board.name: ZBOX-CI320NANO series
  dmi.board.vendor: ZOTAC
  dmi.board.version: Rev.00
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrB219P027:bd07/16/2015:svnMotherboardbyZOTAC:pnZBOX-CI320NANOseries:pvrRev.00:rvnZOTAC:rnZBOX-CI320NANOseries:rvrRev.00:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: ZBOX-CI320NANO series
  dmi.product.version: Rev.00
  dmi.sys.vendor: Motherboard by ZOTAC

** Summary changed:

- eSATA external drive not recognized by Ubuntu Studio
+ eSATA external drive not recognized by Ubuntu Studio 
kernel-bug-exists-upstream

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

Title:
  eSATA external drive not recognized by Ubuntu Studio kernel-bug-
  exists-upstream

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  did a search for similar problems and found an old bug from earlier
  versions of Ubuntu: bug 153768.

  old bug report said to try some of these things, which I did..

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-57-lowlatency 4.4.0-57.78
  ProcVersionSignature: Ubuntu 4.4.0-57.78-lowlatency 4.4.35
  Uname: Linux 4.4.0-57-lowlatency x86_64
  ApportVersion: 2.20.1-0ubuntu2.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  Edward-admin   1721 F pulseaudio
  CurrentDesktop: XFCE
  Date: Tue Jan  3 13:37:32 2017
  GvfsMonitorLog: Monitoring events. Press Ctrl+C to quit.
  HibernationDevice:

[Kernel-packages] [Bug 1653796] Re: eSATA external drive not recognized by Ubuntu Studio

possible progress here:

dmesg | grep -i "attached "
[3.045731] sd 0:0:0:0: Attached scsi generic sg0 type 0
[3.051706] sd 0:0:0:0: [sda] Attached SCSI disk

sda obviously my internal drive, which leaves that sg0 is my eSATA
drive?

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

Title:
  eSATA external drive not recognized by Ubuntu Studio

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  did a search for similar problems and found an old bug from earlier
  versions of Ubuntu: bug 153768.

  old bug report said to try some of these things, which I did..

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-57-lowlatency 4.4.0-57.78
  ProcVersionSignature: Ubuntu 4.4.0-57.78-lowlatency 4.4.35
  Uname: Linux 4.4.0-57-lowlatency x86_64
  ApportVersion: 2.20.1-0ubuntu2.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  Edward-admin   1721 F pulseaudio
  CurrentDesktop: XFCE
  Date: Tue Jan  3 13:37:32 2017
  GvfsMonitorLog: Monitoring events. Press Ctrl+C to quit.
  HibernationDevice: RESUME=UUID=cd636119-7499-4207-a479-13ab3d7c7d28
  HotplugNewDevices:
   
  HotplugNewMounts:
   
  InstallationDate: Installed on 2016-12-19 (15 days ago)
  InstallationMedia: Ubuntu-Studio 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  JournalErrors:
   Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] 
failed with exit code 1: Hint: You are currently not seeing messages from other 
users and the system.
 Users in the 'systemd-journal' group can see all messages. Pass -q to
 turn off this notice.
   No journal files were opened due to insufficient permissions.
  MachineType: Motherboard by ZOTAC ZBOX-CI320NANO series
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-57-lowlatency 
root=UUID=838e029d-694d-496b-b3ef-116bf1ff4afa ro quiet splash 
intel_idle.max_cstate=2 vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-57-lowlatency N/A
   linux-backports-modules-4.4.0-57-lowlatency  N/A
   linux-firmware   1.157.6
  SourcePackage: linux
  Symptom: storage
  UdevMonitorLog:
   monitor will print the received events for:
   UDEV - the event which udev sends out after rule processing
  UdisksMonitorLog:
   Monitoring the udisks daemon. Press Ctrl+C to exit.
   13:37:57.897: The udisks-daemon is running (name-owner :1.52).
  UpgradeStatus: No upgrade log present (probably fresh install)
  WifiSyslog:
   
  dmi.bios.date: 07/16/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: B219P027
  dmi.board.asset.tag: N/A
  dmi.board.name: ZBOX-CI320NANO series
  dmi.board.vendor: ZOTAC
  dmi.board.version: Rev.00
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrB219P027:bd07/16/2015:svnMotherboardbyZOTAC:pnZBOX-CI320NANOseries:pvrRev.00:rvnZOTAC:rnZBOX-CI320NANOseries:rvrRev.00:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: ZBOX-CI320NANO series
  dmi.product.version: Rev.00
  dmi.sys.vendor: Motherboard by ZOTAC

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1653796/+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 1646277] Re: Xenial server 16.04.x will have a black screen after PXE installation

2017-01-11 Thread Leo-Chen

That v4.4.35 was PASS

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

Title:
  Xenial server 16.04.x will have a black screen after PXE installation

Status in debian-installer package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  In Progress
Status in debian-installer source package in Xenial:
  Confirmed
Status in linux source package in Xenial:
  In Progress

Bug description:
  The display will keep black screen after install 16.04.x via PXE(need
  use "Ctrl+Alt+F1" to change to terminal 1, then can see text mode
  screen)

  Quanta team is installing Xenial server using PXE boot.   After the
  installation, the console will show a black screen.   Hitting ctl-
  alt-f1 displays the text mode screen OK.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/1646277/+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 1655437] Re: 16.04 fails to boot with kernel 4.4.0-22-generic

2017-01-11 Thread jeffrey leung

I ran apport-collect after booting up with the 4.4.0-21-generic kernel.
I was not able to boot into the OS with the 4.4.0-22-generic kernel to
run the command.

When boot fails and it drops to shell, it doesn't appear to be accepting
keyboard input. I found some old issues with USB drivers not being
installed yet but they are pretty old. Digging deeper into that
information to see if I can recover and boot into 16.04 with
4.4.0-22-generic kernel.

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

Title:
16.04 fails to boot with kernel 4.4.0-22-generic

Status in linux package in Ubuntu:
Confirmed

Bug description:
During ENIC driver development on our end, there was a mistake and the
driver was built on the 4.4.0-22-generic kernel but we intended it to
be on the inbox kernel with 16.04 which is 4.4.0-21-generic. So when
testing the ENIC driver, it required a kernel upgrade and afterwards
we found it wasn't able to boot due to some volume group issues it
appears from the error messages.

We fixed the driver issue on our end to target the correct inbox
kernel version and it's working fine. We also haven't seen any issues
with 16.04 and newer kernels. However, management is still concerned
about the issue with 16.04 xenial xerus at 4.4.0-22-generic kernel. Is
it possible to look into this issue? Or maybe would it be possible to
get that kernel version removed from the package so a customer doesn't
upgrade to that kernel after an offline install?

I am able to replicate the issue easily by doing an offline install of
16.04 so the kernel does not get automatically upgraded, then
upgrading to 4.4.0-22-generic and rebooting after install.

1. If I install 16.04 with auto partitioning, after updating the
kernel to 4.4.0-22-generic and rebooting, I see ubuntu-vg not found
errors. I’ve attached ubuntu.jpg for this.

2. If I install 16.04 with manual partitioning, I don’t see the vg not
found, but OS still fails to boot and goes to shell. I’ve attached
ubuntu2.jpg for this.

Thanks,
Jeff
---
ApportVersion: 2.20.1-0ubuntu2
Architecture: amd64
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq',
'/dev/snd/timer'] failed with exit code 1:
DistroRelease: Ubuntu 16.04
HibernationDevice: RESUME=UUID=545c0ff1-8be4-4ca3-95ad-7e971f832aba
InstallationDate: Installed on 2017-01-10 (0 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64
(20160420.1)
IwConfig:
enp138s0 no wireless extensions.

enp133s0 no wireless extensions.

lono wireless extensions.
Lsusb:
Bus 002 Device 003: ID 0624:0402 Avocent Corp. Cisco Virtual Keyboard and
Mouse
Bus 002 Device 002: ID 8087:8002 Intel Corp.
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 002: ID 8087:800a Intel Corp.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Cisco Systems Inc UCSB-B420-M4
Package: linux (not installed)
ProcEnviron:
LANGUAGE=en_US
TERM=xterm-256color
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcFB: 0 VESA VGA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic
root=UUID=9c7d131f-2177-40d2-8418-f8581a8d4ef5 ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
linux-restricted-modules-4.4.0-21-generic N/A
linux-backports-modules-4.4.0-21-generic N/A
linux-firmware1.157
RfKill:

Tags: xenial
Uname: Linux 4.4.0-21-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

_MarkForUpload: True
dmi.bios.date: 11/07/2016
dmi.bios.vendor: Cisco Systems, Inc.
dmi.bios.version: B420M4.3.1.2f.0.110720161154
dmi.board.name: UCSB-B420-M4
dmi.board.vendor: Cisco Systems Inc
dmi.board.version: 73-16458-06
dmi.chassis.type: 18
dmi.chassis.vendor: Cisco Systems Inc
dmi.chassis.version: 68-4777-02
dmi.modalias:
dmi:bvnCiscoSystems,Inc.:bvrB420M4.3.1.2f.0.110720161154:bd11/07/2016:svnCiscoSystemsInc:pnUCSB-B420-M4:pvr03:rvnCiscoSystemsInc:rnUCSB-B420-M4:rvr73-16458-06:cvnCiscoSystemsInc:ct18:cvr68-4777-02:
dmi.product.name: UCSB-B420-M4
dmi.product.version: 03
dmi.sys.vendor: Cisco Systems Inc

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1655437/+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 1491654] Re: Intel P3700 PCIe SSD string shows ''Unknown'' during Ubuntu 14.04 installation

2017-01-11 Thread Leo-Chen

Yes, The system can installed and got version.

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

Title:
  Intel P3700 PCIe SSD string shows ''Unknown'' during Ubuntu 14.04
  installation

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Trusty:
  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:
  Current Behavior
  ==
  1. Intel P3700 PCIe SSD string shows "Unknow" during Ubuntu 14.04 install.

  Reference Verification
  ==
  1. Which version of previous BIOS/BMC/HW passed/failed? 1st Test
  2. Which similar project/product passed/failed? NA

  Steps to reproduce the problem
  ==
  1. Install Intel P3700 PCIe SSD*2 and SAS 12G HDD*8 with LSI 3108 into SUT.
  2. Power on system and install Ubuntu 14.04.
  3. Intel P3700 PCIe SSD string shows "Unknown" during OS install.

  Expected Behavior
  ==
  1. Intel P3700 PCIe SSD string should not show "Unknown" during Ubuntu 14.04 
install.

  Pcie SSD config:HDD/SSD:Intel,SSDPE2MD016T4,PCI-e,1.6TB,Gen3

  Copied from private bug:
  https://bugs.launchpad.net/quantatw/+bug/1454965

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1491654/+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 1647400] Re: system freeze when swapping to encrypted swap partition

2017-01-11 Thread alex

I can confirm pre-mature OOM issues running 4.4.0-59; a downgrade back
to 4.4.0-57 completely fixes the problem.

The specific workload in this case was a build server
(http://concourse.ci) which makes heavy use of btrfs and runc
containers.

I will try to spend some time this week to make a more generic
reproduction case.

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

Title:
  system freeze when swapping to encrypted swap partition

Status in Ubuntu on IBM z Systems:
  Fix Released
Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Xenial:
  Fix Released

Bug description:
  == Comment: #0 - Bernd-Rainer Bresser  - 2016-12-05 
04:27:00 ==
  +++ This bug was initially created as a clone of Bug #147836 +++

  ---Problem Description---
  When the system is installed with encrypted swap partition the attempt to 
swap ends in a system freeze. No error, no dump, the system needs to be 
reloaded.
   
  Contact Information = Bernd-Rainer Bresser/Germany/IBM, Wen Yi AG 
Gao/China/IBM 
   
  ---uname output---
  Linux s38lp65 4.4.0-36-generic #55-Ubuntu SMP Thu Aug 11 18:05:09 UTC 2016 
s390x s390x s390x GNU/Linux
   
  Machine Type = z13 LPAR 
   
  ---System Hang---
   System is frozen. No error, no dump, the system needs to be reloaded.
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
   1. install a system with encrypted swap partition. This can be done using 
the installer or via manual updates to /etc/fstab and /etc/crypttab.

  2. Verify encrypted swap partition exists
   cryptsetup status kvmibm-swap
  /dev/mapper/kvmibm-swap is active and is in use.
type:PLAIN
cipher:  aes-xts-plain64:sha256
keysize: 256 bits
device:  /dev/dasda2
offset:  0 sectors
size:8388672 sectors
mode:read/write

  3. force swapping
  this can be done by a command like this (if the system has 8GB memory)
  dd if=/dev/zero of=/dev/null ibs=16k obs=8G count=2MB
   
  Stack trace output:
   no
   
  Oops output:
   no
   
  System Dump Location:
   
   
  *Additional Instructions for Bernd-Rainer Bresser/Germany/IBM, Wen Yi AG 
Gao/China/IBM: 
  -Attach sysctl -a output output to the bug.

  == Comment: #1 - Bernd-Rainer Bresser  - 2016-12-05 
04:33:24 ==
  - the problem was originally found on KVM for IBM z 1.1.3
  - test on Ubuntu 16.04.1 showed the same issue here
  - on KVM for IBM z 1.1.3 the problem could be solved/circumvented by reverting
 commit 564e81a57f9788b1475127012e0fd44e9049e342
Author: Tetsuo Handa 
Date:   Fri Feb 5 15:36:30 2016 -0800
  mm, vmstat: fix wrong WQ sleep when memory reclaim doesn't make 
any progress

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1647400/+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 1655476] ms10-35-mcdivittB0-kernel (arm64) - tests ran: 1, failed: 0

tests ran:   1, failed: 0;
  
http://kernel.ubuntu.com/testing/3.13.0-108.155-generic/ms10-35-mcdivittB0-kernel__3.13.0-108.155__2017-01-11_23-59-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/1655476

Title:
  linux: 3.13.0-108.155 -proposed tracker

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

Bug description:
  This bug is for tracking the 3.13.0-108.155 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: Uploaded

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1655476/+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 1655122] ms10-34-mcdivittB0-kernel (arm64) - tests ran: 64, failed: 2

tests ran:  64, failed: 2;
  
http://kernel.ubuntu.com/testing/4.9.0-12.13-generic/ms10-34-mcdivittB0-kernel__4.9.0-12.13__2017-01-11_23-22-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/1655122

Title:
  linux: 4.9.0-12.13 -proposed tracker

Status in Kernel Development Workflow:
  In Progress
Status in Kernel Development Workflow automated-testing series:
  Incomplete
Status in Kernel Development Workflow prepare-package series:
  Fix Released
Status in Kernel Development Workflow prepare-package-meta series:
  Fix Released
Status in Kernel Development Workflow prepare-package-signed series:
  Fix Released
Status in Kernel Development Workflow promote-to-proposed series:
  Fix Released
Status in Kernel Development Workflow promote-to-release series:
  New
Status in Kernel Development Workflow regression-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Zesty:
  Confirmed

Bug description:
  This bug is for tracking the 4.9.0-12.13 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-development-workflow/+bug/1655122/+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 1655476] onza (i386) - tests ran: 1, failed: 0

tests ran:   1, failed: 0;
  
http://kernel.ubuntu.com/testing/3.13.0-108.155-generic/onza__3.13.0-108.155__2017-01-11_23-48-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/1655476

Title:
  linux: 3.13.0-108.155 -proposed tracker

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

Bug description:
  This bug is for tracking the 3.13.0-108.155 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: Uploaded

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

tests ran:   2, failed: 0;
  
http://kernel.ubuntu.com/testing/4.9.0-12.13-generic/ms10-35-mcdivittB0-kernel__4.9.0-12.13__2017-01-11_23-37-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/1655122

Title:
  linux: 4.9.0-12.13 -proposed tracker

Status in Kernel Development Workflow:
  In Progress
Status in Kernel Development Workflow automated-testing series:
  Incomplete
Status in Kernel Development Workflow prepare-package series:
  Fix Released
Status in Kernel Development Workflow prepare-package-meta series:
  Fix Released
Status in Kernel Development Workflow prepare-package-signed series:
  Fix Released
Status in Kernel Development Workflow promote-to-proposed series:
  Fix Released
Status in Kernel Development Workflow promote-to-release series:
  New
Status in Kernel Development Workflow regression-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Zesty:
  Confirmed

Bug description:
  This bug is for tracking the 4.9.0-12.13 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-development-workflow/+bug/1655122/+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 1655476] modoc (ppc64el) - tests ran: 1, failed: 0

tests ran:   1, failed: 0;
  
http://kernel.ubuntu.com/testing/3.13.0-108.155-generic/modoc__3.13.0-108.155__2017-01-11_23-26-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/1655476

Title:
  linux: 3.13.0-108.155 -proposed tracker

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

Bug description:
  This bug is for tracking the 3.13.0-108.155 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: Uploaded

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1655476/+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 1655476] onza (amd64) - tests ran: 1, failed: 0

tests ran:   1, failed: 0;
  
http://kernel.ubuntu.com/testing/3.13.0-108.155-generic/onza__3.13.0-108.155__2017-01-11_23-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/1655476

Title:
  linux: 3.13.0-108.155 -proposed tracker

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

Bug description:
  This bug is for tracking the 3.13.0-108.155 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: Uploaded

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1655476/+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 1655122] ms10-35-mcdivittB0-kernel (arm64) - tests ran: 16, failed: 4

tests ran:  16, failed: 4;
  
http://kernel.ubuntu.com/testing/4.9.0-12.13-generic/ms10-35-mcdivittB0-kernel__4.9.0-12.13__2017-01-11_22-55-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/1655122

Title:
  linux: 4.9.0-12.13 -proposed tracker

Status in Kernel Development Workflow:
  In Progress
Status in Kernel Development Workflow automated-testing series:
  Incomplete
Status in Kernel Development Workflow prepare-package series:
  Fix Released
Status in Kernel Development Workflow prepare-package-meta series:
  Fix Released
Status in Kernel Development Workflow prepare-package-signed series:
  Fix Released
Status in Kernel Development Workflow promote-to-proposed series:
  Fix Released
Status in Kernel Development Workflow promote-to-release series:
  New
Status in Kernel Development Workflow regression-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Zesty:
  Confirmed

Bug description:
  This bug is for tracking the 4.9.0-12.13 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-development-workflow/+bug/1655122/+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 1655476] Re: linux: 3.13.0-108.155 -proposed tracker

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

** Changed in: kernel-sru-workflow/prepare-package
 Assignee: Canonical Kernel Team (canonical-kernel-team) => John Donnelly 
(jpdonnelly)

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

** Description changed:

  This bug is for tracking the 3.13.0-108.155 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 --
  derivative-trackers-created: true
  phase: Uploaded
+ kernel-stable-phase-changed:Wednesday, 11. January 2017 23:01 UTC
+ kernel-stable-phase:Uploaded

** Description changed:

  This bug is for tracking the 3.13.0-108.155 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: Uploaded
- kernel-stable-phase-changed:Wednesday, 11. January 2017 23:01 UTC
- kernel-stable-phase:Uploaded

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

Title:
  linux: 3.13.0-108.155 -proposed tracker

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

Bug description:
  This bug is for tracking the 3.13.0-108.155 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: Uploaded

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1655476/+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 1655122] ms10-34-mcdivittB0-kernel (arm64) - tests ran: 141, failed: 0

tests ran: 141, failed: 0;
  
http://kernel.ubuntu.com/testing/4.9.0-12.13-generic/ms10-34-mcdivittB0-kernel__4.9.0-12.13__2017-01-11_22-07-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/1655122

Title:
  linux: 4.9.0-12.13 -proposed tracker

Status in Kernel Development Workflow:
  In Progress
Status in Kernel Development Workflow automated-testing series:
  Incomplete
Status in Kernel Development Workflow prepare-package series:
  Fix Released
Status in Kernel Development Workflow prepare-package-meta series:
  Fix Released
Status in Kernel Development Workflow prepare-package-signed series:
  Fix Released
Status in Kernel Development Workflow promote-to-proposed series:
  Fix Released
Status in Kernel Development Workflow promote-to-release series:
  New
Status in Kernel Development Workflow regression-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Zesty:
  Confirmed

Bug description:
  This bug is for tracking the 4.9.0-12.13 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-development-workflow/+bug/1655122/+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 1551712] Re: Belkin Thunderbolt 2 Express Dock HD display port hot plug not supported.

** Attachment removed: "syslog_boot_with_thunderbolt_then_reseat"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1551712/+attachment/4802406/+files/syslog_boot_with_thunderbolt_then_reseat

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

Title:
  Belkin Thunderbolt 2 Express Dock HD display port hot plug not
  supported.

Status in linux package in Ubuntu:
  Invalid

Bug description:
  There are two problems when using this dock:

  1. When booted, connecting the dock only allows USB and Ethernet to work, it 
does not support HDMI or DisplayPort monitors
  2. When booted with the device connected, while the device works fine, 
reseating the dock causes no adapters to work (No USB, Ethernet, HDMI and 
DisplayPort)

  This makes this dock and other Thunderbolt docks unusable, because I
  can't hotplug it correctly.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: linux-image-4.2.0-30-generic 4.2.0-30.36
  ProcVersionSignature: Ubuntu 4.2.0-30.36-generic 4.2.8-ckt3
  Uname: Linux 4.2.0-30-generic x86_64
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  graingert   1560 F pulseaudio
   /dev/snd/controlC0:  graingert   1560 F pulseaudio
  CurrentDesktop: Unity
  Date: Tue Mar  1 12:42:39 2016
  InstallationDate: Installed on 2016-01-05 (55 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  MachineType: Apple Inc. MacBookPro12,1
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.2.0-30-generic.efi.signed 
root=UUID=665d68d7-0c44-48e6-9e4c-9496a5c21d21 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.2.0-30-generic N/A
   linux-backports-modules-4.2.0-30-generic  N/A
   linux-firmware1.149.3
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/26/2015
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: MBP121.88Z.0167.B15.1510261437
  dmi.board.name: Mac-E43C1C25D4880AD6
  dmi.board.vendor: Apple Inc.
  dmi.board.version: MacBookPro12,1
  dmi.chassis.type: 9
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-E43C1C25D4880AD6
  dmi.modalias: 
dmi:bvnAppleInc.:bvrMBP121.88Z.0167.B15.1510261437:bd10/26/2015:svnAppleInc.:pnMacBookPro12,1:pvr1.0:rvnAppleInc.:rnMac-E43C1C25D4880AD6:rvrMacBookPro12,1:cvnAppleInc.:ct9:cvrMac-E43C1C25D4880AD6:
  dmi.product.name: MacBookPro12,1
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.

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

tests ran:  11, failed: 2;
  
http://kernel.ubuntu.com/testing/4.9.0-12.13-generic/ms10-35-mcdivittB0-kernel__4.9.0-12.13__2017-01-11_19-27-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/1655122

Title:
  linux: 4.9.0-12.13 -proposed tracker

Status in Kernel Development Workflow:
  In Progress
Status in Kernel Development Workflow automated-testing series:
  Incomplete
Status in Kernel Development Workflow prepare-package series:
  Fix Released
Status in Kernel Development Workflow prepare-package-meta series:
  Fix Released
Status in Kernel Development Workflow prepare-package-signed series:
  Fix Released
Status in Kernel Development Workflow promote-to-proposed series:
  Fix Released
Status in Kernel Development Workflow promote-to-release series:
  New
Status in Kernel Development Workflow regression-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Zesty:
  Confirmed

Bug description:
  This bug is for tracking the 4.9.0-12.13 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-development-workflow/+bug/1655122/+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 1655071] onza (i386) - tests ran: 1, failed: 0

tests ran:   1, failed: 0;
  
http://kernel.ubuntu.com/testing/3.2.0-121.164-generic/onza__3.2.0-121.164__2017-01-11_22-22-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/1655071

Title:
  linux: 3.2.0-121.164 -proposed tracker

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

Bug description:
  This bug is for tracking the 3.2.0-121.164 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: Uploaded

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1655071/+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 1648873] Comment bridged from LTC Bugzilla

2017-01-11 Thread bugproxy

--- Comment From mauri...@br.ibm.com 2017-01-11 17:07 EDT---
*** Bug 150058 has been marked as a duplicate of this bug. ***

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

Title:
  Ubuntu 16.10 netboot install fails with "Oops: Exception in kernel
  mode, sig: 5 [#1] " (lpfc)

Status in debian-installer package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Fix Released
Status in debian-installer source package in Xenial:
  New
Status in linux source package in Xenial:
  Invalid
Status in debian-installer source package in Yakkety:
  New
Status in linux source package in Yakkety:
  Fix Released

Bug description:
  == Comment: #33 - Mauricio Faria De Oliveira - 2016-12-09 06:49:57 ==

  Hi Canonical,

  Can you please apply this patch [1] to 16.10 and 16.04.x HWE (4.8) ?
  It's fixes a regression introduced in 4.8.

  As you can see, it's in the SCSI maintainer (James Bottomley)'s
  'fixes' branch, but didn't make 4.9-rc8 (maybe he considered it late
  for this one).

  We have installer, boot, and post-boot problems due to this one.
  It'd be good if the netboot images for 16.04.x HWE kernel can get it too.

  Thank you,

  [1] scsi: lpfc: fix oops/BUG in lpfc_sli_ringtxcmpl_put() 
  
http://git.kernel.org/cgit/linux/kernel/git/jejb/scsi.git/commit/?h=fixes=2319f847a8910cff1d46c9b66aa1dd7cc3e836a9

  Historical context:

  == Comment: #0 - HARSHA THYAGARAJA - 2016-11-21 02:39:35 ==
  ---Problem Description---
  Ubuntu 16.10 netboot install fails with "Oops: Exception in kernel mode. " 
(kernel: 4.8.0-27)
   
  Machine Type = Power8 baremetal  
   
  ---boot type---
  QEMU direct boot kernel/initrd
   
  ---Kernel cmdline used to launch install---
  On a Power8 server,  Using kernel and initrd images, 

  netcfg/disable_dhcp=true netcfg/confirm_static=true 
netcfg/choose_interface=98:BE:94:00:4C:68 netcfg/get_ipaddress=9.47.67.159/20 
netcfg/get_gateway=9.47.79.254 netcfg/get_nameservers=
   
  ---Install repository type---
  Internet repository
   
  ---Install repository Location---
  
http://ports.ubuntu.com/ubuntu-ports/dists/yakkety/main/installer-ppc64el/current/images/netboot/ubuntu-installer/ppc64el/
   
  ---Point of failure---
  Other failure during installation (stage 1)

  == Comment: #1 - HARSHA THYAGARAJA - 2016-11-21 02:41:54 ==
  The netboot install fails and Call traces are seen at the Disk detection step.

  == Comment: #8 - Mauricio Faria De Oliveira - 2016-11-21 15:58:25 ==
  Finally got it.

  The assembly offset/code + the trap signal is due to this BUG_ON(),
  and the second condition triggered the trap.

  Checking why piocb is not NULL but piocb->vport is NULL.
  This might have happened in the lpfc_linkdown_port() path, in the stack trace.

  Would need a more readable console log (ie, dmesg, as requested in
  comments 5, 3) to help understanding it.

  --

  static int
  lpfc_sli_ringtxcmpl_put(struct lpfc_hba *phba, struct lpfc_sli_ring *pring,
  struct lpfc_iocbq *piocb)
  {
  lockdep_assert_held(>hbalock);

  BUG_ON(!piocb || !piocb->vport);
  <...>
  }

  [  226.147886] NIP [db7324c0]
  lpfc_sli_ringtxcmpl_put+0x48/0x120 [lpfc]

  0x2478 + 0x48 = 0x24c0 (tdnei; trap doubleword not equal immediate)

  2478 :
  <...>
  2498:   78 2b bf 7c mr  r31,r5 // r31 is *piocb (r5 is the 
3rd function parameter)
  249c:   78 1b 7d 7c mr  r29,r3
  24a0:   78 23 9e 7c mr  r30,r4
  24a4:   01 00 00 48 bl  24a4  
// probably converted at module load time to the call lockdep_assert_held()
  24a8:   00 00 00 60 nop
  24ac:   00 00 bf 2f cmpdi   cr7,r31,0 // compare piocb with 0. 
checking for NULL.
  24b0:   70 00 9e 41 beq cr7,2520 
 // if equal to zero, branch out. done w/ the  
former part of the OR check.
  24b4:   e8 00 3f e9 ld  r9,232(r31) // an offset of piocb. 
probably piocb->vport in the bug_on
  24b8:   74 00 29 7d cntlzd  r9,r9 // count leading zeroes. if r59 
is null (0), leading zeroes is 64 (binary: 0100_, bit 6 is 1, and 6 LSbs 
[bits 5-0] are 0)
  24bc:   82 d1 29 79 rldicl  r9,r9,58,6 // rotate left 58 (ie, 
those 6 LSbs are now MSbs, and that bit 6 from 64 was rotated in the register 
and is now bit 0, the LSb), now AND the 6 MSbs w/ 0-bits, and the all lower 
bits with 1-bits (ie, save the LSb). 
  24c0:   00 00 09 0b tdnei   r9,0 // trap if not equal to zero. 
(ie, the whole r9 was zero, with 64 leading/consecutive zeroes, then bit 6 is 
1, it becomes bit 0.. and since bit 0 is now 1, r9 is thus non-zero, and the 
trap triggers.)this checked the latter part of the OR.

To manage notifications about this bug go to:

Re: [Kernel-packages] [Bug 1655735] Re: Incompatible libdevmapper 1.02.136 (2016-11-05) and kernel driver (unknown version).

If you run `dmsetup ls` as non-root on amd64, you get an error that's
close:

% dmsetup ls
/dev/mapper/control: open failed: Permission denied
Failure to communicate with kernel device-mapper driver.
Incompatible libdevmapper 1.02.136 (2016-11-05) and kernel driver (unknown 
version).
Command failed

where as the failure in the log file says:

[K/dev/mapper/control: mknod failed: Operation not permitted
Failure to communicate with kernel device-mapper driver.
Check that device-mapper is available in the kernel.

If you run the same command as root on amd64, it works.

So my question is: despite having needs-root, is it somehow possible that
autopkgtest is running the armhf command as non-root, and the slightly
different error message is indicating that, or is it really not available when
run as root on armhf.

If you have an armhf device with an up-to-date Zesty, can you please
check?

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

Title:
  Incompatible libdevmapper 1.02.136 (2016-11-05) and kernel driver
  (unknown version).

Status in linux package in Ubuntu:
  Confirmed
Status in lvm2 package in Ubuntu:
  New
Status in multipath-tools package in Ubuntu:
  New

Bug description:
  There is a new Zesty regression on armhf, related to the autopkgtest
  for ubuntu-image.  Here's a log of a recent run:

  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
  /autopkgtest-zesty/zesty/armhf/u/ubuntu-
  image/20170111_171929_431b1@/log.gz

  Scroll to the bottom and you see this:

  Incompatible libdevmapper 1.02.136 (2016-11-05) and kernel driver (unknown 
version).
  device mapper prerequisites not met
  /dev/mapper/control: mknod failed: Operation not permitted
  Failure to communicate with kernel device-mapper driver.
  Check that device-mapper is available in the kernel.
  Incompatible libdevmapper 1.02.136 (2016-11-05) and kernel driver (unknown 
version).
  device mapper prerequisites not met

  Don't be misled by the gadget.yamls which name different
  architectures.  ubuntu-image should be able to build a disk image for
  any architecture on any architecture.

  What this test does is build the image, then run kpartx to map the
  partitions in the image, and then mount the partitions.  It doesn't do
  anything other than ensure that the partitions can be mounted, and
  this is where it's failing.

  This test succeeds on amd64, i386, and ppc64el.  It's never passed on
  s390x so that's not a regression.  It *used* to pass on armhf even on
  Zesty, but the recent upload of 0.13+17.10ubuntu2 displays the
  regression.

  I will bugtask this to libdevmapper and kpartx since it's possibly a
  bug in one of those packages (though I still suspect the kernel).

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: linux-image-4.9.0-11-generic 4.9.0-11.12
  ProcVersionSignature: Ubuntu 4.9.0-11.12-generic 4.9.0
  Uname: Linux 4.9.0-11-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair nvidia_uvm nvidia_drm 
nvidia_modeset nvidia
  ApportVersion: 2.20.4-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  barry  5414 F pulseaudio
   /dev/snd/controlC0:  barry  5414 F pulseaudio
  CurrentDesktop: Unity
  Date: Wed Jan 11 13:10:30 2017
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=8cc96f00-242f-42c6-bdb9-72db178f8864
  InstallationDate: Installed on 2016-01-22 (355 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160117)
  MachineType: Gigabyte Technology Co., Ltd. Z170X-UD5
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.9.0-11-generic 
root=UUID=d03718f1-9983-4b07-a942-1b42fe8352ec ro
  RelatedPackageVersions:
   linux-restricted-modules-4.9.0-11-generic N/A
   linux-backports-modules-4.9.0-11-generic  N/A
   linux-firmware1.162
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/24/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F2
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z170X-UD5-CF
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF2:bd07/24/2015:svnGigabyteTechnologyCo.,Ltd.:pnZ170X-UD5:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ170X-UD5-CF:rvrx.x:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: Z170X-UD5
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

To manage notifications about this bug go to:

[Kernel-packages] [Bug 1523178] Re: 1217:8520 [Dell Latitude E7450] O2 Micro, SD/MMC Card Reader doesn't work

Blackgr, to keep this relevant to upstream, one would want to
periodically check for, and test the latest mainline kernel (now
4.10-rc3) as it is released.

Could you please advise?

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

Title:
  1217:8520 [Dell Latitude E7450] O2 Micro, SD/MMC Card Reader doesn't
  work

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Under ubuntu 15.10 I can't use my Sandisk ultra 64GB microSD (with a
  SD card adapter) with the built in SD card reader. I seem to be
  getting the following errors.

  [ 1268.126602] sdhci: Timeout waiting for Buffer Read Ready interrupt during 
tuning procedure, falling back to fixed sampling clock
  [ 1268.128381] mmc0: tuning execution failed
  [ 1268.128386] mmc0: error -5 whilst initialising SD card
  [ 1268.554319] sdhci: Timeout waiting for Buffer Read Ready interrupt during 
tuning procedure, falling back to fixed sampling clock
  [ 1268.556098] mmc0: tuning execution failed
  [ 1268.556103] mmc0: error -5 whilst initialising SD card
  [ 1268.993995] sdhci: Timeout waiting for Buffer Read Ready interrupt during 
tuning procedure, falling back to fixed sampling clock
  [ 1268.995778] mmc0: tuning execution failed
  [ 1268.995786] mmc0: error -5 whilst initialising SD card
  [ 1269.453666] sdhci: Timeout waiting for Buffer Read Ready interrupt during 
tuning procedure, falling back to fixed sampling clock
  [ 1269.455449] mmc0: tuning execution failed
  [ 1269.455458] mmc0: error -5 whilst initialising SD card

  It was working fine under vivid with kernel 3.19.

  Went through all the kernels from 3.19 to 4.2
  (http://kernel.ubuntu.com/~kernel-ppa/) and found out that until
  4.1.8-040108-generic the SD card reader would play fine and only after
  I put 4.1.9 and on I started getting the errors.

  WORKAROUND: rmmod sdhci sdhci_pci sdhci_acpi
  modprobe sdhci debug_quirks2="0x1"
  modprobe sdhci_pci

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: linux-image-4.2.0-19-generic 4.2.0-19.23
  ProcVersionSignature: Ubuntu 4.2.0-19.23-generic 4.2.6
  Uname: Linux 4.2.0-19-generic x86_64
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  alex   1606 F pulseaudio
   /dev/snd/controlC0:  alex   1606 F pulseaudio
   /dev/snd/controlC1:  alex   1606 F pulseaudio
  CurrentDesktop: Unity
  Date: Sun Dec  6 01:40:18 2015
  HibernationDevice: RESUME=UUID=acf75838-59f9-4461-9fe4-e9bdf33b28be
  InstallationDate: Installed on 2015-10-27 (38 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  MachineType: Dell Inc. Latitude E7450
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-19-generic 
root=UUID=c654e4bc-b0e1-4a85-844f-99f068b2efff ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.2.0-19-generic N/A
   linux-backports-modules-4.2.0-19-generic  N/A
   linux-firmware1.149.3
  SourcePackage: linux
  UpgradeStatus: Upgraded to wily on 2015-11-04 (31 days ago)
  dmi.bios.date: 10/28/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A08
  dmi.board.name: 0R1VJD
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA08:bd10/28/2015:svnDellInc.:pnLatitudeE7450:pvr:rvnDellInc.:rn0R1VJD: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/1523178/+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 1655071] onza (amd64) - tests ran: 1, failed: 0

tests ran:   1, failed: 0;
  
http://kernel.ubuntu.com/testing/3.2.0-121.164-generic/onza__3.2.0-121.164__2017-01-11_22-00-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/1655071

Title:
  linux: 3.2.0-121.164 -proposed tracker

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

Bug description:
  This bug is for tracking the 3.2.0-121.164 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: Uploaded

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1655071/+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 1655735] Re: Incompatible libdevmapper 1.02.136 (2016-11-05) and kernel driver (unknown version).

Found this older bug:
https://bugs.launchpad.net/ubuntu/+source/devmapper/+bug/105623

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

Title:
  Incompatible libdevmapper 1.02.136 (2016-11-05) and kernel driver
  (unknown version).

Status in linux package in Ubuntu:
  Confirmed
Status in lvm2 package in Ubuntu:
  New
Status in multipath-tools package in Ubuntu:
  New

Bug description:
  There is a new Zesty regression on armhf, related to the autopkgtest
  for ubuntu-image.  Here's a log of a recent run:

  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
  /autopkgtest-zesty/zesty/armhf/u/ubuntu-
  image/20170111_171929_431b1@/log.gz

  Scroll to the bottom and you see this:

  Incompatible libdevmapper 1.02.136 (2016-11-05) and kernel driver (unknown 
version).
  device mapper prerequisites not met
  /dev/mapper/control: mknod failed: Operation not permitted
  Failure to communicate with kernel device-mapper driver.
  Check that device-mapper is available in the kernel.
  Incompatible libdevmapper 1.02.136 (2016-11-05) and kernel driver (unknown 
version).
  device mapper prerequisites not met

  Don't be misled by the gadget.yamls which name different
  architectures.  ubuntu-image should be able to build a disk image for
  any architecture on any architecture.

  What this test does is build the image, then run kpartx to map the
  partitions in the image, and then mount the partitions.  It doesn't do
  anything other than ensure that the partitions can be mounted, and
  this is where it's failing.

  This test succeeds on amd64, i386, and ppc64el.  It's never passed on
  s390x so that's not a regression.  It *used* to pass on armhf even on
  Zesty, but the recent upload of 0.13+17.10ubuntu2 displays the
  regression.

  I will bugtask this to libdevmapper and kpartx since it's possibly a
  bug in one of those packages (though I still suspect the kernel).

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: linux-image-4.9.0-11-generic 4.9.0-11.12
  ProcVersionSignature: Ubuntu 4.9.0-11.12-generic 4.9.0
  Uname: Linux 4.9.0-11-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair nvidia_uvm nvidia_drm 
nvidia_modeset nvidia
  ApportVersion: 2.20.4-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  barry  5414 F pulseaudio
   /dev/snd/controlC0:  barry  5414 F pulseaudio
  CurrentDesktop: Unity
  Date: Wed Jan 11 13:10:30 2017
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=8cc96f00-242f-42c6-bdb9-72db178f8864
  InstallationDate: Installed on 2016-01-22 (355 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160117)
  MachineType: Gigabyte Technology Co., Ltd. Z170X-UD5
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.9.0-11-generic 
root=UUID=d03718f1-9983-4b07-a942-1b42fe8352ec ro
  RelatedPackageVersions:
   linux-restricted-modules-4.9.0-11-generic N/A
   linux-backports-modules-4.9.0-11-generic  N/A
   linux-firmware1.162
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/24/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F2
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z170X-UD5-CF
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF2:bd07/24/2015:svnGigabyteTechnologyCo.,Ltd.:pnZ170X-UD5:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ170X-UD5-CF:rvrx.x:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: Z170X-UD5
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1655735/+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 1648388] Re: Install Ubuntu16.04 in RAID1 created by Intel RSTe and the system hangs while rebooting

Lo, to keep this relevant to upstream, one would want to periodically
check for, and test the latest mainline kernel (now 4.10-rc3) as it is
released.

Could you please advise?

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

Title:
  Install Ubuntu16.04 in RAID1 created by Intel RSTe and the system
  hangs while rebooting

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Install Ubuntu16.04 in RAID1 created by Intel RSTe no matter legacy mode or 
UEFI mode.
  System hangs while rebooting

  Not found the issue in RAID0
  No issue on Ubuntu14.04
  Driver-OS inbox support

  Below as error messages
  ===
  INFO:  task systemd-shutdow:1 blocked for more than 120 seconds.
  Not tainted 4.4.0-21-generic #37-Ubuntu
  "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.

  INFO:  task  jbd2/md126p2-8:1732 blocked for more than 120 seconds.
  Not tainted 4.4.0-21-generic #37-Ubuntu
  "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.

  INFO:  task ext4lazyinit:1873 blocked for more than 120 seconds.
  Not tainted 4.4.0-21-generic #37-Ubuntu
  "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.

  INFO:  task kworker/u66:4:3139 blocked for more than 120 seconds.
  Not tainted 4.4.0-21-generic #37-Ubuntu
  "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
  ===

  WORKAROUND: edit /etc/sysctl.conf with follow commands and the system don't 
hang while rebooting:
  vm.dirty_background_ratio=5
  vm.dirty_ratio=10
  kernel.panic=3
  kernel.hung_task_panic=1
  kernel.hung_task_timeout_secs=30

  ---
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=f578df47-a1b8-4e66-bd37-904f943eb01b
  InstallationDate: Installed on 2016-12-15 (10 days ago)
  InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.3)
  MachineType: Dell DCS6430G
  Package: linux (not installed)
  ProcEnviron:
   LANGUAGE=en
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic.efi.signed 
root=UUID=bc552762-1955-44b8-a83e-2a414f0e0bd1 ro
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-21-generic N/A
   linux-backports-modules-4.4.0-21-generic  N/A
   linux-firmware1.157
  RfKill:

  Tags:  xenial
  Uname: Linux 4.4.0-21-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

  _MarkForUpload: True
  dmi.bios.date: 03/22/2016
  dmi.bios.vendor: Dell
  dmi.bios.version: 2.0.3
  dmi.board.name: 038VV0
  dmi.board.vendor: Dell
  dmi.board.version: X01
  dmi.chassis.type: 23
  dmi.chassis.vendor: Dell
  dmi.modalias: 
dmi:bvnDell:bvr2.0.3:bd03/22/2016:svnDell:pnDCS6430G:pvr:rvnDell:rn038VV0:rvrX01:cvnDell:ct23:cvr:
  dmi.product.name: DCS6430G
  dmi.sys.vendor: Dell

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1648388/+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 1655122] ms10-34-mcdivittB0-kernel (arm64) - tests ran: 36, failed: 0

tests ran:  36, failed: 0;
  
http://kernel.ubuntu.com/testing/4.9.0-12.13-generic/ms10-34-mcdivittB0-kernel__4.9.0-12.13__2017-01-11_20-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/1655122

Title:
  linux: 4.9.0-12.13 -proposed tracker

Status in Kernel Development Workflow:
  In Progress
Status in Kernel Development Workflow automated-testing series:
  Incomplete
Status in Kernel Development Workflow prepare-package series:
  Fix Released
Status in Kernel Development Workflow prepare-package-meta series:
  Fix Released
Status in Kernel Development Workflow prepare-package-signed series:
  Fix Released
Status in Kernel Development Workflow promote-to-proposed series:
  Fix Released
Status in Kernel Development Workflow promote-to-release series:
  New
Status in Kernel Development Workflow regression-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Zesty:
  Confirmed

Bug description:
  This bug is for tracking the 4.9.0-12.13 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-development-workflow/+bug/1655122/+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 1654214] Re: Belkin Thunderbolt 2 Express Dock HD display port hot plug not supported.

dunk, the issue you are reporting is an upstream one. Could you please
report this problem following the instructions verbatim at
https://wiki.ubuntu.com/Bugs/Upstream/kernel to the appropriate mailing
list (TO Andreas Noever CC linux-kernel )?

Please provide a direct URL to your post to the mailing list when it
becomes available so that it may be tracked.

Thank you for your help.

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

** Description changed:

- MachineType: Apple Inc. MacBookPro12,5
Peripheral: Belkin Thunderbolt 2 Express Dock HD. Model: F4U085

- [Text copied from bug/1551712]
- 1. When booted without the dock connected, connecting the dock only allows
USB and Ethernet to work, it does not support HDMI or DisplayPort monitors.
Re-seating the dock from here does not stop USB and Ethernet from working.
+ 1. When booted without the dock connected, connecting the dock only
+ allows USB and Ethernet to work, it does not support HDMI or DisplayPort
+ monitors. Re-seating the dock from here does not stop USB and Ethernet
+ from working.

2. When booted with the device connected, while the device works fine,
reseating the dock causes no adapters to work (No USB, Ethernet, HDMI
and DisplayPort)

-
This bug was generated with the Thunderbolt IO expander connected at boot
time and therefore all IO is working as intended.
- Also (manually) attached is a copy of syslog, lsmod and lspci where the dock
is removed then re-attached. (search for the annotation "Removing Thunderbolt"
and "Inserting Thunderbolt".)
+ Also (manually) attached is a copy of syslog, lsmod and lspci where the dock
is removed then re-attached.

The 3rd state where the system is booted without the doc is not
accounted for in the attached logs.
-
- Please let me know if you want any more information.

ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: linux-image-4.8.0-32-generic 4.8.0-32.34
ProcVersionSignature: Ubuntu 4.8.0-32.34-generic 4.8.11
Uname: Linux 4.8.0-32-generic x86_64
ApportVersion: 2.20.3-0ubuntu8.2
Architecture: amd64
AudioDevicesInUse:
- USERPID ACCESS COMMAND
- /dev/snd/controlC3: duncan 2524 F pulseaudio
- /dev/snd/controlC2: duncan 2524 F pulseaudio
- /dev/snd/controlC0: duncan 2524 F pulseaudio
- /dev/snd/controlC1: duncan 2524 F pulseaudio
+ USERPID ACCESS COMMAND
+ /dev/snd/controlC3: duncan 2524 F pulseaudio
+ /dev/snd/controlC2: duncan 2524 F pulseaudio
+ /dev/snd/controlC0: duncan 2524 F pulseaudio
+ /dev/snd/controlC1: duncan 2524 F pulseaudio
CurrentDesktop: Unity
Date: Thu Jan 5 10:18:15 2017
EcryptfsInUse: Yes
HibernationDevice: RESUME=UUID=33476504-147f-4970-8a3b-969e4dac63c9
InstallationDate: Installed on 2016-12-30 (5 days ago)
InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
MachineType: Apple Inc. MacBookPro11,5
ProcFB: 0 radeondrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-32-generic.efi.signed
root=UUID=ae7e8674-a8e6-4de5-a469-a0ae717af319 ro libata.force=noncq quiet
splash vt.handoff=7
RelatedPackageVersions:
- linux-restricted-modules-4.8.0-32-generic N/A
- linux-backports-modules-4.8.0-32-generic N/A
- linux-firmware1.161.1
+ linux-restricted-modules-4.8.0-32-generic N/A
+ linux-backports-modules-4.8.0-32-generic N/A
+ linux-firmware1.161.1
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 02/15/2016
dmi.bios.vendor: Apple Inc.
dmi.bios.version: MBP114.88Z.0172.B09.1602151732
dmi.board.name: Mac-06F11F11946D27C5
dmi.board.vendor: Apple Inc.
dmi.board.version: MacBookPro11,5
dmi.chassis.type: 9
dmi.chassis.vendor: Apple Inc.
dmi.chassis.version: Mac-06F11F11946D27C5
dmi.modalias:
dmi:bvnAppleInc.:bvrMBP114.88Z.0172.B09.1602151732:bd02/15/2016:svnAppleInc.:pnMacBookPro11,5:pvr1.0:rvnAppleInc.:rnMac-06F11F11946D27C5:rvrMacBookPro11,5:cvnAppleInc.:ct9:cvrMac-06F11F11946D27C5:
dmi.product.name: MacBookPro11,5
dmi.product.version: 1.0
dmi.sys.vendor: Apple Inc.

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

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

Title:
Belkin Thunderbolt 2 Express Dock HD display port hot plug not
supported.

Status in linux package in Ubuntu:
Triaged

Bug description:
Peripheral: Belkin Thunderbolt 2 Express Dock HD. Model: F4U085

1. When booted without the dock connected, connecting the dock only
allows USB and Ethernet to work, it does not support HDMI or
DisplayPort monitors. Re-seating the dock from here does not stop USB
and Ethernet from working.

2. When booted with the device connected, while the device works fine,
reseating the dock

[Kernel-packages] [Bug 1655476] Re: linux: 3.13.0-108.155 -proposed tracker

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

** Changed in: kernel-sru-workflow/prepare-package-signed
 Assignee: Canonical Kernel Team (canonical-kernel-team) => John Donnelly 
(jpdonnelly)

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

Title:
  linux: 3.13.0-108.155 -proposed tracker

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

Bug description:
  This bug is for tracking the 3.13.0-108.155 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 --
  derivative-trackers-created: true
  phase: Uploaded

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1655476/+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 1626894] Re: nvme drive probe failure

2017-01-11 Thread Kamal Mostafa

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

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

** Changed in: linux (Ubuntu Yakkety)
   Status: Fix Released => 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/1626894

Title:
  nvme drive probe failure

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

Bug description:
  After upgrading from linux-image-4.4.0-38-generic to proposed update
  linux-image-4.4.0-39-generic, NVMe drives are no longer working. dmesg
  shows a probe failure.

  On the previous kernel version everything is working as expected.
  ->%-
  [1.005243] Hardware name: FUJITSU D3417-B1/D3417-B1, BIOS V5.0.0.11 
R1.12.0.SR.2 for D3417-B1x   04/01/2016
  [1.005349] Workqueue: events nvme_remove_dead_ctrl_work [nvme]
  [1.005484]  0286 b6c91251 880fe6e8bce0 
813f1f83
  [1.005800]  880fe02150f0 c90006a7c000 880fe6e8bd00 
8106bdff
  [1.006117]  880fe02150f0 880fe0215258 880fe6e8bd10 
8106be3c
  [1.006433] Call Trace:
  [1.006509]  [] dump_stack+0x63/0x90
  [1.006589]  [] iounmap.part.1+0x7f/0x90
  [1.006668]  [] iounmap+0x2c/0x30
  [1.006770]  [] nvme_dev_unmap.isra.35+0x1a/0x30 [nvme]
  [1.007048]  [] nvme_remove+0xce/0xe0 [nvme]
  [1.007140]  [] pci_device_remove+0x39/0xc0
  [1.007220]  [] __device_release_driver+0xa1/0x150
  [1.007301]  [] device_release_driver+0x23/0x30
  [1.007382]  [] pci_stop_bus_device+0x8a/0xa0
  [1.007462]  [] 
pci_stop_and_remove_bus_device_locked+0x1a/0x30
  [1.007559]  [] nvme_remove_dead_ctrl_work+0x3c/0x50 
[nvme]
  [1.007642]  [] process_one_work+0x165/0x480
  [1.007722]  [] worker_thread+0x4b/0x4c0
  [1.007801]  [] ? process_one_work+0x480/0x480
  [1.007881]  [] kthread+0xd8/0xf0
  [1.007959]  [] ? kthread_create_on_node+0x1e0/0x1e0
  [1.008041]  [] ret_from_fork+0x3f/0x70
  [1.008120]  [] ? kthread_create_on_node+0x1e0/0x1e0
  [1.008222] Trying to free nonexistent resource 

  [1.008276] genirq: Flags mismatch irq 0. 0080 (nvme1q0) vs. 00015a00 
(timer)
  [1.008281] Trying to free nonexistent resource 

  [1.008282] nvme :02:00.0: Removing after probe failure
  [1.008645] Trying to free nonexistent resource 

  [1.027213] iounmap: bad address c90006ae
  [1.027456] CPU: 2 PID: 86 Comm: kworker/2:1 Not tainted 4.4.0-39-generic 
#59-Ubuntu
  -%<-

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1626894/+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 1641451] Re: ALPS Touchpad incorrectly detected as PS/2 mouse in Dell Latitude 7370

2017-01-11 Thread Michael Doube

Thanks for your help with this, looks like it's fixed for Xenial on
stock kernel v4.4 so I will not proceed with an SRU at this stage

:~$ uname -a
Linux Bethany 4.4.0-59-generic #80-Ubuntu SMP Fri Jan 6 17:47:47 UTC 2017 
x86_64 x86_64 x86_64 GNU/Linux

:~$ cat /proc/bus/input/devices
I: Bus=0011 Vendor=0002 Product=0008 Version=0800
N: Name="AlpsPS/2 ALPS DualPoint TouchPad"
P: Phys=isa0060/serio1/input0
S: Sysfs=/devices/platform/i8042/serio1/input/input6
U: Uniq=
H: Handlers=mouse1 event7 
B: PROP=1
B: EV=b
B: KEY=e520 7 0 0 0 0
B: ABS=2608103

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

Title:
  ALPS Touchpad incorrectly detected as PS/2 mouse in Dell Latitude 7370

Status in linux package in Ubuntu:
  Fix Released

Bug description:
  Touchpad is detected but appears to be running some generic drivers
  which mean the full suite of multi-touch controls and disabling
  touchpad while typing are missing.

  Laptop model directly from the sticker of the computer.
  Dell Latitude 7370
  Reg Model P67G

  Manufacturer of the Touchpad.
  Alps

  When the symptom first appeared.
  Since installing Ubuntu

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xserver-xorg-input-synaptics 1.8.2-1ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-47.68-generic 4.4.24
  Uname: Linux 4.4.0-47-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  Date: Sun Nov 13 20:08:03 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  InstallationDate: Installed on 2016-05-15 (182 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Dell Inc. Latitude 7370
  ProcEnviron:
   LANGUAGE=en_GB:en
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-47-generic.efi.signed 
root=UUID=d96256e6-13a6-46a5-ba80-2e121d8f8dab ro quiet splash vt.handoff=7
  SourcePackage: xserver-xorg-input-synaptics
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/14/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 01.05.03
  dmi.board.name: 0MMWGJ
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr01.05.03:bd07/14/2016:svnDellInc.:pnLatitude7370:pvr:rvnDellInc.:rn0MMWGJ:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude 7370
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2.2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2.2
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Sat Nov 12 17:24:12 2016
  xserver.configfile: default
  xserver.errors:

  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id5217
   vendor SHP
  xserver.version: 2:1.18.4-0ubuntu0.1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1641451/+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 1655411] Re: Cannot enable VC4 graphics driver on RPi 3

2017-01-11 Thread Alberto Aguirre

Turns out we simply need to use the latest firmware loader blobs, then
the vc4 overlay is applied correctly while using u-boot.

https://github.com/raspberrypi/firmware/tree/master/boot

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

Title:
  Cannot enable VC4 graphics driver on RPi 3

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  It seems the VC4 device tree overlay is not applied by the Rpi
  firmware.

  I tried adding dtoverlay=vc4-kms-v3d and adding a corresponding
  .../overlays/vc4-kms-v3d.dtbo file but it seems the Rpi bootloader
  does not apply the overlay at all.

  I merged vc4-kms-v3d.dtbo into bcm2710-rpi-3-b.dtb using a dtmerge utility 
compiled by pulling pieces from (https://github.com/raspberrypi/userland and 
https://github.com/dgibson/dtc)
  The result is here: https://github.com/albaguirre/dtmerge

  With this new device tree binary blob, The VC4 driver (as a module)
  loads (and you can see /dev/dri/ entries)

  I also played around with the tip of u-boot tree
  (git://git.denx.de/u-boot.git) which has support to apply device tree
  overlays - it applied fine and VC4 is at least recognized but the
  driver cannot initialize properly.

  Any idea on what magic incantation is needed for the RPi loaders
  (start.elf etc) to apply the vc4 overlay?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1655411/+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 1655683] Re: kernel BUG at skbuff.h:1486 Insufficient linear data in skb __skb_pull.part.7+0x4/0x6 [openvswitch]

2017-01-11 Thread Tim Gardner

https://lists.ubuntu.com/archives/kernel-team/2017-January/081806.html

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

** Changed in: linux (Ubuntu Trusty)
 Assignee: (unassigned) => Andrew Crawford (acrawford)

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

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

Title:
  kernel BUG at skbuff.h:1486 Insufficient linear data in skb
  __skb_pull.part.7+0x4/0x6 [openvswitch]

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Trusty:
  In Progress

Bug description:
  Since 2016-12-30 EST we have been experiencing repeated crashes of our
  OpenStack Icehouse / Trusty Neutron node with a kernel BUG at skbuff.h
  line 1486:

  1471 /**
  1472 * skb_peek - peek at the head of an _buff_head
  1473 * @list_: list to peek at
  1474 *
  1475 * Peek an _buff. Unlike most other operations you _MUST_
  1476 * be careful with this one. A peek leaves the buffer on the
  1477 * list and someone else may run off with it. You must hold
  1478 * the appropriate locks or have a private queue to do this.
  1479 *
  1480 * Returns %NULL for an empty list or a pointer to the head element.
  1481 * The reference count is not incremented and the reference is therefore
  1482 * volatile. Use with caution.
  1483 */
  1484 static inline struct sk_buff *skb_peek(const struct sk_buff_head *list_)
  1485 {
  1486 struct sk_buff *skb = list_->next;
  1487
  1488 if (skb == (struct sk_buff *)list_)
  1489 skb = NULL;
  1490 return skb;
  1491 }

  This generally results in a full panic crash of the Neutron node and
  connectivity breaking for VMs within the cloud. However, after using
  crash-dumptools to collect information on the crashes over the past
  three days, the kernel loaded by kexec during the crashdump appears in
  about 2 out of 3 crash instances to continue running, and we see a
  flap of the neutron services instead of a full panic that brings the
  Neutron server down and necessitates a hard reboot.

  I believe that this is a manifestation of the openvswitch and issue
  described on 2017-01-08 as:

  "OVS can only process L2 packets. But OVS GRE receive handler
  can accept IP-GRE packets. When such packet is processed by
  OVS datapath it can trigger following assert failure due
  to insufficient linear data in skb."

  https://patchwork.ozlabs.org/patch/712373/

  I have not tested the patch provided above yet.

  Other information and a few sample dmesg outputs from the crash:
  (multiple dumps available)

  # lsb_release -rd
  Description: Ubuntu 14.04.5 LTS
  Release: 14.04

  # apt-cache policy openvswitch
  N: Unable to locate package openvswitch
  root@neutron01:/var/crash# apt-cache policy openvswitch-common
  openvswitch-common:
Installed: 2.0.2-0ubuntu0.14.04.3
Candidate: 2.0.2-0ubuntu0.14.04.3
Version table:
   *** 2.0.2-0ubuntu0.14.04.3 0
  500 http://us.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   2.0.1+git20140120-0ubuntu2 0
  500 http://us.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages

  # apt-cache policy openvswitch-switch
  openvswitch-switch:
Installed: 2.0.2-0ubuntu0.14.04.3
Candidate: 2.0.2-0ubuntu0.14.04.3
Version table:
   *** 2.0.2-0ubuntu0.14.04.3 0
  500 http://us.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   2.0.1+git20140120-0ubuntu2 0
  500 http://us.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages

  # apt-cache policy neutron-plugin-openvswitch-agent
  neutron-plugin-openvswitch-agent:
Installed: 1:2014.1.5-0ubuntu7
Candidate: 1:2014.1.5-0ubuntu7
Version table:
   *** 1:2014.1.5-0ubuntu7 0
  500 http://us.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   1:2014.1.3-0ubuntu1.1 0
  500 http://security.ubuntu.com/ubuntu/ trusty-security/main amd64 
Packages
   1:2014.1-0ubuntu1 0
  500 http://us.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages

  example dmesg:

  ## dmesg.201701060019

  > [33100.131019] [ cut here ]
  > [33100.131176] kernel BUG at 
/build/linux-mi9H1O/linux-3.13.0/include/linux/skbuff.h:1486!
  > [33100.131424] invalid opcode:  [#1] SMP
  > [33100.131560] Modules linked in: xt_nat xt_conntrack ip6table_filter 
ip6_tables iptable_filter xt_REDIRECT xt_tcpudp iptable_nat nf_conntrack_ipv4 
nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack ip_tables x_tables veth 
openvswitch gre vxlan ip_tunnel libcrc32c ipmi_devintf gpio_ich cdc_ether 
x86_pkg_temp_thermal intel_powerclamp coretemp usbnet kvm_intel mii kvm 
crct10dif_pclmul crc32_pclmul ghash_clmulni_intel aesni_intel aes_x86_64 lrw 
gf128mul glue_helper

[Kernel-packages] [Bug 1626894] Re: nvme drive probe failure

2017-01-11 Thread Wayne Scott

Odd, but I have another machine with almost the same Intel SSD and it is
running kernel -57 just fine.

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

Title:
  nvme drive probe failure

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

Bug description:
  After upgrading from linux-image-4.4.0-38-generic to proposed update
  linux-image-4.4.0-39-generic, NVMe drives are no longer working. dmesg
  shows a probe failure.

  On the previous kernel version everything is working as expected.
  ->%-
  [1.005243] Hardware name: FUJITSU D3417-B1/D3417-B1, BIOS V5.0.0.11 
R1.12.0.SR.2 for D3417-B1x   04/01/2016
  [1.005349] Workqueue: events nvme_remove_dead_ctrl_work [nvme]
  [1.005484]  0286 b6c91251 880fe6e8bce0 
813f1f83
  [1.005800]  880fe02150f0 c90006a7c000 880fe6e8bd00 
8106bdff
  [1.006117]  880fe02150f0 880fe0215258 880fe6e8bd10 
8106be3c
  [1.006433] Call Trace:
  [1.006509]  [] dump_stack+0x63/0x90
  [1.006589]  [] iounmap.part.1+0x7f/0x90
  [1.006668]  [] iounmap+0x2c/0x30
  [1.006770]  [] nvme_dev_unmap.isra.35+0x1a/0x30 [nvme]
  [1.007048]  [] nvme_remove+0xce/0xe0 [nvme]
  [1.007140]  [] pci_device_remove+0x39/0xc0
  [1.007220]  [] __device_release_driver+0xa1/0x150
  [1.007301]  [] device_release_driver+0x23/0x30
  [1.007382]  [] pci_stop_bus_device+0x8a/0xa0
  [1.007462]  [] 
pci_stop_and_remove_bus_device_locked+0x1a/0x30
  [1.007559]  [] nvme_remove_dead_ctrl_work+0x3c/0x50 
[nvme]
  [1.007642]  [] process_one_work+0x165/0x480
  [1.007722]  [] worker_thread+0x4b/0x4c0
  [1.007801]  [] ? process_one_work+0x480/0x480
  [1.007881]  [] kthread+0xd8/0xf0
  [1.007959]  [] ? kthread_create_on_node+0x1e0/0x1e0
  [1.008041]  [] ret_from_fork+0x3f/0x70
  [1.008120]  [] ? kthread_create_on_node+0x1e0/0x1e0
  [1.008222] Trying to free nonexistent resource 

  [1.008276] genirq: Flags mismatch irq 0. 0080 (nvme1q0) vs. 00015a00 
(timer)
  [1.008281] Trying to free nonexistent resource 

  [1.008282] nvme :02:00.0: Removing after probe failure
  [1.008645] Trying to free nonexistent resource 

  [1.027213] iounmap: bad address c90006ae
  [1.027456] CPU: 2 PID: 86 Comm: kworker/2:1 Not tainted 4.4.0-39-generic 
#59-Ubuntu
  -%<-

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1626894/+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 1626894] Re: nvme drive probe failure

2017-01-11 Thread Wayne Scott

Another data point...

I have 2 Intel P3700 NVMe SSDs on an x99 chipset motherboard.
For me Ubuntu 16.04 Kernel 4.4.0-53 works, but -57 and -59 both fail to find 
the SSDs.

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

Title:
  nvme drive probe failure

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

Bug description:
  After upgrading from linux-image-4.4.0-38-generic to proposed update
  linux-image-4.4.0-39-generic, NVMe drives are no longer working. dmesg
  shows a probe failure.

  On the previous kernel version everything is working as expected.
  ->%-
  [1.005243] Hardware name: FUJITSU D3417-B1/D3417-B1, BIOS V5.0.0.11 
R1.12.0.SR.2 for D3417-B1x   04/01/2016
  [1.005349] Workqueue: events nvme_remove_dead_ctrl_work [nvme]
  [1.005484]  0286 b6c91251 880fe6e8bce0 
813f1f83
  [1.005800]  880fe02150f0 c90006a7c000 880fe6e8bd00 
8106bdff
  [1.006117]  880fe02150f0 880fe0215258 880fe6e8bd10 
8106be3c
  [1.006433] Call Trace:
  [1.006509]  [] dump_stack+0x63/0x90
  [1.006589]  [] iounmap.part.1+0x7f/0x90
  [1.006668]  [] iounmap+0x2c/0x30
  [1.006770]  [] nvme_dev_unmap.isra.35+0x1a/0x30 [nvme]
  [1.007048]  [] nvme_remove+0xce/0xe0 [nvme]
  [1.007140]  [] pci_device_remove+0x39/0xc0
  [1.007220]  [] __device_release_driver+0xa1/0x150
  [1.007301]  [] device_release_driver+0x23/0x30
  [1.007382]  [] pci_stop_bus_device+0x8a/0xa0
  [1.007462]  [] 
pci_stop_and_remove_bus_device_locked+0x1a/0x30
  [1.007559]  [] nvme_remove_dead_ctrl_work+0x3c/0x50 
[nvme]
  [1.007642]  [] process_one_work+0x165/0x480
  [1.007722]  [] worker_thread+0x4b/0x4c0
  [1.007801]  [] ? process_one_work+0x480/0x480
  [1.007881]  [] kthread+0xd8/0xf0
  [1.007959]  [] ? kthread_create_on_node+0x1e0/0x1e0
  [1.008041]  [] ret_from_fork+0x3f/0x70
  [1.008120]  [] ? kthread_create_on_node+0x1e0/0x1e0
  [1.008222] Trying to free nonexistent resource 

  [1.008276] genirq: Flags mismatch irq 0. 0080 (nvme1q0) vs. 00015a00 
(timer)
  [1.008281] Trying to free nonexistent resource 

  [1.008282] nvme :02:00.0: Removing after probe failure
  [1.008645] Trying to free nonexistent resource 

  [1.027213] iounmap: bad address c90006ae
  [1.027456] CPU: 2 PID: 86 Comm: kworker/2:1 Not tainted 4.4.0-39-generic 
#59-Ubuntu
  -%<-

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1626894/+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 1655735] Re: Incompatible libdevmapper 1.02.136 (2016-11-05) and kernel driver (unknown version).

On Jan 11, 2017, at 08:10 PM, Joseph Salisbury wrote:

>Does the error go away if you boot a Xenial test kernel on this machine
>and re-run the test?  That will tell us if it is a kernel regression.

We're a bit hardware starved atm, but trying to test this.

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

Title:
  Incompatible libdevmapper 1.02.136 (2016-11-05) and kernel driver
  (unknown version).

Status in linux package in Ubuntu:
  Confirmed
Status in lvm2 package in Ubuntu:
  New
Status in multipath-tools package in Ubuntu:
  New

Bug description:
  There is a new Zesty regression on armhf, related to the autopkgtest
  for ubuntu-image.  Here's a log of a recent run:

https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
  /autopkgtest-zesty/zesty/armhf/u/ubuntu-
  image/20170111_171929_431b1@/log.gz

  Scroll to the bottom and you see this:

  Incompatible libdevmapper 1.02.136 (2016-11-05) and kernel driver (unknown 
version).
  device mapper prerequisites not met
  /dev/mapper/control: mknod failed: Operation not permitted
  Failure to communicate with kernel device-mapper driver.
  Check that device-mapper is available in the kernel.
  Incompatible libdevmapper 1.02.136 (2016-11-05) and kernel driver (unknown 
version).
  device mapper prerequisites not met

  Don't be misled by the gadget.yamls which name different
  architectures.  ubuntu-image should be able to build a disk image for
  any architecture on any architecture.

  What this test does is build the image, then run kpartx to map the
  partitions in the image, and then mount the partitions.  It doesn't do
  anything other than ensure that the partitions can be mounted, and
  this is where it's failing.

  This test succeeds on amd64, i386, and ppc64el.  It's never passed on
  s390x so that's not a regression.  It *used* to pass on armhf even on
  Zesty, but the recent upload of 0.13+17.10ubuntu2 displays the
  regression.

  I will bugtask this to libdevmapper and kpartx since it's possibly a
  bug in one of those packages (though I still suspect the kernel).

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: linux-image-4.9.0-11-generic 4.9.0-11.12
  ProcVersionSignature: Ubuntu 4.9.0-11.12-generic 4.9.0
  Uname: Linux 4.9.0-11-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair nvidia_uvm nvidia_drm 
nvidia_modeset nvidia
  ApportVersion: 2.20.4-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  barry  5414 F pulseaudio
   /dev/snd/controlC0:  barry  5414 F pulseaudio
  CurrentDesktop: Unity
  Date: Wed Jan 11 13:10:30 2017
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=8cc96f00-242f-42c6-bdb9-72db178f8864
  InstallationDate: Installed on 2016-01-22 (355 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160117)
  MachineType: Gigabyte Technology Co., Ltd. Z170X-UD5
  ProcFB:

  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.9.0-11-generic 
root=UUID=d03718f1-9983-4b07-a942-1b42fe8352ec ro
  RelatedPackageVersions:
   linux-restricted-modules-4.9.0-11-generic N/A
   linux-backports-modules-4.9.0-11-generic  N/A
   linux-firmware1.162
  RfKill:

  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/24/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F2
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z170X-UD5-CF
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF2:bd07/24/2015:svnGigabyteTechnologyCo.,Ltd.:pnZ170X-UD5:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ170X-UD5-CF:rvrx.x:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: Z170X-UD5
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1655735/+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 1655755] Re: Update "UBUNTU: SAUCE: suspicious unlocked ->status reading and writing in ipc/sem.c" for 4.10

2017-01-11 Thread Seth Forshee

Andy, could you take a look at this? I suspect the patch isn't needed
but would like confirmation of this from you.

** Changed in: linux (Ubuntu)
 Assignee: (unassigned) => Andy Whitcroft (apw)

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

Title:
  Update "UBUNTU: SAUCE: suspicious unlocked ->status reading and
  writing in ipc/sem.c" for 4.10

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  This patch was dropped during the rebase to 4.10-rc1 due to conflicts
  with upstream changes. If this patch is still needed it will need to
  be updated.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1655755/+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 1655755] [NEW] Update "UBUNTU: SAUCE: suspicious unlocked ->status reading and writing in ipc/sem.c" for 4.10

2017-01-11 Thread Seth Forshee

Public bug reported:

This patch was dropped during the rebase to 4.10-rc1 due to conflicts
with upstream changes. If this patch is still needed it will need to be
updated.

** Affects: linux (Ubuntu)
 Importance: Medium
 Assignee: Andy Whitcroft (apw)
 Status: 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/1655755

Title:
  Update "UBUNTU: SAUCE: suspicious unlocked ->status reading and
  writing in ipc/sem.c" for 4.10

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  This patch was dropped during the rebase to 4.10-rc1 due to conflicts
  with upstream changes. If this patch is still needed it will need to
  be updated.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1655755/+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 1655075] Re: linux-ti-omap4: 3.2.0-1499.126 -proposed tracker

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

** Description changed:

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

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

Title:
  linux-ti-omap4: 3.2.0-1499.126 -proposed tracker

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

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

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

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

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

** Description changed:

  This bug is for tracking the 3.2.0-1682.109 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: 1655071
  phase: Uploaded

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

Title:
  linux-armadaxp: 3.2.0-1682.109 -proposed tracker

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

Bug description:
  This bug is for tracking the 3.2.0-1682.109 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: 1655071
  phase: Uploaded

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

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

** Changed in: kernel-sru-workflow/prepare-package-lbm
 Assignee: Canonical Kernel Team (canonical-kernel-team) => John Donnelly 
(jpdonnelly)

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

** Description changed:

  This bug is for tracking the 3.2.0-121.164 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 --
  derivative-trackers-created: true
  phase: Uploaded
+ kernel-stable-phase:Uploaded
+ kernel-stable-phase-changed:Wednesday, 11. January 2017 20:32 UTC

** Description changed:

  This bug is for tracking the 3.2.0-121.164 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: Uploaded
- kernel-stable-phase:Uploaded
- kernel-stable-phase-changed:Wednesday, 11. January 2017 20:32 UTC

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

Title:
  linux: 3.2.0-121.164 -proposed tracker

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

Bug description:
  This bug is for tracking the 3.2.0-121.164 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: Uploaded

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1655071/+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 1655379] Re: Bug fixes for IBM VNIC Driver

2017-01-11 Thread Tim Gardner

IIRC "needs unknown symbol .TOC" was a toolchain issue (binutils). Try
using a Zesty chroot.

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

Title:
  Bug fixes for IBM VNIC Driver

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

Bug description:
  In order to bring the VNIC driver up to date and pull in fixes for all
  of the bugs we have seen we would need to have the following patches
  applied.

  
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/drivers/net/ethernet/ibm/ibmvnic.c?h=v4.10-rc3=12608c260d2fe36746508cb4fa20b6e9a5f9c241

  
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/drivers/net/ethernet/ibm/ibmvnic.c?h=v4.10-rc3=87737f8810db445db171ca81ca4cc43bd5b067ce

  
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/drivers/net/ethernet/ibm/ibmvnic.c?h=v4.10-rc3=d894be57ca92c8a8819ab544d550809e8731137b

  
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/drivers/net/ethernet/ibm/ibmvnic.c?h=v4.10-rc3=9888d7b02c7793cbbcbdd05dd9e14cc0e78d1db7

  
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/drivers/net/ethernet/ibm/ibmvnic.c?h=v4.10-rc3=8bf371e6adff29758cc3c57c17df4486513081f8

  
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/drivers/net/ethernet/ibm/ibmvnic.c?h=v4.10-rc3=6dbcd8fb5968fda3a5fba019dfb0c80c3139627b

  
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/drivers/net/ethernet/ibm/ibmvnic.c?h=v4.10-rc3=b7f193da17fb18b752bef77ce52eb49723299bd8

  
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/drivers/net/ethernet/ibm/ibmvnic.c?h=v4.10-rc3=e1fac0adf0f9b2c1eb49e658e6ed070a744bbaef

  I created a tree based on 16.04.2 kernel and included these commits.

  https://github.com/leitao/ubuntu-yakkety/tree/vnic

  I will be generating kernel binaries, so, we can test it.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1655379/+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 1625805] Re: dragonboard: history daemon dereferences a rogue pointer

2017-01-11 Thread Pat McGowan

** Changed in: canonical-devices-system-image
   Status: Fix Committed => Fix Released

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

Title:
  dragonboard: history daemon dereferences a rogue pointer

Status in Canonical System Image:
  Fix Released
Status in history-service package in Ubuntu:
  Fix Committed
Status in linux package in Ubuntu:
  Invalid

Bug description:
  we are running the unity8 session snap on amd64 without any problems.
  to setup and reproduce the problem follow the "on Dragonboard" section of 
  
https://docs.google.com/document/d/1o-jKITqUxRsujmN3OwRj3wRnn6dgblKuvrhKjeN8-Wc

  You can also find the panic signature at line 3276 of the attached
  syslog.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1625805/+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 1655683] Re: kernel BUG at skbuff.h:1486 Insufficient linear data in skb __skb_pull.part.7+0x4/0x6 [openvswitch]

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

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

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

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

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

Title:
  kernel BUG at skbuff.h:1486 Insufficient linear data in skb
  __skb_pull.part.7+0x4/0x6 [openvswitch]

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

Bug description:
  Since 2016-12-30 EST we have been experiencing repeated crashes of our
  OpenStack Icehouse / Trusty Neutron node with a kernel BUG at skbuff.h
  line 1486:

  1471 /**
  1472 * skb_peek - peek at the head of an _buff_head
  1473 * @list_: list to peek at
  1474 *
  1475 * Peek an _buff. Unlike most other operations you _MUST_
  1476 * be careful with this one. A peek leaves the buffer on the
  1477 * list and someone else may run off with it. You must hold
  1478 * the appropriate locks or have a private queue to do this.
  1479 *
  1480 * Returns %NULL for an empty list or a pointer to the head element.
  1481 * The reference count is not incremented and the reference is therefore
  1482 * volatile. Use with caution.
  1483 */
  1484 static inline struct sk_buff *skb_peek(const struct sk_buff_head *list_)
  1485 {
  1486 struct sk_buff *skb = list_->next;
  1487
  1488 if (skb == (struct sk_buff *)list_)
  1489 skb = NULL;
  1490 return skb;
  1491 }

  This generally results in a full panic crash of the Neutron node and
  connectivity breaking for VMs within the cloud. However, after using
  crash-dumptools to collect information on the crashes over the past
  three days, the kernel loaded by kexec during the crashdump appears in
  about 2 out of 3 crash instances to continue running, and we see a
  flap of the neutron services instead of a full panic that brings the
  Neutron server down and necessitates a hard reboot.

  I believe that this is a manifestation of the openvswitch and issue
  described on 2017-01-08 as:

  "OVS can only process L2 packets. But OVS GRE receive handler
  can accept IP-GRE packets. When such packet is processed by
  OVS datapath it can trigger following assert failure due
  to insufficient linear data in skb."

  https://patchwork.ozlabs.org/patch/712373/

  I have not tested the patch provided above yet.

  Other information and a few sample dmesg outputs from the crash:
  (multiple dumps available)

  # lsb_release -rd
  Description: Ubuntu 14.04.5 LTS
  Release: 14.04

  # apt-cache policy openvswitch
  N: Unable to locate package openvswitch
  root@neutron01:/var/crash# apt-cache policy openvswitch-common
  openvswitch-common:
Installed: 2.0.2-0ubuntu0.14.04.3
Candidate: 2.0.2-0ubuntu0.14.04.3
Version table:
   *** 2.0.2-0ubuntu0.14.04.3 0
  500 http://us.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   2.0.1+git20140120-0ubuntu2 0
  500 http://us.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages

  # apt-cache policy openvswitch-switch
  openvswitch-switch:
Installed: 2.0.2-0ubuntu0.14.04.3
Candidate: 2.0.2-0ubuntu0.14.04.3
Version table:
   *** 2.0.2-0ubuntu0.14.04.3 0
  500 http://us.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   2.0.1+git20140120-0ubuntu2 0
  500 http://us.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages

  # apt-cache policy neutron-plugin-openvswitch-agent
  neutron-plugin-openvswitch-agent:
Installed: 1:2014.1.5-0ubuntu7
Candidate: 1:2014.1.5-0ubuntu7
Version table:
   *** 1:2014.1.5-0ubuntu7 0
  500 http://us.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   1:2014.1.3-0ubuntu1.1 0
  500 http://security.ubuntu.com/ubuntu/ trusty-security/main amd64 
Packages
   1:2014.1-0ubuntu1 0
  500 http://us.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages

  example dmesg:

  ## dmesg.201701060019

  > [33100.131019] [ cut here ]
  > [33100.131176] kernel BUG at 
/build/linux-mi9H1O/linux-3.13.0/include/linux/skbuff.h:1486!
  > [33100.131424] invalid opcode:  [#1] SMP
  > [33100.131560] Modules linked in: xt_nat xt_conntrack ip6table_filter 
ip6_tables iptable_filter xt_REDIRECT xt_tcpudp iptable_nat nf_conntrack_ipv4 
nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack ip_tables x_tables veth 
openvswitch gre vxlan ip_tunnel libcrc32c ipmi_devintf gpio_ich cdc_ether 
x86_pkg_temp_thermal intel_powerclamp coretemp usbnet kvm_intel mii kvm 
crct10dif_pclmul crc32_pclmul ghash_clmulni_intel

[Kernel-packages] [Bug 1655552] Re: package libasound2:i386 1.1.0-0ubuntu1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configurat

2017-01-11 Thread Apport retracing service

** Tags removed: need-duplicate-check

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

Title:
  package libasound2:i386 1.1.0-0ubuntu1 failed to install/upgrade:
  package is in a very bad inconsistent state; you should  reinstall it
  before attempting configuration

Status in alsa-lib package in Ubuntu:
  New

Bug description:
  i don t now

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libasound2:i386 1.1.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-57.78-generic 4.4.35
  Uname: Linux 4.4.0-57-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.4
  Architecture: amd64
  Date: Wed Jan 11 09:04:43 2017
  Dependencies:
   gcc-6-base 6.0.1-0ubuntu1
   libasound2-data 1.1.0-0ubuntu1
   libc6 2.23-0ubuntu5
   libgcc1 1:6.0.1-0ubuntu1
  DuplicateSignature:
   package:libasound2:i386:1.1.0-0ubuntu1
   Processing triggers for libc-bin (2.23-0ubuntu5) ...
   dpkg: error processing package libasound2:i386 (--configure):
package is in a very bad inconsistent state; you should
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  InstallationDate: Installed on 2016-08-13 (150 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  PackageArchitecture: i386
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.15ubuntu0.2
  SourcePackage: alsa-lib
  Title: package libasound2:i386 1.1.0-0ubuntu1 failed to install/upgrade: 
package is in a very bad inconsistent state; you should  reinstall it before 
attempting configuration
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-lib/+bug/162/+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 1655735] Re: Incompatible libdevmapper 1.02.136 (2016-11-05) and kernel driver (unknown version).

Does the error go away if you boot a Xenial test kernel on this machine
and re-run the test?  That will tell us if it is a kernel regression.

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

** Tags added: kernel-key

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

Title:
  Incompatible libdevmapper 1.02.136 (2016-11-05) and kernel driver
  (unknown version).

Status in linux package in Ubuntu:
  Confirmed
Status in lvm2 package in Ubuntu:
  New
Status in multipath-tools package in Ubuntu:
  New

Bug description:
  There is a new Zesty regression on armhf, related to the autopkgtest
  for ubuntu-image.  Here's a log of a recent run:

  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
  /autopkgtest-zesty/zesty/armhf/u/ubuntu-
  image/20170111_171929_431b1@/log.gz

  Scroll to the bottom and you see this:

  Incompatible libdevmapper 1.02.136 (2016-11-05) and kernel driver (unknown 
version).
  device mapper prerequisites not met
  /dev/mapper/control: mknod failed: Operation not permitted
  Failure to communicate with kernel device-mapper driver.
  Check that device-mapper is available in the kernel.
  Incompatible libdevmapper 1.02.136 (2016-11-05) and kernel driver (unknown 
version).
  device mapper prerequisites not met

  Don't be misled by the gadget.yamls which name different
  architectures.  ubuntu-image should be able to build a disk image for
  any architecture on any architecture.

  What this test does is build the image, then run kpartx to map the
  partitions in the image, and then mount the partitions.  It doesn't do
  anything other than ensure that the partitions can be mounted, and
  this is where it's failing.

  This test succeeds on amd64, i386, and ppc64el.  It's never passed on
  s390x so that's not a regression.  It *used* to pass on armhf even on
  Zesty, but the recent upload of 0.13+17.10ubuntu2 displays the
  regression.

  I will bugtask this to libdevmapper and kpartx since it's possibly a
  bug in one of those packages (though I still suspect the kernel).

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: linux-image-4.9.0-11-generic 4.9.0-11.12
  ProcVersionSignature: Ubuntu 4.9.0-11.12-generic 4.9.0
  Uname: Linux 4.9.0-11-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair nvidia_uvm nvidia_drm 
nvidia_modeset nvidia
  ApportVersion: 2.20.4-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  barry  5414 F pulseaudio
   /dev/snd/controlC0:  barry  5414 F pulseaudio
  CurrentDesktop: Unity
  Date: Wed Jan 11 13:10:30 2017
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=8cc96f00-242f-42c6-bdb9-72db178f8864
  InstallationDate: Installed on 2016-01-22 (355 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160117)
  MachineType: Gigabyte Technology Co., Ltd. Z170X-UD5
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.9.0-11-generic 
root=UUID=d03718f1-9983-4b07-a942-1b42fe8352ec ro
  RelatedPackageVersions:
   linux-restricted-modules-4.9.0-11-generic N/A
   linux-backports-modules-4.9.0-11-generic  N/A
   linux-firmware1.162
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/24/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F2
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z170X-UD5-CF
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF2:bd07/24/2015:svnGigabyteTechnologyCo.,Ltd.:pnZ170X-UD5:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ170X-UD5-CF:rvrx.x:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: Z170X-UD5
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1655735/+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 1655580] Re: package linux-image-extra-3.19.0-79-generic 3.19.0-79.87~14.04.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status

2017-01-11 Thread Emily Ratliff

** Information type changed from Private Security to Public

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

Title:
  package linux-image-extra-3.19.0-79-generic 3.19.0-79.87~14.04.1
  failed to install/upgrade: subprocess installed post-installation
  script returned error exit status 1

Status in linux-lts-vivid package in Ubuntu:
  New

Bug description:
  The error msg came several minutes after I logged in. 
  Actually, I couldn't understand very well the magnitude of the problem. 
  So, I'm sending the problem to you... Thank you.
  Regards, 
  IOS

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: linux-image-extra-3.19.0-79-generic 3.19.0-79.87~14.04.1
  ProcVersionSignature: Ubuntu 3.19.0-78.86~14.04.1-generic 3.19.8-ckt22
  Uname: Linux 3.19.0-78-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.23
  Architecture: amd64
  Date: Wed Jan 11 12:06:31 2017
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2016-01-03 (373 days ago)
  InstallationMedia: Ubuntu-Server 14.04.3 LTS "Trusty Tahr" - Beta amd64 
(20150805)
  RelatedPackageVersions:
   dpkg 1.17.5ubuntu5.7
   apt  1.0.1ubuntu2.17
  SourcePackage: linux-lts-vivid
  Title: package linux-image-extra-3.19.0-79-generic 3.19.0-79.87~14.04.1 
failed to install/upgrade: subprocess installed post-installation script 
returned error exit status 1
  UpgradeStatus: Upgraded to trusty on 2017-01-08 (2 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-lts-vivid/+bug/1655580/+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 1655552] Re: package libasound2:i386 1.1.0-0ubuntu1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configurat

2017-01-11 Thread Emily Ratliff

** Information type changed from Private Security to Public

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

Title:
  package libasound2:i386 1.1.0-0ubuntu1 failed to install/upgrade:
  package is in a very bad inconsistent state; you should  reinstall it
  before attempting configuration

Status in alsa-lib package in Ubuntu:
  New

Bug description:
  i don t now

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libasound2:i386 1.1.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-57.78-generic 4.4.35
  Uname: Linux 4.4.0-57-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.4
  Architecture: amd64
  Date: Wed Jan 11 09:04:43 2017
  Dependencies:
   gcc-6-base 6.0.1-0ubuntu1
   libasound2-data 1.1.0-0ubuntu1
   libc6 2.23-0ubuntu5
   libgcc1 1:6.0.1-0ubuntu1
  DuplicateSignature:
   package:libasound2:i386:1.1.0-0ubuntu1
   Processing triggers for libc-bin (2.23-0ubuntu5) ...
   dpkg: error processing package libasound2:i386 (--configure):
package is in a very bad inconsistent state; you should
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  InstallationDate: Installed on 2016-08-13 (150 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  PackageArchitecture: i386
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.15ubuntu0.2
  SourcePackage: alsa-lib
  Title: package libasound2:i386 1.1.0-0ubuntu1 failed to install/upgrade: 
package is in a very bad inconsistent state; you should  reinstall it before 
attempting configuration
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-lib/+bug/162/+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 1655122] ms10-34-mcdivittB0-kernel (arm64) - tests ran: 10, failed: 2

tests ran:  10, failed: 2;
  
http://kernel.ubuntu.com/testing/4.9.0-12.13-generic/ms10-34-mcdivittB0-kernel__4.9.0-12.13__2017-01-11_19-00-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/1655122

Title:
  linux: 4.9.0-12.13 -proposed tracker

Status in Kernel Development Workflow:
  In Progress
Status in Kernel Development Workflow automated-testing series:
  Incomplete
Status in Kernel Development Workflow prepare-package series:
  Fix Released
Status in Kernel Development Workflow prepare-package-meta series:
  Fix Released
Status in Kernel Development Workflow prepare-package-signed series:
  Fix Released
Status in Kernel Development Workflow promote-to-proposed series:
  Fix Released
Status in Kernel Development Workflow promote-to-release series:
  New
Status in Kernel Development Workflow regression-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Zesty:
  Confirmed

Bug description:
  This bug is for tracking the 4.9.0-12.13 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-development-workflow/+bug/1655122/+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 1655748] Re: linux-lts-vivid: 3.19.0-80.88~14.04.1 -proposed tracker

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

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

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

** Description changed:

  This bug is for tracking the 3.19.0-80.88~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 --
  kernel-stable-master-bug: 1655745
+ kernel-stable-phase-changed:Wednesday, 11. January 2017 20:02 UTC
+ kernel-stable-phase:Packaging

** Description changed:

  This bug is for tracking the 3.19.0-80.88~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 --
+ derivative-trackers-created: true
  kernel-stable-master-bug: 1655745
- kernel-stable-phase-changed:Wednesday, 11. January 2017 20:02 UTC
- kernel-stable-phase:Packaging
+ phase: Packaging

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

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

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  New
Status in Kernel SRU Workflow prepare-package series:
  Confirmed
Status in Kernel SRU Workflow prepare-package-meta series:
  Confirmed
Status in Kernel SRU Workflow prepare-package-signed series:
  Confirmed
Status in Kernel SRU Workflow promote-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
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-80.88~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 --
  derivative-trackers-created: true
  kernel-stable-master-bug: 1655745
  phase: Packaging

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

Backport packages from packages here can be worked on, the following tracking 
bugs were opened for them:
linux-lts-vivid (14.04.1) - bug 1655748

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

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

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

** Description changed:

  This bug is for tracking the 3.19.0-80.88 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
+ 
+ kernel-stable-phase-changed:Wednesday, 11. January 2017 19:46 UTC
+ kernel-stable-phase:Packaging

** Description changed:

  This bug is for tracking the 3.19.0-80.88 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
  
  kernel-stable-phase-changed:Wednesday, 11. January 2017 19:46 UTC
  kernel-stable-phase:Packaging
+ 
+ -- swm properties --
+ derivative-trackers-created: true
+ phase: Packaging

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

Title:
  linux: 3.19.0-80.88 -proposed tracker

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

Bug description:
  This bug is for tracking the 3.19.0-80.88 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

  kernel-stable-phase-changed:Wednesday, 11. January 2017 19:46 UTC
  kernel-stable-phase:Packaging

  -- swm properties --
  derivative-trackers-created: true
  phase: Packaging

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1655745/+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 1655748] [NEW] linux-lts-vivid: 3.19.0-80.88~14.04.1 -proposed tracker

Public bug reported:

This bug is for tracking the 3.19.0-80.88~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 --
kernel-stable-master-bug: 1655745

** Affects: kernel-sru-workflow
 Importance: Medium
 Status: In Progress

** Affects: kernel-sru-workflow/automated-testing
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/certification-testing
 Importance: Medium
 Assignee: Canonical Hardware Certification (canonical-hw-cert)
 Status: New

** Affects: kernel-sru-workflow/prepare-package
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/prepare-package-meta
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/prepare-package-signed
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/promote-to-proposed
 Importance: Medium
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru)
 Status: New

** Affects: kernel-sru-workflow/promote-to-security
 Importance: Medium
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru)
 Status: New

** Affects: kernel-sru-workflow/promote-to-updates
 Importance: Medium
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru)
 Status: New

** Affects: kernel-sru-workflow/regression-testing
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/security-signoff
 Importance: Medium
 Assignee: Canonical Security Team (canonical-security)
 Status: New

** Affects: kernel-sru-workflow/verification-testing
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: linux-lts-vivid (Ubuntu)
 Importance: Undecided
 Status: Invalid

** Affects: linux-lts-vivid (Ubuntu Trusty)
 Importance: Medium
 Status: Confirmed


** Tags: block-proposed-trusty kernel-release-tracking-bug trusty

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

** Tags added: block-proposed-trusty

** Also affects: linux-lts-vivid (Ubuntu Trusty)
   Importance: Undecided
   Status: New

** Tags added: trusty

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

** Also affects: kernel-sru-workflow/automated-testing
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/certification-testing
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/prepare-package
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/prepare-package-meta
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/prepare-package-signed
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/promote-to-proposed
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/promote-to-security
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/promote-to-updates
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/regression-testing
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/security-signoff
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/verification-testing
   Importance: Undecided
   Status: New

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

** Changed in: kernel-sru-workflow
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/automated-testing
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/automated-testing
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

** Changed in: kernel-sru-workflow/certification-testing
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/certification-testing
 Assignee: (unassigned) => Canonical Hardware Certification 
(canonical-hw-cert)

** Changed in: kernel-sru-workflow/prepare-package
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/prepare-package
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

** Changed in: kernel-sru-workflow/prepare-package-meta
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/prepare-package-meta
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

** Changed in: kernel-sru-workflow/prepare-package-signed
   Importance: Undecided => Medium

** Changed in:

[Kernel-packages] [Bug 1571798] Re: Broadwell ECRC Support missing in Ubuntu

2017-01-11 Thread Mark W Wenning

Bjorn Helgaas, have you looked at the ACPI dump?   Any suggestions on
how to proceed?

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

Title:
  Broadwell ECRC Support missing in Ubuntu

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Vivid:
  In Progress
Status in linux source package in Wily:
  In Progress
Status in linux source package in Xenial:
  In Progress
Status in linux source package in Yakkety:
  In Progress

Bug description:
  Here is the problem statement from the Dell team:

  When booting into Ubuntu 14.04.4 with a Broadwell CPU and an Intel
  Quick Assist Card, the memory location that corresponds to ECRC is set
  to 0x01e0, when the BIOS is setting this location 0x00a0 pre-OS boot.
  This causes the card to not function unless we implement the following
  workaround using setpci.

  “setpci –s AA:BB.C 160.w=0”, where AA:BB.C is the PCI Root Path for
  the Intel Quick Assit Card.

  We’ve verified the memory location is correct when booting to other
  OSes, such as RHEL 7.2 and Windows Server 2012 R2.

  If there is any information you can give as to why this may be
  occurring in Ubuntu or where we may start to debug when the memory is
  changed, we would appreciate it.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1571798/+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 1653796] Re: eSATA external drive not recognized by Ubuntu Studio

still not showing after reboot with new kernel.  uname -r shows v4.10.


** Attachment added: "still-not-showing-by-rescanning.png"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1653796/+attachment/4803036/+files/still-not-showing-by-rescanning.png

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

Title:
  eSATA external drive not recognized by Ubuntu Studio

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  did a search for similar problems and found an old bug from earlier
  versions of Ubuntu: bug 153768.

  old bug report said to try some of these things, which I did..

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-57-lowlatency 4.4.0-57.78
  ProcVersionSignature: Ubuntu 4.4.0-57.78-lowlatency 4.4.35
  Uname: Linux 4.4.0-57-lowlatency x86_64
  ApportVersion: 2.20.1-0ubuntu2.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  Edward-admin   1721 F pulseaudio
  CurrentDesktop: XFCE
  Date: Tue Jan  3 13:37:32 2017
  GvfsMonitorLog: Monitoring events. Press Ctrl+C to quit.
  HibernationDevice: RESUME=UUID=cd636119-7499-4207-a479-13ab3d7c7d28
  HotplugNewDevices:
   
  HotplugNewMounts:
   
  InstallationDate: Installed on 2016-12-19 (15 days ago)
  InstallationMedia: Ubuntu-Studio 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  JournalErrors:
   Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] 
failed with exit code 1: Hint: You are currently not seeing messages from other 
users and the system.
 Users in the 'systemd-journal' group can see all messages. Pass -q to
 turn off this notice.
   No journal files were opened due to insufficient permissions.
  MachineType: Motherboard by ZOTAC ZBOX-CI320NANO series
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-57-lowlatency 
root=UUID=838e029d-694d-496b-b3ef-116bf1ff4afa ro quiet splash 
intel_idle.max_cstate=2 vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-57-lowlatency N/A
   linux-backports-modules-4.4.0-57-lowlatency  N/A
   linux-firmware   1.157.6
  SourcePackage: linux
  Symptom: storage
  UdevMonitorLog:
   monitor will print the received events for:
   UDEV - the event which udev sends out after rule processing
  UdisksMonitorLog:
   Monitoring the udisks daemon. Press Ctrl+C to exit.
   13:37:57.897: The udisks-daemon is running (name-owner :1.52).
  UpgradeStatus: No upgrade log present (probably fresh install)
  WifiSyslog:
   
  dmi.bios.date: 07/16/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: B219P027
  dmi.board.asset.tag: N/A
  dmi.board.name: ZBOX-CI320NANO series
  dmi.board.vendor: ZOTAC
  dmi.board.version: Rev.00
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrB219P027:bd07/16/2015:svnMotherboardbyZOTAC:pnZBOX-CI320NANOseries:pvrRev.00:rvnZOTAC:rnZBOX-CI320NANOseries:rvrRev.00:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: ZBOX-CI320NANO series
  dmi.product.version: Rev.00
  dmi.sys.vendor: Motherboard by ZOTAC

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1653796/+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 1655745] [NEW] linux: 3.19.0-80.88 -proposed tracker

2017-01-11 Thread John Donnelly

Public bug reported:

This bug is for tracking the 3.19.0-80.88 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

kernel-stable-phase-changed:Wednesday, 11. January 2017 19:46 UTC
kernel-stable-phase:Packaging

-- swm properties --
derivative-trackers-created: true
phase: Packaging

** Affects: kernel-sru-workflow
 Importance: Medium
 Status: In Progress

** Affects: kernel-sru-workflow/automated-testing
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/certification-testing
 Importance: Medium
 Assignee: Canonical Hardware Certification (canonical-hw-cert)
 Status: New

** Affects: kernel-sru-workflow/prepare-package
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: Confirmed

** Affects: kernel-sru-workflow/prepare-package-meta
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: Confirmed

** Affects: kernel-sru-workflow/prepare-package-signed
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: Confirmed

** Affects: kernel-sru-workflow/promote-to-proposed
 Importance: Medium
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru)
 Status: New

** Affects: kernel-sru-workflow/promote-to-security
 Importance: Medium
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru)
 Status: New

** Affects: kernel-sru-workflow/promote-to-updates
 Importance: Medium
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru)
 Status: New

** Affects: kernel-sru-workflow/regression-testing
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/security-signoff
 Importance: Medium
 Assignee: Canonical Security Team (canonical-security)
 Status: New

** Affects: kernel-sru-workflow/upload-to-ppa
 Importance: Medium
 Status: Invalid

** Affects: kernel-sru-workflow/verification-testing
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

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


** Tags: block-proposed-vivid kernel-release-tracking-bug vivid

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

** Tags added: block-proposed-vivid

** Tags added: vivid

** Also affects: kernel-sru-workflow/automated-testing
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/certification-testing
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/prepare-package
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/prepare-package-meta
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/prepare-package-signed
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/promote-to-proposed
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/promote-to-security
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/promote-to-updates
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/regression-testing
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/security-signoff
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/upload-to-ppa
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/verification-testing
   Importance: Undecided
   Status: New

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

** Changed in: kernel-sru-workflow
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/automated-testing
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/automated-testing
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

** Changed in: kernel-sru-workflow/certification-testing
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/certification-testing
 Assignee: (unassigned) => Canonical Hardware Certification 
(canonical-hw-cert)

** Changed in: kernel-sru-workflow/prepare-package
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/prepare-package
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

** Changed in: kernel-sru-workflow/prepare-package-meta
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/prepare-package-meta
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

** Changed in: kernel-sru-workflow/prepare-package-signed
   Importance: Undecided => Medium

**

[Kernel-packages] [Bug 1653796] Re: eSATA external drive not recognized by Ubuntu Studio

using "all" header package installed ok.
Then after that the image packages for generic and low latency both installed 
but with error "Possible missing firmware"
see attached.
haven't reboot yet..

** Attachment added: "possible-missing-firmware.png"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1653796/+attachment/4803035/+files/possible-missing-firmware.png

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

Title:
  eSATA external drive not recognized by Ubuntu Studio

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  did a search for similar problems and found an old bug from earlier
  versions of Ubuntu: bug 153768.

  old bug report said to try some of these things, which I did..

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-57-lowlatency 4.4.0-57.78
  ProcVersionSignature: Ubuntu 4.4.0-57.78-lowlatency 4.4.35
  Uname: Linux 4.4.0-57-lowlatency x86_64
  ApportVersion: 2.20.1-0ubuntu2.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  Edward-admin   1721 F pulseaudio
  CurrentDesktop: XFCE
  Date: Tue Jan  3 13:37:32 2017
  GvfsMonitorLog: Monitoring events. Press Ctrl+C to quit.
  HibernationDevice: RESUME=UUID=cd636119-7499-4207-a479-13ab3d7c7d28
  HotplugNewDevices:
   
  HotplugNewMounts:
   
  InstallationDate: Installed on 2016-12-19 (15 days ago)
  InstallationMedia: Ubuntu-Studio 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  JournalErrors:
   Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] 
failed with exit code 1: Hint: You are currently not seeing messages from other 
users and the system.
 Users in the 'systemd-journal' group can see all messages. Pass -q to
 turn off this notice.
   No journal files were opened due to insufficient permissions.
  MachineType: Motherboard by ZOTAC ZBOX-CI320NANO series
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-57-lowlatency 
root=UUID=838e029d-694d-496b-b3ef-116bf1ff4afa ro quiet splash 
intel_idle.max_cstate=2 vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-57-lowlatency N/A
   linux-backports-modules-4.4.0-57-lowlatency  N/A
   linux-firmware   1.157.6
  SourcePackage: linux
  Symptom: storage
  UdevMonitorLog:
   monitor will print the received events for:
   UDEV - the event which udev sends out after rule processing
  UdisksMonitorLog:
   Monitoring the udisks daemon. Press Ctrl+C to exit.
   13:37:57.897: The udisks-daemon is running (name-owner :1.52).
  UpgradeStatus: No upgrade log present (probably fresh install)
  WifiSyslog:
   
  dmi.bios.date: 07/16/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: B219P027
  dmi.board.asset.tag: N/A
  dmi.board.name: ZBOX-CI320NANO series
  dmi.board.vendor: ZOTAC
  dmi.board.version: Rev.00
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrB219P027:bd07/16/2015:svnMotherboardbyZOTAC:pnZBOX-CI320NANOseries:pvrRev.00:rvnZOTAC:rnZBOX-CI320NANOseries:rvrRev.00:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: ZBOX-CI320NANO series
  dmi.product.version: Rev.00
  dmi.sys.vendor: Motherboard by ZOTAC

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1653796/+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 1653796] Re: eSATA external drive not recognized by Ubuntu Studio

First new kernel install attempt failed. See attached.

** Attachment added: "Errors-EncounteredWhileProcessing.png"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1653796/+attachment/4803034/+files/Errors-EncounteredWhileProcessing.png

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

Title:
  eSATA external drive not recognized by Ubuntu Studio

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  did a search for similar problems and found an old bug from earlier
  versions of Ubuntu: bug 153768.

  old bug report said to try some of these things, which I did..

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-57-lowlatency 4.4.0-57.78
  ProcVersionSignature: Ubuntu 4.4.0-57.78-lowlatency 4.4.35
  Uname: Linux 4.4.0-57-lowlatency x86_64
  ApportVersion: 2.20.1-0ubuntu2.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  Edward-admin   1721 F pulseaudio
  CurrentDesktop: XFCE
  Date: Tue Jan  3 13:37:32 2017
  GvfsMonitorLog: Monitoring events. Press Ctrl+C to quit.
  HibernationDevice: RESUME=UUID=cd636119-7499-4207-a479-13ab3d7c7d28
  HotplugNewDevices:
   
  HotplugNewMounts:
   
  InstallationDate: Installed on 2016-12-19 (15 days ago)
  InstallationMedia: Ubuntu-Studio 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  JournalErrors:
   Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] 
failed with exit code 1: Hint: You are currently not seeing messages from other 
users and the system.
 Users in the 'systemd-journal' group can see all messages. Pass -q to
 turn off this notice.
   No journal files were opened due to insufficient permissions.
  MachineType: Motherboard by ZOTAC ZBOX-CI320NANO series
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-57-lowlatency 
root=UUID=838e029d-694d-496b-b3ef-116bf1ff4afa ro quiet splash 
intel_idle.max_cstate=2 vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-57-lowlatency N/A
   linux-backports-modules-4.4.0-57-lowlatency  N/A
   linux-firmware   1.157.6
  SourcePackage: linux
  Symptom: storage
  UdevMonitorLog:
   monitor will print the received events for:
   UDEV - the event which udev sends out after rule processing
  UdisksMonitorLog:
   Monitoring the udisks daemon. Press Ctrl+C to exit.
   13:37:57.897: The udisks-daemon is running (name-owner :1.52).
  UpgradeStatus: No upgrade log present (probably fresh install)
  WifiSyslog:
   
  dmi.bios.date: 07/16/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: B219P027
  dmi.board.asset.tag: N/A
  dmi.board.name: ZBOX-CI320NANO series
  dmi.board.vendor: ZOTAC
  dmi.board.version: Rev.00
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrB219P027:bd07/16/2015:svnMotherboardbyZOTAC:pnZBOX-CI320NANOseries:pvrRev.00:rvnZOTAC:rnZBOX-CI320NANOseries:rvrRev.00:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: ZBOX-CI320NANO series
  dmi.product.version: Rev.00
  dmi.sys.vendor: Motherboard by ZOTAC

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1653796/+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 1653796] Re: eSATA external drive not recognized by Ubuntu Studio

above comment shows that it may have to do with my dual boot system of
Centos 7 and Ubuntu Studio.

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

Title:
  eSATA external drive not recognized by Ubuntu Studio

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  did a search for similar problems and found an old bug from earlier
  versions of Ubuntu: bug 153768.

  old bug report said to try some of these things, which I did..

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-57-lowlatency 4.4.0-57.78
  ProcVersionSignature: Ubuntu 4.4.0-57.78-lowlatency 4.4.35
  Uname: Linux 4.4.0-57-lowlatency x86_64
  ApportVersion: 2.20.1-0ubuntu2.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  Edward-admin   1721 F pulseaudio
  CurrentDesktop: XFCE
  Date: Tue Jan  3 13:37:32 2017
  GvfsMonitorLog: Monitoring events. Press Ctrl+C to quit.
  HibernationDevice: RESUME=UUID=cd636119-7499-4207-a479-13ab3d7c7d28
  HotplugNewDevices:
   
  HotplugNewMounts:
   
  InstallationDate: Installed on 2016-12-19 (15 days ago)
  InstallationMedia: Ubuntu-Studio 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  JournalErrors:
   Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] 
failed with exit code 1: Hint: You are currently not seeing messages from other 
users and the system.
 Users in the 'systemd-journal' group can see all messages. Pass -q to
 turn off this notice.
   No journal files were opened due to insufficient permissions.
  MachineType: Motherboard by ZOTAC ZBOX-CI320NANO series
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-57-lowlatency 
root=UUID=838e029d-694d-496b-b3ef-116bf1ff4afa ro quiet splash 
intel_idle.max_cstate=2 vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-57-lowlatency N/A
   linux-backports-modules-4.4.0-57-lowlatency  N/A
   linux-firmware   1.157.6
  SourcePackage: linux
  Symptom: storage
  UdevMonitorLog:
   monitor will print the received events for:
   UDEV - the event which udev sends out after rule processing
  UdisksMonitorLog:
   Monitoring the udisks daemon. Press Ctrl+C to exit.
   13:37:57.897: The udisks-daemon is running (name-owner :1.52).
  UpgradeStatus: No upgrade log present (probably fresh install)
  WifiSyslog:
   
  dmi.bios.date: 07/16/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: B219P027
  dmi.board.asset.tag: N/A
  dmi.board.name: ZBOX-CI320NANO series
  dmi.board.vendor: ZOTAC
  dmi.board.version: Rev.00
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrB219P027:bd07/16/2015:svnMotherboardbyZOTAC:pnZBOX-CI320NANOseries:pvrRev.00:rvnZOTAC:rnZBOX-CI320NANOseries:rvrRev.00:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: ZBOX-CI320NANO series
  dmi.product.version: Rev.00
  dmi.sys.vendor: Motherboard by ZOTAC

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1653796/+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 1653796] Re: eSATA external drive not recognized by Ubuntu Studio

I will be following the instructions from
https://wiki.ubuntu.com/Kernel/MainlineBuilds?action=show=KernelMainlineBuilds
to try out the newest upstream 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/1653796

Title:
  eSATA external drive not recognized by Ubuntu Studio

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  did a search for similar problems and found an old bug from earlier
  versions of Ubuntu: bug 153768.

  old bug report said to try some of these things, which I did..

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-57-lowlatency 4.4.0-57.78
  ProcVersionSignature: Ubuntu 4.4.0-57.78-lowlatency 4.4.35
  Uname: Linux 4.4.0-57-lowlatency x86_64
  ApportVersion: 2.20.1-0ubuntu2.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  Edward-admin   1721 F pulseaudio
  CurrentDesktop: XFCE
  Date: Tue Jan  3 13:37:32 2017
  GvfsMonitorLog: Monitoring events. Press Ctrl+C to quit.
  HibernationDevice: RESUME=UUID=cd636119-7499-4207-a479-13ab3d7c7d28
  HotplugNewDevices:
   
  HotplugNewMounts:
   
  InstallationDate: Installed on 2016-12-19 (15 days ago)
  InstallationMedia: Ubuntu-Studio 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  JournalErrors:
   Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] 
failed with exit code 1: Hint: You are currently not seeing messages from other 
users and the system.
 Users in the 'systemd-journal' group can see all messages. Pass -q to
 turn off this notice.
   No journal files were opened due to insufficient permissions.
  MachineType: Motherboard by ZOTAC ZBOX-CI320NANO series
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-57-lowlatency 
root=UUID=838e029d-694d-496b-b3ef-116bf1ff4afa ro quiet splash 
intel_idle.max_cstate=2 vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-57-lowlatency N/A
   linux-backports-modules-4.4.0-57-lowlatency  N/A
   linux-firmware   1.157.6
  SourcePackage: linux
  Symptom: storage
  UdevMonitorLog:
   monitor will print the received events for:
   UDEV - the event which udev sends out after rule processing
  UdisksMonitorLog:
   Monitoring the udisks daemon. Press Ctrl+C to exit.
   13:37:57.897: The udisks-daemon is running (name-owner :1.52).
  UpgradeStatus: No upgrade log present (probably fresh install)
  WifiSyslog:
   
  dmi.bios.date: 07/16/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: B219P027
  dmi.board.asset.tag: N/A
  dmi.board.name: ZBOX-CI320NANO series
  dmi.board.vendor: ZOTAC
  dmi.board.version: Rev.00
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrB219P027:bd07/16/2015:svnMotherboardbyZOTAC:pnZBOX-CI320NANOseries:pvrRev.00:rvnZOTAC:rnZBOX-CI320NANOseries:rvrRev.00:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: ZBOX-CI320NANO series
  dmi.product.version: Rev.00
  dmi.sys.vendor: Motherboard by ZOTAC

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1653796/+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 1655122] ms10-35-mcdivittB0-kernel (arm64) - tests ran: 18, failed: 0

tests ran:  18, failed: 0;
  
http://kernel.ubuntu.com/testing/4.9.0-12.13-generic/ms10-35-mcdivittB0-kernel__4.9.0-12.13__2017-01-11_18-20-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/1655122

Title:
  linux: 4.9.0-12.13 -proposed tracker

Status in Kernel Development Workflow:
  In Progress
Status in Kernel Development Workflow automated-testing series:
  Incomplete
Status in Kernel Development Workflow prepare-package series:
  Fix Released
Status in Kernel Development Workflow prepare-package-meta series:
  Fix Released
Status in Kernel Development Workflow prepare-package-signed series:
  Fix Released
Status in Kernel Development Workflow promote-to-proposed series:
  Fix Released
Status in Kernel Development Workflow promote-to-release series:
  New
Status in Kernel Development Workflow regression-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Zesty:
  Confirmed

Bug description:
  This bug is for tracking the 4.9.0-12.13 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-development-workflow/+bug/1655122/+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 1655735] Re: Incompatible libdevmapper 1.02.136 (2016-11-05) and kernel driver (unknown version).

On Jan 11, 2017, at 06:30 PM, Brad Figg wrote:

>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 is probably a regression only on armhf, so the logs generated on amd64
won't be helpful.

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

Title:
  Incompatible libdevmapper 1.02.136 (2016-11-05) and kernel driver
  (unknown version).

Status in linux package in Ubuntu:
  Confirmed
Status in lvm2 package in Ubuntu:
  New
Status in multipath-tools package in Ubuntu:
  New

Bug description:
  There is a new Zesty regression on armhf, related to the autopkgtest
  for ubuntu-image.  Here's a log of a recent run:

https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
  /autopkgtest-zesty/zesty/armhf/u/ubuntu-
  image/20170111_171929_431b1@/log.gz

  Scroll to the bottom and you see this:

  Incompatible libdevmapper 1.02.136 (2016-11-05) and kernel driver (unknown 
version).
  device mapper prerequisites not met
  /dev/mapper/control: mknod failed: Operation not permitted
  Failure to communicate with kernel device-mapper driver.
  Check that device-mapper is available in the kernel.
  Incompatible libdevmapper 1.02.136 (2016-11-05) and kernel driver (unknown 
version).
  device mapper prerequisites not met

  Don't be misled by the gadget.yamls which name different
  architectures.  ubuntu-image should be able to build a disk image for
  any architecture on any architecture.

  What this test does is build the image, then run kpartx to map the
  partitions in the image, and then mount the partitions.  It doesn't do
  anything other than ensure that the partitions can be mounted, and
  this is where it's failing.

  This test succeeds on amd64, i386, and ppc64el.  It's never passed on
  s390x so that's not a regression.  It *used* to pass on armhf even on
  Zesty, but the recent upload of 0.13+17.10ubuntu2 displays the
  regression.

  I will bugtask this to libdevmapper and kpartx since it's possibly a
  bug in one of those packages (though I still suspect the kernel).

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: linux-image-4.9.0-11-generic 4.9.0-11.12
  ProcVersionSignature: Ubuntu 4.9.0-11.12-generic 4.9.0
  Uname: Linux 4.9.0-11-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair nvidia_uvm nvidia_drm 
nvidia_modeset nvidia
  ApportVersion: 2.20.4-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  barry  5414 F pulseaudio
   /dev/snd/controlC0:  barry  5414 F pulseaudio
  CurrentDesktop: Unity
  Date: Wed Jan 11 13:10:30 2017
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=8cc96f00-242f-42c6-bdb9-72db178f8864
  InstallationDate: Installed on 2016-01-22 (355 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160117)
  MachineType: Gigabyte Technology Co., Ltd. Z170X-UD5
  ProcFB:

  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.9.0-11-generic 
root=UUID=d03718f1-9983-4b07-a942-1b42fe8352ec ro
  RelatedPackageVersions:
   linux-restricted-modules-4.9.0-11-generic N/A
   linux-backports-modules-4.9.0-11-generic  N/A
   linux-firmware1.162
  RfKill:

  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/24/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F2
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z170X-UD5-CF
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF2:bd07/24/2015:svnGigabyteTechnologyCo.,Ltd.:pnZ170X-UD5:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ170X-UD5-CF:rvrx.x:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: Z170X-UD5
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1655735/+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 1655122] ms10-34-mcdivittB0-kernel (arm64) - tests ran: 18, failed: 0

tests ran:  18, failed: 0;
  
http://kernel.ubuntu.com/testing/4.9.0-12.13-generic/ms10-34-mcdivittB0-kernel__4.9.0-12.13__2017-01-11_17-56-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/1655122

Title:
  linux: 4.9.0-12.13 -proposed tracker

Status in Kernel Development Workflow:
  In Progress
Status in Kernel Development Workflow automated-testing series:
  Incomplete
Status in Kernel Development Workflow prepare-package series:
  Fix Released
Status in Kernel Development Workflow prepare-package-meta series:
  Fix Released
Status in Kernel Development Workflow prepare-package-signed series:
  Fix Released
Status in Kernel Development Workflow promote-to-proposed series:
  Fix Released
Status in Kernel Development Workflow promote-to-release series:
  New
Status in Kernel Development Workflow regression-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Zesty:
  Confirmed

Bug description:
  This bug is for tracking the 4.9.0-12.13 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-development-workflow/+bug/1655122/+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 1650336] Re: NFS client : kernel 4.4.0-57 crash with nfsv4 enries in /etc/fstab

Thanks for finding out the bug does not exist in the upstream 4.8
kernel.  There are only a couple more test kernels for the bisect, so we
may as well finish it.

I built the next test kernel, up to the following commit:
4891ae8e5d0801f13739c26300ac4cd162c3e63c

The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1650336


It might also be worthwhile to test the latest upstream 4.4 kernel to
see if the commit that fixes the bug in 4.8 was also cc'd to stable.

The latest 4.4 kernel is available from:
http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.4.41/

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

Title:
  NFS client : kernel 4.4.0-57 crash with nfsv4 enries in /etc/fstab

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

Bug description:
  On (K)ubuntu 16.04.01 (Xenial) Upgrading to kernel 4.4.0-57 the kernel
  crash on boot when in /etc/fstab a nfsv4 entry is active

  When comment the line or set to noauto the kernel boot with no error
  and mounting the nfs shares (after uncomment ) is also possible
  without error

  4.4.0-54 boots without this problem.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1650336/+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 1418339] Re: kernel set the wrong max_sectors_kb for 4K disks(sd.c)

2017-01-11 Thread Slava

I am also affected bu that bug
usb 2-5: new high-speed USB device number 2 using ehci-pci
[  248.566881] usb 2-5: New USB device found, idVendor=0c76, idProduct=0005
[  248.566885] usb 2-5: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[  248.566889] usb 2-5: Product: USB Flash Disk  
[  248.566891] usb 2-5: Manufacturer: SanDisk 
[  248.566894] usb 2-5: SerialNumber: 444553544200F040383D0C57
[  248.567386] usb-storage 2-5:1.0: USB Mass Storage device detected
[  248.570210] scsi host16: usb-storage 2-5:1.0
[  249.571364] scsi 16:0:0:0: Direct-Access SanDisk  USB Flash Disk   1.00 
PQ: 0 ANSI: 2
[  249.571994] sd 16:0:0:0: Attached scsi generic sg3 type 0
[  249.572507] sd 16:0:0:0: [sdd] 31273440 512-byte logical blocks: (16.0 
GB/14.9 GiB)
[  249.573227] sd 16:0:0:0: [sdd] Write Protect is off
[  249.573231] sd 16:0:0:0: [sdd] Mode Sense: 03 00 00 00
[  249.574568] sd 16:0:0:0: [sdd] No Caching mode page found
[  249.574575] sd 16:0:0:0: [sdd] Assuming drive cache: write through
[  249.580859]  sdd: sdd1
[  249.583771] sd 16:0:0:0: [sdd] Attached SCSI removable disk
[  249.608466] sd 16:0:0:0: [sdd] tag#0 FAILED Result: hostbyte=DID_OK 
driverbyte=DRIVER_SENSE
[  249.608472] sd 16:0:0:0: [sdd] tag#0 Sense Key : Illegal Request [current] 
[  249.608476] sd 16:0:0:0: [sdd] tag#0 Add. Sense: Invalid command operation 
code
[  249.608481] sd 16:0:0:0: [sdd] tag#0 CDB: Read(6) 08 00 08 00 08 00
[  249.608484] blk_update_request: critical target error, dev sdd, sector 2048

Disk works ok on Win 7 but not in ubuntu 16.04
uname -a
Linux *** 4.4.0-59-generic #80-Ubuntu SMP Fri Jan 6 17:36:54 UTC 2017 i686 i686 
i686 GNU/Linux

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

Title:
  kernel set the wrong max_sectors_kb for 4K disks(sd.c)

Status in linux package in Ubuntu:
  Fix Released

Bug description:
  [Impact]
  Problem Description
  ===
  We get following error messages on the console and IO fails.

  [   63.322503] sd 0:2:2:0: [sdc]
  [   63.322603] Result: hostbyte=DID_ERROR driverbyte=DRIVER_SENSE
  [   63.322661] sd 0:2:2:0: [sdc]
  [   63.322697] Sense Key : Illegal Request [current]
  [   63.322757] sd 0:2:2:0: [sdc]
  [   63.322792] Add. Sense: Invalid field in cdb
  [   63.322839] sd 0:2:2:0: [sdc] CDB:
  [   63.322874] Write(10): 2a 00 03 02 17 a0 00 00 80 00
  [   63.323038] blk_update_request: critical target error, dev sdc, sector 
403750144
  [   63.323117] sd 0:2:2:0: [sdc]
  [   63.323152] Result: hostbyte=DID_ERROR driverbyte=DRIVER_SENSE
  [   63.323210] sd 0:2:2:0: [sdc]
  [   63.323245] Sense Key : Illegal Request [current]
  [   63.323303] sd 0:2:2:0: [sdc]
  [   63.323338] Add. Sense: Invalid field in cdb
  [   63.323385] sd 0:2:2:0: [sdc] CDB:
  [   63.323420] Write(10): 2a 00 03 02 17 20 00 00 80 00
  [   63.323580] blk_update_request: critical target error, dev sdc, sector 
403749120

  [  138.410612] EXT4-fs warning (device dm-2): ext4_end_bio:317: I/O error 
-121 writing to inode 265776 (offset 0 size 393216 starting block 33920)
  [  138.410727] Buffer I/O error on device dm-2, logical block 33920
  [  138.410785] Buffer I/O error on device dm-2, logical block 33921
  [  138.410842] Buffer I/O error on device dm-2, logical block 33922
  [  138.410900] Buffer I/O error on device dm-2, logical block 33923
  [  138.410957] Buffer I/O error on device dm-2, logical block 33924

  ---uname output---
  Ubuntu 15.04

  Machine Type = P8(Alpine)

  [Test Case]
  Steps to Reproduce
  =
   read/write to a 4K array.

  [Fix]
  commit 3a9794d32984b67a6d8992226918618f0e51e5d5 upstream

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

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

apport-collect 1655735

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

Title:
  Incompatible libdevmapper 1.02.136 (2016-11-05) and kernel driver
  (unknown version).

Status in linux package in Ubuntu:
  Incomplete
Status in lvm2 package in Ubuntu:
  New
Status in multipath-tools package in Ubuntu:
  New

Bug description:
  There is a new Zesty regression on armhf, related to the autopkgtest
  for ubuntu-image.  Here's a log of a recent run:

  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
  /autopkgtest-zesty/zesty/armhf/u/ubuntu-
  image/20170111_171929_431b1@/log.gz

  Scroll to the bottom and you see this:

  Incompatible libdevmapper 1.02.136 (2016-11-05) and kernel driver (unknown 
version).
  device mapper prerequisites not met
  /dev/mapper/control: mknod failed: Operation not permitted
  Failure to communicate with kernel device-mapper driver.
  Check that device-mapper is available in the kernel.
  Incompatible libdevmapper 1.02.136 (2016-11-05) and kernel driver (unknown 
version).
  device mapper prerequisites not met

  Don't be misled by the gadget.yamls which name different
  architectures.  ubuntu-image should be able to build a disk image for
  any architecture on any architecture.

  What this test does is build the image, then run kpartx to map the
  partitions in the image, and then mount the partitions.  It doesn't do
  anything other than ensure that the partitions can be mounted, and
  this is where it's failing.

  This test succeeds on amd64, i386, and ppc64el.  It's never passed on
  s390x so that's not a regression.  It *used* to pass on armhf even on
  Zesty, but the recent upload of 0.13+17.10ubuntu2 displays the
  regression.

  I will bugtask this to libdevmapper and kpartx since it's possibly a
  bug in one of those packages (though I still suspect the kernel).

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: linux-image-4.9.0-11-generic 4.9.0-11.12
  ProcVersionSignature: Ubuntu 4.9.0-11.12-generic 4.9.0
  Uname: Linux 4.9.0-11-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair nvidia_uvm nvidia_drm 
nvidia_modeset nvidia
  ApportVersion: 2.20.4-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  barry  5414 F pulseaudio
   /dev/snd/controlC0:  barry  5414 F pulseaudio
  CurrentDesktop: Unity
  Date: Wed Jan 11 13:10:30 2017
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=8cc96f00-242f-42c6-bdb9-72db178f8864
  InstallationDate: Installed on 2016-01-22 (355 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160117)
  MachineType: Gigabyte Technology Co., Ltd. Z170X-UD5
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.9.0-11-generic 
root=UUID=d03718f1-9983-4b07-a942-1b42fe8352ec ro
  RelatedPackageVersions:
   linux-restricted-modules-4.9.0-11-generic N/A
   linux-backports-modules-4.9.0-11-generic  N/A
   linux-firmware1.162
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/24/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F2
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z170X-UD5-CF
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF2:bd07/24/2015:svnGigabyteTechnologyCo.,Ltd.:pnZ170X-UD5:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ170X-UD5-CF:rvrx.x:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: Z170X-UD5
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1655735/+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 1655735] Re: Incompatible libdevmapper 1.02.136 (2016-11-05) and kernel driver (unknown version).

Removed unhelpful attachments and retagged to armhf.

** Also affects: lvm2 (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: multipath-tools (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  Incompatible libdevmapper 1.02.136 (2016-11-05) and kernel driver
  (unknown version).

Status in linux package in Ubuntu:
  Incomplete
Status in lvm2 package in Ubuntu:
  New
Status in multipath-tools package in Ubuntu:
  New

Bug description:
  There is a new Zesty regression on armhf, related to the autopkgtest
  for ubuntu-image.  Here's a log of a recent run:

  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
  /autopkgtest-zesty/zesty/armhf/u/ubuntu-
  image/20170111_171929_431b1@/log.gz

  Scroll to the bottom and you see this:

  Incompatible libdevmapper 1.02.136 (2016-11-05) and kernel driver (unknown 
version).
  device mapper prerequisites not met
  /dev/mapper/control: mknod failed: Operation not permitted
  Failure to communicate with kernel device-mapper driver.
  Check that device-mapper is available in the kernel.
  Incompatible libdevmapper 1.02.136 (2016-11-05) and kernel driver (unknown 
version).
  device mapper prerequisites not met

  Don't be misled by the gadget.yamls which name different
  architectures.  ubuntu-image should be able to build a disk image for
  any architecture on any architecture.

  What this test does is build the image, then run kpartx to map the
  partitions in the image, and then mount the partitions.  It doesn't do
  anything other than ensure that the partitions can be mounted, and
  this is where it's failing.

  This test succeeds on amd64, i386, and ppc64el.  It's never passed on
  s390x so that's not a regression.  It *used* to pass on armhf even on
  Zesty, but the recent upload of 0.13+17.10ubuntu2 displays the
  regression.

  I will bugtask this to libdevmapper and kpartx since it's possibly a
  bug in one of those packages (though I still suspect the kernel).

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: linux-image-4.9.0-11-generic 4.9.0-11.12
  ProcVersionSignature: Ubuntu 4.9.0-11.12-generic 4.9.0
  Uname: Linux 4.9.0-11-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair nvidia_uvm nvidia_drm 
nvidia_modeset nvidia
  ApportVersion: 2.20.4-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  barry  5414 F pulseaudio
   /dev/snd/controlC0:  barry  5414 F pulseaudio
  CurrentDesktop: Unity
  Date: Wed Jan 11 13:10:30 2017
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=8cc96f00-242f-42c6-bdb9-72db178f8864
  InstallationDate: Installed on 2016-01-22 (355 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160117)
  MachineType: Gigabyte Technology Co., Ltd. Z170X-UD5
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.9.0-11-generic 
root=UUID=d03718f1-9983-4b07-a942-1b42fe8352ec ro
  RelatedPackageVersions:
   linux-restricted-modules-4.9.0-11-generic N/A
   linux-backports-modules-4.9.0-11-generic  N/A
   linux-firmware1.162
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/24/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F2
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z170X-UD5-CF
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF2:bd07/24/2015:svnGigabyteTechnologyCo.,Ltd.:pnZ170X-UD5:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ170X-UD5-CF:rvrx.x:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: Z170X-UD5
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1655735/+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 1655735] [NEW] Incompatible libdevmapper 1.02.136 (2016-11-05) and kernel driver (unknown version).

Public bug reported:

There is a new Zesty regression on armhf, related to the autopkgtest for
ubuntu-image.  Here's a log of a recent run:

https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
/autopkgtest-zesty/zesty/armhf/u/ubuntu-
image/20170111_171929_431b1@/log.gz

Scroll to the bottom and you see this:

Incompatible libdevmapper 1.02.136 (2016-11-05) and kernel driver (unknown 
version).
device mapper prerequisites not met
/dev/mapper/control: mknod failed: Operation not permitted
Failure to communicate with kernel device-mapper driver.
Check that device-mapper is available in the kernel.
Incompatible libdevmapper 1.02.136 (2016-11-05) and kernel driver (unknown 
version).
device mapper prerequisites not met

Don't be misled by the gadget.yamls which name different architectures.
ubuntu-image should be able to build a disk image for any architecture
on any architecture.

What this test does is build the image, then run kpartx to map the
partitions in the image, and then mount the partitions.  It doesn't do
anything other than ensure that the partitions can be mounted, and this
is where it's failing.

This test succeeds on amd64, i386, and ppc64el.  It's never passed on
s390x so that's not a regression.  It *used* to pass on armhf even on
Zesty, but the recent upload of 0.13+17.10ubuntu2 displays the
regression.

I will bugtask this to libdevmapper and kpartx since it's possibly a bug
in one of those packages (though I still suspect the kernel).

ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: linux-image-4.9.0-11-generic 4.9.0-11.12
ProcVersionSignature: Ubuntu 4.9.0-11.12-generic 4.9.0
Uname: Linux 4.9.0-11-generic x86_64
NonfreeKernelModules: zfs zunicode zavl zcommon znvpair nvidia_uvm nvidia_drm 
nvidia_modeset nvidia
ApportVersion: 2.20.4-0ubuntu1
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  barry  5414 F pulseaudio
 /dev/snd/controlC0:  barry  5414 F pulseaudio
CurrentDesktop: Unity
Date: Wed Jan 11 13:10:30 2017
EcryptfsInUse: Yes
HibernationDevice: RESUME=UUID=8cc96f00-242f-42c6-bdb9-72db178f8864
InstallationDate: Installed on 2016-01-22 (355 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160117)
MachineType: Gigabyte Technology Co., Ltd. Z170X-UD5
ProcFB:
 
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.9.0-11-generic 
root=UUID=d03718f1-9983-4b07-a942-1b42fe8352ec ro
RelatedPackageVersions:
 linux-restricted-modules-4.9.0-11-generic N/A
 linux-backports-modules-4.9.0-11-generic  N/A
 linux-firmware1.162
RfKill:
 
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/24/2015
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: F2
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: Z170X-UD5-CF
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: x.x
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF2:bd07/24/2015:svnGigabyteTechnologyCo.,Ltd.:pnZ170X-UD5:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ170X-UD5-CF:rvrx.x:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.name: Z170X-UD5
dmi.product.version: To be filled by O.E.M.
dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

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

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


** Tags: apport-bug armhf third-party-packages zesty

** Attachment removed: "AlsaInfo.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1655735/+attachment/4803005/+files/AlsaInfo.txt

** Attachment removed: "CRDA.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1655735/+attachment/4803006/+files/CRDA.txt

** Attachment removed: "CurrentDmesg.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1655735/+attachment/4803007/+files/CurrentDmesg.txt

** Attachment removed: "Dependencies.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1655735/+attachment/4803008/+files/Dependencies.txt

** Attachment removed: "IwConfig.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1655735/+attachment/4803009/+files/IwConfig.txt

** Attachment removed: "JournalErrors.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1655735/+attachment/4803010/+files/JournalErrors.txt

** Attachment removed: "Lspci.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1655735/+attachment/4803011/+files/Lspci.txt

** Attachment removed: "Lsusb.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1655735/+attachment/4803012/+files/Lsusb.txt

** Attachment removed: "ProcCpuinfo.txt"

[Kernel-packages] [Bug 1605974] Re: usbduxsigma_firmware.bin: old version causes driver crash

2017-01-11 Thread Łukasz Zemczak

Could this bug description get updated to follow the
https://wiki.ubuntu.com/StableReleaseUpdates#SRU_Bug_Template guideline?
Thank you!

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

Title:
  usbduxsigma_firmware.bin: old version causes driver crash

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

Bug description:
  The firmware of the usbduxsigma (alongside with the usbduxsigma.c) was
  updated in 2015 during a major rewrite but its binary was still the
  old one which causes the kernel driver to fail.

  I've submitted a patch to the kernel people (see below).

  However, as a quick fix could you also apply the patch to the package
  directly to have this fixed now and then we can wait until it trickles
  down from the kernel.

  I'm the maintainer of both the firmware and the drivers.

  This affects both 32 and 64 bit distros.

  Best,
  /Bernd Porr (www.linux-usb-daq.co.uk)

  Description:  Ubuntu 16.04.1 LTS
  Release:  16.04

  linux-firmware:
Installed: 1.157.2
Candidate: 1.157.2
Version table:
   *** 1.157.2 500
  500 http://gb.archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
  500 http://gb.archive.ubuntu.com/ubuntu xenial-updates/main i386 
Packages
  100 /var/lib/dpkg/status
   1.157 500
  500 http://gb.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  500 http://gb.archive.ubuntu.com/ubuntu xenial/main i386 Packages

  Expect to happen: plug in a duxduxsigma device, start comedirecord and see 
the signals plotted
  Happens instead: plug in a duxduxsigma device, start comedirecord and GARBLED 
DATA shows up / crash
  Fix: install this patch (new version of the firmware binary)

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-firmware 1.157.2 [modified: 
lib/firmware/usbduxsigma_firmware.bin]
  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
  CurrentDesktop: Unity
  Date: Sun Jul 24 10:04:19 2016
  Dependencies:
   
  InstallationDate: Installed on 2013-12-09 (957 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20131209)
  PackageArchitecture: all
  SourcePackage: linux-firmware
  UpgradeStatus: Upgraded to xenial on 2016-07-23 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1605974/+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 1647826] Re: intel 8260 doesn't work with linux kernel 4.8 when using ucode version 22

2017-01-11 Thread Łukasz Zemczak

Could this bug description get updated to follow the
https://wiki.ubuntu.com/StableReleaseUpdates#SRU_Bug_Template guideline?
Thank you!

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

Title:
  intel 8260 doesn't work with linux kernel 4.8 when using ucode version
  22

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

Bug description:
  The -22 microcode for the intel 8260 wifi adapter has compatibility
  issues with Linux Kernel 4.8 under certain hardware configurations.

  The iwlwifi module crashes resulting in wifi failing with "device not
  ready" and kernel errors reported in dmesg.

  [   10.691115] iwlwifi :6e:00.0: Microcode SW error detected.
  Restarting 0x200.

  Renaming the ucode file at /lib/firmware/iwlwifi-8000C-22.ucode to
  fallback to the -21 ucode resolves the issue and wifi begins working
  normally again.

  This is an issue with Linux kernel 4.8 on both yakkety and xenial, so
  the bug doesn't currently affect users on xenial, but will begin to
  after the 16.04.2 HWE release.  Kernel 4.4 is unaffected because it
  doesn't attempt to use the -22 ucode

  The failure doesn't necessarily affect all machines of a given model
  with the 8260, but I can reproduce it on multiple laptops when 64GB of
  RAM are installed (4x16GB).  The RAM itself does not appear to be an
  issue.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1647826/+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 1655071] Re: linux: 3.2.0-121.164 -proposed tracker

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

** Changed in: kernel-sru-workflow/prepare-package
 Assignee: Canonical Kernel Team (canonical-kernel-team) => John Donnelly 
(jpdonnelly)

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

Title:
  linux: 3.2.0-121.164 -proposed tracker

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

Bug description:
  This bug is for tracking the 3.2.0-121.164 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 --
  derivative-trackers-created: true
  phase: Uploaded

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1655071/+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 1655122] ms10-35-mcdivittB0-kernel (arm64) - tests ran: 1, failed: 0

tests ran:   1, failed: 0;
  
http://kernel.ubuntu.com/testing/4.9.0-12.13-generic/ms10-35-mcdivittB0-kernel__4.9.0-12.13__2017-01-11_17-56-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/1655122

Title:
  linux: 4.9.0-12.13 -proposed tracker

Status in Kernel Development Workflow:
  In Progress
Status in Kernel Development Workflow automated-testing series:
  Incomplete
Status in Kernel Development Workflow prepare-package series:
  Fix Released
Status in Kernel Development Workflow prepare-package-meta series:
  Fix Released
Status in Kernel Development Workflow prepare-package-signed series:
  Fix Released
Status in Kernel Development Workflow promote-to-proposed series:
  Fix Released
Status in Kernel Development Workflow promote-to-release series:
  New
Status in Kernel Development Workflow regression-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Zesty:
  Confirmed

Bug description:
  This bug is for tracking the 4.9.0-12.13 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-development-workflow/+bug/1655122/+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 1655122] Re: linux: 4.9.0-12.13 -proposed tracker

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

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

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

** Changed in: kernel-development-workflow/automated-testing
   Status: Confirmed => Incomplete

** Description changed:

  This bug is for tracking the 4.9.0-12.13 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: Uploaded
+ kernel-phase-changed:Wednesday, 11. January 2017 17:31 UTC
+ kernel-phase:Promoted to proposed

** Description changed:

  This bug is for tracking the 4.9.0-12.13 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: Uploaded
- kernel-phase-changed:Wednesday, 11. January 2017 17:31 UTC
- kernel-phase:Promoted to proposed
+ phase: Promoted to proposed
+ proposed-announcement-sent: true
+ proposed-testing-requested: true

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

Title:
  linux: 4.9.0-12.13 -proposed tracker

Status in Kernel Development Workflow:
  In Progress
Status in Kernel Development Workflow automated-testing series:
  Incomplete
Status in Kernel Development Workflow prepare-package series:
  Fix Released
Status in Kernel Development Workflow prepare-package-meta series:
  Fix Released
Status in Kernel Development Workflow prepare-package-signed series:
  Fix Released
Status in Kernel Development Workflow promote-to-proposed series:
  Fix Released
Status in Kernel Development Workflow promote-to-release series:
  New
Status in Kernel Development Workflow regression-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Zesty:
  Confirmed

Bug description:
  This bug is for tracking the 4.9.0-12.13 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-development-workflow/+bug/1655122/+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 1655476] Re: linux: 3.13.0-108.155 -proposed tracker

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

** Changed in: kernel-sru-workflow/prepare-package-meta
 Assignee: Canonical Kernel Team (canonical-kernel-team) => John Donnelly 
(jpdonnelly)

** Description changed:

  This bug is for tracking the 3.13.0-108.155 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
  
- kernel-stable-phase-changed:Tuesday, 10. January 2017 22:30 UTC
- kernel-stable-phase:Packaging
- 
  -- swm properties --
  derivative-trackers-created: true
  phase: Packaging
+ kernel-stable-phase-changed:Wednesday, 11. January 2017 17:16 UTC
+ kernel-stable-phase:Uploaded

** Description changed:

  This bug is for tracking the 3.13.0-108.155 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 --
  derivative-trackers-created: true
- phase: Packaging
- kernel-stable-phase-changed:Wednesday, 11. January 2017 17:16 UTC
- kernel-stable-phase:Uploaded
+ phase: Uploaded

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

Title:
  linux: 3.13.0-108.155 -proposed tracker

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

Bug description:
  This bug is for tracking the 3.13.0-108.155 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 --
  derivative-trackers-created: true
  phase: Uploaded

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1655476/+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 1542743] Re: Bluetooth: Patch file not found ar3k/AthrBT_0x00000200.dfu

2017-01-11 Thread chevrier

Thank you so much!! This works for Kernel 4.9.2
Your deb files allowed me to get bluetooth to work on all possible kernels...
you are the man!

i just need to figure out now how to get the sound to come out from the 
earphones when plugged in - that driver I downloaded for the old kernels does 
not seem to work for the newer one - a bit of a nuisance - i am using recon 3d 
i soundblaster, i think...  it's the standard on dell alienware i believe (m17 
r 2 for me)
many thanks

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

Title:
  Bluetooth: Patch file not found ar3k/AthrBT_0x0200.dfu

Status in bluez package in Ubuntu:
  Confirmed

Bug description:
  Since some Versions of Linux Kernel and Ubuntu Releases this problem
  exists.

  I am now running ubuntu 16.04 prerelease and still have the same
  problem.

  Bluetooth does not work with the atheros device on  msi gt 72 2qd
  notebook.

  WORKAROUND FOR [0CF3:3004] DEVICE ONLY with kernel 4.4:

  sudo apt install dkms
  wget 
https://launchpad.net/~hanipouspilot/+archive/ubuntu/bluetooth/+files/btusb-lp1542743-dkms_0.1_all.deb
  sudo dpkg -i btusb-lp1542743-dkms_0.1_all.deb

  FOR KERNEL 4.8 A WORKAROUND DKMS DEB IS

  https://launchpad.net/~hanipouspilot/+archive/ubuntu/bluetooth/+files
  /btusb-lp1542743-dkms_0.2~4.8_all.deb

  dmesg | grep Bluetooth:
  [2.655360] Bluetooth: Core ver 2.21
  [2.655373] Bluetooth: HCI device and connection manager initialized
  [2.655377] Bluetooth: HCI socket layer initialized
  [2.655379] Bluetooth: L2CAP socket layer initialized
  [2.655385] Bluetooth: SCO socket layer initialized
  [6.612790] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
  [6.612794] Bluetooth: BNEP filters: protocol multicast
  [6.612798] Bluetooth: BNEP socket layer initialized
  [9.016880] Bluetooth: Patch file not found ar3k/AthrBT_0x0200.dfu
  [9.016882] Bluetooth: Loading patch file failed

  hwinfo | grep Bluetooth:
  <6>[6.612790] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
    <6>[6.612794] Bluetooth: BNEP filters: protocol multicast
    <6>[6.612798] Bluetooth: BNEP socket layer initialized
    <3>[9.016880] Bluetooth: Patch file not found ar3k/AthrBT_0x0200.dfu
    <3>[9.016882] Bluetooth: Loading patch file failed
  60: USB 00.0: 11500 Bluetooth Device
    Model: "Atheros AR3012 Bluetooth 4.0"
    Device: usb 0x3004 "AR3012 Bluetooth 4.0"

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: bluez 5.36-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-2.16-generic 4.4.0
  Uname: Linux 4.4.0-2-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  ApportVersion: 2.19.4-0ubuntu2
  Architecture: amd64
  Date: Sun Feb  7 00:38:04 2016
  ExecutablePath: /usr/lib/bluetooth/bluetoothd
  InstallationDate: Installed on 2015-10-24 (105 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  InterestingModules: bnep btusb bluetooth
  MachineType: Micro-Star International Co., Ltd. GT72 2QD
  ProcEnviron:
   LANG=de_DE.UTF-8
   PATH=(custom, no user)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-2-generic 
root=UUID=f7880b23-39b5-423a-bdbf-62b111783450 ro quiet splash
  SourcePackage: bluez
  UpgradeStatus: Upgraded to xenial on 2016-02-02 (4 days ago)
  dmi.bios.date: 12/19/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: E1781IMS.10I
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: MS-1781
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: REV:0.C
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 10
  dmi.chassis.vendor: Micro-Star International Co., Ltd.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrE1781IMS.10I:bd12/19/2014:svnMicro-StarInternationalCo.,Ltd.:pnGT722QD:pvrREV0.C:rvnMicro-StarInternationalCo.,Ltd.:rnMS-1781:rvrREV0.C:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrToBeFilledByO.E.M.:
  dmi.product.name: GT72 2QD
  dmi.product.version: REV:0.C
  dmi.sys.vendor: Micro-Star International Co., Ltd.
  hciconfig:

  rfkill:
   0: phy0: Wireless LAN
    Soft blocked: yes
    Hard blocked: no

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1542743/+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 1491654] Re: Intel P3700 PCIe SSD string shows ''Unknown'' during Ubuntu 14.04 installation

Are you able to get any versions of Ubuntu to install on the system?

Maybe you could install Ubuntu on another disk, but still have the SSD
drives installed.  That will allow us to test various kernels and/or
patches to try and get the SSD to be recognized.

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

Title:
  Intel P3700 PCIe SSD string shows ''Unknown'' during Ubuntu 14.04
  installation

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Trusty:
  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:
  Current Behavior
  ==
  1. Intel P3700 PCIe SSD string shows "Unknow" during Ubuntu 14.04 install.

  Reference Verification
  ==
  1. Which version of previous BIOS/BMC/HW passed/failed? 1st Test
  2. Which similar project/product passed/failed? NA

  Steps to reproduce the problem
  ==
  1. Install Intel P3700 PCIe SSD*2 and SAS 12G HDD*8 with LSI 3108 into SUT.
  2. Power on system and install Ubuntu 14.04.
  3. Intel P3700 PCIe SSD string shows "Unknown" during OS install.

  Expected Behavior
  ==
  1. Intel P3700 PCIe SSD string should not show "Unknown" during Ubuntu 14.04 
install.

  Pcie SSD config:HDD/SSD:Intel,SSDPE2MD016T4,PCI-e,1.6TB,Gen3

  Copied from private bug:
  https://bugs.launchpad.net/quantatw/+bug/1454965

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1491654/+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 1655379] Re: Bug fixes for IBM VNIC Driver

2017-01-11 Thread Breno Leitão

** Attachment added: "generic.inclusion-list.log"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1655379/+attachment/4802923/+files/generic.inclusion-list.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/1655379

Title:
  Bug fixes for IBM VNIC Driver

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

Bug description:
  In order to bring the VNIC driver up to date and pull in fixes for all
  of the bugs we have seen we would need to have the following patches
  applied.

  
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/drivers/net/ethernet/ibm/ibmvnic.c?h=v4.10-rc3=12608c260d2fe36746508cb4fa20b6e9a5f9c241

  
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/drivers/net/ethernet/ibm/ibmvnic.c?h=v4.10-rc3=87737f8810db445db171ca81ca4cc43bd5b067ce

  
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/drivers/net/ethernet/ibm/ibmvnic.c?h=v4.10-rc3=d894be57ca92c8a8819ab544d550809e8731137b

  
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/drivers/net/ethernet/ibm/ibmvnic.c?h=v4.10-rc3=9888d7b02c7793cbbcbdd05dd9e14cc0e78d1db7

  
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/drivers/net/ethernet/ibm/ibmvnic.c?h=v4.10-rc3=8bf371e6adff29758cc3c57c17df4486513081f8

  
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/drivers/net/ethernet/ibm/ibmvnic.c?h=v4.10-rc3=6dbcd8fb5968fda3a5fba019dfb0c80c3139627b

  
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/drivers/net/ethernet/ibm/ibmvnic.c?h=v4.10-rc3=b7f193da17fb18b752bef77ce52eb49723299bd8

  
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/drivers/net/ethernet/ibm/ibmvnic.c?h=v4.10-rc3=e1fac0adf0f9b2c1eb49e658e6ed070a744bbaef

  I created a tree based on 16.04.2 kernel and included these commits.

  https://github.com/leitao/ubuntu-yakkety/tree/vnic

  I will be generating kernel binaries, so, we can test it.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1655379/+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 1655379] Re: Bug fixes for IBM VNIC Driver

2017-01-11 Thread Breno Leitão

In Fact, I am not able to find anything useful in these files, other
than the error. Take a look

** Attachment added: "generic.depmod.log"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1655379/+attachment/4802922/+files/generic.depmod.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/1655379

Title:
  Bug fixes for IBM VNIC Driver

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

Bug description:
  In order to bring the VNIC driver up to date and pull in fixes for all
  of the bugs we have seen we would need to have the following patches
  applied.

  
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/drivers/net/ethernet/ibm/ibmvnic.c?h=v4.10-rc3=12608c260d2fe36746508cb4fa20b6e9a5f9c241

  
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/drivers/net/ethernet/ibm/ibmvnic.c?h=v4.10-rc3=87737f8810db445db171ca81ca4cc43bd5b067ce

  
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/drivers/net/ethernet/ibm/ibmvnic.c?h=v4.10-rc3=d894be57ca92c8a8819ab544d550809e8731137b

  
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/drivers/net/ethernet/ibm/ibmvnic.c?h=v4.10-rc3=9888d7b02c7793cbbcbdd05dd9e14cc0e78d1db7

  
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/drivers/net/ethernet/ibm/ibmvnic.c?h=v4.10-rc3=8bf371e6adff29758cc3c57c17df4486513081f8

  
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/drivers/net/ethernet/ibm/ibmvnic.c?h=v4.10-rc3=6dbcd8fb5968fda3a5fba019dfb0c80c3139627b

  
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/drivers/net/ethernet/ibm/ibmvnic.c?h=v4.10-rc3=b7f193da17fb18b752bef77ce52eb49723299bd8

  
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/drivers/net/ethernet/ibm/ibmvnic.c?h=v4.10-rc3=e1fac0adf0f9b2c1eb49e658e6ed070a744bbaef

  I created a tree based on 16.04.2 kernel and included these commits.

  https://github.com/leitao/ubuntu-yakkety/tree/vnic

  I will be generating kernel binaries, so, we can test it.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1655379/+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 1655075] Re: linux-ti-omap4: 3.2.0-1499.126 -proposed tracker

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

** Changed in: kernel-sru-workflow/prepare-package
 Assignee: ubuntu-armel-kernel (ubuntu-armel-kernel) => John Donnelly 
(jpdonnelly)

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

Title:
  linux-ti-omap4: 3.2.0-1499.126 -proposed tracker

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

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

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1655075/+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 1655683] Re: kernel BUG at skbuff.h:1486 Insufficient linear data in skb __skb_pull.part.7+0x4/0x6 [openvswitch]

The kernel running in the above apport report is the patched kernel FYI.

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

Title:
  kernel BUG at skbuff.h:1486 Insufficient linear data in skb
  __skb_pull.part.7+0x4/0x6 [openvswitch]

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Since 2016-12-30 EST we have been experiencing repeated crashes of our
  OpenStack Icehouse / Trusty Neutron node with a kernel BUG at skbuff.h
  line 1486:

  1471 /**
  1472 * skb_peek - peek at the head of an _buff_head
  1473 * @list_: list to peek at
  1474 *
  1475 * Peek an _buff. Unlike most other operations you _MUST_
  1476 * be careful with this one. A peek leaves the buffer on the
  1477 * list and someone else may run off with it. You must hold
  1478 * the appropriate locks or have a private queue to do this.
  1479 *
  1480 * Returns %NULL for an empty list or a pointer to the head element.
  1481 * The reference count is not incremented and the reference is therefore
  1482 * volatile. Use with caution.
  1483 */
  1484 static inline struct sk_buff *skb_peek(const struct sk_buff_head *list_)
  1485 {
  1486 struct sk_buff *skb = list_->next;
  1487
  1488 if (skb == (struct sk_buff *)list_)
  1489 skb = NULL;
  1490 return skb;
  1491 }

  This generally results in a full panic crash of the Neutron node and
  connectivity breaking for VMs within the cloud. However, after using
  crash-dumptools to collect information on the crashes over the past
  three days, the kernel loaded by kexec during the crashdump appears in
  about 2 out of 3 crash instances to continue running, and we see a
  flap of the neutron services instead of a full panic that brings the
  Neutron server down and necessitates a hard reboot.

  I believe that this is a manifestation of the openvswitch and issue
  described on 2017-01-08 as:

  "OVS can only process L2 packets. But OVS GRE receive handler
  can accept IP-GRE packets. When such packet is processed by
  OVS datapath it can trigger following assert failure due
  to insufficient linear data in skb."

  https://patchwork.ozlabs.org/patch/712373/

  I have not tested the patch provided above yet.

  Other information and a few sample dmesg outputs from the crash:
  (multiple dumps available)

  # lsb_release -rd
  Description: Ubuntu 14.04.5 LTS
  Release: 14.04

  # apt-cache policy openvswitch
  N: Unable to locate package openvswitch
  root@neutron01:/var/crash# apt-cache policy openvswitch-common
  openvswitch-common:
Installed: 2.0.2-0ubuntu0.14.04.3
Candidate: 2.0.2-0ubuntu0.14.04.3
Version table:
   *** 2.0.2-0ubuntu0.14.04.3 0
  500 http://us.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   2.0.1+git20140120-0ubuntu2 0
  500 http://us.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages

  # apt-cache policy openvswitch-switch
  openvswitch-switch:
Installed: 2.0.2-0ubuntu0.14.04.3
Candidate: 2.0.2-0ubuntu0.14.04.3
Version table:
   *** 2.0.2-0ubuntu0.14.04.3 0
  500 http://us.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   2.0.1+git20140120-0ubuntu2 0
  500 http://us.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages

  # apt-cache policy neutron-plugin-openvswitch-agent
  neutron-plugin-openvswitch-agent:
Installed: 1:2014.1.5-0ubuntu7
Candidate: 1:2014.1.5-0ubuntu7
Version table:
   *** 1:2014.1.5-0ubuntu7 0
  500 http://us.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   1:2014.1.3-0ubuntu1.1 0
  500 http://security.ubuntu.com/ubuntu/ trusty-security/main amd64 
Packages
   1:2014.1-0ubuntu1 0
  500 http://us.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages

  example dmesg:

  ## dmesg.201701060019

  > [33100.131019] [ cut here ]
  > [33100.131176] kernel BUG at 
/build/linux-mi9H1O/linux-3.13.0/include/linux/skbuff.h:1486!
  > [33100.131424] invalid opcode:  [#1] SMP
  > [33100.131560] Modules linked in: xt_nat xt_conntrack ip6table_filter 
ip6_tables iptable_filter xt_REDIRECT xt_tcpudp iptable_nat nf_conntrack_ipv4 
nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack ip_tables x_tables veth 
openvswitch gre vxlan ip_tunnel libcrc32c ipmi_devintf gpio_ich cdc_ether 
x86_pkg_temp_thermal intel_powerclamp coretemp usbnet kvm_intel mii kvm 
crct10dif_pclmul crc32_pclmul ghash_clmulni_intel aesni_intel aes_x86_64 lrw 
gf128mul glue_helper ablk_helper cryptd sb_edac edac_core lpc_ich wmi ipmi_si 
bonding shpchp ioatdma lp mac_hid parport ahci libahci sfc igb e1000e mtd dca 
i2c_algo_bit ptp pps_core megaraid_sas mdio
  > [33100.133560] CPU: 2 PID: 0 Comm: swapper/2 Not

[Kernel-packages] [Bug 1655683] Re: kernel BUG at skbuff.h:1486 Insufficient linear data in skb __skb_pull.part.7+0x4/0x6 [openvswitch]

Sorry, apport-collect is trying to open a browser from a server where
none is installed. I generated the report with apport-cli and have
attached here instead.

** Attachment added: "apport.linux-image-3.13.0-106-generic.b9qc1535.apport"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1655683/+attachment/4802917/+files/apport.linux-image-3.13.0-106-generic.b9qc1535.apport

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

Title:
  kernel BUG at skbuff.h:1486 Insufficient linear data in skb
  __skb_pull.part.7+0x4/0x6 [openvswitch]

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Since 2016-12-30 EST we have been experiencing repeated crashes of our
  OpenStack Icehouse / Trusty Neutron node with a kernel BUG at skbuff.h
  line 1486:

  1471 /**
  1472 * skb_peek - peek at the head of an _buff_head
  1473 * @list_: list to peek at
  1474 *
  1475 * Peek an _buff. Unlike most other operations you _MUST_
  1476 * be careful with this one. A peek leaves the buffer on the
  1477 * list and someone else may run off with it. You must hold
  1478 * the appropriate locks or have a private queue to do this.
  1479 *
  1480 * Returns %NULL for an empty list or a pointer to the head element.
  1481 * The reference count is not incremented and the reference is therefore
  1482 * volatile. Use with caution.
  1483 */
  1484 static inline struct sk_buff *skb_peek(const struct sk_buff_head *list_)
  1485 {
  1486 struct sk_buff *skb = list_->next;
  1487
  1488 if (skb == (struct sk_buff *)list_)
  1489 skb = NULL;
  1490 return skb;
  1491 }

  This generally results in a full panic crash of the Neutron node and
  connectivity breaking for VMs within the cloud. However, after using
  crash-dumptools to collect information on the crashes over the past
  three days, the kernel loaded by kexec during the crashdump appears in
  about 2 out of 3 crash instances to continue running, and we see a
  flap of the neutron services instead of a full panic that brings the
  Neutron server down and necessitates a hard reboot.

  I believe that this is a manifestation of the openvswitch and issue
  described on 2017-01-08 as:

  "OVS can only process L2 packets. But OVS GRE receive handler
  can accept IP-GRE packets. When such packet is processed by
  OVS datapath it can trigger following assert failure due
  to insufficient linear data in skb."

  https://patchwork.ozlabs.org/patch/712373/

  I have not tested the patch provided above yet.

  Other information and a few sample dmesg outputs from the crash:
  (multiple dumps available)

  # lsb_release -rd
  Description: Ubuntu 14.04.5 LTS
  Release: 14.04

  # apt-cache policy openvswitch
  N: Unable to locate package openvswitch
  root@neutron01:/var/crash# apt-cache policy openvswitch-common
  openvswitch-common:
Installed: 2.0.2-0ubuntu0.14.04.3
Candidate: 2.0.2-0ubuntu0.14.04.3
Version table:
   *** 2.0.2-0ubuntu0.14.04.3 0
  500 http://us.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   2.0.1+git20140120-0ubuntu2 0
  500 http://us.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages

  # apt-cache policy openvswitch-switch
  openvswitch-switch:
Installed: 2.0.2-0ubuntu0.14.04.3
Candidate: 2.0.2-0ubuntu0.14.04.3
Version table:
   *** 2.0.2-0ubuntu0.14.04.3 0
  500 http://us.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   2.0.1+git20140120-0ubuntu2 0
  500 http://us.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages

  # apt-cache policy neutron-plugin-openvswitch-agent
  neutron-plugin-openvswitch-agent:
Installed: 1:2014.1.5-0ubuntu7
Candidate: 1:2014.1.5-0ubuntu7
Version table:
   *** 1:2014.1.5-0ubuntu7 0
  500 http://us.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   1:2014.1.3-0ubuntu1.1 0
  500 http://security.ubuntu.com/ubuntu/ trusty-security/main amd64 
Packages
   1:2014.1-0ubuntu1 0
  500 http://us.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages

  example dmesg:

  ## dmesg.201701060019

  > [33100.131019] [ cut here ]
  > [33100.131176] kernel BUG at 
/build/linux-mi9H1O/linux-3.13.0/include/linux/skbuff.h:1486!
  > [33100.131424] invalid opcode:  [#1] SMP
  > [33100.131560] Modules linked in: xt_nat xt_conntrack ip6table_filter 
ip6_tables iptable_filter xt_REDIRECT xt_tcpudp iptable_nat nf_conntrack_ipv4 
nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack ip_tables x_tables veth 
openvswitch gre vxlan ip_tunnel libcrc32c ipmi_devintf gpio_ich cdc_ether 
x86_pkg_temp_thermal intel_powerclamp coretemp usbnet kvm_intel mii kvm 
crct10dif_pclmul crc32_pclmul ghash_clmulni_intel aesni_intel aes_x86_64 lrw 
gf128mul

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

2017-01-11 Thread bugproxy

--- Comment From hbath...@in.ibm.com 2017-01-11 10:55 EDT---
Kernel commit f5509cc18daa ("mm: Hardened usercopy") introduced the
BUG() we are hitting here.

This BUG() was also hit while reading kcore, which was fixed with
kernel commit df04abfd181a ("fs/proc/kcore.c: Add bounce buffer
for ktext data"). Not convinced if similar fix is ideal here.
Working on the fix.

This issue is not just observed with ssh dump target but also with
other dump targets. Updated the bug summary accordingly..

Thanks
Hari

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

Title:
  Ubuntu 17.04: "Oops: Exception in kernel mode, sig: 5 [#1]" seen
  during fadump over ssh on Alpine machine.

Status in makedumpfile package in Ubuntu:
  New

Bug description:
  Problem Description
  
  "Oops: Exception in kernel mode, sig: 5 [#1]" seen during fadump over ssh on 
Alpine machine.

  Steps to Reproduce
  
  1. Configure fadump over ssh on Alpine machine.
  ssh-keygen -t rsa

  Add below lines in /etc/default/kdump-tools
  SSH="ubuntu@9.114.15.240"
  SSH_KEY=/root/.ssh/id_rsa

  # kdump-config propagate

  # kdump-config load

  # kdump-config show

  2. Trigger crash

  Logs
  ===
  ubuntu@alp9:~$ [   41.884641] usercopy: kernel memory exposure attempt 
detected from c000fb001020 (task_struct) (61408 bytes)
  [   41.884668] kernel BUG at /build/linux-okcqyo/linux-4.9.0/mm/usercopy.c:75!
  [   41.884672] Oops: Exception in kernel mode, sig: 5 [#1]
  [   41.884674] SMP NR_CPUS=2048 [   41.884676] NUMA 
  [   41.884677] pSeries
  [   41.884679] Modules linked in: pseries_rng vmx_crypto ib_iser rdma_cm 
iw_cm ib_cm ib_core configfs iscsi_tcp libiscsi_tcp libiscsi 
scsi_transport_iscsi ip_tables x_tables autofs4 btrfs raid10 raid456 
async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq 
libcrc32c raid1 raid0 multipath linear ibmvscsi lpfc crc32c_vpmsum 
scsi_transport_fc
  [   41.884714] CPU: 8 PID: 3977 Comm: makedumpfile Not tainted 
4.9.0-11-generic #12-Ubuntu
  [   41.884717] task: c00151fcdc00 task.stack: c00150064000
  [   41.884719] NIP: c0312978 LR: c0312974 CTR: 
006338e4
  [   41.884722] REGS: c001500678d0 TRAP: 0700   Not tainted  
(4.9.0-11-generic)
  [   41.884725] MSR: 80029033 [   41.884732]   
CR: 2800  XER: 0004
  [   41.884734] CFAR: c0b26cac SOFTE: 1 
  GPR00: c0312974 c00150067b50 c141a400 0063 
  GPR04: c00179a0ade8 c00179a1fc40 00a1b6ef  
  GPR08: 0007 c0f7f87c 000178a9 3ff0 
  GPR12: 2200 ce794800 3fff7f4d0010 3fff7f4d0010 
  GPR16: bb01 54150c98 5412da08 0001 
  GPR20: 540fea40 38448150 0001 c1717798 
  GPR24: 0001 c00150067cf0  1020 
  GPR28: c000fb01 0001 efe0 c000fb001020 
  NIP [c0312978] __check_object_size+0x88/0x2c0
  [   41.884777] LR [c0312974] __check_object_size+0x84/0x2c0
  [   41.884780] Call Trace:
  [   41.884782] [c00150067b50] [c0312974] 
__check_object_size+0x84/0x2c0 (unreliable)
  [   41.884787] [c00150067bd0] [c006aea4] copy_to_user+0x64/0xa0
  [   41.884791] [c00150067c10] [c0042360] 
copy_oldmem_page+0x140/0x1d0
  [   41.884796] [c00150067c60] [c03cd5a8] 
read_from_oldmem.part.0+0x138/0x150
  [   41.884800] [c00150067cd0] [c03cd6fc] read_vmcore+0x13c/0x270
  [   41.884803] [c00150067d40] [c03b8918] proc_reg_read+0x88/0xd0
  [   41.884807] [c00150067d70] [c0318f4c] __vfs_read+0x3c/0x70
  [   41.884811] [c00150067d90] [c031a1ac] vfs_read+0xbc/0x1b0
  [   41.884814] [c00150067de0] [c031bdc8] SyS_read+0x68/0x110
  [   41.884818] [c00150067e30] [c000bd84] system_call+0x38/0xe0
  [   41.884820] Instruction dump:
  [   41.884823] 6000 6042 3c82ff93 3ca2ff9d 38847130 38a5b3f8 3c62ff94 
7fc8f378 
  [   41.884830] 7fe6fb78 38635f20 488142dd 6000 <0fe0> 6042 
2ba30010 409d017c 
  [   41.884838] ---[ end trace c33ccad89db3894a ]---
  [   41.884840] 
  Copying data   : [ 43.7 %] -889527+439 records in
  [   41.805683] kdump-tools[3621]: 889744+1 records out
  [   41.805920] kdump-tools[3621]: 455549276 bytes (456 MB, 434 MiB) copied, 
24.5065 s, 18.6 MB/s
  [   42.263162] kdump-tools[3621]:  * kdump-tools: saved vmcore in 
ubuntu@9.114.15.240:/home/ubuntu/9.114.15.239-201701090710
  [   42.264882] kdump-tools[3621]:  * running makedumpfile --dump-dmesg 
/proc/vmcore /tmp/dmesg.201701090710
  [   42.268482] kdump-tools[3621]: The kernel version is not

[Kernel-packages] [Bug 1641235] Re: Ubuntu 16.10: kdump over nfs did not generate complete vmcore

2017-01-11 Thread bugproxy

--- Comment From ru...@us.ibm.com 2017-01-11 10:45 EDT---
Thanks for the update Louis

** Tags added: bugnameltc-148148 severity-high

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

Title:
  Ubuntu 16.10: kdump over nfs did not generate complete vmcore

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

Bug description:
  == Comment: #0 - HARSHA THYAGARAJA - 2016-11-03 08:05:59 ==
  ---Problem Description---
  kdump over nfs did not generate complete vmcore
   
  ---uname output---
  Linux ltciofvtr-firestone1 4.8.0-26-generic #28-Ubuntu SMP Tue Oct 18 
14:41:40 UTC 2016 ppc64le ppc64le ppc64le GNU/Linux
   
  Machine Type = PowerNV (Baremetal) - Firestone 
   
  ---Steps to Reproduce---
   1. Setup NFS
  2. Trigger crash: echo c > /proc/sysrq-trigger

  
  == Comment: #6 - Kevin W. Rudd - 2016-11-04 16:30:49 ==

  Hi Harsha.

  It looks like the base kdump NFS functionality works just fine.  The
  known issue with makedumpfile is causing it to drop back to using "cp"
  to transfer the entire, non-compressed /proc/vmcore image.  That's a
  rather large amount of data to send over to the remote server, and it
  appears to be sending back an I/O error after the first 122G.

  Further debug would need to be done to determine if this is a client-
  side or server-side issue.  I recommend first bringing your remote NFS
  server up to the current release as it is currently a bit down-rev.

  == Comment: #8 - HARSHA THYAGARAJA  - 2016-11-10 02:02:31 ==

  Hi Kevin,
  I updated my peer to Ubuntu 16.10 and still saw the same observation. 
  A snippet of the problem at hand is pasted below. 

  [   20.610748] kdump-tools[4559]: Starting kdump-tools:  * Mounting NFS 
mountpoint 150.1.1.20:/home/tools ...
  [   53.400516] kdump-tools[4559]:  * Dumping to NFS mountpoint 
150.1.1.20:/home/tools/201611100158
  [   53.409242] kdump-tools[4559]:  * running makedumpfile -c -d 31 
/proc/vmcore /mnt/var/crash/9.47.84.18-201611100158/dump-incomplete
  [   53.526593] kdump-tools[4559]: get_mem_map: Can't distinguish the memory 
type.
  [   53.527154] kdump-tools[4559]: The kernel version is not supported.
  [   53.527488] kdump-tools[4559]: The makedumpfile operation may be 
incomplete.
  [   53.527813] kdump-tools[4559]: makedumpfile Failed.
  [   53.528117] kdump-tools[4559]:  * kdump-tools: makedumpfile failed, 
falling back to 'cp'
  [   90.754092] kdump-tools[4559]: cp: error writing 
'/mnt/var/crash/9.47.84.18-201611100158/vmcore-incomplete': Input/output error
  [   90.754857] kdump-tools[4559]:  * kdump-tools: failed to save vmcore in 
/mnt/var/crash/9.47.84.18-201611100158
  [   90.756155] kdump-tools[4559]:  * running makedumpfile --dump-dmesg 
/proc/vmcore /mnt/var/crash/9.47.84.18-201611100158/dmesg.201611100158
  [   90.758731] kdump-tools[4559]: get_mem_map: Can't distinguish the memory 
type.
  [   90.759089] kdump-tools[4559]: The kernel version is not supported.
  [   90.759436] kdump-tools[4559]: The makedumpfile operation may be 
incomplete.
  [   90.759780] kdump-tools[4559]: makedumpfile Failed.
  [   90.760094] kdump-tools[4559]:  * kdump-tools: makedumpfile --dump-dmesg 
failed. dmesg content will be unavailable
  [   90.760668] kdump-tools[4559]:  * kdump-tools: failed to save dmesg 
content in /mnt/var/crash/9.47.84.18-201611100158
  [   90.846117] kdump-tools[4559]: Thu, 10 Nov 2016 01:59:56 -0500
  [   90.886629] kdump-tools[4559]: Failed to read reboot parameter file: No 
such file or directory
  [   90.887070] kdump-tools[4559]: Rebooting.

  == Comment: #13 - Kevin W. Rudd  - 2016-11-11 17:12:33 ==

  I was able to replicate this with debugging at both the kdump client
  and remote NFS server.  The server was perfectly happy with the data
  coming at it, and appeared to be processing a COMMIT request from the
  client when the client shut down the connection.

  Looking at the client-side logs after a failure showed that it was
  logging "server ... not responding" messages, and bailed on the
  connection within the span of just a few seconds.

  This appears to be due to a very over-aggressive timeout being
  specified in /usr/sbin/kdump-config:

  mount -t nfs -o nolock -o tcp -o soft -o timeo=5 -o retrans=5 $NFS
  $KDUMP_COREDIR

  The timeo value is deciseconds, and "5" is far too aggressive for this
  type of connection.  From my observations, the COMMIT was not issued
  until about 60G was transferred, and most remote servers will take a
  lot longer than 5 tenths of a second to flush that amount of data and
  respond to the COMMIT.

  I'm not sure what problem specifying this timeo value was supposed to
  address, but it would be better to leave the timeo value at its

[Kernel-packages] [Bug 1655075] Re: linux-ti-omap4: 3.2.0-1499.126 -proposed tracker

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

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

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

** Changed in: kernel-sru-workflow/prepare-package-meta
 Assignee: Canonical Kernel Team (canonical-kernel-team) => John Donnelly 
(jpdonnelly)

** Description changed:

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

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
+ derivative-trackers-created: true
  kernel-stable-master-bug: 1655071
- kernel-stable-phase-changed:Wednesday, 11. January 2017 15:46 UTC
- kernel-stable-phase:Uploaded
+ phase: Uploaded

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

Title:
  linux-ti-omap4: 3.2.0-1499.126 -proposed tracker

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

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

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

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

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

** Changed in: kernel-sru-workflow/prepare-package-meta
 Assignee: Canonical Kernel Team (canonical-kernel-team) => John Donnelly 
(jpdonnelly)

** Description changed:

  This bug is for tracking the 3.2.0-121.164 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
  
- kernel-stable-phase:Packaging
- kernel-stable-phase-changed:Monday, 09. January 2017 16:34 UTC
- 
  -- swm properties --
  derivative-trackers-created: true
  phase: Packaging
+ kernel-stable-phase-changed:Wednesday, 11. January 2017 15:48 UTC
+ kernel-stable-phase:Uploaded

** Description changed:

  This bug is for tracking the 3.2.0-121.164 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 --
  derivative-trackers-created: true
- phase: Packaging
- kernel-stable-phase-changed:Wednesday, 11. January 2017 15:48 UTC
- kernel-stable-phase:Uploaded
+ phase: Uploaded

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

Title:
  linux: 3.2.0-121.164 -proposed tracker

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

Bug description:
  This bug is for tracking the 3.2.0-121.164 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 --
  derivative-trackers-created: true
  phase: Uploaded

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1655071/+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 1655683] Re: kernel BUG at skbuff.h:1486 Insufficient linear data in skb __skb_pull.part.7+0x4/0x6 [openvswitch]

** Attachment added: "linux-image-3.13.0-106-generic-201701051502.crash"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1655683/+attachment/4802911/+files/linux-image-3.13.0-106-generic-201701051502.crash

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

Title:
  kernel BUG at skbuff.h:1486 Insufficient linear data in skb
  __skb_pull.part.7+0x4/0x6 [openvswitch]

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Since 2016-12-30 EST we have been experiencing repeated crashes of our
  OpenStack Icehouse / Trusty Neutron node with a kernel BUG at skbuff.h
  line 1486:

  1471 /**
  1472 * skb_peek - peek at the head of an _buff_head
  1473 * @list_: list to peek at
  1474 *
  1475 * Peek an _buff. Unlike most other operations you _MUST_
  1476 * be careful with this one. A peek leaves the buffer on the
  1477 * list and someone else may run off with it. You must hold
  1478 * the appropriate locks or have a private queue to do this.
  1479 *
  1480 * Returns %NULL for an empty list or a pointer to the head element.
  1481 * The reference count is not incremented and the reference is therefore
  1482 * volatile. Use with caution.
  1483 */
  1484 static inline struct sk_buff *skb_peek(const struct sk_buff_head *list_)
  1485 {
  1486 struct sk_buff *skb = list_->next;
  1487
  1488 if (skb == (struct sk_buff *)list_)
  1489 skb = NULL;
  1490 return skb;
  1491 }

  This generally results in a full panic crash of the Neutron node and
  connectivity breaking for VMs within the cloud. However, after using
  crash-dumptools to collect information on the crashes over the past
  three days, the kernel loaded by kexec during the crashdump appears in
  about 2 out of 3 crash instances to continue running, and we see a
  flap of the neutron services instead of a full panic that brings the
  Neutron server down and necessitates a hard reboot.

  I believe that this is a manifestation of the openvswitch and issue
  described on 2017-01-08 as:

  "OVS can only process L2 packets. But OVS GRE receive handler
  can accept IP-GRE packets. When such packet is processed by
  OVS datapath it can trigger following assert failure due
  to insufficient linear data in skb."

  https://patchwork.ozlabs.org/patch/712373/

  I have not tested the patch provided above yet.

  Other information and a few sample dmesg outputs from the crash:
  (multiple dumps available)

  # lsb_release -rd
  Description: Ubuntu 14.04.5 LTS
  Release: 14.04

  # apt-cache policy openvswitch
  N: Unable to locate package openvswitch
  root@neutron01:/var/crash# apt-cache policy openvswitch-common
  openvswitch-common:
Installed: 2.0.2-0ubuntu0.14.04.3
Candidate: 2.0.2-0ubuntu0.14.04.3
Version table:
   *** 2.0.2-0ubuntu0.14.04.3 0
  500 http://us.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   2.0.1+git20140120-0ubuntu2 0
  500 http://us.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages

  # apt-cache policy openvswitch-switch
  openvswitch-switch:
Installed: 2.0.2-0ubuntu0.14.04.3
Candidate: 2.0.2-0ubuntu0.14.04.3
Version table:
   *** 2.0.2-0ubuntu0.14.04.3 0
  500 http://us.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   2.0.1+git20140120-0ubuntu2 0
  500 http://us.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages

  # apt-cache policy neutron-plugin-openvswitch-agent
  neutron-plugin-openvswitch-agent:
Installed: 1:2014.1.5-0ubuntu7
Candidate: 1:2014.1.5-0ubuntu7
Version table:
   *** 1:2014.1.5-0ubuntu7 0
  500 http://us.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   1:2014.1.3-0ubuntu1.1 0
  500 http://security.ubuntu.com/ubuntu/ trusty-security/main amd64 
Packages
   1:2014.1-0ubuntu1 0
  500 http://us.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages

  example dmesg:

  ## dmesg.201701060019

  > [33100.131019] [ cut here ]
  > [33100.131176] kernel BUG at 
/build/linux-mi9H1O/linux-3.13.0/include/linux/skbuff.h:1486!
  > [33100.131424] invalid opcode:  [#1] SMP
  > [33100.131560] Modules linked in: xt_nat xt_conntrack ip6table_filter 
ip6_tables iptable_filter xt_REDIRECT xt_tcpudp iptable_nat nf_conntrack_ipv4 
nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack ip_tables x_tables veth 
openvswitch gre vxlan ip_tunnel libcrc32c ipmi_devintf gpio_ich cdc_ether 
x86_pkg_temp_thermal intel_powerclamp coretemp usbnet kvm_intel mii kvm 
crct10dif_pclmul crc32_pclmul ghash_clmulni_intel aesni_intel aes_x86_64 lrw 
gf128mul glue_helper ablk_helper cryptd sb_edac edac_core lpc_ich wmi ipmi_si 
bonding shpchp ioatdma lp mac_hid parport ahci libahci sfc igb e1000e mtd dca 
i2c_algo_bit ptp pps_core

[Kernel-packages] [Bug 1655683] Re: kernel BUG at skbuff.h:1486 Insufficient linear data in skb __skb_pull.part.7+0x4/0x6 [openvswitch]

** Attachment added: "dump.201701051502"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1655683/+attachment/4802913/+files/dump.201701051502

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

Title:
  kernel BUG at skbuff.h:1486 Insufficient linear data in skb
  __skb_pull.part.7+0x4/0x6 [openvswitch]

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Since 2016-12-30 EST we have been experiencing repeated crashes of our
  OpenStack Icehouse / Trusty Neutron node with a kernel BUG at skbuff.h
  line 1486:

  1471 /**
  1472 * skb_peek - peek at the head of an _buff_head
  1473 * @list_: list to peek at
  1474 *
  1475 * Peek an _buff. Unlike most other operations you _MUST_
  1476 * be careful with this one. A peek leaves the buffer on the
  1477 * list and someone else may run off with it. You must hold
  1478 * the appropriate locks or have a private queue to do this.
  1479 *
  1480 * Returns %NULL for an empty list or a pointer to the head element.
  1481 * The reference count is not incremented and the reference is therefore
  1482 * volatile. Use with caution.
  1483 */
  1484 static inline struct sk_buff *skb_peek(const struct sk_buff_head *list_)
  1485 {
  1486 struct sk_buff *skb = list_->next;
  1487
  1488 if (skb == (struct sk_buff *)list_)
  1489 skb = NULL;
  1490 return skb;
  1491 }

  This generally results in a full panic crash of the Neutron node and
  connectivity breaking for VMs within the cloud. However, after using
  crash-dumptools to collect information on the crashes over the past
  three days, the kernel loaded by kexec during the crashdump appears in
  about 2 out of 3 crash instances to continue running, and we see a
  flap of the neutron services instead of a full panic that brings the
  Neutron server down and necessitates a hard reboot.

  I believe that this is a manifestation of the openvswitch and issue
  described on 2017-01-08 as:

  "OVS can only process L2 packets. But OVS GRE receive handler
  can accept IP-GRE packets. When such packet is processed by
  OVS datapath it can trigger following assert failure due
  to insufficient linear data in skb."

  https://patchwork.ozlabs.org/patch/712373/

  I have not tested the patch provided above yet.

  Other information and a few sample dmesg outputs from the crash:
  (multiple dumps available)

  # lsb_release -rd
  Description: Ubuntu 14.04.5 LTS
  Release: 14.04

  # apt-cache policy openvswitch
  N: Unable to locate package openvswitch
  root@neutron01:/var/crash# apt-cache policy openvswitch-common
  openvswitch-common:
Installed: 2.0.2-0ubuntu0.14.04.3
Candidate: 2.0.2-0ubuntu0.14.04.3
Version table:
   *** 2.0.2-0ubuntu0.14.04.3 0
  500 http://us.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   2.0.1+git20140120-0ubuntu2 0
  500 http://us.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages

  # apt-cache policy openvswitch-switch
  openvswitch-switch:
Installed: 2.0.2-0ubuntu0.14.04.3
Candidate: 2.0.2-0ubuntu0.14.04.3
Version table:
   *** 2.0.2-0ubuntu0.14.04.3 0
  500 http://us.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   2.0.1+git20140120-0ubuntu2 0
  500 http://us.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages

  # apt-cache policy neutron-plugin-openvswitch-agent
  neutron-plugin-openvswitch-agent:
Installed: 1:2014.1.5-0ubuntu7
Candidate: 1:2014.1.5-0ubuntu7
Version table:
   *** 1:2014.1.5-0ubuntu7 0
  500 http://us.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   1:2014.1.3-0ubuntu1.1 0
  500 http://security.ubuntu.com/ubuntu/ trusty-security/main amd64 
Packages
   1:2014.1-0ubuntu1 0
  500 http://us.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages

  example dmesg:

  ## dmesg.201701060019

  > [33100.131019] [ cut here ]
  > [33100.131176] kernel BUG at 
/build/linux-mi9H1O/linux-3.13.0/include/linux/skbuff.h:1486!
  > [33100.131424] invalid opcode:  [#1] SMP
  > [33100.131560] Modules linked in: xt_nat xt_conntrack ip6table_filter 
ip6_tables iptable_filter xt_REDIRECT xt_tcpudp iptable_nat nf_conntrack_ipv4 
nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack ip_tables x_tables veth 
openvswitch gre vxlan ip_tunnel libcrc32c ipmi_devintf gpio_ich cdc_ether 
x86_pkg_temp_thermal intel_powerclamp coretemp usbnet kvm_intel mii kvm 
crct10dif_pclmul crc32_pclmul ghash_clmulni_intel aesni_intel aes_x86_64 lrw 
gf128mul glue_helper ablk_helper cryptd sb_edac edac_core lpc_ich wmi ipmi_si 
bonding shpchp ioatdma lp mac_hid parport ahci libahci sfc igb e1000e mtd dca 
i2c_algo_bit ptp pps_core megaraid_sas mdio
  > [33100.133560] CPU: 2 PID: 0 Comm:

[Kernel-packages] [Bug 1655683] Re: kernel BUG at skbuff.h:1486 Insufficient linear data in skb __skb_pull.part.7+0x4/0x6 [openvswitch]