Re: [Kernel-packages] [Bug 1403949] Re: package linux-image-3.16.0-28-generic 3.16.0-28.38 failed to install/upgrade: subprocess installed post-installation script returned error exit status 17

[Ankush]

Thanks for responding me.
I appreciate it.
I have reinstalled the ubuntu 14.10 LTS with GNOME.
It is working fine now.

On Fri, Dec 19, 2014 at 8:50 PM, Jamie Strandboge 
wrote:

> ** Information type changed from Private Security to Public
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1403949
>
> Title:
>   package linux-image-3.16.0-28-generic 3.16.0-28.38 failed to
>   install/upgrade: subprocess installed post-installation script
>   returned error exit status 17
>
> Status in linux package in Ubuntu:
>   New
>
> Bug description:
>   I am using Linux Ubuntu 10.14.
>
>   ProblemType: Package
>   DistroRelease: Ubuntu 14.10
>   Package: linux-image-3.16.0-28-generic 3.16.0-28.38
>   ProcVersionSignature: Ubuntu 3.16.0-23.31-generic 3.16.4
>   Uname: Linux 3.16.0-23-generic x86_64
>   ApportVersion: 2.14.7-0ubuntu8
>   Architecture: amd64
>   AudioDevicesInUse:
>USERPID ACCESS COMMAND
>/dev/snd/controlC1:  ankush 2268 F pulseaudio
>/dev/snd/controlC0:  ankush 2268 F pulseaudio
>   Date: Thu Dec 18 21:50:53 2014
>   DuplicateSignature:
> package:linux-image-3.16.0-28-generic:3.16.0-28.38:subprocess installed
> post-installation script returned error exit status 17
>   ErrorMessage: subprocess installed post-installation script returned
> error exit status 17
>   HibernationDevice: RESUME=UUID=81f05cb3-6468-4118-9d35-dc75feebef42
>   InstallationDate: Installed on 2014-12-15 (3 days ago)
>   InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64
> (20141022.1)
>   MachineType: TOSHIBA Satellite C50-A
>   ProcFB: 0 inteldrmfb
>   ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.16.0-23-generic
> root=UUID=fb3ee1a1-ac86-49f2-8fb3-78eda9541821 ro quiet splash vt.handoff=7
>   PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No
> PulseAudio daemon running, or not running as session daemon.
>   RelatedPackageVersions: grub-pc 2.02~beta2-15
>   SourcePackage: linux
>   StagingDrivers: keucr
>   Title: package linux-image-3.16.0-28-generic 3.16.0-28.38 failed to
> install/upgrade: subprocess installed post-installation script returned
> error exit status 17
>   UpgradeStatus: No upgrade log present (probably fresh install)
>   dmi.bios.date: 10/14/2013
>   dmi.bios.vendor: TOSHIBA
>   dmi.bios.version: 1.00
>   dmi.board.asset.tag: ATN12345678901234567
>   dmi.board.name: PT10S
>   dmi.board.vendor: TOSHIBA
>   dmi.board.version: To be filled by O.E.M.
>   dmi.chassis.asset.tag: No Asset Tag
>   dmi.chassis.type: 10
>   dmi.chassis.vendor: TOSHIBA
>   dmi.chassis.version: To Be Filled By O.E.M.
>   dmi.modalias:
> dmi:bvnTOSHIBA:bvr1.00:bd10/14/2013:svnTOSHIBA:pnSatelliteC50-A:pvrPSCGLG-00D00G:rvnTOSHIBA:rnPT10S:rvrTobefilledbyO.E.M.:cvnTOSHIBA:ct10:cvrToBeFilledByO.E.M.:
>   dmi.product.name: Satellite C50-A
>   dmi.product.version: PSCGLG-00D00G
>   dmi.sys.vendor: TOSHIBA
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1403949/+subscriptions
>

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

Title:
  package linux-image-3.16.0-28-generic 3.16.0-28.38 failed to
  install/upgrade: subprocess installed post-installation script
  returned error exit status 17

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I am using Linux Ubuntu 10.14.

  ProblemType: Package
  DistroRelease: Ubuntu 14.10
  Package: linux-image-3.16.0-28-generic 3.16.0-28.38
  ProcVersionSignature: Ubuntu 3.16.0-23.31-generic 3.16.4
  Uname: Linux 3.16.0-23-generic x86_64
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  ankush 2268 F pulseaudio
   /dev/snd/controlC0:  ankush 2268 F pulseaudio
  Date: Thu Dec 18 21:50:53 2014
  DuplicateSignature: 
package:linux-image-3.16.0-28-generic:3.16.0-28.38:subprocess installed 
post-installation script returned error exit status 17
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 17
  HibernationDevice: RESUME=UUID=81f05cb3-6468-4118-9d35-dc75feebef42
  InstallationDate: Installed on 2014-12-15 (3 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
  MachineType: TOSHIBA Satellite C50-A
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.16.0-23-generic 
root=UUID=fb3ee1a1-ac86-49f2-8fb3-78eda9541821 ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: grub-pc 2.02~beta2-15
  SourcePackage: linux
  StagingDrivers: keucr
  Title: package linux-image-3.16.0-28-generic 3.16.0-28.38 failed to 
install/upgrade: subprocess installed post-installation script ret

[Kernel-packages] [Bug 451282] Re: display is fully dimmed after resume from suspend

[Rochvellon]

It seems it works with Kubuntu 14.04 and Kernel 3.16 (Utopic) on a TP
X200.

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

Title:
  display is fully dimmed after resume from suspend

Status in linux package in Ubuntu:
  Won't Fix

Bug description:
  Binary package hint: gnome-power-manager

  When I resume from suspend (while on AC power), the laptop display
  brightness is set to it's lowest level, even when I had the brightness
  turned all the way up before. Interestingly enough, this only seems to
  happen on the first suspend after a reboot. Once I have turned up the
  display brightness again using the function keys, the next
  suspend/resume cycle will work normally (until the next reboot).
  Finally, when I use the function keys to increase the brightness after
  a suspend, I see that the brightness level in the notification bar
  indicates that the brightness is set to the maximum. Only after
  repeated adjustments with the function keys, the indicator 'resets'
  and reflects the true display brightness level. I'm using the
  proprietary nvidia display driver, but I've never had this problem
  before in Jaunty. Also, in case it makes a difference, I've set my
  laptop to suspend on lid closure since that's the way I generally
  suspend the laptop.

  ProblemType: Bug
  Architecture: amd64
  CheckboxSubmission: 464ed6184a4fbf79d6e3084c58b13de8
  CheckboxSystem: d00f84de8a555815fa1c4660280da308
  Date: Wed Oct 14 09:46:16 2009
  DistroRelease: Ubuntu 9.10
  NonfreeKernelModules: nvidia
  Package: gnome-power-manager 2.28.0-0ubuntu6
  ProcEnviron:
   PATH=(custom, user)
   LANG=en_CA.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 2.6.31-14.46-generic
  SourcePackage: gnome-power-manager
  Uname: Linux 2.6.31-14-generic x86_64

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/451282/+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 1401748] Re: Screen freezes when I close the lid

[Christopher M. Penalver]

Aline Freitas, this bug report is being closed due to your last comment
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1401748/comments/7
regarding this being fixed with a BIOS update. For future reference you
can manage the status of your own bugs by clicking on the current status
in the yellow line and then choosing a new status in the revealed drop
down box. You can learn more about bug statuses at
https://wiki.ubuntu.com/Bugs/Status. Thank you again for taking the time
to report this bug and helping to make Ubuntu better. Please submit any
future bugs you may find.

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

Title:
  Screen freezes when I close the lid

Status in linux package in Ubuntu:
  Invalid

Bug description:
  The same description from  #1385926 applies here. However, my system
  is Ubuntu with Unity, with a default install.

  Also, the suggested workaround (choose "suspend" from menu) works too.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: linux-image-3.16.0-26-generic 3.16.0-26.35
  ProcVersionSignature: Ubuntu 3.16.0-26.35-generic 3.16.7-ckt1
  Uname: Linux 3.16.0-26-generic x86_64
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  aline  3946 F pulseaudio
   /dev/snd/controlC1:  aline  3946 F pulseaudio
  CurrentDesktop: Unity
  Date: Fri Dec 12 01:50:19 2014
  HibernationDevice: RESUME=UUID=79e6a4c6-8955-4d56-b942-90b1ba6cd5e3
  InstallationDate: Installed on 2014-08-31 (102 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  MachineType: Hewlett-Packard HP Pavilion 14 Notebook PC
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.16.0-26-generic.efi.signed 
root=/dev/mapper/vg-root ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.16.0-26-generic N/A
   linux-backports-modules-3.16.0-26-generic  N/A
   linux-firmware 1.138
  SourcePackage: linux
  UpgradeStatus: Upgraded to utopic on 2014-11-30 (11 days ago)
  dmi.bios.date: 09/26/2013
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.23
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 2162
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 29.24
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.23:bd09/26/2013:svnHewlett-Packard:pnHPPavilion14NotebookPC:pvr088110305E1610100:rvnHewlett-Packard:rn2162:rvr29.24:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.name: HP Pavilion 14 Notebook PC
  dmi.product.version: 088110305E1610100
  dmi.sys.vendor: Hewlett-Packard

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1401748/+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 1301245] Re: System unresponsive under (IO/memory?) load

[Launchpad Bug Tracker]

[Expired for linux (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  System unresponsive under (IO/memory?) load

Status in linux package in Ubuntu:
  Expired

Bug description:
  Tasks producing a lot of IO activity and/or use large amount of memory
  (uncompressing a .tar.gz file, starting a VM in virtualbox) starve the
  rest of the system. The system is responding to user input very slowly
  (jerky mouse pointer movement with >1s intervals etc). I have not seen
  that issue on previous Ubuntu versions, this is the first time I use a
  64 bit system with full disk encryption.

  64bit Xubuntu 13.10. Full disk encryption. 4GB memory. Sony Vaio
  laptop. Same behavior observed with Nouveau and NVidia drivers.

  $ uname -a
  Linux laptop 3.11.0-18-generic #32-Ubuntu SMP Tue Feb 18 21:11:14 UTC 2014 
x86_64 x86_64 x86_64 GNU/Linux

  $ free -m
   total   used   free sharedbuffers cached
  Mem:  3870   2580   1289  0 33406
  -/+ buffers/cache:   2140   1730
  Swap: 4011959   3052

  $ lspci
  00:00.0 Host bridge: Intel Corporation Core Processor DRAM Controller (rev 02)
  00:01.0 PCI bridge: Intel Corporation Core Processor PCI Express x16 Root 
Port (rev 02)
  00:1a.0 USB controller: Intel Corporation 5 Series/3400 Series Chipset USB2 
Enhanced Host Controller (rev 05)
  00:1b.0 Audio device: Intel Corporation 5 Series/3400 Series Chipset High 
Definition Audio (rev 05)
  00:1c.0 PCI bridge: Intel Corporation 5 Series/3400 Series Chipset PCI 
Express Root Port 1 (rev 05)
  00:1c.1 PCI bridge: Intel Corporation 5 Series/3400 Series Chipset PCI 
Express Root Port 2 (rev 05)
  00:1c.2 PCI bridge: Intel Corporation 5 Series/3400 Series Chipset PCI 
Express Root Port 3 (rev 05)
  00:1c.3 PCI bridge: Intel Corporation 5 Series/3400 Series Chipset PCI 
Express Root Port 4 (rev 05)
  00:1c.5 PCI bridge: Intel Corporation 5 Series/3400 Series Chipset PCI 
Express Root Port 6 (rev 05)
  00:1c.6 PCI bridge: Intel Corporation 5 Series/3400 Series Chipset PCI 
Express Root Port 7 (rev 05)
  00:1d.0 USB controller: Intel Corporation 5 Series/3400 Series Chipset USB2 
Enhanced Host Controller (rev 05)
  00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev a5)
  00:1f.0 ISA bridge: Intel Corporation Mobile 5 Series Chipset LPC Interface 
Controller (rev 05)
  00:1f.2 SATA controller: Intel Corporation 5 Series/3400 Series Chipset 6 
port SATA AHCI Controller (rev 05)
  00:1f.3 SMBus: Intel Corporation 5 Series/3400 Series Chipset SMBus 
Controller (rev 05)
  00:1f.6 Signal processing controller: Intel Corporation 5 Series/3400 Series 
Chipset Thermal Subsystem (rev 05)
  01:00.0 VGA compatible controller: NVIDIA Corporation GT218M [GeForce 310M] 
(rev a2)
  01:00.1 Audio device: NVIDIA Corporation High Definition Audio Controller 
(rev a1)
  02:00.0 Network controller: Qualcomm Atheros AR9287 Wireless Network Adapter 
(PCI-Express) (rev 01)
  03:00.0 SD Host controller: Ricoh Co Ltd MMC/SD Host Controller
  03:00.1 System peripheral: Ricoh Co Ltd R5U2xx (R5U230 / R5U231 / R5U241) 
[Memory Stick Host Controller]
  03:00.3 FireWire (IEEE 1394): Ricoh Co Ltd R5C832 PCIe IEEE 1394 Controller
  03:00.4 SD Host controller: Ricoh Co Ltd MMC/SD Host Controller
  04:00.0 Ethernet controller: Marvell Technology Group Ltd. 88E8057 PCI-E 
Gigabit Ethernet Controller (rev 10)
  05:00.0 Multimedia controller: Fujitsu Limited. Device 2036
  06:00.0 USB controller: NEC Corporation uPD720200 USB 3.0 Host Controller 
(rev 03)
  3f:00.0 Host bridge: Intel Corporation Core Processor QuickPath Architecture 
Generic Non-core Registers (rev 02)
  3f:00.1 Host bridge: Intel Corporation Core Processor QuickPath Architecture 
System Address Decoder (rev 02)
  3f:02.0 Host bridge: Intel Corporation Core Processor QPI Link 0 (rev 02)
  3f:02.1 Host bridge: Intel Corporation Core Processor QPI Physical 0 (rev 02)
  3f:02.2 Host bridge: Intel Corporation Core Processor Reserved (rev 02)
  3f:02.3 Host bridge: Intel Corporation Core Processor Reserved (rev 02)

  $ lsmod 
  Module  Size  Used by
  pci_stub   12622  1 
  vboxpci23194  0 
  vboxnetadp 25670  0 
  vboxnetflt 27613  0 
  vboxdrv   320455  3 vboxnetadp,vboxnetflt,vboxpci
  bnep   19704  2 
  rfcomm 69130  16 
  parport_pc 32701  0 
  ppdev  17671  0 
  snd_hda_codec_hdmi 41154  4 
  snd_hda_codec_realtek56475  1 
  snd_hda_intel  52267  5 
  snd_hda_codec 188738  3 
snd_hda_codec_realtek,snd_hda_codec_hdmi,snd_hda_intel
  uvcvideo   80885  1 
  intel_powerclamp

[Kernel-packages] [Bug 1401748] Re: Screen freezes when I close the lid

[Aline Freitas]

As HP only releases their BIOS firmware update for my model in 64bits
Windows-only exe, and after many attempts to do it without installing
windows (WinPE live, for example) has failed I ended formatting
everything, installing windows 8, updating the BIOS and then restoring
Ubuntu.

My system is working now, fortunatelly without screen freezing.

Thank you, for your help Christopher!

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

Title:
  Screen freezes when I close the lid

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  The same description from  #1385926 applies here. However, my system
  is Ubuntu with Unity, with a default install.

  Also, the suggested workaround (choose "suspend" from menu) works too.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: linux-image-3.16.0-26-generic 3.16.0-26.35
  ProcVersionSignature: Ubuntu 3.16.0-26.35-generic 3.16.7-ckt1
  Uname: Linux 3.16.0-26-generic x86_64
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  aline  3946 F pulseaudio
   /dev/snd/controlC1:  aline  3946 F pulseaudio
  CurrentDesktop: Unity
  Date: Fri Dec 12 01:50:19 2014
  HibernationDevice: RESUME=UUID=79e6a4c6-8955-4d56-b942-90b1ba6cd5e3
  InstallationDate: Installed on 2014-08-31 (102 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  MachineType: Hewlett-Packard HP Pavilion 14 Notebook PC
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.16.0-26-generic.efi.signed 
root=/dev/mapper/vg-root ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.16.0-26-generic N/A
   linux-backports-modules-3.16.0-26-generic  N/A
   linux-firmware 1.138
  SourcePackage: linux
  UpgradeStatus: Upgraded to utopic on 2014-11-30 (11 days ago)
  dmi.bios.date: 09/26/2013
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.23
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 2162
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 29.24
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.23:bd09/26/2013:svnHewlett-Packard:pnHPPavilion14NotebookPC:pvr088110305E1610100:rvnHewlett-Packard:rn2162:rvr29.24:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.name: HP Pavilion 14 Notebook PC
  dmi.product.version: 088110305E1610100
  dmi.sys.vendor: Hewlett-Packard

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1401748/+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 204133] Re: wubi install unusable - Buffer I/O error on device loop0

[Raymond Michael Attila Erdey]

I have the same problem in 14.04 and do not know how to rsolve 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/204133

Title:
  wubi install unusable - Buffer I/O error on device loop0

Status in Wubi, Windows Ubuntu Installer:
  Fix Released
Status in Wubi 8.04 series:
  In Progress
Status in linux package in Ubuntu:
  Invalid
Status in lupin package in Ubuntu:
  Fix Released
Status in ntfs-3g package in Ubuntu:
  Fix Released
Status in linux source package in Hardy:
  Invalid
Status in lupin source package in Hardy:
  Won't Fix
Status in ntfs-3g source package in Hardy:
  Fix Released
Status in linux source package in Intrepid:
  Invalid
Status in lupin source package in Intrepid:
  Fix Released
Status in ntfs-3g source package in Intrepid:
  Fix Released

Bug description:
  LATEST ISO TESTED:
  Ubuntu amd64 20080411 w/
  wubi rev 482

  ISO TESTED:
  Ubuntu amd64 20080319

  
  After what seemed to be a successful install via wubi I am unable to login to 
the system.
  I booted into rescue mode and found in dmesg the following:

  Buffer I/O error on device loop0, logical block 872512
  lost page write due to I/O error, on loop0
  ...
  EXT3-fs error (device loop0): ext3_get_inode_loc: unable to read inode block 
- inode=114030, block=229669
  Aborting journal on device loop0.
  __journal_remove_journal_head: freeing b_committed_data
  (repeat 6x)
  Remounting filesystem read-only

To manage notifications about this bug go to:
https://bugs.launchpad.net/wubi/+bug/204133/+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 1404428] Status changed to Confirmed

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

Title:
  System does not resume after suspend

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  In linux-image-3.13.0-41 and -43, my system goes to sleep when the lid
  is closed, but does not resume when the lid is opened.  It's probably
  hardware specific (MacBook Pro running Trusty/14.04), but I saw that
  my hardware data was sent with this report.

  I noticed the problem in 3.13.0-43 and installed linux-images backward
  until I found one that does not suffer from this problem.
  Suspend/resume works in 3.13.0-40 and previous versions and does not
  work in 3.13.0-41 and later versions, reproducibly (I rebooted with
  different kernel versions several times to be sure).  Something was
  introduced in this version that breaks suspend/resume.

  For now, I'm using 3.13.0-40, but I'm hoping this gets resolved so
  that I can keep up to date with kernel versions again.  (Thanks!)

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-41-generic 3.13.0-41.70
  ProcVersionSignature: Ubuntu 3.13.0-40.69-generic 3.13.11.10
  Uname: Linux 3.13.0-40-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.14.1-0ubuntu3.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  pivarski   2310 F pulseaudio
   /dev/snd/controlC0:  pivarski   2310 F pulseaudio
  Date: Fri Dec 19 19:43:31 2014
  HibernationDevice: RESUME=UUID=c3b7c7b4-008d-4753-b205-63ab65db36e7
  InstallationDate: Installed on 2014-09-27 (83 days ago)
  InstallationMedia: Xubuntu 14.04 LTS "Trusty Tahr" - Release amd64 
(20140416.2)
  MachineType: Apple Inc. MacBookPro6,2
  ProcFB:
   0 nouveaufb
   1 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-40-generic.efi.signed 
root=UUID=e4ed6837-c7cd-42bf-8e63-e213f9b4681c ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-40-generic N/A
   linux-backports-modules-3.13.0-40-generic  N/A
   linux-firmware 1.127.10
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/09/11
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: MBP61.88Z.0057.B0F.1112091028
  dmi.board.asset.tag: Base Board Asset Tag#
  dmi.board.name: Mac-F22586C8
  dmi.board.vendor: Apple Inc.
  dmi.board.version: MacBookPro6,2
  dmi.chassis.type: 10
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-F22586C8
  dmi.modalias: 
dmi:bvnAppleInc.:bvrMBP61.88Z.0057.B0F.1112091028:bd12/09/11:svnAppleInc.:pnMacBookPro6,2:pvr1.0:rvnAppleInc.:rnMac-F22586C8:rvrMacBookPro6,2:cvnAppleInc.:ct10:cvrMac-F22586C8:
  dmi.product.name: MacBookPro6,2
  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/1404428/+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 1404428] [NEW] System does not resume after suspend

[Jim Pivarski]

Public bug reported:

In linux-image-3.13.0-41 and -43, my system goes to sleep when the lid
is closed, but does not resume when the lid is opened.  It's probably
hardware specific (MacBook Pro running Trusty/14.04), but I saw that my
hardware data was sent with this report.

I noticed the problem in 3.13.0-43 and installed linux-images backward
until I found one that does not suffer from this problem.
Suspend/resume works in 3.13.0-40 and previous versions and does not
work in 3.13.0-41 and later versions, reproducibly (I rebooted with
different kernel versions several times to be sure).  Something was
introduced in this version that breaks suspend/resume.

For now, I'm using 3.13.0-40, but I'm hoping this gets resolved so that
I can keep up to date with kernel versions again.  (Thanks!)

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: linux-image-3.13.0-41-generic 3.13.0-41.70
ProcVersionSignature: Ubuntu 3.13.0-40.69-generic 3.13.11.10
Uname: Linux 3.13.0-40-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.14.1-0ubuntu3.6
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  pivarski   2310 F pulseaudio
 /dev/snd/controlC0:  pivarski   2310 F pulseaudio
Date: Fri Dec 19 19:43:31 2014
HibernationDevice: RESUME=UUID=c3b7c7b4-008d-4753-b205-63ab65db36e7
InstallationDate: Installed on 2014-09-27 (83 days ago)
InstallationMedia: Xubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2)
MachineType: Apple Inc. MacBookPro6,2
ProcFB:
 0 nouveaufb
 1 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-40-generic.efi.signed 
root=UUID=e4ed6837-c7cd-42bf-8e63-e213f9b4681c ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-3.13.0-40-generic N/A
 linux-backports-modules-3.13.0-40-generic  N/A
 linux-firmware 1.127.10
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/09/11
dmi.bios.vendor: Apple Inc.
dmi.bios.version: MBP61.88Z.0057.B0F.1112091028
dmi.board.asset.tag: Base Board Asset Tag#
dmi.board.name: Mac-F22586C8
dmi.board.vendor: Apple Inc.
dmi.board.version: MacBookPro6,2
dmi.chassis.type: 10
dmi.chassis.vendor: Apple Inc.
dmi.chassis.version: Mac-F22586C8
dmi.modalias: 
dmi:bvnAppleInc.:bvrMBP61.88Z.0057.B0F.1112091028:bd12/09/11:svnAppleInc.:pnMacBookPro6,2:pvr1.0:rvnAppleInc.:rnMac-F22586C8:rvrMacBookPro6,2:cvnAppleInc.:ct10:cvrMac-F22586C8:
dmi.product.name: MacBookPro6,2
dmi.product.version: 1.0
dmi.sys.vendor: Apple Inc.

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


** Tags: amd64 apport-bug trusty

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

Title:
  System does not resume after suspend

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  In linux-image-3.13.0-41 and -43, my system goes to sleep when the lid
  is closed, but does not resume when the lid is opened.  It's probably
  hardware specific (MacBook Pro running Trusty/14.04), but I saw that
  my hardware data was sent with this report.

  I noticed the problem in 3.13.0-43 and installed linux-images backward
  until I found one that does not suffer from this problem.
  Suspend/resume works in 3.13.0-40 and previous versions and does not
  work in 3.13.0-41 and later versions, reproducibly (I rebooted with
  different kernel versions several times to be sure).  Something was
  introduced in this version that breaks suspend/resume.

  For now, I'm using 3.13.0-40, but I'm hoping this gets resolved so
  that I can keep up to date with kernel versions again.  (Thanks!)

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-41-generic 3.13.0-41.70
  ProcVersionSignature: Ubuntu 3.13.0-40.69-generic 3.13.11.10
  Uname: Linux 3.13.0-40-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.14.1-0ubuntu3.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  pivarski   2310 F pulseaudio
   /dev/snd/controlC0:  pivarski   2310 F pulseaudio
  Date: Fri Dec 19 19:43:31 2014
  HibernationDevice: RESUME=UUID=c3b7c7b4-008d-4753-b205-63ab65db36e7
  InstallationDate: Installed on 2014-09-27 (83 days ago)
  InstallationMedia: Xubuntu 14.04 LTS "Trusty Tahr" - Release amd64 
(20140416.2)
  MachineType: Apple Inc. MacBookPro6,2
  ProcFB:
   0 nouveaufb
   1 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-40-generic.efi.signed 
root=UUID=e4ed6837-c7cd-42bf-8e63-e213f9b4681c ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-40-generic N/A
   linux-backports-modules-3.13.0-40-generic  N/A
   linux-firmware 1.127.10
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/09/11
  dmi.bios.vendor: Appl

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

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

Title:
  Kernel panic while cpying files through USB HHD

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have a new MSI CX61 2PC 2198XFR that I installed today with Ubuntu
  14.04 LTS that works fine with my old computer.

  Some info for the new one :
  Linux JPD-CX61-2PC 3.13.0-43-generic #72-Ubuntu SMP Mon Dec 8 19:35:06 UTC 
2014 x86_64 x86_64 x86_64 GNU/Linux

  When I plugged an external USB HDD or when I make a huge copy from one
  USB HDD to the internal SSD, I issued a kernel panic with a
  probability of 33%. Four kernel panics in less than an hour.

  Except that (!), the computer is working perfectly. So I think the
  issue is linked to the USB 3.0 transfer.

  Thank you for your help.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-43-generic 3.13.0-43.72
  ProcVersionSignature: Ubuntu 3.13.0-43.72-generic 3.13.11.11
  Uname: Linux 3.13.0-43-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.1-0ubuntu3.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jpd3073 F pulseaudio
   /dev/snd/controlC1:  jpd3073 F pulseaudio
  CurrentDesktop: Unity
  Date: Sat Dec 20 00:01:28 2014
  HibernationDevice: RESUME=UUID=d546a8f2-c074-4f4a-bae2-e2119ab9d8e7
  InstallationDate: Installed on 2014-12-19 (0 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  MachineType: Micro-Star International Co., Ltd. CX61 2PC
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-43-generic 
root=UUID=bf5d2969-4391-4c6a-826b-a536aaf46fb0 ro quiet splash
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-43-generic N/A
   linux-backports-modules-3.13.0-43-generic  N/A
   linux-firmware 1.127.10
  SourcePackage: linux
  StagingDrivers: zram
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/26/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: E16GDIMS.60P
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: MS-16GD
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: REV:1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: CX61 2PC
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrE16GDIMS.60P:bd08/26/2014:svnMicro-StarInternationalCo.,Ltd.:pnCX612PC:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-16GD:rvrREV1.0:cvnCX612PC:ct10:cvrN/A:
  dmi.product.name: CX61 2PC
  dmi.product.version: REV:1.0
  dmi.sys.vendor: Micro-Star International Co., Ltd.

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

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

Title:
  [regression] Intel 10Gb NIC Crashes

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I posted this to net...@vger.kernel.org as well:
  http://www.spinics.net/lists/netdev/msg309110.html

  I think the next step is to try to bisect this down to a specific commit. I'm 
starting to look at the instructions here:
  https://wiki.ubuntu.com/Kernel/KernelBisection

  -

  Previous history of this thread:
  http://thread.gmane.org/gmane.linux.network/326672

  On 2014-11-04 22:57:19, Tom Herbert wrote:
  > Using vlan and bonding? vlan_dev_hard_start_xmit called. A possible
  > cause is that bonding interface is out of sync with slave interface
  > w.r.t. GSO features. Do we know if this worked in 3.14, 3.15?

  I'm seeing the same sort of crash/warning (skb_war_bad_offload). It's
  happening on Intel 10 Gig NICs using the ixgbe driver. I'm using bridges
  (for virtual machines) on top of VLANs on top of 802.3ad bonding. I'm
  using an MTU of 9000 on the bond0 interface, but 1500 everywhere else.

  I'm always bonding two ports: one one system, I'm bonding two ports on
  identical one-port NICs; on another system, I'm bonding two ports on a
  single two-port NIC. Both systems exhibit the same behavior.

  Everything has worked fine for a couple years on Ubuntu 12.04 Precise
  (Linux 3.2.0). It immediately broke when I upgraded to Ubuntu 14.04
  Trusty (Linux 3.13.0). I can also reproduce this using the packaged
  version of Linux 3.16.0 on Trusty.

  In contrast to other reports of this bug, disabling scatter gather on
  the physical interfaces (e.g. eth0) does *not* stop the crashes
  (assuming I disabled it correctly).

  I currently have two systems (one with Precise, one with Trusty)
  available to do any testing that you'd find helpful.

  Here's a first pass at getting some debugging data.

  The broken system (Ubuntu 14.04 Trusty):

  rlaager@BROKEN:~$ uname -a
  Linux BROKEN 3.13.0-43-generic #72-Ubuntu SMP Mon Dec 8 19:35:06 UTC
  2014 x86_64 x86_64 x86_64 GNU/Linux

  rlaager@BROKEN:~$ ethtool -k p6p1
  Features for p6p1:
  rx-checksumming: on
  tx-checksumming: on
  tx-checksum-ipv4: on
  tx-checksum-ip-generic: off [fixed]
  tx-checksum-ipv6: on
  tx-checksum-fcoe-crc: on [fixed]
  tx-checksum-sctp: on
  scatter-gather: on
  tx-scatter-gather: on
  tx-scatter-gather-fraglist: off [fixed]
  tcp-segmentation-offload: on
  tx-tcp-segmentation: on
  tx-tcp-ecn-segmentation: off [fixed]
  tx-tcp6-segmentation: on
  udp-fragmentation-offload: off [fixed]
  generic-segmentation-offload: on
  generic-receive-offload: on
  large-receive-offload: off
  rx-vlan-offload: on
  tx-vlan-offload: on
  ntuple-filters: off
  receive-hashing: on
  highdma: on [fixed]
  rx-vlan-filter: on
  vlan-challenged: off [fixed]
  tx-lockless: off [fixed]
  netns-local: off [fixed]
  tx-gso-robust: off [fixed]
  tx-fcoe-segmentation: on [fixed]
  tx-gre-segmentation: off [fixed]
  tx-ipip-segmentation: off [fixed]
  tx-sit-segmentation: off [fixed]
  tx-udp_tnl-segmentation: off [fixed]
  tx-mpls-segmentation: off [fixed]
  fcoe-mtu: off [fixed]
  tx-nocache-copy: on
  loopback: off [fixed]
  rx-fcs: off [fixed]
  rx-all: off
  tx-vlan-stag-hw-insert: off [fixed]
  rx-vlan-stag-hw-parse: off [fixed]
  rx-vlan-stag-filter: off [fixed]
  l2-fwd-offload: off

  rlaager@BROKEN:~$ ethtool -k bond0
  Features for bond0:
  rx-checksumming: off [fixed]
  tx-checksumming: on
  tx-checksum-ipv4: off [fixed]
  tx-checksum-ip-generic: on
  tx-checksum-ipv6: off [fixed]
  tx-checksum-fcoe-crc: off [fixed]
  tx-checksum-sctp: off [fixed]
  scatter-gather: on
  tx-scatter-gather: on
  tx-scatter-gather-fraglist: off [requested on]
  tcp-segmentation-offload: on
  tx-tcp-segmentation: on
  tx-tcp-ecn-segmentation: on
  tx-tcp6-segmentation: on
  udp-fragmentation-offload: off [fixed]
  generic-segmentation-offload: on
  generic-receive-offload: on
  large-receive-offload: off
  rx-vlan-offload: on
  tx-vlan-offload: on
  ntuple-filters: off [fixed]
  receive-hashing: off [fixed]
  highdma: on
  rx-vlan-filter: on
  vlan-challenged: off [fixed]
  tx-lockless: on [fixed]
  netns-local: off [fixed]
  tx-gso-robust: off [fixed]
  tx-fcoe-segmentation: off [fixed]
  tx-gre-segmentation: off [fixed]
  tx-ipip-segmentation: off [fixed]
  tx-sit-segmentation: off [fixed]
  tx-udp_tnl-segmentation: on
  tx-mpls-segmentation: off [fixed]
  fcoe-mtu: off [fixed]
  tx-nocache-copy: off [requested on]
  loopback: off [fixed]
  rx-fcs: off [fixed]
  rx-all: off [fixed]
  tx-vlan-stag-hw-insert: off [fixed]
  rx-vlan-s

[Kernel-packages] [Bug 1401943] Re: [Asus P8Z77-V DELUXE] Kernel upgrade to 3.16.0-28 causes boot hang on my system

[William]

Same on my Ubuntu 14.10  system right after upgrade to kernel version
3.16.0-28. The earlier version (3.16.0-25) boots just fine. Will be
reverting back to the early version for now.

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

Title:
  [Asus P8Z77-V DELUXE] Kernel upgrade to 3.16.0-28 causes boot hang on
  my system

Status in linux package in Ubuntu:
  Triaged

Bug description:
  Under Ubuntu 14.10, I installed the latest kernel 3.16.0-28 and after
  reboot my system won't boot - result is blank screen. No console from
  ctrl+alt+fX.

  Re-installed from 14.10 install media, choosing do-not-install-
  updates, and found that strangely this still resulted in 3.16.0-28
  being installed - and thus same boot hang.

  System boots fine with earlier kernel version (3.16.0-23).

  I tried the 'ubuntu-bug linux' console command to report a bug with
  the kernel - however, this gathers information about the running
  (working) kernel 3.16.0-23 rather than the broken 3.16.0-28.

  Will attach screenshot of output of text error during boot.
  --- 
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  soren  2355 F pulseaudio
   /dev/snd/controlC1:  soren  2355 F pulseaudio
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 14.10
  HibernationDevice: RESUME=UUID=0e328329-6f3c-4967-a46e-9f695c6dd970
  InstallationDate: Installed on 2014-12-12 (0 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
  IwConfig:
   eth0  no wireless extensions.
   
   eth1  no wireless extensions.
   
   lono wireless extensions.
  MachineType: System manufacturer System Product Name
  Package: linux (not installed)
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-23-generic 
root=UUID=3347210c-8dee-4b0b-a67c-fb900809ae6f ro quiet splash
  ProcVersionSignature: Ubuntu 3.16.0-23.31-generic 3.16.4
  RelatedPackageVersions:
   linux-restricted-modules-3.16.0-23-generic N/A
   linux-backports-modules-3.16.0-23-generic  N/A
   linux-firmware 1.138
  RfKill:
   
  Tags:  utopic
  Uname: Linux 3.16.0-23-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 02/24/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0801
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: P8Z77-V DELUXE
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0801:bd02/24/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8Z77-VDELUXE:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1401943/+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 1404407] [NEW] Kernel panic while cpying files through USB HHD

[DUVAL Jean-Pierre]

Public bug reported:

I have a new MSI CX61 2PC 2198XFR that I installed today with Ubuntu
14.04 LTS that works fine with my old computer.

Some info for the new one :
Linux JPD-CX61-2PC 3.13.0-43-generic #72-Ubuntu SMP Mon Dec 8 19:35:06 UTC 2014 
x86_64 x86_64 x86_64 GNU/Linux

When I plugged an external USB HDD or when I make a huge copy from one
USB HDD to the internal SSD, I issued a kernel panic with a probability
of 33%. Four kernel panics in less than an hour.

Except that (!), the computer is working perfectly. So I think the issue
is linked to the USB 3.0 transfer.

Thank you for your help.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: linux-image-3.13.0-43-generic 3.13.0-43.72
ProcVersionSignature: Ubuntu 3.13.0-43.72-generic 3.13.11.11
Uname: Linux 3.13.0-43-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.14.1-0ubuntu3.6
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  jpd3073 F pulseaudio
 /dev/snd/controlC1:  jpd3073 F pulseaudio
CurrentDesktop: Unity
Date: Sat Dec 20 00:01:28 2014
HibernationDevice: RESUME=UUID=d546a8f2-c074-4f4a-bae2-e2119ab9d8e7
InstallationDate: Installed on 2014-12-19 (0 days ago)
InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2)
MachineType: Micro-Star International Co., Ltd. CX61 2PC
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-43-generic 
root=UUID=bf5d2969-4391-4c6a-826b-a536aaf46fb0 ro quiet splash
RelatedPackageVersions:
 linux-restricted-modules-3.13.0-43-generic N/A
 linux-backports-modules-3.13.0-43-generic  N/A
 linux-firmware 1.127.10
SourcePackage: linux
StagingDrivers: zram
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/26/2014
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: E16GDIMS.60P
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: MS-16GD
dmi.board.vendor: Micro-Star International Co., Ltd.
dmi.board.version: REV:1.0
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: CX61 2PC
dmi.chassis.version: N/A
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrE16GDIMS.60P:bd08/26/2014:svnMicro-StarInternationalCo.,Ltd.:pnCX612PC:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-16GD:rvrREV1.0:cvnCX612PC:ct10:cvrN/A:
dmi.product.name: CX61 2PC
dmi.product.version: REV:1.0
dmi.sys.vendor: Micro-Star International Co., Ltd.

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


** Tags: amd64 apport-bug staging trusty

** Attachment added: "sudo lspci -vnvn > lspci-vnvn.log"
   
https://bugs.launchpad.net/bugs/1404407/+attachment/4284410/+files/lspci-vnvn.log

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

Title:
  Kernel panic while cpying files through USB HHD

Status in linux package in Ubuntu:
  New

Bug description:
  I have a new MSI CX61 2PC 2198XFR that I installed today with Ubuntu
  14.04 LTS that works fine with my old computer.

  Some info for the new one :
  Linux JPD-CX61-2PC 3.13.0-43-generic #72-Ubuntu SMP Mon Dec 8 19:35:06 UTC 
