date:20160504

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

Title:
  Dell Bluetooth card not working except enable/disable

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After install this bluetooth card, it can be enabled and disabled, but
  blue manager always claims "Bluetooth is disabled"

  usb-devices omits this card, even though it appears in lsusb.
  Bus 003 Device 003: ID 413c:8141 Dell Computer Corp.   

  This has been a problem since before 14.04, and 16.04 has not yet
  solved it.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-21-generic 4.4.0-21.37
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic i686
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   dell   1676 F...m pulseaudio
   /dev/snd/controlC0:  dell   1676 F pulseaudio
  CurrentDesktop: Unity
  Date: Wed May  4 19:24:49 2016
  HibernationDevice: RESUME=UUID=125fc390-b5fa-4322-a0c7-79fb51f68fa9
  InstallationDate: Installed on 2015-10-24 (193 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta i386 (20150805)
  MachineType: Dell Inc. Latitude D630
  PccardctlIdent:
   Socket 0:
 no product info available
  PccardctlStatus:
   Socket 0:
 no card
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-21-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-21-generic N/A
   linux-backports-modules-4.4.0-21-generic  N/A
   linux-firmware1.157
  SourcePackage: linux
  UpgradeStatus: Upgraded to xenial on 2016-05-01 (2 days ago)
  dmi.bios.date: 01/04/2010
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A17
  dmi.board.name: 0JY102
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA17:bd01/04/2010:svnDellInc.:pnLatitudeD630:pvr:rvnDellInc.:rn0JY102:rvr:cvnDellInc.:ct8:cvr:
  dmi.product.name: Latitude D630
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1578094/+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 1539158] Re: Unable to pair with in-car hands-free system after OTA-9 update

2016-05-04 Thread Konrad Zapałowicz

This is awesome, thank you for performing the test case. Now I know that
the flaw is still somewhere in the Ubuntu System Settings and it is most
probably a race.

As for the other issues that you have observed I would prefer to first
solve the pairing bug and the other you mention will be waiting in the
queue. The best thing, as you suggest, would be to report these as
separate issues so that we can track them and manage the priorities.

Best

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

Title:
  Unable to pair with in-car hands-free system after OTA-9 update

Status in Canonical System Image:
  Confirmed
Status in bluez package in Ubuntu:
  Confirmed
Status in ubuntu-system-settings package in Ubuntu:
  Confirmed

Bug description:
  After OTA-9 I started having trouble with my bluetooth connection to the car 
hands-free system (no sound, and incoming calls no longer displayed the 
number), so I have reset both the car and the phone connections (eg. forgot the 
devices).
  Now I can't even pair the phone with the car's system. 
  The car finds the phone, and then asks me to enter the code "" to pair 
the device, but after a few moments, it just says the connection failed and 
asks me to try again. Which fails again.

  It was working fine just before the update.

  Any logs I should post to help debug?

  PS - The car is a 2015 Honda Civic Tourer, if that matters.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1539158/+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 1574612] Re: Random hangs

2016-05-04 Thread Serrie

** Tags added: kernel-fixed-upstream kernel-fixed-upstream-4.6.0-rc6

** Tags removed: kernel-fixed-upstream-4.6.0-rc6
** Tags added: kernel-fixed-upstream-4.6-rc6

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

Title:
Random hangs

Status in linux package in Ubuntu:
Confirmed

Bug description:
System hangs randomly. This mostly occurs anywhere between 15 minutes
and a few hours after boot. Couldn't figure out the trigger. Happened
while viewing YouTube, using Spotify switching to Eclipse etc. SSH
still works, so I can get to the machine if the lockup occurs. That's
how I submitted the bug. All screens freeze though, while audio keeps
on working (like music from Spotify or sound from a YouTube video).
The only thing that seems to keep working UI-wise is the mouse
pointer.

Had memtest running for half an hour without problems.

The issue occurs multiple times a day. Issue doesn't seem to be
triggered if I remove linux-image-4.2.0-35-generic and go back to
linux-image-4.2.0-16-generic. Did use the linux-image-4.2.0-16-generic
kernel for a few days without issues.

The kern.log contains some stacktraces with the method being
'schedule'. This is around the time the hang occurs.

See extra debug information for more info.

ProblemType: Bug
DistroRelease: Ubuntu 15.10
Package: linux-image-4.2.0-35-generic 4.2.0-35.40
ProcVersionSignature: Ubuntu 4.2.0-35.40-generic 4.2.8-ckt5
Uname: Linux 4.2.0-35-generic x86_64
ApportVersion: 2.19.1-0ubuntu5
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: serrie 1815 F pulseaudio
/dev/snd/pcmC0D0c: serrie 1815 F...m pulseaudio
/dev/snd/controlC0: serrie 1815 F pulseaudio
Date: Mon Apr 25 13:56:48 2016
InstallationDate: Installed on 2016-04-12 (13 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
IwConfig:
docker0 no wireless extensions.

enp4s0no wireless extensions.

lono wireless extensions.
MachineType: System manufacturer System Product Name
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-35-generic
root=UUID=c15a8aa0-fb21-495c-bbc6-ea4f2018dc1f ro quiet splash vt.handoff=7
PulseList:
Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not
accessible: Permission denied
No PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
linux-restricted-modules-4.2.0-35-generic N/A
linux-backports-modules-4.2.0-35-generic N/A
linux-firmware1.149.3
RfKill:

SourcePackage: linux
UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
UpgradeStatus: Upgraded to wily on 2016-04-22 (3 days ago)
dmi.bios.date: 01/27/2016
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 0505
dmi.board.asset.tag: Default string
dmi.board.name: B150M-A D3
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev X.0x
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvr0505:bd01/27/2016:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnB150M-AD3:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:
dmi.product.name: System Product Name
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer

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

2016-05-04 Thread Serrie

Latest upstream kernel is running stable for 2 days straight. No hangs
and the kernel log is way cleaner, even though there are some i915
errors present. Attached the new kern.log if needed.

** Attachment added: "kern_upstream_4.6.0-rc6.log"

https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1574612/+attachment/4655327/+files/kern_upstream_4.6.0-rc6.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/1574612

Title:
Random hangs

Status in linux package in Ubuntu:
Confirmed

Had memtest running for half an hour without problems.

The kern.log contains some stacktraces with the method being
'schedule'. This is around the time the hang occurs.

See extra debug information for more info.

enp4s0no wireless extensions.

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

[Kernel-packages] [Bug 1470250] Re: [Hyper-V] Ubuntu 14.04.2 LTS Generation 2 SCSI Errors on VSS Based Backups

2016-05-04 Thread Emsi

I experienced it during migration and other means involving snapshots.

-- 
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
Status in linux source package in Xenial:
  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 1578141] [NEW] Predictable interface names partially broken with igb driver

2016-05-04 Thread Dr. Jens Rosenboom

Public bug reported:

Note: I'm not sure whether this is really a kernel bug or something
within systemd/udev, please advise how to further debug.

On a system with two GE ports, instead of getting named eno1 and eno2, I
am getting eno1 and renameN. Where N starts at 3 and increases by 2 on
every iteration of doing "rmmod igb;modprobe igb". The corresponding
lines in dmesg look like this:

[2.748429] igb :07:00.0: added PHC on eth0
[2.748431] igb :07:00.0: Intel(R) Gigabit Ethernet Network Connection
[2.748433] igb :07:00.0: eth0: (PCIe:5.0Gb/s:Width x4) 00:25:90:d7:60:8e
[2.748505] igb :07:00.0: eth0: PBA No: 106100-000
[2.748506] igb :07:00.0: Using MSI-X interrupts. 8 rx queue(s), 8 tx 
queue(s)
[2.802555] igb :07:00.1: added PHC on eth1
[2.802557] igb :07:00.1: Intel(R) Gigabit Ethernet Network Connection
[2.802559] igb :07:00.1: eth1: (PCIe:5.0Gb/s:Width x4) 00:25:90:d7:60:8f
[2.802631] igb :07:00.1: eth1: PBA No: 106100-000
[2.802632] igb :07:00.1: Using MSI-X interrupts. 8 rx queue(s), 8 tx 
queue(s)
[2.803618] igb :07:00.0 eno1: renamed from eth0
[2.833208] igb :07:00.1 rename3: renamed from eth1

What is even worse: Sometimes the naming changes and the second
interface ends up as eno1 while the first interface is named renameN
with an even N. The bad thing about this version is that when it happens
while the installer is running, the installer will setup "rename2" as
the primary network interface, which works fine for the installation
itself, but after installation is finished and the first boot of the
installed system happens, that interface will be gone, leaving the
system without network connectivity.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: linux-image-4.4.0-21-generic 4.4.0-21.37
ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
Uname: Linux 4.4.0-21-generic x86_64
AlsaDevices:
 total 0
 crw-rw 1 root audio 116,  1 May  4 09:48 seq
 crw-rw 1 root audio 116, 33 May  4 09:48 timer
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
ApportVersion: 2.20.1-0ubuntu2
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
Date: Wed May  4 10:00:39 2016
HibernationDevice: RESUME=/dev/mapper/compute--node37--vg-swap
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
Lsusb:
 Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
 Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 001 Device 003: ID 0557:2221 ATEN International Co., Ltd Winbond Hermon
 Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Supermicro X9DRT-HF+
PciMultimedia:
 
ProcEnviron:
 LANGUAGE=en_US:
 TERM=screen
 PATH=(custom, no user)
 LANG=en_US
 SHELL=/bin/bash
ProcFB: 0 VESA VGA
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-21-generic 
root=/dev/mapper/compute--node37--vg-root ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-4.4.0-21-generic N/A
 linux-backports-modules-4.4.0-21-generic  N/A
 linux-firmware1.157
RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/21/2014
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 3.0c
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: X9DRT-HF+
dmi.board.vendor: Supermicro
dmi.board.version: 0123456789
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 17
dmi.chassis.vendor: Supermicro
dmi.chassis.version: 0123456789
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3.0c:bd05/21/2014:svnSupermicro:pnX9DRT-HF+:pvr0123456789:rvnSupermicro:rnX9DRT-HF+:rvr0123456789:cvnSupermicro:ct17:cvr0123456789:
dmi.product.name: X9DRT-HF+
dmi.product.version: 0123456789
dmi.sys.vendor: Supermicro

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


** Tags: amd64 apport-bug xenial

** Attachment added: "version.log"
   
https://bugs.launchpad.net/bugs/1578141/+attachment/4655387/+files/version.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/1578141

Title:
  Predictable interface names partially broken with igb driver

Status in linux package in Ubuntu:
  New

Bug description:
  Note: I'm not sure whether this is really a kernel bug or something
  within systemd/udev, please advise how to further debug.

  On a system with two GE ports, instead of getting named eno1 and eno2,
  I am getting eno1 and renameN. Where N starts at 3 and increases by 2
  on every iteration of doing "rmmod igb;modprobe igb". The
  corresponding lines in dmesg look like this:

[Kernel-packages] [Bug 1578141] 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/1578141

Title:
  Predictable interface names partially broken with igb driver

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Note: I'm not sure whether this is really a kernel bug or something
  within systemd/udev, please advise how to further debug.

  On a system with two GE ports, instead of getting named eno1 and eno2,
  I am getting eno1 and renameN. Where N starts at 3 and increases by 2
  on every iteration of doing "rmmod igb;modprobe igb". The
  corresponding lines in dmesg look like this:

  [2.748429] igb :07:00.0: added PHC on eth0
  [2.748431] igb :07:00.0: Intel(R) Gigabit Ethernet Network Connection
  [2.748433] igb :07:00.0: eth0: (PCIe:5.0Gb/s:Width x4) 
00:25:90:d7:60:8e
  [2.748505] igb :07:00.0: eth0: PBA No: 106100-000
  [2.748506] igb :07:00.0: Using MSI-X interrupts. 8 rx queue(s), 8 tx 
queue(s)
  [2.802555] igb :07:00.1: added PHC on eth1
  [2.802557] igb :07:00.1: Intel(R) Gigabit Ethernet Network Connection
  [2.802559] igb :07:00.1: eth1: (PCIe:5.0Gb/s:Width x4) 
00:25:90:d7:60:8f
  [2.802631] igb :07:00.1: eth1: PBA No: 106100-000
  [2.802632] igb :07:00.1: Using MSI-X interrupts. 8 rx queue(s), 8 tx 
queue(s)
  [2.803618] igb :07:00.0 eno1: renamed from eth0
  [2.833208] igb :07:00.1 rename3: renamed from eth1

  What is even worse: Sometimes the naming changes and the second
  interface ends up as eno1 while the first interface is named renameN
  with an even N. The bad thing about this version is that when it
  happens while the installer is running, the installer will setup
  "rename2" as the primary network interface, which works fine for the
  installation itself, but after installation is finished and the first
  boot of the installed system happens, that interface will be gone,
  leaving the system without network connectivity.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-21-generic 4.4.0-21.37
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 May  4 09:48 seq
   crw-rw 1 root audio 116, 33 May  4 09:48 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  Date: Wed May  4 10:00:39 2016
  HibernationDevice: RESUME=/dev/mapper/compute--node37--vg-swap
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb:
   Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
   Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 001 Device 003: ID 0557:2221 ATEN International Co., Ltd Winbond Hermon
   Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Supermicro X9DRT-HF+
  PciMultimedia:
   
  ProcEnviron:
   LANGUAGE=en_US:
   TERM=screen
   PATH=(custom, no user)
   LANG=en_US
   SHELL=/bin/bash
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-21-generic 
root=/dev/mapper/compute--node37--vg-root ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-21-generic N/A
   linux-backports-modules-4.4.0-21-generic  N/A
   linux-firmware1.157
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/21/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3.0c
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: X9DRT-HF+
  dmi.board.vendor: Supermicro
  dmi.board.version: 0123456789
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 17
  dmi.chassis.vendor: Supermicro
  dmi.chassis.version: 0123456789
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3.0c:bd05/21/2014:svnSupermicro:pnX9DRT-HF+:pvr0123456789:rvnSupermicro:rnX9DRT-HF+:rvr0123456789:cvnSupermicro:ct17:cvr0123456789:
  dmi.product.name: X9DRT-HF+
  dmi.product.version: 0123456789
  dmi.sys.vendor: Supermicro

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1578141/+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 1575261] Re: volume/mute keys no longer work

2016-05-04 Thread Max Waterman

This seems to be caused by :

https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1575260

worked around by making a symlink :

sudo ln -s /usr/lib/x86_64-linux-gnu/libusbmuxd.so.4.0.0 /usr/lib/x86_64
-linux-gnu/libusbmuxd.so.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/1575261

Title:
  volume/mute keys no longer work

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After upgrading from 15.10 to 16.04, my volume keys no longer work. In
  15.10, pressing the volume up/down resulted in the volume going
  up/down as indicated in the applet in the top menu, accompanied by a
  blip. Since upgrading, there is no response to the keys.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-21-generic 4.4.0-21.37
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  davidmaxwaterman   2348 F pulseaudio
   /dev/snd/controlC0:  davidmaxwaterman   2348 F pulseaudio
  CurrentDesktop: Unity
  Date: Tue Apr 26 17:27:24 2016
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=f6a6d0a5-8059-4f25-9b03-f560ceb68f6d
  InstallationDate: Installed on 2015-05-20 (342 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  MachineType: LENOVO 20CM001QUK
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-21-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-21-generic N/A
   linux-backports-modules-4.4.0-21-generic  N/A
   linux-firmware1.157
  SourcePackage: linux
  UpgradeStatus: Upgraded to xenial on 2016-04-22 (4 days ago)
  dmi.bios.date: 04/06/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N10ET33W (1.12 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20CM001QUK
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0E50510 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN10ET33W(1.12):bd04/06/2015:svnLENOVO:pn20CM001QUK:pvrThinkPadX250:rvnLENOVO:rn20CM001QUK:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.name: 20CM001QUK
  dmi.product.version: ThinkPad X250
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1575261/+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 1575260] Re: Failed to start Daemon for power management.

2016-05-04 Thread Max Waterman

It seems this problem caused the 'Screen Display' utility to fail :

https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1577760

and was worked around by making a new symlink :

sudo ln -s /usr/lib/x86_64-linux-gnu/libusbmuxd.so.4.0.0 /usr/lib/x86_64
-linux-gnu/libusbmuxd.so.2

It seems some binaries aren't linked correctly.

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

Title:
  Failed to start Daemon for power management.

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  One of the many issue since upgrading to 16.10, I get this in my
  syslog :

454 Apr 26 07:57:40 mwaterm1-x250 upowerd[13918]: /usr/lib/upower/upowerd: 
error while loading shared libraries: libusbmuxd.so.2: cannot open shared 
object file: No such file or directory
455 Apr 26 07:57:40 mwaterm1-x250 systemd[1]: upower.service: Main process 
exited, code=exited, status=127/n/a
456 Apr 26 07:57:40 mwaterm1-x250 systemd[1]: Failed to start Daemon for 
power management.
457 Apr 26 07:57:40 mwaterm1-x250 systemd[1]: upower.service: Unit entered 
failed state.
458 Apr 26 07:57:40 mwaterm1-x250 systemd[1]: upower.service: Failed with 
result 'exit-code'.
459 Apr 26 07:57:41 mwaterm1-x250 systemd[1]: upower.service: Service 
hold-off time over, scheduling restart.
460 Apr 26 07:57:41 mwaterm1-x250 systemd[1]: Stopped Daemon for power 
management.
461 Apr 26 07:57:41 mwaterm1-x250 systemd[1]: upower.service: Start request 
repeated too quickly.
462 Apr 26 07:57:41 mwaterm1-x250 systemd[1]: Failed to start Daemon for 
power management.
463 Apr 26 07:58:04 mwaterm1-x250 gnome-session[2230]: 
gnome-session-binary[2230]: GnomeDesktop-WARNING: Failed to acquire idle 
monitor object manager: Timeout was reached
464 Apr 26 07:58:04 mwaterm1-x250 gnome-session-binary[2230]: 
GnomeDesktop-WARNING: Failed to acquire idle monitor object manager: Timeout 
was reached
465 Apr 26 07:58:04 mwaterm1-x250 kernel: [27931.343128] 
unity-settings-[13900]: segfault at 0 ip 7f21751ade69 sp 7ffc7ad90ea0 
error 4 in libupower-glib.so.3.0.1[7f217519e000+24000]

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-21-generic 4.4.0-21.37
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  davidmaxwaterman   2348 F pulseaudio
   /dev/snd/controlC0:  davidmaxwaterman   2348 F pulseaudio
  CurrentDesktop: Unity
  Date: Tue Apr 26 17:19:05 2016
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=f6a6d0a5-8059-4f25-9b03-f560ceb68f6d
  InstallationDate: Installed on 2015-05-20 (342 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  MachineType: LENOVO 20CM001QUK
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-21-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-21-generic N/A
   linux-backports-modules-4.4.0-21-generic  N/A
   linux-firmware1.157
  SourcePackage: linux
  UpgradeStatus: Upgraded to xenial on 2016-04-22 (4 days ago)
  dmi.bios.date: 04/06/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N10ET33W (1.12 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20CM001QUK
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0E50510 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN10ET33W(1.12):bd04/06/2015:svnLENOVO:pn20CM001QUK:pvrThinkPadX250:rvnLENOVO:rn20CM001QUK:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.name: 20CM001QUK
  dmi.product.version: ThinkPad X250
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1575260/+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 1568865] Re: [drm:intel_cpu_fifo_underrun_irq_handler [i915_bpo]] ERROR CPU pipe B FIFO underrun

I am also seeing this, with a fresh install of 16.04 on a new Dell
Precision 5510 (also Skylake, similar to the XPS 15 9550).

When I plug in an external monitor I see this error in syslog:

May  4 12:13:01 cherry kernel: [ 1362.648527] [ cut here 
]
May  4 12:13:01 cherry kernel: [ 1362.648542] WARNING: CPU: 7 PID: 1182 at 
/build/linux-Ay7j_C/linux-4.4.0/ubuntu/i915/intel_pm.c:3572 
skl_update_other_pipe_wm+0x16c/0x180 [i915_bpo]()
May  4 12:13:01 cherry kernel: [ 1362.648543] WARN_ON(!wm_changed)
May  4 12:13:01 cherry kernel: [ 1362.648544] Modules linked in: rfcomm bnep 
smsc75xx usbnet mii bbswitch(OE) pci_stub vboxpci(OE) vboxnetadp(OE) 
vboxnetflt(OE) vboxdrv(OE) arc4 nls_iso8859_1 snd_hda_codec_hdmi iwlmvm 
dell_rbtn dell_led dell_laptop intel_rapl x86_pkg_temp_thermal dell_wmi 
intel_powerclamp coretemp snd_hda_codec_realtek dcdbas i2c_designware_platform 
i2c_designware_core mxm_wmi sparse_keymap snd_hda_codec_generic mac80211 
kvm_intel dell_smm_hwmon kvm iwlwifi uvcvideo cfg80211 irqbypass 
videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 snd_hda_intel rtsx_pci_ms 
memstick snd_hda_codec serio_raw videobuf2_core snd_hda_core v4l2_common 
snd_hwdep videodev snd_pcm hid_multitouch input_leds media joydev snd_seq_midi 
snd_seq_midi_event btusb snd_rawmidi btrtl snd_seq snd_seq_device snd_timer snd 
mei_me mei soundcore idma64 shpchp virt_dma processor_thermal_device 
intel_soc_dts_iosf intel_lpss_pci hci_uart btbcm btqca btintel bluetooth 
int3403_thermal dell_smo8800 intel_lpss_a
 cpi intel_lpss wmi int3400_thermal acpi_als mac_hid int3402_thermal 
acpi_thermal_rel int340x_thermal_zone kfifo_buf acpi_pad industrialio 
parport_pc ppdev lp parport autofs4 drbg ansi_cprng algif_skcipher af_alg 
dm_crypt hid_generic usbhid rtsx_pci_sdmmc crct10dif_pclmul crc32_pclmul 
i915_bpo aesni_intel aes_x86_64 lrw gf128mul glue_helper ablk_helper intel_ips 
cryptd i2c_algo_bit drm_kms_helper syscopyarea sysfillrect psmouse sysimgblt 
fb_sys_fops drm ahci rtsx_pci libahci i2c_hid hid pinctrl_sunrisepoint video 
pinctrl_intel fjes [last unloaded: nvidia]
May  4 12:13:01 cherry kernel: [ 1362.648588] CPU: 7 PID: 1182 Comm: Xorg 
Tainted: PW  OE   4.4.0-21-generic #37-Ubuntu
May  4 12:13:01 cherry kernel: [ 1362.648589] Hardware name: Dell Inc. 
Precision 5510/0N8J4R, BIOS 01.02.00 04/07/2016
May  4 12:13:01 cherry kernel: [ 1362.648590]  0286 
df0da080 8804a71e79a8 813e93c3
May  4 12:13:01 cherry kernel: [ 1362.648591]  8804a71e79f0 
c03efc70 8804a71e79e0 81080f62
May  4 12:13:01 cherry kernel: [ 1362.648593]  8804aa572000 
8804a3089d9c 8804aa574000 8804a3a64b78
May  4 12:13:01 cherry kernel: [ 1362.648594] Call Trace:
May  4 12:13:01 cherry kernel: [ 1362.648597]  [] 
dump_stack+0x63/0x90
May  4 12:13:01 cherry kernel: [ 1362.648599]  [] 
warn_slowpath_common+0x82/0xc0
May  4 12:13:01 cherry kernel: [ 1362.648601]  [] 
warn_slowpath_fmt+0x5c/0x80
May  4 12:13:01 cherry kernel: [ 1362.648610]  [] 
skl_update_other_pipe_wm+0x16c/0x180 [i915_bpo]
May  4 12:13:01 cherry kernel: [ 1362.648619]  [] 
skl_update_wm+0x186/0x5f0 [i915_bpo]
May  4 12:13:01 cherry kernel: [ 1362.648629]  [] ? 
intel_display_power_put+0xd0/0x130 [i915_bpo]
May  4 12:13:01 cherry kernel: [ 1362.648638]  [] 
intel_update_watermarks+0x1e/0x30 [i915_bpo]
May  4 12:13:01 cherry kernel: [ 1362.648652]  [] 
intel_atomic_commit+0x466/0xdb0 [i915_bpo]
May  4 12:13:01 cherry kernel: [ 1362.648663]  [] ? 
drm_atomic_check_only+0x18e/0x590 [drm]
May  4 12:13:01 cherry kernel: [ 1362.648672]  [] 
drm_atomic_commit+0x37/0x60 [drm]
May  4 12:13:01 cherry kernel: [ 1362.648677]  [] 
drm_atomic_helper_set_config+0x76/0xb0 [drm_kms_helper]
May  4 12:13:01 cherry kernel: [ 1362.648685]  [] ? 
drm_modeset_lock_all_ctx+0x9a/0xb0 [drm]
May  4 12:13:01 cherry kernel: [ 1362.648693]  [] 
drm_mode_set_config_internal+0x62/0x100 [drm]
May  4 12:13:01 cherry kernel: [ 1362.648701]  [] 
drm_mode_setcrtc+0x3d2/0x4f0 [drm]
May  4 12:13:01 cherry kernel: [ 1362.648706]  [] 
drm_ioctl+0x152/0x540 [drm]
May  4 12:13:01 cherry kernel: [ 1362.648714]  [] ? 
drm_mode_setplane+0x1b0/0x1b0 [drm]
May  4 12:13:01 cherry kernel: [ 1362.648716]  [] 
do_vfs_ioctl+0x29f/0x490
May  4 12:13:01 cherry kernel: [ 1362.648718]  [] ? 
__sys_recvmsg+0x80/0x90
May  4 12:13:01 cherry kernel: [ 1362.648719]  [] 
SyS_ioctl+0x79/0x90
May  4 12:13:01 cherry kernel: [ 1362.648721]  [] 
entry_SYSCALL_64_fastpath+0x16/0x71
May  4 12:13:01 cherry kernel: [ 1362.648722] ---[ end trace 5c4996187af7546b 
]---
May  4 12:13:02 cherry kernel: [ 1363.740247] 
[drm:intel_cpu_fifo_underrun_irq_handler [i915_bpo]] *ERROR* CPU pipe B FIFO 
underrun


After this, I have an issue where moving the mouse into the laptop's screen 
causes the screen to go black (after some brief glitches). In fact, it's enough 
to move the mouse pointer close to the configured boundary between the external 
screen and the laptop scr

[Kernel-packages] [Bug 1568865] Re: [drm:intel_cpu_fifo_underrun_irq_handler [i915_bpo]] ERROR CPU pipe B FIFO underrun

FWIW I still have this issue without Unity and Compiz running, so I
don't think it has anything to do with those. I don't see any relevant
logging from X even after starting it with -logverbose 6.

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

Title:
  [drm:intel_cpu_fifo_underrun_irq_handler [i915_bpo]] *ERROR* CPU pipe
  B FIFO underrun

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Running Gnome-Shell on ubuntu 16.04 on my Dell XPS 15 9550 laptop
  using Intel graphics (Nvidia card turned off), I get this error in
  syslog when plugging in an external monitor (HDMI).

  Apr 11 14:28:38 miaco kernel: [ 2616.604641]
  [drm:intel_cpu_fifo_underrun_irq_handler [i915_bpo]] *ERROR* CPU pipe
  B FIFO underrun


  Meanwhile both screens flash and show corruption. Most of the time
  this has caused a hang that needs a hard power off to get out of, but
  occasionally removing the external monitor is enough to get going
  again and so I've been able to find this message in the logs.

  Note that when using Nvidia (proprietary) drivers and Unity DE I do
  not have this problem; so it seems to be related to the intel drivers,
  or possibly Gnome Shell's use of them.

  Happy to help if I can (would like to be able to use external
  monitors!)

  Rich

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-18-generic 4.4.0-18.34
  ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6
  Uname: Linux 4.4.0-18-generic x86_64
  ApportVersion: 2.20.1-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  rich   1943 F pulseaudio
  Date: Mon Apr 11 14:31:26 2016
  InstallationDate: Installed on 2016-03-21 (21 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160307)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 04f3:21d5 Elan Microelectronics Corp. 
   Bus 001 Device 002: ID 0a5c:6410 Broadcom Corp. 
   Bus 001 Device 004: ID 0c45:6713 Microdia 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. XPS 15 9550
  ProcEnviron:
   LANGUAGE=en_GB:en
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-18-generic.efi.signed 
root=UUID=3f8391d5-e9cc-4768-8efb-8f04d340567c ro quiet splash vt.handoff=7
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-18-generic N/A
   linux-backports-modules-4.4.0-18-generic  N/A
   linux-firmware1.157
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/25/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 01.01.19
  dmi.board.name: 0N7TVV
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr01.01.19:bd01/25/2016:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0N7TVV:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 15 9550
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1568865/+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 1568865] Re: [drm:intel_cpu_fifo_underrun_irq_handler [i915_bpo]] ERROR CPU pipe B FIFO underrun

This is also with the latest bios update (A07) from Dell.

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

Title:
  [drm:intel_cpu_fifo_underrun_irq_handler [i915_bpo]] *ERROR* CPU pipe
  B FIFO underrun

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Running Gnome-Shell on ubuntu 16.04 on my Dell XPS 15 9550 laptop
  using Intel graphics (Nvidia card turned off), I get this error in
  syslog when plugging in an external monitor (HDMI).

  Apr 11 14:28:38 miaco kernel: [ 2616.604641]
  [drm:intel_cpu_fifo_underrun_irq_handler [i915_bpo]] *ERROR* CPU pipe
  B FIFO underrun


  Meanwhile both screens flash and show corruption. Most of the time
  this has caused a hang that needs a hard power off to get out of, but
  occasionally removing the external monitor is enough to get going
  again and so I've been able to find this message in the logs.

  Note that when using Nvidia (proprietary) drivers and Unity DE I do
  not have this problem; so it seems to be related to the intel drivers,
  or possibly Gnome Shell's use of them.

  Happy to help if I can (would like to be able to use external
  monitors!)

  Rich

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-18-generic 4.4.0-18.34
  ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6
  Uname: Linux 4.4.0-18-generic x86_64
  ApportVersion: 2.20.1-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  rich   1943 F pulseaudio
  Date: Mon Apr 11 14:31:26 2016
  InstallationDate: Installed on 2016-03-21 (21 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160307)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 04f3:21d5 Elan Microelectronics Corp. 
   Bus 001 Device 002: ID 0a5c:6410 Broadcom Corp. 
   Bus 001 Device 004: ID 0c45:6713 Microdia 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. XPS 15 9550
  ProcEnviron:
   LANGUAGE=en_GB:en
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-18-generic.efi.signed 
root=UUID=3f8391d5-e9cc-4768-8efb-8f04d340567c ro quiet splash vt.handoff=7
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-18-generic N/A
   linux-backports-modules-4.4.0-18-generic  N/A
   linux-firmware1.157
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/25/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 01.01.19
  dmi.board.name: 0N7TVV
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr01.01.19:bd01/25/2016:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0N7TVV:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 15 9550
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1568865/+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 1568865] Re: [drm:intel_cpu_fifo_underrun_irq_handler [i915_bpo]] ERROR CPU pipe B FIFO underrun

