[Kernel-packages] [Bug 1814555] Re: Ubuntu boot failure. 4.18.0-14 boot stalls. (does not boot)

2019-02-09 Thread Török Edwin
I confirm that 4.18.0-15.16 has fixed the problem for me too on a Lenovo
X300, thanks.

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

Title:
  Ubuntu boot failure. 4.18.0-14 boot stalls. (does not boot)

Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Cosmic:
  Fix Released

Bug description:
  Today my Ubuntu (18.10) did an auto-upgrade to 4.18.0-14-generic,
  requested a reboot, and was unable to boot. After the "Starting
  Load/Save RF Kill Switch Status..." line it is waiting forever.
  (Or/and doing something behind the scenes. After a while, even the HDD
  indicator led go out.)

  This is a permanent error, so kernel 4.18.0-14 does NOT boot.
  I was able to boot with kernel 4.18.0-13. (By pressing Shift when grub 
starts.)

  My configuration is "nothing fancy", possibly-except the locale (ISO-8859-2, 
hu and en), Xcfe4, gdm3, gnome-screensaver.
  I have already upgraded to the latest packages. (sudo apt-get dist-upgrade)

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

-- 
Mailing list: https://launchpad.net/~kernel-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 1813657] Re: 4.18.0-14 doesn't boot past grub