2014 x86_64 x86_64 x86_64 GNU/Linux

  When I plugged an external USB HDD or when I make a huge copy from one
  USB HDD to the internal SSD, I issued a kernel panic with a
  probability of 33%. Four kernel panics in less than an hour.

  Except that (!), the computer is working perfectly. So I think the
  issue is linked to the USB 3.0 transfer.

  Thank you for your help.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-43-generic 3.13.0-43.72
  ProcVersionSignature: Ubuntu 3.13.0-43.72-generic 3.13.11.11
  Uname: Linux 3.13.0-43-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.1-0ubuntu3.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jpd3073 F pulseaudio
   /dev/snd/controlC1:  jpd3073 F pulseaudio
  CurrentDesktop: Unity
  Date: Sat Dec 20 00:01:28 2014
  HibernationDevice: RESUME=UUID=d546a8f2-c074-4f4a-bae2-e2119ab9d8e7
  InstallationDate: Installed on 2014-12-19 (0 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  MachineType: Micro-Star International Co., Ltd. CX61 2PC
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-43-generic 
root=UUID=bf5d2969-4391-4c6a-826b-a536aaf46fb0 ro quiet splash
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-43-generic N/A
   linux-backports-modules-3.13.0-43-generic  N/A
   linux-firmware 1.127.10
  SourcePackage: linux
  StagingDrivers: zram
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/26/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: E16GDIMS.60P
  dmi.board.asset.tag: To be filled by O.E.M.
  

[Kernel-packages] [Bug 1404409] [NEW] [regression] Intel 10Gb NIC Crashes

[Richard Laager]

Public bug reported:

I posted this to net...@vger.kernel.org as well:
http://www.spinics.net/lists/netdev/msg309110.html

I think the next step is to try to bisect this down to a specific commit. I'm 
starting to look at the instructions here:
https://wiki.ubuntu.com/Kernel/KernelBisection

-

Previous history of this thread:
http://thread.gmane.org/gmane.linux.network/326672

On 2014-11-04 22:57:19, Tom Herbert wrote:
> Using vlan and bonding? vlan_dev_hard_start_xmit called. A possible
> cause is that bonding interface is out of sync with slave interface
> w.r.t. GSO features. Do we know if this worked in 3.14, 3.15?

I'm seeing the same sort of crash/warning (skb_war_bad_offload). It's
happening on Intel 10 Gig NICs using the ixgbe driver. I'm using bridges
(for virtual machines) on top of VLANs on top of 802.3ad bonding. I'm
using an MTU of 9000 on the bond0 interface, but 1500 everywhere else.

I'm always bonding two ports: one one system, I'm bonding two ports on
identical one-port NICs; on another system, I'm bonding two ports on a
single two-port NIC. Both systems exhibit the same behavior.

Everything has worked fine for a couple years on Ubuntu 12.04 Precise
(Linux 3.2.0). It immediately broke when I upgraded to Ubuntu 14.04
Trusty (Linux 3.13.0). I can also reproduce this using the packaged
version of Linux 3.16.0 on Trusty.

In contrast to other reports of this bug, disabling scatter gather on
the physical interfaces (e.g. eth0) does *not* stop the crashes
(assuming I disabled it correctly).

I currently have two systems (one with Precise, one with Trusty)
available to do any testing that you'd find helpful.

Here's a first pass at getting some debugging data.

The broken system (Ubuntu 14.04 Trusty):

rlaager@BROKEN:~$ uname -a
Linux BROKEN 3.13.0-43-generic #72-Ubuntu SMP Mon Dec 8 19:35:06 UTC
2014 x86_64 x86_64 x86_64 GNU/Linux

rlaager@BROKEN:~$ ethtool -k p6p1
Features for p6p1:
rx-checksumming: on
tx-checksumming: on
tx-checksum-ipv4: on
tx-checksum-ip-generic: off [fixed]
tx-checksum-ipv6: on
tx-checksum-fcoe-crc: on [fixed]
tx-checksum-sctp: on
scatter-gather: on
tx-scatter-gather: on
tx-scatter-gather-fraglist: off [fixed]
tcp-segmentation-offload: on
tx-tcp-segmentation: on
tx-tcp-ecn-segmentation: off [fixed]
tx-tcp6-segmentation: on
udp-fragmentation-offload: off [fixed]
generic-segmentation-offload: on
generic-receive-offload: on
large-receive-offload: off
rx-vlan-offload: on
tx-vlan-offload: on
ntuple-filters: off
receive-hashing: on
highdma: on [fixed]
rx-vlan-filter: on
vlan-challenged: off [fixed]
tx-lockless: off [fixed]
netns-local: off [fixed]
tx-gso-robust: off [fixed]
tx-fcoe-segmentation: on [fixed]
tx-gre-segmentation: off [fixed]
tx-ipip-segmentation: off [fixed]
tx-sit-segmentation: off [fixed]
tx-udp_tnl-segmentation: off [fixed]
tx-mpls-segmentation: off [fixed]
fcoe-mtu: off [fixed]
tx-nocache-copy: on
loopback: off [fixed]
rx-fcs: off [fixed]
rx-all: off
tx-vlan-stag-hw-insert: off [fixed]
rx-vlan-stag-hw-parse: off [fixed]
rx-vlan-stag-filter: off [fixed]
l2-fwd-offload: off

rlaager@BROKEN:~$ ethtool -k bond0
Features for bond0:
rx-checksumming: off [fixed]
tx-checksumming: on
tx-checksum-ipv4: off [fixed]
tx-checksum-ip-generic: on
tx-checksum-ipv6: off [fixed]
tx-checksum-fcoe-crc: off [fixed]
tx-checksum-sctp: off [fixed]
scatter-gather: on
tx-scatter-gather: on
tx-scatter-gather-fraglist: off [requested on]
tcp-segmentation-offload: on
tx-tcp-segmentation: on
tx-tcp-ecn-segmentation: on
tx-tcp6-segmentation: on
udp-fragmentation-offload: off [fixed]
generic-segmentation-offload: on
generic-receive-offload: on
large-receive-offload: off
rx-vlan-offload: on
tx-vlan-offload: on
ntuple-filters: off [fixed]
receive-hashing: off [fixed]
highdma: on
rx-vlan-filter: on
vlan-challenged: off [fixed]
tx-lockless: on [fixed]
netns-local: off [fixed]
tx-gso-robust: off [fixed]
tx-fcoe-segmentation: off [fixed]
tx-gre-segmentation: off [fixed]
tx-ipip-segmentation: off [fixed]
tx-sit-segmentation: off [fixed]
tx-udp_tnl-segmentation: on
tx-mpls-segmentation: off [fixed]
fcoe-mtu: off [fixed]
tx-nocache-copy: off [requested on]
loopback: off [fixed]
rx-fcs: off [fixed]
rx-all: off [fixed]
tx-vlan-stag-hw-insert: off [fixed]
rx-vlan-stag-hw-parse: off [fixed]
rx-vlan-stag-filter: off [fixed]
l2-fwd-offload: off [fixed]

rlaager@BROKEN:~$ ethtool -k br7
Features for br7:
rx-checksumming: off [fixed]
tx-checksumming: on
tx-checksum-ipv4: off [fixed]
tx-checksum-ip-generic: on
tx-checksum-ipv6: off [fixed]
tx-checksum-fcoe-crc: off [fixed]
tx-checksum-sctp: off [fixed]
scatter-gather: on
tx-scatter-gather: on
tx-scatter-gather-fraglist: off [requested on]
tcp-segmentation-offload: on
tx-tcp-segmentation: on
tx-tcp-ecn-segmentation: on
t

[Kernel-packages] [Bug 1385937] Re: [Acer Travelmate B115-M] Synaptic touchpad not correctly detected in kernel 3.16 after upgrade to Ubuntu 14.10

[Christopher M. Penalver]

** Description changed:

  Since the upgrade from Ubuntu 14.04 to 14.10 the Synaptic touchpad is
  not detected entirely. The secondary key (right mouse button) does not
  work with kernel 3.16.0-23-generic. Falling back under Ubuntu 14.10 to
  the kernel 3.13.0-37-generic the Synaptic touchpad is detected fully and
  right mouse button works again.
+ 
+ WORKAROUND: Set in BIOS Touchpad from Advanced, to Basic.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: linux-image-3.16.0-23-generic 3.16.0-23.31
  ProcVersionSignature: Ubuntu 3.16.0-23.31-generic 3.16.4
  Uname: Linux 3.16.0-23-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
-  USERPID ACCESS COMMAND
-  /dev/snd/controlC0:  hpannenb   2336 F pulseaudio
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC0:  hpannenb   2336 F pulseaudio
  CurrentDesktop: Unity
  Date: Sun Oct 26 19:45:20 2014
  HibernationDevice: RESUME=UUID=8aa00459-6b0d-4baf-84e4-7f945406d6b2
  InstallationDate: Installed on 2014-10-10 (15 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  Lsusb:
-  Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
-  Bus 001 Device 003: ID 1bcf:2c57 Sunplus Innovation Technology Inc. 
-  Bus 001 Device 004: ID 0489:e046 Foxconn / Hon Hai 
-  Bus 001 Device 002: ID 05e3:0608 Genesys Logic, Inc. Hub
-  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
+  Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
+  Bus 001 Device 003: ID 1bcf:2c57 Sunplus Innovation Technology Inc.
+  Bus 001 Device 004: ID 0489:e046 Foxconn / Hon Hai
+  Bus 001 Device 002: ID 05e3:0608 Genesys Logic, Inc. Hub
+  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Acer TravelMate B115-M
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-23-generic.efi.signed 
root=UUID=902f1410-63a6-41f1-893c-ab5e74543832 ro acpi_backlight=vendor quiet 
splash vt.handoff=7
  RelatedPackageVersions:
-  linux-restricted-modules-3.16.0-23-generic N/A
-  linux-backports-modules-3.16.0-23-generic  N/A
-  linux-firmware 1.138
+  linux-restricted-modules-3.16.0-23-generic N/A
+  linux-backports-modules-3.16.0-23-generic  N/A
+  linux-firmware 1.138
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/27/2014
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.22
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: Roxy
  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.22:bd08/27/2014:svnAcer:pnTravelMateB115-M:pvrV1.22:rvnAcer:rnRoxy:rvrType2-A01BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion:
  dmi.product.name: TravelMate B115-M
  dmi.product.version: V1.22
  dmi.sys.vendor: Acer

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

Title:
  [Acer Travelmate B115-M] Synaptic touchpad not correctly detected in
  kernel 3.16 after upgrade to Ubuntu 14.10

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Since the upgrade from Ubuntu 14.04 to 14.10 the Synaptic touchpad is
  not detected entirely. The secondary key (right mouse button) does not
  work with kernel 3.16.0-23-generic. Falling back under Ubuntu 14.10 to
  the kernel 3.13.0-37-generic the Synaptic touchpad is detected fully
  and right mouse button works again.

  WORKAROUND: Set in BIOS Touchpad from Advanced, to Basic.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: linux-image-3.16.0-23-generic 3.16.0-23.31
  ProcVersionSignature: Ubuntu 3.16.0-23.31-generic 3.16.4
  Uname: Linux 3.16.0-23-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  hpannenb   2336 F pulseaudio
  CurrentDesktop: Unity
  Date: Sun Oct 26 19:45:20 2014
  HibernationDevice: RESUME=UUID=8aa00459-6b0d-4baf-84e4-7f945406d6b2
  InstallationDate: Installed on 2014-10-10 (15 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 1bcf:2c57 Sunplus Innovation Technology Inc.
   Bus 001 Device 004: ID 0489:e046 Foxconn / Hon Hai
   Bus 001 Device 002: ID 05e3:0608 Genesys Logic, Inc. Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Acer TravelMate B115-M
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-23-generic.efi.signed 
root=UUID=902f1410-63a6-41f1-893c-ab5e74543832 ro 

[Kernel-packages] [Bug 1275879] Re: Kernel panic

[Diego Rodriguez]

Brad: I'm testing the proposed kernel fix for trusty right now, but as
Donald mentioned, 5 days might not be enough to test it since the kernel
panic occurs randomly after a period of time.

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

Title:
  Kernel panic

Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Trusty:
  Fix Committed
Status in linux source package in Utopic:
  Fix Committed
Status in linux source package in Vivid:
  Fix Committed

Bug description:
  SRU Justification

  Impact: Under certain workloads a BUG in the xen-netfront driver is
  getting triggered.

  Fix: Remove the offending BUG, and a related BUG which would have also
  been triggered by the same conditions.

  Test Case: This bug has only been seen under certain workloads
  involving haproxy and has proved challenging to reproduce. The fix has
  been verified by an affected user, with the BUG replaced by a WARN to
  ensure that the conditions which would have triggered the bug were
  actually encountered.

  Regression Potential: The fix has been verified and acked upstream.
  Removing the BUGs will not affect cases which were not crashing
  previously, and cases which were crashing can't really be made much
  worse.

  ---

  I run ubuntu servers 13.04, 13.10, and 14.04 on the AWS cloud.
  Whenever I install haproxy and nginx on the same server, after hitting
  it for a while, a kernel panic is caused. However, the kernel panic
  does not show up in ubuntu 12.04.  The kernel panic is pasted at the
  end of the attachment.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1275879/+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 1372609] Re: Touchpad detected as mouse on Asus ux303ln laptop

[Pilot6]

@JFL
In default setting left click is tap in any place of the touchpad.
This can be disabled in System Settings.
In this casy you will need to press a hardware button in lower left.

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

Title:
  Touchpad detected as mouse on Asus ux303ln laptop

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

Bug description:
  Hi! I'm following the bug reporting documentation here:

  
https://wiki.ubuntu.com/DebuggingTouchpadDetection#In_case_Touchpad_features_like_scrolling.2C_tapping.2C_etc._do_not_work_at_all.

  The touchpad on my new Asus ux303ln laptop is detected as a mouse, so
  I can't access touchpad features such as two-finger scrolling.

  The laptop was very recently released and I couldn't find any
  outstanding firmware updates for it through Asus's Windows-based
  tools.

  % lsb_release -rd
  Description:  Ubuntu 14.04.1 LTS
  Release:  14.04

  Per the instructions on the wiki, I'm attaching output from
  /proc/bus/input/devices,` xinput --list`, and /var/log/Xorg.0.log.

  This machine also has a touchscreen, which I'm fairly certain is the
  "maXtouch digitizer" visible in the logs. I haven't yet restarted in
  Windows to see if it says anything useful about the touchpad, but I
  can do so if that's helpful. This is a fresh install of 14.04 and I
  haven't done much customization of it apart from installing some
  applications and changing the default resolution.

  The only relevant bit I noticed in /var/log/dmesg is this:

  [3.967547] input: PS/2 Logitech Wheel Mouse as
  /devices/platform/i8042/serio4/input/input11

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-35-generic 3.13.0-35.62
  ProcVersionSignature: Ubuntu 3.13.0-35.62-generic 3.13.11.6
  Uname: Linux 3.13.0-35-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  tim2234 F pulseaudio
   /dev/snd/controlC1:  tim2234 F pulseaudio
  CurrentDesktop: Unity
  Date: Mon Sep 22 14:30:33 2014
  HibernationDevice: RESUME=UUID=e6052f15-271a-4424-aac2-9b0ee1e490ed
  InstallationDate: Installed on 2014-09-22 (0 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 03eb:8a32 Atmel Corp. 
   Bus 001 Device 002: ID 064e:9700 Suyin Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. UX303LN
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-35-generic.efi.signed 
root=UUID=4f908b1b-e06f-4dc9-9642-e952d2598e42 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-35-generic N/A
   linux-backports-modules-3.13.0-35-generic  N/A
   linux-firmware 1.127.6
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/23/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX303LN.203
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX303LN
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX303LN.203:bd06/23/2014:svnASUSTeKCOMPUTERINC.:pnUX303LN:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX303LN:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: UX303LN
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1372609/+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 1372609] Re: Touchpad detected as mouse on Asus ux303ln laptop

[JFL]

Great fix.  Thanks.

A question though.  To left click, you have to just "touch" the area on
the lower left.  I don't like that behaviour.  How do I make it so you
have to physically "click" to register a mouse click?  Which config
needs to be changed, or is that a lower-level driver issue?

Thanks for your hard work on this!

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

Title:
  Touchpad detected as mouse on Asus ux303ln laptop

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

Bug description:
  Hi! I'm following the bug reporting documentation here:

  
https://wiki.ubuntu.com/DebuggingTouchpadDetection#In_case_Touchpad_features_like_scrolling.2C_tapping.2C_etc._do_not_work_at_all.

  The touchpad on my new Asus ux303ln laptop is detected as a mouse, so
  I can't access touchpad features such as two-finger scrolling.

  The laptop was very recently released and I couldn't find any
  outstanding firmware updates for it through Asus's Windows-based
  tools.

  % lsb_release -rd
  Description:  Ubuntu 14.04.1 LTS
  Release:  14.04

  Per the instructions on the wiki, I'm attaching output from
  /proc/bus/input/devices,` xinput --list`, and /var/log/Xorg.0.log.

  This machine also has a touchscreen, which I'm fairly certain is the
  "maXtouch digitizer" visible in the logs. I haven't yet restarted in
  Windows to see if it says anything useful about the touchpad, but I
  can do so if that's helpful. This is a fresh install of 14.04 and I
  haven't done much customization of it apart from installing some
  applications and changing the default resolution.

  The only relevant bit I noticed in /var/log/dmesg is this:

  [3.967547] input: PS/2 Logitech Wheel Mouse as
  /devices/platform/i8042/serio4/input/input11

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-35-generic 3.13.0-35.62
  ProcVersionSignature: Ubuntu 3.13.0-35.62-generic 3.13.11.6
  Uname: Linux 3.13.0-35-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  tim2234 F pulseaudio
   /dev/snd/controlC1:  tim2234 F pulseaudio
  CurrentDesktop: Unity
  Date: Mon Sep 22 14:30:33 2014
  HibernationDevice: RESUME=UUID=e6052f15-271a-4424-aac2-9b0ee1e490ed
  InstallationDate: Installed on 2014-09-22 (0 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 03eb:8a32 Atmel Corp. 
   Bus 001 Device 002: ID 064e:9700 Suyin Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. UX303LN
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-35-generic.efi.signed 
root=UUID=4f908b1b-e06f-4dc9-9642-e952d2598e42 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-35-generic N/A
   linux-backports-modules-3.13.0-35-generic  N/A
   linux-firmware 1.127.6
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/23/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX303LN.203
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX303LN
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX303LN.203:bd06/23/2014:svnASUSTeKCOMPUTERINC.:pnUX303LN:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX303LN:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: UX303LN
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1372609/+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 1404384] [NEW] python-apport crashes when told to allow the user to view the report..

[Stephen Frost]

Public bug reported:

This is pretty rough:

root@tamriel:~# apport-collect 1404374

*** Collecting problem information

The collected information can be sent to the developers to improve the
application. This might take a few minutes.
.dpkg-query: no packages found matching linux
...

*** Send problem report to the developers?

After the problem report has been sent, please fill out the form in the
automatically opened web browser.

What would you like to do? Your options are:
  S: Send report (470.3 KB)
  V: View report
  K: Keep report file for sending later or copying to somewhere else
  I: Cancel and ignore future crashes of this program version
  C: Cancel
Please choose (S/V/K/I/C): V
Traceback (most recent call last):
  File "/usr/bin/apport-cli", line 370, in 
if not app.run_argv():
  File "/usr/lib/python2.7/dist-packages/apport/ui.py", line 652, in run_argv
return self.run_update_report()
  File "/usr/lib/python2.7/dist-packages/apport/ui.py", line 568, in 
run_update_report
response = self.ui_present_report_details(allowed_to_report)
  File "/usr/bin/apport-cli", line 209, in ui_present_report_details
self.collect_info()
  File "/usr/lib/python2.7/dist-packages/apport/ui.py", line 966, in 
collect_info
if self.report['ProblemType'] == 'Crash':
  File "/usr/lib/python2.7/UserDict.py", line 23, in __getitem__
raise KeyError(key)
KeyError: 'ProblemType'

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

** Package changed: linux (Ubuntu) => apport (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/1404384

Title:
  python-apport crashes when told to allow the user to view the report..

Status in apport package in Ubuntu:
  New

Bug description:
  This is pretty rough:

  root@tamriel:~# apport-collect 1404374

  *** Collecting problem information

  The collected information can be sent to the developers to improve the
  application. This might take a few minutes.
  .dpkg-query: no packages found matching linux
  ...

  *** Send problem report to the developers?

  After the problem report has been sent, please fill out the form in the
  automatically opened web browser.

  What would you like to do? Your options are:
S: Send report (470.3 KB)
V: View report
K: Keep report file for sending later or copying to somewhere else
I: Cancel and ignore future crashes of this program version
C: Cancel
  Please choose (S/V/K/I/C): V
  Traceback (most recent call last):
File "/usr/bin/apport-cli", line 370, in 
  if not app.run_argv():
File "/usr/lib/python2.7/dist-packages/apport/ui.py", line 652, in run_argv
  return self.run_update_report()
File "/usr/lib/python2.7/dist-packages/apport/ui.py", line 568, in 
run_update_report
  response = self.ui_present_report_details(allowed_to_report)
File "/usr/bin/apport-cli", line 209, in ui_present_report_details
  self.collect_info()
File "/usr/lib/python2.7/dist-packages/apport/ui.py", line 966, in 
collect_info
  if self.report['ProblemType'] == 'Crash':
File "/usr/lib/python2.7/UserDict.py", line 23, in __getitem__
  raise KeyError(key)
  KeyError: 'ProblemType'

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1404384/+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 1404050] Re: After loading Ubuntu along side windows, my keyboard does not work on either boot menu. Keyboard works after boot is complete.

[Arnold L. Pearl]

Issue was resolved by moving the USB keyboard connector from the front
USB port to a USB port on the rear of the computer.  Boot menu works as
advertised, must have to do with timing and priority of the USB ports.

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

Title:
  After loading Ubuntu along side windows, my keyboard does not work on
  either boot menu.  Keyboard works after boot is complete.

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Prior to loading Ubuntu 14.10, my system boot menu comes up and I can
  make changes using my keyboard. (F10,F11, up, down etc).  After
  loading Ubuntu, my keyboard does not respond on either boot menu.
  (Launch Ubuntu, Launch Window)  As a result, I can't change my system
  boot and I can't change between Windows and Ubuntu on the Ubuntu boot
  menu. (defaults to Ubuntu)

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: ubuntu-release-upgrader-core 1:14.10.9
  ProcVersionSignature: Ubuntu 3.16.0-28.38-generic 3.16.7-ckt1
  Uname: Linux 3.16.0-28-generic x86_64
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: amd64
  CrashDB: ubuntu
  CurrentDesktop: Unity
  Date: Thu Dec 18 17:15:45 2014
  InstallationDate: Installed on 2014-12-14 (3 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: ubuntu-release-upgrader
  Symptom: dist-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)

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

[Stephen Frost]

apport information

** Attachment added: "WifiSyslog.txt"
   
https://bugs.launchpad.net/bugs/1404374/+attachment/4284394/+files/WifiSyslog.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/1404374

Title:
  Apparently ipv6-related crash in Linux version 3.13.0-43-generic
  (buildd@tipua) (gcc version 4.8.2 (Ubuntu 4.8.2-19ubuntu 1) )
  #72-Ubuntu SMP Mon Dec 8 19:35:06 UTC 2014 (Ubuntu
  3.13.0-43.72-generic 3.13.11.11)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I'm on OFTC and Freenode as Snow-Man if folks want to chat further or
  if there's anything I can run with 'crash' to provide additional
  information.

  This is a KVM guest running under a physical box which is running the
  same kernel (43.72)

  I've downgraded the KVM guest to Linux tamriel 3.13.0-40-generic
  #69-Ubuntu SMP Thu Nov 13 17:53:56 UTC 2014 x86_64 x86_64 x86_64
  GNU/Linux; hopefully this will be stable but I'll report back if it's
  not.  Other guests are running the 43.72 kernel and have not crashed,
  but most are single-cpu while the guest which is crashing is 4-cpu.

  I have crash installed and a dump file.  Here is the dmesg output from
  the crash:

  [   15.407890] general protection fault:  [#1] SMP 
  [   15.411159] Modules linked in: ttm drm_kms_helper kvm_amd drm kvm 
syscopyarea sysfillrect sysimgblt i2c_piix4 serio_raw lp mac_hid parport 
psmouse floppy virtio_scsi
  [   15.411159] CPU: 3 PID: 2398 Comm: smtp Not tainted 3.13.0-43-generic 
#72-Ubuntu
  [   15.411159] Hardware name: Bochs Bochs, BIOS Bochs 01/01/2011
  [   15.411159] task: 8800d8776000 ti: 880036a14000 task.ti: 
880036a14000
  [   15.411159] RIP: 0010:[]  [] 
ip6_xmit+0x1a2/0x410
  [   15.411159] RSP: 0018:880036a15b18  EFLAGS: 00010286
  [   15.411159] RAX: 5709 RBX: 8800dbbb94e8 RCX: 
0001
  [   15.411159] RDX: 8189cc00 RSI: 0028 RDI: 
8800d96126c0
  [   15.411159] RBP: 880036a15b78 R08:  R09: 
000165d6
  [   15.411159] R10:  R11:  R12: 
8800d9bfa6c0
  [   15.411159] R13: 8800d96126c0 R14: 0060 R15: 
880036a15b90
  [   15.411159] FS:  7f02749c3740() GS:88011fd8() 
knlGS:
  [   15.411159] CS:  0010 DS:  ES:  CR0: 80050033
  [   15.411159] CR2: 7f027620d048 CR3: da851000 CR4: 
06e0
  [   15.428200] Stack:
  [   15.428200]  880036a15b78 816f0ac8 8800d8ea18e8 
0adc
  [   15.430445]  81cda780 06ff880036a15fd8 880036a15ba4 
8800d9bfa6c0
  [   15.430673]  8800dbbb94e8 8800d9bfada0 0020 
8800d96126c0
  [   15.433514] Call Trace:
  [   15.433514]  [] ? inet6_csk_route_socket+0x128/0x200
  [   15.433514]  [] inet6_csk_xmit+0x7d/0xd0
  [   15.433514]  [] tcp_transmit_skb+0x469/0x8d0
  [   15.433514]  [] tcp_write_xmit+0x140/0xb10
  [   15.433514]  [] ? tcp_current_mss+0x54/0x80
  [   15.433514]  [] tcp_push_one+0x30/0x40
  [   15.433514]  [] tcp_sendmsg+0x4e1/0xdb0
  [   15.433514]  [] inet_sendmsg+0x64/0xb0
  [   15.433514]  [] ? apparmor_socket_sendmsg+0x17/0x20
  [   15.433514]  [] sock_aio_write+0xfe/0x130
  [   15.433514]  [] do_sync_write+0x5a/0x90
  [   15.433514]  [] vfs_write+0x1ad/0x1f0
  [   15.433514]  [] SyS_write+0x49/0xa0
  [   15.433514]  [] ? SyS_poll+0x65/0x100
  [   15.433514]  [] system_call_fastpath+0x1a/0x1f
  [   15.433514] Code: 49 8b 45 20 ff 50 20 39 43 68 77 6d 48 8b 43 58 48 83 e0 
fe 48 8b 80 48 01 00 00 48 85 c0 0f 84 51 02 00 00 48 8b 80 68 02 00 00 <65> 48 
ff 40 28 8b 53 68 65 48 01 50 30 48 8b 44 24 20 48 8b 80 
  [   15.433514] RIP  [] ip6_xmit+0x1a2/0x410
  [   15.433514]  RSP 

  Here's it the output from crash:

KERNEL: /usr/lib/debug/boot/vmlinux-3.13.0-43-generic
  DUMPFILE: /var/crash/201412191519/dump.201412191519  [PARTIAL DUMP]
  CPUS: 4
  DATE: Fri Dec 19 15:19:18 2014
UPTIME: 00:00:15
  LOAD AVERAGE: 0.58, 0.13, 0.04
 TASKS: 229
  NODENAME: tamriel
   RELEASE: 3.13.0-43-generic
   VERSION: #72-Ubuntu SMP Mon Dec 8 19:35:06 UTC 2014
   MACHINE: x86_64  (2700 Mhz)
MEMORY: 4 GB
 PANIC: ""
   PID: 2398
   COMMAND: "smtp"
  TASK: 8800d8776000  [THREAD_INFO: 880036a14000]
   CPU: 3
 STATE: TASK_RUNNING (PANIC)

  Probably not really interesting, but here's the lspci -vnvn output:

  00:00.0 Host bridge [0600]: Intel Corporation 440FX - 82441FX PMC [Natoma] 
[8086:1237] (rev 02)
  Subsystem: Red Hat, Inc Qemu virtual machine [1af4:1100]
  Control: I/O+ Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR+ FastB2B- DisINTx-
  Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- 
SERR- TAbort- 
SERR- TAbort- 
SERR- TAbort- 
SE

[Kernel-packages] [Bug 1404374] Re: Apparently ipv6-related crash in Linux version 3.13.0-43-generic (buildd@tipua) (gcc version 4.8.2 (Ubuntu 4.8.2-19ubuntu 1) ) #72-Ubuntu SMP Mon Dec 8 19:35:06 UTC

[Stephen Frost]

Note that the apport information included is from the 40.69 kernel boot,
of course.

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

Title:
  Apparently ipv6-related crash in Linux version 3.13.0-43-generic
  (buildd@tipua) (gcc version 4.8.2 (Ubuntu 4.8.2-19ubuntu 1) )
  #72-Ubuntu SMP Mon Dec 8 19:35:06 UTC 2014 (Ubuntu
  3.13.0-43.72-generic 3.13.11.11)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I'm on OFTC and Freenode as Snow-Man if folks want to chat further or
  if there's anything I can run with 'crash' to provide additional
  information.

  This is a KVM guest running under a physical box which is running the
  same kernel (43.72)

  I've downgraded the KVM guest to Linux tamriel 3.13.0-40-generic
  #69-Ubuntu SMP Thu Nov 13 17:53:56 UTC 2014 x86_64 x86_64 x86_64
  GNU/Linux; hopefully this will be stable but I'll report back if it's
  not.  Other guests are running the 43.72 kernel and have not crashed,
  but most are single-cpu while the guest which is crashing is 4-cpu.

  I have crash installed and a dump file.  Here is the dmesg output from
  the crash:

  [   15.407890] general protection fault:  [#1] SMP 
  [   15.411159] Modules linked in: ttm drm_kms_helper kvm_amd drm kvm 
syscopyarea sysfillrect sysimgblt i2c_piix4 serio_raw lp mac_hid parport 
psmouse floppy virtio_scsi
  [   15.411159] CPU: 3 PID: 2398 Comm: smtp Not tainted 3.13.0-43-generic 
#72-Ubuntu
  [   15.411159] Hardware name: Bochs Bochs, BIOS Bochs 01/01/2011
  [   15.411159] task: 8800d8776000 ti: 880036a14000 task.ti: 
880036a14000
  [   15.411159] RIP: 0010:[]  [] 
ip6_xmit+0x1a2/0x410
  [   15.411159] RSP: 0018:880036a15b18  EFLAGS: 00010286
  [   15.411159] RAX: 5709 RBX: 8800dbbb94e8 RCX: 
0001
  [   15.411159] RDX: 8189cc00 RSI: 0028 RDI: 
8800d96126c0
  [   15.411159] RBP: 880036a15b78 R08:  R09: 
000165d6
  [   15.411159] R10:  R11:  R12: 
8800d9bfa6c0
  [   15.411159] R13: 8800d96126c0 R14: 0060 R15: 
880036a15b90
  [   15.411159] FS:  7f02749c3740() GS:88011fd8() 
knlGS:
  [   15.411159] CS:  0010 DS:  ES:  CR0: 80050033
  [   15.411159] CR2: 7f027620d048 CR3: da851000 CR4: 
06e0
  [   15.428200] Stack:
  [   15.428200]  880036a15b78 816f0ac8 8800d8ea18e8 
0adc
  [   15.430445]  81cda780 06ff880036a15fd8 880036a15ba4 
8800d9bfa6c0
  [   15.430673]  8800dbbb94e8 8800d9bfada0 0020 
8800d96126c0
  [   15.433514] Call Trace:
  [   15.433514]  [] ? inet6_csk_route_socket+0x128/0x200
  [   15.433514]  [] inet6_csk_xmit+0x7d/0xd0
  [   15.433514]  [] tcp_transmit_skb+0x469/0x8d0
  [   15.433514]  [] tcp_write_xmit+0x140/0xb10
  [   15.433514]  [] ? tcp_current_mss+0x54/0x80
  [   15.433514]  [] tcp_push_one+0x30/0x40
  [   15.433514]  [] tcp_sendmsg+0x4e1/0xdb0
  [   15.433514]  [] inet_sendmsg+0x64/0xb0
  [   15.433514]  [] ? apparmor_socket_sendmsg+0x17/0x20
  [   15.433514]  [] sock_aio_write+0xfe/0x130
  [   15.433514]  [] do_sync_write+0x5a/0x90
  [   15.433514]  [] vfs_write+0x1ad/0x1f0
  [   15.433514]  [] SyS_write+0x49/0xa0
  [   15.433514]  [] ? SyS_poll+0x65/0x100
  [   15.433514]  [] system_call_fastpath+0x1a/0x1f
  [   15.433514] Code: 49 8b 45 20 ff 50 20 39 43 68 77 6d 48 8b 43 58 48 83 e0 
fe 48 8b 80 48 01 00 00 48 85 c0 0f 84 51 02 00 00 48 8b 80 68 02 00 00 <65> 48 
ff 40 28 8b 53 68 65 48 01 50 30 48 8b 44 24 20 48 8b 80 
  [   15.433514] RIP  [] ip6_xmit+0x1a2/0x410
  [   15.433514]  RSP 

  Here's it the output from crash:

KERNEL: /usr/lib/debug/boot/vmlinux-3.13.0-43-generic
  DUMPFILE: /var/crash/201412191519/dump.201412191519  [PARTIAL DUMP]
  CPUS: 4
  DATE: Fri Dec 19 15:19:18 2014
UPTIME: 00:00:15
  LOAD AVERAGE: 0.58, 0.13, 0.04
 TASKS: 229
  NODENAME: tamriel
   RELEASE: 3.13.0-43-generic
   VERSION: #72-Ubuntu SMP Mon Dec 8 19:35:06 UTC 2014
   MACHINE: x86_64  (2700 Mhz)
MEMORY: 4 GB
 PANIC: ""
   PID: 2398
   COMMAND: "smtp"
  TASK: 8800d8776000  [THREAD_INFO: 880036a14000]
   CPU: 3
 STATE: TASK_RUNNING (PANIC)

  Probably not really interesting, but here's the lspci -vnvn output:

  00:00.0 Host bridge [0600]: Intel Corporation 440FX - 82441FX PMC [Natoma] 
[8086:1237] (rev 02)
  Subsystem: Red Hat, Inc Qemu virtual machine [1af4:1100]
  Control: I/O+ Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR+ FastB2B- DisINTx-
  Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- 
SERR- TAbort- 
SERR- TAbort- 
SERR- T

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

[Stephen Frost]

apport information

** Attachment added: "ProcCpuinfo.txt"
   
https://bugs.launchpad.net/bugs/1404374/+attachment/4284389/+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/1404374

Title:
  Apparently ipv6-related crash in Linux version 3.13.0-43-generic
  (buildd@tipua) (gcc version 4.8.2 (Ubuntu 4.8.2-19ubuntu 1) )
  #72-Ubuntu SMP Mon Dec 8 19:35:06 UTC 2014 (Ubuntu
  3.13.0-43.72-generic 3.13.11.11)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I'm on OFTC and Freenode as Snow-Man if folks want to chat further or
  if there's anything I can run with 'crash' to provide additional
  information.

  This is a KVM guest running under a physical box which is running the
  same kernel (43.72)

  I've downgraded the KVM guest to Linux tamriel 3.13.0-40-generic
  #69-Ubuntu SMP Thu Nov 13 17:53:56 UTC 2014 x86_64 x86_64 x86_64
  GNU/Linux; hopefully this will be stable but I'll report back if it's
  not.  Other guests are running the 43.72 kernel and have not crashed,
  but most are single-cpu while the guest which is crashing is 4-cpu.

  I have crash installed and a dump file.  Here is the dmesg output from
  the crash:

  [   15.407890] general protection fault:  [#1] SMP 
  [   15.411159] Modules linked in: ttm drm_kms_helper kvm_amd drm kvm 
syscopyarea sysfillrect sysimgblt i2c_piix4 serio_raw lp mac_hid parport 
psmouse floppy virtio_scsi
  [   15.411159] CPU: 3 PID: 2398 Comm: smtp Not tainted 3.13.0-43-generic 
#72-Ubuntu
  [   15.411159] Hardware name: Bochs Bochs, BIOS Bochs 01/01/2011
  [   15.411159] task: 8800d8776000 ti: 880036a14000 task.ti: 
880036a14000
  [   15.411159] RIP: 0010:[]  [] 
ip6_xmit+0x1a2/0x410
  [   15.411159] RSP: 0018:880036a15b18  EFLAGS: 00010286
  [   15.411159] RAX: 5709 RBX: 8800dbbb94e8 RCX: 
0001
  [   15.411159] RDX: 8189cc00 RSI: 0028 RDI: 
8800d96126c0
  [   15.411159] RBP: 880036a15b78 R08:  R09: 
000165d6
  [   15.411159] R10:  R11:  R12: 
8800d9bfa6c0
  [   15.411159] R13: 8800d96126c0 R14: 0060 R15: 
880036a15b90
  [   15.411159] FS:  7f02749c3740() GS:88011fd8() 
knlGS:
  [   15.411159] CS:  0010 DS:  ES:  CR0: 80050033
  [   15.411159] CR2: 7f027620d048 CR3: da851000 CR4: 
06e0
  [   15.428200] Stack:
  [   15.428200]  880036a15b78 816f0ac8 8800d8ea18e8 
0adc
  [   15.430445]  81cda780 06ff880036a15fd8 880036a15ba4 
8800d9bfa6c0
  [   15.430673]  8800dbbb94e8 8800d9bfada0 0020 
8800d96126c0
  [   15.433514] Call Trace:
  [   15.433514]  [] ? inet6_csk_route_socket+0x128/0x200
  [   15.433514]  [] inet6_csk_xmit+0x7d/0xd0
  [   15.433514]  [] tcp_transmit_skb+0x469/0x8d0
  [   15.433514]  [] tcp_write_xmit+0x140/0xb10
  [   15.433514]  [] ? tcp_current_mss+0x54/0x80
  [   15.433514]  [] tcp_push_one+0x30/0x40
  [   15.433514]  [] tcp_sendmsg+0x4e1/0xdb0
  [   15.433514]  [] inet_sendmsg+0x64/0xb0
  [   15.433514]  [] ? apparmor_socket_sendmsg+0x17/0x20
  [   15.433514]  [] sock_aio_write+0xfe/0x130
  [   15.433514]  [] do_sync_write+0x5a/0x90
  [   15.433514]  [] vfs_write+0x1ad/0x1f0
  [   15.433514]  [] SyS_write+0x49/0xa0
  [   15.433514]  [] ? SyS_poll+0x65/0x100
  [   15.433514]  [] system_call_fastpath+0x1a/0x1f
  [   15.433514] Code: 49 8b 45 20 ff 50 20 39 43 68 77 6d 48 8b 43 58 48 83 e0 
fe 48 8b 80 48 01 00 00 48 85 c0 0f 84 51 02 00 00 48 8b 80 68 02 00 00 <65> 48 
ff 40 28 8b 53 68 65 48 01 50 30 48 8b 44 24 20 48 8b 80 
  [   15.433514] RIP  [] ip6_xmit+0x1a2/0x410
  [   15.433514]  RSP 

  Here's it the output from crash:

KERNEL: /usr/lib/debug/boot/vmlinux-3.13.0-43-generic
  DUMPFILE: /var/crash/201412191519/dump.201412191519  [PARTIAL DUMP]
  CPUS: 4
  DATE: Fri Dec 19 15:19:18 2014
UPTIME: 00:00:15
  LOAD AVERAGE: 0.58, 0.13, 0.04
 TASKS: 229
  NODENAME: tamriel
   RELEASE: 3.13.0-43-generic
   VERSION: #72-Ubuntu SMP Mon Dec 8 19:35:06 UTC 2014
   MACHINE: x86_64  (2700 Mhz)
MEMORY: 4 GB
 PANIC: ""
   PID: 2398
   COMMAND: "smtp"
  TASK: 8800d8776000  [THREAD_INFO: 880036a14000]
   CPU: 3
 STATE: TASK_RUNNING (PANIC)

  Probably not really interesting, but here's the lspci -vnvn output:

  00:00.0 Host bridge [0600]: Intel Corporation 440FX - 82441FX PMC [Natoma] 
[8086:1237] (rev 02)
  Subsystem: Red Hat, Inc Qemu virtual machine [1af4:1100]
  Control: I/O+ Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR+ FastB2B- DisINTx-
  Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- 
SERR- TAbort- 
SERR- TAbort- 
SERR- TAbort- 

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

[Stephen Frost]

apport information

** Attachment added: "ProcModules.txt"
   
https://bugs.launchpad.net/bugs/1404374/+attachment/4284391/+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/1404374

Title:
  Apparently ipv6-related crash in Linux version 3.13.0-43-generic
  (buildd@tipua) (gcc version 4.8.2 (Ubuntu 4.8.2-19ubuntu 1) )
  #72-Ubuntu SMP Mon Dec 8 19:35:06 UTC 2014 (Ubuntu
  3.13.0-43.72-generic 3.13.11.11)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I'm on OFTC and Freenode as Snow-Man if folks want to chat further or
  if there's anything I can run with 'crash' to provide additional
  information.

  This is a KVM guest running under a physical box which is running the
  same kernel (43.72)

  I've downgraded the KVM guest to Linux tamriel 3.13.0-40-generic
  #69-Ubuntu SMP Thu Nov 13 17:53:56 UTC 2014 x86_64 x86_64 x86_64
  GNU/Linux; hopefully this will be stable but I'll report back if it's
  not.  Other guests are running the 43.72 kernel and have not crashed,
  but most are single-cpu while the guest which is crashing is 4-cpu.

  I have crash installed and a dump file.  Here is the dmesg output from
  the crash:

  [   15.407890] general protection fault:  [#1] SMP 
  [   15.411159] Modules linked in: ttm drm_kms_helper kvm_amd drm kvm 
syscopyarea sysfillrect sysimgblt i2c_piix4 serio_raw lp mac_hid parport 
psmouse floppy virtio_scsi
  [   15.411159] CPU: 3 PID: 2398 Comm: smtp Not tainted 3.13.0-43-generic 
#72-Ubuntu
  [   15.411159] Hardware name: Bochs Bochs, BIOS Bochs 01/01/2011
  [   15.411159] task: 8800d8776000 ti: 880036a14000 task.ti: 
880036a14000
  [   15.411159] RIP: 0010:[]  [] 
ip6_xmit+0x1a2/0x410
  [   15.411159] RSP: 0018:880036a15b18  EFLAGS: 00010286
  [   15.411159] RAX: 5709 RBX: 8800dbbb94e8 RCX: 
0001
  [   15.411159] RDX: 8189cc00 RSI: 0028 RDI: 
8800d96126c0
  [   15.411159] RBP: 880036a15b78 R08:  R09: 
000165d6
  [   15.411159] R10:  R11:  R12: 
8800d9bfa6c0
  [   15.411159] R13: 8800d96126c0 R14: 0060 R15: 
880036a15b90
  [   15.411159] FS:  7f02749c3740() GS:88011fd8() 
knlGS:
  [   15.411159] CS:  0010 DS:  ES:  CR0: 80050033
  [   15.411159] CR2: 7f027620d048 CR3: da851000 CR4: 
06e0
  [   15.428200] Stack:
  [   15.428200]  880036a15b78 816f0ac8 8800d8ea18e8 
0adc
  [   15.430445]  81cda780 06ff880036a15fd8 880036a15ba4 
8800d9bfa6c0
  [   15.430673]  8800dbbb94e8 8800d9bfada0 0020 
8800d96126c0
  [   15.433514] Call Trace:
  [   15.433514]  [] ? inet6_csk_route_socket+0x128/0x200
  [   15.433514]  [] inet6_csk_xmit+0x7d/0xd0
  [   15.433514]  [] tcp_transmit_skb+0x469/0x8d0
  [   15.433514]  [] tcp_write_xmit+0x140/0xb10
  [   15.433514]  [] ? tcp_current_mss+0x54/0x80
  [   15.433514]  [] tcp_push_one+0x30/0x40
  [   15.433514]  [] tcp_sendmsg+0x4e1/0xdb0
  [   15.433514]  [] inet_sendmsg+0x64/0xb0
  [   15.433514]  [] ? apparmor_socket_sendmsg+0x17/0x20
  [   15.433514]  [] sock_aio_write+0xfe/0x130
  [   15.433514]  [] do_sync_write+0x5a/0x90
  [   15.433514]  [] vfs_write+0x1ad/0x1f0
  [   15.433514]  [] SyS_write+0x49/0xa0
  [   15.433514]  [] ? SyS_poll+0x65/0x100
  [   15.433514]  [] system_call_fastpath+0x1a/0x1f
  [   15.433514] Code: 49 8b 45 20 ff 50 20 39 43 68 77 6d 48 8b 43 58 48 83 e0 
fe 48 8b 80 48 01 00 00 48 85 c0 0f 84 51 02 00 00 48 8b 80 68 02 00 00 <65> 48 
ff 40 28 8b 53 68 65 48 01 50 30 48 8b 44 24 20 48 8b 80 
  [   15.433514] RIP  [] ip6_xmit+0x1a2/0x410
  [   15.433514]  RSP 

  Here's it the output from crash:

KERNEL: /usr/lib/debug/boot/vmlinux-3.13.0-43-generic
  DUMPFILE: /var/crash/201412191519/dump.201412191519  [PARTIAL DUMP]
  CPUS: 4
  DATE: Fri Dec 19 15:19:18 2014
UPTIME: 00:00:15
  LOAD AVERAGE: 0.58, 0.13, 0.04
 TASKS: 229
  NODENAME: tamriel
   RELEASE: 3.13.0-43-generic
   VERSION: #72-Ubuntu SMP Mon Dec 8 19:35:06 UTC 2014
   MACHINE: x86_64  (2700 Mhz)
MEMORY: 4 GB
 PANIC: ""
   PID: 2398
   COMMAND: "smtp"
  TASK: 8800d8776000  [THREAD_INFO: 880036a14000]
   CPU: 3
 STATE: TASK_RUNNING (PANIC)

  Probably not really interesting, but here's the lspci -vnvn output:

  00:00.0 Host bridge [0600]: Intel Corporation 440FX - 82441FX PMC [Natoma] 
[8086:1237] (rev 02)
  Subsystem: Red Hat, Inc Qemu virtual machine [1af4:1100]
  Control: I/O+ Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR+ FastB2B- DisINTx-
  Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- 
SERR- TAbort- 
SERR- TAbort- 
SERR- TAbort- 

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

[Stephen Frost]

apport information

** Attachment added: "UdevDb.txt"
   https://bugs.launchpad.net/bugs/1404374/+attachment/4284392/+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/1404374

Title:
  Apparently ipv6-related crash in Linux version 3.13.0-43-generic
  (buildd@tipua) (gcc version 4.8.2 (Ubuntu 4.8.2-19ubuntu 1) )
  #72-Ubuntu SMP Mon Dec 8 19:35:06 UTC 2014 (Ubuntu
  3.13.0-43.72-generic 3.13.11.11)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I'm on OFTC and Freenode as Snow-Man if folks want to chat further or
  if there's anything I can run with 'crash' to provide additional
  information.

  This is a KVM guest running under a physical box which is running the
  same kernel (43.72)

  I've downgraded the KVM guest to Linux tamriel 3.13.0-40-generic
  #69-Ubuntu SMP Thu Nov 13 17:53:56 UTC 2014 x86_64 x86_64 x86_64
  GNU/Linux; hopefully this will be stable but I'll report back if it's
  not.  Other guests are running the 43.72 kernel and have not crashed,
  but most are single-cpu while the guest which is crashing is 4-cpu.

  I have crash installed and a dump file.  Here is the dmesg output from
  the crash:

  [   15.407890] general protection fault:  [#1] SMP 
  [   15.411159] Modules linked in: ttm drm_kms_helper kvm_amd drm kvm 
syscopyarea sysfillrect sysimgblt i2c_piix4 serio_raw lp mac_hid parport 
psmouse floppy virtio_scsi
  [   15.411159] CPU: 3 PID: 2398 Comm: smtp Not tainted 3.13.0-43-generic 
#72-Ubuntu
  [   15.411159] Hardware name: Bochs Bochs, BIOS Bochs 01/01/2011
  [   15.411159] task: 8800d8776000 ti: 880036a14000 task.ti: 
880036a14000
  [   15.411159] RIP: 0010:[]  [] 
ip6_xmit+0x1a2/0x410
  [   15.411159] RSP: 0018:880036a15b18  EFLAGS: 00010286
  [   15.411159] RAX: 5709 RBX: 8800dbbb94e8 RCX: 
0001
  [   15.411159] RDX: 8189cc00 RSI: 0028 RDI: 
8800d96126c0
  [   15.411159] RBP: 880036a15b78 R08:  R09: 
000165d6
  [   15.411159] R10:  R11:  R12: 
8800d9bfa6c0
  [   15.411159] R13: 8800d96126c0 R14: 0060 R15: 
880036a15b90
  [   15.411159] FS:  7f02749c3740() GS:88011fd8() 
knlGS:
  [   15.411159] CS:  0010 DS:  ES:  CR0: 80050033
  [   15.411159] CR2: 7f027620d048 CR3: da851000 CR4: 
06e0
  [   15.428200] Stack:
  [   15.428200]  880036a15b78 816f0ac8 8800d8ea18e8 
0adc
  [   15.430445]  81cda780 06ff880036a15fd8 880036a15ba4 
8800d9bfa6c0
  [   15.430673]  8800dbbb94e8 8800d9bfada0 0020 
8800d96126c0
  [   15.433514] Call Trace:
  [   15.433514]  [] ? inet6_csk_route_socket+0x128/0x200
  [   15.433514]  [] inet6_csk_xmit+0x7d/0xd0
  [   15.433514]  [] tcp_transmit_skb+0x469/0x8d0
  [   15.433514]  [] tcp_write_xmit+0x140/0xb10
  [   15.433514]  [] ? tcp_current_mss+0x54/0x80
  [   15.433514]  [] tcp_push_one+0x30/0x40
  [   15.433514]  [] tcp_sendmsg+0x4e1/0xdb0
  [   15.433514]  [] inet_sendmsg+0x64/0xb0
  [   15.433514]  [] ? apparmor_socket_sendmsg+0x17/0x20
  [   15.433514]  [] sock_aio_write+0xfe/0x130
  [   15.433514]  [] do_sync_write+0x5a/0x90
  [   15.433514]  [] vfs_write+0x1ad/0x1f0
  [   15.433514]  [] SyS_write+0x49/0xa0
  [   15.433514]  [] ? SyS_poll+0x65/0x100
  [   15.433514]  [] system_call_fastpath+0x1a/0x1f
  [   15.433514] Code: 49 8b 45 20 ff 50 20 39 43 68 77 6d 48 8b 43 58 48 83 e0 
fe 48 8b 80 48 01 00 00 48 85 c0 0f 84 51 02 00 00 48 8b 80 68 02 00 00 <65> 48 
ff 40 28 8b 53 68 65 48 01 50 30 48 8b 44 24 20 48 8b 80 
  [   15.433514] RIP  [] ip6_xmit+0x1a2/0x410
  [   15.433514]  RSP 

  Here's it the output from crash:

KERNEL: /usr/lib/debug/boot/vmlinux-3.13.0-43-generic
  DUMPFILE: /var/crash/201412191519/dump.201412191519  [PARTIAL DUMP]
  CPUS: 4
  DATE: Fri Dec 19 15:19:18 2014
UPTIME: 00:00:15
  LOAD AVERAGE: 0.58, 0.13, 0.04
 TASKS: 229
  NODENAME: tamriel
   RELEASE: 3.13.0-43-generic
   VERSION: #72-Ubuntu SMP Mon Dec 8 19:35:06 UTC 2014
   MACHINE: x86_64  (2700 Mhz)
MEMORY: 4 GB
 PANIC: ""
   PID: 2398
   COMMAND: "smtp"
  TASK: 8800d8776000  [THREAD_INFO: 880036a14000]
   CPU: 3
 STATE: TASK_RUNNING (PANIC)

  Probably not really interesting, but here's the lspci -vnvn output:

  00:00.0 Host bridge [0600]: Intel Corporation 440FX - 82441FX PMC [Natoma] 
[8086:1237] (rev 02)
  Subsystem: Red Hat, Inc Qemu virtual machine [1af4:1100]
  Control: I/O+ Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR+ FastB2B- DisINTx-
  Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- 
SERR- TAbort- 
SERR- TAbort- 
SERR- TAbort- 
SERR- TAbor

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

[Stephen Frost]

apport information

** Attachment added: "UdevLog.txt"
   
https://bugs.launchpad.net/bugs/1404374/+attachment/4284393/+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/1404374

Title:
  Apparently ipv6-related crash in Linux version 3.13.0-43-generic
  (buildd@tipua) (gcc version 4.8.2 (Ubuntu 4.8.2-19ubuntu 1) )
  #72-Ubuntu SMP Mon Dec 8 19:35:06 UTC 2014 (Ubuntu
  3.13.0-43.72-generic 3.13.11.11)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I'm on OFTC and Freenode as Snow-Man if folks want to chat further or
  if there's anything I can run with 'crash' to provide additional
  information.

  This is a KVM guest running under a physical box which is running the
  same kernel (43.72)

  I've downgraded the KVM guest to Linux tamriel 3.13.0-40-generic
  #69-Ubuntu SMP Thu Nov 13 17:53:56 UTC 2014 x86_64 x86_64 x86_64
  GNU/Linux; hopefully this will be stable but I'll report back if it's
  not.  Other guests are running the 43.72 kernel and have not crashed,
  but most are single-cpu while the guest which is crashing is 4-cpu.

  I have crash installed and a dump file.  Here is the dmesg output from
  the crash:

  [   15.407890] general protection fault:  [#1] SMP 
  [   15.411159] Modules linked in: ttm drm_kms_helper kvm_amd drm kvm 
syscopyarea sysfillrect sysimgblt i2c_piix4 serio_raw lp mac_hid parport 
psmouse floppy virtio_scsi
  [   15.411159] CPU: 3 PID: 2398 Comm: smtp Not tainted 3.13.0-43-generic 
#72-Ubuntu
  [   15.411159] Hardware name: Bochs Bochs, BIOS Bochs 01/01/2011
  [   15.411159] task: 8800d8776000 ti: 880036a14000 task.ti: 
880036a14000
  [   15.411159] RIP: 0010:[]  [] 
ip6_xmit+0x1a2/0x410
  [   15.411159] RSP: 0018:880036a15b18  EFLAGS: 00010286
  [   15.411159] RAX: 5709 RBX: 8800dbbb94e8 RCX: 
0001
  [   15.411159] RDX: 8189cc00 RSI: 0028 RDI: 
8800d96126c0
  [   15.411159] RBP: 880036a15b78 R08:  R09: 
000165d6
  [   15.411159] R10:  R11:  R12: 
8800d9bfa6c0
  [   15.411159] R13: 8800d96126c0 R14: 0060 R15: 
880036a15b90
  [   15.411159] FS:  7f02749c3740() GS:88011fd8() 
knlGS:
  [   15.411159] CS:  0010 DS:  ES:  CR0: 80050033
  [   15.411159] CR2: 7f027620d048 CR3: da851000 CR4: 
06e0
  [   15.428200] Stack:
  [   15.428200]  880036a15b78 816f0ac8 8800d8ea18e8 
0adc
  [   15.430445]  81cda780 06ff880036a15fd8 880036a15ba4 
8800d9bfa6c0
  [   15.430673]  8800dbbb94e8 8800d9bfada0 0020 
8800d96126c0
  [   15.433514] Call Trace:
  [   15.433514]  [] ? inet6_csk_route_socket+0x128/0x200
  [   15.433514]  [] inet6_csk_xmit+0x7d/0xd0
  [   15.433514]  [] tcp_transmit_skb+0x469/0x8d0
  [   15.433514]  [] tcp_write_xmit+0x140/0xb10
  [   15.433514]  [] ? tcp_current_mss+0x54/0x80
  [   15.433514]  [] tcp_push_one+0x30/0x40
  [   15.433514]  [] tcp_sendmsg+0x4e1/0xdb0
  [   15.433514]  [] inet_sendmsg+0x64/0xb0
  [   15.433514]  [] ? apparmor_socket_sendmsg+0x17/0x20
  [   15.433514]  [] sock_aio_write+0xfe/0x130
  [   15.433514]  [] do_sync_write+0x5a/0x90
  [   15.433514]  [] vfs_write+0x1ad/0x1f0
  [   15.433514]  [] SyS_write+0x49/0xa0
  [   15.433514]  [] ? SyS_poll+0x65/0x100
  [   15.433514]  [] system_call_fastpath+0x1a/0x1f
  [   15.433514] Code: 49 8b 45 20 ff 50 20 39 43 68 77 6d 48 8b 43 58 48 83 e0 
fe 48 8b 80 48 01 00 00 48 85 c0 0f 84 51 02 00 00 48 8b 80 68 02 00 00 <65> 48 
ff 40 28 8b 53 68 65 48 01 50 30 48 8b 44 24 20 48 8b 80 
  [   15.433514] RIP  [] ip6_xmit+0x1a2/0x410
  [   15.433514]  RSP 

  Here's it the output from crash:

KERNEL: /usr/lib/debug/boot/vmlinux-3.13.0-43-generic
  DUMPFILE: /var/crash/201412191519/dump.201412191519  [PARTIAL DUMP]
  CPUS: 4
  DATE: Fri Dec 19 15:19:18 2014
UPTIME: 00:00:15
  LOAD AVERAGE: 0.58, 0.13, 0.04
 TASKS: 229
  NODENAME: tamriel
   RELEASE: 3.13.0-43-generic
   VERSION: #72-Ubuntu SMP Mon Dec 8 19:35:06 UTC 2014
   MACHINE: x86_64  (2700 Mhz)
MEMORY: 4 GB
 PANIC: ""
   PID: 2398
   COMMAND: "smtp"
  TASK: 8800d8776000  [THREAD_INFO: 880036a14000]
   CPU: 3
 STATE: TASK_RUNNING (PANIC)

  Probably not really interesting, but here's the lspci -vnvn output:

  00:00.0 Host bridge [0600]: Intel Corporation 440FX - 82441FX PMC [Natoma] 
[8086:1237] (rev 02)
  Subsystem: Red Hat, Inc Qemu virtual machine [1af4:1100]
  Control: I/O+ Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR+ FastB2B- DisINTx-
  Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- 
SERR- TAbort- 
SERR- TAbort- 
SERR- TAbort- 
SERR- TA

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

[Stephen Frost]

apport information

** Attachment added: "Lspci.txt"
   https://bugs.launchpad.net/bugs/1404374/+attachment/4284388/+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/1404374

Title:
  Apparently ipv6-related crash in Linux version 3.13.0-43-generic
  (buildd@tipua) (gcc version 4.8.2 (Ubuntu 4.8.2-19ubuntu 1) )
  #72-Ubuntu SMP Mon Dec 8 19:35:06 UTC 2014 (Ubuntu
  3.13.0-43.72-generic 3.13.11.11)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I'm on OFTC and Freenode as Snow-Man if folks want to chat further or
  if there's anything I can run with 'crash' to provide additional
  information.

  This is a KVM guest running under a physical box which is running the
  same kernel (43.72)

  I've downgraded the KVM guest to Linux tamriel 3.13.0-40-generic
  #69-Ubuntu SMP Thu Nov 13 17:53:56 UTC 2014 x86_64 x86_64 x86_64
  GNU/Linux; hopefully this will be stable but I'll report back if it's
  not.  Other guests are running the 43.72 kernel and have not crashed,
  but most are single-cpu while the guest which is crashing is 4-cpu.

  I have crash installed and a dump file.  Here is the dmesg output from
  the crash:

  [   15.407890] general protection fault:  [#1] SMP 
  [   15.411159] Modules linked in: ttm drm_kms_helper kvm_amd drm kvm 
syscopyarea sysfillrect sysimgblt i2c_piix4 serio_raw lp mac_hid parport 
psmouse floppy virtio_scsi
  [   15.411159] CPU: 3 PID: 2398 Comm: smtp Not tainted 3.13.0-43-generic 
#72-Ubuntu
  [   15.411159] Hardware name: Bochs Bochs, BIOS Bochs 01/01/2011
  [   15.411159] task: 8800d8776000 ti: 880036a14000 task.ti: 
880036a14000
  [   15.411159] RIP: 0010:[]  [] 
ip6_xmit+0x1a2/0x410
  [   15.411159] RSP: 0018:880036a15b18  EFLAGS: 00010286
  [   15.411159] RAX: 5709 RBX: 8800dbbb94e8 RCX: 
0001
  [   15.411159] RDX: 8189cc00 RSI: 0028 RDI: 
8800d96126c0
  [   15.411159] RBP: 880036a15b78 R08:  R09: 
000165d6
  [   15.411159] R10:  R11:  R12: 
8800d9bfa6c0
  [   15.411159] R13: 8800d96126c0 R14: 0060 R15: 
880036a15b90
  [   15.411159] FS:  7f02749c3740() GS:88011fd8() 
knlGS:
  [   15.411159] CS:  0010 DS:  ES:  CR0: 80050033
  [   15.411159] CR2: 7f027620d048 CR3: da851000 CR4: 
06e0
  [   15.428200] Stack:
  [   15.428200]  880036a15b78 816f0ac8 8800d8ea18e8 
0adc
  [   15.430445]  81cda780 06ff880036a15fd8 880036a15ba4 
8800d9bfa6c0
  [   15.430673]  8800dbbb94e8 8800d9bfada0 0020 
8800d96126c0
  [   15.433514] Call Trace:
  [   15.433514]  [] ? inet6_csk_route_socket+0x128/0x200
  [   15.433514]  [] inet6_csk_xmit+0x7d/0xd0
  [   15.433514]  [] tcp_transmit_skb+0x469/0x8d0
  [   15.433514]  [] tcp_write_xmit+0x140/0xb10
  [   15.433514]  [] ? tcp_current_mss+0x54/0x80
  [   15.433514]  [] tcp_push_one+0x30/0x40
  [   15.433514]  [] tcp_sendmsg+0x4e1/0xdb0
  [   15.433514]  [] inet_sendmsg+0x64/0xb0
  [   15.433514]  [] ? apparmor_socket_sendmsg+0x17/0x20
  [   15.433514]  [] sock_aio_write+0xfe/0x130
  [   15.433514]  [] do_sync_write+0x5a/0x90
  [   15.433514]  [] vfs_write+0x1ad/0x1f0
  [   15.433514]  [] SyS_write+0x49/0xa0
  [   15.433514]  [] ? SyS_poll+0x65/0x100
  [   15.433514]  [] system_call_fastpath+0x1a/0x1f
  [   15.433514] Code: 49 8b 45 20 ff 50 20 39 43 68 77 6d 48 8b 43 58 48 83 e0 
fe 48 8b 80 48 01 00 00 48 85 c0 0f 84 51 02 00 00 48 8b 80 68 02 00 00 <65> 48 
ff 40 28 8b 53 68 65 48 01 50 30 48 8b 44 24 20 48 8b 80 
  [   15.433514] RIP  [] ip6_xmit+0x1a2/0x410
  [   15.433514]  RSP 

  Here's it the output from crash:

KERNEL: /usr/lib/debug/boot/vmlinux-3.13.0-43-generic
  DUMPFILE: /var/crash/201412191519/dump.201412191519  [PARTIAL DUMP]
  CPUS: 4
  DATE: Fri Dec 19 15:19:18 2014
UPTIME: 00:00:15
  LOAD AVERAGE: 0.58, 0.13, 0.04
 TASKS: 229
  NODENAME: tamriel
   RELEASE: 3.13.0-43-generic
   VERSION: #72-Ubuntu SMP Mon Dec 8 19:35:06 UTC 2014
   MACHINE: x86_64  (2700 Mhz)
MEMORY: 4 GB
 PANIC: ""
   PID: 2398
   COMMAND: "smtp"
  TASK: 8800d8776000  [THREAD_INFO: 880036a14000]
   CPU: 3
 STATE: TASK_RUNNING (PANIC)

  Probably not really interesting, but here's the lspci -vnvn output:

  00:00.0 Host bridge [0600]: Intel Corporation 440FX - 82441FX PMC [Natoma] 
[8086:1237] (rev 02)
  Subsystem: Red Hat, Inc Qemu virtual machine [1af4:1100]
  Control: I/O+ Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR+ FastB2B- DisINTx-
  Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- 
SERR- TAbort- 
SERR- TAbort- 
SERR- TAbort- 
SERR- TAbort-

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

[Stephen Frost]

apport information

** Attachment added: "ProcInterrupts.txt"
   
https://bugs.launchpad.net/bugs/1404374/+attachment/4284390/+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/1404374

Title:
  Apparently ipv6-related crash in Linux version 3.13.0-43-generic
  (buildd@tipua) (gcc version 4.8.2 (Ubuntu 4.8.2-19ubuntu 1) )
  #72-Ubuntu SMP Mon Dec 8 19:35:06 UTC 2014 (Ubuntu
  3.13.0-43.72-generic 3.13.11.11)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I'm on OFTC and Freenode as Snow-Man if folks want to chat further or
  if there's anything I can run with 'crash' to provide additional
  information.

  This is a KVM guest running under a physical box which is running the
  same kernel (43.72)

  I've downgraded the KVM guest to Linux tamriel 3.13.0-40-generic
  #69-Ubuntu SMP Thu Nov 13 17:53:56 UTC 2014 x86_64 x86_64 x86_64
  GNU/Linux; hopefully this will be stable but I'll report back if it's
  not.  Other guests are running the 43.72 kernel and have not crashed,
  but most are single-cpu while the guest which is crashing is 4-cpu.

  I have crash installed and a dump file.  Here is the dmesg output from
  the crash:

  [   15.407890] general protection fault:  [#1] SMP 
  [   15.411159] Modules linked in: ttm drm_kms_helper kvm_amd drm kvm 
syscopyarea sysfillrect sysimgblt i2c_piix4 serio_raw lp mac_hid parport 
psmouse floppy virtio_scsi
  [   15.411159] CPU: 3 PID: 2398 Comm: smtp Not tainted 3.13.0-43-generic 
#72-Ubuntu
  [   15.411159] Hardware name: Bochs Bochs, BIOS Bochs 01/01/2011
  [   15.411159] task: 8800d8776000 ti: 880036a14000 task.ti: 
880036a14000
  [   15.411159] RIP: 0010:[]  [] 
ip6_xmit+0x1a2/0x410
  [   15.411159] RSP: 0018:880036a15b18  EFLAGS: 00010286
  [   15.411159] RAX: 5709 RBX: 8800dbbb94e8 RCX: 
0001
  [   15.411159] RDX: 8189cc00 RSI: 0028 RDI: 
8800d96126c0
  [   15.411159] RBP: 880036a15b78 R08:  R09: 
000165d6
  [   15.411159] R10:  R11:  R12: 
8800d9bfa6c0
  [   15.411159] R13: 8800d96126c0 R14: 0060 R15: 
880036a15b90
  [   15.411159] FS:  7f02749c3740() GS:88011fd8() 
knlGS:
  [   15.411159] CS:  0010 DS:  ES:  CR0: 80050033
  [   15.411159] CR2: 7f027620d048 CR3: da851000 CR4: 
06e0
  [   15.428200] Stack:
  [   15.428200]  880036a15b78 816f0ac8 8800d8ea18e8 
0adc
  [   15.430445]  81cda780 06ff880036a15fd8 880036a15ba4 
8800d9bfa6c0
  [   15.430673]  8800dbbb94e8 8800d9bfada0 0020 
8800d96126c0
  [   15.433514] Call Trace:
  [   15.433514]  [] ? inet6_csk_route_socket+0x128/0x200
  [   15.433514]  [] inet6_csk_xmit+0x7d/0xd0
  [   15.433514]  [] tcp_transmit_skb+0x469/0x8d0
  [   15.433514]  [] tcp_write_xmit+0x140/0xb10
  [   15.433514]  [] ? tcp_current_mss+0x54/0x80
  [   15.433514]  [] tcp_push_one+0x30/0x40
  [   15.433514]  [] tcp_sendmsg+0x4e1/0xdb0
  [   15.433514]  [] inet_sendmsg+0x64/0xb0
  [   15.433514]  [] ? apparmor_socket_sendmsg+0x17/0x20
  [   15.433514]  [] sock_aio_write+0xfe/0x130
  [   15.433514]  [] do_sync_write+0x5a/0x90
  [   15.433514]  [] vfs_write+0x1ad/0x1f0
  [   15.433514]  [] SyS_write+0x49/0xa0
  [   15.433514]  [] ? SyS_poll+0x65/0x100
  [   15.433514]  [] system_call_fastpath+0x1a/0x1f
  [   15.433514] Code: 49 8b 45 20 ff 50 20 39 43 68 77 6d 48 8b 43 58 48 83 e0 
fe 48 8b 80 48 01 00 00 48 85 c0 0f 84 51 02 00 00 48 8b 80 68 02 00 00 <65> 48 
ff 40 28 8b 53 68 65 48 01 50 30 48 8b 44 24 20 48 8b 80 
  [   15.433514] RIP  [] ip6_xmit+0x1a2/0x410
  [   15.433514]  RSP 

  Here's it the output from crash:

KERNEL: /usr/lib/debug/boot/vmlinux-3.13.0-43-generic
  DUMPFILE: /var/crash/201412191519/dump.201412191519  [PARTIAL DUMP]
  CPUS: 4
  DATE: Fri Dec 19 15:19:18 2014
UPTIME: 00:00:15
  LOAD AVERAGE: 0.58, 0.13, 0.04
 TASKS: 229
  NODENAME: tamriel
   RELEASE: 3.13.0-43-generic
   VERSION: #72-Ubuntu SMP Mon Dec 8 19:35:06 UTC 2014
   MACHINE: x86_64  (2700 Mhz)
MEMORY: 4 GB
 PANIC: ""
   PID: 2398
   COMMAND: "smtp"
  TASK: 8800d8776000  [THREAD_INFO: 880036a14000]
   CPU: 3
 STATE: TASK_RUNNING (PANIC)

  Probably not really interesting, but here's the lspci -vnvn output:

  00:00.0 Host bridge [0600]: Intel Corporation 440FX - 82441FX PMC [Natoma] 
[8086:1237] (rev 02)
  Subsystem: Red Hat, Inc Qemu virtual machine [1af4:1100]
  Control: I/O+ Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR+ FastB2B- DisINTx-
  Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- 
SERR- TAbort- 
SERR- TAbort- 
SERR- TAb

[Kernel-packages] [Bug 1404374] Re: Apparently ipv6-related crash in Linux version 3.13.0-43-generic (buildd@tipua) (gcc version 4.8.2 (Ubuntu 4.8.2-19ubuntu 1) ) #72-Ubuntu SMP Mon Dec 8 19:35:06 UTC

[Stephen Frost]

apport information

** Tags added: apport-collected

** Description changed:

  I'm on OFTC and Freenode as Snow-Man if folks want to chat further or if
  there's anything I can run with 'crash' to provide additional
  information.
  
  This is a KVM guest running under a physical box which is running the
  same kernel (43.72)
  
  I've downgraded the KVM guest to Linux tamriel 3.13.0-40-generic
  #69-Ubuntu SMP Thu Nov 13 17:53:56 UTC 2014 x86_64 x86_64 x86_64
  GNU/Linux; hopefully this will be stable but I'll report back if it's
  not.  Other guests are running the 43.72 kernel and have not crashed,
  but most are single-cpu while the guest which is crashing is 4-cpu.
  
  I have crash installed and a dump file.  Here is the dmesg output from
  the crash:
  
  [   15.407890] general protection fault:  [#1] SMP 
  [   15.411159] Modules linked in: ttm drm_kms_helper kvm_amd drm kvm 
syscopyarea sysfillrect sysimgblt i2c_piix4 serio_raw lp mac_hid parport 
psmouse floppy virtio_scsi
  [   15.411159] CPU: 3 PID: 2398 Comm: smtp Not tainted 3.13.0-43-generic 
#72-Ubuntu
  [   15.411159] Hardware name: Bochs Bochs, BIOS Bochs 01/01/2011
  [   15.411159] task: 8800d8776000 ti: 880036a14000 task.ti: 
880036a14000
  [   15.411159] RIP: 0010:[]  [] 
ip6_xmit+0x1a2/0x410
  [   15.411159] RSP: 0018:880036a15b18  EFLAGS: 00010286
  [   15.411159] RAX: 5709 RBX: 8800dbbb94e8 RCX: 
0001
  [   15.411159] RDX: 8189cc00 RSI: 0028 RDI: 
8800d96126c0
  [   15.411159] RBP: 880036a15b78 R08:  R09: 
000165d6
  [   15.411159] R10:  R11:  R12: 
8800d9bfa6c0
  [   15.411159] R13: 8800d96126c0 R14: 0060 R15: 
880036a15b90
  [   15.411159] FS:  7f02749c3740() GS:88011fd8() 
knlGS:
  [   15.411159] CS:  0010 DS:  ES:  CR0: 80050033
  [   15.411159] CR2: 7f027620d048 CR3: da851000 CR4: 
06e0
  [   15.428200] Stack:
  [   15.428200]  880036a15b78 816f0ac8 8800d8ea18e8 
0adc
  [   15.430445]  81cda780 06ff880036a15fd8 880036a15ba4 
8800d9bfa6c0
  [   15.430673]  8800dbbb94e8 8800d9bfada0 0020 
8800d96126c0
  [   15.433514] Call Trace:
  [   15.433514]  [] ? inet6_csk_route_socket+0x128/0x200
  [   15.433514]  [] inet6_csk_xmit+0x7d/0xd0
  [   15.433514]  [] tcp_transmit_skb+0x469/0x8d0
  [   15.433514]  [] tcp_write_xmit+0x140/0xb10
  [   15.433514]  [] ? tcp_current_mss+0x54/0x80
  [   15.433514]  [] tcp_push_one+0x30/0x40
  [   15.433514]  [] tcp_sendmsg+0x4e1/0xdb0
  [   15.433514]  [] inet_sendmsg+0x64/0xb0
  [   15.433514]  [] ? apparmor_socket_sendmsg+0x17/0x20
  [   15.433514]  [] sock_aio_write+0xfe/0x130
  [   15.433514]  [] do_sync_write+0x5a/0x90
  [   15.433514]  [] vfs_write+0x1ad/0x1f0
  [   15.433514]  [] SyS_write+0x49/0xa0
  [   15.433514]  [] ? SyS_poll+0x65/0x100
  [   15.433514]  [] system_call_fastpath+0x1a/0x1f
  [   15.433514] Code: 49 8b 45 20 ff 50 20 39 43 68 77 6d 48 8b 43 58 48 83 e0 
fe 48 8b 80 48 01 00 00 48 85 c0 0f 84 51 02 00 00 48 8b 80 68 02 00 00 <65> 48 
ff 40 28 8b 53 68 65 48 01 50 30 48 8b 44 24 20 48 8b 80 
  [   15.433514] RIP  [] ip6_xmit+0x1a2/0x410
  [   15.433514]  RSP 
  
  Here's it the output from crash:
  
KERNEL: /usr/lib/debug/boot/vmlinux-3.13.0-43-generic
  DUMPFILE: /var/crash/201412191519/dump.201412191519  [PARTIAL DUMP]
  CPUS: 4
  DATE: Fri Dec 19 15:19:18 2014
UPTIME: 00:00:15
  LOAD AVERAGE: 0.58, 0.13, 0.04
 TASKS: 229
  NODENAME: tamriel
   RELEASE: 3.13.0-43-generic
   VERSION: #72-Ubuntu SMP Mon Dec 8 19:35:06 UTC 2014
   MACHINE: x86_64  (2700 Mhz)
MEMORY: 4 GB
 PANIC: ""
   PID: 2398
   COMMAND: "smtp"
  TASK: 8800d8776000  [THREAD_INFO: 880036a14000]
   CPU: 3
 STATE: TASK_RUNNING (PANIC)
  
  Probably not really interesting, but here's the lspci -vnvn output:
  
  00:00.0 Host bridge [0600]: Intel Corporation 440FX - 82441FX PMC [Natoma] 
[8086:1237] (rev 02)
  Subsystem: Red Hat, Inc Qemu virtual machine [1af4:1100]
  Control: I/O+ Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR+ FastB2B- DisINTx-
  Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- 
SERR- TAbort- 
SERR- TAbort- 
SERR- TAbort- 
SERR- TAbort- 
SERR- TAbort- 
SERR- TAbort- 
SERR- TAbort- 
SERR- TAbort- 
SERR- TAbort- 
SERR- TAbort- 
SERR- TAbort- 
SERR- TAbort- 
SERR- TAbort- 
SERR- TAbort- 
SERR- TAbort- 
SERR- TAbort- 
SERR- TAbort- 
SERR- 
+  LANG=en_US.UTF-8
+  SHELL=/bin/bash
+ ProcFB:
+  
+ ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-40-generic 
root=/dev/mapper/hostname--vg-root ro nomodeset crashkernel=384M-:128M
+ ProcVersionSignature: Ubuntu 3.13.0-40.69-generic 3.13.11.10
+ RelatedPackageVersions:
+  linux-restricted-

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

[Brad Figg]

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

apport-collect 1404374

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

** Tags added: trusty

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

Title:
  Apparently ipv6-related crash in Linux version 3.13.0-43-generic
  (buildd@tipua) (gcc version 4.8.2 (Ubuntu 4.8.2-19ubuntu 1) )
  #72-Ubuntu SMP Mon Dec 8 19:35:06 UTC 2014 (Ubuntu
  3.13.0-43.72-generic 3.13.11.11)

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I'm on OFTC and Freenode as Snow-Man if folks want to chat further or
  if there's anything I can run with 'crash' to provide additional
  information.

  This is a KVM guest running under a physical box which is running the
  same kernel (43.72)

  I've downgraded the KVM guest to Linux tamriel 3.13.0-40-generic
  #69-Ubuntu SMP Thu Nov 13 17:53:56 UTC 2014 x86_64 x86_64 x86_64
  GNU/Linux; hopefully this will be stable but I'll report back if it's
  not.  Other guests are running the 43.72 kernel and have not crashed,
  but most are single-cpu while the guest which is crashing is 4-cpu.

  I have crash installed and a dump file.  Here is the dmesg output from
  the crash:

  [   15.407890] general protection fault:  [#1] SMP 
  [   15.411159] Modules linked in: ttm drm_kms_helper kvm_amd drm kvm 
syscopyarea sysfillrect sysimgblt i2c_piix4 serio_raw lp mac_hid parport 
psmouse floppy virtio_scsi
  [   15.411159] CPU: 3 PID: 2398 Comm: smtp Not tainted 3.13.0-43-generic 
#72-Ubuntu
  [   15.411159] Hardware name: Bochs Bochs, BIOS Bochs 01/01/2011
  [   15.411159] task: 8800d8776000 ti: 880036a14000 task.ti: 
880036a14000
  [   15.411159] RIP: 0010:[]  [] 
ip6_xmit+0x1a2/0x410
  [   15.411159] RSP: 0018:880036a15b18  EFLAGS: 00010286
  [   15.411159] RAX: 5709 RBX: 8800dbbb94e8 RCX: 
0001
  [   15.411159] RDX: 8189cc00 RSI: 0028 RDI: 
8800d96126c0
  [   15.411159] RBP: 880036a15b78 R08:  R09: 
000165d6
  [   15.411159] R10:  R11:  R12: 
8800d9bfa6c0
  [   15.411159] R13: 8800d96126c0 R14: 0060 R15: 
880036a15b90
  [   15.411159] FS:  7f02749c3740() GS:88011fd8() 
knlGS:
  [   15.411159] CS:  0010 DS:  ES:  CR0: 80050033
  [   15.411159] CR2: 7f027620d048 CR3: da851000 CR4: 
06e0
  [   15.428200] Stack:
  [   15.428200]  880036a15b78 816f0ac8 8800d8ea18e8 
0adc
  [   15.430445]  81cda780 06ff880036a15fd8 880036a15ba4 
8800d9bfa6c0
  [   15.430673]  8800dbbb94e8 8800d9bfada0 0020 
8800d96126c0
  [   15.433514] Call Trace:
  [   15.433514]  [] ? inet6_csk_route_socket+0x128/0x200
  [   15.433514]  [] inet6_csk_xmit+0x7d/0xd0
  [   15.433514]  [] tcp_transmit_skb+0x469/0x8d0
  [   15.433514]  [] tcp_write_xmit+0x140/0xb10
  [   15.433514]  [] ? tcp_current_mss+0x54/0x80
  [   15.433514]  [] tcp_push_one+0x30/0x40
  [   15.433514]  [] tcp_sendmsg+0x4e1/0xdb0
  [   15.433514]  [] inet_sendmsg+0x64/0xb0
  [   15.433514]  [] ? apparmor_socket_sendmsg+0x17/0x20
  [   15.433514]  [] sock_aio_write+0xfe/0x130
  [   15.433514]  [] do_sync_write+0x5a/0x90
  [   15.433514]  [] vfs_write+0x1ad/0x1f0
  [   15.433514]  [] SyS_write+0x49/0xa0
  [   15.433514]  [] ? SyS_poll+0x65/0x100
  [   15.433514]  [] system_call_fastpath+0x1a/0x1f
  [   15.433514] Code: 49 8b 45 20 ff 50 20 39 43 68 77 6d 48 8b 43 58 48 83 e0 
fe 48 8b 80 48 01 00 00 48 85 c0 0f 84 51 02 00 00 48 8b 80 68 02 00 00 <65> 48 
ff 40 28 8b 53 68 65 48 01 50 30 48 8b 44 24 20 48 8b 80 
  [   15.433514] RIP  [] ip6_xmit+0x1a2/0x410
  [   15.433514]  RSP 

  Here's it the output from crash:

KERNEL: /usr/lib/debug/boot/vmlinux-3.13.0-43-generic
  DUMPFILE: /var/crash/201412191519/dump.201412191519  [PARTIAL DUMP]
  CPUS: 4
  DATE: Fri Dec 19 15:19:18 2014
UPTIME: 00:00:15
  LOAD AVERAGE: 0.58, 0.13, 0.04
 TASKS: 229
  NODENAME: tamriel
   RELEASE: 3.13.0-43-generic
   VERSION: #72-Ubuntu SMP Mon Dec 8 19:35:06 UTC 2014
   MACHINE: x86_64  (2700 Mhz)
MEMORY: 4 GB
 PANIC: ""
   PID: 2398
   COMMAND: "smtp"
  TASK: 8800d8776000  [THREAD_INFO: 880036a14000]
   CPU: 3
 STATE: TASK_RUNNING (PANIC)

  Probably not really interesting, but here's the lspci -vnvn output:

  00:0

[Kernel-packages] [Bug 1404374] [NEW] Apparently ipv6-related crash in Linux version 3.13.0-43-generic (buildd@tipua) (gcc version 4.8.2 (Ubuntu 4.8.2-19ubuntu 1) ) #72-Ubuntu SMP Mon Dec 8 19:35:06 U

[Stephen Frost]

Public bug reported:

I'm on OFTC and Freenode as Snow-Man if folks want to chat further or if
there's anything I can run with 'crash' to provide additional
information.

This is a KVM guest running under a physical box which is running the
same kernel (43.72)

I've downgraded the KVM guest to Linux tamriel 3.13.0-40-generic
#69-Ubuntu SMP Thu Nov 13 17:53:56 UTC 2014 x86_64 x86_64 x86_64
GNU/Linux; hopefully this will be stable but I'll report back if it's
not.  Other guests are running the 43.72 kernel and have not crashed,
but most are single-cpu while the guest which is crashing is 4-cpu.

I have crash installed and a dump file.  Here is the dmesg output from
the crash:

[   15.407890] general protection fault:  [#1] SMP 
[   15.411159] Modules linked in: ttm drm_kms_helper kvm_amd drm kvm 
syscopyarea sysfillrect sysimgblt i2c_piix4 serio_raw lp mac_hid parport 
psmouse floppy virtio_scsi
[   15.411159] CPU: 3 PID: 2398 Comm: smtp Not tainted 3.13.0-43-generic 
#72-Ubuntu
[   15.411159] Hardware name: Bochs Bochs, BIOS Bochs 01/01/2011
[   15.411159] task: 8800d8776000 ti: 880036a14000 task.ti: 
880036a14000
[   15.411159] RIP: 0010:[]  [] 
ip6_xmit+0x1a2/0x410
[   15.411159] RSP: 0018:880036a15b18  EFLAGS: 00010286
[   15.411159] RAX: 5709 RBX: 8800dbbb94e8 RCX: 0001
[   15.411159] RDX: 8189cc00 RSI: 0028 RDI: 8800d96126c0
[   15.411159] RBP: 880036a15b78 R08:  R09: 000165d6
[   15.411159] R10:  R11:  R12: 8800d9bfa6c0
[   15.411159] R13: 8800d96126c0 R14: 0060 R15: 880036a15b90
[   15.411159] FS:  7f02749c3740() GS:88011fd8() 
knlGS:
[   15.411159] CS:  0010 DS:  ES:  CR0: 80050033
[   15.411159] CR2: 7f027620d048 CR3: da851000 CR4: 06e0
[   15.428200] Stack:
[   15.428200]  880036a15b78 816f0ac8 8800d8ea18e8 
0adc
[   15.430445]  81cda780 06ff880036a15fd8 880036a15ba4 
8800d9bfa6c0
[   15.430673]  8800dbbb94e8 8800d9bfada0 0020 
8800d96126c0
[   15.433514] Call Trace:
[   15.433514]  [] ? inet6_csk_route_socket+0x128/0x200
[   15.433514]  [] inet6_csk_xmit+0x7d/0xd0
[   15.433514]  [] tcp_transmit_skb+0x469/0x8d0
[   15.433514]  [] tcp_write_xmit+0x140/0xb10
[   15.433514]  [] ? tcp_current_mss+0x54/0x80
[   15.433514]  [] tcp_push_one+0x30/0x40
[   15.433514]  [] tcp_sendmsg+0x4e1/0xdb0
[   15.433514]  [] inet_sendmsg+0x64/0xb0
[   15.433514]  [] ? apparmor_socket_sendmsg+0x17/0x20
[   15.433514]  [] sock_aio_write+0xfe/0x130
[   15.433514]  [] do_sync_write+0x5a/0x90
[   15.433514]  [] vfs_write+0x1ad/0x1f0
[   15.433514]  [] SyS_write+0x49/0xa0
[   15.433514]  [] ? SyS_poll+0x65/0x100
[   15.433514]  [] system_call_fastpath+0x1a/0x1f
[   15.433514] Code: 49 8b 45 20 ff 50 20 39 43 68 77 6d 48 8b 43 58 48 83 e0 
fe 48 8b 80 48 01 00 00 48 85 c0 0f 84 51 02 00 00 48 8b 80 68 02 00 00 <65> 48 
ff 40 28 8b 53 68 65 48 01 50 30 48 8b 44 24 20 48 8b 80 
[   15.433514] RIP  [] ip6_xmit+0x1a2/0x410
[   15.433514]  RSP 

Here's it the output from crash:

  KERNEL: /usr/lib/debug/boot/vmlinux-3.13.0-43-generic
DUMPFILE: /var/crash/201412191519/dump.201412191519  [PARTIAL DUMP]
CPUS: 4
DATE: Fri Dec 19 15:19:18 2014
  UPTIME: 00:00:15
LOAD AVERAGE: 0.58, 0.13, 0.04
   TASKS: 229
NODENAME: tamriel
 RELEASE: 3.13.0-43-generic
 VERSION: #72-Ubuntu SMP Mon Dec 8 19:35:06 UTC 2014
 MACHINE: x86_64  (2700 Mhz)
  MEMORY: 4 GB
   PANIC: ""
 PID: 2398
 COMMAND: "smtp"
TASK: 8800d8776000  [THREAD_INFO: 880036a14000]
 CPU: 3
   STATE: TASK_RUNNING (PANIC)

Probably not really interesting, but here's the lspci -vnvn output:

00:00.0 Host bridge [0600]: Intel Corporation 440FX - 82441FX PMC [Natoma] 
[8086:1237] (rev 02)
Subsystem: Red Hat, Inc Qemu virtual machine [1af4:1100]
Control: I/O+ Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR+ FastB2B- DisINTx-
Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- 
SERR- TAbort- 
SERR- TAbort- SERR- TAbort- 
SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- 
SERR- TAbort- 
SERR- TAbort- SERR- TAbort- 
SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- https://bugs.launchpad.net/bugs/1404374

Title:
  Apparently ipv6-related crash in Linux version 3.13.0-43-generic
  (buildd@tipua) (gcc version 4.8.2 (Ubuntu 4.8.2-19ubuntu 1) )
  #72-Ubuntu SMP Mon Dec 8 19:35:06 UTC 2014 (Ubuntu
  3.13.0-43.72-generic 3.13.11.11)

Status in linux package in Ubuntu:
  New

Bug description:
  I'm on OFTC and Freenode as Snow-Man if folks want to chat further or
  if there's anything I can run with 'crash' to provide additional
  information.

  This is a KVM guest running under a physical box

[Kernel-packages] [Bug 1335478] Re: A new instance of IBM Domino 'bindsock' cannot bind to ports <1024 Kernel 3.13.0-29 and above

[Kit Davis]

** Tags removed: verification-needed-utopic
** Tags added: verification-done-utopic

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

Title:
  A new instance of IBM Domino 'bindsock' cannot bind to ports <1024
  Kernel  3.13.0-29 and above

Status in linux package in Ubuntu:
  Fix Committed
Status in linux-lts-trusty package in Ubuntu:
  Invalid
Status in linux-lts-utopic package in Ubuntu:
  Invalid
Status in linux source package in Lucid:
  Fix Committed
Status in linux-lts-trusty source package in Lucid:
  Invalid
Status in linux-lts-utopic source package in Lucid:
  Invalid
Status in linux source package in Precise:
  Fix Committed
Status in linux-lts-trusty source package in Precise:
  Fix Committed
Status in linux-lts-utopic source package in Precise:
  Invalid
Status in linux source package in Trusty:
  Fix Committed
Status in linux-lts-trusty source package in Trusty:
  Invalid
Status in linux-lts-utopic source package in Trusty:
  Fix Committed
Status in linux source package in Utopic:
  Fix Committed
Status in linux-lts-trusty source package in Utopic:
  Invalid
Status in linux-lts-utopic source package in Utopic:
  Invalid
Status in linux source package in Vivid:
  Fix Committed
Status in linux-lts-trusty source package in Vivid:
  Invalid
Status in linux-lts-utopic source package in Vivid:
  Invalid

Bug description:
  Starting  with kernels  3.2.0-64 and 3.13.0-29  Something has changed
  to once again that prevents IBM Domino's
  "/opt/ibm/domino/notes/latest/linux/bindsock" binary that runs as root
  (setuid) to get ports lower than 1024 for it's LDAP, SMTP, IMAP, POP3,
  and HTTP processes.

  The Domino server reports  the following: :
    "Listener failure: 'bindsock' is missing, not executable, not owned by 
root, not setuid root or user needs net_privaddr privilege."

  This is the same behaviour that was reported and subsequently
  corrected in Bug # 1269053

  ===
  break-fix: dbb490b96584d4e958533fb637f08b557f505657 
6a2a2b3ae0759843b22c929881cc184b00cc63ff

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1335478/+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 1335478] Re: A new instance of IBM Domino 'bindsock' cannot bind to ports <1024 Kernel 3.13.0-29 and above

[Ben Erickson]

I have also tested kernel 3.13.0-44 on Trusty-Proposed and it solves the
bug. I have modified the tag verification-needed-trusty to verification-
done-trusty.

** Tags removed: verification-needed-trusty
** Tags added: verification-done-trusty

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

Title:
  A new instance of IBM Domino 'bindsock' cannot bind to ports <1024
  Kernel  3.13.0-29 and above

Status in linux package in Ubuntu:
  Fix Committed
Status in linux-lts-trusty package in Ubuntu:
  Invalid
Status in linux-lts-utopic package in Ubuntu:
  Invalid
Status in linux source package in Lucid:
  Fix Committed
Status in linux-lts-trusty source package in Lucid:
  Invalid
Status in linux-lts-utopic source package in Lucid:
  Invalid
Status in linux source package in Precise:
  Fix Committed
Status in linux-lts-trusty source package in Precise:
  Fix Committed
Status in linux-lts-utopic source package in Precise:
  Invalid
Status in linux source package in Trusty:
  Fix Committed
Status in linux-lts-trusty source package in Trusty:
  Invalid
Status in linux-lts-utopic source package in Trusty:
  Fix Committed
Status in linux source package in Utopic:
  Fix Committed
Status in linux-lts-trusty source package in Utopic:
  Invalid
Status in linux-lts-utopic source package in Utopic:
  Invalid
Status in linux source package in Vivid:
  Fix Committed
Status in linux-lts-trusty source package in Vivid:
  Invalid
Status in linux-lts-utopic source package in Vivid:
  Invalid

Bug description:
  Starting  with kernels  3.2.0-64 and 3.13.0-29  Something has changed
  to once again that prevents IBM Domino's
  "/opt/ibm/domino/notes/latest/linux/bindsock" binary that runs as root
  (setuid) to get ports lower than 1024 for it's LDAP, SMTP, IMAP, POP3,
  and HTTP processes.

  The Domino server reports  the following: :
    "Listener failure: 'bindsock' is missing, not executable, not owned by 
root, not setuid root or user needs net_privaddr privilege."

  This is the same behaviour that was reported and subsequently
  corrected in Bug # 1269053

  ===
  break-fix: dbb490b96584d4e958533fb637f08b557f505657 
6a2a2b3ae0759843b22c929881cc184b00cc63ff

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1335478/+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 1385937] Re: [Acer Travelmate B115-M] Synaptic touchpad not correctly detected in kernel 3.16 after upgrade to Ubuntu 14.10

[holger_p.]

I pulled today's commits from
git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git which
build as kernel 3.18.0 showing still the same issue.

Additionaly I took the opportunity to upgrade my ACER B115's BIOS from V1.22 to 
V1.26. Luckily I had to reset my personal settings back and with this I also 
took a deeper look into the BIOS settings. There I discovered a setting under 
MAIN->TOUCHPAD=ADVANCED. This seems to be the "default" with an additional note 
like: ...take care the I2C driver is loaded first if using advanced setting...
I decided to set this to BASIC instead and since then the Synaptic touchpad is 
recognised UNDER 14.10 as with previous Ubuntu 14.04.

I assume the I2C_HID recognition does not yet work as supposed to since
the dmesg with TOUCHPAD=ADVANCE under 3.16 showed

i2c_hid i2c-SYN1B7D:01: failed to retrieve report from device.

which it does not under the BIOS setting MAIN->TOUCHPAD=BASIC .

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

Title:
  [Acer Travelmate B115-M] Synaptic touchpad not correctly detected in
  kernel 3.16 after upgrade to Ubuntu 14.10

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Since the upgrade from Ubuntu 14.04 to 14.10 the Synaptic touchpad is
  not detected entirely. The secondary key (right mouse button) does not
  work with kernel 3.16.0-23-generic. Falling back under Ubuntu 14.10 to
  the kernel 3.13.0-37-generic the Synaptic touchpad is detected fully
  and right mouse button works again.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: linux-image-3.16.0-23-generic 3.16.0-23.31
  ProcVersionSignature: Ubuntu 3.16.0-23.31-generic 3.16.4
  Uname: Linux 3.16.0-23-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  hpannenb   2336 F pulseaudio
  CurrentDesktop: Unity
  Date: Sun Oct 26 19:45:20 2014
  HibernationDevice: RESUME=UUID=8aa00459-6b0d-4baf-84e4-7f945406d6b2
  InstallationDate: Installed on 2014-10-10 (15 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 1bcf:2c57 Sunplus Innovation Technology Inc. 
   Bus 001 Device 004: ID 0489:e046 Foxconn / Hon Hai 
   Bus 001 Device 002: ID 05e3:0608 Genesys Logic, Inc. Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Acer TravelMate B115-M
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-23-generic.efi.signed 
root=UUID=902f1410-63a6-41f1-893c-ab5e74543832 ro acpi_backlight=vendor quiet 
splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.16.0-23-generic N/A
   linux-backports-modules-3.16.0-23-generic  N/A
   linux-firmware 1.138
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/27/2014
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.22
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: Roxy
  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.22:bd08/27/2014:svnAcer:pnTravelMateB115-M:pvrV1.22:rvnAcer:rnRoxy:rvrType2-A01BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion:
  dmi.product.name: TravelMate B115-M
  dmi.product.version: V1.22
  dmi.sys.vendor: Acer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1385937/+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 1335478] Re: A new instance of IBM Domino 'bindsock' cannot bind to ports <1024 Kernel 3.13.0-29 and above

[Kit Davis]

I've tested the kernel (3.13.0-44) from Trusty-Proposed and it solves
the bug.   I cannot figure out where the tag "verification-needed-
utopic" resides and therefore I can't change the tag to "verification-
done"

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

Title:
  A new instance of IBM Domino 'bindsock' cannot bind to ports <1024
  Kernel  3.13.0-29 and above

Status in linux package in Ubuntu:
  Fix Committed
Status in linux-lts-trusty package in Ubuntu:
  Invalid
Status in linux-lts-utopic package in Ubuntu:
  Invalid
Status in linux source package in Lucid:
  Fix Committed
Status in linux-lts-trusty source package in Lucid:
  Invalid
Status in linux-lts-utopic source package in Lucid:
  Invalid
Status in linux source package in Precise:
  Fix Committed
Status in linux-lts-trusty source package in Precise:
  Fix Committed
Status in linux-lts-utopic source package in Precise:
  Invalid
Status in linux source package in Trusty:
  Fix Committed
Status in linux-lts-trusty source package in Trusty:
  Invalid
Status in linux-lts-utopic source package in Trusty:
  Fix Committed
Status in linux source package in Utopic:
  Fix Committed
Status in linux-lts-trusty source package in Utopic:
  Invalid
Status in linux-lts-utopic source package in Utopic:
  Invalid
Status in linux source package in Vivid:
  Fix Committed
Status in linux-lts-trusty source package in Vivid:
  Invalid
Status in linux-lts-utopic source package in Vivid:
  Invalid

Bug description:
  Starting  with kernels  3.2.0-64 and 3.13.0-29  Something has changed
  to once again that prevents IBM Domino's
  "/opt/ibm/domino/notes/latest/linux/bindsock" binary that runs as root
  (setuid) to get ports lower than 1024 for it's LDAP, SMTP, IMAP, POP3,
  and HTTP processes.

  The Domino server reports  the following: :
    "Listener failure: 'bindsock' is missing, not executable, not owned by 
root, not setuid root or user needs net_privaddr privilege."

  This is the same behaviour that was reported and subsequently
  corrected in Bug # 1269053

  ===
  break-fix: dbb490b96584d4e958533fb637f08b557f505657 
6a2a2b3ae0759843b22c929881cc184b00cc63ff

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1335478/+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 1393317] Re: Intel 7265 [8086:095b] Wireless disconnect automatically