Assuming this is what's responsible for the issue, to me this is quite a
major bug as it prevents use of external display together with the
laptop screen.

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

Title:
  [drm:intel_cpu_fifo_underrun_irq_handler [i915_bpo]] *ERROR* CPU pipe
  B FIFO underrun

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Running Gnome-Shell on ubuntu 16.04 on my Dell XPS 15 9550 laptop
  using Intel graphics (Nvidia card turned off), I get this error in
  syslog when plugging in an external monitor (HDMI).

  Apr 11 14:28:38 miaco kernel: [ 2616.604641]
  [drm:intel_cpu_fifo_underrun_irq_handler [i915_bpo]] *ERROR* CPU pipe
  B FIFO underrun


  Meanwhile both screens flash and show corruption. Most of the time
  this has caused a hang that needs a hard power off to get out of, but
  occasionally removing the external monitor is enough to get going
  again and so I've been able to find this message in the logs.

  Note that when using Nvidia (proprietary) drivers and Unity DE I do
  not have this problem; so it seems to be related to the intel drivers,
  or possibly Gnome Shell's use of them.

  Happy to help if I can (would like to be able to use external
  monitors!)

  Rich

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-18-generic 4.4.0-18.34
  ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6
  Uname: Linux 4.4.0-18-generic x86_64
  ApportVersion: 2.20.1-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  rich   1943 F pulseaudio
  Date: Mon Apr 11 14:31:26 2016
  InstallationDate: Installed on 2016-03-21 (21 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160307)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 04f3:21d5 Elan Microelectronics Corp. 
   Bus 001 Device 002: ID 0a5c:6410 Broadcom Corp. 
   Bus 001 Device 004: ID 0c45:6713 Microdia 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. XPS 15 9550
  ProcEnviron:
   LANGUAGE=en_GB:en
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-18-generic.efi.signed 
root=UUID=3f8391d5-e9cc-4768-8efb-8f04d340567c ro quiet splash vt.handoff=7
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-18-generic N/A
   linux-backports-modules-4.4.0-18-generic  N/A
   linux-firmware1.157
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/25/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 01.01.19
  dmi.board.name: 0N7TVV
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr01.01.19:bd01/25/2016:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0N7TVV:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 15 9550
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1568865/+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 1578176] [NEW] Cannot place or recieve calls when using in-car bluetooth system

Public bug reported:

After working around bug
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1539158 I was able
to pair the phone (BQ Aquaris E4.5) with the car hands-free system.

However, thing don't quite work as expected.
I can use the car's system to place a call using the phone, but The audio is 
not getting properly routed. After placing the call, I can't hear any sounds 
(not even the "ringing" noise), I don't get any feedback after the other person 
has answered the phone, and the other person can't hear me either.

Furthermore, Long after the other person has hung up the call, the phone
still looks like the call is ongoing (I have to manually disconnect it).

I can also use the system to answer an incoming call, but the sympthoms
are the same. No audio on either end.

Would a debug log be helpful in this situation 
(https://wiki.ubuntu.com/DebuggingBluetooth)?
Or is something else required?

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

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

Title:
  Cannot place or recieve calls when using in-car bluetooth system

Status in bluez package in Ubuntu:
  New

Bug description:
  After working around bug
  https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1539158 I was
  able to pair the phone (BQ Aquaris E4.5) with the car hands-free
  system.

  However, thing don't quite work as expected.
  I can use the car's system to place a call using the phone, but The audio is 
not getting properly routed. After placing the call, I can't hear any sounds 
(not even the "ringing" noise), I don't get any feedback after the other person 
has answered the phone, and the other person can't hear me either.

  Furthermore, Long after the other person has hung up the call, the
  phone still looks like the call is ongoing (I have to manually
  disconnect it).

  I can also use the system to answer an incoming call, but the
  sympthoms are the same. No audio on either end.

  Would a debug log be helpful in this situation 
(https://wiki.ubuntu.com/DebuggingBluetooth)?
  Or is something else required?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1578176/+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 1578176] Re: Cannot place or recieve calls when using in-car bluetooth system

I should also add that *before* OTA9 the entire system worked
flawlessly, so this is likely related to the update to Bluez5.

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

Title:
  Cannot place or recieve calls when using in-car bluetooth system

Status in bluez package in Ubuntu:
  New

Bug description:
  After working around bug
  https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1539158 I was
  able to pair the phone (BQ Aquaris E4.5) with the car hands-free
  system.

  However, thing don't quite work as expected.
  I can use the car's system to place a call using the phone, but The audio is 
not getting properly routed. After placing the call, I can't hear any sounds 
(not even the "ringing" noise), I don't get any feedback after the other person 
has answered the phone, and the other person can't hear me either.

  Furthermore, Long after the other person has hung up the call, the
  phone still looks like the call is ongoing (I have to manually
  disconnect it).

  I can also use the system to answer an incoming call, but the
  sympthoms are the same. No audio on either end.

  Would a debug log be helpful in this situation 
(https://wiki.ubuntu.com/DebuggingBluetooth)?
  Or is something else required?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1578176/+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 1536841] Re: xenial can't access network printer 14.04.3 no problem

2016-05-04 Thread jerrylamos

With a lot of effort and million monkeys on the keyboard I was finally able to 
get Xenial to access Windows 10 printer.
Yakkety Yak same problem all over again.  
I'll flail around a bit and open another bug if necessary.
Conclusion, Ubuntu developers don't have a Windows 10 on their network to check 
compatibility in the real world.

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

Title:
  xenial can't access network printer 14.04.3 no problem

Status in linux package in Ubuntu:
  Expired

Bug description:
  There was an error during the CUPS operation: 'client-error-not-
  possible'.

  14.04.3 on another partition accesses network printer on XP just fine.

  With identical smb.conf xenial cannot access the printer.

  Xenial can access XP jpg images etc. so network connection to XP
  working fine.

  See attached screenshot

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.3.0-6-generic 4.3.0-6.17
  ProcVersionSignature: Ubuntu 4.3.0-6.17-generic 4.3.3
  Uname: Linux 4.3.0-6-generic x86_64
  ApportVersion: 2.19.3-0ubuntu3
  Architecture: amd64
  Date: Thu Jan 21 18:41:32 2016
  InstallationDate: Installed on 2015-12-26 (26 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20151209)
  ProcEnviron:
   LANGUAGE=en_US
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.3.0-6-generic 
root=UUID=c8c33dea-5f04-4670-84f3-daf1d956e6b8 ro quiet splash vt.handoff=7
  SourcePackage: linux
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/10/2011
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 5CKT69AUS
  dmi.board.name: LENOVO
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: NONE
  dmi.modalias: 
dmi:bvnLENOVO:bvr5CKT69AUS:bd01/10/2011:svnLENOVO:pn6234A1U:pvrThinkCentreM58p:rvnLENOVO:rnLENOVO:rvrNONE:cvnLENOVO:ct3:cvrNONE:
  dmi.product.name: 6234A1U
  dmi.product.version: ThinkCentre M58p
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1536841/+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 1578178] [NEW] Caller ID not displayed using in-car bluetooth system when recieving a call

Public bug reported:

When the phone is connected to the in-car hands free bluetooth system and I 
receive a call, I expect the caller ID to be displayed in the car's 
infotainment system. This was working until OTA9, which has made the system 
display "Unknown" when receiving a call.
I can use the phone's contacts from the car, so no everything is broken in that 
respect.

Would a verbose bluetooth log be helpful
(https://wiki.ubuntu.com/DebuggingBluetooth), or would something else be
required to help further investigate?

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

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

Title:
  Caller ID not displayed using in-car bluetooth system when recieving a
  call

Status in bluez package in Ubuntu:
  New

Bug description:
  When the phone is connected to the in-car hands free bluetooth system and I 
receive a call, I expect the caller ID to be displayed in the car's 
infotainment system. This was working until OTA9, which has made the system 
display "Unknown" when receiving a call.
  I can use the phone's contacts from the car, so no everything is broken in 
that respect.

  Would a verbose bluetooth log be helpful
  (https://wiki.ubuntu.com/DebuggingBluetooth), or would something else
  be required to help further investigate?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1578178/+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 1559308] Re: Plugging HDMI screen in causes system hang

2016-05-04 Thread Koen Roggemans

In comment #8 it's mentioned that it is not fixed in 4.4.0-22. I hope that's a 
typo :-(
I have a crashing 4.4.0-21 (Thinkpad 13 with an Intel N3150 processor / HD 510 
Graphics) 
My workaround is installing kernel 4.6RC6

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

Title:
  Plugging HDMI screen in causes system hang

Status in linux package in Ubuntu:
  Fix Committed

Bug description:
  I have a 4K UHD laptop screen and am running Ubuntu Gnome 16.04 Beta1
  using 4.4.0-13-generic and the Nouveau drivers.

  If I plug in an external HDMI monitor (FHD) either into either HDMI
  port (there's one on the machine and there's one available via a usb
  3.1 extra adaptor) then the whole system hangs, completely
  unresponsive and needing a hard reboot. Before hanging the 2nd display
  gets an image as expected, but the laptop's screen flashes randomly,
  sometimes you see weird artifacts. Then the hang comes.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xserver-xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-13.29-generic 4.4.5
  Uname: Linux 4.4.0-13-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: GNOME
  Date: Fri Mar 18 20:43:42 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Skylake Integrated Graphics [8086:191b] (rev 06) (prog-if 
00 [VGA controller])
 Subsystem: Dell Skylake Integrated Graphics [1028:06e4]
 Subsystem: Dell GM107M [GeForce GTX 960M] [1028:06e4]
  InstallationDate: Installed on 2016-03-15 (3 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Alpha amd64 
(20160225.1)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 04f3:21d5 Elan Microelectronics Corp. 
   Bus 001 Device 002: ID 0a5c:6410 Broadcom Corp. 
   Bus 001 Device 004: ID 0c45:6713 Microdia 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. XPS 15 9550
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-13-generic.efi.signed 
root=UUID=b026feed-8801-44f4-9f3f-c245f4a1f25e ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/25/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 01.01.19
  dmi.board.name: 0N7TVV
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr01.01.19:bd01/25/2016:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0N7TVV:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 15 9550
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.1.2-1ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.1.2-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.1-1ubuntu4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.6.1-1ubuntu2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160218-1ubuntu3
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Fri Mar 18 17:28:07 2016
  xserver.configfile: default
  xserver.errors:
   Failed to load module "nvidia" (module does not exist, 0)
   Failed to load module "nvidia" (module does not exist, 0)
   Unknown chipset: NV117
   SynPS/2 Synaptics TouchPad: Read error 19
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id5182 
   vendor SHP
  xserver.version: 2:1.18.1-1ubuntu4

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1559308/+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 1575148] Re: Ubuntu 16.04 with kernel 4.4.0.21 does not recognize at all the nvidia card of a macbook pro 11, 1

2016-05-04 Thread Albert

More details: upon resume from sleep, after pluging in an external
monitor to be able to trigger whatever makes the screen come up, the tty
1 shows the following:

Ubuntu 16.04 LTS metall tty1
metall login: [ 7875.907520] xhci_hcd :00:14.0: Command comp
letion event does not match command
[ 7876.111524] usb 2-3: device not accepting address 4, error -62
[ 7880.915458] xhci_hcd :00:14.0: Error while assigning device slot ID
[ 7880.915482] xhci_hcd :00:14.0: Max number of devices this xHCI host 
supports is 32.
[ 7880.915504] usb usb1-port1: couldn't allocate usb_device
[ 7886.707269] xhci_hcd :00:14.0: Command completion event does not match 
command
[ 7892.126537] usb 2-3: device not accepting address 5, error -62


For comparison, the "lsusb" command prints:

$ lsusb 
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 003: ID 05ac:0259 Apple, Inc. 
Bus 001 Device 006: ID 05ac:8289 Apple, Inc. 
Bus 001 Device 002: ID 0a5c:4500 Broadcom Corp. BCM2046B1 USB 2.0 Hub (part of 
BCM2046 Bluetooth)
Bus 001 Device 007: ID 413c:3016 Dell Computer Corp. Optical 5-Button Wheel 
Mouse
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub


Of note: when the screen is black, the keyboard LED lighting doesn't come up 
either.

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

Title:
  Ubuntu 16.04 with kernel 4.4.0.21 does not recognize at all the nvidia
  card of a macbook pro 11,1

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  This macbook pro 11,1 has two cards:

  1. An nvidia card, which was both recognized in Ubuntu 14.04 with
  kernels 3.13.*, and worked well using the provided drivers under
  "Additional drivers".

  2. An intel integrated card, which was not in use under Ubuntu 14.04, but 
which now, under ubuntu 16.04, is the only card in use. The 'lspci' command 
states:
  00:02.0 VGA compatible controller [0300]: Intel Corporation Haswell-ULT 
Integrated Graphics Controller [8086:0a2e] (rev 09)

  ... and there is no trace at all of the nvidia card under lspci.

  dmesg shows one crytic message, perhaps indicating that the nvidia
  card could not be recognized:

  [0.190838] pci :00:02.0: Video device with shadowed ROM

  dmesg lists a number of "failed" entries, such as:

  [   11.791463] usb 1-3: hub failed to enable device, error -62

  [   24.891009] wl: module verification failed: signature and/or
  required key missing - tainting kernel

  ... and also:

  [0.190096] pci :06:00.0: BAR 15: no space for [mem size 0x0020 
64bit pref]
  [0.190098] pci :06:00.0: BAR 15: failed to assign [mem size 
0x0020 64bit pref]
  [0.190099] pci :06:04.0: BAR 14: no space for [mem size 0x0020]
  [0.190100] pci :06:04.0: BAR 14: failed to assign [mem size 
0x0020]
  [0.190102] pci :06:04.0: BAR 15: no space for [mem size 0x0020 
64bit pref]
  [0.190103] pci :06:04.0: BAR 15: failed to assign [mem size 
0x0020 64bit pref]
  [0.190104] pci :06:06.0: BAR 14: no space for [mem size 0x0020]
  [0.190105] pci :06:06.0: BAR 14: failed to assign [mem size 
0x0020]
  [0.190107] pci :06:06.0: BAR 15: no space for [mem size 0x0020 
64bit pref]
  [0.190108] pci :06:06.0: BAR 15: failed to assign [mem size 
0x0020 64bit pref]
  [0.190109] pci :06:00.0: BAR 13: no space for [io  size 0x1000]
  [0.190110] pci :06:00.0: BAR 13: failed to assign [io  size 0x1000]
  [0.190111] pci :06:04.0: BAR 13: no space for [io  size 0x1000]
  [0.190112] pci :06:04.0: BAR 13: failed to assign [io  size 0x1000]
  [0.190113] pci :06:06.0: BAR 13: no space for [io  size 0x1000]
  [0.190114] pci :06:06.0: BAR 13: failed to assign [io  size 0x1000]
  [0.190116] pci :06:06.0: BAR 14: no space for [mem size 0x0020]
  [0.190117] pci :06:06.0: BAR 14: failed to assign [mem size 
0x0020]
  [0.190119] pci :06:06.0: BAR 15: no space for [mem size 0x0020 
64bit pref]
  [0.190120] pci :06:06.0: BAR 15: failed to assign [mem size 
0x0020 64bit pref]
  [0.190121] pci :06:06.0: BAR 13: no space for [io  size 0x1000]
  [0.190122] pci :06:06.0: BAR 13: failed to assign [io  size 0x1000]
  [0.190124] pci :06:04.0: BAR 14: no space for [mem size 0x0020]
  [0.190125] pci :06:04.0: BAR 14: failed to assign [mem size 
0x0020]
  [0.190126] pci :06:04.0: BAR 15: no space for [mem size 0x0020 
64bit pref]
  [0.190127] pci :06:04.0: BAR 15: failed to assign [mem size 
0x0020 64bit pref]
  [0.190129] pci :06:04.0: BAR 13: no space for [io  size 0x1000]
  [0.190130] pci :06:04.0: BAR 13: failed to assign [io  size 0x1000]
  [0.190131] pci :06:00.0: BAR 15: no space for [mem size 0x0020

[Kernel-packages] [Bug 1539158] Re: Unable to pair with in-car hands-free system after OTA-9 update

You are welcome. Let me know if you need me to test something else.
I have also opened 2 new tickets for the 2 "downstream" reported issues:

https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1578176
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1578178

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

Title:
  Unable to pair with in-car hands-free system after OTA-9 update

Status in Canonical System Image:
  Confirmed
Status in bluez package in Ubuntu:
  Confirmed
Status in ubuntu-system-settings package in Ubuntu:
  Confirmed

Bug description:
  After OTA-9 I started having trouble with my bluetooth connection to the car 
hands-free system (no sound, and incoming calls no longer displayed the 
number), so I have reset both the car and the phone connections (eg. forgot the 
devices).
  Now I can't even pair the phone with the car's system. 
  The car finds the phone, and then asks me to enter the code "" to pair 
the device, but after a few moments, it just says the connection failed and 
asks me to try again. Which fails again.

  It was working fine just before the update.

  Any logs I should post to help debug?

  PS - The car is a 2015 Honda Civic Tourer, if that matters.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1539158/+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 1577905] Re: Dell TB15 audio is distorted

Soon to be released in Ubuntu-4.4.0-22.38 (via v4.4.8 stable)

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

Title:
  Dell  TB15 audio is distorted

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

Bug description:
  On the Dell TB15 and Dell WD15 docks, analogue audio output is
  distorted.  This is because of a missing driver quirk on docks.

  It has been fixed upstream here.
  
http://git.kernel.org/cgit/linux/kernel/git/tiwai/sound.git/commit/?id=adcdd0d5a1cb779f6d455ae70882c19c527627a8

  Please backport it into Ubuntu.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1577905/+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 1577905] Re: Dell TB15 audio is distorted

via 3.19.8-ckt20 stable

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

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

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

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

Title:
  Dell  TB15 audio is distorted

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Trusty:
  Confirmed
Status in linux source package in Vivid:
  Fix Committed
Status in linux source package in Wily:
  New
Status in linux source package in Xenial:
  Fix Released

Bug description:
  On the Dell TB15 and Dell WD15 docks, analogue audio output is
  distorted.  This is because of a missing driver quirk on docks.

  It has been fixed upstream here.
  
http://git.kernel.org/cgit/linux/kernel/git/tiwai/sound.git/commit/?id=adcdd0d5a1cb779f6d455ae70882c19c527627a8

  Please backport it into Ubuntu.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1577905/+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 1578022] Re: dmidecode fails to output smibios 3.0 info

2016-05-04 Thread Jeff Lane

We found this during certification testing of a couple models from one
OEM that apparently use SMIBIOS 3.0.

The failed test shows this in the output:

mmap: Can't map beyond end of file /sys/firmware/dmi/tables/DMI
Table is unreachable, sorry.
*** Incorrect or unknown server chassis type!

Failed 1 test (see above)

We also capture output of dmidecode in the test logs, on the 3.0 system
this is all we get in output:

# dmidecode 3.0
Getting SMBIOS data from sysfs.
SMBIOS 3.0.0 present.
Table at 0x7BB4E000.

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

** Tags added: hwcert-server

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

Title:
  dmidecode fails to output smibios 3.0 info

Status in dmidecode package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 16.04, dmidecode 3.0-2 can display smibios 2.8 but not smibios
  3.0. Rhel 7.2 can display smibios 3.0 on the same system without a
  problem.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dmidecode/+bug/1578022/+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 1577905] Re: Dell TB15 audio is distorted

via 4.2.8-ckt9 stable

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

** Also affects: linux (Ubuntu Yakkety)
   Importance: Undecided
   Status: 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/1577905

Title:
  Dell  TB15 audio is distorted

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Trusty:
  Confirmed
Status in linux source package in Vivid:
  Fix Committed
Status in linux source package in Wily:
  Fix Committed
Status in linux source package in Xenial:
  Fix Released
Status in linux source package in Yakkety:
  Fix Released

Bug description:
  On the Dell TB15 and Dell WD15 docks, analogue audio output is
  distorted.  This is because of a missing driver quirk on docks.

  It has been fixed upstream here.
  
http://git.kernel.org/cgit/linux/kernel/git/tiwai/sound.git/commit/?id=adcdd0d5a1cb779f6d455ae70882c19c527627a8

  Please backport it into Ubuntu.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1577905/+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 1577905] Re: Dell TB15 audio is distorted

v4.6-rc4~18^2~2

** Changed in: linux (Ubuntu Yakkety)
   Status: Confirmed => 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/1577905

Title:
  Dell  TB15 audio is distorted

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Trusty:
  Confirmed
Status in linux source package in Vivid:
  Fix Committed
Status in linux source package in Wily:
  Fix Committed
Status in linux source package in Xenial:
  Fix Released
Status in linux source package in Yakkety:
  Fix Released

Bug description:
  On the Dell TB15 and Dell WD15 docks, analogue audio output is
  distorted.  This is because of a missing driver quirk on docks.

  It has been fixed upstream here.
  
http://git.kernel.org/cgit/linux/kernel/git/tiwai/sound.git/commit/?id=adcdd0d5a1cb779f6d455ae70882c19c527627a8

  Please backport it into Ubuntu.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1577905/+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 1577898] Re: thunderbolt hotplug is broken

2016-05-04 Thread Mario Limonciello

Here is the patch as submitted to LKML from ACPICA:
http://www.spinics.net/lists/linux-acpi/msg65737.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/1577898

Title:
  thunderbolt hotplug is broken

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Trusty:
  Confirmed
Status in linux source package in Xenial:
  Confirmed

Bug description:
  Thunderbolt hotplug is broken on type-c ports.  Redhat already
  submitted a patch for this that was accepted into upstream ACPICA, but
  it needs to be backported into Ubuntu's kernel.

  I've verified that the patch works properly using a type-C USB
  Ethernet dongle as well as hot-plugging a Dell TB15 dock.

  http://www.spinics.net/lists/linux-acpi/msg65578.html

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1577898/+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 1578022] Re: dmidecode fails to output smibios 3.0 info

2016-05-04 Thread Colin Ian King

Can you supply some more information:

1. Which kernels were being used?  (RH 7.2 and Ubuntu)

2.  Can you tar up the /sys/firmware directory on both systems so I can
see if there any obvious differences at the interface level.

You will need to do that as root to be able to read the data.

Thanks


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

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

** Changed in: dmidecode (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 dmidecode in Ubuntu.
https://bugs.launchpad.net/bugs/1578022

Title:
  dmidecode fails to output smibios 3.0 info

Status in dmidecode package in Ubuntu:
  In Progress

Bug description:
  Ubuntu 16.04, dmidecode 3.0-2 can display smibios 2.8 but not smibios
  3.0. Rhel 7.2 can display smibios 3.0 on the same system without a
  problem.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dmidecode/+bug/1578022/+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 1573062] Re: memory_stress_ng failing for IBM Power S812LC(TN71-BP012) for 16.04

2016-05-04 Thread Mike Rushton

Confirmed the above kernel fails in the same manner.

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

Title:
  memory_stress_ng failing for IBM Power S812LC(TN71-BP012) for 16.04

Status in linux package in Ubuntu:
  Triaged

Bug description:
  memory_stress_ng, as part of server certification is failing for IBM
  Power S812LC(TN71-BP012) in bare metal mode. Failing in this case is
  defined by the test locking up the server in an unrecoverable state
  which only a reboot will fix.

  I will be attaching screen and kern logs for the failures and a
  successful run on 14.04 on the same server.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1573062/+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 1567418] Re: intel_modeset_check_state+0x88e/0x8a0 [i915_bpo]

Sorry I spoke too soon -- I still get the error, it just took longer to
show up :(

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

Title:
  intel_modeset_check_state+0x88e/0x8a0 [i915_bpo]

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Hi,

  I'm using a new Skylake Thinkpad T460s with and external monitor
  connected via Displayport and Ubuntu 16.04 and the latest kernel as of
  today: Linux test 4.4.0-17-generic #33-Ubuntu SMP Tue Mar 29 17:17:28
  UTC 2016 x86_64 x86_64 x86_64 GNU/Linux

  X will from time to time lock up when the computer is left idle for a
  long time and both displays (laptop and external) go to sleep and then
  woken up.

  Apr  6 22:46:16 test kernel: [ 9191.647675] [ cut here 
]
  Apr  6 22:46:16 test kernel: [ 9191.647700] WARNING: CPU: 2 PID: 1152 at 
/build/linux-YiIlnA/linux-4.4.0/ubuntu/i915/intel_display.c:12843 
intel_modeset_check_state+0x88e/0x8a0 [i915_bpo]()
  Apr  6 22:46:16 test kernel: [ 9191.647701] encoder detached but still 
enabled on pipe B.
  Apr  6 22:46:16 test kernel: [ 9191.647701] Modules linked in: msr pci_stub 
vboxpci(OE) vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) bnep uvcvideo 
videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 videobuf2_core v4l2_common 
videodev media snd_usb_audio snd_usbmidi_lib btusb btrtl btbcm btintel 
bluetooth binfmt_misc nls_iso8859_1 arc4 snd_hda_codec_hdmi 
snd_hda_codec_realtek intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp 
snd_hda_codec_generic snd_soc_skl snd_soc_skl_ipc iwlmvm snd_hda_ext_core 
snd_soc_sst_ipc snd_soc_sst_dsp snd_soc_core mac80211 snd_compress ac97_bus 
snd_pcm_dmaengine dw_dmac_core snd_hda_intel snd_seq_midi snd_seq_midi_event 
snd_hda_codec snd_hda_core snd_rawmidi snd_hwdep joydev input_leds iwlwifi 
serio_raw rtsx_pci_ms memstick snd_pcm thinkpad_acpi cfg80211 nvram mei_me 
shpchp mei snd_seq snd_seq_device snd_timer snd soundcore mac_hid tpm_crb 
kvm_intel kvm irqbypass parport_pc ppdev lp parport autofs4 drbg ansi_cprng 
algif_skcipher af_alg dm_crypt hid_mi
 crosoft hid_generic usbhid hid rtsx_pci_sdmmc i915_bpo crct10dif_pclmul 
