[Kernel-packages] [Bug 1714420] [NEW] kernel oops - kvm guest started at boot time

[Daniel Black]

Public bug reported:

[0.00] Linux version 4.4.0-93-generic (buildd@bos01-ppc64el-025)
(gcc version 5.4.0 20160609 (Ubuntu/IBM 5.4.0-6ubuntu1~16.04.4) )
#116-Ubuntu SMP Fri Aug 11 16:30:16 UTC 2017 (Ubuntu
4.4.0-93.116-generic 4.4.79)

...
[  380.184554] KVM guest htab at c0799900 (order 29), LPID 2
[  380.527576] Facility 'TM' unavailable, exception at 0xd0003aad7f10, 
MSR=90009033
[  380.527717] Oops: Unexpected facility unavailable exception, sig: 6 [#2]
[  380.527775] SMP NR_CPUS=2048 NUMA PowerNV
[  380.527823] Modules linked in: vhost_net vhost macvtap macvlan xt_CHECKSUM 
iptable_mangle ipt_REJECT nf_reject_ipv4 xt_tcpudp ebtable_filter ebtables 
ip6table_filter ip6_tables ipt_MASQUERADE nf_nat_masquerade_ipv4 xfrm_user 
xfrm_algo iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 xt_addrtype 
iptable_filter ip_tables xt_conntrack x_tables nf_nat nf_conntrack br_netfilter 
overlay binfmt_misc bridge stp llc kvm_hv uio_pdrv_genirq uio leds_powernv 
ipmi_powernv ibmpowernv vmx_crypto powernv_rng ipmi_msghandler kvm_pr kvm 
autofs4 xfs btrfs raid456 async_raid6_recov async_memcpy async_pq async_xor 
async_tx xor raid6_pq libcrc32c raid0 multipath linear raid1 raid10 ses 
enclosure mlx4_en be2net lpfc vxlan mlx4_core scsi_transport_fc ip6_udp_tunnel 
udp_tunnel ipr
[  380.528781] CPU: 24 PID: 4277 Comm: qemu-system-ppc Tainted: G  D
 4.4.0-93-generic #116-Ubuntu
[  380.528861] task: c3c389b0 ti: c01fb2428000 task.ti: 
c01fb2428000
[  380.528929] NIP: d0003aad7f10 LR: d00037d52a14 CTR: d0003aad7e40
[  380.528997] REGS: c01fb242b7b0 TRAP: 0f60   Tainted: G  D  
(4.4.0-93-generic)
[  380.529076] MSR: 90009033   CR: 22024848  
XER: 
[  380.529247] CFAR: d0003aad7ea4 SOFTE: 1
   GPR00: d00037d52a14 c01fb242ba30 d0003aaec018 
c01fdbf6
   GPR04: c01f8580 c01fb242bbc0  

   GPR08: 0001 c3c389b0 0001 
d00037d578f8
   GPR12: d0003aad7e40 cfb4e400  
001f
   GPR16: 3fff7206 0080 3fff892c4390 
3fff7285f200
   GPR20: 010009988430 0100099affd0 3fff7285eb60 
100c1ff0
   GPR24: 3bcf4e10 3fff72040028  
c01fdbf6
   GPR28:  c01f8580 c01fdbf6 
c01f8580
[  380.530119] NIP [d0003aad7f10] kvmppc_vcpu_run_hv+0xd0/0xff0 [kvm_hv]
[  380.530188] LR [d00037d52a14] kvmppc_vcpu_run+0x44/0x60 [kvm]
[  380.530245] Call Trace:
[  380.530270] [c01fb242ba30] [c01fb242bab0] 0xc01fb242bab0 
(unreliable)
[  380.530353] [c01fb242bb70] [d00037d52a14] kvmppc_vcpu_run+0x44/0x60 
[kvm]
[  380.530436] [c01fb242bba0] [d00037d4f674] 
kvm_arch_vcpu_ioctl_run+0x64/0x170 [kvm]
[  380.530519] [c01fb242bbe0] [d00037d43918] kvm_vcpu_ioctl+0x528/0x7b0 
[kvm]
[  380.530602] [c01fb242bd40] [c02fff60] do_vfs_ioctl+0x480/0x7d0
[  380.530671] [c01fb242bde0] [c0300384] SyS_ioctl+0xd4/0xf0
[  380.530742] [c01fb242be30] [c0009204] system_call+0x38/0xb4
[  380.530837] Instruction dump:
[  380.530904] e92d02a0 e9290a50 e9290108 792a07e3 41820058 e92d02a0 e9290a50 
e9290108
[  380.531126] 7927e8a4 78e71f87 40820ed8 e92d02a0 <7d4022a6> f9490ee8 e92d02a0 
7d4122a6
[  380.531350] ---[ end trace 8f9b3b82f9a07d76 ]---


Needs kernel patch e47057151422a67ce08747176fa21cb3b526a2c9 according to Cyril

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: linux-image-4.4.0-93-generic 4.4.0-93.116
ProcVersionSignature: Ubuntu 4.4.0-93.116-generic 4.4.79
Uname: Linux 4.4.0-93-generic ppc64le
AlsaDevices:
 total 0
 crw-rw 1 root audio 116,  1 Sep  1 15:03 seq
 crw-rw 1 root audio 116, 33 Sep  1 15:03 timer
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
ApportVersion: 2.20.1-0ubuntu2.10
Architecture: ppc64el
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: Fri Sep  1 15:34:14 2017
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
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.
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
PciMultimedia:
 
ProcFB:
 
ProcKernelCmdLine: root=UUID=c3fd6cdf-331d-4c9a-9a51-efabe9deea59 ro splash 
quiet
ProcLoadAvg: 

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

[bugproxy]

--- Comment From furma...@us.ibm.com 2017-09-01 00:40 EDT---
I tested the test kernel made available by jsalisbury and it worked for me as 
well.

This is a pretty big blocker - very much hoping this makes it into a new
kernel soon.

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

Title:
  KVM on 16.04.3 throws an error

Status in The Ubuntu-power-systems project:
  In Progress
Status in linux package in Ubuntu:
  In Progress
Status in qemu package in Ubuntu:
  Won't Fix
Status in linux source package in Xenial:
  In Progress
Status in linux source package in Zesty:
  Invalid

Bug description:
  Problem Description
  
  KVM on Ubuntu 16.04.3 throws an error when used
   
  ---uname output---
  Linux bastion-1 4.4.0-89-generic #112-Ubuntu SMP Mon Jul 31 19:37:08 UTC 2017 
ppc64le ppc64le ppc64le GNU/Linux
   
  Machine Type =  8348-21C Habanero 
   
  ---Steps to Reproduce---
   Install 16.04.3

  install KVM like:

  apt-get install libvirt-bin qemu qemu-slof qemu-system qemu-utils

  then exit and log back in so virsh will work without sudo

  then run my spawn script

  $ cat spawn.sh
  #!/bin/bash

  img=$1
  qemu-system-ppc64 \
  -machine pseries,accel=kvm,usb=off -cpu host -m 512 \
  -display none -nographic \
  -net nic -net user \
  -drive "file=$img"

  with a freshly downloaded ubuntu cloud image

  sudo ./spawn.sh xenial-server-cloudimg-ppc64el-disk1.img

  And I get nothing on the output.

  and errors in dmesg

  
  ubuntu@bastion-1:~$ [  340.180295] Facility 'TM' unavailable, exception at 
0xd000148b7f10, MSR=90009033
  [  340.180399] Oops: Unexpected facility unavailable exception, sig: 6 [#1]
  [  340.180513] SMP NR_CPUS=2048 NUMA PowerNV
  [  340.180547] Modules linked in: xt_CHECKSUM iptable_mangle ipt_MASQUERADE 
nf_nat_masquerade_ipv4 iptable_nat nf_nat_ipv4 nf_nat nf_conntrack_ipv4 
nf_defrag_ipv4 xt_conntrack nf_conntrack ipt_REJECT nf_reject_ipv4 xt_tcpudp 
bridge stp llc ebtable_filter ebtables ip6table_filter ip6_tables 
iptable_filter ip_tables x_tables kvm_hv kvm binfmt_misc joydev input_leds 
mac_hid opal_prd ofpart cmdlinepart powernv_flash ipmi_powernv ipmi_msghandler 
mtd at24 uio_pdrv_genirq uio ibmpowernv powernv_rng vmx_crypto ib_iser rdma_cm 
iw_cm ib_cm ib_sa ib_mad ib_core ib_addr iscsi_tcp libiscsi_tcp libiscsi 
scsi_transport_iscsi autofs4 btrfs raid10 raid456 async_raid6_recov 
async_memcpy async_pq async_xor async_tx xor raid6_pq raid1 raid0 multipath 
linear mlx4_en hid_generic usbhid hid uas usb_storage ast i2c_algo_bit bnx2x 
ttm drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops mlx4_core drm 
ahci vxlan libahci ip6_udp_tunnel udp_tunnel mdio libcrc32c
  [  340.181331] CPU: 46 PID: 5252 Comm: qemu-system-ppc Not tainted 
4.4.0-89-generic #112-Ubuntu
  [  340.181382] task: c01e34c30b50 ti: c01e34ce4000 task.ti: 
c01e34ce4000
  [  340.181432] NIP: d000148b7f10 LR: d00014822a14 CTR: 
d000148b7e40
  [  340.181475] REGS: c01e34ce77b0 TRAP: 0f60   Not tainted  
(4.4.0-89-generic)
  [  340.181519] MSR: 90009033   CR: 22024848  
XER: 
  [  340.181629] CFAR: d000148b7ea4 SOFTE: 1 
  GPR00: d00014822a14 c01e34ce7a30 d000148cc018 c01e37bc 
  GPR04: c01db9ac c01e34ce7bc0   
  GPR08: 0001 c01e34c30b50 0001 d000148278f8 
  GPR12: d000148b7e40 cfb5b500  001f 
  GPR16: 3fff91c3 0080 3fffa8e34390 3fff9242f200 
  GPR20: 3fff92430010 01001de5c030 3fff9242eb60 100c1ff0 
  GPR24: 3fffc91fe990 3fff91c10028  c01e37bc 
  GPR28:  c01db9ac c01e37bc c01db9ac 
  [  340.182315] NIP [d000148b7f10] kvmppc_vcpu_run_hv+0xd0/0xff0 [kvm_hv]
  [  340.182357] LR [d00014822a14] kvmppc_vcpu_run+0x44/0x60 [kvm]
  [  340.182394] Call Trace:
  [  340.182413] [c01e34ce7a30] [c01e34ce7ab0] 0xc01e34ce7ab0 
(unreliable)
  [  340.182468] [c01e34ce7b70] [d00014822a14] 
kvmppc_vcpu_run+0x44/0x60 [kvm]
  [  340.182522] [c01e34ce7ba0] [d0001481f674] 
kvm_arch_vcpu_ioctl_run+0x64/0x170 [kvm]
  [  340.182581] [c01e34ce7be0] [d00014813918] 
kvm_vcpu_ioctl+0x528/0x7b0 [kvm]
  [  340.182634] [c01e34ce7d40] [c02fffa0] do_vfs_ioctl+0x480/0x7d0
  [  340.182678] [c01e34ce7de0] [c03003c4] SyS_ioctl+0xd4/0xf0
  [  340.182723] [c01e34ce7e30] [c0009204] system_call+0x38/0xb4
  [  340.182766] Instruction dump:
  [  340.182788] e92d02a0 e9290a50 e9290108 792a07e3 41820058 e92d02a0 e9290a50 
e9290108 
  [  340.182863] 7927e8a4 78e71f87 40820ed8 e92d02a0 <7d4022a6> f9490ee8 
e92d02a0 7d4122a6 
  [  340.182938] ---[ end trace bc5080cb7d18f102 ]---
  [  340.276202] 

[Kernel-packages] [Bug 1701486] Re: System brightness slider doesn't work any more

[Kai-Heng Feng]

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

Title:
  System brightness slider doesn't work any more

Status in linux package in Ubuntu:
  Invalid

Bug description:
  Update from 4.10.0-24 to 26 broke it. Using Linux Mint 18.1 x64
  Cinnamon.

  Changing /sys/class/backlight/intel_backlight/brightness manually
  works though.

  $ cat /proc/version_signature
  Ubuntu 4.10.0-26.30~16.04.1-generic 4.10.17

  $ sudo lspci -vnvn 
  00:00.0 Host bridge [0600]: Intel Corporation Sky Lake Host Bridge/DRAM 
Registers [8086:1910] (rev 07)
Subsystem: Dell Skylake Host Bridge/DRAM Registers [1028:0706]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel driver in use: skl_uncore

  00:01.0 PCI bridge [0604]: Intel Corporation Sky Lake PCIe Controller (x16) 
[8086:1901] (rev 07) (prog-if 00 [Normal decode])
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- Reset- FastB2B-
PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
Capabilities: [88] Subsystem: Intel Corporation Skylake PCIe Controller 
(x16) [8086:2015]
Capabilities: [80] Power Management version 3
Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA 
PME(D0+,D1-,D2-,D3hot+,D3cold+)
Status: D3 NoSoftRst+ PME-Enable+ DSel=0 DScale=0 PME-
Capabilities: [90] MSI: Enable+ Count=1/1 Maskable- 64bit-
Address: fee00218  Data: 
Capabilities: [a0] 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 256 bytes, MaxReadReq 128 bytes
DevSta: CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr- 
TransPend-
LnkCap: Port #2, Speed 8GT/s, Width x16, ASPM L0s L1, Exit 
Latency L0s <1us, L1 <8us
ClockPM- Surprise- LLActRep- BwNot+ ASPMOptComp+
LnkCtl: ASPM Disabled; 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 #1, PowerLimit 75.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: Not Supported, TimeoutDis-, LTR+, 
OBFF Via WAKE# ARIFwd-
DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis-, LTR+, 
OBFF Via WAKE# 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: -6dB, 
EqualizationComplete-, EqualizationPhase1-
 EqualizationPhase2-, EqualizationPhase3-, 
LinkEqualizationRequest-
Capabilities: [100 v1] Virtual Channel
Caps:   LPEVC=0 RefClk=100ns PATEntryBits=1
Arb:Fixed- WRR32- WRR64- WRR128-
Ctrl:   ArbSelect=Fixed
Status: InProgress-
VC0:Caps:   PATOffset=00 MaxTimeSlots=1 RejSnoopTrans-
Arb:Fixed+ WRR32- WRR64- WRR128- TWRR128- WRR256-
Ctrl:   Enable+ ID=0 ArbSelect=Fixed TC/VC=ff
Status: NegoPending+ InProgress-
Capabilities: [140 v1] Root Complex Link
Desc:   PortNumber=02 ComponentID=01 EltType=Config
Link0:  Desc:   TargetPort=00 TargetComponent=01 AssocRCRB- 
LinkType=MemMapped LinkValid+
Addr:   fed19000
Capabilities: [d94 v1] #19
Kernel driver in use: pcieport
Kernel modules: shpchp

  00:01.1 PCI bridge [0604]: Intel Corporation Sky 

[Kernel-packages] [Bug 1701486] Re: System brightness slider doesn't work any more

[Mygod]

Feel free to do so. Currently I don't have enough time to investigate
which specific parameter(s) caused the issue. Thanks for your help!

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

Title:
  System brightness slider doesn't work any more

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Update from 4.10.0-24 to 26 broke it. Using Linux Mint 18.1 x64
  Cinnamon.

  Changing /sys/class/backlight/intel_backlight/brightness manually
  works though.

  $ cat /proc/version_signature
  Ubuntu 4.10.0-26.30~16.04.1-generic 4.10.17

  $ sudo lspci -vnvn 
  00:00.0 Host bridge [0600]: Intel Corporation Sky Lake Host Bridge/DRAM 
Registers [8086:1910] (rev 07)
Subsystem: Dell Skylake Host Bridge/DRAM Registers [1028:0706]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel driver in use: skl_uncore

  00:01.0 PCI bridge [0604]: Intel Corporation Sky Lake PCIe Controller (x16) 
[8086:1901] (rev 07) (prog-if 00 [Normal decode])
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- Reset- FastB2B-
PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
Capabilities: [88] Subsystem: Intel Corporation Skylake PCIe Controller 
(x16) [8086:2015]
Capabilities: [80] Power Management version 3
Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA 
PME(D0+,D1-,D2-,D3hot+,D3cold+)
Status: D3 NoSoftRst+ PME-Enable+ DSel=0 DScale=0 PME-
Capabilities: [90] MSI: Enable+ Count=1/1 Maskable- 64bit-
Address: fee00218  Data: 
Capabilities: [a0] 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 256 bytes, MaxReadReq 128 bytes
DevSta: CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr- 
TransPend-
LnkCap: Port #2, Speed 8GT/s, Width x16, ASPM L0s L1, Exit 
Latency L0s <1us, L1 <8us
ClockPM- Surprise- LLActRep- BwNot+ ASPMOptComp+
LnkCtl: ASPM Disabled; 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 #1, PowerLimit 75.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: Not Supported, TimeoutDis-, LTR+, 
OBFF Via WAKE# ARIFwd-
DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis-, LTR+, 
OBFF Via WAKE# 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: -6dB, 
EqualizationComplete-, EqualizationPhase1-
 EqualizationPhase2-, EqualizationPhase3-, 
LinkEqualizationRequest-
Capabilities: [100 v1] Virtual Channel
Caps:   LPEVC=0 RefClk=100ns PATEntryBits=1
Arb:Fixed- WRR32- WRR64- WRR128-
Ctrl:   ArbSelect=Fixed
Status: InProgress-
VC0:Caps:   PATOffset=00 MaxTimeSlots=1 RejSnoopTrans-
Arb:Fixed+ WRR32- WRR64- WRR128- TWRR128- WRR256-
Ctrl:   Enable+ ID=0 ArbSelect=Fixed TC/VC=ff
Status: NegoPending+ InProgress-
Capabilities: [140 v1] Root Complex Link
Desc:   PortNumber=02 ComponentID=01 EltType=Config
Link0:  Desc:   TargetPort=00 TargetComponent=01 AssocRCRB- 
LinkType=MemMapped LinkValid+
Addr:   fed19000
Capabilities: [d94 v1] #19
Kernel driver in use: pcieport

[Kernel-packages] [Bug 1701486] Re: System brightness slider doesn't work any more

[Kai-Heng Feng]

So I guess we can close the issue?

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

Title:
  System brightness slider doesn't work any more

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Update from 4.10.0-24 to 26 broke it. Using Linux Mint 18.1 x64
  Cinnamon.

  Changing /sys/class/backlight/intel_backlight/brightness manually
  works though.

  $ cat /proc/version_signature
  Ubuntu 4.10.0-26.30~16.04.1-generic 4.10.17

  $ sudo lspci -vnvn 
  00:00.0 Host bridge [0600]: Intel Corporation Sky Lake Host Bridge/DRAM 
Registers [8086:1910] (rev 07)
Subsystem: Dell Skylake Host Bridge/DRAM Registers [1028:0706]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel driver in use: skl_uncore

  00:01.0 PCI bridge [0604]: Intel Corporation Sky Lake PCIe Controller (x16) 
[8086:1901] (rev 07) (prog-if 00 [Normal decode])
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- Reset- FastB2B-
PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
Capabilities: [88] Subsystem: Intel Corporation Skylake PCIe Controller 
(x16) [8086:2015]
Capabilities: [80] Power Management version 3
Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA 
PME(D0+,D1-,D2-,D3hot+,D3cold+)
Status: D3 NoSoftRst+ PME-Enable+ DSel=0 DScale=0 PME-
Capabilities: [90] MSI: Enable+ Count=1/1 Maskable- 64bit-
Address: fee00218  Data: 
Capabilities: [a0] 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 256 bytes, MaxReadReq 128 bytes
DevSta: CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr- 
TransPend-
LnkCap: Port #2, Speed 8GT/s, Width x16, ASPM L0s L1, Exit 
Latency L0s <1us, L1 <8us
ClockPM- Surprise- LLActRep- BwNot+ ASPMOptComp+
LnkCtl: ASPM Disabled; 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 #1, PowerLimit 75.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: Not Supported, TimeoutDis-, LTR+, 
OBFF Via WAKE# ARIFwd-
DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis-, LTR+, 
OBFF Via WAKE# 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: -6dB, 
EqualizationComplete-, EqualizationPhase1-
 EqualizationPhase2-, EqualizationPhase3-, 
LinkEqualizationRequest-
Capabilities: [100 v1] Virtual Channel
Caps:   LPEVC=0 RefClk=100ns PATEntryBits=1
Arb:Fixed- WRR32- WRR64- WRR128-
Ctrl:   ArbSelect=Fixed
Status: InProgress-
VC0:Caps:   PATOffset=00 MaxTimeSlots=1 RejSnoopTrans-
Arb:Fixed+ WRR32- WRR64- WRR128- TWRR128- WRR256-
Ctrl:   Enable+ ID=0 ArbSelect=Fixed TC/VC=ff
Status: NegoPending+ InProgress-
Capabilities: [140 v1] Root Complex Link
Desc:   PortNumber=02 ComponentID=01 EltType=Config
Link0:  Desc:   TargetPort=00 TargetComponent=01 AssocRCRB- 
LinkType=MemMapped LinkValid+
Addr:   fed19000
Capabilities: [d94 v1] #19
Kernel driver in use: pcieport
Kernel modules: shpchp

  00:01.1 PCI bridge [0604]: Intel Corporation Sky Lake PCIe Controller (x8) 

[Kernel-packages] [Bug 1701486] Re: System brightness slider doesn't work any more

[Mygod]

That does seem to make the problem go away.

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

Title:
  System brightness slider doesn't work any more

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Update from 4.10.0-24 to 26 broke it. Using Linux Mint 18.1 x64
  Cinnamon.

  Changing /sys/class/backlight/intel_backlight/brightness manually
  works though.

  $ cat /proc/version_signature
  Ubuntu 4.10.0-26.30~16.04.1-generic 4.10.17

  $ sudo lspci -vnvn 
  00:00.0 Host bridge [0600]: Intel Corporation Sky Lake Host Bridge/DRAM 
Registers [8086:1910] (rev 07)
Subsystem: Dell Skylake Host Bridge/DRAM Registers [1028:0706]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel driver in use: skl_uncore

  00:01.0 PCI bridge [0604]: Intel Corporation Sky Lake PCIe Controller (x16) 
[8086:1901] (rev 07) (prog-if 00 [Normal decode])
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- Reset- FastB2B-
PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
Capabilities: [88] Subsystem: Intel Corporation Skylake PCIe Controller 
(x16) [8086:2015]
Capabilities: [80] Power Management version 3
Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA 
PME(D0+,D1-,D2-,D3hot+,D3cold+)
Status: D3 NoSoftRst+ PME-Enable+ DSel=0 DScale=0 PME-
Capabilities: [90] MSI: Enable+ Count=1/1 Maskable- 64bit-
Address: fee00218  Data: 
Capabilities: [a0] 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 256 bytes, MaxReadReq 128 bytes
DevSta: CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr- 
TransPend-
LnkCap: Port #2, Speed 8GT/s, Width x16, ASPM L0s L1, Exit 
Latency L0s <1us, L1 <8us
ClockPM- Surprise- LLActRep- BwNot+ ASPMOptComp+
LnkCtl: ASPM Disabled; 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 #1, PowerLimit 75.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: Not Supported, TimeoutDis-, LTR+, 
OBFF Via WAKE# ARIFwd-
DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis-, LTR+, 
OBFF Via WAKE# 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: -6dB, 
EqualizationComplete-, EqualizationPhase1-
 EqualizationPhase2-, EqualizationPhase3-, 
LinkEqualizationRequest-
Capabilities: [100 v1] Virtual Channel
Caps:   LPEVC=0 RefClk=100ns PATEntryBits=1
Arb:Fixed- WRR32- WRR64- WRR128-
Ctrl:   ArbSelect=Fixed
Status: InProgress-
VC0:Caps:   PATOffset=00 MaxTimeSlots=1 RejSnoopTrans-
Arb:Fixed+ WRR32- WRR64- WRR128- TWRR128- WRR256-
Ctrl:   Enable+ ID=0 ArbSelect=Fixed TC/VC=ff
Status: NegoPending+ InProgress-
Capabilities: [140 v1] Root Complex Link
Desc:   PortNumber=02 ComponentID=01 EltType=Config
Link0:  Desc:   TargetPort=00 TargetComponent=01 AssocRCRB- 
LinkType=MemMapped LinkValid+
Addr:   fed19000
Capabilities: [d94 v1] #19
Kernel driver in use: pcieport
Kernel modules: shpchp

  00:01.1 PCI bridge [0604]: Intel Corporation Sky Lake PCIe Controller 

[Kernel-packages] [Bug 1711936] Missing required logs.

[Ubuntu Kernel Bot]

This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:

apport-collect 1711936

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

Title:
  Severe graphical corruption in gnome-shell with nouveau [Nvidia
  GeForce 8400M GS]

Status in gnome-shell package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  When running gnome-shell on Ubuntu 17.10, text is visible only as white 
blocks (or sometimes not visible at all), and some graphics, such as the icons 
on the launcher menu, are corrupt. Only objects drawn by the gnome-shell and 
related programs seem to be affected. Software which is not part of the 
gnome-shell, such as LibreOffice, calculator, terminal, etc displays without 
corruption.
  --- 
  ApportVersion: 2.20.6-0ubuntu6
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 17.10
  GsettingsChanges: org.gnome.desktop.interface gtk-im-module 
'gtk-im-context-simple'
  InstallationDate: Installed on 2017-08-20 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170818)
  Package: linux
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5
  Tags:  artful wayland-session
  Uname: Linux 4.12.0-11-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1711936/+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 1711936] Re: Severe graphical corruption in gnome-shell with nouveau [Nvidia GeForce 8400M GS]