[Simon Déziel]

** Tags removed: verification-needed-trusty
** Tags added: verification-done-trusty

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

Title:
  Intel 7265 [8086:095b] Wireless disconnect automatically

Status in HWE Next Project:
  In Progress
Status in linux package in Ubuntu:
  Fix Committed
Status in linux-firmware package in Ubuntu:
  In Progress
Status in linux source package in Trusty:
  Fix Committed
Status in linux-firmware source package in Trusty:
  Confirmed
Status in linux source package in Utopic:
  Fix Released
Status in linux-firmware source package in Utopic:
  Confirmed

Bug description:
  SRU Justification:

  Impact: Intel's latest wireless adapter will disconnect automatically
  Fix: bump firmware API version to 9(the version 9 firmwares of 3160, 7260 and 
7265 were already in trusty, but need an upgrade from 23.214.9.0 to the latest 
25.222.9.0)
  Testcase: already tested with Intel 7265 [8086:095b] in OEM projects.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1393317/+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 1396338] Re: [Dell Latitude E7440] Wifi keeps dropping with Intel Wireless 7260

[Niels Holmgaard]

Did not disect to the bottom - released version 3.16.0-28 corrects the
problem, so I assume that someone beat me to it.

Fixed and verified over the last few days by switching back and forth
between -25 and -28. Wifi keeps dropping in -25, and stays stable
overnight in -28.

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

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

