date:20180907

[Kernel-packages] [Bug 1772038] Re: ubuntu/xubuntu 18.04 kernel crash during install.

2018-09-07 Thread Nigel Stewart

Confirming this issue for USB installer for both 18.04.1 and 16.04.5 on HP 
Compaq dc5800.
The "acpi=off noapic" kernel parameter workaroud works for installing the 
system.
And interestingly, once installed to SATA drive the system boots and behaves 
normally.

I'd be happy to try a new ISO or update the BIOS, for the purposes here.

https://www.pcworld.idg.com.au/review/hp/compaq_dc5800_small_form_factor_pc_ks738pa/225069/specs/

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

Title:
  ubuntu/xubuntu 18.04 kernel crash during install.

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

Bug description:
  I've been trying to install ubuntu 18.04, but the system crashes with a 
kernel panic and thus won't run. So how do I report this bug?
  The system passes all memory tests and runs 17.10 with no problems, but will 
not run 18.04

  There is very little data gathering that I can do, as the system will
  not boot, not even into text mode.

  PS. This back door way of creating a bug report is very poor when
  dealing with systems that don't run.

  The steps required to reproduce this bug are:
  1) download Ubuntu and/or Xubuntu
  2) burn the installation image to a dvd
  3) insert dvd into target computer
  4) power on target computer
  5) wait a couple of seconds
  6) Stare at frozen screen saying Kernel panic
  7) Go back to step 1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1772038/+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 1607355] Re: Task (usually mongod) blocked more 120 seconds (lock-ups) in juju on lxc/lxd + zfs

2018-09-07 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/1607355

Title:
  Task (usually mongod) blocked more 120 seconds (lock-ups) in juju on
  lxc/lxd + zfs

Status in linux package in Ubuntu:
  Expired

Bug description:
  I was able to reproduce this 2 or 3 times last 2 days. I have the
  following setup:

  Containers for Trusty/kilo service machines:

  inaddy@workstation:~$ lxc-ls  | grep tk
  tkcephmon01  RUNNING 0 -  192.168.65.52 -
  tkcephmon02  RUNNING 0 -  192.168.65.51 -
  tkcephmon03  RUNNING 0 -  192.168.65.48 -
  tkcinder RUNNING 0 -  192.168.65.49 -
  tkdash   RUNNING 0 -  192.168.65.50 -
  tkglance RUNNING 0 -  192.168.65.53 -
  tkjuju   RUNNING 0 -  192.168.65.15 -
  tkkeystone   RUNNING 0 -  192.168.65.54 -
  tkmysql  RUNNING 0 -  192.168.65.55 -
  tknova   RUNNING 0 -  192.168.65.56 -
  tkrabbit RUNNING 0 -  192.168.65.57 -
  tkswiftproxy RUNNING 0 -  192.168.65.58 -

  And compute nodes + neutrongw as kvm guests:

  inaddy@workstation:~$ virsh list --all | grep tk
   21tkcompute01running
   22tkcompute02running
   23tkcompute03running
   24tkneutrongwrunning

  All my LXC containers are on top of ZFS:

  Linux workstation 4.4.0-32-generic #51-Ubuntu SMP Tue Jul 19 18:09:07
  UTC 2016 x86_64 x86_64 x86_64 GNU/Linux

  And my KVM guests are on top of ext4 + 1.2 raid0 stripped volume.

  I'm getting the lockups bellow (usually for mongod, from tkjuju
  container, the juju controller). After the first lockup appears
  (schedule timeout coming from zfs sync logic most likely), JuJu
  controller starts giving me errors on "update-status". From "juju
  status":

  glance/0error  idle1.25.6  10  9292/tcp   
tkglance   hook failed: "update-status"
  keystone/0  error  idle1.25.6  11 
tkkeystone hook failed: "update-status"
  mysql/0 error  idle1.25.6  12 
tkmysqlhook failed: "config-changed"
  neutron-api/0   error  idle1.25.6  4   9696/tcp   
tkneutrongwhook failed: "update-status"
  nova-compute/0  error  idle1.25.6  1  
tkcompute01hook failed: "update-status"
  nova-compute/1  error  idle1.25.6  2  
tkcompute02hook failed: "update-status"
  nova-compute/2  error  idle1.25.6  3  
tkcompute03hook failed: "update-status"

  Lockups:

  [105601.816578] INFO: task mongod:14480 blocked for more than 120 seconds.
  [105601.816583]   Tainted: P   O4.4.0-32-generic #51-Ubuntu
  [105601.816584] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [105601.816586] mongod  D 88010ec47ba8 0 14480  16855 
0x0100
  [105601.816590]  88010ec47ba8 57992eeb 880108e5ee00 
880108e58dc0
  [105601.816592]  88010ec48000 88081ecd6d00 7fff 
8182a600
  [105601.816594]  88010ec47d08 88010ec47bc0 81829e05 

  [105601.816596] Call Trace:
  [105601.816603]  [] ? bit_wait+0x60/0x60
  [105601.816606]  [] schedule+0x35/0x80
  [105601.816608]  [] schedule_timeout+0x1b5/0x270
  [105601.816612]  [] ? find_get_pages_tag+0x109/0x190
  [105601.816614]  [] ? bit_wait+0x60/0x60
  [105601.816616]  [] io_schedule_timeout+0xa4/0x110
  [105601.816618]  [] bit_wait_io+0x1b/0x70
  [105601.816620]  [] __wait_on_bit+0x5d/0x90
  [105601.816622]  [] wait_on_page_bit+0xcb/0xf0
  [105601.816625]  [] ? autoremove_wake_function+0x40/0x40
  [105601.816628]  [] __filemap_fdatawait_range+0xf3/0x160
  [105601.816630]  [] filemap_fdatawait_range+0x14/0x30
  [105601.816632]  [] filemap_write_and_wait_range+0x3f/0x70
  [105601.816682]  [] zpl_fsync+0x38/0x90 [zfs]
  [105601.816685]  [] vfs_fsync_range+0x4b/0xb0
  [105601.816687]  [] SyS_msync+0x17e/0x1f0
  [105601.816689]  [] entry_SYSCALL_64_fastpath+0x16/0x71
  [117121.961545] INFO: task txg_sync:4589 blocked for more than 120 seconds.
  [117121.961549]   Tainted: P   O4.4.0-32-generic #51-Ubuntu
  [117121.961550] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [117121.961551] txg_syncD 8807e1fbbaa8 0  4589  2 
