date:20160331

[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/1493989

Title:
  After display goes to sleep, sometimes external monitor is black

Status in linux package in Ubuntu:
  Expired

Bug description:
  In a gnome session, my screen locks & turns off after a certain amount
  of inactivity (but the system is not in suspend).

  When I wake the display back up by moving mouse / hitting a key, it
  seems like my external monitor is redetected -- both internal &
  external screen blink black as if I had just plugged in my external
  monitor, and then _sometimes_ the external monitor stays black (but
  thinks it is receiving input).  Other times it's fine, but when the
  issue happens, the displays control panel still thinks the external
  screen is connected, just nothing is visible.  Unplugging & replugging
  the screen fixes the issue, and it happens maybe 1/2 the time the
  display locks.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: xserver-xorg-video-intel 2:2.99.917+git20150808-0ubuntu2
  ProcVersionSignature: Ubuntu 4.2.0-7.7-generic 4.2.0
  Uname: Linux 4.2.0-7-generic x86_64
  ApportVersion: 2.18-0ubuntu9
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: GNOME
  Date: Wed Sep  9 13:05:10 2015
  DistUpgraded: Fresh install
  DistroCodename: wily
  DistroVariant: ubuntu
  DkmsStatus: virtualbox, 5.0.2, 4.2.0-7-generic, x86_64: installed
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Crystal Well Integrated Graphics Controller [8086:0d26] 
(rev 08) (prog-if 00 [VGA controller])
 Subsystem: Apple Inc. Device [106b:0147]
  InstallationDate: Installed on 2015-08-21 (19 days ago)
  InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Alpha amd64 (20150819)
  MachineType: Apple Inc. MacBookPro11,4
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.2.0-7-generic.efi.signed 
root=/dev/mapper/ubuntu--gnome--vg-root ro quiet splash vt.handoff=7
  SourcePackage: xserver-xorg-video-intel
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/05/2015
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: MBP114.88Z.0172.B04.1506051511
  dmi.board.name: Mac-06F11FD93F0323C5
  dmi.board.vendor: Apple Inc.
  dmi.board.version: MacBookPro11,4
  dmi.chassis.type: 9
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-06F11FD93F0323C5
  dmi.modalias: 
dmi:bvnAppleInc.:bvrMBP114.88Z.0172.B04.1506051511:bd06/05/2015:svnAppleInc.:pnMacBookPro11,4:pvr1.0:rvnAppleInc.:rnMac-06F11FD93F0323C5:rvrMacBookPro11,4:cvnAppleInc.:ct9:cvrMac-06F11FD93F0323C5:
  dmi.product.name: MacBookPro11,4
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.
  version.compiz: compiz N/A
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.64-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.6.3-1ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.6.3-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.17.2-1ubuntu6
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.2-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 
1:7.5.0+git20150819-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20150808-0ubuntu2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.11-1ubuntu3
  xserver.bootTime: Wed Sep  9 11:12:13 2015
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id   41006 
   vendor APP
  xserver.version: 2:1.17.2-1ubuntu6

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1493989/+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 1526683] Re: 10ec:8821 rtl8821ae loses connection occasionally on 2.4 GHz network requiring hardware button to be toggled twice for connection to be re-established

[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/1526683

Title:
  10ec:8821 rtl8821ae loses connection occasionally on 2.4 GHz network
  requiring hardware button to be toggled twice for connection to be re-
  established

Status in linux package in Ubuntu:
  Expired

Bug description:
  rtl8821ae loses connection occasionally connected to 802.11n 2.4 GHz
  ASUS Wireless Router RT-AC51U (firmware 3.0.0.4.378_9135-gac2b2c2on).
  This requires WiFi hardware button to be toggled twice for connection
  to be re-established.

  WORKAROUND: Set router to "legacy" mode (i.e. 802.11g).

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.3.0-2-generic 4.3.0-2.11 [modified: 
boot/vmlinuz-4.3.0-2-generic]
  ProcVersionSignature: Ubuntu 4.3.0-2.11-generic 4.3.0
  Uname: Linux 4.3.0-2-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.19.3-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  mikaela1361 F pulseaudio
   /dev/snd/controlC1:  mikaela1361 F pulseaudio
  CurrentDesktop: MATE
  Date: Wed Dec 16 11:35:09 2015
  HibernationDevice: RESUME=UUID=431ec214-73ef-4058-b283-5721bb5a45d2
  InstallationDate: Installed on 2015-12-12 (3 days ago)
  InstallationMedia: Ubuntu-MATE 16.04 LTS "Xenial Xerus" - Alpha amd64 
(20151212)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0bda:57b4 Realtek Semiconductor Corp.
   Bus 001 Device 006: ID 13d3:3414 IMC Networks
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. X550JX
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.3.0-2-generic.efi.signed 
root=UUID=ab0e7270-40bc-4a68-a541-59fd96690354 ro rw acpi_osi=
  RelatedPackageVersions:
   linux-restricted-modules-4.3.0-2-generic N/A
   linux-backports-modules-4.3.0-2-generic  N/A
   linux-firmware   1.154
  SourcePackage: linux
  UdevLog: Error: [Errno 2] Tiedostoa tai hakemistoa ei ole: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/07/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X550JX.204
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X550JX
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrX550JX.204:bd05/07/2015:svnASUSTeKCOMPUTERINC.:pnX550JX:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX550JX:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: X550JX
  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/1526683/+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 1514078] Re: Ubuntu freezes on boot when asking for encryption password on kernels newer then 3.19.0-28-generic

[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/1514078

Title:
  Ubuntu freezes on boot when asking for encryption password on kernels
  newer then 3.19.0-28-generic

Status in linux package in Ubuntu:
  Expired

Bug description:
  I have my main partition encrypted. When I start my computer, Ubuntu
  will prompt me to enter my disk encryption password. This works fine
  on the kernel 3.19.0-28-generic, but if I use any of the newer
  kernels, like 29, 30, 31 and 32, the system appears to freeze as soon
  as it gets to the prompt screen.

  I can't actually tell whats going on when its frozen. The only symptom is 
that it does not accept keyboard input anymore, so I can't actually enter my 
encryption password. Nothing happens when I press the keys. It might have been 
that
  1) the whole computer had a kernel panic, 
  2) it might be frozen in some other way,
  3) or it may be just that something went wrong when setting up my keyboard to 
accept input and that the computer is otherwise running fine.

  I don't really know, all I can really tell is that if I go back to an older 
kernel, like 28, it works absolutely fine, but anything newer and I can't boot 
my computer at all.
  --- 
  ApportVersion: 2.17.2-0ubuntu1.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  bradley1734 F pulseaudio
   /dev/snd/controlC0:  bradley1734 F pulseaudio
  DistroRelease: Ubuntu 15.04
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=a56109c4-0eb7-418f-b525-2ae82c52ec32
  InstallationDate: Installed on 2015-08-31 (73 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 064e:9700 Suyin Corp. 
   Bus 001 Device 002: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. UX305FA
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-28-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.19.0-28.30-generic 3.19.8-ckt5
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-3.19.0-28-generic N/A
   linux-backports-modules-3.19.0-28-generic  N/A
   linux-firmware 1.143.4
  Tags:  vivid
  UdevLog: Error: [Errno 2] Aucun fichier ou dossier de ce type: '/var/log/udev'
  Uname: Linux 3.19.0-28-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 03/26/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX305FA.208
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX305FA
  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.:bvrUX305FA.208:bd03/26/2015:svnASUSTeKCOMPUTERINC.:pnUX305FA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX305FA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: UX305FA
  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/1514078/+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 1539979] Re: error

[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/1539979

Title:
  error

Status in linux package in Ubuntu:
  Expired

Bug description:
  error

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1539979/+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 1538202] Re: Reboot then waking up after suspend on Acer Asprire 7540

[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/1538202

Title:
  Reboot then waking up after suspend on Acer Asprire 7540

Status in linux package in Ubuntu:
  Expired

Bug description:
  I'm using Ubuntu 15.10.

  Then I wake up computer after suspend, it just reboots. This happens with 
X.org ATI driver only, but with fglrx I'm greeted with a black screen (even 
backlights are turned off) and I have to reboot anyway. (but whatever, fglrx 
works horrible, I would never install it back) 
  ALSO, computer wakes up normally on latest upstream kernel 
(4.5.0-040500rc1-generic)

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: linux-image-4.2.0-25-lowlatency 4.2.0-25.30
  ProcVersionSignature: Ubuntu 4.2.0-25.30-lowlatency 4.2.6
  Uname: Linux 4.2.0-25-lowlatency x86_64
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  potato 2548 F pulseaudio
   /dev/snd/controlC1:  potato 2548 F pulseaudio
  CurrentDesktop: Unity
  Date: Tue Jan 26 20:19:24 2016
  HibernationDevice: RESUME=UUID=2277e00a-0411-4136-b180-2892752df2e0
  InstallationDate: Installed on 2016-01-17 (9 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  MachineType: Acer Aspire 7540
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-25-lowlatency 
root=UUID=ae6c8d51-38da-4c25-9281-6b9ceac5b2ca ro quiet splash acpi_sleep=nonvs 
quiet splash acpi_sleep=nonvs vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.2.0-25-lowlatency N/A
   linux-backports-modules-4.2.0-25-lowlatency  N/A
   linux-firmware   1.149.3
  SourcePackage: linux
  UdevLog: Error: [Errno 2] Нет такого файла или каталога: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/07/2009
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: V1.11
  dmi.board.name: JV71TR
  dmi.board.vendor: Acer
  dmi.board.version: Rev
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvrV1.11:bd12/07/2009:svnAcer:pnAspire7540:pvr0100:rvnAcer:rnJV71TR:rvrRev:cvnAcer:ct10:cvrNone:
  dmi.product.name: Aspire 7540
  dmi.product.version: 0100
  dmi.sys.vendor: Acer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1538202/+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 1539852] Re: Ubuntu detects no bluetooth devices, Windows 10 on same laptop detects dozen

[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/1539852

Title:
  Ubuntu detects no bluetooth devices, Windows 10 on same laptop detects
  dozen

Status in linux package in Ubuntu:
  Expired

Bug description:
  Ubuntu detects no bluetooth devices, Windows 10 on same laptop detects
  dozen which is probably all bluetooth devices on this floor of this
  apartment house.

  I have no idea what Bluetooth chipset I have, the only information I
  found with googling and various system information tools is "realtek".
  I am hoping that either Apport includes that information or you could
  tell me how do I dig out that information.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.3.0-7-generic 4.3.0-7.18
  ProcVersionSignature: Ubuntu 4.3.0-7.18-generic 4.3.3
  Uname: Linux 4.3.0-7-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.19.4-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  mikaela1961 F pulseaudio
   /dev/snd/controlC1:  mikaela1961 F pulseaudio
  CurrentDesktop: MATE
  Date: Sat Jan 30 09:38:26 2016
  HibernationDevice: RESUME=UUID=431ec214-73ef-4058-b283-5721bb5a45d2
  InstallationDate: Installed on 2015-12-12 (48 days ago)
  InstallationMedia: Ubuntu-MATE 16.04 LTS "Xenial Xerus" - Alpha amd64 
(20151212)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0bda:57b4 Realtek Semiconductor Corp. 
   Bus 001 Device 002: ID 13d3:3414 IMC Networks 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. X550JX
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.3.0-7-generic.efi.signed 
root=UUID=ab0e7270-40bc-4a68-a541-59fd96690354 ro rw acpi_osi=
  RelatedPackageVersions:
   linux-restricted-modules-4.3.0-7-generic N/A
   linux-backports-modules-4.3.0-7-generic  N/A
   linux-firmware   1.155
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/31/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X550JX.209
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X550JX
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrX550JX.209:bd10/31/2015:svnASUSTeKCOMPUTERINC.:pnX550JX:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX550JX:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: X550JX
  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/1539852/+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 1540075] Re: Resume Problem on Dell Inspiron 1525

[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/1540075

Title:
  Resume Problem on Dell Inspiron 1525

Status in linux package in Ubuntu:
  Expired

Bug description:
  The problem occurs occasionally, but seems to happen more often
  lately.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-76-generic 3.13.0-76.120
  ProcVersionSignature: Ubuntu 3.13.0-76.120-generic 3.13.11-ckt30
  Uname: Linux 3.13.0-76-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gertq3 2229 F pulseaudio
  CurrentDesktop: Unity
  Date: Sun Jan 31 14:09:10 2016
  HibernationDevice: RESUME=UUID=740856ad-2375-4b37-a945-af238f3d9708
  InstallationDate: Installed on 2010-06-24 (2046 days ago)
  InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100429)
  MachineType: Dell Inc. Inspiron 1525
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-76-generic 
root=UUID=84b3520e-92ed-4b55-8a45-ad5b24337159 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-76-generic N/A
   linux-backports-modules-3.13.0-76-generic  N/A
   linux-firmware 1.127.20
  SourcePackage: linux
  UpgradeStatus: Upgraded to trusty on 2015-03-24 (312 days ago)
  dmi.bios.date: 10/27/2009
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A17
  dmi.board.name: 0U990C
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA17:bd10/27/2009:svnDellInc.:pnInspiron1525:pvr:rvnDellInc.:rn0U990C:rvr:cvnDellInc.:ct8:cvr:
  dmi.product.name: Inspiron 1525
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1540075/+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 1539080] Re: Intel wifi broken after resume

[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/1539080

Title:
  Intel wifi broken after resume

Status in linux package in Ubuntu:
  Expired

Bug description:
  After resume, wifi doesn't come back up, all wifi related commands
  take a long time before failing with input/output error.

  Kernel log only seems to show some slowpaths being hit, but wifi sure
  isn't working here...

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.3.0-7-generic 4.3.0-7.18
  ProcVersionSignature: Ubuntu 4.3.0-7.18-generic 4.3.3
  Uname: Linux 4.3.0-7-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.19.4-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  stgraber   2746 F pulseaudio
   /dev/snd/controlC0:  stgraber   2746 F pulseaudio
  Date: Thu Jan 28 14:37:03 2016
  InstallationDate: Installed on 2015-04-23 (279 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  MachineType: LENOVO 20BXCTO1WW
  ProcEnviron:
   LANGUAGE=en_CA:en
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_CA.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.3.0-7-generic.efi.signed 
root=UUID=2a5a25ae-6bd9-40e1-8554-c38e0883a462 ro quiet splash swapaccount=1 
vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.3.0-7-generic N/A
   linux-backports-modules-4.3.0-7-generic  N/A
   linux-firmware   1.155
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/10/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: JBET47WW (1.12 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20BXCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0E50512 STD
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrJBET47WW(1.12):bd03/10/2015:svnLENOVO:pn20BXCTO1WW:pvrThinkPadT450s:rvnLENOVO:rn20BXCTO1WW:rvrSDK0E50512STD:cvnLENOVO:ct10:cvrNone:
  dmi.product.name: 20BXCTO1WW
  dmi.product.version: ThinkPad T450s
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1539080/+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 1538444] Re: Cannot read Samsung 128Gb EVO Plus SD card

[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/1538444

Title:
  Cannot read Samsung 128Gb EVO Plus SD card

Status in linux package in Ubuntu:
  Expired

Bug description:
  Jan 26 23:39:42 raven kernel: [219527.166471] mmc0: cannot verify signal 
voltage switch
  Jan 26 23:39:42 raven kernel: [219527.296399] mmc0: tuning execution failed
  Jan 26 23:39:42 raven kernel: [219527.296404] mmc0: error -22 whilst 
initialising SD card
  Jan 26 23:39:43 raven kernel: [219528.627397] mmc0: cannot verify signal 
voltage switch
  Jan 26 23:39:43 raven kernel: [219528.760476] mmc0: tuning execution failed
  Jan 26 23:39:43 raven kernel: [219528.760482] mmc0: error -22 whilst 
initialising SD card
  Jan 26 23:39:45 raven kernel: [219530.096201] mmc0: cannot verify signal 
voltage switch
  Jan 26 23:39:45 raven kernel: [219530.227975] mmc0: new ultra high speed 
SDR104 SDXC card at address 59b4
  Jan 26 23:39:45 raven kernel: [219530.228182] mmcblk0: mmc0:59b4 0 119 
GiB 
  Jan 26 23:39:45 raven kernel: [219530.230631] mmcblk0: unknown error -22 
sending read/write command, card status 0x900
  Jan 26 23:39:45 raven kernel: [219530.844656] mmc0: cannot verify signal 
voltage switch
  Jan 26 23:39:45 raven kernel: [219530.973918] mmc0: tuning execution failed
  Jan 26 23:39:45 raven kernel: [219530.973923] mmc0: tried to reset card
  Jan 26 23:39:45 raven kernel: [219530.973926] blk_update_request: I/O error, 
dev mmcblk0, sector 0
  Jan 26 23:39:45 raven kernel: [219530.973929] Buffer I/O error on dev 
mmcblk0, logical block 0, async page read
  Jan 26 23:39:45 raven kernel: [219530.975764] ldm_validate_partition_table(): 
Disk read failed.
  Jan 26 23:39:45 raven kernel: [219530.975768] Dev mmcblk0: unable to read RDB 
block 0
  Jan 26 23:39:45 raven kernel: [219530.977623]  mmcblk0: unable to read 
partition table
  Jan 26 23:39:45 raven kernel: [219530.986856] mmcblk0: unknown error -22 
sending read/write command, card status 0x900
  Jan 26 23:39:46 raven kernel: [219531.601118] mmc0: cannot verify signal 
voltage switch
  Jan 26 23:39:46 raven kernel: [219531.728358] mmc0: tried to reset card

  /dev/mmcblk0 and /dev/mmcblk0p1 appear, but are not usable.

  The card works fine in my Samsung phone. I can write to it using MTP.
  I have 32Gb and 64Gb SanDisk cards which work fine in the laptop AND the 
phone.

  So this is just an incompatibility with this particular card and this
  laptop - all other combinations work fine.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: linux-image-4.2.0-25-generic 4.2.0-25.30
  ProcVersionSignature: Ubuntu 4.2.0-25.30-generic 4.2.6
  Uname: Linux 4.2.0-25-generic x86_64
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  shevek 3066 F pulseaudio
   /dev/snd/controlC1:  shevek 3066 F pulseaudio
  CurrentDesktop: XFCE
  Date: Tue Jan 26 23:48:26 2016
  HibernationDevice: RESUME=UUID=22fd2208-7557-432d-bbff-95dd97905323
  InstallationDate: Installed on 2015-05-18 (253 days ago)
  InstallationMedia: Xubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422.1)
  MachineType: LENOVO 20CKCT01WW
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.2.0-25-generic.efi.signed 
root=/dev/mapper/xubuntu--vg-root ro noprompt persistent quiet splash 
vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.2.0-25-generic N/A
   linux-backports-modules-4.2.0-25-generic  N/A
   linux-firmware1.149.3
  SourcePackage: linux
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: Upgraded to wily on 2016-01-17 (10 days ago)
  dmi.bios.date: 08/20/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N11ET34W (1.10 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20CKCT01WW
  dmi.board.vendor: LENOVO
  dmi.board.version: 0B98417 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN11ET34W(1.10):bd08/20/2015:svnLENOVO:pn20CKCT01WW:pvrThinkPadT550:rvnLENOVO:rn20CKCT01WW:rvr0B98417WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.name: 20CKCT01WW
  dmi.product.version: ThinkPad T550
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1538444/+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 1540045] Re: BUG: Bad rss-counter state mm:ffff88010af5cb00 idx:1 val:512

[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/1540045

Title:
  BUG: Bad rss-counter state mm:88010af5cb00 idx:1 val:512

Status in linux package in Ubuntu:
  Expired

Bug description:
  I'm not sure exactly what triggered this, but happened while a vmware
  virtual machine was under heavy load.

  ProblemType: KernelOops
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.3.0-7-generic 4.3.0-7.18 [modified: 
boot/vmlinuz-4.3.0-7-generic]
  ProcVersionSignature: Ubuntu 4.3.0-7.18-generic 4.3.3
  Uname: Linux 4.3.0-7-generic x86_64
  NonfreeKernelModules: nvidia
  Annotation: Your system might become unstable now and might need to be 
restarted.
  ApportVersion: 2.19.4-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  wade   2121 F pulseaudio
   /dev/snd/controlC1:  wade   2121 F pulseaudio
   /dev/snd/controlC0:  wade   2121 F pulseaudio
  Date: Sun Jan 31 04:14:52 2016
  Failure: oops
  HibernationDevice: RESUME=UUID=659ef7fe-fc16-45e4-a3cb-4484d08c8422
  InstallationDate: Installed on 2016-01-31 (0 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160130)
  MachineType: MSI MS-7924
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.3.0-7-generic.efi.signed 
root=UUID=740f64dc-d330-484d-9a81-d9c683d362ec ro rootflags=subvol=@ quiet 
splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: kerneloops-daemon 0.12+git20090217-3ubuntu9
  RfKill:
   
  SourcePackage: linux
  Title: BUG: Bad rss-counter state mm:88010af5cb00 idx:1 val:512
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/08/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V1.11
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z97M-G43(MS-7924)
  dmi.board.vendor: MSI
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: To be filled by O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV1.11:bd01/08/2016:svnMSI:pnMS-7924:pvr1.0:rvnMSI:rnZ97M-G43(MS-7924):rvr1.0:cvnMSI:ct3:cvr1.0:
  dmi.product.name: MS-7924
  dmi.product.version: 1.0
  dmi.sys.vendor: MSI

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1540045/+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 1563441] fozzie (i386) - tests ran: 155, failed: 1

tests ran: 155, failed: 1;
  
http://kernel.ubuntu.com/testing/4.4.0-17.33/fozzie__4.4.0-17.33__2016-04-01_01-19-00/results-index.html

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

Title:
  linux: 4.4.0-17.33 -proposed tracker

Status in Kernel Development Workflow:
  In Progress
Status in Kernel Development Workflow automated-testing series:
  Incomplete
Status in Kernel Development Workflow prepare-package series:
  Fix Released
Status in Kernel Development Workflow prepare-package-meta series:
  Fix Released
Status in Kernel Development Workflow prepare-package-signed series:
  Fix Released
Status in Kernel Development Workflow promote-to-proposed series:
  Fix Released
Status in Kernel Development Workflow promote-to-release series:
  New
Status in Kernel Development Workflow regression-testing series:
  New
Status in linux package in Ubuntu:
  New
Status in linux source package in Xenial:
  New

Bug description:
  This bug is for tracking the 4.4.0-17.33 upload package. This bug will
  contain status and testing results related to that upload.

  Block-Proposed: xenial linux 4.4.0-17.33
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  kernel-Prepare-package-start:Tuesday, 29. March 2016 16:41 UTC
  kernel-phase-changed:Tuesday, 29. March 2016 16:41 UTC
  kernel-phase:Prepare
  kernel-stable-Promote-to-proposed-end:Tuesday, 29. March 2016 17:01 UTC
  proposed-announcement-sent:True

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-development-workflow/+bug/1563441/+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 1563441] kili (amd64) - tests ran: 1, failed: 1

tests ran:   1, failed: 1;
  
http://kernel.ubuntu.com/testing/4.4.0-17.33/kili__4.4.0-17.33__2016-03-31_23-14-00/results-index.html

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

Title:
  linux: 4.4.0-17.33 -proposed tracker

Status in Kernel Development Workflow:
  In Progress
Status in Kernel Development Workflow automated-testing series:
  Incomplete
Status in Kernel Development Workflow prepare-package series:
  Fix Released
Status in Kernel Development Workflow prepare-package-meta series:
  Fix Released
Status in Kernel Development Workflow prepare-package-signed series:
  Fix Released
Status in Kernel Development Workflow promote-to-proposed series:
  Fix Released
Status in Kernel Development Workflow promote-to-release series:
  New
Status in Kernel Development Workflow regression-testing series:
  New
Status in linux package in Ubuntu:
  New
Status in linux source package in Xenial:
  New

Bug description:
  This bug is for tracking the 4.4.0-17.33 upload package. This bug will
  contain status and testing results related to that upload.

  Block-Proposed: xenial linux 4.4.0-17.33
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  kernel-Prepare-package-start:Tuesday, 29. March 2016 16:41 UTC
  kernel-phase-changed:Tuesday, 29. March 2016 16:41 UTC
  kernel-phase:Prepare
  kernel-stable-Promote-to-proposed-end:Tuesday, 29. March 2016 17:01 UTC
  proposed-announcement-sent:True

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-development-workflow/+bug/1563441/+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 1563441] dagmar (i386) - tests ran: 155, failed: 1

tests ran: 155, failed: 1;
  
http://kernel.ubuntu.com/testing/4.4.0-17.33/dagmar__4.4.0-17.33__2016-04-01_01-13-00/results-index.html

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

Title:
  linux: 4.4.0-17.33 -proposed tracker

Status in Kernel Development Workflow:
  In Progress
Status in Kernel Development Workflow automated-testing series:
  Incomplete
Status in Kernel Development Workflow prepare-package series:
  Fix Released
Status in Kernel Development Workflow prepare-package-meta series:
  Fix Released
Status in Kernel Development Workflow prepare-package-signed series:
  Fix Released
Status in Kernel Development Workflow promote-to-proposed series:
  Fix Released
Status in Kernel Development Workflow promote-to-release series:
  New
Status in Kernel Development Workflow regression-testing series:
  New
Status in linux package in Ubuntu:
  New
Status in linux source package in Xenial:
  New

Bug description:
  This bug is for tracking the 4.4.0-17.33 upload package. This bug will
  contain status and testing results related to that upload.

  Block-Proposed: xenial linux 4.4.0-17.33
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  kernel-Prepare-package-start:Tuesday, 29. March 2016 16:41 UTC
  kernel-phase-changed:Tuesday, 29. March 2016 16:41 UTC
  kernel-phase:Prepare
  kernel-stable-Promote-to-proposed-end:Tuesday, 29. March 2016 17:01 UTC
  proposed-announcement-sent:True

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-development-workflow/+bug/1563441/+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 1564712] Missing required logs.

This bug is missing log files that will aid in diagnosing the problem.
>From a terminal window please run:

apport-collect 1564712

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

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

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

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

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

Title:
  The Front MIC jack can't work on a HP desktop machine

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Summary: When plugin microphone to port on front panel, it can not be
  detected and not work. Rear one works fine.

  This bug is for tracking purposes; please do not triage.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1564712/+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 1564712] Re: The Front MIC jack can't work on a HP desktop machine

2016-03-31 Thread Hui Wang

** Changed in: hwe-next
   Importance: Undecided => Critical

** Changed in: hwe-next
 Assignee: (unassigned) => Hui Wang (hui.wang)

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

Title:
  The Front MIC jack can't work on a HP desktop machine

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  New

Bug description:
  Summary: When plugin microphone to port on front panel, it can not be
  detected and not work. Rear one works fine.

  This bug is for tracking purposes; please do not triage.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1564712/+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 1556096] Re: [Ubuntu 16.04.1] RELEASE and ACQUIRE atomics on Power

2016-03-31 Thread Tim Gardner

** Also affects: linux (Ubuntu Xenial)
   Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
   Status: Triaged

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

** Changed in: linux (Ubuntu Xenial)
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Tim Gardner 
(timg-tpi)

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

Title:
  [Ubuntu 16.04.1] RELEASE and ACQUIRE atomics on Power

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