Title:
  [Dell Latitude E7440] Wifi keeps dropping with Intel Wireless 7260

Status in linux package in Ubuntu:
  Fix Released

Bug description:
  After the connection is dropped, a hardware switch disconnect/connect is 
necessary to re-establish connection, the connection does not automatically 
reappear. The problematic line in the dmesg output is:
  wlan0: deauthenticated from 00:16:b6:01:69:74 (Reason: 
7=CLASS3_FRAME_FROM_NONASSOC_STA)

  
  The frequency of the problem drops considerably moving to a less congested 
channel, but it still happens - I am stationary at about 3 meters from the 
access point. Other devices (Android phones, iPad, other laptops) are 
connecting to the same access point with no problems at all.

  Network controller [0280]: Intel Corporation Wireless 7260 [8086:08b1] (rev 
73)
Subsystem: Intel Corporation Dual Band Wireless-AC 7260 [8086:4470]

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: linux-image-3.16.0-24-generic 3.16.0-24.32
  ProcVersionSignature: Ubuntu 3.16.0-24.32-generic 3.16.4
  Uname: Linux 3.16.0-24-generic x86_64
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  niels  2502 F pulseaudio
   /dev/snd/controlC1:  niels  2502 F pulseaudio
  CurrentDesktop: Unity
  Date: Tue Nov 25 21:24:21 2014
  HibernationDevice: RESUME=UUID=fe0b3838-4f25-4296-a7c7-872862359ccf
  InstallationDate: Installed on 2014-10-16 (40 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  MachineType: Dell Inc. Latitude E7440
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-24-generic 
root=UUID=28b33773-57cd-4cb6-bd65-1c2acadbd079 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.16.0-24-generic N/A
   linux-backports-modules-3.16.0-24-generic  N/A
   linux-firmware 1.138
  SourcePackage: linux
  UpgradeStatus: Upgraded to utopic on 2014-10-25 (31 days ago)
  dmi.bios.date: 06/26/2014
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A10
  dmi.board.name: 03HFCG
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA10:bd06/26/2014:svnDellInc.:pnLatitudeE7440:pvr01:rvnDellInc.:rn03HFCG:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E7440
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1396338/+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 1404335] Re: xgene: BUG: soft lockup - CPU#0 stuck for 23s! [halt:2059] on poweroff

[Craig Magina]

Here is an output from the console of a system experiencing this issue.

This bug occurs after executing "sudo poweroff" and "sudo shutdown -h now" This 
issue was found on trusty-updates and trusty-
proposed. It wasn't seen in the released version.

$ uname -a
Linux am5 3.13.0-37-generic #64-Ubuntu SMP Mon Sep 22 21:32:32 UTC 2014 aarch64 
aarch64 aarch64 GNU/Linux

U-Boot 2013.04-mustang_sw_1.13.28-beta (Aug 25 2014 - 14:16:10)

ubuntu@am5:~$ sudo poweroff

Broadcast message from ubuntu@am5
 (/dev/ttyS0) at 17:33 ...

The system is going down for power off NOW!
ubuntwait-for-state stop/waiting
 * Stopping rsync daemon rsync [ OK ]
 * Asking all remaining processes to terminate... [ OK ]
 * All processes ended within 1 seconds... [ OK ]
 * Deactivating swap... [ OK ]
 * Unmounting local filesystems... [ OK ]
 * Will now halt
[22800.565563] reboot: System halted
[22828.004581] BUG: soft lockup - CPU#0 stuck for 23s! [halt:2059]
[22856.004581] BUG: soft lockup - CPU#0 stuck for 23s! [halt:2059]
[22884.004581] BUG: soft lockup - CPU#0 stuck for 22s! [halt:2059]
[22912.004580] BUG: soft lockup - CPU#0 stuck for 22s! [halt:2059]
[22940.004580] BUG: soft lockup - CPU#0 stuck for 22s! [halt:2059]
[22968.004580] BUG: soft lockup - CPU#0 stuck for 22s! [halt:2059]
[22996.004580] BUG: soft lockup - CPU#0 stuck for 22s! [halt:2059]
[23024.004580] BUG: soft lockup - CPU#0 stuck for 22s! [halt:2059]
[23052.004580] BUG: soft lockup - CPU#0 stuck for 22s! [halt:2059]
[23080.004580] BUG: soft lockup - CPU#0 stuck for 22s! [halt:2059]
[23108.004580] BUG: soft lockup - CPU#0 stuck for 23s! [halt:2059]
[23136.004580] BUG: soft lockup - CPU#0 stuck for 23s! [halt:2059]
[23164.004580] BUG: soft lockup - CPU#0 stuck for 23s! [halt:2059]
[23192.004580] BUG: soft lockup - CPU#0 stuck for 23s! [halt:2059]
[23220.004580] BUG: soft lockup - CPU#0 stuck for 23s! [halt:2059]
[23248.004580] BUG: soft lockup - CPU#0 stuck for 22s! [halt:2059]
[23276.004580] BUG: soft lockup - CPU#0 stuck for 22s! [halt:2059]
[23304.004580] BUG: soft lockup - CPU#0 stuck for 22s! [halt:2059]
[23332.004580] BUG: soft lockup - CPU#0 stuck for 22s! [halt:2059]
[23360.004580] BUG: soft lockup - CPU#0 stuck for 22s! [halt:2059]

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

Title:
  xgene: BUG: soft lockup - CPU#0 stuck for 23s! [halt:2059] on poweroff

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  [Impact]
  Fixes an issue where after the system halts the cpu starts to experience soft 
lockups.

  [Test Case]
  The most reliable means of reproducing this issue is to 'sudo poweroff' the 
system from the console.

  [Regression Potential]
  These patches are upstream patches that have been in the utopic kernel for 
quite a while and only affect the arm64 architecture.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1404335/+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 1401935] Re: [Acer Aspire V3-371] Touchpad stops working after suspend

[Christopher M. Penalver]

reggar, the next step is to fully reverse commit bisect from kernel 3.16
to 3.18.1 in order to identify the last bad commit, followed immediately
by the first good one. Once this commit has been identified, then it may
be reviewed as a candidate for backporting into your release. Could you
please do this following
https://wiki.ubuntu.com/Kernel/KernelBisection#How_do_I_reverse_bisect_the_upstream_kernel.3F
?  Please note, finding adjacent kernel versions is not fully commit
bisecting.

Thank you for your understanding.

Helpful bug reporting tips:
https://wiki.ubuntu.com/ReportingBugs

** Tags added: needs-reverse-bisect

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

Title:
  [Acer Aspire V3-371] Touchpad stops working after suspend

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The touchpad stops working after suspend. From /proc/bus/input/devices:
  I: Bus=0018 Vendor=06cb Product=2991 Version=0100
  N: Name="SYN1B7F:01 06CB:2991 UNKNOWN"
  P: Phys=
  S: 
Sysfs=/devices/pci:00/INT33C3:00/i2c-7/i2c-SYN1B7F:01/0018:06CB:2991.0002/input/input15
  U: Uniq=
  H: Handlers=mouse0 event13
  B: PROP=1
  B: EV=b
  B: KEY=6420 1 0 0 0 0
  B: ABS=2608003

  WORKAROUND: sudo modprobe -r i2c_hid && sudo modprobe i2c_hid

  ---
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  martijn2357 F pulseaudio
   /dev/snd/controlC0:  martijn2357 F pulseaudio
  DistroRelease: Ubuntu 14.10
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2014-12-08 (4 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
  MachineType: Acer Aspire V3-371
  Package: linux (not installed)
  ProcEnviron:
   LANGUAGE=nl
   TERM=xterm
   PATH=(custom, no user)
   LANG=nl_NL.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-28-generic.efi.signed 
root=UUID=c404c12a-11b8-47c7-a6bc-24e7a572025b ro i8042.nomux=1 i8042.reset 
quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.16.0-28.37-generic 3.16.7-ckt1
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-3.16.0-28-generic N/A
   linux-backports-modules-3.16.0-28-generic  N/A
   linux-firmware 1.138
  Tags:  utopic
  Uname: Linux 3.16.0-28-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

  _MarkForUpload: True
  dmi.bios.date: 09/05/2014
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.12
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Aspire V3-371
  dmi.board.vendor: Acer
  dmi.board.version: V1.12
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V1.12
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.12:bd09/05/2014:svnAcer:pnAspireV3-371:pvrV1.12:rvnAcer:rnAspireV3-371:rvrV1.12:cvnAcer:ct10:cvrV1.12:
  dmi.product.name: Aspire V3-371
  dmi.product.version: V1.12
  dmi.sys.vendor: Acer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1401935/+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 1401935] Re: [Acer Aspire V3-371] Touchpad stops working after suspend

[Christopher M. Penalver]

raggar, the next step is to fully reverse commit bisect from kernel 3.16
to 3.18.1 in order to identify the last bad commit, followed immediately
by the first good one. Once this commit has been identified, then it may
be reviewed as a candidate for backporting into your release. Could you
please do this following
https://wiki.ubuntu.com/Kernel/KernelBisection#How_do_I_reverse_bisect_the_upstream_kernel.3F
? Please note, finding adjacent kernel versions is not fully commit
bisecting.

Thank you for your understanding.

Helpful bug reporting tips:
https://wiki.ubuntu.com/ReportingBugs

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

Title:
  [Acer Aspire V3-371] Touchpad stops working after suspend

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The touchpad stops working after suspend. From /proc/bus/input/devices:
  I: Bus=0018 Vendor=06cb Product=2991 Version=0100
  N: Name="SYN1B7F:01 06CB:2991 UNKNOWN"
  P: Phys=
  S: 
Sysfs=/devices/pci:00/INT33C3:00/i2c-7/i2c-SYN1B7F:01/0018:06CB:2991.0002/input/input15
  U: Uniq=
  H: Handlers=mouse0 event13
  B: PROP=1
  B: EV=b
  B: KEY=6420 1 0 0 0 0
  B: ABS=2608003

  WORKAROUND: sudo modprobe -r i2c_hid && sudo modprobe i2c_hid

  ---
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  martijn2357 F pulseaudio
   /dev/snd/controlC0:  martijn2357 F pulseaudio
  DistroRelease: Ubuntu 14.10
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2014-12-08 (4 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
  MachineType: Acer Aspire V3-371
  Package: linux (not installed)
  ProcEnviron:
   LANGUAGE=nl
   TERM=xterm
   PATH=(custom, no user)
   LANG=nl_NL.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-28-generic.efi.signed 
root=UUID=c404c12a-11b8-47c7-a6bc-24e7a572025b ro i8042.nomux=1 i8042.reset 
quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.16.0-28.37-generic 3.16.7-ckt1
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-3.16.0-28-generic N/A
   linux-backports-modules-3.16.0-28-generic  N/A
   linux-firmware 1.138
  Tags:  utopic
  Uname: Linux 3.16.0-28-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

  _MarkForUpload: True
  dmi.bios.date: 09/05/2014
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.12
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Aspire V3-371
  dmi.board.vendor: Acer
  dmi.board.version: V1.12
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V1.12
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.12:bd09/05/2014:svnAcer:pnAspireV3-371:pvrV1.12:rvnAcer:rnAspireV3-371:rvrV1.12:cvnAcer:ct10:cvrV1.12:
  dmi.product.name: Aspire V3-371
  dmi.product.version: V1.12
  dmi.sys.vendor: Acer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1401935/+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 1391476] Re: [MacBookPro11, 1] Laptop wakes up while lid closed

[Christopher M. Penalver]

Erlenmayr, the general issue of resuming from suspend while a closed
laptop is in a jostling bag is one that wouldn't be unique to Ubuntu, as
it affects all hardware and operating systems. I've dealt with folks who
have caused hardware failure to a brand new computer due to this. What
I've done myself, and suggest to others is hibernate instead of suspend.

However, the disabling keyboard wakeup from suspend would be a
fundamental, large scale change that would need to originate upstream,
given the implementation would be hardware dependent, and may require a
hardware quirk list.

This would appear to be a similar, but distinctly different issue then
the one scoped to this report, how you said this is not reproducible in
Trusty. If this still remains true, a bisect would still need to occur
as previously advised.

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

