date:20190204

[Kernel-packages] [Bug 1814628] [NEW] divide error: 0000 with Ubuntu 18.04

2019-02-04 Thread Tony

Public bug reported:

Got a host running lots of virtual machines crashing today with the
following terminal output (if that's to any help):

[3430458.298979] divide error:  [#1] SMP PTI
[3430458.304484] Modules linked in: cpuid vhost_net vhost tap nf_conntrack_ipv6 
nf_defrag_ipv6 xt_physdev br_netfilter ip_set nfnetlink kvm_intel kvm irqbypass 
rpcsec_gss_krb5 auth_rpcgss nfsv4 nfs lockd grace sunrpc cachefiles fscache 
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 ebtable_filter ebtables 
ip6table_filter ip6_tables devlink iptable_filter 8021q garp mrp stp llc 
bonding ipmi_ssif intel_rapl sb_edac x86_pkg_temp_thermal intel_powerclamp 
coretemp dcdbas intel_cstate intel_rapl_perf ipmi_si mei_me ipmi_devintf 
lpc_ich mei shpchp ipmi_msghandler acpi_power_meter mac_hid sch_fq_codel 
ib_iser rdma_cm iw_cm ib_cm ib_core iscsi_tcp libiscsi_tcp libiscsi
[3430458.389747]  scsi_transport_iscsi ip_tables x_tables autofs4 btrfs 
zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor 
async_tx xor raid6_pq raid1 raid0 multipath linear crct10dif_pclmul mgag200 
crc32_pclmul i2c_algo_bit ghash_clmulni_intel ttm pcbc mxm_wmi drm_kms_helper 
bnx2x aesni_intel syscopyarea sysfillrect aes_x86_64 sysimgblt fb_sys_fops 
crypto_simd glue_helper ptp cryptd drm pps_core ahci mdio libahci libcrc32c wmi 
[last unloaded: irqbypass]
[3430458.440756] CPU: 1 PID: 0 Comm: swapper/1 Not tainted 4.15.0-43-generic 
#46-Ubuntu
[3430458.450411] Hardware name: Dell Inc. PowerEdge R430/0CN7X8, BIOS 2.7.1 
01/26/2018
[3430458.460008] RIP: 0010:update_group_capacity+0x19d/0x1f0
[3430458.467098] RSP: 0018:91043ec03bd8 EFLAGS: 00010247
[3430458.474207] RAX: 006314d6 RBX: 0001 RCX: 
024d
[3430458.483490] RDX:  RSI:  RDI: 
00022880
[3430458.492769] RBP: 91043ec03c00 R08: 9104376dc940 R09: 
1dcd6500
[3430458.502071] R10: 91043ec0 R11: 0001 R12: 
910437625000
[3430458.511391] R13: 9104376dc940 R14:  R15: 
91043ec03c30
[3430458.520724] FS:  () GS:91043ec0() 
knlGS:
[3430458.531161] CS:  0010 DS:  ES:  CR0: 80050033
[3430458.538994] CR2: 00010960b008 CR3: 003f8300a002 CR4: 
003626e0
[3430458.548416] DR0:  DR1:  DR2: 

[3430458.557858] DR3:  DR6: fffe0ff0 DR7: 
0400
[3430458.567298] Call Trace:
[3430458.571507]  
[3430458.575253]  find_busiest_group+0xff/0x9c0
[3430458.581327]  load_balance+0x164/0x9c0
[3430458.586928]  ? sched_clock+0x9/0x10
[3430458.592347]  ? sched_clock_cpu+0x11/0xb0
[3430458.598249]  rebalance_domains+0x245/0x2d0
[3430458.604372]  run_rebalance_domains+0x139/0x1f0
[3430458.610901]  __do_softirq+0xe4/0x2bb
[3430458.616459]  irq_exit+0xb8/0xc0
[3430458.621538]  scheduler_ipi+0xea/0x130
[3430458.627201]  smp_reschedule_interrupt+0x39/0xe0
[3430458.633860]  reschedule_interrupt+0x84/0x90
[3430458.640138]  
[3430458.644096] RIP: 0010:cpuidle_enter_state+0xa7/0x2f0
[3430458.651289] RSP: 0018:a90100107e68 EFLAGS: 0246 ORIG_RAX: 
ff02
[3430458.661431] RAX: 91043ec22880 RBX: 000c2ffbd05252a7 RCX: 
001f
[3430458.671114] RDX: 000c2ffbd05252a7 RSI: ff1e5f04e459 RDI: 

[3430458.680819] RBP: a90100107ea8 R08:  R09: 
0d17
[3430458.690557] R10: a90100107e38 R11: 0eca R12: 
c900ff401f58
[3430458.700303] R13: 0004 R14: 9bb71d18 R15: 

[3430458.710075]  ? cpuidle_enter_state+0x97/0x2f0
[3430458.716723]  cpuidle_enter+0x17/0x20
[3430458.722455]  call_cpuidle+0x23/0x40
[3430458.728041]  do_idle+0x18c/0x1f0
[3430458.733312]  cpu_startup_entry+0x73/0x80
[3430458.739293]  start_secondary+0x1ab/0x200
[3430458.745229]  secondary_startup_64+0xa5/0xb0
[3430458.751415] Code: 34 10 48 8b 96 38 0a 00 00 48 8b 86 30 0a 00 00 48 8b b6 
a0 09 00 00 49 d1 e9 48 29 d6 ba 00 00 00 00 48 0f 48 f2 31 d2 44 01 ce <48> f7 
f6 48 3d ff 03 00 00 77 0c ba 00 04 00 00 48 29 c2 48 0f
[3430458.775397] RIP: update_group_capacity+0x19d/0x1f0 RSP: 91043ec03bd8
[3430458.784442] ---[ end trace c1ae6368b9740f8a ]---
[3430458.866540] Kernel panic - not syncing: Fatal exception in interrupt
[3430458.866591] Kernel Offset: 0x1960 from 0x8100 (relocation 
range: 0x8000-0xbfff)
[3430458.954898] ---[ end Kernel panic - not syncing: Fatal exception in 
interrupt

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

Title:
  divide error:

[Kernel-packages] [Bug 1799988] Re: Missing wifi and bluetooth after sleep on XPS 9370

2019-02-04 Thread Kai-Heng Feng

Please test this kernel:

https://people.canonical.com/~khfeng/lp1799988-d3delay/

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

Title:
  Missing wifi and bluetooth after sleep on XPS 9370

Status in Dell Sputnik:
  New
Status in linux package in Ubuntu:
  In Progress

Bug description:
  I have XPS9370 with self-installed Ubuntu 18.10 (not project sputnik) with 
Killer 1435 wireless module.
  And sometimes I find wifi and bluetooth missing after sleep. I cannot exactly 
define preconditions, but it seems there are following steps to reproduce the 
issue
  1. Connect something via bluetooth  (I use bluetooth headset)
  2. Send laptop to sleep
  3. Wake it and find wifi and bluetooth missing.

  I have to mention that I have also been experienced bluetooth only
  missing, but it somehow transformed to the issue with both wireless
  devices.

  Dmesg after waking up with the issue attached
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  kao2362 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.10
  InstallationDate: Installed on 2018-09-22 (33 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180922)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 012: ID 0489:e0a2 Foxconn / Hon Hai 
   Bus 001 Device 002: ID 0bda:58f4 Realtek Semiconductor Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. XPS 13 9370
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-10-generic 
root=UUID=34230cbd-d3d2-4cb8-855a-307883bc35ea ro quiet splash 
mem_sleep_default=deep video=1920x1080 usbcore.dyndbg=+p vt.handoff=1
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-10-generic N/A
   linux-backports-modules-4.18.0-10-generic  N/A
   linux-firmware 1.175
  Tags:  cosmic
  Uname: Linux 4.18.0-10-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 08/09/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.5.1
  dmi.board.name: 0VM1FG
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.5.1:bd08/09/2018:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn0VM1FG:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 9370
  dmi.product.sku: 07E6
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1813869] Re: Redpine: Driver crash with network-manager 1.10 and above

2019-02-04 Thread Khaled El Mously

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

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

Title:
  Redpine: Driver crash with network-manager 1.10 and above

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

Bug description:
  SRU Justification:
  --

  Impact: 
  ---
Kernel crash upon inserting Redpine driver

  Test case:
  --
1) Install network-manager v(1.10) snap.
2) Insert Redpine modules.
3) Observe the behavior.

  Result:
  ---
 Redpine driver crashes the entire kernel and below is the crash log.
 ... skipping ...
 [ 49.130185] BUG: unable to handle kernel NULL pointer dereference at 