0x
  [117121.96155

[Kernel-packages] [Bug 1714178]

2018-09-07 Thread Daniel van Vugt

*** Bug 107840 has been marked as a duplicate of this bug. ***

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

Title:
  Triple 4K monitor display failed (modesetting driver limited to
  8192x8192)

Status in X.Org X server:
  Confirmed
Status in linux package in Ubuntu:
  Triaged
Status in mesa package in Ubuntu:
  Triaged
Status in xorg-server package in Ubuntu:
  Triaged
Status in linux source package in Bionic:
  Confirmed
Status in mesa source package in Bionic:
  Confirmed
Status in xorg-server source package in Bionic:
  Confirmed

Bug description:
  Title: Triple monitor display failed with Dell Dock (HiDPI)
  (modesetting)

  Summary: Triple monitor display failed with Dell Dock (HiDPI)
  (modesetting)

  Steps:
  1. a laptop with Built-in 4K LCD
  2. Cold boot system with Dell Dock connected
  3. Connect a 4K monitor to Dock
  4. Connect 2nd 4K monitor to Dock
  5. Go to [All Settings]=>[Displays] to have the following configuration.
  Resolution: 4kx2k@60Hz (one Built-in LCD + two external monitors)
  Mirror displays: disable

  Expected results: Triple monitor display should works without issues
  Actual results: Triple monitor display failed with Dell Dock

  Additional information:
  1. Linux distribution: Ubuntu 16.04+modesetting, 16.04.3, and 17.04
  2. Laptop: Dell Precision 5520
  3. Dell Business Thunderbolt Dock - TB16
  https://goo.gl/vFDjpi

  WORKAROUND (UBUNTU 18.04+):
  Log in to "Ubuntu on Wayland" instead of "Ubuntu".

  ---
  .tmp.unity_support_test.0:

  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  DistUpgraded: Fresh install
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-xenial-amd64-20160624-2
  DistroCodename: xenial
  DistroRelease: Ubuntu 16.04
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Device [8086:591d] (rev 04) (prog-if 00 [VGA controller])
     Subsystem: Dell Device [1028:07bf]
     Subsystem: Dell Device [1028:07bf]
  InstallationDate: Installed on 2017-08-29 (2 days ago)
  InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 
20160624-10:47
  MachineType: Dell Inc. Precision 5520
  Package: xorg-server (not installed)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.11.0-14-generic.efi.signed 
root=UUID=b79ae801-0652-4785-beaf-e8387d798948 ro acpi_rev_override quiet 
splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.11.0-14.20~16.04.1-generic 4.11.12
  Tags:  xenial ubuntu compiz-0.9
  Uname: Linux 4.11.0-14-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/08/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.3.3
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.3.3:bd05/08/2017:svnDellInc.:pnPrecision5520:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr:
  dmi.product.name: Precision 5520
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.76-1~ubuntu16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2

To manage notifications about this bug go to:
https://bugs.launchpad.net/xorg-server/+bug/1714178/+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 1777238] Re: video lag

2018-09-07 Thread Boris

This is getting really bad.  I can't even type without the screen freezing 
momentarily!
What information would be most useful to diagnose the problem?  How do I 
collect it?  How do I add it to the ticket?

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

Title:
  video lag

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The problem exists for months and I didn't find a good answer on it.
  It affects many softwares: Cheese, Super Tux Cart, VLC (when I rewind
  the video the sounds continues, but the video stops), youtube,
  Hangouts and every software where video is played.

  I experienced that there are 2 things that can break it:
   - if I move the mouse out and in on the affected window (it doesn't work in 
full screen)
   - if I open the system monitor, the problem also disappears

  other people also face with this problem:
  
https://unix.stackexchange.com/questions/447696/ubuntu-16-04-18-04-video-playback-lags-stutters
  
https://askubuntu.com/questions/1032035/ubuntu-18-04-budgie-desktop-video-lag-youtube-twitch-in-chrome
  
https://askubuntu.com/questions/1030074/my-video-player-in-ubuntu-18-04-lts-lags/1030194
  https://askubuntu.com/questions/1030155/youtube-video-lag-on-18-04

  Ubuntu 4.15.0-23.25-generic 4.15.18
  it was upgraded from 16.04

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: cheese 3.28.0-1ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  Uname: Linux 4.15.0-23-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jun 16 14:34:26 2018
  ExecutablePath: /usr/bin/cheese
  InstallationDate: Installed on 2016-08-04 (680 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: Dell Inc. Latitude E5440
  RelatedPackageVersions:
   cheese3.28.0-1ubuntu1
   cheese-common 3.28.0-1ubuntu1
  SourcePackage: linux
  UpgradeStatus: Upgraded to bionic on 2018-04-02 (74 days ago)
  dmi.bios.date: 05/01/2014
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A06
  dmi.board.name: 009TY8
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA06:bd05/01/2014:svnDellInc.:pnLatitudeE5440:pvr01:rvnDellInc.:rn009TY8:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E5440
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  vandor 3436 F pulseaudio
   /dev/snd/controlC1:  vandor 3436 F pulseaudio
   /dev/snd/controlC0:  vandor 3436 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=b5a3c617-9443-458f-92a3-63eea1f57d5c
  InstallationDate: Installed on 2016-08-04 (681 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: Dell Inc. Latitude E5440
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-23-generic 
root=UUID=38affd30-88f0-4a36-b9ae-6b5c210844b4 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-23-generic N/A
   linux-backports-modules-4.15.0-23-generic  N/A
   linux-firmware 1.173.1
  Tags:  bionic
  Uname: Linux 4.15.0-23-generic x86_64
  UpgradeStatus: Upgraded to bionic on 2018-04-02 (74 days ago)
  UserGroups: adm bumblebee cdrom dip docker libvirt libvirtd lpadmin mail 
plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/01/2014
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A06
  dmi.board.name: 009TY8
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA06:bd05/01/2014:svnDellInc.:pnLatitudeE5440:pvr01:rvnDellInc.:rn009TY8:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E5440
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

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

2018-09-07 Thread Ubuntu Kernel Bot

This change was made by a bot.

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

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

Title:
  usb 3-4: device descriptor read/64, error -110

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hello,

  dmesg:
  [7.776138] usb 3-4: device descriptor read/64, error -110
  [8.048909] usb 3-4: New USB device found, idVendor=0cf3, idProduct=9271, 
bcdDevice= 1.08
  [8.048917] usb 3-4: New USB device strings: Mfr=16, Product=32, 
SerialNumber=48
  [8.048922] usb 3-4: Product: USB2.0 WLAN
  [8.048927] usb 3-4: Manufacturer: ATHEROS
  [8.048939] usb 3-4: SerialNumber: 12345

  --

  https://bugzilla.kernel.org/show_bug.cgi?id=201037

  --

  Best regards,
  --
  Cristian Aravena Romero (caravena)

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1791389/+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 1791389] [NEW] usb 3-4: device descriptor read/64, error -110

2018-09-07 Thread Cristian Aravena Romero

Public bug reported:

Hello,

dmesg:
[7.776138] usb 3-4: device descriptor read/64, error -110
[8.048909] usb 3-4: New USB device found, idVendor=0cf3, idProduct=9271, 
bcdDevice= 1.08
[8.048917] usb 3-4: New USB device strings: Mfr=16, Product=32, 
SerialNumber=48
[8.048922] usb 3-4: Product: USB2.0 WLAN
[8.048927] usb 3-4: Manufacturer: ATHEROS
[8.048939] usb 3-4: SerialNumber: 12345

--

https://bugzilla.kernel.org/show_bug.cgi?id=201037

--

Best regards,
--
Cristian Aravena Romero (caravena)

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

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


** Tags: amd64 apport-bug cosmic package-from-proposed wayland-session

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

Title:
  usb 3-4: device descriptor read/64, error -110

Status in linux package in Ubuntu:
  New

Bug description:
  Hello,

  dmesg:
  [7.776138] usb 3-4: device descriptor read/64, error -110
  [8.048909] usb 3-4: New USB device found, idVendor=0cf3, idProduct=9271, 
bcdDevice= 1.08
  [8.048917] usb 3-4: New USB device strings: Mfr=16, Product=32, 
SerialNumber=48
  [8.048922] usb 3-4: Product: USB2.0 WLAN
  [8.048927] usb 3-4: Manufacturer: ATHEROS
  [8.048939] usb 3-4: SerialNumber: 12345

  --

  https://bugzilla.kernel.org/show_bug.cgi?id=201037

  --

  Best regards,
  --
  Cristian Aravena Romero (caravena)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: linux-image-4.18.0-7-generic 4.18.0-7.8
  ProcVersionSignature: Ubuntu 4.18.0-7.8-generic 4.18.5
  Uname: Linux 4.18.0-7-generic x86_64
  ApportVersion: 2.20.10-0ubuntu9
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  caravena   2485 F pulseaudio
   /dev/snd/pcmC0D0p:   caravena   2485 F...m pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Sep  7 20:39:28 2018
  InstallationDate: Installed on 2017-10-13 (329 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 530U3C/530U4C
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.18.0-7-generic 
root=UUID=707d0f89-4b1d-4432-9d50-6058dc4c1ee9 ro rootflags=subvol=@ quiet 
splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-7-generic N/A
   linux-backports-modules-4.18.0-7-generic  N/A
   linux-firmware1.175
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/15/2013
  dmi.bios.vendor: Phoenix Technologies Ltd.
  dmi.bios.version: P14AAJ
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: SAMSUNG_NP1234567890
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: FAB1
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type:

[Kernel-packages] [Bug 1791372] Re: Keyboard backlight not working on Asus ZenBook Flip UX561UD laptop in Cosmic 18.10, works with 18.04.1 desktop installer live image

2018-09-07 Thread Mario Vukelic

** Description changed:

Repro:
1. Press Fn+F3/F4 in fresh install from current Cosmic desktop image, fully
updated

-> Keyboard backlight should come on or change but doesn't. The gnome-
shell icon for the keyboard backlight appears for both keys, but the
icon's "progress" bar is not visible.

Kernel version is linux-image-4.17.0-9-generic

The keyboard backlight works perfectly when booting from the 18.04.1
- desktop live image.
+ desktop live image. When turning on light with 18.04.1, it is off again
+ after rebooting into 18.10. (However 18.04.1 seems to freeze when
+ shutting down from menu, I have to hard-shut it off).

- On Cosmic, most other Fn+Fx special keys work (display brightness, touchpad
off, sound etc.).
- Only the airplane mode key fails, but only in gnome-shell, it works on the
console (this is filed as
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1791367)
-
- In case it matters, Nvidia binary drivers are installed but Nvidia is
- switched off via Prime setting in nvidia-settings. Running with Intel
- drivers.
+ Most other Fn+Fx special keys on this laptop work (display brightness,
+ touchpad off, sound etc.) except for the airplane mode key. However the
+ airplane mode key only fails in gnome-shell but works on the console
+ (this is filed as https://bugs.launchpad.net/ubuntu/+source/gnome-
+ shell/+bug/1791367)

ProblemType: Bug
DistroRelease: Ubuntu 18.10
Package: linux-image-4.17.0-9-generic 4.17.0-9.10
ProcVersionSignature: Ubuntu 4.17.0-9.10-generic 4.17.17
Uname: Linux 4.17.0-9-generic x86_64
ApportVersion: 2.20.10-0ubuntu9
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: angela16196 F pulseaudio
CurrentDesktop: ubuntu:GNOME
Date: Fri Sep 7 22:08:12 2018
InstallationDate: Installed on 2018-09-05 (1 days ago)
InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180822)
Lsusb:
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 004: ID 8087:0a2b Intel Corp.
Bus 001 Device 003: ID 13d3:5256 IMC Networks
Bus 001 Device 002: ID 8644:800b Intenso GmbG Micro Line (4GB)
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: ASUSTeK COMPUTER INC. UX561UD
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.17.0-9-generic
root=UUID=02bad6b5-ca8f-4184-b477-935995e14bdc ro quiet splash vt.handoff=1
RelatedPackageVersions:
linux-restricted-modules-4.17.0-9-generic N/A
linux-backports-modules-4.17.0-9-generic N/A
linux-firmware1.174
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 03/06/2018
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: UX561UD.304
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: UX561UD
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: 1.0
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 31
dmi.chassis.vendor: ASUSTeK COMPUTER INC.
dmi.chassis.version: 1.0
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvrUX561UD.304:bd03/06/2018:svnASUSTeKCOMPUTERINC.:pnUX561UD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX561UD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct31:cvr1.0:
dmi.product.family: ZenBook Flip
dmi.product.name: UX561UD
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.

** Description changed:

Repro:
1. Press Fn+F3/F4 in fresh install from current Cosmic desktop image, fully
updated

-> Keyboard backlight should come on or change but doesn't. The gnome-
shell icon for the keyboard backlight appears for both keys, but the
icon's "progress" bar is not visible.

Kernel version is linux-image-4.17.0-9-generic
+
+ This is the same in X and Wayland session. In case it matters, Nvidia
+ binary drivers are installed but Nvidia is switched off via Prime
+ setting in nvidia-settings. Running with Intel drivers

The keyboard backlight works perfectly when booting from the 18.04.1
desktop live image. When turning on light with 18.04.1, it is off again
after rebooting into 18.10. (However 18.04.1 seems to freeze when
shutting down from menu, I have to hard-shut it off).

Most other Fn+Fx special keys on this laptop work (display brightness,
touchpad off, sound etc.) except for the airplane mode key. However the
airplane mode key only fails in gnome-shell but works on the console
(this is filed as https://bugs.launchpad.net/ubuntu/+source/gnome-
shell/+bug/1791367)

[Kernel-packages] [Bug 1791372] Re: Keyboard backlight not working on Asus ZenBook Flip UX561UD laptop in Cosmic 18.10, works with 18.04.1 desktop installer live image

2018-09-07 Thread Mario Vukelic

** Description changed:

  Repro:
  1. Press Fn+F3/F4 in fresh install from current Cosmic desktop image, fully 
updated
  
  -> Keyboard backlight should come on or change but doesn't.  The gnome-
  shell icon for the keyboard backlight appears for both keys, but the
  icon's "progress" bar is not visible.
  
  Kernel version is linux-image-4.17.0-9-generic
  
  The keyboard backlight works perfectly when booting from the 18.04.1
- desktop live image, Most other Fn+Fx special keys on this laptop work
- (display brightness, touchpad off, sound etc.) except for the airplane
- mode key. However the airplane mode key only fails in gnome-shell but
- works on the console (this is filed as
- https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1791367)
+ desktop live image.
+ 
+ On Cosmic, most other Fn+Fx special keys work (display brightness, touchpad 
off, sound etc.).
+ Only the airplane mode key fails, but only in gnome-shell, it works on the 
console (this is filed as 
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1791367)
  
  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: linux-image-4.17.0-9-generic 4.17.0-9.10
  ProcVersionSignature: Ubuntu 4.17.0-9.10-generic 4.17.17
  Uname: Linux 4.17.0-9-generic x86_64
  ApportVersion: 2.20.10-0ubuntu9
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  angela16196 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Sep  7 22:08:12 2018
  InstallationDate: Installed on 2018-09-05 (1 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180822)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0a2b Intel Corp.
   Bus 001 Device 003: ID 13d3:5256 IMC Networks
   Bus 001 Device 002: ID 8644:800b Intenso GmbG Micro Line (4GB)
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. UX561UD
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.17.0-9-generic 
root=UUID=02bad6b5-ca8f-4184-b477-935995e14bdc ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.17.0-9-generic N/A
   linux-backports-modules-4.17.0-9-generic  N/A
   linux-firmware1.174
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/06/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX561UD.304
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX561UD
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 31
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX561UD.304:bd03/06/2018:svnASUSTeKCOMPUTERINC.:pnUX561UD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX561UD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct31:cvr1.0:
  dmi.product.family: ZenBook Flip
  dmi.product.name: UX561UD
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

** Description changed:

  Repro:
  1. Press Fn+F3/F4 in fresh install from current Cosmic desktop image, fully 
updated
  
  -> Keyboard backlight should come on or change but doesn't.  The gnome-
  shell icon for the keyboard backlight appears for both keys, but the
  icon's "progress" bar is not visible.
  
  Kernel version is linux-image-4.17.0-9-generic
  
  The keyboard backlight works perfectly when booting from the 18.04.1
  desktop live image.
  
  On Cosmic, most other Fn+Fx special keys work (display brightness, touchpad 
off, sound etc.).
  Only the airplane mode key fails, but only in gnome-shell, it works on the 
console (this is filed as 
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1791367)
+ 
+ In case it matters, Nvidia binary drivers are installed but Nvidia is
+ switched off via Prime setting in nvidia-settings. Running with Intel
+ drivers.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: linux-image-4.17.0-9-generic 4.17.0-9.10
  ProcVersionSignature: Ubuntu 4.17.0-9.10-generic 4.17.17
  Uname: Linux 4.17.0-9-generic x86_64
  ApportVersion: 2.20.10-0ubuntu9
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  angela16196 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Sep  7 22:08:12 2018
  InstallationDate: Installed on 2018-09-05 (1 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180822)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0a2b Intel Corp.
   Bus 001 Device 003: ID 13d3:5256 IMC Networks
   Bus 001 Device 002: ID 8644:800b Intenso GmbG Micro Line (4GB)
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. UX561UD
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.17.0-9-generic 
root=UU

[Kernel-packages] [Bug 1788563] Re: L1TF mitigation not effective

2018-09-07 Thread Tyler Hicks

I built Xenial and Trusty test kernels with those commits backported:

https://people.canonical.com/~tyhicks/lp1788563/xenial/
https://people.canonical.com/~tyhicks/lp1788563/trusty/

Please test the kernels and see if it resolves the bug for you. See the
comment above for details on installing test kernels. 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/1788563

Title:
  L1TF mitigation not effective

Status in linux package in Ubuntu:
  Triaged
Status in linux source package in Trusty:
  Triaged
Status in linux source package in Xenial:
  Triaged
Status in linux source package in Bionic:
  Triaged
Status in linux source package in Cosmic:
  Triaged

Bug description:
  Lenovo Thinkpad W530 system with 32 GB RAM

  dmesg | grep -i l1tf
  [0.038386] L1TF: System has more than MAX_PA/2 memory. L1TF mitigation 
not effective.
  [ 2652.469669] L1TF CPU bug present and SMT on, data leak possible. See 
CVE-2018-3646 and https://www.kernel.org/doc/html/latest/admin-guide/l1tf.html 
for details.

  Related:
  https://bugzilla.opensuse.org/show_bug.cgi?id=1105536

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-32-generic 4.15.0-32.35
  ProcVersionSignature: Ubuntu 4.15.0-32.35-generic 4.15.18
  Uname: Linux 4.15.0-32-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  pgera  2809 F pulseaudio
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Thu Aug 23 03:38:40 2018
  InstallationDate: Installed on 2018-08-11 (12 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: LENOVO 24382LU
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-32-generic 
root=UUID=e2607c8a-4bd1-49fe-ad07-83046492fac5 ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-32-generic N/A
   linux-backports-modules-4.15.0-32-generic  N/A
   linux-firmware 1.173.1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/11/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G5ETB2WW (2.72 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 24382LU
  dmi.board.vendor: LENOVO
  dmi.board.version: NO DPK
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrG5ETB2WW(2.72):bd06/11/2018:svnLENOVO:pn24382LU:pvrThinkPadW530:rvnLENOVO:rn24382LU:rvrNODPK:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad W530
  dmi.product.name: 24382LU
  dmi.product.version: ThinkPad W530
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1788563/+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 1791377] [NEW] linux-azure: 4.18.0-1001.1 -proposed tracker

2018-09-07 Thread Marcelo Cerri

Public bug reported:

This bug is for tracking the 4.18.0-1001.1 upload package. This bug will
contain status and testing results related to that upload.

For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

** Affects: kernel-sru-workflow
 Importance: Medium
 Status: In Progress

** Affects: kernel-sru-workflow/automated-testing
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/prepare-package
 Importance: Medium
 Assignee: Marcelo Cerri (mhcerri)
 Status: In Progress

** Affects: kernel-sru-workflow/prepare-package-meta
 Importance: Medium
 Assignee: Marcelo Cerri (mhcerri)
 Status: In Progress

** Affects: kernel-sru-workflow/prepare-package-signed
 Importance: Medium
 Assignee: Marcelo Cerri (mhcerri)
 Status: In Progress

** Affects: kernel-sru-workflow/promote-to-proposed
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/promote-to-release
 Importance: Medium
 Assignee: Ubuntu Package Archive Administrators (ubuntu-archive)
 Status: New

** Affects: kernel-sru-workflow/regression-testing
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/stakeholder-signoff
 Importance: Medium
 Assignee: Joshua R. Poulson (jrp)
 Status: New

** Affects: linux-azure (Ubuntu)
 Importance: Medium
 Status: Confirmed

** Affects: linux-azure (Ubuntu Cosmic)
 Importance: Medium
 Status: Confirmed


** Tags: cosmic kernel-release-tracking-bug kernel-release-tracking-bug-live

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

** Tags added: kernel-release-tracking-bug-live

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

** Tags added: cosmic

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

** Also affects: kernel-sru-workflow/automated-testing
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/prepare-package
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/prepare-package-meta
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/prepare-package-signed
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/promote-to-proposed
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/promote-to-release
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/regression-testing
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/stakeholder-signoff
   Importance: Undecided
   Status: New

** Changed in: kernel-sru-workflow/automated-testing
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/automated-testing
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

** Changed in: kernel-sru-workflow/prepare-package
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/prepare-package
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

** Changed in: kernel-sru-workflow/prepare-package-meta
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/prepare-package-meta
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

** Changed in: kernel-sru-workflow/prepare-package-signed
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/prepare-package-signed
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

** Changed in: kernel-sru-workflow/promote-to-proposed
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/promote-to-proposed
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

** Changed in: kernel-sru-workflow/promote-to-release
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/promote-to-release
 Assignee: (unassigned) => Ubuntu Package Archive Administrators 
(ubuntu-archive)

** Changed in: kernel-sru-workflow/regression-testing
   Importance: Undecided => Medium

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

** Changed in: kernel-sru-workflow/stakeholder-signoff
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/stakeholder-signoff
 Assignee: (unassigned) => Joshua R. Poulson (jrp)

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

** Changed in: kernel-sru-workflow
   Status: New => In Progress

** Changed in: kernel-sru-workflow
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/prepare-package
   Status: New => In Progress

** Chan

[Kernel-packages] [Bug 1762940] Re: Ubuntu 18.04 d-i install screen becomes blurry on Huawei server in EFI boot mode

2018-09-07 Thread dann frazier

@Mao: correct, I do not observe screen blur in d-i on D05.

btw, note also bug 1780076

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

Title:
  Ubuntu 18.04 d-i install screen becomes blurry on Huawei server in EFI
  boot mode

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

Bug description:
  For all(as I know) Huawei servers, the vga adapter are embed in the
  iBMC chips. Those server can install from ISO manually for 16.04.4 and
  screen display normally. But for 18.04 ( tested both for daily and
  final beta)version, the install screen is blur. One of tested server
  is Huawei 2855 v5, the certification link for 16.04 are
  https://certification.ubuntu.com/hardware/201707-25596/.

  Below are key difference of dmesg. It seems might related with DRM.

  18.04 install screen is blur 
  dmesg
  ...
  [2.039009] fb0: EFI VGA frame buffer device
  ...
  [4.178058] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
  [4.191435] [drm] No driver support for vblank timestamp query.
  [4.209338] checking generic (9000 30) vs hw (0 0)
  [4.209384] fbcon: hibmcdrmfb (fb1) is primary device
  [4.209385] fbcon: Remapping primary device, fb1, to tty 1-63
  ...
  [5.357024] hibmc-drm :07:00.0: fb1: hibmcdrmfb frame buffer device
  [5.380085] [drm] Initialized hibmc 1.0.0 20160828 for :07:00.0 on 
minor 0
  ...
  [5.636624] vga16fb: initializing
  [5.636627] vga16fb: mapped to 0x48a7a1d2
  [5.636630] checking generic (9000 30) vs hw (a 1)
  [5.636676] fb2: VGA16 VGA frame buffer device
  ...

  16.04.4 install screen is fine (no screen blur)
  dmesg
  ...
  [2.000419] fb0: EFI VGA frame buffer device
  
  [8.795065] vga16fb: initializing
  [8.795068] vga16fb: mapped to 0x880a
  [8.795071] checking generic (9800 30) vs hw (a 1)
  [8.795121] fb1: VGA16 VGA frame buffer device
  ...

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1762940/+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 1791372] Re: Keyboard backlight not working on Asus ZenBook Flip UX561UD laptop in Cosmic 18.10, works with 18.04.1 desktop installer live image

2018-09-07 Thread Mario Vukelic

Bios version 304 is the latest from Asus

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

Title:
  Keyboard backlight not working on Asus ZenBook Flip UX561UD laptop in
  Cosmic 18.10, works with 18.04.1 desktop installer live image

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Repro:
  1. Press Fn+F3/F4 in fresh install from current Cosmic desktop image, fully 
updated

  -> Keyboard backlight should come on or change but doesn't.  The
  gnome-shell icon for the keyboard backlight appears for both keys, but
  the icon's "progress" bar is not visible.

  Kernel version is linux-image-4.17.0-9-generic

  The keyboard backlight works perfectly when booting from the 18.04.1
  desktop live image, Most other Fn+Fx special keys on this laptop work
  (display brightness, touchpad off, sound etc.) except for the airplane
  mode key. However the airplane mode key only fails in gnome-shell but
  works on the console (this is filed as
  https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1791367)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: linux-image-4.17.0-9-generic 4.17.0-9.10
  ProcVersionSignature: Ubuntu 4.17.0-9.10-generic 4.17.17
  Uname: Linux 4.17.0-9-generic x86_64
  ApportVersion: 2.20.10-0ubuntu9
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  angela16196 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Sep  7 22:08:12 2018
  InstallationDate: Installed on 2018-09-05 (1 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180822)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0a2b Intel Corp.
   Bus 001 Device 003: ID 13d3:5256 IMC Networks
   Bus 001 Device 002: ID 8644:800b Intenso GmbG Micro Line (4GB)
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. UX561UD
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.17.0-9-generic 
root=UUID=02bad6b5-ca8f-4184-b477-935995e14bdc ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.17.0-9-generic N/A
   linux-backports-modules-4.17.0-9-generic  N/A
   linux-firmware1.174
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/06/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX561UD.304
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX561UD
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 31
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX561UD.304:bd03/06/2018:svnASUSTeKCOMPUTERINC.:pnUX561UD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX561UD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct31:cvr1.0:
  dmi.product.family: ZenBook Flip
  dmi.product.name: UX561UD
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1791372/+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 1791372] Re: Keyboard backlight not working on Asus ZenBook Flip UX561UD laptop in Cosmic 18.10, works with 18.04.1 desktop installer live image

2018-09-07 Thread Mario Vukelic

Please let me know whatever I can do to help debug this

** Description changed:

  Repro:
  1. Press Fn+F3/F4 in fresh install from current Cosmic desktop image, fully 
updated
  
  -> Keyboard backlight should come on or change but doesn't.  The gnome-
  shell icon for the keyboard backlight appears for both keys, but the
  icon's "progress" bar is not visible.
  
  Kernel version is linux-image-4.17.0-9-generic
  
  The keyboard backlight works perfectly when booting from the 18.04.1
  desktop live image, Most other Fn+Fx special keys on this laptop work
  (display brightness, touchpad off, sound etc.) except for the airplane
  mode key. However the airplane mode key only fails in gnome-shell but
- works on the console (this is filed as #1791367)
+ works on the console (this is filed as bug #1791367)
  
  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: linux-image-4.17.0-9-generic 4.17.0-9.10
  ProcVersionSignature: Ubuntu 4.17.0-9.10-generic 4.17.17
  Uname: Linux 4.17.0-9-generic x86_64
  ApportVersion: 2.20.10-0ubuntu9
  Architecture: amd64
  AudioDevicesInUse:
-  USERPID ACCESS COMMAND
-  /dev/snd/controlC0:  angela16196 F pulseaudio
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC0:  angela16196 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Sep  7 22:08:12 2018
  InstallationDate: Installed on 2018-09-05 (1 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180822)
  Lsusb:
-  Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
-  Bus 001 Device 004: ID 8087:0a2b Intel Corp. 
-  Bus 001 Device 003: ID 13d3:5256 IMC Networks 
-  Bus 001 Device 002: ID 8644:800b Intenso GmbG Micro Line (4GB)
-  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
+  Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
+  Bus 001 Device 004: ID 8087:0a2b Intel Corp.
+  Bus 001 Device 003: ID 13d3:5256 IMC Networks
+  Bus 001 Device 002: ID 8644:800b Intenso GmbG Micro Line (4GB)
+  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. UX561UD
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.17.0-9-generic 
root=UUID=02bad6b5-ca8f-4184-b477-935995e14bdc ro quiet splash vt.handoff=1
  RelatedPackageVersions:
-  linux-restricted-modules-4.17.0-9-generic N/A
-  linux-backports-modules-4.17.0-9-generic  N/A
-  linux-firmware1.174
+  linux-restricted-modules-4.17.0-9-generic N/A
+  linux-backports-modules-4.17.0-9-generic  N/A
+  linux-firmware1.174
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/06/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX561UD.304
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX561UD
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 31
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX561UD.304:bd03/06/2018:svnASUSTeKCOMPUTERINC.:pnUX561UD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX561UD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct31:cvr1.0:
  dmi.product.family: ZenBook Flip
  dmi.product.name: UX561UD
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

** Description changed:

  Repro:
  1. Press Fn+F3/F4 in fresh install from current Cosmic desktop image, fully 
updated
  
  -> Keyboard backlight should come on or change but doesn't.  The gnome-
  shell icon for the keyboard backlight appears for both keys, but the
  icon's "progress" bar is not visible.
  
  Kernel version is linux-image-4.17.0-9-generic
  
  The keyboard backlight works perfectly when booting from the 18.04.1
  desktop live image, Most other Fn+Fx special keys on this laptop work
  (display brightness, touchpad off, sound etc.) except for the airplane
  mode key. However the airplane mode key only fails in gnome-shell but
- works on the console (this is filed as bug #1791367)
+ works on the console (this is filed as LP#1791367)
  
  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: linux-image-4.17.0-9-generic 4.17.0-9.10
  ProcVersionSignature: Ubuntu 4.17.0-9.10-generic 4.17.17
  Uname: Linux 4.17.0-9-generic x86_64
  ApportVersion: 2.20.10-0ubuntu9
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  angela16196 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Sep  7 22:08:12 2018
  InstallationDate: Installed on 2018-09-05 (1 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180822)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0a2b Intel Corp.
   Bus 001 Device 003: ID 13d3:5256 IMC Networks
   Bus 001 Device 002: ID 8644:800b Intenso GmbG Micro Line (4GB)
   Bus 001 Device 001: ID 1d6b:0002 Lin

[Kernel-packages] [Bug 1791372] [NEW] Keyboard backlight not working on Asus ZenBook Flip UX561UD laptop in Cosmic 18.10, works with 18.04.1 desktop installer live image

2018-09-07 Thread Mario Vukelic

Public bug reported:

Repro:
1. Press Fn+F3/F4 in fresh install from current Cosmic desktop image, fully 
updated

-> Keyboard backlight should come on or change but doesn't.  The gnome-
shell icon for the keyboard backlight appears for both keys, but the
icon's "progress" bar is not visible.

Kernel version is linux-image-4.17.0-9-generic

The keyboard backlight works perfectly when booting from the 18.04.1
desktop live image, Most other Fn+Fx special keys on this laptop work
(display brightness, touchpad off, sound etc.) except for the airplane
mode key. However the airplane mode key only fails in gnome-shell but
works on the console (this is filed as
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1791367)

ProblemType: Bug
DistroRelease: Ubuntu 18.10
Package: linux-image-4.17.0-9-generic 4.17.0-9.10
ProcVersionSignature: Ubuntu 4.17.0-9.10-generic 4.17.17
Uname: Linux 4.17.0-9-generic x86_64
ApportVersion: 2.20.10-0ubuntu9
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  angela16196 F pulseaudio
CurrentDesktop: ubuntu:GNOME
Date: Fri Sep  7 22:08:12 2018
InstallationDate: Installed on 2018-09-05 (1 days ago)
InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180822)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 004: ID 8087:0a2b Intel Corp.
 Bus 001 Device 003: ID 13d3:5256 IMC Networks
 Bus 001 Device 002: ID 8644:800b Intenso GmbG Micro Line (4GB)
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: ASUSTeK COMPUTER INC. UX561UD
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.17.0-9-generic 
root=UUID=02bad6b5-ca8f-4184-b477-935995e14bdc ro quiet splash vt.handoff=1
RelatedPackageVersions:
 linux-restricted-modules-4.17.0-9-generic N/A
 linux-backports-modules-4.17.0-9-generic  N/A
 linux-firmware1.174
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 03/06/2018
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: UX561UD.304
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: UX561UD
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: 1.0
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 31
dmi.chassis.vendor: ASUSTeK COMPUTER INC.
dmi.chassis.version: 1.0
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX561UD.304:bd03/06/2018:svnASUSTeKCOMPUTERINC.:pnUX561UD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX561UD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct31:cvr1.0:
dmi.product.family: ZenBook Flip
dmi.product.name: UX561UD
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.

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


** Tags: amd64 apport-bug cosmic wayland-session

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

Title:
  Keyboard backlight not working on Asus ZenBook Flip UX561UD laptop in
  Cosmic 18.10, works with 18.04.1 desktop installer live image

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Repro:
  1. Press Fn+F3/F4 in fresh install from current Cosmic desktop image, fully 
updated

  -> Keyboard backlight should come on or change but doesn't.  The
  gnome-shell icon for the keyboard backlight appears for both keys, but
  the icon's "progress" bar is not visible.

  Kernel version is linux-image-4.17.0-9-generic

  The keyboard backlight works perfectly when booting from the 18.04.1
  desktop live image, Most other Fn+Fx special keys on this laptop work
  (display brightness, touchpad off, sound etc.) except for the airplane
  mode key. However the airplane mode key only fails in gnome-shell but
  works on the console (this is filed as
  https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1791367)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: linux-image-4.17.0-9-generic 4.17.0-9.10
  ProcVersionSignature: Ubuntu 4.17.0-9.10-generic 4.17.17
  Uname: Linux 4.17.0-9-generic x86_64
  ApportVersion: 2.20.10-0ubuntu9
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  angela16196 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Sep  7 22:08:12 2018
  InstallationDate: Installed on 2018-09-05 (1 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180822)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0a2b Intel Corp.
   Bus 001 Device 003: ID 13d3:5256 IMC Networks
   Bus 001 Device 002: ID 8644:800b Intenso GmbG Micro Line (4GB)
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. UX561UD
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.17.0-9-generic 
root=UUID=02bad6b5-ca8f-4184-b477-935995e14bdc ro quiet splash vt.handoff=1
  R

[Kernel-packages] [Bug 1791372] Status changed to Confirmed

2018-09-07 Thread Ubuntu Kernel Bot

This change was made by a bot.

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

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

Title:
  Keyboard backlight not working on Asus ZenBook Flip UX561UD laptop in
  Cosmic 18.10, works with 18.04.1 desktop installer live image

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Repro:
  1. Press Fn+F3/F4 in fresh install from current Cosmic desktop image, fully 
updated

  -> Keyboard backlight should come on or change but doesn't.  The
  gnome-shell icon for the keyboard backlight appears for both keys, but
  the icon's "progress" bar is not visible.

  Kernel version is linux-image-4.17.0-9-generic

  The keyboard backlight works perfectly when booting from the 18.04.1
  desktop live image, Most other Fn+Fx special keys on this laptop work
  (display brightness, touchpad off, sound etc.) except for the airplane
  mode key. However the airplane mode key only fails in gnome-shell but
  works on the console (this is filed as
  https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1791367)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: linux-image-4.17.0-9-generic 4.17.0-9.10
  ProcVersionSignature: Ubuntu 4.17.0-9.10-generic 4.17.17
  Uname: Linux 4.17.0-9-generic x86_64
  ApportVersion: 2.20.10-0ubuntu9
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  angela16196 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Sep  7 22:08:12 2018
  InstallationDate: Installed on 2018-09-05 (1 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180822)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0a2b Intel Corp.
   Bus 001 Device 003: ID 13d3:5256 IMC Networks
   Bus 001 Device 002: ID 8644:800b Intenso GmbG Micro Line (4GB)
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. UX561UD
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.17.0-9-generic 
root=UUID=02bad6b5-ca8f-4184-b477-935995e14bdc ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.17.0-9-generic N/A
   linux-backports-modules-4.17.0-9-generic  N/A
   linux-firmware1.174
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/06/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX561UD.304
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX561UD
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 31
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX561UD.304:bd03/06/2018:svnASUSTeKCOMPUTERINC.:pnUX561UD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX561UD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct31:cvr1.0:
  dmi.product.family: ZenBook Flip
  dmi.product.name: UX561UD
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

2018-09-07 Thread kernelorg

So still no concrete 100% sure fire solution?

Incredible.

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

Title:
  Ryzen 1800X freeze - rcu_sched detected stalls on CPUs/tasks

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

Bug description:
  Hi,

  
  We aregetting various kernel crash on a pretty new config.
  We're using Ryzen 1800X CPU with X370 Gaming Pro Carbon MB (7A32V1) using 
latest BIOS available (1.52)

  We are running Ubuntu 17.04 (amd64), we've tried different kernel version, 
native one and releases from http://kernel.ubuntu.com/~kernel-ppa/mainline/ too.
  Tested kernel version:

  native 17.04 kernel
  4.10.15

  Issues are the same, we're getting random freeze on the machine.

  Here is kern.log entry when happening :

  May 10 22:41:56 dev2 kernel: [24366.186246] INFO: rcu_sched detected stalls 
on CPUs/tasks:
  May 10 22:41:56 dev2 kernel: [24366.187618] 0-...: (1 GPs behind) 
idle=49b/1/0 softirq=28561/28563 fqs=913449
  May 10 22:41:56 dev2 kernel: [24366.188977] (detected by 12, t=1860207 
jiffies, g=10001, c=1, q=4656)
  May 10 22:41:56 dev2 kernel: [24366.190344] Task dump for CPU 0:
  May 10 22:41:56 dev2 kernel: [24366.190345] swapper/0   R  running task   
 0 0  0 0x0008
  May 10 22:41:56 dev2 kernel: [24366.190348] Call Trace:
  May 10 22:41:56 dev2 kernel: [24366.190354]  ? native_safe_halt+0x6/0x10
  May 10 22:41:56 dev2 kernel: [24366.190355]  ? default_idle+0x20/0xd0
  May 10 22:41:56 dev2 kernel: [24366.190358]  ? arch_cpu_idle+0xf/0x20
  May 10 22:41:56 dev2 kernel: [24366.190360]  ? default_idle_call+0x23/0x30
  May 10 22:41:56 dev2 kernel: [24366.190362]  ? do_idle+0x16f/0x200
  May 10 22:41:56 dev2 kernel: [24366.190364]  ? cpu_startup_entry+0x71/0x80
  May 10 22:41:56 dev2 kernel: [24366.190366]  ? rest_init+0x77/0x80
  May 10 22:41:56 dev2 kernel: [24366.190368]  ? start_kernel+0x464/0x485
  May 10 22:41:56 dev2 kernel: [24366.190369]  ? 
early_idt_handler_array+0x120/0x120
  May 10 22:41:56 dev2 kernel: [24366.190371]  ? 
x86_64_start_reservations+0x24/0x26
  May 10 22:41:56 dev2 kernel: [24366.190372]  ? x86_64_start_kernel+0x14d/0x170
  May 10 22:41:56 dev2 kernel: [24366.190373]  ? start_cpu+0x14/0x14
  May 10 22:44:56 dev2 kernel: [24546.188093] INFO: rcu_sched detected stalls 
on CPUs/tasks:
  May 10 22:44:56 dev2 kernel: [24546.189461] 0-...: (1 GPs behind) 
idle=49b/1/0 softirq=28561/28563 fqs=935027
  May 10 22:44:56 dev2 kernel: [24546.190823] (detected by 14, t=1905212 
jiffies, g=10001, c=1, q=4740)
  May 10 22:44:56 dev2 kernel: [24546.192191] Task dump for CPU 0:
  May 10 22:44:56 dev2 kernel: [24546.192192] swapper/0   R  running task   
 0 0  0 0x0008
  May 10 22:44:56 dev2 kernel: [24546.192195] Call Trace:
  May 10 22:44:56 dev2 kernel: [24546.192199]  ? native_safe_halt+0x6/0x10
  May 10 22:44:56 dev2 kernel: [24546.192201]  ? default_idle+0x20/0xd0
  May 10 22:44:56 dev2 kernel: [24546.192203]  ? arch_cpu_idle+0xf/0x20
  May 10 22:44:56 dev2 kernel: [24546.192204]  ? default_idle_call+0x23/0x30
  May 10 22:44:56 dev2 kernel: [24546.192206]  ? do_idle+0x16f/0x200
  May 10 22:44:56 dev2 kernel: [24546.192208]  ? cpu_startup_entry+0x71/0x80
  May 10 22:44:56 dev2 kernel: [24546.192210]  ? rest_init+0x77/0x80
  May 10 22:44:56 dev2 kernel: [24546.192211]  ? start_kernel+0x464/0x485
  May 10 22:44:56 dev2 kernel: [24546.192213]  ? 
early_idt_handler_array+0x120/0x120
  May 10 22:44:56 dev2 kernel: [24546.192214]  ? 
x86_64_start_reservations+0x24/0x26
  May 10 22:44:56 dev2 kernel: [24546.192215]  ? x86_64_start_kernel+0x14d/0x170
  May 10 22:44:56 dev2 kernel: [24546.192217]  ? start_cpu+0x14/0x14

  Depending on the kernel version, we've got NMI watchdog errors related to CPU 
stuck (mentioning the CPU core id, which is random).
  Crash is happening randomly, but in general after some hours (3-4h).

  Now, we've installed kernel 4.11.0-041100-generic #201705041534 this morning 
and waiting for crash...
  For now, the machine is not "used", at least, it's not CPU stressed...

  
  Thanks
  --- 
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  DistroRelease: Ubuntu 17.04
  InstallationDate: Installed on 2017-05-09 (1 days ago)
  InstallationMedia: Ubuntu-Server 17.04 "Zesty Zapus" - Release amd64 
(20170412)
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  Tags:  zesty
  Uname: Linux 4.11.0-041100-generic x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True

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

-- 
Mailing list: https://launchpad.net/~

[Kernel-packages] [Bug 1690085]

2018-09-07 Thread kernel

Who knows ?

When I say that "Typical Current Idle" appears to eliminate the "freeze
when idle" problem, I mean that (a) that is my experience (to date), and
(b) I have seen others reporting similar experience.

I'm not aware of any public, definitive information from AMD, any
motherboard vendor or the relevant kernel folk -- certainly nothing
which says what the "Typical Current Idle" BIOS option actually does,
and whether or how it solves the problem, in part or completely.

Sadly, this long thread has almost nothing to do with identifying any
actual Kernel bug or bugs.  It's more a sort of support group.  [Hello,
I'm Chris and I'm an AMD Ryzen user... since I found the "Typical
Current Idle" BIOS option, I haven't had a "freeze while idle" for two
weeks -- praise be.]

If you are looking for useful information, look away now: angry,
bewildered person about to howl at the moon...

--

...do I find the situation "Incredible" ?  hmmm...

[Final warning: reduced signal/noise ration ahead.]

I bought my Ryzen machine the moment I could order it.

When I came to build it, I found there was some confusion about the
"standard" fitting for the CPU cooler -- the plate glued to the
motherboard and the cooler fitting were incompatible.  I found myself in
a three-way stand-off between AMD, the motherboard vendor and the cooler
vendor.  If there was a specification for the standard AM4 socket
fitting for the cooler, it was Top Secret.  In the end I voided all
warranties, ripped the plate from the motherboard and replaced it by the
one supplied with the cooler.

When I set up my new machine, I found the standard configuration for the
memory was not as fast as I expected, noting
.  But, I
stumbled across this
 where I discovered that the 2667
MT/s I was expecting was for 2 DIMMs; with my 4 DIMMs, 2133 MT/s is what
I should have expected.  Silly Me !  I have seen BIOSes since then which
are supposed to improve memory support... but I think that's more
options for overclocking... who knows ?  Call me old fashioned, but I am
disappointed (but no longer surprised) that I cannot find an AMD data
sheet that specifies memory support (or much of anything else, for that
matter).

Can I find any documentation for AGESA ?  No.  It's various versions
(and changes in version numbering) ?  No.

Does my motherboard vendor provide release notes for each BIOS version ?
No.  How did I discover which BIOS version had the "Typical Current
Idle" option ?  By experiment.

If the platform_x86...@kernel-bugs.osdl.org fairy has died because I
stopped clapping, then I'm sorry.

... so, Incredible ?  Nah.  Infuriating ?  You bet.

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

Title:
  Ryzen 1800X freeze - rcu_sched detected stalls on CPUs/tasks

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

Bug description:
  Hi,

  
  We aregetting various kernel crash on a pretty new config.
  We're using Ryzen 1800X CPU with X370 Gaming Pro Carbon MB (7A32V1) using 
latest BIOS available (1.52)

  We are running Ubuntu 17.04 (amd64), we've tried different kernel version, 
native one and releases from http://kernel.ubuntu.com/~kernel-ppa/mainline/ too.
  Tested kernel version:

  native 17.04 kernel
  4.10.15

  Issues are the same, we're getting random freeze on the machine.

  Here is kern.log entry when happening :

  May 10 22:41:56 dev2 kernel: [24366.186246] INFO: rcu_sched detected stalls 
on CPUs/tasks:
  May 10 22:41:56 dev2 kernel: [24366.187618] 0-...: (1 GPs behind) 
idle=49b/1/0 softirq=28561/28563 fqs=913449
  May 10 22:41:56 dev2 kernel: [24366.188977] (detected by 12, t=1860207 
jiffies, g=10001, c=1, q=4656)
  May 10 22:41:56 dev2 kernel: [24366.190344] Task dump for CPU 0:
  May 10 22:41:56 dev2 kernel: [24366.190345] swapper/0   R  running task   
 0 0  0 0x0008
  May 10 22:41:56 dev2 kernel: [24366.190348] Call Trace:
  May 10 22:41:56 dev2 kernel: [24366.190354]  ? native_safe_halt+0x6/0x10
  May 10 22:41:56 dev2 kernel: [24366.190355]  ? default_idle+0x20/0xd0
  May 10 22:41:56 dev2 kernel: [24366.190358]  ? arch_cpu_idle+0xf/0x20
  May 10 22:41:56 dev2 kernel: [24366.190360]  ? default_idle_call+0x23/0x30
  May 10 22:41:56 dev2 kernel: [24366.190362]  ? do_idle+0x16f/0x200
  May 10 22:41:56 dev2 kernel: [24366.190364]  ? cpu_startup_entry+0x71/0x80
  May 10 22:41:56 dev2 kernel: [24366.190366]  ? rest_init+0x77/0x80
  May 10 22:41:56 dev2 kernel: [24366.190368]  ? start_kernel+0x464/0x485
  May 10 22:41:56 dev2 kernel: [24366.190369]  ? 
early_idt_handler_array+0x120/0x120
  May 10 22:41:56 dev2 kernel: [24366.190371]  ? 
x86_64_start_reservations+0x24/0x26
  May 10 22:41:56 dev2 kernel: [2

[Kernel-packages] [Bug 1788563] Re: L1TF mitigation not effective

2018-09-07 Thread Joseph Salisbury

I built a Bionic test kernel with commits 9df9516, b0a182f8 and cc51e542. The 
test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1788563/bionic

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

Note about installing test kernels:
• If the test kernel is prior to 4.15(Bionic) you need to install the 
linux-image and linux-image-extra .deb packages.
• If the test kernel is 4.15(Bionic) or newer, you need to install the 
linux-modules, linux-modules-extra and linux-image-unsigned .deb packages.

Thanks in advance!

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

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

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

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

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

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

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

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

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

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

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

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

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

Title:
  L1TF mitigation not effective

Status in linux package in Ubuntu:
  Triaged
Status in linux source package in Trusty:
  Triaged
Status in linux source package in Xenial:
  Triaged
Status in linux source package in Bionic:
  Triaged
Status in linux source package in Cosmic:
  Triaged

Bug description:
  Lenovo Thinkpad W530 system with 32 GB RAM

  dmesg | grep -i l1tf
  [0.038386] L1TF: System has more than MAX_PA/2 memory. L1TF mitigation 
not effective.
  [ 2652.469669] L1TF CPU bug present and SMT on, data leak possible. See 
CVE-2018-3646 and https://www.kernel.org/doc/html/latest/admin-guide/l1tf.html 
for details.

  Related:
  https://bugzilla.opensuse.org/show_bug.cgi?id=1105536

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-32-generic 4.15.0-32.35
  ProcVersionSignature: Ubuntu 4.15.0-32.35-generic 4.15.18
  Uname: Linux 4.15.0-32-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  pgera  2809 F pulseaudio
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Thu Aug 23 03:38:40 2018
  InstallationDate: Installed on 2018-08-11 (12 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: LENOVO 24382LU
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-32-generic 
root=UUID=e2607c8a-4bd1-49fe-ad07-83046492fac5 ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-32-generic N/A
   linux-backports-modules-4.15.0-32-generic  N/A
   linux-firmware 1.173.1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/11/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G5ETB2WW (2.72 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 24382LU
  dmi.board.vendor: LENOVO
  dmi.board.version: NO DPK
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrG5ETB2WW(2.72):bd06/11/2018:svnLENOVO:pn24382LU:pvrThinkPadW530:rvnLENOVO:rn24382LU:rvrNODPK:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad W530
  dmi.product.name: 24382LU
  dmi.product.version: ThinkPad W530
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1788563/+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 1789834] Re: off-by-one bug in L1TF mitigation

2018-09-07 Thread Joseph Salisbury

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

** This bug has been marked a duplicate of bug 1788563
   L1TF mitigation not effective

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

Title:
  off-by-one bug in L1TF mitigation

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

Bug description:
  due to an off-by-one bug in the L1TF patch, the "rare" case of systems still 
vulnerable
  is more frequent.

  This typically happens on Nehalem+ destop/entry-level server systems
  with 32G memory installed.

  Originally this was reported in OpenSUSE, but I can confirm this is
  also happens with the latest trusty kernel (3.13.0-157-generic)

  
https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git/commit/?id=b0a182f875689647b014bc01d36b340217792852

  The following patch increases the memory limit for the mitigation on
  these systems in general:

  
https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git/commit/?h=x86/urgent&id=cc51e5428ea54f575d49cfcede1d4cb3a72b4ec4

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1789834/+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 1790595] Re: Line 6 POD HD500 driver fault

2018-09-07 Thread Губанов Сергей

Same error with v4.19-rc2. I run apport-collect with v4.19, it create
only two posts after you.

[   98.377153] usb 1-5: new high-speed USB device number 5 using xhci_hcd
[   98.504474] usb 1-5: config 1 interface 1 altsetting 0 bulk endpoint 0x1 has 
invalid maxpacket 64
[   98.504482] usb 1-5: config 1 interface 1 altsetting 0 bulk endpoint 0x81 
has invalid maxpacket 64
[   98.504873] usb 1-5: New USB device found, idVendor=0e41, idProduct=414d, 
bcdDevice= 0.00
[   98.504878] usb 1-5: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[   98.504881] usb 1-5: Product: POD HD500
[   98.504885] usb 1-5: Manufacturer: Line 6
[   98.527466] snd_usb_podhd 1-5:1.0: Line 6 POD HD500 found
[   98.528210] snd_usb_podhd 1-5:1.0: Line 6 POD HD500 now attached
[   98.528242] snd_usb_podhd 1-5:1.1: Line 6 POD HD500 found
[   98.528244] usb 1-5: selecting invalid altsetting 1
[   98.528246] snd_usb_podhd 1-5:1.1: set_interface failed
[   98.528250] snd_usb_podhd 1-5:1.1: Line 6 POD HD500 now disconnected
[   98.528257] snd_usb_podhd: probe of 1-5:1.1 failed with error -22
[   98.528271] usbcore: registered new interface driver snd_usb_podhd


I bought that device when I used 14.04 KXStudio with kernel v3.14 and error was 
present there.
I start a thread at https://ubuntuforums.org/showthread.php?t=2385101. After 
Temüjin answer i install Ubuntu Release with kernel v4.15 - Kubuntu 18.04? but 
still no luck with POD HD500.

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

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

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

Title:
  Line 6 POD HD500 driver fault

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Release:
  DISTRIB_ID=Ubuntu
  DISTRIB_RELEASE=18.04
  DISTRIB_CODENAME=bionic
  DISTRIB_DESCRIPTION="Ubuntu 18.04.1 LTS"
  NAME="Ubuntu"
  VERSION="18.04.1 LTS (Bionic Beaver)"
  ID=ubuntu
  ID_LIKE=debian
  PRETTY_NAME="Ubuntu 18.04.1 LTS"
  VERSION_ID="18.04"
  HOME_URL="https://www.ubuntu.com/";
  SUPPORT_URL="https://help.ubuntu.com/";
  BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/";
  
PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy";

  VERSION_CODENAME=bionic
  UBUNTU_CODENAME=bionic

  uname:

  Linux GSLM 4.15.0-33-lowlatency #36-Ubuntu SMP PREEMPT Wed Aug 15
  17:20:28 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux

  lspci -vnvn  https://pastebin.com/7KM9bybk


  dmesg:

  usb 1-5: new high-speed USB device number 6 using xhci_hcd
  [ 44.208541] usb 1-5: config 1 interface 1 altsetting 0 bulk endpoint
  0x1 has invalid maxpacket 64
  [ 44.208548] usb 1-5: config 1 interface 1 altsetting 0 bulk endpoint
  0x81 has invalid maxpacket 64
  [ 44.209063] usb 1-5: New USB device found, idVendor=0e41, idProduct=414d
  [ 44.209068] usb 1-5: New USB device strings: Mfr=1, Product=2,
  SerialNumber=0
  [ 44.209072] usb 1-5: Product: POD HD500
  [ 44.209076] usb 1-5: Manufacturer: Line 6
  [ 44.209992] snd_usb_podhd 1-5:1.0: Line 6 POD HD500 found
  [ 44.210969] snd_usb_podhd 1-5:1.0: Line 6 POD HD500 now attached
  [ 44.211283] snd_usb_podhd 1-5:1.1: Line 6 POD HD500 found
  [ 44.211289] usb 1-5: selecting invalid altsetting 1
  [ 44.211292] snd_usb_podhd 1-5:1.1: set_interface failed
  [ 44.211304] snd_usb_podhd 1-5:1.1: Line 6 POD HD500 now disconnected
  [ 44.211317] snd_usb_podhd: probe of 1-5:1.1 failed with error -22
  [ 69.605987] nvidia-modeset: Allocated GPU:0
  (GPU-a23356f9-937a-4843-a3cc-da12769e0681) @ PCI::01:00.0
  [ 69.606386] nvidia-modeset: Freed GPU:0
  (GPU-a23356f9-937a-4843-a3cc-da12769e0681) @ PCI::01:00.0
  [ 153.206595] usb 1-5: USB disconnect, device number 6
  [ 153.207101] snd_usb_podhd 1-5:1.0: Line 6 POD HD500 now disconnected
  [ 165.694350] usb 1-1: new high-speed USB device number 7 using xhci_hcd
  [ 165.842687] usb 1-1: config 1 interface 1 altsetting 0 bulk endpoint
  0x1 has invalid maxpacket 64
  [ 165.842693] usb 1-1: config 1 interface 1 altsetting 0 bulk endpoint
  0x81 has invalid maxpacket 64
  [ 165.843146] usb 1-1: New USB device found, idVendor=0e41,
  idProduct=414d
  [ 165.843147] usb 1-1: New USB device strings: Mfr=1, Product=2,
  SerialNumber=0
  [ 165.843149] usb 1-1: Product: POD HD500
  [ 165.843150] usb 1-1: Manufacturer: Line 6
  [ 165.843800] snd_usb_podhd 1-1:1.0: Line 6 POD HD500 found
  [ 165.844514] snd_usb_podhd 1-1:1.0: Line 6 POD HD500 now attached
  [ 165.844740] snd_usb_podhd 1-1:1.1: Line 6 POD HD500 found
  [ 165.844742] usb 1-1: selecting invalid altsetting 1
  [ 165.844743] snd_usb_podhd 1-1:1.1: set_interface failed
  [ 165.844747] snd_usb_podhd 1-1:1.1: Line 6 POD HD500 now disconnected
  [ 165.844752] snd_usb_podhd: probe of 1-1:1.1 failed with error -22
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 18.04
  InstallationD

[Kernel-packages] [Bug 1790595] ProcEnviron.txt

2018-09-07 Thread Губанов Сергей

apport information

** Attachment added: "ProcEnviron.txt"
   
https://bugs.launchpad.net/bugs/1790595/+attachment/5186104/+files/ProcEnviron.txt

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

Title:
  Line 6 POD HD500 driver fault

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Release:
  DISTRIB_ID=Ubuntu
  DISTRIB_RELEASE=18.04
  DISTRIB_CODENAME=bionic
  DISTRIB_DESCRIPTION="Ubuntu 18.04.1 LTS"
  NAME="Ubuntu"
  VERSION="18.04.1 LTS (Bionic Beaver)"
  ID=ubuntu
  ID_LIKE=debian
  PRETTY_NAME="Ubuntu 18.04.1 LTS"
  VERSION_ID="18.04"
  HOME_URL="https://www.ubuntu.com/";
  SUPPORT_URL="https://help.ubuntu.com/";
  BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/";
  
PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy";

  VERSION_CODENAME=bionic
  UBUNTU_CODENAME=bionic

  uname:

  Linux GSLM 4.15.0-33-lowlatency #36-Ubuntu SMP PREEMPT Wed Aug 15
  17:20:28 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux

  lspci -vnvn  https://pastebin.com/7KM9bybk


  dmesg:

  usb 1-5: new high-speed USB device number 6 using xhci_hcd
  [ 44.208541] usb 1-5: config 1 interface 1 altsetting 0 bulk endpoint
  0x1 has invalid maxpacket 64
  [ 44.208548] usb 1-5: config 1 interface 1 altsetting 0 bulk endpoint
  0x81 has invalid maxpacket 64
  [ 44.209063] usb 1-5: New USB device found, idVendor=0e41, idProduct=414d
  [ 44.209068] usb 1-5: New USB device strings: Mfr=1, Product=2,
  SerialNumber=0
  [ 44.209072] usb 1-5: Product: POD HD500
  [ 44.209076] usb 1-5: Manufacturer: Line 6
  [ 44.209992] snd_usb_podhd 1-5:1.0: Line 6 POD HD500 found
  [ 44.210969] snd_usb_podhd 1-5:1.0: Line 6 POD HD500 now attached
  [ 44.211283] snd_usb_podhd 1-5:1.1: Line 6 POD HD500 found
  [ 44.211289] usb 1-5: selecting invalid altsetting 1
  [ 44.211292] snd_usb_podhd 1-5:1.1: set_interface failed
  [ 44.211304] snd_usb_podhd 1-5:1.1: Line 6 POD HD500 now disconnected
  [ 44.211317] snd_usb_podhd: probe of 1-5:1.1 failed with error -22
  [ 69.605987] nvidia-modeset: Allocated GPU:0
  (GPU-a23356f9-937a-4843-a3cc-da12769e0681) @ PCI::01:00.0
  [ 69.606386] nvidia-modeset: Freed GPU:0
  (GPU-a23356f9-937a-4843-a3cc-da12769e0681) @ PCI::01:00.0
  [ 153.206595] usb 1-5: USB disconnect, device number 6
  [ 153.207101] snd_usb_podhd 1-5:1.0: Line 6 POD HD500 now disconnected
  [ 165.694350] usb 1-1: new high-speed USB device number 7 using xhci_hcd
  [ 165.842687] usb 1-1: config 1 interface 1 altsetting 0 bulk endpoint
  0x1 has invalid maxpacket 64
  [ 165.842693] usb 1-1: config 1 interface 1 altsetting 0 bulk endpoint
  0x81 has invalid maxpacket 64
  [ 165.843146] usb 1-1: New USB device found, idVendor=0e41,
  idProduct=414d
  [ 165.843147] usb 1-1: New USB device strings: Mfr=1, Product=2,
  SerialNumber=0
  [ 165.843149] usb 1-1: Product: POD HD500
  [ 165.843150] usb 1-1: Manufacturer: Line 6
  [ 165.843800] snd_usb_podhd 1-1:1.0: Line 6 POD HD500 found
  [ 165.844514] snd_usb_podhd 1-1:1.0: Line 6 POD HD500 now attached
  [ 165.844740] snd_usb_podhd 1-1:1.1: Line 6 POD HD500 found
  [ 165.844742] usb 1-1: selecting invalid altsetting 1
  [ 165.844743] snd_usb_podhd 1-1:1.1: set_interface failed
  [ 165.844747] snd_usb_podhd 1-1:1.1: Line 6 POD HD500 now disconnected
  [ 165.844752] snd_usb_podhd: probe of 1-1:1.1 failed with error -22
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-07-03 (63 days ago)
  InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  MachineType: ASUSTeK COMPUTER INC. N501VW
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-33-lowlatency 
root=UUID=d7f11886-eed1-4644-ac54-ada42c063889 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-33.36-lowlatency 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-33-lowlatency N/A
   linux-backports-modules-4.15.0-33-lowlatency  N/A
   linux-firmware1.173.1
  Tags:  bionic
  Uname: Linux 4.15.0-33-lowlatency x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/28/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: N501VW.304
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: N501VW
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrN501VW.304:bd11/28/2016:svnASUSTeKCOMPUTERINC.:pnN501VW:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnN501VW:rvr1.0:cv

[Kernel-packages] [Bug 1790595] Re: Line 6 POD HD500 driver fault

2018-09-07 Thread Губанов Сергей

apport information

** Description changed:

  Release:
  DISTRIB_ID=Ubuntu
  DISTRIB_RELEASE=18.04
  DISTRIB_CODENAME=bionic
  DISTRIB_DESCRIPTION="Ubuntu 18.04.1 LTS"
  NAME="Ubuntu"
  VERSION="18.04.1 LTS (Bionic Beaver)"
  ID=ubuntu
  ID_LIKE=debian
  PRETTY_NAME="Ubuntu 18.04.1 LTS"
  VERSION_ID="18.04"
  HOME_URL="https://www.ubuntu.com/";
  SUPPORT_URL="https://help.ubuntu.com/";
  BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/";
  
PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy";
  
  VERSION_CODENAME=bionic
  UBUNTU_CODENAME=bionic
  
  uname:
  
  Linux GSLM 4.15.0-33-lowlatency #36-Ubuntu SMP PREEMPT Wed Aug 15
  17:20:28 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
  
  lspci -vnvn  https://pastebin.com/7KM9bybk
  
  
  dmesg:
  
  usb 1-5: new high-speed USB device number 6 using xhci_hcd
  [ 44.208541] usb 1-5: config 1 interface 1 altsetting 0 bulk endpoint
  0x1 has invalid maxpacket 64
  [ 44.208548] usb 1-5: config 1 interface 1 altsetting 0 bulk endpoint
  0x81 has invalid maxpacket 64
  [ 44.209063] usb 1-5: New USB device found, idVendor=0e41, idProduct=414d
  [ 44.209068] usb 1-5: New USB device strings: Mfr=1, Product=2,
  SerialNumber=0
  [ 44.209072] usb 1-5: Product: POD HD500
  [ 44.209076] usb 1-5: Manufacturer: Line 6
  [ 44.209992] snd_usb_podhd 1-5:1.0: Line 6 POD HD500 found
  [ 44.210969] snd_usb_podhd 1-5:1.0: Line 6 POD HD500 now attached
  [ 44.211283] snd_usb_podhd 1-5:1.1: Line 6 POD HD500 found
  [ 44.211289] usb 1-5: selecting invalid altsetting 1
  [ 44.211292] snd_usb_podhd 1-5:1.1: set_interface failed
  [ 44.211304] snd_usb_podhd 1-5:1.1: Line 6 POD HD500 now disconnected
  [ 44.211317] snd_usb_podhd: probe of 1-5:1.1 failed with error -22
  [ 69.605987] nvidia-modeset: Allocated GPU:0
  (GPU-a23356f9-937a-4843-a3cc-da12769e0681) @ PCI::01:00.0
  [ 69.606386] nvidia-modeset: Freed GPU:0
  (GPU-a23356f9-937a-4843-a3cc-da12769e0681) @ PCI::01:00.0
  [ 153.206595] usb 1-5: USB disconnect, device number 6
  [ 153.207101] snd_usb_podhd 1-5:1.0: Line 6 POD HD500 now disconnected
  [ 165.694350] usb 1-1: new high-speed USB device number 7 using xhci_hcd
  [ 165.842687] usb 1-1: config 1 interface 1 altsetting 0 bulk endpoint
  0x1 has invalid maxpacket 64
  [ 165.842693] usb 1-1: config 1 interface 1 altsetting 0 bulk endpoint
  0x81 has invalid maxpacket 64
  [ 165.843146] usb 1-1: New USB device found, idVendor=0e41,
  idProduct=414d
  [ 165.843147] usb 1-1: New USB device strings: Mfr=1, Product=2,
  SerialNumber=0
  [ 165.843149] usb 1-1: Product: POD HD500
  [ 165.843150] usb 1-1: Manufacturer: Line 6
  [ 165.843800] snd_usb_podhd 1-1:1.0: Line 6 POD HD500 found
  [ 165.844514] snd_usb_podhd 1-1:1.0: Line 6 POD HD500 now attached
  [ 165.844740] snd_usb_podhd 1-1:1.1: Line 6 POD HD500 found
  [ 165.844742] usb 1-1: selecting invalid altsetting 1
  [ 165.844743] snd_usb_podhd 1-1:1.1: set_interface failed
  [ 165.844747] snd_usb_podhd 1-1:1.1: Line 6 POD HD500 now disconnected
  [ 165.844752] snd_usb_podhd: probe of 1-1:1.1 failed with error -22
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-07-03 (63 days ago)
  InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  MachineType: ASUSTeK COMPUTER INC. N501VW
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-33-lowlatency 
root=UUID=d7f11886-eed1-4644-ac54-ada42c063889 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-33.36-lowlatency 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-33-lowlatency N/A
   linux-backports-modules-4.15.0-33-lowlatency  N/A
   linux-firmware1.173.1
  Tags:  bionic
  Uname: Linux 4.15.0-33-lowlatency x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/28/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: N501VW.304
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: N501VW
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrN501VW.304:bd11/28/2016:svnASUSTeKCOMPUTERINC.:pnN501VW:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnN501VW:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: N
  dmi.product.name: N501VW
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
+ --- 
+ ProblemType: Bug
+ ApportVersion: 2.20.9-0ubuntu7.2
+ Architecture: amd64
+ CurrentDesktop: KDE
+ DistroRelease: Ubuntu 18.04
+ InstallationDate: Installed on 2018-07-03 (66 days ago)
+ Installation

78 matches

Mail list logo