Title:
  [MacBookPro11,1] Laptop wakes up while lid closed

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Same behavior when using pm-suspend. It is hard to notice whether the
  laptop wakes up, especially because that does not always happen
  immediately. Getting to sleep takes up to 30 seconds. Hardware damage
  may be a result of waking up while lid is closed, for example if
  laptop is transported in a bag. I suspect that the problem comes from
  the Intel video driver. See extract from kern.log.

  WORKAROUND: Disable XHC1 in /proc/acpi/wakeup.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: linux-image-3.16.0-24-generic 3.16.0-24.32
  ProcVersionSignature: Ubuntu 3.16.0-24.32-generic 3.16.4
  Uname: Linux 3.16.0-24-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  stephan2266 F pulseaudio
   /dev/snd/controlC1:  stephan2266 F pulseaudio
  CurrentDesktop: Unity
  CurrentDmesg: Error: command ['sh', '-c', 'dmesg | comm -13 --nocheck-order 
/var/log/dmesg -'] failed with exit code 1: comm: /var/log/dmesg: Permission 
denied
  Date: Tue Nov 11 12:11:02 2014
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2014-10-08 (33 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 05ac:0259 Apple, Inc.
   Bus 001 Device 006: ID 05ac:8289 Apple, Inc.
   Bus 001 Device 002: ID 0a5c:4500 Broadcom Corp. BCM2046B1 USB 2.0 Hub (part 
of BCM2046 Bluetooth)
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Apple Inc. MacBookPro11,1
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-24-generic.efi.signed 
root=UUID=d3ef8cca-2c30-46c5-88cc-a5f523abf8ac ro quiet splash vt.handoff=7
  SourcePackage: linux
  UpgradeStatus: Upgraded to utopic on 2014-10-17 (24 days ago)
  WifiSyslog:

  dmi.bios.date: 02/12/2014
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: MBP111.88Z.0138.B07.1402121134
  dmi.board.asset.tag: Base Board Asset Tag#
  dmi.board.name: Mac-189A3D4F975D5FFC
  dmi.board.vendor: Apple Inc.
  dmi.board.version: MacBookPro11,1
  dmi.chassis.type: 10
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-189A3D4F975D5FFC
  dmi.modalias: 
dmi:bvnAppleInc.:bvrMBP111.88Z.0138.B07.1402121134:bd02/12/2014:svnAppleInc.:pnMacBookPro11,1:pvr1.0:rvnAppleInc.:rnMac-189A3D4F975D5FFC:rvrMacBookPro11,1:cvnAppleInc.:ct10:cvrMac-189A3D4F975D5FFC:
  dmi.product.name: MacBookPro11,1
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.
  ---
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC1D0p:   stephan2266 F...m pulseaudio
   /dev/snd/controlC0:  stephan2266 F pulseaudio
   /dev/snd/controlC1:  stephan2266 F pulseaudio
  CurrentDesktop: Unity
  CurrentDmesg: Error: command ['sh', '-c', 'dmesg | comm -13 --nocheck-order 
/var/log/dmesg -'] failed with exit code 1: comm: /var/log/dmesg: Permission 
denied
  DistroRelease: Ubuntu 14.10
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2014-10-08 (34 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  MachineType: Apple Inc. MacBookPro11,1
  NonfreeKernelModules: wl
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-24-generic.efi.signed 
root=UUID=d3ef8cca-2c30-46c5-88cc-a5f523abf8ac ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.16.0-24.32-generic 3.16.4
  Tags:  utopic
  Uname: Linux 3.16.0-24-generic x86_64
  UpgradeStatus: Upgraded to utopic on 2014-10-17 (24 days ago)
  UserGroups: sudo
  WifiSyslog:

  _MarkForUpload: True
  dmi.bios.date: 02/12/2014
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: MBP111.88Z.

[Kernel-packages] [Bug 1335478] Re: A new instance of IBM Domino 'bindsock' cannot bind to ports <1024 Kernel 3.13.0-29 and above

[Ben Erickson]

Thanks, Andy- I've provided all this info in PMR 41425,227,000.

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

Title:
  A new instance of IBM Domino 'bindsock' cannot bind to ports <1024
  Kernel  3.13.0-29 and above

Status in linux package in Ubuntu:
  Fix Committed
Status in linux-lts-trusty package in Ubuntu:
  Invalid
Status in linux-lts-utopic package in Ubuntu:
  Invalid
Status in linux source package in Lucid:
  Fix Committed
Status in linux-lts-trusty source package in Lucid:
  Invalid
Status in linux-lts-utopic source package in Lucid:
  Invalid
Status in linux source package in Precise:
  Fix Committed
Status in linux-lts-trusty source package in Precise:
  Fix Committed
Status in linux-lts-utopic source package in Precise:
  Invalid
Status in linux source package in Trusty:
  Fix Committed
Status in linux-lts-trusty source package in Trusty:
  Invalid
Status in linux-lts-utopic source package in Trusty:
  Fix Committed
Status in linux source package in Utopic:
  Fix Committed
Status in linux-lts-trusty source package in Utopic:
  Invalid
Status in linux-lts-utopic source package in Utopic:
  Invalid
Status in linux source package in Vivid:
  Fix Committed
Status in linux-lts-trusty source package in Vivid:
  Invalid
Status in linux-lts-utopic source package in Vivid:
  Invalid

Bug description:
  Starting  with kernels  3.2.0-64 and 3.13.0-29  Something has changed
  to once again that prevents IBM Domino's
  "/opt/ibm/domino/notes/latest/linux/bindsock" binary that runs as root
  (setuid) to get ports lower than 1024 for it's LDAP, SMTP, IMAP, POP3,
  and HTTP processes.

  The Domino server reports  the following: :
    "Listener failure: 'bindsock' is missing, not executable, not owned by 
root, not setuid root or user needs net_privaddr privilege."

  This is the same behaviour that was reported and subsequently
  corrected in Bug # 1269053

  ===
  break-fix: dbb490b96584d4e958533fb637f08b557f505657 
6a2a2b3ae0759843b22c929881cc184b00cc63ff

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1335478/+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 1402834] Re: fuse filesystems get disconnected on container exit

[Serge Hallyn]

Patches sent to the lxc-devel mailing list to follow up on stgraber's
idea.

So between this and Eric's patch to prevent anyone but root from doing
umount -f, this should become non-urgent.

But it still seems wrong.

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

Title:
  fuse filesystems get disconnected on container exit

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  When bind-mounting a directory from a fuse filesytems into a container,
  then when the container is shut down, the userspace process serving the
  fuse fs is terminated.  The original fuse mountpoint remains busy until it
  is manually unmounted.

  I've tested this with sshfs, git://github.com/stgraber/cgmanagerfs,
  the bbfs example fs from http://www.cs.nmsu.edu/~pfeiffer/fuse-tutorial/,
  or git://github.com/lxc/lxcfs.

  To reproduce:

  Mount a fusefs - say sshfs - with -o allow_other, let's say onto
  /tmp/d.

  sshfs -f -d -o allow_other somehost:$HOME /tmp/d

  Bind that into a container by adding

  lxc.mount.entry = /tmp/d freezer none bind,create=dir 0 0

  to the container's config.

  start the container, stop it.

  the fuse program stops (exits 0 in fact)

  the mount is not cleaned up - ls /tmp/d on the host henceforth
  complains:

ls: cannot access /tmp/d Transport endpoint is not connected"

  (sudo umount /tmp/d cleans it up)

  I don't know for sure whether this is a kernel or libfuse bug.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1402834/+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 1391476] Re: [MacBookPro11, 1] Laptop wakes up while lid closed

[Christopher M. Penalver]

** Description changed:

- Same behavior when using pm-suspend. This bug may be CRITICAL, because
- it is hard to notice whether the laptop waking up, especially because
- that does not always happen immediately. Getting to sleep takes up to 30
- seconds. Hardware damage may be a result of waking up while lid is
- closed, for example if laptop is transported in a bag.
+ Same behavior when using pm-suspend. It is hard to notice whether the
+ laptop wakes up, especially because that does not always happen
+ immediately. Getting to sleep takes up to 30 seconds. Hardware damage
+ may be a result of waking up while lid is closed, for example if laptop
+ is transported in a bag. I suspect that the problem comes from the Intel
+ video driver. See extract from kern.log.
  
- I suspect that the problem comes from the Intel video driver. See
- extract from kern.log.
+ WORKAROUND: Disable XHC1 in /proc/acpi/wakeup.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: linux-image-3.16.0-24-generic 3.16.0-24.32
  ProcVersionSignature: Ubuntu 3.16.0-24.32-generic 3.16.4
  Uname: Linux 3.16.0-24-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
-  USERPID ACCESS COMMAND
-  /dev/snd/controlC0:  stephan2266 F pulseaudio
-  /dev/snd/controlC1:  stephan2266 F pulseaudio
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC0:  stephan2266 F pulseaudio
+  /dev/snd/controlC1:  stephan2266 F pulseaudio
  CurrentDesktop: Unity
  CurrentDmesg: Error: command ['sh', '-c', 'dmesg | comm -13 --nocheck-order 
/var/log/dmesg -'] failed with exit code 1: comm: /var/log/dmesg: Permission 
denied
  Date: Tue Nov 11 12:11:02 2014
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2014-10-08 (33 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  Lsusb:
-  Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
-  Bus 001 Device 003: ID 05ac:0259 Apple, Inc. 
-  Bus 001 Device 006: ID 05ac:8289 Apple, Inc. 
-  Bus 001 Device 002: ID 0a5c:4500 Broadcom Corp. BCM2046B1 USB 2.0 Hub (part 
of BCM2046 Bluetooth)
-  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
+  Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
+  Bus 001 Device 003: ID 05ac:0259 Apple, Inc.
+  Bus 001 Device 006: ID 05ac:8289 Apple, Inc.
+  Bus 001 Device 002: ID 0a5c:4500 Broadcom Corp. BCM2046B1 USB 2.0 Hub (part 
of BCM2046 Bluetooth)
+  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Apple Inc. MacBookPro11,1
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-24-generic.efi.signed 
root=UUID=d3ef8cca-2c30-46c5-88cc-a5f523abf8ac ro quiet splash vt.handoff=7
  SourcePackage: linux
  UpgradeStatus: Upgraded to utopic on 2014-10-17 (24 days ago)
  WifiSyslog:
-  
+ 
  dmi.bios.date: 02/12/2014
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: MBP111.88Z.0138.B07.1402121134
  dmi.board.asset.tag: Base Board Asset Tag#
  dmi.board.name: Mac-189A3D4F975D5FFC
  dmi.board.vendor: Apple Inc.
  dmi.board.version: MacBookPro11,1
  dmi.chassis.type: 10
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-189A3D4F975D5FFC
  dmi.modalias: 
dmi:bvnAppleInc.:bvrMBP111.88Z.0138.B07.1402121134:bd02/12/2014:svnAppleInc.:pnMacBookPro11,1:pvr1.0:rvnAppleInc.:rnMac-189A3D4F975D5FFC:rvrMacBookPro11,1:cvnAppleInc.:ct10:cvrMac-189A3D4F975D5FFC:
  dmi.product.name: MacBookPro11,1
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.
- --- 
+ ---
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
-  USERPID ACCESS COMMAND
-  /dev/snd/pcmC1D0p:   stephan2266 F...m pulseaudio
-  /dev/snd/controlC0:  stephan2266 F pulseaudio
-  /dev/snd/controlC1:  stephan2266 F pulseaudio
+  USERPID ACCESS COMMAND
+  /dev/snd/pcmC1D0p:   stephan2266 F...m pulseaudio
+  /dev/snd/controlC0:  stephan2266 F pulseaudio
+  /dev/snd/controlC1:  stephan2266 F pulseaudio
  CurrentDesktop: Unity
  CurrentDmesg: Error: command ['sh', '-c', 'dmesg | comm -13 --nocheck-order 
/var/log/dmesg -'] failed with exit code 1: comm: /var/log/dmesg: Permission 
denied
  DistroRelease: Ubuntu 14.10
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2014-10-08 (34 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  MachineType: Apple Inc. MacBookPro11,1
  NonfreeKernelModules: wl
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-24-generic.efi.signed 
root=UUID=d3ef8cca-2c30-46c5-88cc-a5f523abf8ac ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.16.0-24.32-generic 3.16.4
  Tags:  utopic
  Uname: Linux 3.16.0-24-generic x86_64
  UpgradeStatus: Upgraded to utopic on 2014-10-17 (24 days ago)
  UserGroups: sudo
  WifiSyslog:
-  
+ 
  _MarkForUpload: True
  dmi.bios.date: 02/12/2014
  dmi.

[Kernel-packages] [Bug 1385937] Re: [Acer Travelmate B115-M] Synaptic touchpad not correctly detected in kernel 3.16 after upgrade to Ubuntu 14.10

[Christopher M. Penalver]

holger_p., would this be reproducible in the latest mainline kernel
available 3.18.1?

** Tags removed: kernel-bug-exists-upstream-3.18-rc1

** Tags removed: performing-bisect

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

Title:
  [Acer Travelmate B115-M] Synaptic touchpad not correctly detected in
  kernel 3.16 after upgrade to Ubuntu 14.10

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Since the upgrade from Ubuntu 14.04 to 14.10 the Synaptic touchpad is
  not detected entirely. The secondary key (right mouse button) does not
  work with kernel 3.16.0-23-generic. Falling back under Ubuntu 14.10 to
  the kernel 3.13.0-37-generic the Synaptic touchpad is detected fully
  and right mouse button works again.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: linux-image-3.16.0-23-generic 3.16.0-23.31
  ProcVersionSignature: Ubuntu 3.16.0-23.31-generic 3.16.4
  Uname: Linux 3.16.0-23-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  hpannenb   2336 F pulseaudio
  CurrentDesktop: Unity
  Date: Sun Oct 26 19:45:20 2014
  HibernationDevice: RESUME=UUID=8aa00459-6b0d-4baf-84e4-7f945406d6b2
  InstallationDate: Installed on 2014-10-10 (15 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 1bcf:2c57 Sunplus Innovation Technology Inc. 
   Bus 001 Device 004: ID 0489:e046 Foxconn / Hon Hai 
   Bus 001 Device 002: ID 05e3:0608 Genesys Logic, Inc. Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Acer TravelMate B115-M
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-23-generic.efi.signed 
root=UUID=902f1410-63a6-41f1-893c-ab5e74543832 ro acpi_backlight=vendor quiet 
splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.16.0-23-generic N/A
   linux-backports-modules-3.16.0-23-generic  N/A
   linux-firmware 1.138
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/27/2014
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.22
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: Roxy
  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.22:bd08/27/2014:svnAcer:pnTravelMateB115-M:pvrV1.22:rvnAcer:rnRoxy:rvrType2-A01BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion:
  dmi.product.name: TravelMate B115-M
  dmi.product.version: V1.22
  dmi.sys.vendor: Acer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1385937/+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 1379340] Re: qemu-kvm guest panic for AMD smp trusty guests

[Daniele Viganò]

I can confirm that the issue looks fixed using 3.13.0-44.73~precise1
from precise-proposed.

I made more than ten reboots with the new kernel installed on VMs and
all were successful. Then I switched back to the previous
3.13.0-43.72~precise1 and VMs boot failed at the first trial. Again back
to propose 3.13.0-44.73~precise1 at VM were booting fine.

I'm not using Trusty on these AMD machines so I cannot test it. But the
kernel is the same as precise so the issue should be fixed also on
Trusty.

** Tags added: verification-done-precise

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

Title:
  qemu-kvm guest panic for AMD smp trusty guests

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

Bug description:
  [Impact]
  When using KVM on an AMD host with a kernel that has CONFIG_DEBUG_RODATA 
enabled, a guest with: multiple vCPUs, and exposing features to the guest such 
as tsc_adjust can cause a divide error on kvm_unlock_kick when booting the VM.

  This impacts kernels 3.12+.

  [Test Case]
  1) Create a VM on an AMD host with appropriate features (Opteron 6xxx for 
example)
  2) Edit virsh xml to have  and multiple 
vCPUs.
  3) Boot VM with VGA console using virt-manager (I couldn't reproduce strictly 
monitoring via virsh console).

  [Fix]
  commit c1118b3602c2329671ad5ec8bdf8e374323d6343 upstream

  --

  Just upgraded OpenStack compute hosts in our public cloud (using qemu-
  kvm via libvirt) from Precise to Trusty (14.04.1), now on kernel
  3.13.0-36-generic with qemu-kvm 2.0.0+dfsg-2ubuntu1.5.

  Following the upgrade, whenever we try to start an smp/multicore
  Trusty guest (existing or new), we run into this panic [1] inside the
  guest just towards the end of boot. This happens consistently for smp
  guests using the Trusty kernel (i.e., it also affects earlier Ubuntus
  using the HWE kernel from Trusty but not their native versions). I
  didn't have any other distro images to hand with 3.13.x kernels, but
  none of the others I tested were affected (in the 3.2 - 3.16 kernel
  range).

  There are scarce similar reports out there, but the one we did find
  pointed to a CPU feature as the trigger. We were running these hosts
  with libvirt cpu mode set to "host-passthrough" (so qemu starts with
  "-cpu host"), on AMD 6200 & 6300 Opteron hardware. Switching the guest
  domains to use cpu mode "host-model" instead works around the issue
  and is perfectly acceptable for most of our users.

  We have various other Intel compute hosts and they don't seem to be
  affected.

  (1)
  [ 11.256924] divide error:  [#1] SMP
  [ 11.258133] Modules linked in: kvm_amd kvm crct10dif_pclmul crc32_pclmul 
ghash_clmulni_intel aesni_intel aes_x86_64 lrw gf128mul glue_helper ablk_helper 
cryptd serio_raw lp parport psmouse floppy
  [ 11.260228] CPU: 0 PID: 0 Comm: swapper/0 Not tainted 3.13.0-36-generic 
#63-Ubuntu
  [ 11.260228] Hardware name: OpenStack Foundation OpenStack Nova, BIOS Bochs 
01/01/2011
  [ 11.260228] task: 81c15480 ti: 81c0 task.ti: 
81c0
  [ 11.260228] RIP: 0010:[] [] 
kvm_unlock_kick+0xa8/0x100
  [ 11.260228] RSP: 0018:88023fc03c98 EFLAGS: 00010046
  [ 11.260228] RAX: 0005 RBX:  RCX: 0001
  [ 11.260228] RDX: 81eaf408 RSI:  RDI: 
  [ 11.260228] RBP: 88023fc03cb8 R08: 81eaf400 R09: 
  [ 11.260228] R10: 880037612cc0 R11: ea0002eb0a00 R12: 8800374a33c0
  [ 11.260228] R13: 0020 R14: 0001 R15: 0286
  [ 11.260228] FS: 7f1e8b538740() GS:88023fc0() 
knlGS:
  [ 11.260228] CS: 0010 DS:  ES:  CR0: 8005003b
  [ 11.260228] CR2: 7f1e8ae09d50 CR3: 01c0e000 CR4: 000406f0
  [ 11.260228] Stack:
  [ 11.260228] 0286 0001 0001 
00c3
  [ 11.260228] 88023fc03cc8 81717ed6 88023fc03ce0 
8172641a
  [ 11.260228] 8800374a33c0 88023fc03d18 810aaeb0 
88023295e000
  [ 11.260228] Call Trace:
  [ 11.260228] 
  [ 11.260228] [] __ticket_unlock_slowpath+0x24/0x34
  [ 11.260228] [] _raw_spin_unlock_irqrestore+0x3a/0x40
  [ 11.260228] [] __wake_up_sync_key+0x50/0x60
  [ 11.260228] [] sock_def_readable+0x3a/0x70
  [ 11.260228] [] packet_rcv+0x2fa/0x430
  [ 11.260228] [] __netif_receive_skb_core+0x360/0x840
  [ 11.260228] [] __netif_receive_skb+0x18/0x60
  [ 11.260228] [] netif_receive_skb+0x23/0x90
  [ 11.260228] [] virtnet_poll+0x4d4/0x850
  [ 11.260228] [] net_rx_action+0x152/0x250
  [ 11.260228] [] __do_softirq+0xec/0x2c0
  [ 11.260228] [] irq_exit+0x105/0x110
  [ 11.260228] [] do_IRQ+0x56/0xc0
  [ 11.260228] [] common_interrupt+0x6d/0x6d
  [ 11.2602

[Kernel-packages] [Bug 1397032] Re: [Lenovo ThinkPad T540p] Intel Wireless Dual Band 7260AC fails to connect

[Christopher M. Penalver]

Federico Sassi, the next step is to fully reverse commit bisect from
kernel 3.18-rc7 to 3.18.1 in order to identify the last bad commit,
followed immediately by the first good one. Once this commit has been
identified, then it may be reviewed as a candidate for backporting into
your release. Could you please do this following
https://wiki.ubuntu.com/Kernel/KernelBisection#How_do_I_reverse_bisect_the_upstream_kernel.3F
?  Please note, finding adjacent kernel versions is not fully commit
bisecting.

Thank you for your understanding.

Helpful bug reporting tips:
https://wiki.ubuntu.com/ReportingBugs

** Tags removed: kernel-bug-exists-upstream-3.18-rc7
** Tags added: kernel-fixed-upstream-3.18.1

** Tags added: needs-reverse-bisect

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

Title:
  [Lenovo ThinkPad T540p] Intel Wireless Dual Band 7260AC fails to
  connect

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I have a Lenovo Thinkpad T540p and the wireless connection isn't
  working correctly. It will list the available networks but when trying
  to connect it will keep asking for the password or when it connects
  the connection will last only few seconds and the packet loss on a
  ping will be very high.

  I've followed bug 
https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1354975 in order 
to find a solution but without luck. I've tried to turn off power management, 
install latest kernel ( linux-image-3.17.0-031700-generic ) and related updated 
firmware according to http://wireless.kernel.org/en/users/Drivers/iwlwifi . 
Tried also the updated firmware for the older kernel and with the older kernel.
  I've tried also Ubuntu 14.10 with same results. I've tried to move closer to 
the router but with no change at all.

  Network controller [0280]: Intel Corporation Wireless 7260 [8086:08b2] (rev 
83)
   Subsystem: Intel Corporation Dual Band Wireless-AC 7260 [8086:c270]

  sudo lshw -C network
  network
     description: Wireless interface
     product: Wireless 7260
     vendor: Intel Corporation
     physical id: 0
     bus info: pci@:04:00.0
     logical name: wlan0
     version: 83
     serial: e8:b1:fc:d2:e3:9e
     width: 64 bits
     clock: 33MHz
     capabilities: pm msi pciexpress bus_master cap_list ethernet physical 
wireless
     configuration: broadcast=yes driver=iwlwifi 
driverversion=3.13.0-40-generic firmware=22.24.8.0 latency=0 link=no 
multicast=yes wireless=IEEE 802.11abgn
     resources: irq:47 memory:e140-e1401fff

  WORKAROUND: Disable 802.11n on the router.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-40-generic 3.13.0-40.69
  ProcVersionSignature: Ubuntu 3.13.0-40.69-generic 3.13.11.10
  Uname: Linux 3.13.0-40-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  fsassi 1930 F pulseaudio
   /dev/snd/controlC1:  fsassi 1930 F pulseaudio
  Date: Thu Nov 27 16:13:07 2014
  HibernationDevice: RESUME=UUID=650269f1-902f-4143-8cd4-27d1631b5d05
  InstallationDate: Installed on 2014-11-26 (0 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  MachineType: LENOVO 20BECTO1WW
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-40-generic.efi.signed 
root=UUID=00883037-516d-4066-9e6b-581d1c2a4b7d ro quiet splash vt.handoff=7
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-40-generic N/A
   linux-backports-modules-3.13.0-40-generic  N/A
   linux-firmware 1.127.8
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/22/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GMET67WW (2.15 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20BECTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0E50512 STD
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrGMET67WW(2.15):bd09/22/2014:svnLENOVO:pn20BECTO1WW:pvrThinkPadT540p:rvnLENOVO:rn20BECTO1WW:rvrSDK0E50512STD:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 20BECTO1WW
  dmi.product.version: ThinkPad T540p
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1275879] Re: Kernel panic

[Donald Stufft]

So, I don't have a problem testing this on trusty-proposed but the 5 day
thing might be an issue. The kernel panic happened randomly after some
period of time, it wasn't something I could trigger on demand. All I can
do is run a server and wait some period of time and see if it kernel
panics or not. Is that good enough?

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

Title:
  Kernel panic

Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Trusty:
  Fix Committed
Status in linux source package in Utopic:
  Fix Committed
Status in linux source package in Vivid:
  Fix Committed

Bug description:
  SRU Justification

  Impact: Under certain workloads a BUG in the xen-netfront driver is
  getting triggered.

  Fix: Remove the offending BUG, and a related BUG which would have also
  been triggered by the same conditions.

  Test Case: This bug has only been seen under certain workloads
  involving haproxy and has proved challenging to reproduce. The fix has
  been verified by an affected user, with the BUG replaced by a WARN to
  ensure that the conditions which would have triggered the bug were
  actually encountered.

  Regression Potential: The fix has been verified and acked upstream.
  Removing the BUGs will not affect cases which were not crashing
  previously, and cases which were crashing can't really be made much
  worse.

  ---

  I run ubuntu servers 13.04, 13.10, and 14.04 on the AWS cloud.
  Whenever I install haproxy and nginx on the same server, after hitting
  it for a while, a kernel panic is caused. However, the kernel panic
  does not show up in ubuntu 12.04.  The kernel panic is pasted at the
  end of the attachment.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1275879/+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 1335478] Re: A new instance of IBM Domino 'bindsock' cannot bind to ports <1024 Kernel 3.13.0-29 and above

[Andy Whitcroft]

The attached test.c should tickle this bug, sendmsg should return ret=4
errno=0 when the fix is applied, ret=-1 errno=22 when it is not.

** Attachment added: "test.c"
   
https://bugs.launchpad.net/ubuntu/+source/linux-lts-trusty/+bug/1335478/+attachment/4284352/+files/test.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/1335478

Title:
  A new instance of IBM Domino 'bindsock' cannot bind to ports <1024
  Kernel  3.13.0-29 and above

Status in linux package in Ubuntu:
  Fix Committed
Status in linux-lts-trusty package in Ubuntu:
  Invalid
Status in linux-lts-utopic package in Ubuntu:
  Invalid
Status in linux source package in Lucid:
  Fix Committed
Status in linux-lts-trusty source package in Lucid:
  Invalid
Status in linux-lts-utopic source package in Lucid:
  Invalid
Status in linux source package in Precise:
  Fix Committed
Status in linux-lts-trusty source package in Precise:
  Fix Committed
Status in linux-lts-utopic source package in Precise:
  Invalid
Status in linux source package in Trusty:
  Fix Committed
Status in linux-lts-trusty source package in Trusty:
  Invalid
Status in linux-lts-utopic source package in Trusty:
  Fix Committed
Status in linux source package in Utopic:
  Fix Committed
Status in linux-lts-trusty source package in Utopic:
  Invalid
Status in linux-lts-utopic source package in Utopic:
  Invalid
Status in linux source package in Vivid:
  Fix Committed
Status in linux-lts-trusty source package in Vivid:
  Invalid
Status in linux-lts-utopic source package in Vivid:
  Invalid

Bug description:
  Starting  with kernels  3.2.0-64 and 3.13.0-29  Something has changed
  to once again that prevents IBM Domino's
  "/opt/ibm/domino/notes/latest/linux/bindsock" binary that runs as root
  (setuid) to get ports lower than 1024 for it's LDAP, SMTP, IMAP, POP3,
  and HTTP processes.

  The Domino server reports  the following: :
    "Listener failure: 'bindsock' is missing, not executable, not owned by 
root, not setuid root or user needs net_privaddr privilege."

  This is the same behaviour that was reported and subsequently
  corrected in Bug # 1269053

  ===
  break-fix: dbb490b96584d4e958533fb637f08b557f505657 
6a2a2b3ae0759843b22c929881cc184b00cc63ff

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

[Brad Figg]

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

apport-collect 1404335

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

Title:
  xgene: BUG: soft lockup - CPU#0 stuck for 23s! [halt:2059] on poweroff

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  [Impact]
  Fixes an issue where after the system halts the cpu starts to experience soft 
lockups.

  [Test Case]
  The most reliable means of reproducing this issue is to 'sudo poweroff' the 
system from the console.

  [Regression Potential]
  These patches are upstream patches that have been in the utopic kernel for 
quite a while and only affect the arm64 architecture.

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

[Brad Figg]

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

apport-collect 1404050

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

Title:
  After loading Ubuntu along side windows, my keyboard does not work on
  either boot menu.  Keyboard works after boot is complete.

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Prior to loading Ubuntu 14.10, my system boot menu comes up and I can
  make changes using my keyboard. (F10,F11, up, down etc).  After
  loading Ubuntu, my keyboard does not respond on either boot menu.
  (Launch Ubuntu, Launch Window)  As a result, I can't change my system
  boot and I can't change between Windows and Ubuntu on the Ubuntu boot
  menu. (defaults to Ubuntu)

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: ubuntu-release-upgrader-core 1:14.10.9
  ProcVersionSignature: Ubuntu 3.16.0-28.38-generic 3.16.7-ckt1
  Uname: Linux 3.16.0-28-generic x86_64
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: amd64
  CrashDB: ubuntu
  CurrentDesktop: Unity
  Date: Thu Dec 18 17:15:45 2014
  InstallationDate: Installed on 2014-12-14 (3 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: ubuntu-release-upgrader
  Symptom: dist-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1404050/+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 1404050] Re: After loading Ubuntu along side windows, my keyboard does not work on either boot menu. Keyboard works after boot is complete.

[Brian Murray]

** Package changed: ubuntu-release-upgrader (Ubuntu) => linux (Ubuntu)

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

Title:
  After loading Ubuntu along side windows, my keyboard does not work on
  either boot menu.  Keyboard works after boot is complete.

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Prior to loading Ubuntu 14.10, my system boot menu comes up and I can
  make changes using my keyboard. (F10,F11, up, down etc).  After
  loading Ubuntu, my keyboard does not respond on either boot menu.
  (Launch Ubuntu, Launch Window)  As a result, I can't change my system
  boot and I can't change between Windows and Ubuntu on the Ubuntu boot
  menu. (defaults to Ubuntu)

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: ubuntu-release-upgrader-core 1:14.10.9
  ProcVersionSignature: Ubuntu 3.16.0-28.38-generic 3.16.7-ckt1
  Uname: Linux 3.16.0-28-generic x86_64
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: amd64
  CrashDB: ubuntu
  CurrentDesktop: Unity
  Date: Thu Dec 18 17:15:45 2014
  InstallationDate: Installed on 2014-12-14 (3 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: ubuntu-release-upgrader
  Symptom: dist-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1404050/+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 1334950] Re: [HP 14 Touchsmart][HP 15 Touchsmart] Volume mute LED is not working

[Brad Figg]

This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
trusty' to 'verification-done-trusty'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: verification-needed-trusty

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

Title:
  [HP 14 Touchsmart][HP 15 Touchsmart] Volume mute LED is not working

Status in HWE Next Project:
  Fix Released
Status in HWE Next trusty series:
  Confirmed
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Trusty:
  Fix Committed

Bug description:
  CID: 201310-14248 HP 15 Touchsmart

  There is a mute key on this system, along with a Mute LED on it.
  The mute key works fine, but the LED is not working at all.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-30-generic 3.13.0-30.54
  ProcVersionSignature: Ubuntu 3.13.0-30.54-generic 3.13.11.2
  Uname: Linux 3.13.0-30-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  ubuntu 1649 F pulseaudio
   /dev/snd/controlC0:  ubuntu 1649 F pulseaudio
  CRDA:
   country TW:
(2402 - 2472 @ 40), (3, 27)
(5270 - 5330 @ 40), (3, 17), DFS
(5735 - 5815 @ 40), (3, 30)
  CurrentDesktop: Unity
  Date: Thu Jun 26 23:57:42 2014
  HibernationDevice: RESUME=UUID=540104b4-4be9-4245-8c53-2f8471e94cbb
  InstallationDate: Installed on 2014-06-26 (0 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  MachineType: Hewlett-Packard HP 15 Notebook PC
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-30-generic.efi.signed 
root=UUID=61fbea42-9507-49b2-b9ad-b0050652e97e ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-30-generic N/A
   linux-backports-modules-3.13.0-30-generic  N/A
   linux-firmware 1.127.4
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/06/2013
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: F.09
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 2192
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 41.1A
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrF.09:bd12/06/2013:svnHewlett-Packard:pnHP15NotebookPC:pvr088710025E112:rvnHewlett-Packard:rn2192:rvr41.1A:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.name: HP 15 Notebook PC
  dmi.product.version: 088710025E112
  dmi.sys.vendor: Hewlett-Packard

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1334950/+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 1404050] [NEW] After loading Ubuntu along side windows, my keyboard does not work on either boot menu. Keyboard works after boot is complete.

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

Prior to loading Ubuntu 14.10, my system boot menu comes up and I can
make changes using my keyboard. (F10,F11, up, down etc).  After loading
Ubuntu, my keyboard does not respond on either boot menu.  (Launch
Ubuntu, Launch Window)  As a result, I can't change my system boot and I
can't change between Windows and Ubuntu on the Ubuntu boot menu.
(defaults to Ubuntu)

ProblemType: Bug
DistroRelease: Ubuntu 14.10
Package: ubuntu-release-upgrader-core 1:14.10.9
ProcVersionSignature: Ubuntu 3.16.0-28.38-generic 3.16.7-ckt1
Uname: Linux 3.16.0-28-generic x86_64
ApportVersion: 2.14.7-0ubuntu8
Architecture: amd64
CrashDB: ubuntu
CurrentDesktop: Unity
Date: Thu Dec 18 17:15:45 2014
InstallationDate: Installed on 2014-12-14 (3 days ago)
InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
PackageArchitecture: all
ProcEnviron:
 LANGUAGE=en_US
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: ubuntu-release-upgrader
Symptom: dist-upgrade
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug dist-upgrade utopic
-- 
After loading Ubuntu along side windows, my keyboard does not work on either 
boot menu.  Keyboard works after boot is complete.
https://bugs.launchpad.net/bugs/1404050
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 1346067] Re: [Dell Latitude E5440] O2 Card reader [1217:8520] could not be detected after rebooting this system

[Brad Figg]

This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
utopic' to 'verification-done-utopic'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!

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

Title:
  [Dell Latitude E5440] O2 Card reader [1217:8520] could not be detected
  after rebooting this system

Status in HWE Next Project:
  Fix Committed
Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Trusty:
  Fix Committed
Status in linux source package in Utopic:
  Fix Committed
Status in linux source package in Vivid:
  Fix Committed

Bug description:
  SRU Justification:

  Impact: the card reader does not work on this system after rebooting.
  Fix: cherry pick a simple one line patch
  Testcase: already tested in OEM projects

  
  CID: 201307-14017 Dell Latitude E5440

  The O2 card reader, O2 Micro, Inc. SD/MMC Card Reader Controller [1217:8520] 
(rev 01)
  is not stable on this system, the card reader cannot be detected.
  It works normally after reboot, but will be gone if you reboot it one more 
time

  Steps:
  1. Install 14.04 + update (3.13.0-32), boot to desktop
  2. Run lspci -nn to see if the card reader is there
  3. Insert a SD card
  4. Reboot, go through step 2 and 3 again

  Expected result:
  * Card reader should be found in lspci output, SD card should be mounted 
automatically

  Actual result:
  * Nothing happened, the card was not detected at all
  * On step 4, the card reader works, if rebooted again, it will be gone.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-32-generic 3.13.0-32.57
  ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4
  Uname: Linux 3.13.0-32-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 1398 F pulseaudio
   /dev/snd/controlC1:  ubuntu 1398 F pulseaudio
  CurrentDesktop: Unity
  Date: Mon Jul 21 04:07:31 2014
  HibernationDevice: RESUME=UUID=730e0474-ac0b-4fc6-a321-6203c9b07a19
  InstallationDate: Installed on 2014-07-21 (0 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  MachineType: Dell Inc. Latitude E5440
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-32-generic.efi.signed 
root=UUID=b55056b7-f859-4273-9793-12757a75c5ee ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-32-generic N/A
   linux-backports-modules-3.13.0-32-generic  N/A
   linux-firmware 1.127.4
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/26/2014
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A07
  dmi.board.name: 01348S
  dmi.board.vendor: Dell Inc.
  dmi.board.version: X02
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA07:bd06/26/2014:svnDellInc.:pnLatitudeE5440:pvr01:rvnDellInc.:rn01348S:rvrX02:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E5440
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1346067/+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 1335478] Re: A new instance of IBM Domino 'bindsock' cannot bind to ports <1024 Kernel 3.13.0-29 and above

[Brad Figg]

This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
trusty' to 'verification-done-trusty'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: verification-needed-utopic

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

Title:
  A new instance of IBM Domino 'bindsock' cannot bind to ports <1024
  Kernel  3.13.0-29 and above

Status in linux package in Ubuntu:
  Fix Committed
Status in linux-lts-trusty package in Ubuntu:
  Invalid
Status in linux-lts-utopic package in Ubuntu:
  Invalid
Status in linux source package in Lucid:
  Fix Committed
Status in linux-lts-trusty source package in Lucid:
  Invalid
Status in linux-lts-utopic source package in Lucid:
  Invalid
Status in linux source package in Precise:
  Fix Committed
Status in linux-lts-trusty source package in Precise:
  Fix Committed
Status in linux-lts-utopic source package in Precise:
  Invalid
Status in linux source package in Trusty:
  Fix Committed
Status in linux-lts-trusty source package in Trusty:
  Invalid
Status in linux-lts-utopic source package in Trusty:
  Fix Committed
Status in linux source package in Utopic:
  Fix Committed
Status in linux-lts-trusty source package in Utopic:
  Invalid
Status in linux-lts-utopic source package in Utopic:
  Invalid
Status in linux source package in Vivid:
  Fix Committed
Status in linux-lts-trusty source package in Vivid:
  Invalid
Status in linux-lts-utopic source package in Vivid:
  Invalid

Bug description:
  Starting  with kernels  3.2.0-64 and 3.13.0-29  Something has changed
  to once again that prevents IBM Domino's
  "/opt/ibm/domino/notes/latest/linux/bindsock" binary that runs as root
  (setuid) to get ports lower than 1024 for it's LDAP, SMTP, IMAP, POP3,
  and HTTP processes.

  The Domino server reports  the following: :
    "Listener failure: 'bindsock' is missing, not executable, not owned by 
root, not setuid root or user needs net_privaddr privilege."

  This is the same behaviour that was reported and subsequently
  corrected in Bug # 1269053

  ===
  break-fix: dbb490b96584d4e958533fb637f08b557f505657 
6a2a2b3ae0759843b22c929881cc184b00cc63ff

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1335478/+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 1379340] Re: qemu-kvm guest panic for AMD smp trusty guests

[Brad Figg]

This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
utopic' to 'verification-done-utopic'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!

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

Title:
  qemu-kvm guest panic for AMD smp trusty guests

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

Bug description:
  [Impact]
  When using KVM on an AMD host with a kernel that has CONFIG_DEBUG_RODATA 
enabled, a guest with: multiple vCPUs, and exposing features to the guest such 
as tsc_adjust can cause a divide error on kvm_unlock_kick when booting the VM.

  This impacts kernels 3.12+.

  [Test Case]
  1) Create a VM on an AMD host with appropriate features (Opteron 6xxx for 
example)
  2) Edit virsh xml to have  and multiple 
vCPUs.
  3) Boot VM with VGA console using virt-manager (I couldn't reproduce strictly 
monitoring via virsh console).

  [Fix]
  commit c1118b3602c2329671ad5ec8bdf8e374323d6343 upstream

  --

  Just upgraded OpenStack compute hosts in our public cloud (using qemu-
  kvm via libvirt) from Precise to Trusty (14.04.1), now on kernel
  3.13.0-36-generic with qemu-kvm 2.0.0+dfsg-2ubuntu1.5.

  Following the upgrade, whenever we try to start an smp/multicore
  Trusty guest (existing or new), we run into this panic [1] inside the
  guest just towards the end of boot. This happens consistently for smp
  guests using the Trusty kernel (i.e., it also affects earlier Ubuntus
  using the HWE kernel from Trusty but not their native versions). I
  didn't have any other distro images to hand with 3.13.x kernels, but
  none of the others I tested were affected (in the 3.2 - 3.16 kernel
  range).

  There are scarce similar reports out there, but the one we did find
  pointed to a CPU feature as the trigger. We were running these hosts
  with libvirt cpu mode set to "host-passthrough" (so qemu starts with
  "-cpu host"), on AMD 6200 & 6300 Opteron hardware. Switching the guest
  domains to use cpu mode "host-model" instead works around the issue
  and is perfectly acceptable for most of our users.

  We have various other Intel compute hosts and they don't seem to be
  affected.

  (1)
  [ 11.256924] divide error:  [#1] SMP
  [ 11.258133] Modules linked in: kvm_amd kvm crct10dif_pclmul crc32_pclmul 
ghash_clmulni_intel aesni_intel aes_x86_64 lrw gf128mul glue_helper ablk_helper 
cryptd serio_raw lp parport psmouse floppy
  [ 11.260228] CPU: 0 PID: 0 Comm: swapper/0 Not tainted 3.13.0-36-generic 
#63-Ubuntu
  [ 11.260228] Hardware name: OpenStack Foundation OpenStack Nova, BIOS Bochs 
01/01/2011
  [ 11.260228] task: 81c15480 ti: 81c0 task.ti: 
81c0
  [ 11.260228] RIP: 0010:[] [] 
kvm_unlock_kick+0xa8/0x100
  [ 11.260228] RSP: 0018:88023fc03c98 EFLAGS: 00010046
  [ 11.260228] RAX: 0005 RBX:  RCX: 0001
  [ 11.260228] RDX: 81eaf408 RSI:  RDI: 
  [ 11.260228] RBP: 88023fc03cb8 R08: 81eaf400 R09: 
  [ 11.260228] R10: 880037612cc0 R11: ea0002eb0a00 R12: 8800374a33c0
  [ 11.260228] R13: 0020 R14: 0001 R15: 0286
  [ 11.260228] FS: 7f1e8b538740() GS:88023fc0() 
knlGS:
  [ 11.260228] CS: 0010 DS:  ES:  CR0: 8005003b
  [ 11.260228] CR2: 7f1e8ae09d50 CR3: 01c0e000 CR4: 000406f0
  [ 11.260228] Stack:
  [ 11.260228] 0286 0001 0001 
00c3
  [ 11.260228] 88023fc03cc8 81717ed6 88023fc03ce0 
8172641a
  [ 11.260228] 8800374a33c0 88023fc03d18 810aaeb0 
88023295e000
  [ 11.260228] Call Trace:
  [ 11.260228] 
  [ 11.260228] [] __ticket_unlock_slowpath+0x24/0x34
  [ 11.260228] [] _raw_spin_unlock_irqrestore+0x3a/0x40
  [ 11.260228] [] __wake_up_sync_key+0x50/0x60
  [ 11.260228] [] sock_def_readable+0x3a/0x70
  [ 11.260228] [] packet_rcv+0x2fa/0x430
  [ 11.260228] [] __netif_receive_skb_core+0x360/0x840
  [ 11.260228] [] __netif_receive_skb+0x18/0x60
  [ 11.260228] [] netif_receive_skb+0x23/0x90
  [ 11.260228] [] virtnet_poll+0x4d4/0x850
  [ 11.260228] [] net_rx_action+0x152/0x250
  [ 11.260228] [] __do_softirq+0xec/0x2c0
  [ 11.260228] [] irq_exit+0x105/0x110
  [ 11.260228] [] do_IRQ+0x56/0xc0
  [ 11.260228] [] common_interrupt+0x6d/0x6d
  [ 11.260228] 
  [ 11.260228] [] ? native_safe_halt+0x6/0

[Kernel-packages] [Bug 1335478] Re: A new instance of IBM Domino 'bindsock' cannot bind to ports <1024 Kernel 3.13.0-29 and above

[Brad Figg]

This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
utopic' to 'verification-done-utopic'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!

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

Title:
  A new instance of IBM Domino 'bindsock' cannot bind to ports <1024
  Kernel  3.13.0-29 and above

Status in linux package in Ubuntu:
  Fix Committed
Status in linux-lts-trusty package in Ubuntu:
  Invalid
Status in linux-lts-utopic package in Ubuntu:
  Invalid
Status in linux source package in Lucid:
  Fix Committed
Status in linux-lts-trusty source package in Lucid:
  Invalid
Status in linux-lts-utopic source package in Lucid:
  Invalid
Status in linux source package in Precise:
  Fix Committed
Status in linux-lts-trusty source package in Precise:
  Fix Committed
Status in linux-lts-utopic source package in Precise:
  Invalid
Status in linux source package in Trusty:
  Fix Committed
Status in linux-lts-trusty source package in Trusty:
  Invalid
Status in linux-lts-utopic source package in Trusty:
  Fix Committed
Status in linux source package in Utopic:
  Fix Committed
Status in linux-lts-trusty source package in Utopic:
  Invalid
Status in linux-lts-utopic source package in Utopic:
  Invalid
Status in linux source package in Vivid:
  Fix Committed
Status in linux-lts-trusty source package in Vivid:
  Invalid
Status in linux-lts-utopic source package in Vivid:
  Invalid

Bug description:
  Starting  with kernels  3.2.0-64 and 3.13.0-29  Something has changed
  to once again that prevents IBM Domino's
  "/opt/ibm/domino/notes/latest/linux/bindsock" binary that runs as root
  (setuid) to get ports lower than 1024 for it's LDAP, SMTP, IMAP, POP3,
  and HTTP processes.

  The Domino server reports  the following: :
    "Listener failure: 'bindsock' is missing, not executable, not owned by 
root, not setuid root or user needs net_privaddr privilege."

  This is the same behaviour that was reported and subsequently
  corrected in Bug # 1269053

  ===
  break-fix: dbb490b96584d4e958533fb637f08b557f505657 
6a2a2b3ae0759843b22c929881cc184b00cc63ff

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1335478/+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 1335478] Re: A new instance of IBM Domino 'bindsock' cannot bind to ports <1024 Kernel 3.13.0-29 and above

[Brad Figg]

This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
lucid' to 'verification-done-lucid'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: verification-needed-lucid

** Tags added: verification-needed-precise

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

Title:
  A new instance of IBM Domino 'bindsock' cannot bind to ports <1024
  Kernel  3.13.0-29 and above

Status in linux package in Ubuntu:
  Fix Committed
Status in linux-lts-trusty package in Ubuntu:
  Invalid
Status in linux-lts-utopic package in Ubuntu:
  Invalid
Status in linux source package in Lucid:
  Fix Committed
Status in linux-lts-trusty source package in Lucid:
  Invalid
Status in linux-lts-utopic source package in Lucid:
  Invalid
Status in linux source package in Precise:
  Fix Committed
Status in linux-lts-trusty source package in Precise:
  Fix Committed
Status in linux-lts-utopic source package in Precise:
  Invalid
Status in linux source package in Trusty:
  Fix Committed
Status in linux-lts-trusty source package in Trusty:
  Invalid
Status in linux-lts-utopic source package in Trusty:
  Fix Committed
Status in linux source package in Utopic:
  Fix Committed
Status in linux-lts-trusty source package in Utopic:
  Invalid
Status in linux-lts-utopic source package in Utopic:
  Invalid
Status in linux source package in Vivid:
  Fix Committed
Status in linux-lts-trusty source package in Vivid:
  Invalid
Status in linux-lts-utopic source package in Vivid:
  Invalid

Bug description:
  Starting  with kernels  3.2.0-64 and 3.13.0-29  Something has changed
  to once again that prevents IBM Domino's
  "/opt/ibm/domino/notes/latest/linux/bindsock" binary that runs as root
  (setuid) to get ports lower than 1024 for it's LDAP, SMTP, IMAP, POP3,
  and HTTP processes.

  The Domino server reports  the following: :
    "Listener failure: 'bindsock' is missing, not executable, not owned by 
root, not setuid root or user needs net_privaddr privilege."

  This is the same behaviour that was reported and subsequently
  corrected in Bug # 1269053

  ===
  break-fix: dbb490b96584d4e958533fb637f08b557f505657 
6a2a2b3ae0759843b22c929881cc184b00cc63ff

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

[Brad Figg]

This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
trusty' to 'verification-done-trusty'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: verification-needed-trusty

** Tags added: verification-needed-utopic

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

Title:
  Kernel panic

Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Trusty:
  Fix Committed
Status in linux source package in Utopic:
  Fix Committed
Status in linux source package in Vivid:
  Fix Committed

Bug description:
  SRU Justification

  Impact: Under certain workloads a BUG in the xen-netfront driver is
  getting triggered.

  Fix: Remove the offending BUG, and a related BUG which would have also
  been triggered by the same conditions.

  Test Case: This bug has only been seen under certain workloads
  involving haproxy and has proved challenging to reproduce. The fix has
  been verified by an affected user, with the BUG replaced by a WARN to
  ensure that the conditions which would have triggered the bug were
  actually encountered.

  Regression Potential: The fix has been verified and acked upstream.
  Removing the BUGs will not affect cases which were not crashing
  previously, and cases which were crashing can't really be made much
  worse.

  ---

  I run ubuntu servers 13.04, 13.10, and 14.04 on the AWS cloud.
  Whenever I install haproxy and nginx on the same server, after hitting
  it for a while, a kernel panic is caused. However, the kernel panic
  does not show up in ubuntu 12.04.  The kernel panic is pasted at the
  end of the attachment.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1275879/+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 1346067] Re: [Dell Latitude E5440] O2 Card reader [1217:8520] could not be detected after rebooting this system