0134
 [ 49.138969] IP: [] rsi_prepare_mgmt_desc+0xd3/0x2d0 
[ven_rsi_91x]
 [ 49.244030] CPU: 0 PID: 31 Comm: kworker/u4:1 Not tainted 
4.4.0-139-generic #165-Ubuntu
 [ 49.252988] Hardware name: Dell Inc. Edge Gateway 3001/, BIOS 
01.00.00 04/17/2017
 [ 49.261374] Workqueue: rsi_scan_worker rsi_scan_start [ven_rsi_91x]
 [ 49.268385] task: 880078538cc0 ti: 8800785e4000 task.ti: 
8800785e4000
 [ 49.276765] rsi_prepare_mgmt_desc+0xd3/0x2d0 [ven_rsi_91x]
 [ 49.387307] [] rsi_send_probe_request+0x2c7/0x350 
[ven_rsi_91x]
 [ 49.395784] [] rsi_scan_start+0x222/0x380 
[ven_rsi_91x]
 [ 49.403486] [] ? __schedule+0x301/0x7f0
 [ 49.409633] [] process_one_work+0x16b/0x490
 [ 49.416164] [] worker_thread+0x4b/0x4d0
 [ 49.422306] [] ? process_one_work+0x490/0x490
 [ 49.429032] [] kthread+0xe7/0x100
 [ 49.434589] [] ? __schedule+0x301/0x7f0
 [ 49.440731] [] ? kthread_create_on_node+0x1e0/0x1e0
 [ 49.448042] [] ret_from_fork+0x55/0x80
 [ 49.454086] [] ? kthread_create_on_node+0x1e0/0x1e0 


  Root cause analysis:
  
 In nm-1.10 and above versions, MAC spoof is enabled by default. In 
Redpine
 driver, this handling is missed. Hence, Added the fix for the same.

  Fix:
  
 Copied the Custom MAC address into driver global structure.

  Regression Petential:
  -
  This is a very direct issue Since the driver is crashing upon 
inserting the
  modules. we ran the multiple times insertion and deletion of modules 
and connected
  to third-party AP, did data transfer.

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

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

[Kernel-packages] [Bug 1802636] Re: REGRESSION: only one displayport fron docking station is used at a time

2019-02-04 Thread Launchpad Bug Tracker

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

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

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

Title:
  REGRESSION: only one displayport fron docking station is used at a
  time

Status in linux package in Ubuntu:
  Expired

Bug description:
  When my HP 840 G3 is connected to its docking station only one
  DisplayPort is used at a time. If I disconnect the one in use, the
  other is enabled. Only one display is detected. I'm using a fresh
  installation of Ubuntu 18.10. Before, on 18.04, it worked.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: xorg 1:7.7+19ubuntu8
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  Uname: Linux 4.18.0-10-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  BootLog: Error: [Errno 13] Permesso negato: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Nov 10 12:49:30 2018
  DistUpgraded: Fresh install
  DistroCodename: cosmic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Skylake GT2 [HD Graphics 520] [8086:1916] (rev 07) 
(prog-if 00 [VGA controller])
     Subsystem: Hewlett-Packard Company Skylake GT2 [HD Graphics 520] 
