[Kernel-packages] [Bug 1510344] Re: Keyboard Backlight Turns on at boot

2015-11-03 Thread Matthias König
Addendum: I noticed the backlight also gets switched back on after not
using the keyboard and touchpad for a few seconds. I suspect this has
something to do with the way it acts when it is switched on normally:
After not typing anything or using the touchpad for a few seconds, the
backlight is switched off to save power and gets switched back on when
you touch the keyboard.

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

Title:
  Keyboard Backlight Turns on at boot

Status in Dell Sputnik:
  Confirmed
Status in One Hundred Papercuts:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  System: Dell XPS 13 9343

  Action: Boot computer

  Expected Behavior: Keyboard backlight would be off when computer is
  booted

  Actual Behavior: Keyboard backlight is on at boot

  This did not happen with Ubuntu 15.04

  There are new files in Ubuntu 15.10 -
  /sys/class/leds/dell::kbd_backlight$

  cat stop_timeout
  60s

   cat start_triggers 
  +keyboard +touchpad

  cat trigger 
  [none] AC-online BAT0-charging-or-full BAT0-charging BAT0-full 
BAT0-charging-blink-full-solid usb-gadget usb-host cpu0 cpu1 cpu2 cpu3 mmc0 
rfkill0

  cat brightness 
  2

  ---

  Unsure if these files are important, but included in the report

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: linux-image-4.1.0-2-generic 4.1.0-2.2
  ProcVersionSignature: Ubuntu 4.1.0-2.2-generic 4.1.3
  Uname: Linux 4.1.0-2-generic x86_64
  ApportVersion: 2.18-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  ubuntu 2488 F pulseaudio
   /dev/snd/controlC0:  ubuntu 2488 F pulseaudio
  CasperVersion: 1.362
  CurrentDesktop: Unity
  Date: Tue Oct 27 01:29:47 2015
  IwConfig:
   enx00249b0981e3  no wireless extensions.
   
   lono wireless extensions.
  LiveMediaBuild: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150730)
  MachineType: Dell Inc. XPS 13 9343
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi 
file=/cdrom/preseed/username.seed boot=casper quiet splash --- 
cdrom-detect/try-usb=true noprompt
  RelatedPackageVersions:
   linux-restricted-modules-4.1.0-2-generic N/A
   linux-backports-modules-4.1.0-2-generic  N/A
   linux-firmware   1.145
  RfKill:
   0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  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/14/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A05
  dmi.board.name: 0TM99H
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA05:bd07/14/2015:svnDellInc.:pnXPS139343:pvr:rvnDellInc.:rn0TM99H:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 13 9343
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/dell-sputnik/+bug/1510344/+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 1512603] [NEW] nut-monitor systemd service is absent in nut-client package since Ubuntu vivid

2015-11-03 Thread Andrew
Public bug reported:

The systemd unit for the upsmon has disapperared from nut-client package
since Ubuntu trusty:

http://packages.ubuntu.com/trusty/amd64/nut-client/filelist
(2.7.1-1ubuntu1)

vs

http://packages.ubuntu.com/vivid/amd64/nut-client/filelist
(2.7.1-1ubuntu4)

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

** Package changed: kexec-tools (Ubuntu) => nut (Ubuntu)

** Description changed:

- The systemd service for the upsmon has disapperared from nut-client
- package since Ubuntu trusty:
+ The systemd unit for the upsmon has disapperared from nut-client package
+ since Ubuntu trusty:
  
  http://packages.ubuntu.com/trusty/amd64/nut-client/filelist
  (2.7.1-1ubuntu1)
  
  vs
  
  http://packages.ubuntu.com/vivid/amd64/nut-client/filelist
  (2.7.1-1ubuntu4)

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

Title:
  nut-monitor systemd service is absent in nut-client package since
  Ubuntu vivid

Status in nut package in Ubuntu:
  New

Bug description:
  The systemd unit for the upsmon has disapperared from nut-client
  package since Ubuntu trusty:

  http://packages.ubuntu.com/trusty/amd64/nut-client/filelist
  (2.7.1-1ubuntu1)

  vs

  http://packages.ubuntu.com/vivid/amd64/nut-client/filelist
  (2.7.1-1ubuntu4)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nut/+bug/1512603/+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 1488719] Re: dmesg shows "[drm:gen8_irq_handler [i915]] *ERROR* The master control interrupt lied (SDE)!"

2015-11-03 Thread Puggan
Got this error in my dmesg, and gets daily KDM crashes.

Have an Asus X555L with 2 external monitors connected,
each morning when i get back to the computer, the laptop screen dosn't start,
and I have no working window managment => I can use the active window, but 
can't change active window.

Also, if i activate the wireless-card, I can see the si (software interupt) in 
top raise to 100%, and then I lose all controll.
And all I found so far is this error message 1836 times in the dmesg-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/1488719

Title:
  dmesg shows "[drm:gen8_irq_handler [i915]] *ERROR* The master control
  interrupt lied (SDE)!"

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

Bug description:
  On a recent intel NUC using i915 graphics, I get the following errors
  in dmesg:

  [drm:gen8_irq_handler [i915]] *ERROR* The master control interrupt
  lied (SDE)!

  There are two monitors connected to this box, one with mini-
  HDMI->HDMI, one with mini-DP->HDMI cable.

  Maybe related:

  https://bugs.freedesktop.org/show_bug.cgi?id=80896

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: linux-image-generic 3.19.0.26.25
  ProcVersionSignature: Ubuntu 3.19.0-26.28-generic 3.19.8-ckt4
  Uname: Linux 3.19.0-26-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1.3
  Architecture: amd64
  Date: Wed Aug 26 10:07:31 2015
  InstallationDate: Installed on 2015-08-01 (24 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-26-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root 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)

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1488719/+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 1115555] Re: Backlight control does not work, but there are entries in /sys/class/backlight.

2015-11-03 Thread Gaele Strootman
** 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/111

Title:
  Backlight control does not work, but there are entries in
  /sys/class/backlight.

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

Bug description:
  Backlight control does not work, but there are entries in
  /sys/class/backlight.

  This may require the ACPI backlight driver to not take control so that
  a vendor specific driver will have a chance to register.

  I wanto mention that this goes beyond just the applet not working.  My
  data does change in Ubuntu for those entries and the acpi interface to
  the Linux Kernel is not able to use that changed data to change the
  hardware brightness setting.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: linux-image-3.2.0-37-generic 3.2.0-37.58
  ProcVersionSignature: Ubuntu 3.2.0-37.58-generic 3.2.35
  Uname: Linux 3.2.0-37-generic x86_64
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
  ApportVersion: 2.0.1-0ubuntu17.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  carkaci1936 F pulseaudio
   /dev/snd/controlC0:  carkaci1936 F pulseaudio
  CRDA:
   country AW:
(2402 - 2482 @ 40), (N/A, 20)
(5170 - 5250 @ 40), (N/A, 20)
(5250 - 5330 @ 40), (N/A, 20), DFS
(5490 - 5710 @ 40), (N/A, 27), DFS
  Card0.Amixer.info:
   Card hw:0 'Intel'/'HDA Intel at 0xd050 irq 48'
 Mixer name : 'Cirrus Logic CS4206'
 Components : 'HDA:10134206,106b1800,00100301'
 Controls  : 25
 Simple ctrls  : 11
  Card1.Amixer.info:
   Card hw:1 'Generic'/'HD-Audio Generic at 0xd044 irq 49'
 Mixer name : 'ATI R6xx HDMI'
 Components : 'HDA:1002aa01,00aa0100,00100200'
 Controls  : 6
 Simple ctrls  : 1
  Card1.Amixer.values:
   Simple mixer control 'IEC958',0
 Capabilities: pswitch pswitch-joined penum
 Playback channels: Mono
 Mono: Playback [on]
  Date: Mon Feb  4 21:53:10 2013
  HibernationDevice: RESUME=UUID=2850be5d-9902-4a6d-8e97-3f9d34028e02
  InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 
(20120823.1)
  MachineType: Apple Inc. iMac11,3
  MarkForUpload: True
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-37-generic 
root=UUID=83592388-7d5b-432f-94fe-74542604df39 ro acpi_osi=Linux quiet splash 
vt.handoff=7
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory 
/home/carkaci not ours.
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-3.2.0-37-generic N/A
   linux-backports-modules-3.2.0-37-generic  N/A
   linux-firmware1.79.1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/03/10
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: IM112.88Z.0057.B00.1005031455
  dmi.board.name: Mac-F2238BAE
  dmi.board.vendor: Apple Inc.
  dmi.board.version: iMac11,3
  dmi.chassis.type: 13
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-F2238BAE
  dmi.modalias: 
dmi:bvnAppleInc.:bvrIM112.88Z.0057.B00.1005031455:bd05/03/10:svnAppleInc.:pniMac11,3:pvr1.0:rvnAppleInc.:rnMac-F2238BAE:rvriMac11,3:cvnAppleInc.:ct13:cvrMac-F2238BAE:
  dmi.product.name: iMac11,3
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/111/+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 1512415] Re: hpsa driver has problems with interacting with tape drives and media changer

2015-11-03 Thread Karsten Elfenbein
Hi Joseph,

the tape drives and autochanger now work as expected with the provided
kernel.

Thanks
Karsten

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

Title:
  hpsa driver has problems with interacting with tape drives and media
  changer

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

Bug description:
  There are multiple problems with tape drives when using a media changer on an 
hpsa controller.
  The problem appears for example when you label tapes in Dell Netvault.

  The problem does not appear in current vanilla kernel 4.2.3.

  After bisecting the problem the actually first good commit is: 
  3ce438df106826edde7ad724f3819716a3f0cf56 is the first bad commit
  commit 3ce438df106826edde7ad724f3819716a3f0cf56
  Author: Matt Gates 
  Date:   Wed Dec 4 17:10:36 2013 -0600

  [SCSI] hpsa: allow SCSI mid layer to handle unit attention

  We were clobbering the SCSI status and setting
  cmd->result = DID_SOFT_ERROR << 16; to get a retry,
  but better to let the mid layer handle the unit
  attention.

  Signed-off-by: Matt Gates 
  Acked-by: Stephen M. Cameron 
  Signed-off-by: James Bottomley 

  :04 04 a7ea924772d20fd6faa968a855cffdb864876264
  99765902968200eacf3a6ff1267b691a7bb24ebe M  drivers

  thanks to git bisecting rules:
  good = label errors = old kernel
  bad = no label errors = newer kernel

  Please consider backporting that fix to the 3.13 ubuntu kernel.
  --- 
  ApportVersion: 2.0.1-0ubuntu17.13
  Architecture: amd64
  DistroRelease: Ubuntu 12.04
  MarkForUpload: True
  Package: linux (not installed)
  ProcEnviron:
   LANGUAGE=en_US:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  Tags:  precise precise
  Uname: Linux 4.2.3-custom x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
  --- 
  ApportVersion: 2.0.1-0ubuntu17.13
  Architecture: amd64
  DistroRelease: Ubuntu 12.04
  MarkForUpload: True
  Package: linux-image-3.13.0-65-generic 3.13.0-65.106~precise1
  PackageArchitecture: amd64
  ProcEnviron:
   LANGUAGE=en_US:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  Tags:  precise
  Uname: Linux 4.2.3-custom x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

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

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


Re: [Kernel-packages] [Bug 1423672] Re: ext4_mb_generate_buddy:756: group N, block bitmap and bg descriptor inconsistent: X vs Y

2015-11-03 Thread Jan Wagner
Am 29.10.15 um 03:29 schrieb LouieGosselin:
> I'm posting again to add that I conducted some more tests and ext3 does
> not encounter corruption under the same conditions. I hope this
> information is helpful to others, if anyone needs more information let
> me know and I'll see what I can do. I'll probably switch my own VMs to
> ext3 so I don't have to worry about these FS crashes.

I created a new LVM Volume and a new ext3 FS. I copied the whole FS from
ext4 to ext3 and running now the VM on ext3.

Today the ext4_mb_generate_buddy bug did hit me agian. With ext3 FS and
running the VM with "cache=none" setting.

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

Title:
  ext4_mb_generate_buddy:756: group N, block bitmap and bg descriptor
  inconsistent: X vs Y

Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Trusty:
  Confirmed
Status in linux package in Debian:
  New

Bug description:
  I noticed that one of my VM had this "dmesg -T" output:

  [Tue Feb 17 09:53:27 2015] systemd-udevd[5433]: starting version 204
  [Thu Feb 19 06:25:08 2015] EXT4-fs error (device vda1): 
ext4_mb_generate_buddy:756: group 5, block bitmap and bg descriptor 
inconsistent: 16446 vs 16445 free clusters
  [Thu Feb 19 06:25:09 2015] Aborting journal on device vda1-8.
  [Thu Feb 19 06:25:09 2015] EXT4-fs (vda1): Remounting filesystem read-only
  [Thu Feb 19 06:25:09 2015] [ cut here ]
  [Thu Feb 19 06:25:09 2015] WARNING: CPU: 0 PID: 9946 at 
/build/buildd/linux-3.13.0/fs/ext4/ext4_jbd2.c:259 
__ext4_handle_dirty_metadata+0x1a2/0x1c0()
  [Thu Feb 19 06:25:09 2015] Modules linked in: nf_conntrack_ipv6 
nf_defrag_ipv6 ip6table_filter ip6_tables xt_tcpudp nf_conntrack_ipv4 
nf_defrag_ipv4 xt_owner xt_conntrack nf_conntrack iptable_filter ip_tables 
x_tables serio_raw psmouse floppy
  [Thu Feb 19 06:25:09 2015] CPU: 0 PID: 9946 Comm: logrotate Not tainted 
3.13.0-45-generic #74-Ubuntu
  [Thu Feb 19 06:25:09 2015] Hardware name: QEMU Standard PC (i440FX + PIIX, 
1996), BIOS Bochs 01/01/2011
  [Thu Feb 19 06:25:09 2015]  0009 880003a11aa0 
81720eb6 
  [Thu Feb 19 06:25:09 2015]  880003a11ad8 810677cd 
88c41340 
  [Thu Feb 19 06:25:09 2015]  88000a58e000 81835280 
1302 880003a11ae8
  [Thu Feb 19 06:25:09 2015] Call Trace:
  [Thu Feb 19 06:25:09 2015]  [] dump_stack+0x45/0x56
  [Thu Feb 19 06:25:09 2015]  [] 
warn_slowpath_common+0x7d/0xa0
  [Thu Feb 19 06:25:09 2015]  [] warn_slowpath_null+0x1a/0x20
  [Thu Feb 19 06:25:09 2015]  [] 
__ext4_handle_dirty_metadata+0x1a2/0x1c0
  [Thu Feb 19 06:25:09 2015]  [] ? ext4_dirty_inode+0x2a/0x60
  [Thu Feb 19 06:25:09 2015]  [] ext4_free_blocks+0x646/0xbf0
  [Thu Feb 19 06:25:09 2015]  [] ? wake_up_bit+0x25/0x30
  [Thu Feb 19 06:25:09 2015]  [] ext4_ext_rm_leaf+0x505/0x8f0
  [Thu Feb 19 06:25:09 2015]  [] ? 
__ext4_ext_check+0x197/0x370
  [Thu Feb 19 06:25:09 2015]  [] ? 
ext4_ext_remove_space+0xc0/0x7e0
  [Thu Feb 19 06:25:09 2015]  [] 
ext4_ext_remove_space+0x31c/0x7e0
  [Thu Feb 19 06:25:09 2015]  [] ext4_ext_truncate+0xb0/0xe0
  [Thu Feb 19 06:25:09 2015]  [] ext4_truncate+0x379/0x3c0
  [Thu Feb 19 06:25:09 2015]  [] ext4_evict_inode+0x408/0x4d0
  [Thu Feb 19 06:25:09 2015]  [] evict+0xb0/0x1b0
  [Thu Feb 19 06:25:09 2015]  [] iput+0xf5/0x180
  [Thu Feb 19 06:25:09 2015]  [] __dentry_kill+0x1a8/0x200
  [Thu Feb 19 06:25:09 2015]  [] dput+0xa5/0x180
  [Thu Feb 19 06:25:09 2015]  [] __fput+0x176/0x260
  [Thu Feb 19 06:25:09 2015]  [] fput+0xe/0x10
  [Thu Feb 19 06:25:09 2015]  [] task_work_run+0xa7/0xe0
  [Thu Feb 19 06:25:09 2015]  [] do_notify_resume+0x97/0xb0
  [Thu Feb 19 06:25:09 2015]  [] int_signal+0x12/0x17
  [Thu Feb 19 06:25:09 2015] ---[ end trace ebff9843d81b5c41 ]---
  [Thu Feb 19 06:25:09 2015] BUG: unable to handle kernel NULL pointer 
dereference at 0028
  [Thu Feb 19 06:25:09 2015] IP: [] 
__ext4_error_inode+0x31/0x160
  [Thu Feb 19 06:25:09 2015] PGD 167067 PUD 161067 PMD 0 
  [Thu Feb 19 06:25:09 2015] Oops:  [#1] SMP 
  [Thu Feb 19 06:25:09 2015] Modules linked in: nf_conntrack_ipv6 
nf_defrag_ipv6 ip6table_filter ip6_tables xt_tcpudp nf_conntrack_ipv4 
nf_defrag_ipv4 xt_owner xt_conntrack nf_conntrack iptable_filter ip_tables 
x_tables serio_raw psmouse floppy
  [Thu Feb 19 06:25:09 2015] CPU: 0 PID: 9946 Comm: logrotate Tainted: G
W 3.13.0-45-generic #74-Ubuntu
  [Thu Feb 19 06:25:09 2015] Hardware name: QEMU Standard PC (i440FX + PIIX, 
1996), BIOS Bochs 01/01/2011
  [Thu Feb 19 06:25:09 2015] task: 880009ac4800 ti: 880003a1 
task.ti: 880003a1
  [Thu Feb 19 06:25:09 2015] RIP: 0010:[]  
[] __ext4_error_inode+0x31/0x160
  [Thu Feb 19 06:25:09 2015] RSP: :880003a11a58  EFLAGS: 00010292
  [Thu Feb 19 06:25:09 2015] RAX:  RBX: 

[Kernel-packages] [Bug 1173681] Re: 168c:002b [Asus U32U] asus_nb_wmi AR9285 ath9k not working after updating to Ubuntu 13.04 Raring

2015-11-03 Thread Habib
Same here,

Debian Jessie, the product model is Asus N551ZU

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

Title:
  168c:002b [Asus U32U] asus_nb_wmi AR9285 ath9k not working after
  updating to Ubuntu 13.04 Raring

Status in Linux:
  Invalid
Status in Linux Deepin:
  New
Status in linux package in Ubuntu:
  Fix Released

Bug description:
  update: updated the BIOS to the latest version but the problem
  persists.

  Booting with the older kernel (latest linux kernel from 12.10) every thing 
works fine. After upgrading to Raring Ringtail Ubuntu 13.04, with the new 
kernel, hardware get blocked/disabled and wireless doesn't work:
  0: phy0: Wireless LAN
   Soft blocked: no
   Hard blocked: yes
  1: asus-wlan: Wireless LAN
   Soft blocked: no
   Hard blocked: no

  WORKAROUND - is only applicable to Asus Notebooks/netbooks that use the 
"asus_nb_wmi" driver:
  Create and edit asus_nb_wmi.conf file with this command:
  sudo echo "options asus_nb_wmi wapf=4" | sudo tee 
/etc/modprobe.d/asus_nb_wmi.conf

  For more detailed info of the workaround please see:
  http://ubuntuforums.org/showthread.php?t=2181558

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: linux-image-3.8.0-19-generic 3.8.0-19.29
  ProcVersionSignature: Ubuntu 3.8.0-19.29-generic 3.8.8
  Uname: Linux 3.8.0-19-generic x86_64
  ApportVersion: 2.9.2-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  x  1822 F pulseaudio
  CurrentDmesg:
   [  370.100280] r8169 :04:00.2 eth1: link up
   [  370.100322] IPv6: ADDRCONF(NETDEV_CHANGE): eth1: link becomes ready
   [  891.718748] systemd-hostnamed[2649]: Warning: nss-myhostname is not 
installed. Changing the local hostname might make it unresolveable. Please 
install nss-myhostname!
   [14119.241628] rtsx_pci :04:00.0: vpd r/w failed.  This is likely a 
firmware bug on this device.  Contact the card vendor for a firmware update.
  Date: Sat Apr 27 17:31:51 2013
  HibernationDevice: RESUME=UUID=e417e9f2-b63e-4b79-9be4-c21f55547205
  InstallationDate: Installed on 2012-07-13 (287 days ago)
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 
(20120425)
  MachineType: ASUSTeK Computer Inc. U32U
  MarkForUpload: True
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-19-generic 
root=UUID=3ad9d88b-a7a5-460f-ba15-a78dd7f2fc94 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.8.0-19-generic N/A
   linux-backports-modules-3.8.0-19-generic  N/A
   linux-firmware1.106
  SourcePackage: linux
  UpgradeStatus: Upgraded to raring on 2013-04-27 (0 days ago)
  dmi.bios.date: 12/16/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: U32U.204
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: U32U
  dmi.board.vendor: ASUSTeK Computer Inc.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK Computer Inc.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrU32U.204:bd12/16/2011:svnASUSTeKComputerInc.:pnU32U:pvr1.0:rvnASUSTeKComputerInc.:rnU32U:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0:
  dmi.product.name: U32U
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK Computer Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1173681/+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 1491494] Re: Ubuntu 14.04.03 LPAR hits kernel oops after serial adapter is removed from profile

2015-11-03 Thread bugproxy
** Tags removed: targetmilestone-inin14043
** Tags added: targetmilestone-inin14044

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

Title:
  Ubuntu 14.04.03 LPAR hits kernel oops after serial adapter is removed
  from profile

Status in linux package in Ubuntu:
  Triaged

Bug description:
  -- Problem Description --

  The failure related to the BELL-3 (2 port-Async EIA-232 adapter).
  Ubuntu always hit exception when the adapter is not present. See my
  test scenarios below.

  Test #1: Boot Ubuntu with BELL-3 adapter 
  ===

  - The Ubuntu LPAR was running with the BELL-3 (2 port-Async EIA-232 adapter) 
before. So I assigned the BELL-3 adapter to Ubuntu LPAR profile and powered on 
the LPAR. 
  => Ubuntu boot fine this time.

   
  Test #2: Boot Ubuntu with BELL-3 adapter removed from LPAR profile
  ===

  - I powered down the Ubuntu partition and removed the BELL-3 adapter from 
LPAR profile then powered on the LPAR.
  => Ubuntu hit the exception.

  Elapsed time since release of system processors: 0 mins 9 secs
  error: no suitable video mode found.
  OF stdout device is: /vdevice/vty@3000
  Preparing to boot Linux version 3.19.0-23-generic (buildd@denneed03) (gcc 
version 4.8.2 (Ubuntu 4.8.2-19ubuntu1) ) #24~14.04.1-Ubuntu SMP Wed Jul 8 
11:17:19 UTC 2015 (Ubuntu 3.19.0-23.24~14.04.1-generic 3.19.8-ckt2)
  Detected machine type: 0101
  Max number of cores passed to firmware: 256 (NR_CPUS = 2048)
  Calling ibm,client-architecture-support... done
  command line: BOOT_IMAGE=/boot/vmlinux-3.19.0-23-generic 
root=UUID=768190e7-f633-4c63-a1e3-588d12dea265 ro quiet splash vt.handoff=7
  memory layout at init:
memory_limit :  (16 MB aligned)
alloc_bottom : 0b42
alloc_top: 1000
alloc_top_hi : 1000
rmo_top  : 1000
ram_top  : 1000
  instantiating rtas at 0x0ecb... done
  prom_hold_cpus: skipped
  copying OF device tree...
  Building dt strings...
  Building dt structure...
  Device tree strings 0x0b43 -> 0x0b4316b1
  Device tree struct  0x0b44 -> 0x0b47
  Calling quiesce...
  returning from prom_init
   -> smp_release_cpus()
  spinning_secondaries = 15
   <- smp_release_cpus()
   <- setup_system()
  [0.661510] 
/build/linux-lts-vivid-uV14Ja/linux-lts-vivid-3.19.0/drivers/rtc/hctosys.c: 
unable to open rtc device (rtc0)
  [0.672826] sd 0:0:1:0: [sda] Assuming drive cache: write through
  [4.658302] device-mapper: table: 252:0: multipath: error getting device
  [4.691990] device-mapper: table: 252:0: multipath: error getting device
  [4.934034] device-mapper: table: 252:0: multipath: error getting device
  [4.951977] device-mapper: table: 252:0: multipath: error getting device
   * Discovering and coalescing multipaths...  [ OK 
] 
  Skipping profile in /etc/apparmor.d/disable: usr.sbin.rsyslogd
   * Starting AppArmor profiles[ OK 
] 
  Loading the saved-state of the serial devices... 
  [5.109665] Unable to handle kernel paging request for data at address 
0xd803
  [5.109677] Faulting instruction address: 0xc060fec4
  [5.109685] Oops: Kernel access of bad area, sig: 11 [#1]
  [5.109691] SMP NR_CPUS=2048 NUMA pSeries
  [5.109699] Modules linked in: dm_round_robin dm_multipath scsi_dh 
pseries_rng rtc_generic knem(OE) nfsd auth_rpcgss nfs_acl nfs lockd grace 
sunrpc fscache rdma_ucm(OE) ib_ucm(OE) rdma_cm(OE) iw_cm(OE) configfs 
ib_ipoib(OE) ib_cm(OE) ib_uverbs(OE) ib_umad(OE) mlx5_ib(OE) mlx5_core(OE) 
mlx4_ib(OE) ib_sa(OE) ib_mad(OE) ib_core(OE) ib_addr(OE) mlx4_en(OE) 
mlx4_core(OE) mlx_compat(OE)
  [5.109759] CPU: 1 PID: 1816 Comm: setserial Tainted: G   OE  
3.19.0-23-generic #24~14.04.1-Ubuntu
  [5.109769] task: c000f389c880 ti: c000f0528000 task.ti: 
c000f0528000
  [5.109777] NIP: c060fec4 LR: c0617498 CTR: 
c060fe20
  [5.109785] REGS: c000f052b6b0 TRAP: 0300   Tainted: G   OE   
(3.19.0-23-generic)
  [5.109793] MSR: 80009033   CR: 84002022  
XER: 
  [5.109814] CFAR: c0008468 DAR: d803 DSISR: 4200 
SOFTE: 1 
  GPR00: c0617498 c000f052b930 c144c700 00bf 
  GPR04: d803 00bf c000f399 0141 
  GPR08: c0611d20 c13539e0 d800 c1351ba8 
  GPR12: c060fe20 ce830900   
  GPR16:     
  GPR20: 007d 0040   
  GPR24:  c000f53cbc00 0001 

[Kernel-packages] [Bug 1115555] [NEW] Backlight control does not work, but there are entries in /sys/class/backlight.

2015-11-03 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

Backlight control does not work, but there are entries in
/sys/class/backlight.

This may require the ACPI backlight driver to not take control so that a
vendor specific driver will have a chance to register.

I wanto mention that this goes beyond just the applet not working.  My
data does change in Ubuntu for those entries and the acpi interface to
the Linux Kernel is not able to use that changed data to change the
hardware brightness setting.

ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: linux-image-3.2.0-37-generic 3.2.0-37.58
ProcVersionSignature: Ubuntu 3.2.0-37.58-generic 3.2.35
Uname: Linux 3.2.0-37-generic x86_64
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
ApportVersion: 2.0.1-0ubuntu17.1
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  carkaci1936 F pulseaudio
 /dev/snd/controlC0:  carkaci1936 F pulseaudio
CRDA:
 country AW:
(2402 - 2482 @ 40), (N/A, 20)
(5170 - 5250 @ 40), (N/A, 20)
(5250 - 5330 @ 40), (N/A, 20), DFS
(5490 - 5710 @ 40), (N/A, 27), DFS
Card0.Amixer.info:
 Card hw:0 'Intel'/'HDA Intel at 0xd050 irq 48'
   Mixer name   : 'Cirrus Logic CS4206'
   Components   : 'HDA:10134206,106b1800,00100301'
   Controls  : 25
   Simple ctrls  : 11
Card1.Amixer.info:
 Card hw:1 'Generic'/'HD-Audio Generic at 0xd044 irq 49'
   Mixer name   : 'ATI R6xx HDMI'
   Components   : 'HDA:1002aa01,00aa0100,00100200'
   Controls  : 6
   Simple ctrls  : 1
Card1.Amixer.values:
 Simple mixer control 'IEC958',0
   Capabilities: pswitch pswitch-joined penum
   Playback channels: Mono
   Mono: Playback [on]
Date: Mon Feb  4 21:53:10 2013
HibernationDevice: RESUME=UUID=2850be5d-9902-4a6d-8e97-3f9d34028e02
InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 
(20120823.1)
MachineType: Apple Inc. iMac11,3
MarkForUpload: True
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcFB: 0 radeondrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-37-generic 
root=UUID=83592388-7d5b-432f-94fe-74542604df39 ro acpi_osi=Linux quiet splash 
vt.handoff=7
PulseList:
 Error: command ['pacmd', 'list'] failed with exit code 1: Home directory 
/home/carkaci not ours.
 No PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
 linux-restricted-modules-3.2.0-37-generic N/A
 linux-backports-modules-3.2.0-37-generic  N/A
 linux-firmware1.79.1
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/03/10
dmi.bios.vendor: Apple Inc.
dmi.bios.version: IM112.88Z.0057.B00.1005031455
dmi.board.name: Mac-F2238BAE
dmi.board.vendor: Apple Inc.
dmi.board.version: iMac11,3
dmi.chassis.type: 13
dmi.chassis.vendor: Apple Inc.
dmi.chassis.version: Mac-F2238BAE
dmi.modalias: 
dmi:bvnAppleInc.:bvrIM112.88Z.0057.B00.1005031455:bd05/03/10:svnAppleInc.:pniMac11,3:pvr1.0:rvnAppleInc.:rnMac-F2238BAE:rvriMac11,3:cvnAppleInc.:ct13:cvrMac-F2238BAE:
dmi.product.name: iMac11,3
dmi.product.version: 1.0
dmi.sys.vendor: Apple Inc.

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


** Tags: amd64 apport-bug kernel-bug-exists-upstream-v3.8-rc6 
needs-upstream-testing precise regression-potential
-- 
Backlight control does not work, but there are entries in /sys/class/backlight.
https://bugs.launchpad.net/bugs/111
You received this bug notification because you are a member of Kernel Packages, 
which is subscribed to linux in Ubuntu.

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


[Kernel-packages] [Bug 1012291] Re: USB disconnect

2015-11-03 Thread Christopher M. Penalver
databill, it will help immensely if you filed a new report via a terminal:
ubuntu-bug linux

Please feel free to subscribe me to it.

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

Title:
   USB disconnect

Status in linux package in Ubuntu:
  Expired

Bug description:
  USB ports are often resetted and disconnected.
  Below an example sequence:

  [mar giu 12 18:57:22 2012] usb 2-1.6: reset low-speed USB device number 106 
using ehci_hcd
  [mar giu 12 18:57:22 2012] usb 2-1.6: USB disconnect, device number 106
  [mar giu 12 18:57:22 2012] usb 2-1: reset high-speed USB device number 105 
using ehci_hcd
  [mar giu 12 18:57:23 2012] usb 2-1.6: new low-speed USB device number 107 
using ehci_hcd
  [mar giu 12 18:57:23 2012] input: Chicony 2.4G Multimedia Wireless Kit as 
/devices/pci:00/:00:1d.0/usb2/2-1/2-1.6/2-1.6:1.0/input/input297
  [mar giu 12 18:57:23 2012] generic-usb 0003:04F2:0860.00E9: input,hidraw0: 
USB HID v1.11 Keyboard [Chicony 2.4G Multimedia Wireless Kit] on 
usb-:00:1d.0-1.6/input0
  [mar giu 12 18:57:23 2012] input: Chicony 2.4G Multimedia Wireless Kit as 
/devices/pci:00/:00:1d.0/usb2/2-1/2-1.6/2-1.6:1.1/input/input298
  [mar giu 12 18:57:23 2012] generic-usb 0003:04F2:0860.00EA: 
input,hiddev0,hidraw1: USB HID v1.11 Mouse [Chicony 2.4G Multimedia Wireless 
Kit] on usb-:00:1d.0-1.6/input1
  [mar giu 12 18:57:23 2012] usb 2-1: USB disconnect, device number 105
  [mar giu 12 18:57:23 2012] usb 2-1.6: USB disconnect, device number 107
  [mar giu 12 18:57:23 2012] usb 2-1: new high-speed USB device number 108 
using ehci_hcd
  [mar giu 12 18:57:23 2012] hub 2-1:1.0: USB hub found
  [mar giu 12 18:57:23 2012] hub 2-1:1.0: 8 ports detected
  [mar giu 12 18:57:24 2012] usb 1-1.3.1.3: reset full-speed USB device number 
51 using ehci_hcd
  [mar giu 12 18:57:24 2012] usb 2-1.6: new low-speed USB device number 109 
using ehci_hcd
  [mar giu 12 18:57:24 2012] input: Chicony 2.4G Multimedia Wireless Kit as 
/devices/pci:00/:00:1d.0/usb2/2-1/2-1.6/2-1.6:1.0/input/input299
  [mar giu 12 18:57:24 2012] generic-usb 0003:04F2:0860.00EB: input,hidraw0: 
USB HID v1.11 Keyboard [Chicony 2.4G Multimedia Wireless Kit] on 
usb-:00:1d.0-1.6/input0
  [mar giu 12 18:57:24 2012] input: Chicony 2.4G Multimedia Wireless Kit as 
/devices/pci:00/:00:1d.0/usb2/2-1/2-1.6/2-1.6:1.1/input/input300
  [mar giu 12 18:57:24 2012] generic-usb 0003:04F2:0860.00EC: 
input,hiddev0,hidraw1: USB HID v1.11 Mouse [Chicony 2.4G Multimedia Wireless 
Kit] on usb-:00:1d.0-1.6/input1
  [mar giu 12 18:57:24 2012] input: 3M 3M USB Touchscreen - EX II as 
/devices/pci:00/:00:1a.0/usb1/1-1/1-1.3/1-1.3.1/1-1.3.1.3/1-1.3.1.3:1.0/input/input301
  [mar giu 12 18:57:24 2012] usb 1-1.3.4: reset low-speed USB device number 50 
using ehci_hcd
  [mar giu 12 18:57:24 2012] usb 1-1.3.1.3: USB disconnect, device number 51
  [mar giu 12 18:57:25 2012] usb 1-1.3.1: reset high-speed USB device number 49 
using ehci_hcd
  [mar giu 12 18:57:25 2012] usb 1-1.3.1.3: new full-speed USB device number 52 
using ehci_hcd
  [mar giu 12 18:57:25 2012] input: 3M 3M USB Touchscreen - EX II as 
/devices/pci:00/:00:1a.0/usb1/1-1/1-1.3/1-1.3.1/1-1.3.1.3/1-1.3.1.3:1.0/input/input302
  [mar giu 12 18:57:25 2012] usb 1-1.5.1: reset full-speed USB device number 48 
using ehci_hcd
  [mar giu 12 18:57:26 2012] usb 1-1.5.1: USB disconnect, device number 48
  [mar giu 12 18:57:26 2012] usb 1-1.5: reset high-speed USB device number 42 
using ehci_hcd
  [mar giu 12 18:57:26 2012] usb 1-1.5.1: new full-speed USB device number 53 
using ehci_hcd
  [mar giu 12 18:57:26 2012] usb 1-1.3.1: USB disconnect, device number 49
  [mar giu 12 18:57:26 2012] usb 1-1.3.1.3: USB disconnect, device number 52
  [mar giu 12 18:57:26 2012] usb 1-1.3.4: USB disconnect, device number 50
  [mar giu 12 18:57:26 2012] usb 1-1.3: reset high-speed USB device number 41 
using ehci_hcd
  [mar giu 12 18:57:27 2012] usb 1-1.3.1: new high-speed USB device number 54 
using ehci_hcd
  [mar giu 12 18:57:27 2012] hub 1-1.3.1:1.0: USB hub found
  [mar giu 12 18:57:27 2012] hub 1-1.3.1:1.0: 4 ports detected
  [mar giu 12 18:57:27 2012] usb 1-1.3.4: new low-speed USB device number 55 
using ehci_hcd
  [mar giu 12 18:57:27 2012] input: BIZLINK  BIZ A01 V1.47 as 
/devices/pci:00/:00:1a.0/usb1/1-1/1-1.3/1-1.3.4/1-1.3.4:1.0/input/input303
  [mar giu 12 18:57:27 2012] generic-usb 0003:06C4:1400.00ED: input,hidraw2: 
USB HID v1.10 Keyboard [BIZLINK  BIZ A01 V1.47] on usb-:00:1a.0-1.3.4/input0
  [mar giu 12 18:57:27 2012] input: BIZLINK  BIZ A01 V1.47 as 
/devices/pci:00/:00:1a.0/usb1/1-1/1-1.3/1-1.3.4/1-1.3.4:1.1/input/input304
  [mar giu 12 18:57:27 2012] generic-usb 0003:06C4:1400.00EE: input,hidraw3: 
USB HID v1.10 Mouse [BIZLINK  BIZ A01 V1.47] on usb-:00:1a.0-1.3.4/input1
  [mar giu 12 18:57:27 2012] usb 1-1.3.1.3: new 

[Kernel-packages] [Bug 1384342] Re: kernel messages intel_crtc_wait_for_pending_flips correlate to compiz hang

2015-11-03 Thread Mike
Upgrading to 3.16 still caused display to crash.

I've successfully upgraded to kernel 3.19 (3.19.0-31-generic) and
haven't experienced the display crash issue since.

 sudo apt-get install linux-generic-lts-vivid

I only ran into one issue with the i915 DKMS module crashing and fixed it by 
installing the 3.19 version:
  
 sudo apt-get install i915-3.19-3.13-dkms

Since those two package upgrades, my 14.04.3 LTS install has been
running great.

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

Title:
  kernel messages intel_crtc_wait_for_pending_flips correlate to compiz
  hang

Status in Linux:
  Unknown
Status in System76:
  New
Status in xf86-video-intel:
  Fix Released
Status in linux package in Ubuntu:
  Triaged
Status in linux package in Debian:
  Confirmed
Status in linux package in Fedora:
  Unknown
Status in linux package in openSUSE:
  Unknown

Bug description:
  I am fairly frequently (maybe once every 2 days) seeing screen
  lockups.  The system is fine, and then screen locks up. mouse is still
  movable and even changes icon based on content under it (ie mouse over
  link changes to pointing hand).  Programs are still running (often
  this occurs during a google hangout, and the hangout, audio and mic
  seem to work fine).

  Today when this happened I had more patience and hit ctrl-alt-f1, and then 
subsequently saw that dmesg had:
  [82218.556025] [ cut here ]
  [82218.556074] WARNING: CPU: 0 PID: 8799 at 
/build/buildd/linux-3.16.0/drivers/gpu/drm/i915/intel_display.c:3324 
intel_crtc_wait_for_pending_flips+0x16c/0x180 [i915]()
  [82218.556095] Modules linked in: xt_conntrack ipt_REJECT overlayfs pci_stub 
vboxpci(OE) vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) xt_CHECKSUM 
iptable_mangle ipt_MASQUERADE iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 
nf_nat_ipv4 nf_nat nf_conntrack xt_tcpudp bridge stp llc iptable_filter 
ip_tables x_tables rfcomm bnep binfmt_misc dm_crypt uvcvideo videobuf2_vmalloc 
videobuf2_memops videobuf2_core v4l2_common videodev media dm_multipath scsi_dh 
coretemp kvm_intel kvm arc4 joydev iwldvm mac80211 serio_raw btusb bluetooth 
pcmcia 6lowpan_iphc thinkpad_acpi snd_seq_midi snd_seq_midi_event nvram 
snd_hda_codec_conexant snd_hda_codec_generic r852 sm_common lpc_ich nand 
snd_rawmidi nand_ecc nand_bch snd_hda_intel bch nand_ids snd_hda_controller 
snd_hda_codec snd_hwdep mtd snd_seq iwlwifi r592 memstick snd_pcm
  [82218.556112]  yenta_socket pcmcia_rsrc pcmcia_core cfg80211 snd_seq_device 
shpchp snd_timer mei_me mei snd soundcore mac_hid parport_pc ppdev tp_smapi(OE) 
thinkpad_ec(OE) lp parport btrfs raid10 raid456 async_raid6_recov async_memcpy 
async_pq async_xor async_tx xor raid6_pq raid1 raid0 multipath linear 
hid_generic usbhid hid psmouse firewire_ohci ahci libahci firewire_core 
sdhci_pci sdhci crc_itu_t i915 wmi e1000e i2c_algo_bit drm_kms_helper video drm 
ptp pps_core pata_acpi [last unloaded: ipmi_msghandler]
  [82218.556114] CPU: 0 PID: 8799 Comm: kworker/0:1 Tainted: GW  OE 
3.16.0-23-generic #30-Ubuntu
  [82218.556115] Hardware name: LENOVO 7417CTO/7417CTO, BIOS 7UET94WW (3.24 ) 
10/17/2012
  [82218.556119] Workqueue: events console_callback
  [82218.556122]  0009 880016a3faf8 8177fcbc 

  [82218.556123]  880016a3fb30 8106fd8d  
880035a5a000
  [82218.556124]  880035948210 880035826800 880035826800 
880016a3fb40
  [82218.556125] Call Trace:
  [82218.556130]  [] dump_stack+0x45/0x56
  [82218.556133]  [] warn_slowpath_common+0x7d/0xa0
  [82218.556135]  [] warn_slowpath_null+0x1a/0x20
  [82218.556153]  [] 
intel_crtc_wait_for_pending_flips+0x16c/0x180 [i915]
  [82218.556156]  [] ? prepare_to_wait_event+0x100/0x100
  [82218.556175]  [] intel_crtc_disable_planes+0x33/0x1c0 
[i915]
  [82218.556177]  [] ? __ww_mutex_lock+0x1b/0xb0
  [82218.556196]  [] i9xx_crtc_disable+0x51/0x3f0 [i915]
  [82218.556220]  [] intel_crtc_update_dpms+0x67/0xa0 [i915]
  [82218.556237]  [] intel_connector_dpms+0x59/0x70 [i915]
  [82218.556245]  [] drm_fb_helper_dpms.isra.5+0xc1/0x100 
[drm_kms_helper]
  [82218.556251]  [] drm_fb_helper_blank+0x31/0x90 
[drm_kms_helper]
  [82218.556254]  [] fb_blank+0x57/0xc0
  [82218.556256]  [] fbcon_blank+0xfb/0x300
  [82218.556258]  [] ? __queue_delayed_work+0x182/0x1c0
  [82218.556259]  [] ? try_to_grab_pending+0xa9/0x160
  [82218.556262]  [] ? lock_timer_base.isra.34+0x2b/0x50
  [82218.556264]  [] ? try_to_del_timer_sync+0x4f/0x70
  [82218.556266]  [] do_blank_screen+0x1d3/0x280
  [82218.556267]  [] console_callback+0x68/0x160
  [82218.556269]  [] process_one_work+0x182/0x4e0
  [82218.556270]  [] worker_thread+0x6b/0x6a0
  [82218.556272]  [] ? __schedule+0x39d/0x890
  [82218.556273]  [] ? process_one_work+0x4e0/0x4e0
  [82218.556275]  [] kthread+0xdb/0x100
  [82218.556277]  [] ? 

[Kernel-packages] [Bug 1512691] [NEW] [Macbook Pro] Backlight control does not work, but there are entries in /sys/class/backlight

2015-11-03 Thread Gaele Strootman
Public bug reported:

Backlight control stopped working after upgrade from Vivid to Wily.

Macbook Pro 11,3 with nouveau.

/sys/class/backlight/gmux_backlight$ grep . *
actual_brightness:16777215
bl_power:0
brightness:400
grep: device: Is a directory
max_brightness:-1
grep: power: Is a directory
grep: subsystem: Is a directory
type:platform


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

ProblemType: Bug
DistroRelease: Ubuntu 15.10
Package: linux-image-4.2.0-16-generic 4.2.0-16.19
ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3
Uname: Linux 4.2.0-16-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.19.1-0ubuntu4
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  gaele  2525 F pulseaudio
 /dev/snd/controlC0:  gaele  2525 F pulseaudio
CurrentDesktop: Unity
Date: Tue Nov  3 13:44:25 2015
EcryptfsInUse: Yes
HibernationDevice: RESUME=UUID=716bc023-ef4e-436e-8e5b-5a1f548faef8
InstallationDate: Installed on 2015-04-26 (190 days ago)
InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
MachineType: Apple Inc. MacBookPro11,3
ProcFB: 0 nouveaufb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-16-generic.efi.signed 
root=UUID=38c8fe6d-3763-4619-a710-f65494173fe4 ro quiet splash 
libata.force=noncq vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-4.2.0-16-generic N/A
 linux-backports-modules-4.2.0-16-generic  N/A
 linux-firmware1.149
SourcePackage: linux
UpgradeStatus: Upgraded to wily on 2015-10-22 (11 days ago)
dmi.bios.date: 06/05/2015
dmi.bios.vendor: Apple Inc.
dmi.bios.version: MBP112.88Z.0138.B15.1506050548
dmi.board.asset.tag: Base Board Asset Tag#
dmi.board.name: Mac-2BD1B31983FE1663
dmi.board.vendor: Apple Inc.
dmi.board.version: MacBookPro11,3
dmi.chassis.type: 10
dmi.chassis.vendor: Apple Inc.
dmi.chassis.version: Mac-2BD1B31983FE1663
dmi.modalias: 
dmi:bvnAppleInc.:bvrMBP112.88Z.0138.B15.1506050548:bd06/05/2015:svnAppleInc.:pnMacBookPro11,3:pvr1.0:rvnAppleInc.:rnMac-2BD1B31983FE1663:rvrMacBookPro11,3:cvnAppleInc.:ct10:cvrMac-2BD1B31983FE1663:
dmi.product.name: MacBookPro11,3
dmi.product.version: 1.0
dmi.sys.vendor: Apple Inc.

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


** Tags: amd64 apport-bug 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/1512691

Title:
  [Macbook Pro] Backlight control does not work, but there are entries
  in /sys/class/backlight

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Backlight control stopped working after upgrade from Vivid to Wily.

  Macbook Pro 11,3 with nouveau.

  /sys/class/backlight/gmux_backlight$ grep . *
  actual_brightness:16777215
  bl_power:0
  brightness:400
  grep: device: Is a directory
  max_brightness:-1
  grep: power: Is a directory
  grep: subsystem: Is a directory
  type:platform

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

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: linux-image-4.2.0-16-generic 4.2.0-16.19
  ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3
  Uname: Linux 4.2.0-16-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.19.1-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  gaele  2525 F pulseaudio
   /dev/snd/controlC0:  gaele  2525 F pulseaudio
  CurrentDesktop: Unity
  Date: Tue Nov  3 13:44:25 2015
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=716bc023-ef4e-436e-8e5b-5a1f548faef8
  InstallationDate: Installed on 2015-04-26 (190 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  MachineType: Apple Inc. MacBookPro11,3
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-16-generic.efi.signed 
root=UUID=38c8fe6d-3763-4619-a710-f65494173fe4 ro quiet splash 
libata.force=noncq vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.2.0-16-generic N/A
   linux-backports-modules-4.2.0-16-generic  N/A
   linux-firmware1.149
  SourcePackage: linux
  UpgradeStatus: Upgraded to wily on 2015-10-22 (11 days ago)
  dmi.bios.date: 06/05/2015
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: MBP112.88Z.0138.B15.1506050548
  dmi.board.asset.tag: Base Board Asset Tag#
  dmi.board.name: Mac-2BD1B31983FE1663
  dmi.board.vendor: Apple Inc.
  dmi.board.version: MacBookPro11,3
  dmi.chassis.type: 10
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-2BD1B31983FE1663
  dmi.modalias: 
dmi:bvnAppleInc.:bvrMBP112.88Z.0138.B15.1506050548:bd06/05/2015:svnAppleInc.:pnMacBookPro11,3:pvr1.0:rvnAppleInc.:rnMac-2BD1B31983FE1663:rvrMacBookPro11,3:cvnAppleInc.:ct10:cvrMac-2BD1B31983FE1663:
  dmi.product.name: MacBookPro11,3
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.

To manage 

[Kernel-packages] [Bug 1512691] Re: [Macbook Pro] Backlight control does not work, but there are entries in /sys/class/backlight

2015-11-03 Thread Gaele Strootman
Contrary to bug #111, nothing changes after changing the brightness
in MacOSX and rebooting back into Ubuntu. I'm still at maximum
brightness.

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

Title:
  [Macbook Pro] Backlight control does not work, but there are entries
  in /sys/class/backlight

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Backlight control stopped working after upgrade from Vivid to Wily.

  Macbook Pro 11,3 with nouveau.

  /sys/class/backlight/gmux_backlight$ grep . *
  actual_brightness:16777215
  bl_power:0
  brightness:400
  grep: device: Is a directory
  max_brightness:-1
  grep: power: Is a directory
  grep: subsystem: Is a directory
  type:platform

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

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: linux-image-4.2.0-16-generic 4.2.0-16.19
  ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3
  Uname: Linux 4.2.0-16-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.19.1-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  gaele  2525 F pulseaudio
   /dev/snd/controlC0:  gaele  2525 F pulseaudio
  CurrentDesktop: Unity
  Date: Tue Nov  3 13:44:25 2015
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=716bc023-ef4e-436e-8e5b-5a1f548faef8
  InstallationDate: Installed on 2015-04-26 (190 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  MachineType: Apple Inc. MacBookPro11,3
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-16-generic.efi.signed 
root=UUID=38c8fe6d-3763-4619-a710-f65494173fe4 ro quiet splash 
libata.force=noncq vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.2.0-16-generic N/A
   linux-backports-modules-4.2.0-16-generic  N/A
   linux-firmware1.149
  SourcePackage: linux
  UpgradeStatus: Upgraded to wily on 2015-10-22 (11 days ago)
  dmi.bios.date: 06/05/2015
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: MBP112.88Z.0138.B15.1506050548
  dmi.board.asset.tag: Base Board Asset Tag#
  dmi.board.name: Mac-2BD1B31983FE1663
  dmi.board.vendor: Apple Inc.
  dmi.board.version: MacBookPro11,3
  dmi.chassis.type: 10
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-2BD1B31983FE1663
  dmi.modalias: 
dmi:bvnAppleInc.:bvrMBP112.88Z.0138.B15.1506050548:bd06/05/2015:svnAppleInc.:pnMacBookPro11,3:pvr1.0:rvnAppleInc.:rnMac-2BD1B31983FE1663:rvrMacBookPro11,3:cvnAppleInc.:ct10:cvrMac-2BD1B31983FE1663:
  dmi.product.name: MacBookPro11,3
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1512691/+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 1482711] Re: X displays nothing instead of login screen

2015-11-03 Thread Christopher M. Penalver
** 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/1482711

Title:
  X displays nothing instead of login screen

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The kernel version in the auto-generated information is wrong, because
  when using the kernel with the problem, I can't do anything, including
  send bug reports. This happened with the newest kernel update to
  3.13.0-61. I am using -59, which still works, to send the report.
  Since this is at least possibly graphics related bug I should also
  state that the update automatically changed the nvidia driver from
  331-updates to 340-updates, however Nvidia's page for the 340 driver
  does not include my graphics card (GeForce 610M). I do use

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-59-generic 3.13.0-59.98
  ProcVersionSignature: Ubuntu 3.13.0-59.98-generic 3.13.11-ckt22
  Uname: Linux 3.13.0-59-generic i686
  ApportVersion: 2.14.1-0ubuntu3.11
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  trun   2629 F pulseaudio
  CurrentDesktop: Unity
  Date: Fri Aug  7 09:22:29 2015
  HibernationDevice: RESUME=UUID=6d121e03-2523-4564-ab73-f600c35a6142
  InstallationDate: Installed on 2014-11-23 (256 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release i386 
(20140722.2)
  Lsusb:
   Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
   Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 001 Device 003: ID 1bcf:288a Sunplus Innovation Technology Inc. 
   Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Acer Aspire 7739G
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-59-generic 
root=/dev/mapper/vg_hydra-lv_root ro noplymouth
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-59-generic N/A
   linux-backports-modules-3.13.0-59-generic  N/A
   linux-firmware 1.127.14
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  WifiSyslog:
   
  dmi.bios.date: 10/11/2011
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.04
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: HMA71_CP
  dmi.board.vendor: Acer
  dmi.board.version: Type2 - Board Version
  dmi.chassis.type: 10
  dmi.chassis.vendor: Chassis Manufacturer
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.04:bd10/11/2011:svnAcer:pnAspire7739G:pvrV1.04:rvnAcer:rnHMA71_CP:rvrType2-BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion:
  dmi.product.name: Aspire 7739G
  dmi.product.version: V1.04
  dmi.sys.vendor: Acer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1482711/+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 1115555] Re: Backlight control does not work, but there are entries in /sys/class/backlight.

2015-11-03 Thread Christopher M. Penalver
** No longer affects: linux (Ubuntu)

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

Title:
  Backlight control does not work, but there are entries in
  /sys/class/backlight.

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Backlight control does not work, but there are entries in
  /sys/class/backlight.

  This may require the ACPI backlight driver to not take control so that
  a vendor specific driver will have a chance to register.

  I wanto mention that this goes beyond just the applet not working.  My
  data does change in Ubuntu for those entries and the acpi interface to
  the Linux Kernel is not able to use that changed data to change the
  hardware brightness setting.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: linux-image-3.2.0-37-generic 3.2.0-37.58
  ProcVersionSignature: Ubuntu 3.2.0-37.58-generic 3.2.35
  Uname: Linux 3.2.0-37-generic x86_64
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
  ApportVersion: 2.0.1-0ubuntu17.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  carkaci1936 F pulseaudio
   /dev/snd/controlC0:  carkaci1936 F pulseaudio
  CRDA:
   country AW:
(2402 - 2482 @ 40), (N/A, 20)
(5170 - 5250 @ 40), (N/A, 20)
(5250 - 5330 @ 40), (N/A, 20), DFS
(5490 - 5710 @ 40), (N/A, 27), DFS
  Card0.Amixer.info:
   Card hw:0 'Intel'/'HDA Intel at 0xd050 irq 48'
 Mixer name : 'Cirrus Logic CS4206'
 Components : 'HDA:10134206,106b1800,00100301'
 Controls  : 25
 Simple ctrls  : 11
  Card1.Amixer.info:
   Card hw:1 'Generic'/'HD-Audio Generic at 0xd044 irq 49'
 Mixer name : 'ATI R6xx HDMI'
 Components : 'HDA:1002aa01,00aa0100,00100200'
 Controls  : 6
 Simple ctrls  : 1
  Card1.Amixer.values:
   Simple mixer control 'IEC958',0
 Capabilities: pswitch pswitch-joined penum
 Playback channels: Mono
 Mono: Playback [on]
  Date: Mon Feb  4 21:53:10 2013
  HibernationDevice: RESUME=UUID=2850be5d-9902-4a6d-8e97-3f9d34028e02
  InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 
(20120823.1)
  MachineType: Apple Inc. iMac11,3
  MarkForUpload: True
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-37-generic 
root=UUID=83592388-7d5b-432f-94fe-74542604df39 ro acpi_osi=Linux quiet splash 
vt.handoff=7
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory 
/home/carkaci not ours.
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-3.2.0-37-generic N/A
   linux-backports-modules-3.2.0-37-generic  N/A
   linux-firmware1.79.1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/03/10
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: IM112.88Z.0057.B00.1005031455
  dmi.board.name: Mac-F2238BAE
  dmi.board.vendor: Apple Inc.
  dmi.board.version: iMac11,3
  dmi.chassis.type: 13
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-F2238BAE
  dmi.modalias: 
dmi:bvnAppleInc.:bvrIM112.88Z.0057.B00.1005031455:bd05/03/10:svnAppleInc.:pniMac11,3:pvr1.0:rvnAppleInc.:rnMac-F2238BAE:rvriMac11,3:cvnAppleInc.:ct13:cvrMac-F2238BAE:
  dmi.product.name: iMac11,3
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/111/+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 1505242] Re: WARNING: ... intel_display.c:11100 intel_check_page_flip

2015-11-03 Thread Christopher M. Penalver
Visi Bilius, could you please test the latest mainline kernel (4.3, not
4.3-rcX) and advise to the results?

** Changed in: linux (Ubuntu)
   Status: Invalid => 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/1505242

Title:
  WARNING: ... intel_display.c:11100 intel_check_page_flip

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I see warnings similar to this occasionally in the dmesg output.
  I first noticed it, when the system refused to put load on all but one core, 
and I tried to find the reason.
  But it happened again a few times, and I did not notice that effect (or any).
  I do not know the trigger. I suspect playing video.
  This is a fresh install of Ubuntu 15.04 on a fresh hardware.

  I found several similar error reports with google. All appeared to be 
unsolved.
  I thought, I submit this report, anyway. Perhaps it provides some new 
information.

  [ 5967.045926] [ cut here ]
  [ 5967.045949] WARNING: CPU: 3 PID: 0 at 
/build/linux-qOmAV7/linux-3.19.0/ubuntu/i915/intel_display.c:11100 
intel_check_page_flip+0x11c/0x130 [i915_bpo]()
  [ 5967.045950] Kicking stuck page flip: queued at 343930, now 343934
  [ 5967.045951] Modules linked in: cfg80211 binfmt_misc dm_crypt nls_iso8859_1 
snd_hda_codec_hdmi snd_hda_codec_realtek snd_hda_codec_generic snd_hda_intel 
eeepc_wmi snd_hda_controller asus_wmi sparse_keymap snd_hda_codec snd_usb_audio 
snd_usbmidi_lib snd_hwdep x86_pkg_temp_thermal snd_pcm coretemp kvm_intel kvm 
snd_seq_midi snd_seq_midi_event crct10dif_pclmul snd_rawmidi ip6t_REJECT 
nf_reject_ipv6 crc32_pclmul ghash_clmulni_intel nf_log_ipv6 snd_seq uvcvideo 
aesni_intel videobuf2_vmalloc videobuf2_memops snd_seq_device aes_x86_64 
videobuf2_core lrw xt_hl gf128mul v4l2_common glue_helper hid_multitouch 
videodev ablk_helper ip6t_rt cryptd snd_timer media snd joydev serio_raw 
i915_bpo nf_conntrack_ipv6 soundcore nf_defrag_ipv6 intel_ips drm_kms_helper 
ipt_REJECT nf_reject_ipv4 drm 8250_fintek nf_log_ipv4
  [ 5967.045968]  nf_log_common i2c_algo_bit i2c_hid shpchp xt_LOG mac_hid 
acpi_pad xt_limit xt_tcpudp xt_addrtype nf_conntrack_ipv4 nf_defrag_ipv4 
xt_conntrack ip6table_filter ip6_tables nf_conntrack_netbios_ns 
nf_conntrack_broadcast nf_nat_ftp nf_nat nf_conntrack_ftp nf_conntrack 
iptable_filter ip_tables x_tables parport_pc ppdev lp parport autofs4 btrfs xor 
raid6_pq hid_generic usbhid hid mxm_wmi e1000e psmouse ptp pps_core ahci 
libahci wmi video
  [ 5967.045984] CPU: 3 PID: 0 Comm: swapper/3 Not tainted 3.19.0-30-generic 
#34-Ubuntu
  [ 5967.045985] Hardware name: System manufacturer System Product Name/Z170-A, 
BIOS 0502 07/14/2015
  [ 5967.045986]  c076c138 88046ed83d68 817c4d5f 
0007
  [ 5967.045987]  88046ed83db8 88046ed83da8 81076a8a 
88046ed83db8
  [ 5967.045988]  88045ac18800 880456f46000 88045ac189a8 

  [ 5967.045990] Call Trace:
  [ 5967.045991][] dump_stack+0x45/0x57
  [ 5967.045997]  [] warn_slowpath_common+0x8a/0xc0
  [ 5967.045999]  [] warn_slowpath_fmt+0x46/0x50
  [ 5967.046011]  [] intel_check_page_flip+0x11c/0x130 
[i915_bpo]
  [ 5967.046021]  [] gen8_irq_handler+0x37e/0x5d0 [i915_bpo]
  [ 5967.046023]  [] ? read_tsc+0x9/0x10
  [ 5967.046026]  [] handle_irq_event_percpu+0x77/0x1a0
  [ 5967.046027]  [] handle_irq_event+0x41/0x70
  [ 5967.046029]  [] handle_edge_irq+0x6e/0x120
  [ 5967.046031]  [] handle_irq+0x22/0x40
  [ 5967.046033]  [] do_IRQ+0x4f/0xf0
  [ 5967.046034]  [] common_interrupt+0x6d/0x6d
  [ 5967.046035][] ? finish_task_switch+0x67/0x150
  [ 5967.046039]  [] __schedule+0x39c/0x8e0
  [ 5967.046041]  [] schedule_preempt_disabled+0x29/0x70
  [ 5967.046043]  [] cpu_startup_entry+0x187/0x3b0
  [ 5967.046045]  [] start_secondary+0x197/0x1c0
  [ 5967.046046] ---[ end trace 6b6de72fa2c286b6 ]---

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: linux-image-3.19.0-30-generic 3.19.0-30.34
  ProcVersionSignature: Ubuntu 3.19.0-30.34-generic 3.19.8-ckt6
  Uname: Linux 3.19.0-30-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  lacko  1507 F pulseaudio
   /dev/snd/controlC0:  lacko  1507 F pulseaudio
  CurrentDesktop: Unity
  Date: Mon Oct 12 15:05:50 2015
  InstallationDate: Installed on 2015-10-10 (2 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  IwConfig:
   eth0  no wireless extensions.
   
   lono wireless extensions.
  MachineType: System manufacturer System Product Name
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-30-generic.efi.signed 
root=/dev/mapper/ubuntu_ssd1-ubuntu_root ro rootflags=subvol=@ quiet splash
  RelatedPackageVersions:
   linux-restricted-modules-3.19.0-30-generic N/A
   

[Kernel-packages] [Bug 1115555] Re: Backlight control does not work, but there are entries in /sys/class/backlight.

2015-11-03 Thread Christopher M. Penalver
Gaele Strootman, it will help immensely if you filed a new report via a 
terminal:
ubuntu-bug linux

Please feel free to subscribe me to it.

** Project changed: linux => linux (Ubuntu)

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

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

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

Title:
  Backlight control does not work, but there are entries in
  /sys/class/backlight.

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Backlight control does not work, but there are entries in
  /sys/class/backlight.

  This may require the ACPI backlight driver to not take control so that
  a vendor specific driver will have a chance to register.

  I wanto mention that this goes beyond just the applet not working.  My
  data does change in Ubuntu for those entries and the acpi interface to
  the Linux Kernel is not able to use that changed data to change the
  hardware brightness setting.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: linux-image-3.2.0-37-generic 3.2.0-37.58
  ProcVersionSignature: Ubuntu 3.2.0-37.58-generic 3.2.35
  Uname: Linux 3.2.0-37-generic x86_64
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
  ApportVersion: 2.0.1-0ubuntu17.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  carkaci1936 F pulseaudio
   /dev/snd/controlC0:  carkaci1936 F pulseaudio
  CRDA:
   country AW:
(2402 - 2482 @ 40), (N/A, 20)
(5170 - 5250 @ 40), (N/A, 20)
(5250 - 5330 @ 40), (N/A, 20), DFS
(5490 - 5710 @ 40), (N/A, 27), DFS
  Card0.Amixer.info:
   Card hw:0 'Intel'/'HDA Intel at 0xd050 irq 48'
 Mixer name : 'Cirrus Logic CS4206'
 Components : 'HDA:10134206,106b1800,00100301'
 Controls  : 25
 Simple ctrls  : 11
  Card1.Amixer.info:
   Card hw:1 'Generic'/'HD-Audio Generic at 0xd044 irq 49'
 Mixer name : 'ATI R6xx HDMI'
 Components : 'HDA:1002aa01,00aa0100,00100200'
 Controls  : 6
 Simple ctrls  : 1
  Card1.Amixer.values:
   Simple mixer control 'IEC958',0
 Capabilities: pswitch pswitch-joined penum
 Playback channels: Mono
 Mono: Playback [on]
  Date: Mon Feb  4 21:53:10 2013
  HibernationDevice: RESUME=UUID=2850be5d-9902-4a6d-8e97-3f9d34028e02
  InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 
(20120823.1)
  MachineType: Apple Inc. iMac11,3
  MarkForUpload: True
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-37-generic 
root=UUID=83592388-7d5b-432f-94fe-74542604df39 ro acpi_osi=Linux quiet splash 
vt.handoff=7
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory 
/home/carkaci not ours.
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-3.2.0-37-generic N/A
   linux-backports-modules-3.2.0-37-generic  N/A
   linux-firmware1.79.1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/03/10
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: IM112.88Z.0057.B00.1005031455
  dmi.board.name: Mac-F2238BAE
  dmi.board.vendor: Apple Inc.
  dmi.board.version: iMac11,3
  dmi.chassis.type: 13
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-F2238BAE
  dmi.modalias: 
dmi:bvnAppleInc.:bvrIM112.88Z.0057.B00.1005031455:bd05/03/10:svnAppleInc.:pniMac11,3:pvr1.0:rvnAppleInc.:rnMac-F2238BAE:rvriMac11,3:cvnAppleInc.:ct13:cvrMac-F2238BAE:
  dmi.product.name: iMac11,3
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/111/+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 1115555] Re: Backlight control does not work, but there are entries in /sys/class/backlight.

2015-11-03 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

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

Title:
  Backlight control does not work, but there are entries in
  /sys/class/backlight.

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Backlight control does not work, but there are entries in
  /sys/class/backlight.

  This may require the ACPI backlight driver to not take control so that
  a vendor specific driver will have a chance to register.

  I wanto mention that this goes beyond just the applet not working.  My
  data does change in Ubuntu for those entries and the acpi interface to
  the Linux Kernel is not able to use that changed data to change the
  hardware brightness setting.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: linux-image-3.2.0-37-generic 3.2.0-37.58
  ProcVersionSignature: Ubuntu 3.2.0-37.58-generic 3.2.35
  Uname: Linux 3.2.0-37-generic x86_64
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
  ApportVersion: 2.0.1-0ubuntu17.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  carkaci1936 F pulseaudio
   /dev/snd/controlC0:  carkaci1936 F pulseaudio
  CRDA:
   country AW:
(2402 - 2482 @ 40), (N/A, 20)
(5170 - 5250 @ 40), (N/A, 20)
(5250 - 5330 @ 40), (N/A, 20), DFS
(5490 - 5710 @ 40), (N/A, 27), DFS
  Card0.Amixer.info:
   Card hw:0 'Intel'/'HDA Intel at 0xd050 irq 48'
 Mixer name : 'Cirrus Logic CS4206'
 Components : 'HDA:10134206,106b1800,00100301'
 Controls  : 25
 Simple ctrls  : 11
  Card1.Amixer.info:
   Card hw:1 'Generic'/'HD-Audio Generic at 0xd044 irq 49'
 Mixer name : 'ATI R6xx HDMI'
 Components : 'HDA:1002aa01,00aa0100,00100200'
 Controls  : 6
 Simple ctrls  : 1
  Card1.Amixer.values:
   Simple mixer control 'IEC958',0
 Capabilities: pswitch pswitch-joined penum
 Playback channels: Mono
 Mono: Playback [on]
  Date: Mon Feb  4 21:53:10 2013
  HibernationDevice: RESUME=UUID=2850be5d-9902-4a6d-8e97-3f9d34028e02
  InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 
(20120823.1)
  MachineType: Apple Inc. iMac11,3
  MarkForUpload: True
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-37-generic 
root=UUID=83592388-7d5b-432f-94fe-74542604df39 ro acpi_osi=Linux quiet splash 
vt.handoff=7
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory 
/home/carkaci not ours.
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-3.2.0-37-generic N/A
   linux-backports-modules-3.2.0-37-generic  N/A
   linux-firmware1.79.1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/03/10
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: IM112.88Z.0057.B00.1005031455
  dmi.board.name: Mac-F2238BAE
  dmi.board.vendor: Apple Inc.
  dmi.board.version: iMac11,3
  dmi.chassis.type: 13
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-F2238BAE
  dmi.modalias: 
dmi:bvnAppleInc.:bvrIM112.88Z.0057.B00.1005031455:bd05/03/10:svnAppleInc.:pniMac11,3:pvr1.0:rvnAppleInc.:rnMac-F2238BAE:rvriMac11,3:cvnAppleInc.:ct13:cvrMac-F2238BAE:
  dmi.product.name: iMac11,3
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.

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

2015-11-03 Thread Brad Figg
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/1512691

Title:
  [Macbook Pro] Backlight control does not work, but there are entries
  in /sys/class/backlight

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Backlight control stopped working after upgrade from Vivid to Wily.

  Macbook Pro 11,3 with nouveau.

  /sys/class/backlight/gmux_backlight$ grep . *
  actual_brightness:16777215
  bl_power:0
  brightness:400
  grep: device: Is a directory
  max_brightness:-1
  grep: power: Is a directory
  grep: subsystem: Is a directory
  type:platform

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

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: linux-image-4.2.0-16-generic 4.2.0-16.19
  ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3
  Uname: Linux 4.2.0-16-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.19.1-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  gaele  2525 F pulseaudio
   /dev/snd/controlC0:  gaele  2525 F pulseaudio
  CurrentDesktop: Unity
  Date: Tue Nov  3 13:44:25 2015
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=716bc023-ef4e-436e-8e5b-5a1f548faef8
  InstallationDate: Installed on 2015-04-26 (190 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  MachineType: Apple Inc. MacBookPro11,3
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-16-generic.efi.signed 
root=UUID=38c8fe6d-3763-4619-a710-f65494173fe4 ro quiet splash 
libata.force=noncq vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.2.0-16-generic N/A
   linux-backports-modules-4.2.0-16-generic  N/A
   linux-firmware1.149
  SourcePackage: linux
  UpgradeStatus: Upgraded to wily on 2015-10-22 (11 days ago)
  dmi.bios.date: 06/05/2015
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: MBP112.88Z.0138.B15.1506050548
  dmi.board.asset.tag: Base Board Asset Tag#
  dmi.board.name: Mac-2BD1B31983FE1663
  dmi.board.vendor: Apple Inc.
  dmi.board.version: MacBookPro11,3
  dmi.chassis.type: 10
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-2BD1B31983FE1663
  dmi.modalias: 
dmi:bvnAppleInc.:bvrMBP112.88Z.0138.B15.1506050548:bd06/05/2015:svnAppleInc.:pnMacBookPro11,3:pvr1.0:rvnAppleInc.:rnMac-2BD1B31983FE1663:rvrMacBookPro11,3:cvnAppleInc.:ct10:cvrMac-2BD1B31983FE1663:
  dmi.product.name: MacBookPro11,3
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1512691/+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 123920] Re: Bluetooth Logitech Dinovo Keyboard/Mouse don't work

2015-11-03 Thread Daniel Beauyat
The solution from Dhanish Patel solved my problem with Logitech Cordless MX 
5500 on Ubuntu 15.10 Wily Werewolf!
I have keyboard/mouse combo from Logitech named Logitech Cordless MX 
(Revolution) 5500; this combo has 1 bluetooth dongle to receive input from both 
mouse and keyboard.

I was using it without problem on Ubuntu 14.04 LTS.
I just switched to Ubuntu 15.10 and keyboard/mouse do not work at all!!! After 
some search, I found this webpage and tried that solution:
Change: KERNEL=="hiddev*"
To: KERNEL=="hidraw*"
After reboot, MX 5500 Wireless keyb/mouse combo now works on Wily Werewolf.

On 15.10 Wily Werewolf though, the path to the modified file is:
/lib/udev/rules.d/97-hid2hci.rules

I modified line 14:
From: KERNEL=="hiddev*", ATTRS{idVendor}=="046d", 
ATTRS{idProduct}=="c70[345abce]|c71[3bc]", \
To: KERNEL=="hidraw*", ATTRS{idVendor}=="046d", 
ATTRS{idProduct}=="c70[345abce]|c71[3bc]", \

Thanks for sharing the solution :)

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

Title:
  Bluetooth Logitech Dinovo Keyboard/Mouse don't work

Status in Bluez Utilities:
  New
Status in Bluez-utils:
  New
Status in Linux Mint:
  Invalid
Status in Unity:
  Invalid
Status in bluez package in Ubuntu:
  Triaged
Status in linux package in Ubuntu:
  Invalid
Status in linux-source-2.6.22 package in Ubuntu:
  Won't Fix
Status in udev package in Ubuntu:
  Invalid

Bug description:
  Testing Gutsy Gibbon Tribe 2 LiveCD and bluetooth keyboard and mouse will 
work until Nautilus starts.  After Nautilus starts the keyboard and mouse are 
unresponsive and do not work.
  I tried reconnecting the keyboard and mouse by using the discovery buttons on 
both the Bluetooth Dongle and Input device.  The problem still persists.
  Using Intel P4 2.8 Ghz Processor, 3 GB ddr400 ram, Intel D875PBZ motherboard. 
 Logitech Dinovo media keyboard and mx1000 laser bluetooth mouse, with logitech 
mini bluetooth receiver.

To manage notifications about this bug go to:
https://bugs.launchpad.net/bluez/+bug/123920/+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 1512691] Re: [Macbook Pro] Backlight control does not work, but there are entries in /sys/class/backlight

2015-11-03 Thread Joseph Salisbury
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.3 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.3-unstable/


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

** Tags added: needs-bisect regression-release

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

Title:
  [Macbook Pro] Backlight control does not work, but there are entries
  in /sys/class/backlight

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Backlight control stopped working after upgrade from Vivid to Wily.

  Macbook Pro 11,3 with nouveau.

  /sys/class/backlight/gmux_backlight$ grep . *
  actual_brightness:16777215
  bl_power:0
  brightness:400
  grep: device: Is a directory
  max_brightness:-1
  grep: power: Is a directory
  grep: subsystem: Is a directory
  type:platform

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

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: linux-image-4.2.0-16-generic 4.2.0-16.19
  ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3
  Uname: Linux 4.2.0-16-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.19.1-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  gaele  2525 F pulseaudio
   /dev/snd/controlC0:  gaele  2525 F pulseaudio
  CurrentDesktop: Unity
  Date: Tue Nov  3 13:44:25 2015
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=716bc023-ef4e-436e-8e5b-5a1f548faef8
  InstallationDate: Installed on 2015-04-26 (190 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  MachineType: Apple Inc. MacBookPro11,3
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-16-generic.efi.signed 
root=UUID=38c8fe6d-3763-4619-a710-f65494173fe4 ro quiet splash 
libata.force=noncq vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.2.0-16-generic N/A
   linux-backports-modules-4.2.0-16-generic  N/A
   linux-firmware1.149
  SourcePackage: linux
  UpgradeStatus: Upgraded to wily on 2015-10-22 (11 days ago)
  dmi.bios.date: 06/05/2015
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: MBP112.88Z.0138.B15.1506050548
  dmi.board.asset.tag: Base Board Asset Tag#
  dmi.board.name: Mac-2BD1B31983FE1663
  dmi.board.vendor: Apple Inc.
  dmi.board.version: MacBookPro11,3
  dmi.chassis.type: 10
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-2BD1B31983FE1663
  dmi.modalias: 
dmi:bvnAppleInc.:bvrMBP112.88Z.0138.B15.1506050548:bd06/05/2015:svnAppleInc.:pnMacBookPro11,3:pvr1.0:rvnAppleInc.:rnMac-2BD1B31983FE1663:rvrMacBookPro11,3:cvnAppleInc.:ct10:cvrMac-2BD1B31983FE1663:
  dmi.product.name: MacBookPro11,3
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1512691/+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 1512406] Re: Green Screen instead of video stream

2015-11-03 Thread Joseph Salisbury
This issue appears to be an upstream bug, since you tested the latest
upstream kernel. Would it be possible for you to open an upstream bug
report[0]? That will allow the upstream Developers to examine the issue,
and may provide a quicker resolution to the bug.

Please follow the instructions on the wiki page[0]. The first step is to
email the appropriate mailing list. If no response is received, then a
bug may be opened on bugzilla.kernel.org.

Once this bug is reported upstream, please add the tag: 'kernel-bug-
reported-upstream'.

[0] https://wiki.ubuntu.com/Bugs/Upstream/kernel


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

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

Title:
  Green Screen instead of video stream

Status in linux package in Ubuntu:
  Triaged

Bug description:
  I found that in some software, e.g. gnome-sushi, cheese,  etc. video stream 
is malfunctioning.
  Due to this bug, the output of video is shown as a simple green screen, but 
the audio is fine.
  Here you can check the gnome-sushi bug I submitted earlier: 
https://bugs.launchpad.net/ubuntu/+source/gnome-sushi/+bug/1512316
  I attached a screenshot and some files dumped by apport from cheese, to this 
issue.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: cheese 3.16.1-1ubuntu2
  ProcVersionSignature: Ubuntu 4.2.0-17.21-generic 4.2.3
  Uname: Linux 4.2.0-17-generic x86_64
  ApportVersion: 2.19.2-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Nov  2 19:33:34 2015
  InstallationDate: Installed on 2015-04-24 (192 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  MachineType: LENOVO 2349KEG
  RelatedPackageVersions:
   cheese3.16.1-1ubuntu2
   cheese-common 3.16.1-1ubuntu2
  SourcePackage: linux
  UpgradeStatus: Upgraded to xenial on 2015-11-01 (0 days ago)
  dmi.bios.date: 09/04/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G1ET97WW (2.57 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 2349KEG
  dmi.board.vendor: LENOVO
  dmi.board.version: Win8 Pro DPK TPG
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrG1ET97WW(2.57):bd09/04/2013:svnLENOVO:pn2349KEG:pvrThinkPadT430:rvnLENOVO:rn2349KEG:rvrWin8ProDPKTPG:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 2349KEG
  dmi.product.version: ThinkPad T430
  dmi.sys.vendor: LENOVO
  --- 
  ApportVersion: 2.19.2-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  danialbehzadi   2545 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=8c26a350-8c96-4961-957e-050eaa9b36ea
  InstallationDate: Installed on 2015-04-24 (192 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  MachineType: LENOVO 2349KEG
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-17-generic 
root=UUID=a1abeb16-2852-43c8-8d5b-330faa072bf8 ro ipv6.disable=1 quiet splash 
vt.handoff=7
  ProcVersionSignature: Ubuntu 4.2.0-17.21-generic 4.2.3
  RelatedPackageVersions:
   linux-restricted-modules-4.2.0-17-generic N/A
   linux-backports-modules-4.2.0-17-generic  N/A
   linux-firmware1.152
  Tags:  xenial
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  Uname: Linux 4.2.0-17-generic x86_64
  UpgradeStatus: Upgraded to xenial on 2015-11-01 (0 days ago)
  UserGroups: adm cdrom dip disk libvirtd lpadmin plugdev sambashare sudo 
vboxusers
  _MarkForUpload: True
  dmi.bios.date: 09/04/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G1ET97WW (2.57 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 2349KEG
  dmi.board.vendor: LENOVO
  dmi.board.version: Win8 Pro DPK TPG
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrG1ET97WW(2.57):bd09/04/2013:svnLENOVO:pn2349KEG:pvrThinkPadT430:rvnLENOVO:rn2349KEG:rvrWin8ProDPKTPG:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 2349KEG
  dmi.product.version: ThinkPad T430
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1512406/+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 1509776] Re: xubuntu 15.10 synaptics ps2 touchpad mouse cursor jumps

2015-11-03 Thread liontamer
** 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/1509776

Title:
  xubuntu 15.10 synaptics ps2 touchpad mouse cursor jumps

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  running live xubuntu 15.10 from usb stick.  Synaptics ps2 touchpad configured 
to act as simple mouse.  Mouse cursor suddenly and frequently jumps to screen 
edge with no reason.  Problem not present in 15.04 with same touchpad 
configuration but has occurred in some earlier versions.  Not prepared to 
upgrade as touchpad practically unusable.
  --- 
  ApportVersion: 2.19.1-0ubuntu3
  Architecture: amd64
  CasperVersion: 1.365
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: XFCE
  DistUpgraded: Fresh install
  DistroCodename: wily
  DistroRelease: Ubuntu 15.10
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation 4th Gen Core Processor Integrated Graphics Controller 
[8086:0416] (rev 06) (prog-if 00 [VGA controller])
 Subsystem: Pegatron Device [1b0a:2109]
 Subsystem: Pegatron Device [1b0a:2109]
  LiveMediaBuild: Xubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  MachineType: Novatech Ltd. Novatech 15.6 NSPIRE Laptop
  Package: xorg 1:7.7+7ubuntu4
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi initrd=/casper/initrd.lz 
file=/cdrom/preseed/username.seed boot=casper  quiet splash --- persistent
  ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3
  Tags:  wily ubuntu
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  Uname: Linux 4.2.0-16-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/05/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: C15B.610
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: C15B
  dmi.board.vendor: Novatech Ltd.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Novatech Ltd.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrC15B.610:bd12/05/2013:svnNovatechLtd.:pnNovatech15.6NSPIRELaptop:pvr1.0:rvnNovatechLtd.:rnC15B:rvr1.0:cvnNovatechLtd.:ct10:cvr1.0:
  dmi.product.name: Novatech 15.6 NSPIRE Laptop
  dmi.product.version: 1.0
  dmi.sys.vendor: Novatech Ltd.
  version.compiz: compiz N/A
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.64-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.0.2-1ubuntu4
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.0.2-1ubuntu4
  version.xserver-xorg-core: xserver-xorg-core 2:1.17.2-1ubuntu9
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.2-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 
1:7.5.0+git20150819-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20150808-0ubuntu4
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.11-1ubuntu3
  xserver.bootTime: Mon Nov  2 10:44:16 2015
  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)
   NOUVEAU(G0): Failed to initialise context object: 2D_NVC0 (0)
   NOUVEAU(G0): Error initialising acceleration.  Falling back to NoAccel
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id   18412 
   vendor AUO
  xserver.version: 2:1.17.2-1ubuntu9

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1509776/+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 1510125] Re: occasionally loses external monitor

2015-11-03 Thread Joe Barnett
Still happens on 4.3 mainline.  It's happened on every kernel I've used
on this machine, and feels related to bug #1493989 , though may not be.

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

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

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

Title:
  occasionally loses external monitor

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Occasionally the screen will blank and all windows move from the
  external monitor to the laptop monitor.  Relatively immediately
  afterward both screens re-enable, but the windows don't move back to
  the external monitor.

  This usually appears to be triggered by a specific application, eg,
  "ScudCloud" (a slack client that embeds an HTML webkit view), or
  enabling the flash plugin in an existing firefox window.

  dmesg shows:
  [  174.404713] [ cut here ]
  [  174.404736] WARNING: CPU: 0 PID: 1699 at 
/build/linux-AxjFAn/linux-4.2.0/drivers/gpu/drm/i915/i915_gem.c:5269 
i915_gem_track_fb+0x129/0x140 [i915]()
  [  174.404738] WARN_ON(!(old->frontbuffer_bits & frontbuffer_bits))
  [  174.404739] Modules linked in:
  [  174.404741]  bnep pci_stub vboxpci(OE) vboxnetadp(OE) vboxnetflt(OE) 
vboxdrv(OE) asix usbnet mii xt_addrtype xt_conntrack ipt_MASQUERADE 
nf_nat_masquerade_ipv4 iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 
iptable_filter ip_tables x_tables nf_nat nf_conntrack bridge stp llc aufs 
nls_iso8859_1 applesmc input_polldev uvcvideo videobuf2_vmalloc 
videobuf2_memops videobuf2_core v4l2_common videodev media btusb btrtl btbcm 
btintel bluetooth snd_usb_audio snd_usbmidi_lib joydev input_leds bcm5974 
snd_hda_codec_hdmi x86_pkg_temp_thermal intel_powerclamp coretemp 
snd_hda_codec_cirrus kvm_intel snd_hda_codec_generic kvm snd_seq_midi 
snd_seq_midi_event brcmfmac snd_hda_intel brcmutil snd_hda_codec snd_hda_core 
cfg80211 snd_hwdep snd_rawmidi bdc_pci lpc_ich snd_pcm mei_me snd_seq mei 
snd_seq_device
  [  174.404776]  snd_timer thunderbolt snd sbs soundcore acpi_als kfifo_buf 
shpchp sbshc industrialio apple_gmux mac_hid apple_bl parport_pc ppdev lp 
parport autofs4 jitterentropy_rng drbg ansi_cprng algif_skcipher af_alg 
dm_crypt hid_plantronics hid_microsoft hid_logitech_hidpp hid_generic 
hid_logitech_dj hid_apple usbhid hid crct10dif_pclmul crc32_pclmul i915 
ghash_clmulni_intel aesni_intel aes_x86_64 lrw gf128mul glue_helper ablk_helper 
i2c_algo_bit uas cryptd drm_kms_helper usb_storage drm ahci libahci video
  [  174.404803] CPU: 0 PID: 1699 Comm: gnome-shell Tainted: G   OE   
4.2.0-16-generic #19-Ubuntu
  [  174.404804] Hardware name: Apple Inc. MacBookPro11,4/Mac-06F11FD93F0323C5, 
BIOS MBP114.88Z.0172.B04.1506051511 06/05/2015
  [  174.404806]   5f8a407a 8804613eba28 
817e8c09
  [  174.404808]   8804613eba80 8804613eba68 
8107b3c6
  [  174.404811]  880465a3 0001 88046756e640 
8804658558c0
  [  174.404813] Call Trace:
  [  174.404818]  [] dump_stack+0x45/0x57
  [  174.404823]  [] warn_slowpath_common+0x86/0xc0
  [  174.404825]  [] warn_slowpath_fmt+0x55/0x70
  [  174.404836]  [] i915_gem_track_fb+0x129/0x140 [i915]
  [  174.404852]  [] intel_prepare_plane_fb+0xe7/0x1a0 [i915]
  [  174.404859]  [] 
drm_atomic_helper_prepare_planes+0x59/0xe0 [drm_kms_helper]
  [  174.404872]  [] __intel_set_mode+0x1ae/0xb60 [i915]
  [  174.404886]  [] intel_crtc_set_config+0x2b6/0x580 [i915]
  [  174.404899]  [] ? drm_mode_create+0x25/0x60 [drm]
  [  174.404908]  [] drm_mode_set_config_internal+0x66/0x100 
[drm]
  [  174.404917]  [] drm_mode_setcrtc+0x3e9/0x500 [drm]
  [  174.404923]  [] drm_ioctl+0x125/0x610 [drm]
  [  174.404930]  [] ? drm_mode_setplane+0x1b0/0x1b0 [drm]
  [  174.404934]  [] do_vfs_ioctl+0x295/0x480
  [  174.404936]  [] SyS_ioctl+0x79/0x90
  [  174.404939]  [] entry_SYSCALL_64_fastpath+0x16/0x75
  [  174.404941] ---[ end trace fc649a1af1173285 ]---
  [  175.018549] snd_hda_codec_hdmi hdaudioC0D0: HDMI: ELD buf size is 0, force 
128
  [  175.018587] snd_hda_codec_hdmi hdaudioC0D0: HDMI: invalid ELD data byte 0
  [  175.184359] thunderbolt :07:00.0: resetting error on 0:c.
  [  175.184396] thunderbolt :07:00.0: 0:c: hotplug: scanning
  [  175.184400] thunderbolt :07:00.0: 0:c: hotplug: no switch found
  [  176.225350] thunderbolt :07:00.0: resetting error on 0:c.
  [  176.225389] thunderbolt :07:00.0: 0:c: got unplug event for 
disconnected port, ignoring
  [  181.480150] usb 1-1.3.1: reset high-speed USB device number 10 using 
xhci_hcd
  [  581.943528] usb 1-1.3.1: reset high-speed USB device number 10 using 
xhci_hcd

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: linux-image-4.2.0-16-generic 4.2.0-16.19
  ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3
  Uname: Linux 

[Kernel-packages] [Bug 1492146] Re: igb Detected Tx Unit Hang

2015-11-03 Thread Joseph Salisbury
The commits that caused this bug were introduced by the fixes for bug
1454892.

I've created a new test kernel for bug 1454892, but I would like to
ensure it does not introduce this regression again.  Could folks
affected by this bug test my new test kernel?  It can be downloaded
from:

http://kernel.ubuntu.com/~jsalisbury/lp1454892/lts-backport-utopic/

Note, with this test kernel you would need to install both the linux-
image and linux-image-extra .deb packages.

Thanks in advance!

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

Title:
  igb Detected Tx Unit Hang

Status in linux-lts-utopic package in Ubuntu:
  Confirmed
Status in linux-lts-utopic source package in Trusty:
  Fix Released

Bug description:
  Hello!

  Have a:

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

  with kenel 3.16.0-46-generic.

  Today i do dist-upgrade and kernel was upgraded to 3.16.0-48-generic
  version.

  After reboot i've got this:

  Sep  4 09:02:52 mail kernel: [  310.616324] igb :02:00.0 em1: Reset 
adapter Sep  4 09:02:52 mail kernel: [  310.831157] igb :02:00.1 em2: Reset 
adapter Sep  4 09:02:56 mail kernel: [  315.154686] igb :02:00.0 em1: igb: 
em1 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX Sep  4 09:02:56 mail 
kernel: [  315.202651] igb :02:00.1 em2: igb: em2 NIC Link is Up 1000 Mbps 
Full Duplex, Flow Control: RX Sep  4 09:03:02 mail kernel: [  321.608099] igb 
:02:00.0: Detected Tx Unit Hang
  Sep  4 09:03:02 mail kernel: [  321.608099]   Tx Queue <6>
  Sep  4 09:03:02 mail kernel: [  321.608099]   TDH  <23>
  Sep  4 09:03:02 mail kernel: [  321.608099]   TDT  <23>
  Sep  4 09:03:02 mail kernel: [  321.608099]   next_to_use  <25>
  Sep  4 09:03:02 mail kernel: [  321.608099]   next_to_clean<23>
  Sep  4 09:03:02 mail kernel: [  321.608099] buffer_info[next_to_clean]
  Sep  4 09:03:02 mail kernel: [  321.608099]   time_stamp   <112af>
  Sep  4 09:03:02 mail kernel: [  321.608099]   next_to_watch

  Sep  4 09:03:02 mail kernel: [  321.608099]   jiffies  <11531>
  Sep  4 09:03:02 mail kernel: [  321.608099]   desc.status  <120200>
  Sep  4 09:03:04 mail kernel: [  323.607349] igb :02:00.0: Detected Tx 
Unit Hang
  Sep  4 09:03:04 mail kernel: [  323.607349]   Tx Queue <6>
  Sep  4 09:03:04 mail kernel: [  323.607349]   TDH  <23>
  Sep  4 09:03:04 mail kernel: [  323.607349]   TDT  <23>
  Sep  4 09:03:04 mail kernel: [  323.607349]   next_to_use  <25>
  Sep  4 09:03:04 mail kernel: [  323.607349]   next_to_clean<23>
  Sep  4 09:03:04 mail kernel: [  323.607349] buffer_info[next_to_clean]
  Sep  4 09:03:04 mail kernel: [  323.607349]   time_stamp   <112af>
  Sep  4 09:03:04 mail kernel: [  323.607349]   next_to_watch

  Sep  4 09:03:04 mail kernel: [  323.607349]   jiffies  <11725>
  Sep  4 09:03:04 mail kernel: [  323.607349]   desc.status  <120200>
  Sep  4 09:03:06 mail kernel: [  325.606602] igb :02:00.0: Detected Tx 
Unit Hang
  Sep  4 09:03:06 mail kernel: [  325.606602]   Tx Queue <6>
  Sep  4 09:03:06 mail kernel: [  325.606602]   TDH  <23>
  Sep  4 09:03:06 mail kernel: [  325.606602]   TDT  <23>
  Sep  4 09:03:06 mail kernel: [  325.606602]   next_to_use  <25>
  Sep  4 09:03:06 mail kernel: [  325.606602]   next_to_clean<23>
  Sep  4 09:03:06 mail kernel: [  325.606602] buffer_info[next_to_clean]
  Sep  4 09:03:06 mail kernel: [  325.606602]   time_stamp   <112af>
  Sep  4 09:03:06 mail kernel: [  325.606602]   next_to_watch

  Sep  4 09:03:06 mail kernel: [  325.606602]   jiffies  <11919>
  Sep  4 09:03:06 mail kernel: [  325.606602]   desc.status  <120200>

  All network connections droped after that. System still unusable.

  Only after boot with old linux-image-3.16.0-46-generic my production
  mail server can work.

  It's a critical bug for me, can anybody help me?

  ethtool -i em1
  driver: igb
  version: 5.2.13-k
  firmware-version: 1.61, 0x8cd5, 1.949.0
  bus-info: :02:00.0
  supports-statistics: yes
  supports-test: yes
  supports-eeprom-access: yes
  supports-register-dump: yes
  supports-priv-flags: no

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-lts-utopic/+bug/1492146/+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 1491957] Re: 3.16.0.48 kernel in hyper-v cause hv_netvsc problem

2015-11-03 Thread Joseph Salisbury
The commits that caused this bug were introduced by the fixes for bug
1454892.

I've created a new test kernel for bug 1454892, but I would like to
ensure it does not introduce this regression again.  Could folks
affected by this bug test my new test kernel?  It can be downloaded
from:

http://kernel.ubuntu.com/~jsalisbury/lp1454892/lts-backport-utopic/

Note, with this test kernel you would need to install both the linux-
image and linux-image-extra .deb packages.

Thanks in advance!

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

Title:
  3.16.0.48 kernel in hyper-v cause hv_netvsc problem

Status in linux-lts-utopic package in Ubuntu:
  Fix Released
Status in linux-lts-utopic source package in Trusty:
  Fix Released

Bug description:
  I have an Ubuntu 14.04 LTS in Hyper-V. It works well. Today I apt
  upgrade the kernel from 3.16.0.46 to 3.16.0.48 and after reboot, I
  have network connection problems, and have a lot of error message on
  screen like the above ones.

  Sep  3 18:48:07 RailGun kernel: [   71.437967] hv_netvsc vmbus_0_16 eth0: 
unable to send receive completion pkt (tid 2068)...retrying 4
  Sep  3 18:48:07 RailGun kernel: [   71.438276] hv_netvsc vmbus_0_16 eth0: 
unable to send receive completion pkt (tid 2068)...give up retrying
  Sep  3 18:48:07 RailGun kernel: [   71.438596] hv_netvsc vmbus_0_16 eth0: 
unable to send receive completion pkt (tid 2069)...retrying 1
  Sep  3 18:48:07 RailGun kernel: [   71.439016] hv_netvsc vmbus_0_16 eth0: 
unable to send receive completion pkt (tid 2069)...retrying 2
  Sep  3 18:48:07 RailGun kernel: [   71.439434] hv_netvsc vmbus_0_16 eth0: 
unable to send receive completion pkt (tid 2069)...retrying 3
  Sep  3 18:48:07 RailGun kernel: [   71.439847] hv_netvsc vmbus_0_16 eth0: 
unable to send receive completion pkt (tid 2069)...retrying 4
  Sep  3 18:48:07 RailGun kernel: [   71.440155] hv_netvsc vmbus_0_16 eth0: 
unable to send receive completion pkt (tid 2069)...give up retrying
  Sep  3 18:48:07 RailGun kernel: [   71.465593] hv_netvsc vmbus_0_16 eth0: 
unable to send receive completion pkt (tid 206a)...retrying 1
  Sep  3 18:48:07 RailGun kernel: [   71.466165] hv_netvsc vmbus_0_16 eth0: 
unable to send receive completion pkt (tid 206a)...retrying 2
  Sep  3 18:48:07 RailGun kernel: [   71.466827] hv_netvsc vmbus_0_16 eth0: 
unable to send receive completion pkt (tid 206a)...retrying 3
  Sep  3 18:48:07 RailGun kernel: [   71.467508] hv_netvsc vmbus_0_16 eth0: 
unable to send receive completion pkt (tid 206a)...retrying 4
  Sep  3 18:48:07 RailGun kernel: [   71.468056] hv_netvsc vmbus_0_16 eth0: 
unable to send receive completion pkt (tid 206a)...give up retrying
  Sep  3 18:48:07 RailGun kernel: [   71.474507] hv_netvsc vmbus_0_16 eth0: 
unable to send receive completion pkt (tid 206b)...retrying 1
  Sep  3 18:48:07 RailGun kernel: [   71.474998] hv_netvsc vmbus_0_16 eth0: 
unable to send receive completion pkt (tid 206b)...retrying 2
  Sep  3 18:48:07 RailGun kernel: [   71.475419] hv_netvsc vmbus_0_16 eth0: 
unable to send receive completion pkt (tid 206b)...retrying 3
  Sep  3 18:48:07 RailGun kernel: [   71.475833] hv_netvsc vmbus_0_16 eth0: 
unable to send receive completion pkt (tid 206b)...retrying 4
  Sep  3 18:48:07 RailGun kernel: [   71.476145] hv_netvsc vmbus_0_16 eth0: 
unable to send receive completion pkt (tid 206b)...give up retrying
  Sep  3 18:48:07 RailGun kernel: [   71.483356] hv_netvsc vmbus_0_16 eth0: 
unable to send receive completion pkt (tid 206c)...retrying 1
  Sep  3 18:48:07 RailGun kernel: [   71.483823] hv_netvsc vmbus_0_16 eth0: 
unable to send receive completion pkt (tid 206c)...retrying 2
  Sep  3 18:48:07 RailGun kernel: [   71.484266] hv_netvsc vmbus_0_16 eth0: 
unable to send receive completion pkt (tid 206c)...retrying 3
  Sep  3 18:48:07 RailGun kernel: [   71.484683] hv_netvsc vmbus_0_16 eth0: 
unable to send receive completion pkt (tid 206c)...retrying 4
  Sep  3 18:48:07 RailGun kernel: [   71.484993] hv_netvsc vmbus_0_16 eth0: 
unable to send receive completion pkt (tid 206c)...give up retrying
  Sep  3 18:48:07 RailGun kernel: [   71.491738] hv_netvsc vmbus_0_16 eth0: 
unable to send receive completion pkt (tid 206d)...retrying 1
  Sep  3 18:48:07 RailGun kernel: [   71.492223] hv_netvsc vmbus_0_16 eth0: 
unable to send receive completion pkt (tid 206d)...retrying 2
  Sep  3 18:48:07 RailGun kernel: [   71.492645] hv_netvsc vmbus_0_16 eth0: 
unable to send receive completion pkt (tid 206d)...retrying 3
  Sep  3 18:48:07 RailGun kernel: [   71.493060] hv_netvsc vmbus_0_16 eth0: 
unable to send receive completion pkt (tid 206d)...retrying 4
  Sep  3 18:48:07 RailGun kernel: [   71.493369] hv_netvsc vmbus_0_16 eth0: 
unable to send receive completion pkt (tid 206d)...give up retrying
  Sep  3 18:48:07 RailGun kernel: [   71.493689] hv_netvsc vmbus_0_16 eth0: 
unable to send 

[Kernel-packages] [Bug 1512815] Re: read() from pty doesn't finish.

2015-11-03 Thread Joseph Salisbury
** Changed in: linux (Ubuntu)
   Importance: Undecided => Medium

** Tags added: kernel-da-key needs-bisect trusty vivid wily

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

** Changed in: linux (Ubuntu)
 Assignee: (unassigned) => Joseph Salisbury (jsalisbury)

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

Title:
  read() from pty doesn't finish.

Status in linux package in Ubuntu:
  In Progress

Bug description:
  It has been brought to my attention

  By the attached test program pty, a pair of process repeats writing
  and reading only '\n' to a master pseudoterminal device (/dev/ptmx)
  and a slave pseudoterminal device (/dev/pts/N) each. When we carry out
  the following 30 pairs 10,000 times, in a pair each process doesn't
  finish reading.

  $ pty 30
  The following message will be usually indicated immediately.
  #name copy num/sec usec/num
  pty_switch 30 1541842 0.648575

  When a message wasn't indicated any more, we got the attached dump file. 
  A kernel was 3.13.0-45.74. 
  A system was Ubuntu 14.04 LTS.

  The same problem occurred in case of 3.13.0-55.92 kernel and the following 
kernel have been tested as well:
  2.6.32, 3.10: not reproduces.
  3.19, 4.0.0, 4.1.3: reproduces.

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

2015-11-03 Thread Brad Figg
This bug is missing log files that will aid in diagnosing the problem.
>From a terminal window please run:

apport-collect 1512848

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

Title:
  Radeon VCE Init Error

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Since upgrading to Ubuntu 15.10, I have encountered graphics
  performance issues, and have occasionally experienced lockups during
  boot.

  dmesg | grep radeon
  [2.103294] [drm] radeon kernel modesetting enabled.
  [2.114677] radeon :01:00.0: enabling device ( -> 0003)
  [2.226348] radeon :01:00.0: VRAM: 1024M 0x - 
0x3FFF (1024M used)
  [2.226349] radeon :01:00.0: GTT: 2048M 0x4000 - 
0xBFFF
  [2.226494] [drm] radeon: 1024M of VRAM memory ready
  [2.226506] [drm] radeon: 2048M of GTT memory ready.
  [2.232296] [drm] radeon: dpm initialized
  [2.234760] [drm] enabling PCIE gen 3 link speeds, disable with 
radeon.pcie_gen2=0
  [3.456910] radeon :01:00.0: WB enabled
  [3.456912] radeon :01:00.0: fence driver on ring 0 use gpu addr 
0x4c00 and cpu addr 0x88041663ac00
  [3.456914] radeon :01:00.0: fence driver on ring 1 use gpu addr 
0x4c04 and cpu addr 0x88041663ac04
  [3.456915] radeon :01:00.0: fence driver on ring 2 use gpu addr 
0x4c08 and cpu addr 0x88041663ac08
  [3.456916] radeon :01:00.0: fence driver on ring 3 use gpu addr 
0x4c0c and cpu addr 0x88041663ac0c
  [3.456918] radeon :01:00.0: fence driver on ring 4 use gpu addr 
0x4c10 and cpu addr 0x88041663ac10
  [3.457696] radeon :01:00.0: fence driver on ring 5 use gpu addr 
0x00075a18 and cpu addr 0xc90002035a18
  [3.558371] radeon :01:00.0: VCE init error (-110).
  [3.558376] radeon :01:00.0: radeon: MSI limited to 32-bit
  [3.558397] radeon :01:00.0: radeon: using MSI.
  [3.558421] [drm] radeon: irq initialized.
  [4.538452] radeon :01:00.0: No connectors reported connected with 
modes
  [4.539564] radeon :01:00.0: fb1: radeondrmfb frame buffer device
  [4.539598] [drm] Initialized radeon 2.43.0 20080528 for :01:00.0 on 
minor 1
  [   11.629124] [drm] enabling PCIE gen 3 link speeds, disable with 
radeon.pcie_gen2=0
  [   12.627048] radeon :01:00.0: WB enabled
  [   12.627050] radeon :01:00.0: fence driver on ring 0 use gpu addr 
0x4c00 and cpu addr 0x88041663ac00
  [   12.627051] radeon :01:00.0: fence driver on ring 1 use gpu addr 
0x4c04 and cpu addr 0x88041663ac04
  [   12.627053] radeon :01:00.0: fence driver on ring 2 use gpu addr 
0x4c08 and cpu addr 0x88041663ac08
  [   12.627054] radeon :01:00.0: fence driver on ring 3 use gpu addr 
0x4c0c and cpu addr 0x88041663ac0c
  [   12.627055] radeon :01:00.0: fence driver on ring 4 use gpu addr 
0x4c10 and cpu addr 0x88041663ac10
  [   12.627838] radeon :01:00.0: fence driver on ring 5 use gpu addr 
0x00075a18 and cpu addr 0xc90002035a18
  [   12.728529] radeon :01:00.0: VCE init error (-110).

  
  xrandr --listproviders
  Providers: number : 3
  Provider 0: id: 0x6a cap: 0x9, Source Output, Sink Offload crtcs: 4 outputs: 
5 associated providers: 2 name:Intel
  Provider 1: id: 0x41 cap: 0x6, Sink Output, Source Offload crtcs: 2 outputs: 
0 associated providers: 2 name:radeon
  Provider 2: id: 0x41 cap: 0x6, Sink Output, Source Offload crtcs: 2 outputs: 
0 associated providers: 2 name:radeon

  
  lspci -k 
  00:00.0 Host bridge: Intel Corporation 3rd Gen Core processor DRAM Controller 
(rev 09)
  Subsystem: Samsung Electronics Co Ltd Device c0e6
  Kernel driver in use: ivb_uncore
  00:01.0 PCI bridge: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor 
PCI Express Root Port (rev 09)
  Kernel driver in use: pcieport
  00:02.0 VGA compatible controller: Intel Corporation 3rd Gen Core processor 
Graphics Controller (rev 09)
  DeviceName:  Onboard IGD
  Subsystem: Samsung Electronics Co Ltd Device c0e6
  Kernel driver in use: i915
  01:00.0 Display controller: Advanced Micro Devices, Inc. [AMD/ATI] Mars 
[Radeon HD 8670A/8670M/8750M] (rev ff)
  Kernel driver in use: radeon

  
  Possible upstream Debian bug: 
  

[Kernel-packages] [Bug 1512815] Re: 14.04: read() from pty doesn't finish.

2015-11-03 Thread Eric Desrochers
This is a reproducer for the stall problem in drivers/tty/n_tty.c

To reproduce the problem, save the program below as pty.c, compile it,
and run it in parallel.

# cc -o pty pty.c
# for i in {1..16}; do ./pty& done; wait
The problem can be reproduced on a multi-socket server with recent CPUs.
The program always stalled during the first run when I used a server
with the following CPU.
  Intel(R) Xeon(R) CPU E5-2698 v3 @ 2.30GHz
  2-sockets x 16-cores x 2-threads

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

Title:
  14.04: read() from pty doesn't finish.

Status in linux package in Ubuntu:
  New

Bug description:
  It has been brought to my attention

  By the attached test program pty, a pair of process repeats writing
  and reading only '\n' to a master pseudoterminal device (/dev/ptmx)
  and a slave pseudoterminal device (/dev/pts/N) each. When we carry out
  the following 30 pairs 10,000 times, in a pair each process doesn't
  finish reading.

  $ pty 30
  The following message will be usually indicated immediately.
  #name copy num/sec usec/num
  pty_switch 30 1541842 0.648575

  When a message wasn't indicated any more, we got the attached dump file. 
  A kernel was 3.13.0-45.74. 
  A system was Ubuntu 14.04 LTS.

  The same problem occurred in case of 3.13.0-55.92 kernel and the following 
kernel have been tested as well:
  2.6.32, 3.10: not reproduces.
  3.19, 4.0.0, 4.1.3: reproduces.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1512815/+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 1512815] [NEW] 14.04: read() from pty doesn't finish.

2015-11-03 Thread Eric Desrochers
Public bug reported:

It has been brought to my attention

By the attached test program pty, a pair of process repeats writing and
reading only '\n' to a master pseudoterminal device (/dev/ptmx) and a
slave pseudoterminal device (/dev/pts/N) each. When we carry out the
following 30 pairs 10,000 times, in a pair each process doesn't finish
reading.

$ pty 30
The following message will be usually indicated immediately.
#name copy num/sec usec/num
pty_switch 30 1541842 0.648575

When a message wasn't indicated any more, we got the attached dump file. 
A kernel was 3.13.0-45.74. 
A system was Ubuntu 14.04 LTS.

The same problem occurred in case of 3.13.0-55.92 kernel and the following 
kernel have been tested as well:
2.6.32, 3.10: not reproduces.
3.19, 4.0.0, 4.1.3: reproduces.

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

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

Title:
  14.04: read() from pty doesn't finish.

Status in linux package in Ubuntu:
  New

Bug description:
  It has been brought to my attention

  By the attached test program pty, a pair of process repeats writing
  and reading only '\n' to a master pseudoterminal device (/dev/ptmx)
  and a slave pseudoterminal device (/dev/pts/N) each. When we carry out
  the following 30 pairs 10,000 times, in a pair each process doesn't
  finish reading.

  $ pty 30
  The following message will be usually indicated immediately.
  #name copy num/sec usec/num
  pty_switch 30 1541842 0.648575

  When a message wasn't indicated any more, we got the attached dump file. 
  A kernel was 3.13.0-45.74. 
  A system was Ubuntu 14.04 LTS.

  The same problem occurred in case of 3.13.0-55.92 kernel and the following 
kernel have been tested as well:
  2.6.32, 3.10: not reproduces.
  3.19, 4.0.0, 4.1.3: reproduces.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1512815/+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 1512815] Re: 14.04: read() from pty doesn't finish.

2015-11-03 Thread Eric Desrochers
LKML reference: 
https://lkml.org/lkml/2015/9/28/849

There is a fix applied upstream starting at v4.3-rc5

---
commit e81107d4c6bd098878af9796b24edc8d4a9524fd
Author: Kosuke Tatsukawa 
Date:   Fri Oct 2 08:27:05 2015 +

tty: fix stall caused by missing memory barrier in drivers/tty/n_tty.c
---

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

Title:
  14.04: read() from pty doesn't finish.

Status in linux package in Ubuntu:
  New

Bug description:
  It has been brought to my attention

  By the attached test program pty, a pair of process repeats writing
  and reading only '\n' to a master pseudoterminal device (/dev/ptmx)
  and a slave pseudoterminal device (/dev/pts/N) each. When we carry out
  the following 30 pairs 10,000 times, in a pair each process doesn't
  finish reading.

  $ pty 30
  The following message will be usually indicated immediately.
  #name copy num/sec usec/num
  pty_switch 30 1541842 0.648575

  When a message wasn't indicated any more, we got the attached dump file. 
  A kernel was 3.13.0-45.74. 
  A system was Ubuntu 14.04 LTS.

  The same problem occurred in case of 3.13.0-55.92 kernel and the following 
kernel have been tested as well:
  2.6.32, 3.10: not reproduces.
  3.19, 4.0.0, 4.1.3: reproduces.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1512815/+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 1512815] Re: 14.04: read() from pty doesn't finish.

2015-11-03 Thread Eric Desrochers
According to the dump a pair of process PID 7347 and 7348 were still
waiting for read() from /dev/ptmx (struct file 880c65357c00) and
/dev/pts/18 (struct file 880c65357500) respectively .

Normal behavior is as follows;
PID 7347: read(/dev/ptmx) -> write(/dev/ptmx),
PID 7348: write(/dev/pts/18) -> read(/dev/pts/18).

In the dump, PID 7348 finished writing to /dev/pts/18, and was waiting
for completion of reading, while PID 7347 continued waiting for reading
/dev/ptmx.

Though data has already arrived at /dev/ptmx, PID 7347 doesn't seem to
have been woken up while being linked to the queue of the data to be
read at tty_struct 0x88085438ac00.

- PID: 7347 TASK: 880853111800 CPU: 15 COMMAND: "pty"
#0 [88084477dc90] __schedule at 81724e19
#1 [88084477dcf8] schedule at 817252d9
#2 [88084477dd08] schedule_timeout at 81724529
#3 [88084477ddb8] n_tty_read at 8144f6a4
#4 [88084477dec0] tty_read at 8144a94d
#5 [88084477df08] vfs_read at 811bda65
#6 [88084477df40] sys_read at 811be579
#7 [88084477df80] system_call_fastpath at 8173196d
RIP: 7fb735a52290 RSP: 7fff290b4ee8 RFLAGS: 00010212
RAX:  RBX: 8173196d RCX: 10a8b550
RDX: 0001 RSI: 7fff290b51af RDI: 0023
RBP: 7fff290b51b0 R8: 7fff290b51c0 R9: 7fff290b5128
R10: 7fff290b4f60 R11: 0246 R12: 7fff290b53d0
R13: 003b R14: 0020 R15: 0010
ORIG_RAX:  CS: 0033 SS: 002b

#5 [88084477df08] vfs_read at 811bda65
88084477df10: 880c65357c00 7fff290b51af
88084477df20: 0001 
88084477df30: 001e 88084477df78
88084477df40: 811be579

- PID: 7348 TASK: 88084354c800 CPU: 4 COMMAND: "pty"
#0 [880844631c90] __schedule at 81724e19
#1 [880844631cf8] schedule at 817252d9
#2 [880844631d08] schedule_timeout at 81724529
#3 [880844631db8] n_tty_read at 8144f6a4
#4 [880844631ec0] tty_read at 8144a94d
#5 [880844631f08] vfs_read at 811bda65
#6 [880844631f40] sys_read at 811be579
#7 [880844631f80] system_call_fastpath at 8173196d
RIP: 7fb735a52290 RSP: 7fff290b4ee8 RFLAGS: 00010206
RAX:  RBX: 8173196d RCX: 7c9d4d40
RDX: 0001 RSI: 7fff290b51af RDI: 0024
RBP: 7fff290b51b0 R8: 7fff290b51c0 R9: 7fff290b5128
R10: 7fff290b4f60 R11: 0246 R12: 7fff290b53d0
R13: 003b R14: 0021 R15: 0010
ORIG_RAX:  CS: 0033 SS: 002b

#5 [880844631f08] vfs_read at 811bda65
880844631f10: 880c65357500 7fff290b51af
880844631f20: 0001 
880844631f30: 001e 880844631f78
880844631f40: 811be579

- Files opened by PID 7347 and 7348:

FD FILE DENTRY INODE TYPE PATH tty_struct n_tty_data


35 880c65357c00 88085f5dbc80 880c674e5fd8 CHR /dev/ptmx 
0x88085438ac00 0xc9001edfb000
36 880c65357500 8808460cb8c0 8808460d36c0 CHR /dev/pts/18 
0x88085438a800 0xc9001edff000

# struct file->private_data(struct tty_file_private)
# struct tty_file_private->tty(struct tty_struct)
# struct tty_struct->disc_data (struct n_tty_data)

- About FD 35 (struct file 880c65357c00)

crash> struct tty_struct 0x88085438ac00
:
read_wait = {
lock = {
{
rlock = {
raw_lock = {
{
head_tail = 0x3e363e36,
tickets = {
head = 0x3e36,
tail = 0x3e36
}
}
}
}
}
},
task_list = {
next = 0x88084477de80,
prev = 0x88084477de80
}
},

crash> eval 0x88084477de80 - 0x18
hexadecimal: 88084477de68

crash> struct wait_queue_t 88084477de68
struct wait_queue_t {
flags = 0,
private = 0x880853111800, <== *
func = 0x8109a9b0 ,
task_list = {
next = 0x88085438ae30,
prev = 0x88085438ae30
}
}

A task_struct of PID 7347 is linked to a read_wait queue.

crash> struct n_tty_data 0xc9001edfb000
struct n_tty_data {
read_head = 2795, <== *


raw = 1 '\001',
real_raw = 1 '\001',
icanon = 0 '\000',
push = 0 '\000',
read_tail = 2794, <== *
}

read_head - read_tail = 1 1 byte data hasn't be read.

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

Title:
  14.04: read() from pty doesn't finish.

Status in linux package in Ubuntu:
  New

Bug description:
  It has been brought to my attention

  By the attached test program pty, a pair of process repeats writing
  and reading only '\n' to a master pseudoterminal device (/dev/ptmx)
  and a slave pseudoterminal device (/dev/pts/N) each. When we carry out
  the following 30 pairs 10,000 times, in a pair each process doesn't
  finish reading.

  $ pty 30
  The following message 

[Kernel-packages] [Bug 1189721] Re: Ralink RT3290 doesn't have a bluetooth driver

2015-11-03 Thread Hồng Quân
Still exists in Ubuntu 15.10

$ uname -a  
Linux Werewolf 4.2.0-16-generic #19-Ubuntu SMP Thu Oct 8 15:35:06 UTC 2015 
x86_64 x86_64 x86_64 GNU/Linux

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

Title:
  Ralink RT3290 doesn't have a bluetooth driver

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

Bug description:
  As of Raring Ubuntu has a wifi driver for the RT3290 that works out of
  the box.

  It still does not have bluetooth support.

  This thread in the Ubuntu forums links to a driver that is claimed to
  work:

  http://ubuntuforums.org/showthread.php?t=2115570
  --- 
  ApportVersion: 2.9.2-0ubuntu8.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  graeme 2412 F pulseaudio
  CRDA:
   country GB:
(2402 - 2482 @ 40), (N/A, 20)
(5170 - 5250 @ 40), (N/A, 20)
(5250 - 5330 @ 40), (N/A, 20), DFS
(5490 - 5710 @ 40), (N/A, 27), DFS
  DistroRelease: Ubuntu 13.04
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=2d107179-35e2-4b1f-8bdd-90a01132ec70
  InstallationDate: Installed on 2013-05-17 (144 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  MachineType: Hewlett-Packard HP ProBook 4540s
  MarkForUpload: True
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-31-generic 
root=UUID=ac74fd89-3445-4a6d-b91b-ae4987867afe ro quiet splash 
acpi_backlight=vendor vt.handoff=7
  ProcVersionSignature: Ubuntu 3.8.0-31.46-generic 3.8.13.8
  RelatedPackageVersions:
   linux-restricted-modules-3.8.0-31-generic N/A
   linux-backports-modules-3.8.0-31-generic  N/A
   linux-firmware1.106
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  Tags:  raring
  Uname: Linux 3.8.0-31-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo
  dmi.bios.date: 11/06/2012
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 68IRR Ver. F.32
  dmi.board.name: 17F6
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 58.1D
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68IRRVer.F.32:bd11/06/2012:svnHewlett-Packard:pnHPProBook4540s:pvrA1018C1100:rvnHewlett-Packard:rn17F6:rvrKBCVersion58.1D:cvnHewlett-Packard:ct10:cvr:
  dmi.product.name: HP ProBook 4540s
  dmi.product.version: A1018C1100
  dmi.sys.vendor: Hewlett-Packard

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1189721/+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 1512769] Re: Touchpad not working

2015-11-03 Thread Gregor Eesmaa
Fixed by re-attaching the keyboard.

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

Title:
  Touchpad not working

Status in linux package in Ubuntu:
  Invalid

Bug description:
  Touchpad on "Samsung XE700T1C"'s detachable "USB Keyboard+SmartPad" not 
working since Ubuntu 15.10 installation.
  --- 
  ApportVersion: 2.19.1-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gregor 1179 F pulseaudio
  DistroRelease: Ubuntu 15.10
  HibernationDevice: RESUME=UUID=f583b267-223b-4685-9fae-405a662da45f
  InstallationDate: Installed on 2015-11-03 (0 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 700T1C
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-16-generic 
root=UUID=2dd18d48-2240-40b9-88a1-12a388790609 ro quiet splash 
acpi_backlight=vendor vt.handoff=7
  ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3
  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-16-generic N/A
   linux-backports-modules-4.2.0-16-generic  N/A
   linux-firmware1.149
  Tags:  wily
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  Uname: Linux 4.2.0-16-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 02/15/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P10AAT.050.140215.dg
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: XE700T1C-K01EE
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: SEC_SW_REVISION_1234567890ABCD
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 8
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP10AAT.050.140215.dg:bd02/15/2014:svnSAMSUNGELECTRONICSCO.,LTD.:pn700T1C:pvrP10AAT:rvnSAMSUNGELECTRONICSCO.,LTD.:rnXE700T1C-K01EE:rvrSEC_SW_REVISION_1234567890ABCD:cvnSAMSUNGELECTRONICSCO.,LTD.:ct8:cvrN/A:
  dmi.product.name: 700T1C
  dmi.product.version: P10AAT
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1512769/+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 1512848] [NEW] Radeon VCE Init Error

2015-11-03 Thread schmod
Public bug reported:

Since upgrading to Ubuntu 15.10, I have encountered graphics performance
issues, and have occasionally experienced lockups during boot.

dmesg | grep radeon
[2.103294] [drm] radeon kernel modesetting enabled.
[2.114677] radeon :01:00.0: enabling device ( -> 0003)
[2.226348] radeon :01:00.0: VRAM: 1024M 0x - 
0x3FFF (1024M used)
[2.226349] radeon :01:00.0: GTT: 2048M 0x4000 - 
0xBFFF
[2.226494] [drm] radeon: 1024M of VRAM memory ready
[2.226506] [drm] radeon: 2048M of GTT memory ready.
[2.232296] [drm] radeon: dpm initialized
[2.234760] [drm] enabling PCIE gen 3 link speeds, disable with 
radeon.pcie_gen2=0
[3.456910] radeon :01:00.0: WB enabled
[3.456912] radeon :01:00.0: fence driver on ring 0 use gpu addr 
0x4c00 and cpu addr 0x88041663ac00
[3.456914] radeon :01:00.0: fence driver on ring 1 use gpu addr 
0x4c04 and cpu addr 0x88041663ac04
[3.456915] radeon :01:00.0: fence driver on ring 2 use gpu addr 
0x4c08 and cpu addr 0x88041663ac08
[3.456916] radeon :01:00.0: fence driver on ring 3 use gpu addr 
0x4c0c and cpu addr 0x88041663ac0c
[3.456918] radeon :01:00.0: fence driver on ring 4 use gpu addr 
0x4c10 and cpu addr 0x88041663ac10
[3.457696] radeon :01:00.0: fence driver on ring 5 use gpu addr 
0x00075a18 and cpu addr 0xc90002035a18
[3.558371] radeon :01:00.0: VCE init error (-110).
[3.558376] radeon :01:00.0: radeon: MSI limited to 32-bit
[3.558397] radeon :01:00.0: radeon: using MSI.
[3.558421] [drm] radeon: irq initialized.
[4.538452] radeon :01:00.0: No connectors reported connected with modes
[4.539564] radeon :01:00.0: fb1: radeondrmfb frame buffer device
[4.539598] [drm] Initialized radeon 2.43.0 20080528 for :01:00.0 on 
minor 1
[   11.629124] [drm] enabling PCIE gen 3 link speeds, disable with 
radeon.pcie_gen2=0
[   12.627048] radeon :01:00.0: WB enabled
[   12.627050] radeon :01:00.0: fence driver on ring 0 use gpu addr 
0x4c00 and cpu addr 0x88041663ac00
[   12.627051] radeon :01:00.0: fence driver on ring 1 use gpu addr 
0x4c04 and cpu addr 0x88041663ac04
[   12.627053] radeon :01:00.0: fence driver on ring 2 use gpu addr 
0x4c08 and cpu addr 0x88041663ac08
[   12.627054] radeon :01:00.0: fence driver on ring 3 use gpu addr 
0x4c0c and cpu addr 0x88041663ac0c
[   12.627055] radeon :01:00.0: fence driver on ring 4 use gpu addr 
0x4c10 and cpu addr 0x88041663ac10
[   12.627838] radeon :01:00.0: fence driver on ring 5 use gpu addr 
0x00075a18 and cpu addr 0xc90002035a18
[   12.728529] radeon :01:00.0: VCE init error (-110).


xrandr --listproviders
Providers: number : 3
Provider 0: id: 0x6a cap: 0x9, Source Output, Sink Offload crtcs: 4 outputs: 5 
associated providers: 2 name:Intel
Provider 1: id: 0x41 cap: 0x6, Sink Output, Source Offload crtcs: 2 outputs: 0 
associated providers: 2 name:radeon
Provider 2: id: 0x41 cap: 0x6, Sink Output, Source Offload crtcs: 2 outputs: 0 
associated providers: 2 name:radeon


lspci -k 
00:00.0 Host bridge: Intel Corporation 3rd Gen Core processor DRAM Controller 
(rev 09)
Subsystem: Samsung Electronics Co Ltd Device c0e6
Kernel driver in use: ivb_uncore
00:01.0 PCI bridge: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor 
PCI Express Root Port (rev 09)
Kernel driver in use: pcieport
00:02.0 VGA compatible controller: Intel Corporation 3rd Gen Core processor 
Graphics Controller (rev 09)
DeviceName:  Onboard IGD
Subsystem: Samsung Electronics Co Ltd Device c0e6
Kernel driver in use: i915
01:00.0 Display controller: Advanced Micro Devices, Inc. [AMD/ATI] Mars [Radeon 
HD 8670A/8670M/8750M] (rev ff)
Kernel driver in use: radeon


Possible upstream Debian bug: 
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=803087

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


** Tags: kernel-bug kernel-graphics

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

Title:
  Radeon VCE Init Error

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Since upgrading to Ubuntu 15.10, I have encountered graphics
  performance issues, and have occasionally experienced lockups during
  boot.

  dmesg | grep radeon
  [2.103294] [drm] radeon kernel modesetting enabled.
  [2.114677] radeon :01:00.0: enabling device ( -> 0003)
  [2.226348] radeon :01:00.0: VRAM: 1024M 0x - 
0x3FFF (1024M used)
  [2.226349] radeon :01:00.0: GTT: 2048M 0x4000 - 

[Kernel-packages] [Bug 1512769] Re: Touchpad not working

2015-11-03 Thread Joseph Salisbury
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.3 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.3-unstable/

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

Title:
  Touchpad not working

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Touchpad on "Samsung XE700T1C"'s detachable "USB Keyboard+SmartPad" not 
working since Ubuntu 15.10 installation.
  --- 
  ApportVersion: 2.19.1-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gregor 1179 F pulseaudio
  DistroRelease: Ubuntu 15.10
  HibernationDevice: RESUME=UUID=f583b267-223b-4685-9fae-405a662da45f
  InstallationDate: Installed on 2015-11-03 (0 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 700T1C
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-16-generic 
root=UUID=2dd18d48-2240-40b9-88a1-12a388790609 ro quiet splash 
acpi_backlight=vendor vt.handoff=7
  ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3
  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-16-generic N/A
   linux-backports-modules-4.2.0-16-generic  N/A
   linux-firmware1.149
  Tags:  wily
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  Uname: Linux 4.2.0-16-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 02/15/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P10AAT.050.140215.dg
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: XE700T1C-K01EE
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: SEC_SW_REVISION_1234567890ABCD
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 8
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP10AAT.050.140215.dg:bd02/15/2014:svnSAMSUNGELECTRONICSCO.,LTD.:pn700T1C:pvrP10AAT:rvnSAMSUNGELECTRONICSCO.,LTD.:rnXE700T1C-K01EE:rvrSEC_SW_REVISION_1234567890ABCD:cvnSAMSUNGELECTRONICSCO.,LTD.:ct8:cvrN/A:
  dmi.product.name: 700T1C
  dmi.product.version: P10AAT
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1512769/+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 1509029] Re: [Hyper-V] Crash in hot-add/remove scsi devices (smp)

2015-11-03 Thread Joseph Salisbury
Thanks for the test results, Chris.  I also built Trusty and Vivid test 
kernels.  The can be downloaded from:
Trusty: http://kernel.ubuntu.com/~jsalisbury/lp1509029/trusty
Vivid:  ttp://kernel.ubuntu.com/~jsalisbury/lp1509029/vivid

Can you give these kernels a test as well.  I'll submit an SRU request
for them as well if the testing is good.

Thanks again.

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

Title:
  [Hyper-V] Crash in hot-add/remove scsi devices (smp)

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

Bug description:
  On some host errors storvsc module tries to remove sdev by scheduling a job
  which does the following:

 sdev = scsi_device_lookup(wrk->host, 0, 0, wrk->lun);
 if (sdev) {
 scsi_remove_device(sdev);
 scsi_device_put(sdev);
 }

  While this code seems correct the following crash is observed:

   general protection fault:  [#1] SMP DEBUG_PAGEALLOC
   RIP: 0010:[]  [] bdi_destroy+0x39/0x220
   ...
   [] ? _raw_spin_unlock_irq+0x2c/0x40
   [] blk_cleanup_queue+0x17b/0x270
   [] __scsi_remove_device+0x54/0xd0 [scsi_mod]
   [] scsi_remove_device+0x2b/0x40 [scsi_mod]
   [] storvsc_remove_lun+0x3d/0x60 [hv_storvsc]
   [] process_one_work+0x1b1/0x530
   ...

  The problem comes with the fact that many such jobs (for the same device)
  are being scheduled simultaneously. While scsi_remove_device() uses
  shost->scan_mutex and scsi_device_lookup() will fail for a device in
  SDEV_DEL state there is no protection against someone who did
  scsi_device_lookup() before we actually entered __scsi_remove_device(). So
  the whole scenario looks like that: two callers do simultaneous (or
  preemption happens) calls to scsi_device_lookup() ant these calls succeed
  for all of them, after that both callers try doing scsi_remove_device().
  shost->scan_mutex only serializes their calls to __scsi_remove_device()
  and we end up doing the cleanup path twice.

  Signed-off-by: Vitaly Kuznetsov 
  ---
   drivers/scsi/scsi_sysfs.c | 8 
   1 file changed, 8 insertions(+)

  diff --git a/drivers/scsi/scsi_sysfs.c b/drivers/scsi/scsi_sysfs.c
  index b89..e0d2707 100644
  --- a/drivers/scsi/scsi_sysfs.c
  +++ b/drivers/scsi/scsi_sysfs.c
  @@ -1076,6 +1076,14 @@ void __scsi_remove_device(struct scsi_device *sdev)
   {
  struct device *dev = >sdev_gendev;

  +   /*
  +* This cleanup path is not reentrant and while it is impossible
  +* to get a new reference with scsi_device_get() someone can still
  +* hold a previously acquired one.
  +*/
  +   if (sdev->sdev_state == SDEV_DEL)
  +   return;
  +
  if (sdev->is_visible) {
  if (scsi_device_set_state(sdev, SDEV_CANCEL) != 0)
  return;

  
  --
  2.4.3

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

2015-11-03 Thread Brad Figg
This bug is missing log files that will aid in diagnosing the problem.
>From a terminal window please run:

apport-collect 1512815

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

Title:
  read() from pty doesn't finish.

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  It has been brought to my attention

  By the attached test program pty, a pair of process repeats writing
  and reading only '\n' to a master pseudoterminal device (/dev/ptmx)
  and a slave pseudoterminal device (/dev/pts/N) each. When we carry out
  the following 30 pairs 10,000 times, in a pair each process doesn't
  finish reading.

  $ pty 30
  The following message will be usually indicated immediately.
  #name copy num/sec usec/num
  pty_switch 30 1541842 0.648575

  When a message wasn't indicated any more, we got the attached dump file. 
  A kernel was 3.13.0-45.74. 
  A system was Ubuntu 14.04 LTS.

  The same problem occurred in case of 3.13.0-55.92 kernel and the following 
kernel have been tested as well:
  2.6.32, 3.10: not reproduces.
  3.19, 4.0.0, 4.1.3: reproduces.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1512815/+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 1512815] Re: read() from pty doesn't finish.

2015-11-03 Thread Eric Desrochers
** Summary changed:

- 14.04: read() from pty doesn't finish.
+ read() from pty doesn't finish.

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

Title:
  read() from pty doesn't finish.

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  It has been brought to my attention

  By the attached test program pty, a pair of process repeats writing
  and reading only '\n' to a master pseudoterminal device (/dev/ptmx)
  and a slave pseudoterminal device (/dev/pts/N) each. When we carry out
  the following 30 pairs 10,000 times, in a pair each process doesn't
  finish reading.

  $ pty 30
  The following message will be usually indicated immediately.
  #name copy num/sec usec/num
  pty_switch 30 1541842 0.648575

  When a message wasn't indicated any more, we got the attached dump file. 
  A kernel was 3.13.0-45.74. 
  A system was Ubuntu 14.04 LTS.

  The same problem occurred in case of 3.13.0-55.92 kernel and the following 
kernel have been tested as well:
  2.6.32, 3.10: not reproduces.
  3.19, 4.0.0, 4.1.3: reproduces.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1512815/+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 1512769] Re: Touchpad not working

2015-11-03 Thread Gregor Eesmaa
1. I think I've successfully used the touchpad on this device with Ubuntu 14.10 
in the past even though it wasn't recognized as a touchpad and I couldn't use 
multi-finger gestures with it - perhaps an attempt to fix it could've resulted 
in it not working in this version of Ubuntu? 
2. The specified kernel (v4.3-unstable or v4.3-wily) didn't fix the problem.

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

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

Title:
  Touchpad not working

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Touchpad on "Samsung XE700T1C"'s detachable "USB Keyboard+SmartPad" not 
working since Ubuntu 15.10 installation.
  --- 
  ApportVersion: 2.19.1-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gregor 1179 F pulseaudio
  DistroRelease: Ubuntu 15.10
  HibernationDevice: RESUME=UUID=f583b267-223b-4685-9fae-405a662da45f
  InstallationDate: Installed on 2015-11-03 (0 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 700T1C
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-16-generic 
root=UUID=2dd18d48-2240-40b9-88a1-12a388790609 ro quiet splash 
acpi_backlight=vendor vt.handoff=7
  ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3
  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-16-generic N/A
   linux-backports-modules-4.2.0-16-generic  N/A
   linux-firmware1.149
  Tags:  wily
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  Uname: Linux 4.2.0-16-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 02/15/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P10AAT.050.140215.dg
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: XE700T1C-K01EE
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: SEC_SW_REVISION_1234567890ABCD
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 8
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP10AAT.050.140215.dg:bd02/15/2014:svnSAMSUNGELECTRONICSCO.,LTD.:pn700T1C:pvrP10AAT:rvnSAMSUNGELECTRONICSCO.,LTD.:rnXE700T1C-K01EE:rvrSEC_SW_REVISION_1234567890ABCD:cvnSAMSUNGELECTRONICSCO.,LTD.:ct8:cvrN/A:
  dmi.product.name: 700T1C
  dmi.product.version: P10AAT
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.

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

2015-11-03 Thread ubuntu
Sorry for the long delay in posting results but I did want to share what we've 
learned.
1) The failures happen during the VSS Snapshot/checkpoint creation process.   
You can reproduce the errors by doing manual VSS snapshots.
2) The heavier the VM load, especially I/O,  the more likely the error will 
occur.
3) Every kernel posted (including the Willy) share the same problem - 
differences were not significant between them.
4) During snapshot creation, even RHEL hits a bump. There's a small delay in 
response times but nothing that causes errors.  Installing LIS 4.0 doesn't make 
a difference.

Unfortunately, I can't follow-up with further testing.  After figuring
this out we cancelled the migration to Hyper-V and invested further in
our VMware infrastructure.   :(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/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 Utopic:
  In Progress
Status in linux source package in Vivid:
  In Progress
Status in linux source package in Wily:
  In Progress

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

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

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

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

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


[Kernel-packages] [Bug 1512769] Re: Touchpad not working

2015-11-03 Thread Joseph Salisbury
Was the touchpad working with prior releases?

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

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

Title:
  Touchpad not working

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Touchpad on "Samsung XE700T1C"'s detachable "USB Keyboard+SmartPad" not 
working since Ubuntu 15.10 installation.
  --- 
  ApportVersion: 2.19.1-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gregor 1179 F pulseaudio
  DistroRelease: Ubuntu 15.10
  HibernationDevice: RESUME=UUID=f583b267-223b-4685-9fae-405a662da45f
  InstallationDate: Installed on 2015-11-03 (0 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 700T1C
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-16-generic 
root=UUID=2dd18d48-2240-40b9-88a1-12a388790609 ro quiet splash 
acpi_backlight=vendor vt.handoff=7
  ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3
  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-16-generic N/A
   linux-backports-modules-4.2.0-16-generic  N/A
   linux-firmware1.149
  Tags:  wily
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  Uname: Linux 4.2.0-16-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 02/15/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P10AAT.050.140215.dg
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: XE700T1C-K01EE
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: SEC_SW_REVISION_1234567890ABCD
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 8
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP10AAT.050.140215.dg:bd02/15/2014:svnSAMSUNGELECTRONICSCO.,LTD.:pn700T1C:pvrP10AAT:rvnSAMSUNGELECTRONICSCO.,LTD.:rnXE700T1C-K01EE:rvrSEC_SW_REVISION_1234567890ABCD:cvnSAMSUNGELECTRONICSCO.,LTD.:ct8:cvrN/A:
  dmi.product.name: 700T1C
  dmi.product.version: P10AAT
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1512769/+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 1512884] Re: hv driver in -lbm package not used

2015-11-03 Thread Luis Henriques
** Changed in: linux (Ubuntu Precise)
   Status: Incomplete => Confirmed

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

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

Title:
  hv driver in -lbm package not used

Status in linux package in Ubuntu:
  Confirmed
Status in linux-backports-modules-3.2.0 package in Ubuntu:
  New
Status in linux source package in Precise:
  Confirmed
Status in linux-backports-modules-3.2.0 source package in Precise:
  New

Bug description:
  The driver in the linux-backports-modules-3.2.0 package is not being
  used and is currently unmaintained.  It should be disabled, as the in-
  kernel version seems to be preferred.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1512884/+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 1509120] Re: Process accounting deadlock with idmapd callout when writing to NFSv4 mount

2015-11-03 Thread Dave Chiluk
Yeah, I think so, if you are "creative" enough to put your accounting on
your nfs mount, and then have your nfs service fail, you should expect
your machine to stop functioning.  Otherwise it could be a potential
accounting/security hole.

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

Title:
  Process accounting deadlock with idmapd callout when writing to NFSv4
  mount

Status in linux package in Ubuntu:
  Invalid
Status in nfs-utils package in Ubuntu:
  In Progress

Bug description:
  [Impact]

   * Programs accessing nfsv4 mounts will hang on request_key interface
  with nfs4 + sec=sys with old nfsv4 hosts.  Kernel is waiting on
  usermodehelper provided by keyutils.

   * INFO: task ls:2101 blocked for more than 120 seconds.
Not tainted 3.13.0-66-generic #108-Ubuntu
  "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
  ls D 88007fd13180 0 2101 1215 0x0004
   88007b14d630 0086 8800374e6000 88007b14dfd8
   00013180 00013180 8800374e6000 88007b14d6b0
   88007ffd1460 0002 812d0ce0 88007b14d6a0
  Call Trace:
   [] ? umh_keys_init+0x20/0x20
   [] schedule+0x29/0x70
   [] key_wait_bit+0xe/0x20
   [] __wait_on_bit+0x62/0x90
   [] ? umh_keys_init+0x20/0x20
   [] out_of_line_wait_on_bit+0x77/0x90
   [] ? autoremove_wake_function+0x40/0x40
   [] wait_for_key_construction+0x6e/0x80
   [] request_key+0x5c/0xa0
   [] nfs_idmap_get_key+0xaf/0x1c0 [nfsv4]
   [] nfs_map_name_to_uid+0xef/0x150 [nfsv4]
   [] decode_getfattr_attrs+0xe47/0x14b0 [nfsv4]
   [] ? sched_clock+0x9/0x10
   [] decode_getfattr_generic.constprop.102+0x8c/0xf0 [nfsv4]
   [] ? nfs4_xdr_dec_access+0xa0/0xa0 [nfsv4]
   [] nfs4_xdr_dec_getattr+0x70/0x80 [nfsv4]
   [] rpcauth_unwrap_resp+0x86/0xd0 [sunrpc]
   [] ? nfs4_xdr_dec_access+0xa0/0xa0 [nfsv4]
   [] call_decode+0x1df/0x870 [sunrpc]
   [] ? call_refreshresult+0x170/0x170 [sunrpc]
   [] ? call_refreshresult+0x170/0x170 [sunrpc]
   [] __rpc_execute+0x84/0x400 [sunrpc]
   [] rpc_execute+0x5e/0xa0 [sunrpc]
   [] rpc_run_task+0x70/0x90 [sunrpc]
   [] nfs4_call_sync_sequence+0x56/0x80 [nfsv4]
   [] _nfs4_proc_getattr+0xbe/0xd0 [nfsv4]
   [] nfs4_proc_getattr+0x5a/0xd0 [nfsv4]
   [] __nfs_revalidate_inode+0xbf/0x310 [nfs]
   [] nfs_opendir+0xe3/0x100 [nfs]
   [] do_dentry_open+0x233/0x2e0
   [] ? nfs_readdir_clear_array+0x70/0x70 [nfs]
   [] vfs_open+0x49/0x50
   [] do_last+0x564/0x1240
   [] ? link_path_walk+0x256/0x880
   [] ? apparmor_file_alloc_security+0x5b/0x180
   [] ? security_file_alloc+0x16/0x20
   [] path_openat+0xbb/0x650
   [] do_filp_open+0x3a/0x90
   [] ? do_mmap_pgoff+0x34e/0x3d0
   [] ? __alloc_fd+0xa7/0x130
   [] do_sys_open+0x129/0x280
   [] ? do_page_fault+0x1a/0x70
   [] SyS_openat+0x14/0x20
   [] system_call_fastpath+0x1a/0x1f

  [Regression Potential]

   * Minimal this was applied to vivid+wily via bug 1449074.

  [Other Info]
   
   * Sulution is to add keyutils as Required to nfs-common.

  Original Description 
  __

  ---Problem Description---
  System hang when process accounting to a NFSv4 mount.

  ---uname output---
  Linux ppc001 3.19.0-30-generic #34~14.04.1-Ubuntu SMP Fri Oct 2 22:21:52
  UTC 2015 ppc64le ppc64le ppc64le GNU/Linux

  ---Problem Details---

  We have a customer that is experiencing intermittent system hangs on
  their system.  After a bit of debug, it was discovered that the
  trigger was turning on process accounting and writing to a file hosted
  via an NFSv4 mount.  During the testing, several vmcores were
  captured, and the fingerprint indicates a mutex deadlock situation
  with process accounting.   In the most recent vmcore, it appears that
  the scenario is something like the following:

  1. PID: 4898 COMMAND: "ls" triggers a write to the process accounting file.
  2. The resulting NFS write needs idmapd information and calls out to idmapd
  3. The idmapd usermodehelper process triggers another process accounting 
update that blocks on the mutex being held by PID 4898.

  PID: 4898   TASK: c01fd26d7580  CPU: 7   COMMAND: "ls"
   #0 [c01fd274a950] __switch_to at c0015934
   #1 [c01fd274ab20] __switch_to at c0015934
   #2 [c01fd274ab80] __schedule at c0a11de8
   #3 [c01fd274ada0] schedule_timeout at c0a16284
   #4 [c01fd274ae90] wait_for_common at c0a1360c
   #5 [c01fd274af10] call_usermodehelper_exec at c00ccd38
   #6 [c01fd274af70] call_sbin_request_key at c0429258
   #7 [c01fd274b100] request_key_and_link at c042983c
   #8 [c01fd274b200] request_key at c0429978
   #9 [c01fd274b240] nfs_idmap_get_key at d0002ca8b0bc [nfsv4]
  #10 [c01fd274b2b0] nfs_map_name_to_uid at d0002ca8bbd0 [nfsv4]
  #11 [c01fd274b320] 

[Kernel-packages] [Bug 1509120] Re: Process accounting deadlock with idmapd callout when writing to NFSv4 mount

2015-11-03 Thread Dave Chiluk
** Tags added: sts

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

Title:
  Process accounting deadlock with idmapd callout when writing to NFSv4
  mount

Status in linux package in Ubuntu:
  Invalid
Status in nfs-utils package in Ubuntu:
  In Progress

Bug description:
  [Impact]

   * Programs accessing nfsv4 mounts will hang on request_key interface
  with nfs4 + sec=sys with old nfsv4 hosts.  Kernel is waiting on
  usermodehelper provided by keyutils.

   * INFO: task ls:2101 blocked for more than 120 seconds.
Not tainted 3.13.0-66-generic #108-Ubuntu
  "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
  ls D 88007fd13180 0 2101 1215 0x0004
   88007b14d630 0086 8800374e6000 88007b14dfd8
   00013180 00013180 8800374e6000 88007b14d6b0
   88007ffd1460 0002 812d0ce0 88007b14d6a0
  Call Trace:
   [] ? umh_keys_init+0x20/0x20
   [] schedule+0x29/0x70
   [] key_wait_bit+0xe/0x20
   [] __wait_on_bit+0x62/0x90
   [] ? umh_keys_init+0x20/0x20
   [] out_of_line_wait_on_bit+0x77/0x90
   [] ? autoremove_wake_function+0x40/0x40
   [] wait_for_key_construction+0x6e/0x80
   [] request_key+0x5c/0xa0
   [] nfs_idmap_get_key+0xaf/0x1c0 [nfsv4]
   [] nfs_map_name_to_uid+0xef/0x150 [nfsv4]
   [] decode_getfattr_attrs+0xe47/0x14b0 [nfsv4]
   [] ? sched_clock+0x9/0x10
   [] decode_getfattr_generic.constprop.102+0x8c/0xf0 [nfsv4]
   [] ? nfs4_xdr_dec_access+0xa0/0xa0 [nfsv4]
   [] nfs4_xdr_dec_getattr+0x70/0x80 [nfsv4]
   [] rpcauth_unwrap_resp+0x86/0xd0 [sunrpc]
   [] ? nfs4_xdr_dec_access+0xa0/0xa0 [nfsv4]
   [] call_decode+0x1df/0x870 [sunrpc]
   [] ? call_refreshresult+0x170/0x170 [sunrpc]
   [] ? call_refreshresult+0x170/0x170 [sunrpc]
   [] __rpc_execute+0x84/0x400 [sunrpc]
   [] rpc_execute+0x5e/0xa0 [sunrpc]
   [] rpc_run_task+0x70/0x90 [sunrpc]
   [] nfs4_call_sync_sequence+0x56/0x80 [nfsv4]
   [] _nfs4_proc_getattr+0xbe/0xd0 [nfsv4]
   [] nfs4_proc_getattr+0x5a/0xd0 [nfsv4]
   [] __nfs_revalidate_inode+0xbf/0x310 [nfs]
   [] nfs_opendir+0xe3/0x100 [nfs]
   [] do_dentry_open+0x233/0x2e0
   [] ? nfs_readdir_clear_array+0x70/0x70 [nfs]
   [] vfs_open+0x49/0x50
   [] do_last+0x564/0x1240
   [] ? link_path_walk+0x256/0x880
   [] ? apparmor_file_alloc_security+0x5b/0x180
   [] ? security_file_alloc+0x16/0x20
   [] path_openat+0xbb/0x650
   [] do_filp_open+0x3a/0x90
   [] ? do_mmap_pgoff+0x34e/0x3d0
   [] ? __alloc_fd+0xa7/0x130
   [] do_sys_open+0x129/0x280
   [] ? do_page_fault+0x1a/0x70
   [] SyS_openat+0x14/0x20
   [] system_call_fastpath+0x1a/0x1f

  [Regression Potential]

   * Minimal this was applied to vivid+wily via bug 1449074.

  [Other Info]
   
   * Sulution is to add keyutils as Required to nfs-common.

  Original Description 
  __

  ---Problem Description---
  System hang when process accounting to a NFSv4 mount.

  ---uname output---
  Linux ppc001 3.19.0-30-generic #34~14.04.1-Ubuntu SMP Fri Oct 2 22:21:52
  UTC 2015 ppc64le ppc64le ppc64le GNU/Linux

  ---Problem Details---

  We have a customer that is experiencing intermittent system hangs on
  their system.  After a bit of debug, it was discovered that the
  trigger was turning on process accounting and writing to a file hosted
  via an NFSv4 mount.  During the testing, several vmcores were
  captured, and the fingerprint indicates a mutex deadlock situation
  with process accounting.   In the most recent vmcore, it appears that
  the scenario is something like the following:

  1. PID: 4898 COMMAND: "ls" triggers a write to the process accounting file.
  2. The resulting NFS write needs idmapd information and calls out to idmapd
  3. The idmapd usermodehelper process triggers another process accounting 
update that blocks on the mutex being held by PID 4898.

  PID: 4898   TASK: c01fd26d7580  CPU: 7   COMMAND: "ls"
   #0 [c01fd274a950] __switch_to at c0015934
   #1 [c01fd274ab20] __switch_to at c0015934
   #2 [c01fd274ab80] __schedule at c0a11de8
   #3 [c01fd274ada0] schedule_timeout at c0a16284
   #4 [c01fd274ae90] wait_for_common at c0a1360c
   #5 [c01fd274af10] call_usermodehelper_exec at c00ccd38
   #6 [c01fd274af70] call_sbin_request_key at c0429258
   #7 [c01fd274b100] request_key_and_link at c042983c
   #8 [c01fd274b200] request_key at c0429978
   #9 [c01fd274b240] nfs_idmap_get_key at d0002ca8b0bc [nfsv4]
  #10 [c01fd274b2b0] nfs_map_name_to_uid at d0002ca8bbd0 [nfsv4]
  #11 [c01fd274b320] decode_getfattr_attrs at d0002ca7f59c [nfsv4]
  #12 [c01fd274b420] decode_getfattr_generic.constprop.96 at 
d0002ca7fd78
  [nfsv4]
  #13 [c01fd274b4d0] nfs4_xdr_dec_getattr at d0002ca80738 [nfsv4]
  #14 

[Kernel-packages] [Bug 1512593] Re: :Ubuntu NV: Panic timeout=0 means Ubuntu does not reboot and recover from HMI (e.g. Core Unit Checkstop)

2015-11-03 Thread Chris J Arges
** Changed in: linux (Ubuntu)
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Chris J Arges 
(arges)

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

** Changed in: linux (Ubuntu)
   Status: Triaged => 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/1512593

Title:
  :Ubuntu NV: Panic timeout=0 means Ubuntu does not reboot and recover
  from HMI (e.g. Core Unit Checkstop)

Status in linux package in Ubuntu:
  In Progress

Bug description:
  Problem Description
  ==
  I attempted to inject a Core Unit Checkstop error by flipping Core FIR bit 5 
on a K80 (Nvidia) 42L Server ( FSP - gp4fp1.aus.stglabs.ibm.com ). I was 
expecting the server to crash due to a Sapphire assert ( PEL with SRC BB821410 
) and a Sapphire dump to be collected in the process.

  However on injecting the error , the host ( Ubuntu NV ) crashed, and
  never recovered. OPAL however seemed to stay up and there were a
  plethora of mail box errors - B182953C logged by the FSP.

  Error Inject
  --
  $ putscom pu.ex 10013100 5 1 1 -ib -p3 -c5
  s1.ex   k0:n0:s0:p03:c5
  ecmd_ppc putscom pu.ex 10013100 5 1 1 -ib -p3 -c5

  
  Console message
  --
  [htx@gp4p01]  [1m/sys/devices/system/cpu# [0m [ 1652.976253] Fatal Hypervisor 
Maintenance interrupt [Not recovered]
  [ 1652.976332]  Error detail: Malfunction Alert
  [ 1652.976402]  HMER: 8040
  [ 1652.976450] Kernel panic - not syncing: Unrecoverable HMI exception
  [ 1652.976467] CPU: 24 PID: 1261 Comm: kworker/24:1 Tainted: P   OE 
3.16.0-37-generic #51~14.04.1-Ubuntu
  [ 1652.976530] Workqueue: events hmi_event_handler
  [ 1652.976561] Call Trace:
  [ 1652.976571] [c000189bf9e0] [c0017330] show_stack+0x170/0x290 
(unreliable)
  [ 1652.976647] [c000189bfac0] [c09eb8e4] dump_stack+0x90/0xbc
  [ 1652.976674] [c000189bfaf0] [c09e2b5c] panic+0x104/0x2a8
  [ 1652.976703] [c000189bfb80] [c007306c] 
hmi_event_handler+0x19c/0x2b0
  [ 1652.976732] [c000189bfc50] [c00d62dc] 
process_one_work+0x1ac/0x4d0
  [ 1652.976772] [c000189bfce0] [c00d6b80] worker_thread+0x190/0x630
  [ 1652.976800] [c000189bfd80] [c00e0024] kthread+0x114/0x140
  [ 1652.976837] [c000189bfe30] [c000a468] 
ret_from_kernel_thread+0x5c/0x74
  [ 1652.977085] ---[ end Kernel panic - not syncing: Unrecoverable HMI 
exception
   

  .
  .
  .
  .
  
|--|
  | 0x50227CFC 06/14/2015 22:27:43 System Hypervisor Firmware   
mbox |
  | 0x50227CFC Processed   Predictive Error 
B182953C | --> Unexpected mail box error , needs investigation 
  
|--|
  | 0x50227CDD 06/14/2015 22:27:21 System Hypervisor Firmware   
spif |
  | 0x50227CDD Processed   Predictive Error 
B182951C | --> Unexpected mail box error , needs investigation 
  
|--|
  | 0x50227CC0 06/14/2015 22:26:57 System Hypervisor Firmware   
mbox |
  | 0x50227CC0 Processed   Predictive Error 
B182953C | --> Unexpected mail box error , needs investigation 
  
|--|
  | 0x50227C9E 06/14/2015 22:26:31 System Hypervisor Firmware   
spif |
  | 0x50227C9E Processed   Predictive Error 
B182951C | --> Unexpected mail box error , needs investigation 
  
|--|
  | 0x50227C88 06/14/2015 22:26:12 System Hypervisor Firmware   
mbox |
  | 0x50227C88 Processed   Predictive Error 
B182953C | --> Unexpected mail box error , needs investigation 
  
|--|
  | 0x50227C7E 06/14/2015 22:26:06 System Hypervisor Firmware   
spif |
  | 0x50227C7E Processed   Predictive Error 
B182951C | --> Unexpected mail box error , needs investigation 
  
|--|
  | 0x50227C4F 06/14/2015 22:25:27 System Hypervisor Firmware   
mbox |
  | 0x50227C4F Processed   Predictive Error 
B182953C | --> Unexpected mail box error , needs investigation 
  
|--|
  | 0x50227C40 06/14/2015 22:25:16 System Hypervisor Firmware   
spif |
  | 0x50227C40 Processed   Predictive Error 
B182951C | --> Unexpected mail box 

[Kernel-packages] [Bug 1512884] [NEW] hv driver in -lbm package not used

2015-11-03 Thread Luis Henriques
Public bug reported:

The driver in the linux-backports-modules-3.2.0 package is not being
used and is currently unmaintained.  It should be disabled, as the in-
kernel version seems to be preferred.

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

** Affects: linux-backports-modules-3.2.0 (Ubuntu)
 Importance: Undecided
 Status: New

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

** Affects: linux-backports-modules-3.2.0 (Ubuntu Precise)
 Importance: Undecided
 Status: New

** Also affects: linux-backports-modules-3.2.0 (Ubuntu)
   Importance: Undecided
   Status: New

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

** Also affects: linux-backports-modules-3.2.0 (Ubuntu Precise)
   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/1512884

Title:
  hv driver in -lbm package not used

Status in linux package in Ubuntu:
  Incomplete
Status in linux-backports-modules-3.2.0 package in Ubuntu:
  New
Status in linux source package in Precise:
  Incomplete
Status in linux-backports-modules-3.2.0 source package in Precise:
  New

Bug description:
  The driver in the linux-backports-modules-3.2.0 package is not being
  used and is currently unmaintained.  It should be disabled, as the in-
  kernel version seems to be preferred.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1512884/+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 1512593] Re: :Ubuntu NV: Panic timeout=0 means Ubuntu does not reboot and recover from HMI (e.g. Core Unit Checkstop)

2015-11-03 Thread Leann Ogasawara
** Package changed: ubuntu => linux (Ubuntu)

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

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

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

Title:
  :Ubuntu NV: Panic timeout=0 means Ubuntu does not reboot and recover
  from HMI (e.g. Core Unit Checkstop)

Status in linux package in Ubuntu:
  Triaged

Bug description:
  Problem Description
  ==
  I attempted to inject a Core Unit Checkstop error by flipping Core FIR bit 5 
on a K80 (Nvidia) 42L Server ( FSP - gp4fp1.aus.stglabs.ibm.com ). I was 
expecting the server to crash due to a Sapphire assert ( PEL with SRC BB821410 
) and a Sapphire dump to be collected in the process.

  However on injecting the error , the host ( Ubuntu NV ) crashed, and
  never recovered. OPAL however seemed to stay up and there were a
  plethora of mail box errors - B182953C logged by the FSP.

  Error Inject
  --
  $ putscom pu.ex 10013100 5 1 1 -ib -p3 -c5
  s1.ex   k0:n0:s0:p03:c5
  ecmd_ppc putscom pu.ex 10013100 5 1 1 -ib -p3 -c5

  
  Console message
  --
  [htx@gp4p01]  [1m/sys/devices/system/cpu# [0m [ 1652.976253] Fatal Hypervisor 
Maintenance interrupt [Not recovered]
  [ 1652.976332]  Error detail: Malfunction Alert
  [ 1652.976402]  HMER: 8040
  [ 1652.976450] Kernel panic - not syncing: Unrecoverable HMI exception
  [ 1652.976467] CPU: 24 PID: 1261 Comm: kworker/24:1 Tainted: P   OE 
3.16.0-37-generic #51~14.04.1-Ubuntu
  [ 1652.976530] Workqueue: events hmi_event_handler
  [ 1652.976561] Call Trace:
  [ 1652.976571] [c000189bf9e0] [c0017330] show_stack+0x170/0x290 
(unreliable)
  [ 1652.976647] [c000189bfac0] [c09eb8e4] dump_stack+0x90/0xbc
  [ 1652.976674] [c000189bfaf0] [c09e2b5c] panic+0x104/0x2a8
  [ 1652.976703] [c000189bfb80] [c007306c] 
hmi_event_handler+0x19c/0x2b0
  [ 1652.976732] [c000189bfc50] [c00d62dc] 
process_one_work+0x1ac/0x4d0
  [ 1652.976772] [c000189bfce0] [c00d6b80] worker_thread+0x190/0x630
  [ 1652.976800] [c000189bfd80] [c00e0024] kthread+0x114/0x140
  [ 1652.976837] [c000189bfe30] [c000a468] 
ret_from_kernel_thread+0x5c/0x74
  [ 1652.977085] ---[ end Kernel panic - not syncing: Unrecoverable HMI 
exception
   

  .
  .
  .
  .
  
|--|
  | 0x50227CFC 06/14/2015 22:27:43 System Hypervisor Firmware   
mbox |
  | 0x50227CFC Processed   Predictive Error 
B182953C | --> Unexpected mail box error , needs investigation 
  
|--|
  | 0x50227CDD 06/14/2015 22:27:21 System Hypervisor Firmware   
spif |
  | 0x50227CDD Processed   Predictive Error 
B182951C | --> Unexpected mail box error , needs investigation 
  
|--|
  | 0x50227CC0 06/14/2015 22:26:57 System Hypervisor Firmware   
mbox |
  | 0x50227CC0 Processed   Predictive Error 
B182953C | --> Unexpected mail box error , needs investigation 
  
|--|
  | 0x50227C9E 06/14/2015 22:26:31 System Hypervisor Firmware   
spif |
  | 0x50227C9E Processed   Predictive Error 
B182951C | --> Unexpected mail box error , needs investigation 
  
|--|
  | 0x50227C88 06/14/2015 22:26:12 System Hypervisor Firmware   
mbox |
  | 0x50227C88 Processed   Predictive Error 
B182953C | --> Unexpected mail box error , needs investigation 
  
|--|
  | 0x50227C7E 06/14/2015 22:26:06 System Hypervisor Firmware   
spif |
  | 0x50227C7E Processed   Predictive Error 
B182951C | --> Unexpected mail box error , needs investigation 
  
|--|
  | 0x50227C4F 06/14/2015 22:25:27 System Hypervisor Firmware   
mbox |
  | 0x50227C4F Processed   Predictive Error 
B182953C | --> Unexpected mail box error , needs investigation 
  
|--|
  | 0x50227C40 06/14/2015 22:25:16 System Hypervisor Firmware   
spif |
  | 0x50227C40 Processed   Predictive Error 
B182951C | --> Unexpected mail box error , needs 

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

2015-11-03 Thread Brad Figg
This bug is missing log files that will aid in diagnosing the problem.
>From a terminal window please run:

apport-collect 1512884

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

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

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

Title:
  hv driver in -lbm package not used

Status in linux package in Ubuntu:
  Incomplete
Status in linux-backports-modules-3.2.0 package in Ubuntu:
  New
Status in linux source package in Precise:
  Incomplete
Status in linux-backports-modules-3.2.0 source package in Precise:
  New

Bug description:
  The driver in the linux-backports-modules-3.2.0 package is not being
  used and is currently unmaintained.  It should be disabled, as the in-
  kernel version seems to be preferred.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1512884/+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 1511511] Re: USB keyboard stops working after pressing extended key

2015-11-03 Thread Daniel M. Lambea
The keyboard was bought a few months ago and the bug have always been
there. I've tried the keyboard both in upgraded systems and in fresh
installations to no avail.

Following your instructions, I have just tested it right now using the
mainline kernel (at the URL you provided) and the bug is still showing,
so I proceed with adding the tag 'kernel-bug-exists-upstream'.


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

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

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

Title:
  USB keyboard stops working after pressing extended key

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  USB keyboard Cougar K500 gaming keyboard has some additional extended
  keys, all of them making the keyboard stop responding if pressed under
  linux. The device is recovered only by unplugging the USB and plugging
  it again.

  The keyboard has been tested under Ubuntu 14.04.3 LTS, Ubuntu 15.04
  and Ubuntu 15.10 (the latter running as virtualbox guest). All tests
  failed with exactly the same behaviour.

  USB ID is: "060b:500a Solid Year".

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: linux-image-4.2.0-16-generic 4.2.0-16.19 [modified: 
boot/vmlinuz-4.2.0-16-generic]
  ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3
  Uname: Linux 4.2.0-16-generic x86_64
  ApportVersion: 2.19.1-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  pinfli 1055 F pulseaudio
  Date: Thu Oct 29 19:33:23 2015
  HibernationDevice: RESUME=UUID=f68f4b91-ea68-4e4b-9a10-8ed5bca2efbe
  InstallationDate: Installed on 2015-10-24 (5 days ago)
  InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Release amd64 
(20151021)
  IwConfig:
   enp0s3no wireless extensions.
   
   lono wireless extensions.
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 002: ID 060b:500a Solid Year 
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: innotek GmbH VirtualBox
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-16-generic 
root=UUID=523dfd8b-b825-47e3-a116-cb85f901386c ro quiet splash
  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.2.0-16-generic N/A
   linux-backports-modules-4.2.0-16-generic  N/A
   linux-firmware1.149
  RfKill:
   
  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: 12/01/2006
  dmi.bios.vendor: innotek GmbH
  dmi.bios.version: VirtualBox
  dmi.board.name: VirtualBox
  dmi.board.vendor: Oracle Corporation
  dmi.board.version: 1.2
  dmi.chassis.type: 1
  dmi.chassis.vendor: Oracle Corporation
  dmi.modalias: 
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
  dmi.product.name: VirtualBox
  dmi.product.version: 1.2
  dmi.sys.vendor: innotek GmbH

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1511511/+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 1484159] Re: Qualcomm Atheros Device [168c:0042] (rev 30) not working on Ubuntu

2015-11-03 Thread Sasha
Hay guys,

look at this

http://askubuntu.com/questions/678145/my-wifi-qualcomm-atheros-device-
168c0041-rev-20-doesnt-show-up-and-work-in

Seems like it's the second last version of this hardware we're talking about 
([168c:0041] (rev 20)).
I don't know if that is of any help, but I wanted to share it with you.

My thought is "is it that unlikely to say take this version and grade it
up to the newer version?". I'm not familiar with developing/programing
those things. And also a new linux user. I'm using the same machine and
have the same issue.

Best regards

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

Title:
  Qualcomm Atheros Device [168c:0042] (rev 30) not working on Ubuntu

Status in linux package in Ubuntu:
  Triaged

Bug description:
  Hi,
  Qualcomm Atheros Device [168c:0042] (rev 30) is not supported by linux 
kernal. Please add support.

  Thanks

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-61-generic 3.13.0-61.100
  ProcVersionSignature: Ubuntu 3.13.0-61.100-generic 3.13.11-ckt22
  Uname: Linux 3.13.0-61-generic i686
  ApportVersion: 2.14.1-0ubuntu3.11
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu14   1658 F pulseaudio
   /dev/snd/controlC1:  ubuntu14   1658 F pulseaudio
  CurrentDesktop: Unity
  Date: Wed Aug 12 20:31:24 2015
  HibernationDevice: RESUME=UUID=0483444a-0d9a-4215-b36b-4aee75fd9ec0
  InstallationDate: Installed on 2015-08-11 (0 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release i386 
(20140722.2)
  IwConfig:
   lono wireless extensions.
   
   eth0  no wireless extensions.
  MachineType: Acer Aspire E5-573
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-61-generic 
root=UUID=72a8a100-d5ec-4e9d-8bc5-45695001a29c ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-61-generic N/A
   linux-backports-modules-3.13.0-61-generic  N/A
   linux-firmware 1.127.15
  SourcePackage: linux
  StagingDrivers: rts5139
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/20/2015
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.11
  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.11:bd04/20/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/1484159/+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 1509776] Re: xubuntu 15.10 synaptics ps2 touchpad mouse cursor jumps

2015-11-03 Thread liontamer
Sorry I am being slow to think.  I tried installing kernel 4.30 in 15.04
in place of 3-3.19-0-31 and the bug is not present with either but it is
present in 15.10 with either 4.30 or 4.2.0-16.  This suggests to me that
the problem is not in the kernel.  I wonder if it is connected with
window snapping (although I have this turned off), not moving the window
but moving the cursor in anticipation?

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

Title:
  xubuntu 15.10 synaptics ps2 touchpad mouse cursor jumps

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  running live xubuntu 15.10 from usb stick.  Synaptics ps2 touchpad configured 
to act as simple mouse.  Mouse cursor suddenly and frequently jumps to screen 
edge with no reason.  Problem not present in 15.04 with same touchpad 
configuration but has occurred in some earlier versions.  Not prepared to 
upgrade as touchpad practically unusable.
  --- 
  ApportVersion: 2.19.1-0ubuntu3
  Architecture: amd64
  CasperVersion: 1.365
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: XFCE
  DistUpgraded: Fresh install
  DistroCodename: wily
  DistroRelease: Ubuntu 15.10
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation 4th Gen Core Processor Integrated Graphics Controller 
[8086:0416] (rev 06) (prog-if 00 [VGA controller])
 Subsystem: Pegatron Device [1b0a:2109]
 Subsystem: Pegatron Device [1b0a:2109]
  LiveMediaBuild: Xubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  MachineType: Novatech Ltd. Novatech 15.6 NSPIRE Laptop
  Package: xorg 1:7.7+7ubuntu4
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi initrd=/casper/initrd.lz 
file=/cdrom/preseed/username.seed boot=casper  quiet splash --- persistent
  ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3
  Tags:  wily ubuntu
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  Uname: Linux 4.2.0-16-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/05/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: C15B.610
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: C15B
  dmi.board.vendor: Novatech Ltd.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Novatech Ltd.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrC15B.610:bd12/05/2013:svnNovatechLtd.:pnNovatech15.6NSPIRELaptop:pvr1.0:rvnNovatechLtd.:rnC15B:rvr1.0:cvnNovatechLtd.:ct10:cvr1.0:
  dmi.product.name: Novatech 15.6 NSPIRE Laptop
  dmi.product.version: 1.0
  dmi.sys.vendor: Novatech Ltd.
  version.compiz: compiz N/A
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.64-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.0.2-1ubuntu4
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.0.2-1ubuntu4
  version.xserver-xorg-core: xserver-xorg-core 2:1.17.2-1ubuntu9
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.2-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 
1:7.5.0+git20150819-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20150808-0ubuntu4
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.11-1ubuntu3
  xserver.bootTime: Mon Nov  2 10:44:16 2015
  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)
   NOUVEAU(G0): Failed to initialise context object: 2D_NVC0 (0)
   NOUVEAU(G0): Error initialising acceleration.  Falling back to NoAccel
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id   18412 
   vendor AUO
  xserver.version: 2:1.17.2-1ubuntu9

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1509776/+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 1512415] Re: hpsa driver has problems with interacting with tape drives and media changer

2015-11-03 Thread Joseph Salisbury
** Changed in: linux (Ubuntu)
 Assignee: (unassigned) => Joseph Salisbury (jsalisbury)

** Changed in: linux (Ubuntu Trusty)
 Assignee: (unassigned) => Joseph Salisbury (jsalisbury)

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

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

** Tags added: trusty vivid

** Tags removed: 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/1512415

Title:
  hpsa driver has problems with interacting with tape drives and media
  changer

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

Bug description:
  There are multiple problems with tape drives when using a media changer on an 
hpsa controller.
  The problem appears for example when you label tapes in Dell Netvault.

  The problem does not appear in current vanilla kernel 4.2.3.

  After bisecting the problem the actually first good commit is: 
  3ce438df106826edde7ad724f3819716a3f0cf56 is the first bad commit
  commit 3ce438df106826edde7ad724f3819716a3f0cf56
  Author: Matt Gates 
  Date:   Wed Dec 4 17:10:36 2013 -0600

  [SCSI] hpsa: allow SCSI mid layer to handle unit attention

  We were clobbering the SCSI status and setting
  cmd->result = DID_SOFT_ERROR << 16; to get a retry,
  but better to let the mid layer handle the unit
  attention.

  Signed-off-by: Matt Gates 
  Acked-by: Stephen M. Cameron 
  Signed-off-by: James Bottomley 

  :04 04 a7ea924772d20fd6faa968a855cffdb864876264
  99765902968200eacf3a6ff1267b691a7bb24ebe M  drivers

  thanks to git bisecting rules:
  good = label errors = old kernel
  bad = no label errors = newer kernel

  Please consider backporting that fix to the 3.13 ubuntu kernel.
  --- 
  ApportVersion: 2.0.1-0ubuntu17.13
  Architecture: amd64
  DistroRelease: Ubuntu 12.04
  MarkForUpload: True
  Package: linux (not installed)
  ProcEnviron:
   LANGUAGE=en_US:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  Tags:  precise precise
  Uname: Linux 4.2.3-custom x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
  --- 
  ApportVersion: 2.0.1-0ubuntu17.13
  Architecture: amd64
  DistroRelease: Ubuntu 12.04
  MarkForUpload: True
  Package: linux-image-3.13.0-65-generic 3.13.0-65.106~precise1
  PackageArchitecture: amd64
  ProcEnviron:
   LANGUAGE=en_US:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  Tags:  precise
  Uname: Linux 4.2.3-custom x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1512415/+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 1509120] Re: Process accounting deadlock with idmapd callout when writing to NFSv4 mount

2015-11-03 Thread Dave Chiluk
** Changed in: nfs-utils (Ubuntu)
 Assignee: (unassigned) => Dave Chiluk (chiluk)

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

Title:
  Process accounting deadlock with idmapd callout when writing to NFSv4
  mount

Status in linux package in Ubuntu:
  In Progress
Status in nfs-utils package in Ubuntu:
  New

Bug description:
  ---Problem Description---
  System hang when process accounting to a NFSv4 mount.

  ---uname output---
  Linux ppc001 3.19.0-30-generic #34~14.04.1-Ubuntu SMP Fri Oct 2 22:21:52
  UTC 2015 ppc64le ppc64le ppc64le GNU/Linux

  ---Problem Details---

  We have a customer that is experiencing intermittent system hangs on
  their system.  After a bit of debug, it was discovered that the
  trigger was turning on process accounting and writing to a file hosted
  via an NFSv4 mount.  During the testing, several vmcores were
  captured, and the fingerprint indicates a mutex deadlock situation
  with process accounting.   In the most recent vmcore, it appears that
  the scenario is something like the following:

  1. PID: 4898 COMMAND: "ls" triggers a write to the process accounting file.
  2. The resulting NFS write needs idmapd information and calls out to idmapd
  3. The idmapd usermodehelper process triggers another process accounting 
update that blocks on the mutex being held by PID 4898.

  PID: 4898   TASK: c01fd26d7580  CPU: 7   COMMAND: "ls"
   #0 [c01fd274a950] __switch_to at c0015934
   #1 [c01fd274ab20] __switch_to at c0015934
   #2 [c01fd274ab80] __schedule at c0a11de8
   #3 [c01fd274ada0] schedule_timeout at c0a16284
   #4 [c01fd274ae90] wait_for_common at c0a1360c
   #5 [c01fd274af10] call_usermodehelper_exec at c00ccd38
   #6 [c01fd274af70] call_sbin_request_key at c0429258
   #7 [c01fd274b100] request_key_and_link at c042983c
   #8 [c01fd274b200] request_key at c0429978
   #9 [c01fd274b240] nfs_idmap_get_key at d0002ca8b0bc [nfsv4]
  #10 [c01fd274b2b0] nfs_map_name_to_uid at d0002ca8bbd0 [nfsv4]
  #11 [c01fd274b320] decode_getfattr_attrs at d0002ca7f59c [nfsv4]
  #12 [c01fd274b420] decode_getfattr_generic.constprop.96 at 
d0002ca7fd78 
  [nfsv4]
  #13 [c01fd274b4d0] nfs4_xdr_dec_getattr at d0002ca80738 [nfsv4]
  #14 [c01fd274b530] rpcauth_unwrap_resp at d0001fe67180 [sunrpc]
  #15 [c01fd274b600] call_decode at d0001fe527c8 [sunrpc]
  #16 [c01fd274b6b0] __rpc_execute at d0001fe64260 [sunrpc]
  #17 [c01fd274b790] rpc_run_task at d0001fe54a78 [sunrpc]
  #18 [c01fd274b7c0] nfs4_call_sync_sequence at d0002ca60960 [nfsv4]
  #19 [c01fd274b860] _nfs4_proc_getattr at d0002ca6217c [nfsv4]
  #20 [c01fd274b930] nfs4_proc_getattr at d0002ca6f494 [nfsv4]
  #21 [c01fd274b9a0] __nfs_revalidate_inode at d000202cf614 [nfs]
  #22 [c01fd274ba30] nfs_revalidate_file_size at d000202c9618 [nfs]
  #23 [c01fd274ba70] nfs_file_write at d000202cabdc [nfs]
  #24 [c01fd274bb00] new_sync_write at c02b3d9c
  #25 [c01fd274bbd0] __kernel_write at c02b3fec
  #26 [c01fd274bc20] do_acct_process at c0166b78
  #27 [c01fd274bcc0] acct_process at c016748c
  #28 [c01fd274bcf0] do_exit at c00b3660
  #29 [c01fd274bdc0] do_group_exit at c00b3b14
  #30 [c01fd274be00] sys_exit_group at c00b3bdc
  #31 [c01fd274be30] system_call at c0009258

  PID: 4900   TASK: c03c9946c180  CPU: 16  COMMAND: "kworker/u320:2"
   #0 [c03c994fb790] __switch_to at c0015934
   #1 [c03c994fb960] __switch_to at c0015934
   #2 [c03c994fb9c0] __schedule at c0a11de8
   #3 [c03c994fbbe0] schedule_preempt_disabled at c0a12980
   #4 [c03c994fbc00] __mutex_lock_slowpath at c0a14aec
   #5 [c03c994fbc80] mutex_lock at c0a14c4c
   #6 [c03c994fbcb0] acct_get at c01663ec
   #7 [c03c994fbcf0] acct_process at c0167480
   #8 [c03c994fbd20] do_exit at c00b3660
   #9 [c03c994fbdf0] call_usermodehelper at c00ccaf4
  #10 [c03c994fbe30] ret_from_kernel_thread at c000956c

  Historical bug data:

  from customer:

   am uploading a crash dump file from a lock up event that I just had.
  I was reminded on a status update call this morning that I never tried
  running process accounting since opening the ticket and updating the
  kernel. So, I tried that this morning. The first time I turned it on
  with the default output location and didn?t have any problems. Then I
  tried turning it on with the output going to our shared disk space,
  which is where I was originally sending it. I ran a couple commands
  that returned just fine, then when I ran a CUDA test program it didn?t
  

[Kernel-packages] [Bug 1509120] Re: Process accounting deadlock with idmapd callout when writing to NFSv4 mount

2015-11-03 Thread Dave Chiluk
I verified that keyutils is already included in vivid+ in order to fix
1449074.  So this shouldn't be too much of an issue to fix in trusty as
well.

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

Title:
  Process accounting deadlock with idmapd callout when writing to NFSv4
  mount

Status in linux package in Ubuntu:
  In Progress
Status in nfs-utils package in Ubuntu:
  New

Bug description:
  ---Problem Description---
  System hang when process accounting to a NFSv4 mount.

  ---uname output---
  Linux ppc001 3.19.0-30-generic #34~14.04.1-Ubuntu SMP Fri Oct 2 22:21:52
  UTC 2015 ppc64le ppc64le ppc64le GNU/Linux

  ---Problem Details---

  We have a customer that is experiencing intermittent system hangs on
  their system.  After a bit of debug, it was discovered that the
  trigger was turning on process accounting and writing to a file hosted
  via an NFSv4 mount.  During the testing, several vmcores were
  captured, and the fingerprint indicates a mutex deadlock situation
  with process accounting.   In the most recent vmcore, it appears that
  the scenario is something like the following:

  1. PID: 4898 COMMAND: "ls" triggers a write to the process accounting file.
  2. The resulting NFS write needs idmapd information and calls out to idmapd
  3. The idmapd usermodehelper process triggers another process accounting 
update that blocks on the mutex being held by PID 4898.

  PID: 4898   TASK: c01fd26d7580  CPU: 7   COMMAND: "ls"
   #0 [c01fd274a950] __switch_to at c0015934
   #1 [c01fd274ab20] __switch_to at c0015934
   #2 [c01fd274ab80] __schedule at c0a11de8
   #3 [c01fd274ada0] schedule_timeout at c0a16284
   #4 [c01fd274ae90] wait_for_common at c0a1360c
   #5 [c01fd274af10] call_usermodehelper_exec at c00ccd38
   #6 [c01fd274af70] call_sbin_request_key at c0429258
   #7 [c01fd274b100] request_key_and_link at c042983c
   #8 [c01fd274b200] request_key at c0429978
   #9 [c01fd274b240] nfs_idmap_get_key at d0002ca8b0bc [nfsv4]
  #10 [c01fd274b2b0] nfs_map_name_to_uid at d0002ca8bbd0 [nfsv4]
  #11 [c01fd274b320] decode_getfattr_attrs at d0002ca7f59c [nfsv4]
  #12 [c01fd274b420] decode_getfattr_generic.constprop.96 at 
d0002ca7fd78 
  [nfsv4]
  #13 [c01fd274b4d0] nfs4_xdr_dec_getattr at d0002ca80738 [nfsv4]
  #14 [c01fd274b530] rpcauth_unwrap_resp at d0001fe67180 [sunrpc]
  #15 [c01fd274b600] call_decode at d0001fe527c8 [sunrpc]
  #16 [c01fd274b6b0] __rpc_execute at d0001fe64260 [sunrpc]
  #17 [c01fd274b790] rpc_run_task at d0001fe54a78 [sunrpc]
  #18 [c01fd274b7c0] nfs4_call_sync_sequence at d0002ca60960 [nfsv4]
  #19 [c01fd274b860] _nfs4_proc_getattr at d0002ca6217c [nfsv4]
  #20 [c01fd274b930] nfs4_proc_getattr at d0002ca6f494 [nfsv4]
  #21 [c01fd274b9a0] __nfs_revalidate_inode at d000202cf614 [nfs]
  #22 [c01fd274ba30] nfs_revalidate_file_size at d000202c9618 [nfs]
  #23 [c01fd274ba70] nfs_file_write at d000202cabdc [nfs]
  #24 [c01fd274bb00] new_sync_write at c02b3d9c
  #25 [c01fd274bbd0] __kernel_write at c02b3fec
  #26 [c01fd274bc20] do_acct_process at c0166b78
  #27 [c01fd274bcc0] acct_process at c016748c
  #28 [c01fd274bcf0] do_exit at c00b3660
  #29 [c01fd274bdc0] do_group_exit at c00b3b14
  #30 [c01fd274be00] sys_exit_group at c00b3bdc
  #31 [c01fd274be30] system_call at c0009258

  PID: 4900   TASK: c03c9946c180  CPU: 16  COMMAND: "kworker/u320:2"
   #0 [c03c994fb790] __switch_to at c0015934
   #1 [c03c994fb960] __switch_to at c0015934
   #2 [c03c994fb9c0] __schedule at c0a11de8
   #3 [c03c994fbbe0] schedule_preempt_disabled at c0a12980
   #4 [c03c994fbc00] __mutex_lock_slowpath at c0a14aec
   #5 [c03c994fbc80] mutex_lock at c0a14c4c
   #6 [c03c994fbcb0] acct_get at c01663ec
   #7 [c03c994fbcf0] acct_process at c0167480
   #8 [c03c994fbd20] do_exit at c00b3660
   #9 [c03c994fbdf0] call_usermodehelper at c00ccaf4
  #10 [c03c994fbe30] ret_from_kernel_thread at c000956c

  Historical bug data:

  from customer:

   am uploading a crash dump file from a lock up event that I just had.
  I was reminded on a status update call this morning that I never tried
  running process accounting since opening the ticket and updating the
  kernel. So, I tried that this morning. The first time I turned it on
  with the default output location and didn?t have any problems. Then I
  tried turning it on with the output going to our shared disk space,
  which is where I was originally sending it. I ran a couple commands
  that returned 

[Kernel-packages] [Bug 1512848] Re: Radeon VCE Init Error

2015-11-03 Thread Joseph Salisbury
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.3 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.3-unstable/


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

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

Title:
  Radeon VCE Init Error

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

Bug description:
  Since upgrading to Ubuntu 15.10, I have encountered graphics
  performance issues, and have occasionally experienced lockups during
  boot.

  dmesg | grep radeon
  [2.103294] [drm] radeon kernel modesetting enabled.
  [2.114677] radeon :01:00.0: enabling device ( -> 0003)
  [2.226348] radeon :01:00.0: VRAM: 1024M 0x - 
0x3FFF (1024M used)
  [2.226349] radeon :01:00.0: GTT: 2048M 0x4000 - 
0xBFFF
  [2.226494] [drm] radeon: 1024M of VRAM memory ready
  [2.226506] [drm] radeon: 2048M of GTT memory ready.
  [2.232296] [drm] radeon: dpm initialized
  [2.234760] [drm] enabling PCIE gen 3 link speeds, disable with 
radeon.pcie_gen2=0
  [3.456910] radeon :01:00.0: WB enabled
  [3.456912] radeon :01:00.0: fence driver on ring 0 use gpu addr 
0x4c00 and cpu addr 0x88041663ac00
  [3.456914] radeon :01:00.0: fence driver on ring 1 use gpu addr 
0x4c04 and cpu addr 0x88041663ac04
  [3.456915] radeon :01:00.0: fence driver on ring 2 use gpu addr 
0x4c08 and cpu addr 0x88041663ac08
  [3.456916] radeon :01:00.0: fence driver on ring 3 use gpu addr 
0x4c0c and cpu addr 0x88041663ac0c
  [3.456918] radeon :01:00.0: fence driver on ring 4 use gpu addr 
0x4c10 and cpu addr 0x88041663ac10
  [3.457696] radeon :01:00.0: fence driver on ring 5 use gpu addr 
0x00075a18 and cpu addr 0xc90002035a18
  [3.558371] radeon :01:00.0: VCE init error (-110).
  [3.558376] radeon :01:00.0: radeon: MSI limited to 32-bit
  [3.558397] radeon :01:00.0: radeon: using MSI.
  [3.558421] [drm] radeon: irq initialized.
  [4.538452] radeon :01:00.0: No connectors reported connected with 
modes
  [4.539564] radeon :01:00.0: fb1: radeondrmfb frame buffer device
  [4.539598] [drm] Initialized radeon 2.43.0 20080528 for :01:00.0 on 
minor 1
  [   11.629124] [drm] enabling PCIE gen 3 link speeds, disable with 
radeon.pcie_gen2=0
  [   12.627048] radeon :01:00.0: WB enabled
  [   12.627050] radeon :01:00.0: fence driver on ring 0 use gpu addr 
0x4c00 and cpu addr 0x88041663ac00
  [   12.627051] radeon :01:00.0: fence driver on ring 1 use gpu addr 
0x4c04 and cpu addr 0x88041663ac04
  [   12.627053] radeon :01:00.0: fence driver on ring 2 use gpu addr 
0x4c08 and cpu addr 0x88041663ac08
  [   12.627054] radeon :01:00.0: fence driver on ring 3 use gpu addr 
0x4c0c and cpu addr 0x88041663ac0c
  [   12.627055] radeon :01:00.0: fence driver on ring 4 use gpu addr 
0x4c10 and cpu addr 0x88041663ac10
  [   12.627838] radeon :01:00.0: fence driver on ring 5 use gpu addr 
0x00075a18 and cpu addr 0xc90002035a18
  [   12.728529] radeon :01:00.0: VCE init error (-110).

  
  xrandr --listproviders
  Providers: number : 3
  Provider 0: id: 0x6a cap: 0x9, Source Output, Sink Offload crtcs: 4 outputs: 
5 associated providers: 2 name:Intel
  Provider 1: id: 0x41 cap: 0x6, Sink Output, Source Offload crtcs: 2 outputs: 
0 associated providers: 2 name:radeon
  Provider 2: id: 0x41 cap: 0x6, Sink Output, Source Offload crtcs: 2 outputs: 
0 associated providers: 2 name:radeon

  
  lspci -k 
  00:00.0 Host bridge: Intel Corporation 3rd Gen Core processor DRAM Controller 
(rev 09)
  Subsystem: Samsung Electronics Co Ltd Device c0e6
  Kernel driver in use: ivb_uncore
  00:01.0 PCI bridge: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor 
PCI Express Root Port (rev 09)
  Kernel driver in use: pcieport
  00:02.0 VGA compatible controller: Intel Corporation 3rd Gen Core processor 
Graphics Controller (rev 09)
  DeviceName:  Onboard IGD
  Subsystem: Samsung Electronics Co Ltd Device c0e6
  Kernel driver in use: i915
  01:00.0 Display controller: Advanced Micro Devices, Inc. [AMD/ATI] Mars 
[Radeon HD 8670A/8670M/8750M] 

[Kernel-packages] [Bug 1512848] ProcCpuinfo.txt

2015-11-03 Thread schmod
apport information

** Attachment added: "ProcCpuinfo.txt"
   
https://bugs.launchpad.net/bugs/1512848/+attachment/4512328/+files/ProcCpuinfo.txt

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

Title:
  Radeon VCE Init Error

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

Bug description:
  Since upgrading to Ubuntu 15.10, I have encountered graphics
  performance issues, and have occasionally experienced lockups during
  boot.

  dmesg | grep radeon
  [2.103294] [drm] radeon kernel modesetting enabled.
  [2.114677] radeon :01:00.0: enabling device ( -> 0003)
  [2.226348] radeon :01:00.0: VRAM: 1024M 0x - 
0x3FFF (1024M used)
  [2.226349] radeon :01:00.0: GTT: 2048M 0x4000 - 
0xBFFF
  [2.226494] [drm] radeon: 1024M of VRAM memory ready
  [2.226506] [drm] radeon: 2048M of GTT memory ready.
  [2.232296] [drm] radeon: dpm initialized
  [2.234760] [drm] enabling PCIE gen 3 link speeds, disable with 
radeon.pcie_gen2=0
  [3.456910] radeon :01:00.0: WB enabled
  [3.456912] radeon :01:00.0: fence driver on ring 0 use gpu addr 
0x4c00 and cpu addr 0x88041663ac00
  [3.456914] radeon :01:00.0: fence driver on ring 1 use gpu addr 
0x4c04 and cpu addr 0x88041663ac04
  [3.456915] radeon :01:00.0: fence driver on ring 2 use gpu addr 
0x4c08 and cpu addr 0x88041663ac08
  [3.456916] radeon :01:00.0: fence driver on ring 3 use gpu addr 
0x4c0c and cpu addr 0x88041663ac0c
  [3.456918] radeon :01:00.0: fence driver on ring 4 use gpu addr 
0x4c10 and cpu addr 0x88041663ac10
  [3.457696] radeon :01:00.0: fence driver on ring 5 use gpu addr 
0x00075a18 and cpu addr 0xc90002035a18
  [3.558371] radeon :01:00.0: VCE init error (-110).
  [3.558376] radeon :01:00.0: radeon: MSI limited to 32-bit
  [3.558397] radeon :01:00.0: radeon: using MSI.
  [3.558421] [drm] radeon: irq initialized.
  [4.538452] radeon :01:00.0: No connectors reported connected with 
modes
  [4.539564] radeon :01:00.0: fb1: radeondrmfb frame buffer device
  [4.539598] [drm] Initialized radeon 2.43.0 20080528 for :01:00.0 on 
minor 1
  [   11.629124] [drm] enabling PCIE gen 3 link speeds, disable with 
radeon.pcie_gen2=0
  [   12.627048] radeon :01:00.0: WB enabled
  [   12.627050] radeon :01:00.0: fence driver on ring 0 use gpu addr 
0x4c00 and cpu addr 0x88041663ac00
  [   12.627051] radeon :01:00.0: fence driver on ring 1 use gpu addr 
0x4c04 and cpu addr 0x88041663ac04
  [   12.627053] radeon :01:00.0: fence driver on ring 2 use gpu addr 
0x4c08 and cpu addr 0x88041663ac08
  [   12.627054] radeon :01:00.0: fence driver on ring 3 use gpu addr 
0x4c0c and cpu addr 0x88041663ac0c
  [   12.627055] radeon :01:00.0: fence driver on ring 4 use gpu addr 
0x4c10 and cpu addr 0x88041663ac10
  [   12.627838] radeon :01:00.0: fence driver on ring 5 use gpu addr 
0x00075a18 and cpu addr 0xc90002035a18
  [   12.728529] radeon :01:00.0: VCE init error (-110).

  
  xrandr --listproviders
  Providers: number : 3
  Provider 0: id: 0x6a cap: 0x9, Source Output, Sink Offload crtcs: 4 outputs: 
5 associated providers: 2 name:Intel
  Provider 1: id: 0x41 cap: 0x6, Sink Output, Source Offload crtcs: 2 outputs: 
0 associated providers: 2 name:radeon
  Provider 2: id: 0x41 cap: 0x6, Sink Output, Source Offload crtcs: 2 outputs: 
0 associated providers: 2 name:radeon

  
  lspci -k 
  00:00.0 Host bridge: Intel Corporation 3rd Gen Core processor DRAM Controller 
(rev 09)
  Subsystem: Samsung Electronics Co Ltd Device c0e6
  Kernel driver in use: ivb_uncore
  00:01.0 PCI bridge: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor 
PCI Express Root Port (rev 09)
  Kernel driver in use: pcieport
  00:02.0 VGA compatible controller: Intel Corporation 3rd Gen Core processor 
Graphics Controller (rev 09)
  DeviceName:  Onboard IGD
  Subsystem: Samsung Electronics Co Ltd Device c0e6
  Kernel driver in use: i915
  01:00.0 Display controller: Advanced Micro Devices, Inc. [AMD/ATI] Mars 
[Radeon HD 8670A/8670M/8750M] (rev ff)
  Kernel driver in use: radeon

  
  Possible upstream Debian bug: 
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=803087
  --- 
  ApportVersion: 2.19.1-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  aschmadel   2152 F pulseaudio
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 15.10
  EcryptfsInUse: Yes
  HibernationDevice: 

[Kernel-packages] [Bug 1512848] RfKill.txt

2015-11-03 Thread schmod
apport information

** Attachment added: "RfKill.txt"
   https://bugs.launchpad.net/bugs/1512848/+attachment/4512333/+files/RfKill.txt

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

Title:
  Radeon VCE Init Error

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

Bug description:
  Since upgrading to Ubuntu 15.10, I have encountered graphics
  performance issues, and have occasionally experienced lockups during
  boot.

  dmesg | grep radeon
  [2.103294] [drm] radeon kernel modesetting enabled.
  [2.114677] radeon :01:00.0: enabling device ( -> 0003)
  [2.226348] radeon :01:00.0: VRAM: 1024M 0x - 
0x3FFF (1024M used)
  [2.226349] radeon :01:00.0: GTT: 2048M 0x4000 - 
0xBFFF
  [2.226494] [drm] radeon: 1024M of VRAM memory ready
  [2.226506] [drm] radeon: 2048M of GTT memory ready.
  [2.232296] [drm] radeon: dpm initialized
  [2.234760] [drm] enabling PCIE gen 3 link speeds, disable with 
radeon.pcie_gen2=0
  [3.456910] radeon :01:00.0: WB enabled
  [3.456912] radeon :01:00.0: fence driver on ring 0 use gpu addr 
0x4c00 and cpu addr 0x88041663ac00
  [3.456914] radeon :01:00.0: fence driver on ring 1 use gpu addr 
0x4c04 and cpu addr 0x88041663ac04
  [3.456915] radeon :01:00.0: fence driver on ring 2 use gpu addr 
0x4c08 and cpu addr 0x88041663ac08
  [3.456916] radeon :01:00.0: fence driver on ring 3 use gpu addr 
0x4c0c and cpu addr 0x88041663ac0c
  [3.456918] radeon :01:00.0: fence driver on ring 4 use gpu addr 
0x4c10 and cpu addr 0x88041663ac10
  [3.457696] radeon :01:00.0: fence driver on ring 5 use gpu addr 
0x00075a18 and cpu addr 0xc90002035a18
  [3.558371] radeon :01:00.0: VCE init error (-110).
  [3.558376] radeon :01:00.0: radeon: MSI limited to 32-bit
  [3.558397] radeon :01:00.0: radeon: using MSI.
  [3.558421] [drm] radeon: irq initialized.
  [4.538452] radeon :01:00.0: No connectors reported connected with 
modes
  [4.539564] radeon :01:00.0: fb1: radeondrmfb frame buffer device
  [4.539598] [drm] Initialized radeon 2.43.0 20080528 for :01:00.0 on 
minor 1
  [   11.629124] [drm] enabling PCIE gen 3 link speeds, disable with 
radeon.pcie_gen2=0
  [   12.627048] radeon :01:00.0: WB enabled
  [   12.627050] radeon :01:00.0: fence driver on ring 0 use gpu addr 
0x4c00 and cpu addr 0x88041663ac00
  [   12.627051] radeon :01:00.0: fence driver on ring 1 use gpu addr 
0x4c04 and cpu addr 0x88041663ac04
  [   12.627053] radeon :01:00.0: fence driver on ring 2 use gpu addr 
0x4c08 and cpu addr 0x88041663ac08
  [   12.627054] radeon :01:00.0: fence driver on ring 3 use gpu addr 
0x4c0c and cpu addr 0x88041663ac0c
  [   12.627055] radeon :01:00.0: fence driver on ring 4 use gpu addr 
0x4c10 and cpu addr 0x88041663ac10
  [   12.627838] radeon :01:00.0: fence driver on ring 5 use gpu addr 
0x00075a18 and cpu addr 0xc90002035a18
  [   12.728529] radeon :01:00.0: VCE init error (-110).

  
  xrandr --listproviders
  Providers: number : 3
  Provider 0: id: 0x6a cap: 0x9, Source Output, Sink Offload crtcs: 4 outputs: 
5 associated providers: 2 name:Intel
  Provider 1: id: 0x41 cap: 0x6, Sink Output, Source Offload crtcs: 2 outputs: 
0 associated providers: 2 name:radeon
  Provider 2: id: 0x41 cap: 0x6, Sink Output, Source Offload crtcs: 2 outputs: 
0 associated providers: 2 name:radeon

  
  lspci -k 
  00:00.0 Host bridge: Intel Corporation 3rd Gen Core processor DRAM Controller 
(rev 09)
  Subsystem: Samsung Electronics Co Ltd Device c0e6
  Kernel driver in use: ivb_uncore
  00:01.0 PCI bridge: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor 
PCI Express Root Port (rev 09)
  Kernel driver in use: pcieport
  00:02.0 VGA compatible controller: Intel Corporation 3rd Gen Core processor 
Graphics Controller (rev 09)
  DeviceName:  Onboard IGD
  Subsystem: Samsung Electronics Co Ltd Device c0e6
  Kernel driver in use: i915
  01:00.0 Display controller: Advanced Micro Devices, Inc. [AMD/ATI] Mars 
[Radeon HD 8670A/8670M/8750M] (rev ff)
  Kernel driver in use: radeon

  
  Possible upstream Debian bug: 
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=803087
  --- 
  ApportVersion: 2.19.1-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  aschmadel   2152 F pulseaudio
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 15.10
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=5208c4c8-b199-4f3f-92ad-9addd6bd
  

[Kernel-packages] [Bug 1512848] CurrentDmesg.txt

2015-11-03 Thread schmod
apport information

** Attachment added: "CurrentDmesg.txt"
   
https://bugs.launchpad.net/bugs/1512848/+attachment/4512324/+files/CurrentDmesg.txt

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

Title:
  Radeon VCE Init Error

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

Bug description:
  Since upgrading to Ubuntu 15.10, I have encountered graphics
  performance issues, and have occasionally experienced lockups during
  boot.

  dmesg | grep radeon
  [2.103294] [drm] radeon kernel modesetting enabled.
  [2.114677] radeon :01:00.0: enabling device ( -> 0003)
  [2.226348] radeon :01:00.0: VRAM: 1024M 0x - 
0x3FFF (1024M used)
  [2.226349] radeon :01:00.0: GTT: 2048M 0x4000 - 
0xBFFF
  [2.226494] [drm] radeon: 1024M of VRAM memory ready
  [2.226506] [drm] radeon: 2048M of GTT memory ready.
  [2.232296] [drm] radeon: dpm initialized
  [2.234760] [drm] enabling PCIE gen 3 link speeds, disable with 
radeon.pcie_gen2=0
  [3.456910] radeon :01:00.0: WB enabled
  [3.456912] radeon :01:00.0: fence driver on ring 0 use gpu addr 
0x4c00 and cpu addr 0x88041663ac00
  [3.456914] radeon :01:00.0: fence driver on ring 1 use gpu addr 
0x4c04 and cpu addr 0x88041663ac04
  [3.456915] radeon :01:00.0: fence driver on ring 2 use gpu addr 
0x4c08 and cpu addr 0x88041663ac08
  [3.456916] radeon :01:00.0: fence driver on ring 3 use gpu addr 
0x4c0c and cpu addr 0x88041663ac0c
  [3.456918] radeon :01:00.0: fence driver on ring 4 use gpu addr 
0x4c10 and cpu addr 0x88041663ac10
  [3.457696] radeon :01:00.0: fence driver on ring 5 use gpu addr 
0x00075a18 and cpu addr 0xc90002035a18
  [3.558371] radeon :01:00.0: VCE init error (-110).
  [3.558376] radeon :01:00.0: radeon: MSI limited to 32-bit
  [3.558397] radeon :01:00.0: radeon: using MSI.
  [3.558421] [drm] radeon: irq initialized.
  [4.538452] radeon :01:00.0: No connectors reported connected with 
modes
  [4.539564] radeon :01:00.0: fb1: radeondrmfb frame buffer device
  [4.539598] [drm] Initialized radeon 2.43.0 20080528 for :01:00.0 on 
minor 1
  [   11.629124] [drm] enabling PCIE gen 3 link speeds, disable with 
radeon.pcie_gen2=0
  [   12.627048] radeon :01:00.0: WB enabled
  [   12.627050] radeon :01:00.0: fence driver on ring 0 use gpu addr 
0x4c00 and cpu addr 0x88041663ac00
  [   12.627051] radeon :01:00.0: fence driver on ring 1 use gpu addr 
0x4c04 and cpu addr 0x88041663ac04
  [   12.627053] radeon :01:00.0: fence driver on ring 2 use gpu addr 
0x4c08 and cpu addr 0x88041663ac08
  [   12.627054] radeon :01:00.0: fence driver on ring 3 use gpu addr 
0x4c0c and cpu addr 0x88041663ac0c
  [   12.627055] radeon :01:00.0: fence driver on ring 4 use gpu addr 
0x4c10 and cpu addr 0x88041663ac10
  [   12.627838] radeon :01:00.0: fence driver on ring 5 use gpu addr 
0x00075a18 and cpu addr 0xc90002035a18
  [   12.728529] radeon :01:00.0: VCE init error (-110).

  
  xrandr --listproviders
  Providers: number : 3
  Provider 0: id: 0x6a cap: 0x9, Source Output, Sink Offload crtcs: 4 outputs: 
5 associated providers: 2 name:Intel
  Provider 1: id: 0x41 cap: 0x6, Sink Output, Source Offload crtcs: 2 outputs: 
0 associated providers: 2 name:radeon
  Provider 2: id: 0x41 cap: 0x6, Sink Output, Source Offload crtcs: 2 outputs: 
0 associated providers: 2 name:radeon

  
  lspci -k 
  00:00.0 Host bridge: Intel Corporation 3rd Gen Core processor DRAM Controller 
(rev 09)
  Subsystem: Samsung Electronics Co Ltd Device c0e6
  Kernel driver in use: ivb_uncore
  00:01.0 PCI bridge: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor 
PCI Express Root Port (rev 09)
  Kernel driver in use: pcieport
  00:02.0 VGA compatible controller: Intel Corporation 3rd Gen Core processor 
Graphics Controller (rev 09)
  DeviceName:  Onboard IGD
  Subsystem: Samsung Electronics Co Ltd Device c0e6
  Kernel driver in use: i915
  01:00.0 Display controller: Advanced Micro Devices, Inc. [AMD/ATI] Mars 
[Radeon HD 8670A/8670M/8750M] (rev ff)
  Kernel driver in use: radeon

  
  Possible upstream Debian bug: 
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=803087
  --- 
  ApportVersion: 2.19.1-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  aschmadel   2152 F pulseaudio
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 15.10
  EcryptfsInUse: Yes
  HibernationDevice: 

[Kernel-packages] [Bug 1512848] UdevDb.txt

2015-11-03 Thread schmod
apport information

** Attachment added: "UdevDb.txt"
   https://bugs.launchpad.net/bugs/1512848/+attachment/4512334/+files/UdevDb.txt

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

Title:
  Radeon VCE Init Error

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

Bug description:
  Since upgrading to Ubuntu 15.10, I have encountered graphics
  performance issues, and have occasionally experienced lockups during
  boot.

  dmesg | grep radeon
  [2.103294] [drm] radeon kernel modesetting enabled.
  [2.114677] radeon :01:00.0: enabling device ( -> 0003)
  [2.226348] radeon :01:00.0: VRAM: 1024M 0x - 
0x3FFF (1024M used)
  [2.226349] radeon :01:00.0: GTT: 2048M 0x4000 - 
0xBFFF
  [2.226494] [drm] radeon: 1024M of VRAM memory ready
  [2.226506] [drm] radeon: 2048M of GTT memory ready.
  [2.232296] [drm] radeon: dpm initialized
  [2.234760] [drm] enabling PCIE gen 3 link speeds, disable with 
radeon.pcie_gen2=0
  [3.456910] radeon :01:00.0: WB enabled
  [3.456912] radeon :01:00.0: fence driver on ring 0 use gpu addr 
0x4c00 and cpu addr 0x88041663ac00
  [3.456914] radeon :01:00.0: fence driver on ring 1 use gpu addr 
0x4c04 and cpu addr 0x88041663ac04
  [3.456915] radeon :01:00.0: fence driver on ring 2 use gpu addr 
0x4c08 and cpu addr 0x88041663ac08
  [3.456916] radeon :01:00.0: fence driver on ring 3 use gpu addr 
0x4c0c and cpu addr 0x88041663ac0c
  [3.456918] radeon :01:00.0: fence driver on ring 4 use gpu addr 
0x4c10 and cpu addr 0x88041663ac10
  [3.457696] radeon :01:00.0: fence driver on ring 5 use gpu addr 
0x00075a18 and cpu addr 0xc90002035a18
  [3.558371] radeon :01:00.0: VCE init error (-110).
  [3.558376] radeon :01:00.0: radeon: MSI limited to 32-bit
  [3.558397] radeon :01:00.0: radeon: using MSI.
  [3.558421] [drm] radeon: irq initialized.
  [4.538452] radeon :01:00.0: No connectors reported connected with 
modes
  [4.539564] radeon :01:00.0: fb1: radeondrmfb frame buffer device
  [4.539598] [drm] Initialized radeon 2.43.0 20080528 for :01:00.0 on 
minor 1
  [   11.629124] [drm] enabling PCIE gen 3 link speeds, disable with 
radeon.pcie_gen2=0
  [   12.627048] radeon :01:00.0: WB enabled
  [   12.627050] radeon :01:00.0: fence driver on ring 0 use gpu addr 
0x4c00 and cpu addr 0x88041663ac00
  [   12.627051] radeon :01:00.0: fence driver on ring 1 use gpu addr 
0x4c04 and cpu addr 0x88041663ac04
  [   12.627053] radeon :01:00.0: fence driver on ring 2 use gpu addr 
0x4c08 and cpu addr 0x88041663ac08
  [   12.627054] radeon :01:00.0: fence driver on ring 3 use gpu addr 
0x4c0c and cpu addr 0x88041663ac0c
  [   12.627055] radeon :01:00.0: fence driver on ring 4 use gpu addr 
0x4c10 and cpu addr 0x88041663ac10
  [   12.627838] radeon :01:00.0: fence driver on ring 5 use gpu addr 
0x00075a18 and cpu addr 0xc90002035a18
  [   12.728529] radeon :01:00.0: VCE init error (-110).

  
  xrandr --listproviders
  Providers: number : 3
  Provider 0: id: 0x6a cap: 0x9, Source Output, Sink Offload crtcs: 4 outputs: 
5 associated providers: 2 name:Intel
  Provider 1: id: 0x41 cap: 0x6, Sink Output, Source Offload crtcs: 2 outputs: 
0 associated providers: 2 name:radeon
  Provider 2: id: 0x41 cap: 0x6, Sink Output, Source Offload crtcs: 2 outputs: 
0 associated providers: 2 name:radeon

  
  lspci -k 
  00:00.0 Host bridge: Intel Corporation 3rd Gen Core processor DRAM Controller 
(rev 09)
  Subsystem: Samsung Electronics Co Ltd Device c0e6
  Kernel driver in use: ivb_uncore
  00:01.0 PCI bridge: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor 
PCI Express Root Port (rev 09)
  Kernel driver in use: pcieport
  00:02.0 VGA compatible controller: Intel Corporation 3rd Gen Core processor 
Graphics Controller (rev 09)
  DeviceName:  Onboard IGD
  Subsystem: Samsung Electronics Co Ltd Device c0e6
  Kernel driver in use: i915
  01:00.0 Display controller: Advanced Micro Devices, Inc. [AMD/ATI] Mars 
[Radeon HD 8670A/8670M/8750M] (rev ff)
  Kernel driver in use: radeon

  
  Possible upstream Debian bug: 
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=803087
  --- 
  ApportVersion: 2.19.1-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  aschmadel   2152 F pulseaudio
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 15.10
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=5208c4c8-b199-4f3f-92ad-9addd6bd
  

[Kernel-packages] [Bug 1512848] Re: Radeon VCE Init Error

2015-11-03 Thread schmod
apport information

** Tags added: apport-collected wily

** Description changed:

  Since upgrading to Ubuntu 15.10, I have encountered graphics performance
  issues, and have occasionally experienced lockups during boot.
  
  dmesg | grep radeon
  [2.103294] [drm] radeon kernel modesetting enabled.
  [2.114677] radeon :01:00.0: enabling device ( -> 0003)
  [2.226348] radeon :01:00.0: VRAM: 1024M 0x - 
0x3FFF (1024M used)
  [2.226349] radeon :01:00.0: GTT: 2048M 0x4000 - 
0xBFFF
  [2.226494] [drm] radeon: 1024M of VRAM memory ready
  [2.226506] [drm] radeon: 2048M of GTT memory ready.
  [2.232296] [drm] radeon: dpm initialized
  [2.234760] [drm] enabling PCIE gen 3 link speeds, disable with 
radeon.pcie_gen2=0
  [3.456910] radeon :01:00.0: WB enabled
  [3.456912] radeon :01:00.0: fence driver on ring 0 use gpu addr 
0x4c00 and cpu addr 0x88041663ac00
  [3.456914] radeon :01:00.0: fence driver on ring 1 use gpu addr 
0x4c04 and cpu addr 0x88041663ac04
  [3.456915] radeon :01:00.0: fence driver on ring 2 use gpu addr 
0x4c08 and cpu addr 0x88041663ac08
  [3.456916] radeon :01:00.0: fence driver on ring 3 use gpu addr 
0x4c0c and cpu addr 0x88041663ac0c
  [3.456918] radeon :01:00.0: fence driver on ring 4 use gpu addr 
0x4c10 and cpu addr 0x88041663ac10
  [3.457696] radeon :01:00.0: fence driver on ring 5 use gpu addr 
0x00075a18 and cpu addr 0xc90002035a18
  [3.558371] radeon :01:00.0: VCE init error (-110).
  [3.558376] radeon :01:00.0: radeon: MSI limited to 32-bit
  [3.558397] radeon :01:00.0: radeon: using MSI.
  [3.558421] [drm] radeon: irq initialized.
  [4.538452] radeon :01:00.0: No connectors reported connected with 
modes
  [4.539564] radeon :01:00.0: fb1: radeondrmfb frame buffer device
  [4.539598] [drm] Initialized radeon 2.43.0 20080528 for :01:00.0 on 
minor 1
  [   11.629124] [drm] enabling PCIE gen 3 link speeds, disable with 
radeon.pcie_gen2=0
  [   12.627048] radeon :01:00.0: WB enabled
  [   12.627050] radeon :01:00.0: fence driver on ring 0 use gpu addr 
0x4c00 and cpu addr 0x88041663ac00
  [   12.627051] radeon :01:00.0: fence driver on ring 1 use gpu addr 
0x4c04 and cpu addr 0x88041663ac04
  [   12.627053] radeon :01:00.0: fence driver on ring 2 use gpu addr 
0x4c08 and cpu addr 0x88041663ac08
  [   12.627054] radeon :01:00.0: fence driver on ring 3 use gpu addr 
0x4c0c and cpu addr 0x88041663ac0c
  [   12.627055] radeon :01:00.0: fence driver on ring 4 use gpu addr 
0x4c10 and cpu addr 0x88041663ac10
  [   12.627838] radeon :01:00.0: fence driver on ring 5 use gpu addr 
0x00075a18 and cpu addr 0xc90002035a18
  [   12.728529] radeon :01:00.0: VCE init error (-110).
  
  
  xrandr --listproviders
  Providers: number : 3
  Provider 0: id: 0x6a cap: 0x9, Source Output, Sink Offload crtcs: 4 outputs: 
5 associated providers: 2 name:Intel
  Provider 1: id: 0x41 cap: 0x6, Sink Output, Source Offload crtcs: 2 outputs: 
0 associated providers: 2 name:radeon
  Provider 2: id: 0x41 cap: 0x6, Sink Output, Source Offload crtcs: 2 outputs: 
0 associated providers: 2 name:radeon
  
  
  lspci -k 
  00:00.0 Host bridge: Intel Corporation 3rd Gen Core processor DRAM Controller 
(rev 09)
  Subsystem: Samsung Electronics Co Ltd Device c0e6
  Kernel driver in use: ivb_uncore
  00:01.0 PCI bridge: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor 
PCI Express Root Port (rev 09)
  Kernel driver in use: pcieport
  00:02.0 VGA compatible controller: Intel Corporation 3rd Gen Core processor 
Graphics Controller (rev 09)
  DeviceName:  Onboard IGD
  Subsystem: Samsung Electronics Co Ltd Device c0e6
  Kernel driver in use: i915
  01:00.0 Display controller: Advanced Micro Devices, Inc. [AMD/ATI] Mars 
[Radeon HD 8670A/8670M/8750M] (rev ff)
  Kernel driver in use: radeon
  
  
  Possible upstream Debian bug: 
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=803087
+ --- 
+ ApportVersion: 2.19.1-0ubuntu4
+ Architecture: amd64
+ AudioDevicesInUse:
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC0:  aschmadel   2152 F pulseaudio
+ CurrentDesktop: KDE
+ DistroRelease: Ubuntu 15.10
+ EcryptfsInUse: Yes
+ HibernationDevice: RESUME=UUID=5208c4c8-b199-4f3f-92ad-9addd6bd
+ InstallationDate: Installed on 2013-09-23 (771 days ago)
+ InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
+ JournalErrors:
+  No journal files were found.
+  -- No entries --
+ MachineType: SAMSUNG ELECTRONICS CO., LTD. 870Z5E/880Z5E/680Z5E
+ Package: linux (not installed)
+ ProcFB:
+  0 inteldrmfb
+  1 radeondrmfb
+ 

[Kernel-packages] [Bug 1512848] CRDA.txt

2015-11-03 Thread schmod
apport information

** Attachment added: "CRDA.txt"
   https://bugs.launchpad.net/bugs/1512848/+attachment/4512323/+files/CRDA.txt

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

Title:
  Radeon VCE Init Error

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

Bug description:
  Since upgrading to Ubuntu 15.10, I have encountered graphics
  performance issues, and have occasionally experienced lockups during
  boot.

  dmesg | grep radeon
  [2.103294] [drm] radeon kernel modesetting enabled.
  [2.114677] radeon :01:00.0: enabling device ( -> 0003)
  [2.226348] radeon :01:00.0: VRAM: 1024M 0x - 
0x3FFF (1024M used)
  [2.226349] radeon :01:00.0: GTT: 2048M 0x4000 - 
0xBFFF
  [2.226494] [drm] radeon: 1024M of VRAM memory ready
  [2.226506] [drm] radeon: 2048M of GTT memory ready.
  [2.232296] [drm] radeon: dpm initialized
  [2.234760] [drm] enabling PCIE gen 3 link speeds, disable with 
radeon.pcie_gen2=0
  [3.456910] radeon :01:00.0: WB enabled
  [3.456912] radeon :01:00.0: fence driver on ring 0 use gpu addr 
0x4c00 and cpu addr 0x88041663ac00
  [3.456914] radeon :01:00.0: fence driver on ring 1 use gpu addr 
0x4c04 and cpu addr 0x88041663ac04
  [3.456915] radeon :01:00.0: fence driver on ring 2 use gpu addr 
0x4c08 and cpu addr 0x88041663ac08
  [3.456916] radeon :01:00.0: fence driver on ring 3 use gpu addr 
0x4c0c and cpu addr 0x88041663ac0c
  [3.456918] radeon :01:00.0: fence driver on ring 4 use gpu addr 
0x4c10 and cpu addr 0x88041663ac10
  [3.457696] radeon :01:00.0: fence driver on ring 5 use gpu addr 
0x00075a18 and cpu addr 0xc90002035a18
  [3.558371] radeon :01:00.0: VCE init error (-110).
  [3.558376] radeon :01:00.0: radeon: MSI limited to 32-bit
  [3.558397] radeon :01:00.0: radeon: using MSI.
  [3.558421] [drm] radeon: irq initialized.
  [4.538452] radeon :01:00.0: No connectors reported connected with 
modes
  [4.539564] radeon :01:00.0: fb1: radeondrmfb frame buffer device
  [4.539598] [drm] Initialized radeon 2.43.0 20080528 for :01:00.0 on 
minor 1
  [   11.629124] [drm] enabling PCIE gen 3 link speeds, disable with 
radeon.pcie_gen2=0
  [   12.627048] radeon :01:00.0: WB enabled
  [   12.627050] radeon :01:00.0: fence driver on ring 0 use gpu addr 
0x4c00 and cpu addr 0x88041663ac00
  [   12.627051] radeon :01:00.0: fence driver on ring 1 use gpu addr 
0x4c04 and cpu addr 0x88041663ac04
  [   12.627053] radeon :01:00.0: fence driver on ring 2 use gpu addr 
0x4c08 and cpu addr 0x88041663ac08
  [   12.627054] radeon :01:00.0: fence driver on ring 3 use gpu addr 
0x4c0c and cpu addr 0x88041663ac0c
  [   12.627055] radeon :01:00.0: fence driver on ring 4 use gpu addr 
0x4c10 and cpu addr 0x88041663ac10
  [   12.627838] radeon :01:00.0: fence driver on ring 5 use gpu addr 
0x00075a18 and cpu addr 0xc90002035a18
  [   12.728529] radeon :01:00.0: VCE init error (-110).

  
  xrandr --listproviders
  Providers: number : 3
  Provider 0: id: 0x6a cap: 0x9, Source Output, Sink Offload crtcs: 4 outputs: 
5 associated providers: 2 name:Intel
  Provider 1: id: 0x41 cap: 0x6, Sink Output, Source Offload crtcs: 2 outputs: 
0 associated providers: 2 name:radeon
  Provider 2: id: 0x41 cap: 0x6, Sink Output, Source Offload crtcs: 2 outputs: 
0 associated providers: 2 name:radeon

  
  lspci -k 
  00:00.0 Host bridge: Intel Corporation 3rd Gen Core processor DRAM Controller 
(rev 09)
  Subsystem: Samsung Electronics Co Ltd Device c0e6
  Kernel driver in use: ivb_uncore
  00:01.0 PCI bridge: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor 
PCI Express Root Port (rev 09)
  Kernel driver in use: pcieport
  00:02.0 VGA compatible controller: Intel Corporation 3rd Gen Core processor 
Graphics Controller (rev 09)
  DeviceName:  Onboard IGD
  Subsystem: Samsung Electronics Co Ltd Device c0e6
  Kernel driver in use: i915
  01:00.0 Display controller: Advanced Micro Devices, Inc. [AMD/ATI] Mars 
[Radeon HD 8670A/8670M/8750M] (rev ff)
  Kernel driver in use: radeon

  
  Possible upstream Debian bug: 
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=803087
  --- 
  ApportVersion: 2.19.1-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  aschmadel   2152 F pulseaudio
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 15.10
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=5208c4c8-b199-4f3f-92ad-9addd6bd
  

[Kernel-packages] [Bug 1512848] ProcInterrupts.txt

2015-11-03 Thread schmod
apport information

** Attachment added: "ProcInterrupts.txt"
   
https://bugs.launchpad.net/bugs/1512848/+attachment/4512330/+files/ProcInterrupts.txt

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

Title:
  Radeon VCE Init Error

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

Bug description:
  Since upgrading to Ubuntu 15.10, I have encountered graphics
  performance issues, and have occasionally experienced lockups during
  boot.

  dmesg | grep radeon
  [2.103294] [drm] radeon kernel modesetting enabled.
  [2.114677] radeon :01:00.0: enabling device ( -> 0003)
  [2.226348] radeon :01:00.0: VRAM: 1024M 0x - 
0x3FFF (1024M used)
  [2.226349] radeon :01:00.0: GTT: 2048M 0x4000 - 
0xBFFF
  [2.226494] [drm] radeon: 1024M of VRAM memory ready
  [2.226506] [drm] radeon: 2048M of GTT memory ready.
  [2.232296] [drm] radeon: dpm initialized
  [2.234760] [drm] enabling PCIE gen 3 link speeds, disable with 
radeon.pcie_gen2=0
  [3.456910] radeon :01:00.0: WB enabled
  [3.456912] radeon :01:00.0: fence driver on ring 0 use gpu addr 
0x4c00 and cpu addr 0x88041663ac00
  [3.456914] radeon :01:00.0: fence driver on ring 1 use gpu addr 
0x4c04 and cpu addr 0x88041663ac04
  [3.456915] radeon :01:00.0: fence driver on ring 2 use gpu addr 
0x4c08 and cpu addr 0x88041663ac08
  [3.456916] radeon :01:00.0: fence driver on ring 3 use gpu addr 
0x4c0c and cpu addr 0x88041663ac0c
  [3.456918] radeon :01:00.0: fence driver on ring 4 use gpu addr 
0x4c10 and cpu addr 0x88041663ac10
  [3.457696] radeon :01:00.0: fence driver on ring 5 use gpu addr 
0x00075a18 and cpu addr 0xc90002035a18
  [3.558371] radeon :01:00.0: VCE init error (-110).
  [3.558376] radeon :01:00.0: radeon: MSI limited to 32-bit
  [3.558397] radeon :01:00.0: radeon: using MSI.
  [3.558421] [drm] radeon: irq initialized.
  [4.538452] radeon :01:00.0: No connectors reported connected with 
modes
  [4.539564] radeon :01:00.0: fb1: radeondrmfb frame buffer device
  [4.539598] [drm] Initialized radeon 2.43.0 20080528 for :01:00.0 on 
minor 1
  [   11.629124] [drm] enabling PCIE gen 3 link speeds, disable with 
radeon.pcie_gen2=0
  [   12.627048] radeon :01:00.0: WB enabled
  [   12.627050] radeon :01:00.0: fence driver on ring 0 use gpu addr 
0x4c00 and cpu addr 0x88041663ac00
  [   12.627051] radeon :01:00.0: fence driver on ring 1 use gpu addr 
0x4c04 and cpu addr 0x88041663ac04
  [   12.627053] radeon :01:00.0: fence driver on ring 2 use gpu addr 
0x4c08 and cpu addr 0x88041663ac08
  [   12.627054] radeon :01:00.0: fence driver on ring 3 use gpu addr 
0x4c0c and cpu addr 0x88041663ac0c
  [   12.627055] radeon :01:00.0: fence driver on ring 4 use gpu addr 
0x4c10 and cpu addr 0x88041663ac10
  [   12.627838] radeon :01:00.0: fence driver on ring 5 use gpu addr 
0x00075a18 and cpu addr 0xc90002035a18
  [   12.728529] radeon :01:00.0: VCE init error (-110).

  
  xrandr --listproviders
  Providers: number : 3
  Provider 0: id: 0x6a cap: 0x9, Source Output, Sink Offload crtcs: 4 outputs: 
5 associated providers: 2 name:Intel
  Provider 1: id: 0x41 cap: 0x6, Sink Output, Source Offload crtcs: 2 outputs: 
0 associated providers: 2 name:radeon
  Provider 2: id: 0x41 cap: 0x6, Sink Output, Source Offload crtcs: 2 outputs: 
0 associated providers: 2 name:radeon

  
  lspci -k 
  00:00.0 Host bridge: Intel Corporation 3rd Gen Core processor DRAM Controller 
(rev 09)
  Subsystem: Samsung Electronics Co Ltd Device c0e6
  Kernel driver in use: ivb_uncore
  00:01.0 PCI bridge: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor 
PCI Express Root Port (rev 09)
  Kernel driver in use: pcieport
  00:02.0 VGA compatible controller: Intel Corporation 3rd Gen Core processor 
Graphics Controller (rev 09)
  DeviceName:  Onboard IGD
  Subsystem: Samsung Electronics Co Ltd Device c0e6
  Kernel driver in use: i915
  01:00.0 Display controller: Advanced Micro Devices, Inc. [AMD/ATI] Mars 
[Radeon HD 8670A/8670M/8750M] (rev ff)
  Kernel driver in use: radeon

  
  Possible upstream Debian bug: 
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=803087
  --- 
  ApportVersion: 2.19.1-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  aschmadel   2152 F pulseaudio
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 15.10
  EcryptfsInUse: Yes
  HibernationDevice: 

[Kernel-packages] [Bug 1492146] Re: igb Detected Tx Unit Hang

2015-11-03 Thread Mark Sapiro
I spoke too soon. It took about 20 minutes for the issue to develop, but
it has reappeared just as before with the new kernel.

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

Title:
  igb Detected Tx Unit Hang

Status in linux-lts-utopic package in Ubuntu:
  Confirmed
Status in linux-lts-utopic source package in Trusty:
  Fix Released

Bug description:
  Hello!

  Have a:

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

  with kenel 3.16.0-46-generic.

  Today i do dist-upgrade and kernel was upgraded to 3.16.0-48-generic
  version.

  After reboot i've got this:

  Sep  4 09:02:52 mail kernel: [  310.616324] igb :02:00.0 em1: Reset 
adapter Sep  4 09:02:52 mail kernel: [  310.831157] igb :02:00.1 em2: Reset 
adapter Sep  4 09:02:56 mail kernel: [  315.154686] igb :02:00.0 em1: igb: 
em1 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX Sep  4 09:02:56 mail 
kernel: [  315.202651] igb :02:00.1 em2: igb: em2 NIC Link is Up 1000 Mbps 
Full Duplex, Flow Control: RX Sep  4 09:03:02 mail kernel: [  321.608099] igb 
:02:00.0: Detected Tx Unit Hang
  Sep  4 09:03:02 mail kernel: [  321.608099]   Tx Queue <6>
  Sep  4 09:03:02 mail kernel: [  321.608099]   TDH  <23>
  Sep  4 09:03:02 mail kernel: [  321.608099]   TDT  <23>
  Sep  4 09:03:02 mail kernel: [  321.608099]   next_to_use  <25>
  Sep  4 09:03:02 mail kernel: [  321.608099]   next_to_clean<23>
  Sep  4 09:03:02 mail kernel: [  321.608099] buffer_info[next_to_clean]
  Sep  4 09:03:02 mail kernel: [  321.608099]   time_stamp   <112af>
  Sep  4 09:03:02 mail kernel: [  321.608099]   next_to_watch

  Sep  4 09:03:02 mail kernel: [  321.608099]   jiffies  <11531>
  Sep  4 09:03:02 mail kernel: [  321.608099]   desc.status  <120200>
  Sep  4 09:03:04 mail kernel: [  323.607349] igb :02:00.0: Detected Tx 
Unit Hang
  Sep  4 09:03:04 mail kernel: [  323.607349]   Tx Queue <6>
  Sep  4 09:03:04 mail kernel: [  323.607349]   TDH  <23>
  Sep  4 09:03:04 mail kernel: [  323.607349]   TDT  <23>
  Sep  4 09:03:04 mail kernel: [  323.607349]   next_to_use  <25>
  Sep  4 09:03:04 mail kernel: [  323.607349]   next_to_clean<23>
  Sep  4 09:03:04 mail kernel: [  323.607349] buffer_info[next_to_clean]
  Sep  4 09:03:04 mail kernel: [  323.607349]   time_stamp   <112af>
  Sep  4 09:03:04 mail kernel: [  323.607349]   next_to_watch

  Sep  4 09:03:04 mail kernel: [  323.607349]   jiffies  <11725>
  Sep  4 09:03:04 mail kernel: [  323.607349]   desc.status  <120200>
  Sep  4 09:03:06 mail kernel: [  325.606602] igb :02:00.0: Detected Tx 
Unit Hang
  Sep  4 09:03:06 mail kernel: [  325.606602]   Tx Queue <6>
  Sep  4 09:03:06 mail kernel: [  325.606602]   TDH  <23>
  Sep  4 09:03:06 mail kernel: [  325.606602]   TDT  <23>
  Sep  4 09:03:06 mail kernel: [  325.606602]   next_to_use  <25>
  Sep  4 09:03:06 mail kernel: [  325.606602]   next_to_clean<23>
  Sep  4 09:03:06 mail kernel: [  325.606602] buffer_info[next_to_clean]
  Sep  4 09:03:06 mail kernel: [  325.606602]   time_stamp   <112af>
  Sep  4 09:03:06 mail kernel: [  325.606602]   next_to_watch

  Sep  4 09:03:06 mail kernel: [  325.606602]   jiffies  <11919>
  Sep  4 09:03:06 mail kernel: [  325.606602]   desc.status  <120200>

  All network connections droped after that. System still unusable.

  Only after boot with old linux-image-3.16.0-46-generic my production
  mail server can work.

  It's a critical bug for me, can anybody help me?

  ethtool -i em1
  driver: igb
  version: 5.2.13-k
  firmware-version: 1.61, 0x8cd5, 1.949.0
  bus-info: :02:00.0
  supports-statistics: yes
  supports-test: yes
  supports-eeprom-access: yes
  supports-register-dump: yes
  supports-priv-flags: no

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-lts-utopic/+bug/1492146/+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 1492146] Re: igb Detected Tx Unit Hang

2015-11-03 Thread Mark Sapiro
I have installed

linux-image-3.16.0-52-generic_3.16.0-52.71~14.04.1_amd64.deb and
linux-image-extra-3.16.0-52-generic_3.16.0-52.71~14.04.1_amd64.deb

from http://kernel.ubuntu.com/~jsalisbury/lp1454892/lts-backport-utopic/
and rebooted and I do not see the issue reported in this bug. It appears
at least for me that the above kernel does not have the regression.

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

Title:
  igb Detected Tx Unit Hang

Status in linux-lts-utopic package in Ubuntu:
  Confirmed
Status in linux-lts-utopic source package in Trusty:
  Fix Released

Bug description:
  Hello!

  Have a:

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

  with kenel 3.16.0-46-generic.

  Today i do dist-upgrade and kernel was upgraded to 3.16.0-48-generic
  version.

  After reboot i've got this:

  Sep  4 09:02:52 mail kernel: [  310.616324] igb :02:00.0 em1: Reset 
adapter Sep  4 09:02:52 mail kernel: [  310.831157] igb :02:00.1 em2: Reset 
adapter Sep  4 09:02:56 mail kernel: [  315.154686] igb :02:00.0 em1: igb: 
em1 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX Sep  4 09:02:56 mail 
kernel: [  315.202651] igb :02:00.1 em2: igb: em2 NIC Link is Up 1000 Mbps 
Full Duplex, Flow Control: RX Sep  4 09:03:02 mail kernel: [  321.608099] igb 
:02:00.0: Detected Tx Unit Hang
  Sep  4 09:03:02 mail kernel: [  321.608099]   Tx Queue <6>
  Sep  4 09:03:02 mail kernel: [  321.608099]   TDH  <23>
  Sep  4 09:03:02 mail kernel: [  321.608099]   TDT  <23>
  Sep  4 09:03:02 mail kernel: [  321.608099]   next_to_use  <25>
  Sep  4 09:03:02 mail kernel: [  321.608099]   next_to_clean<23>
  Sep  4 09:03:02 mail kernel: [  321.608099] buffer_info[next_to_clean]
  Sep  4 09:03:02 mail kernel: [  321.608099]   time_stamp   <112af>
  Sep  4 09:03:02 mail kernel: [  321.608099]   next_to_watch

  Sep  4 09:03:02 mail kernel: [  321.608099]   jiffies  <11531>
  Sep  4 09:03:02 mail kernel: [  321.608099]   desc.status  <120200>
  Sep  4 09:03:04 mail kernel: [  323.607349] igb :02:00.0: Detected Tx 
Unit Hang
  Sep  4 09:03:04 mail kernel: [  323.607349]   Tx Queue <6>
  Sep  4 09:03:04 mail kernel: [  323.607349]   TDH  <23>
  Sep  4 09:03:04 mail kernel: [  323.607349]   TDT  <23>
  Sep  4 09:03:04 mail kernel: [  323.607349]   next_to_use  <25>
  Sep  4 09:03:04 mail kernel: [  323.607349]   next_to_clean<23>
  Sep  4 09:03:04 mail kernel: [  323.607349] buffer_info[next_to_clean]
  Sep  4 09:03:04 mail kernel: [  323.607349]   time_stamp   <112af>
  Sep  4 09:03:04 mail kernel: [  323.607349]   next_to_watch

  Sep  4 09:03:04 mail kernel: [  323.607349]   jiffies  <11725>
  Sep  4 09:03:04 mail kernel: [  323.607349]   desc.status  <120200>
  Sep  4 09:03:06 mail kernel: [  325.606602] igb :02:00.0: Detected Tx 
Unit Hang
  Sep  4 09:03:06 mail kernel: [  325.606602]   Tx Queue <6>
  Sep  4 09:03:06 mail kernel: [  325.606602]   TDH  <23>
  Sep  4 09:03:06 mail kernel: [  325.606602]   TDT  <23>
  Sep  4 09:03:06 mail kernel: [  325.606602]   next_to_use  <25>
  Sep  4 09:03:06 mail kernel: [  325.606602]   next_to_clean<23>
  Sep  4 09:03:06 mail kernel: [  325.606602] buffer_info[next_to_clean]
  Sep  4 09:03:06 mail kernel: [  325.606602]   time_stamp   <112af>
  Sep  4 09:03:06 mail kernel: [  325.606602]   next_to_watch

  Sep  4 09:03:06 mail kernel: [  325.606602]   jiffies  <11919>
  Sep  4 09:03:06 mail kernel: [  325.606602]   desc.status  <120200>

  All network connections droped after that. System still unusable.

  Only after boot with old linux-image-3.16.0-46-generic my production
  mail server can work.

  It's a critical bug for me, can anybody help me?

  ethtool -i em1
  driver: igb
  version: 5.2.13-k
  firmware-version: 1.61, 0x8cd5, 1.949.0
  bus-info: :02:00.0
  supports-statistics: yes
  supports-test: yes
  supports-eeprom-access: yes
  supports-register-dump: yes
  supports-priv-flags: no

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-lts-utopic/+bug/1492146/+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 1512848] Re: Radeon VCE Init Error

2015-11-03 Thread schmod
** Bug watch added: Debian Bug tracker #803087
   http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=803087

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

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

Title:
  Radeon VCE Init Error

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

Bug description:
  Since upgrading to Ubuntu 15.10, I have encountered graphics
  performance issues, and have occasionally experienced lockups during
  boot.

  dmesg | grep radeon
  [2.103294] [drm] radeon kernel modesetting enabled.
  [2.114677] radeon :01:00.0: enabling device ( -> 0003)
  [2.226348] radeon :01:00.0: VRAM: 1024M 0x - 
0x3FFF (1024M used)
  [2.226349] radeon :01:00.0: GTT: 2048M 0x4000 - 
0xBFFF
  [2.226494] [drm] radeon: 1024M of VRAM memory ready
  [2.226506] [drm] radeon: 2048M of GTT memory ready.
  [2.232296] [drm] radeon: dpm initialized
  [2.234760] [drm] enabling PCIE gen 3 link speeds, disable with 
radeon.pcie_gen2=0
  [3.456910] radeon :01:00.0: WB enabled
  [3.456912] radeon :01:00.0: fence driver on ring 0 use gpu addr 
0x4c00 and cpu addr 0x88041663ac00
  [3.456914] radeon :01:00.0: fence driver on ring 1 use gpu addr 
0x4c04 and cpu addr 0x88041663ac04
  [3.456915] radeon :01:00.0: fence driver on ring 2 use gpu addr 
0x4c08 and cpu addr 0x88041663ac08
  [3.456916] radeon :01:00.0: fence driver on ring 3 use gpu addr 
0x4c0c and cpu addr 0x88041663ac0c
  [3.456918] radeon :01:00.0: fence driver on ring 4 use gpu addr 
0x4c10 and cpu addr 0x88041663ac10
  [3.457696] radeon :01:00.0: fence driver on ring 5 use gpu addr 
0x00075a18 and cpu addr 0xc90002035a18
  [3.558371] radeon :01:00.0: VCE init error (-110).
  [3.558376] radeon :01:00.0: radeon: MSI limited to 32-bit
  [3.558397] radeon :01:00.0: radeon: using MSI.
  [3.558421] [drm] radeon: irq initialized.
  [4.538452] radeon :01:00.0: No connectors reported connected with 
modes
  [4.539564] radeon :01:00.0: fb1: radeondrmfb frame buffer device
  [4.539598] [drm] Initialized radeon 2.43.0 20080528 for :01:00.0 on 
minor 1
  [   11.629124] [drm] enabling PCIE gen 3 link speeds, disable with 
radeon.pcie_gen2=0
  [   12.627048] radeon :01:00.0: WB enabled
  [   12.627050] radeon :01:00.0: fence driver on ring 0 use gpu addr 
0x4c00 and cpu addr 0x88041663ac00
  [   12.627051] radeon :01:00.0: fence driver on ring 1 use gpu addr 
0x4c04 and cpu addr 0x88041663ac04
  [   12.627053] radeon :01:00.0: fence driver on ring 2 use gpu addr 
0x4c08 and cpu addr 0x88041663ac08
  [   12.627054] radeon :01:00.0: fence driver on ring 3 use gpu addr 
0x4c0c and cpu addr 0x88041663ac0c
  [   12.627055] radeon :01:00.0: fence driver on ring 4 use gpu addr 
0x4c10 and cpu addr 0x88041663ac10
  [   12.627838] radeon :01:00.0: fence driver on ring 5 use gpu addr 
0x00075a18 and cpu addr 0xc90002035a18
  [   12.728529] radeon :01:00.0: VCE init error (-110).

  
  xrandr --listproviders
  Providers: number : 3
  Provider 0: id: 0x6a cap: 0x9, Source Output, Sink Offload crtcs: 4 outputs: 
5 associated providers: 2 name:Intel
  Provider 1: id: 0x41 cap: 0x6, Sink Output, Source Offload crtcs: 2 outputs: 
0 associated providers: 2 name:radeon
  Provider 2: id: 0x41 cap: 0x6, Sink Output, Source Offload crtcs: 2 outputs: 
0 associated providers: 2 name:radeon

  
  lspci -k 
  00:00.0 Host bridge: Intel Corporation 3rd Gen Core processor DRAM Controller 
(rev 09)
  Subsystem: Samsung Electronics Co Ltd Device c0e6
  Kernel driver in use: ivb_uncore
  00:01.0 PCI bridge: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor 
PCI Express Root Port (rev 09)
  Kernel driver in use: pcieport
  00:02.0 VGA compatible controller: Intel Corporation 3rd Gen Core processor 
Graphics Controller (rev 09)
  DeviceName:  Onboard IGD
  Subsystem: Samsung Electronics Co Ltd Device c0e6
  Kernel driver in use: i915
  01:00.0 Display controller: Advanced Micro Devices, Inc. [AMD/ATI] Mars 
[Radeon HD 8670A/8670M/8750M] (rev ff)
  Kernel driver in use: radeon

  
  Possible upstream Debian bug: 
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=803087

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : 

[Kernel-packages] [Bug 1512848] Re: Radeon VCE Init Error

2015-11-03 Thread schmod
Confirmed with 4.3.0-040300-generic

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

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

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

Title:
  Radeon VCE Init Error

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

Bug description:
  Since upgrading to Ubuntu 15.10, I have encountered graphics
  performance issues, and have occasionally experienced lockups during
  boot.

  dmesg | grep radeon
  [2.103294] [drm] radeon kernel modesetting enabled.
  [2.114677] radeon :01:00.0: enabling device ( -> 0003)
  [2.226348] radeon :01:00.0: VRAM: 1024M 0x - 
0x3FFF (1024M used)
  [2.226349] radeon :01:00.0: GTT: 2048M 0x4000 - 
0xBFFF
  [2.226494] [drm] radeon: 1024M of VRAM memory ready
  [2.226506] [drm] radeon: 2048M of GTT memory ready.
  [2.232296] [drm] radeon: dpm initialized
  [2.234760] [drm] enabling PCIE gen 3 link speeds, disable with 
radeon.pcie_gen2=0
  [3.456910] radeon :01:00.0: WB enabled
  [3.456912] radeon :01:00.0: fence driver on ring 0 use gpu addr 
0x4c00 and cpu addr 0x88041663ac00
  [3.456914] radeon :01:00.0: fence driver on ring 1 use gpu addr 
0x4c04 and cpu addr 0x88041663ac04
  [3.456915] radeon :01:00.0: fence driver on ring 2 use gpu addr 
0x4c08 and cpu addr 0x88041663ac08
  [3.456916] radeon :01:00.0: fence driver on ring 3 use gpu addr 
0x4c0c and cpu addr 0x88041663ac0c
  [3.456918] radeon :01:00.0: fence driver on ring 4 use gpu addr 
0x4c10 and cpu addr 0x88041663ac10
  [3.457696] radeon :01:00.0: fence driver on ring 5 use gpu addr 
0x00075a18 and cpu addr 0xc90002035a18
  [3.558371] radeon :01:00.0: VCE init error (-110).
  [3.558376] radeon :01:00.0: radeon: MSI limited to 32-bit
  [3.558397] radeon :01:00.0: radeon: using MSI.
  [3.558421] [drm] radeon: irq initialized.
  [4.538452] radeon :01:00.0: No connectors reported connected with 
modes
  [4.539564] radeon :01:00.0: fb1: radeondrmfb frame buffer device
  [4.539598] [drm] Initialized radeon 2.43.0 20080528 for :01:00.0 on 
minor 1
  [   11.629124] [drm] enabling PCIE gen 3 link speeds, disable with 
radeon.pcie_gen2=0
  [   12.627048] radeon :01:00.0: WB enabled
  [   12.627050] radeon :01:00.0: fence driver on ring 0 use gpu addr 
0x4c00 and cpu addr 0x88041663ac00
  [   12.627051] radeon :01:00.0: fence driver on ring 1 use gpu addr 
0x4c04 and cpu addr 0x88041663ac04
  [   12.627053] radeon :01:00.0: fence driver on ring 2 use gpu addr 
0x4c08 and cpu addr 0x88041663ac08
  [   12.627054] radeon :01:00.0: fence driver on ring 3 use gpu addr 
0x4c0c and cpu addr 0x88041663ac0c
  [   12.627055] radeon :01:00.0: fence driver on ring 4 use gpu addr 
0x4c10 and cpu addr 0x88041663ac10
  [   12.627838] radeon :01:00.0: fence driver on ring 5 use gpu addr 
0x00075a18 and cpu addr 0xc90002035a18
  [   12.728529] radeon :01:00.0: VCE init error (-110).

  
  xrandr --listproviders
  Providers: number : 3
  Provider 0: id: 0x6a cap: 0x9, Source Output, Sink Offload crtcs: 4 outputs: 
5 associated providers: 2 name:Intel
  Provider 1: id: 0x41 cap: 0x6, Sink Output, Source Offload crtcs: 2 outputs: 
0 associated providers: 2 name:radeon
  Provider 2: id: 0x41 cap: 0x6, Sink Output, Source Offload crtcs: 2 outputs: 
0 associated providers: 2 name:radeon

  
  lspci -k 
  00:00.0 Host bridge: Intel Corporation 3rd Gen Core processor DRAM Controller 
(rev 09)
  Subsystem: Samsung Electronics Co Ltd Device c0e6
  Kernel driver in use: ivb_uncore
  00:01.0 PCI bridge: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor 
PCI Express Root Port (rev 09)
  Kernel driver in use: pcieport
  00:02.0 VGA compatible controller: Intel Corporation 3rd Gen Core processor 
Graphics Controller (rev 09)
  DeviceName:  Onboard IGD
  Subsystem: Samsung Electronics Co Ltd Device c0e6
  Kernel driver in use: i915
  01:00.0 Display controller: Advanced Micro Devices, Inc. [AMD/ATI] Mars 
[Radeon HD 8670A/8670M/8750M] (rev ff)
  Kernel driver in use: radeon

  
  Possible upstream Debian bug: 
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=803087
  --- 
  ApportVersion: 2.19.1-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  aschmadel   2152 F pulseaudio
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 15.10
  EcryptfsInUse: Yes
  HibernationDevice: 

[Kernel-packages] [Bug 1509120] Comment bridged from LTC Bugzilla

2015-11-03 Thread bugproxy
--- Comment From ru...@us.ibm.com 2015-11-03 20:56 EDT---
Thanks for chasing down the missing dependency side of the equation here.

That still leaves the potential of deadlock if the callout exec ever
returns non-zero for any other reason.  Are the risks considered low
enough to simply document this as a potential hazard of writing process
accounting information across an NFSv4 mount?

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

Title:
  Process accounting deadlock with idmapd callout when writing to NFSv4
  mount

Status in linux package in Ubuntu:
  Invalid
Status in nfs-utils package in Ubuntu:
  In Progress

Bug description:
  [Impact]

   * Programs accessing nfsv4 mounts will hang on request_key interface
  with nfs4 + sec=sys with old nfsv4 hosts.  Kernel is waiting on
  usermodehelper provided by keyutils.

   * INFO: task ls:2101 blocked for more than 120 seconds.
Not tainted 3.13.0-66-generic #108-Ubuntu
  "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
  ls D 88007fd13180 0 2101 1215 0x0004
   88007b14d630 0086 8800374e6000 88007b14dfd8
   00013180 00013180 8800374e6000 88007b14d6b0
   88007ffd1460 0002 812d0ce0 88007b14d6a0
  Call Trace:
   [] ? umh_keys_init+0x20/0x20
   [] schedule+0x29/0x70
   [] key_wait_bit+0xe/0x20
   [] __wait_on_bit+0x62/0x90
   [] ? umh_keys_init+0x20/0x20
   [] out_of_line_wait_on_bit+0x77/0x90
   [] ? autoremove_wake_function+0x40/0x40
   [] wait_for_key_construction+0x6e/0x80
   [] request_key+0x5c/0xa0
   [] nfs_idmap_get_key+0xaf/0x1c0 [nfsv4]
   [] nfs_map_name_to_uid+0xef/0x150 [nfsv4]
   [] decode_getfattr_attrs+0xe47/0x14b0 [nfsv4]
   [] ? sched_clock+0x9/0x10
   [] decode_getfattr_generic.constprop.102+0x8c/0xf0 [nfsv4]
   [] ? nfs4_xdr_dec_access+0xa0/0xa0 [nfsv4]
   [] nfs4_xdr_dec_getattr+0x70/0x80 [nfsv4]
   [] rpcauth_unwrap_resp+0x86/0xd0 [sunrpc]
   [] ? nfs4_xdr_dec_access+0xa0/0xa0 [nfsv4]
   [] call_decode+0x1df/0x870 [sunrpc]
   [] ? call_refreshresult+0x170/0x170 [sunrpc]
   [] ? call_refreshresult+0x170/0x170 [sunrpc]
   [] __rpc_execute+0x84/0x400 [sunrpc]
   [] rpc_execute+0x5e/0xa0 [sunrpc]
   [] rpc_run_task+0x70/0x90 [sunrpc]
   [] nfs4_call_sync_sequence+0x56/0x80 [nfsv4]
   [] _nfs4_proc_getattr+0xbe/0xd0 [nfsv4]
   [] nfs4_proc_getattr+0x5a/0xd0 [nfsv4]
   [] __nfs_revalidate_inode+0xbf/0x310 [nfs]
   [] nfs_opendir+0xe3/0x100 [nfs]
   [] do_dentry_open+0x233/0x2e0
   [] ? nfs_readdir_clear_array+0x70/0x70 [nfs]
   [] vfs_open+0x49/0x50
   [] do_last+0x564/0x1240
   [] ? link_path_walk+0x256/0x880
   [] ? apparmor_file_alloc_security+0x5b/0x180
   [] ? security_file_alloc+0x16/0x20
   [] path_openat+0xbb/0x650
   [] do_filp_open+0x3a/0x90
   [] ? do_mmap_pgoff+0x34e/0x3d0
   [] ? __alloc_fd+0xa7/0x130
   [] do_sys_open+0x129/0x280
   [] ? do_page_fault+0x1a/0x70
   [] SyS_openat+0x14/0x20
   [] system_call_fastpath+0x1a/0x1f

  [Regression Potential]

   * Minimal this was applied to vivid+wily via bug 1449074.

  [Other Info]
   
   * Sulution is to add keyutils as Required to nfs-common.

  Original Description 
  __

  ---Problem Description---
  System hang when process accounting to a NFSv4 mount.

  ---uname output---
  Linux ppc001 3.19.0-30-generic #34~14.04.1-Ubuntu SMP Fri Oct 2 22:21:52
  UTC 2015 ppc64le ppc64le ppc64le GNU/Linux

  ---Problem Details---

  We have a customer that is experiencing intermittent system hangs on
  their system.  After a bit of debug, it was discovered that the
  trigger was turning on process accounting and writing to a file hosted
  via an NFSv4 mount.  During the testing, several vmcores were
  captured, and the fingerprint indicates a mutex deadlock situation
  with process accounting.   In the most recent vmcore, it appears that
  the scenario is something like the following:

  1. PID: 4898 COMMAND: "ls" triggers a write to the process accounting file.
  2. The resulting NFS write needs idmapd information and calls out to idmapd
  3. The idmapd usermodehelper process triggers another process accounting 
update that blocks on the mutex being held by PID 4898.

  PID: 4898   TASK: c01fd26d7580  CPU: 7   COMMAND: "ls"
   #0 [c01fd274a950] __switch_to at c0015934
   #1 [c01fd274ab20] __switch_to at c0015934
   #2 [c01fd274ab80] __schedule at c0a11de8
   #3 [c01fd274ada0] schedule_timeout at c0a16284
   #4 [c01fd274ae90] wait_for_common at c0a1360c
   #5 [c01fd274af10] call_usermodehelper_exec at c00ccd38
   #6 [c01fd274af70] call_sbin_request_key at c0429258
   #7 [c01fd274b100] request_key_and_link at c042983c
   #8 [c01fd274b200] request_key at c0429978
   #9 

[Kernel-packages] [Bug 1512815] Re: read() from pty doesn't finish.

2015-11-03 Thread Joseph Salisbury
I built a Wily test kernel with a cherry pick of commit e81107d.  The test 
kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1512815/

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

Note, you need to install both the linux-image and linux-image-extra
.deb packages.

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

Title:
  read() from pty doesn't finish.

Status in linux package in Ubuntu:
  In Progress

Bug description:
  It has been brought to my attention

  By the attached test program pty, a pair of process repeats writing
  and reading only '\n' to a master pseudoterminal device (/dev/ptmx)
  and a slave pseudoterminal device (/dev/pts/N) each. When we carry out
  the following 30 pairs 10,000 times, in a pair each process doesn't
  finish reading.

  $ pty 30
  The following message will be usually indicated immediately.
  #name copy num/sec usec/num
  pty_switch 30 1541842 0.648575

  When a message wasn't indicated any more, we got the attached dump file. 
  A kernel was 3.13.0-45.74. 
  A system was Ubuntu 14.04 LTS.

  The same problem occurred in case of 3.13.0-55.92 kernel and the following 
kernel have been tested as well:
  2.6.32, 3.10: not reproduces.
  3.19, 4.0.0, 4.1.3: reproduces.

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

2015-11-03 Thread schmod
apport information

** Attachment added: "IwConfig.txt"
   
https://bugs.launchpad.net/bugs/1512848/+attachment/4512325/+files/IwConfig.txt

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

Title:
  Radeon VCE Init Error

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

Bug description:
  Since upgrading to Ubuntu 15.10, I have encountered graphics
  performance issues, and have occasionally experienced lockups during
  boot.

  dmesg | grep radeon
  [2.103294] [drm] radeon kernel modesetting enabled.
  [2.114677] radeon :01:00.0: enabling device ( -> 0003)
  [2.226348] radeon :01:00.0: VRAM: 1024M 0x - 
0x3FFF (1024M used)
  [2.226349] radeon :01:00.0: GTT: 2048M 0x4000 - 
0xBFFF
  [2.226494] [drm] radeon: 1024M of VRAM memory ready
  [2.226506] [drm] radeon: 2048M of GTT memory ready.
  [2.232296] [drm] radeon: dpm initialized
  [2.234760] [drm] enabling PCIE gen 3 link speeds, disable with 
radeon.pcie_gen2=0
  [3.456910] radeon :01:00.0: WB enabled
  [3.456912] radeon :01:00.0: fence driver on ring 0 use gpu addr 
0x4c00 and cpu addr 0x88041663ac00
  [3.456914] radeon :01:00.0: fence driver on ring 1 use gpu addr 
0x4c04 and cpu addr 0x88041663ac04
  [3.456915] radeon :01:00.0: fence driver on ring 2 use gpu addr 
0x4c08 and cpu addr 0x88041663ac08
  [3.456916] radeon :01:00.0: fence driver on ring 3 use gpu addr 
0x4c0c and cpu addr 0x88041663ac0c
  [3.456918] radeon :01:00.0: fence driver on ring 4 use gpu addr 
0x4c10 and cpu addr 0x88041663ac10
  [3.457696] radeon :01:00.0: fence driver on ring 5 use gpu addr 
0x00075a18 and cpu addr 0xc90002035a18
  [3.558371] radeon :01:00.0: VCE init error (-110).
  [3.558376] radeon :01:00.0: radeon: MSI limited to 32-bit
  [3.558397] radeon :01:00.0: radeon: using MSI.
  [3.558421] [drm] radeon: irq initialized.
  [4.538452] radeon :01:00.0: No connectors reported connected with 
modes
  [4.539564] radeon :01:00.0: fb1: radeondrmfb frame buffer device
  [4.539598] [drm] Initialized radeon 2.43.0 20080528 for :01:00.0 on 
minor 1
  [   11.629124] [drm] enabling PCIE gen 3 link speeds, disable with 
radeon.pcie_gen2=0
  [   12.627048] radeon :01:00.0: WB enabled
  [   12.627050] radeon :01:00.0: fence driver on ring 0 use gpu addr 
0x4c00 and cpu addr 0x88041663ac00
  [   12.627051] radeon :01:00.0: fence driver on ring 1 use gpu addr 
0x4c04 and cpu addr 0x88041663ac04
  [   12.627053] radeon :01:00.0: fence driver on ring 2 use gpu addr 
0x4c08 and cpu addr 0x88041663ac08
  [   12.627054] radeon :01:00.0: fence driver on ring 3 use gpu addr 
0x4c0c and cpu addr 0x88041663ac0c
  [   12.627055] radeon :01:00.0: fence driver on ring 4 use gpu addr 
0x4c10 and cpu addr 0x88041663ac10
  [   12.627838] radeon :01:00.0: fence driver on ring 5 use gpu addr 
0x00075a18 and cpu addr 0xc90002035a18
  [   12.728529] radeon :01:00.0: VCE init error (-110).

  
  xrandr --listproviders
  Providers: number : 3
  Provider 0: id: 0x6a cap: 0x9, Source Output, Sink Offload crtcs: 4 outputs: 
5 associated providers: 2 name:Intel
  Provider 1: id: 0x41 cap: 0x6, Sink Output, Source Offload crtcs: 2 outputs: 
0 associated providers: 2 name:radeon
  Provider 2: id: 0x41 cap: 0x6, Sink Output, Source Offload crtcs: 2 outputs: 
0 associated providers: 2 name:radeon

  
  lspci -k 
  00:00.0 Host bridge: Intel Corporation 3rd Gen Core processor DRAM Controller 
(rev 09)
  Subsystem: Samsung Electronics Co Ltd Device c0e6
  Kernel driver in use: ivb_uncore
  00:01.0 PCI bridge: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor 
PCI Express Root Port (rev 09)
  Kernel driver in use: pcieport
  00:02.0 VGA compatible controller: Intel Corporation 3rd Gen Core processor 
Graphics Controller (rev 09)
  DeviceName:  Onboard IGD
  Subsystem: Samsung Electronics Co Ltd Device c0e6
  Kernel driver in use: i915
  01:00.0 Display controller: Advanced Micro Devices, Inc. [AMD/ATI] Mars 
[Radeon HD 8670A/8670M/8750M] (rev ff)
  Kernel driver in use: radeon

  
  Possible upstream Debian bug: 
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=803087
  --- 
  ApportVersion: 2.19.1-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  aschmadel   2152 F pulseaudio
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 15.10
  EcryptfsInUse: Yes
  HibernationDevice: 

[Kernel-packages] [Bug 1512848] PulseList.txt

2015-11-03 Thread schmod
apport information

** Attachment added: "PulseList.txt"
   
https://bugs.launchpad.net/bugs/1512848/+attachment/4512332/+files/PulseList.txt

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

Title:
  Radeon VCE Init Error

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

Bug description:
  Since upgrading to Ubuntu 15.10, I have encountered graphics
  performance issues, and have occasionally experienced lockups during
  boot.

  dmesg | grep radeon
  [2.103294] [drm] radeon kernel modesetting enabled.
  [2.114677] radeon :01:00.0: enabling device ( -> 0003)
  [2.226348] radeon :01:00.0: VRAM: 1024M 0x - 
0x3FFF (1024M used)
  [2.226349] radeon :01:00.0: GTT: 2048M 0x4000 - 
0xBFFF
  [2.226494] [drm] radeon: 1024M of VRAM memory ready
  [2.226506] [drm] radeon: 2048M of GTT memory ready.
  [2.232296] [drm] radeon: dpm initialized
  [2.234760] [drm] enabling PCIE gen 3 link speeds, disable with 
radeon.pcie_gen2=0
  [3.456910] radeon :01:00.0: WB enabled
  [3.456912] radeon :01:00.0: fence driver on ring 0 use gpu addr 
0x4c00 and cpu addr 0x88041663ac00
  [3.456914] radeon :01:00.0: fence driver on ring 1 use gpu addr 
0x4c04 and cpu addr 0x88041663ac04
  [3.456915] radeon :01:00.0: fence driver on ring 2 use gpu addr 
0x4c08 and cpu addr 0x88041663ac08
  [3.456916] radeon :01:00.0: fence driver on ring 3 use gpu addr 
0x4c0c and cpu addr 0x88041663ac0c
  [3.456918] radeon :01:00.0: fence driver on ring 4 use gpu addr 
0x4c10 and cpu addr 0x88041663ac10
  [3.457696] radeon :01:00.0: fence driver on ring 5 use gpu addr 
0x00075a18 and cpu addr 0xc90002035a18
  [3.558371] radeon :01:00.0: VCE init error (-110).
  [3.558376] radeon :01:00.0: radeon: MSI limited to 32-bit
  [3.558397] radeon :01:00.0: radeon: using MSI.
  [3.558421] [drm] radeon: irq initialized.
  [4.538452] radeon :01:00.0: No connectors reported connected with 
modes
  [4.539564] radeon :01:00.0: fb1: radeondrmfb frame buffer device
  [4.539598] [drm] Initialized radeon 2.43.0 20080528 for :01:00.0 on 
minor 1
  [   11.629124] [drm] enabling PCIE gen 3 link speeds, disable with 
radeon.pcie_gen2=0
  [   12.627048] radeon :01:00.0: WB enabled
  [   12.627050] radeon :01:00.0: fence driver on ring 0 use gpu addr 
0x4c00 and cpu addr 0x88041663ac00
  [   12.627051] radeon :01:00.0: fence driver on ring 1 use gpu addr 
0x4c04 and cpu addr 0x88041663ac04
  [   12.627053] radeon :01:00.0: fence driver on ring 2 use gpu addr 
0x4c08 and cpu addr 0x88041663ac08
  [   12.627054] radeon :01:00.0: fence driver on ring 3 use gpu addr 
0x4c0c and cpu addr 0x88041663ac0c
  [   12.627055] radeon :01:00.0: fence driver on ring 4 use gpu addr 
0x4c10 and cpu addr 0x88041663ac10
  [   12.627838] radeon :01:00.0: fence driver on ring 5 use gpu addr 
0x00075a18 and cpu addr 0xc90002035a18
  [   12.728529] radeon :01:00.0: VCE init error (-110).

  
  xrandr --listproviders
  Providers: number : 3
  Provider 0: id: 0x6a cap: 0x9, Source Output, Sink Offload crtcs: 4 outputs: 
5 associated providers: 2 name:Intel
  Provider 1: id: 0x41 cap: 0x6, Sink Output, Source Offload crtcs: 2 outputs: 
0 associated providers: 2 name:radeon
  Provider 2: id: 0x41 cap: 0x6, Sink Output, Source Offload crtcs: 2 outputs: 
0 associated providers: 2 name:radeon

  
  lspci -k 
  00:00.0 Host bridge: Intel Corporation 3rd Gen Core processor DRAM Controller 
(rev 09)
  Subsystem: Samsung Electronics Co Ltd Device c0e6
  Kernel driver in use: ivb_uncore
  00:01.0 PCI bridge: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor 
PCI Express Root Port (rev 09)
  Kernel driver in use: pcieport
  00:02.0 VGA compatible controller: Intel Corporation 3rd Gen Core processor 
Graphics Controller (rev 09)
  DeviceName:  Onboard IGD
  Subsystem: Samsung Electronics Co Ltd Device c0e6
  Kernel driver in use: i915
  01:00.0 Display controller: Advanced Micro Devices, Inc. [AMD/ATI] Mars 
[Radeon HD 8670A/8670M/8750M] (rev ff)
  Kernel driver in use: radeon

  
  Possible upstream Debian bug: 
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=803087
  --- 
  ApportVersion: 2.19.1-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  aschmadel   2152 F pulseaudio
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 15.10
  EcryptfsInUse: Yes
  HibernationDevice: 

[Kernel-packages] [Bug 1512848] ProcModules.txt

2015-11-03 Thread schmod
apport information

** Attachment added: "ProcModules.txt"
   
https://bugs.launchpad.net/bugs/1512848/+attachment/4512331/+files/ProcModules.txt

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

Title:
  Radeon VCE Init Error

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

Bug description:
  Since upgrading to Ubuntu 15.10, I have encountered graphics
  performance issues, and have occasionally experienced lockups during
  boot.

  dmesg | grep radeon
  [2.103294] [drm] radeon kernel modesetting enabled.
  [2.114677] radeon :01:00.0: enabling device ( -> 0003)
  [2.226348] radeon :01:00.0: VRAM: 1024M 0x - 
0x3FFF (1024M used)
  [2.226349] radeon :01:00.0: GTT: 2048M 0x4000 - 
0xBFFF
  [2.226494] [drm] radeon: 1024M of VRAM memory ready
  [2.226506] [drm] radeon: 2048M of GTT memory ready.
  [2.232296] [drm] radeon: dpm initialized
  [2.234760] [drm] enabling PCIE gen 3 link speeds, disable with 
radeon.pcie_gen2=0
  [3.456910] radeon :01:00.0: WB enabled
  [3.456912] radeon :01:00.0: fence driver on ring 0 use gpu addr 
0x4c00 and cpu addr 0x88041663ac00
  [3.456914] radeon :01:00.0: fence driver on ring 1 use gpu addr 
0x4c04 and cpu addr 0x88041663ac04
  [3.456915] radeon :01:00.0: fence driver on ring 2 use gpu addr 
0x4c08 and cpu addr 0x88041663ac08
  [3.456916] radeon :01:00.0: fence driver on ring 3 use gpu addr 
0x4c0c and cpu addr 0x88041663ac0c
  [3.456918] radeon :01:00.0: fence driver on ring 4 use gpu addr 
0x4c10 and cpu addr 0x88041663ac10
  [3.457696] radeon :01:00.0: fence driver on ring 5 use gpu addr 
0x00075a18 and cpu addr 0xc90002035a18
  [3.558371] radeon :01:00.0: VCE init error (-110).
  [3.558376] radeon :01:00.0: radeon: MSI limited to 32-bit
  [3.558397] radeon :01:00.0: radeon: using MSI.
  [3.558421] [drm] radeon: irq initialized.
  [4.538452] radeon :01:00.0: No connectors reported connected with 
modes
  [4.539564] radeon :01:00.0: fb1: radeondrmfb frame buffer device
  [4.539598] [drm] Initialized radeon 2.43.0 20080528 for :01:00.0 on 
minor 1
  [   11.629124] [drm] enabling PCIE gen 3 link speeds, disable with 
radeon.pcie_gen2=0
  [   12.627048] radeon :01:00.0: WB enabled
  [   12.627050] radeon :01:00.0: fence driver on ring 0 use gpu addr 
0x4c00 and cpu addr 0x88041663ac00
  [   12.627051] radeon :01:00.0: fence driver on ring 1 use gpu addr 
0x4c04 and cpu addr 0x88041663ac04
  [   12.627053] radeon :01:00.0: fence driver on ring 2 use gpu addr 
0x4c08 and cpu addr 0x88041663ac08
  [   12.627054] radeon :01:00.0: fence driver on ring 3 use gpu addr 
0x4c0c and cpu addr 0x88041663ac0c
  [   12.627055] radeon :01:00.0: fence driver on ring 4 use gpu addr 
0x4c10 and cpu addr 0x88041663ac10
  [   12.627838] radeon :01:00.0: fence driver on ring 5 use gpu addr 
0x00075a18 and cpu addr 0xc90002035a18
  [   12.728529] radeon :01:00.0: VCE init error (-110).

  
  xrandr --listproviders
  Providers: number : 3
  Provider 0: id: 0x6a cap: 0x9, Source Output, Sink Offload crtcs: 4 outputs: 
5 associated providers: 2 name:Intel
  Provider 1: id: 0x41 cap: 0x6, Sink Output, Source Offload crtcs: 2 outputs: 
0 associated providers: 2 name:radeon
  Provider 2: id: 0x41 cap: 0x6, Sink Output, Source Offload crtcs: 2 outputs: 
0 associated providers: 2 name:radeon

  
  lspci -k 
  00:00.0 Host bridge: Intel Corporation 3rd Gen Core processor DRAM Controller 
(rev 09)
  Subsystem: Samsung Electronics Co Ltd Device c0e6
  Kernel driver in use: ivb_uncore
  00:01.0 PCI bridge: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor 
PCI Express Root Port (rev 09)
  Kernel driver in use: pcieport
  00:02.0 VGA compatible controller: Intel Corporation 3rd Gen Core processor 
Graphics Controller (rev 09)
  DeviceName:  Onboard IGD
  Subsystem: Samsung Electronics Co Ltd Device c0e6
  Kernel driver in use: i915
  01:00.0 Display controller: Advanced Micro Devices, Inc. [AMD/ATI] Mars 
[Radeon HD 8670A/8670M/8750M] (rev ff)
  Kernel driver in use: radeon

  
  Possible upstream Debian bug: 
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=803087
  --- 
  ApportVersion: 2.19.1-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  aschmadel   2152 F pulseaudio
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 15.10
  EcryptfsInUse: Yes
  HibernationDevice: 

[Kernel-packages] [Bug 1512848] UdevLog.txt

2015-11-03 Thread schmod
apport information

** Attachment added: "UdevLog.txt"
   
https://bugs.launchpad.net/bugs/1512848/+attachment/4512335/+files/UdevLog.txt

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

Title:
  Radeon VCE Init Error

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

Bug description:
  Since upgrading to Ubuntu 15.10, I have encountered graphics
  performance issues, and have occasionally experienced lockups during
  boot.

  dmesg | grep radeon
  [2.103294] [drm] radeon kernel modesetting enabled.
  [2.114677] radeon :01:00.0: enabling device ( -> 0003)
  [2.226348] radeon :01:00.0: VRAM: 1024M 0x - 
0x3FFF (1024M used)
  [2.226349] radeon :01:00.0: GTT: 2048M 0x4000 - 
0xBFFF
  [2.226494] [drm] radeon: 1024M of VRAM memory ready
  [2.226506] [drm] radeon: 2048M of GTT memory ready.
  [2.232296] [drm] radeon: dpm initialized
  [2.234760] [drm] enabling PCIE gen 3 link speeds, disable with 
radeon.pcie_gen2=0
  [3.456910] radeon :01:00.0: WB enabled
  [3.456912] radeon :01:00.0: fence driver on ring 0 use gpu addr 
0x4c00 and cpu addr 0x88041663ac00
  [3.456914] radeon :01:00.0: fence driver on ring 1 use gpu addr 
0x4c04 and cpu addr 0x88041663ac04
  [3.456915] radeon :01:00.0: fence driver on ring 2 use gpu addr 
0x4c08 and cpu addr 0x88041663ac08
  [3.456916] radeon :01:00.0: fence driver on ring 3 use gpu addr 
0x4c0c and cpu addr 0x88041663ac0c
  [3.456918] radeon :01:00.0: fence driver on ring 4 use gpu addr 
0x4c10 and cpu addr 0x88041663ac10
  [3.457696] radeon :01:00.0: fence driver on ring 5 use gpu addr 
0x00075a18 and cpu addr 0xc90002035a18
  [3.558371] radeon :01:00.0: VCE init error (-110).
  [3.558376] radeon :01:00.0: radeon: MSI limited to 32-bit
  [3.558397] radeon :01:00.0: radeon: using MSI.
  [3.558421] [drm] radeon: irq initialized.
  [4.538452] radeon :01:00.0: No connectors reported connected with 
modes
  [4.539564] radeon :01:00.0: fb1: radeondrmfb frame buffer device
  [4.539598] [drm] Initialized radeon 2.43.0 20080528 for :01:00.0 on 
minor 1
  [   11.629124] [drm] enabling PCIE gen 3 link speeds, disable with 
radeon.pcie_gen2=0
  [   12.627048] radeon :01:00.0: WB enabled
  [   12.627050] radeon :01:00.0: fence driver on ring 0 use gpu addr 
0x4c00 and cpu addr 0x88041663ac00
  [   12.627051] radeon :01:00.0: fence driver on ring 1 use gpu addr 
0x4c04 and cpu addr 0x88041663ac04
  [   12.627053] radeon :01:00.0: fence driver on ring 2 use gpu addr 
0x4c08 and cpu addr 0x88041663ac08
  [   12.627054] radeon :01:00.0: fence driver on ring 3 use gpu addr 
0x4c0c and cpu addr 0x88041663ac0c
  [   12.627055] radeon :01:00.0: fence driver on ring 4 use gpu addr 
0x4c10 and cpu addr 0x88041663ac10
  [   12.627838] radeon :01:00.0: fence driver on ring 5 use gpu addr 
0x00075a18 and cpu addr 0xc90002035a18
  [   12.728529] radeon :01:00.0: VCE init error (-110).

  
  xrandr --listproviders
  Providers: number : 3
  Provider 0: id: 0x6a cap: 0x9, Source Output, Sink Offload crtcs: 4 outputs: 
5 associated providers: 2 name:Intel
  Provider 1: id: 0x41 cap: 0x6, Sink Output, Source Offload crtcs: 2 outputs: 
0 associated providers: 2 name:radeon
  Provider 2: id: 0x41 cap: 0x6, Sink Output, Source Offload crtcs: 2 outputs: 
0 associated providers: 2 name:radeon

  
  lspci -k 
  00:00.0 Host bridge: Intel Corporation 3rd Gen Core processor DRAM Controller 
(rev 09)
  Subsystem: Samsung Electronics Co Ltd Device c0e6
  Kernel driver in use: ivb_uncore
  00:01.0 PCI bridge: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor 
PCI Express Root Port (rev 09)
  Kernel driver in use: pcieport
  00:02.0 VGA compatible controller: Intel Corporation 3rd Gen Core processor 
Graphics Controller (rev 09)
  DeviceName:  Onboard IGD
  Subsystem: Samsung Electronics Co Ltd Device c0e6
  Kernel driver in use: i915
  01:00.0 Display controller: Advanced Micro Devices, Inc. [AMD/ATI] Mars 
[Radeon HD 8670A/8670M/8750M] (rev ff)
  Kernel driver in use: radeon

  
  Possible upstream Debian bug: 
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=803087
  --- 
  ApportVersion: 2.19.1-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  aschmadel   2152 F pulseaudio
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 15.10
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=5208c4c8-b199-4f3f-92ad-9addd6bd
 

[Kernel-packages] [Bug 1512848] Lsusb.txt

2015-11-03 Thread schmod
apport information

** Attachment added: "Lsusb.txt"
   https://bugs.launchpad.net/bugs/1512848/+attachment/4512327/+files/Lsusb.txt

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

Title:
  Radeon VCE Init Error

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

Bug description:
  Since upgrading to Ubuntu 15.10, I have encountered graphics
  performance issues, and have occasionally experienced lockups during
  boot.

  dmesg | grep radeon
  [2.103294] [drm] radeon kernel modesetting enabled.
  [2.114677] radeon :01:00.0: enabling device ( -> 0003)
  [2.226348] radeon :01:00.0: VRAM: 1024M 0x - 
0x3FFF (1024M used)
  [2.226349] radeon :01:00.0: GTT: 2048M 0x4000 - 
0xBFFF
  [2.226494] [drm] radeon: 1024M of VRAM memory ready
  [2.226506] [drm] radeon: 2048M of GTT memory ready.
  [2.232296] [drm] radeon: dpm initialized
  [2.234760] [drm] enabling PCIE gen 3 link speeds, disable with 
radeon.pcie_gen2=0
  [3.456910] radeon :01:00.0: WB enabled
  [3.456912] radeon :01:00.0: fence driver on ring 0 use gpu addr 
0x4c00 and cpu addr 0x88041663ac00
  [3.456914] radeon :01:00.0: fence driver on ring 1 use gpu addr 
0x4c04 and cpu addr 0x88041663ac04
  [3.456915] radeon :01:00.0: fence driver on ring 2 use gpu addr 
0x4c08 and cpu addr 0x88041663ac08
  [3.456916] radeon :01:00.0: fence driver on ring 3 use gpu addr 
0x4c0c and cpu addr 0x88041663ac0c
  [3.456918] radeon :01:00.0: fence driver on ring 4 use gpu addr 
0x4c10 and cpu addr 0x88041663ac10
  [3.457696] radeon :01:00.0: fence driver on ring 5 use gpu addr 
0x00075a18 and cpu addr 0xc90002035a18
  [3.558371] radeon :01:00.0: VCE init error (-110).
  [3.558376] radeon :01:00.0: radeon: MSI limited to 32-bit
  [3.558397] radeon :01:00.0: radeon: using MSI.
  [3.558421] [drm] radeon: irq initialized.
  [4.538452] radeon :01:00.0: No connectors reported connected with 
modes
  [4.539564] radeon :01:00.0: fb1: radeondrmfb frame buffer device
  [4.539598] [drm] Initialized radeon 2.43.0 20080528 for :01:00.0 on 
minor 1
  [   11.629124] [drm] enabling PCIE gen 3 link speeds, disable with 
radeon.pcie_gen2=0
  [   12.627048] radeon :01:00.0: WB enabled
  [   12.627050] radeon :01:00.0: fence driver on ring 0 use gpu addr 
0x4c00 and cpu addr 0x88041663ac00
  [   12.627051] radeon :01:00.0: fence driver on ring 1 use gpu addr 
0x4c04 and cpu addr 0x88041663ac04
  [   12.627053] radeon :01:00.0: fence driver on ring 2 use gpu addr 
0x4c08 and cpu addr 0x88041663ac08
  [   12.627054] radeon :01:00.0: fence driver on ring 3 use gpu addr 
0x4c0c and cpu addr 0x88041663ac0c
  [   12.627055] radeon :01:00.0: fence driver on ring 4 use gpu addr 
0x4c10 and cpu addr 0x88041663ac10
  [   12.627838] radeon :01:00.0: fence driver on ring 5 use gpu addr 
0x00075a18 and cpu addr 0xc90002035a18
  [   12.728529] radeon :01:00.0: VCE init error (-110).

  
  xrandr --listproviders
  Providers: number : 3
  Provider 0: id: 0x6a cap: 0x9, Source Output, Sink Offload crtcs: 4 outputs: 
5 associated providers: 2 name:Intel
  Provider 1: id: 0x41 cap: 0x6, Sink Output, Source Offload crtcs: 2 outputs: 
0 associated providers: 2 name:radeon
  Provider 2: id: 0x41 cap: 0x6, Sink Output, Source Offload crtcs: 2 outputs: 
0 associated providers: 2 name:radeon

  
  lspci -k 
  00:00.0 Host bridge: Intel Corporation 3rd Gen Core processor DRAM Controller 
(rev 09)
  Subsystem: Samsung Electronics Co Ltd Device c0e6
  Kernel driver in use: ivb_uncore
  00:01.0 PCI bridge: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor 
PCI Express Root Port (rev 09)
  Kernel driver in use: pcieport
  00:02.0 VGA compatible controller: Intel Corporation 3rd Gen Core processor 
Graphics Controller (rev 09)
  DeviceName:  Onboard IGD
  Subsystem: Samsung Electronics Co Ltd Device c0e6
  Kernel driver in use: i915
  01:00.0 Display controller: Advanced Micro Devices, Inc. [AMD/ATI] Mars 
[Radeon HD 8670A/8670M/8750M] (rev ff)
  Kernel driver in use: radeon

  
  Possible upstream Debian bug: 
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=803087
  --- 
  ApportVersion: 2.19.1-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  aschmadel   2152 F pulseaudio
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 15.10
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=5208c4c8-b199-4f3f-92ad-9addd6bd
  

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

2015-11-03 Thread schmod
apport information

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

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

Title:
  Radeon VCE Init Error

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

Bug description:
  Since upgrading to Ubuntu 15.10, I have encountered graphics
  performance issues, and have occasionally experienced lockups during
  boot.

  dmesg | grep radeon
  [2.103294] [drm] radeon kernel modesetting enabled.
  [2.114677] radeon :01:00.0: enabling device ( -> 0003)
  [2.226348] radeon :01:00.0: VRAM: 1024M 0x - 
0x3FFF (1024M used)
  [2.226349] radeon :01:00.0: GTT: 2048M 0x4000 - 
0xBFFF
  [2.226494] [drm] radeon: 1024M of VRAM memory ready
  [2.226506] [drm] radeon: 2048M of GTT memory ready.
  [2.232296] [drm] radeon: dpm initialized
  [2.234760] [drm] enabling PCIE gen 3 link speeds, disable with 
radeon.pcie_gen2=0
  [3.456910] radeon :01:00.0: WB enabled
  [3.456912] radeon :01:00.0: fence driver on ring 0 use gpu addr 
0x4c00 and cpu addr 0x88041663ac00
  [3.456914] radeon :01:00.0: fence driver on ring 1 use gpu addr 
0x4c04 and cpu addr 0x88041663ac04
  [3.456915] radeon :01:00.0: fence driver on ring 2 use gpu addr 
0x4c08 and cpu addr 0x88041663ac08
  [3.456916] radeon :01:00.0: fence driver on ring 3 use gpu addr 
0x4c0c and cpu addr 0x88041663ac0c
  [3.456918] radeon :01:00.0: fence driver on ring 4 use gpu addr 
0x4c10 and cpu addr 0x88041663ac10
  [3.457696] radeon :01:00.0: fence driver on ring 5 use gpu addr 
0x00075a18 and cpu addr 0xc90002035a18
  [3.558371] radeon :01:00.0: VCE init error (-110).
  [3.558376] radeon :01:00.0: radeon: MSI limited to 32-bit
  [3.558397] radeon :01:00.0: radeon: using MSI.
  [3.558421] [drm] radeon: irq initialized.
  [4.538452] radeon :01:00.0: No connectors reported connected with 
modes
  [4.539564] radeon :01:00.0: fb1: radeondrmfb frame buffer device
  [4.539598] [drm] Initialized radeon 2.43.0 20080528 for :01:00.0 on 
minor 1
  [   11.629124] [drm] enabling PCIE gen 3 link speeds, disable with 
radeon.pcie_gen2=0
  [   12.627048] radeon :01:00.0: WB enabled
  [   12.627050] radeon :01:00.0: fence driver on ring 0 use gpu addr 
0x4c00 and cpu addr 0x88041663ac00
  [   12.627051] radeon :01:00.0: fence driver on ring 1 use gpu addr 
0x4c04 and cpu addr 0x88041663ac04
  [   12.627053] radeon :01:00.0: fence driver on ring 2 use gpu addr 
0x4c08 and cpu addr 0x88041663ac08
  [   12.627054] radeon :01:00.0: fence driver on ring 3 use gpu addr 
0x4c0c and cpu addr 0x88041663ac0c
  [   12.627055] radeon :01:00.0: fence driver on ring 4 use gpu addr 
0x4c10 and cpu addr 0x88041663ac10
  [   12.627838] radeon :01:00.0: fence driver on ring 5 use gpu addr 
0x00075a18 and cpu addr 0xc90002035a18
  [   12.728529] radeon :01:00.0: VCE init error (-110).

  
  xrandr --listproviders
  Providers: number : 3
  Provider 0: id: 0x6a cap: 0x9, Source Output, Sink Offload crtcs: 4 outputs: 
5 associated providers: 2 name:Intel
  Provider 1: id: 0x41 cap: 0x6, Sink Output, Source Offload crtcs: 2 outputs: 
0 associated providers: 2 name:radeon
  Provider 2: id: 0x41 cap: 0x6, Sink Output, Source Offload crtcs: 2 outputs: 
0 associated providers: 2 name:radeon

  
  lspci -k 
  00:00.0 Host bridge: Intel Corporation 3rd Gen Core processor DRAM Controller 
(rev 09)
  Subsystem: Samsung Electronics Co Ltd Device c0e6
  Kernel driver in use: ivb_uncore
  00:01.0 PCI bridge: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor 
PCI Express Root Port (rev 09)
  Kernel driver in use: pcieport
  00:02.0 VGA compatible controller: Intel Corporation 3rd Gen Core processor 
Graphics Controller (rev 09)
  DeviceName:  Onboard IGD
  Subsystem: Samsung Electronics Co Ltd Device c0e6
  Kernel driver in use: i915
  01:00.0 Display controller: Advanced Micro Devices, Inc. [AMD/ATI] Mars 
[Radeon HD 8670A/8670M/8750M] (rev ff)
  Kernel driver in use: radeon

  
  Possible upstream Debian bug: 
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=803087
  --- 
  ApportVersion: 2.19.1-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  aschmadel   2152 F pulseaudio
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 15.10
  EcryptfsInUse: Yes
  HibernationDevice: 

[Kernel-packages] [Bug 1512848] Lspci.txt

2015-11-03 Thread schmod
apport information

** Attachment added: "Lspci.txt"
   https://bugs.launchpad.net/bugs/1512848/+attachment/4512326/+files/Lspci.txt

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

Title:
  Radeon VCE Init Error

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

Bug description:
  Since upgrading to Ubuntu 15.10, I have encountered graphics
  performance issues, and have occasionally experienced lockups during
  boot.

  dmesg | grep radeon
  [2.103294] [drm] radeon kernel modesetting enabled.
  [2.114677] radeon :01:00.0: enabling device ( -> 0003)
  [2.226348] radeon :01:00.0: VRAM: 1024M 0x - 
0x3FFF (1024M used)
  [2.226349] radeon :01:00.0: GTT: 2048M 0x4000 - 
0xBFFF
  [2.226494] [drm] radeon: 1024M of VRAM memory ready
  [2.226506] [drm] radeon: 2048M of GTT memory ready.
  [2.232296] [drm] radeon: dpm initialized
  [2.234760] [drm] enabling PCIE gen 3 link speeds, disable with 
radeon.pcie_gen2=0
  [3.456910] radeon :01:00.0: WB enabled
  [3.456912] radeon :01:00.0: fence driver on ring 0 use gpu addr 
0x4c00 and cpu addr 0x88041663ac00
  [3.456914] radeon :01:00.0: fence driver on ring 1 use gpu addr 
0x4c04 and cpu addr 0x88041663ac04
  [3.456915] radeon :01:00.0: fence driver on ring 2 use gpu addr 
0x4c08 and cpu addr 0x88041663ac08
  [3.456916] radeon :01:00.0: fence driver on ring 3 use gpu addr 
0x4c0c and cpu addr 0x88041663ac0c
  [3.456918] radeon :01:00.0: fence driver on ring 4 use gpu addr 
0x4c10 and cpu addr 0x88041663ac10
  [3.457696] radeon :01:00.0: fence driver on ring 5 use gpu addr 
0x00075a18 and cpu addr 0xc90002035a18
  [3.558371] radeon :01:00.0: VCE init error (-110).
  [3.558376] radeon :01:00.0: radeon: MSI limited to 32-bit
  [3.558397] radeon :01:00.0: radeon: using MSI.
  [3.558421] [drm] radeon: irq initialized.
  [4.538452] radeon :01:00.0: No connectors reported connected with 
modes
  [4.539564] radeon :01:00.0: fb1: radeondrmfb frame buffer device
  [4.539598] [drm] Initialized radeon 2.43.0 20080528 for :01:00.0 on 
minor 1
  [   11.629124] [drm] enabling PCIE gen 3 link speeds, disable with 
radeon.pcie_gen2=0
  [   12.627048] radeon :01:00.0: WB enabled
  [   12.627050] radeon :01:00.0: fence driver on ring 0 use gpu addr 
0x4c00 and cpu addr 0x88041663ac00
  [   12.627051] radeon :01:00.0: fence driver on ring 1 use gpu addr 
0x4c04 and cpu addr 0x88041663ac04
  [   12.627053] radeon :01:00.0: fence driver on ring 2 use gpu addr 
0x4c08 and cpu addr 0x88041663ac08
  [   12.627054] radeon :01:00.0: fence driver on ring 3 use gpu addr 
0x4c0c and cpu addr 0x88041663ac0c
  [   12.627055] radeon :01:00.0: fence driver on ring 4 use gpu addr 
0x4c10 and cpu addr 0x88041663ac10
  [   12.627838] radeon :01:00.0: fence driver on ring 5 use gpu addr 
0x00075a18 and cpu addr 0xc90002035a18
  [   12.728529] radeon :01:00.0: VCE init error (-110).

  
  xrandr --listproviders
  Providers: number : 3
  Provider 0: id: 0x6a cap: 0x9, Source Output, Sink Offload crtcs: 4 outputs: 
5 associated providers: 2 name:Intel
  Provider 1: id: 0x41 cap: 0x6, Sink Output, Source Offload crtcs: 2 outputs: 
0 associated providers: 2 name:radeon
  Provider 2: id: 0x41 cap: 0x6, Sink Output, Source Offload crtcs: 2 outputs: 
0 associated providers: 2 name:radeon

  
  lspci -k 
  00:00.0 Host bridge: Intel Corporation 3rd Gen Core processor DRAM Controller 
(rev 09)
  Subsystem: Samsung Electronics Co Ltd Device c0e6
  Kernel driver in use: ivb_uncore
  00:01.0 PCI bridge: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor 
PCI Express Root Port (rev 09)
  Kernel driver in use: pcieport
  00:02.0 VGA compatible controller: Intel Corporation 3rd Gen Core processor 
Graphics Controller (rev 09)
  DeviceName:  Onboard IGD
  Subsystem: Samsung Electronics Co Ltd Device c0e6
  Kernel driver in use: i915
  01:00.0 Display controller: Advanced Micro Devices, Inc. [AMD/ATI] Mars 
[Radeon HD 8670A/8670M/8750M] (rev ff)
  Kernel driver in use: radeon

  
  Possible upstream Debian bug: 
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=803087
  --- 
  ApportVersion: 2.19.1-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  aschmadel   2152 F pulseaudio
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 15.10
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=5208c4c8-b199-4f3f-92ad-9addd6bd
  

[Kernel-packages] [Bug 1509120] Re: Process accounting deadlock with idmapd callout when writing to NFSv4 mount

2015-11-03 Thread Dave Chiluk
** Description changed:

+ [Impact]
+ 
+  * Programs accessing nfsv4 mounts will hang on request_key interface
+ with nfs4 + sec=sys with old nfsv4 hosts.  Kernel is waiting on
+ usermodehelper provided by keyutils.
+ 
+  * INFO: task ls:2101 blocked for more than 120 seconds.
+   Not tainted 3.13.0-66-generic #108-Ubuntu
+ "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
+ ls D 88007fd13180 0 2101 1215 0x0004
+  88007b14d630 0086 8800374e6000 88007b14dfd8
+  00013180 00013180 8800374e6000 88007b14d6b0
+  88007ffd1460 0002 812d0ce0 88007b14d6a0
+ Call Trace:
+  [] ? umh_keys_init+0x20/0x20
+  [] schedule+0x29/0x70
+  [] key_wait_bit+0xe/0x20
+  [] __wait_on_bit+0x62/0x90
+  [] ? umh_keys_init+0x20/0x20
+  [] out_of_line_wait_on_bit+0x77/0x90
+  [] ? autoremove_wake_function+0x40/0x40
+  [] wait_for_key_construction+0x6e/0x80
+  [] request_key+0x5c/0xa0
+  [] nfs_idmap_get_key+0xaf/0x1c0 [nfsv4]
+  [] nfs_map_name_to_uid+0xef/0x150 [nfsv4]
+  [] decode_getfattr_attrs+0xe47/0x14b0 [nfsv4]
+  [] ? sched_clock+0x9/0x10
+  [] decode_getfattr_generic.constprop.102+0x8c/0xf0 [nfsv4]
+  [] ? nfs4_xdr_dec_access+0xa0/0xa0 [nfsv4]
+  [] nfs4_xdr_dec_getattr+0x70/0x80 [nfsv4]
+  [] rpcauth_unwrap_resp+0x86/0xd0 [sunrpc]
+  [] ? nfs4_xdr_dec_access+0xa0/0xa0 [nfsv4]
+  [] call_decode+0x1df/0x870 [sunrpc]
+  [] ? call_refreshresult+0x170/0x170 [sunrpc]
+  [] ? call_refreshresult+0x170/0x170 [sunrpc]
+  [] __rpc_execute+0x84/0x400 [sunrpc]
+  [] rpc_execute+0x5e/0xa0 [sunrpc]
+  [] rpc_run_task+0x70/0x90 [sunrpc]
+  [] nfs4_call_sync_sequence+0x56/0x80 [nfsv4]
+  [] _nfs4_proc_getattr+0xbe/0xd0 [nfsv4]
+  [] nfs4_proc_getattr+0x5a/0xd0 [nfsv4]
+  [] __nfs_revalidate_inode+0xbf/0x310 [nfs]
+  [] nfs_opendir+0xe3/0x100 [nfs]
+  [] do_dentry_open+0x233/0x2e0
+  [] ? nfs_readdir_clear_array+0x70/0x70 [nfs]
+  [] vfs_open+0x49/0x50
+  [] do_last+0x564/0x1240
+  [] ? link_path_walk+0x256/0x880
+  [] ? apparmor_file_alloc_security+0x5b/0x180
+  [] ? security_file_alloc+0x16/0x20
+  [] path_openat+0xbb/0x650
+  [] do_filp_open+0x3a/0x90
+  [] ? do_mmap_pgoff+0x34e/0x3d0
+  [] ? __alloc_fd+0xa7/0x130
+  [] do_sys_open+0x129/0x280
+  [] ? do_page_fault+0x1a/0x70
+  [] SyS_openat+0x14/0x20
+  [] system_call_fastpath+0x1a/0x1f
+ 
+ [Regression Potential]
+ 
+  * Minimal this was applied to vivid+wily via bug 1449074.
+ 
+ [Other Info]
+  
+  * Sulution is to add keyutils as Required to nfs-common.
+ 
+ Original Description 
+ __
+ 
  ---Problem Description---
  System hang when process accounting to a NFSv4 mount.
  
  ---uname output---
  Linux ppc001 3.19.0-30-generic #34~14.04.1-Ubuntu SMP Fri Oct 2 22:21:52
  UTC 2015 ppc64le ppc64le ppc64le GNU/Linux
  
  ---Problem Details---
  
  We have a customer that is experiencing intermittent system hangs on
  their system.  After a bit of debug, it was discovered that the trigger
  was turning on process accounting and writing to a file hosted via an
  NFSv4 mount.  During the testing, several vmcores were captured, and the
  fingerprint indicates a mutex deadlock situation with process
  accounting.   In the most recent vmcore, it appears that the scenario is
  something like the following:
  
  1. PID: 4898 COMMAND: "ls" triggers a write to the process accounting file.
  2. The resulting NFS write needs idmapd information and calls out to idmapd
  3. The idmapd usermodehelper process triggers another process accounting 
update that blocks on the mutex being held by PID 4898.
  
  PID: 4898   TASK: c01fd26d7580  CPU: 7   COMMAND: "ls"
-  #0 [c01fd274a950] __switch_to at c0015934
-  #1 [c01fd274ab20] __switch_to at c0015934
-  #2 [c01fd274ab80] __schedule at c0a11de8
-  #3 [c01fd274ada0] schedule_timeout at c0a16284
-  #4 [c01fd274ae90] wait_for_common at c0a1360c
-  #5 [c01fd274af10] call_usermodehelper_exec at c00ccd38
-  #6 [c01fd274af70] call_sbin_request_key at c0429258
-  #7 [c01fd274b100] request_key_and_link at c042983c
-  #8 [c01fd274b200] request_key at c0429978
-  #9 [c01fd274b240] nfs_idmap_get_key at d0002ca8b0bc [nfsv4]
+  #0 [c01fd274a950] __switch_to at c0015934
+  #1 [c01fd274ab20] __switch_to at c0015934
+  #2 [c01fd274ab80] __schedule at c0a11de8
+  #3 [c01fd274ada0] schedule_timeout at c0a16284
+  #4 [c01fd274ae90] wait_for_common at c0a1360c
+  #5 [c01fd274af10] call_usermodehelper_exec at c00ccd38
+  #6 [c01fd274af70] call_sbin_request_key at c0429258
+  #7 [c01fd274b100] request_key_and_link at c042983c
+  #8 [c01fd274b200] request_key at c0429978
+  #9 [c01fd274b240] nfs_idmap_get_key at d0002ca8b0bc [nfsv4]
  #10 [c01fd274b2b0] 

[Kernel-packages] [Bug 1509120] Re: Process accounting deadlock with idmapd callout when writing to NFSv4 mount

2015-11-03 Thread Dave Chiluk
Add keyutils to Depends: for nfs-common

** Patch added: "lp1509120.trusty.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1509120/+attachment/4512348/+files/lp1509120.trusty.debdiff

** Changed in: nfs-utils (Ubuntu)
   Importance: Undecided => Medium

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

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

** Changed in: nfs-utils (Ubuntu)
   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/1509120

Title:
  Process accounting deadlock with idmapd callout when writing to NFSv4
  mount

Status in linux package in Ubuntu:
  Invalid
Status in nfs-utils package in Ubuntu:
  In Progress

Bug description:
  [Impact]

   * Programs accessing nfsv4 mounts will hang on request_key interface
  with nfs4 + sec=sys with old nfsv4 hosts.  Kernel is waiting on
  usermodehelper provided by keyutils.

   * INFO: task ls:2101 blocked for more than 120 seconds.
Not tainted 3.13.0-66-generic #108-Ubuntu
  "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
  ls D 88007fd13180 0 2101 1215 0x0004
   88007b14d630 0086 8800374e6000 88007b14dfd8
   00013180 00013180 8800374e6000 88007b14d6b0
   88007ffd1460 0002 812d0ce0 88007b14d6a0
  Call Trace:
   [] ? umh_keys_init+0x20/0x20
   [] schedule+0x29/0x70
   [] key_wait_bit+0xe/0x20
   [] __wait_on_bit+0x62/0x90
   [] ? umh_keys_init+0x20/0x20
   [] out_of_line_wait_on_bit+0x77/0x90
   [] ? autoremove_wake_function+0x40/0x40
   [] wait_for_key_construction+0x6e/0x80
   [] request_key+0x5c/0xa0
   [] nfs_idmap_get_key+0xaf/0x1c0 [nfsv4]
   [] nfs_map_name_to_uid+0xef/0x150 [nfsv4]
   [] decode_getfattr_attrs+0xe47/0x14b0 [nfsv4]
   [] ? sched_clock+0x9/0x10
   [] decode_getfattr_generic.constprop.102+0x8c/0xf0 [nfsv4]
   [] ? nfs4_xdr_dec_access+0xa0/0xa0 [nfsv4]
   [] nfs4_xdr_dec_getattr+0x70/0x80 [nfsv4]
   [] rpcauth_unwrap_resp+0x86/0xd0 [sunrpc]
   [] ? nfs4_xdr_dec_access+0xa0/0xa0 [nfsv4]
   [] call_decode+0x1df/0x870 [sunrpc]
   [] ? call_refreshresult+0x170/0x170 [sunrpc]
   [] ? call_refreshresult+0x170/0x170 [sunrpc]
   [] __rpc_execute+0x84/0x400 [sunrpc]
   [] rpc_execute+0x5e/0xa0 [sunrpc]
   [] rpc_run_task+0x70/0x90 [sunrpc]
   [] nfs4_call_sync_sequence+0x56/0x80 [nfsv4]
   [] _nfs4_proc_getattr+0xbe/0xd0 [nfsv4]
   [] nfs4_proc_getattr+0x5a/0xd0 [nfsv4]
   [] __nfs_revalidate_inode+0xbf/0x310 [nfs]
   [] nfs_opendir+0xe3/0x100 [nfs]
   [] do_dentry_open+0x233/0x2e0
   [] ? nfs_readdir_clear_array+0x70/0x70 [nfs]
   [] vfs_open+0x49/0x50
   [] do_last+0x564/0x1240
   [] ? link_path_walk+0x256/0x880
   [] ? apparmor_file_alloc_security+0x5b/0x180
   [] ? security_file_alloc+0x16/0x20
   [] path_openat+0xbb/0x650
   [] do_filp_open+0x3a/0x90
   [] ? do_mmap_pgoff+0x34e/0x3d0
   [] ? __alloc_fd+0xa7/0x130
   [] do_sys_open+0x129/0x280
   [] ? do_page_fault+0x1a/0x70
   [] SyS_openat+0x14/0x20
   [] system_call_fastpath+0x1a/0x1f

  [Regression Potential]

   * Minimal this was applied to vivid+wily via bug 1449074.

  [Other Info]
   
   * Sulution is to add keyutils as Required to nfs-common.

  Original Description 
  __

  ---Problem Description---
  System hang when process accounting to a NFSv4 mount.

  ---uname output---
  Linux ppc001 3.19.0-30-generic #34~14.04.1-Ubuntu SMP Fri Oct 2 22:21:52
  UTC 2015 ppc64le ppc64le ppc64le GNU/Linux

  ---Problem Details---

  We have a customer that is experiencing intermittent system hangs on
  their system.  After a bit of debug, it was discovered that the
  trigger was turning on process accounting and writing to a file hosted
  via an NFSv4 mount.  During the testing, several vmcores were
  captured, and the fingerprint indicates a mutex deadlock situation
  with process accounting.   In the most recent vmcore, it appears that
  the scenario is something like the following:

  1. PID: 4898 COMMAND: "ls" triggers a write to the process accounting file.
  2. The resulting NFS write needs idmapd information and calls out to idmapd
  3. The idmapd usermodehelper process triggers another process accounting 
update that blocks on the mutex being held by PID 4898.

  PID: 4898   TASK: c01fd26d7580  CPU: 7   COMMAND: "ls"
   #0 [c01fd274a950] __switch_to at c0015934
   #1 [c01fd274ab20] __switch_to at c0015934
   #2 [c01fd274ab80] __schedule at c0a11de8
   #3 [c01fd274ada0] schedule_timeout at c0a16284
   #4 [c01fd274ae90] wait_for_common at c0a1360c
   #5 [c01fd274af10] call_usermodehelper_exec at c00ccd38
   #6 [c01fd274af70] call_sbin_request_key at c0429258
   #7 [c01fd274b100] request_key_and_link at c042983c
 

[Kernel-packages] [Bug 1495043] Re: Suspend/Resume Regression 3.19.0-28-generic Dell xps15

2015-11-03 Thread Joachim Van der Auwera
I seem to have the same problem on a Dell M3800.
Unfortunately, I have no "wl" module installed, so that does not make a 
difference.
The problem appeared in a 15.04 in one of the last weeks before 15.10 release. 
It is still there in 15.10.

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

Title:
  Suspend/Resume Regression 3.19.0-28-generic Dell xps15

Status in linux package in Ubuntu:
  Triaged

Bug description:
  Suspend resume was working on 3.19.0-26 but 3.19.0-28 appears to
  suspend, but no longer resumes.  Relevant portion of dmesg info using
  pm-trace is as follows:

  [1.168740] registered taskstats version 1
  [1.170526] Key type trusted registered
  [1.174836] Key type encrypted registered
  [1.174843] AppArmor: AppArmor sha1 policy hashing enabled
  [1.176721] input: AT Translated Set 2 keyboard as 
/devices/platform/i8042/serio0/input/input3
  [1.398911] evm: HMAC attrs: 0x1
  [1.399640]   Magic number: 0:469:661
  [1.399643]   hash matches 
/build/linux-5xFjum/linux-3.19.0/drivers/base/power/main.c:642
  [1.399655]   hash matches 
/build/linux-5xFjum/linux-3.19.0/drivers/base/power/main.c:738
  [1.399670] block ram14: hash matches
  [1.399692] platform PNP0C0A:00: hash matches
  [1.399711] battery PNP0C0A:00: hash matches
  [1.399793] rtc_cmos 00:01: setting system clock to 1976-02-02 02:39:41 
UTC (192076781)
  [1.399886] BIOS EDD facility v0.16 2004-Jun-25, 0 devices found
  [1.399887] EDD information not available.
  [1.399970] PM: Hibernation image not present or could not be loaded.
  [1.400304] Freeing unused kernel memory: 1408K (81d36000 - 
81e96000)
  [1.400305] Write protecting the kernel read-only data: 12288k

  To reproduce the bug:
  1) Boot into Ubuntu Gnome with kernel 3.19.0.28-generic
  2) Log in to desktop.
  3) Close laptop lid
  4) Wait about 10 seconds (doesn't seem to be critical how long you wait)
  5) Open laptop lid.

  What happens:
  The keyboard backlight and the power button light come on, but the screen 
remains blank.  Using Ctr-Alt-F1 does nothing (can't get to a virtual console, 
indicating that it's not just X that has stopped)

  What I expect to happen:
  On opening of the laptop lid, I expect the lockscreen to show.

  Other info:
  This laptop has nvidia graphics disabled using nvidia-prime

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: linux-image-3.19.0-28-generic 3.19.0-28.30
  ProcVersionSignature: Ubuntu 3.19.0-28.30-generic 3.19.8-ckt5
  Uname: Linux 3.19.0-28-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.17.2-0ubuntu1.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  mark   1566 F pulseaudio
   /dev/snd/controlC0:  mark   1566 F pulseaudio
  CurrentDesktop: GNOME
  Date: Sat Sep 12 19:26:03 2015
  HibernationDevice: RESUME=UUID=ff91bc8d-f7ef-4650-81e0-608068f4f8cb
  InstallationDate: Installed on 2015-08-31 (12 days ago)
  InstallationMedia: Ubuntu-GNOME 15.04 "Vivid Vervet" - Release amd64 
(20150422)
  MachineType: Dell Inc. XPS 15 9530
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-28-generic.efi.signed 
root=UUID=b69e369b-42c8-4f85-8a2c-dcfec06b7d88 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.19.0-28-generic N/A
   linux-backports-modules-3.19.0-28-generic  N/A
   linux-firmware 1.143.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/30/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A09
  dmi.board.name: XPS 15 9530
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A09
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvrA09:bd07/30/2015:svnDellInc.:pnXPS159530:pvrA09:rvnDellInc.:rnXPS159530:rvrA09:cvnDellInc.:ct8:cvrNotSpecified:
  dmi.product.name: XPS 15 9530
  dmi.product.version: A09
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1495043/+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 1511577] Re: CVE-2015-8019

2015-11-03 Thread Steve Beattie
** Changed in: linux-raspi2 (Ubuntu Precise)
   Status: New => Invalid

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

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

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

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

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

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

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

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

Title:
  CVE-2015-8019

Status in linux package in Ubuntu:
  New
Status in linux-armadaxp package in Ubuntu:
  Invalid
Status in linux-ec2 package in Ubuntu:
  Invalid
Status in linux-flo package in Ubuntu:
  New
Status in linux-fsl-imx51 package in Ubuntu:
  Invalid
Status in linux-goldfish package in Ubuntu:
  New
Status in linux-lts-backport-maverick package in Ubuntu:
  New
Status in linux-lts-backport-natty 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-mako package in Ubuntu:
  New
Status in linux-manta package in Ubuntu:
  New
Status in linux-mvl-dove 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:
  New
Status in linux-armadaxp source package in Precise:
  New
Status in linux-ec2 source package in Precise:
  Invalid
Status in linux-flo source package in Precise:
  Invalid
Status in linux-fsl-imx51 source package in Precise:
  Invalid
Status in linux-goldfish source package in Precise:
  Invalid
Status in linux-lts-backport-maverick source package in Precise:
  New
Status in linux-lts-backport-natty source package in Precise:
  New
Status in linux-lts-quantal source package in Precise:
  New
Status in linux-lts-raring source package in Precise:
  Invalid
Status in linux-lts-saucy source package in Precise:
  New
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-mako source package in Precise:
  Invalid
Status in linux-manta source package in Precise:
  Invalid
Status in linux-mvl-dove source package in Precise:
  Invalid
Status in linux-raspi2 source package in Precise:
  Invalid
Status in linux-ti-omap4 source package in Precise:
  New
Status in linux source package in Trusty:
  New
Status in linux-armadaxp source package in Trusty:
  Invalid
Status in linux-ec2 source package in Trusty:
  Invalid
Status in linux-flo source package in Trusty:
  Invalid
Status in linux-fsl-imx51 source package in Trusty:
  Invalid
Status in linux-goldfish source package in Trusty:
  Invalid
Status in linux-lts-backport-maverick source package in Trusty:
  New
Status in linux-lts-backport-natty source package in Trusty:
  New
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:
  New
Status in linux-lts-vivid 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-mvl-dove 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:
  Invalid
Status in linux-ec2 source package in Vivid:
  Invalid
Status in linux-flo source package in Vivid:
  New
Status in linux-fsl-imx51 source package in Vivid:
  Invalid
Status in linux-goldfish source package in Vivid:
  New
Status in linux-lts-backport-maverick source package in Vivid:
  New
Status in linux-lts-backport-natty source package in Vivid:
  New
Status in linux-lts-quantal source package in Vivid:
  Invalid
Status in linux-lts-raring source package in Vivid:
  Invalid
Status in linux-lts-saucy source package in Vivid:
  Invalid
Status in linux-lts-trusty source package in Vivid:
  Invalid
Status in linux-lts-utopic source package in Vivid:
  Invalid
Status in linux-lts-vivid source package in Vivid:
  Invalid
Status in linux-mako source package in 

[Kernel-packages] [Bug 1507588] Re: linux is missing provides for virtualbox-guest-modules [i386 amd64 x32]

2015-11-03 Thread Andy Whitcroft
Now correctly on linux-image-*:

 Provides: fuse-module, ivtv-modules, kvm-api-4, linux-image, linux-
image-3.0, redhat-cluster-modules, virtualbox-guest-modules


** Tags removed: verification-needed-wily
** Tags added: verification-done-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/1507588

Title:
  linux is missing provides for virtualbox-guest-modules [i386 amd64
  x32]

Status in linux package in Ubuntu:
  Fix Committed
Status in linux-meta package in Ubuntu:
  Fix Committed

Bug description:
  We are missing provides for virtualbox-guest-modules [i386 amd64 x32]
  on the main kernel.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1507588/+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 1488170] Re: Bluetooth initiated after quitting airplane mode

2015-11-03 Thread Sven
Also experienced on Aquaris E5 OTA-6

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

Title:
  Bluetooth initiated after quitting airplane mode

Status in Canonical System Image:
  Confirmed
Status in bluez package in Ubuntu:
  Confirmed
Status in urfkill package in Ubuntu:
  Confirmed

Bug description:
  This happens despite bluetooth not being enabled when entering
  airplane mode.

  On Aquaris E5 OTA-5.

  Boot with bluetooth disabled
  Turn on flight mode
  turn off flight mode
  Bluetooth gets enabled

  See bug #1421249 for related symptoms

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1488170/+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 1512848] Re: Radeon VCE Init Error

2015-11-03 Thread Bug Watch Updater
** Changed in: linux (Debian)
   Status: Unknown => 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/1512848

Title:
  Radeon VCE Init Error

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

Bug description:
  Since upgrading to Ubuntu 15.10, I have encountered graphics
  performance issues, and have occasionally experienced lockups during
  boot.

   dmesg | grep -E 'drm|radeon'
  [2.164605] [drm] Initialized drm 1.1.0 20060810
  [2.192852] [drm] radeon kernel modesetting enabled.
  [2.201268] [drm] Memory usable by graphics device = 2048M
  [2.201274] fb: switching to inteldrmfb from EFI VGA
  [2.201394] [drm] Replacing VGA console driver
  [2.204234] radeon :01:00.0: enabling device ( -> 0003)
  [2.207919] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
  [2.207921] [drm] Driver supports precise vblank timestamp query.
  [2.242929] fbcon: inteldrmfb (fb0) is primary device
  [3.529125] [drm:intel_pipe_config_compare [i915]] *ERROR* mismatch in 
has_drrs (expected 1, found 0)
  [3.529141] WARNING: CPU: 1 PID: 195 at 
/home/kernel/COD/linux/drivers/gpu/drm/i915/intel_display.c:12700 
intel_modeset_check_state+0x5aa/0x870 [i915]()
  [3.529150] Modules linked in: hid_logitech_hidpp hid_logitech_dj usbhid 
hid rtsx_usb_sdmmc rtsx_usb amdkfd amd_iommu_v2 i915(+) radeon(+) i2c_algo_bit 
ttm drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops psmouse r8169 
ahci drm libahci mii fjes wmi video
  [3.529201]  [] drm_atomic_commit+0x37/0x60 [drm]
  [3.529206]  [] drm_atomic_helper_set_config+0x1bf/0x420 
[drm_kms_helper]
  [3.529212]  [] drm_mode_set_config_internal+0x62/0x100 
[drm]
  [3.529215]  [] restore_fbdev_mode+0xb3/0x110 
[drm_kms_helper]
  [3.529219]  [] 
drm_fb_helper_restore_fbdev_mode_unlocked+0x25/0x70 [drm_kms_helper]
  [3.529221]  [] drm_fb_helper_set_par+0x2d/0x50 
[drm_kms_helper]
  [3.529253]  [] drm_fb_helper_initial_config+0x250/0x3e0 
[drm_kms_helper]
  [3.535608] i915 :00:02.0: fb0: inteldrmfb frame buffer device
  [3.546293] [drm] Initialized i915 1.6.0 20150731 for :00:02.0 on 
minor 0
  [3.546469] [drm] initializing kernel modesetting (OLAND 0x1002:0x6600 
0x144D:0xC0E6).
  [3.546483] [drm] register mmio base: 0xF7E0
  [3.546484] [drm] register mmio size: 262144
  [3.574408] [drm] GPU not posted. posting now...
  [3.587216] radeon :01:00.0: VRAM: 1024M 0x - 
0x3FFF (1024M used)
  [3.587218] radeon :01:00.0: GTT: 2048M 0x4000 - 
0xBFFF
  [3.587220] [drm] Detected VRAM RAM=1024M, BAR=256M
  [3.587220] [drm] RAM width 128bits DDR
  [3.587314] [drm] radeon: 1024M of VRAM memory ready
  [3.587315] [drm] radeon: 2048M of GTT memory ready.
  [3.587322] [drm] Loading oland Microcode
  [3.587398] [drm] Internal thermal controller without fan control
  [3.587450] [drm] probing gen 2 caps for device 8086:151 = 261ad03/e
  [3.593155] [drm] radeon: dpm initialized
  [3.594806] [drm] Found VCE firmware/feedback version 50.0.1 / 17!
  [3.594811] [drm] GART: num cpu pages 524288, num gpu pages 524288
  [3.595617] [drm] probing gen 2 caps for device 8086:151 = 261ad03/e
  [3.595620] [drm] enabling PCIE gen 3 link speeds, disable with 
radeon.pcie_gen2=0
  [4.815819] [drm] PCIE GART of 2048M enabled (table at 0x002E8000).
  [4.815912] radeon :01:00.0: WB enabled
  [4.815914] radeon :01:00.0: fence driver on ring 0 use gpu addr 
0x4c00 and cpu addr 0x880416408c00
  [4.815916] radeon :01:00.0: fence driver on ring 1 use gpu addr 
0x4c04 and cpu addr 0x880416408c04
  [4.815917] radeon :01:00.0: fence driver on ring 2 use gpu addr 
0x4c08 and cpu addr 0x880416408c08
  [4.815918] radeon :01:00.0: fence driver on ring 3 use gpu addr 
0x4c0c and cpu addr 0x880416408c0c
  [4.815919] radeon :01:00.0: fence driver on ring 4 use gpu addr 
0x4c10 and cpu addr 0x880416408c10
  [4.816694] radeon :01:00.0: fence driver on ring 5 use gpu addr 
0x00075a18 and cpu addr 0xc90003035a18
  [4.917369] radeon :01:00.0: VCE init error (-110).
  [4.917391] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
  [4.917391] [drm] Driver supports precise vblank timestamp query.
  [4.917393] radeon :01:00.0: radeon: MSI limited to 32-bit
  [4.917461] radeon :01:00.0: radeon: using MSI.
  [4.917484] [drm] radeon: irq initialized.
  [5.062349] [drm] ring test on 0 succeeded in 2 usecs
  [5.062353] [drm] ring test on 1 succeeded in 1 usecs
  [5.062356] [drm] ring test on 2 succeeded in 1 usecs
  [5.062362] [drm] ring 

[Kernel-packages] [Bug 1189721] Re: Ralink RT3290 doesn't have a bluetooth driver

2015-11-03 Thread Alexandre Magno
I want notify that I have no more access to a test machine. The project
at GitHub is stopped but still accepts pull requests. Sorry.

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

Title:
  Ralink RT3290 doesn't have a bluetooth driver

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

Bug description:
  As of Raring Ubuntu has a wifi driver for the RT3290 that works out of
  the box.

  It still does not have bluetooth support.

  This thread in the Ubuntu forums links to a driver that is claimed to
  work:

  http://ubuntuforums.org/showthread.php?t=2115570
  --- 
  ApportVersion: 2.9.2-0ubuntu8.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  graeme 2412 F pulseaudio
  CRDA:
   country GB:
(2402 - 2482 @ 40), (N/A, 20)
(5170 - 5250 @ 40), (N/A, 20)
(5250 - 5330 @ 40), (N/A, 20), DFS
(5490 - 5710 @ 40), (N/A, 27), DFS
  DistroRelease: Ubuntu 13.04
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=2d107179-35e2-4b1f-8bdd-90a01132ec70
  InstallationDate: Installed on 2013-05-17 (144 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  MachineType: Hewlett-Packard HP ProBook 4540s
  MarkForUpload: True
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-31-generic 
root=UUID=ac74fd89-3445-4a6d-b91b-ae4987867afe ro quiet splash 
acpi_backlight=vendor vt.handoff=7
  ProcVersionSignature: Ubuntu 3.8.0-31.46-generic 3.8.13.8
  RelatedPackageVersions:
   linux-restricted-modules-3.8.0-31-generic N/A
   linux-backports-modules-3.8.0-31-generic  N/A
   linux-firmware1.106
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  Tags:  raring
  Uname: Linux 3.8.0-31-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo
  dmi.bios.date: 11/06/2012
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 68IRR Ver. F.32
  dmi.board.name: 17F6
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 58.1D
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68IRRVer.F.32:bd11/06/2012:svnHewlett-Packard:pnHPProBook4540s:pvrA1018C1100:rvnHewlett-Packard:rn17F6:rvrKBCVersion58.1D:cvnHewlett-Packard:ct10:cvr:
  dmi.product.name: HP ProBook 4540s
  dmi.product.version: A1018C1100
  dmi.sys.vendor: Hewlett-Packard

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1189721/+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 1512593] Re: :Ubuntu NV: Panic timeout=0 means Ubuntu does not reboot and recover from HMI (e.g. Core Unit Checkstop)

2015-11-03 Thread Chris J Arges
This is not a bug with our kernel config. Perhaps changing the userspace tool 
to check for this behavior and setting the sysctl value to the desired value 
may be possible.
Marking as Invalid for now, please feel free to reopen if you feel this is 
still an issue.
Thanks!

** Changed in: linux (Ubuntu)
   Status: In Progress => 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/1512593

Title:
  :Ubuntu NV: Panic timeout=0 means Ubuntu does not reboot and recover
  from HMI (e.g. Core Unit Checkstop)

Status in linux package in Ubuntu:
  Invalid

Bug description:
  Problem Description
  ==
  I attempted to inject a Core Unit Checkstop error by flipping Core FIR bit 5 
on a K80 (Nvidia) 42L Server ( FSP - gp4fp1.aus.stglabs.ibm.com ). I was 
expecting the server to crash due to a Sapphire assert ( PEL with SRC BB821410 
) and a Sapphire dump to be collected in the process.

  However on injecting the error , the host ( Ubuntu NV ) crashed, and
  never recovered. OPAL however seemed to stay up and there were a
  plethora of mail box errors - B182953C logged by the FSP.

  Error Inject
  --
  $ putscom pu.ex 10013100 5 1 1 -ib -p3 -c5
  s1.ex   k0:n0:s0:p03:c5
  ecmd_ppc putscom pu.ex 10013100 5 1 1 -ib -p3 -c5

  
  Console message
  --
  [htx@gp4p01]  [1m/sys/devices/system/cpu# [0m [ 1652.976253] Fatal Hypervisor 
Maintenance interrupt [Not recovered]
  [ 1652.976332]  Error detail: Malfunction Alert
  [ 1652.976402]  HMER: 8040
  [ 1652.976450] Kernel panic - not syncing: Unrecoverable HMI exception
  [ 1652.976467] CPU: 24 PID: 1261 Comm: kworker/24:1 Tainted: P   OE 
3.16.0-37-generic #51~14.04.1-Ubuntu
  [ 1652.976530] Workqueue: events hmi_event_handler
  [ 1652.976561] Call Trace:
  [ 1652.976571] [c000189bf9e0] [c0017330] show_stack+0x170/0x290 
(unreliable)
  [ 1652.976647] [c000189bfac0] [c09eb8e4] dump_stack+0x90/0xbc
  [ 1652.976674] [c000189bfaf0] [c09e2b5c] panic+0x104/0x2a8
  [ 1652.976703] [c000189bfb80] [c007306c] 
hmi_event_handler+0x19c/0x2b0
  [ 1652.976732] [c000189bfc50] [c00d62dc] 
process_one_work+0x1ac/0x4d0
  [ 1652.976772] [c000189bfce0] [c00d6b80] worker_thread+0x190/0x630
  [ 1652.976800] [c000189bfd80] [c00e0024] kthread+0x114/0x140
  [ 1652.976837] [c000189bfe30] [c000a468] 
ret_from_kernel_thread+0x5c/0x74
  [ 1652.977085] ---[ end Kernel panic - not syncing: Unrecoverable HMI 
exception
   

  .
  .
  .
  .
  
|--|
  | 0x50227CFC 06/14/2015 22:27:43 System Hypervisor Firmware   
mbox |
  | 0x50227CFC Processed   Predictive Error 
B182953C | --> Unexpected mail box error , needs investigation 
  
|--|
  | 0x50227CDD 06/14/2015 22:27:21 System Hypervisor Firmware   
spif |
  | 0x50227CDD Processed   Predictive Error 
B182951C | --> Unexpected mail box error , needs investigation 
  
|--|
  | 0x50227CC0 06/14/2015 22:26:57 System Hypervisor Firmware   
mbox |
  | 0x50227CC0 Processed   Predictive Error 
B182953C | --> Unexpected mail box error , needs investigation 
  
|--|
  | 0x50227C9E 06/14/2015 22:26:31 System Hypervisor Firmware   
spif |
  | 0x50227C9E Processed   Predictive Error 
B182951C | --> Unexpected mail box error , needs investigation 
  
|--|
  | 0x50227C88 06/14/2015 22:26:12 System Hypervisor Firmware   
mbox |
  | 0x50227C88 Processed   Predictive Error 
B182953C | --> Unexpected mail box error , needs investigation 
  
|--|
  | 0x50227C7E 06/14/2015 22:26:06 System Hypervisor Firmware   
spif |
  | 0x50227C7E Processed   Predictive Error 
B182951C | --> Unexpected mail box error , needs investigation 
  
|--|
  | 0x50227C4F 06/14/2015 22:25:27 System Hypervisor Firmware   
mbox |
  | 0x50227C4F Processed   Predictive Error 
B182953C | --> Unexpected mail box error , needs investigation 
  
|--|
  | 0x50227C40 06/14/2015 22:25:16 System Hypervisor Firmware   
spif |
  | 0x50227C40 

[Kernel-packages] [Bug 1498862] Re: autopkgtest: rebuild test should not run when testing ourselves

2015-11-03 Thread Andy Whitcroft
Latest testing shows this short circuited:

adt-run [02:02:32]: test rebuild: [---
rebuild: short circuiting build for 'linux-meta/4.2.0.17.19'
adt-run [02:02:33]: test rebuild: ---]

** Tags removed: verification-needed-wily
** Tags added: verification-done-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/1498862

Title:
  autopkgtest: rebuild test should not run when testing ourselves

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

Bug description:
  We have a rebuild test which is intended to confirm the kernel still
  builds when core-utils, gcc, ld etc change.  It makes no sense for
  this test to run for the kernel itself as it takes a very long time to
  run and we have literally just built the kernel with those tools.

  Check for the trigger being something other than the kernel packages
  themselves before doing the rebuild.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1498862/+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 1512900] [NEW] spontaneous suspend/resume failure

2015-11-03 Thread Matthias Andree
Public bug reported:

Computer failed to resume, at least USB did not come back online, screen
remained blank.

ProblemType: KernelOops
DistroRelease: Ubuntu 14.04
Package: linux-image-3.19.0-31-generic 3.19.0-31.36~14.04.1
ProcVersionSignature: Ubuntu 3.19.0-31.36~14.04.1-generic 3.19.8-ckt7
Uname: Linux 3.19.0-31-generic x86_64
Annotation: This occured during a previous suspend and prevented it from 
resuming properly.
ApportVersion: 2.14.1-0ubuntu3.18
Architecture: amd64
Date: Tue Nov  3 23:16:21 2015
ExecutablePath: /usr/share/apport/apportcheckresume
Failure: suspend/resume
InterpreterPath: /usr/bin/python3.4
ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume
ProcEnviron:
 TERM=linux
 PATH=(custom, no user)
SourcePackage: linux-lts-vivid
Title: suspend/resume failure
UpgradeStatus: Upgraded to trusty on 2014-08-29 (431 days ago)
UserGroups:

** Affects: linux-lts-vivid (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-kerneloops resume suspend trusty

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

Title:
  spontaneous suspend/resume failure

Status in linux-lts-vivid package in Ubuntu:
  New

Bug description:
  Computer failed to resume, at least USB did not come back online,
  screen remained blank.

  ProblemType: KernelOops
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.19.0-31-generic 3.19.0-31.36~14.04.1
  ProcVersionSignature: Ubuntu 3.19.0-31.36~14.04.1-generic 3.19.8-ckt7
  Uname: Linux 3.19.0-31-generic x86_64
  Annotation: This occured during a previous suspend and prevented it from 
resuming properly.
  ApportVersion: 2.14.1-0ubuntu3.18
  Architecture: amd64
  Date: Tue Nov  3 23:16:21 2015
  ExecutablePath: /usr/share/apport/apportcheckresume
  Failure: suspend/resume
  InterpreterPath: /usr/bin/python3.4
  ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
  SourcePackage: linux-lts-vivid
  Title: suspend/resume failure
  UpgradeStatus: Upgraded to trusty on 2014-08-29 (431 days ago)
  UserGroups:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-lts-vivid/+bug/1512900/+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 1488719] Re: dmesg shows "[drm:gen8_irq_handler [i915]] *ERROR* The master control interrupt lied (SDE)!"

2015-11-03 Thread Jeroko
I get this error on my new Toshiba P50t-C-104, with kernel 4.3. No
monitors attached, just the default laptop screen. I get a black screen
after this message on boot. The only way to boot is to use the
'nomodeset' kernel parameter, but that dissables the intel graphics
card.

[6.254918] [drm:i915_gem_open] 
[6.254990] [drm:drm_mode_getresources] CRTC[3] CONNECTORS[2] ENCODERS[2]
[6.254993] [drm:drm_mode_getresources] [CRTC:21]
[6.254995] [drm:drm_mode_getresources] [CRTC:25]
[6.254996] [drm:drm_mode_getresources] [CRTC:29]
[6.254997] [drm:drm_mode_getresources] [ENCODER:31:TMDS-31]
[6.254999] [drm:drm_mode_getresources] [ENCODER:39:TMDS-39]
[6.255000] [drm:drm_mode_getresources] [CONNECTOR:32:eDP-1]
[6.255002] [drm:drm_mode_getresources] [CONNECTOR:40:HDMI-A-1]
[6.255003] [drm:drm_mode_getresources] CRTC[3] CONNECTORS[2] ENCODERS[2]
[6.255008] [drm:drm_mode_getconnector] [CONNECTOR:32:?]
[6.255010] [drm:drm_helper_probe_single_connector_modes_merge_bits] 
[CONNECTOR:32:eDP-1]
[6.255011] [drm:intel_dp_detect] [CONNECTOR:32:eDP-1]
[6.255018] [drm:edp_panel_vdd_on] Turning eDP port A VDD on
[6.255024] [drm:edp_panel_vdd_on] PP_STATUS: 0x8008 PP_CONTROL: 
0xabcd000f
[6.255476] [drm:drm_edid_to_eld] ELD: no CEA Extension found
[6.255480] [drm:drm_helper_probe_single_connector_modes_merge_bits] 
[CONNECTOR:32:eDP-1] probed modes :
[6.255483] [drm:drm_mode_debug_printmodeline] Modeline 33:"3840x2160" 60 
533250 3840 3888 3920 4000 2160 2163 2168  0x48 0xa
[6.255487] [drm:drm_mode_getconnector] [CONNECTOR:32:?]
[6.255497] [drm:drm_mode_getconnector] [CONNECTOR:40:?]
[6.255498] [drm:drm_helper_probe_single_connector_modes_merge_bits] 
[CONNECTOR:40:HDMI-A-1]
[6.255500] [drm:intel_hdmi_detect] [CONNECTOR:40:HDMI-A-1]
[6.255657] [drm:gmbus_xfer] GMBUS [i915 gmbus dpb] NAK for addr: 0050 w(1)
[6.255658] [drm:gmbus_xfer] GMBUS [i915 gmbus dpb] NAK on first message, 
retry
[6.255815] [drm:gen8_irq_handler [i915]] *ERROR* The master control 
interrupt lied (SDE)!
[6.255817] [drm:gmbus_xfer] GMBUS [i915 gmbus dpb] NAK for addr: 0050 w(1)
[6.255819] [drm:drm_do_probe_ddc_edid] drm: skipping non-existent adapter 
i915 gmbus dpb
[6.255821] [drm:drm_helper_probe_single_connector_modes_merge_bits] 
[CONNECTOR:40:HDMI-A-1] disconnected
[6.255824] [drm:drm_mode_getconnector] [CONNECTOR:40:?]
[6.255826] [drm:drm_helper_probe_single_connector_modes_merge_bits] 
[CONNECTOR:40:HDMI-A-1]
[6.255828] [drm:intel_hdmi_detect] [CONNECTOR:40:HDMI-A-1]
[6.255986] [drm:gmbus_xfer] GMBUS [i915 gmbus dpb] NAK for addr: 0050 w(1)
[6.255988] [drm:gmbus_xfer] GMBUS [i915 gmbus dpb] NAK on first message, 
retry
[6.256147] [drm:gen8_irq_handler [i915]] *ERROR* The master control 
interrupt lied (SDE)!
[6.256149] [drm:gmbus_xfer] GMBUS [i915 gmbus dpb] NAK for addr: 0050 w(1)
[6.256150] [drm:drm_do_probe_ddc_edid] drm: skipping non-existent adapter 
i915 gmbus dpb
[6.256152] [drm:drm_helper_probe_single_connector_modes_merge_bits] 
[CONNECTOR:40:HDMI-A-1] disconnected
[6.302099] init: alsa-restore main process (976) terminated with status 99

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

Title:
  dmesg shows "[drm:gen8_irq_handler [i915]] *ERROR* The master control
  interrupt lied (SDE)!"

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

Bug description:
  On a recent intel NUC using i915 graphics, I get the following errors
  in dmesg:

  [drm:gen8_irq_handler [i915]] *ERROR* The master control interrupt
  lied (SDE)!

  There are two monitors connected to this box, one with mini-
  HDMI->HDMI, one with mini-DP->HDMI cable.

  Maybe related:

  https://bugs.freedesktop.org/show_bug.cgi?id=80896

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: linux-image-generic 3.19.0.26.25
  ProcVersionSignature: Ubuntu 3.19.0-26.28-generic 3.19.8-ckt4
  Uname: Linux 3.19.0-26-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1.3
  Architecture: amd64
  Date: Wed Aug 26 10:07:31 2015
  InstallationDate: Installed on 2015-08-01 (24 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-26-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root 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)

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1488719/+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 1189721] Re: Ralink RT3290 doesn't have a bluetooth driver

2015-11-03 Thread Alexandre Magno
My brother donated the machine to my brother in law and he does not use
GNU/Linux.

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

Title:
  Ralink RT3290 doesn't have a bluetooth driver

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

Bug description:
  As of Raring Ubuntu has a wifi driver for the RT3290 that works out of
  the box.

  It still does not have bluetooth support.

  This thread in the Ubuntu forums links to a driver that is claimed to
  work:

  http://ubuntuforums.org/showthread.php?t=2115570
  --- 
  ApportVersion: 2.9.2-0ubuntu8.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  graeme 2412 F pulseaudio
  CRDA:
   country GB:
(2402 - 2482 @ 40), (N/A, 20)
(5170 - 5250 @ 40), (N/A, 20)
(5250 - 5330 @ 40), (N/A, 20), DFS
(5490 - 5710 @ 40), (N/A, 27), DFS
  DistroRelease: Ubuntu 13.04
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=2d107179-35e2-4b1f-8bdd-90a01132ec70
  InstallationDate: Installed on 2013-05-17 (144 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  MachineType: Hewlett-Packard HP ProBook 4540s
  MarkForUpload: True
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-31-generic 
root=UUID=ac74fd89-3445-4a6d-b91b-ae4987867afe ro quiet splash 
acpi_backlight=vendor vt.handoff=7
  ProcVersionSignature: Ubuntu 3.8.0-31.46-generic 3.8.13.8
  RelatedPackageVersions:
   linux-restricted-modules-3.8.0-31-generic N/A
   linux-backports-modules-3.8.0-31-generic  N/A
   linux-firmware1.106
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  Tags:  raring
  Uname: Linux 3.8.0-31-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo
  dmi.bios.date: 11/06/2012
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 68IRR Ver. F.32
  dmi.board.name: 17F6
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 58.1D
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68IRRVer.F.32:bd11/06/2012:svnHewlett-Packard:pnHPProBook4540s:pvrA1018C1100:rvnHewlett-Packard:rn17F6:rvrKBCVersion58.1D:cvnHewlett-Packard:ct10:cvr:
  dmi.product.name: HP ProBook 4540s
  dmi.product.version: A1018C1100
  dmi.sys.vendor: Hewlett-Packard

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1189721/+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 1129865] Re: [Broadcom Combo BT/Wifi Card] 21D3 21D7 Bluetooth does not detect anything at all

2015-11-03 Thread Vincent Gerris
also for 15.04 with 105b:e065 Product=BCM43142A0.
details for fix:
https://github.com/gnebehay/gnebehay.com/blob/master/contents/blog/lenovo-flexpad-bluetooth-debian/index.md
it works for 3.19. the 0-31-generic 4 bit kernel, I just had to :
sudo rfkill unblock all
to get the bluetooth soft unblocked before the un- and reload of the module.
I suppose that approach works for more hardware.

How can we get it in the kernel?

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

Title:
  [Broadcom Combo BT/Wifi Card] 21D3 21D7 Bluetooth does not detect
  anything at all

Status in linux package in Ubuntu:
  Won't Fix
Status in linux source package in Precise:
  Won't Fix
Status in linux source package in Quantal:
  Won't Fix
Status in linux source package in Raring:
  Won't Fix
Status in linux source package in Trusty:
  Confirmed

Bug description:
  Tried several attemtps to scan for new bluetooth devices (BT icon ->
  Set up new device).  I tried this with three bluetooth headsets, a
  bluetooth mouse and a cellphone, in an environment where there are
  multiple active bluetooth targets that are discoverable.

  The bluetooth adapter on this system did not, at any time, detect ANY
  bluetooth device.  I verified MY devices by pairing them all with my
  own laptop and all three were pairable.

  rfkill indicates that there are no blocks

  ubuntu@201107-8317:~$ rfkill list
  0: dell-wifi: Wireless LAN
Soft blocked: no
Hard blocked: no
  1: hci0: Bluetooth
Soft blocked: no
Hard blocked: no

  and syslog shows where the device entered discovery but it failed to
  detect anything.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: linux-image-3.2.0-38-generic 3.2.0-38.60
  ProcVersionSignature: Ubuntu 3.2.0-38.60-generic 3.2.37
  Uname: Linux 3.2.0-38-generic x86_64
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
  ApportVersion: 2.0.1-0ubuntu17.1
  Architecture: amd64
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 1: Generic_1 [HD-Audio Generic], device 0: ALC269VB Analog [ALC269VB 
Analog]
 Subdevices: 1/1
 Subdevice #0: subdevice #0
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  ubuntu 1769 F pulseaudio
   /dev/snd/controlC0:  ubuntu 1769 F pulseaudio
  CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 
not found.
  Card0.Amixer.info:
   Card hw:0 'Generic'/'HD-Audio Generic at 0xa0344000 irq 52'
 Mixer name : 'ATI R6xx HDMI'
 Components : 'HDA:1002aa01,00aa0100,00100200'
 Controls  : 6
 Simple ctrls  : 1
  Card0.Amixer.values:
   Simple mixer control 'IEC958',0
 Capabilities: pswitch pswitch-joined penum
 Playback channels: Mono
 Mono: Playback [on]
  Card1.Amixer.info:
   Card hw:1 'Generic_1'/'HD-Audio Generic at 0xa034 irq 16'
 Mixer name : 'Realtek ALC269VB'
 Components : 'HDA:10ec0269,102804c3,00100100'
 Controls  : 18
 Simple ctrls  : 10
  Date: Tue Feb 19 01:50:56 2013
  HibernationDevice: RESUME=UUID=7cf2dba5-3ce7-4345-8773-ac7bd6078a79
  InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 
(20120823.1)
  IwConfig:
   lono wireless extensions.
   
   eth0  no wireless extensions.
  MachineType: Dell Inc. Dell System Inspiron M4110
  MarkForUpload: True
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB:
   0 radeondrmfb
   1 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-38-generic 
root=UUID=b677d5d5-25d4-4eae-b0c2-84a4e8c5dd92 ro quiet splash initcall_debug 
vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.2.0-38-generic N/A
   linux-backports-modules-3.2.0-38-generic  N/A
   linux-firmware1.79.1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/22/2011
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: X19
  dmi.board.asset.tag: Base Board Asset Tag Unknown
  dmi.board.name: Q4E3A3
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A11
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnDellInc.:bvrX19:bd07/22/2011:svnDellInc.:pnDellSystemInspironM4110:pvr:rvnDellInc.:rnQ4E3A3:rvrA11:cvnDellInc.:ct8:cvr0.1:
  dmi.product.name: Dell System Inspiron M4110
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1129865/+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 1065400] Re: Support for loading Broadcom bluetooth firmware

2015-11-03 Thread Vincent Gerris
patch for 105b:e065 : 
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1129865/comments/17 seems 
to be still absent.
Fix for it is in the link.
I asked Jesse what happened direction upstream.
Let's hope it gets in there

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

Title:
  Support for loading Broadcom bluetooth firmware

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Precise:
  Fix Released
Status in linux source package in Quantal:
  Fix Released
Status in linux source package in Raring:
  Fix Released
Status in linux source package in Saucy:
  Fix Released

Bug description:
  Broadcom bluetooth chips require a tool called patchram uploader [1]
  to load firmware. This applies to at least BCM20702 and BCM43142.
  Although some of the devices have an OTPROM that contains required
  firmware, but it is found that these devices would not have HFP/HSP
  support unless a upgraded firmware is loaded via patchram uploader.

  This tool requires hci device to do the firmware loading, but this may
  cause some race condition between patchram tool and bluetoothd or
  something that also works on hci interface.

  Also it needs some hooks to make firmware loads after bootup, s3,  s4,
  rfkill, and device hotplug events. Implement this loader in kernel
  module would make things more easier.

  [1] http://marc.info/?l=linux-bluetooth=132039175324993=2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1065400/+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 1242321] Re: USB 3.0 Harddrive not recognised

2015-11-03 Thread solarw
I have same problem on 15.10
Suppose this happens after suspend mode. usb3 hdd does not recognized by 
ubuntu. no messages in dmesg

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

Title:
  USB 3.0 Harddrive not recognised

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu is not recognising any device plugged into any USB 3.0 ports.
  Sometimes Ubuntu will freeze for a few seconds when you plug something
  into a USB 3.0 port; when Ubuntu comes out of the freeze, the device
  is still NOT recognised.

  No problems with USB 2.0 ports and devices.

  The USB 3.0 on this computer only works in Windows 7 (I'm dual booting
  Ubuntu 13.10 and Windows 7, both are 64-bit).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1242321/+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 1483325] Re: mount -t overlayfs misinforms when nonexisting directories are provided

2015-11-03 Thread Andy Whitcroft
** Changed in: linux (Ubuntu)
Milestone: ubuntu-15.10 => ubuntu-15.11

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

Title:
  mount -t overlayfs misinforms when nonexisting directories are
  provided

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Consider the directory structure like this:

  root@MIKE /tmp/ofs> ls -al
  total 20
  drwxr-xr-x 5 root root 4096 Aug 10 18:09 .
  drwxrwxrwt 9 root root 4096 Aug 10 18:09 ..
  drwxr-xr-x 2 root root 4096 Aug 10 18:09 lower
  drwxr-xr-x 2 root root 4096 Aug 10 18:09 mounting
  drwxr-xr-x 2 root root 4096 Aug 10 18:09 upper

  Mounting upper over lower on mounting mount point works just fine:

  root@MIKE /tmp/ofs> mount -t overlayfs myoverlay -o 
lowerdir=lower,upperdir=upper mounting/
  root@MIKE /tmp/ofs> df -Th mounting/
  Filesystem Type   Size  Used Avail Use% Mounted on
  myoverlay  overlayfs  219G   94G  114G  46% /tmp/ofs/mounting
  root@MIKE /tmp/ofs> 

  However if the directory name is misspelled (that is, we're providing
  wrong directory), the error message is misleading:

  32 root@MIKE /tmp/ofs> mount -t overlayfs myoverlay -o 
lowerdir=IAMWRONG,upperdir=upper mounting/
  mount: special device myoverlay does not exist

  
  I'm running this on Ubuntu 14.04.3 LTS, using 3.13.0-61-generic kernel.

  I'm not sure if this fits under 'linux' package, but I can't seem to be able 
to find 'mount' package in Launchpad.
  --- 
  ApportVersion: 2.14.1-0ubuntu3.11
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  mario  2458 F pulseaudio
   /dev/snd/controlC0:  mario  2458 F pulseaudio
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=fa8de8e9-450d-4a2e-8ca6-fa542a0352e3
  InstallationDate: Installed on 2014-12-16 (236 days ago)
  InstallationMedia: Ubuntu MATE 14.04.1 "Trusty Tahr" - final amd64 (2014)
  MachineType: LENOVO 42405XG
  NonfreeKernelModules: nvidia
  Package: linux (not installed)
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-61-generic 
root=UUID=a3231802-c7ff-406a-9aca-83a4bb0c7d70 ro quiet splash
  ProcVersionSignature: Ubuntu 3.13.0-61.100-generic 3.13.11-ckt22
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-61-generic N/A
   linux-backports-modules-3.13.0-61-generic  N/A
   linux-firmware 1.127.14
  Tags:  trusty
  Uname: Linux 3.13.0-61-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip disk fuse libvirtd lpadmin plugdev sambashare 
sbuild sudo
  _MarkForUpload: True
  dmi.bios.date: 12/06/2011
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 8AET56WW (1.36 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 42405XG
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr8AET56WW(1.36):bd12/06/2011:svnLENOVO:pn42405XG:pvrThinkPadT520:rvnLENOVO:rn42405XG:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 42405XG
  dmi.product.version: ThinkPad T520
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1483325/+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 1492466] Re: linux-lts-trusty: not split but trusty linux is leading to upgrade issues

2015-11-03 Thread Andy Whitcroft
** Changed in: linux-lts-trusty (Ubuntu)
Milestone: ubuntu-15.10 => ubuntu-15.11

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

Title:
  linux-lts-trusty: not split but trusty linux is leading to upgrade
  issues

Status in linux-lts-trusty package in Ubuntu:
  Triaged
Status in linux-lts-trusty source package in Precise:
  Triaged

Bug description:
  This leads to upgrade failures:

Unpacking linux-image-extra-3.13.0-63-generic (3.13.0-63.103) ...
dpkg: error processing archive 
/var/cache/apt/archives/linux-image-extra-3.13.0-63-generic_3.13.0-63.103_amd64.deb
 (--unpack): trying to overwrite  
'/lib/modules/3.13.0-63-generic/kernel/mm/hwpoison-inject.ko', which is also in 
package linux-image-3.13.0-63-generic 3.13.0-63.104~precise1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-lts-trusty/+bug/1492466/+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 1436945] Re: devel: consider fq_codel as the default qdisc for networking

2015-11-03 Thread Andy Whitcroft
** Changed in: linux (Ubuntu)
Milestone: ubuntu-15.10 => ubuntu-15.11

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

Title:
  devel: consider fq_codel as the default qdisc for networking

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  This was raised on the kernel-team@ mailing list, we should look at
  this if other distros are starting to move.

  ===

  Date: Tue, 24 Mar 2015 10:54:37 -0700 
 
  From: Dave Taht  
 
  To: Joseph Salisbury  
 
  Cc: Kernel Team , ubuntu-de...@lists.ubuntu.com 
 
  Subject: Re: Minutes from the Ubuntu Kernel Team meeting, 2015-03-24  
 

 
  I must confess I had hoped ubuntu would adopt fq_codel as the default 
 
  qdisc in this go-around. It is still not quite part of fedora´s   
 
  default either, but is now in arch, (and nearly everyone else 
 
  downstream from systemd), and has long been the default in openwrt,   
 
  and at this point, just requires a single sysctl to enable.   
 

 
  It certainly could use more widespread testing, perhaps in the next release?  
 

 
  d@nuc-client:~$ cat /etc/sysctl.d/10-bufferbloat.conf 
 
  net.core.default_qdisc=fq_codel

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1436945/+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 1480411] Re: rm -r * fails to delete directories when using overlayfs in a user-namespace

2015-11-03 Thread Andy Whitcroft
** Changed in: linux (Ubuntu)
Milestone: ubuntu-15.10 => ubuntu-15.11

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

Title:
  rm -r * fails to delete directories when using overlayfs in a user-
  namespace

Status in linux package in Ubuntu:
  Confirmed
Status in lxc package in Ubuntu:
  Confirmed

Bug description:
  rm -r * fails to delete directories when using overlayfs in a user-
  namespace.

  If overlayfs is mounted as follows,

     mount -n -t overlay overlay -o
  lowerdir=lowerdir,upperdir=upperdir,workdir=workdir mntpt

  and if lowerdir contains lowerdir/foo/bar.txt, then,

     rm -r mntpt/foo

  fails with error message,

     "rm: cannot remove ‘mntpt/foo’: Operation not permitted"

  strace shows,

  unlinkat(AT_FDCWD, "mntpt/foo", AT_REMOVEDIR) = -1 EPERM
  (Operation not permitted)

  OS details: 64-bit ubuntu 14.04.2 with the linux-generic-lts-vivid
  kernel (3.19).

  The bug does not occur on ubuntu 14.04.2 with the default linux-
  generic 3.13 kernel.

  The bug occurs for any vanilla 3.18+ kernel to which the 1-line patch,
  "overlayfs: allow unprivileged mounts" is added.  (The patch is at,
  http://kernel.ubuntu.com/git/ubuntu/ubuntu-
  vivid.git/commit/?id=78ec45495b15d27d4cc6d05cc454e30ec5b587ea)

  The bug occurs regardless of whether the filesystem underlying
  overlayfs is tmpfs or ext4.

  The bug also occurs when running ubuntu 15.04 (ubuntu vivid) in a
  virtual machine (qemu-system-x86_64).  The host is ubuntu 14.04.2 with
  the default 3.13 kernel.

  A script which reproduces the bug is attached and is also available at
  http://paste.ubuntu.com/11974137/

  Hardware: intel core2 duo processor in a macbook-4.1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1480411/+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 1490267] Re: Regression in overlayfs

2015-11-03 Thread Andy Whitcroft
** Changed in: linux (Ubuntu)
Milestone: ubuntu-15.10 => ubuntu-15.11

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

Title:
  Regression in overlayfs

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  When installing the linux-lts-vivid kernel in Ubuntu 14.04, there is a
  regression with overlayfs and unprivileged containers: 'failed to
  whiteout'

  Below the system information:

  - Kernel error: http://pastebin.com/iajXHbHZ
  - Kernel version: 3.19.0-25-generic #26~14.04.1-Ubuntu SMP Fri Jul 24 
21:16:20 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux
  - Executed LXC command: lxc-clone -s -B overlayfs orig test (both 
unprivileged containers)
  - LXC version: 1.0.7

  We discussed this on the LXC user mailing list, and this is likely a bug in 
one of the patches that add support for unprivileged use of overlayfs.
  --- 
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Aug 30 13:56 seq
   crw-rw 1 root audio 116, 33 Aug 30 13:56 timer
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.14.1-0ubuntu3.12
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 14.04
  Ec2AMI: ami-fceee9e1
  Ec2AMIManifest: (unknown)
  Ec2AvailabilityZone: eu-central-1b
  Ec2InstanceType: t2.micro
  Ec2Kernel: unavailable
  Ec2Ramdisk: unavailable
  IwConfig: Error: [Errno 2] No such file or directory
  Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize 
libusb: -99
  MachineType: Xen HVM domU
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB:
   0 cirrusdrmfb
   1 xen
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-26-generic 
root=UUID=dde0e30e-be54-43dc-9a44-5769353c2e27 ro console=tty1 console=ttyS0
  ProcVersionSignature: Ubuntu 3.19.0-26.28~14.04.1-generic 3.19.8-ckt4
  RelatedPackageVersions:
   linux-restricted-modules-3.19.0-26-generic N/A
   linux-backports-modules-3.19.0-26-generic  N/A
   linux-firmware 1.127.15
  RfKill: Error: [Errno 2] No such file or directory
  StagingDrivers: visorutil
  Tags:  trusty ec2-images staging
  Uname: Linux 3.19.0-26-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 05/06/2015
  dmi.bios.vendor: Xen
  dmi.bios.version: 4.2.amazon
  dmi.chassis.type: 1
  dmi.chassis.vendor: Xen
  dmi.modalias: 
dmi:bvnXen:bvr4.2.amazon:bd05/06/2015:svnXen:pnHVMdomU:pvr4.2.amazon:cvnXen:ct1:cvr:
  dmi.product.name: HVM domU
  dmi.product.version: 4.2.amazon
  dmi.sys.vendor: Xen

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1490267/+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 1493839] Re: overlayfs: disabling V1 support leads to compile failure

2015-11-03 Thread Andy Whitcroft
** Changed in: linux (Ubuntu)
Milestone: ubuntu-15.10 => ubuntu-15.11

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

Title:
  overlayfs: disabling  V1 support leads to compile failure

Status in linux package in Ubuntu:
  Triaged

Bug description:
  "CONFIG_OVERLAY_FS_V1 is not set":

  fs/overlayfs/super.c: In function 'ovl_init': 

  fs/overlayfs/super.c:1213:30: error: 'ovl_v1_fs_type' undeclared (first 
use in this function) 
  fs/overlayfs/super.c:1213:30: note: each undeclared identifier is 
reported only once for each function it appears in  
  fs/overlayfs/super.c: In function 'ovl_exit': 

  fs/overlayfs/super.c:1226:26: error: 'ovl_v1_fs_type' undeclared (first 
use in this function) 
  scripts/Makefile.build:258: recipe for target 'fs/overlayfs/super.o' 
failed

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1493839/+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 1413664] Re: 15.04: consider enabling CONFIG_DEBUG_INFO_SPLIT and package the .dwo files

2015-11-03 Thread Andy Whitcroft
** Changed in: linux (Ubuntu)
Milestone: ubuntu-15.10 => ubuntu-15.11

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

Title:
  15.04: consider enabling CONFIG_DEBUG_INFO_SPLIT and package the .dwo
  files

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  There is a new more efficient debug format enabled via
  CONFIG_DEBUG_INFO_SPLIT, this spits out new .dwo files which need
  packaging in the .ddeb before we can enable this.  Evaluate whether
  the other tooling we have will handle it before doing so.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1413664/+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 1478609] Re: overlayfs: port v1 support to v4.2

2015-11-03 Thread Andy Whitcroft
** Changed in: linux (Ubuntu)
Milestone: ubuntu-15.10 => ubuntu-15.11

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

Title:
  overlayfs: port v1 support to v4.2

Status in linux package in Ubuntu:
  Fix Committed

Bug description:
  Need to port overlayfs v1 support to v4.2.

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

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


  1   2   >