[Daniel van Vugt]

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

** No longer affects: gnome-shell (Ubuntu)

** Tags added: nouveau

** Also affects: gnome-shell (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/1711936

Title:
  Severe graphical corruption in gnome-shell with nouveau [Nvidia
  GeForce 8400M GS]

Status in gnome-shell package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  When running gnome-shell on Ubuntu 17.10, text is visible only as white 
blocks (or sometimes not visible at all), and some graphics, such as the icons 
on the launcher menu, are corrupt. Only objects drawn by the gnome-shell and 
related programs seem to be affected. Software which is not part of the 
gnome-shell, such as LibreOffice, calculator, terminal, etc displays without 
corruption.
  --- 
  ApportVersion: 2.20.6-0ubuntu6
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 17.10
  GsettingsChanges: org.gnome.desktop.interface gtk-im-module 
'gtk-im-context-simple'
  InstallationDate: Installed on 2017-08-20 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170818)
  Package: linux
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5
  Tags:  artful wayland-session
  Uname: Linux 4.12.0-11-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1711936/+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 1711936] Re: Severe graphical corruption in gnome-shell with nouveau [Nvidia GeForce 8400M GS]

[Alex Jones]

Proprietary driver (as well as simply disabling Wayland and using X with
Nouveau) fixes this issue. Perhaps for now Wayland should be blacklisted
for this card (and other cards that have this same issue).

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

Title:
  Severe graphical corruption in gnome-shell with nouveau [Nvidia
  GeForce 8400M GS]

Status in gnome-shell package in Ubuntu:
  Incomplete
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  When running gnome-shell on Ubuntu 17.10, text is visible only as white 
blocks (or sometimes not visible at all), and some graphics, such as the icons 
on the launcher menu, are corrupt. Only objects drawn by the gnome-shell and 
related programs seem to be affected. Software which is not part of the 
gnome-shell, such as LibreOffice, calculator, terminal, etc displays without 
corruption.
  --- 
  ApportVersion: 2.20.6-0ubuntu6
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 17.10
  GsettingsChanges: org.gnome.desktop.interface gtk-im-module 
'gtk-im-context-simple'
  InstallationDate: Installed on 2017-08-20 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170818)
  Package: linux
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5
  Tags:  artful wayland-session
  Uname: Linux 4.12.0-11-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1711936/+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 1690136] Re: Azure: make it possible to boot without initrd

[Leann Ogasawara]

** Package changed: linux (Ubuntu) => linux-azure (Ubuntu)

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

Title:
  Azure: make it possible to boot without initrd

Status in linux-azure package in Ubuntu:
  Confirmed

Bug description:
  SRU Justification:

  Impact: currently it's not possible to boot Azure instances without an
  initrd. The flexibility of booting an instance without an initrd is
  important to reduce boot time.

  Fix: Make the modules hv_vmbus and hv_storvsc built-in in the Azure
  kernel.

  Testcase:
  - Edit the grub.cfg file and remove the initrd entry.
  - Change the root= parameter to use the partition path instead of the partion 
UUID (the initramfs is usually responsible for fetching those information about 
disks and partitions).
  - If necessary, add rootfstype=ext4 to the kernel parameters.
  - After rebooting the system should be available.

  NOTE: This report is to track changes made to the azure custom kernel
  which cannot be correctly represented in launchpad.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1690136/+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 1628173] Re: ISST-LTE:pVM:roselp2:ubuntu 16.10: crash failed to check vmcore of 4.8 kernel

[bugproxy]

--- Comment From ru...@us.ibm.com 2017-08-31 17:54 EDT---
Closing this bug against 16.10 as it is EOL and linux-crashdump has been 
updated for zesty.

** Tags removed: targetmilestone-inin1610
** Tags added: targetmilestone-inin1704

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

Title:
  ISST-LTE:pVM:roselp2:ubuntu 16.10: crash failed to check vmcore of 4.8
  kernel

Status in crash package in Ubuntu:
  In Progress

Bug description:
  == Comment: #0 - Ping Tian Han  - 2016-09-22 03:05:36 ==
  ---Problem Description---
  crash cannot check vmcore of 4.8 kernel. 

  Then when trying to check the core with crash:

  % sudo crash /usr/lib/debug/boot/vmlinux-4.8.0-14-generic
  /var/crash/201609212349/vmcore.201609212349

  crash 7.1.5
  Copyright (C) 2002-2016  Red Hat, Inc.
  Copyright (C) 2004, 2005, 2006, 2010  IBM Corporation
  Copyright (C) 1999-2006  Hewlett-Packard Co
  Copyright (C) 2005, 2006, 2011, 2012  Fujitsu Limited
  Copyright (C) 2006, 2007  VA Linux Systems Japan K.K.
  Copyright (C) 2005, 2011  NEC Corporation
  Copyright (C) 1999, 2002, 2007  Silicon Graphics, Inc.
  Copyright (C) 1999, 2000, 2001, 2002  Mission Critical Linux, Inc.
  This program is free software, covered by the GNU General Public License,
  and you are welcome to change it and/or distribute copies of it under
  certain conditions.  Enter "help copying" to see the conditions.
  This program has absolutely no warranty.  Enter "help warranty" for details.

  GNU gdb (GDB) 7.6
  Copyright (C) 2013 Free Software Foundation, Inc.
  License GPLv3+: GNU GPL version 3 or later 
  This is free software: you are free to change and redistribute it.
  There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
  and "show warranty" for details.
  This GDB was configured as "powerpc64le-unknown-linux-gnu"...

  please wait... (gathering kmem slab cache data)
  crash: invalid kernel virtual address: 7aa9fe0100  type: "pmd page"

   
  ---uname output---
  Linux roselp2 4.8.0-14-generic #15-Ubuntu SMP Tue Sep 20 21:59:33 UTC 2016 
ppc64le ppc64le ppc64le GNU/Linux
   
  Machine Type = IBM,8286-42A, lpar 
   
  ---Steps to Reproduce---
   1. install 4.8 kernel
  2. trigger kdump to get vmcore
  3. check the vmcore with crash

  
  == Comment: #8 - Hari Krishna Bathini  - 2016-09-24 14:12:23 ==
  The below commit is needed for vtop address translation to succeed

commit 182914debbb9a2671ef644027fedd339aa9c80e0
Author: Dave Anderson 
Date:   Fri Sep 23 09:09:15 2016 -0400

  With the introduction of radix MMU in Power ISA 3.0, there are
  changes in kernel page table management accommodating it.  This patch
  series makes appropriate changes here to work for such kernels.
  Also, this series fixes a few bugs along the way:
  
ppc64: fix vtop page translation for 4K pages
ppc64: Use kernel terminology for each level in 4-level page table
ppc64/book3s: address changes in kernel v4.5
ppc64/book3s: address change in page flags for PowerISA v3.0
ppc64: use physical addresses and unfold pud for 64K page size
ppc64/book3s: support big endian Linux page tables
  
  The patches are needed for Linux v4.5 and later kernels on all
  ppc64 hardware.
  (hbath...@linux.vnet.ibm.com)
  --

  Also, the below commit is needed

commit 8ceb1ac628bf6a0a7f0bbfff030ec93081bca4cd
Author: Dave Anderson 
Date:   Mon May 23 11:23:01 2016 -0400

  Fix for Linux commit 0139aa7b7fa12ceef095d99dc36606a5b10ab83a, which
  renamed the page._count member to page._refcount.  Without the patch,
  certain "kmem" commands fail with the "kmem: invalid structure member
  offset: page_count".
  (ander...@redhat.com)

  Thanks
  Hari

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/crash/+bug/1628173/+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 1714367] Re: bcmwl-kernel-source no longer works on hwe kernel

[Scott Testerman]

Laptop info:

description: Notebook
product: 0769AK8 (Lenovo)
vendor: LENOVO
version: 3000 N200
serial: redacted
width: 64 bits
capabilities: smbios-2.4 dmi-2.4 vsyscall32
configuration: boot=oem-specific chassis=notebook family=Lenovo sku=Lenovo 
uuid=redacted
  *-core
   description: Motherboard
   product: IEL10
   vendor: LENOVO
   physical id: 0
   version: REFERENCE
   serial: redacted
 *-firmware
  description: BIOS
  vendor: LENOVO
  physical id: 0
  version: 68ET37WW
  date: 07/29/2008
  size: 106KiB
  capacity: 960KiB
  capabilities: pci pnp apm upgrade shadowing escd cdboot bootselect 
edd int13floppy360 int13floppy1200 int13floppy720 int13floppy2880 
int5printscreen int9keyboard int14serial int17printer int10video acpi usb 
ls120boot biosbootspecification

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

Title:
  bcmwl-kernel-source no longer works on hwe kernel

Status in bcmwl package in Ubuntu:
  New

Bug description:
  bcmwl-kernel-source worked correctly on the original 16.04 LTS kernel,
  but no longer works on the hwe kernel (4.10.0-33).  I am using the b43
  open source driver temporarily in order to file this report.

  Description:  Ubuntu 16.04.3 LTS
  Release:  16.04

  bcmwl-kernel-source:
Installed: 6.30.223.271+bdcom-0ubuntu1~1.1
Candidate: 6.30.223.271+bdcom-0ubuntu1~1.1
Version table:
   *** 6.30.223.271+bdcom-0ubuntu1~1.1 500
  500 http://us.archive.ubuntu.com/ubuntu xenial-updates/restricted 
amd64 Packages
  100 /var/lib/dpkg/status
   6.30.223.248+bdcom-0ubuntu8 500
  500 http://us.archive.ubuntu.com/ubuntu xenial/restricted amd64 
Packages

  04:00.0 Network controller: Broadcom Corporation BCM4311 802.11b/g WLAN (rev 
01)
Subsystem: Broadcom Corporation BCM4311 802.11b/g WLAN
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR+ FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1714367/+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 1714367] [NEW] bcmwl-kernel-source no longer works on hwe kernel

[Scott Testerman]

Public bug reported:

bcmwl-kernel-source worked correctly on the original 16.04 LTS kernel,
but no longer works on the hwe kernel (4.10.0-33).  I am using the b43
open source driver temporarily in order to file this report.

Description:Ubuntu 16.04.3 LTS
Release:16.04

bcmwl-kernel-source:
  Installed: 6.30.223.271+bdcom-0ubuntu1~1.1
  Candidate: 6.30.223.271+bdcom-0ubuntu1~1.1
  Version table:
 *** 6.30.223.271+bdcom-0ubuntu1~1.1 500
500 http://us.archive.ubuntu.com/ubuntu xenial-updates/restricted amd64 
Packages
100 /var/lib/dpkg/status
 6.30.223.248+bdcom-0ubuntu8 500
500 http://us.archive.ubuntu.com/ubuntu xenial/restricted amd64 Packages

04:00.0 Network controller: Broadcom Corporation BCM4311 802.11b/g WLAN (rev 01)
Subsystem: Broadcom Corporation BCM4311 802.11b/g WLAN
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR+ FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- https://bugs.launchpad.net/bugs/1714367

Title:
  bcmwl-kernel-source no longer works on hwe kernel

Status in bcmwl package in Ubuntu:
  New

Bug description:
  bcmwl-kernel-source worked correctly on the original 16.04 LTS kernel,
  but no longer works on the hwe kernel (4.10.0-33).  I am using the b43
  open source driver temporarily in order to file this report.

  Description:  Ubuntu 16.04.3 LTS
  Release:  16.04

  bcmwl-kernel-source:
Installed: 6.30.223.271+bdcom-0ubuntu1~1.1
Candidate: 6.30.223.271+bdcom-0ubuntu1~1.1
Version table:
   *** 6.30.223.271+bdcom-0ubuntu1~1.1 500
  500 http://us.archive.ubuntu.com/ubuntu xenial-updates/restricted 
amd64 Packages
  100 /var/lib/dpkg/status
   6.30.223.248+bdcom-0ubuntu8 500
  500 http://us.archive.ubuntu.com/ubuntu xenial/restricted amd64 
Packages

  04:00.0 Network controller: Broadcom Corporation BCM4311 802.11b/g WLAN (rev 
01)
Subsystem: Broadcom Corporation BCM4311 802.11b/g WLAN
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR+ FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1714367/+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 1630304] Re: Ubuntu 16.10 KVM: Issue doing hotplug detach to SRIOV VF

[bugproxy]

** Tags removed: targetmilestone-inin1610
** Tags added: targetmilestone-inin1710

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

Title:
  Ubuntu 16.10 KVM: Issue doing hotplug detach to SRIOV VF

Status in linux package in Ubuntu:
  Opinion

Bug description:
  ---Problem Description---
  I can not get hotplug attach to work in Ubuntu but if I try to detach a CX4 