crc32_pclmul aesni_intel aes_x86_64 lrw gf128mul glue_helper ablk_helper 
intel_ips cryptd i2c_algo_bit drm_kms_helper syscopyarea sysfillrect sysimgblt 
e1000e nvme psmouse fb_sys_fops ptp drm pps_core rtsx_pci wmi video fjes
  Apr  6 22:46:16 test kernel: [ 9191.647744] CPU: 2 PID: 1152 Comm: Xorg 
Tainted: GW  OE   4.4.0-17-generic #33-Ubuntu
  Apr  6 22:46:16 test kernel: [ 9191.647745] Hardware name: LENOVO 
20F9CTO1WW/20F9CTO1WW, BIOS N1CET40W (1.08 ) 03/09/2016
  Apr  6 22:46:16 test kernel: [ 9191.647746]  0286 
98929f69 8804ff7a3ac0 813e8123
  Apr  6 22:46:16 test kernel: [ 9191.647747]  8804ff7a3b08 
c0324498 8804ff7a3af8 8107fe12
  Apr  6 22:46:16 test kernel: [ 9191.647749]  880502bfeb18 
880502e3e000 880502bfeb48 880502bfeb30
  Apr  6 22:46:16 test kernel: [ 9191.647750] Call Trace:
  Apr  6 22:46:16 test kernel: [ 9191.647753]  [] 
dump_stack+0x63/0x90
  Apr  6 22:46:16 test kernel: [ 9191.647756]  [] 
warn_slowpath_common+0x82/0xc0
  Apr  6 22:46:16 test kernel: [ 9191.647757]  [] 
warn_slowpath_fmt+0x5c/0x80
  Apr  6 22:46:16 test kernel: [ 9191.647773]  [] 
intel_modeset_check_state+0x88e/0x8a0 [i915_bpo]
  Apr  6 22:46:16 test kernel: [ 9191.647788]  [] 
intel_atomic_commit+0x943/0xdb0 [i915_bpo]
  Apr  6 22:46:16 test kernel: [ 9191.647791]  [] ? 
wake_atomic_t_function+0x60/0x60
  Apr  6 22:46:16 test kernel: [ 9191.647803]  [] ? 
drm_atomic_check_only+0x18e/0x590 [drm]
  Apr  6 22:46:16 test kernel: [ 9191.647811]  [] 
drm_atomic_commit+0x37/0x60 [drm]
  Apr  6 22:46:16 test kernel: [ 9191.647817]  [] 
drm_atomic_helper_set_config+0x76/0xb0 [drm_kms_helper]
  Apr  6 22:46:16 test kernel: [ 9191.647825]  [] 
drm_mode_set_config_internal+0x62/0x100 [drm]
  Apr  6 22:46:16 test kernel: [ 9191.647833]  [] 
drm_mode_setcrtc+0x3d2/0x4f0 [drm]
  Apr  6 22:46:16 test kernel: [ 9191.647839]  [] 
drm_ioctl+0x152/0x540 [drm]
  Apr  6 22:46:16 test kernel: [ 9191.647841]  [] ? 
__set_current_blocked+0x36/0x60
  Apr  6 22:46:16 test kernel: [ 9191.647848]  [] ? 
drm_mode_setplane+0x1b0/0x1b0 [drm]
  Apr  6 22:46:16 test kernel: [ 9191.647851]  [] 
do_vfs_ioctl+0x29f/0x490
  Apr  6 22:46:16 test kernel: [ 9191.647853]  [] ? 
fpu__restore_sig+0x4d/0x60
  Apr  6 22:46:16 test kernel: [ 9191.647854]  [] 
SyS_ioctl+0x79/0x90
  Apr  6 22:46:16 test kernel: [ 9191.647857]  [] 
entry_SYSCALL_64_fastpath+0x16/0x71
  Apr  6 22:46:16 test kernel: [ 9191.647858] ---[ end trace 04fd011c68d81b00 
]---
  Apr  6 22:46:16 test kernel: [ 9191.823700] [ cut here 
]

  
  Attached is the full kernel log from boot until the issue happens, at which 
point, if I have a lockup of X I need to reboot to get back to

[Kernel-packages] [Bug 1567418] Re: intel_modeset_check_state+0x88e/0x8a0 [i915_bpo]

I had this issue too with a new Dell Precision 5510 and 16.04 (also
Skylake).

I found setting  i915_bpo.preliminary_hw_support=1 seems to help -- any
chance that works for you too?

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

Title:
  intel_modeset_check_state+0x88e/0x8a0 [i915_bpo]

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Hi,

  I'm using a new Skylake Thinkpad T460s with and external monitor
  connected via Displayport and Ubuntu 16.04 and the latest kernel as of
  today: Linux test 4.4.0-17-generic #33-Ubuntu SMP Tue Mar 29 17:17:28
  UTC 2016 x86_64 x86_64 x86_64 GNU/Linux

  X will from time to time lock up when the computer is left idle for a
  long time and both displays (laptop and external) go to sleep and then
  woken up.

  Apr  6 22:46:16 test kernel: [ 9191.647675] [ cut here 
]
  Apr  6 22:46:16 test kernel: [ 9191.647700] WARNING: CPU: 2 PID: 1152 at 
/build/linux-YiIlnA/linux-4.4.0/ubuntu/i915/intel_display.c:12843 
intel_modeset_check_state+0x88e/0x8a0 [i915_bpo]()
  Apr  6 22:46:16 test kernel: [ 9191.647701] encoder detached but still 
enabled on pipe B.
  Apr  6 22:46:16 test kernel: [ 9191.647701] Modules linked in: msr pci_stub 
vboxpci(OE) vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) bnep uvcvideo 
videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 videobuf2_core v4l2_common 
videodev media snd_usb_audio snd_usbmidi_lib btusb btrtl btbcm btintel 
bluetooth binfmt_misc nls_iso8859_1 arc4 snd_hda_codec_hdmi 
snd_hda_codec_realtek intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp 
snd_hda_codec_generic snd_soc_skl snd_soc_skl_ipc iwlmvm snd_hda_ext_core 
snd_soc_sst_ipc snd_soc_sst_dsp snd_soc_core mac80211 snd_compress ac97_bus 
snd_pcm_dmaengine dw_dmac_core snd_hda_intel snd_seq_midi snd_seq_midi_event 
snd_hda_codec snd_hda_core snd_rawmidi snd_hwdep joydev input_leds iwlwifi 
serio_raw rtsx_pci_ms memstick snd_pcm thinkpad_acpi cfg80211 nvram mei_me 
shpchp mei snd_seq snd_seq_device snd_timer snd soundcore mac_hid tpm_crb 
kvm_intel kvm irqbypass parport_pc ppdev lp parport autofs4 drbg ansi_cprng 
algif_skcipher af_alg dm_crypt hid_mi
 crosoft hid_generic usbhid hid rtsx_pci_sdmmc i915_bpo crct10dif_pclmul 
crc32_pclmul aesni_intel aes_x86_64 lrw gf128mul glue_helper ablk_helper 
intel_ips cryptd i2c_algo_bit drm_kms_helper syscopyarea sysfillrect sysimgblt 
e1000e nvme psmouse fb_sys_fops ptp drm pps_core rtsx_pci wmi video fjes
  Apr  6 22:46:16 test kernel: [ 9191.647744] CPU: 2 PID: 1152 Comm: Xorg 
Tainted: GW  OE   4.4.0-17-generic #33-Ubuntu
  Apr  6 22:46:16 test kernel: [ 9191.647745] Hardware name: LENOVO 
20F9CTO1WW/20F9CTO1WW, BIOS N1CET40W (1.08 ) 03/09/2016
  Apr  6 22:46:16 test kernel: [ 9191.647746]  0286 
98929f69 8804ff7a3ac0 813e8123
  Apr  6 22:46:16 test kernel: [ 9191.647747]  8804ff7a3b08 
c0324498 8804ff7a3af8 8107fe12
  Apr  6 22:46:16 test kernel: [ 9191.647749]  880502bfeb18 
880502e3e000 880502bfeb48 880502bfeb30
  Apr  6 22:46:16 test kernel: [ 9191.647750] Call Trace:
  Apr  6 22:46:16 test kernel: [ 9191.647753]  [] 
dump_stack+0x63/0x90
  Apr  6 22:46:16 test kernel: [ 9191.647756]  [] 
warn_slowpath_common+0x82/0xc0
  Apr  6 22:46:16 test kernel: [ 9191.647757]  [] 
warn_slowpath_fmt+0x5c/0x80
  Apr  6 22:46:16 test kernel: [ 9191.647773]  [] 
intel_modeset_check_state+0x88e/0x8a0 [i915_bpo]
  Apr  6 22:46:16 test kernel: [ 9191.647788]  [] 
intel_atomic_commit+0x943/0xdb0 [i915_bpo]
  Apr  6 22:46:16 test kernel: [ 9191.647791]  [] ? 
wake_atomic_t_function+0x60/0x60
  Apr  6 22:46:16 test kernel: [ 9191.647803]  [] ? 
drm_atomic_check_only+0x18e/0x590 [drm]
  Apr  6 22:46:16 test kernel: [ 9191.647811]  [] 
drm_atomic_commit+0x37/0x60 [drm]
  Apr  6 22:46:16 test kernel: [ 9191.647817]  [] 
drm_atomic_helper_set_config+0x76/0xb0 [drm_kms_helper]
  Apr  6 22:46:16 test kernel: [ 9191.647825]  [] 
drm_mode_set_config_internal+0x62/0x100 [drm]
  Apr  6 22:46:16 test kernel: [ 9191.647833]  [] 
drm_mode_setcrtc+0x3d2/0x4f0 [drm]
  Apr  6 22:46:16 test kernel: [ 9191.647839]  [] 
drm_ioctl+0x152/0x540 [drm]
  Apr  6 22:46:16 test kernel: [ 9191.647841]  [] ? 
__set_current_blocked+0x36/0x60
  Apr  6 22:46:16 test kernel: [ 9191.647848]  [] ? 
drm_mode_setplane+0x1b0/0x1b0 [drm]
  Apr  6 22:46:16 test kernel: [ 9191.647851]  [] 
do_vfs_ioctl+0x29f/0x490
  Apr  6 22:46:16 test kernel: [ 9191.647853]  [] ? 
fpu__restore_sig+0x4d/0x60
  Apr  6 22:46:16 test kernel: [ 9191.647854]  [] 
SyS_ioctl+0x79/0x90
  Apr  6 22:46:16 test kernel: [ 9191.647857]  [] 
entry_SYSCALL_64_fastpath+0x16/0x71
  Apr  6 22:46:16 test kernel: [ 9191.647858] ---[ end trace 04fd011c68d81b00 
]---
  Apr  6 22:46:16 test kernel: [ 9191.823700] [ cut here 
]

  
  Attached is the full kernel log from boo

[Kernel-packages] [Bug 1578256] [NEW] wifi not working in acer E 15

2016-05-04 Thread Himanshu39

Public bug reported:

wifi in not working on my acer Aspire E 15 need help.

rfkill list all
0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
1: acer-wireless: Wireless LAN
Soft blocked: no
Hard blocked: no
lspci
00:00.0 Host bridge: Intel Corporation Haswell-ULT DRAM Controller (rev 0b)
00:02.0 VGA compatible controller: Intel Corporation Haswell-ULT Integrated 
Graphics Controller (rev 0b)
00:03.0 Audio device: Intel Corporation Haswell-ULT HD Audio Controller (rev 0b)
00:14.0 USB controller: Intel Corporation Lynx Point-LP USB xHCI HC (rev 04)
00:1b.0 Audio device: Intel Corporation Lynx Point-LP HD Audio Controller (rev 
04)
00:1c.0 PCI bridge: Intel Corporation Lynx Point-LP PCI Express Root Port 1 
(rev e4)
00:1c.2 PCI bridge: Intel Corporation Lynx Point-LP PCI Express Root Port 3 
(rev e4)
00:1c.3 PCI bridge: Intel Corporation Lynx Point-LP PCI Express Root Port 4 
(rev e4)
00:1d.0 USB controller: Intel Corporation Lynx Point-LP USB EHCI #1 (rev 04)
00:1f.0 ISA bridge: Intel Corporation Lynx Point-LP LPC Controller (rev 04)
00:1f.2 SATA controller: Intel Corporation Lynx Point-LP SATA Controller 1 
[AHCI mode] (rev 04)
00:1f.3 SMBus: Intel Corporation Lynx Point-LP SMBus Controller (rev 04)
02:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 
PCI Express Gigabit Ethernet Controller (rev 15)
03:00.0 Network controller: Qualcomm Atheros Device 0042 (rev 30)

using ubuntu 14.04
Ubuntu 3.13.0-86.130-generic 3.13.11-ckt39
wifi connections are not showing under connection area.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: linux-image-3.13.0-86-generic 3.13.0-86.130
ProcVersionSignature: Ubuntu 3.13.0-86.130-generic 3.13.11-ckt39
Uname: Linux 3.13.0-86-generic x86_64
ApportVersion: 2.14.1-0ubuntu3
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  railyatri   2081 F pulseaudio
 /dev/snd/controlC0:  railyatri   2081 F pulseaudio
CurrentDesktop: Unity
Date: Wed May  4 20:14:31 2016
HibernationDevice: RESUME=UUID=15d78b99-e6fc-4078-ac51-a2b37365b776
InstallationDate: Installed on 2016-05-02 (1 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
IwConfig:
 eth0  no wireless extensions.
 
 lono wireless extensions.
MachineType: Acer Aspire E5-573
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-86-generic 
root=UUID=8f0d504d-6746-42b4-a216-f654f55cf52e ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-3.13.0-86-generic N/A
 linux-backports-modules-3.13.0-86-generic  N/A
 linux-firmware 1.127
SourcePackage: linux
StagingDrivers: rts5139
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/30/2015
dmi.bios.vendor: Insyde Corp.
dmi.bios.version: V1.35
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: ZORO_BH
dmi.board.vendor: Acer
dmi.board.version: Type2 - A01 Board Version
dmi.chassis.type: 10
dmi.chassis.vendor: Chassis Manufacturer
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.35:bd11/30/2015:svnAcer:pnAspireE5-573:pvrV3.72:rvnAcer:rnZORO_BH:rvrType2-A01BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion:
dmi.product.name: Aspire E5-573
dmi.product.version: V3.72
dmi.sys.vendor: Acer

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


** Tags: amd64 apport-bug package-from-proposed staging 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/1578256

Title:
  wifi not working in acer E 15

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  wifi in not working on my acer Aspire E 15 need help.

  rfkill list all
  0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  1: acer-wireless: Wireless LAN
Soft blocked: no
Hard blocked: no
  lspci
  00:00.0 Host bridge: Intel Corporation Haswell-ULT DRAM Controller (rev 0b)
  00:02.0 VGA compatible controller: Intel Corporation Haswell-ULT Integrated 
Graphics Controller (rev 0b)
  00:03.0 Audio device: Intel Corporation Haswell-ULT HD Audio Controller (rev 
0b)
  00:14.0 USB controller: Intel Corporation Lynx Point-LP USB xHCI HC (rev 04)
  00:1b.0 Audio device: Intel Corporation Lynx Point-LP HD Audio Controller 
(rev 04)
  00:1c.0 PCI bridge: Intel Corporation Lynx Point-LP PCI Express Root Port 1 
(rev e4)
  00:1c.2 PCI bridge: Intel Corporation Lynx Point-LP PCI Express Root Port 3 
(rev e4)
  00:1c.3 PCI bridge: Intel Corporation Lynx Point-LP PCI Express Root Port 4 
(rev e4)
  00:1d.0 USB controller: Intel Corporation Lynx Point-LP USB EHCI #1 (rev 04)
  00:1f.0 ISA bridge: Intel Corporation Lynx Point-LP LPC Controller (rev 04)
  00:1f.2 SATA controller: Intel Corporation Lynx Point-LP SATA Controller 1 
[AHCI mode] (rev 04)
  00:1f.3 SMBus: Intel Cor

[Kernel-packages] [Bug 1578256] 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/1578256

Title:
  wifi not working in acer E 15

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  wifi in not working on my acer Aspire E 15 need help.

  rfkill list all
  0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  1: acer-wireless: Wireless LAN
Soft blocked: no
Hard blocked: no
  lspci
  00:00.0 Host bridge: Intel Corporation Haswell-ULT DRAM Controller (rev 0b)
  00:02.0 VGA compatible controller: Intel Corporation Haswell-ULT Integrated 
Graphics Controller (rev 0b)
  00:03.0 Audio device: Intel Corporation Haswell-ULT HD Audio Controller (rev 
0b)
  00:14.0 USB controller: Intel Corporation Lynx Point-LP USB xHCI HC (rev 04)
  00:1b.0 Audio device: Intel Corporation Lynx Point-LP HD Audio Controller 
(rev 04)
  00:1c.0 PCI bridge: Intel Corporation Lynx Point-LP PCI Express Root Port 1 
(rev e4)
  00:1c.2 PCI bridge: Intel Corporation Lynx Point-LP PCI Express Root Port 3 
(rev e4)
  00:1c.3 PCI bridge: Intel Corporation Lynx Point-LP PCI Express Root Port 4 
(rev e4)
  00:1d.0 USB controller: Intel Corporation Lynx Point-LP USB EHCI #1 (rev 04)
  00:1f.0 ISA bridge: Intel Corporation Lynx Point-LP LPC Controller (rev 04)
  00:1f.2 SATA controller: Intel Corporation Lynx Point-LP SATA Controller 1 
[AHCI mode] (rev 04)
  00:1f.3 SMBus: Intel Corporation Lynx Point-LP SMBus Controller (rev 04)
  02:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. 
RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 15)
  03:00.0 Network controller: Qualcomm Atheros Device 0042 (rev 30)

  using ubuntu 14.04
  Ubuntu 3.13.0-86.130-generic 3.13.11-ckt39
  wifi connections are not showing under connection area.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-86-generic 3.13.0-86.130
  ProcVersionSignature: Ubuntu 3.13.0-86.130-generic 3.13.11-ckt39
  Uname: Linux 3.13.0-86-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  railyatri   2081 F pulseaudio
   /dev/snd/controlC0:  railyatri   2081 F pulseaudio
  CurrentDesktop: Unity
  Date: Wed May  4 20:14:31 2016
  HibernationDevice: RESUME=UUID=15d78b99-e6fc-4078-ac51-a2b37365b776
  InstallationDate: Installed on 2016-05-02 (1 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  IwConfig:
   eth0  no wireless extensions.
   
   lono wireless extensions.
  MachineType: Acer Aspire E5-573
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-86-generic 
root=UUID=8f0d504d-6746-42b4-a216-f654f55cf52e ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-86-generic N/A
   linux-backports-modules-3.13.0-86-generic  N/A
   linux-firmware 1.127
  SourcePackage: linux
  StagingDrivers: rts5139
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/30/2015
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.35
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: ZORO_BH
  dmi.board.vendor: Acer
  dmi.board.version: Type2 - A01 Board Version
  dmi.chassis.type: 10
  dmi.chassis.vendor: Chassis Manufacturer
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.35:bd11/30/2015:svnAcer:pnAspireE5-573:pvrV3.72:rvnAcer:rnZORO_BH:rvrType2-A01BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion:
  dmi.product.name: Aspire E5-573
  dmi.product.version: V3.72
  dmi.sys.vendor: Acer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1578256/+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 1559576] Re: Ubuntu GNOME boots to black screen when using proprietary Nvidia drivers on a laptop with Optimus

2016-05-04 Thread Tassos

I upgraded the following packages on 2016.5.3:

nvidia-common:amd64 (1:0.4.17, 1:0.4.17.1), ubuntu-drivers-common:amd64
(1:0.4.17, 1:0.4.17.1)

And the black screen showed up again. I had to switch back to lightdm to
login. Hope this information 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/1559576

Title:
  Ubuntu GNOME boots to black screen when using proprietary Nvidia
  drivers on a laptop with Optimus

Status in gdm:
  Confirmed
Status in Ubuntu GNOME:
  Triaged
Status in gdm3 package in Ubuntu:
  Triaged
Status in linux package in Ubuntu:
  Invalid
Status in gdm3 source package in Xenial:
  Triaged
Status in linux source package in Xenial:
  Invalid

Bug description:
  Using latest Ubuntu Gnome x64 daily build with all updates installed. 
  Lenovo Z70-80 laptop with Nvidia 840M, BIOS updated to latest version, secure 
boot and other potentially problematic BIOS settings disabled.

  Can only see a black screen instead of a log-in screen after boot completes 
when proprietary Nvidia drivers are installed.
  Regular Ubuntu works absolutely fine on the same machine with the same driver 
version. Attempting to use older drivers on Ubuntu Gnome made no difference.

  Bug is affecting more than just me. We were talking about workarounds
  in ubuntuforums. User fthx claims that switching to lightdm fixes the
  issue
  http://ubuntuforums.org/showthread.php?t=2317628&p=13457703#post13457703

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-14-generic 4.4.0-14.30
  ProcVersionSignature: Ubuntu 4.4.0-14.30-generic 4.4.5
  Uname: Linux 4.4.0-14-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  Date: Sat Mar 19 23:19:21 2016
  HibernationDevice: RESUME=UUID=4f8fb76c-f99d-4c54-8a67-eed0653d8eb6
  InstallationDate: Installed on 2016-03-19 (0 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Alpha amd64 
(20160318)
  MachineType: LENOVO 80FG
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-14-generic.efi.signed 
root=UUID=572a19f6-7324-4269-ad36-7ffc9919f7a2 ro noprompt persistent quiet 
splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-14-generic N/A
   linux-backports-modules-4.4.0-14-generic  N/A
   linux-firmware1.156
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/22/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: ABCN96WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: Lenovo Z70-80
  dmi.board.vendor: LENOVO
  dmi.board.version: NO DPK
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo Z70-80
  dmi.modalias: 
dmi:bvnLENOVO:bvrABCN96WW:bd09/22/2015:svnLENOVO:pn80FG:pvrLenovoZ70-80:rvnLENOVO:rnLenovoZ70-80:rvrNODPK:cvnLENOVO:ct10:cvrLenovoZ70-80:
  dmi.product.name: 80FG
  dmi.product.version: Lenovo Z70-80
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/gdm/+bug/1559576/+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 1556264] Re: [Hyper-V] vmbus: Fix a bug in hv_need_to_signal_on_read()

Joshua,

Would it be possible to have the fixes in -proposed tested?

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

Title:
  [Hyper-V] vmbus: Fix a bug in hv_need_to_signal_on_read()

Status in linux package in Ubuntu:
  Fix Released
Status in linux-lts-vivid package in Ubuntu:
  Fix Committed
Status in linux source package in Trusty:
  Fix Committed
Status in linux-lts-vivid source package in Trusty:
  Fix Committed
Status in linux source package in Wily:
  Fix Committed
Status in linux source package in Xenial:
  Fix Released