Bug description:
  Will Deacon proposed the RELEASE/ACQUIRE/RELAXED semantics for atomic
  operations(https://lkml.org/lkml/2015/8/6/498), which has been already
  merged in 4.3-rc1. More people tend to use it for better
  performance(https://lkml.org/lkml/2015/9/20/47). These semantics are
  proposed for better fitting the need of high scalability.

   However, the efficient implementation hasn't been merged yet. As we
  have a weaker memory order model on POWER, if we didn't implement
  these atomics efficently, there would be no benefit we can gain from
  these new operations.

  A proposal of an efficient implemenation has been sent out to
  upstream(https://lkml.org/lkml/2015/9/16/527), hopefully will get
  merged. Still there may be more atomics having RELEASE and ACQUIRE
  semantics, and there need more effort to implement them correctly.
  Also, we need to spread these new atomic variants to LTC kernel team
  to understand what they can provide and how to use them.

  > Was this feature already accepted upstream?

  Not yet, still waiting to get into the maintainer's tree, but there is
  no obvious objection to this feature.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1556096/+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 1564712] [NEW] The Front MIC jack can't work on a HP desktop machine

2016-03-31 Thread Hui Wang

Public bug reported:

Summary: When plugin microphone to port on front panel, it can not be
detected and not work. Rear one works fine.

This bug is for tracking purposes; please do not triage.

** Affects: hwe-next
 Importance: Critical
 Assignee: Hui Wang (hui.wang)
 Status: New

** Affects: linux (Ubuntu)
 Importance: Critical
 Assignee: Hui Wang (hui.wang)
 Status: New

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

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

Title:
  The Front MIC jack can't work on a HP desktop machine

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  New

Bug description:
  Summary: When plugin microphone to port on front panel, it can not be
  detected and not work. Rear one works fine.

  This bug is for tracking purposes; please do not triage.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1564712/+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 1534856] Re: lsusb hangs

2016-03-31 Thread olza

I believe that I have the same problem, however it is my mouse that (I think) 
causes it.
At least my mouse loses power (not mouses fault as tested by plugging into 
other computers/usb power outlets).
Anything I can do to help?

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

Title:
  lsusb hangs

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  When plugging an external sound card into USB3 ports on my ASUSTeK
  P9X79 motherboard, lsusb hangs and the usb device no longer works.  If
  I plug the sound card into a USB2 port, lsusb does not hang but the
  device is not detected and there are 0 messages printed in dmesg.

  bash$ strace lsusb -v
  munmap(0x7fa344ff3000, 4096)= 0
  open("/sys/bus/usb/devices/usb3/descriptors", O_RDONLY) = 6
  read(6,

  It hangs on this read and Ctrl-C cannot kill it until I unplug the usb
  device.

  This device was working until maybe 1-2 months ago, I believe when
  signed UEFI kernels started getting pushed to LTS although that is
  just a guess on my part.  I've tried falling back but I can't find a
  kernel that works anymore.

  bash$ uname -a
  3.13.0-74-generic x86_64

  bash$ lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 14.04.3 LTS
  Release:  14.04
  Codename: trusty

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1534856/+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 1336541] Re: No TRIM via USB

2016-03-31 Thread Tom Yan

The ASMedia bridges (as of the USB 3.1 Gen 2 ASM1351) simply does NOT
have UNMAP->TRIM implemented at all. It does support the "ATA
PASSTHROUGH" SCSI command, and it does not block TRIM on that, so hdparm
works.

The only one I've seen that supports UNMAP->TRIM is JMicron JMS567.

However, the implementation seems to be only partially done. Apparently
it does not support / has issue with queued UNMAP commands though
(assuming the uas driver in the kernel is doing everything right).
Therefore, blkdiscard/fstrim will work fine with the usb-storage driver
(`u` quirk), but will have issue with the uas driver on it.

Also, for some reason (maybe the aforementioned one), it has the LBPME
bit set to 0. So you need to change the provisioning_mode sysfs file
with `echo -n unmap` too (though that can be necessary anyway when the
usb-storage driver (u quirk) is in use, since it prefers Read Capacity
(10), which does not check the LBPME bit at all).

Unlike the ASMedia chips, it seems to block TRIM in its ATA PASSTHROUGH
btw.

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

Title:
  No TRIM via USB

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  As USB attached SSDs are becoming quite big and affordable, along comes the 
idea of installing systems on these.
  But with current USB drivers, some functionality seems to be missing from USB 
subsystem.

  The system does not recognize it is an SSD, but it is corrected manually:
  # cat /etc/udev/rules.d/10-forcessd.rules
  SUBSYSTEM=="block", ATTRS{vendor}=="SanDisk", ATTRS{model}=="Extreme", 
KERNEL=="sd?", ATTR{queue/rotational}="0"

  # cat /sys/block/sdb/queue/rotational
  0

  Checked hdparm, it is saying I have TRIM on the device:
  # hdparm -I /dev/sdb

  /dev/sdb:

  ATA device, with non-removable media
   Model Number:   SanDisk pSSD
  (...)
  Commands/features:
   Enabled  Supported:
  (...)
  * Data Set Management TRIM supported (limit 8 blocks)
  * Deterministic read ZEROs after TRIM
  (...)

  Here is appropriate dmesg:
  [3.815604] usb 2-8: Manufacturer: SunplusIT INC.
  [4.122002] usb 3-3: new SuperSpeed USB device number 2 using xhci_hcd
  [4.138402] usb 3-3: New USB device found, idVendor=0781, idProduct=5580
  [4.138404] usb 3-3: New USB device strings: Mfr=1, Product=2, 
SerialNumber=3
  [4.138405] usb 3-3: Product: Extreme
  [4.138406] usb 3-3: Manufacturer: SanDisk
  [4.138407] usb 3-3: SerialNumber: AA011109131654094942
  [4.141393] usb-storage 3-3:1.0: USB Mass Storage device detected
  [4.141431] scsi0 : usb-storage 3-3:1.0
  [4.141703] usbcore: registered new interface driver usb-storage

  And:
  [5.331311] sd 0:0:0:0: [sdb] 122544516 512-byte logical blocks: (62.7 
GB/58.4 GiB)
  [5.331608] sd 0:0:0:0: [sdb] Write Protect is off
  [5.331611] sd 0:0:0:0: [sdb] Mode Sense: 33 00 00 08
  [5.331855] sd 0:0:0:0: [sdb] Write cache: disabled, read cache: enabled, 
doesn't support DPO or FUA
  [5.339849]  sdb: sdb1 sdb2 sdb3 < sdb5 >
  [5.340783] sd 0:0:0:0: [sdb] Attached SCSI disk

  From here I'll be using /boot formatted to ext4 to eliminate luks,lvm
  and btrfs from the equasion:

  # mount |grep sdb2
  /dev/sdb2 on /boot type ext4 (rw,noexec,discard)

  # fstrim -v /boot/
  fstrim: /boot/: FITRIM ioctl failed: Operation not supported

  # strace fstrim -v /boot/
  (...)
  open("/boot/", O_RDONLY)= 3
  ioctl(3, FITRIM, 0x7fffdded85c0)= -1 EOPNOTSUPP (Operation not 
supported)
  (...)

  During debugging, I've tried compiling a kernel with UAS module to
  check, it booted, system was g changed with the trim - as it wouldn't
  been used at all.

  Any ideas why TRIM is not working on USB?
  Any timeframes for possible fix?
  Any workarounds maybe?
  --- 
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  dome   2460 F pulseaudio
   /dev/snd/pcmC1D0p:   dome   2460 F...m pulseaudio
   /dev/snd/controlC0:  dome   2460 F pulseaudio
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=bafebd1d-6988-438f-afd4-b41bb8608616
  InstallationDate: Installed on 2014-06-12 (56 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  MachineType: LENOVO 20AR001AUK
  Package: linux (not installed)
  ProcEnviron:
   LANGUAGE=en_US
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-24-generic 
root=/dev/mapper/system-root ro rootflags=subvol=@ 
cryptopts=target=crypter,source=/dev/disk/by-uuid/dc149cdf-62f9-4e29-a048-dd0403f51d56,lvm=system,discard
 quiet splash crashkernel=384M-:128M vt.handoff=7
  ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9
  PulseList:
   Error:

[Kernel-packages] [Bug 1499556] Re: Computer Reboots Instead of Halting

2016-03-31 Thread Ed Novak

I recently tested this with the latest ubuntu 16.04 beta 2 image and I
have the same behaviour.

I've also tested with several variants of the acpi kernel parameter
including acpi=off, acpi=strict, and acpi=oldboot  none changed the
behaviour except for acpi=off.  When this parameter was set, I was able
to press the power button to shutdown but the system shuts down
_immediately_ and I'm fairly certain the OS hasn't even flushed to disk
yet, so that's not a good workaround.

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

Title:
  Computer Reboots Instead of Halting

Status in linux package in Ubuntu:
  Triaged

Bug description:
  With Ubuntu 14.04 LTS, everytime I try to shutdown my system reboots instead. 
I have tried a variety of shutdown methods including:
  sudo init 0
  sudo shutdown -P now
  sudo shutdown now
  sudo shutdown -h now
  sudo shutdown -H now
  sudo shutdown -HP now
  (all previous variants with "now" replaced with "1")
  shutting down via the KDE menu (clicking the menu, clicking 'leave' section, 
clicking shutdown in the dialog box).

  The system hard shuts down if I hold the power button for 5 seconds.

  I have attached a zip of my entire /var/log directory.

  ---
  ApportVersion: 2.14.1-0ubuntu3.15
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: kwin
  CurrentDesktop: KDE
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroRelease: Ubuntu 14.04
  DistroVariant: kubuntu
  DkmsStatus: fglrx-core, 15.200, 3.16.0-50-generic, x86_64: installed
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Kabini [Radeon HD 8330] [1002:9832] 
(prog-if 00 [VGA controller])
     Subsystem: ASRock Incorporation Device [1849:9832]
  InstallationDate: Installed on 2015-08-21 (53 days ago)
  InstallationMedia: Kubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150219.1)
  LightdmGreeterLog:
   QInotifyFileSystemWatcherEngine::addPaths: inotify_add_watch failed: No such 
file or directory
   QFileSystemWatcher: failed to add paths: /var/lib/lightdm/.config/ibus/bus
   Bus::open: Can not get ibus-daemon's address.
   IBusInputContext::createInputContext: no connection to ibus-daemon
   file:///usr/share/kde4/apps/lightdm-kde-greeter/themes/userbar/main.qml:135: 
Unable to assign [undefined] to QString usersession
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  NonfreeKernelModules: fglrx
  Package: xorg 1:7.7+1ubuntu8.1
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-50-generic 
root=UUID=13cf69b2-83fd-4907-ba34-fa3e24e8294a ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.16.0-50.67~14.04.1-generic 3.16.7-ckt16
  Tags:  trusty kubuntu
  Uname: Linux 3.16.0-50-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo users
  _MarkForUpload: True
  dmi.bios.date: 10/27/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.00
  dmi.board.name: QC5000-ITX/PH
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.00:bd10/27/2014:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnQC5000-ITX/PH:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.
  version.compiz: compiz N/A
  version.fglrx-installer: fglrx-installer N/A
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.60-2~ubuntu14.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri N/A
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
  xserver.bootTime: Tue Oct 13 20:01:14 2015
  xserver.configfile: default
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.16.0-1ubuntu1.2~trusty2
  xserver.video_driver: fglrx

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1499556/+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 1558701] bantam (amd64) - tests ran: 194, failed: 12

tests ran: 194, failed: 12;
  
http://kernel.ubuntu.com/testing/3.19.0-58.64/bantam__3.19.0-58.64__2016-03-31_22-36-00/results-index.html

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

Title:
  linux: 3.19.0-58.64 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  Confirmed
Status in Kernel SRU Workflow promote-to-updates series:
  Confirmed
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Vivid:
  New

Bug description:
  This bug is for tracking the 3.19.0-58.64 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
  kernel-stable-Prepare-package-start:Thursday, 17. March 2016 17:37 UTC
  kernel-stable-Promote-to-proposed-end:Thursday, 17. March 2016 18:02 UTC
  kernel-stable-Prepare-package-end:Friday, 18. March 2016 04:03 UTC
  kernel-stable-Promote-to-proposed-start:Friday, 18. March 2016 04:03 UTC
  kernel-stable-Verification-testing-start:Friday, 18. March 2016 13:01 UTC
  kernel-stable-Certification-testing-start:Friday, 18. March 2016 13:01 UTC
  kernel-stable-Security-signoff-start:Friday, 18. March 2016 13:01 UTC
  proposed-announcement-sent:True
  kernel-stable-Regression-testing-start:Friday, 18. March 2016 13:01 UTC
  kernel-stable-Security-signoff-end:Saturday, 19. March 2016 14:41 UTC
  kernel-stable-Regression-testing-end:Monday, 28. March 2016 15:02 UTC
  kernel-stable-Verification-testing-end:Tuesday, 29. March 2016 15:01 UTC
  kernel-stable-phase:CopyToUpdates
  kernel-stable-Promote-to-updates-start:Thursday, 31. March 2016 20:56 UTC
  kernel-stable-phase-changed:Thursday, 31. March 2016 20:56 UTC
  kernel-stable-Certification-testing-end:Thursday, 31. March 2016 20:56 UTC

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1558701/+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 1563441] fozzie (amd64) - tests ran: 182, failed: 1

tests ran: 182, failed: 1;
  
http://kernel.ubuntu.com/testing/4.4.0-17.33/fozzie__4.4.0-17.33__2016-03-31_23-13-00/results-index.html

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

Title:
  linux: 4.4.0-17.33 -proposed tracker

Status in Kernel Development Workflow:
  In Progress
Status in Kernel Development Workflow automated-testing series:
  Incomplete
Status in Kernel Development Workflow prepare-package series:
  Fix Released
Status in Kernel Development Workflow prepare-package-meta series:
  Fix Released
Status in Kernel Development Workflow prepare-package-signed series:
  Fix Released
Status in Kernel Development Workflow promote-to-proposed series:
  Fix Released
Status in Kernel Development Workflow promote-to-release series:
  New
Status in Kernel Development Workflow regression-testing series:
  New
Status in linux package in Ubuntu:
  New
Status in linux source package in Xenial:
  New

Bug description:
  This bug is for tracking the 4.4.0-17.33 upload package. This bug will
  contain status and testing results related to that upload.

  Block-Proposed: xenial linux 4.4.0-17.33
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  kernel-Prepare-package-start:Tuesday, 29. March 2016 16:41 UTC
  kernel-phase-changed:Tuesday, 29. March 2016 16:41 UTC
  kernel-phase:Prepare
  kernel-stable-Promote-to-proposed-end:Tuesday, 29. March 2016 17:01 UTC
  proposed-announcement-sent:True

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-development-workflow/+bug/1563441/+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 1563441] dagmar (amd64) - tests ran: 182, failed: 1

tests ran: 182, failed: 1;
  
http://kernel.ubuntu.com/testing/4.4.0-17.33/dagmar__4.4.0-17.33__2016-03-31_23-13-00/results-index.html

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

Title:
  linux: 4.4.0-17.33 -proposed tracker

Status in Kernel Development Workflow:
  In Progress
Status in Kernel Development Workflow automated-testing series:
  Incomplete
Status in Kernel Development Workflow prepare-package series:
  Fix Released
Status in Kernel Development Workflow prepare-package-meta series:
  Fix Released
Status in Kernel Development Workflow prepare-package-signed series:
  Fix Released
Status in Kernel Development Workflow promote-to-proposed series:
  Fix Released
Status in Kernel Development Workflow promote-to-release series:
  New
Status in Kernel Development Workflow regression-testing series:
  New
Status in linux package in Ubuntu:
  New
Status in linux source package in Xenial:
  New

Bug description:
  This bug is for tracking the 4.4.0-17.33 upload package. This bug will
  contain status and testing results related to that upload.

  Block-Proposed: xenial linux 4.4.0-17.33
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  kernel-Prepare-package-start:Tuesday, 29. March 2016 16:41 UTC
  kernel-phase-changed:Tuesday, 29. March 2016 16:41 UTC
  kernel-phase:Prepare
  kernel-stable-Promote-to-proposed-end:Tuesday, 29. March 2016 17:01 UTC
  proposed-announcement-sent:True

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-development-workflow/+bug/1563441/+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 1563441] modoc (ppc64el) - tests ran: 22, failed: 5

tests ran:  22, failed: 5;
  
http://kernel.ubuntu.com/testing/4.4.0-17.33/modoc__4.4.0-17.33__2016-04-01_00-02-00/results-index.html

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

Title:
  linux: 4.4.0-17.33 -proposed tracker

Status in Kernel Development Workflow:
  In Progress
Status in Kernel Development Workflow automated-testing series:
  Incomplete
Status in Kernel Development Workflow prepare-package series:
  Fix Released
Status in Kernel Development Workflow prepare-package-meta series:
  Fix Released
Status in Kernel Development Workflow prepare-package-signed series:
  Fix Released
Status in Kernel Development Workflow promote-to-proposed series:
  Fix Released
Status in Kernel Development Workflow promote-to-release series:
  New
Status in Kernel Development Workflow regression-testing series:
  New
Status in linux package in Ubuntu:
  New
Status in linux source package in Xenial:
  New

Bug description:
  This bug is for tracking the 4.4.0-17.33 upload package. This bug will
  contain status and testing results related to that upload.

  Block-Proposed: xenial linux 4.4.0-17.33
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  kernel-Prepare-package-start:Tuesday, 29. March 2016 16:41 UTC
  kernel-phase-changed:Tuesday, 29. March 2016 16:41 UTC
  kernel-phase:Prepare
  kernel-stable-Promote-to-proposed-end:Tuesday, 29. March 2016 17:01 UTC
  proposed-announcement-sent:True

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-development-workflow/+bug/1563441/+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 571728] Re: rngd quit after some time when using TPM

2016-03-31 Thread Tyler Hicks

Hi Laurent - Do you have any idea if this bug is still valid? I feel
like enough things have changed in rng-tools and tpm-rng since you filed
this bug that it may no longer be valid.

I've set up rngd on my laptop, with the TPM rng (via the tpm-rng module)
backing /dev/hwrng, to see if I see the same 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/571728

Title:
  rngd quit after some time when using TPM

Status in linux package in Ubuntu:
  Incomplete
Status in rng-tools package in Ubuntu:
  New

Bug description:
  Binary package hint: rng-tools

  Hi,

  rngd stop running after some time.

  In dmesg I get:

  [ 2262.262564] tpm_tis 00:09: Error left over data
  [ 2262.262580] tpm_tis 00:09: tpm_transmit: tpm_recv: error -5
  --- 
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.21.
  Architecture: amd64
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 0: Intel [HDA Intel], device 0: STAC92xx Analog [STAC92xx Analog]
 Subdevices: 2/2
 Subdevice #0: subdevice #0
 Subdevice #1: subdevice #1
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  bigon  1832 F pulseaudio
  CRDA: Error: [Errno 2] Aucun fichier ou dossier de ce type
  Card0.Amixer.info:
   Card hw:0 'Intel'/'HDA Intel at 0xf6adc000 irq 21'
 Mixer name : 'Intel G45 DEVCTG'
 Components : 'HDA:111d76b2,1028024f,00100302 
HDA:80862802,80860101,0010'
 Controls  : 24
 Simple ctrls  : 15
  DistroRelease: Ubuntu 10.04
  HibernationDevice: RESUME=UUID=2015b0ce-0d4e-4c1e-a43e-99849945e657
  MachineType: Dell Inc. Latitude E6500
  Package: linux (not installed)
  PccardctlIdent:
   Socket 0:
 no product info available
  PccardctlStatus:
   Socket 0:
 no card
  ProcCmdLine: BOOT_IMAGE=/vmlinuz-2.6.32-22-generic 
root=/dev/mapper/hostname-root ro quiet splash
  ProcEnviron:
   PATH=(custom, user)
   LANG=fr_BE.utf8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 2.6.32-22.33-generic 2.6.32.11+drm33.2
  Regression: No
  RelatedPackageVersions: linux-firmware 1.34
  Reproducible: Yes
  Tags: lucid  needs-upstream-testing
  Uname: Linux 2.6.32-22-generic x86_64
  UserGroups: adm admin cdrom dialout libvirtd lpadmin plugdev sambashare 
wireshark
  dmi.bios.date: 10/30/2009
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A18
  dmi.board.name: 0W612R
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA18:bd10/30/2009:svnDellInc.:pnLatitudeE6500:pvr:rvnDellInc.:rn0W612R:rvr:cvnDellInc.:ct8:cvr:
  dmi.product.name: Latitude E6500
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/571728/+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 1564463] Re: Joystick Dragonrise Axes confused in Ubuntu 14.04

2016-03-31 Thread Bug Watch Updater

** Changed in: linux (Debian)
   Status: Unknown => 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/1564463

Title:
  Joystick Dragonrise Axes confused in Ubuntu 14.04

Status in linux package in Ubuntu:
  Incomplete
Status in linux package in Debian:
  Confirmed

Bug description:
  In Ubuntu 14.04 axis 2 (left-right of the right joystick) is hardly
  working.

  Its conflicting and superimposed by axis 0 (left-right of the left
  joystick)

  Axis 2 was allready behaving bad in eralier versions now its completly
  broken.

  Also jscal complains when applying stored settings from earlier ubuntu
  versions as the joystick now has 6 axes [0-5] and used to have 7, but
  this seems correct.

  The Dragonrise chip seems to be very widespread among different
  speedlink and LinQ models

  There is a related bugreport in Debian Bug-Tracker: 
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=785606
  that makes

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

Here's the relevant information:

xenial linux 4.4.0-17.33 REGR summary

Please verify test results in http://people.canonical.com/~kernel/status
/adt-matrix/overall.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/1563441

Title:
  linux: 4.4.0-17.33 -proposed tracker

Status in Kernel Development Workflow:
  In Progress
Status in Kernel Development Workflow automated-testing series:
  Incomplete
Status in Kernel Development Workflow prepare-package series:
  Fix Released
Status in Kernel Development Workflow prepare-package-meta series:
  Fix Released
Status in Kernel Development Workflow prepare-package-signed series:
  Fix Released
Status in Kernel Development Workflow promote-to-proposed series:
  Fix Released
Status in Kernel Development Workflow promote-to-release series:
  New
Status in Kernel Development Workflow regression-testing series:
  New
Status in linux package in Ubuntu:
  New
Status in linux source package in Xenial:
  New

Bug description:
  This bug is for tracking the 4.4.0-17.33 upload package. This bug will
  contain status and testing results related to that upload.

  Block-Proposed: xenial linux 4.4.0-17.33
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  kernel-Prepare-package-start:Tuesday, 29. March 2016 16:41 UTC
  kernel-phase-changed:Tuesday, 29. March 2016 16:41 UTC
  kernel-phase:Prepare
  kernel-stable-Promote-to-proposed-end:Tuesday, 29. March 2016 17:01 UTC
  proposed-announcement-sent:True

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-development-workflow/+bug/1563441/+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 1563441] dagmar (amd64) - tests ran: 182, failed: 1

tests ran: 182, failed: 1;
  
http://kernel.ubuntu.com/testing/4.4.0-17.33/dagmar__4.4.0-17.33__2016-03-31_21-07-00/results-index.html

** Description changed:

  This bug is for tracking the 4.4.0-17.33 upload package. This bug will
  contain status and testing results related to that upload.
  
  Block-Proposed: xenial linux 4.4.0-17.33
- 
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  kernel-Prepare-package-start:Tuesday, 29. March 2016 16:41 UTC
  kernel-phase-changed:Tuesday, 29. March 2016 16:41 UTC
  kernel-phase:Prepare
  kernel-stable-Promote-to-proposed-end:Tuesday, 29. March 2016 17:01 UTC
+ proposed-announcement-sent:True

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

Title:
  linux: 4.4.0-17.33 -proposed tracker

Status in Kernel Development Workflow:
  In Progress
Status in Kernel Development Workflow automated-testing series:
  Incomplete
Status in Kernel Development Workflow prepare-package series:
  Fix Released
Status in Kernel Development Workflow prepare-package-meta series:
  Fix Released
Status in Kernel Development Workflow prepare-package-signed series:
  Fix Released
Status in Kernel Development Workflow promote-to-proposed series:
  Fix Released
Status in Kernel Development Workflow promote-to-release series:
  New
Status in Kernel Development Workflow regression-testing series:
  New
Status in linux package in Ubuntu:
  New
Status in linux source package in Xenial:
  New

Bug description:
  This bug is for tracking the 4.4.0-17.33 upload package. This bug will
  contain status and testing results related to that upload.

  Block-Proposed: xenial linux 4.4.0-17.33
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  kernel-Prepare-package-start:Tuesday, 29. March 2016 16:41 UTC
  kernel-phase-changed:Tuesday, 29. March 2016 16:41 UTC
  kernel-phase:Prepare
  kernel-stable-Promote-to-proposed-end:Tuesday, 29. March 2016 17:01 UTC
  proposed-announcement-sent:True

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-development-workflow/+bug/1563441/+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 1563441] Re: linux: 4.4.0-17.33 -proposed tracker

2016-03-31 Thread Andy Whitcroft

** Tags added: apw-b-p

** Description changed:

  This bug is for tracking the 4.4.0-17.33 upload package. This bug will
  contain status and testing results related to that upload.
+ 
+ Block-Proposed: xenial linux 4.4.0-17.33
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  kernel-Prepare-package-start:Tuesday, 29. March 2016 16:41 UTC
  kernel-phase-changed:Tuesday, 29. March 2016 16:41 UTC
  kernel-phase:Prepare
- kernel-stable-Promote-to-proposed-end:Thursday, 31. March 2016 19:01 UTC
- proposed-announcement-sent:True
+ kernel-stable-Promote-to-proposed-end:Tuesday, 29. March 2016 17:01 UTC

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

Title:
  linux: 4.4.0-17.33 -proposed tracker

Status in Kernel Development Workflow:
  In Progress
Status in Kernel Development Workflow automated-testing series:
  Incomplete
Status in Kernel Development Workflow prepare-package series:
  Fix Released
Status in Kernel Development Workflow prepare-package-meta series:
  Fix Released
Status in Kernel Development Workflow prepare-package-signed series:
  Fix Released
Status in Kernel Development Workflow promote-to-proposed series:
  Fix Released
Status in Kernel Development Workflow promote-to-release series:
  New
Status in Kernel Development Workflow regression-testing series:
  New
Status in linux package in Ubuntu:
  New
Status in linux source package in Xenial:
  New

Bug description:
  This bug is for tracking the 4.4.0-17.33 upload package. This bug will
  contain status and testing results related to that upload.

  Block-Proposed: xenial linux 4.4.0-17.33

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  kernel-Prepare-package-start:Tuesday, 29. March 2016 16:41 UTC
  kernel-phase-changed:Tuesday, 29. March 2016 16:41 UTC
  kernel-phase:Prepare
  kernel-stable-Promote-to-proposed-end:Tuesday, 29. March 2016 17:01 UTC

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-development-workflow/+bug/1563441/+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 1437492] Re: boot stalls on USB detection errors

2016-03-31 Thread Awesome Donkey

Since I switched to Arch because of this issue, I haven't encountered it
since. Maybe it's a Ubuntu kernel issue?

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

Title:
  boot stalls on USB detection errors

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

Bug description:
  My system boots slow. I investigated this and it seems 
systemd-udev-settle.service is the culprit.
  My system runs ext4 with GPT on UEFI.
  I do not use encryption or LVM.

  $ journalctl -u systemd-udev-settle
  -- Logs begin at fri 2015-03-27 19:03:06 CET, end at fri 2015-03-27 22:06:32 
CET. --
  mar 27 19:03:42 hostname systemd[1]: Started udev Wait for Complete Device 
Initialization.

  $ systemd-analyze
  Startup finished in 14.865s (firmware) + 11.133s (loader) + 6.127s (kernel) + 
42.079s (userspace) = 1min 14.206s

  $ systemd-analyze critical-chain
  http://paste.ubuntu.com/10691416/

  $ systemd-analyze blame
  36.013s systemd-udev-settle.service
  http://paste.ubuntu.com/10691314/

  $ systemctl show systemd-udev-settle.service -p RequiredBy
  RequiredBy=

  $ systemctl show systemd-udev-settle.service -p WantedBy
  WantedBy=friendly-recovery.service

  $ systemd-analyze plot > boot.svg
  http://imgh.us/boot_1.svg

  $ systemd-analyze dump
  http://paste.ubuntu.com/10691856/

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: systemd 219-5ubuntu1
  ProcVersionSignature: Ubuntu 3.19.0-10.10-generic 3.19.2
  Uname: Linux 3.19.0-10-generic x86_64
  ApportVersion: 2.16.2-0ubuntu5
  Architecture: amd64
  CurrentDesktop: GNOME-Flashback:Unity
  Date: Fri Mar 27 22:05:28 2015
  InstallationDate: Installed on 2013-12-26 (455 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  MachineType: ASUS All Series
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-10-generic.efi.signed 
root=UUID=31dc4488-28d4-4d2a-aa51-6733e237d5f8 ro quiet splash vt.handoff=7
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/18/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2103
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z87-PRO
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2103:bd08/18/2014:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ87-PRO:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: All Series
  dmi.product.version: System Version
  dmi.sys.vendor: ASUS

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1437492/+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 1558727] bantam (i386) - tests ran: 153, failed: 1

tests ran: 153, failed: 1;
  
http://kernel.ubuntu.com/testing/3.13.0-83.127/bantam__3.13.0-83.127__2016-03-31_18-40-00/results-index.html

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

Title:
  linux: 3.13.0-85.129 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Fix Released
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  Confirmed
Status in Kernel SRU Workflow promote-to-updates series:
  Confirmed
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Trusty:
  Confirmed

Bug description:
  This bug is for tracking the 3.13.0-85.129 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
  kernel-stable-Promote-to-proposed-end:Thursday, 17. March 2016 22:51 UTC
  kernel-stable-Prepare-package-end:Friday, 18. March 2016 03:05 UTC
  kernel-stable-Promote-to-proposed-start:Friday, 18. March 2016 03:05 UTC
  kernel-stable-Verification-testing-start:Friday, 18. March 2016 12:01 UTC
  kernel-stable-Certification-testing-start:Friday, 18. March 2016 12:02 UTC
  kernel-stable-Security-signoff-start:Friday, 18. March 2016 12:02 UTC
  proposed-announcement-sent:True
  kernel-stable-Regression-testing-start:Friday, 18. March 2016 12:02 UTC
  kernel-stable-Security-signoff-end:Friday, 18. March 2016 20:03 UTC
  kernel-stable-Regression-testing-end:Monday, 28. March 2016 15:03 UTC
  kernel-stable-Verification-testing-end:Tuesday, 29. March 2016 15:01 UTC
  kernel-stable-phase:CopyToUpdates
  kernel-stable-Promote-to-updates-start:Thursday, 31. March 2016 03:01 UTC
  kernel-stable-phase-changed:Thursday, 31. March 2016 03:01 UTC
  kernel-stable-Certification-testing-end:Thursday, 31. March 2016 03:01 UTC

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1558727/+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 1437492] Re: boot stalls on USB detection errors

2016-03-31 Thread Fred

Serge Malo,
A workaround is to enter the BIOS, keep the built-in Intel USB enabled, but set 
the third-party ASMedia USB to disabled.

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

Title:
  boot stalls on USB detection errors

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

Bug description:
  My system boots slow. I investigated this and it seems 
systemd-udev-settle.service is the culprit.
  My system runs ext4 with GPT on UEFI.
  I do not use encryption or LVM.

  $ journalctl -u systemd-udev-settle
  -- Logs begin at fri 2015-03-27 19:03:06 CET, end at fri 2015-03-27 22:06:32 
CET. --
  mar 27 19:03:42 hostname systemd[1]: Started udev Wait for Complete Device 
Initialization.

  $ systemd-analyze
  Startup finished in 14.865s (firmware) + 11.133s (loader) + 6.127s (kernel) + 
42.079s (userspace) = 1min 14.206s

  $ systemd-analyze critical-chain
  http://paste.ubuntu.com/10691416/

  $ systemd-analyze blame
  36.013s systemd-udev-settle.service
  http://paste.ubuntu.com/10691314/

  $ systemctl show systemd-udev-settle.service -p RequiredBy
  RequiredBy=

  $ systemctl show systemd-udev-settle.service -p WantedBy
  WantedBy=friendly-recovery.service

  $ systemd-analyze plot > boot.svg
  http://imgh.us/boot_1.svg

  $ systemd-analyze dump
  http://paste.ubuntu.com/10691856/

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: systemd 219-5ubuntu1
  ProcVersionSignature: Ubuntu 3.19.0-10.10-generic 3.19.2
  Uname: Linux 3.19.0-10-generic x86_64
  ApportVersion: 2.16.2-0ubuntu5
  Architecture: amd64
  CurrentDesktop: GNOME-Flashback:Unity
  Date: Fri Mar 27 22:05:28 2015
  InstallationDate: Installed on 2013-12-26 (455 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  MachineType: ASUS All Series
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-10-generic.efi.signed 
root=UUID=31dc4488-28d4-4d2a-aa51-6733e237d5f8 ro quiet splash vt.handoff=7
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/18/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2103
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z87-PRO
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2103:bd08/18/2014:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ87-PRO:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: All Series
  dmi.product.version: System Version
  dmi.sys.vendor: ASUS

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1437492/+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 1437492] Re: boot stalls on USB detection errors