[103c:8079]
  InstallationDate: Installed on 2018-11-01 (9 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 04ca:7054 Lite-On Technology Corp.
   Bus 001 Device 003: ID 8087:0a2b Intel Corp.
   Bus 001 Device 002: ID 03f0:521d Hewlett-Packard
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP EliteBook 840 G3
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-10-generic 
root=UUID=1203967d-3709-4fd4-966f-4c08b53203ce ro quiet splash vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/08/2017
  dmi.bios.vendor: HP
  dmi.bios.version: N75 Ver. 01.16
  dmi.board.name: 8079
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 85.76
  dmi.chassis.asset.tag: 5CG7320Q91
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.modalias: 
dmi:bvnHP:bvrN75Ver.01.16:bd06/08/2017:svnHP:pnHPEliteBook840G3:pvr:rvnHP:rn8079:rvrKBCVersion85.76:cvnHP:ct10:cvr:
  dmi.product.family: 103C_5336AN HP EliteBook
  dmi.product.name: HP EliteBook 840 G3
  dmi.product.sku: L3C65AV
  dmi.sys.vendor: HP
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.95-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-3ubuntu2.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3

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

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

[Kernel-packages] [Bug 1791312] Re: ubuntu 18.04 flickering screen with Radeon X1600

2019-02-04 Thread Paul Dufresne

Indeed, the two radeon parameters for PLL mention in previous message
does not seems to appear anymore in modinfo radeon.

paul@paul-NC210-NC110:~/linux-stable$ git log --oneline v3.15-rc1..v3.15-rc2 | 
grep radeon
bcddee29b0b8 drm/radeon/ci: make sure mc ucode is loaded before checking the 
size
8c79bae6a30f drm/radeon/si: make sure mc ucode is loaded before checking the 
size
f8a2645ecede drm/radeon: improve PLL params if we don't match exactly v2
74073c9dd299 drm/radeon: memory leak on bo reservation failure. v2
681941c1790b drm/radeon: fix VCE fence command
7e1858f9aff7 drm/radeon: re-enable mclk dpm on R7 260X asics
277babc374f6 drm/radeon: add support for newer mc ucode on CI (v2)
1ebe92802eaf drm/radeon: add support for newer mc ucode on SI (v2)
5fb9cc4d8b16 drm/radeon: apply more strict limits for PLL params v2
6abc6d5c73b2 drm/radeon: update CI DPM powertune settings
90c4cde9d5a2 drm/radeon: fix runpm handling on APUs (v4)
57700ad1f2f2 drm/radeon: disable mclk dpm on R7 260X
8902e6f2b832 drm/radeon: Improve vramlimit module param documentation
be0949f5eb9c drm/radeon: fix audio pin counts for DCE6+ (v2)
379dfc25e257 drm/radeon/dp: switch to the common i2c over aux code
25377b921b40 drm/radeon/dp: handle zero sized i2c over aux transactions (v2)
paul@paul-NC210-NC110:~/linux-stable$ 

paul@paul-NC210-NC110:~/linux-stable$ git show 5fb9cc4d8b16
commit 5fb9cc4d8b1639b9a7487c1ee7b2b0c52877327d
Author: Christian König 
Date:   Fri Apr 4 13:45:42 2014 +0200

drm/radeon: apply more strict limits for PLL params v2

Letting post and refernce divider get to big is bad for signal stability.

v2: increase the limit to 210

Signed-off-by: Christian König 

diff --git a/drivers/gpu/drm/radeon/radeon_display.c 
b/drivers/gpu/drm/radeon/radeon_display.c
index 386cfa4c194d..2f42912031ac 100644
--- a/drivers/gpu/drm/radeon/radeon_display.c
+++ b/drivers/gpu/drm/radeon/radeon_display.c
@@ -937,6 +937,9 @@ void radeon_compute_pll_avivo(struct radeon_pll *pll,
}
post_div = post_div_best;
 
+   /* limit reference * post divider to a maximum */
+   ref_div_max = min(210 / post_div, ref_div_max);
+
/* get matching reference and feedback divider */
ref_div = max(den / post_div, 1u);
fb_div = nom;
paul@paul-NC210-NC110:~/linux-stable$ 
I might try to recompile kernel with that line commented out.
But it has been many years I did not compile a 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/1791312

Title:
  ubuntu 18.04 flickering screen with Radeon X1600

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  my laptop: HP Compaq nx9420
  my grafic card: 
  01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] 
RV530/M56-P [Mobility Radeon X1600] (prog-if 00 [VGA controller])

  attachment:
  the bug-apport-file

  Description:
  I start ubuntu 18.04 LTS (Kernel 4.15.0.33) in textmode;
  -> as soon as the kernel-module radeon.ko is loaded the screen starts 
flickering
  when starting the grafic-mode the flickering continues; so the screen is 
unusable.

  when setting the option "radeon.modeset=0" (thus: not use radeon drivers) the 
screen does not flicker
  but the resolution is limited to 1400x1050 (instead of natural 1680x1050)
  so I can not use this as work-around

  when using the old ubuntu 14.04.05 LTS (Kernel 3.13.0-157)
  the screen is o.k. NO flickering in textmode, nice grafic, NO flickering 
  xrandr tells: 1680x1050 60.1

  so I must stay on old ubuntu 14.04.05 ???

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

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

Re: [Kernel-packages] [Bug 1811755] Re: X1 Extreme: only one of the two SSDs is loaded

2019-02-04 Thread Tim Penhey

Will this fix make its way back into the bionic-updates?

Tim

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

Title:
  X1 Extreme: only one of the two SSDs is loaded

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Bionic:
  Fix Committed
Status in linux source package in Cosmic:
  Fix Committed

