date:20180305

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

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

** Also affects: linux (Ubuntu Bionic)
   Importance: Critical
 Assignee: Ubuntu on IBM Power Systems Bug Triage (ubuntu-power-triage)
   Status: Triaged

** Changed in: linux (Ubuntu Bionic)
 Assignee: Ubuntu on IBM Power Systems Bug Triage (ubuntu-power-triage) => 
Joseph Salisbury (jsalisbury)

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

Title:
  Ubuntu 18.04 - Performance: Radix page fault handler bug in KVM

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

Bug description:
  == Comment: #0 - JENIFER HOPPER  - 2018-02-27 17:25:59 ==
  +++ This bug was initially created as a clone of Bug #165215 +++

  ---Problem Description---
  Paul Mackerras has posted a fix to a Radix page fault handler bug in KVM:

  http://patchwork.ozlabs.org/patch/877033/
  " KVM: PPC: Book3S HV: Fix handling of large pages in radix page fault 
handler "

  This is critical for P9 KVM performance. Using an open source database 
workload, we saw an 11% throughput improvement with this patch when the guest 
was backed w/ 2MB hugepages. Without this patch, hugepage backing does not help 
performance compared to base page size. 
   
  ---uname output---
  18.04 lts
   
  Machine Type = 5104-22C 
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
Back guest w/ 2MB pages, run a throughput test and compare performance.
   
  Contact Information = jhop...@us.ibm.com

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

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

[Kernel-packages] [Bug 1752336] Re: BUG: Bad page map in process CompositorTileW pte:94aadfb0 pmd:943ae067

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.16 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.16-rc4

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

Title:
  BUG: Bad page map in process CompositorTileW  pte:94aadfb0
  pmd:943ae067

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  This just happened

  ProblemType: KernelOops
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-10-generic 4.15.0-10.11
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  Annotation: Your system might become unstable now and might need to be 
restarted.
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  gdm3937 F pulseaudio
fabio  4501 F pulseaudio
   /dev/snd/controlC0:  gdm3937 F pulseaudio
fabio  4501 F pulseaudio
  Date: Wed Feb 28 16:18:53 2018
  Failure: oops
  HibernationDevice: RESUME=UUID=f6770099-4a42-48e3-b4ab-588190b2a701
  InstallationDate: Installed on 2017-08-21 (191 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170820)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0bda:57b4 Realtek Semiconductor Corp. 
   Bus 001 Device 008: ID 13d3:3408 IMC Networks 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. X550JK
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-10-generic 
root=UUID=3eab3ace-7b67-4e6a-aea7-d31b73cc4819 ro quiet splash vt.handoff=1
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: kerneloops-daemon N/A
  SourcePackage: linux
  Title: BUG: Bad page map in process CompositorTileW  pte:94aadfb0 pmd:943ae067
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/08/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X550JK.303
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X550JK
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrX550JK.303:bd10/08/2014:svnASUSTeKCOMPUTERINC.:pnX550JK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX550JK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: X
  dmi.product.name: X550JK
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

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

[Kernel-packages] [Bug 1749744] Re: kernel warning

2018-03-05 Thread Kai-Heng Feng

Please try drm-intel-nightly [1]. If the issue still happen,

then file an upstream bug at https://bugs.freedesktop.org/
Product: DRI
Component: DRM/Intel

[1] kernel.ubuntu.com/~kernel-ppa/mainline/drm-intel-nightly/current/

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

Title:
  kernel warning

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I get very often this kernel oops:

  93228.008170] WARN_ON(i915_gem_object_has_pinned_pages(obj))
  [93228.008241] [ cut here ]
  [93228.008341] WARNING: CPU: 0 PID: 25751 at 
/build/linux-UKCsxy/linux-4.13.0/drivers/gpu/drm/i915/i915_gem.c:4422 
__i915_gem_free_objects+0x2ba/0x2f0 [i915]
  [93228.008342] Modules linked in: ccm xt_tcpudp ip6t_rpfilter ip6t_REJECT 
nf_reject_ipv6 ipt_REJECT nf_reject_ipv4 xt_conntrack ip_set nfnetlink 
ebtable_nat ebtable_broute bridge stp llc ip6table_nat nf_conntrack_ipv6 
nf_defrag_ipv6 nf_nat_ipv6 ip6table_mangle ip6table_raw ip6table_security 
iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack 
libcrc32c iptable_mangle iptable_raw iptable_security ebtable_filter ebtables 
ip6table_filter ip6_tables iptable_filter rfcomm bnep cdc_ether usbnet mii 
cdc_wdm cdc_acm coretemp kvm_intel snd_hda_codec_conexant snd_hda_codec_generic 
kvm irqbypass btusb btrtl snd_hda_intel snd_hda_codec snd_hda_core snd_hwdep 
snd_pcm btbcm btintel snd_seq_midi input_leds serio_raw bluetooth arc4 
snd_seq_midi_event thinkpad_acpi nvram wmi_bmof lpc_ich snd_rawmidi
  [93228.008402]  ecdh_generic iwldvm mac80211 iwlwifi cfg80211 snd_seq 
snd_seq_device snd_timer shpchp snd mei_me mei soundcore mac_hid binfmt_misc 
sch_fq_codel parport_pc ppdev lp parport ip_tables x_tables autofs4 hid_generic 
usbhid hid psmouse i915 ahci libahci i2c_algo_bit drm_kms_helper e1000e 
syscopyarea ptp sysfillrect sysimgblt fb_sys_fops pps_core drm wmi video
  [93228.008440] CPU: 0 PID: 25751 Comm: kworker/0:0 Tainted: GW   
4.13.0-32-lowlatency #35-Ubuntu
  [93228.008442] Hardware name: LENOVO 7470WGU/7470WGU, BIOS 6DET72WW (3.22 ) 
10/25/2012
  [93228.008485] Workqueue: events __i915_gem_free_work [i915]
  [93228.008488] task: 881ab17d4a00 task.stack: a03e01ca8000
  [93228.008531] RIP: 0010:__i915_gem_free_objects+0x2ba/0x2f0 [i915]
  [93228.008533] RSP: 0018:a03e01cabe00 EFLAGS: 00010286
  [93228.008535] RAX: 002e RBX: 881a37abcdc0 RCX: 
a2a62fc8
  [93228.008537] RDX:  RSI: 0092 RDI: 
0283
  [93228.008538] RBP: a03e01cabe30 R08: 0708 R09: 
a2f73600
  [93228.008540] R10: a03e01cabdd8 R11:  R12: 
8819f5e0ec00
  [93228.008541] R13: 881aac343f2c R14: 881aac34 R15: 
1000
  [93228.008544] FS:  () GS:881abbc0() 
knlGS:
  [93228.008546] CS:  0010 DS:  ES:  CR0: 80050033
  [93228.008547] CR2: 562440d00d80 CR3: 000130214000 CR4: 
06f0
  [93228.008549] Call Trace:
  [93228.008597]  __i915_gem_free_work+0x38/0x50 [i915]
  [93228.008604]  process_one_work+0x1de/0x430
  [93228.008607]  worker_thread+0x48/0x400
  [93228.008611]  kthread+0x125/0x140
  [93228.008613]  ? process_one_work+0x430/0x430
  [93228.008615]  ? kthread_create_on_node+0x70/0x70
  [93228.008620]  ret_from_fork+0x1f/0x30
  [93228.008622] Code: ff e8 18 cd 3a e1 e9 b6 fd ff ff 48 89 df e8 4e ea ff ff 
e9 b2 fe ff ff 48 c7 c6 88 b0 55 c0 48 c7 c7 95 c5 54 c0 e8 17 2d 49 e1 <0f> ff 
c7 83 d0 01 00 00 00 00 00 00 e9 74 fe ff ff 4c 89 f7 e8 
  [93228.008667] ---[ end trace 11aef733e4977a50 ]---


  
  Ubuntu 4.13.0-32.35-lowlatency 4.13.13

  
  00:00.0 Host bridge [0600]: Intel Corporation Mobile 4 Series Chipset Memory 
Controller Hub [8086:2a40] (rev 07)
  Subsystem: Lenovo Mobile 4 Series Chipset Memory Controller Hub 
[17aa:20e0]
  Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR+ FastB2B- DisINTx-
  Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- 
SERR- 

  00:02.0 VGA compatible controller [0300]: Intel Corporation Mobile 4 Series 
Chipset Integrated Graphics Controller [8086:2a42] (rev 07) (prog-if 00 [VGA 
controller])
  Subsystem: Lenovo Mobile 4 Series Chipset Integrated Graphics 
Controller [17aa:20e4]
  Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
  Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- 
SERR- 
  Kernel driver in use: i915
  Kernel modules: i915

  00:02.1 Display controller [0380]: Intel Corporation Mobile 4 Series Chipset 
Integrated Graphics Controller [8086:2a43] (rev 07)
  Subsystem: Lenovo Mobile 4 Series Chipset Integrated Graphics 
Controller [17aa:20e4]
  Control: I/O+

[Kernel-packages] [Bug 1753371] Re: Ubuntu 18.04 - Kernel crash on nvme subsystem-reset /dev/nvme0 (Bolt / NVMe)

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

** No longer affects: linux (Ubuntu)

** Package changed: kernel-package (Ubuntu) => linux (Ubuntu)

** Also affects: ubuntu-power-systems
   Importance: Undecided
   Status: New

** Changed in: ubuntu-power-systems
   Importance: Undecided => Critical

** Changed in: ubuntu-power-systems
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

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

Title:
  Ubuntu 18.04 - Kernel crash on nvme subsystem-reset /dev/nvme0 (Bolt /
  NVMe)

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

Bug description:
  == Comment: #1 - NAVEED A. UPPINANGADY SALIH  -
  2018-02-25 23:45:13 ==

  
  == Comment: #6 - Wen Xiong  - 2018-02-27 10:41:23 ==
  hi Naveed,

  nvme subsystem-reset calls EEH recovery path. Is EEH recovery working
  with Bolt on this machine?

  Thanks,
  Wendy

  == Comment: #11 - Wen Xiong  - 2018-03-02 16:03:46 ==
  The following patch should fix the issue.

  http://lists.infradead.org/pipermail/linux-
  nvme/2018-February/015745.html

  It should be accepted into community soon. Keith has agreed to queue
  up for 4.16.

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

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

[Kernel-packages] [Bug 1752350] Re: Bionic x86_64 Linux Kernel 4.15 fails to boot on Xen

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

** Also affects: linux (Ubuntu Bionic)
   Importance: High
   Status: Confirmed

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

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

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

Title:
  Bionic x86_64 Linux Kernel 4.15 fails to boot on Xen

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

