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

[bugproxy]

--- Comment From sikri...@in.ibm.com 2017-11-21 02:33 EDT---
Hi Daniel,

Yes. I meant TCP Segmentation Offload when I said large-send offload.

Your understanding of the current ibmveth code is right.

AIX Path MTU Discovery is enabled by default and so though the very
first packet (larger payload) can leave the LPAR with higher MSS, AIX
will discover that the path MTU size is lower than the MSS negotiated.
This leads to AIX TCP recovering (based on path MTU values) and sending
packets of right MTU size for further packets.

But if user disables Path MTU and configures an MTU higher than what
physical NIC can support, then this will lead to packet drops (and AIX
stack cannot rediscover MTU without path MTU). So, second scenario you
mentioned in your note will lead to communication issues.

Also by default, AIX MTU settings are optimal ones i.e 1500 bytes (even
when TSO is enabled). This helps in AIX LPAR sending larger payloads
with MSS value of 1500. If an user knows that the physical NIC in VIOS
or Linux IO server has Jumbo frames enabled, MTU can be set to 9000
(here again if TSO is enabled, larger payloads will go with MSS of
9000).  So, the optimal values are the default values (1500/9000).

Regards,
Siva K.

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

Title:
  Ubuntu 16.04.02: ibmveth: Support to enable LSO/CSO for Trunk VEA

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

Bug description:
  
  == SRU Justification ==
  Commit 66aa0678ef is request to fix four issues with the ibmveth driver.
  The issues are as follows:
  - Issue 1: ibmveth doesn't support largesend and checksum offload features 
when configured as "Trunk".
  - Issue 2: SYN packet drops seen at destination VM. When the packet
  originates, it has CHECKSUM_PARTIAL flag set and as it gets delivered to IO
  server's inbound Trunk ibmveth, on validating "checksum good" bits in ibmveth
  receive routine, SKB's ip_summed field is set with CHECKSUM_UNNECESSARY flag.
  - Issue 3: First packet of a TCP connection will be dropped, if there is
  no OVS flow cached in datapath.
  - Issue 4: ibmveth driver doesn't have support for SKB's with frag_list.

  The details for the fixes to these issues are described in the commits
  git log.



  == Comment: #0 - BRYANT G. LY  - 2017-05-22 08:40:16 ==
  ---Problem Description---

   - Issue 1: ibmveth doesn't support largesend and checksum offload features
     when configured as "Trunk". Driver has explicit checks to prevent
     enabling these offloads.

   - Issue 2: SYN packet drops seen at destination VM. When the packet
     originates, it has CHECKSUM_PARTIAL flag set and as it gets delivered to
     IO server's inbound Trunk ibmveth, on validating "checksum good" bits
     in ibmveth receive routine, SKB's ip_summed field is set with
     CHECKSUM_UNNECESSARY flag. This packet is then bridged by OVS (or Linux
     Bridge) and delivered to outbound Trunk ibmveth. At this point the
     outbound ibmveth transmit routine will not set "no checksum" and
     "checksum good" bits in transmit buffer descriptor, as it does so only
     when the ip_summed field is CHECKSUM_PARTIAL. When this packet gets
     delivered to destination VM, TCP layer receives the packet with checksum
     value of 0 and with no checksum related flags in ip_summed field. This
     leads to packet drops. So, TCP connections never goes through fine.

   - Issue 3: First packet of a TCP connection will be dropped, if there is
     no OVS flow cached in datapath. OVS while trying to identify the flow,
     computes the checksum. The computed checksum will be invalid at the
     receiving end, as ibmveth transmit routine zeroes out the pseudo
     checksum value in the packet. This leads to packet drop.

   - Issue 4: ibmveth driver doesn't have support for SKB's with frag_list.
     When Physical NIC has GRO enabled and when OVS bridges these packets,
     OVS vport send code will end up calling dev_queue_xmit, which in turn
     calls validate_xmit_skb.
     In validate_xmit_skb routine, the larger packets will get segmented into
     MSS sized segments, if SKB has a frag_list and if the driver to which
     they are delivered to doesn't support NETIF_F_FRAGLIST feature.

  Contact Information = Bryant G. Ly/b...@us.ibm.com

  ---uname output---
  4.8.0-51.54

  Machine Type = p8

  ---Debugger---
  A debugger is not configured

  ---Steps to Reproduce---
   Increases performance greatly

  The patch has been accepted upstream:
  https://patchwork.ozlabs.org/patch/764533/

To manage notifications about this bug go to:

[Kernel-packages] [Bug 1733306] Re: FS-Cache: Assertion failed

[DanielT]

Hi Joseph,

Thanks for your advice.
I've installed the kernel but the machine is currently in heavy usage so I 
might only have a chance to reboot to about a week later. Will update once I 
try it.

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

Title:
  FS-Cache: Assertion failed

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I'm encountering many random kernel panic after enabling fsc with NFS.
  Then I see a number of following err msgs right before it crashed.

  Nov 20 12:04:26 g2 kernel: [170689.549374] FS-Cache: 
  Nov 20 12:04:26 g2 kernel: [170689.549381] FS-Cache: Assertion failed
  Nov 20 12:04:26 g2 kernel: [170689.549384] FS-Cache: 6 == 5 is false
  Nov 20 12:04:26 g2 kernel: [170689.549439] [ cut here 
]
  Nov 20 12:04:26 g2 kernel: [170689.549490] kernel BUG at 