Bug description:
  The following patch has been submitted upstream in response to
  investigation of customer issues with network connections hanging
  under high load.

  On the consumer side, we have interrupt driven flow management of the
  producer. It is sufficient to base the signalling decision on the
  amount of space that is available to write after the read is complete.
  The current code samples the previous available space and uses this in
  making the signalling decision. This state can be stale and is
  unnecessary. Since the state can be stale, we end up not signalling
  the host (when we should) and this can result in a hang. Fix this
  problem by removing the unnecessary check.

  I would like to thank Arseney Romanenko 
  for pointing out this bug.

  Signed-off-by: K. Y. Srinivasan 
  Tested-by: Dexuan Cui 
  Cc: 
  ---
   drivers/hv/ring_buffer.c |7 +++
   1 files changed, 3 insertions(+), 4 deletions(-)

  diff --git a/drivers/hv/ring_buffer.c b/drivers/hv/ring_buffer.c
  index 5613e2b..085003a 100644
  --- a/drivers/hv/ring_buffer.c
  +++ b/drivers/hv/ring_buffer.c
  @@ -103,8 +103,7 @@ static bool hv_need_to_signal(u32 old_write, struct 
hv_ring_buffer_info *rbi)
*there is room for the producer to send the pending packet.
*/

  -static bool hv_need_to_signal_on_read(u32 prev_write_sz,
  - struct hv_ring_buffer_info *rbi)
  +static bool hv_need_to_signal_on_read(struct hv_ring_buffer_info *rbi)
   {
  u32 cur_write_sz;
  u32 r_size;
  @@ -120,7 +119,7 @@ static bool hv_need_to_signal_on_read(u32 prev_write_sz,
  cur_write_sz = write_loc >= read_loc ? r_size - (write_loc - 
read_loc) :
  read_loc - write_loc;

  -   if ((prev_write_sz < pending_sz) && (cur_write_sz >= pending_sz))
  +   if (cur_write_sz >= pending_sz)
  return true;

  return false;
  @@ -455,7 +454,7 @@ int hv_ringbuffer_read(struct hv_ring_buffer_info 
*inring_info,
  /* Update the read index */
  hv_set_next_read_location(inring_info, next_read_location);

  -   *signal = hv_need_to_signal_on_read(bytes_avail_towrite, inring_info);
  +   *signal = hv_need_to_signal_on_read(inring_info);

  return ret;
   }

  We have customers who are encountering this issue. Although this patch
  is not yet accepted upstream, we would like to get them a test kernel
  as soon as we can.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1556264/+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 1556264] Re: [Hyper-V] vmbus: Fix a bug in hv_need_to_signal_on_read()

2016-05-04 Thread Chris Valean

Hi Joe,

I will have this verified asap, thanks for the notice!

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

Title:
  [Hyper-V] vmbus: Fix a bug in hv_need_to_signal_on_read()

Status in linux package in Ubuntu:
  Fix Released
Status in linux-lts-vivid package in Ubuntu:
  Fix Committed
Status in linux source package in Trusty:
  Fix Committed
Status in linux-lts-vivid source package in Trusty:
  Fix Committed
Status in linux source package in Wily:
  Fix Committed
Status in linux source package in Xenial:
  Fix Released

Bug description:
  The following patch has been submitted upstream in response to
  investigation of customer issues with network connections hanging
  under high load.

  On the consumer side, we have interrupt driven flow management of the
  producer. It is sufficient to base the signalling decision on the
  amount of space that is available to write after the read is complete.
  The current code samples the previous available space and uses this in
  making the signalling decision. This state can be stale and is
  unnecessary. Since the state can be stale, we end up not signalling
  the host (when we should) and this can result in a hang. Fix this
  problem by removing the unnecessary check.

  I would like to thank Arseney Romanenko 
  for pointing out this bug.

  Signed-off-by: K. Y. Srinivasan 
  Tested-by: Dexuan Cui 
  Cc: 
  ---
   drivers/hv/ring_buffer.c |7 +++
   1 files changed, 3 insertions(+), 4 deletions(-)

  diff --git a/drivers/hv/ring_buffer.c b/drivers/hv/ring_buffer.c
  index 5613e2b..085003a 100644
  --- a/drivers/hv/ring_buffer.c
  +++ b/drivers/hv/ring_buffer.c
  @@ -103,8 +103,7 @@ static bool hv_need_to_signal(u32 old_write, struct 
hv_ring_buffer_info *rbi)
*there is room for the producer to send the pending packet.
*/

  -static bool hv_need_to_signal_on_read(u32 prev_write_sz,
  - struct hv_ring_buffer_info *rbi)
  +static bool hv_need_to_signal_on_read(struct hv_ring_buffer_info *rbi)
   {
  u32 cur_write_sz;
  u32 r_size;
  @@ -120,7 +119,7 @@ static bool hv_need_to_signal_on_read(u32 prev_write_sz,
  cur_write_sz = write_loc >= read_loc ? r_size - (write_loc - 
read_loc) :
  read_loc - write_loc;

  -   if ((prev_write_sz < pending_sz) && (cur_write_sz >= pending_sz))
  +   if (cur_write_sz >= pending_sz)
  return true;

  return false;
  @@ -455,7 +454,7 @@ int hv_ringbuffer_read(struct hv_ring_buffer_info 
*inring_info,
  /* Update the read index */
  hv_set_next_read_location(inring_info, next_read_location);

  -   *signal = hv_need_to_signal_on_read(bytes_avail_towrite, inring_info);
  +   *signal = hv_need_to_signal_on_read(inring_info);

  return ret;
   }

  We have customers who are encountering this issue. Although this patch
  is not yet accepted upstream, we would like to get them a test kernel
  as soon as we can.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1556264/+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 1568865] Re: [drm:intel_cpu_fifo_underrun_irq_handler [i915_bpo]] ERROR CPU pipe B FIFO underrun

2016-05-04 Thread Simon Ransome

I see the same FIFO under-run issue in Kubuntu 16.04. The manifestation
appears to be either the laptop display remaining totally blank (but not
disabled - the pointer appears to travel through it) on boot-up, resume
from lid-open or resume from screensaver, or the display going blank
when the mouse pointer enters the laptop screen and resuming when the
pointer exits - but always in the presence of a second display connected
over HDMI. Temporary "fixes" have so far included closing the lid and
opening (often seems to resolve the blank state from screensaver) and
unplugging and re-plugging HDMI, which sometimes sorts the blanking on
mouse pointer problem.

sample errors:

[   90.483130] [drm:intel_cpu_fifo_underrun_irq_handler [i915_bpo]] *ERROR* CPU 
pipe A FIFO underrun
[  139.548826] [drm:intel_cpu_fifo_underrun_irq_handler [i915_bpo]] *ERROR* CPU 
pipe A FIFO underrun

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

Title:
  [drm:intel_cpu_fifo_underrun_irq_handler [i915_bpo]] *ERROR* CPU pipe
  B FIFO underrun

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Running Gnome-Shell on ubuntu 16.04 on my Dell XPS 15 9550 laptop
  using Intel graphics (Nvidia card turned off), I get this error in
  syslog when plugging in an external monitor (HDMI).

  Apr 11 14:28:38 miaco kernel: [ 2616.604641]
  [drm:intel_cpu_fifo_underrun_irq_handler [i915_bpo]] *ERROR* CPU pipe
  B FIFO underrun


  Meanwhile both screens flash and show corruption. Most of the time
  this has caused a hang that needs a hard power off to get out of, but
  occasionally removing the external monitor is enough to get going
  again and so I've been able to find this message in the logs.

  Note that when using Nvidia (proprietary) drivers and Unity DE I do
  not have this problem; so it seems to be related to the intel drivers,
  or possibly Gnome Shell's use of them.

  Happy to help if I can (would like to be able to use external
  monitors!)

  Rich

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-18-generic 4.4.0-18.34
  ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6
  Uname: Linux 4.4.0-18-generic x86_64
  ApportVersion: 2.20.1-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  rich   1943 F pulseaudio
  Date: Mon Apr 11 14:31:26 2016
  InstallationDate: Installed on 2016-03-21 (21 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160307)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 04f3:21d5 Elan Microelectronics Corp. 
   Bus 001 Device 002: ID 0a5c:6410 Broadcom Corp. 
   Bus 001 Device 004: ID 0c45:6713 Microdia 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. XPS 15 9550
  ProcEnviron:
   LANGUAGE=en_GB:en
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-18-generic.efi.signed 
root=UUID=3f8391d5-e9cc-4768-8efb-8f04d340567c ro quiet splash vt.handoff=7
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-18-generic N/A
   linux-backports-modules-4.4.0-18-generic  N/A
   linux-firmware1.157
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/25/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 01.01.19
  dmi.board.name: 0N7TVV
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr01.01.19:bd01/25/2016:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0N7TVV:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 15 9550
  dmi.sys.vendor: Dell Inc.

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

@faulpeltz,

I am continuing to test the next test kernel up to commit:
dfbdac2e

Are you testing 3.13.0-34.60 or would you be wiling to do that?  Just to
confirm it does not contain the bug and the bisect was started at the
correct versions.

-- 
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
Status in linux source package in Xenial:
  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 1578291] [NEW] Problem with kernel module ideapad_laptop

2016-05-04 Thread Jordyn Carattini

Public bug reported:

Every time I press the volume down button on my lenovo edge 2. I get this in 
the dmesg logs:
ideapad_laptop: Unknown event: 1

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: linux-image-generic 4.4.0.21.22
ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
Uname: Linux 4.4.0-21-generic x86_64
ApportVersion: 2.20.1-0ubuntu2
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  jordyn 1553 F pulseaudio
CurrentDesktop: Unity
Date: Wed May  4 11:05:44 2016
InstallationDate: Installed on 2016-05-03 (0 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 003: ID 06cb:7b0f Synaptics, Inc. 
 Bus 001 Device 002: ID 174f:14e6 Syntek 
 Bus 001 Device 005: ID 154b:005d PNY 
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: LENOVO 80QF
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic.efi.signed 
root=UUID=213928cb-b312-4984-9ef4-ff03f9435626 ro nosplash verbose debug 
earlycon
RelatedPackageVersions:
 linux-restricted-modules-4.4.0-21-generic N/A
 linux-backports-modules-4.4.0-21-generic  N/A
 linux-firmware1.157
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/10/2015
dmi.bios.vendor: LENOVO
dmi.bios.version: D3CN28WW
dmi.board.asset.tag: No Asset Tag
dmi.board.name: Lenovo Edge 2-1580
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40709 WIN
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Lenovo Edge 2-1580
dmi.modalias: 
dmi:bvnLENOVO:bvrD3CN28WW:bd12/10/2015:svnLENOVO:pn80QF:pvrLenovoEdge2-1580:rvnLENOVO:rnLenovoEdge2-1580:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoEdge2-1580:
dmi.product.name: 80QF
dmi.product.version: Lenovo Edge 2-1580
dmi.sys.vendor: LENOVO

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


** Tags: amd64 apport-bug xenial

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

Title:
  Problem with kernel module ideapad_laptop

Status in linux package in Ubuntu:
  New

Bug description:
  Every time I press the volume down button on my lenovo edge 2. I get this in 
the dmesg logs:
  ideapad_laptop: Unknown event: 1

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-generic 4.4.0.21.22
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jordyn 1553 F pulseaudio
  CurrentDesktop: Unity
  Date: Wed May  4 11:05:44 2016
  InstallationDate: Installed on 2016-05-03 (0 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 06cb:7b0f Synaptics, Inc. 
   Bus 001 Device 002: ID 174f:14e6 Syntek 
   Bus 001 Device 005: ID 154b:005d PNY 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 80QF
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic.efi.signed 
root=UUID=213928cb-b312-4984-9ef4-ff03f9435626 ro nosplash verbose debug 
earlycon
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-21-generic N/A
   linux-backports-modules-4.4.0-21-generic  N/A
   linux-firmware1.157
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/10/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: D3CN28WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Lenovo Edge 2-1580
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo Edge 2-1580
  dmi.modalias: 
dmi:bvnLENOVO:bvrD3CN28WW:bd12/10/2015:svnLENOVO:pn80QF:pvrLenovoEdge2-1580:rvnLENOVO:rnLenovoEdge2-1580:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoEdge2-1580:
  dmi.product.name: 80QF
  dmi.product.version: Lenovo Edge 2-1580
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1578291/+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 1479136] Re: [ubuntu 14.04.2] Artefacts in radeon driver on kernel 3.16 and upwards

2016-05-04 Thread thom

Maybebut it is not supposed to cause such weird side effects

I ended up doing a git bisect myself on this issue:

https://bugs.freedesktop.org/show_bug.cgi?id=87682
(because it's an upstream bug)

Anyone any tips how to continue ?

** Bug watch added: freedesktop.org Bugzilla #87682
   https://bugs.freedesktop.org/show_bug.cgi?id=87682

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

Title:
  [ubuntu 14.04.2] Artefacts in radeon driver on kernel 3.16 and upwards

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu-Mate 14.04.2

  This is what I get if I run a kernel newer than 3.13: 
https://www.youtube.com/watch?v=nx2-Fvihzxg
  sorry for the link, I just don't know how to describe these artefacts 
verbally.
  (a storm of small horizontal moving blips from right to left ??)

  Those artefacts appear as soon as new kernel is selected in GRUB, and
  remain during the whole session.

  The lastest kernel (from the main repository that is) working without
  artifacts is v3.13.0.59. All later kernels have artifacts. All later
  kernels also are either "-utopic" or "-vivid" instead of "-trusty",
  but I do not know if it is related.

  
  GPU: Mobility Radeon HD 3200 (RS780M)
  System: Ubuntu Mate 14.04.2  32-bit

  Kernels tested: 3.13.0.59 (and earlier) , 3.16.0.45 , 3.19.0.25 
  Only  3.13.0.59 (and earlier) are without problems.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1479136/+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 1577905] Re: Dell TB15 audio is distorted

** Changed in: linux (Ubuntu Trusty)
   Status: Confirmed => Fix Committed

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

Title:
  Dell  TB15 audio is distorted

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Trusty:
  Fix Committed
Status in linux source package in Vivid:
  Fix Committed
Status in linux source package in Wily:
  Fix Committed
Status in linux source package in Xenial:
  Fix Released
Status in linux source package in Yakkety:
  Fix Released

Bug description:
  On the Dell TB15 and Dell WD15 docks, analogue audio output is
  distorted.  This is because of a missing driver quirk on docks.

  It has been fixed upstream here.
  
http://git.kernel.org/cgit/linux/kernel/git/tiwai/sound.git/commit/?id=adcdd0d5a1cb779f6d455ae70882c19c527627a8

  Please backport it into Ubuntu.

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

Title:
  Problem with kernel module ideapad_laptop

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Every time I press the volume down button on my lenovo edge 2. I get this in 
the dmesg logs:
  ideapad_laptop: Unknown event: 1

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-generic 4.4.0.21.22
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jordyn 1553 F pulseaudio
  CurrentDesktop: Unity
  Date: Wed May  4 11:05:44 2016
  InstallationDate: Installed on 2016-05-03 (0 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 06cb:7b0f Synaptics, Inc. 
   Bus 001 Device 002: ID 174f:14e6 Syntek 
   Bus 001 Device 005: ID 154b:005d PNY 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 80QF
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic.efi.signed 
root=UUID=213928cb-b312-4984-9ef4-ff03f9435626 ro nosplash verbose debug 
earlycon
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-21-generic N/A
   linux-backports-modules-4.4.0-21-generic  N/A
   linux-firmware1.157
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/10/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: D3CN28WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Lenovo Edge 2-1580
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo Edge 2-1580
  dmi.modalias: 
dmi:bvnLENOVO:bvrD3CN28WW:bd12/10/2015:svnLENOVO:pn80QF:pvrLenovoEdge2-1580:rvnLENOVO:rnLenovoEdge2-1580:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoEdge2-1580:
  dmi.product.name: 80QF
  dmi.product.version: Lenovo Edge 2-1580
  dmi.sys.vendor: LENOVO

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

2016-05-04 Thread bugproxy

--- Comment From vaish...@in.ibm.com 2016-05-04 12:35 EDT---
-- Comment from Pavithra--
Hi,

I tried it on another firestone machine with 17-Feb build. Installation
is successful and issue not observed.

root@ltc-fire4:~# uname -a
Linux ltc-fire4 4.2.0-34-generic #39~14.04.1-Ubuntu SMP Fri Mar 11 11:37:53 UTC 
2016 ppc64le ppc64le ppc64le GNU/Linux
root@ltc-fire4:~# mount
/dev/mapper/ltc--fire4--vg-root on / type ext3 (rw,errors=remount-ro)
proc on /proc type proc (rw,noexec,nosuid,nodev)
sysfs on /sys type sysfs (rw,noexec,nosuid,nodev)
none on /sys/fs/cgroup type tmpfs (rw)
none on /sys/fs/fuse/connections type fusectl (rw)
none on /sys/kernel/debug type debugfs (rw)
none on /sys/kernel/security type securityfs (rw)
udev on /dev type devtmpfs (rw,mode=0755)
devpts on /dev/pts type devpts (rw,noexec,nosuid,gid=5,mode=0620)
tmpfs on /run type tmpfs (rw,noexec,nosuid,size=10%,mode=0755)
none on /run/lock type tmpfs (rw,noexec,nosuid,nodev,size=5242880)
none on /run/shm type tmpfs (rw,nosuid,nodev)
none on /run/user type tmpfs (rw,noexec,nosuid,nodev,size=104857600,mode=0755)
none on /sys/fs/pstore type pstore (rw)
tracefs on /var/lib/ureadahead/debugfs/tracing type tracefs (rw,relatime)
/dev/sda2 on /boot type ext2 (rw)
systemd on /sys/fs/cgroup/systemd type cgroup 
(rw,noexec,nosuid,nodev,none,name=systemd)
root@ltc-fire4:~# lvs
LV VG   Attr  LSize   Pool Origin Data%  Move Log Copy%  Convert
root   ltc-fire4-vg -wi-ao--- 893.54g
swap_1 ltc-fire4-vg -wi-ao---  37.69g

Thanks,
Pavithra

Closing bug as the issue is not observed.
Thank you.

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

Title:
  ubuntu 14.04.4 installation with "Guided - use entire disk and set up
  LVM" fails for ext3 file system.

Status in linux package in Ubuntu:
  New

Bug description:
  Problem Description
  ===
  ubuntu 14.04.4 installation on Firestone baremetal with "Guided - use entire 
disk and set up LVM" fails when ext3 is chosen as / file system. Below error 
message is displayed.

  
  ? [!!] Partition disks ?
  ?  ?
  ?Failed to create a file system?
  ? The ext3 file system creation in partition #1 of LVM VG FR21p01-vg,  ?
  ? LV root failed.  ?
  ?  ?
  ?   ?
  ?  ?
  

  
  Steps to Reproduce
  =
  1. Start netboot installation on Firestone baremetal machine from 
  
http://ports.ubuntu.com/ubuntu-ports/dists/trusty-proposed/main/installer-ppc64el/current/images/wily-netboot/
  2. During "Partition disks" select 
  Manual -> Guided partitioning -> Guided - use entire disk and set up LVM

?? [!!] Partition disks ???
? ?
? The installer can guide you through partitioning a disk (using  ?
? different standard schemes) or, if you prefer, you can do it?
? manually. With guided partitioning you will still have a chance later   ?
? to review and customise the results.?
? ?
? If you choose guided partitioning for an entire disk, you will next ?
? be asked which disk should be used. ?
? ?
? Partitioning method:?
? ?
?  Guided - use entire partition, SCSI5 (0,0,0), partition #2 (sdk)   ?
?  Guided - use the largest continuous free space ?   ?
?  Guided - use entire disk and set up LVM?   ?
?  Guided - use entire disk and set up encrypted LVM  ?
?  Manual ?
? ?
??
? ?
???

?? [!!] Partition disks ???
?

[Kernel-packages] [Bug 1578305] [NEW] Stoney powerplay support

2016-05-04 Thread Tom St Denis

Public bug reported:

I'd love to submit a patch right now but I can't since the clone is
taking way too long...

The bug is in drivers/gpu/drm/amd/amdgpu/amdgpu_powerplay.c on line 83
you need to insert

case CHIP_STONEY:

before CHIP_CARRIZO to get ST to successfully init with the amdgpu
module.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: linux-image-4.4.0-21-generic 4.4.0-21.37 [modified: 
boot/vmlinuz-4.4.0-21-generic]
ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
Uname: Linux 4.4.0-21-generic x86_64
ApportVersion: 2.20.1-0ubuntu2
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  amd1533 F pulseaudio
 /dev/snd/controlC0:  amd1533 F pulseaudio
CurrentDesktop: Unity
Date: Wed May  4 12:35:10 2016
HibernationDevice: RESUME=UUID=39b1897f-c3d9-4222-9b73-94e0f6527917
InstallationDate: Installed on 2016-05-04 (0 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
IwConfig:
 enx54b80aefee18  no wireless extensions.
 
 enx1a1b9c20  no wireless extensions.
 
 lono wireless extensions.
MachineType: AMD Gardenia-ST
ProcFB:
 
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic.efi.signed 
root=UUID=f4bc1961-0964-4010-a6e5-401bbfe28352 ro quiet splash vt.handoff=7 
amdgpu.powerplay=0
RelatedPackageVersions:
 linux-restricted-modules-4.4.0-21-generic N/A
 linux-backports-modules-4.4.0-21-generic  N/A
 linux-firmware1.157
RfKill:
 
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/30/2015
dmi.bios.vendor: Insyde Corp.
dmi.bios.version: WGY5930N_Weekly_15_09_3
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: Gardenia-ST
dmi.board.vendor: AMD
dmi.board.version: Base Board Version
dmi.chassis.asset.tag: Chassis Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: Chassis Manufacturer
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnInsydeCorp.:bvrWGY5930N_Weekly_15_09_3:bd09/30/2015:svnAMD:pnGardenia-ST:pvr1:rvnAMD:rnGardenia-ST:rvrBaseBoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion:
dmi.product.name: Gardenia-ST
dmi.product.version: 1
dmi.sys.vendor: AMD

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


** Tags: amd64 apport-bug xenial

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

Title:
  Stoney powerplay support

Status in linux package in Ubuntu:
  New

Bug description:
  I'd love to submit a patch right now but I can't since the clone is
  taking way too long...

  The bug is in drivers/gpu/drm/amd/amdgpu/amdgpu_powerplay.c on line 83
  you need to insert

  case CHIP_STONEY:

  before CHIP_CARRIZO to get ST to successfully init with the amdgpu
  module.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-21-generic 4.4.0-21.37 [modified: 
boot/vmlinuz-4.4.0-21-generic]
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  amd1533 F pulseaudio
   /dev/snd/controlC0:  amd1533 F pulseaudio
  CurrentDesktop: Unity
  Date: Wed May  4 12:35:10 2016
  HibernationDevice: RESUME=UUID=39b1897f-c3d9-4222-9b73-94e0f6527917
  InstallationDate: Installed on 2016-05-04 (0 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  IwConfig:
   enx54b80aefee18  no wireless extensions.
   
   enx1a1b9c20  no wireless extensions.
   
   lono wireless extensions.
  MachineType: AMD Gardenia-ST
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic.efi.signed 
root=UUID=f4bc1961-0964-4010-a6e5-401bbfe28352 ro quiet splash vt.handoff=7 
amdgpu.powerplay=0
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-21-generic N/A
   linux-backports-modules-4.4.0-21-generic  N/A
   linux-firmware1.157
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/30/2015
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: WGY5930N_Weekly_15_09_3
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: Gardenia-ST
  dmi.board.vendor: AMD
  dmi.board.version: Base Board Version
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Chassis Manufacturer
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrWGY5930N_Weekly_15_09_3:bd09/30/2015:svnAMD:pnGardenia-ST:pvr1:rvnAMD:rnGardenia-ST:rvrBaseBoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion:
  dmi.product.name: Gardenia-ST
  dmi.product.version: 1
  dmi.sys.vendor: AMD

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubunt

[Kernel-packages] [Bug 1574727] Re: [SRU] Enforce using signed kernels and modules on UEFI

Hello Mathieu, or anyone else affected,

Accepted mokutil into trusty-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/mokutil/0.3.0-0ubuntu3~14.04.1 in a
few hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
enable and use -proposed.  Your feedback will aid us getting this update
out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, and change the tag
from verification-needed to verification-done. If it does not fix the
bug for you, please add a comment stating that, and change the tag to
verification-failed.  In either case, details of your testing will help
us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

** Changed in: mokutil (Ubuntu Trusty)
   Status: New => Fix Committed

** Tags added: verification-needed

** Changed in: mokutil (Ubuntu Wily)
   Status: New => Fix Committed

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

Title:
  [SRU] Enforce using signed kernels and modules on UEFI

Status in dkms package in Ubuntu:
  Fix Released
Status in efivar package in Ubuntu:
  Fix Released
Status in grub2 package in Ubuntu:
  New
Status in grub2-signed package in Ubuntu:
  New
Status in mokutil package in Ubuntu:
  Fix Released
Status in shim package in Ubuntu:
  New
Status in dkms source package in Precise:
  New
Status in efivar source package in Precise:
  New
Status in grub2 source package in Precise:
  New
Status in grub2-signed source package in Precise:
  New
Status in mokutil source package in Precise:
  New
Status in shim source package in Precise:
  New
Status in dkms source package in Trusty:
  New
Status in efivar source package in Trusty:
  Fix Committed
Status in grub2 source package in Trusty:
  New
Status in grub2-signed source package in Trusty:
  New
Status in mokutil source package in Trusty:
  Fix Committed
Status in shim source package in Trusty:
  New
Status in dkms source package in Wily:
  New
Status in efivar source package in Wily:
  Fix Released
Status in grub2 source package in Wily:
  New
Status in grub2-signed source package in Wily:
  New
Status in mokutil source package in Wily:
  Fix Committed
Status in shim source package in Wily:
  New
Status in dkms source package in Xenial:
  Fix Released
Status in efivar source package in Xenial:
  Fix Released
Status in grub2 source package in Xenial:
  New
Status in grub2-signed source package in Xenial:
  New
Status in mokutil source package in Xenial:
  Fix Released
Status in shim source package in Xenial:
  New

Bug description:
  [Rationale]
  Secure Boot is good. We want to be able to validate that as much as possible 
of the boot process happens with signed binaries; from our shim (the part that 
is loaded by the EFI firmware itself), down to grub2, the kernel, and even 
loaded modules.

  [Impact]
  All our users booting in UEFI; on all supported releases.

  [Test cases]
  

  Test cases here are separated by the components that need to be
  changed:

  = grub2 =

  Booting signed kernels:
  1) Try to boot a custom kernel
  2) Verify that the kernel will not be loaded by grub (you should see an error 
message about the signature)

  Prompting on upgrade:
  0) On a system that runs a dkms module (such as r8168-dkms, rtl8812au-dkms, 
ndiswrapper-dkms, bbswitch-dkms, etc.)
  1) Make sure that validation is enabled and reboot: 'sudo mokutil 
--enable-validation && sudo reboot'
  2) Upgrade to the new grub2 package (you may need to download the updated 
package beforehand)
  3) Validate that grub2 prompts you to disable shim validation.

  = dkms =

  Prompting for dkms on install:
  1) Install r8168-dkms
  2) Verify that you're asked to disable shim validation, and walked through 
the process via debconf prompts.

  Prompting for dkms on upgrade
  0) On a system that runs a dkms module (such as r8168-dkms, rtl8812au-dkms, 
ndiswrapper-dkms, bbswitch-dkms, etc.)
  1) Make sure that validation is enabled and reboot: 'sudo mokutil 
--enable-validation && reboot'
  2) Upgrade to the new dkms package (you may need to download the updated 
package beforehand)
  3) Validate that dkms prompts you to disable shim validation.

  = shim =

  Booting:
  -> Validate that it allows booting grubx64.efi signed with the old key.
  -> Validate that it allows booting grubx64.efi signed with the new key.

  Validation toggle:
  0) Boot the system; verify if /sys/firmware/efi/efivars/MokSBStateRT-* is 
present;
  If MokSBStateRT is preset:
  1) sudo mokutil --enable-validation && sudo reboot
  2) Validate that Mok asks you if you want to enab

[Kernel-packages] [Bug 1573062] Re: memory_stress_ng failing for IBM Power S812LC(TN71-BP012) for 16.04

Can you test the 4.1 kernel next?  It can be downloaded from:

http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.1-wily/

We may also want to test the latest mainline kernel to see if this bug
is already fixed there.  If it is, we can perform a "Reverse" bisect to
find the fix.  The mainline kernel is available from:

http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.6-rc6-wily/

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

Title:
  memory_stress_ng failing for IBM Power S812LC(TN71-BP012) for 16.04

Status in linux package in Ubuntu:
  Triaged

Bug description:
  memory_stress_ng, as part of server certification is failing for IBM
  Power S812LC(TN71-BP012) in bare metal mode. Failing in this case is
  defined by the test locking up the server in an unrecoverable state
  which only a reboot will fix.

  I will be attaching screen and kern logs for the failures and a
  successful run on 14.04 on the same server.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1573062/+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 1574727] Please test proposed package

Hello Mathieu, or anyone else affected,

Accepted mokutil into wily-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/mokutil/0.3.0-0ubuntu3~15.10.1 in a
few hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
enable and use -proposed.  Your feedback will aid us getting this update
out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, and change the tag
from verification-needed to verification-done. If it does not fix the
bug for you, please add a comment stating that, and change the tag to
verification-failed.  In either case, details of your testing will help
us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

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

Title:
  [SRU] Enforce using signed kernels and modules on UEFI

Status in dkms package in Ubuntu:
  Fix Released
Status in efivar package in Ubuntu:
  Fix Released
Status in grub2 package in Ubuntu:
  New
Status in grub2-signed package in Ubuntu:
  New
Status in mokutil package in Ubuntu:
  Fix Released
Status in shim package in Ubuntu:
  New
Status in dkms source package in Precise:
  New
Status in efivar source package in Precise:
  New
Status in grub2 source package in Precise:
  New
Status in grub2-signed source package in Precise:
  New
Status in mokutil source package in Precise:
  New
Status in shim source package in Precise:
  New
Status in dkms source package in Trusty:
  New
Status in efivar source package in Trusty:
  Fix Committed
Status in grub2 source package in Trusty:
  New
Status in grub2-signed source package in Trusty:
  New
Status in mokutil source package in Trusty:
  Fix Committed
Status in shim source package in Trusty:
  New
Status in dkms source package in Wily:
  New
Status in efivar source package in Wily:
  Fix Released
Status in grub2 source package in Wily:
  New
Status in grub2-signed source package in Wily:
  New
Status in mokutil source package in Wily:
  Fix Committed
Status in shim source package in Wily:
  New
Status in dkms source package in Xenial:
  Fix Released
Status in efivar source package in Xenial:
  Fix Released
Status in grub2 source package in Xenial:
  New
Status in grub2-signed source package in Xenial:
  New
Status in mokutil source package in Xenial:
  Fix Released
Status in shim source package in Xenial:
  New

Bug description:
  [Rationale]
  Secure Boot is good. We want to be able to validate that as much as possible 
of the boot process happens with signed binaries; from our shim (the part that 
is loaded by the EFI firmware itself), down to grub2, the kernel, and even 
loaded modules.

  [Impact]
  All our users booting in UEFI; on all supported releases.

  [Test cases]
  

  Test cases here are separated by the components that need to be
  changed:

  = grub2 =

  Booting signed kernels:
  1) Try to boot a custom kernel
  2) Verify that the kernel will not be loaded by grub (you should see an error 
message about the signature)

  Prompting on upgrade:
  0) On a system that runs a dkms module (such as r8168-dkms, rtl8812au-dkms, 
ndiswrapper-dkms, bbswitch-dkms, etc.)
  1) Make sure that validation is enabled and reboot: 'sudo mokutil 
--enable-validation && sudo reboot'
  2) Upgrade to the new grub2 package (you may need to download the updated 
package beforehand)
  3) Validate that grub2 prompts you to disable shim validation.

  = dkms =

  Prompting for dkms on install:
  1) Install r8168-dkms
  2) Verify that you're asked to disable shim validation, and walked through 