2016-03-31 Thread Serge Malo

I see the same problem with 2 different m/b:
Asus X99-A and Asus Z97-A
I can see the problem with Kernels 3.16 and 3.19.

Does anyone have a work-around, such as changing USB parameters in the
BIOS?

I also see that a complete power down temporarily fixes the issue.

Also woth noting: my Z97-A system has a dual-boot (Ubuntu/Windows). When I boot 
Windows after having been in Ubuntu, Windows has the same issue: it seems 
frozen for about 30s when booting.
But when I do a cold boot in Windows, and only reboot in Windows, I don't see 
the problem.

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

Title:
  boot stalls on USB detection errors

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

Bug description:
  My system boots slow. I investigated this and it seems 
systemd-udev-settle.service is the culprit.
  My system runs ext4 with GPT on UEFI.
  I do not use encryption or LVM.

  $ journalctl -u systemd-udev-settle
  -- Logs begin at fri 2015-03-27 19:03:06 CET, end at fri 2015-03-27 22:06:32 
CET. --
  mar 27 19:03:42 hostname systemd[1]: Started udev Wait for Complete Device 
Initialization.

  $ systemd-analyze
  Startup finished in 14.865s (firmware) + 11.133s (loader) + 6.127s (kernel) + 
42.079s (userspace) = 1min 14.206s

  $ systemd-analyze critical-chain
  http://paste.ubuntu.com/10691416/

  $ systemd-analyze blame
  36.013s systemd-udev-settle.service
  http://paste.ubuntu.com/10691314/

  $ systemctl show systemd-udev-settle.service -p RequiredBy
  RequiredBy=

  $ systemctl show systemd-udev-settle.service -p WantedBy
  WantedBy=friendly-recovery.service

  $ systemd-analyze plot > boot.svg
  http://imgh.us/boot_1.svg

  $ systemd-analyze dump
  http://paste.ubuntu.com/10691856/

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: systemd 219-5ubuntu1
  ProcVersionSignature: Ubuntu 3.19.0-10.10-generic 3.19.2
  Uname: Linux 3.19.0-10-generic x86_64
  ApportVersion: 2.16.2-0ubuntu5
  Architecture: amd64
  CurrentDesktop: GNOME-Flashback:Unity
  Date: Fri Mar 27 22:05:28 2015
  InstallationDate: Installed on 2013-12-26 (455 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  MachineType: ASUS All Series
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-10-generic.efi.signed 
root=UUID=31dc4488-28d4-4d2a-aa51-6733e237d5f8 ro quiet splash vt.handoff=7
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/18/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2103
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z87-PRO
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2103:bd08/18/2014:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ87-PRO:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: All Series
  dmi.product.version: System Version
  dmi.sys.vendor: ASUS

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1437492/+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 1470250] Re: [Hyper-V] Ubuntu 14.04.2 LTS Generation 2 SCSI Errors on VSS Based Backups

2016-03-31 Thread Joseph Salisbury

I actually just tested the 3.13.0-35 kernel and not -32.  It DID exhibit
the bug.  I'll next test the 3.13.0-26 kernel.  Current results are:

3.13.0-16 - GOOD
3.13.0-17 - GOOD
3.13.0-26 - TESTING NEXT
3.13.0-35 - BAD
3.13.0-49 - BAD

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

Title:
  [Hyper-V] Ubuntu 14.04.2 LTS Generation 2 SCSI Errors on VSS Based
  Backups

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Trusty:
  In Progress
Status in linux source package in Vivid:
  In Progress
Status in linux source package in Wily:
  In Progress

Bug description:
  Customers have reported running various versions of Ubuntu 14.04.2 LTS
  on Generation 2 Hyper-V Hosts.On a random Basis, the file system
  will be mounted Read-Only due to a "disk error" (which really isn't
  the case here).As a result, they must reboot the Ubuntu guest to
  get the file system to mount RW again.

  The Error seen are the following:
  Apr 30 00:02:01 balticnetworkstraining kernel: [640153.968142] storvsc: Sense 
Key : Unit Attention [current] 
  Apr 30 00:02:01 balticnetworkstraining kernel: [640153.968145] storvsc: Add. 
Sense: Changed operating definition
  Apr 30 00:02:01 balticnetworkstraining kernel: [640153.968161] sd 0:0:0:0: 
Warning! Received an indication that the operating parameters on this target 
have changed. The Linux SCSI layer does not automatically adjust these 
parameters.
  Apr 30 01:23:26 balticnetworkstraining kernel: [645039.584164] hv_storvsc 
vmbus_0_4: cmd 0x2a scsi status 0x2 srb status 0x82
  Apr 30 01:23:26 balticnetworkstraining kernel: [645039.584178] hv_storvsc 
vmbus_0_4: stor pkt 88006eb6c700 autosense data valid - len 18
  Apr 30 01:23:26 balticnetworkstraining kernel: [645039.584180] storvsc: Sense 
Key : Unit Attention [current] 
  Apr 30 01:23:26 balticnetworkstraining kernel: [645039.584183] storvsc: Add. 
Sense: Changed operating definition
  Apr 30 01:23:26 balticnetworkstraining kernel: [645039.584198] sd 0:0:0:0: 
Warning! Received an indication that the operating parameters on this target 
have changed.  The Linux SCSI layer does not automatically adjust these 
parameters.

  This relates to the VSS "Windows Server Backup" process that kicks off at 
midnight on the host and finishes an hour and half later.   
  Yes, we do have hv_vss_daemon and hv_kvp_daemon running for the correct 
kernel version we have.   We're currently running kernel version 
3.13.0-49-generic #83 on one system and 3.16.0-34-generic #37 on the other. -- 
We see the same errors on both.
  As a result, we've been hesitant to drop any more ubuntu guests on our 2012R2 
hyper-v system because of this.   We can stop the backup process and all is 
good, but we need nightly backups to image all of our VM's.   All the windows 
guests have no issues of course.   We also have some CentOS based guests 
running without issues from what we've seen.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1470250/+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 1558905] Re: linux-lts-vivid: 3.19.0-58.64~14.04.1 -proposed tracker

** Changed in: kernel-sru-workflow/promote-to-security
   Status: New => Confirmed

** Changed in: kernel-sru-workflow/promote-to-updates
   Status: New => Confirmed

** Description changed:

  This bug is for tracking the 3.19.0-58.64~14.04.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
  kernel-stable-Prepare-package-start:Friday, 18. March 2016 04:01 UTC
  kernel-stable-master-bug:1558701
  -- swm properties --
  phase: Uploaded
  kernel-stable-Prepare-package-end:Wednesday, 23. March 2016 13:57 UTC
  kernel-stable-Promote-to-proposed-end:Wednesday, 23. March 2016 11:57 UTC
  kernel-stable-Promote-to-proposed-start:Wednesday, 23. March 2016 13:57 UTC
  kernel-stable-Verification-testing-start:Wednesday, 23. March 2016 14:03 UTC
  kernel-stable-Certification-testing-start:Wednesday, 23. March 2016 14:03 UTC
  kernel-stable-Security-signoff-start:Wednesday, 23. March 2016 14:03 UTC
  proposed-announcement-sent:True
  kernel-stable-Regression-testing-start:Wednesday, 23. March 2016 14:03 UTC
  kernel-stable-Security-signoff-end:Monday, 28. March 2016 19:01 UTC
- kernel-stable-phase:Testing
- kernel-stable-phase-changed:Tuesday, 29. March 2016 15:01 UTC
  kernel-stable-Verification-testing-end:Tuesday, 29. March 2016 15:01 UTC
  kernel-stable-Regression-testing-end:Tuesday, 29. March 2016 15:01 UTC
  kernel-stable-Certification-testing-end:Thursday, 31. March 2016 16:01 UTC
+ kernel-stable-phase:CopyToUpdates
+ kernel-stable-phase-changed:Thursday, 31. March 2016 20:57 UTC
+ kernel-stable-Promote-to-updates-start:Thursday, 31. March 2016 20:57 UTC

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

Title:
  linux-lts-vivid: 3.19.0-58.64~14.04.1 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Fix Released
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  Confirmed
Status in Kernel SRU Workflow promote-to-updates series:
  Confirmed
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux-lts-vivid package in Ubuntu:
  Invalid
Status in linux-lts-vivid source package in Trusty:
  New

Bug description:
  This bug is for tracking the 3.19.0-58.64~14.04.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
  kernel-stable-Prepare-package-start:Friday, 18. March 2016 04:01 UTC
  kernel-stable-master-bug:1558701
  -- swm properties --
  phase: Uploaded
  kernel-stable-Prepare-package-end:Wednesday, 23. March 2016 13:57 UTC
  kernel-stable-Promote-to-proposed-end:Wednesday, 23. March 2016 11:57 UTC
  kernel-stable-Promote-to-proposed-start:Wednesday, 23. March 2016 13:57 UTC
  kernel-stable-Verification-testing-start:Wednesday, 23. March 2016 14:03 UTC
  kernel-stable-Certification-testing-start:Wednesday, 23. March 2016 14:03 UTC
  kernel-stable-Security-signoff-start:Wednesday, 23. March 2016 14:03 UTC
  proposed-announcement-sent:True
  kernel-stable-Regression-testing-start:Wednesday, 23. March 2016 14:03 UTC
  kernel-stable-Security-signoff-end:Monday, 28. March 2016 19:01 UTC
  kernel-stable-Verification-testing-end:Tuesday, 29. March 2016 15:01 UTC
  kernel-stable-Regression-testing-end:Tuesday, 29. March 2016 15:01 UTC
  kernel-stable-Certification-testing-end:Thursday, 31. March 2016 16:01 UTC
  kernel-stable-phase:CopyToUpdates
  kernel-stable-phase-changed:Thursday, 31. March 2016 20:57 UTC
  kernel-stable-Promote-to-updates-start:Thursday, 31. March 2016 20:57 UTC

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1558905/+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 1558701] Re: linux: 3.19.0-58.64 -proposed tracker

** Changed in: kernel-sru-workflow/certification-testing
   Status: In Progress => Invalid

** Changed in: kernel-sru-workflow/promote-to-security
   Status: New => Confirmed

** Changed in: kernel-sru-workflow/promote-to-updates
   Status: New => Confirmed

** Description changed:

  This bug is for tracking the 3.19.0-58.64 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
  kernel-stable-Prepare-package-start:Thursday, 17. March 2016 17:37 UTC
  kernel-stable-Promote-to-proposed-end:Thursday, 17. March 2016 18:02 UTC
  kernel-stable-Prepare-package-end:Friday, 18. March 2016 04:03 UTC
  kernel-stable-Promote-to-proposed-start:Friday, 18. March 2016 04:03 UTC
  kernel-stable-Verification-testing-start:Friday, 18. March 2016 13:01 UTC
  kernel-stable-Certification-testing-start:Friday, 18. March 2016 13:01 UTC
  kernel-stable-Security-signoff-start:Friday, 18. March 2016 13:01 UTC
  proposed-announcement-sent:True
  kernel-stable-Regression-testing-start:Friday, 18. March 2016 13:01 UTC
  kernel-stable-Security-signoff-end:Saturday, 19. March 2016 14:41 UTC
  kernel-stable-Regression-testing-end:Monday, 28. March 2016 15:02 UTC
- kernel-stable-phase:Testing
- kernel-stable-phase-changed:Tuesday, 29. March 2016 15:01 UTC
  kernel-stable-Verification-testing-end:Tuesday, 29. March 2016 15:01 UTC
+ kernel-stable-phase:CopyToUpdates
+ kernel-stable-Promote-to-updates-start:Thursday, 31. March 2016 20:56 UTC
+ kernel-stable-phase-changed:Thursday, 31. March 2016 20:56 UTC
+ kernel-stable-Certification-testing-end:Thursday, 31. March 2016 20:56 UTC

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

Title:
  linux: 3.19.0-58.64 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  Confirmed
Status in Kernel SRU Workflow promote-to-updates series:
  Confirmed
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Vivid:
  New

Bug description:
  This bug is for tracking the 3.19.0-58.64 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
  kernel-stable-Prepare-package-start:Thursday, 17. March 2016 17:37 UTC
  kernel-stable-Promote-to-proposed-end:Thursday, 17. March 2016 18:02 UTC
  kernel-stable-Prepare-package-end:Friday, 18. March 2016 04:03 UTC
  kernel-stable-Promote-to-proposed-start:Friday, 18. March 2016 04:03 UTC
  kernel-stable-Verification-testing-start:Friday, 18. March 2016 13:01 UTC
  kernel-stable-Certification-testing-start:Friday, 18. March 2016 13:01 UTC
  kernel-stable-Security-signoff-start:Friday, 18. March 2016 13:01 UTC
  proposed-announcement-sent:True
  kernel-stable-Regression-testing-start:Friday, 18. March 2016 13:01 UTC
  kernel-stable-Security-signoff-end:Saturday, 19. March 2016 14:41 UTC
  kernel-stable-Regression-testing-end:Monday, 28. March 2016 15:02 UTC
  kernel-stable-Verification-testing-end:Tuesday, 29. March 2016 15:01 UTC
  kernel-stable-phase:CopyToUpdates
  kernel-stable-Promote-to-updates-start:Thursday, 31. March 2016 20:56 UTC
  kernel-stable-phase-changed:Thursday, 31. March 2016 20:56 UTC
  kernel-stable-Certification-testing-end:Thursday, 31. March 2016 20:56 UTC

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1558701/+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 1557706] Re: linux: 4.2.0-35.40 -proposed tracker

** Changed in: kernel-sru-workflow/certification-testing
   Status: In Progress => Invalid

** Changed in: kernel-sru-workflow/promote-to-security
   Status: New => Confirmed

** Changed in: kernel-sru-workflow/promote-to-updates
   Status: New => Confirmed

** Description changed:

  This bug is for tracking the 4.2.0-35.40 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
  kernel-stable-Prepare-package-start:Tuesday, 15. March 2016 18:45 UTC
  kernel-stable-Promote-to-proposed-end:Tuesday, 15. March 2016 20:01 UTC
  kernel-stable-Prepare-package-end:Wednesday, 16. March 2016 06:04 UTC
  kernel-stable-Promote-to-proposed-start:Wednesday, 16. March 2016 06:04 UTC
  kernel-stable-Verification-testing-start:Wednesday, 16. March 2016 15:01 UTC
  kernel-stable-Certification-testing-start:Wednesday, 16. March 2016 15:01 UTC
  kernel-stable-Security-signoff-start:Wednesday, 16. March 2016 15:01 UTC
  proposed-announcement-sent:True
  kernel-stable-Regression-testing-start:Wednesday, 16. March 2016 15:01 UTC
  kernel-stable-Security-signoff-end:Friday, 18. March 2016 07:00 UTC
- kernel-stable-phase:Testing
- kernel-stable-phase-changed:Monday, 28. March 2016 15:02 UTC
  kernel-stable-Verification-testing-end:Monday, 28. March 2016 15:02 UTC
  kernel-stable-Regression-testing-end:Monday, 28. March 2016 15:02 UTC
+ kernel-stable-phase:CopyToUpdates
+ kernel-stable-Promote-to-updates-start:Thursday, 31. March 2016 20:54 UTC
+ kernel-stable-phase-changed:Thursday, 31. March 2016 20:54 UTC
+ kernel-stable-Certification-testing-end:Thursday, 31. March 2016 20:54 UTC

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

Title:
  linux: 4.2.0-35.40 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  Confirmed
Status in Kernel SRU Workflow promote-to-updates series:
  Confirmed
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Wily:
  New

Bug description:
  This bug is for tracking the 4.2.0-35.40 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
  kernel-stable-Prepare-package-start:Tuesday, 15. March 2016 18:45 UTC
  kernel-stable-Promote-to-proposed-end:Tuesday, 15. March 2016 20:01 UTC
  kernel-stable-Prepare-package-end:Wednesday, 16. March 2016 06:04 UTC
  kernel-stable-Promote-to-proposed-start:Wednesday, 16. March 2016 06:04 UTC
  kernel-stable-Verification-testing-start:Wednesday, 16. March 2016 15:01 UTC
  kernel-stable-Certification-testing-start:Wednesday, 16. March 2016 15:01 UTC
  kernel-stable-Security-signoff-start:Wednesday, 16. March 2016 15:01 UTC
  proposed-announcement-sent:True
  kernel-stable-Regression-testing-start:Wednesday, 16. March 2016 15:01 UTC
  kernel-stable-Security-signoff-end:Friday, 18. March 2016 07:00 UTC
  kernel-stable-Verification-testing-end:Monday, 28. March 2016 15:02 UTC
  kernel-stable-Regression-testing-end:Monday, 28. March 2016 15:02 UTC
  kernel-stable-phase:CopyToUpdates
  kernel-stable-Promote-to-updates-start:Thursday, 31. March 2016 20:54 UTC
  kernel-stable-phase-changed:Thursday, 31. March 2016 20:54 UTC
  kernel-stable-Certification-testing-end:Thursday, 31. March 2016 20:54 UTC

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1557706/+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 1563441] Re: linux: 4.4.0-17.33 -proposed tracker

Here's the relevant information:

xenial linux 4.4.0-17.33 REGR summary

Please verify test results in http://people.canonical.com/~kernel/status
/adt-matrix/overall.txt


** Changed in: kernel-development-workflow/automated-testing
   Status: New => Confirmed

** Description changed:

  This bug is for tracking the 4.4.0-17.33 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
  kernel-Prepare-package-start:Tuesday, 29. March 2016 16:41 UTC
  kernel-phase-changed:Tuesday, 29. March 2016 16:41 UTC
  kernel-phase:Prepare
  kernel-stable-Promote-to-proposed-end:Thursday, 31. March 2016 19:01 UTC
+ proposed-announcement-sent:True

** Changed in: kernel-development-workflow/automated-testing
   Status: Confirmed => Incomplete

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

Title:
  linux: 4.4.0-17.33 -proposed tracker

Status in Kernel Development Workflow:
  In Progress
Status in Kernel Development Workflow automated-testing series:
  Incomplete
Status in Kernel Development Workflow prepare-package series:
  Fix Released
Status in Kernel Development Workflow prepare-package-meta series:
  Fix Released
Status in Kernel Development Workflow prepare-package-signed series:
  Fix Released
Status in Kernel Development Workflow promote-to-proposed series:
  Fix Released
Status in Kernel Development Workflow promote-to-release series:
  New
Status in Kernel Development Workflow regression-testing series:
  New
Status in linux package in Ubuntu:
  New
Status in linux source package in Xenial:
  New

Bug description:
  This bug is for tracking the 4.4.0-17.33 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
  kernel-Prepare-package-start:Tuesday, 29. March 2016 16:41 UTC
  kernel-phase-changed:Tuesday, 29. March 2016 16:41 UTC
  kernel-phase:Prepare
  kernel-stable-Promote-to-proposed-end:Thursday, 31. March 2016 19:01 UTC
  proposed-announcement-sent:True

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-development-workflow/+bug/1563441/+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 1564470] Re: Unable to install NI-VISA nikal kernel module because of GPL-only symbol 'pgprot_writecombine'

What is interesting nikal.ko module builds and loads successfully without any 
manual patching on
* Ubuntu 14.04.1 LTS with linux-3.13.
* Ubuntu 12.04.5 LTS with linux-3.2.

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

Title:
  Unable to install NI-VISA nikal kernel module because of GPL-only
  symbol 'pgprot_writecombine'

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Steps to reproduce:
  1. Login to National Instruments site
  2. Download NI-VISA 15.0 for linux (NI-VISA-15.0.0.iso).
  3. Launch its installation by "sudo ./INSTALL"
  4. Get errors on nikal kernel modules compilation about "pgprot_writecombine" 
symbol 
  (

  sudo /usr/local/natinst/nikal/bin/updateNIDrivers 
  Configuring NI-KAL for kernel version 4.4.0-16-generic...
  Building module nikal...
  <11>Mar 31 23:04:51 nikal:   CC [M]  
/var/lib/nikal/4.4.0-16-generic/nikal/nikal.o
  <11>Mar 31 23:04:51 nikal:   Building modules, stage 2.
  <11>Mar 31 23:04:51 nikal:   MODPOST 1 modules
  <11>Mar 31 23:04:51 nikal: FATAL: modpost: GPL-incompatible module nikal.ko 
uses GPL-only symbol 'pgprot_writecombine'
  <11>Mar 31 23:04:51 nikal: scripts/Makefile.modpost:91: recipe for target 
'__modpost' failed
  <11>Mar 31 23:04:51 nikal: make[2]: *** [__modpost] Error 1
  <11>Mar 31 23:04:51 nikal: Makefile:1399: recipe for target 'modules' failed
  <11>Mar 31 23:04:51 nikal: make[1]: *** [modules] Error 2
  <11>Mar 31 23:04:51 nikal: Makefile:32: recipe for target 'nikal.ko' failed
  <11>Mar 31 23:04:51 nikal: make: *** [nikal.ko] Error 2
  <11>Mar 31 23:04:51 nikal: ERROR:  failed to build nikal
  <11>Mar 31 23:04:51 nikal: ERROR:  NI-KAL update failed.
  <11>Mar 31 23:04:51 nikal: ERROR:  make of nikal kernel module failed, not 
installing kernel module.
  <11>Mar 31 23:04:51 nikal: ERROR:  updateNIDrivers should be called again 
after fixing the problem.
  <11>Mar 31 23:04:51 nikal: ERROR:  Logging failure...
  find: ‘/lib/modules/4.4.0-15-generic/kernel/natinst’: No such file or 
directory
  <11>Mar 31 23:04:51 nikal: ERROR:  Include the file 
/tmp/niSystemReport.out.gz when contacting
  <11>Mar 31 23:04:51 nikal: ERROR:  National Instruments for support.
  <11>Mar 31 23:04:51 nikal: ERROR: Update of National Instruments drivers 
failed.

  
  )

  Temporary solution:
  1. Edit /usr/src/linux-headers-4.4.0-16-generic/Module.symvers
  and change line
     0xd544e902 pgprot_writecombine vmlinux EXPORT_SYMBOL_GPL
  to
     0xd544e902 pgprot_writecombine vmlinux EXPORT_SYMBOL
  2. Edit /boot/abi-4.4.0-16-generic
  and change line
     EXPORT_SYMBOL_GPL vmlinux 0xd544e902   pgprot_writecombine
  to
     EXPORT_SYMBOL vmlinux 0xd544e902   pgprot_writecombine

  but it does not help - I get "nikal: Unknown symbol
  pgprot_writecombine (err 0)" in syslog.

  Expected results:
  0. The 'pgprot_writecombine' symbol is exported as EXPORT_SYMBOL
  1. Ubuntu can compile and load NI nikal module.

  Actual results:
  Unable to use NI-VISA under Ubuntu.

  Reference (openSUSE):
  