VF from a guest I am getting some issues:
  Like in this case:
  [  474.393308] vfio-pci 0001:01:00.3: No device request channel registered, 
blocked until released by user
  [  474.393543] pci 0001:01: 0.3: [PE# 006] Removing DMA window #0
  [  474.393553] pci 0001:01: 0.3: [PE# 006] Removing DMA window #1
  [  474.393906] mlx5_core 0001:01:00.3: enabling device ( -> 0002)
  [  474.393939] mlx5_core 0001:01:00.3: Using 32-bit DMA via iommu
  [  474.400360] pci 0001:01: 0.3: [PE# 006] Setting up window#0 0..7fff 
pg=1000
  [  474.400380] mlx5_core 0001:01:00.3: firmware version: 12.17.226
  [  474.401341] pci 0001:01: 0.3: [PE# 006] Enabling 64-bit DMA bypass
  [  474.402284] EEH: Frozen PE#6 on PHB#1 detected
  [  474.402475] EEH: PE location: Slot4, PHB location: N/A
  [  474.403699] EEH: This PCI device has failed 1 times in the last hour
  [  474.403700] EEH: Notify device drivers to shutdown
  [  474.403707] mlx5_core 0001:01:00.3: mlx5_pci_err_detected was called
  [  474.403711] mlx5_core 0001:01:00.3: 
0001:01:00.3:mlx5_enter_error_state:115:(pid 779): start
  [  474.403870] mlx5_core 0001:01:00.3: 
0001:01:00.3:mlx5_enter_error_state:120:(pid 779): end

  
  One time I saw 
  SSep 13 09:41:32 ltc-fire1 kernel: [70437.943722] vfio-pci 0001:01:00.3: No 
device request channel registered, blocked until released by user
  Sep 13 09:41:32 ltc-fire1 kernel: [70437.944076] mlx5_core 0001:01:00.3: 
enabling device ( -> 0002)
  Sep 13 09:41:32 ltc-fire1 kernel: [70437.944110] mlx5_core 0001:01:00.3: 
Using 32-bit DMA via iommu
  Sep 13 09:41:32 ltc-fire1 kernel: [70437.944145] pci 0001:01: 0.3: [PE# 006] 
Removing DMA window #0
  Sep 13 09:41:32 ltc-fire1 kernel: [70437.944152] pci 0001:01: 0.3: [PE# 006] 
Removing DMA window #1
  Sep 13 09:41:32 ltc-fire1 kernel: [70437.944195] mlx5_core 0001:01:00.3: 
firmware version: 12.17.226
  Sep 13 09:41:32 ltc-fire1 kernel: [70437.944260] Unable to handle kernel 
paging request for data at address 0x
  Sep 13 09:41:32 ltc-fire1 kernel: [70437.944533] Faulting instruction 
address: 0xc05b37e0
  Sep 13 09:41:32 ltc-fire1 kernel: [70437.944592] Oops: Kernel access of bad 
area, sig: 11 [#1]
  Sep 13 09:41:32 ltc-fire1 kernel: [70437.944636] SMP NR_CPUS=2048 NUMA PowerNV
  Sep 13 09:41:32 ltc-fire1 kernel: [70437.944851] Modules linked in: vfio_pci 
irqbypass vfio_iommu_spapr_tce vfio_virqfd vfio vfio_spapr_eeh xt_CHECKSUM 
iptable_mangle ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_nat_ipv4 
nf_nat nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack nf_conntrack ipt_REJECT 
nf_reject_ipv4 xt_tcpudp kvm_hv kvm_pr kvm ebtable_filter ebtables 
ip6table_filter ip6_tables iptable_filter rdma_ucm(OE) ib_ucm(OE) rdma_cm(OE) 
iw_cm(OE) configfs ib_ipoib(OE) ib_cm(OE) ib_uverbs(OE) ib_umad(OE) mlx5_ib(OE) 
mlx5_core(OE) mlx4_ib(OE) ib_sa(OE) ib_mad(OE) ib_core(OE) mlx4_en(OE) 
ib_addr(OE) ib_netlink(OE) mlx4_core(OE) mlx_compat(OE) bridge stp llc joydev 
input_leds mac_hid ofpart at24 cmdlinepart powernv_flash ipmi_powernv 
nvmem_core uio_pdrv_genirq opal_prd mtd ipmi_msghandler uio ibmpowernv 
powernv_rng binfmt_misc dm_multipath knem(OE) ip_tables x_tables autofs4 
hid_generic usbhid hid uas usb_storage ast i2c_algo_bit ttm drm_kms_helper 
syscopyarea sysfillrect sys
 imgblt fb_sys_fops drm ahci devlink libahci [last unloaded: mlx4_core]
  Sep 13 09:41:32 ltc-fire1 kernel: [70437.946007] CPU: 40 PID: 12501 Comm: 
libvirtd Tainted: G   OE   4.7.0unofficial #5
  Sep 13 09:41:32 ltc-fire1 kernel: [70437.946074] task: c00ec319a200 ti: 
c00ec324c000 task.ti: c00ec324c000
  Sep 13 09:41:32 ltc-fire1 kernel: [70437.946140] NIP: c05b37e0 LR: 
c05ad070 CTR: 
  Sep 13 09:41:32 ltc-fire1 kernel: [70437.946208] REGS: c00ec324f100 TRAP: 
0300   Tainted: G   OE(4.7.0unofficial)
  Sep 13 09:41:32 ltc-fire1 kernel: [70437.946286] MSR: 90010280b033 
  CR: 84028844  XER: 2000
  Sep 13 09:41:32 ltc-fire1 kernel: [70437.946533] CFAR: c0008468 DAR: 
 DSISR: 4000 SOFTE: 0
  Sep 13 09:41:32 ltc-fire1 kernel: [70437.946533] GPR00: c05d19c8 
c00ec324f380 c13bef00 
  Sep 13 09:41:32 ltc-fire1 kernel: [70437.946533] GPR04:  
  
  Sep 13 09:41:32 ltc-fire1 kernel: [70437.946533] GPR08:  
  f3803140
 

[Kernel-packages] [Bug 1707875] Re: include support for Python bindings in "perf"

[bugproxy]

** Tags removed: targetmilestone-inin---
** Tags added: targetmilestone-inin1710

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

Title:
  include support for Python bindings in "perf"

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

Bug description:
  == Comment: #0 - Paul A. Clarke  - 2017-07-26 09:59:57 ==
  ---Problem Description---
  Request to build python bindings support with perf.

  ---Steps to Reproduce---
   Ubuntu-17.04# perf script -g python
  Python scripting not supported.  Install libpython and rebuild perf to enable 
it.
  For example:
# apt-get install python-dev (ubuntu)
# yum install python-devel (Fedora)
etc.
   
  Userspace tool common name: perf 
   
  Userspace rpm: linux-tools-common 

  Userspace tool obtained from project website:  na

  == Comment: #2 - MAMATHA INAMDAR  - 2017-08-01 05:02:34 
==
  After installing libpython, downloaded ubuntu 17.04 linux source code and 
compiled perf tool then it works fine.

  # ./perf script  -g python 
  generated Python script: perf-script.py

  but when I run perf tool without rebuilding after installing libpython
  it shows an error

  # perf script  -g python 
  Python scripting not supported.  Install libpython and rebuild perf to enable 
it.
  For example:
# apt-get install python-dev (ubuntu)
# yum install python-devel (Fedora)
etc.
  root@p8wookie:/home/Mamatha/ubuntu/ubuntu-zesty/tools/perf# perf --version
  perf version 4.10.17

  == Comment: #3 - MAMATHA INAMDAR  - 2017-08-01 05:03:44 
==
  Request to build python bindings support with perf.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1707875/+subscriptions

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

[Kernel-packages] [Bug 1702998] Re: Ubuntu 17.04: Guest crashed @writeback_sb_inodes+0x310/0x590

[Joseph Salisbury]

I built a Zesty test kernel with the requested two commits,
03e262798884b0a5f948b17433afd80606cb3497 and
f759741d9d913eb57784a94b9bca78b376fc26a9.  The also required a prereq
commit to built properly: b1d2dc5659b41741f5a29b2ade76ffb4e5bb13d8.

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

Can you test this kernel and see if it resolves 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/1702998

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

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

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

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

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

  
  Host and guest kernel build
  =
  4.10.0-8-generic

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

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

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

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

[bugproxy]

--- Comment From gwal...@br.ibm.com 2017-08-31 16:01 EDT---
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1709171/comments/6

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

Title:
  Revert 'Auto-online hotplugged memory'" patch

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

Bug description:
  == Comment: #2 - Gustavo Luiz Ferreira Walbon - 2017-07-24 16:00:16 ==
  This backport patch reverts to the previous behavior hotplug memory, and to 
ensure that CONFIG_MEMORY_HOTPLUG_DEFAULT_ONLINE is unset in the kernel config 
as well.

  == Comment: #3 - Reza A. Arbab - 2017-07-24 16:34:45 ==
  The patch to backport is

  943db62c316c ("powerpc/pseries: Revert 'Auto-online hotplugged
  memory'")

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1706380/+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 1626984] Re: kernel BUG at /build/linux-lts-xenial-_hWfOZ/linux-lts-xenial-4.4.0/security/apparmor/include/context.h:69!

[Eric Desrochers]

I was also able to reproduce using the above reproducer[1]

[1] - cat /sys/module/apparmor/parameters/audit

I think the problem here is that files in apparmor shouldn't be writable
while apparmor is disable.

-rw---

If I do :

# chmod 400 /sys/module/apparmor/parameters/audit (-r--)

then

# cat /sys/module/apparmor/parameters/audit doesn't crash and displays :
"Invalid argument", just like upstream kernel does.

- Eric

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

Title:
  kernel BUG at /build/linux-lts-xenial-_hWfOZ/linux-lts-
  xenial-4.4.0/security/apparmor/include/context.h:69!

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I am runing sosreport on ubuntu 14.04.4 LTS which has upgrade the kernel to 
4.4.0-38-generic, it get oops while copying 
/sys/module/apparmor/parameters/audit. and it also can be triggered with
  cat /sys/module/apparmor/parameters/audit.

  [  213.174092] [ cut here ]
  [  213.174130] kernel BUG at 
/build/linux-lts-xenial-_hWfOZ/linux-lts-xenial-4.4.0/security/apparmor/include/context.h:69!
  [  213.174187] invalid opcode:  [#1] SMP 
  [  213.174215] Modules linked in: ppdev lp joydev serio_raw parport_pc 
parport psmouse virtio_scsi floppy
  [  213.174283] CPU: 0 PID: 2246 Comm: cat Not tainted 4.4.0-38-generic 
#57~14.04.1-Ubuntu
  [  213.174324] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 
rel-1.8.2-0-g33fbe13 by qemu-project.org 04/01/2014
  [  213.174380] task: 880037b15780 ti: 8800399c4000 task.ti: 
8800399c4000
  [  213.174419] RIP: 0010:[]  [] 
aa_current_raw_label.part.6+0x4/0x6
  [  213.174478] RSP: 0018:8800399c7d60  EFLAGS: 00010246
  [  213.174506] RAX:  RBX: 88003a426000 RCX: 
88003e3802a0
  [  213.174542] RDX: 88003a426000 RSI: 81ddc0d8 RDI: 
88003a426000
  [  213.174578] RBP: 8800399c7d60 R08: 88003e3802a0 R09: 

  [  213.174614] R10: 1000 R11: 0246 R12: 
81e44ae0
  [  213.174658] R13: 88003e3802a0 R14: 81e4c220 R15: 
88003c2b2e40
  [  213.174702] FS:  7f7bea106740() GS:88003fc0() 
knlGS:
  [  213.174743] CS:  0010 DS:  ES:  CR0: 80050033
  [  213.174781] CR2: 00a40038 CR3: 3cdfa000 CR4: 
06f0
  [  213.174819] Stack:
  [  213.174832]  8800399c7d88 8136d58a 88003a426000 
88003a426000
  [  213.174885]  88003e3802a0 8800399c7da0 8136fda2 
88003e39c5f0
  [  213.174928]  8800399c7dd0 8109a7e4 88003c2b2e40 
81a170c0
  [  213.174971] Call Trace:
  [  213.174996]  [] policy_view_capable+0x1ba/0x220
  [  213.175030]  [] param_get_audit+0x12/0x50
  [  213.175062]  [] param_attr_show+0x54/0xa0
  [  213.175092]  [] module_attr_show+0x1d/0x30
  [  213.175130]  [] sysfs_kf_seq_show+0xc2/0x1a0
  [  213.175162]  [] kernfs_seq_show+0x23/0x30
  [  213.175199]  [] seq_read+0xe5/0x350
  [  213.175227]  [] kernfs_fop_read+0x10d/0x170
  [  213.176170]  [] __vfs_read+0x18/0x40
  [  213.177101]  [] vfs_read+0x7f/0x130
  [  213.178016]  [] SyS_read+0x46/0xa0
  [  213.178932]  [] entry_SYSCALL_64_fastpath+0x16/0x75
  [  213.179814] Code: 80 3d 1a 7f b8 00 00 75 1d 55 be 2e 00 00 00 48 c7 c7 f0 
2f cb 81 48 89 e5 e8 7c 50 cf ff 5d c6 05 fb 7e b8 00 01 c3 55 48 89 e5 <0f> 0b 
b8 01 00 00 00 3e 0f c1 07 ff c0 ff c8 7f 26 80 3d df 7e 
  [  213.182634] RIP  [] aa_current_raw_label.part.6+0x4/0x6
  [  213.183528]  RSP 

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1626984/+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 1626984] Re: kernel BUG at /build/linux-lts-xenial-_hWfOZ/linux-lts-xenial-4.4.0/security/apparmor/include/context.h:69!

[Eric Desrochers]

I was also able to reproduce using the above reproducer[1]

[1] - cat /sys/module/apparmor/parameters/audit

I think the problem here is that files in apparmor shouldn't be writable while 
apparmor is disable.
(-rw---)

If I do :

# chmod 400 /sys/module/apparmor/parameters/audit (-r)

then

# cat /sys/module/apparmor/parameters/audit doesn't crash and displays :
"Invalid argument", just like upstream kernel does.

- Eric

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

Title:
  kernel BUG at /build/linux-lts-xenial-_hWfOZ/linux-lts-
  xenial-4.4.0/security/apparmor/include/context.h:69!

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I am runing sosreport on ubuntu 14.04.4 LTS which has upgrade the kernel to 
4.4.0-38-generic, it get oops while copying 
/sys/module/apparmor/parameters/audit. and it also can be triggered with
  cat /sys/module/apparmor/parameters/audit.

  [  213.174092] [ cut here ]
  [  213.174130] kernel BUG at 
/build/linux-lts-xenial-_hWfOZ/linux-lts-xenial-4.4.0/security/apparmor/include/context.h:69!
  [  213.174187] invalid opcode:  [#1] SMP 
  [  213.174215] Modules linked in: ppdev lp joydev serio_raw parport_pc 
parport psmouse virtio_scsi floppy
  [  213.174283] CPU: 0 PID: 2246 Comm: cat Not tainted 4.4.0-38-generic 
#57~14.04.1-Ubuntu
  [  213.174324] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 
rel-1.8.2-0-g33fbe13 by qemu-project.org 04/01/2014
  [  213.174380] task: 880037b15780 ti: 8800399c4000 task.ti: 
8800399c4000
  [  213.174419] RIP: 0010:[]  [] 
aa_current_raw_label.part.6+0x4/0x6
  [  213.174478] RSP: 0018:8800399c7d60  EFLAGS: 00010246
  [  213.174506] RAX:  RBX: 88003a426000 RCX: 
88003e3802a0
  [  213.174542] RDX: 88003a426000 RSI: 81ddc0d8 RDI: 
88003a426000
  [  213.174578] RBP: 8800399c7d60 R08: 88003e3802a0 R09: 

  [  213.174614] R10: 1000 R11: 0246 R12: 
81e44ae0
  [  213.174658] R13: 88003e3802a0 R14: 81e4c220 R15: 
88003c2b2e40
  [  213.174702] FS:  7f7bea106740() GS:88003fc0() 
knlGS:
  [  213.174743] CS:  0010 DS:  ES:  CR0: 80050033
  [  213.174781] CR2: 00a40038 CR3: 3cdfa000 CR4: 
06f0
  [  213.174819] Stack:
  [  213.174832]  8800399c7d88 8136d58a 88003a426000 
88003a426000
  [  213.174885]  88003e3802a0 8800399c7da0 8136fda2 
88003e39c5f0
  [  213.174928]  8800399c7dd0 8109a7e4 88003c2b2e40 
81a170c0
  [  213.174971] Call Trace:
  [  213.174996]  [] policy_view_capable+0x1ba/0x220
  [  213.175030]  [] param_get_audit+0x12/0x50
  [  213.175062]  [] param_attr_show+0x54/0xa0
  [  213.175092]  [] module_attr_show+0x1d/0x30
  [  213.175130]  [] sysfs_kf_seq_show+0xc2/0x1a0
  [  213.175162]  [] kernfs_seq_show+0x23/0x30
  [  213.175199]  [] seq_read+0xe5/0x350
  [  213.175227]  [] kernfs_fop_read+0x10d/0x170
  [  213.176170]  [] __vfs_read+0x18/0x40
  [  213.177101]  [] vfs_read+0x7f/0x130
  [  213.178016]  [] SyS_read+0x46/0xa0
  [  213.178932]  [] entry_SYSCALL_64_fastpath+0x16/0x75
  [  213.179814] Code: 80 3d 1a 7f b8 00 00 75 1d 55 be 2e 00 00 00 48 c7 c7 f0 
2f cb 81 48 89 e5 e8 7c 50 cf ff 5d c6 05 fb 7e b8 00 01 c3 55 48 89 e5 <0f> 0b 
b8 01 00 00 00 3e 0f c1 07 ff c0 ff c8 7f 26 80 3d df 7e 
  [  213.182634] RIP  [] aa_current_raw_label.part.6+0x4/0x6
  [  213.183528]  RSP 

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1626984/+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 1626984] Re: kernel BUG at /build/linux-lts-xenial-_hWfOZ/linux-lts-xenial-4.4.0/security/apparmor/include/context.h:69!

[Eric Desrochers]

At first glance, it seems the problem seems to be introduce with
commit[1].

I notice the problem while running the sosreport kernel plugin[2] on a
system with apparmor disable (apparmor=0).


[1] - commit
commit a3c6147c6f4132e943db2cff4e1a85887277fc2a
Author: John Johansen 
Date:   Fri Mar 18 06:09:27 2016 -0700

UBUNTU: SAUCE: (no-up) apparmor: sync of apparmor3.5-beta1 snapshot

[2] - sos/plugins/kernel.py
..
58 clocksource_path = "/sys/devices/system/clocksource/clocksource0/"
59 self.add_copy_spec([
60 "/proc/modules",
61 "/proc/sys/kernel/random/boot_id",
==> 62 "/sys/module/*/parameters",
63 "/sys/module/*/initstate",
64 "/sys/module/*/refcnt",
65 "/sys/module/*/taint",
66 "/sys/firmware/acpi/*",
..

- Eric

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

Title:
  kernel BUG at /build/linux-lts-xenial-_hWfOZ/linux-lts-
  xenial-4.4.0/security/apparmor/include/context.h:69!

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I am runing sosreport on ubuntu 14.04.4 LTS which has upgrade the kernel to 
4.4.0-38-generic, it get oops while copying 
/sys/module/apparmor/parameters/audit. and it also can be triggered with
  cat /sys/module/apparmor/parameters/audit.

  [  213.174092] [ cut here ]
  [  213.174130] kernel BUG at 
/build/linux-lts-xenial-_hWfOZ/linux-lts-xenial-4.4.0/security/apparmor/include/context.h:69!
  [  213.174187] invalid opcode:  [#1] SMP 
  [  213.174215] Modules linked in: ppdev lp joydev serio_raw parport_pc 
parport psmouse virtio_scsi floppy
  [  213.174283] CPU: 0 PID: 2246 Comm: cat Not tainted 4.4.0-38-generic 
#57~14.04.1-Ubuntu
  [  213.174324] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 
rel-1.8.2-0-g33fbe13 by qemu-project.org 04/01/2014
  [  213.174380] task: 880037b15780 ti: 8800399c4000 task.ti: 
8800399c4000
  [  213.174419] RIP: 0010:[]  [] 
aa_current_raw_label.part.6+0x4/0x6
  [  213.174478] RSP: 0018:8800399c7d60  EFLAGS: 00010246
  [  213.174506] RAX:  RBX: 88003a426000 RCX: 
88003e3802a0
  [  213.174542] RDX: 88003a426000 RSI: 81ddc0d8 RDI: 
88003a426000
  [  213.174578] RBP: 8800399c7d60 R08: 88003e3802a0 R09: 

  [  213.174614] R10: 1000 R11: 0246 R12: 
81e44ae0
  [  213.174658] R13: 88003e3802a0 R14: 81e4c220 R15: 
88003c2b2e40
  [  213.174702] FS:  7f7bea106740() GS:88003fc0() 
knlGS:
  [  213.174743] CS:  0010 DS:  ES:  CR0: 80050033
  [  213.174781] CR2: 00a40038 CR3: 3cdfa000 CR4: 
06f0
  [  213.174819] Stack:
  [  213.174832]  8800399c7d88 8136d58a 88003a426000 
88003a426000
  [  213.174885]  88003e3802a0 8800399c7da0 8136fda2 
88003e39c5f0
  [  213.174928]  8800399c7dd0 8109a7e4 88003c2b2e40 
81a170c0
  [  213.174971] Call Trace:
  [  213.174996]  [] policy_view_capable+0x1ba/0x220
  [  213.175030]  [] param_get_audit+0x12/0x50
  [  213.175062]  [] param_attr_show+0x54/0xa0
  [  213.175092]  [] module_attr_show+0x1d/0x30
  [  213.175130]  [] sysfs_kf_seq_show+0xc2/0x1a0
  [  213.175162]  [] kernfs_seq_show+0x23/0x30
  [  213.175199]  [] seq_read+0xe5/0x350
  [  213.175227]  [] kernfs_fop_read+0x10d/0x170
  [  213.176170]  [] __vfs_read+0x18/0x40
  [  213.177101]  [] vfs_read+0x7f/0x130
  [  213.178016]  [] SyS_read+0x46/0xa0
  [  213.178932]  [] entry_SYSCALL_64_fastpath+0x16/0x75
  [  213.179814] Code: 80 3d 1a 7f b8 00 00 75 1d 55 be 2e 00 00 00 48 c7 c7 f0 
2f cb 81 48 89 e5 e8 7c 50 cf ff 5d c6 05 fb 7e b8 00 01 c3 55 48 89 e5 <0f> 0b 
b8 01 00 00 00 3e 0f c1 07 ff c0 ff c8 7f 26 80 3d df 7e 
  [  213.182634] RIP  [] aa_current_raw_label.part.6+0x4/0x6
  [  213.183528]  RSP 

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1626984/+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 1567557] Re: Performance degradation of "zfs clone"

[Colin Ian King]

@Brian, Yes indeed I have performed exhaustive testing on this on
Xenial, Zesty, Artful. A full exhaustive test takes 5 hours and I have
performed the upgrade steps and checked this out.

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

Title:
  Performance degradation of "zfs clone"

Status in Native ZFS for Linux:
  New
Status in zfs-linux package in Ubuntu:
  Fix Released
Status in zfs-linux source package in Xenial:
  Fix Committed
Status in zfs-linux source package in Zesty:
  Fix Committed
Status in zfs-linux source package in Artful:
  Fix Released

Bug description:
  [SRU Justification]

  Creating tens of hundreds of clones can be prohibitively slow. The
  underlying mechanism to gather clone information is using a 16K buffer
  which limits performance.  Also, the initial assumption is to pass in
  zero sized buffer to   the underlying ioctl() to get an idea of the
  size of the buffer required to fetch information back to userspace.
  If we bump the initial buffer to a larger size then we reduce the need
  for two ioctl calls which improves performance.

  [Fix]
  Bump initial buffer size from 16K to 256K

  [Regression Potential]
  This is minimal as this is just a tweak in the initial buffer size and larger 
sizes are handled correctly by ZFS since they are normally used on the second 
ioctl() call once we have established the size of the buffer required from the 
first ioctl() call. Larger initial buffers just remove the need for the initial 
size estimation for most cases where the number of clones is less than ~5000.  
There is a risk that a larger buffer size could lead to a ENOMEM issue when 
allocating the buffer, but the size of buffer used is still trivial for modern 
large 64 bit servers running ZFS.

  [Test case]
  Create 4000 clones. With the fix this takes 35-40% less time than without the 
fix. See the example test.sh script as an example of how to create this many 
clones.


  
  --

  I've been running some scale tests for LXD and what I've noticed is
  that "zfs clone" gets slower and slower as the zfs filesystem is
  getting busier.

  It feels like "zfs clone" requires some kind of pool-wide lock or
  something and so needs for all operations to complete before it can
  clone a new filesystem.

  A basic LXD scale test with btrfs vs zfs shows what I mean, see below
  for the reports.

  The test is run on a completely dedicated physical server with the
  pool on a dedicated SSD, the exact same machine and SSD was used for
  the btrfs test.

  The zfs filesystem is configured with those settings:
   - relatime=on
   - sync=disabled
   - xattr=sa

  So it shouldn't be related to pending sync() calls...

  The workload in this case is ultimately 1024 containers running busybox as 
their init system and udhcpc grabbing an IP.
  The problem gets significantly worse if spawning busier containers, say a 
full Ubuntu system.

  === zfs ===
  root@edfu:~# /home/ubuntu/lxd-benchmark spawn --count=1024 
--image=images:alpine/edge/amd64 --privileged=true
  Test environment:
    Server backend: lxd
    Server version: 2.0.0.rc8
    Kernel: Linux
    Kernel architecture: x86_64
    Kernel version: 4.4.0-16-generic
    Storage backend: zfs
    Storage version: 5
    Container backend: lxc
    Container version: 2.0.0.rc15

  Test variables:
    Container count: 1024
    Container mode: privileged
    Image: images:alpine/edge/amd64
    Batches: 128
    Batch size: 8
    Remainder: 0

  [Apr  3 06:42:51.170] Importing image into local store: 
64192037277800298d8c19473c055868e0288b039349b1c6579971fe99fdbac7
  [Apr  3 06:42:52.657] Starting the test
  [Apr  3 06:42:53.994] Started 8 containers in 1.336s
  [Apr  3 06:42:55.521] Started 16 containers in 2.864s
  [Apr  3 06:42:58.632] Started 32 containers in 5.975s
  [Apr  3 06:43:05.399] Started 64 containers in 12.742s
  [Apr  3 06:43:20.343] Started 128 containers in 27.686s
  [Apr  3 06:43:57.269] Started 256 containers in 64.612s
  [Apr  3 06:46:09.112] Started 512 containers in 196.455s
  [Apr  3 06:58:19.309] Started 1024 containers in 926.652s
  [Apr  3 06:58:19.309] Test completed in 926.652s

  === btrfs ===
  Test environment:
    Server backend: lxd
    Server version: 2.0.0.rc8
    Kernel: Linux
    Kernel architecture: x86_64
    Kernel version: 4.4.0-16-generic
    Storage backend: btrfs
    Storage version: 4.4
    Container backend: lxc
    Container version: 2.0.0.rc15

  Test variables:
    Container count: 1024
    Container mode: privileged
    Image: images:alpine/edge/amd64
    Batches: 128
    Batch size: 8
    Remainder: 0

  [Apr  3 07:42:12.053] Importing image into local store: 
64192037277800298d8c19473c055868e0288b039349b1c6579971fe99fdbac7
  [Apr  3 07:42:13.351] Starting the test
  [Apr  3 07:42:14.793] Started 8 containers in 1.442s
  [Apr  3 

[Kernel-packages] [Bug 1711407] Re: unregister_netdevice: waiting for lo to become free

[Fabian Holler]

Attached are the logs for an Oops on Ubuntu 14.04 on kernel linux-
image-4.4.0-93-generic=4.4.0-93.116~14.04.1

** Attachment added: "kernoops-4.4.0-93.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1711407/+attachment/4941963/+files/kernoops-4.4.0-93.txt

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

Title:
  unregister_netdevice: waiting for lo to become free

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  This is a "continuation" of bug 1403152, as that bug has been marked
  "fix released" and recent reports of failure may (or may not) be a new
  bug.  Any further reports of the problem should please be reported
  here instead of that bug.

  --

  [Impact]

  When shutting down and starting containers the container network
  namespace may experience a dst reference counting leak which results
  in this message repeated in the logs:

  unregister_netdevice: waiting for lo to become free. Usage count =
  1

  This can cause issues when trying to create net network namespace and
  thus block a user from creating new containers.

  [Test Case]

  ?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1711407/+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 1714317] Re: package bcmwl-kernel-source 6.30.223.248+bdcom-0ubuntu11 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before att

[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 bcmwl in Ubuntu.
https://bugs.launchpad.net/bugs/1714317

Title:
  package bcmwl-kernel-source 6.30.223.248+bdcom-0ubuntu11 failed to
  install/upgrade: package is in a very bad inconsistent state; you
  should  reinstall it before attempting configuration

Status in bcmwl package in Ubuntu:
  New

Bug description:
  Issues with doing initial system updates.

  ProblemType: Package
  DistroRelease: Ubuntu 16.10
  Package: bcmwl-kernel-source 6.30.223.248+bdcom-0ubuntu11
  ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0
  Uname: Linux 4.8.0-22-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8.7
  AptOrdering:
   gnome-shell-common:amd64: Install
   python-gi:amd64: Install
   gnome-tweak-tool:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  Date: Thu Aug 31 13:40:47 2017
  DuplicateSignature:
   package:bcmwl-kernel-source:6.30.223.248+bdcom-0ubuntu11
   Processing triggers for libglib2.0-0:amd64 (2.50.2-2ubuntu1) ...
   dpkg: error processing package bcmwl-kernel-source (--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 2017-08-31 (0 days ago)
  InstallationMedia: budgie-remix 16.10 "Budgie-remix" -  amd64 (20161013)
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu1.1
   apt  1.3.5
  SourcePackage: bcmwl
  Title: package bcmwl-kernel-source 6.30.223.248+bdcom-0ubuntu11 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/bcmwl/+bug/1714317/+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 1714317] [NEW] package bcmwl-kernel-source 6.30.223.248+bdcom-0ubuntu11 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before a

[Lloyd Harp]

Public bug reported:

Issues with doing initial system updates.

ProblemType: Package
DistroRelease: Ubuntu 16.10
Package: bcmwl-kernel-source 6.30.223.248+bdcom-0ubuntu11
ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0
Uname: Linux 4.8.0-22-generic x86_64
ApportVersion: 2.20.3-0ubuntu8.7
AptOrdering:
 gnome-shell-common:amd64: Install
 python-gi:amd64: Install
 gnome-tweak-tool:amd64: Install
 NULL: ConfigurePending
Architecture: amd64
Date: Thu Aug 31 13:40:47 2017
DuplicateSignature:
 package:bcmwl-kernel-source:6.30.223.248+bdcom-0ubuntu11
 Processing triggers for libglib2.0-0:amd64 (2.50.2-2ubuntu1) ...
 dpkg: error processing package bcmwl-kernel-source (--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 2017-08-31 (0 days ago)
InstallationMedia: budgie-remix 16.10 "Budgie-remix" -  amd64 (20161013)
RelatedPackageVersions:
 dpkg 1.18.10ubuntu1.1
 apt  1.3.5
SourcePackage: bcmwl
Title: package bcmwl-kernel-source 6.30.223.248+bdcom-0ubuntu11 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)

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


** Tags: amd64 apport-package yakkety

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

Title:
  package bcmwl-kernel-source 6.30.223.248+bdcom-0ubuntu11 failed to
  install/upgrade: package is in a very bad inconsistent state; you
  should  reinstall it before attempting configuration

Status in bcmwl package in Ubuntu:
  New

Bug description:
  Issues with doing initial system updates.

  ProblemType: Package
  DistroRelease: Ubuntu 16.10
  Package: bcmwl-kernel-source 6.30.223.248+bdcom-0ubuntu11
  ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0
  Uname: Linux 4.8.0-22-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8.7
  AptOrdering:
   gnome-shell-common:amd64: Install
   python-gi:amd64: Install
   gnome-tweak-tool:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  Date: Thu Aug 31 13:40:47 2017
  DuplicateSignature:
   package:bcmwl-kernel-source:6.30.223.248+bdcom-0ubuntu11
   Processing triggers for libglib2.0-0:amd64 (2.50.2-2ubuntu1) ...
   dpkg: error processing package bcmwl-kernel-source (--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 2017-08-31 (0 days ago)
  InstallationMedia: budgie-remix 16.10 "Budgie-remix" -  amd64 (20161013)
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu1.1
   apt  1.3.5
  SourcePackage: bcmwl
  Title: package bcmwl-kernel-source 6.30.223.248+bdcom-0ubuntu11 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/bcmwl/+bug/1714317/+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 1567557] Re: Performance degradation of "zfs clone"

[Brian Murray]

Has this also been verified with Ubuntu 17.04? While its unlikely people
are upgrading from 16.04 to 17.04 it is an upgrade path and we should
ensure this fix does not regress and release these updates together.

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

Title:
  Performance degradation of "zfs clone"

Status in Native ZFS for Linux:
  New
Status in zfs-linux package in Ubuntu:
  Fix Released
Status in zfs-linux source package in Xenial:
  Fix Committed
Status in zfs-linux source package in Zesty:
  Fix Committed
Status in zfs-linux source package in Artful:
  Fix Released

Bug description:
  [SRU Justification]

  Creating tens of hundreds of clones can be prohibitively slow. The
  underlying mechanism to gather clone information is using a 16K buffer
  which limits performance.  Also, the initial assumption is to pass in
  zero sized buffer to   the underlying ioctl() to get an idea of the
  size of the buffer required to fetch information back to userspace.
  If we bump the initial buffer to a larger size then we reduce the need
  for two ioctl calls which improves performance.

  [Fix]
  Bump initial buffer size from 16K to 256K

  [Regression Potential]
  This is minimal as this is just a tweak in the initial buffer size and larger 
sizes are handled correctly by ZFS since they are normally used on the second 
ioctl() call once we have established the size of the buffer required from the 
first ioctl() call. Larger initial buffers just remove the need for the initial 
size estimation for most cases where the number of clones is less than ~5000.  
There is a risk that a larger buffer size could lead to a ENOMEM issue when 
allocating the buffer, but the size of buffer used is still trivial for modern 
large 64 bit servers running ZFS.

  [Test case]
  Create 4000 clones. With the fix this takes 35-40% less time than without the 
fix. See the example test.sh script as an example of how to create this many 
clones.


  
  --

  I've been running some scale tests for LXD and what I've noticed is
  that "zfs clone" gets slower and slower as the zfs filesystem is
  getting busier.

  It feels like "zfs clone" requires some kind of pool-wide lock or
  something and so needs for all operations to complete before it can
  clone a new filesystem.

  A basic LXD scale test with btrfs vs zfs shows what I mean, see below
  for the reports.

  The test is run on a completely dedicated physical server with the
  pool on a dedicated SSD, the exact same machine and SSD was used for
  the btrfs test.

  The zfs filesystem is configured with those settings:
   - relatime=on
   - sync=disabled
   - xattr=sa

  So it shouldn't be related to pending sync() calls...

  The workload in this case is ultimately 1024 containers running busybox as 
their init system and udhcpc grabbing an IP.
  The problem gets significantly worse if spawning busier containers, say a 
full Ubuntu system.

  === zfs ===
  root@edfu:~# /home/ubuntu/lxd-benchmark spawn --count=1024 
--image=images:alpine/edge/amd64 --privileged=true
  Test environment:
    Server backend: lxd
    Server version: 2.0.0.rc8
    Kernel: Linux
    Kernel architecture: x86_64
    Kernel version: 4.4.0-16-generic
    Storage backend: zfs
    Storage version: 5
    Container backend: lxc
    Container version: 2.0.0.rc15

  Test variables:
    Container count: 1024
    Container mode: privileged
    Image: images:alpine/edge/amd64
    Batches: 128
    Batch size: 8
    Remainder: 0

  [Apr  3 06:42:51.170] Importing image into local store: 
64192037277800298d8c19473c055868e0288b039349b1c6579971fe99fdbac7
  [Apr  3 06:42:52.657] Starting the test
  [Apr  3 06:42:53.994] Started 8 containers in 1.336s
  [Apr  3 06:42:55.521] Started 16 containers in 2.864s
  [Apr  3 06:42:58.632] Started 32 containers in 5.975s
  [Apr  3 06:43:05.399] Started 64 containers in 12.742s
  [Apr  3 06:43:20.343] Started 128 containers in 27.686s
  [Apr  3 06:43:57.269] Started 256 containers in 64.612s
  [Apr  3 06:46:09.112] Started 512 containers in 196.455s
  [Apr  3 06:58:19.309] Started 1024 containers in 926.652s
  [Apr  3 06:58:19.309] Test completed in 926.652s

  === btrfs ===
  Test environment:
    Server backend: lxd
    Server version: 2.0.0.rc8
    Kernel: Linux
    Kernel architecture: x86_64
    Kernel version: 4.4.0-16-generic
    Storage backend: btrfs
    Storage version: 4.4
    Container backend: lxc
    Container version: 2.0.0.rc15

  Test variables:
    Container count: 1024
    Container mode: privileged
    Image: images:alpine/edge/amd64
    Batches: 128
    Batch size: 8
    Remainder: 0

  [Apr  3 07:42:12.053] Importing image into local store: 
64192037277800298d8c19473c055868e0288b039349b1c6579971fe99fdbac7
  [Apr  3 07:42:13.351] Starting the test
  [Apr  3 07:42:14.793] Started 8 containers in 

[Kernel-packages] [Bug 1713821] Re: arm64 arch_timer fixes

[Seth Forshee]

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

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

Title:
  arm64 arch_timer fixes

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

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

  1) Some arm64 systems have hardware defects in their architected timer
  implementations that require errata, which we workaround in the
  kernel. However, it's possible that this workaround will not be
  applied if the timer was reset w/ the user access bit set.

  2) The Juno board fails to initialize a timer at boot:

    arch_timer: Unable to map frame @ 0x
    arch_timer: Frame missing phys irq.
    Failed to initialize '/timer@2a81': -22

  3) Possible boot warning from arch_timer_mem_of_init():
     'Trying to vfree() nonexistent vm area'

  4) There's a theoretical problem where the first frame of a timer
  could be used even though a better suited timer frame is available.

  5) An infinite recursion loop will occur when enabling the function
  tracer in builds with CONFIG_PREEMPT_TRACER=y. Ubuntu does not enable
  CONFIG_PREEMPT_TRACER, so this will only be a problem if that changes.

  [Test Case]
  I've regression tested this on both a system w/ an errata workaround 
(HiSilicon D05) and one that is not (Cavium ThunderX CRB1S). In both cases the 
timer was initialized correctly. Verified by looking at the boot messages:

  dannf@d05-3:~$ dmesg | grep arch_timer
  [0.00] arch_timer: Enabling global workaround for HiSilicon erratum 
161010101
  [0.00] arch_timer: CPU0: Trapping CNTVCT access
  [0.00] arch_timer: cp15 timer(s) running at 50.00MHz (phys).
  [0.194241] arch_timer: CPU1: Trapping CNTVCT access
  [0.197305] arch_timer: CPU2: Trapping CNTVCT access
  <.>
  [0.396228] arch_timer: CPU62: Trapping CNTVCT access
  [0.399752] arch_timer: CPU63: Trapping CNTVCT access

  ubuntu@grotrian:~$ dmesg | grep arch_timer
  [0.00] arch_timer: cp15 timer(s) running at 100.00MHz (phys).

  [Regression Risk]
  The regression risk is restricted to ARM systems, as this driver only applies 
there. Regressions could lead to a timer failing to initialize, or a system 
that requires errata not having the appropriate workaround applied. (Which are 
also the  conditions that the suggested backports are attempting to fix).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1713821/+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 1713103] Re: snapd 2.27.3+17.10 ADT test failure with linux 4.13.0-6.7

[Seth Forshee]

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

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

Title:
  snapd 2.27.3+17.10 ADT test failure with linux 4.13.0-6.7

Status in linux package in Ubuntu:
  Fix Committed

Bug description:
  Testing failed on:
  amd64: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-artful-canonical-kernel-team-unstable/artful/amd64/s/snapd/20170825_154928_33cfc@/log.gz
  i386: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-artful-canonical-kernel-team-unstable/artful/i386/s/snapd/20170825_150258_33cfc@/log.gz
  ppc64el: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-artful-canonical-kernel-team-unstable/artful/ppc64el/s/snapd/20170825_141201_33cfc@/log.gz

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

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

[Kernel-packages] [Bug 1238110] Update Released

[Brian Murray]

The verification of the Stable Release Update for makedumpfile has
completed successfully and the package has now been released to
-updates.  Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  makedumpfile needs porting for AArch64

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

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

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

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

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

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

  - Demoting the "Depends:" to a "Recommends:". I actually think we
  should do this going forward (https://bugs.debian.org/cgi-
  bin/bugreport.cgi?bug=865701), but this would be a change in behavior
  to people who may install kdump-tools w/ Recommends-disabled and
  expect to stil get makedumpfile.

  - Demoting only on arm64: This isn't possible unless we switch kdump-
  tools from Binary: any to Binary: all. I also think there are good
  reasons to do that in future releases (https://bugs.debian.org/cgi-
  bin/bugreport.cgi?bug=863858), but it seems overkill for just enabling
  arm64.

To manage notifications about this bug go to:
https://bugs.launchpad.net/linaro-aarch64/+bug/1238110/+subscriptions

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

[Kernel-packages] [Bug 1238110] Re: makedumpfile needs porting for AArch64

[Launchpad Bug Tracker]

This bug was fixed in the package makedumpfile - 1:1.5.9-5ubuntu0.5

---
makedumpfile (1:1.5.9-5ubuntu0.5) xenial; urgency=medium

  * Build on arm64. While this version of makedumpfile doesn't support
creating filtered dumps of Ubuntu arm64 kernels, it does satisfy
the dependency for kdump-tools, which will cleanly fallback to 'cp'
mode if makedumpfile fails. LP: #1238110, LP: #1694859.

 -- dann frazier   Mon, 17 Jul 2017 16:58:59
-0600

** Changed in: makedumpfile (Ubuntu Xenial)
   Status: Fix Committed => Fix Released

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

Title:
  makedumpfile needs porting for AArch64

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

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

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

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

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

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

  - Demoting the "Depends:" to a "Recommends:". I actually think we
  should do this going forward (https://bugs.debian.org/cgi-
  bin/bugreport.cgi?bug=865701), but this would be a change in behavior
  to people who may install kdump-tools w/ Recommends-disabled and
  expect to stil get makedumpfile.

  - Demoting only on arm64: This isn't possible unless we switch kdump-
  tools from Binary: any to Binary: all. I also think there are good
  reasons to do that in future releases (https://bugs.debian.org/cgi-
  bin/bugreport.cgi?bug=863858), but it seems overkill for just enabling
  arm64.

To manage notifications about this bug go to:
https://bugs.launchpad.net/linaro-aarch64/+bug/1238110/+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 1694859] Re: arm64 kernel crashdump support

[Launchpad Bug Tracker]

This bug was fixed in the package makedumpfile - 1:1.5.9-5ubuntu0.5

---
makedumpfile (1:1.5.9-5ubuntu0.5) xenial; urgency=medium

  * Build on arm64. While this version of makedumpfile doesn't support
creating filtered dumps of Ubuntu arm64 kernels, it does satisfy
the dependency for kdump-tools, which will cleanly fallback to 'cp'
mode if makedumpfile fails. LP: #1238110, LP: #1694859.

 -- dann frazier   Mon, 17 Jul 2017 16:58:59
-0600

** Changed in: makedumpfile (Ubuntu Xenial)
   Status: Fix Committed => Fix Released

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

Title:
  arm64 kernel crashdump support

Status in kexec-tools package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in makedumpfile package in Ubuntu:
  Fix Released
Status in kexec-tools source package in Xenial:
  Fix Released
Status in linux source package in Xenial:
  Won't Fix
Status in makedumpfile source package in Xenial:
  Fix Released
Status in kexec-tools source package in Yakkety:
  In Progress
Status in linux source package in Yakkety:
  Won't Fix
Status in makedumpfile source package in Yakkety:
  Won't Fix
Status in kexec-tools source package in Zesty:
  Fix Released
Status in linux source package in Zesty:
  Fix Released
Status in makedumpfile source package in Zesty:
  Fix Released

Bug description:
  Note: Updates are being staged at ppa:dannf/arm64-kdump.

  [Impact]
  It is not possible to collect a kernel crash dump from a crashed arm64 server 
for later debugging.

  [Test Case]
  sudo apt install kdump-tools
  (reboot, so crashkernel= is added to the kernel commandline)
  echo c | sudo tee /proc/sysrq-trigger

  Crash dump should occur, with artifacts collected in /var/crash.

  If you want to verify that the dump is usable, install the
  corresponding linux-image--dbgsym package and run:

  sudo crash /usr/lib/debug/boot/vmlinux-
  /var/crash//dump.

  crash should successfully load, placing you at a "crash>" prompt. At that 
prompt, you can issue the 'bt' command to see a backtrace.
  Note: you need crash from zesty (7.1.8-1ubuntu1) or later.

  [Regression Risk]
  = Kernel =
  3 patches here touch code outside of arch/arm64/:

  memblock: add memblock_clear_nomap()
  This adds a new function with no callers, so regression risk is negligible.
  (A later patch adds a call to it under arch/arm64/).

  memblock: add memblock_cap_memory_range()
  This refactors some of the code in memblock_mem_limit_remove_map() into a new 
function. The only existing caller of memblock_mem_limit_remove_map() is under 
arch/arm64/, so the regression risk outside of arm64 is negligible.

  efi/libstub/arm*: Set default address and size cells values for an empty dtb
  Because this code is for EFI platforms that support device-tree, it is 
de-facto ARM-specific (as noted in the patch title).

  For arm64, we have mitigated the risk by explicit regression testing on 
several platforms:
   - Qualcomm QDF2400
   - Cavium ThunderX CRB1S
   - HP m400 (X-Gene)
   - HiSilicon D05 (Hi07)

  = kexec-tools =
  == zesty ==
  For zesty, 10 patches are required to add kdump support.

  0001-kexec-extend-the-semantics-of-kexec_iomem_for_each_l.patch:
  This modifies a function used on armhf & x86. The description explains the 
change, and why it does not impact those archs:

  -
  The current users of kexec_iomem_for_each_line(), arm, sh and x86, will not
  be affected by this change because
  * arm
    The callback function only returns -1 or 0, and the return value of
    kexec_iomem_for_each_line() will never be used.
  * sh, x86
    The callback function may return (-1 for sh,) 0 or 1, but always returns
    1 once we have reached the maximum number of entries allowed.
    Even so the current kexec_iomem_for_each_line() counts them up.
    This change actually fixes this bug.
  -

  0002-kexec-generalize-and-rename-get_kernel_stext_sym.patch:
  This generalizes a function that was duplicated by arm & x86 and makes it 
common so arm64 can use it.

  The remaining 8 of these only touch code in kexec/arch/arm64, so
  regression risk for other architectures is negligible.

  Finally, I have tested this update on both i386 and amd64 VMs. i386
  crashes do not currently work in zesty (filed LP: #1699874), and my
  test results show no change there. amd64 worked before, and continues
  to work with these changes.

  == yakkety ==
  Since yakkety is based on an older upstream, 6 additional patches are 
required:

  arm-fix-get_kernel_stext_sym-to-close-its-file.patch:
  This is a cleanup patch, cherry-picked because it allows later patches to 
apply w/o backporting. ARM-specific.

  kexec-add-max_size-to-memory_ranges.patch:
  Adds a new element to struct, to be used by later commits.

  

[Kernel-packages] [Bug 1713787] Re: linux 4.4.0-93 triggers call traces

[Simon Déziel]

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

4.4.0-94.117 has solved the problem so I'll mark this as a duplicate of
LP: #1711535 (update to stable kernel 4.4.82).

** This bug has been marked a duplicate of bug 1711535
   Xenial update to 4.4.82 stable release

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

Title:
  linux 4.4.0-93 triggers call traces

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  == Regression details ==

  Since the rolled out 4.4.0-93, we are getting many ~identical call
  traces that look like this:

  [ cut here ]
  WARNING: CPU: 0 PID:  at 
/build/linux-YyUNAI/linux-4.4.0/net/core/dev.c:2445 
skb_warn_bad_offload+0xd1/0x120()
  bond0: caps=(0x0fd97ba9, 0x) len=1487 data_len=0 
gso_size=1440 gso_type=6 ip_summed=0
  Modules linked in: binfmt_misc nf_log_ipv6 nf_conntrack_ipv6 nf_defrag_ipv6 
ip6table_filter ip6_tables nf_log_ipv4 nf_log_common xt_LOG xt_tcpudp 
nf_conntrack_ipv4 nf_defrag_ipv4 xt_owner xt_conntrack nf_conntrack 
iptable_filter ip_tables x_tables 8021q garp mrp bonding ipmi_devintf dcdbas 
intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp crct10dif_pclmul 
ipmi_ssif crc32_pclmul bridge ghash_clmulni_intel stp llc aesni_intel 
aes_x86_64 lrw gf128mul glue_helper ablk_helper cryptd vhost_net vhost macvtap 
macvlan sb_edac edac_core kvm_intel kvm ipmi_si 8250_fintek ipmi_msghandler 
lpc_ich irqbypass shpchp mei_me mei acpi_power_meter mac_hid drbd lru_cache 
autofs4 btrfs xor raid6_pq bnx2x mxm_wmi vxlan ip6_udp_tunnel tg3 udp_tunnel 
ahci mdio ptp libcrc32c libahci megaraid_sas pps_core fjes wmi
  CPU: 0 PID:  Comm: qemu-system-x86 Not tainted 4.4.0-93-generic 
#116-Ubuntu
  Hardware name: Dell Inc. PowerEdge R830/0VVT0H, BIOS 1.3.4 11/09/2016
   0286 f5a0655ded96de87 88bd7f2038c0 813f9f83
   88bd7f203908 81d6f780 88bd7f2038f8 810812f2
   88b6e118e000 8a3d17f52000 0006 0081
  Call Trace:
 [] dump_stack+0x63/0x90
   [] warn_slowpath_common+0x82/0xc0
   [] warn_slowpath_fmt+0x5c/0x80
   [] ? ___ratelimit+0xa2/0xe0
   [] skb_warn_bad_offload+0xd1/0x120
   [] __skb_gso_segment+0xfd/0x110
   [] validate_xmit_skb.isra.97.part.98+0x10d/0x2b0
   [] __dev_queue_xmit+0x582/0x590
   [] dev_queue_xmit+0x10/0x20
   [] vlan_dev_hard_start_xmit+0x98/0x120 [8021q]
   [] dev_hard_start_xmit+0x249/0x3d0
   [] __dev_queue_xmit+0x526/0x590
   [] dev_queue_xmit+0x10/0x20
   [] br_dev_queue_push_xmit+0x7a/0x140 [bridge]
   [] br_forward_finish+0x3d/0xb0 [bridge]
   [] ? br_handle_frame_finish+0x3a0/0x620 [bridge]
   [] __br_forward+0xa6/0x130 [bridge]
   [] br_forward+0x87/0x90 [bridge]
   [] br_handle_frame_finish+0x3a0/0x620 [bridge]
   [] ? __netif_receive_skb_core+0x364/0xa60
   [] ? dev_gro_receive+0x1c0/0x3c0
   [] br_handle_frame+0x174/0x2b0 [bridge]
   [] ? tg3_poll_work+0x4cb/0xf10 [tg3]
   [] ? __netif_receive_skb+0x18/0x60
   [] __netif_receive_skb_core+0x364/0xa60
   [] ? napi_gro_flush+0x5a/0x80
   [] __netif_receive_skb+0x18/0x60
   [] process_backlog+0xa8/0x150
   [] net_rx_action+0x21e/0x360
   [] __do_softirq+0x101/0x290
   [] do_softirq_own_stack+0x1c/0x30
 [] do_softirq.part.19+0x38/0x40
   [] do_softirq+0x1d/0x20
   [] netif_rx_ni+0x33/0x80
   [] tun_get_user+0x506/0x880
   [] tun_chr_write_iter+0x57/0x70
   [] do_iter_readv_writev+0x6c/0xa0
   [] do_readv_writev+0x18f/0x230
   [] vfs_writev+0x39/0x50
   [] SyS_writev+0x59/0xf0
   [] entry_SYSCALL_64_fastpath+0x16/0x71
  ---[ end trace 9fe5c984ff319e6a ]---

  For now this doesn't seem to have any user visible impact but we are
  not paying close attention to latencies/packet losses.

  Discovered in version:  linux-image-4.4.0-93-generic 4.4.0-93.116
  Last known good version: linux-image-4.4.0-92-generic 4.4.0-92.115

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-93-generic 4.4.0-93.116
  ProcVersionSignature: Ubuntu 4.4.0-93.116-generic 4.4.79
  Uname: Linux 4.4.0-93-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Aug 28 12:27 seq
   crw-rw 1 root audio 116, 33 Aug 28 12:27 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: [Errno 2] No such file or directory: 'fuser'
  Date: Tue Aug 29 13:46:12 2017
  HibernationDevice: RESUME=/dev/mapper/vghost-swap
  InstallationDate: Installed on 2017-04-01 (149 days ago)
  InstallationMedia: Ubuntu-Server 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.8)
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb:
   Bus 002 Device 002: ID 8087:8002 Intel Corp. 
   Bus 002 Device 001: 

[Kernel-packages] [Bug 1711407] Re: unregister_netdevice: waiting for lo to become free

[Fabian Holler]

With https://github.com/fho/docker-samba-loop I was able to reproduce
kernel Oopses on a clean Ubuntu 16.0.4 installation with:

- linux-image-4.10.0-32-generic=4.10.0-32.36~16.04.1
- linux-image-4.11.0-14-generic=4.11.0-14.20~16.04.1

On 4.11.0-14 it was much harder to reproduce. Sometimes only a warning
happened, 1x time I was able to produce an Oops with
https://github.com/fho/docker-samba-loop/commits/more_stress
But I don't know if the changes in the branch made it more likely to happen or
if it was only a coincidence.


The kernel message:
  unregister_netdevice: waiting for lo to become free. Usage count = 1
shows up, some minutes later the oops and/or warning happens.


In a different scenario were the Ubuntu 16.04 servers were running multiple 
docker containers with Nginx or small network applications in parallel, I was 
also able to reproduce the kernel Oopses also on:

- linux-image-4.10.0-1004-gcp
- linux-image-4.4.0-93-generic
- linux-image-4.11.0-14-generic
- linux-image-4.12.10-041210-generic=4.12.10-041210.20170830

I haven't tried again to reproduce it with those kernels on a clean Ubuntu
installation and unfortunately didn't kept the kernel logs.


Kernel logs can be found in the attached file.

** Attachment added: "kernel-logs.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1711407/+attachment/4941935/+files/kernel-logs.txt

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

Title:
  unregister_netdevice: waiting for lo to become free

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  This is a "continuation" of bug 1403152, as that bug has been marked
  "fix released" and recent reports of failure may (or may not) be a new
  bug.  Any further reports of the problem should please be reported
  here instead of that bug.

  --

  [Impact]

  When shutting down and starting containers the container network
  namespace may experience a dst reference counting leak which results
  in this message repeated in the logs:

  unregister_netdevice: waiting for lo to become free. Usage count =
  1

  This can cause issues when trying to create net network namespace and
  thus block a user from creating new containers.

  [Test Case]

  ?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1711407/+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 1714298] Re: Xenial update to 4.4.85 stable release

[Stefan Bader]

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

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

** Changed in: linux (Ubuntu Xenial)
 Assignee: (unassigned) => Stefan Bader (smb)

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

** Description changed:

+ SRU Justification
  
- SRU Justification
+ Impact:
+    The upstream process for stable tree updates is quite similar
+    in scope to the Ubuntu SRU process, e.g., each patch has to
+    demonstrably fix a bug, and each patch is vetted by upstream
+    by originating either directly from a mainline/stable Linux tree or
+    a minimally backported form of that patch. The 4.4.85 upstream stable
+    patch set is now available. It should be included in the Ubuntu
+    kernel as well.
  
- Impact:
-The upstream process for stable tree updates is quite similar
-in scope to the Ubuntu SRU process, e.g., each patch has to
-demonstrably fix a bug, and each patch is vetted by upstream
-by originating either directly from a mainline/stable Linux tree or
-a minimally backported form of that patch. The 4.4.85 upstream stable
-patch set is now available. It should be included in the Ubuntu
-kernel as well.
+    git://git.kernel.org/
  
-git://git.kernel.org/
+ TEST CASE: TBD
  
- TEST CASE: TBD
- 
-The following patches from the 4.4.85 stable release shall be
- applied:
+ The following patches from the 4.4.85 stable release shall be applied:
+ * af_key: do not use GFP_KERNEL in atomic contexts
+ * dccp: purge write queue in dccp_destroy_sock()
+ * dccp: defer ccid_hc_tx_delete() at dismantle time
+ * ipv4: fix NULL dereference in free_fib_info_rcu()
+ * net_sched/sfq: update hierarchical backlog when drop packet
+ * ipv4: better IP_MAX_MTU enforcement
+ * sctp: fully initialize the IPv6 address in sctp_v6_to_addr()
+ * tipc: fix use-after-free
+ * ipv6: reset fn->rr_ptr when replacing route
+ * ipv6: repair fib6 tree in failure case
+ * tcp: when rearming RTO, if RTO time is in past then fire RTO ASAP
+ * irda: do not leak initialized list.dev to userspace
+ * net: sched: fix NULL pointer dereference when action calls some targets
+ * net_sched: fix order of queue length updates in qdisc_replace()
+ * mei: me: add broxton pci device ids
+ * mei: me: add lewisburg device ids
+ * Input: trackpoint - add new trackpoint firmware ID
+ * Input: elan_i2c - add ELAN0602 ACPI ID to support Lenovo Yoga310
+ * ALSA: core: Fix unexpected error at replacing user TLV
+ * ALSA: hda - Add stereo mic quirk for Lenovo G50-70 (17aa:3978)
+ * ARCv2: PAE40: Explicitly set MSB counterpart of SLC region ops addresses
+ * i2c: designware: Fix system suspend
+ * drm: Release driver tracking before making the object available again
+ * drm/atomic: If the atomic check fails, return its value first
+ * drm: rcar-du: lvds: Fix PLL frequency-related configuration
+ * drm: rcar-du: lvds: Rename PLLEN bit to PLLON
+ * drm: rcar-du: Fix crash in encoder failure error path
+ * drm: rcar-du: Fix display timing controller parameter
+ * drm: rcar-du: Fix H/V sync signal polarity configuration
+ * tracing: Fix freeing of filter in create_filter() when set_str is false
+ * cifs: Fix df output for users with quota limits
+ * cifs: return ENAMETOOLONG for overlong names in cifs_open()/cifs_lookup()
+ * nfsd: Limit end of page list when decoding NFSv4 WRITE
+ * perf/core: Fix group {cpu,task} validation
+ * Bluetooth: hidp: fix possible might sleep error in hidp_session_thread
+ * Bluetooth: cmtp: fix possible might sleep error in cmtp_session
+ * Bluetooth: bnep: fix possible might sleep error in bnep_session
+ * binder: use group leader instead of open thread
+ * binder: Use wake up hint for synchronous transactions.
+ * ANDROID: binder: fix proc->tsk check.
+ * iio: imu: adis16480: Fix acceleration scale factor for adis16480
+ * iio: hid-sensor-trigger: Fix the race with user space powering up sensors
+ * staging: rtl8188eu: add RNX-N150NUB support
+ * ASoC: simple-card: don't fail if sysclk setting is not supported
+ * ASoC: rsnd: disable SRC.out only when stop timing
+ * ASoC: rsnd: avoid pointless loop in rsnd_mod_interrupt()
+ * ASoC: rsnd: Add missing initialization of ADG req_rate
+ * ASoC: rsnd: ssi: 24bit data needs right-aligned settings
+ * ASoC: rsnd: don't call update callback if it was NULL
+ * ntb_transport: fix qp count bug
+ * ntb_transport: fix bug calculating num_qps_mw
+ * ACPI: ioapic: Clear on-stack resource before using it
+ * ACPI / APEI: Add missing synchronize_rcu() on NOTIFY_SCI removal
+ * Linux 4.4.85

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

Title:
  Xenial update to 4.4.85 stable release

Status in linux package in Ubuntu:
  Invalid
Status in linux source package in 

[Kernel-packages] [Bug 1714298] [NEW] Xenial update to 4.4.85 stable release

[Stefan Bader]

Public bug reported:


SRU Justification

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

   git://git.kernel.org/

TEST CASE: TBD

   The following patches from the 4.4.85 stable release shall be
applied:

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

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


** Tags: kernel-stable-tracking-bug

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

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

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

Title:
  Xenial update to 4.4.85 stable release

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

Bug description:
  
  SRU Justification

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

 git://git.kernel.org/

  TEST CASE: TBD

 The following patches from the 4.4.85 stable release shall be
  applied:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1714298/+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 711397] Re: package firmware-b43legacy-installer 4.178.10.4-5 failed to install/upgrade due to unsupported hardware

[Colin Watson]

** Attachment removed: "4827E1007C3C6FEF.jpg"
   
https://bugs.launchpad.net/ubuntu/+source/b43-fwcutter/+bug/711397/+attachment/4928025/+files/4827E1007C3C6FEF.jpg

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

Title:
  package firmware-b43legacy-installer 4.178.10.4-5 failed to
  install/upgrade due to unsupported hardware

Status in b43-fwcutter package in Ubuntu:
  Fix Released

Bug description:
  All of the bug reports collected here deal with the package
  installation failing due to unsupported hardware.

  Binary package hint: b43-fwcutter

  it failed

  ProblemType: PackageDistroRelease: Ubuntu 11.04
  Package: firmware-b43legacy-installer 4.178.10.4-5
  ProcVersionSignature: Ubuntu 2.6.38-1.28-generic 2.6.38-rc2
  Uname: Linux 2.6.38-1-generic i686
  NonfreeKernelModules: wl
  Architecture: i386
  Date: Tue Feb  1 11:55:39 2011
  ErrorMessage: ErrorMessage: subprocess installed post-installation script 
returned error exit status 1
  PackageArchitecture: allSourcePackage: b43-fwcutter
  Title: package firmware-b43legacy-installer 4.178.10.4-5 failed to 
install/upgrade: ErrorMessage: subprocess installed post-installation script 
returned error exit status 1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/b43-fwcutter/+bug/711397/+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 1709626] Re: Kernel Oops - unable to handle kernel paging request; RIP is at free_pipe_info+0x57/0x90

[Erik Hoeschler]

Hey Joseph,

after we switched to Kernel 4.4.0-31-generic everything is working fine
for now. I think we can close this bugreport because the bug is related
to the GPFS Kernel Modules which weren't tested properly on
4.4.0-87-generic.

Thanks for your support!
Regards,
Erik

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

Title:
  Kernel Oops - unable to handle kernel paging request; RIP is at
  free_pipe_info+0x57/0x90

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

Bug description:
  Hi,

  I'm running a Docker swarm with 5 Nodes. Each node is getting this
  kernel oops pretty frequently, i would say once a day. I'm not able to
  reproduce it effectively but it seem's to happen in case a docker
  stack consisting of approx. 40 containers gets deployed.

  Thanks in advance!

  Description:  Ubuntu 16.04.3 LTS
  Release:  16.04

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-87-generic 4.4.0-87.110
  ProcVersionSignature: Ubuntu 4.4.0-87.110-generic 4.4.73
  Uname: Linux 4.4.0-87-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Aug  9 10:23 seq
   crw-rw 1 root audio 116, 33 Aug  9 10:23 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: [Errno 2] No such file or directory: 'fuser'
  Date: Wed Aug  9 15:31:53 2017
  HibernationDevice: RESUME=/dev/mapper/vg00-lv_swap
  InstallationDate: Installed on 2016-06-01 (434 days ago)
  InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.3)
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  MachineType: VMware, Inc. VMware Virtual Platform
  PciMultimedia:
   
  ProcEnviron:
   LANGUAGE=en_US:en
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 svgadrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-87-generic 
root=/dev/mapper/vg00-lv_root ro cgroup_enable=memory swapaccount=1
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-87-generic N/A
   linux-backports-modules-4.4.0-87-generic  N/A
   linux-firmware1.157.11
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/21/2015
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: 6.00
  dmi.board.name: 440BX Desktop Reference Platform
  dmi.board.vendor: Intel Corporation
  dmi.board.version: None
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 1
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd09/21/2015:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:
  dmi.product.name: VMware Virtual Platform
  dmi.product.version: None
  dmi.sys.vendor: VMware, Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1709626/+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 1714229] Status changed to Confirmed