the process via debconf prompts.

  Prompting for dkms on upgrade
  0) On a system that runs a dkms module (such as r8168-dkms, rtl8812au-dkms, 
ndiswrapper-dkms, bbswitch-dkms, etc.)
  1) Make sure that validation is enabled and reboot: 'sudo mokutil 
--enable-validation && reboot'
  2) Upgrade to the new dkms package (you may need to download the updated 
package beforehand)
  3) Validate that dkms prompts you to disable shim validation.

  = shim =

  Booting:
  -> Validate that it allows booting grubx64.efi signed with the old key.
  -> Validate that it allows booting grubx64.efi signed with the new key.

  Validation toggle:
  0) Boot the system; verify if /sys/firmware/efi/efivars/MokSBStateRT-* is 
present;
  If MokSBStateRT is preset:
  1) sudo mokutil --enable-validation && sudo reboot
  2) Validate that Mok asks you if you want to enable validation
  Otherwise:
  1) sudo mokutil --disable-validation && sudo reboot
  2) Validate that Mok asks you if you want to disable validation
  Finally:
  3) Complete the process to t

[Kernel-packages] [Bug 1570195] Re: Net tools cause kernel soft lockup after DPDK touched VirtIO-pci devices

2016-05-04 Thread Launchpad Bug Tracker

This bug was fixed in the package dpdk - 2.2.0-0ubuntu8