http://forums.ni.com/t5/Instrument-Control-GPIB-Serial/GPL-incompatible-module-nikal-ko/td-p/3218730

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-16-generic 4.4.0-16.32
  ProcVersionSignature: Ubuntu 4.4.0-16.32-generic 4.4.6
  Uname: Linux 4.4.0-16-generic i686
  ApportVersion: 2.20-0ubuntu3
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  flash  1549 F pulseaudio
   /dev/snd/controlC0:  flash  1549 F pulseaudio
  CurrentDesktop: Unity
  Date: Thu Mar 31 18:16:37 2016
  InstallationDate: Installed on 2016-03-26 (4 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Beta i386 (20160323)
  IwConfig:
   lono wireless extensions.

   enp1s0no wireless extensions.
  MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M.
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-16-generic 
root=UUID=eab7b488-5040-499c-afd8-21a7ce9e2383 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-16-generic N/A
   linux-backports-modules-4.4.0-16-generic  N/A
   linux-firmware1.157
  RfKill:

  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/09/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: FD
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: F2A55M-DS2
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias:

[Kernel-packages] [Bug 1564470] Re: Unable to install NI-VISA nikal kernel module because of GPL-only symbol 'pgprot_writecombine'

** Description changed:

  Steps to reproduce:
  1. Login to National Instruments site
  2. Download NI-VISA 15.0 for linux (NI-VISA-15.0.0.iso).
  3. Launch its installation by "sudo ./INSTALL"
- 4. Get errors on nikal kernel modules compilation about "pgprot_writecombine" 
symbol ("nikal: FATAL: modpost: GPL-incompatible module nikal.ko uses GPL-only 
symbol 'pgprot_writecombine'")
+ 4. Get errors on nikal kernel modules compilation about "pgprot_writecombine" 
symbol 
+ (
+ 
+ sudo /usr/local/natinst/nikal/bin/updateNIDrivers 
+ Configuring NI-KAL for kernel version 4.4.0-16-generic...
+ Building module nikal...
+ <11>Mar 31 23:04:51 nikal:   CC [M]  
/var/lib/nikal/4.4.0-16-generic/nikal/nikal.o
+ <11>Mar 31 23:04:51 nikal:   Building modules, stage 2.
+ <11>Mar 31 23:04:51 nikal:   MODPOST 1 modules
+ <11>Mar 31 23:04:51 nikal: FATAL: modpost: GPL-incompatible module nikal.ko 
uses GPL-only symbol 'pgprot_writecombine'
+ <11>Mar 31 23:04:51 nikal: scripts/Makefile.modpost:91: recipe for target 
'__modpost' failed
+ <11>Mar 31 23:04:51 nikal: make[2]: *** [__modpost] Error 1
+ <11>Mar 31 23:04:51 nikal: Makefile:1399: recipe for target 'modules' failed
+ <11>Mar 31 23:04:51 nikal: make[1]: *** [modules] Error 2
+ <11>Mar 31 23:04:51 nikal: Makefile:32: recipe for target 'nikal.ko' failed
+ <11>Mar 31 23:04:51 nikal: make: *** [nikal.ko] Error 2
+ <11>Mar 31 23:04:51 nikal: ERROR:  failed to build nikal
+ <11>Mar 31 23:04:51 nikal: ERROR:  NI-KAL update failed.
+ <11>Mar 31 23:04:51 nikal: ERROR:  make of nikal kernel module failed, not 
installing kernel module.
+ <11>Mar 31 23:04:51 nikal: ERROR:  updateNIDrivers should be called again 
after fixing the problem.
+ <11>Mar 31 23:04:51 nikal: ERROR:  Logging failure...
+ find: ‘/lib/modules/4.4.0-15-generic/kernel/natinst’: No such file or 
directory
+ <11>Mar 31 23:04:51 nikal: ERROR:  Include the file 
/tmp/niSystemReport.out.gz when contacting
+ <11>Mar 31 23:04:51 nikal: ERROR:  National Instruments for support.
+ <11>Mar 31 23:04:51 nikal: ERROR: Update of National Instruments drivers 
failed.
+ 
+ 
+ )
  
  Temporary solution:
  1. Edit /usr/src/linux-headers-4.4.0-16-generic/Module.symvers
  and change line
-0xd544e902 pgprot_writecombine vmlinux EXPORT_SYMBOL_GPL
+    0xd544e902 pgprot_writecombine vmlinux EXPORT_SYMBOL_GPL
  to
-0xd544e902 pgprot_writecombine vmlinux EXPORT_SYMBOL
+    0xd544e902 pgprot_writecombine vmlinux EXPORT_SYMBOL
  2. Edit /boot/abi-4.4.0-16-generic
- and change line 
-EXPORT_SYMBOL_GPL vmlinux 0xd544e902   pgprot_writecombine
+ and change line
+    EXPORT_SYMBOL_GPL vmlinux 0xd544e902   pgprot_writecombine
  to
-EXPORT_SYMBOL vmlinux 0xd544e902   pgprot_writecombine
+    EXPORT_SYMBOL vmlinux 0xd544e902   pgprot_writecombine
  
  but it does not help - I get "nikal: Unknown symbol pgprot_writecombine
  (err 0)" in syslog.
  
  Expected results:
  0. The 'pgprot_writecombine' symbol is exported as EXPORT_SYMBOL
  1. Ubuntu can compile and load NI nikal module.
  
  Actual results:
  Unable to use NI-VISA under Ubuntu.
  
  Reference (openSUSE):
  
http://forums.ni.com/t5/Instrument-Control-GPIB-Serial/GPL-incompatible-module-nikal-ko/td-p/3218730
  
  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-16-generic 4.4.0-16.32
  ProcVersionSignature: Ubuntu 4.4.0-16.32-generic 4.4.6
  Uname: Linux 4.4.0-16-generic i686
  ApportVersion: 2.20-0ubuntu3
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  flash  1549 F pulseaudio
   /dev/snd/controlC0:  flash  1549 F pulseaudio
  CurrentDesktop: Unity
  Date: Thu Mar 31 18:16:37 2016
  InstallationDate: Installed on 2016-03-26 (4 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Beta i386 (20160323)
  IwConfig:
   lono wireless extensions.
  
   enp1s0no wireless extensions.
  MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M.
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-16-generic 
root=UUID=eab7b488-5040-499c-afd8-21a7ce9e2383 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-16-generic N/A
   linux-backports-modules-4.4.0-16-generic  N/A
   linux-firmware1.157
  RfKill:
  
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/09/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: FD
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: F2A55M-DS2
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias:

[Kernel-packages] [Bug 1564470] Re: Unable to install NI-VISA nikal kernel module because of GPL-only symbol 'pgprot_writecombine'

** Tags removed: trusty

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

Title:
  Unable to install NI-VISA nikal kernel module because of GPL-only
  symbol 'pgprot_writecombine'

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Steps to reproduce:
  1. Login to National Instruments site
  2. Download NI-VISA 15.0 for linux (NI-VISA-15.0.0.iso).
  3. Launch its installation by "sudo ./INSTALL"
  4. Get errors on nikal kernel modules compilation about "pgprot_writecombine" 
symbol ("nikal: FATAL: modpost: GPL-incompatible module nikal.ko uses GPL-only 
symbol 'pgprot_writecombine'")

  Temporary solution:
  1. Edit /usr/src/linux-headers-4.4.0-16-generic/Module.symvers
  and change line
 0xd544e902 pgprot_writecombine vmlinux EXPORT_SYMBOL_GPL
  to
 0xd544e902 pgprot_writecombine vmlinux EXPORT_SYMBOL
  2. Edit /boot/abi-4.4.0-16-generic
  and change line 
 EXPORT_SYMBOL_GPL vmlinux 0xd544e902   pgprot_writecombine
  to
 EXPORT_SYMBOL vmlinux 0xd544e902   pgprot_writecombine

  but it does not help - I get "nikal: Unknown symbol
  pgprot_writecombine (err 0)" in syslog.

  Expected results:
  0. The 'pgprot_writecombine' symbol is exported as EXPORT_SYMBOL
  1. Ubuntu can compile and load NI nikal module.

  Actual results:
  Unable to use NI-VISA under Ubuntu.

  Reference (openSUSE):
  
http://forums.ni.com/t5/Instrument-Control-GPIB-Serial/GPL-incompatible-module-nikal-ko/td-p/3218730

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-16-generic 4.4.0-16.32
  ProcVersionSignature: Ubuntu 4.4.0-16.32-generic 4.4.6
  Uname: Linux 4.4.0-16-generic i686
  ApportVersion: 2.20-0ubuntu3
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  flash  1549 F pulseaudio
   /dev/snd/controlC0:  flash  1549 F pulseaudio
  CurrentDesktop: Unity
  Date: Thu Mar 31 18:16:37 2016
  InstallationDate: Installed on 2016-03-26 (4 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Beta i386 (20160323)
  IwConfig:
   lono wireless extensions.

   enp1s0no wireless extensions.
  MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M.
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-16-generic 
root=UUID=eab7b488-5040-499c-afd8-21a7ce9e2383 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-16-generic N/A
   linux-backports-modules-4.4.0-16-generic  N/A
   linux-firmware1.157
  RfKill:

  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/09/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: FD
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: F2A55M-DS2
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrFD:bd01/09/2014:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnF2A55M-DS2:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To be filled by O.E.M.
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1564470/+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 1564591] Re: Sync kernel zfs and spl to version 0.6.5.6 - align with zfsutils-linux and spl packages

2016-03-31 Thread Colin Ian King

** Description changed:

  We need to sync with zfs 0.6.5.6-0ubuntu3 to pick up a couple of minor
  fixes:
  
  Add support 32 bit FS_IOC32_{GET|SET}FLAGS compat ioctls (for powerpc64 big 
endian mode)
- Fix aarch64 compilation, missing hrtime_t and timestruc_t types
+ Fix aarch64 compilation, missing hrtime_t and timestruct_t types

** Summary changed:

- Sync kernel zfs and spl to version 0.6.5.6 - align with zfsutils-linux and 
spl packages
+ Sync kernel zfs 0.6.5.6 - align with zfsutils-linux and spl packages

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

Title:
  Sync kernel zfs 0.6.5.6 - align with zfsutils-linux and spl packages

Status in linux package in Ubuntu:
  In Progress

Bug description:
  We need to sync with zfs 0.6.5.6-0ubuntu3 to pick up a couple of minor
  fixes:

  Add support 32 bit FS_IOC32_{GET|SET}FLAGS compat ioctls (for powerpc64 big 
endian mode)
  Fix aarch64 compilation, missing hrtime_t and timestruct_t types

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1564591/+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 1562230] Re: [Hewlett-Packard HP ENVY 17 Notebook PC] hibernate/resume failure

2016-03-31 Thread Kesantielu

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

Title:
  [Hewlett-Packard HP ENVY 17 Notebook PC] hibernate/resume failure

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Notebook cannot resume from hibernation.

  ProblemType: KernelOops
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-15-generic 4.4.0-15.31
  ProcVersionSignature: Ubuntu 4.4.0-15.31-generic 4.4.6
  Uname: Linux 4.4.0-15-generic x86_64
  Annotation: This occurred during a previous hibernation, and prevented the 
system from resuming properly.
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  zh 2098 F pulseaudio
   /dev/snd/controlC0:  zh 2098 F pulseaudio
  Date: Sat Mar 26 07:41:25 2016
  DuplicateSignature: hibernate/resume:Hewlett-Packard HP ENVY 17 Notebook 
PC:F.65
  ExecutablePath: /usr/share/apport/apportcheckresume
  Failure: hibernate/resume
  HibernationDevice: RESUME=UUID=378e2e05-278e-45c4-a558-68a1e8b83eab
  InterpreterPath: /usr/bin/python3.5
  MachineType: Hewlett-Packard HP ENVY 17 Notebook PC
  ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-15-generic.efi.signed 
root=UUID=c8951135-cb49-43fc-b142-4b426e3a988b ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-15-generic N/A
   linux-backports-modules-4.4.0-15-generic  N/A
   linux-firmware1.157
  SourcePackage: linux
  Title: [Hewlett-Packard HP ENVY 17 Notebook PC] hibernate/resume failure
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  dmi.bios.date: 11/20/2014
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.65
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 1966
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 93.52
  dmi.chassis.asset.tag: 5CG3456NSY
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.65:bd11/20/2014:svnHewlett-Packard:pnHPENVY17NotebookPC:pvr088510305B0610100:rvnHewlett-Packard:rn1966:rvrKBCVersion93.52:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.name: HP ENVY 17 Notebook PC
  dmi.product.version: 088510305B0610100
  dmi.sys.vendor: Hewlett-Packard

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1562230/+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 1564591] [NEW] Sync kernel zfs and spl to version 0.6.5.6 - align with zfsutils-linux and spl packages

2016-03-31 Thread Colin Ian King

Public bug reported:

We need to sync with zfs 0.6.5.6-0ubuntu3 to pick up a couple of minor
fixes:

Add support 32 bit FS_IOC32_{GET|SET}FLAGS compat ioctls (for powerpc64 big 
endian mode)
Fix aarch64 compilation, missing hrtime_t and timestruct_t types

** Affects: linux (Ubuntu)
 Importance: Medium
 Assignee: Colin Ian King (colin-king)
 Status: In Progress

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

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

** Changed in: linux (Ubuntu)
 Assignee: (unassigned) => Colin Ian King (colin-king)

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

Title:
  Sync kernel zfs and spl to version 0.6.5.6 - align with zfsutils-linux
  and spl packages

Status in linux package in Ubuntu:
  In Progress

Bug description:
  We need to sync with zfs 0.6.5.6-0ubuntu3 to pick up a couple of minor
  fixes:

  Add support 32 bit FS_IOC32_{GET|SET}FLAGS compat ioctls (for powerpc64 big 
endian mode)
  Fix aarch64 compilation, missing hrtime_t and timestruct_t types

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1564591/+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 1564470] Re: Unable to install NI-VISA nikal kernel module because of GPL-only symbol 'pgprot_writecombine'

** Tags added: trusty

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

Title:
  Unable to install NI-VISA nikal kernel module because of GPL-only
  symbol 'pgprot_writecombine'

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Steps to reproduce:
  1. Login to National Instruments site
  2. Download NI-VISA 15.0 for linux (NI-VISA-15.0.0.iso).
  3. Launch its installation by "sudo ./INSTALL"
  4. Get errors on nikal kernel modules compilation about "pgprot_writecombine" 
symbol ("nikal: FATAL: modpost: GPL-incompatible module nikal.ko uses GPL-only 
symbol 'pgprot_writecombine'")

  Temporary solution:
  1. Edit /usr/src/linux-headers-4.4.0-16-generic/Module.symvers
  and change line
 0xd544e902 pgprot_writecombine vmlinux EXPORT_SYMBOL_GPL
  to
 0xd544e902 pgprot_writecombine vmlinux EXPORT_SYMBOL
  2. Edit /boot/abi-4.4.0-16-generic
  and change line 
 EXPORT_SYMBOL_GPL vmlinux 0xd544e902   pgprot_writecombine
  to
 EXPORT_SYMBOL vmlinux 0xd544e902   pgprot_writecombine

  but it does not help - I get "nikal: Unknown symbol
  pgprot_writecombine (err 0)" in syslog.

  Expected results:
  0. The 'pgprot_writecombine' symbol is exported as EXPORT_SYMBOL
  1. Ubuntu can compile and load NI nikal module.

  Actual results:
  Unable to use NI-VISA under Ubuntu.

  Reference (openSUSE):
  
http://forums.ni.com/t5/Instrument-Control-GPIB-Serial/GPL-incompatible-module-nikal-ko/td-p/3218730

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-16-generic 4.4.0-16.32
  ProcVersionSignature: Ubuntu 4.4.0-16.32-generic 4.4.6
  Uname: Linux 4.4.0-16-generic i686
  ApportVersion: 2.20-0ubuntu3
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  flash  1549 F pulseaudio
   /dev/snd/controlC0:  flash  1549 F pulseaudio
  CurrentDesktop: Unity
  Date: Thu Mar 31 18:16:37 2016
  InstallationDate: Installed on 2016-03-26 (4 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Beta i386 (20160323)
  IwConfig:
   lono wireless extensions.

   enp1s0no wireless extensions.
  MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M.
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-16-generic 
root=UUID=eab7b488-5040-499c-afd8-21a7ce9e2383 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-16-generic N/A
   linux-backports-modules-4.4.0-16-generic  N/A
   linux-firmware1.157
  RfKill:

  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/09/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: FD
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: F2A55M-DS2
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrFD:bd01/09/2014:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnF2A55M-DS2:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To be filled by O.E.M.
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1564470/+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 1438510] Re: [REGRESSION] bluetooth headset no longer supports a2dp

2016-03-31 Thread Horacio Arroyo

Just applied to a fresh 16.04 beta 2 install, despite having to create
/etc/bluetooth/audio.conf manually, it worked again for me.

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

Title:
  [REGRESSION] bluetooth headset no longer supports a2dp

Status in bluez package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed
Status in bluez source package in Vivid:
  Confirmed
Status in pulseaudio source package in Vivid:
  Confirmed

Bug description:
  Just installed 15.04 fresh from the latest ISO (beta2).

  I'm bummed to see my bluetooth headset (Bose Soundlink overear) seems
  to have regressed in functionality.

  In 14.10, I was able to set the output profile either to a2dp or
  hsp/hfp (telephony duplex).

  In 15.04, it only works in telephony duplex mode.  I can't get high
  fidelity sound playback to work at all.

  This thread seems to be related, though the workaround within did not solve 
the problem for me:
  https://bbs.archlinux.org/viewtopic.php?id=194006

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1438510/+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 1553427] Re: [LENOVO S10-3] suspend/resume failure

2016-03-31 Thread Jonathan Duff

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

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

Title:
  [LENOVO S10-3] suspend/resume failure

Status in linux package in Ubuntu:
  Triaged

Bug description:
  - goes to sleep and netbook indicator light flashes.
  - touch keyboard or mouse and it starts to resume.
  - goes to black screen with all indicator light but hard drive light on
  - hard drive light flashes once.
  - caps lock fails to light up and toggle
  conclusion:
  goes to a black screen and fails to resume.
  unresponsive in switching to virtual terminals or toggling caps lock light.

  ProblemType: KernelOops
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-9-generic 4.4.0-9.24
  ProcVersionSignature: Ubuntu 4.4.0-9.24-generic 4.4.3
  Uname: Linux 4.4.0-9-generic x86_64
  Annotation: This occurred during a previous suspend, and prevented the system 
from resuming properly.
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  user   1660 F pulseaudio
  Date: Fri Mar  4 16:38:43 2016
  DuplicateSignature: suspend/resume:LENOVO S10-3:2ACN23WW
  ExecutablePath: /usr/share/apport/apportcheckresume
  Failure: suspend/resume
  HibernationDevice: RESUME=UUID=3cd1818a-c595-48c2-9604-a4c99101405f
  InstallationDate: Installed on 2016-02-27 (7 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  InterpreterPath: /usr/bin/python3.5
  MachineType: LENOVO S10-3
  ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume
  ProcEnviron:
   PATH=(custom, no user)
   LANG=en_US.UTF-8
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-9-generic 
root=UUID=bc2bf6a8-2064-486f-beeb-bcd366e8ba2f ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-9-generic N/A
   linux-backports-modules-4.4.0-9-generic  N/A
   linux-firmware   1.156
  SourcePackage: linux
  Title: [LENOVO S10-3] suspend/resume failure
  UpgradeStatus: Upgraded to xenial on 2016-02-28 (5 days ago)
  UserGroups:
   
  dmi.bios.date: 03/12/2010
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 2ACN23WW
  dmi.board.name: Mariana3A
  dmi.board.vendor: Lenovo
  dmi.board.version: Rev 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Lenovo
  dmi.chassis.version: Rev 1.0
  dmi.modalias: 
dmi:bvnLENOVO:bvr2ACN23WW:bd03/12/2010:svnLENOVO:pnS10-3:pvrLenovo:rvnLenovo:rnMariana3A:rvrRev1.0:cvnLenovo:ct10:cvrRev1.0:
  dmi.product.name: S10-3
  dmi.product.version: Lenovo
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1553427/+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 1563441] Re: linux: 4.4.0-17.33 -proposed tracker

** Description changed:

  This bug is for tracking the 4.4.0-17.33 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
  kernel-Prepare-package-start:Tuesday, 29. March 2016 16:41 UTC
  kernel-phase-changed:Tuesday, 29. March 2016 16:41 UTC
  kernel-phase:Prepare
+ kernel-stable-Promote-to-proposed-end:Thursday, 31. March 2016 19:01 UTC

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

Title:
  linux: 4.4.0-17.33 -proposed tracker

Status in Kernel Development Workflow:
  In Progress
Status in Kernel Development Workflow automated-testing series:
  New
Status in Kernel Development Workflow prepare-package series:
  Fix Released
Status in Kernel Development Workflow prepare-package-meta series:
  Fix Released
Status in Kernel Development Workflow prepare-package-signed series:
  Fix Released
Status in Kernel Development Workflow promote-to-proposed series:
  Fix Released
Status in Kernel Development Workflow promote-to-release series:
  New
Status in Kernel Development Workflow regression-testing series:
  New
Status in linux package in Ubuntu:
  New
Status in linux source package in Xenial:
  New

Bug description:
  This bug is for tracking the 4.4.0-17.33 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
  kernel-Prepare-package-start:Tuesday, 29. March 2016 16:41 UTC
  kernel-phase-changed:Tuesday, 29. March 2016 16:41 UTC
  kernel-phase:Prepare
  kernel-stable-Promote-to-proposed-end:Thursday, 31. March 2016 19:01 UTC

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-development-workflow/+bug/1563441/+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 1540430] Re: Touchpad not working after suspend/resume

7.

sudo su
echo platform > /sys/power/pm_test
exit

sudo sh -c "sync && echo 1 > /sys/power/pm_trace && pm-suspend"

dmesg > dmesg.txt


** Attachment added: "dmesg.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1540430/+attachment/4618632/+files/dmesg.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/1540430

Title:
  Touchpad not working after suspend/resume

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Touchpad not working after suspend/resume on Asus X302LA.

  I have tried both workarounds in bug  #1393079 to no success.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.19.0-47-generic 3.19.0-47.53~14.04.1
  ProcVersionSignature: Ubuntu 3.19.0-47.53~14.04.1-generic 3.19.8-ckt10
  Uname: Linux 3.19.0-47-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  Date: Mon Feb  1 16:26:19 2016
  InstallationDate: Installed on 2016-01-31 (0 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  SourcePackage: linux-lts-vivid
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  uros   2656 F pulseaudio
   /dev/snd/controlC0:  uros   2656 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=d2fb9926-f37b-400c-8fae-366846852756
  InstallationDate: Installed on 2016-01-31 (52 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  Lsusb:
   Bus 003 Device 002: ID 8087:8001 Intel Corp. 
   Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 04f2:b483 Chicony Electronics Co., Ltd 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. X302LA
  NonfreeKernelModules: wl
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-56-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.19.0-56.62~14.04.1-generic 3.19.8-ckt15
  RelatedPackageVersions:
   linux-restricted-modules-3.19.0-56-generic N/A
   linux-backports-modules-3.19.0-56-generic  N/A
   linux-firmware 1.127.20
  Tags:  trusty
  Uname: Linux 3.19.0-56-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 08/24/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X302LA.204
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X302LA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrX302LA.204:bd08/24/2015:svnASUSTeKCOMPUTERINC.:pnX302LA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX302LA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: X302LA
  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/1540430/+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 1539843] Re: External microphone does not work

2016-03-31 Thread Alexandr

Solved this problem:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1564252

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

Title:
  External microphone does not work

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Asus N551JM
  In this laptop is combined jack for microphone and headphone. I use headset 
A4Tech Bloody G500 that nice work in Windows. But in KUBUNTU 15.10 and ubuntu 
14.04/15.10 they do not work (work only as headphone). System don't see that i 
connected headset and in pavucontrol i see only embeded in laptop microphone.
  http://www.alsa-project.org/db/?f=bcf71e457acf21a40799621a85a53e5817f829f9
  --- 
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  mogost 1348 F pulseaudio
   /dev/snd/controlC1:  mogost 1348 F pulseaudio
  DistroRelease: Ubuntu 15.10
  HibernationDevice: RESUME=UUID=d1115de1-e4fd-4119-8d26-79091505b000
  InstallationDate: Installed on 2016-01-30 (0 days ago)
  InstallationMedia: Kubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  MachineType: ASUSTeK COMPUTER INC. N551JM
  NonfreeKernelModules: nvidia
  Package: linux (not installed)
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_EN.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-25-generic.efi.signed 
root=UUID=b7b85f18-8c88-4443-8a59-2b3a93642c97 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.2.0-25.30-generic 4.2.6
  RelatedPackageVersions:
   linux-restricted-modules-4.2.0-25-generic N/A
   linux-backports-modules-4.2.0-25-generic  N/A
   linux-firmware1.149.3
  Tags:  wily
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  Uname: Linux 4.2.0-25-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/06/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: N551JM.204
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: N551JM
  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.:bvrN551JM.204:bd10/06/2014:svnASUSTeKCOMPUTERINC.:pnN551JM:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnN551JM:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: N551JM
  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/1539843/+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 1540430] Re: Touchpad not working after suspend/resume

10.

sudo su
echo none > /sys/power/pm_test
exit

sudo sh -c "sync && echo 1 > /sys/power/pm_trace && pm-suspend"

dmesg > dmesg.txt

** Attachment added: "dmesg.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1540430/+attachment/4618635/+files/dmesg.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/1540430