Bug description:
  [Impact]
  On Thinkpad X1 Extreme with two SSDs, if NQN in the firmware are 
  identical, then only one drive can be seen. NQN is supposed to be unique
  but some Intel drives do not follow that.

  [Fix]
  The device-supplied subnqn is ignored and one will be generated as if
  the field is empty.

  The upstream patch conflicts with a value in 'enum nvme_quirks' that we
  added in a SAUCE patch, changed that from (1<<8) to (1<<15).

  [Test]
  With this fix, both drives can be seen.

  [Regression Potential]
  The fix limits to Intel 760p/Pro 7600p SSD, and the fix has been
  verified by the bug reporter.

  -

  I bought a new Thinkpad X1 Extreme, and had it come with two SSDs, one
  256G and the other 512G with the intention of keeping the windows on
  the 256G disk and using the 512G for linux.

  When dealing with the installer, it only ever saw one of the SSDs. I
  did manged to get bionic installed on the 512, but on boot, sometimes
  it doesn't find the 512G disk and I just get a blank screen.  After a
  hard power-off, and reboot, it drops into the grub selector, and
  choosing linux, it failed again, but this time dropped into a VT.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-43-generic 4.15.0-43.46
  ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18
  Uname: Linux 4.15.0-43-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  tim2003 F pulseaudio
   /dev/snd/controlC0:  tim2003 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jan 15 18:53:34 2019
  InstallationDate: Installed on 2019-01-14 (0 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Beta amd64 (20190109)
  MachineType: LENOVO 20MFCTO1WW
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-43-generic 
root=UUID=9254da2f-0220-4b41-8770-ae4b0df0d114 ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-43-generic N/A
   linux-backports-modules-4.15.0-43-generic  N/A
   linux-firmware 1.173.3
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/21/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N2EET35W (1.17 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20MFCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0R32862 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN2EET35W(1.17):bd12/21/2018:svnLENOVO:pn20MFCTO1WW:pvrThinkPadX1Extreme:rvnLENOVO:rn20MFCTO1WW:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X1 Extreme
  dmi.product.name: 20MFCTO1WW
  dmi.product.version: ThinkPad X1 Extreme
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1814400] Re: Thinkpad X250 blanks and locks up when removed from the docking station

2019-02-04 Thread Jason Moore

I am not sure what changed (I have run apt upgrade a couple of times),
but I am no longer having this issue.

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

Title:
  Thinkpad X250 blanks and locks up when removed from the docking
  station

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  My X250 has worked with the docking station for just over three years
  but the latest kernel update (4.15.0-45-generic) seems to have broken
  the ability to undock.

  To reproduce:

  1. Turn the laptop on and log in.
  2. Dock the laptop.
  3. Undock the laptop.

  This leaves the computer in an unresponsive state (screen is black,
  keyboard input of any kind doesn't do anything) and I have to force a
  shutdown.

  If the laptop screen dims while docked, the computer also has be force
  restarted. If you dock the laptop before booting the computer, it
  doesn't boot and is in the same locked state.

  moorepants@garuda:~$ lsb_release -rd
  Description:  Ubuntu 18.04.1 LTS
  Release:  18.04

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-45-generic 4.15.0-45.48
  ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18
  Uname: Linux 4.15.0-45-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  moorepants   2514 F pulseaudio
   /dev/snd/controlC0:  moorepants   2514 F pulseaudio
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Sat Feb  2 12:24:29 2019
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=0001-992b-4a3e-a93f-f6ace66eec1d
  InstallationDate: Installed on 2015-11-14 (1176 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  MachineType: LENOVO 20CMCTO1WW
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-45-generic 
root=UUID=180cbbee-84f0-4f5d-8f67-ab39fe37099a ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-45-generic N/A
   linux-backports-modules-4.15.0-45-generic  N/A
   linux-firmware 1.173.3
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/19/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N10ET36W (1.15 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20CMCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN10ET36W(1.15):bd06/19/2015:svnLENOVO:pn20CMCTO1WW:pvrThinkPadX250:rvnLENOVO:rn20CMCTO1WW:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X250
  dmi.product.name: 20CMCTO1WW
  dmi.product.version: ThinkPad X250
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1814604] Re: Alt-F1 aborts program when moving away from screen

2019-02-04 Thread Rodney

I tried to do the "apport-collect 1814604" above, but I never got an
indication the browser was trying to connect to the https server.  So, I
am changing status to confirmed, as shown above.

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

Title:
  Alt-F1 aborts program when moving away from screen

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  This problem was introduced in the "4.15.0-44" or "4.15.0-45" kernel
  in late January 2019.  The same problem happens in 32 bit and 64 bit
  systems -- both installed before January 2019 and AFTER the problem
  was introduced (that is, complete new installations AFTER).  I have an
  Acer Aspire R15 laptop.

  To reproduce the problem -- after the system boots:

  Ctrl-Alt-F1 (unity) or Ctrl-Alt-F3 (gdm3).  For arguments sake, I'll only 
show unity.
  type in:
  cd /tmp
  ed
  a

  And that puts you into the "ed" editor in "append" (add) mode.

  Ctrl-Alt-F2 (or Alt-F2) and duplicate the typing in of F1 above
  Ctrl-Alt-F3 (or Alt-F3) and duplicate the typing in of F1 above

  Now, Ctrl-Alt-F1 (or Alt-F1) back to screen #1.  It is at the system
  prompt rather than and "ed" prompt, and the error "stdin: Resource
  temporarily unavailable" is displayed.  If you move to "Alt-F2" or
  "Alt-F3", you don't see the error message there, and those screens
  seem unaffected -- that is, it seems to affect only "Alt-F1".  For
  some reason screen #1 aborts the program that is running when you move
  away from "Alt-F1".  You can confirm that the program aborts when
  moving away from "Alt-F1" rather than moving back to "Alt-F1" by doing
  an "ssh" to that computer from another computer and doing a "ps -e |
  egrep tty1" before and after moving away from "Alt-F1".

  You can exit those "ed" sessions back to the system prompt by typing in:
  .
  q

  lsb_release -rd
  Description:  Ubuntu 18.04.1 LTS
  Release:  18.04

  version.log --> Ubuntu 4.15.0-45.48-generic 4.15.18

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

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

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

2019-02-04 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 1814604

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable
to run this command, please add a comment stating that fact and change
the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the
Ubuntu Kernel Team.

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

** Tags added: bionic

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

Title:
  Alt-F1 aborts program when moving away from screen

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  This problem was introduced in the "4.15.0-44" or "4.15.0-45" kernel
  in late January 2019.  The same problem happens in 32 bit and 64 bit
  systems -- both installed before January 2019 and AFTER the problem
  was introduced (that is, complete new installations AFTER).  I have an
  Acer Aspire R15 laptop.

  To reproduce the problem -- after the system boots:

  Ctrl-Alt-F1 (unity) or Ctrl-Alt-F3 (gdm3).  For arguments sake, I'll only 
show unity.
  type in:
  cd /tmp
  ed
  a

  And that puts you into the "ed" editor in "append" (add) mode.

  Ctrl-Alt-F2 (or Alt-F2) and duplicate the typing in of F1 above
  Ctrl-Alt-F3 (or Alt-F3) and duplicate the typing in of F1 above

  Now, Ctrl-Alt-F1 (or Alt-F1) back to screen #1.  It is at the system
  prompt rather than and "ed" prompt, and the error "stdin: Resource
  temporarily unavailable" is displayed.  If you move to "Alt-F2" or
  "Alt-F3", you don't see the error message there, and those screens
  seem unaffected -- that is, it seems to affect only "Alt-F1".  For
  some reason screen #1 aborts the program that is running when you move
  away from "Alt-F1".  You can confirm that the program aborts when
  moving away from "Alt-F1" rather than moving back to "Alt-F1" by doing
  an "ssh" to that computer from another computer and doing a "ps -e |
  egrep tty1" before and after moving away from "Alt-F1".

  You can exit those "ed" sessions back to the system prompt by typing in:
  .
  q

  lsb_release -rd
  Description:  Ubuntu 18.04.1 LTS
  Release:  18.04

  version.log --> Ubuntu 4.15.0-45.48-generic 4.15.18

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

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

[Kernel-packages] [Bug 1814604] [NEW] Alt-F1 aborts program when moving away from screen

2019-02-04 Thread Rodney

Public bug reported:

This problem was introduced in the "4.15.0-44" or "4.15.0-45" kernel in
late January 2019.  The same problem happens in 32 bit and 64 bit
systems -- both installed before January 2019 and AFTER the problem was
introduced (that is, complete new installations AFTER).  I have an Acer
Aspire R15 laptop.

To reproduce the problem -- after the system boots:

Ctrl-Alt-F1 (unity) or Ctrl-Alt-F3 (gdm3).  For arguments sake, I'll only show 
unity.
type in:
cd /tmp
ed
a

And that puts you into the "ed" editor in "append" (add) mode.

Ctrl-Alt-F2 (or Alt-F2) and duplicate the typing in of F1 above
Ctrl-Alt-F3 (or Alt-F3) and duplicate the typing in of F1 above

Now, Ctrl-Alt-F1 (or Alt-F1) back to screen #1.  It is at the system
prompt rather than and "ed" prompt, and the error "stdin: Resource
temporarily unavailable" is displayed.  If you move to "Alt-F2" or
"Alt-F3", you don't see the error message there, and those screens seem
unaffected -- that is, it seems to affect only "Alt-F1".  For some
reason screen #1 aborts the program that is running when you move away
from "Alt-F1".  You can confirm that the program aborts when moving away
from "Alt-F1" rather than moving back to "Alt-F1" by doing an "ssh" to
that computer from another computer and doing a "ps -e | egrep tty1"
before and after moving away from "Alt-F1".

You can exit those "ed" sessions back to the system prompt by typing in:
.
q

lsb_release -rd
Description:Ubuntu 18.04.1 LTS
Release:18.04

version.log --> Ubuntu 4.15.0-45.48-generic 4.15.18

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


** Tags: bionic

** Attachment added: "lpsci-vnvn.log"
   
https://bugs.launchpad.net/bugs/1814604/+attachment/5235991/+files/lpsci-vnvn.log

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

Title:
  Alt-F1 aborts program when moving away from screen

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  This problem was introduced in the "4.15.0-44" or "4.15.0-45" kernel
  in late January 2019.  The same problem happens in 32 bit and 64 bit
  systems -- both installed before January 2019 and AFTER the problem
  was introduced (that is, complete new installations AFTER).  I have an
  Acer Aspire R15 laptop.

  To reproduce the problem -- after the system boots:

  Ctrl-Alt-F1 (unity) or Ctrl-Alt-F3 (gdm3).  For arguments sake, I'll only 
show unity.
  type in:
  cd /tmp
  ed
  a

  And that puts you into the "ed" editor in "append" (add) mode.

  Ctrl-Alt-F2 (or Alt-F2) and duplicate the typing in of F1 above
  Ctrl-Alt-F3 (or Alt-F3) and duplicate the typing in of F1 above

  Now, Ctrl-Alt-F1 (or Alt-F1) back to screen #1.  It is at the system
  prompt rather than and "ed" prompt, and the error "stdin: Resource
  temporarily unavailable" is displayed.  If you move to "Alt-F2" or
  "Alt-F3", you don't see the error message there, and those screens
  seem unaffected -- that is, it seems to affect only "Alt-F1".  For
  some reason screen #1 aborts the program that is running when you move
  away from "Alt-F1".  You can confirm that the program aborts when
  moving away from "Alt-F1" rather than moving back to "Alt-F1" by doing
  an "ssh" to that computer from another computer and doing a "ps -e |
  egrep tty1" before and after moving away from "Alt-F1".

  You can exit those "ed" sessions back to the system prompt by typing in:
  .
  q

  lsb_release -rd
  Description:  Ubuntu 18.04.1 LTS
  Release:  18.04

  version.log --> Ubuntu 4.15.0-45.48-generic 4.15.18

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

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

[Kernel-packages] [Bug 1813509] Re: [i915] NULL pointer on Linux 4.18.0-14-generic / cosmic

2019-02-04 Thread Török Edwin

If you still have the 4.18.0-13-generic kernel try booting that, it
helped me get a working screen again.

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

Title:
  [i915] NULL pointer on Linux 4.18.0-14-generic / cosmic

Status in linux-signed package in Ubuntu:
  Confirmed

Bug description:
  After updated an old laptop to Ubuntu Cosmic (was running Xenial
  before) the graphic hangs at startup, nothing is displayed but a grey
  screen (grub residual), note that the recovery boot option using
  `nodmodeset` displays a text console and I'm still able to log-in over
  a serial tty on normal boot so kernel is alive but computer is not
  usable due to lack graphic support.

  Computer is a Thinkpad X61 Tablet plugged on an X6 Tablet UltraBase
  - http://www.thinkwiki.org/wiki/Category:X61_Tablet
  - http://www.thinkwiki.org/wiki/ThinkPad_X6_Tablet_UltraBase
  GPU is an Intel GMA X3100
  - http://www.thinkwiki.org/wiki/Intel_Graphics_Media_Accelerator_X3100

  Some information:

  # lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 18.10
  Release:  18.10
  Codename: cosmic

  # uname -a
  Linux arwen 4.18.0-14-generic #15-Ubuntu SMP Mon Jan 14 09:01:02 UTC 2019 
x86_64 x86_64 x86_64 GNU/Linux

  # lspci -vvv -nn -s 00:02.0
  00:02.0 VGA compatible controller [0300]: Intel Corporation Mobile 
GM965/GL960 Integrated Graphics Controller (primary) [8086:2a02] (rev 0c) 
(prog-if 00 [VGA controller])
Subsystem: Lenovo GM965 [X3100] on ThinkPad T61/R61 [17aa:20b5]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR-  8b 52 
08 48 c7 40 0c 00 00 00 00 83 ca 04 89 50 08 48 8d 50 14 
  [2.709180] RSP: 0018:c2718067b978 EFLAGS: 00010287
  [2.709180] RAX: c27190303000 RBX: 9e5533e87200 RCX: 
c27190303044
  [2.709180] RDX:  RSI: 01a8 RDI: 
0150
  [2.709180] RBP: c2718067b988 R08: 0001 R09: 
0002
  [2.709180] R10: 0001 R11: 9e5533e87200 R12: 
0202
  [2.709180] R13: 9e5533e87200 R14: 9e553380ac00 R15: 
9e5533ab8000
  [2.709180] FS:  7fd9f63c88c0() GS:9e557e40() 
knlGS:
  [2.709180] CS:  0010 DS:  ES:  CR0: 80050033
  [2.709180] CR2: 0008 CR3: 34302000 CR4: 
06f0
  [2.709180] Call Trace:
  [2.709180]  i915_request_alloc+0x24e/0x370 [i915]
  [2.709180]  i915_gem_init+0x26b/0x470 [i915]
  [2.709180]  i915_driver_load+0xab8/0xd80 [i915]
  [2.709180]  ? mutex_lock+0x12/0x30
  [2.709180]  i915_pci_probe+0x46/0x60 [i915]
  [2.709180]  local_pci_probe+0x46/0x90
  [2.709180]  pci_device_probe+0x11c/0x1a0
  [2.709180]  driver_probe_device+0x2e3/0x460
  [2.709180]  __driver_attach+0xe4/0x110
  [2.709180]  ? driver_probe_device+0x460/0x460
  [2.709180]  bus_for_each_dev+0x74/0xb0
  [2.709180]  ? kmem_cache_alloc_trace+0x1c4/0x1d0
  [2.709180]  driver_attach+0x1e/0x20
  [2.709180]  bus_add_driver+0x159/0x230
  [2.709180]  ? 0xc0474000
  [2.709180]  driver_register+0x70/0xc0
  [2.709180]  ? 0xc0474000
  [2.709180]  __pci_register_driver+0x57/0x60
  [2.709180]  i915_init+0x55/0x58 [i915]
  [2.709180]  do_one_initcall+0x4a/0x1c4
  [2.709180]  ? _cond_resched+0x19/0x30
  [2.709180]  ? kmem_cache_alloc_trace+0xb8/0x1d0
  [2.709180]  ? do_init_module+0x27/0x220
  [2.709180]  do_init_module+0x60/0x220
  [2.709180]  load_module+0x14f4/0x1890
  [2.709180]  __do_sys_finit_module+0xbd/0x120
  [2.709180]  ? __do_sys_finit_module+0xbd/0x120
  [2.709180]  __x64_sys_finit_module+0x1a/0x20
  [2.709180]  do_syscall_64+0x5a/0x110
  [2.709180]  entry_SYSCALL_64_after_hwframe+0x44/0xa9
  [2.709180] RIP: 0033:0x7fd9f6e4d219
  [2.709180] Code: 00 c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 48 89 
f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 
f0 ff ff 73 01 c3 48 8b 0d 47 fc 0c 00 f7 d8 64 89 01 48 
  [2.709180] RSP: 002b:7ffc11865868 EFLAGS: 0246 ORIG_RAX: 
0139
  [2.709180] RAX: ffda RBX: 5580d38f98c0 RCX: 
7fd9f6e4d219
  [2.709180] RDX:  RSI: 7fd9f6d31cad RDI: 
0012
  [2.709180] RBP: 7fd9f6d31cad R08:  R09: 

  [2.709180] R10: 0012 R11: 0246 R12: 

  [2.709180] R13: 5580d3913ae0 R14: 0002 R15: 
5580d38f98c0
  [2.709180] Modules linked in: gpio_ich i915(+) i2c_algo_bit 
drm_kms_helper syscopyarea sysfillrect sdhci_pci

[Kernel-packages] [Bug 1813509] Re: [i915] NULL pointer on Linux 4.18.0-14-generic / cosmic

2019-02-04 Thread Launchpad Bug Tracker

Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  [i915] NULL pointer on Linux 4.18.0-14-generic / cosmic

Status in linux-signed package in Ubuntu:
  Confirmed

Bug description:
  After updated an old laptop to Ubuntu Cosmic (was running Xenial
  before) the graphic hangs at startup, nothing is displayed but a grey
  screen (grub residual), note that the recovery boot option using
  `nodmodeset` displays a text console and I'm still able to log-in over
  a serial tty on normal boot so kernel is alive but computer is not
  usable due to lack graphic support.

  Computer is a Thinkpad X61 Tablet plugged on an X6 Tablet UltraBase
  - http://www.thinkwiki.org/wiki/Category:X61_Tablet
  - http://www.thinkwiki.org/wiki/ThinkPad_X6_Tablet_UltraBase
  GPU is an Intel GMA X3100
  - http://www.thinkwiki.org/wiki/Intel_Graphics_Media_Accelerator_X3100

  Some information:

  # lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 18.10
  Release:  18.10
  Codename: cosmic

  # uname -a
  Linux arwen 4.18.0-14-generic #15-Ubuntu SMP Mon Jan 14 09:01:02 UTC 2019 
x86_64 x86_64 x86_64 GNU/Linux

  # lspci -vvv -nn -s 00:02.0
  00:02.0 VGA compatible controller [0300]: Intel Corporation Mobile 
GM965/GL960 Integrated Graphics Controller (primary) [8086:2a02] (rev 0c) 
(prog-if 00 [VGA controller])
Subsystem: Lenovo GM965 [X3100] on ThinkPad T61/R61 [17aa:20b5]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR-  8b 52 
08 48 c7 40 0c 00 00 00 00 83 ca 04 89 50 08 48 8d 50 14 
  [2.709180] RSP: 0018:c2718067b978 EFLAGS: 00010287
  [2.709180] RAX: c27190303000 RBX: 9e5533e87200 RCX: 
c27190303044
  [2.709180] RDX:  RSI: 01a8 RDI: 
0150
  [2.709180] RBP: c2718067b988 R08: 0001 R09: 
0002
  [2.709180] R10: 0001 R11: 9e5533e87200 R12: 
0202
  [2.709180] R13: 9e5533e87200 R14: 9e553380ac00 R15: 
9e5533ab8000
  [2.709180] FS:  7fd9f63c88c0() GS:9e557e40() 
knlGS:
  [2.709180] CS:  0010 DS:  ES:  CR0: 80050033
  [2.709180] CR2: 0008 CR3: 34302000 CR4: 
06f0
  [2.709180] Call Trace:
  [2.709180]  i915_request_alloc+0x24e/0x370 [i915]
  [2.709180]  i915_gem_init+0x26b/0x470 [i915]
  [2.709180]  i915_driver_load+0xab8/0xd80 [i915]
  [2.709180]  ? mutex_lock+0x12/0x30
  [2.709180]  i915_pci_probe+0x46/0x60 [i915]
  [2.709180]  local_pci_probe+0x46/0x90
  [2.709180]  pci_device_probe+0x11c/0x1a0
  [2.709180]  driver_probe_device+0x2e3/0x460
  [2.709180]  __driver_attach+0xe4/0x110
  [2.709180]  ? driver_probe_device+0x460/0x460
  [2.709180]  bus_for_each_dev+0x74/0xb0
  [2.709180]  ? kmem_cache_alloc_trace+0x1c4/0x1d0
  [2.709180]  driver_attach+0x1e/0x20
  [2.709180]  bus_add_driver+0x159/0x230
  [2.709180]  ? 0xc0474000
  [2.709180]  driver_register+0x70/0xc0
  [2.709180]  ? 0xc0474000
  [2.709180]  __pci_register_driver+0x57/0x60
  [2.709180]  i915_init+0x55/0x58 [i915]
  [2.709180]  do_one_initcall+0x4a/0x1c4
  [2.709180]  ? _cond_resched+0x19/0x30
  [2.709180]  ? kmem_cache_alloc_trace+0xb8/0x1d0
  [2.709180]  ? do_init_module+0x27/0x220
  [2.709180]  do_init_module+0x60/0x220
  [2.709180]  load_module+0x14f4/0x1890
  [2.709180]  __do_sys_finit_module+0xbd/0x120
  [2.709180]  ? __do_sys_finit_module+0xbd/0x120
  [2.709180]  __x64_sys_finit_module+0x1a/0x20
  [2.709180]  do_syscall_64+0x5a/0x110
  [2.709180]  entry_SYSCALL_64_after_hwframe+0x44/0xa9
  [2.709180] RIP: 0033:0x7fd9f6e4d219
  [2.709180] Code: 00 c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 48 89 
f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 
f0 ff ff 73 01 c3 48 8b 0d 47 fc 0c 00 f7 d8 64 89 01 48 
  [2.709180] RSP: 002b:7ffc11865868 EFLAGS: 0246 ORIG_RAX: 
0139
  [2.709180] RAX: ffda RBX: 5580d38f98c0 RCX: 
7fd9f6e4d219
  [2.709180] RDX:  RSI: 7fd9f6d31cad RDI: 
0012
  [2.709180] RBP: 7fd9f6d31cad R08:  R09: 

  [2.709180] R10: 0012 R11: 0246 R12: 

  [2.709180] R13: 5580d3913ae0 R14: 0002 R15: 
5580d38f98c0
  [2.709180] Modules linked in: gpio_ich i915(+) i2c_algo_bit 
drm_kms_helper

[Kernel-packages] [Bug 1771276] Re: linux 4.15 currupts ipsec packets over non ethernet devices

2019-02-04 Thread CalderCoalson

Any movement on this?

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

Title:
  linux 4.15 currupts ipsec packets over non ethernet devices

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

Bug description:
  Linux 4.15 has a bug that currupts ipsec packets if they are received over a 
non ethernet interface.
  This is a serve showstopper bug for me since it breaks my VPN setup and locks 
me out of my server.

  see https://wiki.strongswan.org/issues/2571 and
  
https://git.kernel.org/pub/scm/linux/kernel/git/davem/net.git/commit/?id=87cdf3148b11

  since 4.15 is already EOL, the only possibility is backporting the
  linked patch

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

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

[Kernel-packages] [Bug 1814393] Re: "make: write error: stdout" on parallel builds

2019-02-04 Thread Sebastian Urban

I am seeing the same problem on a fully updated Ubuntu system running
Linux 4.15.0-45.

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

Title:
"make: write error: stdout" on parallel builds

Status in linux-signed package in Ubuntu:
New

Bug description:
- Release of Ubuntu: 18.04.1 LTS (Kubuntu).
- Package version: linux-image-4.15.0-44-generic,
linux-image-4.15.0-45-generic.
- Expected outcome: Large parallel make build completing properly.
- What happened instead: Build stops with "make: write error: stdout".

Full explanation:

Since the update to kernel 4.15.0-44 (linux-image-4.15.0-44-generic)
in Kubuntu Bionic I'm experiencing issues in my ThinkPad P52 laptop
during large parallel builds of source code (eg: a buildroot full
rebuild for a work project). Note that this reports isn't about kernel
builds, but about large project builds in general.

I don't think it's relevant, but I'm running those builds in an
schroot with the same Ubuntu Bionic distro I'm also using as main host
distro.

The specific error I get is this (in Spanish):

make[4]: error al escribir: stdout

I call Buildroot's make like this from KDE Konsole with "infinite
history buffer" enabled (uses a tmp file to store the logs):

V=1 make ...some stuff... 2>&1

However, the error is reproducible in Konsole even if I call make
without options and also if I use "limited (in-memory) history buffer"
as well as "no history buffer". Buildroot autoselects a
parallelization level (-j) automatically. In my case, I'm using a Xeon
E-2176 CPU with 12 threads.

Searching on the Internet I found a thread[1] where people from the
GNU Make project say that the error may be coming from the C runtime
library (and I suspect originating from the kernel).

I can NOT reproduce the issue on linux-image-4.15.0-43-generic
(selected from grub at boot), but I experience it with linux-
image-4.15.0-44-generic and linux-image-4.15.0-45-generic. That's why
I'm reporting this bug against the linux package.

Interestingly enough, I can NOT reproduce the issue on linux-
image-4.15.0-45-generic (haven't tried previous versions) when
building from xterm instead of Konsole. Unfortunately, this laptop has
a 4K screen and xterm isn't an option for me.

If I build redirecting stdout and stderr to different files to avoid
terminal output and then watching the stdout file with tail -f, the
tail command eventually finishes although the build continues and I
can keep watching it by running tail again. An infinite build loop
never finishes with this redirection (error not reproducible). Same
results with the 2>&1 redirection to a single file.

All this looks a bit like a poltergeist, but the only thing I'm sure
about is that it all started with the upgrade from 4.15.0-43 to -44
and it continues on -45.

Thank you.

[1]
http://gnu-make.2324884.n4.nabble.com/Spurious-quot-write-error-quot-on-parallel-builds-td15695.html

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

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

[Kernel-packages] [Bug 1791312] Re: ubuntu 18.04 flickering screen with Radeon X1600

2019-02-04 Thread Paul Dufresne

From: https://kernel.ubuntu.com/~kernel-ppa/mainline/v3.15-rc2-trusty/CHANGES
I see the folowing changes for radeon:

Alex Deucher (13):
  drm/radeon/dp: handle zero sized i2c over aux transactions (v2)
  drm/dp/i2c: send bare addresses to properly reset i2c connections (v4)
  drm/dp/i2c: Update comments about common i2c over dp assumptions (v3)
  drm/radeon/dp: switch to the common i2c over aux code
  drm/radeon: fix audio pin counts for DCE6+ (v2)
  drm/radeon: disable mclk dpm on R7 260X
  drm/radeon: fix runpm handling on APUs (v4)
  drm/radeon: update CI DPM powertune settings
  drm/radeon: add support for newer mc ucode on SI (v2)
  drm/radeon: add support for newer mc ucode on CI (v2)
  drm/radeon: re-enable mclk dpm on R7 260X asics
  drm/radeon/si: make sure mc ucode is loaded before checking the size
  drm/radeon/ci: make sure mc ucode is loaded before checking the size

Christian KÃ¶nig (2):
  drm/radeon: apply more strict limits for PLL params v2
  drm/radeon: improve PLL params if we don't match exactly v2

Christoph Jaeger (2):
  ...
  drm/radeon: fix VCE fence command

Quentin Casasnovas (1):
  drm/radeon: memory leak on bo reservation failure. v2

The:
Christian KÃ¶nig (2):
  drm/radeon: apply more strict limits for PLL params v2
  drm/radeon: improve PLL params if we don't match exactly v2
rings a bell for me, because I believe someone somewhere was saying that a 
kernel parameter
speaking of PLL was fixing the problem... but people did not find PLL 
parameters for radeon,
so people did not follow about that comment.

From:
https://www.x.org/releases/current/doc/man/man4/radeon.4.xhtml
I see:
Option "LVDSProbePLL" "boolean"
When BIOS panel information isn’t available (like on PowerBooks), it may still 
be necessary to
use the firmware-provided PLL values for the panel or flickering will happen. 
This option will
force probing of the current value programmed in the chip when X is launched in 
that case.
This is only useful for LVDS panels (laptop internal panels). The default is on.
Also:
Option "DefaultTMDSPLL" "boolean"
Use the default driver provided TMDS PLL values rather than the ones provided 
by the BIOS.
This option has no effect on Mac cards.
Enable this option if you are having problems with a DVI monitor using the 
internal TMDS controller.
The default is off.

Also:
  drm/radeon: update CI DPM powertune settings
ring an other bell, because I think I remember someone saying something about 
DPM in some message.
Sorry for not being more specific.

A similar, older fixed closed bug:
https://bugzilla.kernel.org/show_bug.cgi?id=26552

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

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

Title:
  ubuntu 18.04 flickering screen with Radeon X1600

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  my laptop: HP Compaq nx9420
  my grafic card: 
  01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] 
RV530/M56-P [Mobility Radeon X1600] (prog-if 00 [VGA controller])

  attachment:
  the bug-apport-file

  Description:
  I start ubuntu 18.04 LTS (Kernel 4.15.0.33) in textmode;
  -> as soon as the kernel-module radeon.ko is loaded the screen starts 
flickering
  when starting the grafic-mode the flickering continues; so the screen is 
unusable.

  when setting the option "radeon.modeset=0" (thus: not use radeon drivers) the 
screen does not flicker
  but the resolution is limited to 1400x1050 (instead of natural 1680x1050)
  so I can not use this as work-around

  when using the old ubuntu 14.04.05 LTS (Kernel 3.13.0-157)
  the screen is o.k. NO flickering in textmode, nice grafic, NO flickering 
  xrandr tells: 1680x1050 60.1

  so I must stay on old ubuntu 14.04.05 ???

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

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

[Kernel-packages] [Bug 1721987] Re: No sound from right audio channel

2019-02-04 Thread Reda Borchardt

It never ceases to amaze me how collectively we manage to overcome these
issues. Yes, your wantedby list is a great addition. The left speaker is
so loud I hardly noticed the lack of stereo after waking.

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

Title:
  No sound from right audio channel

Status in Linux:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  No audio comes out of the right speaker on the laptop.  When playing a
  test video such as https://www.youtube.com/watch?v=hTvJoYnpeRQ the
  right-channel audio is never heard (i.e., it does not get converted
  into mono and played through the left speaker).

  When plugging in headphones, audio is heard from both channels.

  In Windows, both speakers work, so it is not a physical problem with
  the speakers.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-12-generic 4.13.0-12.13 [modified: 
boot/vmlinuz-4.13.0-12-generic]
  ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
  Uname: Linux 4.13.0-12-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  user   1127 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Oct  7 12:58:01 2017
  InstallationDate: Installed on 2017-10-07 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  MachineType: HUAWEI HUAWEI MateBook X
  ProcEnviron:
   PATH=(custom, no username)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-12-generic.efi.signed 
root=UUID=f0a69f35-7c1e-4280-b325-6b7fec6e174a ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-12-generic N/A
   linux-backports-modules-4.13.0-12-generic  N/A
   linux-firmware 1.168
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/14/2017
  dmi.bios.vendor: HUAWEI
  dmi.bios.version: 1.12
  dmi.board.name: HUAWEI MateBook X
  dmi.board.vendor: HUAWEI
  dmi.board.version: 2.0
  dmi.chassis.type: 10
  dmi.chassis.vendor: HUAWEI
  dmi.modalias: 
dmi:bvnHUAWEI:bvr1.12:bd08/14/2017:svnHUAWEI:pnHUAWEIMateBookX:pvr2.0:rvnHUAWEI:rnHUAWEIMateBookX:rvr2.0:cvnHUAWEI:ct10:cvr:
  dmi.product.family: HUAWEI MateBook
  dmi.product.name: HUAWEI MateBook X
  dmi.product.version: 2.0
  dmi.sys.vendor: HUAWEI

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

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

[Kernel-packages] [Bug 1748689] Re: Mounting SMB shares with vers=3.0 in fstab gives "ioctl error in smb2_get_dfs_refer rc=-2"

2019-02-04 Thread Andrew Reis

BUMP

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

Title:
  Mounting SMB shares with vers=3.0 in fstab gives "ioctl error in
  smb2_get_dfs_refer rc=-2"

Status in dellserver:
  New
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Xubuntu 17.10 artful
  Kernel: x86_64 Linux 4.13.0-32.35-generic
  cifs-utils 2:6.7-1
  smbclient  2:4.6.7+dfsg-1ubuntu3.1

  Mounting an SMB share with
  
sec=ntlmssp,vers=3.0,credentials=/home/.smbcredentials,dir_mode=0777,file_mode=0777

  in /etc/fstab gives the error: "CIFS VFS: ioctl error in
  smb2_get_dfs_refer rc=-2" in dmesg.

  Shares mounted this way are readable, but writing data to them (or using 
programs such as EasyTAG to write to them) ultimately fails. This bug did not 
occur in kernel 4.10. Mounting the share(s) with vers=1.0 does not give the 
error, but this is a haphazard fix as SMB v3.0 carries many security features 
with it not avaliable in SMB 1.0.
  --- 
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 17.10
  HibernationDevice: RESUME=/dev/mapper/DeusVitam--vg-swap_1
  JournalErrors:
   Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] 
failed with exit code 1: Hint: You are currently not seeing messages from other 
users and the system.
 Users in the 'systemd-journal' group can see all messages. Pass -q to
 turn off this notice.
   No journal files were opened due to insufficient permissions.
  MachineType: ASUS All Series
  Package: linux (not installed)
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic 
root=/dev/mapper/hostname--vg-root ro splash quiet amdgpu.cik_support=1 
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 x86_64
  UpgradeStatus: Upgraded to artful on 2018-02-05 (7 days ago)
  UserGroups: libvirt libvirtd sudo wireshark
  WifiSyslog:
   
  _MarkForUpload: True
  dmi.bios.date: 03/16/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0701
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z97-E/USB 3.1
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  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.:bvr0701:bd03/16/2016:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ97-E/USB3.1:rvrRevX.0x:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: ASUS MB
  dmi.product.name: All Series
  dmi.product.version: System Version
  dmi.sys.vendor: ASUS

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

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

1 2 3 4 >

1 - 100 of 373 matches

Mail list logo