[Brad Figg]

This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
trusty' to 'verification-done-trusty'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: verification-needed-trusty

** Tags added: verification-needed-utopic

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

Title:
  [Dell Latitude E5440] O2 Card reader [1217:8520] could not be detected
  after rebooting this system

Status in HWE Next Project:
  Fix Committed
Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Trusty:
  Fix Committed
Status in linux source package in Utopic:
  Fix Committed
Status in linux source package in Vivid:
  Fix Committed

Bug description:
  SRU Justification:

  Impact: the card reader does not work on this system after rebooting.
  Fix: cherry pick a simple one line patch
  Testcase: already tested in OEM projects

  
  CID: 201307-14017 Dell Latitude E5440

  The O2 card reader, O2 Micro, Inc. SD/MMC Card Reader Controller [1217:8520] 
(rev 01)
  is not stable on this system, the card reader cannot be detected.
  It works normally after reboot, but will be gone if you reboot it one more 
time

  Steps:
  1. Install 14.04 + update (3.13.0-32), boot to desktop
  2. Run lspci -nn to see if the card reader is there
  3. Insert a SD card
  4. Reboot, go through step 2 and 3 again

  Expected result:
  * Card reader should be found in lspci output, SD card should be mounted 
automatically

  Actual result:
  * Nothing happened, the card was not detected at all
  * On step 4, the card reader works, if rebooted again, it will be gone.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-32-generic 3.13.0-32.57
  ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4
  Uname: Linux 3.13.0-32-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 1398 F pulseaudio
   /dev/snd/controlC1:  ubuntu 1398 F pulseaudio
  CurrentDesktop: Unity
  Date: Mon Jul 21 04:07:31 2014
  HibernationDevice: RESUME=UUID=730e0474-ac0b-4fc6-a321-6203c9b07a19
  InstallationDate: Installed on 2014-07-21 (0 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  MachineType: Dell Inc. Latitude E5440
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-32-generic.efi.signed 
root=UUID=b55056b7-f859-4273-9793-12757a75c5ee ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-32-generic N/A
   linux-backports-modules-3.13.0-32-generic  N/A
   linux-firmware 1.127.4
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/26/2014
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A07
  dmi.board.name: 01348S
  dmi.board.vendor: Dell Inc.
  dmi.board.version: X02
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA07:bd06/26/2014:svnDellInc.:pnLatitudeE5440:pvr01:rvnDellInc.:rn01348S:rvrX02:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E5440
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1346067/+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 1359052] Re: [HP Z1-G2] Realtek card reader [10ec:5249] does not work after suspended on this system

[Brad Figg]

This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
trusty' to 'verification-done-trusty'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: verification-needed-trusty

** Tags added: verification-needed-utopic

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

Title:
  [HP Z1-G2] Realtek card reader [10ec:5249] does not work after
  suspended on this system

Status in HWE Next Project:
  Fix Committed
Status in HWE Next trusty series:
  Fix Committed
Status in HWE Next utopic series:
  Fix Committed
Status in HWE Next vivid series:
  Fix Committed
Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Trusty:
  Fix Committed
Status in linux source package in Utopic:
  Fix Committed
Status in linux source package in Vivid:
  Fix Committed

Bug description:
  SRU Justification:

  Impact: the card reader does not work on this system after s3.
  Fix: cherry pick a simple patchset only for the certain driver module.
  Testcase: already tested in OEM projects

  Before suspend
  [ 12.896116] rtsx_pci :03:00.0: irq 47 for MSI/MSI-X
  [ 12.896128] rtsx_pci :03:00.0: rtsx_pci_acquire_irq: pcr->msi_en = 1, 
pci->irq = 47
  After resume
  [ 89.354583] rtsx_pci :03:00.0: no hotplug settings from platform

  rmmod rtsx_pci
  modprobe rtsx_pci
  doesn't work

  Reboot
  [ 12.358093] rtsx_pci :03:00.0: irq 47 for MSI/MSI-X
  [ 12.358103] rtsx_pci :03:00.0: rtsx_pci_acquire_irq: pcr->msi_en = 1, 
pci->irq = 47
  [ 12.455971] rtsx_pci: probe of :03:00.0 failed with error -110

  Then driver cannot be loaded

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1359052/+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 1379340] Re: qemu-kvm guest panic for AMD smp trusty guests

[Brad Figg]

This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
trusty' to 'verification-done-trusty'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: verification-needed-trusty

** Tags added: verification-needed-utopic

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

Title:
  qemu-kvm guest panic for AMD smp trusty guests

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

Bug description:
  [Impact]
  When using KVM on an AMD host with a kernel that has CONFIG_DEBUG_RODATA 
enabled, a guest with: multiple vCPUs, and exposing features to the guest such 
as tsc_adjust can cause a divide error on kvm_unlock_kick when booting the VM.

  This impacts kernels 3.12+.

  [Test Case]
  1) Create a VM on an AMD host with appropriate features (Opteron 6xxx for 
example)
  2) Edit virsh xml to have  and multiple 
vCPUs.
  3) Boot VM with VGA console using virt-manager (I couldn't reproduce strictly 
monitoring via virsh console).

  [Fix]
  commit c1118b3602c2329671ad5ec8bdf8e374323d6343 upstream

  --

  Just upgraded OpenStack compute hosts in our public cloud (using qemu-
  kvm via libvirt) from Precise to Trusty (14.04.1), now on kernel
  3.13.0-36-generic with qemu-kvm 2.0.0+dfsg-2ubuntu1.5.

  Following the upgrade, whenever we try to start an smp/multicore
  Trusty guest (existing or new), we run into this panic [1] inside the
  guest just towards the end of boot. This happens consistently for smp
  guests using the Trusty kernel (i.e., it also affects earlier Ubuntus
  using the HWE kernel from Trusty but not their native versions). I
  didn't have any other distro images to hand with 3.13.x kernels, but
  none of the others I tested were affected (in the 3.2 - 3.16 kernel
  range).

  There are scarce similar reports out there, but the one we did find
  pointed to a CPU feature as the trigger. We were running these hosts
  with libvirt cpu mode set to "host-passthrough" (so qemu starts with
  "-cpu host"), on AMD 6200 & 6300 Opteron hardware. Switching the guest
  domains to use cpu mode "host-model" instead works around the issue
  and is perfectly acceptable for most of our users.

  We have various other Intel compute hosts and they don't seem to be
  affected.

  (1)
  [ 11.256924] divide error:  [#1] SMP
  [ 11.258133] Modules linked in: kvm_amd kvm crct10dif_pclmul crc32_pclmul 
ghash_clmulni_intel aesni_intel aes_x86_64 lrw gf128mul glue_helper ablk_helper 
cryptd serio_raw lp parport psmouse floppy
  [ 11.260228] CPU: 0 PID: 0 Comm: swapper/0 Not tainted 3.13.0-36-generic 
#63-Ubuntu
  [ 11.260228] Hardware name: OpenStack Foundation OpenStack Nova, BIOS Bochs 
01/01/2011
  [ 11.260228] task: 81c15480 ti: 81c0 task.ti: 
81c0
  [ 11.260228] RIP: 0010:[] [] 
kvm_unlock_kick+0xa8/0x100
  [ 11.260228] RSP: 0018:88023fc03c98 EFLAGS: 00010046
  [ 11.260228] RAX: 0005 RBX:  RCX: 0001
  [ 11.260228] RDX: 81eaf408 RSI:  RDI: 
  [ 11.260228] RBP: 88023fc03cb8 R08: 81eaf400 R09: 
  [ 11.260228] R10: 880037612cc0 R11: ea0002eb0a00 R12: 8800374a33c0
  [ 11.260228] R13: 0020 R14: 0001 R15: 0286
  [ 11.260228] FS: 7f1e8b538740() GS:88023fc0() 
knlGS:
  [ 11.260228] CS: 0010 DS:  ES:  CR0: 8005003b
  [ 11.260228] CR2: 7f1e8ae09d50 CR3: 01c0e000 CR4: 000406f0
  [ 11.260228] Stack:
  [ 11.260228] 0286 0001 0001 
00c3
  [ 11.260228] 88023fc03cc8 81717ed6 88023fc03ce0 
8172641a
  [ 11.260228] 8800374a33c0 88023fc03d18 810aaeb0 
88023295e000
  [ 11.260228] Call Trace:
  [ 11.260228] 
  [ 11.260228] [] __ticket_unlock_slowpath+0x24/0x34
  [ 11.260228] [] _raw_spin_unlock_irqrestore+0x3a/0x40
  [ 11.260228] [] __wake_up_sync_key+0x50/0x60
  [ 11.260228] [] sock_def_readable+0x3a/0x70
  [ 11.260228] [] packet_rcv+0x2fa/0x430
  [ 11.260228] [] __netif_receive_skb_core+0x360/0x840
  [ 11.260228] [] __netif_receive_skb+0x18/0x60
  [ 11.260228] [] netif_receive_skb+0x23/0x90
  [ 11.260228] [] virtnet_poll+0x4d4/0x850
  [ 11.260228] [] net_rx_action+0x152/0x250
  [ 11.260228] [] __do_softirq+0xec/0x2c0
  [ 11.260228] [] irq_exit+0x105/0x110
  [ 11.260228] [] do_IRQ+0x56/0xc0
  [ 11.260228] [

[Kernel-packages] [Bug 1335478] Re: A new instance of IBM Domino 'bindsock' cannot bind to ports <1024 Kernel 3.13.0-29 and above

[Brad Figg]

This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
precise' to 'verification-done-precise'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: verification-needed-trusty

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

Title:
  A new instance of IBM Domino 'bindsock' cannot bind to ports <1024
  Kernel  3.13.0-29 and above

Status in linux package in Ubuntu:
  Fix Committed
Status in linux-lts-trusty package in Ubuntu:
  Invalid
Status in linux-lts-utopic package in Ubuntu:
  Invalid
Status in linux source package in Lucid:
  Fix Committed
Status in linux-lts-trusty source package in Lucid:
  Invalid
Status in linux-lts-utopic source package in Lucid:
  Invalid
Status in linux source package in Precise:
  Fix Committed
Status in linux-lts-trusty source package in Precise:
  Fix Committed
Status in linux-lts-utopic source package in Precise:
  Invalid
Status in linux source package in Trusty:
  Fix Committed
Status in linux-lts-trusty source package in Trusty:
  Invalid
Status in linux-lts-utopic source package in Trusty:
  Fix Committed
Status in linux source package in Utopic:
  Fix Committed
Status in linux-lts-trusty source package in Utopic:
  Invalid
Status in linux-lts-utopic source package in Utopic:
  Invalid
Status in linux source package in Vivid:
  Fix Committed
Status in linux-lts-trusty source package in Vivid:
  Invalid
Status in linux-lts-utopic source package in Vivid:
  Invalid

Bug description:
  Starting  with kernels  3.2.0-64 and 3.13.0-29  Something has changed
  to once again that prevents IBM Domino's
  "/opt/ibm/domino/notes/latest/linux/bindsock" binary that runs as root
  (setuid) to get ports lower than 1024 for it's LDAP, SMTP, IMAP, POP3,
  and HTTP processes.

  The Domino server reports  the following: :
    "Listener failure: 'bindsock' is missing, not executable, not owned by 
root, not setuid root or user needs net_privaddr privilege."

  This is the same behaviour that was reported and subsequently
  corrected in Bug # 1269053

  ===
  break-fix: dbb490b96584d4e958533fb637f08b557f505657 
6a2a2b3ae0759843b22c929881cc184b00cc63ff

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1335478/+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 1323426] Re: HP Z8000 bluetooth mouse

[Bela Berczi]

I could not pair the Z8000 mouse to 12.04 LTS. Importatnt to mention,
the desktop sometimes freezes during the pairing.

The bluez version is: 4.98-2ubuntu7.2.
The laptop is an HP Envy TouchSmart 15.

I was able to connect other Bluetoth mouses to the op. system except the
reported HP Z8000 mouse.

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

Title:
  HP Z8000 bluetooth mouse

Status in bluez package in Ubuntu:
  Confirmed

Bug description:
  This mouse is a HID over GAT recent HP low power mouse.

  It  is recognized as ALL types bluetooth peripherals not as a mouse!

  The mouse at the end of the installation process (automatic pin
  selection) results as PAIRED  but the connection option is not
  available in the bluetooth setting dialog.

  UBUNTU is last 14.04 full updated at filing bug time.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1323426/+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 1359052] Re: [HP Z1-G2] Realtek card reader [10ec:5249] does not work after suspended on this system

[Brad Figg]

This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
utopic' to 'verification-done-utopic'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!

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

Title:
  [HP Z1-G2] Realtek card reader [10ec:5249] does not work after
  suspended on this system

Status in HWE Next Project:
  Fix Committed
Status in HWE Next trusty series:
  Fix Committed
Status in HWE Next utopic series:
  Fix Committed
Status in HWE Next vivid series:
  Fix Committed
Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Trusty:
  Fix Committed
Status in linux source package in Utopic:
  Fix Committed
Status in linux source package in Vivid:
  Fix Committed

Bug description:
  SRU Justification:

  Impact: the card reader does not work on this system after s3.
  Fix: cherry pick a simple patchset only for the certain driver module.
  Testcase: already tested in OEM projects

  Before suspend
  [ 12.896116] rtsx_pci :03:00.0: irq 47 for MSI/MSI-X
  [ 12.896128] rtsx_pci :03:00.0: rtsx_pci_acquire_irq: pcr->msi_en = 1, 
pci->irq = 47
  After resume
  [ 89.354583] rtsx_pci :03:00.0: no hotplug settings from platform

  rmmod rtsx_pci
  modprobe rtsx_pci
  doesn't work

  Reboot
  [ 12.358093] rtsx_pci :03:00.0: irq 47 for MSI/MSI-X
  [ 12.358103] rtsx_pci :03:00.0: rtsx_pci_acquire_irq: pcr->msi_en = 1, 
pci->irq = 47
  [ 12.455971] rtsx_pci: probe of :03:00.0 failed with error -110

  Then driver cannot be loaded

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1359052/+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 1395465] Re: [ASUS X200MA] Bluetooth does not work

[Pilot6]

I am testing it for two weeks already. It definitely solves the problem.

** Tags removed: verification-needed-utopic
** Tags added: verification-done-utopic

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

Title:
  [ASUS X200MA] Bluetooth does not work

Status in linux package in Ubuntu:
  Triaged
Status in linux source package in Utopic:
  Fix Committed
Status in linux source package in Vivid:
  Triaged

Bug description:
  The 13d3:3408 device is not listed in ath3k and btusb modules.
  It is an AR3012 type device, which requires loadin firmware.
  This code is added to new Windows drivers.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-39-generic 3.13.0-39.66
  ProcVersionSignature: Ubuntu 3.13.0-39.66-generic 3.13.11.8
  Uname: Linux 3.13.0-39-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  pilot6 1960 F pulseaudio
  CurrentDesktop: Unity
  CurrentDmesg: [   32.527666] init: plymouth-upstart-bridge main process 
ended, respawning
  Date: Sun Nov 23 15:24:00 2014
  HibernationDevice: RESUME=UUID=2f501090-6091-423c-abb1-a09f9c524fc3
  InstallationDate: Installed on 2014-10-31 (23 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 05e3:0608 Genesys Logic, Inc. USB-2.0 4-Port HUB
   Bus 001 Device 002: ID 0bda:5603 Realtek Semiconductor Corp.
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. X200MA
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-39-generic.efi.signed 
root=UUID=8b0c6000-31d7-4e41-bfbf-4149ad0122d4 ro quiet splash acpi_osi= 
vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-39-generic N/A
   linux-backports-modules-3.13.0-39-generic  N/A
   linux-firmware 1.127.8
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/11/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X200MA.502
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X200MA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrX200MA.502:bd09/11/2014:svnASUSTeKCOMPUTERINC.:pnX200MA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX200MA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: X200MA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

[Brad Figg]

This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
utopic' to 'verification-done-utopic'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!

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

Title:
  Kernel panic

Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Trusty:
  Fix Committed
Status in linux source package in Utopic:
  Fix Committed
Status in linux source package in Vivid:
  Fix Committed

Bug description:
  SRU Justification

  Impact: Under certain workloads a BUG in the xen-netfront driver is
  getting triggered.

  Fix: Remove the offending BUG, and a related BUG which would have also
  been triggered by the same conditions.

  Test Case: This bug has only been seen under certain workloads
  involving haproxy and has proved challenging to reproduce. The fix has
  been verified by an affected user, with the BUG replaced by a WARN to
  ensure that the conditions which would have triggered the bug were
  actually encountered.

  Regression Potential: The fix has been verified and acked upstream.
  Removing the BUGs will not affect cases which were not crashing
  previously, and cases which were crashing can't really be made much
  worse.

  ---

  I run ubuntu servers 13.04, 13.10, and 14.04 on the AWS cloud.
  Whenever I install haproxy and nginx on the same server, after hitting
  it for a while, a kernel panic is caused. However, the kernel panic
  does not show up in ubuntu 12.04.  The kernel panic is pasted at the
  end of the attachment.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1275879/+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 1399440] Re: Add iwlwifi firmware monitor support in utopic

[Brad Figg]

This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
utopic' to 'verification-done-utopic'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: verification-needed-utopic

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

Title:
  Add iwlwifi firmware monitor support in utopic

Status in linux package in Ubuntu:
  In Progress

Bug description:
  SRU Justification:

  Impact: These patches do not fix a bug. Instead, they help Intel
  collect data from devices which are experiencing errors due to bugs in
  the firmware which will help them fix these bugs.

  Test Case: I have tested these patches to verify that I did not
  observe any regressions with the affected hardware and to verify the
  functionality of the firmware monitor support.

  Regression Potential: The firmware monitor support defaults to being
  disabled and is only enabled when the fw_monitor=1 option is passed to
  iwlwifi, which helps to limit the possibility of regressions under
  normal use. I have also reviewed and tested the patches without
  finding any regressions.

  ---

  These were introduced in 3.17 and then backported to 3.16 by Intel
  [1]. They aren't upstream stable material, but since Intel wireless is
  probably the most widely used wireless hardware among Ubuntu users it
  makes sense for us to take the patches if they will help Intel fix
  bugs in their firmware.

  [1]
  http://permalink.gmane.org/gmane.linux.kernel.wireless.general/129744

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1399440/+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 1400349] Re: [SRU] new arm64 optimized copy_to_user and copy_from_user assembly code

[Brad Figg]

This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
trusty' to 'verification-done-trusty'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: verification-needed-trusty

** Tags added: verification-needed-utopic

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

Title:
  [SRU] new arm64 optimized copy_to_user and copy_from_user assembly
  code

Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Trusty:
  Fix Committed
Status in linux source package in Utopic:
  Fix Committed

Bug description:
  [Impact]
  The copy_{to,from}_user implementations in the Ubuntu kernel are suboptimal. 
Optimized implementations have been submitted upstream and have shown a 
significant improvement in network performance.

  [Test Case]
  Generate traffic from one node to another using iperf.

  [Regression Risk]
  These functions are obviously used heavily throughout the kernel, so a defect 
here could have significant impact. This risk is mitigated by using an 
implementation heavily based on the linaro string libraries (which are used in 
other places already, e.g. glibc), and through active testing of this patch on 
real hardware using a trusty-kernel base. The new patch will also undergo 
regression testing to ensure the memory corruption issue of the previous patch 
does not exist.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1400349/+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 1400349] Re: [SRU] new arm64 optimized copy_to_user and copy_from_user assembly code

[Brad Figg]

This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
utopic' to 'verification-done-utopic'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!

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

Title:
  [SRU] new arm64 optimized copy_to_user and copy_from_user assembly
  code

Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Trusty:
  Fix Committed
Status in linux source package in Utopic:
  Fix Committed

Bug description:
  [Impact]
  The copy_{to,from}_user implementations in the Ubuntu kernel are suboptimal. 
Optimized implementations have been submitted upstream and have shown a 
significant improvement in network performance.

  [Test Case]
  Generate traffic from one node to another using iperf.

  [Regression Risk]
  These functions are obviously used heavily throughout the kernel, so a defect 
here could have significant impact. This risk is mitigated by using an 
implementation heavily based on the linaro string libraries (which are used in 
other places already, e.g. glibc), and through active testing of this patch on 
real hardware using a trusty-kernel base. The new patch will also undergo 
regression testing to ensure the memory corruption issue of the previous patch 
does not exist.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1400349/+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 1398596] Re: [Revert] arm64: optimized copy_to_user and copy_from_user assembly code

[Brad Figg]

This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
utopic' to 'verification-done-utopic'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!

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

Title:
  [Revert] arm64: optimized copy_to_user and copy_from_user assembly
  code

Status in linux package in Ubuntu:
  Triaged
Status in linux source package in Trusty:
  Triaged
Status in linux source package in Utopic:
  Triaged

Bug description:
  [Impact]
  Fixes an issue where the kernel hits unhandled pagefaults when copy_to_user 
is called.

  http://www.spinics.net/lists/arm-kernel/msg381811.html

  [Test Case]
  Put the system under memory pressure.

  [Regression Potential]
  It will cause a performance regression on certain workloads on arm64 systems.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1398596/+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 1395465] Re: [ASUS X200MA] Bluetooth does not work

[Brad Figg]

This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
utopic' to 'verification-done-utopic'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: verification-needed-utopic

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

Title:
  [ASUS X200MA] Bluetooth does not work

Status in linux package in Ubuntu:
  Triaged
Status in linux source package in Utopic:
  Fix Committed
Status in linux source package in Vivid:
  Triaged

Bug description:
  The 13d3:3408 device is not listed in ath3k and btusb modules.
  It is an AR3012 type device, which requires loadin firmware.
  This code is added to new Windows drivers.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-39-generic 3.13.0-39.66
  ProcVersionSignature: Ubuntu 3.13.0-39.66-generic 3.13.11.8
  Uname: Linux 3.13.0-39-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  pilot6 1960 F pulseaudio
  CurrentDesktop: Unity
  CurrentDmesg: [   32.527666] init: plymouth-upstart-bridge main process 
ended, respawning
  Date: Sun Nov 23 15:24:00 2014
  HibernationDevice: RESUME=UUID=2f501090-6091-423c-abb1-a09f9c524fc3
  InstallationDate: Installed on 2014-10-31 (23 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 05e3:0608 Genesys Logic, Inc. USB-2.0 4-Port HUB
   Bus 001 Device 002: ID 0bda:5603 Realtek Semiconductor Corp.
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. X200MA
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-39-generic.efi.signed 
root=UUID=8b0c6000-31d7-4e41-bfbf-4149ad0122d4 ro quiet splash acpi_osi= 
vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-39-generic N/A
   linux-backports-modules-3.13.0-39-generic  N/A
   linux-firmware 1.127.8
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/11/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X200MA.502
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X200MA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrX200MA.502:bd09/11/2014:svnASUSTeKCOMPUTERINC.:pnX200MA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX200MA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: X200MA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1395465/+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 1383589] Re: [Dell Vostro 3546] Wireless key does not work on 14.04

[Brad Figg]

This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
trusty' to 'verification-done-trusty'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: verification-needed-trusty

** Tags added: verification-needed-utopic

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

Title:
  [Dell Vostro 3546] Wireless key does not work on 14.04

Status in HWE Next Project:
  Fix Committed
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Trusty:
  Fix Committed
Status in linux source package in Utopic:
  Fix Committed

Bug description:
  SRU Justification:

  Impact: the wireless key does not work on this system.
  Fix: cherry pick a simple blacklist patch
  Testcase: already tested in OEM projects


  CID: 201404-14998 Dell Vostro 3546

  The wireless key does not work on this system.
  With wireless key press, keycode 240 could be captured by sudo showkey -k, 
but the scancode can't be detected with sudo showkey -s

  With xev:
  KeyPress event, serial 34, synthetic NO, window 0x3e1,
  root 0x9c, subw 0x0, time 9313601, (-66,498), root:(721,550),
  state 0x10, keycode 248 (keysym 0x0, NoSymbol), same_screen YES,
  XLookupString gives 0 bytes:
  XmbLookupString gives 0 bytes:
  XFilterEvent returns: False

  KeyRelease event, serial 34, synthetic NO, window 0x3e1,
  root 0x9c, subw 0x0, time 9313601, (-66,498), root:(721,550),
  state 0x10, keycode 248 (keysym 0x0, NoSymbol), same_screen YES,
  XLookupString gives 0 bytes:
  XFilterEvent returns: False

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-37-generic 3.13.0-37.64
  ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7
  Uname: Linux 3.13.0-37-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  ubuntu 1822 F pulseaudio
   /dev/snd/controlC0:  ubuntu 1822 F pulseaudio
  CRDA:
   country TW:
    (2402 - 2472 @ 40), (3, 27)
    (5270 - 5330 @ 40), (3, 17), DFS
    (5735 - 5815 @ 40), (3, 30)
  CurrentDesktop: Unity
  Date: Tue Oct 21 02:35:48 2014
  HibernationDevice: RESUME=UUID=d93dea8f-2e64-47af-bd90-9671a077bc8f
  InstallationDate: Installed on 2014-10-21 (0 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  MachineType: Dell Inc. Vostro 3546
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-37-generic.efi.signed 
root=UUID=8cb5999b-23f7-4b24-aa9f-e70e7645129f ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-37-generic N/A
   linux-backports-modules-3.13.0-37-generic  N/A
   linux-firmware 1.127.7
  SourcePackage: linux
  StagingDrivers: rts5139
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/05/2014
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A04
  dmi.board.name: 02R010
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A04
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvrA04:bd08/05/2014:svnDellInc.:pnVostro3546:pvrNotSpecified:rvnDellInc.:rn02R010:rvrA04:cvnDellInc.:ct8:cvrNotSpecified:
  dmi.product.name: Vostro 3546
  dmi.product.version: Not Specified
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1383589/+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 1398596] Re: [Revert] arm64: optimized copy_to_user and copy_from_user assembly code

[Brad Figg]

This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
trusty' to 'verification-done-trusty'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: verification-needed-trusty

** Tags added: verification-needed-utopic

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

Title:
  [Revert] arm64: optimized copy_to_user and copy_from_user assembly
  code

Status in linux package in Ubuntu:
  Triaged
Status in linux source package in Trusty:
  Triaged
Status in linux source package in Utopic:
  Triaged

Bug description:
  [Impact]
  Fixes an issue where the kernel hits unhandled pagefaults when copy_to_user 
is called.

  http://www.spinics.net/lists/arm-kernel/msg381811.html

  [Test Case]
  Put the system under memory pressure.

  [Regression Potential]
  It will cause a performance regression on certain workloads on arm64 systems.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1398596/+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 1400289] Re: Hyper-V: drivers:scsi:storvsc: Fix a bug in handling ring buffer failures that may result in I/O freeze

[Brad Figg]

This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
precise' to 'verification-done-precise'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: verification-needed-precise

** Tags added: verification-needed-trusty

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

Title:
  Hyper-V: drivers:scsi:storvsc: Fix a bug in handling ring buffer
  failures that may result in I/O freeze

Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Precise:
  Fix Committed
Status in linux source package in Trusty:
  Fix Committed
Status in linux source package in Utopic:
  Fix Committed
Status in linux source package in Vivid:
  Fix Committed

Bug description:
  As requested by Microsoft.

  ===

  Andy,

  Could you pick up this patch. Customers are hitting this issue on
  Azure (on Canonical images).

  Regards,

  K. Y

  ===
  drivers:scsi:storvsc: Fix a bug in handling ring buffer failures that may 
result in I/O freeze

  When ring buffer returns an error indicating retry, storvsc may not
  return a proper error code to SCSI when bounce buffer is not used.
  This has introduced I/O freeze on RAID running atop storvsc devices.
  This patch fixes it by always returning a proper error code.

  Signed-off-by: Long Li 
  Reviewed-by: K. Y. Srinivasan 
  ---
   drivers/scsi/storvsc_drv.c | 7 +++
   1 file changed, 3 insertions(+), 4 deletions(-)

  diff --git a/drivers/scsi/storvsc_drv.c b/drivers/scsi/storvsc_drv.c
  index e3ba251..4cff0dd 100644
  --- a/drivers/scsi/storvsc_drv.c
  +++ b/drivers/scsi/storvsc_drv.c
  @@ -1688,13 +1688,12 @@ static int storvsc_queuecommand(struct Scsi_Host 
*host, struct scsi_cmnd *scmnd)
  if (ret == -EAGAIN) {
  /* no more space */

  -   if (cmd_request->bounce_sgl_count) {
  +   if (cmd_request->bounce_sgl_count)
  destroy_bounce_buffer(cmd_request->bounce_sgl,
  cmd_request->bounce_sgl_count);

  -   ret = SCSI_MLQUEUE_DEVICE_BUSY;
  -   goto queue_error;
  -   }
  +   ret = SCSI_MLQUEUE_DEVICE_BUSY;
  +   goto queue_error;
  }

  return 0;

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1400289/+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 1400289] Re: Hyper-V: drivers:scsi:storvsc: Fix a bug in handling ring buffer failures that may result in I/O freeze

[Brad Figg]

This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
trusty' to 'verification-done-trusty'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: verification-needed-utopic

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

Title:
  Hyper-V: drivers:scsi:storvsc: Fix a bug in handling ring buffer
  failures that may result in I/O freeze

Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Precise:
  Fix Committed
Status in linux source package in Trusty:
  Fix Committed
Status in linux source package in Utopic:
  Fix Committed
Status in linux source package in Vivid:
  Fix Committed

Bug description:
  As requested by Microsoft.

  ===

  Andy,

  Could you pick up this patch. Customers are hitting this issue on
  Azure (on Canonical images).

  Regards,

  K. Y

  ===
  drivers:scsi:storvsc: Fix a bug in handling ring buffer failures that may 
result in I/O freeze

  When ring buffer returns an error indicating retry, storvsc may not
  return a proper error code to SCSI when bounce buffer is not used.
  This has introduced I/O freeze on RAID running atop storvsc devices.
  This patch fixes it by always returning a proper error code.

  Signed-off-by: Long Li 
  Reviewed-by: K. Y. Srinivasan 
  ---
   drivers/scsi/storvsc_drv.c | 7 +++
   1 file changed, 3 insertions(+), 4 deletions(-)

  diff --git a/drivers/scsi/storvsc_drv.c b/drivers/scsi/storvsc_drv.c
  index e3ba251..4cff0dd 100644
  --- a/drivers/scsi/storvsc_drv.c
  +++ b/drivers/scsi/storvsc_drv.c
  @@ -1688,13 +1688,12 @@ static int storvsc_queuecommand(struct Scsi_Host 
*host, struct scsi_cmnd *scmnd)
  if (ret == -EAGAIN) {
  /* no more space */

  -   if (cmd_request->bounce_sgl_count) {
  +   if (cmd_request->bounce_sgl_count)
  destroy_bounce_buffer(cmd_request->bounce_sgl,
  cmd_request->bounce_sgl_count);

  -   ret = SCSI_MLQUEUE_DEVICE_BUSY;
  -   goto queue_error;
  -   }
  +   ret = SCSI_MLQUEUE_DEVICE_BUSY;
  +   goto queue_error;
  }

  return 0;

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1400289/+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 1396235] Re: Ubuntu - unable to use XMON debugger (running ppc64le on PowerVM)