Title:
  Touchpad not working after suspend/resume

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Touchpad not working after suspend/resume on Asus X302LA.

  I have tried both workarounds in bug  #1393079 to no success.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.19.0-47-generic 3.19.0-47.53~14.04.1
  ProcVersionSignature: Ubuntu 3.19.0-47.53~14.04.1-generic 3.19.8-ckt10
  Uname: Linux 3.19.0-47-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  Date: Mon Feb  1 16:26:19 2016
  InstallationDate: Installed on 2016-01-31 (0 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  SourcePackage: linux-lts-vivid
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  uros   2656 F pulseaudio
   /dev/snd/controlC0:  uros   2656 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=d2fb9926-f37b-400c-8fae-366846852756
  InstallationDate: Installed on 2016-01-31 (52 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  Lsusb:
   Bus 003 Device 002: ID 8087:8001 Intel Corp. 
   Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 04f2:b483 Chicony Electronics Co., Ltd 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. X302LA
  NonfreeKernelModules: wl
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-56-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.19.0-56.62~14.04.1-generic 3.19.8-ckt15
  RelatedPackageVersions:
   linux-restricted-modules-3.19.0-56-generic N/A
   linux-backports-modules-3.19.0-56-generic  N/A
   linux-firmware 1.127.20
  Tags:  trusty
  Uname: Linux 3.19.0-56-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 08/24/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X302LA.204
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X302LA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrX302LA.204:bd08/24/2015:svnASUSTeKCOMPUTERINC.:pnX302LA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX302LA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: X302LA
  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/1540430/+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 1540430] Re: Touchpad not working after suspend/resume

latest Xorg.0.log

** Attachment added: "Xorg.0.log"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1540430/+attachment/4618640/+files/Xorg.0.log

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

Title:
  Touchpad not working after suspend/resume

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Touchpad not working after suspend/resume on Asus X302LA.

  I have tried both workarounds in bug  #1393079 to no success.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.19.0-47-generic 3.19.0-47.53~14.04.1
  ProcVersionSignature: Ubuntu 3.19.0-47.53~14.04.1-generic 3.19.8-ckt10
  Uname: Linux 3.19.0-47-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  Date: Mon Feb  1 16:26:19 2016
  InstallationDate: Installed on 2016-01-31 (0 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  SourcePackage: linux-lts-vivid
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  uros   2656 F pulseaudio
   /dev/snd/controlC0:  uros   2656 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=d2fb9926-f37b-400c-8fae-366846852756
  InstallationDate: Installed on 2016-01-31 (52 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  Lsusb:
   Bus 003 Device 002: ID 8087:8001 Intel Corp. 
   Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 04f2:b483 Chicony Electronics Co., Ltd 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. X302LA
  NonfreeKernelModules: wl
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-56-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.19.0-56.62~14.04.1-generic 3.19.8-ckt15
  RelatedPackageVersions:
   linux-restricted-modules-3.19.0-56-generic N/A
   linux-backports-modules-3.19.0-56-generic  N/A
   linux-firmware 1.127.20
  Tags:  trusty
  Uname: Linux 3.19.0-56-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 08/24/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X302LA.204
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X302LA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrX302LA.204:bd08/24/2015:svnASUSTeKCOMPUTERINC.:pnX302LA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX302LA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: X302LA
  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/1540430/+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 1540430] Re: Touchpad not working after suspend/resume

6.

sudo su
echo devices > /sys/power/pm_test
exit

sudo sh -c "sync && echo 1 > /sys/power/pm_trace && pm-suspend"

dmesg > dmesg.txt

** Attachment added: "dmesg.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1540430/+attachment/4618629/+files/dmesg.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/1540430

Title:
  Touchpad not working after suspend/resume

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Touchpad not working after suspend/resume on Asus X302LA.

  I have tried both workarounds in bug  #1393079 to no success.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.19.0-47-generic 3.19.0-47.53~14.04.1
  ProcVersionSignature: Ubuntu 3.19.0-47.53~14.04.1-generic 3.19.8-ckt10
  Uname: Linux 3.19.0-47-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  Date: Mon Feb  1 16:26:19 2016
  InstallationDate: Installed on 2016-01-31 (0 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  SourcePackage: linux-lts-vivid
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  uros   2656 F pulseaudio
   /dev/snd/controlC0:  uros   2656 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=d2fb9926-f37b-400c-8fae-366846852756
  InstallationDate: Installed on 2016-01-31 (52 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  Lsusb:
   Bus 003 Device 002: ID 8087:8001 Intel Corp. 
   Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 04f2:b483 Chicony Electronics Co., Ltd 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. X302LA
  NonfreeKernelModules: wl
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-56-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.19.0-56.62~14.04.1-generic 3.19.8-ckt15
  RelatedPackageVersions:
   linux-restricted-modules-3.19.0-56-generic N/A
   linux-backports-modules-3.19.0-56-generic  N/A
   linux-firmware 1.127.20
  Tags:  trusty
  Uname: Linux 3.19.0-56-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 08/24/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X302LA.204
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X302LA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrX302LA.204:bd08/24/2015:svnASUSTeKCOMPUTERINC.:pnX302LA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX302LA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: X302LA
  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/1540430/+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 1540430] Re: Touchpad not working after suspend/resume

8.

sudo su
echo processors > /sys/power/pm_test
exit


sudo sh -c "sync && echo 1 > /sys/power/pm_trace && pm-suspend"

dmesg > dmesg.txt


** Attachment added: "dmesg.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1540430/+attachment/4618633/+files/dmesg.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/1540430

Title:
  Touchpad not working after suspend/resume

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Touchpad not working after suspend/resume on Asus X302LA.

  I have tried both workarounds in bug  #1393079 to no success.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.19.0-47-generic 3.19.0-47.53~14.04.1
  ProcVersionSignature: Ubuntu 3.19.0-47.53~14.04.1-generic 3.19.8-ckt10
  Uname: Linux 3.19.0-47-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  Date: Mon Feb  1 16:26:19 2016
  InstallationDate: Installed on 2016-01-31 (0 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  SourcePackage: linux-lts-vivid
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  uros   2656 F pulseaudio
   /dev/snd/controlC0:  uros   2656 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=d2fb9926-f37b-400c-8fae-366846852756
  InstallationDate: Installed on 2016-01-31 (52 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  Lsusb:
   Bus 003 Device 002: ID 8087:8001 Intel Corp. 
   Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 04f2:b483 Chicony Electronics Co., Ltd 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. X302LA
  NonfreeKernelModules: wl
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-56-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.19.0-56.62~14.04.1-generic 3.19.8-ckt15
  RelatedPackageVersions:
   linux-restricted-modules-3.19.0-56-generic N/A
   linux-backports-modules-3.19.0-56-generic  N/A
   linux-firmware 1.127.20
  Tags:  trusty
  Uname: Linux 3.19.0-56-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 08/24/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X302LA.204
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X302LA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrX302LA.204:bd08/24/2015:svnASUSTeKCOMPUTERINC.:pnX302LA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX302LA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: X302LA
  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/1540430/+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 1540430] Re: Touchpad not working after suspend/resume

5.

uname -a
Linux X302LA 4.6.0-040600rc1-generic #201603261930 SMP Sat Mar 26 23:32:43 UTC 
2016 x86_64 x86_64 x86_64 GNU/Linux

sudo su
echo freezer > /sys/power/pm_test
exit

sudo sh -c "sync && echo 1 > /sys/power/pm_trace && pm-suspend"

dmesg > dmesg.txt


** Attachment added: "dmesg.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1540430/+attachment/4618628/+files/dmesg.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/1540430

Title:
  Touchpad not working after suspend/resume

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Touchpad not working after suspend/resume on Asus X302LA.

  I have tried both workarounds in bug  #1393079 to no success.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.19.0-47-generic 3.19.0-47.53~14.04.1
  ProcVersionSignature: Ubuntu 3.19.0-47.53~14.04.1-generic 3.19.8-ckt10
  Uname: Linux 3.19.0-47-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  Date: Mon Feb  1 16:26:19 2016
  InstallationDate: Installed on 2016-01-31 (0 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  SourcePackage: linux-lts-vivid
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  uros   2656 F pulseaudio
   /dev/snd/controlC0:  uros   2656 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=d2fb9926-f37b-400c-8fae-366846852756
  InstallationDate: Installed on 2016-01-31 (52 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  Lsusb:
   Bus 003 Device 002: ID 8087:8001 Intel Corp. 
   Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 04f2:b483 Chicony Electronics Co., Ltd 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. X302LA
  NonfreeKernelModules: wl
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-56-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.19.0-56.62~14.04.1-generic 3.19.8-ckt15
  RelatedPackageVersions:
   linux-restricted-modules-3.19.0-56-generic N/A
   linux-backports-modules-3.19.0-56-generic  N/A
   linux-firmware 1.127.20
  Tags:  trusty
  Uname: Linux 3.19.0-56-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 08/24/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X302LA.204
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X302LA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrX302LA.204:bd08/24/2015:svnASUSTeKCOMPUTERINC.:pnX302LA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX302LA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: X302LA
  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/1540430/+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 1540430] Re: Touchpad not working after suspend/resume

11.

sudo cat /sys/kernel/debug/suspend_stats >suspend_stats

12.

N/A

** Attachment added: "suspend_stats"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1540430/+attachment/4618636/+files/suspend_stats

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

Title:
  Touchpad not working after suspend/resume

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Touchpad not working after suspend/resume on Asus X302LA.

  I have tried both workarounds in bug  #1393079 to no success.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.19.0-47-generic 3.19.0-47.53~14.04.1
  ProcVersionSignature: Ubuntu 3.19.0-47.53~14.04.1-generic 3.19.8-ckt10
  Uname: Linux 3.19.0-47-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  Date: Mon Feb  1 16:26:19 2016
  InstallationDate: Installed on 2016-01-31 (0 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  SourcePackage: linux-lts-vivid
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  uros   2656 F pulseaudio
   /dev/snd/controlC0:  uros   2656 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=d2fb9926-f37b-400c-8fae-366846852756
  InstallationDate: Installed on 2016-01-31 (52 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  Lsusb:
   Bus 003 Device 002: ID 8087:8001 Intel Corp. 
   Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 04f2:b483 Chicony Electronics Co., Ltd 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. X302LA
  NonfreeKernelModules: wl
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-56-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.19.0-56.62~14.04.1-generic 3.19.8-ckt15
  RelatedPackageVersions:
   linux-restricted-modules-3.19.0-56-generic N/A
   linux-backports-modules-3.19.0-56-generic  N/A
   linux-firmware 1.127.20
  Tags:  trusty
  Uname: Linux 3.19.0-56-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 08/24/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X302LA.204
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X302LA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrX302LA.204:bd08/24/2015:svnASUSTeKCOMPUTERINC.:pnX302LA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX302LA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: X302LA
  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/1540430/+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 1540430] Re: Touchpad not working after suspend/resume

9.

sudo su
echo core > /sys/power/pm_test
exit


sudo sh -c "sync && echo 1 > /sys/power/pm_trace && pm-suspend"

dmesg > dmesg.txt

** Attachment added: "dmesg.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1540430/+attachment/4618634/+files/dmesg.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/1540430

Title:
  Touchpad not working after suspend/resume

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Touchpad not working after suspend/resume on Asus X302LA.

  I have tried both workarounds in bug  #1393079 to no success.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.19.0-47-generic 3.19.0-47.53~14.04.1
  ProcVersionSignature: Ubuntu 3.19.0-47.53~14.04.1-generic 3.19.8-ckt10
  Uname: Linux 3.19.0-47-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  Date: Mon Feb  1 16:26:19 2016
  InstallationDate: Installed on 2016-01-31 (0 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  SourcePackage: linux-lts-vivid
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  uros   2656 F pulseaudio
   /dev/snd/controlC0:  uros   2656 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=d2fb9926-f37b-400c-8fae-366846852756
  InstallationDate: Installed on 2016-01-31 (52 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  Lsusb:
   Bus 003 Device 002: ID 8087:8001 Intel Corp. 
   Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 04f2:b483 Chicony Electronics Co., Ltd 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. X302LA
  NonfreeKernelModules: wl
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-56-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.19.0-56.62~14.04.1-generic 3.19.8-ckt15
  RelatedPackageVersions:
   linux-restricted-modules-3.19.0-56-generic N/A
   linux-backports-modules-3.19.0-56-generic  N/A
   linux-firmware 1.127.20
  Tags:  trusty
  Uname: Linux 3.19.0-56-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 08/24/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X302LA.204
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X302LA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrX302LA.204:bd08/24/2015:svnASUSTeKCOMPUTERINC.:pnX302LA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX302LA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: X302LA
  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/1540430/+subscriptions

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

Re: [Kernel-packages] [Bug 1564470] Re: Unable to install NI-VISA nikal kernel module because of GPL-only symbol 'pgprot_writecombine'

Dear Ingo Molnar!

I have a problem with *EXPORT_SYMBOL_GPL(pgprot_writecombine)* with Linux
4.4.0.16 on Ubuntu 16.04.
The *pgprot_writecombine* symbol is used in NI_VISA nikal driver (see
forwarded bugreport ).

Is it safe to change *EXPORT_SYMBOL_GPL(pgprot_writecombine) *to
*EXPORT_SYMBOL(pgprot_writecombine)*?


With best regards,
Norbert.

-- Forwarded message --
From: Tim Gardner 
Date: Thu, Mar 31, 2016 at 7:01 PM
Subject: [Bug 1564470] Re: Unable to install NI-VISA nikal kernel module
because of GPL-only symbol 'pgprot_writecombine'
To: nrb...@gmail.com


Commit 92b9af9e4f144535c65aee673cfad309f25fa465 ('x86: i915 needs
pgprot_writecombine() and is_io_mapping_possible()') is where that
symbol is exported. You could send an email to Ingo Molnar
 and see if he is interested in relaxing that export.

--
You received this bug notification because you are subscribed to the bug
report.
https://bugs.launchpad.net/bugs/1564470

Title:
  Unable to install NI-VISA nikal kernel module because of GPL-only
  symbol 'pgprot_writecombine'

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Steps to reproduce:
  1. Login to National Instruments site
  2. Download NI-VISA 15.0 for linux (NI-VISA-15.0.0.iso).
  3. Launch its installation by "sudo ./INSTALL"
  4. Get errors on nikal kernel modules compilation about
"pgprot_writecombine" symbol ("nikal: FATAL: modpost: GPL-incompatible
module nikal.ko uses GPL-only symbol 'pgprot_writecombine'")

  Temporary solution:
  1. Edit /usr/src/linux-headers-4.4.0-16-generic/Module.symvers
  and change line
 0xd544e902 pgprot_writecombine vmlinux EXPORT_SYMBOL_GPL
  to
 0xd544e902 pgprot_writecombine vmlinux EXPORT_SYMBOL
  2. Edit /boot/abi-4.4.0-16-generic
  and change line
 EXPORT_SYMBOL_GPL vmlinux 0xd544e902   pgprot_writecombine
  to
 EXPORT_SYMBOL vmlinux 0xd544e902   pgprot_writecombine

  but it does not help - I get "nikal: Unknown symbol
  pgprot_writecombine (err 0)" in syslog.

  Expected results:
  0. The 'pgprot_writecombine' symbol is exported as EXPORT_SYMBOL
  1. Ubuntu can compile and load NI nikal module.

  Actual results:
  Unable to use NI-VISA under Ubuntu.

  Reference (openSUSE):

http://forums.ni.com/t5/Instrument-Control-GPIB-Serial/GPL-incompatible-
module-nikal-ko/td-p/3218730

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-16-generic 4.4.0-16.32
  ProcVersionSignature: Ubuntu 4.4.0-16.32-generic 4.4.6
  Uname: Linux 4.4.0-16-generic i686
  ApportVersion: 2.20-0ubuntu3
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  flash  1549 F pulseaudio
   /dev/snd/controlC0:  flash  1549 F pulseaudio
  CurrentDesktop: Unity
  Date: Thu Mar 31 18:16:37 2016
  InstallationDate: Installed on 2016-03-26 (4 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Beta i386 (20160323)
  IwConfig:
   lono wireless extensions.

   enp1s0no wireless extensions.
  MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M.
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-16-generic
root=UUID=eab7b488-5040-499c-afd8-21a7ce9e2383 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-16-generic N/A
   linux-backports-modules-4.4.0-16-generic  N/A
   linux-firmware1.157
  RfKill:

  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/09/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: FD
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: F2A55M-DS2
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvrFD:bd01/09/2014:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnF2A55M-DS2:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To be filled by O.E.M.
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

To manage notifications about this bug go to:mi...@elte.hu
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1564470/+subscriptions

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

Title:
  Unable to install NI-VISA nikal kernel module because of GPL-only
  symbol 'pgprot_writecombine'

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Steps to reproduce:
  1. Login to National Instruments site
  2. Download NI-VISA 15.0 for linux

[Kernel-packages] [Bug 1540430] Re: Touchpad not working after suspend/resume

Which part of the process does the issue occur with, the suspend to ram, or 
resuming from?
Resuming from

Please advise how you suspended specifically. (all apply)
Executing at a terminal pm-suspend
Shutting the lid of your laptop, which is set to suspend on close.
Clicking the word Suspend in the GUI.
The computer suspends automatically on inactivity. 

Please advise how you resumed specifically. Doesn't matter. Check
already attached logs.

Pressed the power button
Lifted the lid
Clicked a key on the keyboard 


** Attachment added: "cat /proc/acpi/wakeup > wakeup"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1540430/+attachment/4618608/+files/wakeup

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

Title:
  Touchpad not working after suspend/resume

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Touchpad not working after suspend/resume on Asus X302LA.

  I have tried both workarounds in bug  #1393079 to no success.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.19.0-47-generic 3.19.0-47.53~14.04.1
  ProcVersionSignature: Ubuntu 3.19.0-47.53~14.04.1-generic 3.19.8-ckt10
  Uname: Linux 3.19.0-47-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  Date: Mon Feb  1 16:26:19 2016
  InstallationDate: Installed on 2016-01-31 (0 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  SourcePackage: linux-lts-vivid
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  uros   2656 F pulseaudio
   /dev/snd/controlC0:  uros   2656 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=d2fb9926-f37b-400c-8fae-366846852756
  InstallationDate: Installed on 2016-01-31 (52 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  Lsusb:
   Bus 003 Device 002: ID 8087:8001 Intel Corp. 
   Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 04f2:b483 Chicony Electronics Co., Ltd 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. X302LA
  NonfreeKernelModules: wl
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-56-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.19.0-56.62~14.04.1-generic 3.19.8-ckt15
  RelatedPackageVersions:
   linux-restricted-modules-3.19.0-56-generic N/A
   linux-backports-modules-3.19.0-56-generic  N/A
   linux-firmware 1.127.20
  Tags:  trusty
  Uname: Linux 3.19.0-56-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 08/24/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X302LA.204
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X302LA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrX302LA.204:bd08/24/2015:svnASUSTeKCOMPUTERINC.:pnX302LA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX302LA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: X302LA
  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/1540430/+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 1558727] bantam (amd64) - tests ran: 180, failed: 0

tests ran: 180, failed: 0;
  
http://kernel.ubuntu.com/testing/3.13.0-85.129/bantam__3.13.0-85.129__2016-03-31_15-22-00/results-index.html

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

Title:
  linux: 3.13.0-85.129 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Fix Released
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  Confirmed
Status in Kernel SRU Workflow promote-to-updates series:
  Confirmed
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Trusty:
  Confirmed

Bug description:
  This bug is for tracking the 3.13.0-85.129 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
  kernel-stable-Promote-to-proposed-end:Thursday, 17. March 2016 22:51 UTC
  kernel-stable-Prepare-package-end:Friday, 18. March 2016 03:05 UTC
  kernel-stable-Promote-to-proposed-start:Friday, 18. March 2016 03:05 UTC
  kernel-stable-Verification-testing-start:Friday, 18. March 2016 12:01 UTC
  kernel-stable-Certification-testing-start:Friday, 18. March 2016 12:02 UTC
  kernel-stable-Security-signoff-start:Friday, 18. March 2016 12:02 UTC
  proposed-announcement-sent:True
  kernel-stable-Regression-testing-start:Friday, 18. March 2016 12:02 UTC
  kernel-stable-Security-signoff-end:Friday, 18. March 2016 20:03 UTC
  kernel-stable-Regression-testing-end:Monday, 28. March 2016 15:03 UTC
  kernel-stable-Verification-testing-end:Tuesday, 29. March 2016 15:01 UTC
  kernel-stable-phase:CopyToUpdates
  kernel-stable-Promote-to-updates-start:Thursday, 31. March 2016 03:01 UTC
  kernel-stable-phase-changed:Thursday, 31. March 2016 03:01 UTC
  kernel-stable-Certification-testing-end:Thursday, 31. March 2016 03:01 UTC

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1558727/+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 1563441] Re: linux: 4.4.0-17.33 -proposed tracker

2016-03-31 Thread Adam Conrad

** Changed in: kernel-development-workflow/promote-to-proposed
   Status: Incomplete => Fix Released

** Changed in: kernel-development-workflow/promote-to-proposed
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Adam Conrad 
(adconrad)

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

Title:
  linux: 4.4.0-17.33 -proposed tracker

Status in Kernel Development Workflow:
  In Progress
Status in Kernel Development Workflow automated-testing series:
  New
Status in Kernel Development Workflow prepare-package series:
  Fix Released
Status in Kernel Development Workflow prepare-package-meta series:
  Fix Released
Status in Kernel Development Workflow prepare-package-signed series:
  Fix Released
Status in Kernel Development Workflow promote-to-proposed series:
  Fix Released
Status in Kernel Development Workflow promote-to-release series:
  New
Status in Kernel Development Workflow regression-testing series:
  New
Status in linux package in Ubuntu:
  New
Status in linux source package in Xenial:
  New

Bug description:
  This bug is for tracking the 4.4.0-17.33 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
  kernel-Prepare-package-start:Tuesday, 29. March 2016 16:41 UTC
  kernel-phase-changed:Tuesday, 29. March 2016 16:41 UTC
  kernel-phase:Prepare

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-development-workflow/+bug/1563441/+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 1564487] Re: ISST-LTE:pVM:thymelp2:ubuntu 16.04: cannot analyse vmcore with crash (s390x, ppc64)

2016-03-31 Thread Breno Leitão

Dear Canonical,

These two patches are required in 4.4 kernel because Tim cherry picked
8244062ef1e54502ef55f54cced659913f244c3e, and it became
21b06ff8d4dd559b93ca60e26e8ffd811d030b39. This broke crash, and now
these two patches are required in the crash tool:

 *  098cdab16dfa6a85e9dad2cad604dee14ee15f66
 * 6f1f78e33474d00d5f261d7ed9d835c558b34d61

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

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

Title:
  ISST-LTE:pVM:thymelp2:ubuntu 16.04: cannot analyse vmcore with crash
  (s390x, ppc64)

Status in crash package in Ubuntu:
  Confirmed

Bug description:
  == Comment: #0 - Ping Tian Han - 2016-03-31 02:19:27 ==
  ---Problem Description---
  With the kexec-tools comes from 
https://bugzilla.linux.ibm.com/show_bug.cgi?id=136588#c58 , we have dumpped a 
vmcore for bug 139815 after quiting from xmon. But when trying to analyse with 
crash:

  % sudo crash /usr/lib/debug/boot/vmlinux-4.4.0-15-generic
  /var/crash/201603310043/dump.201603310043

  crash 7.1.4
  Copyright (C) 2002-2015  Red Hat, Inc.
  Copyright (C) 2004, 2005, 2006, 2010  IBM Corporation
  Copyright (C) 1999-2006  Hewlett-Packard Co
  Copyright (C) 2005, 2006, 2011, 2012  Fujitsu Limited
  Copyright (C) 2006, 2007  VA Linux Systems Japan K.K.
  Copyright (C) 2005, 2011  NEC Corporation
  Copyright (C) 1999, 2002, 2007  Silicon Graphics, Inc.
  Copyright (C) 1999, 2000, 2001, 2002  Mission Critical Linux, Inc.
  This program is free software, covered by the GNU General Public License,
  and you are welcome to change it and/or distribute copies of it under
  certain conditions.  Enter "help copying" to see the conditions.
  This program has absolutely no warranty.  Enter "help warranty" for details.

  GNU gdb (GDB) 7.6
  Copyright (C) 2013 Free Software Foundation, Inc.
  License GPLv3+: GNU GPL version 3 or later 
  This is free software: you are free to change and redistribute it.
  There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
  and "show warranty" for details.
  This GDB was configured as "powerpc64le-unknown-linux-gnu"...

  please wait... (gathering module symbol data)
  crash: invalid structure member offset: module_num_symtab
 FILE: kernel.c  LINE: 3450  FUNCTION: module_init()

  [/usr/bin/crash] error trace: 1008af0c => 10124250 => 10179bd0 =>
  10083378

10083378: (undetermined)
10179bd0: OFFSET_verify+80
10124250: module_init+1104
1008af0c: main_loop+764

  %

  == Comment: #4 - Hari Krishna Bathini - 2016-03-31 08:20:39 ==
  (In reply to comment #2)
  > Hi, 
  > 
  > Crash failing with 4.4+ kernels is a known issue which is fixed by the
  > upstream patch 
  > 
  > commit 6f1f78e33474d00d5f261d7ed9d835c558b34d61
  > Author: Dave Anderson 
  > Date:   Wed Jan 20 09:56:36 2016 -0500
  > 
  > Fix for the changes made to the kernel module structure introduced by
  > this kernel commit for Linux 4.5 and later kernels:
  > 
  >   commit 7523e4dc5057e157212b4741abd6256e03404cf1
  >   module: use a structure to encapsulate layout.
  > 
  > Without the patch, the crash session fails during initialization
  > with the error message: "crash: invalid structure member offset:
  > module_init_text_size".
  > (seb...@linux.vnet.ibm.com)
  > 

  We also need the below upstream patch along with the patch mentioned
  above to fix this issue

  commit 098cdab16dfa6a85e9dad2cad604dee14ee15f66
  Author: Dave Anderson 
  Date:   Fri Feb 12 14:32:53 2016 -0500

  Fix for the changes made to the kernel module structure introduced by
  this kernel commit for Linux 4.5 and later kernels:
  
commit 8244062ef1e54502ef55f54cced659913f244c3e
modules: fix longstanding /proc/kallsyms vs module insertion race.
  
  Without the patch, the crash session fails during initialization
  with the error message: "crash: invalid structure member offset:
  module_num_symtab".
  (ander...@redhat.com)

  Thanks
  Hari

  == Comment: #9 - Hendrik Brueckner - 2016-03-31 11:47:13 ==
  Problem also exists on s390x:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/crash/+bug/1564487/+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 1556096] Re: [Ubuntu 16.04.1] RELEASE and ACQUIRE atomics on Power

2016-03-31 Thread Leann Ogasawara

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

** Changed in: linux (Ubuntu)
 Assignee: Breno Leitão (breno-leitao) => Canonical Kernel Team 
(canonical-kernel-team)

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

Title:
  [Ubuntu 16.04.1] RELEASE and ACQUIRE atomics on Power

Status in linux package in Ubuntu:
  Triaged

Bug description:
  Will Deacon proposed the RELEASE/ACQUIRE/RELAXED semantics for atomic
  operations(https://lkml.org/lkml/2015/8/6/498), which has been already
  merged in 4.3-rc1. More people tend to use it for better
  performance(https://lkml.org/lkml/2015/9/20/47). These semantics are
  proposed for better fitting the need of high scalability.

   However, the efficient implementation hasn't been merged yet. As we
  have a weaker memory order model on POWER, if we didn't implement
  these atomics efficently, there would be no benefit we can gain from
  these new operations.

  A proposal of an efficient implemenation has been sent out to
  upstream(https://lkml.org/lkml/2015/9/16/527), hopefully will get
  merged. Still there may be more atomics having RELEASE and ACQUIRE
  semantics, and there need more effort to implement them correctly.
  Also, we need to spread these new atomic variants to LTC kernel team
  to understand what they can provide and how to use them.

  > Was this feature already accepted upstream?

  Not yet, still waiting to get into the maintainer's tree, but there is
  no obvious objection to this feature.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1556096/+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 1556096] Re: [Ubuntu 16.04.1] RELEASE and ACQUIRE atomics on Power

2016-03-31 Thread Breno Leitão

Hi Leann,

The patches were finally acccepted and they are on Linus' tree. They
are:

56c08e6d226c powerpc: atomic: Implement acquire/release/relaxed variants for 
cmpxchg
26760fc19a7e powerpc: atomic: Implement acquire/release/relaxed variants for 
xchg
dc53617c4a3f powerpc: atomic: Implement atomic{, 64}_*_return_* variants
e1ab7f39d7e0 atomics: Allow architectures to define their own __atomic_op_* 
helpers

Thank you,
Breno

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

Title:
  [Ubuntu 16.04.1] RELEASE and ACQUIRE atomics on Power

Status in linux package in Ubuntu:
  Triaged

Bug description:
  Will Deacon proposed the RELEASE/ACQUIRE/RELAXED semantics for atomic
  operations(https://lkml.org/lkml/2015/8/6/498), which has been already
  merged in 4.3-rc1. More people tend to use it for better
  performance(https://lkml.org/lkml/2015/9/20/47). These semantics are
  proposed for better fitting the need of high scalability.

   However, the efficient implementation hasn't been merged yet. As we
  have a weaker memory order model on POWER, if we didn't implement
  these atomics efficently, there would be no benefit we can gain from
  these new operations.

  A proposal of an efficient implemenation has been sent out to
  upstream(https://lkml.org/lkml/2015/9/16/527), hopefully will get
  merged. Still there may be more atomics having RELEASE and ACQUIRE
  semantics, and there need more effort to implement them correctly.
  Also, we need to spread these new atomic variants to LTC kernel team
  to understand what they can provide and how to use them.

  > Was this feature already accepted upstream?

  Not yet, still waiting to get into the maintainer's tree, but there is
  no obvious objection to this feature.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1556096/+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 1564487] Re: ISST-LTE:pVM:thymelp2:ubuntu 16.04: cannot analyse vmcore with crash (s390x, ppc64)

2016-03-31 Thread Leann Ogasawara

** Changed in: crash (Ubuntu)
 Assignee: Taco Screen team (taco-screen-team) => Canonical Kernel Team 
(canonical-kernel-team)

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

Title:
  ISST-LTE:pVM:thymelp2:ubuntu 16.04: cannot analyse vmcore with crash
  (s390x, ppc64)

Status in crash package in Ubuntu:
  New

Bug description:
  == Comment: #0 - Ping Tian Han - 2016-03-31 02:19:27 ==
  ---Problem Description---
  With the kexec-tools comes from 
https://bugzilla.linux.ibm.com/show_bug.cgi?id=136588#c58 , we have dumpped a 
vmcore for bug 139815 after quiting from xmon. But when trying to analyse with 
crash:

  % sudo crash /usr/lib/debug/boot/vmlinux-4.4.0-15-generic
  /var/crash/201603310043/dump.201603310043

  crash 7.1.4
  Copyright (C) 2002-2015  Red Hat, Inc.
  Copyright (C) 2004, 2005, 2006, 2010  IBM Corporation
  Copyright (C) 1999-2006  Hewlett-Packard Co
  Copyright (C) 2005, 2006, 2011, 2012  Fujitsu Limited
  Copyright (C) 2006, 2007  VA Linux Systems Japan K.K.
  Copyright (C) 2005, 2011  NEC Corporation
  Copyright (C) 1999, 2002, 2007  Silicon Graphics, Inc.
  Copyright (C) 1999, 2000, 2001, 2002  Mission Critical Linux, Inc.
  This program is free software, covered by the GNU General Public License,
  and you are welcome to change it and/or distribute copies of it under
  certain conditions.  Enter "help copying" to see the conditions.
  This program has absolutely no warranty.  Enter "help warranty" for details.

  GNU gdb (GDB) 7.6
  Copyright (C) 2013 Free Software Foundation, Inc.
  License GPLv3+: GNU GPL version 3 or later 
  This is free software: you are free to change and redistribute it.
  There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
  and "show warranty" for details.
  This GDB was configured as "powerpc64le-unknown-linux-gnu"...

  please wait... (gathering module symbol data)
  crash: invalid structure member offset: module_num_symtab
 FILE: kernel.c  LINE: 3450  FUNCTION: module_init()

  [/usr/bin/crash] error trace: 1008af0c => 10124250 => 10179bd0 =>
  10083378

10083378: (undetermined)
10179bd0: OFFSET_verify+80
10124250: module_init+1104
1008af0c: main_loop+764

  %

  == Comment: #4 - Hari Krishna Bathini - 2016-03-31 08:20:39 ==
  (In reply to comment #2)
  > Hi, 
  > 
  > Crash failing with 4.4+ kernels is a known issue which is fixed by the
  > upstream patch 
  > 
  > commit 6f1f78e33474d00d5f261d7ed9d835c558b34d61
  > Author: Dave Anderson 
  > Date:   Wed Jan 20 09:56:36 2016 -0500
  > 
  > Fix for the changes made to the kernel module structure introduced by
  > this kernel commit for Linux 4.5 and later kernels:
  > 
  >   commit 7523e4dc5057e157212b4741abd6256e03404cf1
  >   module: use a structure to encapsulate layout.
  > 
  > Without the patch, the crash session fails during initialization
  > with the error message: "crash: invalid structure member offset:
  > module_init_text_size".
  > (seb...@linux.vnet.ibm.com)
  > 

  We also need the below upstream patch along with the patch mentioned
  above to fix this issue

  commit 098cdab16dfa6a85e9dad2cad604dee14ee15f66
  Author: Dave Anderson 
  Date:   Fri Feb 12 14:32:53 2016 -0500

  Fix for the changes made to the kernel module structure introduced by
  this kernel commit for Linux 4.5 and later kernels:
  
commit 8244062ef1e54502ef55f54cced659913f244c3e
modules: fix longstanding /proc/kallsyms vs module insertion race.
  
  Without the patch, the crash session fails during initialization
  with the error message: "crash: invalid structure member offset:
  module_num_symtab".
  (ander...@redhat.com)

  Thanks
  Hari

  == Comment: #9 - Hendrik Brueckner - 2016-03-31 11:47:13 ==
  Problem also exists on s390x:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/crash/+bug/1564487/+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 1540430] Re: Touchpad not working after suspend/resume

kernel-bug-exists-upstream
kernel-bug-exists-upstream-4.6.0-040600rc1

uname -a
Linux X302LA 4.6.0-040600rc1-generic #201603261930 SMP Sat Mar 26 23:32:43 UTC 
2016 x86_64 x86_64 x86_64 GNU/Linux

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

Title:
  Touchpad not working after suspend/resume

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Touchpad not working after suspend/resume on Asus X302LA.

  I have tried both workarounds in bug  #1393079 to no success.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.19.0-47-generic 3.19.0-47.53~14.04.1
  ProcVersionSignature: Ubuntu 3.19.0-47.53~14.04.1-generic 3.19.8-ckt10
  Uname: Linux 3.19.0-47-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  Date: Mon Feb  1 16:26:19 2016
  InstallationDate: Installed on 2016-01-31 (0 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  SourcePackage: linux-lts-vivid
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  uros   2656 F pulseaudio
   /dev/snd/controlC0:  uros   2656 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=d2fb9926-f37b-400c-8fae-366846852756
  InstallationDate: Installed on 2016-01-31 (52 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  Lsusb:
   Bus 003 Device 002: ID 8087:8001 Intel Corp. 
   Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 04f2:b483 Chicony Electronics Co., Ltd 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. X302LA
  NonfreeKernelModules: wl
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-56-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.19.0-56.62~14.04.1-generic 3.19.8-ckt15
  RelatedPackageVersions:
   linux-restricted-modules-3.19.0-56-generic N/A
   linux-backports-modules-3.19.0-56-generic  N/A
   linux-firmware 1.127.20
  Tags:  trusty
  Uname: Linux 3.19.0-56-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 08/24/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X302LA.204
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X302LA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrX302LA.204:bd08/24/2015:svnASUSTeKCOMPUTERINC.:pnX302LA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX302LA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: X302LA
  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/1540430/+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 1564475] Comment bridged from LTC Bugzilla

--- Comment From michael.holz...@de.ibm.com 2016-03-31 12:50 EDT---
(In reply to comment #11)
> I do not want to increase it beyond 128MB by default, as this amount of
> memory is reserved by default on all installations big or small. And there
> will always be newer kernel (that reserves more memory) or more devices that
> require higher values.

Ok, if we go with the 128M default our current assumption is that on all
LPARs kdump for Ubuntu will fail.

I am not sure how many customers are aware of the fact that they have to
manually tune the kdump settings. Therefore what about some
documentation like the following:

Depending on your system setup it can be necessary to increase the default 
setting of the "crashkernel=" kernel parameter. It is recommended to test the 
kdump setup with "echo c > /proc/sysrq-trigger".
If the crashkernel value is not high enough, kdump will crash with 
out-of-memory error messages. You can see the message on the operating system 
messages. In case kdump does not work you have to increase the value in 
/etc/zipl.conf.

Do you already have a similar documentation already available?

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

Title:
  128M is not enough for kdump on s390 LPARs

Status in makedumpfile package in Ubuntu:
  Invalid

Bug description:
  == Comment: #0 - Michael Holzheu  - 2016-03-31 
10:59:26 ==
  With the current Ubuntu default setting "crashkernel=128M" kdump on LPARs 
crashes with out-of-memory (see attachment "dmesg_lpar_out_of_mem_128M.txt").

  On z/VM guests 128M seems to be sufficient.

  One reason on our test LPAR is that a lot of devices are attached (see
  attachment "lscss_lpar.txt") which are not required for kdump but
  consume a lot of memory because the s390 CIO layer allocates data
  structures in the kernel for those devices.

  We can disable the devices by using the "cio_ignore=" kernel parameter
  in "/etc/default/kdump-tools". For example, on our LPAR that uses DASD
  0.0.e934 for /var/crash, we added the following line to disable the
  devices:

  KDUMP_CMDLINE_APPEND="irqpoll maxcpus=1
  cio_ignore=all,!condev,!0.0.e934"

  For more information on the "cio_ignore=" kernel parameter see:
  https://github.com/torvalds/linux/blob/master/Documentation/s390/CommonIO

  Even with "cio_ignore=" we still get out-of-memory with
  "crashkernel=128M".

  With "crashkernel=196M" and "cio_ignore=" we are able to create a dump
  on our LPAR. We currently do not know why kdump with "cio_ignore=" on
  LPAR consumes more memory than on z/VM guests.

  == Comment: #1 - Michael Holzheu  - 2016-03-31 
11:03:15 ==
  Kernel messages of kdump out-of-memory crash on LPAR with many devices 
without cio_ignore parameter and 128M crashkernel memory.

  == Comment: #2 - Michael Holzheu  - 2016-03-31 
11:04:10 ==
  Output of lscss showing all attached (not online) devices on the LPAR.

  == Comment: #3 - Michael Holzheu  - 2016-03-31 
11:07:35 ==
  To solve this issue our recommendation is:

  1) Increase "crashkernel=" default to 196M on Ubuntu for s390.

  2) Document that KDUMP_CMDLINE_APPEND with "cio_ignore=" can be used
  to decrease memory consumption for kdump on systems with many devices
  that are not required for kdump.

  The most user friendly solution would be to automatically determine
  the required kdump devices and set the correct "cio_ignore=" kernel
  parameter. But this is not trivial, because it can be difficult to
  find out the required devices for stacked setups like LVM or for
  network dump.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1564475/+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 1563110] Re: No sound on Asus e200ha, intel sst with cx2072x codec

2016-03-31 Thread Gianmaria Scorza

Any news about 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/1563110

Title:
  No sound on Asus e200ha, intel sst with cx2072x codec

Status in alsa-driver package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I've recently bought an Asus e200ha.
  Sound in this laptop doesn't work.
  The sound card is an intel sst with codec conexant cx2072x

  aplay -l:
  aplay: device_list:268: no soundcard found...
  in the sound setting there is a "Dummy output"
  --- 
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=7b77dc46-7d5b-4869-83dd-739980736c3a
  InstallationDate: Installed on 2016-03-28 (0 days ago)
  InstallationMedia: Linux Mint 17.3 "Rosa" - Release amd64 20160105
  Lsusb:
   Bus 002 Device 002: ID 0781:5583 SanDisk Corp. 
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 13d3:3496 IMC Networks 
   Bus 001 Device 002: ID 04f2:b54b Chicony Electronics Co., Ltd 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. E200HA
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-32-generic 
root=UUID=50fb13c0-a8cd-441d-a38b-c0295c1b9a15 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.19.0-32.37~14.04.1-generic 3.19.8-ckt7
  RelatedPackageVersions:
   linux-restricted-modules-3.19.0-32-generic N/A
   linux-backports-modules-3.19.0-32-generic  N/A
   linux-firmware 1.127.16
  Tags:  rosa
  Uname: Linux 3.19.0-32-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/26/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: E200HA.203
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: E200HA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrE200HA.203:bd11/26/2015:svnASUSTeKCOMPUTERINC.:pnE200HA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnE200HA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: E200HA
  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/alsa-driver/+bug/1563110/+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 1564475] Comment bridged from LTC Bugzilla

--- Comment From thorsten.di...@de.ibm.com 2016-03-31 12:31 EDT---
(In reply to comment #9)
> IMHO a good method would be to set in /etc/default/kdump-tools the default
> values explicitely in KDUMP_CMDLINE , e.g.
> KDUMP_CMDLINE="irqpoll maxcpus=1 nousb systemd.unit=kdump-tools.service"
> and to change upon every start/restart of kdump-tools the
> KDUMP_CMDLINE_APPEND to
> KDUMP_CMDLINE_APPEND="", where the
> cio_ignore-statement can be easily computed by executing 'cio_ignore -k',
> which creates an cio_ignore statement for all enabled ccw devices.

where the cio_ignore-statement can be easily computed by executing
'cio_ignore -u && cio_ignore -k'

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

Title:
  128M is not enough for kdump on s390 LPARs

Status in makedumpfile package in Ubuntu:
  Invalid

Bug description:
  == Comment: #0 - Michael Holzheu  - 2016-03-31 
10:59:26 ==
  With the current Ubuntu default setting "crashkernel=128M" kdump on LPARs 
crashes with out-of-memory (see attachment "dmesg_lpar_out_of_mem_128M.txt").

  On z/VM guests 128M seems to be sufficient.

  One reason on our test LPAR is that a lot of devices are attached (see
  attachment "lscss_lpar.txt") which are not required for kdump but
  consume a lot of memory because the s390 CIO layer allocates data
  structures in the kernel for those devices.

  We can disable the devices by using the "cio_ignore=" kernel parameter
  in "/etc/default/kdump-tools". For example, on our LPAR that uses DASD
  0.0.e934 for /var/crash, we added the following line to disable the
  devices:

  KDUMP_CMDLINE_APPEND="irqpoll maxcpus=1
  cio_ignore=all,!condev,!0.0.e934"

  For more information on the "cio_ignore=" kernel parameter see:
  https://github.com/torvalds/linux/blob/master/Documentation/s390/CommonIO

  Even with "cio_ignore=" we still get out-of-memory with
  "crashkernel=128M".

  With "crashkernel=196M" and "cio_ignore=" we are able to create a dump
  on our LPAR. We currently do not know why kdump with "cio_ignore=" on
  LPAR consumes more memory than on z/VM guests.

  == Comment: #1 - Michael Holzheu  - 2016-03-31 
11:03:15 ==
  Kernel messages of kdump out-of-memory crash on LPAR with many devices 
without cio_ignore parameter and 128M crashkernel memory.

  == Comment: #2 - Michael Holzheu  - 2016-03-31 
11:04:10 ==
  Output of lscss showing all attached (not online) devices on the LPAR.

  == Comment: #3 - Michael Holzheu  - 2016-03-31 
11:07:35 ==
  To solve this issue our recommendation is:

  1) Increase "crashkernel=" default to 196M on Ubuntu for s390.

  2) Document that KDUMP_CMDLINE_APPEND with "cio_ignore=" can be used
  to decrease memory consumption for kdump on systems with many devices
  that are not required for kdump.

  The most user friendly solution would be to automatically determine
  the required kdump devices and set the correct "cio_ignore=" kernel
  parameter. But this is not trivial, because it can be difficult to
  find out the required devices for stacked setups like LVM or for
  network dump.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1564475/+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 1564475] Re: 128M is not enough for kdump on s390 LPARs

2016-03-31 Thread Dimitri John Ledkov

128MB is just a sensible default enabled by default everywhere, if in
your case you need more do adjust it accordingly in /etc/zipl.conf and
execute `sudo zipl` and then reboot.

There is no dynamic sizing / computation of zipl.conf and/or crashkernel
paramemter on Ubuntu, and on all architectures one may need to adjust it
to lower/higher values as needed.

** Changed in: makedumpfile (Ubuntu)
   Status: New => Invalid

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

Title:
  128M is not enough for kdump on s390 LPARs

Status in makedumpfile package in Ubuntu:
  Invalid

Bug description:
  == Comment: #0 - Michael Holzheu  - 2016-03-31 
10:59:26 ==
  With the current Ubuntu default setting "crashkernel=128M" kdump on LPARs 
crashes with out-of-memory (see attachment "dmesg_lpar_out_of_mem_128M.txt").

  On z/VM guests 128M seems to be sufficient.

  One reason on our test LPAR is that a lot of devices are attached (see
  attachment "lscss_lpar.txt") which are not required for kdump but
  consume a lot of memory because the s390 CIO layer allocates data
  structures in the kernel for those devices.

  We can disable the devices by using the "cio_ignore=" kernel parameter
  in "/etc/default/kdump-tools". For example, on our LPAR that uses DASD
  0.0.e934 for /var/crash, we added the following line to disable the
  devices:

  KDUMP_CMDLINE_APPEND="irqpoll maxcpus=1
  cio_ignore=all,!condev,!0.0.e934"

  For more information on the "cio_ignore=" kernel parameter see:
  https://github.com/torvalds/linux/blob/master/Documentation/s390/CommonIO

  Even with "cio_ignore=" we still get out-of-memory with
  "crashkernel=128M".

  With "crashkernel=196M" and "cio_ignore=" we are able to create a dump
  on our LPAR. We currently do not know why kdump with "cio_ignore=" on
  LPAR consumes more memory than on z/VM guests.

  == Comment: #1 - Michael Holzheu  - 2016-03-31 
11:03:15 ==
  Kernel messages of kdump out-of-memory crash on LPAR with many devices 
without cio_ignore parameter and 128M crashkernel memory.

  == Comment: #2 - Michael Holzheu  - 2016-03-31 
11:04:10 ==
  Output of lscss showing all attached (not online) devices on the LPAR.

  == Comment: #3 - Michael Holzheu  - 2016-03-31 
11:07:35 ==
  To solve this issue our recommendation is:

  1) Increase "crashkernel=" default to 196M on Ubuntu for s390.

  2) Document that KDUMP_CMDLINE_APPEND with "cio_ignore=" can be used
  to decrease memory consumption for kdump on systems with many devices
  that are not required for kdump.

  The most user friendly solution would be to automatically determine
  the required kdump devices and set the correct "cio_ignore=" kernel
  parameter. But this is not trivial, because it can be difficult to
  find out the required devices for stacked setups like LVM or for
  network dump.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1564475/+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 1564206] Re: fix for do_tools_cpupower when cross-compiling

2016-03-31 Thread Ubuntu Foundations Team Bug Bot

** Tags added: patch

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

Title:
  fix for do_tools_cpupower when cross-compiling

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

Bug description:
  cpupower's Makefile uses ${CROSS} instead of ${CROSS_COMPILE}
  The problem is that debian/rules.d/2-binary-arch.mk needs to set CROSS 
instead of CROSS_COMPILE, like so:

  make -C $(builddirpa)/tools/power/cpupower \
  CROSS=$(CROSS_COMPILE) \
  LIB_MIN=$(abi_release) CPUFREQ_BENCH=false

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1564206/+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 1557690] Comment bridged from LTC Bugzilla

--- Comment From a.efrem...@ru.ibm.com 2016-03-31 12:16 EDT---
Verified on 4.4.0-16

root@s83lp41:~# uname -a
Linux s83lp41 4.4.0-16-generic #32-Ubuntu SMP Thu Mar 24 22:32:30 UTC 2016 
s390x s390x s390x GNU/Linux

root@s83lp41:~# cat /boot/config-4.4.0-16-generic | grep _NUMA
CONFIG_ARCH_SUPPORTS_NUMA_BALANCING=y
CONFIG_NUMA_BALANCING=y
# CONFIG_NUMA_BALANCING_DEFAULT_ENABLED is not set
CONFIG_NUMA=y
CONFIG_NUMA_EMU=y

root@s83lp41:~# cat /boot/config-4.4.0-16-generic | grep _EMU_SIZE
CONFIG_EMU_SIZE=0x1000

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

Title:
  s390/kconfig: CONFIG_NUMA without CONFIG_NUMA_EMU does not make any
  sense on s390x

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Fix Released

Bug description:
  == Comment: #0 - Hendrik Brueckner - 2016-03-15 06:33:03 ==
  For NUMA, ensure the setting of these kernel configuration for s390x:

  # CONFIG_NUMA_BALANCING_DEFAULT_ENABLED is not set
  CONFIG_NUMA_EMU=y
  CONFIG_EMU_SIZE=0x1000

  
  CONFIG_NUMA without CONFIG_NUMA_EMU does not make any sense. s390 does not 
provide hardware topology information. However, we do support fake NUMA to 
improve performance issues seen with very large memory configurations. 
Therefore, CONFIG_NUMA_EMU has to be enabled.

  Given that we only support fake NUMA
  CONFIG_NUMA_BALANCING_DEFAULT_ENABLED should be disabled, since it
  moves pages without any benefit but costs additional cpu cycles.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1557690/+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 1470250] Re: [Hyper-V] Ubuntu 14.04.2 LTS Generation 2 SCSI Errors on VSS Based Backups

2016-03-31 Thread Joseph Salisbury

The 3.13.0-17 kernel ran for 24 hours without hitting the bug.  We know
that the  3.13.0-49 kernel exhibits the bug.  So my next test will be
with the 3.13.0-32.56 kernel  to try and narrow down the version
further.

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

Title:
  [Hyper-V] Ubuntu 14.04.2 LTS Generation 2 SCSI Errors on VSS Based
  Backups

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Trusty:
  In Progress
Status in linux source package in Vivid:
  In Progress
Status in linux source package in Wily:
  In Progress

Bug description:
  Customers have reported running various versions of Ubuntu 14.04.2 LTS
  on Generation 2 Hyper-V Hosts.On a random Basis, the file system
  will be mounted Read-Only due to a "disk error" (which really isn't
  the case here).As a result, they must reboot the Ubuntu guest to
  get the file system to mount RW again.

  The Error seen are the following:
  Apr 30 00:02:01 balticnetworkstraining kernel: [640153.968142] storvsc: Sense 
Key : Unit Attention [current] 
  Apr 30 00:02:01 balticnetworkstraining kernel: [640153.968145] storvsc: Add. 
Sense: Changed operating definition
  Apr 30 00:02:01 balticnetworkstraining kernel: [640153.968161] sd 0:0:0:0: 
Warning! Received an indication that the operating parameters on this target 
have changed. The Linux SCSI layer does not automatically adjust these 
parameters.
  Apr 30 01:23:26 balticnetworkstraining kernel: [645039.584164] hv_storvsc 
vmbus_0_4: cmd 0x2a scsi status 0x2 srb status 0x82
  Apr 30 01:23:26 balticnetworkstraining kernel: [645039.584178] hv_storvsc 
vmbus_0_4: stor pkt 88006eb6c700 autosense data valid - len 18
  Apr 30 01:23:26 balticnetworkstraining kernel: [645039.584180] storvsc: Sense 
Key : Unit Attention [current] 
  Apr 30 01:23:26 balticnetworkstraining kernel: [645039.584183] storvsc: Add. 
Sense: Changed operating definition
  Apr 30 01:23:26 balticnetworkstraining kernel: [645039.584198] sd 0:0:0:0: 
Warning! Received an indication that the operating parameters on this target 
have changed.  The Linux SCSI layer does not automatically adjust these 
parameters.

  This relates to the VSS "Windows Server Backup" process that kicks off at 
midnight on the host and finishes an hour and half later.   
  Yes, we do have hv_vss_daemon and hv_kvp_daemon running for the correct 
kernel version we have.   We're currently running kernel version 
3.13.0-49-generic #83 on one system and 3.16.0-34-generic #37 on the other. -- 
We see the same errors on both.
  As a result, we've been hesitant to drop any more ubuntu guests on our 2012R2 
hyper-v system because of this.   We can stop the backup process and all is 
good, but we need nightly backups to image all of our VM's.   All the windows 
guests have no issues of course.   We also have some CentOS based guests 
running without issues from what we've seen.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1470250/+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 1564487] Comment bridged from LTC Bugzilla

--- Comment From ru...@us.ibm.com 2016-03-31 12:05 EDT---
Canonical,

Since this impacts multiple architectures, do you need/want individual
mirror requests for each arch?

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

Title:
  ISST-LTE:pVM:thymelp2:ubuntu 16.04: cannot analyse vmcore with crash
  (s390x, ppc64)

Status in crash package in Ubuntu:
  New

Bug description:
  == Comment: #0 - Ping Tian Han - 2016-03-31 02:19:27 ==
  ---Problem Description---
  With the kexec-tools comes from 
https://bugzilla.linux.ibm.com/show_bug.cgi?id=136588#c58 , we have dumpped a 
vmcore for bug 139815 after quiting from xmon. But when trying to analyse with 
crash:

  % sudo crash /usr/lib/debug/boot/vmlinux-4.4.0-15-generic
  /var/crash/201603310043/dump.201603310043

  crash 7.1.4
  Copyright (C) 2002-2015  Red Hat, Inc.
  Copyright (C) 2004, 2005, 2006, 2010  IBM Corporation
  Copyright (C) 1999-2006  Hewlett-Packard Co
  Copyright (C) 2005, 2006, 2011, 2012  Fujitsu Limited
  Copyright (C) 2006, 2007  VA Linux Systems Japan K.K.
  Copyright (C) 2005, 2011  NEC Corporation
  Copyright (C) 1999, 2002, 2007  Silicon Graphics, Inc.
  Copyright (C) 1999, 2000, 2001, 2002  Mission Critical Linux, Inc.
  This program is free software, covered by the GNU General Public License,
  and you are welcome to change it and/or distribute copies of it under
  certain conditions.  Enter "help copying" to see the conditions.
  This program has absolutely no warranty.  Enter "help warranty" for details.

  GNU gdb (GDB) 7.6
  Copyright (C) 2013 Free Software Foundation, Inc.
  License GPLv3+: GNU GPL version 3 or later 
  This is free software: you are free to change and redistribute it.
  There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
  and "show warranty" for details.
  This GDB was configured as "powerpc64le-unknown-linux-gnu"...

  please wait... (gathering module symbol data)
  crash: invalid structure member offset: module_num_symtab
 FILE: kernel.c  LINE: 3450  FUNCTION: module_init()

  [/usr/bin/crash] error trace: 1008af0c => 10124250 => 10179bd0 =>
  10083378

10083378: (undetermined)
10179bd0: OFFSET_verify+80
10124250: module_init+1104
1008af0c: main_loop+764

  %

  == Comment: #4 - Hari Krishna Bathini - 2016-03-31 08:20:39 ==
  (In reply to comment #2)
  > Hi, 
  > 
  > Crash failing with 4.4+ kernels is a known issue which is fixed by the
  > upstream patch 
  > 
  > commit 6f1f78e33474d00d5f261d7ed9d835c558b34d61
  > Author: Dave Anderson 
  > Date:   Wed Jan 20 09:56:36 2016 -0500
  > 
  > Fix for the changes made to the kernel module structure introduced by
  > this kernel commit for Linux 4.5 and later kernels:
  > 
  >   commit 7523e4dc5057e157212b4741abd6256e03404cf1
  >   module: use a structure to encapsulate layout.
  > 
  > Without the patch, the crash session fails during initialization
  > with the error message: "crash: invalid structure member offset:
  > module_init_text_size".
  > (seb...@linux.vnet.ibm.com)
  > 

  We also need the below upstream patch along with the patch mentioned
  above to fix this issue

  commit 098cdab16dfa6a85e9dad2cad604dee14ee15f66
  Author: Dave Anderson 
  Date:   Fri Feb 12 14:32:53 2016 -0500

  Fix for the changes made to the kernel module structure introduced by
  this kernel commit for Linux 4.5 and later kernels:
  
commit 8244062ef1e54502ef55f54cced659913f244c3e
modules: fix longstanding /proc/kallsyms vs module insertion race.
  
  Without the patch, the crash session fails during initialization
  with the error message: "crash: invalid structure member offset:
  module_num_symtab".
  (ander...@redhat.com)

  Thanks
  Hari

  == Comment: #9 - Hendrik Brueckner - 2016-03-31 11:47:13 ==
  Problem also exists on s390x:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/crash/+bug/1564487/+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 1500242] Re: Bluetooth devices (Jabra BT250, Audi A3 car kit) can not be connected with BQ Aquaris 4.5

2016-03-31 Thread Uranicus

@Konrad

I have now isolated as requested the Audi only. Please check the logs
from 31.03.2016 17:45 h CET onwards.

If you need anything else, please let me know, I am happy to support!

** Attachment added: "20160331_1800.tar.gz"
   
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1500242/+attachment/4618464/+files/20160331_1800.tar.gz

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

Title:
  Bluetooth devices (Jabra BT250, Audi A3 car kit) can not be connected
  with BQ Aquaris 4.5

Status in Canonical System Image:
  In Progress
Status in bluez package in Ubuntu:
  Confirmed
Status in ofono package in Ubuntu:
  Incomplete

Bug description:
  STEPS:
  Requirements: Aquaris E4.5, Jabra BT250 blue tooth handset device (rather old 
one supports blue tooth 1.1 and therefore I thought should be no issue) or Audi 
car kit (A3 2012 model)

  1. Put Jabra BT250 into receiving mode
  2. Phone searches automatically every 15 - 30 seconds for a new blue tooth 
device
  3. Phone finds Jabra BT250 and asks for pairing code
  4. Enter code into phone
  5. Jabra BT250 automatically exits the pairing mode (which is a sign that 
pairing should have worked)
  6. Phone looses connection to Jabra BT250
  7. Manual reconnection via phone works (shows Jabra BT250 as being connected) 
but ignores the device

  Same behaviour with Audi car kit (Audi A3, 2012 model)

  EXPECTED:
  I expect that the blue tooth kits work similar to my Seat Alhambra (also 2012 
model) where the blue tooth pairing etc. works great (except some bugs which 
are already filed).

  ACTUAL:
  No connection to the blue tooth device

  VERSIONS:
  OS-Build-Number: 25
  Ubuntu-Image: 20150825.1

  POSSIBLE ROOT CAUSE:
  Is this issue also solved as soon as bluez5 is implemented? When will this be?

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1500242/+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 1564475] Comment bridged from LTC Bugzilla

--- Comment From thorsten.di...@de.ibm.com 2016-03-31 11:55 EDT---
IMHO a good method would be to set in /etc/default/kdump-tools the default 
values explicitely in KDUMP_CMDLINE , e.g.
KDUMP_CMDLINE="irqpoll maxcpus=1 nousb systemd.unit=kdump-tools.service"
and to change upon every start/restart of kdump-tools the KDUMP_CMDLINE_APPEND 
to
KDUMP_CMDLINE_APPEND="", where the cio_ignore-statement 
can be easily computed by executing 'cio_ignore -k', which creates an 
cio_ignore statement for all enabled ccw devices.

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

Title:
  128M is not enough for kdump on s390 LPARs

Status in makedumpfile package in Ubuntu:
  Invalid

Bug description:
  == Comment: #0 - Michael Holzheu  - 2016-03-31 
10:59:26 ==
  With the current Ubuntu default setting "crashkernel=128M" kdump on LPARs 
crashes with out-of-memory (see attachment "dmesg_lpar_out_of_mem_128M.txt").

  On z/VM guests 128M seems to be sufficient.

  One reason on our test LPAR is that a lot of devices are attached (see
  attachment "lscss_lpar.txt") which are not required for kdump but
  consume a lot of memory because the s390 CIO layer allocates data
  structures in the kernel for those devices.

  We can disable the devices by using the "cio_ignore=" kernel parameter
  in "/etc/default/kdump-tools". For example, on our LPAR that uses DASD
  0.0.e934 for /var/crash, we added the following line to disable the
  devices:

  KDUMP_CMDLINE_APPEND="irqpoll maxcpus=1
  cio_ignore=all,!condev,!0.0.e934"

  For more information on the "cio_ignore=" kernel parameter see:
  https://github.com/torvalds/linux/blob/master/Documentation/s390/CommonIO

  Even with "cio_ignore=" we still get out-of-memory with
  "crashkernel=128M".

  With "crashkernel=196M" and "cio_ignore=" we are able to create a dump
  on our LPAR. We currently do not know why kdump with "cio_ignore=" on
  LPAR consumes more memory than on z/VM guests.

  == Comment: #1 - Michael Holzheu  - 2016-03-31 
11:03:15 ==
  Kernel messages of kdump out-of-memory crash on LPAR with many devices 
without cio_ignore parameter and 128M crashkernel memory.

  == Comment: #2 - Michael Holzheu  - 2016-03-31 
11:04:10 ==
  Output of lscss showing all attached (not online) devices on the LPAR.

  == Comment: #3 - Michael Holzheu  - 2016-03-31 
11:07:35 ==
  To solve this issue our recommendation is:

  1) Increase "crashkernel=" default to 196M on Ubuntu for s390.

  2) Document that KDUMP_CMDLINE_APPEND with "cio_ignore=" can be used
  to decrease memory consumption for kdump on systems with many devices
  that are not required for kdump.

  The most user friendly solution would be to automatically determine
  the required kdump devices and set the correct "cio_ignore=" kernel
  parameter. But this is not trivial, because it can be difficult to
  find out the required devices for stacked setups like LVM or for
  network dump.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1564475/+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 1564463] Missing required logs.

This bug is missing log files that will aid in diagnosing the problem.
>From a terminal window please run:

apport-collect 1564463

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

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

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

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

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

Title:
  Joystick Dragonrise Axes confused in Ubuntu 14.04

Status in linux package in Ubuntu:
  Incomplete
Status in linux package in Debian:
  Unknown

Bug description:
  In Ubuntu 14.04 axis 2 (left-right of the right joystick) is hardly
  working.

  Its conflicting and superimposed by axis 0 (left-right of the left
  joystick)

  Axis 2 was allready behaving bad in eralier versions now its completly
  broken.

  Also jscal complains when applying stored settings from earlier ubuntu
  versions as the joystick now has 6 axes [0-5] and used to have 7, but
  this seems correct.

  The Dragonrise chip seems to be very widespread among different
  speedlink and LinQ models

  There is a related bugreport in Debian Bug-Tracker: 
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=785606
  that makes

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1564463/+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 1564470] Re: Unable to install NI-VISA nikal kernel module because of GPL-only symbol 'pgprot_writecombine'