[Ubuntu Kernel Bot]

This change was made by a bot.

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

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

Title:
  hwclock will set the date to 2/2/2080 with given 2/2/80

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  On node lodygin, run:
  sudo /sbin/hwclock --set --date "2/2/80 03:04:00"

  Will set the date to 2/2/2080. Thus it failed the hwclock test, which
  expect the output of 1980

  This only happen on lodygin, other testing nodes (hainzel, rumford,
  rizzo, fozzie) are good.

  This issue has been tested on Xenial and Zesty, they will all behave
  in the same way.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-93-generic 4.4.0-93.116
  ProcVersionSignature: User Name 4.4.0-93.116-generic 4.4.79
  Uname: Linux 4.4.0-93-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Aug 31 11:27 seq
   crw-rw 1 root audio 116, 33 Aug 31 11:27 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  Date: Thu Aug 31 11:36:37 2017
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  MachineType: AMD Corporation Speedway
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 astdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-93-generic 
root=UUID=e54320fc-c0c6-4801-843e-13288cad433e ro
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-93-generic N/A
   linux-backports-modules-4.4.0-93-generic  N/A
   linux-firmware1.157.11
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/24/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: RSW1001E
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Speedway
  dmi.board.vendor: AMD Corporation
  dmi.board.version: To be filled by O.E.M.
  dmi.chassis.asset.tag: To be filled by O.E.M.
  dmi.chassis.type: 17
  dmi.chassis.vendor: To be filled by O.E.M.
  dmi.chassis.version: To be filled by O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrRSW1001E:bd07/24/2017:svnAMDCorporation:pnSpeedway:pvrTobefilledbyO.E.M.:rvnAMDCorporation:rnSpeedway:rvrTobefilledbyO.E.M.:cvnTobefilledbyO.E.M.:ct17:cvrTobefilledbyO.E.M.:
  dmi.product.name: Speedway
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: AMD Corporation

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1714229/+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 1714229] [NEW] hwclock will set the date to 2/2/2080 with given 2/2/80