[Brad Figg]

This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
utopic' to 'verification-done-utopic'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!

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

Title:
  Ubuntu - unable to use XMON debugger (running ppc64le on PowerVM)

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

Bug description:
  SRU Justification:
  [Impact]
  Users of LE Power8 hardware might not be able to use XMON properly.

  [Test Case]
  # echo x > /proc/sysrq-trigger
  This should put us in the xmon debugger without errors.

  [Fix]
  3b8a3c01096925a824ed3272601082289d9c23a5 can be cleanly cherry-picked to 
3.13/3.16. It only adds cpu_to_be32 macros which shouldn't change the behavior 
of BE mode CPUs.

  --

  == Comment: #0 - Laurent Dufour  - 2014-11-25 
10:13:17 ==
  ---Problem Description---
  Kernel fails to invoke xmon, instead print following messages

  # echo x > /proc/sysrq-trigger
  [   47.600133] SysRq : Entering xmon
  cpu 0xf: Vector: 0  at [c000e8603b80]
  pc: c05610c0: write_sysrq_trigger+0x120/0x260
  lr: c05610c0: write_sysrq_trigger+0x120/0x260
  sp: c000e8603ce0
     msr: 80009033
    current = 0xc000ef4a
    paca= 0xc7df3480   softe: 0irq_happened: 0x00
  pid   = 2303, comm = bash
  [   47.607247] Bad kernel stack pointer fc7b4b0 at ee27cc4
  cpu 0xf: Vector: 300 (Data Access) at [c7f37d40]
  pc: 0ee27cc4
  lr: 0ee27c44
  sp: fc7b4b0
     msr: 80001000
     dar: 1000
   dsisr: 4200
    current = 0xc000ef4a
    paca= 0xc7df3480   softe: 0irq_happened: 0x00
  pid   = 2303, comm = bash
  cpu 0xf: Exception 300 (Data Access) in xmon, returning to main loop
  xmon: WARNING: bad recursive fault on cpu 0xf

  ---uname output---
  N/A

  Machine Type = powervm le

  ---System Hang---
   System is hung

  ---Debugger---
  A debugger is not configured

  ---Steps to Reproduce---
   see problem description

  Stack trace output:
   no

  Oops output:
   see problem description

  System Dump Info:
    The system is not configured to capture a system dump.

  This patch has been sent upstream:
  http://patchwork.ozlabs.org/patch/413744/

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1396235/+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 1386490] Re: HP ProLiant m400 nic doesn't work after trusty

[Brad Figg]

This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
utopic' to 'verification-done-utopic'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: verification-needed-utopic

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

Title:
  HP ProLiant m400 nic doesn't work after trusty

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Utopic:
  Fix Committed
Status in linux source package in Vivid:
  Confirmed

Bug description:
  Starting in 3.15, arm64 began defaulting to non-coherent dma_ops:

  commit c7a4a7658d689f664050c45493d79adf053f226e
  Author: Ritesh Harjani 
  Date:   Wed Apr 23 06:29:46 2014 +0100

  arm64: Make default dma_ops to be noncoherent

  Firmware (dtb in the case of the m400) is responsible for telling the
  kernel when a device requires coherent dma_ops. However, as of utopic,
  this property is not being inherited by downstream devices.
  Specifically, the xgene-pcie device is marked as coherent, but the
  devices behind it (mellanox card) still get initialized with non-
  coherent ops.

  This results in the mlx4 driver bailing out with the following messages:
  [   18.703635] mlx4_core :01:00.0: command 0x23 timed out (go bit not 
cleared)
  [   18.710911] mlx4_core :01:00.0: Failed to initialize queue pair table, 
aborting

  
  There's an upstream discussion on the topic here:
http://www.spinics.net/lists/arm-kernel/msg362320.html

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1386490/+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 1383589] Re: [Dell Vostro 3546] Wireless key does not work on 14.04

[Brad Figg]

This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
utopic' to 'verification-done-utopic'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!

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

Title:
  [Dell Vostro 3546] Wireless key does not work on 14.04

Status in HWE Next Project:
  Fix Committed
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Trusty:
  Fix Committed
Status in linux source package in Utopic:
  Fix Committed

Bug description:
  SRU Justification:

  Impact: the wireless key does not work on this system.
  Fix: cherry pick a simple blacklist patch
  Testcase: already tested in OEM projects


  CID: 201404-14998 Dell Vostro 3546

  The wireless key does not work on this system.
  With wireless key press, keycode 240 could be captured by sudo showkey -k, 
but the scancode can't be detected with sudo showkey -s

  With xev:
  KeyPress event, serial 34, synthetic NO, window 0x3e1,
  root 0x9c, subw 0x0, time 9313601, (-66,498), root:(721,550),
  state 0x10, keycode 248 (keysym 0x0, NoSymbol), same_screen YES,
  XLookupString gives 0 bytes:
  XmbLookupString gives 0 bytes:
  XFilterEvent returns: False

  KeyRelease event, serial 34, synthetic NO, window 0x3e1,
  root 0x9c, subw 0x0, time 9313601, (-66,498), root:(721,550),
  state 0x10, keycode 248 (keysym 0x0, NoSymbol), same_screen YES,
  XLookupString gives 0 bytes:
  XFilterEvent returns: False

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-37-generic 3.13.0-37.64
  ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7
  Uname: Linux 3.13.0-37-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  ubuntu 1822 F pulseaudio
   /dev/snd/controlC0:  ubuntu 1822 F pulseaudio
  CRDA:
   country TW:
    (2402 - 2472 @ 40), (3, 27)
    (5270 - 5330 @ 40), (3, 17), DFS
    (5735 - 5815 @ 40), (3, 30)
  CurrentDesktop: Unity
  Date: Tue Oct 21 02:35:48 2014
  HibernationDevice: RESUME=UUID=d93dea8f-2e64-47af-bd90-9671a077bc8f
  InstallationDate: Installed on 2014-10-21 (0 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  MachineType: Dell Inc. Vostro 3546
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-37-generic.efi.signed 
root=UUID=8cb5999b-23f7-4b24-aa9f-e70e7645129f ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-37-generic N/A
   linux-backports-modules-3.13.0-37-generic  N/A
   linux-firmware 1.127.7
  SourcePackage: linux
  StagingDrivers: rts5139
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/05/2014
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A04
  dmi.board.name: 02R010
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A04
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvrA04:bd08/05/2014:svnDellInc.:pnVostro3546:pvrNotSpecified:rvnDellInc.:rn02R010:rvrA04:cvnDellInc.:ct8:cvrNotSpecified:
  dmi.product.name: Vostro 3546
  dmi.product.version: Not Specified
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1383589/+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 1401150] Re: Endianness issue in the VPHN topology update code

[Brad Figg]

This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
trusty' to 'verification-done-trusty'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: verification-needed-trusty

** Tags added: verification-needed-utopic

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

Title:
  Endianness issue in the VPHN topology update code

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

Bug description:
  SRU Justification:

  [Impact]
  The current VPHN code assumes the NUMA toplogy updates data are big endian. 
They are native endian actually since the hypervisor pass them through 
registers. This has a great performance impact on little endian guests.

  [Test Case]
  Install NUMA capable power8 machine in LE mode, install LE guest. Measure 
performance differences in LE guest after applying this patch.

  [Fix]
  commit 5c9fb1899400096c6818181c525897a31d57e488 upstream
  in v3.18-rc2

  A fix has been sent to fix the issue:

  http://patchwork.ozlabs.org/patch/396171/

  Please pick the following commit from Michael Ellermans's tree:

  
http://git.kernel.org/cgit/linux/kernel/git/mpe/linux.git/commit/?id=5c9fb1899400096c6818181c525897a31d57e488

  which reads: "powerpc/vphn: NUMA node code expects big-endian"

  Now upstream:

  commit 5c9fb1899400096c6818181c525897a31d57e488
  Author: Greg Kurz 
  Date:   Wed Oct 15 12:42:58 2014 +0200

  powerpc/vphn: NUMA node code expects big-endian

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1401150/+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 1386473] Re: Not using all cores after upgrade to 14.10

[Brad Figg]

This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
utopic' to 'verification-done-utopic'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: verification-needed-utopic

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

Title:
  Not using all cores after upgrade to 14.10

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Utopic:
  Fix Committed

Bug description:
  I have a computer with two cpus with 4 cores each (physical) but htop
  is only showing activity on two of these 8 cores (number 1 and 3).
  Also, if I run "stress -c 8" top shows only 25% cpu usage. I've
  rebooted the machine and the problem persists. I also took a look at
  the BIOS settings and found nothing there that looked suspicious.

  If I run 'stress -c 8' only two cores go to 100% in htop as stated
  above (cores 1 and 3). If I run 'stress -c 1', one core goes to 100%
  (either core 1 or 3). If I run taskset -cp   I can
  control which core the process is run on. I can actually move it to
  any core that I want (1, 3 or any other one)! So the cores are
  there... the kernel just doesn't seem to use it unless I explicitly
  tell it to with taskset.

   I've verified that this is a regression when moving from [lxk]ubuntu
  14.04 to 14.10. I used pristine lubuntu 14.10 and 14.04 usb sticks to
  test this out and verified that a cpu sysbench test using 8 threads
  took ~15 sec on 14.04 but ~55 sec on 14.10. The computer this is
  happening on is a Dell Precision T5400 tower workstation.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: linux-image-3.16.0-23-generic 3.16.0-23.31
  ProcVersionSignature: Ubuntu 3.16.0-23.31-generic 3.16.4
  Uname: Linux 3.16.0-23-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: amd64
  CRDA: Error: [Errno 2] No such file or directory: 'iw'
  CurrentDesktop: KDE
  Date: Tue Oct 28 00:46:25 2014
  HibernationDevice: RESUME=UUID=20536d9f-ef05-46dd-a104-47367e464fcd
  InstallationDate: Installed on 2014-02-05 (264 days ago)
  InstallationMedia: Ubuntu-Server 13.10 "Saucy Salamander" - Release amd64 
(20131016)
  IwConfig:
   eth0  no wireless extensions.
   
   lono wireless extensions.
  MachineType: Dell Inc. Precision WorkStation T5400
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-23-generic 
root=UUID=28fc4c4c-cecd-4abe-a788-28f69e745845 ro splash quiet
  RelatedPackageVersions:
   linux-restricted-modules-3.16.0-23-generic N/A
   linux-backports-modules-3.16.0-23-generic  N/A
   linux-firmware 1.138
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: Upgraded to utopic on 2014-10-24 (3 days ago)
  dmi.bios.date: 02/01/2008
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A01
  dmi.board.name: 0RW203
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 7
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA01:bd02/01/2008:svnDellInc.:pnPrecisionWorkStationT5400:pvr:rvnDellInc.:rn0RW203:rvrA00:cvnDellInc.:ct7:cvr:
  dmi.product.name: Precision WorkStation T5400
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1386473/+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 1402764] Re: WARNING: CPU: 1 PID: 4940 at /build/buildd/linux-3.13.0/mm/truncate.c:652 pagecache_isize_extended+0xfd/0x110() in 3.13.0-43-generic

[Brad Figg]

This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
trusty' to 'verification-done-trusty'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: verification-needed-trusty

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

Title:
  WARNING: CPU: 1 PID: 4940 at
  /build/buildd/linux-3.13.0/mm/truncate.c:652
  pagecache_isize_extended+0xfd/0x110() in 3.13.0-43-generic

Status in linux package in Ubuntu:
  Invalid
Status in linux-lts-trusty package in Ubuntu:
  Invalid
Status in linux source package in Precise:
  Invalid
Status in linux-lts-trusty source package in Precise:
  Fix Committed
Status in linux source package in Trusty:
  Fix Committed
Status in linux-lts-trusty source package in Trusty:
  Invalid
Status in linux source package in Utopic:
  Invalid
Status in linux-lts-trusty source package in Utopic:
  Invalid
Status in linux source package in Vivid:
  Invalid
Status in linux-lts-trusty source package in Vivid:
  Invalid

Bug description:
  Hi all,

   I have updated my ubuntu 14.04 LTS server this morning. Until then I
  am seeing a lot of errors like:

  [ 4174.782378] WARNING: CPU: 1 PID: 4940 at
  /build/buildd/linux-3.13.0/mm/truncate.c:652
  pagecache_isize_extended+0xfd/0x110()
  [ 4174.782381] Modules linked in: ctr ccm ipt_MASQUERADE iptable_nat
  nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack
  iptable_filter ip_tables x_tables bridge stp llc snd_hda_codec_hdmi
  arc4 nvidia(POX) rtl8187 snd_hda_intel snd_hda_codec snd_hwdep snd_pcm
  snd_page_alloc mac80211 snd_seq_midi snd_seq_midi_event cfg80211
  eeprom_93cx6 snd_rawmidi joydev snd_seq snd_seq_device kvm_amd
  snd_timer kvm drm snd sp5100_tco amd64_edac_mod soundcore edac_core
  edac_mce_amd i2c_piix4 k10temp mac_hid xfs lp parport libcrc32c
  pata_acpi hid_logitech_dj usbhid hid pata_atiixp tg3 ptp pps_core ahci
  libahci
  [ 4174.782433] CPU: 1 PID: 4940 Comm: URL Classifier Tainted: P
  W  OX 3.13.0-43-generic #72-Ubuntu
  [ 4174.782436] Hardware name: HP ProLiant MicroServer, BIOS O41 10/01/2013
  [ 4174.782439]  0009 88006a90bd70 81720bf6
  
  [ 4174.782443]  88006a90bda8 810677cd 1000
  88012e12f598
  [ 4174.782447]   0008 000dd9d0
  88006a90bdb8
  [ 4174.782451] Call Trace:
  [ 4174.782459]  [] dump_stack+0x45/0x56
  [ 4174.782464]  [] warn_slowpath_common+0x7d/0xa0
  [ 4174.782467]  [] warn_slowpath_null+0x1a/0x20
  [ 4174.782472]  [] pagecache_isize_extended+0xfd/0x110
  [ 4174.782476]  [] truncate_setsize+0x27/0x40
  [ 4174.782515]  [] xfs_setattr_size+0x182/0x3e0 [xfs]
  [ 4174.782540]  [] xfs_file_fallocate+0x19c/0x260 [xfs]
  [ 4174.782546]  [] ? __sb_start_write+0x49/0xe0
  [ 4174.782550]  [] do_fallocate+0xf9/0x190
  [ 4174.782554]  [] SyS_fallocate+0x4c/0x80
  [ 4174.782558]  [] system_call_fastpath+0x1a/0x1f
  [ 4174.782561] ---[ end trace aeb446f67bc8e89e ]---

  ===
  break-fix: 90a8020278c1598fafd071736a0846b38510309c 
f55fefd1a5a339b1bd08c120b93312d6eb64a9fb

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1402764/+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 1402714] Re: Radeon driver crash with linux-kernel-3.13.0-43

[Brad Figg]

This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
trusty' to 'verification-done-trusty'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: verification-needed-trusty

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

Title:
  Radeon driver crash with linux-kernel-3.13.0-43

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Trusty:
  Fix Committed

Bug description:
  SRU Justification:
  [Impact]
  Users of Radeon drivers with some hardware experience crashes on boot.

  [Test Case]
  Boot machine with Radeon driver and affected card, ensure it doesn't crash.

  [Fix]
  commit 83d04c39f9048807a8500e575ae3f1718a3f45bb upstream
  in v3.18-rc2+

  --

  There is syslog cut:
  Dec 14 10:45:14 mediacenter kernel: [ 17.365515] [ cut here 
]
  Dec 14 10:45:14 mediacenter kernel: [ 17.365590] kernel BUG at 
/build/buildd/linux-3.13.0/mm/slub.c:3365!
  Dec 14 10:45:14 mediacenter kernel: [ 17.365670] invalid opcode:  [#1] SMP
  Dec 14 10:45:14 mediacenter kernel: [ 17.365727] Modules linked in: ctr ccm 
snd_hda_codec_realtek arc4 snd_hda_codec_hdmi snd_hda_intel snd_hda_codec 
snd_hwdep snd_pcm snd_page_alloc snd_seq_midi rt2800usb snd_seq_midi_event 
rt2x00usb snd_rawmidi rt2800lib rt2x00lib snd_seq mac80211 snd_seq_device 
kvm_amd snd_timer sp5100_tco cfg80211 kvm i2c_piix4 crc_ccitt serio_raw joydev 
snd w83627ehf hwmon_vid soundcore lp mac_hid parport hid_generic usbhid hid 
radeon ahci r8169 psmouse i2c_algo_bit mii ttm libahci drm_kms_helper drm
  Dec 14 10:45:14 mediacenter kernel: [ 17.366337] CPU: 1 PID: 1301 Comm: Xorg 
Not tainted 3.13.0-43-generic #72-Ubuntu
  Dec 14 10:45:14 mediacenter kernel: [ 17.366427] Hardware name: To Be Filled 
By O.E.M. To Be Filled By O.E.M./E350M1/USB3, BIOS P1.60 05/21/2012
  Dec 14 10:45:14 mediacenter kernel: [ 17.366542] task: ec1e2700 ti: ec112000 
task.ti: ec112000
  Dec 14 10:45:14 mediacenter kernel: [ 17.366608] EIP: 0060:[] 
EFLAGS: 00213246 CPU: 1
  Dec 14 10:45:14 mediacenter kernel: [ 17.366683] EIP is at kfree+0x101/0x110
  Dec 14 10:45:14 mediacenter kernel: [ 17.366730] EAX: 8000 EBX:  
ECX: 00010005 EDX: 8000
  Dec 14 10:45:14 mediacenter kernel: [ 17.366804] ESI: f76fe480 EDI: f8d24d08 
EBP: ec113b88 ESP: ec113b6c
  Dec 14 10:45:14 mediacenter kernel: [ 17.366879] DS: 007b ES: 007b FS: 00d8 
GS: 00e0 SS: 0068
  Dec 14 10:45:14 mediacenter kernel: [ 17.366944] CR0: 80050033 CR2: b64b8024 
CR3: 35b5d000 CR4: 07f0
  Dec 14 10:45:14 mediacenter kernel: [ 17.367018] Stack:
  Dec 14 10:45:14 mediacenter kernel: [ 17.367044] 004c ec113b88 ec113be4 
00024414  f48f2000 f6137400 ec113c4c
  Dec 14 10:45:14 mediacenter kernel: [ 17.367151] f8d24d08  f60bc656 
c736  00aac9a0 712c 7048
  Dec 14 10:45:14 mediacenter kernel: [ 17.367257] 7044   
ec1d2a80 f48f2000 f6137400 f584c800 ec113be0
  Dec 14 10:45:14 mediacenter kernel: [ 17.367362] Call Trace:
  Dec 14 10:45:14 mediacenter kernel: [ 17.367457] [] 
evergreen_hdmi_setmode+0x738/0x9a0 [radeon]
  Dec 14 10:45:14 mediacenter kernel: [ 17.367565] [] ? 
drm_detect_hdmi_monitor+0x69/0xb0 [drm]
  Dec 14 10:45:14 mediacenter kernel: [ 17.367693] [] ? 
radeon_atom_encoder_dpms+0xa7/0x1d0 [radeon]
  Dec 14 10:45:14 mediacenter kernel: [ 17.367824] [] ? 
evergreen_hdmi_enable+0xce/0xf0 [radeon]
  Dec 14 10:45:14 mediacenter kernel: [ 17.367955] [] 
radeon_atom_encoder_mode_set+0x149/0x2c0 [radeon]
  Dec 14 10:45:14 mediacenter kernel: [ 17.368046] [] 
drm_crtc_helper_set_mode+0x4d6/0x550 [drm_kms_helper]
  Dec 14 10:45:14 mediacenter kernel: [ 17.368179] [] 
radeon_property_change_mode.isra.1+0x34/0x40 [radeon]
  Dec 14 10:45:14 mediacenter kernel: [ 17.368305] [] 
radeon_connector_set_property+0x199/0x330 [radeon]
  Dec 14 10:45:14 mediacenter kernel: [ 17.368416] [] 
drm_mode_obj_set_property_ioctl+0x149/0x3c0 [drm]
  Dec 14 10:45:14 mediacenter kernel: [ 17.368521] [] ? 
drm_mode_obj_set_property_ioctl+0x3c0/0x3c0 [drm]
  Dec 14 10:45:14 mediacenter kernel: [ 17.368628] [] 
drm_mode_connector_property_set_ioctl+0x33/0x40 [drm]
  Dec 14 10:45:14 mediacenter kernel: [ 17.368730] [] 
drm_ioctl+0x472/0x500 [drm]
  Dec 14 10:45:14 mediacenter kernel: [ 17.368817] [] ? 
drm_mode_obj_set_property_ioctl+0x3c0/0x3c0 [drm]
  Dec 14 10:45:14 mediacenter kernel: [ 17.368907] [] ? 
handle_mm_fault+0x34d/0x8d0
  Dec 14 10:45:14 mediacenter kernel: [ 17.368974] [] ? 
__pm_runtime_resume+0x51/0x70
  Dec 14 10:45:14 mediacen

[Kernel-packages] [Bug 1400289] Re: Hyper-V: drivers:scsi:storvsc: Fix a bug in handling ring buffer failures that may result in I/O freeze

[Brad Figg]

This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
utopic' to 'verification-done-utopic'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!

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

Title:
  Hyper-V: drivers:scsi:storvsc: Fix a bug in handling ring buffer
  failures that may result in I/O freeze

Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Precise:
  Fix Committed
Status in linux source package in Trusty:
  Fix Committed
Status in linux source package in Utopic:
  Fix Committed
Status in linux source package in Vivid:
  Fix Committed

Bug description:
  As requested by Microsoft.

  ===

  Andy,

  Could you pick up this patch. Customers are hitting this issue on
  Azure (on Canonical images).

  Regards,

  K. Y

  ===
  drivers:scsi:storvsc: Fix a bug in handling ring buffer failures that may 
result in I/O freeze

  When ring buffer returns an error indicating retry, storvsc may not
  return a proper error code to SCSI when bounce buffer is not used.
  This has introduced I/O freeze on RAID running atop storvsc devices.
  This patch fixes it by always returning a proper error code.

  Signed-off-by: Long Li 
  Reviewed-by: K. Y. Srinivasan 
  ---
   drivers/scsi/storvsc_drv.c | 7 +++
   1 file changed, 3 insertions(+), 4 deletions(-)

  diff --git a/drivers/scsi/storvsc_drv.c b/drivers/scsi/storvsc_drv.c
  index e3ba251..4cff0dd 100644
  --- a/drivers/scsi/storvsc_drv.c
  +++ b/drivers/scsi/storvsc_drv.c
  @@ -1688,13 +1688,12 @@ static int storvsc_queuecommand(struct Scsi_Host 
*host, struct scsi_cmnd *scmnd)
  if (ret == -EAGAIN) {
  /* no more space */

  -   if (cmd_request->bounce_sgl_count) {
  +   if (cmd_request->bounce_sgl_count)
  destroy_bounce_buffer(cmd_request->bounce_sgl,
  cmd_request->bounce_sgl_count);

  -   ret = SCSI_MLQUEUE_DEVICE_BUSY;
  -   goto queue_error;
  -   }
  +   ret = SCSI_MLQUEUE_DEVICE_BUSY;
  +   goto queue_error;
  }

  return 0;

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1400289/+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 1401150] Re: Endianness issue in the VPHN topology update code

[Brad Figg]

This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
utopic' to 'verification-done-utopic'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!

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

Title:
  Endianness issue in the VPHN topology update code

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

Bug description:
  SRU Justification:

  [Impact]
  The current VPHN code assumes the NUMA toplogy updates data are big endian. 
They are native endian actually since the hypervisor pass them through 
registers. This has a great performance impact on little endian guests.

  [Test Case]
  Install NUMA capable power8 machine in LE mode, install LE guest. Measure 
performance differences in LE guest after applying this patch.

  [Fix]
  commit 5c9fb1899400096c6818181c525897a31d57e488 upstream
  in v3.18-rc2

  A fix has been sent to fix the issue:

  http://patchwork.ozlabs.org/patch/396171/

  Please pick the following commit from Michael Ellermans's tree:

  
http://git.kernel.org/cgit/linux/kernel/git/mpe/linux.git/commit/?id=5c9fb1899400096c6818181c525897a31d57e488

  which reads: "powerpc/vphn: NUMA node code expects big-endian"

  Now upstream:

  commit 5c9fb1899400096c6818181c525897a31d57e488
  Author: Greg Kurz 
  Date:   Wed Oct 15 12:42:58 2014 +0200

  powerpc/vphn: NUMA node code expects big-endian

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1401150/+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 1397928] Re: Feature: Add powernv-cpufreq upstream bug fixes to ubuntu-14.04.02 kernel

[Brad Figg]

This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
utopic' to 'verification-done-utopic'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: verification-needed-utopic

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

Title:
  Feature: Add powernv-cpufreq upstream bug fixes to ubuntu-14.04.02
  kernel

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Utopic:
  Fix Committed

Bug description:
  SRU Justification:
  [Impact]
  Users of ppc64el arches could have issues related to powernv-cpufreq.
  [Test Case]
  Ensure the pstate of various cpus respond properly after 
hotswapping/kexec/reboot events.
  [Fix]
  789ca24 cpufreq: Allow stop CPU callback to be used by all cpufreq drivers
  b120339 cpufreq: powernv: Set the pstate of the last hotplugged out cpu in 
policy->cpus to minimum
  cf30af76 cpufreq: powernv: Set the cpus to nominal frequency during 
reboot/kexec

  --

  Problem Description
  ===
  This is a feature request to include the following upstream(3.18) commits to 
Ubuntu-14.04.02 kernel.
  1)789ca2 cpufreq: Allow stop CPU callback to be used by all cpufreq drivers
  2)b12033 cpufreq: powernv: Set the pstate of the last hotplugged out cpu in 
policy->cpus to minimum
  3)cf30af cpufreq: powernv: Set the cpus to nominal frequency during 
reboot/kexec

  == Comment: #1 - Shilpasri G. Bhat   ==
  This patch was applied on top of  kernel(3.16) 
ubuntu-trusty/lts-backport-utopic
  (8bf5db16 UBUNTU: Ubuntu-lts-3.16.0-26.34~14.04.1)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1397928/+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 1396235] Re: Ubuntu - unable to use XMON debugger (running ppc64le on PowerVM)

[Brad Figg]

This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
trusty' to 'verification-done-trusty'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: verification-needed-trusty

** Tags added: verification-needed-utopic

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

Title:
  Ubuntu - unable to use XMON debugger (running ppc64le on PowerVM)

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

Bug description:
  SRU Justification:
  [Impact]
  Users of LE Power8 hardware might not be able to use XMON properly.

  [Test Case]
  # echo x > /proc/sysrq-trigger
  This should put us in the xmon debugger without errors.

  [Fix]
  3b8a3c01096925a824ed3272601082289d9c23a5 can be cleanly cherry-picked to 
3.13/3.16. It only adds cpu_to_be32 macros which shouldn't change the behavior 
of BE mode CPUs.

  --

  == Comment: #0 - Laurent Dufour  - 2014-11-25 
10:13:17 ==
  ---Problem Description---
  Kernel fails to invoke xmon, instead print following messages

  # echo x > /proc/sysrq-trigger
  [   47.600133] SysRq : Entering xmon
  cpu 0xf: Vector: 0  at [c000e8603b80]
  pc: c05610c0: write_sysrq_trigger+0x120/0x260
  lr: c05610c0: write_sysrq_trigger+0x120/0x260
  sp: c000e8603ce0
     msr: 80009033
    current = 0xc000ef4a
    paca= 0xc7df3480   softe: 0irq_happened: 0x00
  pid   = 2303, comm = bash
  [   47.607247] Bad kernel stack pointer fc7b4b0 at ee27cc4
  cpu 0xf: Vector: 300 (Data Access) at [c7f37d40]
  pc: 0ee27cc4
  lr: 0ee27c44
  sp: fc7b4b0
     msr: 80001000
     dar: 1000
   dsisr: 4200
    current = 0xc000ef4a
    paca= 0xc7df3480   softe: 0irq_happened: 0x00
  pid   = 2303, comm = bash
  cpu 0xf: Exception 300 (Data Access) in xmon, returning to main loop
  xmon: WARNING: bad recursive fault on cpu 0xf

  ---uname output---
  N/A

  Machine Type = powervm le

  ---System Hang---
   System is hung

  ---Debugger---
  A debugger is not configured

  ---Steps to Reproduce---
   see problem description

  Stack trace output:
   no

  Oops output:
   see problem description

  System Dump Info:
    The system is not configured to capture a system dump.

  This patch has been sent upstream:
  http://patchwork.ozlabs.org/patch/413744/

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1396235/+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 1393317] Re: Intel 7265 [8086:095b] Wireless disconnect automatically

[Brad Figg]

This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
trusty' to 'verification-done-trusty'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: verification-needed-trusty

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

Title:
  Intel 7265 [8086:095b] Wireless disconnect automatically

Status in HWE Next Project:
  In Progress
Status in linux package in Ubuntu:
  Fix Committed
Status in linux-firmware package in Ubuntu:
  In Progress
Status in linux source package in Trusty:
  Fix Committed
Status in linux-firmware source package in Trusty:
  Confirmed
Status in linux source package in Utopic:
  Fix Released
Status in linux-firmware source package in Utopic:
  Confirmed

Bug description:
  SRU Justification:

  Impact: Intel's latest wireless adapter will disconnect automatically
  Fix: bump firmware API version to 9(the version 9 firmwares of 3160, 7260 and 
7265 were already in trusty, but need an upgrade from 23.214.9.0 to the latest 
25.222.9.0)
  Testcase: already tested with Intel 7265 [8086:095b] in OEM projects.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1393317/+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 1404335] [NEW] xgene: BUG: soft lockup - CPU#0 stuck for 23s! [halt:2059] on poweroff

[Craig Magina]

Public bug reported:

[Impact]
Fixes an issue where after the system halts the cpu starts to experience soft 
lockups.

[Test Case]
The most reliable means of reproducing this issue is to 'sudo poweroff' the 
system from the console.

[Regression Potential]
These patches are upstream patches that have been in the utopic kernel for 
quite a while and only affect the arm64 architecture.

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

Title:
  xgene: BUG: soft lockup - CPU#0 stuck for 23s! [halt:2059] on poweroff

Status in linux package in Ubuntu:
  New

Bug description:
  [Impact]
  Fixes an issue where after the system halts the cpu starts to experience soft 
lockups.

  [Test Case]
  The most reliable means of reproducing this issue is to 'sudo poweroff' the 
system from the console.

  [Regression Potential]
  These patches are upstream patches that have been in the utopic kernel for 
quite a while and only affect the arm64 architecture.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1404335/+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 1401935] Re: [Acer Aspire V3-371] Touchpad stops working after suspend

[raggar]

Hello Christopher,

Thanks for your help! I tested the most recent kernel:
3.18.1-031801-generic

In this kernel the touchpad keeps working after a suspend. Do you need
me to test this on a lower kernel as well?

I changed this to confirmed and added the tags.

** Tags added: kernel-fixed-upstream kernel-fixed-upstream-3.18

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

Title:
  [Acer Aspire V3-371] Touchpad stops working after suspend

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The touchpad stops working after suspend. From /proc/bus/input/devices:
  I: Bus=0018 Vendor=06cb Product=2991 Version=0100
  N: Name="SYN1B7F:01 06CB:2991 UNKNOWN"
  P: Phys=
  S: 
Sysfs=/devices/pci:00/INT33C3:00/i2c-7/i2c-SYN1B7F:01/0018:06CB:2991.0002/input/input15
  U: Uniq=
  H: Handlers=mouse0 event13
  B: PROP=1
  B: EV=b
  B: KEY=6420 1 0 0 0 0
  B: ABS=2608003

  WORKAROUND: sudo modprobe -r i2c_hid && sudo modprobe i2c_hid

  ---
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  martijn2357 F pulseaudio
   /dev/snd/controlC0:  martijn2357 F pulseaudio
  DistroRelease: Ubuntu 14.10
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2014-12-08 (4 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
  MachineType: Acer Aspire V3-371
  Package: linux (not installed)
  ProcEnviron:
   LANGUAGE=nl
   TERM=xterm
   PATH=(custom, no user)
   LANG=nl_NL.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-28-generic.efi.signed 
root=UUID=c404c12a-11b8-47c7-a6bc-24e7a572025b ro i8042.nomux=1 i8042.reset 
quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.16.0-28.37-generic 3.16.7-ckt1
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-3.16.0-28-generic N/A
   linux-backports-modules-3.16.0-28-generic  N/A
   linux-firmware 1.138
  Tags:  utopic
  Uname: Linux 3.16.0-28-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

  _MarkForUpload: True
  dmi.bios.date: 09/05/2014
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.12
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Aspire V3-371
  dmi.board.vendor: Acer
  dmi.board.version: V1.12
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V1.12
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.12:bd09/05/2014:svnAcer:pnAspireV3-371:pvrV1.12:rvnAcer:rnAspireV3-371:rvrV1.12:cvnAcer:ct10:cvrV1.12:
  dmi.product.name: Aspire V3-371
  dmi.product.version: V1.12
  dmi.sys.vendor: Acer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1401935/+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 1401935] Re: [Acer Aspire V3-371] Touchpad stops working after suspend

[raggar]

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

Title:
  [Acer Aspire V3-371] Touchpad stops working after suspend

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The touchpad stops working after suspend. From /proc/bus/input/devices:
  I: Bus=0018 Vendor=06cb Product=2991 Version=0100
  N: Name="SYN1B7F:01 06CB:2991 UNKNOWN"
  P: Phys=
  S: 
Sysfs=/devices/pci:00/INT33C3:00/i2c-7/i2c-SYN1B7F:01/0018:06CB:2991.0002/input/input15
  U: Uniq=
  H: Handlers=mouse0 event13
  B: PROP=1
  B: EV=b
  B: KEY=6420 1 0 0 0 0
  B: ABS=2608003

  WORKAROUND: sudo modprobe -r i2c_hid && sudo modprobe i2c_hid

  ---
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  martijn2357 F pulseaudio
   /dev/snd/controlC0:  martijn2357 F pulseaudio
  DistroRelease: Ubuntu 14.10
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2014-12-08 (4 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
  MachineType: Acer Aspire V3-371
  Package: linux (not installed)
  ProcEnviron:
   LANGUAGE=nl
   TERM=xterm
   PATH=(custom, no user)
   LANG=nl_NL.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-28-generic.efi.signed 
root=UUID=c404c12a-11b8-47c7-a6bc-24e7a572025b ro i8042.nomux=1 i8042.reset 
quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.16.0-28.37-generic 3.16.7-ckt1
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-3.16.0-28-generic N/A
   linux-backports-modules-3.16.0-28-generic  N/A
   linux-firmware 1.138
  Tags:  utopic
  Uname: Linux 3.16.0-28-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

  _MarkForUpload: True
  dmi.bios.date: 09/05/2014
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.12
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Aspire V3-371
  dmi.board.vendor: Acer
  dmi.board.version: V1.12
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V1.12
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.12:bd09/05/2014:svnAcer:pnAspireV3-371:pvrV1.12:rvnAcer:rnAspireV3-371:rvrV1.12:cvnAcer:ct10:cvrV1.12:
  dmi.product.name: Aspire V3-371
  dmi.product.version: V1.12
  dmi.sys.vendor: Acer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1401935/+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 1385937] Re: [Acer Travelmate B115-M] Synaptic touchpad not correctly detected in kernel 3.16 after upgrade to Ubuntu 14.10

[holger_p.]

** Tags added: unable-to-bisect

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

Title:
  [Acer Travelmate B115-M] Synaptic touchpad not correctly detected in
  kernel 3.16 after upgrade to Ubuntu 14.10

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Since the upgrade from Ubuntu 14.04 to 14.10 the Synaptic touchpad is
  not detected entirely. The secondary key (right mouse button) does not
  work with kernel 3.16.0-23-generic. Falling back under Ubuntu 14.10 to
  the kernel 3.13.0-37-generic the Synaptic touchpad is detected fully
  and right mouse button works again.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: linux-image-3.16.0-23-generic 3.16.0-23.31
  ProcVersionSignature: Ubuntu 3.16.0-23.31-generic 3.16.4
  Uname: Linux 3.16.0-23-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  hpannenb   2336 F pulseaudio
  CurrentDesktop: Unity
  Date: Sun Oct 26 19:45:20 2014
  HibernationDevice: RESUME=UUID=8aa00459-6b0d-4baf-84e4-7f945406d6b2
  InstallationDate: Installed on 2014-10-10 (15 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 1bcf:2c57 Sunplus Innovation Technology Inc. 
   Bus 001 Device 004: ID 0489:e046 Foxconn / Hon Hai 
   Bus 001 Device 002: ID 05e3:0608 Genesys Logic, Inc. Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Acer TravelMate B115-M
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-23-generic.efi.signed 
root=UUID=902f1410-63a6-41f1-893c-ab5e74543832 ro acpi_backlight=vendor quiet 
splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.16.0-23-generic N/A
   linux-backports-modules-3.16.0-23-generic  N/A
   linux-firmware 1.138
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/27/2014
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.22
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: Roxy
  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.22:bd08/27/2014:svnAcer:pnTravelMateB115-M:pvrV1.22:rvnAcer:rnRoxy:rvrType2-A01BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion:
  dmi.product.name: TravelMate B115-M
  dmi.product.version: V1.22
  dmi.sys.vendor: Acer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1385937/+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 1335478] Re: A new instance of IBM Domino 'bindsock' cannot bind to ports <1024 Kernel 3.13.0-29 and above

[Ben Erickson]

I will try to open a service request based on this information. Is there
anything more specific information about which of the fields is passing
on the junk?

Perhaps this could actually get fixed!

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

Title:
  A new instance of IBM Domino 'bindsock' cannot bind to ports <1024
  Kernel  3.13.0-29 and above

Status in linux package in Ubuntu:
  Fix Committed
Status in linux-lts-trusty package in Ubuntu:
  Invalid
Status in linux-lts-utopic package in Ubuntu:
  Invalid
Status in linux source package in Lucid:
  Fix Committed
Status in linux-lts-trusty source package in Lucid:
  Invalid
Status in linux-lts-utopic source package in Lucid:
  Invalid
Status in linux source package in Precise:
  Fix Committed