2016-03-31 Thread Tim Gardner

Commit 92b9af9e4f144535c65aee673cfad309f25fa465 ('x86: i915 needs
pgprot_writecombine() and is_io_mapping_possible()') is where that
symbol is exported. You could send an email to Ingo Molnar
 and see if he is interested in relaxing that export.

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

Title:
  Unable to install NI-VISA nikal kernel module because of GPL-only
  symbol 'pgprot_writecombine'

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Steps to reproduce:
  1. Login to National Instruments site
  2. Download NI-VISA 15.0 for linux (NI-VISA-15.0.0.iso).
  3. Launch its installation by "sudo ./INSTALL"
  4. Get errors on nikal kernel modules compilation about "pgprot_writecombine" 
symbol ("nikal: FATAL: modpost: GPL-incompatible module nikal.ko uses GPL-only 
symbol 'pgprot_writecombine'")

  Temporary solution:
  1. Edit /usr/src/linux-headers-4.4.0-16-generic/Module.symvers
  and change line
 0xd544e902 pgprot_writecombine vmlinux EXPORT_SYMBOL_GPL
  to
 0xd544e902 pgprot_writecombine vmlinux EXPORT_SYMBOL
  2. Edit /boot/abi-4.4.0-16-generic
  and change line 
 EXPORT_SYMBOL_GPL vmlinux 0xd544e902   pgprot_writecombine
  to
 EXPORT_SYMBOL vmlinux 0xd544e902   pgprot_writecombine

  but it does not help - I get "nikal: Unknown symbol
  pgprot_writecombine (err 0)" in syslog.

  Expected results:
  0. The 'pgprot_writecombine' symbol is exported as EXPORT_SYMBOL
  1. Ubuntu can compile and load NI nikal module.

  Actual results:
  Unable to use NI-VISA under Ubuntu.

  Reference (openSUSE):
  
http://forums.ni.com/t5/Instrument-Control-GPIB-Serial/GPL-incompatible-module-nikal-ko/td-p/3218730

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-16-generic 4.4.0-16.32
  ProcVersionSignature: Ubuntu 4.4.0-16.32-generic 4.4.6
  Uname: Linux 4.4.0-16-generic i686
  ApportVersion: 2.20-0ubuntu3
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  flash  1549 F pulseaudio
   /dev/snd/controlC0:  flash  1549 F pulseaudio
  CurrentDesktop: Unity
  Date: Thu Mar 31 18:16:37 2016
  InstallationDate: Installed on 2016-03-26 (4 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Beta i386 (20160323)
  IwConfig:
   lono wireless extensions.

   enp1s0no wireless extensions.
  MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M.
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-16-generic 
root=UUID=eab7b488-5040-499c-afd8-21a7ce9e2383 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-16-generic N/A
   linux-backports-modules-4.4.0-16-generic  N/A
   linux-firmware1.157
  RfKill:

  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/09/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: FD
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: F2A55M-DS2
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrFD:bd01/09/2014:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnF2A55M-DS2:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To be filled by O.E.M.
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1564470/+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 1558905] Re: linux-lts-vivid: 3.19.0-58.64~14.04.1 -proposed tracker

** Description changed:

  This bug is for tracking the 3.19.0-58.64~14.04.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
  kernel-stable-Prepare-package-start:Friday, 18. March 2016 04:01 UTC
  kernel-stable-master-bug:1558701
  -- swm properties --
  phase: Uploaded
  kernel-stable-Prepare-package-end:Wednesday, 23. March 2016 13:57 UTC
  kernel-stable-Promote-to-proposed-end:Wednesday, 23. March 2016 11:57 UTC
  kernel-stable-Promote-to-proposed-start:Wednesday, 23. March 2016 13:57 UTC
  kernel-stable-Verification-testing-start:Wednesday, 23. March 2016 14:03 UTC
  kernel-stable-Certification-testing-start:Wednesday, 23. March 2016 14:03 UTC
  kernel-stable-Security-signoff-start:Wednesday, 23. March 2016 14:03 UTC
  proposed-announcement-sent:True
  kernel-stable-Regression-testing-start:Wednesday, 23. March 2016 14:03 UTC
  kernel-stable-Security-signoff-end:Monday, 28. March 2016 19:01 UTC
  kernel-stable-phase:Testing
  kernel-stable-phase-changed:Tuesday, 29. March 2016 15:01 UTC
  kernel-stable-Verification-testing-end:Tuesday, 29. March 2016 15:01 UTC
  kernel-stable-Regression-testing-end:Tuesday, 29. March 2016 15:01 UTC
+ kernel-stable-Certification-testing-end:Thursday, 31. March 2016 16:01 UTC

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

Title:
  linux-lts-vivid: 3.19.0-58.64~14.04.1 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Fix Released
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux-lts-vivid package in Ubuntu:
  Invalid
Status in linux-lts-vivid source package in Trusty:
  New

Bug description:
  This bug is for tracking the 3.19.0-58.64~14.04.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
  kernel-stable-Prepare-package-start:Friday, 18. March 2016 04:01 UTC
  kernel-stable-master-bug:1558701
  -- swm properties --
  phase: Uploaded
  kernel-stable-Prepare-package-end:Wednesday, 23. March 2016 13:57 UTC
  kernel-stable-Promote-to-proposed-end:Wednesday, 23. March 2016 11:57 UTC
  kernel-stable-Promote-to-proposed-start:Wednesday, 23. March 2016 13:57 UTC
  kernel-stable-Verification-testing-start:Wednesday, 23. March 2016 14:03 UTC
  kernel-stable-Certification-testing-start:Wednesday, 23. March 2016 14:03 UTC
  kernel-stable-Security-signoff-start:Wednesday, 23. March 2016 14:03 UTC
  proposed-announcement-sent:True
  kernel-stable-Regression-testing-start:Wednesday, 23. March 2016 14:03 UTC
  kernel-stable-Security-signoff-end:Monday, 28. March 2016 19:01 UTC
  kernel-stable-phase:Testing
  kernel-stable-phase-changed:Tuesday, 29. March 2016 15:01 UTC
  kernel-stable-Verification-testing-end:Tuesday, 29. March 2016 15:01 UTC
  kernel-stable-Regression-testing-end:Tuesday, 29. March 2016 15:01 UTC
  kernel-stable-Certification-testing-end:Thursday, 31. March 2016 16:01 UTC

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1558905/+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 1564475] Re: 128M is not enough for kdump on s390 LPARs

2016-03-31 Thread Dimitri John Ledkov

I do not want to increase it beyond 128MB by default, as this amount of
memory is reserved by default on all installations big or small. And
there will always be newer kernel (that reserves more memory) or more
devices that require higher values. Adjusting kernel args in
/etc/zipl.conf is well-known and well-documented.

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

Title:
  128M is not enough for kdump on s390 LPARs

Status in makedumpfile package in Ubuntu:
  Invalid

Bug description:
  == Comment: #0 - Michael Holzheu  - 2016-03-31 
10:59:26 ==
  With the current Ubuntu default setting "crashkernel=128M" kdump on LPARs 
crashes with out-of-memory (see attachment "dmesg_lpar_out_of_mem_128M.txt").

  On z/VM guests 128M seems to be sufficient.

  One reason on our test LPAR is that a lot of devices are attached (see
  attachment "lscss_lpar.txt") which are not required for kdump but
  consume a lot of memory because the s390 CIO layer allocates data
  structures in the kernel for those devices.

  We can disable the devices by using the "cio_ignore=" kernel parameter
  in "/etc/default/kdump-tools". For example, on our LPAR that uses DASD
  0.0.e934 for /var/crash, we added the following line to disable the
  devices:

  KDUMP_CMDLINE_APPEND="irqpoll maxcpus=1
  cio_ignore=all,!condev,!0.0.e934"

  For more information on the "cio_ignore=" kernel parameter see:
  https://github.com/torvalds/linux/blob/master/Documentation/s390/CommonIO

  Even with "cio_ignore=" we still get out-of-memory with
  "crashkernel=128M".

  With "crashkernel=196M" and "cio_ignore=" we are able to create a dump
  on our LPAR. We currently do not know why kdump with "cio_ignore=" on
  LPAR consumes more memory than on z/VM guests.

  == Comment: #1 - Michael Holzheu  - 2016-03-31 
11:03:15 ==
  Kernel messages of kdump out-of-memory crash on LPAR with many devices 
without cio_ignore parameter and 128M crashkernel memory.

  == Comment: #2 - Michael Holzheu  - 2016-03-31 
11:04:10 ==
  Output of lscss showing all attached (not online) devices on the LPAR.

  == Comment: #3 - Michael Holzheu  - 2016-03-31 
11:07:35 ==
  To solve this issue our recommendation is:

  1) Increase "crashkernel=" default to 196M on Ubuntu for s390.

  2) Document that KDUMP_CMDLINE_APPEND with "cio_ignore=" can be used
  to decrease memory consumption for kdump on systems with many devices
  that are not required for kdump.

  The most user friendly solution would be to automatically determine
  the required kdump devices and set the correct "cio_ignore=" kernel
  parameter. But this is not trivial, because it can be difficult to
  find out the required devices for stacked setups like LVM or for
  network dump.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1564475/+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 1500242] Re: Bluetooth devices (Jabra BT250, Audi A3 car kit) can not be connected with BQ Aquaris 4.5