[Po-Hsu Lin]

Public bug reported:

On node lodygin, run:
sudo /sbin/hwclock --set --date "2/2/80 03:04:00"

Will set the date to 2/2/2080. Thus it failed the hwclock test, which
expect the output of 1980

This only happen on lodygin, other testing nodes (hainzel, rumford,
rizzo, fozzie) are good.

This issue has been tested on Xenial and Zesty, they will all behave in
the same way.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: linux-image-4.4.0-93-generic 4.4.0-93.116
ProcVersionSignature: User Name 4.4.0-93.116-generic 4.4.79
Uname: Linux 4.4.0-93-generic x86_64
AlsaDevices:
 total 0
 crw-rw 1 root audio 116,  1 Aug 31 11:27 seq
 crw-rw 1 root audio 116, 33 Aug 31 11:27 timer
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
ApportVersion: 2.20.1-0ubuntu2.10
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
Date: Thu Aug 31 11:36:37 2017
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
MachineType: AMD Corporation Speedway
PciMultimedia:
 
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcFB: 0 astdrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-93-generic 
root=UUID=e54320fc-c0c6-4801-843e-13288cad433e ro
RelatedPackageVersions:
 linux-restricted-modules-4.4.0-93-generic N/A
 linux-backports-modules-4.4.0-93-generic  N/A
 linux-firmware1.157.11
RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/24/2017
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: RSW1001E
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: Speedway
dmi.board.vendor: AMD Corporation
dmi.board.version: To be filled by O.E.M.
dmi.chassis.asset.tag: To be filled by O.E.M.
dmi.chassis.type: 17
dmi.chassis.vendor: To be filled by O.E.M.
dmi.chassis.version: To be filled by O.E.M.
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrRSW1001E:bd07/24/2017:svnAMDCorporation:pnSpeedway:pvrTobefilledbyO.E.M.:rvnAMDCorporation:rnSpeedway:rvrTobefilledbyO.E.M.:cvnTobefilledbyO.E.M.:ct17:cvrTobefilledbyO.E.M.:
dmi.product.name: Speedway
dmi.product.version: To be filled by O.E.M.
dmi.sys.vendor: AMD Corporation

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


** Tags: amd64 apport-bug uec-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/1714229

Title:
  hwclock will set the date to 2/2/2080 with given 2/2/80

Status in linux package in Ubuntu:
  New

Bug description:
  On node lodygin, run:
  sudo /sbin/hwclock --set --date "2/2/80 03:04:00"

  Will set the date to 2/2/2080. Thus it failed the hwclock test, which
  expect the output of 1980

  This only happen on lodygin, other testing nodes (hainzel, rumford,
  rizzo, fozzie) are good.

  This issue has been tested on Xenial and Zesty, they will all behave
  in the same way.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-93-generic 4.4.0-93.116
  ProcVersionSignature: User Name 4.4.0-93.116-generic 4.4.79
  Uname: Linux 4.4.0-93-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Aug 31 11:27 seq
   crw-rw 1 root audio 116, 33 Aug 31 11:27 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  Date: Thu Aug 31 11:36:37 2017
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  MachineType: AMD Corporation Speedway
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 astdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-93-generic 
root=UUID=e54320fc-c0c6-4801-843e-13288cad433e ro
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-93-generic N/A
   linux-backports-modules-4.4.0-93-generic  N/A
   linux-firmware1.157.11
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/24/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: RSW1001E
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Speedway
  dmi.board.vendor: AMD Corporation
  dmi.board.version: To be filled by O.E.M.
  dmi.chassis.asset.tag: To be filled by O.E.M.
  dmi.chassis.type: 17
  dmi.chassis.vendor: To be filled by O.E.M.
  dmi.chassis.version: To be filled by 

[Kernel-packages] [Bug 1704720] Re: ubuntu_lttng_smoke_test failed on Artful 4.11.0-11

[Colin Ian King]

@Sam, is this still an issue now? Can we close 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/1704720

Title:
  ubuntu_lttng_smoke_test failed on Artful 4.11.0-11

Status in linux package in Ubuntu:
  In Progress

Bug description:
  After bug 1699755, this test was found failed on Artful again with
  kernel 4.11.0-11

  $ dmesg | grep lttng
  [ 8282.279726] lttng_kretprobes: loading out-of-tree module taints kernel.
  [ 8282.279754] lttng_kretprobes: module verification failed: signature and/or 
required key missing - tainting kernel
  [ 8282.282192] lttng_tracer: Unknown symbol lttng_ftrace_unregister (err 0)
  [ 8282.282205] lttng_tracer: Unknown symbol lttng_ftrace_register (err 0)
  [ 8282.282216] lttng_tracer: Unknown symbol lttng_ftrace_destroy_private (err 
0)

  $ sudo ./ubuntu_lttng_smoke_test.sh 
  == lttng smoke test of session create/destroy ==
  Session test-kernel-session created.
  Traces will be written in /tmp/lttng-kernel-trace-13336-session
  PASSED (lttng create)
  Session test-kernel-session destroyed
  PASSED (lttng destroy)
   
  == lttng smoke test list kernel events ==
  Error: Unable to list kernel events: Kernel tracer not available
  Error: Command error
  FAILED (lttng list --kernel)
  FAILED (lttng list --kernel more output expected)
   
  == lttng smoke test trace open/close system calls ==
  Session test-kernel-session created.
  Traces will be written in /tmp/lttng-kernel-trace-13336-session
  PASSED (lttng create)
  Error: Event open: Kernel tracer not available (channel channel0, session 
test-kernel-session)
  Error: Event openat: Kernel tracer not available (channel channel0, session 
test-kernel-session)
  Error: Event close: Kernel tracer not available (channel channel0, session 
test-kernel-session)
  FAILED (lttng enable-event)
  Session test-kernel-session destroyed
   
  == lttng smoke test trace context switches ==
  Session test-kernel-session created.
  Traces will be written in /tmp/lttng-kernel-trace-13336-session
  PASSED (lttng create)
  Error: Event sched_switch: Kernel tracer not available (channel channel0, 
session test-kernel-session)
  FAILED (lttng enable-event)
  Session test-kernel-session destroyed
   
  Summary: 4 passed, 4 failed

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.11.0-11-generic 4.11.0-11.16
  ProcVersionSignature: User Name 4.11.0-11.16-generic 4.11.10
  Uname: Linux 4.11.0-11-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Jul 17 04:00 seq
   crw-rw 1 root audio 116, 33 Jul 17 04:00 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.5-0ubuntu5
  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: Mon Jul 17 06:22:17 2017
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  MachineType: Intel Corporation S1200RP
  PciMultimedia:
   
  ProcFB:
   0 mgadrmfb
   1 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.11.0-11-generic 
root=UUID=b0d2ae4e-12dd-423e-acea-272ee8b2a893 ro
  RelatedPackageVersions:
   linux-restricted-modules-4.11.0-11-generic N/A
   linux-backports-modules-4.11.0-11-generic  N/A
   linux-firmware 1.167
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/01/2015
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: S1200RP.86B.03.02.0003.070120151022
  dmi.board.asset.tag: 
  dmi.board.name: S1200RP
  dmi.board.vendor: Intel Corporation
  dmi.board.version: G62254-407
  dmi.chassis.asset.tag: 
  dmi.chassis.type: 17
  dmi.chassis.vendor: ..
  dmi.chassis.version: ..
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrS1200RP.86B.03.02.0003.070120151022:bd07/01/2015:svnIntelCorporation:pnS1200RP:pvr:rvnIntelCorporation:rnS1200RP:rvrG62254-407:cvn..:ct17:cvr..:
  dmi.product.name: S1200RP
  dmi.product.version: 
  dmi.sys.vendor: Intel Corporation

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

[S. W.]

Why should this have changed. This anoying bug is existing since 15.10
and even if there are several tickets nobody funkin cares!

https://bugs.launchpad.net/ubuntu/+source/linux-lts-wily/+bug/1583191
https://bugs.launchpad.net/ubuntu/+source/linux-lts-xenial/+bug/1579803

And yes i'm not dump. I tried the latest kernel...even 4.13...oh
wonder...nothing changed

AND NO this ic NO UPSTREAM BUG! This is Ubuntu related ONLY!! I'm using 
DEBIAN 9 with exactly the same Samba settings, just an other samba version and 
kernel 4.9.
MY guess is this is a Samba related problem!
It happens ONLY when there is heavy use on Samba!