Bug description:
  The Linux Kernel 4.15 from bionic on x86_64 immediately crashes when
  booted as a dom0 under Xen.

  A similar bug was reported by someone else for archlinux
  (https://bugs.archlinux.org/task/57500).

  A patch exists for 4.16. I tried this patch on 4.15.0-10-generic, it
  fixes the problem for me.
  
(https://git.kernel.org/pub/scm/linux/kernel/git/xen/tip.git/patch/?id=4f277295e54c5b7340e48efea3fc5cc21a2872b7).

  Xen output:

  (XEN) Xen version 4.9.0 (Ubuntu 4.9.0-0ubuntu3) (stefan.ba...@canonical.com) 
(gcc (Ubuntu 7.2.0-8ubuntu2) 7.2.0) debug=n  Fri Oct 13 15:58:41 UTC 2017
  (XEN) Bootloader: GRUB 2.02~beta2-36ubuntu3.9
  (XEN) Command line: placeholder com1=115200,8N1 console=com1,vga
  (XEN) Xen image load base address: 0
  (XEN) Video information:
  (XEN)  VGA is text mode 80x25, font 8x16
  (XEN)  VBE/DDC methods: none; EDID transfer time: 0 seconds
  (XEN)  EDID info not retrieved because no DDC retrieval method detected
  (XEN) Disc information:
  (XEN)  Found 1 MBR signatures
  (XEN)  Found 1 EDD information structures
  (XEN) Xen-e820 RAM map:
  (XEN)   - 0009ec00 (usable)
  (XEN)  000f - 0010 (reserved)
  (XEN)  0010 - cb6cfc00 (usable)
  (XEN)  cb6cfc00 - cb723c00 (ACPI NVS)
  (XEN)  cb723c00 - cb725c00 (ACPI data)
  (XEN)  cb725c00 - cc00 (reserved)
  (XEN)  f800 - fc00 (reserved)
  (XEN)  fec0 - fed00400 (reserved)
  (XEN)  fed2 - feda (reserved)
  (XEN)  fee0 - fef0 (reserved)
  (XEN)  ffb0 - 0001 (reserved)
  (XEN)  0001 - 00013000 (usable)
  (XEN) New Xen image base address: 0xcb00
  (XEN) ACPI: RSDP 000FEC00, 0024 (r2 DELL  )
  (XEN) ACPI: XSDT 000FC7E7, 006C (r1 DELLB11K  15 ASL61)
  (XEN) ACPI: FACP 000FC8D7, 00F4 (r3 DELLB11K  15 ASL61)
  (XEN) ACPI: DSDT FFDC89E4, 47BC (r1   DELLdt_ex 1000 INTL 20050624)
  (XEN) ACPI: FACS CB6CFC00, 0040
  (XEN) ACPI: SSDT FFDCD2C1, 00AC (r1   DELLst_ex 1000 INTL 20050624)
  (XEN) ACPI: APIC 000FC9CB, 0092 (r1 DELLB11K  15 ASL61)
  (XEN) ACPI: BOOT 000FCA5D, 0028 (r1 DELLB11K  15 ASL61)
  (XEN) ACPI: ASF! 000FCA85, 0096 (r32 DELLB11K  15 ASL61)
  (XEN) ACPI: MCFG 000FCB1B, 003E (r1 DELLB11K  15 ASL61)
  (XEN) ACPI: HPET 000FCB59, 0038 (r1 DELLB11K  15 ASL61)
  (XEN) ACPI: TCPA 000FCDB5, 0032 (r1 DELLB11K  15 ASL61)
  (XEN) ACPI: DMAR 000FCDE7, 0068 (r1 DELLB11K  15 ASL61)
  (XEN) System RAM: 4022MB (4118964kB)
  (XEN) Domain heap initialised
  (XEN) IOAPIC[0]: apic_id 8, version 32, address 0xfec0, GSI 0-23
  (XEN) Enabling APIC mode:  Flat.  Using 1 I/O APICs
  (XEN) Using scheduler: SMP Credit Scheduler (credit)
  (XEN) Platform timer is 14.318MHz HPET
  (XEN) Detected 2926.007 MHz processor.
  (XEN) Initing memory sharing.
  (XEN) Intel VT-d iommu 0 supported page sizes: 4kB.
  (XEN) Intel VT-d Snoop Control enabled.
  (XEN) Intel VT-d Dom0 DMA Passthrough not enabled.
  (XEN) Intel VT-d Queued Invalidation enabled.
  (XEN) Intel VT-d Interrupt Remapping not enabled.
  (XEN) Intel VT-d Posted Interrupt not enabled.
  (XEN) Intel VT-d Shared EPT tables not enabled.
  (XEN) :04:00.0: unknown type 4
  (XEN) I/O virtualisation enabled
  (XEN)  - Dom0 mode: Relaxed
  (XEN) Interrupt remapping disabled
  (XEN) ENABLING IO-APIC IRQs
  (XEN)  -> Using new ACK method
  (XEN) Allocated console ring of 16 KiB.
  (XEN) VMX: Supported advanced features:
  (XEN)  - APIC MMIO access virtualisation
  (XEN)  - APIC TPR shadow
  (XEN)  - Extended Page Tables (EPT)
  (XEN)  - Virtual-Processor Identifiers (VPID)
  (XEN)  - Virtual NMI
  (XEN)  - MSR direct-access bitmap
  (XEN) HVM: ASIDs enabled.
  (XEN) HVM: VMX enabled
  (XEN) HVM: Hardware Assisted Paging (HAP) detected
  (XEN) HVM: HAP page sizes: 4kB, 2MB
  (XEN) Brought up 4 CPUs
  (XEN) Dom0 has maximum 600 PIRQs
  (XEN) *** LOADING DOMAIN 0 ***
  (XEN)  Xen  kernel: 64-bit, lsb, compat32
  (XEN)  Dom0 kernel: 64-bit, PAE, lsb, paddr 0x100 -> 0x2b69000
  (XEN) PHYSICAL MEMORY

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

2018-03-05 Thread Ben Kantor

Same bug is occurring on 4.13.0-36-generic as well.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/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]  [] 
process_one_work+0x165/0x480
  Nov 20 12:04:26 g2 kernel: [170689.552417]  [] 
worker_thread+0x4b/0x4c0
  Nov 20 12:04:26 g2 kernel:

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

2018-03-05 Thread 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 1753304

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

Title:
  No Internet when waking from suspend

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Ever since I updated my computer later last week I have had no
  internet access after waking from a suspend. This is all I get as a
  response to these ping commands:

  $ ping google.ca
  PING google.ca (216.58.217.195) 56(84) bytes of data.

  $ ping 8.8.8.8
  PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data.

  localhost works, and I am still able to login to my router over
  wireless. No other computer or phone in my house has any problem with
  the internet, so the problem is specific only to my computer and only
  after the software update.

  the nm-applet is alive and I am able to see the wireless connections
  available to me. If I reconnect to the wifi connection it makes no
  difference.

  If I run "sudo service network-manager restart" it also makes no
  difference.

  The only solution I have found so far to fix the problem is to
  completely restart the computer.

  Any help or advice would be appreciated. If I missed some valuable
  information let me know and I will come back with more info.

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

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

[Kernel-packages] [Bug 1753424] Re: s390/crypto: Fix kernel crash on aes_s390 module remove

2018-03-05 Thread Dimitri John Ledkov

Please also provide the upstream linus' tree commit ID, once merged /
when available.

** Changed in: linux (Ubuntu)
 Assignee: Skipper Bug Screeners (skipper-screen-team) => Canonical Kernel 
(canonical-kernel)

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

Title:
  s390/crypto: Fix kernel crash on aes_s390 module remove

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

Bug description:
  Upstream patch to fix the aes_s390 kernel module remove crash,
  introduced with kernel 4.15 rc1.

  Here is the patch to fix the kernel crash on aes_s390 kernel module removal.
  Please note that this patch is as of now not upstream available but in the 
s390 pipe for the next merge window (and so may be visible upstream with the 
start of the 4.17 development kernels).

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

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

[Kernel-packages] [Bug 1752350] Re: Bionic x86_64 Linux Kernel 4.15 fails to boot on Xen

I built a test kernel with commit 4f277295e54c5b7340e48efea3fc5cc21a2872b7.  
The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1752350

Can you test this kernel and see if it resolves this bug?

Note, to test this kernel, you need to install both the linux-image and
linux-image-extra .deb packages.

Thanks in advance!

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

Title:
  Bionic x86_64 Linux Kernel 4.15 fails to boot on Xen

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

Bug description:
  The Linux Kernel 4.15 from bionic on x86_64 immediately crashes when
  booted as a dom0 under Xen.

  A similar bug was reported by someone else for archlinux
  (https://bugs.archlinux.org/task/57500).

  A patch exists for 4.16. I tried this patch on 4.15.0-10-generic, it
  fixes the problem for me.
  
(https://git.kernel.org/pub/scm/linux/kernel/git/xen/tip.git/patch/?id=4f277295e54c5b7340e48efea3fc5cc21a2872b7).

  Xen output:

  (XEN) Xen version 4.9.0 (Ubuntu 4.9.0-0ubuntu3) (stefan.ba...@canonical.com) 
(gcc (Ubuntu 7.2.0-8ubuntu2) 7.2.0) debug=n  Fri Oct 13 15:58:41 UTC 2017
  (XEN) Bootloader: GRUB 2.02~beta2-36ubuntu3.9
  (XEN) Command line: placeholder com1=115200,8N1 console=com1,vga
  (XEN) Xen image load base address: 0
  (XEN) Video information:
  (XEN)  VGA is text mode 80x25, font 8x16
  (XEN)  VBE/DDC methods: none; EDID transfer time: 0 seconds
  (XEN)  EDID info not retrieved because no DDC retrieval method detected
  (XEN) Disc information:
  (XEN)  Found 1 MBR signatures
  (XEN)  Found 1 EDD information structures
  (XEN) Xen-e820 RAM map:
  (XEN)   - 0009ec00 (usable)
  (XEN)  000f - 0010 (reserved)
  (XEN)  0010 - cb6cfc00 (usable)
  (XEN)  cb6cfc00 - cb723c00 (ACPI NVS)
  (XEN)  cb723c00 - cb725c00 (ACPI data)
  (XEN)  cb725c00 - cc00 (reserved)
  (XEN)  f800 - fc00 (reserved)
  (XEN)  fec0 - fed00400 (reserved)
  (XEN)  fed2 - feda (reserved)
  (XEN)  fee0 - fef0 (reserved)
  (XEN)  ffb0 - 0001 (reserved)
  (XEN)  0001 - 00013000 (usable)
  (XEN) New Xen image base address: 0xcb00
  (XEN) ACPI: RSDP 000FEC00, 0024 (r2 DELL  )
  (XEN) ACPI: XSDT 000FC7E7, 006C (r1 DELLB11K  15 ASL61)
  (XEN) ACPI: FACP 000FC8D7, 00F4 (r3 DELLB11K  15 ASL61)
  (XEN) ACPI: DSDT FFDC89E4, 47BC (r1   DELLdt_ex 1000 INTL 20050624)
  (XEN) ACPI: FACS CB6CFC00, 0040
  (XEN) ACPI: SSDT FFDCD2C1, 00AC (r1   DELLst_ex 1000 INTL 20050624)
  (XEN) ACPI: APIC 000FC9CB, 0092 (r1 DELLB11K  15 ASL61)
  (XEN) ACPI: BOOT 000FCA5D, 0028 (r1 DELLB11K  15 ASL61)
  (XEN) ACPI: ASF! 000FCA85, 0096 (r32 DELLB11K  15 ASL61)
  (XEN) ACPI: MCFG 000FCB1B, 003E (r1 DELLB11K  15 ASL61)
  (XEN) ACPI: HPET 000FCB59, 0038 (r1 DELLB11K  15 ASL61)
  (XEN) ACPI: TCPA 000FCDB5, 0032 (r1 DELLB11K  15 ASL61)
  (XEN) ACPI: DMAR 000FCDE7, 0068 (r1 DELLB11K  15 ASL61)
  (XEN) System RAM: 4022MB (4118964kB)
  (XEN) Domain heap initialised
  (XEN) IOAPIC[0]: apic_id 8, version 32, address 0xfec0, GSI 0-23
  (XEN) Enabling APIC mode:  Flat.  Using 1 I/O APICs
  (XEN) Using scheduler: SMP Credit Scheduler (credit)
  (XEN) Platform timer is 14.318MHz HPET
  (XEN) Detected 2926.007 MHz processor.
  (XEN) Initing memory sharing.
  (XEN) Intel VT-d iommu 0 supported page sizes: 4kB.
  (XEN) Intel VT-d Snoop Control enabled.
  (XEN) Intel VT-d Dom0 DMA Passthrough not enabled.
  (XEN) Intel VT-d Queued Invalidation enabled.
  (XEN) Intel VT-d Interrupt Remapping not enabled.
  (XEN) Intel VT-d Posted Interrupt not enabled.
  (XEN) Intel VT-d Shared EPT tables not enabled.
  (XEN) :04:00.0: unknown type 4
  (XEN) I/O virtualisation enabled
  (XEN)  - Dom0 mode: Relaxed
  (XEN) Interrupt remapping disabled
  (XEN) ENABLING IO-APIC IRQs
  (XEN)  -> Using new ACK method
  (XEN) Allocated console ring of 16 KiB.
  (XEN) VMX: Supported advanced features:
  (XEN)  - APIC MMIO access virtualisation
  (XEN)  - APIC TPR shadow
  (XEN)  - Extended Page Tables (EPT)
  (XEN)  - Virtual-Processor Identifiers (VPID)
  (XEN)  - Virtual NMI
  (XEN)  - MSR direct-access bitmap
  (XEN) HVM: ASIDs enabled.
  (XEN) HVM: VMX enabled
  (XEN) HVM: Hardware Assisted Paging (HAP) detected
  (XEN) HVM: HAP page sizes: 4kB, 2MB
  (XEN) Brought up 4 CPUs
  (XEN) Dom0 has maximum 600 PIRQs
  (XEN) *** LOADING DOMAIN 0 ***
  (XEN)  Xen  kernel: 64-bit, lsb, compat32
  (XEN)  Dom0 kernel: 64-bit, PAE, lsb, paddr 0x100 -> 0x2b69000

[Kernel-packages] [Bug 1753424] Upstream patch to fix the aes_s390 kernel module remove crash

Default Comment by Bridge

** Attachment added: "Upstream patch to fix the aes_s390 kernel module remove 
crash"
   
https://bugs.launchpad.net/bugs/1753424/+attachment/5069718/+files/s390-crypto-Fix-kernel-crash-on-aes_s390-module-remo.patch

** Changed in: ubuntu
 Assignee: (unassigned) => Skipper Bug Screeners (skipper-screen-team)

** Package changed: ubuntu => linux (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/1753424

Title:
  s390/crypto: Fix kernel crash on aes_s390 module remove

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

Bug description:
  Upstream patch to fix the aes_s390 kernel module remove crash,
  introduced with kernel 4.15 rc1.

  Here is the patch to fix the kernel crash on aes_s390 kernel module removal.
  Please note that this patch is as of now not upstream available but in the 
s390 pipe for the next merge window (and so may be visible upstream with the 
start of the 4.17 development kernels).

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

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

[Kernel-packages] [Bug 1745349] Re: Hard lockup during boot with linux-image-4.4.0-112-generic

2018-03-05 Thread Mike Turner

I'm afraid that I am not an expert at Ubuntu. I think that I have
installed your test kernel correctly, but I don't know how to prove it.
I used sudo dpkg -i *.deb .

If I have installed it correctly, then it doesn't cure the problem. It
runs fine with noibpb, but fails in the same way if I try to run without
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/1745349

Title:
  Hard lockup during boot with linux-image-4.4.0-112-generic

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

Bug description:
  Systems on ASUS H110M-C Boards don't boot here with Kernel 4.4.0-112
  instead they show

  NMI watchdog: Watchdog detected hard lockup on cpu 0
  NMI watchdog: Watchdog detected hard lockup on cpu 1
  NMI watchdog: Watchdog detected hard lockup on cpu 3
  NMI watchdog: Watchdog detected hard lockup on cpu 2

  I cannot provide any logs of course.

  Booting with 4.4.0-109 works.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-112-generic 4.4.0-112.135
  ProcVersionSignature: Ubuntu 4.4.0-109.132-generic 4.4.98
  Uname: Linux 4.4.0-109-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  lr3200 2013 F pulseaudio
  Date: Thu Jan 25 11:38:55 2018
  HibernationDevice: RESUME=UUID=8e35131d-6d40-4f4f-a3db-c7336e72cbce
  IwConfig:
   lono wireless extensions.
   
   enp5s0no wireless extensions.
   
   enp3s0no wireless extensions.
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 046d:c077 Logitech, Inc. M105 Optical Mouse
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: System manufacturer System Product Name
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-109-generic 
root=UUID=4dc5bb0a-ab7c-48fa-ac23-bcdf23755d93 ro
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-109-generic N/A
   linux-backports-modules-4.4.0-109-generic  N/A
   linux-firmware 1.157.15
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/12/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3601
  dmi.board.asset.tag: Default string
  dmi.board.name: H110M-C
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3601:bd12/12/2017:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnH110M-C:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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

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

[Kernel-packages] [Bug 1753424] Re: s390/crypto: Fix kernel crash on aes_s390 module remove

2018-03-05 Thread Thadeu Lima de Souza Cascardo

** Also affects: linux (Ubuntu Bionic)
   Importance: Undecided
 Assignee: Canonical Kernel (canonical-kernel)
   Status: New

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

Title:
  s390/crypto: Fix kernel crash on aes_s390 module remove

Status in Ubuntu on IBM z Systems:
  Incomplete
Status in linux package in Ubuntu:
  New
Status in linux source package in Bionic:
  New

Bug description:
  Upstream patch to fix the aes_s390 kernel module remove crash,
  introduced with kernel 4.15 rc1.

  Here is the patch to fix the kernel crash on aes_s390 kernel module removal.
  Please note that this patch is as of now not upstream available but in the 
s390 pipe for the next merge window (and so may be visible upstream with the 
start of the 4.17 development kernels).

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

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

[Kernel-packages] [Bug 1752550] Re: Failed to create KVM on Trusty ppc64le, no supported architecture for os type 'hvm'

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

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

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

Title:
  Failed to create KVM on Trusty ppc64le, no supported architecture for
  os type 'hvm'

Status in linux package in Ubuntu:
  Triaged

Bug description:
  Trying to use uvtool to create a KVM instance with Trusty kernel on a
  ppc64le system will fail with:

  uvt-kvm: error: libvirt: internal error: no supported architecture for
  os type 'hvm'

  Command:
  uvt-kvm create kvm-test release=xenial arch=ppc64el

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-142-generic 3.13.0-142.191
  ProcVersionSignature: Ubuntu 3.13.0-142.191-generic 3.13.11-ckt39
  Uname: Linux 3.13.0-142-generic ppc64le
  AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 
2: ls: cannot access /dev/snd/: No such file or directory
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.14.1-0ubuntu3.27
  Architecture: ppc64el
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  CurrentDmesg:

  Date: Thu Mar  1 11:09:14 2018
  Lsusb:
   Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  PciMultimedia:

  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB:

  ProcKernelCmdLine: root=UUID=36575f9a-a03d-4d21-874c-db9886a8ffbd ro 
console=hvc0
  ProcLoadAvg: 1.18 0.67 0.28 1/1074 8837
  ProcLocks:
   1: POSIX  ADVISORY  WRITE 6459 00:11:43064 0 0
   2: FLOCK  ADVISORY  WRITE 2334 00:11:27831 0 EOF
   3: POSIX  ADVISORY  WRITE 2264 00:11:35027 0 EOF
   4: POSIX  ADVISORY  WRITE 2387 00:11:35925 0 EOF
  ProcSwaps:
   Filename TypeSizeUsedPriority
   /swap.img   file 8388544 0   -1
  ProcVersion: Linux version 3.13.0-142-generic (buildd@bos02-ppc64el-009) (gcc 
version 4.8.4 (Ubuntu 4.8.4-2ubuntu1~14.04.3) ) #191-Ubuntu SMP Fri Feb 2 
12:12:31 UTC 2018
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-142-generic N/A
   linux-backports-modules-3.13.0-142-generic  N/A
   linux-firmware  1.127.24
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  cpu_cores: Number of cores present = 20
  cpu_coreson: Number of cores online = 20
  cpu_freq:
   min: 3.694 GHz (cpu 124)
   max: 3.694 GHz (cpu 1)
   avg: 3.694 GHz
  cpu_runmode:
   Could not retrieve current diagnostics mode,
   No firmware implementation of function
  cpu_smt: SMT=8

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

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

[Kernel-packages] [Bug 1752182] Re: [Feature]Update Ubuntu 18.04 lpfc FC driver with 32/64GB HBA support and bug fixes

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

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

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

** Also affects: linux (Ubuntu Bionic)
   Importance: Wishlist
   Status: Triaged

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

Title:
  [Feature]Update Ubuntu 18.04 lpfc FC driver with 32/64GB HBA support
  and bug fixes

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

Bug description:
  This is a placeholder bugzilla that will list all commit ids needed
  for Broadcom Emulex FC 32/64GB new hardware support and all bug fixes
  available upstream.

  Note the lpfc FC driver commit list will include NVMe patches for ease
  of maintainability vs. upstream but we ask that you not build NVMe FC
  since we do not intend to support NVMe FC on 18.04 (4.15 kernel) at
  this time due to all of the unmet upper layer dependencies.

  Laurie Barry

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

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

[Kernel-packages] [Bug 1752574] Re: Thunderbolt NULL pointer dereference in linux 4.15

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

Title:
  Thunderbolt NULL pointer dereference in linux 4.15

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  [0.994565] thunderbolt :09:00.0: enabling device ( -> 0002)
  [0.994957] thunderbolt :09:00.0: NHI initialized, starting thunderbolt
  [0.994961] thunderbolt :09:00.0: allocating TX ring 0 of size 10
  [0.994983] thunderbolt :09:00.0: allocating RX ring 0 of size 10
  [0.994999] thunderbolt :09:00.0: control channel created
  [0.994999] thunderbolt :09:00.0: control channel starting...
  [0.995000] thunderbolt :09:00.0: starting TX ring 0
  [0.995018] thunderbolt :09:00.0: enabling interrupt at register 
0x38200 bit 0 (0x0 -> 0x1)
  [0.995018] thunderbolt :09:00.0: starting RX ring 0
  [0.995033] thunderbolt :09:00.0: enabling interrupt at register 
0x38200 bit 12 (0x1 -> 0x1001)
  [0.995046] thunderbolt :09:00.0: starting ICM firmware
  [0.995060] BUG: unable to handle kernel NULL pointer dereference at 
0980
  [0.995065] IP: pci_write_config_dword+0x5/0x30
  [0.995066] PGD 0 P4D 0 
  [0.995068] Oops:  [#1] SMP PTI
  [0.995069] Modules linked in: thunderbolt(+) ahci(+) ipmi_devintf libahci 
ipmi_msghandler video fjes(-)
  [0.995074] CPU: 6 PID: 214 Comm: systemd-udevd Not tainted 
4.15.0-10-generic #11-Ubuntu
  [0.995075] Hardware name: Gigabyte Technology Co., Ltd. Z170X-UD5 
TH/Z170X-UD5 TH-CF, BIOS F22d 12/01/2017
  [0.995077] RIP: 0010:pci_write_config_dword+0x5/0x30
  [0.995078] RSP: 0018:9e58839779e0 EFLAGS: 00010296
  [0.995079] RAX: 4126 RBX:  RCX: 
0050
  [0.995080] RDX: 0200 RSI: 0034 RDI: 

  [0.995081] RBP: 9e5883977a18 R08: 0200 R09: 
0330
  [0.995082] R10: 2000 R11:  R12: 

  [0.995083] R13: 0050 R14: 92354e146f28 R15: 

  [0.995084] FS:  7f86f2204440() GS:92357ed8() 
knlGS:
  [0.995085] CS:  0010 DS:  ES:  CR0: 80050033
  [0.995086] CR2: 0980 CR3: 00080d1ce004 CR4: 
003606e0
  [0.995087] DR0:  DR1:  DR2: 

  [0.995088] DR3:  DR6: fffe0ff0 DR7: 
0400
  [0.995089] Call Trace:
  [0.995094]  ? pcie2cio_write+0x40/0x80 [thunderbolt]
  [0.995098]  icm_driver_ready+0x178/0x270 [thunderbolt]
  [0.995101]  ? tb_ctl_start+0x50/0x90 [thunderbolt]
  [0.995105]  tb_domain_add+0x79/0x100 [thunderbolt]
  [0.995108]  nhi_probe+0x186/0x300 [thunderbolt]
  [0.995110]  local_pci_probe+0x47/0xa0
  [0.995111]  pci_device_probe+0x145/0x1b0
  [0.995114]  driver_probe_device+0x31e/0x490
  [0.995116]  __driver_attach+0xa7/0xf0
  [0.995118]  ? driver_probe_device+0x490/0x490
  [0.995119]  bus_for_each_dev+0x70/0xc0
  [0.995121]  driver_attach+0x1e/0x20
  [0.995123]  bus_add_driver+0x1c7/0x270
  [0.995124]  ? 0xc03a9000
  [0.995125]  driver_register+0x60/0xe0
  [0.995126]  ? 0xc03a9000
  [0.995128]  __pci_register_driver+0x5a/0x60
  [0.995131]  nhi_init+0x2d/0x1000 [thunderbolt]
  [0.995133]  do_one_initcall+0x52/0x1a0
  [0.995135]  ? _cond_resched+0x19/0x40
  [0.995138]  ? kmem_cache_alloc_trace+0xa6/0x1b0
  [0.995140]  ? do_init_module+0x27/0x209
  [0.995141]  do_init_module+0x5f/0x209
  [0.995143]  load_module+0x191e/0x1f10
  [0.995146]  ? ima_post_read_file+0x96/0xa0
  [0.995148]  SYSC_finit_module+0xfc/0x120
  [0.995149]  ? SYSC_finit_module+0xfc/0x120
  [0.995151]  SyS_finit_module+0xe/0x10
  [0.995152]  do_syscall_64+0x76/0x130
  [0.995154]  entry_SYSCALL_64_after_hwframe+0x21/0x86
  [0.995155] RIP: 0033:0x7f86f1af3a49
  [0.995156] RSP: 002b:7ffdedfa4478 EFLAGS: 0246 ORIG_RAX: 
0139
  [0.995157] RAX: ffda RBX: 559d3ffde790 RCX: 
7f86f1af3a49
  [0.995158] RDX:  RSI: 7f86f17df0e5 RDI: 
0005
  [0.995159] RBP: 7f86f17df0e5 R08:  R09: 
7ffdedfa4590
  [0.995160] R10: 0005 R11: 0246 R12: 

  [0.995161] R13: 559d3ffedbf0 R14: 0002 R15: 
559d3ffde790
  [0.995162] Code: 87 c0 00 00 00 b9 04 00 00 00 48 89 e5 48 8b 40 20 e8 d0 
45 72 00 5d c3 b8 87 00 00 00 c3 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 <48> 8b 
8f 80 09 00 00 83 e1 01 75 0b 55 48 89 e5 e8 a6

[Kernel-packages] [Bug 1752621] Re: BUG: unable to handle kernel paging request at ffffded5330000a0

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

** This bug has been marked a duplicate of bug 1734327
   Kernel panic on a nfsroot 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/1752621

Title:
  BUG: unable to handle kernel paging request at ded533a0

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  [  155.111268] BUG: unable to handle kernel paging request at ded533a0
  [  155.111335] IP: kfree+0x53/0x160
  [  155.111357] PGD 0 
  [  155.111358] P4D 0 

  [  155.111401] Oops:  [#1] SMP PTI
  [  155.111424] Modules linked in: gpio_ich intel_rapl x86_pkg_temp_thermal 
intel_powerclamp coretemp kvm_intel snd_hda_codec_hdmi kvm 
snd_hda_codec_realtek snd_hda_codec_generic snd_hda_intel irqbypass 
snd_hda_codec snd_hda_core crct10dif_pclmul crc32_pclmul ghash_clmulni_intel 
pcbc aesni_intel snd_hwdep aes_x86_64 crypto_simd snd_pcm snd_seq_midi 
snd_seq_midi_event snd_rawmidi joydev input_leds glue_helper snd_seq 
snd_seq_device cryptd snd_timer intel_cstate intel_rapl_perf mei_me shpchp snd 
mei soundcore lpc_ich mac_hid serio_raw parport_pc ppdev lp parport ip_tables 
x_tables autofs4 hid_generic usbhid hid i915 video i2c_algo_bit drm_kms_helper 
syscopyarea sysfillrect sysimgblt ahci fb_sys_fops r8169 libahci drm mii
  [  155.111809] CPU: 0 PID: 1587 Comm: postgres Not tainted 4.13.0-36-generic 
#40-Ubuntu
  [  155.111853] Hardware name: Gigabyte Technology Co., Ltd. 
H67A-USB3-B3/H67A-USB3-B3, BIOS F7 03/27/2012
  [  155.111906] task: 8e971b4845c0 task.stack: 9c1bc2e7c000
  [  155.111942] RIP: 0010:kfree+0x53/0x160
  [  155.111966] RSP: 0018:9c1bc2e7fce8 EFLAGS: 00010282
  [  155.111998] RAX:  RBX: 00102aa3 RCX: 
0003
  [  155.112039] RDX: 2d8460201cf0 RSI: 00010080 RDI: 
716c4000
  [  155.112080] RBP: 9c1bc2e7fd00 R08: 00025d80 R09: 
bafc6a19
  [  155.112121] R10: ded53380 R11:  R12: 
8e974abe7800
  [  155.112162] R13: baba74d4 R14:  R15: 
8e9714f4d3c0
  [  155.112204] FS:  () GS:8e975fa0() 
knlGS:
  [  155.112250] CS:  0010 DS:  ES:  CR0: 80050033
  [  155.112285] CR2: ded533a0 CR3: 00022c20a001 CR4: 
000606f0
  [  155.112326] Call Trace:
  [  155.112349]  security_sk_free+0x44/0x60
  [  155.112377]  __sk_destruct+0x10b/0x190
  [  155.112403]  sk_destruct+0x20/0x30
  [  155.112427]  __sk_free+0x82/0xa0
  [  155.112451]  sk_free+0x19/0x20
  [  155.112472]  tcp_close+0x238/0x3f0
  [  155.112498]  inet_release+0x42/0x70
  [  155.112522]  sock_release+0x25/0x80
  [  155.112546]  sock_close+0x12/0x20
  [  155.114960]  __fput+0xea/0x230
  [  155.117332]  fput+0xe/0x10
  [  155.119604]  task_work_run+0x7c/0xa0
  [  155.121861]  do_exit+0x2d2/0xae0
  [  155.124100]  ? entry_SYSCALL_64_after_hwframe+0xd4/0x139
  [  155.126330]  ? entry_SYSCALL_64_after_hwframe+0xc6/0x139
  [  155.128524]  ? entry_SYSCALL_64_after_hwframe+0xbf/0x139
  [  155.130674]  ? entry_SYSCALL_64_after_hwframe+0xb8/0x139
  [  155.132757]  ? entry_SYSCALL_64_after_hwframe+0xb1/0x139
  [  155.134769]  do_group_exit+0x43/0xb0
  [  155.136307]  SyS_exit_group+0x14/0x20
  [  155.138219]  entry_SYSCALL_64_fastpath+0x24/0xab
  [  155.140110] RIP: 0033:0x7fe7b4851fd8
  [  155.141984] RSP: 002b:7ffe7f1d1e88 EFLAGS: 0246 ORIG_RAX: 
00e7
  [  155.143882] RAX: ffda RBX: 563529f04030 RCX: 
7fe7b4851fd8
  [  155.145590] RDX:  RSI: 003c RDI: 

  [  155.147316] RBP: 7ffe7f1d1e80 R08: 00e7 R09: 
fef8
  [  155.148956] R10: 7fe7acf95148 R11: 0246 R12: 
7fe7acf94d90
  [  155.150230] R13: 0036 R14:  R15: 
7ffe7f1d1c10
  [  155.151492] Code: 00 80 49 01 da 0f 82 1f 01 00 00 48 c7 c7 00 00 00 80 48 
2b 3d 4f b2 01 01 49 01 fa 49 c1 ea 0c 49 c1 e2 06 4c 03 15 2d b2 01 01 <49> 8b 
42 20 48 8d 50 ff a8 01 4c 0f 45 d2 49 8b 52 20 48 8d 42 
  [  155.152892] RIP: kfree+0x53/0x160 RSP: 9c1bc2e7fce8
  [  155.154283] CR2: ded533a0
  [  155.167949] ---[ end trace 28ca6dd18121abd3 ]---

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-36-generic 4.13.0-36.40
  ProcVersionSignature: Ubuntu 4.13.0-36.40-generic 4.13.13
  Uname: Linux 4.13.0-36-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  user   1058 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Mar  1 20:51:56 2018
  HibernationDevice: RESUME=UUID=dcaa0aaf-ec9b-4eec-962b-498d547772f5
  InstallationDate: Installed on 2018-02-23 (5 days ago)
  InstallationMedia: Ubuntu 17.10

[Kernel-packages] [Bug 1752376] Re: Dell Vostro 5568 - Sound device disappears after connecting headphones

Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.16 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.16-rc4

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

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

Title:
  Dell Vostro 5568 - Sound device disappears after connecting headphones

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  With all kernel versions so far tested including mainline v4.15.4 the
  audio device permanently disappears even after a cold reboot once the
  headphones have been plugged/unplugged.

  Looks to be a firmware issue; latest firmware has been installed but
  issue remains.

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

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

[Kernel-packages] [Bug 1750021] Re: fails to dump with latest kpti fixes

2018-03-05 Thread Thadeu Lima de Souza Cascardo

Xenial does not have 83e3c48729d9ebb7af5a31a504f3fd6aff0348c4. Though,
linux-hwe 4.13 has been shipped for Xenial. So, on the kernel side,
there is nothing to fix on our 4.4 kernels, but on the makedumpfile
side, that still needs to be fixed if we want to have some of those
kernels dumpable.

** Description changed:

  When commit 83e3c48729d9ebb7af5a31a504f3fd6aff0348c4 ("mm/sparsemem:
  Allocate mem_section at runtime for CONFIG_SPARSEMEM_EXTREME=y") was
  backported, it broke the exporting of mem_section on vmcoreinfo.
  
  makedumpfile will fail to dump in that case. Backporting a kernel fix
  will make it work again, but that means that some kernel versions won't
  be dumpable. A solution for makedumpfile should be done as well.
  
  Cascardo.
+ 
+ break-fix: 83e3c48729d9ebb7af5a31a504f3fd6aff0348c4
+ a0b1280368d1e91ab72f849ef095b4f07a39bbf1

** Tags removed: kernel-da-key
** Tags added: kernel-bug-break-fix

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

** Changed in: linux (Ubuntu Xenial)
   Status: New => 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/1750021

Title:
  fails to dump with latest kpti fixes

Status in linux package in Ubuntu:
  Fix Released
Status in makedumpfile package in Ubuntu:
  In Progress
Status in linux source package in Xenial:
  Invalid
Status in makedumpfile source package in Xenial:
  New
Status in linux source package in Artful:
  New
Status in makedumpfile source package in Artful:
  New
Status in linux source package in Bionic:
  Fix Released
Status in makedumpfile source package in Bionic:
  In Progress

Bug description:
  When commit 83e3c48729d9ebb7af5a31a504f3fd6aff0348c4 ("mm/sparsemem:
  Allocate mem_section at runtime for CONFIG_SPARSEMEM_EXTREME=y") was
  backported, it broke the exporting of mem_section on vmcoreinfo.

  makedumpfile will fail to dump in that case. Backporting a kernel fix
  will make it work again, but that means that some kernel versions
  won't be dumpable. A solution for makedumpfile should be done as well.

  Cascardo.

  break-fix: 83e3c48729d9ebb7af5a31a504f3fd6aff0348c4
  a0b1280368d1e91ab72f849ef095b4f07a39bbf1

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

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

[Kernel-packages] [Bug 1753428] [NEW] nobp enable msg during boot

2018-03-05 Thread Launchpad Bug Tracker

You have been subscribed to a public bug:

Description will follow

** Affects: linux (Ubuntu)
 Importance: Undecided
 Assignee: Skipper Bug Screeners (skipper-screen-team)
 Status: New


** Tags: architecture-s39064 bugnameltc-165232 severity-high 
targetmilestone-inin1604
-- 
nobp enable msg during boot
https://bugs.launchpad.net/bugs/1753428
You received this bug notification because you are a member of Kernel Packages, 
which is subscribed to linux in Ubuntu.

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

[Kernel-packages] [Bug 1752748] Re: nouveau module can't be loaded

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.16 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.16-rc4


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

Title:
  nouveau module can't be loaded

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Module nouveou can't be loaded. I get the following error message when
  I try to load it manually:

  # modprobe nouveau
  modprobe: ERROR: ../libkmod/libkmod-module.c:832 kmod_module_insert_module() 
could not find module by name='off'
  modprobe: ERROR: could not insert 'off': Unknown symbol in module, or unknown 
parameter (see dmesg)
  modprobe: ERROR: ../libkmod/libkmod-module.c:832 kmod_module_insert_module() 
could not find module by name='off'
  modprobe: ERROR: could not insert 'off': Unknown symbol in module, or unknown 
parameter (see dmesg)
  modprobe: ERROR: ../libkmod/libkmod-module.c:832 kmod_module_insert_module() 
could not find module by name='off'
  modprobe: ERROR: could not insert 'off': Unknown symbol in module, or unknown 
parameter (see dmesg)
  modprobe: ERROR: ../libkmod/libkmod-module.c:832 kmod_module_insert_module() 
could not find module by name='off'
  modprobe: ERROR: could not insert 'off': Unknown symbol in module, or unknown 
parameter (see dmesg)
  modprobe: ERROR: ../libkmod/libkmod-module.c:832 kmod_module_insert_module() 
could not find module by name='off'
  modprobe: ERROR: could not insert 'off': Unknown symbol in module, or unknown 
parameter (see dmesg)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-10-lowlatency 4.15.0-10.11
  ProcVersionSignature: Ubuntu 4.15.0-10.11-lowlatency 4.15.3
  Uname: Linux 4.15.0-10-lowlatency x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  lvella 1453 F pulseaudio
   /dev/snd/controlC0:  lvella 1453 F pulseaudio
   /dev/snd/controlC1:  lvella 1453 F pulseaudio
  CurrentDesktop: XFCE
  Date: Thu Mar  1 20:37:06 2018
  HibernationDevice: RESUME=UUID=3f064780-2aeb-44b4-a8a3-21e590bd1b8f
  InstallationDate: Installed on 2016-06-02 (637 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  IwConfig:
   lono wireless extensions.
   
   enp5s0no wireless extensions.
  MachineType: System manufacturer System Product Name
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-10-lowlatency.efi.signed 
root=UUID=f127c524-7b47-4ff1-b1d6-620ed6f14a29 ro noprompt persistent quiet 
splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-10-lowlatency N/A
   linux-backports-modules-4.15.0-10-lowlatency  N/A
   linux-firmware1.171
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: Upgraded to bionic on 2018-02-28 (1 days ago)
  dmi.bios.date: 04/20/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3701
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: P8H67-M PRO
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3701:bd04/20/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8H67-MPRO:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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

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

[Kernel-packages] [Bug 1752672] Re: CAPI Flash (cxlflash) update

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

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

** Tags added: kernel-da-key

** Also affects: linux (Ubuntu Bionic)
   Importance: Medium
 Assignee: Ubuntu on IBM Power Systems Bug Triage (ubuntu-power-triage)
   Status: Triaged

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

Title:
  CAPI Flash (cxlflash) update

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

Bug description:
  This is a feature for capi flash (cxlflash) inside the kernel.

  We have upstreamed the below 38 patches but they are not in the
  maintainers tree yet. I anticipate them to be available by Friday this
  week. I dont want to miss the boat for 18.04 feature code cutoff. Can
  you please suggest if I should submit these patches as SAUCE patches
  or can it be pulled from mainstream once maintainer pulls it in ?

  8d34234b7e44caa489bb7e684ead1f13b74faf72 cxlflash: Preserve number of 
interrupts for master contexts
  8f20948fde0a06a283b39c3646c8060b62319875 cxlflash: Avoid clobbering context 
control register value
  44569c367471bd57916798a701ad1c7250ec93fb cxlflash: Add argument identifier 
names
  9e63cdb74178a02fa76c3896c2e38479148e60bf cxlflash: Introduce OCXL backend
  0aa60ffb7ca4ce3f5cb33231d9358ab9f0ae9ec4 cxlflash: Hardware AFU for OCXL
  f9e6817464036867a6994732c3b8b873b6fdc530 cxlflash: Read host function 
configuration
  f1718592638ef1e3486ded07ba9aebf784b03db3 cxlflash: Setup function acTag range
  77ece8688ed48e693bbdfef7b856ed146dac5838 cxlflash: Read host AFU configuration
  6491b3338076c8a71f70c326aeacf7ecde139124 cxlflash: Setup AFU acTag range
  90fbea09364d3a32b6b2b0fbbd56c4fbaabe5400 cxlflash: Setup AFU PASID
  16e8be014d2efa0f7e713d5e7cfae9348eaab6fd cxlflash: Adapter context support 
for OCXL
  2d431a892b91f9f004a8b6413d990c55dac6ac16 cxlflash: Use IDR to manage adapter 
contexts
  d0dd47f71da4a9f37cfd2eced36f85c2751fcdf5 cxlflash: Support adapter file 
descriptors for OCXL
  1719110f42503bcac6962daf4492cec3c16c325f cxlflash: Support adapter context 
discovery
  e9ff19884da98139427e23c8ce3bed7614427fed cxlflash: Support image reload 
policy modification
  5706f2a40306b2fe5ffae6fa1eacc81afed3fa11 cxlflash: MMIO map the AFU
  99b7d36979c67708851f8058c9fb6e412d32577b cxlflash: Support starting an 
adapter context
  d8e72cf527fed71641dd011dff13fbd1e5fad2da cxlflash: Support process specific 
mappings
  8cc796025b082c13c1ec3db620e9f23f6082726a cxlflash: Support AFU state toggling
  9e0d9716935bdf9e2c24d3c27ae8be1756eff46e cxlflash: Support reading adapter 
VPD data
  b37e0fdd868e47221e706be4d51c66e5e9224f20 cxlflash: Setup function OCXL link
  099858c80b956752693e0d3bb8f01618a11d48dc cxlflash: Setup OCXL transaction 
layer
  5b1a1f3d49ee4b41778e41bf8147febc885df381 cxlflash: Support process element 
lifecycle
  0e3e9fbfada4506620610497cdc6ce0a0b3cdff2 cxlflash: Support AFU interrupt 
management
  ff7388a91f3739c5420b16f20d74644f5da9b03a cxlflash: Support AFU interrupt 
mapping and registration
  cfa71c77fd9e440b1d8f105151eaf30aff5f3241 cxlflash: Support starting user 
contexts
  270a401d0901eeb736b1da4fd728006ae4d40145 cxlflash: Support adapter context 
polling
  302ce17cba275e295803a2a2aad83debfd02cf5d cxlflash: Support adapter context 
reading
  cc8640bac30541ddc453834d5956ced223ed0020 cxlflash: Support adapter context 
mmap and release
  a071c05a8cab915a3a7d11a87b06da00bc5bc7d5 cxlflash: Support file descriptor 
mapping
  eb01b23138c73967c17c04e79ab4c5df4649984e cxlflash: Introduce object handle fop
  c6a2e3b15bd5a6f85472eac54fede0cffcd6d4e5 cxlflash: Setup LISNs for user 
contexts
  bbfdb7e4d852d213b3b474185918a94aabecad7f cxlflash: Setup LISNs for master 
contexts
  e8d361505cef408ec3afb5f0cf1e4c3fd7f6150b cxlflash: Update synchronous 
interrupt status bits
  dc8e5211cbd6457f618bc49df7e769895b6996bc cxlflash: Introduce OCXL context 
state machine
  9c5567f5e9c92a9f94f7790b2dd905235bc9842c cxlflash: Register for translation 
errors
  96cacd8347f27d258bae75d796cc1f523724a37a cxlflash: Support AFU reset
  966a6e64ddd9624999d895fffab190c7d2f96c85 cxlflash: Enable OCXL operations

  <<< The above is from my local git tree but it has been already sent
  to linux-scsi mailing list >>>

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

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

[Kernel-packages] [Bug 1752772] Re: r8169 ethernet card don't work after returning from suspension

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.16 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.16-rc4


** 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-firmware in Ubuntu.
https://bugs.launchpad.net/bugs/1752772

Title:
  r8169 ethernet card don't work after returning from suspension

Status in linux package in Ubuntu:
  Incomplete
Status in linux-firmware package in Ubuntu:
  New

Bug description:
  I have noticed that the network stopped working on my desktop after
  I've suspended the system and woke it up. On dmesg there are messages
  like:

  [  150.877998] IPv6: ADDRCONF(NETDEV_UP): enp1s0: link is not ready
  [  150.944101] do_IRQ: 3.37 No irq handler for vector
  [  150.944105] r8169 :01:00.0 enp1s0: link down
  [  150.944180] IPv6: ADDRCONF(NETDEV_UP): enp1s0: link is not ready

  When using Xenial (from a different install), this problem is not
  happening. This is happening on Bionic.

  There are only two ways to restore connectivity: 
  1) Reboot the system;
  2) Remove the r8169 module and reinsert it with modprobe.

  The motherboard is a AsRock H55M-LE and the Ethernet controller is:

  01:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd.
  RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 03)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-firmware 1.172
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: LXDE
  Date: Fri Mar  2 00:21:57 2018
  Dependencies:
   
  InstallationDate: Installed on 2018-02-26 (3 days ago)
  InstallationMedia: Lubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180226)
  PackageArchitecture: all
  SourcePackage: linux-firmware
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k4.15.0-10-generic.
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 0: MID [HDA Intel MID], device 0: VT1818S Analog [VT1818S Analog]
 Subdevices: 1/1
 Subdevice #0: subdevice #0
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  usuario1153 F pulseaudio
   /dev/snd/controlC1:  usuario1153 F pulseaudio
  Card0.Amixer.info:
   Card hw:0 'MID'/'HDA Intel MID at 0xfbdf8000 irq 26'
 Mixer name : 'VIA VT1818S'
 Components : 'HDA:11060440,18492818,0010'
 Controls  : 40
 Simple ctrls  : 17
  Card1.Amixer.info:
   Card hw:1 'HDMI'/'HDA ATI HDMI at 0xfbffc000 irq 27'
 Mixer name : 'ATI R6xx HDMI'
 Components : 'HDA:1002aa01,00aa0100,00100200'
 Controls  : 7
 Simple ctrls  : 1
  Card1.Amixer.values:
   Simple mixer control 'IEC958',0
 Capabilities: pswitch pswitch-joined
 Playback channels: Mono
 Mono: Playback [on]
  CurrentDesktop: LXDE
  Dependencies:
   
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=edd83175-c707-4b31-90d2-ce2f5cebc73f
  InstallationDate: Installed on 2018-02-26 (3 days ago)
  InstallationMedia: Lubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180226)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  Package: linux-firmware 1.172
  PackageArchitecture: all
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz 
root=UUID=0c4fc517-b7a0-49b0-bfcb-0485dfe6413b ro quiet
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-10-generic N/A
   linux-backports-modules-4.15.0-10-generic  N/A
   linux-firmware 1.172
  RfKill:
   
  Tags:  bionic
  Uname: Linux 4.15.0-10-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirt lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/20/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.80
  dmi.board.name: H55M-LE
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias:

[Kernel-packages] [Bug 1752828] Re: nfp: fix disabling on hw-tc-offload in flower

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

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

** Also affects: linux (Ubuntu Bionic)
   Importance: Medium
   Status: Triaged

** Tags added: bionic

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

Title:
  nfp: fix disabling on hw-tc-offload in flower

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

Bug description:
  This is a backport request from Netronome for Ubuntu 18.04 LTS

  This patchset corrects the following behaviour:
  1. Add TC filter to hardware while hw-tc-offload is on
  2. Switch hw-tc-offload to off using ethtool
  3. Filters added to hardware in step 1 are still active but can no longer be 
removed. 

  The upstream solution to this problem is to prohibit switching hw-tc-
  offload to off when filters are present in hardware.

  The upstream commits, accepted for v4.16, are:
  d692403e5cf8 (“nfp: forbid disabling hw-tc-offload on representors while 
offload active”)
  0b9de4ca853b (“nfp: don't advertise hw-tc-offload on non-port netdevs”)
  e3ac6c0737e2 (“nfp: bpf: require ETH table”)

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

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

[Kernel-packages] [Bug 1752742] Re: Kernel deadlock when using cachefiles.

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.16 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.16-rc4


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

Title:
  Kernel deadlock when using cachefiles.

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Was using both a cifs share and a nfs share at the moment of the
  crash, both network filesystems get mounted by automount, seems that
  the bug happened at the cifs automatic umount. Machine froze and
  stopped responding pings from the network, not even sysrq keys worked,
  needed a hard power off. Kernel panic (at least what made to syslog)
  follows:

  Mar  1 19:34:04 xps kernel: [ 5497.617469] [ cut here 
]
  Mar  1 19:34:04 xps kernel: [ 5497.617472] kernel BUG at 
/build/linux-fQ94TU/linux-4.4.0/fs/fscache/cookie.c:639!
  Mar  1 19:34:04 xps kernel: [ 5497.617474] invalid opcode:  [#1] SMP 
  Mar  1 19:34:04 xps kernel: [ 5497.617475] Modules linked in: rpcsec_gss_krb5 
nfsv4 nfs drbg ansi_cprng md4 nls_utf8 cifs ccm bnep pci_stub vboxpci(OE) 
vboxnetadp(OE) vboxnetflt(OE) vboxdrv(
  OE) dm_cache_smq dm_cache dm_persistent_data dm_bio_prison zram dm_bufio 
lz4_compress libcrc32c uvcvideo videobuf2_vmalloc videobuf2_memops 
videobuf2_v4l2 ath3k videobuf2_core btusb v4l2_com
  mon btrtl videodev btbcm btintel snd_usb_audio joydev media input_leds 
bluetooth snd_usbmidi_lib snd_hda_codec_hdmi intel_rapl x86_pkg_temp_thermal 
intel_powerclamp coretemp kvm_intel snd_hd
  a_codec_realtek snd_hda_codec_generic kvm dcdbas irqbypass snd_hda_intel arc4 
crct10dif_pclmul crc32_pclmul snd_hda_codec ghash_clmulni_intel ath9k 
aesni_intel snd_hda_core aes_x86_64 lrw sn
  d_hwdep gf128mul glue_helper snd_pcm ath9k_common ablk_helper ath9k_hw cryptd 
snd_seq_midi ath snd_seq_midi_event snd_rawmidi nvidia_uvm(POE) mac80211 
snd_seq snd_seq_device snd_timer cfg802
  11 serio_raw snd mei_me mei soundcore lpc_ich shpchp mac_hid binfmt_misc 
cachefiles nfsd fscache auth_rpcgss parport_pc nfs_acl lockd ppdev lp grace 
sunrpc parport autofs4 btrfs xor uas usb_
  storage raid6_pq hid_generic usbhid hid nvidia_drm(POE) nvidia_modeset(POE) 
nvidia(POE) drm_kms_helper syscopyarea sysfillrect sysimgblt psmouse 
fb_sys_fops ahci r8169 drm libahci mii video 
  fjes
  Mar  1 19:34:04 xps kernel: [ 5497.617515] CPU: 2 PID: 20454 Comm: umount 
Tainted: P   OE   4.4.0-116-generic #140-Ubuntu
  Mar  1 19:34:04 xps kernel: [ 5497.617516] Hardware name: Dell Inc. XPS 
8700/0KWVT8, BIOS A08 04/16/2014
  Mar  1 19:34:04 xps kernel: [ 5497.617517] task: 88034802c600 ti: 
88029858c000 task.ti: 88029858c000
  Mar  1 19:34:04 xps kernel: [ 5497.617518] RIP: 0010:[]  
[] __fscache_cookie_put+0x3a/0x40 [fscache]
  Mar  1 19:34:04 xps kernel: [ 5497.617525] RSP: 0018:88029858fd98  
EFLAGS: 00010282
  Mar  1 19:34:04 xps kernel: [ 5497.617526] RAX: 0001 RBX: 
8802e00244d0 RCX: 0034
  Mar  1 19:34:04 xps kernel: [ 5497.617527] RDX: 0001 RSI: 
8802e0024528 RDI: 8802e0024528
  Mar  1 19:34:04 xps kernel: [ 5497.617528] RBP: 88029858fda0 R08: 
88041ec972c0 R09: 0001
  Mar  1 19:34:04 xps kernel: [ 5497.617528] R10: 0010 R11: 
 R12: 8802dde8f000
  Mar  1 19:34:04 xps kernel: [ 5497.617529] R13: 1f39 R14: 
 R15: 88034802cca0
  Mar  1 19:34:04 xps kernel: [ 5497.617531] FS:  7f93632b5840() 
GS:88041ec8() knlGS:
  Mar  1 19:34:04 xps kernel: [ 5497.617532] CS:  0010 DS:  ES:  CR0: 
80050033
  Mar  1 19:34:04 xps kernel: [ 5497.617533] CR2: 2205d5e14000 CR3: 
000293ff6000 CR4: 00160670
  Mar  1 19:34:04 xps kernel: [ 5497.617534] Stack:
  Mar  1 19:34:04 xps kernel: [ 5497.617535]  8802e0024528 88029858fdb8 
c10a6517 880348d55800
  Mar  1 19:34:04 xps kernel: [ 5497.617536]  88029858fdd0 c1854232 
880348d55800 88029858fdf8
  Mar  1 19:34:04 xps kernel: [ 5497.617538]  c182d3e0 8800a1c7ce40 
880348d55000 880348d55008
  Mar  1 19:34:04 xps kernel: [ 5497.617548] Call Trace:
  Mar

[Kernel-packages] [Bug 1752669] Re: iwlwifi 0000:01:00.0: fail to flush all tx fifo queues Q 0

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

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

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

Title:
  iwlwifi :01:00.0: fail to flush all tx fifo queues Q 0

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

Bug description:
  Hello,

  dmesg:
  [17322.141897] iwlwifi :01:00.0: fail to flush all tx fifo queues Q 0
  [17322.141980] iwlwifi :01:00.0: Queue 0 is active on fifo 3 and stuck 
for 0 ms. SW [136, 137] HW [136, 137] FH TRB=0x080300088

  Regards,
  --
  Cristian

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-11-generic 4.15.0-11.12
  ProcVersionSignature: Ubuntu 4.15.0-11.12-generic 4.15.5
  Uname: Linux 4.15.0-11-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   caravena   1817 F...m pulseaudio
   /dev/snd/controlC0:  caravena   1817 F pulseaudio
  CurrentDesktop: ubuntu-communitheme:ubuntu:GNOME
  Date: Thu Mar  1 14:44:43 2018
  InstallationDate: Installed on 2017-10-13 (139 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 530U3C/530U4C
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.15.0-11-generic 
root=UUID=707d0f89-4b1d-4432-9d50-6058dc4c1ee9 ro rootflags=subvol=@ quiet 
splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-11-generic N/A
   linux-backports-modules-4.15.0-11-generic  N/A
   linux-firmware 1.171
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/15/2013
  dmi.bios.vendor: Phoenix Technologies Ltd.
  dmi.bios.version: P14AAJ
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: SAMSUNG_NP1234567890
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: FAB1
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLtd.:bvrP14AAJ:bd04/15/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn530U3C/530U4C:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnSAMSUNG_NP1234567890:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1:
  dmi.product.family: ChiefRiver System
  dmi.product.name: 530U3C/530U4C
  dmi.product.version: 0.1
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.

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

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

[Kernel-packages] [Bug 1753439] [NEW] Redpine: BLE scanning for nearby beacons per second is too low and result high loss rate.

Public bug reported:

Steps to replicate the issue:

1. Power on the BT device, then change the terminal by "Ctil+F1" or open 
another putty to ssh SUT.
2.Use command below to discover BLE device.
$ sudo stdbuf -i0-o0 -e0 /snap/bluez/current/usr/bin/hcitool lescan 
--duplicates --passive | perl -nle 'print scalar(localtime), " ",$_'
3. log as attachment.

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

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

Title:
  Redpine: BLE scanning for nearby beacons per second is too low and
  result high loss rate.

Status in linux package in Ubuntu:
  New

Bug description:
  Steps to replicate the issue:

  1. Power on the BT device, then change the terminal by "Ctil+F1" or open 
another putty to ssh SUT.
  2.Use command below to discover BLE device.
  $ sudo stdbuf -i0-o0 -e0 /snap/bluez/current/usr/bin/hcitool lescan 
--duplicates --passive | perl -nle 'print scalar(localtime), " ",$_'
  3. log as attachment.

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

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

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

2018-03-05 Thread 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 1753439

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

Title:
  Redpine: BLE scanning for nearby beacons per second is too low and
  result high loss rate.

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Steps to replicate the issue:

  1. Power on the BT device, then change the terminal by "Ctil+F1" or open 
another putty to ssh SUT.
  2.Use command below to discover BLE device.
  $ sudo stdbuf -i0-o0 -e0 /snap/bluez/current/usr/bin/hcitool lescan 
--duplicates --passive | perl -nle 'print scalar(localtime), " ",$_'
  3. log as attachment.

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

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

[Kernel-packages] [Bug 1751660] Re: linux: 4.15.0-11.12 -proposed tracker

2018-03-05 Thread Andy Whitcroft

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

** Changed in: kernel-sru-workflow/automated-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-release
   Status: New => Invalid

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

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

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

Title:
  linux: 4.15.0-11.12 -proposed tracker

Status in Kernel SRU Workflow:
  Invalid
Status in Kernel SRU Workflow automated-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-release series:
  Invalid
Status in Kernel SRU Workflow regression-testing series:
  Invalid
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  Invalid

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

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

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

[Kernel-packages] [Bug 1752829] Re: AMD HAINAN (Radeon R5 M330) Clock frequency is 750MHz while it is supposed to be 1030MHz

2018-03-05 Thread Yassine

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

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

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

Title:
  AMD HAINAN (Radeon R5 M330) Clock frequency is 750MHz while it is
  supposed to be 1030MHz

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Kernel source: /drivers/gpu/drm/radeon/si_dpm.c line 2985:

  max_sclk = 75000;

  instead of

  max_sclk = 103000;

  Why is that? I changed it and rebuilt the kernel, and I can say that
  there are absolutely no issues when using the 1030MHz clock, which is
  what it is supposed to be.

  Linux Version: 4.13.0-36-generic

  --- 
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  yassine3068 F pulseaudio
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 17.10
  HibernationDevice: RESUME=UUID=e9860ff6-0207-40ae-b2dd-115d7c7956b8
  InstallationDate: Installed on 2016-12-19 (439 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 005: ID 0bda:57d6 Realtek Semiconductor Corp. 
   Bus 001 Device 003: ID 0bda:b006 Realtek Semiconductor Corp. 
   Bus 001 Device 002: ID 25a7:0701  
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP Notebook
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: \\boot\vmlinuz-4.13.0-36-generic.efi.signed 
root=UUID=070ac60f-63d1-48e3-9322-44812d365c40 ro quiet splash radeon.runpm=1 
vt.handoff=7 initrd=boot\initrd.img-4.13.0-36-generic
  ProcVersionSignature: Ubuntu 4.13.0-36.40-generic 4.13.13
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-36-generic N/A
   linux-backports-modules-4.13.0-36-generic  N/A
   linux-firmware 1.169.3
  Tags:  artful wayland-session
  Uname: Linux 4.13.0-36-generic x86_64
  UpgradeStatus: Upgraded to artful on 2017-10-20 (135 days ago)
  UserGroups: adm cdrom dialout dip lpadmin lxd plugdev sambashare sudo video
  _MarkForUpload: True
  dmi.bios.date: 11/24/2015
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.1D
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 8136
  dmi.board.vendor: HP
  dmi.board.version: 31.34
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.1D:bd11/24/2015:svnHP:pnHPNotebook:pvrType1ProductConfigId:rvnHP:rn8136:rvr31.34:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV G=N L=CON B=HP
  dmi.product.name: HP Notebook
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP

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

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

[Kernel-packages] [Bug 1753424] Re: s390/crypto: Fix kernel crash on aes_s390 module remove

** Also affects: ubuntu-z-systems
   Importance: Undecided
   Status: New

** Changed in: ubuntu-z-systems
   Importance: Undecided => High

** Changed in: ubuntu-z-systems
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

** Changed in: ubuntu-z-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/1753424

Title:
  s390/crypto: Fix kernel crash on aes_s390 module remove

Status in Ubuntu on IBM z Systems:
  Incomplete
Status in linux package in Ubuntu:
  New
Status in linux source package in Bionic:
  New

Bug description:
  Upstream patch to fix the aes_s390 kernel module remove crash,
  introduced with kernel 4.15 rc1.

  Here is the patch to fix the kernel crash on aes_s390 kernel module removal.
  Please note that this patch is as of now not upstream available but in the 
s390 pipe for the next merge window (and so may be visible upstream with the 
start of the 4.17 development kernels).

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

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

[Kernel-packages] [Bug 1752182] Re: [Feature]Update Ubuntu 18.04 lpfc FC driver with 32/64GB HBA support and bug fixes

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

** Changed in: linux (Ubuntu Bionic)
 Assignee: (unassigned) => 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/1752182

Title:
  [Feature]Update Ubuntu 18.04 lpfc FC driver with 32/64GB HBA support
  and bug fixes

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

Bug description:
  This is a placeholder bugzilla that will list all commit ids needed
  for Broadcom Emulex FC 32/64GB new hardware support and all bug fixes
  available upstream.

  Note the lpfc FC driver commit list will include NVMe patches for ease
  of maintainability vs. upstream but we ask that you not build NVMe FC
  since we do not intend to support NVMe FC on 18.04 (4.15 kernel) at
  this time due to all of the unmet upper layer dependencies.

  Laurie Barry

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

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

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

--- Comment From chand...@in.ibm.com 2018-03-05 05:29 EDT---
*** Bug 165334 has been marked as a duplicate of this bug. ***

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

Title:
  few kernel selftest failed on Ubuntu 17.10

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

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 1730832] Re: [Feature] Add xHCI debug device support in the driver

https://lists.ubuntu.com/archives/kernel-team/2018-March/090558.html

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

Title:
  [Feature] Add xHCI debug device support in the driver

Status in intel:
  Triaged
Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Bionic:
  In Progress

Bug description:
  Description

  xHCI compatible USB host controllers(i.e. super-speed USB3 controllers)
  can be implemented with the Debug Capability(DbC). It presents a debug
  device which is fully compliant with the USB framework and provides the
  equivalent of a very high performance full-duplex serial link. The debug
  capability operation model and registers interface are defined in 7.6.8
  of the xHCI specification, revision 1.1.

  The DbC debug device shares a root port with the xHCI host. By default,
  the debug capability is disabled and the root port is assigned to xHCI.
  When the DbC is enabled, the root port will be assigned to the DbC debug
  device, and the xHCI sees nothing on this port. This implementation uses
  a sysfs node named  under the xHCI device to manage the enabling
  and disabling of the debug capability.

  When the debug capability is enabled, it will present a debug device
  through the debug port. This debug device is fully compliant with the
  USB3 framework, and it can be enumerated by a debug host on the other
  end of the USB link. As soon as the debug device is configured, a TTY
  serial device named /dev/ttyDBC0 will be created.

  One use of this link is running a login service on the debug target.
  Hence it can be remote accessed by a debug host. Another use case can
  probably be found in servers. It provides a peer-to-peer USB link
  between two host-only machines. This provides a reasonable out-of-band
  communication method between two servers.

  Target Kernel: 4.16
  Target Release: 18.04

To manage notifications about this bug go to:
https://bugs.launchpad.net/intel/+bug/1730832/+subscriptions

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

[Kernel-packages] [Bug 1753346] Re: AMD 7 1800X system (Dell Inspiron 5675) randomly freezes

Does this issue go away if you boot back into the prior kernel?

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

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

Title:
  AMD 7 1800X system (Dell Inspiron 5675) randomly freezes

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  This is happening every day or so.  I cannot see anything in the
  kern.log or syslog that give me a clue on where/what the issue might.
  I was using Ubuntu 17.10 earlier and upgraded to Ubuntu 18.04 on
  3/3/2018, since I thought kernel 4.15 might have better support for
  the ryzen 7 and also maybe amdgpu for the radeon 580 might be newer.
  I have removed most external devices except for networking and HDMI
  and audio out.

  Attached a tarball of info, although I believe that since I used
  'ubuntu-bug linux' command, the information might be duplicated,
  apologize for any extra attachments.

  $ ls -l dell-5675-sysinfo/
  total 168
  -rw-r--r-- 1 pss pss 83139 Mar  4 19:47 dmesg
  -rw-r--r-- 1 pss pss 26154 Mar  4 19:44 dmidecode
  -rw-r--r-- 1 pss pss  1507 Mar  4 19:45 gpu-manager.log
  -rw-r--r-- 1 pss pss   110 Mar  4 19:44 lsb-release-a
  -rw-r--r-- 1 pss pss  1464 Mar  4 19:44 lscpu
  -rw-r--r-- 1 pss pss  4353 Mar  4 19:46 lspci
  -rw-r--r-- 1 pss pss  4105 Mar  4 20:05 lspci-vvv-radeon-580.txt
  -rw-r--r-- 1 pss pss 19318 Mar  4 19:48 
mprime-p95v294b8.linux64-results-2018-03-04.txt
  -rw-r--r-- 1 pss pss   104 Mar  4 19:44 uname-a
  -rw-r--r-- 1 pss pss35 Mar  4 20:27 version.log

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-10-generic 4.15.0-10.11
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  pss1801 F pulseaudio
   /dev/snd/controlC0:  pss1801 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Mar  4 20:21:55 2018
  InstallationDate: Installed on 2018-02-16 (16 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  MachineType: Dell Inc. Inspiron 5675
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.utf8
   SHELL=/bin/bash
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-10-generic.efi.signed 
root=UUID=d6a2ae1e-5421-435f-8e4c-e377133cebc9 ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-10-generic N/A
   linux-backports-modules-4.15.0-10-generic  N/A
   linux-firmware 1.172
  SourcePackage: linux
  UpgradeStatus: Upgraded to bionic on 2018-03-04 (1 days ago)
  dmi.bios.date: 12/04/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.3.6
  dmi.board.name: 07PR60
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 3
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: 1.3.6
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.3.6:bd12/04/2017:svnDellInc.:pnInspiron5675:pvr1.3.6:rvnDellInc.:rn07PR60:rvrA00:cvnDellInc.:ct3:cvr1.3.6:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 5675
  dmi.product.version: 1.3.6
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1752829] Re: AMD HAINAN (Radeon R5 M330) Clock frequency is 750MHz while it is supposed to be 1030MHz

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.16 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.16-rc4


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

Title:
  AMD HAINAN (Radeon R5 M330) Clock frequency is 750MHz while it is
  supposed to be 1030MHz

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Kernel source: /drivers/gpu/drm/radeon/si_dpm.c line 2985:

  max_sclk = 75000;

  instead of

  max_sclk = 103000;

  Why is that? I changed it and rebuilt the kernel, and I can say that
  there are absolutely no issues when using the 1030MHz clock, which is
  what it is supposed to be.

  Linux Version: 4.13.0-36-generic

  --- 
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  yassine3068 F pulseaudio
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 17.10
  HibernationDevice: RESUME=UUID=e9860ff6-0207-40ae-b2dd-115d7c7956b8
  InstallationDate: Installed on 2016-12-19 (439 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 005: ID 0bda:57d6 Realtek Semiconductor Corp. 
   Bus 001 Device 003: ID 0bda:b006 Realtek Semiconductor Corp. 
   Bus 001 Device 002: ID 25a7:0701  
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP Notebook
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: \\boot\vmlinuz-4.13.0-36-generic.efi.signed 
root=UUID=070ac60f-63d1-48e3-9322-44812d365c40 ro quiet splash radeon.runpm=1 
vt.handoff=7 initrd=boot\initrd.img-4.13.0-36-generic
  ProcVersionSignature: Ubuntu 4.13.0-36.40-generic 4.13.13
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-36-generic N/A
   linux-backports-modules-4.13.0-36-generic  N/A
   linux-firmware 1.169.3
  Tags:  artful wayland-session
  Uname: Linux 4.13.0-36-generic x86_64
  UpgradeStatus: Upgraded to artful on 2017-10-20 (135 days ago)
  UserGroups: adm cdrom dialout dip lpadmin lxd plugdev sambashare sudo video
  _MarkForUpload: True
  dmi.bios.date: 11/24/2015
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.1D
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 8136
  dmi.board.vendor: HP
  dmi.board.version: 31.34
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.1D:bd11/24/2015:svnHP:pnHPNotebook:pvrType1ProductConfigId:rvnHP:rn8136:rvr31.34:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV G=N L=CON B=HP
  dmi.product.name: HP Notebook
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP

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

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

[Kernel-packages] [Bug 1753292] Re: watchdog: BUG: soft lockup - CPU#0 stuck for 74s! [ksoftirqd/0:7]

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.16 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.16-rc4


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

Title:
  watchdog: BUG: soft lockup - CPU#0 stuck for 74s! [ksoftirqd/0:7]

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  on virtual machine

  ProblemType: KernelOops
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-10-generic 4.15.0-10.11
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  Annotation: Your system might become unstable now and might need to be 
restarted.
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gdm 861 F pulseaudio
igor   1163 F pulseaudio
  Date: Sun Mar  4 10:05:58 2018
  Failure: oops
  InstallationDate: Installed on 2017-11-18 (105 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20171117)
  IwConfig:
   lono wireless extensions.
   
   ens33 no wireless extensions.
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub
   Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: VMware, Inc. VMware Virtual Platform
  ProcFB: 0 svgadrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-10-generic 
root=UUID=1a09b2d1-1d4f-44fc-baa7-37b9cf13c503 ro find_preseed=/preseed.cfg 
auto noprompt priority=critical locale=en_US quiet
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: kerneloops-daemon N/A
  RfKill:
   
  SourcePackage: linux
  Title: watchdog: BUG: soft lockup - CPU#0 stuck for 74s! [ksoftirqd/0:7]
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/19/2017
  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:bd05/19/2017: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/1753292/+subscriptions

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

[Kernel-packages] [Bug 1753050] Re: Does not recognize external monitor

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.16 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.16-rc4


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

Title:
  Does not recognize external monitor

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Neither HDMI (digital) nor VGA (analog) output work with the kernel.
  With 4.4.0-112-generic they work fine.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-116-generic 4.4.0-116.140
  ProcVersionSignature: Ubuntu 4.4.0-116.140-generic 4.4.98
  Uname: Linux 4.4.0-116-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jarnos 1778 F pulseaudio
  CurrentDesktop: XFCE
  Date: Sat Mar  3 09:35:16 2018
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=19c075ab-2b2e-4285-a3a5-dbd15ee7b31e
  InstallationDate: Installed on 2015-11-21 (832 days ago)
  InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-116-generic 
root=UUID=bdc3be24-dee9-4ead-bca0-c9b1e45a87e5 ro persistent quiet splash
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-116-generic N/A
   linux-backports-modules-4.4.0-116-generic  N/A
   linux-firmware 1.157.17
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/01/2011
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 68MVD Ver. F.20
  dmi.board.name: 30C5
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 71.36
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68MVDVer.F.20:bd12/01/2011:svnHewlett-Packard:pn:pvrF.20:rvnHewlett-Packard:rn30C5:rvrKBCVersion71.36:cvnHewlett-Packard:ct10:cvr:
  dmi.product.version: F.20
  dmi.sys.vendor: Hewlett-Packard

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

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

[Kernel-packages] [Bug 1753144] Re: Booting kernel 4.4.0-116.140 fails

Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.16 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.16-rc4


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

Title:
  Booting kernel 4.4.0-116.140 fails

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Booting kernel 4.4.0-116.140 lands me in an ash shell with prompt
  'initramfs'. keyboard and mouse USB fails, so that I can do nothing.

  Error messages from module hid: 'unknown symbol __x86_indirect_thunk_XXX err 
-22' and
  'disagrees about version of __x86_indirect_thunk_XXX err -22, where XXX has 5 
or 6 different 3-letter values.

  I have gcc-5:i386 (5.4.0-6ubuntu1~16.04.6, 5.4.0-6ubuntu1~16.04.9),
  which would be correct according to bug report #1750937. Since there
  are no modules built by DKMS, there is no compilation involved in
  installation.

  I removed and reinstalled the kernel image and headers, but the problem did 
not disappear: 
  Install: linux-headers-generic:i386 (4.4.0.116.122, automatic), 
linux-image-generic:i386 (4.4.0.116.122, automatic), 
linux-headers-4.4.0-116:i386 (4.4.0-116.140, automatic), 
linux-image-extra-4.4.0-116-generic:i386 (4.4.0-116.140, automatic), 
linux-headers-4.4.0-116-generic:i386 (4.4.0-116.140, automatic), 
linux-generic:i386 (4.4.0.116.122), linux-image-4.4.0-116-generic:i386 
(4.4.0-116.140, automatic)

  Since I cannot boot into this kernel, I cannot generate a bug report,
  and there are no syslog entries.

  Description:Ubuntu 16.04.4 LTS
  Release:16.04

  linux-image-4.4.0-116-generic:
Geïnstalleerd: 4.4.0-116.140
  linux-image-extra-4.4.0-116-generic:
Geïnstalleerd: 4.4.0-116.140
  gcc-5:
Geïnstalleerd: 5.4.0-6ubuntu1~16.04.9

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

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

[Kernel-packages] [Bug 1753144] Re: Booting kernel 4.4.0-116.140 fails

Are you able to boot if you select the prior kernel version from the
GRUB menu?

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

Title:
  Booting kernel 4.4.0-116.140 fails

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Booting kernel 4.4.0-116.140 lands me in an ash shell with prompt
  'initramfs'. keyboard and mouse USB fails, so that I can do nothing.

  Error messages from module hid: 'unknown symbol __x86_indirect_thunk_XXX err 
-22' and
  'disagrees about version of __x86_indirect_thunk_XXX err -22, where XXX has 5 
or 6 different 3-letter values.

  I have gcc-5:i386 (5.4.0-6ubuntu1~16.04.6, 5.4.0-6ubuntu1~16.04.9),
  which would be correct according to bug report #1750937. Since there
  are no modules built by DKMS, there is no compilation involved in
  installation.

  I removed and reinstalled the kernel image and headers, but the problem did 
not disappear: 
  Install: linux-headers-generic:i386 (4.4.0.116.122, automatic), 
linux-image-generic:i386 (4.4.0.116.122, automatic), 
linux-headers-4.4.0-116:i386 (4.4.0-116.140, automatic), 
linux-image-extra-4.4.0-116-generic:i386 (4.4.0-116.140, automatic), 
linux-headers-4.4.0-116-generic:i386 (4.4.0-116.140, automatic), 
linux-generic:i386 (4.4.0.116.122), linux-image-4.4.0-116-generic:i386 
(4.4.0-116.140, automatic)

  Since I cannot boot into this kernel, I cannot generate a bug report,
  and there are no syslog entries.

  Description:Ubuntu 16.04.4 LTS
  Release:16.04

  linux-image-4.4.0-116-generic:
Geïnstalleerd: 4.4.0-116.140
  linux-image-extra-4.4.0-116-generic:
Geïnstalleerd: 4.4.0-116.140
  gcc-5:
Geïnstalleerd: 5.4.0-6ubuntu1~16.04.9

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

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

[Kernel-packages] [Bug 1753346] Re: AMD 7 1800X system (Dell Inspiron 5675) randomly freezes

Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.16 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.16-rc4

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

Title:
  AMD 7 1800X system (Dell Inspiron 5675) randomly freezes

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  This is happening every day or so.  I cannot see anything in the
  kern.log or syslog that give me a clue on where/what the issue might.
  I was using Ubuntu 17.10 earlier and upgraded to Ubuntu 18.04 on
  3/3/2018, since I thought kernel 4.15 might have better support for
  the ryzen 7 and also maybe amdgpu for the radeon 580 might be newer.
  I have removed most external devices except for networking and HDMI
  and audio out.

  Attached a tarball of info, although I believe that since I used
  'ubuntu-bug linux' command, the information might be duplicated,
  apologize for any extra attachments.

  $ ls -l dell-5675-sysinfo/
  total 168
  -rw-r--r-- 1 pss pss 83139 Mar  4 19:47 dmesg
  -rw-r--r-- 1 pss pss 26154 Mar  4 19:44 dmidecode
  -rw-r--r-- 1 pss pss  1507 Mar  4 19:45 gpu-manager.log
  -rw-r--r-- 1 pss pss   110 Mar  4 19:44 lsb-release-a
  -rw-r--r-- 1 pss pss  1464 Mar  4 19:44 lscpu
  -rw-r--r-- 1 pss pss  4353 Mar  4 19:46 lspci
  -rw-r--r-- 1 pss pss  4105 Mar  4 20:05 lspci-vvv-radeon-580.txt
  -rw-r--r-- 1 pss pss 19318 Mar  4 19:48 
mprime-p95v294b8.linux64-results-2018-03-04.txt
  -rw-r--r-- 1 pss pss   104 Mar  4 19:44 uname-a
  -rw-r--r-- 1 pss pss35 Mar  4 20:27 version.log

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-10-generic 4.15.0-10.11
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  pss1801 F pulseaudio
   /dev/snd/controlC0:  pss1801 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Mar  4 20:21:55 2018
  InstallationDate: Installed on 2018-02-16 (16 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  MachineType: Dell Inc. Inspiron 5675
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.utf8
   SHELL=/bin/bash
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-10-generic.efi.signed 
root=UUID=d6a2ae1e-5421-435f-8e4c-e377133cebc9 ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-10-generic N/A
   linux-backports-modules-4.15.0-10-generic  N/A
   linux-firmware 1.172
  SourcePackage: linux
  UpgradeStatus: Upgraded to bionic on 2018-03-04 (1 days ago)
  dmi.bios.date: 12/04/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.3.6
  dmi.board.name: 07PR60
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 3
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: 1.3.6
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.3.6:bd12/04/2017:svnDellInc.:pnInspiron5675:pvr1.3.6:rvnDellInc.:rn07PR60:rvrA00:cvnDellInc.:ct3:cvr1.3.6:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 5675
  dmi.product.version: 1.3.6
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1753010] Re: after recent updates playing youtube videos in firefox causes sometimes freezing of the system

Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.16 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.16-rc4


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

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

Title:
  after recent updates playing youtube videos in firefox causes
  sometimes freezing of the system

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  After recent updates that fixed the bug
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1742675 on my
  computer the following different bug has appeared. Playing Youtube
  music videos (static picture + music, length 40-70 minutes) in Firefox
  (as background for other activities on computer) causes sometimes
  (rather often, up to several times per day) freezing of the system.
  And only restart through reset button can help.

  Initially I though that it is related to different Javascript-related
  tasks (manipulating with complex widgets in Chromium, running heavy
  gulp tasks through yarn) but it looks they are not the reason (or at
  least not the main reason). Because right now I have seen the problem
  when keyboard/mouse was not touched at all.

  That's why I think this information is rather enough; and I decided to post 
this bug.
  --- 
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  kamil  2021 F pulseaudio
   /dev/snd/controlC1:  kamil  2021 F pulseaudio
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=5b5ffc28-8999-4ad7-9ff3-f3298c4f28c2
  InstallationDate: Installed on 2017-06-23 (252 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release i386 
(20170215.2)
  MachineType: Packard Bell Easynote ENTE70BH
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-36-generic 
root=UUID=557e3c22-0c8c-44b3-a8f6-5446013327ad ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.13.0-36.40~16.04.1-generic 4.13.13
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-36-generic N/A
   linux-backports-modules-4.13.0-36-generic  N/A
   linux-firmware 1.157.17
  Tags:  xenial
  Uname: Linux 4.13.0-36-generic i686
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 08/08/2016
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.05
  dmi.board.name: Easynote ENTE70BH
  dmi.board.vendor: Packard Bell
  dmi.board.version: V1.05
  dmi.chassis.type: 10
  dmi.chassis.vendor: Packard Bell
  dmi.chassis.version: V1.05
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.05:bd08/08/2016:svnPackardBell:pnEasynoteENTE70BH:pvrV1.05:rvnPackardBell:rnEasynoteENTE70BH:rvrV1.05:cvnPackardBell:ct10:cvrV1.05:
  dmi.product.family: BDW
  dmi.product.name: Easynote ENTE70BH
  dmi.product.version: V1.05
  dmi.sys.vendor: Packard Bell

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

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

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

2018-03-05 Thread 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 1753438

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

Title:
  Redpine: Sometimes Wi-Fi connection shows "unavailable" after resume
  from WoWLAN S4. WLAN can be recover after reboot or reloading WIFI
  driver.

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Following are steps to reproduce the issue:

  1. Ensure WoWLAN is enabled in BIOS.
  2. Initiate connection to an AP (using nmcli)
  3. Configure the device for WoWLAN, run the command:
  $ sudo iw phy phy0 wowlan enable magic-packet
  4. Enter S4 (using hibernate)
  5. From another computer on the same network run the following command:
  $ wakeonlan {mac}
  6. Check network states and WIFI shows "Unavailable"

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

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

[Kernel-packages] [Bug 1752946] Re: System freezes on copy to USB drive since kernel 4.13.0-36 (32bit)

Would it be possible for you to test the proposed kernel and post back if it 
resolves this bug?
See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to 
enable and use -proposed. 

Thank you in advance!


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

** Tags added: kernel-da-key pti

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

Title:
  System freezes on copy to USB drive since kernel 4.13.0-36 (32bit)

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Lately one of my boxes reproducably freezes when I copy data from
  internal hard disk to an USB device (USB hard disk or USB key). It
  looks like it works at first, than the "wait for IO load" in the
  system monitor applet rises to max and the system does no longer
  respond to input, only hard reboot brings it back to life.

  When booting the previous kernel 4.13.0-32 all is fine. Do I boot to
  -36 the error is back.

  I append a lshw dump as text file.
  The hardware basically:
   ASRock Board D1800B-ITX
   CPU: Intel(R) Celeron(R) CPU  J1800  @ 2.41GHz
    4GB RAM
    otherwise nothing special

  System: Ubuntu 17.10
  Kernel (now): Linux Esel 4.13.0-32-generic #35-Ubuntu SMP Thu Jan 25 09:18:49 
UTC 2018 i686 i686 i686 GNU/Linux
  Kernel in question: linux-image-4.13.0-36-generic:
    Installiert:   4.13.0-36.40

  Desktop is Mate
  --- 
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  sunny  1547 F pulseaudio
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 17.10
  HibernationDevice: RESUME=UUID=22925ab1-8a2f-4f13-a372-0a961da45990
  InstallationDate: Installed on 2015-11-19 (834 days ago)
  InstallationMedia: Ubuntu-MATE 15.10 "Wily Werewolf" - Release i386 (20151021)
  IwConfig:
   lono wireless extensions.
   
   enp2s0no wireless extensions.
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 046a:0023 Cherry GmbH CyMotion Master Linux Keyboard 
G230
   Bus 001 Device 003: ID 0557:8021 ATEN International Co., Ltd CS1764A [CubiQ 
DVI KVMP Switch]
   Bus 001 Device 002: ID 05e3:0608 Genesys Logic, Inc. Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-32-generic 
root=UUID=f377d365-a2b2-4d29-b4c6-60ea74207e8f ro processor.max_cstate=1 quiet 
splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-32-generic N/A
   linux-backports-modules-4.13.0-32-generic  N/A
   linux-firmware 1.169.3
  RfKill:
   
  Tags:  artful
  Uname: Linux 4.13.0-32-generic i686
  UpgradeStatus: Upgraded to artful on 2017-10-23 (130 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/07/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P2.00
  dmi.board.name: D1800B-ITX
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP2.00:bd11/07/2016:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnD1800B-ITX:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.

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

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

[Kernel-packages] [Bug 1753439] Re: Redpine: BLE scanning for nearby beacons per second is too low and result high loss rate.

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.16 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.16-rc4


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

Title:
  Redpine: BLE scanning for nearby beacons per second is too low and
  result high loss rate.

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Steps to replicate the issue:

  1. Power on the BT device, then change the terminal by "Ctil+F1" or open 
another putty to ssh SUT.
  2.Use command below to discover BLE device.
  $ sudo stdbuf -i0-o0 -e0 /snap/bluez/current/usr/bin/hcitool lescan 
--duplicates --passive | perl -nle 'print scalar(localtime), " ",$_'
  3. log as attachment.

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

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

[Kernel-packages] [Bug 1753438] Re: Redpine: Sometimes Wi-Fi connection shows "unavailable" after resume from WoWLAN S4. WLAN can be recover after reboot or reloading WIFI driver.

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.16 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.16-rc4


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

Title:
  Redpine: Sometimes Wi-Fi connection shows "unavailable" after resume
  from WoWLAN S4. WLAN can be recover after reboot or reloading WIFI
  driver.

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Following are steps to reproduce the issue:

  1. Ensure WoWLAN is enabled in BIOS.
  2. Initiate connection to an AP (using nmcli)
  3. Configure the device for WoWLAN, run the command:
  $ sudo iw phy phy0 wowlan enable magic-packet
  4. Enter S4 (using hibernate)
  5. From another computer on the same network run the following command:
  $ wakeonlan {mac}
  6. Check network states and WIFI shows "Unavailable"

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

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

[Kernel-packages] [Bug 1753439] Re: Redpine: BLE scanning for nearby beacons per second is too low and result high loss rate.

** Attachment added: "BLE_SCAN.TXT"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1753439/+attachment/5069782/+files/BLE_SCAN.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/1753439

Title:
  Redpine: BLE scanning for nearby beacons per second is too low and
  result high loss rate.

Status in linux package in Ubuntu:
  New

Bug description:
  Steps to replicate the issue:

  1. Power on the BT device, then change the terminal by "Ctil+F1" or open 
another putty to ssh SUT.
  2.Use command below to discover BLE device.
  $ sudo stdbuf -i0-o0 -e0 /snap/bluez/current/usr/bin/hcitool lescan 
--duplicates --passive | perl -nle 'print scalar(localtime), " ",$_'
  3. log as attachment.

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

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

[Kernel-packages] [Bug 1753304] Re: No Internet when waking from suspend

2018-03-05 Thread Etienne Papegnies

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

** No longer affects: ubuntu-mate

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

Title:
  No Internet when waking from suspend

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Ever since I updated my computer later last week I have had no
  internet access after waking from a suspend. This is all I get as a
  response to these ping commands:

  $ ping google.ca
  PING google.ca (216.58.217.195) 56(84) bytes of data.

  $ ping 8.8.8.8
  PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data.

  localhost works, and I am still able to login to my router over
  wireless. No other computer or phone in my house has any problem with
  the internet, so the problem is specific only to my computer and only
  after the software update.

  the nm-applet is alive and I am able to see the wireless connections
  available to me. If I reconnect to the wifi connection it makes no
  difference.

  If I run "sudo service network-manager restart" it also makes no
  difference.

  The only solution I have found so far to fix the problem is to
  completely restart the computer.

  Any help or advice would be appreciated. If I missed some valuable
  information let me know and I will come back with more info.

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

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

[Kernel-packages] [Bug 1752236] Re: Ubuntu 18.04 - Performance: Radix page fault handler bug in KVM

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

Title:
  Ubuntu 18.04 - Performance: Radix page fault handler bug in KVM

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

Bug description:
  == Comment: #0 - JENIFER HOPPER  - 2018-02-27 17:25:59 ==
  +++ This bug was initially created as a clone of Bug #165215 +++

  ---Problem Description---
  Paul Mackerras has posted a fix to a Radix page fault handler bug in KVM:

  http://patchwork.ozlabs.org/patch/877033/
  " KVM: PPC: Book3S HV: Fix handling of large pages in radix page fault 
handler "

  This is critical for P9 KVM performance. Using an open source database 
workload, we saw an 11% throughput improvement with this patch when the guest 
was backed w/ 2MB hugepages. Without this patch, hugepage backing does not help 
performance compared to base page size. 
   
  ---uname output---
  18.04 lts
   
  Machine Type = 5104-22C 
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
Back guest w/ 2MB pages, run a throughput test and compare performance.
   
  Contact Information = jhop...@us.ibm.com

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

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

[Kernel-packages] [Bug 1752236] Re: Ubuntu 18.04 - Performance: Radix page fault handler bug in KVM

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

Title:
  Ubuntu 18.04 - Performance: Radix page fault handler bug in KVM

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

Bug description:
  == Comment: #0 - JENIFER HOPPER  - 2018-02-27 17:25:59 ==
  +++ This bug was initially created as a clone of Bug #165215 +++

  ---Problem Description---
  Paul Mackerras has posted a fix to a Radix page fault handler bug in KVM:

  http://patchwork.ozlabs.org/patch/877033/
  " KVM: PPC: Book3S HV: Fix handling of large pages in radix page fault 
handler "

  This is critical for P9 KVM performance. Using an open source database 
workload, we saw an 11% throughput improvement with this patch when the guest 
was backed w/ 2MB hugepages. Without this patch, hugepage backing does not help 
performance compared to base page size. 
   
  ---uname output---
  18.04 lts
   
  Machine Type = 5104-22C 
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
Back guest w/ 2MB pages, run a throughput test and compare performance.
   
  Contact Information = jhop...@us.ibm.com

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

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

[Kernel-packages] [Bug 1645969] Re: [Feature] Jefferson Peak(9560) WiFi/BT support

2018-03-05 Thread Seth Forshee

We have the merge from comment #7 in bionic already. I'm not seeing the
commits from comment #8 in upstream linux-firmware at all though.

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

Title:
  [Feature] Jefferson Peak(9560) WiFi/BT support

Status in intel:
  New
Status in linux package in Ubuntu:
  Triaged
Status in linux-firmware package in Ubuntu:
  Triaged
Status in linux source package in Bionic:
  Triaged
Status in linux-firmware source package in Bionic:
  Triaged

Bug description:
  Jefferson Peak (JfP):802.11abgn+acR2 MIMO 2x2
  Supports BT 5.0

  HW: Gemini Lake

  Target Release: 18.04

  Uptream schedule: TBD

To manage notifications about this bug go to:
https://bugs.launchpad.net/intel/+bug/1645969/+subscriptions

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

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

--- Comment From heinz-werner_se...@de.ibm.com 2018-03-05 05:04 EDT---
Canonical. any update on this LP ? Many thx in advance

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

Title:
  [18.04 FEAT] Add kvm_stat from kernel tree

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

Bug description:
  Improves RAS characterics of systems running KVM by providing kvm_stat script:
  https://github.com/torvalds/linux/tree/master/tools/kvm/kvm_stat

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

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

[Kernel-packages] [Bug 1752818] Re: nfp: read ME frequency from vNIC ctrl memory

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

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

** Also affects: linux (Ubuntu Bionic)
   Importance: Medium
   Status: Triaged

** Tags added: bionic 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/1752818

Title:
  nfp: read ME frequency from vNIC ctrl memory

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

Bug description:
  This is a backport request from Netronome.

  The following kernel changes were recently upstreamed to correct
  assumptions about ME clock speed which may not be correct for a given
  Netronome SmartNIC. There is also a firmware portion of this fix which
  is pending release. It seems worthwhile updating the kernel so that it
  will behave correctly once that portion of the fix becomes available.

  The kernel commits are:

  1d8ef0c07664 (“nfp: fix TLV offset calculation”)
  ce991ab6662a (“nfp: read ME frequency from vNIC ctrl memory”)
  73a0329b057e (“nfp: add TLV capabilities to the BAR”)

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

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

[Kernel-packages] [Bug 1753347] Re: [SRU] Lenovo E41 Mic mute hotkey is not responding

2018-03-05 Thread Seth Forshee

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

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

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

Title:
  [SRU] Lenovo E41 Mic mute hotkey is not responding

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Artful:
  New

Bug description:
  [Impact]
  Mic mute hotkey (F1) is not working due to the delay answer when reading EC 
VPC. 
  The ideapad_laptop module didn't wait enough time to read VPC.

  [Fix]
  Add more time to wait for reading EC VPC, the correct data will be got.
  Hotkey works well then.

  [Test Case]
  Tested on Lenovo E41, hotkey works well with this patch.

  [Regression Potential]
  No regression is expected.

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

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

[Kernel-packages] [Bug 1741081] Re: zfs-import-cache.service fails on startup

2018-03-05 Thread Łukasz Zemczak

Should I reject the artful SRU in that case? The .service file indeed
looks like it might need some changes, I would prefer the latest bionic
version to be SRUed.

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

Title:
  zfs-import-cache.service fails on startup

Status in zfs-linux package in Ubuntu:
  Fix Released
Status in zfs-linux source package in Artful:
  In Progress
Status in zfs-linux source package in Bionic:
  Fix Released

Bug description:
  == SRU Request, Artful ==

  Enable ZFS module to be loaded without the broken ubuntu-load-zfs-
  unconditionally.patch.

  == Fix ==

  Add a new zfs-load-module.service script that modprobes the ZFS module
  and remove any hard coded module loading from zfs-import-cache.service
  & zfs-import-scan.service and make these latter scripts require the
  new zfs-load-module.service script.  Also remove the now defunct
  ubuntu-load-zfs-unconditionally.patch as this will no longer be
  required.

  == Testcase ==

  On a clean VM, install with the fixed package, zfs should load
  automatically.

  == Regression potential ==

  ZFS module may not load if the changes are broken. However, testing
  proves this not to be the case.

  

  I just noticed on my test VM of artful that zfs-import-cache.service
  does not have a ConditionPathExists=/etc/zfs/zpool.cache. Because of
  that, it fails on startup, since the cache file does not exist.

  This line is being deleted by 
debian/patches/ubuntu-load-zfs-unconditionally.patch. This patch seems to exist 
per:
  https://bugs.launchpad.net/ubuntu/+source/lxd/+bug/1672749

  This patch still exists in bionic, so I assume it will be similarly
  broken.

  If the goal of the patch is to load the module (and only that), I
  think it should create a third unit instead:

  zfs-load-module.service
   ^^ runs modprobe zfs

  zfs-import-cache.service & zfs-import-scan.service
    ^^ per upstream minus modprobe plus Requires=zfs-load-module.service

  I have tested this manually and it works. I can submit a package patch
  if this is the desired solution.

  Interestingly, before this change, zfs-import-scan.service wasn't
  starting. If started manually, it worked. I had to give it a
  `systemctl enable zfs-import-scan.service` to create the Wants
  symlinks. Looking at the zfsutils-linux.postinst, I see the correct
  boilerplate from dh_systemd, so I'm not sure why this wasn't already
  done. Can anyone confirm or deny whether zfs-import-scan.service is
  enabled out-of-the-box on their system?

  Is the zfs-import-scan.service not starting actually the cause of the
  original bug? The design is that *either* zfs-import-cache.service or
  zfs-import-scan.service starts. They both call modprobe zfs.

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

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

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

--- Comment From heinz-werner_se...@de.ibm.com 2018-03-05 04:53 EDT---
We will provide that information ,once available.  Thx

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

Title:
  s390/crypto: Fix kernel crash on aes_s390 module remove

Status in Ubuntu on IBM z Systems:
  Incomplete
Status in linux package in Ubuntu:
  New
Status in linux source package in Bionic:
  New

Bug description:
  Upstream patch to fix the aes_s390 kernel module remove crash,
  introduced with kernel 4.15 rc1.

  Here is the patch to fix the kernel crash on aes_s390 kernel module removal.
  Please note that this patch is as of now not upstream available but in the 
s390 pipe for the next merge window (and so may be visible upstream with the 
start of the 4.17 development kernels).

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

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

[Kernel-packages] [Bug 1747625] Re: [v4.13, mlx5_core] Oops: 0000 [#1] SMP PTI

2018-03-05 Thread Peter Sabaini

Just a note that I didn't see this panic with 4.13.0-36-generic and
rebooting 66 nodes

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

Title:
  [v4.13,mlx5_core] Oops:  [#1] SMP PTI

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

Bug description:
  PowerEdge R730
  4.13.0-26-generic #29~16.04.2-Ubuntu
  mlx5_core firmware version: 14.20.1820

  kernel trace: https://pastebin.ubuntu.com/26529021/

  Issue happened when I issued "reboot" command. Other nodes with same
  specifications and software versions didn't hit this bug.

  A new "reboot" on the node that panic'ed didn't hit the bug.

  I've set "pti=off" on all of them for now.
  --- 
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Feb  5 13:07 seq
   crw-rw 1 root audio 116, 33 Feb  5 13:07 timer
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 16.04
  IwConfig: Error: [Errno 2] No such file or directory
  Lsusb:
   Bus 002 Device 002: ID 8087:8002 Intel Corp. 
   Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 001 Device 003: ID 413c:a001 Dell Computer Corp. Hub
   Bus 001 Device 002: ID 8087:800a Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. PowerEdge R730
  Package: linux (not installed)
  PciMultimedia:
   
  ProcFB: 0 mgadrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic.efi.signed 
root=UUID=2344957a-f5ed-46a7-87a5-255ab83876fb ro console=tty0 
console=ttyS0,115200 console=ttyS1,115200 panic=30 raid=noautodetect 
modprobe.blacklist=floppy
  ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-32-generic N/A
   linux-backports-modules-4.13.0-32-generic  N/A
   linux-firmware 1.157.14
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  xenial uec-images xenial uec-images
  Uname: Linux 4.13.0-32-generic x86_64
  UnreportableReason: The report belongs to a package that is not installed.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dialout dip floppy libvirtd netdev plugdev sudo 
video
  _MarkForUpload: False
  dmi.bios.date: 09/06/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.2.5
  dmi.board.name: 04N3DF
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A10
  dmi.chassis.type: 23
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr2.2.5:bd09/06/2016:svnDellInc.:pnPowerEdgeR730:pvr:rvnDellInc.:rn04N3DF:rvrA10:cvnDellInc.:ct23:cvr:
  dmi.product.name: PowerEdge R730
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1716747] Re: linux 4.12 - high system load and mouse delays - pipe A vblank wait timed out

@Jay, did it not exist in 4.13-0.35-generic?  This bug kind of fell of
the radar for a while, but it would be good to know when it came back.
We can then bisect down the commit.

** Summary changed:

- linux 4.12 - high system load and mouse delays - pipe A vblank wait timed out
+ High system load and mouse delays - pipe A vblank wait timed out

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

Title:
  High system load and mouse delays - pipe A vblank wait timed out

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

Bug description:
  This issue has been observed on a Lenovo X220i laptop:

  1. Booting the laptop with artful's 4.12 kernel results in a very sluggish 
system performance (mouse pointer delays) and a high system load.
  2. /var/log/kern.log indicates a problem with the display driver (see below)
  3. The system works without any issues if the zesty kernel (4.10) is used 
instead.

  Ubuntu release: Artful Aardvark (development branch)
  Kernel package version: 4.12.0.13.14

  
  Sep 12 20:22:45 trinity kernel: [  155.491074] pipe A vblank wait timed out
  Sep 12 20:22:45 trinity kernel: [  155.491117] [ cut here 
]
  Sep 12 20:22:45 trinity kernel: [  155.491171] WARNING: CPU: 0 PID: 203 at 
/build/linux-cK2WUa/linux-4.12.0/drivers/gpu/drm/i915/intel_display.c:12636 
intel_atomic_commit_tail+0x1010/0x1020 [i915]
  Sep 12 20:22:45 trinity kernel: [  155.491172] Modules linked in: 
nf_conntrack_netlink nfnetlink xfrm_user xfrm_algo xt_addrtype br_netfilter 
aufs xt_CHECKSUM iptable_mangle ipt_MASQUERADE nf_nat_masquerade_ipv4 
iptable_nat nf_nat_ipv4 nf_nat nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack 
nf_conntrack ipt_REJECT nf_reject_ipv4 xt_tcpudp bridge stp llc ebtable_filter 
ebtables ip6table_filter ip6_tables iptable_filter binfmt_misc 
snd_hda_codec_hdmi snd_hda_codec_conexant snd_hda_codec_generic snd_hda_intel 
intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp snd_hda_codec 
snd_hda_core snd_hwdep snd_pcm kvm_intel snd_seq_midi kvm snd_seq_midi_event 
irqbypass crct10dif_pclmul crc32_pclmul ghash_clmulni_intel cryptd intel_cstate 
snd_rawmidi intel_rapl_perf arc4 uvcvideo videobuf2_vmalloc iwldvm 
videobuf2_memops videobuf2_v4l2 mac80211
  Sep 12 20:22:45 trinity kernel: [  155.491215]  videobuf2_core videodev 
joydev input_leds media iwlwifi serio_raw cfg80211 snd_seq snd_seq_device 
snd_timer thinkpad_acpi nvram snd mac_hid mei_me mei soundcore lpc_ich shpchp 
parport_pc ppdev lp parport ip_tables x_tables autofs4 xfs libcrc32c mmc_block 
i915 sdhci_pci uas usb_storage sdhci i2c_algo_bit drm_kms_helper psmouse 
syscopyarea ahci sysfillrect libahci sysimgblt e1000e fb_sys_fops drm ptp 
pps_core wmi video
  Sep 12 20:22:45 trinity kernel: [  155.491251] CPU: 0 PID: 203 Comm: 
kworker/u16:5 Not tainted 4.12.0-13-generic #14-Ubuntu
  Sep 12 20:22:45 trinity kernel: [  155.491253] Hardware name: LENOVO 
4290W1A/4290W1A, BIOS 8DET69WW (1.39 ) 07/18/2013
  Sep 12 20:22:45 trinity kernel: [  155.491292] Workqueue: events_unbound 
intel_atomic_commit_work [i915]
  Sep 12 20:22:45 trinity kernel: [  155.491295] task: 8842c14a8000 
task.stack: ae8f0217c000
  Sep 12 20:22:45 trinity kernel: [  155.491330] RIP: 
0010:intel_atomic_commit_tail+0x1010/0x1020 [i915]
  Sep 12 20:22:45 trinity kernel: [  155.491331] RSP: 0018:ae8f0217fd88 
EFLAGS: 00010282
  Sep 12 20:22:45 trinity kernel: [  155.491333] RAX: 001c RBX: 
 RCX: 
  Sep 12 20:22:45 trinity kernel: [  155.491334] RDX:  RSI: 
8842de20dcc8 RDI: 8842de20dcc8
  Sep 12 20:22:45 trinity kernel: [  155.491336] RBP: ae8f0217fe40 R08: 
0001 R09: 039a
  Sep 12 20:22:45 trinity kernel: [  155.491337] R10: ae8f0217fd88 R11: 
 R12: 2359
  Sep 12 20:22:45 trinity kernel: [  155.491338] R13: 8842c150 R14: 
8842c15e6000 R15: 0001
  Sep 12 20:22:45 trinity kernel: [  155.491340] FS:  () 
GS:8842de20() knlGS:
  Sep 12 20:22:45 trinity kernel: [  155.491342] CS:  0010 DS:  ES:  
CR0: 80050033
  Sep 12 20:22:45 trinity kernel: [  155.491343] CR2: 00c420921000 CR3: 
0003a0409000 CR4: 000406f0
  Sep 12 20:22:45 trinity kernel: [  155.491345] Call Trace:
  Sep 12 20:22:45 trinity kernel: [  155.491352]  ? wake_bit_function+0x60/0x60
  Sep 12 20:22:45 trinity kernel: [  155.491386]  
intel_atomic_commit_work+0x12/0x20 [i915]
  Sep 12 20:22:45 trinity kernel: [  155.491390]  process_one_work+0x1e7/0x410
  Sep 12 20:22:45 trinity kernel: [  155.491393]  worker_thread+0x4a/0x410
  Sep 12 20:22:45 trinity kernel: [  155.491396]  kthread+0x125/0x140
  Sep 12 20:22:45 trinity kernel: [  155.491398]  ?

[Kernel-packages] [Bug 1753424] [NEW] s390/crypto: Fix kernel crash on aes_s390 module remove

2018-03-05 Thread Launchpad Bug Tracker

You have been subscribed to a public bug:

Upstream patch to fix the aes_s390 kernel module remove crash,
introduced with kernel 4.15 rc1.

Here is the patch to fix the kernel crash on aes_s390 kernel module removal.
Please note that this patch is as of now not upstream available but in the s390 
pipe for the next merge window (and so may be visible upstream with the start 
of the 4.17 development kernels).

** Affects: linux (Ubuntu)
 Importance: Undecided
 Assignee: Skipper Bug Screeners (skipper-screen-team)
 Status: New


** Tags: architecture-s39064 bugnameltc-165332 severity-high 
targetmilestone-inin1804
-- 
s390/crypto: Fix kernel crash on aes_s390 module remove
https://bugs.launchpad.net/bugs/1753424
You received this bug notification because you are a member of Kernel Packages, 
which is subscribed to linux in Ubuntu.

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

[Kernel-packages] [Bug 1752236] Re: Ubuntu 18.04 - Performance: Radix page fault handler bug in KVM

I built a test kernel with the patch referenced in the description.  The test 
kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1752236

Can you test this kernel and see if it resolves this bug?

Note, to test this kernel, you need to install both the linux-image and
linux-image-extra .deb packages.

Thanks in advance!

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

Title:
  Ubuntu 18.04 - Performance: Radix page fault handler bug in KVM

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

Bug description:
  == Comment: #0 - JENIFER HOPPER  - 2018-02-27 17:25:59 ==
  +++ This bug was initially created as a clone of Bug #165215 +++

  ---Problem Description---
  Paul Mackerras has posted a fix to a Radix page fault handler bug in KVM:

  http://patchwork.ozlabs.org/patch/877033/
  " KVM: PPC: Book3S HV: Fix handling of large pages in radix page fault 
handler "

  This is critical for P9 KVM performance. Using an open source database 
workload, we saw an 11% throughput improvement with this patch when the guest 
was backed w/ 2MB hugepages. Without this patch, hugepage backing does not help 
performance compared to base page size. 
   
  ---uname output---
  18.04 lts
   
  Machine Type = 5104-22C 
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
Back guest w/ 2MB pages, run a throughput test and compare performance.
   
  Contact Information = jhop...@us.ibm.com

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

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

[Kernel-packages] [Bug 1716747] Re: High system load and mouse delays - pipe A vblank wait timed out

2018-03-05 Thread Jay Vosburgh

Joe,

I didn't try anything in between, I went from 4.13.0-16 to -36 and -36
started wigging out again so I backed down to -16.  I can try some
interim kernels next week when I don't need to do work on the laptop in
question.

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

Title:
  High system load and mouse delays - pipe A vblank wait timed out

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

Bug description:
  This issue has been observed on a Lenovo X220i laptop:

  1. Booting the laptop with artful's 4.12 kernel results in a very sluggish 
system performance (mouse pointer delays) and a high system load.
  2. /var/log/kern.log indicates a problem with the display driver (see below)
  3. The system works without any issues if the zesty kernel (4.10) is used 
instead.

  Ubuntu release: Artful Aardvark (development branch)
  Kernel package version: 4.12.0.13.14

  
  Sep 12 20:22:45 trinity kernel: [  155.491074] pipe A vblank wait timed out
  Sep 12 20:22:45 trinity kernel: [  155.491117] [ cut here 
]
  Sep 12 20:22:45 trinity kernel: [  155.491171] WARNING: CPU: 0 PID: 203 at 
/build/linux-cK2WUa/linux-4.12.0/drivers/gpu/drm/i915/intel_display.c:12636 
intel_atomic_commit_tail+0x1010/0x1020 [i915]
  Sep 12 20:22:45 trinity kernel: [  155.491172] Modules linked in: 
nf_conntrack_netlink nfnetlink xfrm_user xfrm_algo xt_addrtype br_netfilter 
aufs xt_CHECKSUM iptable_mangle ipt_MASQUERADE nf_nat_masquerade_ipv4 
iptable_nat nf_nat_ipv4 nf_nat nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack 
nf_conntrack ipt_REJECT nf_reject_ipv4 xt_tcpudp bridge stp llc ebtable_filter 
ebtables ip6table_filter ip6_tables iptable_filter binfmt_misc 
snd_hda_codec_hdmi snd_hda_codec_conexant snd_hda_codec_generic snd_hda_intel 
intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp snd_hda_codec 
snd_hda_core snd_hwdep snd_pcm kvm_intel snd_seq_midi kvm snd_seq_midi_event 
irqbypass crct10dif_pclmul crc32_pclmul ghash_clmulni_intel cryptd intel_cstate 
snd_rawmidi intel_rapl_perf arc4 uvcvideo videobuf2_vmalloc iwldvm 
videobuf2_memops videobuf2_v4l2 mac80211
  Sep 12 20:22:45 trinity kernel: [  155.491215]  videobuf2_core videodev 
joydev input_leds media iwlwifi serio_raw cfg80211 snd_seq snd_seq_device 
snd_timer thinkpad_acpi nvram snd mac_hid mei_me mei soundcore lpc_ich shpchp 
parport_pc ppdev lp parport ip_tables x_tables autofs4 xfs libcrc32c mmc_block 
i915 sdhci_pci uas usb_storage sdhci i2c_algo_bit drm_kms_helper psmouse 
syscopyarea ahci sysfillrect libahci sysimgblt e1000e fb_sys_fops drm ptp 
pps_core wmi video
  Sep 12 20:22:45 trinity kernel: [  155.491251] CPU: 0 PID: 203 Comm: 
kworker/u16:5 Not tainted 4.12.0-13-generic #14-Ubuntu
  Sep 12 20:22:45 trinity kernel: [  155.491253] Hardware name: LENOVO 
4290W1A/4290W1A, BIOS 8DET69WW (1.39 ) 07/18/2013
  Sep 12 20:22:45 trinity kernel: [  155.491292] Workqueue: events_unbound 
intel_atomic_commit_work [i915]
  Sep 12 20:22:45 trinity kernel: [  155.491295] task: 8842c14a8000 
task.stack: ae8f0217c000
  Sep 12 20:22:45 trinity kernel: [  155.491330] RIP: 
0010:intel_atomic_commit_tail+0x1010/0x1020 [i915]
  Sep 12 20:22:45 trinity kernel: [  155.491331] RSP: 0018:ae8f0217fd88 
EFLAGS: 00010282
  Sep 12 20:22:45 trinity kernel: [  155.491333] RAX: 001c RBX: 
 RCX: 
  Sep 12 20:22:45 trinity kernel: [  155.491334] RDX:  RSI: 
8842de20dcc8 RDI: 8842de20dcc8
  Sep 12 20:22:45 trinity kernel: [  155.491336] RBP: ae8f0217fe40 R08: 
0001 R09: 039a
  Sep 12 20:22:45 trinity kernel: [  155.491337] R10: ae8f0217fd88 R11: 
 R12: 2359
  Sep 12 20:22:45 trinity kernel: [  155.491338] R13: 8842c150 R14: 
8842c15e6000 R15: 0001
  Sep 12 20:22:45 trinity kernel: [  155.491340] FS:  () 
GS:8842de20() knlGS:
  Sep 12 20:22:45 trinity kernel: [  155.491342] CS:  0010 DS:  ES:  
CR0: 80050033
  Sep 12 20:22:45 trinity kernel: [  155.491343] CR2: 00c420921000 CR3: 
0003a0409000 CR4: 000406f0
  Sep 12 20:22:45 trinity kernel: [  155.491345] Call Trace:
  Sep 12 20:22:45 trinity kernel: [  155.491352]  ? wake_bit_function+0x60/0x60
  Sep 12 20:22:45 trinity kernel: [  155.491386]  
intel_atomic_commit_work+0x12/0x20 [i915]
  Sep 12 20:22:45 trinity kernel: [  155.491390]  process_one_work+0x1e7/0x410
  Sep 12 20:22:45 trinity kernel: [  155.491393]  worker_thread+0x4a/0x410
  Sep 12 20:22:45 trinity kernel: [  155.491396]  kthread+0x125/0x140
  Sep 12 20:22:45 trinity kernel: [  155.491398]  ? process_one_work+0x410/0x410
  Sep 12 20:22:45 trinity kernel: [  155.491400]  ? 
kthread_create_on_node+0x70/0x70
  Sep 12 20:22:45 trinity kernel:

[Kernel-packages] [Bug 1749040] Re: KPTI support for arm64 systems

2018-03-05 Thread Paolo Pisati

Is there a way for me to manually run disk/disk_stress_ng_dm-1?

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

Title:
  KPTI support for arm64 systems

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

Bug description:
  While regression testing the current linux-hwe proposed kernel
  (4.13.0-33.36~16.04.1), I found that it fails to boot on a Cavium
  ThunderX CRB. I've rebooted twice since upgrading from the current
  -updates kernel, and it's failed to boot both times, with different
  failure modes.

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

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

[Kernel-packages] [Bug 1753428] [NEW] nobp enable msg during boot

Public bug reported:

Description will follow

** Affects: linux (Ubuntu)
 Importance: Undecided
 Assignee: Skipper Bug Screeners (skipper-screen-team)
 Status: New


** Tags: architecture-s39064 bugnameltc-165232 severity-high 
targetmilestone-inin1604

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

** Changed in: ubuntu
 Assignee: (unassigned) => Skipper Bug Screeners (skipper-screen-team)

** Package changed: ubuntu => linux (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/1753428

Title:
  nobp enable msg during boot

Status in linux package in Ubuntu:
  New

Bug description:
  Description will follow

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

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

[Kernel-packages] [Bug 1753438] [NEW] Redpine: Sometimes Wi-Fi connection shows "unavailable" after resume from WoWLAN S4. WLAN can be recover after reboot or reloading WIFI driver.

Public bug reported:

Following are steps to reproduce the issue:

1. Ensure WoWLAN is enabled in BIOS.
2. Initiate connection to an AP (using nmcli)
3. Configure the device for WoWLAN, run the command:
$ sudo iw phy phy0 wowlan enable magic-packet
4. Enter S4 (using hibernate)
5. From another computer on the same network run the following command:
$ wakeonlan {mac}
6. Check network states and WIFI shows "Unavailable"

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

** Summary changed:

- Sometimes Wi-Fi connection shows "unavailable" after resume from WoWLAN S4. 
WLAN can be recover after reboot or reloading WIFI driver.
+ Redpine: Sometimes Wi-Fi connection shows "unavailable" after resume from 
WoWLAN S4. WLAN can be recover after reboot or reloading WIFI driver.

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

Title:
  Redpine: Sometimes Wi-Fi connection shows "unavailable" after resume
  from WoWLAN S4. WLAN can be recover after reboot or reloading WIFI
  driver.

Status in linux package in Ubuntu:
  New

Bug description:
  Following are steps to reproduce the issue:

  1. Ensure WoWLAN is enabled in BIOS.
  2. Initiate connection to an AP (using nmcli)
  3. Configure the device for WoWLAN, run the command:
  $ sudo iw phy phy0 wowlan enable magic-packet
  4. Enter S4 (using hibernate)
  5. From another computer on the same network run the following command:
  $ wakeonlan {mac}
  6. Check network states and WIFI shows "Unavailable"

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

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

[Kernel-packages] [Bug 1753439] Re: Redpine: BLE scanning for nearby beacons per second is too low and result high loss rate.

SRU Justification
=

[Impact]
Less beacons were found in BLE scanning with RS9113 chipset.


[Fix]
BLE Scanning is happening for less scan window, which is causing this issue. 
Scan window value is adjusted (increase)dynamically in firmware when there is 
no activity on WiFi/BT. Along with this fix i firmware, we have added deep 
sleep feature in driver. Driver will put chip in sleep state when there is not 
activity.

[Test Case]
Conducted tests to confirm BLE scanning results are improved with the driver 
and firmware changes. Also, ran suspend resume s3, s4 and s5 stress tests to 
ensure it passed with newly added sleep changes

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

Title:
  Redpine: BLE scanning for nearby beacons per second is too low and
  result high loss rate.

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Steps to replicate the issue:

  1. Power on the BT device, then change the terminal by "Ctil+F1" or open 
another putty to ssh SUT.
  2.Use command below to discover BLE device.
  $ sudo stdbuf -i0-o0 -e0 /snap/bluez/current/usr/bin/hcitool lescan 
--duplicates --passive | perl -nle 'print scalar(localtime), " ",$_'
  3. log as attachment.

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

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

[Kernel-packages] [Bug 1741081] Re: zfs-import-cache.service fails on startup

2018-03-05 Thread Colin Ian King

Yes, please reject the artful SRU

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

Title:
  zfs-import-cache.service fails on startup

Status in zfs-linux package in Ubuntu:
  Fix Released
Status in zfs-linux source package in Artful:
  In Progress
Status in zfs-linux source package in Bionic:
  Fix Released

Bug description:
  == SRU Request, Artful ==

  Enable ZFS module to be loaded without the broken ubuntu-load-zfs-
  unconditionally.patch.

  == Fix ==

  Add a new zfs-load-module.service script that modprobes the ZFS module
  and remove any hard coded module loading from zfs-import-cache.service
  & zfs-import-scan.service and make these latter scripts require the
  new zfs-load-module.service script.  Also remove the now defunct
  ubuntu-load-zfs-unconditionally.patch as this will no longer be
  required.

  == Testcase ==

  On a clean VM, install with the fixed package, zfs should load
  automatically.

  == Regression potential ==

  ZFS module may not load if the changes are broken. However, testing
  proves this not to be the case.

  

  I just noticed on my test VM of artful that zfs-import-cache.service
  does not have a ConditionPathExists=/etc/zfs/zpool.cache. Because of
  that, it fails on startup, since the cache file does not exist.

  This line is being deleted by 
debian/patches/ubuntu-load-zfs-unconditionally.patch. This patch seems to exist 
per:
  https://bugs.launchpad.net/ubuntu/+source/lxd/+bug/1672749

  This patch still exists in bionic, so I assume it will be similarly
  broken.

  If the goal of the patch is to load the module (and only that), I
  think it should create a third unit instead:

  zfs-load-module.service
   ^^ runs modprobe zfs

  zfs-import-cache.service & zfs-import-scan.service
    ^^ per upstream minus modprobe plus Requires=zfs-load-module.service

  I have tested this manually and it works. I can submit a package patch
  if this is the desired solution.

  Interestingly, before this change, zfs-import-scan.service wasn't
  starting. If started manually, it worked. I had to give it a
  `systemctl enable zfs-import-scan.service` to create the Wants
  symlinks. Looking at the zfsutils-linux.postinst, I see the correct
  boilerplate from dh_systemd, so I'm not sure why this wasn't already
  done. Can anyone confirm or deny whether zfs-import-scan.service is
  enabled out-of-the-box on their system?

  Is the zfs-import-scan.service not starting actually the cause of the
  original bug? The design is that *either* zfs-import-cache.service or
  zfs-import-scan.service starts. They both call modprobe zfs.

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

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

[Kernel-packages] [Bug 1577140] Re: Wifi Ralink R3290 disabled by default in ubuntu 16.04

2018-03-05 Thread Shankey

@marian , @Kai-Heng Feng - I have discovered a temporary workaround. All
you have to do is to install old kernel 3.19 in Ubuntu and boot from
it(after clean shut-down). Because ubuntu r3290 pci had worked perfectly
on kernel 3.19. If you want to boot ubuntu from outdated or unsupported
kernel you can simply do that by following link. Please make sure that
you boot on same 3.19 if you boot on newer one you will experience same
issue. In order to fix it you have to again shutdown and make a boot
from same kernel.

For more information please visit this link
https://webwiks.com/techcorner/get-ralink-r3290-work-linux-distribution/

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

Title:
  Wifi Ralink R3290 disabled by default in ubuntu 16.04

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have my personal laptop and it contains PCI Ralink r3290 wifi
  adaptor with bluetooth and when i have installed the fresh version of
  Ubuntu 16.04x64 it doesn’t work at all on boot up. The wifi is
  disabled by default and the it doesn’t activates even by pressing the
  key and when i go the network settings airplane mode is also enabled
  and when i try to disable airplane mode it switches back on. I dont
  know whats going wrong. Earlier my wifi works on ubuntu 15.04. I have
  tried almost every solution and none works in the latest LTS release.

  Please help I am unable to use internet in ubuntu

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-21-generic 4.4.0-21.37 [modified: 
boot/vmlinuz-4.4.0-21-generic]
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  shankey1536 F pulseaudio
   /dev/snd/controlC1:  shankey1536 F pulseaudio
  CurrentDesktop: Unity
  Date: Sun May  1 17:02:12 2016
  HibernationDevice: RESUME=UUID=9fdda691-a6ae-4494-99e3-b76fde1f33a6
  InstallationDate: Installed on 2016-04-24 (7 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  Lsusb:
   Bus 001 Device 003: ID 05c8:036e Cheng Uei Precision Industry Co., Ltd 
(Foxlink) Webcam
   Bus 001 Device 002: ID 8087:8000 Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Hewlett-Packard Compaq 15 Notebook PC
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic 
root=UUID=609ae58a-a43f-4f7b-9a61-e21d3caf457a ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-21-generic N/A
   linux-backports-modules-4.4.0-21-generic  N/A
   linux-firmware1.157
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/26/2015
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.39
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 2211
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 86.52
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.39:bd05/26/2015:svnHewlett-Packard:pnCompaq15NotebookPC:pvr0991100600087:rvnHewlett-Packard:rn2211:rvr86.52:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.name: Compaq 15 Notebook PC
  dmi.product.version: 0991100600087
  dmi.sys.vendor: Hewlett-Packard

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

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

[Kernel-packages] [Bug 1734130] Re: [18.04 FEAT] Add kvm_stat from kernel tree

That's currently in discussion ...

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

Title:
  [18.04 FEAT] Add kvm_stat from kernel tree

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

Bug description:
  Improves RAS characterics of systems running KVM by providing kvm_stat script:
  https://github.com/torvalds/linux/tree/master/tools/kvm/kvm_stat

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

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

[Kernel-packages] [Bug 1753191] Re: Touchpad not working after installing Ubuntu 16.04 LTS

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.16 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.16-rc4


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

Title:
  Touchpad not working after installing Ubuntu 16.04 LTS

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  After installing Ubuntu 16.04 on my thinkpad x220t, my touchpad
  doesn't work at all.

  I do not see a Synaptics touchpad under cat /proc/bus/input/devices

  I've attached my output from dmesg, and I'll attach my output from
  devices, and my Xorg log in the comments

  Thank you in advance for the help
  --- 
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  demroz 1814 F pulseaudio
  CurrentDesktop: X-Cinnamon
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=09061c6d-7452-46e9-8539-5c6c5078ef2a
  InstallationDate: Installed on 2018-03-04 (0 days ago)
  InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 
(20180228)
  MachineType: LENOVO 42983RU
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-36-generic 
root=UUID=70a7bb64-bb83-4ab9-98a4-d3545d1e66ce ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.13.0-36.40~16.04.1-generic 4.13.13
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-36-generic N/A
   linux-backports-modules-4.13.0-36-generic  N/A
   linux-firmware 1.157.17
  Tags:  xenial
  Uname: Linux 4.13.0-36-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/12/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 8DET73WW (1.43 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 42983RU
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr8DET73WW(1.43):bd10/12/2016:svnLENOVO:pn42983RU:pvrThinkPadX220Tablet:rvnLENOVO:rn42983RU:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad X220 Tablet
  dmi.product.name: 42983RU
  dmi.product.version: ThinkPad X220 Tablet
  dmi.sys.vendor: LENOVO
  --- 
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  demroz 1814 F pulseaudio
  CurrentDesktop: X-Cinnamon
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=09061c6d-7452-46e9-8539-5c6c5078ef2a
  InstallationDate: Installed on 2018-03-04 (0 days ago)
  InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 
(20180228)
  MachineType: LENOVO 42983RU
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-36-generic 
root=UUID=70a7bb64-bb83-4ab9-98a4-d3545d1e66ce ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.13.0-36.40~16.04.1-generic 4.13.13
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-36-generic N/A
   linux-backports-modules-4.13.0-36-generic  N/A
   linux-firmware 1.157.17
  Tags:  xenial
  Uname: Linux 4.13.0-36-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/12/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 8DET73WW (1.43 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 42983RU
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr8DET73WW(1.43):bd10/12/2016:svnLENOVO:pn42983RU:pvrThinkPadX220Tablet:rvnLENOVO:rn42983RU:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad X220 Tablet
  dmi.product.name: 42983RU
  dmi.product.version: ThinkPad X220 Tablet
  dmi.sys.vendor: LENOVO

To

[Kernel-packages] [Bug 1753010] Re: after recent updates playing youtube videos in firefox causes sometimes freezing of the system

2018-03-05 Thread Kamil

It will take from me several days to find some free time to understand
how to test kernels safely on working machine. After that it will take
up to several days to be sure that bug is resolved by such fix. So, you
should expect from me report by the next Monday or so.

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

Title:
  after recent updates playing youtube videos in firefox causes
  sometimes freezing of the system

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  After recent updates that fixed the bug
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1742675 on my
  computer the following different bug has appeared. Playing Youtube
  music videos (static picture + music, length 40-70 minutes) in Firefox
  (as background for other activities on computer) causes sometimes
  (rather often, up to several times per day) freezing of the system.
  And only restart through reset button can help.

  Initially I though that it is related to different Javascript-related
  tasks (manipulating with complex widgets in Chromium, running heavy
  gulp tasks through yarn) but it looks they are not the reason (or at
  least not the main reason). Because right now I have seen the problem
  when keyboard/mouse was not touched at all.

  That's why I think this information is rather enough; and I decided to post 
this bug.
  --- 
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  kamil  2021 F pulseaudio
   /dev/snd/controlC1:  kamil  2021 F pulseaudio
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=5b5ffc28-8999-4ad7-9ff3-f3298c4f28c2
  InstallationDate: Installed on 2017-06-23 (252 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release i386 
(20170215.2)
  MachineType: Packard Bell Easynote ENTE70BH
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-36-generic 
root=UUID=557e3c22-0c8c-44b3-a8f6-5446013327ad ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.13.0-36.40~16.04.1-generic 4.13.13
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-36-generic N/A
   linux-backports-modules-4.13.0-36-generic  N/A
   linux-firmware 1.157.17
  Tags:  xenial
  Uname: Linux 4.13.0-36-generic i686
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 08/08/2016
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.05
  dmi.board.name: Easynote ENTE70BH
  dmi.board.vendor: Packard Bell
  dmi.board.version: V1.05
  dmi.chassis.type: 10
  dmi.chassis.vendor: Packard Bell
  dmi.chassis.version: V1.05
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.05:bd08/08/2016:svnPackardBell:pnEasynoteENTE70BH:pvrV1.05:rvnPackardBell:rnEasynoteENTE70BH:rvrV1.05:cvnPackardBell:ct10:cvrV1.05:
  dmi.product.family: BDW
  dmi.product.name: Easynote ENTE70BH
  dmi.product.version: V1.05
  dmi.sys.vendor: Packard Bell

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

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

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

--- Comment From mu...@br.ibm.com 2018-02-26 13:57 EDT---
I tried reproducing this issue in a Firestone system our team owns with Ubuntu 
18.04 and I couldn't reproduce the issue.

root@ltc-fire1:~# cat /etc/lsb-release
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=18.04
DISTRIB_CODENAME=bionic
DISTRIB_DESCRIPTION="Ubuntu Bionic Beaver (development branch)"

root@ltc-fire1:~# uname -r
4.15.0-10-generic

root@ltc-fire1:~# ethtool -i enP1p1s0f0 | grep "driver\|firmware\|bus-info"
driver: tg3
firmware-version: 5719-v1.38i
bus-info: 0001:01:00.0

root@ltc-fire1:~# lspci -vmmnn -s 0001:01:00.0
Slot:   0001:01:00.0
Class:  Ethernet controller [0200]
Vendor: Broadcom Limited [14e4]
Device: NetXtreme BCM5719 Gigabit Ethernet PCIe [1657]
SVendor:IBM [1014]
SDevice:NetXtreme BCM5719 Gigabit Ethernet PCIe (FC 5260/5899 4-port 1 
GbE Adapter for Power) [0420]
Rev:01
NUMANode:   0

Here is a snippet of the kdump attempt to reproduce the issue:

[  129.602468] kdump-tools[1599]: Starting kdump-tools:  * sending makedumpfile 
-c -d 31 -F /proc/vmcore to root@9.40.194.212 : 
/var/crash/9.40.195.135-201802261141/dump-incomplete
[  129.719688] kdump-tools[1599]: The kernel version is not supported.
[  129.720035] kdump-tools[1599]: The makedumpfile operation may be incomplete.
Copying data  : [100.0 %] \   eta: 
0s
[  144.173303] kdump-tools[1599]: The dumpfile is saved to STDOUT.
[  144.173531] kdump-tools[1599]: makedumpfile Completed.
[  144.184688] kdump-tools[1599]: 533781+259 records in
[  144.184975] kdump-tools[1599]: 533918+1 records out
[  144.185223] kdump-tools[1599]: 273366297 bytes (273 MB, 261 MiB) copied, 
14.3426 s, 19.1 MB/s
[  144.419378] kdump-tools[1599]:  * kdump-tools: saved vmcore in 
root@9.40.194.212:/var/crash/9.40.195.135-201802261141
[  144.439183] kdump-tools[1599]:  * running makedumpfile --dump-dmesg 
/proc/vmcore /tmp/dmesg.201802261141
[  144.445902] kdump-tools[1599]: The kernel version is not supported.
[  144.446266] kdump-tools[1599]: The makedumpfile operation may be incomplete.
[  144.446557] kdump-tools[1599]: The dmesg log is saved to 
/tmp/dmesg.201802261141.
[  144.446844] kdump-tools[1599]: makedumpfile Completed.
[  144.717033] kdump-tools[1599]:  * kdump-tools: saved dmesg content in 
root@9.40.194.212:/var/crash/9.40.195.135-201802261141
[  144.718981] kdump-tools[1599]: Mon, 26 Feb 2018 11:42:11 -0700
[  144.825931] kdump-tools[1599]: Rebooting.
[  144.950195] reboot: Restarting system

Both dmesg and dump file were transferred to the peer under /var/crash/

root@ltc-zz4-lp2:~# ls /var/crash/9.40.195.135-201802261141
dmesg.201802261141  dump.201802261141

Pavithra, if you still have the system, could you attempt to reproduce
this issue in your environment?

--- Comment From pavra...@in.ibm.com 2018-02-28 01:46 EDT---
Issue is not observed on same machine with 17.10 and 18.04 on same machine.

we can close the bug.

18.04


Starting Kernel crash dump capture service...
[   29.664816] kdump-tools[1255]: Starting kdump-tools:  * sending makedumpfile 
-c -d 31 -F /proc/vmcore to root@9.40.192.198 : 
/var/crash/9.47.70.29-201802280145/dump-incomplete
[   29.732510] kdump-tools[1255]: The kernel version is not supported.
[   29.732618] kdump-tools[1255]: The makedumpfile operation may be incomplete.
Copying data  : [100.0 %] /   eta: 
0s
[   41.966840] kdump-tools[1255]: The dumpfile is saved to STDOUT.
[   41.966939] kdump-tools[1255]: makedumpfile Completed.
[   42.112371] kdump-tools[1255]: 247581+447 records in
[   42.112456] kdump-tools[1255]: 247802+1 records out
[   42.112557] kdump-tools[1255]: 126874775 bytes (127 MB) copied, 11.3072 s, 
11.2 MB/s
[   43.275938] kdump-tools[1255]:  * kdump-tools: saved vmcore in 
root@9.40.192.198:/var/crash/9.47.70.29-201802280145
[   43.295066] kdump-tools[1255]:  * running makedumpfile --dump-dmesg 
/proc/vmcore /tmp/dmesg.201802280145
[   43.302493] kdump-tools[1255]: The kernel version is not supported.
[   43.302611] kdump-tools[1255]: The makedumpfile operation may be incomplete.
[   43.302694] kdump-tools[1255]: The dmesg log is saved to 
/tmp/dmesg.201802280145.
[   43.302804] kdump-tools[1255]: makedumpfile Completed.
[   44.711325] kdump-tools[1255]:  * kdump-tools: saved dmesg content in 
root@9.40.192.198:/var/crash/9.47.70.29-201802280145
[   44.713050] kdump-tools[1255]: Wed, 28 Feb 2018 01:45:29 -0500
[   44.840303] kdump-tools[1255]: Rebooting.

17.10
==

[root@lep8a crash]# ls
9.47.70.29-201802280052
[root@lep8a crash]# cd 9.47.70.29-201802280052
[root@lep8a 9.47.70.29-201802280052]# ls
dmesg.201802280052  dump.201802280052
[root@lep8a 9.47.70.29-201802280052]# tail dmesg.201802280052
[ 1133.042160] Instruction dump:
[ 1133.042192] 4bfff9f1 4bfffe50 3c4c00e6 384228e0 7c0802a6 6000 3921 
3d42001d
[ 1133.042410] 394adb30 912a 7c0004ac 3940 <992a> 4e800020 3c4c00e6 
384228b0
[

[Kernel-packages] [Bug 1753371] Re: Ubuntu 18.04 - Kernel crash on nvme subsystem-reset /dev/nvme0 (Bolt / NVMe)

I built a test kernel with the patch mentioned in the description.  The test 
kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1753371

Can you test this kernel and see if it resolves this bug?

Note, to test this kernel, you need to install both the linux-image and
linux-image-extra .deb packages.

Thanks in advance!

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

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

** Changed in: linux (Ubuntu)
 Assignee: Ubuntu on IBM Power Systems Bug Triage (ubuntu-power-triage) => 
Joseph Salisbury (jsalisbury)

** Also affects: linux (Ubuntu Bionic)
   Importance: Critical
 Assignee: Joseph Salisbury (jsalisbury)
   Status: Triaged

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

Title:
  Ubuntu 18.04 - Kernel crash on nvme subsystem-reset /dev/nvme0 (Bolt /
  NVMe)

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

Bug description:
  == Comment: #1 - NAVEED A. UPPINANGADY SALIH  -
  2018-02-25 23:45:13 ==

  
  == Comment: #6 - Wen Xiong  - 2018-02-27 10:41:23 ==
  hi Naveed,

  nvme subsystem-reset calls EEH recovery path. Is EEH recovery working
  with Bolt on this machine?

  Thanks,
  Wendy

  == Comment: #11 - Wen Xiong  - 2018-03-02 16:03:46 ==
  The following patch should fix the issue.

  http://lists.infradead.org/pipermail/linux-
  nvme/2018-February/015745.html

  It should be accepted into community soon. Keith has agreed to queue
  up for 4.16.

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

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

[Kernel-packages] [Bug 1753371] Re: Ubuntu 18.04 - Kernel crash on nvme subsystem-reset /dev/nvme0 (Bolt / NVMe)

** Changed in: ubuntu-power-systems
   Status: New => Triaged

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

Title:
  Ubuntu 18.04 - Kernel crash on nvme subsystem-reset /dev/nvme0 (Bolt /
  NVMe)

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

Bug description:
  == Comment: #1 - NAVEED A. UPPINANGADY SALIH  -
  2018-02-25 23:45:13 ==

  
  == Comment: #6 - Wen Xiong  - 2018-02-27 10:41:23 ==
  hi Naveed,

  nvme subsystem-reset calls EEH recovery path. Is EEH recovery working
  with Bolt on this machine?

  Thanks,
  Wendy

  == Comment: #11 - Wen Xiong  - 2018-03-02 16:03:46 ==
  The following patch should fix the issue.

  http://lists.infradead.org/pipermail/linux-
  nvme/2018-February/015745.html

  It should be accepted into community soon. Keith has agreed to queue
  up for 4.16.

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

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

[Kernel-packages] [Bug 1752026] Re: Ubuntu18.04:POWER9:DD2.2 - Unable to start a KVM guest with default machine type(pseries-bionic) complaining "KVM implementation does not support Transactional Memo

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

Title:
  Ubuntu18.04:POWER9:DD2.2 - Unable to start a KVM guest with default
  machine type(pseries-bionic) complaining "KVM implementation does not
  support Transactional Memory, try cap-htm=off" (kvm)

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

Bug description:
  == Comment: #0 - Satheesh Rajendran  - 2018-02-23 
08:31:06 ==
  ---Problem Description---
  libvirt unable to start a KVM guest complaining about cap-htm machine 
property to be off

  Host Env:
  # lscpu
  Architecture:ppc64le
  Byte Order:  Little Endian
  CPU(s):  160
  On-line CPU(s) list: 0-159
  Thread(s) per core:  4
  Core(s) per socket:  20
  Socket(s):   2
  NUMA node(s):2
  Model:   2.2 (pvr 004e 1202)
  Model name:  POWER9 (raw), altivec supported
  CPU max MHz: 3800.
  CPU min MHz: 2166.
  L1d cache:   32K
  L1i cache:   32K
  L2 cache:512K
  L3 cache:10240K
  NUMA node0 CPU(s):   0-79
  NUMA node8 CPU(s):   80-159

  ii  qemu-kvm  1:2.11+dfsg-1ubuntu2
  ppc64el  QEMU Full virtualization on x86 hardware

  ii  libvirt-bin   4.0.0-1ubuntu3
  ppc64el  programs for the libvirt library

  # lsmcode
  Version of System Firmware : 
   Product Name  : OpenPOWER Firmware
   Product Version   : open-power-SUPERMICRO-P9DSU-V1.03-20180205-imp
   Product Extra :  occ-577915f
   Product Extra :  skiboot-v5.9-240-g081882690163-pcbedce4
   Product Extra :  petitboot-v1.6.6-p019c87e
   Product Extra :  sbe-095e608
   Product Extra :  machine-xml-fb5f933
   Product Extra :  hostboot-9bfb201
   Product Extra :  linux-4.14.13-openpower1-p78d7eee

  
   
  Contact Information = sathe...@in.ibm.com 
   
  ---uname output---
  4.15.0-10-generic
   
  Machine Type = power9 boston 2.2 (pvr 004e 1202) 
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
   1. Boot a guest from libvirt with default pseries machine type or 
pseries-bionic

  /usr/bin/virt-install --connect=qemu:///system --hvm --accelerate --name 
'virt-tests-vm1' --machine pseries --memory=32768 
--vcpu=32,sockets=1,cores=32,threads=1 --import --nographics --serial pty 
--memballoon model=virtio --controller type=scsi,model=virtio-scsi --disk 
path=/var/lib/libvirt/images/workspace/runAvocadoFVTTest/avocado-fvt-wrapper/data/avocado-vt/images/ubuntu-18.04-ppc64le.qcow2,bus=scsi,size=10,format=qcow2
 --network=bridge=virbr0,model=virtio,mac=52:54:00:77:78:79 --noautoconsole
  WARNING  No operating system detected, VM performance may suffer. Specify an 
OS with --os-variant for optimal results.

  Starting install...
  ERRORinternal error: process exited while connecting to monitor: 
,id=scsi0-0-0-0,bootindex=1 -netdev tap,fd=24,id=hostnet0,vhost=on,vhostfd=26 
-device 
virtio-net-pci,netdev=hostnet0,id=net0,mac=52:54:00:77:78:79,bus=pci.0,addr=0x1 
-chardev pty,id=charserial0 -device 
spapr-vty,chardev=charserial0,id=serial0,reg=0x3000 -device 
virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x4 -msg timestamp=on
  2018-02-23T14:21:11.081809Z qemu-system-ppc64: KVM implementation does not 
support Transactional Memory, try cap-htm=off
  Domain installation does not appear to have been successful.
  If it was, you can restart your domain by running:
virsh --connect qemu:///system start virt-tests-vm1
  otherwise, please restart your installation.

  2. Fails to boot..

  Note: if we specify machine type as pseries=2.12 it boots fine like
  below

  /usr/bin/virt-install --connect=qemu:///system --hvm --accelerate --name 
'virt-tests-vm1' --machine pseries-2.12 --memory=32768 
--vcpu=32,sockets=1,cores=32,threads=1 --import --nographics --serial pty 
--memballoon model=virtio --controller type=scsi,model=virtio-scsi --disk 
path=/var/lib/libvirt/images/workspace/runAvocadoFVTTest/avocado-fvt-wrapper/data/avocado-vt/images/ubuntu-18.04-ppc64le.qcow2,bus=scsi,size=10,format=qcow2
 --network=bridge=virbr0,model=virtio,mac=52:54:00:77:78:79 --noautoconsole
  WARNING  No operating system detected, VM performance may suffer. Specify an 
OS with --os-variant for optimal results.

  qemu-cmd line:

  libvirt+   4283  1 99 09:26 ?00:00:38 qemu-system-ppc64
  -enable-kvm -name guest=virt-tests-vm1,debug-threads=on -S -object
  secret,id=masterKey0,format=raw,file=/var/lib/libvirt/qemu/domain-4
  -virt-tests-vm1/master-key.aes -machine pseries-2.12,accel=kvm,usb=off
  ,dump-guest-core=off -m 32768

[Kernel-packages] [Bug 1752026] Re: Ubuntu18.04:POWER9:DD2.2 - Unable to start a KVM guest with default machine type(pseries-bionic) complaining "KVM implementation does not support Transactional Memo

** Changed in: ubuntu-power-systems
 Assignee: (unassigned) => Canonical Server Team (canonical-server)

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

Title:
  Ubuntu18.04:POWER9:DD2.2 - Unable to start a KVM guest with default
  machine type(pseries-bionic) complaining "KVM implementation does not
  support Transactional Memory, try cap-htm=off" (kvm)

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

Bug description:
  == Comment: #0 - Satheesh Rajendran  - 2018-02-23 
08:31:06 ==
  ---Problem Description---
  libvirt unable to start a KVM guest complaining about cap-htm machine 
property to be off

  Host Env:
  # lscpu
  Architecture:ppc64le
  Byte Order:  Little Endian
  CPU(s):  160
  On-line CPU(s) list: 0-159
  Thread(s) per core:  4
  Core(s) per socket:  20
  Socket(s):   2
  NUMA node(s):2
  Model:   2.2 (pvr 004e 1202)
  Model name:  POWER9 (raw), altivec supported
  CPU max MHz: 3800.
  CPU min MHz: 2166.
  L1d cache:   32K
  L1i cache:   32K
  L2 cache:512K
  L3 cache:10240K
  NUMA node0 CPU(s):   0-79
  NUMA node8 CPU(s):   80-159

  ii  qemu-kvm  1:2.11+dfsg-1ubuntu2
  ppc64el  QEMU Full virtualization on x86 hardware

  ii  libvirt-bin   4.0.0-1ubuntu3
  ppc64el  programs for the libvirt library

  # lsmcode
  Version of System Firmware : 
   Product Name  : OpenPOWER Firmware
   Product Version   : open-power-SUPERMICRO-P9DSU-V1.03-20180205-imp
   Product Extra :  occ-577915f
   Product Extra :  skiboot-v5.9-240-g081882690163-pcbedce4
   Product Extra :  petitboot-v1.6.6-p019c87e
   Product Extra :  sbe-095e608
   Product Extra :  machine-xml-fb5f933
   Product Extra :  hostboot-9bfb201
   Product Extra :  linux-4.14.13-openpower1-p78d7eee

  
   
  Contact Information = sathe...@in.ibm.com 
   
  ---uname output---
  4.15.0-10-generic
   
  Machine Type = power9 boston 2.2 (pvr 004e 1202) 
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
   1. Boot a guest from libvirt with default pseries machine type or 
pseries-bionic

  /usr/bin/virt-install --connect=qemu:///system --hvm --accelerate --name 
'virt-tests-vm1' --machine pseries --memory=32768 
--vcpu=32,sockets=1,cores=32,threads=1 --import --nographics --serial pty 
--memballoon model=virtio --controller type=scsi,model=virtio-scsi --disk 
path=/var/lib/libvirt/images/workspace/runAvocadoFVTTest/avocado-fvt-wrapper/data/avocado-vt/images/ubuntu-18.04-ppc64le.qcow2,bus=scsi,size=10,format=qcow2
 --network=bridge=virbr0,model=virtio,mac=52:54:00:77:78:79 --noautoconsole
  WARNING  No operating system detected, VM performance may suffer. Specify an 
OS with --os-variant for optimal results.

  Starting install...
  ERRORinternal error: process exited while connecting to monitor: 
,id=scsi0-0-0-0,bootindex=1 -netdev tap,fd=24,id=hostnet0,vhost=on,vhostfd=26 
-device 
virtio-net-pci,netdev=hostnet0,id=net0,mac=52:54:00:77:78:79,bus=pci.0,addr=0x1 
-chardev pty,id=charserial0 -device 
spapr-vty,chardev=charserial0,id=serial0,reg=0x3000 -device 
virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x4 -msg timestamp=on
  2018-02-23T14:21:11.081809Z qemu-system-ppc64: KVM implementation does not 
support Transactional Memory, try cap-htm=off
  Domain installation does not appear to have been successful.
  If it was, you can restart your domain by running:
virsh --connect qemu:///system start virt-tests-vm1
  otherwise, please restart your installation.

  2. Fails to boot..

  Note: if we specify machine type as pseries=2.12 it boots fine like
  below

  /usr/bin/virt-install --connect=qemu:///system --hvm --accelerate --name 
'virt-tests-vm1' --machine pseries-2.12 --memory=32768 
--vcpu=32,sockets=1,cores=32,threads=1 --import --nographics --serial pty 
--memballoon model=virtio --controller type=scsi,model=virtio-scsi --disk 
path=/var/lib/libvirt/images/workspace/runAvocadoFVTTest/avocado-fvt-wrapper/data/avocado-vt/images/ubuntu-18.04-ppc64le.qcow2,bus=scsi,size=10,format=qcow2
 --network=bridge=virbr0,model=virtio,mac=52:54:00:77:78:79 --noautoconsole
  WARNING  No operating system detected, VM performance may suffer. Specify an 
OS with --os-variant for optimal results.

  qemu-cmd line:

  libvirt+   4283  1 99 09:26 ?00:00:38 qemu-system-ppc64
  -enable-kvm -name guest=virt-tests-vm1,debug-threads=on -S -object
  secret,id=masterKey0,format=raw,file=/var/lib/libvirt/qemu/domain-4
  -virt-tests-vm1/master-key.aes -machine

[Kernel-packages] [Bug 1752026] Re: Ubuntu18.04:POWER9:DD2.2 - Unable to start a KVM guest with default machine type(pseries-bionic) complaining "KVM implementation does not support Transactional Memo

** Changed in: qemu (Ubuntu)
 Assignee: Ubuntu on IBM Power Systems Bug Triage (ubuntu-power-triage) => 
Canonical Server Team (canonical-server)

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

Title:
  Ubuntu18.04:POWER9:DD2.2 - Unable to start a KVM guest with default
  machine type(pseries-bionic) complaining "KVM implementation does not
  support Transactional Memory, try cap-htm=off" (kvm)

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

Bug description:
  == Comment: #0 - Satheesh Rajendran  - 2018-02-23 
08:31:06 ==
  ---Problem Description---
  libvirt unable to start a KVM guest complaining about cap-htm machine 
property to be off

  Host Env:
  # lscpu
  Architecture:ppc64le
  Byte Order:  Little Endian
  CPU(s):  160
  On-line CPU(s) list: 0-159
  Thread(s) per core:  4
  Core(s) per socket:  20
  Socket(s):   2
  NUMA node(s):2
  Model:   2.2 (pvr 004e 1202)
  Model name:  POWER9 (raw), altivec supported
  CPU max MHz: 3800.
  CPU min MHz: 2166.
  L1d cache:   32K
  L1i cache:   32K
  L2 cache:512K
  L3 cache:10240K
  NUMA node0 CPU(s):   0-79
  NUMA node8 CPU(s):   80-159

  ii  qemu-kvm  1:2.11+dfsg-1ubuntu2
  ppc64el  QEMU Full virtualization on x86 hardware

  ii  libvirt-bin   4.0.0-1ubuntu3
  ppc64el  programs for the libvirt library

  # lsmcode
  Version of System Firmware : 
   Product Name  : OpenPOWER Firmware
   Product Version   : open-power-SUPERMICRO-P9DSU-V1.03-20180205-imp
   Product Extra :  occ-577915f
   Product Extra :  skiboot-v5.9-240-g081882690163-pcbedce4
   Product Extra :  petitboot-v1.6.6-p019c87e
   Product Extra :  sbe-095e608
   Product Extra :  machine-xml-fb5f933
   Product Extra :  hostboot-9bfb201
   Product Extra :  linux-4.14.13-openpower1-p78d7eee

  
   
  Contact Information = sathe...@in.ibm.com 
   
  ---uname output---
  4.15.0-10-generic
   
  Machine Type = power9 boston 2.2 (pvr 004e 1202) 
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
   1. Boot a guest from libvirt with default pseries machine type or 
pseries-bionic

  /usr/bin/virt-install --connect=qemu:///system --hvm --accelerate --name 
'virt-tests-vm1' --machine pseries --memory=32768 
--vcpu=32,sockets=1,cores=32,threads=1 --import --nographics --serial pty 
--memballoon model=virtio --controller type=scsi,model=virtio-scsi --disk 
path=/var/lib/libvirt/images/workspace/runAvocadoFVTTest/avocado-fvt-wrapper/data/avocado-vt/images/ubuntu-18.04-ppc64le.qcow2,bus=scsi,size=10,format=qcow2
 --network=bridge=virbr0,model=virtio,mac=52:54:00:77:78:79 --noautoconsole
  WARNING  No operating system detected, VM performance may suffer. Specify an 
OS with --os-variant for optimal results.

  Starting install...
  ERRORinternal error: process exited while connecting to monitor: 
,id=scsi0-0-0-0,bootindex=1 -netdev tap,fd=24,id=hostnet0,vhost=on,vhostfd=26 
-device 
virtio-net-pci,netdev=hostnet0,id=net0,mac=52:54:00:77:78:79,bus=pci.0,addr=0x1 
-chardev pty,id=charserial0 -device 
spapr-vty,chardev=charserial0,id=serial0,reg=0x3000 -device 
virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x4 -msg timestamp=on
  2018-02-23T14:21:11.081809Z qemu-system-ppc64: KVM implementation does not 
support Transactional Memory, try cap-htm=off
  Domain installation does not appear to have been successful.
  If it was, you can restart your domain by running:
virsh --connect qemu:///system start virt-tests-vm1
  otherwise, please restart your installation.

  2. Fails to boot..

  Note: if we specify machine type as pseries=2.12 it boots fine like
  below

  /usr/bin/virt-install --connect=qemu:///system --hvm --accelerate --name 
'virt-tests-vm1' --machine pseries-2.12 --memory=32768 
--vcpu=32,sockets=1,cores=32,threads=1 --import --nographics --serial pty 
--memballoon model=virtio --controller type=scsi,model=virtio-scsi --disk 
path=/var/lib/libvirt/images/workspace/runAvocadoFVTTest/avocado-fvt-wrapper/data/avocado-vt/images/ubuntu-18.04-ppc64le.qcow2,bus=scsi,size=10,format=qcow2
 --network=bridge=virbr0,model=virtio,mac=52:54:00:77:78:79 --noautoconsole
  WARNING  No operating system detected, VM performance may suffer. Specify an 
OS with --os-variant for optimal results.

  qemu-cmd line:

  libvirt+   4283  1 99 09:26 ?00:00:38 qemu-system-ppc64
  -enable-kvm -name guest=virt-tests-vm1,debug-threads=on -S -object
  secret,id=masterKey0,format=raw,file=/var/lib/libvirt/qemu/domain-4

[Kernel-packages] [Bug 1752026] Re: Ubuntu18.04:POWER9:DD2.2 - Unable to start a KVM guest with default machine type(pseries-bionic) complaining "KVM implementation does not support Transactional Memo

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

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

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

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

Title:
  Ubuntu18.04:POWER9:DD2.2 - Unable to start a KVM guest with default
  machine type(pseries-bionic) complaining "KVM implementation does not
  support Transactional Memory, try cap-htm=off" (kvm)

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

Bug description:
  == Comment: #0 - Satheesh Rajendran  - 2018-02-23 
08:31:06 ==
  ---Problem Description---
  libvirt unable to start a KVM guest complaining about cap-htm machine 
property to be off

  Host Env:
  # lscpu
  Architecture:ppc64le
  Byte Order:  Little Endian
  CPU(s):  160
  On-line CPU(s) list: 0-159
  Thread(s) per core:  4
  Core(s) per socket:  20
  Socket(s):   2
  NUMA node(s):2
  Model:   2.2 (pvr 004e 1202)
  Model name:  POWER9 (raw), altivec supported
  CPU max MHz: 3800.
  CPU min MHz: 2166.
  L1d cache:   32K
  L1i cache:   32K
  L2 cache:512K
  L3 cache:10240K
  NUMA node0 CPU(s):   0-79
  NUMA node8 CPU(s):   80-159

  ii  qemu-kvm  1:2.11+dfsg-1ubuntu2
  ppc64el  QEMU Full virtualization on x86 hardware

  ii  libvirt-bin   4.0.0-1ubuntu3
  ppc64el  programs for the libvirt library

  # lsmcode
  Version of System Firmware : 
   Product Name  : OpenPOWER Firmware
   Product Version   : open-power-SUPERMICRO-P9DSU-V1.03-20180205-imp
   Product Extra :  occ-577915f
   Product Extra :  skiboot-v5.9-240-g081882690163-pcbedce4
   Product Extra :  petitboot-v1.6.6-p019c87e
   Product Extra :  sbe-095e608
   Product Extra :  machine-xml-fb5f933
   Product Extra :  hostboot-9bfb201
   Product Extra :  linux-4.14.13-openpower1-p78d7eee

  
   
  Contact Information = sathe...@in.ibm.com 
   
  ---uname output---
  4.15.0-10-generic
   
  Machine Type = power9 boston 2.2 (pvr 004e 1202) 
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
   1. Boot a guest from libvirt with default pseries machine type or 
pseries-bionic

  /usr/bin/virt-install --connect=qemu:///system --hvm --accelerate --name 
'virt-tests-vm1' --machine pseries --memory=32768 
--vcpu=32,sockets=1,cores=32,threads=1 --import --nographics --serial pty 
--memballoon model=virtio --controller type=scsi,model=virtio-scsi --disk 
path=/var/lib/libvirt/images/workspace/runAvocadoFVTTest/avocado-fvt-wrapper/data/avocado-vt/images/ubuntu-18.04-ppc64le.qcow2,bus=scsi,size=10,format=qcow2
 --network=bridge=virbr0,model=virtio,mac=52:54:00:77:78:79 --noautoconsole
  WARNING  No operating system detected, VM performance may suffer. Specify an 
OS with --os-variant for optimal results.

  Starting install...
  ERRORinternal error: process exited while connecting to monitor: 
,id=scsi0-0-0-0,bootindex=1 -netdev tap,fd=24,id=hostnet0,vhost=on,vhostfd=26 
-device 
virtio-net-pci,netdev=hostnet0,id=net0,mac=52:54:00:77:78:79,bus=pci.0,addr=0x1 
-chardev pty,id=charserial0 -device 
spapr-vty,chardev=charserial0,id=serial0,reg=0x3000 -device 
virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x4 -msg timestamp=on
  2018-02-23T14:21:11.081809Z qemu-system-ppc64: KVM implementation does not 
support Transactional Memory, try cap-htm=off
  Domain installation does not appear to have been successful.
  If it was, you can restart your domain by running:
virsh --connect qemu:///system start virt-tests-vm1
  otherwise, please restart your installation.

  2. Fails to boot..

  Note: if we specify machine type as pseries=2.12 it boots fine like
  below

  /usr/bin/virt-install --connect=qemu:///system --hvm --accelerate --name 
'virt-tests-vm1' --machine pseries-2.12 --memory=32768 
--vcpu=32,sockets=1,cores=32,threads=1 --import --nographics --serial pty 
--memballoon model=virtio --controller type=scsi,model=virtio-scsi --disk 
path=/var/lib/libvirt/images/workspace/runAvocadoFVTTest/avocado-fvt-wrapper/data/avocado-vt/images/ubuntu-18.04-ppc64le.qcow2,bus=scsi,size=10,format=qcow2
 --network=bridge=virbr0,model=virtio,mac=52:54:00:77:78:79 --noautoconsole
  WARNING  No operating system detected, VM performance may suffer. Specify an 
OS with --os-variant for optimal results.

  qemu-cmd line:

  libvirt+   4283  1 99 09:26 ?00:00:38 qemu-system-ppc64
  -enable-kvm -name guest=virt-tests-vm1,debug-threads=on -S -object

[Kernel-packages] [Bug 1751994] Re: ppc64el: Support firmware disable of RFI flush

** Changed in: linux (Ubuntu)
 Assignee: Ubuntu on IBM Power Systems Bug Triage (ubuntu-power-triage) => 
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/1751994

Title:
  ppc64el: Support firmware disable of RFI flush

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

Bug description:
  == Comment: #0 - Breno Leitao  - 2018-02-26 13:59:55 ==
  Hi Canonical,

  We still need some changes regarding spectre and meltdown. We need to
  backport the following commit to all supported kernel.

  I undertand that the backport for kernel 4.XX should be trivial. Not
  sure about kernel 3.13 yet.

  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=582605a429e20ae68fd0b041b2e840af296edd08
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=eb0a2d2620ae431c543963c8c7f08f597366fc60

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

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

[Kernel-packages] [Bug 1753346] Re: AMD 7 1800X system (Dell Inspiron 5675) randomly freezes

2018-03-05 Thread Pragnesh Sampat

Since the last boot, it has been up for:

$ uptime
 08:29:04 up 13:54,  1 user,  load average: 0.37, 0.32, 0.16

I should be able to try the mainline builds at some point, I am
wondering if I should leave it alone for a couple of days since this
specific boot has a USB backup hard drive removed.  I removed it
yesterday in case it might have had an impact.  After the USB drive test
is done, if the problem persists, I will try your suggestion of mainline
kernels.

Thanks for your help.

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

Title:
  AMD 7 1800X system (Dell Inspiron 5675) randomly freezes

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  This is happening every day or so.  I cannot see anything in the
  kern.log or syslog that give me a clue on where/what the issue might.
  I was using Ubuntu 17.10 earlier and upgraded to Ubuntu 18.04 on
  3/3/2018, since I thought kernel 4.15 might have better support for
  the ryzen 7 and also maybe amdgpu for the radeon 580 might be newer.
  I have removed most external devices except for networking and HDMI
  and audio out.

  Attached a tarball of info, although I believe that since I used
  'ubuntu-bug linux' command, the information might be duplicated,
  apologize for any extra attachments.

  $ ls -l dell-5675-sysinfo/
  total 168
  -rw-r--r-- 1 pss pss 83139 Mar  4 19:47 dmesg
  -rw-r--r-- 1 pss pss 26154 Mar  4 19:44 dmidecode
  -rw-r--r-- 1 pss pss  1507 Mar  4 19:45 gpu-manager.log
  -rw-r--r-- 1 pss pss   110 Mar  4 19:44 lsb-release-a
  -rw-r--r-- 1 pss pss  1464 Mar  4 19:44 lscpu
  -rw-r--r-- 1 pss pss  4353 Mar  4 19:46 lspci
  -rw-r--r-- 1 pss pss  4105 Mar  4 20:05 lspci-vvv-radeon-580.txt
  -rw-r--r-- 1 pss pss 19318 Mar  4 19:48 
mprime-p95v294b8.linux64-results-2018-03-04.txt
  -rw-r--r-- 1 pss pss   104 Mar  4 19:44 uname-a
  -rw-r--r-- 1 pss pss35 Mar  4 20:27 version.log

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-10-generic 4.15.0-10.11
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  pss1801 F pulseaudio
   /dev/snd/controlC0:  pss1801 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Mar  4 20:21:55 2018
  InstallationDate: Installed on 2018-02-16 (16 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  MachineType: Dell Inc. Inspiron 5675
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.utf8
   SHELL=/bin/bash
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-10-generic.efi.signed 
root=UUID=d6a2ae1e-5421-435f-8e4c-e377133cebc9 ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-10-generic N/A
   linux-backports-modules-4.15.0-10-generic  N/A
   linux-firmware 1.172
  SourcePackage: linux
  UpgradeStatus: Upgraded to bionic on 2018-03-04 (1 days ago)
  dmi.bios.date: 12/04/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.3.6
  dmi.board.name: 07PR60
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 3
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: 1.3.6
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.3.6:bd12/04/2017:svnDellInc.:pnInspiron5675:pvr1.3.6:rvnDellInc.:rn07PR60:rvrA00:cvnDellInc.:ct3:cvr1.3.6:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 5675
  dmi.product.version: 1.3.6
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1753346] Re: AMD 7 1800X system (Dell Inspiron 5675) randomly freezes

2018-03-05 Thread Pragnesh Sampat

Since I bought the system, around 2/15 or so, it has only run Ubuntu
17.10 and 18.04.  These are the kernels I could find in kern.log.  It
has frozen in all 3 of them.

$ cat /tmp/kversions.txt 
kern.log.3:Feb 15 22:59:33 roke kernel: [0.00] Kernel command line: 
BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic.efi.signed 
root=UUID=d6a2ae1e-5421-435f-8e4c-e377133cebc9 ro quiet splash vt.handoff=7
kern.log.2:Feb 19 18:27:12 roke kernel: [0.00] Kernel command line: 
BOOT_IMAGE=/boot/vmlinuz-4.13.0-36-generic.efi.signed 
root=UUID=d6a2ae1e-5421-435f-8e4c-e377133cebc9 ro quiet splash vt.handoff=7
kern.log.1:Mar  3 19:10:37 roke kernel: [0.00] Kernel command line: 
BOOT_IMAGE=/boot/vmlinuz-4.15.0-10-generic.efi.signed 
root=UUID=d6a2ae1e-5421-435f-8e4c-e377133cebc9 ro quiet splash vt.handoff=1

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

Title:
  AMD 7 1800X system (Dell Inspiron 5675) randomly freezes

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  This is happening every day or so.  I cannot see anything in the
  kern.log or syslog that give me a clue on where/what the issue might.
  I was using Ubuntu 17.10 earlier and upgraded to Ubuntu 18.04 on
  3/3/2018, since I thought kernel 4.15 might have better support for
  the ryzen 7 and also maybe amdgpu for the radeon 580 might be newer.
  I have removed most external devices except for networking and HDMI
  and audio out.

  Attached a tarball of info, although I believe that since I used
  'ubuntu-bug linux' command, the information might be duplicated,
  apologize for any extra attachments.

  $ ls -l dell-5675-sysinfo/
  total 168
  -rw-r--r-- 1 pss pss 83139 Mar  4 19:47 dmesg
  -rw-r--r-- 1 pss pss 26154 Mar  4 19:44 dmidecode
  -rw-r--r-- 1 pss pss  1507 Mar  4 19:45 gpu-manager.log
  -rw-r--r-- 1 pss pss   110 Mar  4 19:44 lsb-release-a
  -rw-r--r-- 1 pss pss  1464 Mar  4 19:44 lscpu
  -rw-r--r-- 1 pss pss  4353 Mar  4 19:46 lspci
  -rw-r--r-- 1 pss pss  4105 Mar  4 20:05 lspci-vvv-radeon-580.txt
  -rw-r--r-- 1 pss pss 19318 Mar  4 19:48 
mprime-p95v294b8.linux64-results-2018-03-04.txt
  -rw-r--r-- 1 pss pss   104 Mar  4 19:44 uname-a
  -rw-r--r-- 1 pss pss35 Mar  4 20:27 version.log

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-10-generic 4.15.0-10.11
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  pss1801 F pulseaudio
   /dev/snd/controlC0:  pss1801 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Mar  4 20:21:55 2018
  InstallationDate: Installed on 2018-02-16 (16 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  MachineType: Dell Inc. Inspiron 5675
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.utf8
   SHELL=/bin/bash
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-10-generic.efi.signed 
root=UUID=d6a2ae1e-5421-435f-8e4c-e377133cebc9 ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-10-generic N/A
   linux-backports-modules-4.15.0-10-generic  N/A
   linux-firmware 1.172
  SourcePackage: linux
  UpgradeStatus: Upgraded to bionic on 2018-03-04 (1 days ago)
  dmi.bios.date: 12/04/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.3.6
  dmi.board.name: 07PR60
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 3
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: 1.3.6
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.3.6:bd12/04/2017:svnDellInc.:pnInspiron5675:pvr1.3.6:rvnDellInc.:rn07PR60:rvrA00:cvnDellInc.:ct3:cvr1.3.6:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 5675
  dmi.product.version: 1.3.6
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1681909] Re: Ubuntu 17.04: dump is not captured in remote host when kdump over ssh is configured on firestone.

2018-03-05 Thread Thadeu Lima de Souza Cascardo

Can you try 16.04?

Thanks.
Cascardo.

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

Title:
  Ubuntu 17.04: dump is not captured in remote host when kdump over ssh
  is configured on firestone.

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

Bug description:
  == Comment: #0 - PAVITHRA R. PRAKASH  - 2017-03-07 
05:00:29 ==
  ---Problem Description---

  Ubuntu 17.04: dump is not captured in remote host when kdump over ssh
  is configured on firestone.

  ---Steps to Reproduce---

  1. Configure kdump.
  2. Check whether kdump is operational using ?# kdump-config show?.
  3. Install ?kernel-debuginfo? and ?kernel-debuginfo-common? rpms.
  4. Setup password less ssh connection, generate rsa key.
  # ssh-keygen -t rsa
  5. verify id_rsa and id_rsa.pub are created under /root/.ssh/
  6. Edit /etc/default/kdump-tools and add below entries.
  SSH="ubuntu@9.114.15.239"
  SSH_KEY=/root/.ssh/id_rsa
  7. Propagate RSA key.
  # kdump-config propagate
  8. Restart kdump service.
  # kdump-config load
  9. Trigger Crash using below commands.
  # echo "1" > /proc/sys/kernel/sysrq
  # echo "c" > /proc/sysrq-trigger
  10. Verify dump is available in remote server in configured path.

  Machine details
  ===

  $ ipmitool -I lanplus -H  9.47.70.3 -U ADMIN -P admin sol activate

  $ ssh ubuntu@9.47.70.29

  PW: shriya101

  
  Attaching logs

  == Comment: #1 - PAVITHRA R. PRAKASH  -
  2017-03-07 05:01:42 ==

  
  == Comment: #5 - PAVITHRA R. PRAKASH  - 2017-03-07 
23:19:46 ==
  Hi, 

  Attaching the logs.

  Network info:

  root@ltc-firep3:~# hwinfo --network
  36: None 00.0: 10700 Loopback   
[Created at net.126]
Unique ID: ZsBS.GQNx7L4uPNA
SysFS ID: /class/net/lo
Hardware Class: network interface
Model: "Loopback network interface"
Device File: lo
Link detected: yes
Config Status: cfg=new, avail=yes, need=no, active=unknown

  37: None 00.0: 10701 Ethernet
[Created at net.126]
Unique ID: 2lHw.ndpeucax6V1
Parent ID: mIXc.aXC4wIvegH8
SysFS ID: /class/net/enP33p3s0f2
SysFS Device Link: 
/devices/pci0021:00/0021:00:00.0/0021:01:00.0/0021:02:01.0/0021:03:00.2
Hardware Class: network interface
Model: "Ethernet network interface"
Driver: "tg3"
Driver Modules: "tg3"
Device File: enP33p3s0f2
HW Address: 98:be:94:03:18:4a
Permanent HW Address: 98:be:94:03:18:4a
Link detected: no
Config Status: cfg=new, avail=yes, need=no, active=unknown
Attached to: #15 (Ethernet controller)

  38: None 00.0: 10701 Ethernet
[Created at net.126]
Unique ID: 7Onn.ndpeucax6V1
Parent ID: sx0U.aXC4wIvegH8
SysFS ID: /class/net/enP33p3s0f0
SysFS Device Link: 
/devices/pci0021:00/0021:00:00.0/0021:01:00.0/0021:02:01.0/0021:03:00.0
Hardware Class: network interface
Model: "Ethernet network interface"
Driver: "tg3"
Driver Modules: "tg3"
Device File: enP33p3s0f0
HW Address: 98:be:94:03:18:48
Permanent HW Address: 98:be:94:03:18:48
Link detected: yes
Config Status: cfg=new, avail=yes, need=no, active=unknown
Attached to: #16 (Ethernet controller)

  39: None 00.0: 10701 Ethernet
[Created at net.126]
Unique ID: VwX_.ndpeucax6V1
Parent ID: DUng.aXC4wIvegH8
SysFS ID: /class/net/enP33p3s0f3
SysFS Device Link: 
/devices/pci0021:00/0021:00:00.0/0021:01:00.0/0021:02:01.0/0021:03:00.3
Hardware Class: network interface
Model: "Ethernet network interface"
Driver: "tg3"
Driver Modules: "tg3"
Device File: enP33p3s0f3
HW Address: 98:be:94:03:18:4b
Permanent HW Address: 98:be:94:03:18:4b
Link detected: no
Config Status: cfg=new, avail=yes, need=no, active=unknown
Attached to: #25 (Ethernet controller)

  40: None 00.0: 10701 Ethernet
[Created at net.126]
Unique ID: bZ1s.ndpeucax6V1
Parent ID: J7HY.aXC4wIvegH8
SysFS ID: /class/net/enP33p3s0f1
SysFS Device Link: 
/devices/pci0021:00/0021:00:00.0/0021:01:00.0/0021:02:01.0/0021:03:00.1
Hardware Class: network interface
Model: "Ethernet network interface"
Driver: "tg3"
Driver Modules: "tg3"
Device File: enP33p3s0f1
HW Address: 98:be:94:03:18:49
Permanent HW Address: 98:be:94:03:18:49
Link detected: no
Config Status: cfg=new, avail=yes, need=no, active=unknown
Attached to: #4 (Ethernet controller)
  root@ltc-firep3:~# 


  Thanks,
  Pavithra

  == Comment: #6 - PAVITHRA R. PRAKASH  -
  2017-03-07 23:20:47 ==

  
  == Comment: #7 - PAVITHRA R. PRAKASH  - 2017-03-07 
23:21:27 ==

  
  == Comment: #8 - Urvashi Jawere  - 2017-03-08 02:48:15 ==
  I am able to see some errors in syslog ;

  auxiliary
  Mar  7 04:57:44

[Kernel-packages] [Bug 1753489] Re: arm64 - stress_ng triggers panic on crypted lvm

2018-03-05 Thread dann frazier

** Attachment added: "console.log"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1753489/+attachment/5069934/+files/console.log

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

** Also affects: linux (Ubuntu Bionic)
   Importance: Undecided
   Status: Confirmed

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

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

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

Title:
  arm64 - stress_ng triggers panic on crypted lvm

Status in linux package in Ubuntu:
  New
Status in linux source package in Artful:
  Confirmed
Status in linux source package in Bionic:
  New

Bug description:
  [ 1678.415861] kernel BUG at 
/build/linux-hwe-Fuabdm/linux-hwe-4.13.0/fs/jbd2/transaction.c:1868!
  [ 1678.425019] Internal error: Oops - BUG: 0 [#1] SMP
  [ 1678.430358] Modules linked in: nls_iso8859_1 i2c_thunderx i2c_smbus 
cavium_rng_vf thunderx_edac thunderx_zip shpchp ipmi_ssif cavium_rng gpio_keys 
ipmi_devintf ipmi_msghandler uio_pdrv_genirq uio ib_iser rdma_cm iw_cm ib_cm 
ib_core iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi autofs4 btrfs 
algif_skcipher af_alg dm_crypt raid10 raid456 async_raid6_recov async_memcpy 
async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear 
nicvf nicpf ast i2c_algo_bit ttm drm_kms_helper syscopyarea aes_ce_blk 
sysfillrect sysimgblt aes_ce_cipher fb_sys_fops crc32_ce crct10dif_ce drm 
ghash_ce sha2_ce sha1_ce ahci libahci thunder_bgx thunder_xcv mdio_thunder 
thunderx_mmc mdio_cavium aes_neon_bs aes_neon_blk crypto_simd cryptd
  [ 1678.503033] CPU: 3 PID: 776 Comm: jbd2/dm-1-8 Tainted: GWL  
4.13.0-36-generic #40~16.04.1-Ubuntu
  [ 1678.515386] Hardware name: Cavium ThunderX CRB/To be filled by O.E.M., 
BIOS 5.11 12/12/2012
  [ 1678.525143] task: 801f8a75e900 task.stack: 801f633fc000
  [ 1678.532489] PC is at __jbd2_journal_temp_unlink_buffer+0x104/0x160
  [ 1678.540140] LR is at __jbd2_journal_file_buffer+0x8c/0x1f8
  [ 1678.547111] pc : [] lr : [] pstate: 
80400145
  [ 1678.556071] sp : 801f633ffb70
  [ 1678.560960] x29: 801f633ffb70 x28: 7e007ca625c0
  [ 1678.567890] x27:  x26: 801ecd5776e8
  [ 1678.574845] x25:  x24: 01400040
  [ 1678.581812] x23: 0001 x22: 801f3f4bb8f0
  [ 1678.588799] x21: 0003 x20: 801f3f4bb8f0
  [ 1678.595787] x19: 801f4a18ea50 x18: 
  [ 1678.602807] x17:  x16: 
  [ 1678.609844] x15: ddd41681 x14: 3a7accb0
  [ 1678.616895] x13: 4d1a8a2c x12: 91b5ac46
  [ 1678.623964] x11: 801f79729770 x10: 093c8c08
  [ 1678.631058] x9 : 001d x8 : 801ecd577750
  [ 1678.638182] x7 :  x6 : 0001
  [ 1678.645323] x5 :  x4 : 0040
  [ 1678.652468] x3 : 0016 x2 : 801f6d655a28
  [ 1678.659633] x1 :  x0 : 801f6d655a00
  [ 1678.666808] Process jbd2/dm-1-8 (pid: 776, stack limit = 
0x801f633fc000)

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

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

[Kernel-packages] [Bug 1749040] Re: KPTI support for arm64 systems

2018-03-05 Thread dann frazier

I was able to reproduce a crash on a crypted LVM system w/ the pre-KPTI
kernel. LP: #1753489.

The backtrace isn't identical, but it does show that crypted LVM was
fragile even before the KPTI patches.

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

Title:
  KPTI support for arm64 systems

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

Bug description:
  While regression testing the current linux-hwe proposed kernel
  (4.13.0-33.36~16.04.1), I found that it fails to boot on a Cavium
  ThunderX CRB. I've rebooted twice since upgrading from the current
  -updates kernel, and it's failed to boot both times, with different
  failure modes.

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

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

[Kernel-packages] [Bug 1753497] [NEW] Quanta Optical touchscreen recognized as usb but not as input device

2018-03-05 Thread Maarten Wisse

Public bug reported:

I bought a IIyama T2250MTS touchscreen with a Quanta Optical screen in
it that is attached through USB. It fails to register as a hiddev at
kernel level with the following message:

[21071.312190] usbhid 1-12.2:1.0: can't add hid device: -110
[21071.312219] usbhid: probe of 1-12.2:1.0 failed with error -110

Looking into kernel.log shows the same message. Device is seen, udev
tries to link it to the kernel module and this fails.

I tried all sort of things:

sudo modprobe hid-multitouch (this seems the new module that supports
it, since hid-quanta has been dropped from the kernel after 3.2)

The module loads, but the device is not recognized.

It does appear in lsusb:

Bus 001 Device 011: ID 0408:3000 Quanta Computer, Inc. Optical dual-
touch panel

xinput --list does not see it:

⎡ Virtual core pointer  id=2[master pointer  (3)]
⎜   ↳ Virtual core XTEST pointerid=4[slave  pointer  (2)]
⎜   ↳ PixArt USB Optical Mouse  id=9[slave  pointer  (2)]
⎣ Virtual core keyboard id=3[master keyboard (2)]
↳ Virtual core XTEST keyboard   id=5[slave  keyboard (3)]
↳ Power Button  id=6[slave  keyboard (3)]
↳ Power Button  id=7[slave  keyboard (3)]
↳ Sleep Button  id=8[slave  keyboard (3)]
↳ UVC Camera (046d:0821)id=10   [slave  keyboard (3)]
↳ DELL Dell USB Entry Keyboard  id=11   [slave  keyboard (3)]

There haven't been bug reports on Quanta touchscreens for years. My
problem seems most similar to this one:

https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1514310

O yes and the device properly works on Windows 10... I've exchanged the
USB cable for another one. No solution.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: linux-image-4.13.0-36-generic 4.13.0-36.40
ProcVersionSignature: Ubuntu 4.13.0-36.40-generic 4.13.13
Uname: Linux 4.13.0-36-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.7-0ubuntu3.7
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC3:  maarten1288 F pulseaudio
 /dev/snd/controlC1:  maarten1288 F pulseaudio
 /dev/snd/controlC2:  maarten1288 F pulseaudio
 /dev/snd/controlC0:  maarten1288 F pulseaudio
CurrentDesktop: KDE
Date: Mon Mar  5 14:49:49 2018
HibernationDevice: RESUME=UUID=419dcb02-2bfc-4caf-8e07-3bf2c1faf2a2
InstallationDate: Installed on 2016-12-30 (429 days ago)
InstallationMedia: Kubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.1)
IwConfig:
 enp5s0no wireless extensions.
 
 lono wireless extensions.
MachineType: MSI MS-7971
ProcEnviron:
 LANGUAGE=
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=nl_NL.UTF-8
 SHELL=/bin/bash
ProcFB: 0 EFI VGA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-36-generic.efi.signed 
root=UUID=6bc48507-dba2-4e26-beb8-4d999a7aa978 ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-4.13.0-36-generic N/A
 linux-backports-modules-4.13.0-36-generic  N/A
 linux-firmware 1.169.3
RfKill:
 0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
SourcePackage: linux
UpgradeStatus: Upgraded to artful on 2017-10-26 (130 days ago)
dmi.bios.date: 05/23/2016
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: C.70
dmi.board.asset.tag: Default string
dmi.board.name: B150 PC MATE (MS-7971)
dmi.board.vendor: MSI
dmi.board.version: 2.0
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: MSI
dmi.chassis.version: 2.0
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrC.70:bd05/23/2016:svnMSI:pnMS-7971:pvr2.0:rvnMSI:rnB150PCMATE(MS-7971):rvr2.0:cvnMSI:ct3:cvr2.0:
dmi.product.family: Default string
dmi.product.name: MS-7971
dmi.product.version: 2.0
dmi.sys.vendor: MSI

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


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

Title:
  Quanta Optical touchscreen recognized as usb but not as input device

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I bought a IIyama T2250MTS touchscreen with a Quanta Optical screen in
  it that is attached through USB. It fails to register as a hiddev at
  kernel level with the following message:

  [21071.312190] usbhid 1-12.2:1.0: can't add hid device: -110
  [21071.312219] usbhid: probe of 1-12.2:1.0 failed with error -110

  Looking into kernel.log shows the same message. Device is seen, udev
  tries to link it to the kernel module and this fails.

  I tried all sort of things:

  sudo modprobe hid-multitouch (this seems the new module that supports
  it, since hid-quanta has

[Kernel-packages] [Bug 1430696] Re: Bluetooth audio instability: Bluetooth: hci0 SCO packet for unknown connection handle

2018-03-05 Thread Pedro Arthur Duarte (JEdi)

This occurred to me. The log files got around 15GB. I had to enable
$RepeatedMsgReduction in rsyslogd in order to avoid filling my disk.

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

Title:
  Bluetooth audio instability: Bluetooth: hci0 SCO packet for unknown
  connection handle

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  (I'm creating a new bug as instructed at
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/898347/comments/29)

  I havea Nokia BH-216 bluetooth headset. Generally it works well, but
  randomly (after 5-15 minutes of use) it gets disconnected.

  The kernel log output looks like this:

  [ 3272.270382] Bluetooth: hci0 SCO packet for unknown connection handle 0
  [ 3272.270383] Bluetooth: hci0 SCO packet for unknown connection handle 0
  [ 3272.270384] Bluetooth: hci0 SCO packet for unknown connection handle 0
  [ 3272.270384] Bluetooth: hci0 SCO packet for unknown connection handle 48
  [ 3272.270385] Bluetooth: hci0 SCO packet for unknown connection handle 0
  [ 3272.270386] Bluetooth: hci0 SCO packet for unknown connection handle 0

  With quick googling this seems to be happening to other people with
  other hardware and distributions so i suppose this is a BT audio bug
  in kernel. Bug #898347 is related.

  Tested on up to date Ubuntu 14.10 x86_64.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: linux-image-3.16.0-31-generic 3.16.0-31.41
  ProcVersionSignature: Ubuntu 3.16.0-31.41-generic 3.16.7-ckt5
  Uname: Linux 3.16.0-31-generic x86_64
  ApportVersion: 2.14.7-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  vranki 2421 F pulseaudio
   /dev/snd/controlC1:  vranki 2421 F pulseaudio
  CurrentDesktop: X-Cinnamon
  Date: Wed Mar 11 11:22:19 2015
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=71d76087-3fdf-4f57-a0f4-0b128be4d386
  InstallationDate: Installed on 2015-02-12 (26 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
  MachineType: LENOVO 20C600LLMS
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-31-generic 
root=UUID=e114ca99-f1c7-450f-a4a5-553075d92b7c ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.16.0-31-generic N/A
   linux-backports-modules-3.16.0-31-generic  N/A
   linux-firmware 1.138.1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/14/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: J9ET96WW (2.16 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20C600LLMS
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0E50510 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrJ9ET96WW(2.16):bd10/14/2014:svnLENOVO:pn20C600LLMS:pvrThinkPadEdgeE540:rvnLENOVO:rn20C600LLMS:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 20C600LLMS
  dmi.product.version: ThinkPad Edge E540
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1748517] Re: Ubuntu 18.04 - Include latest ibmvnic fixes in Ubuntu kernel

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

Title:
Ubuntu 18.04 - Include latest ibmvnic fixes in Ubuntu kernel

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

Bug description:
We have a number of patches to submit to Canonical for inclusion in
the their release kernel for Ubuntu 18.04.

So far, most of these patches are upstream in Linus' tree, with some
in Dave M's net-next tree. According to the ubuntu-bionic tree, the
latest patch included is 8388a6cf ("ibmvnic: Set state UP"). If
that's true, we'll need about 15 or more patches. There may be more
coming down the pipe soon as well.

Here is a tentative patch list with commit hash and name:

1. 69d08dc Allocate and request vpd in init_resources
2. e791380 Revert to previous mtu when unsupported value requested
3. 896d869 Modify buffer size and number of queues on failover
4. a0dca10 Fix IPv6 packet descriptors
5. f689794 Fix IP offload control buffer
6. 3d16613 Fix pending MAC address changes
7. 09fb35ead58c Don't handle RX interrupts when not up
8. 4eb50ceb5c15 Include header descriptor support for ARP packets
9. 269431e737d2 Increase maximum number of RX/TX queues
10. d45cc3a43c43 Rename IBMVNIC_MAX_TX_QUEUES to IBMVNIC_MAX_QUEUES
11. f743106ec140 fix dma_mapping_error call
12. 4e6759be28e4 Feature implementation of Vital Product Data (VPD)?
13. 37798d021131 Add vnic client data to login buffer
14. 2a1bf597 Fix failover error path for non-fatal resets
15. c26eba03e407 Update reset infrastructure to support tunable parameters
16. aa0bf8510dac Let users change net device features
17. fdb061056f57 Enable TSO support
18. 154820563dd4 Enable scatter-gather support

These should apply cleanly, but I'll check on that.

Thanks!

Here is a tarball of patches. I also included this patch:

https://git.kernel.org/pub/scm/linux/kernel/git/davem/net-
next.git/commit/?id=f813614f531114db796ad66ced75c5dc8db7aa3a

Additional patches that we would like to have included:

https://marc.info/?l=linux-netdev=151803103818174=2
("[PATCH net-next] ibmvnic: queue reset when CRQ gets closed during reset")

https://marc.info/?l=linux-netdev=151796813926975=2
("[PATCH net] ibmvnic: Fix rx queue cleanup for non-fatal resets")

https://marc.info/?l=linux-netdev=151631440609769=2
("[PATCH net v2 1/3] ibmvnic: Modify buffer size and number of queues on
failover")

https://marc.info/?l=linux-netdev=151631444309775=2
("[PATCH net v2 2/3] ibmvnic: Revert to previous mtu when unsupported value
requested")

https://marc.info/?l=linux-netdev=151631448809782=2
("[PATCH net v2 3/3] ibmvnic: Allocate and request vpd in init_resources")

https://git.kernel.org/pub/scm/linux/kernel/git/davem/net-next.git/commit/?id=d45cc3a43c43f867668bdd7ace12b1e6aa68bf46
("ibmvnic: Rename IBMVNIC_MAX_TX_QUEUES to IBMVNIC_MAX_QUEUES")

https://git.kernel.org/pub/scm/linux/kernel/git/davem/net-next.git/commit/?id=269431e737d29da0f496b60188a580822d290a37
("ibmvnic: Increase maximum number of RX/TX queues")

https://git.kernel.org/pub/scm/linux/kernel/git/davem/net-next.git/commit/?id=4eb50ceb5c156a166c0b00ac27f0ff3a0943cdfb
("ibmvnic: Include header descriptor support for ARP packets")

https://marc.info/?l=linux-netdev=151796813526938=2
[PATCH net] ibmvnic: Ensure that buffers are NULL after free

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

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

[Kernel-packages] [Bug 1751337] Re: BCM5719/tg3 loses connectivity due to missing heartbeats between fw and driver

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

Title:
  BCM5719/tg3 loses connectivity due to missing heartbeats between fw
  and driver

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

Bug description:
  User reported several nodes lost connectivity in several situations,
  for instance during the netboot, in which a flood of arp traffic
  happens due to multiple simultaneous boot across the cluster.

  No stack trace or message is seen, the device just stop receiving
  packets.

  In our attempts to reproduce the issue BCM5719 lost connectivity,
  always only under a heavy arp storm, in the follow situations:

  - changing MTU
  - interface configuration (with ifconfig or ip tool) 
  - netboot

  In order to fix the issue we need to include the upstream patches:

  1 - 
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=748a240c5
  which reads: "tg3: Fix rx hang on MTU change with 5717/5719 "

  2 - 
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=506b0a395
  which reads: "tg3: APE heartbeat changes"

  Considering that 18.04 is planned to use linux 4.15 we will need to
  backport only the second patch.

  I'll submit it to the ml and post here a reference.

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

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

[Kernel-packages] [Bug 1749040] Re: KPTI support for arm64 systems

2018-03-05 Thread Paolo Pisati

Good, any other pending tests?

If not, i'll move forward and send a the above v2 arm64 kpti patchset.

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

Title:
  KPTI support for arm64 systems

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

Bug description:
  While regression testing the current linux-hwe proposed kernel
  (4.13.0-33.36~16.04.1), I found that it fails to boot on a Cavium
  ThunderX CRB. I've rebooted twice since upgrading from the current
  -updates kernel, and it's failed to boot both times, with different
  failure modes.

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

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

[Kernel-packages] [Bug 1751404] Re: cxl: patches for POWER9 support missing (CAPI)

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

Title:
  cxl: patches for POWER9 support missing (CAPI)

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

Bug description:
  The following patch, already in mainline, is missing in Ubuntu 18.04
  (kernel v4.15):

  
https://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git/commit/?h=next=b1db551324f72fa14ad82ca31237a7ed418104df
  ("cxl: Add support for ASB_Notify on POWER9")

  Please integrate this patch into Ubuntu 18.04 Thanks in advance for
  your support.

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

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

[Kernel-packages] [Bug 1746801] Re: Request to update 18.04 kernel aacraid to upstream 4.16 version

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

Title:
  Request to update 18.04 kernel aacraid to upstream 4.16 version

Status in The Ubuntu-power-systems project:
  Fix Committed
Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Bionic:
  Fix Committed

Bug description:
  We are asking for the aacraid driver to be updated for 18.04 release
  to match the latest patches upstream, that targeting 4.16. The desired
  patches were merged upstream this week and are present in Linus's
  origin/master branch now.

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

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

[Kernel-packages] [Bug 1746225] Re: [P9, Power NV][WSP][Ubuntu 1804] : "Kernel access of bad area " when grouping different pmu events using perf fuzzer . (perf:)

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

Title:
  [P9,Power NV][WSP][Ubuntu 1804] : "Kernel access of bad area " when
  grouping different pmu events using perf fuzzer . (perf:)

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

Bug description:
  == SRU Justification ==
  Due to this bug, perf fuzzer resulted in crash and system goes for a reboot
  and results in a call trace shown in the bug.  It is due to grouping of 
  different PMU events, which is fixed by mainline commit 
5aa04b3eb6fca63d2e9827be656dcadc26d54e1

  Commit 5aa04b3eb6fca63d2e9827be656dcadc26d54e11 is in mailine as of
  v4.15-rc5.

  
  == Fix ==
  commit 5aa04b3eb6fca63d2e9827be656dcadc26d54e11
  Author: Ravi Bangoria 
  Date:   Thu Nov 30 14:03:22 2017 +0530

  powerpc/perf: Fix oops when grouping different pmu events

  
  == Regression Potential ==
  Low.  This fix is specific to powerpc.

  == 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.

  
  ==Original Bug Description==
  == Comment: #0 - Shriya R. Kulkarni  - 2018-01-30 
03:24:47 ==
  Problem Description :
  ==
  Perf fuzzer resulted in crash and system goes for reboot and the call trace 
is shown below . It is due to grouping of different PMU events.

  Machine details :
  ==
  OS : Ubuntu 1804
  uname -r : 4.13.0-25-generic
  system : Witherspoon + DD2.1
  perf -v : perf version 4.13.13

  ltc-wspoon12 login: [78592.995848] Unable to handle kernel paging request for 
instruction fetch
  [78592.995914] Faulting instruction address: 0x
  [78592.995950] Oops: Kernel access of bad area, sig: 11 [#1]
  [78592.995982] SMP NR_CPUS=2048
  [78592.995985] NUMA
  [78592.996011] PowerNV
  [78592.996045] Modules linked in: vmx_crypto idt_89hpesx crct10dif_vpmsum 
at24 ofpart uio_pdrv_genirq uio cmdlinepart powernv_flash mtd ibmpowernv 
opal_prd ipmi_powernv ipmi_devintf ipmi_msghandler sch_fq_codel ip_tables 
x_tables autofs4 nouveau lpfc ast i2c_algo_bit crc32c_vpmsum ttm drm_kms_helper 
syscopyarea sysfillrect sysimgblt fb_sys_fops drm mlx5_core nvmet_fc nvmet tg3 
nvme_fc nvme_fabrics ahci nvme_core libahci mlxfw devlink scsi_transport_fc
  [78592.996367] CPU: 69 PID: 6010 Comm: perf_fuzzer Tainted: GW   
4.13.0-25-generic #29-Ubuntu
  [78592.996422] task: c03f77b5b500 task.stack: c03d0b0c8000
  [78592.996462] NIP:  LR: c00e9b1c CTR: 

  [78592.996509] REGS: c03d0b0cb780 TRAP: 0400   Tainted: GW
(4.13.0-25-generic)
  [78592.996562] MSR: 900040009033 
  [78592.996588]   CR: 48002874  XER: 
  [78592.996642] CFAR: c00e9b18 SOFTE: 1
  [78592.996642] GPR00: c00eb128 c03d0b0cba00 c15f6200 

  [78592.996642] GPR04: c03d0b0cbba0 c03d0b0cbc20 0002 
c1596b10
  [78592.996642] GPR08: 0002  c1596b10 
c03fecad0028
  [78592.996642] GPR12:  c7a8d480  

  [78592.996642] GPR16:    

  [78592.996642] GPR20: 0001 c03d0b0cbc1c c03d0b0cbc24 
c03d0b0cbb98
  [78592.996642] GPR24: c03d0b0cbba0 c03d0b0cbc20 1555 
c03fefeb4ea0
  [78592.996642] GPR28: c03d0b0cbc20 0002 3000 
c03fefeb5190
  [78592.997170] NIP []   (null)
  [78592.997208] LR [c00e9b1c] power_check_constraints+0x13c/0x5a0
  [78592.997247] Call Trace:
  [78592.997267] [c03d0b0cba00] [c03d0b0cbaa0] 0xc03d0b0cbaa0 
(unreliable)
  [78592.997321] [c03d0b0cbb80] [c00eb128] 
power_pmu_event_init+0x298/0x6a0
  [78592.997373] [c03d0b0cbc70] [c029e6b4] 
perf_try_init_event+0xd4/0x120
  [78592.997424] [c03d0b0cbcb0] [c02a1038] 
perf_event_alloc.part.23+0x7b8/0xb90
  [78592.997475] [c03d0b0cbd30] [c02aa0dc] 
SyS_perf_event_open+0x69c/0xfa0
  [78592.997527] [c03d0b0cbe30] [c000b184] system_call+0x58/0x6c
  [78592.997568] Instruction dump:
  [78592.997597]        

  [78592.997664]        

  [78592.997733] ---[ end trace 57fb7542c4083583 ]---
  [78594.008780]
  [78594.008932] Sending IP[78773.335857584,5] OPAL: Switch to big-endian OS
  I to

[Kernel-packages] [Bug 1746988] Re: [Ubuntu 18.04 FEAT] OpenCAPI enabling

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

Title:
  [Ubuntu 18.04 FEAT] OpenCAPI enabling

Status in The Ubuntu-power-systems project:
  Fix Committed
Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Bionic:
  Fix Committed

Bug description:
  [FEATURE] OpenCAPI enabling

  OpenCAPI is an Open Interface Architecture that allows any
  microprocessor to attach to

*  Coherent user-level accelerators and I/O devices
*  Advanced memories accessible via read/write or user-level DMA semantics
*  Agnostic to processor architecture

  
  This is a feature to enable OpenCapi on Ubuntu 18.04. This is planned to be 
included in 4.16 and it will need to be backported to 4.15:

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

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

[Kernel-packages] [Bug 1746174] Re: Error in CPU frequency reporting when nominal and min pstates are same (cpufreq)

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

Title:
  Error in CPU frequency reporting when nominal and min pstates are same
  (cpufreq)

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
Status in linux source package in Bionic:
  Fix Committed

Bug description:
  == SRU Justification ==
  Commit 09ca4c9b5958 introduced a bug in v4.8-rc2.  The bug is that
  an error happens in CPU frequency reporting when nominal and min pstates
  are the same (cpufreq).  Commit 3fa4680b8 fixes this issue.

  Commit 3fa4680b8 is in mailine as of v4.16-rc1 and has been cc'd to
  upstream stable.

  == Fix ==
  commit 3fa4680b860bf48b437d6a2c039789c4abe202ae
  Author: Shilpasri G Bhat 
  Date:   Fri Jan 12 12:43:53 2018 +0530

  cpufreq: powernv: Dont assume distinct pstate values for nominal
  and pmin

  == Regression Potential ==
  Low.  This commit been cc'd to upstream stable, so it has had additional
  upstream review.

  == 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 - Shilpasri G. Bhat
  +++ This bug was initially created as a clone of Bug #163527 +++

  ---Problem Description---
  Error in CPU frequency reporting when nominal and min pstates are same

  The patch for this issue is accepted to linux-next as

  3fa4680b860bf48b437d6a2c039789c4abe202ae
  cpufreq: powernv: Dont assume distinct pstate values for nominal and pmin

  Some OpenPOWER boxes can have same pstate values for nominal and
  pmin pstates. In these boxes the current code will not initialize
  'powernv_pstate_info.min' variable and result in erroneous CPU
  frequency reporting. This patch fixes this problem.

  Fixes: 09ca4c9b5958 (cpufreq: powernv: Replacing pstate_id with frequency 
table index)
  Reported-by: Alvin Wang 
  Signed-off-by: Shilpasri G Bhat 
  Acked-by: Viresh Kumar 
  Cc: 4.8+  # 4.8+
  Signed-off-by: Rafael J. Wysocki 

  https://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-
  pm.git/commit/drivers/cpufreq/powernv-cpufreq.c?h=linux-
  next=3fa4680b860bf48b437d6a2c039789c4abe202ae

  break-fix: - cf0de9a0d52ff64bcb6b20b6fa4b5d3eb4637719
  break-fix: - 3fa4680b860bf48b437d6a2c039789c4abe202ae

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

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

[Kernel-packages] [Bug 1746988] Re: [Ubuntu 18.04 FEAT] OpenCAPI enabling

** Tags removed: triage-a
** 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/1746988

Title:
  [Ubuntu 18.04 FEAT] OpenCAPI enabling

Status in The Ubuntu-power-systems project:
  Fix Committed
Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Bionic:
  Fix Committed

Bug description:
  [FEATURE] OpenCAPI enabling

  OpenCAPI is an Open Interface Architecture that allows any
  microprocessor to attach to

*  Coherent user-level accelerators and I/O devices
*  Advanced memories accessible via read/write or user-level DMA semantics
*  Agnostic to processor architecture

  
  This is a feature to enable OpenCapi on Ubuntu 18.04. This is planned to be 
included in 4.16 and it will need to be backported to 4.15:

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

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

[Kernel-packages] [Bug 1752145] Re: system freeze after full screen video viewing with Xorg on ultrawide monitor

2018-03-05 Thread Krister

=> lspci -k
00:00.0 Host bridge: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D 
DMI2 (rev 01)
Subsystem: Dell Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D DMI2
00:01.0 PCI bridge: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D 
PCI Express Root Port 1 (rev 01)
Kernel driver in use: pcieport
Kernel modules: shpchp
00:01.1 PCI bridge: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D 
PCI Express Root Port 1 (rev 01)
Kernel driver in use: pcieport
Kernel modules: shpchp
00:02.0 PCI bridge: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D 
PCI Express Root Port 2 (rev 01)
Kernel driver in use: pcieport
Kernel modules: shpchp
00:03.0 PCI bridge: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D 
PCI Express Root Port 3 (rev 01)
Kernel driver in use: pcieport
Kernel modules: shpchp
00:03.1 PCI bridge: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D 
PCI Express Root Port 3 (rev 01)
Kernel driver in use: pcieport
Kernel modules: shpchp
00:03.2 PCI bridge: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D 
PCI Express Root Port 3 (rev 01)
Kernel driver in use: pcieport
Kernel modules: shpchp
00:03.3 PCI bridge: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D 
PCI Express Root Port 3 (rev 01)
Kernel driver in use: pcieport
Kernel modules: shpchp
00:05.0 System peripheral: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 
v4/Xeon D Map/VTd_Misc/System Management (rev 01)
00:05.1 System peripheral: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 
v4/Xeon D IIO Hot Plug (rev 01)
00:05.2 System peripheral: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 
v4/Xeon D IIO RAS/Control Status/Global Errors (rev 01)
00:05.4 PIC: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D I/O APIC 
(rev 01)
Subsystem: Dell Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D I/O APIC
00:11.0 Unassigned class [ff00]: Intel Corporation C610/X99 series chipset SPSR 
(rev 05)
Subsystem: Dell C610/X99 series chipset SPSR
00:14.0 USB controller: Intel Corporation C610/X99 series chipset USB xHCI Host 
Controller (rev 05)
Subsystem: Dell C610/X99 series chipset USB xHCI Host Controller
Kernel driver in use: xhci_hcd
00:16.0 Communication controller: Intel Corporation C610/X99 series chipset MEI 
Controller #1 (rev 05)
Subsystem: Dell C610/X99 series chipset MEI Controller
Kernel driver in use: mei_me
Kernel modules: mei_me
00:16.2 IDE interface: Intel Corporation C610/X99 series chipset IDE-r 
Controller (rev 05)
Subsystem: Dell C610/X99 series chipset IDE-r Controller
Kernel driver in use: ata_generic
Kernel modules: pata_acpi
00:16.3 Serial controller: Intel Corporation C610/X99 series chipset KT 
Controller (rev 05)
Subsystem: Dell C610/X99 series chipset KT Controller
Kernel driver in use: serial
00:19.0 Ethernet controller: Intel Corporation Ethernet Connection I217-LM (rev 
05)
Subsystem: Dell Ethernet Connection I217-LM
Kernel driver in use: e1000e
Kernel modules: e1000e
00:1a.0 USB controller: Intel Corporation C610/X99 series chipset USB Enhanced 
Host Controller #2 (rev 05)
Subsystem: Dell C610/X99 series chipset USB Enhanced Host Controller
Kernel driver in use: ehci-pci
00:1b.0 Audio device: Intel Corporation C610/X99 series chipset HD Audio 
Controller (rev 05)
Subsystem: Dell C610/X99 series chipset HD Audio Controller
Kernel driver in use: snd_hda_intel
Kernel modules: snd_hda_intel
00:1c.0 PCI bridge: Intel Corporation C610/X99 series chipset PCI Express Root 
Port #1 (rev d5)
Kernel driver in use: pcieport
Kernel modules: shpchp
00:1c.1 PCI bridge: Intel Corporation C610/X99 series chipset PCI Express Root 
Port #2 (rev d5)
Kernel driver in use: pcieport
Kernel modules: shpchp
00:1c.2 PCI bridge: Intel Corporation C610/X99 series chipset PCI Express Root 
Port #3 (rev d5)
Kernel driver in use: pcieport
Kernel modules: shpchp
00:1d.0 USB controller: Intel Corporation C610/X99 series chipset USB Enhanced 
Host Controller #1 (rev 05)
Subsystem: Dell C610/X99 series chipset USB Enhanced Host Controller
Kernel driver in use: ehci-pci
00:1f.0 ISA bridge: Intel Corporation C610/X99 series chipset LPC Controller 
(rev 05)
Subsystem: Dell C610/X99 series chipset LPC Controller
Kernel driver in use: lpc_ich
Kernel modules: lpc_ich
00:1f.2 SATA controller: Intel Corporation C610/X99 series chipset 6-Port SATA 
Controller [AHCI mode] (rev 05)
Subsystem: Dell C610/X99 series chipset 6-Port SATA Controller [AHCI 
mode]
Kernel driver in use: ahci
Kernel modules: ahci
00:1f.3 SMBus: Intel Corporation C610/X99 series chipset SMBus Controller (rev 
05)
Subsystem: Dell C610/X99 series

[Kernel-packages] [Bug 1753489] [NEW] arm64 - stress_ng triggers panic on crypted lvm

2018-03-05 Thread dann frazier

Public bug reported:

[ 1678.415861] kernel BUG at 
/build/linux-hwe-Fuabdm/linux-hwe-4.13.0/fs/jbd2/transaction.c:1868!
[ 1678.425019] Internal error: Oops - BUG: 0 [#1] SMP
[ 1678.430358] Modules linked in: nls_iso8859_1 i2c_thunderx i2c_smbus 
cavium_rng_vf thunderx_edac thunderx_zip shpchp ipmi_ssif cavium_rng gpio_keys 
ipmi_devintf ipmi_msghandler uio_pdrv_genirq uio ib_iser rdma_cm iw_cm ib_cm 
ib_core iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi autofs4 btrfs 
algif_skcipher af_alg dm_crypt raid10 raid456 async_raid6_recov async_memcpy 
async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear 
nicvf nicpf ast i2c_algo_bit ttm drm_kms_helper syscopyarea aes_ce_blk 
sysfillrect sysimgblt aes_ce_cipher fb_sys_fops crc32_ce crct10dif_ce drm 
ghash_ce sha2_ce sha1_ce ahci libahci thunder_bgx thunder_xcv mdio_thunder 
thunderx_mmc mdio_cavium aes_neon_bs aes_neon_blk crypto_simd cryptd
[ 1678.503033] CPU: 3 PID: 776 Comm: jbd2/dm-1-8 Tainted: GWL  
4.13.0-36-generic #40~16.04.1-Ubuntu
[ 1678.515386] Hardware name: Cavium ThunderX CRB/To be filled by O.E.M., BIOS 
5.11 12/12/2012
[ 1678.525143] task: 801f8a75e900 task.stack: 801f633fc000
[ 1678.532489] PC is at __jbd2_journal_temp_unlink_buffer+0x104/0x160
[ 1678.540140] LR is at __jbd2_journal_file_buffer+0x8c/0x1f8
[ 1678.547111] pc : [] lr : [] pstate: 
80400145
[ 1678.556071] sp : 801f633ffb70
[ 1678.560960] x29: 801f633ffb70 x28: 7e007ca625c0
[ 1678.567890] x27:  x26: 801ecd5776e8
[ 1678.574845] x25:  x24: 01400040
[ 1678.581812] x23: 0001 x22: 801f3f4bb8f0
[ 1678.588799] x21: 0003 x20: 801f3f4bb8f0
[ 1678.595787] x19: 801f4a18ea50 x18: 
[ 1678.602807] x17:  x16: 
[ 1678.609844] x15: ddd41681 x14: 3a7accb0
[ 1678.616895] x13: 4d1a8a2c x12: 91b5ac46
[ 1678.623964] x11: 801f79729770 x10: 093c8c08
[ 1678.631058] x9 : 001d x8 : 801ecd577750
[ 1678.638182] x7 :  x6 : 0001
[ 1678.645323] x5 :  x4 : 0040
[ 1678.652468] x3 : 0016 x2 : 801f6d655a28
[ 1678.659633] x1 :  x0 : 801f6d655a00
[ 1678.666808] Process jbd2/dm-1-8 (pid: 776, stack limit = 0x801f633fc000)

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

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

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

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

Title:
  arm64 - stress_ng triggers panic on crypted lvm

Status in linux package in Ubuntu:
  New
Status in linux source package in Artful:
  Confirmed
Status in linux source package in Bionic:
  New

Bug description:
  [ 1678.415861] kernel BUG at 
/build/linux-hwe-Fuabdm/linux-hwe-4.13.0/fs/jbd2/transaction.c:1868!
  [ 1678.425019] Internal error: Oops - BUG: 0 [#1] SMP
  [ 1678.430358] Modules linked in: nls_iso8859_1 i2c_thunderx i2c_smbus 
cavium_rng_vf thunderx_edac thunderx_zip shpchp ipmi_ssif cavium_rng gpio_keys 
ipmi_devintf ipmi_msghandler uio_pdrv_genirq uio ib_iser rdma_cm iw_cm ib_cm 
ib_core iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi autofs4 btrfs 
algif_skcipher af_alg dm_crypt raid10 raid456 async_raid6_recov async_memcpy 
async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear 
nicvf nicpf ast i2c_algo_bit ttm drm_kms_helper syscopyarea aes_ce_blk 
sysfillrect sysimgblt aes_ce_cipher fb_sys_fops crc32_ce crct10dif_ce drm 
ghash_ce sha2_ce sha1_ce ahci libahci thunder_bgx thunder_xcv mdio_thunder 
thunderx_mmc mdio_cavium aes_neon_bs aes_neon_blk crypto_simd cryptd
  [ 1678.503033] CPU: 3 PID: 776 Comm: jbd2/dm-1-8 Tainted: GWL  
4.13.0-36-generic #40~16.04.1-Ubuntu
  [ 1678.515386] Hardware name: Cavium ThunderX CRB/To be filled by O.E.M., 
BIOS 5.11 12/12/2012
  [ 1678.525143] task: 801f8a75e900 task.stack: 801f633fc000
  [ 1678.532489] PC is at __jbd2_journal_temp_unlink_buffer+0x104/0x160
  [ 1678.540140] LR is at __jbd2_journal_file_buffer+0x8c/0x1f8
  [ 1678.547111] pc : [] lr : [] pstate: 
80400145
  [ 1678.556071] sp : 801f633ffb70
  [ 1678.560960] x29: 801f633ffb70 x28: 7e007ca625c0
  [ 1678.567890] x27:  x26: 801ecd5776e8
  [ 1678.574845] x25:  x24: 01400040
  [ 1678.581812] x23: 0001 x22: 801f3f4bb8f0
  [ 1678.588799] x21: 0003 x20: 801f3f4bb8f0
  [ 1678.595787] x19: 801f4a18ea50 x18: 
  [ 1678.602807] x17:  x16: 
  [ 1678.609844] x15: ddd41681 x14: 3a7accb0
  [ 1678.616895] x13: 4d1a8a2c x12: 91b5ac46

[Kernel-packages] [Bug 1746080] Re: sysfs/cpu: Add vulnerability folder for ppc64el

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

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

Title:
  sysfs/cpu: Add vulnerability folder for ppc64el

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

Bug description:
  Canonical,

  if you are planning to integrate the following patch, you will need
  the ppc64el patches that could be found attached to this bug:

  From f0dadb2e6bd7b463670a6230d5c23ad859f11c75 Mon Sep 17 00:00:00 2001

   
  From: Thomas Gleixner 
  Date: Sun, 7 Jan 2018 22:48:00 +0100
  Subject: [PATCH 1/3] sysfs/cpu: Add vulnerability folder

  As the meltdown/spectre problem affects several CPU architectures, it makes
  sense to have common way to express whether a system is affected by a
  particular vulnerability or not. If affected the way to express the
  mitigation should be common as well.

  Create /sys/devices/system/cpu/vulnerabilities folder and files for
  meltdown, spectre_v1 and spectre_v2.

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

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

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

--- Comment From bren...@br.ibm.com 2018-03-05 09:46 EDT---
Hi Cascardo,

(In reply to comment #19)
> We are working on getting those fixes to 16.04, on the -updates repository.
> But it's not part of 16.04.4.

I am not sure I understood the following statement. Do you mean that the
fix will be pushed to -updates archive after the 16.04.4, thus, it will
not make the 16.04.4 cut date?

If that is the case, that might cause some impacts,  because we are
making a release that contains some known regressions. Should we
document it somewhere?

Thank you,
Breno

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

Title:
  [Ubuntu 16.04.4] Unable to analyze the vmcore generated by kdump on
  4.13.0-26-generic kernel

Status in The Ubuntu-power-systems project:
  Triaged
Status in crash package in Ubuntu:
  Fix Released
Status in crash source package in Xenial:
  New
Status in crash source package in Artful:
  New
Status in crash source package in Bionic:
  Fix Released

Bug description:
  ---Problem Description---
  Unable to analyze the vmcore generated by kdump on 4.13.0-26-generic kernel 
(Ubuntu 16.04.4)
   
  ---uname output---
  Linux ltc-briggs1 4.13.0-26-generic #29~16.04.2-Ubuntu SMP Tue Jan 9 21:40:36 
UTC 2018 ppc64le ppc64le ppc64le GNU/Linux
   
  Machine Type = 8001-22C 

  ---Steps to Reproduce---
   This bug follow up bug of 
https://bugzilla.linux.ibm.com/show_bug.cgi?id=163565
  The steps to create dump is as follows 

  Once you generate the kdump 
  use crash to analyze the vmcore and we get this error 

  console logs ==

  root@ltc-briggs1:/var/crash/201801150227# ls
  dmesg.201801150227  vmcore.201801150227
  .0-26-generic vmcore.2018011502271150227# crash 
/usr/lib/debug/boot/vmlinux-4.13.

  crash 7.1.4
  Copyright (C) 2002-2015  Red Hat, Inc.
  Copyright (C) 2004, 2005, 2006, 2010  IBM Corporation
  Copyright (C) 1999-2006  Hewlett-Packard Co
  Copyright (C) 2005, 2006, 2011, 2012  Fujitsu Limited
  Copyright (C) 2006, 2007  VA Linux Systems Japan K.K.
  Copyright (C) 2005, 2011  NEC Corporation
  Copyright (C) 1999, 2002, 2007  Silicon Graphics, Inc.
  Copyright (C) 1999, 2000, 2001, 2002  Mission Critical Linux, Inc.
  This program is free software, covered by the GNU General Public License,
  and you are welcome to change it and/or distribute copies of it under
  certain conditions.  Enter "help copying" to see the conditions.
  This program has absolutely no warranty.  Enter "help warranty" for details.
   
  GNU gdb (GDB) 7.6
  Copyright (C) 2013 Free Software Foundation, Inc.
  License GPLv3+: GNU GPL version 3 or later 
  This is free software: you are free to change and redistribute it.
  There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
  and "show warranty" for details.
  This GDB was configured as "powerpc64le-unknown-linux-gnu"...

  please wait... (gathering module symbol data)   
  WARNING: cannot access vmalloc'd module memory

  
  crash: invalid structure member offset: thread_info_task
 FILE: task.c  LINE: 598  FUNCTION: irqstacks_init()

  [/usr/bin/crash] error trace: 1008ade0 => 1011552c => 1017d220 =>
  100833e0

100833e0: (undetermined)
1017d220: OFFSET_verify+80
1011552c: task_init+5084
1008ade0: main_loop+336

  == Comment from Hari Krishna Bathini ==

  There are quite a few commits (all available upstream) that are needed for
  crash tool to work fine. I think the right thing to do here would be to use
  the latest crash tool version 7.2.0 to go with the kernel update. Also, the
  below commit would be needed on top of 7.2.0 crash utility:

commit c8178eca9c74f81a7f803a58d339635cc152e8d9
Author: Dave Anderson 
Date:   Thu Nov 9 11:39:05 2017 -0500

  Update for support of Linux 4.14 and later PPC64 kernels where the
  hash page table geometry accomodates a larger virtual address range.
  Without the patch, the virtual-to-physical translation of user space
  virtual addresses by "vm -p", "vtop", and "rd -u" may generate an
  invalid translation or otherwise fail.
  (hbath...@linux.vnet.ibm.com)

  Similar thing holds true for makedumpfile tool..

  Thanks
  Hari

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

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

[Kernel-packages] [Bug 1745349] Re: Hard lockup during boot with linux-image-4.4.0-112-generic

@Mike Turner, you can confirm which kernel you are running by running
the following command from a terminal: uname -a

@Lars Behrens, as the original bug reporter, can you test the kernel
posted in comment #14?

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

Title:
  Hard lockup during boot with linux-image-4.4.0-112-generic

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

Bug description:
  Systems on ASUS H110M-C Boards don't boot here with Kernel 4.4.0-112
  instead they show

  NMI watchdog: Watchdog detected hard lockup on cpu 0
  NMI watchdog: Watchdog detected hard lockup on cpu 1
  NMI watchdog: Watchdog detected hard lockup on cpu 3
  NMI watchdog: Watchdog detected hard lockup on cpu 2

  I cannot provide any logs of course.

  Booting with 4.4.0-109 works.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-112-generic 4.4.0-112.135
  ProcVersionSignature: Ubuntu 4.4.0-109.132-generic 4.4.98
  Uname: Linux 4.4.0-109-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  lr3200 2013 F pulseaudio
  Date: Thu Jan 25 11:38:55 2018
  HibernationDevice: RESUME=UUID=8e35131d-6d40-4f4f-a3db-c7336e72cbce
  IwConfig:
   lono wireless extensions.
   
   enp5s0no wireless extensions.
   
   enp3s0no wireless extensions.
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 046d:c077 Logitech, Inc. M105 Optical Mouse
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: System manufacturer System Product Name
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-109-generic 
root=UUID=4dc5bb0a-ab7c-48fa-ac23-bcdf23755d93 ro
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-109-generic N/A
   linux-backports-modules-4.4.0-109-generic  N/A
   linux-firmware 1.157.15
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/12/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3601
  dmi.board.asset.tag: Default string
  dmi.board.name: H110M-C
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3601:bd12/12/2017:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnH110M-C:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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

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

[Kernel-packages] [Bug 1746299] Re: update makedumpfile tool version to v1.6.3

** Changed in: ubuntu-power-systems
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

** Changed in: makedumpfile (Ubuntu Xenial)
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

** Changed in: makedumpfile (Ubuntu Artful)
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

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

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

** Tags added: triage-g

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

Title:
  update makedumpfile tool version to v1.6.3

Status in The Ubuntu-power-systems project:
  In Progress
Status in makedumpfile package in Ubuntu:
  Fix Released
Status in makedumpfile source package in Xenial:
  New
Status in makedumpfile source package in Artful:
  New
Status in makedumpfile source package in Bionic:
  Fix Released

Bug description:
  [Impact]
  New upstream kernel versions, as those in linux-hwe package, require a newer 
makedumpfile to be supported. Otherwise, all copies fallback to copying the 
entire memory.

  [Test case]
  kdump-tools has been installed, system rebooted, then crash trigerred and 
verified that a small dump file was present on /var/crash/. Tested on amd64 and 
ppc64le.

  [Regression potential]
  Many other bug fixes have been included in the latest version of the package. 
The changes are supposed to fix these bugs, and have been tested as well. 
However, as the total of changes is not trivial, there is impact of regression 
that has been minimized by the tests done. Regression potential of not 
supporting older kernels has been tested with the kernels shipped on xenial and 
artful as well.


  
  

  == Comment: #0 - Hari Krishna Bathini  - 2018-01-30 
10:46:53 ==
  ---Problem Description---
  update makedumpfile to latest version v1.6.3 that officially supports
  up to kernel version 4.14.8. Since makedumpfile is inherently backward 
compatible,
  this would not break existing functionality..

  Contact Information = hbath...@in.ibm.com

  ---uname output---
  na

  Machine Type = na

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

  ---Steps to Reproduce---
   makedumpfile reports ""The kernel version is not supported" while generating 
vmcore
  Also, there is a possibility of bogus address translations in makedumpfile 
tool with
  missing upstream patches. Can't be so sure without an exhaustive testing. 
Instead,
  it would be a good idea to go with the version which officially supports the 
kernel
  version in question.

  Userspace tool common name: makedumpfile

  The userspace tool has the following bit modes: 64-bit

  Userspace rpm: makedumpfile

  Userspace tool obtained from project website:  na

  *Additional Instructions for hbath...@in.ibm.com:
  -Attach ltrace and strace of userspace application.

  == Comment: #1 - Hari Krishna Bathini  - 2018-01-30 
10:49:13 ==
  With kernel version updated to 4.13.0, please update makedumpfile tool
  version to 1.6.3 which officially supports up to kernel version 4.14.8 [1].

  Thanks
  Hari

  [1]
  http://lists.infradead.org/pipermail/kexec/2018-January/019853.html

  This needs to be tagged for both 16.04.4 & 18.04 releases

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

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

[Kernel-packages] [Bug 1746088] Re: [Ubuntu 16.04.4] Unable to analyze the vmcore generated by kdump on 4.13.0-26-generic kernel