2016-03-31 Thread Uranicus

I have also attached a screenshot of the bluetoothctl output (of the
results from 17:54 h - 17:58 h) where you see that the device connects
and disconnects.

** Attachment added: "screenshot20160331_175905629.png"

https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1500242/+attachment/4618465/+files/screenshot20160331_175905629.png

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

Title:
Bluetooth devices (Jabra BT250, Audi A3 car kit) can not be connected
with BQ Aquaris 4.5

Status in Canonical System Image:
In Progress
Status in bluez package in Ubuntu:
Confirmed
Status in ofono package in Ubuntu:
Incomplete

Bug description:
STEPS:
Requirements: Aquaris E4.5, Jabra BT250 blue tooth handset device (rather old
one supports blue tooth 1.1 and therefore I thought should be no issue) or Audi
car kit (A3 2012 model)

1. Put Jabra BT250 into receiving mode
2. Phone searches automatically every 15 - 30 seconds for a new blue tooth
device
3. Phone finds Jabra BT250 and asks for pairing code
4. Enter code into phone
5. Jabra BT250 automatically exits the pairing mode (which is a sign that
pairing should have worked)
6. Phone looses connection to Jabra BT250
7. Manual reconnection via phone works (shows Jabra BT250 as being connected)
but ignores the device

Same behaviour with Audi car kit (Audi A3, 2012 model)

EXPECTED:
I expect that the blue tooth kits work similar to my Seat Alhambra (also 2012
model) where the blue tooth pairing etc. works great (except some bugs which
are already filed).

ACTUAL:
No connection to the blue tooth device

VERSIONS:
OS-Build-Number: 25
Ubuntu-Image: 20150825.1

POSSIBLE ROOT CAUSE:
Is this issue also solved as soon as bluez5 is implemented? When will this be?

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1500242/+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 1564487] [NEW] ISST-LTE:pVM:thymelp2:ubuntu 16.04: cannot analyse vmcore with crash (s390x, ppc64)

You have been subscribed to a public bug:

== Comment: #0 - Ping Tian Han - 2016-03-31 02:19:27 ==
---Problem Description---
With the kexec-tools comes from 
https://bugzilla.linux.ibm.com/show_bug.cgi?id=136588#c58 , we have dumpped a 
vmcore for bug 139815 after quiting from xmon. But when trying to analyse with 
crash:

% sudo crash /usr/lib/debug/boot/vmlinux-4.4.0-15-generic
/var/crash/201603310043/dump.201603310043

crash 7.1.4
Copyright (C) 2002-2015  Red Hat, Inc.
Copyright (C) 2004, 2005, 2006, 2010  IBM Corporation
Copyright (C) 1999-2006  Hewlett-Packard Co
Copyright (C) 2005, 2006, 2011, 2012  Fujitsu Limited
Copyright (C) 2006, 2007  VA Linux Systems Japan K.K.
Copyright (C) 2005, 2011  NEC Corporation
Copyright (C) 1999, 2002, 2007  Silicon Graphics, Inc.
Copyright (C) 1999, 2000, 2001, 2002  Mission Critical Linux, Inc.
This program is free software, covered by the GNU General Public License,
and you are welcome to change it and/or distribute copies of it under
certain conditions.  Enter "help copying" to see the conditions.
This program has absolutely no warranty.  Enter "help warranty" for details.

GNU gdb (GDB) 7.6
Copyright (C) 2013 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later 
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "powerpc64le-unknown-linux-gnu"...

please wait... (gathering module symbol data)
crash: invalid structure member offset: module_num_symtab
   FILE: kernel.c  LINE: 3450  FUNCTION: module_init()

[/usr/bin/crash] error trace: 1008af0c => 10124250 => 10179bd0 =>
10083378

  10083378: (undetermined)
  10179bd0: OFFSET_verify+80
  10124250: module_init+1104
  1008af0c: main_loop+764

%

== Comment: #4 - Hari Krishna Bathini - 2016-03-31 08:20:39 ==
(In reply to comment #2)
> Hi, 
> 
> Crash failing with 4.4+ kernels is a known issue which is fixed by the
> upstream patch 
> 
> commit 6f1f78e33474d00d5f261d7ed9d835c558b34d61
> Author: Dave Anderson 
> Date:   Wed Jan 20 09:56:36 2016 -0500
> 
> Fix for the changes made to the kernel module structure introduced by
> this kernel commit for Linux 4.5 and later kernels:
> 
>   commit 7523e4dc5057e157212b4741abd6256e03404cf1
>   module: use a structure to encapsulate layout.
> 
> Without the patch, the crash session fails during initialization
> with the error message: "crash: invalid structure member offset:
> module_init_text_size".
> (seb...@linux.vnet.ibm.com)
> 

We also need the below upstream patch along with the patch mentioned
above to fix this issue

commit 098cdab16dfa6a85e9dad2cad604dee14ee15f66
Author: Dave Anderson 
Date:   Fri Feb 12 14:32:53 2016 -0500

Fix for the changes made to the kernel module structure introduced by
this kernel commit for Linux 4.5 and later kernels:

  commit 8244062ef1e54502ef55f54cced659913f244c3e
  modules: fix longstanding /proc/kallsyms vs module insertion race.

Without the patch, the crash session fails during initialization
with the error message: "crash: invalid structure member offset:
module_num_symtab".
(ander...@redhat.com)

Thanks
Hari

== Comment: #9 - Hendrik Brueckner - 2016-03-31 11:47:13 ==
Problem also exists on s390x:

** Affects: crash (Ubuntu)
 Importance: Undecided
 Assignee: Taco Screen team (taco-screen-team)
 Status: New


** Tags: architecture-all bugnameltc-139847 severity-high 
targetmilestone-inin1604
-- 
ISST-LTE:pVM:thymelp2:ubuntu 16.04: cannot analyse vmcore with crash (s390x, 
ppc64)
https://bugs.launchpad.net/bugs/1564487
You received this bug notification because you are a member of Kernel Packages, 
which is subscribed to crash in Ubuntu.

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

[Kernel-packages] [Bug 1564463] Re: Joystick Dragonrise Axes confused in Ubuntu 14.04

2016-03-31 Thread Stephen Kitt

** Bug watch added: Debian Bug tracker #785606
   http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=785606

** Also affects: linux (Debian) via
   http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=785606
   Importance: Unknown
   Status: Unknown

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

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

Title:
  Joystick Dragonrise Axes confused in Ubuntu 14.04

Status in linux package in Ubuntu:
  Incomplete
Status in linux package in Debian:
  Unknown

Bug description:
  In Ubuntu 14.04 axis 2 (left-right of the right joystick) is hardly
  working.

  Its conflicting and superimposed by axis 0 (left-right of the left
  joystick)

  Axis 2 was allready behaving bad in eralier versions now its completly
  broken.

  Also jscal complains when applying stored settings from earlier ubuntu
  versions as the joystick now has 6 axes [0-5] and used to have 7, but
  this seems correct.

  The Dragonrise chip seems to be very widespread among different
  speedlink and LinQ models

  There is a related bugreport in Debian Bug-Tracker: 
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=785606
  that makes

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1564463/+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 1564487] Re: ISST-LTE:pVM:thymelp2:ubuntu 16.04: cannot analyse vmcore with crash (s390x, ppc64)

2016-03-31 Thread Kevin W. Rudd

** Package changed: ubuntu => crash (Ubuntu)

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

Title:
  ISST-LTE:pVM:thymelp2:ubuntu 16.04: cannot analyse vmcore with crash
  (s390x, ppc64)

Status in crash package in Ubuntu:
  New

Bug description:
  == Comment: #0 - Ping Tian Han - 2016-03-31 02:19:27 ==
  ---Problem Description---
  With the kexec-tools comes from 
https://bugzilla.linux.ibm.com/show_bug.cgi?id=136588#c58 , we have dumpped a 
vmcore for bug 139815 after quiting from xmon. But when trying to analyse with 
crash:

  % sudo crash /usr/lib/debug/boot/vmlinux-4.4.0-15-generic
  /var/crash/201603310043/dump.201603310043

  crash 7.1.4
  Copyright (C) 2002-2015  Red Hat, Inc.
  Copyright (C) 2004, 2005, 2006, 2010  IBM Corporation
  Copyright (C) 1999-2006  Hewlett-Packard Co
  Copyright (C) 2005, 2006, 2011, 2012  Fujitsu Limited
  Copyright (C) 2006, 2007  VA Linux Systems Japan K.K.
  Copyright (C) 2005, 2011  NEC Corporation
  Copyright (C) 1999, 2002, 2007  Silicon Graphics, Inc.
  Copyright (C) 1999, 2000, 2001, 2002  Mission Critical Linux, Inc.
  This program is free software, covered by the GNU General Public License,
  and you are welcome to change it and/or distribute copies of it under
  certain conditions.  Enter "help copying" to see the conditions.
  This program has absolutely no warranty.  Enter "help warranty" for details.

  GNU gdb (GDB) 7.6
  Copyright (C) 2013 Free Software Foundation, Inc.
  License GPLv3+: GNU GPL version 3 or later 
  This is free software: you are free to change and redistribute it.
  There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
  and "show warranty" for details.
  This GDB was configured as "powerpc64le-unknown-linux-gnu"...

  please wait... (gathering module symbol data)
  crash: invalid structure member offset: module_num_symtab
 FILE: kernel.c  LINE: 3450  FUNCTION: module_init()

  [/usr/bin/crash] error trace: 1008af0c => 10124250 => 10179bd0 =>
  10083378

10083378: (undetermined)
10179bd0: OFFSET_verify+80
10124250: module_init+1104
1008af0c: main_loop+764

  %

  == Comment: #4 - Hari Krishna Bathini - 2016-03-31 08:20:39 ==
  (In reply to comment #2)
  > Hi, 
  > 
  > Crash failing with 4.4+ kernels is a known issue which is fixed by the
  > upstream patch 
  > 
  > commit 6f1f78e33474d00d5f261d7ed9d835c558b34d61
  > Author: Dave Anderson 
  > Date:   Wed Jan 20 09:56:36 2016 -0500
  > 
  > Fix for the changes made to the kernel module structure introduced by
  > this kernel commit for Linux 4.5 and later kernels:
  > 
  >   commit 7523e4dc5057e157212b4741abd6256e03404cf1
  >   module: use a structure to encapsulate layout.
  > 
  > Without the patch, the crash session fails during initialization
  > with the error message: "crash: invalid structure member offset:
  > module_init_text_size".
  > (seb...@linux.vnet.ibm.com)
  > 

  We also need the below upstream patch along with the patch mentioned
  above to fix this issue

  commit 098cdab16dfa6a85e9dad2cad604dee14ee15f66
  Author: Dave Anderson 
  Date:   Fri Feb 12 14:32:53 2016 -0500

  Fix for the changes made to the kernel module structure introduced by
  this kernel commit for Linux 4.5 and later kernels:
  
commit 8244062ef1e54502ef55f54cced659913f244c3e
modules: fix longstanding /proc/kallsyms vs module insertion race.
  
  Without the patch, the crash session fails during initialization
  with the error message: "crash: invalid structure member offset:
  module_num_symtab".
  (ander...@redhat.com)

  Thanks
  Hari

  == Comment: #9 - Hendrik Brueckner - 2016-03-31 11:47:13 ==
  Problem also exists on s390x:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/crash/+bug/1564487/+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 1494350] Re: QEMU: causes vCPU steal time overflow on live migration

2016-03-31 Thread Bug Watch Updater

** Changed in: linux (Debian)
   Status: Unknown => Fix Released

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

Title:
  QEMU: causes vCPU steal time overflow on live migration

Status in Linux:
  Fix Committed
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Trusty:
  In Progress
Status in linux source package in Vivid:
  In Progress
Status in linux source package in Wily:
  In Progress
Status in linux source package in Xenial:
  Fix Released
Status in linux package in Debian:
  Fix Released

Bug description:
  [Impact]
  It is possible to have vcpu->arch.st.last_steal initialized
  from a thread other than vcpu thread, say the main thread, via
  KVM_SET_MSRS. That can cause steal_time overflow later (when subtracting from 
vcpu threads sched_info.run_delay).

  [Test Case]
  Testing Steps with patched trusty kernel:
  Using savemv & loadvm to simulate the migration process.

  In guest:
  1. check steal_time data location
  rdmsr 0x4b564d03 <- returns the start address 0x7fc0d000

  2. exam the steal time before savevm in qemu monitor
  (qemu) xp /ug 0x7fc0d000
  xp /ug 0x7fc0d000
  7fc0d000:144139048 < steal time value before 
savevm
  (qemu) savevm mytestvm7
  savevm mytestvm7
  (qemu) quit
  quit

  3. give some load to the host system, e.g. stress --cpu 

  4. start the guest with "-loadvm mytestvm7" to restore the state of
  the VM, thus the steal_time MSR

  5. exam the steal time value again
  (qemu) xp /ug 0x7fc0d000
  xp /ug 0x7fc0d000
  7fc0d000:147428917 < with high cpu load after 
loadvm, steal time still shows a linear increase

  The steal_time value would go backward (because of the overflow) after
  the restoration of the VM state without the fix.

  -

  I'm pasting in text from Debian Bug 785557
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=785557
  b/c I couldn't find this issue reported.

  It is present in QEMU 2.3, but I haven't tested later versions.
  Perhaps someone else will find this bug and confirm for later
  versions.  (Or I will when I have time!)

  


  Hi,

  I'm trying to debug an issue we're having with some debian.org machines
  running in QEMU 2.1.2 instances (see [1] for more background). In short,
  after a live migration guests running Debian Jessie (linux 3.16) stop
  accounting CPU time properly. /proc/stat in the guest shows no increase
  in user and system time anymore (regardless of workload) and what stands
  out are extremely large values for steal time:

   % cat /proc/stat
   cpu  2400 0 1842 650879168 2579640 0 25 136562317270 0 0
   cpu0 1366 0 1028 161392988 1238598 0 11 383803090749 0 0
   cpu1 294 0 240 162582008 639105 0 8 39686436048 0 0
   cpu2 406 0 338 163331066 383867 0 4 333994238765 0 0
   cpu3 332 0 235 163573105 318069 0 1 1223752959076 0 0
   intr 355773871 33 10 0 0 0 0 3 0 1 0 0 36 144 0 0 1638612 0 0 0 0 0 0 0 0 0 0
  0 0 0 0 0 0 0 0 0 0 0 0 0 0 5 5001741 41 0 8516993 0 3669582 0 0 0 0 0 0 0 0 0
  0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
  0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
  0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
  0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
  0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
  0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
  0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
  0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
  0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
  0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
  0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
  0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
  0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
  0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
  0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
  0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
  0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
   ctxt 837862829
   btime 1431642967
   processes 8529939
   procs_running 1
   procs_blocked 0
   softirq 225193331 2 77532878 172 7250024 819289 0 54 33739135 176552 
105675225

  Reading the memory pointed to by the steal time MSRs pre- and
  post-migration, I can see that post-migration the high bytes are set to
  0xff:

[Kernel-packages] [Bug 1564470] Re: Unable to install NI-VISA nikal kernel module because of GPL-only symbol 'pgprot_writecombine'

** Description changed:

  Steps to reproduce:
  1. Login to National Instruments site
  2. Download NI-VISA 15.0 for linux (NI-VISA-15.0.0.iso).
  3. Launch its installation by "sudo ./INSTALL"
  4. Get errors on nikal kernel modules compilation about "pgprot_writecombine" 
symbol ("nikal: FATAL: modpost: GPL-incompatible module nikal.ko uses GPL-only 
symbol 'pgprot_writecombine'")
  
  Temporary solution:
  1. Edit /usr/src/linux-headers-4.4.0-16-generic/Module.symvers
  and change line
- 0xd544e902pgprot_writecombine vmlinux EXPORT_SYMBOL_GPL
+0xd544e902 pgprot_writecombine vmlinux EXPORT_SYMBOL_GPL
  to
- 0xd544e902pgprot_writecombine vmlinux EXPORT_SYMBOL
- 2. Edit /boot/
+0xd544e902 pgprot_writecombine vmlinux EXPORT_SYMBOL
+ 2. Edit /boot/abi-4.4.0-16-generic
+ and change line 
+EXPORT_SYMBOL_GPL vmlinux 0xd544e902   pgprot_writecombine
+ to
+EXPORT_SYMBOL vmlinux 0xd544e902   pgprot_writecombine
+ 
+ but it does not help - I get "nikal: Unknown symbol pgprot_writecombine
+ (err 0)" in syslog.
  
  Expected results:
  0. The 'pgprot_writecombine' symbol is exported as EXPORT_SYMBOL
  1. Ubuntu can compile and load NI nikal module.
  
  Actual results:
  Unable to use NI-VISA under Ubuntu.
  
  Reference (openSUSE):
  
http://forums.ni.com/t5/Instrument-Control-GPIB-Serial/GPL-incompatible-module-nikal-ko/td-p/3218730
  
  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-16-generic 4.4.0-16.32
  ProcVersionSignature: Ubuntu 4.4.0-16.32-generic 4.4.6
  Uname: Linux 4.4.0-16-generic i686
  ApportVersion: 2.20-0ubuntu3
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  flash  1549 F pulseaudio
   /dev/snd/controlC0:  flash  1549 F pulseaudio
  CurrentDesktop: Unity
  Date: Thu Mar 31 18:16:37 2016
  InstallationDate: Installed on 2016-03-26 (4 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Beta i386 (20160323)
  IwConfig:
   lono wireless extensions.
  
   enp1s0no wireless extensions.
  MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M.
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-16-generic 
root=UUID=eab7b488-5040-499c-afd8-21a7ce9e2383 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-16-generic N/A
   linux-backports-modules-4.4.0-16-generic  N/A
   linux-firmware1.157
  RfKill:
  
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/09/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: FD
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: F2A55M-DS2
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrFD:bd01/09/2014:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnF2A55M-DS2:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To be filled by O.E.M.
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

Title:
  Unable to install NI-VISA nikal kernel module because of GPL-only
  symbol 'pgprot_writecombine'

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Steps to reproduce:
  1. Login to National Instruments site
  2. Download NI-VISA 15.0 for linux (NI-VISA-15.0.0.iso).
  3. Launch its installation by "sudo ./INSTALL"
  4. Get errors on nikal kernel modules compilation about "pgprot_writecombine" 
symbol ("nikal: FATAL: modpost: GPL-incompatible module nikal.ko uses GPL-only 
symbol 'pgprot_writecombine'")

  Temporary solution:
  1. Edit /usr/src/linux-headers-4.4.0-16-generic/Module.symvers
  and change line
 0xd544e902 pgprot_writecombine vmlinux EXPORT_SYMBOL_GPL
  to
 0xd544e902 pgprot_writecombine vmlinux EXPORT_SYMBOL
  2. Edit /boot/abi-4.4.0-16-generic
  and change line 
 EXPORT_SYMBOL_GPL vmlinux 0xd544e902   pgprot_writecombine
  to
 EXPORT_SYMBOL vmlinux 0xd544e902   pgprot_writecombine

  but it does not help - I get "nikal: Unknown symbol
  pgprot_writecombine (err 0)" in syslog.

  Expected results:
  0. The 'pgprot_writecombine' symbol is exported as EXPORT_SYMBOL
  1. Ubuntu can compile and load NI nikal module.

  Actual results:
  Unable to use NI-VISA under Ubuntu.

  Reference (openSUSE):
  
http://forums.ni.com/t5/Instrument-Control-GPIB-Serial/GPL-incompatible-module-nikal-ko/td-p/3218730

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04

[Kernel-packages] [Bug 1558905] Re: linux-lts-vivid: 3.19.0-58.64~14.04.1 -proposed tracker

2016-03-31 Thread Taihsiang Ho

Hardware Certification have completed testing this -proposed kernel. No
regressions were observed, results are available here:
http://people.canonical.com/~hwcert/sru-
testing/trusty/3.19.0-58.64~14.04.1/trusty-3.19-proposed.html

** Tags added: certification-testing-passed

** Changed in: kernel-sru-workflow/certification-testing
   Status: In Progress => Fix Released

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

Title:
  linux-lts-vivid: 3.19.0-58.64~14.04.1 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Fix Released
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux-lts-vivid package in Ubuntu:
  Invalid
Status in linux-lts-vivid source package in Trusty:
  New

Bug description:
  This bug is for tracking the 3.19.0-58.64~14.04.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
  kernel-stable-Prepare-package-start:Friday, 18. March 2016 04:01 UTC
  kernel-stable-master-bug:1558701
  -- swm properties --
  phase: Uploaded
  kernel-stable-Prepare-package-end:Wednesday, 23. March 2016 13:57 UTC
  kernel-stable-Promote-to-proposed-end:Wednesday, 23. March 2016 11:57 UTC
  kernel-stable-Promote-to-proposed-start:Wednesday, 23. March 2016 13:57 UTC
  kernel-stable-Verification-testing-start:Wednesday, 23. March 2016 14:03 UTC
  kernel-stable-Certification-testing-start:Wednesday, 23. March 2016 14:03 UTC
  kernel-stable-Security-signoff-start:Wednesday, 23. March 2016 14:03 UTC
  proposed-announcement-sent:True
  kernel-stable-Regression-testing-start:Wednesday, 23. March 2016 14:03 UTC
  kernel-stable-Security-signoff-end:Monday, 28. March 2016 19:01 UTC
  kernel-stable-phase:Testing
  kernel-stable-phase-changed:Tuesday, 29. March 2016 15:01 UTC
  kernel-stable-Verification-testing-end:Tuesday, 29. March 2016 15:01 UTC
  kernel-stable-Regression-testing-end:Tuesday, 29. March 2016 15:01 UTC

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1558905/+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 1564475] Re: 128M is not enough for kdump on s390 LPARs

2016-03-31 Thread Gary Gaydos

** Package changed: ubuntu => makedumpfile (Ubuntu)

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

Title:
  128M is not enough for kdump on s390 LPARs

Status in makedumpfile package in Ubuntu:
  New

Bug description:
  == Comment: #0 - Michael Holzheu  - 2016-03-31 
10:59:26 ==
  With the current Ubuntu default setting "crashkernel=128M" kdump on LPARs 
crashes with out-of-memory (see attachment "dmesg_lpar_out_of_mem_128M.txt").

  On z/VM guests 128M seems to be sufficient.

  One reason on our test LPAR is that a lot of devices are attached (see
  attachment "lscss_lpar.txt") which are not required for kdump but
  consume a lot of memory because the s390 CIO layer allocates data
  structures in the kernel for those devices.

  We can disable the devices by using the "cio_ignore=" kernel parameter
  in "/etc/default/kdump-tools". For example, on our LPAR that uses DASD
  0.0.e934 for /var/crash, we added the following line to disable the
  devices:

  KDUMP_CMDLINE_APPEND="irqpoll maxcpus=1
  cio_ignore=all,!condev,!0.0.e934"

  For more information on the "cio_ignore=" kernel parameter see:
  https://github.com/torvalds/linux/blob/master/Documentation/s390/CommonIO

  Even with "cio_ignore=" we still get out-of-memory with
  "crashkernel=128M".

  With "crashkernel=196M" and "cio_ignore=" we are able to create a dump
  on our LPAR. We currently do not know why kdump with "cio_ignore=" on
  LPAR consumes more memory than on z/VM guests.

  == Comment: #1 - Michael Holzheu  - 2016-03-31 
11:03:15 ==
  Kernel messages of kdump out-of-memory crash on LPAR with many devices 
without cio_ignore parameter and 128M crashkernel memory.

  == Comment: #2 - Michael Holzheu  - 2016-03-31 
11:04:10 ==
  Output of lscss showing all attached (not online) devices on the LPAR.

  == Comment: #3 - Michael Holzheu  - 2016-03-31 
11:07:35 ==
  To solve this issue our recommendation is:

  1) Increase "crashkernel=" default to 196M on Ubuntu for s390.

  2) Document that KDUMP_CMDLINE_APPEND with "cio_ignore=" can be used
  to decrease memory consumption for kdump on systems with many devices
  that are not required for kdump.

  The most user friendly solution would be to automatically determine
  the required kdump devices and set the correct "cio_ignore=" kernel
  parameter. But this is not trivial, because it can be difficult to
  find out the required devices for stacked setups like LVM or for
  network dump.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1564475/+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 1564463] [NEW] Joystick Dragonrise Axes confused in Ubuntu 14.04

You have been subscribed to a public bug:

In Ubuntu 14.04 axis 2 (left-right of the right joystick) is hardly
working.

Its conflicting and superimposed by axis 0 (left-right of the left
joystick)

Axis 2 was allready behaving bad in eralier versions now its completly
broken.

Also jscal complains when applying stored settings from earlier ubuntu
versions as the joystick now has 6 axes [0-5] and used to have 7, but
this seems correct.

The Dragonrise chip seems to be very widespread among different
speedlink and LinQ models

There is a related bugreport in Debian Bug-Tracker: 
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=785606
that makes

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

** Affects: linux (Debian)
 Importance: Unknown
 Status: Unknown

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

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

[Kernel-packages] [Bug 1564475] [NEW] 128M is not enough for kdump on s390 LPARs

You have been subscribed to a public bug:

== Comment: #0 - Michael Holzheu  - 2016-03-31 
10:59:26 ==
With the current Ubuntu default setting "crashkernel=128M" kdump on LPARs 
crashes with out-of-memory (see attachment "dmesg_lpar_out_of_mem_128M.txt").

On z/VM guests 128M seems to be sufficient.

One reason on our test LPAR is that a lot of devices are attached (see
attachment "lscss_lpar.txt") which are not required for kdump but
consume a lot of memory because the s390 CIO layer allocates data
structures in the kernel for those devices.

We can disable the devices by using the "cio_ignore=" kernel parameter
in "/etc/default/kdump-tools". For example, on our LPAR that uses DASD
0.0.e934 for /var/crash, we added the following line to disable the
devices:

KDUMP_CMDLINE_APPEND="irqpoll maxcpus=1
cio_ignore=all,!condev,!0.0.e934"

For more information on the "cio_ignore=" kernel parameter see:
https://github.com/torvalds/linux/blob/master/Documentation/s390/CommonIO

Even with "cio_ignore=" we still get out-of-memory with
"crashkernel=128M".

With "crashkernel=196M" and "cio_ignore=" we are able to create a dump
on our LPAR. We currently do not know why kdump with "cio_ignore=" on
LPAR consumes more memory than on z/VM guests.

== Comment: #1 - Michael Holzheu  - 2016-03-31 
11:03:15 ==
Kernel messages of kdump out-of-memory crash on LPAR with many devices without 
cio_ignore parameter and 128M crashkernel memory.

== Comment: #2 - Michael Holzheu  - 2016-03-31 
11:04:10 ==
Output of lscss showing all attached (not online) devices on the LPAR.

== Comment: #3 - Michael Holzheu  - 2016-03-31 
11:07:35 ==
To solve this issue our recommendation is:

1) Increase "crashkernel=" default to 196M on Ubuntu for s390.

2) Document that KDUMP_CMDLINE_APPEND with "cio_ignore=" can be used to
decrease memory consumption for kdump on systems with many devices that
are not required for kdump.

The most user friendly solution would be to automatically determine the
required kdump devices and set the correct "cio_ignore=" kernel
parameter. But this is not trivial, because it can be difficult to find
out the required devices for stacked setups like LVM or for network
dump.

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


** Tags: architecture-s39064 bugnameltc-139866 severity-critical 
targetmilestone-inin---
-- 
128M is not enough for kdump on s390 LPARs
https://bugs.launchpad.net/bugs/1564475
You received this bug notification because you are a member of Kernel Packages, 
which is subscribed to makedumpfile in Ubuntu.

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

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

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

Title:
  Unable to install NI-VISA nikal kernel module because of GPL-only
  symbol 'pgprot_writecombine'

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Steps to reproduce:
  1. Login to National Instruments site
  2. Download NI-VISA 15.0 for linux (NI-VISA-15.0.0.iso).
  3. Launch its installation by "sudo ./INSTALL"
  4. Get errors on nikal kernel modules compilation about "pgprot_writecombine" 