2019-02-04 Thread Török Edwin
Feb  4 15:22:03 mama-tata-laptop kernel: [1.81] 
[drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe B FIFO 
underrun
Feb  4 15:22:03 mama-tata-laptop kernel: [1.822564] [drm] RC6 disabled, 
disabling runtime PM support
Feb  4 15:22:03 mama-tata-laptop kernel: [1.822604] BUG: unable to handle 
kernel NULL pointer dereference at 0008
Feb  4 15:22:03 mama-tata-laptop kernel: [1.822613] PGD 0 P4D 0 
Feb  4 15:22:03 mama-tata-laptop kernel: [1.822623] Oops:  [#1] SMP PTI
Feb  4 15:22:03 mama-tata-laptop kernel: [1.822631] CPU: 0 PID: 176 Comm: 
systemd-udevd Not tainted 4.18.0-14-generic #15-Ubuntu
Feb  4 15:22:03 mama-tata-laptop kernel: [1.822639] Hardware name: LENOVO 
647814G/647814G, BIOS 7TET36WW (1.10 ) 05/11/2009
Feb  4 15:22:03 mama-tata-laptop kernel: [1.822732] RIP: 
0010:gen4_render_ring_flush+0x60/0x110 [i915]
Feb  4 15:22:03 mama-tata-laptop kernel: [1.822737] Code: 00 48 89 df e8 51 
fe ff ff 48 3d 00 f0 ff ff 77 6c 44 89 20 48 8d 48 44 c7 40 04 02 40 00 7a 48 
8b 53 78 48 8b 92 10 02 00 00 <48> 8b 52 08 48 c7 40 0c 00 00 00 00 83 ca 04 89 
50 08 48 8d 50 14 
Feb  4 15:22:03 mama-tata-laptop kernel: [1.822817] RSP: 
0018:b15f80a3f978 EFLAGS: 00010287
Feb  4 15:22:03 mama-tata-laptop kernel: [1.822825] RAX: b15f90002000 
RBX: 967c30438240 RCX: b15f90002044
Feb  4 15:22:03 mama-tata-laptop kernel: [1.822832] RDX:  
RSI: 01a8 RDI: 0150
Feb  4 15:22:03 mama-tata-laptop kernel: [1.822838] RBP: b15f80a3f988 
R08: 0001 R09: 3c4a9d47
Feb  4 15:22:03 mama-tata-laptop kernel: [1.822846] R10: 181a474d 
R11: 967c30438240 R12: 0202
Feb  4 15:22:03 mama-tata-laptop kernel: [1.822852] R13: 967c30438240 
R14: 967c31389000 R15: 967c30dc8000
Feb  4 15:22:03 mama-tata-laptop kernel: [1.822860] FS:  
7f8967b738c0() GS:967c3bc0() knlGS:
Feb  4 15:22:03 mama-tata-laptop kernel: [1.822868] CS:  0010 DS:  ES: 
 CR0: 80050033
Feb  4 15:22:03 mama-tata-laptop kernel: [1.822874] CR2: 0008 
CR3: 000130cc4000 CR4: 06f0
Feb  4 15:22:03 mama-tata-laptop kernel: [1.822881] Call Trace:
Feb  4 15:22:03 mama-tata-laptop kernel: [1.822970]  
i915_request_alloc+0x24e/0x370 [i915]
Feb  4 15:22:03 mama-tata-laptop kernel: [1.823055]  
i915_gem_init+0x26b/0x470 [i915]
Feb  4 15:22:03 mama-tata-laptop kernel: [1.823131]  
i915_driver_load+0xab8/0xd80 [i915]
Feb  4 15:22:03 mama-tata-laptop kernel: [1.823143]  ? mutex_lock+0x12/0x30
Feb  4 15:22:03 mama-tata-laptop kernel: [1.823219]  
i915_pci_probe+0x46/0x60 [i915]
Feb  4 15:22:03 mama-tata-laptop kernel: [1.823229]  
local_pci_probe+0x46/0x90
Feb  4 15:22:03 mama-tata-laptop kernel: [1.823238]  
pci_device_probe+0x11c/0x1a0
Feb  4 15:22:03 mama-tata-laptop kernel: [1.823248]  
driver_probe_device+0x2e3/0x460
Feb  4 15:22:03 mama-tata-laptop kernel: [1.823256]  
__driver_attach+0xe4/0x110
Feb  4 15:22:03 mama-tata-laptop kernel: [1.823263]  ? 
driver_probe_device+0x460/0x460
Feb  4 15:22:03 mama-tata-laptop kernel: [1.823271]  
bus_for_each_dev+0x74/0xb0
Feb  4 15:22:03 mama-tata-laptop kernel: [1.823279]  ? 
kmem_cache_alloc_trace+0x1c4/0x1d0
Feb  4 15:22:03 mama-tata-laptop kernel: [1.823287]  driver_attach+0x1e/0x20
Feb  4 15:22:03 mama-tata-laptop kernel: [1.823294]  
bus_add_driver+0x159/0x230
Feb  4 15:22:03 mama-tata-laptop kernel: [1.823301]  ? 0xc02ec000
Feb  4 15:22:03 mama-tata-laptop kernel: [1.823309]  
driver_register+0x70/0xc0
Feb  4 15:22:03 mama-tata-laptop kernel: [1.823315]  ? 0xc02ec000
Feb  4 15:22:03 mama-tata-laptop kernel: [1.823322]  
__pci_register_driver+0x57/0x60
Feb  4 15:22:03 mama-tata-laptop kernel: [1.823398]  i915_init+0x55/0x58 
[i915]
Feb  4 15:22:03 mama-tata-laptop kernel: [1.823407]  
do_one_initcall+0x4a/0x1c4
Feb  4 15:22:03 mama-tata-laptop kernel: [1.823415]  ? 
_cond_resched+0x19/0x30
Feb  4 15:22:03 mama-tata-laptop kernel: [1.823422]  ? 
kmem_cache_alloc_trace+0xb8/0x1d0
Feb  4 15:22:03 mama-tata-laptop kernel: [1.823430]  ? 
do_init_module+0x27/0x220
Feb  4 15:22:03 mama-tata-laptop kernel: [1.823437]  
do_init_module+0x60/0x220
Feb  4 15:22:03 mama-tata-laptop kernel: [1.823445]  
load_module+0x14f4/0x1890
Feb  4 15:22:03 mama-tata-laptop kernel: [1.823455]  
__do_sys_finit_module+0xbd/0x120
Feb  4 15:22:03 mama-tata-laptop kernel: [1.823462]  ? 
__do_sys_finit_module+0xbd/0x120
Feb  4 15:22:03 mama-tata-laptop kernel: [1.823471]  
__x64_sys_finit_module+0x1a/0x20
Feb  4 15:22:03 mama-tata-laptop kernel: [1.823479]  
do_syscall_64+0x5a/0x110
Feb  4 15:22:03 mama-tata-laptop kernel: [1.823486]  
entry_SYSCALL_64_after_hwframe+0x44/0xa9
Feb  4 15:22:03 mama-tata-laptop kernel: [1.823493] RIP: 

[Kernel-packages] [Bug 1813657] Re: 4.18.0-14 doesn't boot past grub

2019-02-04 Thread Török Edwin
I tried to file a bug, but launchpad keeps timing out (see
https://bugs.launchpad.net/ubuntu/+bug/1814585).

I think I have the same problem on Ubuntu 18.10.
4.18.0-13 was fine, 4.18.0-14 always crashes with BUG on boot.

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

Title:
  4.18.0-14 doesn't boot past grub

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  4.18.0-14 doesn't boot past grub for me in thinkpad t510i. 4.18.0-13
  worked fine. I had to revert back  to 4.15 kernel. I'm using a distro
  that is based off of Ubuntu 18.04.

  System info:
  CPU:Intel(R) Core(TM) i5 CPU   M 520  @ 2.40GHz
  4 cores/threads
  2400.00 MHz
  RAM:7.59 GiB

  I'm not sure how to provide crash info, as the kernel doesn't boot.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux Mint 19.1
  HibernationDevice: RESUME=UUID=fcc2ec6a-a02c-4188-ac0d-a8f924741962
  InstallationDate: Installed on 2019-01-10 (18 days ago)
  InstallationMedia: Linux Mint 19.1 "Tessa" - Release amd64 20181130
  Lsusb:
   Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
   Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 001 Device 003: ID 0a5c:21e8 Broadcom Corp. BCM20702A0 Bluetooth 4.0
   Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 4349BR8
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-44-generic 
root=UUID=3478dfd0-edae-424a-a34f-9f230cb9cacc ro quiet splash
  ProcVersionSignature: Ubuntu 4.15.0-44.47-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-44-generic N/A
   linux-backports-modules-4.15.0-44-generic  N/A
   linux-firmware 1.173.3
  Tags:  tessa
  Uname: Linux 4.15.0-44-generic x86_64
  UnreportableReason: This report is about a package that is not installed.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers wireshark
  _MarkForUpload: False
  dmi.bios.date: 10/26/2010
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 6MET81WW (1.41 )
  dmi.board.name: 4349BR8
  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:bvr6MET81WW(1.41):bd10/26/2010:svnLENOVO:pn4349BR8:pvrThinkPadT510:rvnLENOVO:rn4349BR8:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad T510
  dmi.product.name: 4349BR8
  dmi.product.version: ThinkPad T510
  dmi.sys.vendor: LENOVO

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

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


[Kernel-packages] [Bug 1813657] Re: 4.18.0-14 doesn't boot past grub

2019-02-04 Thread Török Edwin
>From older, working kernels. Note that the FIFO underrun error is
present in these successful boots too (I've been seeing it for years),
but it never crashes before on that.

** Attachment added: "good kern.log"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1813657/+attachment/5235956/+files/kern.log.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/1813657

Title:
  4.18.0-14 doesn't boot past grub

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  4.18.0-14 doesn't boot past grub for me in thinkpad t510i. 4.18.0-13
  worked fine. I had to revert back  to 4.15 kernel. I'm using a distro
  that is based off of Ubuntu 18.04.

  System info:
  CPU:Intel(R) Core(TM) i5 CPU   M 520  @ 2.40GHz
  4 cores/threads
  2400.00 MHz
  RAM:7.59 GiB

  I'm not sure how to provide crash info, as the kernel doesn't boot.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux Mint 19.1
  HibernationDevice: RESUME=UUID=fcc2ec6a-a02c-4188-ac0d-a8f924741962
  InstallationDate: Installed on 2019-01-10 (18 days ago)
  InstallationMedia: Linux Mint 19.1 "Tessa" - Release amd64 20181130
  Lsusb:
   Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
   Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 001 Device 003: ID 0a5c:21e8 Broadcom Corp. BCM20702A0 Bluetooth 4.0
   Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 4349BR8
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-44-generic 
root=UUID=3478dfd0-edae-424a-a34f-9f230cb9cacc ro quiet splash
  ProcVersionSignature: Ubuntu 4.15.0-44.47-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-44-generic N/A
   linux-backports-modules-4.15.0-44-generic  N/A
   linux-firmware 1.173.3
  Tags:  tessa
  Uname: Linux 4.15.0-44-generic x86_64
  UnreportableReason: This report is about a package that is not installed.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers wireshark
  _MarkForUpload: False
  dmi.bios.date: 10/26/2010
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 6MET81WW (1.41 )
  dmi.board.name: 4349BR8
  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:bvr6MET81WW(1.41):bd10/26/2010:svnLENOVO:pn4349BR8:pvrThinkPadT510:rvnLENOVO:rn4349BR8:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad T510
  dmi.product.name: 4349BR8
  dmi.product.version: ThinkPad T510
  dmi.sys.vendor: LENOVO

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

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


[Kernel-packages] [Bug 1742658] Re: linux-generic-hwe-16.04 OOPS in nouveau after security update

2018-12-01 Thread Török Edwin
Hi,

I've been running Ubuntu 18.04 for a while now on this machine, so I do not 
know whether 16.04 would work, it certainly didn't work at all when I filed 
this bugreport.
I would suggest that if anyone else runs into this issue they should upgrade to 
18.04 or 18.10.

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

Title:
  linux-generic-hwe-16.04 OOPS in nouveau after security update

Status in linux package in Ubuntu:
  Confirmed
Status in linux-hwe package in Ubuntu:
  New
Status in linux-hwe-edge package in Ubuntu:
  New
Status in linux-meta-hwe package in Ubuntu:
  New
Status in linux-meta-hwe-edge package in Ubuntu:
  New

Bug description:
  Description:  Ubuntu 16.04.3 LTS
  Release:  16.04

  After upgrading linux-generic-hwe-16.04 to 4.13.0.26.46 I get a black screen 
with nouveau.
  Previously I was running 4.10.0-42-generic, and that kernel still works fine.

  Here is the OOPS:

  an 11 09:39:18 edvin-tower kernel: [3.079986] [drm] Initialized nouveau 
1.3.1 20120801 for :02:00.0 on minor 0
  Jan 11 09:39:18 edvin-tower kernel: [3.100591] BUG: unable to handle 
kernel NULL pointer dereference at   (null)
  Jan 11 09:39:18 edvin-tower kernel: [3.100606] IP:   (null)
  Jan 11 09:39:18 edvin-tower kernel: [3.100610] PGD 0 
  Jan 11 09:39:18 edvin-tower kernel: [3.100611] P4D 0 
  Jan 11 09:39:18 edvin-tower kernel: [3.100615] 
  Jan 11 09:39:18 edvin-tower kernel: [3.100620] Oops: 0010 [#1] SMP PTI
  Jan 11 09:39:18 edvin-tower kernel: [3.100623] Modules linked in: 
hid_generic usbhid hid nouveau mxm_wmi video i2c_algo_bit ttm drm_kms_helper 
syscopyarea sysfillrect e1000e sysimgblt fb_sys_fops drm ptp ahci pps_core 
pata_acpi libahci wmi
  Jan 11 09:39:18 edvin-tower kernel: [3.100643] CPU: 4 PID: 238 Comm: 
kworker/u16:7 Not tainted 4.13.0-26-generic #29~16.04.2-Ubuntu
  Jan 11 09:39:18 edvin-tower kernel: [3.100649] Hardware name: Dell Inc. 
Precision Tower 5810/0K240Y, BIOS A05 12/16/2014
  Jan 11 09:39:18 edvin-tower kernel: [3.100688] Workqueue: nvkm-disp 
gf119_disp_super [nouveau]
  Jan 11 09:39:18 edvin-tower kernel: [3.100694] task: 9d8982d25d00 
task.stack: ac9ec2134000
  Jan 11 09:39:18 edvin-tower kernel: [3.100698] RIP: 0010:  (null)
  Jan 11 09:39:18 edvin-tower kernel: [3.100701] RSP: 0018:ac9ec2137bd8 
EFLAGS: 00010206
  Jan 11 09:39:18 edvin-tower kernel: [3.100706] RAX: c0416f20 RBX: 
 RCX: 0016
  Jan 11 09:39:18 edvin-tower kernel: [3.100710] RDX:  RSI: 
 RDI: 9d898140d180
  Jan 11 09:39:18 edvin-tower kernel: [3.100715] RBP: ac9ec2137c70 R08: 
 R09: 
  Jan 11 09:39:18 edvin-tower kernel: [3.100719] R10: 1000 R11: 
 R12: 
  Jan 11 09:39:18 edvin-tower kernel: [3.100724] R13:  R14: 
ac9ec2137d00 R15: 9d898c542600
  Jan 11 09:39:18 edvin-tower kernel: [3.100728] FS:  
() GS:9d899fd0() knlGS:
  Jan 11 09:39:18 edvin-tower kernel: [3.100733] CS:  0010 DS:  ES: 
 CR0: 80050033
  Jan 11 09:39:18 edvin-tower kernel: [3.100737] CR2:  CR3: 
00029ac0a006 CR4: 001606e0
  Jan 11 09:39:18 edvin-tower kernel: [3.100742] Call Trace:
  Jan 11 09:39:18 edvin-tower kernel: [3.100771]  ? 
nvkm_dp_train_drive+0x214/0x300 [nouveau]
  Jan 11 09:39:18 edvin-tower kernel: [3.100798]  nvkm_dp_train+0x582/0x970 
[nouveau]
  Jan 11 09:39:18 edvin-tower kernel: [3.100824]  
nvkm_dp_acquire+0xd4/0x390 [nouveau]
  Jan 11 09:39:18 edvin-tower kernel: [3.100850]  
nv50_disp_super_2_2+0x6d/0x430 [nouveau]
  Jan 11 09:39:18 edvin-tower kernel: [3.100872]  ? 
nvkm_devinit_pll_set+0xf/0x20 [nouveau]
  Jan 11 09:39:18 edvin-tower kernel: [3.100897]  
gf119_disp_super+0x1b7/0x300 [nouveau]
  Jan 11 09:39:18 edvin-tower kernel: [3.100904]  ? __schedule+0x3ca/0x890
  Jan 11 09:39:18 edvin-tower kernel: [3.100911]  
process_one_work+0x156/0x410
  Jan 11 09:39:18 edvin-tower kernel: [3.100915]  worker_thread+0x4b/0x460
  Jan 11 09:39:18 edvin-tower kernel: [3.100920]  kthread+0x109/0x140
  Jan 11 09:39:18 edvin-tower kernel: [3.100924]  ? 
process_one_work+0x410/0x410
  Jan 11 09:39:18 edvin-tower kernel: [3.100928]  ? 
kthread_create_on_node+0x70/0x70
  Jan 11 09:39:18 edvin-tower kernel: [3.100934]  ret_from_fork+0x1f/0x30
  Jan 11 09:39:18 edvin-tower kernel: [3.100938] Code:  Bad RIP value.
  Jan 11 09:39:18 edvin-tower kernel: [3.100944] RIP:   (null) RSP: 
ac9ec2137bd8
  Jan 11 09:39:18 edvin-tower kernel: [3.100948] CR2: 
  Jan 11 09:39:18 edvin-tower kernel: [3.100952] ---[ end trace 
93a79dae0d3ec749 

[Kernel-packages] [Bug 1696240] Re: linux 4.10 and AMD Polaris11 card -> graphics crash

2017-06-07 Thread Török Edwin
Ubuntu 4.10.0-22-generic: crash
mainline 4.10.17: crash
mainline 4.11.3: OK

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

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

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

Title:
  linux 4.10 and AMD Polaris11 card -> graphics crash

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

Bug description:
  Using 4.10.0-22-generic from Ubuntu and running any of the Unigine benchmarks 
(Heaven-4.0, Valley-1.0, Superposition-1.0) causes the screen to go black and 
the graphics system to crash.
  The graphics card's fan stops working and sensors reports 511C, clearly wrong.

  I can still login via SSH and attempt to stop X, however the
  application (e.g. heaven) just remains in a zombie state and the
  system is unusable, I can't start X again. In fact the graphics card
  ends up in a pretty bad state, because if I press the reset button the
  UEFI BIOS is not able to detect it anymore, I have to power the whole
  system off and on again to make the card work.

  Upgrading to mainline 4.11.3 avoids this problem: all 3 benchmarks are
  running fine, with no crashes.

  I've attached two dmesgs: one with the default, where IOMMU is on and I get 
lots of AMD-Vi warnings logged:
  [  439.903842] [ cut here ]
  [  439.903848] WARNING: CPU: 5 PID: 0 at 
/build/linux-nOqmtv/linux-4.10.0/drivers/iommu/amd_iommu.c:1252 
__domain_flush_pages+0x1f7/0x220
  [  439.903848] Modules linked in: overlay ccm 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 nls_iso8859_1 eeepc_wmi asus_wmi 
sparse_keymap video edac_mce_amd edac_core kvm_amd kvm irqbypass 
crct10dif_pclmul crc32_pclmul ghash_clmulni_intel pcbc aesni_intel 
snd_hda_codec_realtek arc4 aes_x86_64 crypto_simd glue_helper cryptd 
snd_hda_codec_generic ath9k snd_hda_codec_hdmi ath9k_common ath9k_hw 
snd_hda_intel snd_hda_codec snd_hda_core ath snd_hwdep input_leds joydev 
mac80211 snd_pcm snd_seq_midi snd_seq_midi_event snd_rawmidi cfg80211 snd_seq 
fam15h_power i2c_piix4 snd_seq_device
  [  439.903873]  snd_timer snd k10temp mac_hid soundcore tpm_infineon shpchp 
tcp_bbr sch_fq cuse parport_pc ppdev lp parport ip_tables x_tables autofs4 
btrfs raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx 
xor raid6_pq libcrc32c raid1 raid0 multipath linear hid_generic usbhid hid 
amdkfd amd_iommu_v2 amdgpu mxm_wmi i2c_algo_bit ttm drm_kms_helper syscopyarea 
sysfillrect r8169 sysimgblt fb_sys_fops mii drm ahci libahci fjes wmi
  [  439.903893] CPU: 5 PID: 0 Comm: swapper/5 Not tainted 4.10.0-22-generic 
#24-Ubuntu
  [  439.903894] Hardware name: To be filled by O.E.M. To be filled by 
O.E.M./M5A99FX PRO R2.0, BIOS 2501 04/07/2014
  [  439.903895] Call Trace:
  [  439.903896]  
  [  439.903899]  dump_stack+0x63/0x81
  [  439.903900]  __warn+0xcb/0xf0
  [  439.903901]  warn_slowpath_null+0x1d/0x20
  [  439.903903]  __domain_flush_pages+0x1f7/0x220
  [  439.903904]  __queue_flush+0x4b/0xd0
  [  439.903905]  ? queue_flush_all+0x90/0x90
  [  439.903907]  queue_flush_all+0x77/0x90
  [  439.903908]  queue_flush_timeout+0x18/0x20
  [  439.903910]  call_timer_fn+0x35/0x140
  [  439.903911]  run_timer_softirq+0x215/0x4b0
  [  439.903912]  ? ktime_get+0x41/0xb0
  [  439.903914]  ? lapic_next_event+0x1d/0x30
  [  439.903916]  ? clockevents_program_event+0x7f/0x120
  [  439.903918]  __do_softirq+0x104/0x2af
  [  439.903919]  irq_exit+0xb6/0xc0
  [  439.903921]  smp_apic_timer_interrupt+0x3d/0x50
  [  439.903922]  apic_timer_interrupt+0x89/0x90
  [  439.903924] RIP: 0010:cpuidle_enter_state+0x122/0x2c0
  [  439.903925] RSP: 0018:b4e181a23e58 EFLAGS: 0246 ORIG_RAX: 
ff10
  [  439.903926] RAX:  RBX: 0002 RCX: 
001f
  [  439.903926] RDX: 006665f96c97 RSI: 9dbcded56a98 RDI: 

  [  439.903927] RBP: b4e181a23e98 R08: cccd R09: 
0018
  [  439.903927] R10: 0da8 R11: 3557 R12: 
9dbcd036b600
  [  439.903928] R13: baeeba38 R14: 0002 R15: 
baeeba20
  [  439.903929]  
  [  439.903930]  ? cpuidle_enter_state+0x110/0x2c0
  [  439.903931]  cpuidle_enter+0x17/0x20
  [  439.903933]  call_cpuidle+0x23/0x40
  [  439.903934]  do_idle+0x189/0x200
  [  439.903935]  cpu_startup_entry+0x71/0x80
  [  439.903937]  start_secondary+0x154/0x190
  [  439.903938]  start_cpu+0x14/0x14
  [  439.903939] ---[ end trace 9edd64d3e01a6c8c ]---

  And another one with iommu=soft boot 

[Kernel-packages] [Bug 1696240] [NEW] linux 4.10 and AMD Polaris11 card -> graphics crash

2017-06-06 Thread Török Edwin
Public bug reported:

Using 4.10.0-22-generic from Ubuntu and running any of the Unigine benchmarks 
(Heaven-4.0, Valley-1.0, Superposition-1.0) causes the screen to go black and 
the graphics system to crash.
The graphics card's fan stops working and sensors reports 511C, clearly wrong.

I can still login via SSH and attempt to stop X, however the application
(e.g. heaven) just remains in a zombie state and the system is unusable,
I can't start X again. In fact the graphics card ends up in a pretty bad
state, because if I press the reset button the UEFI BIOS is not able to
detect it anymore, I have to power the whole system off and on again to
make the card work.

Upgrading to mainline 4.11.3 avoids this problem: all 3 benchmarks are
running fine, with no crashes.

I've attached two dmesgs: one with the default, where IOMMU is on and I get 
lots of AMD-Vi warnings logged:
[  439.903842] [ cut here ]
[  439.903848] WARNING: CPU: 5 PID: 0 at 
/build/linux-nOqmtv/linux-4.10.0/drivers/iommu/amd_iommu.c:1252 
__domain_flush_pages+0x1f7/0x220
[  439.903848] Modules linked in: overlay ccm 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 nls_iso8859_1 eeepc_wmi asus_wmi 
sparse_keymap video edac_mce_amd edac_core kvm_amd kvm irqbypass 
crct10dif_pclmul crc32_pclmul ghash_clmulni_intel pcbc aesni_intel 
snd_hda_codec_realtek arc4 aes_x86_64 crypto_simd glue_helper cryptd 
snd_hda_codec_generic ath9k snd_hda_codec_hdmi ath9k_common ath9k_hw 
snd_hda_intel snd_hda_codec snd_hda_core ath snd_hwdep input_leds joydev 
mac80211 snd_pcm snd_seq_midi snd_seq_midi_event snd_rawmidi cfg80211 snd_seq 
fam15h_power i2c_piix4 snd_seq_device
[  439.903873]  snd_timer snd k10temp mac_hid soundcore tpm_infineon shpchp 
tcp_bbr sch_fq cuse parport_pc ppdev lp parport ip_tables x_tables autofs4 
btrfs raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx 
xor raid6_pq libcrc32c raid1 raid0 multipath linear hid_generic usbhid hid 
amdkfd amd_iommu_v2 amdgpu mxm_wmi i2c_algo_bit ttm drm_kms_helper syscopyarea 
sysfillrect r8169 sysimgblt fb_sys_fops mii drm ahci libahci fjes wmi
[  439.903893] CPU: 5 PID: 0 Comm: swapper/5 Not tainted 4.10.0-22-generic 
#24-Ubuntu
[  439.903894] Hardware name: To be filled by O.E.M. To be filled by 
O.E.M./M5A99FX PRO R2.0, BIOS 2501 04/07/2014
[  439.903895] Call Trace:
[  439.903896]  
[  439.903899]  dump_stack+0x63/0x81
[  439.903900]  __warn+0xcb/0xf0
[  439.903901]  warn_slowpath_null+0x1d/0x20
[  439.903903]  __domain_flush_pages+0x1f7/0x220
[  439.903904]  __queue_flush+0x4b/0xd0
[  439.903905]  ? queue_flush_all+0x90/0x90
[  439.903907]  queue_flush_all+0x77/0x90
[  439.903908]  queue_flush_timeout+0x18/0x20
[  439.903910]  call_timer_fn+0x35/0x140
[  439.903911]  run_timer_softirq+0x215/0x4b0
[  439.903912]  ? ktime_get+0x41/0xb0
[  439.903914]  ? lapic_next_event+0x1d/0x30
[  439.903916]  ? clockevents_program_event+0x7f/0x120
[  439.903918]  __do_softirq+0x104/0x2af
[  439.903919]  irq_exit+0xb6/0xc0
[  439.903921]  smp_apic_timer_interrupt+0x3d/0x50
[  439.903922]  apic_timer_interrupt+0x89/0x90
[  439.903924] RIP: 0010:cpuidle_enter_state+0x122/0x2c0
[  439.903925] RSP: 0018:b4e181a23e58 EFLAGS: 0246 ORIG_RAX: 
ff10
[  439.903926] RAX:  RBX: 0002 RCX: 001f
[  439.903926] RDX: 006665f96c97 RSI: 9dbcded56a98 RDI: 
[  439.903927] RBP: b4e181a23e98 R08: cccd R09: 0018
[  439.903927] R10: 0da8 R11: 3557 R12: 9dbcd036b600
[  439.903928] R13: baeeba38 R14: 0002 R15: baeeba20
[  439.903929]  
[  439.903930]  ? cpuidle_enter_state+0x110/0x2c0
[  439.903931]  cpuidle_enter+0x17/0x20
[  439.903933]  call_cpuidle+0x23/0x40
[  439.903934]  do_idle+0x189/0x200
[  439.903935]  cpu_startup_entry+0x71/0x80
[  439.903937]  start_secondary+0x154/0x190
[  439.903938]  start_cpu+0x14/0x14
[  439.903939] ---[ end trace 9edd64d3e01a6c8c ]---

And another one with iommu=soft boot option, where nothing interesting
in dmesg shows up, but the system still crashes.

Note: if I turn IOMMU off completely then USB devices are not working
and I cannot use my keyboard/mouse so I cannot test that scenario.

ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: linux-image-generic 4.10.0.22.24
ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15
Uname: Linux 4.10.0-22-generic x86_64
ApportVersion: 2.20.4-0ubuntu4.1
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  edwin  2753 F pulseaudio
 /dev/snd/controlC2:  edwin  2753 F pulseaudio
 /dev/snd/controlC1:  edwin  2753 F pulseaudio
Date: Tue Jun  6 21:09:45 

[Kernel-packages] [Bug 1696240] Re: linux 4.10 and AMD Polaris11 card -> graphics crash

2017-06-06 Thread Török Edwin
** Attachment added: "dmesg IOMMU=soft"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1696240/+attachment/4890325/+files/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/1696240

Title:
  linux 4.10 and AMD Polaris11 card -> graphics crash

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Using 4.10.0-22-generic from Ubuntu and running any of the Unigine benchmarks 
(Heaven-4.0, Valley-1.0, Superposition-1.0) causes the screen to go black and 
the graphics system to crash.
  The graphics card's fan stops working and sensors reports 511C, clearly wrong.

  I can still login via SSH and attempt to stop X, however the
  application (e.g. heaven) just remains in a zombie state and the
  system is unusable, I can't start X again. In fact the graphics card
  ends up in a pretty bad state, because if I press the reset button the
  UEFI BIOS is not able to detect it anymore, I have to power the whole
  system off and on again to make the card work.

  Upgrading to mainline 4.11.3 avoids this problem: all 3 benchmarks are
  running fine, with no crashes.

  I've attached two dmesgs: one with the default, where IOMMU is on and I get 
lots of AMD-Vi warnings logged:
  [  439.903842] [ cut here ]
  [  439.903848] WARNING: CPU: 5 PID: 0 at 
/build/linux-nOqmtv/linux-4.10.0/drivers/iommu/amd_iommu.c:1252 
__domain_flush_pages+0x1f7/0x220
  [  439.903848] Modules linked in: overlay ccm 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 nls_iso8859_1 eeepc_wmi asus_wmi 
sparse_keymap video edac_mce_amd edac_core kvm_amd kvm irqbypass 
crct10dif_pclmul crc32_pclmul ghash_clmulni_intel pcbc aesni_intel 
snd_hda_codec_realtek arc4 aes_x86_64 crypto_simd glue_helper cryptd 
snd_hda_codec_generic ath9k snd_hda_codec_hdmi ath9k_common ath9k_hw 
snd_hda_intel snd_hda_codec snd_hda_core ath snd_hwdep input_leds joydev 
mac80211 snd_pcm snd_seq_midi snd_seq_midi_event snd_rawmidi cfg80211 snd_seq 
fam15h_power i2c_piix4 snd_seq_device
  [  439.903873]  snd_timer snd k10temp mac_hid soundcore tpm_infineon shpchp 
tcp_bbr sch_fq cuse parport_pc ppdev lp parport ip_tables x_tables autofs4 
btrfs raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx 
xor raid6_pq libcrc32c raid1 raid0 multipath linear hid_generic usbhid hid 
amdkfd amd_iommu_v2 amdgpu mxm_wmi i2c_algo_bit ttm drm_kms_helper syscopyarea 
sysfillrect r8169 sysimgblt fb_sys_fops mii drm ahci libahci fjes wmi
  [  439.903893] CPU: 5 PID: 0 Comm: swapper/5 Not tainted 4.10.0-22-generic 
#24-Ubuntu
  [  439.903894] Hardware name: To be filled by O.E.M. To be filled by 
O.E.M./M5A99FX PRO R2.0, BIOS 2501 04/07/2014
  [  439.903895] Call Trace:
  [  439.903896]  
  [  439.903899]  dump_stack+0x63/0x81
  [  439.903900]  __warn+0xcb/0xf0
  [  439.903901]  warn_slowpath_null+0x1d/0x20
  [  439.903903]  __domain_flush_pages+0x1f7/0x220
  [  439.903904]  __queue_flush+0x4b/0xd0
  [  439.903905]  ? queue_flush_all+0x90/0x90
  [  439.903907]  queue_flush_all+0x77/0x90
  [  439.903908]  queue_flush_timeout+0x18/0x20
  [  439.903910]  call_timer_fn+0x35/0x140
  [  439.903911]  run_timer_softirq+0x215/0x4b0
  [  439.903912]  ? ktime_get+0x41/0xb0
  [  439.903914]  ? lapic_next_event+0x1d/0x30
  [  439.903916]  ? clockevents_program_event+0x7f/0x120
  [  439.903918]  __do_softirq+0x104/0x2af
  [  439.903919]  irq_exit+0xb6/0xc0
  [  439.903921]  smp_apic_timer_interrupt+0x3d/0x50
  [  439.903922]  apic_timer_interrupt+0x89/0x90
  [  439.903924] RIP: 0010:cpuidle_enter_state+0x122/0x2c0
  [  439.903925] RSP: 0018:b4e181a23e58 EFLAGS: 0246 ORIG_RAX: 
ff10
  [  439.903926] RAX:  RBX: 0002 RCX: 
001f
  [  439.903926] RDX: 006665f96c97 RSI: 9dbcded56a98 RDI: 

  [  439.903927] RBP: b4e181a23e98 R08: cccd R09: 
0018
  [  439.903927] R10: 0da8 R11: 3557 R12: 
9dbcd036b600
  [  439.903928] R13: baeeba38 R14: 0002 R15: 
baeeba20
  [  439.903929]  
  [  439.903930]  ? cpuidle_enter_state+0x110/0x2c0
  [  439.903931]  cpuidle_enter+0x17/0x20
  [  439.903933]  call_cpuidle+0x23/0x40
  [  439.903934]  do_idle+0x189/0x200
  [  439.903935]  cpu_startup_entry+0x71/0x80
  [  439.903937]  start_secondary+0x154/0x190
  [  439.903938]  start_cpu+0x14/0x14
  [  439.903939] ---[ end trace 9edd64d3e01a6c8c ]---

  And another one with iommu=soft boot option, where nothing interesting
  in dmesg shows up, but the system still crashes.

  Note: if I turn IOMMU off completely then USB devices are not working
  and I cannot use my 

[Kernel-packages] [Bug 1683157] Re: Ethernet, WiFi, touchpad/trackpoint not detected on boot

2017-04-28 Thread Török Edwin
Unfortunately I am not able to reproduce this anymore.
On the day I reported the bug I was able to reproduce it multiple times, next 
day I tried the mainline kernel, it worked, installed back the old kernel and 
again it worked. That was the only package that changed.
Tried a few more times to reproduce the bug since, but no luck.
I thought maybe its bad RAM, but I've run a few memtest cycles and it passed.

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

Title:
  Ethernet, WiFi, touchpad/trackpoint not detected on boot

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  This is a regression from Ubuntu 16.10. I have upgraded this Lenovo
  X300 yesterday, and noticed this bug:

  Steps to reproduce:
   * turn laptop off completely, unplug power
   * plug in power
   * turn on laptop, and boot Xubuntu 17.04
   * Login

  Expected results:
   * Connected to internet, able to use touchpad/trackpoint

  Actual results:
   * At least 1 time out of 4 a lot of devices are not detected during boot
   * There is no WiFi device
   * There is no touchpad/trackpoint device (plugging in an external mouse 
works)
   * Keyboard still works

  Workaround:
   * sudo udevadm trigger
   * all devices get detected and working

  Also reproducible when running on battery.
  Note: I've only seen this bug on this device, my 2 other devices (a Dell 
Latitude E7470 laptop, and an AMD FX desktop) do not have this bug.

  See attached tarball for lspci/lsusb/dmesg/journal outputs from a
  good, and 3 bad boots.

  Here is what happens after udevadm trigger, but the kernel should be able to 
detect all this on its own during boot, without needing a manual udevadm 
trigger!
  [  244.902251] pps_core: LinuxPPS API ver. 1 registered
  [  244.902253] pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo 
Giometti 
  [  244.930231] PTP clock support registered
  [  244.954346] e1000e: Intel(R) PRO/1000 Network Driver - 3.2.6-k
  [  244.954349] e1000e: Copyright(c) 1999 - 2015 Intel Corporation.
  [  244.954711] e1000e :00:19.0: Interrupt Throttling Rate (ints/sec) set 
to dynamic conservative mode
  [  244.966799] FUJITSU Extended Socket Network Device Driver - version 1.2 - 
Copyright (c) 2015 FUJITSU LIMITED
  [  245.345396] Bluetooth: Core ver 2.22
  [  245.345430] NET: Registered protocol family 31
  [  245.345432] Bluetooth: HCI device and connection manager initialized
  [  245.345438] Bluetooth: HCI socket layer initialized
  [  245.345443] Bluetooth: L2CAP socket layer initialized
  [  245.345455] Bluetooth: SCO socket layer initialized
  [  245.478228] usbcore: registered new interface driver btusb
  [  245.681594] media: Linux media interface: v0.10
  [  245.717154] e1000e :00:19.0 eth0: (PCI Express:2.5GT/s:Width x1) 
00:1f:e2:1c:46:e5
  [  245.717159] e1000e :00:19.0 eth0: Intel(R) PRO/1000 Network Connection
  [  245.718968] e1000e :00:19.0 eth0: MAC: 6, PHY: 6, PBA No: 1008FF-0FF
  [  245.719439] shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
  [  245.728940] snd_hda_intel :00:1b.0: probe_mask set to 0x1 for device 
17aa:20ac
  [  245.731649] ACPI Warning: SystemIO range 
0x1028-0x102F conflicts with OpRegion 
0x1000-0x107F (\_SB.PCI0.LPC.PMIO) 
(20160930/utaddress-247)
  [  245.731659] ACPI: If an ACPI driver is available for this device, you 
should use it instead of the native driver
  [  245.731666] ACPI Warning: SystemIO range 
0x11B0-0x11BF conflicts with OpRegion 
0x1180-0x11BF (\_SB.PCI0.LPC.LPIO) 
(20160930/utaddress-247)
  [  245.731673] ACPI: If an ACPI driver is available for this device, you 
should use it instead of the native driver
  [  245.731675] ACPI Warning: SystemIO range 
0x1180-0x11AF conflicts with OpRegion 
0x1180-0x11BF (\_SB.PCI0.LPC.LPIO) 
(20160930/utaddress-247)
  [  245.731682] ACPI: If an ACPI driver is available for this device, you 
should use it instead of the native driver
  [  245.731683] lpc_ich: Resource conflict(s) found affecting gpio_ich
  [  245.811261] Linux video capture interface: v2.00
  [  245.852532] Non-volatile memory driver v1.3
  [  245.859889] thinkpad_acpi: ThinkPad ACPI Extras v0.25
  [  245.859891] thinkpad_acpi: http://ibm-acpi.sf.net/
  [  245.859893] thinkpad_acpi: ThinkPad BIOS 7TET36WW (1.10 ), EC 7THT16WW-1.01
  [  245.859895] thinkpad_acpi: Lenovo ThinkPad X300, model 647814G
  [  245.916791] thinkpad_hwmon thinkpad_hwmon: hwmon_device_register() is 
deprecated. Please convert the driver to use hwmon_device_register_with_info().
  [  245.942778] thinkpad_acpi: radio switch found; radios are enabled
  [  245.942815] thinkpad_acpi: This ThinkPad has standard ACPI backlight 
brightness control, supported by the ACPI video driver
  [ 

[Kernel-packages] [Bug 1683157] [NEW] Ethernet, WiFi, touchpad/trackpoint not detected on boot

2017-04-16 Thread Török Edwin
Public bug reported:

This is a regression from Ubuntu 16.10. I have upgraded this Lenovo X300
yesterday, and noticed this bug:

Steps to reproduce:
 * turn laptop off completely, unplug power
 * plug in power
 * turn on laptop, and boot Xubuntu 17.04
 * Login

Expected results:
 * Connected to internet, able to use touchpad/trackpoint

Actual results:
 * At least 1 time out of 4 a lot of devices are not detected during boot
 * There is no WiFi device
 * There is no touchpad/trackpoint device (plugging in an external mouse works)
 * Keyboard still works

Workaround:
 * sudo udevadm trigger
 * all devices get detected and working

Also reproducible when running on battery.
Note: I've only seen this bug on this device, my 2 other devices (a Dell 
Latitude E7470 laptop, and an AMD FX desktop) do not have this bug.

See attached tarball for lspci/lsusb/dmesg/journal outputs from a good,
and 3 bad boots.

Here is what happens after udevadm trigger, but the kernel should be able to 
detect all this on its own during boot, without needing a manual udevadm 
trigger!
[  244.902251] pps_core: LinuxPPS API ver. 1 registered
[  244.902253] pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo 
Giometti 
[  244.930231] PTP clock support registered
[  244.954346] e1000e: Intel(R) PRO/1000 Network Driver - 3.2.6-k
[  244.954349] e1000e: Copyright(c) 1999 - 2015 Intel Corporation.
[  244.954711] e1000e :00:19.0: Interrupt Throttling Rate (ints/sec) set to 
dynamic conservative mode
[  244.966799] FUJITSU Extended Socket Network Device Driver - version 1.2 - 
Copyright (c) 2015 FUJITSU LIMITED
[  245.345396] Bluetooth: Core ver 2.22
[  245.345430] NET: Registered protocol family 31
[  245.345432] Bluetooth: HCI device and connection manager initialized
[  245.345438] Bluetooth: HCI socket layer initialized
[  245.345443] Bluetooth: L2CAP socket layer initialized
[  245.345455] Bluetooth: SCO socket layer initialized
[  245.478228] usbcore: registered new interface driver btusb
[  245.681594] media: Linux media interface: v0.10
[  245.717154] e1000e :00:19.0 eth0: (PCI Express:2.5GT/s:Width x1) 
00:1f:e2:1c:46:e5
[  245.717159] e1000e :00:19.0 eth0: Intel(R) PRO/1000 Network Connection
[  245.718968] e1000e :00:19.0 eth0: MAC: 6, PHY: 6, PBA No: 1008FF-0FF
[  245.719439] shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
[  245.728940] snd_hda_intel :00:1b.0: probe_mask set to 0x1 for device 
17aa:20ac
[  245.731649] ACPI Warning: SystemIO range 
0x1028-0x102F conflicts with OpRegion 
0x1000-0x107F (\_SB.PCI0.LPC.PMIO) 
(20160930/utaddress-247)
[  245.731659] ACPI: If an ACPI driver is available for this device, you should 
use it instead of the native driver
[  245.731666] ACPI Warning: SystemIO range 
0x11B0-0x11BF conflicts with OpRegion 
0x1180-0x11BF (\_SB.PCI0.LPC.LPIO) 
(20160930/utaddress-247)
[  245.731673] ACPI: If an ACPI driver is available for this device, you should 
use it instead of the native driver
[  245.731675] ACPI Warning: SystemIO range 
0x1180-0x11AF conflicts with OpRegion 
0x1180-0x11BF (\_SB.PCI0.LPC.LPIO) 
(20160930/utaddress-247)
[  245.731682] ACPI: If an ACPI driver is available for this device, you should 
use it instead of the native driver
[  245.731683] lpc_ich: Resource conflict(s) found affecting gpio_ich
[  245.811261] Linux video capture interface: v2.00
[  245.852532] Non-volatile memory driver v1.3
[  245.859889] thinkpad_acpi: ThinkPad ACPI Extras v0.25
[  245.859891] thinkpad_acpi: http://ibm-acpi.sf.net/
[  245.859893] thinkpad_acpi: ThinkPad BIOS 7TET36WW (1.10 ), EC 7THT16WW-1.01
[  245.859895] thinkpad_acpi: Lenovo ThinkPad X300, model 647814G
[  245.916791] thinkpad_hwmon thinkpad_hwmon: hwmon_device_register() is 
deprecated. Please convert the driver to use hwmon_device_register_with_info().
[  245.942778] thinkpad_acpi: radio switch found; radios are enabled
[  245.942815] thinkpad_acpi: This ThinkPad has standard ACPI backlight 
brightness control, supported by the ACPI video driver
[  245.942816] thinkpad_acpi: Disabling thinkpad-acpi brightness events by 
default...
[  245.984287] thinkpad_acpi: rfkill switch tpacpi_bluetooth_sw: radio is 
unblocked
[  246.024641] thinkpad_acpi: Standard ACPI backlight interface available, not 
loading native one
[  246.049036] input: ThinkPad Extra Buttons as 
/devices/platform/thinkpad_acpi/input/input7
[  246.140510] snd_hda_codec_analog hdaudioC0D0: autoconfig for AD1984A: 
line_outs=1 (0x12/0x0/0x0/0x0/0x0) type:speaker
[  246.140514] snd_hda_codec_analog hdaudioC0D0:speaker_outs=0 
(0x0/0x0/0x0/0x0/0x0)
[  246.140518] snd_hda_codec_analog hdaudioC0D0:hp_outs=1 
(0x11/0x0/0x0/0x0/0x0)
[  246.140521] snd_hda_codec_analog hdaudioC0D0:mono: mono_out=0x0
[  246.140524] snd_hda_codec_analog hdaudioC0D0:inputs:
[  246.140528] 

[Kernel-packages] [Bug 1678303] Re: Full system freeze: kernel BUG at /build/linux-7LGLH_/linux-4.10.0/include/linux/swapops.h:129!

2017-03-31 Thread Török Edwin
*** This bug is a duplicate of bug 1674838 ***
https://bugs.launchpad.net/bugs/1674838

Possible related to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1674838 and
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1677611

** This bug has been marked a duplicate of bug 1674838
   kernel BUG at /build/linux-7LGLH_/linux-4.10.0/include/linux/swapops.h:129

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

Title:
  Full system freeze: kernel BUG at /build/linux-
  7LGLH_/linux-4.10.0/include/linux/swapops.h:129!

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Installed Ubuntu 17.04 beta, was logged in to Mate, had Chromium, 
Thunderbird, and a terminal with Vim running.
  I was switching back and forth between Vim and the browser when the whole 
system just froze.
  The desktop didn't react to mouse/keyboard, not even to 
Ctrl+Alt+F1..Ctrl+Alt+F7.
  It did react to SysRQ though: alt+printscreen+s, alt+printscreen+u, 
alt+printscreen+b, alt+printscreen+b.

  Upon reboot I've seen this kernel error in /var/log/kern.log (see attachment 
for full details):
  Mar 31 19:48:30 bolt kernel: [ 1638.798821] kernel BUG at 
/build/linux-7LGLH_/linux-4.10.0/include/linux/swapops.h:12
  [...]
  Mar 31 19:48:30 bolt kernel: [ 1638.799326] Call Trace:
  Mar 31 19:48:30 bolt kernel: [ 1638.799336]  migration_entry_wait+0x74/0x80
  Mar 31 19:48:30 bolt kernel: [ 1638.799350]  do_swap_page+0x5b3/0x770
  Mar 31 19:48:30 bolt kernel: [ 1638.799362]  handle_mm_fault+0x873/0x1360
  Mar 31 19:48:30 bolt kernel: [ 1638.799375]  __do_page_fault+0x23e/0x4e0
  Mar 31 19:48:30 bolt kernel: [ 1638.799387]  do_page_fault+0x22/0x30
  Mar 31 19:48:30 bolt kernel: [ 1638.799399]  page_fault+0x28/0x30
  [...]

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: linux-image-4.10.0-14-generic 4.10.0-14.16
  ProcVersionSignature: Ubuntu 4.10.0-14.16-generic 4.10.3
  Uname: Linux 4.10.0-14-generic x86_64
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  edwin  1610 F pulseaudio
   /dev/snd/controlC1:  edwin  1610 F pulseaudio
  CurrentDesktop: MATE
  Date: Fri Mar 31 20:56:15 2017
  HibernationDevice: RESUME=UUID=3401e45a-9619-4ae8-9e4d-6dc1e7982524
  InstallationDate: Installed on 2017-03-25 (5 days ago)
  InstallationMedia: Ubuntu-MATE 17.04 "Zesty Zapus" - Beta amd64 (20170321.1)
  MachineType: To be filled by O.E.M. To be filled by O.E.M.
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-14-generic.efi.signed 
root=/dev/mapper/ubuntu--mate--vg-root ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-14-generic N/A
   linux-backports-modules-4.10.0-14-generic  N/A
   linux-firmware 1.164
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/07/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2501
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: M5A99FX PRO R2.0
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  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.:bvr2501:bd04/07/2014:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKCOMPUTERINC.:rnM5A99FXPROR2.0:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.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/1678303/+subscriptions

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


[Kernel-packages] [Bug 1678303] [NEW] Full system freeze: kernel BUG at /build/linux-7LGLH_/linux-4.10.0/include/linux/swapops.h:129!

2017-03-31 Thread Török Edwin
*** This bug is a duplicate of bug 1674838 ***
https://bugs.launchpad.net/bugs/1674838

Public bug reported:

Installed Ubuntu 17.04 beta, was logged in to Mate, had Chromium, Thunderbird, 
and a terminal with Vim running.
I was switching back and forth between Vim and the browser when the whole 
system just froze.
The desktop didn't react to mouse/keyboard, not even to 
Ctrl+Alt+F1..Ctrl+Alt+F7.
It did react to SysRQ though: alt+printscreen+s, alt+printscreen+u, 
alt+printscreen+b, alt+printscreen+b.

Upon reboot I've seen this kernel error in /var/log/kern.log (see attachment 
for full details):
Mar 31 19:48:30 bolt kernel: [ 1638.798821] kernel BUG at 
/build/linux-7LGLH_/linux-4.10.0/include/linux/swapops.h:12
[...]
Mar 31 19:48:30 bolt kernel: [ 1638.799326] Call Trace:
Mar 31 19:48:30 bolt kernel: [ 1638.799336]  migration_entry_wait+0x74/0x80
Mar 31 19:48:30 bolt kernel: [ 1638.799350]  do_swap_page+0x5b3/0x770
Mar 31 19:48:30 bolt kernel: [ 1638.799362]  handle_mm_fault+0x873/0x1360
Mar 31 19:48:30 bolt kernel: [ 1638.799375]  __do_page_fault+0x23e/0x4e0
Mar 31 19:48:30 bolt kernel: [ 1638.799387]  do_page_fault+0x22/0x30
Mar 31 19:48:30 bolt kernel: [ 1638.799399]  page_fault+0x28/0x30
[...]

ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: linux-image-4.10.0-14-generic 4.10.0-14.16
ProcVersionSignature: Ubuntu 4.10.0-14.16-generic 4.10.3
Uname: Linux 4.10.0-14-generic x86_64
ApportVersion: 2.20.4-0ubuntu2
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  edwin  1610 F pulseaudio
 /dev/snd/controlC1:  edwin  1610 F pulseaudio
CurrentDesktop: MATE
Date: Fri Mar 31 20:56:15 2017
HibernationDevice: RESUME=UUID=3401e45a-9619-4ae8-9e4d-6dc1e7982524
InstallationDate: Installed on 2017-03-25 (5 days ago)
InstallationMedia: Ubuntu-MATE 17.04 "Zesty Zapus" - Beta amd64 (20170321.1)
MachineType: To be filled by O.E.M. To be filled by O.E.M.
ProcFB: 0 radeondrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-14-generic.efi.signed 
root=/dev/mapper/ubuntu--mate--vg-root ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-4.10.0-14-generic N/A
 linux-backports-modules-4.10.0-14-generic  N/A
 linux-firmware 1.164
RfKill:
 0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/07/2014
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 2501
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: M5A99FX PRO R2.0
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev 1.xx
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.:bvr2501:bd04/07/2014:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKCOMPUTERINC.:rnM5A99FXPROR2.0:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.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.

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


** Tags: amd64 apport-bug zesty

** Attachment added: "x"
   https://bugs.launchpad.net/bugs/1678303/+attachment/4851598/+files/x

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

Title:
  Full system freeze: kernel BUG at /build/linux-
  7LGLH_/linux-4.10.0/include/linux/swapops.h:129!

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Installed Ubuntu 17.04 beta, was logged in to Mate, had Chromium, 
Thunderbird, and a terminal with Vim running.
  I was switching back and forth between Vim and the browser when the whole 
system just froze.
  The desktop didn't react to mouse/keyboard, not even to 
Ctrl+Alt+F1..Ctrl+Alt+F7.
  It did react to SysRQ though: alt+printscreen+s, alt+printscreen+u, 
alt+printscreen+b, alt+printscreen+b.

  Upon reboot I've seen this kernel error in /var/log/kern.log (see attachment 
for full details):
  Mar 31 19:48:30 bolt kernel: [ 1638.798821] kernel BUG at 
/build/linux-7LGLH_/linux-4.10.0/include/linux/swapops.h:12
  [...]
  Mar 31 19:48:30 bolt kernel: [ 1638.799326] Call Trace:
  Mar 31 19:48:30 bolt kernel: [ 1638.799336]  migration_entry_wait+0x74/0x80
  Mar 31 19:48:30 bolt kernel: [ 1638.799350]  do_swap_page+0x5b3/0x770
  Mar 31 19:48:30 bolt kernel: [ 1638.799362]  handle_mm_fault+0x873/0x1360
  Mar 31 19:48:30 bolt kernel: [ 1638.799375]  __do_page_fault+0x23e/0x4e0
  Mar 31 19:48:30 bolt kernel: [ 1638.799387]  do_page_fault+0x22/0x30
  Mar 31 19:48:30 bolt kernel: [ 1638.799399]  page_fault+0x28/0x30
  [...]

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: linux-image-4.10.0-14-generic 4.10.0-14.16
  

[Kernel-packages] [Bug 1590590] Re: Touchpad not recognized on Dell Latitude E7470 Ultrabook

2017-01-25 Thread Török Edwin
Apparently 4.8.0-34-generic detects my Latitude E7470 touchpad/stick as
ALPS instead of BYD (4.8.0-32-generic detects as BYD). I don't know
which would be the correct one, but by default ALPS is way too sensitive
and I have to apply those xprops changes before it is usable again
(basically I can't click anything because no matter how much I want to
hold my finger still, it just goes around in circles and the pointer is
not on top of an icon long enough to click it).

There is also something weird about how the touchpad behaves (or maybe I
noticed it now cause I use it more instead of the trackpoint?), is it
supposed to scroll vertically when I move a single finger vertically on
the right half of it? Basically I have to always move my finger
horizontally first, otherwise it accidentally scrolls.

I think it would be useful to make the BYD/ALPS configurable. The BYD
driver works a lot better by default, and I think I actually prefer it
over the ALPS one :)

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

Title:
  Touchpad not recognized on Dell Latitude E7470 Ultrabook

Status in linux package in Ubuntu:
  Triaged
Status in xserver-xorg-input-synaptics package in Ubuntu:
  Confirmed

Bug description:
  Expected: Touchpad settings available in Mouse & Touchpad Settings
  dialog

  Actual result: Touchpad settings missing entirely

  
  Details:
  The touchpad on my Dell Ultrabook (Latitude E7470) functions mostly. 

  The settings for the touchpad are not available at all in the Mouse
  and Touchpad settings (see http://i.imgur.com/YRGiOrj.png).

  Two-finger scrolling works as expected except it's using "Natural
  Scrolling" by default and there is no way to change it.

  xinput list does not display a touchpad at all:

  ⎡ Virtual core pointerid=2[master pointer  (3)]
  ⎜   ↳ Virtual core XTEST pointer  id=4[slave  pointer 
 (2)]
  ⎜   ↳ ELAN Touchscreenid=11   [slave  pointer 
 (2)]
  ⎜   ↳ ImPS/2 Generic Wheel Mouse  id=13   [slave  pointer 
 (2)]
  ⎣ Virtual core keyboard   id=3[master keyboard (2)]
  ↳ Virtual core XTEST keyboard id=5[slave  
keyboard (3)]
  ↳ Power Buttonid=6[slave  
keyboard (3)]
  ↳ Video Bus   id=7[slave  
keyboard (3)]
  ↳ Power Buttonid=8[slave  
keyboard (3)]
  ↳ Sleep Buttonid=9[slave  
keyboard (3)]
  ↳ Integrated_Webcam_FHD   id=10   [slave  
keyboard (3)]
  ↳ AT Translated Set 2 keyboardid=12   [slave  
keyboard (3)]
  ↳ Dell WMI hotkeysid=14   [slave  
keyboard (3)]
  ↳ DELL Wireless hotkeys   id=15   [slave  
keyboard (3)]

  
  /proc/bus/input/devices lists the device as a "Generic Wheel Mouse"

  Output of `lsb_release -rd`:
  Description:  Ubuntu 16.04 LTS
  Release:  16.04

  xserver-xorg-input-synaptics version information:
  xserver-xorg-input-synaptics:
Installed: 1.8.2-1ubuntu3
Candidate: 1.8.2-1ubuntu3
Version table:
   *** 1.8.2-1ubuntu3 500
  500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  100 /var/lib/dpkg/status

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

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