/build/linux-3phnTq/linux-4.4.0/fs/fscache/operation.c:494!
  Nov 20 12:04:26 g2 kernel: [170689.549557] invalid opcode:  [#1] SMP 
  Nov 20 12:04:26 g2 kernel: [170689.549598] Modules linked in: veth xt_nat 
xt_tcpudp ipt_MASQUERADE nf_nat_masquerade_ipv4 nf_conntrack_netlink nfnetlink 
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 bridge stp llc aufs cachefiles ipmi_devintf rpcsec_gss_krb5 
auth_rpcgss nfsv4 nfs lockd grace fscache snd_hda_codec_hdmi intel_rapl 
x86_pkg_temp_thermal intel_powerclamp kvm_intel kvm ipmi_ssif irqbypass 
serio_raw joydev input_leds snd_hda_intel snd_hda_codec snd_hda_core snd_hwdep 
snd_pcm nvidia_uvm(POE) sb_edac snd_seq_midi snd_seq_midi_event edac_core 
snd_rawmidi snd_seq snd_seq_device snd_timer snd soundcore mei_me lpc_ich mei 
shpchp wmi ipmi_si 8250_fintek ipmi_msghandler acpi_pad acpi_power_meter 
mac_hid sunrpc ib_iser rdma_cm iw_cm ib_cm ib_sa ib_mad ib_core ib_addr 
iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi nct6775 hwmon_vid coretemp 
bonding parport_pc ppdev lp parport autofs4 xfs btrfs raid10 raid456 
async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq 
libcrc32c raid1 raid0 multipath linear nvidia_drm(POE) nvidia_modeset(POE) 
hid_generic crct10dif_pclmul ast crc32_pclmul ghash_clmulni_intel aesni_intel 
aes_x86_64 lrw gf128mul nvidia(POE) glue_helper ttm ablk_helper igb cryptd 
drm_kms_helper psmouse syscopyarea dca sysfillrect ptp sysimgblt fb_sys_fops 
pps_core ahci i2c_algo_bit drm libahci fjes usbhid hid
  Nov 20 12:04:26 g2 kernel: [170689.550993] CPU: 22 PID: 6373 Comm: 
kworker/u98:1 Tainted: P   OE   4.4.0-98-generic #121-Ubuntu
  Nov 20 12:04:26 g2 kernel: [170689.551071] Hardware name: ASUSTeK COMPUTER 
INC. ESC8000 G3 Series/Z10PG-D24 Series, BIOS 3203 05/05/2016
  Nov 20 12:04:26 g2 kernel: [170689.551160] Workqueue: fscache_operation 
fscache_op_work_func [fscache]
  Nov 20 12:04:26 g2 kernel: [170689.551219] task: 882027887000 ti: 
881429ea4000 task.ti: 881429ea4000
  Nov 20 12:04:26 g2 kernel: [170689.551283] RIP: 0010:[]  
[] fscache_put_operation+0x1d6/0x210 [fscache]
  Nov 20 12:04:26 g2 kernel: [170689.551374] RSP: 0018:881429ea7de0  
EFLAGS: 00010282
  Nov 20 12:04:26 g2 kernel: [170689.551421] RAX: 0019 RBX: 
882037224300 RCX: 0006
  Nov 20 12:04:26 g2 kernel: [170689.551490] RDX:  RSI: 
0246 RDI: 88203f28dd50
  Nov 20 12:04:26 g2 kernel: [170689.551551] RBP: 881429ea7df8 R08: 
000a R09: 09c0
  Nov 20 12:04:26 g2 kernel: [170689.551611] R10: 88120db1b300 R11: 
09c0 R12: 882038bf8000
  Nov 20 12:04:26 g2 kernel: [170689.551672] R13: 88202ff08800 R14: 
0c40 R15: 882037224300
  Nov 20 12:04:26 g2 kernel: [170689.551733] FS:  () 
GS:88203f28() knlGS:
  Nov 20 12:04:26 g2 kernel: [170689.551801] CS:  0010 DS:  ES:  CR0: 
80050033
  Nov 20 12:04:26 g2 kernel: [170689.551850] CR2: 7f66b2887500 CR3: 
01e0a000 CR4: 003406e0
  Nov 20 12:04:26 g2 kernel: [170689.551912] DR0:  DR1: 
 DR2: 
  Nov 20 12:04:26 g2 kernel: [170689.551972] DR3:  DR6: 
fffe0ff0 DR7: 0400
  Nov 20 12:04:26 g2 kernel: [170689.552030] Stack:
  Nov 20 12:04:26 g2 kernel: [170689.552051]  882037224300 882038bf8000 
88202ff08800 881429ea7e10
  Nov 20 12:04:26 g2 kernel: [170689.552124]  c065e1ca 88203439e780 
881429ea7e50 8109a635
  Nov 20 12:04:26 g2 kernel: [170689.552196]   88203439e7b0 
882038bf8000 0088
  Nov 20 12:04:26 g2 kernel: [170689.552267] Call Trace:
  Nov 20 12:04:26 g2 kernel: [170689.552299]  [] 
fscache_op_work_func+0x2a/0x50 [fscache]
  Nov 20 12:04:26 g2 kernel: [170689.552363]  

[Kernel-packages] [Bug 1729389] Re: Bluetooth mouse and keyboard connects, works for a few seconds, then doesn't react

[Kai-Heng Feng]

Please find the last working and first non-working kernel from
http://kernel.ubuntu.com/~kernel-ppa/mainline/

You only need to test mainline release, you can ignore version number
that has two points.

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

Title:
  Bluetooth mouse and keyboard connects, works for a few seconds, then
  doesn't react

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After upgrading from Ubuntu Gnome 17.04 to Ubuntu 17.10, bluetooth
  mouse and keyboard connects, works for a few seconds, then doesn't
  react.

  Bluetooth package version: 5.46-0ubuntu3 500

  Please tell me which log-files to upload.

  Thanks
  --- 
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 17.10
  InstallationDate: Installed on 2016-06-11 (509 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Release amd64 
(20160421)
  InterestingModules: rfcomm bnep btusb bluetooth
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 006: ID 04b4:5210 Cypress Semiconductor Corp. 
   Bus 001 Device 005: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 002: ID 13d3:5664 IMC Networks 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 80MK
  Package: bluez 5.46-0ubuntu3
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=da_DK.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic 
root=UUID=ed8fbe48-3db5-4a77-ab34-f35fd1a481cc ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Tags:  artful wayland-session
  Uname: Linux 4.13.0-16-generic x86_64
  UpgradeStatus: Upgraded to artful on 2017-10-23 (11 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 03/01/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: C6CN37WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: VIUU4
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo YOGA 900-13ISK
  dmi.modalias: 
dmi:bvnLENOVO:bvrC6CN37WW:bd03/01/2016:svnLENOVO:pn80MK:pvrLenovoYOGA900-13ISK:rvnLENOVO:rnVIUU4:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoYOGA900-13ISK:
  dmi.product.family: IDEAPAD
  dmi.product.name: 80MK
  dmi.product.version: Lenovo YOGA 900-13ISK
  dmi.sys.vendor: LENOVO
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: A4:34:D9:9A:CD:FF  ACL MTU: 1021:4  SCO MTU: 96:6
UP RUNNING PSCAN ISCAN INQUIRY 
RX bytes:71005 acl:1028 sco:0 events:2920 errors:0
TX bytes:601922 acl:36 sco:0 commands:2468 errors:0

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

-- 
Mailing list: https://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 1728523] Re: QCA6174A XR cannot find any WiFi AP

[Po-Hsu Lin]

Patch applied.

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

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

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

Title:
  QCA6174A XR cannot find any WiFi AP

Status in HWE Next:
  Fix Committed
Status in linux-firmware package in Ubuntu:
  Fix Committed

Bug description:
  QCA6174A XR requires an update firmware

  [   16.158772] ath10k_pci :02:00.0: failed to enable dynamic BW: -11
  [   22.162575] ath10k_pci :02:00.0: could not suspend target (-11)
  [   27.533002] ath10k_pci :02:00.0: failed to enable dynamic BW: -11
  [   33.535958] ath10k_pci :02:00.0: could not suspend target (-11)
  [   38.890790] ath10k_pci :02:00.0: failed to enable dynamic BW: -11
  [   44.893968] ath10k_pci :02:00.0: could not suspend target (-11)
  [   46.358194] i2c_designware i2c_designware.0: controller timed out
  [   47.358231] i2c_designware i2c_designware.0: controller timed out
  [   48.358506] i2c_designware i2c_designware.0: controller timed out
  [   49.566240] i2c_designware i2c_designware.2: controller timed out
  [   50.566862] i2c_designware i2c_designware.2: controller timed out
  [   51.566307] i2c_designware i2c_designware.2: controller timed out
  [   52.670330] i2c_designware i2c_designware.3: controller timed out
  [   53.670775] i2c_designware i2c_designware.3: controller timed out
  [   54.670427] i2c_designware i2c_designware.3: controller timed out
  [   60.326619] ath10k_pci :02:00.0: failed to enable dynamic BW: -11
  [   66.327117] ath10k_pci :02:00.0: could not suspend target (-11)
  [   71.678943] ath10k_pci :02:00.0: failed to enable dynamic BW: -11
  [   77.679084] ath10k_pci :02:00.0: could not suspend target (-11)

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1728523/+subscriptions

-- 
Mailing list: https://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 1727331] Comment bridged from LTC Bugzilla

[bugproxy]

--- Comment From mcfad...@us.ibm.com 2017-11-20 15:08 EDT---
So is the official fix avail yet?  Any outlook?

--- Comment From sthou...@in.ibm.com 2017-11-21 01:07 EDT---
Any update on the official fix ?

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

Title:
  NMI watchdog: BUG: soft lockup on Guest upon boot (KVM)

Status in The Ubuntu-power-systems project:
  Fix Committed
Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Xenial:
  Fix Committed

Bug description:
  == SRU Justification ==
  Xenial does not include the patch:
  "KVM: PPC: Book3S: Treat VTB as a per-subcore register, not per-thread",
  which is commit 88b02cf97bb7 in the upstream Linux kernel repository. The
  symptom of not having this patch is that guests running with threads > 1
  (that is, in SMT2, SMT4 or SMT8 mode) can give spurious soft-lockup messages 
  when they are not in fact locked up, if the guest kernel uses the VTB
  (virtual timebase) register in its softlockup detector code.

  IBM provided this backport of commit 88b02cf97bb7.

  == Fix ==
  commit 88b02cf97bb7e742db3e31671d54177e3e19fd89
  Author: Paul Mackerras 
  Date:   Thu Sep 15 13:42:52 2016 +1000

  KVM: PPC: Book3S: Treat VTB as a per-subcore register, not per-
  thread

  == Regression Potential ==
  This patch is specific to powerpc.  It was provided by and tested by IBM.



  Environment:
  Host OS: Ubuntu 16.04 (4.4.0-97-generic)
  Guest OS: Ubuntu 16.04

  Host is running NovaLink and GPFS.  Guest gets filesystem from gpfs
  cluster.

  Issue:

  While booting the guest OS went into recovery.  dmesg shows CPU soft
  lockup.  This issue is easily recreatable when multiple VMs (about 10)
  are being started simultaneously.

  
...

   - Paul Mackerras  - 2017-10-24 00:42:25 ==

  Looking at kernel sources:

  The Ubuntu host kernel (4.4.0-97) does not include the patch "KVM:
  PPC: Book3S: Treat VTB as a per-subcore register, not per-thread",
  which is commit 88b02cf97bb7 in the upstream Linux kernel repository.
  The symptom of not having this patch is that guests running with
  threads > 1 (that is, in SMT2, SMT4 or SMT8 mode) can give spurious
  soft-lockup messages when they are not in fact locked up, if the guest
  kernel uses the VTB (virtual timebase) register in its softlockup
  detector code.

  This is a backport of commit 88b02cf97bb7 from the upstream Linux
  kernel repository to the Ubuntu 4.4 kernel. It is the fix for the
  problem of seeing spurious soft lockup messages in guests running in
  an SMT mode greater than 1.

  These tests were run on a system with 20 cores.  Each VM had 1 core and 4 
threads (SMT=4).
  It is working very well with this patch

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

-- 
Mailing list: https://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 1729337] Re: CIFS errors on 4.4.0-98, but not on 4.4.0-97 with same config

[FedeX]

Ok this is very weird, it worked fine after the first reboot, but then I
booted once again with 3.13.0-135-generic #184-Ubuntu just to confirm
that the same mount options where failing (which they did). Then I
rebooted again to 3.13.0-134-generic #183~lp1729337Commit5165d87e224 and
the mount it's failing just like with 3.13.0-135-generic #184-Ubuntu

uname -a
Linux ruby2-staging03 3.13.0-134-generic #183~lp1729337Commit5165d87e224 SMP 
Thu Nov 16 21:22:11 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux

$ sudo mount -o remount -a
mount error(22): Invalid argument
Refer to the mount.cifs(8) manual page (e.g. man mount.cifs)

Not sure what to think of this now

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

Title:
  CIFS errors on 4.4.0-98, but not on 4.4.0-97 with same config

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

Bug description:
  == SRU Justification ==
  The bug reporter stated they have a cluster of servers that applied Xenial 
updates
  and then were unable to mount CIFS shares after upgrading to 4.4.0-98. The
  same machines on 4.4.0-97 do not hit the regression.  It was found that the
  regression is fixed by mainline commit:
  4587eee04e2a ("SMB3: Validate negotiate request must always be signed").

  This fix is required in all Ubuntu supported releases.  Commit 4587eee04e2a
  landed in mailine as of 4.14-rc7.  It  was also cc'd to upstream stable,
  but it has not landed in any stable releases yet, which is the reason for
  this SRU.


  == Fix ==
  commit 4587eee04e2ac7ac3ac9fa2bc164fb6e548f99cd
  Author: Steve French 
  Date:   Wed Oct 25 15:58:31 2017 -0500
  SMB3: Validate negotiate request must always be signed

  == Regression Potential ==
  This patch is to fix a regression.  It was also cc'd to upstream stable, so
  it received addition review upstream.

  We have a cluster of servers that applied a security update overnight
  and were unable to mount CIFS shares after upgrading to 4.4.0-98.  The
  same machines on 4.4.0-97 were fine the night before, and are fine
  after downgrading.  The only error message CIFS would report, even on
  verbose, was:

  [  257.089876] CIFS VFS: validate protocol negotiate failed: -11
  [  257.089964] CIFS VFS: cifs_mount failed w/return code = -5

  Rebooting did not help.  Nor did attempting to mount the share
  manually using mount -t cifs.

  Here's the offending line from our /etc/fstab (with hostnames
  sanitized):

  //server/share /mnt/share cifs 
rw,user,credentials=/etc/samba/credentials.share,uid=33,gid=33,file_mode=0770,dir_mode=0770
  ,exec,soft,noserverino,vers=3.0 0 0

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-98-generic 4.4.0-98.121
  ProcVersionSignature: Ubuntu 4.4.0-98.121-generic 4.4.90
  Uname: Linux 4.4.0-98-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Nov  1 07:56 seq
   crw-rw 1 root audio 116, 33 Nov  1 07:56 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: Wed Nov  1 08:49:47 2017
  HibernationDevice: RESUME=/dev/mapper/ubuntu--template--vg-swap_1
  InstallationDate: Installed on 2016-12-16 (319 days ago)
  InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  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:

  ProcFB: 0 svgadrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-98-generic 
root=/dev/mapper/ubuntu--template--vg-root ro
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-98-generic N/A
   linux-backports-modules-4.4.0-98-generic  N/A
   linux-firmware1.157.13
  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: 

Re: [Kernel-packages] [Bug 1724639] Re: Bug in Kernel 4.13 : Intel Mobile Graphics 945 shows 80 % black screen

[Kai-Heng Feng]

The next one:

http://people.canonical.com/~khfeng/lp1724639-4/


> On 20 Nov 2017, at 8:25 PM, Eduard <1724...@bugs.launchpad.net> wrote:
> 
> Hey @Kaihengfeng,
> 
> I tried your kernel from Post #61,
> 
> http://people.canonical.com/~khfeng/lp1724639-3/
> 
> 
> The graphic error is present in this kernel !
> 
> -- 
> You received this bug notification because you are subscribed to linux
> in Ubuntu.
> https://bugs.launchpad.net/bugs/1724639
> 
> Title:
>  Bug in Kernel 4.13 : Intel Mobile Graphics 945 shows 80 % black screen
> 
> Status in linux package in Ubuntu:
>  Confirmed
> Status in openSUSE:
>  Unknown
> 
> Bug description:
>  Installed O.S. on Samsung NC10. Display worked O.K. in text mode so
>  the install went smoothly. When the system is rebooted, however,
>  switching to graphics mode results in the below described screen
>  corruption:-
> 
>  Left  Hand Side 80% of screen black with a blue of white pixels and some 
> blue lines at the top
>  Right Hand Side 20% of screen OK.
> 
>  ProblemType: Bug
>  DistroRelease: Ubuntu 17.10
>  Package: linux-image-4.13.0-16-generic 4.13.0-16.19
>  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
>  Uname: Linux 4.13.0-16-generic i686
>  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
> k4.13.0-16-generic.
>  AplayDevices:
>    List of PLAYBACK Hardware Devices 
>   card 0: Intel [HDA Intel], device 0: ALC272 Analog [ALC272 Analog]
> Subdevices: 1/1
> Subdevice #0: subdevice #0
>  ApportVersion: 2.20.7-0ubuntu3
>  Architecture: i386
>  ArecordDevices:
>    List of CAPTURE Hardware Devices 
>   card 0: Intel [HDA Intel], device 0: ALC272 Analog [ALC272 Analog]
> Subdevices: 1/1
> Subdevice #0: subdevice #0
>  AudioDevicesInUse:
>   USERPID ACCESS COMMAND
>   /dev/snd/controlC0:  ian 918 F pulseaudio
>  Card0.Amixer.info:
>   Card hw:0 'Intel'/'HDA Intel at 0xf034 irq 25'
> Mixer name: 'Realtek ALC272'
> Components: 'HDA:10ec0272,144dca00,0011'
> Controls  : 25
> Simple ctrls  : 12
>  CurrentDesktop: LXDE
>  Date: Wed Oct 18 18:30:15 2017
>  HibernationDevice: RESUME=UUID=c54e130e-6625-4d96-ba75-4efaa6a9da75
>  InstallationDate: Installed on 2017-10-18 (0 days ago)
>  InstallationMedia: Lubuntu 17.10 "Artful Aardvark" - Release i386 
> (20171017.1)
>  MachineType: SAMSUNG ELECTRONICS CO., LTD. NC10
>  ProcFB: 0 inteldrmfb
>  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic 
> root=UUID=d74a58ab-e96e-4531-a2eb-13f0d1610658 ro quiet splash vt.handoff=7
>  RelatedPackageVersions:
>   linux-restricted-modules-4.13.0-16-generic N/A
>   linux-backports-modules-4.13.0-16-generic  N/A
>   linux-firmware 1.169
>  SourcePackage: linux
>  UpgradeStatus: No upgrade log present (probably fresh install)
>  dmi.bios.date: 04/14/2009
>  dmi.bios.vendor: Phoenix Technologies Ltd.
>  dmi.bios.version: 07CA.M002.20090414.KTW
>  dmi.board.name: NC10
>  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
>  dmi.board.version: Not Applicable
>  dmi.chassis.asset.tag: No Asset Tag
>  dmi.chassis.type: 10
>  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
>  dmi.chassis.version: N/A
>  dmi.modalias: 
> dmi:bvnPhoenixTechnologiesLtd.:bvr07CA.M002.20090414.KTW:bd04/14/2009:svnSAMSUNGELECTRONICSCO.,LTD.:pnNC10:pvrNotApplicable:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNC10:rvrNotApplicable:cvnSAMSUNGELECTRONICSCO.,LTD.:ct10:cvrN/A:
>  dmi.product.name: NC10
>  dmi.product.version: Not Applicable
>  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.
> 
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1724639/+subscriptions

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

Title:
  Bug in Kernel 4.13 : Intel Mobile Graphics 945 shows 80 % black screen

Status in linux package in Ubuntu:
  Confirmed
Status in openSUSE:
  Unknown

Bug description:
  Installed O.S. on Samsung NC10. Display worked O.K. in text mode so
  the install went smoothly. When the system is rebooted, however,
  switching to graphics mode results in the below described screen
  corruption:-

  Left  Hand Side 80% of screen black with a blue of white pixels and some blue 
lines at the top
  Right Hand Side 20% of screen OK.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-16-generic 4.13.0-16.19
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic i686
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k4.13.0-16-generic.
  AplayDevices:
    List of PLAYBACK Hardware Devices 
   card 0: Intel [HDA Intel], device 0: ALC272 Analog [ALC272 Analog]
 Subdevices: 1/1
 Subdevice #0: subdevice #0
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: i386
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   

[Kernel-packages] [Bug 1729337] Re: CIFS errors on 4.4.0-98, but not on 4.4.0-97 with same config

[FedeX]

Hi Joseph,

It seems to be working fine with this kernel, is there any particular
info you would like me to provide?

Cheers
FedeX

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

Title:
  CIFS errors on 4.4.0-98, but not on 4.4.0-97 with same config

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

Bug description:
  == SRU Justification ==
  The bug reporter stated they have a cluster of servers that applied Xenial 
updates
  and then were unable to mount CIFS shares after upgrading to 4.4.0-98. The
  same machines on 4.4.0-97 do not hit the regression.  It was found that the
  regression is fixed by mainline commit:
  4587eee04e2a ("SMB3: Validate negotiate request must always be signed").

  This fix is required in all Ubuntu supported releases.  Commit 4587eee04e2a
  landed in mailine as of 4.14-rc7.  It  was also cc'd to upstream stable,
  but it has not landed in any stable releases yet, which is the reason for
  this SRU.


  == Fix ==
  commit 4587eee04e2ac7ac3ac9fa2bc164fb6e548f99cd
  Author: Steve French 
  Date:   Wed Oct 25 15:58:31 2017 -0500
  SMB3: Validate negotiate request must always be signed

  == Regression Potential ==
  This patch is to fix a regression.  It was also cc'd to upstream stable, so
  it received addition review upstream.

  We have a cluster of servers that applied a security update overnight
  and were unable to mount CIFS shares after upgrading to 4.4.0-98.  The
  same machines on 4.4.0-97 were fine the night before, and are fine
  after downgrading.  The only error message CIFS would report, even on
  verbose, was:

  [  257.089876] CIFS VFS: validate protocol negotiate failed: -11
  [  257.089964] CIFS VFS: cifs_mount failed w/return code = -5

  Rebooting did not help.  Nor did attempting to mount the share
  manually using mount -t cifs.

  Here's the offending line from our /etc/fstab (with hostnames
  sanitized):

  //server/share /mnt/share cifs 
rw,user,credentials=/etc/samba/credentials.share,uid=33,gid=33,file_mode=0770,dir_mode=0770
  ,exec,soft,noserverino,vers=3.0 0 0

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-98-generic 4.4.0-98.121
  ProcVersionSignature: Ubuntu 4.4.0-98.121-generic 4.4.90
  Uname: Linux 4.4.0-98-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Nov  1 07:56 seq
   crw-rw 1 root audio 116, 33 Nov  1 07:56 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: Wed Nov  1 08:49:47 2017
  HibernationDevice: RESUME=/dev/mapper/ubuntu--template--vg-swap_1
  InstallationDate: Installed on 2016-12-16 (319 days ago)
  InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  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:

  ProcFB: 0 svgadrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-98-generic 
root=/dev/mapper/ubuntu--template--vg-root ro
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-98-generic N/A
   linux-backports-modules-4.4.0-98-generic  N/A
   linux-firmware1.157.13
  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/1729337/+subscriptions

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

Re: [Kernel-packages] [Bug 1732686] Re: Asus Fx553VD - Keyboard LED backlight controls are not working # kernel-bug-reported-upstream

[Kai-Heng Feng]

> On 21 Nov 2017, at 2:47 AM, R.Erol <1732...@bugs.launchpad.net> wrote:
> 
> Kai , thank you so much!
> 
> That one works nicely , i can adjust the brightness of keyboard and turn
> on and off my keyboard light.
> 
> Thanks again.
> 
> One last question though ; what can i do for ACPI errors?

Unless it breaks your system, otherwise I think it’s safe to let them
stay where they were.

> 
> -- 
> You received this bug notification because you are subscribed to linux
> in Ubuntu.
> https://bugs.launchpad.net/bugs/1732686
> 
> Title:
>  Asus Fx553VD - Keyboard LED backlight controls are not working #
>  kernel-bug-reported-upstream
> 
> Status in linux package in Ubuntu:
>  Triaged
> 
> Bug description:
>  Hi , i'm using this laptop with it's latest bios (V303 -
>  https://www.asus.com/Laptops/ASUS-FX553VD/HelpDesk_BIOS/ )
> 
>  Kernel : 4.14.0-041400-generic x86_64
> 
>  I can't control keyboard LED backlight level with it's dedicated FN
>  keys or anything else. FN keys are recognized by Linux Mint 18.2 and
>  Ubuntu 16.04 but pressing them have no effect.
> 
>  Kernels from 4.10 to 4.14 are the same on that regard.
> 
>  And also i have these errors on "inxi -F && dmesg | grep -i error"
> 
>  [0.031175] ACPI Error: [PRT0] Namespace lookup failure, 
> AE_ALREADY_EXISTS (20170728/dswload-378)
>  [0.040665] ACPI Error: 1 table load failures, 10 successful 
> (20170728/tbxfload-246)
>  [0.506425] acpi PNP0A08:00: _OSC failed (AE_ERROR); disabling ASPM
>  [1.694527] RAS: Correctable Errors collector initialized.
>  [9.833145] EXT4-fs (sda2): re-mounted. Opts: errors=remount-ro
> 
>  I'm not a developer but only a user. So if i opened that issue to the
>  wrong place can you point me the correct place to open it?
> 
>  Thanks.
>  --- 
>  ApportVersion: 2.20.1-0ubuntu2.12
>  Architecture: amd64
>  CurrentDesktop: X-Cinnamon
>  DistroRelease: Linux 18.2
>  InstallationDate: Installed on 2017-10-22 (24 days ago)
>  InstallationMedia: Linux Mint 18.2 "Sonya" - Release amd64 20170628
>  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
>  Package: linux (not installed)
>  ProcEnviron:
>   TERM=xterm-256color
>   PATH=(custom, no user)
>   XDG_RUNTIME_DIR=
>   LANG=tr_TR.UTF-8
>   SHELL=/bin/bash
>  Tags:  sonya
>  Uname: Linux 4.14.0-041400-generic x86_64
>  UnreportableReason: The running kernel is not an Ubuntu kernel
>  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/linux/+bug/1732686/+subscriptions

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

Title:
  Asus Fx553VD - Keyboard LED backlight controls are not working #
  kernel-bug-reported-upstream

Status in linux package in Ubuntu:
  Triaged

Bug description:
  Hi , i'm using this laptop with it's latest bios (V303 -
  https://www.asus.com/Laptops/ASUS-FX553VD/HelpDesk_BIOS/ )

  Kernel : 4.14.0-041400-generic x86_64

  I can't control keyboard LED backlight level with it's dedicated FN
  keys or anything else. FN keys are recognized by Linux Mint 18.2 and
  Ubuntu 16.04 but pressing them have no effect.

  Kernels from 4.10 to 4.14 are the same on that regard.

  And also i have these errors on "inxi -F && dmesg | grep -i error"

  [0.031175] ACPI Error: [PRT0] Namespace lookup failure, AE_ALREADY_EXISTS 
(20170728/dswload-378)
  [0.040665] ACPI Error: 1 table load failures, 10 successful 
(20170728/tbxfload-246)
  [0.506425] acpi PNP0A08:00: _OSC failed (AE_ERROR); disabling ASPM
  [1.694527] RAS: Correctable Errors collector initialized.
  [9.833145] EXT4-fs (sda2): re-mounted. Opts: errors=remount-ro

  I'm not a developer but only a user. So if i opened that issue to the
  wrong place can you point me the correct place to open it?

  Thanks.
  --- 
  ApportVersion: 2.20.1-0ubuntu2.12
  Architecture: amd64
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux 18.2
  InstallationDate: Installed on 2017-10-22 (24 days ago)
  InstallationMedia: Linux Mint 18.2 "Sonya" - Release amd64 20170628
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=tr_TR.UTF-8
   SHELL=/bin/bash
  Tags:  sonya
  Uname: Linux 4.14.0-041400-generic x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  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/linux/+bug/1732686/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : 

[Kernel-packages] [Bug 1729337] Re: CIFS errors on 4.4.0-98, but not on 4.4.0-97 with same config

[FedeX]

Hi Joseph,

Thanks for that

No worries, I'll test this now and report back to you

Cheers
FedeX

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

Title:
  CIFS errors on 4.4.0-98, but not on 4.4.0-97 with same config

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

Bug description:
  == SRU Justification ==
  The bug reporter stated they have a cluster of servers that applied Xenial 
updates
  and then were unable to mount CIFS shares after upgrading to 4.4.0-98. The
  same machines on 4.4.0-97 do not hit the regression.  It was found that the
  regression is fixed by mainline commit:
  4587eee04e2a ("SMB3: Validate negotiate request must always be signed").

  This fix is required in all Ubuntu supported releases.  Commit 4587eee04e2a
  landed in mailine as of 4.14-rc7.  It  was also cc'd to upstream stable,
  but it has not landed in any stable releases yet, which is the reason for
  this SRU.


  == Fix ==
  commit 4587eee04e2ac7ac3ac9fa2bc164fb6e548f99cd
  Author: Steve French 
  Date:   Wed Oct 25 15:58:31 2017 -0500
  SMB3: Validate negotiate request must always be signed

  == Regression Potential ==
  This patch is to fix a regression.  It was also cc'd to upstream stable, so
  it received addition review upstream.

  We have a cluster of servers that applied a security update overnight
  and were unable to mount CIFS shares after upgrading to 4.4.0-98.  The
  same machines on 4.4.0-97 were fine the night before, and are fine
  after downgrading.  The only error message CIFS would report, even on
  verbose, was:

  [  257.089876] CIFS VFS: validate protocol negotiate failed: -11
  [  257.089964] CIFS VFS: cifs_mount failed w/return code = -5

  Rebooting did not help.  Nor did attempting to mount the share
  manually using mount -t cifs.

  Here's the offending line from our /etc/fstab (with hostnames
  sanitized):

  //server/share /mnt/share cifs 
rw,user,credentials=/etc/samba/credentials.share,uid=33,gid=33,file_mode=0770,dir_mode=0770
  ,exec,soft,noserverino,vers=3.0 0 0

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-98-generic 4.4.0-98.121
  ProcVersionSignature: Ubuntu 4.4.0-98.121-generic 4.4.90
  Uname: Linux 4.4.0-98-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Nov  1 07:56 seq
   crw-rw 1 root audio 116, 33 Nov  1 07:56 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: Wed Nov  1 08:49:47 2017
  HibernationDevice: RESUME=/dev/mapper/ubuntu--template--vg-swap_1
  InstallationDate: Installed on 2016-12-16 (319 days ago)
  InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  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:

  ProcFB: 0 svgadrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-98-generic 
root=/dev/mapper/ubuntu--template--vg-root ro
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-98-generic N/A
   linux-backports-modules-4.4.0-98-generic  N/A
   linux-firmware1.157.13
  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/1729337/+subscriptions

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

Re: [Kernel-packages] [Bug 1729674] Re: TB16 dock ethernet corrupts data with hw checksum silently failing

[Kai-Heng Feng]

> On 20 Nov 2017, at 11:47 PM, Dave Chiluk <1729...@bugs.launchpad.net> wrote:
> 
> I reviewed your patch, and it appears as if it only turns off receive
> checksumming. The internets are saying that transmit needs to be turned off
> as well.  Have you checked to see if transmit is affected as well?

TX is not affected under my simple NFS testing.

> 
> I will try to do some transmit tests.  I'll also "test" your kernel when I
> get a chance, but by the looks of the patch there shouldn't be too much to
> test as it simply turns off RX checksuming which is already a known good
> solution.

Yea, just want to make sure USB/PCI ids are the same for both TB15 and TB16.
The TB15 at my hand is not even the mass production one.

> 
> On Mon, Nov 20, 2017 at 2:06 AM, Kai-Heng Feng 
> wrote:
> 
>> Dave,
>> 
>> Please try this kernel,
>> http://people.canonical.com/~khfeng/lp1729674/
>> 
>> The temporary workaround is what we can get before chip vendors solve
>> the issue.
>> 
>> --
>> You received this bug notification because you are subscribed to the bug
>> report.
>> https://bugs.launchpad.net/bugs/1729674
>> 
>> Title:
>>  TB16 dock ethernet corrupts data with hw checksum silently failing
>> 
>> Status in Dell Sputnik:
>>  Triaged
>> Status in linux package in Ubuntu:
>>  In Progress
>> Status in linux package in Fedora:
>>  Confirmed
>> 
>> Bug description:
>>  It looks like TCP  rx and tx checksum offloading is broken on the TB16
>> dock's ethernet adapter. For example downloading a large file such as the
>> Ubuntu ISO, and then running an md5sum on it yields the incorrect md5sum.
>> This is because
>>  rx-checksumming: on
>>  tx-checksumming: on
>>  and both set to on by default.
>> 
>>  Running sudo ethtool -K  tx off rx off, allows the
>>  download to complete correctly.  This is very bad since this can cause
>>  very bad untrustworthy behavior.
>> 
>>  This was conducted using an Dell Precision 5520 on Ubuntu 16.04+linux-
>>  generic-hwe-16.04-edge.
>> 
>>  Thank you
>> 
>> To manage notifications about this bug go to:
>> https://bugs.launchpad.net/dell-sputnik/+bug/1729674/+subscriptions
>> 
> 
> -- 
> You received this bug notification because you are a bug assignee.
> https://bugs.launchpad.net/bugs/1729674
> 
> Title:
>  TB16 dock ethernet corrupts data with hw checksum silently failing
> 
> Status in Dell Sputnik:
>  Triaged
> Status in linux package in Ubuntu:
>  In Progress
> Status in linux package in Fedora:
>  Confirmed
> 
> Bug description:
>  It looks like TCP  rx and tx checksum offloading is broken on the TB16 
> dock's ethernet adapter. For example downloading a large file such as the 
> Ubuntu ISO, and then running an md5sum on it yields the incorrect md5sum.  
> This is because
>  rx-checksumming: on
>  tx-checksumming: on
>  and both set to on by default.
> 
>  Running sudo ethtool -K  tx off rx off, allows the
>  download to complete correctly.  This is very bad since this can cause
>  very bad untrustworthy behavior.
> 
>  This was conducted using an Dell Precision 5520 on Ubuntu 16.04+linux-
>  generic-hwe-16.04-edge.
> 
>  Thank you
> 
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/dell-sputnik/+bug/1729674/+subscriptions

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

Title:
  TB16 dock ethernet corrupts data with hw checksum silently failing

Status in Dell Sputnik:
  Triaged
Status in linux package in Ubuntu:
  In Progress
Status in linux package in Fedora:
  Confirmed

Bug description:
  It looks like TCP  rx and tx checksum offloading is broken on the TB16 dock's 
ethernet adapter. For example downloading a large file such as the Ubuntu ISO, 
and then running an md5sum on it yields the incorrect md5sum.  This is because
  rx-checksumming: on
  tx-checksumming: on
  and both set to on by default.

  Running sudo ethtool -K  tx off rx off, allows the
  download to complete correctly.  This is very bad since this can cause
  very bad untrustworthy behavior.

  This was conducted using an Dell Precision 5520 on Ubuntu 16.04+linux-
  generic-hwe-16.04-edge.

  Thank you

To manage notifications about this bug go to:
https://bugs.launchpad.net/dell-sputnik/+bug/1729674/+subscriptions

-- 
Mailing list: https://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 1718284] Re: package linux-image-4.10.0-35-generic 4.10.0-35.39 failed to install/upgrade: subprocess new pre-installation script returned error exit status 128

[Launchpad Bug Tracker]

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

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

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

Title:
  package linux-image-4.10.0-35-generic 4.10.0-35.39 failed to
  install/upgrade: subprocess new pre-installation script returned error
  exit status 128

Status in linux package in Ubuntu:
  Expired

Bug description:
  recurring failure to install. likely to be local issue

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: linux-image-4.10.0-35-generic 4.10.0-35.39
  ProcVersionSignature: Ubuntu 4.10.0-35.39-generic 4.10.17
  Uname: Linux 4.10.0-35-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  alex   3521 F pulseaudio
   /dev/snd/controlC0:  alex   3521 F pulseaudio
  Date: Mon Sep 18 17:29:36 2017
  ErrorMessage: subprocess new pre-installation script returned error exit 
status 128
  HibernationDevice: RESUME=UUID=53248f42-e64e-45c2-a19c-ea82c55b9eb5
  InstallationDate: Installed on 2016-11-16 (307 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  MachineType: Hewlett-Packard HP Pavilion 15 Notebook PC
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-35-generic.efi.signed 
root=UUID=520bf0a3-9021-4268-b355-10efda7b0177 ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: grub-pc N/A
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  Title: package linux-image-4.10.0-35-generic 4.10.0-35.39 failed to 
install/upgrade: subprocess new pre-installation script returned error exit 
status 128
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/26/2013
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.23
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 2163
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 29.24
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.23:bd09/26/2013:svnHewlett-Packard:pnHPPavilion15NotebookPC:pvr08961030410620100:rvnHewlett-Packard:rn2163:rvr29.24:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.name: HP Pavilion 15 Notebook PC
  dmi.product.version: 08961030410620100
  dmi.sys.vendor: Hewlett-Packard

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

-- 
Mailing list: https://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 1730607] CurrentDmesg.txt

[Andrey Vertexx]

apport information

** Attachment added: "CurrentDmesg.txt"
   
https://bugs.launchpad.net/bugs/1730607/+attachment/5011963/+files/CurrentDmesg.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/1730607

Title:
  mount cifs with SMB 3.0 stop working

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

Bug description:
  I have a Ubuntu Server (14.04.5 LTS (GNU/Linux 4.4.0-98-generic x86_64)) and 
a Windows Server 2012 R2 File Server with a File Share. I mounted a file share 
to my linux server with a cifs-utils.
  Everything worked fine until some kernel update installed on Ubuntu. SMB 3.0 
stopped working and my share not mounted.

  sudo mount -t cifs //myserver.xxx.net/WebBackup -o
  username=user,password=P@ssw0rd,domain=xxx.net,vers=3.0 /backupdrive -
  not working

  mount error(5): Input/output error
  Refer to the mount.cifs(8) manual page (e.g. man mount.cifs)

  if i change to vers=2.1 - it it work
  --- 
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Nov  7 16:11 seq
   crw-rw 1 root audio 116, 33 Nov  7 16:11 timer
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.14.1-0ubuntu3.25
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: Error: [Errno 2] No such file or directory
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=/dev/mapper/ubuntu--vg-swap_1
  InstallationDate: Installed on 2016-02-20 (626 days ago)
  InstallationMedia: Ubuntu-Server 14.04.3 LTS "Trusty Tahr" - Beta amd64 
(20150805)
  IwConfig:
   lono wireless extensions.
   
   eth1  no wireless extensions.
   
   eth0  no wireless extensions.
  Lspci:
   
  Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize 
libusb: -99
  MachineType: Microsoft Corporation Virtual Machine
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=C
   SHELL=/bin/bash
  ProcFB: 0 hyperv_fb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-98-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro
  ProcVersionSignature: Ubuntu 4.4.0-98.121~14.04.1-generic 4.4.90
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-98-generic N/A
   linux-backports-modules-4.4.0-98-generic  N/A
   linux-firmware1.127.23
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  trusty
  Uname: Linux 4.4.0-98-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 11/26/2012
  dmi.bios.vendor: Microsoft Corporation
  dmi.bios.version: Hyper-V UEFI Release v1.0
  dmi.board.asset.tag: None
  dmi.board.name: Virtual Machine
  dmi.board.vendor: Microsoft Corporation
  dmi.board.version: Hyper-V UEFI Release v1.0
  dmi.chassis.asset.tag: 0981-0252-2294-8432-2174-6395-64
  dmi.chassis.type: 3
  dmi.chassis.vendor: Microsoft Corporation
  dmi.chassis.version: Hyper-V UEFI Release v1.0
  dmi.modalias: 
dmi:bvnMicrosoftCorporation:bvrHyper-VUEFIReleasev1.0:bd11/26/2012:svnMicrosoftCorporation:pnVirtualMachine:pvrHyper-VUEFIReleasev1.0:rvnMicrosoftCorporation:rnVirtualMachine:rvrHyper-VUEFIReleasev1.0:cvnMicrosoftCorporation:ct3:cvrHyper-VUEFIReleasev1.0:
  dmi.product.name: Virtual Machine
  dmi.product.version: Hyper-V UEFI Release v1.0
  dmi.sys.vendor: Microsoft Corporation
  --- 
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Nov 21 11:15 seq
   crw-rw 1 root audio 116, 33 Nov 21 11:15 timer
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.14.1-0ubuntu3.27
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: Error: [Errno 2] No such file or directory
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=/dev/mapper/ubuntu--vg-swap_1
  InstallationDate: Installed on 2016-02-20 (639 days ago)
  InstallationMedia: Ubuntu-Server 14.04.3 LTS "Trusty Tahr" - Beta amd64 
(20150805)
  IwConfig:
   lono wireless extensions.
   
   eth1  no wireless extensions.
   
   eth0  no wireless extensions.
  Lspci:
   
  Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize 
libusb: -99
  MachineType: Microsoft Corporation Virtual Machine
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=C
   SHELL=/bin/bash
  ProcFB: 0 hyperv_fb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-101-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro
  ProcVersionSignature: Ubuntu 4.4.0-101.124~14.04.1-generic 4.4.95
  

[Kernel-packages] [Bug 1730607] UdevDb.txt

[Andrey Vertexx]

apport information

** Attachment added: "UdevDb.txt"
   https://bugs.launchpad.net/bugs/1730607/+attachment/5011968/+files/UdevDb.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/1730607

Title:
  mount cifs with SMB 3.0 stop working

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

Bug description:
  I have a Ubuntu Server (14.04.5 LTS (GNU/Linux 4.4.0-98-generic x86_64)) and 
a Windows Server 2012 R2 File Server with a File Share. I mounted a file share 
to my linux server with a cifs-utils.
  Everything worked fine until some kernel update installed on Ubuntu. SMB 3.0 
stopped working and my share not mounted.

  sudo mount -t cifs //myserver.xxx.net/WebBackup -o
  username=user,password=P@ssw0rd,domain=xxx.net,vers=3.0 /backupdrive -
  not working

  mount error(5): Input/output error
  Refer to the mount.cifs(8) manual page (e.g. man mount.cifs)

  if i change to vers=2.1 - it it work
  --- 
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Nov  7 16:11 seq
   crw-rw 1 root audio 116, 33 Nov  7 16:11 timer
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.14.1-0ubuntu3.25
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: Error: [Errno 2] No such file or directory
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=/dev/mapper/ubuntu--vg-swap_1
  InstallationDate: Installed on 2016-02-20 (626 days ago)
  InstallationMedia: Ubuntu-Server 14.04.3 LTS "Trusty Tahr" - Beta amd64 
(20150805)
  IwConfig:
   lono wireless extensions.
   
   eth1  no wireless extensions.
   
   eth0  no wireless extensions.
  Lspci:
   
  Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize 
libusb: -99
  MachineType: Microsoft Corporation Virtual Machine
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=C
   SHELL=/bin/bash
  ProcFB: 0 hyperv_fb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-98-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro
  ProcVersionSignature: Ubuntu 4.4.0-98.121~14.04.1-generic 4.4.90
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-98-generic N/A
   linux-backports-modules-4.4.0-98-generic  N/A
   linux-firmware1.127.23
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  trusty
  Uname: Linux 4.4.0-98-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 11/26/2012
  dmi.bios.vendor: Microsoft Corporation
  dmi.bios.version: Hyper-V UEFI Release v1.0
  dmi.board.asset.tag: None
  dmi.board.name: Virtual Machine
  dmi.board.vendor: Microsoft Corporation
  dmi.board.version: Hyper-V UEFI Release v1.0
  dmi.chassis.asset.tag: 0981-0252-2294-8432-2174-6395-64
  dmi.chassis.type: 3
  dmi.chassis.vendor: Microsoft Corporation
  dmi.chassis.version: Hyper-V UEFI Release v1.0
  dmi.modalias: 
dmi:bvnMicrosoftCorporation:bvrHyper-VUEFIReleasev1.0:bd11/26/2012:svnMicrosoftCorporation:pnVirtualMachine:pvrHyper-VUEFIReleasev1.0:rvnMicrosoftCorporation:rnVirtualMachine:rvrHyper-VUEFIReleasev1.0:cvnMicrosoftCorporation:ct3:cvrHyper-VUEFIReleasev1.0:
  dmi.product.name: Virtual Machine
  dmi.product.version: Hyper-V UEFI Release v1.0
  dmi.sys.vendor: Microsoft Corporation
  --- 
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Nov 21 11:15 seq
   crw-rw 1 root audio 116, 33 Nov 21 11:15 timer
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.14.1-0ubuntu3.27
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: Error: [Errno 2] No such file or directory
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=/dev/mapper/ubuntu--vg-swap_1
  InstallationDate: Installed on 2016-02-20 (639 days ago)
  InstallationMedia: Ubuntu-Server 14.04.3 LTS "Trusty Tahr" - Beta amd64 
(20150805)
  IwConfig:
   lono wireless extensions.
   
   eth1  no wireless extensions.
   
   eth0  no wireless extensions.
  Lspci:
   
  Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize 
libusb: -99
  MachineType: Microsoft Corporation Virtual Machine
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=C
   SHELL=/bin/bash
  ProcFB: 0 hyperv_fb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-101-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro
  ProcVersionSignature: Ubuntu 4.4.0-101.124~14.04.1-generic 4.4.95
  

[Kernel-packages] [Bug 1730607] ProcInterrupts.txt

[Andrey Vertexx]

apport information

** Attachment added: "ProcInterrupts.txt"
   
https://bugs.launchpad.net/bugs/1730607/+attachment/5011966/+files/ProcInterrupts.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/1730607

Title:
  mount cifs with SMB 3.0 stop working

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

Bug description:
  I have a Ubuntu Server (14.04.5 LTS (GNU/Linux 4.4.0-98-generic x86_64)) and 
a Windows Server 2012 R2 File Server with a File Share. I mounted a file share 
to my linux server with a cifs-utils.
  Everything worked fine until some kernel update installed on Ubuntu. SMB 3.0 
stopped working and my share not mounted.

  sudo mount -t cifs //myserver.xxx.net/WebBackup -o
  username=user,password=P@ssw0rd,domain=xxx.net,vers=3.0 /backupdrive -
  not working

  mount error(5): Input/output error
  Refer to the mount.cifs(8) manual page (e.g. man mount.cifs)

  if i change to vers=2.1 - it it work
  --- 
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Nov  7 16:11 seq
   crw-rw 1 root audio 116, 33 Nov  7 16:11 timer
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.14.1-0ubuntu3.25
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: Error: [Errno 2] No such file or directory
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=/dev/mapper/ubuntu--vg-swap_1
  InstallationDate: Installed on 2016-02-20 (626 days ago)
  InstallationMedia: Ubuntu-Server 14.04.3 LTS "Trusty Tahr" - Beta amd64 
(20150805)
  IwConfig:
   lono wireless extensions.
   
   eth1  no wireless extensions.
   
   eth0  no wireless extensions.
  Lspci:
   
  Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize 
libusb: -99
  MachineType: Microsoft Corporation Virtual Machine
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=C
   SHELL=/bin/bash
  ProcFB: 0 hyperv_fb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-98-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro
  ProcVersionSignature: Ubuntu 4.4.0-98.121~14.04.1-generic 4.4.90
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-98-generic N/A
   linux-backports-modules-4.4.0-98-generic  N/A
   linux-firmware1.127.23
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  trusty
  Uname: Linux 4.4.0-98-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 11/26/2012
  dmi.bios.vendor: Microsoft Corporation
  dmi.bios.version: Hyper-V UEFI Release v1.0
  dmi.board.asset.tag: None
  dmi.board.name: Virtual Machine
  dmi.board.vendor: Microsoft Corporation
  dmi.board.version: Hyper-V UEFI Release v1.0
  dmi.chassis.asset.tag: 0981-0252-2294-8432-2174-6395-64
  dmi.chassis.type: 3
  dmi.chassis.vendor: Microsoft Corporation
  dmi.chassis.version: Hyper-V UEFI Release v1.0
  dmi.modalias: 
dmi:bvnMicrosoftCorporation:bvrHyper-VUEFIReleasev1.0:bd11/26/2012:svnMicrosoftCorporation:pnVirtualMachine:pvrHyper-VUEFIReleasev1.0:rvnMicrosoftCorporation:rnVirtualMachine:rvrHyper-VUEFIReleasev1.0:cvnMicrosoftCorporation:ct3:cvrHyper-VUEFIReleasev1.0:
  dmi.product.name: Virtual Machine
  dmi.product.version: Hyper-V UEFI Release v1.0
  dmi.sys.vendor: Microsoft Corporation
  --- 
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Nov 21 11:15 seq
   crw-rw 1 root audio 116, 33 Nov 21 11:15 timer
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.14.1-0ubuntu3.27
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: Error: [Errno 2] No such file or directory
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=/dev/mapper/ubuntu--vg-swap_1
  InstallationDate: Installed on 2016-02-20 (639 days ago)
  InstallationMedia: Ubuntu-Server 14.04.3 LTS "Trusty Tahr" - Beta amd64 
(20150805)
  IwConfig:
   lono wireless extensions.
   
   eth1  no wireless extensions.
   
   eth0  no wireless extensions.
  Lspci:
   
  Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize 
libusb: -99
  MachineType: Microsoft Corporation Virtual Machine
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=C
   SHELL=/bin/bash
  ProcFB: 0 hyperv_fb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-101-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro
  ProcVersionSignature: Ubuntu 4.4.0-101.124~14.04.1-generic 4.4.95
  

[Kernel-packages] [Bug 1730607] ProcModules.txt

[Andrey Vertexx]

apport information

** Attachment added: "ProcModules.txt"
   
https://bugs.launchpad.net/bugs/1730607/+attachment/5011967/+files/ProcModules.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/1730607

Title:
  mount cifs with SMB 3.0 stop working

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

Bug description:
  I have a Ubuntu Server (14.04.5 LTS (GNU/Linux 4.4.0-98-generic x86_64)) and 
a Windows Server 2012 R2 File Server with a File Share. I mounted a file share 
to my linux server with a cifs-utils.
  Everything worked fine until some kernel update installed on Ubuntu. SMB 3.0 
stopped working and my share not mounted.

  sudo mount -t cifs //myserver.xxx.net/WebBackup -o
  username=user,password=P@ssw0rd,domain=xxx.net,vers=3.0 /backupdrive -
  not working

  mount error(5): Input/output error
  Refer to the mount.cifs(8) manual page (e.g. man mount.cifs)

  if i change to vers=2.1 - it it work
  --- 
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Nov  7 16:11 seq
   crw-rw 1 root audio 116, 33 Nov  7 16:11 timer
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.14.1-0ubuntu3.25
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: Error: [Errno 2] No such file or directory
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=/dev/mapper/ubuntu--vg-swap_1
  InstallationDate: Installed on 2016-02-20 (626 days ago)
  InstallationMedia: Ubuntu-Server 14.04.3 LTS "Trusty Tahr" - Beta amd64 
(20150805)
  IwConfig:
   lono wireless extensions.
   
   eth1  no wireless extensions.
   
   eth0  no wireless extensions.
  Lspci:
   
  Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize 
libusb: -99
  MachineType: Microsoft Corporation Virtual Machine
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=C
   SHELL=/bin/bash
  ProcFB: 0 hyperv_fb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-98-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro
  ProcVersionSignature: Ubuntu 4.4.0-98.121~14.04.1-generic 4.4.90
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-98-generic N/A
   linux-backports-modules-4.4.0-98-generic  N/A
   linux-firmware1.127.23
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  trusty
  Uname: Linux 4.4.0-98-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 11/26/2012
  dmi.bios.vendor: Microsoft Corporation
  dmi.bios.version: Hyper-V UEFI Release v1.0
  dmi.board.asset.tag: None
  dmi.board.name: Virtual Machine
  dmi.board.vendor: Microsoft Corporation
  dmi.board.version: Hyper-V UEFI Release v1.0
  dmi.chassis.asset.tag: 0981-0252-2294-8432-2174-6395-64
  dmi.chassis.type: 3
  dmi.chassis.vendor: Microsoft Corporation
  dmi.chassis.version: Hyper-V UEFI Release v1.0
  dmi.modalias: 
dmi:bvnMicrosoftCorporation:bvrHyper-VUEFIReleasev1.0:bd11/26/2012:svnMicrosoftCorporation:pnVirtualMachine:pvrHyper-VUEFIReleasev1.0:rvnMicrosoftCorporation:rnVirtualMachine:rvrHyper-VUEFIReleasev1.0:cvnMicrosoftCorporation:ct3:cvrHyper-VUEFIReleasev1.0:
  dmi.product.name: Virtual Machine
  dmi.product.version: Hyper-V UEFI Release v1.0
  dmi.sys.vendor: Microsoft Corporation
  --- 
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Nov 21 11:15 seq
   crw-rw 1 root audio 116, 33 Nov 21 11:15 timer
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.14.1-0ubuntu3.27
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: Error: [Errno 2] No such file or directory
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=/dev/mapper/ubuntu--vg-swap_1
  InstallationDate: Installed on 2016-02-20 (639 days ago)
  InstallationMedia: Ubuntu-Server 14.04.3 LTS "Trusty Tahr" - Beta amd64 
(20150805)
  IwConfig:
   lono wireless extensions.
   
   eth1  no wireless extensions.
   
   eth0  no wireless extensions.
  Lspci:
   
  Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize 
libusb: -99
  MachineType: Microsoft Corporation Virtual Machine
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=C
   SHELL=/bin/bash
  ProcFB: 0 hyperv_fb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-101-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro
  ProcVersionSignature: Ubuntu 4.4.0-101.124~14.04.1-generic 4.4.95
  

[Kernel-packages] [Bug 1730607] ProcCpuinfo.txt

[Andrey Vertexx]

apport information

** Attachment added: "ProcCpuinfo.txt"
   
https://bugs.launchpad.net/bugs/1730607/+attachment/5011964/+files/ProcCpuinfo.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/1730607

Title:
  mount cifs with SMB 3.0 stop working

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

Bug description:
  I have a Ubuntu Server (14.04.5 LTS (GNU/Linux 4.4.0-98-generic x86_64)) and 
a Windows Server 2012 R2 File Server with a File Share. I mounted a file share 
to my linux server with a cifs-utils.
  Everything worked fine until some kernel update installed on Ubuntu. SMB 3.0 
stopped working and my share not mounted.

  sudo mount -t cifs //myserver.xxx.net/WebBackup -o
  username=user,password=P@ssw0rd,domain=xxx.net,vers=3.0 /backupdrive -
  not working

  mount error(5): Input/output error
  Refer to the mount.cifs(8) manual page (e.g. man mount.cifs)

  if i change to vers=2.1 - it it work
  --- 
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Nov  7 16:11 seq
   crw-rw 1 root audio 116, 33 Nov  7 16:11 timer
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.14.1-0ubuntu3.25
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: Error: [Errno 2] No such file or directory
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=/dev/mapper/ubuntu--vg-swap_1
  InstallationDate: Installed on 2016-02-20 (626 days ago)
  InstallationMedia: Ubuntu-Server 14.04.3 LTS "Trusty Tahr" - Beta amd64 
(20150805)
  IwConfig:
   lono wireless extensions.
   
   eth1  no wireless extensions.
   
   eth0  no wireless extensions.
  Lspci:
   
  Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize 
libusb: -99
  MachineType: Microsoft Corporation Virtual Machine
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=C
   SHELL=/bin/bash
  ProcFB: 0 hyperv_fb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-98-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro
  ProcVersionSignature: Ubuntu 4.4.0-98.121~14.04.1-generic 4.4.90
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-98-generic N/A
   linux-backports-modules-4.4.0-98-generic  N/A
   linux-firmware1.127.23
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  trusty
  Uname: Linux 4.4.0-98-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 11/26/2012
  dmi.bios.vendor: Microsoft Corporation
  dmi.bios.version: Hyper-V UEFI Release v1.0
  dmi.board.asset.tag: None
  dmi.board.name: Virtual Machine
  dmi.board.vendor: Microsoft Corporation
  dmi.board.version: Hyper-V UEFI Release v1.0
  dmi.chassis.asset.tag: 0981-0252-2294-8432-2174-6395-64
  dmi.chassis.type: 3
  dmi.chassis.vendor: Microsoft Corporation
  dmi.chassis.version: Hyper-V UEFI Release v1.0
  dmi.modalias: 
dmi:bvnMicrosoftCorporation:bvrHyper-VUEFIReleasev1.0:bd11/26/2012:svnMicrosoftCorporation:pnVirtualMachine:pvrHyper-VUEFIReleasev1.0:rvnMicrosoftCorporation:rnVirtualMachine:rvrHyper-VUEFIReleasev1.0:cvnMicrosoftCorporation:ct3:cvrHyper-VUEFIReleasev1.0:
  dmi.product.name: Virtual Machine
  dmi.product.version: Hyper-V UEFI Release v1.0
  dmi.sys.vendor: Microsoft Corporation
  --- 
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Nov 21 11:15 seq
   crw-rw 1 root audio 116, 33 Nov 21 11:15 timer
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.14.1-0ubuntu3.27
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: Error: [Errno 2] No such file or directory
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=/dev/mapper/ubuntu--vg-swap_1
  InstallationDate: Installed on 2016-02-20 (639 days ago)
  InstallationMedia: Ubuntu-Server 14.04.3 LTS "Trusty Tahr" - Beta amd64 
(20150805)
  IwConfig:
   lono wireless extensions.
   
   eth1  no wireless extensions.
   
   eth0  no wireless extensions.
  Lspci:
   
  Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize 
libusb: -99
  MachineType: Microsoft Corporation Virtual Machine
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=C
   SHELL=/bin/bash
  ProcFB: 0 hyperv_fb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-101-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro
  ProcVersionSignature: Ubuntu 4.4.0-101.124~14.04.1-generic 4.4.95
  

[Kernel-packages] [Bug 1730607] UdevLog.txt

[Andrey Vertexx]

apport information

** Attachment added: "UdevLog.txt"
   
https://bugs.launchpad.net/bugs/1730607/+attachment/5011969/+files/UdevLog.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/1730607

Title:
  mount cifs with SMB 3.0 stop working

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

Bug description:
  I have a Ubuntu Server (14.04.5 LTS (GNU/Linux 4.4.0-98-generic x86_64)) and 
a Windows Server 2012 R2 File Server with a File Share. I mounted a file share 
to my linux server with a cifs-utils.
  Everything worked fine until some kernel update installed on Ubuntu. SMB 3.0 
stopped working and my share not mounted.

  sudo mount -t cifs //myserver.xxx.net/WebBackup -o
  username=user,password=P@ssw0rd,domain=xxx.net,vers=3.0 /backupdrive -
  not working

  mount error(5): Input/output error
  Refer to the mount.cifs(8) manual page (e.g. man mount.cifs)

  if i change to vers=2.1 - it it work
  --- 
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Nov  7 16:11 seq
   crw-rw 1 root audio 116, 33 Nov  7 16:11 timer
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.14.1-0ubuntu3.25
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: Error: [Errno 2] No such file or directory
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=/dev/mapper/ubuntu--vg-swap_1
  InstallationDate: Installed on 2016-02-20 (626 days ago)
  InstallationMedia: Ubuntu-Server 14.04.3 LTS "Trusty Tahr" - Beta amd64 
(20150805)
  IwConfig:
   lono wireless extensions.
   
   eth1  no wireless extensions.
   
   eth0  no wireless extensions.
  Lspci:
   
  Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize 
libusb: -99
  MachineType: Microsoft Corporation Virtual Machine
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=C
   SHELL=/bin/bash
  ProcFB: 0 hyperv_fb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-98-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro
  ProcVersionSignature: Ubuntu 4.4.0-98.121~14.04.1-generic 4.4.90
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-98-generic N/A
   linux-backports-modules-4.4.0-98-generic  N/A
   linux-firmware1.127.23
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  trusty
  Uname: Linux 4.4.0-98-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 11/26/2012
  dmi.bios.vendor: Microsoft Corporation
  dmi.bios.version: Hyper-V UEFI Release v1.0
  dmi.board.asset.tag: None
  dmi.board.name: Virtual Machine
  dmi.board.vendor: Microsoft Corporation
  dmi.board.version: Hyper-V UEFI Release v1.0
  dmi.chassis.asset.tag: 0981-0252-2294-8432-2174-6395-64
  dmi.chassis.type: 3
  dmi.chassis.vendor: Microsoft Corporation
  dmi.chassis.version: Hyper-V UEFI Release v1.0
  dmi.modalias: 
dmi:bvnMicrosoftCorporation:bvrHyper-VUEFIReleasev1.0:bd11/26/2012:svnMicrosoftCorporation:pnVirtualMachine:pvrHyper-VUEFIReleasev1.0:rvnMicrosoftCorporation:rnVirtualMachine:rvrHyper-VUEFIReleasev1.0:cvnMicrosoftCorporation:ct3:cvrHyper-VUEFIReleasev1.0:
  dmi.product.name: Virtual Machine
  dmi.product.version: Hyper-V UEFI Release v1.0
  dmi.sys.vendor: Microsoft Corporation
  --- 
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Nov 21 11:15 seq
   crw-rw 1 root audio 116, 33 Nov 21 11:15 timer
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.14.1-0ubuntu3.27
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: Error: [Errno 2] No such file or directory
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=/dev/mapper/ubuntu--vg-swap_1
  InstallationDate: Installed on 2016-02-20 (639 days ago)
  InstallationMedia: Ubuntu-Server 14.04.3 LTS "Trusty Tahr" - Beta amd64 
(20150805)
  IwConfig:
   lono wireless extensions.
   
   eth1  no wireless extensions.
   
   eth0  no wireless extensions.
  Lspci:
   
  Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize 
libusb: -99
  MachineType: Microsoft Corporation Virtual Machine
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=C
   SHELL=/bin/bash
  ProcFB: 0 hyperv_fb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-101-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro
  ProcVersionSignature: Ubuntu 4.4.0-101.124~14.04.1-generic 4.4.95
  

[Kernel-packages] [Bug 1730607] ProcCpuinfoMinimal.txt

[Andrey Vertexx]

apport information

** Attachment added: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/bugs/1730607/+attachment/5011965/+files/ProcCpuinfoMinimal.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/1730607

Title:
  mount cifs with SMB 3.0 stop working

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

Bug description:
  I have a Ubuntu Server (14.04.5 LTS (GNU/Linux 4.4.0-98-generic x86_64)) and 
a Windows Server 2012 R2 File Server with a File Share. I mounted a file share 
to my linux server with a cifs-utils.
  Everything worked fine until some kernel update installed on Ubuntu. SMB 3.0 
stopped working and my share not mounted.

  sudo mount -t cifs //myserver.xxx.net/WebBackup -o
  username=user,password=P@ssw0rd,domain=xxx.net,vers=3.0 /backupdrive -
  not working

  mount error(5): Input/output error
  Refer to the mount.cifs(8) manual page (e.g. man mount.cifs)

  if i change to vers=2.1 - it it work
  --- 
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Nov  7 16:11 seq
   crw-rw 1 root audio 116, 33 Nov  7 16:11 timer
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.14.1-0ubuntu3.25
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: Error: [Errno 2] No such file or directory
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=/dev/mapper/ubuntu--vg-swap_1
  InstallationDate: Installed on 2016-02-20 (626 days ago)
  InstallationMedia: Ubuntu-Server 14.04.3 LTS "Trusty Tahr" - Beta amd64 
(20150805)
  IwConfig:
   lono wireless extensions.
   
   eth1  no wireless extensions.
   
   eth0  no wireless extensions.
  Lspci:
   
  Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize 
libusb: -99
  MachineType: Microsoft Corporation Virtual Machine
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=C
   SHELL=/bin/bash
  ProcFB: 0 hyperv_fb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-98-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro
  ProcVersionSignature: Ubuntu 4.4.0-98.121~14.04.1-generic 4.4.90
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-98-generic N/A
   linux-backports-modules-4.4.0-98-generic  N/A
   linux-firmware1.127.23
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  trusty
  Uname: Linux 4.4.0-98-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 11/26/2012
  dmi.bios.vendor: Microsoft Corporation
  dmi.bios.version: Hyper-V UEFI Release v1.0
  dmi.board.asset.tag: None
  dmi.board.name: Virtual Machine
  dmi.board.vendor: Microsoft Corporation
  dmi.board.version: Hyper-V UEFI Release v1.0
  dmi.chassis.asset.tag: 0981-0252-2294-8432-2174-6395-64
  dmi.chassis.type: 3
  dmi.chassis.vendor: Microsoft Corporation
  dmi.chassis.version: Hyper-V UEFI Release v1.0
  dmi.modalias: 
dmi:bvnMicrosoftCorporation:bvrHyper-VUEFIReleasev1.0:bd11/26/2012:svnMicrosoftCorporation:pnVirtualMachine:pvrHyper-VUEFIReleasev1.0:rvnMicrosoftCorporation:rnVirtualMachine:rvrHyper-VUEFIReleasev1.0:cvnMicrosoftCorporation:ct3:cvrHyper-VUEFIReleasev1.0:
  dmi.product.name: Virtual Machine
  dmi.product.version: Hyper-V UEFI Release v1.0
  dmi.sys.vendor: Microsoft Corporation
  --- 
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Nov 21 11:15 seq
   crw-rw 1 root audio 116, 33 Nov 21 11:15 timer
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.14.1-0ubuntu3.27
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: Error: [Errno 2] No such file or directory
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=/dev/mapper/ubuntu--vg-swap_1
  InstallationDate: Installed on 2016-02-20 (639 days ago)
  InstallationMedia: Ubuntu-Server 14.04.3 LTS "Trusty Tahr" - Beta amd64 
(20150805)
  IwConfig:
   lono wireless extensions.
   
   eth1  no wireless extensions.
   
   eth0  no wireless extensions.
  Lspci:
   
  Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize 
libusb: -99
  MachineType: Microsoft Corporation Virtual Machine
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=C
   SHELL=/bin/bash
  ProcFB: 0 hyperv_fb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-101-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro
  ProcVersionSignature: Ubuntu 4.4.0-101.124~14.04.1-generic 

[Kernel-packages] [Bug 1730607] WifiSyslog.txt

[Andrey Vertexx]

apport information

** Attachment added: "WifiSyslog.txt"
   
https://bugs.launchpad.net/bugs/1730607/+attachment/5011970/+files/WifiSyslog.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/1730607

Title:
  mount cifs with SMB 3.0 stop working

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

Bug description:
  I have a Ubuntu Server (14.04.5 LTS (GNU/Linux 4.4.0-98-generic x86_64)) and 
a Windows Server 2012 R2 File Server with a File Share. I mounted a file share 
to my linux server with a cifs-utils.
  Everything worked fine until some kernel update installed on Ubuntu. SMB 3.0 
stopped working and my share not mounted.

  sudo mount -t cifs //myserver.xxx.net/WebBackup -o
  username=user,password=P@ssw0rd,domain=xxx.net,vers=3.0 /backupdrive -
  not working

  mount error(5): Input/output error
  Refer to the mount.cifs(8) manual page (e.g. man mount.cifs)

  if i change to vers=2.1 - it it work
  --- 
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Nov  7 16:11 seq
   crw-rw 1 root audio 116, 33 Nov  7 16:11 timer
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.14.1-0ubuntu3.25
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: Error: [Errno 2] No such file or directory
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=/dev/mapper/ubuntu--vg-swap_1
  InstallationDate: Installed on 2016-02-20 (626 days ago)
  InstallationMedia: Ubuntu-Server 14.04.3 LTS "Trusty Tahr" - Beta amd64 
(20150805)
  IwConfig:
   lono wireless extensions.
   
   eth1  no wireless extensions.
   
   eth0  no wireless extensions.
  Lspci:
   
  Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize 
libusb: -99
  MachineType: Microsoft Corporation Virtual Machine
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=C
   SHELL=/bin/bash
  ProcFB: 0 hyperv_fb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-98-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro
  ProcVersionSignature: Ubuntu 4.4.0-98.121~14.04.1-generic 4.4.90
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-98-generic N/A
   linux-backports-modules-4.4.0-98-generic  N/A
   linux-firmware1.127.23
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  trusty
  Uname: Linux 4.4.0-98-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 11/26/2012
  dmi.bios.vendor: Microsoft Corporation
  dmi.bios.version: Hyper-V UEFI Release v1.0
  dmi.board.asset.tag: None
  dmi.board.name: Virtual Machine
  dmi.board.vendor: Microsoft Corporation
  dmi.board.version: Hyper-V UEFI Release v1.0
  dmi.chassis.asset.tag: 0981-0252-2294-8432-2174-6395-64
  dmi.chassis.type: 3
  dmi.chassis.vendor: Microsoft Corporation
  dmi.chassis.version: Hyper-V UEFI Release v1.0
  dmi.modalias: 
dmi:bvnMicrosoftCorporation:bvrHyper-VUEFIReleasev1.0:bd11/26/2012:svnMicrosoftCorporation:pnVirtualMachine:pvrHyper-VUEFIReleasev1.0:rvnMicrosoftCorporation:rnVirtualMachine:rvrHyper-VUEFIReleasev1.0:cvnMicrosoftCorporation:ct3:cvrHyper-VUEFIReleasev1.0:
  dmi.product.name: Virtual Machine
  dmi.product.version: Hyper-V UEFI Release v1.0
  dmi.sys.vendor: Microsoft Corporation
  --- 
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Nov 21 11:15 seq
   crw-rw 1 root audio 116, 33 Nov 21 11:15 timer
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.14.1-0ubuntu3.27
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: Error: [Errno 2] No such file or directory
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=/dev/mapper/ubuntu--vg-swap_1
  InstallationDate: Installed on 2016-02-20 (639 days ago)
  InstallationMedia: Ubuntu-Server 14.04.3 LTS "Trusty Tahr" - Beta amd64 
(20150805)
  IwConfig:
   lono wireless extensions.
   
   eth1  no wireless extensions.
   
   eth0  no wireless extensions.
  Lspci:
   
  Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize 
libusb: -99
  MachineType: Microsoft Corporation Virtual Machine
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=C
   SHELL=/bin/bash
  ProcFB: 0 hyperv_fb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-101-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro
  ProcVersionSignature: Ubuntu 4.4.0-101.124~14.04.1-generic 4.4.95
  

[Kernel-packages] [Bug 1730607] BootDmesg.txt

[Andrey Vertexx]

apport information

** Attachment added: "BootDmesg.txt"
   
https://bugs.launchpad.net/bugs/1730607/+attachment/5011962/+files/BootDmesg.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/1730607

Title:
  mount cifs with SMB 3.0 stop working

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

Bug description:
  I have a Ubuntu Server (14.04.5 LTS (GNU/Linux 4.4.0-98-generic x86_64)) and 
a Windows Server 2012 R2 File Server with a File Share. I mounted a file share 
to my linux server with a cifs-utils.
  Everything worked fine until some kernel update installed on Ubuntu. SMB 3.0 
stopped working and my share not mounted.

  sudo mount -t cifs //myserver.xxx.net/WebBackup -o
  username=user,password=P@ssw0rd,domain=xxx.net,vers=3.0 /backupdrive -
  not working

  mount error(5): Input/output error
  Refer to the mount.cifs(8) manual page (e.g. man mount.cifs)

  if i change to vers=2.1 - it it work
  --- 
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Nov  7 16:11 seq
   crw-rw 1 root audio 116, 33 Nov  7 16:11 timer
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.14.1-0ubuntu3.25
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: Error: [Errno 2] No such file or directory
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=/dev/mapper/ubuntu--vg-swap_1
  InstallationDate: Installed on 2016-02-20 (626 days ago)
  InstallationMedia: Ubuntu-Server 14.04.3 LTS "Trusty Tahr" - Beta amd64 
(20150805)
  IwConfig:
   lono wireless extensions.
   
   eth1  no wireless extensions.
   
   eth0  no wireless extensions.
  Lspci:
   
  Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize 
libusb: -99
  MachineType: Microsoft Corporation Virtual Machine
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=C
   SHELL=/bin/bash
  ProcFB: 0 hyperv_fb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-98-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro
  ProcVersionSignature: Ubuntu 4.4.0-98.121~14.04.1-generic 4.4.90
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-98-generic N/A
   linux-backports-modules-4.4.0-98-generic  N/A
   linux-firmware1.127.23
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  trusty
  Uname: Linux 4.4.0-98-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 11/26/2012
  dmi.bios.vendor: Microsoft Corporation
  dmi.bios.version: Hyper-V UEFI Release v1.0
  dmi.board.asset.tag: None
  dmi.board.name: Virtual Machine
  dmi.board.vendor: Microsoft Corporation
  dmi.board.version: Hyper-V UEFI Release v1.0
  dmi.chassis.asset.tag: 0981-0252-2294-8432-2174-6395-64
  dmi.chassis.type: 3
  dmi.chassis.vendor: Microsoft Corporation
  dmi.chassis.version: Hyper-V UEFI Release v1.0
  dmi.modalias: 
dmi:bvnMicrosoftCorporation:bvrHyper-VUEFIReleasev1.0:bd11/26/2012:svnMicrosoftCorporation:pnVirtualMachine:pvrHyper-VUEFIReleasev1.0:rvnMicrosoftCorporation:rnVirtualMachine:rvrHyper-VUEFIReleasev1.0:cvnMicrosoftCorporation:ct3:cvrHyper-VUEFIReleasev1.0:
  dmi.product.name: Virtual Machine
  dmi.product.version: Hyper-V UEFI Release v1.0
  dmi.sys.vendor: Microsoft Corporation
  --- 
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Nov 21 11:15 seq
   crw-rw 1 root audio 116, 33 Nov 21 11:15 timer
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.14.1-0ubuntu3.27
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: Error: [Errno 2] No such file or directory
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=/dev/mapper/ubuntu--vg-swap_1
  InstallationDate: Installed on 2016-02-20 (639 days ago)
  InstallationMedia: Ubuntu-Server 14.04.3 LTS "Trusty Tahr" - Beta amd64 
(20150805)
  IwConfig:
   lono wireless extensions.
   
   eth1  no wireless extensions.
   
   eth0  no wireless extensions.
  Lspci:
   
  Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize 
libusb: -99
  MachineType: Microsoft Corporation Virtual Machine
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=C
   SHELL=/bin/bash
  ProcFB: 0 hyperv_fb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-101-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro
  ProcVersionSignature: Ubuntu 4.4.0-101.124~14.04.1-generic 4.4.95
  

[Kernel-packages] [Bug 1730607] Re: mount cifs with SMB 3.0 stop working

[Andrey Vertexx]

Ubuntu 14.04.5 LTS (GNU/Linux 4.4.0-101-generic x86_64) still have a
problem.

** Description changed:

  I have a Ubuntu Server (14.04.5 LTS (GNU/Linux 4.4.0-98-generic x86_64)) and 
a Windows Server 2012 R2 File Server with a File Share. I mounted a file share 
to my linux server with a cifs-utils.
  Everything worked fine until some kernel update installed on Ubuntu. SMB 3.0 
stopped working and my share not mounted.
  
  sudo mount -t cifs //myserver.xxx.net/WebBackup -o
  username=user,password=P@ssw0rd,domain=xxx.net,vers=3.0 /backupdrive -
  not working
  
  mount error(5): Input/output error
  Refer to the mount.cifs(8) manual page (e.g. man mount.cifs)
  
  if i change to vers=2.1 - it it work
  --- 
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Nov  7 16:11 seq
   crw-rw 1 root audio 116, 33 Nov  7 16:11 timer
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.14.1-0ubuntu3.25
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: Error: [Errno 2] No such file or directory
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=/dev/mapper/ubuntu--vg-swap_1
  InstallationDate: Installed on 2016-02-20 (626 days ago)
  InstallationMedia: Ubuntu-Server 14.04.3 LTS "Trusty Tahr" - Beta amd64 
(20150805)
  IwConfig:
   lono wireless extensions.
   
   eth1  no wireless extensions.
   
   eth0  no wireless extensions.
  Lspci:
   
  Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize 
libusb: -99
  MachineType: Microsoft Corporation Virtual Machine
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=C
   SHELL=/bin/bash
  ProcFB: 0 hyperv_fb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-98-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro
  ProcVersionSignature: Ubuntu 4.4.0-98.121~14.04.1-generic 4.4.90
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-98-generic N/A
   linux-backports-modules-4.4.0-98-generic  N/A
   linux-firmware1.127.23
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  trusty
  Uname: Linux 4.4.0-98-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 11/26/2012
  dmi.bios.vendor: Microsoft Corporation
  dmi.bios.version: Hyper-V UEFI Release v1.0
  dmi.board.asset.tag: None
  dmi.board.name: Virtual Machine
  dmi.board.vendor: Microsoft Corporation
  dmi.board.version: Hyper-V UEFI Release v1.0
  dmi.chassis.asset.tag: 0981-0252-2294-8432-2174-6395-64
  dmi.chassis.type: 3
  dmi.chassis.vendor: Microsoft Corporation
  dmi.chassis.version: Hyper-V UEFI Release v1.0
  dmi.modalias: 
dmi:bvnMicrosoftCorporation:bvrHyper-VUEFIReleasev1.0:bd11/26/2012:svnMicrosoftCorporation:pnVirtualMachine:pvrHyper-VUEFIReleasev1.0:rvnMicrosoftCorporation:rnVirtualMachine:rvrHyper-VUEFIReleasev1.0:cvnMicrosoftCorporation:ct3:cvrHyper-VUEFIReleasev1.0:
  dmi.product.name: Virtual Machine
  dmi.product.version: Hyper-V UEFI Release v1.0
  dmi.sys.vendor: Microsoft Corporation
+ --- 
+ AlsaDevices:
+  total 0
+  crw-rw 1 root audio 116,  1 Nov 21 11:15 seq
+  crw-rw 1 root audio 116, 33 Nov 21 11:15 timer
+ AplayDevices: Error: [Errno 2] No such file or directory
+ ApportVersion: 2.14.1-0ubuntu3.27
+ Architecture: amd64
+ ArecordDevices: Error: [Errno 2] No such file or directory
+ AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
+ CRDA: Error: [Errno 2] No such file or directory
+ DistroRelease: Ubuntu 14.04
+ HibernationDevice: RESUME=/dev/mapper/ubuntu--vg-swap_1
+ InstallationDate: Installed on 2016-02-20 (639 days ago)
+ InstallationMedia: Ubuntu-Server 14.04.3 LTS "Trusty Tahr" - Beta amd64 
(20150805)
+ IwConfig:
+  lono wireless extensions.
+  
+  eth1  no wireless extensions.
+  
+  eth0  no wireless extensions.
+ Lspci:
+  
+ Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize 
libusb: -99
+ MachineType: Microsoft Corporation Virtual Machine
+ Package: linux (not installed)
+ PciMultimedia:
+  
+ ProcEnviron:
+  TERM=xterm
+  PATH=(custom, no user)
+  LANG=C
+  SHELL=/bin/bash
+ ProcFB: 0 hyperv_fb
+ ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-101-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro
+ ProcVersionSignature: Ubuntu 4.4.0-101.124~14.04.1-generic 4.4.95
+ RelatedPackageVersions:
+  linux-restricted-modules-4.4.0-101-generic N/A
+  linux-backports-modules-4.4.0-101-generic  N/A
+  linux-firmware 1.127.23
+ RfKill: Error: [Errno 2] No such file or directory
+ Tags:  trusty trusty
+ Uname: Linux 4.4.0-101-generic x86_64
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups:
+  
+ 

[Kernel-packages] [Bug 1731091] Re: The HDMI audio can't work on all Geminilake machines we have (Dell laptops or desktops)

[Hui Wang]

** Changed in: linux-oem (Ubuntu)
   Importance: Undecided => Critical

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

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

** Changed in: linux-oem (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/1731091

Title:
  The HDMI audio can't work on all Geminilake machines we have (Dell
  laptops or desktops)

Status in HWE Next:
  Fix Committed
Status in linux package in Ubuntu:
  Fix Committed
Status in linux-oem package in Ubuntu:
  Fix Committed

Bug description:
  I have filed a bugzilla bug to track this issue:
  https://bugzilla.kernel.org/show_bug.cgi?id=197785

  We have several Geminilake laptop and desktop machines, on these 
  machines, the HW configs are same and are as shown below:

  the HDA controller: 00:0e.0 Audio device [0403]: Intel Corporation 
  Device [8086:3198] (rev 01)
  the HDMI codec: Vendor Id: 0x8086280d
  VGA controller: 00:02.0 VGA compatible controller [0300]: Intel 
  Corporation Device [8086:3184] (rev 01) (prog-if 00 [VGA controller])

  The problem is if we boot the system without plugging the HDMI monitor, 
  the Linux kernel can't find HDMI codec at all. If we plug the HDMI 
  monitor before booting up, the kernel can find the HDMI codec, but there 
  are many errors (as shown below) and the HDMI audio can't play any sound.

  Codec: Intel Geminilake HDMI
  Address: 2
  AFG Function Id: 0x1 (unsol 0)
  Vendor Id: 0x8086280d
  Subsystem Id: 0x80860101
  Revision Id: 0x10
  No Modem Function Group found
  Default PCM:
  N/A
  Default Amp-In caps: N/A
  Default Amp-Out caps: N/A
  State of AFG node 0x01:
 Power: setting=UNKNOWN, actual=UNKNOWN, Error, Clock-stop-OK, 
  Setting-reset
  Invalid AFG subtree
  --endcollapse--

  [   25.504069] snd_hda_intel :00:0e.0: azx_get_response timeout, 
  switching to polling mode: last cmd=0x20bf8100
  [   26.516125] snd_hda_intel :00:0e.0: No response from codec, 
  disabling MSI: last cmd=0x20bf8100
  [   27.528058] snd_hda_intel :00:0e.0: azx_get_response timeout, 
  switching to single_cmd mode: last cmd=0x20bf8100
  [   27.528259] azx_single_wait_for_response: 12 callbacks suppressed
  [   27.547927] snd_hda_codec_hdmi hdaudioC0D2: Unable to sync register 
  0x2f0d00. -5

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1731091/+subscriptions

-- 
Mailing list: https://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 1730261] Re: Reading HDA audio capability register crashes the kernel

[Hui Wang]

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

** Changed in: hwe-next
   Status: Confirmed => 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/1730261

Title:
  Reading HDA audio capability register crashes the kernel

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

Bug description:
  The intel audio device [8086:a348] can not be driven.

  I got below error message.
  [ 14.154439] snd_hda_core: loading out-of-tree module taints kernel.
  [ 14.154474] snd_hda_core: module verification failed: signature and/or 
required key missing - tainting kernel
  [ 14.170181] snd_hda_intel :00:1f.3: Probing card using HDA DKMS, version 
0.201710050116~ubuntu17.10.1
  [ 14.170192] snd_hda_intel :00:1f.3: enabling device (0100 -> 0102)
  [ 14.170344] snd_hda_intel :00:1f.3: bound :00:02.0 (ops 
i915_audio_component_bind_ops [i915])
  [ 14.170359] sdhci-pci :00:14.5: SDHCI controller found [8086:a375] (rev 
1)
  [ 14.192693] BUG: unable to handle kernel paging request at a73f43d8
  [ 14.192697] IP: pci_azx_readl+0x9/0x10 [snd_hda_intel]
  [ 14.192698] PGD 80ad3a067
  [ 14.192698] P4D 80ad3a067
  [ 14.192698] PUD 80ad3b067
  [ 14.192699] PMD 7fe2ef067
  [ 14.192699] PTE 0

  [ 14.192701] Oops:  [#1] SMP
  [ 14.192702] Modules linked in: snd_hda_intel(OE) snd_hda_codec(OE) 
snd_hda_core(OE) kvm irqbypass snd_hwdep btusb btrtl btbcm btintel snd_pcm 
bluetooth ecdh_generic crct10dif_pclmul crc32_pclmul ghash_clmulni_intel pcbc 
snd_seq_midi snd_seq_midi_event aesni_intel snd_rawmidi rtsx_pci_ms memstick 
ucsi_acpi snd_seq snd_seq_device snd_timer wmi_bmof dell_wmi_aio aes_x86_64 
crypto_simd glue_helper cryptd dell_wmi dell_smbios dcdbas snd intel_cstate 
typec_ucsi sparse_keymap shpchp intel_rapl_perf soundcore typec tpm_crb mac_hid 
acpi_als kfifo_buf industrialio acpi_pad parport_pc ppdev lp parport autofs4 
btrfs xor raid6_pq dm_mirror dm_region_hash dm_log hid_generic usbhid 
rtsx_pci_sdmmc i915 i2c_algo_bit drm_kms_helper syscopyarea sysfillrect 
sysimgblt e1000e fb_sys_fops ptp drm pps_core ahci sdhci_pci
  [ 14.192719] rtsx_pci libahci sdhci wmi i2c_hid hid video
  [ 14.192722] CPU: 6 PID: 96 Comm: kworker/6:1 Tainted: G OE 4.13.0-1005-oem 
#6-Ubuntu
  [ 14.192723] Hardware name: Dell Inc. OptiPlex 7450 AIO/03CDJK, BIOS 96.0.2 
08/08/2017
  [ 14.192725] Workqueue: events azx_probe_work [snd_hda_intel]
  [ 14.192726] task: 8abb068697c0 task.stack: a73f4351
  [ 14.192727] RIP: 0010:pci_azx_readl+0x9/0x10 [snd_hda_intel]
  [ 14.192728] RSP: 0018:a73f43513db0 EFLAGS: 00010286
  [ 14.192729] RAX: c07fddc0 RBX: 0fff RCX: 000e1233
  [ 14.192729] RDX: 0100 RSI: 0100 RDI: a73f43d8
  [ 14.192730] RBP: a73f43513db0 R08: c73f3fff R09: 8abb0ac03601
  [ 14.192730] R10: 0ac03601 R11: 4001 R12: 
  [ 14.192731] R13:  R14: 8abb030db000 R15: 
  [ 14.192732] FS: () GS:8abb0b38() 
knlGS:
  [ 14.192733] CS: 0010 DS:  ES:  CR0: 80050033
  [ 14.192733] CR2: a73f43d8 CR3: 0001dea09000 CR4: 003406e0
  [ 14.192734] DR0:  DR1:  DR2: 
  [ 14.192735] DR3:  DR6: fffe0ff0 DR7: 0400
  [ 14.192735] Call Trace:
  [ 14.192738] snd_hdac_bus_parse_capabilities+0x44/0x1f0 [snd_hda_core]
  [ 14.192740] azx_probe_continue+0x75e/0xa30 [snd_hda_intel]
  [ 14.192742] azx_probe_work+0x15/0x20 [snd_hda_intel]
  [ 14.192744] process_one_work+0x156/0x410
  [ 14.192745] worker_thread+0x4b/0x410
  [ 14.192746] kthread+0x109/0x140
  [ 14.192747] ? process_one_work+0x410/0x410
  [ 14.192748] ? kthread_create_on_node+0x70/0x70
  [ 14.192750] ret_from_fork+0x25/0x30
  [ 14.192751] Code: 88 00 05 00 00 04 31 c0 5d c3 0f 1f 84 00 00 00 00 00 0f 
1f 44 00 00 55 48 89 e5 89 3e 5d c3 0f 1f 00 0f 1f 44 00 00 55 48 89 e5 <8b> 07 
5d c3 0f 1f 00 0f 1f 44 00 00 55 48 89 e5 66 89 3e 5d c3
  [ 14.192766] RIP: pci_azx_readl+0x9/0x10 [snd_hda_intel] RSP: a73f43513db0
  [ 14.192766] CR2: a73f43d8
  [ 14.192767] ---[ end trace 7bab59b956c17279 ]---

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1730261/+subscriptions

-- 
Mailing list: https://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 1729500] Re: headset mic can't work on laptops with the codec alc236

[Hui Wang]

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

** Changed in: hwe-next
   Status: Confirmed => 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/1729500

Title:
  headset mic can't work on laptops with the codec alc236

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

Bug description:
  Summary: system can't detect external microphone

  Steps:
  1. install manifest and boot into OS
  2. plug an external microphone to system
  3. check external microphone status

  Expected results: system should able to detect external microphone

  Actual results: system can't detect external microphone

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1729500/+subscriptions

-- 
Mailing list: https://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 1733194] Re: kernel NULL pointer dereference in iwlmvm iwl_mvm_enable_txq

[munin]

I upgraded from 16.04, where I was not having this issue. I think that
was running 4.10?

I tested with the upstream kernel, and the problem persists. Here is a
backtrace from dmesg:

[Mon Nov 20 21:22:24 2017] BUG: unable to handle kernel NULL pointer 
dereference at 0070
[Mon Nov 20 21:22:24 2017] IP: iwl_trans_pcie_txq_enable+0x62/0x440 [iwlwifi]
[Mon Nov 20 21:22:24 2017] PGD 0 P4D 0
[Mon Nov 20 21:22:24 2017] Oops: 0002 [#1] SMP
[Mon Nov 20 21:22:24 2017] Modules linked in: ufs qnx4 hfsplus hfs minix ntfs 
msdos jfs xfs ccm xfrm_user xfrm4_tunnel tunnel4 ipcomp xfrm_ipcomp esp4 ah4 
af_key xfrm_algo xt_policy xt_multiport ip6table_filter ip6_tables 
ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_nat_ipv4 nf_nat ipt_REJECT 
nf_reject_ipv4 xt_tcpudp nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack 
nf_conntrack iptable_filter nls_iso8859_1 arc4 cmdlinepart intel_spi_platform 
intel_spi spi_nor mtd intel_rapl intel_soc_dts_thermal intel_soc_dts_iosf 
intel_powerclamp coretemp kvm_intel bridge stp llc kvm snd_hda_codec_hdmi 
iwlmvm irqbypass mac80211 snd_hda_codec_realtek snd_hda_codec_generic 
punit_atom_debug iwlwifi intel_cstate cfg80211 lpc_ich snd_intel_sst_acpi 
snd_hda_intel btusb snd_intel_sst_core snd_hda_codec btrtl 
snd_soc_sst_atom_hifi2_platform
[Mon Nov 20 21:22:24 2017]  snd_hda_core hci_uart snd_soc_sst_match snd_hwdep 
btbcm serdev snd_soc_core mei_txe btqca btintel shpchp mei snd_compress 
bluetooth ac97_bus snd_pcm_dmaengine snd_pcm dw_dmac ecdh_generic dw_dmac_core 
snd_timer rfkill_gpio snd intel_int0002_vgpio mac_hid soundcore 8250_dw 
spi_pxa2xx_platform pwm_lpss_platform pwm_lpss ib_iser rdma_cm iw_cm ib_cm 
ib_core iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi ip_tables x_tables 
autofs4 btrfs zstd_compress raid10 raid456 async_raid6_recov async_memcpy 
async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear 
i915 crct10dif_pclmul drm_kms_helper igb crc32_pclmul syscopyarea sysfillrect 
dca ghash_clmulni_intel sysimgblt fb_sys_fops cryptd ptp pps_core drm 
i2c_algo_bit ahci libahci video i2c_hid sdhci_acpi hid sdhci
[Mon Nov 20 21:22:24 2017] CPU: 3 PID: 585 Comm: kworker/3:2 Tainted: G
W   4.14.0-041400-generic #201711122031
[Mon Nov 20 21:22:24 2017] Hardware name: NF541 NF541/NF541, BIOS BAR1NA02 
02/25/2016
[Mon Nov 20 21:22:24 2017] Workqueue: events iwl_mvm_add_new_dqa_stream_wk 
[iwlmvm]
[Mon Nov 20 21:22:24 2017] task: 9939ebd4d700 task.stack: b8ed813c8000
[Mon Nov 20 21:22:24 2017] RIP: 0010:iwl_trans_pcie_txq_enable+0x62/0x440 
[iwlwifi]
[Mon Nov 20 21:22:24 2017] RSP: 0018:b8ed813cbc00 EFLAGS: 00010246
[Mon Nov 20 21:22:24 2017] RAX: 09c4 RBX: 001f RCX: 

[Mon Nov 20 21:22:24 2017] RDX:  RSI: 001f RDI: 
2710
[Mon Nov 20 21:22:24 2017] RBP: b8ed813cbc50 R08: 2710 R09: 
0001
[Mon Nov 20 21:22:24 2017] R10:  R11: 9939edd4e010 R12: 

[Mon Nov 20 21:22:24 2017] R13: 9939f0a80018 R14:  R15: 

[Mon Nov 20 21:22:24 2017] FS:  () 
GS:9939ffd8() knlGS:
[Mon Nov 20 21:22:24 2017] CS:  0010 DS:  ES:  CR0: 80050033
[Mon Nov 20 21:22:24 2017] CR2: 0070 CR3: 0002302c4000 CR4: 
001006e0
[Mon Nov 20 21:22:24 2017] Call Trace:
[Mon Nov 20 21:22:24 2017]  iwl_mvm_enable_txq+0x212/0x3a0 [iwlmvm]
[Mon Nov 20 21:22:24 2017]  iwl_mvm_add_new_dqa_stream_wk+0x809/0x1690 [iwlmvm]
[Mon Nov 20 21:22:24 2017]  ? iwl_mvm_add_new_dqa_stream_wk+0x809/0x1690 
[iwlmvm]
[Mon Nov 20 21:22:24 2017]  ? update_load_avg+0x429/0x590
[Mon Nov 20 21:22:24 2017]  ? __switch_to+0x1f3/0x4e0
[Mon Nov 20 21:22:24 2017]  process_one_work+0x1e7/0x410
[Mon Nov 20 21:22:24 2017]  worker_thread+0x32/0x410
[Mon Nov 20 21:22:24 2017]  kthread+0x125/0x140
[Mon Nov 20 21:22:24 2017]  ? process_one_work+0x410/0x410
[Mon Nov 20 21:22:24 2017]  ? kthread_create_on_node+0x70/0x70
[Mon Nov 20 21:22:24 2017]  ret_from_fork+0x25/0x30
[Mon Nov 20 21:22:24 2017] Code: 4c 8b b4 c7 08 7e 00 00 f0 48 0f ab 87 08 8e 
00 00 73 0d 80 3d 76 7b 02 00 00 0f 84 a1 03 00 00 44 89 c7 e8 f1 3f 05 ce 4d 
85 e4 <49> 89 46 70 0f 84 d9 02 00 00 41 0f b6 04 24 89 45 b8 41 0f b6
[Mon Nov 20 21:22:24 2017] RIP: iwl_trans_pcie_txq_enable+0x62/0x440 [iwlwifi] 
RSP: b8ed813cbc00
[Mon Nov 20 21:22:24 2017] CR2: 0070
[Mon Nov 20 21:22:24 2017] ---[ end trace 4d628638dc7f89b5 ]---

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

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

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

Title:
  kernel NULL pointer dereference in iwlmvm iwl_mvm_enable_txq

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  When in AP mode after 

[Kernel-packages] [Bug 1730305] Re: 17.10 boot failure on Lenovo ThinkStation S30

[Alvin Cao]

Hi.

linux-image-4.11.12-041112-generic_4.11.12-041112.201707210350_amd64.deb
worked while linux-
image-4.12.14-041214-generic_4.12.14-041214.201709200843_amd64.deb
failed. Both kernels are the latest build in their major series. So this
bug was introduced in v4.12.

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

Title:
  17.10 boot failure on Lenovo ThinkStation S30

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  This a boot failure(100%) so I cannot provide most information.

  1. I tried upgrading from 17.04, the new kernel 4.13 kernel failed to
  boot but the 4.10 kernel still did. 17.10 could run on kernel 4.10.

  2. Then I tried doing a fresh installation of 17.10. The same result.

  I cannot get the log in text since it's early stage. I attached a
  screen shot of kernel log.

  I think the kernel version is linux-
  image-4.13.0-16-generic_4.13.0-16.19_amd64.deb

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

-- 
Mailing list: https://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 1692538] Re: Ubuntu 16.04.02: ibmveth: Support to enable LSO/CSO for Trunk VEA

[Daniel Axtens]

Hi Siva,

Thank you for your quick and thoughtful response.

I will ask about the default MTU for the veth interface to see if the
user increased it themselves.

I'm not sure I completely understand what you mean about largesend
offload being disabled after retransmits. I'm also not completely sure
if it's largesend offload or just large packets that are causing issues.
If I have understood correctly (e.g.
https://www.ibm.com/support/knowledgecenter/en/ssw_aix_72/com.ibm.aix.performance/tcp_large_send_offload.htm)
large-send offload is what Linux would call TCP Segmentation Offload
(TSO) - does that match your understanding?

Here's my concern. The code I'm looking at (let's look at Zesty, so
v4.10) is in ibmveth.c, ibmveth_poll(). There we see:

 if (length > netdev->mtu + ETH_HLEN) {
ibmveth_rx_mss_helper(skb, mss, lrg_pkt);
adapter->rx_large_packets++;
 }

Then ibmveth_rx_mss_helper() has the following - setting GSO on
regardless of the large_pkt bit:

 /* if mss is not set through Large Packet bit/mss in rx buffer,
  * expect that the mss will be written to the tcp header checksum.
  */
 tcph = (struct tcphdr *)(skb->data + offset);
 if (lrg_pkt) {
skb_shinfo(skb)->gso_size = mss;
 } else if (offset) {
skb_shinfo(skb)->gso_size = ntohs(tcph->check);
tcph->check = 0;
 }

It looks to me that Linux will interpret a packet from the veth adaptor
as a GSO/GRO packet based only on whether or not the size of the
received packet is greater than the linux-side MTU plus the header size
- not based on whether AIX thinks it is transmitting a LSO packet.

To put it another way - if I have understood correctly - there are two
ways we could end up with a GSO/GRO packet coming out of a veth adaptor.
The ibmveth_rx_mss_helper path is taken when the size of the packet is
greater than MTU+ETH_HLEN, which can happen when:

 1) The AIX end has turned on LSO, so the large_packet bit is set
 2) Large-send is off in AIX but there is a mis-matched MTU between AIX and 
Linux

In the first case case, you say that AIX will turn off largesend, which
will fix the issue. But in the second case, if I have understood
correctly, AIX will not be able to do anything. Unless you are saying
that AIX will dynamically reduce the MTU for a connection in the
presence of a number of re-transmits?

This isn't necessarily wrong behaviour from AIX - Linux can't do
anything in this situation either; a 'hop' that can participate in Path
MTU Discovery would be needed.

If I understand it, then, the optimal configuration would be for the AIX
LPAR to set an MTU of 1500/9000 and turn on LSO for veth on the AIX side
- does that sound right?

Thanks again!
Regards,
Daniel

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

Title:
  Ubuntu 16.04.02: ibmveth: Support to enable LSO/CSO for Trunk VEA

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

Bug description:
  
  == SRU Justification ==
  Commit 66aa0678ef is request to fix four issues with the ibmveth driver.
  The issues are as follows:
  - Issue 1: ibmveth doesn't support largesend and checksum offload features 
when configured as "Trunk".
  - Issue 2: SYN packet drops seen at destination VM. When the packet
  originates, it has CHECKSUM_PARTIAL flag set and as it gets delivered to IO
  server's inbound Trunk ibmveth, on validating "checksum good" bits in ibmveth
  receive routine, SKB's ip_summed field is set with CHECKSUM_UNNECESSARY flag.
  - Issue 3: First packet of a TCP connection will be dropped, if there is
  no OVS flow cached in datapath.
  - Issue 4: ibmveth driver doesn't have support for SKB's with frag_list.

  The details for the fixes to these issues are described in the commits
  git log.



  == Comment: #0 - BRYANT G. LY  - 2017-05-22 08:40:16 ==
  ---Problem Description---

   - Issue 1: ibmveth doesn't support largesend and checksum offload features
     when configured as "Trunk". Driver has explicit checks to prevent
     enabling these offloads.

   - Issue 2: SYN packet drops seen at destination VM. When the packet
     originates, it has CHECKSUM_PARTIAL flag set and as it gets delivered to
     IO server's inbound Trunk ibmveth, on validating "checksum good" bits
     in ibmveth receive routine, SKB's ip_summed field is set with
     CHECKSUM_UNNECESSARY flag. This packet is then bridged by OVS (or Linux
     Bridge) and delivered to outbound Trunk ibmveth. At this point the
     outbound ibmveth transmit routine will not set "no checksum" and
     "checksum good" bits in transmit buffer descriptor, as it does so only
     when the ip_summed field is CHECKSUM_PARTIAL. When this 

[Kernel-packages] [Bug 1724911] Re: text VTs are unavailable on desktop after upgrade to Ubuntu 17.10

[Steve Langasek]

fb4e3beeffa47619985f190663c6ef424f063a22 is good.

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

Title:
  text VTs are unavailable on desktop after upgrade to Ubuntu 17.10

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

Bug description:
  After upgrading my laptop to Ubuntu 17.10, I am unable to access
  gettys on any of the text-mode VTs on my system.

  gdm3 is running on VT1, my user session is running on VT2.  I can
  switch between these.  If I switch to VT3, I know that the VT switch
  has happened in the kernel because the X cursor disappears; but the
  display retains the output of my X session, and the text console with
  getty never appears.

  Switching back to VT2 works fine.

  The same problem occurs with either Wayland or X.

  My laptop is docked with an external monitor, which could be a factor.
  (I also notice that during boot, plymouth is only rendered on the
  internal monitor, not the external monitor; this may be related).  I
  have not yet tested whether this problem is reproducible if I undock.

  The system is booting with vt.handoff=7, which I believe is still the
  default in Ubuntu 17.10.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-16-generic 4.13.0-16.19
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  vorlon24080 F pulseaudio
   /dev/snd/controlC0:  vorlon24080 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct 19 09:57:59 2017
  HibernationDevice: RESUME=UUID=6df76279-19ea-45a4-bec9-e4fdc858729a
  InstallationDate: Installed on 2010-09-24 (2582 days ago)
  InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release amd64 
(20100816.1)
  MachineType: LENOVO 2306CTO
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-16-generic.efi.signed 
root=/dev/mapper/hostname-root ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-16-generic N/A
   linux-backports-modules-4.13.0-16-generic  N/A
   linux-firmware 1.169
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: Upgraded to artful on 2017-10-19 (0 days ago)
  dmi.bios.date: 10/25/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G2ET97WW (2.57 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 2306CTO
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrG2ET97WW(2.57):bd10/25/2013:svnLENOVO:pn2306CTO:pvrThinkPadX230:rvnLENOVO:rn2306CTO:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad X230
  dmi.product.name: 2306CTO
  dmi.product.version: ThinkPad X230
  dmi.sys.vendor: LENOVO

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

-- 
Mailing list: https://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 1731971] Re: Artful update to 4.13.12 stable release

[Ubuntu QA Website]

This bug has been reported on the Ubuntu ISO testing tracker.

A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/1731971

** Tags added: iso-testing

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

Title:
  Artful update to 4.13.12 stable release

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

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.13.12 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.13.12 stable release shall be applied:
  * ALSA: timer: Add missing mutex lock for compat ioctls
  * ALSA: seq: Fix nested rwsem annotation for lockdep splat
  * cifs: check MaxPathNameComponentLength != 0 before using it
  * KEYS: return full count in keyring_read() if buffer is too small
  * KEYS: trusted: fix writing past end of buffer in trusted_read()
  * KEYS: fix out-of-bounds read during ASN.1 parsing
  * ASoC: adau17x1: Workaround for noise bug in ADC
  * virtio_blk: Fix an SG_IO regression
  * arm64: ensure __dump_instr() checks addr_limit
  * KVM: arm64: its: Fix missing dynamic allocation check in scan_its_table
  * arm/arm64: KVM: set right LR register value for 32 bit guest when inject
abort
  * arm/arm64: kvm: Disable branch profiling in HYP code
  * ARM: dts: mvebu: pl310-cache disable double-linefill
  * ARM: 8715/1: add a private asm/unaligned.h
  * drm/amdgpu: return -ENOENT from uvd 6.0 early init for harvesting
  * drm/amdgpu: allow harvesting check for Polaris VCE
  * userfaultfd: hugetlbfs: prevent UFFDIO_COPY to fill beyond the end of
i_size
  * ocfs2: fstrim: Fix start offset of first cluster group during fstrim
  * fs/hugetlbfs/inode.c: fix hwpoison reserve accounting
  * mm, swap: fix race between swap count continuation operations
  * drm/i915: Do not rely on wm preservation for ILK watermarks
  * drm/i915/edp: read edp display control registers unconditionally
  * Revert "powerpc64/elfv1: Only dereference function descriptor for non-text
symbols"
  * MIPS: bpf: Fix a typo in build_one_insn()
  * MIPS: smp-cmp: Use right include for task_struct
  * MIPS: microMIPS: Fix incorrect mask in insn_table_MM
  * MIPS: SMP: Fix deadlock & online race
  * Revert "x86: do not use cpufreq_quick_get() for /proc/cpuinfo "cpu MHz""
  * x86: CPU: Fix up "cpu MHz" in /proc/cpuinfo
  * powerpc/kprobes: Dereference function pointers only if the address does not
belong to kernel text
  * futex: Fix more put_pi_state() vs. exit_pi_state_list() races
  * perf/cgroup: Fix perf cgroup hierarchy support
  * x86/mcelog: Get rid of RCU remnants
  * irqchip/irq-mvebu-gicp: Add missing spin_lock init
  * Linux 4.13.12

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

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

[Kernel-packages] [Bug 1655842] Re: "Out of memory" errors after upgrade to 4.4.0-59

[William DeLuca]

We believe that we are experiencing this issue on kernel 4.4.0-1030-aws
as well. We recently move from 14 LTS to 16LTS and are now experience
oom kills.

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

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

Status in linux package in Ubuntu:
  Fix Released
Status in linux-aws package in Ubuntu:
  Confirmed
Status in linux-raspi2 package in Ubuntu:
  Fix Committed
Status in linux source package in Xenial:
  Fix Released
Status in linux-aws source package in Xenial:
  Confirmed
Status in linux-raspi2 source package in Xenial:
  Fix Committed

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

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

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

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

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

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-59-generic 4.4.0-59.80
  ProcVersionSignature: User Name 4.4.0-59.80-generic 4.4.35
  Uname: Linux 4.4.0-59-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Jan 12 06:29 seq
   crw-rw 1 root audio 116, 33 Jan 12 06:29 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.1-0ubuntu2.4
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  Date: Thu Jan 12 06:38:45 2017
  Ec2AMI: ami-0f93966c
  Ec2AMIManifest: (unknown)
  Ec2AvailabilityZone: ap-southeast-2a
  Ec2InstanceType: t2.nano
  Ec2Kernel: unavailable
  Ec2Ramdisk: unavailable
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  MachineType: Xen HVM domU
  PciMultimedia:

  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 cirrusdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-59-generic 
root=UUID=fb0fef08-f3c5-40bf-9776-f7ba00fe72be ro console=tty1 console=ttyS0
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-59-generic N/A
   linux-backports-modules-4.4.0-59-generic  N/A
   linux-firmware1.157.6
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/09/2016
  dmi.bios.vendor: Xen
  dmi.bios.version: 4.2.amazon
  dmi.chassis.type: 1
  dmi.chassis.vendor: Xen
  dmi.modalias: 
dmi:bvnXen:bvr4.2.amazon:bd12/09/2016:svnXen:pnHVMdomU:pvr4.2.amazon:cvnXen:ct1:cvr:
  dmi.product.name: HVM domU
  dmi.product.version: 4.2.amazon
  dmi.sys.vendor: Xen

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

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

[Kernel-packages] [Bug 1733038] 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/1733038

Title:
  freeze

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  freeze

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-98-generic (not installed)
  ProcVersionSignature: Ubuntu 4.4.0-98.121-generic 4.4.90
  Uname: Linux 4.4.0-98-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.12
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   ashish 2171 F...m pulseaudio
   /dev/snd/controlC0:  ashish 2171 F pulseaudio
  CurrentDesktop: Unity
  Date: Sat Nov 18 09:30:02 2017
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-xenial-amd64-20160624-2
  HibernationDevice: RESUME=UUID=c1d38ce9-44c1-4c9c-899d-f4d1efaab9e5
  InstallationDate: Installed on 2017-11-17 (0 days ago)
  InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 
20160624-10:47
  MachineType: Dell Inc. Vostro 14-3468
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-98-generic.efi.signed 
root=UUID=63f0bf97-2f6f-4571-954a-855cc648aa65 ro acpi_rev_override 
locale=en_GB quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-98-generic N/A
   linux-backports-modules-4.4.0-98-generic  N/A
   linux-firmware1.157.13
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/23/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 01.08.00
  dmi.board.name: 0T1X3V
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr01.08.00:bd03/23/2017:svnDellInc.:pnVostro14-3468:pvr:rvnDellInc.:rn0T1X3V:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Vostro 14-3468
  dmi.sys.vendor: Dell Inc.

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

-- 
Mailing list: https://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 1733038] Re: freeze

[Seth Arnold]

** Information type changed from Private Security to Public

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

Title:
  freeze

Status in linux package in Ubuntu:
  New

Bug description:
  freeze

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-98-generic (not installed)
  ProcVersionSignature: Ubuntu 4.4.0-98.121-generic 4.4.90
  Uname: Linux 4.4.0-98-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.12
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   ashish 2171 F...m pulseaudio
   /dev/snd/controlC0:  ashish 2171 F pulseaudio
  CurrentDesktop: Unity
  Date: Sat Nov 18 09:30:02 2017
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-xenial-amd64-20160624-2
  HibernationDevice: RESUME=UUID=c1d38ce9-44c1-4c9c-899d-f4d1efaab9e5
  InstallationDate: Installed on 2017-11-17 (0 days ago)
  InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 
20160624-10:47
  MachineType: Dell Inc. Vostro 14-3468
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-98-generic.efi.signed 
root=UUID=63f0bf97-2f6f-4571-954a-855cc648aa65 ro acpi_rev_override 
locale=en_GB quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-98-generic N/A
   linux-backports-modules-4.4.0-98-generic  N/A
   linux-firmware1.157.13
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/23/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 01.08.00
  dmi.board.name: 0T1X3V
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr01.08.00:bd03/23/2017:svnDellInc.:pnVostro14-3468:pvr:rvnDellInc.:rn0T1X3V:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Vostro 14-3468
  dmi.sys.vendor: Dell Inc.

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

-- 
Mailing list: https://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 1561474] Re: Bluetooth will be disable after resume from suspend on Xenial

[Ubfan]

The bluetooth failure to resume after a suspend seems USB related. The failure 
happens 
about 50% of the time, and when it does, disabling bluetooth and restarting 
fixes
it.
On a Lenovo W520, Ubuntu 16.04, 64 bit, kernel 4.4.0-98-generic, Microsoft 
Sculpt
Comfort BT mouse.

Looking at dmesg|tail on the restoring of BT mouse after sleep and restarting
it, a new USB device is created and used.

Return from sleep, BT indicator greyed, BT says OFF, BT mouse is inactive.
>From the indicator, start BT settings, and from the settings, turn off 
>bluetooth,
(indicator disappears), one line is added to dmesg output:

[37331.845034] usb 1-1.4: USB disconnect, device number 10


>From the settings, turn back on the BT active switch (BT indicator appears):

[37353.288616] usb 1-1.4: new full-speed USB device number 11 using ehci-pci
[37353.386069] usb 1-1.4: New USB device found, idVendor=0a5c, idProduct=217f
[37353.386079] usb 1-1.4: New USB device strings: Mfr=1, Product=2, 
SerialNumber=3
[37353.386084] usb 1-1.4: Product: Broadcom Bluetooth Device
[37353.386089] usb 1-1.4: Manufacturer: Broadcom Corp
[37353.386092] usb 1-1.4: SerialNumber: 60D819B1B675
[37353.578455] [UFW BLOCK] IN=wlp3s0 OUT= 
MAC=01:00:5e:00:00:01:c0:56:27:ce:27:3e:08:00 
SRC=192.168.1.1 DST=224.0.0.1 LEN=28 TOS=0x00 PREC=0xC0 TTL=1 ID=61239 
PROTO=2 

Note the USB device number 10 was disconnected, but the new USB device is 11.
BT indicator is still greyed, BT switch is off, mouse inactive. Turn on BT in 
the indicator
Indicator becomes white.
Absolutely no change in the dmesg output


Click/move mouse to connect, lock shows on BT indicator

[37414.788430] hid-generic 0005:045E:07A2.0012: unknown main item tag 0x0
[37414.789070] input: Microsoft Sculpt Comfort Mouse as 
/devices/pci:00/:00:1a.0
  
/usb1/1-1/1-1.4/1-1.4:1.0/bluetooth/hci0/hci0:11/0005:045E:07A2.0012/input/input32
[37414.789676] hid-generic 0005:045E:07A2.0012: input,hidraw2: BLUETOOTH HID 
v1.29 Mouse
  [Microsoft Sculpt Comfort Mouse] on 60:d8:19:b1:b6:75

Note the USB device has incremented to input32  (this has happened many times 
on this running system)

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

Title:
  Bluetooth will be disable after resume from suspend on Xenial

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  CID: 201208-11536 Dell Latitude 6430u

  The Bluetooth will be disabled after resume from suspend.
  You will need to use "hciconfig hci0 reset" to enable it.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-15-generic 4.4.0-15.31
  ProcVersionSignature: Ubuntu 4.4.0-15.31-generic 4.4.6
  Uname: Linux 4.4.0-15-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 1202 F pulseaudio
  CurrentDesktop: Unity
  Date: Thu Mar 24 19:14:07 2016
  HibernationDevice: RESUME=UUID=25c03762-079c-4c6d-aedb-ec768318a6bf
  InstallationDate: Installed on 2016-03-24 (0 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20151209)
  MachineType: Dell Inc. Latitude 6430U
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-15-generic 
root=UUID=18cfda3e-4f3d-40cf-8e7e-a83030819487 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-15-generic N/A
   linux-backports-modules-4.4.0-15-generic  N/A
   linux-firmware1.157
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/15/2012
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A02
  dmi.board.asset.tag: 1234567
  dmi.board.name: 0MN74V
  dmi.board.vendor: Dell Inc.
  dmi.board.version: X01
  dmi.chassis.asset.tag: 1234567
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA02:bd11/15/2012:svnDellInc.:pnLatitude6430U:pvr01:rvnDellInc.:rn0MN74V:rvrX01:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude 6430U
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

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

-- 
Mailing list: https://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 1732804] Re: [Zesty/Artful] On ARM64 PCIE physical function passthrough guest fails to boot

[Manoj Iyer]

** Changed in: linux (Ubuntu)
 Assignee: Manoj Iyer (manjo) => Canonical Kernel Team 
(canonical-kernel-team)

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

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

Title:
  [Zesty/Artful] On ARM64 PCIE physical function passthrough guest fails
  to boot

Status in linux package in Ubuntu:
  In Progress

Bug description:
  [Impact]
  Passing through a physical function like the Mellanox PCIE ethernet 
controller causes the guest to fail booting, and host reports Hardware Error.
  == Host ==
  [109920.834703] {1}[Hardware Error]: Hardware error from APEI Generic 
Hardware Error Source: 4
  [109920.842142] {1}[Hardware Error]: event severity: recoverable
  [109920.847848] {1}[Hardware Error]:  precise tstamp: 2017-11-16 23:20:05
  [109920.854385] {1}[Hardware Error]:  Error 0, type: recoverable
  [109920.860111] {1}[Hardware Error]:   section_type: PCIe error
  [109920.865718] {1}[Hardware Error]:   port_type: 0, PCIe end point
  [109920.871708] {1}[Hardware Error]:   version: 3.0
  [109920.876343] {1}[Hardware Error]:   command: 0x0006, status: 0x0010
  [109920.882559] {1}[Hardware Error]:   device_id: :01:00.0
  [109920.888113] {1}[Hardware Error]:   slot: 0
  [109920.892285] {1}[Hardware Error]:   secondary_bus: 0x00
  [109920.897489] {1}[Hardware Error]:   vendor_id: 0x15b3, device_id: 0x1013
  [109920.904172] {1}[Hardware Error]:   class_code: 02
  [109920.909378] vfio-pci :01:00.0: aer_status: 0x0004, aer_mask: 
0x
  [109920.916675] Malformed TLP
  [109920.916678] vfio-pci :01:00.0: aer_layer=Transaction Layer, 
aer_agent=Receiver ID
  [109920.924573] vfio-pci :01:00.0: aer_uncor_severity: 0x00062010
  [109920.930736] vfio-pci :01:00.0:   TLP Header: 4a008040 0100 
0100 
  [109920.938548] vfio-pci :01:00.0: broadcast error_detected message
  [109921.965056] pcieport :00:00.0: downstream link has been reset
  [109921.965062] vfio-pci :01:00.0: broadcast mmio_enabled message
  [109921.965066] vfio-pci :01:00.0: broadcast resume message
  [109921.965070] vfio-pci :01:00.0: AER: Device recovery successful
  == Guest ==
  EFI stub: Booting Linux Kernel...
  EFI stub: EFI_RNG_PROTOCOL unavailable, no randomness supplied
  EFI stub: Using DTB from configuration table
  EFI stub: Exiting boot services and installing virtual address map...
  [1.518252] kvm [1]: HYP mode not available
  [2.578929] mlx5_core :05:00.0: mlx5_core_set_issi:778:(pid 152): 
Failed to query ISSI err(-1) status(0) synd(0)
  [2.582424] mlx5_core :05:00.0: failed to set issi
  [2.616756] mlx5_core :05:00.0: mlx5_load_one failed with error code -1

  This is because, virtualization of physical functions are broken on
  systems with Maximum Payload Size bigger than 128. QDF2400 FW tries to
  maximize this setting. We have observed an MPS of 512 on QDF2400
  systems.

  [Fix]
  Patches are in linux-next:
  523184972b28 vfio/pci: Virtualize Maximum Payload Size
  cf0d53ba4947 vfio/pci: Virtualize Maximum Read Request Size

  [Testing]
  With the above patches applied the guest is able to boot when PCIE physical 
function is passthrough and we don't see the errors on the host system.
  == On the Guest ==
  ubuntu@ubuntu-pcitest:~$ lspci
  00:00.0 Host bridge: Red Hat, Inc. Device 0008
  00:01.0 PCI bridge: Red Hat, Inc. Device 000c
  00:01.1 PCI bridge: Red Hat, Inc. Device 000c
  00:01.2 PCI bridge: Red Hat, Inc. Device 000c
  00:01.3 PCI bridge: Red Hat, Inc. Device 000c
  00:01.4 PCI bridge: Red Hat, Inc. Device 000c
  00:01.5 PCI bridge: Red Hat, Inc. Device 000c
  01:00.0 Ethernet controller: Red Hat, Inc Virtio network device (rev 01)
  02:00.0 Communication controller: Red Hat, Inc Virtio console (rev 01)
  03:00.0 SCSI storage controller: Red Hat, Inc Virtio block device (rev 01)
  04:00.0 SCSI storage controller: Red Hat, Inc Virtio block device (rev 01)
  05:00.0 Ethernet controller: Mellanox Technologies MT27700 Family [ConnectX-4]

  ubuntu@ubuntu-pcitest:~$ lsmod | grep mlx
  mlx5_core 471040 0
  devlink 36864 1 mlx5_core
  ptp 28672 1 mlx5_core

  [Regression Potential]
  Two patches to drivers/vfio/pci were cleanly cherry picked from linux-next 
and applied to Artful/Zesty. Tested on ARM64 QDF2400 system and no regressions 
were found.

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

-- 
Mailing list: https://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 1732990] Re: [Artful/Zesty] ACPI APEI error handling bug fixes

[Manoj Iyer]

** Changed in: linux (Ubuntu)
 Assignee: Manoj Iyer (manjo) => Canonical Kernel Team 
(canonical-kernel-team)

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

Title:
  [Artful/Zesty] ACPI APEI error handling bug fixes

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  [Impact]
  Error records which have multiple errors in them will incorrectly report all 
errors after the first one. This results in garbage non-standard error trace 
events to be generated, and for AER and MC errors there will be no kernel 
action to help recover from these errors in the AER and EDAC drivers.

  [Fix]
  Patches in Linus tree fixes this issue:
  aaf2c2fb0f51 ACPI / APEI: clear error status before acknowledging the error
  c4335fdd3822 ACPI: APEI: fix the wrong iteration of generic error status block

  [Testing]
  Insert a e1000 pcie card into the system, run the following command that 
should generate PCIe correctable errors, you will see only the first error in 
each GHES report go to the AER driver rather than all errors from the GHES 
reports.

  $ sudo setpci -s 0002:00:00.0 0x70c.l=0x00808000;sudo setpci -s
  0002:00:00.0 CAP_EXP+0x10.B=0x4b;sleep 1;sudo setpci -s 0002:00:00.0
  CAP_EXP+0x10.B=0x48

  Where "0002:00:00.0" being the root hub for the card.

  [Regression Potential]
  The two patches to ACPI APEI driver was cleanly cherry picked from linus's 
tree and applied to Artful and Zesty. The patches were tested on QDF2400 
platform where it was found to issue and don't introduce any regressions.

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

-- 
Mailing list: https://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 1041790] Re: [snb] GPU lockup IPEHR: 0x0b160001 IPEHR: 0x0b140001, workaround i915.semaphores=0

[Bug Watch Updater]

** Changed in: xserver-xorg-video-intel
   Status: Confirmed => Won't Fix

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

Title:
  [snb] GPU lockup  IPEHR: 0x0b160001 IPEHR: 0x0b140001, workaround
  i915.semaphores=0

Status in xf86-video-intel:
  Won't Fix
Status in linux package in Ubuntu:
  Incomplete
Status in xserver-xorg-video-intel package in Ubuntu:
  Triaged

Bug description:
  X locks up periodically for a 2 to ten seconds at a time and this
  crash log gets generated. It's significantly more than several times a
  day but not quite continuous. If you indeed have this bug, that should
  stop the lockups from happening. Irrespective, please file a new bug
  report so your hardware may be tracked.

  WORKAROUND: Edit your /etc/default/grub from:
  GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"

  to:
  GRUB_CMDLINE_LINUX_DEFAULT="quiet splash i915.semaphores=0"

  run the following and reboot:
  sudo update-grub

  The side effects of this is rendering throughput is dropped by 10%
  with SNA, or as much as 3x with UXA. OpenGL performance is likely to
  be reduced by about 30%. More CPU time is spent waiting for the GPU
  with rc6 disabled, so increased power consumption.

  ProblemType: Crash
  DistroRelease: Ubuntu 12.10
  Package: xserver-xorg-video-intel 2:2.20.3-0ubuntu1
  Uname: Linux 3.6.0-rc3-git-20120826.1015 x86_64
  ApportVersion: 2.5.1-0ubuntu2
  Architecture: amd64
  Chipset: sandybridge-m-gt2
  Date: Sun Aug 26 16:06:32 2012
  DistroCodename: quantal
  DistroVariant: ubuntu
  DuplicateSignature: [sandybridge-m-gt2] GPU lockup  IPEHR: 0x0b160001 IPEHR: 
0x0b140001 Ubuntu 12.10
  EcryptfsInUse: Yes
  ExecutablePath: /usr/share/apport/apport-gpu-error-intel.py
  GpuHangFrequency: Continuously
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Alpha amd64 (20120724.2)
  InterpreterPath: /usr/bin/python3.2mu
  MachineType: Dell Inc. Dell System XPS L502X
  ProcCmdline: /usr/bin/python3 /usr/share/apport/apport-gpu-error-intel.py
  ProcEnviron:

  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.6.0-rc3-git-20120826.1015 
root=UUID=135c8090-427c-460a-909d-eff262cd44b6 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   xserver-xorg 1:7.7+1ubuntu3
   libdrm2  2.4.38-0ubuntu2
   xserver-xorg-video-intel 2:2.20.3-0ubuntu1
  SourcePackage: xserver-xorg-video-intel
  Title: [sandybridge-m-gt2] GPU lockup  IPEHR: 0x0b160001 IPEHR: 0x0b140001
  UdevDb: Error: [Errno 2] No such file or directory: 'udevadm'
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

  dmi.bios.date: 05/29/2012
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A11
  dmi.board.name: 0NJT03
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnDellInc.:bvrA11:bd05/29/2012:svnDellInc.:pnDellSystemXPSL502X:pvr:rvnDellInc.:rn0NJT03:rvrA00:cvnDellInc.:ct8:cvr0.1:
  dmi.product.name: Dell System XPS L502X
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/xserver-xorg-video-intel/+bug/1041790/+subscriptions

-- 
Mailing list: https://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 1730762] Re: 17.10 - suspend/resume failure

[venturia]

I've tested all the following 64bit versions:

version before 3.13 were not starting
version 3.14 and 3.15 were starting only with x.org
for 3.16 and above start with wayland or xorg.

That said, all the 64 bit version fail in managing the suspend resume.


Using the old 14.04.1 32 bit from CD works fine. I don't how to test all the 
other 32 bit version. The bios is not able to start from USB and that make 
everything hard to test.

How I can support you?

A-

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

Title:
  17.10 - suspend/resume failure

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I'm experiencing a failure in the resume process after the suspend.
  When I try to resume the system start, but the screen stay black while
  the disk seem be really busy.

  The only way to exit from this status is unplug the system before
  restart it.

  Let me know how to collect additional info (if necessary).

  Alessandro-

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-16-generic 4.13.0-16.19
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  alessandro   1948 F pulseaudio
   /dev/snd/controlC0:  alessandro   1948 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Nov  7 22:59:45 2017
  HibernationDevice: RESUME=UUID=e43cf651-e870-4c57-826f-54017ec51f13
  InstallationDate: Installed on 2016-07-09 (486 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  IwConfig:
   lono wireless extensions.
   
   enp2s5no wireless extensions.
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 003 Device 002: ID 046d:c03d Logitech, Inc. M-BT96a Pilot Optical Mouse
   Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: Packard Bell NEC IMEDIA 5204
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic 
root=UUID=50ada02b-678c-4b91-96b4-65bcdeaf645c ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-16-generic N/A
   linux-backports-modules-4.13.0-16-generic  N/A
   linux-firmware 1.169
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/14/2006
  dmi.bios.vendor: Phoenix Technologies, LTD
  dmi.bios.version: 6.00 PG
  dmi.board.name: GA-8TRC410M-NF
  dmi.board.vendor: NEC COMPUTERS INTERNATIONAL
  dmi.chassis.type: 3
  dmi.chassis.vendor: NEC COMPUTERS INTERNATIONAL
  dmi.modalias: 
dmi:bvnPhoenixTechnologies,LTD:bvr6.00PG:bd02/14/2006:svnPackardBellNEC:pnIMEDIA5204:pvrPB34310106:rvnNECCOMPUTERSINTERNATIONAL:rnGA-8TRC410M-NF:rvr:cvnNECCOMPUTERSINTERNATIONAL:ct3:cvr:
  dmi.product.name: IMEDIA 5204
  dmi.product.version: PB34310106
  dmi.sys.vendor: Packard Bell NEC

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

-- 
Mailing list: https://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 1733357] Re: System won't go into suspend mode.

[lnxusr]

apport-collect 1733357 is sticks me at a blank launchpad 'Already logged
in' page with no way to indicate any decision.

@jsalsbury, sorry, I don't recall a kernel update for 17.10 and there is
only one option in my boot menu.  This problem seems to have fixed
itself though.  After todays updates of a bunch of cups and python
stuffs, it seems to be working again.  This problem introduced me to
suspend-hybrid and I like it better than plain suspend.  I think I'll
keep my 'temp fix' in place.

I guess we can close this and mark it as 'fixed by the computer
fairies'.

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

Title:
  System won't go into suspend mode.

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Since the following updates installed on Friday Nov 17 my system will
  no longer go into suspend or hibernate via the keybord or the logout
  screen when Suspend is selected.  It will, however, suspend via the
  command line with pm-syspend or pm-suspend-hybrid.

  As a temp workaround, I've added pm-suspend-hybrid to my sudoers and
  reconfigured the Sleep button in a custom shortcut.

  Packages installed Friday:

  code (1.18.0-1510145176, 1.18.1-1510857349) Upgraded at Fri Nov 17 23:36:07 
2017
  gir1.2-gtk-3.0 (3.22.24-0ubuntu1, 3.22.25-0ubuntu0.1) Upgraded at Fri Nov 17 
00:44:01 2017
  libgtk-3-common (3.22.24-0ubuntu1, 3.22.25-0ubuntu0.1) Upgraded at Fri Nov 17 
00:44:01 2017
  libgtk-3-0 (3.22.24-0ubuntu1, 3.22.25-0ubuntu0.1) Upgraded at Fri Nov 17 
00:44:01 2017
  libgtk-3-bin (3.22.24-0ubuntu1, 3.22.25-0ubuntu0.1) Upgraded at Fri Nov 17 
00:44:01 2017
  gtk-update-icon-cache (3.22.24-0ubuntu1, 3.22.25-0ubuntu0.1) Upgraded at Fri 
Nov 17 00:44:01 2017
  accountsservice (0.6.42-0ubuntu3, 0.6.42-0ubuntu3.1) Upgraded at Fri Nov 17 
00:44:01 2017
  libaccountsservice0 (0.6.42-0ubuntu3, 0.6.42-0ubuntu3.1) Upgraded at Fri Nov 
17 00:44:01 2017

  version.log and lspci-vnvn.log are attatched.  I received a 'pcilib:
  sysfs_read_vpd: read failed: Input/output error' on the lspci
  commnand, so it may not be complete.

  Ok, I can only attatch one file, so version.log reads:
  Ubuntu 4.13.0-16.19-generic 4.13.4

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

-- 
Mailing list: https://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 1726818] Re: vagrant artful64 box filesystem too small

[Colin Ian King]

My current hunch is that this is due to blk optimization functionality
that landed in the kernel and perhaps the virt blk device on VirtualBox
does not support it yet.

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

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

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

Title:
  vagrant artful64 box filesystem too small

Status in cloud-images:
  Confirmed
Status in linux package in Ubuntu:
  In Progress

Bug description:
  After building a new vagrant instance using the ubuntu/artful64 box
  (v20171023.1.0), the size of the filesystem seems to be much too
  small. Here's the output of `df -h` on the newly built instance:

  vagrant@ubuntu-artful:~$ df -h
  Filesystem  Size  Used Avail Use% Mounted on
  udev991M 0  991M   0% /dev
  tmpfs   200M  3.2M  197M   2% /run
  /dev/sda1   2.2G  2.1G   85M  97% /
  tmpfs   999M 0  999M   0% /dev/shm
  tmpfs   5.0M 0  5.0M   0% /run/lock
  tmpfs   999M 0  999M   0% /sys/fs/cgroup
  vagrant 210G  182G   28G  87% /vagrant
  tmpfs   200M 0  200M   0% /run/user/1000

  
  For comparison, here is the same from the latest zesty64 box:

  ubuntu@ubuntu-zesty:~$ df -h
  Filesystem  Size  Used Avail Use% Mounted on
  udev992M 0  992M   0% /dev
  tmpfs   200M  3.2M  197M   2% /run
  /dev/sda1   9.7G  2.5G  7.3G  26% /
  tmpfs   999M 0  999M   0% /dev/shm
  tmpfs   5.0M 0  5.0M   0% /run/lock
  tmpfs   999M 0  999M   0% /sys/fs/cgroup
  vagrant 210G  183G   28G  88% /vagrant
  tmpfs   200M 0  200M   0% /run/user/1000

  
  With artful64, the size of /dev/sda1 is reported as 2.2G, which results in 
97% of disk usage immediately after building, even though the disk size is 10G, 
as reported by the fdisk:

  
  vagrant@ubuntu-artful:~$ sudo fdisk -l
  Disk /dev/sda: 10 GiB, 10737418240 bytes, 20971520 sectors
  Units: sectors of 1 * 512 = 512 bytes
  Sector size (logical/physical): 512 bytes / 512 bytes
  I/O size (minimum/optimal): 512 bytes / 512 bytes
  Disklabel type: dos
  Disk identifier: 0x4ad77c39

  Device Boot Start  End  Sectors Size Id Type
  /dev/sda1  * 2048 20971486 20969439  10G 83 Linux

  
  Disk /dev/sdb: 10 MiB, 10485760 bytes, 20480 sectors
  Units: sectors of 1 * 512 = 512 bytes
  Sector size (logical/physical): 512 bytes / 512 bytes
  I/O size (minimum/optimal): 512 bytes / 512 bytes

  
  Almost any additional installation results in a "No space left on device" 
error.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-images/+bug/1726818/+subscriptions

-- 
Mailing list: https://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 1721856] Re: Suspend ends after seconds and laptop resumes

[Karl-Philipp Richter]

Good to know, thank you for your support. The issue is fixed in
4.13.0-16-generic of Ubuntu 17.10 as stated in #16.

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

Title:
  Suspend ends after seconds and laptop resumes

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

Bug description:
  The suspend/standby ends after seconds and the laptop resumes like
  it'd wake up from suspend. I didn't use suspend for a long time
  (months or years) and can't even estimate when it worked for the last
  time.

  This issue is fixed in 4.14-rc3 mainline kernel - although some parts
  of the installation don't work, like ZFS and nvidia-340 which might
  cause the problem as well.

  I'm willing to do git bisect work if you confirm me that this makes
  sense.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: linux-image-4.10.0-35-generic 4.10.0-35.39
  ProcVersionSignature: Ubuntu 4.10.0-35.39-generic 4.10.17
  Uname: Linux 4.10.0-35-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  AudioDevicesInUse:
   BEN.PID ZUGR.  BEFEHL
   /dev/snd/controlC0:  richter   18896 F pulseaudio
  CurrentDesktop: XFCE
  Date: Fri Oct  6 20:21:35 2017
  HibernationDevice: RESUME=UUID=1bb0bb3e-8148-4957-9673-9701bd571c0a
  InstallationDate: Installed on 2015-12-12 (664 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  MachineType: LENOVO 20221
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-35-generic 
root=UUID=791b47e7-915d-4d5a-bce0-d7e9b660a2ab ro 
rootflags=subvol=ubuntu-main-root
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-35-generic N/A
   linux-backports-modules-4.10.0-35-generic  N/A
   linux-firmware 1.164.1
  SourcePackage: linux
  UpgradeStatus: Upgraded to zesty on 2017-05-01 (158 days ago)
  dmi.bios.date: 07/12/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 71CN51WW(V1.21)
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: INVALID
  dmi.board.vendor: LENOVO
  dmi.board.version: 3193WIN8 STD MLT
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo IdeaPad Z500 Touch
  dmi.modalias: 
dmi:bvnLENOVO:bvr71CN51WW(V1.21):bd07/12/2013:svnLENOVO:pn20221:pvrLenovoIdeaPadZ500Touch:rvnLENOVO:rnINVALID:rvr3193WIN8STDMLT:cvnLENOVO:ct10:cvrLenovoIdeaPadZ500Touch:
  dmi.product.name: 20221
  dmi.product.version: Lenovo IdeaPad Z500 Touch
  dmi.sys.vendor: LENOVO

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

-- 
Mailing list: https://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 1721856] Re: Suspend ends after seconds and laptop resumes

[Joseph Salisbury]

The reverse bisect reported the following commit was the fix:
91d57bae0868 ("posix-timers: Make use of forward/remaining callbacks")

This commit was added to mainline as of v4.13-rc1, which means it is
already in Artful(17.10) and Bionic(18.04).

That commit was not a clean cherry pick into Zesty.  It requires some
back porting to core timer code, which means it may not pass SRU
criteria.

Can you see if the bug is fixed for you in 17.10(Artful)?  It can be downloaded 
from:
https://launchpad.net/~canonical-kernel-security-team/+archive/ubuntu/ppa2/+build/13567624

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

Title:
  Suspend ends after seconds and laptop resumes

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

Bug description:
  The suspend/standby ends after seconds and the laptop resumes like
  it'd wake up from suspend. I didn't use suspend for a long time
  (months or years) and can't even estimate when it worked for the last
  time.

  This issue is fixed in 4.14-rc3 mainline kernel - although some parts
  of the installation don't work, like ZFS and nvidia-340 which might
  cause the problem as well.

  I'm willing to do git bisect work if you confirm me that this makes
  sense.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: linux-image-4.10.0-35-generic 4.10.0-35.39
  ProcVersionSignature: Ubuntu 4.10.0-35.39-generic 4.10.17
  Uname: Linux 4.10.0-35-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  AudioDevicesInUse:
   BEN.PID ZUGR.  BEFEHL
   /dev/snd/controlC0:  richter   18896 F pulseaudio
  CurrentDesktop: XFCE
  Date: Fri Oct  6 20:21:35 2017
  HibernationDevice: RESUME=UUID=1bb0bb3e-8148-4957-9673-9701bd571c0a
  InstallationDate: Installed on 2015-12-12 (664 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  MachineType: LENOVO 20221
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-35-generic 
root=UUID=791b47e7-915d-4d5a-bce0-d7e9b660a2ab ro 
rootflags=subvol=ubuntu-main-root
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-35-generic N/A
   linux-backports-modules-4.10.0-35-generic  N/A
   linux-firmware 1.164.1
  SourcePackage: linux
  UpgradeStatus: Upgraded to zesty on 2017-05-01 (158 days ago)
  dmi.bios.date: 07/12/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 71CN51WW(V1.21)
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: INVALID
  dmi.board.vendor: LENOVO
  dmi.board.version: 3193WIN8 STD MLT
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo IdeaPad Z500 Touch
  dmi.modalias: 
dmi:bvnLENOVO:bvr71CN51WW(V1.21):bd07/12/2013:svnLENOVO:pn20221:pvrLenovoIdeaPadZ500Touch:rvnLENOVO:rnINVALID:rvr3193WIN8STDMLT:cvnLENOVO:ct10:cvrLenovoIdeaPadZ500Touch:
  dmi.product.name: 20221
  dmi.product.version: Lenovo IdeaPad Z500 Touch
  dmi.sys.vendor: LENOVO

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

-- 
Mailing list: https://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 1726818] Re: vagrant artful64 box filesystem too small

[Colin Ian King]

I'll try and figure out *why* this patch is causing the kernel grief
tomorrow.

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

Title:
  vagrant artful64 box filesystem too small

Status in cloud-images:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After building a new vagrant instance using the ubuntu/artful64 box
  (v20171023.1.0), the size of the filesystem seems to be much too
  small. Here's the output of `df -h` on the newly built instance:

  vagrant@ubuntu-artful:~$ df -h
  Filesystem  Size  Used Avail Use% Mounted on
  udev991M 0  991M   0% /dev
  tmpfs   200M  3.2M  197M   2% /run
  /dev/sda1   2.2G  2.1G   85M  97% /
  tmpfs   999M 0  999M   0% /dev/shm
  tmpfs   5.0M 0  5.0M   0% /run/lock
  tmpfs   999M 0  999M   0% /sys/fs/cgroup
  vagrant 210G  182G   28G  87% /vagrant
  tmpfs   200M 0  200M   0% /run/user/1000

  
  For comparison, here is the same from the latest zesty64 box:

  ubuntu@ubuntu-zesty:~$ df -h
  Filesystem  Size  Used Avail Use% Mounted on
  udev992M 0  992M   0% /dev
  tmpfs   200M  3.2M  197M   2% /run
  /dev/sda1   9.7G  2.5G  7.3G  26% /
  tmpfs   999M 0  999M   0% /dev/shm
  tmpfs   5.0M 0  5.0M   0% /run/lock
  tmpfs   999M 0  999M   0% /sys/fs/cgroup
  vagrant 210G  183G   28G  88% /vagrant
  tmpfs   200M 0  200M   0% /run/user/1000

  
  With artful64, the size of /dev/sda1 is reported as 2.2G, which results in 
97% of disk usage immediately after building, even though the disk size is 10G, 
as reported by the fdisk:

  
  vagrant@ubuntu-artful:~$ sudo fdisk -l
  Disk /dev/sda: 10 GiB, 10737418240 bytes, 20971520 sectors
  Units: sectors of 1 * 512 = 512 bytes
  Sector size (logical/physical): 512 bytes / 512 bytes
  I/O size (minimum/optimal): 512 bytes / 512 bytes
  Disklabel type: dos
  Disk identifier: 0x4ad77c39

  Device Boot Start  End  Sectors Size Id Type
  /dev/sda1  * 2048 20971486 20969439  10G 83 Linux

  
  Disk /dev/sdb: 10 MiB, 10485760 bytes, 20480 sectors
  Units: sectors of 1 * 512 = 512 bytes
  Sector size (logical/physical): 512 bytes / 512 bytes
  I/O size (minimum/optimal): 512 bytes / 512 bytes

  
  Almost any additional installation results in a "No space left on device" 
error.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-images/+bug/1726818/+subscriptions

-- 
Mailing list: https://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 1726818] Re: vagrant artful64 box filesystem too small

[Colin Ian King]

Whilst one cannot revert this for 4.13, I did remove the offending code,
rebuilt and now one can boot without the kernel failure and the hdd is
resized correctly.

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

Title:
  vagrant artful64 box filesystem too small

Status in cloud-images:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After building a new vagrant instance using the ubuntu/artful64 box
  (v20171023.1.0), the size of the filesystem seems to be much too
  small. Here's the output of `df -h` on the newly built instance:

  vagrant@ubuntu-artful:~$ df -h
  Filesystem  Size  Used Avail Use% Mounted on
  udev991M 0  991M   0% /dev
  tmpfs   200M  3.2M  197M   2% /run
  /dev/sda1   2.2G  2.1G   85M  97% /
  tmpfs   999M 0  999M   0% /dev/shm
  tmpfs   5.0M 0  5.0M   0% /run/lock
  tmpfs   999M 0  999M   0% /sys/fs/cgroup
  vagrant 210G  182G   28G  87% /vagrant
  tmpfs   200M 0  200M   0% /run/user/1000

  
  For comparison, here is the same from the latest zesty64 box:

  ubuntu@ubuntu-zesty:~$ df -h
  Filesystem  Size  Used Avail Use% Mounted on
  udev992M 0  992M   0% /dev
  tmpfs   200M  3.2M  197M   2% /run
  /dev/sda1   9.7G  2.5G  7.3G  26% /
  tmpfs   999M 0  999M   0% /dev/shm
  tmpfs   5.0M 0  5.0M   0% /run/lock
  tmpfs   999M 0  999M   0% /sys/fs/cgroup
  vagrant 210G  183G   28G  88% /vagrant
  tmpfs   200M 0  200M   0% /run/user/1000

  
  With artful64, the size of /dev/sda1 is reported as 2.2G, which results in 
97% of disk usage immediately after building, even though the disk size is 10G, 
as reported by the fdisk:

  
  vagrant@ubuntu-artful:~$ sudo fdisk -l
  Disk /dev/sda: 10 GiB, 10737418240 bytes, 20971520 sectors
  Units: sectors of 1 * 512 = 512 bytes
  Sector size (logical/physical): 512 bytes / 512 bytes
  I/O size (minimum/optimal): 512 bytes / 512 bytes
  Disklabel type: dos
  Disk identifier: 0x4ad77c39

  Device Boot Start  End  Sectors Size Id Type
  /dev/sda1  * 2048 20971486 20969439  10G 83 Linux

  
  Disk /dev/sdb: 10 MiB, 10485760 bytes, 20480 sectors
  Units: sectors of 1 * 512 = 512 bytes
  Sector size (logical/physical): 512 bytes / 512 bytes
  I/O size (minimum/optimal): 512 bytes / 512 bytes

  
  Almost any additional installation results in a "No space left on device" 
error.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-images/+bug/1726818/+subscriptions

-- 
Mailing list: https://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 1733321] Re: network-manager ADT tests fail with on ppc64el with artful/linux 4.13.0.17.18

[Joseph Salisbury]

** Tags added: kernel-key

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

Title:
  network-manager ADT tests fail with on ppc64el with artful/linux
  4.13.0.17.18

Status in linux package in Ubuntu:
  Triaged
Status in linux source package in Artful:
  Triaged

Bug description:
  ppc64el ADT log:
  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
  /autopkgtest-artful/artful/ppc64el/n/network-
  manager/20171120_100719_28642@/log.gz

  Testcase output:
  -
  autopkgtest [10:04:48]: test killswitches-no-urfkill: [---
  make -C /lib/modules/4.13.0-17-generic/build 
KBUILD_SRC=/lib/modules/4.13.0-17-generic/build 
M=/tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests
  make[1]: Entering directory '/usr/src/linux-headers-4.13.0-17-generic'
AR  /tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests/built-in.o
CC [M]  /tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests/fake-rfkill.o
Building modules, stage 2.
MODPOST 1 modules
CC  /tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests/fake-rfkill.mod.o
LD [M]  /tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests/fake-rfkill.ko
  make[1]: Leaving directory '/usr/src/linux-headers-4.13.0-17-generic'
  ERROR: NM could not track device state.
  autopkgtest [10:05:20]: test killswitches-no-urfkill: ---]
  autopkgtest [10:05:20]: test killswitches-no-urfkill:  - - - - - - - - - - 
results - - - - - - - - - -
  killswitches-no-urfkill FAIL non-zero exit status 1
  -

  Package versions [artful/ppc64el]:
  network-manager 1.8.4-1ubuntu3
  linux-meta 4.13.0.17.18

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

-- 
Mailing list: https://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 1733357] Re: System won't go into suspend mode.

[Joseph Salisbury]

Does the bug go away if you boot back into the prior kernel version?

** Tags added: artful needs-bisect

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

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

Title:
  System won't go into suspend mode.

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Since the following updates installed on Friday Nov 17 my system will
  no longer go into suspend or hibernate via the keybord or the logout
  screen when Suspend is selected.  It will, however, suspend via the
  command line with pm-syspend or pm-suspend-hybrid.

  As a temp workaround, I've added pm-suspend-hybrid to my sudoers and
  reconfigured the Sleep button in a custom shortcut.

  Packages installed Friday:

  code (1.18.0-1510145176, 1.18.1-1510857349) Upgraded at Fri Nov 17 23:36:07 
2017
  gir1.2-gtk-3.0 (3.22.24-0ubuntu1, 3.22.25-0ubuntu0.1) Upgraded at Fri Nov 17 
00:44:01 2017
  libgtk-3-common (3.22.24-0ubuntu1, 3.22.25-0ubuntu0.1) Upgraded at Fri Nov 17 
00:44:01 2017
  libgtk-3-0 (3.22.24-0ubuntu1, 3.22.25-0ubuntu0.1) Upgraded at Fri Nov 17 
00:44:01 2017
  libgtk-3-bin (3.22.24-0ubuntu1, 3.22.25-0ubuntu0.1) Upgraded at Fri Nov 17 
00:44:01 2017
  gtk-update-icon-cache (3.22.24-0ubuntu1, 3.22.25-0ubuntu0.1) Upgraded at Fri 
Nov 17 00:44:01 2017
  accountsservice (0.6.42-0ubuntu3, 0.6.42-0ubuntu3.1) Upgraded at Fri Nov 17 
00:44:01 2017
  libaccountsservice0 (0.6.42-0ubuntu3, 0.6.42-0ubuntu3.1) Upgraded at Fri Nov 
17 00:44:01 2017

  version.log and lspci-vnvn.log are attatched.  I received a 'pcilib:
  sysfs_read_vpd: read failed: Input/output error' on the lspci
  commnand, so it may not be complete.

  Ok, I can only attatch one file, so version.log reads:
  Ubuntu 4.13.0-16.19-generic 4.13.4

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

-- 
Mailing list: https://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 1726818] Re: vagrant artful64 box filesystem too small

[Colin Ian King]

git bisect'd to:

c20cfc27a47307e811346f85959cf3cc07ae42f9 is the first bad commit
commit c20cfc27a47307e811346f85959cf3cc07ae42f9
Author: Christoph Hellwig 
Date:   Wed Apr 5 19:21:07 2017 +0200

block: stop using blkdev_issue_write_same for zeroing

We'll always use the WRITE ZEROES code for zeroing now.

Signed-off-by: Christoph Hellwig 
Reviewed-by: Martin K. Petersen 
Reviewed-by: Hannes Reinecke 
Signed-off-by: Jens Axboe 

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

Title:
  vagrant artful64 box filesystem too small

Status in cloud-images:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After building a new vagrant instance using the ubuntu/artful64 box
  (v20171023.1.0), the size of the filesystem seems to be much too
  small. Here's the output of `df -h` on the newly built instance:

  vagrant@ubuntu-artful:~$ df -h
  Filesystem  Size  Used Avail Use% Mounted on
  udev991M 0  991M   0% /dev
  tmpfs   200M  3.2M  197M   2% /run
  /dev/sda1   2.2G  2.1G   85M  97% /
  tmpfs   999M 0  999M   0% /dev/shm
  tmpfs   5.0M 0  5.0M   0% /run/lock
  tmpfs   999M 0  999M   0% /sys/fs/cgroup
  vagrant 210G  182G   28G  87% /vagrant
  tmpfs   200M 0  200M   0% /run/user/1000

  
  For comparison, here is the same from the latest zesty64 box:

  ubuntu@ubuntu-zesty:~$ df -h
  Filesystem  Size  Used Avail Use% Mounted on
  udev992M 0  992M   0% /dev
  tmpfs   200M  3.2M  197M   2% /run
  /dev/sda1   9.7G  2.5G  7.3G  26% /
  tmpfs   999M 0  999M   0% /dev/shm
  tmpfs   5.0M 0  5.0M   0% /run/lock
  tmpfs   999M 0  999M   0% /sys/fs/cgroup
  vagrant 210G  183G   28G  88% /vagrant
  tmpfs   200M 0  200M   0% /run/user/1000

  
  With artful64, the size of /dev/sda1 is reported as 2.2G, which results in 
97% of disk usage immediately after building, even though the disk size is 10G, 
as reported by the fdisk:

  
  vagrant@ubuntu-artful:~$ sudo fdisk -l
  Disk /dev/sda: 10 GiB, 10737418240 bytes, 20971520 sectors
  Units: sectors of 1 * 512 = 512 bytes
  Sector size (logical/physical): 512 bytes / 512 bytes
  I/O size (minimum/optimal): 512 bytes / 512 bytes
  Disklabel type: dos
  Disk identifier: 0x4ad77c39

  Device Boot Start  End  Sectors Size Id Type
  /dev/sda1  * 2048 20971486 20969439  10G 83 Linux

  
  Disk /dev/sdb: 10 MiB, 10485760 bytes, 20480 sectors
  Units: sectors of 1 * 512 = 512 bytes
  Sector size (logical/physical): 512 bytes / 512 bytes
  I/O size (minimum/optimal): 512 bytes / 512 bytes

  
  Almost any additional installation results in a "No space left on device" 
error.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-images/+bug/1726818/+subscriptions

-- 
Mailing list: https://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 1389077] Re: [HP ProBook 4530s / Lenovo G580] Intel Powerclamp is Slowing CPU

[Михаил]

** Summary changed:

- [HP ProBook 4530s] Intel Powerclamp is Slowing CPU
+ [HP ProBook 4530s / Lenovo G580] Intel Powerclamp is Slowing CPU

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

Title:
  [HP ProBook 4530s / Lenovo G580] Intel Powerclamp is Slowing CPU

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I upgraded from KUbuntu 14.04 to 14.10. Immediately, while playing
  minecraft with my daughter, I noticed the game was running very
  slowly. Even after closing the game, my web browsing slowed to a
  crawl.

  Looking at the processes in top, I noticed there were 4 tasks called
  kidle_inject running at 50% CPU each. After spending a long time
  figuring out what caused this, I found out this is caused by the Intel
  Powerclamp driver. I never did anything to enable this, and haven't
  observed this slowdown before the upgrade.

  I found the powerclamp driver in the
  /sys/class/thermal/cooling_device5 directory:

  root@bkat-HP-ProBook-4530s:/sys/class/thermal/cooling_device5# cat type 
  intel_powerclamp
  root@bkat-HP-ProBook-4530s:/sys/class/thermal/cooling_device5# cat cur_state 
  -1
  root@bkat-HP-ProBook-4530s:/sys/class/thermal/cooling_device5# cat max_state 
  50

  I tried to echo 0 to cur_state, but it still reported -1 when I catted
  the value.

  There seems to be no obvious way to disable this, and this should not
  have been enabled in the first place.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: linux-image-3.16.0-24-generic 3.16.0-24.32
  ProcVersionSignature: Ubuntu 3.16.0-24.32-generic 3.16.4
  Uname: Linux 3.16.0-24-generic x86_64
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  bkat   2780 F pulseaudio
  CurrentDesktop: KDE
  Date: Mon Nov  3 23:16:04 2014
  HibernationDevice: RESUME=UUID=35e1d874-a3bd-4227-acab-16f3e929d993
  InstallationDate: Installed on 2012-04-22 (925 days ago)
  InstallationMedia: Kubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
  MachineType: Hewlett-Packard HP ProBook 4530s
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-24-generic 
root=UUID=743f1686-bfe7-4e32-911d-5371633ccec8 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.16.0-24-generic N/A
   linux-backports-modules-3.16.0-24-generic  N/A
   linux-firmware 1.138
  SourcePackage: linux
  UpgradeStatus: Upgraded to utopic on 2014-11-03 (0 days ago)
  dmi.bios.date: 05/13/2011
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 68SRR Ver. F.09
  dmi.board.name: 167C
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 22.1A
  dmi.chassis.asset.tag: CNU1284V1X
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68SRRVer.F.09:bd05/13/2011:svnHewlett-Packard:pnHPProBook4530s:pvrA0001D02:rvnHewlett-Packard:rn167C:rvrKBCVersion22.1A:cvnHewlett-Packard:ct10:cvr:
  dmi.product.name: HP ProBook 4530s
  dmi.product.version: A0001D02
  dmi.sys.vendor: Hewlett-Packard

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

-- 
Mailing list: https://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 1732686] Re: Asus Fx553VD - Keyboard LED backlight controls are not working # kernel-bug-reported-upstream

[R.Erol]

Kai , thank you so much!

That one works nicely , i can adjust the brightness of keyboard and turn
on and off my keyboard light.

Thanks again.

One last question though ; what can i do for ACPI errors?

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

Title:
  Asus Fx553VD - Keyboard LED backlight controls are not working #
  kernel-bug-reported-upstream

Status in linux package in Ubuntu:
  Triaged

Bug description:
  Hi , i'm using this laptop with it's latest bios (V303 -
  https://www.asus.com/Laptops/ASUS-FX553VD/HelpDesk_BIOS/ )

  Kernel : 4.14.0-041400-generic x86_64

  I can't control keyboard LED backlight level with it's dedicated FN
  keys or anything else. FN keys are recognized by Linux Mint 18.2 and
  Ubuntu 16.04 but pressing them have no effect.

  Kernels from 4.10 to 4.14 are the same on that regard.

  And also i have these errors on "inxi -F && dmesg | grep -i error"

  [0.031175] ACPI Error: [PRT0] Namespace lookup failure, AE_ALREADY_EXISTS 
(20170728/dswload-378)
  [0.040665] ACPI Error: 1 table load failures, 10 successful 
(20170728/tbxfload-246)
  [0.506425] acpi PNP0A08:00: _OSC failed (AE_ERROR); disabling ASPM
  [1.694527] RAS: Correctable Errors collector initialized.
  [9.833145] EXT4-fs (sda2): re-mounted. Opts: errors=remount-ro

  I'm not a developer but only a user. So if i opened that issue to the
  wrong place can you point me the correct place to open it?

  Thanks.
  --- 
  ApportVersion: 2.20.1-0ubuntu2.12
  Architecture: amd64
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux 18.2
  InstallationDate: Installed on 2017-10-22 (24 days ago)
  InstallationMedia: Linux Mint 18.2 "Sonya" - Release amd64 20170628
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=tr_TR.UTF-8
   SHELL=/bin/bash
  Tags:  sonya
  Uname: Linux 4.14.0-041400-generic x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  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/linux/+bug/1732686/+subscriptions

-- 
Mailing list: https://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 1724911] Re: text VTs are unavailable on desktop after upgrade to Ubuntu 17.10

[Steve Langasek]

311ac00deff520820d198cda141109f2a5655d4a is bad.

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

Title:
  text VTs are unavailable on desktop after upgrade to Ubuntu 17.10

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

Bug description:
  After upgrading my laptop to Ubuntu 17.10, I am unable to access
  gettys on any of the text-mode VTs on my system.

  gdm3 is running on VT1, my user session is running on VT2.  I can
  switch between these.  If I switch to VT3, I know that the VT switch
  has happened in the kernel because the X cursor disappears; but the
  display retains the output of my X session, and the text console with
  getty never appears.

  Switching back to VT2 works fine.

  The same problem occurs with either Wayland or X.

  My laptop is docked with an external monitor, which could be a factor.
  (I also notice that during boot, plymouth is only rendered on the
  internal monitor, not the external monitor; this may be related).  I
  have not yet tested whether this problem is reproducible if I undock.

  The system is booting with vt.handoff=7, which I believe is still the
  default in Ubuntu 17.10.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-16-generic 4.13.0-16.19
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  vorlon24080 F pulseaudio
   /dev/snd/controlC0:  vorlon24080 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct 19 09:57:59 2017
  HibernationDevice: RESUME=UUID=6df76279-19ea-45a4-bec9-e4fdc858729a
  InstallationDate: Installed on 2010-09-24 (2582 days ago)
  InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release amd64 
(20100816.1)
  MachineType: LENOVO 2306CTO
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-16-generic.efi.signed 
root=/dev/mapper/hostname-root ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-16-generic N/A
   linux-backports-modules-4.13.0-16-generic  N/A
   linux-firmware 1.169
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: Upgraded to artful on 2017-10-19 (0 days ago)
  dmi.bios.date: 10/25/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G2ET97WW (2.57 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 2306CTO
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrG2ET97WW(2.57):bd10/25/2013:svnLENOVO:pn2306CTO:pvrThinkPadX230:rvnLENOVO:rn2306CTO:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad X230
  dmi.product.name: 2306CTO
  dmi.product.version: ThinkPad X230
  dmi.sys.vendor: LENOVO

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

-- 
Mailing list: https://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 1732990] Re: [Artful/Zesty] ACPI APEI error handling bug fixes

[Jeffrey Hugo]

Validated the test kernel in the PPA by installing it onto a QDF2400
device running 16.04.3

Used JTAG to trigger multiple concurrent errors, and observed that all
errors were parsed, instead of just the first one:

root@ubuntu:/home/ubuntu# cat /sys/kernel/debug/tracing/trace
# tracer: nop
#
#  _-=> irqs-off
# / _=> need-resched
#| / _---=> hardirq/softirq
#|| / _--=> preempt-depth
#||| / delay
#   TASK-PID   CPU#  TIMESTAMP  FUNCTION
#  | |   |      | |
  -0 [024] .ns.   462.341863: arm_event: affinity level: 2; 
MPIDR: ; MIDR: 510fc001; running state: 1; PSCI state: 0
  97-overlayroot-2510  [024] ..s.  1010.705078: arm_event: affinity level: 2; 
MPIDR: ; MIDR: 510fc001; running state: 1; PSCI state: 0
  97-overlayroot-2510  [024] ..s.  1010.705081: arm_event: affinity level: 2; 
MPIDR: ; MIDR: 510fc001; running state: 1; PSCI state: 0
  97-overlayroot-2510  [024] ..s.  1010.705082: arm_event: affinity level: 2; 
MPIDR: ; MIDR: 510fc001; running state: 1; PSCI state: 0
  97-overlayroot-2510  [024] ..s.  1010.705083: arm_event: affinity level: 2; 
MPIDR: ; MIDR: 510fc001; running state: 1; PSCI state: 
0 
 
The fixes to the PPA kernel address 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/1732990

Title:
  [Artful/Zesty] ACPI APEI error handling bug fixes

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  [Impact]
  Error records which have multiple errors in them will incorrectly report all 
errors after the first one. This results in garbage non-standard error trace 
events to be generated, and for AER and MC errors there will be no kernel 
action to help recover from these errors in the AER and EDAC drivers.

  [Fix]
  Patches in Linus tree fixes this issue:
  aaf2c2fb0f51 ACPI / APEI: clear error status before acknowledging the error
  c4335fdd3822 ACPI: APEI: fix the wrong iteration of generic error status block

  [Testing]
  Insert a e1000 pcie card into the system, run the following command that 
should generate PCIe correctable errors, you will see only the first error in 
each GHES report go to the AER driver rather than all errors from the GHES 
reports.

  $ sudo setpci -s 0002:00:00.0 0x70c.l=0x00808000;sudo setpci -s
  0002:00:00.0 CAP_EXP+0x10.B=0x4b;sleep 1;sudo setpci -s 0002:00:00.0
  CAP_EXP+0x10.B=0x48

  Where "0002:00:00.0" being the root hub for the card.

  [Regression Potential]
  The two patches to ACPI APEI driver was cleanly cherry picked from linus's 
tree and applied to Artful and Zesty. The patches were tested on QDF2400 
platform where it was found to issue and don't introduce any regressions.

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

-- 
Mailing list: https://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 437760] ☂yahoo wow, that's so excellent

[AloxeCorton]

Yo!

Have you read that  nice article already,  it's so  interesting, please
read  it here  http://www.triathloncoach-
ted.com/donate.php?UE80Mzc3NjBAYnVncy5sYXVuY2hwYWQubmV0

See you around, Danielle Trotter

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

Title:
  [Sony Corporation VGN-SR19VN] suspend/resume failure [non-free: fglrx]

Status in linux package in Ubuntu:
  Invalid

Bug description:
  suspend to ram has stopped working ever since version 8.04
  Karmic Koala doesn't seem to want to resume after a suspend-2-ram operation 
(black blank screen with no possibility to CTRL-ALT-Fx)
  Using proprietary fglrx ATI drivers which seem to be one of the issues around 
this reoccuring problem.
  I'm also using the x86_64 bit version.

  ProblemType: KernelOops
  Annotation: This occured during a previous suspend and prevented it from 
resuming properly.
  AplayDevices:
    List of PLAYBACK Hardware Devices 
   card 0: Intel [HDA Intel], device 0: ALC262 Analog [ALC262 Analog]
 Subdevices: 1/1
 Subdevice #0: subdevice #0
  Architecture: amd64
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 0: Intel [HDA Intel], device 0: ALC262 Analog [ALC262 Analog]
 Subdevices: 1/1
 Subdevice #0: subdevice #0
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  aloxecorton   2494 F pulseaudio
  CRDA: Error: [Errno 2] No such file or directory
  Card0.Amixer.info:
   Card hw:0 'Intel'/'HDA Intel at 0xcd20 irq 22'
 Mixer name : 'Realtek ALC262'
 Components : 'HDA:10ec0262,104d2d00,00100302 
HDA:14f12c06,104d1700,0010'
 Controls  : 18
 Simple ctrls  : 11
  Date: Sun Sep 27 20:04:11 2009
  DistroRelease: Ubuntu 9.10
  ExecutablePath: /usr/share/apport/apportcheckresume
  Failure: suspend/resume
  HibernationDevice: RESUME=UUID=be4c6ebd-4b40-462f-88df-beca6a1d0c37
  InterpreterPath: /usr/bin/python2.6
  MachineType: Sony Corporation VGN-SR19VN
  NonfreeKernelModules: fglrx
  Package: linux-image-2.6.31-11-generic 2.6.31-11.36
  ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.31-11-generic 
root=UUID=3ae8a3c5-ed76-439e-8eee-a736c080b3cb ro quiet splash
  ProcCmdline: /usr/bin/python /usr/share/apport/apportcheckresume
  ProcEnviron: PATH=(custom, no user)
  ProcVersionSignature: Ubuntu 2.6.31-11.36-generic
  RelatedPackageVersions: linux-firmware 1.19
  SourcePackage: linux
  Tags: resume suspend
  Title: [Sony Corporation VGN-SR19VN] suspend/resume failure [non-free: fglrx]
  Uname: Linux 2.6.31-11-generic x86_64
  UserGroups:
   
  dmi.bios.date: 06/05/2008
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: R0280Y1
  dmi.board.asset.tag: N/A
  dmi.board.name: VAIO
  dmi.board.vendor: Sony Corporation
  dmi.board.version: N/A
  dmi.chassis.asset.tag: N/A
  dmi.chassis.type: 10
  dmi.chassis.vendor: Sony Corporation
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrR0280Y1:bd06/05/2008:svnSonyCorporation:pnVGN-SR19VN:pvrC600D1Z5:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A:
  dmi.product.name: VGN-SR19VN
  dmi.product.version: C600D1Z5
  dmi.sys.vendor: Sony Corporation

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

-- 
Mailing list: https://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 1730480] Re: Problem after 17.04 to 17.10 upgrade

[G. Herrick]

This is an image of the line that is visible in the sequence between the Grub 
menu and the Recovery Menu.
Hope that helps.

** Attachment added: "Image of line with ERROR in it"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1730480/+attachment/5011745/+files/20171120_152818.jpg

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

Title:
  Problem after 17.04 to 17.10 upgrade

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Problem after 17.04 to 17.10 upgrade - seven days ago.
  I have to boot using Grub, in recovery mode. System works ok. During power 
down, I get -
  A Stop Job is Running for Session C3 of User GDM - which waits for 1 minute 
30 - and then proceeds to finish.
  System is an AMD64, with graphics on the motherboard. I will search for more 
detail if necessary.
  --- 
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gherrick   1646 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 17.10
  HibernationDevice: RESUME=UUID=26031761-8323-4a7b-85b2-0dc3fbcdb852
  InstallationDate: Installed on 2016-05-05 (551 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  IwConfig:
   enp2s0no wireless extensions.
   
   lono wireless extensions.
  MachineType: Gigabyte Technology Co., Ltd. GA-MA74GMT-S2
  Package: linux (not installed)
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic 
root=UUID=f2bc2165-9cb7-467c-a941-8e5ae02ee038 ro recovery nomodeset
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-16-generic N/A
   linux-backports-modules-4.13.0-16-generic  N/A
   linux-firmware 1.169
  RfKill:
   
  Tags:  artful
  Uname: Linux 4.13.0-16-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 08/31/2010
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F10
  dmi.board.name: GA-MA74GMT-S2
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF10:bd08/31/2010:svnGigabyteTechnologyCo.,Ltd.:pnGA-MA74GMT-S2:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-MA74GMT-S2:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: GA-MA74GMT-S2
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

-- 
Mailing list: https://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 1733357] 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 1733357

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

Title:
  System won't go into suspend mode.

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Since the following updates installed on Friday Nov 17 my system will
  no longer go into suspend or hibernate via the keybord or the logout
  screen when Suspend is selected.  It will, however, suspend via the
  command line with pm-syspend or pm-suspend-hybrid.

  As a temp workaround, I've added pm-suspend-hybrid to my sudoers and
  reconfigured the Sleep button in a custom shortcut.

  Packages installed Friday:

  code (1.18.0-1510145176, 1.18.1-1510857349) Upgraded at Fri Nov 17 23:36:07 
2017
  gir1.2-gtk-3.0 (3.22.24-0ubuntu1, 3.22.25-0ubuntu0.1) Upgraded at Fri Nov 17 
00:44:01 2017
  libgtk-3-common (3.22.24-0ubuntu1, 3.22.25-0ubuntu0.1) Upgraded at Fri Nov 17 
00:44:01 2017
  libgtk-3-0 (3.22.24-0ubuntu1, 3.22.25-0ubuntu0.1) Upgraded at Fri Nov 17 
00:44:01 2017
  libgtk-3-bin (3.22.24-0ubuntu1, 3.22.25-0ubuntu0.1) Upgraded at Fri Nov 17 
00:44:01 2017
  gtk-update-icon-cache (3.22.24-0ubuntu1, 3.22.25-0ubuntu0.1) Upgraded at Fri 
Nov 17 00:44:01 2017
  accountsservice (0.6.42-0ubuntu3, 0.6.42-0ubuntu3.1) Upgraded at Fri Nov 17 
00:44:01 2017
  libaccountsservice0 (0.6.42-0ubuntu3, 0.6.42-0ubuntu3.1) Upgraded at Fri Nov 
17 00:44:01 2017

  version.log and lspci-vnvn.log are attatched.  I received a 'pcilib:
  sysfs_read_vpd: read failed: Input/output error' on the lspci
  commnand, so it may not be complete.

  Ok, I can only attatch one file, so version.log reads:
  Ubuntu 4.13.0-16.19-generic 4.13.4

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

-- 
Mailing list: https://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 1733357] [NEW] System won't go into suspend mode.

[lnxusr]

Public bug reported:

Since the following updates installed on Friday Nov 17 my system will no
longer go into suspend or hibernate via the keybord or the logout screen
when Suspend is selected.  It will, however, suspend via the command
line with pm-syspend or pm-suspend-hybrid.

As a temp workaround, I've added pm-suspend-hybrid to my sudoers and
reconfigured the Sleep button in a custom shortcut.

Packages installed Friday:

code (1.18.0-1510145176, 1.18.1-1510857349) Upgraded at Fri Nov 17 23:36:07 2017
gir1.2-gtk-3.0 (3.22.24-0ubuntu1, 3.22.25-0ubuntu0.1) Upgraded at Fri Nov 17 
00:44:01 2017
libgtk-3-common (3.22.24-0ubuntu1, 3.22.25-0ubuntu0.1) Upgraded at Fri Nov 17 
00:44:01 2017
libgtk-3-0 (3.22.24-0ubuntu1, 3.22.25-0ubuntu0.1) Upgraded at Fri Nov 17 
00:44:01 2017
libgtk-3-bin (3.22.24-0ubuntu1, 3.22.25-0ubuntu0.1) Upgraded at Fri Nov 17 
00:44:01 2017
gtk-update-icon-cache (3.22.24-0ubuntu1, 3.22.25-0ubuntu0.1) Upgraded at Fri 
Nov 17 00:44:01 2017
accountsservice (0.6.42-0ubuntu3, 0.6.42-0ubuntu3.1) Upgraded at Fri Nov 17 
00:44:01 2017
libaccountsservice0 (0.6.42-0ubuntu3, 0.6.42-0ubuntu3.1) Upgraded at Fri Nov 17 
00:44:01 2017

version.log and lspci-vnvn.log are attatched.  I received a 'pcilib:
sysfs_read_vpd: read failed: Input/output error' on the lspci commnand,
so it may not be complete.

Ok, I can only attatch one file, so version.log reads:
Ubuntu 4.13.0-16.19-generic 4.13.4

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

** Attachment added: "lspci-vnvn.log"
   
https://bugs.launchpad.net/bugs/1733357/+attachment/5011729/+files/lspci-vnvn.log

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

Title:
  System won't go into suspend mode.

Status in linux package in Ubuntu:
  New

Bug description:
  Since the following updates installed on Friday Nov 17 my system will
  no longer go into suspend or hibernate via the keybord or the logout
  screen when Suspend is selected.  It will, however, suspend via the
  command line with pm-syspend or pm-suspend-hybrid.

  As a temp workaround, I've added pm-suspend-hybrid to my sudoers and
  reconfigured the Sleep button in a custom shortcut.

  Packages installed Friday:

  code (1.18.0-1510145176, 1.18.1-1510857349) Upgraded at Fri Nov 17 23:36:07 
2017
  gir1.2-gtk-3.0 (3.22.24-0ubuntu1, 3.22.25-0ubuntu0.1) Upgraded at Fri Nov 17 
00:44:01 2017
  libgtk-3-common (3.22.24-0ubuntu1, 3.22.25-0ubuntu0.1) Upgraded at Fri Nov 17 
00:44:01 2017
  libgtk-3-0 (3.22.24-0ubuntu1, 3.22.25-0ubuntu0.1) Upgraded at Fri Nov 17 
00:44:01 2017
  libgtk-3-bin (3.22.24-0ubuntu1, 3.22.25-0ubuntu0.1) Upgraded at Fri Nov 17 
00:44:01 2017
  gtk-update-icon-cache (3.22.24-0ubuntu1, 3.22.25-0ubuntu0.1) Upgraded at Fri 
Nov 17 00:44:01 2017
  accountsservice (0.6.42-0ubuntu3, 0.6.42-0ubuntu3.1) Upgraded at Fri Nov 17 
00:44:01 2017
  libaccountsservice0 (0.6.42-0ubuntu3, 0.6.42-0ubuntu3.1) Upgraded at Fri Nov 
17 00:44:01 2017

  version.log and lspci-vnvn.log are attatched.  I received a 'pcilib:
  sysfs_read_vpd: read failed: Input/output error' on the lspci
  commnand, so it may not be complete.

  Ok, I can only attatch one file, so version.log reads:
  Ubuntu 4.13.0-16.19-generic 4.13.4

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

-- 
Mailing list: https://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 1730188] Re: linux-image-4.4.0-98 kernel panic

[Joseph Salisbury]

** Tags removed: kernel-key
** Tags added: kernel-da-key

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

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

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

Title:
  linux-image-4.4.0-98 kernel panic

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

Bug description:
  Since updating to linux-image-4.4.0-98-generic 2 days ago, I get a kernel 
panic during boot. With 4.4.0-97 the machine boots fine. Screenshot attached.
  --- 
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jos1929 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=5577332d-7a0a-4c5a-9c10-93a5cd6f5e65
  InstallationDate: Installed on 2013-01-05 (1764 days ago)
  InstallationMedia: This
  Lsusb:
   Bus 002 Device 003: ID 04f2:b34c Chicony Electronics Co., Ltd 
   Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
   Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: wortmann TERRA MOBILE 1512/1712
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-97-generic 
root=UUID=b9e9b26b-d84a-494e-921d-31e5e92726eb ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-97.120-generic 4.4.87
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-97-generic N/A
   linux-backports-modules-4.4.0-97-generic  N/A
   linux-firmware1.157.13
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  Tags:  xenial
  Uname: Linux 4.4.0-97-generic x86_64
  UpgradeStatus: Upgraded to xenial on 2016-08-07 (454 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/22/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 4.6.5
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: TERRA MOBILE 1512/1712
  dmi.board.vendor: Wortmann AG
  dmi.board.version: V3.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Wortmann AG
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd10/22/2012:svnwortmann:pnTERRAMOBILE1512/1712:pvrNotApplicable:rvnWortmannAG:rnTERRAMOBILE1512/1712:rvrV3.0:cvnWortmannAG:ct10:cvrN/A:
  dmi.product.name: TERRA MOBILE 1512/1712
  dmi.product.version: Not Applicable
  dmi.sys.vendor: wortmann

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

-- 
Mailing list: https://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 1730596] Re: s390/mm: fix write access check in gup_huge_pmd()

[Joseph Salisbury]

** Tags removed: kernel-key
** Tags added: kernel-da-key

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

Title:
  s390/mm: fix write access check in gup_huge_pmd()

Status in Ubuntu on IBM z Systems:
  Fix Released
Status in linux package in Ubuntu:
  Fix Committed
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 Committed
Status in linux source package in Bionic:
  Fix Committed

Bug description:
  == SRU Justification ==
  The check for the _SEGMENT_ENTRY_PROTECT bit in gup_huge_pmd() is the
  wrong way around. It must not be set for write==1, and not be checked for
  write==0. Fix this similar to how it was fixed for ptes long time ago in
  commit 25591b0 ("[S390] fix get_user_pages_fast").

  One impact of this bug would be unnecessarily using the gup slow path for
  write==0 on r/w mappings. A potentially more severe impact would be that
  gup_huge_pmd() will succeed for write==1 on r/o mappings.

  This bug is fixed by mainline commit ba385c0594, which is in mainline
  as of v4.14-rc2.  It was also cc'd to upstream stable.  It has already
  been accepted in upstream v4.13.y, so Artful and Bionic have the fix
  via the 4.13.5 stable updates.

  == Fix ==
  commit ba385c0594e723d41790ecfb12c610e6f90c7785
  Author: Gerald Schaefer 
  Date:   Mon Sep 18 16:51:51 2017 +0200

  s390/mm: fix write access check in gup_huge_pmd()

  
  == Regression Potential ==
  This patch is specific to s390.  It has also been accepted by upstream 
stable, so additional upstream review has been done.


  
  Addl information

  Problem: The check for the _SEGMENT_ENTRY_PROTECT bit in
    gup_huge_pmd() is the wrong way around. It must not be set
    for write==1, and not be checked for write==0. Allowing
    write==1 with protection bit set, instead of breaking out
    to the slow path, will result in a missing faultin_page()
    to clear the protection bit (for valid writable mappings),
    and the async I/O write operation will fail to write to
    such a mapping.
  Solution: Fix it by correctly checking the protection bit like it is
    also done in gup_pte_range() and gup_huge_pud().
  Reproduction: Async I/O workload on buffers that are mapped as transparent
    hugepages.
  Upstream-ID:  ba385c0594e723d41790ecfb12c610e6f90c7785

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

-- 
Mailing list: https://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 1732978] Re: Ubuntu 17.10: Include patch "crypto: vmx - Use skcipher for ctr fallback"

[Joseph Salisbury]

I built a 17.10 test kernel with a pick of commit e666d4e9ceec94.  The
test kernel can be downloaded from:

http://kernel.ubuntu.com/~jsalisbury/lp1732978/

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

Title:
  Ubuntu 17.10: Include patch "crypto: vmx - Use skcipher for ctr
  fallback"

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

Bug description:
  == Comment: #0 - Paulo Flabiano Smorigo  - 2017-11-17 
10:29:14 ==
  Ubuntu 17.10 uses linux kernel 4.13 witch has a problem with the fallback 
cipher for CTR mode. The commit bellow fixes this problem by using the new 
structure for the generic ciphers. Please add it to the kernel package.

  
https://git.kernel.org/pub/scm/linux/kernel/git/herbert/crypto-2.6.git/commit/?id=e666d4e9ceec94c0a88c94b7db31d56474da43b3

  == Comment: #1 - VIPIN K. PARASHAR  - 2017-11-17 
13:38:05 ==
  (In reply to comment #0)
  > Ubuntu 17.10 uses linux kernel 4.13 witch has a problem with the fallback
  > cipher for CTR mode. The commit bellow fixes this problem by using the new
  > structure for the generic ciphers. Please add it to the kernel package.
  > 
  > https://git.kernel.org/pub/scm/linux/kernel/git/herbert/crypto-2.6.git/
  > commit/?id=e666d4e9ceec94c0a88c94b7db31d56474da43b3

  Which is commit e666d4e9ceec94

  commit e666d4e9ceec94c0a88c94b7db31d56474da43b3
  Author: Paulo Flabiano Smorigo 
  Date:   Mon Oct 16 20:54:19 2017 -0200

  crypto: vmx - Use skcipher for ctr fallback
  
  Signed-off-by: Paulo Flabiano Smorigo 
  Signed-off-by: Herbert Xu 

  Its available with 4.14 kernel.

  
  Hello Canonical,

  Please include commit e666d4e9ceec94 - "crypto: vmx - Use skcipher for ctr 
fallback"
  with Ubuntu 17.10 kernel.

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

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

Re: [Kernel-packages] [Bug 1729674] Re: TB16 dock ethernet corrupts data with hw checksum silently failing

[Dave Chiluk]

I reviewed your patch, and it appears as if it only turns off receive
checksumming. The internets are saying that transmit needs to be turned off
as well.  Have you checked to see if transmit is affected as well?

I will try to do some transmit tests.  I'll also "test" your kernel when I
get a chance, but by the looks of the patch there shouldn't be too much to
test as it simply turns off RX checksuming which is already a known good
solution.

On Mon, Nov 20, 2017 at 2:06 AM, Kai-Heng Feng 
wrote:

> Dave,
>
> Please try this kernel,
> http://people.canonical.com/~khfeng/lp1729674/
>
> The temporary workaround is what we can get before chip vendors solve
> the issue.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1729674
>
> Title:
>   TB16 dock ethernet corrupts data with hw checksum silently failing
>
> Status in Dell Sputnik:
>   Triaged
> Status in linux package in Ubuntu:
>   In Progress
> Status in linux package in Fedora:
>   Confirmed
>
> Bug description:
>   It looks like TCP  rx and tx checksum offloading is broken on the TB16
> dock's ethernet adapter. For example downloading a large file such as the
> Ubuntu ISO, and then running an md5sum on it yields the incorrect md5sum.
> This is because
>   rx-checksumming: on
>   tx-checksumming: on
>   and both set to on by default.
>
>   Running sudo ethtool -K  tx off rx off, allows the
>   download to complete correctly.  This is very bad since this can cause
>   very bad untrustworthy behavior.
>
>   This was conducted using an Dell Precision 5520 on Ubuntu 16.04+linux-
>   generic-hwe-16.04-edge.
>
>   Thank you
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/dell-sputnik/+bug/1729674/+subscriptions
>

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

Title:
  TB16 dock ethernet corrupts data with hw checksum silently failing

Status in Dell Sputnik:
  Triaged
Status in linux package in Ubuntu:
  In Progress
Status in linux package in Fedora:
  Confirmed

Bug description:
  It looks like TCP  rx and tx checksum offloading is broken on the TB16 dock's 
ethernet adapter. For example downloading a large file such as the Ubuntu ISO, 
and then running an md5sum on it yields the incorrect md5sum.  This is because
  rx-checksumming: on
  tx-checksumming: on
  and both set to on by default.

  Running sudo ethtool -K  tx off rx off, allows the
  download to complete correctly.  This is very bad since this can cause
  very bad untrustworthy behavior.

  This was conducted using an Dell Precision 5520 on Ubuntu 16.04+linux-
  generic-hwe-16.04-edge.

  Thank you

To manage notifications about this bug go to:
https://bugs.launchpad.net/dell-sputnik/+bug/1729674/+subscriptions

-- 
Mailing list: https://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 1732945] Re: Kernel Oops - unable to handle kernel NULL pointer dereference at (null); tty_poll+0x55/0x90

[Joseph Salisbury]

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

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

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

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

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


Thanks in advance.

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


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

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

** Tags added: kernel-da-key

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

Title:
  Kernel Oops - unable to handle kernel NULL pointer dereference at
  (null); tty_poll+0x55/0x90

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I have an ubuntu server 16.04.3 running 4.4.0-98-generic.  It randomly
  hangs and requires a hard power cycle.  I have managed to capture the
  following Kernel Oops from the log but I unsure what the cause is.

  Nov 17 15:07:47 server1 kernel: [39934.913759] BUG: unable to handle kernel 
NULL pointer dereference at   (null)
  Nov 17 15:07:47 server1 kernel: [39934.913767] IP: [] 
tty_poll+0x55/0x90
  Nov 17 15:07:47 server1 kernel: [39934.913775] PGD 7197ed067 PUD 6d7040067 
PMD 0 
  Nov 17 15:07:47 server1 kernel: [39934.913781] Oops:  [#1] SMP 
  Nov 17 15:07:47 server1 kernel: [39934.913785] Modules linked in: ipmi_si 
pci_stub vboxpci(OE) vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) xt_multiport 
mpt3sas raid_class scsi_transport_sas mptctl mptbase ip_gre ip_tunnel gre 
dell_rbu ipt_REJECT nf_reject_ipv4 xt_tcpudp xt_iprange xt_conntrack 
iptable_filter iptable_mangle iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 
nf_nat_ipv4 nf_nat nf_conntrack ip_tables x_tables binfmt_misc joydev 
input_leds ipmi_ssif ipmi_devintf hid_generic gpio_ich usbhid dcdbas hid 
intel_powerclamp kvm_intel kvm irqbypass i7core_edac edac_core lpc_ich shpchp 
ipmi_msghandler 8250_fintek mac_hid acpi_power_meter coretemp parport_pc ppdev 
sunrpc lp parport autofs4 bnx2 megaraid_sas wmi fjes [last unloaded: ipmi_si]
  Nov 17 15:07:47 server1 kernel: [39934.913819] CPU: 0 PID: 22392 Comm: telnet 
Tainted: G   OE   4.4.0-98-generic #121-Ubuntu
  Nov 17 15:07:47 server1 kernel: [39934.913821] Hardware name: Dell Inc. 
PowerEdge R310/05XKKK, BIOS 1.12.0 09/06/2013
  Nov 17 15:07:47 server1 kernel: [39934.913822] task: 8808140fa640 ti: 
8806d16c task.ti: 8806d16c
  Nov 17 15:07:47 server1 kernel: [39934.913823] RIP: 0010:[] 
 [] tty_poll+0x55/0x90
  Nov 17 15:07:47 server1 kernel: [39934.913826] RSP: 0018:8806d16c3978  
EFLAGS: 00010246
  Nov 17 15:07:47 server1 kernel: [39934.913827] RAX:  RBX: 
88071f498700 RCX: 0009
  Nov 17 15:07:47 server1 kernel: [39934.913828] RDX: 8000 RSI: 
 RDI: 88071943ac28
  Nov 17 15:07:47 server1 kernel: [39934.913829] RBP: 8806d16c39a0 R08: 
88071f498700 R09: 88071f498700
  Nov 17 15:07:47 server1 kernel: [39934.913830] R10: 0001009732b3 R11: 
 R12: 88071943ac00
  Nov 17 15:07:47 server1 kernel: [39934.913831] R13:  R14: 
8806d16c3aa0 R15: 
  Nov 17 15:07:47 server1 kernel: [39934.913832] FS:  7f2d745ec740() 
GS:88081ee0() knlGS:
  Nov 17 15:07:47 server1 kernel: [39934.913834] CS:  0010 DS:  ES:  
CR0: 80050033
  Nov 17 15:07:47 server1 kernel: [39934.913835] CR2:  CR3: 
0007b3e7 CR4: 26f0
  Nov 17 15:07:47 server1 kernel: [39934.913836] Stack:
  Nov 17 15:07:47 server1 kernel: [39934.913837]  0009 
0040  0001
  Nov 17 15:07:47 server1 kernel: [39934.913838]  0004 
8806d16c3d48 81225873 880814379400
  Nov 17 15:07:47 server1 kernel: [39934.913840]  8806d16c4000 
  8808140fa640
  Nov 17 15:07:47 server1 kernel: [39934.913842] Call Trace:
  Nov 17 15:07:47 server1 kernel: [39934.913846]  [] 
do_select+0x383/0x810
  Nov 17 15:07:47 server1 kernel: [39934.913850]  [] ? 
__dev_queue_xmit+0x286/0x590
  Nov 17 15:07:47 server1 kernel: [39934.913852]  [] ? 
poll_select_copy_remaining+0x140/0x140
  Nov 17 15:07:47 server1 kernel: [39934.913853]  [] ? 
poll_select_copy_remaining+0x140/0x140
  Nov 17 15:07:47 server1 kernel: [39934.913855]  [] ? 
poll_select_copy_remaining+0x140/0x140
  Nov 17 15:07:47 server1 kernel: [39934.913858]  [] ? 
enqueue_task_fair+0xaa/0x8b0
  Nov 17 

[Kernel-packages] [Bug 1733060] Re: Touchpad doesn't work after wake from sleep on HP Pavilion x2 Detachable

[Joseph Salisbury]

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

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

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

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

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


Thanks in advance.

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


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

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

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

Title:
  Touchpad doesn't work after wake from sleep on HP Pavilion x2
  Detachable

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  After waking the laptop from screen, the touchpad does not work. It
  does not react to single finger movement or tapping, nor to two finger
  scroll, nor to pressing down the clickpad left or right. The laptop
  has a detachable screen for use as a tablet. After detaching the
  screen and reattaching the screen the touchpad works again as
  expected.

  I've tried it now a few times and I can reliably reproduce the touchpad 
problem as follows:
  - close the lid, 
  - wait for the led to indicated sleeping. 
  - Open the lid. 
  - Hit enter (otherwise the screen stays dark). 
  - Enter password to unlock using the keyboard. 
  - Try keyboard and touchpad to see whether they work. 
  - It they don't work 
- Pull the screen off of the keyboard base with the integrated touchpad. 
- Reconnect 
- Try keyboard and touchpad again  

  A few attempts below with approximate times. Should be visible in the
  syslog for Nov 18

  NB: In one of these tests the keyboard didn't work after
  disconnect/reconnect. But that is not a persistent problem. I don't
  remember having seen that before, nor was I able to reproduce it a
  second time.

  --
  close lid 10:14:55
  open 
  -> keyboard works
  -> touchpad doesnt work
  disconnect 10:25:09
  reconnect 
  -> keyboard doesnt work
  -> touchpad doesnt work
  disconnect 
  reconnect 
  -> keyboard works
  -> touchpad works 

  --
  close lid 10:39:20
  open 
  -> keyboard works
  -> touchpad doesn't work 
  disconnect 10:41:11
  reconnect 
  -> keyboard works
  -> touchpad works

  --
  close lid 10:47:50
  open 
  -> keyboard works
  -> touchpad doesnt work
  disconnect 10:48:37
  reconnect 
  -> keyboard works
  -> touchpad works

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-16-generic 4.13.0-16.19 [modified: 
boot/vmlinuz-4.13.0-16-generic]
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  peter  1195 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Nov 18 10:50:00 2017
  HibernationDevice: RESUME=UUID=ccc9dd4a-8423-499f-8e57-022be496cfa6
  InstallationDate: Installed on 2017-11-05 (12 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  MachineType: HP HP Pavilion x2 Detachable
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic.efi.signed 
root=UUID=c516cd88-8b77-434a-813a-799e0380a4eb ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-16-generic N/A
   linux-backports-modules-4.13.0-16-generic  N/A
   linux-firmware 1.169
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/14/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F.13
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 8181
  dmi.board.vendor: HP
  dmi.board.version: 42.25
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF.13:bd03/14/2016:svnHP:pnHPPavilionx2Detachable:pvr:rvnHP:rn8181:rvr42.25:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV G=N L=CON B=HP S=SPT
  dmi.product.name: HP Pavilion x2 Detachable
  dmi.sys.vendor: HP

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

-- 
Mailing list: https://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 1732978] Re: Ubuntu 17.10: Include patch "crypto: vmx - Use skcipher for ctr fallback"

[Andrew Cloke]

** Tags added: triage-g

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

Title:
  Ubuntu 17.10: Include patch "crypto: vmx - Use skcipher for ctr
  fallback"

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

Bug description:
  == Comment: #0 - Paulo Flabiano Smorigo  - 2017-11-17 
10:29:14 ==
  Ubuntu 17.10 uses linux kernel 4.13 witch has a problem with the fallback 
cipher for CTR mode. The commit bellow fixes this problem by using the new 
structure for the generic ciphers. Please add it to the kernel package.

  
https://git.kernel.org/pub/scm/linux/kernel/git/herbert/crypto-2.6.git/commit/?id=e666d4e9ceec94c0a88c94b7db31d56474da43b3

  == Comment: #1 - VIPIN K. PARASHAR  - 2017-11-17 
13:38:05 ==
  (In reply to comment #0)
  > Ubuntu 17.10 uses linux kernel 4.13 witch has a problem with the fallback
  > cipher for CTR mode. The commit bellow fixes this problem by using the new
  > structure for the generic ciphers. Please add it to the kernel package.
  > 
  > https://git.kernel.org/pub/scm/linux/kernel/git/herbert/crypto-2.6.git/
  > commit/?id=e666d4e9ceec94c0a88c94b7db31d56474da43b3

  Which is commit e666d4e9ceec94

  commit e666d4e9ceec94c0a88c94b7db31d56474da43b3
  Author: Paulo Flabiano Smorigo 
  Date:   Mon Oct 16 20:54:19 2017 -0200

  crypto: vmx - Use skcipher for ctr fallback
  
  Signed-off-by: Paulo Flabiano Smorigo 
  Signed-off-by: Herbert Xu 

  Its available with 4.14 kernel.

  
  Hello Canonical,

  Please include commit e666d4e9ceec94 - "crypto: vmx - Use skcipher for ctr 
fallback"
  with Ubuntu 17.10 kernel.

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

-- 
Mailing list: https://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 1733070] Re: ntp apparmor profile problem

[Joseph Salisbury]

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

** Changed in: apparmor (Ubuntu)
   Status: Confirmed => 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/1733070

Title:
  ntp apparmor profile problem

Status in apparmor package in Ubuntu:
  New

Bug description:
  the apparmor logs shows a couple of problems:

  Nov 18 13:07:45 carol kernel: [107615.254389] audit: type=1400
  audit(1511010465.396:304): apparmor="DENIED" operation="sendmsg"
  info="Failed name lookup - disconnected path" error=-13
  profile="/usr/sbin/ntpd" name="run/systemd/journal/dev-log" pid=16818
  comm="ntpd" requested_mask="w" denied_mask="w" fsuid=0 ouid=0

  
  and

  Nov 18 13:07:45 carol kernel: [107615.253441] audit: type=1400
  audit(1511010465.395:300): apparmor="DENIED" operation="open"
  profile="/usr/sbin/ntpd" name="/usr/local/bin/" pid=16815 comm="ntpd"
  requested_mask="r" denied_mask="r" fsuid=0 ouid=0


  I fixed these by amending /etc/apparmor.d/usr.sbin.ntpd...

  change the opening to this:
/usr/sbin/ntpd flags=(attach_disconnected) {

  
  add these:
# syslog
/run/systemd/journal/dev-log w,

# not sure why it needs this
/usr/local/bin/ r,

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

-- 
Mailing list: https://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 1733194] Re: kernel NULL pointer dereference in iwlmvm iwl_mvm_enable_txq

[Joseph Salisbury]

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

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

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

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

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


Thanks in advance.

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


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

Title:
  kernel NULL pointer dereference in iwlmvm iwl_mvm_enable_txq

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  When in AP mode after some time, get this BUG:

  Nov 18 23:21:31 bifrost kernel: [18345.860393] BUG: unable to handle kernel 
NULL pointer dereference at 0070
  Nov 18 23:21:31 bifrost kernel: [18345.860552] IP: 
iwl_trans_pcie_txq_enable+0x62/0x440 [iwlwifi]
  Nov 18 23:21:31 bifrost kernel: [18345.860644] PGD 0
  Nov 18 23:21:31 bifrost kernel: [18345.860646] P4D 0
  Nov 18 23:21:31 bifrost kernel: [18345.860682]
  Nov 18 23:21:31 bifrost kernel: [18345.860747] Oops: 0002 [#1] SMP
  Nov 18 23:21:31 bifrost kernel: [18345.860800] Modules linked in: 
nfnetlink_queue nfnetlink_log nfnetlink dummy ufs qnx4 hfsplus hfs minix ntfs 
msdos jfs xfs ccm xfrm_user xfrm4_tunnel tunnel4 ipcomp xfrm_ipcomp esp4 ah4 
af_key xfrm_algo xt_policy xt_multiport ip6table_filter ip6_tables 
ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_nat_ipv4 nf_nat ipt_REJECT 
nf_reject_ipv4 xt_tcpudp nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack 
nf_conntrack iptable_filter nls_iso8859_1 cmdlinepart intel_spi_platform 
intel_spi spi_nor mtd arc4 intel_rapl intel_soc_dts_thermal intel_soc_dts_iosf 
intel_powerclamp coretemp kvm_intel bridge kvm stp llc iwlmvm irqbypass 
punit_atom_debug mac80211 intel_cstate snd_hda_codec_hdmi iwlwifi 
snd_hda_codec_realtek snd_hda_codec_generic cfg80211 btusb snd_hda_intel 
lpc_ich btrtl snd_hda_codec snd_intel_sst_acpi
  Nov 18 23:21:31 bifrost kernel: [18345.861897]  mei_txe snd_hda_core mei 
snd_hwdep shpchp snd_intel_sst_core snd_soc_sst_atom_hifi2_platform hci_uart 
snd_soc_sst_match snd_soc_core btbcm serdev snd_compress btqca ac97_bus btintel 
snd_pcm_dmaengine snd_pcm dw_dmac dw_dmac_core snd_timer bluetooth snd 
soundcore mac_hid intel_int0002_vgpio ecdh_generic spi_pxa2xx_platform 
rfkill_gpio pwm_lpss_platform pwm_lpss 8250_dw ib_iser rdma_cm iw_cm ib_cm 
ib_core iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi ip_tables x_tables 
autofs4 btrfs raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor 
async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear i915 
drm_kms_helper crct10dif_pclmul igb syscopyarea sysfillrect crc32_pclmul 
sysimgblt fb_sys_fops dca ghash_clmulni_intel i2c_algo_bit cryptd ahci ptp drm 
pps_core libahci video
  Nov 18 23:21:31 bifrost kernel: [18345.862995]  i2c_hid hid sdhci_acpi sdhci
  Nov 18 23:21:31 bifrost kernel: [18345.863068] CPU: 1 PID: 1202 Comm: 
kworker/1:2 Tainted: GW   4.13.0-16-generic #19-Ubuntu
  Nov 18 23:21:31 bifrost kernel: [18345.863203] Hardware name: NF541 
NF541/NF541, BIOS BAR1NA02 02/25/2016
  Nov 18 23:21:31 bifrost kernel: [18345.863326] Workqueue: events 
iwl_mvm_add_new_dqa_stream_wk [iwlmvm]
  Nov 18 23:21:31 bifrost kernel: [18345.863428] task: 96862c1c5800 
task.stack: a98a817c
  Nov 18 23:21:31 bifrost kernel: [18345.863539] RIP: 
0010:iwl_trans_pcie_txq_enable+0x62/0x440 [iwlwifi]
  Nov 18 23:21:31 bifrost kernel: [18345.863635] RSP: 0018:a98a817c3be0 
EFLAGS: 00010246
  Nov 18 23:21:31 bifrost kernel: [18345.863718] RAX: 09c4 RBX: 
001f RCX: 
  Nov 18 23:21:31 bifrost kernel: [18345.863824] RDX:  RSI: 
001f RDI: 2710
  Nov 18 23:21:31 bifrost kernel: [18345.863932] RBP: a98a817c3c30 R08: 
2710 R09: 0001
  Nov 18 23:21:31 bifrost kernel: [18345.864039] R10:  R11: 
9686344ce010 R12: 
  Nov 18 23:21:31 bifrost kernel: [18345.864145] R13: 96862c9d0018 R14: 
 R15: 
  Nov 18 23:21:31 bifrost kernel: [18345.864253] FS:  () 
GS:96863fc8() knlGS:
  Nov 18 23:21:31 bifrost kernel: [18345.864373] CS:  0010 DS:  ES:  
CR0: 80050033
  Nov 18 23:21:31 bifrost kernel: [18345.864461] CR2: 0070 CR3: 
00023068b000 CR4: 001006e0
  Nov 18 23:21:31 bifrost kernel: [18345.864568] Call Trace:
  Nov 18 23:21:31 

[Kernel-packages] [Bug 1733306] Re: FS-Cache: Assertion failed

[Joseph Salisbury]

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

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

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

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


Thanks in advance.

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

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

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

** Tags added: kernel-da-key

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

Title:
  FS-Cache: Assertion failed

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I'm encountering many random kernel panic after enabling fsc with NFS.
  Then I see a number of following err msgs right before it crashed.

  Nov 20 12:04:26 g2 kernel: [170689.549374] FS-Cache: 
  Nov 20 12:04:26 g2 kernel: [170689.549381] FS-Cache: Assertion failed
  Nov 20 12:04:26 g2 kernel: [170689.549384] FS-Cache: 6 == 5 is false
  Nov 20 12:04:26 g2 kernel: [170689.549439] [ cut here 
]
  Nov 20 12:04:26 g2 kernel: [170689.549490] kernel BUG at 
/build/linux-3phnTq/linux-4.4.0/fs/fscache/operation.c:494!
  Nov 20 12:04:26 g2 kernel: [170689.549557] invalid opcode:  [#1] SMP 
  Nov 20 12:04:26 g2 kernel: [170689.549598] Modules linked in: veth xt_nat 
xt_tcpudp ipt_MASQUERADE nf_nat_masquerade_ipv4 nf_conntrack_netlink nfnetlink 
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 bridge stp llc aufs cachefiles ipmi_devintf rpcsec_gss_krb5 
auth_rpcgss nfsv4 nfs lockd grace fscache snd_hda_codec_hdmi intel_rapl 
x86_pkg_temp_thermal intel_powerclamp kvm_intel kvm ipmi_ssif irqbypass 
serio_raw joydev input_leds snd_hda_intel snd_hda_codec snd_hda_core snd_hwdep 
snd_pcm nvidia_uvm(POE) sb_edac snd_seq_midi snd_seq_midi_event edac_core 
snd_rawmidi snd_seq snd_seq_device snd_timer snd soundcore mei_me lpc_ich mei 
shpchp wmi ipmi_si 8250_fintek ipmi_msghandler acpi_pad acpi_power_meter 
mac_hid sunrpc ib_iser rdma_cm iw_cm ib_cm ib_sa ib_mad ib_core ib_addr 
iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi nct6775 hwmon_vid coretemp 
bonding parport_pc ppdev lp parport autofs4 xfs btrfs raid10 raid456 
async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq 
libcrc32c raid1 raid0 multipath linear nvidia_drm(POE) nvidia_modeset(POE) 
hid_generic crct10dif_pclmul ast crc32_pclmul ghash_clmulni_intel aesni_intel 
aes_x86_64 lrw gf128mul nvidia(POE) glue_helper ttm ablk_helper igb cryptd 
drm_kms_helper psmouse syscopyarea dca sysfillrect ptp sysimgblt fb_sys_fops 
pps_core ahci i2c_algo_bit drm libahci fjes usbhid hid
  Nov 20 12:04:26 g2 kernel: [170689.550993] CPU: 22 PID: 6373 Comm: 
kworker/u98:1 Tainted: P   OE   4.4.0-98-generic #121-Ubuntu
  Nov 20 12:04:26 g2 kernel: [170689.551071] Hardware name: ASUSTeK COMPUTER 
INC. ESC8000 G3 Series/Z10PG-D24 Series, BIOS 3203 05/05/2016
  Nov 20 12:04:26 g2 kernel: [170689.551160] Workqueue: fscache_operation 
fscache_op_work_func [fscache]
  Nov 20 12:04:26 g2 kernel: [170689.551219] task: 882027887000 ti: 
881429ea4000 task.ti: 881429ea4000
  Nov 20 12:04:26 g2 kernel: [170689.551283] RIP: 0010:[]  
[] fscache_put_operation+0x1d6/0x210 [fscache]
  Nov 20 12:04:26 g2 kernel: [170689.551374] RSP: 0018:881429ea7de0  
EFLAGS: 00010282
  Nov 20 12:04:26 g2 kernel: [170689.551421] RAX: 0019 RBX: 
882037224300 RCX: 0006
  Nov 20 12:04:26 g2 kernel: [170689.551490] RDX:  RSI: 
0246 RDI: 88203f28dd50
  Nov 20 12:04:26 g2 kernel: [170689.551551] RBP: 881429ea7df8 R08: 
000a R09: 09c0
  Nov 20 12:04:26 g2 kernel: [170689.551611] R10: 88120db1b300 R11: 
09c0 R12: 882038bf8000
  Nov 20 12:04:26 g2 kernel: [170689.551672] R13: 88202ff08800 R14: 
0c40 R15: 882037224300
  Nov 20 12:04:26 g2 kernel: [170689.551733] FS:  () 
GS:88203f28() knlGS:
  Nov 20 12:04:26 g2 kernel: [170689.551801] CS:  0010 DS:  ES:  CR0: 
80050033
  Nov 20 12:04:26 g2 kernel: [170689.551850] CR2: 7f66b2887500 CR3: 
01e0a000 CR4: 003406e0
  Nov 20 12:04:26 g2 kernel: [170689.551912] DR0:  DR1: 
 DR2: 
  Nov 20 12:04:26 g2 kernel: [170689.551972] DR3:  DR6: 
fffe0ff0 DR7: 0400
  Nov 20 12:04:26 g2 kernel: [170689.552030] Stack:
  Nov 20 12:04:26 g2 kernel: [170689.552051]  

[Kernel-packages] [Bug 1733321] Re: network-manager ADT tests fail with on ppc64el with artful/linux 4.13.0.17.18

[Joseph Salisbury]

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

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

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

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

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

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

Title:
  network-manager ADT tests fail with on ppc64el with artful/linux
  4.13.0.17.18

Status in linux package in Ubuntu:
  Triaged
Status in linux source package in Artful:
  Triaged

Bug description:
  ppc64el ADT log:
  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
  /autopkgtest-artful/artful/ppc64el/n/network-
  manager/20171120_100719_28642@/log.gz

  Testcase output:
  -
  autopkgtest [10:04:48]: test killswitches-no-urfkill: [---
  make -C /lib/modules/4.13.0-17-generic/build 
KBUILD_SRC=/lib/modules/4.13.0-17-generic/build 
M=/tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests
  make[1]: Entering directory '/usr/src/linux-headers-4.13.0-17-generic'
AR  /tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests/built-in.o
CC [M]  /tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests/fake-rfkill.o
Building modules, stage 2.
MODPOST 1 modules
CC  /tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests/fake-rfkill.mod.o
LD [M]  /tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests/fake-rfkill.ko
  make[1]: Leaving directory '/usr/src/linux-headers-4.13.0-17-generic'
  ERROR: NM could not track device state.
  autopkgtest [10:05:20]: test killswitches-no-urfkill: ---]
  autopkgtest [10:05:20]: test killswitches-no-urfkill:  - - - - - - - - - - 
results - - - - - - - - - -
  killswitches-no-urfkill FAIL non-zero exit status 1
  -

  Package versions [artful/ppc64el]:
  network-manager 1.8.4-1ubuntu3
  linux-meta 4.13.0.17.18

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

-- 
Mailing list: https://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 1732978] Re: Ubuntu 17.10: Include patch "crypto: vmx - Use skcipher for ctr fallback"

[bugproxy]

** Tags removed: bugnameltc-161493 kernel-da-key severity-high triage-g

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

Title:
  Ubuntu 17.10: Include patch "crypto: vmx - Use skcipher for ctr
  fallback"

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

Bug description:
  == Comment: #0 - Paulo Flabiano Smorigo  - 2017-11-17 
10:29:14 ==
  Ubuntu 17.10 uses linux kernel 4.13 witch has a problem with the fallback 
cipher for CTR mode. The commit bellow fixes this problem by using the new 
structure for the generic ciphers. Please add it to the kernel package.

  
https://git.kernel.org/pub/scm/linux/kernel/git/herbert/crypto-2.6.git/commit/?id=e666d4e9ceec94c0a88c94b7db31d56474da43b3

  == Comment: #1 - VIPIN K. PARASHAR  - 2017-11-17 
13:38:05 ==
  (In reply to comment #0)
  > Ubuntu 17.10 uses linux kernel 4.13 witch has a problem with the fallback
  > cipher for CTR mode. The commit bellow fixes this problem by using the new
  > structure for the generic ciphers. Please add it to the kernel package.
  > 
  > https://git.kernel.org/pub/scm/linux/kernel/git/herbert/crypto-2.6.git/
  > commit/?id=e666d4e9ceec94c0a88c94b7db31d56474da43b3

  Which is commit e666d4e9ceec94

  commit e666d4e9ceec94c0a88c94b7db31d56474da43b3
  Author: Paulo Flabiano Smorigo 
  Date:   Mon Oct 16 20:54:19 2017 -0200

  crypto: vmx - Use skcipher for ctr fallback
  
  Signed-off-by: Paulo Flabiano Smorigo 
  Signed-off-by: Herbert Xu 

  Its available with 4.14 kernel.

  
  Hello Canonical,

  Please include commit e666d4e9ceec94 - "crypto: vmx - Use skcipher for ctr 
fallback"
  with Ubuntu 17.10 kernel.

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

-- 
Mailing list: https://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 1731822] Re: system can't detect external microphone with the codec alc274

[Stefan Bader]

** Package changed: linux (Ubuntu) => linux-oem (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/1731822

Title:
  system can't detect external microphone with the codec alc274

Status in HWE Next:
  Triaged
Status in linux-oem package in Ubuntu:
  Incomplete

Bug description:
  After installing the latest artful kernel (Ubuntu-4.13.0-16.19), and
  boot up the system with this kernel, we plug a headset to the headset
  jack, then open the gnome-sound-setting, but we can not see the
  headset microphone in it, there is only one internal microphone in it,
  as a result we can't record the sound with the headset microphone.

  This Dell machine has audio codec alc274, it needs to apply a fixup
  like ALC269_FIXUP_DELL1_MIC_NO_PRESENCE.

  After applying this fixup in the kernel driver, the headset mic can be
  detected and works fine.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1731822/+subscriptions

-- 
Mailing list: https://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 1732978] Re: Ubuntu 17.10: Include patch "crypto: vmx - Use skcipher for ctr fallback"

[Joseph Salisbury]

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

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

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

Title:
  Ubuntu 17.10: Include patch "crypto: vmx - Use skcipher for ctr
  fallback"

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

Bug description:
  == Comment: #0 - Paulo Flabiano Smorigo  - 2017-11-17 
10:29:14 ==
  Ubuntu 17.10 uses linux kernel 4.13 witch has a problem with the fallback 
cipher for CTR mode. The commit bellow fixes this problem by using the new 
structure for the generic ciphers. Please add it to the kernel package.

  
https://git.kernel.org/pub/scm/linux/kernel/git/herbert/crypto-2.6.git/commit/?id=e666d4e9ceec94c0a88c94b7db31d56474da43b3

  == Comment: #1 - VIPIN K. PARASHAR  - 2017-11-17 
13:38:05 ==
  (In reply to comment #0)
  > Ubuntu 17.10 uses linux kernel 4.13 witch has a problem with the fallback
  > cipher for CTR mode. The commit bellow fixes this problem by using the new
  > structure for the generic ciphers. Please add it to the kernel package.
  > 
  > https://git.kernel.org/pub/scm/linux/kernel/git/herbert/crypto-2.6.git/
  > commit/?id=e666d4e9ceec94c0a88c94b7db31d56474da43b3

  Which is commit e666d4e9ceec94

  commit e666d4e9ceec94c0a88c94b7db31d56474da43b3
  Author: Paulo Flabiano Smorigo 
  Date:   Mon Oct 16 20:54:19 2017 -0200

  crypto: vmx - Use skcipher for ctr fallback
  
  Signed-off-by: Paulo Flabiano Smorigo 
  Signed-off-by: Herbert Xu 

  Its available with 4.14 kernel.

  
  Hello Canonical,

  Please include commit e666d4e9ceec94 - "crypto: vmx - Use skcipher for ctr 
fallback"
  with Ubuntu 17.10 kernel.

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

-- 
Mailing list: https://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 1706033] Re: [P9, Power NV][ WSP][Ubuntu 16.04.03] : perf hw breakpoint command results in call traces and system goes for reboot.

[Manoj Iyer]

** Changed in: ubuntu-power-systems
   Status: Incomplete => Fix Released

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

Title:
  [P9, Power NV][ WSP][Ubuntu 16.04.03] : perf hw breakpoint command
  results in call traces and system goes for reboot.

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

Bug description:
  == Comment: #0 - Shriya R. Kulkarni <> - 2017-06-14 04:38:16 ==
  Problem Description :
  =
   
  While running perftool - testsuite, the perf hw breakpoint fails and it 
result in call traces , hence system goes for reboot .

  Machine details :
  ==
  System : P9 , WSP , Bare metal.
  OS : Ubuntu 16.04.03
  uname -a : Linux ltc-wspoon3 4.10.0-23-generic #25~16.04.1-Ubuntu SMP Fri Jun 
9 10:43:34 UTC 2017 ppc64le ppc64le ppc64le GNU/Linux

  Steps to reproduce:
  
  1. Install perf.
  2. git clone perftool-testsuite.
  https://github.com/rfmvh/perftool-testsuite
  3. Do make.
  4. Test fails at step : -- [ FAIL ] -- perf_stat :: test_hw_breakpoints :: 
kspace address execution mem:0xc035c020:x (command exitcode + output 
regexp parsing
  and call trace is seen as system goes for reboot.

  Call traces :
  ===

  ubuntu@ltc-wspoon3:~$ [1602513.518414] Unable to handle kernel paging request 
for data at address 0xc135d3b8
  [1602513.518553] Faulting instruction address: 0xc02869bc
  [1602513.518694] Oops: Kernel access of bad area, sig: 11 [#1]
  [1602513.518782] SMP NR_CPUS=2048 
  [1602513.518784] NUMA 
  [1602513.518842] PowerNV
  [1602513.518922] Modules linked in: vmx_crypto ofpart ipmi_powernv 
cmdlinepart ipmi_devintf powernv_flash ipmi_msghandler ibmpowernv opal_prd mtd 
at24 nvmem_core uio_pdrv_genirq uio autofs4 ast i2c_algo_bit drm_kms_helper 
syscopyarea sysfillrect sysimgblt fb_sys_fops crc32c_vpmsum ttm drm tg3 ahci 
libahci
  [1602513.519399] CPU: 27 PID: 4069 Comm: sysctl Not tainted 4.10.0-22-generic 
#24
  [1602513.519524] task: c000203968c42c00 task.stack: c00020396571
  [1602513.519624] NIP: c02869bc LR: c03f7348 CTR: 
c0286990
  [1602513.519747] REGS: c000203965713a40 TRAP: 0300   Not tainted  
(4.10.0-22-generic)
  [1602513.519876] MSR: 90009033 
  [1602513.519889]   CR: 22002448  XER: 
  [1602513.520058] CFAR: c03f7344 DAR: c135d3b8 DSISR: 0040 
SOFTE: 1 
  [1602513.520058] GPR00: c03f7348 c000203965713cc0 c145d100 
c134af00 
  [1602513.520058] GPR04:  4ee50300 c000203965713d20 
c000203965713e00 
  [1602513.520058] GPR08:  c135d100  
c0b71020 
  [1602513.520058] GPR12: c0286990 c7b4f300  
 
  [1602513.520058] GPR16:    
 
  [1602513.520058] GPR20:    
0001 
  [1602513.520058] GPR24: 3fffc542f5a0 0400 c000203965713e00 
4ee50300 
  [1602513.520058] GPR28: c134af00  c03fee038800 
 
  [1602513.521280] NIP [c02869bc] dirty_ratio_handler+0x2c/0x90
  [1602513.521374] LR [c03f7348] proc_sys_call_handler+0x138/0x1c0
  [1602513.521481] Call Trace:
  [1602513.521526] [c000203965713cc0] [c000203965713d00] 0xc000203965713d00 
(unreliable)
  [1602513.521655] [c000203965713d00] [c03f7348] 
proc_sys_call_handler+0x138/0x1c0
  [1602513.521797] [c000203965713d70] [c03436ec] __vfs_read+0x3c/0x70
  [1602513.521907] [c000203965713d90] [c034516c] vfs_read+0xbc/0x1b0
  [1602513.522016] [c000203965713de0] [c0346dd8] SyS_read+0x68/0x110
  [1602513.522112] [c000203965713e30] [c000b184] system_call+0x38/0xe0
  [1602513.522243] Instruction dump:
  [1602513.522303] 6042 3c4c011d 38426770 7c0802a6 6000 7c0802a6 
fbc1fff0 fbe1fff8 
  [1602513.522445] f8010010 f821ffc1 3d22fff0 7c9f2378  4be66da9 
6000 3d22fff0 
  [1602513.522564] ---[ end trace 17c76e13e641d3c6 ]---
  [1602513.522657] 

  It goes for reboot :

  After booting to Ubuntu , I see series of call traces.

  Ubuntu 16.04.2 LTS ltc-wspoon3 hvc0

  ltc-wspoon3 login: [ 3476.626263] Unable to handle kernel paging request for 
data at address 0xc13ad438
  [ 3476.626422] Faulting instruction address: 0xc029a140
  [ 3476.626537] Oops: Kernel access of bad area, sig: 11 [#1]
  [ 3476.626615] SMP NR_CPUS=2048 
  [ 3476.626616] NUMA 
  [ 3476.626673] PowerNV
  [ 3476.626746] Modules linked in: ipmi_powernv at24 ipmi_devintf nvmem_core 
ipmi_msghandler ofpart cmdlinepart powernv_flash mtd opal_prd vmx_crypto 
ibmpowernv uio_pdrv_genirq uio autofs4 ast 

[Kernel-packages] [Bug 1704730] Re: xfstest fails with corrupt file /mnt/scratch/1 - non-zero size but no extents ( ext4 )

[Andrew Cloke]

** Tags removed: triage-g
** Tags added: triage-a

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

Title:
  xfstest fails with corrupt file /mnt/scratch/1 - non-zero size but no
  extents ( ext4 )

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

Bug description:
  xfstests fails non-zero size but no extents on ext4 filesystem

  Environment
  --
  Kernel Build:  4.12.1-041201-generic

  Model  : 8247-22L
  Platform:  PowerNV ( P8 )

  Uname output
  ---
  # uname -a
  Linux ltc-test-ci2 4.12.1-041201-generic #201707121132 SMP Wed Jul 12 
17:03:25 UTC 2017 ppc64le ppc64le ppc64le GNU/Linux

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

  The test 044 fails with following
  generic/044 - output mismatch (see 
/root/harish/xfstests-dev/results//generic/044.out.bad)
  --- tests/generic/044.out 2017-07-13 06:04:36.208323135 -0400
  +++ /root/harish/xfstests-dev/results//generic/044.out.bad
2017-07-14 06:24:08.153731112 -0400
  @@ -1 +1,1000 @@
   QA output created by 044
  +corrupt file /mnt/scratch/1 - non-zero size but no extents
  +corrupt file /mnt/scratch/2 - non-zero size but no extents
  +corrupt file /mnt/scratch/3 - non-zero size but no extents
  +corrupt file /mnt/scratch/4 - non-zero size but no extents
  +corrupt file /mnt/scratch/5 - non-zero size but no extents
  +corrupt file /mnt/scratch/6 - non-zero size but no extents
  ...
  (Run 'diff -u tests/generic/044.out 
/root/harish/xfstests-dev/results//generic/044.out.bad'  to see the entire diff)
  Ran: generic/044
  Failures: generic/044
  Failed 1 of 1 tests

  
  Dmesg:
  --
  [17244.878673] EXT4-fs (loop0): mounted filesystem with ordered data mode. 
Opts: (null)
  [17245.517227] EXT4-fs (loop2): mounted filesystem with ordered data mode. 
Opts: acl,user_xattr
  [17245.697100] EXT4-fs (loop0): mounted filesystem with ordered data mode. 
Opts: acl,user_xattr
  [17245.710634] run fstests generic/044 at 2017-07-14 06:23:49
  [17246.534410] EXT4-fs (loop2): mounted filesystem with ordered data mode. 
Opts: acl,user_xattr
  [17246.535534] EXT4-fs (loop2): shut down requested (1)
  [17246.535625] Aborting journal on device loop2-8.
  [17247.278467] EXT4-fs (loop2): mounted filesystem with ordered data mode. 
Opts: acl,user_xattr
  [17259.888304] EXT4-fs (loop2): shut down requested (2)
  [17259.995751] Aborting journal on device loop2-8.
  [17260.113582] EXT4-fs (loop2): recovery complete
  [17260.113902] EXT4-fs (loop2): mounted filesystem with ordered data mode. 
Opts: acl,user_xattr
  [17260.190076] EXT4-fs (loop2): mounted filesystem with ordered data mode. 
Opts: acl,user_xattr
  [17264.821978] EXT4-fs (loop2): mounted filesystem with ordered data mode. 
Opts: acl,user_xattr


  == Comment: #2 - SEETEENA THOUFEEK  - 2017-07-17 
02:10:52 ==
  Issue does not happen when running the same test with xfs file system. (ie, 
creating loop device with xfs file system).

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

-- 
Mailing list: https://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 1707875] Re: include support for Python bindings in "perf"

[Andrew Cloke]

** Changed in: ubuntu-power-systems
   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/1707875

Title:
  include support for Python bindings in "perf"

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

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 1708451] Re: Process hangs on HW watchpoint on Power9

[Manoj Iyer]

** Changed in: ubuntu-power-systems
   Status: In Progress => Fix Released

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

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

Title:
  Process hangs on HW watchpoint on Power9

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

Bug description:
  == Comment: #0 - Pedro Miraglia Franco de Carval  - 
2017-06-30 12:52:06 ==
  After setting a hardware watchpoint on a variable through gdb, the traced 
process gets stuck on the instruction that affects the watched address but 
doesn't stop.

  Steps to reproduce:

  Make a program to be traced:

  pedromfc@perch:~$ cat wp_test.c 
  int my_global = 0;

  void main( void ) {
my_global = 1;
  }

  pedromfc@perch:~$ gcc -g -O0 -o wp_test wp_test.c

  Debug the binary:

  pedromfc@perch:~$ gdb -q wp_test
  Reading symbols from wp_test...done.
  (gdb) watch my_global
  Hardware watchpoint 1: my_global
  (gdb) run
  Starting program: /home/pedromfc/wp_test 

  [Program stuck here, manually interrupt]

  ^C
  Program received signal SIGINT, Interrupt.
  0x27a0 in main () at wp_test.c:4
  4   my_global = 1;
  (gdb) disas
  Dump of assembler code for function main:
 0x2780 <+0>:   addis   r2,r12,2
 0x2784 <+4>:   addir2,r2,30592
 0x2788 <+8>:   std r31,-8(r1)
 0x278c <+12>:  stdur1,-48(r1)
 0x2790 <+16>:  mr  r31,r1
 0x2794 <+20>:  nop
 0x2798 <+24>:  addir9,r2,-32492
 0x279c <+28>:  li  r10,1
  => 0x27a0 <+32>:  stw r10,0(r9)
 0x27a4 <+36>:  nop
 0x27a8 <+40>:  addir1,r31,48
 0x27ac <+44>:  ld  r31,-8(r1)
 0x27b0 <+48>:  blr
 0x27b4 <+52>:  .long 0x0
 0x27b8 <+56>:  .long 0x0
 0x27bc <+60>:  .long 0x1000180
  End of assembler dump.

  (gdb) info reg r9
  r9 0x20020014 537002004
  (gdb) p /x _global
  $1 = 0x20020014
  (gdb) continue
  Continuing.

  [Like before, nothing happens]

  ^C
  Program received signal SIGINT, Interrupt.
  0x27a0 in main () at wp_test.c:4
  4   my_global = 1;
  (gdb) disass
  Dump of assembler code for function main:
 0x2780 <+0>:   addis   r2,r12,2
 0x2784 <+4>:   addir2,r2,30592
 0x2788 <+8>:   std r31,-8(r1)
 0x278c <+12>:  stdur1,-48(r1)
 0x2790 <+16>:  mr  r31,r1
 0x2794 <+20>:  nop
 0x2798 <+24>:  addir9,r2,-32492
 0x279c <+28>:  li  r10,1
  => 0x27a0 <+32>:  stw r10,0(r9)
 0x27a4 <+36>:  nop
 0x27a8 <+40>:  addir1,r31,48
 0x27ac <+44>:  ld  r31,-8(r1)
 0x27b0 <+48>:  blr
 0x27b4 <+52>:  .long 0x0
 0x27b8 <+56>:  .long 0x0
 0x27bc <+60>:  .long 0x1000180
  End of assembler dump.
  (gdb) continue
  Continuing.

  Check on another terminal that the program is running (but stuck in
  the same instruction):

  pedromfc@perch:~$ ps -C gdb,wp_test -o pid,comm,state
PIDCOMMANDS
  19178 gdb  S
  19193 wp_testR

  
  This happened on this machine model:

  cpu   : POWER9 (raw), altivec supported
  revision  : 1.0 (pvr 004e 0100)
  machine   : PowerNV 8375-42A
  firmware  : OPAL
  SN: 13C665W

  With this kernel:

  pedromfc@perch:~$ uname -a
  Linux perch 4.10.0-19-generic #21-Ubuntu SMP Thu Apr 6 17:03:05 UTC 2017 
ppc64le ppc64le ppc64le GNU/Linux

  It also happened with this kernel, on another machine:
  [pedromfc@zzfp342p1 ~]$ uname -a
  Linux zzfp342p1 4.11.0-10.el7a.ppc64le #1 SMP Wed Jun 21 20:50:21 EDT 2017 
ppc64le ppc64le ppc64le GNU/Linux

  On another machine (P8) the watchpoint triggers as expected and the
  process stops immediately after the store instruction:

  pedromfc@genoa:~$ uname -a
  Linux genoa 3.13.0-35-generic #62-Ubuntu SMP Fri Aug 15 01:57:29 UTC 2014 
ppc64le ppc64le ppc64le GNU/Linux
  pedromfc@genoa:~$ gdb wp_test
  ...

  Reading symbols from wp_test...done.
  (gdb) watch my_global
  Hardware watchpoint 1: my_global
  (gdb) run
  Starting program: /home/pedromfc/wp_test 
  Hardware watchpoint 1: my_global

  Old value = 0
  New value = 1
  main () at wp_test.c:5
  5 }
  (gdb)

  
  
https://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git/commit/?id=d89ba5353f301971dd7d2f9fdf25c4432728f38e

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

-- 
Mailing list: 

[Kernel-packages] [Bug 1709738] Re: xfstest sanity checks 17 fails on data-hole-data inside page

[Manoj Iyer]

** Changed in: ubuntu-power-systems
   Status: In Progress => Fix Released

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

Title:
  xfstest sanity checks 17 fails on  data-hole-data inside page

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

Bug description:
  Problem Description
  
  xfstests fails with Metadata corruption at leaf on ext4 filesystem

  Environment
  --
  Kernel Build:  4.12.1-041201-generic
  System Name : ltc-test-ci2
  Model  : 8247-22L
  Platform:  PowerNV ( P8 )
  Issue observed in P9 also.

  Uname output
  ---
  # uname -a
  Linux ltc-test-ci2 4.12.1-041201-generic #201707121132 SMP Wed Jul 12 
17:03:25 UTC 2017 ppc64le ppc64le ppc64le GNU/Linux

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

  generic/445  [failed, exit status 1] - output mismatch (see 
/root/harish/xfstests-dev/results//generic/445.out.bad)
  --- tests/generic/445.out   2017-07-13 06:04:36.244322946 -0400
  +++ /root/harish/xfstests-dev/results//generic/445.out.bad  2017-07-14 
02:49:06.540352923 -0400
  @@ -1,2 +1,3 @@
   QA output created by 445
  -Silence is golden
  +seek sanity check failed!
  +(see /root/harish/xfstests-dev/results//generic/445.full for details)
  ...
  (Run 'diff -u tests/generic/445.out 
/root/harish/xfstests-dev/results//generic/445.out.bad'  to see the entire diff)

  
  Nothing observed in dmesg.

  Full log is attached.

  Note: Issue is also observed on distro kernel - 4.11.0-10-generic.

  It needs to have two disks you run the test on. Make sure you create
  those directories before running the test.

  # 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/1709738/+subscriptions

-- 
Mailing list: https://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 1711104] Re: [P9][Ubuntu 16.04.03] Additional PMU fixes for P9

[Andrew Cloke]

** Changed in: ubuntu-power-systems
   Status: Incomplete => In Progress

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

Title:
  [P9][Ubuntu 16.04.03] Additional PMU fixes for P9

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

Bug description:
  == Comment: #0 - Shriya R. Kulkarni  - 2017-08-16 
04:07:45 ==
  Please integrate the following PMU fixes for P9.

  93fc5ca9a0048c ('powerpc/perf: Cleanup of PM_BR_CMPL vs. PM_BRU_CMPL in 
Power9 event list')
  91e0bd1e62519b ('powerpc/perf: Add PM_LD_MISS_L1 and PM_BR_2PATH to power9 
event list')
  70a7e720998d5b ('powerpc/perf: Factor out PPMU_ONLY_COUNT_RUN check code from 
power8')
  7aa345d84245a7 ('powerpc/perf: Update default sdar_mode value for power9')
  101dd590a7fa37 ('powerpc/perf: Avoid spurious PMU interrupts after idle')
  bdd21ddb919d28 ('powerpc/perf: Avoid spurious PMU interrupts after idle on 
Power9')
  3f0bd8dad0db73 ('powerpc/perf: Add POWER9 alternate PM_RUN_CYC and 
PM_RUN_INST_CMPL events')
  20dd4c624d2515 ('powerpc/perf: Fix SDAR_MODE value for continous sampling on 
Power9')
  24bedcb7c81137 ('powerpc/perf: Fix branch event code for power9')
  8c218578fcbbbd ('powerpc/perf: Fix Power9 test_adder fields')

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

-- 
Mailing list: https://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 1719545] Re: [LTCTest][Opal][FW910] cpupower monitor shows multiple stop Idle_Stats

[Andrew Cloke]

Marking as "incomplete" until patch lands upstream and it becomes
actionable.

** Changed in: ubuntu-power-systems
   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/1719545

Title:
  [LTCTest][Opal][FW910] cpupower monitor shows multiple stop Idle_Stats

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

Bug description:
  == Comment: #0 - PAVAMAN SUBRAMANIYAM  - 2017-06-29 
02:30:22 ==
  ---Problem Description---
  cpupower monitor shows multiple stop Idle_Stats
   

   
  ---uname output---
  Linux zz376p1 4.10.0-26-generic #30~16.04.1-Ubuntu SMP Tue Jun 27 09:38:48 
UTC 2017 ppc64le ppc64le ppc64le GNU/Linux
   
  Machine Type = P9 
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
  Install a P9 8375-42A Hardware with Ubuntu 16.04.3 OS.
  Then execute the cpupower monitor command to fetch all the Idle_Stats values.

  root@zz376p1:~# cpupower monitor
|Idle_Stats
  PKG |CORE|CPU | snoo | stop | stop
 0|   8|   0|  0.00|  0.00|  2.79
 0|   8|   1|  0.00|  0.00| 70.68
 0|   8|   2|  0.00|  0.00| 99.87
 0|   8|   3|  0.00|  0.00| 67.28
 0|  12|   4|  0.00|  0.00|  5.17
 0|  12|   5|  0.00|  0.00| 12.50
 0|  12|   6|  0.00|  0.00| 99.74
 0|  12|   7|  0.00|  0.00|  0.00
 8|2048|   8|  0.00|  0.00| 22.14
 8|2048|   9|  0.00|  0.00| 102.3
 8|2048|  10|  0.00|  0.00|  0.00
 8|2048|  11|  0.00|  0.00| 99.97
 8|2052|  12|  0.00|  0.00| 99.70
 8|2052|  13|  0.00|  0.00| 23.86
 8|2052|  14|  0.00|  0.00| 113.1
 8|2052|  15|  0.00|  0.00|  0.00

  As can be seen it shows 2 columns for stop.

  root@zz376p1:~# uname -a
  Linux zz376p1 4.10.0-26-generic #30~16.04.1-Ubuntu SMP Tue Jun 27 09:38:48 
UTC 2017 ppc64le ppc64le ppc64le GNU/Linux

  root@zz376p1:~# cat /etc/os-release
  NAME="Ubuntu"
  VERSION="16.04.2 LTS (Xenial Xerus)"
  ID=ubuntu
  ID_LIKE=debian
  PRETTY_NAME="Ubuntu 16.04.2 LTS"
  VERSION_ID="16.04"
  HOME_URL="http://www.ubuntu.com/;
  SUPPORT_URL="http://help.ubuntu.com/;
  BUG_REPORT_URL="http://bugs.launchpad.net/ubuntu/;
  VERSION_CODENAME=xenial
  UBUNTU_CODENAME=xenial

  root@zz376p1:~# cat /proc/cpuinfo | tail
  processor   : 15
  cpu : POWER9 (raw), altivec supported
  clock   : 2600.00MHz
  revision: 1.0 (pvr 004e 0100)

  timebase: 51200
  platform: PowerNV
  model   : 8375-42A
  machine : PowerNV 8375-42A
  firmware: OPAL
   
  Userspace tool common name: /usr/bin/cpupower 
   
  The userspace tool has the following bit modes: 64-bit 

  Userspace rpm: linux-tools-common

  Userspace tool obtained from project website:  na 
   
  *Additional Instructions for pavsu...@in.ibm.com: 
  -Post a private note with access information to the machine that the bug is 
occuring on.
  -Attach ltrace and strace of userspace application.

  
  .
  There are 3 idle_stats (3 states) in this system. 

  root@zz376p1:/sys/devices/system/cpu/cpu0/cpuidle/state2# cpupower monitor -l
  Monitor "Idle_Stats" (3 states) - Might overflow after 4294967295 s
  snoo  [T] -> snooze
  stop  [T] -> stop0_lite
  stop  [T] -> stop1_lite

  root@zz376p1:/sys/devices/system/cpu/cpu0/cpuidle/state2# cpupower idle-info
  CPUidle driver: powernv_idle
  CPUidle governor: menu
  analyzing CPU 0:

  Number of idle states: 3
  Available idle states: snooze stop0_lite stop1_lite
  snooze:
  Flags/Description: snooze
  Latency: 0
  Usage: 224
  Duration: 423
  stop0_lite:
  Flags/Description: stop0_lite
  Latency: 0
  Usage: 1685
  Duration: 530522
  stop1_lite:
  Flags/Description: stop1_lite
  Latency: 4
  Usage: 12693
  Duration: 5405898106

  root@zz376p1:/sys/devices/system/cpu/cpu0/cpuidle/state2# cpupower monitor -l
  Monitor "Idle_Stats" (3 states) - Might overflow after 4294967295 s
  snoo  [T] -> snooze
  stop  [T] -> stop0_lite
  stop  [T] -> stop1_lite
  root@zz376p1:/sys/devices/system/cpu/cpu0/cpuidle/state2# cpupower idle-info
  CPUidle driver: powernv_idle
  CPUidle governor: menu
  analyzing CPU 0:

  Number of idle states: 3
  Available idle states: snooze stop0_lite stop1_lite
  snooze:
  Flags/Description: snooze
  Latency: 0
  Usage: 272
  Duration: 905
  stop0_lite:
  Flags/Description: stop0_lite
  Latency: 0
  Usage: 2141
  Duration: 536399
  stop1_lite:
  Flags/Description: stop1_lite
  Latency: 4
  Usage: 15396
  Duration: 6625668881

  
  cpu monitor will print the results of all the 3 available idle_stats .

  The first stop -> stop0_lite stats
  and
  The second stop -> stop1_lite stats.

  cpupower monitor header prints the header list by getting the name of
  the idle stats.

  name  (name description)
  snoo   [T] -> snooze
  stop   [T] -> stop0_lite
  stop   [T] -> stop1_lite

  We can change the 

[Kernel-packages] [Bug 1711283] Re: few kernel selftest failed on Ubuntu 17.10

[Andrew Cloke]

** Changed in: ubuntu-power-systems
   Importance: High => Low

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

Title:
  few kernel selftest failed on Ubuntu 17.10

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

Bug description:
  == Comment: #0 - Harish Sriram  - 2017-08-01 05:11:09 ==
  Problem Description
  
  Few kernel selftest failed on Ubuntu 17.10

  Environment
  --
  Kernel Build:  4.11.0-10-generic
  System Name : ltc-test-ci2
  Model  : 8247-22L
  Platform:  PowerNV ( P8 )

  Uname output
  ---
  # uname -a
  Linux ltc-test-ci2 4.11.0-10-generic #15-Ubuntu SMP Thu Jun 29 15:02:54 UTC 
2017 ppc64le ppc64le ppc64le GNU/Linux

  Steps to reproduce:
  
  1. Get kernel source using apt source
  2. Start powerpc specific tests

  The following FAILS are observed.
  selftests:  cycles_test [FAIL]
  selftests:  cycles_with_freeze_test [FAIL]
  selftests:  pmc56_overflow_test [FAIL]
  selftests:  ebb_vs_cpu_event_test [FAIL]
  selftests:  cpu_event_vs_ebb_test [FAIL]
  selftests:  task_event_vs_ebb_test [FAIL]
  selftests:  multi_ebb_procs_test [FAIL]
  selftests:  multi_counter_test [FAIL]
  selftests:  pmae_handling_test [FAIL]
  selftests:  close_clears_pmcc_test [FAIL]
  selftests:  instruction_count_test [FAIL]
  selftests:  ebb_on_willing_child_test [FAIL]
  selftests:  back_to_back_ebbs_test [FAIL]
  selftests:  lost_exception_test [FAIL]
  selftests:  cycles_with_mmcr2_test [FAIL]
  selftests:  tm-vmxcopy [FAIL]

  Full run log is attached.

  == Comment: #5 - Harish Sriram  - 2017-08-08 03:33:36 ==
  With the latest ubuntu mainline kernel 4.13-rc4 from 
http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.13-rc4/, I see following 
additional failures

  selftests:  ptrace-gpr [FAIL]
  selftests:  ptrace-tm-gpr [FAIL]
  selftests:  ptrace-tm-spd-gpr [FAIL]

  # uname -a
  Linux ltc-test-ci2 4.13.0-041300rc4-generic #201708062231 SMP Mon Aug 7 
03:29:19 UTC 2017 ppc64le ppc64le ppc64le GNU/Linux

  Thanks,
  Harish

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

-- 
Mailing list: https://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 1713576] Re: More migrations with constant load

[Manoj Iyer]

** Changed in: ubuntu-power-systems
   Status: Fix Committed => Fix Released

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

Title:
  More migrations with constant load

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

Bug description:
  == SRU Justification ==
  There is a significantly higher number of task migrations when the load is 
  fixed and not balanced across cores.

  Benchmark results are posted in the bug description and in the commits
  git log.

  This bug is resolved by mainline commit 
05b40e057734811ce452344fb3690d09965a7b6a, which is 
  in mailine as of 4.12-rc1.

  
  == Fix ==
  commit 05b40e057734811ce452344fb3690d09965a7b6a
  Author: Srikar Dronamraju 
  Date:   Wed Mar 22 23:27:50 2017 +0530

  sched/fair: Prefer sibiling only if local group is under-utilized

  == Regression Potential ==
  Medium, since this commit does touch the scheduler.  However, the commit only 
makes a change to 
  allow a local group to pull a task, if the source group has more number of 
  tasks than the local group.

  == Test Case ==
  A test kernel was built with this patch and tested by the original bug 
reporter.
  The bug reporter states the test kernel resolved the bug.


  
  == Comment: #0 - PUVICHAKRAVARTHY RAMACHANDRAN  - 2017-08-06 13:44:45 ==
  ---Problem Description---
  Significantly higher number of task migrations when the load is fixed but not 
balanced across cores.

  ---uname output---
  Linux isvbos3 4.10.0-29-generic #33~16.04.1-Ubuntu SMP Tue Jul 25 18:17:06 
UTC 2017 ppc64le ppc64le ppc64le GNU/Linux

  ---Additional Hardware Info---
  Power9 dd2.0

  Machine Type = Power9

  ---Steps to Reproduce---
   Benchmark : Multithreaded - cpu intensive. The system had 2 socket/ 32 
cores/ SMT4 mode.

  When 64 threads was run - the migrations were less over 10s interval.
  when 80 threads were run - the migrations were very high.

  Ideally, it should have been very minimal, as the over all load was
  constant

  == Comment: #3 - SRIKAR DRONAMRAJU - 2017-08-11 06:56:47 ==
  As suspected (commit :  05b40e0577 : "sched/fair: Prefer sibiling only if 
local group is under-utilized")
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=05b40e0577
  should fix the problem

  Ran ' perf stat -a -r 5 -e sched:sched_migrate_task 
/home/srikar/work/ebizzy-0.3/ebizzy -t 35 -S 100'
  to detect the problem and verify the fix

  Here is perf stat without fix.

  Performance counter stats for 'system wide' (5 runs):

   7,758  sched:sched_migrate_task
  ( +-  1.28% )

   100.015658079 seconds time elapsed
  ( +-  0.00% )

  perf stat with fix.

  Performance counter stats for 'system wide' (5 runs):

     415  sched:sched_migrate_task
  ( +- 11.74% )

   100.016021787 seconds time elapsed
  ( +-  0.00% )

  git describe on upstream kernel says v4.11-rc2
  # git describe 05b40e0577
  v4.11-rc2-227-g05b40e0

  == Comment: #4 - SRIKAR DRONAMRAJU - 2017-08-11 07:05:37 ==
  Attaching the patch that needs to be applied to fix this bug.
  Verified that patch fixes the problem.

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

-- 
Mailing list: https://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 1728489] Re: tar -x sometimes fails on overlayfs

[Stefan Bader]

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

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

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

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

Title:
  tar -x sometimes fails on overlayfs

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

Bug description:
  [SRU Justification]

  [Impact]
  A user is seeing failures from extracting tar archives on overlay filesystems 
on the 4.4 kernel in constrained environments. The error presents as: 

  `tar: ./deps/0/bin: Directory renamed before its status could be
  extracted`

  Following this thread (http://www.spinics.net/lists/linux-
  unionfs/msg00856.html), it appears that this occurs when entries in
  the kernel's inode cache are reclaimed, and subsequent lookups return
  new inode numbers.

  Further testing showed that when setting
  `/proc/sys/vm/vfs_cache_pressure` to 0 (don't allow the kernel to
  reclaim inode cache entries due to memory pressure) the error does not
  recur, supporting the hypothesis that cache entries are being evicted.
  However, this setting may lead to a kernel OOM so is not a reasonable
  workaround even temporarily.

  The error cannot be reproduced on a 4.13 kernel, due to the series at
  https://www.spinics.net/lists/linux-fsdevel/msg110235.html. The
  particular relevant commit is
  b7a807dc2010334e62e0afd89d6f7a8913eb14ff, which needs a couple of
  dependencies.

  [Fix]
  For Zesty, backport the entire series.
  For Xenial, where a full backport is not feasible, backport the key commit 
and the short list of dependencies.

  [Testcase]

  # Testing this bug

  The testcase for this particular bug is simple - create an overlay
  filesystem with all layers on the same underlying file system, and
  then see if the inode of a directory is constant across dropping the
  caches:

  mkdir -p /upper/upper /upper/work /lower
  mount -t overlay none /mnt -o 
lowerdir=/lower,upperdir=/upper/upper,workdir=/upper/work
  cd /mnt
  mkdir a
  stat a # observe inode number
  echo 2 > /proc/sys/vm/drop_caches
  stat a # compare inode number

  If the inode number is the same, the fix is successful.

  # Regression testing

  I have run the unionmount test suite from
  http://git.infradead.org/users/dhowells/unionmount-testsuite.git in
  overlay mode (./run --ov), and verified that it still passes.

  (The series cover letter mentions a fork of the test suite at
  https://github.com/amir73il/unionmount-testsuite/commits/overlayfs-
  devel. I have *not* attempted to get this running: it assumes a range
  of changes that are not present in our kernels.)

  [Regression Potential]
  As this changes overlayfs, there is potential for regression in the form of 
unexpected breakages to overlaysfs behaviour.

  I think this is adequately addressed by the regression testing.

  One option to reduce the regression potential on Zesty is to reduce
  the set of patches applied - rather than including the whole series we
  could include just the patches to solve this bug, which are much
  easier to inspect for correctness.

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

-- 
Mailing list: https://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 1709964] Re: Ubuntu 16.04.03: perf tool does not count pm_run_inst_cmpl with rcode on POWER9 DD2.0

[Manoj Iyer]

** Changed in: ubuntu-power-systems
   Status: Fix Committed => Fix Released

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

Title:
  Ubuntu 16.04.03: perf tool does not count pm_run_inst_cmpl with rcode
  on POWER9 DD2.0

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

Bug description:
  == SRU Justification ==
  Ubuntu 16.04.03: perf tool does not count pm_run_inst_cmpl with rcode on 
POWER9 DD2.0.

  This is a regression introduced by mainline commit 8d911904f3ce.  This 
regression
  is resolved by commit 8c218578fcbbbdb10416c8614658bf32e3bf1655.

  Commit 8c218578fc is available in mailine as of 4.12-rc5.



  ---Problem Description---
  Unable to count pm_run_inst_cmpl using perf tool on boston dd2.0

  root@isvbos3:~# perf stat -e r500fa,r600f4 -a  sleep 1

   Performance counter stats for 'system wide':

       r500fa
   8,162,912  r600f4

     1.001562716 seconds time elapsed

  ---uname output---
  Linux isvbos3 4.10.0-29-generic #33~16.04.1-Ubuntu SMP Tue Jul 25 18:17:06 
UTC 2017 ppc64le ppc64le ppc64le GNU/Linux

  Machine Type = p9 dd2.0

  ---Steps to Reproduce---
   root@isvbos3:~# perf stat -e r500fa,r600f4 -a  sleep 1

   Performance counter stats for 'system wide':

       r500fa
   8,162,912  r600f4

     1.001562716 seconds time elapsed

  > Also we need this upstream fix 8c218578fcbbbdb10416c8614658bf32e3bf1655 in
  > the distro.

  $ git log 8c218578fcbbbdb10416c8614658 -1
  commit 8c218578fcbbbdb10416c8614658bf32e3bf1655
  Author: Madhavan Srinivasan 
  Date:   Fri May 26 13:38:27 2017 +0530

  powerpc/perf: Fix Power9 test_adder fields

  Commit 8d911904f3ce4 ('powerpc/perf: Add restrictions to PMC5 in power9 
DD1')
  was added to restrict the use of PMC5 in Power9 DD1. Intention was to 
disable
  the use of PMC5 using raw event code. But instead of updating the
  power9_isa207_pmu structure (used on DD1), the commit incorrectly updated 
the
  power9_pmu structure. Fix it.

  Fixes: 8d911904f3ce ("powerpc/perf: Add restrictions to PMC5 in power9 
DD1")
  Reported-by: Shriya 
  Signed-off-by: Madhavan Srinivasan 
  Tested-by: Shriya 
  Signed-off-by: Michael Ellerman 

  $ git describe --contains 8c218578fcbbbdb
  v4.12-rc7~9^2~13
  $

  Commit 8c218578fc is available with kernel 4.12-rc7 afterwards.

  I don't see this fix in the Ubuntu 16.04.3 Zesty tree (the P9 hwe
  kernel, 4.10 based).

  Need to mirror to Canonical to request they pull in:
  8c218578fcbbbdb10416c8614658bf32e3bf1655

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

-- 
Mailing list: https://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 1716491] Re: New PMU fixes for marked events.

[Manoj Iyer]

** Changed in: ubuntu-power-systems
   Status: In Progress => Fix Released

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

Title:
  New PMU fixes for marked events.

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

Bug description:
  == SRU Justification ==
  The current Zesty kernel does not enable marked events on Power9. The 
  following fixes are required:

  101dd590a7fa ("powerpc/perf: Avoid spurious PMU interrupts after idle")
  09539f9b1236 ("powerpc/perf: POWER9 PMU stops after idle workaround")

  Commit 101dd590a7fa was added to mainline in v4.13-rc3 and commit 
09539f9b1236 
  was added in v4.13-rc4.

  
  == Fixes ==
  commit 101dd590a7fa37954540cf3149a1c502c0acc524
  Author: Nicholas Piggin 
  Date:   Mon Jul 10 16:19:38 2017 +1000

  powerpc/perf: Avoid spurious PMU interrupts after idle

  commit 09539f9b123652e969894d6299ae0df2fe12cb5d
  Author: Nicholas Piggin 
  Date:   Thu Jul 20 11:53:22 2017 +1000

  powerpc/perf: POWER9 PMU stops after idle workaround

  
  == Regression Potential ==
  Low, since these commits are specific to powerpc.


  
  Dear Canonical,

  Please include the following fixes into Ubuntu Zesty (4.10) kernel.
  The current kernel does not enable marked events on Power9. And the
  following fixes are required:

  09539f9b1236 ("powerpc/perf: POWER9 PMU stops after idle workaround")
  101dd590a7fa ("powerpc/perf: Avoid spurious PMU interrupts after idle")

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

-- 
Mailing list: https://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 1724120] Re: Ubuntu 16.04.3 - call traces occurs when memory-hotplug test is run with 16Gb hugepages configured

[Andrew Cloke]

** Tags removed: triage-g
** Tags added: triage-a

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

Title:
  Ubuntu 16.04.3 - call traces occurs when memory-hotplug test is run
  with 16Gb hugepages configured

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

Bug description:
  Issue:

  Call traces occurs when memory-hotplug script is run with 16Gb
  hugepages configured.

  Environment:
  ppc64le PowerVM Lpar

  root@ltctuleta-lp1:~# uname -r
  4.4.0-34-generic

  root@ltctuleta-lp1:~# cat /proc/meminfo | grep -i huge
  AnonHugePages: 0 kB
  HugePages_Total:   2
  HugePages_Free:2
  HugePages_Rsvd:0
  HugePages_Surp:0
  Hugepagesize:   16777216 kB

  root@ltctuleta-lp1:~# free -h
totalusedfree  shared  buff/cache   
available
  Mem:85G 32G 52G 16M193M 
52G
  Swap:   43G  0B 43G

  Steps to reproduce:
  1 - Download kernel source and enter to the directory- 
tools/testing/selftests/memory-hotplug/
  2 - Run  mem-on-off-test.sh script in it.

  System gives call traces like:

  offline_memory_expect_success 639: unexpected fail
  online-offline 668
  [   57.552964] Unable to handle kernel paging request for data at address 
0x0028
  [   57.552977] Faulting instruction address: 0xc029bc04
  [   57.552987] Oops: Kernel access of bad area, sig: 11 [#1]
  [   57.552992] SMP NR_CPUS=2048 NUMA pSeries
  [   57.553002] Modules linked in: btrfs xor raid6_pq pseries_rng sunrpc 
autofs4 ses enclosure nouveau bnx2x i2c_algo_bit ttm drm_kms_helper syscopyarea 
sysfillrect sysimgblt fb_sys_fops drm vxlan ip6_udp_tunnel ipr udp_tunnel 
rtc_generic mdio libcrc32c
  [   57.553050] CPU: 44 PID: 6518 Comm: mem-on-off-test Not tainted 
4.4.0-34-generic #53-Ubuntu
  [   57.553059] task: c0072773c8e0 ti: c0072778 task.ti: 
c0072778
  [   57.553067] NIP: c029bc04 LR: c029bbdc CTR: 
c01107f0
  [   57.553076] REGS: c00727783770 TRAP: 0300   Not tainted  
(4.4.0-34-generic)
  [   57.553083] MSR: 80019033   CR: 24242882  
XER: 0002
  [   57.553104] CFAR: c0008468 DAR: 0028 DSISR: 4000 
SOFTE: 1 
  GPR00: c029bbdc c007277839f0 c15b5d00  
  GPR04: 0029d000 0800  fa01 
  GPR08: fa700020 0008 c185e270 c00e7e50 
  GPR12: 2200 ce6ea200 0029d000 2200 
  GPR16: 1000 c15e2200 0a70  
  GPR20: 0001 0100 0200 c15f16d0 
  GPR24: c1876510  0001 c1872a00 
  GPR28: 0029d000 f000 fa70 0029c000 
  [   57.553211] NIP [c029bc04] dissolve_free_huge_pages+0x154/0x220
  [   57.553219] LR [c029bbdc] dissolve_free_huge_pages+0x12c/0x220
  [   57.553226] Call Trace:
  [   57.553231] [c007277839f0] [c029bbdc] 
dissolve_free_huge_pages+0x12c/0x220 (unreliable)
  [   57.553244] [c00727783a80] [c02dcbc8] 
__offline_pages.constprop.6+0x3f8/0x900
  [   57.553254] [c00727783bd0] [c06fbb38] 
memory_subsys_offline+0xa8/0x110
  [   57.553265] [c00727783c00] [c06d6424] 
device_offline+0x104/0x140
  [   57.553274] [c00727783c40] [c06fba80] 
store_mem_state+0x180/0x190
  [   57.553283] [c00727783c80] [c06d1e58] dev_attr_store+0x68/0xa0
  [   57.553293] [c00727783cc0] [c0398110] sysfs_kf_write+0x80/0xb0
  [   57.553302] [c00727783d00] [c0397028] 
kernfs_fop_write+0x188/0x200
  [   57.553312] [c00727783d50] [c02e190c] __vfs_write+0x6c/0xe0
  [   57.553321] [c00727783d90] [c02e2640] vfs_write+0xc0/0x230
  [   57.553329] [c00727783de0] [c02e367c] SyS_write+0x6c/0x110
  [   57.553339] [c00727783e30] [c0009204] system_call+0x38/0xb4
  [   57.553346] Instruction dump:
  [   57.553351] 7e831836 4bfff991 e91e0028 e8fe0020 7d32e82a f9070008 f8e8 
fabe0020 
  [   57.553366] fade0028 79294620 79291764 7d234a14  3908 
f9030028 81091458 
  [   57.553383] ---[ end trace 617f7bdd75bcfc10 ]---
  [   57.557133] 
  Segmentation fault

  The following commit IDs were built into a 4.10.0-37-generic #41 test
  kernel and verified to fix the problem:

  a525108cf1cc14651602d678da38fa627a76a724
  e1073d1e7920946ac4776a619cc40668b9e1401b
  40692eb5eea209c2dd55857f44b4e1d7206e91d6
  e24a1307ba1f99fc62a0bd61d5e87fcfb6d5503d
  79cc38ded1e1ac86e69c90f604efadd50b0b3762
  4ae279c2c96ab38a78b954d218790a8f6db714e5

To manage notifications about this bug go to:

[Kernel-packages] [Bug 1725350] Re: KVM on 17.10 crashes the machine

[Andrew Cloke]

** Tags added: triage-g

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

Title:
  KVM on 17.10 crashes the machine

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

Bug description:
  When you start qemu on a 17.10 machine, the whole machine goes down
  and crashes:

  [   90.689627] Unable to handle kernel paging request for data at address 
0xf2d3bda0
  [   90.689705] Faulting instruction address: 0xc0361224
  [   90.689840] Oops: Kernel access of bad area, sig: 11 [#1]
  [   90.689911] SMP NR_CPUS=2048 
  [   90.689912] NUMA 
  [   90.690053] PowerNV
  [   90.690092] Modules linked in: xt_CHECKSUM iptable_mangle ipt_MASQUERADE 
nf_nat_masquerade_ipv4 iptable_nat xt_conntrack ipt_REJECT nf_reject_ipv4 
xt_tcpudp bridge stp llc kvm_hv kvm_pr kvm ebtable_filter ebtables 
ip6table_filter ip6_tables iptable_filter openvswitch nf_conntrack_ipv6 
nf_nat_ipv6 nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_defrag_ipv6 nf_nat 
nf_conntrack_netlink nf_conntrack nfnetlink idt_89hpesx snd_hda_codec_hdmi xfs 
joydev input_leds mac_hid snd_hda_intel snd_hda_codec snd_hda_core snd_hwdep 
snd_pcm snd_timer snd soundcore ofpart opal_prd cmdlinepart powernv_flash mtd 
at24 ipmi_powernv ipmi_devintf ipmi_msghandler powernv_rng uio_pdrv_genirq 
vmx_crypto ibmpowernv uio ib_iser rdma_cm iw_cm ib_cm ib_core iscsi_tcp 
libiscsi_tcp libiscsi scsi_transport_iscsi sunrpc ip_tables x_tables
  [   90.690724]  autofs4 btrfs raid10 raid456 async_raid6_recov async_memcpy 
async_pq async_xor async_tx xor hid_generic usbhid hid raid6_pq libcrc32c raid1 
raid0 multipath linear uas usb_storage ast crct10dif_vpmsum i2c_algo_bit 
crc32c_vpmsum ttm drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops 
drm tg3 ahci libahci
  [   90.690937] CPU: 48 PID: 3986 Comm: qemu-system-ppc Not tainted 
4.13.0-12-generic #13-Ubuntu
  [   90.691001] task: c00b122d8700 task.stack: c00b431cc000
  [   90.691167] NIP: c0361224 LR: c0998960 CTR: 
c09a19b0
  [   90.691223] REGS: c00bff61b800 TRAP: 0300   Not tainted  
(4.13.0-12-generic)
  [   90.691277] MSR: 90009033 
  [   90.691282]   CR: 88002844  XER: 
  [   90.691347] CFAR: c099895c DAR: f2d3bda0 DSISR: 4000 
SOFTE: 0 
  [   90.691347] GPR00: c0998960 c00bff61ba80 c15e3000 
c00b4ef61f20 
  [   90.691347] GPR04: c00b44c61680  001f 
001f 
  [   90.691347] GPR08: 001f 02d3bd80 c178e8e8 
c00b5a0c26f0 
  [   90.691347] GPR12: 28002842 cfadf800 c00b52d07880 
c00b44c61680 
  [   90.691347] GPR16:  001f 001f 
c553a560 
  [   90.691347] GPR20: 0001 0002 08000553a560 
c00b5c62a228 
  [   90.691347] GPR24: c5531110 c00b5c632238 0210 
 
  [   90.691347] GPR28: c0998960 c00bff61bc20 c00b4ef61f20 
f2d3bd80 
  [   90.692089] NIP [c0361224] kfree+0x54/0x270
  [   90.692133] LR [c0998960] xhci_urb_free_priv+0x20/0x40
  [   90.692325] Call Trace:
  [   90.692345] [c00bff61ba80] [c00bff61bad0] 0xc00bff61bad0 
(unreliable)
  [   90.692402] [c00bff61bac0] [c0998960] 
xhci_urb_free_priv+0x20/0x40
  [   90.692459] [c00bff61bae0] [c099bfc8] 
xhci_giveback_urb_in_irq.isra.22+0x78/0x190
  [   90.692645] [c00bff61bb40] [c099c350] 
xhci_td_cleanup+0x130/0x200
  [   90.692702] [c00bff61bbc0] [c09a175c] 
handle_tx_event+0x74c/0x1380
  [   90.692759] [c00bff61bcc0] [c09a2894] xhci_irq+0x504/0xf20
  [   90.692808] [c00bff61bde0] [c017b110] 
__handle_irq_event_percpu+0x90/0x300
  [   90.692977] [c00bff61bea0] [c017b3b8] 
handle_irq_event_percpu+0x38/0x90
  [   90.693038] [c00bff61bee0] [c017b474] 
handle_irq_event+0x64/0xb0
  [   90.693094] [c00bff61bf10] [c0180da0] 
handle_fasteoi_irq+0xc0/0x230
  [   90.693155] [c00bff61bf40] [c017972c] 
generic_handle_irq+0x4c/0x70
  [   90.693332] [c00bff61bf60] [c001767c] __do_irq+0x7c/0x1c0
  [   90.693383] [c00bff61bf90] [c002ab70] call_do_irq+0x14/0x24
  [   90.693431] [c00b431cf9d0] [c001785c] do_IRQ+0x9c/0x130
  [   90.693478] [c00b431cfa20] [c0008ac4] 
hardware_interrupt_common+0x114/0x120
  [   90.693663] --- interrupt: 501 at __copy_tofrom_user_power7+0x1f4/0x7cc
  [   90.693663] LR = _copy_to_user+0x3c/0x60
  [   90.693736] [c00b431cfd10] [c00b431cfdc0] 0xc00b431cfdc0 
(unreliable)
  [   90.693797] [c00b431cfd30] [c03bfa90] 

[Kernel-packages] [Bug 1725350] Re: KVM on 17.10 crashes the machine

[Manoj Iyer]

** Changed in: ubuntu-power-systems
   Status: Incomplete => 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/1725350

Title:
  KVM on 17.10 crashes the machine

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

Bug description:
  When you start qemu on a 17.10 machine, the whole machine goes down
  and crashes:

  [   90.689627] Unable to handle kernel paging request for data at address 
0xf2d3bda0
  [   90.689705] Faulting instruction address: 0xc0361224
  [   90.689840] Oops: Kernel access of bad area, sig: 11 [#1]
  [   90.689911] SMP NR_CPUS=2048 
  [   90.689912] NUMA 
  [   90.690053] PowerNV
  [   90.690092] Modules linked in: xt_CHECKSUM iptable_mangle ipt_MASQUERADE 
nf_nat_masquerade_ipv4 iptable_nat xt_conntrack ipt_REJECT nf_reject_ipv4 
xt_tcpudp bridge stp llc kvm_hv kvm_pr kvm ebtable_filter ebtables 
ip6table_filter ip6_tables iptable_filter openvswitch nf_conntrack_ipv6 
nf_nat_ipv6 nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_defrag_ipv6 nf_nat 
nf_conntrack_netlink nf_conntrack nfnetlink idt_89hpesx snd_hda_codec_hdmi xfs 
joydev input_leds mac_hid snd_hda_intel snd_hda_codec snd_hda_core snd_hwdep 
snd_pcm snd_timer snd soundcore ofpart opal_prd cmdlinepart powernv_flash mtd 
at24 ipmi_powernv ipmi_devintf ipmi_msghandler powernv_rng uio_pdrv_genirq 
vmx_crypto ibmpowernv uio ib_iser rdma_cm iw_cm ib_cm ib_core iscsi_tcp 
libiscsi_tcp libiscsi scsi_transport_iscsi sunrpc ip_tables x_tables
  [   90.690724]  autofs4 btrfs raid10 raid456 async_raid6_recov async_memcpy 
async_pq async_xor async_tx xor hid_generic usbhid hid raid6_pq libcrc32c raid1 
raid0 multipath linear uas usb_storage ast crct10dif_vpmsum i2c_algo_bit 
crc32c_vpmsum ttm drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops 
drm tg3 ahci libahci
  [   90.690937] CPU: 48 PID: 3986 Comm: qemu-system-ppc Not tainted 
4.13.0-12-generic #13-Ubuntu
  [   90.691001] task: c00b122d8700 task.stack: c00b431cc000
  [   90.691167] NIP: c0361224 LR: c0998960 CTR: 
c09a19b0
  [   90.691223] REGS: c00bff61b800 TRAP: 0300   Not tainted  
(4.13.0-12-generic)
  [   90.691277] MSR: 90009033 
  [   90.691282]   CR: 88002844  XER: 
  [   90.691347] CFAR: c099895c DAR: f2d3bda0 DSISR: 4000 
SOFTE: 0 
  [   90.691347] GPR00: c0998960 c00bff61ba80 c15e3000 
c00b4ef61f20 
  [   90.691347] GPR04: c00b44c61680  001f 
001f 
  [   90.691347] GPR08: 001f 02d3bd80 c178e8e8 
c00b5a0c26f0 
  [   90.691347] GPR12: 28002842 cfadf800 c00b52d07880 
c00b44c61680 
  [   90.691347] GPR16:  001f 001f 
c553a560 
  [   90.691347] GPR20: 0001 0002 08000553a560 
c00b5c62a228 
  [   90.691347] GPR24: c5531110 c00b5c632238 0210 
 
  [   90.691347] GPR28: c0998960 c00bff61bc20 c00b4ef61f20 
f2d3bd80 
  [   90.692089] NIP [c0361224] kfree+0x54/0x270
  [   90.692133] LR [c0998960] xhci_urb_free_priv+0x20/0x40
  [   90.692325] Call Trace:
  [   90.692345] [c00bff61ba80] [c00bff61bad0] 0xc00bff61bad0 
(unreliable)
  [   90.692402] [c00bff61bac0] [c0998960] 
xhci_urb_free_priv+0x20/0x40
  [   90.692459] [c00bff61bae0] [c099bfc8] 
xhci_giveback_urb_in_irq.isra.22+0x78/0x190
  [   90.692645] [c00bff61bb40] [c099c350] 
xhci_td_cleanup+0x130/0x200
  [   90.692702] [c00bff61bbc0] [c09a175c] 
handle_tx_event+0x74c/0x1380
  [   90.692759] [c00bff61bcc0] [c09a2894] xhci_irq+0x504/0xf20
  [   90.692808] [c00bff61bde0] [c017b110] 
__handle_irq_event_percpu+0x90/0x300
  [   90.692977] [c00bff61bea0] [c017b3b8] 
handle_irq_event_percpu+0x38/0x90
  [   90.693038] [c00bff61bee0] [c017b474] 
handle_irq_event+0x64/0xb0
  [   90.693094] [c00bff61bf10] [c0180da0] 
handle_fasteoi_irq+0xc0/0x230
  [   90.693155] [c00bff61bf40] [c017972c] 
generic_handle_irq+0x4c/0x70
  [   90.693332] [c00bff61bf60] [c001767c] __do_irq+0x7c/0x1c0
  [   90.693383] [c00bff61bf90] [c002ab70] call_do_irq+0x14/0x24
  [   90.693431] [c00b431cf9d0] [c001785c] do_IRQ+0x9c/0x130
  [   90.693478] [c00b431cfa20] [c0008ac4] 
hardware_interrupt_common+0x114/0x120
  [   90.693663] --- interrupt: 501 at __copy_tofrom_user_power7+0x1f4/0x7cc
  [   90.693663] LR = _copy_to_user+0x3c/0x60
  [   90.693736] [c00b431cfd10] [c00b431cfdc0] 0xc00b431cfdc0 
(unreliable)
  [   90.693797] 

[Kernel-packages] [Bug 1729119] Re: NVMe timeout is too short

[Stefan Bader]

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

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

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

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

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

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

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

Title:
  NVMe timeout is too short

Status in linux package in Ubuntu:
  Confirmed
Status in linux-aws package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Fix Committed
Status in linux-aws source package in Xenial:
  Fix Released
Status in linux source package in Zesty:
  Fix Committed
Status in linux-aws source package in Zesty:
  Invalid
Status in linux source package in Artful:
  Fix Committed
Status in linux-aws source package in Artful:
  Invalid

Bug description:
  [SRU Justification]

  [Impact]
  Some NVMe operations time out too quickly. The module parameters allow the 
timeouts to be extended, but only up to 255s, as the counters are bytes. 

  [Fix]
  The underlying parameters are unsigned ints, so make the module parameters 
unsigned ints too, by picking patch 
http://lists.infradead.org/pipermail/linux-nvme/2017-September/012701.html

  [Regression Potential]
  Very limited: only types of module parameters are changing, the patch is 
easily reviewable.

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

-- 
Mailing list: https://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 1728098] Re: [kernel] tty/hvc: Use opal irqchip interface if available

[Manoj Iyer]

** Changed in: ubuntu-power-systems
   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/1728098

Title:
  [kernel] tty/hvc: Use opal irqchip interface if available

Status in The Ubuntu-power-systems project:
  Fix Committed
Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Xenial:
  Fix Committed

Bug description:

  == SRU Justification ==
  This bug is fixed by commit 00dab8187e18.  The commit updates the hvc
  driver to use the OPAL irqchip if made available by the running firmware.
  If it is not present, the driver falls back to the existing OPAL event 
number.   

  Commit 00dab8187e18 was added to mainline is v4.8-rc1, so it is not needed in 
  releases newer than Xenial.  The commit is a clean cherry pick in Xenial.

  
  == Fix ==
  commit 00dab8187e182da41122f66c207707b192509df4
  Author: Sam Mendoza-Jonas 
  Date:   Mon Jul 11 13:38:58 2016 +1000

  tty/hvc: Use opal irqchip interface if available

  
  == Regression Potential ==
  This change is specific to the hvc driver and has been in mainline since 
v4.8-rc1
  without any issues reported.

  == Test Case ==
  A test kernel was built with this patch and tested by the original bug 
reporter.
  The bug reporter states the test kernel resolved the bug.

  
  ---Problem Description---
  Please backport console irq patch .

  commit 00dab8187e182da41122f66c207707b192509df4
  Author: Sam Mendoza-Jonas 
  Date:   Mon Jul 11 13:38:58 2016 +1000

  tty/hvc: Use opal irqchip interface if available

  Update the hvc driver to use the OPAL irqchip if made available by the
  running firmware. If it is not present, the driver falls back to the
  existing OPAL event number.

  Signed-off-by: Samuel Mendoza-Jonas 
  Signed-off-by: Michael Ellerman 

  ---uname output---
  Linux tul217p1 4.4.0-98-generic #121-Ubuntu SMP Tue Oct 10 14:23:01 UTC 2017 
ppc64le ppc64le ppc64le GNU/Linux

  Machine Type = FSP based PowerNV system

  Canonical,

  We need this patch in 16.04 GA 4.4 kernel. This fix will avoid the
  following error:

  Oct 19 22:15:07 tul217p1 kernel: sched: RT throttling activated
  Oct 19 22:15:49 tul217p1 kernel: INFO: rcu_sched self-detected stall on CPU
  Oct 19 22:15:49 tul217p1 kernel:21-...: (85 GPs behind) 
idle=d29/142/0 softirq=26316/26316 fqs=4417
  Oct 19 22:15:49 tul217p1 kernel: (t=5250 jiffies g=30019 c=30018 
q=20591)
  Oct 19 22:15:49 tul217p1 kernel: Call Trace:
  Oct 19 22:15:49 tul217p1 kernel: [c007f4d0f110] [c00fcbe0] 
sched_show_task+0xe0/0x180 (unreliable)
  Oct 19 22:15:49 tul217p1 kernel: [c007f4d0f180] [c013fcf4] 
rcu_dump_cpu_stacks+0xe4/0x150
  Oct 19 22:15:49 tul217p1 kernel: [c007f4d0f1d0] [c0145424] 
rcu_check_callbacks+0x6b4/0x9b0
  Oct 19 22:15:49 tul217p1 kernel: [c007f4d0f300] [c014d288] 
update_process_times+0x58/0xa0
  Oct 19 22:15:49 tul217p1 kernel: [c007f4d0f330] [c01649b8] 
tick_sched_handle.isra.6+0x48/0xe0
  Oct 19 22:15:49 tul217p1 kernel: [c007f4d0f370] [c0164ab4] 
tick_sched_timer+0x64/0xd0
  Oct 19 22:15:49 tul217p1 kernel: [c007f4d0f3b0] [c014dd54] 
__hrtimer_run_queues+0x124/0x450
  Oct 19 22:15:49 tul217p1 kernel: [c007f4d0f440] [c014ed7c] 
hrtimer_interrupt+0xec/0x2c0
  Oct 19 22:15:49 tul217p1 kernel: [c007f4d0f500] [c001f5fc] 
__timer_interrupt+0x8c/0x290
  Oct 19 22:15:49 tul217p1 kernel: [c007f4d0f550] [c001f9b0] 
timer_interrupt+0xa0/0xe0
  Oct 19 22:15:49 tul217p1 kernel: [c007f4d0f580] [c00099d8] 
restore_check_irq_replay+0x54/0x70
  Oct 19 22:15:49 tul217p1 kernel: --- interrupt: 901 at 
arch_local_irq_restore+0x74/0x90
   LR = arch_local_irq_restore+0x74/0x90
  Oct 19 22:15:49 tul217p1 kernel: [c007f4d0f870] [7fff] 
0x7fff (unreliable)
  Oct 19 22:15:49 tul217p1 kernel: [c007f4d0f890] [c00bf808] 
__do_softirq+0xd8/0x3e0
  Oct 19 22:15:49 tul217p1 kernel: [c007f4d0f980] [c00bfd88] 
irq_exit+0xc8/0x100
  Oct 19 22:15:49 tul217p1 kernel: [c007f4d0f9a0] [c001f9b4] 
timer_interrupt+0xa4/0xe0
  Oct 19 22:15:49 tul217p1 kernel: [c007f4d0f9d0] [c00099d8] 
restore_check_irq_replay+0x54/0x70
  Oct 19 22:15:49 tul217p1 kernel: --- interrupt: 901 at 
irq_work_queue+0x60/0xd0
   LR = irq_work_queue+0xa4/0xd0
  Oct 19 22:15:49 tul217p1 kernel: [c007f4d0fcc0] [c007f4d0fd00] 
0xc007f4d0fd00 (unreliable)
  Oct 19 22:15:49 tul217p1 kernel: [c007f4d0fcf0] [c0076a98] 
opal_handle_events+0x108/0x130
  Oct 19 22:15:49 tul217p1 kernel: [c007f4d0fd40] [c0070fc8] 

[Kernel-packages] [Bug 1727331] Re: NMI watchdog: BUG: soft lockup on Guest upon boot (KVM)

[Manoj Iyer]

** Changed in: ubuntu-power-systems
   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/1727331

Title:
  NMI watchdog: BUG: soft lockup on Guest upon boot (KVM)

Status in The Ubuntu-power-systems project:
  Fix Committed
Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Xenial:
  Fix Committed

Bug description:
  == SRU Justification ==
  Xenial does not include the patch:
  "KVM: PPC: Book3S: Treat VTB as a per-subcore register, not per-thread",
  which is commit 88b02cf97bb7 in the upstream Linux kernel repository. The
  symptom of not having this patch is that guests running with threads > 1
  (that is, in SMT2, SMT4 or SMT8 mode) can give spurious soft-lockup messages 
  when they are not in fact locked up, if the guest kernel uses the VTB
  (virtual timebase) register in its softlockup detector code.

  IBM provided this backport of commit 88b02cf97bb7.

  == Fix ==
  commit 88b02cf97bb7e742db3e31671d54177e3e19fd89
  Author: Paul Mackerras 
  Date:   Thu Sep 15 13:42:52 2016 +1000

  KVM: PPC: Book3S: Treat VTB as a per-subcore register, not per-
  thread

  == Regression Potential ==
  This patch is specific to powerpc.  It was provided by and tested by IBM.



  Environment:
  Host OS: Ubuntu 16.04 (4.4.0-97-generic)
  Guest OS: Ubuntu 16.04

  Host is running NovaLink and GPFS.  Guest gets filesystem from gpfs
  cluster.

  Issue:

  While booting the guest OS went into recovery.  dmesg shows CPU soft
  lockup.  This issue is easily recreatable when multiple VMs (about 10)
  are being started simultaneously.

  
...

   - Paul Mackerras  - 2017-10-24 00:42:25 ==

  Looking at kernel sources:

  The Ubuntu host kernel (4.4.0-97) does not include the patch "KVM:
  PPC: Book3S: Treat VTB as a per-subcore register, not per-thread",
  which is commit 88b02cf97bb7 in the upstream Linux kernel repository.
  The symptom of not having this patch is that guests running with
  threads > 1 (that is, in SMT2, SMT4 or SMT8 mode) can give spurious
  soft-lockup messages when they are not in fact locked up, if the guest
  kernel uses the VTB (virtual timebase) register in its softlockup
  detector code.

  This is a backport of commit 88b02cf97bb7 from the upstream Linux
  kernel repository to the Ubuntu 4.4 kernel. It is the fix for the
  problem of seeing spurious soft lockup messages in guests running in
  an SMT mode greater than 1.

  These tests were run on a system with 20 cores.  Each VM had 1 core and 4 
threads (SMT=4).
  It is working very well with this patch

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

-- 
Mailing list: https://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 1732978] Re: Ubuntu 17.10: Include patch "crypto: vmx - Use skcipher for ctr fallback"

[Manoj Iyer]

** Tags added: triage-g

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

Title:
  Ubuntu 17.10: Include patch "crypto: vmx - Use skcipher for ctr
  fallback"

Status in The Ubuntu-power-systems project:
  Triaged
Status in linux package in Ubuntu:
  Triaged
Status in linux source package in Artful:
  Triaged

Bug description:
  == Comment: #0 - Paulo Flabiano Smorigo  - 2017-11-17 
10:29:14 ==
  Ubuntu 17.10 uses linux kernel 4.13 witch has a problem with the fallback 
cipher for CTR mode. The commit bellow fixes this problem by using the new 
structure for the generic ciphers. Please add it to the kernel package.

  
https://git.kernel.org/pub/scm/linux/kernel/git/herbert/crypto-2.6.git/commit/?id=e666d4e9ceec94c0a88c94b7db31d56474da43b3

  == Comment: #1 - VIPIN K. PARASHAR  - 2017-11-17 
13:38:05 ==
  (In reply to comment #0)
  > Ubuntu 17.10 uses linux kernel 4.13 witch has a problem with the fallback
  > cipher for CTR mode. The commit bellow fixes this problem by using the new
  > structure for the generic ciphers. Please add it to the kernel package.
  > 
  > https://git.kernel.org/pub/scm/linux/kernel/git/herbert/crypto-2.6.git/
  > commit/?id=e666d4e9ceec94c0a88c94b7db31d56474da43b3

  Which is commit e666d4e9ceec94

  commit e666d4e9ceec94c0a88c94b7db31d56474da43b3
  Author: Paulo Flabiano Smorigo 
  Date:   Mon Oct 16 20:54:19 2017 -0200

  crypto: vmx - Use skcipher for ctr fallback
  
  Signed-off-by: Paulo Flabiano Smorigo 
  Signed-off-by: Herbert Xu 

  Its available with 4.14 kernel.

  
  Hello Canonical,

  Please include commit e666d4e9ceec94 - "crypto: vmx - Use skcipher for ctr 
fallback"
  with Ubuntu 17.10 kernel.

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

-- 
Mailing list: https://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 1731264] Re: linux: 4.4.0-101.124 -proposed tracker

[Kleber Sacilotto de Souza]

** Changed in: kernel-sru-workflow/snap-release-to-stable
   Status: Confirmed => Fix Released

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

Title:
  linux: 4.4.0-101.124 -proposed tracker

Status in Kernel SRU Workflow:
  Fix Released
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Fix Released
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  Fix Released
Status in Kernel SRU Workflow promote-to-updates series:
  Fix Released
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow snap-certification-testing series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-beta series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-candidate series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-edge series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-stable series:
  Fix Released
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  Fix Released

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

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

  backports: 1731266
  derivatives:
  -- swm properties --
  boot-testing-requested: true
  phase: Released
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

-- 
Mailing list: https://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 1730660] Re: Set PANIC_TIMEOUT=10 on Power Systems

[Stefan Bader]

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

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

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

** Changed in: linux (Ubuntu Xenial)
   Status: New => 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/1730660

Title:
  Set PANIC_TIMEOUT=10 on Power Systems

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

Bug description:
  [Impact]
  When stopping CPUs fail when doing kdump, the system will hang 
indefinitively, instead of rebooting. With this option set, it will reboot 
after 10 seconds when that happens.

  This setting has been the default for trusty, where panic_timeout is
  10. Later releases set it to 0.

  [Test Case]
  When booting a kernel, /proc/sys/kernel/panic should be 10. It's 0 for 
xenial, zesty and artful. After the fix, it's 10.

  [Regression Potential]
  For users that rely on the setting as 0, they will see their system reboot 10 
seconds after a panic. They can set it back to 0 or other value. Though, on 
some rare cases, the system might not boot enough for this setting to be set. 
Balancing that with the case where kdump is used and the system is expected to 
boot, we expect the 10 seconds setting is okay.

  ===

  For ppc64le, in some rare crash cases, kdump won't load unless timeout
  is greater than 0. Only 10 has been tested by IBM, so using a smaller
  value may not work.

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

-- 
Mailing list: https://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 1732894] Re: CPU call trace on AMD Raven Ridge after S3

[Stefan Bader]

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

** Changed in: linux (Ubuntu Artful)
   Status: New => 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/1732894

Title:
  CPU call trace on AMD Raven Ridge after S3

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

Bug description:
  [Impact]

  Dmesg shows a call trace after S3 cycle.

  This has been fixed in v4.14-rc1 with

  commit 9662d43f523dfc0dc242ec29c2921c43898d6ae5
  Author: Yazen Ghannam 
  Date:   Mon Jul 24 12:12:28 2017 +0200

  x86/mce/AMD: Allow any CPU to initialize the smca_banks array

  Current SMCA implementations have the same banks on each CPU with the
  non-core banks only visible to a "master thread" on each die. Practically,
  this means the smca_banks array, which describes the banks, only needs to
  be populated once by a single master thread.
  
  CPU 0 seemed like a good candidate to do the populating. However, it's
  possible that CPU 0 is not enabled in which case the smca_banks array 
won't
  be populated.
  
  Rather than try to figure out another master thread to do the populating,
  we should just allow any CPU to populate the array.
  
  Drop the CPU 0 check and return early if the bank was already initialized.
  Also, drop the WARNing about an already initialized bank, since this will
  be a common, expected occurrence.
  
  The smca_banks array is only populated at boot time and CPUs are brought
  online sequentially. So there's no need for locking around the array.
  
  If the first CPU up is a master thread, then it will populate the array
  with all banks, core and non-core. Every CPU afterwards will return
  early. If the first CPU up is not a master thread, then it will populate
  the array with all core banks. The first CPU afterwards that is a master
  thread will skip populating the core banks and continue populating the
  non-core banks.
  
  Signed-off-by: Yazen Ghannam 
  Signed-off-by: Borislav Petkov 
  Acked-by: Jack Miller 
  Cc: Linus Torvalds 
  Cc: Peter Zijlstra 
  Cc: Thomas Gleixner 
  Cc: Tony Luck 
  Cc: linux-edac 
  Link: http://lkml.kernel.org/r/20170724101228.17326-4...@alien8.de
  Signed-off-by: Ingo Molnar 

  [Test case]

  Suspend/resume Raven Ridge, see that it doesn't show the call trace
  any more.

  [Regression potential]

  4.14 released with it, and it fixes code which "for now" checked only
  CPU 0, so regressions potential is slim to none.

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

-- 
Mailing list: https://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 1728941] Re: linux: -proposed tracker

[Kleber Sacilotto de Souza]

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

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

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

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

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

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

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

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

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

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

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

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

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

Title:
  linux:  -proposed tracker

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

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

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

  backports: 1728943
  derivatives:

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

-- 
Mailing list: https://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 1728943] Re: linux-lts-trusty: -proposed tracker

[Kleber Sacilotto de Souza]

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Title:
  linux-lts-trusty:  -proposed tracker

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

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

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

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

-- 
Mailing list: https://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 1728939] Re: linux: -proposed tracker

[Kleber Sacilotto de Souza]

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Title:
  linux:  -proposed tracker

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

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

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

  backports: 
  derivatives:

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

-- 
Mailing list: https://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 1725322] Re: kernel 4.4.0.97.102 breaks DFS

[Juriaan Bakx]

That last sentence was incorrect, Instead of "Still this only happens
with kernels released after 4.4.0-96" you should read Still this only
happens with kernels released after 4.4.0-92"

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

Title:
  kernel 4.4.0.97.102 breaks DFS

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

Bug description:
  OS: Ubuntu Desktop 16.04.3

  We connect to Windows DFS using automounter with our Linux 16.04
  workstations to let users access the windows shares. Until kernel
  version 4.4.0-96 this worked without any issues. However if a computer
  updates to kernel 4.4.0.97.102, using the same configs and samba
  version, it stops working and reports a "ls: cannot access xx: File
  name too long" error. (where xx is a foldername)

  Also if you run "ls -all" you will see:

  d? ? ? ?   ?? Applications

  on the same computer selecting kernel 4.4.0.21.22 at grub menu:

  drwx--x--x 2 root  root0 Oct 20 16:44 Applications

  Mount commando output (removed hostnames and IP numbers ) on computer
  with kernel 4.4.0.21.22

  //XXX/Public on /vol/winshare/Public type cifs
  
(rw,relatime,vers=1.0,sec=krb5,cache=strict,multiuser,uid=0,noforceuid,gid=0,noforcegid,addr=x.x.x.x
  
file_mode=0755,dir_mode=0755,nounix,mapposix,noperm,rsize=61440,wsize=65536,actimeo=1)

  Mount commando output (removed hostnames and IP numbers ) on the same
  computer with kernel 4.4.0.97.102

  //XXX/Public on /vol/winshare/Public type cifs
  
(rw,relatime,vers=1.0,sec=krb5,cache=strict,multiuser,uid=0,noforceuid,gid=0,noforcegid,addr=x.x.x.x,file_mode=0755,dir_mode=0755,nounix,mapposix,noperm,rsize=61440,wsize=65536,echo_interval=60,actimeo=1)

  During these tests the only thing that changed is the running kernel,
  no other changes were applied.

  autofs config file used for this connection

  Public   -fstype=cifs,sec=krb5,multiuser,nounix,noserverino
  :///Public

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

-- 
Mailing list: https://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 1725322] Re: kernel 4.4.0.97.102 breaks DFS

[Juriaan Bakx]

Interestingly when running sudo ls, using the machine keytab, is works.
So looks for me the problem is somewhere in the user kerberos ticket.
Still this only happens with kernels released after 4.4.0-96

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

Title:
  kernel 4.4.0.97.102 breaks DFS

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

Bug description:
  OS: Ubuntu Desktop 16.04.3

  We connect to Windows DFS using automounter with our Linux 16.04
  workstations to let users access the windows shares. Until kernel
  version 4.4.0-96 this worked without any issues. However if a computer
  updates to kernel 4.4.0.97.102, using the same configs and samba
  version, it stops working and reports a "ls: cannot access xx: File
  name too long" error. (where xx is a foldername)

  Also if you run "ls -all" you will see:

  d? ? ? ?   ?? Applications

  on the same computer selecting kernel 4.4.0.21.22 at grub menu:

  drwx--x--x 2 root  root0 Oct 20 16:44 Applications

  Mount commando output (removed hostnames and IP numbers ) on computer
  with kernel 4.4.0.21.22

  //XXX/Public on /vol/winshare/Public type cifs
  
(rw,relatime,vers=1.0,sec=krb5,cache=strict,multiuser,uid=0,noforceuid,gid=0,noforcegid,addr=x.x.x.x
  
file_mode=0755,dir_mode=0755,nounix,mapposix,noperm,rsize=61440,wsize=65536,actimeo=1)

  Mount commando output (removed hostnames and IP numbers ) on the same
  computer with kernel 4.4.0.97.102

  //XXX/Public on /vol/winshare/Public type cifs
  
(rw,relatime,vers=1.0,sec=krb5,cache=strict,multiuser,uid=0,noforceuid,gid=0,noforcegid,addr=x.x.x.x,file_mode=0755,dir_mode=0755,nounix,mapposix,noperm,rsize=61440,wsize=65536,echo_interval=60,actimeo=1)

  During these tests the only thing that changed is the running kernel,
  no other changes were applied.

  autofs config file used for this connection

  Public   -fstype=cifs,sec=krb5,multiuser,nounix,noserverino
  :///Public

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

-- 
Mailing list: https://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 1729277] Re: linux-aws: 4.4.0-1003.3 -proposed tracker

[Brad Figg]

The package has been published and the bug is being set to Fix Released


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

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

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1731264
  phase: Promoted to security
  proposed-announcement-sent: true
  proposed-testing-requested: true
+ kernel-stable-phase-changed:Monday, 20. November 2017 13:05 UTC
+ kernel-stable-phase:Released

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1731264
- phase: Promoted to security
+ phase: Released
  proposed-announcement-sent: true
  proposed-testing-requested: true
- kernel-stable-phase-changed:Monday, 20. November 2017 13:05 UTC
- kernel-stable-phase:Released

** Tags removed: kernel-release-tracking-bug-live

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

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

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

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: 1731264
  phase: Released
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

-- 
Mailing list: https://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 1731264] Re: linux: 4.4.0-101.124 -proposed tracker

[Brad Figg]

The package has been published and the bug is being set to Fix Released


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

** Changed in: kernel-sru-workflow/snap-release-to-stable
   Status: New => Confirmed

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

** Description changed:

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

** Description changed:

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

** Tags removed: kernel-release-tracking-bug-live

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

Title:
  linux: 4.4.0-101.124 -proposed tracker

Status in Kernel SRU Workflow:
  Fix Released
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Fix Released
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  Fix Released
Status in Kernel SRU Workflow promote-to-updates series:
  Fix Released
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow snap-certification-testing series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-beta series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-candidate series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-edge series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-stable series:
  Confirmed
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  Fix Released

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

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

  backports: 1731266
  derivatives:
  -- swm properties --
  boot-testing-requested: true
  phase: Released
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

-- 
Mailing list: https://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 1732535] Re: linux-aws: 4.4.0-1041.50 -proposed tracker

[Brad Figg]

The package has been published and the bug is being set to Fix Released


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

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

** Description changed:

  This bug is for tracking the 4.4.0-1041.50 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: 1731264
  phase: Promoted to security
  proposed-announcement-sent: true
  proposed-testing-requested: true
+ kernel-stable-phase-changed:Monday, 20. November 2017 13:05 UTC
+ kernel-stable-phase:Released

** Description changed:

  This bug is for tracking the 4.4.0-1041.50 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: 1731264
- phase: Promoted to security
+ phase: Released
  proposed-announcement-sent: true
  proposed-testing-requested: true
- kernel-stable-phase-changed:Monday, 20. November 2017 13:05 UTC
- kernel-stable-phase:Released

** Tags removed: kernel-release-tracking-bug-live

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

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

Status in Kernel SRU Workflow:
  Fix Released
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  Fix Released
Status in Kernel SRU Workflow promote-to-updates series:
  Fix Released
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow snap-certification-testing series:
  Invalid
Status in Kernel SRU Workflow snap-release-to-beta series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-candidate series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-edge series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-stable series:
  Invalid
Status in Kernel SRU Workflow upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux-aws package in Ubuntu:
  Invalid
Status in linux-aws source package in Xenial:
  Fix Released

Bug description:
  This bug is for tracking the 4.4.0-1041.50 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: 1731264
  phase: Released
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

-- 
Mailing list: https://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 1733321] 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 1733321

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

** Tags added: artful

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

Title:
  network-manager ADT tests fail with on ppc64el with artful/linux
  4.13.0.17.18

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  ppc64el ADT log:
  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
  /autopkgtest-artful/artful/ppc64el/n/network-
  manager/20171120_100719_28642@/log.gz

  Testcase output:
  -
  autopkgtest [10:04:48]: test killswitches-no-urfkill: [---
  make -C /lib/modules/4.13.0-17-generic/build 
KBUILD_SRC=/lib/modules/4.13.0-17-generic/build 
M=/tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests
  make[1]: Entering directory '/usr/src/linux-headers-4.13.0-17-generic'
AR  /tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests/built-in.o
CC [M]  /tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests/fake-rfkill.o
Building modules, stage 2.
MODPOST 1 modules
CC  /tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests/fake-rfkill.mod.o
LD [M]  /tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests/fake-rfkill.ko
  make[1]: Leaving directory '/usr/src/linux-headers-4.13.0-17-generic'
  ERROR: NM could not track device state.
  autopkgtest [10:05:20]: test killswitches-no-urfkill: ---]
  autopkgtest [10:05:20]: test killswitches-no-urfkill:  - - - - - - - - - - 
results - - - - - - - - - -
  killswitches-no-urfkill FAIL non-zero exit status 1
  -

  Package versions [artful/ppc64el]:
  network-manager 1.8.4-1ubuntu3
  linux-meta 4.13.0.17.18

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

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