symbol ("nikal: FATAL: modpost: GPL-incompatible module nikal.ko uses GPL-only 
symbol 'pgprot_writecombine'")

  Temporary solution:
  1. Edit /usr/src/linux-headers-4.4.0-16-generic/Module.symvers
  and change line
  0xd544e902pgprot_writecombine vmlinux EXPORT_SYMBOL_GPL
  to
  0xd544e902pgprot_writecombine vmlinux EXPORT_SYMBOL
  2. Edit /boot/

  Expected results:
  0. The 'pgprot_writecombine' symbol is exported as EXPORT_SYMBOL
  1. Ubuntu can compile and load NI nikal module.

  Actual results:
  Unable to use NI-VISA under Ubuntu.

  Reference (openSUSE):
  
http://forums.ni.com/t5/Instrument-Control-GPIB-Serial/GPL-incompatible-module-nikal-ko/td-p/3218730

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-16-generic 4.4.0-16.32
  ProcVersionSignature: Ubuntu 4.4.0-16.32-generic 4.4.6
  Uname: Linux 4.4.0-16-generic i686
  ApportVersion: 2.20-0ubuntu3
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  flash  1549 F pulseaudio
   /dev/snd/controlC0:  flash  1549 F pulseaudio
  CurrentDesktop: Unity
  Date: Thu Mar 31 18:16:37 2016
  InstallationDate: Installed on 2016-03-26 (4 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Beta i386 (20160323)
  IwConfig:
   lono wireless extensions.

   enp1s0no wireless extensions.
  MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M.
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-16-generic 
root=UUID=eab7b488-5040-499c-afd8-21a7ce9e2383 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-16-generic N/A
   linux-backports-modules-4.4.0-16-generic  N/A
   linux-firmware1.157
  RfKill:

  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/09/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: FD
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: F2A55M-DS2
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrFD:bd01/09/2014:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnF2A55M-DS2:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To be filled by O.E.M.
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1564470/+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 1564470] [NEW] Unable to install NI-VISA nikal kernel module because of GPL-only symbol 'pgprot_writecombine'

Public bug reported:

Steps to reproduce:
1. Login to National Instruments site
2. Download NI-VISA 15.0 for linux (NI-VISA-15.0.0.iso).
3. Launch its installation by "sudo ./INSTALL"
4. Get errors on nikal kernel modules compilation about "pgprot_writecombine" 
symbol ("nikal: FATAL: modpost: GPL-incompatible module nikal.ko uses GPL-only 
symbol 'pgprot_writecombine'")

Temporary solution:
1. Edit /usr/src/linux-headers-4.4.0-16-generic/Module.symvers
and change line
0xd544e902  pgprot_writecombine vmlinux EXPORT_SYMBOL_GPL
to
0xd544e902  pgprot_writecombine vmlinux EXPORT_SYMBOL
2. Edit /boot/

Expected results:
0. The 'pgprot_writecombine' symbol is exported as EXPORT_SYMBOL
1. Ubuntu can compile and load NI nikal module.

Actual results:
Unable to use NI-VISA under Ubuntu.

Reference (openSUSE):
http://forums.ni.com/t5/Instrument-Control-GPIB-Serial/GPL-incompatible-module-nikal-ko/td-p/3218730

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: linux-image-4.4.0-16-generic 4.4.0-16.32
ProcVersionSignature: Ubuntu 4.4.0-16.32-generic 4.4.6
Uname: Linux 4.4.0-16-generic i686
ApportVersion: 2.20-0ubuntu3
Architecture: i386
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  flash  1549 F pulseaudio
 /dev/snd/controlC0:  flash  1549 F pulseaudio
CurrentDesktop: Unity
Date: Thu Mar 31 18:16:37 2016
InstallationDate: Installed on 2016-03-26 (4 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Beta i386 (20160323)
IwConfig:
 lono wireless extensions.

 enp1s0no wireless extensions.
MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M.
ProcFB: 0 radeondrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-16-generic 
root=UUID=eab7b488-5040-499c-afd8-21a7ce9e2383 ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-4.4.0-16-generic N/A
 linux-backports-modules-4.4.0-16-generic  N/A
 linux-firmware1.157
RfKill:

SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 01/09/2014
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: FD
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: F2A55M-DS2
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: x.x
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrFD:bd01/09/2014:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnF2A55M-DS2:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.name: To be filled by O.E.M.
dmi.product.version: To be filled by O.E.M.
dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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


** Tags: apport-bug xenial

** Description changed:

  Steps to reproduce:
  1. Login to National Instruments site
  2. Download NI-VISA 15.0 for linux (NI-VISA-15.0.0.iso).
  3. Launch its installation by "sudo ./INSTALL"
  4. Get errors on nikal kernel modules compilation about "pgprot_writecombine" 
symbol ("nikal: FATAL: modpost: GPL-incompatible module nikal.ko uses GPL-only 
symbol 'pgprot_writecombine'")
  
  Temporary solution:
  1. Edit /usr/src/linux-headers-4.4.0-16-generic/Module.symvers
  and change line
  0xd544e902pgprot_writecombine vmlinux EXPORT_SYMBOL_GPL
  to
  0xd544e902pgprot_writecombine vmlinux EXPORT_SYMBOL
  2. Edit /boot/
  
  Expected results:
  0. The 'pgprot_writecombine' symbol is exported as EXPORT_SYMBOL
  1. Ubuntu can compile and load NI nikal module.
  
  Actual results:
  Unable to use NI-VISA under Ubuntu.
  
+ Reference (openSUSE):
+ 
http://forums.ni.com/t5/Instrument-Control-GPIB-Serial/GPL-incompatible-module-nikal-ko/td-p/3218730
+ 
  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-16-generic 4.4.0-16.32
  ProcVersionSignature: Ubuntu 4.4.0-16.32-generic 4.4.6
  Uname: Linux 4.4.0-16-generic i686
  ApportVersion: 2.20-0ubuntu3
  Architecture: i386
  AudioDevicesInUse:
-  USERPID ACCESS COMMAND
-  /dev/snd/controlC1:  flash  1549 F pulseaudio
-  /dev/snd/controlC0:  flash  1549 F pulseaudio
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC1:  flash  1549 F pulseaudio
+  /dev/snd/controlC0:  flash  1549 F pulseaudio
  CurrentDesktop: Unity
  Date: Thu Mar 31 18:16:37 2016
  InstallationDate: Installed on 2016-03-26 (4 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Beta i386 (20160323)
  IwConfig:
-  lono wireless extensions.
-  
-  enp1s0no wireless extensions.
+  lono wireless extensions.
+ 
+  enp1s0no wireless extensions.
  MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M.
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine:

[Kernel-packages] [Bug 1564217] Re: Hot add of a disk attached to LSI Logic SAS is not getting detected

2016-03-31 Thread Tim Gardner

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

** Also affects: linux via
   http://bugzilla.kernel.org/show_bug.cgi?id=114611
   Importance: Unknown
   Status: Unknown

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

Title:
  Hot add of a disk attached to LSI Logic SAS is not getting detected

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

Bug description:
  when install VM ubuntu 16.04 beta1 image in VMware ESXi,  Hot add of
  a disk attached to LSI Logic SAS is not getting detected

  Steps to reproduce:
  1.Install ubuntu 16.04 beta1 with BUS logic SAS as boot controller in VMware 
ESXi 6.0GA.
  2.Power on the VM
  3.Hot add a hard disk to LSI SAS controller, the ubuntu 16.04 does not detect 
the disk

  the developer from VMware company investigate it and find it's a kernel issue.
  Bug 114611(https://bugzilla.kernel.org/show_bug.cgi?id=114611) is tracking it 
and now have fix for it.

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1564217/+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 1506050] Re: intel cpu frequency is stuck at ~400mhz

2016-03-31 Thread Chris Ng

According to that bug report, thi was fixed in thermald 1.4.3-5~14.04.2.
I have that installed, and microcode 0x36 and frequency scaling appears
to be working correctly.

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

Title:
  intel cpu frequency is stuck at ~400mhz

Status in linux-lts-vivid package in Ubuntu:
  Invalid

Bug description:
  I upgraded an install of 14.0.4.3 to the LST Enablement Stack for
  Vivid (kernel 3.19) that is running on a Xeon E5-1630 V3 (a Haswell
  Quad-Core) .  Booting with 3.19 would result in the system being very
  sluggish.  'cpupower frequency-info' would report that the CPU was
  running at around 400mhz, as would 'cat
  /sys/devices/system/cpu/cpu*/cpufreq/scaling_cur_freq'.  The CPUs
  would remain around 400mhz regardless of load.

  This was using the intel_pstate driver and the powersave governor.
  Switching to the performance governor had no effect.  Using the acpi-
  cpufreq driver also had no effect, the system was still sluggish even
  though the reported frequencies in /sys/devices/.

  Eventually I tracked it down to the original install having had the
  intel_microcode package installed at some point.  Once I removed this
  then the CPU frequencies scaled correctly with load.  FYI the
  particular version installed was intel-microcode/trusty-updates,now
  2.20140624-t-1ubuntu2 amd64.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.19.0-30-generic 3.19.0-30.34~14.04.1
  ProcVersionSignature: Ubuntu 3.19.0-30.34~14.04.1-generic 3.19.8-ckt6
  Uname: Linux 3.19.0-30-generic x86_64
  NonfreeKernelModules: nvidia zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.14.1-0ubuntu3.15
  Architecture: amd64
  Date: Wed Oct 14 12:38:05 2015
  InstallationDate: Installed on 2014-08-05 (434 days ago)
  InstallationMedia: Lubuntu 14.04 LTS "Trusty Tahr" - Release amd64 
(20140416.2)
  SourcePackage: linux-lts-vivid
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-lts-vivid/+bug/1506050/+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 1511534] Re: [Hyper-V] Fibre Channel multipath error message

2016-03-31 Thread Chris Valean

While having a second look at this I can conclude that the messages from 
device-mapper are due to a device that is not a multipath target, in which case 
it should be blacklisted in the multipath config file.
This will make multipath to not map them, and using this we were able to no 
longer see the error messages.
I was able to verify this on a 15.04 with upstream.

Ignoring local disks from multipath is also detailed here:
https://help.ubuntu.com/lts/serverguide/multipath-setting-up-dm-
multipath.html

Given this and the fact that this didn't pose any issues from the
initial report, we can close this issue.

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

Title:
  [Hyper-V] Fibre Channel multipath error message

Status in linux package in Ubuntu:
  Triaged
Status in linux source package in Wily:
  Triaged
Status in linux source package in Xenial:
  Triaged

Bug description:
  Problem statement:
  Wily (and probably other previous releases with the updated kernels) return a 
multipath error for vFC (virtual Fibre Channel).

  Symptoms:
  The following messages are in the dmesg log during booting:
  device-mapper: table: 252:4: multipath: error getting device
  device-mapper: IOCtl: error adding target to table

  After logging in, run the command: multipath -ll

  The multipath command does not return any errors, and no new messages
  are added to the dmesg log or syslog after running the multipath
  command.

  
  Steps to repro
  
  Tested with the released Wily (15.10), kernel 4.2.0-16-generic.

   1. Create a Wily VM.
   2. Boot and install the multipath-tools package.
   3. Shutdown and attach a Virtual Fiber Channel adapter and connect it to a 
virtual SAN.
  Note: The host must have a Fiber Channel adapter. Use Hyper-V managers 
Virtual SAN Manager to create a Virtual Fiber Channel Storage Area Network.
   4. Boot the VM.
   5. Issue the following command to see any errors were reported during the 
boot.
  dmesg | grep -i error
  You should see the following two error:
  device-mapper: table: 252:4: multipath: error getting device
  device-mapper: IOCtl: error adding target to table

  Otherwise, the vFC disks are usable and show no issues at a use test
  case.

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

apport information

** Attachment added: "ProcCpuinfo.txt"
   
https://bugs.launchpad.net/bugs/1564423/+attachment/4618355/+files/ProcCpuinfo.txt

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

Title:
  Touchpad not recognized

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Hi, my Acer E3-111 stopped recognizing the touchpad.  External mouse works; 
the machine seems not to recognize the hardware.  Even the system settings only 
shows me mouse settings.  Attaching dmesg and devices.
  The problem started about a week ago after installing an update and rebooting.
  Thanks!
  Andrea

  $ cat /proc/version_signature
  Ubuntu 3.19.0-56.62~14.04.1-generic 3.19.8-ckt15

  $ cat /proc/bus/input/devices
  I: Bus=0019 Vendor= Product=0001 Version=
  N: Name="Power Button"
  P: Phys=PNP0C0C/button/input0
  S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input0
  U: Uniq=
  H: Handlers=kbd event0 
  B: PROP=0
  B: EV=3
  B: KEY=10 0

  I: Bus=0019 Vendor= Product=0003 Version=
  N: Name="Sleep Button"
  P: Phys=PNP0C0E/button/input0
  S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0E:00/input/input1
  U: Uniq=
  H: Handlers=kbd event1 
  B: PROP=0
  B: EV=3
  B: KEY=4000 0 0

  I: Bus=0019 Vendor= Product=0005 Version=
  N: Name="Lid Switch"
  P: Phys=PNP0C0D/button/input0
  S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0D:00/input/input2
  U: Uniq=
  H: Handlers=event2 
  B: PROP=0
  B: EV=21
  B: SW=1

  I: Bus=0019 Vendor= Product=0001 Version=
  N: Name="Power Button"
  P: Phys=LNXPWRBN/button/input0
  S: Sysfs=/devices/LNXSYSTM:00/LNXPWRBN:00/input/input3
  U: Uniq=
  H: Handlers=kbd event3 
  B: PROP=0
  B: EV=3
  B: KEY=10 0

  I: Bus=0011 Vendor=0001 Product=0001 Version=ab41
  N: Name="AT Translated Set 2 keyboard"
  P: Phys=isa0060/serio0/input0
  S: Sysfs=/devices/platform/i8042/serio0/input/input4
  U: Uniq=
  H: Handlers=sysrq kbd event4 
  B: PROP=0
  B: EV=120013
  B: KEY=1 c0200 0 0 700f0203 3802078f870f401 febfffdfffef 
fffe
  B: MSC=10
  B: LED=7

  I: Bus=0019 Vendor= Product=0006 Version=
  N: Name="Video Bus"
  P: Phys=LNXVIDEO/video/input0
  S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/LNXVIDEO:01/input/input5
  U: Uniq=
  H: Handlers=kbd event5 
  B: PROP=0
  B: EV=3
  B: KEY=3e000b 0 0 0

  I: Bus=0003 Vendor=045e Product=07b2 Version=0111
  N: Name="Microsoft Microsoft® Nano Transceiver v1.0"
  P: Phys=usb-:00:14.0-2.3/input0
  S: 
Sysfs=/devices/pci:00/:00:14.0/usb1/1-2/1-2.3/1-2.3:1.0/0003:045E:07B2.0001/input/input6
  U: Uniq=
  H: Handlers=sysrq kbd event6 
  B: PROP=0
  B: EV=120013
  B: KEY=10007 ff8007ff febeffdff3cf fffe
  B: MSC=10
  B: LED=7

  I: Bus=0003 Vendor=045e Product=07b2 Version=0111
  N: Name="Microsoft Microsoft® Nano Transceiver v1.0"
  P: Phys=usb-:00:14.0-2.3/input1
  S: 
Sysfs=/devices/pci:00/:00:14.0/usb1/1-2/1-2.3/1-2.3:1.1/0003:045E:07B2.0002/input/input7
  U: Uniq=
  H: Handlers=mouse0 event7 
  B: PROP=0
  B: EV=17
  B: KEY=1f 0 0 0 0
  B: REL=1c3
  B: MSC=10

  I: Bus=0003 Vendor=045e Product=07b2 Version=0111
  N: Name="Microsoft Microsoft® Nano Transceiver v1.0"
  P: Phys=usb-:00:14.0-2.3/input2
  S: 
Sysfs=/devices/pci:00/:00:14.0/usb1/1-2/1-2.3/1-2.3:1.2/0003:045E:07B2.0003/input/input8
  U: Uniq=
  H: Handlers=sysrq kbd event8 js0 
  B: PROP=0
  B: EV=10001f
  B: KEY=3f0003007f 0 0 4c317aff32d bf544456 c01 
130f938b17c007 7bfad951dfff febeffdfffef fffe
  B: REL=40
  B: ABS=ff01000701ff
  B: MSC=10

  I: Bus=0019 Vendor= Product= Version=
  N: Name="Acer WMI hotkeys"
  P: Phys=wmi/input0
  S: Sysfs=/devices/virtual/input/input9
  U: Uniq=
  H: Handlers=rfkill kbd event9 
  B: PROP=0
  B: EV=13
  B: KEY=1c 0 0 0 0 160080c00 30 0 0
  B: MSC=10

  I: Bus=0019 Vendor= Product= Version=
  N: Name="Acer BMA150 accelerometer"
  P: Phys=wmi/input1
  S: Sysfs=/devices/virtual/input/input10
  U: Uniq=
  H: Handlers=event10 js1 
  B: PROP=0
  B: EV=9
  B: ABS=7

  I: Bus= Vendor= Product= Version=
  N: Name="HDA Intel PCH Headphone"
  P: Phys=ALSA
  S: Sysfs=/devices/pci:00/:00:1b.0/sound/card0/input11
  U: Uniq=
  H: Handlers=event11 
  B: PROP=0
  B: EV=21
  B: SW=4

  I: Bus= Vendor= Product= Version=
  N: Name="HDA Intel PCH HDMI/DP,pcm=3"
  P: Phys=ALSA
  S: Sysfs=/devices/pci:00/:00:1b.0/sound/card0/input12
  U: Uniq=
  H: Handlers=event12 
  B: PROP=0
  B: EV=21
  B: SW=140

  I: Bus=0003 Vendor=04f2 Product=b47f Version=4051
  N: Name="VGA Webcam"
  P: Phys=usb-:00:14.0-4/button
  S: Sysfs=/devices/pci:00/:00:14.0/usb1/1-4/1-4:1.0/input/input13
  U: Uniq=
  H: Handlers=kbd event13 
  B:

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

apport information

** Attachment added: "UdevLog.txt"
   
https://bugs.launchpad.net/bugs/1564423/+attachment/4618362/+files/UdevLog.txt

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

Title:
  Touchpad not recognized

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Hi, my Acer E3-111 stopped recognizing the touchpad.  External mouse works; 
the machine seems not to recognize the hardware.  Even the system settings only 
shows me mouse settings.  Attaching dmesg and devices.
  The problem started about a week ago after installing an update and rebooting.
  Thanks!
  Andrea

  $ cat /proc/version_signature
  Ubuntu 3.19.0-56.62~14.04.1-generic 3.19.8-ckt15

  $ cat /proc/bus/input/devices
  I: Bus=0019 Vendor= Product=0001 Version=
  N: Name="Power Button"
  P: Phys=PNP0C0C/button/input0
  S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input0
  U: Uniq=
  H: Handlers=kbd event0 
  B: PROP=0
  B: EV=3
  B: KEY=10 0

  I: Bus=0019 Vendor= Product=0003 Version=
  N: Name="Sleep Button"
  P: Phys=PNP0C0E/button/input0
  S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0E:00/input/input1
  U: Uniq=
  H: Handlers=kbd event1 
  B: PROP=0
  B: EV=3
  B: KEY=4000 0 0

  I: Bus=0019 Vendor= Product=0005 Version=
  N: Name="Lid Switch"
  P: Phys=PNP0C0D/button/input0
  S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0D:00/input/input2
  U: Uniq=
  H: Handlers=event2 
  B: PROP=0
  B: EV=21
  B: SW=1

  I: Bus=0019 Vendor= Product=0001 Version=
  N: Name="Power Button"
  P: Phys=LNXPWRBN/button/input0
  S: Sysfs=/devices/LNXSYSTM:00/LNXPWRBN:00/input/input3
  U: Uniq=
  H: Handlers=kbd event3 
  B: PROP=0
  B: EV=3
  B: KEY=10 0

  I: Bus=0011 Vendor=0001 Product=0001 Version=ab41
  N: Name="AT Translated Set 2 keyboard"
  P: Phys=isa0060/serio0/input0
  S: Sysfs=/devices/platform/i8042/serio0/input/input4
  U: Uniq=
  H: Handlers=sysrq kbd event4 
  B: PROP=0
  B: EV=120013
  B: KEY=1 c0200 0 0 700f0203 3802078f870f401 febfffdfffef 
fffe
  B: MSC=10
  B: LED=7

  I: Bus=0019 Vendor= Product=0006 Version=
  N: Name="Video Bus"
  P: Phys=LNXVIDEO/video/input0
  S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/LNXVIDEO:01/input/input5
  U: Uniq=
  H: Handlers=kbd event5 
  B: PROP=0
  B: EV=3
  B: KEY=3e000b 0 0 0

  I: Bus=0003 Vendor=045e Product=07b2 Version=0111
  N: Name="Microsoft Microsoft® Nano Transceiver v1.0"
  P: Phys=usb-:00:14.0-2.3/input0
  S: 
Sysfs=/devices/pci:00/:00:14.0/usb1/1-2/1-2.3/1-2.3:1.0/0003:045E:07B2.0001/input/input6
  U: Uniq=
  H: Handlers=sysrq kbd event6 
  B: PROP=0
  B: EV=120013
  B: KEY=10007 ff8007ff febeffdff3cf fffe
  B: MSC=10
  B: LED=7

  I: Bus=0003 Vendor=045e Product=07b2 Version=0111
  N: Name="Microsoft Microsoft® Nano Transceiver v1.0"
  P: Phys=usb-:00:14.0-2.3/input1
  S: 
Sysfs=/devices/pci:00/:00:14.0/usb1/1-2/1-2.3/1-2.3:1.1/0003:045E:07B2.0002/input/input7
  U: Uniq=
  H: Handlers=mouse0 event7 
  B: PROP=0
  B: EV=17
  B: KEY=1f 0 0 0 0
  B: REL=1c3
  B: MSC=10

  I: Bus=0003 Vendor=045e Product=07b2 Version=0111
  N: Name="Microsoft Microsoft® Nano Transceiver v1.0"
  P: Phys=usb-:00:14.0-2.3/input2
  S: 
Sysfs=/devices/pci:00/:00:14.0/usb1/1-2/1-2.3/1-2.3:1.2/0003:045E:07B2.0003/input/input8
  U: Uniq=
  H: Handlers=sysrq kbd event8 js0 
  B: PROP=0
  B: EV=10001f
  B: KEY=3f0003007f 0 0 4c317aff32d bf544456 c01 
130f938b17c007 7bfad951dfff febeffdfffef fffe
  B: REL=40
  B: ABS=ff01000701ff
  B: MSC=10

  I: Bus=0019 Vendor= Product= Version=
  N: Name="Acer WMI hotkeys"
  P: Phys=wmi/input0
  S: Sysfs=/devices/virtual/input/input9
  U: Uniq=
  H: Handlers=rfkill kbd event9 
  B: PROP=0
  B: EV=13
  B: KEY=1c 0 0 0 0 160080c00 30 0 0
  B: MSC=10

  I: Bus=0019 Vendor= Product= Version=
  N: Name="Acer BMA150 accelerometer"
  P: Phys=wmi/input1
  S: Sysfs=/devices/virtual/input/input10
  U: Uniq=
  H: Handlers=event10 js1 
  B: PROP=0
  B: EV=9
  B: ABS=7

  I: Bus= Vendor= Product= Version=
  N: Name="HDA Intel PCH Headphone"
  P: Phys=ALSA
  S: Sysfs=/devices/pci:00/:00:1b.0/sound/card0/input11
  U: Uniq=
  H: Handlers=event11 
  B: PROP=0
  B: EV=21
  B: SW=4

  I: Bus= Vendor= Product= Version=
  N: Name="HDA Intel PCH HDMI/DP,pcm=3"
  P: Phys=ALSA
  S: Sysfs=/devices/pci:00/:00:1b.0/sound/card0/input12
  U: Uniq=
  H: Handlers=event12 
  B: PROP=0
  B: EV=21
  B: SW=140

  I: Bus=0003 Vendor=04f2 Product=b47f Version=4051
  N: Name="VGA Webcam"
  P: Phys=usb-:00:14.0-4/button
  S: Sysfs=/devices/pci:00/:00:14.0/usb1/1-4/1-4:1.0/input/input13
  U: Uniq=
  H: Handlers=kbd event13 
  B: PROP=0

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

apport information

** Attachment added: "UdevDb.txt"
   https://bugs.launchpad.net/bugs/1564423/+attachment/4618361/+files/UdevDb.txt

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

Title:
  Touchpad not recognized

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Hi, my Acer E3-111 stopped recognizing the touchpad.  External mouse works; 
the machine seems not to recognize the hardware.  Even the system settings only 
shows me mouse settings.  Attaching dmesg and devices.
  The problem started about a week ago after installing an update and rebooting.
  Thanks!
  Andrea

  $ cat /proc/version_signature
  Ubuntu 3.19.0-56.62~14.04.1-generic 3.19.8-ckt15

  $ cat /proc/bus/input/devices
  I: Bus=0019 Vendor= Product=0001 Version=
  N: Name="Power Button"
  P: Phys=PNP0C0C/button/input0
  S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input0
  U: Uniq=
  H: Handlers=kbd event0 
  B: PROP=0
  B: EV=3
  B: KEY=10 0

  I: Bus=0019 Vendor= Product=0003 Version=
  N: Name="Sleep Button"
  P: Phys=PNP0C0E/button/input0
  S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0E:00/input/input1
  U: Uniq=
  H: Handlers=kbd event1 
  B: PROP=0
  B: EV=3
  B: KEY=4000 0 0

  I: Bus=0019 Vendor= Product=0005 Version=
  N: Name="Lid Switch"
  P: Phys=PNP0C0D/button/input0
  S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0D:00/input/input2
  U: Uniq=
  H: Handlers=event2 
  B: PROP=0
  B: EV=21
  B: SW=1

  I: Bus=0019 Vendor= Product=0001 Version=
  N: Name="Power Button"
  P: Phys=LNXPWRBN/button/input0
  S: Sysfs=/devices/LNXSYSTM:00/LNXPWRBN:00/input/input3
  U: Uniq=
  H: Handlers=kbd event3 
  B: PROP=0
  B: EV=3
  B: KEY=10 0

  I: Bus=0011 Vendor=0001 Product=0001 Version=ab41
  N: Name="AT Translated Set 2 keyboard"
  P: Phys=isa0060/serio0/input0
  S: Sysfs=/devices/platform/i8042/serio0/input/input4
  U: Uniq=
  H: Handlers=sysrq kbd event4 
  B: PROP=0
  B: EV=120013
  B: KEY=1 c0200 0 0 700f0203 3802078f870f401 febfffdfffef 
fffe
  B: MSC=10
  B: LED=7

  I: Bus=0019 Vendor= Product=0006 Version=
  N: Name="Video Bus"
  P: Phys=LNXVIDEO/video/input0
  S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/LNXVIDEO:01/input/input5
  U: Uniq=
  H: Handlers=kbd event5 
  B: PROP=0
  B: EV=3
  B: KEY=3e000b 0 0 0

  I: Bus=0003 Vendor=045e Product=07b2 Version=0111
  N: Name="Microsoft Microsoft® Nano Transceiver v1.0"
  P: Phys=usb-:00:14.0-2.3/input0
  S: 
Sysfs=/devices/pci:00/:00:14.0/usb1/1-2/1-2.3/1-2.3:1.0/0003:045E:07B2.0001/input/input6
  U: Uniq=
  H: Handlers=sysrq kbd event6 
  B: PROP=0
  B: EV=120013
  B: KEY=10007 ff8007ff febeffdff3cf fffe
  B: MSC=10
  B: LED=7

  I: Bus=0003 Vendor=045e Product=07b2 Version=0111
  N: Name="Microsoft Microsoft® Nano Transceiver v1.0"
  P: Phys=usb-:00:14.0-2.3/input1
  S: 
Sysfs=/devices/pci:00/:00:14.0/usb1/1-2/1-2.3/1-2.3:1.1/0003:045E:07B2.0002/input/input7
  U: Uniq=
  H: Handlers=mouse0 event7 
  B: PROP=0
  B: EV=17
  B: KEY=1f 0 0 0 0
  B: REL=1c3
  B: MSC=10

  I: Bus=0003 Vendor=045e Product=07b2 Version=0111
  N: Name="Microsoft Microsoft® Nano Transceiver v1.0"
  P: Phys=usb-:00:14.0-2.3/input2
  S: 
Sysfs=/devices/pci:00/:00:14.0/usb1/1-2/1-2.3/1-2.3:1.2/0003:045E:07B2.0003/input/input8
  U: Uniq=
  H: Handlers=sysrq kbd event8 js0 
  B: PROP=0
  B: EV=10001f
  B: KEY=3f0003007f 0 0 4c317aff32d bf544456 c01 
130f938b17c007 7bfad951dfff febeffdfffef fffe
  B: REL=40
  B: ABS=ff01000701ff
  B: MSC=10

  I: Bus=0019 Vendor= Product= Version=
  N: Name="Acer WMI hotkeys"
  P: Phys=wmi/input0
  S: Sysfs=/devices/virtual/input/input9
  U: Uniq=
  H: Handlers=rfkill kbd event9 
  B: PROP=0
  B: EV=13
  B: KEY=1c 0 0 0 0 160080c00 30 0 0
  B: MSC=10

  I: Bus=0019 Vendor= Product= Version=
  N: Name="Acer BMA150 accelerometer"
  P: Phys=wmi/input1
  S: Sysfs=/devices/virtual/input/input10
  U: Uniq=
  H: Handlers=event10 js1 
  B: PROP=0
  B: EV=9
  B: ABS=7

  I: Bus= Vendor= Product= Version=
  N: Name="HDA Intel PCH Headphone"
  P: Phys=ALSA
  S: Sysfs=/devices/pci:00/:00:1b.0/sound/card0/input11
  U: Uniq=
  H: Handlers=event11 
  B: PROP=0
  B: EV=21
  B: SW=4

  I: Bus= Vendor= Product= Version=
  N: Name="HDA Intel PCH HDMI/DP,pcm=3"
  P: Phys=ALSA
  S: Sysfs=/devices/pci:00/:00:1b.0/sound/card0/input12
  U: Uniq=
  H: Handlers=event12 
  B: PROP=0
  B: EV=21
  B: SW=140

  I: Bus=0003 Vendor=04f2 Product=b47f Version=4051
  N: Name="VGA Webcam"
  P: Phys=usb-:00:14.0-4/button
  S: Sysfs=/devices/pci:00/:00:14.0/usb1/1-4/1-4:1.0/input/input13
  U: Uniq=
  H: Handlers=kbd event13 
  B: PROP=0
  B:

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