[   37.424709] audit: type=1400 audit(1503500221.451:3):
apparmor="STATUS" operation="profile_load" profile="unconfined"
name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=683
comm="apparmor_parser"
[   37.424959] audit: type=1400 audit(1503500221.452:4):
apparmor="STATUS" operation="profile_load" profile="unconfined"
name="/usr/lib/NetworkManager/nm-dhcp-helper" pid=683 comm="apparmor_parser"
[   37.425188] audit: type=1400 audit(1503500221.452:5):
apparmor="STATUS" operation="profile_load" profile="unconfined"
name="/usr/lib/connman/scripts/dhclient-script" pid=683
comm="apparmor_parser"
[   37.704058] audit: type=1400 audit(1503500221.731:6):
apparmor="STATUS" operation="profile_load" profile="unconfined"
name="/usr/lib/snapd/snap-confine" pid=688 comm="apparmor_parser"
[   37.704408] audit: type=1400 audit(1503500221.731:7):
apparmor="STATUS" operation="profile_load" profile="unconfined"
name="/usr/lib/snapd/snap-confine//mount-namespace-capture-helper"
pid=688 comm="apparmor_parser"
[   37.714792] audit: type=1400 audit(1503500221.742:8):
apparmor="STATUS" operation="profile_load" profile="unconfined"
name="/usr/lib/lightdm/lightdm-guest-session" pid=684 comm="apparmor_parser"
[   37.715154] audit: type=1400 audit(1503500221.742:9):
apparmor="STATUS" operation="profile_load" profile="unconfined"
name="/usr/lib/lightdm/lightdm-guest-session//chromium" pid=684
comm="apparmor_parser"
[   37.814957] audit: type=1400 audit(1503500221.842:10):
apparmor="STATUS" operation="profile_load" profile="unconfined"
name="/usr/sbin/cups-browsed" pid=690 comm="apparmor_parser"
[   37.854086] audit: type=1400 audit(1503500221.881:11):
apparmor="STATUS" operation="profile_load" profile="unconfined"
name="/usr/sbin/ippusbxd" pid=694 comm="apparmor_parser"
[   67.352219] NFSD: Using /var/lib/nfs/v4recovery as the NFSv4 state
recovery directory
[   67.352252] NFSD: starting 90-second grace period (net af1ec8c0)
[   82.774749] kauditd_printk_skb: 5 callbacks suppressed
[   82.774751] audit: type=1400 audit(1503500267.300:17):
apparmor="DENIED" operation="capable" profile="/usr/sbin/ntpd" pid=1467
comm="ntpd" capability=12  capname="net_admin"
[  114.385440] random: crng init done
[89653.176401] INFO: task btrfs-cleaner:226 blocked for more than 120
seconds.
[89653.176425]   Not tainted 4.13.0-041300rc6-generic #201708201831
[89653.176426] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs"
disables this message.
[89653.176428] btrfs-cleaner   D0   226  2 0x
[89653.176432] Call Trace:
[89653.176473]  __schedule+0x28b/0x890
[89653.176475]  schedule+0x36/0x80
[89653.176639]  wait_current_trans+0xd8/0x110 [btrfs]
[89653.176652]  ? wait_woken+0x80/0x80
[89653.176667]  start_transaction+0x33a/0x410 [btrfs]
[89653.176681]  btrfs_start_transaction+0x1e/0x20 [btrfs]
[89653.176693]  btrfs_drop_snapshot+0x90/0x890 [btrfs]
[89653.176706]  ? btrfs_delete_unused_bgs+0x36/0x3c0 [btrfs]
[89653.176720]  btrfs_clean_one_deleted_snapshot+0xb7/0x100 [btrfs]
[89653.176733]  cleaner_kthread+0x14a/0x180 [btrfs]
[89653.176739]  kthread+0x125/0x140
[89653.176753]  ? __btree_submit_bio_start+0x20/0x20 [btrfs]
[89653.176754]  ? kthread_create_on_node+0x70/0x70
[89653.176755]  ? kthread_create_on_node+0x70/0x70
[89653.176760]  ret_from_fork+0x25/0x30
[89653.176776] INFO: task nmbd:1367 blocked for more than 120 seconds.
[89653.176777]   Not tainted 4.13.0-041300rc6-generic #201708201831
[89653.176778] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs"
disables this message.
[89653.176780] nmbdD0  1367  1 0x
[89653.176781] Call Trace:
[89653.176783]  __schedule+0x28b/0x890
[89653.176784]  schedule+0x36/0x80
[89653.176800]  lock_extent_bits+0x170/0x1c0 [btrfs]
[89653.176801]  ? wait_woken+0x80/0x80
[89653.176816]  lock_and_cleanup_extent_if_need+0x88/0x350 [btrfs]
[89653.176831]  __btrfs_buffered_write+0x26c/0x730 [btrfs]
[89653.176846]  btrfs_file_write_iter+0x1f1/0x560 [btrfs]
[89653.176857]  __vfs_write+0xf5/0x170
[89653.176859]  vfs_write+0xb1/0x1a0
[89653.176861]  SyS_write+0x55/0xc0
[89653.176863]  entry_SYSCALL_64_fastpath+0x1e/0xa9
[89653.176864] RIP: 0033:0x7fa7b0ccb670
[89653.176865] RSP: 002b:7ffc58804b88 EFLAGS: 0246 ORIG_RAX:
0001
[89653.176866] RAX: ffda RBX: 556380ae3050 RCX:
7fa7b0ccb670
[89653.176867] RDX: 

[Kernel-packages] [Bug 1705748] Re: Samsung SSD 960 EVO 500GB refused to change power state

[Kai-Heng Feng]

Try it here:
http://people.canonical.com/~khfeng/pm961-quirks/

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

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

Status in linux package in Ubuntu:
  In Progress

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

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

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

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

  System, drive details below:

  M2 nvme drive: Samsung SSD 960 EVO 500GB

  Ubuntu 4.10.0-26.30~16.04.1-generic 4.10.17

  M/B Asus Prime B350m-A
  Ryzen 1600 cpu

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

  
  nvme list

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

  sudo nvme id-ctrl /dev/nvme0

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

[Kernel-packages] [Bug 1713467] Re: linux-aws: 4.4.0-1033.42 -proposed tracker

[Po-Hsu Lin]

4.4.0-1033.42 - aws
Regression test CMPL.
http://kernel.ubuntu.com/testing/tracker-index.html

Issue to note in x86_64 (aws):
  libhugetlbfs - 1 failed (brk_near_huge), Killed by signal 15, bad 
configuration 3
  ubuntu_lxc - Failed to start networking in ubuntu-cloud container

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

** Changed in: kernel-sru-workflow/regression-testing
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Po-Hsu Lin 
(cypressyew)

** Tags added: regression-testing-passed

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

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

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

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

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1713467/+subscriptions

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

[Kernel-packages] [Bug 1714190] Re: ubuntu_sysdig_smoke_test stuck on Zesty s390x zKVM / zVM

[Colin Ian King]

I think the hang is because the sysdig trace log fills the drive and
there is no more free space for the test run continue. I'll try and
limit this somehow and see if that helps

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

Title:
  ubuntu_sysdig_smoke_test stuck on Zesty s390x zKVM / zVM

Status in linux package in Ubuntu:
  In Progress

Bug description:
  From the test log, it looks like this test get stuck on s390x zVM and
  zKVM (kernel03, s2lp6g003) for a couple hours with zesty kernel.

  01:14:28 DEBUG| Running 
'/home/ubuntu/autotest/client/tests/ubuntu_sysdig_smoke_test/ubuntu_sysdig_smoke_test.sh'
  01:14:28 DEBUG| [stdout] == sysdig smoke test to trace dd, cat, read and 
writes ==
  01:14:28 DEBUG| [stdout] Try 1 of 10

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1714190/+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 1697556] Re: Computer freezes after login - 4.10.0-22-generic

[John Lewis]

Well, I'm running 4.10.0-33-generic, and although sometimes I have to
login twice, and it has frozen on a couple of occasions, it's pretty
much okay. So I'm not sure what exactly is different about my combo than
yours, except maybe the firmware version I'm running on the 9560.

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

Title:
  Computer freezes after login - 4.10.0-22-generic

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have got a new Ubuntu 17.04 install on a Dell XPS 15 (Intel(R)
  Core(TM) i7-7700HQ CPU @ 2.80GHz) that was installed a couple of days
  ago. Login worked fine too.

  A couple of days later I installed the suggested kernel update
  "4.10.0-22-generic". With kernel 4.10.0-22-generic, the computer
  freezes right after login (i.e. after pressing enter, the background
  image with the mouse is shown, no responses to any key strokes).

  Syslog excerpt:

  Jun 12 22:12:48 computername kernel: [   47.603358] NMI watchdog: BUG: soft 
lockup - CPU#1 stuck for 23s! [Xorg.wrap:1672]
  Jun 12 22:12:48 computername kernel: [   47.603360] Modules linked in: ccm 
msr arc4 cmac rfcomm uvcvideo videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 
videobuf2_core videodev media btusb btrtl bnep hid_multitouch nls_iso8859_1 
i2c_designware_platform i2c_designware_core snd_hda_codec_hdmi dell_wmi 
dell_led dell_smbios snd_hda_codec_realtek snd_hda_codec_generic snd_hda_intel 
dcdbas ath10k_pci snd_hda_codec ath10k_core intel_rapl snd_hda_core ath 
x86_pkg_temp_thermal snd_hwdep intel_powerclamp mac80211 snd_pcm coretemp 
snd_seq_midi snd_seq_midi_event cfg80211 snd_rawmidi rtsx_pci_ms kvm_intel 
memstick kvm irqbypass crct10dif_pclmul joydev crc32_pclmul snd_seq 
ghash_clmulni_intel snd_seq_device input_leds snd_timer serio_raw snd soundcore 
idma64 virt_dma mei_me mei shpchp processor_thermal_device intel_soc_dts_iosf 
intel_lpss_pci intel_pch_thermal
  Jun 12 22:12:48 computername kernel: [   47.603422]  hci_uart btbcm btqca 
btintel bluetooth dell_smo8800 intel_hid intel_lpss_acpi sparse_keymap 
intel_lpss tpm_crb int3403_thermal int3400_thermal acpi_als 
int340x_thermal_zone acpi_thermal_rel acpi_pad kfifo_buf industrialio mac_hid 
pcbc aesni_intel crypto_simd glue_helper cryptd aes_x86_64 dm_crypt parport_pc 
ppdev lp parport ip_tables x_tables autofs4 nouveau rtsx_pci_sdmmc i915 ttm 
i2c_algo_bit drm_kms_helper syscopyarea mxm_wmi sysfillrect psmouse sysimgblt 
fb_sys_fops nvme drm nvme_core rtsx_pci ahci libahci i2c_hid hid 
pinctrl_sunrisepoint video wmi pinctrl_intel fjes
  Jun 12 22:12:48 computername kernel: [   47.603453] CPU: 1 PID: 1672 Comm: 
Xorg.wrap Not tainted 4.10.0-22-generic #24-Ubuntu
  Jun 12 22:12:48 computername kernel: [   47.603453] Hardware name: Dell Inc. 
XPS 15 9560/05FFDN, BIOS 1.3.3 05/08/2017

  
  Note, this problem is observed with kernel 4.10.0-22-generic whereas it's not 
observed with 4.10.0-21-generic. As I was not able to login to my computer I am 
writing this bug report while it runs on kernel 4.10.0-21-generic. Therefore 
the information attached through the "ubuntu-bug linux" command here, are 
referring to the kernel that is actually working. I decided to nonetheless 
include that information as it might contain other kernel unrelated information 
that would help you troubleshooting.

  Please see attached file "syslog-4.10.0-22-generic-freeze-after-
  login.log" for the full syslog.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: linux-image-4.10.0-21-generic 4.10.0-21.23
  ProcVersionSignature: Ubuntu 4.10.0-21.23-generic 4.10.11
  Uname: Linux 4.10.0-21-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  hkuehn 1796 F pulseaudio
  CurrentDesktop: GNOME
  Date: Mon Jun 12 23:17:08 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2017-05-30 (13 days ago)
  InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 138a:0091 Validity Sensors, Inc. 
   Bus 001 Device 002: ID 0cf3:e300 Atheros Communications, Inc. 
   Bus 001 Device 004: ID 0c45:6713 Microdia 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. XPS 15 9560
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-21-generic.efi.signed 
root=UUID=e0800d30-3eff-46ac-a6af-38e3bcf99b58 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-21-generic N/A
   linux-backports-modules-4.10.0-21-generic  N/A
   linux-firmware 1.164.1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/08/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 

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

[André Düwel]

So instead of downgrading my BIOS, I've updated it from 1.2.29 to
version 1.3.0 which was released two days ago by DELL for the XPS15
9550. USB ports at the TB16 is now working without issues again.

I don't get any checksum errors, too:
for i in 1 2 3 4; do curl -s 
http://de.releases.ubuntu.com/zesty/ubuntu-17.04-server-amd64.img -o $i.iso; 
md5sum $i.iso; done
4672ce371fb3c1170a9e71bc4b2810b9  1.iso
4672ce371fb3c1170a9e71bc4b2810b9  2.iso
4672ce371fb3c1170a9e71bc4b2810b9  3.iso
4672ce371fb3c1170a9e71bc4b2810b9  4.iso

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

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

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

Bug description:
  [SRU Justification]

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

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

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

  ---

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

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

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

  Here are the relevant kernel log messages:

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

[Kernel-packages] [Bug 1697556] Re: Computer freezes after login - 4.10.0-22-generic

[John Lewis]

When you had the nvidia drivers installed, can you confirm how you
installed them?

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

Title:
  Computer freezes after login - 4.10.0-22-generic

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have got a new Ubuntu 17.04 install on a Dell XPS 15 (Intel(R)
  Core(TM) i7-7700HQ CPU @ 2.80GHz) that was installed a couple of days
  ago. Login worked fine too.

  A couple of days later I installed the suggested kernel update
  "4.10.0-22-generic". With kernel 4.10.0-22-generic, the computer
  freezes right after login (i.e. after pressing enter, the background
  image with the mouse is shown, no responses to any key strokes).

  Syslog excerpt:

  Jun 12 22:12:48 computername kernel: [   47.603358] NMI watchdog: BUG: soft 
lockup - CPU#1 stuck for 23s! [Xorg.wrap:1672]
  Jun 12 22:12:48 computername kernel: [   47.603360] Modules linked in: ccm 
msr arc4 cmac rfcomm uvcvideo videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 
videobuf2_core videodev media btusb btrtl bnep hid_multitouch nls_iso8859_1 
i2c_designware_platform i2c_designware_core snd_hda_codec_hdmi dell_wmi 
dell_led dell_smbios snd_hda_codec_realtek snd_hda_codec_generic snd_hda_intel 
dcdbas ath10k_pci snd_hda_codec ath10k_core intel_rapl snd_hda_core ath 
x86_pkg_temp_thermal snd_hwdep intel_powerclamp mac80211 snd_pcm coretemp 
snd_seq_midi snd_seq_midi_event cfg80211 snd_rawmidi rtsx_pci_ms kvm_intel 
memstick kvm irqbypass crct10dif_pclmul joydev crc32_pclmul snd_seq 
ghash_clmulni_intel snd_seq_device input_leds snd_timer serio_raw snd soundcore 
idma64 virt_dma mei_me mei shpchp processor_thermal_device intel_soc_dts_iosf 
intel_lpss_pci intel_pch_thermal
  Jun 12 22:12:48 computername kernel: [   47.603422]  hci_uart btbcm btqca 
btintel bluetooth dell_smo8800 intel_hid intel_lpss_acpi sparse_keymap 
intel_lpss tpm_crb int3403_thermal int3400_thermal acpi_als 
int340x_thermal_zone acpi_thermal_rel acpi_pad kfifo_buf industrialio mac_hid 
pcbc aesni_intel crypto_simd glue_helper cryptd aes_x86_64 dm_crypt parport_pc 
ppdev lp parport ip_tables x_tables autofs4 nouveau rtsx_pci_sdmmc i915 ttm 
i2c_algo_bit drm_kms_helper syscopyarea mxm_wmi sysfillrect psmouse sysimgblt 
fb_sys_fops nvme drm nvme_core rtsx_pci ahci libahci i2c_hid hid 
pinctrl_sunrisepoint video wmi pinctrl_intel fjes
  Jun 12 22:12:48 computername kernel: [   47.603453] CPU: 1 PID: 1672 Comm: 
Xorg.wrap Not tainted 4.10.0-22-generic #24-Ubuntu
  Jun 12 22:12:48 computername kernel: [   47.603453] Hardware name: Dell Inc. 
XPS 15 9560/05FFDN, BIOS 1.3.3 05/08/2017

  
  Note, this problem is observed with kernel 4.10.0-22-generic whereas it's not 
observed with 4.10.0-21-generic. As I was not able to login to my computer I am 
writing this bug report while it runs on kernel 4.10.0-21-generic. Therefore 
the information attached through the "ubuntu-bug linux" command here, are 
referring to the kernel that is actually working. I decided to nonetheless 
include that information as it might contain other kernel unrelated information 
that would help you troubleshooting.

  Please see attached file "syslog-4.10.0-22-generic-freeze-after-
  login.log" for the full syslog.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: linux-image-4.10.0-21-generic 4.10.0-21.23
  ProcVersionSignature: Ubuntu 4.10.0-21.23-generic 4.10.11
  Uname: Linux 4.10.0-21-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  hkuehn 1796 F pulseaudio
  CurrentDesktop: GNOME
  Date: Mon Jun 12 23:17:08 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2017-05-30 (13 days ago)
  InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 138a:0091 Validity Sensors, Inc. 
   Bus 001 Device 002: ID 0cf3:e300 Atheros Communications, Inc. 
   Bus 001 Device 004: ID 0c45:6713 Microdia 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. XPS 15 9560
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-21-generic.efi.signed 
root=UUID=e0800d30-3eff-46ac-a6af-38e3bcf99b58 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-21-generic N/A
   linux-backports-modules-4.10.0-21-generic  N/A
   linux-firmware 1.164.1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/08/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.3.3
  dmi.board.name: 05FFDN
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 

[Kernel-packages] [Bug 1713467] Re: linux-aws: 4.4.0-1033.42 -proposed tracker

[Brad Figg]

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

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

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

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

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

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1713467/+subscriptions

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

[Kernel-packages] [Bug 1714190] Re: ubuntu_sysdig_smoke_test stuck on Zesty s390x zKVM / zVM

[Po-Hsu Lin]

I would say this issue might be difficult to reproduce.

For kernel03, it has failed for 2 times and passed on the third run.
For s2lp6g003 it has passed on the first run, but stuck on the second.

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

Title:
  ubuntu_sysdig_smoke_test stuck on Zesty s390x zKVM / zVM

Status in linux package in Ubuntu:
  In Progress

Bug description:
  From the test log, it looks like this test get stuck on s390x zVM and
  zKVM (kernel03, s2lp6g003) for a couple hours with zesty kernel.

  01:14:28 DEBUG| Running 
'/home/ubuntu/autotest/client/tests/ubuntu_sysdig_smoke_test/ubuntu_sysdig_smoke_test.sh'
  01:14:28 DEBUG| [stdout] == sysdig smoke test to trace dd, cat, read and 
writes ==
  01:14:28 DEBUG| [stdout] Try 1 of 10

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1714190/+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 1697556] Re: Computer freezes after login - 4.10.0-22-generic

[hamid]

I have the same issue on my Dell XPS 9560. It has been running fine in
"intel" graphics mode up until and including kernel 4.8. With 4.10 and
4.11 it either freezes pre-boot, before I even reach the FDE password
prompt, or, if I uninstall the nvidia drivers, it freezes at some point
after.

Currently I have no nvidia drivers installed, and have had to move back
to 4.8 to boot, because 4.10 lets me enter the FDE password and then
freezes.

I've tested various combinations of kernel and drivers/no drivers and
kernel versions, and have seen either a freeze preventing me from
accessing the logs or, where possible seen "CPU stuck" messages.

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