---
dpdk (2.2.0-0ubuntu8) xenial; urgency=medium

  * d/p/ubuntu-backport-[36-37] fix virtio issues (LP: #1570195):
- don't let DPDK initialize virtio devices still in use by the kernel
- this avoids conflicts between kernel and dpdk usage of those devices
- an admin now has to unbind/bind devices as on physical hardware
- this is in the dpdk 16.04 release and delta can then be dropped
- d/dpdk-doc.README.Debian update for changes in virtio-pci handling
- d/dpdk.interfaces update for changes in virtio-pci handling
  * d/p/ubuntu-backport-38... fix for memory leak (LP: #1570466):
- call vhost_destroy_device on removing vhost user ports to fix memory leak
- this likely is in the dpdk 16.07 release and delta can then be dropped
  * d/p/ubuntu-fix-vhost-user-socket-permission.patch fox (LP: #1546565):
- when vhost_user sockets are created they are owner:group of the process
- the DPDK api to create those has no way to specify owner:group
- to fix that without breaking the API and potential workaround code in
  consumers of the library like openvswitch 2.6 for example. This patch
  adds an EAL commandline option to specify user:group created vhost_user
  sockets should have.

 -- Christian Ehrhardt   Mon, 25 Apr
2016 11:42:40 +0200

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

Title:
  Net tools cause kernel soft lockup after DPDK touched  VirtIO-pci
  devices

Status in dpdk package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Confirmed
Status in dpdk source package in Xenial:
  Fix Released
Status in linux source package in Xenial:
  New

Bug description:
  Guys,

   I'm facing an issue here with both "ethtool" and "ip", while trying
  to manage black-listed by DPDK PCI VirtIO devices.

   You'll need an Ubuntu Xenial KVM guest, with 4 VirtIO vNIC cards, to
  run those tests

   PCI device example from inside a Xenial guest:

  ---
  # lspci | grep Ethernet
  00:03.0 Ethernet controller: Red Hat, Inc Virtio network device
  00:04.0 Ethernet controller: Red Hat, Inc Virtio network device
  00:05.0 Ethernet controller: Red Hat, Inc Virtio network device
  00:06.0 Ethernet controller: Red Hat, Inc Virtio network device
  ---

  Where "ens3" is the first / default interface, attached to Libvirt's
  "default" network. The "ens4" is reserved for "ethtool / ip" tests
  (attached to another Libvirt's network without IPs or DHCP), "ens5"
  will be "dpdk0" and "ens6" "dpdk1"...

  ---
   *** How it works?

   1- For example, try to enable multi-queue on DPDK's devices, boot
  your Xenial guest, and run:

   ethtool -L ens5 combined 4
   ethtool -L ens6 combined 4

   2- Install openvswitch-switch-dpdk configure DPDK and OVS and fire it
  up.

   https://help.ubuntu.com/16.04/serverguide/DPDK.html

   service openvswitch-switch stop
   service dpdk stop

   OVS DPDK Options (/etc/default/openvswitch-switch):

  --
  DPDK_OPTS='--dpdk -c 0x1 -n 4 --socket-mem 1024 --pci-blacklist 
:00:03.0,:00:04.0'
  --

   service dpdk start
   service openvswitch-switch start

   - Enable multi-queue on OVS+DPDK inside of the VM:

   ovs-vsctl set Open_vSwitch . other_config:n-dpdk-rxqs=4
   ovs-vsctl set Open_vSwitch . other_config:pmd-cpu-mask=0xff00

   * Multi-queue apparently works! ovs-vswitchd consumes more that 100%
  of CPU, meaning that it multi-queue is there...

   *** Where it fails?

   1- Reboot the VM and try to run ethtool again (or go straight to 2
  below):

   ethtool -L ens5 combined 4

   2- Try to fire up ens4:

   ip link set dev ens4 up

  
   # FAIL! Both commands hangs, consuming 100% of guest's CPU...

   So, it looks like a Linux fault, because it is "allowing" the DPDK
  VirtIO App (a user land App), to interfere with kernel devices in a
  strange way...

  Best,
  Thiago

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-18-generic 4.4.0-18.34
  ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6
  Uname: Linux 4.4.0-18-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Apr 14 00:35 seq
   crw-rw 1 root audio 116, 33 Apr 14 00:35 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.1-0ubuntu1
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: [Errno 2] No such file or directory: 'fuser'
  CRDA: N/A
  Date: Thu Apr 14 01:27:27 2016
  HibernationDevice: RESUME=UUID=833e999c-e066-433c-b8a2-4324bb8d56de
  InstallationDate: Installed on 2016-04-07 (7 days ago)
  InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Beta amd64 
(20160406)
  IwConfig: Error: [Errno 2] No such file or directory: 'iw

[Kernel-packages] [Bug 1570195] Update Released

The verification of the Stable Release Update for dpdk has completed
successfully and the package has now been released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  Net tools cause kernel soft lockup after DPDK touched  VirtIO-pci
  devices

Status in dpdk package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Confirmed
Status in dpdk source package in Xenial:
  Fix Released
Status in linux source package in Xenial:
  New

Bug description:
  Guys,

   I'm facing an issue here with both "ethtool" and "ip", while trying
  to manage black-listed by DPDK PCI VirtIO devices.

   You'll need an Ubuntu Xenial KVM guest, with 4 VirtIO vNIC cards, to
  run those tests

   PCI device example from inside a Xenial guest:

  ---
  # lspci | grep Ethernet
  00:03.0 Ethernet controller: Red Hat, Inc Virtio network device
  00:04.0 Ethernet controller: Red Hat, Inc Virtio network device
  00:05.0 Ethernet controller: Red Hat, Inc Virtio network device
  00:06.0 Ethernet controller: Red Hat, Inc Virtio network device
  ---

  Where "ens3" is the first / default interface, attached to Libvirt's
  "default" network. The "ens4" is reserved for "ethtool / ip" tests
  (attached to another Libvirt's network without IPs or DHCP), "ens5"
  will be "dpdk0" and "ens6" "dpdk1"...

  ---
   *** How it works?

   1- For example, try to enable multi-queue on DPDK's devices, boot
  your Xenial guest, and run:

   ethtool -L ens5 combined 4
   ethtool -L ens6 combined 4

   2- Install openvswitch-switch-dpdk configure DPDK and OVS and fire it
  up.

   https://help.ubuntu.com/16.04/serverguide/DPDK.html

   service openvswitch-switch stop
   service dpdk stop

   OVS DPDK Options (/etc/default/openvswitch-switch):

  --
  DPDK_OPTS='--dpdk -c 0x1 -n 4 --socket-mem 1024 --pci-blacklist 
:00:03.0,:00:04.0'
  --

   service dpdk start
   service openvswitch-switch start

   - Enable multi-queue on OVS+DPDK inside of the VM:

   ovs-vsctl set Open_vSwitch . other_config:n-dpdk-rxqs=4
   ovs-vsctl set Open_vSwitch . other_config:pmd-cpu-mask=0xff00

   * Multi-queue apparently works! ovs-vswitchd consumes more that 100%
  of CPU, meaning that it multi-queue is there...

   *** Where it fails?

   1- Reboot the VM and try to run ethtool again (or go straight to 2
  below):

   ethtool -L ens5 combined 4

   2- Try to fire up ens4:

   ip link set dev ens4 up

  
   # FAIL! Both commands hangs, consuming 100% of guest's CPU...

   So, it looks like a Linux fault, because it is "allowing" the DPDK
  VirtIO App (a user land App), to interfere with kernel devices in a
  strange way...

  Best,
  Thiago

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-18-generic 4.4.0-18.34
  ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6
  Uname: Linux 4.4.0-18-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Apr 14 00:35 seq
   crw-rw 1 root audio 116, 33 Apr 14 00:35 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.1-0ubuntu1
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: [Errno 2] No such file or directory: 'fuser'
  CRDA: N/A
  Date: Thu Apr 14 01:27:27 2016
  HibernationDevice: RESUME=UUID=833e999c-e066-433c-b8a2-4324bb8d56de
  InstallationDate: Installed on 2016-04-07 (7 days ago)
  InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Beta amd64 
(20160406)
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
  PciMultimedia:
   
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-18-generic 
root=UUID=9911604e-353b-491f-a0a9-804724350592 ro
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-18-generic N/A
   linux-backports-modules-4.4.0-18-generic  N/A
   linux-firmwareN/A
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/01/2014
  dmi.bios.vendor: SeaBIOS
  dmi.bios.version: Ubuntu-1.8.2-1ubuntu1
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version:

[Kernel-packages] [Bug 1570195] Re: Net tools cause kernel soft lockup after DPDK touched VirtIO-pci devices

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

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

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

Title:
  Net tools cause kernel soft lockup after DPDK touched  VirtIO-pci
  devices

Status in dpdk package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Confirmed
Status in dpdk source package in Xenial:
  Fix Released
Status in linux source package in Xenial:
  New

Bug description:
  Guys,

   I'm facing an issue here with both "ethtool" and "ip", while trying
  to manage black-listed by DPDK PCI VirtIO devices.

   You'll need an Ubuntu Xenial KVM guest, with 4 VirtIO vNIC cards, to
  run those tests

   PCI device example from inside a Xenial guest:

  ---
  # lspci | grep Ethernet
  00:03.0 Ethernet controller: Red Hat, Inc Virtio network device
  00:04.0 Ethernet controller: Red Hat, Inc Virtio network device
  00:05.0 Ethernet controller: Red Hat, Inc Virtio network device
  00:06.0 Ethernet controller: Red Hat, Inc Virtio network device
  ---

  Where "ens3" is the first / default interface, attached to Libvirt's
  "default" network. The "ens4" is reserved for "ethtool / ip" tests
  (attached to another Libvirt's network without IPs or DHCP), "ens5"
  will be "dpdk0" and "ens6" "dpdk1"...

  ---
   *** How it works?

   1- For example, try to enable multi-queue on DPDK's devices, boot
  your Xenial guest, and run:

   ethtool -L ens5 combined 4
   ethtool -L ens6 combined 4

   2- Install openvswitch-switch-dpdk configure DPDK and OVS and fire it
  up.

   https://help.ubuntu.com/16.04/serverguide/DPDK.html

   service openvswitch-switch stop
   service dpdk stop

   OVS DPDK Options (/etc/default/openvswitch-switch):

  --
  DPDK_OPTS='--dpdk -c 0x1 -n 4 --socket-mem 1024 --pci-blacklist 
:00:03.0,:00:04.0'
  --

   service dpdk start
   service openvswitch-switch start

   - Enable multi-queue on OVS+DPDK inside of the VM:

   ovs-vsctl set Open_vSwitch . other_config:n-dpdk-rxqs=4
   ovs-vsctl set Open_vSwitch . other_config:pmd-cpu-mask=0xff00

   * Multi-queue apparently works! ovs-vswitchd consumes more that 100%
  of CPU, meaning that it multi-queue is there...

   *** Where it fails?

   1- Reboot the VM and try to run ethtool again (or go straight to 2
  below):

   ethtool -L ens5 combined 4

   2- Try to fire up ens4:

   ip link set dev ens4 up

  
   # FAIL! Both commands hangs, consuming 100% of guest's CPU...

   So, it looks like a Linux fault, because it is "allowing" the DPDK
  VirtIO App (a user land App), to interfere with kernel devices in a
  strange way...

  Best,
  Thiago

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-18-generic 4.4.0-18.34
  ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6
  Uname: Linux 4.4.0-18-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Apr 14 00:35 seq
   crw-rw 1 root audio 116, 33 Apr 14 00:35 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.1-0ubuntu1
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: [Errno 2] No such file or directory: 'fuser'
  CRDA: N/A
  Date: Thu Apr 14 01:27:27 2016
  HibernationDevice: RESUME=UUID=833e999c-e066-433c-b8a2-4324bb8d56de
  InstallationDate: Installed on 2016-04-07 (7 days ago)
  InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Beta amd64 
(20160406)
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
  PciMultimedia:
   
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-18-generic 
root=UUID=9911604e-353b-491f-a0a9-804724350592 ro
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-18-generic N/A
   linux-backports-modules-4.4.0-18-generic  N/A
   linux-firmwareN/A
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/01/2014
  dmi.bios.vendor: SeaBIOS
  dmi.bios.version: Ubuntu-1.8.2-1ubuntu1
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-i440fx-wily
  dmi.modalias: 
dmi:bvnSeaBIOS:bvrUbuntu-1.8.2-1ubuntu1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-wily:cvnQEMU:ct1:cvrpc-i440fx-wily:
  dmi.product.name: Standard PC (i440FX + PIIX, 1996)
  dmi.product.version: pc-i440fx-wily
  dmi.sys.vendor: QEMU

To ma

[Kernel-packages] [Bug 1568830] Re: make_request bug: can't convert block across chunks or bigger than 512k 2554601336 124

Would it be possible for you to test the latest upstream stable 3.2
kernel next?  It can be downloaded from:

http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.2.80-precise/

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

Title:
  make_request bug: can't convert block across chunks or bigger than
  512k 2554601336 124

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I have a couple of RAID arrays with the following configuration:

  /dev/md1:
  Version : 1.2
Creation Time : Sat Dec 26 19:49:41 2015
   Raid Level : raid0
   Array Size : 1953524736 (1863.03 GiB 2000.41 GB)
 Raid Devices : 2
Total Devices : 2
  Persistence : Superblock is persistent

  Update Time : Sat Dec 26 19:49:41 2015
State : clean
   Active Devices : 2
  Working Devices : 2
   Failed Devices : 0
Spare Devices : 0

   Chunk Size : 512K

 Name : linux.interlinx.bc.ca:1  (local to host 
linux.interlinx.bc.ca)
 UUID : f27ae74d:e2997e50:9df158ee:c5ed3cbb
   Events : 0

  Number   Major   Minor   RaidDevice State
 0   8   160  active sync   /dev/sdb
 1   8   321  active sync   /dev/sdc

  /dev/md0:
  Version : 0.90
Creation Time : Mon Jan 26 19:51:38 2009
   Raid Level : raid1
   Array Size : 1953514496 (1863.02 GiB 2000.40 GB)
Used Dev Size : 1953514496 (1863.02 GiB 2000.40 GB)
 Raid Devices : 2
Total Devices : 2
  Preferred Minor : 0
  Persistence : Superblock is persistent

  Update Time : Fri Apr  8 00:00:42 2016
State : active, degraded
   Active Devices : 1
  Working Devices : 1
   Failed Devices : 1
Spare Devices : 0

 UUID : 2f8fc5e0:a0eb646a:2303d005:33f25f21
   Events : 0.5031387

  Number   Major   Minor   RaidDevice State
 0   8   480  active sync   /dev/sdd
 1   001  removed

 2   91-  faulty spare   /dev/md1

  This configuration has worked for a number of years but has all of a
  sudden started breaking with:

  [37722.335880] md/raid0:md1: make_request bug: can't convert block across 
chunks or bigger than 512k 2554601336 124
  [37722.335887] md/raid1:md0: md1: rescheduling sector 2554601336
  [37722.376776] md/raid1:md0: redirecting sector 2554601336 to other mirror: 
md1
  [37722.386455] md/raid0:md1: make_request bug: can't convert block across 
chunks or bigger than 512k 2554601336 124
  [37722.386461] md/raid1:md0: md1: rescheduling sector 2554601336
  [37722.412059] md/raid1:md0: redirecting sector 2554601336 to other mirror: 
sdd
  [37722.735049] md/raid0:md1: make_request bug: can't convert block across 
chunks or bigger than 512k 2554608496 124
  [37722.735056] md/raid1:md0: md1: rescheduling sector 2554608496
  [37722.789926] md/raid1:md0: redirecting sector 2554608496 to other mirror: 
md1
  [37722.798689] md/raid0:md1: make_request bug: can't convert block across 
chunks or bigger than 512k 2554608496 124
  [37722.798696] md/raid1:md0: md1: rescheduling sector 2554608496
  [37722.859314] md/raid1:md0: redirecting sector 2554608496 to other mirror: 
sdd
  [37724.819090] md/raid0:md1: make_request bug: can't convert block across 
chunks or bigger than 512k 2554606584 12
  [37724.819096] md/raid1:md0: md1: rescheduling sector 2554606584
  [37727.455279] md/raid1:md0: redirecting sector 2554606584 to other mirror: 
sdd
  [37752.406865] md/raid0:md1: make_request bug: can't convert block across 
chunks or bigger than 512k 1748150224 124
  [37752.521219] md/raid1:md0: Disk failure on md1, disabling device.
  [37752.521222] md/raid1:md0: Operation continuing on 1 devices.
  [37752.580186] RAID1 conf printout:
  [37752.580190]  --- wd:1 rd:2
  [37752.580194]  disk 0, wo:0, o:1, dev:sdd
  [37752.580197]  disk 1, wo:1, o:0, dev:md1
  [37752.580199] RAID1 conf printout:
  [37752.580201]  --- wd:1 rd:2
  [37752.580203]  disk 0, wo:0, o:1, dev:sdd
  [37752.580228] BUG: unable to handle kernel paging request at 1dff2107
  [37752.584011] IP: [] close_write+0x6a/0xa0 [raid1]
  [37752.584011] PGD 20f667067 PUD 20f669067 PMD 0 
  [37752.584011] Oops:  [#1] SMP 
  [37752.584011] CPU 0 
  [37752.584011] Modules linked in: iptable_mangle iptable_filter 
ipt_MASQUERADE xt_tcpudp iptable_nat nf_nat nf_conntrack_ipv4 nf_conntrack 
nf_defrag_ipv4 ip_tables x_tables autofs4 nfsd nfs lockd fscache auth_rpcgss 
nfs_acl sunrpc snd_hda_codec_realtek snd_hda_intel snd_hda_codec snd_hwdep 
snd_pcm radeon snd_seq_midi ttm drm_kms_helper snd_rawmidi ftdi_sio 
snd_seq_midi_event snd_seq snd_timer drm ppdev snd_seq_device pl2303 usbserial 
serio_raw i2c_algo_bit mac_hid asus_atk0110 snd parport_pc parport soundcore 
snd_page_alloc edac_core edac_mce_amd i2c_piix4 k8temp shpchp 8021q garp s

[Kernel-packages] [Bug 1578305] 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/1578305

Title:
  Stoney powerplay support

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I'd love to submit a patch right now but I can't since the clone is
  taking way too long...

  The bug is in drivers/gpu/drm/amd/amdgpu/amdgpu_powerplay.c on line 83
  you need to insert

  case CHIP_STONEY:

  before CHIP_CARRIZO to get ST to successfully init with the amdgpu
  module.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-21-generic 4.4.0-21.37 [modified: 
boot/vmlinuz-4.4.0-21-generic]
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  amd1533 F pulseaudio
   /dev/snd/controlC0:  amd1533 F pulseaudio
  CurrentDesktop: Unity
  Date: Wed May  4 12:35:10 2016
  HibernationDevice: RESUME=UUID=39b1897f-c3d9-4222-9b73-94e0f6527917
  InstallationDate: Installed on 2016-05-04 (0 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  IwConfig:
   enx54b80aefee18  no wireless extensions.
   
   enx1a1b9c20  no wireless extensions.
   
   lono wireless extensions.
  MachineType: AMD Gardenia-ST
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic.efi.signed 
root=UUID=f4bc1961-0964-4010-a6e5-401bbfe28352 ro quiet splash vt.handoff=7 
amdgpu.powerplay=0
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-21-generic N/A
   linux-backports-modules-4.4.0-21-generic  N/A
   linux-firmware1.157
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/30/2015
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: WGY5930N_Weekly_15_09_3
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: Gardenia-ST
  dmi.board.vendor: AMD
  dmi.board.version: Base Board Version
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Chassis Manufacturer
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrWGY5930N_Weekly_15_09_3:bd09/30/2015:svnAMD:pnGardenia-ST:pvr1:rvnAMD:rnGardenia-ST:rvrBaseBoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion:
  dmi.product.name: Gardenia-ST
  dmi.product.version: 1
  dmi.sys.vendor: AMD

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1578305/+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 1561830] Re: Hard disk writes fail in 16.04 daily on nForce 430

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

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

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

** Tags added: performing-bisect

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

Title:
  Hard disk writes fail in 16.04 daily on nForce 430

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

Bug description:
  I have an old PC I use for testing new operating systems.  It has
  previously had Ubuntu 15.10 installed and working.  The motherboard is
  an Asus M2NPV-VM, with Nvidia nForce 430 chipset and Nvidia GeForce
  6150 GPU.  I have installed an Nvidia GT220 card to use for more
  modern video support.

  When I attempt to install Ubuntu 16.04 beta (daily xenial-desktop-
  amd64.iso file downloaded 24/03/2016  18:17), it starts to write to
  the hard disk (Samsung HD103UJ), and after a short time the install
  got lots of disk write errors in kern.log.  After the errors, the disk
  was unable to be read either, with "fdisk -l /dev/sda" failing to read
  a sector, where it had worked before starting the install.  Unplugging
  the SATA cable to the drive and plugging it in again made the drive
  work again (on /dev/sdc), but another attempt to install failed with
  the same write errors.

  I noticed that the log had swap write errors also, so I rebooted the
  install DVD again, and this time did a "swapoff -a" command before
  attempting to install, but got the same errors again.  So I found my
  Ubuntu 15.10 install DVD and tried a new install from that, which
  worked just fine.

  On rebooting with my 16.04 daily DVD, I again did "swapoff -a" so that
  the DVD based system would run normally, then tried mounting the EXT4
  system partition I had just installed using the 15.10 install DVD.
  That worked, so I tried dd commands to do test writes to that
  partition.  The following commands worked:

dd if=/dev/zero of=/mnt/sda8/tmp/output bs=8k count=10k
dd if=/dev/zero of=/mnt/sda8/tmp/output bs=8k count=100k

  but when I did this command:

dd if=/dev/zero of=/mnt/sda8/tmp/output bs=8k count=1000k

  after a while errors started appearing in kern.log, just as with the
  attempts to install 16.04.

  It appears that with sustained write activity, the errors will start
  and then the drive will become unusable until it is unplugged and
  plugged in again.

  I have attached the kern.log and syslog files from the 15.10 install
  that worked, and the 16.04 install attempt that failed.  The first
  error message appears to be this:

  ata3: EH in SWNCQ mode,QC:qc_active 0x1FFF sactive 0x1FFF
  ata3: SWNCQ:qc_active 0x1 defer_bits 0x1FFE last_issue_tag 0x0
  dhfis 0x1 dmafis 0x0 sdbfis 0x0

  which leads me to suspect a problem with the handling of the SATA 
controller's interrupts.
  --- 
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 2233 F pulseaudio
   /dev/snd/controlC1:  ubuntu 2233 F pulseaudio
  CasperVersion: 1.368
  DistroRelease: Ubuntu 16.04
  IwConfig:
   enp0s20   no wireless extensions.
   
   lono wireless extensions.
   
   enp2s9no wireless extensions.
  LiveMediaBuild: Ubuntu 16.04 LTS "Xenial Xerus" - Beta amd64 (20160323)
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 002: ID 0458:0118 KYE Systems Corp. (Mouse Systems) 
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: System manufacturer System Product Name
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: file=/cdrom/preseed/hostname.seed boot=casper 
initrd=/casper/initrd.lz quiet splash ---
  ProcVersionSignature: Ubuntu 4.4.0-15.31-generic 4.4.6
  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
  RfKill:
   
  Tags:  xenial
  Uname: Linux 4.4.0-15-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 08/07/2008
  dmi.bios.vendor: Phoenix Technologies, LTD
  dmi.bios.version: ASUS M2NPV-VM ACPI BIOS Revision 1401
  dmi.board.name: M2NPV-VM
  dmi.board.vendor: ASUSTek Computer INC.
  dmi.board.version: 1.xx
  dmi.chassis.asset.tag: 123456789000
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnPhoenixT

[Kernel-packages] [Bug 1578305] Re: Stoney powerplay support

2016-05-04 Thread Tom St Denis

Sorry I meant this commit

https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/drivers/gpu/drm/amd/amdgpu/amdgpu_powerplay.c?id=9c97e75f0fe6f98285127fb0424862087916e83f

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

Title:
  Stoney powerplay support

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I'd love to submit a patch right now but I can't since the clone is
  taking way too long...

  The bug is in drivers/gpu/drm/amd/amdgpu/amdgpu_powerplay.c on line 83
  you need to insert

  case CHIP_STONEY:

  before CHIP_CARRIZO to get ST to successfully init with the amdgpu
  module.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-21-generic 4.4.0-21.37 [modified: 
boot/vmlinuz-4.4.0-21-generic]
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  amd1533 F pulseaudio
   /dev/snd/controlC0:  amd1533 F pulseaudio
  CurrentDesktop: Unity
  Date: Wed May  4 12:35:10 2016
  HibernationDevice: RESUME=UUID=39b1897f-c3d9-4222-9b73-94e0f6527917
  InstallationDate: Installed on 2016-05-04 (0 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  IwConfig:
   enx54b80aefee18  no wireless extensions.
   
   enx1a1b9c20  no wireless extensions.
   
   lono wireless extensions.
  MachineType: AMD Gardenia-ST
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic.efi.signed 
root=UUID=f4bc1961-0964-4010-a6e5-401bbfe28352 ro quiet splash vt.handoff=7 
amdgpu.powerplay=0
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-21-generic N/A
   linux-backports-modules-4.4.0-21-generic  N/A
   linux-firmware1.157
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/30/2015
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: WGY5930N_Weekly_15_09_3
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: Gardenia-ST
  dmi.board.vendor: AMD
  dmi.board.version: Base Board Version
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Chassis Manufacturer
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrWGY5930N_Weekly_15_09_3:bd09/30/2015:svnAMD:pnGardenia-ST:pvr1:rvnAMD:rnGardenia-ST:rvrBaseBoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion:
  dmi.product.name: Gardenia-ST
  dmi.product.version: 1
  dmi.sys.vendor: AMD

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

2016-05-04 Thread Tom St Denis

This is fixed in upstream on the v4.5 tag by the following commit

https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/drivers/gpu/drm/amd/amdgpu/amdgpu_powerplay.c?id=3466904d38ff1e63f0a19cb31166db67f2d05c61

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

Title:
  Stoney powerplay support

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I'd love to submit a patch right now but I can't since the clone is
  taking way too long...

  The bug is in drivers/gpu/drm/amd/amdgpu/amdgpu_powerplay.c on line 83
  you need to insert

  case CHIP_STONEY:

  before CHIP_CARRIZO to get ST to successfully init with the amdgpu
  module.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-21-generic 4.4.0-21.37 [modified: 
boot/vmlinuz-4.4.0-21-generic]
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  amd1533 F pulseaudio
   /dev/snd/controlC0:  amd1533 F pulseaudio
  CurrentDesktop: Unity
  Date: Wed May  4 12:35:10 2016
  HibernationDevice: RESUME=UUID=39b1897f-c3d9-4222-9b73-94e0f6527917
  InstallationDate: Installed on 2016-05-04 (0 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  IwConfig:
   enx54b80aefee18  no wireless extensions.
   
   enx1a1b9c20  no wireless extensions.
   
   lono wireless extensions.
  MachineType: AMD Gardenia-ST
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic.efi.signed 
root=UUID=f4bc1961-0964-4010-a6e5-401bbfe28352 ro quiet splash vt.handoff=7 
amdgpu.powerplay=0
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-21-generic N/A
   linux-backports-modules-4.4.0-21-generic  N/A
   linux-firmware1.157
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/30/2015
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: WGY5930N_Weekly_15_09_3
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: Gardenia-ST
  dmi.board.vendor: AMD
  dmi.board.version: Base Board Version
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Chassis Manufacturer
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrWGY5930N_Weekly_15_09_3:bd09/30/2015:svnAMD:pnGardenia-ST:pvr1:rvnAMD:rnGardenia-ST:rvrBaseBoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion:
  dmi.product.name: Gardenia-ST
  dmi.product.version: 1
  dmi.sys.vendor: AMD

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1578305/+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 1578317] [NEW] Mouse stuck at start-up

2016-05-04 Thread josep

Public bug reported:

My mouse is stuck at start-up. A workaround is to enter "sudo rmmod
usbhid; modprobe usbhid" and the mouse starts working.

josep@josep-GJ306AA-ABE-m8175-es:~$ lsusb
Bus 002 Device 002: ID 058f:6362 Alcor Micro Corp. Flash Card Reader/Writer
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 008 Device 005: ID 050d:016a Belkin Components Bluetooth Mini Dongle
Bus 008 Device 004: ID 0a5c:4503 Broadcom Corp. Mouse (Boot Interface Subclass)
Bus 008 Device 003: ID 0a5c:4502 Broadcom Corp. Keyboard (Boot Interface 
Subclass)
Bus 008 Device 002: ID 0a5c:4500 Broadcom Corp. BCM2046B1 USB 2.0 Hub (part of 
BCM2046 Bluetooth)
Bus 008 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 004: ID 15d9:0a4c Trust International B.V. USB+PS/2 Optical Mouse
Bus 001 Device 002: ID 05e3:0608 Genesys Logic, Inc. Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: linux-image-4.4.0-21-generic 4.4.0-21.37 [modified: 
boot/vmlinuz-4.4.0-21-generic]
ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
Uname: Linux 4.4.0-21-generic x86_64
ApportVersion: 2.20.1-0ubuntu2
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  josep  1664 F pulseaudio
CurrentDesktop: Unity
Date: Wed May  4 19:08:48 2016
HibernationDevice: RESUME=UUID=b0bbcadd-00af-44cd-8f5d-eea7fee41c90
InstallationDate: Installed on 2016-04-28 (6 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
IwConfig:
 enp0s25   no wireless extensions.
 
 lono wireless extensions.
 
 enp1s0no wireless extensions.
MachineType: HP-Pavilion GJ306AA-ABE m8175.es
ProcFB: 0 nouveaufb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic 
root=UUID=816f2dbe-34e1-4512-a2b8-565bc86cb28e ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-4.4.0-21-generic N/A
 linux-backports-modules-4.4.0-21-generic  N/A
 linux-firmware1.157
RfKill:
 0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/11/2007
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 5.05
dmi.board.name: Berkeley
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: 1.xx
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Hewlett-Packard
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr5.05:bd07/11/2007:svnHP-Pavilion:pnGJ306AA-ABEm8175.es:pvr:rvnASUSTeKComputerINC.:rnBerkeley:rvr1.xx:cvnHewlett-Packard:ct3:cvrChassisVersion:
dmi.product.name: GJ306AA-ABE m8175.es
dmi.sys.vendor: HP-Pavilion

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


** Tags: amd64 apport-bug xenial

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

Title:
  Mouse stuck at start-up

Status in linux package in Ubuntu:
  New

Bug description:
  My mouse is stuck at start-up. A workaround is to enter "sudo rmmod
  usbhid; modprobe usbhid" and the mouse starts working.

  josep@josep-GJ306AA-ABE-m8175-es:~$ lsusb
  Bus 002 Device 002: ID 058f:6362 Alcor Micro Corp. Flash Card Reader/Writer
  Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 008 Device 005: ID 050d:016a Belkin Components Bluetooth Mini Dongle
  Bus 008 Device 004: ID 0a5c:4503 Broadcom Corp. Mouse (Boot Interface 
Subclass)
  Bus 008 Device 003: ID 0a5c:4502 Broadcom Corp. Keyboard (Boot Interface 
Subclass)
  Bus 008 Device 002: ID 0a5c:4500 Broadcom Corp. BCM2046B1 USB 2.0 Hub (part 
of BCM2046 Bluetooth)
  Bus 008 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  Bus 001 Device 004: ID 15d9:0a4c Trust International B.V. USB+PS/2 Optical 
Mouse
  Bus 001 Device 002: ID 05e3:0608 Genesys Logic, Inc. Hub
  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-21-generic 4.4.0-21.37 [modified: 
boot/vmlinuz-4.4.0-21-generic]
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  ApportVersion: 2.20

[Kernel-packages] [Bug 1559308] Re: Plugging HDMI screen in causes system hang

2016-05-04 Thread Ethan

Kernel 4.4.8  solved my issues completely! I can plug any monitor before
or after boot using DP or HDMI. I also have multiple window managers
working flawlessly.

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

Title:
  Plugging HDMI screen in causes system hang

Status in linux package in Ubuntu:
  Fix Committed

Bug description:
  I have a 4K UHD laptop screen and am running Ubuntu Gnome 16.04 Beta1
  using 4.4.0-13-generic and the Nouveau drivers.

  If I plug in an external HDMI monitor (FHD) either into either HDMI
  port (there's one on the machine and there's one available via a usb
  3.1 extra adaptor) then the whole system hangs, completely
  unresponsive and needing a hard reboot. Before hanging the 2nd display
  gets an image as expected, but the laptop's screen flashes randomly,
  sometimes you see weird artifacts. Then the hang comes.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xserver-xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-13.29-generic 4.4.5
  Uname: Linux 4.4.0-13-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: GNOME
  Date: Fri Mar 18 20:43:42 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Skylake Integrated Graphics [8086:191b] (rev 06) (prog-if 
00 [VGA controller])
 Subsystem: Dell Skylake Integrated Graphics [1028:06e4]
 Subsystem: Dell GM107M [GeForce GTX 960M] [1028:06e4]
  InstallationDate: Installed on 2016-03-15 (3 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Alpha amd64 
(20160225.1)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 04f3:21d5 Elan Microelectronics Corp. 
   Bus 001 Device 002: ID 0a5c:6410 Broadcom Corp. 
   Bus 001 Device 004: ID 0c45:6713 Microdia 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. XPS 15 9550
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-13-generic.efi.signed 
root=UUID=b026feed-8801-44f4-9f3f-c245f4a1f25e ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/25/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 01.01.19
  dmi.board.name: 0N7TVV
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr01.01.19:bd01/25/2016:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0N7TVV:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 15 9550
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.1.2-1ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.1.2-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.1-1ubuntu4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.6.1-1ubuntu2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160218-1ubuntu3
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Fri Mar 18 17:28:07 2016
  xserver.configfile: default
  xserver.errors:
   Failed to load module "nvidia" (module does not exist, 0)
   Failed to load module "nvidia" (module does not exist, 0)
   Unknown chipset: NV117
   SynPS/2 Synaptics TouchPad: Read error 19
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id5182 
   vendor SHP
  xserver.version: 2:1.18.1-1ubuntu4

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1559308/+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-05-04 Thread faulpeltz

@jsalisbury
We have 3.13.0-34.60 already running for about 22hours straight, no problems 
yet, as well as dfbdac2e, which also runs fine for now.
I'll just keep it running for a few days
Also, unfortunately, our result for 5e6cf71 might be invalid because the test 
machine ran out of disk space on the host because of excessive snapshot disks 
piling up. I had to add a delay of a couple of minutes after each backup to 
prevent this from happening, this caused basically the same error (kernel error 
message, readonly remount, disk i/o hang) as the real crash
So if things are stable with those two versions I will rerun 5e6cf71 and 
83215219 to make sure the result can be trusted
You already tested a kernel with 6ad4874 reverted, right? Are we sure this is 
not the culprit?

@emsi
We experienced that too, but weirdly trying to crash it by creating snapshots 
in a loop only caused one crash on one machine and wasnt reproducible any more

-- 
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
Status in linux source package in Xenial:
  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 1578325] Missing required logs.

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

apport-collect 1578325

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

Title:
  Kernel Oops - BUG: unable to handle kernel NULL pointer dereference at
  0010; RIP is 0010:[]
  [] propagate_one+0xbe/0x1c0

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I cannot log in to Ubuntu anymore:
   - the default login hangs
   - switching to a VT shows the Kernel Oops and then nothing else works

  Description:  Ubuntu 16.04 LTS
  Release:  16.04

  linux-image-generic:
Installed: 4.4.0.21.22
Candidate: 4.4.0.21.22
Version table:
   *** 4.4.0.21.22 500
  500 http://ubuntu.mirror.su.se/ubuntu xenial/main amd64 Packages
  100 /var/lib/dpkg/status

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1578325/+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 1578325] [NEW] Kernel Oops - BUG: unable to handle kernel NULL pointer dereference at 0000000000000010; RIP is 0010:[] [] propagate_one+0xbe/

Public bug reported:

I cannot log in to Ubuntu anymore:
 - the default login hangs
 - switching to a VT shows the Kernel Oops and then nothing else works

Description:Ubuntu 16.04 LTS
Release:16.04

linux-image-generic:
  Installed: 4.4.0.21.22
  Candidate: 4.4.0.21.22
  Version table:
 *** 4.4.0.21.22 500
500 http://ubuntu.mirror.su.se/ubuntu xenial/main amd64 Packages
100 /var/lib/dpkg/status

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

** Attachment added: "Kernel Oops.log"
   
https://bugs.launchpad.net/bugs/1578325/+attachment/4655827/+files/Kernel%20Oops.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/1578325

Title:
  Kernel Oops - BUG: unable to handle kernel NULL pointer dereference at
  0010; RIP is 0010:[]
  [] propagate_one+0xbe/0x1c0

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I cannot log in to Ubuntu anymore:
   - the default login hangs
   - switching to a VT shows the Kernel Oops and then nothing else works

  Description:  Ubuntu 16.04 LTS
  Release:  16.04

  linux-image-generic:
Installed: 4.4.0.21.22
Candidate: 4.4.0.21.22
Version table:
   *** 4.4.0.21.22 500
  500 http://ubuntu.mirror.su.se/ubuntu xenial/main amd64 Packages
  100 /var/lib/dpkg/status

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

Title:
  Mouse stuck at start-up

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  My mouse is stuck at start-up. A workaround is to enter "sudo rmmod
  usbhid; modprobe usbhid" and the mouse starts working.

  josep@josep-GJ306AA-ABE-m8175-es:~$ lsusb
  Bus 002 Device 002: ID 058f:6362 Alcor Micro Corp. Flash Card Reader/Writer
  Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 008 Device 005: ID 050d:016a Belkin Components Bluetooth Mini Dongle
  Bus 008 Device 004: ID 0a5c:4503 Broadcom Corp. Mouse (Boot Interface 
Subclass)
  Bus 008 Device 003: ID 0a5c:4502 Broadcom Corp. Keyboard (Boot Interface 
Subclass)
  Bus 008 Device 002: ID 0a5c:4500 Broadcom Corp. BCM2046B1 USB 2.0 Hub (part 
of BCM2046 Bluetooth)
  Bus 008 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  Bus 001 Device 004: ID 15d9:0a4c Trust International B.V. USB+PS/2 Optical 
Mouse
  Bus 001 Device 002: ID 05e3:0608 Genesys Logic, Inc. Hub
  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-21-generic 4.4.0-21.37 [modified: 
boot/vmlinuz-4.4.0-21-generic]
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  josep  1664 F pulseaudio
  CurrentDesktop: Unity
  Date: Wed May  4 19:08:48 2016
  HibernationDevice: RESUME=UUID=b0bbcadd-00af-44cd-8f5d-eea7fee41c90
  InstallationDate: Installed on 2016-04-28 (6 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  IwConfig:
   enp0s25   no wireless extensions.
   
   lono wireless extensions.
   
   enp1s0no wireless extensions.
  MachineType: HP-Pavilion GJ306AA-ABE m8175.es
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic 
root=UUID=816f2dbe-34e1-4512-a2b8-565bc86cb28e ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-21-generic N/A
   linux-backports-modules-4.4.0-21-generic  N/A
   linux-firmware1.157
  RfKill:
   0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/11/2007
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 5.05
  dmi.board.name: Berkeley
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr5.05:bd07/11/2007:svnHP-Pavilion:pnGJ306AA-ABEm8175.es:pvr:rvnASUSTeKComputerINC.:rnBerkeley:rvr1.xx:cvnHewlett-Packard:ct3:cvrChassisVersion:
  dmi.product.name: GJ306AA-ABE m8175.es
  dmi.sys.vendor: HP-Pavilion

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1578317/+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 1578325] Re: Kernel Oops - BUG: unable to handle kernel NULL pointer dereference at 0000000000000010; RIP is 0010:[] [] propagate_one+0xbe/0x

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

Title:
  Kernel Oops - BUG: unable to handle kernel NULL pointer dereference at
  0010; RIP is 0010:[]
  [] propagate_one+0xbe/0x1c0

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I cannot log in to Ubuntu anymore:
   - the default login hangs
   - switching to a VT shows the Kernel Oops and then nothing else works

  Description:  Ubuntu 16.04 LTS
  Release:  16.04

  linux-image-generic:
Installed: 4.4.0.21.22
Candidate: 4.4.0.21.22
Version table:
   *** 4.4.0.21.22 500
  500 http://ubuntu.mirror.su.se/ubuntu xenial/main amd64 Packages
  100 /var/lib/dpkg/status

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1578325/+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 1578305] Re: Stoney powerplay support

** Also affects: linux (Ubuntu Yakkety)
   Importance: Undecided
   Status: Confirmed

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

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

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

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

Title:
  Stoney powerplay support

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  In Progress
Status in linux source package in Yakkety:
  Fix Released

Bug description:
  I'd love to submit a patch right now but I can't since the clone is
  taking way too long...

  The bug is in drivers/gpu/drm/amd/amdgpu/amdgpu_powerplay.c on line 83
  you need to insert

  case CHIP_STONEY:

  before CHIP_CARRIZO to get ST to successfully init with the amdgpu
  module.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-21-generic 4.4.0-21.37 [modified: 
boot/vmlinuz-4.4.0-21-generic]
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  amd1533 F pulseaudio
   /dev/snd/controlC0:  amd1533 F pulseaudio
  CurrentDesktop: Unity
  Date: Wed May  4 12:35:10 2016
  HibernationDevice: RESUME=UUID=39b1897f-c3d9-4222-9b73-94e0f6527917
  InstallationDate: Installed on 2016-05-04 (0 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  IwConfig:
   enx54b80aefee18  no wireless extensions.
   
   enx1a1b9c20  no wireless extensions.
   
   lono wireless extensions.
  MachineType: AMD Gardenia-ST
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic.efi.signed 
root=UUID=f4bc1961-0964-4010-a6e5-401bbfe28352 ro quiet splash vt.handoff=7 
amdgpu.powerplay=0
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-21-generic N/A
   linux-backports-modules-4.4.0-21-generic  N/A
   linux-firmware1.157
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/30/2015
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: WGY5930N_Weekly_15_09_3
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: Gardenia-ST
  dmi.board.vendor: AMD
  dmi.board.version: Base Board Version
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Chassis Manufacturer
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrWGY5930N_Weekly_15_09_3:bd09/30/2015:svnAMD:pnGardenia-ST:pvr1:rvnAMD:rnGardenia-ST:rvrBaseBoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion:
  dmi.product.name: Gardenia-ST
  dmi.product.version: 1
  dmi.sys.vendor: AMD

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1578305/+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 1570195] Re: Net tools cause kernel soft lockup after DPDK touched VirtIO-pci devices

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

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

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

Title:
  Net tools cause kernel soft lockup after DPDK touched  VirtIO-pci
  devices

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

Bug description:
  Guys,

   I'm facing an issue here with both "ethtool" and "ip", while trying
  to manage black-listed by DPDK PCI VirtIO devices.

   You'll need an Ubuntu Xenial KVM guest, with 4 VirtIO vNIC cards, to
  run those tests

   PCI device example from inside a Xenial guest:

  ---
  # lspci | grep Ethernet
  00:03.0 Ethernet controller: Red Hat, Inc Virtio network device
  00:04.0 Ethernet controller: Red Hat, Inc Virtio network device
  00:05.0 Ethernet controller: Red Hat, Inc Virtio network device
  00:06.0 Ethernet controller: Red Hat, Inc Virtio network device
  ---

  Where "ens3" is the first / default interface, attached to Libvirt's
  "default" network. The "ens4" is reserved for "ethtool / ip" tests
  (attached to another Libvirt's network without IPs or DHCP), "ens5"
  will be "dpdk0" and "ens6" "dpdk1"...

  ---
   *** How it works?

   1- For example, try to enable multi-queue on DPDK's devices, boot
  your Xenial guest, and run:

   ethtool -L ens5 combined 4
   ethtool -L ens6 combined 4

   2- Install openvswitch-switch-dpdk configure DPDK and OVS and fire it
  up.

   https://help.ubuntu.com/16.04/serverguide/DPDK.html

   service openvswitch-switch stop
   service dpdk stop

   OVS DPDK Options (/etc/default/openvswitch-switch):

  --
  DPDK_OPTS='--dpdk -c 0x1 -n 4 --socket-mem 1024 --pci-blacklist 
:00:03.0,:00:04.0'
  --

   service dpdk start
   service openvswitch-switch start

   - Enable multi-queue on OVS+DPDK inside of the VM:

   ovs-vsctl set Open_vSwitch . other_config:n-dpdk-rxqs=4
   ovs-vsctl set Open_vSwitch . other_config:pmd-cpu-mask=0xff00

   * Multi-queue apparently works! ovs-vswitchd consumes more that 100%
  of CPU, meaning that it multi-queue is there...

   *** Where it fails?

   1- Reboot the VM and try to run ethtool again (or go straight to 2
  below):

   ethtool -L ens5 combined 4

   2- Try to fire up ens4:

   ip link set dev ens4 up

  
   # FAIL! Both commands hangs, consuming 100% of guest's CPU...

   So, it looks like a Linux fault, because it is "allowing" the DPDK
  VirtIO App (a user land App), to interfere with kernel devices in a
  strange way...

  Best,
  Thiago

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-18-generic 4.4.0-18.34
  ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6
  Uname: Linux 4.4.0-18-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Apr 14 00:35 seq
   crw-rw 1 root audio 116, 33 Apr 14 00:35 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.1-0ubuntu1
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: [Errno 2] No such file or directory: 'fuser'
  CRDA: N/A
  Date: Thu Apr 14 01:27:27 2016
  HibernationDevice: RESUME=UUID=833e999c-e066-433c-b8a2-4324bb8d56de
  InstallationDate: Installed on 2016-04-07 (7 days ago)
  InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Beta amd64 
(20160406)
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
  PciMultimedia:
   
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-18-generic 
root=UUID=9911604e-353b-491f-a0a9-804724350592 ro
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-18-generic N/A
   linux-backports-modules-4.4.0-18-generic  N/A
   linux-firmwareN/A
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/01/2014
  dmi.bios.vendor: SeaBIOS
  dmi.bios.version: Ubuntu-1.8.2-1ubuntu1
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-i440fx-wily
  dmi.modalias: 
dmi:bvnSeaBIOS:bvrUbuntu-1.8.2-1ubuntu1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-wily:cvnQEMU:ct1:cvrpc-i440fx-wily:
  dmi.product.name: Standard PC (i440FX + PIIX, 1996)
  dmi.product.version: pc-i440fx-wily
  dmi.sys.vendor: QEMU

To manage notifications about this

[Kernel-packages] [Bug 1578325] Re: Kernel Oops - BUG: unable to handle kernel NULL pointer dereference at 0000000000000010; RIP is 0010:[] [] propagate_one+0xbe/0x

Sorry, apport collecting does not work in recovery and I can't log in

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

Title:
  Kernel Oops - BUG: unable to handle kernel NULL pointer dereference at
  0010; RIP is 0010:[]
  [] propagate_one+0xbe/0x1c0

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I cannot log in to Ubuntu anymore:
   - the default login hangs
   - switching to a VT shows the Kernel Oops and then nothing else works

  Description:  Ubuntu 16.04 LTS
  Release:  16.04

  linux-image-generic:
Installed: 4.4.0.21.22
Candidate: 4.4.0.21.22
Version table:
   *** 4.4.0.21.22 500
  500 http://ubuntu.mirror.su.se/ubuntu xenial/main amd64 Packages
  100 /var/lib/dpkg/status

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1578325/+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 1546694] Re: Bluetooth cannot detect other devices (Lite-on 3014 + Atheros AR9565)

Fix came in via stable kernel releases; no verification required.

** Tags removed: verification-needed-trusty verification-needed-vivid
verification-needed-wily verification-needed-xenial

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

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

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

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

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

Title:
  Bluetooth cannot detect other devices (Lite-on 3014 + Atheros AR9565)

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

Bug description:
  I bought an Acer Cloudbook 11 but the bluetooth doesn't seem to work.
  The system shows the indicator icon but he doesn't detect any devices.
  The wifi works correctly.

  lsb_release -rb:
  Description:  Ubuntu 15.10
  Release:  15.10
  --- 
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  thenawaker   1387 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 15.10
  HibernationDevice: RESUME=UUID=8e395c05-c5e5-482d-ac5e-bbfeffcc37a6
  InstallationDate: Installed on 2016-02-17 (0 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 04ca:3014 Lite-On Technology Corp. 
   Bus 001 Device 003: ID 064e:9404 Suyin Corp. 
   Bus 001 Device 002: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Acer Aspire one 1-131
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-27-generic.efi.signed 
root=/dev/mmcblk0p2 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.2.0-27.32-generic 4.2.8-ckt1
  RelatedPackageVersions:
   linux-restricted-modules-4.2.0-27-generic N/A
   linux-backports-modules-4.2.0-27-generic  N/A
   linux-firmware1.144+ar3012
  Tags:  wily
  UdevLog: Error: [Errno 2] Aucun fichier ou dossier de ce type: '/var/log/udev'
  Uname: Linux 4.2.0-27-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 07/30/2015
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.06
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: Caltech
  dmi.board.vendor: Acer
  dmi.board.version: V1.06
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.06:bd07/30/2015:svnAcer:pnAspireone1-131:pvrV1.06:rvnAcer:rnCaltech:rvrV1.06:cvnAcer:ct10:cvrChassisVersion:
  dmi.product.name: Aspire one 1-131
  dmi.product.version: V1.06
  dmi.sys.vendor: Acer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1546694/+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 1556562] Re: VIA C7-D machine "kernel NULL pointer dereference" in skcipher_recvmsg_async

Hi Jeffrey-  Can you confirm that the Wily kernel (4.2.0-36.41)
currently in -proposed fixes this bug?  Thanks!

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

Title:
  VIA C7-D machine "kernel NULL pointer dereference" in
  skcipher_recvmsg_async

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

Bug description:
  I'm working on an Lubuntu 15 machine. It was chosen because it
  supports VIA C7-D processor and the VIA PM400 chipset without crashing
  (also see ). Lubuntu 15 uses the 4.2 kernel:

$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 15.10
Release:15.10
Codename:   wily

  And:

$ uname -a
Linux via 4.2.0-30-generic #36-Ubuntu SMP Fri Feb 26 00:57:19 UTC 2016 i686 
i686 i686 GNU/Linux

  When running a particular program (details below), it hangs in syscall
  248 and results in the following dmesg/syslog output. The process
  cannot be killed, the machine does not respond to a 'shutdown -r now',
  and the machine requires a hard reset.

  ...
  [ 4505.429577] BUG: unable to handle kernel NULL pointer dereference at 
0008
  [ 4505.429593] IP: [] skcipher_recvmsg_async.isra.13+0x4b2/0x500 
[algif_skcipher]
  [ 4505.429607] *pdpt = 34ee3001 *pde =  
  [ 4505.429614] Oops:  [#3] SMP 
  [ 4505.429621] Modules linked in: jitterentropy_rng drbg ansi_cprng 
algif_skcipher af_alg snd_hda_codec_realtek snd_hda_codec_generic snd_hda_intel 
snd_hda_codec snd_hda_core snd_hwdep snd_pcm snd_seq_midi snd_seq_midi_event 
snd_rawmidi padlock_sha snd_seq padlock_aes snd_seq_device via_cputemp 
snd_timer hwmon_vid via_rng snd input_leds serio_raw soundcore i2c_viapro 
shpchp 8250_fintek mac_hid parport_pc ppdev lp parport autofs4 pata_acpi 
hid_generic usbhid hid psmouse r8169 pata_via sata_via mii
  [ 4505.429689] CPU: 0 PID: 1532 Comm: afalgtest Tainted: G  D 
4.2.0-30-generic #36-Ubuntu
  [ 4505.429695] Hardware name: To Be Filled By O.E.M. To Be Filled By 
O.E.M./Weibu, BIOS 080014  11/17/2011
  [ 4505.429700] task: f4e0e040 ti: f4e3c000 task.ti: f4e3c000
  [ 4505.429705] EIP: 0060:[] EFLAGS: 00010202 CPU: 0
  [ 4505.429712] EIP is at skcipher_recvmsg_async.isra.13+0x4b2/0x500 
[algif_skcipher]
  [ 4505.429717] EAX: f3f97c00 EBX: f3f3ee00 ECX: f3f97c00 EDX: 
  [ 4505.429722] ESI: f3f3ee00 EDI: 0ff0 EBP: f4e3ddc8 ESP: f4e3dd70
  [ 4505.429726]  DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068
  [ 4505.429731] CR0: 80050033 CR2: 0008 CR3: 3247a520 CR4: 06b0
  [ 4505.429735] Stack:
  [ 4505.429738]  f3f97df4 f3f97c00 f3f97de0  f3f97c04 0020 
f4e3dd00 0018
  [ 4505.429750]  1ff0 f3fb4400 f3f97c04 0ff0 f4e3de40 f3f97de8 
f4e3de38 f3fa
  [ 4505.429761]  0002 0002 f3f97c00 f1f58180 c1210510 f4e3de38 
f4e3ddf4 f8a6cd6b
  [ 4505.429772] Call Trace:
  [ 4505.429788]  [] ? free_ioctx_users+0xa0/0xa0
  [ 4505.429795]  [] skcipher_recvmsg+0x2b/0x1f0 [algif_skcipher]
  [ 4505.429803]  [] ? skcipher_check_key.isra.8+0x2a/0xb0 
[algif_skcipher]
  [ 4505.429810]  [] skcipher_recvmsg_nokey+0x31/0x40 [algif_skcipher]
  [ 4505.429820]  [] sock_recvmsg+0x3d/0x50
  [ 4505.429826]  [] sock_read_iter+0x84/0xd0
  [ 4505.429833]  [] ? sock_recvmsg+0x50/0x50
  [ 4505.429839]  [] aio_run_iocb+0x110/0x2c0
  [ 4505.429846]  [] ? sock_recvmsg+0x50/0x50
  [ 4505.429854]  [] ? error_code+0x67/0x6c
  [ 4505.429865]  [] ? kmem_cache_alloc+0x1b4/0x1e0
  [ 4505.429875]  [] ? __fdget+0x12/0x20
  [ 4505.429881]  [] do_io_submit+0x1ef/0x4a0
  [ 4505.429893]  [] ? security_file_alloc+0x2f/0x50
  [ 4505.429900]  [] SyS_io_submit+0x20/0x30
  [ 4505.429911]  [] sysenter_do_call+0x12/0x12
  [ 4505.429915] Code: 00 00 00 75 24 8b 45 ac ff 52 0c 89 c7 83 ff 8d 75 8f 8b 
45 e4 3e ff 80 fc 01 00 00 bf ef fd ff ff e9 62 fc ff ff 8d 76 00 89 c8  52 
08 89 c7 eb db 8b 45 e4 31 d2 8b 80 20 02 00 00 8b 58 1c
  [ 4505.429982] EIP: [] skcipher_recvmsg_async.isra.13+0x4b2/0x500 
[algif_skcipher] SS:ESP 0068:f4e3dd70
  [ 4505.429991] CR2: 0008
  [ 4505.429997] ---[ end trace 3cce7cc6be0ad960 ]---

  **

  The process details is this is a failed self test for the upcoming
  OpenSSL 1.1.0. The OpenSSL RT bug report for this issue is at
  http://rt.openssl.org/Ticket/Display.html?id=4411. Two attempts to
  debug it resulted in two hung processes:

  $ ps -A | grep afalgtest
  1030 pts/000:00:00 afalgtest
  1196 pts/000:00:00 afalgtest

  And:

  via:test$ sudo cat /proc/1030/syscall 
  248 0xb7fd6000 0x1 0xbfff98d4 0xb7fb9270 0xbfff98e0 0xb7ec45f7 0xbfff986c 
0xb7fdbbe8
  via:test$ sudo cat /proc/1196/syscall 
  248 0xb7fd6000 0x1 0xbfff98d4 0xb7fb9270 0xbfff98e0 0xb7ec45f7 0xbfff986c 
0xb7fdbbe8

  Its not clear to me what that particular syscall is:

  $ cat /usr/include/asm-generic/unis

[Kernel-packages] [Bug 1578325] Re: Kernel Oops - BUG: unable to handle kernel NULL pointer dereference at 0000000000000010; RIP is 0010:[] [] propagate_one+0xbe/0x

** Attachment added: "version.log"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1578325/+attachment/4655911/+files/version.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/1578325

Title:
  Kernel Oops - BUG: unable to handle kernel NULL pointer dereference at
  0010; RIP is 0010:[]
  [] propagate_one+0xbe/0x1c0

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I cannot log in to Ubuntu anymore:
   - the default login hangs
   - switching to a VT shows the Kernel Oops and then nothing else works

  Description:  Ubuntu 16.04 LTS
  Release:  16.04

  linux-image-generic:
Installed: 4.4.0.21.22
Candidate: 4.4.0.21.22
Version table:
   *** 4.4.0.21.22 500
  500 http://ubuntu.mirror.su.se/ubuntu xenial/main amd64 Packages
  100 /var/lib/dpkg/status

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1578325/+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 1578305] Re: Stoney powerplay support

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

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

Title:
  Stoney powerplay support

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

Bug description:
  I'd love to submit a patch right now but I can't since the clone is
  taking way too long...

  The bug is in drivers/gpu/drm/amd/amdgpu/amdgpu_powerplay.c on line 83
  you need to insert

  case CHIP_STONEY:

  before CHIP_CARRIZO to get ST to successfully init with the amdgpu
  module.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-21-generic 4.4.0-21.37 [modified: 
boot/vmlinuz-4.4.0-21-generic]
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  amd1533 F pulseaudio
   /dev/snd/controlC0:  amd1533 F pulseaudio
  CurrentDesktop: Unity
  Date: Wed May  4 12:35:10 2016
  HibernationDevice: RESUME=UUID=39b1897f-c3d9-4222-9b73-94e0f6527917
  InstallationDate: Installed on 2016-05-04 (0 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  IwConfig:
   enx54b80aefee18  no wireless extensions.
   
   enx1a1b9c20  no wireless extensions.
   
   lono wireless extensions.
  MachineType: AMD Gardenia-ST
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic.efi.signed 
root=UUID=f4bc1961-0964-4010-a6e5-401bbfe28352 ro quiet splash vt.handoff=7 
amdgpu.powerplay=0
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-21-generic N/A
   linux-backports-modules-4.4.0-21-generic  N/A
   linux-firmware1.157
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/30/2015
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: WGY5930N_Weekly_15_09_3
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: Gardenia-ST
  dmi.board.vendor: AMD
  dmi.board.version: Base Board Version
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Chassis Manufacturer
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrWGY5930N_Weekly_15_09_3:bd09/30/2015:svnAMD:pnGardenia-ST:pvr1:rvnAMD:rnGardenia-ST:rvrBaseBoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion:
  dmi.product.name: Gardenia-ST
  dmi.product.version: 1
  dmi.sys.vendor: AMD

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1578305/+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 1578325] Re: Kernel Oops - BUG: unable to handle kernel NULL pointer dereference at 0000000000000010; RIP is 0010:[] [] propagate_one+0xbe/0x

** Attachment added: "lspci-vnvn.log"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1578325/+attachment/4655912/+files/lspci-vnvn.log

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

Title:
  Kernel Oops - BUG: unable to handle kernel NULL pointer dereference at
  0010; RIP is 0010:[]
  [] propagate_one+0xbe/0x1c0

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I cannot log in to Ubuntu anymore:
   - the default login hangs
   - switching to a VT shows the Kernel Oops and then nothing else works

  Description:  Ubuntu 16.04 LTS
  Release:  16.04

  linux-image-generic:
Installed: 4.4.0.21.22
Candidate: 4.4.0.21.22
Version table:
   *** 4.4.0.21.22 500
  500 http://ubuntu.mirror.su.se/ubuntu xenial/main amd64 Packages
  100 /var/lib/dpkg/status

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1578325/+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 1543419] Re: ubuntu 14.04.4 installation with "Guided - use entire disk and set up LVM" fails for ext3 file system.

2016-05-04 Thread Steve Langasek

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

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

Title:
  ubuntu 14.04.4 installation with "Guided - use entire disk and set up
  LVM" fails for ext3 file system.

Status in linux package in Ubuntu:
  Invalid

Bug description:
  Problem Description
  ===
  ubuntu 14.04.4 installation on Firestone baremetal with "Guided - use entire 
disk and set up LVM" fails when ext3 is chosen as / file system. Below error 
message is displayed.

  
  ? [!!] Partition disks ?
  ?  ?
  ?Failed to create a file system?
  ? The ext3 file system creation in partition #1 of LVM VG FR21p01-vg,  ?
  ? LV root failed.  ?
  ?  ?
  ?   ?
  ?  ?
  

  
  Steps to Reproduce
  =
  1. Start netboot installation on Firestone baremetal machine from 
  
http://ports.ubuntu.com/ubuntu-ports/dists/trusty-proposed/main/installer-ppc64el/current/images/wily-netboot/
  2. During "Partition disks" select 
  Manual -> Guided partitioning -> Guided - use entire disk and set up LVM

?? [!!] Partition disks ???
? ?
? The installer can guide you through partitioning a disk (using  ?
? different standard schemes) or, if you prefer, you can do it?
? manually. With guided partitioning you will still have a chance later   ?
? to review and customise the results.?
? ?
? If you choose guided partitioning for an entire disk, you will next ?
? be asked which disk should be used. ?
? ?
? Partitioning method:?
? ?
?  Guided - use entire partition, SCSI5 (0,0,0), partition #2 (sdk)   ?
?  Guided - use the largest continuous free space ?   ?
?  Guided - use entire disk and set up LVM?   ?
?  Guided - use entire disk and set up encrypted LVM  ?
?  Manual ?
? ?
??
? ?
???

?? [!!] Partition disks ???
? ?
? This is an overview of your currently configured partitions and mount   ?
? points. Select a partition to modify its settings (file system, mount   ?
? point, etc.), a free space to create partitions, or a device to ?
? initialize its partition table. ?
? ?
?  Guided partitioning?
?  Configure software RAID?
?  Configure the Logical Volume Manager   ?   ?
?  Configure encrypted volumes?   ?
?  Configure iSCSI volumes?   ?
? ?   ?
?  LVM VG tul8p1-vg, LV root - 959.4 GB Linux device-mapper (linear)  ?   ?
?  > #1959.4 GBxfs?   ?
?  LVM VG tul8p1-vg, LV swap_1 - 40.5 GB Linux device-mapper (linear  ?   ?
?  > #1 40.5 GB F  swap  swap ?
? ?
??
? ?
??

[Kernel-packages] [Bug 1572316] Re: oops when propagating mounts into containers

Hi, I'm having a kernel oops with similar trace, but for me it happens at login 
time. Maybe there's an automatic mount.
Mine is https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1578325

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

Title:
  oops when propagating mounts into containers

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

Bug description:
  If I use LXD on xenial with a configuration that does something like:
  (/nfs in my case is an nfs mount, but based on the kernel code in
  question anything is probably okay):

  devices:
bind:
  type: disk
  source: /nfs
  path: /nfs
  recursive: "true"

  and then start the container and on the host, do a new mount:

  sudo mount $ipaddr:/some/nfs/path /nfs/newpath

  You get the following kernel oops:

  Apr 11 21:59:36 stock2 kernel: [ 1648.993034] Oops:  [#1] SMP 
  Apr 11 21:59:36 stock2 kernel: [ 1648.993415] Modules linked in: binfmt_misc 
veth rpcsec_gss_krb5 auth_rpcgss nfsv4 nfs lockd grace fscache xt_CHECKSUM 
iptable_mangle xt_tcpudp ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat 
nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack bridge stp llc 
iptable_filter ip_tables x_tables zfs(PO) zunicode(PO) zcommon(PO) znvpair(PO) 
spl(O) zavl(PO) ppdev kvm_intel parport_pc joydev kvm input_leds mac_hid 
irqbypass parport i2c_piix4 8250_fintek serio_raw ib_iser rdma_cm iw_cm ib_cm 
ib_sa ib_mad ib_core ib_addr sunrpc iscsi_tcp libiscsi_tcp libiscsi 
scsi_transport_iscsi autofs4 btrfs raid10 raid456 async_raid6_recov 
async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 
multipath linear cirrus ttm drm_kms_helper syscopyarea sysfillrect sysimgblt 
psmouse fb_sys_fops floppy drm pata_acpi
  Apr 11 21:59:36 stock2 kernel: [ 1649.002015] CPU: 2 PID: 9449 Comm: 
mount.nfs Tainted: P   O4.4.0-18-generic #34+tych0201604111025
  Apr 11 21:59:36 stock2 kernel: [ 1649.003037] Hardware name: QEMU Standard PC 
(i440FX + PIIX, 1996), BIOS Ubuntu-1.8.2-1ubuntu1 04/01/2014
  Apr 11 21:59:36 stock2 kernel: [ 1649.004042] task: 880074c1a580 ti: 
880067d3 task.ti: 880067d3
  Apr 11 21:59:36 stock2 kernel: [ 1649.004810] RIP: 0010:[]  
[] propagate_one+0xbe/0x1c0
  Apr 11 21:59:36 stock2 kernel: [ 1649.005654] RSP: 0018:880067d33d68  
EFLAGS: 00010297
  Apr 11 21:59:36 stock2 kernel: [ 1649.006211] RAX: 88003bb4ca80 RBX: 
880074ad8300 RCX: 880074503500
  Apr 11 21:59:36 stock2 kernel: [ 1649.006934] RDX:  RSI: 
019c RDI: 
  Apr 11 21:59:36 stock2 kernel: [ 1649.007656] RBP: 880067d33d78 R08: 
8800363bad80 R09: 813eac5c
  Apr 11 21:59:36 stock2 kernel: [ 1649.008390] R10: ea2b5800 R11: 
00018711 R12: 8800363ba600
  Apr 11 21:59:36 stock2 kernel: [ 1649.009111] R13: 880067d33dc0 R14: 
880074ad8300 R15: 
  Apr 11 21:59:36 stock2 kernel: [ 1649.009835] FS:  7f653eac4880() 
GS:88007cd0() knlGS:
  Apr 11 21:59:36 stock2 kernel: [ 1649.010642] CS:  0010 DS:  ES:  
CR0: 8005003b
  Apr 11 21:59:36 stock2 kernel: [ 1649.011237] CR2: 0010 CR3: 
77a4e000 CR4: 06e0
  Apr 11 21:59:36 stock2 kernel: [ 1649.011984] Stack:
  Apr 11 21:59:36 stock2 kernel: [ 1649.012255]  880074ad8300 
8800363ba600 880067d33db0 8123d060
  Apr 11 21:59:36 stock2 kernel: [ 1649.013070]  88003bb4ca80 
8800363ba600 88000c211980 
  Apr 11 21:59:36 stock2 kernel: [ 1649.013892]  880067d33e98 
880067d33df8 8122dd97 88003bb4c900
  Apr 11 21:59:36 stock2 kernel: [ 1649.014751] Call Trace:
  Apr 11 21:59:36 stock2 kernel: [ 1649.015053]  [] 
propagate_mnt+0x120/0x150
  Apr 11 21:59:36 stock2 kernel: [ 1649.015643]  [] 
attach_recursive_mnt+0x147/0x230
  Apr 11 21:59:36 stock2 kernel: [ 1649.016286]  [] 
graft_tree+0x58/0x90
  Apr 11 21:59:36 stock2 kernel: [ 1649.016809]  [] 
do_add_mount+0x8e/0xd0
  Apr 11 21:59:36 stock2 kernel: [ 1649.017342]  [] 
do_mount+0x2c0/0xe00
  Apr 11 21:59:36 stock2 kernel: [ 1649.017863]  [] ? 
copy_mount_options+0xb4/0x220
  Apr 11 21:59:36 stock2 kernel: [ 1649.018466]  [] 
SyS_mount+0x9f/0x100
  Apr 11 21:59:36 stock2 kernel: [ 1649.018996]  [] 
entry_SYSCALL_64_fastpath+0x16/0x71
  Apr 11 21:59:36 stock2 kernel: [ 1649.019631] Code: 39 90 d8 00 00 00 75 ec 
8b b0 10 01 00 00 48 89 3d 80 e1 f8 00 48 89 05 81 e1 f8 00 39 b1 10 01 00 00 
74 19 48 8b bf d8 00 00 00 <48> 8b 47 10 48 89 3d 5f e1 f8 00 48 89 05 60 e1 f8 
00 8b 43 30 
  Apr 11 21:59:36 stock2 kernel: [ 1649.022395] RIP  [] 
propagate_one+0xbe/0x1c0
  Apr 11 21:59:36 stock2 kernel: [ 1649.022990]  RSP 
  Apr 11 21:59:36 stock2 kernel: [ 1649.023362] CR2: 0010
  Apr 11 21:59:3

[Kernel-packages] [Bug 1470250] Re: [Hyper-V] Ubuntu 14.04.2 LTS Generation 2 SCSI Errors on VSS Based Backups

@faulpeltz,

Yes, I did test a kernel with commit 6ad4874.  I tried this before
starting the bisect since it looked suspect.

I'm still testing dfbdac2e as well and will let it run for another 24
hours.

-- 
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
Status in linux source package in Xenial:
  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 1561403] Re: CVE-2016-2117

2016-05-04 Thread Steve Beattie

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

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

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

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

** Changed in: linux-ti-omap4 (Ubuntu Precise)
   Status: New => Invalid

** Changed in: linux-armadaxp (Ubuntu Precise)
   Status: New => Invalid

** Changed in: linux-lts-utopic (Ubuntu Trusty)
   Status: New => Fix Committed

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

Title:
  CVE-2016-2117

Status in linux package in Ubuntu:
  New
Status in linux-armadaxp package in Ubuntu:
  Invalid
Status in linux-flo package in Ubuntu:
  New
Status in linux-goldfish package in Ubuntu:
  New
Status in linux-lts-quantal package in Ubuntu:
  Invalid
Status in linux-lts-raring package in Ubuntu:
  Invalid
Status in linux-lts-saucy package in Ubuntu:
  Invalid
Status in linux-lts-trusty package in Ubuntu:
  Invalid
Status in linux-lts-utopic package in Ubuntu:
  Invalid
Status in linux-lts-vivid package in Ubuntu:
  Invalid
Status in linux-lts-wily package in Ubuntu:
  Invalid
Status in linux-lts-xenial package in Ubuntu:
  Invalid
Status in linux-mako package in Ubuntu:
  New
Status in linux-manta package in Ubuntu:
  Invalid
Status in linux-raspi2 package in Ubuntu:
  New
Status in linux-ti-omap4 package in Ubuntu:
  Invalid
Status in linux source package in Precise:
  Invalid
Status in linux-armadaxp source package in Precise:
  Invalid
Status in linux-flo source package in Precise:
  Invalid
Status in linux-goldfish source package in Precise:
  Invalid
Status in linux-lts-quantal source package in Precise:
  Invalid
Status in linux-lts-raring source package in Precise:
  Invalid
Status in linux-lts-saucy source package in Precise:
  Invalid
Status in linux-lts-trusty source package in Precise:
  New
Status in linux-lts-utopic source package in Precise:
  Invalid
Status in linux-lts-vivid source package in Precise:
  Invalid
Status in linux-lts-wily source package in Precise:
  Invalid
Status in linux-lts-xenial source package in Precise:
  Invalid
Status in linux-mako source package in Precise:
  Invalid
Status in linux-manta source package in Precise:
  Invalid
Status in linux-raspi2 source package in Precise:
  Invalid
Status in linux-ti-omap4 source package in Precise:
  Invalid
Status in linux source package in Trusty:
  Fix Committed
Status in linux-armadaxp source package in Trusty:
  Invalid
Status in linux-flo source package in Trusty:
  Invalid
Status in linux-goldfish source package in Trusty:
  Invalid
Status in linux-lts-quantal source package in Trusty:
  Invalid
Status in linux-lts-raring source package in Trusty:
  Invalid
Status in linux-lts-saucy source package in Trusty:
  Invalid
Status in linux-lts-trusty source package in Trusty:
  Invalid
Status in linux-lts-utopic source package in Trusty:
  Fix Committed
Status in linux-lts-vivid source package in Trusty:
  New
Status in linux-lts-wily source package in Trusty:
  New
Status in linux-lts-xenial source package in Trusty:
  New
Status in linux-mako source package in Trusty:
  Invalid
Status in linux-manta source package in Trusty:
  Invalid
Status in linux-raspi2 source package in Trusty:
  Invalid
Status in linux-ti-omap4 source package in Trusty:
  Invalid
Status in linux source package in Vivid:
  New
Status in linux-armadaxp source package in Vivid:
  New
Status in linux-flo source package in Vivid:
  New
Status in linux-goldfish source package in Vivid:
  New
Status in linux-lts-quantal source package in Vivid:
  New
Status in linux-lts-raring source package in Vivid:
  New
Status in linux-lts-saucy source package in Vivid:
  New
Status in linux-lts-trusty source package in Vivid:
  New
Status in linux-lts-utopic source package in Vivid:
  New
Status in linux-lts-vivid source package in Vivid:
  New
Status in linux-lts-wily source package in Vivid:
  New
Status in linux-lts-xenial source package in Vivid:
  New
Status in linux-mako source package in Vivid:
  New
Status in linux-manta source package in Vivid:
  New
Status in linux-raspi2 source package in Vivid:
  New
Status in linux-ti-omap4 source package in Vivid:
  New
Status in linux source package in Wily:
  Fix Committed
Status in linux-armadaxp source package in Wily:
  Invalid
Status in linux-flo source package in Wily:
  New
Status in linux-goldfish source package in Wily:
  New
Status in linux-lts-quantal source package in Wily:
  Invalid
Status in linux-lts-raring source package in Wily:
  Invalid
Status in linux-lts-saucy source package in Wily:
  Invalid
Status in linux-lts-trusty source package in Wily:
  Invalid
Status in linux-lts-utopic source package in Wily:
  Invalid
Status in linux-lts-vivid source package in Wily:
  Invalid
Status in linux-lts-wi

[Kernel-packages] [Bug 1578325] Re: Kernel Oops - BUG: unable to handle kernel NULL pointer dereference at 0000000000000010; RIP is 0010:[] [] propagate_one+0xbe/0x

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

Removing lxd solved the problem

Workaround:
sudo apt remove lxd

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

** Changed in: lxd (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/1578325

Title:
  Kernel Oops - BUG: unable to handle kernel NULL pointer dereference at
  0010; RIP is 0010:[]
  [] propagate_one+0xbe/0x1c0

Status in linux package in Ubuntu:
  Confirmed
Status in lxd package in Ubuntu:
  Confirmed

Bug description:
  I cannot log in to Ubuntu anymore:
   - the default login hangs
   - switching to a VT shows the Kernel Oops and then nothing else works

  Description:  Ubuntu 16.04 LTS
  Release:  16.04

  linux-image-generic:
Installed: 4.4.0.21.22
Candidate: 4.4.0.21.22
Version table:
   *** 4.4.0.21.22 500
  500 http://ubuntu.mirror.su.se/ubuntu xenial/main amd64 Packages
  100 /var/lib/dpkg/status

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1578325/+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 1578325] Re: Kernel Oops - BUG: unable to handle kernel NULL pointer dereference at 0000000000000010; RIP is 0010:[] [] propagate_one+0xbe/0x

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

This bug has the same stack trace of
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1572316

** This bug has been marked a duplicate of bug 1572316
   oops when propagating mounts into containers

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

Title:
  Kernel Oops - BUG: unable to handle kernel NULL pointer dereference at
  0010; RIP is 0010:[]
  [] propagate_one+0xbe/0x1c0

Status in linux package in Ubuntu:
  Confirmed
Status in lxd package in Ubuntu:
  Confirmed

Bug description:
  I cannot log in to Ubuntu anymore:
   - the default login hangs
   - switching to a VT shows the Kernel Oops and then nothing else works

  Description:  Ubuntu 16.04 LTS
  Release:  16.04

  linux-image-generic:
Installed: 4.4.0.21.22
Candidate: 4.4.0.21.22
Version table:
   *** 4.4.0.21.22 500
  500 http://ubuntu.mirror.su.se/ubuntu xenial/main amd64 Packages
  100 /var/lib/dpkg/status

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1578325/+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 1561830] Re: Hard disk writes fail in 16.04 daily on nForce 430

I built a Xenial test kernel with a revert of commit 64d513ac31.  The
test kernel can be downloaded from:

http://kernel.ubuntu.com/~jsalisbury/lp1561830/

Can you test this kernel and see if it resolves 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/1561830

Title:
  Hard disk writes fail in 16.04 daily on nForce 430

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

Bug description:
  I have an old PC I use for testing new operating systems.  It has
  previously had Ubuntu 15.10 installed and working.  The motherboard is
  an Asus M2NPV-VM, with Nvidia nForce 430 chipset and Nvidia GeForce
  6150 GPU.  I have installed an Nvidia GT220 card to use for more
  modern video support.

  When I attempt to install Ubuntu 16.04 beta (daily xenial-desktop-
  amd64.iso file downloaded 24/03/2016  18:17), it starts to write to
  the hard disk (Samsung HD103UJ), and after a short time the install
  got lots of disk write errors in kern.log.  After the errors, the disk
  was unable to be read either, with "fdisk -l /dev/sda" failing to read
  a sector, where it had worked before starting the install.  Unplugging
  the SATA cable to the drive and plugging it in again made the drive
  work again (on /dev/sdc), but another attempt to install failed with
  the same write errors.

  I noticed that the log had swap write errors also, so I rebooted the
  install DVD again, and this time did a "swapoff -a" command before
  attempting to install, but got the same errors again.  So I found my
  Ubuntu 15.10 install DVD and tried a new install from that, which
  worked just fine.

  On rebooting with my 16.04 daily DVD, I again did "swapoff -a" so that
  the DVD based system would run normally, then tried mounting the EXT4
  system partition I had just installed using the 15.10 install DVD.
  That worked, so I tried dd commands to do test writes to that
  partition.  The following commands worked:

dd if=/dev/zero of=/mnt/sda8/tmp/output bs=8k count=10k
dd if=/dev/zero of=/mnt/sda8/tmp/output bs=8k count=100k

  but when I did this command:

dd if=/dev/zero of=/mnt/sda8/tmp/output bs=8k count=1000k

  after a while errors started appearing in kern.log, just as with the
  attempts to install 16.04.

  It appears that with sustained write activity, the errors will start
  and then the drive will become unusable until it is unplugged and
  plugged in again.

  I have attached the kern.log and syslog files from the 15.10 install
  that worked, and the 16.04 install attempt that failed.  The first
  error message appears to be this:

  ata3: EH in SWNCQ mode,QC:qc_active 0x1FFF sactive 0x1FFF
  ata3: SWNCQ:qc_active 0x1 defer_bits 0x1FFE last_issue_tag 0x0
  dhfis 0x1 dmafis 0x0 sdbfis 0x0

  which leads me to suspect a problem with the handling of the SATA 
controller's interrupts.
  --- 
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 2233 F pulseaudio
   /dev/snd/controlC1:  ubuntu 2233 F pulseaudio
  CasperVersion: 1.368
  DistroRelease: Ubuntu 16.04
  IwConfig:
   enp0s20   no wireless extensions.
   
   lono wireless extensions.
   
   enp2s9no wireless extensions.
  LiveMediaBuild: Ubuntu 16.04 LTS "Xenial Xerus" - Beta amd64 (20160323)
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 002: ID 0458:0118 KYE Systems Corp. (Mouse Systems) 
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: System manufacturer System Product Name
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: file=/cdrom/preseed/hostname.seed boot=casper 
initrd=/casper/initrd.lz quiet splash ---
  ProcVersionSignature: Ubuntu 4.4.0-15.31-generic 4.4.6
  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
  RfKill:
   
  Tags:  xenial
  Uname: Linux 4.4.0-15-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 08/07/2008
  dmi.bios.vendor: Phoenix Technologies, LTD
  dmi.bios.version: ASUS M2NPV-VM ACPI BIOS Revision 1401
  dmi.board.name: M2NPV-VM
  dmi.board.vendor: ASUSTek Computer INC.
  dmi.board.version: 1.xx
  dmi.chassis.asset.tag: 123456789000
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnPhoenixTechnologies,LTD:bvrASUSM2NPV-VMACPIBIOSRevis

[Kernel-packages] [Bug 1572316] Re: oops when propagating mounts into containers - RIP: 0010:[] [] propagate_one+0xbe/0x1c0

** Summary changed:

- oops when propagating mounts into containers
+ oops when propagating mounts into containers - RIP: 0010:[] 
[] propagate_one+0xbe/0x1c0

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

Title:
  oops when propagating mounts into containers - RIP:
  0010:[] []
  propagate_one+0xbe/0x1c0

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

Bug description:
  If I use LXD on xenial with a configuration that does something like:
  (/nfs in my case is an nfs mount, but based on the kernel code in
  question anything is probably okay):

  devices:
bind:
  type: disk
  source: /nfs
  path: /nfs
  recursive: "true"

  and then start the container and on the host, do a new mount:

  sudo mount $ipaddr:/some/nfs/path /nfs/newpath

  You get the following kernel oops:

  Apr 11 21:59:36 stock2 kernel: [ 1648.993034] Oops:  [#1] SMP 
  Apr 11 21:59:36 stock2 kernel: [ 1648.993415] Modules linked in: binfmt_misc 
veth rpcsec_gss_krb5 auth_rpcgss nfsv4 nfs lockd grace fscache xt_CHECKSUM 
iptable_mangle xt_tcpudp ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat 
nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack bridge stp llc 
iptable_filter ip_tables x_tables zfs(PO) zunicode(PO) zcommon(PO) znvpair(PO) 
spl(O) zavl(PO) ppdev kvm_intel parport_pc joydev kvm input_leds mac_hid 
irqbypass parport i2c_piix4 8250_fintek serio_raw ib_iser rdma_cm iw_cm ib_cm 
ib_sa ib_mad ib_core ib_addr sunrpc iscsi_tcp libiscsi_tcp libiscsi 
scsi_transport_iscsi autofs4 btrfs raid10 raid456 async_raid6_recov 
async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 
multipath linear cirrus ttm drm_kms_helper syscopyarea sysfillrect sysimgblt 
psmouse fb_sys_fops floppy drm pata_acpi
  Apr 11 21:59:36 stock2 kernel: [ 1649.002015] CPU: 2 PID: 9449 Comm: 
mount.nfs Tainted: P   O4.4.0-18-generic #34+tych0201604111025
  Apr 11 21:59:36 stock2 kernel: [ 1649.003037] Hardware name: QEMU Standard PC 
(i440FX + PIIX, 1996), BIOS Ubuntu-1.8.2-1ubuntu1 04/01/2014
  Apr 11 21:59:36 stock2 kernel: [ 1649.004042] task: 880074c1a580 ti: 
880067d3 task.ti: 880067d3
  Apr 11 21:59:36 stock2 kernel: [ 1649.004810] RIP: 0010:[]  
[] propagate_one+0xbe/0x1c0
  Apr 11 21:59:36 stock2 kernel: [ 1649.005654] RSP: 0018:880067d33d68  
EFLAGS: 00010297
  Apr 11 21:59:36 stock2 kernel: [ 1649.006211] RAX: 88003bb4ca80 RBX: 
880074ad8300 RCX: 880074503500
  Apr 11 21:59:36 stock2 kernel: [ 1649.006934] RDX:  RSI: 
019c RDI: 
  Apr 11 21:59:36 stock2 kernel: [ 1649.007656] RBP: 880067d33d78 R08: 
8800363bad80 R09: 813eac5c
  Apr 11 21:59:36 stock2 kernel: [ 1649.008390] R10: ea2b5800 R11: 
00018711 R12: 8800363ba600
  Apr 11 21:59:36 stock2 kernel: [ 1649.009111] R13: 880067d33dc0 R14: 
880074ad8300 R15: 
  Apr 11 21:59:36 stock2 kernel: [ 1649.009835] FS:  7f653eac4880() 
GS:88007cd0() knlGS:
  Apr 11 21:59:36 stock2 kernel: [ 1649.010642] CS:  0010 DS:  ES:  
CR0: 8005003b
  Apr 11 21:59:36 stock2 kernel: [ 1649.011237] CR2: 0010 CR3: 
77a4e000 CR4: 06e0
  Apr 11 21:59:36 stock2 kernel: [ 1649.011984] Stack:
  Apr 11 21:59:36 stock2 kernel: [ 1649.012255]  880074ad8300 
8800363ba600 880067d33db0 8123d060
  Apr 11 21:59:36 stock2 kernel: [ 1649.013070]  88003bb4ca80 
8800363ba600 88000c211980 
  Apr 11 21:59:36 stock2 kernel: [ 1649.013892]  880067d33e98 
880067d33df8 8122dd97 88003bb4c900
  Apr 11 21:59:36 stock2 kernel: [ 1649.014751] Call Trace:
  Apr 11 21:59:36 stock2 kernel: [ 1649.015053]  [] 
propagate_mnt+0x120/0x150
  Apr 11 21:59:36 stock2 kernel: [ 1649.015643]  [] 
attach_recursive_mnt+0x147/0x230
  Apr 11 21:59:36 stock2 kernel: [ 1649.016286]  [] 
graft_tree+0x58/0x90
  Apr 11 21:59:36 stock2 kernel: [ 1649.016809]  [] 
do_add_mount+0x8e/0xd0
  Apr 11 21:59:36 stock2 kernel: [ 1649.017342]  [] 
do_mount+0x2c0/0xe00
  Apr 11 21:59:36 stock2 kernel: [ 1649.017863]  [] ? 
copy_mount_options+0xb4/0x220
  Apr 11 21:59:36 stock2 kernel: [ 1649.018466]  [] 
SyS_mount+0x9f/0x100
  Apr 11 21:59:36 stock2 kernel: [ 1649.018996]  [] 
entry_SYSCALL_64_fastpath+0x16/0x71
  Apr 11 21:59:36 stock2 kernel: [ 1649.019631] Code: 39 90 d8 00 00 00 75 ec 
8b b0 10 01 00 00 48 89 3d 80 e1 f8 00 48 89 05 81 e1 f8 00 39 b1 10 01 00 00 
74 19 48 8b bf d8 00 00 00 <48> 8b 47 10 48 89 3d 5f e1 f8 00 48 89 05 60 e1 f8 
00 8b 43 30 
  Apr 11 21:59:36 stock2 kernel: [ 1649.022395] RIP  [] 
propagate_one+0xbe/0x1c0
  Apr 11 21:59:36 stock2 kernel: [ 1649.022990]  RSP 
  Apr 11 21:59:36 stock2 kernel: [ 1649.023362] CR2: 0010

[Kernel-packages] [Bug 1539158] Re: Unable to pair with in-car hands-free system after OTA-9 update

2016-05-04 Thread Konrad Zapałowicz

It seems that I know what is happening and why the pairing is denied. I
think that it is because the device when added to the internal data
structures is not yet fully initialized as the properties are gathered
asynchronously. In the same time the pin request is executed  that tries
to use the yet not valid device. As a consequence the pairing is denied
as the whole procedure is interrupted.

Now, just to confirm what is happening on the Ubuntu System Settings
side I would like to look at the Ubuntu System Settings log. You can
find somewhere in .cache/upstart/application [now I'm not sure] legacy
/ubuntu-system-settings.log It would be awesome if you could search for
it and paste here. Thanks in advance.

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

Title:
  Unable to pair with in-car hands-free system after OTA-9 update

Status in Canonical System Image:
  Confirmed
Status in bluez package in Ubuntu:
  Confirmed
Status in ubuntu-system-settings package in Ubuntu:
  Confirmed

Bug description:
  After OTA-9 I started having trouble with my bluetooth connection to the car 
hands-free system (no sound, and incoming calls no longer displayed the 
number), so I have reset both the car and the phone connections (eg. forgot the 
devices).
  Now I can't even pair the phone with the car's system. 
  The car finds the phone, and then asks me to enter the code "" to pair 
the device, but after a few moments, it just says the connection failed and 
asks me to try again. Which fails again.

  It was working fine just before the update.

  Any logs I should post to help debug?

  PS - The car is a 2015 Honda Civic Tourer, if that matters.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1539158/+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 1577057] Re: zfs initrd script fails when rootdelay boot option is set

2016-05-04 Thread Sam VdE

Here are the test results:

- no datasets mounted when it breaks
- A delay of 1 second is not enough: breaks on first try
- Retested with 5 seconds delay: ok

- Retested with new zfs script: notok, again the pool is busy error.

I had a quick look at the script and I found the remaining problem: the
command ZFS_STDERR=$(zpool export "$ZFS_RPOOL" >/dev/null) will not
capture stderr messages. I adapted this to ZFS_STDERR=$(zpool export
"$ZFS_RPOOL" 2>&1  >/dev/null) and was able to boot correctly using
rootdelay=10. So I think that solves it.

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

Title:
  zfs initrd script fails when rootdelay boot option is set

Status in zfs-linux package in Ubuntu:
  Confirmed

Bug description:
  It looks like that, when booting off zfs (zfs holds /boot) with the
  rootdelay boot option set, the boot process fails in the initrd fase,
  asking to manually import the pool using zpool import -f -R / -N. I
  only had one system with that parameter set, which I seldom reboot.

  I did not find an upstream reference of this bug or behavior.

  The error is caused by the fact the pool is already imported: "zpool
  status" executed on the initramfs prompt will correctly list the pool
  and all devices online. To continue, one has to export the pool, re-
  import it and exit the initramfs prompt after which regular booting
  continues. Not exporting and reimporting it leaves the pool readonly
  leading to boot errors further down the road (systemd units failing).

  I noticed zfs_autoimport_disable is set to 1 in the initramfs
  environment, so looking at /usr/share/initramfs-tools/scripts/zfs this
  section might be the issue (zpool import succeeding, but $ZFS_HEALTH
  never returning with the correct status (I'm not a programmer but
  perhaps ZFS_HEALTH is a local variable in the zfs_test_import
  function)):

   delay=${ROOTDELAY:-0}

   if [ "$delay" -gt 0 ]
   then
    # Try to import the pool read-only.  If it does not import with
    # the ONLINE status, wait and try again.  The pool could be
    # DEGRADED because a drive is really missing, or it might just
    # be slow to be detected.
    zfs_test_import
    retry_nr=0
    while [ "$retry_nr" -lt "$delay" ] && [ "$ZFS_HEALTH" != "ONLINE" ]
    do
     [ "$quiet" != "y" ] && log_begin_msg "Retrying ZFS read-only import"
     /bin/sleep 1
     zfs_test_import
     retry_nr=$(( $retry_nr + 1 ))
     [ "$quiet" != "y" ] && log_end_msg
    done
    unset retry_nr
    unset ZFS_HEALTH
   fi
   unset delay

  
  Edit: to be clear: I removed the rootdelay parameter, regenerated the initrd, 
and was able to boot successfully afterwards.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1577057/+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 1573648] Re: 16.04 -> AMD APU via VGA gives blank screen

2016-05-04 Thread R. Becke

I've the same issue on my "HP EliteBook 840 G1" when I dock my laptop to
my "HP 2013 UltraSlim-Dockingstation" I get the following error in
"/var/log/syslog":

...
May  4 19:20:18 hp-elitebook-840-g1--s0-v2 kernel: [   64.811603] 
[drm:radeon_dp_link_train [radeon]] *ERROR* clock recovery reached max voltage
May  4 19:20:18 hp-elitebook-840-g1--s0-v2 kernel: [   64.811619] 
[drm:radeon_dp_link_train [radeon]] *ERROR* clock recovery failed
May  4 19:20:18 hp-elitebook-840-g1--s0-v2 kernel: [   65.062599] 
[drm:radeon_dp_link_train [radeon]] *ERROR* clock recovery reached max voltage
May  4 19:20:18 hp-elitebook-840-g1--s0-v2 kernel: [   65.062614] 
[drm:radeon_dp_link_train [radeon]] *ERROR* clock recovery failed
...

I think this bug is related to: 
https://bugs.freedesktop.org/show_bug.cgi?id=76490
And I think the kernel fix is available: 
http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=0e5585dc870af947fab2af96a88c2d8b4270247c

The question is when will this kernel be available in 16.04?

** Bug watch added: freedesktop.org Bugzilla #76490
   https://bugs.freedesktop.org/show_bug.cgi?id=76490

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

Title:
  16.04 -> AMD APU via VGA gives blank screen

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After upgrade to 16.04, the system will only show a blank screen when a 
monitor is connected to the VGA output.
  The system itself is able to completely start-up (checked via a ssh login).

  Starting up using an older kernel (in this case 4.2.0) gives a
  functional graphical system.

  Possibly related dmesg lines (when booting 4.4.0):
kernel: [9.131059] [drm:radeon_dp_link_train [radeon]] *ERROR* clock 
recovery reached max voltage
kernel: [9.131088] [drm:radeon_dp_link_train [radeon]] *ERROR* clock 
recovery failed

  It might be related to the following kernel post (but i am not entirely sure):
https://lists.freedesktop.org/archives/dri-devel/2016-March/10.html

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-21-generic 4.4.0-21.37
  ProcVersionSignature: Ubuntu 4.2.0-35.40-generic 4.2.8-ckt5
  Uname: Linux 4.2.0-35-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  rene   2014 F pulseaudio
   /dev/snd/controlC0:  rene   2014 F pulseaudio
  CurrentDesktop: Unity
  Date: Fri Apr 22 16:29:44 2016
  HibernationDevice: RESUME=UUID=98dbb6ee-ff08-4e9f-b01d-55b2f28c6a1e
  InstallationDate: Installed on 2015-12-29 (114 days ago)
  InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  IwConfig:
   lono wireless extensions.
   
   enp1s0no wireless extensions.
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-35-generic.efi.signed 
root=/dev/mapper/VGelmo-LVroot ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.2.0-35-generic N/A
   linux-backports-modules-4.2.0-35-generic  N/A
   linux-firmware1.157
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: Upgraded to xenial on 2016-04-21 (0 days ago)
  dmi.bios.date: 12/04/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.90
  dmi.board.name: FM2A68M-HD+
  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.90:bd12/04/2015:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnFM2A68M-HD+: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.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1573648/+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 1328965] Re: 3.13.0-29 kernel includes backport of 3.14 16-bit app restrictions but not override method causing wine win9x to fail

The "/proc/sys/abi/ldt16" workaround was removed from the mainline Linux
kernel two years ago* so the method described in comment #17 is only
valid for older kernels.  "/proc/sys/abi/ldt16" will not be present in
recent or any future kernel versions.

For Ubuntu 15.10 or 16.04, the underlying problem with 16-bit apps
should have been resolved by other patches that came in the same
timeframe.  If that functionality itself isn't working, please file a
new bug report.

* 7ed6fb9 Revert "x86-64, modify_ldt: Make support for 16-bit segments a
runtime option"

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

Title:
  3.13.0-29 kernel includes backport of 3.14 16-bit app restrictions but
  not override method causing wine win9x to fail

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Precise:
  Fix Released
Status in linux source package in Trusty:
  Fix Released
Status in linux source package in Utopic:
  Fix Released

Bug description:
  Kernel 3.13.0-29 evidently contains a backport of the 3.14 kernel
  security workaround that disables 16-bit binaries from running.  This
  causes all wine Windows 95 and Windows 98 applications to fail.  The
  3.14 kernel also includes a feature to re-enable support for 16-bit
  binaries by providing the /proc/sys/abi/ldt16 interface.  This part of
  the kernel patch was evidently not backported, so this ability to
  override the 16-bit application prohibition is not available.

  For this reason, I cannot move forward to new kernel releases until
  this is fixed.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-29-generic 3.13.0-29.53
  ProcVersionSignature: Ubuntu 3.13.0-27.50-generic 3.13.11
  Uname: Linux 3.13.0-27-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  soup   1783 F pulseaudio
  CurrentDesktop: Unity
  Date: Wed Jun 11 12:01:26 2014
  HibernationDevice: RESUME=UUID=8dcf6a87-59e8-4af8-9e1f-cbbcc64ca7a4
  InstallationDate: Installed on 2014-04-26 (46 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  MachineType: Hewlett-Packard HP ProBook 4530s
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-27-generic 
root=UUID=b0984c90-6bc2-4dfb-978b-a508cbaff6a9 ro
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-27-generic N/A
   linux-backports-modules-3.13.0-27-generic  N/A
   linux-firmware 1.127.2
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/11/2011
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 68SRR Ver. F.20
  dmi.board.name: 167C
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 22.21
  dmi.chassis.asset.tag: CNU1412MC3
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68SRRVer.F.20:bd10/11/2011:svnHewlett-Packard:pnHPProBook4530s:pvrA0001D02:rvnHewlett-Packard:rn167C:rvrKBCVersion22.21:cvnHewlett-Packard:ct10:cvr:
  dmi.product.name: HP ProBook 4530s
  dmi.product.version: A0001D02
  dmi.sys.vendor: Hewlett-Packard

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1328965/+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 1578141] Re: Predictable interface names partially broken with igb driver

Did this issue start happening after an update/upgrade?  Was there a
prior kernel version where you were not having this particular problem?

Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.6 kernel[0].

If this bug is fixed in the mainline kernel, please add the following
tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag:
'kernel-bug-exists-upstream'.

Once testing of the upstream kernel is complete, please mark this bug as
"Confirmed".


Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.6-rc6-wily/


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

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

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

Title:
  Predictable interface names partially broken with igb driver

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Note: I'm not sure whether this is really a kernel bug or something
  within systemd/udev, please advise how to further debug.

  On a system with two GE ports, instead of getting named eno1 and eno2,
  I am getting eno1 and renameN. Where N starts at 3 and increases by 2
  on every iteration of doing "rmmod igb;modprobe igb". The
  corresponding lines in dmesg look like this:

  [2.748429] igb :07:00.0: added PHC on eth0
  [2.748431] igb :07:00.0: Intel(R) Gigabit Ethernet Network Connection
  [2.748433] igb :07:00.0: eth0: (PCIe:5.0Gb/s:Width x4) 
00:25:90:d7:60:8e
  [2.748505] igb :07:00.0: eth0: PBA No: 106100-000
  [2.748506] igb :07:00.0: Using MSI-X interrupts. 8 rx queue(s), 8 tx 
queue(s)
  [2.802555] igb :07:00.1: added PHC on eth1
  [2.802557] igb :07:00.1: Intel(R) Gigabit Ethernet Network Connection
  [2.802559] igb :07:00.1: eth1: (PCIe:5.0Gb/s:Width x4) 
00:25:90:d7:60:8f
  [2.802631] igb :07:00.1: eth1: PBA No: 106100-000
  [2.802632] igb :07:00.1: Using MSI-X interrupts. 8 rx queue(s), 8 tx 
queue(s)
  [2.803618] igb :07:00.0 eno1: renamed from eth0
  [2.833208] igb :07:00.1 rename3: renamed from eth1

  What is even worse: Sometimes the naming changes and the second
  interface ends up as eno1 while the first interface is named renameN
  with an even N. The bad thing about this version is that when it
  happens while the installer is running, the installer will setup
  "rename2" as the primary network interface, which works fine for the
  installation itself, but after installation is finished and the first
  boot of the installed system happens, that interface will be gone,
  leaving the system without network connectivity.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-21-generic 4.4.0-21.37
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 May  4 09:48 seq
   crw-rw 1 root audio 116, 33 May  4 09:48 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  Date: Wed May  4 10:00:39 2016
  HibernationDevice: RESUME=/dev/mapper/compute--node37--vg-swap
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb:
   Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
   Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 001 Device 003: ID 0557:2221 ATEN International Co., Ltd Winbond Hermon
   Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Supermicro X9DRT-HF+
  PciMultimedia:
   
  ProcEnviron:
   LANGUAGE=en_US:
   TERM=screen
   PATH=(custom, no user)
   LANG=en_US
   SHELL=/bin/bash
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-21-generic 
root=/dev/mapper/compute--node37--vg-root ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-21-generic N/A
   linux-backports-modules-4.4.0-21-generic  N/A
   linux-firmware1.157
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/21/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3.0c
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: X9DRT-HF+
  dmi.board.vendor: Supermicro
  dmi.board.version: 0123456789
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.typ

[Kernel-packages] [Bug 1539158] Re: Unable to pair with in-car hands-free system after OTA-9 update

2016-05-04 Thread Konrad Zapałowicz

** Branch linked: lp:~kzapalowicz/ubuntu-system-settings/fix-1539158

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

Title:
  Unable to pair with in-car hands-free system after OTA-9 update

Status in Canonical System Image:
  Confirmed
Status in bluez package in Ubuntu:
  Confirmed
Status in ubuntu-system-settings package in Ubuntu:
  Confirmed

Bug description:
  After OTA-9 I started having trouble with my bluetooth connection to the car 
hands-free system (no sound, and incoming calls no longer displayed the 
number), so I have reset both the car and the phone connections (eg. forgot the 
devices).
  Now I can't even pair the phone with the car's system. 
  The car finds the phone, and then asks me to enter the code "" to pair 
the device, but after a few moments, it just says the connection failed and 
asks me to try again. Which fails again.

  It was working fine just before the update.

  Any logs I should post to help debug?

  PS - The car is a 2015 Honda Civic Tourer, if that matters.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1539158/+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 1493386] Re: IN CAR: SIM2 calls cann not be routed via car audio

2016-05-04 Thread Uranicus

Are there any news on this bug? How about the implementation progress on
supporting 2 SIM cards used with bluetooth?

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

Title:
  IN CAR: SIM2 calls cann not be routed via car audio

Status in bluez package in Ubuntu:
  Invalid
Status in ofono package in Ubuntu:
  In Progress

Bug description:
  STEPS:
  Requirements: Aquaris E4.5 with 2 SIMs, 2nd phone, a car with blue tooth 
phone support (Seat Alhambra 2012 in my case)

  1. Connect the Aquaris to the car (with two SIM cards, car kid shows the 
provider of the 2nd SIM card in the display)
  2. From the second device call the number of SIM1
  3. Phone & car sound rings and call can be taken

  4. From the second device call the number of SIM2
  5. Phone does ring but car kit not.

  6. Call 2nd phone from Aquaris connected to the car with SIM1 (via the phone 
directly or using the car kit)
  7. Normal behaviour with in car phone & audio system

  8. Call 2nd phone from Aquaris connected to car with SIM2 (only possible 
dialling from the phone)
  9. No sound on the phone, no microphone support

  EXPECTED:
  I expect that calls from SIM2 can be taken and performed as from SIM1

  ACTUAL:
  SIM2 seems not to work when phone is connected to blue tooth of car whereby 
SIM1 works flawlessly

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1493386/+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 1552504] Re: clicking noise on acer 131t-c1yf

kernel-bug-exists-upstream-4.6-rc6
I Installed 4.6-rc6 today and the bug still exists

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

Title:
  clicking noise on acer 131t-c1yf

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  My machine is solid state.
  I updated the intel graphics driver
  I update a few days ago via ubuntu udpater

  There is a subtle clicking noise coming near from the usb port.  The machine 
is solid state and the ubuntu is running from the sd card  The noise happnes 
with usb live boot too.
  The mint 17 usb makes the noise too and then warns me that that the graphics 
gpu will not be used and then the clicking stops.
   
  Lubuntu installed on top of ubuntu still makes the noise.
  Lubuntu live usb does NOT make the noise.
  Windows 10 does not make the noise.

  I suspect compiz, but ultimately I think it is a kernal problem.
  I suspect this is a CherryView Bug.

  
  This bug has been reported on ubuntu forums and ask ubuntu and no responses.
  I will be switching to Lubuntu in a few days unless I hear back from you.  I 
am technical and willing to help.

  
  Bhikkhu Subhuti

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: linux-image-4.2.0-27-generic 4.2.0-27.32
  ProcVersionSignature: Ubuntu 4.2.0-27.32-generic 4.2.8-ckt1
  Uname: Linux 4.2.0-27-generic x86_64
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  bksubhuti   1067 F pulseaudio
  CurrentDesktop: Unity
  Date: Fri Mar  4 08:28:59 2016
  HibernationDevice: RESUME=UUID=709ea197-e6fb-428b-9c1f-4b258452b10c
  InstallationDate: Installed on 2016-02-04 (29 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  MachineType: Acer Aspire R3-131T
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-27-generic.efi.signed 
root=UUID=ec51921a-2804-40c5-96f4-9597628656cb ro noprompt persistent quiet 
splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.2.0-27-generic N/A
   linux-backports-modules-4.2.0-27-generic  N/A
   linux-firmware1.149.3
  SourcePackage: linux
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/21/2015
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.09
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Aspire R3-131T
  dmi.board.vendor: Acer
  dmi.board.version: V1.09
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V1.09
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.09:bd07/21/2015:svnAcer:pnAspireR3-131T:pvrV1.09:rvnAcer:rnAspireR3-131T:rvrV1.09:cvnAcer:ct10:cvrV1.09:
  dmi.product.name: Aspire R3-131T
  dmi.product.version: V1.09
  dmi.sys.vendor: Acer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1552504/+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 1552504] Re: clicking noise on acer 131t-c1yf

** Tags added: kernel-bug-exists-upstream-4.6.rc6

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

Title:
  clicking noise on acer 131t-c1yf

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  My machine is solid state.
  I updated the intel graphics driver
  I update a few days ago via ubuntu udpater

  There is a subtle clicking noise coming near from the usb port.  The machine 
is solid state and the ubuntu is running from the sd card  The noise happnes 
with usb live boot too.
  The mint 17 usb makes the noise too and then warns me that that the graphics 
gpu will not be used and then the clicking stops.
   
  Lubuntu installed on top of ubuntu still makes the noise.
  Lubuntu live usb does NOT make the noise.
  Windows 10 does not make the noise.

  I suspect compiz, but ultimately I think it is a kernal problem.
  I suspect this is a CherryView Bug.

  
  This bug has been reported on ubuntu forums and ask ubuntu and no responses.
  I will be switching to Lubuntu in a few days unless I hear back from you.  I 
am technical and willing to help.

  
  Bhikkhu Subhuti

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: linux-image-4.2.0-27-generic 4.2.0-27.32
  ProcVersionSignature: Ubuntu 4.2.0-27.32-generic 4.2.8-ckt1
  Uname: Linux 4.2.0-27-generic x86_64
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  bksubhuti   1067 F pulseaudio
  CurrentDesktop: Unity
  Date: Fri Mar  4 08:28:59 2016
  HibernationDevice: RESUME=UUID=709ea197-e6fb-428b-9c1f-4b258452b10c
  InstallationDate: Installed on 2016-02-04 (29 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  MachineType: Acer Aspire R3-131T
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-27-generic.efi.signed 
root=UUID=ec51921a-2804-40c5-96f4-9597628656cb ro noprompt persistent quiet 
splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.2.0-27-generic N/A
   linux-backports-modules-4.2.0-27-generic  N/A
   linux-firmware1.149.3
  SourcePackage: linux
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/21/2015
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.09
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Aspire R3-131T
  dmi.board.vendor: Acer
  dmi.board.version: V1.09
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V1.09
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.09:bd07/21/2015:svnAcer:pnAspireR3-131T:pvrV1.09:rvnAcer:rnAspireR3-131T:rvrV1.09:cvnAcer:ct10:cvrV1.09:
  dmi.product.name: Aspire R3-131T
  dmi.product.version: V1.09
  dmi.sys.vendor: Acer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1552504/+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 1552504] Re: clicking noise on acer 131t-c1yf

** Tags removed: kernel-bug-exists-upstream-4.6.rc6
** Tags added: kernel-bug-exists-upstream-4.6-rc6 vivid

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

Title:
  clicking noise on acer 131t-c1yf

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  My machine is solid state.
  I updated the intel graphics driver
  I update a few days ago via ubuntu udpater

  There is a subtle clicking noise coming near from the usb port.  The machine 
is solid state and the ubuntu is running from the sd card  The noise happnes 
with usb live boot too.
  The mint 17 usb makes the noise too and then warns me that that the graphics 
gpu will not be used and then the clicking stops.
   
  Lubuntu installed on top of ubuntu still makes the noise.
  Lubuntu live usb does NOT make the noise.
  Windows 10 does not make the noise.

  I suspect compiz, but ultimately I think it is a kernal problem.
  I suspect this is a CherryView Bug.

  
  This bug has been reported on ubuntu forums and ask ubuntu and no responses.
  I will be switching to Lubuntu in a few days unless I hear back from you.  I 
am technical and willing to help.

  
  Bhikkhu Subhuti

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: linux-image-4.2.0-27-generic 4.2.0-27.32
  ProcVersionSignature: Ubuntu 4.2.0-27.32-generic 4.2.8-ckt1
  Uname: Linux 4.2.0-27-generic x86_64
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  bksubhuti   1067 F pulseaudio
  CurrentDesktop: Unity
  Date: Fri Mar  4 08:28:59 2016
  HibernationDevice: RESUME=UUID=709ea197-e6fb-428b-9c1f-4b258452b10c
  InstallationDate: Installed on 2016-02-04 (29 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  MachineType: Acer Aspire R3-131T
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-27-generic.efi.signed 
root=UUID=ec51921a-2804-40c5-96f4-9597628656cb ro noprompt persistent quiet 
splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.2.0-27-generic N/A
   linux-backports-modules-4.2.0-27-generic  N/A
   linux-firmware1.149.3
  SourcePackage: linux
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/21/2015
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.09
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Aspire R3-131T
  dmi.board.vendor: Acer
  dmi.board.version: V1.09
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V1.09
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.09:bd07/21/2015:svnAcer:pnAspireR3-131T:pvrV1.09:rvnAcer:rnAspireR3-131T:rvrV1.09:cvnAcer:ct10:cvrV1.09:
  dmi.product.name: Aspire R3-131T
  dmi.product.version: V1.09
  dmi.sys.vendor: Acer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1552504/+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 1552504] Re: clicking noise on acer 131t-c1yf