Status in linux-lts-trusty source package in Precise:
  Fix Committed
Status in linux-lts-utopic source package in Precise:
  Invalid
Status in linux source package in Trusty:
  Fix Committed
Status in linux-lts-trusty source package in Trusty:
  Invalid
Status in linux-lts-utopic source package in Trusty:
  Fix Committed
Status in linux source package in Utopic:
  Fix Committed
Status in linux-lts-trusty source package in Utopic:
  Invalid
Status in linux-lts-utopic source package in Utopic:
  Invalid
Status in linux source package in Vivid:
  Fix Committed
Status in linux-lts-trusty source package in Vivid:
  Invalid
Status in linux-lts-utopic source package in Vivid:
  Invalid

Bug description:
  Starting  with kernels  3.2.0-64 and 3.13.0-29  Something has changed
  to once again that prevents IBM Domino's
  "/opt/ibm/domino/notes/latest/linux/bindsock" binary that runs as root
  (setuid) to get ports lower than 1024 for it's LDAP, SMTP, IMAP, POP3,
  and HTTP processes.

  The Domino server reports  the following: :
    "Listener failure: 'bindsock' is missing, not executable, not owned by 
root, not setuid root or user needs net_privaddr privilege."

  This is the same behaviour that was reported and subsequently
  corrected in Bug # 1269053

  ===
  break-fix: dbb490b96584d4e958533fb637f08b557f505657 
6a2a2b3ae0759843b22c929881cc184b00cc63ff

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1335478/+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 1391476] Re: [MacBookPro11, 1] Laptop wakes up while lid closed

[Erlenmayr]

Now I have edited /proc/acpi/wakeup for four weeks and it did not happen
again a single time. It really is the XHC1 (USB3) interface waking up
the computer.

My still unanswered question again: Why is this b* enabled by
default in the first place? A decade before this bug I already
considered it annoying that sleeping computers could be woken up by key
strokes. And now in times of laptops, this is a way to kill hardware.
People close their lid and put the computer into a case or bag. It
should never wake up. An unintended wakeup is a thousand times worse
than a failing wakeup.

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

Title:
  [MacBookPro11,1] Laptop wakes up while lid closed

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Same behavior when using pm-suspend. This bug may be CRITICAL, because
  it is hard to notice whether the laptop waking up, especially because
  that does not always happen immediately. Getting to sleep takes up to
  30 seconds. Hardware damage may be a result of waking up while lid is
  closed, for example if laptop is transported in a bag.

  I suspect that the problem comes from the Intel video driver. See
  extract from kern.log.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: linux-image-3.16.0-24-generic 3.16.0-24.32
  ProcVersionSignature: Ubuntu 3.16.0-24.32-generic 3.16.4
  Uname: Linux 3.16.0-24-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  stephan2266 F pulseaudio
   /dev/snd/controlC1:  stephan2266 F pulseaudio
  CurrentDesktop: Unity
  CurrentDmesg: Error: command ['sh', '-c', 'dmesg | comm -13 --nocheck-order 
/var/log/dmesg -'] failed with exit code 1: comm: /var/log/dmesg: Permission 
denied
  Date: Tue Nov 11 12:11:02 2014
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2014-10-08 (33 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 05ac:0259 Apple, Inc. 
   Bus 001 Device 006: ID 05ac:8289 Apple, Inc. 
   Bus 001 Device 002: ID 0a5c:4500 Broadcom Corp. BCM2046B1 USB 2.0 Hub (part 
of BCM2046 Bluetooth)
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Apple Inc. MacBookPro11,1
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-24-generic.efi.signed 
root=UUID=d3ef8cca-2c30-46c5-88cc-a5f523abf8ac ro quiet splash vt.handoff=7
  SourcePackage: linux
  UpgradeStatus: Upgraded to utopic on 2014-10-17 (24 days ago)
  WifiSyslog:
   
  dmi.bios.date: 02/12/2014
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: MBP111.88Z.0138.B07.1402121134
  dmi.board.asset.tag: Base Board Asset Tag#
  dmi.board.name: Mac-189A3D4F975D5FFC
  dmi.board.vendor: Apple Inc.
  dmi.board.version: MacBookPro11,1
  dmi.chassis.type: 10
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-189A3D4F975D5FFC
  dmi.modalias: 
dmi:bvnAppleInc.:bvrMBP111.88Z.0138.B07.1402121134:bd02/12/2014:svnAppleInc.:pnMacBookPro11,1:pvr1.0:rvnAppleInc.:rnMac-189A3D4F975D5FFC:rvrMacBookPro11,1:cvnAppleInc.:ct10:cvrMac-189A3D4F975D5FFC:
  dmi.product.name: MacBookPro11,1
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.
  --- 
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC1D0p:   stephan2266 F...m pulseaudio
   /dev/snd/controlC0:  stephan2266 F pulseaudio
   /dev/snd/controlC1:  stephan2266 F pulseaudio
  CurrentDesktop: Unity
  CurrentDmesg: Error: command ['sh', '-c', 'dmesg | comm -13 --nocheck-order 
/var/log/dmesg -'] failed with exit code 1: comm: /var/log/dmesg: Permission 
denied
  DistroRelease: Ubuntu 14.10
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2014-10-08 (34 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  MachineType: Apple Inc. MacBookPro11,1
  NonfreeKernelModules: wl
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-24-generic.efi.signed 
root=UUID=d3ef8cca-2c30-46c5-88cc-a5f523abf8ac ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.16.0-24.32-generic 3.16.4
  Tags:  utopic
  Uname: Linux 3.16.0-24-generic x86_64
  UpgradeStatus: Upgraded to utopic on 2014-10-17 (24 days ago)
  UserGroups: sudo
  WifiSyslog:
   
  _MarkForUpload: True
  dmi.bios.date: 02/12/2014
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: MBP111.88Z.0138.B07.1402121134
  dmi.board.asset.tag: Base Board Asset Tag#
  dmi.board.name: Mac-189A3D4F975D5FFC
  dmi.board.vendor: Apple Inc.
  dmi.board.version: MacBookPro11,1
  dmi.chassis.type: 10
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis

[Kernel-packages] [Bug 1391476] Re: [MacBookPro11, 1] Laptop wakes up while lid closed

[Bertails]

@penalvch, as stated by @erlenmayr, the bug is the same in 14.04.01.

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

Title:
  [MacBookPro11,1] Laptop wakes up while lid closed

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Same behavior when using pm-suspend. This bug may be CRITICAL, because
  it is hard to notice whether the laptop waking up, especially because
  that does not always happen immediately. Getting to sleep takes up to
  30 seconds. Hardware damage may be a result of waking up while lid is
  closed, for example if laptop is transported in a bag.

  I suspect that the problem comes from the Intel video driver. See
  extract from kern.log.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: linux-image-3.16.0-24-generic 3.16.0-24.32
  ProcVersionSignature: Ubuntu 3.16.0-24.32-generic 3.16.4
  Uname: Linux 3.16.0-24-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  stephan2266 F pulseaudio
   /dev/snd/controlC1:  stephan2266 F pulseaudio
  CurrentDesktop: Unity
  CurrentDmesg: Error: command ['sh', '-c', 'dmesg | comm -13 --nocheck-order 
/var/log/dmesg -'] failed with exit code 1: comm: /var/log/dmesg: Permission 
denied
  Date: Tue Nov 11 12:11:02 2014
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2014-10-08 (33 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 05ac:0259 Apple, Inc. 
   Bus 001 Device 006: ID 05ac:8289 Apple, Inc. 
   Bus 001 Device 002: ID 0a5c:4500 Broadcom Corp. BCM2046B1 USB 2.0 Hub (part 
of BCM2046 Bluetooth)
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Apple Inc. MacBookPro11,1
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-24-generic.efi.signed 
root=UUID=d3ef8cca-2c30-46c5-88cc-a5f523abf8ac ro quiet splash vt.handoff=7
  SourcePackage: linux
  UpgradeStatus: Upgraded to utopic on 2014-10-17 (24 days ago)
  WifiSyslog:
   
  dmi.bios.date: 02/12/2014
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: MBP111.88Z.0138.B07.1402121134
  dmi.board.asset.tag: Base Board Asset Tag#
  dmi.board.name: Mac-189A3D4F975D5FFC
  dmi.board.vendor: Apple Inc.
  dmi.board.version: MacBookPro11,1
  dmi.chassis.type: 10
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-189A3D4F975D5FFC
  dmi.modalias: 
dmi:bvnAppleInc.:bvrMBP111.88Z.0138.B07.1402121134:bd02/12/2014:svnAppleInc.:pnMacBookPro11,1:pvr1.0:rvnAppleInc.:rnMac-189A3D4F975D5FFC:rvrMacBookPro11,1:cvnAppleInc.:ct10:cvrMac-189A3D4F975D5FFC:
  dmi.product.name: MacBookPro11,1
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.
  --- 
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC1D0p:   stephan2266 F...m pulseaudio
   /dev/snd/controlC0:  stephan2266 F pulseaudio
   /dev/snd/controlC1:  stephan2266 F pulseaudio
  CurrentDesktop: Unity
  CurrentDmesg: Error: command ['sh', '-c', 'dmesg | comm -13 --nocheck-order 
/var/log/dmesg -'] failed with exit code 1: comm: /var/log/dmesg: Permission 
denied
  DistroRelease: Ubuntu 14.10
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2014-10-08 (34 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  MachineType: Apple Inc. MacBookPro11,1
  NonfreeKernelModules: wl
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-24-generic.efi.signed 
root=UUID=d3ef8cca-2c30-46c5-88cc-a5f523abf8ac ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.16.0-24.32-generic 3.16.4
  Tags:  utopic
  Uname: Linux 3.16.0-24-generic x86_64
  UpgradeStatus: Upgraded to utopic on 2014-10-17 (24 days ago)
  UserGroups: sudo
  WifiSyslog:
   
  _MarkForUpload: True
  dmi.bios.date: 02/12/2014
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: MBP111.88Z.0138.B07.1402121134
  dmi.board.asset.tag: Base Board Asset Tag#
  dmi.board.name: Mac-189A3D4F975D5FFC
  dmi.board.vendor: Apple Inc.
  dmi.board.version: MacBookPro11,1
  dmi.chassis.type: 10
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-189A3D4F975D5FFC
  dmi.modalias: 
dmi:bvnAppleInc.:bvrMBP111.88Z.0138.B07.1402121134:bd02/12/2014:svnAppleInc.:pnMacBookPro11,1:pvr1.0:rvnAppleInc.:rnMac-189A3D4F975D5FFC:rvrMacBookPro11,1:cvnAppleInc.:ct10:cvrMac-189A3D4F975D5FFC:
  dmi.product.name: MacBookPro11,1
  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/1391476/+subscriptions

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

[Kernel-packages] [Bug 1404242] WifiSyslog.txt

[Matthew Caron]

apport information

** Attachment added: "WifiSyslog.txt"
   
https://bugs.launchpad.net/bugs/1404242/+attachment/4284248/+files/WifiSyslog.txt

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

Title:
  Radeon crash on 14.04 LTS stops Xorg from starting

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Kernel message:

  [   31.778064] BUG: unable to handle kernel paging request at ec200900
  [   31.778105] IP: [] kfree+0x56/0x140
  [   31.778133] PGD 0 
  [   31.778145] Oops:  [#1] SMP 
  [   31.778165] Modules linked in: snd_hrtimer pci_stub vboxpci(OX) 
vboxnetadp(OX) vboxnetflt(OX) vboxdrv(OX) bnep rfcomm bluetooth ip6t_REJECT 
xt_hl ip6t_rt nf_conntrack_ipv6 nf_defrag_ipv6 ipt_REJECT xt_LOG 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 radeon snd_hda_codec_hdmi snd_hda_codec_realtek snd_hda_intel 
snd_hda_codec gpio_ich snd_hwdep kvm_intel snd_pcm snd_page_alloc ttm 
snd_seq_midi snd_seq_midi_event snd_rawmidi snd_seq snd_seq_device kvm 
snd_timer drm_kms_helper snd drm soundcore i2c_algo_bit serio_raw x38_edac 
lpc_ich edac_core mac_hid binfmt_misc parport_pc ppdev vhba(OX) coretemp it87 
hwmon_vid lp parport pata_acpi hid_generic usbhid hid raid10 raid456 
async_raid6_recov async_memcpy async_pq async_xor async_tx xor firewire_ohci 
firewire_core crc_itu_t ahci raid6_pq r8169 pata_jmic
 ron mii libahci raid1 raid0 multipath floppy linear
  [   31.778734] CPU: 0 PID: 2402 Comm: Xorg Tainted: G   OX 
3.13.0-43-generic #72-Ubuntu
  [   31.778769] Hardware name: Gigabyte Technology Co., Ltd. X48-DQ6/X48-DQ6, 
BIOS F6 02/29/2008
  [   31.778805] task: 8802229e6000 ti: 8802216da000 task.ti: 
8802216da000
  [   31.778835] RIP: 0010:[]  [] 
kfree+0x56/0x140
  [   31.778869] RSP: 0018:8802216dba68  EFLAGS: 00010286
  [   31.778892] RAX: ec200900 RBX: 10024414 RCX: 

  [   31.778922] RDX: ea00 RSI: 5f78 RDI: 
10024414
  [   31.778951] RBP: 8802216dba80 R08: 0013 R09: 
0012
  [   31.778980] R10: ea000880a380 R11: a0405bc1 R12: 

  [   31.779009] R13: a04623b6 R14:  R15: 
88003655e400
  [   31.779039] FS:  7f229d9019c0() GS:88022fc0() 
knlGS:
  [   31.779072] CS:  0010 DS:  ES:  CR0: 80050033
  [   31.779096] CR2: ec200900 CR3: 0002209d8000 CR4: 
07f0
  [   31.779125] Stack:
  [   31.779135]  8800cae3  8800cae3 
8802216dbb38
  [   31.779174]  a04623b6 8802216dbab0 88027048 
7044712c
  [   31.779211]  8802209ee000 10024414 18824414 
18028488
  [   31.779249] Call Trace:
  [   31.779289]  [] evergreen_hdmi_setmode+0x776/0x960 
[radeon]
  [   31.779334]  [] ? drm_detect_hdmi_monitor+0x6e/0xb0 [drm]
  [   31.779385]  [] radeon_atom_encoder_mode_set+0x158/0x2d0 
[radeon]
  [   31.779421]  [] drm_crtc_helper_set_mode+0x498/0x500 
[drm_kms_helper]
  [   31.779470]  [] 
radeon_property_change_mode.isra.1+0x35/0x40 [radeon]
  [   31.779519]  [] 
radeon_connector_set_property+0x18e/0x300 [radeon]
  [   31.779562]  [] 
drm_mode_obj_set_property_ioctl+0x142/0x340 [drm]
  [   31.779604]  [] 
drm_mode_connector_property_set_ioctl+0x30/0x40 [drm]
  [   31.779644]  [] drm_ioctl+0x502/0x630 [drm]
  [   31.779672]  [] ? __do_page_fault+0x204/0x560
  [   31.779707]  [] radeon_drm_ioctl+0x4e/0x90 [radeon]
  [   31.779736]  [] do_vfs_ioctl+0x2e0/0x4c0
  [   31.779762]  [] ? __sb_end_write+0x31/0x60
  [   31.779787]  [] SyS_ioctl+0x81/0xa0
  [   31.779810]  [] system_call_fastpath+0x1a/0x1f
  [   31.779836] Code: 00 00 00 80 ff 77 00 00 48 01 d8 48 0f 42 15 e2 2f a7 00 
48 01 d0 48 ba 00 00 00 00 00 ea ff ff 48 c1 e8 0c 48 c1 e0 06 48 01 d0 <48> 8b 
10 80 e6 80 0f 85 be 00 00 00 49 89 c2 49 8b 02 a8 80 0f 
  [   31.78] RIP  [] kfree+0x56/0x140
  [   31.78]  RSP 
  [   31.78] CR2: ec200900

  Kernel is:

  3.13.0-43-generic

  This looks similar to #1397553, except applies to Trusty.
  --- 
  ApportVersion: 2.14.1-0ubuntu3.6
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/hwC0D2', 
'/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D1c', '/dev/snd/pcmC0D1p', 
'/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', 
'/dev/snd/by-path', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D3p', 
'/dev/snd/controlC1', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=/dev/mapper/drives-swap
  IwConfig:
   eth

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

[Matthew Caron]

apport information

** Attachment added: "CurrentDmesg.txt"
   
https://bugs.launchpad.net/bugs/1404242/+attachment/4284239/+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/1404242

Title:
  Radeon crash on 14.04 LTS stops Xorg from starting

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Kernel message:

  [   31.778064] BUG: unable to handle kernel paging request at ec200900
  [   31.778105] IP: [] kfree+0x56/0x140
  [   31.778133] PGD 0 
  [   31.778145] Oops:  [#1] SMP 
  [   31.778165] Modules linked in: snd_hrtimer pci_stub vboxpci(OX) 
vboxnetadp(OX) vboxnetflt(OX) vboxdrv(OX) bnep rfcomm bluetooth ip6t_REJECT 
xt_hl ip6t_rt nf_conntrack_ipv6 nf_defrag_ipv6 ipt_REJECT xt_LOG 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 radeon snd_hda_codec_hdmi snd_hda_codec_realtek snd_hda_intel 
snd_hda_codec gpio_ich snd_hwdep kvm_intel snd_pcm snd_page_alloc ttm 
snd_seq_midi snd_seq_midi_event snd_rawmidi snd_seq snd_seq_device kvm 
snd_timer drm_kms_helper snd drm soundcore i2c_algo_bit serio_raw x38_edac 
lpc_ich edac_core mac_hid binfmt_misc parport_pc ppdev vhba(OX) coretemp it87 
hwmon_vid lp parport pata_acpi hid_generic usbhid hid raid10 raid456 
async_raid6_recov async_memcpy async_pq async_xor async_tx xor firewire_ohci 
firewire_core crc_itu_t ahci raid6_pq r8169 pata_jmic
 ron mii libahci raid1 raid0 multipath floppy linear
  [   31.778734] CPU: 0 PID: 2402 Comm: Xorg Tainted: G   OX 
3.13.0-43-generic #72-Ubuntu
  [   31.778769] Hardware name: Gigabyte Technology Co., Ltd. X48-DQ6/X48-DQ6, 
BIOS F6 02/29/2008
  [   31.778805] task: 8802229e6000 ti: 8802216da000 task.ti: 
8802216da000
  [   31.778835] RIP: 0010:[]  [] 
kfree+0x56/0x140
  [   31.778869] RSP: 0018:8802216dba68  EFLAGS: 00010286
  [   31.778892] RAX: ec200900 RBX: 10024414 RCX: 

  [   31.778922] RDX: ea00 RSI: 5f78 RDI: 
10024414
  [   31.778951] RBP: 8802216dba80 R08: 0013 R09: 
0012
  [   31.778980] R10: ea000880a380 R11: a0405bc1 R12: 

  [   31.779009] R13: a04623b6 R14:  R15: 
88003655e400
  [   31.779039] FS:  7f229d9019c0() GS:88022fc0() 
knlGS:
  [   31.779072] CS:  0010 DS:  ES:  CR0: 80050033
  [   31.779096] CR2: ec200900 CR3: 0002209d8000 CR4: 
07f0
  [   31.779125] Stack:
  [   31.779135]  8800cae3  8800cae3 
8802216dbb38
  [   31.779174]  a04623b6 8802216dbab0 88027048 
7044712c
  [   31.779211]  8802209ee000 10024414 18824414 
18028488
  [   31.779249] Call Trace:
  [   31.779289]  [] evergreen_hdmi_setmode+0x776/0x960 
[radeon]
  [   31.779334]  [] ? drm_detect_hdmi_monitor+0x6e/0xb0 [drm]
  [   31.779385]  [] radeon_atom_encoder_mode_set+0x158/0x2d0 
[radeon]
  [   31.779421]  [] drm_crtc_helper_set_mode+0x498/0x500 
[drm_kms_helper]
  [   31.779470]  [] 
radeon_property_change_mode.isra.1+0x35/0x40 [radeon]
  [   31.779519]  [] 
radeon_connector_set_property+0x18e/0x300 [radeon]
  [   31.779562]  [] 
drm_mode_obj_set_property_ioctl+0x142/0x340 [drm]
  [   31.779604]  [] 
drm_mode_connector_property_set_ioctl+0x30/0x40 [drm]
  [   31.779644]  [] drm_ioctl+0x502/0x630 [drm]
  [   31.779672]  [] ? __do_page_fault+0x204/0x560
  [   31.779707]  [] radeon_drm_ioctl+0x4e/0x90 [radeon]
  [   31.779736]  [] do_vfs_ioctl+0x2e0/0x4c0
  [   31.779762]  [] ? __sb_end_write+0x31/0x60
  [   31.779787]  [] SyS_ioctl+0x81/0xa0
  [   31.779810]  [] system_call_fastpath+0x1a/0x1f
  [   31.779836] Code: 00 00 00 80 ff 77 00 00 48 01 d8 48 0f 42 15 e2 2f a7 00 
48 01 d0 48 ba 00 00 00 00 00 ea ff ff 48 c1 e8 0c 48 c1 e0 06 48 01 d0 <48> 8b 
10 80 e6 80 0f 85 be 00 00 00 49 89 c2 49 8b 02 a8 80 0f 
  [   31.78] RIP  [] kfree+0x56/0x140
  [   31.78]  RSP 
  [   31.78] CR2: ec200900

  Kernel is:

  3.13.0-43-generic

  This looks similar to #1397553, except applies to Trusty.
  --- 
  ApportVersion: 2.14.1-0ubuntu3.6
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/hwC0D2', 
'/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D1c', '/dev/snd/pcmC0D1p', 
'/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', 
'/dev/snd/by-path', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D3p', 
'/dev/snd/controlC1', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=/dev/mapper/drives-swap
  IwConfig:
   eth0  no wireless extensions.
   
   eth1  no wireless extens

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

[Matthew Caron]

apport information

** Attachment added: "UdevLog.txt"
   
https://bugs.launchpad.net/bugs/1404242/+attachment/4284247/+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/1404242

Title:
  Radeon crash on 14.04 LTS stops Xorg from starting

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Kernel message:

  [   31.778064] BUG: unable to handle kernel paging request at ec200900
  [   31.778105] IP: [] kfree+0x56/0x140
  [   31.778133] PGD 0 
  [   31.778145] Oops:  [#1] SMP 
  [   31.778165] Modules linked in: snd_hrtimer pci_stub vboxpci(OX) 
vboxnetadp(OX) vboxnetflt(OX) vboxdrv(OX) bnep rfcomm bluetooth ip6t_REJECT 
xt_hl ip6t_rt nf_conntrack_ipv6 nf_defrag_ipv6 ipt_REJECT xt_LOG 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 radeon snd_hda_codec_hdmi snd_hda_codec_realtek snd_hda_intel 
snd_hda_codec gpio_ich snd_hwdep kvm_intel snd_pcm snd_page_alloc ttm 
snd_seq_midi snd_seq_midi_event snd_rawmidi snd_seq snd_seq_device kvm 
snd_timer drm_kms_helper snd drm soundcore i2c_algo_bit serio_raw x38_edac 
lpc_ich edac_core mac_hid binfmt_misc parport_pc ppdev vhba(OX) coretemp it87 
hwmon_vid lp parport pata_acpi hid_generic usbhid hid raid10 raid456 
async_raid6_recov async_memcpy async_pq async_xor async_tx xor firewire_ohci 
firewire_core crc_itu_t ahci raid6_pq r8169 pata_jmic
 ron mii libahci raid1 raid0 multipath floppy linear
  [   31.778734] CPU: 0 PID: 2402 Comm: Xorg Tainted: G   OX 
3.13.0-43-generic #72-Ubuntu
  [   31.778769] Hardware name: Gigabyte Technology Co., Ltd. X48-DQ6/X48-DQ6, 
BIOS F6 02/29/2008
  [   31.778805] task: 8802229e6000 ti: 8802216da000 task.ti: 
8802216da000
  [   31.778835] RIP: 0010:[]  [] 
kfree+0x56/0x140
  [   31.778869] RSP: 0018:8802216dba68  EFLAGS: 00010286
  [   31.778892] RAX: ec200900 RBX: 10024414 RCX: 

  [   31.778922] RDX: ea00 RSI: 5f78 RDI: 
10024414
  [   31.778951] RBP: 8802216dba80 R08: 0013 R09: 
0012
  [   31.778980] R10: ea000880a380 R11: a0405bc1 R12: 

  [   31.779009] R13: a04623b6 R14:  R15: 
88003655e400
  [   31.779039] FS:  7f229d9019c0() GS:88022fc0() 
knlGS:
  [   31.779072] CS:  0010 DS:  ES:  CR0: 80050033
  [   31.779096] CR2: ec200900 CR3: 0002209d8000 CR4: 
07f0
  [   31.779125] Stack:
  [   31.779135]  8800cae3  8800cae3 
8802216dbb38
  [   31.779174]  a04623b6 8802216dbab0 88027048 
7044712c
  [   31.779211]  8802209ee000 10024414 18824414 
18028488
  [   31.779249] Call Trace:
  [   31.779289]  [] evergreen_hdmi_setmode+0x776/0x960 
[radeon]
  [   31.779334]  [] ? drm_detect_hdmi_monitor+0x6e/0xb0 [drm]
  [   31.779385]  [] radeon_atom_encoder_mode_set+0x158/0x2d0 
[radeon]
  [   31.779421]  [] drm_crtc_helper_set_mode+0x498/0x500 
[drm_kms_helper]
  [   31.779470]  [] 
radeon_property_change_mode.isra.1+0x35/0x40 [radeon]
  [   31.779519]  [] 
radeon_connector_set_property+0x18e/0x300 [radeon]
  [   31.779562]  [] 
drm_mode_obj_set_property_ioctl+0x142/0x340 [drm]
  [   31.779604]  [] 
drm_mode_connector_property_set_ioctl+0x30/0x40 [drm]
  [   31.779644]  [] drm_ioctl+0x502/0x630 [drm]
  [   31.779672]  [] ? __do_page_fault+0x204/0x560
  [   31.779707]  [] radeon_drm_ioctl+0x4e/0x90 [radeon]
  [   31.779736]  [] do_vfs_ioctl+0x2e0/0x4c0
  [   31.779762]  [] ? __sb_end_write+0x31/0x60
  [   31.779787]  [] SyS_ioctl+0x81/0xa0
  [   31.779810]  [] system_call_fastpath+0x1a/0x1f
  [   31.779836] Code: 00 00 00 80 ff 77 00 00 48 01 d8 48 0f 42 15 e2 2f a7 00 
48 01 d0 48 ba 00 00 00 00 00 ea ff ff 48 c1 e8 0c 48 c1 e0 06 48 01 d0 <48> 8b 
10 80 e6 80 0f 85 be 00 00 00 49 89 c2 49 8b 02 a8 80 0f 
  [   31.78] RIP  [] kfree+0x56/0x140
  [   31.78]  RSP 
  [   31.78] CR2: ec200900

  Kernel is:

  3.13.0-43-generic

  This looks similar to #1397553, except applies to Trusty.
  --- 
  ApportVersion: 2.14.1-0ubuntu3.6
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/hwC0D2', 
'/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D1c', '/dev/snd/pcmC0D1p', 
'/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', 
'/dev/snd/by-path', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D3p', 
'/dev/snd/controlC1', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=/dev/mapper/drives-swap
  IwConfig:
   eth0  no wireless extensions.
   
   eth1  no wireless extensions.
   

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

[Matthew Caron]

apport information

** Attachment added: "ProcCpuinfo.txt"
   
https://bugs.launchpad.net/bugs/1404242/+attachment/4284242/+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/1404242

Title:
  Radeon crash on 14.04 LTS stops Xorg from starting

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Kernel message:

  [   31.778064] BUG: unable to handle kernel paging request at ec200900
  [   31.778105] IP: [] kfree+0x56/0x140
  [   31.778133] PGD 0 
  [   31.778145] Oops:  [#1] SMP 
  [   31.778165] Modules linked in: snd_hrtimer pci_stub vboxpci(OX) 
vboxnetadp(OX) vboxnetflt(OX) vboxdrv(OX) bnep rfcomm bluetooth ip6t_REJECT 
xt_hl ip6t_rt nf_conntrack_ipv6 nf_defrag_ipv6 ipt_REJECT xt_LOG 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 radeon snd_hda_codec_hdmi snd_hda_codec_realtek snd_hda_intel 
snd_hda_codec gpio_ich snd_hwdep kvm_intel snd_pcm snd_page_alloc ttm 
snd_seq_midi snd_seq_midi_event snd_rawmidi snd_seq snd_seq_device kvm 
snd_timer drm_kms_helper snd drm soundcore i2c_algo_bit serio_raw x38_edac 
lpc_ich edac_core mac_hid binfmt_misc parport_pc ppdev vhba(OX) coretemp it87 
hwmon_vid lp parport pata_acpi hid_generic usbhid hid raid10 raid456 
async_raid6_recov async_memcpy async_pq async_xor async_tx xor firewire_ohci 
firewire_core crc_itu_t ahci raid6_pq r8169 pata_jmic
 ron mii libahci raid1 raid0 multipath floppy linear
  [   31.778734] CPU: 0 PID: 2402 Comm: Xorg Tainted: G   OX 
3.13.0-43-generic #72-Ubuntu
  [   31.778769] Hardware name: Gigabyte Technology Co., Ltd. X48-DQ6/X48-DQ6, 
BIOS F6 02/29/2008
  [   31.778805] task: 8802229e6000 ti: 8802216da000 task.ti: 
8802216da000
  [   31.778835] RIP: 0010:[]  [] 
kfree+0x56/0x140
  [   31.778869] RSP: 0018:8802216dba68  EFLAGS: 00010286
  [   31.778892] RAX: ec200900 RBX: 10024414 RCX: 

  [   31.778922] RDX: ea00 RSI: 5f78 RDI: 
10024414
  [   31.778951] RBP: 8802216dba80 R08: 0013 R09: 
0012
  [   31.778980] R10: ea000880a380 R11: a0405bc1 R12: 

  [   31.779009] R13: a04623b6 R14:  R15: 
88003655e400
  [   31.779039] FS:  7f229d9019c0() GS:88022fc0() 
knlGS:
  [   31.779072] CS:  0010 DS:  ES:  CR0: 80050033
  [   31.779096] CR2: ec200900 CR3: 0002209d8000 CR4: 
07f0
  [   31.779125] Stack:
  [   31.779135]  8800cae3  8800cae3 
8802216dbb38
  [   31.779174]  a04623b6 8802216dbab0 88027048 
7044712c
  [   31.779211]  8802209ee000 10024414 18824414 
18028488
  [   31.779249] Call Trace:
  [   31.779289]  [] evergreen_hdmi_setmode+0x776/0x960 
[radeon]
  [   31.779334]  [] ? drm_detect_hdmi_monitor+0x6e/0xb0 [drm]
  [   31.779385]  [] radeon_atom_encoder_mode_set+0x158/0x2d0 
[radeon]
  [   31.779421]  [] drm_crtc_helper_set_mode+0x498/0x500 
[drm_kms_helper]
  [   31.779470]  [] 
radeon_property_change_mode.isra.1+0x35/0x40 [radeon]
  [   31.779519]  [] 
radeon_connector_set_property+0x18e/0x300 [radeon]
  [   31.779562]  [] 
drm_mode_obj_set_property_ioctl+0x142/0x340 [drm]
  [   31.779604]  [] 
drm_mode_connector_property_set_ioctl+0x30/0x40 [drm]
  [   31.779644]  [] drm_ioctl+0x502/0x630 [drm]
  [   31.779672]  [] ? __do_page_fault+0x204/0x560
  [   31.779707]  [] radeon_drm_ioctl+0x4e/0x90 [radeon]
  [   31.779736]  [] do_vfs_ioctl+0x2e0/0x4c0
  [   31.779762]  [] ? __sb_end_write+0x31/0x60
  [   31.779787]  [] SyS_ioctl+0x81/0xa0
  [   31.779810]  [] system_call_fastpath+0x1a/0x1f
  [   31.779836] Code: 00 00 00 80 ff 77 00 00 48 01 d8 48 0f 42 15 e2 2f a7 00 
48 01 d0 48 ba 00 00 00 00 00 ea ff ff 48 c1 e8 0c 48 c1 e0 06 48 01 d0 <48> 8b 
10 80 e6 80 0f 85 be 00 00 00 49 89 c2 49 8b 02 a8 80 0f 
  [   31.78] RIP  [] kfree+0x56/0x140
  [   31.78]  RSP 
  [   31.78] CR2: ec200900

  Kernel is:

  3.13.0-43-generic

  This looks similar to #1397553, except applies to Trusty.
  --- 
  ApportVersion: 2.14.1-0ubuntu3.6
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/hwC0D2', 
'/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D1c', '/dev/snd/pcmC0D1p', 
'/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', 
'/dev/snd/by-path', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D3p', 
'/dev/snd/controlC1', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=/dev/mapper/drives-swap
  IwConfig:
   eth0  no wireless extensions.
   
   eth1  no wireless extensio

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

[Matthew Caron]

apport information

** Attachment added: "ProcInterrupts.txt"
   
https://bugs.launchpad.net/bugs/1404242/+attachment/4284244/+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/1404242

Title:
  Radeon crash on 14.04 LTS stops Xorg from starting

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Kernel message:

  [   31.778064] BUG: unable to handle kernel paging request at ec200900
  [   31.778105] IP: [] kfree+0x56/0x140
  [   31.778133] PGD 0 
  [   31.778145] Oops:  [#1] SMP 
  [   31.778165] Modules linked in: snd_hrtimer pci_stub vboxpci(OX) 
vboxnetadp(OX) vboxnetflt(OX) vboxdrv(OX) bnep rfcomm bluetooth ip6t_REJECT 
xt_hl ip6t_rt nf_conntrack_ipv6 nf_defrag_ipv6 ipt_REJECT xt_LOG 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 radeon snd_hda_codec_hdmi snd_hda_codec_realtek snd_hda_intel 
snd_hda_codec gpio_ich snd_hwdep kvm_intel snd_pcm snd_page_alloc ttm 
snd_seq_midi snd_seq_midi_event snd_rawmidi snd_seq snd_seq_device kvm 
snd_timer drm_kms_helper snd drm soundcore i2c_algo_bit serio_raw x38_edac 
lpc_ich edac_core mac_hid binfmt_misc parport_pc ppdev vhba(OX) coretemp it87 
hwmon_vid lp parport pata_acpi hid_generic usbhid hid raid10 raid456 
async_raid6_recov async_memcpy async_pq async_xor async_tx xor firewire_ohci 
firewire_core crc_itu_t ahci raid6_pq r8169 pata_jmic
 ron mii libahci raid1 raid0 multipath floppy linear
  [   31.778734] CPU: 0 PID: 2402 Comm: Xorg Tainted: G   OX 
3.13.0-43-generic #72-Ubuntu
  [   31.778769] Hardware name: Gigabyte Technology Co., Ltd. X48-DQ6/X48-DQ6, 
BIOS F6 02/29/2008
  [   31.778805] task: 8802229e6000 ti: 8802216da000 task.ti: 
8802216da000
  [   31.778835] RIP: 0010:[]  [] 
kfree+0x56/0x140
  [   31.778869] RSP: 0018:8802216dba68  EFLAGS: 00010286
  [   31.778892] RAX: ec200900 RBX: 10024414 RCX: 

  [   31.778922] RDX: ea00 RSI: 5f78 RDI: 
10024414
  [   31.778951] RBP: 8802216dba80 R08: 0013 R09: 
0012
  [   31.778980] R10: ea000880a380 R11: a0405bc1 R12: 

  [   31.779009] R13: a04623b6 R14:  R15: 
88003655e400
  [   31.779039] FS:  7f229d9019c0() GS:88022fc0() 
knlGS:
  [   31.779072] CS:  0010 DS:  ES:  CR0: 80050033
  [   31.779096] CR2: ec200900 CR3: 0002209d8000 CR4: 
07f0
  [   31.779125] Stack:
  [   31.779135]  8800cae3  8800cae3 
8802216dbb38
  [   31.779174]  a04623b6 8802216dbab0 88027048 
7044712c
  [   31.779211]  8802209ee000 10024414 18824414 
18028488
  [   31.779249] Call Trace:
  [   31.779289]  [] evergreen_hdmi_setmode+0x776/0x960 
[radeon]
  [   31.779334]  [] ? drm_detect_hdmi_monitor+0x6e/0xb0 [drm]
  [   31.779385]  [] radeon_atom_encoder_mode_set+0x158/0x2d0 
[radeon]
  [   31.779421]  [] drm_crtc_helper_set_mode+0x498/0x500 
[drm_kms_helper]
  [   31.779470]  [] 
radeon_property_change_mode.isra.1+0x35/0x40 [radeon]
  [   31.779519]  [] 
radeon_connector_set_property+0x18e/0x300 [radeon]
  [   31.779562]  [] 
drm_mode_obj_set_property_ioctl+0x142/0x340 [drm]
  [   31.779604]  [] 
drm_mode_connector_property_set_ioctl+0x30/0x40 [drm]
  [   31.779644]  [] drm_ioctl+0x502/0x630 [drm]
  [   31.779672]  [] ? __do_page_fault+0x204/0x560
  [   31.779707]  [] radeon_drm_ioctl+0x4e/0x90 [radeon]
  [   31.779736]  [] do_vfs_ioctl+0x2e0/0x4c0
  [   31.779762]  [] ? __sb_end_write+0x31/0x60
  [   31.779787]  [] SyS_ioctl+0x81/0xa0
  [   31.779810]  [] system_call_fastpath+0x1a/0x1f
  [   31.779836] Code: 00 00 00 80 ff 77 00 00 48 01 d8 48 0f 42 15 e2 2f a7 00 
48 01 d0 48 ba 00 00 00 00 00 ea ff ff 48 c1 e8 0c 48 c1 e0 06 48 01 d0 <48> 8b 
10 80 e6 80 0f 85 be 00 00 00 49 89 c2 49 8b 02 a8 80 0f 
  [   31.78] RIP  [] kfree+0x56/0x140
  [   31.78]  RSP 
  [   31.78] CR2: ec200900

  Kernel is:

  3.13.0-43-generic

  This looks similar to #1397553, except applies to Trusty.
  --- 
  ApportVersion: 2.14.1-0ubuntu3.6
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/hwC0D2', 
'/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D1c', '/dev/snd/pcmC0D1p', 
'/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', 
'/dev/snd/by-path', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D3p', 
'/dev/snd/controlC1', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=/dev/mapper/drives-swap
  IwConfig:
   eth0  no wireless extensions.
   
   eth1  no wireless ex