Title:
  Computer freezes after login - 4.10.0-22-generic

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have got a new Ubuntu 17.04 install on a Dell XPS 15 (Intel(R)
  Core(TM) i7-7700HQ CPU @ 2.80GHz) that was installed a couple of days
  ago. Login worked fine too.

  A couple of days later I installed the suggested kernel update
  "4.10.0-22-generic". With kernel 4.10.0-22-generic, the computer
  freezes right after login (i.e. after pressing enter, the background
  image with the mouse is shown, no responses to any key strokes).

  Syslog excerpt:

  Jun 12 22:12:48 computername kernel: [   47.603358] NMI watchdog: BUG: soft 
lockup - CPU#1 stuck for 23s! [Xorg.wrap:1672]
  Jun 12 22:12:48 computername kernel: [   47.603360] Modules linked in: ccm 
msr arc4 cmac rfcomm uvcvideo videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 
videobuf2_core videodev media btusb btrtl bnep hid_multitouch nls_iso8859_1 
i2c_designware_platform i2c_designware_core snd_hda_codec_hdmi dell_wmi 
dell_led dell_smbios snd_hda_codec_realtek snd_hda_codec_generic snd_hda_intel 
dcdbas ath10k_pci snd_hda_codec ath10k_core intel_rapl snd_hda_core ath 
x86_pkg_temp_thermal snd_hwdep intel_powerclamp mac80211 snd_pcm coretemp 
snd_seq_midi snd_seq_midi_event cfg80211 snd_rawmidi rtsx_pci_ms kvm_intel 
memstick kvm irqbypass crct10dif_pclmul joydev crc32_pclmul snd_seq 
ghash_clmulni_intel snd_seq_device input_leds snd_timer serio_raw snd soundcore 
idma64 virt_dma mei_me mei shpchp processor_thermal_device intel_soc_dts_iosf 
intel_lpss_pci intel_pch_thermal
  Jun 12 22:12:48 computername kernel: [   47.603422]  hci_uart btbcm btqca 
btintel bluetooth dell_smo8800 intel_hid intel_lpss_acpi sparse_keymap 
intel_lpss tpm_crb int3403_thermal int3400_thermal acpi_als 
int340x_thermal_zone acpi_thermal_rel acpi_pad kfifo_buf industrialio mac_hid 
pcbc aesni_intel crypto_simd glue_helper cryptd aes_x86_64 dm_crypt parport_pc 
ppdev lp parport ip_tables x_tables autofs4 nouveau rtsx_pci_sdmmc i915 ttm 
i2c_algo_bit drm_kms_helper syscopyarea mxm_wmi sysfillrect psmouse sysimgblt 
fb_sys_fops nvme drm nvme_core rtsx_pci ahci libahci i2c_hid hid 
pinctrl_sunrisepoint video wmi pinctrl_intel fjes
  Jun 12 22:12:48 computername kernel: [   47.603453] CPU: 1 PID: 1672 Comm: 
Xorg.wrap Not tainted 4.10.0-22-generic #24-Ubuntu
  Jun 12 22:12:48 computername kernel: [   47.603453] Hardware name: Dell Inc. 
XPS 15 9560/05FFDN, BIOS 1.3.3 05/08/2017

  
  Note, this problem is observed with kernel 4.10.0-22-generic whereas it's not 
observed with 4.10.0-21-generic. As I was not able to login to my computer I am 
writing this bug report while it runs on kernel 4.10.0-21-generic. Therefore 
the information attached through the "ubuntu-bug linux" command here, are 
referring to the kernel that is actually working. I decided to nonetheless 
include that information as it might contain other kernel unrelated information 
that would help you troubleshooting.

  Please see attached file "syslog-4.10.0-22-generic-freeze-after-
  login.log" for the full syslog.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: linux-image-4.10.0-21-generic 4.10.0-21.23
  ProcVersionSignature: Ubuntu 4.10.0-21.23-generic 4.10.11
  Uname: Linux 4.10.0-21-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  hkuehn 1796 F pulseaudio
  CurrentDesktop: GNOME
  Date: Mon Jun 12 23:17:08 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2017-05-30 (13 days ago)
  InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 138a:0091 Validity Sensors, Inc. 
   Bus 001 Device 002: ID 0cf3:e300 Atheros Communications, Inc. 
   Bus 001 Device 004: ID 0c45:6713 Microdia 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. XPS 15 9560
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-21-generic.efi.signed 
root=UUID=e0800d30-3eff-46ac-a6af-38e3bcf99b58 ro quiet 

[Kernel-packages] [Bug 1696102] Re: xfs/073 test fails with Metadata corruption detected on xfs file system (xfsprogs)

[ChristianEhrhardt]

I was asked to also recheck:
Working on artful for me as well:




[...]
root@cpaelzer-artful:/home/ubuntu/xfstests-dev# ./check tests/xfs/073
FSTYP -- xfs (non-debug)
PLATFORM  -- Linux/ppc64le cpaelzer-artful 4.11.0-10-generic
MKFS_OPTIONS  -- -f -bsize=4096 /dev/loop1
MOUNT_OPTIONS -- /dev/loop1 /mnt/scratch

xfs/073  4s
Ran: xfs/073
Passed all 1 tests

xfsprogs   4.9.0+nmu1ubuntu1ppc64el

---

Comparing Xenial:
./check tests/xfs/073
FSTYP -- xfs (non-debug)
PLATFORM  -- Linux/ppc64le cpaelzer-xenial 4.4.0-92-generic
MKFS_OPTIONS  -- -f -bsize=4096 /dev/loop1
MOUNT_OPTIONS -- /dev/loop1 /mnt/scratch

xfs/073  [failed, exit status 1] - output mismatch (see 
/home/ubuntu/xfstests-dev/results//xfs/073.out.bad)
--- tests/xfs/073.out   2017-08-31 08:53:15.888003364 +
+++ /home/ubuntu/xfstests-dev/results//xfs/073.out.bad  2017-08-31 
08:59:47.111628779 +
@@ -59,8 +59,7 @@
 comparing new image geometry to old
 unmounting and removing new image
 checking new image
-mounting new image on loopback
-comparing new image files to old
-comparing new image directories to old
-comparing new image geometry to old
...
(Run 'diff -u tests/xfs/073.out 
/home/ubuntu/xfstests-dev/results//xfs/073.out.bad'  to see the entire diff)
Ran: xfs/073
Failures: xfs/073
Failed 1 of 1 tests

xfsprogs4.3.0+nmu1ubuntu1

---

@bdmurray - I left you two KVM guests that are set up with that on Diamond and 
imported your keys there, ping me if you need help to access (but vorlon can 
help as well if I'm out of reach).
- cpaelzer-artful
- cpaelzer-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/1696102

Title:
  xfs/073 test fails with Metadata corruption detected on xfs file
  system (xfsprogs)

Status in The Ubuntu-power-systems project:
  Fix Released
Status in linux package in Ubuntu:
  Invalid
Status in xfsprogs package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Invalid
Status in xfsprogs source package in Xenial:
  Triaged
Status in linux source package in Zesty:
  Invalid
Status in xfsprogs source package in Zesty:
  Triaged

Bug description:
  Problem Description
  
  xfs/073 test fails with Metadata corruption detected on xfs file system. Test 
fails with _check_xfs_filesystem: filesystem on /mnt/test/84004.image2 is 
inconsistent.

  # diff -u tests/xfs/073.out /root/xfstests-dev/results//xfs/073.out.bad
  --- tests/xfs/073.out 2017-03-23 12:13:05.288877197 +0530
  +++ /root/xfstests-dev/results//xfs/073.out.bad   2017-03-27 
11:11:43.023059702 +0530
  @@ -59,8 +59,7 @@
   comparing new image geometry to old
   unmounting and removing new image
   checking new image
  -mounting new image on loopback
  -comparing new image files to old
  -comparing new image directories to old
  -comparing new image geometry to old
  -unmounting and removing new image
  +_check_xfs_filesystem: filesystem on /mnt/test/15413.image2 is inconsistent 
(c)
  +(see /root/xfstests-dev/results//xfs/073.full for details)
  +_check_xfs_filesystem: filesystem on /mnt/test/15413.image2 is inconsistent 
(r)
  +(see /root/xfstests-dev/results//xfs/073.full for details)

  Metadata corruption detected at xfs_agf block 0x1/0x200

  # uname -a
  Linux ltc-tuleta12 4.10.0-21-generic #23~16.04.1-Ubuntu SMP Tue May 2 
12:54:57 UTC 2017 ppc64le ppc64le ppc64le GNU/Linux

  Steps to reproduce:
  
  1. Create a loop device with xfs filesystem
  2. git clone git://git.kernel.org/pub/scm/fs/xfs/xfstests-dev.git; cd 
xfstests-dev
  3. make
  4. Create a local.conf for running with created loop device
  5.. Run xfstests-dev test  : ./check tests/xfs/073

  Full log is attached.

  == Comment: #2 - Harish Sriram  - 2017-05-31 01:22:11 ==
  (In reply to comment #1)
  > Hi Harish,
  > Can you share the steps used in creating the loop device with xfs filesystem
  > ?
  > 
  > Thank you.

  Create loop device:
  # mkdir /mnt/loop-device /mnt/test /mnt/scratch

  # for i in $(seq 0 1); do fallocate -o 0 -l 5GiB 
/mnt/loop-device/file-$i.img; done
  # for i in $(seq 0 1); do losetup /dev/loop$i /mnt/loop-device/file-$i.img; 
done

  Create File system:
  # for i in $(seq 0 1); do mkfs.ext4 -F /dev/loop$i; done

  # cat local.config
  export TEST_DEV=/dev/loop0
  export TEST_DIR=/mnt/test
  export SCRATCH_DEV=/dev/loop1
  export SCRATCH_MNT=/mnt/scratch

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1696102/+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 1655280] Comment bridged from LTC Bugzilla

[bugproxy]

--- Comment From hbath...@in.ibm.com 2017-08-31 04:54 EDT---
(In reply to comment #22)
> Hi, Hari.

Hello Cascardo,

>
> My understanding is that the kernel should handle that. Otherwise, whenever

Sadly, it can't as kexec-tools is the one that creates elf headers for 
/proc/vmcore.
So, with a change in available CPUs/memory, kdump kernel needs to be reloaded.
Probably, with a udev event that does a try-restart of kdump-tool service on
CPU/Memory hot add/remove operation.

> the user manually loads a different kdump kernel, a memory hotplug would
> cause the default kdump kernel to be loaded, not what the user has loaded.

Can't do much about it. If need be, a user has the option to workaround this
problem by adjusting the settings in /etc/default/kdump-tools file to load
a different kdump kernel..

Thanks
Hari

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

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

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

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

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

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

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

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

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1655280/+subscriptions

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

[Kernel-packages] [Bug 1714193] [NEW] Enable ppc64el build

[Colin Ian King]

Public bug reported:

Numatop now supports ppc64el functionality, however the packaging does
not enable this.

** Affects: linux (Ubuntu)
 Importance: High
 Assignee: Colin Ian King (colin-king)
 Status: In Progress

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

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

** Changed in: linux (Ubuntu)
 Assignee: (unassigned) => Colin Ian King (colin-king)

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

Title:
  Enable ppc64el build

Status in linux package in Ubuntu:
  In Progress

Bug description:
  Numatop now supports ppc64el functionality, however the packaging does
  not enable this.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1714193/+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 1714190] Re: ubuntu_sysdig_smoke_test stuck on Zesty s390x zKVM / zVM

[Po-Hsu Lin]

** Tags added: zesty

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

Title:
  ubuntu_sysdig_smoke_test stuck on Zesty s390x zKVM / zVM

Status in linux package in Ubuntu:
  In Progress

Bug description:
  From the test log, it looks like this test get stuck on s390x zVM and
  zKVM (kernel03, s2lp6g003) for a couple hours with zesty kernel.

  01:14:28 DEBUG| Running 
'/home/ubuntu/autotest/client/tests/ubuntu_sysdig_smoke_test/ubuntu_sysdig_smoke_test.sh'
  01:14:28 DEBUG| [stdout] == sysdig smoke test to trace dd, cat, read and 
writes ==
  01:14:28 DEBUG| [stdout] Try 1 of 10

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1714190/+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 1714190] Re: ubuntu_sysdig_smoke_test stuck on Zesty s390x zKVM / zVM

[Colin Ian King]

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

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

Title:
  ubuntu_sysdig_smoke_test stuck on Zesty s390x zKVM / zVM

Status in linux package in Ubuntu:
  In Progress

Bug description:
  From the test log, it looks like this test get stuck on s390x zVM and
  zKVM (kernel03, s2lp6g003) for a couple hours with zesty kernel.

  01:14:28 DEBUG| Running 
'/home/ubuntu/autotest/client/tests/ubuntu_sysdig_smoke_test/ubuntu_sysdig_smoke_test.sh'
  01:14:28 DEBUG| [stdout] == sysdig smoke test to trace dd, cat, read and 
writes ==
  01:14:28 DEBUG| [stdout] Try 1 of 10

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1714190/+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 1714190] Re: ubuntu_sysdig_smoke_test stuck on Zesty s390x zKVM / zVM

[Colin Ian King]

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

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

Title:
  ubuntu_sysdig_smoke_test stuck on Zesty s390x zKVM / zVM

Status in linux package in Ubuntu:
  In Progress

Bug description:
  From the test log, it looks like this test get stuck on s390x zVM and
  zKVM (kernel03, s2lp6g003) for a couple hours with zesty kernel.

  01:14:28 DEBUG| Running 
'/home/ubuntu/autotest/client/tests/ubuntu_sysdig_smoke_test/ubuntu_sysdig_smoke_test.sh'
  01:14:28 DEBUG| [stdout] == sysdig smoke test to trace dd, cat, read and 
writes ==
  01:14:28 DEBUG| [stdout] Try 1 of 10

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1714190/+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 1714190] [NEW] ubuntu_sysdig_smoke_test stuck on Zesty s390x zKVM / zVM

[Po-Hsu Lin]

Public bug reported:

>From the test log, it looks like this test get stuck on s390x zVM and
zKVM (kernel03, s2lp6g003) for a couple hours with zesty kernel.

01:14:28 DEBUG| Running 
'/home/ubuntu/autotest/client/tests/ubuntu_sysdig_smoke_test/ubuntu_sysdig_smoke_test.sh'
01:14:28 DEBUG| [stdout] == sysdig smoke test to trace dd, cat, read and writes 
==
01:14:28 DEBUG| [stdout] Try 1 of 10

** Affects: linux (Ubuntu)
 Importance: High
 Assignee: Colin Ian King (colin-king)
 Status: In Progress


** Tags: zesty

** Changed in: linux (Ubuntu)
 Assignee: (unassigned) => Colin Ian King (colin-king)

** Description changed:

  From the test log, it looks like this test get stuck on s390x zVM and
- zKVM (kernel03, s2lp6g003) with zesty kernel
+ zKVM (kernel03, s2lp6g003) for a couple hours with zesty kernel.
  
  01:14:28 DEBUG| Running 
'/home/ubuntu/autotest/client/tests/ubuntu_sysdig_smoke_test/ubuntu_sysdig_smoke_test.sh'
  01:14:28 DEBUG| [stdout] == sysdig smoke test to trace dd, cat, read and 
writes ==
  01:14:28 DEBUG| [stdout] Try 1 of 10

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

Title:
  ubuntu_sysdig_smoke_test stuck on Zesty s390x zKVM / zVM

Status in linux package in Ubuntu:
  In Progress

Bug description:
  From the test log, it looks like this test get stuck on s390x zVM and
  zKVM (kernel03, s2lp6g003) for a couple hours with zesty kernel.

  01:14:28 DEBUG| Running 
'/home/ubuntu/autotest/client/tests/ubuntu_sysdig_smoke_test/ubuntu_sysdig_smoke_test.sh'
  01:14:28 DEBUG| [stdout] == sysdig smoke test to trace dd, cat, read and 
writes ==
  01:14:28 DEBUG| [stdout] Try 1 of 10

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1714190/+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 1690502] Re: ACPI Error: [\_SB_.PCI0.XHC_.RHUB.HS11] Namespace lookup failure, AE_NOT_FOUND (20160930/dswload-210)

[dino99]

Artful 4.12 kernel still display these errors:

kernel: ACPI Error: [\_SB_.PCI0.XHC_.RHUB.HS11] Namespace lookup failure, 
AE_NOT_FOUND (20170303/dswload-210)
kernel: ACPI Exception: AE_NOT_FOUND, During name lookup/catalog 
(20170303/psobject-241)
kernel: ACPI Exception: AE_NOT_FOUND, (SSDT:xh_rvp08) while loading table 
(20170303/tbxfload-228)
kernel: ACPI Error: 1 table load failures, 5 successful (20170303/tbxfload-246)

This is not a distro issue, but an upstream one:
https://bugzilla.kernel.org/show_bug.cgi?id=193531

Looks like acpica team have released an upgrade:
"support for forward references from package elements was released in version 
20170728"
https://github.com/acpica/acpica/pull/189/

** Description changed:

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

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

Title:
  ACPI Error: [\_SB_.PCI0.XHC_.RHUB.HS11] Namespace lookup failure,
  AE_NOT_FOUND (20160930/dswload-210)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  This is a long standing issue seen on ubuntu

  ACPI Error: [\_SB_.PCI0.XHC_.RHUB.HS11] Namespace lookup failure, 
AE_NOT_FOUND (20160930/dswload-210)
  kernel: ACPI Exception: AE_NOT_FOUND, During name lookup/catalog 
(20160930/psobject-227)
  kernel: ACPI Exception: AE_NOT_FOUND, (SSDT:xh_rvp08) while loading table 
(20160930/tbxfload-228)
  kernel: ACPI Error: 1 table load failures, 5 successful 
(20160930/tbxfload-246)

  As per https://bugzilla.kernel.org/show_bug.cgi?id=117671, that should
  be fixed with recent kernels.

  comment from #4 of the above report:
  ***
  The problem happens when the ACPICA interpreter is trying to load the SSDT.

  So this is the known module level code support issue.
  This module level support could be fixed by just moving module level 
execution to per-table basis, thus this should have already been fixed by an 
upstream module level support improvement.
  
  
https://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm.git/commit/?h=linux-next=3d4b7ae9

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

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

[Kernel-packages] [Bug 1705748] Re: Samsung SSD 960 EVO 500GB refused to change power state

[Kai-Heng Feng]

Originally can't read PCI status:
Aug 15 14:14:02 phs08 kernel: [ 2477.191603] nvme :01:00.0: controller is 
down; will reset: CSTS=0x, PCI_STATUS=0x

Now only controller is dead:
Aug 30 09:35:19 phs08 kernel: [71904.271956] nvme nvme0: controller is down; 
will reset: CSTS=0x, PCI_STATUS=0x10

So I guess other than NVME_QUIRK_NO_DEEPEST_PS, quirk
NVME_QUIRK_DELAY_BEFORE_CHK_RDY is also needed.

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

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

Status in linux package in Ubuntu:
  In Progress

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

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

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

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

  System, drive details below:

  M2 nvme drive: Samsung SSD 960 EVO 500GB

  Ubuntu 4.10.0-26.30~16.04.1-generic 4.10.17

  M/B Asus Prime B350m-A
  Ryzen 1600 cpu

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

  
  nvme list

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

  sudo nvme id-ctrl /dev/nvme0

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